Oracle e-Commerce Gateway User’s Guide Release 11i.2 August, 2000 Part No.
Oracle e-Commerce Gateway User’s Guide, Release 11i.2 (as a variable) for Platform (as a variable) Part No. A75089-02 Copyright © 1996, 1999, Oracle Corporation. All rights reserved.
Contents Send Us Your Comments .................................................................................................................. vii Preface............................................................................................................................................................ ix 1 Overview .................................................................................................................................1 - 1 Oracle e-Commerce Gateway Overview .............
Assigning Column Rules ............................................................................................................... 5 - 7 6 Inbound Exception Processing ..................................................................................... 6 - 1 Inbound Exception Processing ....................................................................................................... Viewing Staged Documents .........................................................................................
Viewing the Status of Concurrent Programs............................................................................... 9 - 7 A Windows and Navigator Paths Windows and Navigator Paths....................................................................................................... A - 2 B Seed Data Reconciliation Seed Data Reconciliation ................................................................................................................ B - 2 Performing Seed Data Reconciliation .........
vi Oracle e-Commerce Gateway User’s Guide
Send Us Your Comments Oracle e-Commerce Gateway User’s Guide, Release 11i Part No. A75089-01 Oracle Corporation welcomes your comments and suggestions on the quality and usefulness of this publication. Your input is an important part of the information used for revision.
Oracle Corporation welcomes your comments and suggestions on the quality and usefulness of this publication. Your input is an important part of the information used for revision.
Preface Welcome to the Oracle® e-Commerce Gateway User’s Guide, Release 11i. This user’s guide includes the information you need to work with Oracle e-Commerce Gateway effectively. It contains detailed information about the following: ■ Oracle e-Commerce Gateway setup. ■ Oracle e-Commerce Gateway windows. ■ Oracle e-Commerce Gateway reports and processes. This preface explains how this user’s guide is organized and introduces other sources of information that can help you.
About This User’s Guide This guide contains overviews as well as task and reference information about Oracle e-Commerce Gateway. Note: For Release 11i, we created the Oracle e-Commerce Gateway Implementation Manual. Most of the information contained in previous releases of the Oracle EDI Gateway User’s Guide has been moved to the implementation manual. For detailed information, see the Oracle e-Commerce Gateway Implementation Manual.
Do Not Use Database Tools to Modify Oracle Applications Data Because Oracle Applications tables are interrelated, any change you make using Oracle Applications 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.
Related User’s Guides Oracle e-Commerce Gateway shares business and setup information with other Oracle Applications products. Therefore, you may want to refer to other user’s guides when you set up and use e-Commerce Gateway. If you do not have the hardcopy versions of these manuals, you can read them online using the Applications Library icon or Help menu command.
Oracle Inventory User’s Guide This guide describes how to define items and item information, perform receiving and inventory transactions, maintain cost control, plan items, perform cycle counting and physical inventories, and set up Oracle Inventory. Oracle Master Scheduling/MRP and Supply Chain Planning User’s Guide This guide describes how to anticipate and manage both supply and demand for your items.
Oracle Receivables User’s Guide Use this manual to learn how to implement flexible address formats for different countries. You can use flexible address formats in the suppliers, banks, invoices, and payments windows. Reference Manuals Oracle Technical Reference Manuals Each technical reference manual contains database diagrams and a detailed description of database tables, forms, reports, and programs for a specific Oracle Applications product.
Multiple Organizations in Oracle Applications If you use the Oracle Applications Multiple Organization Support feature to use multiple sets of books for one e-Commerce Gateway installation, this guide describes all you need to know about setting up and using e-Commerce Gateway with this feature. Oracle Applications Implementation Wizard User’s Guide If you are implementing more than one Oracle product, you can use the Oracle Applications Implementation Wizard to coordinate your setup activities.
Other Sources Training We offer a complete set of formal training courses to help you and your staff master e-Commerce Gateway and reach full productivity quickly. We organize these courses 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.
another EDI expert to the email distribution list, send your email address to edisig@us.oracle.com. Please include the full name and the Oracle customer number. (This email address is not intended for questions that should be directed to Oracle Support Services.
xviii
1 Overview This chapter provides a general overview of Oracle e-Commerce Gateway, including: ■ Oracle e-Commerce Gateway Overview on page 1-2. ■ How Oracle e-Commerce Gateway Works on page 1-3. ■ EDI Transaction Support on page 1-5. For a detailed overview, see: Overview, Oracle e-Commerce Gateway Implementation Manual.
Oracle e-Commerce Gateway Overview Oracle e-Commerce Gateway Overview Oracle Applications provides users with the ability to conduct business electronically between trading partners based on Electronic Commerce standards and methodology. One form of Electronic Commerce is Electronic Data Interchange (EDI). EDI is an electronic exchange of data between trading partners. Interface data files are exchanged in a standard format to minimize manual effort, speed data processing, and ensure accuracy.
How Oracle e-Commerce Gateway Works How Oracle e-Commerce Gateway Works Oracle e-Commerce Gateway is designed with an open and flexible architecture for easy integration with trading partners and / or EDI translators. The e-Commerce Gateway provides a seamless application to application integration solution. When used for EDI (Electronic Data Interchange) solutions, e-Commerce Gateway integrates with EDI translators to provide specific EDI standard formats and versions.
How Oracle e-Commerce Gateway Works rules remain in the exception module where users can analyze the exceptions. After corrective action in other modules or in the e-Commerce Gateway, the transaction may be resubmitted for re-validation. Alternatively, if your trading partner will re-send the transaction, you may delete the transaction from the exception module. The base Oracle application continues validating transactions written to the application’s open interface tables.
EDI Transaction Support EDI Transaction Support The following transactions are supported: Table 1–1 EDI Transaction Support ASC X12 EDIFACT Transaction Code Description Inbound Transactions 810 INVOIC INI Inbound Invoice. This includes support for the following transactions: Air Freight Details and Invoice (110), Motor Carrier Freight Details and Invoice (210), Rail Carrier Freight Details and Invoice (410), and Grocery Product Invoice (880).
EDI Transaction Support Other Transactions The following transactions are available through other products, specifically, Oracle Process Manufacturing, Oracle Order Management, and Oracle Release Management.
2 Setting Up This chapter explains the Oracle e-Commerce Gateway profile options and how to set them up: ■ Setting Up Oracle e-Commerce Gateway on page 2-2. ■ Oracle e-Commerce Gateway Profile Options on page 2-4. ■ Setting Profile Options on page 2-8.
Setting Up Oracle e-Commerce Gateway Setting Up Oracle e-Commerce Gateway This section briefly describes Oracle e-Commerce Gateway setup steps. For the complete discussion, refer to Setting Up, Oracle e-Commerce Gateway Implementation Manual. Note: Oracle e-Commerce Gateway relies on several base Oracle Applications. Please refer to the setup and open interfaces documentation for those products, specifically the appropriate Oracle Applications Implementation Wizard.
Setting Up Oracle e-Commerce Gateway 1. Define code conversion categories to specify a subset of codes within the code conversion table. See: Defining Code Conversion Categories on page 4-8. 2. For each data element in a transaction that requires code conversion by e-Commerce Gateway, assign one code conversion category. See: Assigning Categories on page 4-10. 3. Enter the actual code conversion values from the internal codes to external codes into the code conversion table.
Oracle e-Commerce Gateway Profile Options Oracle e-Commerce Gateway Profile Options There are three system level profile options you must set. These affect all e-Commerce Gateway transactions: ■ Outbound directory. ■ Inbound directory. ■ Allow Split Words in Attachment. There are other transaction level profile options. ■ Enable / disable each transaction. ■ Address derivation precedence. ■ Attachment segment size. ■ Enabling header-level attachments. ■ Enabling line-level attachments.
Oracle e-Commerce Gateway Profile Options ECE_OUT_FILE_PATH (ECE: Output File Path) Indicate the directory where outbound interface data files are written. This value must match the actual directory on disk and that designated in the INIT.ORA file. Note: For the e-Commerce Gateway, you must create inbound and outbound directories on your server, and then specify them in the INIT.ORA file and in the “ECE: Inbound directory” and “ECE: Outbound file path” profile options, respectively.
Oracle e-Commerce Gateway Profile Options When inbound EDI transactions are imported into Oracle Applications, the unique business site address must be established before the transaction can be processed. Each trading partner must have a unique address. A trading partner is a site, such as a plant, a warehouse, a bank branch, or some other business unit. A trading partner is not necessarily a company; one company can have several sites.
Oracle e-Commerce Gateway Profile Options ECE__HEAD_ATT Enables the header attachment for the transaction. The default is Yes. ECE__LINE_ATT Enables the line attachment for the transaction. The default is Yes. ECE__MITEM_ATT Enables the master item attachment for the transaction. The default is Yes. ECE__IITEM_ATT Enables the inventory item attachment for the transaction. The default is Yes.
Setting Profile Options Setting Profile Options ◗◗ To set system-level profile options: 2-8 1. Navigate to the Transaction Profiles window. 2. Enter the outbound directory where your outbound interface data files will be stored. For example, /sqlcom/outbound. 3. Enter the inbound directory where your inbound interface data files will be stored. For example, /sqlcom/inbound. 4. Indicate whether to allow words to be split when the segment size is reached.
Setting Profile Options ◗◗ To set profile options by transaction: 1. Navigate to the Transaction Profiles window. 2. Select the transaction for which you want to set profile options. See: EDI Transaction Support, Oracle e-Commerce Gateway Implementation Manual, Release 11i. 3. Indicate whether the transaction should be enabled or disabled. 4. For inbound transactions only, select the address precedence code. Refer to the profile option description for the meaning of each address precedence codes.
Setting Profile Options 7. ■ Enable or disable the header attachment. ■ Enable or disable the line attachment. ■ Enable or disable the Inventory item attachment. ■ Enable or disable the master item attachment. ■ Enable or disable the shipment attachment. Repeat these steps above for each transaction you use.
3 Trading Partners This chapter discusses how to set up trading partners: ■ Trading Partners on page 3-2. ■ Defining Trading Partner Data on page 3-4.
Trading Partners Trading Partners In the Oracle e-Commerce Gateway, the term ”trading partner” refers to a particular location or address of a customer, supplier, or bank engaged in some type of trading relationship (sending or receiving transactions). Since a given corporation may have several locations, each with a different set of trading relationships, you must define one trading partner for each customer address, supplier site, or bank branch.
Trading Partners The relationship between Oracle e-Commerce Gateway trading partners and trading partner data on the inbound or outbound interface file is found in the Control Record (0010) section of the interface file. During outbound processing, trading partner data from the e-Commerce Gateway definition is placed on the Control Record to identify the sending trading partner.
Defining Trading Partner Data Control Record (0010) section of the interface file. Location code is also included with all address data referenced in the document. Defining Trading Partner Data The term ”trading partner” is used differently in the context of EDI translators than in the context of the e-Commerce Gateway. For EDI translators, the purpose of trading partner data is to: ■ Identify sending and receiving electronic mailbox addresses.
Defining Trading Partner Data 3. Optionally, enter a description for the trading partner group. 4. Do one of the following: ■ ■ To add a new trading partner to a trading partner group, choose the New button to open the Trading Partners window. To update an existing trading partner in a trading partner group, enter the trading partner location code. Then choose the Open button to open the Trading Partners window. ◗◗ To define a trading partner within a trading partner group: 1.
Defining Trading Partner Data 4. Optionally, access trading partner flexfields (also known as attributes) by choosing the flexfield represented by [ ]. In order to be used, flexfields must first be defined using System Administration. ◗◗ To define a trading partner assignment: 1. In the Assignment tabbed region, associate this trading partner definition with the corresponding Oracle Applications physical address entity. This is addressor site-level data. 2.
Defining Trading Partner Data ◗◗ To define trading partner contact data: ■ Optionally, open the Contact tabbed region and enter the EDI contact name, title, basic address data, electronic mail address, phone, fax number, and so on. This data is useful for EDI coordinators in case issues arise regarding transmission of EDI files. This data is not written to the interface data files. The data is independent of all contact data in the Oracle Applications.
Defining Trading Partner Data 3-8 Oracle e-Commerce Gateway User’s Guide
4 Code Conversion This chapter describes the code conversion function of Oracle e-Commerce Gateway: ■ Code Conversion on page 4-2. ■ Defining Code Conversion Categories on page 4-8. ■ Assigning Categories on page 4-10. ■ Predefined Code Categories on page 4-11. ■ Defining Code Conversion Values on page 4-15.
Code Conversion Code Conversion The Oracle e-Commerce Gateway Code Conversion Module is a flexible and extremely powerful feature used to reconcile (convert) values from your trading partner’s application or industry standard to values stored within Oracle Applications. Code conversion is a common problem in any integration scenario where coded values such as Unit of Measure Code or Currency Code are represented differently in each of the applications being integrated.
Code Conversion predefined categories are included in Oracle e-Commerce Gateway. You may choose to implement these predefined categories or define your own. See Defining Code Conversion Categories section for additional details. Define Code Conversion Values is where simple, or advanced code conversion rules along with their corresponding internal/external values are defined. Internal values are defined as code values stored in Oracle Applications.
Code Conversion Use of Keys in Code Conversion In many situations, one set of code conversion rules will not apply to all of your trading partners. Code conversion rules may apply to specific trading partners, specific industry standards, or any number of key attributes defined in Oracle Applications. These rules may be complex and involve a hierarchy of key attributes. For example, trading partner and trading partner location may be defined as two key attributes.
Code Conversion The use of keys can also be combined with direction-specific code conversion rules to provide maximum flexibility and configuration of your unique code conversion requirements. See Code Conversion Based on Direction section for additional information on direction-specific code conversion. Code Conversion Processing The Oracle e-Commerce Gateway Code Conversion Module is designed to process very basic or very complex code conversion rules.
Code Conversion ■ External Values (1-5) from the interface file. All of these values are used to find a record in the Code Conversion Values table that matches the above values. If found, convert External Values (1-5) to Internal Value based on this record definition. If no match is found, continue processing key values (if keys are used).
Code Conversion If no match is found, default Internal Value into the External Value 1 field. Processing Keys (1-5) In Oracle e-Commerce Gateway, keys are used to construct a logical hierarchy of key attributes. Code conversion processing derives key values based on data entered in the Assign Code Conversion Category form.
Defining Code Conversion Categories During outbound code conversion processing, any Code Conversion Values record that contains multiple External Values will convert all External Values and write them to the interface file (if the Code Conversion Values record matches all other criteria). During inbound code conversion processing, all External Values plus other matching criteria must be contained in the Code Conversion Values record in order for that record to qualify for code conversion.
Defining Code Conversion Categories ◗◗ To define additional code conversion categories: 1. Navigate to the Code Conversion Categories window. 2. Enter the category code and description. 3. To assign code conversion values to key attributes (such as a trading partner), enable one or more search keys. For example, if you want to set the first search key to ”X12,” you must enable Search Key 1. The actual search criteria are entered in the Assign Categories window.
Assigning Categories Assigning Categories For a given transaction, use the Assign Categories window to activate code conversion for a transaction data field. If search keys are enabled when you defined code conversion categories, use this window to identify the data elements associated with each key. Prerequisites ❏ Define code conversion categories. See: Defining Code Conversion Categories on page 4-8. ◗◗ To assign code conversion categories: 1. Navigate to the Assign Categories window. 2.
Predefined Code Categories 5. Assign a code conversion category to activate code conversion for the view or application open interface column. If no code category is assigned, code conversion is not performed. See: Predefined Code Categories on page 4-11. 6. Specify a column (Key 1 through Key 5) to define each key. This is used during code conversion processing to derive key values.
Predefined Code Categories Table 4–1 Predefined Code Categories 4-12 Category Codes BUYER_PRODUCT Buyer Product CARRIER Freight Carrier COMPANY_CODE Company CONTAINER_CODE Container CONTAINER_TYPE Container Type CONTAINER_TYPE_CODE Container Type COUNTRY Country CURR_CONV_TYPE Currency Conversion Type CURRENCY Currency CUSTOMER_CODE Customer DOCUMENT_TYPE Document Type EQUIPMENT Equipment FOB FOB FOB_PAYMENT FOB Payment FREIGHT_TERMS Freight Terms HAZ_CLASS Hazardous Clas
Predefined Code Categories Table 4–1 Predefined Code Categories Category Codes REGION2 Region 2 (for state in certain address tables) REGION3 Region 3 SHIP_ORDER_STAT Shipment Order Status SHIP_PRIOR Shipment Priority SHIP_TO_LOCATION Ship To Location SHIP_TO_ORG Ship To Organization SHIP_TO_SITE Ship To Site SHIP_VIA Ship Via (carrier) SS_DESCRIPTOR Supplier Scheduling Descriptor STATE State SUPPLIER_NUMBER Supplier Number SUPPLIER_SITE Supplier Site TAX_CODE Tax Code TAX_EX T
Predefined Code Categories See Also 4-14 ■ Code Conversion on page 4-2. ■ Defining Code Conversion Categories on page 4-8. ■ Assigning Categories on page 4-10. ■ Defining Code Conversion Values on page 4-15.
Defining Code Conversion Values Defining Code Conversion Values Depending upon the EDI standard, user requirements, and the application data, a single Oracle Application internal data element may require one to five external data elements for the interface data file to satisfy the data requirements for the EDI standard or the trading partner. Prerequisites ❏ Define code conversion categories. See: Defining Code Conversion Categories on page 4-8. ❏ Assign Code Conversion Categories.
Defining Code Conversion Values The following validation is performed on your entries: ■ ■ ■ 4. External values must be unique among IN and BOTH directions for the same search keys. Internal values must be unique within OUT and BOTH directions for the same search keys. The internal value and external values must be unique for all directions for the same search keys. Enter search key values (1 - 5) for the set of internal / external values.
5 Interface Data File This chapter discusses how to modify the interface data file and add process or column rules: ■ Changing the Interface Data File Record Layout on page 5-2. ■ Assigning Process Rules on page 5-5. ■ Assigning Column Rules on page 5-7.
Changing the Interface Data File Record Layout Changing the Interface Data File Record Layout Both inbound and outbound interface data file formats are predefined by Oracle e-Commerce Gateway The interface data file format may be used as defined or customized to match your specific business requirements. Some of the reasons to modify the predefined interface data file format include: ■ Exclude unused columns and unused records. ■ Change column size.
Changing the Interface Data File Record Layout ◗◗ To change the interface data file: 1. Navigate to the Interface File Definition window. 2. Select the transaction type. See: EDI Transaction Support on page 1-5. 3. Select the transaction data level. This identifies the level of data within the transaction defined in the e-Commerce Gateway for outbound transactions, and in the application open interface tables for inbound transactions.
Changing the Interface Data File Record Layout record number indicates the relative position of a group on that record in the file. No record can exceed 600 bytes. Attention: To activate data elements, you must define the record number, record position number, and the width of the data element. 5. Change the record position number. You can change the position number to another number within the record or enter blanks to exclude the column from the interface data file.
Assigning Process Rules Only the record layout code and record layout qualifier from the lowest numbered record position is used in the interface data file. 9. Change the record layout qualifier. This identifies the type of data in the record. For example, a generic record layout code for addresses may have a record layout qualifier that identifies the address as a ship-to, bill-to, or remit-to address type. You may modify the predefined value.
Assigning Process Rules The Assign Process Rules window shows the current transaction and all associated process rules. These fields are read-only. For each of the process rule (Invalid Document Address, Invalid Trading Partner, and Test Production Discrepancy), select the appropriate action.
Assigning Column Rules See Also Inbound Exception Processing on page 6-2 Changing the Interface Data File Record Layout on page 5-2 Assigning Column Rules on page 5-7 Assigning Column Rules Use the Assign Column Rules window to assign one to six data validation rules to any data element. You can assign multiple column rules to any column. You can also assign the same column rule type multiple times. In a few transactions, required data fields may have been seeded with the required data element rule.
Assigning Column Rules Table 5–2 Column Rules and Additional Parameters Column Rule Description Additional Parameters Needed Null Dependency Checks if the incoming data for a given column has a null or not null dependency based on the following conditions. Check boxes for Must be Null or Cannot be Null for the data in the column to be reviewed. More than one set of condition parameters can be entered at the same time. Then enter the Column Name, the Dependency, and Value for the condition.
Assigning Column Rules Table 5–2 Column Rules and Additional Parameters Column Rule Description Additional Parameters Needed Valueset Lookup Compares the value in the assigned column to an Oracle Applications Valueset. You must select a valueset from the List of Values. Select a standard Oracle valueset from a list of values. Value is Required Checks if the incoming None required. data for a given column has a non null value. If it is null, the rule is violated.
Assigning Column Rules 5-10 Oracle e-Commerce Gateway User’s Guide
6 Inbound Exception Processing This chapter discusses how failed inbound transactions are processed and viewed, including the following topics: ■ Inbound Exception Processing on page 6-2. ■ Viewing Staged Documents on page 6-3. ■ Viewing Process Violations on page 6-7. ■ Viewing Column Violations on page 6-8.
Inbound Exception Processing Inbound Exception Processing Inbound staged documents are either those that have been imported into the e-Commerce Gateway tables but not yet validated or transactions that have been validated but contain exceptions. Two type of data rule exceptions can be found during data validation, processing rules and column rules. After running the inbound transaction process or resubmitting transactions for re-validation, you can see exceptions in the View Staged Document window.
Viewing Staged Documents Log Only: Places a message in the log file, treats the document as successful, and continues processing. Skip Document: Skip current document and processes the next.
Viewing Staged Documents The Status tab displays a hierarchical tree of each failed transaction: Action Description Aborted The request was aborted based on rules. Application Insert Failed A failure occurred while inserting the document into the open interface tables. Reprocessing This document (and the group to which it belongs) was resubmitted and is either being validated or is waiting to be validated. Skipped Documents The documents were skipped based on rules.
Viewing Staged Documents Summary information is dynamic. When you select nodes in your tree, summary information for the node changes as well. Prerequisites ❏ (Optional.) Set up column rules and actions for data elements in each transaction using the Interface File Definition window. The e-Commerce Gateway may have seeded rules and actions for the validation of some column rules. See: Changing the Interface Data File Record Layout on page 6-2. ◗◗ To view staged documents: 1.
Viewing Staged Documents View Staged Documents window, Transaction Tab: 2. Select the view, All or Errors Only. 3. Select either the Status tab or the Transaction tab. These two tabs represent different ways that you can find the transactions. 4. Use the left side of the window to select the tree node (or line) you want to review for rule violations. 5. Choose Process Violations or Column Violations to drill down on the details. 6.
Viewing Process Violations 7. Choose Resubmit. 8. If you want to delete the document, choose Delete. Deletion occurs for all transactions from the cursor position downward. See Also Inbound Exception Processing on page 6-2 Viewing Process Violations on page 6-7 Viewing Column Violations on page 6-8 Viewing Process Violations The Process Violations windows displays all process rule violations. You then use this data to correct the problems, or you can choose to ignore the violations.
Viewing Column Violations 3. When finished, choose Done. The Process Violations window closes. If you made any changes, you are prompted to save them later. See Also Inbound Exception Processing on page 6-2 Viewing Staged Documents on page 6-3 Viewing Column Violations on page 6-8 Viewing Column Violations The Column Violations windows displays all column rule violations. You then use this data to correct the problems, or you can choose to ignore the violations.
Viewing Column Violations 4. When finished, choose Done. The window closes.
Viewing Column Violations 6-10 Oracle e-Commerce Gateway User’s Guide
7 Inbound Transactions This chapter describes how to run the Oracle e-Commerce Gateway inbound transactions: ■ Running the Invoice Inbound (INI) Program on page 7-2. ■ Running the Price / Sales Catalog Inbound (CATI) Program on page 7-4. ■ ■ ■ ■ ■ ■ Running the Response to Request for Quote Inbound (RRQI) Program on page 7-6. Running the Ship Notice / Manifest Inbound (ASNI) Program on page 7-9. Running the Shipping and Billing Notice Inbound (SBNI) Program on page 7-11.
Running the Invoice Inbound (INI) Program Running the Invoice Inbound (INI) Program Use this transaction to import supplier invoices into your Oracle Payables system for manual or electronic payment. Using the Payables Open Interface, you can accomplish high-volume invoice import complete with all standard online invoice entry features, including purchase order matching, invoice approval, and invoice batch processing.
Running the Invoice Inbound (INI) Program Select Yes to initiate the Payables Open Interface Import program using the default parameter values. Enter No if you do not want to initiate the Payables Open Interface. 7. Enter the following parameters: Payables: Batch Name: If you are using batch control, enter a name to be assigned to the batch of invoices to be imported.
Running the Price / Sales Catalog Inbound (CATI) Program Submitting a Request, Oracle Applications User’s Guide Viewing the Status of Concurrent Programs on page 9-7 Running the Price / Sales Catalog Inbound (CATI) Program Use this transaction to import supplier catalogs into your Purchasing system as Catalog Quotes. This supports catalog lookup and purchase order placement.
Running the Price / Sales Catalog Inbound (CATI) Program 4. Open the Parameters window. 5. Enter the inbound data file name or accept the default. 6. In the Execute Open Interface field, ■ ■ 7. Enter Y to initiate the Purchasing Document Open Interface program using the default parameter values. Enter N if you do not want to initiate Purchasing Document Open Interface in Purchasing.
Running the Response to Request for Quote Inbound (RRQI) Program ■ Release using Autocreate: allows you to use the Purchasing Autocreate function to convert purchase requisitions into blanket releases for blanket purchase orders. Debug Mode: Set the debug mode to report on debug information. Debug information is written to the concurrent manager log file: OFF: No debug information is generated. LOW: Summary debug information is written to the concurrent manager log file.
Running the Response to Request for Quote Inbound (RRQI) Program Prerequisites ❏ Create the inbound directory and update the INIT.ORA file. See: Defining Data File Directories, Oracle e-Commerce Gateway Implementation Manual, Release 11i. ❏ Define the ECE: Inbound file path profile option. See: e-Commerce Gateway Profile Options, Oracle e-Commerce Gateway Implementation Manual, Release 11i. ❏ Define trading partner relationships and enable EDI transactions for the trading partner.
Running the Response to Request for Quote Inbound (RRQI) Program Create or Update Items: Used with the Price/Sales Catalog or Response to RFQ to indicate whether you wish to update the item master with catalog item changes or add catalog items to the item master. Create Sourcing Rules: Indicate Yes or No on whether vendor sourcing rules should be created automatically during the Price/Sales Catalog and Response to RFQ import process.
Running the Ship Notice / Manifest Inbound (ASNI) Program See Also Inbound Response to Request for Quote, Oracle e-Commerce Gateway Implementation Manual, Release 11i Submitting a Request, Oracle Applications User’s Guide Viewing the Status of Concurrent Programs on page 9-7 Running the Ship Notice / Manifest Inbound (ASNI) Program Use this transaction to import supplier ship notices into your Purchasing system as a pre-receipt.
Running the Ship Notice / Manifest Inbound (ASNI) Program 3. Select the Ship Notice Inbound request. 4. Open the Parameters window. 5. Enter the inbound data file name or accept the default. 6. In the Execute Open Interface field, ■ ■ 7. enter Y to initiate the Receiving Open Interface program immediately. There are no program parameters. enter N if you do not want to initiate the Receiving Open Interface program in Purchasing. There are no program parameters.
Running the Shipping and Billing Notice Inbound (SBNI) Program Running the Shipping and Billing Notice Inbound (SBNI) Program Use this transaction to import supplier ship notices and invoices into your Purchasing and Payables system as a pre-receipt and unapproved invoice. Similar to the Ship Notice/Manifest transaction, the electronic ship notice provides a shipment identifier to facilitate the receipt of the physical goods and the creation of the unapproved invoice in a single EDI transaction.
Running the Shipping and Billing Notice Inbound (SBNI) Program 3. Select Shipment and Billing Notice request. 4. Open the Parameters window. 5. Enter the inbound data file name or accept the default. 6. In the Execute Open Interface field, ■ ■ 7. enter Y to initiate the Receiving Open Interface program immediately. There are no program parameters. enter N if you do not want to initiate the Receiving Open Interface program in Purchasing. There are no program parameters.
Running the Planning Schedule Inbound (SPSI) Program Running the Planning Schedule Inbound (SPSI) Program Use this transaction to import customer planning schedules into your Oracle Release Management system. Using the Release Management Demand Processor, you can import customer planning schedules into your Oracle Order Management and Oracle Planning systems.
Running the Planning Schedule Inbound (SPSI) Program 3. Select the IN: Inbound Planning Schedule (830/DELFOR) request. 4. Open the Parameters window. 5. Accept or change the Inbound Directory Path. 6. Enter the inbound data file. 7. In the Execute DSP flag field: Select Yes to initiate the Demand Processor. Select No if you do not want to initiate the Demand Processor. 8. Enter the Transaction Type: SPSI (defaulted). 9. Enter the Map Code for this file: RLM_SPSI_FF 10.
Running the Planning Schedule Inbound (SPSI) Program 7. In the Execute DSP flag field: Select Yes to initiate the Demand Processor. Select No if you do not want to initiate the Demand Processor. 8. Enter the Transaction Type: SPSI 9. Enter the Map Code for this file: RLM_SPSI_FF 10. Select the Debug Mode: 0, 1, 2, or 3 Set the Debug Mode to report on debug information for troubleshooting. Debug information is written to the concurrent manager log file: The Debug Mode is set using a number.
Running the Production Sequence Schedule Inbound (PSQI) Program Planning/Material Release Schedule Inbound, Oracle e-Commerce Gateway Implementation Manual, Release 11i Submitting a Request, Oracle Applications User’s Guide Oracle Release Management Implementation Manual, Release 11i Oracle Release Management User’s Guide, Release 11i Running the Production Sequence Schedule Inbound (PSQI) Program Use this transaction to import customer production sequence schedules into your Oracle Release Management sys
Running the Production Sequence Schedule Inbound (PSQI) Program ◗◗ To run the Production Sequence Schedule Inbound Program: This transaction may be submitted under either the EC Gateway Responsibility or the Release Management Responsibility. From the EC Gateway Responsibility: 1. Select the Process Import Program. 2. Select Request to submit an individual request. 3. Select the IN: Inbound Production Sequence Schedule (866) request. 4. Open the Parameters window. 5.
Running the Production Sequence Schedule Inbound (PSQI) Program From the Release Management Responsibility: 1. Navigate to the Process Inbound EDI Transactions. 2. Select Request to submit an individual request. 3. Select the IN: Inbound Production Sequence (866) request. 4. Open the Parameters window. 5. Accept or change the Inbound Directory Path. 6. Enter the inbound data file. 7. In the Execute DSP flag field: Select Yes to initiate the Demand Processor.
Running the Shipping Schedule Inbound (SSSI) Program For details on how to automate the process, see: Process Automation, Using e-Commerce Gateway for Inbound Demand, Oracle Release Management Implementation Manual, Release 11i.
Running the Shipping Schedule Inbound (SSSI) Program ❏ Define trading partner relationships and enable EDI transactions for the trading partner. See: Defining Trading Partner Data on page 3-4. ❏ Define code conversions. See: Defining Code Conversion Categories on page 4-8, Assigning Categories on page 4-10, and Defining Code Conversion Values on page 4-15. ❏ Customize interface data file layout, if necessary. See: Changing the Interface Data File Record Layout on page 5-2.
Running the Shipping Schedule Inbound (SSSI) Program 3 = HIGH: High level debug information is written to the concurrent manager log file. (This option generates an abundance of information.) 10. When finished, choose OK in the Parameters window. 11. Choose Submit and make a note of the Request ID returned. From the Release Management Responsibility: 1. Navigate to the Process Inbound EDI Transactions. 2. Select Request to submit an individual request. 3.
Running the Shipping Schedule Inbound (SSSI) Program Automating the Shipping Schedule Inbound Program The steps for receiving inbound EDI demand schedule transactions in Oracle e-Commerce Gateway and loading them from Oracle e-Commerce Gateway to Oracle Release Management can be automated. For details on how to automate the process, see: Process Automation, Using e-Commerce Gateway for Inbound Demand, Oracle Release Management Implementation Manual, Release 11i.
8 Outbound Transactions This chapter describes how to run the Oracle e-Commerce Gateway outbound transactions: ■ ■ ■ ■ ■ ■ ■ ■ ■ Extensible Architecture on page 8-2. Running the Application Advice Outbound (ADVO) Extract Program on page 8-2. Running the Invoice Outbound (INO) Extract Program on page 8-7. Running the Credit Memo / Debit Memo (CDMO) Extract Program on page 8-9. Running the Payment Order / Remittance Advice Outbound (PYO) Extract Program on page 8-10.
Extensible Architecture Extensible Architecture The Oracle e-Commerce Gateway provides two methods to add additional data elements that are not defined in Oracle Applications to EDI transactions: ■ Descriptive flexfields. ■ Oracle e-Commerce Gateway extensible architecture. Either method may be used separately, or both methods may be used together to customize a specific transaction to meet business needs.
Running the Application Advice Outbound (ADVO) Extract Program Prerequisites ❏ Create the outbound directory and update the INIT.ORA file. See: Defining Data File Directories, Oracle e-Commerce Gateway Implementation Manual, Release 11i. ❏ Define the ECE: Output file path profile option. See: e-Commerce Gateway Profile Options, Oracle e-Commerce Gateway Implementation Manual, Release 11i. ❏ Define trading partner relationships and enable EDI transactions for the trading partner.
Running the INTRASTAT Movement Statistics (MVSTO) Extract Program ■ Set the debug mode to report on debug information. Debug information is written to the concurrent manager log file: OFF: No debug information is generated. LOW: Summary debug information is written to the concurrent manager log file. MEDIUM: Medium level debug information is written to the concurrent manager log file. HIGH: High level debug information is written to the concurrent manager log file. (This option generates much information.
Running the INTRASTAT Movement Statistics (MVSTO) Extract Program As data is extracted from e-Commerce Gateway, only movement statistics with the status of Verify or Frozen are extracted. Once data is extracted, the e-Commerce Gateway sets the transaction status to EDI. Note: Oracle e-Commerce Gateway extracts data from Oracle Purchasing, Oracle Inventory, and Oracle Order Management tables. However, you only need licenses to one of these applications to run the Movement Statistics program.
Running the INTRASTAT Movement Statistics (MVSTO) Extract Program ■ ■ ■ ■ ■ ■ ■ Enter the legal entity. This must match the setup for movement statistic parameters. Enter the zone code. This must match the economic zone associated with the legal entity in the movement statistics setup. Enter the ”stat” type: INSTAT or EXSTAT. Enter the period name. This must match the period associated with the legal entity in the movement statistics setup.
Running the Invoice Outbound (INO) Extract Program Running the Invoice Outbound (INO) Extract Program Use this transaction to bill customers for goods sold and services rendered. Prerequisite Setup in Oracle Receivables Use Receivables to enter or adjust customer invoices. You have the option of including credit memos and debit memos in this transaction. Or, you may generate them separately using the Credit Memo / Debit Memo Outbound transaction.
Running the Invoice Outbound (INO) Extract Program 3. Select the Invoice Outbound transaction. 4. In the Parameters window, enter the following optional selection criteria: ■ Specify an output data file name if not using the default. ■ Enter creation dates, From and To. ■ Enter a bill-to customer name. ■ Enter a bill-to site name. ■ Enter a document type and a transaction (invoice) number. ■ Set the debug mode to report on debug information.
Running the Credit Memo / Debit Memo (CDMO) Extract Program Running the Credit Memo / Debit Memo (CDMO) Extract Program Use this transaction to process credit and debit memos that are generated in Oracle Receivables. You can generate credit memos and debit memos in the transaction, or have them generated with the Invoice Outbound transaction. See: Running the Invoice Outbound (INO) Extract Program on page 8-7.
Running the Payment Order / Remittance Advice Outbound (PYO) Extract Program ■ ■ Enter a document type and a transaction (credit memo / debit memo) number. Set the debug mode to report on debug information. Debug information is written to the concurrent manager log file: OFF: No debug information is generated. LOW: Summary debug information is written to the concurrent manager log file. MEDIUM: Medium level debug information is written to the concurrent manager log file.
Running the Payment Order / Remittance Advice Outbound (PYO) Extract Program Payments made using electronic funds transfer (EFT) may be processed via EDI if your EDI translator has the means to download the payment data from Payables to tape for delivery to the payee’s bank. Prerequisite Set Up in Oracle Payables Use Payables to enable the payer and payee site.
Running the Planning and Shipping Schedule (SSSO and SPSO) Extract Program See Also Outbound Payment Order / Remittance Advice, Oracle e-Commerce Gateway Implementation Manual, Release 11i Submitting a Request, Oracle Applications User’s Guide Viewing the Status of Concurrent Programs on page 9-7 Running the Planning and Shipping Schedule (SSSO and SPSO) Extract Program Use the planning schedule to communicate forecast requirements to your suppliers.
Running the Planning and Shipping Schedule (SSSO and SPSO) Extract Program Use Scheduler Workbench or enable AutoConfirm option in AutoSchedule to confirm your schedules. Only confirmed schedules may be transmitted via EDI to your supplier(s). Oracle Purchasing Supplier Scheduling uses components of Oracle Purchasing to calculate and maintain schedules. Use the Approved Supplier list created in Purchasing to establish a relationship between the ship-to organization, supplier site, and item.
Running the Planning and Shipping Schedule (SSSO and SPSO) Extract Program 3. Select the Planning or Shipping Schedule Outbound transaction. 4. In the Parameters window, enter the following optional selection criteria: ■ Specify an output data file name if you are not using the default. ■ Enter the schedule ID. ■ Set the debug mode to report on debug information. Debug information is written to the concurrent manager log file: OFF: No debug information is generated.
Running the Purchase Order Outbound (POO) Extract Program Running the Purchase Order Outbound (POO) Extract Program Use this transaction to procure goods and services from suppliers. Approved purchase orders (POs), including standard POs, planned orders, planned releases, blanket purchase agreement, and blanket releases can be extracted. Note: This transaction is not used to convey PO change or acknowledgment information.
Running the Purchase Order Outbound (POO) Extract Program ❏ Define code conversions. See: Defining Code Conversion Categories on page 4-8, Assigning Categories on page 4-10, and Defining Code Conversion Values on page 4-15. ❏ Customize interface data file layout, if necessary. See: Changing the Interface Data File Record Layout on page 5-2. Note: Both the outbound Purchase Order and Purchase Order Change Request transactions allow attachments. See: Attachments on page 8-20.
Running the Outbound Purchase Order Change Request (POCO) Extract Program 7. Enter completion options. 8. Choose Submit and make a note of the Request ID returned.
Running the Outbound Purchase Order Change Request (POCO) Extract Program Procurement Card Information The Outbound Purchase Order Change Request transaction includes procurement card information in the interface data file. This includes credit card type, credit card number, and expiration date. You can attach text to the outbound Purchase Order and the Purchase Order Change Request transactions at the header, line, and shipment levels.
Running the Outbound Purchase Order Change Request (POCO) Extract Program ◗◗ To run the Purchase Order Change extract program: 1. Navigate to the Extract Program window. 2. Select Request to submit an individual request. 3. Select the PO Change Outbound transaction. 4. In the Parameters window, enter the following optional selection criteria: ■ Enter the output file name if you are not using the default. ■ Enter the PO number From and To. ■ Enter the PO revision date From and To.
Attachments Attachments You can attach text to the outbound Purchase Order and the Purchase Order Change Request transactions at the header, line, and shipment levels. Attachments can be stored as short text (up to 2 Kilobytes) or long text (up to 2 Gigabytes) of data. Each attachment can be split into segments (or records). Segment size is set using the POO Attachment Segment Size and / or the POCO Attachment Segment Size profile options. The default for both profile options is 400 bytes.
9 Oracle e-Commerce Gateway Reports This chapter discusses Oracle e-Commerce Gateway reports: ■ Reports on page 9-2. ■ Code Conversion Values Report on page 9-2. ■ Interface File Data Report on page 9-3. ■ Transaction Layout Definition Report on page 9-5. ■ Trading Partner Report on page 9-5. ■ Transactions / Trading Partners Report on page 9-6. ■ Viewing the Status of Concurrent Programs on page 9-7.
Reports Reports Reports are submitted using the Standard Request Submission window. In the Submit Requests window, enter Audit Information Report in the Name field. ■ Code Conversion Values Report on page 9-2. ■ Interface File Data Report on page 9-3. ■ Transaction Layout Definition Report on page 9-5. ■ Trading Partner Report on page 9-5. ■ Transactions / Trading Partners Report on page 9-6.
Interface File Data Report External Value Enter an external (transaction interface data file) value or leave blank to report on all external values. See Also Submitting a Request, Oracle Applications User’s Guide Interface File Data Report Reports on all the data in a specified transaction interface data file.
Interface File Data Report Table 9–1 Interface Data FIle Columns and Descriptions Column Description Application Column For outbound transactions, application column is the source column of the Oracle data within the Application Table. For inbound transactions, the application column is the column within the interim Application Table of the Oracle application open interface (API) to receive the data.
Trading Partner Report Transaction Layout Definition Report Reports exact layout of a specified transaction interface data file. All interface data files are made up of several records. Each record has two sections, the record key (positions 1-100) and the application data area (positions 101-600). Each record also has a record number that identifies the level and block of data in the interface data file. The numbering scheme for each level is in increments of 1000.
Transactions / Trading Partners Report Trading Partner Enter a specific trading partner or leave blank to report on all trading partners within a trading partner group. Print Contact Information Select Y (Yes) or N (No; default) to include or exclude, respectively, EDI contact data for each trading partner. Creation Date From / To Enter the date the trading partner was created From and / or To. Both are optional. If the From date is blank, all trading partners are listed until the To date.
Viewing the Status of Concurrent Programs Test Flag Select T (Test), P (Production), or leave blank to report on both test and production transactions. See Also Submitting a Request, Oracle Applications User’s Guide Viewing the Status of Concurrent Programs ◗◗ To view the status of your concurrent programs: ■ Choose View My Requests from the Help menu of the Submit Requests window and identify your request for inbound or outbound transactions.
Viewing the Status of Concurrent Programs 9-8 Oracle e-Commerce Gateway User’s Guide
A Windows and Navigator Paths This appendix shows you the default Navigator path for each e-Commerce Gateway window. Refer to this appendix when you do not already know the Navigator path for a window you want to use.
Windows and Navigator Paths Windows and Navigator Paths For windows described in other manuals: See... Refer to this manual for a complete window description. User Oracle Applications User’s Guide Text in brackets ([ ]) indicates a button.
B Seed Data Reconciliation This appendix describes what seed data is in Oracle e-Commerce Gateway and explains how to reconcile your seed data when upgrading: ■ Seed Data Reconciliation on page B-2. ■ Performing Seed Data Reconciliation on page B-4.
Seed Data Reconciliation 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, and so on. In this chapter, the definition of seed data is limited to the data used for: ■ Definition of transaction record layouts. ■ Assignment of code categories to a transaction record layout. ■ Definition of process rules associated with a transaction.
Seed Data Reconciliation ■ Identify new columns. ■ Reapplies your customized preexisting record layout modifications (optional). ■ ■ Reapplies process rules, column rules, and code conversion category assignments to the columns in the new transaction record layout (optional). Produces a request log to report discrepancies between the preexisting and new transaction record layouts.
Performing Seed Data Reconciliation See Also Performing Seed Data Reconciliation: page 4 Performing Seed Data Reconciliation The following steps accomplish a full Seed Data Reconciliation review: 1. Run the Transaction Layout Definition Report. (Optional) 2. Apply the transaction-specific patch. 3. Submit the Seed Data Reconciliation request. 4. Run the Transaction Layout Definition Report again. (Optional) 5. Review the Seed Data Reconciliation request log. 6.
Performing Seed Data Reconciliation ◗◗ To execute the Seed Data Reconciliation Request: 1. Enter the Transaction Type from the List of Values. After patches are applied, any transaction that needs seed data reconciliation will appear in the Transaction Type List of Values. Select one of your transactions from the List of Values. If you do not have a transaction in that list implemented, you need not submit a request for that transaction at this time.
Performing Seed Data Reconciliation 6. When finished, choose OK in the parameter window. 7. Enter schedule options to schedule the request. 8. Enter Completion Options 9. Choose Submit and make a note of the Request ID returned. Once the request for reconciliation for a particular transaction is completed, the transaction is removed from the Transaction Type’s List of Values. Repeat these steps for each of your implemented transactions that appear in the Transaction Type List of Values.
Performing Seed Data Reconciliation record layout and the record layout in the patch reference the same record/position number for two different data elements. If this occurs, the Seed Data Reconciliation Request Log will report the discrepancy but you must manually define the correct record/position number using the Interface File Definition form. Following is sample output from the Seed Data Reconciliation Request Log: ***** Column: ”ASN_TYPE” * Checking to see if any Column Rules need to be reconciled..
Performing Seed Data Reconciliation column rules. Use the Interface File Definition form to reapply these assignments and definitions. Review and Modify for Post Processes (if necessary) Notify trading partners if there are interface file changes that affect their process. If the new transaction record layouts impacts data maps in any subsequent or preceding processes, make appropriate changes to the data maps.
Glossary A ANSI American National Standards Institute which establishes national standards for the United States. The parent organization for X12 and also serves as the North American representative to ISO (International Standards Organization). ASC X12 Accredited Standards Committee X12 group. This group is accredited by ANSI and maintains and develops the EDI standards for the United States and Canada. ASCII American Standard Code for Information Interchange.
business application Software that performs a particular business function or group of functions (accounts payable, for example). business document A document used for conducting business between two trading partners — a purchase order or invoice, for example. E EDI See Electronic Data Interchange (EDI) EDIFACT Electronic Data Interchange for Administration, Commerce, and Trade is the current acronym for standards developed within Working Party 4.
in the form of credit and debit transfers, related bank balance, banking transactions, and account analysis. functional acknowledgment The acknowledgment to indicate the results of the syntactical analysis of electronically encoded documents. Applies to a functional group and can include detail. N National Automated Clearing House Association The NACHA is a non-profit organization responsible for developing and maintaining the rules and guidelines for using the ACH network.
transaction set line item area The line item area encompasses the actual business transaction set and includes information, such as quantities, descriptions, and prices. transaction set summary area The summary area contains control information and other data that relate to the total transaction. V VAN(S) Value Added Network (Supplier). W wire A payment method where you pay invoices by notifying your bank to debit your account and credit your suppliers account.
Index A Application Advice outbound extracting, 8 - 2 ASC X12 810, 7 - 2, 8 - 7 820, 8 - 10 824, 8 - 2 830, 8 - 12 832, 7 - 4 843, 7 - 6 850, 8 - 15 856, 7 - 9 857, 7 - 11 860, 8 - 17 862, 8 - 12 Assigning Categories, 4 - 10 Assigning Column Rules, 5 - 7 Assigning Process Rules, 5 - 5 Attachments, 8 - 20 C Changing the Interface Data File, 5 - 2 Code categories predefined, 4 - 11 Code conversion, 4 - 2 Code Conversion Values Report, 9 - 2 Column rules, 5 - 7 Column violations, 6 - 8 E EDIFACT APERAK, 8 -
O Overview, T 1-2 Trading partner data, 3 - 4 Trading Partner Report, 9 - 5 Trading partners overview, 3 - 2 Transaction code ADVO, 8 - 2 ASNI, 7 - 9 CATI, 7 - 4 CDMO, 8 - 9 INI, 7 - 2 INO, 8 - 7 POCO, 8 - 17 POO, 8 - 15 PYO, 8 - 10 RRQI, 7 - 6 SBNI, 7 - 11 SSPO, 8 - 12 SSSO, 8 - 12 Transaction Layout Definition Report, 9 - 5 Transactions Enabled for Trading Partners Report, 9 - 6 Transactions supported, 1 - 5 P Payment Order / Remittance Advice outbound extracting, 8 - 10 Performing Seed Data Reconcilia
