Menu Access
Character: EDI 3 3 and EDI 3 4
GUI: Click here
As mentioned in the introduction all partner specific mapping information should be done using the Segment Override function. Since both functions are the same they are presented here in the same topic. The only difference between them is that the Segment Override function allows for a partner field and the Segment Maintenance function does not.
Use this function to update segment and segment line information for specific trading
partners that is to be used when EDI data is generated, and when transaction sets are
processed. It allows you to specify what information is to be placed into an outgoing
transaction set, and allows you to specify into what field are particular data element
goes into when processing transaction sets with the Receive EDI Data function.
Before running this function, you must load in segment and segment line information by
using the EDI Data File Loader function, if this
has not yet been done.
You will be prompted for the version and trading partner to process. You will receive
an error message if segment information is not loaded in for the version you want to
process, or if the trading partner entered is not set up.
You will then be prompted for a transaction set number, and a segment sequence number. If
there is no segment information for the transaction set and segment sequence number
requested, you will receive an error message.
You will then be prompted for a transaction set number, a segment sequence number, and a
segment name. If there is no segment information for the transaction set and segment
sequence number requested, the system will try to retrieve segment information using the
segment name entered. If there is more than one segment that uses this segment name, you
will be asked which one to use. If the system cannot find the segment to work with using
the segment sequence number or segment name specified, you will receive an error message.
After retrieving the segment that you want to work with, you will be asked for a level.
This level field is used by the Generate EDI Data
function in order to know what segments to process during a particular phase of the
generation process. Multiple levels can be specified by separating each level where the
segment is to be used with a comma. This field should normally not be changed unless you
are told to by GTR support. If you change the level field, all segment line records
associated with this EDI segment are changed.
A browse frame will then appear listing the elements that are used by a particular segment. Use the |UP/DOWN ARROW| keys to go between data elements. Choose a data element to work with and hit enter. You will then be presented with the next frame:
Field | Description |
Misc | Enter any miscellaneous information about this data element. |
Line-no | Enter the line number to use when entering segment information. When EDI
data is generated, the system will process information by line number. If you are setting
up information in order to process the 850 transaction set (i.e. purchase orders) with the
Receive EDI Data function, the line number must be between 1 and 49 to process quote and
quote-line information, and between 50 and 99 to process order and order-line information. To delete a line number enter the line number followed by CTRL-D or the equivalent function key. |
Incoming | |
File name | Enter the file name to use to assign data to when data from an incoming transaction set is processed, or leave blank if the data element is not to be saved in the database. The file name entered is validated against the dictionary. |
Field name | Enter the field name to use to assign data to when data from an incoming transaction set is processed, or leave blank if the data element is not to be saved in the database. The field name entered is validated against the dictionary. |
Array element | Enter the array element to use when data from an incoming transaction set is processed. If the field name entered is an array field, then entering 0 in this field will cause the system to assign the data to the next array element available. If the field name entered is not an array field, then this field will automatically be set to 0. |
Add/assign value | Enter "yes" if you want to add the value from the incoming transaction set to the database field specified, or "no" to set the database field to value specified in the incoming transaction set.This field is only used if the database field to assign the value to is either an integer, decimal or character field. Otherwise, the value is assigned to the database field specified. |
Translation table | Enter the name of the translation table to use when incoming transaction sets are processed. If a translation table code is entered, the system will translate the data element to the value in the translation table. |
Qualifier | Enter the qualifier to use to indicate to the system that the following data element is to be assigned to a particular data base field. The qualifier entered must exist in the EDI qualifier dictionary.If qualifier "*DE*" is entered, then the qualifier's description will be added to the following data element if that data element is assigned to a data base field. |
Countries | Enter the countries that are allowed to use the element or "*" for all countries. If multiple countries are specified, then they must be separated by commas. |
Outgoing | |
Translation Table | Enter the name of the translation table to use when outgoing transaction sets are processed. If a translation table code is entered, the system will translate the data element to the value in the translation table. |
Qualifier | Enter the qualifier to use when generating EDI data for this position in a segment. The qualifier entered must exist in the EDI qualifier dictionary. |
Countries | Enter the countries that are allowed to use the element or "*" for all countries. If multiple countries are specified, then they must be separated by commas. |
After entering the fields in this frame you will be presented with the next frame:
Field | Description | ||||||||||||||
Incoming | |||||||||||||||
Formula | Enter a formula to be used to extract information from a data element when inbound transaction sets are processed. Any PROGRESS function can be used. In addition, you can use any EDI keyword or function keyword, as well as the special keywords |CURRELEM|, implying the data element being processed, and |ELEMENT|[n] (where n = the element number on the current line [element numbers start at the segment identifier]), which refers to the data elements in a given segment line. The inbound formula must return a character value. | ||||||||||||||
Outgoing | |||||||||||||||
Return Value | Enter the value to return for an outbound formula. The following values
can be specified for an outbound formula: integer, decimal, recid, character, date, or logical You may type an abbreviated return value or the complete return value. Using abbreviated return values reduces typing when entering EDI formulas. When you type in an abbreviated value, and you have finished the "Segment Override Maintenance - Formulas" frame, the long form will replace the abbreviated value in the system. The table below indicates upper-case abbreviated values for clarity, but you may enter the abbreviated value in upper or lower case. Valid abbreviated return values are:
|
||||||||||||||
Formula | Enter a formula to be used to assign a value to a data element when EDI
data is generated. Any PROGRESS function can be used. In addition, you can add or subtract
the values of database fields or constants. Any references to database files must be
specified by EDI keywords enclosed in EDI brackets (e.g. |PO-NO|). The special keyword, |LEVEL|, is used to generate specific values for a formula, based on which level a segment sequence number is processed. To use a calculated value in a formula (i.e. a variable), enter the variable name between EDI brackets, preceded by VC: for a character variable (e.g. |VC:CHAR-VAR|), VN: for a numeric variable (e.g. |VN:NUM-VAR|), VD: for a date variable (e.g. |VD:DATE-VAR|), or VL: for a logical variable (e.g. |VL:LOGICAL-VAR|). The PVN:, and QVN: prefixes allow you to perform price and quantity conversions on a numeric variable. The values of the variables must be defined by the program used to generate EDI data. The value that the formula returns must correspond to the "Return value" specified for the outgoing formula. |
For more information on formulas see Formula Theory.
Last update October 20, 2006