Tuesday, May 25, 2010

people soft Components Interview Questions,faq's,tutorial

RE: Which of the following is NOT TRUE in Component In...
--------------------------------------------------------------------------------

The Component Interface can be mapped to only 1 component.

But There can be multiple component Interfacses for 1 Component



--------------------------------------------------------------------------------
RE: Which of the following is NOT TRUE in Component In...
--------------------------------------------------------------------------------

A component interface can be mapped to only one component.

The Component Interface can be mapped to only 1 component.

But There can be multiple component Interfacses for 1 Component

Which of the following is NOT TRUE in Component Interface (CI) Architecture?
A component interface can be mapped to multiple PeopleSoft components

The main attributes of a Component Interface (CI) are?
Keys, Properties & Collections, Methods and Name

The main attributes of CI are

1. Component Interface Name

2. Keys like Get keys, Find Keys and Create Keys.

Get Keys:- All the Search keys of a Componant (Record) will become Get Keys of CI

Find Keys:- All search Keys and Alt Search Keys

Create Keys: If the underlying Componant is in add mode then Create keys will be automaticall created.

3. Methods - There are 5 Standard Methods r there in CI like Find, Get, Save, Cancel and Create.

4.Properties and Collections ( Fields and Records).

i hope this will help u.

Thanks

Jayaram.

RE: The main attributes of a Component Interface (CI) ...
--------------------------------------------------------------------------------

The main attributes of CI are

1. Component Interface Name

2. Keys like Get keys Find Keys and Create Keys.

Get Keys:- All the Search keys of a Componant (Record) will become Get Keys of CI

Find Keys:- All search Keys and Alt Search Keys

Create Keys: If the underlying Componant is in add mode then Create keys will be automaticall created.

3. Methods - There are 5 Standard Methods r there in CI like Find Get Save Cancel and Create.

4.Properties and Collections ( Fields and Records).

i hope this will help u.

Thanks

Jayaram.



--------------------------------------------------------------------------------
RE: The main attributes of a Component Interface (CI) ...
--------------------------------------------------------------------------------

The main attributes of CI are1. Component Interface Name2. Keys like Get keys Find Keys and Create Keys.3.Methods-There are 5 standard methods in CI like Create Cancel Find Search Save4.Properties and Collections ( Fields and Records).

q:Which of the following are TRUE when a Component Interface (CI) is created on component that has Add?action enabled?

ans:Get keys, Create keys and Find keys gets created automaticallyThe Create method is created alongwith the other Standard methods for the CI

RE: Which of the following are TRUE when a Component I...
--------------------------------------------------------------------------------

The create method will not be present if the Add mode for the Component is not enabled. This is the one thing that is true when a CI is created for a Add mode component.

Which one of the following are standard properties when a Component Interface (CI) is created?
GetHistoryItems

RE: Which one of the following are standard properties...
--------------------------------------------------------------------------------

InteractiveMode GetHistoryItems and EditHistoryItems

With reference to the Component Interface Tester which of the following is NOT TRUE
GetExisting option is equivalent to opening a record in Update/Display Mode only

The following are various steps that describes the peoplecode logic while implementing a Component Interface?
1.Establish a user session
2.Get the Component Interface
3.populate the Create Keys
4.ceate an Instance of the CI
5.populate the required fields
6. Save the CI

Which of the following can be mapped as Find Keys for a Component Interface?
A OR b

Search key and alternate search key

Which plan order created manually and rest from schedule order?

How to do object security?How to connect report through process scheduler?

Object Security - Object Security is used to restrict the PeopleTools objects that specific developers can access.

=======================

PS8.0, PT8.15.

Application designer - Go - PeopleTools - Object Security.

Create a Group Id - Select type of object - The windows will be splitted into two boxes. Then move the objects, to which access has to be given to the developer/s, into the left side of window. Save the Group Id.

Now link the Group Id to the permission list which is attached to the developer userid.



--------------------------------------------------------------------------------
RE: how to do object security?how to connect rep...
--------------------------------------------------------------------------------

To connect a report first we have to know about run control page. So that we can add the required fields over there and then passing those oprid and runctlid through the stdapi.sqc we can run an an SQR by including this SQC. This can be runned through the process sheduler. If directly we can go to the process sheduler request and made a request for the SQR. This happens only when the report repositry and distubution has been set properly. After making request we can run the process sheduler

--------------------------------------------------------------------------------
RE: how to do object security?how to connect rep...
--------------------------------------------------------------------------------

Object Security - Object Security is used to restrict the PeopleTools objects that specific developers can access.


PS8.0 PT8.15.

Application designer - Go - PeopleTools - Object Security.

Create a Group Id - Select type of object - The windows will be splitted into two boxes. Then move the objects to which access has to be given to the developer/s into the left side of window. Save the Group Id.

Now link the Group Id to the permission list which is attached to the developer userid.


If you are PS developer then In what scenarios Component Interface will have advantages over component?




--------------------------------------------------------------------------------
difference between Component and component interface
--------------------------------------------------------------------------------

A component exposes your pages to peoplesoft only.Moreover it helps us to define common properties for a set of related pages.

A component interface is a set of application programming interfaces (APIs) that you can use to access and modify PeopleSoft database information programmatically. PeopleSoft Component Interfaces expose a PeopleSoft component (a set of pages grouped for a business purpose) for synchronous access from another application (PeopleCode Java C/C++ or Component Object Model [COM]).


RE: If you are PS developer then In what scenarios Component Interface will have advantages over component?
--------------------------------------------------------------------------------

In case where you have large amount of data entries or a repeatable amount of entries over time that could be scheduled.



--------------------------------------------------------------------------------
RE: What is component Interface meant for?
--------------------------------------------------------------------------------

It is an integration tool which is used to integrate peoplesoft component from one application to another application.The application can be another peoplesoft application or third party application (c/c++ java).


--------------------------------------------------------------------------------
What is component Interface meant for?
--------------------------------------------------------------------------------

Component Interface is the major aspect of a component .Its a PeopleTool is useful for synchronous access from other application like Java C++ COM etc.It integrate another Component Interface of external system.


--------------------------------------------------------------------------------
RE: What is component Interface meant for?
--------------------------------------------------------------------------------

Component Interface exposes Data and Business logic of a business process to internal/external applications through PeopleSoft API/Java/C++/VB


--------------------------------------------------------------------------------
RE: Difference between search record and add search re...
--------------------------------------------------------------------------------

according to me

search record and add searchrecord functionalities are same but add searchrecord with add mode


--------------------------------------------------------------------------------
RE: Difference between search record and add search re...
--------------------------------------------------------------------------------

When we mention a record name in the search record option in the component properties then the searching will take place from that record when the component search page appears. When we add a new value in the add mode the record name that we specify in the add search record option the new value gets stored there. By default if we don’t mention any value in the add search record option then the new value will be stored in the table mentioned in the search record option.

RE: Difference between search record and add search record?
--------------------------------------------------------------------------------

Search record is used to select the record which is resposible for runtime search page.

Add search record is used to add one more search record it is used when the primary record is different from search recoed.

RE: Difference between search record and add search record?
--------------------------------------------------------------------------------

Search record : These records are used as qualifying entries so that the correct entry or correction is made into the record displayed in the panels / Pages.

Add search record: It is a field that defines the Search record for the Add action.

RE: Difference between search record and add search record?
--------------------------------------------------------------------------------

Search record : These records are used as qualifying entries so that the correct entry or correction is made into the record displayed in the panels / Pages.

Add search record: It is a field that defines the Search record for the Add action.


RE: What is Recordgroup in peoplsoft?
--------------------------------------------------------------------------------

Record group in pplsoft is a logical group of functionally related tables and views which enable tableset sharing

RE: What is Recordgroup in peoplsoft?
--------------------------------------------------------------------------------

A Record Group is a group of related records keyed by SetID which define the valid values for one or more fields in PeopleSoft. Related values are keyed with/under a single Record Group.

For example Record Group FS_02 defines edit tables related to Calendars. Record Group FS_26 defines edit tables related to Locations. Record Group AR_02 defines edit tables related to the Accounts Receivable Aging.

The structure of Record Groups is core to the feature of PeopleSoft known as TableSet sharing. Record Groups support sharing one set of valid values across multiple Business Units.

All Business Units in PeopleSoft Financials must have a completely defined TableSet of valid values. To support this Business Units are often defined with reference to a default SetID. The SetID value is then the key used to access the complete set of valid values know as a Table Set.

Within a TableSet each Record Group must reference one and only one SetID. Values specific to a Business Unit are keyed by a SetID referenced only by that Business Unit - sometimes the actual BU is used as the key/SetID value. Values shared with one or more Business Units are typically keyed by a more generic SetID - perhaps representative of a market or geographic segment. Finally values shared across all Business Units are usually keyed by a generic SetID - sometimes SHARE or MODEL.



I may need to integrate my .asp based website with several People Soft modules (People Soft HCM, Financial Interface). Essentially, I just need to exchange information to keep account records in sync. This will ultimately involve passing XML files back and forth, parsing them and processing the appropriate requests.

The most likely options are:

Option1: Build something on the People Soft side of things
We could build an application within the People Soft network that uses the People Tools to receive and process the requests. The customer already "owns" People Tools. Would there be any other licensing fees that I need to worry about.

Option 2: We build something on our servers to access the People Soft server
I'm quite sure that the customer is not going to allow any outside access to their People soft database, however, if they did, what tools/packages would I need to use/purchase in order to facilitate this access (we'd be using ASP/COM or .NET development tools). We do not own Peoplesoft. WE'd be a 3rd party developer in this equation.

Sorry if these are incredibly simplistic questions. I know nothing about Peoplesoft. It just sounds really, really expensive and I have to believe all of these little development options and API's each have their own $$$ tied to them and I want to make sure I cover all of our costs.

RE: I may need to integrate my .asp based website with...
--------------------------------------------------------------------------------

Which version of PeopleTools are you using?

PeopleTools has several built-in features that you can use to do such kind of integrations.

It would also help if you can let us know what you want to integrate who is going to be the publisher who is subscriber what kind of processing is required etc.

I would then be able to help you in this.

How to insert and update rows into a record using Application Engine and Component Interface?

There are many ways to insert and update rows into a record either using Application Engine or Component Interfaces.
In Application Engine programe, using peopelecode we can create a standalone rowset with the record to be updated. Fill the rowset using rowset.fill method. Manipulate the data and use record.Save() method.

In Component Interfaces, if the record is in the CI buffer. If the data is populated in the buffer, the CI Save method will update or insert the data in the record.

How do we maintain Consistancy between Components and CI?
A CI is called in Save-prechange with Currently active component buffer datas. the called CI gets saved successfully. but the component from which CI called gets errored in Save-postchange. How do we maintain consistancy between two components.

RE: How do we maintain Consistancy between Components and CI?
--------------------------------------------------------------------------------

We need not maintain any consistency between CI and Component unless we miss the procedures in creating and updating the CI.
The save failed means validations were not through. Analyse and rectify issues with data as per business need.
As save failed at save post change no commit will be issued for transaction and so everything gets roll backed.
Post a Comment

Receive All Free Updates Via Facebook.