Explore topic-wise InterviewSolutions in .

• KEY-It is the primary key of the RECORD. Can be used as search key or NEED not be.
• Alternate search key-it is used for SEARCHING purposes.

• UPDATE/display: can VIEW CURRENT and FUTURE rows. Can update only future rows.
• Update/display all: can view HISTORY, current and future rows. Can update only future rows.
• Correction: can view and update history, current and future rows.

We have FIELD LEVEL AUDIT and RECORD level audit.

We have field level audit and record level audit.

The STRUCTURE of the table in RECORD level audit is: AUDIT_OPRID, AUDIT_STAMP, AUDIT_ACTN, AUDIT_RECNAME and can ADD FIELDS from record.

The structure of the table in record level audit is: AUDIT_OPRID, AUDIT_STAMP, AUDIT_ACTN, AUDIT_RECNAME and can add fields from record.

We have PROMPT table EDIT, yes/no table edit, TRANSLATE table edit as the table EDITS.

We have prompt table edit, yes/no table edit, translate table edit as the table edits.

Conditions are:

• The CHILD record should have all the KEY fields of parent record and at least one more key field other than the key fields of parent record.
• We should mention the parent record in the record properties of child record.
• We can not go for more than three levels of parent/child relationships.

ADVANTAGES are:

• To have referential integrity.
• No need to enter information again and again

Conditions are:

Advantages are:

Yes we can insert subpage USING insert subpage. After insert subpage into MAIN PAGE, drag the subpage into the grid. When we save the page we are successfully ABLE to save the page SHOWING that we can insert a subpage into a grid.

Yes we can insert subpage using insert subpage. After insert subpage into main page, drag the subpage into the grid. When we save the page we are successfully able to save the page showing that we can insert a subpage into a grid.

No we can not hide the PRIMARY PAGE of a component. If the component had only one page then by making this page also invisible we WONT have any component existing so we are not allowed to hide the primary page.

No we can not hide the primary page of a component. If the component had only one page then by making this page also invisible we wont have any component existing so we are not allowed to hide the primary page.

Expert entry ENABLES a USER to change from INTERACTIVE to DEFERRED mode at runtime for appropriate transactions

Expert entry enables a user to change from interactive to deferred mode at runtime for appropriate transactions

You might want to reuse the same component multiple TIMES with different search RECORDS. You can accomplish this by overriding the component search record at run-time when the component is opened from a menu item without creating separate copies of the component.

The component OVERRIDE is temporary, and occurs only when the component is opened from the menu item in which the override is SET. It does not change the component definition.

You might want to reuse the same component multiple times with different search records. You can accomplish this by overriding the component search record at run-time when the component is opened from a menu item without creating separate copies of the component.

The component override is temporary, and occurs only when the component is opened from the menu item in which the override is set. It does not change the component definition.

It is n-tier architecture. We have CLIENT, web server, application server and Database server. We have jolt and tuxedo. We have WSL, WSH, JSL, JSH, QUEUES and services. In database server we have SYSTEM TABLES, peopletools tables and application tables.

It is n-tier architecture. We have client, web server, application server and Database server. We have jolt and tuxedo. We have WSL, WSH, JSL, JSH, QUEUES and services. In database server we have system tables, peopletools tables and application tables.

In FIELD EDIT for each field change, a TRANSITION to the application SERVER to the database is taken PLACE. In Saveedit for all the fields , only one transition to the application server to the Database is taken place.

In Field edit for each field change, a transition to the application server to the database is taken place. In Saveedit for all the fields , only one transition to the application server to the Database is taken place.

Think-time functions suspend PROCESSING either until the user has taken some action (such as clicking a BUTTON in a MESSAGE BOX), or until an external PROCESS has run to completion.

Think-time functions suspend processing either until the user has taken some action (such as clicking a button in a message box), or until an external process has run to completion.

• Field edit
• SAVE edit
• Search save
• ROW DELETE
• row INSERT

• %MODE
  Returns A—for ADD mode.
  Returns U — for UPDATE mode

 SQLEXEC is used to execute the SQL statements(SELECT,INSERT,update,delete). We can GET only one row at a TIME.

 SQLEXEC is used to execute the sql statements(select,insert,update,delete). We can get only one row at a time.

Component BUFFER CONTAINS all the data of the ACTIVE component. Data buffer contains the data other than the data in the component buffer (Data of other records)

Component buffer contains all the data of the active component. Data buffer contains the data other than the data in the component buffer (Data of other records)

• Rowset
• ROW
• Record
• Field
• ARRAY
• File
• Sql
• CHART
• grid and so on.

• If default MODE for COMPONENT is search mode: only searchinit will fired.
• If default mode for component is NEW mode :FIELD default, field formula, rowinit, searchinit.

• System variables and USER DEFINED variables.
• SCOPE
• GLOBAL
• COMPONENT
• Local

• In default PROCESSING, any BLANK fields in the component are SET to their default value.
• You can specify the default value either in the Record Field Properties, or in FieldDefault PEOPLECODE

• FIELD default specifies only the default value for a field when we are in ADD mode.
• ROW init FIRES only when a row of data coming from database to component BUFFER

• Saveprechange—last event that executes before UPDATING the data from COMPONENT buffer to the database.
• Savepostchange –fires after the updation of data in the database.
• SQLEXEC — FUNCTION DIRECTLY interacts with the database.

• Getlevel0()— used to get the rowset of the level0.
• %subrec — is used only in Dynamic View SQL where it expands to the columns of a subrecord:
• %selectall–%SelectAll is SHORTHAND for SELECTING all fields in the specified RECORD, wrapping date/time fields with %DateOut, %TimeOut.

• An array is a collection of data storage LOCATIONS, each of which holds the same type of data.
• The maximum depth of a PEOPLECODE array is 15 dimensions.
• Push and unshift are the functions of the array used to add the elements into the array ONE from the END of the array and one from the beginning. Pop is a function of array used to select and delete an ELEMENT from the end of the array.

• GETROWSET –is used to get ROWSET for a record in the component buffer.
• Createrowset—is used to CREATE rowset for a record which in database, and is also called a STANDALONE rowset

USING Dosave and Dosavenow FUNCTIONS.

Using Dosave and Dosavenow functions.

POSTPONES some USER actions to reduce the number of trips to the database so that INCREASES the performance (in SYSTEM edits, field edit, and field change).

Advantages:

• Reduces the network traffic.
• Increases the performance.

Postpones some user actions to reduce the number of trips to the database so that increases the performance (in system edits, field edit, and field change).

Advantages:

Adddropdownitem() Deletedropdownitem()

Adddropdownitem() Deletedropdownitem()

&Rs.Select or Scrollselect()

&Rs.Select or Scrollselect()

Primary permission list is USED for MASS change and DEFINITION SECURITY purposes.

Primary permission list is used for mass change and definition security purposes.

To GIVE access to the RECORDS that are to be used in QUERY, we have create a new query security tree and add the records which we want to give the access and then ASSIGN a access group to the tree. After that we have to add that query tree and query access group to the permission list.

To give access to the records that are to be used in query, we have create a new query security tree and add the records which we want to give the access and then assign a access group to the tree. After that we have to add that query tree and query access group to the permission list.

• The user should have the PERMISSION to update the object. This is given by the Definition security.
• The GROUP, which HOLDS the object, should be added to the permission list of the user in update mode.

• Structure & CONTENT
• MENU IMPORT
• Register COMPONENT

• A SUB PAGE is utilized where you want to display or capture similar INFORMATION for various entities,
  for example, capturing an address, for a company or for a person, would need similar information like Street address,State county, COUNTRY,Pincode etc.. In those situations a sub page would be used, to design once and REUSE at multiple places.

• A Secondary Page is used to display or capture secondary information about an entity.A secondary page could use various sub pages, but the reverse is not true.

USING SQLExec FUNCTION

SQLExec (“SELECT EMPLID,NAME FROM PS_PERSONAL_DATA”, &Emplid, &Name);

Using SQLExec Function

SQLExec (“SELECT EMPLID,NAME FROM PS_PERSONAL_DATA”, &Emplid, &Name);

• An array is a collection of data storage locations, each of which holds the same type of data.
• The maximum depth of a PeopleCode array is 15 dimensions.
• Push and UnShift are the FUNCTIONS of the array used to add the ELEMENTS into the array one from the END of the array and one from the BEGINNING.
• Pop is a function of array used to select and delete an element from the end of the array.

• SqlExec MEANS it bypasses the component buffer and it is directly contacts DATABASE to retrieve data.
• But it RETRIEVES the data row by row and not POSSIBLE for bulk insert.
• But in the CASE of Create SQL we can able insert the data in bulk.

MetaStrings are special TYPE of SQL expressions preceded by % sign.

MetaStrings are used in the following:

• SQLExec
• In application designer to build dynamic views
• With rowset object methods (select, fill)
• SQL OBJECTS
• Record class methods (Insert, Update)
• Application Engine
• Cobol
• Scroll BUFFER functions (ScrollSelect and its RELATIVES).
• Some Record class methods (Insert, Update, and so on.

MetaStrings are special type of SQL expressions preceded by % sign.

MetaStrings are used in the following:

• Record GROUP consists of RECORDS with similar functionality.
• To setup a record in record group we should enter a set CONTROL field value in record PROPERTIES.

Search VIEWS are USED for THREE main reasons.

• Adding CRITERIA to the search dialogue page
• Providing row level security
• Implementing search page processing

Search views are used for three main reasons.

This RECORD field property is USED to UPDATE the DATE field of particular record with the server’s current date and time whenever a user creates or updates a row. Even the user enter the DATA into that field, the data which the user enters will be updated by the system’s current date and time.

This record field property is used to update the date field of particular record with the server’s current date and time whenever a user creates or updates a row. Even the user enter the data into that field, the data which the user enters will be updated by the system’s current date and time.

• SetId is the highest level key in the PeopleSoft. Location, Department and Jobcode TABLES are control tables and setid’s control the control tables during the transaction.
• Table set sharing is a PLACE where control tables are listed. It is accessed by business unit.

EX: If we have two locations Arizona and OHIO with setid’s xyz and abc,
suppose if we change Ohio’s setid to xyz then we can access all INFORMATION related to Arizona/xyz like jobcodes etc.

EX: If we have two locations Arizona and Ohio with setid’s xyz and abc,
suppose if we change Ohio’s setid to xyz then we can access all information related to Arizona/xyz like jobcodes etc.

• A class is the formal definition of an object and acts as a TEMPLATE from which an instance of an object is created at runtime.
• The class defines the properties of the object and the METHODS used to control the object’s behavior.
• PeopleSoft delivers predefined CLASSES (such as Array, File, Field, SQL, and so on).
• You can create your own classes USING the APPLICATION class. You can also extend the functionality of the existing classes using the Application class.