Extensible architecture, Seed data reconciliation example – Oracle A75089-02 User Manual

Page 133

Advertising
background image

Seed Data Reconciliation

Seed Data Reconciliation

B-3

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.

Extensible Architecture

If you have e-Commerce Gateway extension tables for the outbound transaction,
you must re-run the SQL script to populate the extension tables and update the
interface data file definition. For each new column added to the extension table, you
must again insert a record into ECE_INTERFACE_COLUMNS to position the data
element in the interface data file.

Seed Data Reconciliation Example

The following table lists an example of seed data reconciliation. (Record layout
attributes include record, position, length, record layout, and qualifier.)

Table B–1

Seed Data Reconciliation Example

Data
Element

Record Layout
Attributes

Notes

Before
Patch

In the Patch

ABC

1000,
100, 30,
RF, REF

1000, 100, 50,
RF, REF

If Preserve Transaction Layout is Y, length remains at 30
after reconciliation. If N, length is updated to 50 after
reconciliation.

ABC

1000,
100, 50,
PO, POI

1050, 90, 50,
RF, REF

Data element given all new record layout attributes in the
patch. If Preserve Transaction Layout is Y before patch,
attributes are retained after reconciliation. If Preserve
Transaction Layout is N in the patch, the patch attributes
are used.

ABC

does not
exist

1000, 10, 40,
RF, REF

New data element is defined in the patch. If Preserve
Transaction Layout is Y or N, new data element is added to
the transaction record layout.

ABC

XYZ

1010, 90

,

50, RF,
REF

does not
exist

1000, 30, 50,
RF, RF1

1010, 90

, 50,

RF, REF

Two different data elements reference the same record and
position number.

If Preserve Transaction Layout is Y or N, data elements
cannot be automatically reconciled and manual
intervention is required to resolve the discrepancy.

Advertising