GAINSystems Oracle Integration Overview

GAINSystems has a long track record of integration success with Oracle. To facilitate the exchange of data between Oracle and GAINS, the GAINS Integration Toolkit (GIT) was developed by GAINSystems as a purpose-specific utility strictly for GAINS-related interfacing. It enables precise mapping of fields between Oracle and the GAINS database. The diagram below provides a summary-level data flow between GAINS and Oracle.

Standard mapping templates are provided out of the box and are maintained by GAINS to ensure integrity across new GAINS and Oracle ERP versions. Data is transferred by means of interface files (XML or ASCII), or by directly populating Oracle staging tables via auto-generated queries. The GUI-based toolkit also provides great flexibility in tailoring its usage to client-specific variations of Oracle. It can be used on-demand to interface data, or it can be run automatically as part of a regularly scheduled batch process. In both cases, data may be imported and/or exported to Oracle.

Aliases are used in the toolkit to map GAINS fields to corresponding fields in Oracle and vice versa. These aliases are then logically grouped in a variety of ways to create Data Sets. As is shown in the screenshot (Figure 2), SQL is automatically generated which can be used to import or export the data. This particular example shows the mapping for a bill-of-material interface file.

GAINS®

Figure 1: Common information exchanges between Oracle and GAINS

Page 1 of 3

Parameter Optimization

SAP GAINS

Material-level costs and parametersItem Master

Sales order lines sold/usedDemand Transactions

Purchase order linesSupply Transactions

Kit-component relationshipsBill-of-Material

New-obsolete item relationshipsItem Supercession

Others - as neeeded

Stock Policy

Default/Preferred Source

Demand Forecast

Safety Stock / ROP

Order Quantity / ROQ

Purchase Orders

Work Orders

Transfer Orders

Replenishment Optimization

Oracle

Data Sets are then further grouped into Data Maps and Groups. This enables well-defined groups of interfaces for various situations. For example, a client may choose to only interface new or updated items daily, while processing all items on the weekend during low system usage. The Integration Toolkit allows the specification of a Data Group (Figure 3), which contains only the data needed for daily processing, and another Data Group, which may contain the data needed for weekend processing.

Figure 2: Grouping of alia in a defined bill-of-material data set

Figure 3: Data Sets are maintained in Data Groups to facilitate multiple interface processes

Page 2 of 3

1200 North Ashland AvenueSuite 300 • Chicago, IL 60622 USATel: (630) 505-3030Fax: (630) 505-3041Website: www.gainsystems.com

CHICAGO, ILLINOIS

MELBOURNE, AUSTRALIA

GAINS is a wholly owned proprietary system by GAINSystems, headquartered in Oak Brook, IL USAGAINS and GAINSystems are registered trademarks of GAINSystemsCopyright © GAINSystems 1971-2010

Planned Improvements

The next release of the GIT (due in 2010) is based on a Web Services architecture that is fully SOA ready. This set of Web Services, in addition to improving the toolkit’s general architecture, will improve the on-demand/event-based integration capabilities between GAINS and Oracle.

Appendix 1: Summary of the Oracle-to-GAINS data table mappings

Appendix 2: Example of the GAINS-to-Oracle data table mapping (similar mappings exist for other order types and inventory parameters)

Page 3 of 3

# Type of Data GAINSystems File Oracle Tables Referenced Notes

1 Item Master InitInfc

1) kesx_mtl_related_items_all

Defines items along with and attributes and on-hand values

2) inv.mtl_system_items_b3) apps.mtl_categories4) inv.mtl_item_categories5) gl.gl_code_combinations6) bom.cst_item_costs7) apps.mtl_onhand_quantities8) inv.mtl_secondary_inventories

2 Demand Transactions Dmdtrans

1) ont.oe_order_lines_all

Defines set of open and historical demand transactions

2) apps.hz_cust_accounts3) inv.mtl_system_items_b4) ont.oe_order_headers_all5) inv.mtl_material_transactions6) wip.wip_discrete_jobs wdj7) wip.wip_entities8) ar.hz_cust_accounts9) apps.mtl_system_items

3 Supplier Transactions Suptrans

1) wip.wip_discrete_jobs

Defines set of open and historical supply transactions

2) wip.wip_entities3) inv.mtl_system_items_b4) apps.mtl_categories5) inv.mtl_item_categories6) po.po_lines_all7) apps.fnd_user8) wip.wip_requirement_operations9) po.po_requisition_headers_all10) po.po_requisition_lines_all11) po.rcv_shipment_lines12) po.po_distributions_all13) po.po_headers_all14) po.po_line_locations_all

4 Superceded Items Subchain1) kesx_mtl_related_items_all Defines relationships between items

where supercessions have occurred2) inv.mtl_system_items_b

5 Bill of Materials BilloMat

1) apps.bom_inventory_components

Defines relationships between kits and associated components

2) apps.bom_bill_of_materials3) apps.mtl_system_items 4) kesx_mtl_related_items_all5) inv.mtl_system_items

# Type of Data Oracle Tables Referenced Notes

1 Purchase Orders1) po_headers.po_distributions_interface Defines required purchase order

information such as supplier, quantity, date, etc.

2) po_headers.po_headers_interface3) po_headers.po_lines_interface