Home

Oracle® e-Commerce Gateway

1. cccc cee eee ceeceee eens ea eaaa AA a EERE a Enea R ea aE aiaia aaa 2 1 Other Application Implementations ssnneneeieenseinenssrintisrinenintrntisrintninrnnrinsinsrnnrnnennnennee 2 3 Determine Communications Methods For The Transactions 0 0 ccsceseeseeeee eee eneeeees 2 6 Implementation Planning siirt a aedi kia see a aa paaa andai 2 7 3 Oracle e Commerce Gateway Implementation Checklist Implementation Stepska dae tienda A eG i e a 3 1 Implementation Checklist for Software Upgrade ccccccee cece cee eeee scene seen seer eeenneenees 3 2 Implementation Checklist for Fresh Install 00 00 0 cece ee ee eterna ree ener neeteeteeeies 3 8 4 Implementation Details Define Responsibilities s aii aaea trenda aaa eaaa aa a iha iad aeiia daa 4 2 Define UTL_FILE_DIR Parameter in INIT ORA File 0 ccccccccccccccceeeceeeeeeeeeeeeeeeeeeeeees 4 2 Review Release 12 Upgrade Guideline 0 00 cece eee terrier eee ree eee tee tneesneeeeneetneeegs 4 3 Set UP Profiles rentia aie vin eet ots ee a need Renin ented E 4 5 System Profile Window 3 02720 ee dase cds atari sane diria dds a tavetes 4 6 Transaction Profile Wind Ow tii 2 fs0hes ccetanes patatine ain a aa Ae a A aiai a 4 7 Transaction Specific Options 0cce cece tee eee a esse see a e aeiaai 4 8 Outbound Purchase Order Transaction Profile 0 00ccec escent eee teeter eee tee neeeeeaes 4 11 Determine Process
2. ple ER 1_ Variable definitions stored int contact data from the MATI 1 Find the position of the ITEM ID in the PL SQL table hat position to select th ERIAL ANALYSTS custom table plsql table ITEM ID ECE Mat Every value in the PL SQI so convert the value to a number ItemIDPosition AR TRX LINES X Then necessary L table is stored as VARCHAR2 plsql_table v_ItemIDPosition value Get the necessary data from MATERIAL ANALYSTS and insert it for exam INSERT INTO ece ar trx lines x Transaction Record ID END PROC EDUR F Populate Material Analyst Code Material Analyst _Last_Name Material Analyst _First_Name Material Analyst Phone Material Analyst Email SELECT 1 fkey material analyst _code material analyst _last_name material analyst first _name material analyst phone material analyst _email FROM material analysts WHERE inventory item id v_ItemID Extension Line Once the procedure has been modified it must be recompiled for the changes to take effect Log into SQL Plus as the APPS user and issue the following command Extensible Architecture 11 17 SQL gt ECEPOOXB pls Package body created The customization process is complete each subsequent execution of the outbund Purchase Order transaction will include the new extension
3. 0010 Control Record Only one record occurrence per transaction 0020 0070 Gateway Flexfields One set of records per transaction 1000 1999 Application Advice Header Only one record occurrence Records per transaction 2000 2999 Application Advice Detail One set of detail records per Records error within the transaction The following table is a summary list of the records that comprise the Outbound Application Advice transaction The table shows the functional data grouping of records the data level the record numbers and relevant notes about the data grouping ADVO Transaction Record Summary Type of Data Data Level Record Number Note 1 Control Record HEADER 0010 2 Trading Partner HEADER 0020 050 Custom Header Attributes 3 Trading Partner HEADER 0060 0070 Custom Detail Attributes 4 Advice Header HEADER 1000 1010 Flexfields External References 6 Advice Header HEADER 1020 1030 Flexfields Internal References Transaction Summary Layouts A 87 Type of Data Data Level Record Number Note 8 Trading Partner HEADER 1040 Address 9 Extension Table HEADER 1900 Custom Header Level 10 Advice Detail DETAIL 2000 2010 Flexfields External References 12 Advice Detail DETAIL 2020 2030 Flexfields Internal References 14 Advice Detail DETAIL 2040 Data Error 15 Advice Detail DETAIL 2050 Data Accepted 16 Extension Table DETAIL 2900 Custom Detail Level Outbound Application Advice Common Key The
4. Error Correction If you agree that a detected exception is an error you must proceed to get the error corrected Since the documents being transmitted between you and your trading partner represent legal documents Oracle e Commerce Gateway does not allow you to correct any errors so the errors must be corrected at the source If you cannot resolve the exception using the appropriate Oracle Applications set up you can bypass the validation in Oracle e Commerce Gateway by enabling the IGNORE check box via the View Staged Documents window Alternately you can delete the transaction and ask your trading partner to resend a corrected transaction If the error originated in Oracle Applications you must correct the error in the appropriate Oracle Applications module and then resubmit the transaction using the View Staged Documents window There is no need to re import the interface file from the sender If you determine that a detected exception is really a warning that does not adversely affect the process you can do one of the following 4 18 Oracle e Commerce Gateway Implementation Manual e Unz assign the column rule using the Assign Column Rules window This change applies to all documents of the same transaction type until you re assign the rule e Assign a less restrictive column rule or column rule action using the Assign Column Rules window This change applies to all documents of the same transaction type until you reset th
5. If the Supplier Inventory Item is in the transaction compare it to the derived Supplier Inventory Item Use the derived supplier inventory item and create an error message showing the sent inventory item if the vendor inventory items do not match CUSTOMER_ITEM_NAME is populated and Inventory Item Cross Reference Generic CUSTOMER_ITEM_ID_TYPE isa valid Cross table Reference Type other than CUST or INV If the Supplier Inventory Item is in the transaction compare it to the derived Supplier Inventory Item Use the derived supplier inventory item and create an error message showing the sent inventory item if the supplier inventory items do not match CUSTOMER_ITEM_NAME is NOT populated Inventory Item table for internal vendor and only the Supplier Inventory Item is items populated If the CUSTOMER_ITEM_ID_TYPE is null but data is in the CUSTOMER_ITEM_NAME the search will span all three tables until the item is found You run the risk of getting multiple table hits in the inventory item cross reference generic table if the same item number is defined under multiple CUSTOMER_ITEM_ID_TYPEs such as UPC and EAN However since the naming conventions for multiple items are diverse the probability may be slight Multiple items found will cause an error on the item 6 54 Oracle e Commerce Gateway Implementation Manual Data in the e Commerce Gateway Transaction Order of the Tables Searched CUSTOMER_ITE
6. Trading Partner Link to Oracle e Commerce Gateway Suppliers and supplier sites are defined in either Oracle Purchasing or Oracle Payables Included in the definition is the EDI Location Code that trading partners agree to 6 72 Oracle e Commerce Gateway Implementation Manual exchange to represent the full detailed address Often they do not send the full address but just the EDI Location Code This is a critical data field to Oracle e Commerce Gateway The EDI Location Code is the link between a supplier supplier site in Oracle Applications and the trading partner site definition in Oracle e Commerce Gateway This enables Oracle e Commerce Gateway to access the detailed data about the supplier or supplier site in the base Oracle Applications without maintaining the detail data in Oracle e Commerce Gateway To ensure that the trading partner link between Oracle e Commerce Gateway and Oracle Applications is set up properly verify that the supplier supplier site and the EDI Location Code in Oracle Applications is the correct supplier supplier site selected for the Trading Partner definition in Oracle e Commerce Gateway The selected supplier supplier site and the EDI Location Code defined in Oracle Applications are displayed in the Define Trading Partners window Assignment tab If the data is not what you intend it to be you must make the appropriate changes for the transaction to be imported for the correct trading partner This could involv
7. 6 140 Oracle e Commerce Gateway Implementation Manual e FROM_TO ITEM_DETAIL_TYPE_INT Detail Type is used by the Demand Processor to determine how the schedule line itself should be interpreted Valid Values 0 Past Due Firm 1 Firm Demand 2 Forecast Demand 3 Authorization 4 Shipment Receipt Data 5 Other ITEM_DETAIL_SUBTYPE_INT Detail Subtype is used by the Demand Processor to determine how the schedule line itself should be interpreted in context of its corresponding Detail Type Each Item Detail Type has a corresponding list of valid Item Detail Subtypes listed in the table below If ITEM_DETAIL_TYPE Equals then ITEM_DETAIL_SUBTYPE contains 0 1 2 1 Day 2 Week 3 Flexible 4 Month 5 Quarter 3 FINISHED Finished Goods MATERIAL Raw Material LABOR_MATERIAL Labor and Material LABOR Labor PRIOR_CUM_REQ Prior Cumulative Required Application Transaction Detail 6 141 If ITEM_DETAIL_TYPE Equals then ITEM_DETAIL_SUBTYPE contains 4 SHIPMENT Shipment RECEIPT Receipt CUM Customer CUM CUM_REJECTED CUM Rejected 5 AHEAD_BEHIND Ahead Behind INVENTORY_BALANCE Inventory Balance HOLDOUT_QTY In Holdout START_DATE_TIME_DET Customer specified date time as transmitted by the customer on the transaction Format YYYYMMDD HHMMSS OTY_TYPE_CODE_INT Quantity Type is used by the Demand Processor to determine how the quantity on schedule lines should be
8. 6 148 Oracle e Commerce Gateway Implementation Manual Management Demand Processor Refer to the Oracle Release Management Implementation Manual and Oracle Release Management User s Guide for details 1 RLM MRP Forecast Selection List e If defined the MRP Forecast Selection List lists all the names of Forecasts to which inbound Release Management forecast demand can be assigned e If set to none forecast data will not be imported into Planning 2 RLM CUM Management Enabled Determines whether or not CUM Management is enabled at the Site level To use the CUM Management features of Oracle Release Management this must be set to Yes 3 RLM Print CUM Data on Shipping Documents Determines whether or not CUM Data should be printed on shipping documents 4 RLM Debug Mode Determines if a debug file is written for running the Demand Processor Valid Values are 0 highest debug level Null no debug file is generated This is the default value 5 RLM Workflow Enabled Determines whether or not the Demand Processor is enabled to run in workflow mode 6 ECE SPSI Enabled Determines whether or not inbound planning schedule transaction is enabled 7 ECE SSSI Enabled Determines whether or not inbound shipping schedule transaction is enabled 8 ECE PSQI Enabled Determines whether or not inbound sequenced shipping schedule transaction is enabled 9 Release Management Processing Rules e There are five
9. Construction of ORIG_SYS_DOCUMENT_REF Original System Document Reference 86420 03 Defaulted by the POI Program to use CUSTOMER_PO_NUMBER Your Modified Purchase Order Number moved into CUSTOMER_PO_NUMBER 86420 03 Note You concatenated the fields Construction of ORIG_SYS_DOCUMENT_REF Original System Document Reference 86420 03 Constructed by the EDI Translator then copied to the file Purchase Order Number Purchase Order Release Number from Customer s Purchasing Application from Customer s Purchasing Application 86420 03 This concatenation needs to be reversed in purchase order acknowledgments so customers see the two data elements separately You may use flexfields to store the data elements separately to facilitate the purchase order acknowledgment transaction that requires two separate components OPERATION_CODE This code identifies that the transaction is to be inserted changed or deleted For new orders the appropriate code is INSERT Code conversion is permitted for this data element if a code is placed in the OPERATION_CODE_EXT1 field and the code is set up through the three code conversion forms in the e Commerce Gateway The valid values are INSERT UPDATE or DELETE DEFAULT The code is set to INSERT for this transaction by the e Commerce Gateway if a code is not provided in the transaction or not derived through code conversion This code is written to all the Order Import tables for the
10. Supplier Flexfiel ds Supplier Site Flexfiel ds Supplier Site Flexfiel ds Supplier Site Flexfiel ds Supplier Site Flexfiel ds Supplier Site Address Supplier Site Contact TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD PO PO PO PO PO PO PO PO PO 1090 1100 1110 1120 1130 1140 1150 1160 1170 A2 A2 A2 Al A2 A2 A2 AD CN SU2 SU3 SU4 SS1 SS2 SS3 SS4 SU1 SS1 Transaction Summary Layouts A 147 Data Trading Partner Ref1 Ref2 Ref3 PO LINE SHIPM ENT Record Number Record Layout Record Layout Qualifie r 26 27 28 29 30 31 32 33 34 35 Supplier Site Contact Ship to Address Code Ship to Contact s Bill to Address Code Bill to Contact Buyer Name Buyer Commu nication s Procure ment Card Header Attach ment Master Header Attach ment Detail TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD PO PO PO PO PO PO PO PO PO PO 1180 1190 1200 1210 1220 1230 1240 1250 1800 1810 CN AX CN AX CN PO PO PR AT AT SS2 ST1 ST1 BT1 BT1 PO4 PO5 CRD HAH HAD A 148 Oracle e Commerce Gateway Implementation Manual Data Trading Partner Ref 1 PO
11. The Inbound Purchase Order and Outbound Ship Notice Manifest transactions are based on the Oracle Process Manufacturing data model and should be treated as different transactions even though they share the same name as their respective transactions in Oracle Order Management Transaction List Available with Oracle Process Manufacturing X12 Trans EDIFACT Direction Description Base Oracle Message Application 850 ORDERS inbound Purchase Order into Oracle Process Manufacturing 855 ORDRSP outbound Purchase Order from Oracle Acknowledgmen Process t Manufacturing 856 DESADV outbound Ship from Oracle Notice Manifest Process Manufacturing Processing Traditional EDI Transactions Although Oracle e Commerce Gateway has evolved into an e business integrator it continues to be the hub for processing high volume traditional EDI transactions The following section describes how traditional EDI transactions are processed through Oracle e Commerce Gateway Interface Files between Oracle e Commerce Gateway and Any Translator ASCII files are passed between Oracle e Commerce Gateway and any Translator for traditional EDI transaction processing For inbound transactions the Translator copies the data from its position in the standard EDI transaction to its required position in the Oracle transaction interface file The reverse data mapping is done for outbound transactions Oracle e Commerce Gateway creates a transaction interface
12. e To minimize re mapping of existing data maps use a position number that will position this data element to the end of the record e Define a column width less than or equal what Oracle Applications supports to prevent data from being truncated e Review the sequence number of the other related external fields and assign a sequence number not already used by the other fields If you need to re sequence the existing external fields to accommodate the new external field make sure they are uniquely sequenced from 1 to 5 e Do not use sequence number 0 as it is reserved for the data element s internal value e Use the same layout code and qualifier as the other related external fields in the record e Assign a column rule for the external field as necessary Activate Unmapped Data Elements Similar to additional external fields for code conversion there are other Oracle e Commerce Gateway or Oracle Applications fields which were included in the transaction design but not mapped to the transaction interface file You can activate these unmapped fields to add new data elements to existing transactions by assigning the appropriate column attributes The guidelines are similar to those stated above for activating unmapped external fields for code conversion although these data elements are not limited to supporting code conversion requirements only Implementation Details 4 27 Extend Oracle e Commerce Gateway Supported Transactions Ora
13. loading program The data for the Order Import tables have the following sources e Data in the transaction from the trading partner or determined by the EDI Translator e Data derived or hard codes by the POI Program given the trading partner or the presence of data in the transaction 6 26 Oracle e Commerce Gateway Implementation Manual e Data derived by the Order Import process when it calls APIs to the Oracle tables The following is a list of the Order Management Open Interface required fields or other notations about the data elements These fields are required for the Order Management Open Interface Import program to successfully process and move the data from the Order Management Open Interface tables into the Oracle Order Management base application tables Required fields noted as derived or hard coded do not require a value in the transaction on the transaction interface file since the values are determined by the Oracle e Commerce Gateway process Refer to the Oracle Order Management User s Guide for details The following table shows sample columns from OE_HEADERS_INTERFACE table Sample Columns from the OE_HEADERS_INTERFACE Table Oracle Oracle Hardcoded Deri Record Number Position Applications e Commerce ved Number Column Name Gateway for Fields Column Name OPERATION _C OPERATION_C _ If Null default 1000 030 040 ODE ODE _EXT1 ot INSERT CUSTOMER_PO CUSTOMER PO Required by 1000 050 _NUMBER _NUMBER
14. 9 22 Oracle e Commerce Gateway Implementation Manual envelopes or functional groups by the sending Trading Partner Example of Separating Transactions into Different Electronic Envelopes or Functional Groups Sending Trading Sending EDI Sending EDI Receiving EDI Partner Translator Translator Translator Electronic Envelope Functional Group X12 ISA or X12 GS or UN EDIFACT UNB UN EDIFACT UNG Transaction with 123456789 900 Writes the data from Location this functional ABC A code in their group to file for application Organization A processing Transaction with 123456789 911 Writes the data from Location this functional ABC B code in their group to file for application Organization B processing Organizations in Oracle Application Open Interface Tables Even if transactions across all organizations could be loaded into the Application Open Interface tables by the Oracle e Commerce Gateway during one execution each application open interface has its own requirements about executing all organizations simultaneously or separately Some Application Open Interfaces may only allow transactions from a single organization in its Application Open Interface tables at one time while others may allow transactions across several organizations in the Application Open Interface tables Even if transactions across organizations could simultaneity reside on the Application Open Interface tables the Application Open Interface process ma
15. CREATED_BY CREATED_BY Derived LAST_UPDATE LAST_UPDATE Derived D_BY D_BY CREATION_DA CREATION_DA Set to SYSDATE TE TE LAST_UPDATE LAST_UPDATE Set to SYSDATE _DATE _DATE The following table shows the header level records for OE_PROCE_ADJS_INTERFACE Header Level Records for O0E_PROCE_ADJS_INTERFACE Oracle Oracle Hardcoded Deri Record Number Position Applications e Commerce ved Number Column Name Gateway for Required Column Name Fields ORIG_SYS_DOC ORIG _SYS_DOC Required 1800 010 UMENT_REF UMENT_REF ORIG_SYS_DIS ORIG_SYS_ Required 1800 030 OUNT_REF DISOUNT _REF OPERATION_C OPERATION_C _ If Null default 1800 040 050 ODE ORDER_SOURC E_ID LAST_UPDATE D_BY LAST_UPDATE _DATE ODE _EXT1 ORDER_SOURC E_ID LAST_UPDATE D_BY LAST_UPDATE _DATE to INSERT Hard code 6 meaning EDI Derived Set to SYSDATE Application Transaction Detail 6 33 Oracle Oracle Hardcoded Deri Record Number Position Applications e Commerce ved Number Column Name Gateway for Required Column Name Fields CREATION_DA CREATION_DA Set to SYSDATE TE TE CREATED_BY CREATED_BY Derived The following table shows the header level records for OE_LRESERVTNS_INTERFACE Header Level Records for O0E_RESERVTNS_INTERFACE Oracle Oracle Hardcoded Deri Record Number Position Applications e Commerce ved Number Column Name Gateway for Required Column Name Fields ORIG_SYS_DOC ORIG _SYS_DOC Req
16. Code Conversion 10 3 performed again using the remaining concatenated values This is performed until either a match is found or until all values are exhausted If a match is found using the external value s an internal value from the Code Conversion value table is written to the transaction interface file If a match is not found a null value is returned and the internal value copied to the external 1 field then written to the transaction interface file Code Conversion Windows There are three windows used in code conversion The purpose of each is summarized in the following table Purposes of Code Conversion Windows Code Conversion Windows Purpose Define Code Conversion Category Define a code conversion category that identifies a subset of code conversion values Indicates how many search keys will be examined during actual code conversion Assign Code Conversion Categories Enable code conversion for a data element in a given transaction Indicate the columns that have the code values to use in the search key Define Code Conversion Value Lists the actual code conversion values to cross reference the internal and 1 5 external codes Code Conversion Categories Window A code conversion category is a label for a set of entries in the code conversion table that contains the internal codes and external codes that you defined During code conversion only the code conversion table entries with the assigned category
17. GA GA GA BK4 BK5 SK1 SK2 SK3 SK4 SK5 VS1 A 98 Oracle e Commerce Gateway Implementation Manual Record TP_CD Ref 1 BATC H Ref 2 INVOIC E Ref 3 Record blank Number Record Layout Record Layout Qualifie r 26 27 28 29 30 31 32 33 Global PVS Flexfiel ds 5 9 Global PVS Flexfiel ds 10 14 Global PVS Flexfiel ds 15 19 Global PVS Flexfiel d 20 Bill To Internal Address VAT Registra tion Extensio n Tables Paymen t Data Remitta nce Inv oice Details TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD BATCH BATCH BATCH BATCH BATCH BATCH BATCH BATCH INVOIC E 1200 1210 1220 1230 1240 1250 1900 2000 GA GA GA GA AX VA custom VS2 VS3 VS4 VS5 PY TAX custom INV Transaction Summary Layouts A 99 Record TP_CD Ref 1 Ref 2 Ref 3 Record Record Record BATC INVOIC blank Number Layout Layout H E Qualifie r 34 Remitta TP_CD BATCH INVOIC 2010 Al RE1 nce E Advice Flexfiel ds 1 4 35 Remitta TP_CD BATCH INVOIC 2020 Al RE2 nce E Advice Flexfiel ds 5 9 36 Remitta TP_CD BATCH INVOIC 2030 Al RE3 nce E Advice Flexfiel ds 10 14 37 Remitta TP_CD BATCH INVOIC 2040 Al RE4 nce E Advice Flexfiel d15 38 Global TP_CD BATCH INVOIC 2050 GA IN1 INV E Flexfiel ds 1 4 39 Global TP_CD BATCH INVOIC 2060 G
18. Know the Required Fields and Default Data Know the required fields in the transaction interface file and the application open interface and know the defaults defined in the Oracle e Commerce Gateway for the transaction The open interface tables require certain fields to be populated to properly process the incoming data Because it is not known whether the data is available on the source system a default value can be used so that processing can continue Required fields and default values are dependent on how the application is configured to handle keyboard entry in setup It is also very important that the base application is set up with the data that it is expecting Other Application Implementations Translators For standard transactions an e Commerce environment must be installed Generally the following must be done in the Translator specifically and the e Commerce environment generally This document does not discuss the detail of installing Translators or the operation of Translators Each company must install a Translator to processes traditional standard transactions such as ASC X12 transactions and EDIFACT messages They must review its system requirements and its integration requirements with the Oracle e Commerce Gateway The ability to configure the Translator to suit different formats is also a consideration to facilitate any changes that may be required from updates to the Oracle e Commerce Implementation Positioning
19. Ref 2 LINE Ref 3 Record SHIPM Number ENT Record Layout Record Layout Qualifie r 36 37 38 39 40 41 42 43 44 Basic Item Data Basic Item Data Basic Item Data Hazard ous Material Codes Item Note to Supplier Line Flexfiel ds Line Flexfiel ds Line Flexfiel ds Line Flexfiel ds Line Part Flexfiel ds TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD PO PO PO PO PO PO PO PO PO LINE LINE LINE LINE LINE LINE LINE LINE LINE 2000 2010 2020 2030 2040 2050 2060 2070 2080 IT IT IT IT A1 A2 A2 A2 A1 IT1 IT2 IT3 IT4 LN1 LN2 LN3 LN4 LP1 Transaction Summary Layouts A 149 Data Trading Partner Ref 1 PO Ref2 Ref3 LINE SHIPM ENT Record Number Record Layout Record Layout Qualifie r 45 46 47 48 49 50 51 52 A 150 Oracle e Commerce Gateway Implementation Manual Line Part Flexfiel ds Line Part Flexfiel ds Line Part Flexfiel ds Line Part Segmen ts Line Part Segmen ts Line Attach ment Master Line Attach ment Detail Master Item Attach ment Master TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD PO PO PO PO PO PO PO PO LINE LINE LINE LINE LINE LINE LINE
20. Required Line Number Optional Line Order Quantity Line UOM Line Attribute 1 Line Attribute 2 Transaction Record ID 4 Transaction Record ID Determine Table Ownership Since database tables may only be altered either by their owner or by a user that has been granted this privilege it is necessary to determine the owner or schema for the extension table By default all Oracle ee Commerce Gateway tables are owned by the user EC when the Oracle Applications are installed while the APPS user is usually created as a privileged account To verify the owner of the extension table type the following from any SQL Plus session SQL gt select owner from all_tables wher table name ECE PO INTERFACE LINES X OWNER EC 1 row selected Add Columns to Extension Table To add the desired columns to the extension table log into SQL Plus either as the owner in this case the user EC or as a privileged user such as APPS and type the following SQL gt alter table EC ECE_PO INTERFACE LINES X add Material Analyst Code VARCHAR 30 Material Analyst Last Name VARCHAR2 40 L Material Analyst First Name VARCHAR2 20 Material Analyst Phone VARCHAR2 30 Material Analyst Email VARCHAR2 30 Table altered The new extension table structure can be verified by typing the following 11 8 Oracle e
21. Ship to EDI_ LOCATION CODE Use a plus sign between these fields to improve readability Alternative Original System Shipment Reference If your trading partner can retain unique shipment numbers to identify the shipment level shipment schedule dates ship to locations data in their purchasing application the shipment number may be copied into the ORIG_SYS_SHIPMENT_RFF field in the transaction file If you maintain the same coding convention for the three original reference fields for both the inbound purchase order and the inbound purchase order change the change order process can match the order data in the base Order Management tables It is assumed that you will only modify the shipment records that changed and add Application Transaction Detail 6 19 shipment records that were not already present In another scenario the trading partner may send all the shipment records even shipment records with no changes for your review if you cannot accurately match the shipment records from the purchasing application Sample Original System Shipment Reference Original System Shipment Reference 6 Shipment Number You copied from the transaction 6 The following table is a sample of all Original System Data using Shipment Numbers Sample Original System Data Using Shipment Numbers LEVEL Data Element Content Sample Note Header Original System Purchase Order 86420 03 the default Number Document Reference Release
22. Structure Record Numbers Control Record 0010 Ship Notice Manifest Header 1000 1900 Item Detail 2000 2900 LPN ContentsiLot amp Serial 4000 An Inbound Ship Notice Manifest transaction contains a single Control Record and Ship Notice Manifest Header Record The header record may have multiple Item Detail Records The Item Detail record may have multiple LPN Contents Lot and Serial Records This structure is further described in the table below The following table shows the content and occurrences of the records comprising the Inbound Ship Notice Manifest transaction Record Occurrences Within the ASNI Transaction Records Content Occurrences 0010 Control Record Only one record occurrence per transaction 1000 1900 Shipment Notice Header Only one record occurrence Records per transaction 2000 3900 Shipment Notice Item One set of records per item Records within the Shipment Notice header 4000 License Plate Information One set of records per item within the Shipment Notice Header The following table is a summary list of the records that comprise the Inbound Ship Notice Manifest transaction The table shows the functional data grouping of records the data level the record numbers and relevant notes about the data grouping A 118 Oracle e Commerce Gateway Implementation Manual ASNI Transaction Record Summary Type of Data Data Level RECORD Note 1 Control Record HEADER 0010 2 Shipment Notice HEADER
23. TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD PO PO PO PO PO PO PO PO A 42 Oracle e Commerce Gateway Implementation Manual 1090 1100 1110 1200 1210 1220 1230 1240 FB NT MS A1 A2 A2 A2 A1 SHP SHP MIS HD1 HD2 HD3 HD4 PO1 Sequen Data Trading Ref 1 Ref 2 Ref 3 Record Record Record ce Partner Number Layout Layout Qualifie r 18 Purchas TP_CD PO 1250 A2 PO2 e Order Flexfiel ds 5 9 19 Purchas TP_CD PO 1260 A2 PO3 e Order Flexfiel ds 1 14 20 Purchas TP_CD PO 1270 A2 PO4 e Order Flexfiel d15 21 Global TP_CD PO 1280 Al GL1 Flexfiel ds 1 4 22 Global TP_CD PO 1290 A2 GL2 Flexfiel ds 5 9 23 Global TP_CD PO 1300 A2 GL3 Flexfiel ds 10 14 24 Global TP_CD PO 1310 A2 GL4 Flexfiel ds 15 19 25 Global TP_CD PO 1320 A2 GL5 Flexfiel d 20 26 Custom TP_CD PO 1400 CU CUS er Name amp Number Transaction Summary Layouts A 43 Sequen ce Data Trading Partner Ref 1 Ref 2 Ref 3 Record Number Record Record Layout Layout Qualifie r 27 28 29 30 31 32 33 34 35 Sold to Address header level Sold to Contact header level Ship to Address header level Ship to Contact header level Invoice Address header level Invoice Contact header level Ordered By Name Ship fro m Address Credits Data TP_CD TP
24. e Which code conversion sets are to be used for the transaction for the trading partner e Communication method e Communication service provider The Oracle e Commerce Gateway requires the Translator s identification code for its trading partner definition in the transaction interface file on the Control Record 0010 It is defined at the Translator Code in the trading partner setup in the Trading Partner Detain tab in the Trading Partner setup Code Conversion Like the Oracle e Commerce Gateway Translators provide for code conversion between the value defined in the base Oracle Application and the values required by the EDI standard or the trading partner Code conversion is performed on specific data elements You can use the Oracle e Commerce Gateway for some data elements and the Translator on other data elements You should decide where it is most efficient for your implementations bearing in mind how easy it will be in the future to add edit or delete conversions in the Oracle e Commerce Gateway or the Translator 2 4 Oracle e Commerce Gateway Implementation Manual Data Mapping Review the Oracle e Commerce Gateway transaction interface files and the EDI standard transaction to determine where the data is positioned in the EDI standard transaction If transaction data maps already exist they provides a good starting point since the standard transaction portion of the data map can be copied from the existing data map You wi
25. 1 Ref 2 Ref 3 Record Record Record Partner Invoice Item blank Number Layout Layout Qualifie r 21 Invoice TP_CD INVOIC ITEM 4030 A2 IT4 Line E Flexfiel d15 22 Invoice TP_CD INVOIC ITEM 4100 Al IG1 Line E Global Flexfiel ds 1 4 23 Invoice TP_CD INVOIC ITEM 4110 A2 IG2 Line E Global Flexfiel ds 5 9 24 Invoice TP_CD INVOIC ITEM 4120 A2 IG3 Line E Global Flexfiel ds 10 14 25 Invoice TP_CD INVOIC ITEM 4130 A2 IG4 Line E Global Flexfiel ds 15 19 26 Invoice TP_CD INVOIC ITEM 4140 A2 IG5 Line E Global Flexfiel d 20 27 Extensio TP_CD INVOIC ITEM 4900 Custo n E m Tables Item A 78 Oracle e Commerce Gateway Implementation Manual Inbound Shipment and Billing Notice SBNI 857 No EDIFACT A single transaction has the following data hierarchy and data looping SBNI Inbound Ship Notice Billing Structure Record Numbers Control Record 0010 Ship Notice Billing Header 1000 1900 Item Detail 2000 3900 Item Detail 2000 3900 Item Detail 2000 3900 An Inbound Shipment and Billing Notice transaction contains a single Control Record and Ship Notice Billing Header The header record may have multiple Item Detail Records This structure is further described in the table below The following table shows the content and occurrences of the records comprising the Inbound Shipment and Billing Notice transaction Record occurrences within the transaction Records Content Occurrences 0010 Con
26. 5 9 Purchase TP_CD PO 1260 A2 PO3 Order Flexfields 1 14 Purchase TP_CD PO 1270 A2 PO4 Order Flexfield 15 Global TP_CD PO 1280 Al GL1 Flexfields 1 4 Transaction Summary Layouts A 19 Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner Number Layout Layout Qualifier Global TP_CD PO 1290 A2 GL2 Flexfields 5 9 Global TP_CD PO 1300 A2 GL3 Flexfields 10 14 Global TP_CD PO 1310 A2 GL4 Flexfields 15 19 Global TP_CD PO 1320 A2 GL5 Flexfield 20 Customer TP_CD PO 1400 CU CUS Name amp Number Sold to TP_CD PO 1410 AD SLD Address header level Sold to TP_CD PO 1420 CN SLD Contact header level Ship to TP_CD PO 1500 AD ST1 Address header level Ship to TP_CD PO 1510 CN ST1 Contact header level A 20 Oracle e Commerce Gateway Implementation Manual Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner Number Layout Layout Qualifier Invoice TP_CD PO 1520 AD BT1 Address header level Invoice TP_CD PO 1530 CN BT1 Contact header level Ordered TP_CD PO 1540 CN OBY By Name Ship fro TP_CD PO 1600 AD SFM m Address Credits TP_CD PO 1700 CR CRD Data Credit TP_CD PO 1710 Al CR1 Flexfields 1 4 Credit TP_CD PO 1720 A2 CR2 Flexfields 5 9 Credit TP_CD PO 1730 A2 CR3 Flexfields 10 14 Credit TP_CD PO 1740 A2 CR4 Flexfield 15 Price TP_CD PO 1800 PR ADJ Adjustme nts Data Transaction Summary Layouts A 21 Data Trading Re
27. 53 54 55 56 57 58 59 60 Master Item Attach ment Detail Inventor y Item Attach ment Header Inventor y Item Attach ment Detail Basic Shipme nt Data Shipme nt Flexfiel ds Shipme nt Flexfiel ds Shipme nt Flexfiel ds Shipme nt Flexfiel ds TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD PO PO PO PO PO PO PO PO LINE LINE LINE LINE LINE LINE LINE LINE SHIPM ENT SHIPM ENT SHIPM ENT SHIPM ENT SHIPM ENT 2830 2840 2850 3000 3010 3020 3030 3040 AT AT AT SH Al A2 A3 A4 MAD IAH IAD SH1 SH1 SH2 SH3 SH4 A 166 Oracle e Commerce Gateway Implementation Manual Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner PO ITEM SHIPM Number Layout Layout ENT Qualifie r 61 Ship To TP_CD PO LINE SHIPM 3050 AX SL1 Address ENT Code 62 Ship To TP_CD PO LINE SHIPM 3060 CN SL1 Contact ENT 63 Shipme TP_CD PO LINE SHIPM 3800 AT SAH nt ENT Attach ment Header 64 Shipme TP_CD PO LINE SHIPM 3810 AT SAD nt ENT Attach ment Detail 65 Distribu TP_CD PO LINE SHIPM 4000 DS DIS tions ENT Data DISTRI BUTIO NS 66 Deliver TP_CD PO LINE SHIPM 4100 AD DST y ENT Address DISTRI BUTIO NS 67 Deliver TP_CD PO LINE SHIPM 4110 CN DST y ENT Contact DISTRI BUTIO NS Transaction Summary Layouts A 167 Data Trading Ref 1 Ref
28. 65 Distribu TP_CD PO LINE SHIPM 4000 DS DIS tions ENT Data DISTRI BUTIO NS 66 Deliver TP_CD PO LINE SHIPM 4100 AD DST y ENT Address DISTRI BUTIO NS 67 Deliver TP_CD PO LINE SHIPM 4110 CN DST y ENT Contact DISTRI BUTIO NS A 152 Oracle e Commerce Gateway Implementation Manual Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner PO LINE SHIPM Number Layout Layout ENT Qualifie r 68 Distribu TP_CD PO LINE SHIPM 4200 Al DS1 tions ENT Flexfiel DISTRI ds BUTIO NS 69 Distribu TP_CD PO LINE SHIPM 4210 A2 DS2 tions ENT Flexfiel DISTRI ds BUTIO NS 70 Distribu TP_CD PO LINE SHIPM 4220 A2 DS3 tions ENT Flexfiel DISTRI ds BUTIO NS 71 Distribu TP_CD PO LINE SHIPM 4230 A2 DS4 tions ENT Flexfiel DISTRI ds BUTIO NS Outbound Purchase Order Changes POCO 860 ORDCHG A single transaction has the following data hierarchy and data looping Transaction Summary Layouts A 153 POCO Outbound Purchase Order Change Structure Control Record Purchase Order Header Header Attachment Header Header Attachment Detail Line Line Attachment Header Line Attachment Detail Master Item Attachment Header Master Item Attachment Detail Inventory Attachment Header Inventory Attachment Detail Shipments Shipment Attachment Header Shipment Attachment Detail Distributions Record Number 0010 1000 1800 1810 2000 2130 2800 2810 2820 2830 2840 2850
29. A2 Al A2 A2 A2 SO2 SO3 SO4 SI1 SI2 SIS SI4 A 242 Oracle e Commerce Gateway Implementation Manual Data Trading Partner Ref1 Ref2 Ref3 PS ITEM SCHE DULE Record Record Number Layout Record Layout Qualifie r 62 Extensio n Tables Item Level 63 Forecast Dates Authori zation Receipt Data 64 Extensio n Tables Forecast Level TP_CD TP_CD TP_CD PS ITEM PS ITEM SCHED ULE PS ITEM SCHED ULE 2900 Custo m 4000 SC 4900 Custo m Custo m SCH Custo m Outbound Shipping Schedule SSSO 862 DELJIT The following table shows the content and occurrences of the records comprising the Outbound Shipping Schedule transaction Record occurrences Within the SSSO Transaction Records Content Occurrences 0010 Control Records Only one record occurrence per transaction 0020 0070 Gateway Flexfields One set of records per transaction 1000 1900 Header Records Only one record occurrence per transaction Transaction Summary Layouts A 243 Records Content Occurrences 2000 2900 Item Records One set of records per item within the Shipping Schedule header 4000 4900 Authorization Forecast One records per forecast Schedule schedule authorization or receipt data per item The following table is a summary list of the records that comprise the Outbound Shipping Schedule transaction The table shows the functio
30. Cross Referencing in Oracle Inventory Inventory Item Cross Reference table is accessed to validate the generic item and derive its corresponding internal inventory item The derived Inventory Item is compared to the Inventory Item in the transaction If the derived and the sent Inventory Item do not match an error message is generated where the sent inventory item is displayed in the error 1 In all cases where more than one table entry is retrieved during the table search an error message is created 2 In all cases where the derived inventory item from the table search and the inventory item found in the transaction do not match the derived inventory item replaces the sent inventory item in the Order Import tables and the inventory item from the transaction is shown in the error message Results of Item Cross Referencing on the Sales Order If the customer item generic inventory item to supplier inventory item cross referencing is successful and the supplier inventory item validation is successful the proper item data is moved to the following fields in the sales order in Order Management The following table shows results of a cross referenced sales order The first column shows the data from the transaction and the second column shows the data passed to the base Orders tables 6 60 Oracle e Commerce Gateway Implementation Manual Data in the transaction In the Order passed to the base Orders tab
31. Custom Custom Production Sequence PSQI 866 NA A single transaction has the following data hierarchy and data looping A 216 Oracle e Commerce Gateway Implementation Manual PSQI Production Sequence Schedule Inbound Control Record Production Sequence Schedule Header item Line Detail _ subline Details Record Numbers 0010 1000 1900 2000 2900 3000 3900 4000 4900 An Inbound Production Sequence Schedule transaction contains a single Control Record and Production Sequence Schedule Header The header record can have multiple Item Records which can have multiple Line Detail Records which can have multiple Subline Detail Records This structure is further described in the table below The following table shows the content and occurrences of the records comprising the Inbound Production Sequence Schedule Record Occurrences Within the PSQI Transaction Records 0010 0070 1000 1900 2000 2900 3000 3900 4000 4900 CONTENT Control Record Header Records Date and Defaults Item Records within Date Subline Item Records within Item OCCURRENCES Only one record occurrence per transaction Only one record occurrence per transaction Date and defaults applicable to subsequent details One set of items and related data per date One optional set of subline records within configuration details The following table is a summary list of the records that comprise the
32. Flexfiel ds 3 Trading TP_CD PO 0030 A2 TH2 Partner Header Flexfiel ds 4 Trading TP_CD PO 0040 A2 TH3 Partner Header Flexfiel ds 5 Trading TP_CD PO 0050 A2 TH4 Partner Header Flexfiel ds 6 Trading TP_CD PO 0060 Al TD1 Partner Detail Flexfiel ds 7 Trading TP_CD PO 0070 A2 TD2 Partner Detail Flexfiel ds Transaction Summary Layouts A 145 Data Trading Partner Ref1 Ref2 Ref3 PO LINE SHIPM ENT Record Number Record Layout Record Layout Qualifie r 10 11 12 13 14 15 16 Purchas e Order Basic Header Paymen t Terms Purchas e Order Basic Header Purchas e Order Notes to Supplier Purchas e Order Flexfiel ds Purchas e Order Flexfiel ds Purchas e Order Flexfiel ds Purchas e Order Flexfiel ds Supplier Flexfiel ds TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD PO PO PO PO PO PO PO PO PO 1000 1010 1020 1030 1040 1050 1060 1070 1080 PO PO PO PO Al A2 A2 A2 Al POI PO2 PO3 PO3 POI PO2 PO3 PO4 SU1 A 146 Oracle e Commerce Gateway Implementation Manual Data Trading Partner Ref1 Ref2 Ref 3 PO LINE SHIPM ENT Record Number Record Record Layout Layout Qualifie r 17 18 19 20 21 22 23 24 25 Supplier Flexfiel ds Supplier Flexfiel ds
33. Flexfields 7 Bill to Site HEADER 1060 1090 Flexfields Flexfields 8 Ship to HEADER 1100 Address Code 9 Ship to Misc HEADER 1110 1115 Data Contacts 10 Sold to HEADER 1200 Address Code 11 Sold to Misc HEADER 1210 1215 data Contact 12 Remit to HEADER 1300 1315 Address Code 13 Ship From Codes HEADER 1400 A 186 Oracle e Commerce Gateway Implementation Manual Data Data Level Record Number Note 14 Basic Invoice HEADER 2000 Header Data 15 Invoice Misc HEADER 2010 2020 Data 16 Shipment Data HEADER 2030 17 Currency Data HEADER 2040 Misc Data 18 Payment Terms HEADER 2050 Data 19 Sales HEADER 2060 Representative Comments 20 Invoice Header HEADER1 3000 3030 Flexfields Flexfields 21 Invoice Header HEADER1 3040 3070 Flexfields Interface Flexfields 22 Equipment Data HEADER1 3075 23 Header ALLOWANCE 3080 3090 Allowance Char CHARGES ges HEADER 24 Header ALLOWANCE 3091 3094 Flexfields Allowance Char CHARGES ges Flexfields HEADER 25 Extension ALLOWANCE 3900 Custom Tables Invoice CHARGES Header Data HEADER 26 Basic Line Data LINE 4000 Transaction Summary Layouts A 187 Data Data Level Record Number Note 27 Sales Order LINE 4010 Data Part Descriptions 28 Sales Channel LINE 4020 29 Order Status LINE 4030 Transaction Reference Key 30 Interface Line LINE 5000 5030 Flexfields Flexfields 31 Line Flexfields LINE 5040 5070 Flexfields 32 Line Part LINE 5100 5130 Flexfields Flexfields 34 TP Head
34. From this window users can select documents that have rule exceptions and resubmit after the errors have been resolved or delete the documents This window consists of two major components The left side shows the transactions in a tree format and the right side shows the corresponding selected level summary The Summary shows different information depending on the tree node that is selected The tree data is only a snapshot of the staging table Users need to Refresh the view to see any new modified data in the staging table Two functions are available from this window The Resubmit function allows the users to resubmit the given set of documents or a single document to be processed again through the inbound process after errors have been corrected For example users can select IN Invoice 810 INVOIC and use the resubmit function In this case the inbound process will revalidate all the Invoices that have a status of Skip Document The status will be changed to Reprocess and a concurrent request is submitted to process the documents Also the tree is refreshed with new data The Delete function enables users to delete the given set of documents or a single document and the corresponding rule exceptions For example users can select Trading Partner Alpha and use the Delete function In this case it deletes all of the invoices that have a status of Skip Document for Trading Partner Alpha After deleting the documents the document tree is re
35. INVOIC E INVOIC LINE E INVOIC LINE E 3092 3093 3094 3900 4000 4010 AH AH AH IT IT TH2 IH3 IH4 Custo IT1 IT2 A 196 Oracle e Commerce Gateway Implementation Manual Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner INVOIC ITEM TAX Number Layout Layout E Qualifie r 52 Sales TP_CD INVOIC_ LINE 4020 IT IT3 Channel E Order Status 53 Transact TP_CD INVOIC LINE 4030 IT IT4 ion E Referen ce Key Order Status 54 Interfac TP_CD INVOIC LINE 5000 Al IL1 e Line E Flexfiel ds 1 4 55 Interfac TP_CD INVOIC LINE 5010 A2 IL2 e Line E Flexfiel ds 5 9 56 Interfac TP_CD INVOIC LINE 5020 A2 IL3 e Line E Flexfiel ds 10 14 57 Interfac TP_CD INVOIC LINE 5030 A2 IL4 e Line E Flexfiel d15 58 Line TP_CD INVOIC_ LINE 5040 Al LN1 Flexfiel E ds 1 4 59 Line TP_CD INVOIC_ LINE 5050 A2 LN2 Flexfiel E ds 5 9 Transaction Summary Layouts A 197 Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner INVOIC ITEM TAX Number Layout Layout E Qualifie r 60 Line TP_CD INVOIC LINE 5060 A2 LN3 Flexfiel E ds 10 14 61 Line TP_CD INVOIC LINE 5070 A2 LN4 Flexfiel E d15 62 Line TP_CD INVOIC LINE 5100 Al LP1 Part E Flexfiel ds 1 4 63 Line TP_CD INVOIC LINE 5110 A2 LP2 Part E Flexfiel ds 5 9 64 Line TP_CD INVOIC LINE 5120 A2 LP3 Part E Flexfiel ds 10 14 65 Line TP_CD INVOIC_ LINE 5130 A2 LP4 Part E Flexfiel d15 66 TP TP_CD INVOIC LINE 5140 A2 HT1 Hea
36. If you chose to update Oracle Applications data or change the erroneous entries using the Open Interface Invoices window in Payables you can resubmit the Payables Open Interface Import process to re validate the transaction 6 86 Oracle e Commerce Gateway Implementation Manual If you chose to have the supplier send a corrected transaction you must first purge the rejected invoice data in the Payables Open Interface tables by submitting the Purge Payables Open Interface program and then re import the updated transaction using Oracle e Commerce Gateway Inbound Shipment and Billing Notice SBNI 857 No EDIFACT Refer to the Oracle Purchasing section page 6 95 for details regarding this transaction Outbound Application Advice ADVO 824 APERAK Trading Partner Link to Oracle e Commerce Gateway Suppliers and supplier sites are defined in either Oracle Purchasing or Oracle Payables Included in the definition is the EDI Location Code that trading partners agree to exchange to represent the full detailed address Often they do not send the full address but just the EDI Location Code This is a critical data field to Oracle e Commerce Gateway The EDI Location Code is the link between a supplier supplier site in Oracle Applications and the trading partner site definition in Oracle e Commerce Gateway This enables Oracle e Commerce Gateway to access the detailed data about the supplier or supplier site in the base Oracle Applications without
37. In that case a Confirmed Receipt must be performed LOT_NUMBER This column identifies the Lot Number of the material shipped If this number violates the lot uniqueness constraints lot information will not be imported and a Confirmed Receipt must be performed FROM_SERIAL_ NUMBER TO_SERIAL_NUMBER The two columns identify the serial numbers shipped If the serial numbers violate the serial uniqueness constraints serial information will not be imported and a Confirmed Receipt must be performed QUANTITY This column represents the quantity of material packed on this LPN UOM_CODE_INT This column represents the internal UOM code defined in Oracle Applications UOM_CODE_EXT1 EXT5 These columns represent the external UOM code found in the transaction if code conversion is defined as such Outbound Application Advice ADVO 824 APERAK Refer to the Oracle Payables section page 6 64 for details regarding this transaction Outbound Purchase Order POO 850 ORDERS Trading Partner Link to Oracle e Commerce Gateway Suppliers and supplier sites are defined in either Oracle Purchasing or Oracle Payables Included in the definition is the EDI Location Code that trading partners agree to exchange to represent the full detailed address Often they do not send the full address but just the EDI Location Code This is a critical data field to Oracle e Commerce Gateway The EDI Location Code is the link between a supplier supplier site
38. Item Level Ship to TP_CD Contact Item Level Invoice to TP_CD Contacts Trading TP_CD Partner Flexfields 1 4 Trading TP_CD Partner Flexfields 5 9 Ref 1 PO PO PO PO PO PO PO PO PO Ref 2 LINE LINE LINE LINE LINE LINE LINE LINE LINE Ref 3 Record Number 4700 4710 4720 4730 4800 4810 4820 4830 4840 Record Layout Al A2 A2 A2 AD CN CN Al A2 Record Layout Qualifier RT1 RT2 RT3 RT4 ST1 ST1 IND TP1 TP2 A 28 Oracle e Commerce Gateway Implementation Manual Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner Number Layout Layout Qualifier Trading TP_CD PO LINE 4850 A2 TP3 Partner Flexfields 10 14 Trading TP_CD PO LINE 4860 A2 TP4 Partner Flexfield 15 Ship fro TP_CD PO LINE 4870 AD SFR m Address Item Level Credits TP_CD PO LINE 5000 CR CRD Data Credit TP_CD PO LINE 5100 Al CR1 Flexfields 1 4 Credit TP_CD PO LINE 5110 A2 CR2 Flexfields 5 9 Credit TP_CD PO LINE 5120 A2 CR3 Flexfields 10 14 Credit TP_CD PO LINE 5130 A2 CR4 Flexfield 15 Price TP_CD PO LINE 6000 PR ADJ Adjustme nts Data Discount TP _CD PO LINE 6010 PR AD1 List Names Transaction Summary Layouts A 29 Data Price Adjustme nt Flexfields 1 4 Price Adjustme nt Flexfields 5 9 Price Adjustme nt Flexfields 10 14 Price Adjustme nt
39. LINE 2090 2100 2110 2120 2130 2800 2810 2820 A2 A2 A2 PS PS AT AT AT LP2 LP3 LP4 PS1 PS2 LAH LAD MAH Data Trading Partner Ref 1 PO Ref 2 LINE Ref 3 SHIPM ENT Record Number Record Record Layout Layout Qualifie r 53 54 55 56 57 58 59 60 Master Item Attach ment Detail Inventor y Item Attach ment Master Inventor y Item Attach ment Detail Basic Shipme nt Data Shipme nt Flexfiel ds Shipme nt Flexfiel ds Shipme nt Flexfiel ds Shipme nt Flexfiel ds TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD PO PO PO PO PO PO PO PO LINE LINE LINE LINE LINE LINE LINE LINE SHIPM ENT SHIPM ENT SHIPM ENT SHIPM ENT SHIPM ENT 2830 2840 2850 3000 3010 3020 3030 3040 AT AT AT SH A1 A2 A2 A2 MAD IAH IAD SH1 SH1 SH2 SH3 SH4 Transaction Summary Layouts A 151 Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner PO LINE SHIPM Number Layout Layout ENT Qualifie r 61 Ship To TP_CD PO LINE SHIPM 3050 AX SL1 Address ENT Code 62 Ship To TP_CD PO LINE SHIPM 3060 CN SL1 Contact ENT 63 Shipme TP_CD PO LINE SHIPM 3800 AT SAH nt ENT Attach ment Master 64 Shipme TP_CD PO LINE SHIPM 3810 AT SAD nt ENT Attach ment Detail
40. MVSTO Transaction Record Summary Data Data Level Record Number Note 1 Control Record HEADER 0010 2 Trading Partner HEADER 0020 0050 Custom Header Flexfields 3 Movement Type HEADER 1000 Status Period 4 Legal Entity HEADER 1010 Address 5 Total Units HEADER 1020 Records amp Weight Transaction Summary Layouts A 3 Data Data Level Record Number Note 6 Nature of DETAIL 2000 Transaction Mov ement 7 Post Area Zone DETAIL 2010 Code 8 Currency Cost DETAIL 2020 Price 9 Transaction Qty DETAIL 2030 UOM Weight 10 Commodity DETAIL 2040 Code Descriptio n 11 Item DETAIL 2050 Description Comments 12 Document DETAIL 2060 Source Reference 13 Shipment Receip DETAIL 2070 t Reference Container 14 Invoice DETAIL 2080 Date Reference Qty 15 Bill to Address DETAIL 2090 16 Vendor DETAIL 2100 Name Site 17 Movement DETAIL 2200 2230 Flexfields Flexfields 18 Bill to Address LOCATION 3000 A 4 Oracle e Commerce Gateway Implementation Manual Data Data Level Record Number Note 19 Ship to Address LOCATION 3010 20 Vendor Address LOCATION 3020 The following table shows the Common Key positions 1 100 for the Outbound Movement Statistics transaction The table shows the position length code and content of the Common Key elements Transaction specific Data in the Common Key of the MVSTO transaction Position Length Code Content 1 25 25 TP_CD Trading Partner Code as define
41. Oracle Applications supports two forms of Electronic Funds Transfer EFT The first is directly from Oracle Payables via a Payables created payment file that is sent to the bank for disbursement directly into the supplier s bank account Refer to the Creating Electronic Funds Transfer Payments without the Oracle e Commerce Gateway section Oracle Payables User s Guide for details The second form of EFT is via the Oracle e Commerce Gateway outbound Payment Order Remittance Advice 820 PAYORD REMADV 820 PAYEXT REMADV transaction PAYORD PAYEXT PAYMUL The EDIFACT PAYORD message is for payments to a single supplier The EDIFACT PAYEXT message is for payments to multiple suppliers The EDIFACT PAYMUL message is for multiple currency payment batches Oracle Payables does not support this feature Pre note Payment You can set up a pre note payment by creating a zero dollar invoice Select Allow Zero Invoices when you create the payment batch to include this invoice Your disbursement bank will process this pre note payment to verify the accuracy of the payer and payee bank account data Transaction Handling Options The outbound Payment Order Remittance Advice transaction is designed to accommodate both the payment and associated invoice data With a single transaction you can instruct your disbursement bank to do one of the following e Disburse funds directly to the supplier s bank account and process the remittance Applicatio
42. Regardless of how you set the Transaction Handling code Oracle e Commerce Gateway will construct the entire file so your disbursement bank has everything it needs If your supplier cannot receive an electronic remittance advice a hard copy may be printed using Oracle Payables and sent to the supplier Trading Partner Link to Oracle e Commerce Gateway Bank branch data for the disbursement bank is defined in Oracle Payables Included in the definition is the EDI Location Code that trading partners agree to exchange to represent the full detailed address Often they do not send the full address but just the EDI Location Code This is a critical data field to Oracle e Commerce Gateway The EDI Location Code is the link between a bank branch in Oracle Payables and the trading partner site bank branch definition in Oracle e Commerce Gateway This enables Oracle e Commerce Gateway to access the detailed data about the bank branch in the Oracle Payables without maintaining the detail data in Oracle e Commerce Gateway To ensure that the trading partner link between Oracle e Commerce Gateway and Oracle Payables is set up properly verify that the bank branch and the EDI Location Code in Oracle Payables is the correct bank branch selected for the Trading Partner definition in Oracle e Commerce Gateway The selected bank branch and the EDI Location Code defined in Oracle Payables are displayed in the Define Trading Partners window Assignment tab If
43. See below for details on how to set up this transaction PAYORD PAYEXT PAYMUL The EDIFACT PAYORD message is for payments to a single supplier The EDIFACT PAYEXT message is for payments to multiple suppliers The EDIFACT PAYMUL message is for multiple currency payment batches Oracle Payables does not support this feature Pre note Payment You can set up a pre note payment by creating a zero dollar invoice Select Allow Zero Invoices when you create the payment batch to include this invoice Your disbursement bank will process this pre note payment to verify the accuracy of the payer and payee bank account data Transaction Handling Options The outbound Payment Order Remittance Advice transaction is designed to accommodate both the payment and associated invoice data With a single transaction you can instruct your disbursement bank to do one of the following e Disburse funds directly to the supplier s bank account and process the remittance advice e Disburse funds directly to the supplier s bank account do nothing with the remittance advice e Send remittance advice electronically to the supplier do nothing with the payment e Disburse funds directly to the supplier s bank account and send remittance advice to the supplier electronically You indicate your instructions to the disbursement bank by setting the Transaction Application Transaction Detail 6 89 Handling code when you define your supplier or supplier sites
44. Select an operating unit for the Trading Partner Group Enter a new Trading Partner name or position your cursor on an existing Trading Partner name Select the appropriate New or Open button All Trading Partners within the group are all associated with the specified operating unit defined for the 4 28 Oracle e Commerce Gateway Implementation Manual group 2 Define Trading Partner Assignment From the Define Trading Partner window select the Assignment tab Select the name and site from the list of values Only the names and sites from the operating unit specified in the Trading Partner Groups window are presented in the list of values When multiple operating units are associated with your responsibility if you want to associate a different set of addresses for the same Trading Partner group and same Trading Partner then you have to reselect the operating unit in the Trading Partner Groups form first and then change the setup for the underlying Trading Partners This way the associated Trading Partner addresses of another operating unit can be viewed for selection when defining Trading Partners for the group The operating unit is relevant to the underlying addresses only and not to the Trading Partner groups or Trading Partner headers The EDI Location Code is returned from the base Oracle Application where the site is defined 3 Define Trading Partner Details From the Define Trading Partner window select the Details tab Ent
45. Site address data is used within EDI transactions for instance as a ship to address or a bill to address Each Trading Partner address site in Oracle Applications to be used in EDI transactions should have an EDI Location Code assigned to it in the base application The EDI Location Code represents the customer address supplier site or bank branch full address It is typically a code in the EDI transaction in the X12 N104 segment or in the EDIFACT NAD segment it may also be a made up code according to any existing or agreed naming conventions The EDI Location Code is part of the address entities set up in the Oracle Application The Oracle e Commerce Gateway derives the column ID for the full address stored in Oracle Receivables Oracle Payables or HR Locations given the EDI Location Code and Translator Code found in the Oracle e Commerce Gateway Trading Partner windows see below The EDI Location Code is displayed on the Trading Partner Assignment tab once the Trading Partner site is selected Although the EDI standards allow for full address details to be used the Oracle e Commerce Gateway only supports the use of Location Codes in the transaction interface file for most transactions For some inbound transactions the application open interface may accept the full name and addresses into the tables for certain business functions However they are generally expecting the column ID to be predetermined Do not confuse the EDI Location
46. TP_CD SS SS SS SS SS SS SS 1700 1710 1720 1730 1750 1760 1770 A1 A2 A2 A2 A1 A2 A2 ST1 ST2 ST3 ST4 OP1 OP2 OP3 Transaction Summary Layouts A 251 Data Trading Partner Ref 1 SS Ref 2 ITEM Record Number Record Layout Record Layout Qualifie r 33 34 35 36 37 38 39 40 41 Ship To Options Flexfiel d15 Extensio n Tables Schedul e Level Basic Item Data Product Descript ion Hazard ous Material Data Contact Names Last Receipt Data Ship to Organiz ation Address Code Ship to Organiz ation Data TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD SS SS SS SS SS SS SS SS SS ITEM ITEM ITEM ITEM ITEM ITEM ITEM 1780 1900 2000 2010 2020 2030 2040 2050 2060 A2 Custo m IT IT HZ CN LS AX ST OP4 Custo m IT1 IT2 HZ1 IT1 LS1 SI2 SIS A 252 Oracle e Commerce Gateway Implementation Manual Data Trading Partner Ref 1 SS Ref2 Ref3 ITEM SCHE DULE Record Number Record Layout Record Layout Qualifie r 42 43 44 45 46 47 48 Approv ed Supplier List Flexfiel ds 1 4 Approv ed Supplier List Flexfiel ds 5 9 Approv ed Supplier List Flexfiel ds 10 14 Appro
47. ed will have BX on the file Tradin 8 Partner site specifi ed will have PC on the file 10 22 Oracle e Commerce Gateway Implementation Manual Categ Directi Key 1 Key2 Key3 Intern Extern Extern Note ory on searc searc searc al al al searc searc h key h key hkey Code Code Code h key h key searc 1 2 h key retrie retrie ved ved data data 4 UOM OUT X12 Each EA Majorit y of Tradin 8 Partner s want EA They were assigne d the Docum ent Standa rd X12 5 UOM OUT OTHE Each PC Other R Tradin 8 Partner s want PC They were assigne d the Docum ent Standa rd OTHE R to allow this entry in the table Code Conversion 10 23 Categ Directi Key 1 Key2 Key3 Intern Extern Extern ory on searc searc searc al al al searc searc h key h key hkey Code Code Code h key h key searc 1 2 h key retrie retrie ved ved data data Note 6 UOM OUT Each EA PC Default write two codes to the file EDI transla tor will choose one based on the data mappi ng rule for the given Tradin 8 Partner This avoids makin 8 entries for each Tradin 8 Partner needin g the PC on the file In table above items 1 5 The exact code for the data map is in external code 1 on the file given the Trading Partner data in the search key You chose not to have the translator choose between EA or PC by accessing item 5 Items 1 through 3
48. er Flexfiel ds 1 4 TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD MEMO MEMO MEMO MEMO MEMO MEMO MEMO 0030 0040 0050 1000 1010 1015 1020 A4 A4 A4 AD CM RF A1 TH2 TH3 TH4 BT1 BT1 BT1 BT1 A 174 Oracle e Commerce Gateway Implementation Manual Data Trading Partner Ref1 Ref2 MEMO ITEM Ref 3 Record TAX Number Record Layout Record Layout Qualifie r 10 11 12 13 14 15 16 17 Bill to Custom er Flexfiel ds 5 9 Bill to Custom er Flexfiel ds 10 14 Bill to Custom er Flexfiel d15 Bill to Site Flexfiel ds 1 4 Bill to Site Flexfiel ds 5 9 Bill to Site Flexfiel ds 10 14 Bill to Site Flexfiel d15 Ship to Address Code TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD MEMO MEMO MEMO MEMO MEMO MEMO MEMO MEMO 1030 1040 1050 1060 1070 1080 1090 1100 A2 A2 A2 Al A2 A2 A2 AD BT2 BT3 BT4 BS1 BS2 BS3 BS4 ST1 Transaction Summary Layouts A 175 Data Trading Partner Ref1 Ref2 Ref3 MEMO ITEM TAX Record Number Record Layout Record Layout Qualifie r 18 19 20 21 22 22 23 24 Ship to Misc Data Contact s Ship to Misc Data Contact s Sold to Address Code Sold to Misc Data Contact Sol
49. for price ADJUSTMENT adjustments 27 Price PRICE 1820 1850 Flexfields Adjustment ADJUSTMENT Flexfields 28 Reservations RESERVATION 1900 Data 29 Reservations RESERVATION 1910 1940 Flexfields Flexfields 30 Action Data ACTION 1950 31 Action Flexfields ACTION 1960 1990 Flexfields 32 Item LINE 2000 Original System Reference Configuration 33 Inventory Item LINE DETAIL 2010 2020 Flexfields Segments 34 Item Detail LINE DETAIL 3000 Items Price 35 Change Data LINE DETAIL 3010 36 Change LINE DETAIL 3012 3018 Comments 37 Payment LINE DETAIL 3020 Type Code Tax Exempt 38 Project Task LINE DETAIL 3030 Contract Numbers Transaction Summary Layouts A 37 Sequence Data Data Level Record Number Note 39 Service LINE DETAIL 3050 Comments 40 FOB Point LINE DETAIL 3080 Freight Terms Shipment Priority Method Freight Carrier 41 Demand Bucket LINE DETAIL 3090 42 Shipment LINE DETAIL 4000 quantities dates 43 Shipping amp LINE DETAIL 4010 Packing Instructions 44 Item Flexfields LINE DETAIL 4200 4230 Flexfields 45 Global Header LINE DETAIL 4300 4340 Flexfields Flexfields 46 Pricing LINE DETAIL 4400 442 Flexfields Flexfields 47 Industry Header LINE DETAIL 4500 4560 Flexfields Flexfields 48 Service LINE DETAIL 4600 463 Flexfields Flexfields 49 Return Flexfields LINE DETAIL 4700 473 Flexfields 50 Ship to Address LINE DETAIL 4800 Line Level 51 Ship to Contact LINE DETAIL 4810 Line Level 52 Deliver to LINE DETAIL 4820
50. meaning Order Import will calculate a price even if one is found in the transactions The calculated price and the price in the transaction will be compared There is an error if there is a discrepancy CUSTOMER_LINE_NUMBER This is the customer s line number as defined in their procurement application There is no default This reference is passed from the transactions LINE_NUMBER This is the order line number as calculated by the e Commerce Gateway as required by 6 42 Oracle e Commerce Gateway Implementation Manual Update Columns Order Import Do not enter data into this field for new orders DEFAULT Increment the line counter by one for each LINE level record that is read OPERATION_CODE See OPERATION_CODE under the OE_HEADERS_INTERFACE table above ORDER_SOURCE_ID This code identifies that the transaction was loaded into Order Import via the e Commerce Gateway DEFAULT The code is set to 6 meaning EDI Item Data CUSTOMER_ITEM_NAME This column represents the customer s item number for the buyer item as defined in their purchasing application CUSTOMER_ITEM_REVISION This column represents the customer s item s revision level This field is for display only This field is not used in the Inventory tables to look up the supplier item INVENTORY_ITEM This column represents the supplier s item number corresponding to the buyer item as defined in Oracle Inventory ITEM_REVISION This column represents the
51. specific inbound transaction ECE_XXX_ENA Enables the Functional Yes Yes BLED transaction where xxx represents a specific transaction For more profile category information see Oracle Applications System Administrator s Guide Maintenance for details Transaction Profile Window Enable Disable Flag for Each Transaction For each transaction supported by Oracle e Commerce Gateway there is a transaction enabled flag i e ECE_XXX_ENABLED where XXX represents a specific transaction This flag indicates if a transaction will be enabled or disabled at the system level The setting determines Oracle e Commerce Gateway s ability to process a given transaction If the flag is disabled the transaction will not be processed by Oracle e Commerce Gateway You still need to enable the flag in the Detail tab of the Define Trading Partner Implementation Details 4 7 window to enable the transaction at the trading partner level Address Precedence for Each Inbound Transaction All inbound transactions have an address derivation precedence profile option The address derivation derives addresses based on certain codes provided to the Oracle e Commerce Gateway in inbound transaction interface files The address precedence has three categories of components They have unique address ids location code translator codes location names and physical addresses These addresses are verified and validated as transactions are processed T
52. subsequent re extraction Produces an interface data file for use by the EDI Translator Inbound Process Flow The inbound transaction flow is similar to the outbound transaction flow Oracle e Commerce Gateway performs the following functions during an inbound transaction process after it receives an interface file from the EDI Translator or other process Reviews the System and Transaction profiles Gets Trading Partner validation processing parameters Validates data based on user defined process rules for the transaction Applies code conversions if set up and activated Validates data based on user defined column rules for the data elements Captures transaction data exceptions These exceptions can be reviewed on line from the staging tables to examine the exception condition The correction action is performed in a trading partner set up or other application set up then the transaction can be revalidated Optionally transactions may be deleted from the view staging tables Loads valid transactions into the appropriate Oracle Application Open Interface tables for the transaction All the valid transactions are loaded into the Application Open Interface tables where it is validated by Oracle Open Interface s Application Program Interfaces APIs Valid Introduction 1 13 data is loaded into Oracle Application base tables Exception data is detected both in Oracle e Commerce Gateway and Oracle Applications depending on t
53. that internal code is passed to the application open interface table Note Code conversion is not performed on the data element by the Oracle e Commerce Gateway if data is already found in the internal field for that data element Concatenated Search Key for Inbound Transactions The following example illustrates the use of the concatenated search key in several attempts to find code conversion table entries for an inbound transaction The Oracle e Commerce Gateway moves data from the transaction interface file into its transaction tables for processing The data may come directly in the transaction from your Trading Partner or be derived by the Oracle e Commerce Gateway Some date elements need code conversion on 1 5 external codes to the internal code defined in the base Oracle application The external codes are defined by Trading Partners or standard transactions You may activate code conversion only on the data elements columns listed in the Assign Categories window By entering search keys the table entry does not apply to all Trading Partners Trading Partner codes and Trading Partner site codes are often search keys in the code conversion value tables since Trading Partners often have site specific codes This example steps through a code conversion table searching for a table entry where the value AIR in the CARRIER_EXT1 external 1 column along with its search keys with the value GAMMA in CUSTOMER_NAME in Key 1 and value 999
54. transaction profiles Enable disable transaction for all transactions Address precedence for inbound transactions Set up transaction specific profiles for outbound transactions such as the Purchase Order or Purchase Order Change transactions Review seeded Process Rule Actions and update rule action if default behavior is not desired Review seeded Column Rule Actions for required fields and update rule action if default behavior is not desired Review seeded Column Rule Actions for date and numeric fields and update rule action if default behavior is not desired Reference IM Implementation Manual User s Guide Setting Profile Options IM Set Up Profiles User s Guide Setting Profile Options IM Set Up Profiles IM Determine Process and Column Rules and Actions IM Determine Process Column Rules and Actions Application Set Up IM Determine Process and Column Rules and Actions 3 4 Oracle e Commerce Gateway Implementation Manual Step 11 12 13 14 15 16 Required Optional Optional for inbound transactions As Needed Optional Required Required Required Description Determine if other columns in the transaction require Column Rules Enable additional data fields as necessary using reference fields descriptive flexfields or the Oracle e Commerce Gateway Extensible Architecture Review interface file definitions record
55. 1 4 9 Advice Header External Referen ces 5 6 10 Advice Header Internal Referen ces 1 5 11 Advice Header Internal Referen ce 6 TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD Ref 1 DOC DOC DOC DOC DOC Ref 2 ERR_C NT Ref 3 blank Record Number 0050 0060 0070 1000 1010 1020 1030 Record Layout A2 Al A2 HD HD HD HD Record Qualifie r TH4 TD1 TD2 EX1 EX2 IN1 IN2 A 90 Oracle e Commerce Gateway Implementation Manual 12 13 14 15 16 17 18 Record Trading Partner Address Extensio n Table Header Level Advice Detail External Referen ces 1 4 Advice Detail External Referen ces 5 6 Advice Detail Internal Referen ces 1 5 Advice Detail Internal Referen ce 6 Advice Detail Data Error TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD Ref 1 DOC DOC DOC DOC DOC DOC DOC DOC Ref 2 ERR_C NT ERR_C NT ERR_C NT ERR_C NT ERR_C NT ERR_C NT Ref 3 Record blank Number 1040 1900 2000 2010 2020 2030 2040 Record Layout AD custom DT DT DT DT ER Record Qualifie r TP1 custom EX1 EX2 IN1 IN2 ER1 Transaction Summary Layouts A 91 Record TP_CD Ref1 Ref 2 Ref 3 Record Record Record DOC ERR_C blank Number Layout
56. 1000 Basic Header 3 Carrier Weights HEADER 1010 Packaging 4 Shipment HEADER 1020 Method of Payment 5 Currency Tax HEADER 1030 Payment Terms 6 Allowances Cha HEADER 1040 rges Freight 7 Hazardous HEADER 1050 Material Special Handling 8 Header Note HEADER 1090 9 Vendor HEADER 1100 Address Code 10 Destination HEADER 1120 Address Code 11 Destination HEADER 1130 Contact 12 Shipment HEADER 1200 1230 Flexfields Header Flexfields 13 Basic Item Data LINE 2000 Transaction Summary Layouts A 119 Type of Data Data Level RECORD Note 14 Hazardous LINE 2010 Material Codes 15 Currency Tax LINE 2020 Item Level 16 Notes Shipping LINE 2030 Instructions 17 Shipment Line LINE 2100 2130 Flexfields Flexfields 18 Transaction LINE 2140 2170 Flexfields Flexfields 19 Destination LINE 3000 Address 20 Destination LINE 3020 Location 21 License Plate LPN 4000 Used with Information Oracle WMS Inbound Ship Notice Manifest Common Key The following table shows the Common Key positions 1 100 for the Inbound Ship Notice Manifest transaction The table shows the position length code and content of the Common Key elements Transaction specific Data in the ASNI Transaction Common Key Position 1 25 26 47 48 69 Length 25 22 22 Code TP_CD SHIPMENT LINE Content Trading Partner Code as defined in the EDI Translator Shipment Number Item Number A 120 Oracle e Comm
57. 114 115 Ship fro m Address Item Level Credits Data Credit Flexfiel ds 1 4 Credit Flexfiel ds 5 9 Credit Flexfiel ds 10 14 Credit Flexfiel d15 Price Adjust ments Data Discoun t List Names Change Reason Text 1 Change Reason Text 2 TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD PO PO PO PO PO PO PO PO PO PO LINE LINE LINE LINE LINE LINE LINE LINE LINE LINE 4870 5000 5100 5110 5120 5130 6000 6010 6020 6030 AD CR Al A2 A2 A2 PR PR PR PR SFR CRD CR1 CR2 CR3 CR4 ADJ AD1 CM1 CM2 A 54 Oracle e Commerce Gateway Implementation Manual Sequen Data Trading Ref 1 Ref 2 Ref 3 Record Record Record ce Partner Number Layout Layout Qualifie r 116 Change TP_CD PO LINE 6040 PR CM3 Reason Text 3 117 Change TP_CD PO LINE 6050 PR CM4 Reason Text 4 118 Price TP_CD PO LINE 6110 A1 AD1 Adjust ment Flexfiel ds 1 4 119 Price TP_CD PO LINE 6110 A2 AD2 Adjust ment Flexfiel ds 5 9 120 Price TP_CD PO LINE 6120 A2 AD3 Adjust ment Flexfiel ds 10 14 121 Price TP_CD PO LINE 6130 A2 AD4 Adjust ment Flexfiel d15 122 Reserva TP_CD PO LINE 7000 RS RES tions Data 123 Reserva TP_CD PO LINE 7100 A1 RS1 tion Flexfiel ds 1 4 Transaction Summary Layouts A 55 Sequen ce Data Trading Partner R
58. 189 Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner INVOIC ITEM TAX Number Layout Layout E Qualifie r 3 Trading TP_CD INVOIC 0030 A4 TH2 Partner E Header Flexfiel ds 4 Trading TP_CD INVOIC 0040 A4 TH3 Partner E Header Flexfiel ds 5 Trading TP_CD INVOIC 0050 A4 TH4 Partner E Header Flexfiel ds 6 Trading TP_CD INVOIC 0060 A3 TD1 Partner E Detail Flexfiel ds 7 Trading TP_CD INVOIC 0070 A4 TD2 Partner E Detail Flexfiel ds 8 Bill To TP_CD INVOIC 1000 AD BT1 Address E Code 9 Bill to TP_CD INVOIC 1010 CM BT1 Misc E Data Contact S A 190 Oracle e Commerce Gateway Implementation Manual Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner INVOIC ITEM TAX Number Layout Layout E Qualifie r 10 Bill to TP_CD INVOIC 1015 RF BT1 TP E Referen ce Codes 11 Bill to TP_CD INVOIC 1020 Al BT1 Custom E er Flexfiel ds 1 4 12 Bill to TP_CD INVOIC 1030 A2 BT2 Custom E er Flexfiel ds 5 9 13 Bill to TP_CD INVOIC 1040 A2 BT3 Custom E er Flexfiel ds 10 14 14 Bill to TP_CD INVOIC 1050 A2 BT4 Custom E er Flexfiel d15 15 Bill to TP_CD INVOIC 1060 Al BS1 Site E Flexfiel ds 1 4 16 Bill to TP_CD INVOIC 1070 A2 BS2 Site E Flexfiel ds 5 9 Transaction Summary Layouts A 191 Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner INVOIC ITEM TAX Number Layout Layout E Qualifie r 17 Bill to TP_CD INVOIC 1080 A2 BS3 Site E Flexfiel ds 10 14 18 Bil
59. 2 3 Gateway These changes may be in the form of new or additional transactions changes in the customer s business requirements and changes occasioned by new or existing trading partners If the Translator is difficult to update or configure this may impact the successful timely outcome of an EDI implementation Another consideration is whether or not the Translator is running on the same server as the Oracle e Commerce Gateway In some cases the Translator has been installed on a separate machine for example a mainframe When this is the case it is necessary to allow for file transfer requirements and scheduling to from the Translator In some instances a file transfer to from a mainframe may require that the file be of fixed length In this case the variable nature of the files used by the Oracle e Commerce Gateway may pose problems of padding for outbound transactions and interface file definition for inbound transactions Trading Partner Definitions Translators have criteria for defining trading partners that is different from the trading partner definitions used in the Oracle e Commerce Gateway The Translator setup requires identifying the following e Sender and receiver identification codes for the electronic envelopes e The EDI standard and its version release or data dictionary for traditional EDI transactions e The transaction s data map used to map data between the source data file and the standard transaction
60. 2 Ref 3 Record Record Record Partner PO ITEM SHIPM Number Layout Layout ENT Qualifie r 68 Distribu TP_CD PO LINE SHIPM 4200 Al DS1 tions ENT Flexfiel DISTRI ds BUTIO NS 69 Distribu TP_CD PO LINE SHIPM 4210 A2 DS2 tions ENT Flexfiel DISTRI ds BUTIO NS 70 Distribu TP_CD PO LINE SHIPM 4220 A2 DS3 tions ENT Flexfiel DISTRI ds BUTIO NS 71 Distribu TP_CD PO LINE SHIPM 4230 A2 DS4 tions ENT Flexfiel DISTRI ds BUTIO NS Oracle Receivables Transaction Summaries Oracle Receivables Transactions Transaction Direction Transaction ASC X12 EDIFACT Name Code Credit Outbound CDMO 812 CREADV DEBA Memo Debit DV Memo Invoice Outbound INO 810 INVOIC A 168 Oracle e Commerce Gateway Implementation Manual Current Information The transaction file may change when enhancements are made such as additional data added to the transaction Current transaction summaries can be found on Oracle Support s web site Current detail record layouts are reported via the Transaction Definition Layout Report and the Interface File Data Report Outbound Credit Memo Debit Memo CDMO 812 CREADV DEBADV A single transaction has the following data hierarchy and data looping CDMO Outbound Credit Memo Debit Memo Structure Record Numbers Control Record 0010 Credit Memo Dehit Memo Header 1000 3075 Headeratowance and Charges 3080 3900 Credit Memo Debit Memo Item 4000 5900 Line Tax 6000 6095 An Outbound Credit Memo Debit Memo
61. 3000 3060 3800 3810 4000 4230 An Outbound Purchase Order transaction contains a single Control Record and Purchase Order Header Record The header record may have multiple Header Attachment Detail Records and Line Records The Line Record may have multiple Line Attachment Header Records Master Item Attachment Header Records and Inventory Item Attachment Header Records The Line Attachment Header Record may have multiple Line Attachment Detail Records The Master Item Attachment Header Record may have multiple Master Item Attachment Detail Records The Inventory Attachment Header Record may have multiple Inventory Attachment Detail Records and multiple Shipment Records The Shipment Records may have multiple Shipment Attachment Header Records and Distributions Records The Shipment Attachment Header Record A 154 Oracle e Commerce Gateway Implementation Manual may have multiple Shipment Attachment Detail Records The following table shows the content and occurrences of the records comprising the Outbound Purchase Order Change transaction Record occurrences Within the POCO Transaction Records Contents Occurrences 0010 Control Record Only one record occurrence per transaction 0020 0070 Gateway Flexfields One set of records per transaction 1000 1900 PO Header Records Only one record occurrence per transaction 2000 2900 PO Line Records One set of records per line within the PO header 3000 3900 PO Shipment Records
62. 6 126 Oracle e Commerce Gateway Implementation Manual Table Column Value PO_HEADERS_ARCHIVE PO_HEADERS_ARCHIVE PO_RELEASES PO_RELEASES PO_RELEASES PO_RELEASES PO_RELEASES_ARCHIVE PO_RELEASES_ARCHIVE PO_RELEASES_ARCHIVE PO_RELEASES_ARCHIVE PRINTED_DATE PRINT_COUNT EDI_PROCESSED_FLAG LAST_UPDATE_DATE PRINTED_DATE PRINT_COUNT EDI_PROCESSED_FLAG LAST_UPDATE_DATE PRINTED_DATE PRINT_COUNT SYSDATE Increment by 1 Y SYSDATE SYSDATE Increment by 1 Y SYSDATE SYSDATE Increment by 1 The PO_LHEADERS and PO_HEADERS_ARCHIVE tables are used for standard planned or blanket purchase orders The PO_LRELEASES and PO_RELEASES_ARCHIVE tables are used for blanket purchase order releases Note While transmitting Outbound Purchase Order Change POCO 860 ORDCHG to a supplier the output received contains information for the entire purchase orders not just the data for the fields that were changed on the purchase order Oracle Receivables The implementation of any transaction requires some setup in Oracle Applications and Oracle e Commerce Gateway This section focuses on the application setups necessary to implement a transaction that integrates with Oracle Receivables The transactions included with Oracle Receivables are listed in the following table Note See Oracle Receivables Transaction Summaries page A 168 for layout details Application Transaction De
63. 6060 A2 TX4 Tax E Flexfiel d15 A 200 Oracle e Commerce Gateway Implementation Manual Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner INVOIC ITEM TAX Number Layout Layout E Qualifie r 85 Line TP_CD INVOIC_ LINE TAX 6070 Al VT1 VAT E Tax Flexfiel ds 1 4 86 Line TP_CD INVOIC LINE TAX 6080 A2 VT2 VAT E Tax Flexfiel ds 5 9 87 Line TP_CD INVOIC LINE TAX 6090 A2 VT3 VAT E Tax Flexfiel ds 10 14 88 Line TP_CD INVOIC LINE TAX 6095 A2 VT4 VAT E Tax Flexfiel d15 Oracle Release Management Transaction Summaries Oracle Release Management Transactions Transaction Direction Transaction ASC X12 EDIFACT Name Code Planning Inbound SPSI 830 DELFOR Schedule Production Inbound PSQI 866 N A Sequence Transaction Summary Layouts A 201 Transaction Direction Transaction ASC X12 EDIFACT Name Code Shipping Inbound SSSI 862 DELJIT Schedule Current Information The transaction file may change when enhancements are made such as additional data added to the transaction Current transaction summaries can be found on Oracle Support s web site when they are released Current detail record layouts are reported via the Transaction Definition Layout Report and the Interface File Data Report Planning Schedule SPSI 830 DELFOR A single transaction has the following data hierarchy and looping SPSI Planning Material Release Schedule Inbound Record Numbers Control Record 0010 Planning
64. 8000 8900 Lot Serial at OM LINE Level 9000 9900 Shipment OM LINE Level 3000 4900 Credits at OM LINE Level 5000 5900 Price Adjustments at OM LINE Level 6000 6900 Reservations at OM LINE Level 7000 7900 Actions at OM LINE Level 8000 8900 Lot Serial fat OM LINE Level 9000 9900 Note The customer and supplier item data in records 2000 2900 will be repeated on each shipment level data in records 3000 4900 to create entries in the Order Import LINE table The following table shows the content and occurrences of the records comprising the Outbound Purchase Order transaction Transaction Summary Layouts A 11 Record Occurrences within the POI transaction Records Content Ocurrences 0010 1000 1699 1700 1740 1800 1850 1900 1910 1950 1990 2000 2900 3000 4900 5000 5900 6000 6900 7000 7900 8000 8900 9000 9900 Control Record PO Header Records Credits Price Adjustments Reservations Actions PO Line PO Line Shipment Credits Price Adjustments Lot Serial Reservations Actions Only one record occurrence per transaction Only one record occurrence per transaction One set of records per header One set of records per header One set of records per header One set of records per header One set of records per item within the PO header One set of records per shipment within the PO Line One set of records per s
65. 860 ORDCHG Change Current Information The transaction file may change when enhancements are made such as additional data added to the transaction Current transaction summaries can be found on Oracle Support s web site Current detail record layouts are reported via the Transaction Definition Layout Report and the Interface File Data Report Inbound Price Sales Catalog CATI 832 PRICAT A single transaction has the following data hierarchy and data looping A 102 Oracle e Commerce Gateway Implementation Manual CATI Inbound Price Sales Catalog Structure Record Numbers Control Record 0010 Price Sales Catalog Header 1000 1900 Item Detail 2000 2900 Item Detail 2000 2900 item Detail 2000 2900 An Inbound Price Sales Catalog transaction contains a single Control Record and Price Sales Catalog Header Record The header record may have multiple Item Detail Records This structure is further described in the table below The following table shows the content and occurrences of the records comprising the Inbound Price Sales Catalog transaction Record Occurrences Within the CATI Transaction Records Content Occurrences 0010 Control Record Only one record occurrence per transaction 1000 1999 Transaction Header Only one set of records per price sales catalog 2000 2999 Transaction Item One set of item records per item within the transaction The following table is a summary list of the records comp
66. Applications make changes to the original schedule on the Release Management Demand Workbench or ask the supplier to resend the transaction with the corrected values If you chose to update Oracle Applications data you can resubmit the Release Management Demand Processor to revalidate the transaction 6 158 Oracle e Commerce Gateway Implementation Manual Production Sequence Schedule PSQI 866 DELJIT SYNCRO SYNPAC Customers addresses and locations are defined in Oracle Accounts Receivable and Oracle Order Management Included in the definition is the EDI Location Code The EDI Location Code is a code that represents a customer s full detailed address Often the customer does not send the full address but just the EDI Location Code This is a critical data field to Oracle e Commerce Gateway The EDI Location Code is the link between a customer address in Oracle Applications and the trading partner site definition in Oracle e Commerce Gateway This enables Oracle e Commerce Gateway to access the detailed data about the customer address in the base Oracle Applications without maintaining the detail data in Oracle e Commerce Gateway To ensure that the trading partner link between Oracle e Commerce Gateway and Oracle Applications is set up properly verify that the customer address and the EDI Location Code in Oracle Applications is the correct customer address selected for the Trading Partner definition in Oracle e Commerce Gateway The sele
67. Change Order Data in Order Import Document Reference PO Change Order Data in Order Import Line Reference line number Change Order Data in Order Import Shipment Reference shipment number Note on Matching change order to order in base order tables 86420 03 86420 03 86420 03 001 002 002 Change order data not match to base order line 001 shipment number 5 Add line 2 shipment number 1 Change order data not match to base order line 002 shipment number 1 Add line 2 shipment number 1 Change order data not match to base order line 002 shipment number 2 Add line 2 shipment number 2 If the customer does not send a unique non changeable shipment level identifier that is 6 22 Oracle e Commerce Gateway Implementation Manual assigned to the Original System Shipment Reference such as the Shipment Number then any subsequent change order processing will require human intervention to do the record matching and determine what shipment data will be updated ORIG_SYS_CREDIT_REF Original System Credit Reference ORIG_SYS_DISCOUNT_REF Original System Discount Reference ORIG_SYS_LOTSERIAL_REF Original System Lot Serial Reference ORIG_SYS_RESERVATION_REF Original System Reservation Reference DEFAULT There are no defaults to the Credit Discount Lot Serial or Reservation reference fields You need to supply this data in the record if you
68. Code C SI Code Link established in Detail Window of Trading Partner Fomm The Translator Code CWS004 defined in the EDI Translator is not limited to one Trading Partner address site using that code in the Oracle e Commerce Gateway Other sites may also use it for Computer Warehouse Services The Translator Code used between the Oracle e Commerce Gateway and the EDI Translator may also consist of a concatenation of Translator Code and Location Code for example in this case CWS004 C SJ You determine the naming convention Linking Trading Partner Data to the Oracle Application Source The following illustration relates the Trading Partner data in the Oracle e Commerce Gateway windows to the address site in the Oracle Application 9 8 Oracle e Commerce Gateway Implementation Manual Trading Partner Data Relates to the Address Site in Oracle Application Define Trading Partner Partner Supplier Assignment Tab Computer T Warehouse Supplier Services Computer Warehouse Services Supplier Site Supplier Site 124 45th St 124 45th St San Jose CA San Jose CA Location EDI Location po inbound Detail Tab Checks Enabled Transaction ONLY for EDI Location on Document Doc Type Translator Control Record 0010 IN PO CSW SFO Outbound Enable all Trading Partners to OUT Invoice CSW CHIC be extracted Define a Trading Partner address site level mo ru 20S FO FU
69. Commerce Gateway Implementation Manual SQL gt describe EC ECE PO INTERFACE LINES X ECE PO INTERFACE LINES X TRANSACTION RECORD ID NOT NULL NUMBER MATERIAL ANALYST CODE VARCHAR2 30 MATERIAL ANALYST LAST NAME VARCHAR2 40 MATERIAL ANALYST FIRST NAME VARCHAR2 20 MATERIAL ANALYST PHONE VARCHAR2 30 MATERIAL ANALYST EMATL VARCHAR2 30 The extension table has now been modified to fit the business requirements and the modifications described above are shown below Oracle e Commerce Gateway Interface Table and Modified Extension Table for Purchase Order Line Data ECE PO INTERFACE LINES Legend ECE_PO_INTERFACE_LINES_X z Unique ID Required Line Number Optional Material Analyst Code Line Order Quantity Material Analyst Last Name Line UOM Material Analyst First Name Sth Material Analyst Phone Line Attribute 1 Material Analyst e Mail Line Attribute 2 Transaction Record ID ___ eee Transaction Record ID Define Data Positions in the Outbound Interface File Task Add records to the ECE_INTERFACE_ COLUMNS table The Oracle e Commerce Gateway employs a series of tables that function as a data dictionary When the Oracle e Commerce Gateway is installed these tables are seeded with all the data necessary to support the standard transactions For outbound transactions the table ECE INTERFACE
70. Commerce Gateway Implementation Manual Data Trading Ref 1 Ref 2 Ref Record Record Record Partner SCH_R ITEM SCHE Number Layout Layout EF DULE Qualifie r 48 Industr TP_CD SCH_R ITEM SCHED 4210 42 A2 ID2 ID7 y EF ULE 60 Flexfiel ds 49 Trading TP_CD SCH_R ITEM SCHED 4300 Al TD1 Partner EF ULE Flexfiel ds Cont ext 50 Trading TP_CD SCH_R ITEM SCHED 4310 43 A2 TD2 TD Partner EF ULE 30 4 Flexfiel ds 51 Subline TP_CD SCH_R ITEM SCHED 5000 QT DIV Require EF ULE ments 52 Item TP_CD SCH_R ITEM SCHED 5010 RF DIV Detail EF ULE Miscella neous Referen ces Codes and Values 53 Schedul TP_CD SCH_R ITEM SCHED 5100 A1 SS1 e Line EF ULE Flexfiel ds Cont ext 54 Schedul TP_CD SCH_R ITEM SCHED 5110 51 A2 SS2 SS4 e Line EF ULE 30 Flexfiel ds Transaction Summary Layouts A 215 Data Trading Partner Ref 1 SCH_R EF Ref 2 ITEM Ref SCHE DULE Record Number Record Layout Record Layout Qualifie r 55 56 57 58 59 Industr MA Flexfiel ds Cont ext Industr y Flexfiel ds Trading Partner Flexfiel ds Cont ext Trading Partner Flexfiel ds Extensio n Tables Item Detail Level TP_CD TP_CD TP_CD TP_CD SCH_R EF SCH_R EF SCH_R EF SCH_R EF ITEM ITEM ITEM ITEM SCHED ULE SCHED ULE SCHED ULE SCHED ULE 5200 5210 52 60 5300 5310 53 30 5900 A1 A2 A1 A2 IS1 IS2 IS7 TS1 TS2 TS4
71. Commerce Gateway into the PO_LINES_INTERFACE for PO lines and shipments table The Purchasing Documents Open Interface API validates this data and moves the valid data into the PO_LINES for PO lines and PO_LINE_LOCATIONS for PO shipments tables If your supplier offers fixed pricing then they only need to supply a unit price Review Purchasing Documents Open Interface Exceptions The processing strategy of the Purchasing Documents Open Interface is to process line by line This means if the Purchasing Documents Open Interface detected an exception at the document header it will not proceed to the document lines At the document line level the Purchasing Documents Open Interface will write valid document lines to the base application tables or write an exception message to the PO_LINTERFACE_ERRORS table for each invalid document line thereby accepting partial transactions You can use the Purchasing Interface Errors Report in Oracle Purchasing to review all exceptions detected by the Purchasing Documents Open Interface API Refer to the Oracle Manufacturing Distribution Sales amp Service Open Interface manual Oracle Purchasing Open Interfaces document for a detailed list of detectable errors and 6 104 Oracle e Commerce Gateway Implementation Manual their meaning Resolve Purchasing Documents Open Interface Exceptions To resolve Purchasing Documents Open Interface exceptions you can either correct the set up data in Oracle App
72. DELI 20000814 20000814 ACTUA 100 EA VER 000000 000000 L 4 4000 4 RECE RECE 20000626 20000626 ACTUA 25 EA IPT IVED 000000 000000 L 5 4000 4 CUM RECE 20000626 20000626 CUMUL 40000 EA IVED 000000 000000 ATIVE 6 4000 4 SHIP SHIP 20000626 20000626 ACTUA 150 EA MEN 000000 000000 L T Sample 4000 Demand Schedule Records Case 1 This is a past due demand record showing that a quantity of 90 was to be shipped on June 26 2000 Case 2 This is firm demand record showing that a cumulative quantity of 26000 is to be delivered July 24 2000 The discrete quantity is derived by the demand processor Case 3 This is a forecast demand record showing that a weekly bucket quantity of 100 is forecast to be requested for delivery the week of August 14 2000 Case 4 This is a Shipment Receipt record showing that the customer received a shipment of 25 on June 26 2000 The Shipment Receipt record can also have the Supplier s delivery number in the ITEM_DETAIL_REF_VALUE_1 field in Record 5010 Case 5 This is a Cumulative Shipment Receipt record showing that the customer has received a cumulative quantity of 40000 as of June 26 2000 Case 6 This is a Shipment Receipt record showing that the customer received notification of a 6 146 Oracle e Commerce Gateway Implementation Manual shipment of 150 on June 26 2000 Demand Schedule Subdetail Records Record 5000 Record 5000 contains the schedule subdetail as noted in the following t
73. EDI Location Code as defined in the base Oracle Application for that address must be placed in the Address Location external code field so the Oracle e Commerce Gateway can use it to determine the address site in the base Oracle Application Do not place it in the Address Location internal code field Once the Oracle 9 12 Oracle e Commerce Gateway Implementation Manual e Commerce Gateway locates the address site in the base Oracle Application the site s column ID can be passed to the Oracle Application open interface table The EDI Location Codes found in the address records in the transaction detail do not need to be defined as a Trading Partner in the Oracle e Commerce Gateway unless that EDI Location Code may also appear on the Control Record 0010 for any transaction See Control Record page 9 10 Any address site in the transaction detail such as the customer customer site or supplier supplier site must be defined in the base Oracle Application and the EDI Location Code for the site must be entered If the EDI Location Code is not entered the address cannot be determined by the Oracle e Commerce Gateway Outbound Transactions One transaction may contain several types of address sites in the transaction detail but only one business address type such as bill to ship to or remit to in the transaction is recognized by the Oracle e Commerce Gateway as the key address site to examine for the Trading Partner setup The Oracle e Commerc
74. Entity 35 N302 Address Line 2 7 Business Entity 35 N301 Address Line 3 8 Business Entity 35 N302 Address Line 4 9 Business Entity City 30 N401 10 Business Entity Postal 15 N403 Code 11 Business Entity 20 Country Internal 12 Business Entity 03 N404 Country ISO external 5 26 Oracle e Commerce Gateway Implementation Manual Seq Business Entity Length ASC X12 Data 13 Business Entity State 20 internal 14 Business Entity State 10 N402 External 15 Business Entity 20 Province internal 16 Business Entity 10 N402 Province External 17 Business Entity 25 County Address AX Record Layout The following table shows the record layout of the AX Address Record record code type All name and address records that have REGION 1 REGION2 and REGIONS in place of explicit state province and county data have the following format This data is extracted from Human Resources tables There may be cases where the interface process does not populate some data fields depending on data availability Address AX Record Layout Seq Business Entity Length ASC X12 Data 1 Common Key 100 including Record Number 2 Business Entity Site 20 Internal Code Internal 3 Business Entity Site 20 N104 Code External EDI Location Code 4 Business Entity Name 60 N102 Transaction Interface File Architecture 5 27 Seq Business Entity Length ASC X12 Data 5 Business Entity 35 N301 Address L
75. Flexfiel ds Line Flexfiel ds Line Part Flexfiel ds TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD PO PO PO PO PO PO PO PO PO LINE LINE LINE LINE LINE LINE LINE LINE LINE 2000 2010 2020 2030 2040 2050 2060 2070 2080 IT IT IT IT A1 A2 A3 A4 A1 IT1 IT2 IT3 IT4 LN1 LN2 LN3 LN4 LP1 A 164 Oracle e Commerce Gateway Implementation Manual Data Trading Partner Ref 1 PO Ref2 Ref3 ITEM SHIPM ENT Record Number Record Layout Record Layout Qualifie r 45 46 47 48 49 50 51 52 Line Part Flexfiel ds Line Part Flexfiel ds Line Part Flexfiel ds Line Part Segmen ts Line Part Segmen ts Line Attach ment Header Line Attach ment Detail Master Item Attach ment Header TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD PO PO PO PO PO PO PO PO LINE LINE LINE LINE LINE LINE LINE LINE 2090 2100 2110 2120 2130 2800 2810 2820 A2 A3 A4 PS PS AT AT AT LP2 LP3 LP4 PS1 PS2 LAH LAD MAH Transaction Summary Layouts A 165 Data Trading Partner Ref 1 PO Ref 2 ITEM Ref 3 SHIPM ENT Record Number Record Record Layout Layout Qualifie r
76. Flexfield 15 Reservati ons Data Reservati on Flexfields 1 4 Reservati on Flexfields 5 9 Reservati on Flexfields 10 14 Trading Partner TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD Ref 1 PO PO PO PO PO PO PO PO Ref 2 LINE LINE LINE LINE LINE LINE LINE LINE Ref 3 Record Number 6110 6110 6120 6130 7000 7100 7110 7120 Record Layout Al A2 A2 A2 RS Al A2 A2 Record Layout Qualifier AD1 AD2 AD3 AD4 RES RS1 RS2 RS3 A 30 Oracle e Commerce Gateway Implementation Manual Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner Number Layout Layout Qualifier Reservati TP _CD PO LINE 7130 A2 RS4 on Flexfield 15 Action TP_CD PO LINE 8000 AC ACT Data Actions TP_CD PO LINE 8100 Al ACI Flexfields 1 4 Actions TP_CD PO LINE 8110 A2 AC2 Flexfields 5 9 Actions TP_CD PO LINE 8120 A2 AC3 Flexfields 10 14 Actions TP_CD PO LINE 8130 A2 AC4 Flexfield 15 Lot TP_CD PO LINE 9000 LT SER Serials Data Serial Lot TP _CD PO LINE 9100 Al LT1 Flexfields 1 4 Serial Lot TP_CD PO LINE 9110 A2 LT2 Flexfields 5 9 Serial Lot TP_CD PO LINE 9120 A2 LT3 Flexfields 10 14 Transaction Summary Layouts A 31 Data Trading Ref 1 Ref 2 Partner Serial Lot TP_CD PO LINE Flexfield 15 Ref 3 Record Number 9130 Record Layout A2 Record La
77. Freight Carrier Trading Partner TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD Ref 1 PO PO PO PO PO PO PO Ref 2 LINE LINE LINE LINE LINE LINE LINE Ref 3 Record Number 2010 2020 3000 3020 3030 3050 3080 Record Layout IT IT LN PY PJ SV FB Record Layout Qualifier IS1 IS2 LN1 TAX SRV CM1 SHP A 24 Oracle e Commerce Gateway Implementation Manual Data Demand Bucket Class Stream Shipment Data UOM Ship Pro mise Dates Shipping amp Packing Instructio ns Item Flexfields 1 4 Item Flexfields 5 9 Item Flexfields 10 14 Item Flexfield 15 Global Header Flexfields 1 4 Trading Partner TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD Ref 1 PO PO PO PO PO PO PO PO Ref 2 LINE LINE LINE LINE LINE LINE LINE LINE Ref 3 Record Number 3090 4000 4010 4200 4210 4220 4230 4300 Record Layout DM DT NT Al A2 A2 A2 Al Record Layout Qualifier DMD QTY NTE IT1 IT2 IT3 IT4 GL1 Transaction Summary Layouts A 25 Data Trading Partner Global TP_CD Header Flexfields 5 9 Global TP_CD Header Flexfields 10 14 Global TP_CD Header Flexfields 15 19 Global TP_CD Header Flexfield 20 Pricing TP_CD Flexfie
78. Gateway Implementation Manual Data Rule Description Value is Required Checks if the incoming data for a given column has a non null value i e it cannot be blank Each rule is associated with an action taken when an exception is detected The exception processing options are skip current document log the violation and continue processing or abort the entire run Another form of transaction configuration is performed on the transaction data based on user defined code conversion rules The Oracle e Commerce Gateway Code Conversion module supports the following e One Oracle code to one external code e One Oracle code to many external codes e Criteria based code conversion e Intelligent search for Oracle or external code s An example of a one to one relationship is the conversion of a single Oracle code for unit of measure to a unit of measure code based on the ISO 9000 code list the ASC X12 code list or your private code list An example of a one to many relationship is the conversion of a single Oracle code for payment terms to its ASC X12 components for discount percent discount days and net days You can define a code conversion rule that applies to all transactions for all trading partners or one that is specific to a trading partner and transaction combination For maximum flexibility you can define up to five specific criteria per rule Intelligent search is used to identify the Oracle internal or external code
79. Guide for a list of the program parameters The two database views are as follows e ECE _PYO_INVOICE_V ECE_PYO_PAYMENT_V The ECE_PYO_PAYMENTS_V view used to identify which payments and associated invoices are eligible for extraction The extract criteria are as follows e Trading partner is defined e Transaction type enabled for the trading partner e Payments have not been previously extracted e Payments are flagged as OK to pay e Payments have not been voided e Bank account ID bank name and bank branch ID assigned to the payment match those in the payment batch If necessary you can use SQLPLUS to verify if there are any eligible documents to be extracted To do so you must first set the organization context and then issue the SQL count function as follows SQLPLUS gt execute fnd client _info set_org context lt Org number gt SQLPLUS gt select count ECE PYO PAYMENTS V Review all your set ups if the count value is 0 as this indicates there are no eligible documents to be extracted Columns Updated Upon Extraction Once the Translator sends the transactions to the bank and you have verified the bank has received the file you can confirm the payment batch to indicate the invoices have been paid This prevents the same invoice from being included in a future payment batch Refer to the Confirming Payment Batches section Oracle Payables User s Guide for details Inbound Invoice INI 810 INVOIC
80. IT4 IT5 IT6 ST Transaction Summary Layouts A 115 Record TP_CD Ref 1 DOC Ref2 Ref 3 ITEM blank Record Number Record Layout Record Layout Qualifie r 22 23 24 25 26 27 28 29 Line Level Flexfiel ds 1 4 Line Level Flexfiel ds 5 9 Line Level Flexfiel ds 10 14 Line Level Flexfiel d15 Shipme nt Flexfiel ds 1 4 Shipme nt Flexfiel ds 5 9 Shipme nt Flexfiel ds 10 14 Shipme nt Flexfiel d15 TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD DOC DOC DOC DOC DOC DOC DOC DOC LINE LINE LINE LINE LINE LINE LINE LINE 2200 2210 2220 2230 2240 2250 2260 2270 Al A2 A2 A2 Al A2 A2 A2 LN1 LN2 LN3 LN4 SH1 SH2 SH3 SH4 A 116 Oracle e Commerce Gateway Implementation Manual Record TP_CD Ref1 Ref 2 Ref 3 Record Record Record DOC ITEM blank Number Layout Layout Qualifie r 30 Item TP_CD DOC LINE 2280 Al IT1 Level Flexfiel ds 1 4 31 Item TP_CD DOC LINE 2290 A2 IT2 Level Flexfiel ds 5 9 32 Item TP_CD DOC LINE 2300 A2 IT3 Level Flexfiel ds 10 14 33 Item TP_CD DOC LINE 2310 A2 IT4 Level Flexfiel d15 Inbound Ship Notice Manifest ASNI 856 DESADV A single transaction has the following data hierarchy and data looping Transaction Summary Layouts A 117 ASNI Inbound Ship Notice Manifest
81. Interfac e Line Flexfiel ds 1 4 Interfac e Line Flexfiel ds 5 9 TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD MEMO MEMO MEMO MEMO MEMO MEMO MEMO LINE LINE LINE LINE LINE LINE 3900 4000 4010 4020 4030 5000 5010 IT IT IT IT Al A2 Custo m IT1 IT2 IT3 IT4 IL1 IL2 A 180 Oracle e Commerce Gateway Implementation Manual Data Trading Partner Ref 1 MEMO Ref 2 ITEM Ref 3 Record TAX Number Record Layout Record Layout Qualifie r 54 55 56 57 58 59 60 61 62 Interfac e Line Flexfiel ds 10 14 Interfac e Line Flexfiel d15 Line Flexfiel ds 1 4 Line Flexfiel ds 5 9 Line Flexfiel ds 10 14 Line Flexfiel d15 Line Part Flexfiel ds 1 4 Line Part Flexfiel ds 5 9 Line Part Flexfiel ds 10 14 TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD MEMO MEMO MEMO MEMO MEMO MEMO MEMO MEMO MEMO LINE LINE LINE LINE LINE LINE LINE LINE LINE 5020 5030 5040 5050 5060 5070 5100 5110 5120 A2 A2 Al A2 A2 A2 Al A2 A2 IL3 IL4 LN1 LN2 LN3 LN4 LP1 LP2 LP3 Transaction Summary Layouts A 181 Data Trading Partner Ref 1 MEMO Ref 2 Ref 3 ITEM TAX Record Number Record Layout Reco
82. Layout Qualifie r 3 Currenc y Paymen t Terms 4 FOB Carrier Freight Terms 5 Action Type 6 Comme nts 7 Ship to Address 8 Bill to Address 9 Ship From Address 10 Header Flexfiel ds 1 4 11 Header Flexfiel ds 5 9 12 Header Flexfiel ds 10 14 TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD DOC DOC DOC DOC DOC DOC DOC DOC DOC DOC 1010 1020 1030 1040 1100 1110 1120 1200 1210 1220 HB HC HE NT AX AX AD Al A2 A2 HD2 HD3 HD5 HCM ST BT SF HD1 HD2 HD3 A 114 Oracle e Commerce Gateway Implementation Manual Record TP_CD Ref 1 DOC Ref 2 ITEM Ref 3 Record blank Number Record Layout Record Layout Qualifie r 13 14 15 16 17 18 19 21 Header Flexfiel d15 Item Identific ation Quantit y Descript ion Prices Dates Paymen t Terms Item Level FOB Carrier Freight Terms Item Level Hazard ous data Weight Volume Lead Time Ship To Data Item Level TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD DOC DOC DOC DOC DOC DOC DOC DOC LINE LINE LINE LINE LINE LINE LINE 1230 2000 2010 2020 2030 2040 2050 2100 A2 IA IB IC ID IE IF AX HD4 IT1 IT2 IT3
83. Line Part LINE 5100 5130 Flexfields Flexfields 34 TP Header LINE 5140 5160 Flexfields Flexfields 34 TP Line LINE 5170 5190 Flexfields Flexfields A 172 Oracle e Commerce Gateway Implementation Manual Data Data Level Record Number Note 35 Industry LINE 5200 5220 Flexfields Flexfields 36 Extension LINE 5900 Custom Tables Item Data 37 Line Tax Data LINE TAX 6000 6020 38 VAT Tax Data LINE TAX 6025 39 Line Tax LINE TAX 6030 6060 Flexfields Flexfields 40 VAT Tax LINE TAX 6070 6095 Flexfields Flexfields The following table shows the Common Key positions 1 100 for the Outbound Credit Memo Debit Memo transaction The table shows the position length code and content of the Common Key elements Transaction specific Data in the Common Key of the CDMO Transaction Per Record Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner MEMO ITEM TAX Number Layout Layout Qualifie r 1 Control TP_CD MEMO 0010 CT CTL Record 2 Trading TP_CD MEMO 0020 A3 TH1 Partner Header Flexfiel ds Transaction Summary Layouts A 173 Data Trading Partner Ref1 Ref2 Ref3 MEMO ITEM TAX Record Number Record Layout Record Layout Qualifie r 3 Trading Partner Header Flexfiel ds 4 Trading Partner Header Flexfiel ds 5 Trading Partner Header Flexfiel ds 6 Bill To Address Code 7 Bill to Misc Data Contact s 8 Bill to TP Referen ce Codes 9 Bill to Custom
84. Link to Oracle e Commerce Gateway Oracle e Commerce Gateway Required Fields Review Oracle e Commerce Gateway Exceptions Resolve Oracle e Commerce Gateway Exceptions Relevant Oracle Application Profiles and Setups Oracle Application Open Interface Required Fields Review Application Open Interface Exceptions Return Application Advice to Trading Partner if appropriate Resolve Application Open Interface Exceptions Current Information The transaction requirements may change when enhancements are made such as additional data added to the transaction Current transaction details can be found on Oracle Support s web site Current detail record layouts are reported via the Transaction Layout Definition Report and the Interface File Data Report Refer to Oracle Shipping Execution Transaction Summaries on page page A 229 for a diagram of the record hierarchy record looping structure and record summaries 6 134 Oracle e Commerce Gateway Implementation Manual Planning Material Release SPSI 830 DELFOR DELINS Shipping Schedule SSSI 862 DELJIT DELINS CALDEL KANBAN The Planning Material Release transactions can include both forecast and firm requirements The planning schedule with release capability transaction may be used in various ways or in a combination of ways such as e a simple forecast e a forecast with the buyer s authorization for the seller to commit resources such as labor or material e a forecast that is also use
85. Misc HEADER 1010 1015 Data Contacts 6 Bill to Customer HEADER 1020 1050 Flexfields Flexfields A 170 Oracle e Commerce Gateway Implementation Manual Data Data Level Record Number Note 7 Bill to Site HEADER 1060 1090 Flexfields Flexfields 8 Ship to HEADER 1100 Address Code 9 Ship to Misc HEADER 1110 1115 Data Contacts 10 Sold to HEADER 1200 Address Code 11 Sold to Misc HEADER 1210 1215 data Contact 12 Remit to HEADER 1300 1315 Address Code 13 Ship From Codes HEADER 1400 14 Basic Memo HEADER 2000 Header Data 15 Memo Misc HEADER 2010 2020 Data 16 Shipment Data HEADER 2030 17 Currency Data HEADER 2040 Misc Data 18 Payment Terms HEADER 2050 Data 19 Sales HEADER 2060 Representative Comments 20 Transaction HEADER1 3000 3030 Flexfields Flexfields Transaction Summary Layouts A 171 Data Data Level Record Number Note 21 Interface HEADER1 3040 3070 Flexfields Flexfields 22 Equipment Data HEADER1 3075 23 Header ALLOWANCE 3080 3090 Allowance Char CHARGES ges HEADER 24 Header ALLOWANCE 3091 3094 Flexfields Allowance Char CHARGES ges Flexfields HEADER 25 Extension ALLOWANCE 3900 Custom Tables Memo CHARGES Header Data HEADER 26 Basic Line Data LINE 4000 27 Sales Order LINE 4010 Data Part Descriptions 28 Sales Channel LINE 4020 29 Order Status LINE 4030 Transaction Reference Key 30 Interface Line LINE 5000 5030 Flexfields Flexfields 31 Line Flexfields LINE 5040 5070 Flexfields 32
86. Number E Record Layout Record Layout Qualifie r 10 11 12 13 14 15 16 17 Account Data Paymen t Data Vendor Flexfiel ds Bank Address Code Bank Contact s Supplier Bank Vendor Site Address Code Global ABA Flexfiel ds 1 4 Global ABA Flexfiel ds 5 9 Global ABA Flexfiel ds 10 14 TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD BATCH BATCH BATCH BATCH BATCH BATCH BATCH BATCH BATCH BATCH 1000 1010 1020 1030 1040 1050 1080 1090 1100 1110 BK PY VN AD CN AD AD GA GA GA BK1 PAY VNI1 BK1 BK1 SB1 VS1 BK1 BK2 BK3 Transaction Summary Layouts A 97 Record TP_CD Ref 1 BATC H Ref2 Ref3 INVOIC blank E Record Record Record Number Layout Layout Qualifie r 18 19 20 21 22 23 24 25 Global ABA Flexfiel ds 15 19 Global ABA Flexfiel d 20 Global ABAS Flexfiel ds 1 4 Global ABAS Flexfiel ds 5 9 Global ABAS Flexfiel ds 10 14 Global ABAS Flexfiel ds 15 19 Global ABAS Flexfiel d 20 Global PVS Flexfiel ds 1 4 TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD BATCH BATCH BATCH BATCH BATCH BATCH BATCH BATCH 1120 1130 1140 1150 1160 1170 1180 1190 GA GA GA GA GA
87. OE_RESER 7000 120 130 VTNS_INT ERFACE Line OE_ACTIO 8000 NS_INTER FACE Line OE_LOTSE 9000 120 130 RIAL_INT ERFACE Outbound Purchase Order Acknowledgment POAO 855 ORDRSP POCAO 865 ORDRSP When a new Sales Order is changed to a Booked status within Order Management an APl is called This API determines if the customer and customer location are defined as a Trading Partner within e Commerce Gateway and if the POAO transaction is enabled for the Trading Partner When an existing Sales Order is modified and changed to a Booked status within Order Management an API is called This API determines if the customer and customer location are defined as a Trading Partner within e Commerce Gateway and if the POCAO transaction is enabled for the Trading Partner If either of the above mentioned conditions is met then the Sales Order data is either added or updated in the O0E_LHEADERS_ACKS and OE_LINE_ACKS tables The ACKNOWLEDGE_FLAG must be set to Y in the O0E_HEADERS_ACKS table to make the acknowledgment eligible for extraction Application Transaction Detail 6 63 Oracle Payables The implementation of any transaction requires some setup in Oracle Applications and Oracle e Commerce Gateway This section focuses on the application setups necessary to implement a transaction that integrates with Oracle Payables The table below lists the Oracle Payables transactions Note See Oracle Payables Transaction Summaries page A 71 f
88. One set of records per schedule within the PO line 4000 4230 PO Distributions Records One set of records per distribution within the PO Shipment The following table is a summary list of the records comprising the Outbound Purchase Order Change transaction The table shows the functional data grouping of records the data level the record numbers and relevant notes about the data grouping POCO Transaction Record Summary Seq Data Data Level Record Number Note 1 Control Record HEADER 0010 2 Trading Partner HEADER 0020 0050 Custom Header Flexfields Transaction Summary Layouts A 155 Seq Data Data Level Record Number Note 3 Trading Partner HEADER 0060 0070 Custom Detail Flexfields 4 Purchase Order HEADER 1000 Basic Header 5 Payment Terms HEADER 1010 6 Purchase Order HEADER 1020 Basic Header 7 Purchase Order HEADER 1030 Notes to Supplier 8 Purchase Order HEADER 1040 1070 Flexfields Flexfields 9 Supplier HEADER 1080 1110 Flexfields Flexfields 10 Supplier Site HEADER 1120 1150 Flexfields Flexfields 11 Supplier Site HEADER 1160 Address Code 12 Supplier Site HEADER 1170 1180 Contacts 13 Ship to HEADER 1190 Address Code 14 Ship to Contacts HEADER 1200 15 Bill to HEADER 1210 Address Code 16 Bill to Contact HEADER 1220 17 Buyer Name HEADER 1230 A 156 Oracle e Commerce Gateway Implementation Manual Seq Data Data Level Record Number Note 18 Buyer HEADER 1240 Communications 19 Procure
89. Oracle e Commerce Gateway responsibility to user s Define UTL_FILE_DIR Parameter in INIT ORA File The Database Administrator DBA must define the UTL_FILE_DIR parameter in the INIT ORA file To use Oracle e Commerce Gateway you must first create directories where data files for both inbound and outbound transactions are stored Oracle e Commerce Gateway uses the UTL_FILE package to read and write the ASCII transaction interface flat files on the server UTL_FILE can only write to accessible directories The directories are defined by the utl_file_dir parameter in the init lt SID gt ora file This file is usually found in the ORACLE_HOME dbs directory Within this file each accessible directory is indicated by a line similar to utl file dir directory name The specification of directory name will vary depending on the operating system If the operating system is case sensitive then directory name is case sensitive The value for directory name must be a physical directory as opposed to a variable logical or an alias In addition the value for directory name must match the value defined in the Oracle e Commerce Gateway profile for ECE Inbound File Path and ECE Output File Path Refer to Set Up Profiles for the details For example the following entries are legal for a UNIX system assuming the directories specified exist utl _ file dir tmpdirectory name utl_ file dir home oracle output_files In addition to
90. Order Import Item Cross Referencing Data in the e Commerce Gateway Transaction Oracle Payables Oracle Process Manufacturing Oracle Purchasing Oracle Receivables Oracle Release Management Oracle Shipping Execution Oracle Supplier Scheduling Oracle Inventory The implementation of any transaction requires some setup in Oracle Applications and Oracle e Commerce Gateway This section focuses on the application setups necessary to implement a transaction that integrates with Oracle Inventory The Oracle Inventory transactions are listed in the following table Application Transaction Detail 6 1 Oracle Inventory Transactions Transaction Direction Transaction ASC X12 EDIFACT Name Code Movement Outbound MVSTO N A CUSDEC Statistics Note See Oracle Inventory Transaction Summaries page A 1 for layout details The topics covered for outbound transactions include the following e Trading Partner Link to Oracle e Commerce Gateway e Relevant Oracle Application Profiles and Setups e Extract Criteria e Columns Updated Upon Extraction Current Information The transaction requirements may change when enhancements are made such as additional data added to the transaction Current transaction details can be found on Oracle Support s web site Current detail record layouts are reported via the Transaction Layout Definition Report and the Interface File Data Report Outbound Movement Statistics MVSTO No X12 CUSDEC Tradin
91. Purchase Order Acknowldegment and PO Change Acknowledgment Structure Control Record Order Acknowledgment Header Order Ack Item Order Ack Shipment Order Ack Shipment Order Ack Item Order Ack Shpment Order Ack Shpment The following table shows the content and occurrences of the records comprising the Outbound Purchase Order Acknowledgment and Outbound Purchase Order Change Acknowledgment transactions Record occurrences within the POAO POCAO transactions Records Content Occurrences 0010 e Commerce Gateway Control Record 1000 1540 Acknowledgment Header Records Only one record occurrence per transaction Only one record occurrence per transaction A 58 Oracle e Commerce Gateway Implementation Manual Records Content Occurrences 2000 4030 Acknowledgment Item One set of records per item Records within the Acknowledgment header The following table is a summary list of the records that comprise the Outbound Purchase Order Acknowledgment and the Outbound Purchase Order Change Acknowledgment transactions The table shows the functional data grouping of records the data level the record numbers and relevant notes about the data grouping POAO and POCAO Transaction Record Summary Seq Data Data Level Record Number Note 1 Control Record HEADER 0010 2 Basic Purchase HEADER 1000 Order Header 3 Currency Code HEADER 1060 amp Conversion Rates 4 Tax Exempt HEADER 1080 Info
92. Purchase Order Outbound POO transaction has the corresponding extension package body ECEPOOXB pls containing the following procedures e Populate_Ext_Header e Populate_Ext_Line e Populate_Ext_Shipment To populate the new columns added to ECE_PO_INTERFACE_LINES_X in the earlier example the procedure Populate_Ext_Line requires modification As installed the entire procedure reads as follows Procedure follows PROCEDURE Populate Ext Line 1_fkey IN NUMBER l plsql_ table IN ece flatfile pvt interface tbl_type Is BEGIN NULL END PROCEDURE Populate Ext Line which does absolutely nothing although the procedure is called each time a record is inserted into ECE_PO_INTERFACE_LINES The procedure takes two parameters a key value and a PL SQL table The key value is the TRANSACTION_RECORD_ID value which is the primary key for both the interface table and the extension table interface_tbl_type is a PL SQL table typedef with the following structure Extensible Architecture 11 13 base _ table name VARCHAR2 50 Application table name base_column_name VARCHAR2 50 Application column name interface table nam VARCHAR2 50 Interface table nam interface column_name VARCHAR2 50 Interface column name record num NUMBER Interface File Record Num position NUMBER Interface File Position data_length NUMBER
93. SCHEDULE 2100 Code ITEM 24 Bill To Address SCHEDULE 2110 Code ITEM 25 Intermediate SCHEDULE 2120 Ship To Address ITEM Code 26 Ship From SCHEDULE 2130 Address Code ITEM 27 Miscellaneous SCHEDULE 2140 Name Codes and ITEM Values 28 Carrier Details SCHEDULE 2150 ITEM Transaction Summary Layouts A 205 Data Data Level Record Number Note 29 Item Note Text SCHEDULE 2160 ITEM 30 Hazardous SCHEDULE 2170 Material data ITEM 31 Ship Delivery SCHEDULE 2180 Pattern Codes ITEM 32 Schedule Line SCHEDULE 2300 2330 Flexfields Flexfields ITEM 33 Industry SCHEDULE 2340 2400 Flexfields Flexfields ITEM 34 Trading Partner SCHEDULE 2500 2530 Flexfields Flexfields ITEM 35 Extension SCHEDULE 2900 Custom Tables Item ITEM Data 36 Schedule Item SCHEDULE 4000 Detail Data ITEM Requirements Authorizations Shipped Receive d data etc 37 Item Detail Misc SCHEDULE 4010 References ITEM 38 Item Detail Note SCHEDULE 4020 Text ITEM 39 Schedule Line SCHEDULE 4100 4130 Flexfields Flexfields ITEM 40 Industry SCHEDULE 4200 4260 Flexfields Flexfields ITEM A 206 Oracle e Commerce Gateway Implementation Manual Data Data Level Record Number Note 41 Trading Partner SCHEDULE 4300 4330 Flexfields Flexfields ITEM 42 Subline SCHEDULE 5000 Requirements ITEM 43 Item Detail Misc SCHEDULE 5010 References ITEM Codes and Values 44 Schedule Line SCHEDULE 5100 5130 Flexfields Flexfields ITEM 45 Industry SCHEDULE 5200 5260 Flexfields
94. SITE Column E In the example above the first search has the full key including the external 1 code AIR Since there was no table entry for CUSTOMER_NAME with value GAMMA and CUSTOMER_SITE with value 9999 the highest order key is removed for the second search attempt In this case the customer site 9999 was removed from the search key parameters KEY2 with CUSTOMER_SITE was the highest number search key at this time The second search with just CUSTOMER_NAME with value GAMMA and the external 1 code AIR also did not find a table entry So the current highest order key is removed for the next search attempt In this case the customer GAMMA was removed from the search key parameter KEY1 with CUSTOMER_NAME was the highest number search Code Conversion 10 33 key at this time The third search is made with all blank search keys The internal code is code AIR This search found a table entry It is shown in sample code converstion table entry 7 Consequently the internal value Over Night from the code conversion value table is copied to CARRIER_INT column in the transaction table If no table entry is found then the CARRIER_EXT1 external 1 value is moved into the column CARRIER_INT field in the transaction table Over Night is the valid value for the Oracle Application open interface erface Concatenated Search Key for Outbound Transactions The following example illustrates the use of the concatenated search key in several at
95. Schedule 1 subdetail3 6 144 Oracle e Commerce Gateway Implementation Manual Record Subrecord Subrecord e Commerce Demand Gateway File Processor Data Content Level Four Levels of Two Levels of Data Data HEADER and LINE 2000 4000 Schedule2 data Copy schedule for second for its subdetail schedule data 2000 4000 5000 Schedule2 LINE subdetaill Item2 Schedule 2 subdetail1 2000 4000 5000 Schedule2 LINE subdetail2 Item2 Schedule 2 subdetail2 2000 4000 Schedule3 data LINE for third Item2 Schedule schedule 3 2000 4000 Schedule3 data LINE for fourth Item2 Schedule schedule 4 Demand Schedule Detail Records Record 4000 contains the schedule detail as noted in the following table Case Reco ITEM ITEM DATE START_D END_DAT QTY_TY ITEM UOM rd _DET _DET _TYP ATE_TIM E_TIME_ PE_COD _DET INT Num AIL_ AILS E CO E DET DET Pos E_INT AIL_ D TYPE UBTY DE Pos 190 200 Pos 210 QUA Pos INT PEIN NT NTIT 280 Pos T Pos Y 10 Pos 130 Pos 70 270 1 4000 0 1 SHIP 20000626 20000626 ACTUA 90 EA 000000 000000 L 2 4000 1 1 DELI 20000724 20000724 CUMUL 26000 EA VER 000000 000000 ATIVE Application Transaction Detail 6 145 Case Reco ITEM ITEM DATE START_D END_DAT QTY_TY ITEM UOM rd _DET _DET _TYP ATE_TIM E_TIME_ PE_COD _DET INT Num AIL_ AILS E_ CO E DET DET Pos E_INT AIL_ D TYPE UBTY DE Pos 190 200 Pos 210 QUA Pos INT PEIN NT NTIT 280 Pos T Pos Y 10 Pos 130 Pos 70 270 3 4000 2 2
96. Schedule Header 1000 1900 item 2000 2900 Schedule Detail 4000 4900 Schedule Subdetails 5000 5900 An Inbound Planning Material Release Schedule transaction contains one Control Record and Planning Schedule Header The Planning Schedule Header record can have multiple Item Records which can have multiple Schedule Detail Records which can have multiple Schedule Subdetail Records This structure is further described in the table below The following table shows the content and occurrences of the records comprising the Inbound Planning Material Release transaction A 202 Oracle e Commerce Gateway Implementation Manual Record Occurrences Within the SPSI Transaction Records Content Occurrences 0010 0070 Control Records Only one record occurrence per transaction 1000 1900 Header Records Only one record occurrence per transaction 2000 2900 Item Records One set of records per item within the Planning or Shipping Schedule header 4000 4900 Item Detail Records Multiple detail records per item requirements authorizations receipt data etc 5000 5900 Subdivide Requirements Optional splitting of Records requirements by time or destination The following table is a summary list of the records that comprise the Inbound Planning Material Release Schedule transaction The table shows the functional data grouping of records the data level the record numbers and relevant notes about the data grouping SPSI Transacti
97. Transaction Detail 6 101 e UPDATE Catalog change The following types of data are supported with a catalog change e Unit price e Item description e Unit of measure e Price breaks for blanket purchase agreements e Expiration date for blanket purchase agreements e Supplier URL to get additional item data DOCUMENT_TYPE_CODE This column is not mapped or referenced by the Oracle e Commerce Gateway because the data is not required by the transaction EFFECTIVE_DATE EXPIRATION_DATE These two columns are required if you are replacing an existing catalog or if sourcing rules i e if you answered YES to Create Sourcing Rules parameter are to be created The values are used to locate the old price sales catalog and retire it SHIP_FROM_ADDRESS_CODE This column represents the supplier site code The value is derived by the Purchasing Documents Open Interface based on the supplier site id SHIP_FROM_ADDRESS_ID This column represents the vendor site id The value is derived by Oracle e Commerce Gateway based on the vendor id which itself is derived from the Translator Code on record 0010 element 70 and EDI Location Code on record 0010 element 80 The Purchasing Documents Open Interfaces uses the supplier site id to derive the supplier site code SHIP_FROM_CUSTOMER_ID This column represents the supplier ID Oracle e Commerce Gateway derives this value based on the Translator Code on record 0010 element 70 and EDI Locat
98. Transaction type enabled for the trading partner e Material movement statistics have not been previously extracted e Material movement statistics status is either FROZEN or VERIFIED Application Transaction Detail 6 3 e Material movement type matches type selected when transaction was initiated If necessary you can use SQLPLUS to verify if there are any eligible documents to be extracted To do so you must first set the organization context and then issue the SQL count function as follows SQLPLUS gt execute fnd client _info set_org context lt Org number gt SQLPLUS gt select count ECE MVSTO DETAILS V Review all your set ups if the count value is 0 as this indicates there are no eligible documents to be extracted Columns Updated Upon Extraction Once an eligible material movement statistic entry is successfully extracted and written to the transaction interface file it is marked by Oracle e Commerce Gateway to prevent it from subsequent extraction The following table is a list of fields updated based on an excerpt of code in the ECEMVSOB pls file to update the MTL_MOVEMENT_STATISTICS table Columns Updated Upon Extraction Column Value EDI_LSENT_FLAG Y EDI_TRANSACTION_DATE SYSDATE EDI_TRANSACTION_REFERENCE see below EDI_TRANSACTION_REFERENCE is the concatenation of the parameter values entered when the transaction was initiated e Legal entity e Zone code e Period Name e Stat type eit
99. Transactions Method Applies to Outbound Applies to Inbound Transactions Transactions Trading Partner Header Yes No Reference fields Descriptive Flexfields in the Yes Yes Oracle e Commerce Gateway Descriptive Flexfields in the Yes No base Oracle Applications Oracle e Commerce Gateway Yes No Extensible Architecture Interface File Definition Yes Yes Interface Data File processing No Yes Trading Partner Header Reference fields There are two Trading Partner reference fields on the Trading Partner header defined in the Define Trading Partner window as TP_REFERENCE_EXT1 and 4 20 Oracle e Commerce Gateway Implementation Manual TP_REFERENCE_EXT2 e These fields are written to the control record 0010 in every outbound transaction e This data can be mapped to a standard transaction field by the Translator if required e These fields are not examined by the Oracle e Commerce Gateway for inbound transactions Descriptive Flexfields in Oracle e Commerce Gateway Oracle e Commerce Gateway standard mapping contains a selection of flexfields that allow for the transmission of additional data outbound inbound if that data has its origin or destination in activated flexfields within the Oracle Applications e The availability and transaction level header line shipment etc of these flexfields in the Oracle e Commerce Gateway is dependent on the transaction involved It cannot be assumed that every transaction will alw
100. United States of America 24 hours a day seven days a week For TTY support call 800 446 2398 Documentation Accessibility Our goal is to make Oracle products services and supporting documentation accessible with good usability to the disabled community To that end our documentation includes features that make information available to users of assistive technology This documentation is available in HTML format and contains markup to xi facilitate access by the disabled community Accessibility standards will continue to evolve over time and Oracle is actively engaged with other market leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers For more information visit the Oracle Accessibility Program Web site at http www oracle com accessibility Accessibility of Code Examples in Documentation Screen readers may not always correctly read the code examples in this document The conventions for writing code require that closing braces should appear on an otherwise empty line however some screen readers may not always read a line of text that consists solely of a bracket or brace Accessibility of Links to External Web Sites in Documentation Structure xii This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control Oracle neither evaluates nor makes any representations regarding the accessi
101. after the seeded columns on a record or even written to another record to minimize the impact on existing data maps The Internal code conversion field numbered 0 must not be altered The 0 is an indicator that this field is the Internal code for the Oracle Application e Any changes to the interface file definition must be synchronized with the mapping to the Translator e Removing fields is a simple action but the implications of finding that the fields are required at a later date will affect the Translator mapping and also may affect the Transaction Specification agreement with Trading Partners Refer to Modify Transaction Interface File page 4 23 for guidelines on changing transaction interface file definitions Interface Data File Processing The file produced by Oracle e Commerce Gateway for outbound transactions and imported by it for inbound transactions is a flat text file It may be manipulated by standard editor or programming languages such as SQL and COBOL Because of this the file may for example be padded in the case of transmission via software that requires fixed length fields For inbound transmissions data may be added by reference to the Oracle Applications or third party tables in the case where data is missing from the inbound transactions or data such as tax coding needs to be added based upon specific geographic supply sources 4 22 Oracle e Commerce Gateway Implementation Manual Oracle e Commerce Gate
102. and Column Rules and Actions 0 00 c ccc eee terete ete eteeteeeeies 4 13 Enable Additional Transaction Data 00 ccc cece cee eee ee eee e ete eee ta ae secee eet ae eetaaeeeenees 4 20 Modify Transaction Interface File 0 0 0 0 ccccecc cece ceee eens eee cee ec eeeeaeeeeeseaessaeeesaessaeeeeeeaaes 4 23 Synchronize New Transaction Layout Definitions with Translatot 0 0 0cccee 4 28 Common Transaction Interface File Definition Errors 00 0 000cccceec eee eee etree tees tees 4 28 Set Up Trading P rtheis i fis ius sasha hades eds A ENAA E A EA EAA ER E AE E aA EREN Taaie 4 28 Common Setup Errors iiem eve denecsis dette cove detestegaueatecatues cestatanael aa raah saaie aaia meatag us a 4 29 Set Up Code Conversi terenie eaan a et a a e e ei Eee aeea aae 4 30 Interface with TranslatotS yiida naaa aa a aaa aeti 4 30 Commiini cations aeea eieiei iiia ii ia aE E EEAS 4 33 Archive Bachuip tini e aea aiaei aE E SA E EE i 4 34 5 Transaction Interface File Architecture File Structure Overview zc cscs vss cei ec raa eiia AAA aga aap N A Taa A ate ae 5 1 Interface Data File Structttre 4 2 0 4he ngaa anata nl Khia aes 5 4 Special Records isis siccscisisaciseesteccesedd socsadaestds sete dads aaa a E Eaa eia apia aaa ste at aaan ties 5 7 Optional Outbound Trading Partner Flexfield Records 0020 0070 e eee 5 15 Common Record Key 1 100 0 0 0 0 cocci eee a idi 5 15 Common Records Based on R
103. and using alerts Oracle Applications System Administrator s Guide Security describes User Management data security function security auditing and security configurations Oracle Alert User s Guide This guide explains how to define periodic and event alerts to monitor the status of your Oracle Applications data Other Implementation Documentation Oracle Assets User Guide This guide provides you with information on how to implement and use Oracle Assets Use this guide to understand the implementation steps required for application use including defining depreciation books depreciation method and asset categories It also contains information on setting up assets in the system maintaining assets retiring and reinstating assets depreciation group depreciation accounting and tax accounting budgeting online inquiries impairment processing and Oracle Assets reporting The guide explains using Oracle Assets with Multiple Reporting Currencies MRC This guide also includes a comprehensive list of profile options that you can set to customize application behavior Oracle Applications Multiple Organizations Implementation Guide This guide describes the multiple organizations concepts in Oracle Applications It describes in detail on setting up and working effectively with multiple organizations in Oracle Applications Oracle Applications Flexfields Guide This guide provides flexfields planning setup and reference informatio
104. are accessed for the given data element The Code Conversion Categories window lists predefined categories or new categories that you created The code categories are used to enable a data element for code conversion in the Assign Categories window You also indicate in this window how many search keys you will use in Code Conversion Values window for that category of data A search key is a data element that limits the use of the code conversion table entry to a specific Trading Partner Trading Partner site or other entity that you define For example customer ACME their Chicago site has 10 4 Oracle e Commerce Gateway Implementation Manual its own list of carrier codes The search keys would have the first key value to represent Acme Corporation and the second search key value to represent their Chicago site Assign Categories Window The Assign Categories window lists which data elements in the transaction are candidates for code conversion These are the only data elements in a transaction that you can enable for code conversion A data element is enabled for code conversion by entering a code category next to the data element in this window You will also indicate the 1 5 source column names from the transaction that contains the actual data that you want reviewed as the 1 5 search keys if you use keys In the previous window Code Conversion Categories window you also enable the corresponding 1 5 search keys by checking the appro
105. are made such as additional data added to the transaction Current transaction details can be found on Oracle Support s web site Current detail record layouts are reported via the Transaction Layout Definition Report and the Interface File Data Report Note See Oracle Order Management Transaction Summaries page A 9 for layout details Inbound Purchase Order POI 850 ORDERS This transaction is the inbound purchase order from the customer s procurement application into the Oracle Order Management application This transaction uses the Order Management Order Import open interface Trading Partner Link to Oracle e Commerce Gateway Customers and Customer sites are defined in either Oracle Receivables or Oracle Order Management Included in the definition is the EDI Location Code that trading partners agree to exchange to represent the full detailed address Often they do not send the full address but just the EDI Location Code This is a critical data field to Oracle e Commerce Gateway The EDI Location Code is the link between a Customer Customer site in Oracle Applications and the trading partner site definition in Oracle e Commerce Gateway This enables Oracle e Commerce Gateway to access the detailed data about the Customer or Customer site in the base Oracle Applications without maintaining the detail data in Oracle e Commerce Gateway To ensure that the trading partner link between Oracle e Commerce Gateway and Oracle Application
106. be used in the code conversion value tables Since keys 1 5 are blank and the 3 table entries did not apply all code conversion enabled data elements will find the 4 table entries given the external codes as part of the key Not finding a value in the code conversion table is not an error There may be cases where only select values for a data element need code conversion To require all values to have a code conversion table entry may cause you to do an excessive number of code conversion entries that are not necessary or desired Understanding Code Conversion for Inbound Transactions using Direction IN For inbound transactions the entire search key to access the table consists of the following Category Direction Keys 1 5 External Codes 1 5 Code Conversion 10 13 This full search key is used to find a table entry for the internal code that can be copied to the base Oracle Application s open interface table During code conversion for inbound transactions code conversion table entries marked with the direction IN and BOTH are read See section below on the direction BOTH page 10 15 Code conversion table entries which are given the direction IN are accessed during code conversion for inbound transactions only Entering the direction IN allows you to enter the entire search key for inbound transactions yet allows duplicate data to be entered for the Internal codes e Inbound Transaction Entire Search Key Must b
107. by the Translator Code EDI Location Code combination in the Trading Partner set up If they are different then this rule is violated e Invalid Document Address There are several procedures which validate and derive different types of addresses Ship to Bill to Sold To etc If one of these procedures are unable to derive a unique address site then this rule is violated This validation occurs for all the key address sites associated with the transaction except for the location code on the control record e Seeded Process Rules Each inbound transaction is seeded with the three process rules outlined above In addition each rule is seeded with a default rule action of Skip Document that tells Oracle e Commerce Gateway to skip the current document and proceed to the next document if a process rule exception is detected You can change the corresponding process rule action if the default behavior is not desired see below regarding Rule Actions Column Rules Column rules are defined at the column level and apply to a specific data element of a given transaction Except for the seeded column rules see below regarding Seeded 4 14 Oracle e Commerce Gateway Implementation Manual Column Rules column rules are not required If they are used you must define an associated rule action that tells Oracle e Commerce Gateway how to proceed if a column rule exception is detected The same set of rule actions available for process rules a
108. can easily separate transactions into different files if the transactions are segregated into different Trading Partner electronic mailboxes or envelopes or at least separated by functional groups within the electronic envelope For instance for an X12 transaction the element Application Receiver s Code GS03 is often used for this sort of routing Since Trading Partners do not want to incur the cost of additional electronic mailboxes they may be willing to separate the transactions into different functional groups within an existing electronic envelope provided they can isolate the transaction in their processes Another feasible solution to separate transactions by their organization code is to have the Trading Partner create the transactions in separate address locations that are in synchronization with your organization definitions If you have a single physical address that you have defined to two or more organizations you may request that your Trading Partner also distinguish the locations within their application They can define a unique address site in their application so a different Location Code may be assigned to each location even if it has the same physical address This location set up will allow their EDI translator to separate the transactions to different electronic envelopes or functional groups within the electronic envelope Consequently transactions can be processed into different organizations The following table sh
109. choose from many sources of information including online documentation training and support services to increase your knowledge and understanding of Oracle e Commerce Gateway This book is included on the Oracle Applications Documentation Library which is supplied in the Release 12 Media Pack You can download soft copy documentation as PDF files from the Oracle Technology Network at http otn oracle com documentation or you can purchase hard copy documentation from the Oracle Store at http oraclestore oracle com The Oracle Applications Release 12 Documentation Library contains the latest information including any documents that have changed significantly between releases If substantial changes to this book are necessary a revised version will be made available on the virtual documentation library on Oracle MetaLink For a full list of documentation resources for Oracle Applications Release 12 see Oracle Applications Documentation Resources Release 12 OracleMetaLink Document 394692 1 If this guide refers you to other Oracle Applications documentation use only the Release 12 versions of those guides Integration Repository The Oracle Integration Repository is a compilation of information about the service endpoints exposed by the Oracle E Business Suite of applications It provides a complete catalog of Oracle E Business Suite s business service interfaces The tool lets users easily discover and deploy the appropriate busines
110. columns to examine for the actual search key values You decide which columns are used as the Key1 through Key5 The following were set up for this transaction e Column is CARRIER_INT e The Category SHIP_VIA is assigned to CARRIER_INT to enable code conversion e Key 1 is assigned the CUSTOMER_NAME column in the transaction table e Key 2 is assigned the CUSTOMER_SITE column in the transaction table You selected the keys from a list of values The full search key to access the code conversion value table for outbound transactions include the code category direction Key 1 Key 2 and the internal code For example the first entry in the table includes the following search key values See the sample Code Conversion Value Table page 10 32 for all entries e Key 1 has value ALPHA for the CUSTOMER_NAME e Key 2 has value 1006 for the CUSTOMER_SITE The Code Conversion Value window includes the search key values applicable to the internal and external codes for all the Trading Partners and all transactions The Category that you assign to a column limits the access to just those table entries that have been assigned that Category Creating the Search Key The table below has data found in the transaction or derived by the Oracle e Commerce Code Conversion 10 35 Gateway The data was moved to the transaction columns in the Oracle e Commerce Gateway process Data Data Transaction Data Description Customer Customer Site Ca
111. data element has seeded column attributes for record number position width sequence layout code layout qualifier process rules and column rules Any one of these column attributes may be changed as necessary with the following guidelines Do not change the column attributes of the common key in any record The Interface File Definition window prevents this so this guideline applies to custom coding only Do not change the column attributes of the control record Do not use detail level record numbers in header records Do not repeat record numbers within or outside the same data level Do not repeat position numbers within the same record Define a column width less than or equal what Oracle Applications supports to prevent data from being truncated Make sure the total length of the record does not exceed 1024 bytes with the first 100 bytes reserved for the common key Do not use sequence number 0 as it is reserved for the data element s internal value Make sure the external fields defined for code conversion are uniquely sequenced from 1 to 5 If you change a layout code make sure you make the same change for every data element in the record The layout code from the first data element in the record is Implementation Details 4 25 written to the transaction interface file e If you change a layout qualifier make sure you make the same change for the related data elements in the record The layout qualifier from the fir
112. define your trading partners and get a better understanding of how these fields are used in the process Review Oracle e Commerce Gateway Exceptions Use the Oracle e Commerce Gateway View Staged Documents window to review the Oracle e Commerce Gateway transaction exceptions Once the exceptions are identified and resolved you can submit the transaction for reprocessing ignore the exception during reprocessing or delete the transaction Select the option in the View Staged Documents window Resolve Oracle e Commerce Gateway Exceptions To resolve Oracle e Commerce Gateway exceptions you can either correct the set up data in Oracle e Commerce Gateway or Oracle Applications or ask the Trading Partner to send a corrected transaction If the Trading Partner sends a corrected transaction be sure to delete the erroneous transaction from Oracle e Commerce Gateway s staging tables using the View Staged Documents window The duplicate transaction may cause confusion Relevant Oracle Purchasing Inventory Profiles and Setups The following is a list of the Purchasing setups related to the Purchasing Documents Open Interface Refer to the Oracle Purchasing User s Guide for details 1 PO Archive Catalog on Approval e If the profile option is set to Yes Oracle Purchasing archives the price sales catalog once it is approved e This profile option works in conjunction with the Approval Status parameter If the Approval Status was set to Inc
113. e If both the customer generic items and the supplier inventory item are sent in the transaction compare the supplier item in the transaction to the derived internal supplier inventory item to be equal If the supplier item in the transaction and the derived vendor inventory item do not equal display an error and use the derived internal supplier inventory item in the order The discrepancy should be discussed with the customer to determine the accurate supplier time and have the customer update their tables if necessary e If only the supplier inventory item is sent validate it Inventory Tables Three Oracle Inventory tables contain various item data customer item cross reference data generic inventory items cross reference data and the internal supplier inventory items The first two tables will be searched to cross reference the items in the transaction to the internal inventory item Define all the cross reference items and the internal inventory item in Oracle Inventory before running the e Commerce Gateway inbound purchase order process and Order Import Table Content Navigation Customer Cross Reference table MTL_CUSTOMER_ITEM_XR EFS MTL_CUSTOMER_ITEMS Inventory Item Cross Reference generic table MTL_CROSS_REFERENCES Customer specific items to cross reference to internal supplier item Generic inventory items such as UPC codes ISBN codes and EAN codes to cross reference to internal supp
114. er an Caja ajam fi ge ajm eas i A z be Oracle Oracle Open Oracle e Commerce Flat File EDI Translator EDI Message Applications Interface Gateway Received Oracle e Commerce Gateway resides between Oracle Applications and a translator and processes data using ASCII interface files The EDI Translator accommodates the EDI standards such as ASC X12 and EDIFACT and monitors transmitting standard formatted data between Trading Partners The format and content of this file can be adjusted using the Interface File Definition window within Oracle e Commerce Gateway though any changes must be implemented within the EDI Translator s data map and set up An EDI Translator data map may be defined to produce a transaction according to the recommendations of any industry guideline such as UCS EIDX or AIAG A data map may accommodate the data requirements of a single trading partner or many trading partners Oracle e Commerce Gateway processes data via the transaction interface file that is received from or sent to the Translator Oracle e Commerce Gateway is independent of all standard formats since only the business data is found in the Oracle e Commerce Gateway transaction interface files Oracle e Commerce Gateway does not have communication software to transmit the standard formatted data between trading partners Oracle e Commerce Gateway relies on the Translator being connected to third party communication service providers to transmit data to
115. for the given transaction This is usually found in the ASC X12 N104 ID code or the EDIFACT NAD segment This code is maintained in the Oracle Application 5 12 Oracle e Commerce Gateway Implementation Manual Seq Data Element Value Note 16 17 18 19 20 Trading Partner Description TP Reference 1 TP Reference 2 Transaction Date Time Transmission Run ID This is the Trading Partner description as defined in Oracle e Commerce Gateway for outbound transactions or by the Translator for inbound transactions This is the Trading Partner reference 1 code defined in Oracle e Commerce Gateway for the primary Trading Partner location for outbound transactions This is the Trading Partner reference 2 code defined in Oracle e Commerce Gateway for the primary Trading Partner location for outbound transactions This is the date and time that the transaction is created by Oracle e Commerce Gateway or the Translator Run ID from the Concurrent Manager which created the transaction Transaction Interface File Architecture 5 13 Seq Data Element Value Note 21 22 23 24 25 Organization ID from inbound transaction Document Standard Control Number 1 from inbound external transaction Control Number 2 from inbound external transaction Control Number 3 from inbound external transaction This is the internal id associated with the
116. for the shipment within a line in the 6 18 Oracle e Commerce Gateway Implementation Manual order This field is used for matching the line s schedules in subsequent transactions to the current order s schedules in Order Management Often the current request date is the value used ORIG_SYS_SHIPMENT_REF shipment indicator must be unique within the ORIG_SYS_LINE_REF line indicator within the purchase order that is identified by the ORIG_SYS_DOCUMENT_REF header indicator The same customer request data may be entered for several ship to locations To guarantee uniqueness concatenate the ship to EDI LOCATION code to the date For example the customer request date in the transaction ship to EDI location code would be 120000308 CHIC 02 A character such as the plus sign between each component improves readability The ORIG_SYS_LINE is derived by the POI program or generated by a process such as the EDI Translator before the order is imported into the Order Import tables The customer does not send it in the transaction as the Original System Shipment Reference field Sample Original System Shipment Reference Original System Shipment Reference Original System Shipment Reference 19990308 000000 CHIC 01 19990308 000000 CHIC 01 Default Default Current Request Date includes time Ship To EDI_LOCATION CODE 19990308 CHIC 01 Note The user may enter data in this field or use the default that is the CUSTOMER_REQUEST_SYSDATE
117. guideline for this second phase would be one day of testing for each day of modification The following table represents a project timeline for a simple implementation project The resources for the project are the Customer EDI Implementer and an Experienced Oracle e Commerce Gateway Implementer An X indicates that the resource participates in that phase of the project Simple Implementation Project Timeline Phase Time Days Customer EDI Experienced Oracle Implentor e Commerce Gateway Implementor Training 2 X X Project Definition 10 X X Setups 2 X X Testing 10 X X Modification TBD X X Moving to Production 5 X N A Status Production 15 X X Status Ongoing Support Implementation Positioning 2 9 3 Oracle e Commerce Gateway Implementation Checklist This chapter contains Oracle e Commerce Gateway implementation steps and checklists This chapter covers the following topics e Implementation Steps e Implementation Checklist for Software Upgrade e Implementation Checklist for Fresh Install Implementation Steps The following is a list of the implementation steps to implement a transaction in Release 12 Since the total solution requires other Oracle Application modules as well as a Translator references to these products are included There are two possible starting points when implementing a transaction they are as follows e Upgrading from Release 11i to Release 12 Important For the Release 1
118. header record may have multiple Header Allowance and Charges Records and Invoice Item Records The item records may have multiple Line Tax and Item Allowances and Charges Records This structure is further described in the table below The following table shows the content and occurrences of the records comprising the Outbound Invoice transaction Record Occurrences Within the INO Transaction Records Contents Occurrences 0010 Control Records Only one record occurrence per transaction 0020 0070 Gateway Flexfields One set of records per transaction 1000 3900 Invoice Header Records Only one record occurrence per transaction 4000 5900 Invoice Line Records One set of records per line within the invoice header 6000 7900 Invoice Line Detail Records One set of records per item within the invoice line The following table is a summary list of the records that comprise the Outbound Invoice Transaction Summary Layouts A 185 transaction The table shows the functional data grouping of records the data level the record numbers and relevant notes about the data grouping INO Transaction Record Summary Data Data Level Record Number Note 1 Control Record HEADER 0010 2 Trading Partner HEADER 0020 0050 Custom Header Flexfields 3 Trading Partner HEADER 0060 0070 Custom Detail Flexfields 4 Bill To Address HEADER 1000 Code 5 Bill to Misc HEADER 1010 1015 Data Contacts 6 Bill to Customer HEADER 1020 1050 Flexfields
119. if applicable Line Original System Customer Line 001 the default Number Line Reference Line Original System Shipment 6 copied into the Number transaction Shipment Reference 6 20 Oracle e Commerce Gateway Implementation Manual Order in base Order tables Document Reference PO Order in base Order tables Line Reference line number Order in base Order tables Shipment Reference shipment number Change Order Data in Order Import Document Reference PO Change Order Data in Order Import Line Reference line number Change Order Data in Order Import Shipment Reference shipment number Note on Matching change order to order in base order tables 86420 03 86420 03 86420 03 001 001 001 86420 03 86420 03 86420 03 001 001 001 Change order data match to Line 001 shipment 1 in the base order No change order data found for Line 001 shipment 2 Do not update the record in the base order Change order data match to Line 001 shipment 3 in the base order Change order data not match to base order line 001 shipment number 4 Add line 1 shipment number 4 Application Transaction Detail 6 21 Order in base Order tables Document Reference PO Order in base Order tables Line Reference line number Order in base Order tables Shipment Reference shipment number
120. in the associated interface table It is used to maintain the link between the two tables Simple SQL DDL statements like the ALTER TABLE command may be used to add columns to the desired extension table For example suppose a business assigns a material analyst to each purchased item to determine data like item specifications tolerances and quality standards Further suppose that the business has created a custom database table to hold the data about the material analyst calling it MATERIAL_ANALYSTS The business wishes to send contact data from this custom table with each Purchase Order line in the event that the vendor has any item related questions specifically data from the following columns in the custom table e MATERIAL _ANALYST_CODE e MATERIAL ANALYST_LAST_NAME e MATERIAL ANALYST_FIRST_NAME e MATERIAL _ANALYST_PHONE e MATERIAL ANALYST_EMAIL First locate the proper extension table in the database The Oracle e Commerce Gateway interface table that holds Purchase Order line data is ECE_PO_INTERFACE_LINES and the corresponding extension table is ECE_PO_INTERFACE_LINES_X As installed the interface and extension tables may be illustrated as shown below The ECE_PO_INTERFACE_LINES_X table has only the Transaction Record ID column Extensible Architecture 11 7 Oracle e Commerce Gateway Interface and Extension Tables for Purchase Order Line Data ECE PO INTERFACE LINES Legend ECE_PO_INTERFACE_LINES_X a Unique ID
121. it is lost or deleted The first level is the backup of the Oracle database performed by the DBA and makes sure that changes made to the applications in the database from any source are preserved for any needed recovery The second level is the backup of the entire system performed by the system administrator This backs up the files from the operating system level whether they are part of the database or not The strategy you choose for these functions is the first step to determine how much archiving needs to be done The Oracle e Commerce Gateway often needs another level of archiving Once the data has been extracted from the base application into a transaction interface file and again once that transaction interface file has been processed into a transaction file by the Translator these files should be preserved The first reason is to save them as an audit trail showing what data was sent through the process to the trading partner This audit trail also serves to identify the transformation done by the Oracle e Commerce Gateway and the Translator so that you can correct the conversions they do The second reason is that there may be legal constraints in the trading partner s country and or industry which require commercial documents to be kept for a period of months if not years It is also possible that the trading partner s industry sector may deal in huge value or high risk goods e g aerospace in which case secure archiving of transact
122. layouts for the transaction and make any necessary adjustments Run Transaction Layout Definition Report to get the current definitions Synchronize the data maps in the Translator with the transaction interface file definitions Ensure that Location Code is defined for the trading partner entity customer site supplier site bank branch internal location defined in Oracle Applications Reference IM Implementation Manual IM Determine Process and Column Rules and Actions IM Enable Additional Transaction Data User s Guide Changing the Interface Data File Record Layout IM Modify Transaction Interface File User s Guide Reports IM Interface with Translators IM Application Transaction Detail Oracle e Commerce Gateway Implementation Checklist 3 5 Step Required Optional 17 Required 18 As Needed 19 Required 3 6 Oracle e Commerce Gateway Implementation Manual Description Reference IM Implementation Manual Define trading IM Set Up Trading partner Partner Assign trading Trading Partner partner to address site in Oracle Applications using Define Trading Partner Assignment tab Define translator code using Define Trading Partner Details tab This is the link to the Translator definition for the trading partner Enable transaction s for trading partner s Set up code IM Set Up Code conversions Conversion Review define Code Code Conversion Conversio
123. layouts are reported via the Transaction Layout Definition Report and the Interface File Data Report Inbound Shipment and Billing Notice SBNI 857 No EDIFACT Refer to the Oracle Purchasing section page 6 95 for details regarding this transaction Outbound Application Advice ADVO 824 APERAK Trading Partner Link to Oracle e Commerce Gateway Suppliers and supplier sites are defined in either Oracle Purchasing or Oracle Payables Included in the definition is the EDI Location Code that trading partners agree to exchange to represent the full detailed address Often they do not send the full address but just the EDI Location Code This is a critical data field to Oracle e Commerce Gateway The EDI Location Code is the link between a supplier supplier site in Oracle Applications and the trading partner site definition in Oracle e Commerce Gateway This enables Oracle e Commerce Gateway to access the detailed data about the supplier or supplier site in the base Oracle Applications without maintaining the detail data in Oracle e Commerce Gateway To ensure that the trading partner link between Oracle e Commerce Gateway and Application Transaction Detail 6 65 Oracle Applications is set up properly verify that the supplier supplier site and the EDI Location Code in Oracle Applications is the correct supplier supplier site selected for the Trading Partner definition in Oracle e Commerce Gateway The selected supplier supplier site and the E
124. level of information they need i e LOW MEDIUM or HIGH The amount of trace data that is generated varies depending on the level of trace chosen The levels are LOW This is the lowest level of tracing data This level displays data like Customer Supplier Name purchase order number name etc for a given transaction MEDIUM In addition to the data displayed at the LOW level this level displays data about the major processes being executed for the transaction If a process is failing the user can look at the output to determine which process is failing using this level HIGH This is the highest level of tracing data In addition to the data displayed at the LOW and MEDIUM levels this level shows all the major processes sub processes actual program variables and their values This level may not be suitable for most users It is designed more for a developer to use in researching difficult to fix problems All output regardless of the level is written to the log file that is created by the concurrent manager and is indented for each sub process performed to allow for ease of research Note For the Outbound Payment transactions instead of using the parameters window for the concurrent request you need to set them out in the ECE_PYO_DEBUG_MODE profile option for debug purposes Error Messages The error messages listed in the tables below are divided into two categories The first category is a list of common error mes
125. line item level TERMS_NAME This column represents the payment terms and is required if you did not define payment terms for the supplier AP_INVOICE_LINES_INTERFACE Table The following table lists the required fields for the AP_INVOICE_LINES_INTERFACE table Oracle Cond Oracle Hardcoded Record Position Applications e Commerce Derived Number Number Column Gateway Name for Column Required Name Fields LINE_TYPE_ LINE_TYPE_ 3000 10 LOOKUP_C LOOKUP_C ODE ODE AMOUNT AMOUNT 3000 110 PO NUMBE Yes PO_NUMBE 3010 10 R R INVOICE_ID Derived LINE_NUMB Derived ER AMOUNT This column represents the invoice distribution amount If the Invoice Match Option indicated on the transaction interface file is Purchase Order this column is the quantity invoiced multiplied by the unit price If the Invoice Match Option indicated on the transaction interface file is Receipt this amount is distributed across the non invoiced receipts beginning with the oldest If the Application Transaction Detail 6 85 invoice amount exceeds the total amount for the non invoiced receipts the overage is applied to the newest non invoiced receipt LINE_TYPE_LOOKUP_CODE This column identifies the invoice line type The valid values are ITEM TAX FREIGHT or MISCELLANEOUS PO_NUMBER This column represents the purchase order to match the invoice to Purchase order numbers may be entered at the header or line item level Review Payable
126. maintaining the detail data in Oracle e Commerce Gateway To ensure that the trading partner link between Oracle e Commerce Gateway and Oracle Applications is set up properly verify that the supplier supplier site and the EDI Location Code in Oracle Applications is the correct supplier supplier site selected for the Trading Partner definition in Oracle e Commerce Gateway The selected supplier supplier site and the EDI Location Code defined in Oracle Applications are displayed in the Define Trading Partners window Assignment tab If the data is not what you intend it to be you must make the appropriate changes for the transaction to be extracted for the correct trading partner This could involve either altering the supplier supplier site in the base Oracle Application or assigning a different supplier supplier site to that EDI Location Code in Oracle e Commerce Gateway Please note that if the trading partner is associated with multiple operating units then the transaction to be extracted is for a specified operating unit only linked to your responsibility To extract all the data for multiple operating units you still need to execute the program one by one by specifying different operating unit each time when you run the program See the Outbound Transactions chapter in the Oracle e Commerce Gateway User s Guide for details Refer to the Trading Partner chapter for recommendations on selecting the correct trading partner EDI Location Code for
127. nE aeia o aai EE E AATE 9 16 Organizations in Oracle Application Open Interface Tables 0ssneseneseseseseeeeeerrereeen 9 23 Trading Partner WindOWS cieciu neinir e ataa e o i a pekia erii iaeia 9 23 Code Conversion Code Conversione oneni i e iat A TEA ET A E A A R 10 1 Concatenated Search Key for Inbound Transactions sssssesssesenissrresrnesrrrssrrnsrreseresre 10 29 Concatenated Search Key for Outbound Transactions 0 000cc cece eee tee rset teen tneetaes 10 34 Extensible Architecture Customizing EDI Transactions sbin aehd seisein aranana eaten ieina aaiae atian 11 1 Descriptive FleyxfieldS iirc niione aiae a arrana aaia a iaar aea Eiaeai 11 2 Steps for Extensible Architecture snssnnssssinsnssiitesrnstisrinrinsrnstisrnnninsrnntnsrinnnnsrnnennrenern ne 11 5 A Transaction Summary Layouts vi Oracle Inventory Transaction Summaries 0 0c ccc eee ee ete eee tena ree eteeeeeneeseneseeeeenee A 1 Oracle Order Management Transaction Summaries s ssenesiseissirsirerrseierirsrnsnnrierensrene A 9 Oracle Payables Transaction Summaries ssssesesssinseisrintissinerisrinrissrnnrisrnnrnsstnnrrerenen ent A 71 Oracle Process Manufacturing Transaction Summiaries 0 0 00 ccs eee eter eee etees A 101 Oracle Purchasing Transaction Summaries 00 0cccc eee ee eee eee eee eteeeeneeteeeteneneneates A 102 Oracle Receivables Transaction Summaries 0 c ccccee
128. on selecting the correct trading partner EDI Location Code for the control record 0010 for the transaction in the transaction interface file Relevant Oracle Purchasing Profiles and Set Ups Extract Criteria The following is a list of the Purchasing set ups related to the outbound Purchase Order Change transaction Archive on lt Attribute gt for change orders In the Setup gt Purchasing gt Document Types window set the following e Set the Archive on Approve for each document type enabled DO NOT set the attribute to Archive on Print This prevents the eligible purchase orders from being extracted since they will print and archive before the extract can happen Refer to the Oracle Purchasing User s Guide for the details The outbound Purchase Order Change transaction is controlled by three database views that are defined according to the Oracle Purchasing data model for purchase orders The three views contain variables which are dynamically set based on your responses to the extract program parameters refer to Oracle e Commerce Gateway User s Guide Outbound Transactions chapter for a list of the program parameters The three database views are as follows e ECE_POCO_HEADERS V e ECE_POCO_LINES_V e ECE_POCO_SHIPMENTS_V The ECE_POCO_HEADERS_V view is used to identify which purchase order changes Application Transaction Detail 6 125 are eligible for extraction The extract criteria are as follows e Trading par
129. or debit memo enabled for the trading partner e Transaction type is invoice credit memo or debit memo e Transaction type invoice credit memo or debit memo has not been printed or previously extracted e Transaction type invoice credit memo or debit memo status is COMPLETE e Transaction type invoice credit memo or debit memo print option is PRI If necessary you can use SQLPLUS to verify if there are any eligible documents to be extracted To do so you must first set the organization context and then issue the SQL count function as follows SQLPLUS gt execute fnd_client_info set_org context lt Org number gt SQLPLUS gt select count ECE INO HEADERS V Review all your set ups if the count value is 0 as this indicates there are no eligible documents to be extracted Columns Updated Upon Extraction Once an eligible supplier invoice is successfully extracted and written to the transaction interface file it is marked by Oracle e Commerce Gateway to prevent it from subsequent extraction The following table lists the fields updated in the RA_CUSTOMER_TRX table based on an excerpt of code in the UPDATE_AR procedure defined in the ECEINOB pls file Column Value Updated To EDI_PROCESSED_FLAG Y EDI_PROCESSED_STATUS ED LAST_UPDATE_DATE SYSDATE PRINTING _COUNT increment 1 PRINTING_LAST_PRINTED SYSDATE 6 130 Oracle e Commerce Gateway Implementation Manual Column Value Updated To PRI
130. packing slip number from the supplier This number will be used during the PO receipt process to recall the shipment data related to the purchase orders and items in the shipment 6 112 Oracle e Commerce Gateway Implementation Manual If no value is provided the Receiving Open Interface tries to default a value from the PACKING _ SLIP or INVOICE _NUM columns The values in this column must be unique from the supplier for one year SHIPPED_DATE This column represents the date the shipment was shipped The value must be earlier than or equal to the system date SHIP_FROM_CUSTOMER_ID This column represents the vendor ID Oracle e Commerce Gateway derives this value based on the Translator Code on record 0010 element 70 and EDI Location Code on record 0010 element 80 combination The Receiving Open Interface uses the vendor ID to derive the vendor name and number SHIP_TO_INT_LOCATION_ID This column represents the destination organization for the shipment A valid inventory organization code in Purchasing is required for the Inbound Ship Notice Manifest or Inbound Shipment and Billing Notice transactions The destination organization code may be specified at the header or line level However if it is specified at the header level then the same value applies to all the shipment lines TRANS_PURPOSE_APPLICATION This column represents the transaction purpose code The valid values are NEW or CANCEL Place the value in record 1000
131. planning schedule is successfully extracted and written to the transaction interface file it is marked by Oracle e Commerce Gateway to prevent it from subsequent extraction The following tables lists the fields updated in the CHV_SCHEDULE_HEADERS table based on an excerpt of code in the UPDATE_CHV_SCHEDULE_HEADERS procedure defined in the ECSPSOB pls file Column Value EDI_COUNT Increment by 1 LAST_EDI_DATE SYSDATE LAST_UPDATED_BY 1 LAST_UPDATE_DATE SYSDATE COMMUNICATION_CODE see below COMMUNICATION_CODE is set based on the original value as shown in the 6 180 Oracle e Commerce Gateway Implementation Manual following table Original Extract Successful Set New COMMUNICATION_CODE COMMUNICATION_CODE BOTH Yes PRINT EDI Yes NONE Outbound Shipping Schedule SSSO 862 DELJIT Trading Partner Link to Oracle e Commerce Gateway Suppliers and supplier sites are defined in either Oracle Purchasing or Oracle Payables Included in the definition is the EDI Location Code that trading partners agree to exchange to represent the full detailed address Often they do not send the full address but just the EDI Location Code This is a critical data field to Oracle e Commerce Gateway The EDI Location Code is the link between a supplier supplier site in Oracle Applications and the trading partner site definition in Oracle e Commerce Gateway This enables Oracle e Commerce Gateway to access the detailed data about the supplier or
132. rules associated with the transaction record layout changes 4 4 Oracle e Commerce Gateway Implementation Manual For detailed information on how the Seed Data Reconciliation process works refer to the Oracle e Commerce Gateway User s Guide Set Up Profiles Recognizing that no two businesses operate in the exact same manner Oracle e Commerce Gateway provides users with profile options to configure their implementation This allows the user to set up an ERP environment that matches their business environment Oracle e Commerce Gateway supports two types of profile options system level profile options which are used by all transactions and transaction level profile options used by a specific transaction System level profiles are usually done as an initial set up whereas transaction level profile options are done as you implement a transaction System Profiles Initial Setup The following table lists the three system profile options The table also shows profile description category whether the profile option is required or optional and its default value System Profile Options System Profile Description Category Required Default Value Option ECE OUT_FILE_ Indicates the Deployment Yes No Default PATH directory to which outbound data files are written This value must match the actual directory on disk and is designated in the INIT ORA file Implementation Details 4 5 System Profile Option Descript
133. rules and configuration parameters then you can implement any of the pre built transactions Extensibility hooks are provided to integrate custom transactions and extend the Oracle e Commerce Gateway supported transactions by incorporating data from non Oracle Applications data sources Configurable Integration Environment Oracle e Commerce Gateway supports configurations at the system transaction trading partner and process levels giving you utmost control of your data interface files and business processes You can configure how data elements are validated and mapped the structure and layout of an interface file when a business process is initiated and how it should proceed Furthermore you can control the behavior of a process if an exception is detected All rules are stored in a repository to support dynamic run time message creation automated process monitoring and exception analysis Using a single window you can change a rule by changing the information stored in the Oracle e Commerce Gateway repository The updated rule takes effect at run time without any code modifications System level configurations apply to all transactions and include the following e Define inbound outbound file directory e Enable disable transactions e Define text wrapping rules Transaction level configurations apply to a specific transaction and include the Introduction 1 3 following e Validation Rules e Code Conversions e Tr
134. supplier site in the base Oracle Applications without maintaining the detail data in Oracle e Commerce Gateway To ensure that the trading partner link between Oracle e Commerce Gateway and Oracle Applications is set up properly verify that the supplier supplier site and the EDI Location Code in Oracle Applications is the correct supplier supplier site selected for the Trading Partner definition in Oracle e Commerce Gateway The selected supplier supplier site and the EDI Location Code defined in Oracle Applications are displayed in the Define Trading Partners window Assignment tab If the data is not what you intend it to be you must make the appropriate changes for the transaction to be extracted for the correct trading partner This could involve either altering the supplier supplier site in the base Oracle Application or assigning a different supplier supplier site to that EDI Location Code in Oracle e Commerce Gateway Please note that if the trading partner is associated with multiple operating units then the transaction to be extracted is for a specified operating unit only linked to your responsibility To extract all the data for multiple operating units you still need to execute the program one by one by specifying different operating unit each time when you run the program See the Outbound Transactions chapter in the Oracle e Commerce Gateway User s Guide for details Refer to the Trading Partner chapter for recommendations on select
135. table data elements in the output transaction interface file 11 18 Oracle e Commerce Gateway Implementation Manual A Transaction Summary Layouts This appendix contains transaction summary information for Oracle Applications about Oracle e Commerce Gateway implementation This appendix covers the following topics e Oracle Inventory Transaction Summaries e Oracle Order Management Transaction Summaries e Oracle Payables Transaction Summaries e Oracle Process Manufacturing Transaction Summaries e Oracle Purchasing Transaction Summaries e Oracle Receivables Transaction Summaries e Oracle Release Management Transaction Summaries e Oracle Shipping Execution Transaction Summaries e Oracle Supplier Scheduling Transaction Summaries Oracle Inventory Transaction Summaries The following Oracle Inventory transaction is summarized in this appendix Oracle Inventory Transaction Summaries Transaction Direction Transaction ASC X12 EDIFACT Name Code Movement Outbound MVSTO N A CUSDEC Statistics Transaction Summary Layouts A 1 Current Information The transaction file may change when enhancements are made such as additional data added to the transaction Current transaction summaries can be found on Oracle Support s web site Current detail record layouts are reported via the Transaction Definition Layout Report and the Interface File Data Report Outbound Movement Statistics INTRASTAT MVSTO No X12 CUSDEC
136. the Trading Partner needs to be notified that there was a problem with the transaction They may need to send a corrected transactions Description This message appears in the concurrent manager log file The filename that was entered on the Import Process parameters window contains no data type Description This message appears in the concurrent manager log file The filename that was entered on the Import Process parameters window contains no data Solution Confirm that the filename is correct or that the file is in the directory indicated in the Profile Options window and retransmit the data file 8 6 Oracle e Commerce Gateway Implementation Manual Message Description and Solution Please use a valid organization ID Description The Organization ID provided in the transaction is not defined in the HR_LOCATIONS_ALL table Note that it is unusual for a transaction to contain the Organization ID Solution The associated records with this document should be deleted from the View Staged Documents window The data cannot be corrected If the Trading Partner provided the Organization ID in the transactions inform them to correct the transaction and resend the data Troubleshooting 8 7 Message Description and Solution The incoming test flag is different from that set up for the Trading Partner Description This message appears in the View Staged Documents window and is a result of an impor
137. the United States Government or anyone licensing or using the Programs on behalf of the United States Government the following notice is applicable U S GOVERNMENT RIGHTS Programs software databases and related documentation and technical data delivered to U S Government customers are commercial computer software or commercial technical data pursuant to the applicable Federal Acquisition Regulation and agency specific supplemental regulations As such use duplication disclosure modification and adaptation of the Programs including documentation and technical data shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement and to the extent applicable the additional rights set forth in FAR 52 227 19 Commercial Computer Software Restricted Rights June 1987 Oracle Corporation 500 Oracle Parkway Redwood City CA 94065 The Programs are not intended for use in any nuclear aviation mass transit medical or other inherently dangerous applications It shall be the licensee s responsibility to take all appropriate fail safe backup redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes and we disclaim liability for any damages caused by such use of the Programs The Programs may provide links to Web sites and access to content products and services from third parties Oracle is not responsible for the availability of or any con
138. the control record 0010 for the transaction in the transaction interface file Application Transaction Detail 6 87 Extract Criteria The outbound Application Advice transaction is controlled by two database views that are defined according to the Oracle e Commerce Gateway data model for application advice data The two views contain variables which are dynamically set based on your responses to the extract program parameters refer to the Outbound Transactions chapter Oracle e Commerce Gateway User s Guide for a list of the program parameters The two database views are as follows e ECE _ADVO_DETAILS V e ECE_ADVO_HEADERS V The ECE_ADVO_HEADERS_V view is used to identify which application advice data is eligible for extraction The extract criteria are as follows e Trading partner is defined e Transaction type enabled for the trading partner e Application advice has not been previously extracted e Application advice provided by one of the following three inbound transactions e Ship Notice Manifest from Oracle Purchasing Receivables e Shipment and Billing Notice from Oracle Purchasing Receivables e Invoice from Oracle Payables Refer to the details for the relevant inbound transaction to determine how it populates the ECE_ADVO_HEADERS and ECE_ADVO_DETAILS tables If necessary you can use SQLPLUS to verify if there are any eligible documents to be extracted To do so you must first set the organization context and th
139. the detail data in Oracle e Commerce Gateway To ensure that the trading partner link between Oracle e Commerce Gateway and Oracle Payables is set up properly verify that the bank branch and the EDI Location Code in Oracle Payables is the correct bank branch selected for the Trading Partner definition in Oracle e Commerce Gateway The selected bank branch and the EDI Location Code defined in Oracle Payables are displayed in the Define Trading Partners window Assignment tab If the data is not what you intend it to be you must make the appropriate changes for the transaction to be extracted for the correct bank branch This could involve either altering the bank branch in the base Oracle Payables or assigning a different bank branch to that EDI Location Code in Oracle e Commerce Gateway Refer to the Trading Partner chapter for recommendations on selecting the correct trading partner EDI Location Code for the control record 0010 for the transaction in the transaction interface file Relevant Oracle Payables Profiles and Setups The outbound Payment Order Remittance Advice transaction is an event driven process initiated in Oracle Payables as a payment format after the invoices are selected and the payment batch is created This transaction cannot be initiated from Oracle e Commerce Gateway 6 68 Oracle e Commerce Gateway Implementation Manual The following is a list of the Payables set ups related to the outbound Payment Order Remittance Ad
140. time execution engine takes over and proceeds according to the system transaction and trading partner configurations you defined If necessary a user activated run time execution log is available to assist with trouble shooting This diagnostic tool supports multiple levels of trace details for both technical and non technical analysts View Transaction Exceptions The status of a transaction process and any reported exceptions may be viewed using a single workbench style window known as the View Staged Documents window Summary or detailed inquires are supported using tree style navigation Dynamic windows and drill downs are provided to help analyze the cause of an exception 1 6 Oracle e Commerce Gateway Implementation Manual Once the cause of the exception is identified and resolved you have the option to submit the transaction for reprocessing or treat the exception as a warning by ignoring or deleting the exception The status inquiry trouble shooting and re processing of transactions are all done in one single window the View Staged Documents window Several reports facilitate the implementation process Use the reports to view trading partner and code conversion data or review the seeded transaction layout definitions and the contents of a data file Transaction List Oracle e Commerce Gateway is independent of all EDI standards and can be integrated with any upstream or downstream process via an ASCII file It is this i
141. transaction contains a single Control Record and Credit Memo Debit Memo Header Record The header record may have multiple Header Allowance and Charges Records and Credit Memo Debit Memo Item Records The item record may have multiple Line Tax Records and Item Allowances and Charges Records This structure is further described in the table below The following table shows the content and occurrences of the records comprising the Outbound Credit Memo Debit Memo transaction Transaction Summary Layouts A 169 Record Occurrences Within the CDMO Transaction Records Contents Occurrences 0010 0070 e Commerce Gateway Only one record occurrence Control Records per transaction 1000 3900 Memo Header Records Only one record occurrence per transaction 4000 5900 Memo Line Records One set of records per line within the memo header 6000 7900 Memo Line Detail Records One set of records per item within the memo line The following table is a summary list of the records that comprise the Outbound Credit Memo Debit Memo transaction The table shows the functional data grouping of records the data level the record numbers and relevant notes about the data grouping CDMO Transaction Record Summary Data Data Level Record Number Note 1 Control Record HEADER 0010 2 Trading Partner HEADER 0020 0050 Custom Header Flexfields 3 Trading Partner HEADER 0060 0070 Custom Detail Flexfields 4 Bill To Address HEADER 1000 Code 5 Bill to
142. two sections as follows e Payables Open Interface Audit Report e Payables Open Interface Rejections Report The Audit section lists the invoices that were successfully imported while the Rejections section lists invoices that were not successfully imported and the reason for the rejection Refer to the Payables Open Interface Import section Oracle Payables User s Guide for a detailed list of the rejection codes and their meaning Return Application Advice to Supplier To return invoice acknowledgments to the supplier execute the Payables Open Interface Outbound Advice program to populate the Oracle e Commerce Gateway Application Advice tables ECE_ADVO_HEADERS and ECE_ADVO_DETAILS with the status of all supplier invoices processed Once the Application Advice tables are populated you can initiate the outbound Application Advice ADVO 824 APERAK transaction to acknowledge all invoices processed or just those containing exceptions Resolve Payables Open Interface Exceptions There are three ways to resolve Payables Open Interface exceptions as follows e Correct set up data in Oracle Applications e Correct erroneous entries in the Payables Open Interface table using Open Interface Invoices window e Request supplier to send a corrected transaction If you chose to update Oracle Applications data or change the erroneous entries using the Open Interface Invoices window in Payables you can resubmit the Payables Open Interface Import pr
143. units you still need to execute the program one by one by specifying different operating unit each time when you run the program See the Outbound Transactions chapter in the Oracle e Commerce Gateway User s Guide for details Refer to the Trading Partner chapter for recommendations on selecting the correct trading partner EDI Location Code for the control record 0010 for the transaction in the transaction interface file Application Transaction Detail 6 175 Relevant Oracle Shipping Execution Profiles and Setups There are no required setups in Oracle Shipping Execution for this transaction Extract Criteria Once the shipment is confirmed define a trip to specify the exact contents A trip may be a truck load containing x number of items in y number of boxes defined in z number of pallets After the trip is closed the shipping process initiates the transaction through the Oracle e Commerce Gateway This transaction is event driven by the shipping process it is not usually driven by a scheduled concurrent manager request However Oracle e Commerce Gateway can be used to extract the transaction again if necessary The outbound Shipment Notice Manifest transaction is formed by the following seven database views that are defined according to the Oracle Shipping Execution data model for the Shipment Notice Manifest transaction e WSH_DSNO_ALLOWANCE_CHARGES V e WSH_DSNO_CONTAINERS_V e WSH_DSNO_DELIVERIES_V header e WSH_DSNO_DELIV
144. 005 Alpha gr ALPHA J A ound 1 4 SHIP_VI OUT Beta Ove BETA A A right 1 4 SHIP_VI OUT Beta Gro BETA J A und Since keys 1 5 are blank these table entries may be retrieved for all 10 12 Oracle e Commerce Gateway Implementation Manual data elements assigned code category UOM for inbound transactions whose internal codes are listed above You may use external 1 for the X12 codes and external 2 for the EDIFACT codes External 3 5 may contain alternative codes for one of those standards or other standards Given the Trading Partner the translation data map will choose the desired internal and external data elements to use Since key 1 has the Document Standard Code only Trading Partners given the specific Document Standard Code showing in key 1 will access those records The default Document Standard Code is assigned to a Trading Partner s transaction via the Detail tab in the Define Trading Partner Since keys 1 2 are entered in the code conversion table those table entries are found only when the transaction has the values found in key 1 and 2 What data elements are represented by keys 1 5 are specified in the Assign Code Conversion Categories window for example they may be customer number and customer site number Select your column values based on the data elements that are available to you in that transaction In the illustration the customer number and customer site numbers were available in the transaction so they could
145. 040 MENT_REF MENT_REF ORIG_SYS_LOT ORIG_SYS_LOT Required 9000 050 SERIAL_REF SERIAL_REF ORDER_SOURC ORDER_SOURC Hard code 6 E_ID E_ID meaning EDI LAST_UPDATE LAST_UPDATE Derived D_BY D_BY 6 38 Oracle e Commerce Gateway Implementation Manual Oracle Oracle Hardcoded Deri Record Number Position Applications e Commerce ved Number Column Name Gateway for Required Column Name Fields LAST_UPDATE LAST_UPDATE Set to SYSDATE _DATE _DATE CREATION_DA CREATION_DA Set to SYSDATE TE TE CREATED_BY CREATED_BY Derived OE_HEADERS_INTERFACE Table CUSTOMER_PO_NUMBER This column represents the purchase order number for the customer purchase order being imported into Oracle Order Management The number need not be unique for the customer If the purchase order is a release the release number may be concatenated to the purchase order number separated by a dash for example PO1234 01 for purchase order PO1234 with release 01 If you concatenate the customer s purchase order number and release number you may impact the ORIG_SYS_DOCUMENT_REFERENCE See the illustration below Construction of CUSTOMER_PO_NUMBER Modified Purchase Order Number 86420 0 Constructed by the EDI Translator to load into Oracle Order Management Purchase Order Number from Customer s Purchasing Application Purchase Order Release Number from Customer s Purchasing Application 86420 03 Application Transaction Detail 6 39
146. 10 Numbers 6 Supplier Site HEADER 1020 Address Code 7 Supplier Site HEADER 1030 Phone 8 Ship to HEADER 1050 Address Code Transaction Summary Layouts A 231 Data Data Level Record Number Note 9 Ship to HEADER 1060 Miscellaneous Data 10 Schedule Header HEADER 1500 1530 Flexfields Flexfields 11 Vendor HEADER 1600 1630 Flexfields Flexfields 12 Vendor Site HEADER 1650 1680 Flexfields Flexfields 13 Shipping HEADER 1700 1730 Flexfields Organization Flexfields 14 Ship To Options HEADER 1750 1780 Flexfields Flexfields 15 Extension HEADER 1900 Custom Tables Purchase Order Header Data 16 Basic Item Data ITEM 2000 17 Product ITEM 2010 Description 18 Hazardous ITEM 2020 Material Codes 19 Contact Names ITEM 2030 20 Last Receipt ITEM 2040 Data 21 Ship To ITEM 2050 Organization Address Code A 232 Oracle e Commerce Gateway Implementation Manual Data Data Level Record Number Note 22 Ship To ITEM 2060 Organization Data 23 Approved ITEM 2100 2130 Flexfields Supplier List Flexfields 24 Item Flexfields ITEM 2150 2180 Flexfields 25 Ship To ITEM 2200 2230 Flexfields Organization Flexfields 26 Organization ITEM 2250 2280 Flexfields Option Flexfields 27 Schedule Item ITEM 2300 2330 Flexfields Flexfields 28 Extension ITEM 2900 Custom Tables Item Data 29 Forecast and ITEM DETAILS See updates Authorization Data 30 Extension ITEM DETAILS Custom Tables Forecast and Authorization Data Th
147. 10 14 Shipme nt Flexfiel d15 Item Level Flexfiel d 1 4 TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD DOC DOC DOC DOC DOC DOC DOC DOC LINE LINE LINE LINE LINE LINE LINE LINE 2210 2220 2230 2240 2250 2260 2270 2280 A2 A2 A2 A1 A2 A2 A2 A1 LN2 LN3 LN4 SH1 SH2 SH3 SH4 IT1 Transaction Summary Layouts A 109 Record TP_CD_ Ref 1 Ref 2 Ref 3 Record Record Record DOC ITEM blank Number Layout Layout Qualifie r 31 Item TP_CD DOC LINE 2290 A2 IT2 Level Flexfiel d 5 9 32 Item TP_CD DOC LINE 2300 A2 IT3 Level Flexfiel d 10 14 33 Item TP_CD DOC LINE 2310 A2 IT4 Level Flexfiel d15 Inbound Response to Request for Quotation RRQI 843 QUOTES A single transaction has the following data hierarchy and data looping RRQ Inbound Response to Request for Quotation Structure Control Record Response to RFQ Header Item Detail Item Deta Item Deta Record Numbers 0010 1000 1900 2000 2900 2000 2900 2000 2900 An Inbound Response to Request for Quotation transaction contains a single Control Record and Response to RFQ Header Record The header record may have multiple Item Detail Records This structure is further described in the table below A 110 Oracle e Commerce Gateway Implementation Manual The following table shows the content and occurrences
148. 1120 1150 Flexfields Flexfields 11 Supplier Site HEADER 1160 Address Code 12 Supplier Site HEADER 1170 1180 Contacts 13 Ship to HEADER 1190 Address code 14 Ship to Contacts HEADER 1200 15 Bill to HEADER 1210 Address Code 16 Bill to Contact HEADER 1220 17 Buyer Name HEADER 1230 Transaction Summary Layouts A 141 Seq Data Data Level Record Number Note 18 Buyer HEADER 1240 Communications 19 Procurement HEADER 1250 Card 20 Header HEADER 1800 Attachment ATTACHMENT Master HEADER 21 Header HEADER 1810 Attachment ATTACHMENT Detail DETAIL 22 Basic Item Data LINE 2000 23 Basic Item Data LINE 2010 24 Basic Item Data LINE 2020 Hazardous Material Codes 25 Item Note to LINE 2030 Supplier 26 Line Flexfields LINE 2040 2070 Flexfields 27 Line Part LINE 2080 2110 Flexfields Flexfields 28 Line Part LINE 2120 Segments 29 Line Part LINE 2130 Segments 30 Line Attachment LINE 2800 Master ATTACHMENT HEADER A 142 Oracle e Commerce Gateway Implementation Manual Seq Data Data Level Record Number Note 31 Line Attachment LINE 2810 Detail ATTACHMENT DETAIL 32 Master Item MASTER ITEM 2820 Attachment ATTACHMENT Master HEADER 33 Master Item MASTER ITEM 2830 Attachment ATTACHMENT Detail DETAIL 34 Inventory Item INVENTORY 2840 Attachment ITEM Master ATTACHMENT HEADER 35 Inventory Item INVENTORY 2850 Attachment ITEM Detail ATTACHMENT DETAIL 36 Basic Shipment SHIPMENT 3000 Data 37 Shipment SHIPMENT 3010 3040 Flexfi
149. 170 180 10 70 Schedule generation date Control number from the electronic envelope such as the X12 ISA or EDIFACT UNB assigned by the customer EDI translator for auditing The second level control number from the electronic transaction such as the X12 GS assigned by the customer EDI translator for auditing The third level control number from the electronic transaction such as the X12 ST assigned by the customer EDI translator for auditing Schedule types Planning Shipping or Sequenced Transaction Purpose Original Replace Cancel etc Application Transaction Detail 6 137 Oracle e Commerce Gateway Column Name for Required Fields Record Number Position Number Note SCHEDULE_SOURC E ITEM_DETAIL_TYPE _INT ITEM_DETAIL_SUBT YPE_INT DATE_TYPE_CODE_ INT START_DATE_TIME _DET QTY_TYPE_CODE_I NT ITEM_DETAIL_QUA NTITY UOM_CODE_INT_D 1000 4000 4000 4000 4000 4000 4000 4000 280 10 70 130 180 210 270 280 EDI or manual transaction for this schedule such as 830 862 866 DELFOR MANUAL etc Past Due Firm Forecast Authorization Shipment Receipt Data or Other Bucket Type Type of Authorization or Cumulative or Last Shipment Receipt Type of Start End Date SHIP DELIVER RECEIVED FROM_TO Customer specified date time ACTUAL or CUMULATIVE Requested quantity Abbreviated u
150. 1i version that are supported for upgrading to Release 12 see Oracle Applications Upgrade Guide Release 11i to Release 12 for details e Fresh install of Release 12 The purpose of the implementation checklist is to guide you through the implementation process The details for each step are described in the implementation section referenced or the corresponding Oracle reference manual Oracle e Commerce Gateway Implementation Checklist 3 1 Implementation Checklist for Software Upgrade Following is the implementation checklist presented in table format Presented in the table are the step number a required or optional indicator a description of the step and reference information Important For the Release 11i version that are supported for upgrading to Release 12 see Oracle Applications Upgrade Guide Release 11i to Release 12 for details Implementation Checklist for Software Upgrade Step Required Optional Description Reference IM Implementation Manual 1 Required Install Release 12 Oracle Applications Oracle e Commerce Installation Guide Gateway Using Rapid Install 2 Required Run the following User s Guide Reports reports for each transaction implemented in Release 11i to view the Release 12 transaction layout definitions and code conversion assignments after the upgrade Transaction Layout Definition Report Code Conversion Values Report 3 2 Oracle e Commerce Gateway Implementation Man
151. 2 A2 SS SS ST1 ST2 SH1 SH2 SH3 Transaction Summary Layouts A 249 Data Trading Partner Ref1 Ref2 Ref 3 SS ITEM SCHE DULE Record Number Record Layout Record Layout Qualifie r 17 18 19 20 21 22 23 24 25 Schedul e Header Flexfiel d15 Vendor Flexfiel ds 1 4 Vendor Flexfiel ds 5 9 Vendor Flexfiel ds 10 14 Vendor Flexfiel d15 Vendor Site Flexfiel ds 1 4 Vendor Site Flexfiel ds 5 9 Vendor Site Flexfiel ds 10 14 Vendor Site Flexfiel d15 TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD SS SS SS SS SS SS SS 5S SS 1530 1600 1610 1620 1630 1650 1660 1670 1680 A2 A1 A2 A2 A2 A1 A2 A2 A2 SH4 VN1 VN2 VN3 VN4 VS1 VS2 VS3 VS4 A 250 Oracle e Commerce Gateway Implementation Manual Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner SS ITEM SCHE Number Layout Layout DULE Qualifie r 26 27 28 29 30 31 32 Shippin 8 Organiz ation Flexfiel ds 1 4 Shippin 8 Organiz ation Flexfiel ds 5 9 Shippin 8 Organiz ation Flexfiel ds 10 14 Shippin 8 Organiz ation Flexfiel d15 Ship To Options Flexfiel ds 1 4 Ship To Options Flexfiel ds 5 9 Ship To Options Flexfiel ds 10 14 TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD
152. 20 Fidelity Inveetmente P D Box 93001 TERHE SCOTE ROSE ME V10C TE 617 86a B418 1220CmAT1 m1 BT Fidality Invastaenta 1230POPOIGUTIRIE WICEMEL 617 392 0259 2000TTITI1 1 Each EA 123 achf 2010TTIT2E Q iw QUANTITY 2020T8I73 3000 gt SCH 2030TTIT achf ardf h9k as1l prn F aohf ardf hk agi 2060RL LEI ACAI PR 002 28071261 2O50R2L52 rasi28 ZO60AZLES al ST Fidelity Iovestwant e zz 1 A00 OSRENIT 1 19980712 009400 mai cfo J J Daly 6 Tids Streat 302072602 T1 Boston MA 02110 203072603 FER DC GCOTT ROGE M3 Y10C TE 617 563 5410 3002504 Oracle e Commerce Gateway extracts outbound transaction data from application tables and loads inbound transactions into the base Oracle Application Open Interface tables The components of the outbound transaction flow as shown below are as follows Oracle Applications gt Oracle e Commerce Gateway gt Flat File gt EDI Translator gt EDI Message sent out Outbound Flow of a Transaction with Oracle e Commerce Gateway lt a Pn l Broo oe a pi gt se gt SS fe b amp Oracle Oracle e Commerce Flat File EDI Translator EDI Message Applications Gateway Sent Out gt The components of the inbound transaction flow as shown below are as follows EDI Message received gt EDI Translator gt Flat File gt Oracle e Commerce Gateway gt Oracle Open Interface gt Oracle Applications Introduction 1 11 Inbound Flow of a Transaction with Oracle e Commerce Gateway 7 LAL a S ye p A
153. 2100 Item Level 18 Line Level LINE 2200 2230 Flexfields Flexfields 19 Shipment LINE 2240 2270 Flexfields Flexfields 20 Item Level LINE 2280 2310 Flexfields Flexfields Inbound Response to Request for Quotation Common Key The following table shows the Common Key positions 1 100 for the Inbound Response to Request for Quotation transaction The table shows the position length code and A 112 Oracle e Commerce Gateway Implementation Manual content of the Common Key elements Transaction specific Data in the RRQI Common Key Position Length Code Content 1 25 25 TP_CD Trading Partner Code as defined in the Translator 26 47 22 DOC Transaction Identification from trading partner 48 69 22 ITEM Supplier Item Number 70 91 22 blank Not Used 92 95 4 varies Record Number 96 97 2 varies Record Layout 98 100 3 varies Record Layout Qualifier The following table shows the Common Key positions 1 100 for the records of the Inbound Response to Request for Quotation transaction Transaction specific Data in the Common Key of the RRQI Transaction Per Record Record TP_CD Ref1 Ref 2 Ref 3 Record Record Record DOC ITEM blank Number Layout Layout Qualifie r 1 Control TP_CD DOC 0010 CT CTL Record 2 Transact TP_CD DOC 1000 HA HD1 ion Identific ation Transaction Summary Layouts A 113 Record TP_CD Ref1 Ref2 Ref3 DOC ITEM blank Record Number Record Layout Record
154. 24 The following table illustrates the architecture of the records such as 0010 3000 that define a transaction and the two portions of data that define a single record The first Transaction Interface File Architecture 5 1 portion is the data in record positions 1 100 and the second portion is the application data in positions 101 1024 Record Architecture Content Record Number Record Position Record Positions 1 100 101 1024 Control record 0010 Common Key Base Application Data Trading Partner 0020 0050 Common Key Base Application Header Flexfields Data Trading Partner 0060 0070 Common Key Base Application Detail Flexfields Data Base Application 1000 etc Common Key Base Application Data Data Base Application 2000 etc Common Key Base Application Data Data Base Application 3000 etc Common Key Base Application Data Data Refer to Modify Transaction Interface File the Code Conversion chapter and the Oracle e Commerce Gateway User s Guide for detail on how to modify the records Control Record Record 0010 Each transaction must start with a control record that has key data to pass between Oracle e Commerce Gateway and a Translator The control record is identified by record number 0010 Key data includes the Translator code a key EDI Location Code for that transaction and a Document Code like POO for the outbound purchase order For inbound transactions batch control numbers from standard transactions may
155. 30 A2 IH4 ion Flexfiel d15 36 Interfac TP_CD MEMO 3040 A1 IH5 e Flexfiel ds 1 4 37 Interfac TP_CD MEMO 3050 A2 IH6 e Flexfiel ds 5 9 38 Interfac TP_CD MEMO 3060 A2 IH7 e Flexfiel ds 10 14 39 Interfac TP_CD MEMO 3070 A2 IH8 e Flexfiel d15 40 Memo TP_CD MEMO 3075 IV IV8 Header Shippin 8 Instructi ons A 178 Oracle e Commerce Gateway Implementation Manual Data Trading Partner Ref1 Ref2 MEMO ITEM Ref 3 Record TAX Number Record Layout Record Layout Qualifie r 41 42 43 44 45 46 Header Allowa nce Cha rges Header Allowa nce Cha rges Header Allowa nce Cha rges Flexfiel ds 1 4 Header Allowa nce Cha rges Flexfiel ds 5 9 Header Allowa nce Cha rges Flexfiel ds 10 14 Header Allowa nce Cha rges Flexfiel d15 TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD MEMO MEMO MEMO MEMO MEMO MEMO 3080 3090 3091 3092 3093 3094 AH AH AH AH AH AH AH1 AH2 TH1 TH2 TH3 TH4 Transaction Summary Layouts A 179 Data Trading Partner Ref 1 Ref 2 MEMO ITEM Record Record Number Layout Record Layout Qualifie r 47 48 49 50 51 52 53 Extensio n Tables Memo Header Data Basic Line Data Sales Order Data Part Custom er Item Descript ion Sales Channel Order Status Transact ion Referen ce Key Order Status
156. 6 122 Oracle e Commerce Gateway Implementation Manual The ECE_POO_HEADERS_V view is used to identify which purchase orders are eligible for extraction The extract criteria are as follows e Trading partner is defined e Transaction type enabled for the trading partner e Purchase order has not been printed or previously extracted e Purchase order status is Approved e Purchase order has not been canceled e Purchase order is not on hold If necessary you can use SQLPLUS to verify if there are any eligible documents to be extracted To do so you must first set the organization context and then issue the SQL count function as follows SQLPLUS gt execute fnd_client_info set_org context lt Org number gt SQLPLUS gt select count ECE POO HEADERS V Review all your set ups if the count value is 0 as this indicates there are no eligible documents to be extracted Columns Updated Upon Extraction Once an eligible purchase order is successfully extracted and written to the transaction interface file it is marked by Oracle e Commerce Gateway to prevent it from subsequent extraction The following table lists the fields updated based on an excerpt of code in the UPDATE_PO procedure defined in the ECEPOOB pls file Table Column Value PO_HEADERS EDI_PROCESSED_FLAG Y PO_HEADERS LAST_UPDATE_DATE SYSDATE PO_HEADERS PRINTED_DATE SYSDATE PO_HEADERS PRINT_COUNT Increment by 1 PO_HEADERS_ARCHIVE EDI_PROCESSED_FLAG Y P
157. 70 ME ME_INT INVOICE_C Yes INVOICE_C 1010 10 URRENCY_C URRENCY_C ODE ODE EXCHANGE Yes EXCHANGE 1010 30 _RATE _RATE EXCHANGE Yes EXCHANGE 1010 40 _DATE _DATE INVOICE_ID Derived SOURCE H EDI_LGATE WAY EXCHANGE Yes _RATE_TYPE EXCHANGE_RATE_TYPE is not mapped or referenced by the Oracle e Commerce Gateway because the data is not required by the transaction INVOICE_AMOUNT This column represents the total amount for the invoice calculated as the sum of the invoice line amounts INVOICE_CURRENCY_CODE EXCHANGE_DATE EXCHANGE_RATE Currency code exchange date and exchange rate are required for foreign currency invoices where the currency code is different from the functional currency The exchange date identifies the exchange rate to be used to compute the invoice amount INVOICE_NUM This column represents the invoice number for the supplier invoice being imported into Oracle Payables The number must be unique for the supplier as the Payables Open Interface Import program will reject duplicate invoice numbers PO_NUMBER Application Transaction Detail 6 77 This column represents the purchase order to match the invoice to Purchase order numbers may be entered at the header or line item level TERMS_NAME This column represents the payment terms and is required if you did not define payment terms for the supplier AP_INVOICE_LINES_INTERFACE Table The following table lists the required fields for the AP_INVOICE_L
158. 862 DELJIT outbound Shipping from Oracle Schedule Supplier Scheduling 810 INVOIC inbound Invoice includes into Oracle data for the ASC Payables X12 110 210 410 880 transactions 820 PAYORD outbound Payment Orders from Oracle Remittance Payables REMADV Advice 850 ORDERS inbound Purchase Orders into Oracle Order Management 875 ORDERS inbound Grocery into Oracle Purchase Orders Order Management 1 8 Oracle e Commerce Gateway Implementation Manual X12 Trans EDIFACT Direction Description Base Oracle Message Application 855 ORDRSP outbound Purchase Order from Oracle Acknowledgmen Order ts Management 860 ORDCHG inbound Purchase Order from Oracle Changes Order Management 865 ORDRSP outbound Purchase Order from Oracle Change Order Acknowledgmen Management ts 856 DESADV outbound Ship from Oracle Notice Manifest Shipping Execution 830 DELFOR inbound Planning into Oracle Schedule Release Management 862 DELJIT inbound Shipping into Oracle Schedule Release Management 866 no inbound Production into Oracle i Sequence Release equivalent Management 810 INVOIC outbound Invoice includes from Oracle data for the ASC Receivables X12 110 210 410 880 transactions 812 CREADV DEBA outbound Credit Memo from Oracle DV Debit Memo Receivables N A CUSDEC outbound Movement from Oracle Statistics Inventory INTRASTAT The transactions in the following table are available with Oracle Process Manufacturing Introduction 1 9
159. 9 Destinat TP_CD SHIPM LINE 3020 CO ST ion ENT Locatio n Inbound Shipping and Billing Notice SBNI 857 No EDIFACT A single transaction has the following data hierarchy and data looping SBNI Inbound Ship Notice Billing Structure Record Numbers Control Record 0010 Ship Notice Billing Header 1000 1900 Item Detail 2000 3900 Item Detail 2000 3900 litem Detail 2000 3900 An Inbound Shipping and Billing Notice transaction contains a single Control Record and Ship Notice Billing Header Record The header record may have multiple Item Detail records This structure is further described in the table below The following table shows the content and occurrences of the records comprising the Inbound Shipping and Billing Notice transaction Transaction Summary Layouts A 125 Record Occurrences Within the SBNI Transaction Records Content Occurrences 0010 Control Record Only one record occurrence per transaction 1000 1900 Shipment Notice Header Only one record occurrence Records per transaction 2000 3900 Shipment Notice Item One set of records per item Records within the Shipment Notice header The following table is a summary list of the records that comprise the Inbound Shipping and Billing Notice transaction The table shows the functional data grouping of records the data level the record numbers and relevant notes about the data grouping SBNI Transaction Record Summary Seq Type
160. 9 in CUSTOMER SITE in Key 2 are in the transaction The intent is to find the corresponding internal code given the 1 5 external CARRIER_EXT1 through CARRIER_EXT5 codes so they may be written to Oracle application open interface tables The code conversion value table is read with the following parameters and conditions e Access code conversion values table entries with the SHIP_VIA Category since SHIP_VIA was assigned to the CARRIER_INT column via the Assign Code Conversion window e The Oracle e Commerce Gateway moves the transaction values GAMMA into the CUSTOMER NAME column and the value 9999 into the CUSTOMER_SITE column which are the column names for the search keys In this sample only Key 1 Code Conversion 10 29 and Key 2 were enabled for the customer name and customer site respectively The Oracle e Commerce Gateway derived the customer name given the customer site 9999 in the transaction e The external code is part of the full search key for inbound transactions e Since this is an inbound transaction the process accesses table entries only with transaction direction IN and BOTH Code Conversion Setups The following code conversion table setups were done for this example The Code Conversion Categories window has two of the potential five search keys enabled for Category SHIP_VIA to accommodate the customer name and customer site search keys in the other code conversion windows The Assign Code Conversion wind
161. 90 Oracle e Commerce Gateway Implementation Manual Electronic Payments with Oracle e Commerce Gateway section for the details 1 Enter an EDI ID Number in the Banks window for your disbursement bank Refer to Oracle Payables User s Guide Defining Banks section for the details Define a payment document that uses the EDI Outbound Program as the payment format and assign this payment document to your disbursement bank account Refer to Oracle Payables User s Guide Defining and Maintaining Payables Payment Documents section for the details Enter bank data for each supplier site you want to pay Refer to Oracle Payables User s Guide Defining Supplier Bank Accounts section for the details Enter electronic payment data for each supplier site you want to pay Refer to Oracle Payables User s Guide Electronic Data Interchange Region of the Suppliers and Supplier Site Windows section for the details This is where you specify the following e EDI Location An identifier for the supplier that links to e Commerce Gateway trading partner EDIID Number ID number used by Oracle Energy e Payment Method Indicates how the electronic payment will be made Payment Method values and their descriptions are listed in the table below Payment Method Description ACH Automatic Clearing House BACS Bankers Automatic Clearing System BOP Financial Institution Option CWT Clearing House Inter bank Payment System CHIPS Funds Wire T
162. A IN2 INV E Flexfiel ds 5 9 40 Global TP_CD BATCH INVOIC 2070 GA IN3 INV E Flexfiel ds 10 14 A 100 Oracle e Commerce Gateway Implementation Manual Record TP_CD Ref 1 Ref 2 Ref 3 Record Record Record BATC INVOIC blank Number Layout Layout H E Qualifie r 41 Global TP_CD BATCH INVOIC 2080 GA IN4 INV E Flexfiel ds 15 19 42 Global TP_CD BATCH INVOIC 2090 GA IN5 INV E Flexfiel d20 Oracle Process Manufacturing Transaction Summaries Oracle Process Manufacturing Transactions Transaction Direction Transaction ASC X12 EDIFACT Name Code OPM Purchase Inbound GPOI 850 ORDERS Order OPM Purchase Outbound GPOAO 855 ORDRSP Order Acknowledgmen t OPM Ship Outbound GASNO 856 ORDADV Notice Manifest Current Information Refer to the Oracle Process Manufacturing User s Guide for transaction details Current detail record layouts are reported via the Transaction Definition Layout Report and the Interface File Data Report Transaction Summary Layouts A 101 Oracle Purchasing Transaction Summaries Oracle Purchasing Transactions Transaction Direction Transaction ASC X12 EDIFACT Name Code Price Sales Inbound CATI 832 PRICAT Catalog Response to Inbound RRQI 843 QUOTES Request for Quotation Ship Inbound ASNI 856 DESADV Notice Manifest Shipment and Inbound SBNI 857 N A Billing Notice Application Outbound ADVO 824 APERAK Advice Purchase Order Outbound POO 850 ORDERS Purchase Order Outbound POCO
163. ABC s original codes In this way the Trading Partner that created the original transaction receives response transactions containing their own internal codes Code conversion enables you to e Convert Trading Partner and electronic data standards external data to their equivalent internal Oracle application data and vice versa e Identify up to five levels of keys to uniquely associate codes to a specific Trading Partner or other entity For example a Trading Partner has multiple ship to locations which each have unique carrier codes Each set of carrier codes can be entered into the code conversion value table to be used only for the specific Trading Partner site Code Conversion 10 1 Definitions Code The value of a data element field or database table column For purposes of code conversion a code is typically a freight carrier a unit of measure For example the value of a carrier code may be FED Code Conversion Category A label for a set of codes For example SHIP_VIA UOM ORDER_TYPE PAY_TERMS are code conversion categories Data Element The smallest unit of a record Each record contains many data elements including but not limited to carrier code and unit of measure Data elements correspond to fields in Oracle Applications windows or database tables External Code A code in the transaction s transaction interface file regardless if it is an inbound or outbound transaction that represents data in the Tra
164. ADER _ID This column represents a sequence generated unique identifier It is system generated when the interface table is loaded LINE_ID This column represents a sequence generated unique identifier It is system generated when the interface table is loaded LINE_SOURCE Schedule source at line level since lines can also be manually entered PROCESS_STATUS Indicates the current processing status of a record Valid Values 1 Do not process 2 Waiting to be processed 3 In process 6 172 Oracle e Commerce Gateway Implementation Manual 4 Error 5 Processed 6 Processed with errors REQUEST_ID This column represents a sequence generated unique identifier assigned to the concurrent request for the demand processor Update Columns CREATED_BY This code identifies who loaded this transaction into the Demand Processor tables The code is set to the Requester ID associated with the concurrent manager request that processed this transaction CREATION_DATE This is the date that the e Commerce Gateway loaded the transaction into the Demand Processor table entries This date is set to the system date LAST_UPDATE_DATE This date is equal to the CREATION_DATE for this transaction This date is set to the system date LAST_UPDATED_BY This code is equal to the CREATED_BY code for this transaction Review Release Management Demand Processor Exceptions The Oracle Release Management Demand Processor Exception Handli
165. ALYSTS custom table ece flatfile PVT find pos 1 plsql_ table ITEM ID v_ItemIDPosition lue in the PL SQL table is stored as VARCHAR2 rt the value to a number O_NUMBER 1 plsql table v_ItemIDPosition necessary data from MATERIAL ANALYSTS and values in temporary variables Material Analyst Code Material Analyst _Last_Name Material Analyst First Name Material Analyst Phone Material Analyst Email v_mat_code v_mat_last_ name v_mat_first_name v_mat_phone v_mat_email material analysts Every va so conve k a v ItemID T J Get the store th as SELECT into FROM WHER xx Get the xx The posi x7 ece_extra F inventory item id v_ItemID position of extensible column from pl sql table tion is stored in temp position ct_utils_pub ext_get_value l_plsql_table Extensible Architecture 11 15 Material Analyst _Code temp position old value j 7 Store the external value in pl sql table in the position xx derived above zy ece_extract_utils_pub ext_insert_value l_plsql_table temp position v mat code a xx Repeat the last two steps for all the extensible columns END PROCEDURE Populate Ext Line Important This procedure is particularly used for POO and POCO transactions The differences between POO POCO and other types of transactions are highlighted as follows e Get the posit
166. CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD PO PO PO PO PO PO PO PO PO LINE LINE LINE LINE LINE LINE LINE LINE LINE 4550 4560 4600 4610 4620 4630 4700 4710 4720 A2 A2 Al A2 A2 A2 Al A2 A2 IN6 IN7 SV1 SV2 SV3 SV4 RT1 RT2 RT3 A 52 Oracle e Commerce Gateway Implementation Manual Sequen ce Data Trading Partner Ref 1 Ref 2 Ref 3 Record Number Record Layout Record Layout Qualifie r 98 99 100 101 102 103 104 105 Return Flexfiel d15 Ship to Address Item Level Ship to Contact Item Level Invoice to Contact s Trading Partner Flexfiel ds 1 4 Trading Partner Flexfiel ds 5 9 Trading Partner Flexfiel ds 10 14 Trading Partner Flexfiel d15 TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD PO PO PO PO PO PO PO PO LINE LINE LINE LINE LINE LINE LINE LINE 4730 4800 4810 4820 4830 4840 4850 4860 A2 AD CN CN A1 A2 A2 A2 RT4 ST1 ST1 IND TP1 TP2 TP3 TP4 Transaction Summary Layouts A 53 Sequen ce Data Trading Partner Ref 1 Ref 2 Ref 3 Record Number Record Record Layout Layout Qualifie r 106 107 108 109 110 111 112 113
167. COLUMNS contains the data that informs the extract process which data elements to write to the interface file as well as where in the output file to position them Only the data elements that appear in this table will be written to the interface file for a given outbound transaction Consequently records for the user defined data in the extension tables must be added to ECE_INTERFACE_COLUMNS Continuing the earlier example for each column that was added to ECE_PO_INTERFACE _LINES_X a record must be inserted into ECE_INTERFACE_ COLUMNS for the new data to appear in the output file Log into a SQL Plus session either as the owner of ECE_INTERFACE_COLUMNS typically EC or as a privileged user such as APPS and type the following Extensible Architecture 11 9 command to insert the first column of the new extension table data Do this for each column that was previously defined INSERT Statement follows INSERT INTO ece_ interface columns interface column_id interface table id interface column_name table name column_name record number position width data_type conversion sequence record layout code record layout_qualifier conversion group id xref category allowed element tag_name external level map_id staging column creation date created by last_update_ date last_updated_ by last_update_ login SELECT ece interface column_id_s NEXTVAL SELECT eit interface table id FROM ece interface tables
168. CUR y Cost R Price 12 Transact TP_CD HEADE DETAIL 2030 MV AMT ion Qty R UOM Weight 13 Commo TP_CD HEADE DETAIL 2040 MV COM dity R Code D escriptio n 14 Item TP_CD HEADE DETAIL 2050 MV CMT Descript R ion Comme nts Transaction Summary Layouts A 7 Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner Header Detail Locati Number Layout Layout on Qualifie r 15 Docume TP_CD HEADE DETAIL 2060 MV DOC nt R Source Referen ce 16 Shipme TP_CD HEADE DETAIL 2070 MV MSC nt Recei R pt Referen ce Contain er 17 Invoice TP_CD HEADE DETAIL 2080 MV INV Date Re R ference Qty 18 Bill to TP_CD HEADE DETAIL 2090 LC CUS Address R 19 Vendor TP_CD HEADE DETAIL 2100 LC VEN Name S R ite 20 Movem TP_CD HEADE DETAIL 2200 Al MV1 ent R Flexfiel ds 1 4 21 Movem TP_CD HEADE DETAIL 2210 A2 MV2 ent R Flexfiel ds 5 9 22 Movem TP_CD HEADE DETAIL 2220 A2 MV3 ent R Flexfiel ds 10 14 A 8 Oracle e Commerce Gateway Implementation Manual Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner Header Detail Locati Number Layout Layout on Qualifie r 23 Movem TP_CD HEADE DETAIL 2230 A2 MV4 ent R Flexfiel d15 24 Bill to TP_CD HEADE DETAIL LOCAT 3000 AD BT1 Address R ION 25 Shipto TP_CD HEADE DETAIL LOCAT 3010 AD ST1 Address R ION 26 Vendor TP_CD HEADE DETAIL LOCAT 3020 AD VN1 Address R ION Oracle Order Management Transaction Summaries Order Management Transaction Summaries Transaction Dire
169. CUSTOMER_NAME with value GAMMA and CUSTOMER SITE with value 9999 in the code converstion values table the highest order key is removed for the second search attempt In this case the customer site 9999 was removed from the search key parameters KEY2 with CUSTOMER_SITE was the highest number search key at this time 2 The second search with just CUSTOMER_NAME with value GAMMA and the internal code Over Night also did not find a table entry So the current highest order key is removed for the next search attempt In this case the customer GAMMA was removed from the search key parameter KEY1 with CUSTOMER_NAME was the highest number search key at this time 10 38 Oracle e Commerce Gateway Implementation Manual The third search is made with all blank search keys The internal code is code Over Night This search found a table entry It is shown in entry 7 Consequently the External 1 value AIR from the code conversion value table is copied to CARRIER_EXT1 column in the transaction table If no table entry is found then the CARRIER_INT value is copied to the CARRIER_EXT1 column in the transaction table Ultimately the data in CARRIER_INT and CARRIER_EXT1 appears in the transaction interface file if they are assigned a record number record position and length respectively These record assignments are displayed in the Transaction Interface Definition window window Code Conversion 10 39 11 Extensible Architecture This chapter
170. Category since SHIP_VIA was assigned to the CARRIER_INT column via the Assign Code Conversion window e The Oracle e Commerce Gateway moves the transaction values GAMMA into the CUSTOMER NAME column and the value 9999 into the CUSTOMER_SITE column which are the column names for the search keys In this sample only Key 1 and Key 2 were enabled for the customer name and customer site respectively The Oracle e Commerce Gateway derived the customer name given the customer site 9999 in the transaction 10 34 Oracle e Commerce Gateway Implementation Manual e The internal code is part of the full search key for outbound transactions e Over Night is moved into the CARRIER_INT internal field on the transaction interface file Any one of the CARRIER_EXT1 through CARRIER_EXT5 external codes is written to the transaction interface file if a record number record position and field length are assigned to the particular field e Since this is an outbound transaction the process accesses table entries only with transaction direction OUT and BOTH Code Conversion Set Ups The following code conversion table setups were done for this example The Code Conversion Categories window has two of the potential five search keys enabled for Category SHIP_VIA to accommodate the customer name and customer site search keys in the other code conversion windows The Assign Code Conversion window enables code conversion on a column and specifies which
171. Code with the other Location Codes in base Oracle Applications where address sites are defined The EDI Location Code exists to link the address site in the base Oracle Application to the Oracle e Commerce Gateway process The following table summarizes the purpose of the EDI Location Codes as defined in the base Oracle Application and when used in the transaction interface file Trading Partner 9 3 Purposes of EDI Location Codes in Base Oracle Application EDI Location Define in base Oracle Application Found in the transaction s Control Record 0010 Found in the transaction other than on Control Record 0010 Purpose for Outbound Transactions Extract EDI Location Code retrieved with the full address for each address within transaction so they are available for data mapping in an EDI translation process The EDI Location Code for the primary site in the transaction is placed on the Control Record Each transaction has a predefined site e g a bill to site for payment transactions that it will use to access the Oracle e Commerce Gateway tables to check that it is enabled The Primary site must have been defined as a Trading Partner in the Oracle e Commerce Gateway so its transactions could be enabled for processing for the specific transaction The EDI Location Code for the address site is retrieved along with the full address when the transaction was extracted then written to the transaction int
172. Commerce Gateway is in itself a comprehensive product that will suit most customer s e business integration requirements most of the effort expended during an implementation cycle concerns defining mapping and balancing customer requirements against trading partner expectations This guide includes implementation details and contains an overview of the main points that should be taken into consideration during the course of an Oracle e Commerce Gateway project This implementation manual provides the following e Required knowledge profile for an implementer e Implementation checklist e Profiles and validation rules setup details e Trading Partner setup details and recommendations Introduction 1 1 e Code conversion setup details and recommendations e Oracle Application setups for the transactions e Transaction interface file architecture e Transaction interface file modification guidelines e Testing recommendations e Details about the supported transactions e Trouble Shooting tools and recommendations e Recommendations on how to extend the supported transactions Note Details for adding transactions not supported by Oracle e Commerce Gateway are not included in this document Documentation The following documentation for Oracle e Commerce Gateway is available e Oracle e Commerce Gateway User s Guide e Oracle e Commerce Gateway Technical Reference Manual TRM Someone in your organization may need this manual if any cust
173. Contacts A 38 Oracle e Commerce Gateway Implementation Manual Sequence Data Data Level Record Number Note 53 Trader Partner LINE DETAIL 4830 4860 Flexfields Flexfields 54 Ship from LINE DETAIL 4870 Address Line Level 55 Credits Data CREDIT 5000 56 Credit Flexfields CREDIT 5100 5130 Flexfields 57 Price PRICE 6000 Adjustments ADJUSTMENT Data 58 Discount List PRICE 6010 Names for price ADJUSTMENT adjustments 59 Change Reason PRICE 6020 Text ADJUSTMENT 60 Price PRICE 6100 6130 Flexfields Adjustment ADJUSTMENT Flexfields 61 Reservations RESERVATION 7000 Data 62 Reservations RESERVATION 7100 7130 Flexfields Flexfields 63 Action Data ACTION 8000 64 Action Flexfields ACTION 8100 8130 Flexfields 65 Lot Serial Data LOT SERIAL 9000 66 Serial Lot LOT SERIAL 9100 9130 Flexfields Flexfields The following table shows the Common Key positions positions 1 100 for the Transaction Summary Layouts A 39 Outbound Purchase Order Change transaction The table shows the position length code and content of the Common Key elements Transaction specific data in the Common Key positions 1 100 Position Length Code Content 1 25 25 TP_CD Trading Partner Code as defined in the EDI Translator 26 47 22 PO Purchase order number 48 69 22 ITEM Purchase order line number 70 91 22 blank Not needed 92 95 4 varies Record Number 96 97 2 varies Record Layout 98 100 3 varies Record Layout Qualifier The f
174. D associated with the concurrent manager request that processed this transaction CREATION_DATE This is the date that the e Commerce Gateway loaded the transaction into the Order Import table entries This date is set to the system date LAST_UPDATE_DATE This date is equal to the CREATION_DATE for this transaction This date is set to the system date LAST_UPDATED_BY This code is equal to the CREATED_BY code for this transaction OE_LOTSERIALS_INTERFACE Table If you do not plan to use this feature you should deactivate the records that are associated to this table If you do not deactivate the records errors will occur in the Order Import validation because the records will be incomplete Application Transaction Detail 6 45 ORDER_SOURCE_ID This code identifies that the transaction was loaded into Order Import via the e Commerce Gateway DEFAULT The code is set to 6 meaning EDI Original System Reference Data Update Columns ORIG_SYS_DOCUMENT_REF ORIG_SYS_LINE_REF ORIG_SYS_SHIPMENT_REF See Definition above ORIG_SYS_LOTSERIAL_REF CREATED_BY This code identifies who loaded this transaction into the Order Import tables The code is set to the Requester ID associated with the concurrent manager request that processed this transaction CREATION_DATE This is the date that the e Commerce Gateway loaded the transaction into the Order Import table entries This date is set to the system date LAST_UPDATE
175. DI Location Code defined in Oracle Applications are displayed in the Define Trading Partners window Assignment tab If the data is not what you intend it to be you must make the appropriate changes for the transaction to be extracted for the correct trading partner This could involve either altering the supplier supplier site in the base Oracle Application or assigning a different supplier supplier site to that EDI Location Code in Oracle e Commerce Gateway Refer to the Trading Partner chapter for recommendations on selecting the correct trading partner EDI Location Code for the control record 0010 for the transaction in the transaction interface file Extract Criteria The outbound Application Advice transaction is controlled by two database views that are defined according to the Oracle e Commerce Gateway data model for application advice data The two views contain variables which are dynamically set based on your responses to the extract program parameters refer to Oracle e Commerce Gateway User s Guide Outbound Transactions chapter for a list of the program parameters The two database views are as follows e ECE_ADVO_DETAILS_V e ECE_ADVO_HEADERS_V The ECE_ADVO_HEADERS_V view is used to identify which application advice data is eligible for extraction The extract criteria are as follows e Trading partner is defined e Transaction type enabled for the trading partner e Application advice has not been previously extracted e Ap
176. Data length data_type VARCHAR2 50 Data type value VARCHAR2 400 Interface table valu layout_code VARCHAR2 2 Layout Code layout_qualifier VARCHAR2 3 Layout Qualifier interface column_id NUMBER Interface Column Id conversion sequence NUMBER Conversion Sequence xref category id NUMBER Cross reference category conversion group_id NUMBER Conversion Group Id xref keyl_ source column VARCHAR2 50 Cross reference source 1 xref key2 source column VARCHAR2 50 Cross reference source 2 xref key3 source column VARCHAR2 50 Cross reference source 3 xref key4 source column VARCHAR2 50 Cross reference source 4 xref key5 source column VARCHAR2 50 Cross reference source 5 ext_vall VARCHAR2 80 Cross reference value 1 ext_val2 VARCHAR2 80 Cross reference value 2 ext_val3 VARCHAR2 80 Cross reference value 3 ext_val4 VARCHAR2 80 Cross reference value 4 ext_val5 VARCHAR2 80 Cross reference value 5 Each record in the PL SQL table represents a single column in the interface table and there is one record in the PL SQL table for every column in the interface table In other words the PL SQL table can be viewed as an array of records with each record having the above structure The int_val attribute holds the value stored in the interface table column converted to VARCHAR2 Important It is important to note that the PL SQL table is built using the COLUMN_NAMEs from the associated out
177. ELJIT 0 00ccecccec ee eee eee eeeetene eter eteeeeeneenes 6 181 7 Test Transactions Testing Inbound Transactions sissies eee scene anadi raaraa eiia eeinetan atia 7 1 Testing Outbound Transactions 0 0cccccecceeeee cece eeee sees cee seneeceeeseaeseaesaeeseseeessnennenaes 7 4 Printing and Extract of Documents 0 00c ccc ec eee eeee eee reece ee tees neta aee eee seeeseeseesneeenaes 7 6 8 Troubleshooting Troubleshooting i si eaa a aaa aa EARE EAE E E E EE E Taia 8 1 Error Messages nurse einari anaa aaa aaia ka apaa Aaa eda aa EdE 8 2 Inbound Transactions erter aeaa a aaa E ao ERE Ea aaae e e a 8 13 Transaction Exception Summaries ss ssssssnseisiineissinstnssintissinrtnnrintinsrnrtrenntinsrnererentnn ete 8 14 Reports a ae ea a a Ea Ea AE A AE 8 17 9 Trading Partner 10 11 Trading Partneri sa aana e Enada Aara Aaa Aa Ea aaa Eataa aAA A ERARE ERA 9 1 Trading Partner Group ceiien eaa a a aaa aee Taaa a aa AE aara AEE 9 2 EDI Location Codes ziin ikina aeaaaee daaa ana ota aga Selo aANT 9 3 Translator Codeseira aaia aan aat a atarna aiaiai 9 5 Translator Code and EDI Location Code Across Applications sssss1nssssinernserneissnsene nen 9 7 Linking Trading Partner Data to the Oracle Application Source c cece eee eeeeeees 9 8 EDI Location Codes in the Transaction Interface Files 000ccccecseceeeeeeteee eee eeeeeeeneee 9 10 Multiple Organizations ce ssciess nanpa
178. EM_ID Yes LOCATOR Yes OE_ORDER__ Yes HEADER_ID OE_ORDER__ Yes LINE_ID PO_HEADER _ID PO_LINE_ID_ Yes SUBINVENT Yes ORY TO_ORGANI Yes ZATION_CO DE TO_ORGANI Yes ZATION_ID Application Transaction Detail 6 117 Oracle Cond Oracle Hardcoded Record Position Applications e Commerce Derived Number Number Column Gateway Name for Column Required Name Fields VENDOR_ID VENDOR_N UM VENDOR_N AME AUTO_TRANSACT_CODE This column identifies the type of incoming data The valid values are SHIP RECEIVE or DELIVER The default value is RECEIVE if no value is provided on the inbound flat file A value of SHIP tells the Receiving Open Interface to process the inbound ship notice as a ship notice only You will need to execute the PO receipt process in Purchasing when the physical goods arrive at your dock Use this setting if the physical goods are scheduled to arrive after the ship notice A value of RECEIVE tells the Receiving Open Interface to process the inbound ship notice as a ship notice and a PO receipt Use this setting if the physical goods are scheduled to arrive with the ship notice or this is a service PO that does not require a physical receipt A value of DELIVER tells the Receiving Open Interface to process the inbound ship notice as a ship notice a PO receipt and delivery Use this setting to receive and deliver the physical goods to the requester or to invent
179. ERY_ATTRIBS_V header level e WSH_DSNO_ITEM_DETAILS_V e WSH_DSNO_ITEMS_V e WSH_DSNO_ORDERS_V The ECE_DSNO_DELIVERIES_V view is used to identify which Shipment Notice Manifest is eligible for extraction The extract criteria are the following e Trading partner is defined e Transaction type enabled for the trading partner e The Stop is closed Columns Updated Upon Extraction The following is a list of fields updated by the WSH_ECE_VIEW_DEF_UPDATE_DEL_ASN_INFO procedure that is executed after the transaction data is extracted The table updated is the WSH_NEW_DELIVERIES 6 176 Oracle e Commerce Gateway Implementation Manual Column Value ASN_SEQ_ NUMBER ASN_DATE_SENT SYSDATE Oracle Supplier Scheduling The implementation of any transaction requires some set up in Oracle Applications and Oracle e Commerce Gateway This chapter focuses on the application set ups necessary to implement a transaction that integrates with Oracle Supplier Scheduling Transaction Direction Transaction ASC X12 EDIFACT Name Code Planning Outbound SPSO 830 DELFOR Schedule Shipping Outbound SSSO 862 DELJIT Schedule The topics covered for outbound transactions include the following e Trading Partner Link to Oracle e Commerce Gateway e Relevant Oracle Application Profiles and Set Ups e Planning Shipping Schedule Extract Options e Extract Criteria e Columns Updated upon Extraction Current Information The tra
180. E_I NT ITEM_DETAIL_QUA NTITY UOM_CODE_INT SCHEDULE_LINE_N UM 1000 2000 2000 2000 2000 2000 2000 2040 150 10 70 130 190 210 270 10 Derived EDI or manual transaction for this schedule i e 830 862 866 DELFOR MANUAL etc Past Due Firm Forecast Authorization Shipment Receipt Data or Other Bucket type type of Authorization or cumulative or last shipment receipt Ship Deliver Received From_To Customer specified date time Actual or cumulative Requested quantity Abbreviated unit of measure code Unique identifier of a line within a schedule Application Transaction Detail 6 161 Oracle e Commerce Record Number Position Number Note Gateway Column Name for Required Fields CUSTOMER_ITEM_E 3100 20 The customer item as XT defined in their application This code is consider an externally defined code hence the EXT suffix Control Record 0010 TEST_INDICATOR This column represents the test or production indicator from the Trading Partner If this value does not match the test or production indicator associated with the trading partner defined in Oracle e Commerce Gateway a process rule exception is detected and an exception message will display in the View Staged Documents window The valid values are T for test and P for production Note The TEST_INDICATOR is examined by the Demand Processor to determine how far the tran
181. Electronic post box number e Interchange sender receiver ID ISA06 08 or EDIFACT equivalent e Customer or supplier code as used in Oracle Applications e Customer name or Supplier name e Dun amp Bradstreet s DUNS or DUNS 4 number The Translator Code provides an additional identifier in the transaction interface file It is assigned at the transaction type level in the Trading Partner Detail window This allows Trading Partner sites to have different Translator Codes hence electronic mailboxes for different transactions For outbound transactions the Translator Code provides an identifier that the EDI translator software can use to identify the Trading Partner set up for the transaction EDI translator software might use the Translator Code alone or in conjunction with the EDI Location Code to identify its Trading Partner set up For inbound transactions the Translator Code is used in conjunction with the EDI Location Code to uniquely identify the Trading Partner set up in the Oracle e Commerce Gateway that the transaction refers to This also allows multiple Trading Partners to use the same EDI Location Codes since the actual Trading Partners can be distinguished by their Translator Code Since an Oracle e Commerce Gateway Trading Partner represents an address site multiple Trading Partners defined in the Oracle e Commerce Gateway may share the same Translator Code in the EDI translator Since the Trading Partner definition is ide
182. Fields TP_TRANSLATOR_C_ 0010 70 Translator identifier ODE for this trading partner TP_LOCATION_CO 0010 80 The EDI Location DE Code INVOICE_NUM 1000 10 INVOICE_AMOUNT 1000 40 ITEM_LINE_TYPE_C 3000 10 ODE AMOUNT 3000 110 Control Record 0010 TEST_INDICATOR This column represents the test or production indicator from the Trading Partner If this value does not match the test or production indicator associated with the trading partner defined in Oracle e Commerce Gateway a process rule exception is detected Then an exception message is displayed in the View Staged Documents window The valid values are T for test and P for production TP_DOCUMENT_ID This column identifies the type of document being sent by the Trading Partner If this document type is not enabled for the trading partner defined in Oracle e Commerce Gateway a process rule exception is detected Then an exception message is displayed in the View Staged Documents window The valid value is INI for standard invoice TP_TRANSLATOR_CODE TP_LOCATION_CODE EDI Location Code The two columns in combination uniquely identify a Trading Partner in Oracle e Commerce Gateway Once the trading partner definition is accessed Oracle e Commerce Gateway can verify whether the transaction is enabled for the Trading Partner If this trading partner is not defined in Oracle e Commerce Gateway a process rule exception is detected Then an exception message is displayed in t
183. Flexfiel ds 1 4 19 Global TP_CD PO 1290 A2 GL2 Flexfiel ds 5 9 20 Global TP_CD PO 1300 A2 GL3 Flexfiel ds 10 14 21 Global TP_CD PO 1310 A2 GL4 Flexfiel ds 15 19 22 Global TP_CD PO 1320 A2 GL5 Flexfiel ds 20 23 Custom TP_CD PO 1400 CU CUS er Name amp Number Transaction Summary Layouts A 65 Seq Data Trading Partner Ref 1 Ref 2 Ref 3 Record Number Record Record Layout Layout Qualifie r 24 25 26 27 28 29 30 31 Sold_to Address Informa tion Sold_to Contact Informa tion Ship_to Address Informa tion Ship_to Contact Informa tion Invoice Address Informa tion Invoice Contact Informa tion Ordered By Name Original System Referen ces TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD PO PO PO PO PO PO PO PO LINE 1410 1420 1500 1510 1520 1530 1540 2000 AD CN AD CN AD CN CN IT SLD SLD ST1 ST1 BT1 BT1 OBY IT1 A 66 Oracle e Commerce Gateway Implementation Manual Seq Data Trading Partner Ref 1 Ref 2 Ref 3 Record Number Record Layout Record Layout Qualifie r 32 33 34 35 36 37 38 Item Type Codes Item Segmen ts 1 10 Item Segmen ts 11 20 Deman d Class Bucket Type Custom er Paymen t Terms Tax Exempt Informa tion Project Task Contra
184. Flexfields ITEM 46 Trading Partner SCHEDULE 5300 5330 Flexfields Flexfields ITEM 47 Extension SCHEDULE 5900 Custom Tables Schedule ITEM Item Detail Data The following table shows the Common Key positions 1 100 for the Inbound Planning Material Release Schedule transaction The table shows the position length code and content of the Common Key elements Transaction specific Data in the SPSI Common Key Position Length CODE CONTENT 1 25 25 TP_CD Trading Partner Code as defined in the EDI Translator 26 47 22 SCH_REF Schedule Reference number Transaction Summary Layouts A 207 Position Length CODE CONTENT 48 69 70 91 92 95 96 97 98 100 22 22 ITEM SCHEDULE varies varies varies Schedule line number OR Sequence Counter of the Record 2000 Schedule detail number within schedule line OR Sequence Counter of Record 4000 within the given Record 2000 Record Number Record Layout Record Layout Qualifier The following table shows the Common Key positions 1 100 for the records of the Inbound Planning Material Release Schedule transaction Transaction specific Data in the Common Key of the SPSI Transaction Per Record Data Control Record Schedul e Header Schedul e Header Note Text Trading Partner TP_CD TP_CD TP_CD Ref 1 Ref 2 Ref SCH_R ITEM SCHE EF SCH_R EF SCH_R EF SCH_R EF A 208 Oracle
185. Flexfields ITEM 2150 2180 Flexfields 25 Ship To ITEM 2200 2230 Flexfields Organization Flexfields 26 Organization ITEM 2250 2280 Flexfields Option Flexfields 27 Schedule Item ITEM 2300 2330 Flexfields Flexfields 28 Extension ITEM 2900 Custom Tables Item Data 29 Forecast and ITEM DETAILS 4000 Authorization Data 30 Extension ITEM DETAILS 4900 Custom Tables Forecast and Authorization Data Outbound Shipping Schedule The following table shows the Common Key positions 1 100 for the Outbound Shipping Schedule transaction The table shows the position length code and content of the Common Key elements A 246 Oracle e Commerce Gateway Implementation Manual Transaction specific Data in the SSSO Transaction Common Key Position Length Code Content 1 25 25 TP_CD Trading Partner Code as defined in the EDI Translator 26 47 22 SS Shipping Schedule number 48 69 22 ITEM Shipping Schedule line number 70 91 22 SCHEDULE Schedule Bucket Number 92 95 4 varies Record Number 96 97 2 varies Record Layout 98 100 3 varies Record Layout Qualifier The following table shows the Common Key positions 1 100 for the records of the Outbound Shipping Schedule transaction Transaction specific Data in the Common Key of the SSSO Transaction Per Record Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner SS ITEM SCHE Number Layout Layout DULE Qualifie r 1 Control TP_CD SS 0010 CT CTL
186. Flexfields LINE 3200 3240 Flexfields 34 Pricing LINE 3300 3320 Flexfields Flexfields 35 Industry LINE 3400 3460 Flexfields Flexfields 36 Return Flexfields LINE 3470 3500 Flexfields Transaction Summary Layouts A 61 Seq Data Data Level Record Number Note 37 Ship_to Address LINE 4000 Item Level 38 Ship_to Contacts LINE 4010 Item Level 39 Ship_from LINE 4020 Address Item Level 40 Deliver_to LINE 4030 Contacts Item Level The following table shows the Common Key positions 1 100 for the Outbound Purchase Order Change and Purchase Order Change Acknowledgment transactions The table shows the position length code and content of the Common Key elements Transaction specific data in the Common Key of the POAO POCAO transactions Position Length Code Content 1 25 25 TP_CD Trading Partner Code as defined in the EDI translator 26 47 22 PO Purchase Order Number 48 69 22 ITEM Purchase Order Line Number 70 91 22 blank Not needed 92 95 4 varies Record Number 96 97 2 varies Record Layout 98 100 3 varies Record Layout Qualifier A 62 Oracle e Commerce Gateway Implementation Manual The following table shows the Common Key positions 1 100 for the records of the Outbound Purchase Order Change and Outbound Purchase Order Change Acknowledgment transactions Transaction specific data in the Common Key of the POCO POCAO transactions Seq Data Trading Ref 1 Partner Ref 3 Numb
187. H1 TH2 TH3 TH4 TD1 TD2 A 160 Oracle e Commerce Gateway Implementation Manual Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner PO ITEM SHIPM Number Layout Layout ENT Qualifie r 10 11 12 13 14 15 16 Purchas e Order Basic Header Paymen t Terms Purchas e Order Basic Header Purchas e Order Notes to Supplier Purchas e Order Flexfiel ds Purchas e Order Flexfiel ds Purchas e Order Flexfiel ds Purchas e Order Flexfiel ds Supplier Flexfiel ds TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD PO PO PO PO PO PO PO PO PO 1000 1010 1020 1030 1040 1050 1060 1070 1080 PO PO PO PO Al A2 A3 A4 Al POI PO2 PO3 PO4 POI PO2 PO3 PO4 SU1 Transaction Summary Layouts A 161 Data Trading Partner Ref1 Ref2 Ref 3 PO ITEM SHIPM ENT Record Number Record Record Layout Layout Qualifie r 17 18 19 20 21 22 23 24 25 Supplier Flexfiel ds Supplier Flexfiel ds Supplier Flexfiel ds Supplier Site Flexfiel ds Supplier Site Flexfiel ds Supplier Site Flexfiel ds Supplier Site Flexfiel ds Supplier Site Address Supplier Site Contact TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD PO PO PO PO P
188. HEAD_BEHIND Ahead Behind INVENTORY_BALANCE Inventory Balance HOLDOUT_QTY In Holdout DATE_TYPE_CODE_INT Date Type is used by the Demand Processor to determine how the start and end date on each schedule line should be interpreted For Demand Detail Types Past Due Firm and Forecast the Date Type is critical because it indicates whether the schedule demand is shipment based or delivery based For other Detail Types Authorizations Shipped Received Information and Other the Date Type is simply informational and is not used in processing Valid Values e SHIP e DELIVER e RECEIVED e FROM_TO START_DATE_TIME Customer specified date time as transmitted by the customer on the transaction Format YYYYMMDD HHMMSS OTY_TYPE_CODE_INT Quantity Type is used by the Demand Processor to determine how the quantity on schedule lines should be interpreted in context of its Detail Type and Detail Subtype Valid Values Application Transaction Detail 6 165 e ACTUAL e CUMMULATIVE ITEM_DETAIL_QUANTITY This column represents the requested quantity The ITEM_DETAIL_QUANTITY value corresponds to the ITEM_DETAIL_TYPE_INT as shown in the following table If then ITEM_DETAIL_TYPE_INT ITEM_DETAIL_QUANTITY Equals Contains 0 1 2 Demand Quantity 3 Authorization Quantity 4 Shipped received or cum quantity 5 Miscellaneous quantity such as ahead behind inventory balance UOM_CODE_INT This is the abbrevi
189. HEDULE 3100 Reference Data ITEM 23 More Customer SCHEDULE 3110 Reference Data ITEM Transaction Summary Layouts A 219 Data Data Level Record Number Note 24 More Customer SCHEDULE 3120 Reference Data ITEM including Dock FBO Configuration Key 25 Item Detail SCHEDULE 3140 Reference Codes ITEM and Values 26 Customer s item SCHEDULE 3180 description ITEM 27 Customer SCHEDULE 3200 transportation ITEM data 28 Item Note Text SCHEDULE 3220 ITEM 29 Handling and SCHEDULE 3240 Hazardous data ITEM 30 Ship Delivery SCHEDULE 3260 Pattern ITEM 31 Line Flexfields SCHEDULE 3300 3340 Flexfields ITEM 32 Industry SCHEDULE 3380 3440 Flexfields Flexfields ITEM 33 Trading Partner SCHEDULE 3460 3520 Flexfields Flexfields ITEM 34 Subline detail SCHEDULE 4000 ITEM 35 Other Name SCHEDULE 4010 Codes and ITEM Values A 220 Oracle e Commerce Gateway Implementation Manual Data Data Level Record Number Note 36 Item Note Text SCHEDULE 4030 ITEM 37 Item SCHEDULE 4050 Measurement ITEM External The following table shows the Common Key positions 1 100 for the Inbound Production Sequence Schedule transaction The table shows the position length code and contents of the Common Key elements Transaction specific Data in the Common Key of the PSQI Transaction Position Length CODE CONTENT 1 25 25 TP_CD Trading Partner Code as defined in the EDI Translator 26 47 22 SCH_REF Schedule Reference Number 48 69 22 SEQ Sequen
190. HIPM 1 Identification on SCH ENT NUMBER within last PO1 Second SCH Assigned CUSTOMER_SHIPM 2 Identification on SCH ENT NUMBER within last PO1 Comment Text Flags The e Commerce Gateway allows only a maximum length of 1024 characters per field To import text more than 1024 characters long write a custom procedure to concatenate several fields to import them to the longer field allowed in the open interface tables There are several flags in the interface tables of Order Management that affect the Order Import processing Valid values of these flags are Y N and null Null means different things depending on the particular flag The Order Import process sets the defaults if a code is not found in the transaction Most of the flag data elements are not activated on the transaction since the defaults are usually adequate Their data elements are listed at the end of the activated data elements in the Transaction Definition form 6 24 Oracle e Commerce Gateway Implementation Manual Order Management Flags Flag Description Default Possible Values Booked Cancelled Closed Error Ready This flag can be used instead of populating the oe_actions_interface table with the BOOK_ORDER action and it has the same effect The Cancelled flag is typically used to indicate that the line or order being imported should be imported in a Cancelled state The Closed flag is typically used to indicate that the lin
191. INE LINE LINE 3000 3010 3012 3014 3016 3018 3020 3030 LN LN LN LN LN LN PY PJ LN1 CHG CM1 CM2 CM3 CM4 TAX SRV Sequen ce Data Trading Ref 1 Partner Ref 2 Ref 3 Record Number Record Layout Record Layout Qualifie r 67 68 69 70 71 72 Service Transact ion Comme nts FOB Point Freight Terms Shipme nt Priority Method Freight Carrier Deman d Bucket Class Stream Shipme nt Data UOM Ship Pr omise Dates Shippin g amp Packing Instructi ons Item Flexfiel ds 1 4 TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD PO PO PO PO PO PO LINE LINE LINE LINE LINE LINE 3050 3080 3090 4000 4010 4200 SV FB DM DT NT A1 CM1 SHP DMD QTY NTE IT1 Transaction Summary Layouts A 49 Sequen ce Data Trading Partner Ref 1 Ref 2 Ref 3 Record Number Record Layout Record Layout Qualifie r 73 74 75 76 77 78 79 80 81 Item Flexfiel ds 5 9 Item Flexfiel ds 10 14 Item Flexfiel d15 Global Header Flexfiel ds 1 4 Global Header Flexfiel ds 5 9 Global Header Flexfiel ds 10 14 Global Header Flexfiel ds 15 19 Global Header Flexfiel d 20 Pricing Flexfiel ds 1 4 TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD T
192. INE LINE LINE TAX TAX TAX TAX TAX TAX TAX 5220 5900 6000 6005 6010 6020 6025 6030 6040 A2 TX TX TX TX TX A1 A2 IA3 Custo m TX1 TX2 TX3 TX4 TX5 TX1 TX2 Transaction Summary Layouts A 183 Data Trading Partner Ref 1 MEMO Ref 2 ITEM Ref 3 TAX Record Number Record Layout Record Layout Qualifie r 81 82 83 84 85 86 Line Tax Flexfiel ds 10 14 Line Tax Flexfiel d15 Line VAT Tax Flexfiel ds 1 4 Line VAT Tax Flexfiel ds 5 9 Line VAT Tax Flexfiel ds 10 14 Line VAT Tax Flexfiel d15 TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD MEMO MEMO MEMO MEMO MEMO MEMO LINE LINE LINE LINE LINE LINE TAX TAX TAX TAX TAX TAX 6050 6060 6070 6080 6090 6095 A2 A2 Al A2 A2 A2 TX3 TX4 VT1 VT2 VT3 VT4 Outbound Invoice INO 810 INVOIC A single transaction has the following data hierarchy and data looping A 184 Oracle e Commerce Gateway Implementation Manual INO Outbound Invoice Structure Control Record Invoice Header Header Allowance and Charges Invoice Item Line Tax Record Numbers 0010 1000 3075 3080 3900 4000 5900 6000 6095 An Outbound Invoice transaction contains a single Control Record and Invoice Header Record The
193. INE 3020 Misc Flexfields Description 11 Invoice Line INVOICE LINE 4000 4030 Flexfields Flexfields 12 Invoice Line INVOICE LINE 4100 4140 Flexfields Global Flexfields 13 Extension INVOICE LINE 4900 Custom Tables Invoice Item Data Inbound Invoice Common Key The following table shows the Common Key positions 1 100 for the Inbound Invoice transaction The table shows the position length code and content of the Common Key elements Transaction specific data in the INI transaction Common Key Position Length Code Content 1 25 25 TP_CD Trading Partner Code as defined in the EDI Translator 26 47 22 INVOICE Invoice number 48 69 22 ITEM Purchase Order Line Item Number A 74 Oracle e Commerce Gateway Implementation Manual Position Length Code Content 70 91 22 blank blank 92 95 4 Varies Record Number 96 97 2 Varies Record Layout 98 100 3 Varies Record Layout Qualifier The following table shows the Common Key positions 1 100 for the records of the Inbound Invoice transaction Transaction specific data in the Common Key positions per record of the INI transaction Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner Invoice Item blank Number Layout Layout Qualifie r 1 Control TP_CD INVOIC 0010 CT CTL Record E 2 Basic TP_CD INVOIC 1000 IV IV1 Invoice E Header 3 Basic TP_CD INVOIC 1010 IV IV2 Invoice E Header 4 Vendor TP_CD INVOIC 1020 AD BF Site E 5 In
194. INES_INTERFACE table Oracle Cond Oracle Hardcoded Record Position Applications e Commerce Derived Number Number Column Gateway Name for Column Required Name Fields LINE_TYPE_ LINE_TYPE_ 3000 10 LOOKUP_C LOOKUP_C ODE ODE AMOUNT AMOUNT 3000 110 PO NUMBE Yes PO_NUMBE 3010 10 R R INVOICE_ID Derived LINE_NUMB Derived ER AMOUNT This column represents the invoice distribution amount If the Invoice Match Option indicated on the transaction interface file is Purchase Order this column is the quantity invoiced multiplied by the unit price If the Invoice Match Option indicated on the transaction interface file is Receipt this amount is distributed across the non invoiced receipts beginning with the oldest If the invoice amount exceeds the total amount for the non invoiced receipts the overage is applied to the newest non invoiced receipt LINE_TYPE_LOOKUP_CODE This column identifies the invoice line type The valid values are ITEM TAX FREIGHT or MISCELLANEOUS 6 78 Oracle e Commerce Gateway Implementation Manual PO_NUMBER This column represents the purchase order to match the invoice to Purchase order numbers may be entered at the header or line item level Review Payables Open Interface Exceptions At the completion of the Payables Open Interface Import program the Payables Open Interface Report is automatically initiated to report the status of all supplier invoices processed The report contains
195. Inbound Transaction Summary Layouts A 217 Production Sequence Schedule transaction The table shows the functional data grouping of records the data level the record numbers and relevant notes about the data grouping PSQI Transaction Record Summary Data Data Level Record Number Note 1 Control Record SCHEDULE 0010 HEADER 2 Basic Schedule SCHEDULE 1000 Header HEADER 3 Schedule Header SCHEDULE 1010 Note Text HEADER 4 Customer SCHEDULE 1020 Address HEADER 5 Schedule Header SCHEDULE 1080 Misc Contacts HEADER 6 Schedule Header SCHEDULE 1090 Misc References HEADER 7 Schedule Header SCHEDULE 1500 1530 Flexfields HEADER 9 Trading Partner SCHEDULE 1600 1630 Header HEADER Flexfields 10 Ship To Address SCHEDULE 1700 and Code HEADER 11 Bill To Address SCHEDULE 1710 and Code HEADER 12 Intermediate SCHEDULE 1720 Ship To Address HEADER and Code A 218 Oracle e Commerce Gateway Implementation Manual Data Data Level Record Number Note 13 Ship From SCHEDULE 1730 Address and HEADER Code 14 Other Name SCHEDULE 1740 Codes and HEADER Values 15 Item Data Date SCHEDULE 2000 and Quantity ITEM Data 16 Unit of SCHEDULE 2040 Measurement ITEM 17 Item Reference SCHEDULE 2200 ITEM 18 Ship To Address SCHEDULE 3000 and Code ITEM 19 Bill To Address SCHEDULE 3010 and Code ITEM 20 Intermediate SCHEDULE 3020 Ship To Address ITEM and Code 21 Ship From SCHEDULE 3030 Address and ITEM Code 22 Customer SC
196. Inbound Price Sales Catalog transaction The table shows the position length code and content of the Common Key elements Transaction specific Data in the CATI Transaction Common Key Position Length Code Content 1 25 25 TP_CD Trading Partner Code as defined in the EDI Translator Transaction Summary Layouts A 105 Position Length Code Content 26 47 22 DOC Transaction Identification from trading partner 48 69 22 ITEM Supplier Item Number 70 91 22 blank Not Used 92 95 4 varies Record Number 96 97 2 varies Record Layout 98 100 3 varies Record Layout Qualifier The following table shows the Common Key positions 1 100 for the records of the Inbound Price Sales Catalog transaction Transaction specific Data in the Common Key of the CATI Transaction Per Record Record TP_CD Ref1 Ref 2 Ref 3 Record Record Record DOC ITEM blank Number Layout Layout Qualifie r 1 Control TP_CD DOC 0010 CT CTL Record 2 Transact TP_CD DOC 1000 HA HD1 ion Identific ation 3 Currenc TP_CD DOC 1010 HB HD2 y Paymen t Terms A 106 Oracle e Commerce Gateway Implementation Manual Record TP_CD Ref 1 Ref 2 Ref 3 Record Record Record DOC ITEM blank Number Layout Layout Qualifie r 4 FOB TP_CD DOC 1020 HC HD3 Carrier Freight Terms 5 Action TP_CD DOC 1030 HE HD5 Type 6 Comme TP_CD DOC 1040 NT HCM nts 7 Ship to TP_CD DOC 1100 AX ST Address 8 Bill to TP_CD DOC 1110 AX BT Address 9 Ship TP_CD D
197. Interface exceptions as follows e Using the information given by the View Staging Documents window in the e Commerce Gateway correct the set up data in Oracle Applications e Correct erroneous entries in the Order Management Order Import window e Request the customer to send a corrected transaction If you chose to update Oracle Applications data or change the erroneous entries using the Order Import window in Order Management you can resubmit the Order Management Open Interface Order Import process to revalidate the transaction If you chose to have the customer send a corrected transaction you must first delete the rejected Order data in the Order Management Open Interface tables using the Order Import window and then re import the updated transaction using the Oracle e Commerce Gateway Order Import Item Cross Referencing Item cross referencing and validation are not performed in the e Commerce Gateway The e Commerce Gateway writes data to the Order Import tables Order Import calls 6 48 Oracle e Commerce Gateway Implementation Manual the Process Order API that then calls Oracle Inventory s item cross reference APIs The API is given the customer item or generic item and a cross reference type to identify which type it is and optionally the vendor item to determine the following e Derive the internal supplier s inventory item given the customer item or generic inventory item e g customer item UPC ISBN or EAN number
198. L_TYPE_INT Detail Type is used by the Demand Processor to determine how the schedule line itself should be interpreted Valid Values 0 Past Due Firm 1 Firm Demand 2 Forecast Demand 3 Authorization 4 Shipment Receipt Data 5 Other ITEM_DETAIL_SUBTYPE_INT Detail Subtype is used by the Demand Processor to determine how the schedule line itself should be interpreted in context of its corresponding Detail Type Each Item Detail Type has a corresponding list of valid Item Detail Subtypes as shown in the following table If then ITEM_DETAIL_TYPE_INT ITEM_DETAIL_SUBTYPE_INT Equals Contains 0 1 2 1 Day 2 Week 3 Flexible 4 Month 5 Quarter Application Transaction Detail 6 155 If ITEM_DETAIL_TYPE_INT Equals then ITEM_DETAIL_SUBTYPE_INT Contains FINISHED Finished Goods MATERIAL Raw Material LABOR_MATERIAL Labor amp Material LABOR Labor PRIOR_CUM_REQ Prior Cumulative Required SHIPMENT Shipment RECEIPT Receipt CUM Customer CUM CUM_REJECTED CUM Rejected AHEAD_BEHIND Ahead Behind INVENTORY_BAL Inventory Balance HOLDOUT_QTY In Holdout ITEM_DETAIL_QUANTITY This column represents the requested quantity The ITEM_DETAIL_QUANTITY value corresponds to the ITEM_DETAIL_TYPE_INT as shown in the following table If ITEM_DETAIL_TYPE_INT then ITEM_DETAIL_QUANTITY 0 1 2 Demand Quantity Authorization Quantity Shipped receiv
199. Location DE Code Control Record 0010 DOCUMENT_ID This column identifies the type of document being sent by the Trading Partner If this document type is not enabled for the trading partner defined in Oracle e Commerce Gateway a process rule exception is detected Then an exception message is displayed in the View Staged Documents window The valid values are CATT for prices sales catalog or RRQI for response to Request for Quote RFQ TEST_INDICATOR This column represents the test or production indicator from the Trading Partner If this value does not match the test or production indicator associated with the trading partner defined in Oracle e Commerce Gateway a process rule exception is detected Then an exception message is displayed in the View Staged Documents window 6 98 Oracle e Commerce Gateway Implementation Manual The valid values are T for test and P for production TP_TRANSLATOR_CODE TP_LOCATION_CODE EDI Location Code The two columns in combination uniquely identify a Trading Partner in Oracle e Commerce Gateway Once the trading partner definition is accessed Oracle e Commerce Gateway can verify whether the transaction is enabled for the Trading Partner If this trading partner is not defined in Oracle e Commerce Gateway a process rule exception is detected Then an exception message is displayed in the View Staged Documents window Refer to the Trading Partner chapter for details on how to properly
200. M LINE 3020 CO ST ion ENT Locatio n Outbound Application Advice ADVO 824 APERAK A single transaction has the following data hierarchy and data looping A 132 Oracle e Commerce Gateway Implementation Manual ADVO Outbound Application Advice Structure Record Numbers Control Record 0010 Application Advice Header 1000 1900 Error 2000 2900 Error 2000 2900 Error 2000 2900 An Outbound Application Advice transaction contains a single Control Record and Application Advice Header Record The header record may have multiple Error Records This structure is further described in the table below The following table shows the content and occurrences of the records comprising the Outbound Application Advice transaction Record Occurrences Within the ADVO Transaction Records Content Occurrences 0010 Control Record Only one record occurrence per transaction 0020 0070 Gateway Flexfields One set of records per transaction 1000 1999 Application Advice Header Only one record occurrence Records per transaction 2000 2999 Application Advice Detail One set of detail records per Records error within the transaction The following table is a summary list of the records that comprise the Outbound Application Advice transaction The table shows the functional data grouping the data level the record number and relevant notes about the data grouping Transaction Summary Layouts A 133 ADVO Transaction Re
201. M_NAME is populated and CUSTOMER_ITEM_ID_TYPE is null If the Supplier Inventory Item is sent compare it to the derived Supplier Inventory Item Use the derived supplier inventory item and create an error message showing the sent inventory item if the vendor inventory items do not match Combination of Item Data in the Transaction Record 2000 The following table summarizes the results of item cross referencing given the combination of data on the record 2000 Customer Cross Reference table Inventory Item Cross Reference Generic table Inventory Item table internal supplier items In the follwong table the column INVENTORY_ITEM is in record 2000 position 30 The column Interpretation of CUSTOMER_ITEM_NAME is in record 2000 position 50 The column Sample CUSTOMER_ITEM_ID_TYPE as defined in Oracle Inventory is in record 2000 position 70 or 80 depending on code conversion INVENTORY_ITEM Interpretation of CUSTOMER_ITEM__ NAME Sample CUSTOMER_ITEM_ I D_TYPE Result of Item Cross Referencing in Oracle Inventory Null Null any Customer Specific item any Internal Item in the Customer Item Cross Reference table CUST INT Customer Item Cross Reference table is accessed to validate the customer item and derive its corresponding internal inventory item Customer Item Cross Reference table is accessed to validate the customer item and derive its corresponding internal invento
202. NTING_ORIGINAL_DATE SYSDATE PRINTING_PENDING N Outbound Credit Memo Debit Memo CDMO 812 CREADV DEBADV Trading Partner Link to Oracle e Commerce Gateway Customer and customer sites are defined in either Oracle Receivables or Oracle Order Management Included in the definition is the EDI Location Code that trading partners agree to exchange to represent the full detailed address Often they do not send the full address but just the EDI Location Code This is a critical data field to Oracle e Commerce Gateway The EDI Location Code is the link between a customer customer site in Oracle Applications and the trading partner site definition in Oracle e Commerce Gateway This enables Oracle e Commerce Gateway to access the detailed data about the customer or customer site in the base Oracle Applications without maintaining the detail data in Oracle e Commerce Gateway To ensure that the trading partner link between Oracle e Commerce Gateway and Oracle Applications is set up properly verify that the customer customer site and the EDI Location Code in Oracle Applications is the correct customer customer site selected for the Trading Partner definition in Oracle e Commerce Gateway The selected customer customer site and the EDI Location Code defined in Oracle Applications are displayed in the Define Trading Partners window Assignment tab If the data is not what you intend it to be you must make the appropriate changes for the transaction to b
203. Name Hardcoded Derived Record Number Position Number RLM_SCHED ULE_TYPE_I NT SCHEDULE_ PURPOSE_I NT SCHEDULE_ SOURCE CREATED_B Y CREATION_ DATE HEADER_ID LAST_UPDA TE_DATE LAST_UPDA TED_BY PROCESS_ST ATUS REQUEST_ID HEADER_ID Derived Derived Derived Derived Derived Derived Derived 1000 1000 1000 10 70 150 Most of the data was defined in the Oracle e Commerce Gateway Required Fields section above Data fields that were not defined in that section but are derived are defined below HEADER_ID This column represents a sequence generated unique identifier It is system generated when the interface table is loaded Application Transaction Detail 6 169 PROCESS_STATUS Indicates the current processing status of a record Valid Values 1 Do not process 2 Waiting to be processed 3 In process 4 Error 5 Processed 6 Processed with errors REQUEST_ID This column represents a sequence generated unique identifier assigned to the concurrent request for the demand processor Update Columns CREATED_BY This code identifies who loaded this transaction into the Demand Processor tables The code is set to the Requester ID associated with the concurrent manager request that processed this transaction CREATION_DATE This is the date that the e Commerce Gateway loaded the transaction into the Demand Processor table entries This date is s
204. O PO PO PO PO 1090 1100 1110 1120 1130 1140 1150 1160 1170 A2 A3 A4 Al A2 A3 A4 AD CN SU2 SU3 SU4 SS1 SS2 SS3 SS4 SU1 SS1 A 162 Oracle e Commerce Gateway Implementation Manual Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner PO ITEM SHIPM Number Layout Layout ENT Qualifie r 26 27 28 29 30 31 32 33 34 35 Supplier Site Contact Ship to Address Code Ship to Contact s Bill to Address Code Bill to Contact Buyer Name Buyer Commu nication s Procure ment Card Header Attach ment Master Header Attach ment Detail TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD PO PO PO PO PO PO PO PO PO PO 1180 1190 1200 1210 1220 1230 1240 1250 1800 1810 CN AX CN AX CN PO PO PR AT AT SS2 ST1 ST1 BT1 BT1 POS PO6 CRD HAH HAD Transaction Summary Layouts A 163 Data Trading Partner Ref 1 PO Ref2 Ref3 ITEM SHIPM ENT Record Number Record Layout Record Layout Qualifie r 36 37 38 39 40 41 42 43 44 Basic Item Data Basic Item Data Basic Item Data Hazard ous Material Codes Item Note to Supplier Line Flexfiel ds Line Flexfiel ds Line
205. OC 1120 AD SF From Address 10 Header TP_CD DOC 1200 Al HD1 Flexfiel ds 1 4 11 Header TP_CD DOC 1210 A2 HD2 Flexfiel ds 5 9 12 Header TP_CD DOC 1220 A2 HD3 Flexfiel ds 10 14 13 Header TP_CD DOC 1230 A2 HD4 Flexfiel ds 15 14 Item TP_CD DOC LINE 2000 IA IT1 Identific ation Transaction Summary Layouts A 107 Record TP_CD Ref 1 DOC Ref2 Ref 3 ITEM blank Record Number Record Layout Record Layout Qualifie r 15 16 17 18 19 21 22 Quantit y Descript ion Prices Dates Paymen t Terms Item Level FOB Carrier Freight Terms Item Level Hazard ous data Weight Volume Lead Time Ship To Data Item Level Line Level Flexfiel d1 4 TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD DOC DOC DOC DOC DOC DOC DOC LINE LINE LINE LINE LINE LINE LINE 2010 2020 2030 2040 2050 2100 2200 IB IC ID IE IF AX Al IT2 IT3 IT4 IT5 IT6 ST LN1 A 108 Oracle e Commerce Gateway Implementation Manual Record TP_CD Ref 1 DOC Ref 2 ITEM Ref 3 Record blank Number Record Layout Record Layout Qualifie r 23 24 25 26 27 28 29 30 Line Level Flexfiel d 5 9 Line Level Flexfiel d 10 14 Line Level Flexfiel d15 Shipme nt Flexfiel d1 4 Shipme nt Flexfiel d 5 9 Shipme nt Flexfiel d
206. OCATION_CODE EDI Location Code The two columns in combination uniquely identify a Trading Partner in Oracle e Commerce Gateway Once the trading partner definition is accessed Oracle e Commerce Gateway can verify whether the transaction is enabled for the Trading Partner If this trading partner is not defined in Oracle e Commerce Gateway a process rule exception is detected Then an exception message is displayed in the View Staged Documents window Refer to the Trading Partner section to properly define your trading partners and get a better understanding of how these fields are used in the process Review Oracle e Commerce Gateway Exceptions Use the Oracle e Commerce Gateway View Staged Documents window to review the Oracle e Commerce Gateway transaction exceptions as specified by the process and column rules in the e Commerce Gateway Once the exceptions are identified and resolved you can submit the transaction for reprocessing ignore the exception during reprocessing or delete the transaction Select the preferred option in the View Staged Documents window Resolve Oracle e Commerce Gateway Exceptions 6 8 To resolve Oracle e Commerce Gateway exceptions you can either correct the set up data in Oracle e Commerce Gateway or Oracle Applications or ask the Trading Partner to send a corrected transaction Note You cannot change the actual content of the inbound transaction via the View Staged Document window If the Tradi
207. ORACLE Oracle e Commerce Gateway Implementation Manual Release 12 Part No B31058 01 December 2006 Oracle e Commerce Gateway Implementation Manual Release 12 Part No B31058 01 Copyright 1996 2006 Oracle All rights reserved Primary Author Bonnie Shebat Williams Fred Graham Debbie Quezadaz Janet Lee Melody Yang Contributing Author Santiago Bastidas Neeraj Chauhan Neeraj Kumar Steve Moriarity Dan McCoy Geoffrey Scott Baker Steve Nelson Hari Praveen Sukhamoy Saha Arvind Srinivasan The Programs which include both the software and documentation contain proprietary information they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright patent and other intellectual and industrial property laws Reverse engineering disassembly or decompilation of the Programs except to the extent required to obtain interoperability with other independently created software or as specified by law is prohibited The information contained in this document is subject to change without notice If you find any problems in the documentation please report them to us in writing This document is not warranted to be error free Except as may be expressly permitted in your license agreement for these Programs no part of these Programs may be reproduced or transmitted in any form or by any means electronic or mechanical for any purpose If the Programs are delivered to
208. O_HEADERS_ARCHIVE LAST_UPDATE_DATE SYSDATE PO_HEADERS_ARCHIVE PRINTED_DATE SYSDATE Application Transaction Detail 6 123 Table Column Value PO_HEADERS_ARCHIVE PRINT_COUNT Increment by 1 PO_RELEASES EDI_PROCESSED_FLAG Y PO_RELEASES LAST_UPDATE_DATE SYSDATE PO_RELEASES PRINTED_DATE SYSDATE PO_RELEASES PRINT_COUNT Increment by 1 PO_RELEASES_ARCHIVE EDI_PROCESSED_FLAG Y PO_RELEASES_ARCHIVE LAST_UPDATE_DATE SYSDATE PO_RELEASES_ARCHIVE PRINTED_DATE SYSDATE PO_RELEASES_ARCHIVE PRINT_COUNT Increment by 1 The PO_LHEADERS and PO_HEADERS_ARCHIVE tables are used for standard planned or blanket purchase orders The PO_RELEASES and PO_RELEASES_ARCHIVE tables are used for blanket purchase order releases Outbound Purchase Order Change POCO 860 ORDCHG Trading Partner Link to Oracle e Commerce Gateway Suppliers and supplier sites are defined in either Oracle Purchasing or Oracle Payables Included in the definition is the EDI Location Code that trading partners agree to exchange to represent the full detailed address Often they do not send the full address but just the EDI Location Code This is a critical data field to Oracle e Commerce Gateway The EDI Location Code is the link between a supplier supplier site in Oracle Applications and the trading partner site definition in Oracle e Commerce Gateway This enables Oracle e Commerce Gateway to access the detailed data about the supplier or supplier site in the base Oracle Applications wi
209. Order Import ORDER_TYPE ORDER_TYPE _ This can be 1000 080 090 EXT1 defaulted Values must match those defined in Order Management Use code conversion for the standard code in the transaction if necessary ORDER_CATEG ORDER_CATEG If Null default 1000 100 110 ORY ORY _EXT1 to ORDER ORIG SYS_DOC ORIG SYS_DOC If Null derived 1000 120 UMENT_REF UMENT_REF Application Transaction Detail 6 27 Oracle Applications Column Name for Fields Oracle e Commerce Gateway Column Name Position Number Hardcoded Deri Record Number ved ORDER_DATE_ TYPE CUSTOMER_N AME CUSTOMER_N UMBER All Sold to Address Data ORDER_DATE_ TYPE _EXT1 CUSTOMER_N AME not required CUSTOMER_N UMBER not required SOLD TO Address If Null default to SHIP so the dates are interpreted as ship dates and not delivery dates 1000 130 140 Derived given 1400 010 the EDI Location code and Translator code on Control Record 0010 Data on Record 1400 will be not be imported unless the customer was not found Derived given 1400 020 the EDI Location code and Translator code on Control Record 0010 Data on Record 1400 will not be imported unless the customer was not found Derived given 1410 the EDI Location code and Translator code on Control Record 0010 6 28 Oracle e Commerce Gateway Implementation Manual Oracle Oracle Hardcoded Deri Rec
210. PM LINE 2120 A2 SL3 nt Line ENT Flexfiel ds 10 14 23 Shipme TP_CD SHIPM LINE 2130 A2 SL4 nt Line ENT Flexfiel d15 24 Order TP_CD SHIPM LINE 2140 Al RCI Line ENT Flexfiel ds 1 4 25 Order TP_CD SHIPM LINE 2150 A2 RC2 Line ENT Flexfiel ds 5 9 26 Order TP_CD SHIPM LINE 2160 A2 RC3 Line ENT Flexfiel ds 10 14 27 Order TP_CD SHIPM LINE 2170 A2 RC4 Line ENT Flexfiel d15 28 Destinat TP_CD SHIPM LINE 3000 AX ST ion ENT Address Code Transaction Summary Layouts A 85 Record TP_CD Ref1 Ref 2 Ref 3 Record Record Record Shipm Line blank Number Layout Layout ent Qualifie r 29 Destinat TP_CD SHIPM LINE 3020 CO ST ion ENT Locatio n Outbound Application Advice ADVO 824 APERAK A single transaction has the following data hierarchy and data looping ADVO Outbound Application Advice Structure Record Numbers Control Record 0010 Application Advice Header 1000 1900 Error 2000 2900 Error 2000 2900 Error 2000 2900 An Outbound Application Advice transaction contains a single Control Record and Application Advice Header The header record may have multiple Error records This structure is further described in the table below The following table shows the content and occurrences of the records comprising the Outbound Application Advice transaction A 86 Oracle e Commerce Gateway Implementation Manual Record occurrences within the ADVO transaction Records Content Occurrences
211. PO LINE 4000 AD ST1 Address Item Level 66 Ship to TP_CD PO LINE 4010 CN ST1 Contact Item Level 67 Ship fro TP_CD PO LINE 4020 AD ST1 m Address Item Level 68 Invoice TP_CD PO LINE 4030 CN ST1 Contact Item Level Oracle Payables Transaction Summaries Oracle Payables Transaction Summaries Transaction Direction Transaction ASC X12 EDIFACT Name Code Invoice Inbound INI 810 INVOIC Shipment and Inbound SBNI 857 N A Billing Notice Application Outbound ADVO 824 APERAK Advice Transaction Summary Layouts A 71 Transaction Direction Transaction ASC X12 EDIFACT Name Code Payment Outbound PYO 820 PAYORD Order Remittanc PAYEXT e Advice REMADV Current Information The transaction file may change when enhancements are made such as additional data added to the transaction Current transaction summaries can be found on Oracle Support s web site Current detail record layouts are reported via the Transaction Definition Layout Report and the Interface File Data Report Inbound Invoice INI 810 INVOIC A single transaction has the following data hierarchy and data looping INI Inbound Invoice Structure Record Numbers Control Record 0010 Invoice Header 1000 2900 Item Detail 3000 4900 Item Detail 3000 4900 Iter Detail 3000 4900 An inbound invoice transaction contains a single Control Record and Invoice Header Record The header record may have multiple Item Detail Records This s
212. P_CD TP_CD PO PO PO PO PO PO PO PO PO LINE LINE LINE LINE LINE LINE LINE LINE LINE 4210 4220 4230 4300 4310 4320 4330 4340 4400 A2 A2 A2 A1 A2 A2 A2 A2 A1 IT2 IT3 IT4 GL1 GL2 GL3 GL4 GL5 PC1 A 50 Oracle e Commerce Gateway Implementation Manual Sequen Data Trading Ref 1 Ref 2 Ref 3 Record Record Record ce Partner Number Layout Layout Qualifie r 82 Pricing TPCD PO LINE 4410 A2 PC2 Flexfiel ds 5 9 83 Pricing TP_CD PO LINE 4420 A2 PC3 Flexfiel d10 84 Industr TP_CD PO LINE 4500 Al IN1 y Header Flexfiel ds 1 4 85 Industr TP_CD PO LINE 4510 A2 IN2 y Header Flexfiel ds 5 9 86 Industr TP_CD PO LINE 4520 A2 IN3 y Header Flexfiel ds 10 14 87 Industr TP_CD PO LINE 4540 A2 IN4 y Header Flexfiel ds 15 19 88 Industr TP_CD PO LINE 4540 A2 IN5 y Header Flexfiel ds 20 24 Transaction Summary Layouts A 51 Sequen ce Data Trading Partner Ref 1 Ref 2 Ref 3 Record Number Record Layout Record Layout Qualifie r 89 90 91 92 93 94 95 96 97 Industr JX Header Flexfiel ds 25 29 Industr y Header Flexfiel d 30 Service Flexfiel ds 1 4 Service Flexfiel ds 5 9 Service Flexfiel ds 10 14 Service Flexfiel d15 Return Flexfiel ds 1 4 Return Flexfiel ds 5 9 Return Flexfiel ds 10 14 TP_CD TP_
213. Performed Performed Column Columns UOM_CODE UOM_CODE 2010 100 The Internal If placed in _INT code is the Dome value Ea derivedin UOM_CODE must be f data isin c d _INT field by moved here this field on conversion a translator by one of the the file code given the andahereis following conversion is c desin the io code methods not External 1 5 conversion 1 ee In fields performed this case the i this value is Determined value is The internal ied toth in the Oracle copied to the moved code is Abplicati e Commerce pplication directly into moved to the o Gateway pen the Open Interface through code Applicati pplication Interface Table conversion Open Table if 2 Directly Interface found during from the file tables code if it is present conversion if no code conversion value is found external 1 is copied to the Application open Interface Table Note that the derived Internal value is not written to the inbound file Code Conversion 10 27 Application Oracle Sample Sample Code No Code Open e Commerce Record Position Conversion Conversion Interface Gateway Number Number Performed Performed Column Columns UOM_CODE 2010 110 Place on the If data is _EXT1 file by a placed in the translator to External be used for codes by a code translator conversion and there is no code conversion performed this code is copied to the Application Open Interface Table
214. Purchase Order transaction Record Occurrences Within the POO Transaction Records Content Occurrences 0010 Control Record Only one record occurrence per transaction 0020 0070 Gateway Flexfields One set of records per transaction 1000 1900 PO Header Records Only one record occurrence per transaction 2000 2900 PO Line Records One set of records per line within the PO header 3000 3900 PO Shipment Records One set of records per schedule within the PO line 4000 4230 PO Distributions Records One set of records per distribution within the PO shipment The following table is a summary list of the records that comprise the Outbound Purchase Order transaction The table shows the functional data grouping of records the data level the record numbers and relevant notes about the data grouping POO Transaction Record Summary Seq Data Data Level Record Number Note 1 Control Record HEADER 0010 2 Trading Partner HEADER 0020 0050 Custom Header Flexfields A 140 Oracle e Commerce Gateway Implementation Manual Seq Data Data Level Record Number Note 3 Trading Partner HEADER 0060 0070 Custom Detail Flexfields 4 Purchase Order HEADER 1000 Basic Header 5 Payment Terms HEADER 1010 6 Purchase Order HEADER 1020 Basic Header 7 Purchase Order HEADER 1030 Notes to Supplier 8 Purchase Order HEADER 1040 1070 Flexfields Flexfields 9 Supplier HEADER 1080 1110 Flexfields Flexfields 10 Supplier Site HEADER
215. Qualifie NT r 19 Advice TP_CD DOC ERR_C 2050 AC ACI Detail NT Data Accept ed 20 Extensio TP_CD DOC ERR_C 2900 custom custom n Table NT Detail Level Outbound Payment Order Remittance Advice PYO 820 PAYORD REMADV A single transaction has the following data hierarchy and data looping PYO Outbound Payment Order Remittance Advice Structure Record Numbers Control Record 0010 PaymentiRem Advice Header Batch 1900 1900 invoice 2000 2900 Invoice 2000 2900 Invoice 2000 2900 An Outbound Payment Order Remittance Advice transaction contains a single Control Record and Payment Remittance Advice Header The header record may contain have Invoice Records This structure is further described in the table below The following table shows the content and occurrences of the records comprising the Outbound Payment Order Remittance Advice transaction A 92 Oracle e Commerce Gateway Implementation Manual Record occurrences within the PYO transaction Records Content Occurrences 0010 Control Record Only one record occurrence per transaction 0020 0070 Gateway Flexfields One set of records per transaction 1000 1250 Payment Header Records Only one record occurrence per transaction 2000 2090 Remittance Invoice Records One set of records per invoice within the Payment Header The following table is a summary list of the records that comprise the Outbound Payment Order Remittance Adv
216. RQI 843 QUOTES Trading Partner Link to Oracle e Commerce Gateway Suppliers and supplier sites are defined in either Oracle Purchasing or Oracle Payables Included in the definition is the EDI Location Code that trading partners agree to exchange to represent the full detailed address Often they do not send the full address but just the EDI Location Code This is a critical data field to Oracle e Commerce Gateway The EDI Location Code is the link between a supplier supplier site in Oracle Applications and the trading partner site definition in Oracle e Commerce Gateway This enables Oracle e Commerce Gateway to access the detailed data about the supplier or supplier site in the base Oracle Applications without maintaining the detail data in Oracle e Commerce Gateway To ensure that the trading partner link between Oracle e Commerce Gateway and Oracle Applications is set up properly verify that the supplier supplier site and the EDI Location Code in Oracle Applications is the correct supplier supplier site selected for the Trading Partner definition in Oracle e Commerce Gateway The selected supplier supplier site and the EDI Location Code defined in Oracle Applications are displayed in the Define Trading Partners window Assignment tab If the data is not what you intend it to be you must make the appropriate changes for the transaction to be imported for the correct trading partner This could involve either altering the supplier supplier si
217. Record SCHE Number Layout DULE Record Layout Qualifie r 35 36 37 38 39 40 41 Schedul e Line Flexfiel ds Cont ext Schedul e Line Flexfiel ds Industr y Flexfiel ds Cont ext Industr y Flexfiel ds Trading Partner Flexfiel ds Cont ext Trading Partner Flexfiel ds Extensio n Tables Schedul e Item Level TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD SCH_R EF SCH_R EF SCH_R EF SCH_R EF SCH_R EF SCH_R EF ITEM ITEM ITEM ITEM ITEM ITEM 2300 A1 2310 23 A2 30 2340 A1 2350 24 A2 00 2500 Al 2510 25 A2 30 2900 Custom SI1 SI2 SI4 IN1 IN2 IN7 TL1 TL2 TL4 Custom Transaction Summary Layouts A 213 Data Trading Ref 1 Ref 2 Ref Record Record Record Partner SCH_R ITEM SCHE Number Layout Layout EF DULE Qualifie r 42 Schedul TP_CD SCH_R ITEM SCHED 4000 SC SCH e Item EF ULE Detail Data Require ments Authori zations Shipped Receive d data etc 43 Item TP_CD SCHR ITEM SCHED 4010 RF SCH Detail EF ULE Miscella neous Referen ces 44 Item TP_CD SCHR ITEM SCHED 4020 NT SCH Detail EF ULE Note Text 45 Schedul TP_CD SCH_R ITEM SCHED 4100 Al SD1 e Line EF ULE Flexfiel ds Cont ext 46 Schedul TP_CD SCH_R ITEM SCHED 4110 41 A2 SD2 SD e Line EF ULE 30 4 Flexfiel ds 47 Industr TP_CD SCHR ITEM SCHED 4200 Al ID1 y EF ULE Flexfiel ds Cont ext A 214 Oracle e
218. Record 2 Trading TP_CD SS 0020 Al TH1 Partner Header Flexfiel ds Transaction Summary Layouts A 247 Data Trading Partner Ref1 Ref2 Ref 3 SS ITEM SCHE DULE Record Number Record Layout Record Layout Qualifie r 3 Trading Partner Header Flexfiel ds 4 Trading Partner Header Flexfiel ds 5 Trading Partner Header Flexfiel ds 6 Trading Partner Detail Flexfiel ds 7 Trading Partner Detail Flexfiel ds 8 Plannin 8 Schedul e Header 9 Plannin 8 Schedul e Header TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD SS SS SS SS SS SS SS 0030 0040 0050 0060 0070 1000 1010 A2 A2 A2 A1 A2 HD SP TH2 TH3 TH4 TD1 TD2 FRC SU A 248 Oracle e Commerce Gateway Implementation Manual Data Trading Partner Ref1 Ref2 Ref3 SS ITEM SCHE DULE Record Number Record Record Layout Layout Qualifie r 10 11 12 13 14 15 16 Plannin 8 Schedul e Header Plannin 8 Schedul e Header Plannin 8 Schedul e Header Plannin 8 Schedul e Header Schedul e Header Flexfiel ds 1 4 Schedul e Header Flexfiel ds 5 9 Schedul e Header Flexfiel ds 10 15 TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD SS 5S SS SS SS SS SS 1020 1030 1050 1060 1500 1510 1520 AD CN AX ST A1 A
219. Record Structure A single transaction has the following data hierarchy and data looping MVSTO Outbound Movement Statistics Structure Record Numbers Control Record 0010 Movement Statistics Header 1000 1900 Item Detail 2000 2900 Addresses 3000 3900 Item Detail 2000 2900 Asoresses 3000 3900 An outbound movement statistics transaction contains a single Control Record and Movement Statistics Header Record The header record may have multiple Item Detail Records which may have multiple Address Records This structure is further described in the table below The following table shows the content and occurrences of the records comprising the Outbound Movement Statistics transaction A 2 Oracle e Commerce Gateway Implementation Manual Record occurrences within the MVSTO transaction Records Content Occurrences 0010 0050 e Commerce Gateway Only one record occurrence Control Records per transaction 1000 1020 Movement Header Records Only one record occurrence per transaction 2000 2230 Movement Detail Records One set of records per item within the movement header 3000 3020 Movement Location Records One set of records per item within the movement detail The following table is a summary list of the records that comprise the Outbound Movement Statistics transaction The table shows the functional data grouping of records the data level the record numbers and relevant notes about the data grouping
220. Required 7000 050 ERVATION_RE ERVATION_RE F F OPERATION_C OPERATION_C _ If Null default 7000 060 070 ODE ODE _EXT1 to INSERT ORDER_SOURC ORDER _SOURC Hard code 6 E_ID E_ID meaning EDI The following table shows the line level records for OELACTIONS_INTERFACE Line Level Records for O0E_ACTIONS_INTERFACE Oracle Oracle Hardcoded Deri Record Number Position Applications e Commerce ved Number Column Name Gateway for Required Column Name Fields ORIG_SYS_DOC ORIG _SYS_DOC Required 8000 010 UMENT_REF UMENT_REF ORIG_SYS_LINE ORIG _SYS_ Required 8000 030 _REF LINE _REF Application Transaction Detail 6 37 Oracle Oracle Hardcoded Deri Record Number Position Applications e Commerce ved Number Column Name Gateway for Required Column Name Fields ORIG_SYS_SHIP ORIG_SYS_SHIP Required 8000 040 MENT_REF MENT_REF OPERATION_C OPERATION_C _ If Null default 8000 050 060 ODE ORDER_SOURC E_ID ODE _EXT1 ORDER_SOURC E_ID to INSERT Hard code 6 meaning EDI The following table shows the line level records for OE_LOTSERIALS_INTERFACE Line Level Records for OE_LOTSERIALS_INTERFACE Oracle Oracle Hardcoded Deri Record Number Position Applications e Commerce ved Number Column Name Gateway for Required Column Name Fields ORIG_SYS_DOC ORIG _SYS_DOC Required 9000 010 UMENT_REF UMENT_REF ORIG_SYS_LINE ORIG_SYS_ Required 9000 030 _REF LINE _REF ORIG_SYS_SHIP ORIG_SYS_SHIP Required 9000
221. SPSO 830 DELFOR Planning Scheduling Schedule Oracle Supplier SSSO 862 DELJIT Shipping Scheduling Schedule Oracle ADVO 824 APERAK Application Receivables and Advice Purchasing Descriptive Flexfields The Descriptive Flexfields feature of the Oracle Applications provides a flexible method for adding implementation specific data elements to any of the applications without programming These data elements are stored in the ATTRIBUTE columns in the base applications tables All of the ATTRIBUTE columns associated with the relevant application base tables for a specific transaction are included in the Oracle e Commerce Gateway interface tables for outbound transactions and in the Application open interface tables for inbound transactions Like all Application base tables the Oracle e Commerce Gateway table ECE_TP_HEADERS and ECE_TP_DETAILS contains ATTRIBUTE columns The ATTRIBUTE columns in ECE_TP_HEADERS and ECE_TP_DETAILS may be used to include additional Trading Partner specific data in the interface file given the trading partner definition used with the transaction Use of the Descriptive Flexfields feature in the Oracle Applications requires no additional setup for inclusion in Oracle e Commerce Gateway transactions Once the 11 2 Oracle e Commerce Gateway Implementation Manual desired flexfields are set up and defined in the Applications any data stored in them is automatically included in the relevant Oracle e Commerce Ga
222. SYS_DOCUMENT_REF ORIG_SYS_LINE_REF ORIG_SYS_SHIPMENT_REF See Definition above ORIG_SYS_CREDITS_REF CREATED_BY This code identifies who loaded this transaction into the Order Import tables The code is set to the Requester ID associated with the concurrent manager request that processed this transaction CREATION_DATE This is the date that the e Commerce Gateway loaded the transaction into the Order Import table entries This date is set to the system date LAST_UPDATE_DATE This date is equal to the CREATION_DATE for this transaction This date is set to the system date LAST_UPDATED_BY 6 44 Oracle e Commerce Gateway Implementation Manual This code is equal to the CREATED_BY code for this transaction OE_PRICE_ADJS_INTERFACE Table If you do not plan to use this feature you should deactivate the records that are associated to this table If you do not deactivate the records errors will occur in the Order Import validation because the records will be incomplete ORDER_SOURCE_ID This code identifies that the transaction was loaded into Order Import via the e Commerce Gateway DEFAULT The code is set to 6 meaning EDI Original System Reference Data Update Columns ORIG_SYS_DOCUMENT_REF ORIG_SYS_LINE_REF ORIG_SYS_SHIPMENT_REF See Definition above ORIG_SYS_DISCOUNT_REF CREATED_BY This code identifies who loaded this transaction into the Order Import tables The code is set to the Requester I
223. T1 through _EXT5 for the same column name Either the e Commerce Gateway s Code Conversion process can derive the internal codes to place them in the open interface tables or the values may be placed in the internal code fields on the file if they are derived from another process Only the internal codes are referred to below for simplicity RLM_SCHEDULE_TYPE_INT This column represents the Schedule type Valid Values PLANNING SHIPPING SEQUENCED SCHEDULE_PURPOSE_INT This column represents the Schedule Purpose code Valid Values ADD ORIGINAL REPLACE CANCEL CHANGE DELETE and CONFIRMATION SCHEDULE_SOURCE This column represents the EDI or manual transaction source for this schedule such as 830 862 866 DELFOR MANUAL Refer to the Release Management Implementation Manual and the Release Management User s Guide for detailed descriptions of all codes and the impact on processing for each code value Record 4000 DATE_TYPE_CODE_INT Date Type is used by the Demand Processor to determine how the start date and end date on each schedule line should be interpreted For Demand Detail Types Past Due Firm and Forecast the Date Type is critical because it indicates whether the schedule demand is shipment based or delivery based For other Detail Types Authorizations Shipped Received data and Other the Date Type is simply informational and is not used in processing Valid Values e SHIP e DELIVER e RECEIVED
224. TORY_ITEM_SEGME NT_1 10 Item 3 INVENTORY_ITEM_SEGME NT_11 20 1st Prices configuration options references 1st Schedule1 dates etc 2nd Prices configuration options references 2nd Schedule1 dates etc Order Import Level Copy all item data to each of its shipments LINE Item 2 Schedule1 data LINE Item2 Schedule1 data LINE Item 2 Schedule2 data LINE Item2 Schedule2 data Copy all item data to each of its shipments Copy all item data to each of its shipments Copy all item data to each of its shipments LINE Item 3 Schedule1 data LINE Item3 Schedule1 data LINE Item 3 Schedule2 data LINE Item3 Schedule2 data The following table illustrates key data on records 2000 4900 that contain the line and Application Transaction Detail 6 13 shipment detail required by Order Import Refer to the transaction record layout for the position of the data on the record Line and Shipment Records Case Record Customer Customer Item ID Type Inventory Line Item Item 3000 Operation Price Quantity UOM 4000 Shipment Customer Number Request Date 1 2000 1 ABC CUST XYZ 2 3000 INSERT 10 00 3 4000 1 20000101 230000 4 3000 INSERT 10 00 5 4000 2 20000202 000000 6 3000 INSERT 10 00 7 4000 3 20000202 000000 8 2000 2 WWW 9 3000 INSERT 20 00 10 4000 1 20000101 230000 11 3000 INSERT 20 00 12 4000 2 20000102 220000 Case 1 ITEM DETAIL Record 2000 contains the c
225. TP_CD PO LINE 3230 A2 GL4 Flexfiel ds 15 19 50 Global TP_CD PO LINE 3240 A2 GL5 Flexfiel ds 20 51 Pricing TP_CD PO LINE 3300 Al PC1 Flexfiel ds 1 4 52 Pricing TP_CD PO LINE 3310 A2 PC2 Flexfiel ds 5 9 53 Pricing TP_CD PO LINE 3320 A2 PC3 Flexfiel d10 54 Industr TP_CD PO LINE 3400 Al IN1 y Flexfiel ds 1 4 55 Industr TP_CD PO LINE 3410 A2 IN2 y Flexfiel ds 5 9 Transaction Summary Layouts A 69 Seq Data Trading Partner Ref 1 Ref 2 Ref 3 Record Number Record Layout Record Layout Qualifie r 56 57 58 59 60 61 62 63 64 Industr y Flexfiel ds 10 14 Industr y Flexfiel ds 15 19 Industr y Flexfiel ds 20 24 Industr y Flexfiel ds 25 29 Industr y Flexfiel ds 30 Return Flexfiel ds 1 4 Return Flexfiel ds 5 9 Return Flexfiel ds 10 14 Return Flexfiel ds 15 TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD PO PO PO PO PO PO PO PO PO LINE LINE LINE LINE LINE LINE LINE LINE LINE 3420 3430 3440 3450 3460 3470 3480 3490 3500 A2 A2 A2 A2 A2 A1 A2 A2 A2 IN3 IN4 IN5 IN6 IN7 RT1 RT2 RT3 RT4 A 70 Oracle e Commerce Gateway Implementation Manual Seq Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner Number Layout Layout Qualifie r 65 Ship to TP_CD
226. TP_CD SCH_R SEQ 3460 Al TL1 Partner EF Flexfiel ds 46 Trading TP_CD SCH_R SEQ 3480 A2 TL2 Partner EF Flexfiel ds 47 Trading TP_CD SCH_R SEQ 3500 A2 TL3 Partner EF Flexfiel ds 48 Trading TP_CD SCH_R SEQ 3520 A2 TL4 Partner EF Flexfiel ds 49 Subline TP_CD SCH_R SEQ SEQ SU 4000 SL SLN detail EF BLINE 50 Other TP_CD SCH_R SEQ SEQ SU 4010 MN MNI Name EF BLINE Codes and Values 51 Item TP_CD SCH_R SEQ SEQ SU 4030 NT PIC Note EF BLINE Text 52 Item TP_CD SCH_R SEQ SEQ SU 4050 ME MEA Measur EF BLINE ement External Shipping Schedule SSSI 862 DELJIT A 228 Oracle e Commerce Gateway Implementation Manual See the Inbound Planning Material Release Schedule SPSI 830 DELFOR page A 202 above These transactions have the same record layout Oracle Shipping Execution Transaction Summaries Oracle Shipping Execution Transactions Transaction Direction Transaction ASC X12 EDIFACT Name Code Ship Outbound DSNO 856 DESADV Notice Manifest Current Information The transaction file may change when enhancements are made such as additional data added to the transaction Current transaction summaries can be found on Oracle Support s web site when they are released Current detail record layouts are reported via the Transaction Definition Layout Report and the Interface File Data Report Outbound Ship Notice Manifest DSNO 856 DESADV The receiver of a Ship Notice Manifest transaction may use the data for more than one purp
227. T_DAT 4000 180 E_TIME_DET QTY_TYPE_ 4000 210 CODE_INT ITEM_DETAI 4000 270 L_QUANTIT Y UOM_CODE 4000 280 _INT_D CREATED_B Derived Y CREATION_ Derived DATE Application Transaction Detail 6 153 Oracle Cond Oracle Hard coded Record Position Applications e Commerce Derived Number Number Column Gateway Name for Column Required Name Fields HEADER_ID Derived LAST_UPDA Derived TE_BY LAST_UPDA Derived TE_DATE LINE_ID Derived LINE_SOUR Derived CE PROCESS_ST Derived ATUS REQUEST_ID Derived SCHEDULE_ Derived ITEM_NUM SCHEDULE_ Derived LINE_NUM LINE_ID This column represents a sequence generated unique identifier It is system generated when the interface table is loaded HEADER_ID This column represents a sequence generated unique identifier It is system generated when the interface table is loaded DATE_TYPE_CODE_INT Date Type is used by the Demand Processor to determine how the start date and end date on each schedule line should be interpreted For Demand Detail Types Past Due Firm and Forecast the Date Type is critical because it indicates whether the schedule demand is shipment based or delivery based 6 154 Oracle e Commerce Gateway Implementation Manual For other Detail Types Authorizations Shipped Received Information and Other the Date Type is simply informational and is not used in processing Valid Values e SHIP e DELIVER e RECEIVED e FROM_TO ITEM_DETAI
228. The supplier illustration above highlights the following key items when assigning a Trading Partner to a suppler supplier site in Oracle Payables e The Trading Partner area within the Trading Partner Group window establishes the following A name and description for the Trading Partner definition Both fields are free form text though a naming convention is recommended on the Trading Partner name and Trading Partner Group Note Trading Partner Group is not linked to other Oracle Applications e This Trading Partner name will be associated to a single suppler supplier site in the Trading Partner Assignment tab e The Trading Partner Assignment tab establishes the following e Links the Trading Partner definition to the appropriate suppler supplier site in Oracle Payables e The EDI Location Code from Oracle Payables is displayed for the selected Trading Partner 9 9 address site e The Trading Partner Details tab establishes the following within the Oracle e Commerce Gateway e Enables a document transaction document type for processing e Defines the Translator Code for that transaction e Flags the transaction as test or production e Display the format of the transaction Flat File FF in this case EDI Location Codes in the Transaction Interface Files Inbound Transactions Control Record 0010 The Control Record is the first record in each transaction It contains a field called the Trading Partner Location Co
229. This field contains the customer item or a generic item as defined in the customer s inventory application e Item Type CUSTOMER_ITEM_ID_TYPE This field contains a valid qualifier that identifies the type of item placed in CUSTOMER_ITEM_NAME CUSTOMER_ITEM_ID_TYPE The following table has samples of the CUSTOMER_ITEM_ID_TYPE and its interpretation The column Sample CUSTOMER_ITEM_ID_TYPE is as it is defined in Oracle Inventory in record 2000 position 70 or 80 depending on code conversion The column Intepretation of CUSTOMER_ITEM_NAME comes from record 2000 position 50 Application Transaction Detail 6 51 CUSTOMER ITEMI D_TYPE Seeded Code Seeded Code User Defined Code User Defined Code Sample CUSTOMER_ITEML_I D_TYPE CUST INT UPC EAN Interpretation of CUSTOMER_ITEM_ NAME Customer Specific item Internal Item in the Customer Item Cross Reference table UPC code EAN number Table to which the search will be directed Customer Item Cross Reference Table Customer Item Cross Reference Table Inventory Item Cross Reference table Inventory Item Cross Reference table If the wrong code is passed to the Order Import tables you may not get a match on the item If a code is entered that does not exist there will be an error on the item When in doubt leave it null Processing of a null CUSTOMER_ITEM_ID_TYPE a later feature CUSTOMER_ITEM_ID_TYPE Code Conversion Code con
230. Transaction Interface File Architecture This chapter contains information about transaction interface file architecture This chapter covers the following topics e File Structure Overview e Interface Data File Structure e Special Records e Optional Outbound Trading Partner Flexfield Records 0020 0070 e Common Record Key 1 100 e Common Records Based on Record Layout Code e Code Conversion Internal and External Codes on the File File Structure Overview Oracle e Commerce Gateway produces ASCII files for outbound transactions For inbound transactions Oracle e Commerce Gateway processes ASCII file produced by a Translator Each file consists of several records that are uniquely identified by its record number A set of record numbers are assigned to a level of data in the transaction for example the records in range 1000 1999 may contain data at the header level of the document Records in range 2000 2999 may contain data at the item level of the document Each transaction consists of multiple levels of data They are indicated by their level names show in the Interface File Definition window Usually the data from a level is written to many records in the transaction interface file Each record may consist of a single set of data elements such as all the currency data on the same record or it may consist of several groups of related data The amount of data on any record is constrained only by a maximum record length of 10
231. UOM_CODE not activated notactivated Used as part _EXT2 of a code conversion if properly enabled UOM_CODE not activated not activated _EXT3 UOM_CODE not activated not activated _EXT4 UOM_CODE not activated not activated _EXT5 Activated External Data Fields on the Transaction Interface File Though there may be data in all five external codes in the code conversion tables the only external codes to actually be copied to the transaction interface file are the ones that are activated for the file They are activated if the data element shows a record number position and width on the data element in the Interface File Definition window or the Transaction Layout Definition report If data elements are not activated but you wish to use them in the transaction interface file activate them by entering a record number position and width using the Interface File Definition window For outbound transactions both the internal code and external codes are written to the 10 23 Oracle e Commerce Gateway Implementation Manual transaction interface file They are available on the file for mapping to the EDI standard transaction by an EDI translator For inbound transactions the external codes are expected in the file for code conversion or to be passed directly to the application open interface table if an internal code is not derived by code conversion If another process determines the internal code and writes it to the transaction interface file
232. When to Use Keys 1 5 Besides the internal and external codes you can limit the applicability of a table entry to a specific Trading Partner or any other entity that you chose by entering values in the search keys The search key will be data of your choice that identifies that Trading Partner or other entity If internal and external code entries apply to specific Trading Partners or a group of Trading Partners one to five limiting search keys plus the internal and external codes must be entered into the code conversion table To use Keys 1 5 set ups are required in the Code Conversion Categories window and the Assign Categories window previously discussed Users must indicate what the full search key will be during code conversion set up For example it may be the sales channel customer code and customer site Users select what columns to examine from columns in the specific transaction tables in the Oracle e Commerce Gateway These columns contain the actual code values examined during code conversion Relationship of the Code Conversion Windows The following illustrations show the relationship of the five keys across the three code conversion windows 1 Code Conversion Categories window In the example only two keys are turned on so a maximum of two search keys will be read during code conversion 2 Assign Categories window In the Assign Categories window the columns that contain the data in the transaction to be used as the s
233. Y_ITEM any Inventory Item Interpretation of CUSTOMER_ITEM_ NAME any Internal Item in the Customer Item Cross Reference table Sample CUSTOMER_ITEM_ I D_TYPE INT Result of Item Cross Referencing in Oracle Inventory Customer Item Cross Reference table is accessed to validate the customer item and derive its corresponding internal inventory item The derived Inventory Item is compared to the Inventory Item in the transaction If the derived and the sent Inventory Item do not match an error message is generated where the sent inventory item is displayed in the error 6 58 Oracle e Commerce Gateway Implementation Manual INVENTORY_ITEM any Inventory Item Interpretation of CUSTOMER_ITEM__ NAME any UPC code Sample CUSTOMER_ITEM_ D_TYPE UPC Result of Item Cross Referencing in Oracle Inventory Inventory Item Cross Reference table is accessed to validate the generic item and derive its corresponding internal inventory item The derived Inventory Item is compared to the Inventory Item in the transaction If the derived and the sent Inventory Item do not match an error message is generated where the sent inventory item is displayed in the error Application Transaction Detail 6 59 Error Situations INVENTORY_ITEM any Inventory Item Interpretation of CUSTOMER_ITEM_ NAME any EAN number Sample CUSTOMER_ITEM_ I D_TYPE EAN Result of Item
234. Yes SHIPPED_D 1000 70 ATE ATE AUTO_TRA Yes AUTO_TRA 1000 100 120 NSACT_CO NSACT_CO DE DE SHIPMENT_ Yes PICK_SLIP_ 1000 10 NUM NUMBER AUTO_TRANSACT_CODE This column identifies the type of incoming data The valid values are SHIP RECEIVE or DELIVER The default value is RECEIVE if no value is provided in the transaction A value of SHIP tells the Receiving Open Interface to process the inbound ship notice as a ship notice only You will need to execute the PO receipt process in Purchasing when the physical goods arrive at your dock Use this setting if the physical goods are scheduled to arrive after the ship notice A value of RECEIVE tells the Receiving Open Interface to process the inbound ship notice as a ship notice and a PO receipt Use this setting if the physical goods are scheduled to arrive with the ship notice or this is a service PO that does not require a physical receipt A value of DELIVER tells the Receiving Open Interface to process the inbound ship notice as a ship notice a PO receipt and delivery Use this setting to receive and deliver the physical goods to the requester or to inventory This option assumes you do not want to inspect the goods INVOICE_NUM INVOICE_DATE INVOICE_AMOUNT Invoice number date and amount are required for the Inbound Shipment and Billing Notice transaction to create an invoice The invoice number must be unique for the supplier PICK_SLIP_NUMBER This column represents the
235. _CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD PO PO PO PO PO PO PO PO PO 1410 1420 1500 1510 1520 1530 1540 1600 1700 AD CN AD CN AD CN CN AD CR SLD SLD ST1 ST1 BT1 BT1 OBY SFM CRD A 44 Oracle e Commerce Gateway Implementation Manual Sequen Data Trading Ref 1 Ref 2 Ref 3 Record Record Record ce Partner Number Layout Layout Qualifie r 36 Credit TP_CD PO 1710 Al CR1 Flexfiel ds 1 4 37 Credit TP_CD PO 1720 A2 CR2 Flexfiel ds 5 9 38 Credit TP_CD PO 1730 A2 CR3 Flexfiel ds 10 14 39 Credit TP_CD PO 1740 A2 CR4 Flexfiel d15 40 Price TP_CD PO 1800 PR ADJ Adjust ments Data 41 Discoun TP_CD PO 1810 PR AD1 t List Names 42 Price TP_CD PO 1820 A1 AD1 Adjust ment Flexfiel ds 1 4 43 Price TP_CD PO 1830 A2 AD2 Adjust ment Flexfiel ds 5 9 Transaction Summary Layouts A 45 Sequen Data Trading Ref 1 Ref 2 Ref 3 Record Record Record ce Partner Number Layout Layout Qualifie r 44 Price TP_CD PO 1840 A2 AD3 Adjust ment Flexfiel ds 10 14 45 Price TP_CD PO 1850 A2 AD4 Adjust ment Flexfiel d15 46 Reserva TP_CD PO 1900 RS RES tions Data 47 Reserva TP_CD PO 1910 Al RS1 tion Flexfiel ds 1 4 48 Reserva TP_CD PO 1920 A2 RS2 tion Flexfiel ds 5 9 49 Reserva TP_CD PO 1930 A2 RS3 tion Flexfiel ds 10 14 50 Reserva TP_CD PO 1940 A2 RS4 tion Flexfiel d15 51 Act
236. _DATE This date is equal to the CREATION_DATE for this transaction This date is set to the system date LAST_UPDATED_BY This code is equal to the CREATED_BY code for this transaction OE_RESERVTNS_INTERFACE Table If you do not plan to use this feature you should deactivate the records that are associated to this table If you do not deactivate the records errors will occur in the Order Import validation because the records will be incomplete ORDER_SOURCE_ID This code identifies that the transaction was loaded into Order Import via the e Commerce Gateway DEFAULT The code is set to 6 meaning EDI 6 46 Oracle e Commerce Gateway Implementation Manual Update Columns Original System Reference Data ORIG_SYS_DOCUMENT_REF ORIG_SYS_LINE_REF ORIG_SYS_SHIPMENT_REF See Definition above ORIG_SYS_RESERVATION_REF CREATED_BY This code identifies who loaded this transaction into the Order Import tables The code is set to the Requester ID associated with the concurrent manager request that processed this transaction CREATION_DATE This is the date that the e Commerce Gateway loaded the transaction into the Order Import table entries This date is set to the system date LAST_UPDATE_DATE This date is equal to the CREATION_DATE for this transaction This date is set to the system date LAST_UPDATED_BY This code is equal to the CREATED_BY code for this transaction OE_ACTIONS_INTERFACE Table If you do not p
237. _FILE_DIR in the init ora file Once it processes a file that file is copied into the final directory below D inbound_flat_file Gateway_input archive Obviously mechanisms such as UNIX shell scripts or Windows batch files need to be defined to move these files between some of these directories Execution in some cases can be set up in the translator the movements from D outbound_flat_file to D outbound_flat_file archive and D inbound_flat_file Gateway_input to D inbound_flat_file Gateway_input archive will have to be set up to execute in Concurrent Processing as part of a Process Set running the Oracle e Commerce processing A degree of operating system expertise will be required for successful implementation For example a UNIX cron job needs to be set up to run the communication process ftp or mail file processing and then move the files to the other directories at certain times of the day If this process is followed you will be able to examine the files created at each step They will also be able to process without contention however there are eventually going to be a lot of files out there Even if disk space is fairly cheap eventually performance will force the removal of older files You may want to consider removing the files after you make the operating system backup Once they are preserved on a separate medium they can always be recovered as needed 4 36 Oracle e Commerce Gateway Implementation Manual 5
238. a HEADER 2040 Payment Terms Data HEADER 2050 Sales Representative HEADER 2060 Comments 5 6 Oracle e Commerce Gateway Implementation Manual Data Type Data Level Record Number Position 92 95 Header Flexfields HEADER 3000 3030 Header Allowance Charges HEADER 3080 3090 Extension Tables Header HEADER 3900 Data custom Basic Item Data ITEM 4000 Sales Order Data ITEM 4010 Part Descriptions Sales ITEM 4020 Channel Order Status Transaction Reference Key ITEM 4030 Line Flexfields ITEM 5000 5030 Extension Tables Item Data ITEM 5900 custom Line Tax Data ITEM DETAIL 6000 6010 Line Tax Flexfields ITEM DETAIL 6020 6060 Extension Tables Transaction ITEM DETAIL custom Line Detail Data Special Records Control Record 0010 Layout Control Record 0010 is used by both the Oracle e Commerce Gateway and the Translator for Trading Partner identification It includes data identifying the document transaction type transaction date and time Trading Partner code and whether it is a test or production transaction This record is 1024 characters long This record contains key data needed by the Oracle e Commerce Gateway Control Record 0010 is the first record for every transaction Transaction Interface File Architecture 5 7 The following table shows the record layout of the Control Record 0010 Included are the sequence number data element length position and sample data for inbound and outbound transactions Contro
239. a from Oracle Purchasing and Oracle Planning 6 178 Oracle e Commerce Gateway Implementation Manual Refer to the Oracle Purchasing Planning and Supplier Scheduling User s Guide for necessary profile set ups related to Purchasing MRP MPS and DRP There are no specific profile options that control how the planning schedules are extracted Planning Schedule Extract Options Extract Criteria The following table lists the planning schedule extract options The table lists the Oracle Applications Product the process and the method Oracle Applications Process Method Product Supplier Scheduling Scheduler s Workbench for Event Driven manually created schedules Supplier Scheduling AutoSchedule for Event Driven automatically created schedules Oracle e Commerce Gateway Outbound Planning Schedule Concurrent Manager Request Transaction Since the purpose of the Planning Schedule is to work closely with your suppliers to get the right materials to the right place at the right time the most expeditious option is to transmit the planning schedules at the time the schedule is created in the Scheduler Workbench or via AutoSchedule All planning schedules must be confirmed before they are eligible for extraction Schedules may be confirmed using the Scheduler Workbench or in AutoSchedule via the AutoConfirm process The outbound Planning Schedule transaction is controlled by two database views which are defined according to t
240. able Example Record 5000 Case Record 5000 START_DAT CUST_SHIP_ ITEM_DETAI UOM_CODE E_ TIME_DET TO_EXT_SD L_QUANTIT _INT_SD _SD Y_SD Pos 20 Pos 40 Pos 10 Pos 30 4000 1 5000 20000626 NULL 100 NULL 070000 2 5000 20000626 NULL 50 NULL 100000 Note Record 4000 data precedes its related 5000 series records Cases 1 amp 2 are examples of Just In Time JIT records Case 1 This is a JIT record for a quantity of 100 to be delivered at 7 00 AM on June 26 2000 Case 2 This is a JIT record for a quantity of 50 to be delivered at 10 00 AM on June 26 2000 Customer ship to external codes and unit of measurement UOM codes on Record 5000 are required only if they are different than previously indicated at the item level on Record 4000 Usually they are not different You may place the codes in these fields at any time Record 5010 Record 5010 contains the schedule subdetail that consists of three pairs of Item Detail Reference Values and its corresponding Item Detail Reference Codes The Item Detail Reference Code is a qualifier to indicate the type of data in its corresponding Item Detail Reference Values The qualifier may be the data qualifier defined in the EDI standard such as X12 or EDIFACT Application Transaction Detail 6 147 Note You can have a Record 5010 without a Record 5000 and vice versa They are independent of each other An example of a Record 5010 is shown in the table below Example Reco
241. able that will be written to the application open interface table Data found on the base application document or derived by the Oracle e Commerce Gateway This data will be written to the transaction interface file Data found on the transaction interface file or derived by the Oracle e Commerce Gateway This data is used to derive the Oracle internal code for the application open interface table Data found in the code conversion table given the internal code then written to the transaction interface file Data found in the code conversion table given the internal code then written to the transaction interface file The code conversion value table has a data element called Direction meaning transaction direction The transaction direction determines if the table entry is accessed Code Conversion 10 9 during the code conversion process Direction is in the table to allow additional flexibility to code conversion values and eliminate repeating entries for multiple Trading Partners as search keys The transaction Direction field in the code conversion tables allows table entries to be entered with duplicate internal codes or duplicate external codes depending on the value of the Direction code For inbound transactions duplicate external codes can be entered in the table which converts to the same internal code For outbound transactions duplicate internal codes can be entered in the table as long as the 1 5 external co
242. acle e Commerce Gateway and which on the Translator is part of the Synchronization process above One map can serve multiple Trading Partners Detecting Files The Translator must recognize when it has data waiting to be translated or communicated Normally this is done manually by the user or by the presence of a file in a given directory This is why the files built by the Oracle e Commerce Gateway are in one directory moved to another directory to be translated and once formatted to the desired standard moved into a third directory to be communicated Transferring Files The link between the Translator and the Gateway must also be considered i e are they on the same server on different UNIX boxes or is the Translator on a mainframe This affects both the file structures going back and forth e g variable for UNIX but fixed width for mainframe transfers and possibly the functionality of the Translator For example the mainframe based Translator may use an older architecture which means it is potentially less flexible in set up terms than its newer UNIX cousin Communications The Translator identifies and uses the communication method specified for each trading partner This can be any method supported by the hardware and software of the system Implementation Details 4 33 Archive Backup The goal of archiving or backing up data is to preserve data at each stage of its creation and transmission so that it can be recovered if
243. ading Partner address site If an EDI Location Code is used exclusively in the Control Record as a default it does not need to be a real location of the customer e g it need not be a real ship to location for a customer for an inbound purchase order The EDI Translator could assign a default EDI Location Code on the Control Record which could be associated with the Translator Code so the Trading Partner determinations can be done in the Oracle e Commerce Gateway The address site still must be fully defined in Oracle e Commerce Gateway See Transaction Detail Address Records page 9 15 Note A constant or default EDI Location Code for a given Oracle Customer or Oracle Supplier may be used for any inbound transaction The address site associated with that EDI Location Code is used to determine the Oracle Customer or Oracle Supplier to be associated with Trading Partner 9 15 all the address sites in the detail of that transaction For example the table below shows the three customer addresses defined in Oracle Order Entry Oracle Receivables for the Customer Acme Corp with Customer ID 123423 For this customer the EDI Location Code CHIC could be used as a Default EDI Location Code in the Control Record 0010 Whatever is placed in the EDI Location Code in the Control Record in this case CHIC it will be used to retrieve the customer level data Acme Corp with Customer ID 123423 The Trading Partner setup for the address associat
244. alyst First Name Material Analyst Phone Material Analyst e Mail ECE_PO_INTERFACE_LINES_X Transaction Record ID Material Analyst Code Legend Material Analyst Last Name Unique ID Material Analyst First Name Required Material Analyst Phone Optional Material Analyst e Mail The following process is performed to bring all the data together into the common interface tables before writing the records to the output file 1 The Oracle e Commerce Gateway extracts and denormalizes all the relevant Oracle base application data including Trading Partner data into the transaction specific interface tables Any enabled code conversions are performed after the data is extracted from the base application tables but before the data is written to the interface tables Using a unique identifier from the interface tables as search keys data elements are selected from the appropriate external source and written to the extension tables All data elements from both the interface tables and their corresponding extension tables are formatted into 1024 byte or less records sequenced and written to the transaction common ECE_OUTPUT table The formatted records in the ECE_OUTPUT table are written in the proper 11 4 Oracle e Commerce Gateway Implementation Manual sequence to the output file 6 The transaction records are deleted from the interface tables extension tables and the output table Using the outbound Purchase Order transact
245. ansaction Layout By defining the validation rules you indicate how a transaction is to be validated what constitutes an exception and what action to take if an exception is detected This ensures that only valid transactions are passed to Oracle e Commerce Gateway for processing Oracle e Commerce Gateway supports the following validation and exception processing rules The transaction exception rules include invalid trading partner invalid Address and Test Production mode discrepancy The data validation rules and their descriptions are listed in the following table Data Validation Rules Data Rule Description Data Type Checking Default if Null Null Dependency Predefined List Simple Lookup Valueset Lookup Compares the data types of the data in the file to the data type defined in Gateway transaction table Moves a default value to the staging table column if the field is NULL blank in the interface file Checks if the incoming data for a given column has a null dependency Checks if the incoming data for a given column is equal to or not equal to a value ina predefined list in the Oracle e Commerce Gateway Checks if the incoming data for a given column is a valid value equal to the one found in the user defined table and column that will be used in a SQL Select Statement Checks if the incoming data for a given column is a valid value in a standard Oracle Valueset 1 4 Oracle e Commerce
246. ant transaction area Understanding the Oracle e Commerce Gateway Functions Attend an Oracle e Commerce Gateway Course Implementers should attend an Oracle e Commerce Gateway course They must understand all the features including profile setups process rules column rules trading partner definitions and code conversion for setting up the product Understand Trading Partner Setups It is essential that the relationship between Translator and EDI Location Codes be completely understood Also a policy should be put in place with the customer so an administrator can easily maintain the trading partner setup screens given only basic data about the Trading Partner Location and permissible transactions Understand General Code Conversion Setups The Code Conversion capabilities of the Oracle e Commerce Gateway can provide a comprehensive set of criteria to convert internal Oracle codes site codes payment codes etc to from the terms used by the Trading Partners These conversions can be undertaken globally or based upon specific criteria using up to five keys see the Oracle e Commerce Gateway User s Manual for more details Conversion requirements should be carefully planned and kept as simple as possible to avoid over complex situations requiring burdensome maintenance Understand Extension tables for Outbound Transactions Implementers should understand or have access to a developer who understands PL SQL and how data is stored in th
247. anual Setup for Text Note Original Change Use Length Translator Data The translator 80 Map will map each data element to a field that is your specified length You do not need to manipulate text size to fit into a standard data element if the data was divided into several record in the transaction interface file The use of attachments is not required If not used consider disabling the attachment record defined for the transaction Refer to Modify Transaction Interface File page 4 23 for more details Common Setup Errors The following are common set up errors related to system transaction level profiles e Did not define system level profile options e Concurrent Manager log file reflects an error indicating transaction is not enabled e Errors regarding address derivation occurred Refer to Troubleshooting chapter for details Determine Process and Column Rules and Actions Oracle e Commerce Gateway s exception handler is designed to provide quick and easy analysis of any exception detected during inbound processing It is a tool to pre validate incoming data before the data is imported into Oracle Application s Open Interface tables for processing into Oracle Applications base tables The exception handler uses tree style navigation and color coded icons to help you quickly identify the exception Dynamic windows and drill downs provide summary and detailed information to help you analyze and diagnose the cause o
248. are displayed in the following table Any transaction may use any range of numbers for a data level 5 16 Oracle e Commerce Gateway Implementation Manual Sample Record Numbers Record Number Record Number Content Sample Simple Transaction Sample Longer Transaction 0010 0010 Control Record 0020 0070 0020 0070 Oracle e Commerce Gateway Flexfields 1000 1890 1000 4890 Application Header Level 1900 1990 4900 4990 Application Header Level Extension Table Custom 2000 2890 5000 5890 Application Detail Level 1 2900 2990 5900 5990 Application Detail Level 1 Extension Table Custom 3000 3890 6000 6890 Application Detail Level 2 3900 3990 6900 6990 Application Detail Level 2 Extension Table Custom 4000 4890 7000 7890 Application Detail Level 3 4900 4990 7900 7990 Application Detail Level 3 Extension Table Custom The numbering scheme per data level is in increments of 1000 The numbering scheme per record is in increments of 10 allowing for new data levels and records to be inserted The record numbers are not used consistently across transactions For example the record 1050 may contain different data depending upon the transaction The X900 series in any range is reserved for the Oracle e Commerce Gateway extension tables for consistency Record Layout Code 96 97 The record layout code is used to indicate the type of data in the record These codes are particularly useful when reusable records such as addres
249. are using those records When testing this transaction be sure to change all values of the Original System References for each test otherwise the transaction will fail in the Order Import validation due to duplicate entries Customer Shipment Number CUSTOMER_SHIPMENT_NUMBER is a counter for the set of shipment data within an item that is identified by the same CUSTOMER_LINE_NUMBER The customer in the transaction sends this number It can be used to match change order shipment records to the base order line record if you copy it to the ORIG_SYS_SHIPMENT_REF not use the default It has no purpose if the inbound purchase order process generates this number Order Management has its own shipment number counter that is used in Order Import Sample X12 X12 Data Element Order Import Data Order Import Data Segment Elment for this Customer Generate d Data First PO1 Assigned CUSTOMER_LINE_ 001 Identification on PO1 NUMBER First SCH Assigned CUSTOMER_SHIPM 1 Identification on SCH ENT NUMBER within last PO1 Second SCH Assigned CUSTOMER_SHIPM 2 Identification on SCH ENT NUMBER within last PO1 Third SCH Assigned CUSTOMER_SHIPM 3 Identification on SCH ENT NUMBER within last PO1 Application Transaction Detail 6 23 Sample X12 X12 Data Element Order Import Data Order Import Data Segment Elment for this Customer Generate d Data Second PO1 Assigned CUSTOMER _LINE_ 002 Identification on NUMBER PO1 First SCH Assigned CUSTOMER_S
250. assed to the Order Import tables following the logic of the code conversion process Refer to Code Conversion page 10 1 for details The following table levels of data are included in the transaction file at both the Order header and Order line level Additional Original System reference data is required at the Order line level Data is only required if these tables are used e OE_CREDITS_INTERFACE e OE_PRICE_ADJS_INTERFACE e OE_RESERVTNS_INTERFACE e OE_ACTIONS_INTERFACE e OE_PRICE_ATTS_INTERFACE The following table level of data is included in the transaction file at the Order line level only Data is only required if the table is used e OE_LOTSERIALS_INTERFACE Leave at least one column activated to appear in the transaction interface file Header Level Records for O0E_CREDITS_INTERFACE Oracle Oracle Hardcoded Deri Record Number Position Applications e Commerce ved Number Column Name Gateway for Required Column Name Fields ORIG_SYS_DOC ORIG_SYS_DOC_ Required 1700 010 UMENT_REF UMENT_REF ORIG_SYS_CRE ORIG_SYS_ Required 1700 030 DIT_REF CREDIT _REF OPERATION_C OPERATION_C _ If Null default 1700 040 050 ODE ORDER_SOURC E_ID ODE _EXT1 ORDER_SOURC E_ID to INSERT Hard code 6 meaning EDI 6 32 Oracle e Commerce Gateway Implementation Manual Oracle Oracle Hardcoded Deri Record Number Position Applications e Commerce ved Number Column Name Gateway for Required Column Name Fields
251. at any one of our many Education Centers you can arrange for our trainers to teach at your facility or you can use Oracle Learning Network OLN Oracle University s online education utility In addition Oracle training professionals can tailor standard courses or develop custom courses to meet your needs For example you may want to use your organization s structure terminology and data as examples in a customized training session delivered at your own facility Support From on site support to central support our team of experienced professionals provides the help and information you need to keep Oracle e Commerce Gateway working for you This team includes your Technical Representative Account Manager and Oracle s large staff of consultants and support specialists with expertise in your business area managing an Oracle Database and your hardware and software environment Do Not Use Database Tools to Modify Oracle Applications Data xviii Oracle STRONGLY RECOMMENDS that you never use SQL Plus Oracle Data Browser database triggers or any other tool to modify Oracle Applications data unless otherwise instructed Oracle provides powerful tools you can use to create store change retrieve and maintain information in an Oracle database But if you use Oracle tools such as SQL Plus to modify Oracle Applications data you risk destroying the integrity of your data and you lose the ability to audit changes to your data Because Ora
252. atabase table an external non Oracle relational database or a file Collectively call these tables and files external tables or external source data in this chapter The external table must contain the unique key which is a data element also found in the Oracle e Commerce Gateway interface table If the data is not already in the Oracle e Commerce Gateway transaction interface table the code needs customization to add that unique identifier to the interface tables in order to become a key to the records in the external source data The illustration below shows the ECE_PO_INTERFACE_LINES interface table and its corresponding extension table ECE_PO_INTERFACE_LINES_X The ECE_PO_INTERFACE_ LINES table contains the element Item ID which is used as the unique key for a custom Oracle Applications table called MATERIAL_ANALYST The data from the MATERIAL_ANALYST table is used to populate the ECE_PO_INTERFACE_LINES_X table Extensible Architecture 11 3 Relationship Diagram Between Oracle e Commerce Gateway Tables and Oracle Applications Custom Table Oracle e Commerce Gateway Interface and Extension Tables Oracle Applications Custom Table ECE_PO_INTERFACE_LINES PO Number PO Type Release Number Line Number Line Order Quantity MATERIAL_ANALYST Line UOM Item ID nef Inventory Item ID Line Attribute 1 Line Attribute 2 Material Analyst Code Material Analyst Last Name Transaction Record ID Material An
253. ated unit of measure code as defined in Oracle Inventory CUSTOMER_ITEM_EXT This is the external Customer part number that is defined in Oracle Inventory and cross referenced to an inventory item Review Oracle e Commerce Gateway Exceptions Use the Oracle e Commerce Gateway View Staged Documents window to review the Oracle e Commerce Gateway transaction exceptions Once the exceptions are identified and resolved you can submit the transaction for reprocessing ignore the exception during reprocessing or delete the transaction Select the option in the View Staged Documents window Resolve Oracle e Commerce Gateway Exceptions To resolve Oracle e Commerce Gateway exceptions you can either correct the set up data in Oracle e Commerce Gateway or Oracle Applications or ask the Trading Partner to send a corrected transaction If the Trading Partner sends a corrected transaction you must delete the erroneous transaction from Oracle e Commerce Gateway s staging tables using the View Staged 6 166 Oracle e Commerce Gateway Implementation Manual Documents window Relevant Oracle Release Management Profiles and Setup The following is a list of the Release Management setups related to the Release Management Demand Processor Refer to the Oracle Release Management Implementation Manual and Oracle Release Management User s Guide for the details 1 RLM MRP Forecast Selection List e If defined the MRP Forecast Selection List lists all th
254. ateway transaction exceptions Once the exceptions are identified and resolved you can submit the transaction for reprocessing ignore the exception during reprocessing or delete the transaction Select the option in the View Staged Documents window Resolve Oracle e Commerce Gateway Exceptions To resolve Oracle e Commerce Gateway exceptions you can either correct the set up data in Oracle e Commerce Gateway or Oracle Applications or ask the Trading Partner to send a corrected transaction If the Trading Partner sends a corrected transaction be sure to delete the erroneous transaction from Oracle e Commerce Gateway s staging tables using the View Staged Documents window The duplicate transaction may cause confusion Relevant Oracle Payables Profiles and Setups The following is a list of the Payables set ups related to the Receiving Open Interface Application Transaction Detail 6 75 Invoice Hold Reason You can optionally set up an Invoice Hold Reason unique to this transaction All invoices being imported into Oracle Payables may be placed on hold using the unique Invoice Hold Reason This may be useful during implementation of a new trading partner so that you can review the electronically transmitted invoices before approving them for payment Use the Invoice Approvals window to define an invoice hold reason Refer to Oracle Payables User s Guide for details Payables Open Interface Required Fields The Payables Open Interfac
255. ay Implementation Manual Data Trading Partner Ref 1 PS Ref2 Ref3 ITEM SCHE DULE Record Number Record Layout Record Layout Qualifie r 49 50 51 52 53 54 Item Flexfiel d15 Ship to Organiz ation Flexfiel ds item 1 4 Ship to Organiz ation Flexfiel ds item 5 9 Ship to Organiz ation Flexfiel ds item 10 14 Ship to Organiz ation Flexfiel d item 15 Organiz ation Option Flexfiel ds 1 4 TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD PS PS PS PS PS PS ITEM ITEM ITEM ITEM ITEM ITEM 2180 2200 2210 2220 2230 2250 A2 Al A2 A2 A2 Al IT4 DI1 DI2 DI3 DI4 SO1 Transaction Summary Layouts A 241 Data Trading Partner Ref 1 PS Ref2 Ref3 ITEM SCHE DULE Record Number Record Record Layout Layout Qualifie r 55 56 57 58 59 60 61 Organiz ation Option Flexfiel ds 5 9 Organiz ation Option Flexfiel ds 10 14 Organiz ation Option Flexfiel d15 Schedul e Item Flexfiel ds 1 4 Schedul e Item Flexfiel ds 5 9 Schedul e Item Flexfiel ds 10 14 Schedul e Item Flexfiel d15 TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD PS PS PS PS PS PS PS ITEM ITEM ITEM ITEM ITEM ITEM ITEM 2260 2270 2280 2300 2310 2320 2330 A2 A2
256. ay appear in the interface data file with no data if the columns are not enabled Trading Partner flexfields are not applicable to inbound transactions You must enable the Trading Partner header flexfields and Trading Partner detail flexfields system administration required to use them Common Record Key 1 100 The table below describes the Oracle transaction interface file record key which occupies the first 100 characters of each record in every transaction This record area facilitates any visual audit and research into the file Note The content of the first 100 characters on the control record 0010 is defined the same as every other record for a given transaction The record number allows the Translator to uniquely identify a record layout within the transaction Do not rely on the record layout code and record layout qualifier to uniquely identify a record Some transaction data in the record key may be truncated so the Translator should refer to the full transaction data in the data area positions 101 1024 of the record The data in Key 1 through Key 3 varies by the transaction and the record level within the transaction The following table displays a summary of the Record Key 0 100 data elements Record Key 1 100 Data Element Summary Seq Data Element Position Length 1 Translator Code 1 25 25 short Transaction Interface File Architecture 5 15 Seq Data Element Position Length 2 Key 1 Prima
257. ays have all flexfields available to be mapped the mapping should therefore be verified on a case by case basis e Unlike the extensible architecture the data that can be mapped into the flexfields is limited to the number of flexfields that have been activated within Oracle Applications and is also limited by the scope of the Application Open Interface for a given inbound transaction e Any additional data that is passed via flexfields must have a suitable corresponding position within the fields available in the message standard being used Descriptive Flexfields in the base Oracle Applications Subject to the comments mentioned in the previous section data contained within the flexfields activated in the Oracle Applications can be transmitted outbound via the Oracle e Commerce Gateway Most additional data transmission requirements can be met using mapped flexfields where the extra data required is to be found within the relevant Oracle Applications Oracle e Commerce Gateway Extensible Architecture The Oracle e Commerce Gateway Extensible Architecture feature is used when data from an outside application must be merged with Oracle Applications data to create a single outbound transaction This feature affords great flexibility to customize outbound transactions based on individual business needs For example there may be data contained in legacy systems tables or files that must be included in a transmission along with data extracted fr
258. be written on the control record for tracking The transaction data in the transaction detail records follow the control record Descriptive Flexfield Records Records 0020 0070 The Oracle e Commerce Gateway has descriptive flexfields in records 0020 0070 in any outbound transaction interface file This flexfield data is written to the outbound transaction interface file whenever the flexfields are defined They are available for data mapping in the Translator Common Record Key 5 2 Oracle e Commerce Gateway Implementation Manual Each record has two sections the record common key positions 1 100 and the application data area positions beyond 100 The common key is written on every record in the file It is used as a visual reference on each record to facilitate browsing the file or extracting transaction from a file if needed The following key data is in the common key Not all the fields are mentioned here e Translator Code is the code that identifies the Trading Partner in the Translator e Reference 1 is the document or transaction identifier from the header record of the transaction For example it may be the invoice number or the purchase order number e Reference 2 is an identifier from the next document level such as a line or detail level For example it may be a line number e Reference 3 is an identifier from the next document level such as a shipment level For example it may be a shipment number Note that on
259. ber 70 91 22 blank N A 92 95 4 varies Record Number 96 97 2 varies Record Layout 98 100 3 varies Record Layout Qualifier The following table shows the Common Key positions 1 100 for the records of the Inbound Shipping and Billing Notice transaction Transaction specific Data in the Common Key of the SBNI Transaction Per Record Record TP_CD Ref1 Ref 2 Ref 3 Record Record Record SHIPM LINE blank Number Layout Layout ENT Qualifie r 1 Control TP_CD SHIPM 0010 CT CTL Record ENT 2 Shipme TP_CD SHIPM 1000 L1 DL1 nt ENT Notice Basic Header A 128 Oracle e Commerce Gateway Implementation Manual Record TP_CD Ref1 Ref 2 Ref 3 Record Record Record SHIPM LINE blank Number Layout Layout ENT Qualifie r Carrier TP_CD SHIPM 1010 L2 DL2 Weights ENT Packagi ng Shipme TP_CD SHIPM 1020 L3 DL3 nt ENT Method of Paymen t Currenc TP_CD SHIPM 1030 L4 DL4 y Tax ENT Paymen t Terms Allowa TP_CD SHIPM 1040 L5 DL5 nces Ch ENT arges Freight Hazard TP_CD SHIPM 1050 HZ HZ1 ous ENT Material Special Handlin 8 Header TP_CD SHIPM 1090 N1 NH1 Note ENT Vendor TP_CD SHIPM 1100 AD SF Address ENT Code Transaction Summary Layouts A 129 Record TP_CD Ref1 Ref 2 Ref 3 Record Record Record SHIPM LINE blank Number Layout Layout ENT Qualifie r 10 Destinat TP_CD SHIPM 1120 AX ST ion ENT Address Code 11 Destinat TP_CD SHIPM 1130 CN ST ion ENT Con
260. bility of these Web sites 1 Introduction This chapter contains implementation information about Oracle e Commerce Gateway 2 Implementation Positioning This chapter contains information about Oracle e Commerce Gateway implementation 3 Oracle e Commerce Gateway Implementation Checklist This chapter contains Oracle e Commerce Gateway implementation steps and checklists 4 Implementation Details This chapter contains Oracle e Commerce Gateway implementation details 5 Transaction Interface File Architecture This chapter contains information about transaction interface file architecture 6 Application Transaction Detail This chapter contains information about application transaction detail 7 Test Transactions This chapter contains test transactions for Oracle e Commerce Gateway implementation 8 Troubleshooting This chapter contains troubleshooting information about Oracle e Commerce Gateway implementation 9 Trading Partner This chapter contains trading partner information 10 Code Conversion This chapter contains the code conversion information about Oracle e Commerce Gateway implementation 11 Extensible Architecture This chapter contains extensible architecture information about Oracle e Commerce Gateway implementation A Transaction Summary Layouts This appendix contains transaction summary information for Oracle Applications about Oracle e Commerce Gateway implementation Related Information Sources You can
261. ble menu on your Oracle Applications HTML help window by reading from the Oracle Applications Documentation Library included in your media pack or by using a Web browser with a URL that your system administrator provides If you require printed guides you can purchase them from the Oracle Store at http oraclestore oracle com Guides Related to All Products Oracle Applications User s Guide This guide explains how to navigate enter data query and run reports using the user interface UI of Oracle Applications This guide also includes information on setting user profiles as well as running and reviewing concurrent requests You can access this guide online by choosing Getting Started with Oracle Applications from any Oracle Applications help file Documents Related to This Product xiv Oracle e Commerce Gateway User s Guide This guide describes the functionality of Oracle e Commerce Gateway and the necessary setup steps in order for Oracle Applications to conduct business with trading partners through Electronic Data Interchange EDI It also contains how to run extract programs for outbound transactions import programs for inbound transactions and the relevant reports Oracle Purchasing User s Guide This guide describes how to create and approve purchasing documents including requisitions different types of purchase orders quotations RFQs and receipts This guide also describes how to manage your supply base th
262. bled the import process proceeds to validate the transaction using the user defined column rules If no process or column rule exceptions are detected the Oracle e Commerce Gateway import program will write the transaction to the Receiving Open Interface tables to be processed by the Receiving Open Interface API Oracle e Commerce Record Number Position Number Note Gateway Column Name for Required Fields TEST_INDICATOR 0010 20 T or P ASN_TYPE 0010 30 ASNT or SBNI Document ID TRAN PURPOSE_EX 0010 50 NEW or CANCEL TI TP_TRANSLATOR_C 0010 70 Translator identifier ODE for this Trading Partner TP_LOCATION_CO 0010 80 The EDI Location DE Code PICK_SLIP_NUMBE 1000 10 R TRAN_PURPOSE_A 1000 110 NEW or CANCEL PPLICATION PURCHASE_ORDER 2000 50 _NUM ORIGINAL_SYSTEM 2000 70 _LINE_REFERENCE 6 106 Oracle e Commerce Gateway Implementation Manual Oracle e Commerce Record Number Position Number Note Gateway Column Name for Required Fields QUANTITY Defaulted to ship quantity in record 2000 position 80 SHIPPED_UNIT_CO 2000 90 DE_INT Control Record 0010 ASN_TYPE Document ID This column identifies the type of document being sent by the Trading Partner If this document type is not enabled for the trading partner defined in Oracle e Commerce Gateway a process rule exception is detected Then an exception message is displayed in the View Staged Documents window The valid
263. bound transaction view and not from the associated outbound interface table Therefore when using the ece_flatfile_pvt package procedures and functions make sure that the COLUMN_NAME value that is passed matches the column name in the associated view To complete the earlier example suppose that the custom table MATERIAL_ANALYSTS contains the column INVENTORY_ITEM_ID to associate the material analyst contact data with a specific purchasable item The following modifications to the Populate_Ext_Lines procedure will extract the necessary data from the custom database table and insert it into the extension table The Procedure POO and POCO Transactions Only 11 14 Oracle e Commerce Gateway Implementation Manual PROCE rs ae ae Kk DURE Popu Variable v_ItemID v_ItemIDPosition INT vm v_mat_last_name VARCHAR2 v_mat_first name VARCHAR2 500 at_code late Ext Line 1 fkey IN NUMBER l_plsql_table IN ece flatfile PVT interface tbl type definitions INTEGER r VARCHAR2 w w mi mi r 500 500 r v_mat_phone VARCHAR2 500 v_mat_email VARCHAR2 500 temp position INTEGER old_value BEGIN Kk Kk Kk Kk ey Find the VARCHAR2 32767 position of the ITEM ID in the PL SQL table Then use the value stored in that position to select the necessary contact data from the MATERIAL AN
264. c t Number s FOB Point Freight Terms TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD PO PO PO PO PO PO PO LINE LINE LINE LINE LINE LINE LINE 2010 2020 2030 2040 2050 2060 2070 IT IT IT DM IT PD FB IT2 SG1 SG2 DMD PTT PRJ FOB Transaction Summary Layouts A 67 Seq Data Trading Partner Ref 1 Ref 2 Ref 3 Record Number Record Layout Record Layout Qualifie r 39 40 41 42 43 44 45 46 Shipme nt Priority Method Freight Carrier Sales represe ntative Referen ce Ids UOM Ship Pr omise Dates Lead Time Item Flexfiel ds 1 4 Item Flexfiel ds 5 9 Item Flexfiel ds 10 14 Item Flexfiel ds 15 Global Flexfiel ds 1 4 TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD PO PO PO PO PO PO PO PO LINE LINE LINE LINE LINE LINE LINE LINE 2080 2090 3000 3100 3110 3120 3130 3200 SH MS DT Al A2 A2 A2 Al SHP LNE DTL IT1 IT2 IT3 IT4 GL1 A 68 Oracle e Commerce Gateway Implementation Manual Seq Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner Number Layout Layout Qualifie r 47 Global TP_CD PO LINE 3210 A2 GL2 Flexfiel ds 5 9 48 Global TP_CD PO LINE 3220 A2 GL3 Flexfiel ds 10 14 49 Global
265. categories of Processing Rules attributes e Demand Management Application Transaction Detail 6 149 e Demand Fences e Order Management e CUM Management e General e These five categories are defined for each Ship From Ship To business entity for which Release Management will process demand e If terms are not defined at the optional lower levels they will default from higher levels There are three levels where the Processing Rules can be defined e Ship From Customer mandatory e Ship From Address optional e Ship From Customer Item optional can be linked to either of the other two levels Release Management Demand Processor Required Fields The Release Management Demand Processor is used to process Planning Material Release Shipping Schedule and Production Sequence Schedule transactions It validates the incoming data entered into the Release Management Interface tables by the Oracle e Commerce Gateway import program The following is a list of the Release Management Demand Processor required fields These fields are required for the Release Management Demand Processor to successfully process and move the data from the Release Management Interface tables into the Oracle Order Management and Oracle Planning base application tables Required fields noted as derived or hardcoded do not require a value in the transaction on the transaction interface file since the values are determined by the Oracle e Commerce Gateway p
266. ce Counter of the Record 2000 70 91 22 SEQ _SUBLINE Sequence Counter of Record 4000 within the given Record 2000 92 95 4 varies Record Number 96 97 2 varies Record Layout 98 100 3 varies Record Layout Qualifier The following table shows the Common Key positions 1 100 for the records of the Inbound Production Sequence Schedule transaction Transaction Summary Layouts A 221 Transaction specific Data in the Common Key of the PSQI Transaction Per Record Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner SCH_R SEQ SEQ_S Number Layout Layout EF UBLINE Qualifie r 1 Control TP_CD SCHR 0010 CT CTL Record EF 2 Basic TP_CD SCH_R 1000 HD HDR Schedul EF e Header 3 Schedul TP_CD SCH_R 1010 NT HDR e EF Header Note Text 4 Custom TP_CD SCHR 1020 Al SIH er EF Address 5 Schedul TP_CD SCHR 1080 CO HDR e EF Header Misc Contact s 6 Schedul TP_CD SCH_R 1090 RF HDR e EF Header Misc Referen ces 7 Schedul TP_CD SCH_R 1500 A1 SH1 e EF Header Flexfiel ds A 222 Oracle e Commerce Gateway Implementation Manual Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner SCH_R SEQ SEQ_S Number Layout Layout EF UBLINE Qualifie r 9 Schedul TP_CD SCH_R 1510 A2 SH2 e EF Header Flexfiel ds 10 Schedul TP_CD SCH_R 1520 A2 SH3 e EF Header Flexfiel ds 11 Schedul TP_CD SCH_R 1530 A2 SH4 e EF Header Flexfiel ds 12 Trading TP_CD SCHR 1600 Al 1H1 Partner EF Header Flexfiel ds 13 Tra
267. ce table has the flexfield with the full length of 150 characters if needed Transaction Interface File Architecture 5 19 Record Layout Codes Description Meaning A2 Flexfield Layout 2 A3 Flexfield Layout 3 A4 Flexfield Layout 4 A5 Flexfield Layout 5 Flexfields Layout 2 Layout 2 contains attributes each with length 80 The interface table has the flexfield with the full length of 150 characters if needed Flexfields Layout 3 Layout 3 contains the Flexfield Context plus attributes each with length 100 The interface table has the attribute with the full length of 150 characters if needed Flexfields Layout 4 Layout 4 contains attributes each with length 100 The interface table has the flexfield with the full length of 150 characters if needed Flexfields Layout 5 Layout 5 contains four pairs of internal defined flexfields and its external converted codes plus the Flexfield Context The interface table has the flexfield with the full length of 150 characters if needed 5 20 Oracle e Commerce Gateway Implementation Manual Record Layout Codes Description Meaning A6 Flexfield Layout 6 AD Address Record AX Address Record CN Contact Record Format 1 CM Contact Record Format Flexfields Layout 6 Layout 6 contains four pairs of internal defined flexfields and its external converted codes The interface table has the flexfield with the full length of 150 characte
268. cle Applications tables are interrelated any change you make using an Oracle Applications form can update many tables at once But when you modify Oracle Applications data using anything other than Oracle Applications you may change a row in one table without making corresponding changes in related tables If your tables get out of synchronization with each other you risk retrieving erroneous information and you risk unpredictable results throughout Oracle Applications When you use Oracle Applications to modify your data Oracle Applications automatically checks that your changes are valid Oracle Applications also keeps track of who changes information If you enter information into database tables using database tools you may store invalid information You also lose the ability to track who has changed your information because SQL Plus and other database tools do not keep a record of changes xix 1 Introduction This chapter contains implementation information about Oracle e Commerce Gateway This chapter covers the following topics e Purpose of the Implementation Manual e Documentation e Oracle e Commerce Gateway Overview e Processing Traditional EDI Transactions e EDI Translators Purpose of the Implementation Manual The Oracle e Commerce Gateway Implementation Manual provides details to facilitate implementation of the product and highlights additional actions to ensure a successful implementation While Oracle e
269. cle e Commerce Gateway provides several methods to extend currently supported transactions through the use of trading partner reference fields descriptive flexfields and Oracle e Commerce Gateway Extensible Architecture Refer to Enable Additional Transaction Data for details on when and how to use each method Synchronize New Transaction Layout Definitions with Translator Once the necessary changes are entered re run the Transaction Layout Definition Report and use the report output to synchronize your new transaction layout definitions with the translator Common Transaction Interface File Definition Errors Moving data elements from the line level to the header level Changing the record layout or column attributes of the control record Deleting the control record Incorrect usage of external fields for code conversion Exceeding maximum record length of 1024 bytes Deleting data element containing a process rule Deleting data elements that are required by Oracle e Commerce Gateway or Oracle Applications Refer to Troubleshooting chapter for details Set Up Trading Partners The steps for setting up a Trading Partner are detailed below First read the chapter on the Trading Partner for important details about the Trading Partner Reference the Oracle e Commerce Gateway User s Guide for details to complete the windows 1 Define Trading Partner Group Enter a new Trading Partner Group or access an existing Trading Partner Group
270. contains extensible architecture information about Oracle e Commerce Gateway implementation This chapter covers the following topics e Customizing EDI Transactions e Descriptive Flexfields e Steps for Extensible Architecture Customizing EDI Transactions The Oracle e Commerce Gateway provides two methods to add data elements to transactions that are not defined in the Oracle Applications data model The two methods are e Descriptive Flexfields e Extensible Architecture Either method may be used separately or both methods may be used to customize a specific transaction to meet the business needs Descriptive flexfields may be used for both inbound and outbound transactions while the Extensible Architecture feature applies only to outbound transactions The transactions in the following table use the Extensible Architecture described below Refer to Oracle Support s website for documentation for the other outbound transactions using another method of Extensible Architecture which does not use transaction specific ECE_ tables Extensible Architecture 11 1 Oracle Products Use Extensible Architecture to Customize EDI Transactions Oracle Product Transaction ASCX 12 EDIFACT Description Code Oracle Payables PYO 820 PAYORD Payment Remitt REMADV ance Advice Oracle INO 810 INVOIC Invoice Receivables Oracle POO 850 ORDERS Purchase Orders Purchasing Oracle POCO 860 ORDCHG Purchase Order Purchasing Changes Oracle Supplier
271. cord Summary Type of Data Data Level Record Number Note 1 Control Record HEADER 0010 2 Trading Partner HEADER 0020 0050 Custom Header Attributes 3 Trading Partner HEADER 0060 0070 Custom Detail Attributes 4 Advice Header HEADER 1000 1010 Flexfields External References 6 Advice Header HEADER 1020 1030 Flexfields Internal References 8 Trading Partner HEADER 1040 Address 9 Extension Table HEADER 1900 Custom Header Level 10 Advice Detail DETAIL 2000 2010 Flexfields External References 12 Advice Detail DETAIL 2020 2030 Flexfields Internal References 14 Advice Detail DETAIL 2040 Data Error 15 Advice Detail DETAIL 2050 Data Accepted 16 Extension Table DETAIL 2900 Custom Detail Level Outbound Application Advice Common Key A 134 Oracle e Commerce Gateway Implementation Manual The following table shows the Common Key positions 1 100 for the Outbound Application Advice transaction The table shows the position length code and content of the Common Key elements Transaction specific Data in the ADVO Common Key Position Length Code Content 1 25 25 TP_CD Trading Partner Code as defined in the EDI Translator 26 47 22 DOC Related Document ID 48 69 22 ERR_CNT Error Counter 70 91 22 blank Not Used 92 95 4 varies Record Number 96 97 2 varies Record Layout 98 100 3 varies Record Layout Qualifier The following table shows the Common Key positions 1 100 for the records of t
272. ct supplier supplier site selected for the Trading Partner definition in Oracle e Commerce Gateway The selected supplier supplier site and the EDI Location Code defined in Oracle Applications are displayed in the Define Trading Partners window Assignment tab If the data is not what you intend it to be you must make the appropriate changes for the transaction to be extracted for the correct trading partner This could involve either altering the supplier supplier site in the base Oracle Application or assigning a different supplier supplier site to that EDI Location Code in Oracle e Commerce Gateway Please note that if the trading partner is associated with multiple operating units then the transaction to be extracted is for a specified operating unit only linked to your responsibility To extract all the data for multiple operating units you still need to execute the program one by one by specifying different operating unit each time when you run the program See the Outbound Transactions chapter in the Oracle e Commerce Gateway User s Guide for details Refer to the Trading Partner chapter for recommendations on selecting the correct trading partner EDI Location Code for the control record 0010 for the transaction in the transaction interface file Relevant Oracle Application Profiles and Setups Use Oracle Supplier Scheduling Scheduler s Workbench to create planning schedules Oracle Supplier Scheduling will gather the supply and demand dat
273. cted customer address and the EDI Location Code defined in Oracle Applications are displayed in the Assignment tab of the Define Trading Partners window If the data is not correct you must make the appropriate changes for the transaction to be imported for the correct trading partner This could involve either altering the customer address in the base Oracle Application or assigning a different customer address to that EDI Location Code in Oracle e Commerce Gateway Note On inbound EDI Demand Transactions the customer also sends a Supplier Code The Supplier Code identifies the Supplier to the customer The Supplier Codes are defined in the Release Management Processing Rules Window They are not defined in the e Commerce Gateway to be used by this transaction process Refer to the Release Management Implementation Manual and the Release Management User s Guidefor additional information on setting up the Supplier Code Oracle e Commerce Gateway Required Fields The following table lists the Oracle e Commerce Gateway required fields These fields are required to authenticate the trading partner and transaction If the required data is not provided in the transaction the Oracle e Commerce Gateway import process fails the transaction and an exception message will display in the View Staged Documents window If the trading partner is valid and the transaction is enabled the import process proceeds to validate the transaction using the user defi
274. ction Transaction ASC X12 EDIFACT Name Code Purchase Order Inbound POI 850 ORDERS Purchase Order Inbound POCI 860 ORDCHG Change Purchase Order Outbound POAO 855 ORDRSP Acknowledgmen t Purchase Order Outbound POCAO 865 ORDRSP Acknowledgmen t Current Information The transaction file may change when enhancements are made such as additional data Transaction Summary Layouts A 9 added to the transaction Current transaction summaries can be found on Oracle Support s web site Current detail record layouts are reported via the Transaction Definition Layout Report and the Interface File Data Report Inbound Purchase Order POI 850 ORDERS POI 850 ORDERS Record Structure A single transaction has the data hierarchy and data looping as presented in the following diagram and table A 10 Oracle e Commerce Gateway Implementation Manual POI Inbound Purchase Order Structure Record Numbers Control Record 0010 Purchase Order Header 1000 1699 Credits at OM HEADER Level 1700 1740 Price Adjustments fat OM HEADER Level 1800 1850 Reservations at OM HEADER Level 1900 1910 Actions at OM HEADER Level 1950 1990 Item OM LINE Level 2000 2900 Part Numbers here Shipment OM LINE Level 3000 4900 Shipment Detail in this range Credits at OM LINE Level 5000 5900 Price Adjustments at OM LINE Level 6000 6900 Reservations at OM LINE Level 7000 7900 Actions at OM LINE Level
275. ctions have a three level structure 1 Order Header 2 Order Line 3 Order Shipment Schedules The Order Import open interface tables have a two level structure 1 Order Header 2 Order Line Combined Order Line and Order Shipment The e Commerce Gateway transaction accommodated the three level transactions so that the item data is written only once on Record 2000 also records 2010 2020 if needed followed by all the shipment schedules in records 3000 4900 The process will combine the item data to each set of its associated shipment data before writing the data to the Order Import LINE level table Though price is often set at the line level in a standard transaction it was necessary to have the price at the shipment level in this transaction to allow different prices at the Order Import LINE level hence all price data is on record 3000 The following table has a simple example of the X12 850 Purchase Order segments mapping to the e Commerce Gateway transaction Example of X12 850 Purchase Order and e Commerce Gateway Transaction Mapping X12 850 X12 850 e Commerce e Commerce Order Import Transaction Transaction Gateway POI Gateway POI Level Level Segment File File Data Transaction Content Record HEADER BEG 1000 Basic PO header HEADER Line Item 1 PO1 2000 Basic PO item 1 for first shipment Shipment SCH 3000 4000 Shipment Data LINE first for Item 1 with first Item 1 shipment shipment 1 6 10 Oracle e C
276. cuments Open Interface tables by the Oracle e Commerce Gateway import program The following is a list of the Purchasing Documents Open Interface required fields These fields are required for the Purchasing Documents Open Interface API to successfully process and move the data from the Purchasing Documents Open Interface tables into the Oracle Purchasing base application tables Required fields noted as derived or hardcoded do not require a value in the transaction on the transaction interface file since the values are determined by the Oracle e Commerce Gateway process PO_HEADERS_INTERFACE Table The following table lists the required fields for the POLHEADERS_INTERFACE table 6 100 Oracle e Commerce Gateway Implementation Manual Oracle Cond Oracle Hardcoded Record Position Applications e Commerce Derived Number Number Column Gateway Name for Column Required Name Fields VENDOR_D VENDOR_D 1000 10 OC_NUM OC_NUM EFFECTIVE_ Yes EFFECTIVE_ 1000 20 DATE DATE EXPIRATIO Yes EXPIRATIO 1000 30 N_DATE N_DATE ACTION ACTION_TY 1030 10 PE_CODE_I NT VENDOR_SI SHIP_FROM 1120 10 TE_CODE _ADDRESS_ CODE VENDOR_ID SHIP_FROM 1120 170 _CUSTOMER _ID VENDOR_SI SHIP_FROM 1120 180 TE_ID _ADDRESS_I D DOCUMENT _TYPE_COD E INTERFACE_ INTERFACE_ Derived HEADER_ID HEADER_ID ACTION_TYPE_CODE_INT This column is the catalog type indicator The valid values are as follows e ORIGINAL New catalog e REPLACE Replacement catalog Application
277. d as an order release mechanism containing such elements as resource authorizations period to date cumulative quantities and specific ship delivery patterns for requirements that have been represented in buckets such as weekly monthly or quarterly The Shipping Schedule transaction contains firm delivery information and is intended by the customer to refine requirements already presented in the planning schedule It facilitates the practice of Just In Time JIT manufacturing by providing the customer with a mechanism to issue precise shipping schedule requirements on a more frequent basis such as daily shipping schedules versus weekly planning schedules Trading Partner Link to Oracle e Commerce Gateway Customers and customer sites are defined in Oracle Accounts Receivable and Oracle Order Management Included in the definition is the EDI Location Code The EDI Location Code is a code that represents a customer s full detailed address Often the customer does not send the full address but just the EDI Location Code This is a critical data field to Oracle e Commerce Gateway The EDI Location Code is the link between a customer address in Oracle Applications and the trading partner site definition in Oracle e Commerce Gateway This enables Oracle e Commerce Gateway to access the detailed data about the customer address in the base Oracle Applications without maintaining the detail data in Oracle e Commerce Gateway To ensure that the tra
278. d in the EDI Translator 26 47 22 HEADER Movement Header 48 69 22 DETAIL Movement Detail 70 91 22 LOCATION Move Detail Location 92 95 4 Varies Record Number 96 97 2 Varies Record Layout 98 100 3 Varies Record Layout Qualifier The following table shows the Common Key positions 1 100 for the records of the Outbound Movement Statistics transaction Transaction Summary Layouts A 5 Transaction specific Data in the Common Key of the MVSTO transaction per record Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner Header Detail Locati Number Layout Layout on Qualifie r 1 Control TP_CD HEADE 0010 CT CTL Record R 2 Trading TP_CD HEADE 0020 Al TH1 Partner R Hdr Flexfiel ds 1 4 3 Trading TP_CD HEADE 0030 A2 TH2 Partner R Hdr Flexfiel ds 4 9 4 Trading TP_CD HEADE 0040 A2 TH3 Partner R Hdr Flexfiel ds 10 14 5 Trading TP_CD HEADE 0050 A2 TH4 Partner R Hdr Flexfiel d15 6 Movem TP_CD HEADE 1000 RP RPT ent R Type Status Period 7 Legal TP_CD HEADE 1010 AX LE1 Entity R Address A 6 Oracle e Commerce Gateway Implementation Manual Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner Header Detail Locati Number Layout Layout on Qualifie r 8 Total TP_CD HEADE 1020 RP TOT Units R Records amp Weight 9 Nature TP_CD HEADE DETAIL 2000 MV MOV of R Transact ion Mov ement 10 Post TP_CD HEADE DETAIL 2010 MV MV1 Area R Zone Code 11 Currence TP_CD HEADE DETAIL 2020 MV
279. d showing in key 1 will access those records The default document standard which is used for this code conversion value table is assigned to a Trading Partner s transaction via the Detail tab in the Define Trading Partner window Remember that the Document Standard Code applies to the entire transaction for the Trading Partner It does not change per data element Since keys 1 2 are entered in the code conversion table these entries apply only to the entities whose values are entered in keys 1 2 Since keys 1 5 are blank and the 3 table entries did not apply all code conversion enabled data elements will find the 4 table entries given the external codes as part of the key If code conversion is enabled and a table entry is not found the external 1 code is written to the application open interface tables They may fail data validation when the application open interface is executed if not entered properly in the code conversion tables The data should be visible for the applications regular error handling procedures Understanding Code Conversion for Inbound and Outbound Transactions using Code Conversion 10 15 Direction BOTH Table entries that are given the direction BOTH are accessed during code conversion for both inbound and outbound transactions All the rules specified above for inbound and outbound transactions apply to the entries with direction BOTH You should be able to enter the direction BOTH for most table entrie
280. d to TP Referen ce Remit to Address Code Remit to TP Referen ce Ship From Codes TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD MEMO MEMO MEMO MEMO MEMO MEMO MEMO MEMO 1110 1115 1200 1210 1215 1300 1315 1400 CM RF AD CM RF AD RF SF ST1 ST1 SO1 SO1 SO1 RE1 RE1 SF1 A 176 Oracle e Commerce Gateway Implementation Manual Data Trading Partner Ref 1 MEMO ITEM Ref 3 Record TAX Number Record Record Layout Layout Qualifie r 25 26 27 28 29 30 31 32 Basic Invoice Header Data Memo Amount Data Memo Misc Data Shipme nt Data Currenc y Data Shippin g Data Miscella neous Data Paymen t Terms Data Sales Represe ntative Comme nts Transact ion Flexfiel ds 1 4 TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD MEMO MEMO MEMO MEMO MEMO MEMO MEMO MEMO 2000 2010 2020 2030 2040 2050 2060 3000 IV IV1 IV IV2 IV IV3 IV IV4 IV IV5 IV IV6 IV IV7 Al TH1 Transaction Summary Layouts A 177 Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner MEMO ITEM TAX Number Layout Layout Qualifie r 33 Transact TP_CD MEMO 3010 A2 TH2 ion Flexfiel ds 5 9 34 Transact TP_CD MEMO 3020 A2 IH3 ion Flexfiel ds 10 14 35 Transact TP_CD MEMO 30
281. dcoded Record Position Applications e Commerce Derived Number Number Column Gateway Name for Column Required Name Fields PO_NUMBE Yes PO_NUMBE 1000 30 R R INVOICE_A INVOICE_A 1000 40 MOUNT MOUNT TERMS_NA Yes TERMS_NA 1000 70 ME ME_INT INVOICE_C Yes INVOICE_C 1010 10 URRENCY_C URRENCY_C ODE ODE EXCHANGE Yes EXCHANGE 1010 30 _RATE _RATE EXCHANGE Yes EXCHANGE 1010 40 _DATE _DATE INVOICE_ID Derived SOURCE H EDI_GATE WAY EXCHANGE Yes _RATE_TYPE EXCHANGE_RATE_TYPE is not mapped or referenced by the Oracle e Commerce Gateway because the data is not required by the transaction INVOICE_AMOUNT This column represents the total amount for the invoice calculated as the sum of the invoice line amounts INVOICE_CURRENCY_CODE EXCHANGE_DATE EXCHANGE_RATE Currency code exchange date and exchange rate are required for foreign currency invoices where the currency code is different from the functional currency The exchange date identifies the exchange rate to be used to compute the invoice amount 6 84 Oracle e Commerce Gateway Implementation Manual INVOICE_NUM This column represents the invoice number for the supplier invoice being imported into Oracle Payables The number must be unique for the supplier as the Payables Open Interface Import program will reject duplicate invoice numbers PO_NUMBER This column represents the purchase order to match the invoice to Purchase order numbers may be entered at the header or
282. de For inbound transactions this field must have one of the EDI Location Codes for the Trading Partner sending the transaction The Trading Partner site represented by that EDI Location code must be fully defined in the Oracle e Commerce Gateway and base Oracle Application Note For inbound transactions the only time that a Trading Partner must be fully defined in the Oracle e Commerce Gateway and the base Oracle Application is when its EDI Location code is used in the Control Record A fully defined Trading Partner means the following e Inthe Trading Partner Group window the Trading Partner group and Trading Partner name are defined e Inthe Trading Partner Details tab the appropriate transaction and transaction types are enabled the Test Production flag is set to the correct code the Translator Code is accurately entered and the EDI box is enabled e Inthe Trading Partner Assignment tab the Trading Partner is linked to the appropriate address site in the base Oracle Application e In the base Oracle Application the Trading Partner and Trading Partner site is defined and the EDI Location Code for the site is entered The combination of the Translator Code and the EDI Location Code on the Control 9 10 Oracle e Commerce Gateway Implementation Manual Record 0010 must lead to a single Trading Partner definition in the Oracle e Commerce Gateway The Oracle e Commerce Gateway uses the EDI Location Code in the Control Reco
283. der E Flexfiel ds 1 5 67 TP TP_CD INVOIC LINE 5150 A2 HT2 Header E Flexfiel ds 6 10 A 198 Oracle e Commerce Gateway Implementation Manual Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner INVOIC ITEM TAX Number Layout Layout E Qualifie r 68 TP TP_CD INVOIC LINE 5160 A2 HT3 Header E Flexfiel ds 11 15 69 TP Line TP_CD INVOIC LINE 5170 A2 LT1 Flexfiel E ds 1 5 70 TP Line TP_CD INVOIC LINE 5180 A2 LT2 Flexfiel E ds 6 10 71 TP Line TP_CD INVOIC LINE 5190 A2 LT3 Flexfiel E ds 11 15 72 Industr TP_CD INVOIC LINE 5200 A2 IA1 y E Flexfiel ds 1 5 73 Industr TP_CD INVOIC LINE 5210 A2 IA2 y E Flexfiel ds 6 10 74 Industr TP_CD INVOIC LINE 5220 A2 IA3 y E Flexfiel ds 11 15 75 Extensio TP_CD INVOIC LINE 5900 Custo n E m Tables Item Data 76 Line TP_CD INVOIC LINE TAX 6000 TX TX1 Tax E Data Transaction Summary Layouts A 199 Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner INVOIC ITEM TAX Number Layout Layout E Qualifie r 77 Line TP_CD INVOIC_ LINE TAX 6005 TX TX2 Tax E Type 78 Line TP_CD INVOIC LINE TAX 6010 TX TX3 Tax E Classific ation 79 Line TP_CD INVOIC LINE TAX 6020 TX TX4 Tax E Code 80 VAT TP_CD INVOIC LINE TAX 6025 TX TX5 Tax E Data 81 Line TP_CD INVOIC LINE TAX 6030 A1 TX1 Tax E Flexfiel ds 1 4 82 Line TP_CD INVOIC LINE TAX 6040 A2 TX2 Tax E Flexfiel ds 5 9 83 Line TP_CD INVOIC LINE TAX 6050 A2 TX3 Tax E Flexfiel ds 10 14 84 Line TP_CD INVOIC LINE TAX
284. des are unique If the Direction is BOTH the entire search key including the internal and external codes are unique The Define Code Conversion Values window does not allow you to create duplicate table entries even across entries using the other directions IN OUT and BOTH You may need to remove an entry for another direction in order to accommodate a table entry that uses direction BOTH Transaction direction is discussed further after we understand how the code conversion value table is read in general for inbound and outbound transactions as illustrated in the following two tables Full Search Key for Outbound Transaction Goal Create a key including the known internal code from the Oracle application to find all the external codes so they may be written to the transaction interface file Keys 1 5 are optional Keys are used when the table entry does not apply to all Trading Partners The following table illustrates a full search key search performed for an outbound transaction The columns Category Direction Keys 1 thru 5 and Internal Code represent the entire search key The columns External Code 1 through External Code 5 represent data retrieved for the transaction interface file Full Search Key for Outbound Transaction Categor Directio Keys1 Internal Externa Externa Externa Externa Externa y n thru 5 Code Code Code Code Code Code 1 2 3 4 5 UOM OUT Each EA PC UOM OUT Box BX BX Full Search Key
285. ding Partner s perspective Internal codes in contrast are found in Oracle Applications Internal Code A code defined in the Oracle Applications regardless if it is an inbound or outbound transaction External codes in contrast are found in the transaction interface file Key n 1 5 Value A value contained in a key column also 1 5 that when concatenated with other keys comprise a search key Keys are concatenated beginning with 1 and continuing through all defined keys up to a maximum of 5 during the code conversion table search Key n 1 5 Column Table or view columns that contain values used as part of the search key Search Key Accessing the code conversion table includes a concatenated search key consisting of the 1 5 user defined search keys If all five search keys have data then the table entries are very restricted to whom the codes apply Data in Key 1 is less restricted on access and may apply to several Trading Partners If all five search keys are blank the table entries will be read for all Trading Partners transactions for that code category The maximum number of search keys that you enabled in the Assign Code Conversion Categories window are concatenated for the first search If a code conversion table entry is not found the highest order key is removed then a subsequent search of the code conversion table is made Removing the highest order search key of the remaining search keys and accessing the table wit
286. ding TP_CD SCHR 1610 A2 TH2 Partner EF Header Flexfiel ds 14 Trading TP_CD SCHR 1620 A2 TH3 Partner EF Header Flexfiel ds 15 Trading TP_CD SCHR 1630 A2 TH4 Partner EF Header Flexfiel ds Transaction Summary Layouts A 223 Data Trading Ref 1 Ref 2 Record Record Record Partner SCH_R SEQ Number Layout Layout EF Qualifie r 16 ShipTo TP_CD SCH_R 1700 AD STH Address EF and Code 17 Bill To TP_CD SCHR 1710 AD BTH Address EF and Code 18 Interme TP_CD SCHR 1720 AD ICH diate EF Ship To Address and Code 19 Ship TP_CD SCHR 1730 AD SFH From EF Address and Code 20 Other TP_CD SCH_R 1740 MN MNH Name EF Codes and Values 21 Item TP_CD SCHR SEQ 2000 SC DT Data EF Date and Quantit y Data 22 Unitof TP_CD SCHR SEQ 2040 UM UOM Measur EF ement A 224 Oracle e Commerce Gateway Implementation Manual Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner SCH_R SEQ SEQ_S Number Layout Layout EF UBLINE Qualifie r 23 Item TP_CD SCH_R SEQ 2200 RF DTM Referen EF ce 24 Ship To TP_CD SCH_R SEQ 3000 AD STI Address EF and Code 25 Bill To TP_CD SCH_R SEQ 3010 AD BTI Address EF and Code 26 Interme TP_CD SCHR SEQ 3020 AD ICI diate EF Ship To Address and Code 27 Ship TP_CD SCH_R SEQ 3030 AD SFI From EF Address and Code 28 Custom TP_CD SCH_R SEQ 3100 i IT1 er EF Referen ce Data 29 More TP_CD SCH_R SEQ 3110 I2 IT2 Custom EF er Referen ce Data Transaction Summary Layouts A 225 Da
287. ding partner link between Oracle e Commerce Gateway and Oracle Applications is set up properly verify that the customer address and the EDI Location Code in Oracle Applications is the correct customer address selected for the Trading Partner definition in Oracle e Commerce Gateway The selected customer address and the EDI Location Code defined in Oracle Applications are displayed in the Assignment tab of the Define Trading Partners window If the data is not correct you must make the appropriate changes for the transaction to be imported for the correct trading partner This could involve either altering the customer address in the base Oracle Application or assigning a different customer address to that EDI Location Code in Oracle e Commerce Gateway Application Transaction Detail 6 135 Refer to the Trading Partner chapter for recommendations on selecting the correct trading partner EDI Location Code for the control record 0010 for the transaction Note On inbound EDI Demand Transactions the customer also sends a Supplier Code The Supplier Code identifies the Supplier to the customer The Supplier Codes are defined in the Release Management Processing Rules Window They are not defined in the e Commerce Gateway to be used by this transaction process Refer to the Release Management Implementation Manual and the Release Management User s Guide for additional information on setting up the Supplier Code Oracle e Commerce Gateway Required Fiel
288. dits at OM LINE Level 5000 5900 Price Adjustments fat OM LINE Level 6000 6900 Reservations at OM LINE Level 7000 7900 Actions fat OM LINE Level 8000 8900 Lot Serial at OM LINE Level 9000 9900 Shipment OM LINE Level 3000 4900 Credits at OM LINE Level 5000 5900 Price Adjustments at OM LINE Level 6000 6900 Reservations at OM LINE Level 7000 7900 Actions fat OM LINE Level 8000 8900 Lot Serial at OM LINE Level 9000 9900 An Outbound Purchase Order transaction contains a single Control Record and Purchase Order Header Record The header record may have multiple Header Attachment Detail Records and Line Records The Line Record may have multiple Line Attachment Header Records Master Item Attachment Header Records and Inventory Item Attachment Header Records The Line Attachment Header Record may have multiple Line Attachment Detail Records The Master Item Attachment Header Record may have multiple Master Item Attachment Detail Records The Inventory Attachment Header Record may have multiple Inventory Attachment Detail Records and multiple Transaction Summary Layouts A 139 Shipment Records The Shipment Records may have multiple Shipment Attachment Header Records and Distributions Records The Shipment Attachment Header Record may have multiple Shipment Attachment Detail Records The following table shows the content and occurrences of the records comprising the Outbound
289. dor Site Flexfiel ds 5 9 Vendor Site Flexfiel ds 10 14 Vendor Site Flexfiel d5 TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD PS PS PS PS PS PS PS PS PS 1530 1600 1610 1620 1630 1650 1660 1670 1680 A2 Al A2 A2 A2 Al A2 A2 A2 SH4 VNI1 VN2 VN3 VN4 VS1 VS2 VS3 VS4 Transaction Summary Layouts A 237 Data Trading Partner Ref 1 PS Ref 2 ITEM Ref 3 SCHE DULE Record Number Record Layout Record Layout Qualifie r 26 27 28 29 30 31 32 Shippin 8 Organiz ation Flexfiel ds 1 4 Shippin 8 Organiz ation Flexfiel ds 5 9 Shippin 8 Organiz ation Flexfiel ds 10 14 Shippin 8 Organiz ation Flexfiel d15 Ship To Options Flexfiel ds 1 4 Ship To Options Flexfiel ds 5 9 Ship To Options Flexfiel ds 10 14 TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD PS PS PS PS PS PS PS 1700 1710 1720 1730 1750 1760 1770 A1 A2 A2 A2 A1 A2 A2 ST1 ST2 ST3 ST4 OP1 OP2 OP3 A 238 Oracle e Commerce Gateway Implementation Manual Data Trading Partner Ref 1 PS Ref 2 ITEM Ref 3 Record SCHE Number DULE Record Layout Record Layout Qualifie r 33 34 35 36 37 38 39 40 41 Ship To Op
290. ds The following table lists the Oracle ee Commerce Gateway required fields These fields are required to authenticate the trading partner and transaction If the required data is not provided in the transaction the Oracle e Commerce Gateway import process fails the transaction and an exception message will display in the View Staged Documents window If the trading partner is valid and the transaction is enabled the import process proceeds to validate the transaction using the user defined column rules If no process or column rule exceptions are detected the Oracle e Commerce Gateway import program will write the transaction to the Release Management Interface tables to be processed by the Release Management Demand Processor Oracle e Commerce Gateway Required Fields Oracle e Commerce Record Number Position Number Note Gateway Column Name for Required Fields TEST_INDICATOR 0010 20 T or P DOCUMENT_CODE 0010 60 Schedule Reference number TP_TRANSLATOR_C 0010 70 Translator identifier ODE for this trading partner TP_LOCATION_CO 0010 80 The EDI Location DE Code 6 136 Oracle e Commerce Gateway Implementation Manual Oracle e Commerce Gateway Column Name for Required Fields Record Number Position Number Note TRANSACTION_DA TE EDI_CONTROL_NU M_1 EDI_CONTROL_NU M_2 EDI_CONTROL_NU M3 RLM_SCHEDULE_T YPE_INT SCHEDULE_PURPO SE_INT 0010 0010 0010 0010 1000 1000 120 160
291. e Outbound Purchase Order Change transaction Transaction Summary Layouts A 33 Record occurrences within the POCI transaction Records CONTENT OCCURRENCES 0010 1000 1699 1700 1740 1800 1850 1900 1910 1950 1990 2000 2900 3000 4900 5000 5900 6000 6900 7000 7900 8000 8900 9000 9900 Control Record PO Header Records Credits Price Adjustments Reservations Actions PO Line PO Line Shipment Credits Price Adjustments Lot Serial Reservations Actions Only one record occurrence per transaction Only one record occurrence per transaction One set of records per header One set of records per header One set of records per header One set of records per header One set of records per item within the PO header One set of records per shipment within the PO Line One set of records per shipment within the PO Line One set of records per shipment within the PO Line One set of records per shipment within the PO Line One set of records per shipment within the PO Line One set of records per shipment within the PO Line The following table is as a summary list of the records that comprise the Outbound Purchase Order Change transaction The table shows the functional data grouping of records the data level the record numbers and relevant notes about the data grouping A 34 Oracle e Commerce Gateway Implementation Manual POCI Transaction Record Sum
292. e or order being imported should be imported in a Closed state The Order Import process sets on the error flag whenever an error is encountered during the validation process The ready flag indicates that the record will be processed in the Order Import Process N A N or Null N or Null N or Null Y or Null Y N Null N Null N Null N Null Y N Null Application Transaction Detail 6 25 Flag Description Default Possible Values Rejected Rejected orders or N or Null rejected order lines are DELETED during the next execution of the Order Import program Validate Mode Parameter in Concurrent Manager N Null There is a validate mode parameter in Concurrent Manager for executing Order Import This parameter tells the process to only validate the record and not to process valid records any further Base Order Management tables will not have records inserted updated or deleted READY_FLAG Only Validate Parameter N Y N N Y or NULL Y Y or NULL N Processing Record is not processed Record is not processed Process to Validate Only Process to Insert Update Delete in Base Table Order Import Open Interface Data The Order Management Order Import Open Interface is used by the Inbound Purchase Order transaction This validates the incoming data entered into the Order Management Open Interface tables by the Oracle e Commerce Gateway import program or any other
293. e Commerce Gateway Implementation Manual DULE Record 0010 1000 Record Record Number Layout Layout Qualifie r CT CTL HD HDR NT HDR 1010 Data Trading Ref 1 Ref 2 Ref Record Record Record Partner SCH_R ITEM SCHE Number Layout Layout EF DULE Qualifie r 4 Schedul TP_CD SCH_R 1020 AD SIH e Issuer EF Address Code 5 Header TP_CD SCHR 1030 CO HDR Miscella EF neous Contact s 6 Header TP_CD SCH_R 1040 RF HDR Miscella EF neous Referen ces 7 Schedul TP_CD SCH_R 1100 A1 SH1 e EF Header Flexfiel ds Cont ext 8 Schedul TP_CD SCH_R 1110 11 A2 SH2 SH e EF 30 4 Header Flexfiel ds 9 Trading TP_CD SCH_R 1200 Al TH1 Partner EF Flexfiel ds Cont ext 10 Trading TP_CD SCH_R 1210 12 A2 TH2 TH Partner EF 30 4 Flexfiel ds Transaction Summary Layouts A 209 Data Trading Ref 1 Ref 2 Ref Record Record Record Partner SCH_R ITEM SCHE Number Layout Layout EF DULE Qualifie r 11 Ship To TP_CD SCH_R 1300 AD STH Address EF Code 12 Bill To TP_CD SCH_R 1310 AD BTH Address EF Code 13 Interme TP_CD SCH_R 1320 AD ICH diate EF Ship To Address Code 14 Supplier TP_CD SCH_R 1330 AD SFH Ship EF From Address Code 15 Miscella TP_CD SCH_R 1340 MN MNH neous EF Name Codes and Values 16 Extensio 1900 Custom Custom n Tables Schedul e Level 17 Basic TP_CD SCH_R ITEM 2000 Il IT1 Item EF Data 18 Product TP_CD SCH_R ITEM 2010 12 IT2 Descript EF ion Data A 210 Oracle e Commerce Gateway Implementatio
294. e Gateway predetermines which Trading Partner site in an outbound transaction is reviewed to determine if the transaction should be extracted A Trading Partner must be fully defined in the Oracle e Commerce Gateway if that site s outbound transactions are to be extracted The following table shows sample Primary Address Site Types on the Control Record 0010 for Outbound Transactions Examples of Primary Address Site Types on the Control Record 0010 for Outbound Transaction Transaction Transaction ASC EDIFACT Site Address Code Type for the X12 Control Record 0010 Application ADVO 824 APERAK Supplier Site Advice for 810 Invoice INO 810 INVOIC Customer Bill To Site Movement MVSTO CUSDEC Legal Entity Statistics Trading Partner 9 13 Transaction Transaction ASC EDIFACT Site Address Code Type for the X12 Control Record 0010 Payment Remitt PYO 820 REMADV Paying Bank ance Advice Branch PAYORD PAYE XT Planning SPSO 830 DELFOR Supplier Site Schedule Purchase Order POCO 860 ORDCHG Supplier Site Change Purchase Orders POO 850 ORDERS Supplier Site Ship ASNO 856 DESADV Customer Ship Notice Manifest to Site Shipping SSSO 862 DELJIT Supplier Site Schedule Note The Trading Partner site must be fully defined as a Trading Partner in the Oracle e Commerce Gateway and the base Oracle Application to have the Trading Partner site s transaction extracted Like the inbound transaction a fully defined Trading Partner means t
295. e Oracle Applications file system and database Outlines the actions performed by these utilities such as monitoring parallel processes generating Applications files and maintaining Applications database entities Part of Maintaining Oracle Applications a 3 book set that also includes Oracle Applications Patching Procedures and Oracle Applications Maintenance Procedures Oracle Applications Maintenance Procedures This guide describes how to use AD maintenance utilities to complete tasks such as compiling invalid objects managing parallel processing jobs and maintaining snapshot information Part of Maintaining Oracle Applications a 3 book set that also includes Oracle Applications Patching Procedures and Oracle Applications Maintenance Utilities Oracle Applications System Administrator s Guide Documentation Set This documentation set provides planning and reference information for the Oracle Applications System Administrator Oracle Applications System Administrator s Guide Configuration contains information on system configuration steps including defining concurrent programs and managers enabling Oracle Applications Manager features and setting up printers and online help Oracle Applications System Administrator s Guide Maintenance provides information for frequent tasks such as monitoring your system with Oracle Applications Manager managing concurrent managers and reports using diagnostic utilities managing profile options
296. e Support s web site Current detail record layouts are reported via the Transaction Definition Layout Report and the Interface File Data Report Outbound Planning Schedule SPSO 830 DELFOR The following table shows the content and occurrences of the records comprising the Outbound Planning Schedule transaction Record Occurrences Within the SPSO Transaction Records Content Occurrences 0010 Control Record Only one record occurrence per transaction 0020 0070 Gateway Flexfields One set of records per transaction 1000 1900 Header Records Only one record occurrence per transaction A 230 Oracle e Commerce Gateway Implementation Manual Records Content Occurrences 2000 2900 Item Records One set of records per item within the Planning Schedule header 4000 4900 Authorization Forecast One records per forecast Schedule schedule authorization or receipt data per item The following table is a summary list of the records that comprise the Outbound Planning Schedule transaction The table shows the functional data grouping of records the data level the record numbers and relevant notes about the data grouping SPSO Transaction Record Summary Data Data Level Record Number Note 1 Control Record HEADER 0010 2 Trading Partner HEADER 0020 0050 Flexfields Header Flexfields 3 Trading Partner HEADER 0060 0070 Flexfields Detail Flexfields 4 Basic Planning HEADER 1000 Schedule Header 5 Supplier HEADER 10
297. e code conversion windows Code Conversion 10 17 The following table shows examples of Document Standards used in the search key Examples of Document Standard as Part of the Search Key note Category Direction Key 1 Key 2 Internal External External Code Code 1 Code 2 1 UOM OUT Each EA PC 2 UOM BOTH X12 Each EA 2 UOM BOTH X12 Piece PC 2 UOM BOTH EDIFACT Each EA 2 UOM BOTH EDIFACT Piece PC Assume that you entered X12 codes in external code 1 and EDIFACT in external code 2 This method allows you to enter just one table entry to have the internal code set to Each then return the external codes EA and PC for outbound transactions This entry cannot be used for inbound transactions since only the X12 or only the EDIFACT code is in the transaction or message but not both codes in a given transaction You need a separate set up for the inbound transactions Enter separate table entries by document standard if it is an alternate method for 1 Since key 1 is the document standard only the table entries with key 1 set to one of the standards X12 EDIFACT etc are retrieved for a given Trading Partner if they are assigned a document standard for that transaction If a Trading Partner s transaction is not given a document standard then the entry 1 will be read for the outbound transactions Planning the Use of Direction in Code Conversion Review your code conversion needs and develop a plan for you
298. e database They can determine feasibility of changes how to make those changes without disturbing the existing routines and how to make them in such a way that the changes can be easily adapted when patches are installed This also applies to inbound transactions when additional routines are needed to make the data put into the interface tables by the Oracle e Commerce Gateway 2 2 Oracle e Commerce Gateway Implementation Manual compatible with the import process and or the customer s needs A basic knowledge of the table structure of the relevant Oracle Applications and Oracle e Commerce Gateway is a big advantage if any custom work is contemplated Understand Oracle Applications and Application Open Interfaces Know the Transient Data in the Oracle Application The Oracle Applications produce data as needed by the application They may not retain data in the tables that is calculated because the numbers used to produce the calculation number of units and discount percentage in the example below may change each time the application is run The data is printed on a permanent paper document Because EDI is a substitute for the paper document this data must be computed and stored in the outgoing file The implementer must allow for this by defining a field in the EDI extension table and the code to populate it Know the Functionality of the Oracle Application Verify that the Oracle Application performs the function expected by the transaction
299. e either altering the supplier supplier site in the base Oracle Application or assigning a different supplier supplier site to that EDI Location Code in Oracle e Commerce Gateway Refer to the Trading Partner chapter for recommendations on selecting the correct trading partner EDI Location Code for the control record 0010 for the transaction in the transaction interface file Oracle e Commerce Gateway Required Fields The following is a list of the Oracle e Commerce Gateway required fields These fields are required to authenticate the trading partner and transaction If the required data is not provided in the transaction the Oracle e Commerce Gateway import process fails the transaction Then an exception message is displayed in the View Staged Documents window If the trading partner is valid and the transaction is enabled the import process proceeds to validate the transaction using the user defined column rules If no process or column rule exceptions are detected the Oracle e Commerce Gateway import program will write the transaction to the Payables Open Interface tables to be processed by the Payables Open Interface API Oracle e Commerce Record Number Position Number Note Gateway Column Name for Required Fields TEST_INDICATOR 0010 20 T or P TP_DOCUMENT_ID 0010 30 ASNT or SBNI Application Transaction Detail 6 73 Oracle e Commerce Record Number Position Number Note Gateway Column Name for Required
300. e extracted for the correct trading partner This could involve either altering the customer customer site in the base Oracle Application or assigning a different customer customer site to that EDI Location Code in Oracle e Commerce Gateway Please note that if the trading partner is associated with multiple operating units then the transaction to be extracted is for a specified operating unit only linked to your responsibility To extract all the data for multiple operating units you still need to execute the program one by one by specifying different operating unit each time when you run the program See the Outbound Transactions chapter in the Oracle e Commerce Gateway User s Guide for details Refer to the Trading Partner chapter for recommendations on selecting the correct trading partner EDI Location Code for the control record 0010 for the transaction in the transaction interface file Application Transaction Detail 6 131 Two Methods of Sending Credit Memos Debit Memos Extract Criteria The 810 INVOIC transaction supports invoices credit memos and debit memos In addition you can use the 812 CREADV DEBADV transaction to send just the credit memos and debit memos The method you chose is dependent on your agreement with your supplier Any credit memo debit memo extracted using the 812 CREADV DEBADYV transaction will not be eligible for extraction by the 810 INVOIC transaction The outbound credit memo debit memo transaction is cont
301. e following table shows the Common Key positions 1 100 for the Outbound Planning Schedule transaction The table shows the position length code and content of the Common Key elements Transaction Summary Layouts A 233 Transaction specific Data in the SPSO Transaction Common Key Position Length Code Content 1 25 25 TP_CD Trading Partner Code as defined in the EDI Translator 26 47 22 PS Planning Schedule number 48 69 22 ITEM Planning Schedule line number 70 91 22 SCHEDULE Schedule Bucket Number 92 95 4 varies Record Number 96 97 2 varies Record Layout 98 100 3 varies Record Layout Qualifier The following table shows the Common Key positions 1 100 for the records of the Outbound Planning Schedule transaction Transaction specific Data in the Common Key of the SPSO Transaction Per Record Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner PS ITEM SCHE Number Layout Layout DULE Qualifie r 1 Control TP_CD PS 0010 CT CTL Record 2 Trading TP_CD PS 0020 A1 TH1 A 234 Oracle e Commerce Gateway Implementation Manual Partner Header Flexfiel ds Data Trading Partner Ref1 Ref2 Ref3 PS ITEM SCHE DULE Record Number Record Layout Record Layout Qualifie r Trading Partner Header Flexfiel ds Trading Partner Header Flexfiel ds Trading Partner Header Flexfiel ds Trading Partner Detail Flexfiel ds Trading Partner Detail F
302. e is used by the Inbound Invoice transaction It is used to validate the incoming data entered into the Payables Open Interface tables by the Oracle e Commerce Gateway import program The following is a list of the Payables Open Interface required fields These fields are required for the Payables Open Interface Import program to successfully process and move the data from the Payables Open Interface tables into the Oracle Payables base application tables Required fields noted as derived or hardcoded do not require a value in the transaction on the transaction interface file since the values are determined by the Oracle e Commerce Gateway process Refer to the Payables Open Interface Appendix section Oracle Payables User s Guide for details on derived defaulted and conditional fields see Cond items in the following tables AP_INVOICES_INTERFACE Table The table below lists the required fields for the AP_INVOICES_INTERFACE table Oracle Cond Oracle Hardcoded Record Position Applications e Commerce Derived Number Number Column Gateway Name for Column Required Name Fields INVOICE_N INVOICE_N 1000 10 UM UM PO NUMBE Yes PO_NUMBE 1000 30 R R INVOICE_A INVOICE_A 1000 40 MOUNT MOUNT 6 76 Oracle e Commerce Gateway Implementation Manual Oracle Cond Oracle Hardcoded Record Position Applications e Commerce Derived Number Number Column Gateway Name for Column Required Name Fields TERMS_NA Yes TERMS_NA 1000
303. e names of Forecasts to which inbound Release Management forecast demand can be assigned e If set to none forecast data will not be imported into Planning 2 RLM CUM Management Enabled Determines whether or not CUM Management is enabled at the Site level To use the CUM Management features of Oracle Release Management this must be set to Yes 3 RLM Print CUM Data on Shipping Documents Determines whether or not CUM Data should be printed on shipping documents 4 RLM Debug Mode Determines if debug file is written for running the Demand Processor Valid Values 0 Highest debug level Null No debug file is generated The default value is Null 5 RLM Workflow Enabled Determines whether or not the Demand Processor is enabled to run in workflow mode 6 ECE SPSI Enabled Determines whether or not inbound planning schedule transaction is enabled 7 ECE SSSI Enabled Determines whether or not inbound shipping schedule transaction is enabled 8 ECE PSQI Enabled Determines whether or not inbound sequenced shipping schedule transaction is enabled Application Transaction Detail 6 167 9 Release Management Processing Rules e There are five categories of Processing Rules attributes Demand Management Demand Fences Order Management CUM Management General e These five categories are defined for each Ship From Ship To business entity for which Release Management will process the demand e If terms are no
304. e on Oracle MetaLink and www oracle com It contains the most current Documentation Library plus all documents revised or released recently Send your comments to us using the electronic mail address appsdoc_us oracle com Please give your name address electronic mail address and telephone number optional If you need assistance with Oracle software then please contact your support representative or Oracle Support Services If you require training or instruction in using Oracle software then please contact your Oracle local office and inquire about our Oracle University offerings A list of Oracle offices is available on our Web site at www 0oracle com Preface Intended Audience Welcome to Release 12 of the Oracle e Commerce Gateway Implementation Manual This guide assumes you have a working knowledge of the following e The principles and customary practices of your business area e Oracle e Commerce Gateway If you have never used Oracle e Commerce Gateway Oracle suggests you attend training classes available through Oracle University e The Oracle Applications graphical user interface To learn more about the Oracle Applications graphical user interface read the Oracle Applications User s Guide See Related Information Sources on page xiii for more Oracle Applications product information TTY Access to Oracle Support Services Oracle provides dedicated Text Telephone TTY access to Oracle Support Services within the
305. e quite different to satisfy their particular needs In the Oracle e Commerce Gateway Trading Partner data is used to e Link to a specified operating unit e Link a particular address location in Oracle Applications to the Trading Partner definition in the Oracle e Commerce Gateway e Provide a means of telling the EDI Translator which Trading Partner data maps and mailbox are to be used outbound transactions e Enable specific transactions for Trading Partners e Determine if the EDI status of a Trading Partner is Test or Production This section provides important detail about Trading Partner definitions EDI Location Codes Translator Codes their importance on the transaction interface files and multi org considerations The Trading Partner windows along with some recommendations are at the end of this chapter for your reference Trading Partner Group The Oracle e Commerce Gateway allows the Trading Partners to be listed in convenient groups to facilitate access to individual organization records For example a car manufacturer may group its Trading Partners by seat suppliers tire manufacturers windshield companies engine parts suppliers or each individual supplier A publisher may group Trading Partners by printer major outlet distributor exporter bank and their individual customers The group may depend on whether the Trading Partners are customers or suppliers Additionally to support multiple organizations Oracle e C
306. e report scripts can be found the Release 12 Upgrade manual Seed Data Reconciliation Seed data is generally defined as any data delivered with a standard installation of Oracle Applications This includes menu definitions concurrent manager definitions list of values etc In this chapter the definition of seed data is limited to the data used for e Definition of transaction record layouts e Assignment of code categories to a transaction record layout e Definition of process rules associated with a transaction e Definition of column rules associated with a transaction Whenever a transaction specific patch is applied there may be changes or additions to the transaction record layout Code category assignments column rules and process rules are closely linked to the transaction record layout so these definitions may also be impacted by a change to the transaction record layout The Release 12 Seed Data Reconciliation process allows you to reapply the preexisting transaction record layout if a patch updated the transaction record layout or accept the new transaction record layout Retaining the preexisting transaction record layout gives you a record layout that minimizes or eliminates transaction data map changes for any process that uses your transaction such as the Translator In addition to reconciling transaction record layouts this process also performs reconciliation on the code conversion assignment column rules and process
307. e rule e Request that Oracle e Commerce Gateway ignore the validation by enabling the IGNORE flag via the View Staged Documents window e Delete the transaction using the View Staged Documents window Once you processed the warning exception you can resubmit the transaction using the View Staged Documents window for processing into the Application Open Interface tables When the import process of loading data into the Application Open Interface tables completes successfully you must resubmit the request to execute the Application Open Interface process so the data can be imported into the Oracle Applications base tables Oracle e Commerce Gateway s exception handler is designed to validate the entire inbound file and report all exceptions to you so that you can make the necessary corrections all at once However if there are errors at multiple levels of the transaction Oracle e Commerce Gateway s exception handler proceeds as far as it can and then continue processing only after the necessary corrections are made and the transaction is resubmitted for processing In the best case scenario all exceptions are reported the first time In the worse case scenario this is an iterative process requiring your attention at each iteration until all exceptions are resolved Common Setup Errors The Assign Process Rules and Assign Column Rules window prevents you from defining invalid or incomplete validation rules However if you define an incorrect
308. e search key is unique It does not matter what the internal codes are since they are not part of the entire search key Items 2 If a document standard is entered for the Trading Partner in the Trading Partner Detail tab and the a data element is assigned the column DOCUMENT_STANDARD in the Code Conversion Assignment tab these table entries will be accessed in the code conversion process before the entries 1 are accessed by all Trading Partners Planning for Direction BOTH for Inbound and Outbound Transactions The following table illustrates an example in which all entries are not feasible for the direction BOTH 10 20 Oracle e Commerce Gateway Implementation Manual Example of Planning for Direction BOTH for Inbound and Outbound Transactions Category Direction Key 1 Key 2 External External Internal Code 1 Code 2 Part Key Part Key Part Key for for for Inbound Inbound Outboun d 1 UOM BOTH EA Each 2 UOM BOTH PC Each 3 UOM BOTH X12 EA Each 4 UOM BOTH X12 PC Each 5 UOM BOTH EDIFACT EA Each 6 UOM BOTH EDIFACT PC Each All Entries Not Feasible for Direction BOTH Though you may wish to use the data in the code conversion value for both inbound and outbound transactions the entry in 2 will not be accepted into the code conversion value table after 1 is entered The reason that entries 1 and 2 are not feasible at the same time is that outbound transactions are using the Internal codes as part o
309. e the trading partner definition is accessed Oracle e Commerce Gateway can verify whether the transaction is enabled for the Trading Partner If this trading partner is not defined in Oracle e Commerce Gateway a process rule exception is detected and an exception message will display in the View Staged Documents window Refer to the Trading Partner chapter for details on how to properly define your trading partners and get a better understanding of how these fields are used in the process TRANSACTION_DATE This column is the schedule generation date that is sent in the transmission EDI_LCONTROL_NUM_1 EDI control number 1 is the control number from the electronic envelope such as the X12 ISA or EDIFACT UNB It is assigned by the customer EDI translator for auditing EDI_CONTROL_NUM_2 EDI control number 2 is the second level control number from the electronic transaction such as the X12 GS It is assigned by the customer EDI translator for auditing EDI_CONTROL_NUM_3 EDI control number 3 is the third level control number from the transaction such as the X12 ST It is assigned by the customer EDI translator for auditing Application Transaction Detail 6 139 Record 1000 Note The fields with the suffix INT are the internal codes that must be defined in the Oracle Release Management One to five external codes from the transaction may be entered into their corresponding external code fields that have the suffixes _EX
310. e unique e Retrieved Data for the Application Open Interface Tables Example Inbound Transaction The Search Key Must Be Unique Columns Category Direction Key 1 Key 2 and External Code 1 and External Code 2 Example of Code Conversion for Inbound Transactions using Direction IN Note Category Direction Key 1 Key 2 External External Internal Code 1 Code 2 Code 1 UOM IN EA Each 1 UOM IN PC Each 2 UOM IN EDIFACT PC Each 2 UOM IN X12 PC Each 2 UOM IN X12 EA Each 3 SHIP_VI IN 1004 1110 TRUCK A Truck air A 3 SHIP_VI IN 1004 1110 TRUCK J Truck mo A tor 3 SHIP_VI IN 1004 TRUCK J Truck air A motor 3 SHIP_VI IN 2010 1005 ALPHA A Alpha air A 10 14 Oracle e Commerce Gateway Implementation Manual Note Category Direction Key 1 Key 2 External External Internal Code 1 Code 2 Code 3 1 4 1 4 SHIP_VI IN 2010 1005 ALPHA J Alpha gr A ound SHIP_VI IN BETA A Beta Ove A right SHIP_VI IN BETA J Beta Gro A und Since keys 1 5 are blank these table entries may be retrieved for all data elements looking for code category UOM for inbound transactions whose external codes 1 2 are listed above The external 1 may be a mixture of EDI standard codes expected from the transaction For example the EA may be the expected X12 code while the PC may be the expected EDIFACT code Since key 1 has the document standard code only Trading Partners given the specific document standar
311. earch keys in the code conversion value table are 10 6 Oracle e Commerce Gateway Implementation Manual identified Because the example uses only two keys only Key1 and Key2 are populated 3 Code Conversion Values window In the Code Conversions Values window the actual data values are entered In the example the value_1 of 1000 is the customer code and the value_2 of 2000 is the customer site number to be used as part of the full search key during code conversion Relationship of the Code Conversion Windows Keys Used Code Conversion Categories Window 3 4 5 Assign Categories Window Key 4 Key 5 Code Conversion Values Window Key 3 Key 4 Key 5 value_1 Keys 3 4 and 5 are not activated in this example The following illustration shows the relationship of the five keys across the three code conversion windows with actual data Code Conversion 10 7 Relationship of the Five Keys Across the Three Code Conversion Windows Keys Used Code Conversion Categories Window Ead Ead 5 Assign Categories Window Key 3 Key 4 Key 5 Customer_CD Customer_Site Code Conversion Values Window Key 3 Key 4 Key 5 Keys 3 4 and 5 are not activated in this example Reading the Code Conversion Values Table Outbound and inbound transactions use different full search keys to access data in the code conversion table The following must be considered when creating the full search keys for successfu
312. ecord Layout Code cccccccce ec eee eee eeeeteee eter eteeeteneeees 5 19 Code Conversion Internal and External Codes on the File 0 00 ec ceec eee eee eeeeeeeees 5 30 6 Application Transaction Detail Oracle InVentOrysiscccasivcscccssiaiecssssasceesiaetececinna dttwotes ottewes beseacekesascapats aaa aa aiian a dapin aeiae 6 1 Outbound Movement Statistics MVSTO No X12 CUSDEC seseeseeeeeeeeereeeerrresrrrrreseen 6 2 Oracle Order Management xicas cided iveicie is sstdee e dle sides a e ea E a a en Ea 6 5 Inbound Purchase Order POI 850 ORDERS ccccecsesceesesseseeeseeseceeseseaseeesaseaeeaneasenseateas 6 6 Comment Textar ar aa aae a a a aa a A a T 6 24 Flag Srna pinia e r T a cee Sew DN T E 6 24 Validate Mode Parameter in Concurrent Managet cccccccccsecsecrecseetecnseeeesenecnseeeenes 6 26 Order Import Open Interface Data cccccccccscc ects ccseene cre ceecnecneeeeeeaecaeeeceesneseeeneeeneenas 6 26 OE_HEADERS_INTERFACE Table 00c cesses eeeeeeseeseessaesee aiiai dicaian diant 6 39 OF LINES INTERFACE Table nic iniri e a enhi accncesulideardbbaateuteonedavs died 6 42 OF PRICE ADJS INTERFACE Table sic ciiiitetnities tenet sited aa ei i e a 6 45 OE RESERVINS INTERFAGE Table ieai a aa ai ade ra Eaa aaa 6 46 OF ACTIONS INTERFACE Tabler iia aena aaa aa EEE AE ER EEE EERE 6 47 Review Order Management Open Interface Exceptions 0 0 cccceee ects reeernetnetees 6 48 Order Impo
313. ed Oracle e Commerce Gateway can verify whether the transaction is enabled for the Trading Application Transaction Detail 6 81 Partner If this trading partner is not defined in Oracle e Commerce Gateway a process rule exception is detected Then an exception message is displayed in the View Staged Documents window Refer to the Trading Partner chapter for details on how to properly define your trading partners and get a better understanding of how these fields are used in the process Transaction Detail Records AMOUNT This column represents the invoice distribution amount If the Invoice Match Option indicated on the transaction interface file is Purchase Order this column is the quantity invoiced multiplied by the unit price If the Invoice Match Option indicated on the transaction interface file is Receipt this amount is distributed across the non invoiced receipts beginning with the oldest If the invoice amount exceeds the total amount for the non invoiced receipts the overage is applied to the newest non invoiced receipt INVOICE_AMOUNT This column represents the total amount for the invoice calculated as the sum of the invoice line amounts INVOICE_NUM This column represents the invoice number for the supplier invoice being imported into Oracle Payables The number must be unique for the supplier as the Payables Open Interface Import program will reject duplicate invoice numbers ITEM_LINE_TYPE_CODE This colum
314. ed or cum quantity Miscellaneous quantity such as ahead behind inventory balance 6 156 Oracle e Commerce Gateway Implementation Manual OTY_TYPE_CODE_INT Quantity Type is used by the Demand Processor to determine how the quantity on schedule lines should be interpreted in context of its Detail Type and Detail Subtype Valid Values e ACTUAL e CUMULATIVE START_DATE_TIME_DET Customer specified date time as transmitted by the customer on the transaction Format YYYYMMDD HHMMSS UOM_CODE_INT_D This is the abbreviated unit of measure code as defined in Oracle Inventory LINE_SOURCE Schedule source at line level since lines can also be manually entered PROCESS_STATUS Indicates the current processing status of a record 1 Do not process 2 Waiting to be processed 3 In process 4 Error 5 Processed 6 Processed with errors REQUEST_ID This column represents a sequence generated unique identifier assigned to the concurrent request for the demand processor Update Columns CREATED_BY This code identifies who loaded this transaction into the Demand Processor tables The code is set to the Requester ID associated with the concurrent manager request that processed this transaction CREATION_DATE This is the date that the e Commerce Gateway loaded the transaction into the Demand Processor table entries This date is set to the system date LAST_UPDATE_DATE Application Transaction Detail 6 157 Thi
315. ed with CHIC must be fully defined as a Trading Partner in the Oracle e Commerce Gateway Address Physical EDI Location EDI Location Address is Use asa Table Address Code Code Linked to Default for Determines Customer ID EDI Location Address ID Code on the Control Record 0010 Address 1 654 South INDY 23245 123423 Blvd Indianapolis IN Address 2 123 Main St CHIC 74536 123423 CHIC Chicago IL Address 3 876 North ATLA 45234 123423 Ave Atlanta GA Note All these EDI Location Codes point to the same Customer ID 123423 In this case the Trading Partner site must still be fully defined as a Trading Partner in the Oracle e Commerce Gateway and the base Oracle Application including entering the EDI Location code in order to process the transaction Multiple Organizations Oracle e Commerce Gateway supports multiple organizations by associating Trading Partners with operating units linked to your responsibility during the Trading Partner group setup Once the operating units are assigned to Trading Partner groups the Trading Partners within the groups are automatically associated with the specified 9 16 Oracle e Commerce Gateway Implementation Manual operating units Therefore when defining Trading Partners you will find only those addresses associated with the specified operating units that are linked to your responsibility from the list of values for selection When multiple operating units are associated with yo
316. ef 1 Ref 2 Ref 3 Record Number Record Layout Record Layout Qualifie r 124 125 126 127 128 129 130 131 132 Reserva tion Flexfiel ds 5 9 Reserva tion Flexfiel ds 10 14 Reserva tion Flexfiel d15 Action Data Actions Flexfiel ds 1 4 Actions Flexfiel ds 5 9 Actions Flexfiel ds 10 14 Actions Flexfiel d15 Lot Serials Data TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD PO PO PO PO PO PO PO PO PO LINE LINE LINE LINE LINE LINE LINE LINE LINE 7110 7120 7130 8000 8100 8110 8120 8130 9000 A2 A2 A2 AC Al A2 A2 A2 LT RS2 RS3 RS4 ACT ACI AC2 AC3 AC4 SER A 56 Oracle e Commerce Gateway Implementation Manual Sequen Data Trading Ref 1 Ref 2 Ref 3 Record Record Record ce Partner Number Layout Layout Qualifie r 133 Serial TP_CD PO LINE 9100 Al LT1 Lot Flexfiel ds 1 4 134 Serial TP_CD PO LINE 9110 A2 LT2 Lot Flexfiel ds 5 9 135 Serial TP_CD PO LINE 9120 A2 LT3 Lot Flexfiel ds 10 14 136 Serial TP_CD PO LINE 9130 A2 LT4 Lot Flexfiel d15 Outbound Purchase Order Change Acknowledgment POAO 855 ORDRSP POCAO 865 ORDRSP A single transaction has the data hierarchy and data looping presented in the following diagram and table Transaction Summary Layouts A 57 POAO POCAO Outbound
317. eit ece mappings em WHERE em map code EC POO FF AND eit output_level 5 AND em map_ id eit map_id ULL ZZ C ir ERIAL ANALYST CODE D 2222422422 C ag C SELECT map id FROM ece mappings WHERE map code EC_ POO FF FIELD500 SYSDATE 1 SYSDATE 1 1 FROM DUAL One INSERT statement is required for each column that was added to the extension 11 10 Oracle e Commerce Gateway Implementation Manual table Note For the extensible architecture columns e The column_name should be populated and not base_column_name Table_name is not mandatory and it can be null e Interface_column_name interface_table_name base_table_name and base_column_name should be null in ece_interface_columns for extensible columns e Record number position width layout code and qualifier should be populated if the column has to be printed on the flat file e The insert statement should be run after seed data reconciliation is run for the transaction FIELDnnn Numbers In the INSERT statement above you define your specific field to a generic FIELDnnn column in the Oracle e Commerce Gateway Five hundred generic FIELD names FIELD1 through FIELD500 are predefined for any table within a transaction It is recommended that you start using FIELD500 then decrease the field n
318. elds 38 Ship To SHIPMENT 3050 Flexfields Address Code 39 Ship To Contact SHIPMENT 3060 40 Shipment SHIPMENT 3800 Attachment ATTACHMENT Master HEADER 41 Shipment SHIPMENT 3810 Attachment ATTACHMENT Detail DETAIL 42 Distributions DISTRIBUTION 4000 4110 Data Transaction Summary Layouts A 143 Seq Data Data Level Record Number Note 43 Distributions DISTRIBUTION 4200 4230 Flexfields Outbound Purchase Orders The following table shows the Common Key positions 1 100 for the Outbound Purchase Order transaction The table shows the position code length and content of the Common Key elements Transaction specific Data in the POO Common Key Position Length Code Content 1 25 25 TP_CD Trading Partner Code as defined in the EDI Translator 26 47 22 PO Purchase order number 48 69 22 ITEM Inventory item id 70 91 22 SHIPMENT Shipment number 92 95 4 varies Record Number 96 97 2 varies Record Layout 98 100 3 varies Record Layout Qualifier The following table shows the Common Key positions 1 100 for the records of the Outbound Purchase Order transaction A 144 Oracle e Commerce Gateway Implementation Manual Transaction specific Data in the Common Key of the POO Transaction Per Record Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner PO LINE SHIPM Number Layout Layout ENT Qualifie r 1 Control TP_CD PO 0010 CT CTL Record 2 Trading TP_CD PO 0020 Al TH1 Partner Header
319. elines regarding file structure changes e Due to the one to many relationship between header and detail level data do not move detail level data to the header level e If you move header level data to the detail level make sure the header level aggregated data is accurately represented as de aggregated data at the detail level This may require some re mapping or custom coding to accomplish e Do not use the same record number across different data levels e Moving records around within the same data level is acceptable Change Record Layout Each data element is defined to a relative position within a record The relative position 4 24 Oracle e Commerce Gateway Implementation Manual indicates the order the data elements are written to the transaction interface file Except for the control record the relative position of a data element in a record may be changed as necessary The following are some guidelines regarding record layout changes Do not change the record layout of the common key in any record The Interface File Definition window prevents this so this guideline applies to custom coding only Do not change the record layout of the control record If you move a data element from one record to another make sure the total length of the record does not exceed 1024 bytes with the first 100 bytes reserved for the common key Change Column Attribute Aside from being defined to a relative position within the record each
320. ements in the common key These data elements are required e Do not delete data elements containing a process rule as process rules are required e Do not delete data elements required by Oracle e Commerce Gateway or Oracle Applications Open Interface These data elements have the Value is Required column rule defined for it Refer to the Application Transaction Detail chapter for a list of required fields by transaction 4 26 Oracle e Commerce Gateway Implementation Manual Activate Additional External Fields for Code Conversion During the design process five external fields are defined for each data element identified as a candidate for code conversion However the actual number of external fields that are activated are based on the requirements of the receiving system Examples of the receiving system s requirements are the EDI standards ISO 9000 standards i e UOM codes or currency codes or specific trading partner requirements Any of the five external fields that are not activated are available for you You can activate these unmapped external fields by assigning the appropriate column attributes including record number position number width sequence layout code layout qualifier and column rules The following are guidelines for activating unmapped external fields e Use the same record number as the other related external fields if the maximum does not exceed 1024 bytes with the first 100 bytes reserved for the common key
321. en ces 1 4 Advice Detail External Referen ces 5 6 Advice Detail Internal Referen ces 1 5 TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD DOC DOC DOC DOC DOC DOC DOC ERR_C NT ERR_C NT ERR_C NT 1020 1030 1040 1900 2000 2010 2020 HD HD AD custom DT DT DT IN1 IN2 TP1 custom EX1 EX2 IN1 Transaction Summary Layouts A 137 Record TP_CD Ref 1 Ref 2 Ref 3 Record Record Record DOC ERR_C blank Number Layout Layout NT Qualifie r 17 Advice TP CD DOC ERR_C 2030 DT IN2 Detail NT Internal Referen ce 6 18 Advice TP CD DOC ERR_C 2040 ER ER1 Detail NT Data Error 19 Advice TP CD DOC ERR_C 2050 AC AC1 Detail NT Data Accept ed 20 Extensio TP_CD DOC ERR_C 2900 custom custom n Table NT Detail Level Outbound Purchase Orders POO 850 ORDERS A single transaction has the following data hierarchy and data looping A 138 Oracle e Commerce Gateway Implementation Manual POO Outbound Purchase Order Structure Record Numbers Control Record 0010 Purchase Order Header 1000 1699 Credits fat OM HEADER Level 1700 1740 Price Adjustments at OM HEADER Level 1800 1850 Reservations at OM HEADER Level 1900 1910 Actions at OM HEADER Level 1950 1990 Item OM LINE Level 2000 2900 Part Numbers here Shipment OM LINE Level 3000 4900 Shipment Detail in this range Cre
322. en issue the SQL count function as follows SQLPLUS gt execute fnd_client_info set_org context lt Org number gt SQLPLUS gt select count ECE ADVO HEADERS V Review all your set ups if the count value is 0 as this indicates there are no eligible documents to be extracted Columns Updated Upon Extraction Once an eligible application advice is successfully extracted and written to the transaction interface file it is marked by Oracle e Commerce Gateway to prevent it from subsequent extraction The following fields are updated based on an excerpt of code in the ECADVOB pls file to update the ECE_LADVO_HEADERS table 6 88 Oracle e Commerce Gateway Implementation Manual e EDI_PROCESSED_FLAG value updated to Y e EDI_PROCESS_DATE value updated to SYSDATE Outbound Payment Order Remittance Advice PYO 820 PAYORD PAYEXT REMADV Two Forms of Electronic Funds Transfer EFT Oracle Applications supports two forms of Electronic Funds Transfer EFT The first is directly from Oracle Payables via a Payables created payment file that is sent to the bank for disbursement directly into the supplier s bank account Refer to the Creating Electronic Funds Transfer Payments without the Oracle e Commerce Gateway section Oracle Payables User s Guide for details The second form of EFT is via the Oracle e Commerce Gateway outbound Payment Order Remittance Advice 820 PAYORD REMADV 820 PAYEXT REMADV transaction
323. er Record Record Layout Record Layout Qualifie r 1 Control Record 2 Basic Purchas e Order Header 3 Currenc y Code amp Convers ion Rates 4 Tax Exempt Informa tion 5 Custom er Paymen t Terms List Price 6 FOB Point Freight Terms TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD PO PO PO PO PO PO 0010 1000 1060 1080 1090 1100 CT PO PO TX TR FB CTL POI CUR TAX TRM FOB Transaction Summary Layouts A 63 Seq Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner Number Layout Layout Qualifie r 7 Shipme TP_CD PO 1110 SH SHP nt Priority Freight Carrier 8 Shippin TP_CD PO 1120 IN NTE g amp Packing Instructi ons 9 Request TP_CD PO 1130 MS HDR Dates Schedul e Limits 10 Header TP_CD PO 1200 Al HD1 Flexfiel ds 1 4 11 Header TP_CD PO 1210 A2 HD2 Flexfiel ds 5 9 12 Header TP_CD PO 1220 A2 HD3 Flexfiel ds 10 14 13 Header TP_CD PO 1230 A2 HD4 Flexfiel ds 15 14 Purchas TP_CD PO 1240 Al PO1 e Order Flexfiel ds 1 4 A 64 Oracle e Commerce Gateway Implementation Manual Seq Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner Number Layout Layout Qualifie r 15 Purchas TP_CD PO 1250 A2 PO2 e Order Flexfiel ds 5 9 16 Purchas TP_CD PO 1260 A2 PO3 e Order Flexfiel ds 1 14 17 Purchas TP_CD PO 1270 A2 PO4 e Order Flexfiel ds 15 18 Global TP_CD PO 1280 Al GL1
324. er 70 91 22 blank Not needed 92 95 4 varies Record Number 96 97 2 varies Record Layout 98 100 3 varies Record Layout Qualifier The following table shows the Common Key positions 1 100 for the records of the Outbound Purchase Order transaction Transaction Summary Layouts A 17 Transaction specific data in the Common Key positions 1 100 per record Data Trading Partner Ref 1 Record Number Record Layout Record Layout Qualifier Control TP_CD Record Basic TP_CD Purchase Order Header Currency TP_CD Code amp Conversi on Rates Payment TP_CD Amount Credit Card Payment Type Co de Tax Exempt FOB TP_CD Point Freight Terms Shipment Priority Shipping Method Shipping TP_CD amp Packing Instructio ns Demand TP_CD Class PO PO PO PO PO PO PO 0010 1000 1060 1070 1090 1100 1110 CT PO PY PY FB NT MS CTL PO1 CUR TAX SHP SHP MIS A 18 Oracle e Commerce Gateway Implementation Manual Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner Number Layout Layout Qualifier Header TP_CD PO 1200 Al HD1 Flexfields 1 4 Header TP_CD PO 1210 A2 HD2 Flexfields 5 9 Header TP_CD PO 1220 A2 HD3 Flexfields 10 14 Header TP_CD PO 1230 A2 HD4 Flexfield 15 Purchase TP_CD PO 1240 A1 PO1 Order Flexfields 1 4 Purchase TP_CD PO 1250 A2 PO2 Order Flexfields
325. er LINE 5140 5160 Flexfields Flexfields 34 TP Line LINE 5170 5190 Flexfields Flexfields 35 Industry LINE 5200 5220 Flexfields Flexfields 36 Extension LINE 5900 Custom Tables Item Data 37 Line Tax Data LINE TAX 6000 6020 38 VAT Tax Data LINE TAX 6025 39 Line Tax LINE TAX 6030 6060 Flexfields Flexfields 40 VAT Tax LINE TAX 6070 6095 Flexfields Flexfields The following table shows the Common Key positions 1 100 for the Outbound Invoice A 188 Oracle e Commerce Gateway Implementation Manual transaction The table shows the position length code and content of the Common Key elements Transaction specific Data in the Common Key Positions 1 100 Position Length Code Content 1 25 25 TP_CD Trading Partner Code as defined in the EDI Translator 26 47 22 INVOICE Invoice number 48 69 22 ITEM Item sequence number 70 91 22 TAX Tax sequence number 92 95 4 Varies Record Number 96 97 2 Varies Record Layout 98 100 3 Varies Record Layout Qualifier The following table shows the Common Key positions 1 100 for the records of the Outbound Invoice transaction Transaction specific Data in the Common Key of the INO Transaction Per Record Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner INVOIC ITEM TAX Number Layout Layout E Qualifie r 1 Control TP_CD INVOIC 0010 CT CTL Record E 2 Trading TP_CD INVOIC 0020 A3 TH1 Partner E Header Flexfiel ds Transaction Summary Layouts A
326. er items and generic items for accurate order fulfilment If only the supplier item is sent then they are more likely to be maintained accurately by the customer If CUSTOMER_ITEM_ID_TYPE is not null then only the table corresponding to its value is searched This enables you to restrict customers to ordering items that are set up using only the specific CUSTOMER_ITEM_ID_TYPE If you want all the tables to be searched then leave this field null For example if you know that the customer sent a customer item and then you should populate CUSTOMER_ITEM_ID_TYPE with CUST to speed up processing Only the customer cross reference item table will be accessed for validating the CUSTOMER_ITEM_NAME If you know the customer sent a UPC code then you should populate CUSTOMER_ITEM_ID_TYPE with the UPC Only the generic item table will be accessed for validating the CUSTOMER_ITEM_NAME If the INVENTORY_ITEM is also populated in the transaction it will be compared to the derived inventory item from the item cross referencing If they are different a warning is generated The derived inventory items will be used in the sales order The following table summarizes the tables that are accessed given the data on record 2000 in the transaction Application Transaction Detail 6 53 Data in the e Commerce Gateway Table Searched Transaction CUSTOMER_ITEM_NAME is populated and Customer Cross Reference table CUSTOMER _ITEM_ID_TYPE is CUST or INT
327. er the transactions the transaction types the translator code and the document standard for code conversion for the trading partner You will also enable the document transaction for processing and set the Test indicator to flag the transaction as test or production 4 Define Trading Partner Contact Optional From the Define Trading Partner window select the Contact tab The information on the contact tab is optional It contains contact data for the specified trading partner It may be used by the EDI Coordinator for the trading partner s EDI Coordinator s contact data This data is for reference only It is not used by Oracle e Commerce Gateway Common Setup Errors The following are common Trading Partner setup errors e Invalid Trading Partner EDI Location Code e Transaction not enabled e Invalid Trading Partner e Trading Partner Group already exists Implementation Details 4 29 e This location already has a different Trading Partner value Overwrite e INVALID_OPERATION error occurred while writing to the output file Refer to Troubleshooting chapter for details Set Up Code Conversion The steps for setting up a Code Conversion are detailed below First read the section on Code Conversion Detail for important details about Code Conversion Refer to the Oracle e Commerce Gateway User s Guide for details to complete the forms 1 Review Define Code Conversion Categories Review the list of seeded Code Conversion Ca
328. er transactions for the handling of 4 8 Oracle e Commerce Gateway Implementation Manual attachment data to suppliers These profiles require the user to define if attachments are to be enabled at various levels of a transaction The purpose of these profile options is to make the transaction interface file size manageable The available values for the profile names listed below are Yes or No Yes will enable the attachments and No will disable the attachments If using attachments you also need to define the attachment segment size profile option Attachments are supported at different levels e Header Level header attachment e Inventory Item level master item attachment and inventory item attachment e PO Line Level line attachment e Shipment level shipment attachment Below is a table showing the purchase order specific transaction profile options their descriptions profile categories an indicator of required or optional and their default values Purchase Order Specific Transaction Profile Option Purchase Description Category Required Default Value Order Specific Transaction Profile Option ECE POO_ATTA Sets the Functional Yes 400 CHMENT_SEG attachment MENT_SIZE segment size for the outbound Purchase Order transaction Attachments can be split into segments to accommodate their insertion into the data file The segment size is expressed in bytes Implementation Details 4 9 Purchase Descriptio
329. erce Gateway Implementation Manual 70 91 92 95 96 97 98 100 22 blank N A varies Record Number varies Record Layout varies Record Layout Qualifier The following table shows the Common Key positions 1 100 for the records of the Inbound Ship Notice Manifest transaction Transaction specific data in the Common Key of the ASNI Transaction Per Record Record TP_CD Ref1 Ref 2 Ref 3 Record Record Record SHIPM LINE blank Number Layout Layout ENT Qualifie r 1 Control TP_CD SHIPM 0010 CT CTL Record ENT 2 Shipme TP_CD SHIPM 1000 L1 DL1 nt ENT Notice Basic Header 3 Carrier TP_CD SHIPM 1010 L2 DL2 Weights ENT Packagi ng 4 Shipme TP_CD SHIPM 1020 L3 DL3 nt ENT Method of Paymen t Transaction Summary Layouts A 121 Record TP_CD Ref 1 Ref 2 Ref 3 Record Record Record SHIPM LINE blank Number Layout Layout ENT Qualifie r 5 Currenc TP_CD SHIPM 1030 L4 DL4 y Tax ENT Paymen t Terms 6 Allowa TP_CD SHIPM 1040 L5 DL5 nces Ch ENT arges Freight 7 Hazard TP_CD SHIPM 1050 HZ HZ1 ous ENT Material Special Handlin 8 8 Header TP_CD SHIPM 1090 N1 NH1 Note ENT 9 Vendor TP_CD SHIPM 1100 AD SF Address ENT Code 10 Destinat TP_CD SHIPM 1120 AX ST ion ENT Address Code 11 Destinat TP_CD SHIPM 1130 CN ST ion ENT Contact 12 Shipme TP_CD SHIPM 1200 Al SH1 nt ENT Header Flexfiel ds 1 4 A 122 Oracle e Commerce Gateway Implementation Manual Record TP_CD Ref1 Re
330. erence types and their names The types are stored in the MTL_CROSS_REFERENCE_TYPES table The corresponding field in the transaction is the CUSTOMER_ITEM_ID_TYPE One of the user defined codes can be written to the Order Import table if you wish to use the Inventory Item Cross Reference table during item cross referencing no values are seeded by Oracle Inventory The following table has samples of the CUSTOMER_ITEM_ID_TYPE that may be defined by the user 6 50 Oracle e Commerce Gateway Implementation Manual Sample of User Defined Cross Reference Meaning Types for Inventory Items UPC Uniform Product Code EAN European Article Number Use any EAN format that you choose ISBN International Standard Book Number Refer the Oracle Inventory User s Guide for details on how to set up the various items Data in the e Commerce Gateway Transaction There are three essential columns in the transaction in record 2000 Either one or both item fields may be populated The customer must decide if the customer item or generic item is placed in the e Commerce Gateway transaction since only one field is in the transaction record to hold either field e Supplier Item INVENTORY_ITEM The supplier s inventory item number as stored in the customer s application and found in the transaction It should be an item defined as an inventory item in Oracle Inventory since it validated against that table e Customer Item CUSTOMER_ITEM_NAME
331. erface file Note Only the primary site for the Control Record was checked in the Oracle e Commerce Gateway 9 4 Oracle e Commerce Gateway Implementation Manual Purpose for Inbound Transactions The EDI Location and Translator code are used to find each address in the base application to retrieve the column ID if it is needed for the application open interface tables The EDI Location and Translator code must be defined as a Trading Partner in the Oracle e Commerce Gateway to verify that this transaction is enabled for this Trading Partner If it is not enabled the transaction is rejected If itis enabled the column ID for the customer or supplier associated with the site on the Control Record is retrieved and passed to the Oracle Application open interface tables All the address sites in the transaction will be associated to this derived customer or supplier The EDI Location and Translator code are used to find each address in the base application to retrieve the column ID if it is needed for the application open interface tables Translator Codes The Translator Code can be any arbitrary text value that you use to define the Trading Partner identifier in the EDI translator The format or selection of the Translator Code might be dictated by the functionality of the EDI translator software A naming convention for the identifier may have been used Typical sources for the Translator Code include e
332. es e Translator Code and EDI Location Code Across Applications e Linking Trading Partner Data to the Oracle Application Source e EDI Location Codes in the Transaction Interface Files e Multiple Organizations e Organizations in Oracle Application Open Interface Tables e Trading Partner Windows Trading Partner In the Oracle e Commerce Gateway the term Trading Partner refers to an entity such as a customer supplier or bank at a particular location or address with which you exchanges routine commercial documents through EDI Since a given entity may have several locations you must define one Trading Partner for each customer address supplier site or bank branch as required for processing by the Oracle e Commerce Gateway For the consideration of multiple organizations you can associate Trading Partners with operating units linked to your responsibility through the Trading Partner Group setups Once a Trading Partner Group is linked to an operating unit all Trading Partners within the group are all automatically associated with the selected operating unit the associated Trading Partner addresses are also linked to the selected operating unit as well Additionally the Trading Partner Type such as a customer supplier or Trading Partner 9 1 bank will also be restricted to the operating unit Trading Partner data must be set up both in your EDI translator software and in the Oracle e Commerce Gateway The set up parameters ar
333. es window In the example the source column for Key 1 Customer is CUSTOMER_NAME and the source column for Key 2 Customer Site is CUSTOMER_SITE Access the Code Conversion Value Table Using Each Search Key Search Code Directio Key 1 Key 2 Key Key Key Externa Order n 11 Categor Custo Custo 3 4 5 y mer mer Code Site First SHIP_V OUT GAMM 9999 AIR Search IA A Second SHIP_V BOTH GAMM AIR Search IA A Third SHIP_V OUT AIR Search IA Source CUSTO CUSTO Column MER_ MER _SI TE NAME Searching the Code Conversion Value Table The code conversion value table is read using the search keys in the table above Three accesses to the code conversion value table may be attempted The order of the search and the constructed keys are shown in the table The three search keys will now be used to search the following example code conversion values table 10 32 Oracle e Commerce Gateway Implementation Manual Example of Searching the Code Conversion Value Table Table Code Direction Key Key Key External Internal Entry Category 1 1 2 3 5 Code Code Customer Customer Site 1 SHIP_VI IN ALPHA 1006 Alpha Ai Alpha Ai A r r 2 SHIP_VI IN ALPHA 1099 Alpha Ai Alpha Fa A r st 3 SHIP_VI IN ALPHA Alpha Ai Alpha Q A r uick 4 SHIP_VI IN BETA 1099 Beta Air Beta Trav A el 5 SHIP_VI IN BETA 1100 Beta Air Beta Fast A er 6 SHIP_VI IN BETA Beta Air Beta Quic A ker 7 SHIP_VI IN AIR Over A Night Source CUSTOM CUSTOM ER_NAM_ ER
334. et to the system date LAST_UPDATE_DATE This date is equal to the CREATION_DATE for this transaction This date is set to the system date LAST_UPDATED_BY This code is equal to the CREATED_BY code for this transaction RLM_INTERFACE_LINES Table The following table lists the required fields for the RLM_INTERFACE_LINES table 6 170 Oracle e Commerce Gateway Implementation Manual Required Fields for the RLM_INTERFACE_LINES Table Oracle Cond Oracle Hardcoded Applications e Commerce Derived Column Gateway Name for Column Required Name Fields Record Number Position Number ITEM_DETAI L_TYPE_INT ITEM_DETAI L_SUBTYPE_ INT DATE_TYPE _CODE_INT START_DAT E_TIME QOTY_TYPE_ CODE_INT ITEM_DETAI L_QUANTIT Y UOM_CODE _INT CUSTOMER _ ITEM_EXT CREATED_B Derived Y CREATION_ Derived DATE HEADER_ID HEADER_ID Derived LAST_UPDA Derived TE_DATE 2000 2000 2000 2000 2000 2000 2040 3100 010 070 130 190 210 270 010 020 Application Transaction Detail 6 171 Oracle Cond Oracle Hardcoded Record Position Applications e Commerce Derived Number Number Column Gateway Name for Column Required Name Fields LAST_UPDA Derived TED_BY LINE_ID LINE_ID Derived LINE_SOUR Derived CE PROCESS_ST Derived ATUS REQUEST_ID Derived SCHEDULE_ Derived LINE_NUM LINE_ID This column represents a sequence generated unique identifier HE
335. f 1 Ref 2 Ref 3 Record Record Record Partner Number Layout Layout Qualifier Discount TP _CD PO 1810 PR AD1 List Names Price TP_CD PO 1820 Al AD1 Adjustme nt Flexfields 1 4 Price TP_CD PO 1830 A2 AD2 Adjustme nt Flexfields 5 9 Price TP_CD PO 1840 A2 AD3 Adjustme nt Flexfields 10 14 Price TP_CD PO 1850 A2 AD4 Adjustme nt Flexfield 15 Reservati TP_CD PO 1900 RS RES ons Data Reservati TP_CD PO 1910 Al RS1 on Flexfields 1 4 Reservati TP _CD PO 1920 A2 RS2 on Flexfields 5 9 A 22 Oracle e Commerce Gateway Implementation Manual Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner Number Layout Layout Qualifier Reservati TP _CD PO 1930 A2 RS3 on Flexfields 10 14 Reservati TP CD PO 1940 A2 RS4 on Flexfield 15 Action TP_CD PO 1950 AC ACT Data Actions TP_CD PO 1960 Al ACI Flexfields 1 4 Actions TP_CD PO 1970 A2 AC2 Flexfields 5 9 Actions TP_CD PO 1980 A2 AC3 Flexfields 10 14 Actions TP_CD PO 1990 A2 AC4 Flexfield 15 Item Data TP_CD PO LINE 2000 IT ITM Original System Reference Configur ation Data Transaction Summary Layouts A 23 Data Inventory Item Segments 1 10 Inventory Item Segments 11 20 Operatio n Code Price Quantitie s List Price Customer Payment Terms Tax Exempt Project Task Contract Numbers Service Transacti on Comment s FOB Point Freight Terms Shipment Priority Method
336. f 2 Ref 3 Record Record Record SHIPM LINE blank Number Layout Layout ENT Qualifie r 13 Shipme TP_CD SHIPM 1210 A2 SH2 nt ENT Header Flexfiel ds 5 9 14 Shipme TP_CD SHIPM 1220 A2 SH3 nt ENT Header Flexfiel ds 10 14 15 Shipme TP_CD SHIPM 1230 A2 SH4 nt ENT Header Flexfiel d15 16 Basic TP_CD SHIPM LINE 2000 L1 IT1 Item ENT Data 17 Hazard TP_CD SHIPM LINE 2010 L2 IT2 ous ENT Material Codes 18 Currence TP_CD SHIPM LINE 2020 L3 IT3 y Tax ENT Item Level 19 Notes TP_CD SHIPM LINE 2030 N1 ND1 ENT 20 Shipme TP_CD SHIPM LINE 2100 A1 SL1 nt Line ENT Flexfiel ds 1 4 Transaction Summary Layouts A 123 Record TP_CD Ref1 Ref 2 Ref 3 Record Record Record SHIPM LINE blank Number Layout Layout ENT Qualifie r 21 Shipme TP_CD SHIPM LINE 2110 A2 SL2 nt Line ENT Flexfiel ds 5 9 22 Shipme TP_CD SHIPM LINE 2120 A2 SL3 nt Line ENT Flexfiel ds 10 14 23 Shipme TP_CD SHIPM LINE 2130 A2 SL4 nt Line ENT Flexfiel d15 24 Order TP_CD SHIPM LINE 2140 Al RCI Line ENT Flexfiel ds 1 4 25 Order TP_CD SHIPM LINE 2150 A2 RC2 Line ENT Flexfiel ds 5 9 26 Order TP_CD SHIPM LINE 2160 A2 RC3 Line ENT Flexfiel ds 10 14 27 Order TP_CD SHIPM LINE 2170 A2 RC4 Line ENT Flexfiel d15 28 Destinat TP_CD SHIPM LINE 3000 AX ST ion ENT Address Code A 124 Oracle e Commerce Gateway Implementation Manual Record TP_CD Ref1 Ref 2 Ref 3 Record Record Record SHIPM LINE blank Number Layout Layout ENT Qualifie r 2
337. f Site Code Location Code to Copy from the Transaction Detail into the Control Record 0010 Invoice INI 810 INVOIC Supplier Site Planning SPSI 830 DELFOR Supplier Ship To Schedule Site Trading Partner 9 11 Transaction Transaction ASC X12 EDIFACT Type of Site Code Location Code to Copy from the Transaction Detail into the Control Record 0010 Price Sales CATI 832 PRICAT Supplier Site Catalog Production PSQI 866 Supplier Ship To Sequence Site Purchase Orders POI 850 ORDERS Customer Ship To Site Response to RRQI 843 REQOTE Supplier Site Request for Quotation Ship Noticeand SBNI 857 Customer Ship Billing To Site Ship ASNI 856 DESADV Customer Ship Notice Manifest To Site Shipping SSSI 862 DELJIT Supplier Ship To Schedule Site Transaction Detail Address Records The transaction detail records contain address records such as the ship to address or bill to address The records usually have record types of AD to identify them as address records and a record qualifier like ST for ship to or BT for bill to to identify the type of address The Oracle e Commerce Gateway does not examine address site usage such as bill to usage or ship to usage in the base Oracle Application trading partner tables The site usage for an address in the file is defined by what record the address is found in the transaction interface file Each address record has an internal address Location Code and an external address Location Code The
338. f any exception Once the cause of an exception is identified and resolved you have the option to resubmit the transaction for processing ignore the exception or delete the transaction Implementation Details 4 13 To take advantage of Oracle e Commerce Gateway s exception handler you must first define the validation rules There are two types of validation rules one at the process level for the overall transaction and the second at the column level for the individual data elements within a transaction You define the validation rules using the Assign Process Rules or Assign Column Rules window accessible via the Interface File Definition window Process Rules Process rules are defined at the transaction level and apply to the entire transaction Process rules are required and should not be changed although the Assign Process Rules window does not prevent it Oracle e Commerce Gateway s exception handler supports three process rules as follows e Invalid Trading Partner This rule checks if the incoming translator code location code combination on the interface file control record is defined for a trading partner Additionally the transaction type identified on the incoming interface file must be enabled for the trading partner identified e Test Production Discrepancy This rule checks if the incoming test flag on the control record 0010 in the transaction interface file matches the flag setting for the Trading Partner identified
339. f the entire search key When the value Each is found in the transaction even if the Trading Partner was given a default standard to use for code conversion the internal code Each cannot determine whether EA or PC should be written to the transaction interface file Similar reasoning applies to 3 4 and 5 6 when items 4 and 6 are attempted to be entered Multiple Standard Codes Convert to a Single Internal Code There may be code conversion entries needed where multiple codes in a single standard may need to be converted to a single code in the Oracle application The following table illustrates this case In the table columns Category Direction Key 1 Key 2 Key 3 and Internal Code comprise the outbound transaction s entire search key This search key must be unique The columns External Code 1 and External Code 2 are data retrieved for the Transaction Interface File Code Conversion 10 21 Example of Multiple Standard Codes Convert to a Single Internal Code Categ Directi ory on searc searc h key h key Key 1 searc h key Key 2 searc h key Key 3 Intern searc al h key Code searc h key Extern Extern al al Code Code 1 2 retrie retrie ved ved data data Note 1 UOM OUT X12 Acme Denver Each 2 UOM OUT X12 Acme Chicag Each o 3 UOM OUT X12 Acme Each EA BX PC Tradin 8 Partner site specifi ed will have EA on the file Tradin 8 Partner site specifi
340. facturing product 6 94 Oracle e Commerce Gateway Implementation Manual Transaction Direction Transaction ASC X12 EDIFACT Name Code OPM Purchase Inbound GPOI 850 ORDERS Order OPM Purchase Outbound GPOAO 855 ORDRSP Order Acknowledgmen t OPM Ship Outbound GASNO 856 DESADV Notice Manifest Refer to the product documentation for details on how to implement these transactions Note See Oracle Process Manufacturing Transaction Summaries page A 101 for layout details Current Information The transaction requirements may change when enhancements are made such as additional data added to the transaction Current transaction details can be found on Oracle Support s web site Current detail record layouts are reported via the Transaction Layout Definition Report and the Interface File Data Report Oracle Purchasing The implementation of any transaction requires some setup in Oracle Applications and Oracle e Commerce Gateway This chapter focuses on the application setups necessary to implement a transaction that integrates with Oracle Purchasing Note See Oracle Purchasing Transaction Summaries page A 102 for layout details The following table lists the transactions that integrate with Oracle Purchasing Application Transaction Detail 6 95 Transaction Direction Transaction ASC X12 EDIFACT Name Code Price Sales Inbound CATI 832 PRICAT Catalogue Response to Inbound RROI 843 QUOTES Request for Qu
341. ference fields are used to match change orders to original orders Thus these values must be unique within all orders for a customer and entered with the new orders The same algorithm that determines this data must be used to derive the data in the new order POI transaction and change order POCI transaction process to successfully matched change orders to new orders Application Transaction Detail 6 15 Original System Reference Data in all Order Import Tables Table LEVEL Data Element Default Content Sample Header Original System Purchase Order 86420 03 Number Release if Document Reference applicable Line Original System Customer Line 001 Number Line Reference Line Original System Current Request Data 19990308000 CHC 01 Shipment Reference Ship to EDI Location Code Higher level Original System data is propagated to the lower data levels in the transaction For example the derived ORIG_SYS_DOCUMENT REFERENCE at the header level is copied to the same field at the LINE and all other used levels for that transaction Data must be unique only within the given customer This is illustrated in the following table Unique Data for Each Customer Table Level Data Element Customer A Customer B Header Original System 86420 03 86420 03 Document Reference Line 1 First Original System 86420 03 86420 03 Shipment Document Reference Copy from Header Line 1 First Original System 001 001 Shipment Line Refere
342. ferent operating unit each time when you run the program See the Outbound Transactions chapter in the Oracle e Commerce Gateway User s Guide for details Refer to the Trading Partner chapter for recommendations on selecting the correct trading partner EDI Location Code for the control record 0010 for the transaction in the transaction interface file Relevant Oracle Purchasing Profiles and Set Ups The following is a list of the Purchasing set ups related to the outbound Purchase Order transaction 1 Archive on lt Attribute gt for original orders In the Setup gt Purchasing gt Document Types window set the following Set the Archive on Approve for each document type enabled DO NOT set the attribute to Archive on Print This prevents the eligible purchase orders from being extracted since they will print and archive before the extract can happen Refer to the Oracle Purchasing User s Guide for the details Extract Criteria The outbound Purchase Order transaction is controlled by three database views that are defined according to the Oracle Purchasing data model for purchase orders The three views contain variables which are dynamically set based on your responses to the extract program parameters refer to Oracle e Commerce Gateway User s Guide Outbound Transactions chapter for a list of the program parameters The three database views are as follows e ECE_POO_HEADERS V ECE_POO_LINES V e ECE_POO_SHIPMENTS_V
343. fied by ITM to distinguish the data from other IT records in this transaction 2100 A1 IT1 Flexfield data with Reusable Record A1 Layout qualified by IT1 5 18 Oracle e Commerce Gateway Implementation Manual Record Number Record Layout Record Qualifier Content 2110 A2 IT2 Flexfield data with Reusable Record A2 Layout qualified by IT2 Common Records Based on Record Layout Code Record Layout codes are indicated in positions 96 97 of the common record key Several data elements relate to each other and can be found in several standard transactions These related elements for example include addresses contact data and flexfields The actual content of any record is qualified by the record layout qualifier for example ST or ST1 for ship to address and BT or BT1 for bill to address Verify the record layout for any record in a transaction including its data element length of the field and its position using the record in the Interface File Definition window Note You can modify these record layouts However any changes may affect the Translator data map you are using The following table contains record layout codes their descriptions and meanings These record layouts may be seen in many transactions Common Record Layout Record Layout Codes Description Meaning Al Flexfield Layout 1 Flexfields Layout 1 Layout 1 contains the Flexfield Context plus attributes each with length 80 The interfa
344. file of the data from the base Oracle Application The Translator copies the data to its position in the chosen standard The following illustration shows sample data from an ASC X12 Purchase Order 850 transaction on the right and an Oracle e Commerce Gateway outbound purchase order POO interface file on the left 1 10 Oracle e Commerce Gateway Implementation Manual Sample Interface File Between Oracle e Commerce Gateway and Purchase Order O01 0CRCTLEDPPOO STAND 60003432 Poo 101168514PR0D 09560566332 1000PNPa160003432 O 19900610 1436 5EeramDARD O 0010 gt ISA GS 1010P0p0214 15 Fet 30 Common Carriar Delivered Prapay and Add NII 1020RFORC3 23029 ENTEX INFORMATION GERVICES IFC 103 0P0Pa3 1040a1 P01 sANDARD 1000 gt BEG 1050AR2FO2 1060AR2FO3 AWD e ELLI 01 0959036 1080A1601 S POrO95H56332 23029 02062A 980618 71 443 182 1090425902 F2 950 19210001 110042903 He 0 EE G0003432 980618 111042604 EDI Y PERADI CHARL GUTERIE TE 617 352 0299 113042662 FOB DF 2i Delivered 1140a298316510676502 16652502 LD re rere 18 15 Bet 30 115022994 2000 gt PO1 rm 002 980712 1160aDa01 28110 zomo 02062 vB uA TDS Common Carrier 1170CH861617 475 3947 B1 VE EFTEX INFORMATION GERVICES IHC 1100CF662 M1 98T Fidelity Invastmenta I2 J J DALY 1190AXATIJIDALY Fidality Inveetmente c o J J Daly amp Tida St Z3 0 0 J J Daly Tide street 1200cHaTIRDBE gcorT we v10c 617 563 5416 44 Boston HA 02110 1210axeT11
345. following table shows the Common Key positions 1 100 for the Outbound Application Advice transaction The table shows the position length code and content of the Common Key elements Transaction specific data in the ADVO transaction Common Key Position Length Code Content 1 25 25 TP_CD Trading Partner Code as defined in the EDI Translator 26 47 22 DOC Related Document ID 48 69 22 ERR_CNT Error Counter A 88 Oracle e Commerce Gateway Implementation Manual Position Length Code Content 70 91 22 blank Not Used 92 95 4 varies Record Number 96 97 2 varies Record Layout 98 100 3 varies Record Layout Qualifier The following table shows the Common Key positions 1 100 for the records of the Outbound Application Advice transaction Transaction specific data in the Common Key of the ADVO transaction per record Record TP_CD Ref 1 DOC Ref 2 ERR_C NT Ref 3 blank Record Record Record Number Layout Qualifie r Control Record Trading Partner Header Attribut es Trading Partner Header Attribut es Trading Partner Header Attribut es TP_CD TP_CD TP_CD TP_CD 0010 0020 0030 0040 CT CTL Al TH1 A2 TH2 A2 TH3 Transaction Summary Layouts A 89 Record 5 Trading Partner Header Attribut es 6 Trading Partner Detail Attribut es 7 Trading Partner Detail Attribut es 8 Advice Header External Referen ces
346. for Inbound Transaction 10 10 Oracle e Commerce Gateway Implementation Manual Goal Create a key including the known 1 5 external codes on the transaction interface file to find the internal code that is needed for the base Oracle application open interface table Keys 1 5 are optional Keys are used when the table entry does not apply to all Trading Partners The following table illustrates a full search key search performed for an inbound transaction The columns Category Direction Keys 1 thru 5 and External Code 1 through External Code 5 represent the entire search key The columns Internal Code represents the data retrieved to write to the Application Open Interface Tables Full Search Key for Inbound Transaction Categor Directio Keys1 Externa Externa Externa Externa Externa Internal y n thru 5 Code Code Code Code I Code Code 1 2 3 4 5 UOM IN EA Each UOM IN PC Each Understanding Code Conversion for Outbound Transaction using Direction OUT For outbound transactions the entire search key to access the table entries consists of the following e Category e Direction e Keys1 5 e Internal Code This full search key is used to find a table entry to return the external codes 1 5 that can be copied to the transaction interface files During code conversion for outbound transactions code conversion table entries marked with the direction OUT and BOTH are read See section below on the direction BOTH En
347. freshed without the deleted documents Troubleshooting 8 13 Transaction Exception Summaries There are four summary windows on the right side for different level tree nodes The summary window for the Status options All Status Status with Errors and Transaction options All Transactions Transactions with Errors are very similar The only difference is the order of the status and the transaction fields The status level 1 summary for the Status options shows the following information Status Transaction Number of Documents Total Violations Status of selected documents currently in the staging table List of transaction type name for given status Number of documents for given status transaction type Total number of exceptions including all the processing and column exceptions for given status transaction type The status level 2 summary for the Status options shows the following information Status Transaction Trading Partner Number of Documents Total Violations Status of selected documents currently in the staging table Identifies the transaction type name List of trading partner names for the selected transaction Number of documents for given status transaction type and trading partner Total number of exceptions including all the processing and column exceptions for given status transaction type and trading partner The status level 3 summary for the Status
348. from the Define Code Conversion Category window The category is assigned to a transaction This prevents the category from being deleted Solution All assignments for this category to transactions must be removed before the code conversion category can be deleted This can be accomplished by using the Assign Code Conversion Categories window Troubleshooting 8 3 Message Description and Solution This location already has a different Trading Partner value Trading Partner Group tp_group_code already exists Enter a unique group code Description The value selected in the Site field on the DefineTrading Partner window Assignment tab for either the Customer or the Supplier is already defined to a trading partner Solution You must be careful how you reply to this question If you answer Yes you may override a valid Trading Partner assignment made in the DefineTrading Partner window Assignment tab To be on the safe side No should be the appropriate response and some research should be performed before continuing Description The user has attempted to add a trading partner group that already exists Solution Either add your trading partner information to an existing trading partner group or create a new trading partner group Common Processing Error Messages Common Processing Error Messages Message Description and Solution INVALID_OPERATION error occurred while writing to output f
349. g Partner Link to Oracle e Commerce Gateway Legal entities are defined in Oracle Human Resources Included in the definition is the EDI Location Code that trading partners agree to exchange to represent the full detailed address Often they do not send the full address but just the EDI Location Code a critical data field to Oracle e Commerce Gateway The EDI Location Code is the link between a legal entity in Oracle Human Resources and the trading partner site definition in Oracle e Commerce Gateway This enables Oracle e Commerce Gateway to access the detailed data about the legal entity in Oracle Human Resources without maintaining the detail data in Oracle e Commerce Gateway To ensure that the trading partner link between Oracle e Commerce Gateway and 6 2 Oracle e Commerce Gateway Implementation Manual Extract Criteria Oracle Human Resources is set up properly verify that the legal entity and the EDI Location Code in Oracle Human Resources is the correct legal entity selected for the trading partner definition in Oracle e Commerce Gateway The selected legal entity and the EDI Location Code defined in Oracle Human Resources are displayed in the Define Trading Partners window Assignment tab If the data is not what you intend it to be you must make the appropriate changes for the transaction to be extracted for the correct trading partner This could involve either altering the legal entity in Oracle Human Resources or assigning a diffe
350. g outbound transactions Crucial to the successful implementation of an outbound transaction are all the setups necessary in Oracle e Commerce Gateway and Oracle Applications plus the application process to ensure that documents are eligible for extraction So before you initiate the extract process you must verify all your setups This chapter assumes that the outbound transaction interface file will be placed in the directory specified in the Oracle e Commerce Gateway system profile ECE Output File Path and is available for the downstream processes i e Translator or other process Refer to the Application Transaction Details for details related to the following for the outbound transaction you are implementing e Transaction specific special considerations e Trading partner link between Oracle e Commerce Gateway and Oracle Applications 7 4 Oracle e Commerce Gateway Implementation Manual Extract Criteria Columns Updated Upon Extraction Verify Oracle e Commerce Gateway Setups Verify the following in the Oracle e Commerce Gateway System profiles are set Relevant transaction profiles are set Trading partner is defined and linked to Oracle Applications Transaction is enabled at the system profile level as well as at the trading partner detail level Relevant code conversions are defined Verify Oracle Applications Setups Verify the following in the appropriate Oracle application Relevant application profile and set ups a
351. gement Demand Processor to revalidate the transaction Oracle Shipping Execution The following table lists the transaction delivered with Release 12 Oracle Shipping Execution Transactions Transaction Direction Transaction ASC EDIFACT Name Code X12 Ship Outbound DSNO 856 DESADV Notice Manifest The topics covered for outbound transactions include the following e Trading Partner Link to Oracle e Commerce Gateway e Relevant Oracle Shipping Execution Setups e Extract Criteria e Columns Updated Upon Extraction Current Information The transaction requirements may change when enhancements are made such as additional data added to the transaction Current transaction details can be found on Oracle Support s web site 6 174 Oracle e Commerce Gateway Implementation Manual Current detail record layouts are reported via the Transaction Layout Definition Report and the Interface File Data Report Note See Oracle Shipping Execution Transaction Summaries page A 229 for layout details Outbound Shipment Notice Manifest DSNO 856 DESADV Trading Partner Link to Oracle e Commerce Gateway Customers and Customer sites are definedSuppliers are defined in either Oracle Order Management or Oracle Receivables Included in the definition is the EDI Location Code that trading partners agree to exchange to represent the full detailed address Often they do not send the full address but just the EDI Location Code This is a critica
352. given transaction ORDER_CATEGORY This code identifies the category of the order as defined in Order Management The valid values are ORDER MIXED or RETURN DEFAULT The code is set to ORDER 6 40 Oracle e Commerce Gateway Implementation Manual ORDER_DATE_TYPE The expected type of date is defaulted in Order Import to the value set up for the customer or customer site The value will apply to all dates in the transaction You may override the customer default by entering one of the following codes in the transaction or derive it through code conversion For code conversion you can copy the date qualifier found in the standard transaction to the e Commerce Gateway transaction and set up code conversion to derive one of the following codes e ARRIVAL e SHIP ORDER_SOURCE_ID This code identifies that the transaction was loaded into Order Import via the e Commerce Gateway DEFAULT The code is set to 6 meaning EDI ORDER_TYPE This code identifies the type of order such as a standard order You define these codes in Order Management There is no default You must enter a value READY_FLAG This flag indicates if the transaction is ready to be moved to the Order Management base order tables if all validation is passed If you set it to N even the valid order would remain in the Order Import tables until the flag is set to Y or the transaction is deleted from the Order Import tables SOLD_TO_ORG_ID Not activated on t
353. h is found or until all values are exhausted If a match is found using the external value s an internal value from the Code Conversion value table is passed to the application open interface table if no transaction exceptions are found by the Oracle e Commerce Gateway If a match is not found a null value is returned and the external 1 field is passed to the application open interface table if no transaction exceptions are found by the Oracle e Commerce Gateway Note It is recommended to use unique identifiers such as translator code location code or the combination of both which are available at the time of code conversion as keys to identify the customer supplier or bank for code conversion Outbound Transactions An outbound transaction begins when data is extracted from Oracle applications The Oracle e Commerce Gateway performs code conversion where applicable For each data element activated for code conversion a search key made up of up to five concatenate values defined in the Code Conversion windows is searched for in the transaction columns specified in the Assign Categories window Any number of values from 1 to 5 can be specified when you define code conversion values in the Define Code Conversion Values window These values are concatenated to form the search key Multiple searches are performed first using all defined values If no match is found the last value is dropped from the search key and the search is
354. h the modified key continues until a table entry is found or no table entry is found This modification of the key continues until the last 10 2 Oracle e Commerce Gateway Implementation Manual access is made with all five search keys set to blanks Table entries with the 1 5 search keys set to blanks means that the table entry is applicable to all Trading Partners Code Conversion Process While the setup steps for code conversion are identical for inbound and outbound transactions the specific process of code conversion differs Inbound Transactions An inbound transaction arrives in a transaction interface file that is then processed by the Oracle e Commerce Gateway The import program reads the transaction interface file stores the data in memory and performs code conversion For each data element activated for code conversion a search key made up of up to five concatenated values defined in the code conversion windows is searched for in the transaction columns specified in the Assign Categories window Any number of values from 1 to 5 can be specified when you define code conversion values in the Code Conversion Values window These values are concatenated to form the search key Multiple searches are performed first using all defined values If no match is found the last value is dropped from the search key and the search is performed again using the remaining concatenated values This process is performed again until either a matc
355. hanged by the user The report parameters are shown in the following table Refer to the Reports section of the Oracle e Commerce Gateway User s Guide for more detail Report Parameters Valid Values List of Values Required Transaction Code Enter lt blank gt to Yes No select all Transactions or enter a specific Transaction Troubleshooting 8 17 Report Parameters Valid Values List of Values Required Include Data not Enter Yes or No to Yes Yes Mapped include exclude data not mapped Default is No Interface File Data Report This report allows the user to produce a hard copy listing of the data contained within a specific transaction data file The report contains the transaction record layout and the actual data stored in each of the data fields The report parameters are shown in the following table Report Parameters Valid Values List of Values Required Transaction Code Enter specific Yes Yes Transaction Code Path to Data File Enter the directory No Yes path where the data file resides Default from profile option value for inbound outbound based on transaction code Data File Name Enter the name of the No Yes data file 8 18 Oracle e Commerce Gateway Implementation Manual 9 Trading Partner This chapter contains trading partner information This chapter covers the following topics e Trading Partner e Trading Partner Group e EDI Location Codes e Translator Cod
356. hat Translator Code That determination is totally in the realm of Trading Partner definitions as you determine and set up within the EDI Translator Translator Code and EDI Location Code Across Applications The relationship of the Translator Code and the EDI Location Code across the three applications is illustrated below The Oracle e Commerce Gateway shares the following codes with the other applications for the following reasons e The EDI Location Code is shared with the base Oracle Application to identify an address site e The EDI Translator Code is shared with the Translator It is used to identify the Trading Partner in the translation software This code is first defined in the translator then copied to the Oracle e Commerce Gateway For outbound transactions this code is written on the Control Record 0010 so the translator can identify the Trading Partner For inbound transactions the Translator Code is used to distinguish Trading Partners who may use the same set of EDI Location Codes Trading Partner 9 7 Relationship Diagram of Translator Code and EDI Location Code Across Applications Base Oracle Application Computer Warehouse Services 124 45Sth St San Jose CA Link established in Assignment Window of Trading Partner Form Oracle e Commerce EDI Translator Gateway Trading Partnen CWS San Jose Computer Warehouse Services Site Address with 124 45Sth St Location San Jose CA
357. he Outbound Application Advice transaction Transaction specific Data in the Common Key of the ADVO Transaction Per Record Record TP_CD Ref1 Ref 2 Ref 3 Record Record Record DOC ERR_C blank Number Layout Layout NT Qualifie r 1 Control TP_CD 0010 CT CTL Record 2 Trading TP_CD 0020 Al TH1 Partner Header Attribut es Transaction Summary Layouts A 135 Record TP_CD Ref1 Ref2 Ref3 DOC ERR_C blank NT Record Number Record Layout Record Layout Qualifie r 3 Trading Partner Header Attribut es 4 Trading Partner Header Attribut es 5 Trading Partner Header Attribut es 6 Trading Partner Detail Attribut es 7 Trading Partner Detail Attribut es 8 Advice Header External Referen ces 1 4 9 Advice Header External Referen ces 5 6 TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD DOC DOC 0030 0040 0050 0060 0070 1000 1010 A2 A2 A2 Al A2 HD HD TH2 TH3 TH4 TD1 TD2 EX1 EX2 A 136 Oracle e Commerce Gateway Implementation Manual Record TP_CD Ref 1 DOC Ref2 Ref3 ERR_C blank NT Record Number Record Layout Record Layout Qualifie r 10 11 12 13 14 15 16 Advice Header Internal Referen ces 1 5 Advice Header Internal Referen ce 6 Trading Partner Address Extensio n Table Header Level Advice Detail External Refer
358. he Oracle Supplier Scheduling data model for planning schedules The two views contain variables which are dynamically set based on your responses to the extract program parameters refer to Oracle e Commerce Gateway User s Guide Outbound Transactions chapter for a list of the program parameters The two database views are as follows e ECE_SPSO_ITEMS_V e ECE_SPSO_HEADERS_V The ECE_SPSO_HEADERS_V view is used to identify which planning schedules are Application Transaction Detail 6 179 eligible for extraction The extract criteria are as follows e Trading partner is defined e Transaction type enabled for the trading partner e Planning schedule has not been printed or previously extracted e Planning schedule defined in Supplier Scheduling with communication code of EDI or BOTH e Planning schedule has a status of CONFIRMED e Planning schedule horizon start end dates fall within the organization s period start end dates If necessary you can use SQLPLUS to verify if there are any eligible documents to be extracted To do so you must first set the organization context and then issue the SQL count function as follows SQLPLUS gt execute fnd_client_info set_org context lt Org number gt SQLPLUS gt select count ECE SPSO HEADERS V Review all your set ups if the count value is 0 as this indicates there are no eligible documents to be extracted Columns Updated Upon Extraction Once an eligible
359. he View Staged 6 74 Oracle e Commerce Gateway Implementation Manual Documents window Refer to the Trading Partner chapter for details on how to properly define your trading partners and get a better understanding of how these fields are used in the process Transaction Detail Records AMOUNT This column represents the invoice distribution amount If the Invoice Match Option indicated on the transaction interface file is Purchase Order this column is the quantity invoiced multiplied by the unit price If the Invoice Match Option indicated on the transaction interface file is Receipt this amount is distributed across the non invoiced receipts beginning with the oldest If the invoice amount exceeds the total amount for the non invoiced receipts the overage is applied to the newest non invoiced receipt INVOICE_AMOUNT This column represents the total amount for the invoice calculated as the sum of the invoice line amounts INVOICE_NUM This column represents the invoice number for the supplier invoice being imported into Oracle Payables The number must be unique for the supplier as the Payables Open Interface Import program will reject duplicate invoice numbers ITEM_LINE_TYPE_CODE This column identifies the invoice line type The valid values are ITEM TAX FREIGHT or MISCELLANEOUS Review Oracle e Commerce Gateway Exceptions Use the Oracle e Commerce Gateway View Staged Documents window to review the Oracle e Commerce G
360. he actual document standard X12 suffices since the external codes are unique Both Internal Code and External Codes on the Transaction Interface File You could set up Column Rules on the internal column in the transaction though the internal value is not found on the transaction interface file This may occur when the Application Open Interface file may require a value in certain columns but the values are derived by the Oracle e Commerce Gateway This assumes that code conversion is performed on the data element using the internal and external values on the files that are associated with that data element Code conversion is performed before any column rule validation is performed on a column data element defined in the transaction The code conversion process Code Conversion 10 25 associates in memory the internal code found in the code conversion table to the internal field that has the assigned Column Rule The value of that internal field is validated against all the Column Rules enabled for that field Code Conversion is performed before Column Rules are applied Consider the example shown in the following table to satisfy the data requirement if code conversion is performed on a field 10 26 Oracle e Commerce Gateway Implementation Manual Example of Code Conversion is Performed on a Field Application Oracle Sample Sample Code No Code Open e Commerce Record Position Conversion Conversion Interface Gateway Number Number
361. he address precedence profile option has the following list of values LOC Default Address components and or location code combination The address derivation uses the combination of location code and address components to derive the address If there is only one value provided either location code or address components the address will be derived based on the provided value If both location code and address components are provided then it will be based on the combination of both Note If no address is found for both location code and address components or if the populated address components and location code do not match then a message Unable to derive ship to address will appear If both location code and physical address are provided then it will derive address through location code and compare it with that derived through physical address LTC Location code translator code combination A trading partner setup is required for the address to be derived LPA Location code physical address party details combination The address derivation uses the combination of location code customer name customer number and address components to derive the address If there is only a partial set of values provided the address will be derived based on the provided values This feature is available only for address type CUSTOMER Transaction Specific Options Purchase Order Transactions Additional profiles exist for the Purchase Ord
362. he following e Inthe Trading Partner Group window the Trading Partner group and Trading Partner name are defined e Inthe Trading Partner Details tab the appropriate transaction and transaction types are enabled the Test Production flag is set to the correct code the Translator Code is accurately entered and the EDI box is enabled e Inthe Trading Partner Assignment tab the Trading Partner is linked to the appropriate address site in the base Oracle Application e In the base Oracle Application the Trading Partner and Trading Partner site is defined and the EDI Location Code for the site is entered Control Record 0010 The primary EDI Location Code for a transaction is written to the Control Record 0010 9 14 Oracle e Commerce Gateway Implementation Manual along with the Translator Code These are critical for each process to identify the Trading Partner Transaction Detail Address Records Like the inbound transaction the outbound transaction detail records contain address records such as the ship to address or bill to address The records usually have record types of AD to identify them as address records and a record qualifier like ST for ship to or BT for bill to to identify the type of address Each address record has an internal address Location Code and an external address Location Code The Oracle e Commerce Gateway populates both location fields in the transaction interface file The EDI Location Code for that add
363. he requirements A Translator data map may be defined to produce a transaction according to the recommendations of any industry guideline such as UCS EIDX or AIAG A single data map may accommodate the data requirements of a single trading partner or many trading partners 4 30 Oracle e Commerce Gateway Implementation Manual The Translator identifies each trading partner s transactions with a unique code and then invokes a communication method ftp e mail fax etc to transmit this file either to the trading partner directly or to a third party for further processing or communication The process is reversed received communication of standard EDI file through translator to interface file for inbound transactions The following should be considered for interfacing with a Translator e Accurate Translator Code e Available reports e Changes in Record Layout due to upgrade or patch e Predefined record layouts and data maps in the Translator e Synchronize record layouts in the Oracle e Commerce Gateway and the Translator e Create data maps in the Translator for inbound transaction e Create data maps in the Translator for outbound transactions e Detecting Files e Transferring Files e Communications Accurate Translator Code The Translator Code is used to identify Trading Partners between the Oracle e Commerce Gateway and the Translator The Translator Code is first defined in the Translator In the Translator it is used to acce
364. he transaction interface file This code identifies that the customer for all the ship to sites in the transaction It is derived given the EDI Location Code and Translator on the Control Record 0010 Refer to the Trading Partner Section in the Oracle e Commerce Gateway Implementation Manual for details Original System Reference Data ORIG_SYS_DOCUMENT_REF See Definition above Update Columns CREATED _ BY This code identifies who loaded this transaction into the Order Import tables The code Application Transaction Detail 6 41 is set to the Requester ID associated with the concurrent manager request that processed this transaction CREATION_DATE This is the date that the e Commerce Gateway loaded the transaction into the Order Import table entries This date is set to the system date LAST_UPDATE_DATE This date is equal to the CREATION_DATE for this transaction This date is set to the system date LAST_UPDATED_BY This code is equal to the CREATED_BY code for this transaction OE_LINES_INTERFACE Table Configuration Data The following data elements must be entered for Configured items to show the relationship of line items in the file e TOP_LINE_MODEL_REF e LINE_TO_LINE_REF e MODEL_GROUP_NUMBER e OPTION_NUMBER e COMPONENT_CODE e SORT ORDER CALCULATE_PRICE_ FLAG This flag indicates to Order Import to calculate a price flag is Y or not calculate a price flag is N DEFAULT The code is set to Y
365. he type of exception encountered For example Oracle e Commerce Gateway would detect that the trading partner was not set up for a given transaction whereas the base Oracle Application API would detect a duplicate invoice The application s standard error handling functions are used to identify report and resolve errors Errors detected by the Translator are resolved by the error handling in that process Reoccurring data errors that originate from the sender should be discussed with the trading partner for permanent corrections EDI Translators The following section describes function performed by an EDI Translator in the processing of traditional EDI transactions The various standards for message formatting are both precise and potentially changing in addition there are many issues regarding the various addressing methods and communication protocols that may be used for the actual exchange of transactions A formatting and communications interface is therefore required between Oracle e Commerce Gateway and the external communications service This interface software is called the EDI Translator There are a number of specialist companies who operate in this area offering packages to address these requirements EDI Translators generally provide tools to map any interface data file format to any format including standard EDI transactions and messages so data mapping to a standard like SPEC2000 should not be an issue with most Translator pr
366. her INSTAT or EXSTAT e Movement Type either A for arrivals D for Dispatch AC for arrival adjustments or DC for dispatch adjustments 6 4 Oracle e Commerce Gateway Implementation Manual Oracle Order Management The following table shows the transactions that are delivered with Release 12 Oracle Order Management Transactions Transaction Direction Transaction ASC X12 EDIFACT Name Code Purchase Order Inbound POI 850 ORDERS Purchase Order Inbound POCI 860 ORDCHG Change Purchase Order Outbound POAO 855 ORDRSP Acknowledgmen t PO Change Outbound POCAO 865 ORDRSP Acknowledgmen t The topics covered for inbound transactions include the following The topics covered for outbound transactions include the following Trading Partner Link to Oracle e Commerce Gateway Oracle e Commerce Gateway Required Fields Review Oracle e Commerce Gateway Exceptions Resolve Oracle e Commerce Gateway Exceptions Relevant Oracle Order Management Profiles and Setup Steps Order Management Open Interface Required Fields Review Order Management Open Interface Exceptions Resolve Order Management Open Interface Exceptions Transaction Handling Options Trading Partner Link to Oracle e Commerce Gateway Application Transaction Detail 6 5 e Relevant Oracle Order Management Profiles and Setup steps e Extract Criteria e Columns Updated Upon Extraction Current Information The transaction requirements may change when enhancements
367. hipment within the PO Line One set of records per shipment within the PO Line One set of records per shipment within the PO Line One set of records per shipment within the PO Line One set of records per shipment within the PO Line The following table is a summary list of the records that comprise the Outbound Purchase Order transaction The table shows the functional data grouping of records the data level the record numbers and relevant notes about the data grouping A 12 Oracle e Commerce Gateway Implementation Manual POI Transaction Record Summary Data Data Level Record Number Note Control Record HEADER 0010 Basic Purchase Order HEADER 1000 Header Currency Code amp HEADER 1060 Conversion Rates Payment Amount HEADER 1070 Credit Card Payment Type Code Tax Exempt FOB Point Freight HEADER 1090 Terms Shipment Priority Shipping Method Shipping amp Packing HEADER 1100 Instructions Header Request Date HEADER 1110 Demand Class Header Flexfields HEADER 1200 1230 Flexfields PO Header Flexfields HEADER 1240 1270 Flexfields Global Header HEADER 1280 1320 Flexfields Flexfields Customer Name amp HEADER 1400 Flexfields Number Sold to Address HEADER 1410 Sold to Contact HEADER 1420 Ship to Address HEADER 1500 Header Level Transaction Summary Layouts A 13 Data Data Level Record Number Note Ship to Contact HEADER 1510 Header Level Invoice Address HEADER 1520 I
368. his column is the schedule generation date that is sent in the transmission EDI_CONTROL_NUM_1 EDI control number 1 is the control number from the outer electronic envelope that is used for auditing purposes This code such as the X12 ISA segment or the EDIFACT UNB segment is assigned by the customer s EDI translator EDI_CONTROL_NUM_2 EDI control number 2 is the second level control number from the electronic envelope that is used for auditing purposes This code such as the X12 GS segment is assigned by the customer s EDI translator EDI_CONTROL_NUM_3 EDI control number 3 is the third level control number that is used for auditing purposes Often the control number from the X12 Starting Transaction ST segment is used Transaction Detail Records Note The fields with the suffix INT are the internal codes that must be defined in the Oracle Release Management One to five external codes from the transaction may be entered into their corresponding external code fields that have the suffixes _EXT1 through _EXT5 for the same column name Either the e Commerce Gateway s Code Conversion process can derive the internal codes to place them in the open interface tables or the values may be placed in the internal code fields on the file if they are derived from another process Refer to the Code Conversion chapter for details Only the internal codes are referred to below for simplicity RLM_SCHEDULE_TYPE_INT This column represents
369. ically transmitted invoices before approving them for payment Use the Invoice Approvals window to define an invoice hold reason Refer to Oracle Payables User s Guide for details Payables Open Interface Required Fields The Payables Open Interface is used by the Inbound Invoice transaction It is used to validate the incoming data entered into the Payables Open Interface tables by the Oracle e Commerce Gateway import program The following is a list of the Payables Open Interface required fields These fields are required for the Payables Open Interface Import program to successfully process and move the data from the Payables Open Interface tables into the Oracle Payables base application tables Required fields noted as derived or hardcoded do not require a value in the transaction on the transaction interface file since the values are determined by the Oracle e Commerce Gateway process Refer to the Payables Open Interface Appendix section Oracle Payables User s Guide for details on derived defaulted and conditional fields see Cond items in the following tables AP_INVOICES_INTERFACE Table The table below lists the required fields for the AP_INVOICES_INTERFACE table Oracle Cond Oracle Hardcoded Record Position Applications e Commerce Derived Number Number Column Gateway Name for Column Required Name Fields INVOICE_N INVOICE_N 1000 10 UM UM Application Transaction Detail 6 83 Oracle Cond Oracle Har
370. ice TP_CD INVOIC 3020 A2 IH3 Header E Flexfiel ds 10 14 37 Invoice TP_CD INVOIC 3030 A2 IH4 Header E Flexfiel d15 38 Invoice TP_CD INVOIC 3040 A1 IH5 Header E Interfac e Flexfiel ds 1 4 39 Invoice TP_CD INVOIC 3050 A2 IH6 Header E Interfac e Flexfiel ds 5 9 A 194 Oracle e Commerce Gateway Implementation Manual Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner INVOIC ITEM TAX Number Layout Layout E Qualifie r 40 Invoice TP_CD INVOIC 3060 A2 IH7 Header E Interfac e Flexfiel ds 10 14 41 Invoice TP_CD INVOIC 3070 A2 IH8 Header E Interfac e Flexfiel d15 42 Invoice TP_CD INVOIC 3075 IV IV8 Header E Shippin 8 Instructi ons 43 Header TP_CD INVOIC 3080 AH AH1 Allowa E nce Cha rges 44 Header TP_CD INVOIC 3090 AH AH2 Allowa E nce Cha rges 45 Header TP_CD INVOIC 3091 AH IH1 Allowa E nce Cha rges Flexfiel ds 1 4 Transaction Summary Layouts A 195 Data Trading Partner Ref1 Ref2 INVOIC ITEM E Ref 3 TAX Record Number Record Layout Record Layout Qualifie r 46 47 48 49 50 51 Header Allowa nce Cha rges Flexfiel ds 5 9 Header Allowa nce Cha rges Flexfiel ds 10 14 Header Allowa nce Cha rges Flexfiel d15 Extensio n Tables Invoice Header Data Basic Line Data Sales Order Data Part Custom er Item Descript ion TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD INVOIC E INVOIC E INVOIC E
371. ice transaction The table shows the functional data grouping of records the data level the record numbers and relevant notes about the data grouping PYO Transaction Record Summary Type of Data Data Level Record Number 1 Control Record CHECK 0010 2 Trading Partner CHECK 0020 0050 Custom Header Attributes 3 Trading Partner CHECK 0060 0070 Custom Detail Attributes 4 Account Data CHECK 1000 5 Payment Data CHECK 1010 6 Vendor CHECK 1020 Flexfields Transaction Summary Layouts A 93 Type of Data Data Level Record Number 7 Bank CHECK 1030 Address Code 8 Bank Contacts CHECK 1040 9 Supplier Bank CHECK 1050 10 Vendor Site CHECK 1080 Address Code 11 Global ABA CHECK 1090 1130 Flexfields Attribute Flexfields 12 Global ABAS CHECK 1140 1180 Flexfields Attribute Flexfields 13 Global PVS CHECK 1190 1230 Flexfields Attribute Flexfields 14 Bill To Internal CHECK 1240 Address 15 VAT CHECK 1250 Registration 16 Extension CHECK 1900 custom Tables Payment Data 17 Remittance Invoi INVOICE 2000 ce Details 18 Remittance INVOICE 2010 2040 Flexfields Advice Flexfields A 94 Oracle e Commerce Gateway Implementation Manual Type of Data Data Level Record Number 19 Global INV INVOICE 2050 2090 Flexfields Attribute Flexfields Outbound Payment Order Remittance Advice Common Key The following table shows the Common Key positions 1 100 for the Outbound Payment Order Remittance Advice transaction The table
372. ide This guide describes how to set up Oracle Shipping to process and plan your trips stops and deliveries ship confirmation query shipments determine freight cost and charges to meet your business needs Oracle Release Management User s Guide This manual describes how to manage high volume electronic demand by continually incorporating your customers demand into your order and planning processes By explaining how to validate archive manage and reconcile incoming planning shipping and production sequence schedules with updates to sales orders and forecasts it enables you to electronically collaborate with your customers to more accurately manage demand It also describes how to plan create and manage trading partner layers for trading partner specific customizations Installation and System Administration Oracle Applications Concepts This book is intended for all those planning to deploy Oracle E Business Suite Release XV xvi 12 or contemplating significant changes to a configuration After describing the Oracle Applications architecture and technology stack it focuses on strategic topics giving a broad outline of the actions needed to achieve a particular goal plus the installation and configuration choices that may be available Oracle Applications Installation Guide Using Rapid Install This book is intended for use by anyone who is responsible for installing or upgrading Oracle Applications It provides instructio
373. ierarchy can be illustrated as follows Sales Organization Hierarchy Vision Corporation Vision USA Eastern Western Region Region To secure sales data within the company relevant operating units can be associated with predefined security profiles For example all sales data access privileges are grouped into the Vision Sales security profile USA Sales security profile is for USA related data and regional security profiles are for designated regional data System Vision UK administrators can associate these security profiles containing multiple operating units Trading Partner 9 17 with users through appropriate responsibilities Therefore sales supervisors can easily access sales data in the Eastern or Western region without changing their responsibilities The following diagram illustrates the relationship between security profiles responsibilities and operating units for this sales company Relationship Diagram Between Security Profiles Responsibilities and Operating Units Responsibility Security Profile Operating Unit Sales Manager Sales USA Sales Mision usA Supervisor Security Profile Eastern Region Western Region Sales Representative EDI Location Code in Multiple Organizations The Oracle e Commerce Gateway process limits its address site table search to base Oracle Application address column IDs defined with the same organization specified in the Oracle e Commerce Gateway res
374. ile Description Read write and execute permissions need to be established within Unix at both the file and directory levels Solution Make the appropriate permission changes using the Unix chmod command 8 4 Oracle e Commerce Gateway Implementation Manual Message Description and Solution Unable to derive a unique address due to ambiguous setup data Unable to derive the address ID for the given address Description This message appears in the View Staged Documents window and is a result of an import process exception The problem is due to a missing or incorrect data in the Oracle Application or the Oracle e Commerce Gateway that was insufficient to derive a unique customer site or supplier site This error occurred during address derivation that may have also used the name field from the transaction Address Precedence profile in the Profile Set Up section Solution Resolve the trading partner set up or change the address derivation option then resubmit the document from the View Staged Documents window Description This message appears in the View Staged Documents window and is a result of an import process exception The system was not able to determine the correct address based on address derivation process Usually the Translator Code and EDI Location Code in the transaction were not assigned to a single customer site or supplier site across organizations This may happen in a multi org environment
375. in Oracle Applications and the trading partner site definition in Oracle e Commerce Gateway This enables Oracle e Commerce Gateway to access the detailed data about the supplier or supplier site in the base Oracle Applications without maintaining the detail data in Oracle e Commerce Gateway To ensure that the trading partner link between Oracle e Commerce Gateway and Oracle Applications is set up properly verify that the supplier supplier site and the EDI Location Code in Oracle Applications is the correct supplier supplier site selected for Application Transaction Detail 6 121 the Trading Partner definition in Oracle e Commerce Gateway The selected supplier supplier site and the EDI Location Code defined in Oracle Applications are displayed in the Define Trading Partners window Assignment tab If the data is not what you intend it to be you must make the appropriate changes for the transaction to be extracted for the correct trading partner This could involve either altering the supplier supplier site in the base Oracle Application or assigning a different supplier supplier site to that EDI Location Code in Oracle e Commerce Gateway Please note that if the trading partner is associated with multiple operating units then the transaction to be extracted is for a specified operating unit only linked to your responsibility To extract all the data for multiple operating units you still need to execute the program one by one by specifying dif
376. increments of 1000 The following table shows sample record numbers and levels Record Structure Record Content Number 0010 Control Record 0020 0070 Oracle e Commerce Gateway Flexfields 1000 1999 Application Header Level 2000 2999 Application Detail Level 3000 3999 Application Next Detail Level 4000 4999 Application Next Detail Level Sample Record Numbers and Levels The exact record number blocks varies by transaction due to variations in the data required However the hierarchy remains the same Large transactions may have any level span over several blocks of 1000 For example the header level may span from 1000 to 3999 and the item level may span from 4000 to 5999 Transaction Interface File Architecture 5 5 Sample File Structure The following table illustrates the record number range and levels of data for a sample transaction Sample File Structure Data Type Data Level Record Number Position 92 95 Control Record CONTROL 0010 Trading Partner Header TRADING PARTNER 0020 0050 Flexfields Trading Partner Detail TRADING PARTNER 0060 0070 Flexfields Bill To Address Code HEADER 1000 Bill to Misc Data Contacts HEADER 1010 Bill to Customer Flexfields HEADER 1020 1050 Bill to Site Flexfields HEADER 1060 1090 Ship to Address code HEADER 1100 Ship to Misc data contacts HEADER 1110 Ship From Codes HEADER 1400 Basic Header Data HEADER 2000 Amount Data HEADER 2010 Currency Data Misc dat
377. indicates there are no eligible documents to be extracted Columns Updated Upon Extraction Once an eligible credit memo or debit memo is successfully extracted and written to the transaction interface file it is marked by Oracle e Commerce Gateway to prevent it from subsequent extraction The following table lists the fields updated in the RA_CUSTOMER_TRX table based on an excerpt of code in the UPDATE_AR procedure defined in the ECECDMOB pls file Column Value Updated To EDI_PROCESSED_FLAG Y EDI_PROCESSED_STATUS ED LAST_UPDATE_DATE SYSDATE PRINTING_COUNT increment 1 PRINTING_LAST_PRINTED SYSDATE PRINTING_ORIGINAL_DATE SYSDATE PRINTING_PENDING N Oracle Release Management The implementation of any transaction requires some set up in Oracle Applications and Oracle e Commerce Gateway This section focuses on the application setups necessary to implement a transaction that integrates with Oracle Release Management The Oracle Release Management transactions are listed in the following table Application Transaction Detail 6 133 Oracle Release Management Transactions Transaction Direction Transaction ASC X12 EDIFACT ODETTE Name Code Planning Mat Inbound SPSI 830 DELFOR DELINS erial Release Shipping Inbound SSSI 862 DELJIT DELINS Schedule CALDEL KANBAN Production Inbound PSQI 866 DELJIT SYNCRO Sequence SYNPAC Schedule The topics covered for inbound transactions include the following Trading Partner
378. ine 1 6 Business Entity 35 N302 Address Line 2 7 Business Entity 35 N301 Address Line 3 8 Business Entity City 30 N401 9 Business Entity Postal 15 N403 Code 10 Business Entity 20 Country Internal 11 Business Entity 03 N404 Country ISO External 12 Business Entity 25 REGION 1 Internal 13 Business Entity 10 N402 REGION 1 External 14 Business Entity 25 REGION 2 Internal 15 Business Entity 10 N402 REGION 2 External 16 Business Entity 25 REGION 3 Internal 17 Business Entity 10 REGION 3 External Contact Format 1 CN Record Layout The following table shows the record layout of the record layout code CN 5 28 Oracle e Commerce Gateway Implementation Manual Contact Record Format 1 You may add secondary contact data to this record Contact Format 1 CN Record Layout Seq Business Entity Contact Data Length ASC X12 10 Common Key including Record Number Business Entity Primary Contact Last Name Business Entity Primary Contact First Name Business Entity primary Contact Job Title Business Entity Primary Area Code 1 Business Entity Primary Telephone 1 Business Entity Primary Area Code 2 Business Entity Primary Telephone 2 Business Entity Primary Area Code 3 Business Entity Primary Telephone 3 100 35 35 40 10 60 10 60 10 60 PERO2 PERO9 PERO4 PERO4 PERO4 PERO4 PERO4 PERO4 Contact Format 2 CM Reco
379. ing 1 Verify that the invoices you wish to pay electronically are defined with Electronic as the payment method 2 Verify that the invoices you wish to pay do not have active holds placed on them 3 Approve the invoices you wish to pay 4 Verify that you have confirmed the default remit to bank account for each scheduled payment 5 Create a Pay Group type lookup specifically for EDI payments to separate the non EDI payments from the EDI payments This is an optional set up step 6 Create the Payment Batch Refer to Oracle Payables User s Guide Initiating Payment Batches section for the details 7 Refer to Oracle Payables User s Guide Modifying Payment Batches section for details on how to modify a payment batch if necessary 8 Format the Payment Batch This process initiates the Oracle e Commerce Gateway outbound Payment Order Remittance Advice transaction that creates a transaction interface file Extract Criteria The outbound Payment Order Remittance Advice transaction is controlled by two database views that are defined according to the Oracle Payables data model for payments and their corresponding invoices The two views contain variables which are Application Transaction Detail 6 93 dynamically set based on your responses to the extract program parameters refer to Oracle e Commerce Gateway User s Guide Outbound Transactions chapter for a list of the program parameters The two database views are as fo
380. ing the correct trading partner EDI Location Code for the control record 0010 for the transaction in the transaction interface file Application Transaction Detail 6 181 Relevant Oracle Application Profiles and Setups Use Oracle Supplier Scheduling Scheduler s Workbench to create shipping schedules Oracle Supplier Scheduling will gather the supply and demand data from Oracle Purchasing and Oracle Planning Refer to the Oracle Purchasing Planning and Supplier Scheduling User s Guide for necessary profile set ups related to Purchasing MRP MPS and DRP There are no specific profile options that control how the shipping schedules are extracted Shipping Schedule Extract Options Extract Criteria The following table lists the shipping schedule extract options The table lists the Oracle Applications Product the process and the method Oracle Applications Process Method Product Supplier Scheduling Scheduler s Workbench for Event Driven manually created schedules Supplier Scheduling AutoSchedule for Event Driven automatically created schedules Oracle e Commerce Gateway Outbound Shipping Schedule Concurrent Manager Request Transaction Since the purpose of the Shipping Schedule is to work closely with your suppliers to get the right materials to the right place at the right time the most expeditious option is to transmit the shipping schedules at the time the schedule is created in the Scheduler Workbench or via Aut
381. input archive Directory the translator archives each file as it successfully translates it D outbound_flat_file Translator_output This is where the translator writes its outbound transaction files D outbound_flat_file communication This is where the communication process looks for files that are ready to be sent D outbound_flat_file communication archive This is where the communication process copies files it has successfully transmitted Inbound Directory Structure A sample set of directories and files are listed below D inbound_flat_file communication This is where the receiving communication process deposits the incoming file Once the communication process finishes the file s are copied to the following file D inbound_flat_file translator_input This is the directory where the translator looks for its input Again the translator generally gets all files in the directory Once it successfully translates a given file it copies it to the following file D inbound_flat_file translator_input archive D inbound_flat_file translator_output Implementation Details 4 35 This is where the translator writes the translated file When the translation run is complete for all files in the translator_input directory the files are copied into the following file D inbound_flat_file Gateway_input This is where the Oracle e Commerce Gateway looks for transaction interface files to process It should be defined in UTL
382. ins valid values Review this using the Oracle e Commerce Gateway Interface File Data Report Testing the Inbound Transaction Perform the following for inbound transactions Initiate the inbound transaction and enable run time execution log debug parameter to HIGH or MEDIUM to monitor the import process Specify valid values for the program parameters refer to Oracle e Commerce Gateway User s Guide for the parameter list When the import process completes review the Concurrent Request Log and report for detected exceptions If the import process failed Oracle e Commerce Gateway validations use the Oracle e Commerce Gateway View Staged Documents window to review Oracle e Commerce Gateway exceptions If the import process failed Oracle Application Open Interface API validations use the Oracle Applications report to review the exceptions If the exceptions are due to set up errors in Oracle e Commerce Gateway or Oracle Applications make the necessary corrections and submit the transaction for reprocessing Test Transactions 7 3 e If the exceptions are due to invalid data from the Trading Partner request a new transaction interface file containing the corrected transactions Delete the exceptions using Oracle e Commerce Gateway View Staged Documents window and then re import the new file e Continue to initiate the import process review exceptions resolve exceptions and re process the transaction until the transaction complete
383. interpreted in context of its Detail Type and Detail Subtype Valid Values e ACTUAL e CUMULATIVE ITEM_DETAIL_QUANTITY This column represents the requested quantity The following table lists the ITEM_DETAIL_QUANTITY values for corresponding ITEM_DETAIL_TYPE If ITEM_DETAIL_TYPE Equals then ITEM_DETAIL_QUANTITY contains 0 1 2 Demand Quantity 3 Authorization Quantity 4 Shipped Received or CUM Quantity 5 Miscellaneous Quantity such as Ahead Behind or Inventory Balance 6 142 Oracle e Commerce Gateway Implementation Manual UOM_CODE_INT_D This is the abbreviated unit of measure codes defined in Oracle Inventory Code Conversion Categories Interface Tables Oracle e Commerce Gateway provides seeded Code Conversions for external values associated with the standards for values that are supported within the Demand Processor The following Code Conversion Categories are applicable to any or all of the inbound demand schedule transactions Code Conversion Categories Data Demand Processor Column Name Date Type RLM_DATE_TYPE Detail Type RLM_DTL_TYPE Detail Subtype RLM_DTL_SUBTYP Quantity Type RLM_QTY_TYPE Schedule Type RLM_SCHED_TYPE Purpose Code RLM_TRX_PURP Ship Delivery Pattern RLM_SHP_DEL_CODE Unit of Measure UOM The e Commerce Gateway transaction has four levels of data The Demand Processor has two interface tables one for the Header level data and one for the Line level data The Line
384. into the application open interface tables for inbound transaction Most descriptive flexfields are defined to a shorter length on the transaction interface file than they are defined in the application due to realistic length on most business data Any field may be increased up to its maximum length defined in the base Oracle application You can assign a different record number to the flexfield if the maximum length of the record is attained See the Interface File Definition section in the Oracle e Commerce Gateway User s Guide for details Interface Data File Structure Each data file consists of several records Each record has two sections the common record key positions 1 100 and the application data area positions 101 to 1024 The structure is shown in the following table Interface Data File Structure Data Position Length Data Section Translator Code 1 25 25 Common Key short Key 1 Document 26 47 22 Common Key identifier Key 2 48 69 22 Common Key Key 3 70 91 22 Common Key 5 4 Oracle e Commerce Gateway Implementation Manual Data Position Length Data Section Record Number 92 95 4 Common Key Record Layout 96 97 2 Common Key Record Layout 98 100 3 Common Key Qualifier Application Data 101 101 1024 up to 924 Application Area 1024 Record Structure Each record is referenced by a number that identifies the level and block of data in the data file The numbering scheme for each level is usually in
385. iolations window and displays the Troubleshooting 8 15 process exceptions for the given document The Columns button opens the Column Violations window and displays the column exceptions for the given level of the document The Process Violations window displays the following data Transaction Map Document Number Message Ignore Check Box Transaction type and the translated transaction type name The map code for the transaction The primary identifier for the document in the staging table The value depends on the transaction i e POI has the PO Number INI has the Invoice Number The process exception text When this box is checked it gives users the ability to ignore the violated rule when resubmitting the document This is the only field that can be modified in this window The Column Violations window displays each column of the selected level in the given document and the number of exceptions for the column The users have the ability to only show columns with exceptions or all columns by selecting the appropriate combination box This window displays the following data Transaction Map Document Number Level Column Name Transaction type and the translated transaction type name The transaction map code The primary identifier for the document in the staging table The value depends on the transaction such as POI has the PO Number INI has the Invoice Number Text desc
386. ion Category Required Default Value ECE ATT_SPLIT_WO RD_ALLOWED ECE IN_FILE_PATH This profile Functional Yes option is used for attachments to the Purchase Order Outbound and Purchase Order Change Outbound transactions A value of Yes indicates words in attachments are split when the segment size is reached No indicates that words are not split A new line is created after a space ora punctuation mark Indicates the directory where inbound data files are expected This value must match the actual directory on the disk and that is designated in the INIT ORA file Deployment Yes No Default No Default For more profile category information see Oracle Applications System Administrator s Guide Maintenance for details System Profile Window Note For system profile options related to directory paths refer to Define UTL_FILE_DIR Parameter in INIT ORA File for the details 4 6 Oracle e Commerce Gateway Implementation Manual Transaction Profiles Ongoing as transactions are implemented Transaction profiles are categorized as follows e Address precedence for each inbound transaction e Enable disable flag for each transaction e Transaction specific options Transaction Profile Option Transaction Description Category Required Default Value Profile Option ECE_XXX_ADD_ Enable Address Functional Yes LOC RESS_PRECED Precedence for ENCE transaction where XXX represents a
387. ion Code on record 0010 element 80 combination The Purchasing Documents Open Interface uses the supplier ID to derive the supplier name and number VENDOR_DOC_NUMBER This column represents the supplier s catalog number as the supplier may not know your Oracle catalog number The supplier s catalog number is used to locate an existing catalog for catalog replacement or update If you are importing a new catalog this column is used to verify that the catalog is not a duplicate 6 102 Oracle e Commerce Gateway Implementation Manual PO_LINES_INTERFACE Table The following table lists the required fields for the PO_LINES_INTERFACE table Oracle Cond Oracle Hardcoded Record Position Application e Commerce Derived Number Number Column Gateway Name for Column Required Name Fields LINE_NUM Yes LINE_LNUM 2000 10 ITEM ITEM 2000 20 QUANTITY Yes QUANTITY 2010 10 EFFECTIVE_ Yes EFFECTIVE_ 2010 60 DATE DATE EXPIRATIO Yes EXPIRATIO 2010 70 N_DATE N_DATE ITEM_DESC Yes ITEM_DESC 2010 80 RIPTION RIPTION UNIT_PRICE Yes UNIT_PRICE 2020 10 SHIPMENT_ Yes SHIPMENT_ 2050 10 NUM NUM INTERFACE _ INTERFACE_ Derived LINE_ID LINE_ID INTERFACE _ INTERFACE__ Derived HEADER_ID HEADER_ID EFFECTIVE_DATE This column is required if you want to create sourcing rules i e if you answered YES to Create Sourcing Rules parameter along with importing a catalog Whether a new sourcing rule is created or an existing rule is updated depends
388. ion TP_CD PO 1950 AC ACT Data A 46 Oracle e Commerce Gateway Implementation Manual Sequen ce Data Trading Partner Ref 1 Ref 2 Ref 3 Record Number Record Layout Record Layout Qualifie r 52 53 54 55 56 57 58 Actions Flexfiel ds 1 4 Actions Flexfiel ds 5 9 Actions Flexfiel ds 10 14 Actions Flexfiel d15 Item Data Origina 1 System Referen ce Configu ration Data Inventor y Item Segmen ts 1 10 Inventor y Item Segmen ts 11 20 TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD PO PO PO PO PO PO PO 1960 1970 1980 1990 LINE 2000 LINE 2010 LINE 2020 Al A2 A2 A2 IT IT IT ACI AC2 AC3 AC4 ITM IS1 IS2 Transaction Summary Layouts A 47 Sequen ce Data Trading Partner Ref 1 Ref 2 Ref 3 Record Number Record Record Layout Layout Qualifie r 59 60 61 62 63 64 65 66 A 48 Oracle e Commerce Gateway Implementation Manual Operati on Code Price Quantiti es List Price Change Data Change Comme nt 1 Change Comme nt 2 Change Comme nt 3 Change Comme nt 4 Custom er Paymen t Terms Tax Exempt Project Task Contrac t Number s TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD PO PO PO PO PO PO PO PO LINE LINE LINE LINE LINE L
389. ion as an example the process flow described above is illustrated as follows Outbound Purchase Order Transaction Process Flow Oracle e Commerce Gateway ECE_PO_INTERFACE_HEADERS ECE_PO_INTERFACE HEADERS x _PO_INTERFACE_HEASDERS_X ECE_OUTPUT Oracle Purchasing are ECE_PO_INTERFACE_LINES Gateway Extract Program Oo ECE_PO_INTERFACE_LINES_X Extension Extract ECE_PO_INTERFACE_SHIPMENTS Program Custom eae _PO_INTERFACE_SHIPMENTS_X POO Data F latfile Other Data Source EDI Translator Steps for Extensible Architecture The Oracle e Commerce Gateway uses interface tables extension tables packaged procedures and setup tables to create interface data files for outbound EDI transactions The setup process to use the Extensible Architecture in the Oracle e Commerce Gateway is a three step process as follows 1 Define the columns in the extension table Task Add the desired new column s to the appropriate extension table 2 Define data positions in the outbound interface file Task For each new column added to the extension table step 1 above insert a record into ECE_INTERFACE_ COLUMNS to position the data element in the Extensible Architecture 11 5 interface file 3 Modify procedures to move the external source data to the extension tables Task Modify the appropriate procedure in the extension package body to populate the new column s with data Check the O
390. ion in the pl sql table ece extract_utils pub ext get value 1_plsql table extension column _name p_position o value e 1 plsql_table is the name of pl sql table this comes as a parameter to extension procedure such as ece poo x populate ext line e extension column_name is the extension column name e p position stores the position of the column in the pl sql table number datatype e o value is the value in the column varchar2 datatype It is not used but to pass a dummy variable e Use the p position from previous procedure to insert value into the pl sql table ece extract_utils pub ext insert value 1_plsql table p_position p_value e 1 plsql_table is the name of the pl sq table e p position is the position found from the ext_get_value e p value is the value to be inserted varchar2 datatype Please 11 16 Oracle e Commerce Gateway Implementation Manual convert p_ value to varchar2 datatype before inserting the value The Procedure For Transactions Other Than POO and POCO PROC EDUR IS ae ae Kk v_ItemI v_ItemIDPosition BEGIN k k k k us Kk Kk aA D th E Populate 1_fkey I Extension Line N NUMBER l_plsql_table IN ece_flatfile_PVT interface_tbl_type INT INT H Q valu Hi Hi ece_flatfile_PVT find pos kxk K kxk v_ItemI kxk XRY An D to TO_NUMB
391. ions is essential in the case of disputes investigations or legal action The other purpose of archiving is to be able to re transmit outbound transactions to trading partners if necessary But whatever the reason or the transaction s involved archiving should apply to both inbound and outbound transactions Transactions may be processed through the Oracle e Commerce Gateway several times per day Each time the extraction process is executed an output file name must be provided to the Concurrent Request To preserve each of these output files separately a unique name is generated with each run The application generates a default file name that starts with the transaction code or you may enter your own file name Another place the archiving is handled is in the translator Almost all translators archive the files they create either immediately after creation or after an attempted transmission whether successful or not Some translators may handle archiving the input file from the Oracle e Commerce Gateway However this only removes the need for the preceding step if the translator is run immediately after the extraction every time For outbound transactions it may also be necessary to designate the directories where a file will be placed by the Oracle e Commerce Gateway archived from the Oracle e Commerce Gateway picked up by the translator for processing output by the translator archived from the translator or picked up by the communicati
392. is Trading Partner specific If there are many Trading Partners 10 24 Oracle e Commerce Gateway Implementation Manual needing separate entries it may be desirable to assign another document standard to group set of Trading Partners though it is not really their true document standard Recall that Document Standard Code exist to facilitate the code conversion table entries If you choose the strategy in the table below you need a set of code conversion value codes with the direction IN for inbound transactions since direction BOTH could not be used because of duplicate internal codes In the table below the columns Category Direction Key 1 Key 2 External Code 1 and External Code 2 comprise the search key for the inbound transaction This search key must be unique The column Internal Code is the data retrieved for the Application Open Interface Tables Example of Code Conversion for Inbound Transaction Category Direction Key 1 Key 2 External External Internal search search search search Code 1 Code 2 Code key key key key search search key key retrieve d data 1 UOM IN EA Each 2 UOM IN PC Each 3 UOM IN X12 EA Each 4 UOM IN X12 PC Each Note For direction IN the External code is part of the entire search key Multiple Codes within a Standard converting to the Same External Code In the table above there is no need for table entries with OTHER in search key 1 For the inbound transactions t
393. l Record 0010 Layout Seq Data Length Position Sample Sample Element Inbound Outbound Transaction Transaction Data Data 01 Translator 25 1 25 A1 ACME 2 A1 ACME 1 Code short 02 Key 1 may 22 26 47 123456789012 64564522 be truncated 3 03 Key 2 22 48 69 04 Key 3 22 70 91 05 Record 4 92 95 0010 0010 Number 06 Record 2 96 97 CT CT Layout 07 Record 3 98 100 CTL CTL Qualifier 08 Communicati 2 101 102 ED ED on Method 09 Test Flag 1 103 P T 10 DocumentID 6 104 109 POI POO 11 Document 5 110 114 STAND BLANK Type 12 Document 2 115 116 OR CH Purpose Code 5 8 Oracle e Commerce Gateway Implementation Manual Seq Data Length Position Sample Sample Element Inbound Outbound Transaction Transaction Data Data 13 Document 35 117 151 123456789012 64564522 Code full 3 14 Translator 30 152 181 A1 ACME 2 A1 ACME 1 Code full 15 TP Location 35 182 216 AC7654 AC9832 Code External 16 Trading 74 217 290 ACME CORP ACME INC Partner Description 17 TP Reference 80 291 370 1234 1 18 TP Reference 80 371 450 9875 2 19 Transaction 15 451 465 19970616 19970626 Date Time 230723 20 Transmission 15 466 480 534342 Run ID 21 Organization 15 see Note Not ID page 5 10 applicable below 22 Document 10 see Note Standard page 5 10 below 23 Control 10 see Note 654 not Number 1 page 5 10 applicable below Transaction Interface File Architecture 5 9 Seq Data Length Position Sample Sample Element Inbound Ou
394. l code conversion in the code conversion table To create any full search key in the code conversion value window the data elements that comprise it come from the sources shown in the following table Full Search Key Component Source Code Conversion Category Defined in the Code Conversion Categories window Then user assigned to a specific data element in a transaction in the Assign Categories window 10 8 Oracle e Commerce Gateway Implementation Manual Full Search Key Component Source Direction Keys 1 5 Internal code inbound transactions Internal code outbound transactions External codes 1 5 inbound transactions External codes 1 5 outbound transactions External codes 1 5 outbound transactions This is the transaction direction that is accessing the code conversion table entry It is part of the full search key It determines if the table entry will be read for the inbound or outbound transactions or transactions in both directions The values are IN for inbound transactions OUT for outbound transactions and BOTH for both inbound and outbound transactions User determined data that limits to what the code conversion value applies Usually it is limited to a Trading Partner site No keys indicated means that the table entry applies to all Trading Partners This is the data defined or recognized by the Oracle application It is usually data found in the code conversion value t
395. l data field to Oracle e Commerce Gateway The EDI Location Code is the link between a customer customer site in Oracle Applications and the trading partner site definition in Oracle e Commerce Gateway This enables Oracle e Commerce Gateway to access the detailed data about the customer or customer site in the base Oracle Applications without maintaining the detail data in Oracle e Commerce Gateway To ensure that the trading partner link between Oracle e Commerce Gateway and Oracle Applications is set up properly verify that the customer customer site and the EDI Location Code in Oracle Applications is the correct customer customer site selected for the Trading Partner definition in Oracle e Commerce Gateway The selected customer customer site and the EDI Location Code defined in Oracle Applications are displayed in the Define Trading Partners window Assignment tab If the data is not what you intend it to be you must make the appropriate changes for the transaction to be extracted for the correct trading partner This could involve either altering the customer customer site in the base Oracle Application or assigning a different customer customer site to that EDI Location Code in Oracle e Commerce Gateway Please note that if the trading partner is associated with multiple operating units then the transaction to be extracted is for a specified operating unit only linked to your responsibility To extract all the data for multiple operating
396. l to TP_CD INVOIC 1090 A2 BS4 Site E Flexfiel d15 19 Shipto TP_CD INVOIC 1100 AD ST1 Address E Code 20 Shipto TP_CD INVOIC 1110 CM ST1 Misc E Data Contact s 21 Ship to TP_CD INVOIC 1115 RF ST1 Misc E Data Contact s 22 Soldto TP_CD INVOIC 1200 AD SO1 Address E Code 22 Soldto TP_CD INVOIC 1210 CM SO1 Misc E Data Contact 23 Soldto TP_CD INVOIC 1215 RF SO1 TP E Referen ce A 192 Oracle e Commerce Gateway Implementation Manual Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner INVOIC ITEM TAX Number Layout Layout E Qualifie r 24 Remitto TP_CD INVOIC 1300 AD RE1 Address E Code 25 Remitto TP_CD INVOIC 1315 RF RE1 TP E Referen ce 26 Ship TP_CD INVOIC 1400 SF SF1 From E Codes 27 Basic TP_CD INVOIC 2000 IV IV1 Invoice E Header Data 28 Invoice TP_CD INVOIC 2010 IV Iv2 Amount E Data 29 Invoice TP_CD INVOIC 2020 IV IV3 Misc E Data 30 Shipme TP_CD INVOIC 2030 IV IV4 nt Data E 31 Currence TP_CD INVOIC 2040 IV IV5 y Data E Shippin g Data Miscella neous Data 32 Paymen TP_CD INVOIC 2050 IV IV6 t Terms E Data Transaction Summary Layouts A 193 Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner INVOIC ITEM TAX Number Layout Layout E Qualifie r 33 Sales TP_CD INVOIC 2060 IV IV7 Represe E ntative Comme nts 34 Invoice TP_CD INVOIC 3000 Al TH1 Header E Flexfiel ds 1 4 35 Invoice TP_CD INVOIC 3010 A2 TH2 Header E Flexfiel ds 5 9 36 Invo
397. lan to use this feature you should deactivate the records that are associated to this table If you do not deactivate the records errors will occur in the Order Import validation because the records will be incomplete ORDER_SOURCE_ID This code identifies that the transaction was loaded into Order Import via the e Commerce Gateway Original System Reference Data Update Columns ORIG_SYS_DOCUMENT_REF ORIG_SYS_LINE_REF ORIG_SYS_SHIPMENT_REF See Definition above CREATED_BY Application Transaction Detail 6 47 This code identifies who loaded this transaction into the Order Import tables The code is set to the Requester ID associated with the concurrent manager request that processed this transaction CREATION_DATE This is the date that the e Commerce Gateway loaded the transaction into the Order Import table entries This date is set to the system date LAST_UPDATE_DATE This date is equal to the CREATION_DATE for this transaction This date is set to the system date LAST_UPDATED_BY This code is equal to the CREATED_BY code for this transaction Review Order Management Open Interface Exceptions At the completion of the Order Management Open Interface Order Import program the orders with exception can be viewed in the Order Import window Refer to the Oracle Order Management User s Guide for details Resolve Order Management Open Interface Exceptions There are three ways to resolve Order Management Open
398. lds 1 4 Pricing TP_CD Flexfields 5 9 Pricing TP_CD Flexfield 10 Industry TP_CD Header Flexfields 1 4 Industry TP_CD Header Flexfields 5 9 Ref 1 PO PO PO PO PO PO PO PO PO Ref 2 LINE LINE LINE LINE LINE LINE LINE LINE LINE Ref 3 Record Number 4310 4320 4330 4340 4400 4410 4420 4500 4510 Record Layout A2 A2 A2 A2 Al A2 A2 Al A2 Record Layout Qualifier GL2 GL3 GL4 GL5 PCI PC2 PC3 IN1 IN2 A 26 Oracle e Commerce Gateway Implementation Manual Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner Number Layout Layout Qualifier Industry TP_CD PO LINE 4520 A2 IN3 Header Flexfields 10 14 Industry TP_CD PO LINE 4540 A2 IN4 Header Flexfields 15 19 Industry TP_CD PO LINE 4540 A2 IN5 Header Flexfields 20 24 Industry TP_CD PO LINE 4550 A2 IN6 Header Flexfields 25 29 Industry TP_CD PO LINE 4560 A2 IN7 Header Flexfield 30 Service TP_CD PO LINE 4600 A1 SV1 Flexfields 1 4 Service TP_CD PO LINE 4610 A2 SV2 Flexfields 5 9 Service TP_CD PO LINE 4620 A2 SV3 Flexfields 10 14 Service TP_CD PO LINE 4630 A2 SV4 Flexfield 15 Transaction Summary Layouts A 27 Data Trading Partner Return TP_CD Flexfields 1 4 Return TP_CD Flexfields 5 9 Return TP_CD Flexfields 10 14 Return TP_CD Flexfield 15 Ship to TP_CD Address
399. le such as 830 862 866 DELFOR MANUAL PROCESS_STATUS Indicates the current processing status of a record Valid Values 1 Do not process 2 Waiting to be processed 3 In process 4 Error 5 Processed 6 Processed with errors REQUEST_ID This column represents a sequence generated unique identifier assigned to the concurrent request for the demand processor Update Columns CREATED_BY This code identifies who loaded this transaction into the Demand Processor tables The code is set to the Requester ID associated with the concurrent manager request that processed this transaction CREATION_DATE This is the date that the e Commerce Gateway loaded the transaction into the Demand Processor table entries This date is set to the system date LAST_UPDATE_DATE 6 152 Oracle e Commerce Gateway Implementation Manual This date is equal to the CREATION_DATE for this transaction This date is set to the system date LAST_UPDATED_BY This code is equal to the CREATED_BY code for this transaction RLM_INTERFACE_LINES Table The following table lists the required fields for the RLM_INTERFACE_LINES table Required Fields for RLM_INTERFACE_LINES Table Oracle Cond Oracle Hard coded Record Position Applications e Commerce Derived Number Number Column Gateway Name for Column Required Name Fields ITEM_DETAI 4000 010 L_TYPE_INT ITEM_DETAI 4000 070 L_SUBTYPE_ INT DATE_TYPE 4000 130 _CODE_INT STAR
400. le E Commerce Gateway interface file to be able to assist with Translator software mapping Implementers must be familiar with codes qualifiers that are used to identify data elements in an EDI transaction Understand Characteristics of the EDI Transaction Implementers must be familiar with the characteristics of an EDI transaction Implementation Positioning 2 1 For example the ASC X12 standard Purchase Order 850 transaction has a three level structure Header Item and Shipments The Oracle Order Management Order Import open interface has a two level structure header and the combined Item Shipments Each combination of the Item and Shipment in the transaction must be combined to create an item record in the transaction interface file Understand the Data Mapping Requirements Implementers should review the client s data mapping requirements to identify elements for which there is no corresponding field in the Oracle E Commerce Gateway transaction interface file For example the Trading Partner may send data at the detail line level in a purchase order transaction that identifies their warehouse bin bulk location The Trading Partner requires the supplier to print this data on a label and apply the label to each carton associated with the detail line item This carton label facilitates the Trading Partner s receiving process If necessary it is recommended that the EDI implementation team include an application specialist in the relev
401. le e Commerce Gateway Transaction Testing Create test acceptance criteria to test the transactions 2 6 Oracle e Commerce Gateway Implementation Manual Bear in mind that each trading partner may have its own requirements and therefore one size may not fit all Customization may extend to a lower level than just the transaction type This may increase the time required for both development and testing Trading partner and customer are not synonymous For example if a chain of ten retail stores allows each store to require some sort of different data on a transaction then there are ten trading partner data maps not one data map Another example is a trading partner in California where the state may require additional hazardous material data for shipping First test internally to validate initial mapping conversions settings and interaction between the Oracle e Commerce Gateway and Translator e g e Interface file testing into out of the Oracle e Commerce Gateway e Interaction testing to from the Translator e Interaction testing along the path between the applications and the Translator output input e Verify and compare the data passed to from the applications with the EDI transaction file into out of the Translator Nominate test Trading Partners for the initial transaction outbound inbound and obtain their agreement to be test sites Where the number of trading partners is large it may be necessary to take a phase testing appr
402. led This action temporarily disables the rule until you reactivate it by assigning an appropriate rule action Rule Action Precedence Since a given data column can have more than one rule defined for it it implies that there can be more than one rule action defined for it If this occurs the exception Implementation Details 4 17 handler applies the rule actions beginning with most conservative to least conservative as follows 1 Abort Run 2 Skip Document 3 Log Only Exception Handler Once the validation rules and associated actions are defined and the process is initiated the run time execution engine proceeds according to your validation rules The status of a transaction process and any detected exceptions may be viewed using a single workbench style window known as the View Staged Documents window Summary or detailed inquiries are available to help you analyze the cause of an exception If necessary a user activated run time execution log is available to assist with trouble shooting This diagnostic tool supports multiple levels of trace details for both technical and non technical analysts Refer to Troubleshooting chapter for details on how to use the Run time Execution Log and View Staged Documents window s to research any detected exceptions Once the cause of an exception is identified and resolved you have the option to resubmit the transaction for processing ignore the exception or delete the transaction
403. les CUSTOMER_ITEM_NAME if sent that has Ordered Item the customer item or generic item Always a validated INVENTORY_ITEM If Inventory Item the internal item only the supplier item was sent it is the inventory item if it is valid otherwise it is the derived supplier item Be sure to modify any form s folder to display both the Ordered Items and the Inventory Item Miscellaneous Item Data ITEM_REVISION on Record 2000 The following item revision fields are for display only These fields are not used in the Inventory tables to look up the Supplier Item for the order in Oracle Order Management e Customer Item Revision CUSTOMER_ITEM_REVISION The customer s item revision level as defined in the customer s purchasing application e Supplier Item Revision ITEM_REVISION The supplier s item revision level as defined in the supplier s order management application If the customer has multiple revisions to the base item that translates to different supplier items then the customer item defined in Oracle Inventory should consist of the base item reference concatenated with the revision number reference See illustration below Base Customer Item Customer Item Customer Item into Supplier Item in in Purchasing Revision in Order Management Oracle Inventory Purchasing defined in Oracle Inventory 86420 03 86420 03 98765 86420 04 86420 04 98799 Application Transaction Detail 6 61 To return the base customer ite
404. level interface table is loaded with both the item data schedule detail and schedule subdetail data from the e Commerce Gateway transaction This structure is shown in the table below For each 4000 record level data that is loaded into the Line level interface table the corresponding 2000 record data will also be loaded Schedule subdetail data may also be in the transaction For each 5000 record level data that is loaded into the Line level interface table the corresponding 2000 record level data and 4000 record level data will also be loaded to create a single entry in the Line level interface table Application Transaction Detail 6 143 Record Subrecord Subrecord e Commerce Demand Gateway File Processor Data Content Level Four Levels of Two Levels of Data Data HEADER and LINE 1000 Schedule Header HEADER 2000 Item1 data Copy data to all its Schedule Detail below 2000 4000 Schedule1 data LINE for first Item1 Schedule schedule 1 2000 4000 Schedule2 data LINE for second Item1 Schedule schedule 2 2000 4000 Schedule3 data LINE for third Item1 Schedule schedule 3 2000 Item2 data Copy data to all its Schedule Detail below 2000 4000 Schedulel detail Copy schedule for first for its subdetail schedule data below 2000 4000 5000 Schedule1 LINE subdetaill Item2 Schedule 1 subdetail1 2000 4000 5000 Schedule1 LINE subdetail2 Item2 Schedule 1 subdetail2 2000 4000 5000 Schedule1 LINE subdetail3 Item2
405. lexfiel ds Plannin 8 Schedul e Header Plannin 8 Schedul e Header TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD PS PS PS PS PS PS PS 0030 0040 0050 0060 0070 1000 1010 A2 A2 A2 A1 A2 HD SP TH2 TH3 TH4 TD1 TD2 FRC SU Transaction Summary Layouts A 235 Data Trading Partner Ref1 Ref2 Ref3 PS ITEM SCHE DULE Record Number Record Record Layout Layout Qualifie r 10 11 12 13 14 15 16 Plannin 8 Schedul e Header Plannin 8 Schedul e Header Plannin 8 Schedul e Header Plannin 8 Schedul e Header Schedul e Header Flexfiel ds 1 4 Schedul e Header Flexfiel ds 5 9 Schedul e Header Flexfiel ds 10 14 TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD PS PS PS PS PS PS PS 1020 1030 1050 1060 1500 1510 1520 AD CN AX ST A1 A2 A2 SS SS ST1 ST2 SH1 SH2 SH3 A 236 Oracle e Commerce Gateway Implementation Manual Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner PS ITEM SCHE Number Layout Layout DULE Qualifie r 17 18 19 20 21 22 23 24 25 Schedul e Header Flexfiel d15 Vendor Flexfiel ds 1 4 Vendor Flexfiel ds 5 9 Vendor Flexfiel ds 10 14 Vendor Flexfiel d15 Vendor Site Flexfiel ds 1 4 Ven
406. lication tables This happens because the Oracle e Commerce Gateway reads only trading partner sites for the specified organization in the responsibility EDI Responsibility All organizations in the multiple organization environment share the same code conversion tables and Trading Partner definition tables in the Oracle e Commerce Gateway However the process limits the Trading Partner EDI Location Code cross referencing to the base Oracle Application address sites which are assigned to the single organization specified in the EDI Responsibility For inbound transactions the EDI import process also has a single organization Trading Partner 9 19 assigned in the EDI Responsibility for that particular execution For outbound transactions if the concurrent programs are for a single organization Oracle e Commerce Gateway will extract data for a specific operating unit If they are for multiple organizations then the data can be extracted for all operating units associated with your responsibility or for a specified operating unit For reports since Trading Partners can be associated with operating units linked to your responsibility during the Trading Partner group setups if the Trading Partner reports or the Transactions Trading Partners reports are for multiple organizations you can run the reports for all operating units associated with your responsibility or for a specified operating unit If the reports are for a single organizatio
407. lications or ask the supplier to resend the transaction with the corrected values If you chose to update Oracle Applications data you can resubmit the Purchasing Documents Open Interface process to re validate the transaction If you chose to have the supplier send a corrected transaction you must first purge the rejected data sitting in the Purchasing Documents Open Interface tables by submitting the Purge Purchasing Documents Open Interface Processed Data program and then re import the updated transaction using Oracle e Commerce Gateway Inbound Ship Notice Manifest ASNI 856 DESADV Inbound Shipment and Billing Notice SBNI 857 No EDIFACT Trading Partner Link to Oracle e Commerce Gateway Suppliers and supplier sites are defined in either Oracle Purchasing or Oracle Payables Included in the definition is the EDI Location Code that trading partners agree to exchange to represent the full detailed address Often they do not send the full address but just the EDI Location Code This is a critical data field to Oracle e Commerce Gateway The EDI Location Code is the link between a supplier supplier site in Oracle Applications and the trading partner site definition in Oracle e Commerce Gateway This enables Oracle e Commerce Gateway to access the detailed data about the supplier or supplier site in the base Oracle Applications without maintaining the detail data in Oracle e Commerce Gateway To ensure that the trading partner link betwee
408. lier item In Oracle Inventory Items gt Customer Items gt Customer Items In Oracle Inventory Items gt Cross Reference Click on the Assign button to add cross references to the cross reference type selected Application Transaction Detail 6 49 Table Content Navigation Vendor s Inventory Item Internal vendor inventory In Oracle Inventory table items Items gt Master Items MTL_SYSTEM_ITEMS Cross Reference Types for the Customer Item Cross Reference Table Cross Reference Types qualify the item that was entered The corresponding field in the transaction is the CUSTOMER_ITEM_ID_TYPE is explained below The Customer Item Cross Reference table has codes CUST and INT seeded by Oracle Inventory One of these codes can be written to the Order Import table if you wish to use the Customer Item Cross Reference table during item cross referencing Seeded Cross Reference Meaning Use Types for Customer Items CUST Customer Specific Number Identify the item as a customer defined item INT Internal Item The item is recognized as the internal supplier s inventory item but it is also defined in the customer cross reference table so the item can also be displayed in the Ordered Item field in the order Cross Reference Types for the Inventory Item Cross Reference Table The user can define many different cross reference type codes for generic inventory items while setting up the item cross ref
409. ll need to substitute its mapped position defined in the Oracle e Commerce Gateway transaction interface file Some Translators provide a base data map for the Oracle e Commerce Gateway transaction interface file These base data maps are currently based on the initial release 11 They are not likely to be plug and play data maps Note that the Translator providers may charge additional license or service fees for these pre configured data maps The base data maps most likely need customization for the following reasons e Whether the internal or external code s are available in the interface file if you used code conversion e System or business requirements e Trading partners requirements The base data maps may also need changes if software patches add or change data element positions in the transaction interface file and you accept new records after the seed data reconciliation review The following reports may facilitate your data map reviews Run the reports as needed e Transaction Record Layout report to see the transaction interface file e Transaction Data File report to see data from a file against its transaction interface file layout The following process should be followed after a patch is applied This process attempts to restore the record layout to the layout as defined before the latest patches were applied Review the log from this process to see the impact of the patch and the reconstructed transaction record layou
410. llows e ECE_PYO_INVOICE_V ECE_PYO_PAYMENT_V The ECE_PYO_PAYMENTS_V view used to identify which payments and associated invoices are eligible for extraction The extract criteria are as follows e Trading partner is defined e Transaction type enabled for the trading partner e Payments have not been previously extracted e Payments are flagged as OK to pay e Payments have not been voided e Bank account ID bank name and bank branch ID assigned to the payment match those in the payment batch If necessary you can use SQLPLUS to verify if there are any eligible documents to be extracted To do so you must first set the organization context and then issue the SQL count function as follows SQLPLUS gt execute fnd client _info set_org context lt Org number gt SQLPLUS gt select count ECE PYO PAYMENTS V Review all your set ups if the count value is 0 as this indicates there are no eligible documents to be extracted Columns Updated Upon Extraction Once the Translator sends the transactions to the bank and you have verified the bank has received the file you can confirm the payment batch to indicate the invoices have been paid This prevents the same invoice from being included in a future payment batch Refer to Oracle Payables User s Guide Confirming Payment Batches section for the details Oracle Process Manufacturing The following table lists the transactions delivered with the Oracle Process Manu
411. ly the first three levels are showing for this visual reference in the file e The record number uniquely identified the set of data in the given transactions This is the only required data in the first hundred bytes of each record e Record Layout and Record Qualifier are labels to identify the type of data on the record if someone must read the file There are some Record Layouts like AD for address that you will see in all transactions An address record may have a Record Qualifier like ST to indicate a ship to address or BT for a bill to address See below for a list of common Record Layouts and Record Qualifier that may be seen in many transactions The following table illustrates the content of a common key Components of a Common Key Translator Ref 1 Ref 2 Ref 3 Record Record Record Code Number Layout Qualifier AB 01 101111 N A N A 0010 N A N A AB 01 101111 N A N A 1000 PO POI AB 01 101111 00001 N A 2000 IT IT1 AB 01 101111 00001 00001 3000 SH SH1 AB 01 101111 00001 00002 3000 SH SH1 Transaction Interface File Architecture 5 3 Translator Ref 1 Ref 2 Ref 3 Record Record Record Code Number Layout Qualifier AB 01 101111 00002 N A 2000 IT IT1 AB 01 101111 00002 00001 3000 SH SH1 AB 01 101111 00002 00002 3000 SH SH1 Application Descriptive Flexfields Records Many descriptive flexfields are found throughout the transaction They are extracted from the application for outbound transactions They may be loaded
412. m 1 line numbers customer item supplier item Item 1 INVENTORY_ITEM_SEGME NT_1 10 Item 1 INVENTORY_ITEM_SEGME NT_11 20 1st Prices configuration options references 1st Schedule1 dates etc 2nd Prices configuration options references 2nd Schedule dates etc 3rd Prices configuration options references 3rd Schedule3 dates etc Item 2 line numbers customer item supplier item Item 2 INVENTORY_ITEM_SEGME NT_1 10 HEADER Copy all item data to each of its shipments Copy all item data to each of its shipments Copy all item data to each of its shipments LINE Item 1 Schedule1 data LINE Item1 Schedule1 data LINE Item1 Schedule2 data LINE Item1 Schedule2 data LINE Item1 Schedule3 data LINE Item1 Schedule3 data Copy all item data to each of its shipments Copy all item data to each of its shipments 6 12 Oracle e Commerce Gateway Implementation Manual e Commerce Gateway POI Transaction Record 2020 3000 4000 3000 4000 2000 2010 2020 3000 4000 3000 4000 Line and Shipment Records e Commerce Gateway POI Transaction Record Data Content Item 2 INVENTORY_ITEM_SEGME NT_11 20 1st Prices configuration options references 1st Schedule1 dates etc 2nd Prices configuration options references 2nd Schedule1 dates etc Item 3 line numbers customer item supplier item Item 3 INVEN
413. m and their revisions to the customer in the purchase order acknowledgement transactions consider storing the two components in flexfields INVENTORY_ITEM_SEGMENT_1 on Record 2010 The internal Oracle Inventory table ID for the valid internal inventory item is moved to INVENTORY_ITEM_SEGMENT_1 in the order in the base Order Management table If the transaction has data in INVENTORY_ITEM_SEGMENT_1 in Record 2010 the item cross referencing is not performed The presence of data in that field assumes that the table ID is to be used in the process Inbound Purchase Order Change POCI 860 ORDCHG Note the record layout difference between the Inbound Purchase Order and the Inbound Purchase Order Change Level Order New New Added Added Inserted Import Record Position Field Field Field Table Record Position Record Header OE_HEAD 1010 all ERS_INTF ACE Header OE_HEAD 1020 1050 all ERS_INTF ACE Header OE_CREDI 1700 100 110 TS_INTER FACE Header OE_PRICE 1800 200 230 _ADJS_INT ERFACE Header OE_RESER 1900 100 110 VTNS_INT ERFACE Header OE_ACTIO 1950 NS_INTER FACE Line OE_LINE_I 3010 all NTERFAC E 6 62 Oracle e Commerce Gateway Implementation Manual Level Order New New Added Added Inserted Import Record Position Field Field Field Table Record Position Record Line OE_LINE_I 3012 3018 all NTERFAC E Line OE_CREDI 5000 130 140 TS_INTER FACE Line OE_PRICE 6020 6050 all 6000 220 250 _ADJS_INT ERFACE Line
414. mary Sequence Data Data Level Record Number Note 1 Control Record HEADER 0010 2 Basic Purchase HEADER 1000 Order Header 3 Change Data HEADER 1010 4 Change HEADER 1020 1050 Comments 5 Currency Code HEADER 1060 amp Conversion Rates 6 Payment HEADER 1070 Amount Credit Card Payment Type Code Tax Exempt 7 FOB Point HEADER 1090 Freight Terms Shipment Priority Shipping Method 8 Shipping amp HEADER 1100 Packing Instructions 9 Header Request HEADER 1110 Date Demand Class 10 Header HEADER 1200 1230 Flexfields Flexfields 11 PO Header HEADER 1240 1270 Flexfields Flexfields Transaction Summary Layouts A 35 Sequence Data Data Level Record Number Note 12 Global Header HEADER 1280 1320 Flexfields Flexfields 13 Customer Name HEADER 1400 Flexfields amp Number 14 Sold to Address HEADER 1410 15 Sold to Contact HEADER 1420 16 Ship to Address HEADER 1500 Header Level 17 Ship to Contact HEADER 1510 Header Level 18 Invoice Address HEADER 1520 19 Invoice Contact HEADER 1530 20 Ordered By HEADER 1540 Name 21 Ship from HEADER 1600 Address Header Level 22 Extension HEADER custom custom Tables Purchase Order Header Data 23 Credits Data CREDIT 1700 24 Credit Flexfields CREDIT 1710 1740 Flexfields 25 Price PRICE 1800 Adjustments ADJUSTMENT Data A 36 Oracle e Commerce Gateway Implementation Manual Sequence Data Data Level Record Number Note 26 Discount List PRICE 1810 Names
415. ment HEADER 1250 Card Data 20 Header HEADER 1800 Attachment Data ATTACHMENT HEADER 21 Header HEADER 1810 Attachment Data ATTACHMENT DETAIL 22 Basic Item Data LINE 2000 23 Basic Item Data LINE 2010 24 Basic Item Data LINE 2020 Hazardous Material Codes 25 Item Note to LINE 2030 Supplier 26 Line Flexfields LINE 2040 2070 Flexfields 27 Line Part LINE 2080 2110 Flexfields Flexfields 28 Line Part LINE 2120 Segments 29 Line Part LINE 2130 Segments 30 Line Attachment LINE 2800 Header ATTACHMENT HEADER Transaction Summary Layouts A 157 Seq Data Data Level Record Number Note 31 Line Attachment LINE 2810 Detail ATTACHMENT DETAIL 32 Master Item MASTER ITEM 2820 Attachment ATTACHMENT Header HEADER 33 Master Item MASTER ITEM 2830 Attachment ATTACHMENT Detail DETAIL 34 Inventory Item INVENTORY 2840 Attachment ITEM Master ATTACHMENT HEADER 35 Inventory Item INVENTORY 2850 Attachment ITEM Detail ATTACHMENT DETAIL 36 Basic Shipment SHIPMENT 3000 Data 37 Shipment SHIPMENT 3010 3040 Flexfields Flexfields 38 Ship To SHIPMENT 3050 Address Code 39 Ship To Contact SHIPMENT 3060 40 Shipment SHIPMENT 3800 Attachment ATTACHMENT Master HEADER 41 Shipment SHIPMENT 3810 Attachment ATTACHMENT Detail DETAIL 42 Distributions DISTRUBTION 4000 4110 Data A 158 Oracle e Commerce Gateway Implementation Manual Seq Data Data Level Record Number Note 43 Distributions DISTRUBTION 4200 4230 Flexfields Flexfields Outbound P
416. ment reference Application Transaction Detail 6 17 Sample Original System Document Reference Original System Document Reference Original System Document Reference 86420 03 86420 03 Default Purchase Order Number Default Purchase Order Release Number 86420 03 Refer to CUSTOMER_PO_NUMBER under OE_HEADERS_ INTERFACE table below for more detail ORIG_SYS_LINE_REF Original System Line Reference Original System Line Reference is an identifier for the line number in the order This field is used for matching lines and schedules in subsequent transactions to the current order in Order Management The ORIG_SYS_LINE_REF and the ORIG_SYS_SHIPMENT_REF are stored at the line level in the base order tables The combination of the ORIG_SYS_LINE_REF and the ORIG_SYS_SHIPMENT_REF see below must be unique within the ORIG_SYS_DOCUMENT_REFERENCE specified at the header The ORIG_SYS_LINE is derived by the POI program or generated by a process such as the EDI Translator before the order is imported into the Order Import tables It is not sent by the customer in the transaction as a field known as Original System Line Reference Sample Original System Line Reference Original System Line Reference 001 Default Customer Line Number 001 Note The user may enter data in this field or use the customer line number default ORIG_SYS_SHIPMENT_REF Original System Shipment Reference Original System Schedule Reference is an identifier
417. mn represents the supplier s item number for the buyer item defined in Oracle Purchasing This must be specified if buyer item number is not available Review Receiving Open Interface Exceptions All exceptions detected by the Receiving Open Interface are written to the PO_INTERFACE_ERRORS table to be reviewed using the Receiving Interface Errors Report for 856 DESADV or Purchasing Interface Errors Report for 857 Refer to the Oracle Manufacturing Distribution Sales amp Service Open Interface manual Oracle Purchasing Open Interfaces document for a detailed list of detectable errors and their meaning Return Application Advice to Supplier In addition to writing error data to the PO_LINTERFACE_ERRORS table the Receiving Open Interface program writes an entry to Oracle e Commerce Gateway s Application Advice tables ECE_LADVO_HEADERS and ECE_ADVO_DETAILS to be reported back to the supplier via the outbound Application Advice 824 APERAK transaction Resolve Receiving Open Interface Exceptions To resolve Receiving Open Interface exceptions you can either correct the set up data in Oracle Applications or ask the supplier to resend the corrected transaction If you chose to update Oracle Applications data you can resubmit the Receiving Open Application Transaction Detail 6 119 Interface process to revalidate the transaction If you chose to have the supplier send a corrected transaction you must first purge the rejected data
418. more detailed error data is provided in the View Log screen of the Submit Request window when you run the Receiving Transaction Processor Refer to the Oracle Purchasing User s Guide for details Receiving Open Interface Required Fields The Inbound Ship Notice Manifest and Inbound Shipment and Billing Notice transactions use the Receiving Open Interface It is used to validate the incoming data entered into the Receiving Open Interface tables by the Oracle e Commerce Gateway import program The following is a list of the Receiving Open Interface required fields These fields are required for the Receiving Open Interface API to successfully process and move the data from the Receiving Open Interface tables into the Oracle Purchasing base application tables Required fields noted as derived or hardcoded do not require a value in the transaction on the transaction interface file since the values are determined by the Oracle e Commerce Gateway process RCV_HEADERS_INTERFACE Table The following table lists the required fields for the RCV_HEADERS_INTERFACE table An asterisk by the column name indicates that it is not mapped referenced by Oracle e Commerce Gateway because the data is not required by the transaction message The lt field gt _ID fields are derived by the Receiving Open Interface API Application Transaction Detail 6 109 Required Fields for the RCV_HEADERS_INTERFACE Table Oracle Cond Oracle Hardcoded Record Positio
419. n Applications e Commerce Derived Number Number Column Gateway Name for Column Required Name Fields SHIPMENT_ Yes PICK_SLIP_ 1000 10 NUM NUMBER SHIPPED_D Yes SHIPPED_D 1000 70 ATE ATE AUTO_TRA Yes AUTO_TRA 1000 100 120 NSACT_CO NSACT_CO DE DE TRANSACTI TRAN_PURP 1000 110 ON_TYPE OSE_APPLIC ATION INVOICE_N Yes INVOICE_N 1030 10 UM UM INVOICE_D Yes INVOICE_D 1030 20 ATE ATE TOTAL_INV Yes INVOICE_A 1030 30 OICE_AMO MOUNT UNT VENDOR_ID SHIP_FROM 1100 170 _CUSTOMER ID SHIP_TO_OR Yes SHIP_TO_IN 1120 10 GANIZATIO T_LOCATIO N_CODE N_ID CREATED_B CREATED_B Derived Y Y 6 110 Oracle e Commerce Gateway Implementation Manual Oracle Applications Column Name for Required Fields Oracle e Commerce Gateway Column Name Hardcoded Record Derived Number Position Number CREATION_ DATE GROUP_ID HEADER_IN TERFACE_ID LAST_UPDA TE_DATE LAST_UPDA TED_BY PROCESSIN G_STATUS_ CODE RECEIPT_SO URCE_CODE VALIDATIO N_FLAG EMPLOYEE_ NAME EMPLOYEE_ ID RECEIPT_N UM VENDOR_N AME VENDOR_N UM CREATION_ DATE GROUP_ID HEADER_IN TERFACE_ID LAST_UPDA TE_DATE LAST_UPDA TED_BY Derived Derived Derived Derived Derived H PENDING H VENDOR H Y Application Transaction Detail 6 111 Oracle Cond Oracle Hardcoded Record Position Applications e Commerce Derived Number Number Column Gateway Name for Column Required Name Fields SHIPPED_D
420. n Categories Enable Code Conversion Define Code Conversion Values Review Oracle IM Application Applications set ups Transaction Detail for each transaction and update as necessary Step 20 21 22 23 Required Optional Required Required Required As Needed Description Prepare data to test transaction Add data in Oracle Applications to test outbound transaction Create inbound file to test inbound transaction Test the transaction being implemented at several levels until results match expectations Internally Oracle e Commerce Gateway and Oracle Applications With Translator With Trading Partner Release fully tested transaction to production Archive transaction interface files as needed Reference IM Implementation Manual IM Test Transactions IM Test Transactions IM Archive Backup In summary the following has been installed or set up e The upgrade version is installed e All custom development re integrated after upgrade is completed when appropriate e System and Transaction Profile setups are entered e Process rules and Column rules are set up Oracle e Commerce Gateway Implementation Checklist 3 7 e Code Conversion is set up e Trading Partners are set up e Base Oracle Application setups are complete e Transaction interface file definitions modifications are completed when appropriate Pass a simple outbound and or inbound
421. n then the reports can be run for a specified operating unit If the transaction interface file contains transactions associated with several organizations the transactions for the other organizations not defined in the current process s EDI Responsibility will not successfully find the Trading Partner s EDI Location Codes with the base Oracle Application customer supplier or bank site addresses Only the address sites associate with the current organization are examined the other address sites are not included in the process to examine the EDI Location Code to determine the address site in the base Oracle Application One of the following happens 1 The transactions for each responsibility can be in separate transaction interface files then processed by each appropriate responsibility The EDI Translator another process or the sending Trading Partner may separate the transactions by organization before the Oracle e Commerce Gateway process is executed 2 All transactions can be loaded from one file However only one organization will successfully find the Trading Partner definitions Transactions that could not find the Trading Partners sites will remain in the View Staging tables Log on with a responsibility of each of the Trading Partner exceptions then on line resubmit the transaction for revalidation Position the cursor at the desired level in the document tree on the left then press the resubmit button The transaction will be
422. n Category Required Default Value Order Specific Transaction Profile Option ECE POO_HEA Enables the Functional Yes No DER_ATTACH header MENT_ENABLE attachment for D the outbound Purchase Order transaction ECE POO_INVE Enables the Functional Yes No NTORY_MITEM master inventory _ATTACHMEN item attachment T for the outbound Purchase Order Request transactions ECE POO_INVE Enables the Functional Yes No NTORY_ITEM_ inventory item ATTACHMENT attachment for the outbound Purchase Request transactions ECE POO_LINE Enables the line Functional Yes No _ATTACHMEN attachment for T_ENABLED the outbound Purchase Order transactions ECE POO_SHIP Enables the Functional Yes No MENT_ATTAC shipment HMENT_ENAB attachment for LED the outbound Purchase Order transactions Note The same options apply to the outbound Purchase Order Change Request transaction For more profile category information see Oracle Applications System Administrator s Guide Maintenance for details 4 10 Oracle e Commerce Gateway Implementation Manual Supplier Scheduling Profile Options Since the purpose of the planning schedule is to work closely with your suppliers to communicate forecast information and to get the right materials to the right place at the right time one additional profile is used to prevent zero schedule from being written to the file Supplier Scheduling Specific Transaction Profile Option Supplier Description Ca
423. n Manual Data Data Transaction Data Description Customer Customer Site Carrier Code Transaction Data GAMMA 9999 AIR Transaction Column CUSTOMER NAME CUSTOMER SITE CARRIER_EXT1 Specific Transaction Data Listed below are the full search key parameters given the data found in the transaction or data derived by the Oracle e Commerce Gateway Use this data to find a code conversion value table entry to retrieve the external code Code Category Direction Key 1 Customer Key 2 Customer Site Key 3 Key 4 Key 5 SHIP_VIA This code category was assigned to a data element in the transaction via the Assign Category window IN and BOTH Determined by the inbound transaction to be processed GAMMA Source column for this key 1 is CUSTOMER_NAME The value GAMMA was derived by the Oracle e Commerce Gateway given the Trading Partner for this transaction 9999 Source column for this ke 2 is CUSTOMER SITE The value 9999 was derived by the Oracle e Commerce Gateway given the Trading Partner for this transaction not used not used not used Code Conversion 10 31 External 1 Code AIR AIR is the value in CARRIER_EXT1 in the transaction interface file The table below shows the three attempts to access the code conversion value table using each search key The number of attempts is always one more than the number of Key boxes that you enabled in the Code Conversion Categori
424. n Manual Data Trading Ref 1 Ref 2 Ref Record Record Record Partner SCH_R ITEM SCHE Number Layout Layout EF DULE Qualifie r 19 Additio TP_CD SCH_R ITEM 2020 B IT3 nal Item EF Data 20 Additio TP_CD SCH_R ITEM 2030 14 IT4 nal Item EF Data 21 Unitof TP_CD SCH_R ITEM 2040 UM UOM Measur EF e 22 Item TP_CD SCH_R ITEM 2050 ME MEA Measur EF ements amp Physical Qualitie s 23 Item TP_CD SCH_R ITEM 2060 RF ITM Miscella EF neous Referen ces 24 Item TP_CD SCH_R ITEM 2070 CO ITM Contact EF Names 25 Bar cod TP_CD SCH_R ITEM 2080 LB LB1 LB2 e EF 2090 Shippin g Label data 26 Ship To TP_CD SCH_R ITEM 2100 AD STI Address EF Code Transaction Summary Layouts A 211 Data Trading Ref 1 Ref 2 Ref Record Record Record Partner SCH_R ITEM SCHE Number Layout Layout EF DULE Qualifie r 27 Bill To TP_CD SCH_R ITEM 2110 AD BTI Address EF Code 28 Interme TP_CD SCH_R ITEM 2120 AD ICI diate EF Ship To Address Code 29 Ship TP_CD SCH_R ITEM 2130 AD SFI From EF Address Code 30 Miscella TP_CD SCH_R ITEM 2140 MN MNI neous EF Name Codes and Values 31 Carrier TP_CD SCH_R ITEM 2150 TD QER Details EF 32 Item TP_CD SCH_R ITEM 2160 NT ITM Note EF Text 33 Hazard TP_CD SCH_R ITEM 2170 HZ HZ1 ous EF Material data 34 Ship De TP_CD SCH_R ITEM 2180 SD SDR livery EF Pattern Codes A 212 Oracle e Commerce Gateway Implementation Manual Data Trading Partner Ref 1 SCH_R EF Ref 2 ITEM Ref Record
425. n Oracle e Commerce Gateway and Oracle Applications is set up properly verify that the supplier supplier site and the EDI Location Code in Oracle Applications is the correct supplier site selected for the Trading Partner definition in Oracle e Commerce Gateway The selected supplier supplier site and the EDI Location Code defined in Oracle Applications are displayed in the Define Trading Partners window Assignment tab If the data is not what you intend it to be you must make the appropriate changes for the transaction to be imported for the correct trading partner This could involve either altering the supplier supplier site in the base Oracle Application or assigning a different supplier supplier site to that EDI Location Code in Oracle e Commerce Gateway Refer to the Trading Partner chapter for recommendations on selecting the correct trading partner EDI Location Code for the control record 0010 for the transaction in the transaction interface file Application Transaction Detail 6 105 Oracle e Commerce Gateway Required Fields The following table lists the Oracle e Commerce Gateway required fields These fields are required to authenticate the trading partner and transaction If the required data is not provided in the transaction the Oracle e Commerce Gateway import process fails the transaction Then an exception message is displayed in the View Staged Documents window If the trading partner is valid and the transaction is ena
426. n Transaction Detail 6 67 advice e Disburse funds directly to the supplier s bank account do nothing with the remittance advice e Send remittance advice electronically to the supplier do nothing with the payment e Disburse funds directly to the supplier s bank account and send remittance advice to the supplier electronically You indicate your instructions to the disbursement bank by setting the Transaction Handling code when you define your supplier or supplier sites Regardless of how you set the Transaction Handling code Oracle e Commerce Gateway will construct the entire file so your disbursement bank has everything it needs If your supplier cannot receive an electronic remittance advice a hard copy may be printed using Oracle Payables and sent to the supplier Trading Partner Link to Oracle e Commerce Gateway Bank branch data for the disbursement bank is defined in Oracle Payables Included in the definition is the EDI Location Code that trading partners agree to exchange to represent the full detailed address Often they do not send the full address but just the EDI Location Code This is a critical data field to Oracle e Commerce Gateway The EDI Location Code is the link between a bank branch in Oracle Payables and the trading partner site bank branch definition in Oracle e Commerce Gateway This enables Oracle e Commerce Gateway to access the detailed data about the bank branch in the Oracle Payables without maintaining
427. n are shown in the following table Inbound Transaction Seeded Column Rules Field Types Column Rule Rule Action Required Fields Value is Required Skip Document Date Fields Data type Checking Skip Document Numeric Fields Data type Checking Skip Document A column is identified as required if it is required by Oracle e Commerce Gateway or the Application Open Interface to successfully import an interface file Examples include values to key fields or parameters that identify a business rule to be used when validating incoming data Refer to the Application Transaction Detail chapter for a list of required fields relevant to the transaction being implemented The Assign Column Rules window allows you to change or delete the column rules for required date or numeric fields but this type of change is not recommended unless the potential exception can be resolved in the Application Open Interface You can change the corresponding column rule action if the default behavior is not desired Whether you use Oracle e Commerce Gateway s exception handler to pre validate 4 16 Oracle e Commerce Gateway Implementation Manual incoming data or not is dependent on your business rules and the accuracy of your trading partner s interface files If you do not define any column rules at all you are assured that at minimum the seeded column rules are executed Given the variety of ways in which Oracle Applications modules support error detection err
428. n for the Oracle Applications implementation team as well as for users responsible for the ongoing maintenance of Oracle Applications product data This guide also provides information on creating custom reports on flexfields data Oracle Applications Developer s Guide This guide contains the coding standards followed by the Oracle Applications development staff It describes the Oracle Application Object Library components needed to implement the Oracle Applications user interface described in the Oracle Applications User Interface Standards for Forms Based Products It also provides information to help you build your custom Oracle Forms Developer forms so that they integrate with Oracle Applications Oracle Applications User Interface Standards for Forms Based Products This guide contains the user interface UI standards followed by the Oracle xvii Applications development staff It describes the UI for the Oracle Applications products and how to apply this UI to the design of an application built by using Oracle Forms Training and Support Training Oracle offers a complete set of training courses to help you and your staff master Oracle e Commerce Gateway and reach full productivity quickly These courses are organized into functional learning paths so you take only those courses appropriate to your job or area of responsibility You have a choice of educational environments You can attend courses offered by Oracle University
429. n identifies the invoice line type The valid values are ITEM TAX FREIGHT or MISCELLANEOUS Review Oracle e Commerce Gateway Exceptions Use the Oracle e Commerce Gateway View Staged Documents window to review the Oracle e Commerce Gateway transaction exceptions Once the exceptions are identified and resolved you can submit the transaction for reprocessing ignore the exception during reprocessing or delete the transaction Select the option in the View Staged Documents window Resolve Oracle e Commerce Gateway Exceptions To resolve Oracle e Commerce Gateway exceptions you can either correct the set up data in Oracle e Commerce Gateway or Oracle Applications or ask the Trading Partner to send a corrected transaction If the Trading Partner sends a corrected transaction be sure to delete the erroneous transaction from Oracle e Commerce Gateway s staging tables using the View Staged 6 82 Oracle e Commerce Gateway Implementation Manual Documents window The duplicate transaction may cause confusion Relevant Oracle Payables Profiles and Setups The following is a list of the Payables set ups related to the Receiving Open Interface Invoice Hold Reason You can optionally set up an Invoice Hold Reason unique to this transaction All invoices being imported into Oracle Payables may be placed on hold using the unique Invoice Hold Reason This may be useful during implementation of a new trading partner so that you can review the electron
430. nal data grouping of records the data level the record numbers and relevant notes about the data grouping SSSO Transaction Record Summary Data Data Level Record Number Note 1 Control Record HEADER 0010 2 Trading Partner HEADER 0020 0050 Flexfields Header Flexfields 3 Trading Partner HEADER 0060 0070 Flexfields Detail Flexfields 4 Basic Planning HEADER 1000 Schedule Header 5 Supplier HEADER 1010 Numbers 6 Supplier Site HEADER 1020 Address Code 7 Supplier Site HEADER 1030 Phone 8 Ship to HEADER 1050 Address Code A 244 Oracle e Commerce Gateway Implementation Manual Data Data Level Record Number Note 9 Ship to HEADER 1060 Miscellaneous Data 10 Schedule Header HEADER 1500 1530 Flexfields Flexfields 11 Vendor HEADER 1600 1630 Flexfields Flexfields 12 Vendor Site HEADER 1650 1680 Flexfields Flexfields 13 Shipping HEADER 1700 1730 Flexfields Organization Flexfields 14 Ship To Options HEADER 1750 1780 Flexfields Flexfields 15 Extension HEADER 1900 Custom Tables Purchase Order Header Data 16 Basic Item Data ITEM 2000 17 Product ITEM 2010 Description 18 Hazardous ITEM 2020 Material Codes 19 Contact Names ITEM 2030 20 Last Receipt ITEM 2040 Data 21 Ship To ITEM 2050 Organization Address Code Transaction Summary Layouts A 245 Data Data Level Record Number Note 22 Ship To ITEM 2060 Organization Data 23 Approved ITEM 2100 2130 Flexfields Supplier List Flexfields 24 Item
431. nbound transaction can be processed the user needs to determine if the predefined transaction record definition meets his business requirements and if the predefined process rules and column rules that are assigned to the transactions meet his needs If the user does not perform this step the Oracle e Commerce Gateway uses the seeded rules and actions for data validation Information concerning the Interface File Definition window and the establishing of process and column rules can be found in this manual Refer to Determine Process and Column Rules and Actions and Modify Transaction Interface File for more details After an inbound transaction request is executed users have the ability to view the documents with exceptions using the View Staged Documents window After processing any inbound transaction the user should check the concurrent manager status If it has a status of warning or error the user can go to the View Staged Documents window to see the document details such as rule exceptions and column values Users should also check the log file for other processing information View Staged Documents Window The View Staged Documents window is used to view the results of inbound document processing Users access this window to display the number of documents in the staging tables and to see if any failed the validation process Users can drill down to view the document numbers such as PO Number or Invoice Number that have rule exceptions
432. nce 1 Line 1 First Original System 19990308 19990308 Shipment Shipment Reference 1 00000 CHIC 01 00000 CHIC 01 6 16 Oracle e Commerce Gateway Implementation Manual Table Level Data Element Customer A Customer B Line 1 Second Original System 86420 03 86420 03 Shipment Document Reference Copy from Header Line 1 Second Original System 001 001 Shipment Line Reference 1 Line 1 Second Original System 19990308 19990308 Shipment 00000 ATL 01 00000 ATL 01 Shipment Reference 2 Sold_to_Customer 1230 1230 ORIG_SYS_DOCUMENT_REF Original System Document Reference Original System Document Reference is an identifier for the order within Order Management to guarantee its uniqueness within one operating unit Most often it is the purchase order number plus release number if appropriate A character such as the dash sign between each component improves readability The ORIG_SYS_DOCUMENT_REF is derived by the POI program or generated by a process such as the EDI Translator before the order is imported into the Order Import tables It is not sent by the customer in the transaction as a field known as Original System Document Reference Sample Original System Document Reference Original System Document Reference 86420 Purchase Order Number 86420 Note The user may enter data in this field or use the purchase order number default The following table shows a sample original system docu
433. ndard process This code is the flag to indicate that the transaction is to be treated as test T or production P by the Translator This code must remain synchronized with the Test flag defined in the Translator Which code overrides the other if they are out of sync depends on the Translator For inbound transactions the EDI Trading Partner detail flag prevails This code identifies the transaction type and its direction e g POI for purchase orders inbound Transaction Interface File Architecture 5 11 Seq Data Element Value Note 11 12 13 14 15 Document Type Document Purpose Code Document Code full Translator Code full Trading Partner Location Code external Depends on the transaction Sample BLANKET STANDARD Depends on the transaction Sample OR original CH change This code identifies sub types of the given transactions such as blanket order or standard orders to process This code identifies the transaction as the original change replacement or other appropriate status for the given transaction This is the primary transaction code such as the purchase order or invoice number The code is the key document identified for the specific transaction This is the full length Translator Code defined in the Translator to identify this Trading Partner This code is the EDI Location code as defined for the Trading Partner
434. ndependence that enables you to select any EDI translator or third party application that best suits your business requirements Included in the Oracle e Commerce Gateway product are many prebuilt business critical transactions and integration configuration tools designed to streamline your implementation to easily transform your business to e business The following table lists many of the transactions provided by Oracle e Commerce Gateway including the direction of the transaction a description of the transaction and the base Oracle Application Transaction List X12 Trans EDIFACT Direction Description Base Oracle Message Application 850 ORDERS outbound Purchase Orders from Oracle Purchasing 860 ORDCHG outbound Purchase Order from Oracle Change Request Purchasing 832 PRICAT inbound Price Sales into Oracle Catalog Purchasing 843 QUOTES inbound Response to into Oracle Request for Purchasing Quotation 856 DESADV inbound Ship into Oracle Notice Manifest Purchasing Introduction 1 7 X12 Trans EDIFACT Direction Description Base Oracle Message Application 857 no inbound Shipment and into Oracle Billing Notice Purchasing and equivalent Payables 824 APERAK outbound Application from Oracle Advice Purchasing and diagnostic Payables message used in response to the inbound ship notice shipment billing notice and invoice transactions 830 DELFOR outbound Planning from Oracle Schedule Supplier Scheduling
435. ne level records for OE_PRICE_ADJS_INTERFACE Application Transaction Detail 6 35 Line Level Records for OE_PRICE_ADJS_INTERFACE Oracle Oracle Hardcoded Deri Record Number Position Applications e Commerce ved Number Column Name Gateway for Required Column Name Fields ORIG_SYS_DOC ORIG _SYS_DOC_ Required 7000 010 UMENT_REF UMENT_REF ORIG_SYS_LINE ORIG_SYS_ Required 6000 030 _REF LINE _REF ORIG_SYS_SHIP ORIG_SYS_SHIP Required 6000 040 MENT_REF MENT_REF ORIG_SYS_DISC ORIG_SYS_DISC Required 6000 050 OUNT_REF OUNT_REF OPERATION_C OPERATION_C _ If Null default 6000 060 070 ODE ORDER_SOURC E_ID LAST_UPDATE D_BY LAST_UPDATE _DATE CREATION_DA TE CREATED_BY ODE _EXT1 ORDER_SOURC E_ID LAST_UPDATE D_BY LAST_UPDATE _DATE CREATION_DA TE CREATED_BY to INSERT Hard code 6 meaning EDI Derived Set to SYSDATE Set to SYSDATE Derived The following table shows the line level records for OE_LRESERVTNS_INTERFACE 6 36 Oracle e Commerce Gateway Implementation Manual Line Level Records for OE_RESERVTNS_INTERFACE Oracle Oracle Hardcoded Deri Record Number Position Applications e Commerce ved Number Column Name Gateway for Required Column Name Fields ORIG_SYS_DOC ORIG _SYS_DOC Required 7000 010 UMENT_REF UMENT_REF ORIG_SYS_LINE ORIG SYS_ Required 7000 030 _REF LINE _REF ORIG_SYS_SHIP ORIG_SYS_SHIP Required 7000 040 MENT_REF MENT_REF ORIG_SYS_RES ORIG _SYS_RES
436. ned column rules If no process or column rule exceptions are detected the Oracle e Commerce Gateway import program will write the transaction to the Receiving Open Interface tables to be processed by the Receiving Open Interface API Application Transaction Detail 6 159 Oracle e Commerce Gateway Required Fields Oracle e Commerce Record Number Position Number Note Gateway Column Name for Required Fields TEST_INDICATOR 0010 20 T or P DOCUMENT_CODE 0010 60 Schedule Reference Number TP_TRANSLATOR_C 0010 70 Translator identifier ODE for this Trading Partner TP_LOCATION_CO 0010 80 The EDI Location DE Code TRANSACTION_DA 0010 120 Schedule Generation TE_TIME date EDI_CONTROL_NU 0010 160 Level 1 control M_1 number assigned by the customer s EDI translator for auditing EDILCONTROL_NU 0010 170 Level 2 control M_2 number assigned by the customer s EDI translator for auditing EDI_CONTROL_NU 0010 180 Level 3 control M_3 number assigned by the customer s EDI translator for auditing RLM_SCHEDULE_T 1000 10 Planning Shipping YPE_INT or Sequenced SCHEDULE_PURPO 1000 70 Original Replace SE_INT Cancel etc 6 160 Oracle e Commerce Gateway Implementation Manual Oracle e Commerce Gateway Column Name for Required Fields Record Number Position Number Note SCHEDULE_SOURC E ITEM_DETAIL_TYPE _INT ITEM_DETAIL_SUBT YPE_INT DATE_TYPE_CODE_ INT START_DATE_TIME QTY_TYPE_COD
437. ng Partner sends a corrected transaction be sure to delete the erroneous transaction from Oracle e Commerce Gateway s staging tables using the View Staged Documents window The duplicate transaction may cause confusion Oracle e Commerce Gateway Implementation Manual Relevant Oracle Order Management Profiles and Setup Steps The required Order Management setup steps are the same whether the order is entered on line or through Order Import The following is a sample list of the Order Management setup steps needed to process orders through the e Commerce Gateway or entered on line e Customer and Customer Sites must be defined in Order Management Oracle Receivables e Order Types must be defined in Order Management e Item and appropriate customer items must be defined in Oracle Inventory Oracle Order Management Defaulting Functionality Oracle Order Management provides powerful Defaulting functionality that is used by the Order Import process as well as by orders entered manually using the Order Management forms If a column is left null in the interface tables then the Defaulting Rules are invoked to provide a value for those columns Many of the attributes can be defaulted per customer or customer site by populating columns in the Customer tables Order Management tab Examples of those attributes are salesperson shipping warehouse payment terms order type freight terms ship method price list and many others There are many o
438. ng lets the supplier accomplish the following tasks e Receive error messages on problems that have halted demand processing e Receive warning messages on potential demand processing problems e Receive information messages on noteworthy situations detected by the Demand Processor e Generate exceptions report automatically after demand processing completion e Review real time report on inbound demand processing exceptions e View exceptions generated for any schedule via the Release Management Workbench until purged e Correct set up data to allow successful demand processing e Correct schedule data to allow successful demand processing Application Transaction Detail 6 173 e Validate customer demand for data that impacts demand processing You can review all exceptions detected by the Release Management Demand Processor in the Release Management Demand Workbench or on the Demand Management Exception Report Refer to the Oracle Release Management User s Guide for more information on the Demand Management Exception Report Resolve Release Management Demand Processor Exceptions To resolve Release Management Demand Processor exceptions you can either correct the set up data in Oracle Applications make changes to the original schedule on the Release Management Demand Workbench or ask the supplier to resend the transaction with the corrected values If you chose to update Oracle Applications data you can resubmit the Release Mana
439. ng topics e Testing Inbound Transactions e Testing Outbound Transactions e Printing and Extract of Documents Testing Inbound Transactions When implementing a new inbound transaction for an existing Trading Partner or a new Trading Partner transaction combination it is recommended that you test at several levels You should first test with your internal systems followed by your Translator then finally with your Trading Partner While you are in the test mode you can set the trading partner transaction combination in Oracle e Commerce Gateway to test status that will alert all parties that this is a test transaction Set your trading partner transaction combination to production status when you are ready to receive a production transaction from your Trading Partner Oracle e Commerce Gateway and Oracle Applications are designed to protect your system from receiving invalid data Oracle e Commerce Gateway validates the incoming data for syntactic accuracy and passes the valid data to the Oracle Application Open Interface tables to validate for semantic accuracy Optionally Oracle e Commerce Gateway may pass invalid data to the Application Open Interface tables for validation by the Application Open Interface API This can happen if you did not define Oracle e Commerce Gateway column rules or you chose to ignore option in View Staged Documents window the exception Both Oracle e Commerce Gateway and Oracle Applications provide Reports window
440. nit of measure code DOCUMENT_CODE This column represents the customer assigned schedule reference or release number TEST_INDICATOR This column represents the test or production indicator from the Trading Partner If this value does not match the test or production indicator associated with the trading 6 138 Oracle e Commerce Gateway Implementation Manual partner defined in Oracle e Commerce Gateway a process rule exception is detected and an exception message will display in the View Staged Documents window The valid values are T for test and P for production Note The TEST_INDICATOR is examined by the Demand Processor to determine how far the transaction can proceed through the application Transactions with a TEST_INDICATOR value of T are validated and archived but no further processing is done In the Release Management Workbench Test Transactions require the Test check box to be checked This allows test transactions to be tested in a production environment for front end data validation To fully test a transaction through a test database environment the transactions must be flagged as production to go beyond just the validation This Demand Processor feature facilitates setup and implementation for inbound demand schedules with new trading partners TP_TRANSLATOR_CODE TP_LOCATION_CODE EDI Location Code The two columns in combination uniquely identify a Trading Partner in Oracle e Commerce Gateway Onc
441. ns for running Rapid Install either to carry out a fresh installation of Oracle Applications Release 12 or as part of an upgrade from Release 11i to Release 12 The book also describes the steps needed to install the technology stack components only for the special situations where this is applicable Oracle Applications Upgrade Guide Release 11i to Release 12 This guide provides information for DBAs and Applications Specialists who are responsible for upgrading a Release 11i Oracle Applications system techstack and products to Release 12 In addition to information about applying the upgrade driver it outlines pre upgrade steps and post upgrade steps and provides descriptions of product specific functional changes and suggestions for verifying the upgrade and reducing downtime Oracle Applications Patching Procedures This guide describes how to patch the Oracle Applications file system and database using AutoPatch and how to use other patching related tools like AD Merge Patch OAM Patch Wizard and OAM Registered Flagged Files Describes patch types and structure and outlines some of the most commonly used patching procedures Part of Maintaining Oracle Applications a 3 book set that also includes Oracle Applications Maintenance Utilities and Oracle Applications Maintenance Procedures Oracle Applications Maintenance Utilities This guide describes how to run utilities such as AD Administration and AD Controller used to maintain th
442. nsaction requirements may change when enhancements are made such as additional data added to the transaction Current transaction details can be found on Oracle Support s web site Current detail record layouts are reported via the Transaction Layout Definition Report and the Interface File Data Report Application Transaction Detail 6 177 Note See Oracle Supplier Scheduling Transaction Summaries page A 230 for layout details Outbound Planning Schedule SPSO 830 DELFOR Trading Partner Link to Oracle e Commerce Gateway Suppliers and supplier sites are defined in either Oracle Purchasing or Oracle Payables Included in the definition is the EDI Location Code that trading partners agree to exchange to represent the full detailed address Often they do not send the full address but just the EDI Location Code This is a critical data field to Oracle e Commerce Gateway The EDI Location Code is the link between a supplier supplier site in Oracle Applications and the trading partner site definition in Oracle e Commerce Gateway This enables Oracle e Commerce Gateway to access the detailed data about the supplier or supplier site in the base Oracle Applications without maintaining the detail data in Oracle e Commerce Gateway To ensure that the trading partner link between Oracle e Commerce Gateway and Oracle Applications is set up properly verify that the supplier supplier site and the EDI Location Code in Oracle Applications is the corre
443. nslator for Inbound Transaction Some trading partners may want to use different data segments of the EDI standard or use other standard formats such as XML for inbound transactions The Translator stores 4 32 Oracle e Commerce Gateway Implementation Manual this layout and formatting information in a file called a data map or simply a map This allows the translator to know where to look in the inbound transaction file for the data needed to populate the EDI segment The translator can also use this map to perform code conversions from the values in the Oracle Applications to the EDI standard for weight for example Deciding which code conversions can be done on the Oracle e Commerce Gateway and which on the translator is part of the Synchronization process above One map can serve multiple trading partners Create Data Maps in the Translator for Outbound Transactions Some trading partners may want to use different data segments of the EDI standard or use other standard formats such as XML for outbound transactions The Translator stores this layout and formatting information in a file called a data map or simply a map This allows the Translator to know where to put the data from the EDI segment in the output transaction file The Translator can also use this map to perform code conversions from the values the EDI standard uses to those the Oracle Application expects for weight for example Deciding which code conversions can be done on the Or
444. nt from the View Staged Documents window Otherwise delete the transaction in the View Staged Documents window Research this transaction with the Trading Partner Troubleshooting 8 9 Message Description and Solution UTL_FILE File location or file name was invalid Description This message appears in the concurrent manager log file This message usually indicates that the values specified for the inbound and outbound directories in the utl_file_dir parameter in the INIT ORA file do not match the values indicated in the Profile Options window for the inbound and outbound directories Solution Make the appropriate corrections restart the database only if the INIT ORA file was changed and resubmit the process The following table contains miscellaneous troubleshooting tips Miscellaneous Troubleshooting Tips Symptom Solution The outbound Payment Order Remittance Advice 820 PAYORD REMADV transaction does not appear on the list of transactions on the Oracle e Commerce Gateway Export Process Trouble writing the output file to the specified directory or you cannot find the output file This transaction is event driven and is automatically submitted by the Oracle Payables Payment Workbench process Check the following PROFILE OPTIONS Make sure the profile option for output directory is defined using the correct operating system syntax Use physical directory name do not use logical di
445. nt in the base Oracle Application e The base application initiates a request within Concurrent manager with key data from the transaction to write the transaction to a transaction interface file e Created by a scheduled request within Concurrent Manager Usually the request extracts all eligible transactions that are ready to be extracted You can limit the transactions selected by entering selection parameters in the request Set up appropriate transaction interface file detection in the file directory The file directory is defined in the initial application setup for all transactions in the System Profile Options in the Oracle e Commerce Gateway The Translator needs to be able to access the interface file Follow your file backup and archive procedures and practices that may also need to consider local fiscal requirements Determine the frequency that the Oracle e Commerce Gateway files are processed through the Translator Ideally you should put completed transaction files either in another directory or under other file names so that the Translator cannot access the file until the Oracle e Commerce Gateway is finished with it Determine Communications Methods For The Transactions Ensure that the order in which the processes are performed e g for outbound transactions Oracle e Commerce Gateway processing file transfer archive or Translator fits in with the local environment and other processes being performed around the Orac
446. nt that customers stay current on the latest patch sets provided by Oracle e Commerce Gateway This insures that they have the most recent bug fixes and added functionality Information on the latest patch sets available can be obtained from Oracle Support Services or their web sites Implementation Details 4 3 Prior to running the Release 12 upgrade process it is important to remember to run the two report scripts that are provided These report scripts help identify customizations that may have been made to the existing transaction record layouts any table updates to accommodate extension tables and identifies new code conversion categories that may have been added If you have made any customizations to the seeded data including extension tables or program routines execute the report scripts both before and after you apply the upgrade The before report identifies the current definitions the after report identifies the new definitions after the upgrade has been applied The differences between the two reports identify the customizations that must be evaluated If necessary re implemented your customizations after you apply the upgrade In addition make certain you have complete documentation of software modifications before applying the patch This allows you to easily re apply your changes and make additional changes if the seed data reconciliation could not restore that transaction layout or set up Detailed information on running thes
447. ntified using both the Translator Code and the Location Code then it is the combination of these two codes that must uniquely identify the Trading Partner setup Both the Translator Code and the EDI Location Code can be shared by a number of Trading Partner setups as long as there is only one Trading Partner setup for each combination of codes Multiple Translator Codes per Trading Partner A given address site may use different Translator Codes for different transactions One business entity may route their financial transactions to an electronic mailbox for their financial center while their procurement center uses a different electronic mailbox Trading Partner 9 5 hence different Translator Codes are associated with different transactions The following table shows an example of multiple Translator Codes Example of Multiple Translator Codes Transaction Type Document from Translator Code Address Site from Trading Partner from Trading Trading Partner Detail Tab Partner Detail Tab Assignment Tab POO Outbound Purchase MAILBOX_PROC C SJ EDI Location Orders Code for Supplier Site INI Inbound Invoices MAILBOX_FIN C SJ EDI Location Code for Remit To Site Note Same address site is used for the Supplier and Remit location Shared Translator Codes Note Do Not Assume One Translator Code to One Trading Partner Definition in the Oracle e Commerce Gateway Several organizations or divisions of a Trading Partner may
448. nvoice Contact HEADER 1530 Ordered By Name HEADER 1540 Ship from Address HEADER 1600 Header Level Extension Tables HEADER custom Purchase Order Header Data Credits Data CREDIT 1700 Credit Flexfields CREDIT 1710 1740 Flexfields Price Adjustments PRICE 1800 Data ADJUSTMENT Discount List Names PRICE 1810 for price ADJUSTMENT adjustments Price Adjustment PRICE 1820 1850 Flexfields Flexfields ADJUSTMENT Reservations Data RESERVATION 1900 Reservations RESERVATION 1910 1940 Flexfields Flexfields Action Data ACTION 1950 Action Flexfields ACTION 1960 1990 Flexfields A 14 Oracle e Commerce Gateway Implementation Manual Data Data Level Record Number Note Item LINE 2000 Original System Reference Configuration Inventory Item LINE DETAIL 2010 2020 Flexfields Segments Item Detail Items LINE DETAIL 3000 Price Payment Type Code LINE DETAIL 3020 Tax Exempt Project Task LINE DETAIL 3030 Contract Numbers Service Comments LINE DETAIL 3050 FOB Point Freight LINE DETAIL 3080 Terms Shipment Priority Method Freight Carrier Demand Bucket LINE DETAIL 3090 Shipment quantities LINE DETAIL 4000 dates Shipping amp Packing LINE DETAIL 4010 Instructions Item Flexfields LINE DETAIL 4200 4230 Flexfields Global Header LINE DETAIL 4300 4340 Flexfields Flexfields Pricing Flexfields LINE DETAIL 4400 442 Flexfields Industry Header LINE DETAIL 4500 4560 Flexfields Flexfields Transaction Summa
449. ny record does not exceed 1024 it is mandatory to begin the extension table data with the x900 record The value for Position determines the relative output order of data elements within the specified Record_Number Important Extension table data elements may only be mapped within the range of the corresponding interface table and no single record number may contain more than 1024 bytes of data Modify Procedures to Move Data to the Extension Tables Task Modify the package body code Just as the Extensible Architecture of the Oracle e Commerce Gateway provides extension tables that may be customized to fit the business needs it also provides packaged procedures that may be customized to populate the extension tables with data There is one extension package for each outbound transaction and each extension package contains one procedure for every extension table in that transaction Extension packages consist of two source code files a package specification and a package body with file names in the respective window e ECExxxxXS pls e ECExxxxXB pls where xxxx denotes the unique three or four letter identifier for a given transaction 11 12 Oracle e Commerce Gateway Implementation Manual These source code files are usually found in the directory e APPL_TOP ec admin sql and may be modified with any text editor Only the package body requires modification the package specification file should not be altered For example the
450. o the Trading Partner chapter for recommendations on selecting the correct trading partner EDI Location Code for the control record 0010 for the transaction in the transaction interface file Two Methods of Sending Credit Memos Debit Memos Extract Criteria The 810 INVOIC transaction supports invoices credit memos and debit memos In addition you can use the 812 CREADV DEBADV transaction to send just the credit memos and debit memos The method you chose is dependent on your agreement with your supplier Any credit memo debit memo extracted using the 810 INVOIC transaction will not be eligible for extraction by the 812 CREADV DEBADV transaction The outbound Invoice transaction is controlled by five database views which are defined according to the Oracle Receivable data model for supplier invoices The five views contain variables which are dynamically set based on your responses to the extract program parameters refer to Oracle e Commerce Gateway User s Guide Outbound Transactions chapter for a list of the program parameters The five database views are as follows ECE_INO_ALLOWANCE_CHARGES V ECE_INO_HEADERS 1_V ECE_INO_HEADER_V ECE_INO_LINE_TAX_V ECE_INO_LINE_V Application Transaction Detail 6 129 The ECE_INO_HEADERS_V view is used to identify which supplier invoices are eligible for extraction The extract criteria are as follows e Trading partner is defined e Transaction type invoice credit memo
451. oSchedule All shipping schedules must be confirmed before they are eligible for extraction Schedules may be confirmed using the Scheduler Workbench or in AutoSchedule via the AutoConfirm process The outbound Shipping Schedule transaction is controlled by two database views which are defined according to the Oracle Supplier Scheduling data model for shipping schedules The two views contain variables which are dynamically set based on your responses to the extract program parameters refer to Oracle e Commerce Gateway User s Guide Outbound Transactions chapter for a list of the program parameters The two database views are as follows 6 182 Oracle e Commerce Gateway Implementation Manual e ECE_SSSO_ITEMS V e ECE_SSSO_HEADERS_V The ECE_SSSO_HEADERS_V view is used to identify which shipping schedules are eligible for extraction The extract criteria are as follows e Trading partner is defined e Transaction type enabled for the trading partner e Shipping schedule has not been printed or previously extracted e Shipping schedule defined in Supplier Scheduling with communication code of EDI or BOTH e Shipping schedule has a status of CONFIRMED e Shipping schedule horizon start end dates fall within the organization s period start end dates If necessary you can use SQLPLUS to verify if there are any eligible documents to be extracted To do so you must first set the organization context and then issue the SQL count function as f
452. oach that is e An initial small set of test trading partners to validate correct mapping and identify any initial issues caused by new mapping specifications and or software e A second larger set of trading partners to verify the fixes implemented as a result of the initial trading partner testing e Final testing with the total trading partner community or move directly to production status It is important that acceptance of correct operation at each stage be documented before proceeding to the next stage of testing Implementation Planning The process of sending and receiving an e commerce transaction is relatively simple As with all simple concepts however there is usually a lot of work to do in mapping customer trading partner and Translator requirements to ensure that each stage has the required data in the correct fields Most of the implementation time is taken in these tasks The checklist for the issues involved in a standard Oracle e Commerce Gateway Implementation Positioning 2 7 implementation can be summarized as e Data mapping requirements Trading Partner setups General Code Conversion setups Extension tables for outbound transactions Standards to be used for transactions Relevant functionality in the Oracle Application Required fields and defaults on transaction interface file and Application Open Interface Customer s setup and procedures for using the Applications Changes in procedures o
453. ocess to re validate the transaction If you chose to have the supplier send a corrected transaction you must first purge the rejected invoice data in the Payables Open Interface tables by submitting the Purge Payables Open Interface program and then re import the updated transaction using Oracle e Commerce Gateway Application Transaction Detail 6 79 Trading Partner Link to Oracle e Commerce Gateway Suppliers and supplier sites are defined in either Oracle Purchasing or Oracle Payables Included in the definition is the EDI Location Code that trading partners agree to exchange to represent the full detailed address Often they do not send the full address but just the EDI Location Code This is a critical data field to Oracle e Commerce Gateway The EDI Location Code is the link between a supplier supplier site in Oracle Applications and the trading partner site definition in Oracle e Commerce Gateway This enables Oracle e Commerce Gateway to access the detailed data about the supplier or supplier site in the base Oracle Applications without maintaining the detail data in Oracle e Commerce Gateway To ensure that the trading partner link between Oracle e Commerce Gateway and Oracle Applications is set up properly verify that the supplier supplier site and the EDI Location Code in Oracle Applications is the correct supplier supplier site selected for the Trading Partner definition in Oracle e Commerce Gateway The selected supplier supplie
454. of Data Data Level RECORD Note 1 Control Record HEADER 0010 2 Shipment Notice HEADER 1000 Basic Header 3 Carrier Weights HEADER 1010 Packaging 4 Shipment HEADER 1020 Method of Payment 5 Currency Tax HEADER 1030 Payment Terms 6 Allowances Cha HEADER 1040 rges Freight A 126 Oracle e Commerce Gateway Implementation Manual Seq Type of Data Data Level RECORD Note 7 Hazardous HEADER 1050 Material Special Handling 8 Header Note HEADER 1090 9 Vendor HEADER 1100 Address Code 10 Destination HEADER 1120 Address Code 11 Destination HEADER 1130 Contact 12 Shipment HEADER 1200 1230 Flexfields Header Flexfields 13 Basic Item Data LINE 2000 14 Hazardous LINE 2010 Material Codes 15 Currency Tax LINE 2020 Item Level 16 Notes LINE 2030 17 Shipment Line LINE 2100 2130 Flexfields Flexfields 18 Transaction LINE 2140 2170 Flexfields Flexfields 19 Destination LINE 3000 Address 20 Destination LINE 3020 Location Inbound Shipping and Billing Notice Common Key Transaction Summary Layouts A 127 The following table shows the Common Key positions 1 100 for the Inbound Shipping and Billing Notice transaction The table shows the position length code and content of the Common Key elements Transaction specific Data in the SBNI Transaction Common Key Position Length Code Content 1 25 25 TP_CD Trading Partner Code as defined in the EDI Translator 26 47 22 SHIPMENT Shipment Number 48 69 22 LINE Item Num
455. of the records comprising the Inbound Response to Request for Quotation transaction Record Occurrences Within the RRQI Transaction Records Content Occurrences 0010 Control Record Only one record occurrence per transaction 1000 1999 Transaction Header Only one set of records per request quote 2000 2999 Transaction Item One set of item records per item within the transaction The following table is a summary list of the records comprising the Inbound Response to Request for Quotation transaction The table shows the functional grouping of records the data level the record numbers and relevant notes about the data grouping RRQI Transaction Record Summary Type of Data Data Level Record Number Note 1 Control Record HEADER 0010 2 Transaction HEADER 1000 Identification 3 Currency HEADER 1010 Payment Terms 4 FOB Carrier HEADER 1020 Freight Terms 5 Action Type HEADER 1030 Group Code 6 Comments HEADER 1040 7 Ship to Address HEADER 1100 Transaction Summary Layouts A 111 Type of Data Data Level Record Number Note 8 Bill to Address HEADER 1110 9 Ship From HEADER 1120 Address 10 Header HEADER 1200 1230 Flexfields Flexfields 11 Item LINE 2000 Identification 12 Quantity LINE 2010 Description 13 Prices Dates LINE 2020 14 Payment Terms LINE 2030 Item Level 15 FOB Carrier LINE 2040 Freight Terms Item Level 16 Hazardous data LINE 2050 Weight Volume Lead Time 17 Ship To Data LINE
456. ollowing table shows the Common Key positions 1 100 for the records of the Outbound Purchase Order Change transaction Transaction specific data in the Common Key of the POCI transaction per record Sequen Data Trading Ref 1 Ref 2 Ref 3 Record Record Record ce Partner Number Layout Layout Qualifie r 1 Control TP_CD PO 0010 CT CTL Record 2 Basic TP_CD PO 1000 PO PO1 Purchas e Order Header A 40 Oracle e Commerce Gateway Implementation Manual Sequen Data Trading Ref 1 Ref 2 Ref 3 Record Record Record ce Partner Number Layout Layout Qualifie r 3 Change TP_CD PO 1010 PO CHG Data 4 Change TP_CD PO 1020 PO CCl Comme nt 1 5 Change TP_CD PO 1030 PO CC2 Comme nt 2 6 Change TP_CD PO 1040 PO CC3 Comme nt 3 7 Change TP_CD PO 1050 PO CC4 Comme nt 4 8 Currenc TP_CD PO 1060 PY CUR y Code amp Convers ion Rates 9 Paymen TP_CD PO 1070 PY TAX t Amount Credit Card Paymen t Type C ode Tax Exempt Transaction Summary Layouts A 41 Sequen ce Data Trading Ref 1 Ref 2 Ref 3 Partner Record Record Number Layout Record Layout Qualifie r 10 11 12 13 14 15 16 17 FOB Point Freight Terms Shipme nt Priority Shippin 8 Method Shippin g amp Packing Instructi ons Deman d Class Header Flexfiel ds 1 4 Header Flexfiel ds 5 9 Header Flexfiel ds 10 14 Header Flexfiel d15 Purchas e Order Flexfiel ds 1 4
457. ollows SQLPLUS gt execute fnd_client_info set_org context lt Org number gt SQLPLUS gt select count ECE SSSO HEADERS V Review all your set ups if the count value is 0 as this indicates there are no eligible documents to be extracted Columns Updated Upon Extraction Once an eligible shipping schedule is successfully extracted and written to the transaction interface file it is marked by Oracle e Commerce Gateway to prevent it from subsequent extraction The following table lists the fields updated in the CHV_SCHEDULE_HEADERS table based on an excerpt of code in the UPDATE_CHV_SCHEDULE_HEADERS procedure defined in the ECSPSOB pls file This file is shared by both the Planning and Shipping Schedule transaction with specific procedure calls to support each transaction Column Value EDI_COUNT Increment by 1 LAST_EDI_ DATE SYSDATE Application Transaction Detail 6 183 Column Value LAST_UPDATED_BY LAST_UPDATE_DATE COMMUNICATION_CODE 1 SYSDATE see below COMMUNICATION_CODE is set based on the original value as shown in the following table Original Extract Successful Set New COMMUNICATION_CODE COMMUNICATION_CODE BOTH Yes EDI Yes PRINT NONE 6 184 Oracle e Commerce Gateway Implementation Manual l Test Transactions This chapter contains test transactions for Oracle e Commerce Gateway implementation This chapter covers the followi
458. olumn names are used to dynamically build a select statement that is used to select data to compare to the assigned column The tables may be user defined tables outside of the Oracle Applications For example of a Simple Lookup the dynamically built select statement is select lookup_code from ece_lookup_values If the incoming transaction value does not exist in the list of selected values then this rule is violated No List of Value LOV is provided for the table column or condition field Instead a Validate button may be used to verify the syntax of the dynamically built select statement e Valueset Lookup This rule is used to compare the value in the assigned column to an Oracle Implementation Details 4 15 Application Valueset e Value is Required This rule checks if the incoming data for a given column has a non null value If it is null then it violates the rule General guidelines regarding column rule definitions are as follows e Acolumn may have more than one rule defined e Acolumn may have the same rule defined multiple times each with different conditions e The same rule may apply to multiple columns of a given transaction e Different rules for a given column can have different rule actions see below regarding Rule Action Precedence Seeded Column Rules Each inbound transaction is seeded with column rules for required fields date fields and numeric fields The default settings for column rule and rule actio
459. om the base Oracle Application Data that is stored in additional columns in Oracle application tables which are not in the standard Oracle Implementation Details 4 21 application or Oracle e Commerce Gateway configuration may also be written to the extension tables Refer to Extensible Architecture chapter for details Interface File Definition The size location and relative order of the fields processed by Oracle e Commerce Gateway can be modified using the Interface File Definition window The width of a field may be increased or decreased to suit customer or standards requirements The relative position of a field within the interface file record may be changed or a field may be activated to appear in the transaction interface file by allocating it a record number relative position and column width Alternatively fields may be inactivated if they are not required for example to reduce inbound outbound file sizes though it is recommended that the reasons for deactivating fields other than not used flexfields be well understood e External code conversion fields may be renumbered changing the position numbers to allow them to be inserted into or read from the interface file in a different order to their position in the Interface File Definition display refer to the Oracle e Commerce Gateway User s Guide However changing the position number impacts the data map in the Translator Newly activated columns may be positioned
460. omizations such as extension tables are implemented e Oracle Payables User s Guide Oracle e Commerce Gateway Overview e Business Integration Oracle e Commerce Gateway is a standards based integration product for Oracle Applications This integration product allows you to integrate Oracle Applications with applications residing inside or outside of your enterprise communicating via the Intranet Extranet or the Internet Oracle e Commerce Gateway evolved from the Oracle EDI Gateway product focusing on Electronic Data Interchange EDI into a product focused on e business integration All the features and functions of Oracle EDI Gateway are retained and enhanced to create the Oracle e Commerce Gateway product Oracle e Commerce Gateway supports seamless integration streamlined 1 2 Oracle e Commerce Gateway Implementation Manual implementation and rule based transaction processing to automate your business operations The major features include e Open and Extensible Architecture e Streamlined Transaction Implementation e Configurable Integration Environment e Rule Based Process Management e Multiple Organization Access Control by Security Profile e Reports Oracle e Commerce Gateway is designed with an open and extensible architecture for easy integration with any third party application The product is designed with self contained yet integrated modules focused on ease of implementation you simply define the business
461. ommerce Gateway Implementation Manual X12 850 X12 850 e Commerce e Commerce Order Import Transaction Transaction Gateway POI Gateway POI Level Level Segment File File Data Transaction Content Record Shipment SCH 3000 4000 Shipment Data LINE second for Item with second Item 1 shipment 1 shipment 2 Shipment SCH 3000 4000 Shipment Data LINE third for Item 1 with third Item 1 shipment shipment 3 Line Item 2 POI 2000 Basic PO item 2 for first shipment Shipment first SCH 3000 4000 Shipment Data LINE for Item 2 with first shipment Item 2 shipment 1 Shipment SCH 3000 4000 Shipment Data LINE second for Item with second i 2 shipment Item 2 shipment 2 Shipment third SCH 3000 4000 Shipment Data LINE for Item 2 with third shipment Item 2 shipment 3 Shipment fourth SCH 3000 4000 Shipment Data LINE for Item 2 with fourth i shipment Item 2 shipment 4 Note An X12 Schedule SCH Segment contains Order Management Shipment data The following table illustrates the e Commerce Gateway Inbound Purchase Order transaction structure with more detail Application Transaction Detail 6 11 e Commerce Gateway Inbound Purchase Order Transaction Structure e Commerce Gateway POI Transaction Record e Commerce Gateway POI Transaction Record Data Content Order Import Level 1000 2000 2010 2020 3000 4000 3000 4000 3000 4000 2000 2010 Schedule Header Ite
462. ommerce Gateway allows you to associate Trading Partner groups with operating units restricted to the security profile linked to your responsibility All Trading Partners within the groups are assigned to the same operating units the associated Trading Partner addresses for the same operating units can be viewed and set up For example the seat suppliers group for a car manufacturer is associated with the Vision USA operating unit all Trading Partners and the associated addresses within the seat suppliers group are all assigned to the same operating unit Vision USA When multiple operating units are associated with your responsibility if you want to associate a different set of addresses for the same Trading Partner group and same Trading Partner then you have to reselect the operating unit such as change it from Vision USA to Vision Europe in the Trading Partner Group form first and then change the setup for the underlying Trading Partners This way the associated Trading Partner 9 2 Oracle e Commerce Gateway Implementation Manual addresses for Vision Europe can be viewed for selection when defining Trading Partners for the group The operating unit is relevant to the underlying addresses only and not to the Trading Partner groups or Trading Partner headers The Trading Partner group title is a free text field that is not used in any EDI processing It may consist of any title that is meaningful to your organization EDI Location Codes
463. omplete then the imported catalog must be approved before it is archived If the Approval Status was set to Approved then the imported catalog is archived immediately after it is imported into Oracle Purchasing Application Transaction Detail 6 99 e If the profile option is set to No Oracle Purchasing will not archive the price sales catalog 2 Allow Updating of the Item Master e Create or Update Item Master is one of the program parameters to indicate whether to allow creation of a new item or updating of an existing item in the item master e To ensure that item descriptions and item status codes may be updated the following must be set up Allow Item Description Update is enabled in the Purchasing Options window Control Options region INV Default Item Status is set to Active 3 PO Write Server Output to File To facilitate the debugging of the Purchasing Documents Open Interface error logs normally written to the Concurrent Manager log screen may be written to the file system if this profile option is set to Yes 4 Set Up Price Tolerance Define price tolerances in Oracle Purchasing for price increases associated with a price sales catalog update Purchasing Documents Open Interface Required Fields The Purchasing Documents Open Interface is used by the Inbound Price Sales Catalog and Inbound Response to Request for Quotation transactions It is used to validate the incoming data entered into the Purchasing Do
464. on Record Summary Data Data Level Record Number Note 1 Common CONTROL 0010 Control Record 2 Basic Schedule SCHEDULE 1000 Header HEADER 3 Schedule Header SCHEDULE 1010 Note Text HEADER 4 Schedule Issuer SCHEDULE 1020 Address Code HEADER Transaction Summary Layouts A 203 Data Data Level Record Number Note 5 Schedule Header SCHEDULE 1030 Misc Contacts HEADER 6 Schedule Header SCHEDULE 1040 Misc References HEADER 7 Schedule Header SCHEDULE 1100 1130 Flexfields Flexfields HEADER 8 Trading Partner SCHEDULE 1200 1230 Flexfields Header HEADER Flexfields 9 Ship To Address SCHEDULE 1300 Code HEADER 10 Bill To Address SCHEDULE 1310 Code HEADER 11 Intermediate SCHEDULE 1320 Ship To Address HEADER Code 12 Supplier Ship SCHEDULE 1330 From Address HEADER Code 13 Miscellaneous SCHEDULE 1340 Name Codes and HEADER Values 14 Extension SCHEDULE 1900 Custom Tables Schedule HEADER Header Data 15 Basic Item Data SCHEDULE 2000 ITEM 16 Product SCHEDULE 2010 Description Data ITEM A 204 Oracle e Commerce Gateway Implementation Manual Data Data Level Record Number Note 17 Additional Item SCHEDULE 2020 2030 Data ITEM 18 Unit of Measure SCHEDULE 2040 ITEM 19 Item SCHEDULE 2050 Measurements amp ITEM Physical Qualities 20 Item Misc SCHEDULE 2060 References ITEM Codes and Values 21 Item Contact SCHEDULE 2070 Names ITEM 22 Bar code SCHEDULE 2080 2090 Shipping Label ITEM data 23 Ship To Address
465. on process For inbound transactions the directories must be the directory the file is deposited into by the communication process the directory the translator picks up the file from the directory the pre translation file is archived into the directory the Translator writes the translated interface file into and the directory the Oracle e Commerce Gateway reads the file from 4 34 Oracle e Commerce Gateway Implementation Manual Outbound Directory Structure A sample set of directories and files are listed below D outbound_flat_file Directory the Oracle e Commerce Gateway places outbound transaction files It should be defined in UTL_FILE_DIR in the init ora file and the Oracle e Commerce Gateway profile ece outbound file path D outbound_flat_file archive Directory the files from the Oracle e Commerce Gateway are copied into after generation The reason for having this directory and the next one separate the source of file generation so the translator cannot attempt to open a file the Oracle e Commerce Gateway is generating D outbound_flat_file Translator_input Directory the Translator reads its input file from Although this can be the same as the Oracle e Commerce Gateway archive directory it generally should not be This is because the translator usually looks in the outbound directory and reads every file in it It assumes that if the file is in this directory it should be processed D outbound_flat_file Translator_
466. on whether you are importing a new catalog catalog changes or replacing an existing catalog Refer to the Oracle Purchasing Open Interfaces document Sourcing section for a detail description of how this data is used EXPIRATION_DATE Application Transaction Detail 6 103 This column is required if you want to create sourcing rules i e if you answered YES to Create Sourcing Rules parameter along with importing a new or replacement catalog If you are importing catalog changes the value is used to retire the old catalog item Refer to the Oracle Purchasing Open Interfaces document Sourcing section for a detail description of how this data is used ITEM ITEM_DESCRIPTION These two columns are required if you want to create or update an item in the item master i e if you answered YES to the Create or Update Item parameter If you are creating new items both ITEM and ITEM DESCRIPTION are required If you are updating the item master ITEM DESCRIPTION is required LINE_NUM SHIPMENT_NUM QUANTITY UNIT_PRICE To enter price break data the supplier must provide line number shipment number quantity and unit price on the transaction interface file in the format shown in the following table to accommodate Oracle Purchasing s data model Line Number Rec Shipment Number Quantity Rec 2010 Unit Price Rec 2000 Rec 2050 2020 1 1 500 10 00 1 2 1000 7 00 1 3 5000 5 00 The price break data is loaded by Oracle e
467. onfigurations above OPTION_NUMB OPTION_NUMB_ See 2000 110 ER ER Configurations above COMPONENT_ COMPONENT_ See 2000 120 CODE CODE Configurations above SORT_ORDER SORT_ORDER See 2000 130 Configurations above LINE_NUMBER LINE_NUMBER If Null derived 2010 020 6 30 Oracle e Commerce Gateway Implementation Manual Oracle Oracle Hardcoded Deri Record Number Position Applications e Commerce ved Number Column Name Gateway for Fields Column Name CUSTOMER_LI CUSTOMER_LI If Null set to 2010 030 NE_NUMBER NE_NUMBER LINE_NUMBER ITEM_TYPE_CO ITEM_TYPE_CO If Null default 2010 080 090 DE DE to STANDARD CALCULATE_P CALCULATE_P If Null default RICE FLAG RICE FLAG to Y for yes CREATED_BY CREATED_BY Derived CREATION_DA CREATION_DA Set toSYSDATE TE TE DELIVERY_ID DELIVERY_ID Derived LAST_UPDATE LAST_UPDATE _ Set toSYSDATE _DATE _DATE LAST_UPDATE LAST_UPDATE Derived D_BY D_BY ORDER_SOURC ORDER _SOURC Hard code 6 E_ID E_ID meaning EDI READY_FLAG READY_FLAG Set to Y for yes Shipment Dates 3000 many CUSTOMER_SH CUSTOMER_SH Increment by 4000 040 IPMENT_ IPMENT_ one for each set of shipment data NUMBER NUMBER Aitua an item that is identified by the same CUSTOMER _LI NE_NUMBER Ship to Location 3800 many Line Level Application Transaction Detail 6 31 Note Column names denoted with _EXT1 indicates that it can have code conversion for that data element Either the internal value or the external value will be p
468. only U Split payment and remittance advice Z Other types of handling 1 Verify that the invoices you wish to pay electronically are defined with Electronic as the payment method 2 Verify that the invoices you wish to pay do not have active holds placed on them 3 Approve the invoices you wish to pay 4 Verify that you have confirmed the default remit to bank account for each scheduled payment 5 Create a Pay Group type lookup specifically for EDI payments to separate the non EDI payments from the EDI payments This is an optional set up step 6 Create the Payment Batch Refer to the Initiating Payment Batches section Oracle Payables User s Guide for details 7 Refer to the Modifying Payment Batches section Oracle Payables User s Guide for details on how to modify a payment batch if necessary 8 Format the Payment Batch This process initiates the Oracle e Commerce Gateway outbound Payment Order Remittance Advice transaction that creates a transaction interface file Extract Criteria The outbound Payment Order Remittance Advice transaction is controlled by two Application Transaction Detail 6 71 database views that are defined according to the Oracle Payables data model for payments and their corresponding invoices The two views contain variables which are dynamically set based on your responses to the extract program parameters refer to the Outbound Transactions chapter Oracle e Commerce Gateway User s
469. ons e Trading partner link between Oracle e Commerce Gateway and Oracle Applications e Oracle e Commerce Gateway Required Fields e Review Oracle e Commerce Gateway Exceptions e Resolve Oracle e Commerce Gateway Exceptions e Relevant Application Profiles and set Ups e Oracle Application Open Interface Required Fields e Review Application Open Interface Exceptions e Resolve Application Open Interface Exceptions Verify Oracle e Commerce Gateway Setups Verify the following in the Oracle e Commerce Gateway e System profiles are set e Relevant transaction profiles are set e Trading partner is defined and linked to Oracle Applications 7 2 Oracle e Commerce Gateway Implementation Manual Transaction is enabled at the system profile level as well as at the trading partner detail level Relevant code conversions are defined Relevant process rule actions are defined Relevant column rules and associated actions are defined Structure of the transaction interface file received matches the definition reported using the Oracle e Commerce Gateway Transaction Layout Definition Report Transaction interface file contains valid values for all Oracle e Commerce Gateway required fields Review this using the Oracle e Commerce Gateway Interface File Data Report Verify Oracle Applications Setups Verify the following in the appropriate Oracle application Relevant application profile and set ups are defined Transaction interface file conta
470. options shows the following information 8 14 Oracle e Commerce Gateway Implementation Manual Status Transaction Trading Partner Number of Documents Total Violations Status of selected documents currently in the staging table The transaction name Trading Partner name for the selected transactions Number of documents for given status transaction type and trading partner Total number of exceptions including all the processing and column exceptions for given status transaction type and trading partner The status level 4 summary for the Status options shows the following information Status Transaction Trading Partner Map Document Number Level Process Violations Column Violations Status of selected documents currently in the staging table The transaction name Trading partner name for the selected transactions The transaction map code The primary identifier for the document in the staging table The value depends on the transaction such as POI for PO Number INI for Invoice Number The text description of the level Total number of process exceptions for the given document Total number of column exceptions for the given level of the document Process Violation and Column Violation Buttons At the bottom of the status level window are two buttons labeled Process Violations and Columns The Process Violations button opens the Process V
471. or layout details Transaction Direction Transaction ASC X12 EDIFACT Name Code Invoice Inbound INI 810 INVOIC Shipment and Inbound SBNI 857 N A Billing Notice Application Outbound ADVO 824 APERAK Advice Payment Outbound PYO 820 PAYORD REMA Order Remittanc DV e Advice PAYEXT REMA DV The topics covered for inbound transactions include the following e Trading Partner Link to Oracle e Commerce Gateway e Oracle e Commerce Gateway Required Fields e Review Oracle e Commerce Gateway Exceptions e Resolve Oracle e Commerce Gateway Exceptions e Relevant Oracle Payables Profiles and Set Ups e Payables Open Interface Required Fields e Review Payables Open Interface Exceptions e Return Application Advice to Trading Partner if appropriate 6 64 Oracle e Commerce Gateway Implementation Manual e Resolve Payables Open Interface Exceptions The topics covered for outbound transactions include the following e Two forms of Electronic Funds Transfer EFT e PAYORD PAYEXT PAYMUL e Pre note Payment e Transaction Handling Options e Trading Partner Link to Oracle e Commerce Gateway e Relevant Oracle Payables Profiles and Set ups e Extract Criteria e Columns Updated Upon Extraction Current Information The transaction requirements may change when enhancements are made such as additional data added to the transaction Current transaction details can be found on Oracle Support s web site Current detail record
472. or customer site in the base Oracle Applications without maintaining the detail data in Oracle e Commerce Gateway 6 128 Oracle e Commerce Gateway Implementation Manual To ensure that the trading partner link between Oracle e Commerce Gateway and Oracle Applications is set up properly verify that the customer customer site and the EDI Location Code in Oracle Applications is the correct customer customer site selected for the Trading Partner definition in Oracle e Commerce Gateway The selected customer customer site and the EDI Location Code defined in Oracle Applications are displayed in the Define Trading Partners window Assignment tab If the data is not what you intend it to be you must make the appropriate changes for the transaction to be extracted for the correct trading partner This could involve either altering the customer customer site in the base Oracle Application or assigning a different customer customer site to that EDI Location Code in Oracle e Commerce Gateway Please note that if the trading partner is associated with multiple operating units then the transaction to be extracted is for a specified operating unit only linked to your responsibility To extract all the data for multiple operating units you still need to execute the program one by one by specifying different operating unit each time when you run the program See the Outbound Transactions chapter in the Oracle e Commerce Gateway User s Guide for details Refer t
473. or receive data from trading partners after the data is mapped to the desired standard format Outbound Process Flow Oracle e Commerce Gateway outbound transaction process creates interface data files to support any EDI Standard that is available from the Translator Oracle e Commerce Gateway collects all of the business data needed to map to a standard EDI transaction which the receiving Trading Partner can interpret properly into their receiving application using their equivalent of Oracle e Commerce Gateway Translator setup Oracle e Commerce Gateway extracts the data from the base application tables and optionally extracts data from other files tables via extension tables The use of extension tables requires the customization of standard code packages provided with Oracle e Commerce Gateway Oracle e Commerce Gateway does the following 1 12 Oracle e Commerce Gateway Implementation Manual Reviews the System and Transaction profiles Gets Trading Partner processing parameters e g location codes allowable enabled EDI transactions etc Extracts data from Oracle base applications tables relevant to the transaction being processed Optionally retrieves data from customer defined extension tables requires some customization Applies code conversions when set up and activated Populates Oracle e Commerce Gateway tables with all the data gathered Sets the data extract flags in the base Oracle Application table to prevent
474. or reporting and error research tools it is easier to do as much pre validation as possible via Oracle e Commerce Gateway so that you can centralize the error research effort This way all errors may be reviewed and resolved at the same time allowing the transaction to be reprocessed in a timely manner Column Rules and Code Conversion Rule Actions Oracle e Commerce Gateway applies code conversion prior to applying the column rules therefore you can define a column rule for a column allocated for the internal value although the actual value is not placed on the transaction interface file but is derived during code conversion This derived value will be validated using the column rule and then placed in the Application Open Interface table if valid or staged if invalid Refer to Set Up Code Conversion for more details Each process or column rule requires a rule action that tells Oracle e Commerce Gateway how to proceed if an exception is detected There are four rule actions as follows e Skip Document This action skips the current document and continues processing the next document You can view the detected exceptions for this document via the View Staged Documents window e Log Only This action writes a message to the log file It treats the document as a successful document and continues processing the remaining documents e Abort Run This action rolls back the entire run and sets the concurrent request status to Error e Disab
475. ord Number Position Applications e Commerce ved Number Column Name Gateway for Fields Column Name CREATED _BY CREATED_BY Derived from the CREATION_DA TE LAST_UPDATE _DATE LAST_UPDATE D_BY ORDER_SOURC E_ID SOLD_TO_ORD _ID CREATION_DA TE LAST_UPDATE _DATE LAST_UPDATE D_BY ORDER_SOURC E_ID SOLD_TO_ORD _ID Requester ID for the concurrent manager request that Set to SYSDATE Set to SYSDATE Derived from the Requester ID for the concurrent manager request that Please check Hard code 6 meaning EDI Derived during the Trading Partner lookup given the EDI Location code and Translator code on Control Record 0010 Sample columns from the OE_LINES_INTERFACES table Application Transaction Detail 6 29 Sample Columns from the OE_LINES_INTERFACES Table Oracle Oracle Hardcoded Deri Record Number Position Applications e Commerce ved Number Column Name Gateway for Fields Column Name ORIG SYS_DOC ORIG SYS_DOC If Null derived 2000 030 UMENT_REF UMENT_REF ORIG SYS_LINE ORIG SYS_LINE If Null derived 2000 040 _REF _REF ORIG _SYS_SHIP ORIG SYS_SHIP If Null derived 2000 050 MENT_REF MENT_REF OPERATION _C OPERATION_C _ If Null default 2000 060 070 ODE ODE _EXT1 to INSERT TOP_LINE_LMO TOP_LINE_MO_ See 2000 080 DEL_REF DEL_REF Configurations above LINE_TO_LINE LINE_TO_LINE See 2000 090 _REF _REF Configurations above MODEL_GROU MODEL_GROU_ See 2000 100 P_NUMBER P_NUMBER C
476. organization as defined in Oracle Applications This is the standard identified for the document enabled for the Trading Partner This is the batch control number from the outer most electronic envelope for inbound transactions only This is the ASC X12 ISA or EDIFACT UNB control number This is the batch control number from the inner electronic envelope for inbound transactions only This is the ASC X12 GS or EDIFACT UNG control number This is the batch control number from the starting transactions segment for inbound transactions only This is the ASC X12 ST or EDIFACT UNH control number 5 14 Oracle e Commerce Gateway Implementation Manual Optional Outbound Trading Partner Flexfield Records 0020 0070 For outbound transactions you may enable descriptive flexfield data at the Trading Partner header level Record Numbers 0020 0050 and at the Trading Partner Detail level Record Numbers 0060 0070 The Trading Partner header level flexfields are written for every transaction type for the Trading Partner such as all their outbound purchase order transactions and all their outbound purchase order change transactions The Trading Partner detail level flexfields are written for the transaction type enabled for the Trading Partner This flexfield data is written to the outbound transaction interface file whenever the flexfields are defined They are available for data mapping by the Translator The records m
477. ory This option assumes you do not want to inspect the goods DELIVER_TO_PERSON_NAME DELIVER_TO_LOCATION_CODE_INT These two columns are required by the Receiving Open Interface if AUTO_TRANSACT_CODE is set to DELIVER It represents the deliver to information associated with the requester ITEM_NUMBER PRODUCT_DESCRIPTION These two columns represents the buyers item number and item descriptions as defined in Oracle Purchasing ITEM_REVISION 6 118 Oracle e Commerce Gateway Implementation Manual This column represents the item s revision level A value is required if this is an inventory item under revision control and you have distributions with an inventory destination ORIGINAL_SYSTEM_LINE_REFERENCE This column represents the purchase order line number associated with the shipment PURCHASE_ORDER_NUM This column represents the purchase order number associated with the shipment SHIP_TO_INT_LOCATION_ID SHIP_TO_INT_LOCATION_NAME These two columns represents the destination organization for the shipment A valid inventory organization code in Purchasing is required for the Inbound Ship Notice Manifest or Inbound Shipment and Billing Notice transactions If no values are provided at the line level the header values are used as the default for all lines SHIPPED_QUANTITY This column represents the shipment quantity SHIPPED_UNIT_CODE_INT This column represents the shipment quantity unit of measure VENDOR_ITEM_NUM This colu
478. ose The manner in which the data is organized and structured plays a large part in determining its usefulness for a particular function For example a Ship Notice modeled in a Delivery Container Item organization would facilitate the receiving and inspection process where the focus is on verifying the number of containers such as pallets bins and racks received and the number and type of items in each container Conversely a Ship Notice modeled in a Delivery Order Item organization would be better for a process of reconciling received goods against orders where information such as total item quantities order numbers lot numbers and serial numbers are more useful The Oracle e Commerce Gateway presents the data for the Ship Notice Manifest from the Delivery Container Item perspective Container items are associated with their corresponding Order and Detail data so that the EDI translator may invert the levels in the transaction ot meet the trading partner s specific needs Transaction Summary Layouts A 229 Oracle Supplier Scheduling Transaction Summaries Oracle Supplier Scheduling Transactions Transaction Direction Transaction ASC X12 EDIFACT Name Code Planning Outbound SPSO 830 DELFOR Schedule Shipping Outbound SSSO 862 DELJIT Schedule Current Information The transaction file may change when enhancements are made such as additional data added to the transaction Current transaction summaries can be found on Oracl
479. otation Ship Inbound ASNI 856 DESADV Notice Manifest Shipment and Inbound SBNI 857 N A Billing Notice Application Outbound ADVO 824 APERAK Advice Purchase Order Outbound POO 850 ORDERS Purchase Order Outbound POCO 860 ORDCHG Change The topics covered for inbound transactions include the following e Trading Partner Link to Oracle e Commerce Gateway e Oracle e Commerce Gateway Required Fields e Review Oracle e Commerce Gateway Exceptions e Resolve Oracle e Commerce Gateway Exceptions e Relevant Oracle Application Profiles and Setups e Oracle Application Open Interface Required Fields e Review Application Open Interface Exceptions e Return Application Advice to Trading Partner if appropriate e Resolve Application Open Interface Exceptions The topics covered for outbound transactions include the following 6 96 Oracle e Commerce Gateway Implementation Manual e Trading Partner Link to Oracle e Commerce Gateway e Relevant Oracle Purchasing Setups e Extract Criteria e Columns Updated Upon Extraction Current Information The transaction requirements may change when enhancements are made such as additional data added to the transaction Current transaction details can be found on Oracle Support s web site Current detail record layouts are reported via the Transaction Layout Definition Report and the Interface File Data Report Inbound Price Sales Catalog CATI 832 PRICAT Inbound Response to Request for Quotation R
480. oviders They may not provide predefined data maps for all standards but their software should provide a means to handle any to any data mapping Another key feature provided by the Translator is communication error and format checking to ensure that invalid messages are rejected and returned Translator software normally provides built in support for one or more of the EDI standards and communication methods It may also offer support for pre packaged extension products that include proprietary file formats EDI Translators perform the following main functions 1 Integrated Audit Trail Provides an audit trail of transaction activity and profile updates 2 Trading Partner Identification Trading partner identifications are maintained to define which transactions are enabled for test or production which EDI standard and its version release to map the data define data for the electronic envelope define the communications method to be used etc 1 14 Oracle e Commerce Gateway Implementation Manual Standards Translation Maintains ASC X12 and EDIFACT transaction tables for all versions releases XML and other standards as needed Data Mapping Provide data mapping facilities between proprietary formats and the standards Communications Provides scripts to access popular VANs and VASPs They also have the capability to send data over the Internet Short term Transaction Archival Requeues transactions to transmit again a
481. ow enables code conversion on a column and specifies which columns to examine for the actual search key values You decide which columns are used as the Key1 through Key5 The following were set up for this transaction e Column is CARRIER_INT e The Category SHIP_VIA is assigned to CARRIER_INT to enable code conversion e Key 1 is assigned the CUSTOMER_NAME column in the transaction table e Key 2 is assigned the CUSTOMER_SITE column in the transaction table You selected the keys from a list of values The full search key to access the code conversion value table for inbound transactions include the code category direction Key 1 Key 2 and the 1 5 external code For example the first entry in the table includes the following search key values See the sample Code Conversion Value Table for all entries Key 1 has value ALPHA for the CUSTOMER_NAME Key 2 has value 1006 for the CUSTOMER_SITE The Code Conversion Value window includes the search key values applicable to the internal and external codes for all the Trading Partners and all transactions The Category that you assign to a column limits the access to just those table entries that have been assigned that Category Creating the Search Key The table below has data found in the transaction or derived by the Oracle e Commerce Gateway The data was moved to the transaction columns in the Oracle e Commerce Gateway for processing 10 30 Oracle e Commerce Gateway Implementatio
482. ows an example of transactions separated into different locations by the sending Trading Partner Trading Partner 9 21 Example of Separating Transactions into Different Locations Sending Sending Sending Receiving Receiving Note on Trading Trading Trading Trading Process Partner Partner Partner Trading Partner Partner set up Assume Send to Organization different Items must same EDI separate Location be booked to Mailbox but each Codes with different different location into the same Organization Functional separate physical s Group files for address processing in the Oracle e Commerce Gateway Location Enter orders Mailbox Location This address The EDI Code ABC A for 123456789 Code site ID has Translator for organization writes data Items A B C functional ABC A has AN from EDI 11 State St group 900 table address mailbox Chicago IL site ID 97531 123456789 with functional group 900 to the file for Organization A for the Oracle e Commerce Gateway Location Enter orders Mailbox Location This address The EDI Code ABC B for Items X 123456789 Code site ID has Translator XVZ organiza tion writes data for 11 State functional ABC B has B from EDI St Chicago group 911 table address mailbox IL site ID 54321 123456789 with functional group 911 to the file for Organization B for the Oracle e Commerce Gateway The following table shows a sample of transactions separated into different electronic
483. p in addition to the summary items in the software upgrade e System options for the inbound and outbound directory paths are defined in the system profile and match the UTL_FILE_DIR settings in INIT ORA file e System and transaction profile setups are entered e Transaction specific options have been implemented as needed Oracle e Commerce Gateway Implementation Checklist 3 9 4 Implementation Details This chapter contains Oracle e Commerce Gateway implementation details This chapter covers the following topics e Define Responsibilities e Define UTL_FILE_DIR Parameter in INIT ORA File e Review Release 12 Upgrade Guideline e Set Up Profiles e System Profile Window e Transaction Profile Window e Transaction Specific Options e Outbound Purchase Order Transaction Profile e Determine Process and Column Rules and Actions e Enable Additional Transaction Data e Modify Transaction Interface File e Synchronize New Transaction Layout Definitions with Translator e Common Transaction Interface File Definition Errors e Set Up Trading Partners e Common Setup Errors e Set Up Code Conversion e Interface with Translators e Communications e Archive Backup Implementation Details 4 1 Define Responsibilities The System Administrator must assign the Oracle e Commerce Gateway responsibility to the intended users of the Oracle e Commerce Gateway database and windows Responsibility System Administrator Task Assign
484. plication advice provided by one of the following three inbound transactions e Ship Notice Manifest from Oracle Purchasing Receivables e Shipment and Billing Notice from Oracle Purchasing Receivables e Invoice from Oracle Payables Refer to the details for the relevant inbound transaction to determine how it populates the ECE_ADVO_HEADERS and ECE_ADVO_DETAILS tables If necessary you can use SQLPLUS to verify if there are any eligible documents to be extracted To do so you must first set the organization context and then issue the SQL count function as follows 6 66 Oracle e Commerce Gateway Implementation Manual SQLPLUS gt execute fnd_client_info set_org context lt Org number gt SQLPLUS gt select count ECE ADVO HEADERS V Review all your set ups if the count value is 0 as this indicates there are no eligible documents to be extracted Columns Updated Upon Extraction Once an eligible application advice is successfully extracted and written to the transaction interface file it is marked by Oracle e Commerce Gateway to prevent it from subsequent extraction The following fields are updated based on an excerpt of code in the ECADVOB pls file to update the ECE_LADVO_HEADERS table e EDI_PROCESSED_FLAG value updated to Y e EDI_PROCESS_DATE value updated to SYSDATE Outbound Payment Order Remittance Advice PYO 820 PAYORD PAYEXT REMADV Two Forms of Electronic Funds Transfer EFT
485. ponsibility The following example illustrates the same EDI Location Code coming from two Trading Partners defined in two organizations Suppose both Trading Partners use the same code AB123 In the base Oracle Application the EDI locations are defined as two address sites 9 18 Oracle e Commerce Gateway Implementation Manual Example of EDI Location Code in Multiple Organizations Custome Address Trading Trading base Organiza ror Site Partner s Partner Oracle tion for Supplier Translat Location Applicati the or Code Code on on has Address N1 or two Site ID NAD Address segment Site IDs Acme 123 Main EI ACM AB123 12345678 A Inc St E Chicago IL Beta Inc 123Main E3 BETA AB123 13567890 B St Chicago IL Note The address Site column ID is assigned through the Trading Partner Assignment tab It is retrieved by the Oracle e Commerce Gateway during transaction processing The Organization is defined in the base Oracle Application for this address site It is not validated by the Oracle e Commerce Gateway It may be passed to the Application Open Interface table given the Address Site ID that is retrieved by the Oracle e Commerce Gateway If the EDI responsibility has organization A and the Trading Partner sites in the transactions are defined to organization B in the base Oracle Application then EDI Location Codes cross reference process will not successfully find the addresses in the base Oracle app
486. port output if application report is available Printing and Extract of Documents Once the documents are extracted by Oracle e Commerce Gateway they are flagged to prevent them from being extracted again If you have a situation where some documents are printed and sent while others are electronically transmitted to the Trading Partner you must first print the subset of documents before extracting the balance for electronic transmission A given document can be delivered only once to the Trading Partner Refer to Application Transaction Detail for the details regarding which fields are updated upon extraction Some Oracle Applications do allow re printing of documents previously sent or electronically transmitted refer to your application s User s Manual for the specifics related to the outbound transaction you are implementing Printing and electronically transmitting the same document to your Trading Partner is not recommended Use this approach during the testing phase and initial implementation only Using this approach as standard business practice could create confusion for your Trading Partner as they will not know which copy represents the legal document or worse they may process duplicate transactions 7 6 Oracle e Commerce Gateway Implementation Manual 8 Troubleshooting This chapter contains troubleshooting information about Oracle e Commerce Gateway implementation This chapter covers the following topics Trouble
487. position 110 The default value is NEW if no value is provided on the inbound flat file The value entered for TRAN PURPOSE_APPLICATION should be the same value entered for TRAN_PURPOSE_EXT1 in record 0010 position 50 RCV_TRANSACTIONS_INTERFACE Table The following table lists the required fields for the RCV_TRANSACTIONS_INTERFACE table An asterisk by the column name indicates that it is not mapped referenced by Oracle e Commerce Gateway because the data is not required by the transaction message The lt field gt _ID fields are derived by the Receiving Open Interface API Application Transaction Detail 6 113 Required Fields for the RCV_TRANSACTIONS_INTERFACE Table Oracle Cond Oracle Hardcoded Record Position Applications e Commerce Derived Number Number Column Gateway Name for Column Required Name Fields ITEM_NUM ITEM_NUMB 2000 10 ER VENDOR_IT Yes VENDOR_IT 2000 20 EM_NUM EM_NUM ITEM_REVISI Yes ITEM_REVISI 2000 30 ON ON DOCUMENT PURCHASE_ 2000 50 _NUM ORDER_NU M DOCUMENT ORIGINAL_S 2000 70 _LINE_NUM YSTEM_LIN E_ REFERENCE QUANTITY SHIPPED_Q 2000 80 UANTITY UNIT_OF_M SHIPPED_U 2000 90 EASURE NIT_CODE_I NT ITEM_DESC PRODUCT_D 2000 140 RIPTION ESCRIPTION AUTO_TRA AUTO_TRA 2000 160 NSACT_CO NSACT_CO DE DE SHIP_TO_LO Yes SHIP_TO_IN 3000 10 CATION_ID T_LOCATIO N_ID 6 114 Oracle e Commerce Gateway Implementation Manual Oracle Cond Oracle Hardcoded Record Position Applications e Commerce Derived N
488. priate boxes to correspond to the number of column entries you made in this Assign Categories window This tells the program the maximum number of keys to use for that category In the Assign Categories window the Key 1 5 column names for the search keys are in a list of values These column names presented are all the column names in the current level table being reviewed plus all the levels tables above it For example if a data element at the item level is activated column names from both the header level and item level are in the list of values Once you selected the source column of the data the actual values that you would find in those columns for the given transaction are used as search key entries when the code conversion value table is read The source columns may be a customer name customer ID location code site name or whatever you choose You just scroll through the columns in the List of Values that have been defined for that transaction Enabling Code Conversion The code conversion table will be accessed only if the data element in the transaction is activated for code conversion This is done by assigning a code conversion category to the specific data element in a transaction using the Assign Categories window Source of Data for Search Keys Data to indicate a specific Trading Partner or Trading Partner site to be used as the search keys may be data found in several places in the transaction For example they ma
489. propriate document types must be enabled through the Define Trading Partner window Details tab The transaction must also be eligible to be extracted If these set ups are not done the Trading Partner s transactions cannot be extracted Check the following TP DEFINED Confirm that a Trading Partner is defined in Oracle e Commerce Gateway and associated to a valid address entity in Oracle Applications Trading Partner associations are set up using the Trading Partner window Assignment tab TP ENABLED Confirm that the Trading Partner is enabled for the outbound EDI Document and Document Type This is done using the Trading Partner window Details tab TP DEFINE If an entity is both a supplier and a customer make sure to identify two Trading Partners one for each business relationship EXPORT PARAMETERS Confirm that the selection parameters provided for the export process are valid for the documents to be extracted For the outbound Purchase Order 850 ORDERS or Purchase Order Changes 860 ORDCHG the date parameters are inclusive so make sure the end date parameter is one day later than the actual desired date The parameter must be one date later because time is included and you need to extract to the midnight hour FRESH TRANSACTIONS Make sure the selected group of documents have not been printed or previously extracted 8 12 Oracle e Commerce Gateway Implementation Manual Inbound Transactions Before an i
490. r business rules within the Application relating to e Commerce Specific implementation rules negotiated with the Trading Partners Capabilities of the Translator in creating and using the transaction interface file Method for file transfer between the Translator and Oracle e Commerce Gateway The planning process includes the following e Develop project plans Investigate and understand the business impact of each transaction Identify customization requirements Co ordinate the Translator interface Collate all setup data Write transaction or message specifications Produce Test Plans Develop transaction archiving policies Co ordinate testing with Trading Partners The scope of a project depends on the knowledge of the implementers number of 2 8 Oracle e Commerce Gateway Implementation Manual Trading partner sites to define number of Transactions implemented and the number of data maps needed in the Translator A simple project is one that involves one supported transaction few trading partners and minimal code conversion Setup includes the hardware setup and software installation of the pre built products It does not address the changes that may be needed for code conversion and customization which are part of the Modification phase Also Modification may either come before Testing since the need for changes are identified in the Definition phase or there may be another Testing phase after Modification A good minimum
491. r code conversion value table entries The values that you enter in the table are case sensitive Not all scenarios of code conversion table entries can be documented This information 10 18 Oracle e Commerce Gateway Implementation Manual illustrates how the code conversion value table is accessed Use it to develop your code conversion strategy The following tables provide some considerations to help you develop that strategy Planning for Direction OUT for Outbound Transactions The following table shows an example in which all entries are not feasible for the direction OUT Columns External Code 1 and External Code 2 are retrieved for the transaction interface file Example of Planning for Direction OUT for Outbound Transactions entry Categor Directio Key 1 Key 2 Internal Externa Externa Note y n Code Code Code 1 2 1 UOM OUT Each EA PC 2 UOM OUT Each PC EA Entire Search Key is duplicat e to 1 3 UOM OUT EDIFAC Each PC T 4 UOM OUT X12 Each EA Entry items 1 2 Internal code is part of the entire search key For direction OUT both these entries 1 and 2 are not feasible because the entire search key is not unique One entry can be made where you define the external 1 code to have X12 and external 2 code to have EDIFACT Your EDI translator data map will determine which field to use for the Trading Partner If needed alternative entries may be where external 1 and 2 may both have X12 codes and e
492. r delete the transaction Select the option in the View Staged Documents window Resolve Oracle e Commerce Gateway Exceptions To resolve Oracle e Commerce Gateway exceptions you can either correct the set up data in Oracle e Commerce Gateway or Oracle Applications or ask the Trading Partner to send a corrected transaction If the Trading Partner sends a corrected transaction be sure to delete the erroneous transaction from Oracle e Commerce Gateway s staging tables using the View Staged Documents window The duplicate transaction may cause confusion Relevant Oracle Purchasing Profiles and Setups The following is a list of the Purchasing setups related to the Receiving Open Interface 6 108 Oracle e Commerce Gateway Implementation Manual 1 RCV Fail All ASN Lines if One Line Fails e If the profile option is set to Yes and any line failed validation no further validation is performed for the ship notice e If the profile option is set to No and any line failed validation the process continues with the next line 2 ASN Control In the Receiving Options window in Purchasing select Warning Reject or None in the ASN Control field to determine how Purchasing handles the receipt against a purchase order shipment for which a ship notice exists Refer to the Oracle Purchasing User s Guide Defining Receiving Options sections for details 3 PO Enable SQL Trace for Receiving Processor If the profile option is set to Yes
493. r site and the EDI Location Code defined in Oracle Applications are displayed in the Define Trading Partners window Assignment tab If the data is not what you intend it to be you must make the appropriate changes for the transaction to be imported for the correct trading partner This could involve either altering the supplier supplier site in the base Oracle Application or assigning a different supplier supplier site to that EDI Location Code in Oracle e Commerce Gateway Refer to the Trading Partner chapter for recommendations on selecting the correct trading partner EDI Location Code for the control record 0010 for the transaction in the transaction interface file Oracle e Commerce Gateway Required Fields The following is a list of the Oracle e Commerce Gateway required fields These fields are required to authenticate the trading partner and transaction If the required data is not provided in the transaction the Oracle e Commerce Gateway import process fails the transaction Then an exception message is displayed in the View Staged Documents window If the trading partner is valid and the transaction is enabled the import process proceeds to validate the transaction using the user defined column rules If no process or column rule exceptions are detected the Oracle e Commerce Gateway import program will write the transaction to the Payables Open Interface tables to be processed by the Payables Open Interface API Oracle e Commerce Gate
494. racle Support web site for updates in these procedures Important The steps for extensible architecture mentioned here are valid for the following transactions which are not based on Generic Outbound Engine Outbound Purchase Order POO Outbound Purchase Order Change POCO Outbound Invoice INO Outbound Planning Schedule SPSO Outbound Shipping Schedule SSSO Outbound Application Advice ADVO Outbound Movement Statistics MVSTO The following transactions are based on Generic Outbound Engine Outbound Credit Memo Debit Memo CDMO Outbound Shipment Notice Manifest DSNO Outbound Purchase Order Acknowledgement POAO Outbound Purchase Order Change Acknowledgement POCAO Outbound OPM s Shipment Notice GASNO Outbound OPM s Purchase Order Acknowledgement GPOAO Outbound Payment PYO Note In Release 12 the Outbound Payment transaction PYO uses the Generic Outbound Engine and the extensible code is in the package EC_PYO_EXT The procedure names are pyo_ populate _ext_lev0l and pyo populate ext lev02 11 6 Oracle e Commerce Gateway Implementation Manual Define Columns in the Extension Table Task Add columns to the appropriate extension table When the Oracle e Commerce Gateway is installed all extension tables are created There is one extension table for each interface table and each extension table has only column TRANSACTION_RECORD_ID This column corresponds to the TRANSACTION_ RECORD_ID column
495. rading Partner It also enables a document transaction for processing and flags the transaction as test or production The Trading Partner Details tab requires the following e Aline for the each document document type e For inbound transactions there must be a Translator Code entry that exactly matches the Translator Code in Control Record 0010 of the transaction interface file e For outbound transactions the value of the Translator Code must exactly match the Translator Code expected in the EDI Translator e The Enable box must be checked to enable the transaction for this Trading Partner site 9 26 Oracle e Commerce Gateway Implementation Manual 10 Code Conversion This chapter contains the code conversion information about Oracle e Commerce Gateway implementation This chapter covers the following topics e Code Conversion e Concatenated Search Key for Inbound Transactions e Concatenated Search Key for Outbound Transactions Code Conversion The Oracle e Commerce Gateway code conversion function provides a method by which codes used by Trading Partners and electronic data standards can be converted from and to codes used in the Oracle applications For example assume that the ABC Corporation transmits a purchase order to the XYZ Corporation The XYZ Corporation processes the incoming data using its own internal codes i e unit of measure currency freight carriers etc but XYZ is required to return
496. ransacti transacti on key on key on key 1 UOM BOTH EA Each 2 UOM BOTH PC Each 1 UOM BOTH EDIFACT PC Each 1 UOM BOTH X12 EA Each 2 UOM BOTH X12 PC Each 10 16 Oracle e Commerce Gateway Implementation Manual note Category Direction Key 1 Key 2 External External Internal 1 2 Outbou Inbound Inbound nd transacti transacti transacti on key on key on key 1 SHIP_VI BOTH 1004 1110 TRUCK A Truck air A 1 SHIP_VI BOTH 1004 1110 TRUCK J Truck mo A tor 1 SHIP_VI BOTH 1004 TRUCK J Truck air A motor 1 SHIP_VI BOTH 2010 1005 ALPHA A Alpha air A 1 SHIP_VI BOTH 2010 1005 ALPHA J Alpha gr A ound 1 SHIP_VI BOTH BETA A Beta Ove A right 1 SHIP_VI BOTH BETA J Beta Gro A und Note There would not be a unique search key for outbound transaction if the table entry were allowed An alternate code conversion scheme must be chosen 1 Simple table entry exists 2 Items marked 2 will not be allowed as table entries since the full search key for outbound transactions will not be unique Document Standard as Part of the Search Key Document standard is a code to represent the common EDI standards such as X12 and EDIFACT Its purpose is to use the selected code as a search key in the code conversion value table The document standard may be set for a Trading Partner for a specific transaction in the Define Trading Partner Detail tab Follow the usual code conversion set up through the thre
497. ransfer FEW Federal Reserve Fund Wire Transfer Repetitive FWT Federal Reserve Fund Wire Transfer Non repetitive Application Transaction Detail 6 69 Payment Method Description SWT Society for World wide Inter bank Financial Telecommunications SWIFT e Payment Format Indicates type of data being transmitted and the format of the data Payment Format values and their descriptions are listed in the table below Payment Format Description CCD CCP CTP CTX PPD PPP Cash Concentration Disbursement ACH CCD Cash Concentration Disbursement plus Addenda ACH CCP Corporate Trade Payment ACH CTP Corporate Trade Exchange ACH CTX Prearranged Payment and Deposit ACH PPD Prearranged Payment and Deposit plus Addenda ACH PPP e Remittance Method Indicates which party is responsible for sending remittance advice to the payee The valid options are as follows 1 EDI to Payer s bank 2 EDI to Payee s bank 3 EDI to Payee 4 EDI to third party 5 Do not route 6 Remittance Instruction Additional text instructions 6 70 Oracle e Commerce Gateway Implementation Manual 7 Transaction Handling Indicates how payment and remittance advice should be processed The Transaction Handling codes and their descriptions are listed in the table below Handling Code Description C Payment accompanies remittance advice D Payment only I Remittance advice
498. ransfer FEW Federal Reserve Fund Wire Transfer Repetitive FWT Federal Reserve Fund Wire Transfer Non repetitive SWT Society for World wide Inter bank Financial Telecommunications SWIFT Application Transaction Detail 6 91 e Payment Format Indicates type of data being transmitted and the format of the data Payment Format values and their descriptions are listed in the table below Payment Format Description CCD Cash Concentration Disbursement ACH CCD CCP Cash Concentration Disbursement plus Addenda ACH CCP CTP Corporate Trade Payment ACH CTP CTX Corporate Trade Exchange ACH CTX PPD Prearranged Payment and Deposit ACH PPD PPP Prearranged Payment and Deposit plus Addenda ACH PPP e Remittance Method Indicates which party is responsible for sending remittance advice to the payee The valid options are as follows 1 EDI to Payer s bank 2 EDI to Payee s bank 3 EDI to Payee 4 EDI to third party 5 Do not route 6 Remittance Instruction Additional text instructions 7 Transaction Handling Indicates how payment and remittance advice should be processed The Transaction Handling codes and their descriptions are listed in the table below 6 92 Oracle e Commerce Gateway Implementation Manual Handling Code Description C Payment accompanies remittance advice D Payment only I Remittance advice only U Split payment and remittance advice Z Other types of handl
499. rd Shipm Line blank Number Layout Layout ent Qualifie r 5 Currenc TP_CD SHIPM 1030 L4 DL4 y Tax ENT Paymen t Terms 6 Allowa TP_CD SHIPM 1040 L5 DL5 nces Ch ENT arges Freight 7 Hazard TP_CD SHIPM 1050 HZ HZ1 ous ENT Material Special Handlin 8 8 Header TP_CD SHIPM 1090 N1 NH1 Note ENT 9 Vendor TP_CD SHIPM 1100 AD SF Address ENT Code 10 Destinat TP_CD SHIPM 1120 AX ST ion ENT Address Code 11 Destinat TP_CD SHIPM 1130 CN ST ion ENT Contact 12 Shipme TP_CD SHIPM 1200 A1 SH1 nt ENT Header Flexfiel ds 1 4 Transaction Summary Layouts A 83 Record TP_CD Ref1 Ref 2 Ref 3 Record Record Record Shipm Line blank Number Layout Layout ent Qualifie r 13 Shipme TP_CD SHIPM 1210 A2 SH2 nt ENT Header Flexfiel ds 5 9 14 Shipme TP_CD SHIPM 1220 A2 SH3 nt ENT Header Flexfiel ds 10 14 15 Shipme TP_CD SHIPM 1230 A2 SH4 nt ENT Header Flexfiel d15 16 Basic TP_CD SHIPM LINE 2000 L1 IT1 Item ENT Data 17 Hazard TP_CD SHIPM LINE 2010 L2 IT2 ous ENT Material Codes 18 Currence TP_CD SHIPM LINE 2020 L3 IT3 y Tax ENT Item Level 19 Notes TP_CD SHIPM LINE 2030 N1 ND1 ENT 20 Shipme TP_CD SHIPM LINE 2100 A1 SL1 nt Line ENT Flexfiel ds1 4 A 84 Oracle e Commerce Gateway Implementation Manual Record TP_CD Ref 1 Ref 2 Ref 3 Record Record Record Shipm Line blank Number Layout Layout ent Qualifie r 21 Shipme TP_CD SHIPM LINE 2110 A2 SL2 nt Line ENT Flexfiel ds 5 9 22 Shipme TP_CD SHI
500. rd Layout Qualifie r 63 64 65 66 67 68 69 70 71 Line Part Flexfiel d15 TP Header Flexfiel ds 1 5 TP Header Flexfiel ds 6 10 TP Header Flexfiel ds 11 15 TP Line Flexfiel ds 1 5 TP Line Flexfiel ds 6 10 TP Line Flexfiel ds 11 15 Industr y Flexfiel ds 1 5 Industr y Flexfiel ds 6 10 TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD MEMO MEMO MEMO MEMO MEMO MEMO MEMO MEMO MEMO LINE LINE LINE LINE LINE LINE LINE LINE LINE 5130 5140 5150 5160 5170 5180 5190 5200 5210 A2 A2 A2 A2 A2 A2 A2 A2 A2 LP4 HT1 HT2 HT3 LT1 LT2 LT3 IA1 IA2 A 182 Oracle e Commerce Gateway Implementation Manual Data Trading Partner Ref 1 MEMO Ref 2 ITEM Ref 3 TAX Record Record Layout Number Record Layout Qualifie r 72 73 74 75 76 77 78 79 80 Industr y Flexfiel ds 11 15 Extensio n Tables Item Data Line Tax Data Line Tax Type Line Tax Classific ation Line Tax Code VAT Tax Data Line Tax Flexfiel ds 1 4 Line Tax Flexfiel ds 5 9 TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD MEMO MEMO MEMO MEMO MEMO MEMO MEMO MEMO MEMO LINE LINE LINE LINE LINE LINE L
501. rd 5010 Record ITEM_DET ITEM_DET ITEM_DET ITEM_DET ITEM_DET ITEM_DET 5010 AIL_REF_ AIL_REF_ AI_REF_C AIL_REF_ AIL_REF__ AIL_REF_ CODE_1_ VALUE_1_ ODE_1_S VALUE 2 CODE_2_ VALUE_3_ SD SD D SD SD SD Pos 10 Pos 20 Pos 30 Pos 40 Pos 50 Pos 60 4000 5010 XX 29556 Note Record 4000 data precedes its related 5000 series records Example Record 5010 One use of the Record 5010 is to state the supplier s shipper number example 29556 when Record 4000 is used for a last shipment received record Review Oracle e Commerce Gateway Exceptions Use the Oracle e Commerce Gateway View Staged Documents window to review the Oracle e Commerce Gateway transaction exceptions Once the exceptions are identified and resolved you can submit the transaction for reprocessing ignore the exception during reprocessing or delete the transaction Select the option in the View Staged Documents window Resolve Oracle e Commerce Gateway Exceptions To resolve Oracle e Commerce Gateway exceptions you can either correct the set up data in Oracle e Commerce Gateway or Oracle Applications or ask the Trading Partner to send a corrected transaction If the Trading Partner sends a corrected transaction you must delete the erroneous transaction from Oracle e Commerce Gateway s staging tables using the View Staged Documents window Relevant Oracle Release Management Profiles and Setup The following is a list of the Release Management setups related to the Release
502. rd Layout The following table shows the record layout of the record layout code CM Contact Record Format These records can store phone numbers when contact personnel data is not available Area Codes are not stored separately in the application Transaction Interface File Architecture 5 29 Contact Format 2 CM Record Layout Seq Business Entity Contact Data 1 Common Key including Record Number 2 Business Entity Primary Telephone 1 3 Business Entity Primary Telephone 2 4 Business Entity Primary Telephone 3 Length 100 60 PER04 60 PER04 60 PER04 Code Conversion Internal and External Codes on the File The transaction interface file may have one to five external fields activated for the file for a given internal code that is marked as a candidate for code conversion Usually only the external 1 fields is activated by the seeded transaction You may activate other external fields using the Interface File Definition window Reference the Modify Transaction Interface File page 4 23 the Code Conversion chapter and the Oracle e Commerce Gateway User s Guide 5 30 Oracle e Commerce Gateway Implementation Manual 6 Application Transaction Detail This chapter contains information about application transaction detail This chapter covers the following topics Oracle Inventory Oracle Order Management Inbound Purchase Order POI 850 ORDERS Comment Text Review Order Management Open Interface Exceptions
503. rd for two reasons e To identify that the Trading Partner site is setup and enabled for the specific transaction For example EDI Location Code HC CHIC is defined to Trading Partner Herbert Chicago where the specific outbound transaction is enabled for EDI processing e To derive the customer supplier or bank in the Oracle Application to associate with all the address sites in the transaction detail For example the customer Herbert Corporation is derived from the base Oracle Application tables given that the EDI Location Code HC CHIC for the Chicago site was found on the Control Record Either a constant EDI Location Code for the Trading Partner may be entered in the Control Record see Default EDI Location section below or the first appropriate site found in the detail of the transaction may be copied to the Control Record by the EDI Translator The recommended type of location code to copy from the transaction detail into the Control Record 0010 is listed in the following table These types of location are likely to be in the transaction detail however any EDI Location Code for the Trading Partner will work as long as it is fully defined in the Oracle e Commerce Gateway The following table shows examples of Type of Site Location Codes on the Control Record for Inbound Transactions Examples of Type of Site Location Code on the Control Record 0010 for Inbound Transactions Transaction Transaction ASC X12 EDIFACT Type o
504. re defined Execute the necessary application process to ensure that documents are eligible for extraction Run available application Reports to identify documents that are eligible for extraction This can be used to compare the transaction interface file created by Oracle e Commerce Gateway Testing the Outbound Transaction Perform the following for outbound transactions Initiate the outbound transaction and enable run time execution log debug parameter to HIGH or MEDIUM to monitor the import process Specify valid values for the program parameters refer to Oracle e Commerce Gateway User s Guide for the parameter list When the extract process completes review the Concurrent Request Log and Report for detected exceptions Make the necessary corrections in Oracle e Commerce Gateway or Oracle Applications and re initiate the outbound transaction Test Transactions 7 5 e Continue to initiate the extract process review exceptions resolve exceptions and re initiate the outbound transaction until the transaction completes successfully and a transaction interface file is created e Run the Interface File Data Report to review the contents of the transaction interface file Verify the following e Report output matches the data entered in Oracle Applications and is consistent with your selection criteria e Code conversion enabled columns are converted according to your conversion rules e Report output matches application re
505. re used for column rules see below regarding Rule Actions Oracle e Commerce Gateway s exception handler supports seven column rules as follows e Datatype Checking Examples of data types are alphanumeric numeric and date This rule compares the data type defined in the ece_interface_columns table with the data type of the data in the incoming interface file If the data types do not match then this rule is violated e Default If Null This rule is used to put a value into the column if it is null blank in the incoming interface file This is the only rule that modifies the incoming data as a value is placed in the Application Open Interface table The interface file is not updated Use the Log Only rule action for this column rule e Null Dependency This rule is used to create complex comparisons for a column within the document Null Dependency allows the user to set up conditional expressions that indicate whether the assigned column must be null or cannot be null depending on the values in other columns e Predefined List This rule is used to validate the incoming data for a given column against a user defined list For example transaction_method Must Equal EDI implies the value EDI is on the user defined list If Cannot Equal is checked then transaction_method cannot equal EDI e Simple Lookup This rule requires you to identify the specific table and column containing a list of valid values The table and c
506. rectory names DIRECTORY Make sure the utl_file_dir parameter for the outbound file directory is defined in the INIT ORA file to match the profile option setting Make sure to restart the database after making any changes ACCESS Make sure the defined directory is accessible and not write protected If directory is protected use chmod 777 in UNIX to grant access 8 10 Oracle e Commerce Gateway Implementation Manual Symptom Solution The outbound Purchase Order 850 ORDERS Check the setting of the appropriate or Purchase Order Changes 860 ORDCHG Document Type under Setup Purchasing file is empty Options for when archival is performed The options are Archive on Print or Archive on Approval For Oracle Purchasing transactions to be extracted properly the option must be set to Archive on Approval The Archive on Print causes the purchase order to be printed that in turn prohibits Oracle e Commerce Gateway from extracting it Not every purchase order change causes a purchase order revision that triggers a purchase order reprint or purchase order retransmit Check the Oracle Purchasing User Guide for business rules to determine what type of changes create a purchase order revision Troubleshooting 8 11 Symptom Solution The outbound file is empty The Trading Partner TP primary site for the transaction must be set up through the Trading Partner Assignment tab and the transaction and ap
507. rent legal entity to that EDI Location Code in Oracle e Commerce Gateway Please note that if the trading partner is associated with multiple operating units then the transaction to be extracted is for a specified operating unit only linked to your responsibility To extract all the data for multiple operating units you still need to execute the program one by one by specifying different operating unit each time when you run the program See the Outbound Transactions chapter in the Oracle e Commerce Gateway User s Guide for details Refer to the Trading Partner chapter for recommendations on selecting the correct trading partner EDI Location Code for the control record 0010 for the transaction in the transaction interface file The outbound Movement Statistics transaction is controlled by four database views that are defined according to the Oracle Inventory data model for inventory movement statistics The four views contain variables which are dynamically set based on your responses to the extract program parameters refer to Oracle e Commerce Gateway User s Guide Outbound Transactions chapter for a list of the program parameters The four database views are as follows e ECE_MTL_MOV_STAT_V e ECE_MVSTO_DETAILS_V e ECE_MVSTO_HEADERS_V e ECE_MVSTO_LOCATIONS_V The ECE_MVSTO_DETAILS_V view is used to identify which movement statistics are eligible for extraction The extract criteria are as follows e Trading partner is defined e
508. ress is placed in the external address Location code Usually the address column ID from the base Oracle Application is placed in the Location internal address EDI Location Code field The full site address is also placed on the address record The EDI Location Codes found in the address records in the transaction detail do not need to be defined as a Trading Partner in the Oracle e Commerce Gateway unless that EDI Location Code may also appear on the Control Record for any transaction See Control Record page 9 14 Any address site in the transaction detail such as the customer customer site or supplier supplier site must still be defined in the base Oracle Application and the EDI Location Code for the site must be entered If the EDI Location Code is not entered in the base Oracle Application it will not be written to the transaction interface file and not be available for data mapping in the Translator by the Oracle e Commerce Gateway Default EDI Location Code Inbound Transactions Only The EDI Translator may provide an EDI Location Code in the Control Record 0010 to identify a particular Trading Partner address site even if that same EDI Location Code is not found in the transaction detail address records This particular Trading Partner address site will be used to determine the Customer Supplier or Bank to be associated with all the address sites in the detail of that transaction plus check that the transaction is enabled for that Tr
509. revalidated and search for Trading Partner locations defined to the new organization Transactions for yet another organization will continue to reject Continue changing the responsibility and resubmitting transactions until all locations are found If any transactions cannot be processed their Trading Partners must be set up in the base application for that organization under the correct responsibility Note The EDI Location Code will encounter a Trading Partner implying a Trading Partner with the current responsibly not found condition even though the Trading Partner is defined to another organization This may cause confusion because the Trading Partner definition is seen in the Oracle e Commerce 9 20 Oracle e Commerce Gateway Implementation Manual Gateway and the customer suppler bank tables The organizational relationship to the current responsibility is not indicated Separating Transactions in a File by Organization Given the processing rules of the Oracle e Commerce Gateway described above inbound transactions separated into separate transaction interface files per organization may facilitate your processing Transactions may be separated by the following methods e Different electronic mailboxes e Different electronic envelope and or functional group e Trading Partner has multiple Location Codes set up in the source application e Trading Partner can provide the organization code in the transaction EDI Translators
510. rganiz ation Option Flexfiel ds 10 14 Organiz ation Option Flexfiel d15 Schedul e Item Flexfiel ds 1 4 Schedul e Item Flexfiel ds 5 9 Schedul e Item Flexfiel ds 10 14 Schedul e Item Flexfiel d15 TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD SS SS SS SS SS SS SS ITEM ITEM ITEM ITEM ITEM ITEM ITEM 2260 2270 2280 2300 2310 2320 2330 A2 A2 A2 Al A2 A2 A2 SO2 SO3 SO4 SI1 SI2 SIS SI4 Transaction Summary Layouts A 255 Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner SS ITEM SCHE Number Layout Layout DULE Qualifie r 62 Extensio TP_CD SS ITEM 2900 Custo Custo n m m Tables Item Level 63 Forecast TP_CD SS ITEM SCHED 4000 SC SCH Dates ULE Authori zation Receipt Data 64 Extensio TP_CD SS ITEM SCHED 4900 Custo Custo n ULE m m Tables Forecast Level A 256 Oracle e Commerce Gateway Implementation Manual
511. ription of the level These values are seeded in the FND_LOOKUP_VALUES table Name of the column storing the transaction data in the View Staging tables 8 16 Oracle e Commerce Gateway Implementation Manual Column Value Value stored in the Column Name This data came directly from the transaction or was derived in the Oracle e Commerce Gateway Violation Number of column violations for the selected column Message Column exception text for the selected column Ignore Check Box When this box is checked the violation that was determined by the Column Rule will be ignored when resubmitting the document This is the only field that can be modified in this window Reports The Oracle e Commerce Gateway provides two reports that allow the user to verify the transaction layout and contents of their data files Transaction Layout Report This report allows the user to produce an on line report or a hard copy listing of the transaction interface file layouts for the any transaction within the Oracle e Commerce Gateway Each transaction interface file consists of several records Each record has two sections the record key positions 1 100 and the application data area positions 101 amp beyond Every record is referenced by a record number that is unique to a set of data elements This report displays all the data elements in positions 101 and beyond The record key 1 100 is not reported as these seeded values may not be c
512. rising the Inbound Price Sales Catalog transaction The table shows the functional data grouping of records the data level the record numbers and relevant notes about the data grouping Transaction Summary Layouts A 103 CATI Transaction Record Summary Type of Data Data Level Record Number Note 1 Control Record HEADER 0010 2 Transaction HEADER 1000 Identification 3 Currency HEADER 1010 Payment Terms 4 FOB Carrier HEADER 1020 Freight Terms 5 Action Type HEADER 1030 Group Code 6 Comments HEADER 1040 7 Ship to Address HEADER 1100 8 Bill to Address HEADER 1110 9 Ship From HEADER 1120 Address 10 Header HEADER 1200 1230 Flexfields Flexfields 11 Item LINE 2000 Identification 12 Quantity LINE 2010 Description 13 Prices Dates LINE 2020 14 Payment Terms LINE 2030 Item Level A 104 Oracle e Commerce Gateway Implementation Manual Type of Data Data Level Record Number Note 15 FOB Carrier LINE 2040 Freight Terms Item Level 16 Hazardous data LINE 2050 Weight Volume Lead Time 17 Ship To Data LINE 2100 Item Level 18 Line Level LINE 2200 2230 Flexfields Flexfields 19 Shipment LINE 2240 2270 Flexfields Flexfields 20 Item Level LINE 2280 2310 Flexfields Flexfields 21 Item Level LINE 2280 2310 Flexfields Flexfields 22 Item Level LINE 2280 2310 Flexfields Flexfields Inbound Price Sales Catalog Common Key The following table shows the Common Key positions 1 100 for the
513. rmation 5 Customer HEADER 1090 Payment Terms List Price 6 FOB Point HEADER 1100 Freight Terms 7 Shipment HEADER 1110 Priority Freight Carrier 8 Shipping amp HEADER 1120 Packing Instructions Transaction Summary Layouts A 59 Seq Data Data Level Record Number Note 9 Request Dates HEADER 1130 Schedule Limits 10 Header HEADER 1200 1230 Flexfields Flexfields 11 PO Flexfields HEADER 1240 1270 Flexfields 12 Global Flexfields HEADER 1280 1320 Flexfields 13 Customer Name HEADER 1400 amp Number 14 Sold_to HEADER 1410 Organization 15 Sold_to Contact HEADER 1420 Information 16 Ship_to Address HEADER 1500 Information 17 Ship_to Contact HEADER 1510 Information 18 Invoice Address HEADER 1520 Information 19 Invoice Contact HEADER 1530 Information 20 Ordered By HEADER 1540 Name 21 Original System LINE 2000 References 22 Item Type Codes LINE 2010 23 Item Segments LINE 2020 1 10 A 60 Oracle e Commerce Gateway Implementation Manual Seq Data Data Level Record Number Note 24 Item Segments LINE 2030 11 20 25 Demand Class LINE 2040 Bucket Type 26 Customer LINE 2050 Payment Terms Tax Exempt Information 27 Project Task LINE 2060 Contract Numbers 28 FOB Point LINE 2070 Freight Terms 29 Shipment LINE 2080 Priority Method Freight Carrier 30 Sales LINE 2090 representative Reference Ids 31 Order Ship LINE 3000 Quantity UOM 32 Item Flexfields LINE 3100 3130 Flexfields 33 Global
514. rocess RLM_INTERFACE_HEADER Table The following table lists the required fields for the RLM_INTERFACE_HEADER table 6 150 Oracle e Commerce Gateway Implementation Manual Required Fields for RLM_INTERFACE_HEADER Table Oracle Cond Oracle Hard coded Applications e Commerce Derived Column Gateway Name for Column Required Name Fields Record Number Position Number EDI_CONTR OL_NUM_3 RLM_SCHED ULE_TYPE_I NT SCHEDULE_ PURPOSE_I NT SCHEDULE_ SOURCE CREATED_B Derived Y CREATION_ Derived DATE HEADER_ID HEADER_ID Derived LAST_UPDA Derived TE_DATE LAST_UPDA Derived TED_BY PROCESS_ST Derived ATUS REQUEST_ID Derived 0010 1000 1000 1000 180 010 070 280 EDI_CONTROL_NUM_3 EDI control number 3 is the third level control number from the transaction such as the X12 ST It is assigned by the customer s EDI translator for auditing Application Transaction Detail 6 151 HEADER_ID This column represents a sequence generated unique identifier It is system generated when the interface table is loaded RLM_SCHEDULE_TYPE_INT This column represents the Schedule type Valid Values PLANNING SHIPPING SEQUENCED SCHEDULE_PURPOSE_INT This column represents the Schedule Purpose code Valid Values ADD ORIGINAL REPLACE CANCELLATION CHANGE DELETE and CONFIRMATION SCHEDULE_SOURCE This column represents the EDI or manual transaction source for this schedu
515. rolled by five database views which are defined according to the Oracle Receivable data model for credit and debit memos The five views contain variables which are dynamically set based on your responses to the extract program parameters refer to Oracle e Commerce Gateway User s Guide Outbound Transactions chapter for a list of the program parameters The five database views are as follows ECE_CDMO_ALLOWANCE_CHARGES_V e ECE_CDMO_ HEADERS 1 _V e ECE_CDMO HEADER_V e ECE_CDMO _LINE_TAX_V e ECE_CDMO_LINE_V The ECE_CDMO_HEADERS_V view is used to identify which credit debit memos are eligible for extraction The extract criteria are as follows e Trading partner is defined e Credit memo or debit memo enabled for the trading partner e Transaction type is credit memo or debit memo e Credit memo or debit memo has not been printed or previously extracted e Credit memo or debit memo status is COMPLETE e Credit memo or debit memo print option is PRI e Print pending is Y If necessary you can use SQLPLUS to verify if there are any eligible documents to be extracted To do so you must first set the organization context and then issue the SQL count function as follows 6 132 Oracle e Commerce Gateway Implementation Manual SQLPLUS gt execute fnd_client_info set_org context lt Org number gt SQLPLUS gt select count ECE CDMO HEADERS V Review all your set ups if the count value is 0 as this
516. rough agreements sourcing rules and approved supplier lists In addition this guide explains how you can automatically create purchasing documents based on business rules through integration with Oracle Workflow technology which automates many of the key procurement processes Oracle Payables User s Guide This guide describes how to use Oracle Payables to create invoices and make payments In addition it describes how to enter and manage suppliers import invoices using the Payables open interface manage purchase order and receipt matching apply holds to invoices and validate invoices It contains information on managing expense reporting procurement cards and credit cards This guide also explains the accounting for Payables transactions Oracle Receivables User Guide This guide provides you with information on how to use Oracle Receivables Use this guide to learn how to create and maintain transactions and bills receivable enter and apply receipts enter customer information and manage revenue This guide also includes information about accounting in Receivables Use the Standard Navigation Paths appendix to find out how to access each Receivables window Oracle Order Management User s Guide This guide describes how to enter sales orders and returns copy existing sales orders schedule orders release orders create price lists and discounts for orders run processes and create reports Oracle Shipping Execution User s Gu
517. rrier Code Transaction Data GAMMA 9999 Over Night Transaction Column CUSTOMER NAME CUSTOMER SITE CARRIER_INT Listed below are the full search key parameters given the data found in the transaction or data derived by the Oracle e Commerce Gateway Use this data to find a code conversion value table entry to retrieve the internal code Code Category Direction Key 1 Customer Key 2 Customer Site Key 3 Key 4 SHIP_VIA This code category was assigned to a data element in the transaction via the Assign Category window OUT and BOTH Determined by the inbound transaction to be processed GAMMA Sourece column for this key 1 is CUSTOMER_NAME The value GAMMA was derived by the Oracle e Commerce Gateway given the Trading Partner for the transaction 999 Source Column for this key 2 is CUSTOMER _ SITE The value 9999 was derived by the Oracle e Commerce Gateway given the Trading Partner site for this transaction not used not used 10 36 Oracle e Commerce Gateway Implementation Manual Key 5 Internal Code not used Over Night Over Night was the value in CARRIER_INT from the base Oracle Application The table below shows the three sets of full search keys to access the code conversion value table for the three attempts to read the table The number of attempts is always one more than the number of Key boxes that you enabled in the Code Conversion Categories window The source col
518. rs if needed Full Name and Addresses and Codes for each business entity where State and county codes are explicit This is usually data from RA tables Full Name and Addresses and Codes for each business entity where REGION 1 REGION2 REGION3 contain the state and county This is usually data from HR tables Primary Personnel Contact title and phones Primary Contact phone numbers Record Layout Code A1 The following table shows the record layout for the record layout code A1 Descriptive Flexfields Transaction Interface File Architecture 5 21 Record Layout Code A1 Seq Control Level Flexfields Length 1 Common key including 100 Record Number 2 Any Flexfield Context 30 3 Any Flexfield 1 80 4 Any Flexfield 2 80 5 Any Flexfield 3 80 6 Any Flexfield 4 80 Descriptive Flexfields A2 Record Layout The following table shows the record layout for the record layout code A2 Descriptive Flexfields Record Layout Code A2 Seq Control Level Flexfields Length 1 Common key including 100 Record Number 2 Any Flexfield 1 80 3 Any Flexfield 2 80 4 Any Flexfield 3 80 5 Any Flexfield 4 80 6 Any Flexfield 5 80 Descriptive Flexfields A3 Record Layout The following table shows the record layout for the record layout code A3 Descriptive Flexfields 5 22 Oracle e Commerce Gateway Implementation Manual Record Layout Code A3 Seq Control Level Flexfields Length 1 Common ke
519. rt Item Cross Referencing 00 0 cccec cei eee ee retiree ener nieeseeteeeneeteneteeeee 6 48 Data in the e Commerce Gateway Transaction 0 cece cece eerste eens teen eeneeeaee 6 51 Hable Searchessiintiaindia nied titan agig adi eee te a a asia 6 53 Miscellaricous Item Dataciis cciei stevie iis stice sekdeeaebi tea cadedan canted a a a aeta 6 61 Inbound Purchase Order Change POCI 860 ORDCHG cccccccseceecseetecseeteenteeneeneens 6 62 Outbound Purchase Order Acknowledgment POAO 855 ORDRSP POCAO 865 ORDRSP A E E ub iatieladaidesioahlidgatt nati big E mete ned haaths 6 63 Oracle Payables nenova i r Lh ae E gale diteget abigail tetas Medal bation ieee 6 64 Inbound Invoice INI 810 INVOIC 0c eee te eee e nee eter teeter eras setae sete seen tener eaee 6 72 Inbound Shipment and Billing Notice SBNI 857 No EDIFACT 0 c eee eee 6 87 Outbound Application Advice ADVO 824 APERAK c cece ete eerie eee tee teers te 6 87 Outbound Payment Order Remittance Advice PYO 820 PAYORD PAYEXT REMADV a AE AEE stv E E E cachteasltnatae Atlas E aE a tanta a dea dled ea a ated a Beda i a 6 89 Oracle Process Manufacturing ss esississirsiieristisstnsrisrintinrtnsrnnrintrnstnsrnntuntruntnnrnntnnnrnnen en 6 94 Oracle Purchasing miiie at ane e aiara e Ea aa A E aE TE EARRA A 6 95 Inbound Price Sales Catalog CATI 832 PRICAT Inbound Response to Request for Quotation RRQI 843 QUOTES ris isa a i a i aeeie 6 97 Inbo
520. rule or the rule is assigned incorrectly the expected pre validation may not be performed The following are errors related to defining validation rules e Deleted or changed a required process rule e Deleted a column rule for a required field e Changed a column rule for a date or numeric field e Assigned a column rule that does not match the type of data expected for the data element e Did not activate a rule defined with a Disabled rule action e Did not provide a list of valid values for Predefined List column rule Implementation Details 4 19 e Did not provide a valid Oracle Applications valueset for Valueset Lookup column rule e Did not provide a valid table column or condition for Simple Lookup column rule Refer to Troubleshooting chapter for details Enable Additional Transaction Data The information presented in this section is of an advisory nature and assumes you have attended an Oracle e Commerce Gateway training course and are familiar with standard Oracle features such as Flexfields Oracle e Commerce Gateway provides several methods to add data elements to the transactions that are not defined in the base Oracle Applications data model You may wish to add data elements to obtain data that is missing from the inbound file or that is required by multiple organizations The following table lists these methods and whether they apply to inbound or outbound transactions Methods of Adding Data Elements to
521. ry item Application Transaction Detail 6 55 INVENTORY_ITEM Interpretation of CUSTOMER_ITEM_ NAME Null any UPC code Null any EAN number any Inventory Item Null Sample CUSTOMER_ITEM_ I D_TYPE UPC EAN Null Result of Item Cross Referencing in Oracle Inventory Inventory Item Cross Reference table is accessed with the generic item to validate the generic item and derive its corresponding internal inventory item Inventory Item Cross Reference table is accessed with the generic item to validate the generic item and derive its corresponding internal inventory item Inventory Item table is accessed to validate the item in the transaction If the inventory item is invalid an error message is created 6 56 Oracle e Commerce Gateway Implementation Manual INVENTORY_ITEM any Inventory Item Interpretation of CUSTOMER_ITEM_ NAME any Customer Specific item Sample CUSTOMER_ITEM_ I D_TYPE CUST Result of Item Cross Referencing in Oracle Inventory Customer Item Cross Reference table is accessed to validate the customer item and derive its corresponding internal inventory item The derived Inventory Item is compared to the Inventory Item in the transaction If the derived and the sent Inventory Item do not match an error message is generated where the sent inventory item is displayed in the error Application Transaction Detail 6 57 INVENTOR
522. ry Key 26 47 22 3 Key 2 48 69 22 4 Key 3 70 91 22 5 Record Number 92 95 4 6 Record Layout Code 96 97 2 7 Record Layout 98 100 3 Qualifier Translator Code 1 25 This code is the Trading Partner identifier as defined in the Translator The code identifies the communications method electronic mailbox standard and data maps for the specific transaction This code is the link between the Oracle e Commerce Gateway and the Translator This code is defined as the Translator code in Define Trading Partner window Details tab Keys 1 3 26 91 Keys 1 3 represent key data from the first three levels of the given transaction This data is for audit or research purposes to facilitate reading the file directly The data may be truncated Key 1 is the Primary Key from the transaction It may be the purchase order number invoice number or shipment number for corresponding transactions Full primary document key is written in positions 117 151 of the control record 0010 Keys 2 3 represents other data at the second and third level within the transaction A transaction may have more than three levels of data which are not stored in the key area Record Number 92 95 The record number is a unique number within a transaction to identify specific data in a transaction Translators should rely on the record number to uniquely identify a record in the data file A sample of a simple numbering scheme and a larger range numbering scheme
523. ry Layouts A 15 Data Data Level Record Number Note Service Flexfields LINE DETAIL 4600 463 Flexfields Return Flexfields LINE DETAIL 4700 473 Flexfields Ship to Address Line LINE DETAIL 4800 Level Ship to Contact Line LINE DETAIL 4810 Level Deliver to Contacts LINE DETAIL 4820 Trader Partner LINE DETAIL 4830 4860 Flexfields Flexfields Ship from Address LINE DETAIL 4870 Line Level Credits Data CREDIT 5000 Credit Flexfields CREDIT 5100 5130 Flexfields Price Adjustments PRICE 6000 Data ADJUSTMENT Discount List Names PRICE 6010 for price ADJUSTMENT adjustments Price Adjustment PRICE 6100 6130 Flexfields Flexfields ADJUSTMENT Reservations Data RESERVATION 7000 Reservations RESERVATION 7100 7130 Flexfields Flexfields Action Data ACTION 8000 Action Flexfields ACTION 8100 8130 Flexfields A 16 Oracle e Commerce Gateway Implementation Manual Data Data Level Record Number Note Lot Serial Data LOT SERIAL 9000 Serial Lot Flexfields LOT SERIAL 9100 9130 Flexfields The following table shows the Common Key positions 1 100 for the Outbound Purchase Order transaction The table shows the position length code and content of the Common Key elements Transaction specific data in the Common Key positions 1 100 Position Length Code Content 1 25 25 TP_CD Trading Partner Code as defined in the EDI Translator 26 47 22 PO Purchase order number 48 69 22 ITEM Purchase order line numb
524. s if there is a one to one correspondence between the Oracle internal code and its set of external 1 5 codes For an outbound transaction the asterisked table entries in the table below cannot be entered into the tables This is because the single internal code Each would access multiple table entries for the external codes one with the external code EA and the other with the external code PC To be a successful table search only one table entry can be found An error message is displayed when the entry is attempted Even creating table entries using the document standard in key 1 may still cause a conflict within a standard For example this may happen when EA and PC are values both within X12 and within EDIFACT If separating the codes by standards still causes this problem you can select document standard Other for the exceptions and assign Other to those Trading Partners to retrieve the proper code for their transactions In the table below the columns Category Direction Key 1 and Key 2 are part of the search key for both inbound and outbound transactions The columns External 1 and External 2 are part of the key for inbound transactions to find the Internal code The column Internal is part of the key for outbound transactions to find the external codes 1 2 Example Inbound and Outbound Transactions Code Conversion note Category Direction Key 1 Key 2 External External Internal 1 2 Outbou Inbound Inbound nd transacti t
525. s Open Interface Exceptions At the completion of the Payables Open Interface Import program the Payables Open Interface Report is automatically initiated to report the status of all supplier invoices processed The report contains two sections as follows e Payables Open Interface Audit Report e Payables Open Interface Rejections Report The Audit section lists the invoices that were successfully imported while the Rejections section lists invoices that were not successfully imported and the reason for the rejection Refer to the Payables Open Interface Import section Oracle Payables User s Guide for a detailed list of the rejection codes and their meaning Return Application Advice to Supplier To return invoice acknowledgments to the supplier execute the Payables Open Interface Outbound Advice program to populate the Oracle e Commerce Gateway Application Advice tables ECE_ADVO_HEADERS and ECE_ADVO_DETAILS with the status of all supplier invoices processed Once the Application Advice tables are populated you can initiate the outbound Application Advice ADVO 824 APERAK transaction to acknowledge all invoices processed or just those containing exceptions There are three ways to resolve Payables Open Interface exceptions as follows e Correct set up data in Oracle Applications e Correct erroneous entries in the Payables Open Interface table using Open Interface Invoices window e Request supplier to send a corrected transaction
526. s by performing the search using the maximum number of user defined criteria then reducing the number of criteria by one until a match is found If a match is not found a default is used The final transaction configuration is related to the transaction layout Oracle e Commerce Gateway delivers seeded transaction layout definitions representing relevant business data from or to Oracle Applications The transaction layout definitions may be used as is or customized to match the data you transmit to your trading partner The transaction layout configuration options include change file structure change record layout change record attributes and delete records In addition to the system and transaction level configurations you may configure the trading partner attributes The trading partner is the entity you are doing business with and is the key link between Oracle e Commerce Gateway and Oracle s suite of e business products and Introduction 1 5 between Oracle e Commerce Gateway or any third party application The third party application may be an EDI translator for EDI transactions or any other application internal or external to your enterprise In addition to establishing these links you can configure the trading partner attributes to indicate that a transaction is enabled or disabled for processing and indicate the transaction status to be test or production for processing Trading Partners and Multiple Organizations To support m
527. s date is equal to the CREATION_DATE for this transaction This date is set to the system date LAST_UPDATED_BY This code is equal to the CREATED_BY code for this transaction Review Release Management Demand Processor Exceptions The Oracle Release Management Demand Processor Exception Handling lets the supplier accomplish the following tasks e Receive error messages on problems that have halted demand processing e Receive warning messages on potential demand processing problems e Receive information messages on noteworthy situations detected by the Demand Processor e Generate exceptions report automatically after demand processing completion e Review real time report on inbound demand processing exceptions e View exceptions generated for any schedule via the Release Management Workbench until purged e Correct set up data to allow successful demand processing e Correct schedule data to allow successful demand processing Validate customer demand for data that impacts demand processing You can review all exceptions detected by the Release Management Demand Processor in the Release Management Demand Workbench or on the Demand Management Exception Report Refer to the Oracle Release Management User s Guide for more information on the Demand Management Exception Report Resolve Release Management Demand Processor Exceptions To resolve Release Management Demand Processor exceptions you can either correct the set up data in Oracle
528. s eee renee teste e tee tneeeeeeetaes A 168 Oracle Release Management Transaction Summaries 00 ce cee cece etter A 201 Oracle Shipping Execution Transaction Summaries 0 00ccccceeee eee cess cesee tse eeeeeaes A 229 Oracle Supplier Scheduling Transaction Summaries vii Send Us Your Comments Oracle e Commerce Gateway Implementation Manual Release 12 Part No B31058 01 Oracle welcomes customers comments and suggestions on the quality and usefulness of this document Your feedback is important and helps us to best meet your needs as a user of our products For example e Are the implementation steps correct and complete e Did you understand the context of the procedures e Did you find any errors in the information e Does the structure of the information help you with your tasks e Do you need different information or graphics If so where and in what format e Are the examples correct Do you need more examples If you find any errors or have any other suggestions for improvement then please tell us your name the name of the company who has licensed our products the title and part number of the documentation and the chapter section and page number if available Note Before sending us your comments you might like to check that you have the latest version of the document and if any concerns are already addressed To do this access the new Applications Release Online Documentation CD availabl
529. s for you to review detected exceptions Exceptions generally result from incorrect set ups in Oracle e Commerce Gateway or Oracle Applications that may be corrected in the respective applications Another form Test Transactions 7 1 of exception is due to incorrect data sent by the Trading Partner The Trading Partner may be asked to correct the transaction and transmit an updated transaction Since these business transactions represent legal documents general data changes cannot be made on the transaction in the Oracle e Commerce Gateway However if the transaction passes all Oracle e Commerce Gateway validation and is passed to the Application Open Interface tables some Oracle application modules provide tools for data correction The focus of this chapter is on testing inbound transactions Crucial to the successful implementation of an inbound transaction are all the setups necessary in Oracle e Commerce Gateway and Oracle Applications So before you initiate the import process you must verify all your set ups This chapter assumes that the inbound transaction interface file resides in the directory specified in the Oracle e Commerce Gateway system profile ECE Inbound File Path and is available for the Oracle e Commerce Gateway import program to pick up and process Refer to Application Transaction Detail for details related to the following for the inbound transaction you are implementing e Transaction specific special considerati
530. s is set up properly verify that the Customer Customer site and the EDI Location Code in Oracle Applications is the correct Customer Customer site selected for the Trading Partner definition in Oracle e Commerce Gateway The selected Customer Customer site and the EDI Location Code defined in Oracle Applications are displayed in the Define Trading Partners window Assignment tab If the data is not correct you must make the appropriate changes for the transaction to be imported for the correct trading partner This could involve either altering the Customer Customer 6 6 Oracle e Commerce Gateway Implementation Manual site in the base Oracle Application or assigning a different Customer Customer site to that EDI Location Code in Oracle e Commerce Gateway Refer to Trading Partner chapter for recommendations on selecting the correct trading partner EDI Location Code for the control record 0010 for the transaction in the transaction interface file Oracle e Commerce Gateway Required Fields The following is a list of the Oracle e Commerce Gateway required fields These fields are required to authenticate the trading partner and transaction If the required data is not provided in the transaction the Oracle e Commerce Gateway import process fails the transaction Then an exception message is displayed in the View Staged Documents window If the trading partner is valid and the transaction is enabled the import process proceeds to validate the
531. s needed Automatic Transaction Status Feedback to the Application Feedback is provided to Oracle Applications that transactions have confirmed receipts from trading partners or some other transmission status e g buyers may wish to see a confirmation that a supplier received or not a specific order Audit Transaction Archival Maintains historical archival of data for audit purposes Introduction 1 15 2 Implementation Positioning This chapter contains information about Oracle e Commerce Gateway implementation This chapter covers the following topics e Implementation Positioning e Other Application Implementations e Determine Communications Methods For The Transactions e Implementation Planning Implementation Positioning To successfully implement the Oracle e Commerce Gateway and enable specific transactions within the product the implementer needs to have certain knowledge and experience beyond the Oracle e Commerce Gateway This section describes those additional requirements Understand Standards If traditional EDI transactions are being implemented the following must be understood Understand Standard Components Implementers must be familiar with all EDI standards components i e segments elements and code values that make up EDI transactions for which the E Commerce Gateway interface is being implemented Implementers must know which elements in an EDI transaction correspond with fields in an Orac
532. s service interface for integration with any system application or business partner The Oracle Integration Repository is shipped as part of the E Business Suite As your instance is patched the repository is automatically updated with content appropriate for the precise revisions of interfaces in your environment Online Documentation Note that all Oracle Applications documentation is available online HTML or PDF xiii e PDF Documentation See the Oracle Applications Documentation Library for current PDF documentation for your product with each release The Oracle Applications Documentation Library is also available on OracleMetaLink and is updated frequently e Online Help Online help patches HTML are available on OracleMetaLink e Oracle Electronic Technical Reference Manual The Oracle Electronic Technical Reference Manual eTRM contains database diagrams and a detailed description of database tables forms reports and programs for each Oracle Applications product This information helps you convert data from your existing applications and integrate Oracle Applications data with non Oracle applications and write custom reports for Oracle Applications products The Oracle eTRM is available on Oracle MetaLink Related Guides You may want to refer to Oracle Applications implementation documentation when you set up and use Oracle e Commerce Gateway You can read the documentation online by choosing Library from the expanda
533. s successfully and the data is loaded into the base Oracle Applications tables Inbound Transactions in a Multi Organization Environment A single inbound transaction interface file may contain data designated for different organizations defined in Oracle Applications The Oracle e Commerce Gateway import program will process all the data associated with the organization identified by the Responsibility of the person initiating the import process All data designated for other organizations will be flagged as an exception To import the remaining data you must switch to the Responsibility associated with the other organization and then initiate the import process You can continue this approach until all data for all organizations have been processed Testing Outbound Transactions When implementing a new outbound transaction for an existing Trading Partner or a new Trading Partner transaction combination it is recommended that you test at several levels You should first test with your internal systems followed by your Translator then finally with your Trading Partner While you are in the test mode you can set the trading partner transaction combination in Oracle e Commerce Gateway to test status that will alert all parties that this is a test transaction Set your trading partner transaction combination to production status when you are ready to transmit a production transaction to your Trading Partner The focus of this chapter is on testin
534. saction can proceed through the application Transactions with a TEST_INDICATOR value of T are validated and archived but no further processing is done In the Release Management Workbench Test Transactions require that the Test check box is checked This allows test transactions to be tested in a production environment for front end data validation To fully test a transaction through a test database environment the transactions must be flagged as production to go beyond just the validation This Demand Processor feature facilitates set up and implementation for inbound demand schedules with new trading partners DOCUMENT_CODE This column represents the customer assigned schedule reference or release number TP_TRANSLATOR_CODE TP_LOCATION_CODE EDI Location Code The two columns in combination uniquely identify a Trading Partner in Oracle e Commerce Gateway Once the trading partner definition is accessed Oracle e Commerce Gateway can verify whether the transaction is enabled for the Trading Partner If this trading partner is not defined in Oracle e Commerce Gateway a process rule 6 162 Oracle e Commerce Gateway Implementation Manual exception is detected and an exception message will display in the View Staged Documents window Refer to the Trading Partner chapter for details on how to properly define your trading partners and get a better understanding of how these fields are used in the process TRANSACTION_DATE_TIME T
535. sages that appear in the Oracle e Commerce Gateway windows and are usually a result of an input error The second category is a list of the common error messages that are a result of validating and processing transactions These error messages can be viewed either in the concurrent manager log file or in the View Staged Documents window 8 2 Oracle e Commerce Gateway Implementation Manual Common Window Error Messages Message Description and Solution Code Values are defined for this category code You cannot delete it The defined lookup table lookup column or condition is invalid This Category Code is assigned to a transaction You cannot delete it Description The user attempted to delete a code conversion category from the Define Code Conversion Category window The category has code conversion values assigned to it This prevents the category from being deleted Solution All code conversion values assigned for this category to transactions must be removed before the code conversion category can be deleted This can be accomplished by using the Define Code Conversion Values window Description The user attempted to define a simple lookup column rule in the Interface File Definition window Solution Either the value specified for the table lookup column or the lookup condition is invalid Research which value is invalid and correct it Description The user attempted to delete a code conversion category
536. ses and flexfields are used in the file Except for reusable records defined by the Oracle e Commerce Gateway the record layout may have a different meaning across transactions For example the record layout Transaction Interface File Architecture 5 17 IT may contain different data depending upon the transaction Record Layout Qualifiers 98 100 Record qualifier codes qualify what type of data is on the reusable records or any other record in the transaction For example an AD address record must be qualified as a specific type of address record for visual purposes such as a ship to bill to or remit to Other record qualifiers are assigned to every record in the transaction to complete the record key but they do not necessarily facilitate data mapping since only the record number uniquely identifies a record to the Translator The following table illustrates a sample record number record layout code record qualifier code and the contents Refer to Common Records based on record layout codes page 5 19 for record layouts Sample Record Layout Record Number Record Layout Record Qualifier Content 0010 CT CTL Control Record 1010 AD ST1 Address Record with Ship to Location Data 1040 AD BT1 Address Record with Bill to Location Data 1060 A1 HD1 Flexfield data with Reusable Record A1 Layout qualified by HD1 1070 A2 HD2 Flexfield data with Reusable Record A2 Layout qualified by HD2 2000 IT ITM IT for Item data quali
537. shooting Error Messages Inbound Transactions Transaction Exception Summaries Reports Troubleshooting This chapter provides useful information that aids the user in determining the solutions to common Oracle e Commerce Gateway issues and error messages It also provides tips that enable the implementation process to progress smoothly The topics covered in this chapter include Utilizing the enhanced run time execution log or tracing capabilities Common window and processing error messages Miscellaneous troubleshooting tips The purpose of and how to use the View Staged Documents window The use of Oracle e Commerce Gateway reports as a troubleshooting tool Run Time Execution Log When a transaction fails the information that is reported by the concurrent manager in the output file usually is not sufficient enough to allow the user to determine the Troubleshooting 8 1 possible cause of the error Many times the information that is reported has to be physically located in the program to figure out the point of failure Since access to the program and an extensive knowledge of SQL is required the user has a difficult time diagnosing the cause of the problem The user has the ability to activate the run time execution log or tracing capabilities at run time to get additional data about the problem This feature displays as much data as it can about the transaction and the program flow The user has the option of specifying the
538. shows the position length code and content of the Common Key elements Transaction specific data in the PYO transaction Common Key Position Length Code Content 1 25 25 TP_CD Trading Partner Code as defined in the EDI Translator 26 47 22 BATCH Payment Batch Number 48 69 22 INVOICE Invoice Number 70 91 22 blank Not Used 92 95 4 varies Record Number 96 97 2 varies Record Layout 98 100 3 varies Record Layout Qualifier The following table shows the Common Key positions 1 100 for the records of the Outbound Payment Order Remittance Advice transaction Transaction Summary Layouts A 95 Transaction specific data in the Common Key of the PYO transaction per record Record TP_CD Ref 1 BATC H Ref2 Ref 3 INVOIC blank E Record Number Record Layout Record Layout Qualifie r 1 Control Record 2 Trading Partner Header Attribut es 3 Trading Partner Header Attribut es 4 Trading Partner Header Attribut es 5 Trading Partner Header Attribut es 6 Trading Partner Detail Attribut es 7 Trading Partner Detail Attribut es TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD 0010 0020 0030 0040 0050 0060 0070 CT A1 A2 A2 A2 A1 A2 CTL TH1 TH2 TH3 TH4 TD1 TD2 A 96 Oracle e Commerce Gateway Implementation Manual Record TP_CD Ref 1 BATC H Ref 2 Ref 3 Record INVOIC blank
539. sitting in the Receiving Open Interface tables using the Transactions Status Summary window and then re import the updated transaction using Oracle e Commerce Gateway Oracle Warehouse Management Required Fields The following table lists the Oracle Warehouse Management required fields if you have licensed Oracle Warehouse Management and wish to receive LPN data on the ASN If the required data is not provided in the transaction the Oracle Warehouse Management Import process fails to preprocess the LPN data from the ASN The remainder of the import process may succeed without LPN data Oracle Warehouse Management Required Fields Oracle Warehouse Record Number Position Number Note Management Column Name LICENSE_PLATE_N 4000 10 LPN Number UMBER LOT_NUMBER 4000 20 NULL for non lot controlled FROM_SERIAL_NU 4000 30 NULL for non serial MBER controlled TO_SERIAL_NUMBE 4000 40 NULL for non serial R controlled QUANTITY 4000 50 Quantity on LPN UOM_CODE_INT 4000 60 Internal UOM Code UOM_CODE_EXT 4000 70 External UOM Code if code conversion defined License Plate Data LICENSE_PLATE_NUMBER This column identifies the License Plate Number that identifies the container for this line of material In order to be successfully processed this number must be a new LPN 6 120 Oracle e Commerce Gateway Implementation Manual number not previously defined in Oracle WMS If the number already exists the ASN will be processed without LPN data
540. ss trading partner specific maps codes data and their entire profile It is copied to the Translator Code field in the Trading Partner Detail tab in the Define Trading Partner window in the Oracle e Commerce Gateway It must be accurate The Translator Code along with the EDI Location Code are used to derive the trading partner site in the base Oracle Application It is written on every Control Record 0010 at the start of each transaction in the transaction interface file If the Translator Code is wrong then the data may be mapped to the wrong data map and or sent to the wrong Trading Partner Available Reports These reports should be present in one form or another on a Translator Some Translators provide additional reports the ability to develop different reports and the ability to execute user defined queries on Oracle and other databases to produce other reports Implementation Details 4 31 e Transaction Interface File Definition Report The record layout expected for outbound transactions and produced for inbound transactions e Transaction Data File Report Used to validate a data file against its record layout e Trading Partner Definition Report Shows the data entered for each Trading Partner such as contacts Translator Code and method of communication e Trading Partner Map Report Show the translation map for a given Trading Partner or set of trading partners Changes in Record Layout due to Upgrade Patch or C
541. st data element in the record is written to the transaction interface file e Do not change the seeded process rules these are required You may change the process rule action as necessary e Do not change the seeded column rules for data elements that are required by Oracle e Commerce Gateway or Oracle Applications Open Interface These data elements have the Value is Required column rule defined for it Refer to the Application Transaction Detail chapter for a list of required fields by transaction Delete Unused Data Elements and Records During the design process the transaction interface file is defined to accommodate every relevant data element from Oracle Applications including descriptive flexfields However not all data elements are mapped or used because either the message standards or the trading partner did not require it To maximize efficiency delete all unused data elements and records using the following guidelines e Delete all unused Oracle e Commerce Gateway and Oracle Applications descriptive flexfields e Delete all unused Oracle Applications free form text fields such as attachment notes and descriptions e Retain at minimum one of the five allocated external fields in case you want to activate code conversion for the data element in the future Delete all other unused external fields e Do not delete the control record or any data elements in the record This record is required e Do not delete any data el
542. stood by everyone involved with the upgrade process Note the following regarding the upgrade process e Plan the upgrade by reading all the steps that apply to your products before beginning This allows the user to determine the most efficient way to prepare for and finish the process given the unique combination of products e Failure to complete the upgrade preparation and upgrade finishing steps correctly can adversely affect the upgrade process e You must be at release 11 5 7 11 5 8 11 5 9 CU2 or 11 5 10 CU2 of the Oracle Applications to upgrade to Release 12 If you are on any earlier release must upgrade to 11 5 10 CU2 before you can upgrade to R12 See Oracle Applications Upgrade Guide Release 11i to Release 12 for details e Pay close attention to all warnings that indicate where and when you run upgrade steps Carefully coordinating your upgrade preparation work across different products will avoid errors If you are an Automotive customer review the Release 12 Automotive Upgrade documentation to insure that all pre upgrade and post upgrade steps are performed For existing Oracle Order Entry users it is important to note that Oracle Order Entry is not included in the initial Release 12 and thereby the inbound Purchase Orders 850 ORDERS and the outbound Departure based Shipping Notice Manifest 856 DESADV transactions will not be available for use until the new Oracle Order Management product is released It is importa
543. supplier s item revision level This field is for display only This field is not used in the Inventory tables to look up the supplier item Original System Reference Data ORIG_SYS_DOCUMENT_REF ORIG_SYS_LINE_REF ORIG_SYS_SHIPMENT_REF See Definition above CREATED_BY This code identifies who loaded this transaction into the Order Import tables The code is set to the Requester ID associated with the concurrent manager request that processed this transaction CREATION_DATE Application Transaction Detail 6 43 This is the date that the e Commerce Gateway loaded the transaction into the Order Import table entries This date is set to the system date LAST_UPDATE_DATE This date is equal to the CREATION_DATE for this transaction This date is set to the system date LAST_UPDATED_BY This code is equal to the CREATED_BY code for this transaction OE_CREDITS_INTERFACE Table If you do not plan to use this feature you should deactivate the records that are associated to this table If you do not deactivate the records errors will occur in the Order Import validation because the records will be incomplete Records are activated and deactivated in the Transaction Definition window in the e Commerce Gateway ORDER_SOURCE_ID This code identifies that the transaction was loaded into Order Import via the e Commerce Gateway DEFAULT The code is set to 6 meaning EDI Original System Reference Data Update Columns ORIG_
544. t e Seed Data Reconciliation process For outbound transactions if data cannot be found in the transaction interface file as defined by the Oracle e Commerce Gateway supplemental data may be found in user defined flexfields or the user defined transaction extension tables Data may also be mapped to transaction flexfields for inbound transactions Custom code is required to populate the transaction extension tables if that option is used for outbound transactions If there are still gaps in the data determine the best way to address data or functional gaps Two alternatives may be followed for inbound transactions Implementation Positioning 2 5 e Custom modifications may be necessary in the base application e This applies to outbound transactions there may be the case where the transaction passed all the validation in the Oracle e Commerce Gateway but the application open interface may still require additional data Write custom code to add data to the transactions in the application open interface tables This custom code is executed after the Oracle e Commerce Gateway wrote the transactions to the application open interface table but before the application open interface executes e For inbound transactions modifications should be made similarly to those made to populate the extension tables Transaction Processing The Oracle e Commerce Gateway creates transactions by the following methods e A transaction is initiated by an eve
545. t defined at the optional lower levels they will default from higher levels There are three levels where the Processing Rules can be defined Ship From Customer mandatory Ship From Address optional Ship From Customer Item optional can be linked to either of the other two levels Release Management Demand Processor Required Fields The Release Management Demand Processor is used to process Planning Material Release Shipping Schedule and Production Sequence Schedule transactions It validates the incoming data entered into the Release Management interface tables by the Oracle e Commerce Gateway import program The following is a list of the Release Management Demand Processor required fields These fields are required for the Release Management Demand Processor to successfully process and move the data from the Release Management interface tables into the Oracle Order Management and Oracle Planning base application tables Required fields noted as derived or hardcoded do not require a value in the transaction on the transaction interface file since the values are determined by the Oracle e Commerce Gateway process RLM_INTERFACE_HEADER Table The following table lists the required fields for the RLM_INTERFACE_ HEADER table 6 168 Oracle e Commerce Gateway Implementation Manual Required Fields for the RLM_INTERFACE_HEADER Table Oracle Applications Column Name for Required Fields Oracle e Commerce Gateway Column
546. t for the record layout code A6 Descriptive Flexfields This table has a similar layout to A5 for flexfields 5 8 9 12 and 13 15 5 24 Oracle e Commerce Gateway Implementation Manual Record Layout Code A6 Seq Flexfields Length 1 Common key including 100 Record Number 2 Shipment Allowance Charge 70 Flexfield 5 Internal AETC_Reason_Code 3 Shipment Allowance Charge 25 Flexfield 5 External 4 Shipment Allowance Charge 70 Flexfield 6 Internal 5 Shipment Allowance Charge 25 Flexfield 6 External 6 Shipment Allowance Charge 70 Flexfield 7 Internal 7 Shipment Allowance Charge 25 Flexfield 7 External 8 Shipment Allowance Charge 70 Flexfield 8 Internal 9 Shipment Allowance Charge 25 Flexfield 8 External Address AD Record Layout The following table shows the record layout of the AD Address Record record code type All name and address records that have explicit state province and county data have the following format There may be cases where the interface process does not populate some of the data fields depending on data availability Transaction Interface File Architecture 5 25 Address AD Record Layout Seq Business Entity Length ASC X12 Data 1 Common Key 100 including Record Number 2 Business Entity Site 60 Internal Code internal 3 Business Entity Site 35 N104 Code external EDI Location Code 4 Business Entity Name 60 N102 5 Business Entity 35 N301 Address Line 1 6 Business
547. t process exception It indicates that the test flag in the transaction is different than the test production indicator in the Define Trading Partner window Details tab for the transaction being imported For example the test flag in the transaction may contain a value of P production and the Test box may be checked in the Details tab for the transaction being imported These values must correspond for the import process to work properly Solution If the problem exists in the incoming transaction then the associated records with this document should be deleted from the View Staged Documents window and the Trading Partner needs to be notified that there was a problem with the transaction The Trading Partner needs to be informed that this data needs to be corrected by them and the appropriate documents retransmitted Also check the data map in the translator to review what it writes to the transaction interface file If the problem is due to incorrect Trading Partner set up in Oracle e Commerce Gateway then the user should make the required correction and resubmit the document from the View Staged Documents window 8 8 Oracle e Commerce Gateway Implementation Manual Message Description and Solution A Trading Partner with Translator Code lt translator_Code gt EDI Location Code lt location_code gt map lt map_code gt for the lt transaction_type gt transaction is not defined Unable to process the xxx
548. ta Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner SCH_R SEQ SEQ_S Number Layout Layout EF UBLINE Qualifie r 30 More TP_CD SCH_R SEQ 3120 13 IT3 Custom EF er Referen ce Data includin g Dock FBO Configu ration Key 31 Item TP_CD SCH_R SEQ 3140 RF LIN Detail EF Referen ce Codes and Values 32 Custom TP_CD SCHR SEQ 3180 PD LIN er s item EF descript ion 33 Custom TP_CD SCH_R SEQ 3200 TD QER er EF transpor tation data 34 Item TP_CD SCH_R SEQ 3220 NT ITM Note EF Text 35 Handlin TP_CD SCHR SEQ 3240 HZ HZ1 g and EF Hazard ous data A 226 Oracle e Commerce Gateway Implementation Manual Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner SCH_R SEQ SEQ_S Number Layout Layout EF UBLINE Qualifie r 36 Ship De TP_CD SCHR SEQ 3260 SD SDR livery EF Pattern 37 Line TP_CD SCH_R SEQ 3300 Al si Flexfiel EF ds 38 Line TP_CD SCH_R SEQ 3320 A2 SI2 Flexfiel EF ds 39 Line TP_CD SCH_R SEQ 3340 A2 SI3 Flexfiel EF ds 40 Line TP_CD SCH_R SEQ 3360 A2 SI4 Flexfiel EF ds 41 Industr TP_CD SCH_R SEQ 3380 A1 IN1 y EF Flexfiel ds 42 Industr TP_CD SCH_R SEQ 3400 A2 IN2 y EF Flexfiel ds 43 Industr TP_CD SCH_R SEQ 3420 A2 IN3 y EF Flexfiel ds 44 Industr TP_CD SCH_R SEQ 3440 A2 IN4 y EF Flexfiel ds Transaction Summary Layouts A 227 Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner SCH_R SEQ SEQ_S Number Layout Layout EF UBLINE Qualifie r 45 Trading
549. tact 12 Shipme TP_CD SHIPM 1200 Al SH1 nt ENT Header Flexfiel ds 1 4 13 Shipme TP_CD SHIPM 1210 A2 SH2 nt ENT Header Flexfiel ds 5 9 14 Shipme TP_CD SHIPM 1220 A2 SH3 nt ENT Header Flexfiel ds 10 14 15 Shipme TP_CD SHIPM 1230 A2 SH4 nt ENT Header Flexfiel d15 16 Basic TP_CD SHIPM LINE 2000 L1 IT1 Item ENT Data 17 Hazard TP_CD SHIPM LINE 2010 L2 IT2 ous ENT Material Codes A 130 Oracle e Commerce Gateway Implementation Manual Record TP_CD Ref1 Ref 2 Ref 3 Record Record Record SHIPM LINE blank Number Layout Layout ENT Qualifie r 18 Currenc TP_CD SHIPM LINE 2020 L3 IT3 y Tax ENT Item Level 19 Notes TP_CD SHIPM LINE 2030 N1 ND1 ENT 20 Shipme TP_CD SHIPM LINE 2100 Al SL1 nt Line ENT Flexfiel ds1 4 21 Shipme TP_CD SHIPM LINE 2110 A2 SL2 nt Line ENT Flexfiel ds 5 9 22 Shipme TP_CD SHIPM LINE 2120 A2 SL3 nt Line ENT Flexfiel ds 10 14 23 Shipme TP_CD SHIPM LINE 2130 A2 SL4 nt Line ENT Flexfiel d15 24 Order TP_CD SHIPM _ LINE 2140 Al RC1 Line ENT Flexfiel ds 1 4 25 Order TP_CD SHIPM LINE 2150 A2 RC2 Line ENT Flexfiel ds 5 9 Transaction Summary Layouts A 131 Record TP_CD Ref1 Ref 2 Ref 3 Record Record Record SHIPM LINE blank Number Layout Layout ENT Qualifie r 26 Order TP_CD SHIPM LINE 2160 A2 RC3 Line ENT Flexfiel ds 10 14 27 Order TP_CD SHIPM LINE 2170 A2 RC4 Line ENT Flexfiel d15 28 Destinat TP_CD SHIPM LINE 3000 AX ST ion ENT Address Code 29 Destinat TP_CD SHIP
550. tail 6 127 Oracle Receivables Transactions Transaction Direction Transaction ASC X12 EDIFACT Name Code Invoic Outbound INO 810 INVOIC Credit Outbound CDMO 812 CREADV DEBA Memo Debit DV Memo The topics covered for outbound transactions include the following e Trading Partner Link to Oracle e Commerce Gateway e Relevant Oracle Application Profiles and Setups e Extract Criteria e Columns Updated Upon Extraction Current Information The transaction requirements may change when enhancements are made such as additional data added to the transaction Current transaction details can be found on Oracle Support s web site Current detail record layouts are reported via the Transaction Layout Definition Report and the Interface File Data Report Outbound Invoice INO 810 INVOIC Trading Partner Link to Oracle e Commerce Gateway Customer and customer sites are defined in either Oracle Receivables or Oracle Order Management Included in the definition is the EDI Location Code that trading partners agree to exchange to represent the full detailed address Often they do not send the full address but just the EDI Location Code This is a critical data field to Oracle e Commerce Gateway The EDI Location Code is the link between a customer customer site in Oracle Applications and the trading partner site definition in Oracle e Commerce Gateway This enables Oracle e Commerce Gateway to access the detailed data about the customer
551. tbound Transaction Transaction Data Data 24 Control 10 see Note not Number 2 page 5 10 applicable below 25 Control 10 see Note not Number 3 page 5 10 applicable below Control Record Field Descriptions The following table lists the data elements that comprise the Control Record 0010 along with the sequence of the element its value and any notes Control Record Field Descriptions Note Check the Control Record 0010 layout using the Interface File Definition window for the position of this data if they are defined for the transaction Seq Data Element Value Note Translator Code short Key 1 short Key 2 First 25 characters of the Translator Code This is the Trading Partner identifier for this transaction as defined by the Translator First 22 characters of Document Code Do not use in the Translator data map since it may be truncated Second level document identifier 5 10 Oracle e Commerce Gateway Implementation Manual Seq Data Element Value Note 10 Key 3 Record Number Record Layout Record Qualifier Communication Method Test Flag Document ID 0010 CT CTL E EDI T test P production Depends on the transaction Sample POI PO Inbound Third level document identifier Fixed value 0010 Fixed value CT Fixed value CTL This code indicates if this transaction is to be faxed or sent via the EDI sta
552. te in the base Oracle Application or assigning a different supplier supplier site to that EDI Location Code in Oracle e Commerce Gateway Refer to the Trading Partner chapter for recommendations on selecting the correct trading partner EDI Location Code for the control record 0010 for the transaction in the transaction interface file Application Transaction Detail 6 97 Oracle e Commerce Gateway Required Fields The following table lists the Oracle e Commerce Gateway required fields These fields are required to authenticate the trading partner and transaction If the required data is not provided in the transaction the Oracle e Commerce Gateway import process fails the transaction Then an exception message is displayed in the View Staged Documents window If the trading partner is valid and the transaction is enabled the import process proceeds to validate the transaction using the user defined column rules If no process or column rule exceptions are detected the Oracle e Commerce Gateway import program will write the transaction to the Purchasing Documents Open Interface tables to be processed by the Purchasing Documents Open Interface API Oracle e Commerce Record Number Position Number Note Gateway Column Name for Required Fields TEST_INDICATOR 0010 20 T or P DOCUMENT_ID 0010 30 Constant CATT or RRQI TP_TRANSLATOR_C 0010 70 Translator identifier ODE for this Trading Partner TP_LOCATION_CO 0010 80 The EDI
553. tegories Add additional Code Conversion Categories if needed for your code conversion value table entries Enable the number of search keys that you will use in the code conversion value table for each Code Conversion Category if you are using search keys 2 Enable Code Conversion Locate the transaction format map and transaction level that has the column data element name that you need to enable for code conversion You enable a column for code conversion by entering a code conversion category in the Category column When this is done only code conversion value table entries with the code conversion category will be accessed during code conversion for that column If you use search keys enter the column name that contains the value to be used as part of the search key 3 Define Code Conversion Values Enter all the data for the code conversion value tables Category Description Direction Search Key 1 Key 5 Oracle internal code External code 1 external code 5 Interface with Translators The Translator is a third party software application designed to transform a formatted file into any other format Traditionally it transforms proprietary formats to EDI transactions according to the designated standard e g X12 EDIFACT It considers both the data required by the chosen standard and the data required by the trading partner It maps the data from the transaction interface file to the required file format according to t
554. tegory Required Default Value Scheduling Specific Transaction Profile Option ECE_SPSO_EXC Sets the profile Functional No No LUDE_ZERO_S value to prevent CHEDULE_FRO zero schedule M_FF from being written to flat file For more profile category information see Oracle Applications System Administrator s Guide Maintenance for details Outbound Purchase Order Transaction Profile The ECE_POO_ATT_SEG_ SIZE sets the attachment segment size for the outbound purchase order transaction Attachments can be split into segments to accommodate their insertion into the interface file The size of the attachment should be synchronized in three places The following table illustrates where to change it Implementation Details 4 11 Outbound Purchase Order Transaction Profile Setup for Text Length Profile Options window Transaction Profile Setup Interface File Definition window Note Original Change Use Sets the 400 80 80 attachment size for the transaction Attachments can be split into segments to accommodate their insertion into the interface data file The segment size is expressed in bytes The default is 400 Set to the same 800 80 80 length as the attachment If the data element on the file is excessively long the data element will have many trailing blanks If the data element on the file is not long enough the data may be truncated 4 12 Oracle e Commerce Gateway Implementation M
555. tempts to find code conversion table entries for an outbound transaction The Oracle e Commerce Gateway extracts data from Oracle Application tables and optional extension tables then ultimately writes the data to the transaction interface file Some date elements need code conversion from the internal code defined in the base Oracle application to external codes that are required by the Trading Partners or standard transactions You may activate code conversion only on the data elements columns listed in the Assign Categories window By entering search keys the table entry does not apply to all Trading Partners Trading Partner codes and Trading Partner site codes are often search keys in the code conversion value tables since Trading Partners often have site specific codes This example steps through a code conversion table searching for a table entry where the value Over Night in the CARRIER_INT internal column along with its search keys with the value GAMMA in CUSTOMER_NAME in Key 1 and value 9999 in CUSTOMER SITE in Key 2 are set up for the transaction The intent is to find its corresponding 1 5 external CARRIER_EXT1 through CARRIER_EXT5 codes so they may be written to the transaction interface file The code conversion value table is read with the following parameters and conditions It is used to derive the 1 5 external codes desired for the transaction interface file e Access code conversion values table entries with the SHIP_VIA
556. tent provided on third party Web sites You bear all risks associated with the use of such content If you choose to purchase any products or services from a third party the relationship is directly between you and the third party Oracle is not responsible for a the quality of third party products or services or b fulfilling any of the terms of the agreement with the third party including delivery of products or services and warranty obligations related to purchased products or services Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party Oracle JD Edwards PeopleSoft and Siebel are registered trademarks of Oracle Corporation and or its affiliates Other names may be trademarks of their respective owners Contents Send Us Your Comments Preface 1 Introduction Purpose of the Implementation Manual 00 00 cc cece cee eee eres eeee sees eteneseeseneeeeeeeneeenees 1 1 Documentation saa a aaa AA A aa aa gachages e aa aa anA E sahaa AENEAN anes 1 2 Oracle e Commerce Gateway OvervieW essssisessriisrisiisrirsrististrninsrnntnstrnrinsrnnnnnnrnren stenens 1 2 Processing Traditional EDI Transactions 00c ccc ee ee eee eee eeee eres eteneeeneeseeeeeneeeeee 1 10 EDL Translators 12 0 scss fisciisesd cccessiatlcchantecegtetidtaceseuseatunatiauchiol bid caguataatsdedandd aa aaant 1 14 2 Implementation Positioning Implementation Positioning
557. tering the direction OUT allows you to enter the entire search key for outbound transactions yet allow duplicate data to be entered for the external codes 1 5 If code conversion is enabled and a table entry is not found then internal code is also copied to the external 1 data element to be written on the transaction interface file The following tables have illustrations using only 2 of the 5 allowable keys and 2 of the 5 external codes for simplicity Use as many keys and external codes as necessary for Code Conversion 10 11 your business needs Though the illustrations have separate samples by the direction IN OUT BOTH all the table entries reside in one table The columns Category Direction Key 1 Key 2 and Internal Code are supplied by the outbound transaction These five pieces of data comprise the entire search key and the key must be unique Columns External Code 1 and External Code 2 are data that are retrieved for the transaction interface file Example of Code Conversion for Outbound Transaction using Direction OUT note Category Direction Key 1 Key 2 Internal External External Code Code 1 Code 2 1 UOM OUT Each EA PC 1 UOM OUT Box EA PC 2 UOM OUT EDIFACT Each PC 2 UOM OUT X12 Each EA 3 SHIP_VI OUT 1004 1110 Truck air TRUCK A A 3 SHIP_VI OUT 1004 1110 Truck mo TRUCK J A tor 3 SHIP_VI OUT 1004 Truck air TRUCK J A motor 3 SHIP_VI OUT 2010 1005 Alpha air ALPHA A A 3 SHIP_VI OUT 2010 1
558. teway transaction Reference the Oracle Application Flexfields Guide for details Extensible Architecture The Extensible Architecture feature of the Oracle e Commerce Gateway provides a powerful and flexible method to include additional data for outbound transactions While most business needs for additional data can be accommodated by the use of the Descriptive Flexfields feature in the Oracle Applications the Extensible Architecture feature is useful when e More data elements are required than are allowed by the use of Descriptive Flexfields e Data elements need to be extracted from custom Oracle application tables e Data elements need to be extracted from outside the Oracle Applications Each outbound transaction in the Oracle e Commerce Gateway contains a series of interface tables to hold the data that is extracted and denormalized from the relevant Oracle application base tables before being written to the outbound interface file Every interface table in the Oracle e Commerce Gateway also has an associated extension table which may be customized to fit the business needs Each record in an interface table is linked to the corresponding record in the associated extension table Consequently when the interface table record is written to the outbound transaction interface file the corresponding extension table record is written as well The source data to be copied to the extension tables may come from a standard or custom Oracle d
559. text associated with the EDI Responsibility Multiple Organization Note The list of values for Partners in the Define Trading Partner header window lists Partner definitions from ALL organizations If the Trading Partner names need to be identified by organization an organization indicator may be entered as a suffix or prefix in the Trading Partner Name The use of a suffix or prefix gives a different sort order of the Partner list Implement the preference which your organization finds helpful for sorting and viewing Trading Partner names online Define Trading Partner Assignment Tab The Assignment tab of the Define Trading Partner window links the Trading Partner definition to the appropriate Trading Partner and Trading Partner address site in the base Oracle Application Select the correct Trading Partner and Trading Partner site to associate with this Trading Partner site The Oracle e Commerce Gateway defines Trading Partner at the address level The base Oracle Application is likely to define many address sites for a single customer Trading Partner 9 25 supplier or bank Consequently there will be many Oracle e Commerce Gateway Trading Partners associated with a single customer supplier or bank as defined in the base Oracle Application In a multiple organization environment only those customer addresses defined to the operating unit for the current EDI responsibility are presented for selection Multiple Organiza
560. the Schedule type Valid Values PLANNING SHIPPING SEQUENCED SCHEDULE_PURPOSE_INT This column represents the Schedule Purpose code Valid Values ADD ORIGINAL REPLACE CANCEL CHANGE DELETE and CONFIRMATION SCHEDULE_SOURCE Application Transaction Detail 6 163 This column represents the EDI or manual transaction source for this schedule For example 830 862 866 DELFOR MANUAL ITEM_DETAIL_TYPE_INT Detail Type is used by the Demand Processor to determine how the schedule line itself should be interpreted Valid Values 0 Past Due Firm 1 Firm Demand 2 Forecast Demand 3 Authorization 4 Shipment Receipt Data 5 Other ITEM_DETAIL_SUBTYPE_INT Detail Subtype is used by the Demand Processor to determine how the schedule line itself should be interpreted in context of its corresponding Detail Each Detail Type has a corresponding list of valid Detail Subtypes as shown in the following table If then ITEM_DETAIL_TYPE_INT ITEM_DETAIL_SUBTYPE_INT Equals Contains 0 1 2 1 Day 2 Week 3 Flexible 4 Month 5 Quarter 3 FINISHED Finished Goods MATERIAL Raw Material LABOR_MATERIAL Labor and Material LABOR Labor PRIOR_CUM_REQ Prior Cumulative Required 6 164 Oracle e Commerce Gateway Implementation Manual If then ITEM_DETAIL_TYPE_INT ITEM_DETAIL_SUBTYPE_INT Equals Contains 4 SHIPMENT Shipment RECEIPT Receipt CUM Customer CUM CUM_REJECTED CUM Rejected 5 A
561. the data is not what you intend it to be you must make the appropriate changes for the transaction to be extracted for the correct bank branch This could involve either altering the bank branch in the base Oracle Payables or assigning a different bank branch to that EDI Location Code in Oracle e Commerce Gateway Please note that if the trading partner is associated with multiple operating units then the transaction to be extracted is for a specified operating unit only linked to your responsibility To extract all the data for multiple operating units you still need to execute the program one by one by specifying different operating unit each time when you run the program See the Outbound Transactions chapter in the Oracle e Commerce Gateway User s Guide for details Refer to the Trading Partner chapter for recommendations on selecting the correct trading partner EDI Location Code for the control record 0010 for the transaction in the transaction interface file Relevant Oracle Payables Profiles and Setups The outbound Payment Order Remittance Advice transaction is an event driven process initiated in Oracle Payables as a payment format after the invoices are selected and the payment batch is created This transaction cannot be initiated from Oracle e Commerce Gateway The following is a list of the Payables set ups related to the outbound Payment Order Remittance Advice transaction Refer to the Oracle Payables User s Guide Creating 6
562. ther sources for data that can be used in defaulting including Pricing Agreements Order Type Line Type Item etc For a list of what Defaulting Rules are seeded with Order Management see the Oracle Order Management User s Guide Appendix E You can create your own Defaulting Rules by navigating to Setup Rules Defaults from the OM Superuser Menu There is a white paper on Using Defaulting Rules in Oracle Order Management that gives an explanation of the Defaulting Rules forms with examples of their use With appropriate use of Defaulting Rules you can significantly reduce the amount of data that has to be entered manually or populated in the Order Import tables Order Import Open Interface Data Levels The EDI standard transaction has three 3 key levels of data Header Line item and Schedules Shipments The Order Import open interface tables have a two level structure where the order line and a single shipment are combined into one table entry for each combination Order Import requires that line and shipment data be consolidated into the LINE level table For example if an order in a standard EDI transaction has an order line with five 5 shipments then the order line data is combined with each shipment detail in the transaction interface file Subsequently there will be five 5 detail table entries in the Application Transaction Detail 6 9 application Order Import open interface tables Standard Purchase Order EDI Transa
563. this form of database security operating system security must also be considered The file I O operations performed with UTL_FILE will be done by the Oracle user the Oracle user is the owner of the files that are used to run the database and also the owner of the processes that make up a database instance Consequently the Oracle user must have operating system privileges to read from and write to all of the accessible directories If the Oracle user does not have privileges for an accessible directory then any operations in that directory will be prohibited by the operating system To ensure that operating system security allows the Oracle user to create delete rename read and write files in the specified directories the DBA must grant directory 4 2 Oracle e Commerce Gateway Implementation Manual and file access privileges by issuing the CHMOD 777 command at the operating system level This is a UNIX example only so use operating system appropriate commands for your environment The Oracle instance must be brought down and back up for the changes in the init lt SID gt ora file to be effective Review Release 12 Upgrade Guideline Release 12 Upgrade This chapter provides general information about topics to consider while planning the upgrade to Release 12 To facilitate a successful upgrade to Release 12 make sure that the information contained in the Oracle Applications Upgrade Guide Release 11i to Release 12 manual is under
564. thout any code modifications Once the necessary changes are entered re run the Transaction Layout Definition Report and use the report output to synchronize your new transaction layout definitions with the Translator Refer to the Oracle e Commerce Gateway User s Guide for details on how to use the Transaction Layout Definition Report and the Interface File Definitions window The following table reviews some of the terms discussed in this section Implementation Details 4 23 Terms and Definitions Term Definition Data Element Record Common Key Control Record Record 0010 Transaction Interface File The smallest component of a transaction interface file A collection of data elements The first 100 bytes of every record containing key data about the Trading Partner and document The first record of every transaction containing key data about the transaction and trading partner A collection of records containing transaction specific data Refer to the chapter on Transaction Interface File Architecture for a detailed description of Oracle e Commerce Gateway s transaction interface file structure Change File Structure The structure of a transaction interface file is defined during the design process and is based on how the data will be mapped per the message standards The objective is to group the data in logical groups so that it can be easily mapped by the Translator The following are some guid
565. thout maintaining the detail data in Oracle e Commerce Gateway To ensure that the trading partner link between Oracle e Commerce Gateway and Oracle Applications is set up properly verify that the supplier supplier site and the EDI Location Code in Oracle Applications is the correct supplier supplier site selected for the Trading Partner definition in Oracle e Commerce Gateway The selected 6 124 Oracle e Commerce Gateway Implementation Manual supplier supplier site and the EDI Location Code defined in Oracle Applications are displayed in the Define Trading Partners window Assignment tab If the data is not what you intend it to be you must make the appropriate changes for the transaction to be extracted for the correct trading partner This could involve either altering the supplier supplier site in the base Oracle Application or assigning a different supplier supplier site to that EDI Location Code in Oracle e Commerce Gateway Please note that if the trading partner is associated with multiple operating units then the transaction to be extracted is for a specified operating unit only linked to your responsibility To extract all the data for multiple operating units you still need to execute the program one by one by specifying different operating unit each time when you run the program See the Outbound Transactions chapter in the Oracle e Commerce Gateway User s Guide for details Refer to the Trading Partner chapter for recommendations
566. tion Note The list of values of Trading Partner addresses in the Assignment tab list only those addresses associated with the assigned operating unit When multiple operating units are associated with your responsibility if you want to associate a different set of addresses for the same Trading Partner group and same Trading Partner then you have to reselect the operating unit in the Trading Partner Groups form and then change the setup for the underlying Trading Partners The operating unit is relevant to the underlying addresses only and not to the Trading Partner groups or Trading Partner headers Define Trading Partner Contact Tab The Contact tab of the Define Trading Partner window is optional It contains contact data for the specified Trading Partner It may be used by the EDI Coordinator for the Trading Partner s EDI Coordinator s contact data This data is for reference only It is not used by Oracle e Commerce Gateway The Contact tab of the Define Trading Partner window is optional It contains contact data for the specified Trading Partner It may be used by the EDI Coordinator for the Trading Partner s EDI Coordinator s contact data This data is for reference only It is not used by Oracle e Commerce Gateway Define Trading Partner Details Tab The Details tab of the Define Trading Partner window defines the transactions the transaction types the Translator Code and the document standard for code conversion only to the T
567. tion Transaction Detail 6 107 Transaction Detail Records ORIGINAL_SYSTEM_LINE_REFERENCE This column represents the purchase order line number associated with the shipment PICK_SLIP_NUMBER This column represents the packing slip number from the supplier This number will be used during the PO receipt process to recall the shipment data related to the purchase orders and items in the shipment If no value is provided the Receiving Open Interface tries to default a value from the PACKING _ SLIP or INVOICE NUM columns The values in this column must be unique from the supplier for one year PURCHASE_ORDER_NUM This column represents the purchase order number associated with the shipment SHIPPED_UNIT_CODE_INT This column represents the shipment quantity unit of measure TRAN_PURPOSE_APPLICATION This column represents the transaction purpose code The valid values are NEW or CANCEL Place the value in record 1000 position 110 The default value is NEW if no value is provided on the inbound flat file The value entered for TRAN _PURPOSE_APPLICATION should be the same value entered for TRAN_PURPOSE_EXT1 in record 0010 position 50 Review Oracle e Commerce Gateway Exceptions Use the Oracle e Commerce Gateway View Staged Documents window to review the Oracle e Commerce Gateway transaction exceptions Once the exceptions are identified and resolved you can submit the transaction for reprocessing ignore the exception during reprocessing o
568. tion also facilitates custom code to generate Partner names from the base Oracle Application for initialization of the Trading Partner tables or during updates after implementation Trading Partner Naming Convention Recommended Components Component Description Sample Note Organization Organization Code A Trading Partnership Trading Partner ACME Trading Partner Site Address Site Code INDY This may be a site or more refined descriptor Description Free window text that A Acme Indy 45 describes the Meridian components above Other descriptive data can be added Example A ACME INDY for A Acme Indy 45 Meridian The following table lists examples of trading partner names using the prefix and suffix conventions and shows how the lists would be sorted 9 24 Oracle e Commerce Gateway Implementation Manual Examples of Trading Partner Names Using Prefix and Suffix Conventions Prefix Organization on Partner Name Suffix Organization on Partner Name A Acme SJ Acme Atl B A Beta Chic Acme Bos C B Acme Atl Acme SJ A B Beta Indy Beta Atl B C Acme Bos Beta Chic A C Beta Atl Beta Indy B Result Result Listed by Organization Listed by Partner name Trading Partner Lists All Trading Partners regardless of organization in a multiple organization environment are included in the list of values of Partner names in the Define Trading Partner window The Trading Partner names are not limited to the organization con
569. tions Flexfiel d15 Extensio n Tables Schedul e Level Basic Item Data Product Descript ion Hazard ous Material Data Contact Names Last Receipt Data Ship to Organiz ation Address Code Ship to Organiz ation Data TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD PS PS PS PS PS PS PS PS PS ITEM ITEM ITEM ITEM ITEM ITEM ITEM 1780 1900 2000 2010 2020 2030 2040 2050 2060 A2 Custo m IT IT HZ CN LS AX ST OP4 Custo m IT1 IT2 HZ1 IT1 LS1 SI2 SIS Transaction Summary Layouts A 239 Data Trading Partner Ref 1 PS Ref2 Ref3 ITEM SCHE DULE Record Number Record Layout Record Layout Qualifie r 42 43 44 45 46 47 48 Approv ed Supplier List Flexfiel ds 1 4 Approv ed Supplier List Flexfiel ds 5 9 Approv ed Supplier List Flexfiel ds 10 14 Approv ed Supplier List Flexfiel d15 Item Flexfiel ds 1 4 Item Flexfiel ds 5 9 Item Flexfiel ds 10 14 TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD PS PS PS PS PS PS PS ITEM ITEM ITEM ITEM ITEM ITEM ITEM 2100 2110 2120 2130 2150 2160 2170 Al A2 A2 A2 Al A2 A2 ASI AS2 AS3 AS4 IT1 IT2 IT3 A 240 Oracle e Commerce Gatew
570. tner is defined e Transaction type enabled for the trading partner e The original purchase order has been printed or previously extracted e The current set of purchase order changes have not been printed or previously extracted e Purchase order change status is Approved e Purchase order is not on hold If necessary you can use SQLPLUS to verify if there are any eligible documents to be extracted To do so you must first set the organization context and then issue the SQL count function as follows SQLPLUS gt execute fnd_client_info set_org context lt Org number gt SQLPLUS gt select count ECE POCO HEADERS V Review all your set ups if the count value is 0 as this indicates there are no eligible documents to be extracted Columns Updated Upon Extraction Once an eligible purchase order change is successfully extracted and written to the transaction interface file it is marked by Oracle e Commerce Gateway to prevent it from subsequent extraction The following table lists the fields updated based on an excerpt of code in the UPDATE_PO the outbound purchase order and purchase order change share this procedure procedure defined in the ECPOCOB pls file Table Column Value PO_HEADERS EDI_PROCESSED_FLAG Y PO_HEADERS LAST_UPDATE_DATE SYSDATE PO_HEADERS PRINTED_DATE SYSDATE PO_HEADERS PRINT_COUNT Increment by 1 PO_HEADERS_ARCHIVE EDI_PROCESSED_FLAG Y PO_HEADERS_ARCHIVE LAST_UPDATE_DATE SYSDATE
571. transaction through the Oracle e Commerce Gateway to validate the installation before any site specific configuration is undertaken Implementation Checklist for Fresh Install To help ensure a successful implementation do the following e Read the Introduction and become familiar with the pre requisites e Implement related Oracle Applications modules before implementing Oracle e Commerce Gateway e Become familiar with the Oracle e Commerce Gateway set ups If you are implementing Oracle e Commerce Gateway for the first time steps 2 and 3 described in the Implementation Checklist for Software Upgrade section are not required since there is no existing seed data to compare and reconcile Insert steps 1 1 and 1 2 from the table below All other implementation steps are still required in addition to defining an Oracle e Commerce Gateway responsibility to start the implementation process Implementation Checklist for Fresh Install Step Required Optional Description Reference IM Implementation Manual 1 1 Required Define Access IM Define Responisbilities Responsibilities 1 2 Required Define the utl_file_dir IM Define parameters Done by UTL_FILE_DIR DBA Parameter in INIT ORA File 2 Omit Run reports for each 3 8 Oracle e Commerce Gateway Implementation Manual transaction Step Required Optional Description Reference IM Implementation Manual 3 Omit Compare reports In summary the following has been set u
572. transaction using the user defined column rules If no process or column rule exceptions are detected the Oracle e Commerce Gateway import program will write the transaction to the Order Management Open Interface tables to be processed by the Order Management Open Interface API Oracle e Commerce Gateway Required Fields Oracle e Commerce Record Number Position Number Note Gateway Column Name for Required Fields TEST_INDICATOR 0010 20 T or P TP_DOCUMENT_ID 0010 30 POI TP_TRANSLATOR_C 0010 70 Translator identifier ODE for this trading partner TP_LOCATION_CO 0010 80 The EDI Location DE Code Control Record 0010 TEST_INDICATOR This column represents the test or production indicator from the Trading Partner If this value does not match the test or production indicator associated with the trading partner defined in Oracle e Commerce Gateway a process rule exception is detected Then an exception message is displayed in the View Staged Documents window Application Transaction Detail 6 7 The valid values are T for test and P for production TP_DOCUMENT_ID This column identifies the type of document being sent by the Trading Partner If this document type is not enabled for the trading partner defined in Oracle e Commerce Gateway a process rule exception is detected Then an exception message is displayed in the View Staged Documents window The valid value is POI for standard Purchase Order TP_TRANSLATOR_CODE TP_L
573. trol Records Only one record occurrence per transaction 1000 1900 Shipment Notice Header Only one record occurrence Records per transaction 2000 3900 Shipment Notice Item One set of records per item Records within the Shipment Notice header The following table is a summary list of the records that comprise the Inbound Shipment and Billing Notice transaction The table shows the functional data grouping Transaction Summary Layouts A 79 of records the data level the record numbers and relevant notes about the data grouping SBNI Transaction Record Summary Seq Type of Data Data Level Record Note 1 Control Record HEADER 0010 2 Shipment Notice HEADER 1000 Basic Header 3 Carrier Weights HEADER 1010 Packaging 4 Shipment HEADER 1020 Method of Payment 5 Currency Tax HEADER 1030 Payment Terms 6 Allowances Cha HEADER 1040 rges Freight 7 Hazardous HEADER 1050 Material Special Handling 8 Header Note HEADER 1090 9 Vendor HEADER 1100 Address Code 10 Destination HEADER 1120 Address Code 11 Destination HEADER 1130 Contact 12 Shipment HEADER 1200 1230 Flexfields Header Flexfields A 80 Oracle e Commerce Gateway Implementation Manual Seq Type of Data Data Level Record Note 13 Basic Item Data LINE 2000 14 Hazardous LINE 2010 Material Codes 15 Currency Tax LINE 2020 Item Level 16 Notes LINE 2030 17 Shipment Line LINE 2100 2130 Flexfields Flexfields 18 Transaction LINE 2140 2170 Fle
574. tructure is further described in the table below The following table shows the content and occurrences of the records comprising the Inbound Invoice transaction A 72 Oracle e Commerce Gateway Implementation Manual Record occurrences within the INI transaction Records Content Occurrences 0010 Control Records Only one record occurrence per transaction 0020 0070 Gateway Flexfields One set of records per transaction 1000 2999 Invoice Header Records Only one record occurrence per transaction 3000 4999 Invoice Item Records One set of records per item within the invoice header The following table is a summary list of the records that comprise the Inbound Invoice transaction The table shows the functional data grouping of records the data level the record numbers and relevant notes about the data grouping INI Transaction Record Summary Data Data Level Record Number Note 1 Control Record INVOICE 0010 HEADER 2 Basic Invoice INVOICE 1000 Header HEADER 3 Currency INVOICE 1010 HEADER 4 Bill From INVOICE 1020 Address HEADER 5 Invoice Header INVOICE 2000 2030 Flexfields Flexfields HEADER 6 Invoice Header INVOICE 2100 2140 Flexfields Global Flexfields HEADER Transaction Summary Layouts A 73 Data Data Level Record Number Note 7 Extension INVOICE 2900 Custom Tables Invoice HEADER Header 8 Basic Item INVOICE LINE 3000 9 Basic Item INVOICE LINE 3010 Description Tax 10 Invoice Line INVOICE L
575. ual Step Required Optional As Needed Required Required Description Compare the before and after upgrade reports for differences in transaction layout definitions and code conversion assignments Make the necessary changes Adjust transaction layout definitions Reassign code categories Since this is an upgrade there will not be any validation rule differences to reconcile Set up system profiles pay special attention to the profiles for inbound and outbound directory path Inbound file directory Outbound file directory Ensure that inbound and outbound directory paths defined in the system profile match UTL_FILE_DIR settings in INIT ORA file Restart the database if you made changes to the INIT ORA file Reference IM Implementation Manual User s Guide Changing the Interface Data File Record Layout Assigning Categories IM Modify Transaction Interface File IM Set Up Code Conversion Set up system profiles pay special attention to the profiles for inbound and outbound directory path Inbound file directory Outbound file directory IM Define UTL_FILE_DIR parameter in INIT ORA file Oracle e Commerce Gateway Implementation Checklist 3 3 Step Required Optional 6 As Needed 7 As Needed 8 Required for inbound transactions 9 Required for inbound transactions 10 Required for inbound transactions Description Set up general
576. uired 1900 010 UMENT_REF UMENT_REF ORIG_SYS_RES ORIG _SYS_RES Required 1900 030 ERVATION_RE ERVATION_RE F F OPERATION_C OPERATION_C _ If Null default 1900 040 050 ODE ODE _EXT1 to INSERT ORDER_SOURC ORDER_SOURC Hard code 6 E_ID E_ID meaning EDI ORIG_SYS_DOC ORIG _SYS_DOC_ Required 1950 010 UMENT_REF UMENT_REF OPERATION_C OPERATION_C _ If Null default 1950 030 040 ODE ORDER_SOURC E_ID ODE _EXT1 ORDER_SOURC E_ID to INSERT Hard code 6 meaning EDI The following table shows the line level records for OE_CREDITS_INTERFACE 6 34 Oracle e Commerce Gateway Implementation Manual Line Level Records for O0E_CREDITS_INTERFACE Oracle Oracle Hardcoded Deri Record Number Position Applications e Commerce ved Number Column Name Gateway for Required Column Name Fields ORIG_SYS_DOC ORIG _SYS_DOC Required 5000 010 UMENT_REF UMENT_REF ORIG_SYS_LINE ORIG_SYS_ Required 5000 030 _REF LINE _REF ORIG_SYS_SHIP ORIG_SYS_SHIP Required 5000 040 MENT_REF MENT_REF ORIG_SYS_CRE ORIG _SYS_CRE Required 5000 050 DIT_REF DIT_REF OPERATION_C OPERATION_C _ If Null default 5000 060 070 ODE ODE _EXT1 to INSERT ORDER_SOURC ORDER_SOURC Hard code 6 E_ID CREATED_BY LAST_UPDATE D_BY CREATION_DA TE LAST_UPDATE _DATE E_ID CREATED_BY LAST_UPDATE D_BY CREATION_DA TE LAST_UPDATE _DATE meaning EDI Derived Derived Set to SYSDATE Set to SYSDATE The following table shows the li
577. ultiple organizations you can associate trading partners with operating units linked to your responsibility during the trading partner group setups This feature allows you to run trading partner reports and outbound transaction extract concurrent programs for a specified operating unit associated with your responsibility Oracle e Commerce Gateway uses the concept of the security profile linked to your responsibility to control data access within multiple organizations A security profile defined based on organization hierarchies consists of one or more operating units to which a user has access for inquiry reporting transaction and data entry This security profile is then associated with a user through his or her responsibility This allows you to access data in multiple operating units without changing responsibility Three Processing Options Once all the necessary system transaction and trading partner level configurations are defined and you are ready to initiate a transaction Oracle e Commerce Gateway supports three processing options Event driven processing for time critical business transactions such as electronic payments or ship notices Schedule based processing for less critical but routinely used business transactions such as purchase orders User defined processing The processing option you select depends on the nature of your business and transaction criticality Once the transaction process is initiated the run
578. umber Number Column Gateway Name for Column Required Name Fields SHIP_TO_LO SHIP_TO_IN 3000 30 CATION_CO T_LOCATIO DE N_NAME DELIVER_T DELIVER_T 3020 10 O_LOCATIO O_LOCATIO N_CODE N_CODE_ INT DELIVER_T DELIVER_T 3020 70 O_PERSON_ O_PERSON_ NAME NAME CREATED_B CREATED_B Derived Y Y CREATION_ CREATION_ Derived DATE DATE GROUP_ID GROUP_ID Derived HEADER_IN Derived TERFACE_ID INTERFACE _ INTERFACE__ Derived TRANSACTI TRANSACTI ON_ID ON_ID LAST_UPDA LAST_UPDA Derived TE_DATE TE_DATE LAST_UPDA LAST_UPDA Derived TED_BY TED_BY PROCESSIN H BATCH G_MODE_C ODE Application Transaction Detail 6 115 Oracle Applications Column Name for Required Fields Cond Oracle e Commerce Gateway Column Name Hardcoded Derived Record Number Position Number PROCESSIN G_STATUS_ CODE RECEIPT_SO URCE_CODE SOURCE_DO CUMENT_C ODE TRANSACTI ON_DATE TRANSACTI ON_STATUS _CODE TRANSACTI ON_TYPE VALIDATIO N_FLAG CATEGORY_ ID CUSTOMER _ ID DELIVER_T O_LOCATIO N_ID DELIVER_T O_PERSON_I D Yes Yes Yes Yes H PENDING H VENDOR H PO H SYSDATE H PENDING H SHIP 6 116 Oracle e Commerce Gateway Implementation Manual Oracle Cond Oracle Hardcoded Record Position Applications e Commerce Derived Number Number Column Gateway Name for Column Required Name Fields EMPLOYEE_ Yes ID EXPECTED_ Yes RECEIPT_DA TE ITEM_CATE Yes GORY IT
579. umber by one for each of your fields The highest number fields are not likely to be used by the provided transaction There is a potential problem if you need more columns than are available for the given table You will lose data if you reuse FIELDnnn columns already used by the Oracle e Commerce Gateway provided transaction The method for assigning field numbers to your fields is illustrated in the following table Method for Assigning Field Numbers Transaction Purchase Starting FIELD number Ending FIELD number Order Outbound Interface Table Name Oracle e Commerce Gateway 1 n Transaction Available fields for N 1 500 transaction changes Your new fields Use numbers moving 500 backwards from 500 Extensible Architecture 11 11 Record Numbers The value for Record_Number may be any value within the range of the corresponding interface table values For example the Purchase Order Outbound POO transaction has the typical Header Line Line Detail output structure with the ranges shown in the following table Record Numbers for Purchase Order Outbound Transactions Transaction Purchase Order Outbound Record Number Range Interface Table Name ECE_PO_INTERFACE HEADERS 1000 1999 ECE_PO_INTERFACE_LINES 2000 2999 ECE_PO_INTERFACE SHIPMENTS 3000 3999 Although extension table data elements may be interwoven with data elements from the corresponding interface table provided the total number of bytes for a
580. umn for Key 1 Customer is CUSTOMER_NAME The source column for Key 2 Customer Site is CUSTOMER_SITE Access the Code Conversion Value Table Using Full Search Keys Search Code Directio Key 1 Key 2 Key Key Key Internal Order n Categor Custo Custo 3 4 5 Code y mer mer Site First SHIP_V OUT GAMM 9999 Over Search IA A Night Second SHIP_V BOTH GAMM Over Search IA A Night Third SHIP_V OUT Over Search IA Night Searching the Code Conversion Value Table The code conversion value table is read using the search keys shown above Three accesses to the code conversion value table may be attempted The order of the search and the constructed keys are shown in the table These keys will be used to search the following example of a code conversion values table Code Conversion 10 37 Example of Searching the Code Conversion Value Table Table Code Direction Key Key Key Internal External Entry Category Code 1 1 2 3 5 Code Customer Customer Site 1 SHIP_VI IN ALPHA 1006 Alpha Ai Alpha Ai A r r 2 SHIP_VI IN ALPHA 1099 Alpha Fa Alpha Ai A st r 3 SHIP_VI IN ALPHA Alpha Q Alpha Ai A uick r 4 SHIP _ VI IN BETA 1099 Beta Trav Beta Air A el 5 SHIP VI IN BETA 1100 Beta Fast Beta Air A er 6 SHIP VI IN BETA Beta Quic Beta Air A ker V SHIP VI IN Over AIR A Night 1 In the search key algorithm table the first search has the full key including the internal code Over Night Since there was no table entry for
581. und Ship Notice Manifest ASNI 856 DESADV Inbound Shipment and Billing Notice SBNI 857 NO EDIFA CTii a aia a e E taser daeadtes 6 105 Outbound Application Advice ADVO 824 APERAK ssssississrnsisrinrissinsrinrinrrssensee 6 121 Outbound Purchase Order POO 850 ORDERS ssssssssrrssssrrssssrrrsstirrrssttnnnstennnssrnnnne 6 121 Outbound Purchase Order Change POCO 860 ORDCHG ss nessssrssissrressrrnrrsrenenene 6 124 Oracle Rec ivableses siicetiicst pun ceilactties a e n a anaa eaten ae aratata 6 127 Outbound Invoice INO 810 INVOIC 0 c cece eter terete terete tee ee eae tae snaetaeteeeeaeas 6 128 Outbound Credit Memo Debit Memo CDMO 812 CREADV DEBADV csecees 6 131 Oracle Release Managements ccc ei ee ee nr er ener Ee e A ET N 6 133 Planning Material Release SPSI 830 DELFOR DELINS Shipping Schedule SSSI 862 DELJIT DELINS CALDEL KANBAN 0 0 eccesce ese eet estes tree teens te ten staat 6 135 Production Sequence Schedule PSQI 866 DELJIT SYNCRO SYNPAC cesses 6 159 Oracle Shipping Execution 00cccceceecce scene eens cess eee ceeeeaessaeeeaeesaesseesseessaesseessaesaes 6 174 Outbound Shipment Notice Manifest DSNO 856 DESADV c cesceeee enter renee 6 175 Oracle Supplier Scheduling 0 0 cece eee ee re ere eee eteeeseneesneeseeesenreeneeseneeeeeneee 6 177 Outbound Planning Schedule SPSO 830 DELFOR c cece terete eee eteeteeeee 6 178 Outbound Shipping Schedule SSSO 862 D
582. ur responsibility if you want to associate a different set of addresses for the same Trading Partner group and same Trading Partner then you have to reselect the operating unit in the Trading Partner Group form and then change the setup for the underlying Trading Partners The operating unit is relevant to the underlying addresses only and not to the Trading Partner groups or Trading Partner headers Access Control Security by Operating Units To have a secured way for users to access operating units Oracle e Commerce Gateway uses the security profile concept that allows system administrators to predefine the scope of access privileges as a security profile and then use the profile option MO Security Profile to associate the security profile with a responsibility Multiple operating units are associated with a security profile and the security profile is in turn associated with a responsibility Therefore through the access control of security profiles users can access data in multiple operating units without changing responsibility Security profiles are defined based on organization hierarchies For example a sales company consists of USA and UK operating units the USA operating unit has Western Region Sales and East Region Sales Sales managers are responsible for both USA and UK sales supervisors are responsible for either USA or UK and sales representatives are only responsible for their designated sales regions The Sales organization h
583. urchase Order Changes The following table shows the Common Key positions 1 100 for the Outbound Purchase Order Change transaction The table shows the position length code and content of the Common Key elements Transaction specific Data in the POCO Transaction Common Key Position Length Code Contents 1 25 25 TP_CD Trading Partner Code as defined in the EDI Translator 26 47 22 PO Purchase order number 48 69 22 ITEM Purchase order line number 70 91 22 SHIPMENT Shipment Number 92 95 4 varies Record Number 96 97 2 varies Record Layout 98 100 3 varies Record Layout Qualifier The following table shows the Common Key positions 1 100 for the records of the Outbound Purchase Order Change transaction Transaction Summary Layouts A 159 Transaction specific Data in the Common Key of the POCO Transaction Per Record Data Trading Ref 1 Ref 2 Ref 3 Partner PO ITEM SHIPM ENT Record Number Record Layout Record Layout Qualifie r 1 Control Record 2 Trading Partner Header Flexfiel ds 3 Trading Partner Header Flexfiel ds 4 Trading Partner Header Flexfiel ds 5 Trading Partner Header Flexfiel ds 6 Trading Partner Detail Flexfiel ds 7 Trading Partner Detail Flexfiel ds TP_CD PO TP_CD PO TP_CD PO TP_CD PO TP_CD PO TP_CD PO TP_CD PO 0010 0020 0030 0040 0050 0060 0070 CT Al A2 A3 A4 Al A2 CTL T
584. use the same Translator Code like the electronic mailbox that it is associated with depending on how the Trading Partners are defined in the base Oracle Application For instance one Trading Partner mailbox may be shared by a corporation s east coast and west coast offices though they may be defined as two Trading Partners customers or suppliers in the base Oracle Application In the example in the following table the Oracle Supplier is derived from the Supplier site associated with the EDI Location Code and Translator Code found on the Control Record 0010 Example of Shared Translator Codes on the Control Record 0010 Translator EDI Location Supplier Site Supplier Site Supplier Supplier ID Code from from from Oracle ID from from Oracle from Oracle e Commerce e Commerce Purchasing Oracle Purchasing Purchasing Gateway Gateway Purchasing A1 ACME 10 AC BOST Boston 64354345 ACME EAST 135678 9 6 Oracle e Commerce Gateway Implementation Manual Translator EDI Location Supplier Site Supplier Site Supplier Supplier ID Code from from from Oracle ID from from Oracle from Oracle e Commerce e Commerce Purchasing Oracle Purchasing Purchasing Gateway Gateway Purchasing A1 ACME 10 AC DEN Denver 12343221 ACME WEST 654322 Oracle e Commerce Gateway does not need to know how many real business entities are associated with a given Translator Code There may be one business entity or dozens associated with t
585. ustomer line number customer item and or supplier item 6 14 Oracle e Commerce Gateway Implementation Manual Data for INVENTORY_SEGMENT1 through INVENTORY_SEGMENT20 may be written on records 2010 and 2020 if needed The item level data on records 2000 2020 is associated with each set of 3000 4900 records below it They are combined to write an entry into the Order Import LINE table Case 2 and 3 SHIPMENT DETAIL The first set of shipment level data where price and configuration data is on record 3000 and dates are on record 4000 Case 4 and 5 SHIPMENT DETAIL The second set of shipment level data where price and configuration data is on record 3000 and dates are on record 4000 Case 6 and 7 SHIPMENT DETAIL The third set of shipment level data where price and configuration data is on record 3000 and dates are on record 4000 Case 8 ITEM DETAIL Details for the second line item starts IS THIS AN INCOMPLETE STATEMENT Case 9 and 12 SHIPMENT DETAIL Pairs of shipment level detail for the second line item Original System Reference Data in all Order Import Tables Order Import requires a set of Original System reference fields These are derived by the e Commerce Gateway transaction process if one is not found in the transaction The POI transaction program derives the header and line level Original System reference fields if data is not supplied in the transaction when the transaction was created The Original System re
586. ustomization The Oracle Applications and the Oracle e Commerce Gateway may change the layout or actual data contained in the transaction interface file because of an upgrade ora patch They may also change because of your customization to meet your own or a Trading Partner s requirements Predefined Record Layouts and Data Maps in the Translator Many Translator vendors provide pre defined data maps in standard EDI formats for the most common transactions such as purchase orders and invoices They may even provide pre defined base maps for particular large vendors however these maps will almost always need further definition for your particular situation Synchronize Record Layouts in the Oracle e Commerce Gateway and the Translator The Translator must know where to look for data to map to a given standard transaction and format They rely on the Record Number on each record in the transaction interface file to identify the data on that record given the transaction definitions in the Oracle e Commerce Gateway At the same time a Translator may have a preference for getting certain data elements earlier in the outbound transaction interface file so that it can use that data in multiple places In an inbound file it may be easier for the Translator to process the incoming data into a certain order Adjusting the layouts between the Oracle e Commerce Gateway and the Translator can optimize the processing for both Create Data Maps in the Tra
587. v ed Supplier List Flexfiel d15 Item Flexfiel ds 1 4 Item Flexfiel ds 5 9 Item Flexfiel ds 10 14 TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD SS SS SS SS SS SS SS ITEM ITEM ITEM ITEM ITEM ITEM ITEM 2100 2110 2120 2130 2150 2160 2170 A1 A2 A2 A2 A1 A2 A2 AS1 AS2 AS3 AS4 IT1 IT2 IT3 Transaction Summary Layouts A 253 Data Trading Partner Ref 1 SS Ref2 Ref3 ITEM SCHE DULE Record Number Record Layout Record Layout Qualifie r 49 50 51 52 53 54 Item Flexfiel d15 Ship to Organiz ation Flexfiel ds item 1 4 Ship to Organiz ation Flexfiel ds item 5 9 Ship to Organiz ation Flexfiel ds item 10 14 Ship to Organiz ation Flexfiel d item 15 Organiz ation Option Flexfiel ds 1 4 TP_CD TP_CD TP_CD TP_CD TP_CD TP_CD SS SS SS SS SS SS ITEM ITEM ITEM ITEM ITEM ITEM 2180 2200 2210 2220 2230 2250 A2 A1 A2 A2 A2 A1 IT4 DI1 DI2 DI3 DI4 SO1 A 254 Oracle e Commerce Gateway Implementation Manual Data Trading Partner Ref 1 SS Ref2 Ref3 ITEM SCHE DULE Record Number Record Record Layout Layout Qualifie r 55 56 57 58 59 60 61 Organiz ation Option Flexfiel ds 5 9 O
588. values are ASNI for the ship notices and SBNI shipment and billing notice TEST_INDICATOR This column represents the test or production indicator from the Trading Partner If this value does not match the test or production indicator associated with the trading partner defined in Oracle e Commerce Gateway a process rule exception is detected Then an exception message is displayed in the View Staged Documents window The valid values are T for test and P for production TP_TRANSLATOR_CODE TP_LOCATION_CODE EDI Location Code The two columns in combination uniquely identify a Trading Partner in Oracle e Commerce Gateway Once the trading partner definition is accessed Oracle e Commerce Gateway can verify whether the transaction is enabled for the Trading Partner If this trading partner is not defined in Oracle e Commerce Gateway a process rule exception is detected Then an exception message is displayed in the View Staged Documents window Refer to the Trading Partner chapter for details on how to properly define your trading partners and get a better understanding of how these fields are used in the process TRAN_PURPOSE_EXT1 This column represents the transaction purpose code The valid values are NEW or CANCEL The default value is NEW if no value is provided on the inbound flat file The value entered for TRAN _PURPOSE_EXT1 should be the same value entered for TRAN_PURPOSE_APPLICATION in record 1000 position 110 Applica
589. version on the product qualifier in standard transactions is necessary to associate them to the cross reference type as defined in Oracle Inventory X12 Product Qualifier Data Sample Cross Reference Table to which the search Element 235 Type in Oracle Inventory will be directed BP CUST Customer Item Cross Reference table EN EAN Inventory Item Cross Reference table IB ISBN Inventory Item Cross Reference table UP UPC Inventory Item Cross Reference table 6 52 Oracle e Commerce Gateway Implementation Manual X12 Product Qualifier Data Sample Cross Reference Table to which the search Element 235 Type in Oracle Inventory will be directed VP INT Customer Item Cross Reference table if the item is moved into CUSTOMER_ITEM_ NAME in the transaction VP not applicable if the Inventory Item table if the associated item is moved to item is moved into INVENTORY_ITEM INVENTORY_ITEM in the transaction CUSTOMER_ITEM_ID_TYPE can be set up for code conversion in the e Commerce Gateway so the standard code in position 80 can be converted to the valid Oracle code Alternately the EDI translator may place the valid Oracle Inventory defined code in position 70 Table Searches The first item to be used in a search is the customer item or generic item in the CUSTOMER_ITEM_NAME if the field is populated The customer s purchasing application may not be maintaining accurate supplier items if they rely on their own custom
590. vice transaction Refer to the Creating Electronic Payments with Oracle e Commerce Gateway section Oracle Payables User s Guide for details 1 Enter an EDI ID Number in the Banks window for your disbursement bank Refer to the Defining Banks section Oracle Payables User s Guide for details Define a payment document that uses the EDI Outbound Program as the payment format and assign this payment document to your disbursement bank account Refer to the Defining and Maintaining Payables Payment Documents section Oracle Payables User s Guide for details Enter bank data for each supplier site you want to pay Refer to the Defining Supplier Bank Accounts section Oracle Payables User s Guide for details Enter electronic payment data for each supplier site you want to pay Refer to the Electronic Data Interchange Region of the Suppliers and Supplier Site Windows section Oracle Payables User s Guide for details This is where you specify the following e EDI Location An identifier for the supplier that links to e Commerce Gateway trading partner e EDIID Number ID number used by Oracle Energy e Payment Method Indicates how the electronic payment will be made Payment Method values and their descriptions are listed in the table below Payment Method Description ACH Automatic Clearing House BACS Bankers Automatic Clearing System BOP Financial Institution Option CWT Clearing House Inter bank Payment System CHIPS Funds Wire T
591. voice TP_CD INVOIC 2000 Al IV1 Header E Flexfiel ds 1 4 Transaction Summary Layouts A 75 Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner Invoice Item blank Number Layout Layout Qualifie r 6 Invoice TP_CD INVOIC 2010 A2 IV2 Header E Flexfiel ds 5 9 7 Invoice TP_CD INVOIC 2020 A2 IV3 Header E Flexfiel ds 10 14 8 Invoice TP_CD INVOIC 2030 A2 IV4 Header E Flexfiel d15 9 Invoice TP_CD INVOIC 2100 Al HG1 Header E Global Flexfiel ds1 4 10 Invoice TP_CD INVOIC 2110 A2 HG2 Header E Global Flexfiel ds 5 9 11 Invoice TP_CD INVOIC 2120 A2 HG3 Header E Global Flexfiel ds 10 14 12 Invoice TP_CD INVOIC 2130 A2 HG4 Header E Global Flexfiel ds 15 19 A 76 Oracle e Commerce Gateway Implementation Manual Data Trading Ref 1 Ref 2 Ref 3 Record Record Record Partner Invoice Item blank Number Layout Layout Qualifie r 13 Invoice TP_CD INVOIC 2140 A2 HG5 Header E Global Flexfiel d 20 14 Extensio TP_CD INVOIC 2900 Custo n E m Tables Invoice Header 15 Basic TP_CD INVOIC ITEM 3000 IT IT1 Item E Data 16 Basic TP_CD INVOIC ITEM 3010 IT IT2 Item E Data descrip tion 17 Misc TP_CD INVOIC ITEM 3020 IT IT3 Descript E ion 18 Invoice TP_CD INVOIC ITEM 4000 Al IT1 Line E Flexfiel ds 1 4 19 Invoice TP_CD INVOIC ITEM 4010 A2 IT2 Line E Flexfiel ds 5 9 20 Invoice TP_CD INVOIC ITEM 4020 A2 IT3 Line E Flexfiel ds 10 14 Transaction Summary Layouts A 77 Data Trading Ref
592. way Required Fields 6 80 Oracle e Commerce Gateway Implementation Manual Oracle e Commerce Record Number Position Number Note Gateway Column Name for Required Fields TEST_INDICATOR 0010 20 T or P TP_DOCUMENT_ID 0010 30 ASNT or SBNI TP_TRANSLATOR_C_ 0010 70 Translator identifier ODE for this trading partner TP_LOCATION_CO 0010 80 The EDI Location DE Code INVOICE_NUM 1000 10 INVOICE_AMOUNT 1000 40 ITEM_LINE_TYPE_C 3000 10 ODE AMOUNT 3000 110 Control Record 0010 TEST_INDICATOR This column represents the test or production indicator from the Trading Partner If this value does not match the test or production indicator associated with the trading partner defined in Oracle e Commerce Gateway a process rule exception is detected Then an exception message is displayed in the View Staged Documents window The valid values are T for test and P for production TP_DOCUMENT_ID This column identifies the type of document being sent by the Trading Partner If this document type is not enabled for the trading partner defined in Oracle e Commerce Gateway a process rule exception is detected Then an exception message is displayed in the View Staged Documents window The valid value is INI for standard invoice TP_TRANSLATOR_CODE TP_LOCATION_CODE EDI Location Code The two columns in combination uniquely identify a Trading Partner in Oracle e Commerce Gateway Once the trading partner definition is access
593. way files may also be easily read or test files easily created using standard editors It should be noted however that because the file may extend to a width of 1024 characters the editor should be set to minimum margins with fixed non proportional width font to ensure properly formatted display without wrapped data Modify Transaction Interface File Oracle e Commerce Gateway creates outbound and receives inbound transaction interface files The transaction record layouts a k a file formats are pre defined by Oracle e Commerce Gateway and stored in a data repository The seeded transaction layout definitions may be used as is or customized to match the data you transmit to or receive from your trading partner You may want to change the seeded transaction layout definitions for the following reasons e Change file structure e Change record layout e Change column attributes e Delete unused data elements and records e Activate additional external fields for code conversion e Activate unmapped data elements e Extend Oracle e Commerce Gateway supported transactions Use the Transaction Layout Definition Report to review the seeded definitions including any modifications you may have entered Use the Interface File Definitions window to make any necessary definition changes Since the transaction layout definitions are stored in a data repository all changes entered using the Interface File Definition window are effective at run time wi
594. where the combined Translator Code and EDI Location Code are assigned in two organizations Solution The problem is due to missing or incorrect EDI Location Code in the Oracle Applications or the Translator Code in the Oracle e Commerce Gateway in the Define Trading Partner window Assignment tab Resolve the address site and trading partner set ups then the user should resubmit the document from the View Staged Documents window Troubleshooting 8 5 Message Description and Solution Field column_name with value value does not match the defined datatype datatype The file file_name is empty for transaction transaction_type Description This message appears in the View Staged Documents window and is a result of an import process exception The data that is assigned to the noted column_ name does not match the datatype definition For example the datatype definition may be numeric and the data contained within column_name contains alphabetic characters or the datatype definition may be date and the data contained within column_name is not in the proper date format Solution Check the data map to determine if the transaction data is positioned correctly in the transaction interface file for the given transaction If the problem exists in the incoming transaction then the associated records with this document should be deleted from the View Staged Documents window If the Trading Partner is sending invalid data
595. x transaction because it is disabled Description This message appears in the View Staged Documents window and is a result of an import process exception The combination of Translator Code EDI Location Code map and transaction type are not defined in the Oracle Applications Solution Set up the Translator Code in the Oracle Application and the EDI Location Code in the Oracle e Commerce Gateway for the correct Trading Partner Enable the document and document type in the Define Trading Partner window Details tab Obtain the full address for the given EDI Location Code from the Trading Partner if it is necessary to define the site and the EDI Location Code in Oracle Applications After all set ups are complete the user should resubmit the document from the View Staged Documents window If the problem exists in the incoming transaction then the associated records with this document should be deleted from the View Staged Documents window and the Trading Partner needs to be notified that there was a problem with the transaction if necessary The Trading Partner needs to be informed that this data needs to be corrected by them and the appropriate documents retransmitted Description This message appears in the concurrent manager log file The transaction that is being imported is disabled in the Profile Options window Solution If appropriate activate the transaction in the Profile Options window and resubmit the docume
596. xfields Flexfields 19 Destination LINE 3000 Address 20 Destination LINE 3020 Location Inbound Shipment and Billing Notice Common Key The following table shows the Common Key positions 1 100 for the Inbound Shipment and Billing Notice transaction The table shows the position code length and content of the Common Key elements Transaction specific data in the SBNI transaction Common Key Position Length Code Content 1 25 25 TP_CD Trading Partner Code as defined in the EDI Translator 26 47 22 SHIPMENT Shipment Number 48 69 22 LINE Item Number Transaction Summary Layouts A 81 Position Length Code Content 70 91 22 blank N A 92 95 4 varies Record Number 96 97 2 varies Record Layout 98 100 3 varies Record Layout Qualifier The following table shows the Common Key positions 1 100 for the records of the Inbound Shipment and Billing Notice transaction Transaction specific data in the Common Key per record of the SBNI transaction Record TP_CD Ref1 Ref 2 Ref 3 Record Record Record Shipm Line blank Number Layout Layout ent Qualifie r 1 Control TP_CD SHIPM 0010 CT CTL Record ENT 2 Shipme TP_CD SHIPM 1000 L1 DL1 nt ENT Notice Basic Header 3 Carrier TP_CD SHIPM 1010 L2 DL2 Weights ENT Packagi ng 4 Shipme TP_CD SHIPM 1020 L3 DL3 nt ENT Method of Paymen t A 82 Oracle e Commerce Gateway Implementation Manual Record TP_CD Ref 1 Ref 2 Ref 3 Record Record Reco
597. xternal 3 and 4 may both have EDIFACT codes since each standard has multiple codes meaning each to the Oracle application Again you will rely on the EDI translator data map to choose the correct external field for the transaction Entry items 3 4 If a document standard is entered for the Trading Partner in the Trading Partner Detail tab and the a data element is assigned the column DOCUMENT_STANDARD in the Code Conversion Assignment tab these table entries will be accessed in the code conversion process before the global entries 1 are accessed Planning for Direction IN for Inbound Transactions The following table shows an example in which all entries are feasible for the direction Code Conversion 10 19 in The column Internal Code is retrieved for the Application Open Interface tables the rest of the columns represent the search key For the direction in the external code is part of the entire search key The search key must be unique Example of Planning for Direction IN for Inbound Transactions Item Category Direction Key 1 Key 2 External External Internal Code 1 Code 2 Code 1 UOM IN EA Each 1 UOM IN PC Each 2 UOM IN EDIFACT EA Each 2 UOM IN EDIFACT PC Each 2 UOM IN X12 EA Each 2 UOM IN X12 PC Each In the example above external codes are part of the entire search key For direction IN all the entries in the table are feasible even without the document standard because the entir
598. y be one of the following e In the detail of the transaction e Derived Trading Partner data from the Trading Partner site on transaction s Control Record 0010 or e Data found on the transaction s Control Record 0010 Control Record Data as Search Keys For inbound transactions the Trading Partner reference 1 and reference 2 data does not have to match the Trading Partner reference 1 and reference 2 data defined in the Code Conversion 10 5 Trading Partner window You could move data from the electronic envelope or any data you choose into Trading Partner reference 1 or reference 2 so they can be used as search keys during code conversion if you desire Use the Assign Categories window to assign the Trading Partner reference 1 or reference 2 column to be search keys like any other column assignment if you choose to use these fields Code Conversion Values Window The Code Conversion Values window is where the actual internal codes and 1 5 external codes to be converted are entered plus any search keys that apply to the entries e Internal codes are the codes defined or recognized in the base Oracle application e External codes are the codes defined or recognized by external sources such as your Trading Partners or transaction standards When Not to Use Keys 1 5 If the internal and external code entries apply universally to all Trading Partners the codes in the code conversion tables do not have keys 1 5 for the entry
599. y including 100 Record Number 2 Any Flexfield Context 30 3 Any Flexfield 1 100 4 Any Flexfield 2 100 5 Any Flexfield 3 100 Descriptive Flexfields A4 Record Layout The following table shows the record layout for the record layout code A4 Descriptive Flexfields Record Layout Code A4 Seq Control Level Flexfields Length 1 Common key including 100 Record Number 2 Any Flexfield 1 100 3 Any Flexfield 2 100 4 Any Flexfield 3 100 5 Any Flexfield 4 100 Descriptive Flexfields A5 Record Layout The following table shows the record layout for the record layout code A5 Descriptive Flexfields Transaction Interface File Architecture 5 23 Record Layout Code A5 Seq Control Level Flexfields Length 1 Common Key including 100 Record Number 2 Shipment Allowance Charge 30 Flexfield Context 3 Shipment Allowance Charge 70 Flexfield 1 Internal 4 Shipment Allowance Charge 25 Flexfield 1 External AC Special Services_code 5 Shipment Allowance Charge 70 Flexfield 2 Internal 6 Shipment Allowance Charge 25 Flexfield 2 External AC_Special_Charges_code 7 Shipment Allowance Charge 70 Flexfield 3 Internal AETC_number 8 Shipment Allowance Charge 25 Flexfield 3 External 9 Shipment Allowance Charge 70 Flexfield 4 Internal AETC_Responsibility_Code 10 Shipment Allowance Charge 25 Flexfield 4 External Descriptive Flexfields A6 Record Layout The following table shows the record layou
600. y process each organization separately or all organizations at the same time Review the documentation on Application Open Interfaces for each Oracle product for their specific processing rules Trading Partner Windows The Trading Partner windows are discussed below Read the preceding section on Trading Partner detail Trading Partner 9 23 Refer to the Oracle e Commerce Gateway User s Guide and Set Up Trading Partners for detail on using these windows Define Trading Partner Group and Trading Partner A Trading Partner Group is a code that is assigned to a set of Trading Partners to allow them to appear in the Trading Partner list together A Trading Partner Group may be a supplier or customer name or any entity that you choose Since Trading Partner Groups can be associated with operating units linked to your responsibility to support a multiple organization environment once an operating unit is associated with a Trading Partner Group all Trading Partners within the group are all assigned to the same operating unit When an operating unit is added to a Trading Partner Group the associated organization ID is also added to the group Trading Partner Naming Convention Using a naming convention for your Trading Partners is recommended for easy recognition The three components in the following table are recommended The combination of codes must be unique Note that a delimiter between fields improves readability A naming conven
601. yout Qualifier LT4 Inbound Purchase Order Change POCI 860 ORDCHG POCI 860 ORDCHG A single transaction has the data hierarchy and data looping as presented in the following diagram and table A 32 Oracle e Commerce Gateway Implementation Manual POCI Inbound Purchase Order Change Structure Record Numbers Control Record 0010 Purchase Order Header 1000 1699 Credits fat OM HEADER Level 1700 1740 Price Adjustments at OM HEADER Level 1800 1850 Reservations at OM HEADER Level 1900 1910 Actions at OM HEADER Level 1950 1990 Item OM LINE Level 2000 2900 Part Numbers here Shipment OM LINE Level 3000 4900 Shipment Detail in this range Credits at OM LINE Level 5000 5900 Price Adjustments fat OM LINE Level 6000 6900 Reservations at OM LINE Level 7000 7900 Actions at OM LINE Level 8000 8900 Lot Serial at OM LINE Level 9000 9900 Shipment OM LINE Level 3000 4900 Credits at OM LINE Level 5000 5900 Price Adjustments at OM LINE Level 6000 6900 Reservations at OM LINE Level 7000 7900 Actions at OM LINE Level 8000 8900 Lot Serial at OM LINE Level 9000 9900 Note The customer and supplier item data in records 2000 2900 will be repeated on each shipment level data in records 3000 4900 to create entries inthe Order Import LINE table The following table shows the content and occurrences of the records comprising th

Oracle® e-Commerce Gateway

Contents

Download Pdf Manuals

Related Search

Related Contents

Oracle&reg; e-Commerce Gateway

Contents

Download Pdf Manuals

Related Search

Related Contents

Oracle® e-Commerce Gateway