E lectronic D ata I nterchange

Agenda Sterling Commerce GIS businesses process Communication protocols E1 EDI data transformation Comments and Questions

State-of-the-art architecture providing cutting edge performance and scalability SMTP EDIINT (AS1, AS2) FTP, FTP/S HTTP, HTTP/S ebXML SOAP XFORMS (Webforms) EDI / XML RosettaNet Exchanges (e.g., Transora, UCCnet) Trading Partners Value-Added Networks Comm Services Web Extensions Integration Broker Mailbox Intelligent routing Graphical Modeler Collaboration Exception Handling Services > BPM-centric > Open Standards Support Gentran Integration Suite Solution Footprint Technology CRM ERP Messaging Legacy/Custom Apps Applications Databases EAI Adapters Graphical Mapper

Thank You G entran I ntegration S uite

Amsco BP

Data from Amsco

Data Retrieved from FTP Server by GIS

Raw data placed on IFS in From folder

Data Mapped from Amsco Format to Cardinal Format via GIS

GIS places transformed data in to plant folder

GIS submits a job on the corporate Iseries

Plant iSeries Job Reads data that resides on the corporate iSeries Creates work order

EDI Order inbound process Flow Used for all Inbound Orders

EDI Order inbound process Flow 1) EDI order arrives 2) GIS translates into XML file 3) GIS Updates E1 tables using XML file –F47011Order Header –F47012Order Detail –F580100Attributes 4) GIS submits a call to the pre-processor UBE. The call will submit the pre- processor job for the specific Trading partner (Anderson Windows Flexiframe, Anderson Windows Control Number, Jen-Weld, Lincolnwood, SNE, etc.) and business unit (SGIG, SGCG, etc) This UBE will convert attributes from customer to standard Cardinal attributes. Based on the attributes, an item number will be assigned to the line.

EDI Order inbound process Flow 5) R47011 is submitted to generate E1 sales order, tag file and configurator header and detail files. R47011 will be modified to. Release order if at least 1 line item does not have an error. Call the business function to create the Order tag file records (F580015).. Create the Configurator records (F3201 and F3211) by calling the specific Configurator business functions.

1.EDI Order Arrives

2. GIS translates into XML file

3. GIS Updates E1 tables

4. Setup Data Transform Rule(1) F – IF statement –PEL 480 <> L –AND PEL 330 = 5.0 F – Then statement –PEL 330 = 4.7

4. Data Transformation Matrix – If

4. Data Transformation Matrix – Then

4. Preprocess UBE Specific to EDI (AW Control, AW Flexiframe, etc) Will use standard business functions to transform data from EDI to CGI. Will assign the item number based on transformed attributes and custom business function Validate incoming information If error exist, user will use modified P47010 (EDI inquiry & maintenance) and row exit from detail screen to correct the attributes, and rerun the preprocess UBE

5. Load Order to E1 Run R47011 to load order into system –Loads F4201 (Sales order header), F4211 (Sales Order Detail), F (Order tag) and the Configurator files (F3201 and F3211). –Validates all attributes to ensure compliance with configurator rules.

EDI SharePoint Portal Web access to EDI Contacts, Documents, & Tasks

Cardinal EDI customer document Communication Methods File Types EDI Document Types Unit Labels Options Label Color Lite Thickness Overall Unit Thickness File Description CTCF – Color, Treatment, Coating, and Fabrication M-Codes C-Codes Product Terminology Product Information Terms Product Processing Information Terms Shape Catalog Catalog Usage Edgework Side Definitions