Working with Outbound Interface Transactions (WOIT) | Contents | SCVs | Search | Glossary | Reports | Solutions | XML | Index | Generic Customer History API |
Generating Outbound Interface Triggers (GOIT)
Purpose: Use this menu option to create triggers in the IL Outbound Trigger table. You have the option to create triggers for:
• item/SKUs (if the Create Generic Item Download Trigger Records (I15) system control value is selected)
• vendors (if the Create Generic Vendor Download Trigger Records (I16) system control value is selected)
• invoices (if the Create Generic Invoice Download Trigger Records (I17) system control value is selected)
• inventory (if the Create Generic Inventory Download Triggers (I32) system control value is selected)
You can use the Working with Outbound Interface Transactions (WOIT) menu option to review the triggers the system generated.
In this chapter:
• Processing Sequence of Item Triggers
• Generate Outbound Interface Trigger Screen
You can define trigger rules for each IL Process job 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.
If you generate triggers for: |
look at trigger rules for IL Process job: |
trigger rules are based on criteria for these tables: |
item |
Item Outbound |
Item (INITEM) SKU (INSKU) |
vendor |
Vendor Outbound |
Vendor (POVEND) |
invoice |
Invoice Outbound |
Invoice Header (OEINHD) Order Header (OEORDR) |
inventory |
Inventory Download |
Item (INITEM) Item Warehouse (INIWRE) SKU (INSKU) Warehouse (INWRHS Item UPC (ITMUPC) |
Processing Sequence of Item Triggers
The system generates item download triggers alphabetically by item number and SKU code in Kit type sequence. This way all items that are components of any type of kit are processed before the main kit item is processed.
1. The system generates triggers alphabetically by item number and SKU code for all items/SKUs whose Kit type is blank.
2. The system generates triggers alphabetically by item number and SKU code for all items/SKUs whose Kit type is F (finished good kit).
3. The system generates triggers alphabetically by item number and SKU code for all items/SKUs whose Kit type is S (set kit).
4. The system generates triggers alphabetically by item number and SKU code for all items/SKUs whose Kit type is V (variable set kit).
Example: The system generates item download triggers in the following sequence, based on the item’s Kit type.
Item number |
Kit type |
Sequence |
204I |
blank |
1 |
204J |
blank |
2 |
204K |
blank |
3 |
204C |
F |
4 |
204F |
F |
5 |
204B |
S |
6 |
204G |
S |
7 |
204D |
V |
8 |
204E |
V |
9 |
Generate Outbound Interface Trigger Screen
Use this screen to define the type of triggers you wish to create in the IL Outbound Trigger table.
How to display this screen: Enter GOIT in the Fast path field or select Generate Outbound Interface Triggers from a menu.
Field |
Description |
Item |
Indicates whether you wish to create triggers in the IL Outbound Trigger table for items/SKUs. • Selected = Generate item/SKU triggers. The system creates a trigger for each SKU in the SKU table that is associated with an item in the Item table and assigns item/SKU triggers a File code of SKU. • Unselected (default) = Do not generate item/SKU triggers. See Generic Item Download API for more information on processing item download triggers. Note: The Create Generic Item Download Trigger Records (I15) system control value must be selected to generate item triggers. Process sequence: The system generates item download triggers alphabetically by item number and SKU code in Kit type sequence. This way all items that are components of any type of kit are processed before the main kit item is processed. See Processing Sequence of Item Triggers for an example. |
Invoice |
Indicates whether you wish to create triggers in the IL Outbound Trigger table for invoices. • Selected = Generate invoice triggers. The system creates a trigger for each invoice in the Invoice Header table and assigns invoice triggers a File code of IHD. • Unselected (default) = Do not generate invoice triggers. See Generic Invoice Download API for more information on processing invoice download triggers. Note: The Create Generic Invoice Download Trigger Records (I17) system control value must be selected to generate invoice triggers. |
Vendor |
Indicates whether you wish to create triggers in the IL Outbound Trigger table for vendor information. • Selected = Generate vendor triggers. The system creates a trigger for each vendor in the Vendor table and assigns vendor triggers a File code of VND. • Unselected (default) = Do not generate vendor triggers. See Generic Vendor Download API for more information on processing vendor download triggers. Note: The Create Generic Vendor Download Trigger Records (I16) system control value must be selected to generate vendor triggers. |
Inventory |
Indicates whether you wish to create triggers in the IL Outbound Trigger table for inventory information. • Selected = Generate inventory triggers. The system creates a trigger for each SKU in the Item Warehouse table and assigns inventory triggers a File code of ITW. If the Include Non-Allocatable Warehouses (I34) system control value is unselected, the system creates a trigger record for an item only if it has an Item Warehouse record in an allocatable warehouse. • Unselected (default) = Do not generate inventory triggers. See Generic Inventory Download API for more information on processing inventory download triggers. Note: The Create Generic Inventory Download Triggers (I32) system control value must be selected to generate inventory triggers. |
Completing this screen:
1. Select the triggers you would like to generate.
2. Select OK to validate your selection.
3. Select Submit to submit the triggers.
The system submits the:
• ITMDWNLD job to generate item triggers; see Generic Item Download API.
• INVDWNLD job to generate invoice triggers; see Generic Invoice Download API.
• VNDDWNLD job to generate vendor triggers; see Generic Vendor Download API.
• INVENDL job to generate inventory triggers; see Generic Inventory Download API.
Screen Option |
Procedure |
Submit the generation of IL outbound triggers |
Select Submit. The system submits the: • ITMDWNLD job to generate item triggers; see Generic Item Download API. • INVDWNLD job to generate invoice triggers; see Generic Invoice Download API. • VNDDWNLD job to generate vendor triggers; see Generic Vendor Download API. • INVENDL job to generate inventory triggers; see Generic Inventory Download API. |
Working with Outbound Interface Transactions (WOIT) | Contents | SCVs | Search | Glossary | Reports | Solutions | XML | Index | Generic Customer History API |
GOIT OROMS 16.0 December 2016 OTN