This section explains how to configure ASC X12 PM-specific parameter values in ePM.
The following list explains the outbound and inbound messaging model used for Environments and TPs during ePM configuration:
When you are configuring ePM for a component related to the current TP’s Environment, you must take the viewpoint of that Environment.
For example, Company A is the current TP with its own Environment. You are configuring a component related to Company A’s Environment envA. Therefore, in terms of the companies, ToPartner means from Company A (outbound from envA) and FromPartner, to Company A (inbound to envA).
Following the same model, when you are configuring ePM for a component related to a different TP’s Environment, you must take the viewpoint of that Environment.
For example, Company B is a TP with an Environment outside of Company B. You are configuring a component related to Company B’s Environment envB. Therefore, in terms of the companies, ToPartner means from Company B (outbound from envB) and FromPartner, to Company B (inbound to envB).
Therefore, if TPs in the previous examples are named as follows:
tpB is Company A’s TP.
tpA is Company B’s TP.
The following relationship holds true:
tpA is the TP for envB.
tpB is the TP for envA.
ASC X12 PM-specific parameters are of two basic types as explained under:
When ePM displays both sets of parameters in the previous list, parameters appear, which are generic to eXchange and are not explained in this chapter. See the eXchange Integrator User’s Guide for details on these parameters.
For additional information on how to configure ePM parameters, see Importing and Configuring Components in ePM, as well as the eXchange Integrator User’s Guide.
This section explains how to configure Interchange Envelope (outer envelope) ePM parameters for ASC X12 PM. Figure 6–4 shows an ePM example with these parameters displayed. This section describes the following parameters:
Allows you to enter a value representing the code used to identify the type of information in the Authorization Information; required.
The appropriate valid integer that represents the Authorization Information.
None
Allows you to enter a value representing the information used for additional identification or authorization of the interchange sender or the data in the interchange. The type of information is set by the Authorization Information Qualifier (ISA01).
The appropriate valid integer that represents the Author Information.
None
Allows you to enter a value representing the code used to identify the type of information in the Security Information; required.
The appropriate valid integer that represents the Security Information type.
None
Allows you to enter a value representing security information about the interchange sender or the data in the interchange. The type of information is set by the Security Information Qualifier (ISA03) value.
The appropriate valid integer that represents the Security Information.
None
Allows you to enter a value representing the qualifier used to designate the system/method of information code (IC) structure employed to designate the sender ID element being qualified; required.
The appropriate valid integer that represents the IC sender ID qualifier.
None
Allows you to enter a value representing the IC published by the sender for other parties to use as the receiver ID to route data to them. The sender always codes this value for the sender ID element; required.
The appropriate valid integer that represents the interchange sender ID.
None
Allows you to enter a value representing the qualifier used to designate the system/method of IC structure used to designate the receiver ID element being qualified; required.
The appropriate valid integer that represents the IC receiver ID qualifier.
None
Allows you to enter a value representing the IC published by the receiver of the data. When you are sending, this value is used by the sender as their sending ID, thus other parties sending to them use this as a receiving ID to route data to them; required.
The appropriate valid integer that represents the interchange receiver ID.
None
Allows you to enter a value representing the IC used to identify the agency responsible for the control standard used by the message that is enclosed by the current interchange header and trailer; required.
The appropriate valid integer that represents the IC control standard identifier.
U
Allows you to enter a value representing the current IC version number. This number covers all the current interchange control segments; required.
The appropriate valid integer that represents the current IC version number.
00401
Allows you to enter a value representing the data interchange IC control number. This value is a setting that starts calculating the unique identifier for outbound messages. The identifier increments by 1 from this number, for each additional message; required.
The appropriate valid integer that represents the IC control number for the first message. It is recommended that you use the default, unless your system needs dictate otherwise. This number cannot be 0.
1
Allows you to enter a value representing the code sent by the sender to request an interchange acknowledgment (TA1); required.
The appropriate valid integer that represents the acknowledgment code.
1
Allows you to enter a value representing the code used to indicate whether data enclosed by the current interchange envelope is for testing, production, or information only; required.
P, T, or I.
P
Allows you to enter a value that changes the component element default delimiter.
The data element type is not applicable. The component element separator is a delimiter and not a data element. This field provides the delimiter used to separate component data elements within a composite data structure. This value must be different from the data element separator and the segment terminator.
Enter the appropriate delimiter override character.
If you use nondefault delimiters (for example, if you use “!” for segment terminator in v4060), you must ensure that your business rules manually pass the nondefault delimiters into the ExStdEvent/PayloadSection/Envelopes/BusinessProtocol/ location, that is, pass the ISA into .../Batch/Header, the IEA into .../Batch/Trailer, the GS into .../Group/Header, and the GE into .../Group/Trailer.
To use a control character as a delimiter, pass the escaped Unicode UTF-16 representation of the character (\uXXXX). For example, if you wanted to use a carriage return (ASCII 0x0d) as a delimiter, you would pass the string \u000d.
Colon (:) character
Allows you to change the segment terminator default delimiter. See ISA16 Comp Elem Sep for more details.
Enter the delimiter override character.
Tilde (~) character
Allows you to change the element separator default delimiter. See ISA16 Comp Elem Sep for more details.
XML reserved characters, for example &, <, or >, cannot be used as delimiters. See the appropriate XML information source for a complete list of these characters.
Enter the delimiter override character.
Asterisk (*) character
This section explains how to configure Functional Group (inner envelope) ePM parameters for ASC X12 PM. Figure 6–5 shows an ePM example with these parameters displayed. This section contains the following parameters:
Allows you to set a value to match the Group Name attribute of this business action, set in the B2B Host’s Business Service; required.
For example, a Group Name of “HS” is for a 270 action; “HB” for a 271; “PO” for an 850; “PR” for an 855; “FA” for a 997.
None (depends on the current business action)
Allows you to enter a value representing the code identifying the party sending a message transmission. These codes are predefined and agreed upon by the TPs; required.
The appropriate valid integer that represents the application sender code.
None
Allows you to enter a value representing the code identifying the party receiving a message transmission. These codes are predefined and agreed upon by the TPs; required.
The appropriate valid integer that represents the application sender code.
None
Allows you to set the date structure for this transaction set, in a format specified under “Required Values;” required.
CCYYMMDD or CCYYYYMMDD; choose from the list to use a four-digit or two-digit year format, for example:
20041201 = December 1, 2004
050112 = January 12, 2004
CCYYMMDD
Allows you to set the time structure for this transaction set, in a format specified under “Required Values;” required.
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD.
Choose from the list to specify seconds and degrees of accuracy, for example:
2359 = 11:59PM
235959 = 11:59:59PM
23595999 = 11:59:59.99PM
The time is expressed in 24-hour (military) clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59); and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99).
HHMM
Allows you to enter the group control number assigned and maintained by the sender.
The appropriate valid integer that represents the group control number.
0
Allows you to enter a value representing the code used in conjunction with data element (DE) 480 used to identify the issuer of the current X12 standard; required.
The appropriate correct transaction set code (X is recommended, but you may have to use others, for example, T, as required by the current X12 standard being used.
X
Allows you to enter a value representing the code indicating the X12 version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; required.
If the responsible agency code under the GS07 segment is X (recommended), enter values as follows in the appropriate DE 480 positions:
1 through 3 = the current version number
4 through 6 = the release and subrelease levels of the current version
7 through 12 = the current industry or trade association identifiers (optionally assigned by the user)
If code entered for the GS07 segment is different, for example, T, then other formats are allowed, as required by the current X12 standard being used.
None