Skip to Main Content
Return to Navigation

Importing Suppliers Using the Supplier EIP

This section provides an overview of the Supplier EIP (VENDOR) and discusses how to:

Understanding the Supplier EIP

The Supplier EIP uses application messaging to publish supplier information from the PeopleSoft Payables and Purchasing supplier tables to PeopleSoft Payroll, PeopleSoft Student Administration, and other external systems, as well as to subscribe to supplier information published by Payroll, Student Administration, and external systems. You can also supply XML files directly to the EIP to create or modify suppliers.

The Supplier EIP uses four application messages to subscribe to and publish data in the supplier tables.

Message Name

Function

VENDOR_SYNC

Incremental publish and subscribe.

VENDOR_FULLSYNC

Full-table publish and subscribe.

VENDOR_SYNC_EFF

Incremental publish of current effective-dated data.

VENDOR_FULLSYNC_EFF

Full-table publish of current effective-dated data.

The incremental messages process individual records, whereas the full-table messages process entire tables. To update tables with new supplier records as they are published, select the incremental subscribe process. To load the entire supplier table, select the full-table subscribe process. To publish records as they are created, use the incremental publish process. To publish the entire supplier table, use the full-table publish process.

Note: The VENDOR_SYNC_EFF message and the VENDOR_FULLSYNC_EFF message should only be used when you publish data to systems that do not support effective dating. These messages publish only the most current supplier record. They do not publish any history or future rows that might exist.

Note: If you change the value in the Classification field on the Supplier Information - Identifying Information page to HRMS, you must initiate the Full Table publish process for the VENDOR_FULLSYNC application message to update the supplier tables in PeopleSoft Payroll.

Note: In addition to delivering the Supplier EIP as application messages, Oracle's PeopleSoft also delivers it as a web service (Supplier). Enabling web services is discussed in the documentation PeopleTools : Integration Broker.

See the product documentation for PeopleTools: PeopleSoft Integration Broker

Using the Incremental Subscribe Process (VENDOR_SYNC)

The Incremental Subscribe process enables you to subscribe to supplier data incrementally as it is published by PeopleSoft Payroll or by external applications.

Design Pattern

Message Name

Subscription Name

PeopleCode Subscribe

VENDOR_SYNC

SupplierSync

Image: Process flow for incremental subscribe suppliersprocess flow diagramsfor incremental subscribe diagrams of:process flow for incremental subscribe

This diagram illustrates the Incremental Subscribe process:

Process flow for incremental subscribe√ā¬†vendorsprocess flow diagramsfor incremental subscribe diagrams of:process flow for incremental subscribe

Incremental Subscription Process for the VENDOR_SYNC Message

The supplier subscription code uses a component interface that encapsulates the supplier online component to handle default values and edits of the supplier data received in the subscribed message:

Declare Function supplier_intfc PeopleCode FUNCLIB_APEIP.VENDOR_ID FieldFormula;
Local Message _amp_ MSG;
_amp_ MSG = GetMessage();
supplier_intfc(_amp_ MSG);

The same default values and validation that occur online occur through the VNDR_ID component interface.

Not all the data elements in the supplier-related records are exposed in the message. The subscription process assigns the unexposed data elements a default value that is consistent with the PeopleSoft record definition.

Using the Incremental Publish Process (VENDOR_SYNC)

The Incremental Publish process enables you to publish supplier data incrementally to external systems.

Design Pattern

Message Name

Page Group Publish

Supplier_sync

Image: Process flow for incremental publish suppliersprocess flow diagrams for incremental publish diagrams of:process flow for incremental message publish

This diagram illustrates the Incremental Publish process:

Process flow for incremental publish vendorsprocess flow diagrams for incremental publish diagrams of:process flow for incremental message publish

Incremental Publication Process for the VENDOR_SYNC Message

The following code calls the message publication code:

VNDR_ID(page group).SavePostChange
Local Message &msg;
Local Rowset &rs0;
&msg = CreateMessage(Message.VENDOR_SYNC);
If (&msg.IsActive) Then
&rs0 = GetLevel0();
  &msg.CopyRowset(&rs0);
  &msg.Publish();
End-If;

Using the Full Data Subscribe Process (VENDOR_FULLSYNC)

The Full Data Subscribe process enables you to subscribe to supplier data.

Design Pattern

Message Name

Subscription Name

Full Data Replication

VENDOR_FULLSYNC

SupplierFullSync

Image: Process flow for full-data subscription suppliersprocess flow diagrams for full-data subscription diagrams of:process flow for full-data subscription

This diagram illustrates the Full Data Subscribe process:

Process flow for full-data subscription vendorsprocess flow diagrams for full-data subscription diagrams of:process flow for full-data subscription

Code for Full Subscription Process

The following code calls the full subscription process:

Declare Function supplier_intfc PeopleCode FUNCLIB_APEIP.VENDOR_ID FieldFormula;
Local Message &MSG;
&MSG = GetMessage();
Evaluate &MSG.GetRowset().GetRow(1).PSCAMA.MSG_SEQ_FLG.Value
When "H" 
When "T" 
   rem do nothing;
   Break;
When-Other
   supplier_intfc(&MSG);
End-Evaluate

Using the Full Data Publish Process (VENDOR_FULLSYNC)

The Full Table Publish process enables you to publish supplier data to external systems.

Design Pattern

Message Name

Full Data Replication

VENDOR_FULLSYNC

Image: Process flow for full-data publish suppliersprocess flow diagramsfor full-data publish diagrams of:process flow for full-data publish

This diagram illustrates the Full Table Publish process:

Process flow for full-data publish vendorsprocess flow diagramsfor full-data publish diagrams of:process flow for full-data publish

Running the Full Data Publish Process

Use the Full Table Publish Rules page to define the publish rule for the message.

Once you have defined the rules for a full-data publish, you must use the Full Data Publish page to run a PeopleSoft Application Engine process to generate a full-data message that is published to the external systems.

Using the Full Data Publish of Currently Effective Data Process (VENDOR_FULLSYNC_EFF)

The Full Table Publish of Currently Effective Data process (VENDOR_FULLSYNC_EFF) enables you to publish current supplier data to external systems.

Design Pattern

Message Name

Full Data Replication

VENDOR_FULLSYNC_EFF

Image: Process flow for full-data publish of currently effective data suppliersprocess flow diagramsfor full-data publish of currently effective data diagrams of:process flow for full-data publish of currently effective data

This diagram illustrates the Full Table Publish of Currently Effective Data process:

Process flow for full-data publish of currently effective data vendorsprocess flow diagramsfor full-data publish of currently effective data diagrams of:process flow for full-data publish of currently effective data

Use this message only when you publish data to systems that do not support effective dating. This message publishes only the most current supplier record. It does not publish any history or future rows.

To publish PeopleSoft tables that are effective-dated to an external system whose tables are not effective-date-enabled:

  1. Define the publish rule for the message on the Full Table Publish Rules page.

  2. Enter record mapping details on the Record Mapping page.

  3. Use the Full Data Publish process page to generate a full-data message for publication to an external system.

Mapping Effective-Dated Records for the Full Data Publish of Currently Effective Data Process

Use the Record Mapping page to map effective-dated records.

You need to map the following records because they are effective-dated, and the source view selects only the rows that are current.

Number

Record Name

Source View Record

1

VENDOR_ADDR

VNDR_ADDR_EFFVW

2

VENDOR_ADDR_PHN

VNDR_APHN_EFFVW

3

VENDOR_CNTCT

VNDR_CNTCT_EFVW

4

VENDOR_LOC

VNDR_LOC_EFFVW

5

VENDOR_PAY

VNDR_PAY_EFFVW

6

VNDR_BANK_ACCT

VNDR_BANK_EFFVW

7

VNDR_CNTCT_PHN

VNDR_CPHN_EFFVW

Using the Incremental Data Publish of Currently Effective Data Process (VENDOR_SYNC_EFF)

Design Pattern

Message Name

Subscription Name

PeopleCode subscribe

VENDOR_SYNC

SupplierSyncEff

Full data replication

VENDOR_SYNC_EFF

None

Image: Process flow for incremental message publish of currently effective data suppliersprocess flow diagrams for incremental message publish of currently effective data diagrams of:process flow for incremental message publish of currently effective data

This flowchart illustrates how the Incremental Publish of Currently Effective Data process enables you to publish supplier data incrementally to external systems:

Process flow for incremental message publish of currently effective data vendorsprocess flow diagrams for incremental message publish of currently effective data diagrams of:process flow for incremental message publish of currently effective data

Code for Incremental Publish Process for Currently Effective Data

The following code calls the subscription process:

Declare Function process_effdt_msg PeopleCode FUNCLIB_EOEIP.EFFDT_MSG_PC FieldFormula;
process_effdt_msg("VENDOR_SYNC_EFF", False);

As with the Incremental Publish process, during the save time of this process, the Supplier Information component publishes a VENDOR_SYNC message that contains effective-dated information.

For third parties that can handle effective-dated data, messages are received and processed using the SupplierSync subscription method. For third parties that cannot handle effective-dated data, a subscription process called SupplierSyncEff can be invoked for local publications. It has been set up on the message-generating side, and it makes a call to a shared function.

The common function determines if the data is related to the current effective-dated row and, if so, it copies the data to the VENDOR_SYNC_EFF message and publishes it.

If the data has future effective dates, then the information is written to the Delay table (EO_EFFDELAY). A PeopleSoft Application Engine process publishes the data that resides in delay tables as they become current.

Note: Third parties that cannot handle effective-dated data can subscribe only to the VENDOR_SYNC_EFF message.

Perform the following steps to run the Effective Date Publish Application Engine process:

  1. Define the publish rule for the message on the Full Table Publish Rules page.

  2. Create the run control for the Effective Date Publish process on the Effective Date Publish Process page.

Correcting Supplier Records in Error

Correcting errors is discussed in the documentation PeopleTools : Integration Broker.

See documentation PeopleTools : Integration Broker