Oracle A75089-02 - Manual (Page 136)

Performing Seed Data Reconciliation
B-6 Oracle e-Commerce Gateway User’s Guide
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.
Run Transaction Layout Definition Report (Optional)
Select the Run Reports under Reports in the e-Commerce Gateway menu. Submit
the Transaction Layout Definition Report to obtain the after images of the
transaction record layouts for each transaction of interest to you.
This is an optional step, but it is highly recommended. This step is particularly
important if you do not choose to preserve the transaction layout and would like a
before and after image of the transaction record layout. See
Reports on page 9-2.
Review Seed Data Reconciliation Request Log
If you select no for the Preserve the Transaction Layout parameter above, this log
will provide summary information about the Seed Data Reconciliation process.
Detailed reporting is not necessary since all of the record layout definitions in the
patch will be automatically applied.
If you select yes for the Preserve the Transaction Layout parameter above, this log
will provide detailed information about the reconciliation and analysis process used
to apply record layout definitions from the patch.
Each data element in the transaction being reconciled will be analyzed for record
layout differences. If you selected yes for the Preserve Code Category Assignments
or Preserve Column Rules parameter, these definitions will be analyzed for
differences as well.
For each data element, the Seed Data Reconciliation Request Log will record any
updates automatically applied during the reconciliation process as well as data (e.g.
record layout definitions, column rules) which was analyzed, but no update was
required.
It is also possible to encounter a situation where automatic reconciliation is not
possible and manual intervention is required. This will occur if the preexisting