| EDI Parameters (ecedi0100s000) |  |
| Use this session to set parameters that determine how the Electronic Data Interchange (EDI) module operates. Related topics To use a details session
Fields | Description
Effective Date | The date and time that the parameters are valid. The parameters are valid up to the effective date of a more recent parameter setting.
Description | The description or name of the code.
EDI Implemented | If this check box is selected, EDI is implemented.
Standard Path | The directory in which all EDI-related data is located. The actual messages for your company are stored in a series of subdirectories, which will be defined at a later stage (at the network level). The directory defined here is the directory: In which the Import EDI Data (ecedi6220m000) session will search for the defaults.edi file. To which the Export EDI Data (ecedi6221m000) session will write files. That serves as the default value for the directories (paths) defined at the network level. Note The directory entered in this field must exist on your system. Once you begin transmitting messages, do not change the standard path identification.
Our Identification | Your own network address. Note For internal EDI, you can use the company number as an address. For external EDI, the translation/communication software can use the communication address to identify you as the sender of the message.
Fixed Part | The fixed part of your reference number. Note Once you begin transmitting messages, do not change the way the reference number is created. Related topics Structuring reference numbers
Date Format | The date format used as part of the reference number. Note When selecting the date format, remember that the reference number consists of 14 positions. Once you begin transmitting messages, do not change the way the reference number is created. Related topics Structuring reference numbers
First Free Number | The first free number used in the reference number of the next outgoing message. Note You can manually adjust the first free number. Once you begin transmitting messages, do not change the way the reference number is created. Related topics Structuring reference numbers
Action on First Message on New Date | Choose how to increment sequence numbers. Note Because the date is included in the reference number, the number will be unique on a new date, even if the incrementing number is repeated with 0 or 1. You can also keep incrementing the number. In that case, that number tells you how many messages have been generated so far.
Store All Received Messages | If this check box is selected, all received EDI messages are logged in a special ( store_recv ) directory.
Store All Sent Messages | If this check box is selected, all sent EDI messages are logged in a special ( store_sent ) directory.
Suppress Blank Text Lines on Generation | If this check box is selected, the empty lines in the text blocks of outgoing EDI messages are suppressed. This function limits the text content to significant information.
Suppress Blank Generated Text Fields | If this check box is selected, and the text fields for outgoing messages are not filled, the fields are suppressed in the EDI message. This function limits the message content to significant information.
] | The order series to use for address codes that are automatically generated by EDI, when specific address information is received on incoming EDI messages.
] | The user-defined series that will be used when generating incoming sales schedules for incoming EDI schedule-related messages. Note This is the series used to create schedule records. Do not confuse this series with the series used to create schedule releases, which is specified at the message by business partner level.
Interchange Message | The name of the dummy message used in various organizations to describe the layout of the interchange header and the joint message overhead. Related topics Collecting messages by business partner
Interchange Header Conversion Setup | The name of the conversion setup in which the interchange header layout is described. Note This conversion setup must be included in the dummy message in the Interchange Message field.
Message Overhead Conversion Setup | The name of the conversion setup that contains the layout of the joint message overhead. Note The conversion setup must be included in the dummy message in the Interchange Message field. The conversion setup can identify the overhead in all other messages.
Make Use of Tracefile | If this check box is selected, trace files are generated. Note In case of a read or generation error, the log file can provide more insight into the problem. Typically this field is selected during the implementation and testing phases of EDI.
Name of Tracefile | A file that contains process data about read or created ASCII files. Related topics Naming tracefiles
Read in Zero Price | If the price field is included in the incoming conversion setup and a value of zero comes in, this check box determines whether or not this zero price is used. If this check box is selected, a zero price is inserted from the file and considered as manually entered. If this check box is cleared, a default price is retrieved. Note If the price field is not included in the conversion setup, ERP LN searches for a default price. Related topics Price retrieval
Read in Zero Discount | If the discount field is included in the incoming conversion setup and a value of zero comes in, this check box determines whether or not this zero discount is used. If this check box is selected, a zero discount is inserted from the file and considered as manually entered. If this check box is cleared, a default discount is retrieved. Note If the discount field is not included in the conversion setup, ERP LN searches for a default discount. Related topics Discount retrieval