Edi Autopro Documentation

Software Documentation

Software Documentation

EDI Documentation

DOC-1.5 EDI

QAD Proprietary

DOC-1.5 EDI As of 3/22/2005 of 34

März 22. 2005Project No: 10007 Name: AutoPro

Created By: Olivier Jalet Date Created: November 24, 2004

Modified By: Last Modified: March 22, 2005File: EDI Revision: 0.01

Product: AutoPro Total Pages: 34Version: 1.5 Date Approved {Enter Date}

Revision HistoryRev Effective Originator Reason for Change

0.01 Jalet Original version

QAD Proprietary

DOC-1.5 EDI As of 3/22/2005 of 34

Table of Contents

A. INTRODUCTION...........................................................................................................................................4

A.1 General Description / Business Context.......................................................................................................4A.2 Business Need Addressed.............................................................................................................................4

B. EDI FORMAT.................................................................................................................................................4

C. TRADING PARTNER....................................................................................................................................5

D. EDI GLOBAL..................................................................................................................................................8

D.1.1 General Global parameters......................................................................................................................8D.1.2 EDI file name parameters......................................................................................................................10D.1.3 Optional General EDI............................................................................................................................11

E. IMPORT.........................................................................................................................................................11

E.1 Generic Import EDI parameters......................................................................................................................11E.2 Generic CUM Calculation EDI parameters.....................................................................................................13E.3 VDA................................................................................................................................................................14

E.3.1 4905 (LT)...............................................................................................................................................14E.3.2 4915 (ST)...............................................................................................................................................15E.3.3 4913 (ASN)............................................................................................................................................16

E.4 EDIFACT........................................................................................................................................................16E.4.1 DELJIT 96A (ST)..................................................................................................................................16E.4.2 DELJIT 97A (ST/PUS)..........................................................................................................................18E.4.3 DELFOR 96A (LT)...............................................................................................................................18E.4.4 DELFOR 97A (LT)...............................................................................................................................19

E.5 ODETTE.........................................................................................................................................................20E.5.1 DELINS (LT).........................................................................................................................................20E.5.2 AVIEXP (ASN).....................................................................................................................................20

F. EXPORT........................................................................................................................................................21

F.1 Exp VDA.........................................................................................................................................................21F.1.1 Exp 4905 (LT).......................................................................................................................................21F.1.2 Exp 4915 (ST)........................................................................................................................................21F.1.3 Exp 4913 (ASN) v2.0............................................................................................................................21F.1.4 Exp 4913 (ASN) v3.0............................................................................................................................23

F.2 Exp EDIFACT.................................................................................................................................................27F.2.1 Exp DELJIT 96A (ST)...........................................................................................................................27F.2.2 Exp DELJIT 97A (ST/PUS)..................................................................................................................28F.2.3 Exp DELFOR 96A (LT)........................................................................................................................28F.2.4 Exp DELFOR 97A (LT)........................................................................................................................28F.2.5 Exp DESADV 96A (ASN)....................................................................................................................28F.2.6 Exp DESADV 97A (ASN)....................................................................................................................29

F.3 Exp ODETTE..................................................................................................................................................32F.3.1 Exp DELINS v2.0 and 3.0 (LT)............................................................................................................32F.3.2 Exp AVIEXP (ASN) v3.0......................................................................................................................33

QAD Proprietary

DOC-1.5 EDI As of 3/22/2005 of 34

A. Introduction

A.1 General Description / Business Context

This document intends to regroup the EDI import/export documentation describing the necessary setup for every case for both import and export EDI files.

A.2 Business Need Addressed

When speaking on EDI there is 3 main existing standards: VDA, ODETTE and EDIFACT. Each of them has their own “language” using tags to identify the record type. The purpose of this document is not to describe all the segments with all the possible values but to describe the mostly used.

B. EDI FORMATFirst of all, to be able to import an EDI format the system needs to be setup to accept it. To create a new EDI format or verify which format are setup in the system go under: Base/Attribute/Class Code. Select Class name “edi_msg_format” and menu: Members/Valid members. Now create new Member such as “VDA4913-2”. See example below…

QAD Proprietary

DOC-1.5 EDI As of 3/22/2005 of 34

C. TRADING PARTNERWhen the EDI file format are setup in the system, it is then necessary to define a trading

partner to tell to the system what to do when an EDI file is coming in.For example if a VDA 4905 file is coming into the “in” directory from the EDI import

process (see further to determine the directory). The system following the sender Id and receiver Id from the EDI file should be able to identify the associated customer it is addressed to.

To setup such an import, go under EDI/EDI Maintenance/EDI Maintenance. Under the tab partners create a new record.

QAD Proprietary

DOC-1.5 EDI As of 3/22/2005 of 34

QAD Proprietary

DOC-1.5 EDI As of 3/22/2005 of 34

The Import flag specifies that this is an import. The site specifies which site in concerned by the import. Then you have the choice between Supplier (to export schedule or import ASN), Customer (to export ASN or import Schedule) and groupage (usually used to export data).

The receiver Id and Sender Id are usually the key to identify if the message needs to be imported or exported. A sub Id can be also used (second field).

NAD fields are used only for EDIFACT purpose. Sometimes a customer may have a centralized system which sends the EDI file with the same receiver and Sender Ids. In that case an extra information contained in the EDI file is necessary (NAD fields). It is then necessary to setup mandatory NAD fields (those we are sure to find all the time in the EDI file) and for which the value identifies clearly the customer. For example NAD+CN:

If correctly setup the system may then load/export the EDI files. But sometimes it is not so easy because the way of working from some is different than the others. That’s why it is necessary for every EDI import/export to specify a certain number of EDI parameters. It is also necessary to

QAD Proprietary

DOC-1.5 EDI As of 3/22/2005 of 34

have created the necessary Sales Order header, shipping control and ship to (not described in this document).

D. EDI GLOBAL

D.1.1 General Global parametersThere are three levels of EDI Parameters:

– The first are the EDI_GLOBAL parameters. They are used in all EDI imports and EDI exports.

– The second are the EDI parameters linked to a Site. They are used in all imports and exports for that Site.

– The third are the EDI Parameters linked to an EDI Control record. That Parameters are used only for that import or export that is configured in the EDI control record.

In the program the Parameters are loaded in a temp table. That temp table is used in the code always when EDI parameters are used.

The EDI_GLOBAL Parameters are The first to be loaded. Then The EDI Parameters linked to a Site are loaded. If there are parameters with the same five keys field value as loaded EDI_GLOBAL parameters it will take the Site linked Parameter.Then The EDI Parameters linked to an EDI Control record are loaded. If there are parameters with the same five keys field value as loaded EDI parameters it will take the EDI Control linked Parameter.

In EDI imports the Site is not known when the file is received. The Site linked parameters and the EDI Control linked parameters can be used only after the first lines of the files are imported. Note that it is not possible to overwrite EDI_GLOBALS Parameters like INDIR (import directory) with Site linked Parameters. It is only possible for parameters Site is identified.

Some EDI parameters can be set globally to be applied automatically to all the import and export.

EDI Parameter Effect Why to use itINDIR EDI files are imported from the directory specified in value1 of that parameter.INHISTDIR Imported EDI files are moved into the directory specified in value1.

CTLDIR Value1 specifies the directory where log files and lock files are generated.FN_PATHNAME EDI files will be exported to the directory specified in that parameter.FN_TEMPPATHNAME

Temporary directory used to export EDI files. When process complete, moved to value1 of parameter FN_PATHNAME

OUTHIST Directory for exported files. SEVERITYLEVEL The EDI processes writes a messages to the logging Db. There are four kinds of

messages: DEBUG, INFO, WARNING, ERROR. Each message is sent with a severity level. In the parameter serevitylevel you can specifies minimum severity levels for that four message types. Only messages with a severity level greater than or equal to the specified level are written to the database.Value1 is the severity level for DEBUG, value2 for INFO, value3 for

QAD Proprietary

DOC-1.5 EDI As of 3/22/2005 of 34

WARNING, value4 for ERRORDEBUGLOG Value1 specifies the debug log filename. That filename will be extended with

the date. In that file are messages without taking in account the severity level.DEBUGLOG_DEBUGLOG_FILE_LOCK

When more than one EDI import process runs (also Appserver processes) they write message into the same debuglog file. With that parameter they will wait for each other. When setting up this parameter, the waiting processes write date and time and the appserver process id to another file. There is no lock mechanism for that second file. It is then possible to loose information.

CREATE_SPLITDAT In EDI files it is common not to find linefeeds. Setting up this parameter will create a file with linefeeds in the inhist directory. The filename of that file is the same of the imported file but with the extension “in”.

DIRECT_IMPORT The EDI import process use a temp table and splits it in a small messages and affect Appserver processes to import the message per small piece of message. This parameter avoids this process making the import process in only one step. That might be necessary if the import process uses too much system resources when importing an EDI file.

INPRIO Use in order to have two EDI import processes with two different import directories.

CHANGE_EDI_ID It is normally not possible to import files with the same format but different EDI Ids (receiver and sender Ids) for the same EDI Control (trading partner configuration). For instance it is not possible to set up twice a DELINS import for the same trading partner configuration. This parameter enables it.Set the parameter as

– Key2: tradingpartner_edi_id, – key3: tradingpartner_sub_id, – key4: JC_edi_id, – key5: JC_sub_id. – Value1: tradingpartner_edi_id, – value2: tradingpartner_sub_id, – value3: JC_edi_id, – value4: JC_sub_id.

PROG_TO_CALL Set up this parameter to call an alternate program to import or export messages. If no trading partner ID is specified in Key4, the application calls the program specified in Value1 for all trading partners.

– Key2: message format, – key3: program that calls the program specified in Value1– key4: tradingpartner_edi_id. – Value1: Alternate program

OPERATOR_ERRORLOG

Set up operators in this parameter as recipients for notifications from the EDI processes if errors occur. Multiple recipients can be set up and all will receive the e-mail notification.

– Value1: E-mail address for the operator– Value2: Operator name or the environment– Value4: Keyword for the message type: SMS, EMAIL. For SMS, the

message is only the e-mail subject.– Value5: Minimum security level for WARNING and ERROR messages.

If left blank, the EDI process also sends notifications for INFO messages.

QAD Proprietary

DOC-1.5 EDI As of 3/22/2005 of 34

SENDEREMAIL Set up the sender e-mail address of all e-mail messages generated by the EDI processes. If this parameter is not set up, the e-mail sender is always equal to the e-mail receiver.

SKIP_CALC_JIT Skip the JIT schedule calculation for better performances

Component plants usually don’t use the JIT schedule, so performance issues it would be interesting to set this parameter up.

L-NO-TRIM No trimming of customer part Id for every EDI is done.

Force the system not to remove the spaces before the customer part id. This is important when importing an EDI file because the system may not find the part. It is also important when exporting ASN as the spaces must remained as the customer needs to retrieve its own parts from the EDI file.

UOM-REPLACE-UOMId

Replace the UOM used at any SOD level by the value setup. Works only for ASN VDA 4913 export.

Usually the UOM setup for each SOD is EA (each). But when exporting an ASN to a german customer, he may require having ‘ST’ setup instead of ‘EA’.

D.1.2 EDI file name parameters

FN_DELIMITER In Value1 of this parameter, specifies the delimiter that separates the parts of the generated export file name. If you do not set up and link this parameter, it is created automatically by the export program.

FN_EXT In Value1 of this parameter, specifies the extension of the generated export file name. If you do not set up and link this parameter, it is created automatically by the export program.

FN_FILL In Value1 of this parameter, specifies the character that fills empty fields in the generated export file name. If you do not set up and link this parameter, it is created automatically by the export program.

FN_SHIPTOSIZE In Value1 of this parameter, specifies the length of the trading partner ID in the generated export file name. If you do not set up and link this parameter, it is created automatically by the export program.

FN_ORG In Value1 of this parameter, specifies the EDI standards organization ID in the generated export file name. If you do not set up and link this parameter, it is created automatically by the export program. Possible values are:

o V VDAo ODETTEo X XMLo E EBCDIXo I Inhouse

FN_MSGTYPE In Value1 of this parameter, specifies the message type ID in the generated export file name. If you do not set up and link this parameter, it is created automatically by the export program. Possible values are:

o A ASNo D Delivery scheduleo I Inhouse

QAD Proprietary

DOC-1.5 EDI As of 3/22/2005 of 34

FN_COUNTER In Value1 of this parameter, specifies the name of the application counter for a number in the generated export file name. If you do not set up and link this parameter, it is created automatically by the export program. You will not have to set up the counter itself because the export program creates the counter if it does not exist.

NB:Regarding the FN_COUNTER parameter, it creates automatically an Autopro counter. The current value and the increment value can be changed by the user through Base|Global Data|Counter.

D.1.3 Optional General EDI

SENDER When this parameter is set up, the file is always exported with the sender EDI ID specified in Value1 instead of the EDI ID specified in the EDI setup or the site setup.

SENDER_SUB When this parameter is set up, the file is always exported with the sender sub ID specified in Value1 instead of the sub ID specified in the EDI setup or the site setup.

RECEIVER When this parameter is set up, the file is always exported with the receiver EDI ID specified in Value1 instead of the EDI ID specified in the EDI setup.

RECEIVER_SUB When this parameter is set up, the file is always exported with the receiver sub ID specified in Value1 instead of the sub ID specified in the EDI setup.

NB:Usually those parameters don’t need to be setup as the sender and receiver Ids should come from the sender and receiver Ids setup at the EDI control record (trading partner).

E. Import When importing an EDI file, many customers and sales orders can be involved. Depending

on that, the user needs to setup EDI parameters to correctly split the requirements using a specific field such as dock code, plant code...The idea is to have a minimum of EDI parameters setup when only one Sales order is concerned by an EDI load.

E.1 Generic Import EDI parametersIGNORE_NULL_PO Set up this parameter to ignore customer purchase orders that contain only zeros

or blanks and do not create sales order details for them. If this parameter is not set up, only empty purchase orders are ignored.

USE_RELEASE_SEQUENCE

When this parameter is set up and a schedule with the same release ID is imported twice, the second schedule is created with an incremented release sequence. If this parameter is not set up, the second schedule release overwrites the first.

L-EDI-DOCK(used with VDA only)

When this parameter and EDI_DOCK_UPDATE are set up, the dock in the sales order detail is set to the value of this parameter. When EDI_DOCK_UPDATE is not set up, there is a warning message when the value of this parameter is different from the value of dock in the sales order detail.

QAD Proprietary

DOC-1.5 EDI As of 3/22/2005 of 34

Do not mix it with the EDI_DOCK parameter.EDI_DOCK_UPDATE

If this parameter and L_EDI_DOCK are both set up, the dock in the sales order detail is set to the value of L_EDI_DOCK. This parameter has no effect if L_EDI_DOCK is not set up.

UPDATE_ONLY_DOCK

Same as previous but for only one dock.

SCHEDULETIME If this parameter is set up, all bucket times are set to this time. The format is always hh:mm.

REQUIRED_EQ_SHIPPED

If this parameter is set up, the Cum Required Quantity of the schedule is set to the Shipped Quantity of the sales order detail.

SHIPPED_EQ_ REQUIRED

If this parameter is set up, the Shipped Quantity of the sales order detail is set equal to the Cum Required Quantity of the schedule.

DELETE_IF_ERROR_IN_REIMPORT

When this parameter is set up and there is an error when re-importing a schedule that was successfully imported before, the program deletes the first schedule.

Warning Use caution with this parameter. After the schedule is deleted, there is no current schedule for the sales order detail and a newly imported schedule will not be the same version as the one that was deleted.

L-RENAULT This parameter copies all buckets—from Prior Cum Required Date to Start Date of the current imported schedule—from the last schedule to the current imported schedule. Only works with DELINS, DELJIT and DELFOR.

L-RENAULT-PLUS Maintain forecast details from current schedule.Same concept that l-renault but keep the info of the post period concerned by the incoming schedule. (usually the L-renault and L-renault-plus params are combined)

L-BUCK-W-D This parameter changes all imported week buckets today buckets.SOD_CREATE(GLOBAL or LOCAL)

Allow the automatic Sales Order Details (SOD) creation for every import for missing sales order details.In some cases it is better no to setup this parameter as the user may want to keep the control of the SOD creation for some customers. Then it is possible to create this parameter as a generic EDI parameter and assign it to the desired customers.

IGNORE_DOCK_CODEp-cum-req When schedule type is ST, calculate the new prior received quantity following

the previous release Id from the schedule and check if it’s equal with the one coming from the EDI file.

s-cum-req When Schedule type is LT, calculate the new prior received quantity following the previous release Id from the schedule and check if it’s equal with the one coming from the EDI file.

l-cum-recp When Schedule type is ST, set prior cum required quantity equal the last receipt cum quantity.

l-cum-recs When Schedule type is LT, set prior cum required quantity equal the last receipt cum quantity.

l-cum-pup For DELINS and DELFOR, so_cum_acct Check if a prior cum required date or quantity is available otherwise generate an

error message.ship_dlvy_pattern_code

When the ship delivery pattern code setup as value1 is used in the EDI file, an error message is generated.

QAD Proprietary

DOC-1.5 EDI As of 3/22/2005 of 34

IGNORE_CUSTPART_BEGINS

Ignore the part with Id beginning by an element from the list setup in value1.

MULTIPLE_SITE When the SOD is not found, and the MULTIPLE_SITE setup, the system will try to find a match with another site.

SINGLE_PO If a Sales Order details already exist for the customer part Id but a different Purchase Order reference, the system does not import/create the schedule and generate an error message.

l-caldel Load the Kanban info from the EDI file into the schedule.L-FIAT Specific parameter pour FIAT.USE_RELEASE_SEQUENCESKIP_CALC_SUPPLIER

Avoid launching the calculation for supplier schedule when importing an EDI file.

SKIP_CALC_SHIPPER

Avoid launching the calculation for receiving schedule when importing an EDI file

SKIP_CALC_PROD Avoid launching the calculation for production schedule when importing an EDI file

SKIP_CALC_JIT Avoid launching the calculation for JIT schedule when importing an EDI file.IGNORE_IMPORT Ignore any import with the combination sender and receiver SSID, SFID defined

as followedKey2=sender Id (SSID)Key3=sender sub (SFID)Key4=Receiver Id (SSID)Key5= Receiver sub (SFID)

CHANGE_EDI_ID Any import with the combination SSIDs, SFIDs defined as followedKey2=sender Id (SSID)Key3=sender sub (SFID)Key4=Receiver Id (SSID)Key5= Receiver sub (SFID)Will be changed using the following values:Value1=sender Id (SSID)Value2=sender sub (SFID)Value3=Receiver Id (SSID)Value4= Receiver sub (SFID)So when you have to import 2 EDI files having different SSID/SFID for the same kind of message for the same entity (customer or supplier), you only need to setup one EDI Trading partner record and this EDI global parameter.

E.2 Generic CUM Calculation EDI parameters

Parameter Description Param Key Param Value Use Description

QAD Proprietary

DOC-1.5 EDI As of 3/22/2005 of 34

Schedule import – Get

prev requirements

from the “middle”

l-renault-

middle

<blank> =

Always

LT = Long

Term

ST = Short

term

To use when user wants to

maintain the requirements from the

previous active release with date

between the new ones incoming.

(*)

Schedule import – Get

“All” requirements

from prev release.

l-renault-all <number of

days> like

for

“l-renault”

This is to simplify. It is the same

as use “l-renault”, “l-renault-plus”

& “l-renault-middle” all together

Schedule Import –

Calculate Cum Qty

Calc_prior_cu

m

When NO “Cum quantity”

information arrives in the message,

the process calculates it basis on

the previous release. It takes the

“prior cum quantity” and adds all

the “Daily” and “Firm”

requirements till today (or today -

<days indicate in l-renault or l-

renault-all params>) (**)

E.3 VDA

E.3.1 4905 (LT)

QAD Proprietary

DOC-1.5 EDI As of 3/22/2005 of 34

EDI Parameter Effect Why to use itMULTIPLE_CUSTOMER

Allow the system to split the requirement with the USE_SO parameter

When requirements come from the same EDI file to different customers, you need to split them using a criteria (dock code or plant code)

USE_SO When MULTIPLE_CUSTOMER setup (has no effect alone), allow the system to split the requirement against the customer plant code (key2) to a specific SO header (value1). Plant code info can be found in the segment 552 or 512 pos 6–8

When more that 1 SO is concerned by an EDI load and that the key is the plant code.

L3P_DOCK When MULTIPLE_CUSTOMER setup (has no effect alone), allow the system to split the requirement against the dock code (key2) to a specific SO header (value1). Plant code info can be found in the segment 552 or 512 pos 6–8.Possible value can be ALL if more than 1 Sales order Header belong to a same customer but only one is concerned by a specific EDI import.

vda4905-shipto-dock Set the trading partner ship to shipto Id + dock code value.

vda4905-customer-shipto-dock

If setup and not null, replaced the vda4905-shipto-dock value by the value setup in value1

l-def-po Overwrite the PO reference from the EDI file.

l-ford-level NOT USED.l-mon-datel-cummul Force the system to take in account

only the past due date into the calculation of the cums.

l-cummul-ship NOT USEDl-def-int Set the bucket to W or M following

calculation.l-load-cuml-for-po NOT USEDEDI_DOCK Import the dock code from the EDI

file into the customer schedule.Not necessary as it is imported automatically.

E.3.2 4915 (ST)

EDI Parameter Effect Why to use itMULTIPLE_CUSTOME Allow the system to split the When requirements come from the

QAD Proprietary

DOC-1.5 EDI As of 3/22/2005 of 34

R requirement with the USE_SO parameter

same EDI file to different customers, you need to split them using a criteria (dock code or plant code)

USE_SO When MULTIPLE_CUSTOMER setup (has no effect alone), allow the system to split the requirement against the customer plant code (key2) to a specific SO header (value1). Plant code info can be found in the segment 552 or 512 pos 6–8


L3P_DOCK When MULTIPLE_CUSTOMER setup (has no effect alone), allow the system to split the requirement against the dock code (key2) to a specific SO header (value1). Plant code info can be found in the segment 552 or 512 pos 6–8.Possible value can be ALL if more than 1 Sales order Header belong to a same customer but only one is concerned by a specific EDI import.

l-def-po Overwrite the PO reference from the EDI file.

l-ford-level NOT USED.l-mon-date NOT USED.l-cummul NOT USED.l-cummul-ship Force the system to take in account

only the past due date into the calculation of the cums.

l-def-int NOT USEDl-load-cum When VDA period is 333333 or

444444, when setup to YES, ??? l-for-po NOT USED

E.3.3 4913 (ASN)

EDI Parameter EffectCONFIRMED. If this parameter is set up, the shipper is imported as a confirmed

shipper.

CUSTOMER_BOL_ID If this parameter is set up, the customer bill of lading ID of the file is used as BOL ID and MBOL ID in the application

CUSTOMER_BOL_ID_PREFIX

If this parameter is set up, the value is a prefix of the BOL ID and MBOL ID of the imported shipper.

use_po Select the PO Header to use fro the import, defined in value1 when the value from the segment l-csg-3921 is equal to the key1.

QAD Proprietary

DOC-1.5 EDI As of 3/22/2005 of 34

DUMMY_LOCATION Combined with the param LOCATION_HEAD. It forces the system to set the location header Id to the one setup in LOCATION_HEAD.If not setup, location Id is set to “stock”

USE-VENDOR-PART When set to YES or TRUE, retrieve the Supplier item number from the PO.

l-coverrec Retrieve the components of the received part. CONFIRM_RECEIVER When a record is setup in the Jack table CREATE_SHIPPER Combined with CONFIRM_RECEIVER, set to yes, allow the receiver

creationCONFIRM_SHIPPER Combined with CONFIRM_RECEIVER, set to yes, allow the receiver to

be confirmed automatically

E.4 EDIFACT

E.4.1 DELJIT 96A (ST)

EDI Parameter Effect Why to use itL3P_LOGISTIC Allow the system to split the

requirement by dock code.USE_SO When L3P_LOGISTIC setup (has no

effect alone), allow the system to split the requirement against the customer plant code (key2) to a specific SO header (value1). Plant code info can be found in the segment NAD+ST


L3P_DOCK When L3P_LOGISTIC setup (has no effect alone), allow the system to split the requirement against the dock code (key2) to a specific SO header (value1). Plant code info can be found in the segment LOC+11.Possible value can be ALL if more than 1 Sales order Header belong to a same customer but only one is concerned by a specific EDI import.

REQUIRED_EQ_SHIPPED Set CUM Required = Shipped when importing

When the customers don’t work with cums.

SHIPPED_EQ_REQUIRED Set CUM Shipped = Required when importing

L-RENAULT copies dates from today to future from the last schedule to the new one

When the customer sends first a forecast for 2 weeks and then send another forecast for the 2nd week only, usually the system replace the current schedule and lost the forecast for the 1st week. With this parameter, the current

QAD Proprietary

DOC-1.5 EDI As of 3/22/2005 of 34

schedule is modified and keeps the info from the 1st week.

L-RENAULT-PLUS maintain forecast details from current schedule

Same concept that l-renault but keep the info of the post period concerned by the incoming schedule. (usually the L-renault and L-renault-plus params are combined)

ENDSEGMENT First segment after last item, possible values:

– ZZZ: no specific segment– UNS– UNZ

When the data are not sent using the standard way.

FIRSTSEGMENT First segment per item, possible values:

– UNB– LIN– UNH

Idem.

NO-SCC There is no SCC segment on delfor filel-caldel Load the Kanban info from the EDI

file into the schedule.

E.4.2 DELJIT 97A (ST/PUS)

EDI Parameter Effect Why to use it

E.4.3 DELFOR 96A (LT)





L3P_DOCK When L3P_LOGISTIC setup (has no effect alone), allow the system to split the requirement against the dock code (key2) to a specific SO header (value1). Plant code info can be found in the segment LOC+11.Possible value can be ALL if more

QAD Proprietary

DOC-1.5 EDI As of 3/22/2005 of 34

than 1 Sales order Header belong to a same customer but only one is concerned by a specific EDI import.

REQUIRED_EQ_SHIPPED

Set CUM Required = Shipped when importing


SHIPPED_EQ_REQUIRED

Set CUM Shipped = Required when importing


When the customer sends first a forecast for 2 weeks and then send another forecast for the 2nd week only, usually the system replace the current schedule and lost the forecast for the 1st week. With this parameter, the current schedule is modified and keeps the info from the 1st week.








Idem.

NO-SCC There is no SCC segment on delfor file

l-def-pol-cum-pupl-cum-supl-cum-recpl-cum-recsl-for-pol-periodl-longterml-shorttermp-cum-reqs-cum-req

QAD Proprietary

DOC-1.5 EDI As of 3/22/2005 of 34

E.4.4 DELFOR 97A (LT)





L3P_DOCK When L3P_LOGISTIC setup (has no effect alone), allow the system to split the requirement against the dock code (key2) to a specific SO header (value1). Plant code info can be found in the segment LOC+11.Possible value can be ALL if more than 1 Sales order Header belong to a same customer but only one is concerned by a specific EDI import.

L3P_DOCK Specifies for which dock code (key2 must be equal to the value of the segment LOC+11) the SO Header (value1) to use to import the schedule into the correct Sales Order Header.

REQUIRED_EQ_SHIPPED

Set CUM Required = Shipped when importing


SHIPPED_EQ_REQUIRED

Set CUM Shipped = Required when importing


When the customer sends first a forecast for 2 weeks and then send another forecast for the 2nd week only, usually the system replace the current schedule and lost the forecast for the 1st week. With this parameter, the current schedule is modified and keeps the info from the 1st week.






QAD Proprietary

DOC-1.5 EDI As of 3/22/2005 of 34



Idem.

NO-SCC There is no SCC segment on delfor file

E.5 ODETTE

E.5.1 DELINS (LT)

EDI Parameter Effect Why to use it

E.5.2 AVIEXP (ASN)

EDI Parameter EffectAVIEXP_EDI_ID When created Ship from is initialized to the value from the CDT

segment value.l-item-chg NOT USED.l-coverrec NOT USED.USE-SELLER-PART-ID When set to YES or TRUE, the system uses the Sellers Article No,

else uses the Buyers Article No. MULTIPLE_TCO_QTY When created, allow the system to accept more than one quantity of

Articles in Pack.ASN_EMAIL_ACKN + pod_nbr Send an acknowledgment by email.AVIEXP_CONT_ID_COUNTER

Specifies the receiver counter to use for this supplier.

UNH-0062 Specifies the container counter to use for this supplier. (automatically created if not existing)

UNH-0020 Specifies the tag counter to use for this supplier. (automatically created if not existing)

use_po Select the PO Header to use fro the import, defined in value1 when the value from the segment l-csg-3921 is equal to the key1.

F. Export

F.1 General Export

EDI Parameter GLOBAL

Effect

QAD Proprietary

DOC-1.5 EDI As of 3/22/2005 of 34

USE_FORMAT_ + Sales Order Reference

yes When an ASN export is already setup for a customer, it is possible to setup another format to use for a specific Sales Order. Note: the EDI parameters for that message type need to be setup at the same level that the default one.Value1= new format to useValue2 = sender Id (SSID)Value3 = sender sub (SFID)Value4 = Receiver Id (SSID)Value5 = Receiver sub (SFID)

MFG_INTERFACE_ONLY_ + Sales Order Reference

no Put a tag MFGONLY in the name of the exported ASN file name. Used when the user does not want to send ASN directly to the customer but need to export an ASN for the financial system.

EDI_GROUPAGE_ID No Put an EDI Groupage Id from the value1 into the EDI file name.

VEHICLE_ID No Use to replace the Vehicle Id from the BOL.NO_RECEIVER_EXPORT No

F.2 Exp VDA

F.2.1 Exp 4913 (ASN) v2.0The version 2.0 is an old version used for example by JCI Madrid.

EDI Parameter Effect Why to use itCreatesetup[GLOBAL or not]

Create automatic EDI parameters (beginning with fn_...) for the customer export such as customer ASN counter, customer ASN file name, …

Used to avoid waste of time setting up the system. The most important one is that it creates automatically the ASN transmission counter for this customer. Formerly used for generic ASN export, some of these automatic parameters are not used for VDA (described later).

l-711-trs-counterValue customerId_fn_counter

Used to export the transmission nbr in the ASN (seg 711 Pos. 24 & 29)

This parameter used the counter automatically created by “createsetup”. It has to be defined as the fn_counter (automatically created by createsetup) EDI param is not used by VDA.

l-712-effectiveDate Change the value of the “Shipped date & time” segment 712 Pos. 31 & 37 (Carrier delivery date & time)

l-712-Prepayment Export the prepayment of

QAD Proprietary

DOC-1.5 EDI As of 3/22/2005 of 34

freight value setup, in the 712 segment pos 55.

l-712-warehouse Export the customer location value setup, in the 712 segment pos 70

UOM-DEFAULT Specifies the default UOM to use when the UOM is not setup at the SOD level.

UOM-REPLACE-UOMId Replace the UOM used at any SOD level by the value setup

Usually the UOM setup for each SOD is EA (each). This can not be changed because programs work with EA. But when exporting an ASN to a German customer, he may require having ‘ST’ setup instead of ‘EA’.

l-713-Type-Dispatch Export the type of dispatch value setup, in the 713 segment pos 25

CUSTOMER_PLANT Export the customer plant value in the segment 713 pos 49

For the customer it is necessary to know which plant is concerned as nowadays the EDI import process is more and more centralized.

Praeferenz-Status Change the default value for the preference status segment 714 pos 115.

4913ContLevel Used for specific export following the defined value:

– GroupSord: group by item id on 1 line segment 714

– PCKH: export the package header Id into the segment 715??

The customer may request to get the Item grouped on 1 line.

L-715-Pallet Export the pallet details into a new 715

A 715 is always exported for each box/container. Some customers require the pallet detailed. As a result you have two 715 segment records.

l-712-effectiveDate If the value of this parameter is set to “effective” then the carrier date and time values are set to the ASN sent date and time.

l-712-bruttoweight When the l-712-warehouse parameter is setup, then the gross weight of the BOL is replaced by the fixed value from the l-712-bruttoweight value1.

QAD Proprietary

DOC-1.5 EDI As of 3/22/2005 of 34

REPLACE_DOCK_ + shipto Id Replace any dock code from a specific ship to Id by the one setup in the value1.

l-713-Customer-Store Set a specific customer location at the segment 713.

713_PO_REFERENCE_FROM_SOH

When set to NO or FALSE, replace the PO reference (segment 713 pos 31-42) coming from normally the SO details, by the Sales Order Reference.

CREATE718 When setup to YES or TRUE, create the 718 segment (not mandatory).

712_nett_weigth_zero_as_space When Net weight is equal to 0, and the param setup to YES or TRUE, put spaces instead of zero.

BOLID_CUT_FROM_RIGHT Force the system to cut the BOL Id when its size is greater than 8 characters.

MOVE_BOLID_TO_DOC_NBR The BOL Id is moved from 713 pos 6 to pos 110

Because its length is suppose to be greater than 9 characters.

F.2.2 Exp 4913 (ASN) v3.0

EDI Parameter Effect Why to use itCreatesetup[GLOBAL or not]

Create automatic EDI parameters (beginning with fn_...) for the customer export such as customer ASN counter, customer ASN file name, …

Used to avoid waste of time setting up the system. The most important one is that it creates automatically the ASN transmission counter for this customer. Formerly used for generic ASN export, some of these automatic parameters are not used for VDA (described later).

l-711-trs-counterValue customerId_fn_counter

Used to export the transmission nbr in the ASN (seg 711 Pos. 24 & 29)

This parameter used the counter automatically created by “createsetup”. It has to be defined as the fn_counter (automatically created by createsetup) EDI param is not used by VDA.

l-712-effectiveDate Change the value of the “Shipped date & time” segment 712 Pos. 31 & 37 (Carrier delivery date & time)

l-712-Prepayment Export the prepayment of freight value setup, in the 712 segment pos 55.

l-712-warehouse Export the customer location value setup, in the 712 segment pos 70

QAD Proprietary

DOC-1.5 EDI As of 3/22/2005 of 34

UOM-REPLACE-UOMId Replace the UOM used at any SOD level by the value setup

Usually the UOM setup for each SOD is EA (each). But when exporting an ASN to a german customer, he may require having ‘ST’ setup instead of ‘EA’.

l-713-Type-Dispatch Export the type of dispatch value setup, in the 713 segment pos 25

CUSTOMER_PLANT Export the customer plant value in the segment 713 pos 49

For the customer it is necessary to know which plant is concerned as nowadays the EDI import process is more and more centralized.

Praeferenz-Status Change the default value for the preference status segment 714 pos 115.

4913ContLevel Used for specific export following the defined value:

– GroupSord: group by item id on 1 line segment 714

– PCKH: export the package header Id into the segment 715??

The customer may request to get the Item grouped on 1 line.

L-715-Pallet Export the pallet details into a new 715

A 715 is always exported for each box/container. Some customers require the pallet detail. As a result you have two 715 segment records created, one for the box, one for the pallet.

l-712-effectiveDate If the value of this parameter is set to “effective” then the carrier date and time values are set to the ASN sent date and time.

l-712-bruttoweight When the l-712-warehouse parameter is setup, then the gross weight of the BOL is replaced by the fixed value from the l-712-bruttoweight value1.

REPLACE_DOCK_ + shipto Id

Replace any dock code from a specific ship to Id by the one setup in the value1.

l-713-Customer-Store Set a specific customer location at the segment 713 pos 70-76.

713_PO_REFERENCE_FROM_SOH

When set to NO or FALSE, replace the PO reference (segment 713 pos 31-42) coming from normally the SO details, by the Sales Order Reference.

CREATE718 When setup to YES or TRUE, create the 718 segment (not mandatory).

712_nett_weigth_zero_as_space

When Net weight is equal to 0, and

QAD Proprietary

DOC-1.5 EDI As of 3/22/2005 of 34

the param setup to YES or TRUE, put spaces instead of zero.

MFG_INTERFACE_ONLY_ + Sales order Ref

Put a tag MFGONLY in the name of the exported ASN file

Used when the user does not want to send ASN directly to the customer but need to export an ASN for the financial system.

F.2.2.1 EXTRA SETUPTo export some data like the CARRIER info, you need to define a carrier address usage at the ship to Id or at the MBOL level.To be able to add any address type to a ship to or Master BOL: Base|Attribute|class codeAdd the CARRIER member to the class addess_type.

Then Add the SHMHBOLH and SOMHBOLH members to the class address Usage.

QAD Proprietary

DOC-1.5 EDI As of 3/22/2005 of 34

Then you’ll be able to add a CARRIER address to a ship to (SHIP-RECEIVE|Shipping setup|Ship To)

QAD Proprietary

DOC-1.5 EDI As of 3/22/2005 of 34

Idem for the Master BOL through SHIP-RECEIVE|Master Bill Of Lading:

F.3 Exp EDIFACT

F.3.1 Exp DESADV 96A (ASN)

EDI Parameter Effect Why to use itCAL_LOGISTIC Identifies Customer working with

“CALDEL” (like PSA)Export Kanban reference

QUAL_GROSS-WEIGHT Define the qualifier for the Gross Weight and export it. Possible values:

– AADQUAL_CAR-REF Define/export the qualifier for the

Conveyance tte Nbr. Possible values:– CRN

QUAL_Supplier-ident Define/export the qualifier for the Seller/Supplier NAD segment. Possible values:

– SEQUAL_Ship-To-ident Define/export the qualifier for the

Shipto/Consignee NAD segment. Possible values:

– CNQUAL_NAD-agency-CN Define/export the Code list responsible

Agency for “Consignee”, possible values:– 5: used only by PSA– 10

QUAL_NAD-agency-CZ Define/export the Code list responsible Agency for “Consignor”, possible values:

– 10QUAL_NAD-agency-SE Define/export the Code list responsible

Agency for “Seller” , possible values:– 10

QUAL_package-ref To Define/export Pallet label”, possible values:

– AAT

QAD Proprietary

DOC-1.5 EDI As of 3/22/2005 of 34

QUAL_QTY-pack Define the “quantity per pack”. The value depends on the packaging.

NO_DUNS_EXPORT To avoid “Extra” NAD segments exportPIA To Define/export PIA segmentDESADV_IMD To Define/export IMD segmentDESADV_ALI_DET To Define/export ALI (Country of

Origin)L3P_LOGISTIC Identifies Customer working with

“L3P/GPI” (Renault…)To export specific data to that kind of customers.

DESADV_ALI_HEAD To Display ALI +++ 67’ (Header segment)

DESADV_PACK_PALLET Includes the segment PAC for each Pallet in PAC loop

DESADV_PALLET_MEA Includes the segment MEA for each Pallet in PAC loop. Possible values:

– GDESADV_NO_DESPATCH_DTM

To avoid DTM containing the Despatch date

DESADV_NO_PCE_MEA To avoid a MEA segment with the total qty of PCEs

DESADV_NO_MBOL_RFF To avoid segment RFF with MBOL codeDESADV_NAD_CZ To put NAD segment with consignor

codeDESADV_RFF_ADE To put RFF segmentwith “Internal

Supplier code”DESADV_DETAIL_BY_ITEM

To display the Item & pack data in the right way

F.3.2 Exp DESADV 97A (ASN)

EDI Parameter Effect Why to use itQUAL_inner-pack-level Specifies to change the default

Qualifier for the inner pack level, segment: If not setup exported value “1”

QUAL_none-pack-level If not setup exported value “4”QUAL_outer-pack-level If not setup exported value “3”QUAL_buyers-item If not setup exported value “IN”QUAL_cumulative-quantity If not setup exported value “3”QUAL_package-ref If not setup exported value “CW”QUAL_carrier-ref If not setup exported value “CN”QUAL_seal-ref If not setup exported value “SN”QUAL_Container-ident If not setup exported value “CN”QUAL_Railcar-ident If not setup exported value “RR”QUAL_Trailer-ident If not setup exported value “TE”QUAL_doc-ident Specifies to change the default

Qualifier for the Dock code

QAD Proprietary

DOC-1.5 EDI As of 3/22/2005 of 34

segment (LOC). If not setup exported value “11”

QUAL_Material-issuer To Specify the qualifier of the NAD+MI segment.If not setup exported value “MI”

NOT USED

QUAL_Ship-To-ident If not setup exported value “ST”QUAL_Supplier-ident If not setup exported value “SU”QUAL_Ordered-by-ident If not setup exported value “OB”QUAL_despatch-quantity If not setup exported value “12”QUAL_CAR-REF If not setup exported value “CN”QUAL_MBOL-NR If not setup exported value “MB”QUAL_MSG_DATE-TIME If not setup exported value “137”QUAL_DESPATCH_DATE-TIME

If not setup exported value “11”

QUAL_ARRIVAL_DATE-TIME

If not setup exported value “132”

QUAL_GROSS-WEIGHT If not setup exported value “G”QUAL_NET-WEIGHT If not setup exported value “N”QUAL_NUM-UNITS If not setup exported value “SQ”QUAL_Consignment-measurements

If not setup exported value “AAX”

QUAL_UNH-ident-nbr If not setup exported value “A0105”

QUAL_BGM-msg-type If not setup exported value “351”QUAL_NAD-consignor If not setup exported value “CZ”QUAL_GIR-buyer-ref If not setup exported value “BU”QUAL_NAD-agency-CN If not setup exported value “92”QUAL_NAD-agency-CZ If not setup exported value “92”QUAL_NAD-agency-SE If not setup exported value “92”QUAL_PIA-Supp-item If not setup exported value “SA”QUAL_PIA-Dessign-rev If not setup exported value “DR”QUAL_QTY-pack If not setup exported value “52”CAL_LOGISTIC Identifies Customer working with

“CALDEL” (like PSA)Export Kanban reference

L3P_LOGISTIC Identifies Customer working with the “L3P” logistic (like Renault)

DESADV_BOL_ID The Bol Id is then exported in the BGM segment.

BGM-4-1 Function to link to that message, such as BGO, ... If not setup exported value “9”

DESADV_NO_DESPATCH_DTM

When CAL_LOGISTIC, L3P_LOGISTIC or this parameter is setup, the DTM segment regarding the dispatch time (shipped time) is exported.

QAD Proprietary

DOC-1.5 EDI As of 3/22/2005 of 34

DESADV_ALI_HEAD Used to export any value in the ALI segment of the header, or replace the ALI segment if the parameter value begins with “ALI”.If empty then ALI+++67 is exported.If not defined nothing is exported.

DESADV_NO_PCE_MEA To avoid to export the MEA+AAX segment.

DESADV_NO_MBOL_RFF Avoid to export an extra “RFF+MB” segment with the BOL id exported.

EXPORT_MBOL_ID If DESADV_NO_MBOL_RFF is not setup, then the value of this parameter is exported in the RFF segment.If this param is not setup then the BOL id is exported.

NO_DUNS_EXPORT Do not export the NAD segments.DESADV_NAD_CZ To export the consignee segment

(NAD+CZ or qualifier definer upper)

DESADV_RFF_ADE To export Supplier segment (RFF+ADE)

DESADV_TOD Export the TOD segment with the Fob point value.

FIRST_TDT-2-1FIRST_TDT-4-1FIRST_TDT-6-3FIRST_TDT-8-1FIRST_TDT-8-2

Values exported in the first TDT segment

SECOND_TDT-2-1SECOND _TDT-4-1SECOND _TDT-6-3SECOND _TDT-8-1SECOND _TDT-8-2

Values exported in the second TDT segment

DESADV_DETAIL_BY_ITEM

To export every details for each item.If not setup, then not all details are exported.

DESADV_PALLET_MEA To export extra MEA for the pallet info and if not empty, overwrite the qualifier value of the MEA segment for the Pallet gross weight.

QAD Proprietary

DOC-1.5 EDI As of 3/22/2005 of 34

PCI To specify the value to be exported in the PCI segment (default 16).

GIR To export the GIR segmentPIA To export the PIA segmentDESADV_IMD To Define/export IMD segment

CUMM_SHIPPED_UM To Define the cum shipped unit of measure (default is C62) in the QTY segments.

QUAL_order-number Specifies the qualifier in the RFF segment (default is ON) to export the PO reference by item.

DESADV_PAC_PALLET When DESADV_DETAIL_BY_ITEM is setup and not empty export the pallet detail for each item

UNB_APPLICATION Specifies the action value in segment UNB

DESADV_NAD_MI Specifies the Material Issuer Id (segment NAD+MI)

DESADV_NAD_SU Specifies the Supplier Id (segment NAD+SU)

F.4 Exp ODETTE

F.4.1 Exp DELINS v2.0 and 3.0 (LT)

EDI Parameter Effect Why to use itreceiver_sub Reset the sub receiver Id If no value is setup for the sub

receiver Id in the EDI partner control record, then the system pick the default one from the site. In order NOT to export this field, just create this EDI parameter with a blank value.

sender_sub Reset the sub sender Id If no value is setup for the sub sender Id in the EDI partner control record, then the system pick the default one from the site. In order NOT to export this field, just create this EDI parameter with a blank value.

one-msg-per-sched Create one message per schedulel-mult-pdn Works with l-unb-0026l-unb-0026 Specifies an additional comment to process that

file (from the supplier point of view) to be exported in the header (last field of the header).

QAD Proprietary

DOC-1.5 EDI As of 3/22/2005 of 34

l-item-status To export only Item having this status.l-unh-0054-skip Avoid to export the UNH 0054 segmentl-del-past-due If equal to YES, export the DEL segment with

past due date at the header.del-past-due Same as above but for each line. UNB_0004 Used to Specifies the UNH-0020 Specifies the tag counter to use for this supplier. (automatically created if not

existing)UNH-0062 Specifies the container counter to use for this supplier. (automatically created if

not existing)EXPORT-NULL-SCHEDULE-LINE

Export all POD from a purchase order even the one having no requirement

l-bdt-3003 Specifies the BDT segment valueEXPORT_ARRIVE_DATE

Export the expected arrival date according to the transport days from the purchase order.

MONTH_BUCKET_ENDS_WITH_MONTH

When the bucket Id is M, set the date of the requirement for the last day of the month from the month of the requirement date.

MONTH_BUCKET_ENDS_AFTER_FOUR_WEEKS

When the bucket Id is M, set the date of the requirement 28 days later than the requirement date.

MONTH_BUCKET_ENDS_AFTER_ONE_MONTH

When the bucket Id is M, set the date of the requirement 1 month later than the requirement date.

CUSTOMER_SUPPLIER_ID

Export the CUSTOMER_SUPPLIER_ID value into the CSG segment instead of the site Id.

SAD_7153 Export the SAD_7153 value into the SAD segment instead of “03”

F.4.1.1 EXTRA SETUPTo export a schedule it is mandatory to specify a supplier address at the supplier level in Base -> Supplier -> supplier (use the yellow button to add an Supplier address type).

F.4.2 Exp AVIEXP (ASN) v3.0

EDI Parameter EffectUNH-0062 Specifies the container counter to use for this supplier. (automatically

created if not existing)UNH-0020 Specifies the tag counter to use for this supplier. (automatically created if

not existing)AVIEXP_SDT_3036 Export in the segment SDT (Supplier Detail) in the sub segment 3036 (Id)

the specified value of the parameterCDT_Consignor Specifies the Duns number of the Consignee (segment CDT), if not defined

take the default value form the Duns number from the site Address.CDT_Consignor_(Sales Order Reference value)

Specifies the Duns number of the Consignee (segment CDT) for the Sales Order reference specified in the parameter’s name, if not defined take the default value form the Duns number from the site Address or from the

QAD Proprietary

DOC-1.5 EDI As of 3/22/2005 of 34

CDT_Consignor Edi parameter.AVIEXP_CSG_3035 Export in the segment CSG in the sub segment (id) the value of the

parameter specified in value1CSG_Final_Delivery_point Specifies the final delivery point (change the dock code value)DTR_Means_Of_transport Specifies The DRT Means of transport valueDTR_Party_Name Specifies The DRT Party name valueDTR_Transport_Number Specifies The DRT transport number valueDET_Mode_Of_TransPort Specifies The DET Mode of transport valueDET_Incoterms_Code Specifies The DET Intercoms code valueDET_Terms_Of_Delivery_1

Specifies The DET Terms of delivery code 1 value

DET_Terms_Of_Delivery_2

Specifies The DET Terms of delivery code 2 value

QAD Proprietary

Edi Autopro Documentation

Documents

Transcript of Edi Autopro Documentation