Setting Up the CRM Process Integration Packs Admin Utility

This chapter provides an overview of the CRM Process Integration Packs Admin utility and discusses how to:

Sign in to CRM Process Integration Packs.
Configure CRM Process Integration Packs Admin.
Diagnose object document and cross-reference values.
Set up domain value maps.
Configure initial ID cross-references.
Manage initial ID cross-reference services.

Understanding CRM Process Integration Packs Admin

The CRM Process Integration Packs Admin (CRM PIP Admin) utility is used to configure parameters such as domain value maps and ID cross-references. It creates the cross-reference keys for storing such references. The cross-reference information is maintained in the database.

The ID cross-reference service generates and maintains a common reference ID for a business object in relation to all participating applications.

The domain value mapping service receives the Open Application Group (OAG) document and searches the CRM Process Integration Packs repository to obtain the list of values to transform within the OAG document. This is required when the two applications use different values to represent the same information for a given field.

Signing In to CRM Process Integration Packs

To sign into CRM Process Integration Packs, use the CRM Process Integration Packs username and password assigned to you on the PeopleSoft sign-in page.

You access CRM Process Integration Packs modules just like you access PeopleSoft CRM applications and business processes.

Configuring the CRM Process Integration Packs Admin

You use the CRM PIP Admin utility to configure parameters such as domain value maps and initial ID cross-references. To manage the portal structure and content, you need portal administration rights for folder management and content reference management.

Diagnosing Canonical Object Document and Object Cross-Reference Values

Canonical Object Document data maintains the original and external reference paths in the XML for the business objects. When the object value is propagated from source to target, before Extensible Stylesheet Language (XSL) transformation to target native XML format, the system checks for the reference path and retrieves the field value to be incorporated in the target.

The object cross-reference option enables you to modify the cross-references generated for the business objects by the ID cross-reference service.

Note. Using the PIP Diagnosis options, records can only be updated and not deleted.

Pages Used to Diagnose Object Document and Cross-Reference Values

Page Name	Object Name	Navigation	Usage
Canonical Object Document Key Values	DOCKEYDISP	Set Up CRM, Common Definitions, Integration Rules, CRM PIP Admin, PIP Diagnosis, Canonical Object Document	View the canonical object document key values.
Cross-Reference Values	DISPCOMP	Set Up CRM, Common Definitions, Integration Rules, CRM PIP Admin, PIP Diagnosis, Object Cross-Reference	View the cross-reference values inserted for the business objects for each participating application.

Viewing the Cross-Reference Values

Access the Cross Reference Values page.

The field values displayed are:

Cross Reference ID	The ID for the cross-reference value generated. This value is incremented for each master and sub object in each participating application.
Cross Reference Key	The cross-reference key value, which is the same for a master object in all participating applications. The cross-reference key value for the sales order master object will be the same in all participating applications.
Application Instance ID	The instance of the participating application for which the cross-reference key was generated. A separate row is added in the cross-reference tables for each participating application.
Master Object	The master object for which the cross-reference key was generated. For example, it could be sales orders, item master, party, and so on.
Master Object ID	The corresponding reference value for the master object in each application.
Sub Object	The sub object for which the cross-reference key was generated. For example, it could be sales order line, item, address, and so on.
Sub Object ID	The reference value for the sub object corresponding to the master object in each application.
Modify	Click to modify the generated cross-reference values.

Note. The cross reference ID and cross reference key values cannot be modified.

Setting Up Domain Value Maps

This section provides an overview of domain value maps and lists pages used to set up domain value maps.

Understanding Domain Value Maps

During integration, you transform field values from the source application according to the requirements of the target application. The domain value mapping service receives an OAG document and searches the CRM Process Integration Packs repository to obtain a list of values to transform.

You apply domain value maps to a message before it reaches the target application. Domain value maps are stored in the Domain Value Mapping table (ANET_IS_DVM) in the database.

For example, the country field attribute value in the source application might be USA and in the target application, the attribute value might be US.

Pages Used to Set Up Domain Value Maps

Page Name	Object Name	Navigation	Usage
Domain Value Maps	ANET_DVM_COMP	Set Up CRM, Common Definitions, Integration Rules, CRM PIP Admin, Domain Value Maps, Domain Value Maps	Add domain value maps.

Adding Domain Value Maps

Access the Domain Value Maps page.

The field values displayed are:

Touch Point ID	The touch point ID for which the domain value mapping is applicable.
Attribute	The XML path where the source application field value is replaced by the target application field value.
Source Application	The source application whose business object field value is to be replaced.
Source Instance	The source application instance.
Source Value	The value for the business object in the source application. For example, the alternative unit of measure value could be B15 in PeopleSoft and BG in SAP.
Target Application	The target application whose corresponding business object field value is replaced.
Target Instance	The target application instance.
Target Value	The value for the business object in the target application.
Enabled	Select this check box to enable the domain value map.

Configuring Initial ID Cross-References

This section provides an overview of initial ID cross-references and lists pages used to configure initial ID cross-references.

Understanding Initial ID Cross-References

Use these pages to enter values for instance and organization. These values are required to configure the ID cross-reference service and generate cross-reference keys for business objects.

The update customer and item data options are used to receive corresponding table fields from Oracle or SAP as a flat file to PeopleSoft CRM during initial synchronization.

Pages Used to Configure Initial ID Cross-References

Page Name	Object Name	Navigation	Usage
Configure Application Instance	CONFIG_INSTANCE	Set Up CRM, Common Definitions, Integration Rules, CRM PIP Admin, Configure Initial ID Cross-Reference, Instance	Add an application instance.
Configure Organization	CONFIG_ORG	Set Up CRM, Common Definitions, Integration Rules, CRM PIP Admin, Configure Initial ID Cross-Reference, Organization	Add an organization.
Upload Customer Data	CUSTOMERUPLOAD	Set Up CRM, Common Definitions, Integration Rules, CRM PIP Admin, Configure Initial ID Cross-Reference, Upload Customer Data	Update customer data.
Upload Item Data	ITEMUPLOAD	Set Up CRM, Common Definitions, Integration Rules, CRM PIP Admin, Configure Initial ID Cross-Reference, Upload Item Data	Update item data.

Uploading Customer Data

Access the Upload Customer Data page.

To upload customer data:

Select Add a New Value.
Enter the run control ID.
Select the application from which the customer data is uploaded.
Select the application instance from which data is uploaded.
Enter the name and path of the file that will contain the customer data.
Click Save.

Uploading Item Data

Access the Upload Item Data page.

To upload item data:

Select Add a New Value.
Enter the run control ID.
Select the application from which the item data is uploaded to PeopleSoft CRM.
Select the application instance from which data is uploaded.
Enter the name of the file that will contain the item data.
Click Save.

Managing Initial ID Cross-References

This section provides an overview of initial ID cross-reference services and lists pages used to manage initial ID cross-reference services.

Understanding Initial ID Cross-Reference Services

The object ID cross-reference service stores the reference of the same business object in each participating application. It creates cross-reference keys for storing such references. The cross-reference information is maintained in the database.

The ID cross-reference service searches the repository to find the list of keys to map for the OAG document. New records are inserted for primary keys at each level in the OAG document.

Multiple cross-references might be required for a single OAG document. For example, a customer object might contain address information along with customer information. In this case, two records are inserted for each of the participating applications, one for the customer ID and one for the address ID.

For updates, the cross-reference key and the subobject key in the target application are retrieved and substituted in the external reference and original reference tags.

The list of the attributes that require cross-referencing is prepopulated in the CRM Process Integration Packs repository through SQL scripts. Using these values, the ID cross-reference service identifies the attributes in the business object document and generates the cross-reference keys.

Assumptions and Dependencies for Customer Cross-References

When referencing customer business objects, the following assumptions are made:

Data is available at the PeopleSoft database level.
The PeopleSoft setID is mapped to the SAP sales area or the Oracle organization code.
The PeopleSoft customer name is equal to the SAP customer name or the Oracle customer name.
Customers are propagated to SAP or Oracle from PeopleSoft separately (that is, PeopleSoft to SAP or PeopleSoft to Oracle).

Assumptions and Dependencies for Item Cross-References

When referencing item business objects, the following assumptions are made:

Data is available at the PeopleSoft database level.
The PeopleSoft setID is mapped to the SAP sales area or Oracle organization code.
The PeopleSoft inventory item ID is equal to the SAP material number or Oracle Segment1.
Items are propagated to PeopleSoft from SAP or Oracle separately (that is, SAP to PeopleSoft or Oracle to PeopleSoft).

Batch Processing

When you generate cross-reference keys using the batch process, the process can be scheduled to use the system resources effectively. After completion, a report in a specified format is generated for diagnostic purposes. Unsuccessful processes can be resumed through the online process, or another batch process can be initiated. This process is effective for large volumes of data.

Single Item Processing

This process generates cross-reference keys instantly. Use this process for small volumes of data.

Pages Used to Manage Initial ID Cross-References

Page Name	Object Name	Navigation	Usage
Customer ID Cross Reference	CUSTIDCR	Set Up CRM, Common Definitions, Integration Rules, CRM PIP Admin, Initial ID Cross-Reference, Customer Master (Batch)	Set the batch process run for customer data.
ID Cross-Reference	ITEMIDCR	Set Up CRM, Common Definitions, Integration Rules, CRM PIP Admin, Initial ID Cross-Reference, Item Master (Batch)	Set the batch process run for item data.
IDCR	CUST	Set Up CRM, Common Definitions, Integration Rules, CRM PIP Admin, Initial ID Cross-Reference, Customer Master (Online)	Run the process individually for customer objects.
IDCR	CRRCOMP	Set Up CRM, Common Definitions, Integration Rules, CRM PIP Admin, Initial ID Cross-Reference, Item Master (Online)	Run the process individually for item objects.

Setting the Customer Master Batch Process

Access the Customer ID Cross Reference page.

To set the customer master batch process:

Select Add a New Value.
Enter the process run control ID.
Select the source and target applications whose cross-reference keys are to be mapped.
Select the application instances.
Select the source and target organizations whose cross-references are to be mapped.
Click Save.

Note. Follow the same procedure for the setting the item master batch process.

Setting the Item Master Online Process

Access the ID Cross Reference page.

To set the item master online process:

Select the source and target applications whose cross-reference keys are to be mapped.
Select the application instances.
Select the source and target organizations whose cross-reference keys are to be mapped.
Click the Refresh button to display the values in the source and target. Select the rows in the source and target to be mapped.

When you use the Automap option, you need not refresh and select the source and target rows.
Click the Map button to generate the cross-reference key explicitly.
If you click the Auto Map button, the list of data that can be mapped is displayed. Select the required rows and click IDCR.

Important! If you click the Map button, the system does not check if the item name in the source is equivalent to the item name in the target.

However, if you click the Auto Map button, the cross-reference key is generated only after checking that the source item name is equivalent to the target item name. If no two rows are equivalent, in the Automap tab page no row is displayed in the Mapped data grid.

Follow the same procedure for the customer master online process.