solazyme edi 810 outbound process 1 0

Interface Design

Solazyme EDI 810Interface

Team Members SOLAZYME: Michael Beck, Christiane Midence, Betty Mihalovics, Yelena Popova, Brandy Hoffman

Copy To Solazyme; Murthy Juluri; Santosh Pallerla; Loren Joski

Consultant Hari Gandikota

Date Created 04/25/11

Module Oracle EDI, Order Management

Subject Solazyme EDI 810 Interface

Date Updated 05/17/11

Version 1.1

Solazyme EDI 810 Interface Design

Document Control

Change Record

Date

Author Comments

04/25/11 Hari Gandikota 1.0 Initial version05/17/11 Santosh Pallerla 1.1 Auto invoice Scheduling Program

Reviewers

Name Positions

Bandy Hoffman Solazyme Team MemberMichael Beck Solazyme Project ManagerBillanda Quan DiCentral EDI Project CoodinatorNatasha Luzan DiCentral EDI Mapper

Loren Joski DAZSI Project ManagerMurthy Juluri DAZSI Functional Consultant

Santosh Pallera DAZSI Functional Consultant

Reference Documents

Sno Name Doc Name

Note To Holders:

If you receive an electronic copy of this document and print it out, please write your name on the equivalent of the cover page, for document control purposes.

If you receive a hard copy of this document, please write your name on the front cover, for document control purposes.


Contents

Interface Design..................................................................................................................................................................1

Solazyme EDI 810..............................................................................................................................................................1

Interface..............................................................................................................................................................................1

Document Control.............................................................................................................................................2Introduction.......................................................................................................................................................2

Purpose.......................................................................................................................................................................2

Functional Requirement/Business Need...........................................................................................................2Interface Assumptions.......................................................................................................................................2

Scope..........................................................................................................................................................................2

High Level Diagram..........................................................................................................................................2X12 EDI-Oracle EDI Column Mapping...........................................................................................................2

Header Fields..............................................................................................................................................................2

Custom Header Fields.................................................................................................................................................2

Line Fields..................................................................................................................................................................2

Custom Line Fields.....................................................................................................................................................2

Program Logic and Details................................................................................................................................2Custom API Logic......................................................................................................................................................2

Interface Program Modules...............................................................................................................................2Functional Setup................................................................................................................................................2Scheduling Autoinvoice Master Program.........................................................................................................2Open and Closed Issues for this Deliverable.....................................................................................................2

Open Issues.................................................................................................................................................................2

Closed Issues..............................................................................................................................................................2


Introduction

This interface design defines the key assumption, rules and logic that are needed to create the interface programs. The interface program code is not included in this document, but it contains program / module names for this interface. The interface design document is intended to provide the developer with the necessary information for writing interface accurate programs.

Distribute the Interface Program Design to:

developers who are responsible for writing the various pieces of interface code interface project staff client staff member responsible for signing off on the completeness of this program design overall project manager interface project manager

Use the following criteria to ensure the quality of this deliverable:

Is the interface data mapping complete? Are there any application setup decisions that have not been finalized which directly impact the data mapping and the accuracy of the interface code?

Are all of the rules which impact interface documented so that they can be written in the interface code? Is the program logic required to write the interface code documented?

PurposeThis Interface Program Design document describes the:

Key assumptions, scope, business rules and logic to be used by the interface program


Functional Requirement/Business Need

Solazyme requires an interface from Oracle to send the 810 EDI file from Sephora.

The 810 generated from Oracle will be sent to DiCentral for generating and transmitting the X12 810.


Interface Assumptions

The following are Oracle to SOLAZYME Interface assumptions:

R12.1.3 Oracle e-Commerce Gateway would be used to send the EDI 810 File. DiCentral will transform the X12/EDIFACT standards based EDI file sent by Oracle and transmit it to

the Trading Partner DiCentral will retrieve the Oracle 810 EDI File from DiCentral ftp site Custom programs will send the Oracle 810 EDI File from Oracle Server to DiCentral ftp Site

ScopeThe scope of this document is to identify the following to interface Oracle to Interface:

Highlight how EDI Files will interface with Oracle. Program Logic and Details of APIs involved in extraction Functional Setup


High Level Diagram

Below is the EDI interface diagram to Oracle 12.1.3


X12 EDI-Oracle EDI Column Mapping

Header Fields

Sno EDI Tag + Element#

Oracle Interface Column Record Number

Position DataType Comments

1 Communication_method 0010 101 Varchar2(2) Constant ‘ED’2 ISA15 Tp_test_flag 0010 103 Varchar2(1) Constant ‘T’ or ‘P’3 Document_type 0010 104 Varchar2(6) Constant ‘INO’4 Document_ID 0010 110 Varchar2(5) Constant ‘INV’5 ISA06 TP_Translator_Code 0010 152 Varchar2(30) Sender EDI ID

‘6507804777’6 ISA08 TP_Location_Code 0010 182 Varchar2(35) Sender EDI ID

‘6507804777’7 ISA09 Transaction_Date 0010 451 Date(15) Format ‘YYYYMMDD

HH24MMSS’8 Bill_to_customer_code_ext 1000 121 Varchar2(20) Partner ID9 N102 Bill_to_customer_name 1000 141 Varchar2(60) Customer Name10 N301 Bill_to_address1 1000 201 Varchar2(35) Bill To Address111 N302 Bill_to_address2 1000 236 Varchar2(35) Bill To Address112 N401 Bill_to_city 1000 341 Varchar2(30) Bill To City13 N402 Bill_to_postal_code 1000 371 Varchar2(15) Bill To Zip Code14 N404 Bill_to_country 1000 386 Varchar2(20) Bill To Country15 N403 Bill_To_state 1000 409 Varchar2(20) Bill To State16 Ship_to_customer_code_ext 1100 121 Varchar2(20) Ship To code17 N102 Ship_to_customer_name 1100 161 Varchar2(60) Ship To Customer Name18 N301 Ship_to_address1 1100 221 Varchar2(35) Ship to Address119 N302 Ship_to_address2 1100 256 Varchar2(35) Ship to Address220 N401 Ship_to_city 1100 361 Varchar2(30) Ship to City21 N402 Ship_to_postal_code 1100 391 Varchar2(15) Ship to postal code22 N404 Ship_to_country 1100 406 Varchar2(20) Ship to country23 N403 Ship_to_state 1100 429 Varchar2(20) Ship to state24 N102 Remit_to_customer_name 1300 121 Varchar2(60) Remit to name25 N301 Remit_to_address1 1300 141 Varchar2(35) Remit to address126 N302 Remit_to_address2 1300 201 Varchar2(35) Remit to address127 N401 Remit_to_city 1300 341 Varchar2(30) Remit to city28 N402 Remit_to_postal_code 1300 371 Varchar2(15) Remit to postal code29 N404 Remit_to_country 1300 386 Varchar2(20) Remit to country30 N403 Remit_to_state 1300 409 Varchar2(20) Remit to state31 BIG02 Transaction_number 2000 101 Varchar2(20) Invoice Number32 BIG03 Purchase_order_number 2000 196 Varchar2(50) PO Number33 BIG01 Purchase_order_date 2000 326 Date(15) PO Date34 BIG04 Inv_transaction_date 2000 356 Date(15) Invoice date35 TDS01 Total_amount_due 2000 401 Number(22) Total amount


Custom Header Fields




1 REF02 internal_vendor_no 2900 101 Varchar2(30) Vendor Number2 ITD01 terms_type_code 2900 131 Varchar2(30) Terms Code3 ITD02 terms_basis_type 2900 161 Varchar2(30) Terms Basis Code4 N104 for

N1*STbuyer_store_no 2900 191 Varchar2(30) Store Number at Line

Level5 SAC02 adjustment_code1 2900 221 Varchar2(30) SAC Code6 SAC07 adjustment_amt1 2900 251 Varchar2(30) SAC Amount7 SAC02 adjustment_code1 2900 281 Varchar2(30) SAC Code8 SAC07 adjustment_amt1 2900 311 Varchar2(30) SAC Amount9 total_no_lines 2900 341 Varchar2(30) Total Lines

Line Fields




1 IT101 Line_number 4000 101 Varchar2(20) Line Number2 Line_item_number 4000 145 Varchar2(50) Oracle Item number3 IT102 Quantity 4000 267 Varchar2(10) Quantity Invoiced4 IT103 Uom_code_ext1 4000 292 Varchar2(50) Unit of Measure5 Unit_selling_price 4000 319 Number(22) Unit selling pcie6 Invoice_line_type 4000 605 Varchar2(1) L for line, F for

freight7 PID05 Item_description 4010 218 Number(22) Item Desc

Custom Line Fields




1 IT107 upc_code 4900 101 Varchar2(30) Customer upc code2 IT104 retail_price 4900 131 Varchar2(30) Retail price


Program Logic and DetailsThis section describes the:

Custom API Logic

Custom API Logic

Procedure ECE_INO_X. POPULATE_EXTENSION_HEADER

in parameters

1. l_fkey Number

2. l_plsql_tbl ece_flatfile_pvt.Interface_tbl_type

out parameter

Logic

1. Fetch tp_attribute1, tp_attribute2, tp_attribute3, tp_attribute4, ordered_date from order header

2. fetch remit to name, price adjustment dffs

3. update the ece_ar_trx_headers_x extension table

4.

Procedure ECE_INO_X. POPULATE_EXTENSION_LINE

in parameters

1. l_fkey Number

2. l_plsql_tbl ece_flatfile_pvt.Interface_tbl_type

out parameter

Logic

1. Fetch upc_code, retail price from order line.

2. update the ece_ar_trx_lines_x extension table

Procedure xxsz_edi_ftp_pkg. Send_file

in parameters

1. File Path

2. File Name

out parameter

Logic

1. fetch connection details from XXSZ_DICENTRAL_DETAILS lookup type


2. connect to dicentral ftp site.

3. place the ALL_TP_INVOICES.txt file onto the remote ftp directory /out/810/

4. Archive the above file to /home/oracle/edi/out/archive directory

Alter table commands

alter table ec.ece_ar_trx_headers_x

add (internal_vendor_no VARCHAR2(240),

terms_type_code VARCHAR2(240),

terms_basis_type VARCHAR2(240),

buyer_store_no VARCHAR2(240),

adjustment_code1 VARCHAR2(240),

adjustment_amt1 NUMBER,

adjustment_code2 VARCHAR2(240),

adjustment_amt2 NUMBER,

total_no_lines number)

/

ALTER TABLE ec.ece_ar_trx_lines_x

ADD (upc_code VARCHAR2(240),

retail_price NUMBER)

Create Directory Command

o CREATE OR REPLACE DIRECTORY EDI_OUT_FILEPATH AS '/home/oracle/edi/out'

Insert Script for custom columns into INO Meta data

o For Headers

INSERT INTO ece_interface_columns(

interface_column_id,

interface_table_id,

interface_column_name,

table_name,

column_name,

record_number,

position,

width,

data_type,

conversion_sequence,


record_layout_code,

record_layout_qualifier,

conversion_group_id,

xref_category_allowed,

element_tag_name,

external_level,

map_id,

staging_column,

creation_date,

created_by,

last_update_date,

last_updated_by,

last_update_login)

SELECT

ece_interface_column_id_s.NEXTVAL,

(SELECT eit.interface_table_id

FROM ece_interface_tables eit,

ece_mappings em

WHERE em.map_code = 'EC_INO_FF' AND

eit.output_level = '1' AND

em.map_id = eit.map_id),

NULL,

NULL,

'INTERNAL_VENDOR_NO',

2900,

10,

30,

'VARCHAR2',

NULL,

'EX',

'EXT',

NULL,

'N',


NULL,

1,

(SELECT map_id FROM ece_mappings WHERE map_code = 'EC_INO_FF'),

'FIELD500',

SYSDATE,

1,

SYSDATE,

1,

1

FROM DUAL;



interface_table_id,


table_name,

column_name,

record_number,

position,

width,

data_type,


record_layout_code,




element_tag_name,

external_level,

map_id,

staging_column,

creation_date,

created_by,

last_update_date,


last_updated_by,

last_update_login)

SELECT




ece_mappings em




NULL,

NULL,

'TERMS_TYPE_CODE',

2900,

20,

30,

'VARCHAR2',

NULL,

'EX',

'EXT',

NULL,

'N',

NULL,

1,


'FIELD500',

SYSDATE,

1,

SYSDATE,

1,

1

FROM DUAL;




interface_table_id,


table_name,

column_name,

record_number,

position,

width,

data_type,


record_layout_code,




element_tag_name,

external_level,

map_id,

staging_column,

creation_date,

created_by,

last_update_date,

last_updated_by,

last_update_login)

SELECT




ece_mappings em




NULL,


NULL,

'TERMS_BASIS_TYPE',

2900,

30,

30,

'VARCHAR2',

NULL,

'EX',

'EXT',

NULL,

'N',

NULL,

1,


'FIELD500',

SYSDATE,

1,

SYSDATE,

1,

1

FROM DUAL;



interface_table_id,


table_name,

column_name,

record_number,

position,

width,

data_type,



record_layout_code,




element_tag_name,

external_level,

map_id,

staging_column,

creation_date,

created_by,

last_update_date,

last_updated_by,

last_update_login)

SELECT




ece_mappings em




NULL,

NULL,

'BUYER_STORE_NO',

2900,

40,

30,

'VARCHAR2',

NULL,

'EX',

'EXT',

NULL,

'N',


NULL,

1,


'FIELD500',

SYSDATE,

1,

SYSDATE,

1,

1

FROM DUAL;



interface_table_id,


table_name,

column_name,

record_number,

position,

width,

data_type,


record_layout_code,




element_tag_name,

external_level,

map_id,

staging_column,

creation_date,

created_by,

last_update_date,


last_updated_by,

last_update_login)

SELECT




ece_mappings em




NULL,

NULL,

'ADJUSTMENT_CODE1',

2900,

50,

30,

'VARCHAR2',

NULL,

'EX',

'EXT',

NULL,

'N',

NULL,

1,


'FIELD500',

SYSDATE,

1,

SYSDATE,

1,

1

FROM DUAL;




interface_table_id,


table_name,

column_name,

record_number,

position,

width,

data_type,


record_layout_code,




element_tag_name,

external_level,

map_id,

staging_column,

creation_date,

created_by,

last_update_date,

last_updated_by,

last_update_login)

SELECT




ece_mappings em





NULL,

NULL,

'ADJUSTMENT_AMT1',

2900,

60,

30,

'NUMBER',

NULL,

'EX',

'EXT',

NULL,

'N',

NULL,

1,


'FIELD500',

SYSDATE,

1,

SYSDATE,

1,

1

FROM DUAL;



interface_table_id,


table_name,

column_name,

record_number,

position,

width,


data_type,


record_layout_code,




element_tag_name,

external_level,

map_id,

staging_column,

creation_date,

created_by,

last_update_date,

last_updated_by,

last_update_login)

SELECT




ece_mappings em




NULL,

NULL,

'ADJUSTMENT_CODE2',

2900,

70,

30,

'VARCHAR2',

NULL,

'EX',

'EXT',


NULL,

'N',

NULL,

1,


'FIELD500',

SYSDATE,

1,

SYSDATE,

1,

1

FROM DUAL;



interface_table_id,


table_name,

column_name,

record_number,

position,

width,

data_type,


record_layout_code,




element_tag_name,

external_level,

map_id,

staging_column,


creation_date,

created_by,

last_update_date,

last_updated_by,

last_update_login)

SELECT




ece_mappings em




NULL,

NULL,

'ADJUSTMENT_AMT2',

2900,

80,

30,

'NUMBER',

NULL,

'EX',

'EXT',

NULL,

'N',

NULL,

1,


'FIELD500',

SYSDATE,

1,

SYSDATE,

1,


1

FROM DUAL;



interface_table_id,


table_name,

column_name,

record_number,

position,

width,

data_type,


record_layout_code,




element_tag_name,

external_level,

map_id,

staging_column,

creation_date,

created_by,

last_update_date,

last_updated_by,

last_update_login)

SELECT




ece_mappings em





NULL,

NULL,

'TOTAL_NO_LINES',

2900,

90,

22,

'NUMBER',

NULL,

'EX',

'EXT',

NULL,

'N',

NULL,

1,


'FIELD500',

SYSDATE,

1,

SYSDATE,

1,

1

FROM DUAL;

For Lines



interface_table_id,


table_name,

column_name,

record_number,


position,

width,

data_type,


record_layout_code,




element_tag_name,

external_level,

map_id,

staging_column,

creation_date,

created_by,

last_update_date,

last_updated_by,

last_update_login)

SELECT




ece_mappings em




NULL,

NULL,

'UPC_CODE',

4900,

10,

30,

'VARCHAR2',

NULL,


'EX',

'EXT',

NULL,

'N',

NULL,

4,


'FIELD500',

SYSDATE,

1,

SYSDATE,

1,

1

FROM DUAL;



interface_table_id,


table_name,

column_name,

record_number,

position,

width,

data_type,


record_layout_code,




element_tag_name,

external_level,

map_id,


staging_column,

creation_date,

created_by,

last_update_date,

last_updated_by,

last_update_login)

SELECT




ece_mappings em




NULL,

NULL,

'RETAIL_PRICE',

4900,

20,

22,

'NUMBER',

NULL,

'EX',

'EXT',

NULL,

'N',

NULL,

4,


'FIELD500',

SYSDATE,

1,

SYSDATE,


1,

1

FROM DUAL;


Interface Program ModulesThe following table lists each program created for the interface.

Program Type Program Name Description/Purpose Schema/Application

PACKAGE ECE_INO_X e-Commerce Gateway extension package for Invoice

APPs

PACKAGE xxsz_edi_ftp_pkg Package to Perform FTP operations APPS

CONCURRENT PROGRAM XXSZSNDFILE Program to receive files from ftp server XXSZ

REQUEST SET XXSZ810OUT Request Set for processing EDI files XXSZ


Functional Setup

Trading Partner Setup

Switch to e-Commerce Gateway Responsibility. Navigate to Setup=>Trading Partners Define the Trading Partner

Assign the Outbound 810 Transaction


Code Conversion Setup

Switch to e-Commerce Gateway Responsibility. Navigate to Setup=>Assign Code Conversion

Query the POI Map.1. Select Order Header

1. Assign ORDER_TYPE to ORDER_TYPE Conversion Code 2. Select Order Items

1. Assign CUSTOMER_ITEM_ID_TYPE to ITEM_TYPE Conversion Code3. Select Item Details

1. Assign ORDER_QUANTITY_UOM to UOM Conversion Code


Navigate to Setup=>Define Code Conversion Values

Miscellaneous

Define value for sending Email notifications for EDI Issues


Scheduling Autoinvoice Master ProgramCompletion of Autoinvoice Master Program is a prerequisite to generate EDI Invoices

The Autoinvoice master program will be run using a User called as SZUS Reports The password for this user is Solazyme.

The Person incharge of accounts receivable should log into the SZUS Reports user daily to verify the status of the request and see the execution report.

After review of execution report, User has to make sure that there exist no issues. If any issues exist then user has to resolve either by herself or can reach the OraHelp desk for resolution.

It is the Responsibility of the Accounts Receivable user to monitor the SZUS Reports Login.

Autoinvoice Scheduling:

The below Autoinvoice Master Program is scheduled only for Sephora.


Currently this program is scheduled to notify the above three employees of solazyme.

If any of the the employee is end dated it is the responsility of Solazyme IT help desk to add a new person.


Open and Closed Issues for this Deliverable

Open Issues

ID Issue Resolution Responsibility Target Date

Closed Issues

ID Issue Resolution Responsibility Target Date


solazyme edi 810 outbound process 1 0

Documents

interface programs

impact interface

interface program code

interface design document

interface program modules

interface design solazyme

solazyme interface assumptions

interface team memberssolazyme