EHSS Interface Specification(20080819 to client).doc
文本预览下载声明
Interface Specification for EHSS
EHSS Project
Version DRAFT
08/15/08
Author：Toddy Tu， George Cao Contents
1. Overview 3
1. Overview 3
2. Interface Signatures 3
2.1 New Product 3
2.1.1 Purpose 3
2.1.2 Usage Flow 3
2.1.3 Business Description 3
2.1.4 Access Flow 3
2.1.5 Web Service Parameters 3
2.2 Interface Two: Container Size 3
2.2.1 Purpose 3
2.2.2 Usage Flow 3
2.2.3 Access Flow 3
2.2.4 Web service Parameters 3
2.3 Bill of Lading Printing 3
2.3.1 Purpose 3
2.3.2 Usage Flow 3
2.3.3 Business Description 3
2.1.6 Access Flow 3
2.1.7 Web service Parameters 3
Overview
The diagram below provides a high-level infrastructure overview of the Dober system.
Simplified Interface List:
1) New Product
???????? JDE ? EHSS
2) Container Sizes
???????? EHSS ? JDE
3) Bill of Lading Printing
???????? JDE ? EHSS
The followings are fields and sample data for the interfaces:
IMITM IMLITM IMDSC1 IMDSC2 1001 000901-00 Bleach Bulk 1002 000901-01 Bleach 1 Gallon Pail 2312 000901-05 Bleach 55 Gallon Drum I
MITM: JDE primary key – system generated – Never displayed in EHSS
IMLITM:*******-**( *****for raw material, ******* for products, the latter 2 digits are container code.) – user defined
IMDSC1: Product name (text)
4. ???IMDSC2: Product description
For raw material the code is 5 characters in length (XXXXX)
For Finished goods the code is 6 characters in length followed by a “-“ then two characters for the package size (XXXXXX-XX)
Interface Signatures
2.1 New Product
Purpose
When JDE is creating a new product, it activates Trigger to call the interface to synchronically save the three fields value (IMITM, IMLITM, IMDSC1) into the EHSS table EHSS_CHMC.
Usage Flow
Business Description
The followings are our design for the business of the interface from JDE to EHSS.
We at present firstly assume the container code is defined and configured in EHSS;
We can get the product code and container code from the IMLITM from the
显示全部