Bookshelf Home | Contents | Index | Search | PDF

Siebel Connector for PeopleSoft > Prebuilt Integration Objects > Overview >

List of Values (LOV) Bounded Fields

---

Some fields in the Siebel business components take values from a predefined List of Values (LOV). The fields in the integration components that are based on such fields can take values from only that list. So, it is important that these lists of values be appropriately mapped.

For example, the field Account Status in the Account integration component of EAI Account integration object depends on a predefined list of values. This can be seen in Figure 16.

Figure 16. LOV Bounded Fields

As you can see from the Account business component, shown in Figure 17, the field Account Status gets its values from a picklist named PickList Account Status.

Figure 17. Account Status Values

If you look into the properties of PickList Account Status, you will notice that it has LOV type ACCOUNT_STATUS. You can see this in Figure 18.

Figure 18. List of Values

And finally, if you query the list of values for that particular type, all the possible values that can go into the Account Status field as the Language Independent Code are displayed. Here, you can input only the above five values (Active, Contract Pending, Inactive, Marked For Deletion, and Prospect) in the Account Status field.

Note that the prebuilt Integration Objects utilize the AllLangIndependentVals user property. The Siebel Adapter expects the language independent code to be specified in LOV bounded fields. If additional values are needed, they should be added to the List of Values. If the names in the external system are different but the meaning is the same, appropriate mapping should be done possibly using the EAI Value Mapping feature.

Bookshelf Home | Contents | Index | Search | PDF