Sending Item Information to PeopleSoft CRM
If you are integrating with PeopleSoft CRM, you can use the CRM Item Sync EIPs to synchronize item data in the CRM and PeopleSoft Inventory systems. The CRM Item Sync EIPs are two service operations defined in PeopleSoft Integration Broker, ITEM_CRM_FULLSYNC_EFF and ITEM_CRM_SYNC_EFF. Use the ITEM_CRM_FULLSYNC_EFF service operation to send a list of all items in the PeopleSoft Inventory Item Master table to CRM. The PeopleSoft CRM FieldService and Call Center applications use this item information for initial population of their Item Master tables. Use the ITEM_CRM_SYNC_EFF service operation to send incremental updates automatically as item information is modified online or by the Item Loader process (IN_ITMLOAD). When you use the ITEM_CRM_SYNC_EFF service operation, you must also activate the internal ITEM_CRM_SYNC service operation. This service operation does not send data to the PeopleSoft CRM system, but it is essential for ITEM_CRM_SYNC_EFF to work properly.
When you activate the ITEM_CRM_SYNC and ITEM_CRM_SYNC_EFF service operations, outbound item information is generated from these five points within the PeopleSoft system as approved items are being maintained:
-
Define Item component.
-
Approve Item component.
-
Units of Measure component.
-
Copy Item component.
-
Item Loader process (IN_ITMLOAD).
-
Item Add component.
See PeopleSoft Supply Chain Management Integration: PeopleSoft SCM Outbound EIPs.
See PeopleSoft CRM Integrated FieldService
See PeopleSoft CRM Call Center
Setting Up the CRM Item Sync EIPs
PeopleSoft delivers the service operations in PeopleSoft Integration Broker with a default status of Inactive. You must activate each service operation before attempting to send or receive data from a third-party source or another PeopleSoft system, such as CRM. To set up this service operation:
-
Setup within the PeopleSoft Inventory application:
There are no setup steps within PeopleSoft Inventory.
-
Setup within PeopleSoft Integration Broker and Enterprise Components:
PeopleSoft Supply Chain Management Integration: Setting Up Service Operations.
| Service Operation | Direction and Type | Handlers | Chunking Available? | Integrates With |
|---|---|---|---|---|
|
ITEM_CRM_FULLSYNC_EFF |
Outbound Asynchronous |
No |
CRM |
|
|
ITEM_CRM_SYNC_EFF |
Outbound Asynchronous |
No |
CRM |
|
|
ITEM_CRM_SYNC |
Local Asynchronous |
ItemCRMSyncEff |
No |
CRM |
See PeopleSoft Supply Chain Management Integration: Setting Up Service Operations.
See PeopleTools: PeopleSoft Integration Broker
Message Structure
Each service operation uses a message to define the fields and records to be used in the EIP. The structure of this item messages is:
| Segment | Parent | Valid Relationships |
|---|---|---|
|
Item Master |
(None) |
|
|
Item Detail |
Item Master |
1:1 on effective-dated messages or both 1:1 and 1:many on messages that are not effective-dated. |
|
Item Substitute |
Item Master |
1:0, 1:1, or 1:many. |
|
Item UOM |
Item Master |
1:1 or 1:many. |
|
UOM Type |
Item UOM |
1:1 or 1:many. |
Message Segments
The segments that are delivered in each of these item messages varies depending on the source of the message. The tables that are provided under each of the data sources that are listed display the segments that are delivered based on the function that is being performed.
-
The parent segment of the message is always included on the EIP transaction.
If the parent segment does not have a PSCAMA record, or if it does have a PSCAMA record with a blank audit action code, then no modifications were made to the parent segment. In this case, the parent is included only for reference purposes.
-
The EIP transaction is published if any fields for a source record are altered on any of the pages that are listed.
The audit action code on the PSCAMA record is set to the appropriate code based on the action that is being performed. Because all fields on the source records are not sent on the transaction, cases might exist where data is published even though none of the fields have been modified. The logic that determines whether to publish an EIP transaction only checks that the source record has been altered. It does not check field by field to determine whether the altered fields are on the message used by the EIP transaction.
-
Because the logic that publishes the transaction does not check field by field to determine whether a specific field has been altered, all fields that are on a message segment are published if any field on the source record is altered.
-
The item EIP transactions are published only for an item that has an Approved status.
Define Item
The Define Item component sends out various segments of the item message depending on the function that is being performed.
-
Add mode with a status of Approved:
Segment Audit Action Comments and Data Rules Item Master
A
Always published.
Item Detail
A
Always published.
Item UOM
A
Always published.
UOM Type
A
Always published.
Item Substitute
A
Published only if any exist.
-
Update or Correction mode with an item that is saved with a new Approved status. Because an item EIP transaction is never published until it is approved, all message segments for the item are used when approved:
Segment Audit Action Comments and Data Rules Item Master
A
Always published.
Item Detail
A
Always published.
Item UOM
A
Always published.
UOM Type
A
Always published.
Item Substitute
A
Published only if any exist.
-
Update or Correction mode with an item that was previously approved:
Segment Audit Action Comments and Data Rules Item Master
C or space
Always published.
Item Detail
C, D, or space
Published only if a field from the Inventory Item table (ITEM_INV) is modified.
Item Substitute
C, D
Published only if a field from the Item Substitute table (SUBSTITUTE_ITM) is modified.
Item UOM Page
The Item UOM page provides these message segments:
| Segment | Audit Action | Comments and Data Rules |
|---|---|---|
|
Item Master |
Space |
Always published. |
|
Item UOM |
A, C, or D |
Always published. |
|
UOM Type |
A, C, or D |
Always published. |
Item Approval Page
Because an item EIP transaction is never published until it is approved, all message segments for the item are used when approved:
| Segment | Audit Action | Comments and Data Rules |
|---|---|---|
|
Item Master |
A |
Always published. |
|
Item Detail |
A |
Always published. |
|
Item UOM |
A |
Always published. |
|
UOM Type |
A |
Always published. |
|
Item Substitute |
A |
Published only if any exist. |
Item Copy Page
The Item Copy page provides these message segments:
| Segment | Audit Action | Comments and Data Rules |
|---|---|---|
|
Item Master |
A or space |
Always published. |
|
Item Detail |
A |
Published only if this segment is copied. |
|
Item UOM |
A |
Published only if this segment is copied. |
|
UOM Type |
A |
Published only if this segment is copied. |
|
Item Substitute |
A |
Published only if any exist. |
Item Loader Process
The Item Loader process provides different message segments depending on the action that is being taken with the item:
When adding a new item in an Approved status:
| Segment | Audit Action | Comments and Data Rules |
|---|---|---|
|
Item Master |
A |
Always published. |
|
Item Detail |
A |
Always published. |
|
Item UOM |
A |
Always published. |
|
UOM Type |
A |
Always published. |
When updating an existing item that has reached an Approved status:
| Segment | Audit Action | Comments and Data Rules |
|---|---|---|
|
Item Master |
C or space |
Always published. |
|
Item Detail |
C or space |
Published only if altered on inbound message. |
|
Item UOM |
A, C, or space |
Published only if altered on inbound message. |
Full Data Publish
This function is used to copy all items in the database to an interfacing system, or if chunking is being used, to copy all items for a specific chunking value. In this case, all transactions are published with an audit action code of A:
| Segment | Audit Action | Comments and Data Rules |
|---|---|---|
|
Item Master |
A |
Always published. |
|
Item Detail |
A |
Always published. |
|
Item UOM |
A |
Always published. |
|
UOM Type |
A |
Always published. |