Using Enterprise Integration Points for Items

Message Structure

Each service operation uses a message to define the fields and records to be used in the EIP. The structure of the item messages is:

Message Segments

The segments that are delivered in each of the item messages vary depending on the source of the message. The tables that are provided under each of the data sources 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 are 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 (add, change, or delete). Because all fields of the source record are not sent on the EIP transaction, cases may exist in which transactions are published even though none of the fields have been modified. The logic that determines whether to publish a 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 that is on the source record is altered.

• The item EIP transactions are published only for an item that has an Approved status.

Define Item

The component sends out various segments of a 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.

• 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.
  Item Purchasing Attributes	A	Published only if any exist.
  Item Bus Unit Attributes	A	Published only if any exist.
  Item Bus Unit Wgt/Vol	A	Published only if any exist.
  Item Revision	A	Published only if any exist.
  Item Category	A	Published only if any exist.
  Item Manufacturer	A	Published only if any exist.
  Universal Item Identifier	A	Published only if any exist.

• Update or Correction mode with a previously approved item:

  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 UOM Page

The Item UOM page provides these message segments:

Universal Item Identifiers Page

The Universal Item Identifiers page provides these message segments:

Purchasing Attributes Page

The Purchasing Attributes page provides these message segments:

Define Business Unit Item Page

You can use Add or Update mode.

• Add mode: When the page is saved in Add mode, all message segments for the Item EIP are published with an Audit Action Code of A.

  Interfacing systems that are only taking a transaction when the item is added to the business unit use this message to build all information for the item.

  Interfacing systems that take transactions before a business unit is established update their item structures with the business unit level information:

  Segment	Audit Action	Comments and Data Rules
  Item Master	A	Always published.
  Item Detail	A	Always published.
  Item UOM	A	Always published.
  Item Purchasing Attributes	A	Published only if it exists.
  Item Bus Unit Attributes	A	Only the business unit that is being added is published. In this situation, the relationship between the Item Master segment and the Item Bus Unit Attributes segment is always a one-to-one relationship.
  Item Bus Unit Wgt/Vol	A	Published only if any exist.

• Update mode:

  Segment	Audit Action	Comments and Data Rules
  Item Master	Space	Always published.
  Item Bus Unit Attributes	C or space	Only the business unit that is being changed is published. In this situation, the relationship between the Item Master segment and the Item Bus Unit Attributes segment is always a one–to-one relationship.
  Item Bus Unit Wgt/Vol	A, C, or D	Only published if the BU_ITEMS_WTVOL is modified.

Item Approval Page

Because the item EIP is never published until an item is approved, all segments for the item are published when it is approved:

Item Copy Page

The Item Copy page provides these message segments:

REV Maintenance

The REV Maintenance page provides these message segments:

BOM Mass Maintenance by MMC and BOM Mass Maintenance by ECO

The BOM Mass Maintenance pages provide these message segments:

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 with an Approved status:

When updating an existing item that has reached an Approved status:

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 data is published with an audit action code of A:

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:

1. Setup within the PeopleSoft Inventory application:

   There are no setup steps within PeopleSoft Inventory.

2. Setup within PeopleSoft Integration Broker and Enterprise Components:

   Setting Up Service Operations.

See 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:

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:

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:

Item Copy Page

The Item Copy page provides these message segments:

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:

When updating an existing item that has reached an Approved status:

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: