This chapter contains test transactions for Oracle e-Commerce Gateway implementation.
This chapter covers the following topics:
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 E-Business Suite 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 E-Business Suite 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 E-Business Suite provide Reports/windows for you to review detected exceptions.
Exceptions generally result from incorrect set ups in Oracle e-Commerce Gateway or Oracle E-Business Suite that may be corrected in the respective applications. Another form 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 E-Business Suite 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 E-Business Suite. So before you initiate the import process, you must verify all your setups. 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:
Transaction specific special considerations
Trading partner link between Oracle e-Commerce Gateway and Oracle E-Business Suite
Oracle e-Commerce Gateway Required Fields
Review Oracle e-Commerce Gateway Exceptions
Resolve Oracle e-Commerce Gateway Exceptions
Relevant Application Profile Options and Setups
Review Application Open Interface Required Fields
Review Application Open Interface Exceptions
Resolve Application Open Interface Exceptions
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 E-Business Suite
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 the following in the appropriate Oracle E-Business Suite application:
Relevant application profile options and setups are defined
Transaction interface file contains valid values. Review this using the Oracle e-Commerce Gateway Interface File Data Report
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 E-Business Suite application Open Interface API validations, use the application report to review the exceptions
If the exceptions are due to set up errors in Oracle e-Commerce Gateway or Oracle E-Business Suite, make the necessary corrections and submit the transaction for reprocessing
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.
Continue to initiate the import process, review exceptions, resolve exceptions and re-process the transaction until the transaction completes successfully and the data is loaded into the base Oracle E-Business Suite application tables
A single inbound transaction interface file may contain data designated for different organizations defined in Oracle E-Business Suite. 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.
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 testing outbound transactions. Crucial to the successful implementation of an outbound transaction are all the setups necessary in Oracle e-Commerce Gateway and Oracle E-Business Suite 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:
Transaction specific special considerations
Trading partner link between Oracle e-Commerce Gateway and Oracle E-Business Suite
Extract Criteria
Columns Updated Upon Extraction
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 E-Business Suite
Transaction is enabled at the system profile level as well as at the trading partner detail level
Relevant code conversions are defined
Verify the following in the appropriate Oracle E-Business Suite application:
Relevant application profile and setups are 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
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 E-Business Suite and re-initiate the outbound transaction
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
Run the Interface File Data Report to review the contents of the transaction interface file.
Verify the following:
Report output matches the data entered in Oracle E-Business Suite and is consistent with your selection criteria.
Code conversion enabled columns are converted according to your conversion rules.
Report output matches application report output (if application report is available)
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 E-Business Suite 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.