This document discusses the technical aspect of generating EDI data files. The 810, 830, 850, 855, 856, 857, 860, 880, and 882 documents are discussed in detail as well.
Before generating information on a particular document, the system verifies if the
document (i.e., PPS, invoice, purchase order, etc.) exists in the database, and can be
used to generate a transaction set. If the document no longer exists, then a transaction
set will not be generated for it.
The system will then verify if transaction set information and control numbers have been
set up for the trading partner to be used for this document. It will also make sure that
the segment information required to generate a transaction set (i.e. a transaction set
map), has been set up for the trading partner, transaction set and version to use.
Transaction set maps used to create transaction sets are set up using the Segment Override Maintenance function.
If the system does not have all the information that it needs in order to generate a
transaction set for a particular document, then status messages will be displayed, and the
system will attempt to generate a transaction for the next document to be processed.
Generation Process
If the system has determined that it has all the information it needs to generate a
transaction set for a document, it will then attempt to create one for the document being
processed.
The system proceeds to generate all the transaction set lines for each level used by the
transaction set generation program for the document being processed. The level being used
at any point in the generation process depends on what stage the generation process is at.
You will define which level to use for a particular transaction set line in the
transaction set map that is set up for the document. The levels themselves, however, are
system-defined. Please refer to the Transaction
Set Considerations section for more information on the levels that are used when
transaction sets are generated for a document.
As each level is processed, the system retrieves all records related to the record being
processed during a generation level. This allows you to access information that is not
stored on the document itself. For example, when the system generates transaction sets
from invoices (i.e. the 810 transaction set), you can access information from the customer
file, the ship-via file, and other related tables.
The values assigned to a data element on a transaction set line are determined using the
formulas set up in your transaction set map, if a formula has been entered. Otherwise, the
value entered in the "qualifier" field will be used.
If a formula is being used to determine the value to be assigned to a data element, and
the formula does not exist in the trading partner's "send" directory, as defined
in the EDI Partner Maintenance function,
the system will generate the formula, and save it into a temporary directory. If the
system is unable to generate the formula, then you will receive an error message, and the
transaction set will not be generated.
If the formula is "mathematically correct", the system will calculate the value
to assign to a data element on a transaction set line. The value calculated must have the
same data type as the "Return Value" entered for that formula. If it does not
return the same data type, or the value to be assigned to a transaction set is undefined,
then you will receive an error message, and the transaction set will not be generated. For
more information on entering formulas, please refer to the Entering
EDI Formulas document.
If variables (e.g. |VN:NUM-VAR|) are used in a formula, the variable must have been
defined in the program used to generate a particular document (i.e. it must be set up by
the software developer). If the variable is not defined, then the variable will return an
undefined value. For more information on using variables in formulas, please refer to the Entering EDI Formulas document.
After the value to assign to a data element on a transaction set line has been calculated,
the system will then use the translation table specified to convert the value into the
value to be saved on the transaction set line. If the value to be converted has not been
set up in the translation table, then the value will be left unchanged.
It should also be noted that if the element delimiter character to be used when generating
a transaction set is embedded in the value assigned to adata element, the system does not
alter the data element being assigned to a transaction set line. Therefore, the element
delimiter used should notbe a character that can be used to enter information used for a
particular document.
Before adding a data element to a transaction set line, the system will verify that the
data element does not exceed the maximum length allowed.If the data element is too large,
then the system adjusts (i.e. rounds, truncates, as appropriate) that the value so that it
is not larger than the maximum length.
If a trading partner does not use all the data elements used in a transaction set line,
and you do not set them up in your transaction set map, the system will provide
"place holders" (i.e. empty data elements) for those data elements that are
missing.
Once all the data elements needed are processed for a transaction set line, the system
saves the transaction set line, and then works on the next one to be included in the
transaction set being generated. It should be noted that the system does not validate
transaction set lines for mandatory and/or conditional data elements, nor does it check
that the values assigned to a particular data element have the proper data type. This
point should be taken into consideration when setting up a transaction set map with the
documents that you are generating transaction sets for.
Certain transaction set lines are created by the system automatically during the
generation process. Please refer to the Transaction
Set Considerations section for more details.
[For MXP only
During the generation process, the system will automatically add any attached memos (i.e.
Memos created using HyperTools "Attach Memo" feature) used by a document, into
the transaction set being generated at the appropriate point in the generation process. If
you do not want to include attached memos, then set the "Send Attached Memos"
field to "no" in the transaction set information section in EDI Partner Maintenance for the trading
partner/transaction set combination used to process this document.]
If no errors occurred during the generation process, then the system will append the
generated transaction set to the output file specified for the file location being used.
The system then sets the status code for the EDI document to "2" (i.e., sent),
and updates statistics such as date and time sent, and the name of the sender.
For each document where a transaction set has been generated, the system also assigns a
batch number to the EDI document record. The batch number allows you to change the status
code for a group of EDI documents. Please refer to the documentation on the Mass EDI Document Status Code Change
function for more details.
The system also stores the functional group (GS) and transaction set (ST) control numbers
used by the generated transaction set on the EDI document record.
If the EDI document record is in use when a transaction set is generated, a warning
message displays that the statistics, batch number and control numbers cannot be assigned.
After the system has generated transaction sets for those documents with the same
interchange envelope partner, the system "unlocks" the output directory of the
file location being used, allowing other users to generate EDI data to this file location.
Generating Control Segments
The system automatically generates control segments (i.e. the interchange control (ISA),
and functional group (GS) segments) every time a new interchange envelope partner or
document type is processed. The interchange envelope and functional group control numbers
for the trading partner being processed are automatically incremented. If the system is
unable to determine the control number to use, you will receive an error message, and the
documents will not be generated.
If transaction sets are generated successfully, then the functional group trailer (GE) and
interchange control trailer (IEA) segments are inserted into the output file at the
appropriate point.
Units of Measure
The ANSI X12 EDI standards dictate that "standard" units of measure be used when
transaction sets are generated. The system does not validate whether or not the unit of
measure used is valid. Therefore, it is recommended that when unit of measure codes are
created, they be set up in accordance with the ANSI X12 standard. Refer to the ANSI X12
standards, section VIII, element 355, for a list of "standard" unit of measure
codes. For more information on how to set up unit of measure codes, refer to the
documentation for the Unit of Measure Maintenance function in MXP's Inventory Management
module or in the FrameWORX documentation..
Currency Codes
As with unit of measure codes, the ANSI X12 EDI standards define "standard"
currency codes. The system does not validate whether or not the currency code used is
valid. Therefore, it is recommended that when currency codes are created, they be set up
as per the ANSI X12 standard. Refer to the ANSI X12 standards, section VIII, element 100,
for more information on the currency codes to use. For more information on how to set up
currency codes, refer to the documentation on Currency Maintenance in MXP's General Ledger
module or in the FrameWORX documentation..
Test Mode
All the transaction sets generated for a particular interchange envelope partner will use
the same test/production mode setting, as defined in the ISA section of the EDI Partner Maintenance function for the
interchange envelope partner being used. If you are generating different types of
transaction sets for the same trading partner, and some transaction sets are in test mode,
and others are in production mode, then you will have to run the Generate EDI Data function twice; once for those
documents which are in test mode, and then, after setting the test/production mode
indicator to production mode, again for those documents which are in production mode.
Transferring Transaction Sets To Trading Partners
After the system has generated transaction sets, the system will then run the EDI Data File Transfer function for all file
locations where a communications script has been entered for this file location, and the
communications script is to be executed automatically.
If you have not entered a communications script to use for a given file location, then you
are responsible for getting the output file to the trading partner or VAN, via modem or
other method of communication. You are also responsible for removing the output file from
the output directory, as well as for making a backup copy of the output file in the backup
directory for this file location. See the Backups section below for more information on
how backup copies should be made.
Backups
If you have chosen to have the system make a backup of the output file for a given file
location after it has transferred it to a trading partner or VAN using the EDI Data File Transfer function, the system makes a
backup copy of the output file in the backup directory specified for the file location
being processed. The system uses a file name in the following format:
o-<date>.<num> (e.g., o-970724.002)
The <date> is the system date in "YYMMDD" format, and <num> is a
three-digit sequential number. If the system is unable to make a backup copy, an error
message displays.
Backup copies of the output file are named in this format in order that the EDI Data File Manager function can allow you to
restore or perform file management tasks on the backup copies.
Unwrapped/Wrapped Transaction Sets
The EDI system allows you to specify if the transaction sets generated for a trading
partner are to be sent in unwrapped (i.e. each transaction set line is stored on its own
line in the output file), or wrapped (i.e., each transaction set line is part of a single
"continuous" line) format. Some VAN's, however, cannot handle output files with
both wrapped and unwrapped data in the same output file. As a result, make sure that you
have not set up two or more file locations that generate EDI data to the same output file,
where one file location generates EDI data in wrapped format, and another is in unwrapped
format.
The following should be considered when transaction sets are generated:
When 810 (i.e. Invoices) transaction sets are generated using EDI documents with document
type "2", the trading partner's
parameters listed below are used:
Please note that all Partner Transaction Set Information Parameters relating to the TDS, ISS and CTT segments are no longer applicable.
This is because these segments are no longer "hard-coded"; they may now be mapped. Please refer to the specific variables that are
available to be used for these formulas.
Include zero qty shipped lines:
Enter "yes" to include invoice lines with no quantity shipped in a transaction set, or "no" to exclude them from the transaction set.
1+:Gen Inv only; 0:Gen Inv/Cr:
Enter "0" to include all invoices or enter any number greater than 0 to generate invoices only, i.e. no credit notes. Note that this is
only used within the invoicing function and not at the point of generate since no trigger is created.
The following levels are used when generating invoices:
| Level | Used to generate/Notes |
| 1 | Transaction set lines before the item level segments. |
| 2 | Transaction set lines used for item level segments that can be used for serialized or non-serialized items, but not both. If an item is serialized, then each serial/lot number used for a given item number generates item level segments. |
| 3 | Transaction set lines used for item level segments are can be used for serialized and non-serialized items. |
| 4 | Transaction set lines used for segments before additional before additional charge (i.e. ITA) segments. Use this level for the TDS segment. |
| 5 | Transaction set lines used for additional charges. |
| 6 | Transaction set lines after additional charges. Use this level for the ISS segment. |
| 8 | Transaction set lines at final level such as CTT segment. |
The CTT, ISS and TDS segments are no longer automatically
generated by the system.
The following variables are accessible in your transaction set mappings when generating invoices:
| Variable | Type | Level | Value Stored In Variable |
| TOT-INV-AMT | Numeric | 4 | The total of invoice amounts with two (2) implied decimals. |
| DISCBLE-AMT | Numeric | 4 | The discountable invoice amount with two (2) implied decimals. |
| DISC-AMT-DUE | Numeric | 4 | The discountable amount less the total total discount amount on this invoice with two (2) implied decimals. |
| TOT-DISC-AMT | Numeric | 4 | The total discount amount on this invoice with two (2) implied decimals. |
| (note: the TDS segment uses the above 4 variables) | |||
| TOTAL-UNITS | Numeric | 6 | Total shipped invoice quantity for this invoice. |
| TOTAL-WEIGHT | Numeric | 6 | Total weight for this invoice. |
| TOTAL-VOLUME | Numeric | 6 | Total volume for this invoice. |
| (note: the ISS segment uses the above 3 variables) | |||
| NO-INV-LINES | Numeric | 8 | Total number of invoice lines. |
| HASH-TOTAL | Numeric | 8 | The hash total net amount. The amount has an explicit decimal point at 2 decimal places. |
| HASH-TOT-QTY | Numeric | 8 | The hash total quantity shipped amount. The amount has an explicit decimal point at 2 decimal places. |
| (note: the CTT segment uses the above 3 variables) |
Error messages will occur in the following cases and will result
in an invoice not being generated:
1. No invoice lines exist for an invoice.
2. The Invoice/Credit switch on at least one line does not match the header information.
3. The document number on at least one line is set to a number other than that on the invoice.
When the invoice is rejected, the status remains at '1'.
A warning message will occur if you have the document number on any line set as ?. The invoice will, however, still be generated.
When 830 (i.e. MRP-Forecasts) transaction sets are generated using EDI
documents with document type "9", the following levels are used:
| Level | Used to generate/Notes |
| 1 | Transaction set lines before the item level segments. |
| 2 | Transaction set lines used for item level segments. |
The CTT segment is automatically generated by the system.
There are no partner transaction set information parameters to set.
The following variables are accessible in your transaction set mappings when generating forecasts:
| Variable | Type | Level | Value Stored In Variable |
| STARTDATE | numeric | 1 | the first forecast date based on the start day entered in edi 4 1. |
| BOH | numeric | 2 | quantity on hand: if it's a multi bin item, use the item-whs-bin table if it's not a multi bin item, use the item-whs table. |
When 850 (i.e. Purchase Order) transaction sets are generated using EDI documents with
document type "3", the following levels are used:
| Level | Used to generate/Notes |
| 1 | Transaction set lines before the item level segments. |
| 2 | Transaction set lines used for item level segments. |
The CTT segment is automatically generated by the system.
When 855 (i.e. Purchase Order Change) transaction sets are generated using EDI documents
with document type "6", the trading
partner's parameters listed below are used:
Gen. ACK segment at PO1 level:
Enter "yes" if the ACK segment is to be generated for each PO1 segment used in a
purchase order acknowledgement, or "no", if your trading partner does not
require that an ACK segment be sent for each PO1 segment that you receive.
Gen. ACK segment at SLN level:
Enter "yes" if the ACK segment is to be generated for each SLN segment used in a
purchase order acknowledgement, or "no", if your trading partner does not
require that an ACK segment be sent for each SLN segment that you receive.
Levels are not used when generating this transaction set, because a P/O acknowledgement
re-transmits the information that was received from the corresponding incoming purchase
order (850) transaction set. Instead, the generation program used to create P/O
acknowledgement transaction sets generates transaction set lines for only those segments
that you have set up in the transaction set map for the trading partner being processed.
The ACK segment in a P/O acknowledgement is generated by the system only if you request
it. You can generate an ACK segment for either a PO1 segment, an SLN segment or both
segments. When the system creates an ACK segment, it saves the information from the PO1
and/or SLN segment on the ACK segment.
When 856 (i.e. Advanced Ship Notices) transaction sets are generated using EDI documents
with document type "1" (Picking slips), type "5", (Packing slips),
type "7" (Bills of Lading), or type "P" (Invoices) the trading partner's parameters listed
below are used:
Incl zero qty on PPS/Shipped lines:
Enter "yes" to include slip lines (from PPS or invoice lines) with with no quantity entered in a transaction set, or "no" to exclude
them from the transaction set. This option only applies when advanced ship notices are generated from picking slips or invoice
lines. The system automatically excludes packing slip and bill The system automatically excludes packing slip and bill
of lading lines with no quantity entered when advanced ship notices are generated from packing slips or bills of lading.
Use parent ID on HL segment:
Enter "yes" if the parent ID should be saved as part of the HL (Hierarchical
Level) segment (i.e. transaction set line) when the HL segment is generated, or
"no" to not include in the HL segment. The system automatically generates HL
segments as necessary.
Use hier. child on HL segment:
Enter "yes" if the hierarchical child code should be saved as part of the HL (Hierarchical Level) segment (i.e. transaction set line) when
the HL segment is generated, or "no" to not include the HL segment. The hierarchical child code is used to indicate that there are sub-levels
for the hierarchical level being generated. For most trading partners, this parameter should be set to "no".
Generate Pack HL level seg.:
Enter "yes" if "Pack" (i.e. carton/box) level segments should be generated when ASN's are generated or "no" if your trading partner
does not require pack level segments. Pack level segments are typically used to indicate the bar codes and/or carton markings used on a
particular carton or box. This option only applies if advanced ship notices are generated from bills of lading.
Gen. Pick/Pack or Std. pack:
Enter "yes" if advanced ship notices are to be generated in Pick/Pack (i.e. by carton/box number / item number) order, or "no" if you want
them generated in Standard pack (i.e. by item number / carton/box number) order. This option only applies if advanced ship notices are
generated from bills of lading.
Most trading partners in the retail sector prefer to receive advanced ship notices in pick/pack order, whereas most trading partners in the
automotive sector prefer to receive advanced ship notices in standard pack order. Refer to your trading partner's implementation guide, or
contact the trading partner in question to determine the order in which they would like to receive their goods.
By PPS (0) or By CUST-PO (1) (numerical parameter):
This parameter is used when you are generating the advanced shipment notice by Bill of Lading. Should you want to generate the order
level by MXP's PPS (also called picking slip), then set this parameter value to 0. Should you want to generate the
order level by the order's purchase order value, then set this parameter value to 1. It is implied that the lower levels are
thus kept within this picking slip or customer's purchase order umbrella.
From [P]ick/P[A]ck/[B]OL/[I]nv:
This parameter is not used during the generation process, but is used when creating EDI document records to be used by the generation process.
Enter "P" to have the system create EDI document records only for picking slips, "A" to create EDI document records only from packing slips, "B"
to create EDI document records only from bills of lading, or "I" to create EDI document records only from invoices.
HL levels before item level:
Enter the hierarchical levels to be used before the item level when generating advanced
ship notices. To use more than one level, separate each level with a comma (,). If no
hierarchical levels are to be used before the item level, then leave the parameter value
blank.
If hierarchical levels are used, then they must be no longer than 2 characters in length,
and cannot be blank. It should be noted that hierarchical level "I" is reserved
for system use, and cannot be used.
This option is not available for the 856 originating from an invoice.
HL gen. levels bef. item level:
Enter the generation levels (i.e. the "levels" used by the generation process)
to be used for the hierarchical levels before the item level. The number of generation
levels specified must be the same as the number of hierarchical levels used. The
generation levels must be separated with commas if more than one hierarchical level is
used, and cannot be blank. It should be noted that generation levels "1" and
"9" are reserved for system use, and cannot be used.
This option is not available for the 856 originating from an invoice.
HL Levels for Pack level:
Enter the hierarchical level to use when generating "Pack" (i.e. carton/box) level segments. The hierarchical level to use when generating pack
level segments cannot be blank, and must be less than two (2) characters in length. Examples of levels to use are "T" and "P" for tare and pack
levels, respectively.
This option is not available for the 856 originating from an invoice.
HL gen. levels for pack level:
Enter the generation points (i.e. at which point a particular generation level) to be used for the hierarchical levels before the item level
when an 856 transaction set is generated from a bill of lading. The number of generation points specified must be the same as the number of
hierarchical levels used. The generation points must be separated with commas if more than one hierarchical level is used.
If "B" is entered as a generation point, the system will generate the level using bill of lading information. If "P" is entered as a generation
point, the system will generate the level using pack header information. If an invalid generation point is specified, the system will not generate
a transaction set from a bill of lading.
This option is not available for the 856 originating from an invoice.
Gen HL for Kit Items(1:N 0:Y): (numerical parameter)
If your trading partner does not want a separate Hierarchical (Item) Level Segment for each Kit component,
set the value of this parameter to a numerical value of 1. If you want to generate the Item's Hierarchical Level
segment for each kit component as if it were a regular non-kit item, then set this parameter value to numerical
value of 0.
Additional note for this parameter:
When you are processing the ASN by "Bill of Lading", the outbound ASN document can detect whether your item is a
kit component as long as it can find a single order line with the item that is being processed within your bill of lading.
The logical variable |VL:KITCOMP| (see below) is available for your usage independently of this parameter value.
Parent ID on 1st HL (1:N 0:Y): (numerical parameter)
If your trading partner requires that the parent id be blank only in the first HL segment for the shipment but the parent id should
continue to be the same as expected on all other HL levels, then set this parameter appropriately.
Should you require to print blank for the parent ID on the HL shipment level (1st level), then enter 1
(ie one), else type 0.
Typing 0 implies that the HL shipment level segment will display the parent ID on the first level, as usual.
The following levels are used when generating advanced ship notices:
| Level | Used to generate/Notes |
| 1 | Transaction set lines before the first HL segment. |
| 2 | Transaction set lines generated for the first hierarchical level. This level is typically used for "shipment" level segments. |
| 3 | Transaction set lines generated for the second hierarchical level. This level is typically used for "order" level segments. |
| 4-6 | Levels 4 through 6 can be used for other hierarchical levels 5 that are required by your trading partner. |
| 7 | Transaction set lines generated at the "pack" level. This level is typically used to specify the carton/box markings used when shipping goods. |
| 8 | Transaction set lines generated at the "item" level. If an item is serialized, then each serial/lot number used for a given item number generates "item" level transaction set lines. |
| 9 | Transaction set lines generated at the "item" level. If an item is serialised, then each serial/lot number used for a given item number generates "item" level transaction set lines. |
The following MXP tables/files are available when generating advanced ship notices by PPS. Note that any table available on a generation higher level (lower number) is available at a lower generation level:
| Level | Tables available for use in the ASN |
| 1 | bol-header, ar-control, ar-control-d, op-control, ship-via from bol-header, invoice from bol-header, edi-shipment, edi-document, edi-partner. |
| 2 | Shipment Level edi-asn-cont, and the following tables: Only when there exists only one picking slip for this bill of lading and you have set the asn control file switch "Relationship between PPS and BOL (Enter One or Many)" to the value of 'One', the following tables are also available: pps-header, edi-order (created via ASN Update function), order, edi-ord-ext (order extension from inbound 850 or order extension maintenance), currency, ar-term, customer, customer-d, state, country, ship-via, warehouse pack-header, ptdb.z_site, invoice. |
| 3 | pps-header, edi-order (created via ASN Update function), order, edi-ord-ext (order extension from inbound 850 or order extension maintenance), currency, ar-term, customer, customer-d, state, country, ship-via, warehouse pack-header, ptdb.z_site, invoice. |
| 7 | edi-pallet, numerical variable |VN:CART-ON-PALL| |
| 8 | edi-carton |
| 9 | edi-line-con, item, vendor from item table, item-cust, uom from item-cust or item. If the item appears only once within the whole picking slip, then the following tables are available to you: pps-line, warehouse, order-line, edi-ordl-ext (order-line extension from inbound 850 or from order extension maintenance), item-whs-d. |
The following MXP tables/files are available when generating
advanced ship notices by INVOICE. Note that any table available on a generation higher level (lower number) is available at a lower
generation level:
| Level | Tables available for use in the ASN | |||||||||||||||
| 1 | invoice, edi-document, edi-partner, entity, warehouse,
pps-header, order, edi-ord-ext, customer, customer-d, order-type, ar-term, salesman,
comm-type, sls-group, state, tax, currency, rma, ship-via, job, country,
bol-header, pack-header, estimate, z_site, ar-control, ar-open-item, ar-control-d, op-control,
op-control-d. The following variables are accessible in your transaction set mappings when generating this level.
|
|||||||||||||||
| 2 | Shipment Level Same tables as level 1. | |||||||||||||||
| 3 | Order Level Same tables as level 1 | |||||||||||||||
| 7,9 | Item Level Transaction set lines used for item level segments are can be used for serialized and non-serialized items. invoice-line, order-line, edi-ordl-ext, pps-line, gl-account, item, uom, vendor, item-cust, comm-type sls-group, warehouse, item-whs, item-whs-d, poreq, poqreq-line, order-type, rma, rma-line, job, gst, ar-term, state-pst, invoice-ln-s (if available) |
|||||||||||||||
| 4 | After items have been handled:
|
|||||||||||||||
| 5 | Used for additional charges: invoice-add, gst, state-pst, addit-charge |
|||||||||||||||
| 6 |
|
|||||||||||||||
| 8 |
|
The following MXP tables/files are available when generating advanced ship notices by BOL by P/O. Note that any table available on a generation higher level is available at a lower generation level:
| Level | Tables available for use in the ASN |
| 1 | bol-header, ar-control, ar-control-d, op-control, op-control-d, ship-via from bol-header, invoice from bol-header, edi-shipment, edi-document, edi-partner. |
| 2 | Shipment Level edi-asn-cont, and the following tables: When only one picking slip exists for this bill of lading and you have set the asn control file switch "Relationship between PPS and BOL (Enter One or Many)" to the value of'One', the following tables are also available (only if one order exists with this P/O): order, edi-order-po (created via ASN Update function), edi-ord-ext (order extension from inbound 850 or order extension maintenance), currency, ar-term, customer, customer-d, state, country, ship-via, warehouse ptdb.z_site, invoice from the order record. |
| 3 | edi-order-po (created via ASN Update function). When we can find one order for a P/O, these files are available: order, edi-ord-ext (order extension from inbound 850 or order extension maintenance), currency, ar-term, customer, customer-d, state, country, ship-via, warehouse ptdb.z_site, invoice. |
| 7 | edi-pall-po, numeric variable |VN:CART-ON-PALL| |
| 8 | edi-cart-po |
| 9 | edi-line-po, item, vendor from item table, item-cust, uom from item-cust or item. If the item appears only once within the whole purchase order grouping, then the following tables are available to you: pps-line, warehouse, order-line, edi-ordl-ext (order-line extension from inbound 850 or from order extension maintenance), item-whs-d. |
The HL and CTT segments are automatically generated by the system.
The following variables are accessible in your transaction set mappings when generating advance shipment notices:
| Variable | Type | Level | Value Stored In Variable |
| CART-ON-PALL | Numeric | 8 | The total of cartons on the pallet in question (integer). |
| KITCOMP | Logical | 9 | Whether the item is a kit component. Use this variable in your formulas to do special processing for kit components such as suppression of certain segments or segment positions. |
When 857 (i.e. Shipment and Billing Notice) transaction sets are
generated using EDI documents with document type "M", the trading partner's parameters listed below are used:
Include zero qty shipped lines:
Enter "yes" to include invoice lines with no quantity shipped in a transaction set, or "no" to exclude them from the transaction set.
1+:Gen Inv only; 0:Gen Inv/Cr:
Enter "0" to include all invoices or enter any number greater than 0 to generate invoices only, i.e. no credit notes.
Gen HL for Kit Items(1:N 0:Y): (numerical parameter)
If your trading partner does not want a separate Hierarchical (Item) Level Segment for each Kit component,
set the value of this parameter to a numerical value of 1. If you want to generate the Item's Hierarchical Level
segment for each kit component as if it were a regular non-kit item, then set this parameter value to numerical
value of 0.
Use parent ID on HL segment:
Enter "yes" if the parent ID should be saved as part of the HL (Hierarchical Level) segment (i.e. transaction set line) when the HL
segment is generated, or "no" to not include in the HL segment. The system automatically generates HL segments as necessary.
Use hier. child on HL segment:
Enter "yes" if the hierarchical child code should be saved as part of the HL (Hierarchical Level) segment (i.e. transaction set line) when
the HL segment is generated, or "no" to not include the HL segment. The hierarchical child code is used to indicate that there are sub-levels
for the hierarchical level being generated. For most trading partners, this parameter should be set to "no".
Parent ID on 1st HL (1:N 0:Y): (numerical parameter)
If your trading partner requires that the parent id be blank only in the first HL segment for the shipment but the parent id should
continue to be the same as expected on all other HL levels, then set this parameter appropriately.
Should you require to print blank for the parent ID on the HL shipment level (1st level), then enter 1 (ie one), else type 0.
Typing 0 implies that the HL shipment level segment will display the parent ID on the first level, as usual.
The following MXP tables/files are available when generating advanced ship notices by INVOICE. Note that any table available on
a generation higher level (lower number) is available at a lower generation level:
| Level | Tables available for use in the ASN | |||||||||||||||
| 1 | invoice, edi-document, edi-partner, entity, warehouse,
pps-header, order, edi-ord-ext, customer, customer-d, order-type, ar-term, salesman,
comm-type, sls-group, state, tax, currency, rma, ship-via, job, country,
bol-header, pack-header, estimate, z_site, ar-control, ar-open-item, ar-control-d, op-control,
op-control-d.
The following variables are accessible in your transaction set mappings when generating this level.
|
|||||||||||||||
| 2 | Shipment Level Same tables as level 1. |
|||||||||||||||
| 3 | Order Level Same tables as level 1 |
|||||||||||||||
| 7,9 | Item Level Transaction set lines used for item level segments are can be used for serialized and non-serialized items. invoice-line, order-line, edi-ordl-ext, pps-line, gl-account, item, uom, vendor, item-cust, comm-type sls-group, warehouse, item-whs, item-whs-d, poreq, poqreq-line, order-type, rma, rma-line, job, gst, ar-term, state-pst, invoice-ln-s (if available) |
|||||||||||||||
| 4 | After items have been handled:
|
|||||||||||||||
| 5 | Used for additional charges: invoice-add, gst, state-pst, addit-charge |
|||||||||||||||
| 6 |
|
|||||||||||||||
| 8 |
|
When 860 (i.e. Purchase Order Change) transaction sets are generated using EDI documents
with document type "4", the following levels are used:
| Level | Used to generate/Notes |
| 1 | Transaction set lines before the item level segments. |
| 2 | Transaction set lines used for item level segments. |
The CTT segment is automatically generated by the system.
The system sends all purchase order lines used in a purchase order, not only those
purchase order lines which have changed.
When 880 (i.e. Invoices) transaction sets are generated using EDI
documents with document type "8", the trading partner's parameters listed below are used:
Please note that all Partner Transaction Set Information Parameters relating to the TDS, ISS and CTT segments are no longer applicable.
This is because these segments are no longer "hard-coded"; they may now be mapped. Please refer to the specific variables that are
available to be used for these formulas.
Include zero qty shipped lines:
Enter "yes" to include invoice lines with no quantity shipped in a transaction set, or "no" to exclude them from the transaction set.
1+:Gen Inv only; 0:Gen Inv/Cr:
Enter "0" to include all invoices or enter any number greater than 0 to generate invoices only, i.e. no credit notes.
The following levels are used when generating invoices:
| Level | Used to generate/Notes |
| 1 | Transaction set lines before the item level segments. |
| 2 | Transaction set lines used for additional charges. |
| 3 | Transaction set lines used for item level segments that can be used for serialized or non-serialized items, but not both. If an item is serialized, then each serial/lot number used for a given item number generates item level segments. |
| 4 | Transaction set lines used for item level segments are can be used for serialized and non-serialized items. |
| 6 | Transaction set lines used for segments after the Item level segments such as the G31 segment. |
| 8 | Final Transaction set lines such as the G33 segment. |
882 (i.e. Customer Statement) transaction sets are generated
using EDI documents with document type "0".
| Level | Used to generate/Notes |
| 1 | Transaction set lines before the first invoice level segments |
| 2 | Transaction set lines used for invoice level segments. |
| 3 | Transaction set lines after the invoice level segments. |
The following variables are accessible in your transaction set
mappings when generating 882 invoices:
|
Variable |
Type | Level | Value Stored In Variable |
| TOT-INV-AMT | Numeric | 3 | The total of invoice amounts with two (2) implied decimals. |
| PRIOR-BAL | Numeric | 3 | The prior statement balance with two (2) implied decimals. |
| CURRENT-BAL | Numeric | 4 | The current statement balance with two (2) implied decimals. |
When 882 (i.e. Statements) transaction sets are generated using EDI
documents with document type "0", the trading partner's parameters listed below are used:
Generate for 0 Bal. Invoices:
Enter 'yes' to generate statements for invoices with balances = 0.
System Issues
When the system generates outgoing transaction sets, it creates a "lock" file in
the output directory. In the event of a system crash, or other hardware failure, this
"lock" file may not be removed. Use the Remove EDI Lock Files function to remove
this "lock" file from the system.
The system creates a directory underneath your working directory, called
egp<terminalid> (e.g. egpttyp1), where <terminalid> is the terminal from which
this function is being run, to store generated outgoing formulas which were not previously
generated by the Generate EDI
Formulas function. If a system crash, or hardware failure occurs, this directory may
not be removed by the system. You will have to exit to the operating system, and remove
this directory, along with any subdirectories manually.
The system also creates the following temporary files:
In all cases, <terminalid> refers to the terminal from which the Generate EDI Data function is run.
| Filename | Purpose |
| isa<terminalid> | Stores information generated for the interchange control header (i.e. ISA) segment. |
| gs<terminalid> | Stores information generated for the functional group header (i.e. GS) segment. |
| st<terminalid> | Stores information generated for the transaction set control header (i.e. ST) segment. |
| se<terminalid> | Stores information generated for the transaction set control trailer (i.e. SE) segment. |
These files are removed from the system once they are processed. However, it may be
possible that they are not removed due to a hardware crash, or other hardware failure. If
this is the case, you will have to exit to the operating system, and remove these files
manually.
Last updated October 20, 2006