Processing Integration Points

This chapter discusses:

Processing inbound transactions
Processing outbound transactions.
Processing backbone interlinks.

Processing Inbound Transactions

This section discusses how to:

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

Pages Used to Process Inbound Transactions

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 subscribe messages 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 enterprise integration points (EIPs).

Using Transaction Maintenance

Access the Transaction Maintenance page.

All transactional-based information appears 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.

Click the EIP Control ID link to view the transaction line details for the transaction. The system displays the transaction code, which identifies the transaction type, and the transaction description.

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.

Some transactions are preloaded into staging tables while others remain in the Application Messaging Queue until they are successfully processed. Select Queue Based to see those residing in the Application Messaging Queue and Stage Table Status to see those that are in a stage table. If you are retrieving records by transaction, select one of these transaction types:

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

To display all of the records in the transaction log, leave these fields blank.

Click the Search button to populate the page with the transactions that match your criteria.

Purging Transactions

Access the Purge page.

Run the Purge process to 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.

Publishing Outbound Messages

This section discusses how to publish outbound messages.

Page Used to Publish Outbound Messages

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 messages that use the batch publish design pattern.

Publishing Outbound Messages

Access the Publish Outbound Message page.

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

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

Processing Backbone InterlinX Transactions

This section discusses how you process backbone InterlinX transactions.

Page Used to Process Backbone InterlinX Transactions

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

Running the Backbone InterlinX process

Access the Run BBIX Process page.

Override

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