Working with Outbound Interface Transactions (WOIT)
Purpose: Use this option to review triggers in the IL Outbound Trigger table.
Certain actions in Order Administration triggers the system to create IL outbound triggers.
In this topic:
You can create triggers for the following information.
Information | Generated When | See: | File/ Key |
---|---|---|---|
stored value card authorization reversals |
a cancellation is processed against a stored value card payment or the stored value card payment is deactivated and an open, unused authorization amount exists |
AHR |
|
credit card authorization reversals |
the Send reversal field for the service bureau is selected and a cancellation is processed against a credit card payment or the credit card payment is deactivated and an open, unused authorization amount exists |
AHR |
|
ChannelAdvisor shipments |
the BILL_ASYNC job processes a shipment for an order whose type matches the ChannelAdvisor Order Type (L90) |
CAS |
|
customers |
the Create Generic Customer Download Triggers (L12) system control value is selected |
Generic Customer Download API For more information see the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1). |
CST |
invoices |
the Create Generic Invoice Download Trigger Records (I17) system control value is selected |
Generic Invoice Download API and Integration with the Sales Audit Module of the Oracle Retail Merchandising Foundation Cloud Service For more information see the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1). |
IHD |
inventory |
the Create Generic Inventory Download Triggers (I32) system control value is selected |
Generic Inventory Download API For more information see the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1). |
ITW |
pick slips |
the Create Generic Pick Download Triggers (I31) system control value is selected |
Generic Pick Out API For more information see the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1). |
PCH |
purchase orders |
the Use WMS Integration (K25) and/or Create Generic PO Download Triggers (K26) and/or Create Generic PO Download Trigger for PO Receipt (K27) system control values are selected |
Generic Outbound Purchase Order API For more information see the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1). |
POH |
return authorizations |
the Create Return Download Triggers (K28) system control value is selected |
RAD |
|
items/SKUs |
the Create Generic Item Download Trigger Records (I15) system control value is selected |
Generic Item Download API For more information see the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1). |
SKU |
stored value cards |
a stored value card item is processed through billing |
SVC |
|
vendors |
the Create Generic Vendor Download Trigger Records (I16) system control value is selected |
Generic Vendor Download API For more information see the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1). |
VND |
Mass trigger creation: Additionally, you can create triggers for all item/SKUs, vendors, item warehouses (inventory), and/or invoices using the Generating Outbound Interface Triggers (GOIT) menu option.
Jobs in the Working with Integration Layer Processes (IJCT) menu option monitor the triggers in the IL Outbound Trigger table. At certain intervals the jobs process the triggers and generate a download XML message to send to another system.
Each trigger in the IL Outbound Trigger table contains a File code, indicating the Order Administration table(s) associated with the trigger, the key fields necessary to retrieve the information, and which IL Process job processes the trigger record.
Trigger rules: You can define trigger rules for the following IL Process jobs to determine when the system generates a trigger, based on criteria defined. The record for which you wish to create a trigger must meet the trigger rule criteria in order to create a trigger in the IL Outbound Trigger table; see Defining Outbound Interface Trigger Rules.
Example: If a trigger rule for the Item Outbound job is that the item’s Allow SKU field must equal ’Y’, the system creates a trigger only for SKU’ed items.
If you generate triggers for: | look at trigger rules for IL Process job: | trigger rules are based on criteria for this table: |
---|---|---|
customers |
Customer Download Outbound |
Customer Sold To (Company, Customer class, Inactive?, Country) |
item |
Item Outbound |
Item (INITEM) SKU (INSKU) See Item Outbound Trigger Rules. For more information see the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1). |
vendor |
Vendor Outbound |
Vendor (POVEND) See Vendor Outbound Trigger Rules. For more information see the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1). |
invoice |
Invoice Outbound |
Invoice Header (OEINHD) Order Header (OEORDR) See Invoice Outbound Trigger Rules. For more information see the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1). |
inventory |
Inventory Download |
Item (INITEM) Item Warehouse (INIWRE) SKU (INSKU) Warehouse (INWRHS Item UPC (ITMUPC) See Inventory Download Trigger Rules. For more information see the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1). |
pick slips |
Pick Outbound |
Pick Control Header (FLPCTH) See Pick Out Processing. For more information see the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1). |
purchase order |
Purchase Order Outbound |
Purchase Order Header (POH) See Purchase Order Download Trigger Rules For more information see the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1). |
return authorization |
Return Authorization Outbound |
Order Header (OEORDR) |
Note:
Direct table updates are not captured in the IL Outbound Trigger table.
IL Outbound Triggers
This table indicates:
-
when the system creates a trigger
-
the File code assigned to each trigger created
-
the referenced tables, based on the File code
-
the key data captured in the Key field
-
the IL Process job that processes the trigger.
File code | Created when | Refers to table(s) | Key | IL Process job |
---|---|---|---|---|
AHR |
A cancellation is processed against a stored value card or credit card payment or the stored value card or credit card payment is deactivated and an open, unused authorization amount exists. |
Auth History SVC Reversal |
11122222222333444555 where: 111 is the company code 22222222 is the order number 333 is the order payment method sequence number 444 is the authorization sequence number 555 is the authorization reversal sequence number |
SVC_REVRSL (for stored value cards) |
CAS |
The BILL_ASYNC job processes a shipment for an order whose type matches the ChannelAdvisor Order Type (L90) |
Order Header Invoice Header |
111222222223333333 where: 111 is the company code 22222222 is the order number 3333333 is the invoice number |
N/A (processed by the CASHIP periodic function) |
CST |
You create, change, or delete a customer |
Customer Sold To |
11122222222333444555 where: 111 is the company code 222222222 is the customer number |
CUST_OUT |
IHD |
An invoice is created or updated, if the Create Generic Invoice Download Trigger Records (I17) system control value is selected |
Invoice Header Order Header |
111222222223333333 where: 111 is the company code 22222222 is the order number 3333333 is the invoice number |
INVOIC_ OUT |
ITW |
The item/SKU’s availability threshold is breached, if the Create Generic Inventory Download Triggers (I32) system control value is selected, and when you create or maintain a purchase order for the item, if the Include PO Updates (J93) system control value is selected |
Item Warehouse |
11122222222222233333333333333 where: 111 is the company code 222222222222 is the item number 33333333333333 is the SKU code |
INV_ DOWNLD |
PCH |
A pick slip is generated, if the Create Generic Pick Download Triggers (I31) system control value is selected |
Pick Control Header |
1112222222 where: 111 is the company code 2222222 is the pick control number |
PICK_OUT |
POH |
A purchase order outbound trigger is generated, if the Create Generic PO Download Triggers (K26) system control value is selected. |
PO Header |
1112222222 where: 111 is the company code 2222222 is the purchase order number |
PO_OUT |
RAD |
A return authorization is created, changed, or deleted if the Create Return Download Triggers (K28) system control value is selected |
RA Detail |
11122222222333444555 where: 111 is the company code 22222222 is the order number 333 is the ship to number 444 is the return authorization number 555 is the return authorization line number |
RETURN_OUT |
SKU |
An item or SKU is added, updated or deleted, if the Create Generic Item Download Trigger Records (I15) system control value is selected |
Item SKU |
11122222222222233333333333333 where: 111 is the company code 222222222222 is the item number 33333333333333 is the SKU code |
ITEM_OUT |
SVC |
An order containing a stored value card item that is assigned a number is processed through the Billing Async; see Stored Value Card Purchase and Activation |
Stored Value Card |
111222222223334444455555 where: 111 is the company code 22222222 is the order number 333 is the ship to number 44444 is the order detail line sequence number 55555 is the stored value card sequence number |
SVC_OUT |
VND |
A vendor is added, updated or deleted, if the Create Generic Vendor Download Trigger Records (I16) system control value is selected |
Vendor Vendor Extended |
1112222222 where: 111 is the company code 2222222 is the vendor code |
VENDOR_ OUT |
Work with Outbound Interface Transactions Screen
Purpose: Use this screen to review the triggers in the IL Outbound Trigger table.
How to display this screen: Enter WOIT in the Fast path field or select Work with Outbound Interface Transactions from a menu.
Field | Description |
---|---|
File |
A code identifying the Order Administration table(s) containing records you wish to download. This code also indicates which IL Process job processes the trigger record.
|
|
Example: If you create an item, the system creates an item download trigger in the IL Outbound Trigger table with a File code of SKU, indicating a change has been made to the Item and SKU table and an item download message should be generated. The Key field identifies the particular Order Administration company and data, in this example, item and SKU record, that has been updated. Alphanumeric, 3 positions; optional. |
S (status) |
The status of the IL outbound trigger.
The system purges processed (X) trigger records, based on the setting of the Outbound Interface Trigger File Purge Days (I14) system control value, when you run the PURGIJT periodic function (program name ILR0026) or select the Purge option at this screen. Alphanumeric, 1 position; optional. |
Capture date |
The date the activity occurred which created the trigger. Numeric, 6 positions (in user date format); optional. |
Capture time |
The time the activity occurred which created the trigger. Numeric, 6 positions (HH:MM:SS format); display-only. |
Orig process date |
The date the trigger was originally processed by the system. Blank if the trigger has not yet been processed. Numeric, 6 positions (in user date format); display-only. |
Orig process time |
The time the trigger was originally processed by the system. Blank if the trigger has not yet been processed. Numeric, 6 positions (HH:MM:SS format); display-only. |
Last process date |
The date the trigger was last re-processed by the system. You can reprocess a specific trigger by selecting Reset for a trigger. You can reprocess a group of triggers by selecting Reset All. You can only reprocess triggers that are in a pending (P) or processed (X) status. Numeric, 6 positions (in user date format); display-only. |
Last process time |
The time the trigger was last re-processed by the system. Numeric, 6 positions (HH:MM:SS format); display-only. |
From |
The name of the program associated with the Order Administration action that created the trigger. Alphanumeric, 8 positions; display-only. |
A/C |
A code that indicates whether the Order Administration activity represents creation of a new record, a change to an existing record, or a delete of an existing record.
Alphanumeric, 1 position; display-only. |
Key |
A code used to identify the Order Administration company and data that has been updated. The File field identifies the table where the updated data is located. The Key is then used to identify the record in the table that has been updated. ChannelAdvisor shipment If the file code is CAS, the key is company code + order number + invoice number. For example, 0060000123400000123 indicates the trigger is for company 6, order number 1234, and invoice number 123. Customer If the file code is CST, the key is company code + customer number. For example, 006000013049 indicates the trigger is for company 6, customer 13049. Item/SKU If the file code is SKU, the key is company code + item number + SKU code. For example, 555ABC101020 RED GRLS LRGE indicates the trigger is for company 555, item number ABC101020, and SKU code RED GRLS LRGE. If the item is non-SKU’ed, the SKU code is not part of the key. Invoice If the file code is IHD, the key is company code + order number + invoice number. For example, 5550000596900000495 indicates the trigger is for company 555, order number 5969, and invoice number 495. |
|
Inventory If the file code is ITW, the key is company code + item number + SKU code, as described above for Item/SKU. Purchase Order Download If the file code is POH, the key is company code + purchase order number. For example, 0120000636 indicates the purchase order is from company 12 and the purchase order number is 636. Vendor If the file code is VND, the key is company code + vendor code. For example, 55520002 indicates the trigger is for company 555 and vendor number 20002. Stored Value Card If the file code is SVC, the key is company code + order number + ship to number + order detail sequence number + stored value card sequence number. For example, 555000066760010000100004 indicates the trigger is for company 555, order number 6676, ship to number 1, order detail sequence number 1, and stored value card sequence number 4. Return Authorization Download If the file code is RAD, the key is company code + order number + ship to number + return authorization number + return authorization line number. For example, the Key 00700001446001001001 indicates the return authorization download information is located in company 7 for order number 1446, ship to number 1, return authorization number 1, and return authorization line number 1. Alphanumeric, 30 positions; optional. |
Screen Option | Procedure |
---|---|
Delete an IL outbound trigger |
Select Delete for a trigger to advance to the Confirm Delete window; select OK to delete it. Note: The system allows you to delete any trigger, regardless of whether the status is ready (R) or processed (X). |
Reprocess a processed trigger |
Select Reset for a trigger to update the status of the trigger from pending (P) or processed (X) to ready (R). The system also updates the Last processed date and Last processed time fields once the trigger is reprocessed. The next time the IL Process job monitors the IL Outbound Trigger table for unprocessed triggers, the job will reprocess the trigger. Pick triggers associated with a drop ship invoice/pick: If a PCH trigger is associated with a drop ship invoice/pick, you will not be able to re-send a CWPickOut message for the trigger because the system deletes the pick records immediately after the drop ship forms are generated. |
Reprocess a group of triggers |
Select Reset All to advance to the Reset All Window. |
Purge processed triggers |
Select Purge to submit the PURGE_IL job. This job deletes processed (X) trigger records, based on the setting of the Outbound Interface Trigger File Purge Days (I14) system control value. You can also purge records through the PURGIJT periodic function (program name ILR0026). |
Reset All Window
Use this window to update the status of a group of triggers from Pending or Processed to Ready.
To reset: Enter the File code, Capture date, and the current Status of the group of triggers you wish to reprocess and select OK.The system changes the status of the group of triggers to Ready.
The next time the IL Process job monitors the IL Outbound Trigger table for unprocessed triggers, the job will reprocess the triggers.
Pick triggers associated with a drop ship invoice/pick: If a PCH trigger is associated with a drop ship invoice/pick, you will not be able to re-send a CWPickOut message for the trigger because the system deletes the pick records immediately after the drop ship forms are generated.
How to display this screen: Select Reset All at the Work with Outbound Interface Transactions Screen.
Field | Description |
---|---|
File code |
A code identifying the type of triggers you wish to reprocess.
Alphanumeric, 3 positions; required. |
Capture date |
The date the activity occurred which created the group of triggers you wish to reprocess. Numeric, 6 positions (in user date format); required. |
Status |
The status of the group of triggers you wish to reprocess.
Select Pending or Processed in this field to change the status of the group of triggers to Ready. The next time the IL Process job monitors the IL Outbound Trigger table for unprocessed triggers, the job will reprocess the triggers. Alphanumeric, 1 position; required. For more information see the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1). |