This chapter covers the following topics:
Reports are submitted using the Standard Request Submission window.
For additional information on using running requests, see the following topics in the Oracle E-Business Suite User's Guide:
Running Reports and Programs
Monitoring Requests
Viewing Request Output
Reports all defined code conversion values. This data can be used for troubleshooting purposes. You can report on all or specific code categories, internal values, and external values.
Define code conversion categories. See: Defining Code Conversion Categories.
Assign code conversion categories. See: Assigning Categories.
Define code conversion values. See: Defining Code Conversion Values.
You must enter the following parameters:
Enter a specific code category or leave blank to report on all categories.
Enter an internal (Oracle E-Business Suite) value or leave blank to report on all internal values.
Enter an external (transaction interface data file) value or leave blank to report on all external values.
Reports on all the data in a specified transaction interface data file.
The following table lists and describes the columns of the interface data file definition format:
| Column | Description |
|---|---|
| Record Number | Record numbers assigned by the set of data elements. |
| Position | Relative position among the business data within the given record. |
| Length | Data element width. This data is likely to be shorter than data defined in the Oracle E-Business Suite to align the data with the standards. |
| Start Column | Starting column of the data within the given record. It starts in column 101. |
| Interface Column Name | Oracle e-Commerce Gateway uses these interface fields to authenticate the trading partner and transaction before processing each transaction. |
| Interface Column Value | The associated value of each interface column used for processing transactions. |
You must enter the following parameters:
Enter the e-Commerce Gateway transaction code. See: EDI Transaction Support.
Enter the full directory path where the interface data file resides. The default is set by the ECE: Inbound Directory or the ECE: Output file path profile options, respectively.
Enter the name of the interface data file.
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. The exact number of blocks varies by transaction. However, the hierarchy remains the same. Large transactions may have any level span over several blocks of 1000.
Enter the e-Commerce Gateway transaction code or leave blank to report on all transactions. See: EDI Transaction Support.
Enter Yes or No to include or exclude, respectively, data not assigned record numbers. The default is No.
A trading partner in Oracle e-Commerce Gateway is an address defined in Oracle E-Business Suite. A translator code in the e-Commerce Gateway identifies the trading partner as defined in the EDI translator.
Since trading partners can be associated with operating units through the trading partner group setup, Oracle e-Commerce Gateway allows you to run Trading Partner reports and Transactions / Trading Partners reports for a specified operating unit.
Define trading partner groups and individual trading partners. See: Defining Trading Partner Data.
If the Trading Partner reports are single-organization reports, then the Operating Unit field is a mandatory field. You must enter this field to run the report for a specified operating unit.
If the reports are multiple-organization reports and you want to generate the reports for all the operating units associated with your responsibility, then you must run the report one by one by specifying each operating unit individually.
Enter a specific trading partner group or leave it blank to report on all trading partner groups.
Enter a specific trading partner or leave it blank to report on all trading partners within a trading partner group.
Select Y (Yes) or N (No; default) to include or exclude, respectively, EDI contact data for each trading partner.
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. If the To date is blank, all trading partners are listed from the From date to the current date.
Enter the date the trading partner was last updated From and / or To. Both are optional. If the From date is blank, all trading partners are listed until the To date. If the To date is blank, all trading partners are listed from the From date to the current date.
Reports all enabled transactions per trading partner.
Since trading partners can be associated with operating units through the trading partner group setup, Oracle e-Commerce Gateway allows you to run Trading Partner reports and Transactions / Trading Partners reports for a specified operating unit.
Define trading partner groups and individual trading partners. See: Defining Trading Partner Data.
If the Transactions / Trading Partners reports are single-organization reports, then the Operating Unit field is a mandatory field. You must enter this field to run the report for a specified operating unit.
If the reports are multiple-organization reports and you want to generate the reports for all the operating units associated with your responsibility, then you must run the report one by one by specifying each operating unit individually.
Enter the e-Commerce Gateway transaction code or leave blank to report on all transactions. See: EDI Transaction Support.
Enter a specific transaction type or leave blank to report on all transaction types.
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.
Or, choose Requests from the Navigator to open the Concurrent Requests Summary window and find the request ID corresponding to your inbound and / or outbound request. See: Submitting a Request, Oracle E-Business Suite User's Guide.