Peoplesoft Queries Solutions

Creating a new Application Engine definition Setting program properties Understanding program flow Inserting new sections, steps, and actions Loops/logic State records Adding programs to projects Creating a new Application Engine Definition Application Engine programs are definitions that are created and edited within Application Designer.  So, open Application Designer and log in.  Next, either use the File > New menu, press Ctrl + N, or click on the “New” icon on the toolbar. File > New / Ctrl + N: New icon on the toolbar: After you do that, you should get a New dialog.  There is where you tell Application Designer what type of new object you want to create.  From here, you will want to choose the “App Engine Program” object type. This should give you a new Application Engine program window: You probably want to save your program as you go.  You can use File > Save or Ctrl + S or the Save icon ...

Nodes: If you think about the e-mail analogy, the Node would be like the Domain part of the e-mail addresses. For PeopleSoft-to-PeopleSoft communication, Nodes are (usually) PSFT_EP for Financials, PSFT_HR for HRMS, PSFT_LM for LMS, and PSFT_CRM for CRM. They basically tell which application a message belongs to. The node definition is where you define what messages are valid for that node. Prior to PeopleTools 8.53, you’d define them on the “Transaction” tab. In 8.53 and above, you’d define them on the “Routings” tab. Since you might not want just anybody being able to publish a message to a node, you’ll need to set a node password on the first page of the node definition. This password will have to be the same in all of the environments. For example, if you want to publish a message to PSFT_EP from HRMS, the PSFT_EP node password will have to be the same in both Financials and HRMS. Messages: The message definition is where the developer specifies what data a message will contai...

Most techies who’ve looked under the covers will be aware of PSPCMPROG. It’s the underlying table where PeopleCode is stored.  This isn’t immediately useful however as the actual code itself is stored in the PROGTXT field in binary so it’s not easily accessible. For me, this field isn’t quite the most useful on PSPCMPROG.  You may have noticed that if you update the PeopleCode on a record, the record properties aren’t updated to reflect the change – I guess because the record definition itself hasn’t changed (although strangely Component and Page PeopleCode do update the timestamp on the corresponding Component/Page definition – so there’s a bit of an inconsistency there).  So how do you check when and by whom a piece of Record PeopleCode was last updated? If you check the LASTUPDDTTM and LASTUPDOPRID fields on the PSPCMPROG record via SQL then it’s all recorded there. This snippet of knowledge has saved me (or at least expedited troubleshooting by showing me the corre...

Here, I am sharing peoplecode which is to be used for printing report using a push button from the page. All you need to do is to give the following constraints like- &MyReportName="Name from Report Definition in PIA" &MyTemplate="Template name from Report definition/template tab "  e.g., REPORT_NAME_1 and query prompts to filter the data in the report- &rcdQryPrompts e.g.,&rcdQryPrompts.PO_DT.Value = PO_HDR.PO_DT.Value; --------------------------------------------------------------------------------------------------------------------- import PSXP_RPTDEFNMANAGER:*; &LanguageCd = "ENG"; &AsOfDate = %Date; &OutFormat = "PDF"; &MyReportName = "REPORT_NAME"; &MyTemplate = "REPORT_TEMPLATE_NAME"; Local PSXP_RPTDEFNMANAGER:ReportDefn &oReportDefn = create PSXP_RPTDEFNMANAGER:ReportDefn(&MyReportName); &oReportDefn.Get(); Local Record &rcdQryPrompts...