Processing Enterprise Integration Points (EIPs)

This chapter discusses how to:

Process Inbound EIPs.
Process Outbound EIPs.
Process Backbone Interlinks.

Processing Inbound EIPs

This section discusses how to:

Use transaction maintenance.
Use data definition maintenance.
Purge transactions.

Pages Used to Process Inbound EIPs

Page Name	Object Name	Navigation	Usage
Transaction Maintenance	BCT_CTL_UPD	SCM Integrations, Transaction Error Handling, Maintain Transactions, Transaction Maintenance	View all electronic transactions in the transaction log and access the detail pages that enable you to correct transaction errors.
Data Def Maint	EO_EIP_CTL_MAINT	SCM Integrations, Transaction Error Handling, Maintain Data Definitions, Data Def Maint	View data detail or correct errors for inbound EIPs that contain data rather than transactions.
Purge	BCT_INV_REQPURG	SCM Integrations, Process Transactions, Purge, Transactional Data, Purge	Initiate the Purge Application Engine process (IN_BCT_PURGE) that purges transactions for EIPs.

Using Transaction Maintenance

Access the Transaction Maintenance page.

All transactional-based information appears on this page. The system displays the transaction code, which identifies the transaction type, and the transaction description.

EIP Control ID

Click this link to view the transaction line details for the transaction. Detail pages for each transaction type, which are accessible from this page, provide error messages and transaction details that enable you to revise fields containing errors.

You can modify the transaction status here or in the Transaction Maintenance Detail pages. The rules for changing a transaction status are:

Current Status	Change to Status
New	Complete (cancels all lines in the transaction).
Error	Complete (cancels all lines in the transaction). Reprocess.
Complete	Can’t be changed.
In Process	Can’t be changed.
Reprocess	Complete (cancels all lines in the transaction).
Incomplete	Can’t be changed.

Using Data Definition Maintenance

Access the Data Def Maint (data definition maintenance) page.

All data definition transactions appear on this page. Detail pages for each transaction type, which are accessible from this page, provide error messages and transaction details that allow you to revise fields containing errors.

If you want to retrieve records by transaction, select one of these transaction types:

Transaction Type	Description
AP - 100	Retrieves vendor synchronization transactions that have been received. To receive vendor synchronization transactions, you must have PeopleSoft Payables installed.
AP - 200	Retrieves vendor edit transactions that have been received. To receive voucher edit transactions, you must have PeopleSoft Payables installed.
ASNIN	Retrieves advanced shipping receipt transactions that have been received. To receive Advanced Shipping Receipt transactions, you must have PeopleSoft Purchasing installed.
BOM	Retrieves bills of material transactions that have been received. To receive bills of material transactions, you must have PeopleSoft Manufacturing installed.
CONSUMER	Retrieves consumer sync transactions that have been received. To receive consumer sync transactions, you must have PeopleSoft Inventory installed.
ITEM	Retrieves item loader and item sync transactions that have been received. To receive item loader and item sync transactions, you must have PeopleSoft Inventory, PeopleSoft eProcurement, or PeopleSoft Purchasing installed.
ITM_MFGGPO	Retrieves manufacturer group purchasing organization (GPO) item price list transactions that have been received. To receive manufacturer GPO item price list transactions, you must have PeopleSoft Purchasing or PeopleSoft Inventory installed.
PO	Retrieves purchase order transactions that have been received. To receive inbound sales order (850) transactions, you must have PeopleSoft Order Management installed.
POACK	Retrieves purchase order acknowledgement transactions that have been received. To receive purchase order acknowledgement transactions, you must have PeopleSoft Purchasing installed.
POCHG	Retrieves purchase order change transactions that have been received. To receive sales order change (860) transactions, you must have PeopleSoft Order Management installed.
PROCARD	Retrieves procurement card transactions that have been received. To receive procurement card transactions, you must have PeopleSoft Purchasing or PeopleSoft eProcurement installed.
PRODUCTMST	Retrieves product master transactions that have been received. To receive product master transactions, you must have PeopleSoft Order Management installed.
REQLOAD	Retrieves requisition loader transactions that have been received. To receive requisition loader transactions, you must have PeopleSoft Purchasing or PeopleSoft eProcurement installed.
RFQ	Retrieves request for quotation (RFQ) transactions that have been received. To receive inbound request for quote (840) transactions, you must have PeopleSoft Order Management and PeopleSoft Purchasing installed.
RFQRESP	Retrieves RFQ response transactions that have been received. To receive RFQ response transactions, you must have PeopleSoft Purchasing installed.
RMALOAD	Retrieves inventory RMA transactions that have been received. To receive RMA load transactions, you must have PeopleSoft Inventory installed.

Grid Select

Some transactions are loaded into staging tables while others remain in the Integration Broker queue until they are successfully processed. Select Queue to view those residing in the Integration Broker queue and Staged to view those that are in a stage table.

Search

Click this button to display all the transactions that match the search criteria selected.

Note. To display all of the records in the transaction log, leave the search criteria fields blank.

Click the Show Detail Entry button to access the detail pages. Detail pages for each transaction type, which are accessible from this page, provide error messages and transaction details that enable you to revise fields containing errors.

Purging Transactions

Access the Purge page.

Use this page to initiate the Purge process. The Purge process will delete all transactions with a status of Complete or Confirmed from the transaction log.

Use the Data Collection Setup page to choose to not maintain a history, to maintain a history for all transactions, or to maintain a history only for transactions containing errors. You can also determine whether to purge transactions with a status of Complete or Confirmed on this page.

You can view the transaction history by running a query. Use the BCT_HIST and BCT_ERR_HIST tables to view the transaction history.

Inbound Data to Purge

You can choose to purge all transactions, whereby the system purges all transactions containing either the Confirmed or Complete status that you set up on the Data Collection Setup page. Or you can enter a number of days to purge only items with at least that many days since the last activity.

Processing Outbound EIPs

This section discusses how to process outbound EIPs.

Page Used to Process Outbound EIPs

Page Name	Object Name	Navigation	Usage
Publish Outbound Message	IN_RUN_PUB_MSG	SCM Integrations, Publish Outbound Message	Initiate the outbound message publish process for outbound PeopleSoft SCM transactions that use the batch publish design pattern.

Processing Outbound EIPs

Access the Publish Outbound Message page.

Note. This page is used only to process transactions that use the batch publish design pattern.

Select the check box by the name of the message (service operation) that you want to process. The system then makes the message name a link to a transaction-specific page for that service operation. You can process service operations one at a time or in multiples.

Processing Backbone Interlinks

This section discusses how to run the Backbone Interlink process.

Page Used to Process Backbone Interlinks

Page Name	Object Name	Navigation	Usage
BankBone InterlinX - Process Request	SAC_BBIX_RUN_CNTL	SCM Integrations, BackBone InterlinX, Run BBIX Process, BankBone InterlinX - Process Request	Initiates transferring data from one PeopleSoft database to another.

Running the Backbone Interlink Process

Access the BankBone InterlinX - Process Request page.

Override

Select this check box to override the integration’s default filter with a custom filter to use when processing the integration. Once selected, the system makes the Filter field available for entry.