Explore topic-wise InterviewSolutions in .

BASICALLY they have TWO OPTION, public and private if section declared as public then it be ACCESS from other program. Private we cannot call from other program.

Basically they have two option, public and private if section declared as public then it be access from other program. Private we cannot call from other program.

SQL and callsection.

Sql and callsection.

Step properties:-

On Error: –

• Abort – Write message to message log and terminate.
• Ignore – Write message to message log and continue.
• Uppress – No message will be WRITTEN, but program will continue.

People code Action: –

• On RETURN options can used to handle run time errors.
• Abort: – Exits immediately – Not recommended.
• Break: – Exits the current step and section and control returns to the calling step.
• Skip Step: – The program exits the current step, and continues processing at the NEXT step in the section. If this is the LAST step in the section, the calling step resumes control of the processing.

SQL Action properties: –

• No Rows: – When the Sql doesn’t return any rows, you can tell what application engine program should do.
• Abort: -Program terminates Section Break: -Application Engine exits the current section immediately, and control returns to the calling step.
• Continue: – The program continues processing Skip Step: – Application Engine exits the current step immediately and MOVES on to the next step.
• When using skip step keep the following in mind:1) Application Engine ignores the commit for the current step at runtime2) If the current step contains only one Action, only use skip step at by-pass the commit.

Step properties:-

On Error: –

People code Action: –

SQL Action properties: –

• Select/Fetch: Opens the cursor only at the first time and retrieve rows one at loop
• Reselect: It opens the cursor and closes the cursor on each iteration of the loop. It will reselect the same ROW of DATA. Logic in Actions of the step should be such that it will be changing the STATUS of the rows in the table the do select is selecting. Commits are not ignored and will be committed in a reselect loop when the restart is enabled
• Restart able: similar to select/Fetch but it WILL COMMIT inside the loop THUS allowing the checkpoint to the PS_AERUNCONTROL table.

99

99

• %SELECT: if any values have not SELECTED then previous value will be there
• %selectinit : if any values have not selected then previous value will reinitiate to null

• EXIT (1) causes IMMEDIATE termination of a Peoplecode program. Use this PARAMETER to ROLLBACK database changes.
• Exit (0) caused immediate termination of a Peoplecode Program but don’t MAKE rollback in the database.

Run control PARAMETERS passed to each instance of the AE PROGRAM enable it to identify which INPUT rows “BELONG” to it, and each program instance inserts the rows from the source table into its assigned TEMPORARY table instance using %Table.

Run control parameters passed to each instance of the AE program enable it to identify which input rows “belong” to it, and each program instance inserts the rows from the source table into its assigned temporary table instance using %Table.

• It behaviour can control by AE developer. If the RUNTIME OPTIONS are set to continue
• “People Tools will insert rows into the base table using the PROCESS_INSTANCE as a key”
• If temp table doesn’t contain PROCESS_INSTANCE as a key FIELD in a Temporary table, you should CHANGE the
• Temp table runtime options to “Abort” in the appropriate Application Engine programs.

• Define you Temporary Tables.
• Set the Temporary Tables Online pool.
• ASSIGN Temporary Tables to your Application ENGINE PROGRAM in it program.
• Set Temporary Table Batch Pool – INSTANCE count in the AE.
• Build / Rebuild your Temporary Table record.
• Code %Table Meta – SQL as reference to Temporary Tables in your Application Engine program,

so that Application Engine can table references to the assigned Temporary Table instance dynamically at runtime.

so that Application Engine can table references to the assigned Temporary Table instance dynamically at runtime.

Application Engine programs are designed for two types of execution and each has its own pool of Temporary TABLES

• Online: Invoked by CallAppEngine from People Code Run quickly, synchronously, and at random times. Potential for simultaneous executions Uses the online Temporary Table pool. Not restart able. Psae.exe randomly assigns an instance NUMBER from the number range on your online temp tables. If the instance number is in use psae.exe puts the program in Queue until the assigned instance becomes free. Unlock on completion, on Crash free from Manage Abends.
• Batch: Invoked through the Process Scheduler. Run for LONGER amounts of time, asynchronously, and at scheduled times. Can be designed for parallel execution for performance. Uses the Batch/Dedicated Temporary table. Restart able. It allocates instance number based on the availability on a record by record basis and psae.exe begins with the lowest instance numbers. If the properties are SET continue – Base table is used with Process instance as key. If Re-startable – Locked ACROSS Restarts until completes successfully. If not Re-startable on Program completion.

Application Engine programs are designed for two types of execution and each has its own pool of Temporary Tables

Multiple TEMPORARY tables as a POOL of tables will be helpful to achieve parallel processing. Each invocation of your program WOULD have to allocate an unused temporary table, mark it as ‘in use’, use it and RELEASE it back to the pool when you through with it (for each Application ENGINE program you write).

Multiple temporary tables as a pool of tables will be helpful to achieve parallel processing. Each invocation of your program would have to allocate an unused temporary table, mark it as ‘in use’, use it and release it back to the pool when you through with it (for each Application Engine program you write).

• DEDICATED
• UN Dedicated (SHARED)

• Should have PROCESS INSTANCE as KEY
• NAME should end with _TAO

• Do When
• Do While
• Do Select
• Peoplecode
• SQL
• CALL SECTION
• MESSAGE Log
• XSLT
• Do until

• Application Engine Trace File-You can track the step execution of your application execution
• Application Engine Interactive Debugger – First click on the trace tab and turn off the statement TIMINGS.

Select PROFILE -> Edit Profile-> Process Scheduler Tab -> Application section Select Debug check box.
(You can dynamically modify the state record run application engine step by step People Code Debugger for the Application Engine.)
AE Trace FILES: – AE_<PROGRAM Name>_<Process Instance>.AET Without the process instance: – AE_<Date/Timestamp>_<OS_PID>.AET

Select Profile -> Edit Profile-> Process Scheduler Tab -> Application section Select Debug check box.
(You can dynamically modify the state record run application engine step by step People Code Debugger for the Application Engine.)
AE Trace files: – AE_<Program Name>_<Process Instance>.AET Without the process instance: – AE_<Date/Timestamp>_<OS_PID>.AET

• Improved Performance: – Set processing performs SIGNIFICANTLY better than it is -by-row counterpart for “reasonable” batch processing VOLUMES.
• Minimized SQL Overhead: – It tends to use fewer APPLICATION Engine SQL statements that each processed more data than the statements executed in row-by-row processing.
• Easy Maintenance: – if need to make a fix or add an enhancement to SQL, it’s just a matter of modifying the SQL or inserting the new “Chunk”. Leveraging the RDBMS: – With Set – based processing, you take advantage of the SQL processing engine on the database RATHER than placing the processing burden and overhead on the application executable.

Set Processing uses SQL to process groups, or sets, of rows at one time rather than processing each row individually. With row by row processing you following a REPETITIVE loop that selects a row, determines if it meets a GIVEN criterion, if so, apply RULE x to row Update row, COMMIT. With set processing, you only select those rows that meet the filtering criteria and then run the rule once again all the affected rows.

Set Processing uses SQL to process groups, or sets, of rows at one time rather than processing each row individually. With row by row processing you following a repetitive loop that selects a row, determines if it meets a given criterion, if so, apply rule x to row Update row, commit. With set processing, you only select those rows that meet the filtering criteria and then run the rule once again all the affected rows.

PROGRAM Level:

• State Record: One of the state record needs to SQL Table, Since All Derived work record will be re-initializing on commit.
• Program Properties: On the ADVANCED tab in the program properties dialog box, make sure that disable restart is not checked
• Configuration manager: In the configuration manager, sure that Disable restart is not selected on the process scheduler tab.

Section Level Section type:

• The option for section type are prepare only and critical updates
• If the section is preparing data i, e select data, POPULATING temporary TABLES, or updating temporary tables then the section should be prepare only
• If the section is updating the permanent APPLICATION tables in the database, you should select critical update.

Step Level Add an order by clauseThe only restriction for batch runs occurs when you have restart enabled, and you are inside a Do Select that is of the Select/Fetch type (instead of “Re-select” or “Restartable”). with select/Fetch, all commits inside the loop are ignored, including the commit frequency if it’s set.

Program Level:

Section Level Section type:

Step Level Add an order by clauseThe only restriction for batch runs occurs when you have restart enabled, and you are inside a Do Select that is of the Select/Fetch type (instead of “Re-select” or “Restartable”). with select/Fetch, all commits inside the loop are ignored, including the commit frequency if it’s set.

In GENERAL, the TYPES are:

• Standard : Standard entry-point PROGRAM.
• Upgrade Only : USED by PeopleSoft Upgrade utilities only
• Import Only : Used by PeopleSoft Import utilities only
• Daemon Only : Use for daemon type programs
• Transform Only : Support for XSLT Transform programs

In general, the types are:

The 3 COMMON ways to pass a trace PARAMETER are the following:

• Configuration manager
• Process DEFINITION
• Command prompt

The 3 common ways to pass a trace parameter are the following:

• A Trace PARAMETER DETERMINES which TYPE of trace is turned on.
• A Trace value determines what type of DATA is RECORDED in your trace files.

• TRACE &LT;trace value> 384 – mostly USED trace value.

As FOLLOWING:

• TRACE &LT;trace VALUE&GT;
• TOOLSTRACESQL <trace value>
• TOOLSTRACEPC <trace value>

As following:

The SYNTAX for CALLAPPENGINE is as below:

CallAppEngine (APPLID [, STATE RECORD]);

The Syntax for CallAppEngine is as below:

CallAppEngine (applid [, state record]);

Application ENGINE can be execute with a SINGLE click on Push BUTTON, by using the following:

• CreateProcessRequest () , Schedule ()
• CallAppEngine.

Application Engine can be execute with a single click on Push Button, by using the following:

There are many ways of reading run-control parameters in AE, most COMMONLY used are:

• SQL:

%SELECT (EMPLID) /*This will PASS value to State record*/

Select EMPLID from PS_AERUNCONTROL where PROCESS_INSTANCE = %PROCESS_INSTANCE and OPRID= %OPRID

• People code:

&SQL = “Select EMPLID from PS_AERUNCONTROL Where PROCESS_INSTACNE = RECORD.PROCESS_INSTANCE and OPRID = %BIND (PROCESS_INSTANCE)

There are many ways of reading run-control parameters in AE, most commonly used are:

%Select (EMPLID) /*This will pass value to State record*/

Select EMPLID from PS_AERUNCONTROL where PROCESS_INSTANCE = %PROCESS_INSTANCE and OPRID= %OPRID

&SQL = “Select EMPLID from PS_AERUNCONTROL Where PROCESS_INSTACNE = RECORD.PROCESS_INSTANCE and OPRID = %Bind (PROCESS_INSTANCE)

To use STATE RECORD, there are certain prerequisites, they are:

• State Record should be a SQL Table or a Derived work record, for AE Restarts we would definitely need State Record as a SQL Table, as Derived work RECORDS store data only at run-time.
• Name of the State Record should end in AET, the SYSTEM identifies the record as a state record with this notation
• We need to use PROCESS_INSTANCE field in the record and it should be defined as a key
• Any data types except character or numeric must not be required fields

To use state record, there are certain prerequisites, they are:

We can pass DATA between steps in THREE different ways, they are:

• Using State RECORDS – One row can be passed and can have many state records.
• Using Component/Global People code variables
• Using TEMPORARY records – Multiple rows of data can be passed.

We can pass data between steps in three different ways, they are:

There are two types of Variables mainly in Application Engine PEOPLECODE, they are:

• Local variable – These are the variables available for the duration of the program in which they are declared.
• Global / Component – These are the variables available while the Application Engine program is RUNNING. They get SAVED at commits and check points, so they can be used for restarts. Component variables are same as Global in case of the AE.

There are two types of Variables mainly in Application Engine Peoplecode, they are: