This chapter contains Oracle e-Commerce Gateway implementation steps and checklists.
This chapter covers the following topics:
The following is a list of the implementation steps to implement a transaction in Release 12. Since the total solution requires other Oracle E-Business Suite 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:
Upgrading from Release 11i
Important: For the Release 11i version that are supported for upgrading to Release 12, see Oracle E-Business Suite Upgrade Guide: Release 11i to Release 12.1.1 to upgrade Oracle E-Business Suite to Release 12.1.1 from Release 11i.
Follow the instructions mentioned in "Oracle E-Business Suite Release Update Pack Readme, Release 12.1.delta.2 (12.1 RUP 2)", My Oracle Support Knowledge Document 949406.1 to enable Oracle E-Business Suite Release 12.1 RUP 2.
Fresh install of Oracle E-Business Suite 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.
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 E-Business Suite Upgrade Guide: Release 11i to Release 12.1.1 for details to upgrade Oracle E-Business Suite to Release 12.1.1.
Follow the instructions mentioned in "Oracle E-Business Suite Release Update Pack Readme, Release 12.1.delta.2 (12.1 RUP 2)", My Oracle Support Knowledge Document 949406.1 to upgrade to Oracle E-Business Suite Release 12.1 RUP 2.
| Step | Required/ Optional | Description | Reference (IM = Implementation Manual) |
|---|---|---|---|
| 1 | Required | Install Release 12.1 RUP 2 Oracle e-Commerce Gateway. | Oracle E-Business Suite Installation Guide: Using Rapid Install Apply Oracle E-Business Suite Release 12.1.delta.2 Release Update Pack (12.1 RUP 2) to bring your system to the 12.1 RUP 2 release. See "Oracle E-Business Suite Release Update Pack Readme, Release 12.1.delta.2 (12.1 RUP 2)", My Oracle Support Knowledge Document 949406.1 for details. |
| 2 | Required | Run the following 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 |
User's Guide: Reports |
| 3 | As Needed | 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. |
User's Guide: Changing the Interface Data File Record Layout Assigning Categories IM: Modify Transaction Interface File IM: Set Up Code Conversion |
| 4 | Required | Set up system profiles, pay special attention to the profiles for inbound and outbound directory path: Inbound file directory Outbound file directory |
Set up system profiles, pay special attention to the profiles for inbound and outbound directory path: Inbound file directory Outbound file directory |
| 5 | Required | 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 | IM: Define UTL_FILE_DIR parameter in INIT.ORA file |
| 6 | As Needed | Set up general transaction profiles Enable/disable transaction (for all transactions) Address precedence (for inbound transactions) |
User's Guide: Setting Profile Options IM: Set Up Profiles |
| 7 | As Needed | Set up transaction specific profiles for outbound transactions, such as the Purchase Order or Purchase Order Change transactions | User's Guide: Setting Profile Options IM: Set Up Profiles |
| 8 | Required (for inbound transactions) | Review seeded Process Rule Actions and update rule action if default behavior is not desired | IM: Determine Process and Column Rules and Actions |
| 9 | Required (for inbound transactions) | Review seeded Column Rule Actions for required fields and update rule action if default behavior is not desired | IM: Determine Process Column Rules and Actions Application Set Up |
| 10 | Required (for inbound transactions) | Review seeded Column Rule Actions for date and numeric fields and update rule action if default behavior is not desired | IM: Determine Process and Column Rules and Actions |
| 11 | Optional (for inbound transactions) | Determine if other columns in the transaction require Column Rules | IM: Determine Process and Column Rules and Actions |
| 12 | As Needed | Enable additional data fields as necessary using reference fields, descriptive flexfields or the Oracle e-Commerce Gateway Extensible Architecture |
IM: Enable Additional Transaction Data |
| 13 | Optional | Review interface file definitions (record layouts) for the transaction and make any necessary adjustments | User's Guide: Changing the Interface Data File Record Layout IM: Modify Transaction Interface File |
| 14 | Required | Run Transaction Layout Definition Report to get the current definitions | User's Guide: Reports |
| 15 | Required | Synchronize the data maps in the Translator with the transaction interface file definitions | IM: Interface with Translators |
| 16 | Required | Ensure that Location Code is defined for the trading partner entity (customer site, supplier site, bank branch, internal location) defined in Oracle E-Business Suite | IM: Application Transaction Detail |
| 17 | Required | Define trading partner: Assign trading partner to address site in E-Business Suite 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) |
IM: Set Up Trading Partner Trading Partner |
| 18 | As Needed | Set up code conversions Review/define Code Conversion Categories Enable Code Conversion Define Code Conversion Values |
IM: Set Up Code Conversion Code Conversion |
| 19 | Required | Review E-Business Suite setups for each transaction and update as necessary | IM: Application Transaction Detail |
| 20 | Required | Prepare data to test transaction Add data in Oracle E-Business Suite to test outbound transaction Create inbound file to test inbound transaction |
IM: Test Transactions |
| 21 | Required | Test the transaction being implemented at several levels until results match expectations Internally (Oracle e-Commerce Gateway and Oracle E-Business Suite) With Translator With Trading Partner |
IM: Test Transactions |
| 22 | Required | Release fully tested transaction to production | |
| 23 | As Needed | Archive transaction interface files as needed | IM:Archive/Backup |
In summary, the following has been installed or set up:
The upgrade version is installed
All custom development re-integrated after upgrade is completed (when appropriate)
System and Transaction Profile setups are entered
Process rules and Column rules are set up
Code Conversion is set up
Trading Partners are set up
Base Oracle E-Business Suite application setups are complete
Transaction interface file definitions modifications are completed (when appropriate)
Pass a simple outbound and/or inbound transaction through the Oracle e-Commerce Gateway to validate the installation before any site-specific configuration is undertaken.
To help ensure a successful implementation, do the following:
Read the Introduction, and become familiar with the pre-requisites
Implement related Oracle E-Business Suite application modules before implementing Oracle e-Commerce Gateway
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.
| Step | Required/ Optional | Description | Reference (IM: Implementation Manual) |
|---|---|---|---|
| 1.1 | Required | Define Access Responisbilities | IM: Define Responsibilities |
| 1.2 | Required | Define the utl_file_dir parameters. Done by DBA. | IM: Define UTL_FILE_DIR Parameter in INIT.ORA File |
| 2 | Omit | Run reports for each transaction | |
| 3 | Omit | Compare reports |
In summary, the following has been set up in addition to the summary items in the software upgrade:
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
System and transaction profile setups are entered.
Transaction specific options have been implemented (as needed)