Electronic Commerce Client Requirements … Commerce Client Requirements Document (ECCRD) ... Explanation of ANSI X12 Message Map Headings ... X12 and UN/EDIFACT Electronic Data Interchange

Electronic Commerce Client Requirements Document (ECCRD) Chapter 11: Appendix E

Advance Commercial Information (ACI)/ eManifest Legend, Use of Special Characters, and Possible Data Loss or Truncation Draft Version 6

1

Revision History

Date Changes Made

Version Changes Made Changes Made By

October 2012 Draft 1.1 Draft for distribution EDI Reporting

October 2012 Draft 2.0 Draft for distribution EDI Reporting

December 2012 Draft 3.0 Draft for distribution EDI Reporting

January 2013 Draft 4.0 Draft version for distribution EDI Reporting

December 2014 Draft 4.5 Draft for internal review EDI Reporting

January 2015 Draft 5 Draft for external distribution, see Summary of Changes.

EDI Reporting

December 2015 Draft 6 Draft for external distribution, see Summary of Changes.

EDI Reporting

2

TABLE of CONTENTS ANSI X12 Legend ....................................................................................................................................................3

Mapping the WCO Data Model to ANSI X12 .................................................................................................4

Explanation of ANSI X12 Message Map Headings ........................................................................................5

Looping Structure Notes ....................................................................................................................................9

ANSI X12 Legend – Highway and Rail ............................................................................................................. 10

Explanation of Message Map Columns ......................................................................................................... 11

EDIFACT GOVCBR Legend ............................................................................................................................... 15

Mapping the WCO Data Model to the EDIFACT GOVCBR ...................................................................... 16

Explanation of GOVCBR Message Map Columns ....................................................................................... 17

Looping Structure Notes ................................................................................................................................. 22

EDIFACT Legend ................................................................................................................................................. 24

Explanation of Message Map Columns ......................................................................................................... 25

Use of Special Characters – Basic and Extended Character Sets.................................................................... 28

ANSI X12 ........................................................................................................................................................... 30

Basic Character Set .......................................................................................................................................30

Extended Character Set ................................................................................................................................30

EDIFACT ........................................................................................................................................................... 31

UNOA Character Set ....................................................................................................................................31

UNOC Character Set ....................................................................................................................................32

Manifest Forward Data Processing .................................................................................................................... 34

Affected Business Data Elements – Manifest Forward Data Loss or Truncation ........................................ 36

ANSI X12 309 MF: Potential Cases of Data Loss or Truncation ................................................................. 37

EDIFACT GOVCBR Manifest Forward Notice: Potential Cases if Data Loss or Truncation ................ 39

ANSI X12 309 and EDIFACT GOVCBR Manifest Forward Notice: Potential Loss of Volume/Capacity

and Weight Codes ............................................................................................................................................ 40

Identifying Cases of Data Loss/Truncation ................................................................................................. 41

3

ANSI X12 Legend

Note: Although the Canada Border Services Agency (CBSA) is committed to both the ANSI X12 and UN/EDIFACT Electronic Data Interchange standards, please be advised that the current message implementation guides published by the CBSA contain some proprietary aspects. The CBSA is working towards ensuring that future versions of these documents will more closely conform to these standards. Should you require any further details on this matter, please contact the Technical Commercial Client Unit at: [email protected].

mailto:[email protected]

4

Mapping the WCO Data Model to ANSI X12

The new CBSA ANSI ASC X12 EDI message implementation guides will use an updated message documentation format. This format is based on the World Customs Organization (WCO) data model. The first section of each EDI guide provides the WCO data model mapping location (i.e. Path) for each CBSA-required data element. The following is an example of the WCO-to-X12 mapping report:

The CBSA-specific required elements are found on the left side:

1. CBSA data element 2. CBSA-specific usage notes (For definitions of data elements, see Appendix A) 3. Unique WCO data model ID number 4. CBSA WCO data model mapping ID number 5. WCO data model Path location for the element

These elements are then mapped to individual locations within the EDI message map on the right side:

SeN – Segment Number, i.e. order number in the series of segments (7)

Se – Segment, i.e. ANSI X12 Segment Name (M11)

CDE – Segment position, i.e. data element placement along the segment line (28)

DE – ANSI X12 Data Element Number (1073)

St – Status (M = Mandatory)

Format – Attribute Format (ID 1/1)

Example – Sample of value input (N) Path – ANSI X12 mapping location within the EDI message (309.P4.LX.M11.1073(0800:028))

5

Explanation of ANSI X12 Message Map Headings

Each segment within the various ANSI X12 message maps contains a number of information columns for each data element. The function and the values of the columns are described below. Counter/Number/Tag Header Counter No Tag St MaxOcc Level Name

0600 LX M 11 2 Transaction Set Line Number

Use additional LX loops for additional occurrences of N1 Delivery Address or N1 Notify Parties or for R4 Routing ONLY. All other LX segments can occur only in the first LX loop.

0800 7 M11

M 1 3 Manifest Bill of Lading Details

Tag A unique two or three alphanumeric tag for reference purposes. The tags are defined within the X12 data element directories. The tag is transmitted within the EDI messages in the order that they are defined. The same segment header will then be repeated on each subsequent segment page for that group (for reference purposes only). In the example above, LX represents the group and M11 represents the relevant segment within the group. Counter This field appears before the Tag and identifies the Group and Segment position within the ANSI X12 message structure. Segment Number The segment count for each individual message map is consecutively sequential and is indicated in the “No” column. This provides a running count of each sequential segment within the map. Group/Segment Status “St” indicates the CBSA-specific status of the Segment Group and of the Segment itself within the group. (See also Looping Structure Notes below.) Values are: M - Mandatory group or segment: must always be transmitted. C - Conditional group or segment: is transmitted if condition for this group or segment

applies. O - Optional group or segment.

Maximum Usage “MaxOcc” indicates the maximum number of occurrences for the respective group and respective segment based on CBSA-specific requirements.

6

Level “Level” indicates the ‘tree’ position within the Message Structure. Name The first “Name” element reflects the CBSA name for the segment group. The second name entry is the CBSA segment name. If there is no specific CBSA name then the ANSI X12 Name of the segment is then provided. ANSI X12 Definitions vs. CBSA Implementation

ANSI X12 Definitions

Standard Syntax

CBSA Implementation

Business Application Attributes

Tag Name St Format St Format Usage / Remark

N4

N4 03 116 Postal Code O ID 3/15 C ID 5/9 Shipper Postal/Zip Code Mandatory if Country is US or Canada

On each segment page, there are two columns. The Standard element being used appears on the left side, along with the Standard definition and the Standard attributes for each element. In the case of ANSI X12 EDI messages, the ASC X12 syntax requirements are displayed on the left side. On the right side, the CBSA-specific requirements are displayed for each of those same elements. In most cases, any Status or Format differences between the two columns will result in CBSA’s requirement being ‘stronger’ than the Standard. In the sample above, the Standard format (i.e. maximum field length) of N403 Postal Code shows ID 3/15 on the left and ID 5/9 on the right. Therefore the error message that a client might expect to receive for the violating the field length for N403 may vary depending on how exactly many characters are provided. In this case for example:

If a client were to transmit a value with 18 characters, they would receive a syntax reject for exceeding the field length since the Standard field length for X12 element 116 is 15.

However, if a client were to transmit a value with 13 characters, the message would pass initial syntax validation but would then be rejected by CBSA’s business application. The reason is that while the client has not exceeded the Standard field length (i.e. 15), they have exceeded the maximum CBSA field length for the same element (i.e. 9).

7

Tag Segment/Element Segment Id

ANSI X12 Definitions

Standard Syntax

CBSA Implementation


Tag Name St Format St Format Usage / Remark

N9

N9 01 128 Reference Identification Qualifier

M ID 2/3 M ID 2/3 CI Unique Consignment Identifier

N9 02 127 Reference Identification C AN 1/80 C AN 1/35 Unique Consignment Reference Unique number assigned to goods, both for import and export. Mandatory if segment is provided

Remark:

Provide UCR in the first instance of LX only

Example:

N9*CI*UNIQUE CONSIGNMENT REFERENCE NUMBER~

The “Tag” column of the map below the header identifies the segment ID tag followed by the element position within the ASC X12 message structure. The element position numbers identify the position of a data element within a segment. Simple data elements are assigned the next sequential number in order of occurrence within the segment. The Tag is followed by the Data Element Number, which is the assigned Reference ID of the ASC X12 Segment or Data Element, as defined in the ASC X12 directories. Simple data elements are identified by unique numbers. Name (data element level) The name of a unique/individual data element within a segment. Status (St) Depending on the message requirement, different rules of “mandatory” or “conditional” use of a data element may apply. In addition, a hierarchy of rules applies; if a segment is conditional but it is used (based on the condition), some of the elements may become mandatory. (See also Looping Structure Notes below.) In addition to the status, some segments may be repeated more than once within a message. M - Mandatory element: must always be transmitted. C - Conditional element: is transmitted if condition for this element applies. O - Optional element. Format The attributes of data type and maximum size are defined in this column. These are described using the ANSI X12 standard of definition as follows: AN – Alphanumeric characters (a to z, 0 to 9, plus special characters) ID – Coded

8

R – Decimal Number N0 – Number DT – Date TM – Time Usage/Remarks This column provides the notes and/or descriptions on the Segment Groups, Segments, and individual data elements. In the case of Date/Time data elements, the format of the date/time is also defined. Additional text will identify the application data elements associated to the ASC X12 data elements. Remark This field at the bottom may provide overall information regarding the use of the segment within the message map, such as the identification of a business rule. Example A sample of the completed segment line is provided that shows the default syntax to be used to separate each field. Default Syntax The ASC X12 message structure is formatted using the Basic Character Set and an asterisk (*) to control the position of data within a segment. In some cases, optional/conditional data elements within a segment must be skipped (if they are not used). In these cases, more than one asterisk will be required after a particular data element. It is important to note that:

o All data must be transmitted in UPPER CASE. o All data must be left justified. o Asterisks must not be used within any data element field. o The pipe ( | ) and (“!”) are not allowed when sending ANSI X12 format EDI

In order to reduce keying errors, The CBSA system will convert the alpha letter ‘o’ to a numeric zero (0) and the letter ‘i’ to a numeric one (1) when they are used in the transmission of the following data elements: Request ID (Cargo Control Number, Conveyance Reference Number, etc.), and Original CCN, Related Release ID, and AQ Follow-up Indicator.

For example, if the client transmits a Cargo report with the following Request ID; "2000jonie12345", CBSA systems will convert it to "2000j0n1e12345". If in the next three years the same client transmits a Cargo report with the following Request ID: "2000j0n1e12345", CBSA systems would see this as a duplicate Request ID and a reject message would be generated. For further information see Use of Special Characters section.

9

Looping Structure Notes

Note that a hierarchy is also applied when determining whether a given loop or segment is mandatory.

Consider the following ASC X12 looping structure sample:

Counter No Tag St MaxOcc Level Content

1000 N1 C 1 3 Consolidator

1000 37 N1 M 1 3 Party Identification

1100 38 N3 M 1 4 Party Location

1100 39 N3 O 1 4 Party Location

1200 40 N4 M 1 4 Geographic Location

1250 41 PER O 1 4 Administrative Communications Contact

1000 N1 C 1 3 Dangerous Goods Contact

1000 42 N1 M 1 3 Party Identification

1250 43 PER M 1 4 Administrative Communications Contact

Each group level is shaded in grey. The “St” column value will indicate if the group and/or given

segment in that group is mandatory. To determine the contents of a given groups, refer to the lines

drawn on the left of the page: the beginning and end of each overall group are delineated; and within

each overall group, additional sub-groups are also delineated. For example, based on the lines drawn

on the left, the first N1 group above contains segments 37 through 41; the second group delineated

incorporates segments 42 and 43. The presence of two additional outer lines on the left indicates that

both of these groups are also part of two larger groups (however not identified in this example).

In the example above, group elements Consolidator and Dangerous Goods Contact are conditional – not

mandatory. That means the message can be properly formatted to pass syntax validation without

necessarily transmitting either of these groups.

Note however that if one of the above groups is transmitted, then certain segments within that group

become mandatory. In the example above, Consolidator as a group element is not mandatory but if it

is transmitted then segments N1, N3 and N4 become mandatory within the Consolidator group.

Similarly Dangerous Goods Contact is not mandatory but if it is transmitted as a group element then

segments N1 and PER become mandatory within the Dangerous Goods Contact group.

10

ANSI X12 Legend – Highway and Rail



11

Explanation of Message Map Columns

Level: The hierarchical level in which a segment appears in the message structure diagram.

Segment / Tag:

AAA – Segment Name

Loop: Name of loop in which the segment is contained.

Repeat / MaxOcc:

Maximum number of times the loop may repeat. This number may be different from the standard to support CBSA’s implementation of the transaction set.

Usage /St: Condition Designator: Mandatory (M), Conditional (C), or Optional (O). CBSA will use “Required” when the standard designates a segment as optional but is mandatory for CBSA’s implementation of the transaction set. CBSA will use “Conditional” when the standard designates a segment or data element as optional but is required by CBSA when certain business conditions are met.

Max Use / MaxOcc:

Maximum number of times the segment may repeat. This number may be different from the standard to support CBSA’s implementation of the transaction set.

Purpose: Segment purpose as defined by the standard.

Syntax: Relational Conditions: (P) Paired or Multiple (R) Required (E) Exclusion (C) Conditional (L) List Conditional

Notes / Remark:

This section will contain notes specific to CBSA’s implementation of the segment or transaction set. (a.k.a. grey notes)

Counter: Specifies the position number for the EDI segment.

No:

(Number) CBSA reference data. Provides a count of the number of the EDI segments that are

being utilized in CBSA’s EDI Message Map.

12

2

3

4

5

6

1 7

8

9

A

B

C

Segment Diagram

Segment Identifier Segment Terminator

Data Element Reference Designator

Data Element Separator

Data Element Reference Number Condition Designator

Reference Designator * Data Element Type

Component Element Separator * Data Element Length (Max/Min)

Composite Data Structure Number *

Composite Data Structure *

* N/A for eManifest Deployment 4 Note: Only those elements used by CBSA will be displayed.

01 123 02.1 C000 234 02.2 C000 345

AAA * Simple Data Element * Component Data

Element 1 : Component Data Element 2

N/L

M ID 3/3 M AN 1/30 O N0 1/5

1 2 3 4 5 6 7

8 9 A B

C

13

Sample Format

Data Element Summary REF.DES. DATA ELEMENT NAME ATTRIBUTES

01 123 ABC Qualifier M ID 2/2

CODE DEFINITION

00 Definition

Definitions: Segment: A unique two or three alphanumeric tag for reference purposes. The tags are defined within the X12 data element directories. The tag is transmitted within the EDI messages in the order that they are defined. Ref Des: The segment ID tag followed by the element position (“Data Element Reference Designator”) within the ASC X12 message structure. The element position numbers identify the position of a data element within a segment. Simple data elements are assigned the next sequential number in order of occurrence within the segment. Data Element: The assigned Reference ID of the ASC X12 Segment or Data Element, as defined in the ASC X12 directories. Simple data elements are identified by unique numbers. Name: The name of a unique/individual data element within a segment. Attributes: Lists the Condition Designator, Data Element Type and Data Element Length (Max/Min). Condition Designator: M – Mandatory O – Optional M/Z – Mandatory with a semantic note O/Z – Optional with a semantic note X – These elements are optional; however, where one value is provided, an immediately preceding or succeeding value must also be provided. X/Z – Conditional with ANSI X12 semantic note Z – ANSI X12 semantic note. Data Element Type: AN – Alphanumeric characters (a to z, 0 to 9, plus special characters) ID – Coded R – Decimal Number

14

N0 – Number DT – Date TM – Time Code: Details of the content of the data element, the expected values/codes or the applicable application data element to be supplied. In the case of Date/Time data elements the format of the date/time is also defined. Definition: Notes and/or descriptions on the Segment Groups, Segments, and individual data elements. Grey notes will identify the application data elements associated to the ASC X12 data elements.

Default Syntax:

The ASC X12 message structure is formatted using the Basic Character Set and an asterisk (*) to control the position of data within a segment. In some cases, optional/conditional data elements within a segment must be skipped (if they are not used). In these cases, more than one asterisk will be required after a particular data element. It is important to note that:

o All data must be transmitted in UPPER CASE. o All data must be left justified. o Asterisks must not be used within any data element field. o The pipe ( | ) and (“!”) are not allowed when sending ANSI format EDI

In order to reduce keying errors, The CBSA system will convert the alpha letter ‘o’ to a numeric zero (0) and the letter ‘i’ to a numeric one (1) when they are used in the transmission of the following data elements: Request ID (Cargo Control Number, Conveyance Reference Number, etc.), and Original CCN, Related Release ID, and AQ Follow-up Indicator. For example, if the client transmits a Cargo report with the following Request ID; "2000jonie12345", CBSA systems will convert it to "2000j0n1e12345". If in the next three years the same client transmits a Cargo report with the following Request ID: "2000j0n1e12345", CBSA systems would see this as a duplicate Request ID and a reject message would be generated. For further information see Use of Special Characters.

15

EDIFACT GOVCBR Legend



16

Mapping the WCO Data Model to the EDIFACT GOVCBR

New CBSA EDIFACT GOVCBR EDI message implementation guides related to House Bills and Multi-modal Cargo will use an updated message documentation format. This format is based on the World Customs Organization (WCO) data model. The first section of each EFI guide provides the WCO data model mapping location (i.e. Path) for each CBSA-required data element. The following is an example of the WCO-to-EDIFACT GOVCBR mapping report:

The CBSA-specific required elements are found on the left side:

1. CBSA data element 2. CBSA-specific usage notes (For definitions of data elements, see Appendix A) 3. Unique WCO data model ID number 4. CBSA WCO data model mapping ID number 5. WCO data model Path location for the element

These elements are then mapped to individual locations within the EDI message map on the right side:

SeN – Segment Number within the series of segments (19)

Se – Segment, i.e. Segment name (STS)

CDE – Segment position, i.e. data element placement along the segment line (10) o – (if applicable) EDIFACT Composite Element Number (C555)

DE – EDIFACT Data Element number (4405)

St – Status (M = Mandatory)

Format – Attribute Format (an..3)

Example – Sample of value input (1)

GOVCBR-specific Remarks may be included above the “Path” line (1 = Yes 0 = No) Path – GOVCBR mapping location within the EDI message

(GOVCBR.SG138.STS.C555.4405(6010:020:01))

17

Explanation of GOVCBR Message Map Columns

New CBSA EDIFACT messages will use the GOVCBR message type. Information on the GOVCBR message type can be found at http://www.unece.org/trade/untdid/d11b/trmd/govcbr_c.htm. The message maps contain a number of information columns for each data element. The function and the values of the columns are described below. Counter/Number/Tag Header Counter No Tag St MaxOcc Level Name

6760 SG156 C 999 2 Equipment/Seals

6780 57 SEQ M 1 3 Sequence details

Tag Every EDIFACT GOVCBR group (a group of associated segments) is assigned an “SG” (i.e. “Segment Group”) number for reference purposes. The group number (e.g. “SG156”) identifies the relevant section within the GOVCBR message structure. These group numbers are not transmitted within the message and are provided for reference purposes only. This is the first item noted in the “Tag” header column. Every EDIFACT segment (a group of associated data elements) is assigned a unique 3 alpha “Tag” for reference purposes (e.g. “SEQ” above). The tags are defined within the EDIFACT data element directories. Unlike the segment group numbers, it should be noted that each tag is transmitted within the EDI messages, in the order that it is defined. Counter This field appears before the Tag and identifies the Group and Segment position within the EDIFACT message structure. The Segments are numbered in ascending values of 10 for each occurrence of a segment in the message structure. These ascending values of 10 are noted in the “Counter” column and indicate the position within the overall GOVCBR message structure. Since the GOVCBR has many hundreds of segments, it is possible for many unused segments to be skipped. Therefore the counter will not appear to be consecutively sequential.

Segment Number The segment count for each individual message map however is consecutively sequential and is indicated in the “No” column. This provides a running count of each sequential segment within the map.

http://www.unece.org/trade/untdid/d11b/trmd/govcbr_c.htm

18

Group/Segment Status “St” indicates the status of the Segment Group and of the Segment itself within the group. (See also Looping Structure Notes below.) Values are: M - Mandatory group or segment: must always be transmitted. C - Conditional group or segment: is transmitted if condition for this group or segment

applies. Note: There is no “O” for optional in the GOVCBR. All optional elements are considered conditional in

the EDIFACT standard. The term mandatory if segment is provided means Conditional. Maximum Usage “MaxOcc” indicates the maximum number of occurrences for the respective group and respective segment based on CBSA-specific requirements. Level “Level” indicates the ‘tree’ position within the Message Structure. Name The “Name” in the SG section reflects the CBSA name for the segment or segment group. If no CBSA name is provided the UN/EDIFACT Name of the segment is shown. UN/EDIFACT Definitions vs. CBSA Implementation

UN/EDIFACT Definitions

EDIFACT GOVCBR Standard Syntax

CBSA Implementation


Tag Name Pos Place St Forma St Format Usage / Remark

NAD

3251 Postal identification code 080 C an..17 C an..9 Notify Party Postal/Zip Code Mandatory if Country is US or Canada

On each segment page, there are two columns. The Standard element being used appears on the left side, along with the Standard definition and the Standard attributes for each element. In the case of the GOVCBR, UN/EDIFACT syntax requirements are displayed on the left side. On the right side, the CBSA-specific requirements are displayed for each of the same elements. In most cases, any Status or Format differences between the two columns will result in CBSA’s

requirement being ‘stronger’ than the Standard. In the sample above, the Standard format (i.e.

maximum field length) of field 3251 Postal Code shows an..17 on the left and an..9 on the right.

Therefore the error message that a client might expect to receive for the violating the field

length for element 3251 may vary depending on how exactly many characters are provided. In

this case for example:

If a client were to transmit a value with 18 characters, they would receive a syntax reject since the Standard field length for element 3251 is 17.

19

However, if a client were to transmit a value with 15 characters, the message would pass initial syntax validation but would then be rejected by CBSA’s business application. The reason is that while the client has not exceeded the Standard field length (i.e. 17), they have exceed the maximum CBSA field length for the same element (i.e. 9).

Tag Segment/Element Segment Id Tag Name Pos Place St Forma St Format Usage / Remark

SEQ

1229 Action code 010 C an..3 M an..3 4 No action

Remark:

Mandatory trigger segment for syntax purposes

Example:

SEQ+4'

The “Tag” column of the map below the header identifies the alphanumeric or numeric identifier of each of the UN/EDIFACT segments and data elements. There are three (3) types of data elements defined. Descriptions of each are provided below. It should be noted that the Element IDs are not transmitted within the message, only the value of the data element is transmitted in the appropriate position within the segment. COMPOSITE DATA ELEMENT NAME: Identifies a high level name of a set of associated data elements. The associated data elements are referred to as "component" data elements. Composites are identified by a single alpha character (C or S) followed by 3 unique numerics and will appear left-justified within the column. COMPONENT DATA ELEMENT: Identification of a component data element which is part of a composite data element. Component data elements are identified by 4 unique numerics. This value will appear indented under its respective composite data element. SIMPLE DATA ELEMENT NAME: Name of a unique/individual data element within a segment, a "simple" data element contains one element for a single function/use. Simple data elements are identified by 4 unique numerics and will appear left-justified within the column. Name (data element level) This column provides the name of the CBSA Segment, Composite, Component or Simple Data elements, derived from the UN/EDIFACT directories.

20

Element Position/Placement This column of the map identifies the Element position within the EDIFACT message structure. The Element position numbers identify the position of a data element within a segment. In the EDIFACT documentation the Composite data elements and Simple data elements are numbered in a segment using 3-digit numbers. They are assigned ascending values of 10 for each occurrence of a composite or simple data element. If an element is not used then 'not used' may appear under usage. To more specifically identify the data element positions, each Composite is assigned an incrementing number. Within each composite, the component data elements are assigned a sequential subordinate number that represents the actual field placement on the line, regardless of the syntax separator used. This will be indicated in the map as a single number with no leading zeros. Only the component data elements of a composite will display the actual position number on the line. Otherwise the 3-digit position will be displayed alone, for example: UN/EDIFACT Definitions

EDIFACT GOVCBR Standard Syntax

CBSA Implementation


Tag Name Pos Place St Forma St Format Usage / Remark

NAD

3035 Party function code qualifier

010 M an..3 M an..3 CN Consignee

C082 Party identification details 020 C N

3039 Party identifier 2 M an..35 N Not used

C058 Name and address 030 C N

3124 Name and address description

3 M an..35 N Not used

C080 Party name 040 C M

3036 Party name 4 M an..70 M an..70 CBSA Consignee Name

C059 Street 050 C M

3042 Street and number or post office box identifier

5 M an..35 M an..35 Consignee Address Max 105 characters. Address Line 1 (M), 2 and 3 (C) Address Line 1 (M): first instance of EDIFACT element 3042


6 C an..35 C an..35 Address Line 2 (C): second instance of EDIFACT element 3042


7 C an..35 C an..35 Address Line 3 (C): third instance of EDIFACT element 3042

3164 City name 060 C an..35 M an..35 Consignee City

C819 Country subdivision details 070 C C

3229 Country subdivision identifier

9 C an..9 C an2 Consignee Province/State Code Coded Value. Mandatory if Country is US or Canada. See ECCRD Code Table #2 for valid Province/State codes. Syntax note: For this field, provide only the portion of coded data that refers to the Province/State. (Do not provide the portion of the coded data value that refers to the Country.)

3251 Postal identification code 080 C an..17 C an..9 Consignee Postal/Zip Code Mandatory if Country is US or Canada For a Canadian Postal Code, use one of the following formats: A1A1A1, A1A 1A1, or A1A-1A1. For a US Zip Code, supply up to 9 characters (no dash).

3207 Country identifier 090 C an..3 M an2 Consignee Country Code Coded Value. See ECCRD Code Table #3 for valid Country codes.

21

Remark:

Commercial Invoice or other sales document. In circumstances where the freight is consolidated and will be further broken down by a freight forwarder, the "consignee" provided is as shown on the carrier's contract of carriage. The carrier will provide the consignee as shown on their contract of carriage.

Example:

NAD+CN+++CONSIGNEE NAME+CONSIGNEE ADDRESS LINE 1:CONSIGNEE ADDRESS LINE 2:CONSIGNEE ADDRESS LINE

3+CONSIGNEE CITY NAME+ON+N1N 1N1+CA'

Status (St) Depending on the message requirement, different rules of “mandatory” or “conditional” use of a data element may apply. In addition, a hierarchy of rules applies; if a segment or composite data element is conditional but it is used (based on the condition) some of the subordinate elements may be mandatory. (See also Looping Structure Notes below.) In addition to the status, some segments may be repeated more than once within a message. M - Mandatory element: must always be transmitted. C - Conditional element: is transmitted if condition for this element applies. Format The attributes of data type and maximum size are defined in this column. These are described using an EDIFACT standard of definition as follows: a = Alpha characters (a to z) n = Numeric characters (0 to 9) an = Alphanumeric characters (a to z, 0 to 9, plus special characters) .. = Two periods indicate a variable length field or else it is a fixed length field Examples: a5 = alpha must be 5 in length a..5 = alpha up to 5 in length n15 = numeric must be 15 in length an..12 = alpha numeric up to 12 in length an9..15 = alpha numeric, must be minimum 9 characters, up to 15 allowed Usage/Remarks This column provides the details of the content of the data element, the expected values/codes or the applicable application data element to be supplied. In the case of Date/Time data elements, the format of the date/time is also defined. This column also provides notes and/or descriptions on the Segment Groups, Segments and individual data elements. It will also identify the application data elements associated with the EDIFACT data elements. In many cases mandatory EDIFACT codes are used to qualify the data element being supplied. In these cases, the descriptions of the EDIFACT code values are provided.

22

Remark This field at the bottom may provide overall information regarding the use of the segment within the message map, such as the identification of a business rule. Example A sample of the completed segment line is provided. Default Syntax The EDIFACT message structure is formatted using a set of special characters to control the position of data within a segment. The required EDIFACT syntax to be transmitted after each value is provided in the above sample. In some cases conditional data elements within a segment must be “skipped” (if they are not used). In these cases more than one syntax character has been specified after a particular data element. For further information on the use of syntax and special characters refer to the Use of Special Characters section.

Looping Structure Notes

Note that a hierarchy is also applied when determining whether a given loop or segment is mandatory.

Consider the following GOVCBR looping structure sample:

Counter No Tag St MaxOcc Level Content

6070 SG139 C 1 2 Place of Consolidation

6080 37 NAD M 1 2 Name and address

6110 SG140 C 1 3 Place of Consolidation Contact Name

6120 38 CTA M 1 3 Contact information

6110 SG140 C 1 3 Place of Consolidation Contact Number

6120 39 CTA M 1 3 Contact information

6130 40 COM M 1 4 Place of Consolidation Contact Number

6340 SG146 C 1 2 Dangerous Goods Special Instructions

6350 51 RCS M 1 2 Requirements and conditions

6360 52 FTX M 1 3 Free text

Each group level is shaded in grey. The “St” column value will indicate if the group and/or given

segment in that group is mandatory. To determine the contents of a given groups, refer to the lines

drawn on the left of the page: the beginning and end of each overall group are delineated; and within

each overall group, additional sub-groups are also delineated. For example, based on the lines drawn

on the left, the SG139 group above contains segments 37 through 40. SG139 also contains sub-group

SG140, of which two instances are displayed above (i.e. segments 38, 39 and 40). The second group

example delineated (SG146) incorporates segments 51 and 52. The presence of one additional outer line

on the left of each group indicates that both of these groups are part a larger group (however not

identified in this example).

23

In the examples above, group elements Place of Consolidation and Dangerous Goods Special Instructions

are conditional – not mandatory. That means the message can be properly formatted to pass syntax

validation without necessarily transmitting either of these overall groups.

Note however that if one of the above groups is transmitted, then certain segments within that group

become mandatory. In the example above, Place of Consolidation as a group element is not mandatory

but if it is transmitted then only segment NAD becomes mandatory within the Place of Consolidation

group (SG139). Place of Consolidation also contains two additional sub-groups, i.e. two instances of

SG140, each of which is conditional to the use of SG139. If either instance of SG140 is transmitted, then

CTA becomes mandatory in the first instance; both CTA and COM become mandatory in the second

instance.

Similarly Dangerous Goods Special Instructions (SG146) is not mandatory but if it is transmitted as a

group element then segments RCS and FTX become mandatory within the Dangerous Goods Special

Instructions group.

24

EDIFACT Legend



25

Explanation of Message Map Columns

The message map contains a number of information columns for each data element. The function and values of the "columns" are described below. UN/EDIFACT Segment ID. Every EDIFACT segment (a group of associated data elements) is assigned a unique three alpha "Tag" for reference purposes. The tags are defined within the EDIFACT data element directories. It should be noted that the "tag" is transmitted within the EDI messages in the order that they are defined. UN/EDIFACT Element ID This column of the map identifies the alphanumeric or numeric identifier of each of the UN/EDIFACT data elements. There are three (3) types of elements defined. Descriptions of each are provided below. It should be noted that the Element IDs are not transmitted within the message, only the value of the data element is transmitted in the appropriate position within the segment. Composite Data Element Name - Identifies a high level name of a set of associated data elements. The

associated data elements are referred to as "component" data elements. Composites are identified by a single alpha character (C or S) followed by three unique numerics.

Component Data Element Name - Identification of a component data element which is part of a

composite data element. Component data elements are identified by four unique numerics.

Simple Data Element Name - Name of a unique/individual data element within a segment, a

"simple" data element contains one element for a single function/use. Simple data elements are identified by four unique numerics.

Segment/Element Position This column of the map identifies the Segment or Element position within the CUSREP message

structure. The Segments are numbered in ascending values of 10 for each occurrence of a segment

in the message structure. The Element position numbers identify the position of a data element

within a segment. In the EDIFACT documentation only Composite data elements and Simple

data elements are numbered in a segment. They are assigned ascending values of 10 for each

occurrence of a composite or simple data element. To more specifically identify the data element

positions, each Composite is assigned an incrementing number starting at 1. Within each

26

composite, the component data elements are assigned a sequential subordinate number. Simple

data elements are assigned the next sequential number in order of occurrence within the

segment. An example is as follows:

UN/EDIFACT Definitions: Mapping Definitions: Seg. Pos. Element

Pos. Seg. Pos. Element

Pos.

0010 UNH Message Header

Message Header 0010 UNH

0062 Message Reference Number

10 Message Reference Number 0062 1

S009 Message Identifier

20 Message Identifier S009 2

0065 Message Type

Message Type 0065 2.1

0052 Message Version Number

Message Version Number 0052 2.2

0054 Message Release Number

Message Release Number 0054 2.3

0051 Controlling Agency

Controlling Agency 0051 2.4

EDIFACT Data Element Names This column provides the name of the EDIFACT Segment, Composite, Component, or Simple Data element, as defined in the UN/EDIFACT directories. Notes and Descriptions This column of the map provides notes and/or descriptions on the Segments Groups, Segments, and individual data elements. It also will identify the application data elements associated to the EDIFACT data elements. In many cases mandatory EDIFACT codes are used to qualify the data element being supplied. In these cases the description of the EDIFACT codes values are provided. Data Type/Size The attributes of data type and maximum size are defined in this column. These are described using an EDIFACT standard of definition as follows: A = Alpha characters (a to z) N = Numeric characters (0 to 9) AN = Alphanumeric characters (a to z, 0 to 9, plus special characters) .. = Two periods indicate a variable length field, else it is a fixed length field. Examples: A5 = alpha must be 5 characters in length; A..5 = alpha up to 5 characters in length; N15 numeric must be 15 characters in length;

27

AN..12 = alpha numeric up to 12 characters in length. AN9..15 = alpha numeric, must be a minimum of 9 characters, up to 15 characters. Codes and Values This column provides the details of the content of the data element, the expected values/codes or the applicable application data element to be supplied. In the case of Date/Time data elements the format of the date/time is also defined. Default Syntax The EDIFACT message structure is formatted using a set of special characters to control the position of data within a segment. The required EDIFACT syntax to be transmitted after each value is provided in this column. In some cases conditional data elements within a segment must be “skipped” (if they are not used). In these cases more than one syntax character has been specified after a particular data element. Error Response or RNS The syntax of the message will depend on if it is an error response to an inbound arrival or Query message or the message is issued as a Release Notification System (RNS). The two columns describe the status (mandatory or conditional – occurrence count) as described below. Status - Mandatory or Conditional - Occurrence Count Depending on the message requirement different rules of "mandatory" or "conditional" use of a data element may apply. In addition a hierarchy of rules apply, if a segment or composite data element is conditional, but it is used (based on the condition) some of the subordinate elements may be mandatory. In addition to the status some segments may be repeated more than once within a message, if there is a repeat factor this is also specified in this column. M = Mandatory element, must always be transmitted. C = Conditional element, is transmitted if the application condition for this

element applies. M3 = A number after the condition indicates the number of occurrences at the

segment level. (e.g. Mandatory 3 times) N/A = Not applicable for the particular message type.

28

Use of Special Characters – Basic and Extended Character

Sets

29

The following is a list of the character sets used for ANSI X12 and EDIFACT EDI inbound and outbound message transmissions. This section also provides a list of the special characters that may be dropped or altered and other EDI formatting that clients may be required to receive for the ANSI X12 or EDIFACT Manifest Forward. It is possible for CBSA to receive and store incoming field text data from an inbound transmission method which contains formatting that is exceptional to (i.e. may conflict with) a different outbound EDI standard. Examples of this could include e.g. lower case letters, special characters or French formatting, all of which can be input via the Portal. For the purposes of generating the outbound Manifest Forward (MF) Notice using either the ANSI X12 309 or EDIFACT GOVCBR, it is possible that CBSA will use a different outbound character set than is accepted on corresponding inbound EDI Cargo messages. For example, special characters, French text and/or lower case letters can all be received via the eManifest Portal web application and are subsequently stored in CBSA’s system. These same characters would then be generated on the outbound MF client, who may be receiving the outbound MF notice using either ANSI X12 309 or GOVCBR.

ANSI X12 and EDIFACT In order to reduce keying errors, the CBSA system will convert the alpha letter ‘o’ to a numeric zero (0) and the letter ‘i’ to a numeric one (1) when they are used in the transmission of the Cargo Control Number and Conveyance Reference Number. For example, if the client transmits a Cargo report with the following Request ID, 8000jonie12345, CBSA systems will convert it to 8000j0n1e12345. If in the next three years the same client transmits a Cargo report with the following Request ID: 8000j0n1e12345, CBSA systems would see this as a duplicate Request ID and a reject message would be generated. NOTE: the pipe (“|”) and exclamation mark (“!”) are not allowed when sending either ANSI X12 or EDIFACT format EDI.

30

ANSI X12 As noted in the ANSI X12 Legend, CBSA accepts only the Basic Character Set on inbound EDI transmissions.

Basic Character Set

The basic character set of this standard consists of uppercase letters, digits, special characters, and space.

(1) Uppercase letters from A to Z:

<uppercase_letter> ::= "A" | ... | "Z"

(2) Digits from 0 to 9:

<digit> ::= "0" | ... | "9"

(3) Special characters:

<special_char> ::= """ | "&" | "'" | "(" | ")" | "*" | "+" | "," | "-" | "." | "/" | ":" | ";" | "?" | "="

NOTE: Special characters are removed from this category when used as delimiters.

(4) The space character:

<space> ::= " "

However, since the inbound Cargo record can be received via the eManifest Portal web application, the outbound ANSI X12 309 MF from CBSA must allow for the X12 Extended

Character Set. This document therefore serves as the agreement between “communicating parties”, i.e. CBSA and its EDI clients, as noted in the Extended Character Set notes below.

Extended Character Set

An extended character set may be used by agreement between communicating parties and includes the lowercase letters, other special characters, national characters and select language characters.

(1) Lowercase letters from a to z: <lowercase_letter> ::= "a" | ... | "z"

(2) Other special characters: <other_special_char> ::= "%" | "@" | "[" | "]" |"_" | "{" | "}" |

"\" | "|" | "<" | ">" | "~" | "^" | "`"

NOTE: Special characters are removed from this category when used as delimiters.

CBSA does not use the Extended Character "|" on outbound transmissions.

(3) National characters: <national_char> ::= "#" | "$"

31

(4) Select language characters:

<select_language_char> ::= “À”|”Á”|”Â”|”Ä”|”à”|”á”|”â”|”ä”|

“È”|”É”|”Ê”|”è”|”é”|”ê”|”ë”| ”Ì”|”Í”|”Î”|”ì”|”í”|”î”|”ï”| “Ò”|”Ó”|”Ô”|”Ö”|”ò”|”ó”|”ô”|”ö”| ”Ù”|”Ú”|”Û”|”Ü”|“ù”|”ú”|”û”|”ü”| ”Ç”|”ç”|”Ñ”|”ñ”|”¿”|”¡”

NOTE: See ISO document 8859-1 (Latin-1 Alphabet) for an example of an encoding of select language characters. NOTE: The following special characters will be removed from any free text field on the ANSI X12 outbound MF notice:

| "@" | "$" | "%" | "&" | "^" | "’" | "+" | ":" | "?" | "*" | "!" | "~" |

EDIFACT The EDIFACT character sets are identified on the UNB line of the EDI message header. CBSA’s internal system requires that the UNB Special Character Identifier displays restricted character set “UNOA” on all inbound and outbound message maps.

UNOA Character Set

The UNOA character set includes the following: Letters, upper case: A to Z Numerals: 0 to 9 Space character: ___ Full stop: . Comma: , Hyphen/minus sign: - Opening parentheses: ( Closing parentheses: ) Oblique stroke (slash): / Equals sign: =

Reserved for use: Apostrophe: ' segment terminator Plus sign: + segment tag and data element separator Colon: : component data element separator Question mark: ? release character

NOTE: Question mark (?) immediately preceding one of the reserved characters (', +, :, or ?) restores their normal meaning.

e.g. 10?+10=20 means 10+10=20.

32

However, CBSA will actually be using set UNOC for the character set on the outbound EDIFACT GOVCBR Manifest Forward Notice. Unfortunately due to CBSA’s current system limitations, CBSA will be unable to display the letters “UNOC” in outbound MF element UNB.S001.0001 Syntax Identifier until a future date. This limitation also applies to any standard EDIFACT CUSRES response messages. For example, a client may receive an EDIFACT 08A syntax response error message in this format: UNB+UNOA:3+RCCEXXXXX:ZZ+XXXX:02+130722:1151+376602' … FTX+AAO+++SEGMENTGEILINE12ELEM7364[2.4]MAND ELEM MISSING' Note the presence of square brackets (part of the UNOC character set) on the FTX line, yet the character set is defined on the UNB line as “UNOA”. Clients will have to program for this anomaly.

UNOC Character Set

The UNOC (ISO/IEC 8859-1) Character Set includes all of the UNOA characters plus the following:

Latin 1 - 5, Cyrillic, Arabic, Greek and Hebrew alphabets Letters, lower case: a to z Exclamation mark: ! Quotation mark: " Percentage sign: % Ampersand: & Asterisk: * Semi-colon: ; Less-than sign: < Greater-than sign: > Number sign: # Commercial at: @ Left square bracket: [ Reverse solidus: \ Right square bracket: ] Circumflex accent: ^ Grave accent: ` Left curly bracket: { Vertical line: | Right curly bracket: }

NOTE: The following special characters will be removed from any free text field on the EDIFACT GOVCBR outbound MF notice:

| "@" | "$" | "%" | "&" | "^" | "?" | "*" | "!" | "~" |

33

The escape character (?) will be inserted in front of the following special character entries: a. A colon (:); b. An apostrophe (‘); and c. A plus sign (+)

Example: IF a Cargo report had been assigned Cargo description ‘BOB’S BURGERS’, THEN the outbound EDIFACT GOVCBR MF notice will be assigned the following EDI syntax for the Cargo description field:

FTX+AAA+++BOB?’S BURGERS

34

Manifest Forward Data Processing

35

Clients may use Electronic Data Interchange messages (ANSI X12 309) or EDIFACT GOVCBR or the eManifest Portal web application to submit an electronic Cargo report to CBSA. Within CBSA’s Cargo report, a client may choose to identify one or more Secondary Notify Parties (SNPs) that are to be sent an electronic copy of the Cargo report submission, i.e. the EDI Manifest Forward Notice (MF). Future Use Note: At a future date the option to send the EDI MF will also apply to inbound eManifest Multi-modal Cargo. However, please note that at the present time, the only Cargo report to which the MF applies is the EDI House Bill. Therefore throughout this section and until further notice, both the terms “Cargo” and “MF” apply to House Bill Cargo and/or House Bill MF records only. The EDI and eManifest Portal versions of CBSA’s Cargo report possess the same business data elements. There are instances however, where the incoming Cargo data is received in a different format than the outgoing MF data, depending on the transmission method used to transmit vs receive the data. As a result, there are a few cases in which these versions possess different maximum occurrence and field length restrictions for certain Cargo business data elements. For this reason, with respect to maximum occurrence and field length restrictions, CBSA may be required to omit or truncate certain business data entries when generating an outbound MF. As noted in the Use of Special Characters section, CBSA may also include certain text formatting such as lower case letters; and CBSA may also exclude certain special characters that were provided on the inbound message. For potential loss and truncation of data, this appendix provides a list of the affected Cargo business data elements, and describes CBSA’s measures for identifying cases where data has been omitted or truncated in the outbound MF. Note the following:

eManifest Portal clients will not be affected by cases of data loss or truncation when viewing a Cargo MF within the eManifest Portal web application. There is no limit placed on the use of special characters, nor on the use of lower case or French lettering.

EDI clients could be affected by cases of data loss or truncation or change if the MF had been generated using a different EDI message format than the source Cargo report submission.

Examples: o CBSA may receive a GOVCBR Cargo report submission from an EDI client, and may

be required to send an ANSI 309 MF to one or more SNPs. o CBSA may receive a Cargo report submission from an eManifest Portal client, and

may be required to send an EDI MF to one or more SNPs that are registered EDI clients.

36

Affected Business Data Elements – Manifest Forward

Data Loss or Truncation

37

The following list identifies specific business data elements that may experience cases of data loss or truncation in the outbound Manifest Forward (MF) Notice.

Legend

SCENARIO 1: Due to EDI field length restrictions, a business data entry may become truncated in an outbound MF. When this event occurs, the ampersand symbol (&) will be assigned to the last position of the affected EDI data field.

SCENARIO 2: CBSA may be required to convert a numeric business data entry into an integer value in order to satisfy the field length restrictions for an EDI MF. If the integer value exceeds the field length restrictions for an EDI MF, then CBSA will assign zero (0) to the affected EDI data field.

SCENARIO 3: Due to EDI looping restrictions, one or more business data entries may need to be omitted from an outbound EDI MF. When this event occurs, the text “MORE/PLUS” will be assigned to the last occurrence of the looped business data entry.

ANSI X12 309 MF: Potential Cases of Data Loss or Truncation

Business Data Element

Affected EDI Elements

Data Loss / Truncation Category

EDI Discrepancy CBSA Resolution Measure

Named Party * - Name

N102 (Name) Data truncation ANSI AN 1/60

EDIFACT an..70 SCENARIO 1

Named Party * - City

N401 (City Name) Data truncation ANSI AN 1/30 EDIFACT an..35

SCENARIO 1

Named Party * - Province/State Code

N407 (Country Subdivision Code)

Data truncation ANSI AN 1/3 EDIFACT an..9

SCENARIO 1

Named Party * - Administrative Communications Contact Name

PER02 (Name) Data truncation ANSI AN 1/60

EDIFACT an..70 SCENARIO 1

Notify Party Contact

N1 (Notify Party) N1 – Party Identification N3 – Party Location N4 – Geographic Location PER – Administrative

Omission of one or more business data entries

ANSI MaxOcc < 20 EDIFACT MaxOcc = 99

SCENARIO 3

38


Affected EDI Elements

Data Loss / Truncation Category


Communications Contact

Delivery Address Contact

N1 (Delivery Address) N1 – Party Identification N3 – Party Location N4 – Geographic Location PER – Administrative Communications Contact


ANSI MaxOcc < 20 EDIFACT MaxOcc = 99

SCENARIO 3

Seal Number M7 (Seal Numbers) Omission of one or more business data entries

ANSI MaxOcc = 22; EDIFACT MaxOcc = 40

SCENARIO 3

Cargo Weight M1105 (Weight) Cannot output client-supplied numeric entry value

ANSI R 1/10 EDIFACT n..13

SCENARIO 2

Volume M1107 (Volume) Cannot output client-supplied numeric entry value

ANSI R 1/8 EDIFACT n..13

SCENARIO 2

Marks and Numbers

N1003 (Marks and Numbers)

Data truncation ANSI AN 1/48

EDIFACT an..35 eManifest Portal an..50

SCENARIO 1

* Note: Named Party refers to one of the following entities: Shipper, Consignee, Notify Party, Delivery Address, Place of Consolidation, Consolidator, and Dangerous Goods Contact

39

EDIFACT GOVCBR Manifest Forward Notice: Potential Cases if Data Loss or

Truncation


Affected EDI Elements Data Loss / Truncation Category


Equipment Details

SG156 (Equipment) EQD – Equipment details SEQ – Sequence details


EDIFACT MaxOcc = 99 ANSI MaxOcc = 999

SCENARIO 3

Special Instructions

SG138 (Consignment Loop) HAN (Handling instructions) 4078 (Handling instruction description)

Data truncation EDIFACT an..256 ANSI AN 1/80 x 4 (Max 300 chars) eManifest Portal an..300

SCENARIO 1

Cargo Quantity SG193 (Quantity) PAC (Quantity/Type Code) 7224 (Package quantity)

Cannot output client-supplied numeric entry value

EDIFACT n..8 ANSI R 1/15

SCENARIO 2

Marks and Numbers

SG193 (Marks & Numbers) PCI (Marks & Numbers) 7102 (Marks and Numbers)

Data truncation EDIFACT an..35 ANSI AN 1/48 eManifest Portal an..50

SCENARIO 1

UNDG Code SG200 (Goods loop) TCC (UNDG Code)


EDIFACT MaxOcc = 98** ANSI MaxOcc = 99 **A client can loop EDI segment TCC up to 99 times to assign a given commodity entry one HS Code and 98 UNDG Codes.

SCENARIO 3

40

ANSI X12 309 and EDIFACT GOVCBR Manifest Forward Notice: Potential

Loss of Volume/Capacity and Weight Codes

Volume/Capacity Code Translation Tables

VOLUME/CAPACITY

ANSI X12 309 Code EDIFACT GOVCBR Code

Unit of Measure Name

C CMQ Cubic Centimetre

M DMQ Cubic Decimetre

X MTQ Cubic Metre

V LTR Litre

Weight Code Translation Tables

WEIGHT

ANSI X12 309 Code EDIFACT GOVCBR Code

Unit of Measure Name

L LBR Pound

K KGM Kilogram

E TNE Metric Ton

Note: For both tables, the default codes are Z for ANSI X12 309 and ZZZ for GOVCBR

If the CBSA receives a valid Volume/Capacity or Weight Unit of Measure Code that is defined in the Code Translation Tables provided above, the appropriate converted code entry value will be assigned to the outbound ANSI X12 309 or GOVCBR MF. If a Volume/Capacity or Weight Unit of Measure Code that is not defined in the Code Translation Tables is received by the CBSA, the CBSA will assign a default code entry (i.e. Z or ZZZ) to the outbound ANSI X12 309 or GOVCBR MF. The default code entry value indicates that the CBSA was not able to output the original Volume/Capacity or Weight Unit of Measure Code entry value.

41

Identifying Cases of Data Loss/Truncation CBSA has implemented the following measures to identify a business data element that has been affected by data loss or truncation in the outbound EDI MF: SCENARIO 1: The ampersand symbol (&) has been assigned to the last position in an alphanumeric data field.

The ANSI X12 309 and GOVCBR versions of CBSA’s electronic Cargo report possess different field length restrictions for a few business data elements. When generating an outbound EDI MF, if CBSA is unable to assign the full contents of an alphanumeric business data entry to a given data field, then CBSA will truncate the business data entry to satisfy the field length restrictions, and will assign the ampersand symbol (&) to the last position in the data field.

Example:

An ANSI X12 09 Cargo Report can be assigned up to 60 characters for the Shipper Name (AN 1/60), whereas the GOVCBR Cargo Report can be assigned up to 70 characters for the Shipper Name (an..70).

Suppose that CBSA is required to assign the following Shipper Name entry to an outbound ANSI X12 309 MF:

SUPERCALIFRAGILISTICEXPIALIDOCIOUS SHIPPING COMPANY OF AMERICA

In the outbound ANSI X12 309 MF, CBSA will reduce the length of this Shipper Name entry to 60 characters, and will assign the ampersand symbol (&) to the 60th position in the Shipper Name field.

N1*SH*SUPERCALIFRAGILISTICEXPIALIDOCIOUS SHIPPING COMPANY OF AMER&

SCENARIO 2: Zero (0) has been assigned to the Weight, Volume, and/or Quantity field(s). The ANSI X12 309 and GOVCBR versions of CBSA’s electronic Cargo report possess different field length restrictions for the Cargo Weight, Volume, and Quantity elements. When generating an outbound EDI MF, if CBSA is unable to assign the client-supplied data entry value to one of these numeric data fields, then CBSA will perform the following measures:

(i) Convert the numeric data entry to an integer by removing all decimal values.

(ii) Attempt to assign the integer value from step (i) to the appropriate EDI data field. If the integer value exceeds the field length restrictions for the EDI data field, then assign zero (0) to the EDI data field.

42

Example:

An ANSI 309 Cargo Report can be assigned up to 10 digits for the Cargo Weight (R 1/10), whereas the GOVCBR Cargo Report can be assigned up to 13 digits for the Cargo Weight (n..13).

Suppose that CBSA is required to assign the following Cargo Weight entry to an outbound ANSI X12 309 MF:

12345678910 KILOGRAMS

CBSA will attempt to resolve this issue by converting the numeric data entry to an integer value. The integer value will be assigned to the ANSI X12 309 MF’s Cargo Weight data field if it doesn’t exceed the field length restrictions (R 1/10). Otherwise, CBSA will assign zero (0) to the ANSI X12 309 MF’s Cargo Weight data field.

M11*8XXXHOUSEBILLCCN1234*9999***0*K*****9XXXPRIMARYCCN1234*SCAC*SCAC********

****ZZ***N!

SCENARIO 3: In the last occurrence of an EDI loop, a business data entry has been assigned the text “MORE/PLUS”.

The ANSI X12 309 and GOVCBR EDI standards have specific restrictions for looping certain EDI groups and/or segments. These looping restrictions may prevent CBSA from assigning an EDI MF all client-supplied data entries for a given business data element. If CBSA is required to omit one or more business data entries from an outbound EDI MF, then CBSA will assign text “MORE/PLUS” to the last occurrence of the business data element within the EDI MF.

Examples:

Due to the looping restrictions for EDI segment N1, an ANSI X12 309 MF cannot be assigned more than 20 entries for Named Parties (i.e. Shipper, Consignee, Notify Party, Delivery Address, Place of Consolidation, Consolidator, and Dangerous Goods Contact). When generating an ANSI 309 MF, CBSA may be required to omit the 21st, 22nd, …, Xth occurrences of Named Parties. If this event occurs, CBSA will assign text “MORE/PLUS” to the Name field of the 20th Named Party.

Note: For this particular data loss scenario, CBSA will only omit entries for the following types of Named Parties: Notify Party and Delivery Address.

N1*NP*NOTIFY PARTY NAME

N3*NOTIFY PARTY ADDRESS LINE 1*NOTIFY PARTY ADDRESS LINE 2

N3*NOTIFY PARTY ADDRESS LINE 3

N4*NOTIFY PARTY CITY NAME**L2B3V5*CA***ON

PER*IC*NOTIFY PARTY CONTACT NAME*TE*16137615428

N1*NP*MORE/PLUS

N3*NOTIFY PARTY ADDRESS LINE 1*NP ADDRESS LINE 2

N3*NP ADDRESS LINE 3

43

N4*NP CITY NAME**K2P2E6*CA***ON

PER*IC*NP CONTACT NAME*TE*16136089991

Due to the looping restrictions for EDI segment M7, an ANSI X12 309 MF cannot be assigned more than 22 Seal Number entries for a given Cargo commodity. When generating an ANSI 309 MF, CBSA may be required to omit the 23rd, 24th, …, Xth occurrences of Seal Number entries. When this event occurs, CBSA will assign text “MORE/PLUS” to the 22nd Seal Number entry.

VID*CN*CONT*12345*CN SEAL1*CN SEAL2

M7*CN SEAL3*CN SEAL4*CN SEAL5*CN SEAL6




M7*CN SEAL19*CN SEAL20*CN SEAL21*MORE/PLUS

Due to the looping restrictions for EDI segment group SG156, a GOVCBR MF cannot be assigned more than 99 occurrences of Equipment Details (for Container units). When generating a GOVCBR MF, CBSA may be required to omit the 100th, 101st, …, Xth occurrences of Equipment Details. When this event occurs, CBSA will assign text “MORE/PLUS” to the Equipment Identifier field of the 99th Equipment Details entry.

EQD+CN+CONT97

SEQ+4

EQD+CN+CONT98

SEQ+4

EQD+CN+MORE/PLUS

SEQ+4

Documents

Electronic Commerce Client Requirements … Commerce Client Requirements Document (ECCRD) ... Explanation of ANSI X12 Message Map Headings ... X12 and UN/EDIFACT Electronic Data Interchange