Thursday 17 April 2014

PeopleSoft Technical Interview Questions & Answers (Application Engine)

* What are the variables in Application Engine Peoplecode ?
  Local- these are available for the duration of the program in which they are declared Global
 Global / Component -These variables are available while the Application Engine program is   running.  They are saved at commits and checkpoints.
so they can be used for restarts. Component variables are same as Global incase of the AE
*What are the Different ways pass data between the steps?  State records- One row can be passed and can have many state records.
 Component/Global People code variables
 Temporary records- Multiple rows of data can be passed.

*What is Prerequisite for the State record?
Should be either Derived work record Or SQL Table.
Name of the record must end in AET; this is how the system identifies the record as a state record.
PROCESS_INSTANCE must be a key.
Any data types except character or numeric must not be required fields
No People code fires on an Application Engine state record.
No Validation of translate values or Prompt tables are done.

*Order and flow of action types ?
Do When
Do While
Do Select
Peoplecode
SQL
Call Section
Message Log
XSLT
Do Until
*What is Prerequisite for the Temporary record?
Should have process Instance as key
Name should end with _TAO

*Different types of Temporary tables?
Dedicated
Un Dedicated (Shared)

*What are the 3 common ways to pass a trace parameter and value to your program psae.exe?
Configuration manager, Process Definition, Command prompt

*What are the 3 trace parameters you can pass to your psae.exe?
TRACE TOOLSTRACESQL TOOLSTRACEPC

*Which Trace option is the best place to start for general performance information?
TRACE <trace value>384 -mostly used trace value.

*How do you program AE program for the restarts?
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
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.
The 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.