Detailed EDI User Stories

As an EDI Gateway Service,
I want to orchestrate and execute all GCCCANRL EDI data mapping and validation logic,
So that I can ensure strict compliance with US Customs (P140) automated payload constraints in a single consolidated service.

Prerequisites & Setup

[Initialize Empty Segment]
The table response is not available → The Master Control table segment should be initialized to empty values

Core Acceptance Criteria

[11:Set Manual Change Flag]
The system updates manifest data → The 309 manual change flag is set to true
[Log Cancel Release Activity]
Cancel release processing is complete → Create audit log entry with security information, CCN key, transaction details, user ID, timestamp, and cargo release removal action code, then write the log message to the system
[Extract Station Number from Retrieved Record]
The system processes the retrieved station information → The station number is extracted from the master control segment and moved to the table segment
[Use Current Manifest Station Number]
The system handles the lookup failure → The master control segment is initialized to empty values
[Set Destination Station Number for Index]
The system needs to set the destination station number for indexing → The existing destination station number from the manifest is used for the index field
[Extract Station Number from Response]
The response contains valid station information → The station number should be extracted from the response segment
[Set Manual Change Flag to TRUE]
The system is setting cancel release data for the manifest → The manual change flag (309-MANUAL-CHANGE) must be set to TRUE to indicate manual intervention
[Prepare Log Message]
Preparing to send the log entry → The audit information should be formatted into the message structure and the accept status should be cleared
[Send Log Entry to Audit System]
Sending the log entry to the audit system → The system should call the audit service to process the log entry
[Write Message to Log]
Writing to the system log → The message should be written to the log with proper message code, content, length, and module name
[Set Security Information]
The system prepares the audit log message → The security byte is set to high-values for maximum security classification
[Format Complete Log Message]
The log message needs to be transmitted → The complete log input structure is moved to the message format for processing
[Format Message for Logging]
The system prepares to send the audit entry → The log input data must be moved to the message structure for proper formatting
[Send Message to Audit System]
The system sends the audit entry → The CIMS program must be called with CHNG function to transmit the audit message through the alternate PCB
[Write Message to Log]
The system writes the message to the log → The WRITMSGL program must be called with the message code, message content, message length, and module name
[Purge Message Queue]
The system completes the logging process → The CIMS program must be called with PURG function to purge the message queue through the alternate PCB

Structural Validations

None explicitly identified in logic extraction.

As an EDI Gateway Service,
I want to orchestrate and execute all GCCCBOL EDI data mapping and validation logic,
So that I can ensure strict compliance with US Customs (P140) automated payload constraints in a single consolidated service.

Prerequisites & Setup

[Initialize Database Access Parameters]
The system initializes database access parameters → The communication area should be cleared to spaces and the segment type should be set to 'SHIPROOT' to identify the target data structure
[Initialize SHIPMINE segment]
The system begins the data retrieval process → The SHIPMINE data structure is cleared to spaces
[Initialize Search Variables]
The search process begins → The system should set customs broker not found flag to true, EBSNRTD found flag to true, EBSBCBC found flag to true, and temporary customs broker not found flag to true
[Initialize N9 Processing Variables]
The N9 processing begins → The system initializes sequence counter to 0, N9 array index to 1, sets EBSBCCR found flag to true, and sets BM and SI not found flags to true, and sets blank N9 not found flag to true
[Initialize seal counter to 1]
The seal number building process starts → The seal counter is set to 1 and EBSBCCX segment counter is initialized
[Initialize CCN Index to 1]
CCN processing begins → The CCN array index is set to 1 and EBSBCCX indicator is cleared
[Initialize EBSBCCY Processing]
EBSBCCY processing begins → The system clears EBSBCCY indicator and segment data, sets type to 'CR' and initializes sequence to 0
[Initialize EBSBCCY Search]
Preparing to search for related EBSBCCY segments → The system clears EBSBCCY indicators and resets sequence counter to 0
[Initialize Sequence Counter to 0]
The sequence management is being initialized → The sequence counter (WS-SEQ) should be set to 0 to start from the beginning
[Initialize EBSBCCX and EBSBCCY indicators]
The system begins processing multi-bill N10 data → EBSBCCX and EBSBCCY processing indicators are cleared to spaces
[Initialize CCM Sequence to 1]
The processing begins → The CCM sequence counter is set to 1 to start with the first segment
[Initialize EBSBCRT-AD Found Flag]
The additional description processing begins → The system sets the EBSBCRT-AD found flag to true and initializes the description sequence counter to 1
[Initialize EBSBCRT-AD Found Flag]
The additional description retrieval process begins → The EBSBCRT-AD found flag is set to TRUE and description sequence counter is initialized to 1
[Initialize VIN Counter to Zero]
The system begins MV segment processing → The VIN quantity counter is set to zero to track the number of VINs found
[Initialize Co-Load Process]
Co-loaded shipment processing begins → The system resets VIN counter to zero and prepares to search RF reference segments for consolidated shipments
[Initialize VIN Quantity to Zero]
VIN processing begins → The VIN quantity counter is set to zero
[Initialize VIN Counter to Zero]
The VIN retrieval process begins → The VIN counter is set to zero to start counting from the beginning
[Initialize V2 segment counter to 1]
System begins V2 segment processing → V2 segment counter is set to 1 to start sequential processing

Core Acceptance Criteria

[2:Get Shipment Root Data]
The system needs to access shipment root data → The SHIPROOT segment is retrieved using the root key with 'GU' function code
[4:Extract EDI BOL Key]
The system needs to identify the EDI BOL key → If shipment mine data is found, the first data line becomes the EDI BOL key, otherwise the key is set to spaces
[5:Build Broker Information]
Building broker information → First attempt to get broker from EDI BOL data, if not found then search Fastway system data, if still not found then set broker name to 'UNKNOWN'
[5:Build Broker Information]
Processing broker information from EDI BOL → If organization ID is 'XQ', use that broker name and stop searching; if organization ID is 'CB' and no XQ found yet and custom ID is not 'XR' or 'XU', store as temporary broker
[10:Build N9 Reference Numbers]
Building N9 reference numbers from BOL data → Search for 'BM' and 'SI' qualified reference numbers, set empty references to 'N/A', and add them to the reference array up to maximum of 10 entries
[10:Build N9 Reference Numbers]
Building reference numbers → Use shipper bill number as 'BM' reference and search special handling codes for 'SI' type references
[17:Find Multi-Bill CCNs]
Finding related cargo control numbers → Search 'RF' type records for 'XC' qualified cargo control numbers and add them to the CCN array, excluding the current cargo control number
[19:Process Lading Descriptions]
Building cargo descriptions → Collect primary descriptions from L5 segments, additional descriptions from related records, special instructions with codes 'VA', 'VS', or 'EV', and vehicle identification numbers
[27:Process CSA Data]
Searching Fastway data for CSA information → Search for 'N1-01 IM' segments followed by 'N1-02' importer name, 'N1-03' qualifier ('M5', 'BN', or 'AI'), and 'N1-04' business number; set CSA indicator ON only for 'M5' qualifier
[Set Database Function to Get Unique]
The system sets the database function type → The function code should be set to 'GU' (Get Unique) and accept status should be set to 'GE' (Get Equal) to retrieve exactly one matching shipment root record
[Call Database Access Routine]
The system calls the database access routine FWCWBIO → The database call should be executed with the communication control area, database parameters, and shipment root data structure to attempt data retrieval
[Set segment type to 'SHIPMIN']
The system configures the segment type → The segment type is set to 'SHIPMIN' to identify shipment mine records
[Set segment ID to 'E']
The system sets the segment identifier → The segment ID is set to 'E' to identify the specific data category
[Set segment number from counter]
The system configures the segment number → The segment number is set from the WS-SHIPMINE-SEG-NBR counter
[Set function code to 'GU' - Get Unique]
The system sets the database function code → The function code is set to 'GU' for Get Unique operation
[Extract EDI BOL key from data line 1]
The system processes the first data line → The EDI BOL key is extracted from DATA-LINE(1) and stored in WORK-EDI-BOL-KEY
[Extract EDI BOL key from data line 1]
The system processes the EDI BOL key extraction → The WORK-EDI-BOL-KEY is set to spaces
[Set Shipmine Segment Number to 1]
The extraction process begins → The shipmine segment number is set to 1 to start from the first segment
[Retrieve Shipmine Data]
The system attempts to retrieve shipmine data → The system calls the database access routine to get the shipmine segment data
[Extract BOL Key from First Data Line]
The system processes the retrieved shipmine segment → The EDI BOL key is extracted from the first data line and stored in the work area
[Set BOL Key to Blank]
No shipmine data is found in the database → The EDI BOL key is set to blank spaces
[Search EBSNRTD Segments]
The system searches EBSNRTD segments for organization data → Organization records with type 'TN' are retrieved sequentially for broker identification
[Organization ID = 'XQ'?]
An organization record has custom ID equal to 'XQ' → The organization name is set as the final broker name and search is completed
[Organization ID = 'CB'?]
An organization record has ID equal to 'CB' and custom ID is not 'XR' or 'XU' → The organization name is stored as temporary broker name for potential use
[Get Broker from BOL]
No XQ type broker was found during the search → The temporary CB broker name becomes the final broker name
[Parse Broker Name]
The system parses the broker name → The actual broker name is extracted from position 17 onwards
[Starts with 'BROKER '?]
The system parses the broker name → The actual broker name is extracted from position 8 onwards
[Parse Broker Name]
The system parses the broker name → The actual broker name is extracted from position 9 onwards
[Starts with 'CB ' or 'XQ '?]
The system parses the broker name → The actual broker name is extracted from position 4 onwards
[Parse Broker Name]
The system parses the broker name → The actual broker name is extracted from position 5 onwards
[Use Full String as Name]
The system parses the broker name → The entire string is used as the broker name without modification
[Lookup Broker Short Name]
The system looks up the broker name in GCST2RT table → The system searches for a corresponding short name translation
[Use Original Long Name]
The lookup operation finds no matching record → The original parsed long name is used as the final broker name
[Org ID = 'XQ'?]
The organization ID custom field equals 'XQ' → The system should immediately set the organization name as the primary broker name, mark XQ broker as found, set temporary customs broker as not found, and stop searching for other broker types
[Org ID = 'CB' AND No XQ Found?]
The organization ID equals 'CB' and the temporary customs broker is not found and the organization ID custom != 'XR' and not equal to 'XU' → The system should store the organization name as temporary broker name and mark temporary customs broker as found
[Parse Final Broker Name]
The broker name needs to be cleaned and formatted → Standard parsing rules are applied to remove prefixes like 'CUSTOMS BROKER', 'BROKER', 'CB', or 'XQ' and extract the actual broker name
[Check if starts with 'CUSTOMS BROKER ']
The string starts with 'CUSTOMS BROKER ' (15 characters including space) → Extract the broker name from position 16 to 43 (28 characters) and store it as the parsed broker name
[Check if starts with 'CUSTOMS BROKER: ']
The string starts with 'CUSTOMS BROKER: ' (16 characters including colon and space) → Extract the broker name from position 17 to 43 (27 characters) and store it as the parsed broker name
[Check if starts with 'BROKER ']
The string starts with 'BROKER ' (7 characters including space) → Extract the broker name from position 8 to 43 (36 characters) and store it as the parsed broker name
[Check if starts with 'BROKER: ']
The string starts with 'BROKER: ' (8 characters including colon and space) → Extract the broker name from position 9 to 43 (35 characters) and store it as the parsed broker name
[Check if starts with 'CB ' or 'XQ ']
The string starts with 'CB ' or 'XQ ' (3 characters including space) → Extract the broker name from position 4 to 44 (41 characters) and store it as the parsed broker name
[Check if starts with 'CB: ' or 'XQ: ']
The string starts with 'CB: ' or 'XQ: ' (4 characters including colon and space) → Extract the broker name from position 5 to 44 (40 characters) and store it as the parsed broker name
[Use entire string as broker name]
The string does not start with 'CUSTOMS BROKER ', 'CUSTOMS BROKER: ', 'BROKER ', 'BROKER: ', 'CB ', 'XQ ', 'CB: ', or 'XQ: ' → Use the entire string as the parsed broker name without any modification
[Organization ID = 'CB'?]
The organization ID is 'CB' and temporary customs broker is not found and custom ID is not 'XR' or 'XU' → Store the organization name as temporary broker name and set temporary customs broker found indicator
[Organization ID = 'XQ'?]
The organization custom ID is 'XQ' → Set the organization name as the final broker name, mark customs broker as found, and reset temporary customs broker indicator
[Temporary Broker Available?]
A temporary customs broker was found during the search → Use the temporary broker name as the final broker long name
[More Sequences Available?]
Current sequence processing is complete → Continue to next sequence if customs broker not found and more segments available, otherwise end search
[Parse broker name using standard formats]
The string starts with 'CUSTOMS BROKER ', 'CUSTOMS BROKER: ', 'BROKER ', 'BROKER: ', 'CB ', 'CB: ', 'XQ ', or 'XQ: ' → Remove the prefix and extract the remaining text as the broker long name, otherwise use the entire string as broker long name
[Get First EBSBCCR Segment]
The system retrieves EBSBCCR segments with type CR → The system increments the sequence counter and attempts to get the next EBSBCCR segment, setting the found flag based on retrieval success
[Reference Qualifier = BM or SI?]
The system checks the reference number qualifier → The system continues processing only if the qualifier equals 'BM ' or 'SI ', otherwise it retrieves the next segment
[Store Payment Method]
The system retrieves the EBSBCBC segment and the shipment method payment field is not empty → The system stores the shipment method payment value in the cargo report payment method field
[Store CN Reference Number]
The shipment ID number field is not empty and array space is available → The system increments the N9 array index, stores 'CN' as the reference qualifier, and stores the shipment ID number as the reference number
[Call 8430-GET-EBSBCBC to retrieve BOL data]
The system calls the BOL data retrieval service → The EBSBCBC segment data is retrieved from the BOL system
[Extract B2-SHIPMENT-METH-PAY from BOL]
The system processes the payment method extraction → The B2-SHIPMENT-METH-PAY value is extracted from the BOL segment
[BM Reference Number Missing?]
The system processes N9 reference numbers from Fastway source → Extract BM reference from shipper bill number AND set BM found flag to true AND increment reference array index
[Get EBSBCCR Segment from BOL]
The system attempts to retrieve EBSBCCR segments from the Electronic Bill of Lading → The system should sequentially read EBSBCCR segments until no more segments are found or required reference types are located
[Reference Qualifier = BM or SI?]
The system checks the reference number qualifier → The system should continue processing only if the qualifier equals 'BM ' or 'SI ', otherwise skip to the next segment
[Get EBSBCBC Segment]
The system attempts to retrieve the EBSBCBC segment → The system should read the EBSBCBC segment to extract payment method and shipment identification information
[Set BM Reference Number]
The system processes Fastway data for missing references → The system sets 'BM' as the reference qualifier, uses the shipper bill number as the reference value, marks BM as found, and increments to the next reference position
[Extract B2-SHIPMENT-METH-PAY from BOL]
The system retrieves the EBSBCBC BOL segment and the payment method field contains valid data → The payment method is extracted and stored in the cargo report structure
[Store payment method in GCCC-BX03-SHIP-METH-PAY]
The B2-SHIPMENT-METH-PAY field contains valid payment method data → The payment method value is moved to GCCC-BX03-SHIP-METH-PAY field in the cargo report
[Get EBSBCBC Segment from BOL]
The system processes the BOL data for shipment identification → The system should retrieve the EBSBCBC segment containing shipment ID information
[Increment Reference Number Counter]
The system prepares to add the shipment ID as a reference number → The system should increment the reference number counter by 1 to point to the next available array position
[Set seal type to 'SN']
Preparing to retrieve EBSBCCX segments → The type identifier is set to 'SN' for seal number segment retrieval
[Get EBSBCCX segment from BOL]
Retrieving EBSBCCX segments with type 'SN' → The system attempts to get the EBSBCCX segment and sets found/not found status
[Store Seal Number 1 in array]
Storing the seal number data → M7-SEAL-NUMBER-1 is moved to GCSCCS56-SEAL-NUMBER at the current seal counter position
[Store Seal Number 2 in array]
Storing the seal number data → M7-SEAL-NUMBER-2 is moved to GCSCCS56-SEAL-NUMBER at the current seal counter position
[Store Seal Number 3 in array]
Storing the seal number data → M7-SEAL-NUMBER-3 is moved to GCSCCS56-SEAL-NUMBER at the current seal counter position
[Store Seal Number 4 in array]
Storing the seal number data → M7-SEAL-NUMBER-4 is moved to GCSCCS56-SEAL-NUMBER at the current seal counter position
[Increment EBSBCCX segment counter]
Moving to the next segment → The EBSBCCX segment counter (WS-SUB-CX) is incremented by 1
[End Build Seal Numbers]
No more EBSBCCX segments are found:
the seal counter exceeds 20
→ The seal number building process terminates
[Get First EBSBCCR Record]
The system starts the CCN retrieval process → The system retrieves the first EBSBCCR record and initializes sequence counter to 0
[Get EBSBCCX Segment with Type 'RF']
The system searches for EBSBCCX segments → The system retrieves EBSBCCX segment with type 'RF' using current sequence number
[Search for EBSBCCY Segment]
The system searches for EBSBCCY segments until sequence reaches 99 or segment is not found or XC qualifier is found → The system increments sequence and retrieves EBSBCCY segment until termination condition is met
[Start CCN Retrieval]
The CCN retrieval process begins → The system initializes CCN counter to 1 and clears EBSBCCX indicators
[Set RF Type for EBSBCCX Search]
Searching for reference segments in EBSBCCX → The system sets the type to 'RF' for reference segment identification
[Get EBSBCCX RF Segment]
Retrieving EBSBCCX segment with RF type → The system fetches the corresponding RF segment from EBSBCCX
[Set CR Type for EBSBCCY]
Setting up cargo reference segment search → The system sets the type to 'CR' for cargo reference identification
[Get EBSBCCY Segment]
Searching for EBSBCCY segments with XC qualifier and sequence is less than 99 → The system retrieves EBSBCCY segments until XC qualifier is found or search limit is reached
[Increment CX Counter]
Moving to the next segment → The system increments the CX counter by 1 to process the next EBSBCCX RF segment
[Set EBSBCCY Indicator to Spaces]
The system prepares to search for cargo reference information → The EBSBCCY indicator should be set to spaces and the EBSBCCY segment data should be cleared
[Set Type-3 to 'CR']
The search parameters are being configured → The Type-3 parameter should be set to 'CR' to identify cargo reference segment types
[Get EBSBCCX segment with type 'RF']
The system searches for EBSBCCX segments → The system retrieves segments with type 'RF' using the current sequence number
[Set EBSBCCX not found]
The sequence number reaches 99 → The system sets EBSBCCX not found indicator to terminate processing
[Set type to 'CR' and sequence to 0]
The system prepares to search for related cargo data → The system sets type to 'CR', initializes sequence to 0, and clears EBSBCCY indicator
[Loop until sequence = 99 or CCN matches or segment not found]
The system loops through EBSBCCY segments → The system continues until sequence equals 99 OR cargo control number matches current CCN OR segment is not found
[Get QD type EBSBCCY segment with sequence 1]
The system searches for quantity description data → The system retrieves EBSBCCY segment with type 'QD' and sequence number 1
[Extract quantity from N10 quantity field]
The system processes the quantity field → The system extracts numeric characters from right to left, removes leading spaces, replaces them with zeros, and stores the formatted quantity in cargo lading quantity
[Move country code to origin country]
The system extracts country information → The system moves the N10 country code to the cargo origin country field
[Get QD type EBSBCCY segment with sequence 2]
The system searches for additional quantity description data → The system retrieves EBSBCCY segment with type 'QD' and sequence number 2
[Set Type to 'QD' and Sequence to 1]
The extraction process begins → The system sets the segment type to 'QD' and sequence number to 1 to retrieve the first quantity/description segment
[Get EBSBCCY Segment]
The system performs segment retrieval → The system calls the segment retrieval function to get the EBSBCCY segment data
[Extract Numeric Characters from Quantity Field]
The system processes the quantity field CY-N10-QUANTITY → The system extracts numeric characters from position 7 down to position 1, building the quantity string from right to left
[Move Country Code to Origin Country]
The system processes country data → The system moves CY-N10-COUNTRY-CODE to GCCC-ORIG-COUNTRY field
[Store Description in Array]
The system processes the description data → The system moves CY-N10-DESCRIPTION to WS-DESC-EB array at the current index position
[Set Type to 'QD' and Sequence to 2]
The system prepares for second segment retrieval → The system sets the segment type to 'QD' and sequence number to 2
[Get Second EBSBCCY Segment]
The system performs the second segment retrieval → The system calls the segment retrieval function to get the second EBSBCCY segment data
[Store Second Description in Array]
The system processes the second description data → The system moves CY-N10-DESCRIPTION to WS-DESC-EB array at the current index position
[Get First Lading Description from EBSBCCM]
The system processes the first lading description segment → The primary lading description is extracted and added to the description array if not empty or low-values
[Loop Through Remaining EBSBCCM Segments]
The system loops through each segment until no more segments found or maximum reached → Each valid lading description is extracted and processed for additional content
[Get Additional BOL Descriptions for Current Segment]
The system processes L5-ADDITIONAL-LADING-DESC array with index from 1 to 7 → Each non-empty additional description line is added to the description array
[Retrieve VIN Numbers]
The system processes vehicle identification numbers from available segments → Each VIN is prefixed with 'VIN' text and added to description array up to maximum limit
[Get First EBSBCCM Segment]
The system attempts to retrieve the EBSBCCM segment → The segment data is fetched using the EDI BOL key and CCM sequence number
[Store Lading Description in Description Array]
The description content is not empty → The lading description is stored in the description array at the current index position
[Get Additional Description Data from BOL]
Additional description data is needed → The system retrieves up to 7 additional description lines from related EBSBCRT segments
[Increment CCM Sequence]
More segments need to be processed → The CCM sequence number is incremented by 1
[Get Next EBSBCCM Segment]
The system continues processing → The next EBSBCCM segment is retrieved using the incremented sequence number
[Retrieve EBSBCRT-AD Segment]
The system attempts to retrieve an EBSBCRT-AD segment → The system calls the data access routine to fetch the segment using current sequence number
[EBSBCRT-AD Segment Found?]
The retrieval operation completes → If the segment is found, processing continues with description extraction, otherwise the sequence counter is incremented to try the next segment
[Description Index <= 7?]
The system processes individual description lines within the segment → Processing continues for description indexes 1 through 7, then moves to the next segment
[Retrieve EBSBCRT-AD Segment from BOL]
EBSBCRT-AD segment retrieval is requested with current sequence number → The system attempts to retrieve the EBSBCRT-AD segment from BOL data
[EBSBCRT-AD Segment Found?]
The system checks the retrieval result → If segment is found, processing continues with description extraction, otherwise sequence counter is incremented
[Additional Description Index <= 7?]
The system processes individual additional descriptions within the segment → Processing continues for additional description index from 1 to 7
[Get MV Loaded Shipments VINs]
The system processes VIN retrieval and searches through MV segments sequentially → Each valid vehicle ID number from MV segments is extracted, formatted with 'VIN' prefix, and stored in the VIN array with incremented counter
[Set MV Type Filter]
VIN processing begins for MV segments → The type filter is set to 'MV' to identify motor vehicle records
[Loop Through MV Segments]
The system loops through MV segments with incrementing sequence numbers → Each MV segment is processed in order until either no more segments are found or the maximum VIN limit is reached
[Extract Vehicle ID Number, Format VIN with 'VIN' Prefix, Store in VIN Array]
The vehicle ID number is not spaces or low-values → The system formats the vehicle ID with 'VIN' prefix and stores it in the VIN description array, then increments the VIN counter
[VIN Quantity = 0?]
The VIN quantity counter equals zero indicating no VINs were found in MV segments → The system initiates co-loaded shipment VIN processing as an alternative source
[Get RF Reference Segment]
The system searches for RF type segments with sequential numbering → Each RF segment is retrieved to check for consolidated shipment indicators
[Loop Through V2 Motor Vehicle Segments]
The system loops through V2 motor vehicle segments within the consolidation → Each V2 segment is processed sequentially until no more segments are found or maximum vehicle limit is reached
[Extract Co-Load Vehicle ID, Format Co-Load VIN with Prefix, Store Co-Load VIN in Array]
The vehicle ID number in the V2 segment is not spaces or empty → The system formats the vehicle ID with 'VIN' prefix, stores it in the VIN array if under the maximum limit, and increments the VIN counter
[Set Segment Type to MV Motor Vehicle]
Segment type configuration is required → The segment type is set to MV for motor vehicle processing
[Extract Vehicle ID Number from Segment]
VIN extraction is performed → The vehicle identification number is extracted from the segment
[Format VIN with VIN Prefix]
VIN formatting is applied → The VIN is formatted with the VIN prefix to create a complete VIN string
[More Segments Available AND Counter < Maximum?]
Continuation evaluation is performed → Processing continues if more segments are available AND the VIN counter is below the maximum limit, otherwise processing stops
[Get RF Segment from EBSBCCX]
The system attempts to get an RF segment from EBSBCCX → The RF segment data is retrieved and availability status is determined
[Has Consolidated Shipment Number?]
If the consolidated shipment number field → Processing continues to V2 segments if consolidated shipment number exists, otherwise skips to next RF segment
[Get V2 Segment from EBSBCCY]
The system attempts to get a V2 segment from EBSBCCY → The V2 segment data is retrieved and availability status is determined
[Increment VIN Counter]
The system processes the vehicle ID → The VIN counter is incremented by one
[More V2 Segments?]
If continuation of V2 processing → Processing continues with next V2 segment if more exist and limits not exceeded, otherwise moves to next RF segment
[More RF Segments?]
If continuation of RF processing → Processing continues with next RF segment if more exist and limits not exceeded, otherwise ends VIN processing
[Get Vehicle ID Number]
The system processes the MV segment → The vehicle ID number is extracted from the VC-VEHICLE-ID-NO field
[Set Search Type to 'MV' Motor Vehicle]
The VIN retrieval process is initiated → The search type is set to 'MV' to filter for motor vehicle records
[Increment VIN Counter]
The system processes the segment for VIN extraction → The VIN counter is incremented by one
[Extract Vehicle ID Number]
The system processes the segment data → The vehicle ID number is extracted from the segment's vehicle ID field
[Format VIN String with 'VIN' Prefix]
The system formats the VIN for storage → The string 'VIN' is concatenated with the vehicle ID number to create the formatted VIN string
[More Segments Available AND Counter < Maximum?]
If whether to continue the loop → The loop continues if more motor vehicle segments are available AND the VIN counter has not exceeded the maximum allowed VINs
[Loop through RF segments Counter ≤ Max N7 Reference Loop?]
System processes RF segments for co-loaded shipments → System continues looping while counter is less than or equal to maximum N7 reference loop limit
[Get EBSBCCX RF segment]
System attempts to retrieve EBSBCCX RF segment → System calls database routine to get RF segment data using current sequence number
[Contains consolidated shipment number?]
System examines the RF segment content → System identifies if the segment contains consolidated shipment number data
[Loop through V2 segments Counter ≤ Max Motor Vehicles?]
System processes V2 segments for vehicle data → System continues looping while V2 counter is less than or equal to maximum motor vehicles limit
[Get EBSBCCY V2 segment]
System attempts to retrieve EBSBCCY V2 segment → System calls database routine to get V2 segment data using current sequence number
[Increment VIN quantity]
System processes the vehicle identification data → VIN quantity counter is incremented by 1
[Check Extra Description Data]
The extra description field contains data that is not empty spaces and not low-values → The system calls the GCCDESC program to store the extra description data in GCSCCS53 segments using the cargo control number key and insert operation
[Check BOL for CSA]
Searching for N1 importer segments with entity ID 'IM', non-blank name, qualifier 'M5'/'BN'/'AI', and non-blank ID code → Return the importer segment if found, otherwise indicate not found
[Check Fastway for CSA]
Searching for N1-01 'IM' segments with N1-02 importer name, N1-03 qualifier ('M5'/'BN'/'AI'), and N1-04 business number → Extract and return the importer information if complete sequence is found
[Get N1 Importer Segment from BOL]
The system searches for N1 importer segment data → The system retrieves the first N1 importer segment from the EDI BOL data source
[ID Code Qualifier = 'M5'?]
The system checks the ID code qualifier → If the qualifier equals 'M5', the system sets the CSA indicator ON and copies all importer data to the cargo report
[ID Code Qualifier = 'BN'?]
The system checks if the ID code qualifier equals 'BN' → If the qualifier equals 'BN', the system copies importer data to cargo report without setting CSA indicator
[ID Code Qualifier = 'AI'?]
The system checks if the ID code qualifier equals 'AI' → If the qualifier equals 'AI', the system copies importer data to cargo report without setting CSA indicator
[Set CSA Indicator ON]
The system processes the M5 qualified importer → The system sets the CSA indicator to ON status to enable Canada-US trade processing
[Copy Importer Data to Cargo Report]
The system copies importer data → The system copies the importer name to GCCC-IMPORTER, ID code qualifier to GCCC-BUSINESS-NBR-QUAL, and ID code to GCCC-BUSINESS-NBR fields
[Copy Importer Data Only]
The system processes the non-M5 qualified importer → The system copies the importer name to GCCC-IMPORTER, ID code qualifier to GCCC-BUSINESS-NBR-QUAL, and ID code to GCCC-BUSINESS-NBR fields without setting CSA indicator
[Move to Next SHIPMINE Segment]
The system needs to continue searching in subsequent segments → The shipmine segment number is incremented by 1, the next SHIPMINE segment is retrieved, and the data start index is reset to 1
[Extract N1-02 Importer Name]
The system checks the next data line for N1-02 importer name information → If the next data line contains ' N1-02', the importer name is extracted from positions 8-28 of that line and stored as the CSA importer name
[Check Next Data Line for N1-04]
The system checks the next data line for N1-04 business number information → If the data line contains ' N1-04', the business number is extracted from positions 8-17 of that line and stored as the business number
[Set CSA Indicator ON]
The business number qualifier is 'M5' → The CSA indicator is set to ON to enable CSA-specific processing
[Store Importer Name and Business Number]
The N1-04 business number segment has been processed → The importer name is stored in the importer field and the business number is stored in the business number field for subsequent CSA processing
[More SHIPMINE Segments?]
The current data index exceeds position 5 in the current segment → The system attempts to retrieve the next SHIPMINE segment and continues processing if available, or terminates the search if no more segments exist
[Set N1-01 Not Found Flag]
The search process begins → The system sets the N1-01 found flag to false (not found) to initialize the search state
[Data Line Contains 'N1-01 IM'?]
Checking the data line content for importer segment identification → The system determines if the data line contains the exact pattern 'N1-01 IM' starting at position 1 through 9
[Set N1-01 Found Flag]
The importer segment is successfully located → The system sets the N1-01 found flag to true to indicate successful discovery
[Increment Data Index]
Moving to examine the next data line in the current segment → The system increments the data index by 1 to advance to the next sequential data line
[N1-01 Found?]
Determining next action based on search results → The system checks if the N1-01 found flag is true to decide whether to continue searching or proceed with processing
[Move to Next SHIPMINE Segment]
Continuing the search in additional segments → The system increments the SHIPMINE segment number by 1 to access the next available segment
[Get Next SHIPMINE Data]
Retrieving data from the next segment number → The system performs a database call to get SHIPMINE data using the incremented segment number
[Reset Data Index to 1]
Starting to search through the new segment's data lines → The system resets the data index to 1 to begin searching from the first data line of the new segment
[Get N1 Importer Segment from BOL]
The system searches for N1 importer segment data in the EDI BOL → The system retrieves the importer segment if it exists or sets not found status
[ID Code Qualifier = 'M5'?]
The system checks if the ID code qualifier equals 'M5' → CSA indicator is set ON if qualifier is M5, otherwise check for other qualifiers
[Set CSA Indicator ON]
The system processes the M5 qualified importer → The CSA indicator is set to ON to enable Canada-US trade processing
[Copy BOL N1 Importer Data]
The system copies importer data from the N1 segment → Importer name is copied to GCCC-IMPORTER, ID code qualifier to GCCC-BUSINESS-NBR-QUAL, and ID code to GCCC-BUSINESS-NBR
[ID Code Qualifier = 'BN'?]
The system checks if the ID code qualifier equals 'BN' → Importer data is copied if qualifier is BN, otherwise check for AI qualifier
[ID Code Qualifier = 'AI'?]
The system checks if the ID code qualifier equals 'AI' → Importer data is copied if qualifier is AI, otherwise CSA processing ends
[Copy BOL N1 Importer Data Only]
The system copies importer data from the N1 segment → Importer name, ID code qualifier, and ID code are copied to cargo fields but CSA indicator remains OFF
[Search SHIPMINE for N101 Importer Segment]
Searching for importer segments with data line containing ' N1-01 IM' → The N101 found flag is set to true when the segment is located
[Move to Next SHIPMINE Segment]
More data processing is required → Increment SHIPMINE segment number and reset data index to 1 if next segment is found
[Extract Importer Name]
Processing CSA importer information → Extract characters 8-28 from the data line as the CSA importer name
[Extract Business Number]
Processing business number information → Extract characters 8-17 as business number and copy importer name to CSA importer field
[Set CSA Indicator ON]
Processing N1-04 business number segment → Set the CSA indicator to ON to enable CSA processing
[Get N1 Importer Segment from BOL]
The system searches for N1 importer segment with type 'SC' and sequence number 1 → The system retrieves the importer segment data and sets the found indicator
[Qualifier = 'M5'?]
The system checks if the ID code qualifier equals 'M5' → The system sets CSA indicator ON and copies importer data to output fields
[Qualifier = 'BN'?]
The system checks if the ID code qualifier equals 'BN' → The system copies importer data to output fields without setting CSA indicator
[Qualifier = 'AI'?]
The system checks if the ID code qualifier equals 'AI' → The system copies importer data to output fields without setting CSA indicator
[Copy BOL Importer Data]
The system processes the importer data → The system moves N1 name to importer field, ID code qualifier to business number qualifier field, and ID code to business number field
[Search Fastway for N1-01 IM]
The system searches through Fastway shipment mine segments → The system looks for data lines containing 'N1-01 IM' pattern
[Extract N1-02 Importer Name]
The system processes the next data line expecting N1-02 format → The system extracts the importer name from positions 8-28 of the N1-02 data line
[Set CSA Indicator ON]
The system checks if the business number qualifier equals 'M5' → The system sets CSA indicator ON
[Store Importer Information]
The system finalizes the importer data processing → The system moves the extracted business number to business number field and importer name to importer field
[Check BOL for CSA Data]
EDI BOL system is checked for importer segment data → Retrieve N1 importer segment and evaluate for valid CSA data
[Check Fastway for CSA Data]
Fastway system is searched for CSA importer information → Search shipment mine segments for N1-01 IM entity data
[Transfer Importer Name to Cargo Report]
The copy importer data process is executed → The N1-NAME field value is transferred to the GCCC-IMPORTER field in the cargo report segment
[Transfer Business Number Qualifier to Cargo Report]
The copy importer data process is executed → The N1-ID-CODE-QUALIFIER field value is transferred to the GCCC-BUSINESS-NBR-QUAL field in the cargo report segment
[Transfer Business Number to Cargo Report]
The copy importer data process is executed → The N1-ID-CODE field value is transferred to the GCCC-BUSINESS-NBR field in the cargo report segment
[Log Transfer Completion with Details]
All importer data fields have been copied to the cargo report segment → The system logs the completion with timestamp, root key, car ID, EDI BOL key, importer name, business number qualifier, and business number to the system error log
[Get Additional Cargo Description Data]
The system processes additional cargo description segments from EBSBCRT-AD BOL segments → The system should retrieve up to 10 description sequences, each containing up to 7 additional lading descriptions, and store non-empty descriptions in the description array while incrementing the array index
[EBSBCRT-AD Segment Found?]
The EBSBCRT-AD segment is successfully found → The system should initialize description index to 1 and begin processing the segment's description data
[EBSBCRT-AD Segment Found?]
The EBSBCRT-AD segment is not found → The system should increment the description sequence counter and continue to the next sequence without processing description data
[Clear Database Access Parameters]
The system initializes the database access setup process → All database access parameters are cleared to ensure clean state
[Set Segment Type to EBSBCCX]
The system sets the segment type parameter → The segment type is set to EBSBCCX-LIT to identify the target data structure
[Set EDI BOL Key as Root Key]
The system sets the root key parameter → The root key is set to the WORK-EDI-BOL-KEY value for record identification
[Set Dependent Key to CR001]
The system sets the dependent key parameter → The dependent key is set to 'CR001' to identify the specific segment hierarchy
[Move N1-NAME to GCCC-IMPORTER]
The system processes CSA importer data transfer → The importer name from N1-NAME field is copied to GCCC-IMPORTER field in the cargo report
[Move N1-ID-CODE-QUALIFIER to GCCC-BUSINESS-NBR-QUAL]
The system processes CSA importer data transfer → The business number qualifier from N1-ID-CODE-QUALIFIER field is copied to GCCC-BUSINESS-NBR-QUAL field in the cargo report
[Move N1-ID-CODE to GCCC-BUSINESS-NBR]
The system processes CSA importer data transfer → The business number from N1-ID-CODE field is copied to GCCC-BUSINESS-NBR field in the cargo report

Structural Validations

[27:Process CSA Data]
Validating importer information → If entity ID is 'IM' with non-empty name and ID code qualifier is 'M5' with non-empty ID code, set CSA indicator ON and copy importer data; if qualifier is 'BN' or 'AI', only copy importer data without setting CSA indicator
[EDI BOL Key Available?]
The EDI BOL key (WORK-EDI-BOL-KEY) is spaces or empty → The system should skip EDI BOL broker search and exit the process
[EDI BOL Key Available?]
The EDI BOL key is checked for availability → If EDI BOL key is spaces, set indicators to not found and exit, otherwise proceed with broker search
[Broker Long Name Available?]
The broker long name field is evaluated for availability → The system proceeds to standardization lookup only if broker long name is not spaces
[EBSBCBC segment found?]
The system checks if EBSBCBC segment was found → Processing continues only if the BOL segment exists, otherwise payment method processing is skipped
[Payment method field not empty?]
The system checks the B2-SHIPMENT-METH-PAY field → Payment method is processed only if the field is not empty or spaces
[Set Reference Number to 'N/A']
The reference number field is empty or contains only spaces → The system should set the reference number to 'N/A'
[Store Payment Method]
The shipment payment method field is not empty or spaces → The system should store the payment method in the cargo report output structure
[Store Shipment ID as CN Reference]
The shipment identification number field is not empty or spaces → The system should store the shipment ID as a 'CN' qualified reference number in the next available array position
[EBSBCBC segment found?]
The system attempts to retrieve the EBSBCBC BOL segment → The system proceeds with payment method extraction only if the BOL segment is successfully found
[Payment method field not empty?]
The system checks the B2-SHIPMENT-METH-PAY field for content → The payment method is processed only if the field is not empty or contains spaces
[EBSBCBC Segment Found?]
The system checks if the EBSBCBC segment was successfully found → The system should continue processing if segment is found, otherwise terminate the shipment ID extraction process
[Shipment ID Number Available?]
The system checks the B2-SHIPMENT-ID-NO field for valid content → The system should proceed with reference number creation if shipment ID is not spaces, otherwise skip the shipment ID processing
[Seal counter ≤ 20]
The seal counter reaches or exceeds 20 → The seal number processing stops to prevent exceeding the maximum capacity
[Seal Number 1 not empty]
Checking the first seal number field (M7-SEAL-NUMBER-1) → The seal number is processed only if it is not equal to spaces or low-values
[Seal Number 2 not empty]
Checking the second seal number field (M7-SEAL-NUMBER-2) → The seal number is processed only if it is not equal to spaces or low-values
[Seal Number 3 not empty]
Checking the third seal number field (M7-SEAL-NUMBER-3) → The seal number is processed only if it is not equal to spaces or low-values
[Seal Number 4 not empty]
Checking the fourth seal number field (M7-SEAL-NUMBER-4) → The seal number is processed only if it is not equal to spaces or low-values
[EBSBCCR Record Found?]
The EBSBCCR record retrieval is executed → If EBSBCCR record is found, continue with CCN index initialization, otherwise terminate CCN processing
[EBSBCCX Segment Found?]
EBSBCCX segment retrieval is executed or sequence reaches 99 → If EBSBCCX segment is not found or sequence equals 99, terminate processing, otherwise continue with EBSBCCY processing
[Found EBSBCCY with Qualifier 'XC'?]
The system checks the segment qualification → If EBSBCCY segment is not found or qualifier is not 'XC', skip to next EBSBCCX segment, otherwise proceed with CCN comparison
[CCN Different from Current?]
The system compares the CCN reference number with current cargo control number → If CCN equals current cargo control number, skip storage and continue to next segment, otherwise store the CCN
[EBSBCCX Found?]
Checking the retrieval result → The system determines if the EBSBCCX segment was found or not found
[Reached Max Segments?]
The sequence counter equals 99 → The system sets EBSBCCX not found indicator to terminate processing
[EBSBCCY Found?]
Checking the retrieval result → The system determines if the EBSBCCY segment was found or not found
[Reference Qualifier = XC?]
The reference qualifier is evaluated → The system checks if the reference qualifier equals 'XC' for cargo control number identification
[CCN matches cargo control number]
The system compares the reference number with the current cargo control number → Processing continues only if the reference number matches the cargo control number
[Store N10 description in description array]
The N10 description field is not empty and not low-values → The system stores the N10 description in the description array at the current index and increments the index
[Store second N10 description in array]
The second N10 description field is not empty and not low-values → The system stores the second N10 description in the description array at the current index and increments the index
[Segment Found?]
The system checks the retrieval result → If the segment is found, continue with quantity processing; otherwise, terminate the extraction process
[Description Available?]
The system checks for description data → If CY-N10-DESCRIPTION is not spaces and not low-values, proceed to store the description; otherwise, skip to second segment processing
[Second Segment Found?]
The system checks the second retrieval result → If the second segment is found, proceed with description validation; otherwise, terminate the extraction process
[Second Description Available?]
The system checks for description data in the second segment → If CY-N10-DESCRIPTION is not spaces and not low-values, proceed to store the second description; otherwise, terminate the process
[EBSBCCM Found?]
The system checks the retrieval status → Processing continues if segment is found, otherwise processing ends
[Lading Description Not Empty?]
The lading description field is evaluated → The description is processed only if it is not spaces or low-values
[CCM Sequence > 25?]
The CCM sequence number is evaluated → Processing stops if the sequence exceeds 25, otherwise continues to next segment
[Additional Lading Description Not Empty?]
The additional lading description content is evaluated → If the description is not spaces, the content is moved to the description array, otherwise it is skipped
[Description Sequence <= 10 AND EBSBCRT-AD Found?]
The description sequence counter is evaluated → Processing continues only if sequence counter is 10 or less AND EBSBCRT-AD segments are still available
[Has Consolidated Shipment Number?]
The system checks the segment for consolidated shipment indicators → If a consolidated shipment number is present, the system proceeds to process V2 motor vehicle segments within that consolidation
[EBSBCCX MV Segment Found?, MV Segment Found?]
A segment retrieval is attempted → The system determines if the motor vehicle segment was found or not found
[Vehicle ID Number Not Empty?]
If the vehicle identification number field → VIN processing continues if the vehicle ID is not empty or spaces, otherwise moves to next V2 segment
[VIN Number Available?]
If the VIN field content → Processing continues if VIN is not equal to spaces or low-values, otherwise VIN processing is skipped
[RF segment found?]
Database operation completes → System checks if RF segment data was found and sets appropriate processing flag
[V2 segment found?]
Database operation completes → System checks if V2 segment data was found and continues processing accordingly
[Vehicle ID number not empty?]
System examines the vehicle ID number field → System verifies the vehicle ID number is not empty or spaces
[Are cargo descriptions available?]
The description compression process is initiated → The system should verify that cargo descriptions (WS-DESC-1) contain actual data and are not empty spaces before proceeding with compression
[Extract Importer Information]
The segment has entity ID code 'IM' AND name is not blank AND ID code qualifier is 'M5', 'BN', or 'AI' AND ID code is not blank → Consider the importer data valid and complete for CSA processing
[Validate CSA Qualification]
A complete sequence exists with N1-01 'IM', N1-02 importer name (not blank), N1-03 qualifier ('M5'/'BN'/'AI'), and N1-04 business number (not blank) → Consider the importer information valid for CSA processing
[N1 Segment Found?]
The retrieval operation completes → The system checks if a valid N1 segment was found and continues CSA processing only if found, otherwise skips CSA validation
[Entity ID = 'IM' AND Name Not Empty?]
The system validates the segment data → The system verifies that the entity ID code equals 'IM' AND the name field is not empty, proceeding with qualifier validation only if both conditions are met
[Search SHIPMINE for N1-01 IM Segment]
The system searches through data lines from the current start index to position 5 → The system identifies any data line that begins with ' N1-01 IM' and sets the N101 found flag
[Check Next Data Line for N1-03]
The system examines the next data line for N1-03 qualifier information → If the data line contains ' N1-03 M5', ' N1-03 BN', or ' N1-03 AI', the corresponding qualifier (M5, BN, or AI) is stored as the business number qualifier
[Data Index <= 5?]
Checking if more data lines exist in the current segment → The system validates that the data index is less than or equal to 5 to stay within segment boundaries
[SHIPMINE Data Found?]
Checking if the segment retrieval was successful → The system validates that the SHIPMINE data was found (status code is spaces) to determine if more data is available for searching
[N1 Importer Segment Found?]
If the retrieval status → Processing continues if segment is found, otherwise CSA processing is skipped
[Check Entity ID Code = 'IM']
The system checks the entity ID code in the N1 segment → Processing continues only if the entity ID code equals 'IM' indicating an importer
[Entity ID = 'IM' AND Name Not Empty?]
The system validates the entity name and ID code are not empty → Processing continues if both name and ID code contain valid data, otherwise CSA processing ends
[Set Business Number Qualifier M5/BN/AI]
Processing business number qualifier information → Set the business number qualifier to M5, BN, or AI respectively based on the segment data
[Clear Business Number Qualifier]
Business number extraction fails → Clear the business number qualifier field to spaces
[Check Entity ID Code = 'IM']
The system checks the entity ID code in the N1 segment → The system proceeds only if the entity ID code equals 'IM' (Importer)
[Valid Importer Name?]
The system checks the N1 name field → The system proceeds only if the name field is not spaces
[CSA Data Found in BOL?]
The importer data is evaluated for CSA validity → If entity ID is 'IM' with non-empty name and ID code qualifier is 'M5' with non-empty ID code, set CSA indicator ON and copy data; if qualifier is 'BN' or 'AI' with valid data, copy data only; otherwise check Fastway system
[CSA Data Found in Fastway?]
The Fastway importer data is evaluated for CSA validity → If N1-01 IM entity found with N1-02 name, N1-03 qualifier ('M5', 'BN', or 'AI'), and N1-04 ID code, then if qualifier is 'M5' set CSA indicator ON and copy all data; otherwise copy data without setting CSA indicator; if no valid data found, set CSA indicator OFF
[Description Index <= 7?]
The description index exceeds 7 → The system should stop processing descriptions for the current segment and increment the description sequence counter
[Additional Lading Description Not Empty?]
The additional lading description is not empty (not spaces) → The system should store the description in the description array at the current array index and increment both the description array index and description index
[Additional Lading Description Not Empty?]
The additional lading description is empty (contains only spaces) → The system should skip storing the description and only increment the description index to continue processing the next description

As an EDI Gateway Service,
I want to orchestrate and execute all GCCCCADD EDI data mapping and validation logic,
So that I can ensure strict compliance with US Customs (P140) automated payload constraints in a single consolidated service.

Prerequisites & Setup

[Initialize Working Variables]
Working variables need to be set to initial state → Set message index to zero, initialize counters, clear message fields, and set error flags to off state
[Initialize Table Lookup Parameters]
Preparing to call the table lookup function → The system clears all table lookup parameters including key values, flags, and return codes
[Initialize Weight and Quantity Counters]
Starting weight and quantity processing → Set commodity weight counter to zero and number of units counter to zero
[Initialize Commodity Counters]
Commodity processing begins → Weight counter is set to zero AND quantity counter is set to zero
[Initialize EDI BOL I/O Parameters]
The system begins the EDI BOL segment retrieval process → The EDI BOL I/O parameters are cleared and initialized to spaces
[Initialize EBWLGIO Parameters]
The system begins weight segment retrieval process → Communication parameters are cleared and accept status is set to GE for database access
[Initialize Hazmat Sequence Counter]
The system prepares to read hazmat segments → The hazmat sequence counter is set to 1
[Initialize HS Sequence to 1]
Beginning to search for hazmat shipping information → The hazmat shipping info sequence counter is set to 1
[Initialize CCM Sequence to 1]
The system begins to read hazmat commodity segments → The CCM sequence counter is initialized to 1 to start reading from the first hazmat segment
[Initialize Search Parameters]
The search initialization is performed → The entity not found flag is set to true and the transportation segment found flag is set to true
[Initialize Search Parameters]
The search parameters need to be initialized → The organization ID status is set to not found and the transportation segment found status is set to true
[Initialize EBWLGIO Parameters]
The system initializes the retrieval parameters → The EDI BOL key, MCOA sequence number, segment type as EBSMCOA, type as OC, operator as equals, and function code as GU are set for the geographic data lookup
[Initialize CCN Processing Loop]
The system begins processing the CCN array → The system initializes CCN index counter starting from 1 and prepares for loop iteration
[Initialize Weight and Quantity Counters]
The system begins commodity quantity processing → Weight counter and quantity counter are both initialized to zero
[Initialize Weight Counters]
Starting weight processing for commodity segments → Initialize commodity weight counter to zero and number of units counter to zero
[Initialize Fastway Data Retrieval]
The system needs to obtain weight and quantity information → The system initializes Fastway SHIPCOMM data retrieval and sets the get function to 'GU' for first record
[Initialize UC Segment Record]
The system begins building UC segment data → A new GCSCCS55 segment record is initialized with empty values
[Initialize BN Segment Record]
Starting beneficial owner segment creation → A new beneficial owner segment record is initialized with empty values
[Initialize C1 Entity Segment]
The system begins C1 entity segment creation → A new C1 entity segment structure is initialized with empty values
[Initialize N1 Segment Record]
Starting notify party processing → A new N1 segment record is initialized with empty values
[Initialize Empty N1 Segment]
The system begins to process PF or SS entity segments → An empty N1 segment structure is initialized with spaces
[Initialize Table Lookup Parameters]
Setting up the table lookup operation → The system should clear all lookup parameters, set function code to 'GU' for get unique operation, set table identifier to 'MS' for message table, and use the error message number as the search key
[Initialize EDI BOL Access Parameters]
The system prepares to access EDI BOL data → The EDI BOL I/O work area is cleared to spaces, the database accept status is set to 'GE', and all segment data areas are initialized to spaces
[Initialize Search Variables]
The system initializes search parameters → The D5-ORG-ID found flag is set to false and TN segment found flag is set to true
[Initialize MCOA Sequence Counter]
The system begins processing miscellaneous charges or allowances → The MCOA sequence counter is initialized to 1 to start processing from the first segment
[Initialize Weight and Quantity Counters]
The system begins commodity quantity processing → The system sets commodity weight counter and number of units counter to zero
[Initialize Weight Counters]
The system begins weight extraction process → The system should initialize commodity weight counter and number of units counter to zero
[Initialize Fastway Data Retrieval]
The system needs to obtain commodity weight and quantity information → The system should initialize Fastway SHIPCOMM data retrieval and set the get function to 'GU' for first record retrieval
[Initialize SF Segment]
Stuffer entity processing begins → A new stuffer segment structure is initialized with empty values
[Initialize BN Segment Record]
Starting beneficial owner segment processing → A new beneficial owner segment record is initialized with empty values
[Initialize C1 Segment]
C1 carrier entity processing begins → A new C1 segment structure is initialized with empty values
[Initialize Entity Segment]
The system begins to build PF or SS entity segments → The entity segment data structure is initialized to spaces
[Initialize Search Parameters]
The system initializes the search process → Clear search segments, set waybill key as search key, and prepare for equipment sequence iteration
[Initialize Table Access Parameters]
The system prepares to access the message repository → All table access parameters should be cleared and initialized to ensure clean lookup operation
[Initialize Importer Segment]
Importer processing begins → The importer segment workspace is cleared and initialized to spaces
[Initialize Importer Segment]
The importer segment needs to be initialized → All importer segment fields are cleared to spaces
[Initialize EDI BOL Request Parameters]
The system initializes the EDI BOL request parameters → The address segment structure is cleared and ready for data retrieval
[Initialize CNS Search Variables]
The system begins to search for CNS segments → The CNS indicator flag is set to not found and sequence counter is initialized to 1
[Initialize Importer Segment]
Starting importer data processing → The customs record segment GCSCCS55 should be cleared to spaces
[Initialize EBSNRSC Parameters]
System initializes EBSNRSC segment parameters → EBWLGIO structure is cleared, segment type is set to 'EBSNRSC', function code is set to 'GU', operator is set to '=', sequence number is set to '01', and accept status is set to 'GE'
[Initialize EBSNRSA Parameters]
System initializes EBSNRSA segment parameters → EBWLGIO structure is cleared, segment type is set to 'EBSNRSA', function code is set to 'GU', operator is set to '=', EDI BOL key is assigned to root key, sequence numbers are set to '01', and accept status is set to 'GE'

Core Acceptance Criteria

[Border Arrival Date Calculation]
The system calculates the border arrival ETA using the date calculation service → Add the configured number of days to the waybill date to determine border arrival ETA. If the date calculation fails, add an error message for invalid waybill date
[Equipment Validation]
The system validates the car ID using the GCCCARID service → Call GCCCARID service to validate the conveying car. If validation returns all asterisks, add error message for invalid conveying car. If validation succeeds, update conveying car with validated value
[Weight and Quantity Roll-up]
The system rolls up weight and quantity information → For each commodity sequence 1-98, retrieve EDI commodity data and add lading quantity to total units. For first sequence, get weight data and set weight unit based on metric indicator. If no EDI data found, retrieve FastWay commodity data using GU then GN functions, adding units and weight from each commodity record
[Consolidated Load Indicator Retrieval]
The system checks for consolidated load indicators → For each special handling sequence 1-98, retrieve EDI special handling data. If special handling code equals 'CNS', set consolidated indicator to 'Y'. If no CNS code found, set consolidated indicator to blank
[Description Data Compression]
The system compresses the description data → Call GCCCOMP service with 45000 byte source description and 22500 byte target description lengths. Move compressed description to cargo record lading description field. Distribute compressed description data across 46 cargo data segments in customs record 53
[Hazardous Material Processing]
The system processes hazardous material information → First check EDI hazmat data for UN numbers and proper shipping names. If not found in EDI, check FastWay emergency response data for UN codes. If still not found, lookup commodity master for hazmat classification and UN numbers. Extract UN number and commodity description for dangerous goods
[Shipper Record Building]
The system builds the shipper customs record → Set entity ID to 'SH', sequence to '0001'. If EDI shipper data found, use consignor name and shipper chop from EDI, get address from EDI address segments, get contact information from EDI contact segments. If EDI data not found, use shipper data from FastWay shipment root. Validate all segments and insert customs record
[Consignee Record Building]
The system builds the consignee customs record → Set entity ID to 'CN', sequence to '0002'. If EDI consignee data found, use shipper name and consignee chop from EDI, get address from EDI address segments, get contact information from EDI contact segments. If EDI data not found, use consignee data from FastWay shipment root. Validate all segments and insert customs record
[N1 Entity Segment Building]
The system builds N1 entity segments → For each entity type (SF, UC, BN, C1, N1, PF, SS, 11, MC, OO, FW, NN), search EDI transportation data for matching organization ID. If found, extract entity information, address data, and contact information. Build complete N1 segment with entity ID, name, address, and contact details. Validate segment data and insert customs record with appropriate sequence number
[Importer Segment Building]
The system builds the importer segment → If EDI importer data found, create importer record with EDI details and manage CSA indicator based on business number qualifier. If EDI data not found but backed up importer data exists, use backed up data. If AU table data found and no other importer data, create importer record from AU table with business number qualifier 'M5' and turn on CSA indicator
[Corrector EDI with Existing Importer Data?]
The system checks for existing importer data → The system should initiate backup process if all importer fields are populated
[Skip Backup - No Existing Data]
The backup process evaluation occurs → The system should skip backup operations and continue with normal processing
[Date Calculation Successful?]
The system checks the calculation result status → If calculation is successful, the new calculated date is set as border arrival ETA, otherwise an invalid waybill date error message is retrieved and added to the message collection
[Call GCCTBIO to Access MS Table]
The system calls GCCTBIO with function code 'GU' and table ID 'MS' → The system attempts to retrieve the message text from the MS table using the error message number as the key
[Set Empty Message Text]
The system needs to handle the missing message scenario → The system clears the message table segment to spaces
[Table Lookup Successful?]
The table lookup returns successfully → The system should move the table segment to the message structure, extract the English text from the MS table, and move the text to the message label for display
[Move Table Data to GCSTBRTMC]
Valid table data is returned → The table segment data is moved to the MC table structure
[Move Table Data to Working Storage]
The lookup returns successful status → The retrieved table data is moved to the appropriate working storage segment and success flag is set
[Set Failure Flag]
The lookup returns unsuccessful status → The table segment is cleared to spaces and failure flag is set
[Lookup CM Table with Destination Station Number]
The system calls GCCTBIO with table ID 'CM' and destination station number as sequence ID → The system retrieves CM table segment data for further processing
[Get Port Manifest Upon from CM Table]
The system moves the CM table segment to GCSTBRTCM structure → The system extracts the port manifest upon value for subsequent MC table lookup
[Lookup MC Table with Port Manifest Upon]
The system calls GCCTBIO with table ID 'MC' and port manifest upon as sequence ID → The system retrieves MC table segment data for sub-location code extraction
[Set Sub-location Code from MC Table]
The system moves the MC table segment to GCSTBRTMC structure → The system assigns the MC sub-location code to the cargo manifest sub-location code field
[Set Sub-location Code to Spaces]
The CM table lookup fails to return valid data → The sub-location code should be set to spaces without proceeding to MC table lookup
[Extract Port Manifest Upon from CM Data]
The system accesses the CM table segment data → The port manifest upon value is extracted and prepared for MC table lookup
[Set Sub-location Code to Retrieved Value]
The system accesses the MC table segment data → The sub-location code is extracted and assigned to the cargo manifest sub-location code field
[Process Each Commodity Segment from EDI BOL]
The system processes commodity segments starting from sequence 1 and continuing until no more segments are found or sequence exceeds 98 → The system retrieves each EBSBCCM commodity segment using the EDI BOL key and commodity sequence number
[Add Lading Quantity to Total Units]
The system processes the commodity segment → The system adds the L0-LADING-QTY value to the running total of units
[Get EBSBCCR Weight Segment]
The system attempts to retrieve the corresponding EBSBCCR weight segment with type 'CR' and dependent key 'CR001' → If the weight segment is found, the system extracts the N7-WEIGHT value, otherwise sets the weight to zero
[Set Quantity Qualifier from Lading Data]
The system extracts quantity information from the segment → The system sets the lading quantity qualifier to the L0-LADING-QTY-QUAL value from the commodity segment
[Fall Back to Fastway SHIPCOMM Data]
The system needs to obtain weight and quantity information → The system switches to processing Fastway SHIPCOMM segments starting with the first segment using 'GU' function
[Get First SHIPCOMM Segment]
SHIPCOMM segments are available → The system adds NUM-UNITS from SHIPCOMM to the total units, sets quantity qualifier to 'PCS', and adds weight based on metric indicator (MET-CMOD-WGT for metric, CMOD-WGT for standard)
[Get Next SHIPCOMM Segments]
Additional SHIPCOMM segments are available → The system continues processing each subsequent segment using 'GN' function, accumulating units and weight until no more segments are found
[Get EBSBCCM Commodity Segment]
Retrieving EBSBCCM segment with type 'CM' and current sequence number → If invalid EDI BOL flag is set, mark segment as not found, otherwise call EBCLGIO and set found flag based on status
[Add Lading Quantity to Total]
Processing the commodity segment → Add the lading quantity from the segment to the total number of units counter
[Get EBSBCCR Weight Segment]
Retrieving EBSBCCR weight segment with type 'CR' and dependent key 'CR001' → If invalid EDI BOL flag is set, mark weight segment as not found, otherwise call EBCLGIO and set found flag based on status
[Extract Total Weight]
Processing weight information → Move the N7 weight value to the commodity weight counter
[Set Weight to Zero]
Processing weight information → Set commodity weight counter to zero
[Determine Weight Unit from Metric Indicator]
Determining weight unit from shipment root metric indicator → If metric indicator is 'M' or 'L', set weight unit to kilograms, otherwise set weight unit to pounds
[Set Quantity Qualifier from Segment]
Setting quantity qualifier for the shipment → Move the lading quantity qualifier from the commodity segment to the customs quantity qualifier
[Fall Back to Fastway SHIPCOMM Data]
Falling back to Fastway data processing → Set SHIPCOMM found flag and set get function to 'GU' for first segment retrieval
[Get First SHIPCOMM Segment]
Retrieving SHIPCOMM segment with 'GU' function → Call FWCWBIO with shipment root key and SHIPCOMM segment type, set found flag based on status
[Add SHIPCOMM Quantities and Weights]
Processing Fastway commodity data → Add number of units from SHIPCOMM to total units, and if metric indicator is 'M' or 'L', add metric weight and set unit to kilograms, otherwise add standard weight and set unit to pounds
[Get Next SHIPCOMM Segments]
Retrieving additional SHIPCOMM segments → Set get function to 'GN' and continue processing until no more segments are found
[Add Additional SHIPCOMM Data]
Processing additional Fastway data → Add number of units to total, set quantity qualifier to 'PCS', and add appropriate weight based on metric indicator
[Get EBSBCCM Commodity Segment]
The system retrieves EBSBCCM commodity segment with type 'CM' and the current sequence number → If the segment is found, add the L0-LADING-QTY to the running total of units, otherwise set commodity segment not found flag
[Get EBSBCCR Weight Segment]
The system retrieves EBSBCCR weight segment with type 'CR' and dependent key 'CR001' → If weight segment is found, extract N7-WEIGHT value, otherwise set weight to 0, and set weight unit to KG if metric indicator is 'M' or 'L', otherwise set to LB, and capture L0-LADING-QTY-QUAL as quantity qualifier
[Get First SHIPCOMM Record]
The system retrieves the first SHIPCOMM record using 'GU' function → If SHIPCOMM is found, add NUM-UNITS to quantity total, set quantity qualifier to 'PCS', and add MET-CMOD-WGT to weight if metric indicator is 'M' or 'L', otherwise add CMOD-WGT, and set weight unit accordingly
[Set CCM Sequence to 1]
The system prepares to read commodity segments → The CCM sequence counter is set to 1
[Get EBSBCCM Segment]
The system attempts to retrieve EBSBCCM segment data → The system calls EBCLGIO to fetch the commodity segment for the current sequence
[EBSBCCM Segment Found?]
The system checks the retrieval status → IF the segment is found THEN continue processing ELSE use FastWay fallback data
[Extract Lading Quantity from L0-LADING-QTY]
The system processes the segment data → The lading quantity is extracted from L0-LADING-QTY field
[Add to Total Units Counter]
The system updates totals → The lading quantity is added to the total units counter (WS-NUM-UNITS-9)
[First Segment?]
The system checks the sequence number → IF CCM sequence equals 1 THEN retrieve weight segment and set quantity qualifier ELSE skip weight processing
[Get EBSBCCR Weight Segment]
The system needs weight information → The system calls EBCLGIO to retrieve EBSBCCR segment with type 'CR' and dependent key 'CR001'
[Weight Segment Found?]
The system checks the retrieval status → IF weight segment is found THEN extract N7-WEIGHT value ELSE set weight to zero
[Extract Weight from N7-WEIGHT]
The system processes weight data → The weight value is extracted from N7-WEIGHT field and stored in WS-CMOD-WEIGHT-9
[Determine Weight Unit from Metric Indicator]
The system determines the weight unit → IF metric indicator is 'M' or 'L' THEN set weight unit to kilograms ELSE set weight unit to pounds
[Extract Quantity Qualifier from L0-LADING-QTY-QUAL]
The system sets quantity qualifier information → The quantity qualifier is extracted from L0-LADING-QTY-QUAL and stored in GCCC-LADING-QUANTITY-QUALIFIER
[Increment CCM Sequence Counter]
The system prepares for the next segment → The CCM sequence counter (WS-CCM-CM-SEQ) is incremented by 1
[More Segments Available?]
The system checks for continuation → IF CCM sequence is less than or equal to 98 AND segments are still being found THEN continue processing ELSE complete commodity processing
[No EDI Data - Use Fastway Fallback]
The system needs commodity data → The system retrieves commodity information from FastWay SHIPCOMM segments using GU and GN functions
[Set Segment Type to EBSBCCM]
The system prepares to retrieve commodity segment data → The segment type is set to 'EBSBCCM' to specify commodity segment retrieval
[Set Function Code to GU]
The system prepares the database retrieval operation → The function code is set to 'GU' to Execute a get unique operation
[Set EDI BOL Key from Waybill]
The system needs to identify the specific bill of lading → The EDI BOL key from the waybill is assigned to the root key parameter
[Set Type to CM - Commodity]
The system needs to specify the commodity segment subtype → The type identifier is set to 'CM' to indicate commodity information
[Set Sequence Number]
The system needs to identify a specific commodity segment occurrence → The sequence number from the commodity sequence counter is assigned to the segment parameters
[Call EBCLGIO to Retrieve Segment]
The system executes the segment retrieval operation → The EBCLGIO program is called with the configured parameters to retrieve the EBSBCCM segment
[Segment Found?]
The system checks the retrieval status → If the status code is spaces, the segment was found successfully, otherwise the segment was not found
[Set EBSBCCM Found Flag]
The system processes the successful retrieval result → The EBSBCCM found flag is set to true to indicate successful segment retrieval
[Extract Lading Quantity]
The system processes the retrieved commodity data → The lading quantity (L0-LADING-QTY) is added to the running total of units
[Set EBSBCCM Not Found Flag]
The system processes the failed retrieval result → The EBSBCCM not found flag is set to true to indicate unsuccessful segment retrieval
[Set Segment Type to EBSBCCR]
The system configures segment type for database query → Segment type is set to EBSBCCR to target weight records
[Set Function Code to GU]
The system sets database operation type → Function code is set to GU to retrieve unique weight record
[Set Root Key from EDI BOL Key]
The system configures shipment identification → Root key is set to EDI BOL key to target specific shipment weight data
[Call EBCLGIO to Retrieve Weight Data]
The system executes database retrieval operation → EBCLGIO is called with communication parameters to retrieve weight segment data
[Set Weight Segment Found Flag]
Database status indicates successful retrieval (status code is spaces) → Weight segment found flag is set to true
[Set Weight Segment Not Found Flag]
Database status indicates retrieval failure (status code is not spaces) → Weight segment found flag is set to false
[Apply Weight Unit to Commodity Weight]
Processing commodity weight from EDI BOL or shipment commodity data → The system adds the metric commodity weight to the total weight calculation and sets the weight unit flag to kilograms
[Apply Weight Unit to Commodity Weight]
Processing commodity weight from EDI BOL or shipment commodity data → The system adds the standard commodity weight to the total weight calculation and sets the weight unit flag to pounds
[Check EDI BOL Weight/Quantity Data]
The system checks EDI BOL data for weight and quantity values → If both EDI weight equals zero AND EDI quantity equals zero, proceed to Fastway SHIPCOMM fallback processing, otherwise use EDI data
[EDI Weight = 0 AND Quantity = 0?]
Both EDI weight equals zero AND EDI quantity equals zero → Initiate Fastway SHIPCOMM record processing to obtain weight and quantity data
[Process EBSBCCM Commodity Segments]
The system processes commodity segments from sequence 1 to 98 until no more segments found → The system accumulates lading quantity from each segment and captures quantity qualifier from first segment
[Process EBSBCCR Weight Segments]
The system retrieves weight segment for the first commodity sequence → The system captures weight value and sets weight unit based on metric indicator from shipment root
[Fall Back to Fastway SHIPCOMM Data]
The system retrieves first SHIPCOMM record and processes all subsequent SHIPCOMM records → The system accumulates units and weight from all SHIPCOMM records and sets quantity qualifier to 'PCS'
[Set Weight Units Based on Metric Indicator]
The system checks the metric indicator from shipment root data → The system sets weight unit to kilograms if metric indicator is 'M' or 'L', otherwise sets to pounds
[Process EDI BOL Commodity Segments]
The system processes each commodity segment sequentially from 1 to 98 → Each found commodity segment contributes its quantity to the total and the first segment provides weight and unit information
[Get Weight from EDI BOL]
Weight data is extracted from the commodity segment → The weight value is set from the segment and weight unit is determined as kilograms if metric indicator is M or L, otherwise pounds
[Fall Back to Fastway SHIPCOMM Data]
The system retrieves Fastway SHIPCOMM data using GU and GN functions → Weight and quantity are accumulated from all SHIPCOMM records with quantity qualifier set to PCS and weight unit determined by metric indicator
[Set Search Parameters]
Search parameters need to be configured for EBSBCKS segment retrieval → The search sequence counter is set and CNS indicator flag is set to not found
[Loop Through EBSBCKS Segments]
The system retrieves an EBSBCKS segment using the current sequence number → The EBSBCKS segment is retrieved from the EDI BOL database using the waybill key and sequence number
[Check H3 Special Handling Code]
The system examines the H3 special handling code field → The H3 special handling code value is extracted for comparison
[Code = 'CNS'?]
The system compares the special handling code value → If the code equals 'CNS', the consolidated indicator is found, otherwise the search continues
[Continue Search Next Sequence, Increment Sequence Counter]
The search needs to continue to the next sequence → The sequence counter is incremented by 1
[Set Consolidated Load = 'Y']
The consolidated load indicator needs to be set → The consolidated load field is set to 'Y'
[Set Consolidated Load = Space]
The consolidated load indicator needs to be set → The consolidated load field is set to space
[Check EDI BOL for Shipper Data]
The system checks for EDI BOL shipper segment availability → If EDI BOL HN segment is found, extract shipper from EDI BOL, otherwise use Fastway SHIPROOT data
[Get Shipper Name from F1-CONSIGNOR-NAME]
Extracting shipper identification information → Set shipper entity ID to 'SH', get shipper name from F1-CONSIGNOR-NAME, and get shipper CHOP from F1-SHPR-CHOP
[Extract Address from EDI HA Segment]
Processing shipper address information → Extract address line 1 from F2-ADDL-NAME-ADDR-1 and address line 2 from F2-ADDL-NAME-ADDR-2, and if address line 1 is empty set it to 'NA'
[Use Fastway SHIPROOT Address Data]
Processing shipper address information → Use SHPR-ADDR array from SHIPROOT, set address line 1 from SHPR-ADDR(1) or 'NA' if empty, and clear address line 2
[Extract City/State from EDI HC Segment]
Processing shipper location information → Extract city from F4-CITY-NAME, state from F4-STATE-PROV-CODE, postal code from F4-POSTAL-CODE, and country from F4-COUNTRY-CODE
[Parse Fastway Address for City/State]
Processing shipper location information from Fastway data → Parse SHPR-ADDR(2) to extract city name, state/province code, postal code, and determine country code from state lookup table
[Extract Contact from EDI GP Segment]
Processing shipper contact information → Extract contact function code from PER-CONTACT-FUNC-CODE, contact name from PER-NAME, communication number qualifier from PER-COMMUN-NO-QUAL, and communication number from PER-COMMUN-NUMBER
[No Contact Information Available]
Processing shipper contact information → Leave all contact fields empty (contact function code, name, communication qualifier, and communication number)
[Extract Shipper from Fastway SHIPROOT]
Extracting shipper information → Set entity ID to 'SH', get shipper name from SHPR-NM, get shipper CHOP from SHPR-CHOP, and clear ID code qualifier and ID code fields
[Check EDI BOL for Consignee Data]
The system checks for consignee data in the EDI BOL → The system retrieves the EBSNRSC segment with type 'CN' and sequence '01' and sets the found/not found status
[Extract Consignee Name from EDI BOL]
The system processes the consignee segment → The entity ID code is set to 'CN', the consignee name is extracted from D1-SHIPPER-NAME field, and the CHOP code is extracted from D1-CONS-CHOP field
[Check EDI BOL for Address Data]
The system checks for address data in the EDI BOL → The system retrieves the EBSNRSA segment with type 'CN', sequence '01', address type 'CA', and address sequence '01'
[Use Fastway Address Data]
The system falls back to Fastway data → Address line 1 is set from CONS-DATA(3) or 'NA' if empty, and address line 2 is set to spaces
[Check EDI BOL for City/State Data]
The system checks for city/state data in the EDI BOL → The system retrieves the EBSNRSA segment with type 'CN', sequence '01', address type 'CC', and address sequence '01'
[Extract City/State/Postal from EDI BOL]
The system processes the city/state segment → City name is set from D4-CITY-NAME, state/province code is set from D4-STATE-PROV-CODE, postal code is set from D4-POSTAL-CODE, and country code is set from D4-COUNTRY-CODE
[Use Fastway City/State Data]
The system falls back to Fastway data → CONS-DATA(4) is parsed into city name, state/province code, and postal code components, and country code is determined from state/country lookup table
[Check EDI BOL for Contact Info]
The system checks for contact data in the EDI BOL → The system retrieves the EBSNRSA segment with type 'CN', sequence '01', contact type 'GP', and contact sequence '01'
[Extract Contact Information]
The system processes the contact segment → Contact function code is set from PER-CONTACT-FUNC-CODE, contact name is set from PER-NAME, communication number qualifier is set from PER-COMMUN-NO-QUAL, and communication number is set from PER-COMMUN-NUMBER
[Use Fastway Consignee Data]
The system falls back to Fastway data → Entity ID is set to 'CN', consignee name is set from CONS-DATA(1), CHOP code is set from CONS-CHOP, and ID code qualifier and ID code are set to spaces
[Distribute Description Data to GCSCCS53 Array]
Distributing description data to array structure → All 46 description segments are moved from work area to GCSCCS53 cargo data array
[Check for EDI BOL Hazmat Data]
The system checks for EDI BOL hazmat data in commodity segments with type 'CH' → The system identifies if hazmat segments exist and sets the appropriate processing flag
[Process EDI BOL Hazmat Data]
The system processes hazmat information from EDI BOL → The system extracts UN numbers and proper shipping names from the EDI BOL hazmat segments
[Extract UN Number from EDI]
The UN/NA identification code starts with 'UN' → The system moves the complete UN/NA identification code to the commodity UN number field and sets hazmat found flag
[Get Proper Shipping Name from EDI]
The system looks up the corresponding hazmat information segment → If the hazmat information segment is found, the proper shipping name is moved to the commodity description danger field
[Check Next EDI Hazmat Record]
The UN/NA identification code does not start with 'UN' → The system increments the commodity sequence number and continues searching if sequence is 98 or less and hazmat not yet found
[Check Fastway Hazmat Data]
The system checks Fastway shipment commodity data → The system retrieves shipment commodity information and looks up emergency response data
[Use Commodity Table for Hazmat Info]
The system accesses the commodity master table using the commodity code → The system retrieves commodity description and looks up associated hazmat codes
[Set Hazmat Fields to Spaces]
All hazmat data sources have been exhausted without finding valid information → The system clears both the UN number field and commodity description danger field to spaces
[Start Hazmat EDI Extraction]
The hazmat extraction process begins → The commodity description danger field and UN number field are cleared, and hazmat not found flag is set
[Get Next EBSBCCM-CH Segment]
The system attempts to retrieve a hazmat segment → The EBSBCCM CH segment is retrieved using the current sequence number, and hazmat found flag is updated based on retrieval success
[Extract UN Number from LH1 Segment]
The UN/NA identification code starts with 'UN' → The complete UN/NA identification code is extracted and stored as the commodity UN number, and hazmat found flag is set to true
[Retrieve LH3 Proper Shipping Name]
The system attempts to retrieve hazmat shipping details → The EBSBCHI HS segment is retrieved using the current sequence number
[Extract Proper Shipping Name]
The EBSBCHI HS segment contains proper shipping name data → The proper shipping name is extracted and stored as the commodity description danger field
[More Hazmat Segments?]
If continuation criteria → If hazmat has not been found and sequence counter is 98 or less, increment the counter and continue processing, otherwise end the extraction
[Increment Sequence Counter]
The sequence counter is less than or equal to 98 and hazmat is not found → The hazmat sequence counter is incremented by 1
[Set Sequence Counter to 1]
Beginning to search for hazmat segments → The commodity hazmat sequence counter is set to 1
[Get EBSBCCM-CH Segment]
Retrieving the EBSBCCM hazmat commodity segment with type 'CH' → The system attempts to read the hazmat commodity data for the specified sequence number
[Set Hazmat Found Flag]
Hazmat identification processing is successful → The hazmat found flag is set to true
[Get EBSBCHI Segment]
Retrieving the EBSBCHI hazmat shipping info segment with type 'HS' → The system attempts to read the hazmat shipping information for the current commodity and sequence
[Extract Proper Shipping Name from LH3-PROPER-SHIP-NAME]
Extracting the proper shipping name → The LH3-PROPER-SHIP-NAME value is moved to the commodity description danger field
[Increment CH Sequence Counter]
Continuing the search for valid hazmat information → The commodity hazmat sequence counter is incremented by 1
[More CH Segments Available?]
The sequence counter is less than or equal to 98 AND hazmat information has not been found → Continue processing additional hazmat commodity segments
[Get Proper Shipping Name]
The system accesses the LH3 hazmat information segment → The system should retrieve the proper shipping name from LH3-PROPER-SHIP-NAME field if available
[Store Proper Shipping Name]
The system processes the hazmat description data → The system should store the proper shipping name in the commodity description danger field
[Set EDI BOL Key Parameters]
The system prepares to read hazmat segments → The EDI BOL key is set as the root key parameter for segment retrieval
[Set Segment Type to EBSBCCM]
Configuring the segment retrieval parameters → The segment type is set to 'EBSBCCM' to target chemical hazmat segments
[Set Function Code to GU]
Setting up the database access parameters → The function code is set to 'GU' to Execute a get unique operation
[Set Type to CH - Chemical Hazmat]
Specifying the type of hazmat segment to retrieve → The type is set to 'CH' to identify chemical hazmat segments
[Set Sequence Number]
Preparing to retrieve a specific hazmat segment → The sequence number parameter is set to the current CCM sequence value
[Call EBCLGIO to Read Segment]
The system executes the database call → The EBCLGIO program is called to retrieve the EBSBCCM hazmat segment
[Set Hazmat Found Flag]
The system processes the found segment → The hazmat found flag is set to indicate successful segment retrieval
[Extract UN Number from LH1-UN-NA-ID-CD]
The system processes the hazmat data → The UN/NA identification code is extracted from the LH1-UN-NA-ID-CD field
[Increment CCM Sequence]
The system continues searching for hazmat data → The CCM sequence counter is incremented by 1 to target the next segment
[More Segments to Process?]
The system checks for continuation of hazmat processing → If the sequence is within limits and no valid UN number has been found, processing continues with the next segment, otherwise processing ends
[Set Hazmat Not Found Flag]
No valid UN number has been identified → The hazmat not found flag is set to indicate unsuccessful hazmat processing
[Read LH3 Segment for Description]
The system attempts to retrieve the LH3 proper shipping name from the EBSBCHI hazmat information segment → If the EBSBCHI hazmat segment is found, extract the LH3 proper shipping name and store it in the commodity description danger field, otherwise no description is available
[Set Hazmat Information Sequence Counter]
The system begins processing LH3 hazmat description segments → The hazmat information sequence counter is set to 1 to start processing from the first sequence
[Store Proper Shipping Name in Commodity Description Danger Field]
The system processes the extracted proper shipping name → The LH3 proper shipping name is stored in the commodity description danger field for inclusion in the customs manifest
[EDI Hazmat Data Found?]
The system searches for hazmat data sources → EDI hazmat data is checked first and used if available, otherwise system falls back to Fastway data sources
[SHIPCOMM Data Available?]
System attempts to access Fastway SHIPCOMM data → If SHIPCOMM data is found, proceed to SHIPERP segment access, otherwise mark no Fastway hazmat data available
[SHIPERPD Description Found?]
System accesses SHIPERPD segment for hazmat description → If SHIPERPD data is found, use the hazmat description, otherwise proceed with hazmat found flag set
[Continue to Commodity Table Lookup]
System has processed all available hazmat data sources → System continues to commodity table lookup for additional hazmat information if needed
[Get SHIPCOMM Segment]
The system attempts to retrieve commodity data from Fastway SHIPCOMM segment → The SHIPCOMM segment is retrieved and made available for hazmat processing
[Get SHIPERP Segment]
The system retrieves emergency response data from SHIPERP segment → SHIPERP segment containing hazmat identification codes is made available for validation
[Get SHIPERPD Segment]
The system attempts to retrieve SHIPERPD segment data using emergency response STCC code → SHIPERPD segment containing detailed hazmat descriptions is made available for extraction
[Extract Hazmat Description from ERPD-HAZ-DESC]
The system processes the hazmat description field from ERPD-HAZ-DESC → The first 15 characters of hazmat description are extracted and stored in the customs commodity danger description field
[EDI BOL Data Available?]
The system checks for EDI BOL data availability → If the origin road number is not zero, the system attempts to retrieve EDI BOL data from SHIPMIN segment
[Extract Shipper Information from EDI]
The system extracts shipper information → The EBSNRSC segment with entity type 'HN' and sequence '01' is retrieved to get shipper name and identification
[Extract Consignee Information from EDI]
The system extracts consignee information → The EBSNRSC segment with entity type 'CN' and sequence '01' is retrieved to get consignee name and identification
[Extract Entity Segments from EDI]
The system extracts entity segments → Various entity types (SF, UC, BN, C1, N1, PF, SS, 11, MC, OO, FW, NN) are retrieved from EBSNRSC segments based on their specific entity codes
[Extract Address Information]
The system extracts address information → Address segments (N3 and N4 types) are retrieved from EBSNRSA segments to get street addresses, city, state, postal code, and country information
[Process Contact Information]
The system processes contact information → Contact segments (PER type) are retrieved from EBSNRSA segments to get contact function code, name, communication number qualifier, and communication number
[Extract Commodity Information]
The system extracts commodity information → Commodity segments (CM type) and hazmat segments (CH type) are retrieved from EBSBCCM segments to get lading quantity, weight, and hazardous material information
[Process Transportation Segments]
The system processes transportation segments → Transportation segments (TN, T2, TA, T3 types) are retrieved from EBSNRTD segments to get transportation details, additional addresses, and contact information
[Extract MCOA Charge Information]
The system extracts MCOA charge information → MCOA segments (OT, ON, OC types) are retrieved from EBSMCOA segments to get organization details, addresses, and charge information for entities like freight forwarders and bill recipients
[Extract Shipper Name and CHOP from HN Segment]
The system processes shipper record building → The entity ID is set to 'SH', shipper name is extracted from consignor name field, and CHOP code is extracted from shipper CHOP field
[Get Shipper Address from HA Segment]
The system processes shipper address information → Address line 1 and address line 2 are populated from additional name/address fields, with 'NA' as default if address line 1 is blank
[Get Shipper City/State/Postal from HC Segment]
The system processes shipper location information → City name, state/province code, postal code, and country code are extracted from the corresponding HC segment fields
[Get Shipper Contact Info from GP Segment]
The system processes shipper contact information → Contact function code, contact name, communication number qualifier, and communication number are extracted from the GP segment
[Use Fastway Shipper Data as Fallback]
The system builds shipper record → Shipper CHOP, entity ID 'SH', and shipper name are populated from Fastway shipment root data, with address defaulting to 'NA' if blank
[Extract Consignee Name and CHOP from CN Segment]
The system processes consignee record building → The entity ID is set to 'CN', consignee name is extracted from shipper name field, and CHOP code is extracted from consignee CHOP field
[Get Consignee Address from CA Segment]
The system processes consignee address information → Address line 1 and address line 2 are populated from additional name/address fields, with 'NA' as default if address line 1 is blank
[Get Consignee City/State/Postal from CC Segment]
The system processes consignee location information → City name, state/province code, postal code, and country code are extracted from the corresponding CC segment fields
[Use Fastway Consignee Data as Fallback]
The system builds consignee record → Consignee CHOP, entity ID 'CN', and consignee name are populated from Fastway shipment root data, with address defaulting to 'NA' if blank and country lookup from state/province table
[Build Stuffer Entity from PN Segment]
The system processes stuffer entity building → Entity ID is set to 'SF', name is extracted from PN segment, and associated address information is retrieved from PA and PC segments with 'NA' default for missing address
[Build Ultimate Consignee from UN Segment]
The system processes ultimate consignee entity building → Entity ID is set to 'UC', name is extracted from UN segment, and associated address information is retrieved from UA and UC segments with 'NA' default for missing address
[Build Beneficial Owner from BN Segment]
The system processes beneficial owner entity building → Entity ID is set to 'BN', name and CHOP are extracted from BN segment, and associated address information is retrieved from BT and BY segments with 'NA' default for missing address
[Build Carrier Entity from TN Segment]
The system processes transportation entity building for organization IDs C1, N1, 11, MC, OO, or FW → Entity record is created with the organization ID as entity type, name extracted from TN segment, and associated address information retrieved from T2 and TA segments
[Build MCOA Entities from OT Segments]
The system processes MCOA entity building → Entity record is created with PF or SS as entity type, name and ID codes extracted from OT segment, and associated address information retrieved from ON and OC segments with 'NA' default for missing address
[Process NN Segments for Various Entity Types]
The system processes NN segments sequentially → For each valid entity ID found, entity name and CHOP are extracted, and associated address information is retrieved from GC and GA segments
[Get Entity Address from GC Segment]
The system processes entity address information → Address line 1 and address line 2 are populated from additional name/address fields, with 'NA' as default if address line 1 is blank
[Get Entity City/State/Postal from GA Segment]
The system processes entity location information → City name, state/province code, postal code, and country code are extracted from the corresponding GA segment fields
[Build Additional Entities]
Importer data is found in EDI BOL IM segment → Entity ID is set to 'IM', importer name and business number details are extracted, CSA indicator is managed, and address information is populated from associated segments
[Build Additional Entities]
The system builds importer record → Importer information is populated from backup data including CHOP, name, business number qualifier, business number, CSA indicator, address, city, state, postal code, country, and contact information
[EDI BOL Shipper Data Available?]
The system checks for EDI BOL shipper data availability by looking up EBSNRSC segment with type 'HN' and sequence '01' → If EDI BOL shipper data is found, use EDI data source; otherwise fallback to Fastway shipment root data
[Extract Shipper Name and CHOP from EDI BOL]
The system processes the shipper N1 segment data → Set entity ID to 'SH', extract shipper name from F1-CONSIGNOR-NAME, extract CHOP code from F1-SHPR-CHOP, and clear ID code qualifier and ID code fields
[Use Fastway Shipper Data]
The system needs shipper information for the manifest → Set entity ID to 'SH', extract shipper name from SHPR-NM of SHIPROOT, extract CHOP code from SHPR-CHOP of SHIPROOT, and clear ID code qualifier and ID code fields
[EDI BOL Shipper Address Available?]
The system checks for EDI BOL shipper address data by looking up EBSNRSA segment with types 'HN' and 'HA' → If EDI BOL address data is found, use EDI address source; otherwise use Fastway address data
[Extract Address from EDI BOL]
The system processes the shipper address information → Extract address line 1 from F2-ADDL-NAME-ADDR-1, extract address line 2 from F2-ADDL-NAME-ADDR-2, and if address line 1 is blank set it to 'NA'
[Use Fastway Address Data]
The system needs shipper address information → If SHPR-ADDR(1) is blank set address line 1 to 'NA', otherwise use SHPR-ADDR(1) for address line 1, and set address line 2 to spaces
[EDI BOL Shipper City/State Available?]
The system checks for EDI BOL shipper city/state data by looking up EBSNRSA segment with types 'HN' and 'HC' → If EDI BOL city/state data is found, use EDI source; otherwise parse Fastway address data
[Extract City/State/Postal from EDI BOL]
The system processes the shipper location information → Extract city from F4-CITY-NAME, extract state/province from F4-STATE-PROV-CODE, extract postal code from F4-POSTAL-CODE, and extract country code from F4-COUNTRY-CODE
[Parse Fastway Address for City/State/Postal]
The system needs shipper location information → Parse SHPR-ADDR(2) to extract city name, state/province code, and postal code, then lookup country code from state/province using TB-STATE-COUNTRY table
[EDI BOL Contact Info Available?]
The system checks for EDI BOL shipper contact data by looking up EBSNRSA segment with types 'HN' and 'GP' → If EDI BOL contact data is found, extract contact information; otherwise set contact fields to blank
[Extract Contact Information from EDI BOL]
The system processes the shipper contact information → Extract contact function code from PER-CONTACT-FUNC-CODE, extract contact name from PER-NAME, extract communication number qualifier from PER-COMMUN-NO-QUAL, and extract communication number from PER-COMMUN-NUMBER
[EDI BOL Consignee Data Available?]
The system checks for EDI BOL consignee data availability by looking up EBSNRSC segment with type 'CN' and sequence '01' → If EDI BOL consignee data is found, use EDI data source; otherwise fallback to Fastway shipment root data
[Extract Consignee Name and CHOP from EDI BOL]
The system processes the consignee N1 segment data → Set entity ID to 'CN', extract consignee name from D1-SHIPPER-NAME, extract CHOP code from D1-CONS-CHOP, and clear ID code qualifier and ID code fields
[Use Fastway Consignee Data]
The system needs consignee information for the manifest → Set entity ID to 'CN', extract consignee name from CONS-DATA(1) of SHIPROOT, extract CHOP code from CONS-CHOP of SHIPROOT, and clear ID code qualifier and ID code fields
[EDI BOL Consignee Address Available?]
The system checks for EDI BOL consignee address data by looking up EBSNRSA segment with types 'CN' and 'CA' → If EDI BOL address data is found, use EDI address source; otherwise use Fastway address data
[Extract Address from EDI BOL]
The system processes the consignee address information → Extract address line 1 from D2-ADDL-NAME-ADDR-1, extract address line 2 from D2-ADDL-NAME-ADDR-2, and if address line 1 is blank set it to 'NA'
[Use Fastway Address Data]
The system needs consignee address information → If CONS-DATA(3) is blank set address line 1 to 'NA', otherwise use CONS-DATA(3) for address line 1, and set address line 2 to spaces
[EDI BOL Consignee City/State Available?]
The system checks for EDI BOL consignee city/state data by looking up EBSNRSA segment with types 'CN' and 'CC' → If EDI BOL city/state data is found, use EDI source; otherwise parse Fastway address data
[Extract City/State/Postal from EDI BOL]
The system processes the consignee location information → Extract city from D4-CITY-NAME, extract state/province from D4-STATE-PROV-CODE, extract postal code from D4-POSTAL-CODE, and extract country code from D4-COUNTRY-CODE
[Parse Fastway Address for City/State/Postal]
The system needs consignee location information → Parse CONS-DATA(4) to extract city name, state/province code, and postal code, then lookup country code from state/province using TB-STATE-COUNTRY table
[EDI BOL Contact Info Available?]
The system checks for EDI BOL consignee contact data by looking up EBSNRSA segment with types 'CN' and 'GP' → If EDI BOL contact data is found, extract contact information; otherwise set contact fields to blank
[Extract Contact Information from EDI BOL]
The system processes the consignee contact information → Extract contact function code from PER-CONTACT-FUNC-CODE, extract contact name from PER-NAME, extract communication number qualifier from PER-COMMUN-NO-QUAL, and extract communication number from PER-COMMUN-NUMBER
[Process SF - Stuffer Entity]
The system processes SF entity data → The system extracts SF name, address information, city/state/postal data, and contact information, validates the entity data, and creates a record with entity ID 'SF'
[Process UC - Ultimate Consignee]
The system processes UC entity data → The system extracts UC name, address information, city/state/postal data, and contact information, validates the entity data, and creates a record with entity ID 'UC'
[Process BN - Beneficial Owner]
The system processes BN entity data → The system extracts BN name, consignee chop code, address information, city/state/postal data, validates the entity data, and creates a record with entity ID 'BN'
[Process C1 - Carrier Entity]
The system processes C1 entity data → The system extracts C1 name from EDI transportation data if found, otherwise uses consignee data from Fastway, gets address and contact information, validates the entity data, and creates a record with entity ID 'C1'
[Process N1 - Notify Party]
The system processes N1 entity data → The system extracts N1 name, address, and contact information, validates the entity data, and creates a record with entity ID 'N1'
[Process PF/SS - MCOA Entities]
The system processes PF/SS entity data → The system extracts entity name, ID code qualifier, ID code, address information from ON segment, city/state/postal data from OC segment, validates the entity data, and creates a record with the respective entity ID
[Process Additional Entities - 11, MC, OO, FW]
The system processes the additional entity data → The system extracts entity name, address information from T2 segment, city/state/postal data from TA segment, contact information from T3 segment, validates the entity data, and creates a record with the respective entity ID
[Process NN - Multiple Entities]
The system processes NN entity data for each sequence number → The system extracts entity name, consignee chop code, address information from GC segment, city/state/postal data from GA segment, validates the entity data, and creates a record with the entity ID from the NN segment
[Search Transportation Segments]
Transportation segment lookup is performed using segment type 'TN' and the current sequence → The system attempts to retrieve the transportation segment data from EBSNRTD
[Check D5-ORG-ID Match]
The organization ID needs to be extracted → The D5-ORG-ID field is extracted from the transportation segment data
[D5-ORG-ID Matches Target?]
The comparison is performed → If the D5-ORG-ID equals the target entity ID then a match is found, otherwise continue searching
[Mark Entity Found]
The entity found status is updated → The entity found flag is set to true
[Increment Search Sequence]
The search needs to continue to the next segment → The search sequence counter is incremented by 1
[More Segments to Search?]
The system checks for continuation of the search loop → If the transportation segment found flag is true then continue searching, otherwise stop the search
[Entity Located Successfully]
The search process completes successfully → The entity found flag remains true and the search sequence is decremented by 1 to reflect the correct position
[Entity Not Found]
The target entity ID was not matched in any segment → The entity not found flag remains true
[Set Sequence Counter to 1]
The sequence counter needs to be set for iteration → The sequence counter is set to 1 to begin searching from the first sequence
[Prepare EBSNRTD Segment Request]
The segment request is being prepared → The segment type is set to EBSNRTD, function code is set to GU, operator is set to equals, type is set to TN, and the current sequence number is assigned
[Execute EDI BOL Segment Retrieval]
The EDI BOL segment retrieval is executed → The EBCLGIO service is called with the configured parameters to retrieve the transportation segment
[Organization ID Matches Target?]
The organization ID needs to be validated against the target → If the retrieved organization ID equals the target organization ID then a match is found, otherwise continue searching
[Continue Search?]
The continuation criteria needs to be evaluated → If the segment was not found then set transportation segment not found status to true, otherwise if organization ID is not found then continue searching
[Adjust Final Sequence Counter]
The final sequence counter needs to be adjusted → The sequence counter is decremented by 1 to reflect the correct final sequence number
[Start MCOA Entity Processing]
MCOA entity processing begins → The MCOA sequence counter is initialized and processing flags are reset
[Get MCOA Segment by Sequence]
The system attempts to retrieve the MCOA segment → The MCOA segment data is retrieved from EBSMCOA using the sequence number
[Entity Type is PF or SS?]
The system checks the organization ID in the segment → If the organization ID is 'PF' or 'SS', the entity is processed, otherwise it is skipped
[Extract Entity Information]
The system extracts entity information → The organization ID is set as entity ID code, organization name is set as entity name, ID code qualifier and ID code are extracted from the segment
[Get MCOA Address Segment]
The system attempts to retrieve address information → The MCOA ON segment is retrieved using the same sequence number
[Address Segment Found?]
The system checks if address data is available → If address segment is found, extract address lines 1 and 2, otherwise set address line 1 to 'NA' and clear address line 2
[Get MCOA City/State Segment]
The system attempts to retrieve city/state information → The MCOA OC segment is retrieved using the same sequence number
[City/State Segment Found?]
The system checks if city/state data is available → If city/state segment is found, extract city name, state/province code, postal code and country code, otherwise clear all city/state information fields
[Insert Entity Record]
The system inserts the entity record → The entity record is inserted into the GCSCCS55 array with the appropriate sequence number
[More MCOA Segments?]
The system checks for more segments → The sequence counter is incremented and processing continues if more segments are available, otherwise MCOA processing ends
[Get MCOA Segment by Sequence - Retrieve EBSMCOA segment data with sequence number validation]
System attempts to retrieve EBSMCOA segment with type 'OT' (Other) → System successfully retrieves the MCOA segment data and sets found flag
[Set EDI BOL Key as Root Key]
System prepares to retrieve MCOA segment data → System sets EDI BOL key as root key, MCOA sequence number, segment type as EBSMCOA, type as OT, and function code as GU
[Set MCOA Not Found Flag]
Segment retrieval fails or segment type is not 'OT' → System sets MCOA not found flag to indicate unsuccessful retrieval
[Set EDI BOL Key and Sequence Number]
The system prepares to retrieve address information → The EDI BOL key is set from the stored key for record 55 processing and the MCOA sequence number is used as the sequence identifier
[Set Segment Type to EBSMCOA]
Setting up the data retrieval parameters → The segment type is set to 'EBSMCOA' to identify the correct data structure
[Set Type to ON for Address]
Specifying the type of MCOA data to retrieve → The type is set to 'ON' to indicate address information is required
[Call EBCLGIO to Retrieve ON Segment]
The system executes the data retrieval operation → EBCLGIO is called to retrieve the ON segment from the MCOA data structure
[ON Segment Found?]
The system checks the retrieval result → If the status code is spaces, the segment is considered found, otherwise it is not found
[Extract Address Line 1 from F6-ADDL-NAME-ADDR-1]
The system processes the address information → The first address line is extracted from F6-ADDL-NAME-ADDR-1 field and stored in the address info field
[Extract Address Line 2 from F6-ADDL-NAME-ADDR-2]
The system processes the address information → The second address line is extracted from F6-ADDL-NAME-ADDR-2 field and stored in the second address info field
[Set Address Found Flag]
The system updates the processing status → The address found flag is set to indicate successful retrieval
[Clear Address Line 2]
The system handles the missing address information → The second address line is cleared to spaces
[Set Address Not Found Flag]
The system updates the processing status → The address not found flag is set to indicate unsuccessful retrieval
[Call EBCLGIO to Retrieve Segment]
The system calls EBCLGIO to retrieve the segment data → The system attempts to fetch the geographic segment data from the EDI BOL database
[Segment Found?]
The system checks the status code from the retrieval operation → If status code equals spaces, the segment is found; otherwise, the segment is not found
[Extract City Name from F7-CITY-NAME, Extract State/Province Code from F7-STATE-PROV-CODE, Extract Postal Code from F7-POSTAL-CODE, Extract Country Code from F7-COUNTRY-CODE]
The system processes the segment data → The city name, state/province code, postal code, and country code are extracted from the F7 fields in the segment
[Move Data to N4 Address Fields]
The system populates the address fields → The extracted data is moved to the corresponding N4 address fields (N401-CITY-NAME, N402-STATE-PROV-CDE, N403-POSTAL-CDE, N404-COUNTRY-CDE)
[Set Geographic Data Found Flag]
The system completes the data extraction and population → The geographic data found flag is set to indicate successful processing
[Clear All N4 Address Fields]
The system handles the missing data condition → All N4 address fields (city name, state/province code, postal code, country code) are cleared to spaces
[Set Geographic Data Not Found Flag]
The system completes the failed retrieval processing → The geographic data not found flag is set to indicate unsuccessful processing
[Set CCN for Spawn]
Finalizing spawn message parameters → Assign the current CCN from the array to the spawn CCN field
[Set Action Code to 'AM']
Preparing the final spawn message → Set the spawn action code to 'AM' for automated manifest processing
[Spawn GCT0111E for Manifest Creation]
The spawn message is ready for execution → Call the spawn process GCT0111E to create a separate manifest for the current CCN
[Spawn GCT0111E for Manifest Creation]
The system invokes the GCT0111E manifest creation program → The system calls GCT0111E with the spawn message containing waybill, date, CCN, and action code information
[Process EDI Bill of Lading Data]
The system processes the EDI BOL data through GCCCBOL program → The system extracts CCN array data and makes it available for further processing
[Multiple CCNs Found in EDI BOL?]
The system checks if GCWCBOL-CCN-ARRAY-TBL contains data and is not spaces or low-values → The system identifies whether multiple CCNs need to be processed for manifest creation
[Prepare Spawn Message for GCT0111E]
The system prepares spawn message data → The system sets up waybill key, waybill date, extracted CCN, and action code 'AM' in the spawn message structure
[Set Waybill Key and Date]
The system sets waybill information in the spawn message → The system moves original waybill key to SPAWN-WAYBILL and waybill date to SPAWN-WAYBILL-DATE
[Set Current CCN]
The system assigns CCN to the spawn message → The system moves the current CCN value to SPAWN-CCN field in the message structure
[Set Action Code to 'AM']
The system sets the action code in the spawn message → The system assigns action code 'AM' to SPAWN-ACTION-CODE to indicate manifest creation action
[Call GCT0111E Program]
The system invokes the Z700-SPAWN-GCT0111E procedure → The system executes GCT0111E program with the prepared message data for manifest creation
[Check for EDI Importer Data]
The system checks for additional EDI importer data → Verify if EDI importer data exists (WS-S55-IMP-FOUND) for further processing decisions
[Business Number Qualifier BN or Blank?]
If the EDI business number qualifier → Check if business number qualifier is 'BN' or blank (spaces) to determine CSA indicator action
[Turn CSA Indicator OFF]
The system determines CSA indicator setting based on data source priority → Turn CSA indicator OFF to prioritize EDI importer data over AU table data
[Extract AU Importer Data]
The system processes the AU record data → The system extracts the importer name from the AU table segment and stores it for further processing
[Extract AU Business Number]
The system continues processing the AU record → The system extracts the business number from the AU table segment for importer business identification
[Check Business Number Qualifier?]
The business number qualifier is 'BN' or contains spaces → The system should set CSA indicator to OFF
[Reset CSA Indicator OFF for Duplicate Sources]
AU table importer data is found AND EDI BOL importer data exists with business number qualifier (BN or spaces) → Set CSA indicator to OFF to resolve data source conflict
[Save Current Description Data]
The system begins the description capture process → The current manifest data (GCSCCRT), cargo segment data (GCSCCS52), and all cargo description array elements (46 elements) are saved to backup variables for potential restoration
[Retrieve Description from Source CCN]
The description retrieval process is executed → The GCCCCIO2 program is called to fetch all segments (GCSCCS00, GCSCCRT, GCSCCS52, GCSCCS53, GCSCCS54, GCSCCS55, GCSCCS56) from the source CCN
[Retrieve Description from Related CCN]
The system retrieves description data from the related CCN → The system fetches all description segments including main description and cargo data array from the specified CCN
[Return Broker Information]
The system processes the successful lookup result → The broker information from the crossing table segment is made available for manifest processing
[Retrieve EBSBCCM Segment]
The system attempts to retrieve commodity segment EBSBCCM with type 'CM' → The system returns commodity segment data if found or sets not-found status if segment does not exist
[Add Lading Quantity to Total]
The segment contains lading quantity data → The lading quantity is added to the total quantity counter
[Retrieve Weight from EBSBCCR Segment]
The system processes weight data for the commodity → Weight information is retrieved from EBSBCCR segment with type 'CR' and dependent key 'CR001'
[Set Weight from N7-WEIGHT Field]
The segment contains N7-WEIGHT field data → The weight counter is set to the N7-WEIGHT field value
[Set Weight to Zero]
The system processes the first commodity segment → The weight counter is set to zero
[Set Quantity Qualifier from Lading Data]
The system processes the first commodity segment → The quantity qualifier is set to the lading quantity qualifier from the EDI data
[Use Fastway SHIPCOMM Data as Fallback]
The system needs commodity data for the shipment → The system retrieves commodity data from Fastway SHIPCOMM segments as fallback
[Retrieve First SHIPCOMM Segment]
The system retrieves the first SHIPCOMM segment using 'GU' function → The first commodity segment data is returned if available
[Add Units from SHIPCOMM to Total]
The segment contains number of units data → The number of units is added to the total quantity counter
[Add Weight Based on Metric Indicator]
The shipment root metric indicator is 'M' or 'L' → Metric commodity weight is added to total weight, otherwise standard commodity weight is added
[Get Next SHIPCOMM Segment]
The system continues processing additional commodity segments using 'GN' function → Additional commodity segments are retrieved and processed until no more segments are found
[Get EBSBCCM Segment]
Attempting to retrieve EBSBCCM segment with type 'CM' for the current sequence → If segment is found, mark as found for processing, otherwise mark as not found
[Add Lading Quantity to Total]
Processing the commodity segment for weight calculation → Add the L0-LADING-QTY value to the total number of units counter
[Get EBSBCCR Weight Segment]
Processing weight data for the commodity → Retrieve EBSBCCR segment with type 'CR' and dependent key 'CR001' to get weight information
[Extract Total Weight from N7-WEIGHT]
Processing weight data from the segment → Move the N7-WEIGHT value to the commodity weight counter
[Set Weight to Zero]
Processing weight data for the first commodity segment → Set the commodity weight counter to zero
[Check Metric Indicator]
Setting weight unit for the shipment → If metric indicator is 'M' or 'L', set weight unit to KG, otherwise set to LB
[Set Quantity Qualifier from Segment]
Processing the first commodity segment → Move the L0-LADING-QTY-QUAL to the lading quantity qualifier field
[Use Fastway SHIPCOMM Data]
Attempting to get weight and quantity information → Retrieve weight and quantity from SHIPCOMM segments using 'GU' and 'GN' functions, set quantity qualifier to 'PCS', and use metric or standard weight based on metric indicator
[EDI BOL Weight/Quantity Found?]
The system retrieves EDI BOL commodity records and finds valid weight and quantity data → The system uses EDI BOL weight, quantity, and quantity qualifier data for manifest creation
[Check EDI BOL HN Segment Available?]
The system checks for availability of EDI BOL HN segment data → If EDI BOL HN segment is found, use EDI data source, otherwise use Fastway shipper data
[Extract Shipper Name from EDI BOL]
The system processes shipper name information → The shipper name is extracted from F1-CONSIGNOR-NAME field in the EDI BOL data
[Extract Shipper CHOP Code from EDI BOL]
The system processes shipper identification codes → The shipper CHOP code is extracted from F1-SHPR-CHOP field in the EDI BOL data
[Check EDI BOL HA Address Segment?]
The system needs to populate address information → If EDI BOL HA address segment is available, use EDI address data, otherwise use Fastway address data
[Extract Address from EDI BOL HA Segment]
The system processes shipper address information → Address line 1 is extracted from F2-ADDL-NAME-ADDR-1 and address line 2 from F2-ADDL-NAME-ADDR-2
[Use Fastway Shipper Address Data]
The system needs shipper address information → Address information is extracted from Fastway SHPR-ADDR fields
[Check EDI BOL HC City/State Segment?]
The system needs city, state, and postal code information → If EDI BOL HC city/state segment is available, use EDI data, otherwise parse Fastway address data
[Extract City/State/Postal from EDI BOL HC]
The system processes shipper location information → City name is extracted from F4-CITY-NAME, state code from F4-STATE-PROV-CODE, postal code from F4-POSTAL-CODE, and country code from F4-COUNTRY-CODE
[Parse Fastway Address for City/State/Postal]
The system needs to extract location components → The system parses SHPR-ADDR field to extract city name, state/province code, and postal code components
[Check EDI BOL GP Contact Segment?]
The system checks for available contact data sources → If EDI BOL GP contact segment is available, extract contact information, otherwise proceed without contact details
[Extract Contact Information from EDI BOL]
The system processes shipper contact information → Contact function code is extracted from PER-CONTACT-FUNC-CODE, contact name from PER-NAME, communication number qualifier from PER-COMMUN-NO-QUAL, and communication number from PER-COMMUN-NUMBER
[Use Fastway Shipper Data]
The system needs to populate shipper information → The system uses Fastway SHIPROOT data as the primary source for shipper information
[Parse Fastway City/State Information]
The system processes city and state information → The system parses SHPR-ADDR(2) to extract city name, state/province code, and postal code, then determines country code through state lookup
[Search for EDI BOL Consignee Data CN Segment]
The system searches for consignee name data in EDI BOL CN segment type '01' → The system sets the consignee data found flag based on whether the CN segment exists
[Extract Consignee Name and CHOP from EDI]
The system processes the consignee name information → The system sets entity ID to 'CN', extracts shipper name to consignee name field, and sets the consignee CHOP code
[Search for EDI Address Data CA Segment]
The system searches for address data in EDI BOL CA segment for consignee type → The system sets the address data found flag based on whether the CA segment exists
[Use Fastway Address Data]
The system needs address information for the consignee → The system uses consignee address from Fastway data and if blank, sets address line 1 to 'NA' and clears address line 2
[Search for EDI City/State Data CC Segment]
The system searches for city/state data in EDI BOL CC segment for consignee type → The system sets the city/state data found flag based on whether the CC segment exists
[Extract City/State/Postal/Country from EDI]
The system processes the geographic information → The system extracts city name, state/province code, postal code, and country code from the EDI data
[Use Fastway City/State Data]
The system needs geographic information for the consignee → The system parses Fastway consignee address data to extract city, state/province, postal code, and determines country from state lookup table
[Search for EDI Contact Data GP Segment]
The system searches for contact data in EDI BOL GP segment for consignee type → The system sets the contact data found flag based on whether the GP segment exists
[Extract Contact Information from EDI]
The system processes the contact information → The system extracts contact function code, contact name, communication number qualifier, and communication number from the EDI data
[Use Fastway Consignee Data]
The system needs consignee information → The system uses consignee CHOP code, sets entity ID to 'CN', and extracts consignee name from Fastway shipment data
[Build SF Stuffer Entity Segment]
The system processes the stuffer entity segment → The system creates an SF entity record with name, address, city, state, postal code, country, and contact information from the EDI data
[Build UC Ultimate Consignee Segment]
The system processes the ultimate consignee entity segment → The system creates a UC entity record with name, address, city, state, postal code, country, and contact information from the EDI data, defaulting address to 'NA' if not provided
[Build BN Beneficial Owner Segment]
The system processes the beneficial owner entity segment → The system creates a BN entity record with name, consignee chop code, address, city, state, postal code, and country information from the EDI data
[Build C1 Carrier Entity Segment]
The system processes the carrier entity segment from EDI → The system creates a C1 entity record with organization ID, name, address, city, state, postal code, country, and contact information from the EDI transportation data
[Build C1 Carrier Entity Segment]
The system processes the carrier entity segment from Fastway → The system creates a C1 entity record using consignee data from Fastway shipment with name, address, city, state, postal code, and country information
[Build N1 Notify Party Segment]
The system processes the notify party entity segment → The system creates an N1 entity record with organization ID, name, address, city, state, postal code, country, and contact information from the EDI transportation data
[Build PF/SS Entity Segments from MCOA]
The system processes the MCOA entity segment → The system creates a PF or SS entity record with organization ID, name, ID code qualifier, ID code, address, city, state, postal code, and country information from the MCOA data, defaulting address to 'NA' if not provided
[Build Additional Entity Segments]
The system processes each additional entity segment type → The system creates entity records for each found organization type with organization ID, name, address, city, state, postal code, country, and contact information from the EDI transportation data
[Store N1 Segments in Database]
The system stores the entity segment → The system assigns the CCN key, record type 55, current sequence number, and stores the segment data in the database array
[Build SF - Stuffer Entity]
The system processes the PN segment for stuffer information → If PN segment is found, extract stuffer name and create SF entity record with address from PA and PC segments and contact from GP segment
[Build UC - Ultimate Consignee]
The system processes the UN segment for ultimate consignee information → If UN segment is found, extract ultimate consignee name and create UC entity record with address from UA and UC segments and contact from GP segment
[Build BN - Beneficial Owner]
The system processes the BN segment for beneficial owner information → If BN segment is found, extract beneficial owner name and create BN entity record with address from BT and BY segments
[Build C1 - Carrier Entity]
The system processes carrier entity information → If TN segment with C1 is found, extract carrier information with address from T2 and TA segments and contact from T3 segment, otherwise if consignee data code is C, use Fastway consignee data
[Build N1 - Notify Party]
The system processes the TN segment for notify party information → If TN segment with N1 is found, extract notify party information and create N1 entity record
[Build PF/SS - Payment/Service]
The system processes MCOA segment with organization ID PF or SS → If MCOA segment is found with PF or SS organization ID, extract entity information with address from ON and OC segments
[Build Additional Entities]
The system processes TN segments for these entity types → Extract entity information and create corresponding entity records with address and contact details
[Build SF - Stuffer Entity]
Processing stuffer entity segment → Create SF entity record with name, address, city/state/postal, and contact information from EDI data
[Build UC - Ultimate Consignee Entity]
Processing ultimate consignee entity segment → Create UC entity record with name, address, city/state/postal, and contact information from EDI data
[Build BN - Beneficial Owner Entity]
Processing beneficial owner entity segment → Create BN entity record with name, address, city/state/postal information from transportation data
[Build C1 - Carrier Entity]
Processing carrier entity segment → Create C1 entity record with name, address, city/state/postal, and contact information from available data source
[Build N1 - Notify Party Entity]
Processing notify party entity segment → Create N1 entity record with name, address, city/state/postal, and contact information
[Build PF/SS - Payment/Service Entities]
Processing payment/service entity segments → Create entity record with organization ID, name, ID code qualifier, ID code, address, and city/state/postal information
[Build Additional Entities - 11, NN, MC, OO, FW]
Processing additional entity segments → Create corresponding entity records with name, address, city/state/postal, and contact information
[Build IM - Importer Entity]
Processing importer entity segment → Create IM entity record with name, business number, qualifier, address, and contact information, and set CSA indicator appropriately
[EDI BOL Shipper Data Available?]
The system checks for EDI BOL shipper data in HN segment → If EDI BOL shipper data is found, extract shipper name and CHOP code from HN segment, otherwise extract shipper name and CHOP code from Fastway SHIPROOT
[EDI BOL Consignee Data Available?]
The system checks for EDI BOL consignee data in CN segment → If EDI BOL consignee data is found, extract consignee name and CHOP code from CN segment, otherwise extract consignee name and CHOP code from Fastway SHIPROOT
[EDI BOL Address Data Available?]
The system checks for EDI BOL address data in HA/CA segments → If EDI BOL address data is found, extract address lines from HA/CA segments, otherwise extract address from Fastway SHIPROOT address fields and set default 'NA' if address is blank
[EDI BOL City/State Data Available?]
The system checks for EDI BOL city/state data in HC/CC segments → If EDI BOL city/state data is found, extract city, state, postal code and country from HC/CC segments, otherwise parse city, state and postal code from Fastway address field and lookup country code from state-country table
[EDI BOL Contact Data Available?]
The system checks for EDI BOL contact data in GP segment → If EDI BOL contact data is found, extract contact function code, name, communication number qualifier and communication number from GP segment, otherwise set all contact fields to spaces
[EDI BOL Carrier Data Available?]
The system checks for EDI BOL carrier data in TN segment → If EDI BOL carrier data is found, extract organization ID and name from TN segment, otherwise extract entity information from Fastway CONS-DATA fields
[Parse City/State from Fastway Address Field]
State or province code is available → Search the state-country table to find matching country code for the state or province code, and set country code to the found value or spaces if not found
[Retrieve PER Segment from EDI BOL]
The system processes contact information for that entity → Contact function code, person name, communication number qualifier, and communication number are extracted from the PER segment
[Search for EDI BOL Stuffer Segment PN]
The system searches for stuffer segment type 'PN' with sequence '01' → The system retrieves stuffer name and contact information if the segment exists
[Stuffer Segment Found?]
If the search results → Processing continues with stuffer data extraction if segment is found, otherwise stuffer processing is skipped
[Extract Stuffer Name from EDI BOL]
The system processes the stuffer name data → The stuffer name is extracted and assigned to the entity name field
[Search for Stuffer Address Segment PA]
The system searches for address segment type 'PA' with sequence '01' → The system retrieves stuffer address information if the address segment exists
[Address Segment Found?]
If the address search results → Address extraction continues if segment is found, otherwise default address is applied
[Extract Address Lines from EDI BOL]
The system processes the address data → Address line 1 and address line 2 are extracted from the EDI segment
[Search for Stuffer City/State Segment PC]
The system searches for city/state segment type 'PC' with sequence '01' → The system retrieves stuffer geographic information if the segment exists
[City/State Segment Found?]
If the geographic search results → Geographic data extraction continues if segment is found, otherwise contact processing begins
[Extract City, State, Postal, Country from EDI BOL]
The system processes the geographic data → City name, state/province code, postal code and country code are extracted from the EDI segment
[Search for Stuffer Contact Segment GP]
The system searches for contact segment type 'GP' with sequence '01' → The system retrieves stuffer contact information if the segment exists
[Contact Segment Found?]
If the contact search results → Contact data extraction continues if segment is found, otherwise validation processing begins
[Extract Contact Information from EDI BOL]
The system processes the contact data → Contact function code, person name, communication number qualifier and communication number are extracted from the EDI segment
[Search for EDI BOL UN Segment]
The system searches for UN segment type with sequence '01' → The system retrieves the Ultimate Consignee entity data if the segment exists
[Extract UC Entity Data from EDI]
The system processes the Ultimate Consignee data → Entity ID is set to 'UC', entity name is extracted from U1-NAME field, and ID code qualifiers are cleared
[Search for UA Address Segment]
The system searches for corresponding UA address segment with UN type and sequence '01' → The system retrieves address data if the UA segment exists
[Extract Address Lines from EDI]
The system processes the address information → Address line 1 is set from U2-ADDL-NAME-ADDR-1 and address line 2 is set from U2-ADDL-NAME-ADDR-2
[Search for UC City/State Segment]
The system searches for corresponding UC location segment with UN type and sequence '01' → The system retrieves location data if the UC segment exists
[Extract City/State/Postal/Country from EDI]
The system processes the location information → City name is set from U4-CITY-NAME, state/province code from U4-STATE-PROV-CODE, postal code from U4-POSTAL-CODE, and country code from U4-COUNTRY-CODE
[Search for GP Contact Segment]
The system searches for corresponding GP contact segment with UN type and sequence '01' → The system retrieves contact data if the GP segment exists
[Extract Contact Information]
The system processes the contact information → Contact function code is set from PER-CONTACT-FUNC-CODE, contact name from PER-NAME, communication number qualifier from PER-COMMUN-NO-QUAL, and communication number from PER-COMMUN-NUMBER
[Insert UC Record into Database]
The system stores the UC record → The Ultimate Consignee record is inserted into the customs database with sequence numbers 0003-0025
[Set BN Entity ID for Search]
Preparing to search transportation segments → The entity ID is set to 'BN' for beneficial owner identification
[Search Transportation Segments for BN]
Searching transportation segments database → The system retrieves transportation segments matching the beneficial owner entity ID
[BN Transportation Segment Found?]
Evaluating the search results → The system determines whether beneficial owner transportation segment data exists or processing should be skipped
[Search for BN Entity in EDI BOL]
Searching EDI BOL entity segments for beneficial owner data → The system retrieves beneficial owner entity information from EDI BOL segments
[BN Entity Found in EDI BOL?]
Evaluating the EDI BOL search results → The system determines whether to proceed with beneficial owner processing or skip it based on entity existence
[Set BN Entity ID Code]
Processing beneficial owner entity information → The entity ID code 'BN' is assigned to the customs segment
[Extract Beneficial Owner Name]
Processing beneficial owner information → The beneficial owner name is extracted and assigned to the customs segment
[Set Consignee CHOP Code]
Setting up beneficial owner segment data → The consignee CHOP code is assigned to the beneficial owner customs segment
[Search for BN Address Segment]
Searching for beneficial owner address information → The system retrieves address segments matching the beneficial owner entity
[Extract Address Information]
Processing address information → Address line 1 and address line 2 are extracted and assigned to the customs segment
[Search for BN City/State Segment]
Searching for city and state information → The system retrieves city/state segments matching the beneficial owner entity
[Extract City, State, Postal, Country]
Processing city and state information → City name, state/province code, postal code, and country code are extracted and assigned to the customs segment
[Clear City/State Information]
Processing city and state information → City, state, postal code, and country fields are cleared in the customs segment
[Clear Contact Information]
Setting up contact information → All contact function code, name, communication qualifier, and communication number fields are cleared
[Insert BN Record into Customs Database]
Inserting the record into the customs database → The beneficial owner segment record is inserted into the customs database with sequence number between 0003 and 0025
[Skip BN Processing]
Determining processing path → Beneficial owner processing is skipped and the system continues to the next processing step
[Set Entity Type to 'C1']
The entity type needs to be specified → The entity type code is set to 'C1' to identify it as a carrier entity
[Search EDI BOL Transportation Segments]
The system searches for C1 carrier entity information → The system looks up transportation segments with entity type 'C1' in the EDI BOL data
[C1 Entity Found in EDI BOL?]
Evaluating the availability of C1 carrier information → If C1 entity is found in EDI BOL, use EDI data; otherwise check Fastway data source
[Extract Carrier Data from EDI BOL]
Processing carrier information from EDI source → The system extracts carrier name, ID, and related data from the EDI BOL transportation segments
[Get Carrier Name and ID]
Extracting carrier identification information → The carrier name is assigned to entity name field and carrier ID is assigned to entity ID field
[Get Carrier Address from T2 Segment]
Processing carrier address information → The address lines are extracted from T2 segment and assigned to carrier address fields
[Get Carrier City/State from TA Segment]
Processing carrier location information → The city name, state code, postal code, and country code are extracted from TA segment
[Get Carrier Contact from T3 Segment]
Processing carrier contact information → The contact function code, contact name, communication qualifier, and communication number are extracted from T3 segment
[Carrier Data Available in Fastway?]
Evaluating alternative data sources for carrier information → If consignee data field 2 contains carrier information, use Fastway data; otherwise end C1 processing
[Parse City/State/Postal from Consignee Field 4]
Processing carrier location information from Fastway source → The city name, state code, and postal code are parsed from consignee data field 4 and assigned to respective location fields
[Insert C1 Entity into Customs Record]
Adding the carrier entity to the customs record → The C1 entity segment is inserted into the customs record with the appropriate sequence number between 0003 and 0025
[Set Entity ID to 'N1']
Processing notify party entity information → The entity ID code is set to 'N1' to identify this as a notify party record
[Search EDI BOL for Transportation Segments]
Searching for notify party transportation segments → The system iterates through transportation segments starting from sequence 1 until found or maximum sequences reached
[Extract Organization ID from Segment]
Processing the segment data → The organization ID is extracted from the D5-ORG-ID field
[Organization ID Matches 'N1'?]
Validating entity type for notify party processing → If organization ID equals 'N1', continue with notify party processing; otherwise search next segment
[Extract Entity Name]
Processing notify party entity information → The entity name is extracted from D5-NAME field and stored in the N1 segment
[Clear ID Code Qualifier and ID Code]
Setting up notify party N1 segment fields → ID code qualifier and ID code fields are set to spaces
[Get Address Information from T2 Segment]
Looking for address details → System searches for T2 segment with matching sequence number
[Extract Address Line 1 and 2]
Processing address information → Address line 1 and address line 2 are extracted from D6-ADDL-NAME-ADDR-1 and D6-ADDL-NAME-ADDR-2 fields
[Get City/State Information from TA Segment]
Looking for geographic location details → System searches for TA segment with matching sequence number
[Extract City, State, Postal Code, Country]
Processing geographic information → City, state, postal code, and country are extracted from D7 fields and stored in N4 segment data
[Get Contact Information from T3 Segment]
Looking for contact person details → System searches for T3 segment with matching sequence number
[Extract Contact Function, Name, Phone Qualifier, Phone Number]
Processing contact information → Contact function, name, phone qualifier, and phone number are extracted from PER fields and stored in PER segment data
[Insert N1 Record into Customs Database]
Storing notify party information in customs database → The N1 record is inserted into the customs database with sequence number between 0003-0025
[Skip - No N1 Entity Found]
No segments with organization ID 'N1' are found → Notify party processing is skipped and control returns to main processing
[Retrieve MCOA Segment by Sequence Number]
The system attempts to retrieve MCOA segment data → The system calls EBCLGIO to fetch EBSMCOA segment with type 'OT' using the sequence number
[Entity Type is PF or SS?]
The system checks the organization ID in the segment → If F5-ORG-ID equals 'PF' or 'SS', continue processing, otherwise skip to next sequence
[Extract Entity Information]
The system processes the entity information → Extract organization ID, name, ID code qualifier, and ID code from F5 fields
[Set Entity ID Code]
The system populates the N1 segment → Move F5-ORG-ID to GCCS-N101-ENTITY-ID-CDE
[Set Entity Name]
The system populates the N1 segment → Move F5-NAME to GCCS-N102-NAME
[Set ID Code Qualifier]
The system populates the N1 segment → Move F5-ID-CODE-QUAL to GCCS-N103-ID-CDE-QUAL
[Set ID Code]
The system populates the N1 segment → Move F5-ID-CODE to GCCS-N104-ID-CDE
[Extract Entity Information]
The system sets up the N1 segment → Move spaces to GCCS-SC301-CHOP-CDE
[Retrieve Address Information]
The system needs address information → Call EBCLGIO to retrieve EBSMCOA segment with type 'ON' using the same sequence number
[Extract Address Line 1, Extract Address Line 2]
The system processes address information → Move F6-ADDL-NAME-ADDR-1 to GCCS-N301-ADDRESS-INFO-1 and F6-ADDL-NAME-ADDR-2 to GCCS-N302-ADDRESS-INFO-2
[Retrieve City/State Information]
The system needs city and state information → Call EBCLGIO to retrieve EBSMCOA segment with type 'OC' using the same sequence number
[Extract City Name, Extract State/Province Code, Extract Postal Code, Extract Country Code]
The system processes geographic information → Move F7-CITY-NAME to GCCS-N401-CITY-NAME, F7-STATE-PROV-CODE to GCCS-N402-STATE-PROV-CDE, F7-POSTAL-CODE to GCCS-N403-POSTAL-CDE, and F7-COUNTRY-CODE to GCCS-N404-COUNTRY-CDE
[Insert N1 Segment into Database]
The system stores the segment data → Execute Z950-ISRT-GCSCCS55-0003-0025 to insert the segment into GCSCCS55 database with sequence numbers 0003-0025
[Increment Sequence Counter]
The system continues the processing loop → Increment WS-MCOA-SEQ-NBR and continue until SW-EBSMCOA-NOT-FOUND is true
[Build 11 Entity Segment]
The system searches for EDI BOL TN segment with entity type 11 → If found, the system processes the entity data and creates a record 55 segment, otherwise skips to next entity type
[Build NN Entity Segments]
The system searches for EDI BOL NN segments incrementally by sequence number → The system continues processing each found NN segment until no more segments exist
[Process NN Entity Data from EDI]
The system processes the NN entity data → The system extracts entity name, consignee chop code, and builds address and contact information for the customs record
[Get NN Address Information]
The system searches for corresponding address segments (GC type) → If address segments are found, the system extracts address lines; if not found or address line 1 is empty, sets default 'NA' value
[Get NN City/State Information]
The system searches for corresponding geographic segments (GA type) → If geographic segments are found, the system extracts city, state, postal code, and country; if not found, clears all geographic data fields
[Build MC Entity Segment]
The system searches for EDI BOL TN segment with entity type MC → If found, the system processes the MC entity data and creates a record 55 segment, otherwise continues to next entity type
[Build OO Entity Segment]
The system searches for EDI BOL TN segment with entity type OO → If found, the system processes the OO entity data and creates a record 55 segment, otherwise continues to next entity type
[Build FW Entity Segment]
The system searches for EDI BOL TN segment with entity type FW → If found, the system processes the FW entity data and creates a record 55 segment, completing additional entity processing
[Check if Corrector EDI with Existing Importer Data]
The system checks if importer name, business number, and business number qualifier are all present → The system should identify if existing importer data exists and set appropriate processing flags
[Insert New Record]
The system performs an insert operation → Validate the N1 segment and insert the new record into the sequence position array
[Add New Record Normally]
The system stores the importer record → The system validates the N1 segment AND performs the standard insert operation for the new record
[Set Hazmat Search Sequence to 1]
Beginning hazmat segment search → Hazmat search sequence counter is set to 1
[Get EDI BOL Hazmat Segment EBSBCCM-CH]
System attempts to retrieve hazmat segment EBSBCCM with type 'CH' for current sequence → EDI BOL hazmat segment is retrieved if it exists for the specified sequence
[Hazmat Segment Found?]
Checking the retrieval status → If segment exists, continue processing; if not found, end hazmat extraction with no UN number found
[Get Hazmat Info Segment EBSBCHI]
System attempts to retrieve hazmat info segment EBSBCHI with type 'HS' → Detailed hazmat information segment is retrieved if it exists
[Hazmat Info Found?]
Checking retrieval status for detailed hazmat data → If info segment exists, extract proper shipping name; otherwise complete extraction process
[Extract Proper Shipping Name from LH3-PROPER-SHIP-NAME]
Extracting proper shipping name for commodity classification → Proper shipping name is extracted from LH3-PROPER-SHIP-NAME field
[Increment Hazmat Search Sequence]
Continuing search for valid hazmat data → Hazmat search sequence counter is incremented by 1
[More Sequences to Check?]
Determining if additional hazmat segments should be searched → If sequence is 98 or less, continue searching; otherwise end with no UN number found
[Get SHIPCOMM Data]
The system needs to process hazmat information from Fastway data → The system retrieves SHIPCOMM segment data using the shipment root key
[Get SHIPERP Data]
The system processes hazmat information from Fastway data → The system retrieves SHIPERP segment using shipment root key and commodity ID
[Get SHIPERPD Data]
The system needs detailed hazmat description information → The system retrieves SHIPERPD segment using shipment root key, commodity ID, and emergency response STCC code
[Lookup Country from State/Province]
Country code is empty → Look up and assign the corresponding country code from the state-country lookup table
[N4 Address Data Present?]
The N4 address data segment is empty or not present → The system should skip all address validation steps and complete the validation process
[Get State/Province Code]
The system processes the N402 state/province code field → The state/province code is extracted and prepared for country validation lookup
[Clear Working Variables]
The error processing is complete → The working message variable and working error message number variable should be cleared to spaces to prepare for the next error processing cycle
[Table Access Successful?]
The table access returns successfully → The system should move the table segment to the message structure, extract the English text from the message table, and move the English text to the message label field
[Table Access Successful?]
The table access fails or returns no data → The system should clear the message structure by setting it to spaces
[Set Segment Type and Function Code]
The system determines the segment type (EBSNRSC, EBSNRSA, EBSNRTD, EBSMCOA, or EBSBCKS) → The segment type is set in the I/O work area and the function code is set to 'GU' (Get Unique) for database retrieval
[Set Root Key from EDI BOL Key]
The system prepares to access EDI BOL segments → The EDI BOL key for record 55 is moved to the root key field in the I/O work area
[Set Entity Type and Sequence Numbers]
The system configures segment access parameters → The entity type code (HN, HA, HC, GP, CN, CA, CC, PN, PA, PC, UN, UA, UC, BN, BT, BY, TN, T2, T3, TA, NN, GC, GA, OT, ON, OC, SH, CH, HS, CM, CR) is set in TYPE-1 field, sequence numbers are set to appropriate values (typically '01'), and the operator is set to '=' for exact match
[Call EDI BOL I/O Service]
The system needs to retrieve EDI BOL segment data → The EBCLGIO service is called with the communication control block, I/O work area, and target segment data area
[Segment Found?]
The system checks the result of the segment retrieval → If the database status code is spaces, the segment was found successfully; otherwise, the segment was not found
[Load Segment Data]
The segment data needs to be made available for processing → The segment found flag is set to TRUE and the retrieved data remains in the segment data area for further processing
[Clear Segment Data]
The system needs to handle the unsuccessful retrieval → The target segment data area is cleared to spaces and the segment not found flag is set to TRUE
[Return Success Status]
The segment retrieval operation completes → The segment found status flag is set to indicate successful retrieval
[Return Not Found Status]
The segment retrieval operation completes → The segment not found status flag is set to indicate unsuccessful retrieval
[HN - Shipper Name Segment]
The system needs to retrieve shipper name details for customs processing → The HN segment is accessed from EBSNRSC data source with entity type 'HN' and sequence '01', containing shipper name and identification codes
[HA - Shipper Address Segment]
The system needs to retrieve shipper address details for customs processing → The HA segment is accessed from EBSNRSA data source with entity type 'HA' and sequence '01', containing shipper street address lines
[HC - Shipper City/State Segment]
The system needs to retrieve shipper city, state, postal code, and country details for customs processing → The HC segment is accessed from EBSNRSA data source with entity type 'HC' and sequence '01', containing shipper city, state, postal code, and country code
[GP - Contact Person Segment]
The system needs to retrieve contact details for customs processing → The GP segment is accessed from EBSNRSA data source with entity type 'GP' and sequence '01', containing contact function code, name, communication number qualifier, and communication number
[CN - Consignee Name Segment]
The system needs to retrieve consignee name details for customs processing → The CN segment is accessed from EBSNRSC data source with entity type 'CN' and sequence '01', containing consignee name and identification codes
[CA - Consignee Address Segment]
The system needs to retrieve consignee address details for customs processing → The CA segment is accessed from EBSNRSA data source with entity type 'CA' and sequence '01', containing consignee street address lines
[CC - Consignee City/State Segment]
The system needs to retrieve consignee city, state, postal code, and country details for customs processing → The CC segment is accessed from EBSNRSA data source with entity type 'CC' and sequence '01', containing consignee city, state, postal code, and country code
[PN - Stuffer Name Segment]
The system needs to retrieve stuffer name details for customs processing → The PN segment is accessed from EBSNRSC data source with entity type 'PN' and sequence '01', containing stuffer name and identification codes
[UN - Ultimate Consignee Name Segment]
The system needs to retrieve ultimate consignee name details for customs processing → The UN segment is accessed from EBSNRSC data source with entity type 'UN' and sequence '01', containing ultimate consignee name and identification codes
[BN - Beneficial Owner Name Segment]
The system needs to retrieve beneficial owner name details for customs processing → The BN segment is accessed from EBSNRSC data source with entity type 'BN' and sequence '01', containing beneficial owner name and identification codes
[TN - Transportation Name Segment]
The system needs to retrieve transportation entity name details for customs processing → The TN segment is accessed from EBSNRTD data source with varying sequence numbers until the desired organization ID is found, containing transportation entity name and organization ID
[NN - Additional Entity Name Segment]
The system needs to retrieve additional entity name details for customs processing → The NN segment is accessed from EBSNRSC data source with varying sequence numbers, containing entity name and identification codes for various entity types
[Retrieve TN Segment by Sequence Number]
The system retrieves a TN segment from EBSNRTD using the current sequence number → The transportation segment data is loaded if found, otherwise segment not found status is returned
[TN Segment Found?]
The system checks the retrieval status → If segment is found, continue with organization ID matching, otherwise set TN segment not found flag
[Set D5-ORG-ID Found Flag]
The system processes the successful match → The D5-ORG-ID found flag is set to true to indicate successful search completion
[Increment Sequence Counter]
The system prepares for the next search iteration → The sequence counter is incremented by 1 to retrieve the next transportation segment
[Continue Search?]
If search continuation criteria → If target organization ID not found and more segments may exist, continue search loop, otherwise terminate search
[Set TN Segment Not Found Flag]
The system terminates the search process → The TN segment found flag is set to false to indicate search termination
[Adjust Final Sequence Counter]
The system finalizes the search results → The sequence counter is decremented by 1 to reflect the actual last processed sequence number
[Search for BN Entity in Transportation Data]
The system searches for BN entity in transportation data segments with organization ID 'BN' → If BN entity is found, initialize BN segment record and proceed with BN processing, otherwise skip BN processing entirely
[Extract Entity Name]
The system processes the BN entity data → Set entity ID code to 'BN', extract entity name from transportation data, extract consignee CHOP code, and clear identification code fields
[Extract City Name]
The system searches for BY geographic segments and finds geographic data → Extract city name, state/province code, postal code, and country code from BY segments
[Insert BN Record into Database]
The system completes BN segment data processing → Validate the N1 segment data and insert the BN record into the customs database with sequence numbers between 0003 and 0025
[Get MCOA Segment by Sequence]
The system attempts to retrieve the MCOA segment → The system calls the EDI BOL interface to get the MCOA segment data for the specified sequence number
[MCOA Segment Found?]
The system checks the retrieval result → If no MCOA segment is found, processing moves to check for more segments, otherwise processing continues with the found segment
[Entity Type is PF or SS?]
The system checks the entity type in the segment → If the entity type is PF or SS, the segment is processed for customs data creation, otherwise the segment is skipped
[Extract Entity Information]
The system extracts entity information → The entity ID code, entity name, ID code qualifier, and ID code are extracted from the MCOA segment
[Set Entity ID Code]
The system creates the customs record → The entity ID code from the MCOA segment is assigned to the N101 entity ID code field in the customs record
[Set Entity Name]
The system creates the customs record → The entity name from the MCOA segment is assigned to the N102 name field in the customs record
[Set ID Code Qualifier]
The system creates the customs record → The ID code qualifier from the MCOA segment is assigned to the N103 ID code qualifier field in the customs record
[Set ID Code]
The system creates the customs record → The ID code from the MCOA segment is assigned to the N104 ID code field in the customs record
[Get MCOA Address Segment]
The system attempts to get address information → The system calls the EDI BOL interface to retrieve the ON type segment for the current MCOA sequence
[Address Segment Found?]
The system checks if address data was found → If address data is found, extract address lines 1 and 2, otherwise set default address as 'NA'
[Extract Address Line 1]
The system processes the address information → The first additional name/address field is extracted and assigned to the N301 address info field
[Extract Address Line 2]
The system processes the address information → The second additional name/address field is extracted and assigned to the N302 address info field
[Get MCOA City/State Segment]
The system attempts to get city and state information → The system calls the EDI BOL interface to retrieve the OC type segment for the current MCOA sequence
[City/State Segment Found?]
The system checks if city/state data was found → If city/state data is found, extract all location fields, otherwise clear all address fields
[Extract City Name]
The system processes the location information → The city name field is extracted and assigned to the N401 city name field
[Extract State/Province Code]
The system processes the location information → The state/province code field is extracted and assigned to the N402 state/province code field
[Extract Postal Code]
The system processes the location information → The postal code field is extracted and assigned to the N403 postal code field
[Extract Country Code]
The system processes the location information → The country code field is extracted and assigned to the N404 country code field
[Insert Record into Customs Database]
The system inserts the record → The record is inserted into the customs database with the appropriate sequence number and record type 55
[Increment Sequence Counter]
The system completes processing the current segment → The MCOA sequence counter is incremented by 1 to move to the next segment
[More MCOA Segments?]
The system checks for more segments to process → If more MCOA segments are found, processing continues with the next segment, otherwise MCOA processing ends
[Get EBSNRSA Geographic Code Segment - GC]
The system attempts to retrieve the EBSNRSA geographic code segment with type 'GC' → The geographic code segment data is retrieved if found, otherwise processing continues without GC data
[Extract Address Information from GC Segment]
The system processes the address information from the GC segment → Address line 1 is moved to N301 field and address line 2 is moved to N302 field
[Get EBSNRSA Geographic Address Segment - GA]
The system attempts to retrieve the EBSNRSA geographic address segment with type 'GA' → The geographic address segment data is retrieved if found, otherwise geographic data fields are set to spaces
[Extract Geographic Address Data]
The system processes the geographic address information from the GA segment → City name is moved to N401, state/province code to N402, postal code to N403, and country code to N404
[Build Shipper Record - Sequence 0001]
The system builds the shipper record and EDI BOL shipper data (EBSNRSC-HN) is found → The system creates entity ID 'SH', extracts shipper name and CHOP code from EDI data, gets address from EBSNRSA-HA segment, gets city/state/postal/country from EBSNRSA-HC segment, and gets contact information from EBSNRSA-GP segment
[Build Shipper Record - Sequence 0001]
The system builds the shipper record and EDI BOL shipper data is not found → The system creates entity ID 'SH', uses shipper name and CHOP from SHIPROOT, uses shipper address from SHIPROOT, and derives city/state/postal/country from SHIPROOT address data
[Build Consignee Record - Sequence 0002]
The system builds the consignee record and EDI BOL consignee data (EBSNRSC-CN) is found → The system creates entity ID 'CN', extracts consignee name and CHOP code from EDI data, gets address from EBSNRSA-CA segment, gets city/state/postal/country from EBSNRSA-CC segment, and gets contact information from EBSNRSA-GP segment
[Build Consignee Record - Sequence 0002]
The system builds the consignee record and EDI BOL consignee data is not found → The system creates entity ID 'CN', uses consignee name and CHOP from SHIPROOT, uses consignee address from SHIPROOT, and derives city/state/postal/country from SHIPROOT address data
[Build Stuffer Entity SF]
The system finds EDI BOL stuffer data (EBSNRSC-PN) → The system creates entity ID 'SF', extracts stuffer name from EDI data, gets address from EBSNRSA-PA segment, gets city/state/postal/country from EBSNRSA-PC segment, gets contact information from EBSNRSA-GP segment, and inserts the record into customs database
[Build Ultimate Consignee Entity UC]
The system finds EDI BOL ultimate consignee data (EBSNRSC-UN) → The system creates entity ID 'UC', extracts ultimate consignee name from EDI data, gets address from EBSNRSA-UA segment or sets default 'NA', gets city/state/postal/country from EBSNRSA-UC segment or sets to spaces, gets contact information from EBSNRSA-GP segment, and inserts the record into customs database
[Build Beneficial Owner Entity BN]
The system finds EDI BOL beneficial owner data (EBSNRSC-BN) and organization ID is 'BN' → The system creates entity ID 'BN', extracts beneficial owner name and CHOP from EDI data, gets address from EBSNRSA-BT segment or sets default 'NA', gets city/state/postal/country from EBSNRSA-BY segment or sets to spaces, and inserts the record into customs database
[Build Carrier Entity C1]
The system finds EDI BOL carrier data with organization ID 'C1' or Fastway consignee data code 'C' → The system creates entity ID 'C1', extracts carrier name from EDI or Fastway data, gets address information from appropriate segments, gets city/state/postal/country information, gets contact information, and inserts the record into customs database
[Build Notify Party Entity N1]
The system finds EDI BOL data with organization ID 'N1' → The system creates entity ID 'N1', extracts notify party name from EDI data, gets address information from T2 segment, gets city/state/postal/country from TA segment, gets contact information from T3 segment, and inserts the record into customs database
[Build Payment/Service Entity PF/SS]
The system finds EDI BOL MCOA data with organization ID 'PF' or 'SS' → The system creates entity ID matching the organization ID, extracts entity name and ID codes from MCOA data, gets address from ON segment or sets default 'NA', gets city/state/postal/country from OC segment or sets to spaces, and inserts the record into customs database
[Build Other Entity Types 11/NN/MC/OO/FW]
The system finds EDI BOL data with organization IDs '11', 'NN', 'MC', 'OO', or 'FW' → The system creates entity records with matching entity IDs, extracts entity names and details from appropriate EDI segments, gets address and contact information from corresponding segments, validates entity ID values for sequences greater than 2, and inserts valid records into customs database
[Build Importer Entity IM]
The system finds EDI BOL importer data with entity ID 'IM' and existing importer data is available from initialization → The system retains the existing importer data including CHOP code, name, business number qualifier, business number, CSA indicator, address, city, state, postal code, country, and contact information, and inserts the record into customs database
[Build Importer Entity IM]
The system finds EDI BOL importer data with entity ID 'IM' and no existing importer data is available → The system creates entity ID 'IM', extracts importer name and business information from EDI data, gets address from N3 segment or sets default 'NA', gets city/state/postal/country from N4 segment, sets contact information to spaces, and inserts the record into customs database
[Finalize Importer Processing]
The system finalizes importer processing and no importer record was created from EDI data and sequence index is within maximum limit → The system creates entity ID 'IM', uses importer name and business number from AU table, sets business number qualifier to 'M5', sets address to 'NA', clears city/state/postal/country and contact information, sets CSA indicator on, and either replaces existing record or inserts new record based on availability
[EDI BOL Shipper Data Available?]
The system checks for EDI BOL shipper data availability → If HN segment is found in EDI BOL, use EDI data; otherwise use Fastway data
[Extract Shipper Name from EDI BOL]
The system extracts shipper information from EDI BOL → Entity ID is set to 'SH', shipper name is extracted from F1-CONSIGNOR-NAME, and CHOP code is extracted from F1-SHPR-CHOP
[Use Fastway Shipper Data]
The system needs shipper information → Entity ID is set to 'SH', shipper name is extracted from SHPR-NM, and CHOP code is extracted from SHPR-CHOP
[EDI BOL Address Available?]
The system checks for EDI BOL address data → If HA segment is found, extract address from EDI BOL; otherwise use Fastway address data
[Extract Address from EDI BOL]
The system extracts address information → Address line 1 is set from F2-ADDL-NAME-ADDR-1 and address line 2 is set from F2-ADDL-NAME-ADDR-2
[Use Fastway Address Data]
The system needs address information → Address line 1 is set from SHPR-ADDR(1) and address line 2 is cleared
[EDI BOL City/State Available?]
The system checks for EDI BOL city/state data → If HC segment is found, extract city/state from EDI BOL; otherwise parse from Fastway data
[Extract City/State from EDI BOL]
The system extracts location information → City is set from F4-CITY-NAME, state from F4-STATE-PROV-CODE, postal code from F4-POSTAL-CODE, and country from F4-COUNTRY-CODE
[Parse City/State from Fastway Data]
The system needs location information → Address line 2 is parsed to extract city name, state/province code, and postal code
[EDI BOL Contact Available?]
The system checks for EDI BOL contact data → If GP segment is found, extract contact information; otherwise skip contact processing
[Extract Contact Information]
The system extracts contact information → Contact function code, name, communication number qualifier, and communication number are extracted from the GP segment
[EDI BOL Consignee Data Available?]
The system checks for EDI BOL consignee data availability → If CN segment is found in EDI BOL, use EDI data; otherwise use Fastway data
[Extract Consignee Name from EDI BOL]
The system extracts consignee information from EDI BOL → Entity ID is set to 'CN', consignee name is extracted from D1-SHIPPER-NAME, and CHOP code is extracted from D1-CONS-CHOP
[Use Fastway Consignee Data]
The system needs consignee information → Entity ID is set to 'CN', consignee name is extracted from CONS-DATA(1), and CHOP code is extracted from CONS-CHOP
[EDI BOL Shipper Data Available?]
The system checks for EDI BOL shipper data availability → The system identifies if EDI BOL contains shipper name and contact information
[Extract Shipper Name from EDI BOL]
The system processes the shipper information → Shipper entity ID is set to 'SH', shipper name is extracted from consignor name field, and shipper CHOP code is extracted from EDI BOL
[Use Fastway Shipper Data]
The system needs shipper information for customs processing → Shipper CHOP code and name are extracted from SHIPROOT Fastway data with entity ID set to 'SH'
[EDI BOL Address Available?]
The system checks for address data availability → The system identifies if EDI BOL contains shipper address information
[Extract Address from EDI BOL]
The system processes address information → Address line 1 and address line 2 are extracted from EDI BOL additional name/address fields
[Use Fastway Address Data]
The system needs address information → Address information is extracted from SHIPROOT shipper address fields
[EDI BOL City/State Available?]
The system checks for city and state data availability → The system identifies if EDI BOL contains city, state, postal code, and country information
[Extract City/State/Postal from EDI BOL]
The system processes geographic information → City name, state/province code, postal code, and country code are extracted from EDI BOL geographic fields
[Parse Fastway Address String]
The system processes the Fastway address string → City name, state/province code, and postal code are parsed from the Fastway address string format
[EDI BOL Contact Info Available?]
The system checks for contact data availability → The system identifies if EDI BOL contains contact function code, name, and communication details
[Extract Contact Details from EDI BOL]
The system processes contact details → Contact function code, contact name, communication number qualifier, and communication number are extracted from EDI BOL
[EDI BOL Consignee Data Available?]
The system checks for EDI BOL consignee data availability → The system identifies if EDI BOL contains consignee name and contact information
[Extract Consignee Name from EDI BOL]
The system processes the consignee information → Consignee entity ID is set to 'CN', consignee name is extracted from shipper name field, and consignee CHOP code is extracted from EDI BOL
[Use Fastway Consignee Data]
The system needs consignee information for customs processing → Consignee CHOP code and name are extracted from SHIPROOT consignee data with entity ID set to 'CN'
[Parse Fastway Address String into Components - Extract city, state, and postal code from concatenated address field]
The system processes shipper address information for customs manifest creation → The concatenated address string is parsed into separate city name, state/province code, and postal code components and moved to the corresponding N4 segment fields
[Parse Fastway Address String into Components - Extract city, state, and postal code from concatenated address field]
The system processes consignee address information for customs manifest creation → The concatenated address string is parsed into separate city name, state/province code, and postal code components and moved to the corresponding N4 segment fields
[Parse Fastway Address String into Components - Extract city, state, and postal code from concatenated address field]
The system processes notify party address information for customs manifest creation → The concatenated address string is parsed into separate city name, state/province code, and postal code components and moved to the corresponding N4 segment fields
[Move Parsed Components to Output Fields]
The system needs to determine the corresponding country for customs purposes → The system searches the TB-STATE-COUNTRY table using the state/province code as key and assigns the matching country code to WS-COUNTRY, then moves it to GCCS-N404-COUNTRY-CDE
[Store Parsed Postal Code]
The postal code storage process is executed → The processed postal code is stored in the target postal code field
[Build SF - Stuffer Entity]
Building SF entity record and SF entity is found in EDI data → Extract SF entity name, set entity ID to 'SF', clear ID code qualifier and ID code, and retrieve address information from EDI segments
[Build UC - Ultimate Consignee Entity]
Building UC entity record and UC entity is found in EDI data → Extract UC entity name, set entity ID to 'UC', clear ID code qualifier and ID code, and retrieve address information from EDI segments
[Build BN - Beneficial Owner Entity]
Building BN entity record and BN entity is found in EDI data → Extract BN entity name, set entity ID to 'BN', clear ID code qualifier and ID code, set consignee chop code, and retrieve address information from EDI segments
[Build C1 - Carrier Entity]
Building C1 entity record and C1 entity is found in EDI transportation data → Extract C1 organization ID, name, and address information from EDI transportation segments
[Use Fastway Carrier Data]
Building C1 entity record and consignee data code equals 'C' → Extract carrier information from FastWay consignee data and build C1 entity record with name and address
[Build N1 - Notify Party Entity]
Building N1 entity record and N1 entity is found in EDI transportation data → Extract N1 organization ID, name, and address information from EDI transportation segments
[Build PF/SS - Payment/Service Entities]
Building PF/SS entity records and MCOA segments are found with organization ID of 'PF' or 'SS' → Extract entity ID, name, ID code qualifier, ID code, and address information from MCOA segments
[Build Additional Entities - 11, NN, MC, OO, FW]
Building additional entity records and entities with IDs '11', 'NN', 'MC', 'OO', or 'FW' are found → Extract organization ID, name, and address information for each additional entity type from EDI transportation segments
[Backup Original Importer Data]
The system detects existing importer data in temporary variables → The system backs up all original importer details including name, business number, qualifier, address, city, province, postal code, country, and contact information to temporary storage variables
[Process EDI BOL Importer Data]
The system processes the importer segment data → The system extracts importer name, sets it as the customs importer, extracts business number qualifier and business number, sets importer found flag to true, and creates customs record with all importer details including address and contact information
[Corrector EDI Deletes Importer?]
If whether to restore backed up importer data → If backed up importer data exists and current processing found no importer data, the system restores the backed up importer information; otherwise it clears the importer data
[Restore Backed Up Importer Data]
The system restores importer information → The system restores all backed up importer details including chop code, entity ID, name, business number qualifier, business number, CSA indicator, address lines, city, province, postal code, country, and contact information from temporary storage
[Both AU and EDI Importer Found?]
If CSA indicator settings for dual importer sources → If EDI business number qualifier is 'BN' or spaces, the system turns off CSA indicator to prevent conflicts; otherwise CSA indicator remains as set by the respective data source
[Create Final Importer Record]
The system creates the final importer record → The system validates all importer segment data, creates customs record type 55 with entity ID 'IM', includes all importer details, and prepares the record for insertion into customs database
[Check for Existing Importer Data from Corrector EDI]
The system checks for existing importer data from corrector EDI transactions → The system identifies whether backup importer data exists and sets the appropriate processing flag
[Backup Original Importer Data]
The system processes importer segment building → The system backs up all importer details including name, business number qualifier, business number, CSA indicator, address, city, province, postal code, country, and contact information
[Retrieve Importer N1 Segment from EDI BOL]
The system retrieves importer N1 segment data using entity type 'IM' → The system obtains importer entity information from the EDI BOL database or returns empty if not found
[Process New Importer N1 Segment]
The system processes the importer N1 segment with entity ID code equal to 'IM' → The system extracts importer name to customs importer field, moves ID code qualifier to business number qualifier, moves ID code to business number, and sets importer found flag to true
[Set CSA Indicator Management]
The system processes CSA indicator management → The system turns off the CSA indicator
[Process City, State, Postal, Country]
The system processes city and state information → The system copies city name, state/province code, postal code, and country code from the N4 segment
[Process City, State, Postal, Country]
The system processes city and state information → The system clears all N4 data fields including city, state, postal code, and country
[Clear Contact Information]
The system processes contact information → The system clears all contact data fields including contact function code, name, communication number qualifier, and communication number
[Restore Backed Up Importer Data]
The system processes importer data restoration → The system restores all backed up importer details including consignee chop code, entity ID code, importer name, business number qualifier, business number, CSA indicator, address lines, city, province, postal code, country, and contact information, and sets importer found flag to true
[Handle Importer Data Deletion]
The system handles importer data deletion → The system restores backed up importer data and manages CSA indicator, otherwise clears importer name if no importer segment found
[Clear Importer Fields]
The system processes importer field clearing → The system clears the importer name field and entity ID code
[Get Importer N1 Segment from EDI BOL]
The system searches for importer N1 segment data in the EDI BOL → The system retrieves the importer entity information if available
[Is Corrector EDI with Backup Data?]
If this is a corrector EDI transaction with existing backup data → The system chooses to restore backup data if corrector EDI with backup exists, otherwise processes new importer data
[Restore Backup Importer Data]
The system needs to preserve original importer information → The system restores all backup importer data including name, business number, qualifier, address, city, state, postal code, country, and contact information
[Extract Importer Business Information]
The system processes the importer entity information → The system assigns importer name to customs importer field, business number qualifier to customs business number qualifier field, and business number to customs business number field
[Process Address Information]
The system processes the address information → The system assigns address line 1 and address line 2 to customs manifest fields, setting address line 1 to 'NA' if it is spaces or low values
[Process City/State/Postal Information]
The system processes the geographic information → The system assigns city name, state/province code, postal code, and country code to customs manifest fields
[Reset CSA Indicator if AU and EDI Both Found]
The business number qualifier is 'BN' or spaces → The system turns off the CSA indicator
[Corrector EDI Deleting Importer?]
If this represents an importer deletion in a corrector EDI → The system checks for backup data to restore or clears importer information if no backup exists
[Restore Backup and Mark as Found]
The system processes a corrector EDI transaction → The system restores the backup importer data and marks importer as found
[Clear Importer Information]
The system processes the importer information → The system clears the importer field from customs manifest
[Check if Corrector EDI with Existing Importer Data]
The system checks for existing importer data in temporary variables → If temporary importer name contains data, the system identifies this as corrector EDI processing with existing data, otherwise it proceeds as new processing
[Backup Original Importer Data to Temporary Variables]
The system needs to preserve original importer information → All importer details including CHOP code, name, qualifier, business number, CSA indicator, address, city, province, postal code, country, and contact information are copied to temporary storage variables
[Process New Importer Data from EDI BOL]
EDI BOL importer segment is accessed using the EDI BOL key → If the EDI segment is found and contains entity ID 'IM', the importer data is processed, otherwise the system prepares to use backup data
[Create Importer Record from EDI Data]
The system creates the importer customs record → The importer name is stored in customs database, business number qualifier and business number are captured, importer found flag is set, and CSA indicator status is determined based on business number qualifier
[Restore Original Importer Data from Backup Variables]
The system needs to restore original importer information → All importer details including CHOP code, entity ID, name, business qualifiers, CSA indicator, address, city, province, postal code, country, and contact information are restored from temporary variables to the customs record
[Build Final Importer Database Record]
The system creates the final importer database record → A complete customs record type 55 is built with all importer information, validated segments, and proper sequence numbering for database storage
[Check if Corrector EDI has Importer Data?]
The system checks for importer data presence in the EDI → If importer, business number, and business number qualifier are all present, proceed to search existing records, otherwise continue with normal processing
[Search Existing Importer Records]
The system searches through sequence numbers 3 to 24 for existing importer records → Continue searching until an importer is found or sequence exceeds 24
[Clear Current Importer Fields]
The system needs to clear current importer fields for corrector EDI processing → Set importer, business number, and business number qualifier fields to spaces in the current processing area
[Corrector EDI Deletes Importer?]
The system checks if the corrector EDI has deleted importer information → If backed up importer name exists and no new importer data is found in sequence 55, proceed to restore backed up data, otherwise continue normal processing
[Set Importer CHOP from Backup]
The system restores importer information from backup → Set the CHOP code in both the customs record and current processing fields from the backed up value
[Set Importer Name from Backup]
The system restores importer information from backup → Set the importer name in both the customs record and current processing fields from the backed up value
[Set Business Qualifier from Backup]
The system restores importer information from backup → Set the business number qualifier in both the customs record and current processing fields from the backed up value
[Set Business Number from Backup]
The system restores importer information from backup → Set the business number in both the customs record and current processing fields from the backed up value
[Set CSA Indicator from Backup]
The system restores importer information from backup → Set the CSA indicator in the current processing fields from the backed up value
[Set Address from Backup]
The system restores importer information from backup → Set both address line 1 and address line 2 in the customs record from the backed up values
[Set City/State/Postal from Backup]
The system restores importer information from backup → Set the city name, state/province code, postal code, and country code in the customs record from the backed up values
[Set Contact Info from Backup]
The system restores importer information from backup → Set the contact function code, person name, communication number qualifier, and communication number in the customs record from the backed up values
[Clear Importer Fields]
The system cannot restore importer data from backup → Clear the importer field in the current processing area and set importer not found flag
[Corrector EDI Deletes Importer Data?]
The system checks if importer data was deleted by the corrector → If backup data exists and no new importer data was found in EDI, restore the original data, otherwise process new importer data
[Restore Original Importer Data]
The system restores original importer data → Move all backed up values including name, business number, qualifier, address, contact information, and CSA indicator back to the active importer record
[Check if Corrector EDI has Importer Data]
The system checks for importer entity data in the EDI BOL segments → The system determines if importer data exists and proceeds with appropriate processing path
[Backup Original Importer Data to Temporary Variables]
The system processes the corrector EDI importer information → The system retains the original importer data from backup variables including name, business number, qualifier, CSA indicator, address, city, province, postal code, country, and contact information
[Search Existing Records for Importer Entity 'IM']
The system searches for existing importer records with entity ID 'IM' in sequences 3 through 24 → The system identifies if an existing importer record is found and sets the appropriate processing flag
[Process New Importer Data from EDI BOL N1 Segment]
The system processes the EDI BOL N1 segment for importer entity → The system extracts importer name, business number qualifier, business number, and sets the importer found flag
[Set Importer Information in Customs Record]
The system processes the importer information → The system updates the customs record with importer name in both GCCC-IMPORTER and GCCS-N102-NAME fields, and sets the importer found flag
[Update Business Number and Qualifier]
The system processes the importer business identification → The system updates both customs record fields (GCCC-BUSINESS-NBR-QUAL, GCCC-BUSINESS-NBR) and N1 segment fields (GCCS-N103-ID-CDE-QUAL, GCCS-N104-ID-CDE) with the business number qualifier and business number
[Process Importer City/State from N4 Segment]
The system processes the N4 segment for importer location → The system updates the customs record with city name, state/province code, postal code, and country code from the N4 segment
[Clear Contact Information PER Segment Data]
The system handles contact information for the importer → The system clears all PER segment contact fields (contact function code, name, communication number qualifier, and communication number)
[Is this Corrector EDI Deletion Request?]
If this is a deletion request based on the absence of importer data in EDI segments → The system determines the appropriate action path for either deletion or update processing
[Restore Original Importer Data from Backup if Available]
The system processes the deletion request → The system restores the original importer data from backup variables if available, otherwise clears the importer fields
[EDI BOL Available?]
The system checks for EDI BOL data availability → The system should proceed with EDI BOL processing if available, otherwise use default address processing
[Retrieve Importer N3 Segment from EDI BOL]
The system retrieves the importer N3 address segment → The system should extract the address segment from the EDI BOL data source
[Extract Address Line 1 from N3 Segment]
The system extracts address line 1 from the N3 segment → The system should capture the first address line data for further processing
[Extract Address Line 2 from N3 Segment]
The system extracts address line 2 from the N3 segment → The system should capture the second address line data for storage
[Set Address Line 1 to 'NA']
The system processes the empty address line 1 → The system should set address line 1 to 'NA' as the default value
[Keep Original Address Line 1]
The system processes the address line 1 → The system should retain the original address line 1 value without modification
[Store Address Line 2]
The system stores address line 2 → The system should store the address line 2 data as extracted, whether empty or populated
[Set Default 'NA' for Address Line 1]
The system processes importer address information → The system should set address line 1 to 'NA' as the default value
[Clear Address Line 2]
The system processes address line 2 → The system should clear address line 2 to spaces
[Retrieve Importer N4 Segment from EDI BOL]
The system processes importer N4 segment data → The system retrieves city, state, postal code and country information from the EDI BOL N4 segment
[Extract City Name from N4 Segment]
The N4 segment contains city name information → The system extracts the city name from the D4-CITY-NAME field
[Extract State/Province Code from N4 Segment]
The N4 segment contains state or province code information → The system extracts the state/province code from the D4-STATE-PROV-CODE field
[Extract Postal Code from N4 Segment]
The N4 segment contains postal code information → The system extracts the postal code from the D4-POSTAL-CODE field
[Extract Country Code from N4 Segment]
The N4 segment contains country code information → The system extracts the country code from the D4-COUNTRY-CODE field
[Move City to Customs Record]
The system processes the address information for customs record → The city name is stored in the GCCS-N401-CITY-NAME field of the customs record
[Move State/Province to Customs Record]
The system processes the address information for customs record → The state/province code is stored in the GCCS-N402-STATE-PROV-CDE field of the customs record
[Move Postal Code to Customs Record]
The system processes the address information for customs record → The postal code is stored in the GCCS-N403-POSTAL-CDE field of the customs record
[Move Country Code to Customs Record]
The system processes the address information for customs record → The country code is stored in the GCCS-N404-COUNTRY-CDE field of the customs record
[Retrieve Importer PER Segment from EDI BOL]
The system processes importer contact information → The system attempts to retrieve the PER segment for importer contact details from the EDI BOL
[Extract Contact Function Code]
The system processes the contact information → The system extracts the contact function code from the PER segment and stores it in the importer record
[Extract Contact Person Name]
The system processes the contact information → The system extracts the contact person name from the PER segment and stores it in the importer record
[Extract Communication Number Qualifier]
The system processes the contact information → The system extracts the communication number qualifier from the PER segment and stores it in the importer record
[Extract Communication Number]
The system processes the contact information → The system extracts the communication number from the PER segment and stores it in the importer record
[Clear Contact Information Fields]
The system processes importer contact information → The system clears all contact information fields in the importer record
[Check for Existing Importer Data]
The system searches for importer records in sequence 3 through 24 AND finds an entity with ID 'IM' → The system should capture and store all existing importer details including CHOP code, name, business number qualifier, business number, CSA indicator, address information, and contact details
[Backup Original Importer Data]
The system identifies importer entity data with all associated fields populated → The system should store all importer fields in temporary variables including CHOP code, name, address lines, city, province/state, postal code, country, contact information, business number, business number qualifier, and CSA indicator
[Importer Data Deleted by Corrector?]
The system checks for importer entity records in the corrected EDI data AND no importer records are found:
importer fields are cleared
→ The system should identify this as an importer data deletion scenario requiring restoration of original data
[Retain Original Importer Data]
The system processes the importer data restoration → The system should restore all original importer fields from backup variables including CHOP code as SC301, entity ID as 'IM', name as N102, business number qualifier as N103, business number as N104, CSA indicator, address lines as N301/N302, city as N401, state/province as N402, postal code as N403, country as N404, and contact information as PER segments
[Apply Corrector Changes]
The system processes the corrector EDI transaction → The system should apply the corrector changes to update the importer information with the new values provided in the corrector EDI
[Save Current Description Data]
The transit description enhancement process begins → The system saves the current manifest data to backup variables and preserves all 46 cargo description array elements for potential restoration
[Retrieve Description from Reference CCN]
The system attempts to retrieve description data → The system calls GCCCCIO2 to fetch all description segments and populates the description arrays if successful
[Extract Description Components]
The system processes the retrieved data → The system extracts the lading description from GCCC segment and copies all 46 cargo description elements to the working description array
[Update Current Description Data]
Updating the current manifest → The system moves the compressed lading description to GCCC segment and copies all 46 enhanced cargo description elements to the cargo data array
[Set Sub-location Code from MC Table]
The system processes the MC table segment data → The sub-location code is set to the MC sub-location code value from the table
[Set Sub-location Code from RF Table]
The system processes the RF table segment data → The sub-location code is set to RF sub-location code value and customer bonded indicator is set to TRUE
[Move Table Data to GCSTBRTCM]
The system processes the returned table data → The table segment data is moved to GCSTBRTCM structure for further processing
[Move Table Segment to GCSTBRTMC]
The system processes the successful lookup result → The system moves the returned table segment data to the MC table structure
[Retrieve EBSBCKS CNS Segment]
The EBSBCKS segment is retrieved using the EDI BOL key and CNS sequence → The special handling segment data is made available for consolidated load checking
[Check H3 Special Handling Code]
The H3 special handling code is examined → The code is checked to determine if it equals 'CNS' indicating consolidated load
[Set Consolidated Load = 'Y']
The consolidated load flag needs to be set → The consolidated load indicator is set to 'Y'
[Increment CNS Sequence Number]
The search needs to continue to the next sequence → The CNS sequence counter is incremented by 1
[Store Compressed Data in GCSCCS53 Array]
The system stores segmented description data → All 46 description segments are moved from compressed data to WS-GCSCCS53-CARGO-DATA array
[Set Waybill Key for Spawn]
Preparing the spawn message parameters → Set the spawn waybill key to the input waybill key from GCWCCADD
[Set Waybill Date for Spawn]
Preparing the spawn message parameters → Set the spawn waybill date to the working storage waybill date
[Set Current CCN for Spawn]
Preparing the spawn message parameters → Set the spawn CCN to the current CCN from the array at the current index
[Set Action Code to 'AM']
Setting the action code parameter → Set the spawn action code to 'AM' for manifest creation
[Spawn GCT0111E Program]
Invoking the manifest creation process → Call the Z700-SPAWN-GCT0111E procedure to execute the manifest creation program
[Turn CSA Indicator OFF]
The business number qualifier is 'BN' or blank → Turn the CSA indicator OFF to deactivate Canada-US Agreement processing
[Save Current Description Data]
The description capture process begins → The system saves the current cargo manifest record, cargo description segments, and all description array data to temporary storage for potential restoration
[Retrieve Description from Source CCN]
The system attempts to retrieve description data from the source CCN → The system calls GCCCCIO2 program with fetch all segments flag to retrieve cargo description records including GCSCCRT, GCSCCS52, GCSCCS53, GCSCCS54, GCSCCS55, and GCSCCS56 segments
[Extract Description Components]
The system processes the retrieved description data → The system moves the first cargo description segment to GCSCCS53 and the first description array element to GCSCCS55, then extracts lading description and all cargo data elements from the description arrays into working storage
[Update Current Description Data]
The system updates the current description data → The system moves the compressed description to the lading description field and updates all cargo data array elements with the compressed description segments
[Save Current Description Data]
The system begins the transit description enhancement process → The current manifest data (GCSCCRT), commodity segment data (GCSCCS52), and all cargo description segments (GCSCCS53 array) are saved to working storage variables for potential restoration
[Retrieve Description from Related CCN]
The system needs to retrieve description data from the related CCN → The system calls GCCCCIO2 to fetch all segments (GCSCCS00, GCSCCRT, GCSCCS52, GCSCCS53, GCSCCS54, GCSCCS55, GCSCCS56) from the specified CCN using GU function with fetch-all option
[Extract Commodity Description]
The system processes the retrieved data → The lading description is moved from GCCC-LADING-DESCRIPTION to the description work area, and all 46 cargo data segments are moved from WS-GCSCCS53-CARGO-DATA array to the description database work area
[Update Cargo Description Fields]
The system updates the cargo manifest fields → The compressed description is moved from the work area to GCCC-LADING-DESCRIPTION, and all 46 cargo data segments are moved from the description work area to WS-GCSCCS53-CARGO-DATA array
[AU Table Record Found?]
The lookup result is evaluated → If the lookup is successful, the AU table data should be loaded into the working segment, otherwise the AU table data should be cleared to spaces
[Origin Country = 'MX'?]
The current origin country value is evaluated → If the origin country is 'MX' (Mexico), the process should exit immediately and keep the Mexico designation without further state-country validation
[Get EBSBCCM Commodity Segment]
The system attempts to retrieve EBSBCCM commodity segment using EDI BOL key and sequence number → The system returns commodity segment data if found or sets not found status if invalid EDI BOL or segment does not exist
[Add Lading Quantity to Total]
The system processes the commodity segment → The system adds the lading quantity from the segment to the total number of units counter
[Get EBSBCCR Weight Segment]
The system processes the first commodity segment → The system attempts to retrieve the corresponding EBSBCCR weight segment using EDI BOL key and commodity type CR with sequence CR001
[Extract Total Weight]
The system processes the weight segment → The system extracts the N7 weight value and assigns it to the commodity weight counter
[Set Quantity Qualifier from Lading Data]
The system extracts quantity information → The system assigns the lading quantity qualifier from the commodity segment to the customs quantity qualifier
[Use Fastway SHIPCOMM Data as Fallback]
The system needs commodity data for customs processing → The system initiates Fastway SHIPCOMM data retrieval as fallback source
[Get First SHIPCOMM Segment]
The system retrieves the first SHIPCOMM segment → The system calls FWCWBIO with GU function to get the first SHIPCOMM segment and sets found status based on result
[Add SHIPCOMM Quantities and Weights]
The system processes the SHIPCOMM data → The system adds number of units to quantity counter and adds appropriate weight (metric or standard) to weight counter based on metric indicator
[Get Next SHIPCOMM Segments]
The system continues processing additional SHIPCOMM segments → The system calls FWCWBIO with GN function to get next SHIPCOMM segments until no more segments are found
[Get EBSBCCM Segment]
The system attempts to retrieve EBSBCCM commodity segment using EDI BOL key and CM type with sequence number → The system should return commodity segment data if found or set not-found flag if segment does not exist
[Add Lading Quantity to Total]
The system processes the commodity segment data → The system should add the lading quantity from L0-LADING-QTY field to the total units counter
[Get EBSBCCR Weight Segment]
The system needs to extract weight information → The system should retrieve EBSBCCR weight segment using EDI BOL key with CR type and CR001 dependent key
[Extract Total Weight from N7-WEIGHT]
The system processes the weight segment data → The system should extract the weight value from N7-WEIGHT field and assign it to commodity weight counter
[Determine Weight Unit from Metric Indicator]
The system checks the metric indicator from shipment root data → The system should set weight unit to KG if metric indicator is M or L, otherwise set weight unit to LB
[Set Quantity Qualifier from Segment]
The system extracts quantity information → The system should assign the lading quantity qualifier from L0-LADING-QTY-QUAL field to the customs record
[Use Fastway SHIPCOMM Data as Fallback]
The system needs weight and quantity data for customs processing → The system should retrieve weight and quantity from Fastway SHIPCOMM segments and set quantity qualifier to PCS
[EDI BOL Weight/Quantity Found?]
Weight and quantity data is found in EDI BOL records → The system should use EDI BOL commodity and weight data for processing
[Check EDI BOL HN Segment Available?]
The system checks for EDI BOL HN segment availability → If EDI BOL HN segment is found, use EDI data; otherwise use Fastway data as fallback
[Extract Shipper Name from EDI BOL]
The system processes EDI shipper data → Shipper name is extracted to N102 field, CHOP code to SC301 field, and entity ID is set to 'SH'
[Check EDI BOL HA Address Segment?]
The system checks for EDI BOL HA address segment → If HA segment is found, extract address from EDI; otherwise use Fastway address data
[Extract Address from EDI BOL HA Segment]
The system processes EDI address data → Address line 1 is extracted to N301 field and address line 2 to N302 field
[Use Fastway Shipper Address Data]
The system needs shipper address information → Address line 1 is extracted from Fastway shipper address field 1, and if blank, 'NA' is used as default
[Check EDI BOL HC City/State Segment?]
The system checks for EDI BOL HC city/state segment → If HC segment is found, extract city/state from EDI; otherwise parse Fastway address data
[Extract City/State/Postal from EDI BOL HC]
The system processes EDI city/state data → City name is extracted to N401 field, state code to N402 field, postal code to N403 field, and country code to N404 field
[Parse Fastway Address for City/State/Postal]
The system parses Fastway address field 2 → City name, state code, and postal code are extracted and assigned to respective N4 segment fields
[Check EDI BOL GP Contact Segment?]
The system checks for EDI BOL GP contact segment → If GP segment is found, extract contact information; otherwise proceed to validation
[Extract Contact Information from EDI BOL]
The system processes EDI contact data → Contact function code is extracted to PER01 field, contact name to PER02 field, communication qualifier to PER03 field, and communication number to PER04 field
[Use Fastway Shipper Data as Fallback]
The system needs to build shipper record → Shipper information is extracted from Fastway shipment root data including name, CHOP code, and address
[Extract Shipper Name from Fastway]
The system processes Fastway shipper information → Shipper CHOP is extracted to SC301 field, entity ID is set to 'SH', and shipper name is extracted to N102 field
[Parse Fastway City/State Information]
The system parses shipper address field 2 → City name is extracted to N401 field, state code to N402 field, postal code to N403 field, and country code is determined via state lookup
[Search for EDI BOL Consignee Data]
The system searches for consignee data in EDI BOL → The system retrieves consignee segment 'CN' with sequence '01' from EDI BOL data
[Extract Consignee Name from EDI BOL]
The system processes the consignee segment data → The system sets entity ID to 'CN', extracts shipper name as consignee name, and extracts consignee CHOP code
[Search for EDI BOL Address Data]
The system searches for address information → The system retrieves address segment 'CA' with sequence '01' for the consignee
[Extract Address from EDI BOL]
The system processes the address segment → The system extracts additional name/address line 1 and additional name/address line 2 from the EDI BOL data
[Use Fastway Address Data]
The system needs address information for consignee → The system uses consignee address from Fastway shipment root data element 3
[Search for EDI BOL City/State Data]
The system searches for city/state information → The system retrieves city/state segment 'CC' with sequence '01' for the consignee
[Extract City/State/Postal from EDI BOL]
The system processes the city/state segment → The system extracts city name, state/province code, postal code, and country code from the EDI BOL data
[Use Fastway City/State Data]
The system needs geographic information for consignee → The system parses city name, state/province code, postal code, and determines country code from Fastway consignee data element 4
[Search for EDI BOL Contact Data]
The system searches for contact information → The system retrieves contact segment 'GP' with sequence '01' for the consignee
[Extract Contact Information from EDI BOL]
The system processes the contact segment → The system extracts contact function code, contact name, communication number qualifier, and communication number from the EDI BOL data
[Use Fastway Consignee Data]
The system needs consignee information → The system sets entity ID to 'CN', uses consignee CHOP code, and extracts consignee name from Fastway shipment root data element 1
[Build SF Stuffer Entity Segment]
SF entity data is found in EDI BOL segments with entity type 'PN' → Extract SF entity name, address, city, state, postal code, country code and contact information to create SF segment with entity ID 'SF'
[Build UC Ultimate Consignee Segment]
UC entity data is found in EDI BOL segments with entity type 'UN' → Extract UC entity name, address, city, state, postal code, country code and contact information to create UC segment with entity ID 'UC', defaulting address to 'NA' if not provided
[Build BN Beneficial Owner Segment]
BN entity data is found in EDI BOL segments with entity type 'BN' → Extract BN entity name from U1-NAME field, address from BT segments, city/state/postal/country from BY segments to create BN segment with entity ID 'BN', defaulting address to 'NA' if not provided
[Build C1 Carrier Entity Segment]
C1 entity data is found in EDI BOL transportation segments:
consignee data code in Fastway equals 'C'
→ Extract C1 entity information from EDI TN/T2/TA/T3 segments OR from Fastway consignee data to create C1 segment with entity ID 'C1', including name, address, city, state, postal code, country and contact information
[Build N1 Notify Party Segment]
N1 entity data is found in EDI BOL transportation segments → Extract N1 entity information from EDI TN/T2/TA/T3 segments to create N1 segment with entity ID 'N1', including name, address, city, state, postal code, country and contact information
[Build PF/SS Entity Segments from MCOA]
MCOA segment is found with organization ID equal to 'PF' or 'SS' → Extract entity name, ID code qualifier, ID code from F5 fields and address information from ON/OC segments to create PF or SS segment, defaulting address to 'NA' if not provided
[Build Additional Entity Segments]
Transportation segment is found with organization ID matching '11', 'MC', 'OO', or 'FW' → Extract entity information from TN/T2/TA/T3 segments to create corresponding entity segment with matching organization ID, including name, address, city, state, postal code, country and contact information
[Assign Country Codes]
State/province code is provided in entity address data → Search state-country reference table to find matching country code and assign it to entity country field, leaving blank if no match found
[EDI BOL PER Segment Available?]
The system checks for EDI BOL PER segment data → The system identifies whether contact information exists in the EDI source or should use default processing
[Extract Contact Function Code]
The system processes contact information → The contact function code is extracted and stored in the contact function code field
[Extract Contact Person Name]
The system processes contact information → The contact person name is extracted and stored in the person name field
[Extract Communication Number Qualifier]
The system processes contact information → The communication number qualifier is extracted and stored in the communication qualifier field
[Extract Communication Number]
The system processes contact information → The communication number is extracted and stored in the communication number field
[Clear Contact Fields if No Data]
The system processes contact information → All contact fields are cleared or set to spaces
[Retrieve EDI BOL Stuffer Data EBSNRSC-PN]
The system searches for stuffer data with entity type 'PN' and sequence '01' → The system retrieves stuffer name data if available or sets not found status
[Stuffer Data Found?]
Stuffer name data is successfully found → The system continues with stuffer entity processing
[Stuffer Data Found?]
No stuffer name data is found → The system skips stuffer entity processing and continues to next entity type
[Extract Stuffer Name from U1-NAME]
The system processes the stuffer entity information → The stuffer name is extracted from U1-NAME field and assigned to the entity name field
[Retrieve Stuffer Address EBSNRSA-PA]
The system searches for stuffer address data with type 'PA' for the stuffer entity → The system retrieves address information if available or sets not found status
[Extract Address Lines from U2 fields]
The system processes the address information → Address line 1 and address line 2 are extracted from U2-ADDL-NAME-ADDR-1 and U2-ADDL-NAME-ADDR-2 fields
[Retrieve City/State/Postal EBSNRSA-PC]
The system searches for stuffer location data with type 'PC' for the stuffer entity → The system retrieves city, state, postal, and country information if available
[Extract City, State, Postal, Country from U4 fields]
The system processes the location information → City name, state/province code, postal code, and country code are extracted from U4 fields
[Retrieve Contact Information EBSNRSA-GP]
The system searches for stuffer contact data with type 'GP' for the stuffer entity → The system retrieves contact information if available
[Extract Contact Function, Name, Communication Details]
The system processes the contact information → Contact function code, contact name, communication number qualifier, and communication number are extracted from the contact segment
[Set Entity ID to 'UC']
The system processes the UN segment data → The entity ID code is set to 'UC' to identify this as an Ultimate Consignee record
[Extract Ultimate Consignee Name]
The system processes the UN segment → The ultimate consignee name is extracted and assigned to the entity name field
[Address Data Available?]
The system checks for UA address segment availability → If UA address segment is found, extract address lines, otherwise set default address to 'NA'
[Extract Address Lines 1 & 2]
The system processes the address information → Address line 1 and address line 2 are extracted from the UA segment data
[City/State Data Available?]
The system checks for UC city/state segment availability → If UC segment is found, extract city, state, postal and country codes, otherwise clear all geographic fields
[Extract City Name, Extract State/Province Code, Extract Postal Code, Extract Country Code]
The system processes the geographic information → City name, state/province code, postal code, and country code are extracted from the UC segment
[Contact Data Available?]
The system checks for GP contact segment availability → If GP segment is found, extract contact function code, name, communication qualifier and number, otherwise proceed to validation
[Extract Contact Function Code, Extract Contact Name, Extract Communication Qualifier, Extract Communication Number]
The system processes the contact information → Contact function code, contact name, communication number qualifier, and communication number are extracted from the GP segment
[Set Organization ID to 'BN']
Setting up the organization identifier for transportation segment search → The organization ID is set to 'BN' (Beneficial Owner)
[Search for Transportation Segment with BN ID]
Searching for transportation segment data → The system retrieves transportation segment information for beneficial owner entity
[Transportation Segment Found?]
Checking if transportation segment data exists → If transportation segment is found, proceed to search for BN entity; otherwise, end beneficial owner processing
[Search for BN Entity in EDI BOL]
Searching for beneficial owner entity in EDI BOL data → The system retrieves beneficial owner entity information from EDI BOL
[BN Entity Found in EDI BOL?]
Checking if beneficial owner entity data exists → If beneficial owner entity is found, proceed to extract entity details; otherwise, end beneficial owner processing
[Extract BN Entity Name]
Processing beneficial owner entity information → The beneficial owner entity name is extracted and stored in the segment record
[Extract Consignee CHOP Code]
Processing beneficial owner identification codes → The consignee CHOP code is extracted and stored in the beneficial owner segment
[Search for BN Address Segment]
Searching for beneficial owner address data → The system retrieves address segment information for the beneficial owner
[Extract Address Line 1 and 2]
Processing beneficial owner address information → Address line 1 and address line 2 are extracted and stored in the beneficial owner segment
[Search for BN City/State Segment]
Searching for beneficial owner city and state data → The system retrieves city/state segment information for the beneficial owner
[Extract City, State, Postal Code, Country]
Processing beneficial owner location information → City, state, postal code, and country are extracted and stored in the beneficial owner segment
[Clear City/State Information]
Processing beneficial owner location information → All city, state, postal code, and country fields are cleared (set to spaces)
[Clear Contact Information]
Finalizing beneficial owner segment data → All contact function code, name, communication qualifier, and communication number fields are cleared
[Insert BN Record into Customs Database]
Storing the beneficial owner information → The beneficial owner record is inserted into the customs database with sequence numbers 0003-0025
[Set Organization ID to 'C1']
The organization identifier needs to be set → The organization ID is set to 'C1' to identify this as a carrier entity
[Search EDI BOL Transportation Segments]
The system searches for C1 carrier transportation segments → Transportation segments with organization ID 'C1' are retrieved from EDI BOL data
[Extract Carrier Information from EDI BOL]
Carrier information needs to be extracted → Carrier organization ID, name, ID code qualifier, and ID code are extracted from the transportation segment
[Get Transportation Address Data]
Address information is needed for the carrier → Address line 1 and address line 2 are retrieved from T2 transportation address segments
[Get Transportation City/State Data]
City and state information is needed for the carrier → City name, state/province code, postal code, and country code are retrieved from TA transportation segments
[Get Transportation Contact Data]
Contact information is needed for the carrier → Contact function code, contact name, communication number qualifier, and communication number are retrieved from T3 transportation segments
[Check Fastway Consignee Data]
The system checks Fastway consignee data for carrier information → The consignee data code is evaluated to determine if it equals 'C' indicating carrier type
[Parse City/State/Postal from Address]
City, state, and postal code information needs to be extracted → Consignee data field 4 is parsed to extract city name, state/province code, and postal code
[Lookup Country Code from State]
Country code needs to be determined for the carrier address → The state-country lookup table is searched to find the corresponding country code for the state/province code
[Insert C1 Segment into Customs Record]
The segment needs to be added to the customs record → The C1 segment is inserted into the customs record array with sequence numbers 0003-0025
[Search EDI BOL Transportation Segments]
Searching for notify party information → The system iterates through transportation segments looking for organization ID 'N1'
[Extract Organization ID]
Processing the segment data → The organization ID is extracted from the segment for entity type validation
[Organization ID = 'N1'?]
Validating the entity type → Processing continues if organization ID equals 'N1', otherwise the segment is skipped
[Extract Entity Name]
Processing the N1 entity data → The entity name is extracted and stored in the N1 segment record
[Get Transportation Address Segment T2]
Retrieving address information for the entity → The system attempts to get the corresponding T2 address segment
[Extract Address Line 1]
Processing address information → The first address line is extracted and stored in the N1 segment record
[Extract Address Line 2]
Processing additional address information → The second address line is extracted and stored in the N1 segment record
[Get Transportation City/State Segment TA]
Retrieving city and state information for the entity → The system attempts to get the corresponding TA city/state segment
[Extract City Name]
Processing city information → The city name is extracted and stored in the N1 segment record
[Extract State/Province Code]
Processing state/province information → The state/province code is extracted and stored in the N1 segment record
[Extract Postal Code]
Processing postal code information → The postal code is extracted and stored in the N1 segment record
[Extract Country Code]
Processing country information → The country code is extracted and stored in the N1 segment record
[Get Transportation Contact Segment T3]
Retrieving contact information for the entity → The system attempts to get the corresponding T3 contact segment
[Extract Contact Function Code]
Processing contact function information → The contact function code is extracted and stored in the N1 segment record
[Extract Contact Name]
Processing contact name information → The contact name is extracted and stored in the N1 segment record
[Extract Communication Number Qualifier]
Processing communication qualifier information → The communication number qualifier is extracted and stored in the N1 segment record
[Extract Communication Number]
Processing communication number information → The communication number is extracted and stored in the N1 segment record
[Insert N1 Record into Customs Database]
Inserting the record into the customs database → The N1 record is successfully stored in the GCSCCS55 customs database table
[Skip - Not N1 Entity]
The organization ID != 'N1' → The segment is skipped and processing continues with the next segment
[Retrieve MCOA Segment Data]
The system retrieves MCOA segment data with type 'OT' → The MCOA segment is fetched from the EDI database
[Entity Type is PF or SS?]
The entity organization ID is checked → Processing continues only if the entity type is 'PF' or 'SS'
[Extract Entity Information]
Entity information is extracted → Entity ID, name, ID code qualifier, and ID code are captured from the segment
[Set Entity ID and Name]
Entity identification fields are populated → The entity ID code is set to the organization ID and entity name is set to the organization name
[Set ID Code Qualifier and Code]
ID code fields are populated → The ID code qualifier and ID code are set from the MCOA segment, and CHOP code is cleared
[Retrieve Address Information]
Address information is retrieved using MCOA ON segment type → Address data is fetched from the EDI database for the entity
[Set Address Lines from MCOA]
Address fields are populated → Address line 1 and address line 2 are set from the MCOA segment data
[Set Default Address as 'NA']
Address fields need to be populated → Address line 1 is set to 'NA' and address line 2 is cleared
[Retrieve City/State Information]
City and state information is retrieved using MCOA OC segment type → Geographic data is fetched from the EDI database for the entity
[Set City, State, Postal, Country]
Geographic fields are populated → City name, state/province code, postal code, and country code are set from MCOA segment
[Clear City/State Fields]
Geographic fields need to be populated → City name, state/province code, postal code, and country code are all cleared
[Insert Entity Record]
The entity record is inserted → The segment is stored in the GCSCCS55 table with sequence numbers 0003-0025
[Build 11 Entity Segment]
The system searches for EDI BOL TN segments with entity type 11 and finds matching data → The system creates a customs database record with entity type 11 information including name, address, city/state, and contact details
[Process NN Entity Data]
The system processes NN entity data and retrieves associated GC and GA address segments → The system creates a complete entity record with name from NN segment, address from GC segment, city/state/postal/country from GA segment, and inserts it into customs database
[Build MC Entity Segment]
The system searches for EDI BOL TN segments with entity type MC and finds matching data → The system processes the MC entity data and creates a customs database record with Motor Carrier information
[Build OO Entity Segment]
The system searches for EDI BOL TN segments with entity type OO and finds matching data → The system processes the OO entity data and creates a customs database record with Other Organization information
[Build FW Entity Segment]
The system searches for EDI BOL TN segments with entity type FW and finds matching data → The system processes the FW entity data and creates a customs database record with Freight Forwarder information
[Check if Corrector EDI has Importer Data]
The system checks for importer data presence in the transaction → If importer name exists in temporary storage, proceed to read existing importer data, otherwise skip backup process
[Read Existing Importer from Record 55]
The system searches for existing importer records in sequence 3-24 of record type 55 → Read importer records until found or maximum sequence reached
[No Backup Required]
If backup requirements → Skip the backup process and continue with normal processing
[Build SF Stuffer Entity Segments]
Processing SF entity segments from EBSNRSC data source → Extract entity name, address information from PA type, city/state/postal/country from PC type, and contact information from GP type, then create SF entity record with default 'NA' address if address is blank
[Build UC Ultimate Consignee Segments]
Processing UC entity segments from EBSNRSC data source → Extract entity name, address information from UA type, city/state/postal/country from UC type, and contact information from GP type, then create UC entity record with default 'NA' address if address is blank
[Build BN Beneficial Owner Segments]
Processing BN entity segments from EBSNRSC and EBSNRTD data sources → Extract entity name from BN type, address information from BT type, city/state/postal/country from BY type, set consignee chop code, and create BN entity record with default 'NA' address if address is blank
[Build C1 Carrier Entity Segments]
Processing C1 entity segments from EBSNRTD or SHIPROOT data sources → If EBSNRTD data found, extract entity name from TN type, address from T2 type, city/state/postal/country from TA type, and contact from T3 type; otherwise use Fastway consignee data with parsed address information and create C1 entity record
[Build N1 Notify Party Segments]
Processing N1 entity segments from EBSNRTD data source → Extract entity name from TN type, address information from T2 type, city/state/postal/country from TA type, and contact information from T3 type, then create N1 entity record with default 'NA' address if address is blank
[Build PF/SS MCOA Entity Segments]
Processing PF/SS entity segments from EBSMCOA data source → Extract entity name, ID code qualifier, and ID code from OT type, address information from ON type, city/state/postal/country from OC type, then create PF or SS entity record with default 'NA' address if address is blank
[Build 11 Entity Segments]
Processing 11 entity segments from EBSNRTD data source → Extract entity name from TN type, address information from T2 type, city/state/postal/country from TA type, and contact information from T3 type, then create 11 entity record with default 'NA' address if address is blank
[Build MC Entity Segments]
Processing MC entity segments from EBSNRTD data source → Extract entity name from TN type, address information from T2 type, city/state/postal/country from TA type, and contact information from T3 type, then create MC entity record with default 'NA' address if address is blank
[Build OO Entity Segments]
Processing OO entity segments from EBSNRTD data source → Extract entity name from TN type, address information from T2 type, city/state/postal/country from TA type, and contact information from T3 type, then create OO entity record with default 'NA' address if address is blank
[Build FW Entity Segments]
Processing FW entity segments from EBSNRTD data source → Extract entity name from TN type, address information from T2 type, city/state/postal/country from TA type, and contact information from T3 type, then create FW entity record with default 'NA' address if address is blank
[Build IM Importer Segments]
Processing IM entity segments from EBSNRSC or AU table data sources → If EDI data exists, extract importer name, business number qualifier, business number, address, and contact information; if only AU table data exists, create importer record from AU table with business number qualifier 'M5' and set CSA indicator on; if both AU and sequence 55 importer found with business number qualifier 'BN' or blank, turn CSA indicator off
[Get EDI BOL Segment for Entity Type]
System attempts to retrieve entity segment data from EBSNRSC → Entity segment data is retrieved if found, otherwise segment is marked as not found
[Extract Entity Name from N1 Segment]
System processes entity identification information → Entity ID code, name, ID code qualifier, and ID code are extracted and populated
[Get Address Segment N3]
System attempts to retrieve address segment data from EBSNRSA → Address segment data is retrieved if found, otherwise address processing is skipped
[Extract Address Line 1]
System processes address information → Address line 1 and address line 2 are extracted and populated in entity record
[Get City/State Segment N4]
System attempts to retrieve city/state segment data from EBSNRSA → City/state segment data is retrieved if found, otherwise geographic processing is skipped
[Extract City Name]
System processes geographic information → City name, state/province code, postal code, and country code are extracted and populated
[Get Contact Segment PER]
System attempts to retrieve contact segment data from EBSNRSA or EBSNRTD → Contact segment data is retrieved if found, otherwise contact processing is skipped
[Extract Contact Function Code]
System processes contact information → Contact function code, person name, communication number qualifier, and communication number are extracted and populated
[Populate Shipper from Fastway]
Building shipper record (sequence 0001) AND shipper entity type is required → Set entity ID to 'SH' AND populate shipper CHOP code from shipment root AND populate shipper name from shipment root AND set default address values for missing fields
[Populate Consignee from Fastway]
Building consignee record (sequence 0002) AND consignee entity type is required → Set entity ID to 'CN' AND populate consignee CHOP code from shipment root AND populate consignee name from shipment root consignee data field 1 AND set default address values for missing fields
[Parse Address Components]
Processing address field 2 for shipper:
processing address field 4 for consignee
processing carrier address data
→ Parse address into city name, state/province code, and postal code components AND lookup country code using state-country table based on state/province code AND set country code from lookup result
[Lookup Country Code]
Country code determination is required for address validation → Search state-country table for matching state/province code AND set country code from table entry when match found AND set country code to spaces when no match found AND add error message when country code cannot be determined
[Populate Carrier from Fastway]
Building carrier record AND consignee data code field 2 equals 'C' → Set entity ID to 'C1' AND populate carrier name from consignee data field 2 AND populate carrier address from consignee data field 3 AND set carrier address to 'NA' when field 3 is spaces AND parse carrier address components for city, state, postal code, and country
[Entity ID is Shipper/Consignee/Broker?]
The entity type is shipper (SH), consignee (CN), or customs broker (CB) → Generate an invalid entity type error message as these types are reserved for specific record positions
[N4 Address Data Present?]
The N4 address data is completely empty or contains only spaces → The system should skip all address validation and proceed to the next validation step
[Set Function Code to 'GU']
The system sets up the database operation type → The function code should be set to 'GU' to Execute a get unique operation
[Set Table ID to 'MS']
The system identifies which table to access → The table ID should be set to 'MS' to target the message repository table
[Call Table I/O Service]
The system executes the message text retrieval operation → The table I/O service should be called with the configured parameters to Execute the lookup
[Table Access Successful?]
If the operation result → If the return flag indicates 'SUCCESSFUL', the message text should be processed, otherwise handle the failure case
[Move Table Segment to MS Structure]
The system processes the retrieved table segment → The table segment data should be moved to the MS structure for further processing
[Extract English Text Message]
The system extracts the displayable message text → The English text field from the MS structure should be extracted as the message content
[Set Message Label for Display]
The system prepares the message for display → The extracted English text should be assigned to the message label field for user presentation
[Clear MS Structure - No Message Found]
The system handles the retrieval failure → The MS structure should be cleared to spaces to ensure no invalid message text is displayed
[Call IMS to Change Message]
The system needs to process a cargo control number for manifest creation → Call IMS with CHNG function to invoke GCT0111E program, write the message to the processing queue, and purge the IMS message
[Get Importer N1 Segment from EDI BOL]
The system searches for importer N1 segment with entity type 'IM' → The system retrieves importer name and identification details if found
[Is Corrector EDI with Backup Data?]
The system processes a corrector EDI transaction → The system uses the backup importer data instead of processing new EDI data
[Restore Backup Importer Data]
A corrector EDI requires restoration of previous importer information → The system restores importer name, business number, qualifier, address, and contact information from backup
[Extract Importer Information]
The system processes new importer information → The system extracts importer name, business number qualifier, and business number for customs processing
[Get Importer N3 Address Segment]
The system searches for corresponding N3 address segment → The system retrieves address line information for the importer
[Process Address Information]
The system processes address line information → The system sets address line 1 and 2, defaulting to 'NA' if address line 1 is empty
[Get Importer N4 City/State Segment]
The system searches for corresponding N4 city/state segment → The system retrieves city, state, postal code, and country information for the importer
[Process City/State/Postal Information]
The system processes location information → The system sets city name, state/province code, postal code, and country code for the importer
[Clear Contact Information]
The system finalizes importer segment data → The system clears all contact information fields for the importer record
[Insert Importer Record into Customs Database]
The system processes the importer record for storage → The system inserts the importer record into the customs database with sequence number assignment
[Handle Importer Data Deletion]
Previous importer data existed for the shipment → The system processes importer data deletion while preserving backup data if available
[Retain Backup Data if Available]
The system processes importer data deletion → The system retains and uses backup importer data instead of clearing all importer information
[Clear Importer Fields]
The system processes importer data deletion → The system clears importer name and related fields from the customs record
[Reset CSA Indicator]
The system processes importer information from both sources → The system turns off the CSA indicator to prevent duplicate processing
[Get EDI BOL N1 Segment for Importer]
The system searches for importer N1 segment in EDI BOL data → The system retrieves the importer entity segment if it exists or sets not found status
[Check if Corrector EDI Has Backup Data]
The system checks for existing backup importer data → The system identifies whether backup importer name data is available
[Extract Importer Entity Information]
The system processes the importer entity information → The system extracts importer name, business number qualifier, business number, and sets the importer found flag
[Set Entity ID to 'IM']
The system sets up the importer entity record → The entity ID is set to 'IM' to identify this as an importer record
[Extract Importer Name]
The system processes importer entity details → The importer business name is extracted and stored in both customs record and segment fields
[Extract Business Number Qualifier]
The system processes importer identification details → The business number qualifier is extracted and stored in both customs record and segment fields
[Extract Business Number]
The system processes importer identification details → The business number is extracted and stored in both customs record and segment fields
[Set CSA Indicator]
The system completes importer entity processing → The importer found flag is set to indicate successful processing
[Get EDI BOL N3 Address Segment]
The system searches for importer address information → The system retrieves the N3 address segment if it exists or sets not found status
[Extract Address Line 1 and Extract Address Line 2]
The system processes importer address information → Address line 1 is extracted, and if it is blank or low-values then it is set to 'NA', and address line 2 is extracted
[Get EDI BOL N4 City/State Segment]
The system searches for importer city and state information → The system retrieves the N4 city/state segment if it exists or sets not found status
[Extract City Name, Extract State/Province Code, Extract Postal Code, Extract Country Code]
The system processes importer geographic information → City name, state/province code, postal code, and country code are extracted from the segment
[Clear City/State Data]
The system needs to handle missing geographic information → All city, state, postal code, and country fields are cleared
[Clear Contact Information]
The system finalizes importer segment data → All contact information fields including contact function code, name, communication qualifier, and communication number are cleared
[Store Importer in Customs Record]
The system stores the importer information → The importer segment is added to the customs record array for database storage
[Clear Importer Data but Keep Backup]
The system processes a corrector EDI that removes importer information → The system restores backup importer data and sets appropriate processing flags, but if no backup exists and no segment 55 importer found, then importer fields are cleared
[Set CSA Indicator]
The system processes multiple importer data sources → The CSA indicator is turned off to prevent conflicts between importer sources
[Start Importer Segment Building]
Importer segment building is initiated → The importer segment data structure is cleared and ready for processing
[Get Importer N1 Segment from EDI BOL]
The system needs importer information → The system retrieves the N1 segment with entity type 'IM' from the EDI BOL
[Extract Entity ID Code]
The system processes the N1 segment → The entity identification code is extracted and made available for validation
[Backup Importer Data Exists?]
The system checks for existing backup data → The system determines if backup importer name data is available from earlier processing
[Restore Backup Importer Data]
The system needs to populate importer information → All backup importer details including name, business number, address, and contact information are restored to the current segment
[Process New Importer N1 Segment]
The system processes the importer information → The system creates new importer customs data and processes associated address and contact segments
[Create Importer N1 for Customs]
The system creates customs importer information → The importer entity ID code is set and importer found flag is marked
[Set Importer Name and Business Number]
The system populates importer identification → The importer name is set from N1 name field and business number is set from N1 ID code field
[Set Business Number Qualifier]
The system processes business number qualification → The business number qualifier is set from N1 ID code qualifier field for both customs and segment data
[Get and Process N3 Address Segment]
The system needs importer address information → The system retrieves the N3 address segment for the importer from EDI BOL
[Set Address Information]
The system processes address information → Address line 1 is set from EDI data or 'NA' if blank, and address line 2 is set from EDI data
[Set Default 'NA' Address]
The system processes address information → Address line 1 is set to 'NA' and N3 data fields are cleared
[Get and Process N4 City/State Segment]
The system needs importer geographic information → The system retrieves the N4 city/state segment for the importer from EDI BOL
[Set City, State, Postal, Country]
The system processes geographic information → City name, state/province code, postal code, and country code are set from EDI data
[Clear N4 Data Fields]
The system processes geographic information → All N4 data fields including city, state, postal code, and country are cleared
[Insert into Customs Record 55]
The system saves the importer information → The importer segment is inserted into customs record type 55 with appropriate sequence number
[Corrector EDI Deleted Importer?]
The system checks for data deletion → The system determines if the importer was deleted by a corrector EDI transaction
[Backup Data Available?]
The system checks for recovery options → The system determines if backup importer name data is available for restoration
[Restore Backup Importer Data]
The system restores importer information → All backup importer details are restored and CSA indicator logic is applied
[Extract Business Number Qualifier from N1 Segment]
Processing importer information from EDI BOL → Extract business number qualifier from N1 segment and store in GCCC-BUSINESS-NBR-QUAL and GCCS-N103-ID-CDE-QUAL
[Extract Business Number from N1 Segment]
Processing importer information from EDI BOL → Extract business number from N1 segment and store in GCCC-BUSINESS-NBR and GCCS-N104-ID-CDE
[Set CSA Indicator OFF]
Processing importer business number qualifier validation → Set CSA indicator to OFF to disable CSA processing
[Store Qualifier in GCCC-BUSINESS-NBR-QUAL]
Processing importer information from EDI BOL → Store importer name from N1 segment in GCCC-IMPORTER and GCCS-N102-NAME
[Check if Corrector EDI with Existing Importer Data]
The system checks for existing importer data backup requirement → The system should backup all original importer data including CHOP code, name, qualifiers, business number, CSA indicator, address information, city/state/postal data, and contact details to temporary storage variables
[Store Business Number Qualifier]
The system processes business qualifier restoration → The system should move temporary business number qualifier (WS-TEMP-IM-QUAL) to both customs business number qualifier field (GCCC-BUSINESS-NBR-QUAL) and N1 segment qualifier field (GCCS-N103-ID-CDE-QUAL)
[Store Business Number]
The system processes business number restoration → The system should move temporary business number (WS-TEMP-IM-CDE) to both customs business number field (GCCC-BUSINESS-NBR) and N1 segment ID code field (GCCS-N104-ID-CDE)
[Process New EDI Importer Data]
The system determines no backup restoration is required → The system should process the new EDI importer data directly and continue with normal processing flow
[Continue Processing]
The system processes the failure condition → The system should clear the customs importer field (GCCC-IMPORTER) and entity ID code field (GCCS-N101-ENTITY-ID-CDE) to spaces
[Corrector EDI with Importer Data?]
If importer data, business number, and business number qualifier are all present → The system determines whether to proceed with importer data backup or skip the backup process
[Backup Importer Name]
The system backs up importer data before applying corrector EDI changes → The importer name is stored in temporary backup field WS-TEMP-IM-NAME
[Backup Business Number & Qualifier]
The system backs up business identification data before applying corrector EDI changes → The business number qualifier is stored in WS-TEMP-IM-QUAL and business number is stored in WS-TEMP-IM-CDE
[Backup CSA Indicator]
The system backs up CSA status before applying corrector EDI changes → The CSA indicator value is stored in temporary backup field WS-TEMP-CSA-IND
[Backup Address Information]
The system backs up address data before applying corrector EDI changes → Address line 1 is stored in WS-TEMP-IM-ADR1 and address line 2 is stored in WS-TEMP-IM-ADR2
[Backup City/State/Postal Data]
The system backs up location data before applying corrector EDI changes → City name is stored in WS-TEMP-IM-CITY, state/province code in WS-TEMP-IM-PROV, and postal code in WS-TEMP-IM-POSTAL
[Backup Country Code]
The system backs up country data before applying corrector EDI changes → The country code is stored in temporary backup field WS-TEMP-IM-CTRY
[Backup Contact Information]
The system backs up contact data before applying corrector EDI changes → Contact function code is stored in WS-TEMP-IM-CONT-CDE, person name in WS-TEMP-IM-PER-NAME, communication qualifier in WS-TEMP-IM-COM-QUAL, and communication number in WS-TEMP-IM-COM-NUM
[Clear Current Importer Fields]
The system prepares to process corrector EDI changes → The original importer, business number, and business number qualifier fields are cleared to spaces
[AU Table Has Importer Data?]
The system searches AU table using consignee CHOP code and commodity code → If AU table contains matching importer data, proceed to retrieve it, otherwise check EDI data sources
[EDI Has Importer Data?]
The system checks EDI BOL for importer N1 segments → If EDI contains importer data, proceed to validate business number qualifier, otherwise maintain current CSA status
[Turn CSA Indicator Off]
Business number qualifier is 'BN' or blank spaces → Turn off CSA indicator to prevent automatic CSA processing
[Retrieve EDI N1 Importer Segment]
The system needs to process importer business number information → The system retrieves the N1 importer segment from the EDI data using the bill of lading key
[N1 Importer Segment Found?]
The retrieval operation completes → If the segment is found, proceed with business number extraction, otherwise skip business number processing
[Extract Business Number Qualifier from N1-ID-CODE-QUAL]
The system processes the importer identification information → The business number qualifier is extracted from the N1-ID-CODE-QUAL field
[Extract Business Number from N1-ID-CODE]
The system processes the importer identification information → The business number is extracted from the N1-ID-CODE field
[Store Business Number Qualifier in GCCC-BUSINESS-NBR-QUAL]
The system updates the customs record → The qualifier is stored in the GCCC-BUSINESS-NBR-QUAL field
[Store Business Number in GCCC-BUSINESS-NBR]
The system updates the customs record → The business number is stored in the GCCC-BUSINESS-NBR field
[Update Customs Record with Business Number Data]
The system processes the importer information → The customs record is updated with both the business number and qualifier in the appropriate fields
[Set Importer Name from N1-NAME]
The system processes importer identification information → The importer name is extracted from N1-NAME and stored in the customs record
[Mark Importer Data as Found]
The processing of the N1 importer segment completes → The system sets the importer found flag to indicate successful processing
[Get Importer N3 Segment from EDI BOL]
The system processes importer address information → The system retrieves the N3 segment containing address line 1 and address line 2 from the EDI BOL
[N3 Segment Found?]
The N3 segment retrieval is attempted from EDI BOL → If N3 segment is found, extract address details; if not found, set default address values
[Extract Address Line 1 from N3]
The system processes the N3 segment → The system extracts the first address line from field D2-ADDL-NAME-ADDR-1
[Extract Address Line 2 from N3]
The system continues N3 segment processing → The system extracts Address Line 2 from field D2-ADDL-NAME-ADDR-2
[Set Default Address Line 1 to 'NA']
The system processes importer address information → The system sets Address Line 1 to 'NA' and clears Address Line 2
[Clear Address Line 2]
The system sets default address values → The system clears Address Line 2 field
[Get Importer N4 Segment from EDI BOL]
The system processes importer geographic information → The system retrieves the N4 segment containing city, state, postal code, and country data
[N4 Segment Found?]
The N4 segment retrieval is attempted from EDI BOL → If N4 segment is found, extract geographic details; if not found, clear all geographic fields
[Extract City Name from N4]
The system processes the N4 segment → The system extracts the city name from field D4-CITY-NAME
[Extract State/Province Code from N4]
The system continues N4 segment processing → The system extracts the state/province code from field D4-STATE-PROV-CODE
[Extract Postal Code from N4]
The system continues N4 segment processing → The system extracts the postal code from field D4-POSTAL-CODE
[Extract Country Code from N4]
The system completes N4 segment processing → The system extracts the country code from field D4-COUNTRY-CODE
[Clear All N4 Address Fields]
The system processes importer geographic information → The system clears all N4 address fields including city, state, postal code, and country
[Check if EDI BOL Data Available]
System checks for EDI BOL data availability using the EDI BOL key → System determines if valid EDI BOL data exists for contact information extraction
[Retrieve Importer PER Segment from EDI]
System retrieves importer PER segment using entity type 'IM' and sequence '01' and segment type 'GP' → Importer contact person segment is retrieved from EDI BOL data or marked as not found
[Extract Contact Function Code]
System processes the PER segment contact function code field → Contact function code is extracted and stored in the customs record contact function code field
[Extract Contact Person Name]
System processes the PER segment contact name field → Contact person name is extracted and stored in the customs record contact name field
[Extract Communication Number Qualifier]
System processes the PER segment communication number qualifier field → Communication number qualifier is extracted and stored in the customs record communication qualifier field
[Extract Communication Number]
System processes the PER segment communication number field → Communication number is extracted and stored in the customs record communication number field
[Store Contact Information in Customs Record]
All contact fields (function code, person name, communication qualifier, communication number) are populated → Contact information is stored in the customs record type 55 PER segment fields
[Clear Contact Information Fields]
Contact information cannot be extracted from EDI sources → All contact information fields are cleared to spaces in the customs record
[Backup Original Importer Data]
The system processes corrector EDI that may modify or delete importer information → All original importer data is backed up including CHOP code, name, business number qualifier, business number, CSA indicator, address information, city/state/postal data, and contact information, and backup found flag is set to true
[Corrector EDI Deletes Importer?]
The corrector EDI deletes importer information from the current transaction → If backup importer data is available, restore from backup data; otherwise clear importer entity ID and set importer not found status
[Restore from Backup Data]
The system needs to restore importer information → All backed up importer data is restored including CHOP code as SC301, entity ID as 'IM', name as N102, business number qualifier as N103, business number as N104, CSA indicator, address information as N301/N302, city/state/postal as N401/N402/N403/N404, and contact information as PER01/PER02/PER03/PER04, and importer found flag is set
[Clear Importer Entity ID]
The system processes the importer data deletion → Importer entity ID is cleared to spaces and if record 55 importer not found flag is set, clear the importer name field
[Set Segment Type to EBSNRSA]
The system configures the segment type → The segment type is set to EBSNRSA to target address segments
[Set Function Code to GU - Get Unique]
The system sets the function code → The function code is set to GU to retrieve a unique segment
[Set EDI BOL Key for Record 55]
The system assigns the EDI BOL key → The EDI BOL key for record 55 is set as the root key for the request
[Set Type-1 to NN - Notify Party]
The system configures the primary entity type → Type-1 is set to NN to identify notify party segments
[Set Type-2 to GA - Geographic Address]
The system configures the secondary segment type → Type-2 is set to GA to identify geographic address segments
[Set Operator to Equals]
The system configures the search operator → The operator is set to equals for exact segment matching
[Call EDI BOL I/O Service]
The system calls the EDI BOL I/O service → The service is invoked to retrieve the geographic address segment from EDI BOL data
[Set GA Found Flag]
The geographic address segment is successfully found and retrieved → The GA found flag is set to indicate successful retrieval
[Set GA Not Found Flag]
The geographic address segment is not found in the EDI BOL data → The GA not found flag is set to indicate unsuccessful retrieval
[Set Sequence Counter to 1]
The system initializes search parameters → The sequence counter is set to 1 to start searching from the first segment
[Retrieve EBSBCKS Segment]
The system retrieves EBSBCKS segment data using the current sequence number → The segment data is loaded for consolidated load indicator evaluation
[Special Handling Code = 'CNS'?]
The system examines the special handling code field → If the code equals 'CNS', the consolidated indicator is found; otherwise, continue searching next sequence
[Set CNS Indicator Found]
The system processes the consolidated load identification → The CNS indicator flag is set to found state
[Increment Sequence Counter]
The system continues searching for consolidated load indicators → The sequence counter is incremented by 1 to check the next segment
[Counter > 98 OR CNS Found?]
If continuation criteria → If sequence counter exceeds 98 or CNS indicator is found, terminate search; otherwise continue with next segment
[Set Consolidated Flag to 'Y']
The system finalizes the consolidated load determination → The consolidated flag is set to 'Y' to indicate this is a consolidated shipment
[Set Consolidated Flag to Space]
The system finalizes the consolidated load determination → The consolidated flag is set to space to indicate this is not a consolidated shipment
[Get EDI BOL Importer N1 Segment]
Retrieving importer N1 segment with entity type 'IM' and sequence '01' → The system should call EDI BOL interface to get importer entity data
[Extract Importer Name]
Processing the importer entity data → The importer name should be extracted from N1-NAME field and stored in both customs record and importer field
[Extract Business Number Qualifier]
Processing importer identification data → The business number qualifier should be extracted from N1-ID-CODE-QUALIFIER and stored in both customs record and business number qualifier field
[Extract Business Number]
Processing importer identification data → The business number should be extracted from N1-ID-CODE and stored in both customs record and business number field
[Get Importer N3 Address Segment]
Retrieving importer address data with entity type 'IM', sequence '01', and address type 'IC' → The system should call EDI BOL interface to get importer address segment
[Extract Address Line 2]
Processing additional address information → Address line 2 should be extracted from D2-ADDL-NAME-ADDR-2 field and stored in customs record
[Get Importer N4 City/State Segment]
Retrieving importer city/state data with entity type 'IM', sequence '01', and city type 'IA' → The system should call EDI BOL interface to get importer city/state segment
[Extract City Name]
Processing city information → City name should be extracted from D4-CITY-NAME field and stored in customs record
[Extract State/Province Code]
Processing state/province information → State/province code should be extracted from D4-STATE-PROV-CODE field and stored in customs record
[Extract Postal Code]
Processing postal information → Postal code should be extracted from D4-POSTAL-CODE field and stored in customs record
[Extract Country Code]
Processing country information → Country code should be extracted from D4-COUNTRY-CODE field and stored in customs record
[Update CSA Indicator Logic]
Evaluating CSA indicator requirements → The system should check if both AU table data and EDI data are found for CSA determination
[Reset CSA Indicator]
Processing CSA indicator logic → The CSA indicator should be set to off
[Reset CSA Indicator to OFF]
The business number qualifier is 'BN':
the business number qualifier is blank/spaces
→ The CSA indicator is set to OFF
[Keep CSA Indicator Current State]
AU table importer data is not found:
EDI BOL importer data is not found
business number qualifier is neither 'BN' nor blank
→ The CSA indicator maintains its current state without modification
[EDI BOL N3 Segment Found?]
The system checks for EDI BOL N3 segment availability → The system should identify whether address data is available from EDI source or requires fallback processing
[Set Address Line 1 to 'NA']
The system processes the importer address information → The system should set address line 1 to 'NA' as the default value
[Use EDI Address Line 1]
The address line 1 is not empty and does not contain low values → The system should use the EDI address line 1 value directly for the importer record
[Set Address Line 2 from EDI]
The system processes address line 2 information → The system should assign address line 2 from the EDI data to the importer record
[No EDI N3 Segment Available?]
No EDI BOL N3 segment is available → The system should initiate fallback address processing procedures
[Clear All N3 Address Data]
The system processes importer address data → The system should clear all N3 address data fields to ensure clean initialization
[Set Address Line 1 to 'NA']
The system requires a value for address line 1 → The system should set address line 1 to 'NA' as the fallback default value
[Clear All PER Segment Data]
The system processes the importer contact clearing operation → All PER segment contact fields are set to spaces including contact function code, contact name, communication number qualifier, and communication number
[EDI BOL Importer Segment Found?]
The system checks for the presence of an importer segment in the EDI BOL data → If the importer segment is found, continue with normal processing, otherwise proceed with deletion handling logic
[Restore from Backup Data]
The system needs to handle the deletion while preserving original data → The system restores all importer information from backup including chop code, entity ID, name, business number qualifier, business number, CSA indicator, address information, city, province, postal code, country, and contact details, and sets the importer found flag to true
[Clear Current Importer Data]
The system processes the deletion request → If the importer was not found in record 55, the system clears the importer name field and sets the entity ID code to spaces
[Parameters Ready for Segment Retrieval]
System calls EBCLGIO to retrieve EDI BOL segment data → EDI BOL segment data is retrieved and stored in the working storage segment structure
[Display Timestamp with Process Info]
The initialization process displays status information → A formatted message is displayed to system error output containing the date, time, process name, and key business identifiers including CCN key, equipment ID, importer, business number, and business number qualifier

Structural Validations

[Station Information Retrieval]
The system validates station names and state codes → If origin station name is blank, add error message for invalid origin station name. If origin station state code is blank, add error message for invalid origin province/state code, otherwise determine origin country from state code lookup. If destination station name is blank, add error message for invalid destination station name
[Shipper Data Extraction]
The system extracts and validates shipper data → Extract shipper chop, name, and address from shipment data. If shipper name is blank, add error message for invalid shipper name. If shipper address line 1 is blank, set to 'NA'. Process address line 2 with special formatting rules and set default country to 'US' if address is incomplete
[Consignee Data Extraction]
The system extracts and validates consignee data → Extract consignee name, chop, and address from shipment data. If consignee name is blank, add error message for invalid consignee name. If consignee address line 1 is blank, set to 'NA'. Process address line 2 with special formatting rules and set default country to 'CA' if address is incomplete
[Address Validation]
The system validates address information → For each address with state/province code, search state-country table to find matching entry and set corresponding country code. If state/province code is not found in table, add error message for invalid state/province code and leave country code blank
[Contact Information Processing]
The system processes contact information for entity records → Extract contact function code, contact name, communication number qualifier, and communication number. Validate communication qualifier is blank, 'FX', or 'TE'. If contact information is incomplete, generate appropriate error messages for missing required fields
[Origin Station Name Present?]
The origin station name field is empty or contains only spaces → Throw error: indicating invalid origin station name
[Origin Province/State Code Present?]
The origin province or state code field is empty or contains only spaces → Throw error: for invalid origin province state code and clear the origin country determination table
[Destination Station Name Present?]
The destination station name field is empty or contains only spaces → Throw error: indicating invalid destination station name
[Canadian customs code = '00000'?]
The Canadian customs code from MC table equals '00000' → Clear the MC table data AND add an error message for invalid Canadian customs code for manifest port
[Add invalid manifest port error message]
The MC table lookup is not successful → Clear the MC table data AND add an error message for invalid manifest port
[Add invalid customs code error message]
The MC table lookup is not successful → Clear the MC table data AND set error flag 3 to ON AND save the port name for error messaging
[Is Canadian Customs Code '00000'?]
The Canadian customs code equals '00000' → The system should clear the MC table data and Throw error: for invalid Canadian customs code
[Generate MC Table Not Found Error]
The MC table lookup fails to find a matching record → The system should clear MC table data and Throw error: indicating the manifest port was not found in MC table
[Generate Invalid Customs Code Error]
The Canadian customs code in the retrieved record equals '00000' → The system generates an error message for invalid Canadian customs code and uses the port name in the error
[Generate Invalid Manifest Port Error]
The MC table lookup fails to find a matching record → The system generates an error message for invalid manifest port and uses the port name in the error
[Lookup MC Table with Manifest Port]
The system looks up the manifest from port in the MC table using table lookup function → If the lookup is successful, the system retrieves the MC table segment data, otherwise it clears the MC table data and prepares for error processing
[Check if code equals '00000' and generate specific error messages for invalid customs codes]
The Canadian customs code equals '00000' → The system clears the MC table data, sets the port name as message number, retrieves the invalid Canadian customs error message, and adds it to the validation error list
[Set Invalid Port Error]
The MC table lookup fails to find the manifest port → The system clears the MC table data, sets the port name as message number, retrieves the invalid manifest port error message, and adds it to the validation error list
[Set Error Message Number to INV-MFST-PORT-CA-CUSTOMS]
The system needs to retrieve the error message for INV-MFST-PORT-CA-CUSTOMS → The system sets the error message number to INV-MFST-PORT-CA-CUSTOMS for message lookup
[Message Found in MS Table?]
The table lookup function returns a status → The system checks if the return flag equals SUCCESSFUL to determine if the message was found
[Retrieve English Error Message Text]
The system processes the retrieved message data → The system moves the English text field from the message table segment to the working message label
[Error Message Retrieval Request]
The system needs to retrieve error message text from the message table → The system should initialize table lookup parameters, set function code to 'GU', set table ID to 'MS', use the message error number as the key, and call the table access routine
[Table Lookup Successful?]
The table lookup fails or returns an error → The system should set the MS table segment to spaces to clear any invalid data
[Canadian Customs Code = '00000'?]
The Canadian customs code equals '00000' → Clear the MC table data, set error flag 2, and save port name for error message as the customs code is invalid
[Generate 'Invalid Manifest Upon' Error Message]
Processing manifest-to port validation errors → Retrieve and generate 'Invalid Manifest Upon' error message
[Generate 'Invalid Canadian Customs Code' Error Message]
Processing manifest-to port validation errors → Use saved port name and retrieve 'Invalid Canadian Customs Code' error message
[Generate 'Invalid Manifest Port MC' Error Message]
Processing manifest-to port validation errors → Use saved port name and retrieve 'Invalid Manifest Port MC' error message
[Check Canadian Customs Code]
The Canadian customs code equals '00000' → The system marks the Canadian customs code as invalid, generates an error message for invalid Canadian customs port, and clears the MC table data
[Generate MC Table Not Found Error]
The MC table lookup is not successful → The system clears the MC table data, generates an error message for invalid manifest port MC, and uses the port name as the error message number
[Generate Invalid Canadian Customs Code Error Message]
The system validates customs code requirements → The system should Throw error: indicating invalid Canadian customs code for the manifest port
[Generate Manifest Port Not Found Error Message]
The system attempts to validate manifest port information → The system should Throw error: indicating the manifest port was not found in the manifest code table
[Set Port Name in Error Message]
The system prepares an error message → The manifest port name is set in the message number field
[Retrieve Error Message Text]
The system needs the error message text → The error message text is retrieved from the message table
[Add Error Message to Message Array]
The system processes the error → The error message is added to the message array for reporting
[Set Table ID and Key Values]
The table lookup is configured for MS table → The table ID is set to 'MS' and the error message number is used as the search key
[Generate Invalid Destination Station Sub-location Error]
Final sub-location validation is performed → An error message for invalid destination station sub-location code is generated and added to the message list
[Generate Error Message: Invalid Destination Station Sub-location Code]
The system processes the error condition → The system should Throw error: indicating invalid destination station sub-location code and add it to the message collection
[Generate Invalid Conveying Car Error Message]
The validation utility indicates the car ID is invalid → Throw error: for invalid conveying car and add it to the message collection
[Generate Car ID Validation Error]
The car ID validation utility returns an invalid result (all asterisks) → The system should Throw error: indicating invalid conveying car and include the original car value in the message
[Check for Valid EDI BOL Data]
The system checks for valid EDI BOL data by verifying the origin road number is not zero and retrieving the first SHIPMIN segment with type 'E' and sequence '1' → The system sets the EDI BOL availability flag to valid if data is found, otherwise sets it to invalid, and extracts the EDI BOL key from the data line for subsequent processing
[Check for Valid EDI BOL]
The system checks for EDI BOL availability by verifying origin road number is not zero and retrieving SHIPMIN segment with type 'E' and number '1' → If EDI BOL data is found, set valid EDI BOL flag and extract EDI BOL key, otherwise set invalid EDI BOL flag
[Check for Valid EDI BOL]
The system checks for EDI BOL availability by examining the origin road number in SHIPROOT → If origin road number is not zero, retrieve SHIPMINE segment with type 'E' and sequence '1', and if found, extract EDI BOL key from data line 1 and set valid EDI BOL flag, otherwise set invalid EDI BOL flag
[Set Weight to Zero]
The system needs to set a weight value → The weight counter (WS-CMOD-WEIGHT-9) is set to zero
[Valid EDI BOL?]
The system checks for EDI BOL validity → If the EDI BOL is invalid, the system sets the EBSBCCM not found flag and skips segment retrieval
[Valid EDI BOL?]
The system checks EDI BOL validity status → If EDI BOL is invalid, weight segment is marked as not found, otherwise proceed with database retrieval
[Set Weight Segment Not Found]
EDI BOL is determined to be invalid → Weight segment found flag is set to not found without attempting database retrieval
[Weight Data Retrieved Successfully?]
The system checks database operation status → If status code is spaces (success), mark weight segment as found, otherwise mark as not found
[Check for Valid EDI BOL]
The system checks for EDI BOL availability by verifying origin road number is not zero → The system sets EDI BOL availability flag and extracts EDI BOL key if valid data exists
[Check for Valid EDI BOL Data]
The system checks for valid EDI BOL data by verifying origin road number is not zero and retrieving shipment mining data → The system sets EDI BOL availability flag and extracts EDI BOL key if data is found
[Validate Quantity Qualifier]
The system validates the qualifier against the MU (Measurement Unit) table → If the qualifier is not found in the table, an error message is generated for invalid measurement unit
[Validate Qualifier Against MU Table]
Quantity qualifier is validated against MU table → If qualifier not found in MU table, generate error message for invalid measurement unit
[Generate Error Message for Invalid Qualifier]
Quantity qualifier is spaces or empty → Generate error message indicating required quantity qualifier is missing
[EBSBCKS Segment Found?]
The system checks the retrieval status → If the segment is found, processing continues to check the special handling code, otherwise the search continues to the next sequence
[Determine Country Code from State]
Processing shipper country information → Search state-country lookup table to find matching country code for the state, and if not found add error message for invalid state/province code
[Validate Shipper Data Requirements]
Validating shipper data completeness → If shipper name is empty, add error message for invalid shipper name
[Extract Address from EDI BOL]
The system processes the address segment → Address line 1 is set from D2-ADDL-NAME-ADDR-1, address line 2 is set from D2-ADDL-NAME-ADDR-2, and if address line 1 is empty, it is set to 'NA'
[Set Default Address if Missing]
Address line 1 is empty or contains only spaces → Address line 1 is set to 'NA' as the default value
[Lookup State/Country Combination]
The state-country lookup is performed → If a valid country is found, the country code is set; if no valid country is found, an error message is generated for invalid consignee province/state code
[Validate Consignee Data]
Data validation is performed → The system validates that consignee name is not empty, generates error message if consignee name is missing, and calls the N1 segment validation routine
[Generate Invalid State Error]
The shipper state/province code is not found in the state-country lookup table → Generate an invalid shipper province/state code error message and add it to the message collection
[Generate Invalid State Error]
The consignee state/province code is not found in the state-country lookup table → Generate an invalid consignee province/state code error message and add it to the message collection
[Generate Missing Address Error]
The address line 1 is empty → Generate a required address information error message
[Generate City Length Error]
The city name length is less than 2 characters → Generate a minimum length requirement error message for city name
[Generate Postal Code Length Error]
The postal code length is less than 3 characters → Generate a minimum length requirement error message for postal code
[Generate Invalid State/Country Error]
The state/province code is not found in the lookup table for the specified country → Generate an invalid state/province code error message
[Complete Address Validation]
The country code field is still empty → Generate a required country code error message
[UN Number Found in EDI?]
The system examines the UN/NA identification code → If the first two characters equal 'UN', the system accepts it as a valid UN number, otherwise continues searching
[Check UN Number Format]
The system examines the UN/NA identification code → If the first two characters are 'UN', the identifier is considered a valid UN number format
[EDI BOL Valid?]
The EDI BOL validation flag indicates invalid BOL → The hazmat commodity segment not found flag is set AND EDI hazmat processing is skipped
[EBSBCCM-CH Found?]
The database status code is spaces (successful) → The hazmat commodity segment found flag is set
[UN Number Starts with 'UN'?]
The LH1-UN-NA-ID-CD field starts with 'UN' → The UN number format is considered valid for hazmat processing
[EBSBCHI-HS Found?]
The database status code is spaces (successful) → The hazmat shipping info found flag is set
[Check UN Prefix Format]
The system checks the first two characters of the identification code → The system should verify that the prefix equals 'UN' to confirm valid UN number format
[Valid EDI BOL?]
The system attempts to access hazmat segments → If the EDI BOL is invalid, hazmat processing is marked as not found and terminated
[Segment Found?]
The system checks the result of the database call → If the segment is not found, hazmat processing is marked as not found, otherwise processing continues
[UN Number Starts with 'UN'?]
The system validates the identification code format → If the code starts with 'UN', it is processed as a valid UN number, otherwise the sequence is incremented to check the next segment
[EBSBCHI Hazmat Segment Found?]
The system checks for the existence of EBSBCHI hazmat segment with LH3 data → If the segment is found and contains valid data, proceed to extract the proper shipping name, otherwise indicate no description is available
[SHIPERP Data Found?]
System accesses SHIPERP segment for emergency response data → If SHIPERP data is found, validate UN code format, otherwise mark no Fastway hazmat data available
[SHIPCOMM Found?]
The retrieval operation completes → If SHIPCOMM data is found, continue with emergency response data retrieval, otherwise skip Fastway hazmat processing
[SHIPERP Found?]
The retrieval operation completes → If SHIPERP data is found, proceed with UN code format validation, otherwise skip Fastway hazmat processing
[Check UN Code Format]
The system examines the UN/NA code field → The UN code format is validated to ensure it starts with 'UN' prefix
[SHIPERPD Found?]
The retrieval operation completes → If SHIPERPD data is found, extract hazmat description, otherwise proceed with hazmat found flag setting
[Validate EDI BOL Structure]
The system validates the EDI BOL structure → Each N1 segment is validated for required fields (entity ID, name), address information is validated for completeness, and contact information is validated for proper format
[Valid Entity ID Found?]
The system validates the entity ID → If the entity ID matches valid entity ID values, processing continues; otherwise, the entity ID is cleared and processing moves to next entity
[Validate Entity Data Requirements]
The system validates entity data requirements → Required fields are checked including entity ID, name, address line 1, city, state/province, postal code, and country code with appropriate error messages for missing data
[Get PF/SS Address Data]
The PF/SS address information is not found in ON segment → The system sets the primary address to 'NA' and secondary address to spaces as default values
[Get NN Address Data]
The NN address information is not found in GC segment or is spaces → The system sets the address to 'NA' as default value and clears secondary address
[Validate Required Fields]
The entity ID code or entity name is missing → The system generates required field error messages for missing entity ID code and entity name
[Validate Required Fields]
Entity ID code is present but not in valid values list or is shipper/consignee/customs broker → The system generates an invalid entity ID code error message
[Validate Address Information]
The primary address information is missing or spaces → The system generates a required address information error message
[Validate Address Information]
City name is missing or has less than 2 characters → The system generates required city name error message or minimum length error message
[Validate Address Information]
Postal code is present but has less than 3 characters → The system generates a minimum length error message for postal code
[Validate Address Information]
State/province code is missing or invalid for the specified country → The system generates required state/province error message or invalid state/province error message
[Validate Address Information]
Country code is missing or spaces → The system generates a required country code error message
[Validate Contact Information]
Communication number qualifier is missing → The system generates a required communication qualifier error message
[Validate Contact Information]
Communication qualifier is not spaces, 'FX' (fax), or 'TE' (telephone) → The system generates an invalid communication qualifier error message
[Validate Contact Information]
Communication number is missing or spaces → The system generates a required communication number error message
[Transportation Segment Found?]
The system checks the lookup result status → If the status code is spaces then the segment is found, otherwise the segment is not found
[Segment Found?]
The retrieval result needs to be validated → If the status code is spaces then the segment is found, otherwise the segment is not found
[MCOA Segment Found?]
The system checks the retrieval status → If no error status is returned and segment type is 'OT', the segment is considered found, otherwise processing stops
[Validate Entity Segment]
The system validates the entity segment → Standard entity validation rules are applied to ensure data integrity
[Segment Type is OT?]
System validates the segment type → If segment type equals 'OT' then set MCOA found flag, otherwise set MCOA not found flag
[Set Default Address Line 1 to 'NA']
The system handles the missing address information → The first address line is set to 'NA' as a default value
[Check CCN Array from EDI BOL]
The system checks if the CCN array contains data → The system determines whether to proceed with CCN processing or continue with normal processing
[CCN Array from EDI BOL Available?]
The system checks for CCN array data from EDI BOL processing → The system determines if CCN array contains valid data or is empty/low-values to decide processing path
[Check AU and EDI BOL Importer Data?]
The system finds both AU importer data and EDI BOL importer data are present → The system should proceed to validate business number qualifier for CSA indicator adjustment
[Continue Processing]
The system validates sub-location requirements → An error message for invalid destination station sub-location code should be generated
[Check for Valid EDI BOL]
The system checks for valid EDI BOL data by verifying origin road number is not zero → The system sets EDI BOL availability status and extracts BOL key from shipment mining data if available
[Check for Valid EDI BOL]
The system checks for valid EDI BOL data by looking up SHIPMIN segment with type 'E' and sequence '1' → If EDI BOL data is found, extract the EDI BOL key for further processing, otherwise mark as invalid EDI BOL
[Validate Final Weight]
Finalizing weight for customs manifest → If weight is greater than zero, use the calculated weight, otherwise set default weight to '00000001'
[Validate Quantity]
Finalizing quantity for customs manifest → If quantity is greater than zero, use the calculated quantity, otherwise set default quantity to 1
[Check EDI BOL Data Availability]
The system checks for EDI BOL data availability by verifying if origin road number is not zero → The system sets the EDI BOL validity flag and retrieves the EDI BOL key if data is available
[Quantity Qualifier Empty?]
The quantity qualifier field is empty or contains only spaces → The system generates a required field error message for quantity qualifier
[Found in MU Table?]
The quantity qualifier is not found in the measurement units reference table → The system generates a 'not found on MU table' error message
[Validate Shipper Record Data]
The system performs data validation → All required shipper fields are validated for completeness and format compliance according to customs requirements
[Extract Address from EDI BOL]
The system processes the address information → The system extracts address line 1 and 2, and if address line 1 is blank, sets it to 'NA'
[Validate Consignee Record Data]
The system validates the consignee record → The system performs N1 segment validation including entity ID, name, address, city/state/postal/country, and contact information validation
[Build NN Entity Segments]
The system processes the named entity segment → The system creates an NN entity record with entity ID code, name, consignee chop code, address, city, state, postal code, and country information from the EDI data
[Validate All N1 Segments]
The address information is validated → The system sets address line 1 to 'NA' if it is spaces or low-values, and ensures all address components are properly populated
[Build NN Entity Segments]
The system processes NN segments for named entities → If NN segment is found with valid entity ID, extract entity information with address from GC and GA segments, otherwise reset variables if not found
[Entity ID Valid?]
The system validates the entity ID code → If entity ID is not empty and not in valid values list or is shipper, consignee, or customs broker, add invalid entity ID error message
[Name Required?]
The system validates the entity name field → If entity ID is not empty and name is empty, add required name field error message
[Set Default Address to NA]
The system validates the address field → If entity ID is not empty and address line 1 is empty, add required address error message and set default address to NA if address is empty
[Validate City Length >= 2]
The system validates the city name length → If city name is empty, add required city error message, otherwise if city name length is less than 2 characters, add minimum length error message
[Validate Postal Code Length >= 3]
The system validates the postal code length → If postal code is not empty and length is less than 3 characters, add minimum length error message
[Validate State/Country Combination]
The system validates the state/country combination → If country is Canada, USA, or Mexico and state/province is empty, add required state error message, otherwise if state/province does not match country in lookup table, add invalid state error message, and if country is empty, derive country from state lookup
[Validate Entity Data]
The system validates the communication data → If communication qualifier is empty and contact name or communication number is provided, add required qualifier error message, and if qualifier is not empty, FX, or TE, add invalid qualifier error message, and if qualifier or contact name is provided but communication number is empty, add required communication number error message
[Entity ID Present?]
The entity ID code field is evaluated for presence → If entity ID code is spaces, skip entity validation and complete processing, otherwise proceed with entity validation
[Generate Invalid Entity ID Error]
The system needs to report the validation failure → Generate error message 'Invalid Entity ID Value' and add to message collection for the record
[Set Default Address as 'NA']
The system processes address requirements → Address line 1 is set to 'NA' as the default value
[Validate Stuffer Entity Data]
The system validates the stuffer entity data → Required field validations are performed and missing address defaults to 'NA' if not provided
[Set Default Address 'NA']
The system processes Ultimate Consignee address requirements → Address line 2 is cleared and address line 1 is set to 'NA' as default
[Clear City/State/Postal/Country Fields]
The system processes Ultimate Consignee location requirements → All location fields (city name, state/province code, postal code, country code) are cleared
[Validate UC Segment Data]
The system performs N1 segment validation → All required fields are validated according to customs requirements and error messages are generated for missing mandatory data
[Set Default 'NA' Address]
Processing address information → Address line 1 is set to 'NA' as default value
[Validate BN Segment Data]
Validating the segment before database insertion → The beneficial owner segment data is validated according to customs data requirements
[Validate C1 Entity Segment]
Validating the carrier entity information → The system validates required fields, data formats, and business rules for the C1 entity segment
[Transportation Segment Found?]
Checking for segment existence in EDI BOL data → If segment exists, continue processing; otherwise skip to end of notify party processing
[Address Segment Found?]
Checking for address information availability → If T2 segment exists, extract address lines; otherwise proceed to city/state processing
[City/State Segment Found?]
Checking for geographic information availability → If TA segment exists, extract geographic details; otherwise proceed to contact processing
[Contact Segment Found?]
Checking for contact information availability → If T3 segment exists, extract contact details; otherwise proceed to address defaulting
[Validate N1 Segment Data]
Validating segment data for customs compliance → System performs field validation checks and generates error messages for missing required data
[MCOA Segment Found?]
The system checks the retrieval result → If status code is spaces and segment type equals 'OT', set MCOA found flag to true, otherwise set to false
[Address Segment Found?]
The system checks the retrieval result → If status code is spaces, set address found flag to true, otherwise set to false
[Set Default Address as 'NA']
The system needs to populate address fields → Move 'NA' to GCCS-N301-ADDRESS-INFO-1 and spaces to GCCS-N302-ADDRESS-INFO-2
[City/State Segment Found?]
The system checks the retrieval result → If status code is spaces, set city/state found flag to true, otherwise set to false
[Clear City/State Information]
The system needs to populate geographic fields → Move spaces to GCCS-N401-CITY-NAME, GCCS-N402-STATE-PROV-CDE, GCCS-N403-POSTAL-CDE, and GCCS-N404-COUNTRY-CDE
[Validate N1 Segment Data]
The system validates the segment data → Execute Y100-EDIT-N1-SEGMENT to validate all required fields and data integrity
[Validate NN Entity ID Code]
The system checks the entity ID code against valid entity ID values → If the entity ID is valid, processing continues; if invalid, the entity is skipped and importer data is cleared if no S55 importer found
[Code Starts with 'UN'?]
Checking if the identification code represents a valid UN number → If code starts with 'UN', extract the UN number; otherwise increment sequence to check next segment
[Are all required fields empty?]
The segment has empty name, address, city/state/postal/country fields → Generate required field error messages for name, address, city, state/province, postal code, and country
[Entity ID present but Name missing?]
Entity ID code is not empty but entity name is empty → Generate a required name error message
[Entity ID missing but other data present?]
Entity ID code is empty but address data, contact data, or other entity information is not empty → Generate a required entity ID error message
[Is Entity ID valid for this segment type?]
Entity ID code is not empty and is not a valid entity type or is shipper, consignee, or customs broker → Generate an invalid entity ID value error message
[Entity ID present but Address missing?]
Entity ID code is not empty but address line 1 is empty → Generate a required address error message
[City name present?]
City name is empty → Generate a required city name error message
[City name length >= 2 characters?]
City name length is less than 2 characters → Generate a minimum length requirement error message
[Postal code length >= 3 characters?]
Postal code is not empty and length is less than 3 characters → Generate a minimum length requirement error message
[State/Province code present?]
Country code is Canada, USA, or Mexico and state/province code is empty → Generate a required state/province error message
[State/Province and Country combination valid?]
The state/province code is not valid for the specified country according to the state-country lookup table → Generate an invalid state/province error message
[Country code still missing?]
Country code is empty after attempting to derive from state/province code → Generate a required country code error message
[Contact name present but qualifier missing?]
Contact name is not empty but communication number qualifier is empty → Generate a required communication qualifier error message
[Communication number present but qualifier missing?]
Communication number is not empty but communication number qualifier is empty → Generate a required communication qualifier error message
[Communication qualifier is valid?]
Communication qualifier is not blank, 'FX' (fax), or 'TE' (telephone) → Generate an invalid communication qualifier value error message
[Qualifier or name present but number missing?]
Communication qualifier is not empty or contact name is not empty but communication number is empty → Generate a required communication number error message
[Generate Entity ID Required Error]
The system validates the party information → Throw error: indicating that entity ID is required when address information is present
[Generate Name Required Error]
The system validates the party information → Throw error: indicating that name is required when address information is present
[Generate Name Required Error Message]
The system validates the party information → Throw error: indicating that name is required when entity ID is present
[Generate Invalid Entity ID Error]
The system validates the entity ID → Throw error: indicating that the entity ID value is invalid for this party position
[Generate Address Required Error]
The system validates the party information → Throw error: indicating that address is required when entity ID is present
[Is Entity ID or Name Missing?]
The system validates required party information → Both entity ID and name must be present, and all required address fields must be populated with appropriate error messages for missing data
[Is Shipper or Consignee Record?]
All core fields (name, address, city/state/postal, contact) are empty → Generate comprehensive error messages for all missing required fields
[Entity ID Present?]
Entity identifier code is missing or empty → Generate error message requiring entity identifier
[Name Present?]
Entity name field is missing or empty → Generate error message requiring entity name
[Entity ID Valid for Record Type?]
Entity identifier is not in valid list or is shipper/consignee/customs broker type → Generate error message for invalid entity identifier value
[Entity ID Present but Address Missing?]
Primary address information is missing or empty → Generate error message requiring address information
[City Name Present?]
City name field is missing or empty → Generate error message requiring city name
[City Name Length >= 2?]
City name length is less than 2 characters → Generate error message for minimum length requirement
[Postal Code Length >= 3?]
Postal code length is less than 3 characters → Generate error message for postal code minimum length requirement
[Country is CA/US/MX?]
State or province code is missing or empty → Generate error message requiring state or province code
[State/Country Combination Valid?]
State/province code does not correspond to the specified country in reference table → Generate error message for invalid state/province and country combination
[Contact Name Present but Qualifier Missing?, Communication Number Present but Qualifier Missing?]
Communication number qualifier is missing or empty → Generate error message requiring communication qualifier
[Qualifier Valid Value?]
Qualifier value is not spaces, 'FX', or 'TE' → Generate error message for invalid communication qualifier value
[Qualifier or Name Present but Number Missing?]
Communication number is missing or empty → Generate error message requiring communication number
[Generate Shipper Required Field Errors]
The system performs N1 segment validation → The system generates error messages for shipper name required, address required, city required, state required, postal code required, and country required
[Generate Consignee Required Field Errors]
The system performs N1 segment validation → The system generates error messages for consignee name required, address required, city required, state required, postal code required, and country required
[Add N102 Name Required Error Message]
The system checks field consistency → The system generates an error message indicating that the name field is required when entity ID is specified
[Add N101 Entity ID Required Error]
The system checks field dependencies → The system generates an error message indicating that entity ID is required when address information is provided
[Add N102 Name Required Error]
The system checks field dependencies → The system generates an error message indicating that name is required when address information is provided
[Validate N3 Address Fields]
The system validates address requirements → The system generates an error message indicating that address is required for the identified entity
[Validate N4 Geographic Fields]
The system validates geographic information → The system generates an error message indicating that city name is required
[Validate N4 Geographic Fields]
The system validates city name format → The system generates an error message indicating minimum length of 2 characters is required
[Validate N4 Geographic Fields]
The system validates postal code format → The system generates an error message indicating minimum length of 3 characters is required
[Validate N4 Geographic Fields]
The system validates geographic requirements → The system generates an error message indicating that state/province code is required for the specified country
[Validate N4 Geographic Fields]
The system cross-validates state and country codes → The system generates an error message indicating invalid state/province code for the country
[Validate N4 Geographic Fields]
The system validates geographic completeness → The system generates an error message indicating that country code is required
[Validate PER Contact Fields]
The system validates contact information consistency → The system generates an error message indicating that communication qualifier is required when contact name is provided
[Validate PER Contact Fields]
The system validates contact information consistency → The system generates an error message indicating that communication qualifier is required when phone number is provided
[Validate PER Contact Fields]
The system validates qualifier values → The system generates an error message indicating invalid communication qualifier value
[Validate PER Contact Fields]
The system validates contact completeness → The system generates an error message indicating that communication number is required
[Shipper Name Empty?]
The entity name field is empty or spaces → Generate error message indicating entity name is required
[Shipper Address Empty?]
The address field is empty or spaces → Generate error message indicating address is required
[Shipper City Empty?]
The city field is empty or spaces → Generate error message indicating city is required
[Shipper State Empty?]
The state/province field is empty or spaces → Generate error message indicating state/province is required
[Shipper Postal Empty?]
The postal code length is less than 3 characters → Generate error message indicating minimum length of 3 characters required
[Shipper Country Empty?]
The country field is empty or spaces → Generate error message indicating country is required
[Generate Error: Shipper Name Required]
The system needs to communicate the validation failure → Generate appropriate error message based on the specific missing field (name, address, city, state, postal, country)
[Add Error to Message Array]
The system needs to store the error for user notification → Add the error message to the message array, increment message index, and clear temporary message fields
[All Consignee Fields Empty? Name, Address, City/State/Postal]
The consignee name is spaces AND address data is spaces AND city/state/postal data is spaces AND contact data is spaces → The system identifies this as a completely empty consignee record requiring all mandatory field error messages
[Generate Consignee Name Required Error GCCS-E-GEN-CONSIGNEE-REQ]
The consignee name field is spaces → The system generates a consignee required error message using error code GCCS-E-GEN-CONSIGNEE-REQ
[Generate Address Required Error GCCS-E-GEN-REQUIRED-N301]
The address field is spaces → The system generates an address required error message using error code GCCS-E-GEN-REQUIRED-N301
[Generate City Required Error GCCS-E-GEN-REQUIRED-N401]
The city field is spaces → The system generates a city required error message using error code GCCS-E-GEN-REQUIRED-N401
[Generate State Required Error GCCS-E-GEN-REQUIRED-N402]
The state/province field is spaces → The system generates a state required error message using error code GCCS-E-GEN-REQUIRED-N402
[Generate Postal Required Error GCCS-E-GEN-REQUIRED-N403]
The postal code field is spaces → The system generates a postal code required error message using error code GCCS-E-GEN-REQUIRED-N403
[Generate Country Required Error GCCS-E-GEN-REQUIRED-N404]
The country field is spaces → The system generates a country required error message using error code GCCS-E-GEN-REQUIRED-N404
[Add Error Messages to Message Array]
The message index is less than 10 → The system adds each error message to the message array and increments the message index
[Set Return Error Flag]
Error messages exist for the consignee record → The system sets the return status to error to indicate validation failure
[N4 Address Data Present?]
The system checks if the N4 address data fields contain any information → If N4 address data is empty, skip all address validations and complete processing, otherwise proceed with address field validations
[City Name Empty?]
The city name field is empty or contains only spaces → Generate a required field error message for city name (GCCS-E-GEN-REQUIRED-N401)
[City Length < 2 Characters?]
The city name contains fewer than 2 non-space characters → Generate a minimum length error message requiring at least 2 characters (GCCS-E-GEN-MIN-LEN2-REQ)
[Postal Code Length < 3 Characters?]
The postal code contains fewer than 3 non-space characters → Generate a minimum length error message requiring at least 3 characters (GCCS-E-GEN-MIN-LEN3-REQ)
[State/Province Code Empty?]
The state or province code field is empty or contains only spaces → Generate a required field error message for state/province code (GCCS-E-GEN-REQUIRED-N402)
[Valid State-Country Match?]
The state/province code does not exist in the state-country lookup table for the specified country → Generate an invalid state/province code error message (GCCS-E-INVALID-N402)
[Country Code Empty?]
The country code field is empty and cannot be auto-assigned from state/province code → Generate a required field error message for country code (GCCS-E-GEN-REQUIRED-N404)
[City Name Present?]
The city name field is empty or contains only spaces → The system should generate a required city name error message
[City Name Length >= 2?]
The city name has fewer than 2 characters after removing trailing spaces → The system should generate a minimum length requirement error message
[Postal Code Length >= 3?]
The postal code has fewer than 3 characters after removing trailing spaces → The system should generate a postal code minimum length requirement error message
[State/Province Present?]
The state or province code field is empty or contains only spaces → The system should generate a required state/province error message
[Valid State-Country Combination?]
The state/province code does not exist in the state-country lookup table for the specified country → The system should generate an invalid state/province code error message
[Country Code Present?]
The country code field is empty or contains only spaces after all processing → The system should generate a required country code error message
[Generate Error Message]
The validation process determines the state/province code is invalid → The system generates an error message indicating invalid state/province code and adds it to the message collection
[Set Valid Province Flag]
The shipper state/province code is validated against the state-country lookup table → If valid, the corresponding country code is assigned to shipper country field, otherwise an error message is generated for invalid shipper state/province code
[Set Valid Province Flag]
The consignee state/province code is validated against the state-country lookup table → If valid, the corresponding country code is assigned to consignee country field, otherwise an error message is generated for invalid consignee state/province code
[Validate Communication Number Qualifier]
The communication number qualifier is provided and is not blank, 'FX' (fax), or 'TE' (telephone) → Throw error: indicating invalid communication qualifier value
[Generate Error: Communication Qualifier Required]
The communication number qualifier is blank or spaces → Throw error: requiring communication qualifier
[Generate Error: Communication Number Required]
The communication number is blank or spaces → Throw error: requiring communication number
[All N1 Data Empty?]
The system validates the N1 segment data completeness → Generate required field error messages for name (N102), address (N301), city (N401), state/province (N402), postal code (N403), country (N404) AND add each error message to the validation results
[Entity ID Missing but Address Data Present?]
The system validates entity ID requirements → Generate error message indicating entity ID is required
[Name Missing but Entity ID Present?]
The system validates name field requirements → Generate error message indicating name is required
[Entity ID Present but Name Missing?]
The system validates the relationship between entity ID and name → Generate error message indicating name is required
[Invalid Entity ID Value?]
The system validates entity ID values for non-primary records → Generate error message indicating invalid entity ID value
[Entity ID Present but Address Missing?]
The system validates address field requirements → Generate error message indicating address is required
[City Name Length < 2?]
The system validates city name length requirements → Generate error message indicating minimum 2 characters required
[Postal Code Length < 3?]
The system validates postal code length requirements → Generate error message indicating minimum 3 characters required
[State/Province Missing?]
The system validates state/province requirements for North American countries → Generate error message indicating state/province is required
[Invalid State/Country Combination?]
The system validates state/province and country code combination → Generate error message indicating invalid state/province code
[Contact Name Present but Communication Qualifier Missing?]
The system validates communication qualifier requirements for contact information → Generate error message indicating communication qualifier is required
[Communication Number Present but Communication Qualifier Missing?]
The system validates communication qualifier requirements for communication number → Generate error message indicating communication qualifier is required
[Invalid Communication Qualifier Value?]
The system validates communication qualifier values → Generate error message indicating invalid communication qualifier value
[Communication Qualifier Present but Communication Number Missing?]
The system validates communication number requirements → Generate error message indicating communication number is required
[Address Data Present?]
If the N4 segment data for presence of address fields → If N4 data is empty or spaces, skip validation; otherwise proceed with state-country validation
[Add Error Message to Validation Results]
The system processes the error for reporting → The error message is retrieved using Z400-RETRIEVE-ERR-MSG and added to the message array using Z100-ADD-MESSAGE
[Retrieve Error Message Text from MS Table]
The system attempts to retrieve the error message text from the MS table using the error message number → The system should lookup the message text in the MS table and store the retrieved English text for display
[Check Message Index Limit]
The current message index is checked against the maximum limit of 10 → If the index is less than 10, the message should be added; otherwise, the message should be skipped to prevent array overflow
[Add Message to Error Array]
The system adds the error message to the array → The message should be stored in the array at the current index position, the error number should be stored in the corresponding error number array, the message index should be incremented by 1, and the return error flag should be set to indicate an error condition
[Required Field Missing]
The shipper name field is validated → If the shipper name is blank or spaces, an error message for invalid shipper name should be generated and added to the error collection
[Required Field Missing]
The consignee name field is validated → If the consignee name is blank or spaces, an error message for invalid consignee name should be generated and added to the error collection
[Required Field Missing]
The origin station name is validated → If the origin station name is blank or spaces, an error message for invalid origin station name should be generated and added to the error collection
[Required Field Missing]
The destination station name is validated → If the destination station name is blank or spaces, an error message for invalid destination station name should be generated and added to the error collection
[Required Field Missing]
The origin province state code is validated → If the origin province state code is blank or spaces, an error message for invalid origin province state code should be generated and added to the error collection
[Invalid Manifest Port]
The system looks up the manifest port in the MC table → If the manifest port is not found in the MC table, an error message for invalid manifest port should be generated and added to the error collection
[Invalid Customs Code]
The Canadian customs code is validated → If the Canadian customs code equals '00000', an error message for invalid Canadian customs code should be generated and added to the error collection
[Invalid Entity ID]
The conveying car is validated using the car validation system → If the car validation returns all asterisks indicating an invalid car, an error message for invalid conveying car should be generated using the original car value as the message number
[Invalid State/Country Combination]
The system validates the province state code against the state-country lookup table → If no matching country is found for the province state code, an error message for invalid shipper province state code should be generated using the province state code as the message number
[Invalid State/Country Combination]
The system validates the province state code against the state-country lookup table → If no matching country is found for the province state code, an error message for invalid consignee province state code should be generated using the province state code as the message number
[Missing Address Information]
The sub-location code is validated against business rules → If the sub-location code is missing and none of the exemption conditions are met (CSA indicator on, same manifest ports not IIS-A6, US destination, or arrival indicator Y), an error message for invalid destination station sub-location code should be generated
[Invalid Entity ID]
The date calculation system processes the waybill date → If the date calculation fails, an error message for invalid waybill date should be generated and added to the error collection
[Required Field Missing]
The N102 name field is checked for completeness → If the N102 name field is blank or spaces, an error message for required N102 field should be generated and added to the error collection
[Required Field Missing]
The N101 entity ID field is validated → If the N101 entity ID field is blank or spaces while other segment data exists, an error message for required N101 field should be generated and added to the error collection
[Invalid Entity ID]
The entity ID value is checked against valid values → If the entity ID is not in the valid values list or is SH (shipper), CN (consignee), or CB (customs broker), an error message for invalid N101 value should be generated and added to the error collection
[Missing Address Information]
The N301 address information field is validated → If the N301 address information field is blank or spaces, an error message for required N301 field should be generated and added to the error collection
[Required Field Missing]
The N401 city name field is validated → If the N401 city name field is blank or spaces, an error message for required N401 field should be generated and added to the error collection
[Minimum Length Not Met]
The length of the city name is validated → If the city name has fewer than 2 non-space characters, an error message for minimum length 2 required should be generated and added to the error collection
[Minimum Length Not Met]
The length of the postal code is validated → If the postal code has fewer than 3 non-space characters, an error message for minimum length 3 required should be generated and added to the error collection
[Required Field Missing]
The N402 state province code field is validated → If the N402 state province code field is blank or spaces, an error message for required N402 field should be generated and added to the error collection
[Invalid State/Country Combination]
The combination is validated against the state-country lookup table → If no valid combination is found in the lookup table, an error message for invalid N402 should be generated and added to the error collection
[Required Field Missing]
The N404 country code field is validated → If the N404 country code field is blank or spaces, an error message for required N404 field should be generated and added to the error collection
[Required Field Missing]
The PER03 communication number qualifier is validated → If the PER03 field is blank while PER02 name or PER04 communication number is provided, an error message for required PER03 field should be generated and added to the error collection
[Invalid Communication Qualifier]
The qualifier value is validated against approved values → If the PER03 value is not spaces, 'FX' (fax), or 'TE' (telephone), an error message for invalid PER03 value should be generated and added to the error collection
[Required Field Missing]
The PER04 communication number field is validated → If the PER04 field is blank while PER03 qualifier or PER02 name is provided, an error message for required PER04 field should be generated and added to the error collection
[Required Field Missing]
The lading quantity qualifier field is checked → If the lading quantity qualifier is blank or spaces, an error message for required N1010 field should be generated and added to the error collection
[Invalid Entity ID]
The qualifier is looked up in the MU table → If the qualifier is not found in the MU table, an error message for not found on MU should be generated and added to the error collection
[Required Field Missing]
The segment is validated for completeness → An error message for shipper required should be generated and added to the error collection
[Required Field Missing]
The segment is validated for completeness → An error message for consignee required should be generated and added to the error collection
[Error Message Retrieval Request]
The system needs to retrieve the corresponding error message text → The system should lookup the message text from the message table using the error number as the key
[Check if D5-ORG-ID Matches Target]
The system compares the D5-ORG-ID from the segment with the target organization ID → The organization IDs are evaluated for exact match
[Extract Business Address Line 1]
The system searches for BT address segments and finds address data → Extract address line 1 and address line 2 from BT segments, and if address line 1 is empty, set default value 'NA' for address line 1
[Set Default 'NA' Address]
BT address segments are not found or address line 1 is empty → Clear all address data fields and set address line 1 to default value 'NA'
[Clear Geographic Data]
BY geographic segments are not found → Clear all geographic data fields including city name, state/province code, postal code, and country code
[Set Default Address as 'NA']
The system needs to populate address fields → The N301 address field is set to 'NA' and the N302 address field is set to spaces
[Clear Address Fields]
The system needs to populate location fields → All location fields (city name, state/province code, postal code, country code) are set to spaces
[Validate N1 Segment Data]
The system validates the segment data → All required fields are checked for completeness and validity according to customs requirements
[Set Geographic Data to Spaces]
The geographic address segment (GA) is not found in the EDI data → All geographic data fields (N401, N402, N403, N404) are set to spaces
[Validate N1 Segment Data]
The entity has address, city/state, or contact information but missing entity ID or name, or entity ID is invalid for sequences greater than 2 → The system generates appropriate error messages for missing entity ID, missing name when entity ID exists, or invalid entity ID values for non-shipper/consignee/broker entities
[Validate N1 Segment Data]
The address information is missing → The system generates an error message indicating address information is required
[Validate N1 Segment Data]
The city name is provided but has less than 2 characters → The system generates an error message indicating minimum 2 character length requirement
[Validate N1 Segment Data]
The postal code is provided but has less than 3 characters → The system generates an error message indicating minimum 3 character length requirement
[Validate N1 Segment Data]
The state/province code is missing or the state/province and country combination is invalid → The system generates error messages for missing state/province or invalid state/province combinations, and derives country code from state/province when country is missing
[Validate N1 Segment Data]
The country code is missing after state/province validation → The system generates an error message indicating country code is required
[Validate N1 Segment Data]
Communication number qualifier is missing but contact name or communication number is provided, or communication number qualifier is invalid, or communication number is missing when qualifier or contact name is provided → The system generates appropriate error messages for missing communication number qualifier, invalid qualifier values (must be spaces, 'FX', or 'TE'), or missing communication number
[Generate Validation Error Messages]
The system processes validation results → Error messages are retrieved from the message table and added to the error collection
[Set Default 'NA' if Address Missing]
The system processes address fields → Address line 1 is set to 'NA' as default value
[Check Required Fields]
The system checks required fields → Entity ID, name, and address line 1 are verified as non-empty, and error messages are generated for missing required fields
[Validate State/Country Combination]
The system validates the state-country combination → State/province code is verified as valid for Canada, USA, or Mexico, and error messages are generated for invalid combinations
[City Name >= 2 Characters?]
The city name length is validated → If the city name has fewer than 2 characters, a minimum length error message is generated
[EDI BOL has Importer Segment?]
The system searches for importer segment data in the EDI BOL → The system determines if an importer segment with entity ID 'IM' exists and sets the appropriate processing flag
[AU Table has Importer Data?]
The system queries the AU table for matching importer records → The system determines if AU table contains valid importer data and sets the AU importer found flag accordingly
[Process Address Information]
The system processes address information and address line 1 is spaces or low-values → The system sets address line 1 to 'NA' and copies address line 2, otherwise copies both address lines as provided
[Set Default 'NA' if Address Missing]
The system processes address information → The system clears N3 data fields and sets address line 1 to 'NA'
[Validate Business Number and Qualifier]
The system validates the business number and qualifier combination → If both AU table importer and record 55 importer are found and business number qualifier is 'BN' or spaces, the CSA indicator is turned off
[No Backup Data Available?]
The system checks for availability of backed up importer data → If backed up importer name is present, proceed with data restoration, otherwise clear importer fields
[Importer Data Exists in Input Parameters?]
The system checks input parameters for importer data → If importer name, business number, and business number qualifier are all present, proceed to search existing records, otherwise skip backup processing
[Process Importer Address from N3 Segment]
The system processes the N3 segment for importer address → The system sets address line 1 to 'NA' if the address is blank or low-values, otherwise uses the provided address, and sets address line 2 from the segment data
[Validate N1 Segment Data]
The system validates the N1 segment information → The system performs comprehensive validation including entity ID, name, address, city/state, and contact information requirements
[N3 Segment Found?]
The system checks if the N3 segment was found → The system should proceed with address extraction if found, otherwise use default address processing
[Address Line 1 Empty?]
The system checks if address line 1 is empty or contains only spaces or low-values → The system should set a default value if empty, otherwise keep the original value
[Clear All N4 Data Fields]
The N4 segment is not found or retrieval fails → The system clears all N4 data fields in the customs record (GCSCCS55-N4-DATA)
[Set Invalid Waybill Date Error]
The system processes the failed calculation result → An invalid waybill date error code is set for message retrieval
[Retrieve Error Message Text]
The system needs to provide error details → The error message retrieval process is performed to get the descriptive error text
[Add Error to Message Queue]
The system processes the error condition → The error message is added to the message queue for user notification
[Set Error Message: Invalid Manifest Port Canadian Customs Code]
The system detects this invalid customs code → The system generates an error message for invalid manifest port Canadian customs code and adds it to the message array
[Set Error Message: Invalid Manifest Port in MC Table]
The MC table lookup fails to find a matching record → The system generates an error message for invalid manifest port and adds it to the message array
[Log Error - Invalid Manifest Port]
The system attempts to look up the manifest from port in the MC table and the lookup fails → The system clears the MC table data and logs an error message for invalid manifest port
[Extract US Port Exit Code from MC Table]
The Canadian customs code in the MC table record equals '00000' → The system clears the MC table data and adds an error message for invalid Canadian customs code
[Generate Sub-location Error Message]
System validates sub-location requirements → Generate error message for invalid destination station sub-location code
[Generate Sub-location Error Message]
The system processes the error condition → An error message for invalid destination station sub-location code is retrieved and added to the message list
[Generate Sub-location Error Message]
The system processes the error condition → Generate and add error message for invalid destination station sub-location code to the message collection
[Generate Invalid Car Error Message]
The system processes the validation failure → Generate an invalid conveying car error message using the original car value and add it to the message collection
[Validate Quantity Qualifier Against MU Table]
The quantity qualifier is looked up in the MU (Measurement Unit) table → If qualifier is not found in MU table, generate error message indicating qualifier is not valid
[Validate Quantity Qualifier Against MU Table]
Quantity qualifier is blank or spaces → Generate error message indicating quantity qualifier is required
[Set Entity Address to 'NA']
The entity address line 1 field is empty or contains only spaces → The system shall set the entity address line 1 to 'NA'
[Generate Invalid State Error Message]
The state/province code is not found in the state-country lookup table → An invalid shipper province/state code error message is generated
[Generate Invalid State Error Message]
The state/province code is not found in the state-country lookup table → An invalid consignee province/state code error message is generated
[Check CCN Array from EDI BOL]
The system checks the CCN array table from GCWCBOL → The system determines if the CCN array contains valid data or is empty/low-values
[Keep Current Settings]
The sub-location error flag is set indicating an invalid sub-location code → An error message for invalid destination station sub-location code should be added to the message list
[Generate Error Message: Invalid Destination Station Sub-location Code]
The sub-location error flag is set → An error message 'Invalid Destination Station Sub-location Code' is generated and retrieved from the message table
[Add Error to Message Array]
The error message needs to be communicated to the user → The error message is added to the message array and the return status is set to ERROR
[Restore Original Data on Error]
The system handles the retrieval failure → The system restores the saved cargo manifest record, cargo description segments, and clears all description array elements, then restores the saved description array data
[Restore Original Data if Error]
The system needs to handle the enhancement failure → The original manifest data is restored from working storage: WS-SAVE-GCSCCRT to GCSCCRT, WS-SAVE-GCSCCS52 to GCSCCS52, and all 46 saved cargo description segments are restored to WS-GCSCCS53-DATA array
[Generate Error for Invalid Customs Code]
The system validates the customs code → The system generates an error message indicating invalid manifest port Canadian customs code
[MC Table Lookup Successful?]
The MC table lookup is unsuccessful → Clear the MC table segment data and set error flag 3 to ON with the station name saved for error reporting
[Validate Canadian Customs Code]
The system validates the Canadian customs code → If the Canadian customs code equals '00000', clear the MC table segment data and set error flag 2 to ON with the station name saved for error reporting
[Check and Report Manifest-To Errors]
The system checks for any manifest-to related errors → If error flag 1 is ON, generate invalid manifest upon error message; if error flag 2 is ON, generate invalid Canadian customs code error message with station name; if error flag 3 is ON, generate invalid manifest port MC error message with station name
[Check for Valid EDI BOL]
The system checks for valid EDI BOL data by verifying origin road number is not zero and retrieving shipment mining segment E1 → The system sets EDI BOL availability status and extracts EDI BOL key if data is found
[Set Weight to Zero]
The system attempts to process weight information → The system sets the commodity weight counter to zero
[Check for Valid EDI BOL]
The system checks for EDI BOL availability by verifying origin road number is not zero → The system should set EDI BOL validity flag and extract BOL key from shipment mining data if available
[Set Weight to Zero]
The system cannot find weight data for the commodity segment → The system should set the commodity weight counter to zero
[Validate Final Weight Value]
The system validates the final calculated weight → The system should use the calculated weight if greater than zero, otherwise set default weight to 1
[Check EDI BOL Data Availability]
The system needs to retrieve weight and quantity information → The system should first check if EDI BOL data is available by validating the origin road number and retrieving the EDI BOL key
[Quantity Qualifier Empty?]
The quantity qualifier field is empty or contains only spaces → The system generates a required field error message and adds it to the error collection
[Generate Not Found Error]
The lookup operation fails to find a matching record → The system generates a 'not found on MU table' error message and adds it to the error collection
[Validate Shipper Record Data]
The system validates shipper record completeness → All required fields are checked for presence and validity according to customs manifest requirements
[Build NN Entity Segments]
NN entity data is found in EDI BOL segments AND entity ID code is valid according to predefined entity ID values → Extract NN entity name, address from GC segments, city/state/postal/country from GA segments to create NN segment with validated entity ID, OR reset variables if entity not found or invalid
[Set Default Address Values]
Address line 1 is spaces or not provided → Set address line 1 to 'NA' as default value to maintain data integrity
[Validate All N1 Segments]
Entity name, address, city, state, postal code or country information is missing → Generate appropriate error messages for missing required fields including entity ID, name, address line 1, city, state/province, postal code and country code
[Validate All N1 Segments]
Entity ID code is provided but not in valid entity ID list:
is shipper, consignee
customs broker type
→ Generate error message for invalid entity ID value
[Validate All N1 Segments]
City name has less than 2 characters:
postal code has less than 3 characters
contact qualifier is provided without contact number
contact number is provided without qualifier
→ Generate appropriate error messages for minimum length requirements and incomplete contact information
[Validate All N1 Segments]
State/province code is missing:
state/province code is invalid for the specified country
→ Generate error message for missing or invalid state/province code, OR auto-assign country code when state/province is provided but country is missing
[Set Default 'NA' for Address]
The system processes stuffer address information → Address line 1 is set to 'NA' and address line 2 is set to spaces
[Validate N1 Segment Data]
The system validates the complete stuffer entity segment → All required fields are validated and error messages are generated for any missing or invalid data
[Set Default Address to 'NA']
The system processes address information → Address line 1 is set to 'NA' and address line 2 is set to spaces
[Clear City/State/Postal Fields]
The system processes geographic information → City name, state/province code, postal code, and country code fields are set to spaces
[Validate Entity Segment Data]
The system validates the entity segment → All required fields are validated according to entity segment validation rules including entity ID, name, address, and contact information requirements
[Set Default Address to 'NA']
Processing beneficial owner address information → The address line 1 is set to 'NA' (Not Available) as default value
[Validate BN Segment Data]
Validating the beneficial owner segment → The segment data is validated according to business rules for entity segments
[Validate C1 Segment Data]
The C1 segment needs to be validated before insertion → The N1 segment validation routine is performed to check required fields and data formats
[Transportation Segment Found?]
Checking if transportation segment data is available → Processing continues if segment found, otherwise notify party processing ends
[Address Segment Found?]
Checking if address data is available → Address processing continues if T2 segment found, otherwise skip to city/state processing
[City/State Segment Found?]
Checking if city/state data is available → City/state processing continues if TA segment found, otherwise skip to contact processing
[Contact Segment Found?]
Checking if contact data is available → Contact processing continues if T3 segment found, otherwise skip to address defaulting
[Set Default Address if Missing]
The first address line is empty or spaces → The first address line is set to 'NA' as a default value
[Validate N1 Segment Data]
Validating the segment before database insertion → All required fields are validated and any validation errors are recorded
[MCOA Segment Found?]
The system checks if segment data exists and type equals 'OT' → Processing continues if segment is found, otherwise moves to next sequence
[Address Data Found?]
The system checks if MCOA ON segment data exists → Address processing continues if data is found, otherwise default address is set
[City/State Data Found?]
The system checks if MCOA OC segment data exists → Geographic data processing continues if found, otherwise fields are cleared
[Validate Entity Segment]
Entity segment validation is performed → The segment is validated according to N1 segment validation rules
[Validate Entity ID Code]
The system validates the entity ID code against the list of valid entity values → Only entities with valid ID codes (specific predefined values) are processed and invalid entities are skipped
[Are all required fields empty?]
The segment has empty name AND empty address data AND empty city/state data AND empty contact information → Generate required shipper error for sequence 1 or required consignee error for sequence 2
[Entity ID present but Name missing?]
The entity ID code is not empty AND the entity name is empty → Generate a required name error message
[Address data present but Entity ID/Name missing?]
The entity ID code is empty:
the entity name is empty
→ Generate required entity ID error if ID is missing AND generate required name error if name is missing
[Entity ID is invalid type?]
The entity ID code is not empty AND the entity ID is not a valid entity type:
is a shipper code
is a consignee code
is a customs broker code
→ Generate an invalid entity ID value error message
[Address missing when Entity ID present?]
The address information field is empty → Generate a required address error message
[City name missing?]
The city name field is empty → Generate a required city name error message
[City name too short?]
The city name length is less than 2 characters → Generate a minimum length requirement error message
[Postal code too short?]
The postal code length is less than 3 characters → Generate a postal code minimum length error message
[State missing?]
The state or province code is empty → Generate a required state/province error message
[Invalid State/Country combination?]
The state/province code is not found in the state-country lookup table for the specified country → Generate an invalid state/province code error message
[Country code missing?]
The country code field is empty → Generate a required country code error message
[Contact qualifier invalid?]
The communication qualifier is not empty AND not 'FX' (fax) AND not 'TE' (telephone) → Generate an invalid communication qualifier error message
[Contact number missing when required?]
The communication qualifier is not empty:
the contact name is not empty AND the communication number is empty
→ Generate a required communication number error message
[Entity ID Missing but Address/Contact Present?]
The entity ID code is empty AND (address information is not empty:
location information is not empty
contact information is not empty)
→ Generate an error indicating entity ID code is required
[Name Missing but Address/Contact Present?]
The entity name is empty AND (address information is not empty:
location information is not empty
contact information is not empty)
→ Generate an error indicating entity name is required
[Entity ID Present but Name Missing?]
The entity ID code is not empty AND the entity name is empty → Generate an error indicating entity name is required
[Invalid Entity ID Value?]
The entity ID code is not empty AND the entity ID is not a valid entity type AND the entity ID is not 'SH' (shipper) AND the entity ID is not 'CN' (consignee) AND the entity ID is not 'CB' (customs broker) → Generate an error indicating invalid entity ID value
[Entity ID Present but Address Missing?]
The entity ID code is not empty AND the primary address line is empty → Generate an error indicating address information is required
[City Name Missing?]
Location information is not empty AND city name is empty → Generate an error indicating city name is required
[City Name Length < 2?]
City name is not empty AND city name length is less than 2 characters → Generate an error indicating minimum length of 2 characters is required
[Postal Code Length < 3?]
Postal code is not empty AND postal code length is less than 3 characters → Generate an error indicating minimum length of 3 characters is required
[Country is CA/US/MX and State Missing?]
Country code is 'CA' (Canada):
'US' (United States)
'MX' (Mexico) AND state/province code is empty
→ Generate an error indicating state/province code is required
[Invalid State/Country Combination?]
State/province code and country code combination is not found in the state-country reference table → Generate an error indicating invalid state/province code for the specified country
[Country Code Missing?]
Location information is not empty AND country code is empty → Generate an error indicating country code is required
[Contact Name Present but Qualifier Missing?]
Contact person name is not empty AND communication number qualifier is empty → Generate an error indicating communication number qualifier is required
[Communication Number Present but Qualifier Missing?]
Communication number is not empty AND communication number qualifier is empty → Generate an error indicating communication number qualifier is required
[Invalid Communication Qualifier Value?]
Communication number qualifier is not empty AND qualifier is not 'TE' (telephone) AND qualifier is not 'FX' (fax) AND qualifier is not spaces → Generate an error indicating invalid communication qualifier value
[Qualifier or Name Present but Number Missing?]
(Communication number qualifier is not empty:
contact person name is not empty) AND communication number is empty
→ Generate an error indicating communication number is required
[N4 Address Data Present?]
The system checks if the N4 address data field contains any information → If N4 data is empty or spaces, skip address validation; otherwise proceed with validation
[Generate Invalid State/Province Error]
The validation process determines the combination is invalid → Generate error message indicating invalid state/province code for the country
[Generate Required State/Province Error]
The validation process checks for required state/province code → Generate error message indicating state/province code is required
[Generate Required Country Code Error]
The validation process completes country code determination → Generate error message indicating country code is required
[Build NN Entity Segments]
Processing NN entity segments from EBSNRSC data source and entity ID is valid → Extract entity name and consignee chop code, address information from GC type, city/state/postal/country from GA type, then create NN entity record with default 'NA' address if address is blank
[Set Default Address Values]
Processing any entity segment address data → Set address line 1 to 'NA' if blank and leave address line 2 as spaces
[Set Default NA for Missing Address]
Shipper name is spaces:
consignee name is spaces
→ Add error message for invalid shipper name when shipper name is missing AND add error message for invalid consignee name when consignee name is missing
[Entity has State/Province Code?]
The system processes the entity's location information → The system should check if the entity has a valid state or province code before proceeding with country lookup
[Entity ID or Name missing but other data present?]
Entity ID is missing or empty → Generate entity ID required error message
[Entity ID or Name missing but other data present?]
Name is missing or empty → Generate name required error message
[Entity ID present but Name missing?]
Name field is missing or empty → Generate name required error message
[Entity ID invalid or restricted type?]
Entity ID is not in valid values list or is a restricted type (SH, CN, BN) → Generate invalid entity ID value error message
[Entity ID present but Address missing?]
Address information is missing or empty → Generate address required error message
[City name missing?]
City name is missing or empty → Generate city name required error message
[City name too short?]
City name length is less than 2 characters → Generate minimum length requirement error message
[Postal code too short?]
Postal code length is less than 3 characters → Generate postal code minimum length requirement error message
[State/Province missing?]
State or province code is missing or empty → Generate state/province required error message
[State/Country combination invalid?]
State/province code does not belong to the specified country based on lookup table → Generate invalid state/country combination error message
[Country code missing?]
Country code is missing or empty after auto-assignment attempt → Generate country code required error message
[Contact qualifier missing but name present?, Contact qualifier missing but number present?]
Contact communication qualifier is missing or empty → Generate contact qualifier required error message
[Contact qualifier invalid?]
Contact qualifier is not spaces, 'FX', or 'TE' → Generate invalid contact qualifier value error message
[Contact number missing but qualifier/name present?]
Contact communication number is missing or empty → Generate contact number required error message
[Entity ID Code Present?]
The entity identification code field is empty or spaces → Generate a required entity ID error message
[Entity ID Code Present?]
The entity name field is empty or spaces → Generate a required entity name error message
[Entity ID in Allowed Values?]
The entity identification code is present but not in the list of valid entity types → Generate an invalid entity type error message
[Address Information Requirement Validation - Validate that address information is provided when entity ID and name are present]
The entity ID is not spaces AND the entity name is not spaces AND the address line 1 is spaces → The system generates an error message indicating that address information is required
[City Name Length Validation - Validate city name has minimum 2 character length requirement]
The system validates the city name length → If the city name has fewer than 2 characters, generate a minimum length requirement error message and add it to the error queue
[City Name Present?]
The system checks for city name presence → If city name is spaces, skip length validation and continue processing
[Generate Min Length Error Message]
The minimum length validation fails → Generate error message with code GCCS-E-GEN-MIN-LEN2-REQ indicating minimum 2 character length requirement
[Add Error to Message Queue]
The error needs to be recorded → Add the error message to the message queue if there are fewer than 10 messages already queued
[Retrieve Error Message GCCS-E-GEN-MIN-LEN3-REQ]
The system needs to provide error feedback → The system should retrieve the standard minimum length error message
[Add Validation Error Message to Error Collection]
The system processes the validation failure → The system should add the error message to the validation error collection
[State/Province Code Present?]
The state or province code field is empty or contains only spaces → The system should generate a required state/province error message and add it to the validation error list
[Valid State/Province for Country?]
The state/province code is validated against the country using the state-country lookup table → If the state/province code is not valid for the specified country, the system should generate an invalid state/province error message
[Continue Validation]
The country code field is empty or contains only spaces → The system should generate a required country code error message and add it to the validation error list
[State/Province Code Present?]
The state or province code field is empty or spaces → Generate a required state/province code error message
[Generate Required Country Code Error]
The country code field is empty or spaces and cannot be determined from state/province lookup → Generate a required country code error message
[PER03 Qualifier Empty AND Contact Name NOT Empty?]
The communication number qualifier (PER03) is empty AND the contact person name (PER02) is not empty → Throw error: indicating that communication qualifier is required
[PER03 Qualifier Empty AND Communication Number NOT Empty?]
The communication number qualifier (PER03) is empty AND the communication number (PER04) is not empty → Throw error: indicating that communication qualifier is required
[PER03 Qualifier Valid? Blank, FX, or TE]
The communication number qualifier (PER03) is not blank, 'FX', or 'TE' → Throw error: indicating invalid qualifier value
[Communication Qualifier NOT Empty OR Contact Name NOT Empty?]
The communication number qualifier (PER03) is not empty:
the contact person name (PER02) is not empty AND the communication number (PER04) is empty
→ Throw error: indicating that communication number is required
[Contact Name Present?]
Contact name is not blank AND communication qualifier is blank → System generates required communication qualifier error message
[Communication Number Present?]
Communication number is not blank AND communication qualifier is blank → System generates required communication qualifier error message
[Communication Qualifier Valid?]
Communication qualifier is not blank AND not 'FX' AND not 'TE' → System generates invalid communication qualifier value error message
[Validate Field Length Requirements]
The actual string length of the city name is less than 2 characters → The system generates a minimum length requirement error message
[Validate Field Length Requirements]
The actual string length of the postal code is less than 3 characters and postal code is not empty → The system generates a minimum length requirement error message
[Communication Number Qualifier Present?, Contact Name Present?]
The communication number field is empty → Generate error message indicating communication number is required
[Error Message Text Retrieval - Retrieve error message text from MS table for validation failures]
The system needs to retrieve the corresponding error message text → The system should lookup the message text from the MS table using the error number as key and return the English text for display
[Set Message Error Number as Key]
The system configures the search key for message retrieval → The error message number should be assigned as the sequence ID key for table lookup
[Check Entity ID is 'IM']
The system checks the entity ID code → Processing continues only if entity ID equals 'IM' for importer
[Validate N1 Segment Data]
The system validates the N1 segment information → The system ensures required fields are present and data meets customs requirements
[Set Default Address to 'NA']
The system needs to populate address information → Address line 1 is set to 'NA' and all other address fields are cleared
[Validate Importer Segment Data]
The system validates the importer record → The system performs validation checks on entity ID, name, address, geographic, and contact information fields
[EDI BOL Importer Data Found?]
The system checks the retrieval status → The system determines if importer data is available or if corrector EDI deleted the importer
[Entity ID = 'IM' Importer?]
The system validates the entity type → The system confirms if the entity ID equals 'IM' indicating an importer
[N3 Address Data Found?]
The system checks the retrieval status → The system determines if N3 address segment data is available
[N4 City/State Data Found?]
The system checks the retrieval status → The system determines if N4 city/state segment data is available
[Validate N1 Segment Data]
The system validates the segment → All required fields are validated according to customs requirements and business rules
[Business Number Qualifier BN or Blank?]
The system checks if business number qualifier is 'BN' or blank → If qualifier is 'BN' or blank, turn off CSA indicator, otherwise maintain current status
[Address Line 1 Empty?]
The system validates the address completeness → If Address Line 1 is empty or contains only spaces/low-values, set it to 'NA'; otherwise use the extracted value
[Generate Validation Error Messages]
Required contact fields are missing or invalid → Appropriate validation error messages are generated and added to the error message collection
[EBSBCKS Segment Found?]
The system checks if the segment was successfully retrieved → The process continues to check special handling code if segment found, otherwise moves to termination check
[N1 Segment Found?]
The EDI BOL interface returns a status code → If status code is spaces then N1 segment is found, otherwise N1 segment is not found
[Check Entity ID Code]
Checking the entity ID code in the N1 segment → The entity ID code should be extracted for validation
[Entity ID = 'IM'?]
The entity ID code is compared against importer designation → If entity ID equals 'IM' then it is a valid importer entity, otherwise it is not an importer
[N3 Address Found?]
The EDI BOL interface returns a status code → If status code is spaces then address segment is found, otherwise address segment is not found
[Extract Address Line 1]
Processing address information → Address line 1 should be extracted from D2-ADDL-NAME-ADDR-1 field and stored in customs record, or set to 'NA' if blank or low-values
[Set Default 'NA' Address]
Address information is required for customs record → Address line 1 should be set to 'NA' and N3 data section should be cleared
[N4 Segment Found?]
The EDI BOL interface returns a status code → If status code is spaces then city/state segment is found, otherwise city/state segment is not found
[Clear N4 Data]
City/state information processing is required → The N4 data section in customs record should be cleared to spaces
[Validate N1 Segment Data]
Validating the importer record for customs compliance → The system should Execute N1 segment validation to ensure data integrity
[Importer Data Present?]
The system checks for importer data in the input → Processing continues only if importer data is present, otherwise the backup process is skipped
[Business Number Present?]
The system validates the business number field → Processing continues only if business number is not spaces, otherwise backup process is terminated
[Address Line 1 Empty or Low Values?]
The first address line is empty or contains low values → The system should flag the address line as requiring default value assignment

As an EDI Gateway Service,
I want to orchestrate and execute all GCCCCARR EDI data mapping and validation logic,
So that I can ensure strict compliance with US Customs (P140) automated payload constraints in a single consolidated service.

Prerequisites & Setup

[Initialize Arrival Message Structure]
The system begins preparing the arrival message → The GCX148 input structure is initialized to clear any previous data

Core Acceptance Criteria

[7:Send Arrival Message]
The system sends the arrival message → The system should clear acceptance status, call CIMS to send the message, write message log entry, and purge the message from CIMS queue
[Set Security Parameters]
Security parameters need to be established → The security byte is set to HIGH-VALUE to indicate maximum security level
[Populate CCN Key]
The arrival message is being populated with identification data → The CCN key is moved to the train or US CCN field in the message structure
[Populate CCN Key]
Cargo type classification is required → The cargo type indicator is set to CA-CARGO to designate Canadian cargo
[Populate Action Code]
The arrival message requires action specification → The action code is moved from input to the message action code field
[Populate Port Code]
The arrival message requires location specification → The port code is moved from input to the message port code field
[Populate Date/Time]
The arrival message requires timestamp information → The date and time is moved from input to the message date-time field
[Prepare Message for Transmission]
The message needs to be prepared for external system transmission → The input structure is moved to the GCT1481E message field for transmission
[Copy Arrival Data to Message Format]
The system prepares the arrival message for processing → The message structure is initialized with high security level, cargo type set to Canadian cargo, and all arrival data is copied to appropriate message fields
[Send Message to GCX148 System]
The system sends the message to the cargo management system → The message is submitted to CIMS using the alternative PCB communication path with cleared acceptance status
[Write Message Log Entry]
The system processes the message submission → A log entry is written containing the message code, message content, message length, and module name
[Purge IMS Communication]
The system completes message processing → The IMS communication is purged using the alternative PCB to release system resources

Structural Validations

[2:Validate CCN Key]
The CCN key field is blank or contains only spaces → The system should Throw error: 'GCWCCAR-CCN-KEY IS BLANK' and invoke error handling
[3:Validate Action Code]
The action code field is blank or contains only spaces → The system should Throw error: 'GCWCCAR-ACTION-CODE IS BLANK' and invoke error handling
[4:Validate Port Code]
The port code field is blank or contains only spaces → The system should Throw error: 'GCWCCAR-PORT-CODE IS BLANK' and invoke error handling
[Check if Canada Customs Number key is provided and not blank]
The CCN key field is blank or contains only spaces → The system should Throw error: indicating the CCN key is blank and invoke error handling
[Set Error Message: 'GCWCCAR-CCN-KEY IS BLANK']
The validation check detects the missing CCN key → The system should set the error message to 'GCWCCAR-CCN-KEY IS BLANK'
[Call Error Handler]
The error condition needs to be processed → The system should call the error handler routine to manage the validation failure
[Check if action code is provided and not blank]
The action code field is blank or contains only spaces → The system should set an error message indicating the action code is blank and invoke error handling
[Set Error Message: 'Action Code is Blank']
The validation check fails → The system should set the error message to 'GCWCCAR-ACTION-CODE IS BLANK'
[Call Error Handler]
The error condition is detected → The system should call the error handling routine 'CERR' with the common communication area
[Check if port code is provided and not blank]
The port code field is blank or contains only spaces → The system should set an error message 'GCWCCAR-PORT-CODE IS BLANK' and invoke error handling
[Call Error Handler]
The error message has been set for the port code validation failure → The system should call the error handling routine 'CERR' with the common communication area

As an EDI Gateway Service,
I want to orchestrate and execute all GCCCCREL EDI data mapping and validation logic,
So that I can ensure strict compliance with US Customs (P140) automated payload constraints in a single consolidated service.

Prerequisites & Setup

[Initialize CIMS Session]
The message sending process begins → The system calls CIMS with CHNG parameter to initialize the messaging session

Core Acceptance Criteria

[Manifest Release Processing]
The system processes the manual release → The system sets message ID to GCW123, sets manual release flag to true, copies the CCN key, clears the release quantity field, and moves the release reason to comments
[Cargo Release Logging]
The system creates audit log entry → The system initializes logging input, sets action code to LOG-CARGO-RELEASE-REMOVED, and spawns GCT1051E message with security information, CCN key, cargo type CA-CARGO, transaction details, user ID and timestamp
[Release Notification Generation]
The operation is NOT an export operation → The system generates and sends GCT1231E notification message with release details
[Set Manual Release Flag]
The system processes a manual release request → The message ID should be set to GCW123 and the manual release flag should be set to true
[Copy Cargo Control Number]
The system processes the release request → The cargo control number key should be copied to the GCW123 message structure
[Copy Cargo Control Number]
The system prepares the release message → The release quantity field should be set to spaces (cleared)
[Generate Release Notification Message]
The cargo is not classified as export cargo → A release notification message (GCT1231E) should be generated and sent
[Create Cargo Release Removal Log]
All status updates and master manifest processing (if applicable) are complete → The system must create a cargo release removal log entry with action code LOG-CARGO-RELEASE-REMOVED and spawn the logging message (GCT1051E)
[Send Log Message to Audit System]
The system sends the log message to the audit system → The log entry is transmitted via GCT1051E message to the external audit system for processing
[Set Security Level to High]
The system initializes the security settings for the log message → The security byte must be set to high values to indicate maximum security level
[Populate Cargo Control Number]
The system prepares the audit log message → The cargo control number from the manifest record must be copied to the audit log train or US CCN field
[Set Cargo Type as Canadian]
The system sets the cargo type classification → The cargo type must be set to CA-CARGO to indicate Canadian cargo
[Format Log Message]
The system prepares to send the audit message → The complete audit input structure must be moved to the formatted log message structure
[Send Message to Audit Queue]
The system initiates message sending → The CIMS program must be called with CHNG function to send the message to the alternate PCB queue
[Write Message to Log]
The system writes the message to the log → The WRITMSGL program must be called with the message code, message content, message length, and module name
[Purge Message Queue]
The system completes message processing → The CIMS program must be called with PURG function to purge the message from the alternate PCB queue
[Set Message ID to GCW123]
The system prepares release notification message → The message ID is set to GCW123 and manual release flag is set to true
[Copy Cargo Control Number to Message]
The system processes cargo control information → The cargo control number from the release request is copied to the message CCN key field
[Clear Release Quantity Field]
The system sets up message fields → The release quantity field is cleared to spaces
[Copy Release Reason to Comments]
The system prepares the notification message → The release reason is copied to the message comments field
[Send Message via CIMS]
The system processes the notification request → The GCT1231E message is prepared, sent via CIMS, logged, and the message queue is purged
[Send Message to Queue]
The release operation is not an export type → The system sends a GCT1231E notification message through CIMS messaging system
[Prepare Message Content]
The message preparation process starts → The system copies GCX123-INPUT to GCT1231E-MSG and clears the accept status
[Send Message to Queue]
The actual message transmission occurs → The system calls WRITMSGL with message code, content, length and module name parameters
[Terminate CIMS Session]
The message transmission is complete → The system calls CIMS with PURG parameter to terminate the session
[Set Target Segment to Canadian Manifest Cargo]
The target segment needs to be identified → The system sets the target to Canadian manifest cargo segment (GCSCCRT)
[Set Function to Replace Record]
The update function type needs to be specified → The system sets the function to replace (REPL) the existing record

Structural Validations

[Manifest Data Retrieval]
The system attempts to retrieve the corresponding manifest data → The system loads the manifest record if found, or displays error message 'CAN NOT LOCATE MANIFEST FOR RELEASE/CANCEL RELEASE' if the manifest cannot be located
[Generate Error Message]
The manifest data is not found or not within valid range → An error message 'CAN NOT LOCATE MANIFEST FOR RELEASE/CANCEL RELEASE' is generated and error handling is invoked

As an EDI Gateway Service,
I want to orchestrate and execute all GCX122A EDI data mapping and validation logic,
So that I can ensure strict compliance with US Customs (P140) automated payload constraints in a single consolidated service.

Prerequisites & Setup

[4:Initialize Reference Data]
The system initializes reference data and processing flags → Set message label to 'TRAIN REPORT NUMBER :' for train transactions, 'CARGO CONTROL NUMBER :' for cargo transactions, or 'REFERENCE NUMBER :' for other types
[Initialize Test Message Indicators]
Test message indicators need to be reset → Both train test indicator and cargo test indicator must be cleared to spaces
[Initialize Communication Areas]
Communication areas need to be initialized → The system communication block (ISCOM) must be initialized to default values
[Initialize Message Indicators]
Message indicators and counters need to be initialized → WS-IND-TEXT is set to LINE-MESS-MIN, WS-IND-MST is set to LINE-MESS-MIN-MST, WS-IND-USER is set to ZERO, MST-INDX is set to ZERO, and WS-IND-ERR is set to ZERO
[Initialize AEI Work Table]
The system begins the AEI message process → The AEI work table structure is initialized to prepare for email recipient lookup
[Initialize MST Session]
Starting MST message transmission → The system calls SMSTONLY with call letters and header record to establish the session
[Initialize Arrival Message Structure]
The arrival processing begins → The arrival message structure is initialized to clear any previous data
[Initialize Message Structure]
The system begins preparing the arrival message → The message input structure is completely cleared of any previous data
[Initialize Error Message Variables]
The system begins DB2 error processing → The email subject and text fields are cleared to prepare for error message formatting
[Initialize Log Message Structure]
The system begins to create a log entry → The log message structure is cleared and initialized with spaces
[Initialize Message Processing Flags]
The system initializes message processing flags → SW-PROCESS-MST is set to TRUE, SW-PROCESS-MERLIN is set to TRUE, SW-NOT-TRAIN-ERROR is set to TRUE, and SW-NOT-CARGO-ERROR is set to TRUE
[Initialize Message Indicators]
The system sets up message indicators → WS-IND-TEXT is set to LINE-MESS-MIN, WS-IND-MST is set to LINE-MESS-MIN-MST, WS-IND-USER is set to ZERO, MST-INDX is set to ZERO, and WS-IND-ERR is set to ZERO
[Initialize Message Indicators]
Message indicators need to be set up → WS-IND-TEXT is set to LINE-MESS-MIN and WS-IND-MST is set to LINE-MESS-MIN-MST

Core Acceptance Criteria

[Message Type?]
If the message type → Route to acknowledgment processing for ACK messages, or route to error processing for ERROR and WARNING messages
[5:Process Acknowledgment Messages]
The system processes the acknowledgment → Set MST processing flag to false and route to train or cargo acknowledgment processing based on transaction type
[6:Process Train Acknowledgment]
The system looks up the train report → If train not found, set error flag and add error message; if found, clear security errors for deleted records, set ACK status with timestamp, and send AEI notification if flag is 'Y'
[7:Process Cargo Acknowledgment]
The system looks up the cargo control record → If cargo not found, add error message and set DCP interface error flag; if found, set status to 'ACK' when current status is 'SENT', determine processing terminal, and process arrival if indicator is 'Y'
[12:Update Train/Cargo Status]
The system updates the record status → If error type is 'X', set status to 'WARNING' or 'INFO' and exit; for train records not deleted, set error resend flag and status to 'REJECT' for type 'R' or 'ERROR' otherwise; for cargo records, set status to 'REJECT' for type 'R' or 'ERROR' otherwise
[13:Handle Test Messages]
The system processes the test message → Set appropriate test flags (TEST-TRAIN or TEST-CARGO) and proceed to special check processing, bypassing normal error message handling
[14:Send AEI Messages]
The system processes the train acknowledgment or status update → Look up email addresses for the port code, send notification with train ID and status, and fall back to default recipients if lookup fails
[15:Process Message Routing]
The system processes message routing → Get supervisor Merlin ID from terminal table, validate DC-P Merlin IDs, and prepare for sending messages to MST system and Merlin users
[16:Get Supervisor Merlin ID]
The system looks up supervisor information in the LT table → If table entry found, use alternate terminal if specified and retrieve supervisor Merlin ID; if supervisor ID invalid, add error message and clear user Merlin ID
[18:Send Cargo Messages to Merlin]
The system sends the message to Merlin users → Send message to user Merlin ID; if sending fails, fall back to sending to default recipient 'OM01247'
[19:Send Train Messages to Merlin]
The system sends the message to Merlin users → Send message to user Merlin ID with fallback to 'OM01247' if failed, and additionally send a copy to 'CAERROR' file with 'OM01247' as recipient
[20:Send MST Messages]
The system sends messages to MST → Send header message first, then send each message entry using terminal call letters, and finally send wrap-up message
[21:Process Arrival Notifications]
The system processes the cargo acknowledgment → Create arrival notification message with cargo control number, set action code to 'CAA', and send to GCT1481E transaction
[22:Update Iron Highway Records]
The system updates the cargo record and status differs from saved status → Look up Iron Highway configuration, populate record with cargo details including status, car ID, waybill, and shipment ID from N9 segments, then call Iron Highway update program
[24:Log Transaction Activities]
The system logs the transaction activity → Create log message with current status, include transaction number for ACK status, set appropriate cargo or train indicator, and send to GCT1051E logging transaction
[25:Process Special Checks]
The system performs special check processing → Look up T2 table entry, update 358-ACK timestamp for train test messages or 309-ACK timestamp for cargo test messages with current machine date, century, and time
[Process Merlin Configuration Setup]
Merlin configuration setup is required → The system must execute Merlin processing routine to retrieve and validate user configurations
[Retrieve Administration Table Entry]
Administration table lookup is performed with table ID 'AD' and sequence ID 'ADMINID' → Administration table segment is retrieved and stored for further processing
[Extract 4 Merlin User IDs from Admin Table]
Merlin ID validation process begins → Four Merlin user IDs (DC-P-MERLIN-1, DC-P-MERLIN-2, DC-P-MERLIN-3, DC-P-MERLIN-4) are extracted from administration table for validation
[Set IFS Merlin ID as Valid]
User directory status code is blank indicating valid user → IFS Merlin ID is stored as valid for IFS system message routing
[Set HHS Merlin ID as Valid]
User directory status code is blank indicating valid user → HHS Merlin ID is stored as valid for HHS system message routing
[Set IMS Merlin ID as Valid]
User directory status code is blank indicating valid user → IMS Merlin ID is stored as valid for IMS system message routing
[Retrieve Administration Table Entry - Access GCSTBRT table with 'AD' table ID and 'ADMINID' sequence to get Merlin user configuration data]
A request is made to retrieve the administration table entry with table ID 'AD' and sequence ID 'ADMINID' → The system should retrieve the administration segment containing Merlin user configuration data
[Use Original Merlin ID Set ID Found Flag]
The status code indicates successful user validation → The original Merlin ID is stored as WS-DCP-MERLIN-ID and the ID found flag is set to true
[Set Default ID 'OM01247' Set ID Not Found Flag]
The status code indicates user validation failure → The default ID 'OM01247' is assigned to both GCSTBRT-AD-DC-P-MERLIN-1 and WS-DCP-MERLIN-ID, and the ID not found flag is set to true
[Set IFS Merlin ID to Second Merlin ID]
The validation status code is space indicating success → The system assigns the second DC-P Merlin ID to the IFS Merlin ID
[Set IFS Merlin ID to Default First Merlin ID]
The validation status code is not space indicating failure → The system assigns the first DC-P Merlin ID as the default value to the IFS Merlin ID
[Set HHS Merlin ID to Third Merlin ID Value]
The validation status indicates the Merlin ID exists in the system (CC-STATUS-CODE is SPACE) → Assign the third DC-P Merlin ID value to the HHS Merlin ID (WS-HHS-MERLIN-ID)
[Set HHS Merlin ID to Default First Merlin ID]
The validation status indicates the Merlin ID does not exist in the system (CC-STATUS-CODE is not SPACE) → Assign the first DC-P Merlin ID (GCSTBRT-AD-DC-P-MERLIN-1) as the default value to the HHS Merlin ID (WS-HHS-MERLIN-ID)
[Set IMS Merlin ID to Fourth ID Value]
The validation result shows the fourth Merlin ID exists in the EMTZ segment → The system assigns the fourth DC-P Merlin ID value to the IMS Merlin ID variable (WS-IMS-MERLIN-ID)
[Set IMS Merlin ID to Default First ID]
The validation result shows the fourth Merlin ID does not exist in the EMTZ segment → The system assigns the first DC-P Merlin ID value (GCSTBRT-AD-DC-P-MERLIN-1) to the IMS Merlin ID variable (WS-IMS-MERLIN-ID) as a fallback default
[Extract Reference Number from Message]
The system processes the message for reference initialization → The reference number is copied to EMI-REF, MST-REF, MSG-REF-KEY, and WS-REF-NUMBER variables
[Clear Message Content Areas]
Content areas need to be cleared → EMI-TO-USERCODE, EMI-COPY-USERCODE, EMI-KEYWORDS, EMI-TEXT, EMI-RETURN-STATUS-FLAG, MST-TABLE, MST-CALL-LETTRS, and WS-LTERM-PROCESS are set to SPACES
[Set Train Report Label]
The system determines the message type for labeling → MSG-LIB is set to 'TRAIN REPORT NUMBER :'
[Set Cargo Control Label]
The system determines the message type for labeling → MSG-LIB is set to 'CARGO CONTROL NUMBER :'
[Set Generic Reference Label]
The system determines the message type for labeling → MSG-LIB is set to 'REFERENCE NUMBER :'
[Message Type?]
If the message type indicator → The message is routed to train processing if OTI-02-TRAIN is true, cargo processing if OTI-02-CARGO is true, or other reference processing for all other cases
[Send Train Not Found Message]
The train report is not found in the database → An error message 'TRAIN REPORT NOT FOUND ON CUSTOMS DATABASE' is added to the message queue and train error flag is set
[Send CCN Not Found Message]
The cargo control number is not found in the database → An error message 'CCN NOT FOUND ON CUSTOMS D.B. FOR 824 ACK' is added to the message queue and DCP interface error flag is set
[Format Application Message]
The reference number OTI-03-REF-NUM is not spaces → An application message is formatted using the reference number qualifier and advance number, and message counters are incremented
[Update Train Status to ACK]
The train record has AEI-SEND flag set to 'Y' → An AEI notification message is sent containing train ID and current status information
[Retrieve Train Report by Reference Number]
The system processes the acknowledgment → The system retrieves the corresponding train report from the database using the reference number
[Record Acknowledgment Reference Number]
Setting acknowledgment details → The system moves the reference number from the BGN segment to the train acknowledgment number field
[AEI Send Required?]
Checking for additional notifications → The system checks if the AEI send flag equals 'Y' to determine if AEI message should be sent
[Prepare AEI Status Message]
Preparing the notification message → The system creates a message subject containing 'TRAIN: ' followed by the Canadian customs train ID, ' STATUS: ' and the current status
[Send AEI Message to Border Points]
Sending the notification → The system calls the AEI message sending function to transmit the status update
[Retrieve Train Report by Reference Number]
The system processes the train acknowledgment → The system retrieves the corresponding train report from the database using the reference number
[Record Acknowledgment Number]
The system updates the train record → The system records the acknowledgment reference number from the message into the train record
[Send AEI Status Message]
The system sends notifications → The system creates and sends an AEI message containing train ID and current status
[Format Status Message with Train ID and Status]
The system formats the AEI message → The system creates a subject line containing 'TRAIN: ' followed by the Canadian customs train ID, ' STATUS: ' followed by the current train status
[Send AEI Message to Recipients]
The system sends the AEI notification → The system calls the email messaging service with formatted message details and item width of 080
[AEI Message Sent Successfully]
The system completes AEI processing → The system purges the message queue and continues normal processing
[Extract Port Code from Train Record]
The system needs to send AEI notification messages → The port code is extracted from the train record's port of release field and used as the lookup key
[Add Email Recipient to Distribution List]
The system processes the email recipient → The email user ID is moved to the corresponding position in the message distribution list
[Set Default Merlin ID as Sender]
Setting up the message sender information → The default Merlin ID is assigned as the from-user-code for the message
[Retrieve Cargo Control Record by Reference Number]
The system attempts to retrieve the cargo control record using the reference number → The system performs database lookup using the reference number as key for both cargo control and cargo segment records
[Update Cargo Status to ACK]
Processing a cargo acknowledgment message → The system updates the cargo current status to 'ACK'
[Set Current Status to ACK]
Processing a cargo acknowledgment message → The system sets the working current status to 'ACK'
[Set Reference Number from Message]
The system needs to retrieve cargo control records → The reference number is set as the key value for both CCRT-SSAQ and A2RT-SSAQ segments
[Access GCSA2RT Segment First]
The system performs cargo control record retrieval → The system calls CIMS with GHU function to access GCA2-PCB using GCSCCS52 segment and A2RT-SSAQ key
[Access GCSCCRT Segment]
The system continues cargo control record retrieval → The system calls CIMS with GHU function to access GCCC-PCB using GCCC-CARGO-REPORT-SEGMENT and CCRT-SSAQ key
[Return Cargo Control Data]
The status code indicates the GCSCCRT record was found (CC-STATUS-CODE is spaces) → The system returns with the cargo control data available in GCCC-CARGO-REPORT-SEGMENT for further processing
[Retrieve Cargo Control Record by Reference Number]
The system attempts to retrieve the cargo control record using the reference number → The system performs database lookup using the reference number as the key for both cargo control and related segments
[Is Test Message?]
The reference number equals '6105ETESTTRAIN00000000000' → The message is flagged as test data and special test processing is performed
[Is Test Message?]
The reference number starts with '6105ECPRSTESTCARGO' or '6105ETESTCARGO' → The message is flagged as test data and special test processing is performed
[Message Type?]
The message type indicator is evaluated → The message is routed to either train error processing or cargo error processing based on the type indicator
[Is V67 Warning?]
The free-form message text starts with 'V67' → The message is classified as a V67 warning and special warning processing is applied
[Is V67 Warning - Process as Train?]
The free-form message text starts with 'V67' → The message is rerouted to train error processing instead of cargo error processing
[Retrieve Last Modified Terminal]
Terminal information is needed for message routing → If last modified terminal is not empty, use it; otherwise use the creation terminal for processing
[Retrieve Last Modified Terminal]
Terminal information is needed for message routing → If CCN last modify terminal is not empty, use it; otherwise use the CCN creation terminal for processing
[Is Test Train Message?]
The reference number equals '6105ETESTTRAIN00000000000' → The message is flagged as test train data and special test processing is performed
[Handle Test Train Processing]
The reference number matches the test train pattern → Special check processing is performed and test train indicator is set to true
[Is V67 Warning Message?]
The free form message starts with 'V67' → The message is identified as a V67 warning requiring special handling
[Add Warning Message: Train/Cargo Not Found for V67 Warning]
The system processes the missing train record → The message 'TRAIN/CARGO NOT FOUND ON CUSTOMS DATABASE FOR V67 WARNING' is added to the error text and MST entry
[Is V67 Warning?]
The free form message starts with 'V67' → The message is identified as a V67 warning and train message type is set
[Set Train Message Type]
The V67 warning is being processed → The train message type indicator is set to true
[Set Train/Cargo Not Found Message for V67]
The free form message starts with 'V67' → The system adds message 'TRAIN/CARGO NOT FOUND ON CUSTOMS DATABASE FOR V67 WARNING' and sets DCP interface error flag
[Set Train Report Not Found Message]
The free form message does not start with 'V67' → The system adds message 'TRAIN REPORT NOT FOUND ON CUSTOMS DATABASE' and sets DCP interface error flag
[Set Train Report Found Flag]
The free form message starts with 'V67' → The system sets the train type indicator to true
[Reference Number = '6105ETESTTRAIN00000000000'?]
The reference number equals '6105ETESTTRAIN00000000000' → The system sets the test train indicator and initiates test processing workflow
[Save Updated Test Table]
The system completes the timestamp recording → The updated T2 table segment is written back to the database using replace operation
[Update Test Train Acknowledgment Timestamp - Record current system date, century, and time in T2-358-ACK field]
The system processes the test train acknowledgment → The current system date (6 digits), century (2 digits), and time (4 digits) are recorded in the T2-358-ACK field with date in positions 3-8, century in positions 1-2, and time in positions 9-12
[Update Test Train Acknowledgment Timestamp - Record current system date, century, and time in T2-358-ACK field]
The system processes the test cargo acknowledgment → The current system date (6 digits), century (2 digits), and time (4 digits) are recorded in the T2-309-ACK field with date in positions 3-8, century in positions 1-2, and time in positions 9-12
[Retrieve T2 Table Segment]
The system prepares to update acknowledgment timestamps → The T2 table segment is retrieved using table ID 'T2' and empty sequence ID, and if retrieval fails an error message 'T2 CHECK TABLE ENTRY NOT FOUND' is generated
[Save Updated T2 Table Segment]
The timestamp updates are complete → The updated T2 table segment is saved back to the database using the REPL function
[Is Test Cargo Message?, Check if Test Cargo Message]
The reference number starts with '6105ECPRSTESTCARGO' or '6105ETESTCARGO' → The message is flagged as test cargo and routed to special test processing
[Handle Test Cargo Processing]
The test cargo flag is set → The system performs special check processing and exits cargo error handling
[Retrieve Cargo Control Record]
The system searches for the corresponding cargo control record → The cargo record is retrieved if it exists in the database
[Is V67 Warning?, Check for V67 Warning Message]
The free-form message starts with 'V67' → The message is identified as a V67 warning requiring train error processing
[Process Special Test Check]
Special test processing is invoked → The system updates test timestamps in the T2 table and exits cargo error processing
[Access GCSCCRT Segment with Reference Number]
The system searches for the cargo control record → The GCSCCRT segment is accessed using the reference number as the key
[Access GCSA2RT Segment with Reference Number]
The system needs complete cargo information → The GCSA2RT segment is accessed using the same reference number
[Determine Last Modify Terminal]
The system determines message routing → The last modify terminal field is checked for availability
[Use Last Modify Terminal]
Terminal selection for processing is required → The last modify terminal is selected for message routing
[Use Creation Terminal]
Terminal selection for processing is required → The creation terminal is selected as the fallback for message routing
[Store Terminal for Processing]
The terminal selection is completed → The selected terminal is stored in the processing context for message routing
[Retrieve T2 Test Table]
The system needs to update test acknowledgment data → The system should retrieve the T2 table segment from the GCSTBRT table with table ID 'T2'
[Update Test Acknowledgment Timestamp]
A cargo test acknowledgment needs to be recorded → The system should update T2-309-ACK field with current machine date (positions 3-8), current century (positions 1-2), and current time first 4 digits (positions 9-12)
[Save Updated T2 Table]
The timestamp update is complete → The system should save the updated T2 table segment back to the database using REPL function
[Retrieve T2 Test Table Entry]
The system attempts to retrieve the T2 test table entry with empty sequence ID → The system should fetch the T2 table segment for timestamp update operations
[Message Type?]
If the transaction type from the OTI message → If OTI-02-TRAIN is true, process as train test; if OTI-02-CARGO is true, process as cargo test
[Update T2-358-ACK Field for Train Test]
The system processes the train test acknowledgment → The system should move the machine century to positions 1-2, machine date to positions 3-8, and machine time (first 4 digits) to positions 9-12 of the T2-358-ACK field
[Update T2-309-ACK Field for Cargo Test]
The system processes the cargo test acknowledgment → The system should move the machine century to positions 1-2, machine date to positions 3-8, and machine time (first 4 digits) to positions 9-12 of the T2-309-ACK field
[Save Updated T2 Table Entry]
The timestamp update is complete → The system should Execute a REPL operation to save the updated T2 table segment back to the database
[Message Number Available?]
The system checks for availability of a custom message number in GCW122-MSG-NUM field → If custom message number exists and is not spaces, use it for lookup, otherwise use the first 3 characters of the TED free-form message as the error code
[Use Custom Message Number]
The system builds the lookup key for message table query → Concatenate 'B' prefix with the custom message number to form the sequence ID for table lookup
[Lookup Message in MS Table]
The system performs a table segment retrieval using function code 'GU' → Query the MS table using the constructed key and return the table segment or error flag
[Message Found in Table?]
The system checks the return flag from the table lookup operation → If return flag equals 0, message was found in table, otherwise message was not found and raw error text should be used
[Retrieve Standardized English Text]
The system processes the retrieved MS table segment → Set message found flag to true, move table segment to MS segment structure, and extract English text to working storage
[Format Message for Display]
The system prepares the message for display → Add the message text to both EMI text line array and MST entry array at current index positions, and increment the text and MST index counters
[Prepare Message for Transaction Log]
The system prepares the message for transaction logging → Set security byte to high-value, populate sending transaction as 'GCT1221E', set ACF2 user ID, date, time, action code as 'ZZZ', and reference number, then determine record type based on cargo or train classification
[Message Number Available?]
The system checks for availability of a predefined message number in GCW122-MSG-NUM → If predefined message number exists and is not spaces, use it for key construction, otherwise extract first 3 characters from free-form message text
[Build Key with Predefined Message Number]
The system builds the table lookup key → Concatenate 'B' prefix with the predefined message number to form the sequence ID for table lookup
[Set Table ID to 'MS']
The system prepares table access parameters → Set table identifier to 'MS' to access the message text table
[Call Table Lookup Service]
The system needs to retrieve standardized message text → Call GCCTBIO service with GU function code to Execute table segment retrieval
[Set Message Found Flag]
The system processes the lookup result → Set SW-GCSTBRT-MS-FOUND flag to true, move retrieved table segment to GCSTBRT-MS-SEGMENT, and store English text in WS-GCSTBRT-MS-ENG-TEXT
[Store Retrieved Message Text]
The system stores the retrieved message text → Extract English text from GCSTBRT-MS-ENG-TEXT and make it available for message processing operations
[Set Message Not Found Flag]
The system processes the failed lookup result → Set SW-GCSTBRT-MS-NOT-FOUND flag to true to indicate message text was not available in the table
[Send AEI Message if Required]
The train record has AEI send flag set to 'Y' → Send an AEI message containing the train ID and current status
[Save Train Root Segment]
The system needs to update the database record → The current train root segment is saved, the record is retrieved from database, the saved segment is restored, and the record is replaced in the database
[AEI Send Flag = 'Y'?]
The AEI send flag is set to 'Y' for the train record → The system sends an AEI status message containing train ID and current status
[Update Cargo Record in GCSCCRT]
The cargo record status needs to be persisted → The system should update the cargo record in the GCSCCRT database with the new error status and current status
[Retrieve T2 Test Table Entry]
The system needs to update test acknowledgment timestamps → The T2 test table entry is retrieved using table lookup function
[Update Train Test ACK Date/Time T2-358-ACK]
The message type is identified as train test → The current machine date and time are stored in T2-358-ACK field with century, date, and time components
[Update Cargo Test ACK Date/Time T2-309-ACK]
The message type is identified as cargo test → The current machine date and time are stored in T2-309-ACK field with century, date, and time components
[Save Updated Test Table]
The timestamp updates are complete → The modified T2 table segment is saved using replace function
[Clear Message Fields]
The system begins AEI message preparation → All message fields including copy usercode, keywords, text, item sequence numbers, and return status flag are cleared to spaces or initialized
[Prepare AEI Message Content]
The system prepares the AEI message content → Message width is set to 080 characters, sequence numbers are cleared, text content is cleared, and return status flag is initialized
[Set Message Subject with Train ID and Status]
The system formats the AEI message subject → The subject line is formatted as 'TRAIN: [train_id] STATUS: [current_status]'
[Call Email Service to Send Message]
The system calls the email service to send the message → The email service processes the message and returns a status flag indicating success or failure
[AEI Message Sent Successfully]
The return status flag indicates successful transmission → The system continues to message queue purging without further action
[Send to Default Recipients OM01247 and AEI9999]
The return status flag indicates transmission failure → The system clears recipient fields and sets OM01247 as first recipient and AEI9999 as second recipient
[Call Email Service Again]
The system retries the email service call → The email service processes the message to default recipients and returns a status flag
[Second Send Successful]
The return status flag indicates successful transmission to defaults → The system continues to message queue purging
[Purge Message Queue]
The system needs to clean up resources → The message queue is purged and communication status is initialized
[Prepare Email User List for AEI Message]
Preparing to send AEI notification → The system sets the default Merlin ID as sender, configures recipient list, clears copy and keyword fields, sets message width to 080, and initializes return status
[Set Message Subject and Format]
The system prepares the AEI message content → The message subject is formatted as 'TRAIN: [train_id] STATUS: [current_status]' and message formatting parameters are set
[Call Email Send Service]
The system calls the email send service → The email service processes the send request and returns a status indicating success or failure
[Message Sent Successfully]
The email send service returns a successful status → The AEI message process completes successfully and no further action is required
[Send to Backup Recipients OM01247 and AEI9999]
The email send service returns a failure status → The system clears the recipient list and sets 'OM01247' as first recipient and 'AEI9999' as second recipient, then attempts to send the message again
[Process Complete]
The backup email send service returns a successful status → The AEI message process completes successfully using the backup recipients
[MST Processing Required?]
The system checks the MST processing flag → MST processing continues if the flag indicates processing is required, otherwise MST processing is bypassed
[Get Supervisor Merlin ID from Terminal]
The system looks up terminal configuration in the LT table → The supervisor Merlin ID is retrieved from the terminal configuration if the table entry exists, otherwise terminal segment is cleared
[Determine Message Recipients]
The system needs to determine message routing recipients → Valid supervisor Merlin IDs are assigned as recipients, invalid IDs result in empty recipient assignment
[Route to Train Message Recipients]
The system routes the message to train recipients → The message is sent to the supervisor Merlin ID and additionally routed to the CAERROR system with OM01247 as recipient
[Route to Cargo Message Recipients]
The system routes the message to cargo recipients → The message is sent to the supervisor Merlin ID, with fallback to OM01247 if the primary send fails
[Send Messages via MST System]
The system sends messages via MST using SMSTONLY service → Each message entry is transmitted sequentially until all entries are processed, followed by a WRAP command to complete the transmission
[Retrieve LT Segment Data]
The table segment is successfully retrieved → The system moves the table segment data to the LT segment structure for processing
[Set Valid Supervisor ID]
The status code is spaces (indicating success) → The system assigns the supervisor Merlin ID to the user Merlin field for message routing
[Retrieve Terminal Configuration from LT Table]
The system queries the LT table with the terminal identifier → The terminal configuration segment is retrieved and stored for further processing
[Set Valid Supervisor Merlin ID for Message Routing]
The system processes the validation result → The supervisor Merlin ID is assigned to the user Merlin variable for message routing
[Get DC-P Merlin ID 1 from Admin Table]
The system retrieves DC-P Merlin ID 1 from the admin table with table ID 'AD' and sequence ID 'ADMINID' → The DC-P Merlin ID 1 is obtained from the admin table segment
[Clear Message Recipients]
The system prepares to route the message → All recipient fields are cleared to spaces to ensure no residual data affects message routing
[Set Primary Merlin User as Recipient]
The system sets up the primary message recipient → The supervisor Merlin user ID is assigned as the first recipient in the user codes array
[Send Message to Primary User]
The system attempts to send the message via EMCSEND2 service → The message is transmitted to the Merlin messaging system with all required message details including subject, keywords, and text content
[Message Delivery Successful?]
The system checks the message delivery status → If the return status flag equals 0, the message delivery is considered successful, otherwise it is considered failed
[Clear Recipients for Fallback]
The system prepares for fallback message routing → All recipient fields including copy usercode and to usercode are cleared to spaces
[Set Default User OM01247 as Recipient]
The system sets up fallback message routing → The default user ID 'OM01247' is assigned as the first recipient in the user codes array
[Send Message to Default User]
The system attempts fallback message delivery via EMCSEND2 service → The message is transmitted to the default user with the same message content including subject, keywords, and text
[Purge Message Queue]
The system completes message processing → The message queue is purged using CIMS service with PURG function to clean up resources
[Clear Message Recipients]
The system prepares to send the message → All message recipient fields are cleared to spaces
[Set Primary Recipient to Supervisor Merlin ID]
The primary recipient needs to be determined → The supervisor Merlin ID is set as the first recipient in the message
[Send Message to Primary Recipient via EMCSEND2]
The system attempts to send the message → The message is sent via EMCSEND2 service to the primary recipient
[Message Send Successful?]
The message send operation completes → If the return status flag is not 0, the send failed and fallback processing is required
[Set Default Recipient to OM01247]
A fallback recipient needs to be established → The recipient is set to the default support ID 'OM01247'
[Retry Send to Default Recipient]
The system retries the message send → The message is sent via EMCSEND2 service to the default recipient
[Purge Message Queue]
The message processing is finished → The message queue is purged using CIMS PURG function
[Final Purge Message Queue]
The message processing workflow is finishing → The message queue is purged using CIMS PURG function for final cleanup
[Set MST Communication Parameters]
MST communication is being initialized → The system sets origin terminal to 'ISTS' and transaction code to 'GCT122'
[Send Message Header]
Beginning message transmission → The system sends the message header record as the first entry in the message text array
[More Message Entries?]
Processing message entries → The system continues sending entries until it encounters a blank entry indicating no more content
[Send Next Message Entry]
Processing each message entry → The system calls SMSTONLY with the current message entry content
[Send Wrap-Up Command]
Completing MST transmission → The system sets user function code to 'WRAP' and calls SMSTONLY to close the session
[Prepare Arrival Message]
The system finalizes arrival processing → The system copies the complete arrival input structure to the outbound message format
[Send Arrival Transaction to GCT1481E]
The system processes cargo arrival → The system sends the arrival transaction to GCT1481E system for further processing
[Write Message to Log]
The system completes arrival processing → The system writes the arrival message details to the system log for audit trail
[Purge Message Queue]
The system finalizes arrival processing → The system purges the message queue to clean up transaction resources
[Prepare GCT1481E Message Structure]
The system prepares to communicate the arrival information → The GCX148 input data is formatted into the GCT1481E message structure
[Set Security Parameters]
Security parameters need to be set → The security byte is set to high-value to indicate secure transmission
[Extract Cargo Control Number]
An arrival message is being prepared → The cargo control number is extracted and assigned to the message train or US CCN field
[Set Message Type to Cargo Arrival]
The message type needs to be specified → The message type is set to cargo arrival indicator
[Set Action Code to 'CAA']
The action code needs to be specified → The action code is set to 'CAA' to indicate cargo arrival action
[Extract Port Code from Manifest]
Port information is needed for the arrival message → The port code is extracted from the manifest transaction code and assigned to the message port code field
[Prepare Message for Transmission]
The message needs to be prepared for transmission → The complete message input is formatted and prepared for the messaging system
[Send Message to Transaction Queue]
The message needs to be sent to the processing queue → The message is transmitted using the CIMS interface with CHNG function to the alternate PCB
[Write Message to Log]
Logging is required for audit purposes → The message is written to the system log using WRITMSGL with message code, content, length and module name
[Complete Message Transmission]
The transmission process needs to be completed → The message is purged from the processing queue using CIMS with PURG function to the alternate PCB
[Set Security Level to High]
The security level is being configured → The security byte is set to high-value to ensure maximum protection
[Extract Cargo Control Number]
An arrival message is being prepared → The cargo control number is extracted and assigned to the message identifier field
[Set Message Type to Cargo]
The message type classification is being set → The message is marked as a cargo-type message
[Set Action Code to 'CAA' - Cargo Arrival]
The action code is being assigned → The action code is set to 'CAA' to indicate cargo arrival
[Extract Port Code from Manifest]
An arrival message is being prepared → The port code from the manifest transaction is extracted and assigned to the message port code field
[Prepare Message for Transmission]
The message is ready for transmission → The message is sent through the messaging system and the transmission queue is purged
[Set Message Destination to Support Inbox]
The system sets the delivery destination → The destination filename is set to the support inbox constant
[Purge Message Queue]
The system performs cleanup operations → The message queue is purged and system status is reset
[Set Security and Transaction Details]
Security and transaction details need to be recorded → The security byte is set to high-value and sending transaction is set to 'GCT1221E'
[Add Current Status to Log Message]
The transaction status is being recorded in the log → The current status from WS-CURRENT-STATUS is recorded in the log message field
[Send Log Message to GCT1051E]
The log message needs to be sent to the audit system → The log message is sent to the GCT1051E audit logging system using the CIMS interface
[Write Log Message to System]
The message needs to be written to the system log → The log message is written using WRITMSGL service with the message code, content, length, and module name
[Purge Message Queue]
The logging process is complete → The message queue is purged using CIMS PURG function to clean up processed messages
[Access Test Configuration Table T2]
The system attempts to access the test configuration table T2 → The system retrieves the T2 table segment for test processing
[Test Message Type?]
If the message type indicator → If the message is train type, process train test acknowledgment; if cargo type, process cargo test acknowledgment
[Update Train Test Acknowledgment]
The system processes the train test acknowledgment → The system updates the T2-358-ACK field with current machine date (century and date) and current machine time (first 4 digits)
[Update Cargo Test Acknowledgment]
The system processes the cargo test acknowledgment → The system updates the T2-309-ACK field with current machine date (century and date) and current machine time (first 4 digits)
[Save Updated Test Table]
The system completes the timestamp update process → The system saves the updated T2 table segment back to the database using replace function
[Set Reference Number from Input Message]
The system processes the message header setup → The reference number is copied to EMI-REF, MST-REF, MSG-REF-KEY, and WS-REF-NUMBER fields for consistent message tracking
[Clear Message Content Areas]
The system clears message content areas → EMI-TO-USERCODE, EMI-COPY-USERCODE, EMI-KEYWORDS, EMI-TEXT, EMI-RETURN-STATUS-FLAG, MST-TABLE, MST-CALL-LETTRS, and WS-LTERM-PROCESS are set to SPACES
[Set Train Report Header Text]
The system determines the message header text → MSG-LIB is set to 'TRAIN REPORT NUMBER :'
[Set Cargo Control Header Text]
The system determines the message header text → MSG-LIB is set to 'CARGO CONTROL NUMBER :'
[Set Generic Reference Header Text]
The system determines the message header text → MSG-LIB is set to 'REFERENCE NUMBER :'
[Extract Reference Number from Message]
The system processes the message for reference number extraction → The reference number is copied to EMI-REF, MST-REF, MSG-REF-KEY, and WS-REF-NUMBER variables
[Set Train Report Label]
The system determines the message label → MSG-LIB is set to 'TRAIN REPORT NUMBER :'
[Set Cargo Control Number Label]
The system determines the message label → MSG-LIB is set to 'CARGO CONTROL NUMBER :'
[Set Generic Reference Label]
The system determines the message label → MSG-LIB is set to 'REFERENCE NUMBER :'
[Clear Message Fields]
Message fields need to be cleared → EMI-TO-USERCODE, EMI-COPY-USERCODE, EMI-KEYWORDS, EMI-TEXT, EMI-RETURN-STATUS-FLAG, MST-TABLE, MST-CALL-LETTRS, and WS-LTERM-PROCESS are all set to SPACES
[Format Train Report Message]
The transaction type is identified as train operation → The message library text is set to 'TRAIN REPORT NUMBER :' to indicate train-specific reference numbering
[Format Cargo Control Message]
The transaction type is identified as cargo operation → The message library text is set to 'CARGO CONTROL NUMBER :' to indicate cargo-specific reference numbering
[Format Reference Number Message]
The transaction type is neither train nor cargo operation → The message library text is set to 'REFERENCE NUMBER :' as the default reference numbering format
[Format Message for EMI Channel]
The message needs to be distributed through electronic mail interface → The system formats the message into EMI-TEXT-LINE structure for email distribution
[Format Message for MST Channel]
The message needs to be distributed through message switch terminal → The system formats the message into MST-ENTRY structure for terminal distribution
[Format Message for Log Channel]
The message needs to be logged for audit and tracking purposes → The system formats the message into GCX105-MESSAGE structure for logging distribution
[Prepare Message Headers]
Message headers need to be prepared for transmission → The system sets security byte to HIGH-VALUE, sending transaction to 'GCT1221E', ACF2 user ID from common area, and action code to 'ZZZ'
[Set Message Reference Numbers]
Reference number information needs to be included in the message → The system assigns the transaction reference number (OTI-03-REF-NUM) to the train or CCN field in the message header
[Add Date/Time Stamps]
Timestamp information needs to be added to the message → The system assigns the current date (BGN-03-DATE) and time (BGN-04-TIME) to the message header timestamp fields
[Format Subject Line]
Transaction type classification is needed for message routing → The system sets GCX105-CA-CARGO flag for cargo transactions, GCX105-NEW-CA-TRAIN flag for train transactions, or continues without specific classification for other transaction types
[Attempt Primary Message Delivery]
The system calls the messaging service with primary recipient information → The message delivery is attempted and a return status is provided
[Message Delivered Successfully]
The system confirms successful delivery → The system proceeds to purge the message queue and complete processing
[Clear Message Recipients]
The system needs to attempt fallback delivery → All existing recipient fields are cleared to spaces
[Set Default Recipient 'OM01247']
The system needs to set a fallback recipient → The recipient is set to 'OM01247' as the default fallback recipient
[Retry Message Delivery to Default]
The system calls the messaging service with default recipient information → The message delivery is attempted to the default recipient and a return status is provided
[Message Delivered to Default]
The system confirms successful delivery to default recipient → The system proceeds to purge the message queue and complete processing
[Purge Message Queue]
The system needs to clean up the message queue → The message queue is purged using the PURG function
[End Message Processing]
The system finishes message processing → Control is returned to the calling process and message processing ends
[Set Function Code to 'WRAP']
The system needs to complete the message transmission process → The system sets the user function code to 'WRAP' and sends the wrap command to finalize the message transmission
[Send Wrap Command to MST]
The system executes the wrap command transmission → The system calls the message switching terminal service with the wrap command, communication control block, alternate PCB, call letters, and message header record
[Check Reference Number Pattern]
The reference number equals '6105ETESTTRAIN00000000000':
starts with '6105ECPRSTESTCARGO'
starts with '6105ETESTCARGO'
→ The message is classified as test data and special test processing is triggered
[Retrieve T2 Test Table Entry]
The system attempts to retrieve the T2 table entry with empty sequence ID → The T2 test table segment is loaded for timestamp updates
[Message Type?]
The message type indicator shows train (OTI-02-TRAIN is true) → The system prepares to update the train test acknowledgment field (T2-358-ACK)
[Update Train Test Acknowledgment Field]
The system processes the train test acknowledgment → The T2-358-ACK field is updated with current date (century + date) and time
[Update Cargo Test Acknowledgment Field]
The system processes the cargo test acknowledgment → The T2-309-ACK field is updated with current date (century + date) and time
[Save Updated Table Entry]
The system saves the changes → The updated T2 table segment is written back to the database using replace function

Structural Validations

[3:Control Merlin ID Validation]
Each Merlin ID is validated against the EMTZ segment → If DC-P-MERLIN-1 is invalid, use default 'OM01247' and set not-found flag; for other invalid IDs (2,3,4), fall back to DC-P-MERLIN-1 value
[8:Process Error Messages]
The system processes the error message → Check if message is test data first; if not test data, route to train or cargo error processing based on transaction type
[9:Process Train Errors]
The system processes the train error → If train not found, add appropriate error message (V67 warning or general train error); if found, determine processing terminal and handle V67 warnings specially
[10:Process Cargo Errors]
The system processes the cargo error → If cargo not found and message is V67, process as train error; if cargo not found and not V67, add cargo error message; if found, save current status and determine processing terminal
[11:Retrieve Error Message Text]
The system looks up the error message text in the MS table → If message found, use English text from table; if not found, use free-form message text and add 'message not found' error
[Test Message?]
The system checks if the message is test data → Identify as train test if reference equals '6105ETESTTRAIN00000000000', or cargo test if reference starts with '6105ECPRSTESTCARGO' or '6105ETESTCARGO'
[17:Validate Merlin User IDs]
The system validates the Merlin user ID → If DC-P1 ID not found, add error message indicating invalid DC&P Merlin userid
[Train Error?]
The system determines the routing destination → Route to train message sending if train error flag is set, otherwise route to cargo message sending
[Admin Table Found?]
Table lookup return flag equals 0 → Administration table segment is loaded for Merlin ID extraction, otherwise error message is set and error handling is called
[Return Flag = 0?, Move Retrieved Segment to Administration Segment]
The return flag equals 0 indicating successful retrieval → The retrieved table segment should be moved to the administration segment structure for further processing
[Set Error Message: Admin Table Not Found, Call Error Handler]
The return flag != 0 indicating retrieval failure → An error message should be set indicating admin table not found and the error handler should be called
[Check ID Exists in EMTZ Segment]
The system checks the EMTZ segment for user existence using the Merlin ID as the key → The system determines if the user ID exists based on the status code response
[Check if Second Merlin ID Exists in EMTZ Segment]
The system checks if the second Merlin ID exists in the EMTZ segment → If the second Merlin ID is valid (status code is space), assign it to IFS Merlin ID, otherwise assign the first DC-P Merlin ID as default to IFS Merlin ID
[Check if third Merlin ID exists in EMTZ segment and set default to first ID if invalid]
The system validates the third Merlin ID against the EMTZ user segment → If the third Merlin ID exists in the system, assign it to WS-HHS-MERLIN-ID; otherwise assign the first DC-P Merlin ID (GCSTBRT-AD-DC-P-MERLIN-1) as the default value for HHS system
[Check if Fourth Merlin ID Exists in EMTZ Segment]
The system checks if this fourth Merlin ID exists in the EMTZ segment → If the fourth Merlin ID is valid (status code is space), assign it to WS-IMS-MERLIN-ID, otherwise assign the first DC-P Merlin ID (GCSTBRT-AD-DC-P-MERLIN-1) to WS-IMS-MERLIN-ID as default
[Train Report Found?]
The system searches for the train report using the reference number → Processing continues with train update if found, or error message generation if not found
[Cargo Control Number Found?]
The system searches for the cargo control number → Processing continues with cargo update if found, or error message generation if not found
[Set Error Message: Train Report Not Found]
The train report is not found in the database → The system adds the message 'TRAIN REPORT NOT FOUND ON CUSTOMS DATABASE' to the error text and MST entry
[Mark as Train Error for Notification]
The error message is set → The system sets the train error flag to true for subsequent notification processing
[Log Train Not Found Error]
The train report is not found in the database → The system adds 'TRAIN REPORT NOT FOUND ON CUSTOMS DATABASE' message to the error log and sets train error flag
[Log Send Failure Error]
The system handles the send failure → The system logs error message 'SEND TO FILE OF OM01247 FAILED' and calls error handling routine
[Add Error Message: CCN Not Found]
The cargo control number is not found in the customs database → The system adds error message 'CCN NOT FOUND ON CUSTOMS D.B. FOR 824 ACK' and sets DCP interface error flag to true
[Clear GCSA2RT Data]
The status code indicates the GCSA2RT record was not found (CC-STATUS-CODE is not spaces) → The system moves spaces to GCSCCS52 to clear the segment data
[Return Record Not Found Status]
The status code indicates the GCSCCRT record was not found (CC-STATUS-CODE is not spaces) → The system returns with a not found status, making the cargo control data unavailable for processing
[Add Error Message: CCN Not Found]
The cargo control record is not found in the database → The system adds error message 'CCN NOT FOUND ON CUSTOMS D.B. FOR 824 ACK' to the message text and MST entry
[Train Report Found?]
The system searches for the train report using the reference number → If the train report is not found, an error flag is set and a 'train report not found' message is recorded
[Cargo Control Found?]
The system searches for the cargo control number using the reference number → If the cargo control number is not found, an error flag is set and a 'CCN not found' message is recorded
[Error Message Found in Tables?]
The system searches for standardized message text using the error code → If found, the standardized English text is used; if not found, the original free-form message is used and a 'message not found' warning is added
[Error Type?]
The error type from the message table is evaluated → Status is set to INFO for type 'X' with warning messages, WARNING for type 'X' with error messages, ERROR for other types, or REJECT for type 'R'
[Set Train Error Flag]
The message is not a test train message → The train error flag is set to true
[Add Error Message: Train Report Not Found on Database]
The system processes the missing train record → The message 'TRAIN REPORT NOT FOUND ON CUSTOMS DATABASE' is added to the error text and MST entry
[Set Error Flag for DCP Interface]
An error message has been added for the missing train → The DCP interface error flag is set to true
[Set Cargo Error Flag]
The message is confirmed as production cargo data → The cargo error flag is set to true
[Process as Train Error Instead]
The V67 redirection rule is triggered → The system processes the message using train error handling procedures
[Add Error Message: CCN Not Found]
The cargo record is confirmed as not found → An error message 'CCN NOT FOUND ON CUSTOMS DATABASE' is added to the message queue
[Set Cargo Error Processing Flag]
The cargo error processing begins → The cargo error flag is set to indicate cargo-specific error handling
[Process as Train Error Instead]
The system processes the V67 warning → The message is routed to train error processing instead of cargo error processing
[Record CCN Not Found Error]
The system processes the missing cargo record → An error message 'CCN NOT FOUND ON CUSTOMS DATABASE' is recorded for user notification
[Check Reference Number]
The reference number starts with '6105ECPRSTESTCARGO' or starts with '6105ETESTCARGO' → The system should identify this as test cargo data and set the test cargo flag
[T2 Table Found?]
The T2 table retrieval operation is performed → If the table is not found (return flag not equal to '0'), log an error message 'T2 CHECK TABLE ENTRY NOT FOUND'
[Continue Normal Cargo Error Processing]
The reference number does not match test cargo patterns → The system should continue with normal cargo error processing workflow
[Table Entry Found?]
The table retrieval operation completes → If the return flag is not '0', the system should display an error message 'T2 CHECK TABLE ENTRY NOT FOUND' and terminate processing
[Use Standard Error Code from TED Message]
The system builds the lookup key for message table query → Concatenate 'B' prefix with the first 3 characters of TED-02-FREE-FORM-MSG to form the sequence ID for table lookup
[Use Raw Error Message from TED]
The system needs to provide error message text → Set message not found flag to true and use TED-02-FREE-FORM-MSG as the error message text
[Add Secondary Error Message]
The system processes the unfound message scenario → Add a secondary message 'ERROR MESSAGE NOT FOUND ON TABLE :' with the error number, format it for display and logging, and increment message counters
[Build Key with Error Code from Message]
The system builds the table lookup key → Extract first 3 characters from TED-02-FREE-FORM-MSG and concatenate with 'B' prefix to form the sequence ID for table lookup
[Message Text Found?]
If the lookup operation result → If GCCTBIO-RETURN-FLAG equals 0, message text was found successfully, otherwise message text was not found
[Error Type = 'X' Info?]
The error type from the message table is 'X' (informational) → Set current status to 'WARNING' if the original item was a warning, otherwise set to 'INFO', and exit without database updates
[Set Error Resend Flag]
Processing an error message for the train → Set the security error resend flag to 'Y' to indicate the record needs error processing
[Error Type = 'R' Reject?]
The message table error type is 'R' → Set train status to 'REJECT' and current status to 'REJECT', otherwise set train status to 'ERROR' and current status to 'ERROR'
[Set Error/Release Status Index]
Processing an error message for cargo → Set the error or release status index to 'E' to indicate error processing mode
[Error Type = 'R' Reject?]
The message table error type is 'R' → Set cargo error status to 'R' and current status to 'REJECT', otherwise set cargo error status to 'E' and current status to 'ERROR'
[Error Type = 'X' Info Only?]
The error type is 'X' indicating informational message only → The system sets status to WARNING for warning items or INFO for other items and exits without database updates
[Train Report Found in Database?]
The system checks for train record existence in the database → Processing continues only if the train record is found, otherwise the update process is skipped
[Error Type = 'R' Reject?]
The error type is 'R' indicating a rejection → The system sets reject status flag, train status to REJECT, and current status to 'REJECT'
[Set ERROR Status]
The error type is not 'R' → The system sets error status flag, train status to ERROR, and current status to 'ERROR'
[Is Error Type 'X' Info?]
The error type from the message table is 'X' (informational) → The system should set the current status to 'WARNING' for warning items or 'INFO' for other items and exit without updating the cargo database record
[Set Error/Release Status Index to 'E']
The cargo report is found in the system → The system should set the error or release status index to 'E' to indicate error processing mode
[Is Error Type 'R' Reject?]
The error type from the message table is 'R' (reject) → The system should set the error status to 'R', set the current status to 'REJECT', and update the cargo record in the database
[Set Current Status to ERROR]
The error type from the message table is not 'R' (not a reject) and not 'X' (not informational) → The system should set the error status to 'E', set the current status to 'ERROR', and update the cargo record in the database
[Identify as Test Train Message 6105ETESTTRAIN00000000000]
The reference number equals '6105ETESTTRAIN00000000000' → The message is identified as a train test message and test train indicator is set
[Identify as Test Cargo Message 6105ECPRSTESTCARGO or 6105ETESTCARGO]
The reference number starts with '6105ECPRSTESTCARGO' or starts with '6105ETESTCARGO' → The message is identified as a cargo test message and test cargo indicator is set
[Skip Normal Error Processing]
Test message processing is complete → Normal error processing is skipped and control proceeds to transaction logging
[Log Error - Send to OM01247 Failed]
The return status flag indicates failure for the second attempt → The system logs an error message 'SEND TO FILE OF OM01247 FAILED' and calls the error handler
[Send DB2 Error Notification to Support]
The return code indicates a DB2 error condition → An error notification containing the SQL code is sent to the support team and message queue is purged
[Log Send Failure Error]
The backup email send service also returns a failure status → The system logs the error message 'SEND TO FILE OF OM01247 FAILED' and calls the error handling routine
[LTERM Available for Reference?]
The system checks if LTERM process information is available and not empty → Processing continues with LTERM if available, otherwise an error message is generated indicating no LTERM found
[Add Error Message: No LTERM Found]
The system attempts to route messages → An error message 'NO LTERM FOR THIS REFERENCE NUMBER' is added to the message text and MST entry
[Check All Merlin User IDs]
The system validates each Merlin ID against the EMTZ user validation system → Valid Merlin IDs are confirmed for use, invalid IDs trigger error handling
[Add Error Message: DC&P Merlin ID Invalid]
The system processes the invalid Merlin ID → An error message 'DC&P MERLIN USERID INVALID' is added with the invalid ID number
[Error Type?]
If the error context (train vs cargo) → The message is routed to train-specific recipients if it's a train error, otherwise to cargo-specific recipients
[Add Invalid ID Error Message]
The status code is not spaces (indicating failure) → The system adds an error message 'SUPERVISOR MERLIN USERID INVALID' with the invalid ID and clears the user Merlin field
[Terminal Configuration Found?]
The table lookup returns a non-zero status indicating no configuration found → The terminal configuration segment is cleared to spaces
[Validate Supervisor Merlin ID in System]
The system queries the EMTZ segment to validate the supervisor Merlin ID → The validation result determines if the ID is valid or invalid
[Generate Invalid Supervisor ID Error Message]
The system processes the validation failure → An error message 'SUPERVISOR MERLIN USERID INVALID' is added to both text and MST message arrays with the invalid ID included
[Is Supervisor Merlin ID Valid?]
The system validates the supervisor Merlin ID → If the status code is blank, the supervisor Merlin ID is set as valid, otherwise an invalid supervisor ID error message is added and the supervisor Merlin ID is cleared
[Add DC-P Invalid ID Error Message]
The DC-P ID found flag is set to false (not found) → An error message 'DC&P MERLIN USERID INVALID' is added to the message text and MST entry
[Send Copy to CAERROR File]
Additional logging is required → A copy of the message is sent to the CAERROR destination file
[Set Recipient to OM01247 for Error File]
The error file recipient is being configured → The recipient is set to 'OM01247' for the error file destination
[Send to CAERROR Destination]
The system sends the audit copy → The message is sent via EMCSEND2 service to the CAERROR destination
[Prepare Error Message Content]
The system prepares the message content → The formatted subject line is copied to the first line of the message text
[Send Error Notification to Support]
The system sends the notification → The messaging service is called with sender, recipient, subject, and message content
[Log Error Message Send Failure]
The message send operation fails → An error message 'SEND TO FILE OF OM01247 FAILED' is logged and the system error handler is called
[Table T2 Found?]
The test configuration table T2 lookup is performed → If the table is not found, an error message 'T2 CHECK TABLE ENTRY NOT FOUND' is reported and processing stops
[Report Table Not Found Error]
The test configuration table T2 cannot be found or accessed → The system reports error message 'T2 CHECK TABLE ENTRY NOT FOUND' and terminates processing
[Get Standardized Error Text]
The system looks up the error code in the MS table using either GCW122-MSG-NUM or the first 3 characters of the free-form message → The system retrieves the corresponding English text from the message table if the lookup is successful
[Use Standard Error Message]
The table lookup returns a successful result with error text found → The system uses the English text from the message table (GCSTBRT-MS-ENG-TEXT) as the error message content
[Use Free-Form Error Message]
The table lookup fails to find standardized error text → The system uses the original free-form message text (TED-02-FREE-FORM-MSG) and adds an additional error message indicating the lookup failure
[Add Error Context Information]
The error message is being prepared for distribution → The system adds the copy of bad data element (TED-07-COPY-BAD-DATA-ELMT) to provide context about what caused the error
[Primary Delivery Successful?, Default Delivery Successful?]
The system checks the return status flag from the messaging service → If return status flag equals zero or successful indicator, delivery is considered successful, otherwise it is considered failed
[Table Entry Found?]
The table entry retrieval returns a non-zero status code → An error message 'T2 CHECK TABLE ENTRY NOT FOUND' is displayed and processing terminates

As an EDI Gateway Service,
I want to orchestrate and execute all EBCLGIO2 EDI data mapping and validation logic,
So that I can ensure strict compliance with US Customs (P140) automated payload constraints in a single consolidated service.

Prerequisites & Setup

None explicitly identified in logic extraction.

Core Acceptance Criteria

[6:Unqualified Database Access]
Unqualified database access is performed → Call CIMS with function code and PCB, if returned segment name is EBSLGNR then transform data through EBSNPNR format to EBSNRNR format, if returned segment name is EBSLGMC then transform data through EBSMPMC format to EBSMCMC format
[7:Shipment Root Access]
Database access routing is determined → Call EBCLGBC handler with communication area, work area, and segment data
[8:Bill Information Access]
Database access routing is determined → Call EBCLGKS handler with communication area, work area, and segment data
[9:Commodity Access]
Database access routing is determined → Call EBCLGCM handler with communication area, work area, and segment data
[10:Rate Charges Access]
Database access routing is determined → Call EBCLGRT handler with communication area, work area, and segment data
[11:Shipment Conditions Access]
Database access routing is determined → Call EBCLGDP handler with communication area, work area, and segment data
[12:Hazardous Material Access]
Database access routing is determined → Call EBCLGHZ handler with communication area, work area, and segment data
[13:Hazardous Information Access]
Database access routing is determined → Call EBCLGHI handler with communication area, work area, and segment data
[14:Hazardous Materials Access]
Database access routing is determined → Call EBCLGHM handler with communication area, work area, and segment data
[15:Equipment Details Access]
Database access routing is determined → Call EBCLGCR handler with communication area, work area, and segment data
[16:Information Segment Access CX]
Database access routing is determined → Call EBCLGCX handler with communication area, work area, and segment data
[17:Information Segment Access CY]
Database access routing is determined → Call EBCLGCY handler with communication area, work area, and segment data
[18:Information Segment Access AR]
Database access routing is determined → Call EBCLGAR handler with communication area, work area, and segment data
[19:Secondary Index Access]
Database access routing is determined → Call EBCLGSI handler with communication area, work area, and segment data
[20:Destination Station Root Access]
Database access routing is determined → Call EBCLGNR handler with communication area, work area, and segment data
[21:Information Segment Access CG]
Database access routing is determined → Call EBCLGCG handler with communication area, work area, and segment data
[22:Stop-off Name Access]
Database access routing is determined → Call EBCLGSO handler with communication area, work area, and segment data
[23:Stop-off Address Access]
Database access routing is determined → Call EBCLGSD handler with communication area, work area, and segment data
[24:Information Segment Access SC]
Database access routing is determined → Call EBCLGSC handler with communication area, work area, and segment data
[25:Information Segment Access SA]
Database access routing is determined → Call EBCLGSA handler with communication area, work area, and segment data
[26:Information Segment Access RO]
Database access routing is determined → Call EBCLGRO handler with communication area, work area, and segment data
[27:Information Segment Access TD]
Database access routing is determined → Call EBCLGTD handler with communication area, work area, and segment data
[28:Origin Station Root Access]
Database access routing is determined → Call EBCLGMC handler with communication area, work area, and segment data
[29:Transit Inbound Access]
Database access routing is determined → Call EBCLGMI handler with communication area, work area, and segment data
[30:Transit Data Access]
Database access routing is determined → Call EBCLGMD handler with communication area, work area, and segment data
[31:Information Segment Access OA]
Database access routing is determined → Call EBCLGOA handler with communication area, work area, and segment data
[32:Information Segment Access MS]
Database access routing is determined → Call EBCLGMS handler with communication area, work area, and segment data
[33:Pended Destination Access]
Database access routing is determined → Call EBCLGZD handler with communication area, work area, and segment data
[Execute Database Call with Function Code]
The system executes the database call → The database call is made using CIMS with the function code, PCB, and segment data
[Check Segment Name]
The system checks the returned segment name → If segment name equals 'EBSLGNR', process as NR segment data; if segment name equals 'EBSLGMC', process as MC segment data
[Process NR Segment Data]
The system processes the NR segment data → The segment data is moved to EBSNPNR-DATA format and then EBSNRNR-DATA is moved to the output segment
[Process MC Segment Data]
The system processes the MC segment data → The segment data is moved to EBSMPMC-DATA format and then EBSMCMC-DATA is moved to the output segment
[Check Segment Type for EBSBCBC]
The segment type is EBSBCBC or the secondary index indicator is set to YES → The system routes the request to the EBSBCBC shipment root segment access handler
[Call EBCLGBC Module]
The system needs to perform the database operation on EBSBCBC segment → The system calls the EBCLGBC module with communication area, work area, and segment buffer parameters
[Segment Type = EBSBCKS?]
The segment type is evaluated for Bill Information access → If segment type equals EBSBCKS then route to Bill Information handler, otherwise continue to next segment type check
[Call EBCLGKS Module]
The system needs to access Bill Information data → Call the EBCLGKS module with communication area, working storage area, and segment data area parameters to Execute the Bill Information access operation
[Segment Type = EBSBCCM?]
The segment type equals EBSBCCM (EDI Bill of Lading Commodity segment) → The system routes the request to the commodity access processing module
[Call Commodity Access Module EBCLGCM]
The system needs to perform database operations on commodity data → The system calls the EBCLGCM commodity access module with communication area ISCOM, work area EBWLGIO2, and segment data EBLG-SEGMENT as parameters
[Rate Charges Access Request]
If the segment type for routing → The system should route the request to the rate charges handler (EBCLGRT) to access the EBSBCRT segment
[Call Rate Charges Handler]
The system needs to access rate charges data → The system should call program EBCLGRT with communication area ISCOM, work area EBWLGIO2, and segment data EBLG-SEGMENT as parameters
[Segment Type = EBSBCDP?]
The segment type equals EBSBCDP-LIT (shipment conditions segment identifier) → The system routes the request to the shipment conditions access handler
[Call EBCLGDP Module]
The system needs to process shipment conditions data operations → The system calls the EBCLGDP module with communication area, working storage, and segment data parameters to handle the shipment conditions access
[Access EBSBCHZ Segment]
The segment type equals EBSBCHZ-LIT (hazardous material segment identifier) → The system calls the hazardous material handler 'EBCLGHZ' with ISCOM, EBWLGIO2, and EBLG-SEGMENT parameters to access the hazardous material data segment
[Segment Type = EBSBCHI?]
The segment type equals EBSBCHI (hazardous information segment) → The system routes the request to the hazardous information access handler (EBCLGHI)
[Call EBCLGHI Module]
The system needs to process hazardous information data operations → The system calls the EBCLGHI module with communication area (ISCOM), working storage (EBWLGIO2), and segment data (EBLG-SEGMENT) parameters to handle the hazardous information processing
[Call Hazardous Materials Handler]
The system needs to process the hazardous materials request → The system should call the EBCLGHM program with ISCOM, EBWLGIO2, and EBLG-SEGMENT parameters
[Call Equipment Details Handler EBCLGCR]
The system needs to process equipment details data → The system calls the EBCLGCR equipment details handler program with communication area ISCOM, working storage EBWLGIO2, and segment buffer EBLG-SEGMENT
[Information Segment Access CX - Access EDI Bill of Lading information segment (EBSBCCX)]
The segment type matches EBSBCCX literal value → The system calls the EBCLGCX module to handle the EDI Bill of Lading information segment CX operations
[Information Segment Access CY - Access EDI Bill of Lading information segment (EBSBCCY)]
If the segment type for routing → The system calls the EBCLGCY module to handle EDI Bill of Lading information segment CY operations
[Process AR Information Segment]
The system processes the segment access request → The system calls the EBCLGAR module with communication area, working storage, and segment data parameters to handle AR information segment operations
[Secondary Index Access - Access EDI Bill of Lading secondary index segment (EBSBCSI)]
The system processes the access request for this segment type → The system calls the EBCLGSI module passing the communication area (ISCOM), working storage (EBWLGIO2), and segment data (EBLG-SEGMENT) to handle the secondary index operation
[Destination Station Root Access - Access EDI Bill of Lading destination station root segment (EBSNRNR)]
The system processes the access request for the destination station root segment → The system calls the EBCLGNR module with the communication area, working storage, and segment buffer to access the EBSNRNR segment and returns control to the calling program
[Access EBSNRCG Segment]
The system processes the segment access request → The system calls the EBCLGCG module with communication area ISCOM, work area EBWLGIO2, and segment data EBLG-SEGMENT to handle the EDI Bill of Lading information segment operations
[Segment Type = EBSNRSO?]
The segment type is evaluated for stop-off name processing → The system should identify if the segment type equals EBSNRSO and route accordingly
[Call Stop-off Name Handler]
The system needs to process stop-off name data operations → The system should call the EBCLGSO handler with communication area, working storage, and segment data parameters
[Stop-off Address Access - Access EDI Bill of Lading stop-off address segment (EBSNRSD)]
The segment type equals EBSNRSD-LIT (stop-off address segment identifier) → The system calls the stop-off address handler (EBCLGSD) with communication area, working storage, and segment data parameters to process the stop-off address access request
[Information Segment Access SC - Access EDI Bill of Lading information segment (EBSNRSC)]
The segment type validation determines it matches EBSNRSC literal value → The system calls the EBCLGSC module with communication area, working storage, and segment data to process the EDI Bill of Lading information segment access
[Segment Type = EBSNRSA?]
The segment type equals EBSNRSA → The system should route the request to Execute SA Information Segment access processing
[Call EBCLGSA Module]
The system needs to process the SA Information Segment request → The system should call the EBCLGSA module with the communication area, work area, and segment data to handle the SA information segment processing
[Information Segment Access RO - Access EDI Bill of Lading information segment (EBSNRRO)]
The segment type matches EBSNRRO-LIT → The system calls the EBCLGRO module to handle EDI Bill of Lading information segment operations
[Information Segment Access TD - Access EDI Bill of Lading information segment (EBSNRTD)]
The segment type equals EBSNRTD-LIT → The system calls the EBCLGTD module with ISCOM, EBWLGIO2, and EBLG-SEGMENT parameters to handle the TD information segment access
[Origin Station Root Access - Access EDI Bill of Lading origin station root segment (EBSMCMC)]
The system processes the segment access request → The system calls the EBCLGMC module with communication area (ISCOM), working storage (EBWLGIO2), and segment data (EBLG-SEGMENT) to handle the origin station root segment operations
[Transit Inbound Access Request]
The segment type equals EBSMCMI-LIT → The system should route the request to the Transit Inbound handler A230-ACCESS-EBSMCMI
[Call Transit Inbound Handler EBCLGMI]
The A230-ACCESS-EBSMCMI section is performed → The system should call program EBCLGMI with communication area ISCOM, work area EBWLGIO2, and segment data EBLG-SEGMENT
[Call EBCLGMD Module]
The system processes the transit data access request → The system calls the EBCLGMD module with communication area, working storage, and segment buffer parameters to execute the transit data operation
[Information Segment Access OA - Access EDI Bill of Lading information segment (EBSMCOA)]
The segment type equals EBSMCOA literal value → The system calls EBCLGOA module with communication area, working storage, and segment data parameters to process the EBSMCOA segment
[Call EBCLGOA Module]
The system needs to process the EDI Bill of Lading segment → The system calls EBCLGOA program passing ISCOM communication area, EBWLGIO2 working storage, and EBLG-SEGMENT data structure
[Call EBCLGMS Module]
The system needs to access the EBSMCMS information segment → The system calls the EBCLGMS module with communication area ISCOM, work area EBWLGIO2, and segment data EBLG-SEGMENT
[Access EBSMCZD Segment]
The segment type matches EBSMCZD literal value → The system calls the EBCLGZD program with communication area, working storage, and segment data to process the pended destination access request
[Execute Unqualified Database Call]
The system processes the unqualified call → The system executes a database call using CIMS with the provided function code, PCB, and segment parameters
[Check Segment Name]
If the segment name → The system identifies whether the segment is 'EBSLGNR' for NR processing or 'EBSLGMC' for MC processing
[Process NR Segment Data]
The system processes the NR segment data → The system moves the segment data to EBSNPNR-DATA structure, then transforms it to EBSNRNR-DATA format, and finally moves the clean data back to EBLG-SEGMENT
[Process MC Segment Data]
The system processes the MC segment data → The system moves the segment data to EBSMPMC-DATA structure, then transforms it to EBSMCMC-DATA format, and finally moves the clean data back to EBLG-SEGMENT

Structural Validations

[Error Handling]
Segment type routing is attempted → Set segment type in error message and call error handler CERR with invalid segment type message
[Generate Error Message]
The function code is not one of the valid operations (GHU, GU, GHN, GHNP, GN, GNP, ISRT, DLET, REPL) → The invalid function code is moved to error field CERR-FUNC-CODE and error message CERR-FUNC-CODE-MSG is set to CC-ERROR-MESSAGE
[Call Error Handler]
Function code validation fails → The CERR error handling program is called with ISCOM parameter to process the error
[Is Operator Valid?]
The operator is not one of the valid values: EQ (equals), GE (greater than or equal), GT (greater than), LE (less than or equal), LT (less than), with their multiple literal representations → The system generates an operator validation error with the invalid operator value and corresponding error message
[Generate Operator Error]
The operator validation fails → The system moves the invalid operator value to the error operator field, sets the operator error message to the error message field, and calls the error handling program with the communication area
[Generate Function Code Error]
The function code validation fails → Move the invalid function code to the error field, set the function index error message, and call the CERR error handler
[Set Invalid Boolean Operator Error]
The system validates the boolean operator and the operator is not '*', '&', '+', or '|' → The system sets the invalid boolean operator value in error data and sets boolean operator error message for user notification
[Check if OPERATOR-2 equals: = or EQ or GE or >= or GT or > or LE or <= or LT or < or NE]
The second operator validation is performed → The system accepts the operator if it equals any valid comparison operator (EQ, GE, GT, LE, LT with their various literal representations), otherwise generates an invalid second operator error message and calls error handling routine
[Set error message for invalid second operator]
The operator validation fails → The system moves the invalid operator value to CERR-OPERATOR-2, sets the error message to CERR-OPERATOR2-MSG in CC-ERROR-MESSAGE, and calls the CERR error handling routine with ISCOM parameter
[Segment Type = EBSBCHM?]
The segment type is evaluated for hazardous materials processing → The system should identify if the segment type equals EBSBCHM literal value
[Validate Segment Type is EBSBCCR]
The segment type is EBSBCCR-LIT (Equipment Details segment) → The system proceeds to access the equipment details handler
[Validate Segment Type is EBSMCMS]
The segment type is EBSMCMS-LIT → The system proceeds to access the EBSMCMS information segment

As an EDI Gateway Service,
I want to orchestrate and execute all GCCCCIO2 EDI data mapping and validation logic,
So that I can ensure strict compliance with US Customs (P140) automated payload constraints in a single consolidated service.

Prerequisites & Setup

[1:Initialize Program Parameters]
Function code is GU (Get Unique) → Clear all cargo segment data areas (52, 53, 54, 55, 56) and working storage arrays
[Initialize Secondary Segment Structure]
The fetch process begins → The secondary segment data structure (GCSCCS00) should be cleared to spaces
[Initialize Segment Type 52 Processing]
The segment 52 processing routine is invoked → The system clears the communication areas and working storage for segment processing
[Initialize Segment Type 53 Processing]
The segment 53 processing routine is initiated → The communication areas are cleared and record type is set to '53'
[Initialize Segment 54 Processing]
The segment 54 processing routine is initiated → The communication areas are cleared and the record type is set to '54'
[Initialize Segment Type 55 Processing]
The segment 55 processing routine is initiated → The system clears the communication work area and segment data area, and sets the record type to '55'
[Initialize Segment Type 56 Processing]
The segment type 56 processing is initiated → The system clears the working communication area and segment data area, and sets the record type to '56'
[Initialize Secondary Segment Key]
The system initializes the navigation parameters → The secondary segment structure is cleared and the CCN key is set from the cargo root key

Core Acceptance Criteria

[Process All Segments?]
First segment name is set to ALL → Process cargo root segment first, then process all secondary segments if root processing succeeds
[Fetch All Segments?]
First segment name is set to FETCH ALL → Process cargo root segment first, then fetch all secondary segments if root processing succeeds
[4:Fetch All Secondary Segments]
Fetching all secondary segments for the CCN key → Retrieve each segment, validate sequence numbers, and route data to appropriate segment type arrays (52, 53, 54, 55, 56) based on record type
[3:Process All CA Cargo Segments]
Function code is GU (Get Unique) → Fetch all secondary segments, otherwise process each segment type individually (52, 53, 54, 56, 55)
[5:Process Selected Segments]
Processing selected segments from the segment names array → For each requested segment (up to 10), process the corresponding segment type (root, 52, 53, 54, 55, 56) based on segment name and function code
[7:Process Cargo Segment Type 52]
Processing each sequence up to maximum allowed for segment 52 → Skip empty keys for update/delete operations, set sequence numbers, use existing data for update/delete or retrieve and store data for get operations
[8:Process Cargo Segment Type 53]
Processing each sequence up to maximum allowed for segment 53 → Skip empty keys for update/delete operations, set sequence numbers, use existing data for update/delete or retrieve and store data for get operations
[9:Process Cargo Segment Type 54]
Processing each sequence up to maximum allowed for segment 54 → Skip empty keys for update/delete operations, set sequence numbers, use existing data for update/delete or retrieve and store data for get operations
[10:Process Cargo Segment Type 55]
Processing sequences and encountering empty keys with update/delete operations → If return status is OK Execute delete operation, if return status is not OK Execute replace operation, otherwise process normally with sequence handling
[11:Process Cargo Segment Type 56]
Processing each sequence up to maximum allowed for segment 56 → Skip empty keys for update/delete operations, set sequence numbers, use existing data for update/delete or retrieve and store data for get operations
[Function Code is GET?]
The function code is GET (GU) → All cargo segment data areas must be cleared for fresh data retrieval
[Clear Root Segment Data]
Preparing for fresh cargo data retrieval → The root cargo segment data area is cleared to spaces
[Clear Type 52 Segment Data]
Preparing Type 52 cargo segment for data retrieval → The Type 52 segment data area is cleared to spaces
[Clear Type 53 Segment Data]
Preparing Type 53 cargo segment for data retrieval → The Type 53 segment data area is cleared to spaces
[Clear Type 54 Segment Data]
Preparing Type 54 cargo segment for data retrieval → The Type 54 segment data area is cleared to spaces
[Clear Type 55 Segment Data]
Preparing Type 55 cargo segment for data retrieval → The Type 55 segment data area is cleared to spaces
[Clear Type 56 Segment Data]
Preparing Type 56 cargo segment for data retrieval → The Type 56 segment data area is cleared to spaces
[Clear Working Arrays]
Finalizing data area preparation for GET operations → All working storage arrays for cargo segments are cleared to spaces
[Input Parameters Valid]
CCN key is provided AND segment names are specified → Allow the system to continue to main cargo data processing
[Function Code = GU?]
The function code is GU (Get Unique) → The system should fetch all secondary segments instead of processing individual segment types
[Fetch All Secondary Segments]
The system retrieves secondary segments for the CCN key → Each segment should be routed to the appropriate data array based on its record type (52, 53, 54, 55, or 56)
[Process Cargo Segment Type 52]
The system processes cargo segments → Each segment type (52, 53, 54, 55, 56) should be processed individually in sequential order
[Fetch All Secondary Segments]
The record type is '52', '53', '54', '55', or '56' → The segment data should be moved to the corresponding data array for that record type
[Fetch All Secondary Segments]
The return status is not OK, end of file is reached, or the CCN key changes → The system should stop processing segments
[Set CCN Key for Search]
Preparing to search for secondary cargo segments → The CCN key should be set in the secondary segment search structure
[Get First Secondary Cargo Segment]
Starting the fetch process for secondary cargo segments → The system should retrieve the first secondary cargo segment record
[More Segments Available?]
Checking if more segments are available for processing → Continue processing if return status is OK and not end-of-file, otherwise terminate the fetch process
[Segment Type = '52'?]
Determining the segment type for proper storage → Route to type 52 storage if the record type is '52', otherwise check for type 53
[Segment Type = '53'?]
Continuing to determine the segment type for proper storage → Route to type 53 storage if the record type is '53', otherwise check for type 54
[Segment Type = '54'?]
Continuing to determine the segment type for proper storage → Route to type 54 storage if the record type is '54', otherwise check for type 55
[Segment Type = '55'?]
Continuing to determine the segment type for proper storage → Route to type 55 storage if the record type is '55', otherwise check for type 56
[Segment Type = '56'?]
Determining the final segment type for proper storage → Route to type 56 storage if the record type is '56', otherwise proceed to get next segment
[Store in Type 52 Array]
Storing the segment data for later use → The segment data should be stored in the type 52 data array at the sequence number position
[Store in Type 53 Array]
Storing the segment data for later use → The segment data should be stored in the type 53 data array at the sequence number position
[Store in Type 54 Array]
Storing the segment data for later use → The segment data should be stored in the type 54 data array at the sequence number position
[Store in Type 55 Array]
Storing the segment data for later use → The segment data should be stored in the type 55 data array at the sequence number position
[Store in Type 56 Array]
Storing the segment data for later use → The segment data should be stored in the type 56 data array at the sequence number position
[Get Next Secondary Segment]
Continuing the fetch process for remaining segments → The system should retrieve the next secondary cargo segment record
[End Fetch Process]
The fetch loop determines no more processing is needed → The fetch process should terminate and return control to the calling process
[Store in Type 52 Array]
The system processes the segment for storage → The segment data is stored in the Type 52 array at the position corresponding to the sequence number
[Store in Type 53 Array]
The system processes the segment for storage → The segment data is stored in the Type 53 array at the position corresponding to the sequence number
[Store in Type 54 Array]
The system processes the segment for storage → The segment data is stored in the Type 54 array at the position corresponding to the sequence number
[Store in Type 55 Array]
The system processes the segment for storage → The segment data is stored in the Type 55 array at the position corresponding to the sequence number
[Store in Type 56 Array]
The system processes the segment for storage → The segment data is stored in the Type 56 array at the position corresponding to the sequence number
[Process CA Cargo Root Segment for Update/Delete]
If the segment type in the selection array → The system processes the cargo root segment
[Process Cargo Segment Type 52]
If the segment type in the selection array → The system processes cargo segment type 52
[Process Cargo Segment Type 53]
If the segment type in the selection array → The system processes cargo segment type 53
[Process Cargo Segment Type 54]
If the segment type in the selection array → The system processes cargo segment type 54
[Process Cargo Segment Type 55]
If the segment type in the selection array → The system processes cargo segment type 55
[Process Cargo Segment Type 56]
If the segment type in the selection array → The system processes cargo segment type 56
[Move to Next Segment Selection]
The system processes selected segments → The system iterates from position 1 by 1 until position 10 or until segment name is empty
[Root Segment Selected?]
If the segment type at array position I → The system processes the root cargo segment
[Type 52 Segment Selected?]
If the segment type at array position I → The system processes the type 52 cargo segment
[Type 53 Segment Selected?]
If the segment type at array position I → The system processes the type 53 cargo segment
[Type 54 Segment Selected?]
If the segment type at array position I → The system processes the type 54 cargo segment
[Type 55 Segment Selected?]
If the segment type at array position I → The system processes the type 55 cargo segment
[Type 56 Segment Selected?]
If the segment type at array position I → The system processes the type 56 cargo segment
[Process Root Segment]
The system determines root segment processing is required → The system calls the root cargo processing function
[Process Type 52 Segment]
The system determines type 52 segment processing is required → The system calls the type 52 cargo processing function
[Process Type 53 Segment]
The system determines type 53 segment processing is required → The system calls the type 53 cargo processing function
[Process Type 54 Segment]
The system determines type 54 segment processing is required → The system calls the type 54 cargo processing function
[Process Type 55 Segment]
The system determines type 55 segment processing is required → The system calls the type 55 cargo processing function
[Process Type 56 Segment]
The system determines type 56 segment processing is required → The system calls the type 56 cargo processing function
[Move to Next Array Position]
The system completes processing for the current segment → The system increments the array position counter to move to the next segment
[Skip Processing Flag Set?]
The skip processing flag (88-RETURN-SKIP-PRCS) is set to true → The system should exit processing without performing any cargo operations
[Save Current Root Segment Data]
Processing begins for the root segment → The system should save the current GCSCCRT data to WS-GCSCCRT-SAVE for potential restoration
[Clear Communication Area]
Preparing for database operation → The system should clear GCWCCIO communication area and restore the saved accept status
[Set Root Segment Processing Flag]
Setting up for root segment processing → The system should set GCWCCIO-SEG-GCSCCRT flag to true and copy the function code and security index from input parameters
[Set Get Function]
Setting up the database operation → The system should set GCWCCIO-FUNC-GU flag to true
[Set Update/Insert/Delete Function]
Setting up the database operation → The system should use the function code from input parameters (GCWCCIO2-FUNC-CODE)
[Call Database Operation]
Executing the root segment operation → The system should call GCCCCIO program with communication area and root segment data
[Database Operation Successful?]
The operation fails (CC-STATUS-CODE is not spaces) → The system should set data not in range flag, set return status to not OK, and clear root segment data for Get operations
[Set Record Type to '52']
The record type needs to be identified for database operations → The system sets the record type field to '52'
[J > Maximum Sequence?]
The current sequence counter J is compared against the maximum sequence limit → The system continues processing if J is within limits or terminates the loop if J exceeds the maximum sequence count
[Empty Key AND Update/Delete Function?]
The sequence has an empty key identifier → The system skips processing this sequence and continues to the next sequence
[Set Sequence Number J]
The sequence number needs to be established for the current record → The system sets the sequence number field to the current counter value J
[Load Existing Data for Sequence J]
The operation requires existing data for the current sequence → The system loads the existing data from the working storage array for the specified sequence
[Execute Database Operation for Segment 52]
A database operation needs to be executed → The system calls the database interface to Execute the requested operation on the segment record
[Store Retrieved Data to Segment 52]
Data has been retrieved from the database → The system stores the retrieved data to the cargo segment 52 structure and working storage array
[Set Record Type to '53']
The record type needs to be identified → The record type field is set to '53'
[J > Maximum Sequence?]
The current sequence number J is compared against the maximum sequence limit for segment 53 → Processing continues if J is less than or equal to maximum sequence limit, otherwise processing terminates
[Empty Key AND Update/Delete Operation?]
The segment key is empty AND the function is either update or delete operation → The current sequence is skipped and processing continues with the next sequence
[Set Sequence Number J]
The sequence number needs to be established for the current record → The sequence number is set to the current loop counter value J
[Update or Delete Operation?]
The function code indicates an update or delete operation → The existing data from working storage array is moved to the processing area before database operations
[Move Working Storage Data to Processing Area]
The working storage contains existing data for the current sequence → The data from working storage array position J is moved to the processing area
[Execute Database Operations for Segment 53]
Database operations need to be executed → The appropriate database operation is performed based on the function code
[Get Operation?]
The function code indicates a get operation → The retrieved data is stored in both the segment area and working storage array
[Move Retrieved Data to Segment 53]
The operation is a get function → The retrieved data is moved to the segment 53 output area
[Move Retrieved Data to Working Storage Array]
The operation is a get function → The retrieved data is moved to the working storage array at position J
[Increment Sequence Counter J]
The sequence processing needs to continue → The sequence counter J is incremented by 1 to process the next sequence
[Set Record Type to '54']
The record type needs to be identified → The record type field is set to '54'
[Start Sequence Loop J=1]
The processing loop is initiated → The sequence counter J starts at 1 and increments until the maximum sequence limit is reached
[Empty Key AND Update/Delete Function?]
If whether to process the record → The record is skipped and processing continues with the next sequence
[Skip This Sequence]
The skip condition is triggered → Processing moves to the next sequence without performing any operations on the current record
[Set Sequence Number]
The sequence number needs to be assigned → The current loop counter J is assigned as the sequence number for the record
[Update or Delete Function?]
The function type is evaluated → If the function is update or delete, existing data from working storage is used; otherwise, the operation proceeds without pre-loading data
[Move Working Storage Data to Processing Area]
The function is update or delete → The corresponding data from the working storage array is moved to the processing area
[Execute Database Operation for Segment 54]
The database operation is executed → The system performs the requested operation (get, update, delete, or insert) on the cargo segment 54 record
[Get Function?]
The function type is evaluated → If the function is a get operation, the retrieved data is processed and stored; otherwise, processing continues to the next sequence
[Move Retrieved Data to Segment 54]
The function is a get operation → The retrieved data is moved to the cargo segment 54 data structure
[Store Data in Working Storage Array]
The get operation is completed → The data is also stored in the corresponding working storage array position
[Increment Sequence Counter]
Processing of the current sequence is complete → The sequence counter J is incremented to process the next sequence
[Set Record Type to '55']
The record type needs to be identified → The system sets the record type field to '55'
[Start Sequence Loop J=1]
Processing begins for segment type 55 → The system starts a loop with sequence counter J beginning at 1 and continues until J exceeds the maximum sequence limit for segment 55
[Empty Key AND Update/Delete Function?]
The function is either update or delete → The system applies special deletion logic based on the current return status rather than standard processing
[Set Delete Function Parameters]
Special deletion processing is required → The system sets the function to delete, configures segment 55 parameters, sets index as not used, moves the sequence number, clears cargo data, and executes the deletion operation
[Set Replace Function Parameters]
Special replacement processing is required → The system sets all segments for processing, sets the function to replace, configures delete function flag, and sets index as not used
[Set Current Sequence Number]
The sequence number needs to be established for the record → The system moves the current J value to the working sequence field and then to the segment 55 key sequence field
[Move Working Storage Data to Processing Area]
Data needs to be prepared for the database operation → The system moves the working storage data for the current sequence from the segment 55 array to the processing area
[Execute Database Operation for Segment 55]
The database operation needs to be executed → The system calls the database processing routine with the prepared segment data
[Move Result to Segment 55 Output]
Data is successfully retrieved from the database → The system moves the retrieved data to both the segment 55 output area and the working storage array for the current sequence
[Exit Loop - Set J Beyond Maximum]
The return status indicates failure → The system forces loop termination by setting the sequence counter J to a value beyond the maximum sequence limit
[Is Return Status OK?]
The return status is checked for OK condition → If return status is OK, proceed with direct delete operation, otherwise proceed with replace operation
[Set Delete Function Parameters]
Delete operation is selected as the processing path → Clear communication area, set accept status to 'GE', set delete function flag, and configure index as not used
[Set Segment Type 55 for Delete]
Segment type needs to be specified for the delete operation → Set segment type to GCSCCS55 for targeted deletion
[Move Sequence Number to Key]
The sequence number needs to be assigned to the segment key → Move the current sequence number to the segment key sequence field
[Set Replace Function Parameters]
Replace operation is selected as the processing path → Clear communication area, set accept status to 'GE', set replace function flag, and configure index as not used
[Set All Segments for Replace]
Segment scope needs to be specified for the replace operation → Set segment processing to ALL segments mode
[Continue Processing Next Sequence]
Processing needs to continue to next sequence → Skip normal segment operation and continue with next sequence iteration
[Process Normal Segment Operation]
Normal processing path is selected → Execute standard segment processing including sequence assignment, data movement, and cargo processing call
[Empty Key AND Update/Delete Function?]
The segment key at sequence J is empty → The system skips processing for this sequence and continues to the next sequence
[Set Sequence Number J]
A valid sequence needs to be processed → The system moves the counter J to the working sequence field and assigns it to the segment key sequence
[Move Segment Data to Working Storage]
The segment data needs to be prepared for the operation → The system moves the segment data from the working array at sequence J to the segment processing area
[Execute Database Operation for Segment 56]
A database operation needs to be executed → The system calls the data access module to Execute the operation on the segment data
[Move Result to Segment 56 Structure]
The function code is get (GU) → The system moves the retrieved data to both the segment structure and the working array at sequence J
[Set Accept Status to 'GE' for Get]
The function code is GU (Get Unique) → The accept status should be set to 'GE' and the CCN key should be moved to the segment key
[Set Accept Status to 'GB' for Get Next]
The function code is GN (Get Next) → The accept status should be set to 'GB'
[Set Accept Status to 'IIGE' for Insert/Update/Delete]
The function code is neither GU nor GN (indicating insert, update, or delete operation) → The accept status should be set to 'IIGE'
[Set Segment Type to GCSA2RT]
The database interface parameters need to be set → The segment type should be set to GCSA2RT and the function code should be set from the working storage function code
[Call Database Interface GCCCCIO]
The database operation needs to be executed → The system should call program 'GCCCCIO' with the communication area, interface parameters, and segment data
[Status Code Empty?]
The database interface returns a status code → If the status code is empty (spaces), the operation is successful; otherwise, the operation failed
[Set Return Status OK]
The database status code is empty (indicating success) → The return status should be set to OK (88-RETURN-OK)
[Set Return Status Not OK]
The database status code is not empty (indicating failure) → The return status should be set to Not OK (88-RETURN-NOT-OK)
[Set Record Type to '0']
The system sets up search parameters → The record type is set to all zeros as the starting point for segment retrieval
[Set Sequence to '0']
The system sets up search parameters → The sequence number is set to all zeros as the starting point for segment retrieval
[Execute Get First Secondary Segment]
The system executes the get first secondary segment operation with greater than operator → The first secondary segment matching the criteria is retrieved or an appropriate status is returned
[First Segment Found?, Next Segment Found?]
The system checks the operation result → If the status code is spaces, the segment is found and processing continues, otherwise navigation is complete
[Store in Type 52 Array]
The system processes the segment data routing → The segment data is stored in the type 52 data array at the position indicated by the sequence number
[Store in Type 53 Array]
The system processes the segment data routing → The segment data is stored in the type 53 data array at the position indicated by the sequence number
[Store in Type 54 Array]
The system processes the segment data routing → The segment data is stored in the type 54 data array at the position indicated by the sequence number
[Store in Type 55 Array]
The system processes the segment data routing → The segment data is stored in the type 55 data array at the position indicated by the sequence number
[Store in Type 56 Array]
The system processes the segment data routing → The segment data is stored in the type 56 data array at the position indicated by the sequence number
[Execute Get Next Secondary Segment]
The system executes the get next secondary segment operation → The next secondary segment in sequence is retrieved or an appropriate status is returned
[End of File Reached?]
The system checks for end of file condition → If the status code indicates end of file (GE or GB), navigation is complete
[Store in Type 52 Array WS-GCSCCS52-DATA]
The segment record type equals '52' → Store the complete segment data in the Type 52 array at the sequence position
[Store in Type 53 Array WS-GCSCCS53-DATA]
The segment record type equals '53' → Store the complete segment data in the Type 53 array at the sequence position
[Store in Type 54 Array WS-GCSCCS54-DATA]
The segment record type equals '54' → Store the complete segment data in the Type 54 array at the sequence position
[Store in Type 55 Array WS-GCSCCS55-DATA]
The segment record type equals '55' → Store the complete segment data in the Type 55 array at the sequence position
[Store in Type 56 Array WS-GCSCCS56-DATA]
The segment record type equals '56' → Store the complete segment data in the Type 56 array at the sequence position
[Skip Processing - Continue to Next Segment]
The operation is an update or delete function → The system should skip processing this segment and continue to the next sequence number
[Process Segment Normally]
Any operation type is requested → The system should process the segment normally according to the function code
[Process Segment Normally]
The operation is not an update or delete function → The system should process the segment normally according to the function code

Structural Validations

[2:Validate Input Parameters]
Segment names parameter is empty or spaces → Set parameter segment names error and skip processing
[Root Processing OK?]
Root segment processing returns successful status → Continue with secondary segment processing based on requested operation type
[Set Root Not Found Error]
Root segment processing fails or returns not found status → Set root not found error and skip all secondary segment processing
[4:Fetch All Secondary Segments]
Segment sequence number is not numeric → Set sequence number to default value of 1
[Are Segment Names Empty?]
The segment names parameter is empty (spaces) → Set parameter segment names error flag AND set skip processing flag to prevent further processing
[Fetch All Secondary Segments]
The segment's sequence number is not numeric → The sequence number should be set to 1
[CCN Matches Current Record?]
Validating the record belongs to the correct customer → Continue processing if the segment CCN key matches the search CCN key, otherwise terminate the fetch process
[Segment Retrieved Successfully?]
Checking if the segment was successfully retrieved → Process the segment data if return status is OK and CCN keys match, otherwise get the next segment
[Sequence Number Valid?]
Processing the segment sequence number → Use the existing sequence number if it is numeric, otherwise default to sequence number 1
[Set Sequence to 1]
Processing the segment for storage → The sequence number should be set to 1
[Check Record Type]
The system validates the sequence number before storage → The sequence number is set to 1 as the default value
[More Segments to Check?]
The system completes processing a segment at position I → The system checks if I is less than or equal to 10 and if the segment name at position I is not empty to determine if more segments need processing
[CCN Key Empty?]
The CCN key (WS-CCN-KEY) is empty (spaces) → The system should exit processing without performing any cargo operations
[J > Maximum Sequence?]
The current sequence number J is compared against the maximum sequence limit → Processing continues if J is within limits, otherwise processing terminates
[J > Maximum Sequence?]
The current sequence counter J is evaluated → If J exceeds the maximum sequence limit, the system terminates processing; otherwise, it continues with the current sequence
[Check Segment 55 Empty Key]
The segment key is empty AND the function is update or delete → The system should identify this as a special case requiring deletion logic
[J > Maximum Sequence?]
The sequence counter J is compared against the maximum sequence limit for segment type 56 → If J exceeds the maximum sequence limit, the processing loop terminates
[Clear Segment Data]
The function code is GU (Get Unique) and the database operation was not successful → The segment data (GCSCCS00) should be cleared to spaces
[Sequence Not Numeric?]
The system validates the sequence number format → If the sequence number is not numeric, it is defaulted to 1, otherwise the original value is retained
[Set Sequence to 1]
The system processes the invalid sequence number → The sequence number is set to 1 as the default value
[Same CCN Key?]
The system validates the CCN key consistency → If the segment CCN key matches the original CCN key, processing continues, otherwise navigation is complete

As an EDI Gateway Service,
I want to orchestrate and execute all GCCDESC EDI data mapping and validation logic,
So that I can ensure strict compliance with US Customs (P140) automated payload constraints in a single consolidated service.

Prerequisites & Setup

None explicitly identified in logic extraction.

Core Acceptance Criteria

[2:Process Description Records Loop]
The processing begins → The system iterates through sequence numbers 1 to 46 processing each description record
[Move Description Data to Record Structure]
The system begins record preparation → The description data from input parameter position J is moved to the record structure description field
[Set Sequence Number from Loop Counter]
The sequence number needs to be assigned → The loop counter J value is converted to sequence format and assigned to the record sequence key field
[Set Customer Key in Record]
The database record structure is being prepared → The customer credit number key from the input linkage is moved to the database record key field
[Exit Loop - Operation Failed]
The system detects the operation failure → Processing stops immediately and exits the description record processing loop
[Exit Loop - Operation Failed]
The delete operation returns a failure status → The system sets the loop counter to 47 to exit the processing loop immediately
[Stop Processing - Exit Loop]
The delete operation fails or encounters an error → All further processing is stopped and the loop is exited immediately
[Set Database Segment Type]
The system prepares for database access → The database segment type is set to GCSA2RT
[Set Database Segment Type to GCSA2RT]
The database interface is being configured → The segment type must be set to GCSA2RT to ensure proper record handling

Structural Validations

None explicitly identified in logic extraction.

As an EDI Gateway Service,
I want to orchestrate and execute all GCCDUPCA EDI data mapping and validation logic,
So that I can ensure strict compliance with US Customs (P140) automated payload constraints in a single consolidated service.

Prerequisites & Setup

[Initialize Message Structure]
The system begins generating an alert message → All message input fields are cleared to spaces to ensure clean message structure

Core Acceptance Criteria

[Input Source Type?]
The system checks the OUTPUT-MESSAGE field → If OUTPUT-MESSAGE is empty (SPACES), process cargo report input; otherwise process message input
[3:Extract Manifest Identifiers from Cargo Report]
The system extracts manifest identifiers → CCN key, waybill key, and equipment ID are extracted from cargo report segment
[3:Extract Manifest Identifiers from Message Input]
The system extracts manifest identifiers → CCN from input field, waybill components (road, station, number, date), and car ID are extracted from message data
[4:Search for Duplicate Manifests by Car ID]
The system searches for records with the same car ID → Database is queried using car ID as search key and cargo report segment is retrieved
[7:Generate Duplicate Manifest Alert Message]
The system generates alert message → Alert message is created with action code 'ZZZ', message 'DUPLICATE MANIFEST WAS FOUND, BROWSE BY CAR ID', CCN key, transaction details, user ID, and timestamp
[8:Log Duplicate Manifest Event]
The system logs the duplicate event → Alert message is sent to message queue and written to audit log with message details
[10:Restore Original Cargo Data]
The system restores original data → Original cargo report segment is restored from saved copy
[Input Source Type?]
The system checks the OUTPUT-MESSAGE field → If OUTPUT-MESSAGE is empty (SPACES), process cargo report data; otherwise process message input data
[Destination NOT IIS-A6?]
The system checks the GCM24-MANIFEST-TO field → If destination is not 'IIS-A6', continue validation; otherwise skip duplicate checking
[Valid Haulage Rights?]
If GCM24-HAULAGE-SCAC and GCMSG-INPUT-FIELD → If NOT (SCAC is empty AND input field does not start with '6105E'), proceed with duplicate checking; otherwise skip duplicate checking
[Extract from Cargo Report Segment]
The system needs to extract manifest identifiers for duplicate checking → The system captures CCN key from cargo report CCN key field, waybill ID from cargo report waybill key field, and car ID from cargo report equipment ID field
[Extract from Message Input]
The system needs to extract manifest identifiers for duplicate checking → The system captures CCN key from message input field, waybill road from GCM24 waybill road, waybill station from GCM24 waybill station, waybill number from GCM24 waybill number, waybill date from GCM24 date, and car ID from GCM24 car ID
[Input Source Type?]
The system checks the OUTPUT-MESSAGE field → If OUTPUT-MESSAGE equals spaces then process cargo report segment data, otherwise process message input data
[Clear Cargo Report Segment]
The system begins database query preparation → The cargo report segment is cleared to spaces to ensure no residual data affects the query
[Clear Cargo Record Buffer]
The system prepares to get the next record with the same car ID → The cargo report segment buffer is cleared to spaces to prevent data contamination
[Prepare CCN Key for Record Lookup]
The system needs to retrieve a specific cargo record → The CCN key must be extracted from the cargo report segment and prepared for database lookup
[Generate Alert Message with Browse Instruction]
An alert message needs to be created → The system must generate a message with action code 'ZZZ', message text 'DUPLICATE MANIFEST WAS FOUND, BROWSE BY CAR ID', include the CCN key, set security and cargo flags, and populate transaction details including user ID, date, and time
[Send Message to System Queue]
The message needs to be queued for processing → The system must send the message to the alternate PCB queue using CIMS with CHNG operation
[Write Audit Log Entry]
Audit logging is required → The system must call WRITMSGL to write an audit log entry with message code, message content, message length, and module name, followed by a purge operation
[Record Successfully Updated]
The update operation completes successfully → The system generates an audit message 'DUPLICATE MANIFEST WAS FOUND, BROWSE BY CAR ID' with the CCN key, timestamp, and user information for logging and notification
[Set Action Code to 'ZZZ']
The system sets the message action code → The action code is set to 'ZZZ' to identify this as a duplicate manifest alert
[Set Alert Message Text: 'DUPLICATE MANIFEST WAS FOUND, BROWSE BY CAR ID']
The system sets the alert message text → The message text is set to 'DUPLICATE MANIFEST WAS FOUND, BROWSE BY CAR ID' to inform users and provide resolution guidance
[Add CCN Key to Message]
The system adds identification information to the message → The CCN key from the cargo report segment is included in the train or US CCN field of the alert message
[Set Security Level]
The system sets the security level for the message → The security byte is set to high-value to establish maximum security level for the alert
[Set Message Category to Cargo]
The system sets the message category → The message category is set to cargo to ensure proper classification and routing
[Add Transaction Information]
The system adds transaction tracking information → The transaction code from the communication control block is included as the sending transaction in the alert message
[Add User ID Information]
The system adds user identification information → The ACF2 user ID from the communication control block is included in the alert message
[Add Current Date to Message]
The system adds the current date to the message → The machine century and machine date are concatenated together to form the complete date in the alert message
[Add Current Time to Message]
The system adds the current time to the message → The machine time from the communication control block is included in the alert message
[Prepare Message for Queue]
The system prepares the message for queue processing → The complete alert message input is moved to the message queue structure for transmission
[Send Alert Message to System Queue]
The system sends the message to the queue → The alert message is transmitted to the system queue using the alternate PCB and message logging service
[Duplicate Manifest Alert Message Created]
The system needs to create an alert message → The system creates a message with action code 'ZZZ', sets the message content to 'DUPLICATE MANIFEST WAS FOUND, BROWSE BY CAR ID', includes the CCN key as train/CCN identifier, sets security level to high value, and marks it as cargo-related
[Set Message Code]
The system prepares the audit log parameters → The system sets the message code to 'ZZZ' to identify this as a duplicate manifest alert
[Set Message Content]
The system creates the alert message content → The system sets the message to 'DUPLICATE MANIFEST WAS FOUND, BROWSE BY CAR ID' to inform users about the duplicate condition and recommended action
[Set Message Content]
The system needs to identify the specific manifest → The system sets the CCN key as the train or CCN identifier in the alert message
[Set Message Content]
The system sets security parameters → The system sets the security byte to high value to ensure appropriate access control for the alert
[Set Message Content]
The system categorizes the alert type → The system marks the alert as cargo-related to ensure proper routing and handling
[Write Audit Log Entry to System]
The system needs to log the alert → The system writes the message to the audit log using the message logging service with message code, content, length, and module name
[Save Original Cargo Report Segment to Working Storage]
The duplicate manifest checking process is initiated → The original cargo report segment data is saved to working storage for later restoration
[Restore Original Cargo Report Segment from Working Storage]
The duplicate checking operations are finished → The original cargo report segment data is restored from working storage back to the cargo report segment

Structural Validations

[Cargo Report Input Conditions Met?]
If cargo report processing conditions → Process for duplicates if train ID is empty AND destination station is not 'IIS-A6' AND it's not a haulage rights exception (where SCAC is empty and CCN does not start with '6105E')
[Message Input Conditions Met?]
If message input processing conditions → Process for duplicates if train ID is empty AND destination is not 'IIS-A6' AND it's not a haulage rights exception (where SCAC is empty and input field does not start with '6105E')
[Train ID Empty?]
If the GCM24-TRAIN-ID field → If train ID is empty (SPACES), continue validation; otherwise skip duplicate checking
[Mark Current Record as Duplicate Error]
Error code 6200 has been set for duplicate detection → The system marks the current cargo report record as having duplicate error status

As an EDI Gateway Service,
I want to orchestrate and execute all GCCPERM EDI data mapping and validation logic,
So that I can ensure strict compliance with US Customs (P140) automated payload constraints in a single consolidated service.

Prerequisites & Setup

[Initialize Log Message Structure]
The system begins creating the audit log entry → The log message input structure is cleared and initialized to spaces
[Initialize empty broker configuration]
No valid broker configuration record is retrieved from the broker table → The system initializes empty broker segment and B1 segment configurations and exits broker processing
[Initialize Empty Broker Configuration]
No valid broker configuration exists in the system → System initializes empty broker segments and exits configuration retrieval process
[Initialize Default Settings]
No supplementary configuration exists for the broker → System initializes empty B1 segment with default values
[Initialize Empty Broker Configuration]
No broker configuration record exists for the broker name with either specific port or default port '000' → The system initializes empty broker segment and B1 segment configurations and exits the broker processing
[Initialize Empty Broker Configuration]
The system cannot find any valid broker configuration → The broker segment and B1 segment are initialized to empty values
[Initialize Empty B1 Configuration]
The system cannot find supplementary broker information → The B1 segment is initialized to empty values
[Initialize Merlin Message Structure]
The system prepares to send manifest data via Merlin → The system initializes the GCX019 input structure to clear any previous data
[Initialize Internet Message Structure]
The system needs to prepare an internet message → The system initializes the internet message input structure to empty values
[Initialize Fax Message Structure]
The system begins fax transmission setup → The system initializes the fax input structure to clear any previous data
[Initialize default settings]
Initializing default settings → The system should initialize the B1 segment area with default values
[Initialize Empty Broker Configuration]
No broker configuration data is available → The system initializes empty broker segment and B1 segment configurations and exits the broker search process
[Initialize Empty Additional Details]
No B1 table data is available for the broker → The system initializes an empty B1 segment configuration
[Initialize Empty Broker Configuration]
No broker configuration is found in the broker table → The system initializes empty broker segment and additional broker settings to continue processing
[Initialize Broker Configuration as Empty]
No broker configuration is available for the secondary broker → The system initializes the broker segment as empty and exits the process
[Initialize Merlin Message Structure]
The system prepares to send manifest data via Merlin → The system should initialize the Merlin input structure to ensure clean data transmission
[Initialize Internet Message Structure]
The system prepares to send manifest via internet to secondary broker → The internet message input structure is initialized to clear any previous data
[Initialize Fax Message Structure]
Fax delivery is enabled for the broker → The system initializes the fax message input structure with blank values

Core Acceptance Criteria

[7:Generate Waybill Key Change Log Entry]
Audit logging is performed → A log entry is created with message 'WB KEY CHANGED FROM [old-key]', CCN key, transaction details, user ID, and timestamp
[9:Send Manifest Change Notification to Customs]
Notification transmission is initiated → Manifest change notification is sent to customs with CCN key and message 'MANIFEST BEING SENT - WB PERMANENT'
[11:Send Manifest to Primary Broker via X12]
X12 transmission is initiated → Manifest is sent to broker using X12 format with broker's X12 header information
[12:Send Manifest to Primary Broker via Merlin]
Merlin transmission is initiated → Manifest is sent via Merlin system using broker's Merlin ID
[13:Send Manifest to Primary Broker via Internet]
Internet transmission is initiated → Manifest is sent via internet using broker's internet address
[14:Send Manifest to Primary Broker via Fax]
Fax transmission is initiated → Manifest is sent via fax using broker's fax number
[15:Configure Primary Broker Paper Printing]
Paper printing setup is performed → If broker has specific terminal, use broker's terminal for call letters, otherwise use existing batch print call letters
[17:Send Manifest to Secondary Broker via X12]
X12 transmission to secondary broker is initiated → Manifest is sent to secondary broker using X12 format with broker's X12 header information
[18:Send Manifest to Secondary Broker via Merlin]
Merlin transmission to secondary broker is initiated → Manifest is sent via Merlin system using secondary broker's Merlin ID
[19:Send Manifest to Secondary Broker via Internet]
Internet transmission to secondary broker is initiated → Manifest is sent via internet using secondary broker's internet address
[20:Send Manifest to Secondary Broker via Fax]
Fax transmission to secondary broker is initiated → Manifest is sent via fax using secondary broker's fax number
[23:Configure Port-Based Printing Options]
Printing configuration is determined → If port allows print batches OR immediate indicator is 'Y' OR border port is 'Y', then set batch printing with port call letters, otherwise set call letters without batch printing
[8:Determine Customs Notification Requirement]
Change notification requirements are evaluated → Send change notification if 309 change is pending AND it is not a manual change
[Load Manifest Data into Working Storage]
The system processes the retrieved data → The manifest data is loaded into working storage arrays for both GCSCCS53 and GCSCCS55 segments
[Set Database Operation Parameters]
Configuring the database operation → The system should set segment processing to handle all segments
[Call Database Update Service]
Executing the database update → The system should call the database service with all required parameters including manifest segments and arrays
[Copy Updated Segment Data to Working Storage]
Processing the updated segment data → The system should copy the first element of the primary segment array data to the working segment structure
[Copy Additional Segment Data if Available]
Processing additional segment data → The system should copy the first element of the secondary segment array data to the working segment structure
[Build Log Message Text 'WB KEY CHANGED FROM' + Old Key]
The system creates the audit log message text → The message is formatted as 'WB KEY CHANGED FROM' followed by the old waybill key value
[Create Audit Log Entry for Manifest Change]
The system prepares to send change notifications → An audit log entry is created with action code 'ZZZ' and message 'MANIFEST BEING SENT - WB PERMANENT'
[Call Customs Notification Service]
The system processes the transmission creation → The customs notification service is called with notify-customs flag set to true
[Prepare Customs Notification Message]
The system prepares the notification message → The notification action is set to modify and the manifest key is included in the message
[Call Customs Interface Module GCCS309C]
The system needs to transmit the notification to customs → The system calls the GCCS309C module with the notification parameters
[Retrieve additional broker delivery preferences]
The system searches the B1 table using table ID 'B1' and the same broker key information → The system retrieves additional delivery preference settings or initializes empty B1 segment if not found
[Retrieve Broker Delivery Preferences]
System retrieves the broker configuration data → Broker segment data is loaded into working storage for further processing
[Get Additional Broker Settings]
System searches for additional broker settings in B1 table using same table key → System loads additional broker settings if available, otherwise initializes default B1 segment
[Use Found Broker Configuration]
The search returns successfully without errors → The system loads the retrieved broker segment data and B1 segment data for further processing
[Retrieve Broker Delivery Preferences]
The system needs to access broker delivery preferences → The table segment data is moved to the broker segment for processing
[X12 Delivery Enabled?]
The X12 usage indicator equals 'Y' → The system proceeds with X12 electronic transmission setup
[Set Broker Notification Flag]
X12 transmission is being prepared → The system sets the NOTIFY-BROKER flag to true
[Retrieve X12 Header Information]
X12 transmission setup is in progress → The system retrieves the broker's X12 header information from the broker table
[Prepare Manifest Data for X12 Format]
The system prepares data for X12 transmission → The system includes the CCN key in the X12 transmission data structure
[Call X12 Transmission Service]
The system initiates X12 transmission → The system calls the GCCS309C service with the prepared X12 transmission parameters
[Merlin Delivery Enabled?]
The Merlin usage flag equals 'Y' → The system proceeds with Merlin transmission setup
[Set Manifest CCN Key]
The system prepares manifest identification data → The system assigns the current manifest CCN key to the Merlin message CCN field
[Set Security Parameters]
The system configures security parameters → The system sets the security byte to high values for secure transmission
[Set Broker Merlin ID]
The system sets the destination for the Merlin transmission → The system assigns the broker's Merlin ID from the broker table to the message
[Send Manifest to Merlin System]
The system initiates the Merlin transmission → The system calls the GCT0191E print service to send the manifest to the Merlin system
[Set Manifest Key in Message]
The system needs to identify the manifest in the message → The system sets the CCN key from the current manifest into the internet message CCN field
[Set Security Parameters]
The system needs to secure the message transmission → The system sets the security byte to high-values for maximum security level
[Get Internet Address from Broker Configuration]
The system needs the destination address for internet delivery → The system copies the internet address from the broker configuration B1 segment to the message internet field
[Send Manifest via Internet Message Queue]
The system is ready to transmit the manifest → The system calls the internet print service to send the manifest message
[Fax Delivery Enabled?]
The broker's fax usage flag equals 'Y' → The system proceeds to initialize fax message structure for transmission
[Set Manifest Key for Transmission]
The system prepares the manifest for fax transmission → The system assigns the current CCN key to the fax message CCN field
[Configure Security Parameters]
The system configures transmission security → The system sets the security byte to high-values to ensure maximum security clearance
[Set Primary Broker Fax Number]
The system sets the delivery destination → The system assigns the broker's fax number from the broker configuration to the fax message
[Submit Fax Transmission Request]
The system initiates the fax transmission → The system calls the print service to process and send the fax transmission
[Search for broker by name and port]
The system searches the broker table with table ID 'BK', secondary broker name, Canadian flag 'C', and port code from positions 2-3 of manifest transmission code → The system attempts to retrieve the broker configuration record
[Delivery schedule is immediate or default?]
The system checks if the broker delivery schedule equals 'DEFAULT-DELIVERY' or 'IMMEDIATE-DELIVERY' → If the schedule matches either value, processing continues, otherwise the configuration is rejected
[Load broker delivery preferences]
Loading broker delivery preferences → The system should move the retrieved table segment data to the broker configuration working area
[Schedule is immediate or default?]
Checking schedule compliance → The system should allow processing only if delivery schedule equals 'DEFAULT-DELIVERY' or 'IMMEDIATE-DELIVERY', otherwise exit processing
[Load Additional Broker Details]
Valid B1 table data is available → The system loads the additional broker details into the B1 segment configuration
[Load Broker Delivery Methods]
The system processes the retrieved broker table segment → The broker delivery methods configuration is loaded into the broker segment structure
[Load Additional Broker Settings]
The system searches for additional broker settings in B1 table using the same broker key → If B1 configuration is found, it loads the additional settings, otherwise initializes empty B1 segment
[Retrieve Secondary Broker Configuration by Name and Port]
The system searches for broker configuration with table ID 'BK', secondary broker name, Canadian flag 'C', and port code from positions 2-3 of manifest transmission code → The system retrieves the broker configuration segment if found
[Get Additional Broker Details B1 Segment]
The system searches for additional broker details using table ID 'B1' → The system loads the B1 segment if found, otherwise initializes it as empty
[X12 Use Flag = 'Y'?]
The broker's X12 use flag is set to 'Y' → The system proceeds with X12 transmission setup, otherwise skips X12 delivery
[Call X12 Transmission Service GCCS309C]
The system sets broker notification flag, copies X12 broker header information, and copies manifest CCN key → The system calls the X12 transmission service GCCS309C to send the manifest data
[Set Manifest CCN Key]
The system populates the manifest identifier → The system should set the CCN key from the manifest record into the Merlin message CCN field
[Set Security Parameters]
The system configures security parameters for transmission → The system should set the security byte to high-values to ensure proper authorization for the Merlin transmission
[Set Secondary Broker Merlin ID]
The system sets the destination for the transmission → The system should populate the Merlin ID field with the secondary broker's Merlin identifier from the broker configuration
[Send Manifest to Merlin System]
The system initiates the Merlin transmission → The system should call the Merlin print service to deliver the manifest to the secondary broker
[Set Manifest CCN Key in Message]
The system sets the manifest identifier in the message → The CCN key from the manifest is assigned to the internet message CCN field
[Set Security Parameters]
The system configures security settings for the message → High security values are assigned to the internet message security byte
[Get Internet Address from Broker Configuration]
The system needs the internet address for message delivery → The internet address is retrieved from the secondary broker's B1 segment configuration and assigned to the message
[Send Message to Internet Delivery Queue]
The system sends the message for delivery → The GCT0191E print spawning process is performed to queue the internet message for delivery
[Set Manifest CCN Key]
The system prepares the fax notification → The system assigns the manifest CCN key to the fax message CCN field
[Set Security Parameters]
The system configures security settings → The system sets the security byte to high values for maximum security clearance
[Get Broker Fax Number from Configuration]
The system needs the destination fax number → The system retrieves the broker fax number from the broker configuration segment
[Assign Fax Number to Message]
The system prepares for fax transmission → The system assigns the broker fax number to the fax number field in the message
[Send Manifest to Fax Queue]
All fax message components are properly configured → The system calls the fax processing service to queue the manifest for fax delivery
[Extract Port Settings]
The system processes the table segment data → The system should extract the port settings into the appropriate data structure
[Print Batches Enabled OR Immediate Indicator OR Border Port?]
If batch processing eligibility → The system should qualify for batch processing if print batches flag equals 'Y' OR immediate indicator flag equals 'Y' OR border port flag equals 'Y'
[Extract Port Settings from MC Table]
The system processes the configuration data → The system moves the retrieved configuration data to the MC segment structure for evaluation
[Print Batches Enabled OR Immediate Indicator OR Border Port?]
If the port processing requirements → If print batches flag equals 'Y' OR immediate indicator flag equals 'Y' OR border port flag equals 'Y', then enable batch processing mode, otherwise use standard processing mode
[Set Batch Print Call Letters as Index and Print Letters]
The system configures batch print settings → The system sets both batch print call letter index and batch print call letters to the port's MC call letters value
[Set Print Call Letters Only - No Batch Index]
The system configures print settings → The system clears the batch print call letter index to spaces and sets batch print call letters to the port's MC call letters value
[Extract Port Settings]
The system processes the retrieved configuration → The table segment data is moved to the port configuration structure for further processing
[Port Configuration Retrieved Successfully]
If these configuration flags → If print batches is 'Y' OR immediate indicator is 'Y' OR border port is 'Y', then call letters are set for batch printing index and manifest is updated, otherwise call letters are only set for batch printing without index and manifest is updated
[Load Port Configuration Data]
The system processes the retrieved data → The system moves the table segment data to the port configuration structure
[Check Port Printing Requirements]
If the port printing settings → The system checks if print batches flag is 'Y' OR immediate indicator flag is 'Y' OR border port flag is 'Y'
[Set Batch Print Call Letters as Index]
The system configures printing settings → The system sets the port call letters as both the batch print call letter index and the batch print call letters
[Set Call Letters Only - No Index]
The system configures printing settings → The system clears the batch print call letter index and sets only the batch print call letters from port configuration
[Extract Port Settings]
The system processes the retrieved configuration data → The system moves the table segment data to the port configuration structure for further processing
[Print Batches Enabled OR Immediate Indicator OR Border Port?]
If printing requirements → If print batches is 'Y' OR immediate indicator is 'Y' OR border port is 'Y', then enable batch printing with index, otherwise set up print-only configuration
[Set Port Call Letters for Batch Printing Index]
The system sets up printing configuration → The system assigns port call letters to both the batch print call letter index and the batch print call letters fields
[Set Port Call Letters for Print Only]
The system sets up printing configuration → The system clears the batch print call letter index and assigns port call letters only to the batch print call letters field

Structural Validations

[10:Retrieve Primary Broker Configuration]
Delivery schedule is evaluated → Broker notifications are processed only if delivery schedule is 'DEFAULT-DELIVERY' or 'IMMEDIATE-DELIVERY', otherwise skip broker processing
[Delivery schedule is immediate or default?]
The broker's delivery schedule is evaluated against eligible delivery types → Processing continues only if delivery schedule equals 'DEFAULT-DELIVERY' or 'IMMEDIATE-DELIVERY', otherwise broker processing is skipped
[Delivery Schedule Valid?]
System checks if broker delivery schedule is either 'DEFAULT-DELIVERY' or 'IMMEDIATE-DELIVERY' → Processing continues only if delivery schedule matches valid delivery types, otherwise configuration retrieval exits
[Schedule is Default or Immediate?]
If delivery schedule eligibility → Processing continues only if delivery schedule equals 'DEFAULT-DELIVERY' or 'IMMEDIATE-DELIVERY', otherwise the broker is skipped
[Validate delivery schedule]
Validating the delivery schedule → The system should check if the broker delivery schedule is either 'DEFAULT-DELIVERY' or 'IMMEDIATE-DELIVERY'
[Delivery Schedule is Default or Immediate?]
The delivery schedule is either 'DEFAULT-DELIVERY' or 'IMMEDIATE-DELIVERY' → The system continues with transmission processing, otherwise skips the broker notification

As an EDI Gateway Service,
I want to orchestrate and execute all GCX011R EDI data mapping and validation logic,
So that I can ensure strict compliance with US Customs (P140) automated payload constraints in a single consolidated service.

Prerequisites & Setup

[Initialize Segment Keys and Record Types]
The system begins creating manifest data segments → All segment keys are initialized with CCN identifiers and record type indicators are set for segments 52, 53, 54, 55, and 56
[Initialize Error Segment 54]
The system needs to create an error tracking record → An error segment 54 is initialized to capture validation issue details
[Initialize Segment Creation Process]
The system begins the segment creation process → All segment data structures are initialized and ready for population
[Initialize Error Message Counter to Zero]
The system begins error message processing → The error message counter is set to zero

Core Acceptance Criteria

[22:Broker Name Parsing]
The system parses broker names → Extract broker name using priority order: 'CUSTOMS BROKER ' (positions 16-28), 'CUSTOMS BROKER: ' (positions 17-27), 'BROKER ' (positions 8-36), 'BROKER: ' (positions 9-35), 'CB ' (positions 4-41), 'CB: ' (positions 5-40), 'XQ ' (positions 4-41), 'XQ: ' (positions 5-40)
[24:Manifest Creation]
The system creates new manifest → Create cargo report with CCN, set appropriate status (SENT for 6105E with transmission, MANUAL without transmission, LOCAL for non-6105E), establish multi-car relationships (S type for single, F type for followers), and exclude empty cars (EL='E' and BLNG-CDE='ZE')
[29:Customs Transmission Processing]
The system processes customs transmission → Send first 309 transmission if not previously sent and not rejected, set change pending if already sent and not locked, process changes when waybill completed and change pending, exclude idler shipments from customs notification
[30:Broker Notification Processing]
The system processes broker notifications → Check broker table for delivery schedule (DEFAULT/IMMEDIATE), send notifications via configured methods (X12, Merlin, Internet, Fax, Paper), notify both primary and secondary brokers if applicable, send unknown brokers to Merlin system
[8230-GU-SHIPMINS: Get Shipment Minimum Data]
The system accesses shipment minimum data with segment ID 'S' and number '1' → Retrieve shipment minimum data if available, otherwise clear shipment minimum fields
[Populate Message Fields]
The system prepares for waybill information retrieval → Set message carrier code, origin station number, and waybill number from spawn data for downstream processing
[Retrieve Shipment Minimum Data]
The system attempts to retrieve shipment minimum data with segment ID 'S' and number '1' → If shipment data is found, load the data, otherwise clear shipment minimums data and set error flag
[Call FWWWBIO Segment]
Waybill data needs to be retrieved → The system calls the FWWWBIO segment to access the waybill data
[Retrieve Waybill Data]
The system executes the data retrieval operation → The complete waybill data record is retrieved from the Fastway system
[Extract ORIG-CSC-STN-NUM Field]
The system processes the waybill for origin station information → The ORIG-CSC-STN-NUM field value is extracted and made available for further processing
[Execute Database Lookup]
The system executes database lookup against GCSCCRT segment → The system searches for matching manifest record and prepares for result processing
[Retrieve Manifest Data]
A matching manifest record is found in GCSCCRT segment → The system retrieves complete manifest data, sets data found flag, preserves call letters and status information, and returns the manifest record
[Set Not Found Flag]
No matching manifest record is found in GCSCCRT segment → The system sets not found flag, clears any existing manifest data, and returns empty result
[CCN Generation Logic]
The CCN starts with '6105P' → Set transmission flag to NOT-PRESENT, otherwise set to WS-PRESENT
[Extract waybill number and date from spawn data with validation]
System populates message fields → Populate message fields with carrier information and proceed to origin station population
[Extract waybill number and date from spawn data with validation]
System continues message field population → Populate message fields with origin station information and proceed to waybill number population
[Extract waybill number and date from spawn data with validation]
System continues message field population → Populate message fields with waybill number and set waybill components as valid
[Set Waybill Fields in Message]
The system processes the waybill number for field population → Set the waybill fields in the message structure with the extracted waybill number data
[Populate Carrier and Origin Station]
The system processes carrier and station information from the waybill → Populate the carrier code and origin station number in the appropriate message fields
[Populate message fields with waybill data]
The system processes waybill information → Message fields should be populated with the extracted waybill data for downstream processing
[Populate Message Fields with Carrier]
System populates message fields with carrier information → Message structure contains carrier code in appropriate fields
[Set Carrier in Waybill Structure]
System updates waybill structure with carrier data → Waybill structure contains carrier information for manifest processing
[Block Update - User Made Changes]
The manifest has been manually locked by a user (309-LOCKED flag is set) → The system blocks the update and generates error message 'CHANGE NOT APPLIED - MANIFEST MANUALLY CHANGED'
[Block Update - CSA Manifest Arrived]
The manifest status is CSA-DLV (CSA delivered status) → The system blocks the update and generates error message 'CHANGE NOT APPLIED - CSA MANIFEST ARRIVED'
[Block Update - Broker Entry Present]
A broker entry has been filed (broker entry fields are populated) and either broker names don't match (for 6105E) or CCN differs from waybill CCN (for non-6105E) → The system blocks the update and generates error message 'CHANGE NOT APPLIED - BROKER ENTRY PRESENT'
[Block Update - Released Status]
The manifest status is RELEASE, CSA-DLV, or DLACTIV and CCN differs from waybill CCN → The system blocks the update and generates error message 'CHANGE NOT APPLIED - RELEASED STATUS'
[Set Follower Status Override]
The system determines appropriate status for the new follower manifest → System applies status override rules considering transmission requirements, CCN type, and multi-bill processing flags
[Update Spawn Message with Follower Data]
The system updates the spawn message with follower specific information → The spawn message contains the follower manifest data required for processing
[Set Waybill Key for Index]
The system sets the waybill key for database indexing → The waybill key is properly configured to identify the follower manifest
[Spawn GCX011 Update Transaction]
The system spawns a GCX011 update transaction → A GCX011 transaction is initiated to process the follower manifest update
[Restore Original Spawn Data]
The system restores the original spawn data → The spawn message is restored to its original state before processing the next follower
[Block Update - Train Status]
The manifest has been assigned to a train (CDN-CUS-NORTH-TRAIN-ID is not empty) → Block the update and generate error message 'CHANGE NOT APPLIED - MANIFEST ON TRAIN'
[Block Update - 309 Locked]
The manifest has 309 transmission locked status (309-LOCKED is true) → Block the update and generate error message 'CHANGE NOT APPLIED - MANIFEST MANUALLY CHANGED'
[Block Update - Cargo Arrived]
The cargo has already arrived (ARRIVAL-IND is populated) → Block the update and generate error message 'CHANGE NOT APPLIED - CARGO ARRIVED'
[Block Update - CSA Delivered]
The manifest status is CSA-DLV (CSA manifest delivered) → Block the update and generate error message 'CHANGE NOT APPLIED - CSA MANIFEST ARRIVED'
[Block Update - Broker Entry]
For 6105E CCNs: broker entry exists and broker names differ:
For non-6105E CCNs: broker entry exists and CCN differs from waybill CCN
→ Block the update and generate appropriate broker conflict error message
[Update All Followers]
Follower manifests exist for the corrected manifest → Retrieve all follower manifests using B0 segment and prepare them for update
[Spawn Follower Updates]
The system needs to update follower manifests → Spawn GCX011 update process for each follower manifest (excluding master itself) and send GCT0111E transaction message
[Determine Manifest Status]
The CCN starts with '6105E' and transmission is required → The system sets manifest status to 'SENT' for electronic transmission to customs
[Determine Manifest Status]
The CCN starts with '6105E' and transmission flag indicates no transmission needed → The system sets manifest status to 'MANUAL' for manual processing
[Set Data Origin Classification]
The system needs to track the origin of the manifest data → The system assigns a data origin classification (Order Entry, Fastway, or EDI) to indicate the source system or method used to create the manifest
[Create Segment 52 - Basic Manifest Data]
Segment 52 creation is initiated → Basic manifest data segment is created with fundamental shipment details including waybill information, car details, and routing data
[Assign CCN Key to Segment 52]
CCN key assignment is performed → The Cargo Control Number is assigned as the unique identifier for segment 52
[Create Segment 53 - Additional Manifest Info]
Additional manifest information processing is required → Segment 53 is created with supplementary manifest details including broker information, special handling codes, and extended routing data
[Assign CCN Key to Segment 53]
CCN key assignment is performed → The Cargo Control Number is assigned as the unique identifier for segment 53
[Assign CCN Key to Segment 54]
CCN key assignment is performed → The Cargo Control Number is assigned as the unique identifier for segment 54
[Create Segment 55 - Extended Data]
Extended data storage is required → Segment 55 is created with extended manifest attributes and specialized processing information
[Assign CCN Key to Segment 55]
CCN key assignment is performed → The Cargo Control Number is assigned as the unique identifier for segment 55
[Create Segment 56 - Supplemental Info]
Supplemental information storage is needed → Segment 56 is created with miscellaneous manifest data and reference information
[Assign CCN Key to Segment 56]
CCN key assignment is performed → The Cargo Control Number is assigned as the unique identifier for segment 56
[Classify Data Origin]
Data source classification is performed → The system identifies whether data originated from Order Entry, Fastway, or EDI sources
[Data Source Type?]
If the data source type → The system determines if the data source is Order Entry, Fastway, or EDI and routes to appropriate processing logic
[Mark as EDI Origin]
Origin marking is performed → Manifest data is marked with EDI origin indicator and appropriate processing flags are set
[Set Creation Timestamps]
Timestamp assignment is performed → Creation timestamps are set for all segments 52, 53, 54, 55, and 56
[Set User Information]
User information assignment is performed → User identification, session details, and processing context are recorded for all manifest segments
[Complete Segment Creation]
Segment creation completion is processed → The manifest data segments creation process is marked as complete and the system is ready for subsequent processing
[Set Creation Date and User Information]
The system sets metadata for the error message → The error message segment includes creation date and user information for audit and tracking purposes
[Set Car ID and Data Origin Classification]
The system sets contextual information for the error message → The error message segment includes car ID and data origin classification for proper error context identification
[Set Segment Creation Details]
The system prepares to create the error segment → Segment creation details including segment type and basic metadata are established
[Set Origin: Order Entry]
The creation signon field indicates Order Entry system → The error segment origin is set to Order Entry
[Set Origin: Fastway]
The creation signon field indicates Fastway system → The error segment origin is set to Fastway
[Set Origin: EDI]
The creation signon field indicates EDI system → The error segment origin is set to EDI
[Set Creation Date and User Info]
The system finalizes error segment creation → Current date, time, and user information are recorded in the error segment
[309 Lock Status?]
The system checks the 309 lock status → The system should skip transmission processing if CDN-CUS-309-LOCKED equals 'Y', otherwise proceed with transmission
[Determine Action Code Based on Corrector Status]
The system determines the action code for transmission → The system should set action code to MOD if GCCC-CORRECTOR-SIGNON is not spaces, otherwise set to ADD for new manifests or DELETE for deletions
[Set Action Code = ADD]
The system assigns an action code for transmission → The system should set the action code to ADD
[Set Action Code = MOD]
The system assigns an action code for transmission → The system should set the action code to MOD
[Set Action Code = DELETE]
The system assigns an action code for transmission → The system should set the action code to DELETE
[Set Pre-Emanifest Indicator Based on Action Code]
The system sets the pre-emanifest indicator → The system should set the appropriate pre-emanifest indicator value based on the action code type
[Set Original Sent Timestamp]
The system processes the first transmission → The system should set CCN-ORIGINAL-SENT-DATE and CCN-ORIGINAL-SENT-TIME to current date and time
[Preserve Existing Timestamp]
The system processes a subsequent transmission → The system should preserve the existing CCN-ORIGINAL-SENT-DATE and CCN-ORIGINAL-SENT-TIME values
[Create 309 Transmission Record]
The system creates the 309 transmission record → The system should populate the transmission record with manifest data, action code, and pre-emanifest indicator
[Set Change Pending Flag]
The system updates the manifest status → The system should set CDN-CUS-CHANGE-PENDING to 'Y'
[Spawn GCT1401E Transaction]
The system initiates downstream processing → The system should spawn a GCT1401E transaction for customs notification
[Process Secondary Broker Notification]
The system completes primary transmission processing → The system should process notification for the secondary broker if secondary broker data exists
[X12 EDI Delivery?]
The system checks if X12 EDI delivery is enabled for the broker → If X12 EDI is enabled, proceed to X12 EDI transmission; otherwise check next delivery method
[X12 EDI Transmission]
The system processes X12 EDI transmission → Send broker notification via X12 EDI format and update transmission status
[Merlin System Delivery?]
The system checks if Merlin system delivery is enabled for the broker → If Merlin system delivery is enabled, proceed to Merlin system notification; otherwise check next delivery method
[Fax Delivery?]
The system checks if Fax delivery is enabled for the broker → If Fax delivery is enabled, proceed to Fax transmission; otherwise check next delivery method
[Fax Transmission]
The system processes Fax transmission → Send broker notification via Fax transmission and update transmission status
[X12 EDI Delivery Method?]
If the broker's X12 EDI delivery preference setting → If X12 EDI is enabled, the system sets X12 notification flag and prepares EDI header information
[Set X12 EDI Notification]
The system configures X12 notification settings → The system enables X12 EDI notification flag and prepares the transmission for electronic data interchange
[Prepare X12 Header Information]
The system prepares the X12 transmission header → The system formats the header information according to X12 EDI standards with proper sender and receiver identification
[Merlin System Delivery Method?]
If the broker's Merlin system delivery preference setting → If Merlin delivery is enabled, the system sets Merlin notification flag and prepares Merlin ID information
[Prepare Merlin ID Information]
The system prepares Merlin ID information → The system formats the Merlin identification data for proper internal system message routing
[Set Fax Notification Flag]
The system configures Fax notification settings → The system enables Fax notification flag for facsimile transmission delivery
[Execute Selected Delivery Methods]
The system executes the selected delivery methods → The system sends notifications through all enabled delivery channels including X12 EDI, Merlin, Internet, Fax, and Paper as configured for each broker
[Delivery Schedule Type?]
If the delivery schedule type → Route to DEFAULT-DELIVERY validation if schedule is default, IMMEDIATE-DELIVERY validation if immediate, or ARRIVAL-DELIVERY validation if arrival-based
[Notification Context?]
If the notification context → Route to standard notification timing for regular deliveries, immediate notification timing for urgent deliveries, or arrival notification timing for arrival-based deliveries
[Apply Immediate Notification Timing]
The system applies immediate notification timing rules → Configure notification delivery for immediate processing and complete schedule validation
[IMMEDIATE-DELIVERY Schedule?]
The system checks if immediate delivery schedule is configured → The system identifies whether immediate delivery notification is required
[Check Delivery Schedule Type]
The system examines the broker's delivery schedule configuration → The system identifies whether the broker has DEFAULT, IMMEDIATE, or other delivery schedule types configured
[Default Delivery Schedule?]
The system checks if the broker's delivery schedule is set to DEFAULT type → The system routes to default delivery timing validation if DEFAULT schedule is configured, otherwise checks for immediate delivery schedule
[Immediate Delivery Schedule?]
The system checks if the broker's delivery schedule is set to IMMEDIATE type → The system routes to immediate delivery timing validation if IMMEDIATE schedule is configured, otherwise sets invalid delivery status
[Validate Immediate Timing Rules]
The system validates the immediate delivery timing rules and constraints → The system sets the immediate delivery flag and prepares for priority delivery parameter application
[Apply Priority Delivery Parameters]
The system applies priority delivery parameters based on immediate delivery flag → The system configures priority delivery parameters and proceeds to validation check
[Retrieve Broker Information]
The system needs to validate immediate delivery parameters → The system retrieves broker information from the BK table using broker name, Canadian flag 'C', and port code
[Check Delivery Schedule Setting]
The system checks the broker's delivery schedule configuration → The system identifies whether the schedule is set to 'IMMEDIATE', 'DEFAULT', or other delivery types
[Schedule Type?]
If the schedule type → If schedule type is 'IMMEDIATE', proceed to validate immediate delivery rules; if schedule type is 'DEFAULT', set default delivery flag
[Check Business Hours]
The system checks current time against business hour rules → The system validates that the delivery request falls within allowed business hours for immediate processing
[Immediate Delivery Valid?]
If the overall validation result → If all validations pass, set immediate delivery flag; if any validation fails, set default delivery flag
[Set Immediate Delivery Flag]
The system sets delivery processing flags → The system sets the immediate delivery flag to enable immediate processing and notification
[Set Default Delivery Flag]
The system sets delivery processing flags → The system sets the default delivery flag to use standard delivery processing
[Log Validation Result]
The system logs the validation result → The system records the validation outcome, delivery method selected, and any relevant validation details for audit purposes
[IMMEDIATE-DELIVERY Schedule?]
If alternative delivery schedule options → The system identifies if the broker has IMMEDIATE-DELIVERY schedule configured for expedited processing
[Set Immediate Processing Flag]
The system processes delivery schedule validation → The system sets the immediate processing flag to enable expedited delivery handling for the broker
[Use Default Delivery Schedule]
The system processes delivery schedule validation → The system applies the default delivery schedule configuration for standard processing
[Apply Immediate Timing Rules]
The delivery schedule type is IMMEDIATE-DELIVERY → The system applies immediate timing rules for broker notifications
[Set X12 EDI Timing]
X12 EDI is one of the selected notification channels → The system sets X12 EDI specific timing parameters
[Broker Has X12 EDI Capability?]
The system checks broker X12 EDI capability settings → If broker has X12 EDI capability configured, proceed with X12 transmission setup, otherwise use fallback notification method
[Retrieve Broker X12 Settings]
System accesses broker table for X12 configuration → X12 settings including transmission parameters and format specifications are retrieved from broker table
[Set X12 Header Information]
System prepares X12 EDI message header → X12 header information including sender ID, receiver ID, and control numbers are populated
[Format Manifest Data for EDI]
System formats manifest data for EDI transmission → Manifest data is converted to X12 EDI format using appropriate data segments and elements
[Set GCWS309C-NOTIFY-BROKER Flag]
System prepares to send X12 EDI notification → GCWS309C-NOTIFY-BROKER flag is set to indicate broker notification method
[Populate X12 Transaction Set]
System creates X12 transaction set → X12 transaction set is populated with formatted manifest data according to EDI standards
[Add Manifest Details to EDI]
System adds manifest details to EDI message → Manifest details including cargo information, routing data, and customs details are added to X12 EDI message
[Set EDI Transmission Priority]
System determines transmission priority → EDI transmission priority is set based on manifest urgency and broker delivery schedule requirements
[Queue EDI Message for Transmission]
System queues message for transmission → EDI message is placed in transmission queue with appropriate priority and routing information
[Log EDI Transmission Attempt]
System logs transmission attempt → Transmission attempt is logged with timestamp, broker information, and message details
[Transmission Successful?]
System evaluates transmission result → If transmission successful, update broker notification status, otherwise handle transmission error
[Update Broker Notification Status]
System updates broker notification status → Broker notification status is updated to reflect successful X12 EDI delivery
[Record EDI Success]
System records EDI success → Successful EDI transmission is recorded with completion timestamp and delivery confirmation
[Set Fallback Notification Method]
System sets fallback notification method → Alternative notification method such as Merlin, Internet, Fax, or Paper is selected based on broker preferences
[Set Up Merlin Message Structure]
The system sets up the Merlin message structure → The system creates the appropriate message framework for EMI message population
[Populate EMI Message Fields]
The system populates EMI message fields → The system fills in the required message fields for broker notification
[Include Manifest Details]
The system includes manifest details → The system adds manifest information to the notification message
[Include Broker Information]
The system includes broker information → The system adds broker details to the notification message
[Spawn GCT0191E Transaction]
The system spawns GCT0191E transaction → The system creates and initiates the GCT0191E transaction for notification delivery
[Prepare Internet Notification Message]
The system prepares the notification message → The system creates the appropriate message content for internet transmission
[Format Message for Internet Delivery]
The system formats the message for internet transmission → The system applies internet-specific formatting to ensure proper delivery
[Queue Message for Internet Transmission]
The system queues the message for transmission → The system places the message in the internet transmission queue for delivery
[Set Delivery Status to Internet]
The system updates the delivery status → The system sets the delivery status to indicate internet delivery method
[Prepare Fax Notification Message]
The system prepares the fax notification → The system formats the notification message with required broker notification content
[Set Fax Delivery Parameters]
The system sets up fax transmission parameters → The system configures delivery parameters including priority, retry settings, and transmission options
[Queue Fax for Transmission]
The system queues the fax for transmission → The system adds the fax request to the transmission queue with appropriate priority and scheduling
[Update Broker Notification Status]
The system updates notification tracking → The system records the fax notification status and timestamp for the broker
[Log Fax Transmission Request]
The system logs the transmission request → The system creates a log entry with broker details, fax number, message content, and transmission timestamp
[Skip Fax - No Number Available]
The system attempts fax notification → The system skips fax transmission and continues with other notification methods
[Send X12 EDI Notification]
X12 EDI communication method is available and configured for the broker → Send arrival notification via X12 EDI channel
[Prepare Broker Notification]
The system prepares arrival notification message → The system creates notification with action code '04' and relevant arrival details
[Send Arrival Notification to Broker]
If available delivery channels (X12 EDI, Merlin, Internet, Fax, Paper) → The system sends notification through all configured channels and updates delivery status accordingly
[Deletion Authorization Block]
The system detects unauthorized deletion attempt based on manifest status or business rules → The system sets error message number for deletion authorization block, populates error message text 'DELETION NOT AUTHORIZED', creates error segment 54, and sets processing flags to prevent the deletion
[Deletion Authorization Block]
The system detects multi-bill manifest with followers that requires manual deletion → The system sets error message number for multi-bill deletion block, populates error message text 'MULTI-BILL DELETION BLOCKED', creates error segment 54, and sets processing flags to prevent automated deletion
[Set Processing Flags]
The system needs to configure processing control flags to prevent or modify subsequent processing → The system sets processing flags to indicate error status, block further processing, or trigger alternative processing paths based on the error condition
[CCN Original Sent Exists?]
The system checks the CCN original sent indicator → If CCN was originally sent to customs, proceed to spawn customs transmission; otherwise proceed to audit logging
[Spawn Customs Transmission]
The CCN original sent indicator exists → Spawn a customs transmission to notify authorities of the manifest cancellation
[Block Manifest Deletion]
The system determines this is a manifest deletion operation → The system blocks the deletion and generates error message 'MULTI-BILL MANIFEST DELETION REQUIRES MANUAL PROCESSING'
[Determine Email Recipients]
The system needs to notify relevant parties about the blocked change → The system identifies appropriate email recipients based on the shipment details and error type
[Format Email Notification]
The system prepares the email notification → The system formats the email with appropriate error message, shipment details, and recipient information
[Format Email Message]
The system formats the email message → The email includes error message text, manifest details, and appropriate headers
[Spawn GCT1251E Transaction]
The system initiates email delivery → A GCT1251E transaction is spawned to process the email notification
[Generate Report Segments]
The system processes the cargo report for detailed information → The system generates report segments with cargo details, routing information, and regulatory data
[Update Report Status]
Report processing reaches completion stage → The system updates the report status to indicate successful generation and readiness for transmission
[GCT1401E - Customs Transmission Spawn]
The system determines that customs transmission spawn is required → The system spawns GCT1401E transaction with customs data and transmission parameters
[Prepare Spawn Message]
The system prepares the spawn message with transaction-specific data → The system formats the spawn message with all required parameters and data elements
[Set Transaction Parameters]
The system sets transaction parameters including routing and processing flags → The system configures all necessary parameters for successful transaction execution
[Execute Spawn Call]
The system executes the spawn call to the target transaction → The system initiates the target transaction and receives execution status
[Set ADD Action Code]
Action code validation is performed for customs transmission → Action code is set to ADD for initial transmission to customs
[Set MOD Action Code]
Action code validation is performed for customs transmission update → Action code is set to MOD for modification transmission to customs
[Set DEL Action Code]
Action code validation is performed for customs transmission deletion → Action code is set to DEL for deletion transmission to customs
[Set X12 EDI Parameters]
Broker delivery method validation determines X12 EDI is the preferred method → GCT0191E transaction parameters are set for X12 EDI delivery including broker EDI address and message format
[Set Merlin Parameters]
Broker delivery method validation determines Merlin is the preferred method → GCT0191E transaction parameters are set for Merlin delivery including broker Merlin address and message format
[Set Internet Parameters]
Broker delivery method validation determines Internet is the preferred method → GCT0191E transaction parameters are set for Internet delivery including broker email address and message format
[Set Fax Parameters]
Broker delivery method validation determines Fax is the preferred method → GCT0191E transaction parameters are set for Fax delivery including broker fax number and message format
[Email Notification Spawning]
Email notification spawning is requested → GCT1251E transaction is spawned with email parameters including recipient address, subject, and message content
[Set Action Code = 'ADD']
The waybill corrector status field is empty or spaces → The system sets the action code to 'ADD'
[Set Action Code = 'DELETE']
The waybill corrector status is 'D' → The system sets the action code to 'DELETE'
[Set Action Code = 'MOD']
The waybill corrector status is not empty and != 'D' → The system sets the action code to 'MOD'
[Set Pre-Emanifest Indicator = 'N']
The action code is 'DELETE' → The system sets the pre-emanifest indicator to 'N'
[Keep Current Pre-Emanifest Indicator]
The action code is not 'DELETE' → The system maintains the current value of the pre-emanifest indicator
[Save Original Waybill Number]
The system needs to process a follower manifest that requires temporary data substitution → The original waybill number from the spawn message is saved to a preservation variable
[Save Original Waybill Date]
The system needs to process a follower manifest that requires temporary data substitution → The original waybill date from the spawn message is saved to a preservation variable
[Save Original Action Code]
The system needs to process a follower manifest that requires temporary data substitution → The original action code from the spawn message is saved to a preservation variable
[Save Original Car ID]
The system needs to process a follower manifest that requires temporary data substitution → The original car ID from the spawn message is saved to a preservation variable
[Save Original CCN]
The system needs to process a follower manifest that requires temporary data substitution → The original CCN from the spawn message is saved to a preservation variable
[Update Spawn Message with Follower Data]
The system needs to process a specific follower manifest → The spawn message is updated with the follower manifest's waybill number, date, car ID, and CCN data
[Set Follower Waybill Key]
The spawn message is being updated for follower processing → The spawn waybill key is set to the follower manifest's waybill identification key
[Set Follower Waybill Date]
The spawn message is being updated for follower processing → The spawn waybill date is set to the follower manifest's waybill date
[Set Follower Car ID]
The spawn message is being updated for follower processing → The spawn car ID is set to the follower manifest's car identification
[Set Follower CCN]
The spawn message is being updated for follower processing → The spawn CCN is set to the follower manifest's cargo control number
[Execute Spawn Operation]
All follower data has been properly set in the spawn message → The GCT0111E spawn operation is executed with the follower-specific data
[Restore Original Waybill Number]
The follower processing is finished → The original waybill number is restored to the spawn message
[Restore Original Waybill Date]
The follower processing is finished → The original waybill date is restored to the spawn message
[Restore Original Action Code]
The follower processing is finished → The original action code is restored to the spawn message
[Restore Original Car ID]
The follower processing is finished → The original car ID is restored to the spawn message
[Restore Original CCN]
The follower processing is finished → The original CCN is restored to the spawn message
[Update Spawn Message with Follower Data]
The system processes follower data updates → The spawn message is updated with follower's waybill key, waybill date, equipment ID, and cargo control number
[Set Waybill Information]
The system updates spawn message with follower data → SPAWN-WAYBILL is set to the follower's waybill key for index
[Set Waybill Date]
The system updates spawn message with follower data → SPAWN-WAYBILL-DATE is set to the follower's waybill date index
[Set Equipment ID]
The system updates spawn message with follower data → SPAWN-CAR-ID is set to the follower's equipment ID for index
[Set Cargo Control Number]
The system updates spawn message with follower data → SPAWN-CCN is set to the follower's cargo control number
[Execute Spawn Operation]
The system executes the spawn operation → The 8430-SPAWN-GCT0111E procedure is called to execute the GCT0111E transaction
[Update Spawn Message with Follower Data]
Follower update processing requires follower-specific data → Spawn message is updated with follower waybill number, waybill date, action code, car ID, and CCN from the follower manifest
[Execute Follower Update Operation]
Follower update processing is initiated → GCT0111E transaction is spawned to update the follower manifest
[Restore Original Waybill Number]
Data restoration process begins → Original waybill number is restored to the spawn message from temporary storage
[Restore Original Waybill Date]
Data restoration process continues → Original waybill date is restored to the spawn message from temporary storage
[Restore Original Action Code]
Data restoration process continues → Original action code is restored to the spawn message from temporary storage
[Restore Original Car ID]
Data restoration process continues → Original car ID is restored to the spawn message from temporary storage
[Restore Original CCN]
Data restoration process completes → Original CCN is restored to the spawn message from temporary storage and data restoration is complete
[Shipment Data Access 8230-GU-SHIPMINS]
The system needs to retrieve shipment minimum data → The system executes 8230-GU-SHIPMINS to retrieve SHIPMIN segment with ID 'S' and number '1', clearing data if retrieval fails
[Generic Table Lookup 8999-GET-TABLE-SEGMENT]
The system needs to perform a generic table lookup operation → The system executes 8999-GET-TABLE-SEGMENT using GCCTBIO for table access
[Message Table Access 8510-RETRIEVE-ERR-MSG]
The system needs to retrieve error message text → The system executes 8510-RETRIEVE-ERR-MSG to retrieve error message text from 'MS' table using error number, setting MSG-LABEL with English text or spaces if not found
[Shipment Data Retrieval]
The system executes shipment minimums retrieval and the record is found → The system populates SHIPMINS data fields with retrieved information
[Shipment Data Retrieval]
The system executes shipment minimums retrieval and the record is not found → The system clears all SHIPMINS data fields
[Generic Table Lookup - 8999-GET-TABLE-SEGMENT]
The system calls GCCTBIO through the generic table access routine → The system returns table data if found or not-found status for further processing
[309 Lock Status Check]
The system checks for manual change locks → If 309-LOCKED is true (user made manual changes), then updates are not allowed with error 'WB UPDATE NOT APPLIED USER MADE CHANGES TO MFST'
[Check CSA-DLV/Released Status]
The manifest status is CSA-DLV → Reject any update or deletion attempts and generate error message 'CHANGE NOT APPLIED - CSA MANIFEST ARRIVED'
[Check Manifest on Train]
The manifest is already on a train (CDN-CUS-NORTH-TRAIN-ID is not empty) → Reject update and generate error message 'CHANGE NOT APPLIED - MANIFEST ON TRAIN'
[Check 309 Lock Status]
The manifest has 309-LOCKED status indicating manual changes → Reject update and generate error message 'CHANGE NOT APPLIED - MANIFEST MANUALLY CHANGED'
[Block Update - Train Status]
An update request is processed for the manifest → The system blocks the update and generates an error message indicating train assignment prevents changes
[Block Update - User Changes]
An update request is processed for the manifest → The system blocks the update and generates an error message indicating manual changes prevent automatic updates
[Block Update - Arrived Status]
An update request is processed for the manifest → The system blocks the update and generates an error message indicating arrived cargo cannot be modified
[Block Update - CSA Delivered]
An update request is processed for the manifest → The system blocks the update and generates error message 'CHANGE NOT APPLIED - CSA MANIFEST ARRIVED'
[Block Update - Broker Conflict]
An update request is processed that would change broker information → The system blocks the update and generates an error message indicating broker entry conflict prevents changes
[Is 309 Transmission Locked?]
The 309 transmission is locked by user (GCCC-309-LOCKED equals 'Y') → Block the update operation and set 309 lock error message 'WB UPDATE NOT APPLIED USER MADE CHANGES TO MFST'
[Is CSA Delivered?]
The manifest status is CSA delivered (GCCC-STATUS equals 'CSA-DLV') → Block the update operation and set CSA delivery error message 'CHANGE NOT APPLIED - CSA MANIFEST ARRIVED'
[Does Broker Entry Exist?]
A broker entry has been filed for this manifest (broker entry is present) → Block the update operation and set broker entry error message 'BROKER UPDATE NOT APPLIED BROKER ENTRY PRESENT'
[Is Multi-Bill Shipment?]
The shipment is a multi-bill shipment (GCCC-MULTI-BILL-SHIPMENT equals 'Y') → Block the update operation and set multi-bill error message
[All Validations Passed]
The manifest is not on a train AND 309 transmission is not locked AND cargo has not arrived AND manifest is not CSA delivered AND no broker entry exists AND it is not a multi-bill shipment → Allow the update operation to proceed without setting any error flags
[Check Update Request]
The 309 transmission lock status is checked for the manifest → The system determines whether to proceed with update or block it based on lock status
[Block Update Process]
The update process attempts to modify manifest data → The system blocks the update process and prevents any changes to the manifest to preserve user manual modifications
[Continue Normal Processing]
The error handling is complete → The system continues with normal program processing flow without terminating the entire operation
[Create Email Notification]
The system processes the error notification → The system creates an email notification containing the error details
[Manifest Deletion Block]
The manifest has CSA-DLV status:
is a multi-bill with followers
has DELETE-ACTIVE status
is reported on a train
has RELEASE status
has HOLD status (for 6105E)
has broker entry filed (for non-6105E)
→ The system blocks the deletion and generates error message 'DELETION NOT AUTHORIZED'
[Road-Railer Rejection]
The waybill has origin road 974 or 990 AND origin station 000001 or 000002 AND car initial TCSZ or CSRZ or NERZ AND junction symbol 'X' → The system rejects the shipment and generates error message 'ROAD-RAILER SHIPMENT REJECTED'
[Retrieve from MS Table]
The system needs to generate an error message → The system looks up the error text from the MS table using the error number and populates the message field
[Use Predefined Message]
The error type has a predefined message or table lookup fails → The system uses the predefined error message text from internal arrays
[Block Deletion - Already Deleted/Pending]
The manifest status is DELETED or DELPEND → The system blocks the deletion, generates an error message, and sets deletion block flag
[Block Deletion - Released Status]
The manifest status is RELEASE → The system blocks the deletion, generates an error message, and sets deletion block flag
[Block Deletion - CSA Delivered]
The manifest status is CSA-DLV → The system blocks the deletion, generates an error message, and sets deletion block flag
[Block Deletion - Active Delivery]
The manifest status is DLACTIV → The system blocks the deletion, generates an error message, and sets deletion block flag
[Block Deletion - On Train]
The manifest has been reported on a train (train ID is not empty) → The system blocks the deletion, generates an error message, and sets deletion block flag
[Block Deletion - Broker Entry Present]
A broker entry has been filed for the manifest → The system blocks the deletion, generates an error message, and sets deletion block flag
[Block Deletion - Hold Status]
The manifest is in Hold status → The system blocks the deletion, generates an error message, and sets deletion block flag
[Block Deletion - AGI Hold Status]
The manifest is in AGI-Hold status → The system blocks the deletion, generates an error message, and sets deletion block flag
[Block Deletion - Multi-Bill Requires Manual]
The manifest is a multi-bill manifest with follower manifests → The system blocks the deletion, generates an error message indicating manual deletion required, and sets deletion block flag
[Block Deletion Operation]
The system attempts to process a deletion operation → The system blocks the deletion operation and maintains the current manifest state
[Set Blocking Flag]
The system detects the broker entry conflict during update validation → The system sets a blocking flag to prevent the update from proceeding
[Block Deletion - Multi-Bill Contains Followers]
The system checks for follower dependencies → The system blocks the deletion and generates an error message indicating manual deletion is required
[Block Update - Multi-Bill Change Restriction]
The system checks for multi-bill change restrictions → The system blocks the update and generates an error message indicating the change is not allowed
[Has Followers?]
The system checks if the manifest has follower relationships → If followers exist, block deletion with error message 'MULTI-BILL REQUIRES MANUAL DELETION'; if no followers, proceed to train reporting check
[Manifest on Train?]
The system checks if the manifest has been reported on a train (CP-TRAIN-ID is not empty) → If manifest is on train, block deletion with error message 'MANIFEST ON A TRAIN'; if not on train, proceed to hold status check
[In Hold or AGI-Hold?]
The system checks if the manifest status is HOLD or AGI-HOLD → If in hold status, block deletion with error message 'MANIFEST IN HOLD STATUS'; if not in hold, proceed to broker entry check
[Broker Entry Filed?]
The system checks if a broker entry has been filed for the manifest → If broker entry is filed, block deletion with error message 'BROKER ENTRY PRESENT'; if no broker entry, authorize deletion
[Update Manifest Status]
The system updates manifest status → Set appropriate manifest status based on transmission requirements and processing state, preserving existing status flags where applicable
[Preserve Original Spawn Data]
The system needs to modify spawn message data → The system saves the original spawn data to ensure it can be restored after the follower update transaction
[Update Spawn Message with Follower Data]
The system updates the spawn message → The system sets SPAWN-WAYBILL from GCCC-WAYBILL-KEY-FOR-INDEX, SPAWN-WAYBILL-DATE from GCCC-WAYBILL-DATE-INDEX, SPAWN-CAR-ID from GCCC-EQUIPMENT-ID-FOR-INDEX, and SPAWN-CCN from CARGO-CTL-NO
[Spawn GCX011 Update Transaction]
The system initiates the follower update transaction → The system spawns a GCT0111E transaction using the updated spawn data to process the follower manifest update
[Is Manifest on Train?]
The manifest has been assigned to a train (CDN-CUS-NORTH-TRAIN-ID is not empty) → The system blocks the update and generates error message 'WB UPDATE NOT APPLIED MANIFEST ON A TRAIN'
[Is 309 Locked?]
The manifest has been manually locked by a user (309-LOCKED status is true) → The system blocks the update and generates error message 'WB UPDATE NOT APPLIED USER MADE CHANGES TO MFST'
[Has Cargo Arrived?]
The manifest is a 6105E type and the cargo has arrived (ARRIVAL-IND is populated) → The system blocks the update and generates error message 'WB UPDATE NOT APPLIED CARGO IS ARRIVED'
[Is CSA Delivered?]
The manifest status is CSA-DLV (CSA delivered) → The system blocks the update and generates error message 'CHANGE NOT APPLIED - CSA MANIFEST ARRIVED'
[Broker Entry Present?]
A broker entry is present and either the broker names don't match (for 6105E) or the CCN differs from waybill CCN (for non-6105E) → The system blocks the update and generates error message 'BROKER UPDATE NOT APPLIED BROKER ENTRY PRESENT'
[Status = DELETED or DELPEND?]
The manifest status is DELETED or DELPEND → The system blocks the deletion and returns message 'Already Deleted/Pending'
[Status = RELEASE?]
The manifest status is RELEASE → The system blocks the deletion and returns message 'Released Status'
[Status = CSA-DLV?]
The manifest status is CSA-DLV → The system blocks the deletion and returns message 'CSA Delivered'
[Status = DLACTIV?]
The manifest status is DLACTIV → The system blocks the deletion and returns message 'Delete Active Status'
[Manifest on Train?]
The CDN-CUS-NORTH-TRAIN-ID field is not empty → The system blocks the deletion and returns message 'Reported on Train'
[Broker Entry Filed?]
A broker entry has been filed for the manifest → The system blocks the deletion and returns message 'Broker Entry Present'
[Status = HOLD or AGI-HOLD?]
The manifest status is HOLD or AGI-HOLD → The system blocks the deletion and returns message 'Hold Status Active'
[Multi-Bill Manifest with Followers?]
The manifest is a multi-bill manifest with follower records → The system blocks the deletion and returns message 'Multi-Bill Requires Manual'
[Check Train Reporting Fields]
The system checks if the manifest has been reported on a train by validating the CDN-CUS-NORTH-TRAIN-ID field → If the train ID field is not empty, the system blocks the deletion request, sets error message 'WB UPDATE NOT APPLIED MANIFEST ON A TRAIN', and generates an error response. If the train ID field is empty, the system allows the deletion to proceed
[Check Manifest Status]
The system checks the manifest status and finds it is in HOLD or AGI-HOLD status → The system blocks the deletion, generates error message 'DELETION BLOCKED - MANIFEST IN HOLD STATUS', sets error flag, and logs the deletion block event
[Block Deletion]
The system checks the GCCC-BROKER-ENTRY-FILED flag AND the flag value equals 'Y' → The system blocks the deletion operation AND sets error message 'BROKER UPDATE NOT APPLIED BROKER ENTRY PRESENT' AND sets deletion prevention flag AND logs the deletion block event AND returns error to user
[Broker Information Available?]
The system checks for broker information availability → If broker information is available, extract Merlin ID from broker data; otherwise route to unknown broker handling
[Extract Merlin ID from Broker Data]
The system processes known broker information → Extract the Merlin ID from the broker data for message transmission routing
[Unknown Broker - Route to Merlin]
The system encounters an unknown broker scenario → Route the message to the default Merlin system for unknown broker handling
[Prepare Merlin Message Structure]
The system prepares the Merlin message structure → Initialize the message structure with proper formatting and required fields for Merlin transmission
[Set Message Type and Priority]
The system sets message type and priority parameters → Configure message type based on notification requirements and set appropriate priority level for processing
[Populate Manifest Data in Message]
The system populates manifest data in the message → Include all relevant manifest information such as origin, destination, and cargo details in the message structure
[Add Cargo Control Number]
The system adds the cargo control number → Include the CCN in the message to uniquely identify the shipment for broker processing
[Include Waybill Information]
The system includes waybill information → Add waybill number and related shipping details to provide complete shipment context in the message
[Set Delivery Schedule Parameters]
The system sets delivery schedule parameters → Configure delivery timing and schedule preferences based on broker requirements and shipment urgency
[Spawn GCT0191E Transaction]
The system spawns GCT0191E transaction → Create and initiate GCT0191E transaction with the prepared message data for Merlin processing
[Send Message to Merlin System]
The system sends the message to Merlin system → Transmit the message through the Merlin communication interface to notify the broker
[Log Successful Transmission]
The system logs the successful transmission → Record transmission success with timestamp, message details, and broker information for audit trail
[Set Notification Status]
The system sets notification status → Update notification status to reflect successful delivery or error condition for tracking and follow-up
[Block Update - User Made Changes]
The 309 manifest is locked due to user manual changes → The system blocks the update and generates error message 'WB UPDATE NOT APPLIED USER MADE CHANGES TO MFST'
[Create Manifest Data Segments]
The manifest data segments creation step is initiated → The system creates manifest data segments and sets record types for segments 52 through 56
[Set Status to SENT]
The broker is found to be valid and transmission is enabled → The manifest status is set to SENT
[Block Update - CSA Delivered]
The manifest status is CSA-DLV (CSA delivered) → The update is blocked and an error message 'CHANGE NOT APPLIED - CSA MANIFEST ARRIVED' is generated
[Current Status Valid for Update?]
The system checks if the current status allows updates → The update is authorized if status is valid, otherwise it is blocked with appropriate error message
[Parse Broker Name Format]
The system identifies the broker format pattern (CUSTOMS BROKER, BROKER, CB, or XQ with optional colons) → The broker name is extracted from the corresponding character positions based on the identified pattern
[309 Lock Status?]
The system checks for transmission conflicts → Transmission proceeds if manifest is not locked, otherwise transmission is blocked due to lock status
[Original Sent Status?]
The system processes transmission timing → If this is the first transmission, set original sent timestamp to current time, otherwise preserve existing timestamp
[Determine Action Code]
The system determines transmission action code → Action code is set based on corrector status, manifest state, and processing context to indicate the type of transmission required
[Set ADD Action]
The system determines action code type as new manifest → Action code is set to ADD to indicate this is a new manifest submission
[Set MOD Action]
The system determines action code type as updated manifest → Action code is set to MOD to indicate this is a manifest modification
[Set DELETE Action]
The system determines action code type as deleted manifest → Action code is set to DELETE to indicate this manifest is being cancelled
[Control Pre-Emanifest Indicator]
The system controls pre-emanifest indicator setting → Pre-emanifest indicator is set appropriately based on whether this is advance notification or final manifest submission
[Skip Customs Notification]
The system determines if customs notification is required → Customs notification is skipped and transmission process ends without sending to customs
[Proceed with Transmission]
The system determines transmission should proceed → Standard transmission process continues with customs notification and appropriate action codes
[Identify Follower Manifests]
The system needs to process follower manifests → The system retrieves all follower manifests linked to the master CCN using the B0 segment
[Determine Required Segments]
If segment requirements → Required segments are identified for creation based on data content and business needs
[Create Segment 52 - Basic Manifest Data]
Segment 52 creation is initiated → Segment 52 is populated with CCN, waybill number, car information, and essential manifest details
[Create Segment 53 - Additional Manifest Info]
Segment 53 creation is initiated → Segment 53 is populated with extended manifest details and supplementary shipment information
[Create Segment 55 - Status & Control Info]
Segment 55 creation is initiated → Segment 55 is populated with current status, control flags, and processing indicators
[Create Segment 56 - Extended Manifest Data]
Segment 56 creation is initiated → Segment 56 is populated with additional manifest details and extended attributes
[Set Record Types for Each Segment]
Record type assignment is performed → Each segment is assigned its corresponding record type (52, 53, 54, 55, 56) for proper identification
[Classify Data Origin Source]
Data origin classification is performed → The origin source is classified as Order Entry, Fastway, or EDI based on the data source
[Set EDI Origin]
Data origin is being classified → The data origin is set to EDI classification
[Populate Creation Date & User Info]
Creation metadata is being populated → Current date, time, and user identification are recorded in the manifest segments
[Populate Car ID Information]
Car information is being populated in segments → Car initials, car numbers, and equipment details are recorded in appropriate manifest segments
[Write Segments to Database]
Database write operation is initiated → All segments are successfully written to the database with proper keys and relationships
[Log Segment Creation Success]
Success logging is performed → Segment creation success is recorded in system logs with timestamp and details
[Assign CCN Key to All Segments]
The system processes manifest data segments for database storage → The CCN is assigned as the primary key to all manifest data segments (52, 53, 54, 55, 56)
[Assign Record Type to Segment 52 Basic Manifest Data]
The system processes the segment for database storage → Record type '52' is assigned to the basic manifest data segment and stored in GCSCCS52 database table
[Assign Record Type to Segment 53 Equipment Information]
The system processes the segment for database storage → Record type '53' is assigned to the equipment information segment and stored in GCSCCS53 database table
[Assign Record Type to Segment 55 Additional Data]
The system processes the segment for database storage → Record type '55' is assigned to the additional data segment and stored in GCSCCS55 database table
[Assign Record Type to Segment 56 Extended Information]
The system processes the segment for database storage → Record type '56' is assigned to the extended information segment and stored in GCSCCS56 database table
[All Segments Processed?]
The system checks processing completion status → Processing continues until all segments (52, 53, 54, 55, 56) have been assigned keys and record types, then the operation is marked complete
[Set Segment Key with CCN]
The system sets the segment key → The CCN (Cargo Control Number) is assigned as the segment key identifier
[Set Creation Date and User Information]
The system sets the segment metadata → The creation date and user information are recorded in the error segment
[Analyze CREATION-SIGNON Value]
The system analyzes the CREATION-SIGNON field pattern → The system classifies the manifest origin as Order Entry, Fastway, or EDI based on the signon pattern and sets the appropriate data origin classification code
[Set Data Origin Classification Code]
The system processes the origin classification → The system sets the corresponding data origin classification code in the manifest record
[Update Manifest Segment 54]
The system updates the manifest segment → The system writes the origin classification to segment 54 of the manifest record
[Set 309 Change Pending Flag]
The system processes transmission status management → The 309 change pending flag is set to indicate pending transmission changes
[First Time Transmission?]
If transmission history → If no original sent timestamp exists, it is classified as first time transmission, otherwise it is a subsequent transmission
[Set Original Sent Timestamp]
The system processes the first 309 transmission → The original sent timestamp is set to the current date and time
[Preserve Original Sent Date/Time]
The system processes subsequent 309 transmissions → The original sent date and time are preserved without modification
[Set Pre-Emanifest Indicator ON]
The system sets transmission indicators → The pre-emanifest indicator is set to ON
[Set Pre-Emanifest Indicator OFF]
The system sets transmission indicators → The pre-emanifest indicator is set to OFF
[Update 309 Transmission Status]
The system finalizes transmission processing → The 309 transmission status is updated with the appropriate status indicators
[Idler Shipment?]
The system checks if the shipment is classified as an idler shipment → If it is an idler shipment, 309 notification is skipped, otherwise 309 notification is enabled
[Skip 309 Notification]
The system processes 309 transmission notifications → The 309 notification processing is skipped
[Enable 309 Notification]
The system processes 309 transmission notifications → The 309 notification processing is enabled
[Set 309 Lock Status]
The system finalizes transmission status management → The 309 lock status is set to control manifest access
[Status Validation Required?]
If status validation is required → If validation is required, transmission eligibility is validated, otherwise status flags are updated directly
[Update Status Flags]
The system finalizes status management → All relevant status flags are updated to reflect the current transmission state
[Set Pre-Emanifest Indicator ON]
The system processes the ADD action for initial transmission → The pre-emanifest indicator is set to ON and the manifest record is updated
[Maintain Current Indicator]
The system processes a subsequent transmission that is not the first time and has no corrector status → The current pre-emanifest indicator value is maintained unchanged and the manifest record is updated
[Check Processing Context]
The system checks the processing context for transmission history and corrector status → The processing context is categorized as first time transmission, subsequent transmission, or corrector status present
[Check Broker Delivery Schedule Type]
The system checks the broker's delivery schedule field → The system should identify whether the schedule type is IMMEDIATE, DEFAULT, or another delivery preference
[Schedule Type?]
If the schedule type value → The system should route to immediate delivery processing if schedule is IMMEDIATE or to default delivery processing if schedule is DEFAULT
[Set IMMEDIATE-DELIVERY Flag]
The system processes the immediate delivery requirement → The system should set the IMMEDIATE-DELIVERY flag to enable immediate broker notification processing
[Prepare X12 EDI Message]
The delivery method is determined to be X12 EDI → The system prepares X12 EDI message format and sets GCWS309C-NOTIFY-BROKER with X12 header information
[Prepare Merlin Message]
The delivery method is determined to be Merlin → The system prepares Merlin message format and spawns GCT0191E transaction with Merlin ID
[Prepare Fax Transmission]
The delivery method is determined to be Fax → The system prepares fax transmission using BK-BROK-FAX-NUMBER from broker information
[Process Immediate Delivery]
The broker delivery schedule is set to immediate → The system processes immediate delivery without queuing or batching delays
[Manifest Status = DELETED?]
If the transmission action code requirements → The action code is set to DELETE for customs transmission
[Original Sent Timestamp Exists?, Corrector Flag Set?]
If the transmission action code requirements → The action code is set to ADD for customs transmission
[Corrector Flag Set?]
If the transmission action code requirements → The action code is set to MOD for customs transmission
[Prepare ADD Transmission]
The system prepares the transmission parameters → The pre-emanifest indicator is set to identify this as a new manifest submission
[Clear Pre-Emanifest Indicator]
The system prepares the transmission parameters → The pre-emanifest indicator is cleared as this is an update to an existing manifest
[309 Locked by User Changes?]
The manifest is locked due to user changes (309 locked flag is true) → Set transmission eligibility to NO and block transmission with reason 'User Made Changes to Manifest'
[Manifest on Train?]
The manifest is already assigned to a train → Set transmission eligibility to NO and block transmission with reason 'Manifest Already on Train'
[Cargo Already Arrived?]
The cargo has already arrived at the destination → Set transmission eligibility to NO and block transmission with reason 'Cargo Already Arrived'
[Set Transmission Eligible = YES]
The manifest status is not deletion-related AND status is not release/delivery-related AND carrier index is not 999 AND manifest is not locked by user changes AND manifest is not on train AND cargo has not arrived → Set transmission eligibility to YES and allow 309 customs transmission to proceed
[Set Pre-Emanifest Indicator for ADD Action]
The action code is ADD → The pre-emanifest indicator is set to active status
[Update Pre-Emanifest Indicator for MOD Action]
The action code is MOD → The pre-emanifest indicator is updated to modification status
[Clear Pre-Emanifest Indicator for DELETE Action]
The action code is DELETE → The pre-emanifest indicator is cleared and set to inactive status
[First Time Transmission]
The system processes the first-time transmission → The system sets the original sent date to current date AND sets the original sent time to current time AND updates the manifest with these timestamp values
[Subsequent Transmission]
The system processes a subsequent transmission → The system preserves the existing original sent date AND preserves the existing original sent time AND does not overwrite the original timestamp values
[Check CCN-ORIGINAL-SENT Status]
The system checks the CCN-ORIGINAL-SENT field status → IF CCN-ORIGINAL-SENT is empty or spaces THEN route to first-time transmission processing ELSE route to subsequent transmission processing
[Set Immediate Delivery]
The delivery schedule evaluation determines immediate delivery is needed → Delivery priority is set to immediate and notification channels are prioritized accordingly
[Send X12 EDI Notification]
X12 EDI is the selected notification method → Manifest notification is formatted in X12 standard and transmitted to secondary broker's EDI system
[Send Fax Notification]
Fax notification is the selected method → Manifest notification is formatted and queued for fax transmission to secondary broker's fax number
[Schedule Type?]
If the delivery schedule type value → If schedule type is 'IMMEDIATE-DELIVERY', set immediate delivery flag; if 'DEFAULT-DELIVERY', set default delivery flag; otherwise set delivery schedule error
[Set Immediate Delivery Flag]
The system processes the immediate delivery requirement → The immediate delivery flag is set to enable real-time broker notifications
[X12 EDI Available?]
If available notification channels → If X12 EDI is available and preferred, prepare X12 EDI notification with appropriate header information
[Prepare X12 EDI Notification]
The system prepares the notification for delivery → Set GCWS309C-NOTIFY-BROKER with X12 header information and configure EDI routing parameters
[Merlin System Available?]
If Merlin system as a notification option → If Merlin system is available, prepare Merlin notification for delivery
[Internet Address Available?]
If internet notification options → If B1-INTERNET-ADDRESS is populated and valid, prepare internet-based notification
[Use BK-BROK-FAX-NUMBER]
The system configures the notification delivery → Use BK-BROK-FAX-NUMBER as the delivery endpoint for fax transmission
[Default or Immediate Delivery?]
The system determines delivery timing → If broker preference is DEFAULT or not specified, set default delivery schedule; if IMMEDIATE is specified, set immediate delivery schedule
[Set Immediate Delivery Schedule]
The system configures delivery timing parameters → Set delivery schedule to immediate processing and prioritize notification for real-time delivery
[Send Broker Notification]
The system sends arrival notifications → Send notifications through all configured channels: X12 EDI if available, Merlin system if configured, Internet delivery if enabled, Fax transmission if setup, and Paper notification if required, using action code '04' for arrival notifications
[Delivery Method?]
The system determines how to notify the broker of arrival → Select the delivery method based on broker preferences: X12 EDI for electronic transmission, Merlin for system messaging, Internet for web-based delivery, Fax for document transmission, or Paper for physical delivery
[Send X12 EDI Notification]
The system sends arrival notification via X12 EDI → Transmit arrival notification using X12 EDI format with action code '04' for arrival notifications
[Spawn Customs Transmission for Deletion]
The system processes customs notification requirements → A customs transmission for deletion is spawned to notify customs authorities of the manifest cancellation
[Prepare Spawn Data for Follower Update]
The system prepares spawn data for the follower update → Preserve original spawn message, copy follower waybill key, waybill date, equipment ID, and CCN to spawn data
[Restore Original Spawn Data]
The system completes processing for the current follower → Restore the original spawn message data before processing the next follower
[Call FWWWBIO Segment]
The system calls the Fastway waybill interface → The waybill data is retrieved and availability status is determined
[Shipment Minimum Data Retrieval - Retrieve shipment minimum data segments from Fastway system for manifest processing]
The system calls the Fastway system with segment type 'SHIPMIN', segment ID 'S', and segment number '1' → The system should retrieve and store the shipment minimum data if successful, or clear the SHIPMINS data if the retrieval fails
[Set Fastway Call Parameters]
The system sets up the Fastway call parameters → The segment type should be set to 'SHIPMIN', segment ID should be set to 'S', and segment number should be set to '1'
[Validation Successful?]
If the validation results → If validation successful, continue processing, otherwise generate error message and set error flags
[Set Up Fastway Call Parameters]
Setting up the Fastway system call parameters → The segment type is set to 'SHIPMIN', segment ID is set to 'S', and segment number is set to '1'
[Call FWCWBIO with SHIPMIN Segment]
The system calls FWCWBIO to retrieve shipment minimum data → The Fastway system is accessed to retrieve the specified shipment minimum segment
[Manifest Status Check]
The manifest status is 'SENT' or 'MANUAL' → The action code is set to 'ADD' for customs transmission processing
[Manifest Status Check]
The manifest status is 'DELETED' → The action code is set to 'DEL' for customs transmission processing
[Set TRIEX Load Number]
The system prepares customs transmission data → The TRIEX load number is set based on the manifest information
[Spawn Customs Transmission Transaction]
The system completes the cargo report update process → A customs transmission transaction (GCT1401E) is spawned for downstream processing
[Update Spawn Message with Follower Data]
The system processes an individual follower manifest → The spawn message must be updated with the follower's waybill key, waybill date, equipment ID, and CCN number from the follower manifest data
[Set Follower Waybill Key]
The system updates the spawn message with follower data → The GCCC-WAYBILL-KEY-FOR-INDEX from the follower manifest must be moved to SPAWN-WAYBILL in the spawn message
[Set Follower Waybill Date]
The system updates the spawn message with follower data → The GCCC-WAYBILL-DATE-INDEX from the follower manifest must be moved to SPAWN-WAYBILL-DATE in the spawn message
[Set Follower Equipment ID]
The system updates the spawn message with follower data → The GCCC-EQUIPMENT-ID-FOR-INDEX from the follower manifest must be moved to SPAWN-CAR-ID in the spawn message
[Set Follower CCN Number]
The system updates the spawn message with follower data → The CARGO-CTL-NO from the follower manifest must be moved to SPAWN-CCN in the spawn message
[Execute Spawn Operation]
The system executes the spawn operation for the follower → A GCX011 transaction must be spawned with the follower-specific data to process the manifest update
[Restore Original Spawn Data]
The system completes processing of the current follower → The original spawn data must be restored from the backup variables to the spawn message fields
[Retrieve English Text GCSTBRT-MS-ENG-TEXT]
The message lookup is successful → The system should move the English text from GCSTBRT-MS-ENG-TEXT to MSG-LABEL for display

Structural Validations

[41:Error Reporting and Logging]
The system reports errors → Generate appropriate error messages: 'CHANGE NOT APPLIED - CSA MANIFEST ARRIVED' for CSA-DLV status, 'CHANGE NOT APPLIED - MASTER MFST INACTIVE' for inactive master, 'CHANGE NOT APPLIED - WAYBILL COMPLETED' for completed waybills, 'CHANGE NOT APPLIED - MANIFEST MANUALLY CHANGED' for manual changes, and send error notifications via email system
[1400-GET-WAYBILL-INFO: Validate Spawn Data]
The system validates the spawn waybill number → If the waybill number is empty or spaces, set error flag and stop processing with message 'WAYBILL NUMBER IS REQUIRED'
[Check Origin Road Number - Validate ORIG-RD-NUM against rejection criteria (974, 990)]
The origin road number is 974 and the origin station number is either 000001 or 000002 → The system sets the road-railer rejection flag and generates a rejection message
[Check Origin Road Number - Validate ORIG-RD-NUM against rejection criteria (974, 990)]
The origin road number is 990 and the origin station number is either 000001 or 000002 → The system sets the road-railer rejection flag and generates a rejection message
[Generate Rejection Message]
The system processes the rejection → A rejection message is generated to inform about the road-railer rejection
[Generate Country Code Error Message]
Either the manifest-from-port is missing or the port validation fails → The system generates a country code validation error message and prevents further processing of the shipment
[Generate Country Code Error]
The system processes the validation failure → Appropriate error message is generated and processing stops with error status
[FROM Port Available?]
The system checks if manifest-from-port field is populated → If manifest-from-port is empty, generate error message 'MANIFEST FROM PORT IS REQUIRED' and stop validation process
[Station Found in MC Table?]
If the lookup result status → If station is not found in MC table, generate error message indicating invalid entry station and stop validation
[Customs Code ≠ '00000'?]
If the customs code equals '00000' → If customs code equals '00000', generate error message indicating invalid entry station due to inactive customs authorization
[Extract waybill number and date from spawn data with validation]
System validates the action code → If action code is ADD-FUNCTION, IIS-ADD-FUNCTION, or DEL-FUNCTION, proceed with message field population, otherwise set invalid action code error flag
[Extract waybill number and date from spawn data with validation]
System processes invalid components → Generate error message for invalid components and end waybill component processing
[Generate Date Validation Error]
System processes the date validation failure → Generate date validation error message and complete date extraction process with error status
[Check action code against allowed values (ADD, IIS-ADD, DEL) with error handling]
The system validates the action code against allowed values ADD, IIS-ADD, or DEL → If the action code matches ADD, IIS-ADD, or DEL, set valid action code flag and continue processing. If the action code does not match any allowed value, set invalid action code error flag, generate invalid action code error message, populate error message fields, set processing error status, and stop validation processing
[Set Invalid Action Code Error Flag]
The system determines the action code is invalid → Set invalid action code error flag to trigger error message generation and error handling process
[Generate Error Message: Invalid Action Code]
The system processes the invalid action code error → Throw error: indicating that the action code is invalid and specify the allowed values
[Populate Error Message Fields]
The system prepares error information for user notification → Populate error message fields with the invalid action code error details including error description and context information
[Set Processing Error Status]
The system finalizes error handling for invalid action code → Set processing error status to prevent further processing and indicate validation failure
[Waybill is spaces or empty?]
The system validates the extracted waybill number → If waybill is spaces or empty, system should set error flag and display 'WAYBILL NUMBER IS REQUIRED' message
[Set error message: 'WAYBILL NUMBER IS REQUIRED']
The system sets error information → The error message should be set to 'WAYBILL NUMBER IS REQUIRED' to inform user of the missing mandatory field
[Set Invalid Carrier Error]
System sets invalid carrier error condition → Invalid carrier error flag and message are set for error handling
[Set Error Flag and Message]
System sets error flag and message → Error flag is set with appropriate error message for downstream error handling
[Generate Error Message]
The system generates error messages for the validation failure → Appropriate error message is created describing the origin station validation issue
[Block Update - Manifest on Train]
The manifest has a train assignment (CDN-CUS-NORTH-TRAIN-ID is not empty) → The system blocks the update and generates error message 'CHANGE NOT APPLIED - MANIFEST ON TRAIN'
[Block Update - Cargo Arrived]
The cargo has arrived (ARRIVAL-IND field is populated for 6105E type manifests) → The system blocks the update and generates error message 'CHANGE NOT APPLIED - CARGO ARRIVED'
[Block Update - Multi-Bill Changes Not Allowed]
The shipment is a multi-bill shipment and the update would create inconsistencies across related manifests → The system blocks the update and generates error message 'CHANGE NOT APPLIED - MULTI-BILL CHANGES NOT ALLOWED'
[Block Update - Invalid Status]
The manifest status is DELETED, DELPEND, or REJECT → The system blocks the update and generates error message 'CHANGE NOT APPLIED - INVALID STATUS'
[Block Update - Invalid Carrier]
The carrier index is 999 (indicating invalid or test carrier) → The system blocks the update and generates error message 'CHANGE NOT APPLIED - INVALID CARRIER'
[Log Error Message]
The system logs the error message → The system records error message with waybill number, error type, and continues processing remaining ships
[Generate Error Message]
Any blocking condition is encountered (train status, locked status, arrival status, CSA delivery, or broker conflicts) → Generate specific error message corresponding to the blocking condition and send via error reporting system
[Create Segment 54 - Error Messages]
Error message tracking is required → Segment 54 is created to store error messages, validation failures, and processing warnings
[Populate Error Message Numbers]
Error message population is performed → Error message numbers and corresponding descriptive text are populated in segment 54
[Validate All Segments Created]
Segment creation validation is performed → The system confirms that segments 52, 53, 54, 55, and 56 have been successfully created with all required data elements
[Check WS-MSG-ERROR-NBR Array]
The system checks the WS-MSG-ERROR-NBR array for error numbers → If error numbers are found in the array, they are extracted and prepared for error message processing
[Combine Error Numbers from Both Arrays]
The system combines error numbers from both arrays → All error numbers are consolidated into a single collection for error message creation
[Create Error Message Segment 54]
The system creates an error message segment → A segment 54 is created with the appropriate structure for error message transmission
[Populate Segment with Combined Error Numbers]
The system populates the segment with error numbers → The error message segment contains all relevant error numbers from both validation arrays
[Validation Errors Found?]
If validation errors were encountered → If validation errors exist, proceed with error collection; otherwise skip error segment creation
[Collect Error Numbers from WS-MSG-ERROR-NBR Array]
The system begins error collection process → All error numbers from WS-MSG-ERROR-NBR array are collected for error segment creation
[Combine All Error Numbers]
The system processes the collected errors → All error numbers are combined into a consolidated list for error segment population
[Classify Data Origin Source]
The system needs to identify the data origin source → The creation signon field is evaluated to determine if data originated from Order Entry, Fastway, or EDI system
[Populate Error Segment with Car ID]
The system populates error segment details → Car identification information is added to the error segment for tracking purposes
[Store Error Segment 54]
The system completes error segment creation process → The error segment is stored in the database and available for error tracking and reporting
[Error Segment Creation Complete]
The error segment creation process finishes → The system marks the error segment creation as complete and returns control to the main processing flow
[Manifest Status Valid for Transmission?]
The system checks if the manifest status is valid for transmission → The system should reject transmission if status is DELETED, DELPEND, REJECT, RELEASE, CSA-DLV, or DLACTIV, otherwise allow transmission to proceed
[Check Carrier Index ≠ 999]
The system validates the carrier index for transmission eligibility → The system should allow transmission only if carrier index is not equal to 999
[Extract Port Code from Manifest-To-Trans-Code - Parse port code from positions 2:3 with validation]
The system needs to validate broker information → The system extracts port code from positions 2-3 of manifest-to-trans-code field for broker table lookup
[Validate IMMEDIATE-DELIVERY Schedule]
The system validates the immediate delivery schedule parameters → Confirm the schedule supports immediate notification capabilities or flag as invalid if requirements are not met
[Validate Immediate Delivery Parameters]
The system validates immediate delivery parameters → The system confirms immediate delivery configuration is valid and sets appropriate delivery method
[Generate Validation Error]
The system generates a validation error → The system creates appropriate error message indicating delivery schedule validation failure
[Validate Immediate Delivery Rules]
The system validates immediate delivery business rules → The system checks delivery method compatibility, business hour constraints, and other immediate delivery requirements
[Validate Delivery Method]
The system validates the delivery method → The system ensures the configured delivery method (X12, Merlin, Internet, Fax, Paper) supports immediate delivery processing
[Handle EDI Transmission Error]
System handles transmission error → Transmission error is processed and error details are logged for troubleshooting
[Valid Merlin ID?]
The system validates the Merlin ID → The system proceeds to set up message structure if valid, otherwise handles delivery failure
[Check Broker Fax Number Available]
The system checks for fax transmission capability → The system determines if BK-BROK-FAX-NUMBER is present and not empty
[Validate Fax Number Format]
The system prepares for fax transmission → The system validates the fax number format is acceptable for transmission
[Multi-Bill Change Block]
The system identifies a multi-bill change restriction violation → The system sets error message number for multi-bill block, populates error message text 'WB UPDATE NOT APPLIED MANIFEST ON A TRAIN', creates error segment 54, and sets processing flags to block the change
[Train Status Block]
The system detects train assignment status that blocks updates → The system sets error message number for train status block, populates error message text 'WB UPDATE NOT APPLIED MANIFEST ON A TRAIN', creates error segment 54, and sets processing flags to prevent the update
[309 Lock Block]
The system detects 309 lock status that prevents automated updates → The system sets error message number for 309 lock block, populates error message text 'WB UPDATE NOT APPLIED USER MADE CHANGES TO MFST', creates error segment 54, and sets processing flags to block the change
[Cargo Arrived Block]
The system detects cargo arrival status that blocks further updates → The system sets error message number for cargo arrived block, populates error message text 'WB UPDATE NOT APPLIED CARGO IS ARRIVED', creates error segment 54, and sets processing flags to prevent the update
[CSA Delivered Block]
The system detects CSA delivered status that prevents modifications → The system sets error message number for CSA delivery block, populates error message text 'CHANGE NOT APPLIED - CSA MANIFEST ARRIVED', creates error segment 54, and sets processing flags to block the change
[Broker Entry Block]
The system detects existing broker entry that conflicts with the update request → The system sets error message number for broker entry block, populates error message text 'BROKER UPDATE NOT APPLIED BROKER ENTRY PRESENT', creates error segment 54, and sets processing flags to prevent the broker update
[Set Error Message Number]
The system needs to assign a specific error message number for the error type → The system sets the corresponding error message number that maps to the specific error condition for downstream processing and reporting
[Populate Error Message Text]
The system needs to provide descriptive error message text for user communication → The system retrieves the corresponding error message text from the message table and populates the error message field with human-readable description of the error
[Create Error Segment 54]
The system needs to create a formal error record for tracking and audit purposes → The system creates error segment 54 with error details, message number, message text, and relevant context information for error logging and reporting
[Manifest on Train?]
The system checks if the manifest is already assigned to a train by verifying CDN-CUS-NORTH-TRAIN-ID is not empty → The system blocks the waybill update and generates error message 'WB UPDATE NOT APPLIED MANIFEST ON A TRAIN'
[309 Transmission Locked?]
The system checks if the manifest is locked by verifying 309-LOCKED flag is true → The system blocks the waybill update and generates error message 'WB UPDATE NOT APPLIED USER MADE CHANGES TO MFST'
[Cargo Arrived?]
The system checks if cargo has arrived by verifying ARRIVAL-IND is populated for 6105E CCNs → The system blocks the waybill update and generates error message 'WB UPDATE NOT APPLIED CARGO IS ARRIVED'
[CSA Delivered?]
The system checks if the manifest status is CSA-DLV → The system blocks the change and generates error message 'CHANGE NOT APPLIED - CSA MANIFEST ARRIVED'
[Broker Entry Present?]
The system checks if broker entry exists and validates broker name consistency for 6105E CCNs or CCN consistency for non-6105E CCNs → The system blocks the change if validation fails and generates error message 'BROKER UPDATE NOT APPLIED BROKER ENTRY PRESENT'
[Generate Error Message]
The system needs to communicate the reason for blocking the change → The system generates the appropriate error message based on the specific validation rule that was violated
[Retrieve Shipment Data]
The system attempts to retrieve SHIPMIN segment → If retrieval fails, clear all SHIPMINS data fields
[Retrieve Error Messages]
The system retrieves error message text from 'MS' table → Set MSG-LABEL with English text if found, otherwise set to spaces
[Validate Entry Stations]
The system checks the CC-STATUS-CODE field → If CC-STATUS-CODE is SPACES then set EMTZ-FOUND flag, otherwise set EMTZ-NOT-FOUND flag
[Error Message Access]
The request type is identified as error message access → The system routes to message table access method for error message retrieval
[Database Call Execution and Error Handling]
The system checks CC-STATUS-CODE field and finds it contains spaces → The system sets EMTZ-FOUND flag to indicate valid status
[Database Call Execution and Error Handling]
The system checks CC-STATUS-CODE field and finds it contains non-space values → The system sets EMTZ-NOT-FOUND flag to indicate invalid status
[MS Table Lookup - Error Messages]
The system performs MS table lookup using the error number → The system returns English error message text or spaces if message not found
[Validate Spawn Waybill Number]
The system validates the waybill number in the spawn data → If waybill number is missing, set error flag and stop processing with error message
[Generate Error Message]
The system processes the blocked operation → An appropriate error message is generated indicating the specific reason for blocking the operation
[Send Multi-Bill Error Email]
The error handling process is executed → An error notification email is sent to appropriate recipients with details of the multi-bill processing failure
[Generate Multi-Bill Error Message]
The system generates error messages based on the violation type such as CSA delivery status, broker entry mismatches, or multi-bill follower restrictions → The system creates appropriate error messages including 'CHANGE NOT APPLIED - CSA MANIFEST ARRIVED', 'CHANGE NOT APPLIED - MANIFEST MANUALLY CHANGED', or 'MULTI-BILL CONTAINS FOLLOWERS - DELETE MANUALLY' with corresponding error codes
[Return Error Status to User]
The system returns processing results to the requesting user → The system provides error status response including specific error message, affected CCN information, recommended user actions, and contact information for manual resolution assistance
[Train Status Check]
The system checks if CDN-CUS-NORTH-TRAIN-ID is not empty → The system blocks the status change and generates error message 'WB UPDATE NOT APPLIED MANIFEST ON A TRAIN'
[309 Lock Status Check]
The system checks if 309-LOCKED flag is set to true → The system blocks the status change and generates error message 'WB UPDATE NOT APPLIED USER MADE CHANGES TO MFST'
[Cargo Arrival Check]
The system checks if ARRIVAL-IND field is populated indicating cargo arrival → The system blocks the status change and generates error message 'WB UPDATE NOT APPLIED CARGO IS ARRIVED'
[CSA-DLV Status]
The system checks if current manifest status is CSA-DLV → The system blocks the status change and generates error message 'CHANGE NOT APPLIED - CSA MANIFEST ARRIVED'
[Broker Entry Check]
The system checks if broker entry exists and the new broker name differs from existing broker name → The system blocks the broker update and generates error message 'BROKER UPDATE NOT APPLIED BROKER ENTRY PRESENT'
[Is Manifest on Train?]
The manifest has a train assignment (CDN-CUS-NORTH-TRAIN-ID is not empty) → Block the update operation and set train status error message 'WB UPDATE NOT APPLIED MANIFEST ON A TRAIN'
[Has Cargo Arrived?]
The cargo has arrived at destination (GCCC-CARGO-ARRIVED equals 'Y') → Block the update operation and set cargo arrival error message 'WB UPDATE NOT APPLIED CARGO IS ARRIVED'
[Generate Error Message: WB UPDATE NOT APPLIED MANIFEST ON A TRAIN]
The system needs to communicate the reason for the update block to the user → The system should generate the error message 'WB UPDATE NOT APPLIED MANIFEST ON A TRAIN'
[Set Error Processing Flag]
The system needs to track that an error condition exists → The system should set the error processing flag to enable proper error handling workflow
[Set 309 Lock Error Flag]
The 309 transmission is found to be locked (309-LOCKED equals true) → The system sets the 309 lock error flag to indicate update should be blocked
[Generate Error Message: 'WB UPDATE NOT APPLIED USER MADE CHANGES TO MFST']
The system needs to communicate why the update was blocked → The system generates error message 'WB UPDATE NOT APPLIED USER MADE CHANGES TO MFST' to inform that user manual changes prevent automatic updates
[Log Error to System]
The error logging process is executed → The system logs the 309 lock error event with relevant manifest details for audit trail and system monitoring
[Check Cargo Arrival Status]
The system checks the cargo arrival status and finds that the ARRIVAL-IND field is populated indicating the cargo has already arrived → The system should set the cargo arrival error flag and block the waybill update from proceeding
[Generate Error Message: 'WB UPDATE NOT APPLIED CARGO IS ARRIVED']
The system needs to inform the user why the update was not applied → The system should generate the error message 'WB UPDATE NOT APPLIED CARGO IS ARRIVED' and add it to the error collection for transmission
[Generate Error Message: 'CHANGE NOT APPLIED - CSA MANIFEST ARRIVED']
An update attempt is made on this delivered manifest → The system generates error message 'CHANGE NOT APPLIED - CSA MANIFEST ARRIVED' to inform the user why the update was rejected
[Set CSA Delivery Error Flag]
The manifest status is determined to be CSA-DLV (delivered through CSA) → The system sets a CSA delivery error flag to prevent the update from proceeding
[Log Error to System]
The error flag is set and error message is generated → The system logs the CSA delivery error details to the system error log for tracking and audit purposes
[Return Error to User]
The error handling process is complete → The system returns the CSA delivery error message to the user indicating the update cannot be applied because the manifest has already arrived through CSA
[Generate Error Message: 'BROKER UPDATE NOT APPLIED BROKER ENTRY PRESENT']
The system processes the error condition → The system generates error message 'BROKER UPDATE NOT APPLIED BROKER ENTRY PRESENT' to inform users of the restriction
[Generate Error Message]
The system generates error messages → The system creates appropriate error messages such as 'WB UPDATE NOT APPLIED - MULTI-BILL SHIPMENT' or 'CHANGE NOT APPLIED - CUSTOMS APPLICATION CORRECTION REQUIRED'
[Multi-Bill Update Block]
The manifest has a train assignment (CDN-CUS-NORTH-TRAIN-ID is not empty) → The system blocks the update and generates error message 'WB UPDATE NOT APPLIED MANIFEST ON A TRAIN'
[309 Lock Block]
The manifest has been manually locked by a user (309-LOCKED flag is set) → The system blocks the update and generates error message 'WB UPDATE NOT APPLIED USER MADE CHANGES TO MFST'
[Cargo Arrived Block]
The cargo has arrival indicator populated (ARRIVAL-IND is not empty) → The system blocks the update and generates error message 'WB UPDATE NOT APPLIED CARGO IS ARRIVED'
[CSA Delivered Block]
The manifest status is CSA-DLV (CSA delivered) → The system blocks the update and generates error message 'CHANGE NOT APPLIED - CSA MANIFEST ARRIVED'
[Broker Entry Block]
The existing broker name differs from the new broker name being updated → The system blocks the broker update and generates error message 'BROKER UPDATE NOT APPLIED BROKER ENTRY PRESENT'
[Test Waybill Block]
The reporting station number is between 9990-9999:
the car ID is 'CP 00108076'
→ The system blocks processing and generates error message 'TEST WAYBILL BLOCKED'
[Entry Station Invalid]
The manifest-from-port is empty:
the port doesn't exist in MC table
has invalid Canadian customs code '00000'
→ The system rejects the shipment and generates error message 'INVALID ENTRY STATION'
[CCN Duplicate Error]
The CCN already exists in the system for a different waybill or shipment → The system blocks the creation and generates error message 'DUPLICATE CCN EXISTS'
[Status Validation Error]
The requested status transition is not allowed based on current status and business rules → The system blocks the status change and generates error message 'INVALID MANIFEST STATUS'
[Populate Error Segment]
The error needs to be recorded for processing → The system populates the GCSCCS54 error segment with error code, message text, and related data
[Block Deletion - Rejected Status]
The manifest status is REJECT → The system blocks the deletion, generates an error message, and sets deletion block flag
[Is Manifest Status = DELETED?]
The manifest status is DELETED and a deletion request is processed → The system blocks the deletion operation and generates an error message indicating the manifest is already deleted
[Is Manifest Status = DELPEND?]
The manifest status is DELPEND and a deletion request is processed → The system blocks the deletion operation and generates an error message indicating deletion is already pending
[Is Manifest Status = REJECT?]
The manifest status is REJECT and a deletion request is processed → The system blocks the deletion operation and generates an error message indicating rejected manifests cannot be deleted
[Is Manifest Status = RELEASE?]
The manifest status is RELEASE and a deletion request is processed → The system blocks the deletion operation and generates an error message indicating released manifests cannot be deleted
[Is Manifest Status = CSA-DLV?]
The manifest status is CSA-DLV and a deletion request is processed → The system blocks the deletion operation and generates an error message indicating CSA delivered manifests cannot be deleted
[Is Manifest Status = DLACTIV?]
The manifest status is DLACTIV and a deletion request is processed → The system blocks the deletion operation and generates an error message indicating delete active manifests cannot be deleted
[Is Manifest in Hold Status?]
The manifest status is HOLD and a deletion request is processed → The system blocks the deletion operation and generates an error message indicating manifests in hold status cannot be deleted
[Is Manifest in AGI-Hold Status?]
The manifest status is AGI-HOLD and a deletion request is processed → The system blocks the deletion operation and generates an error message indicating manifests in AGI hold status cannot be deleted
[Has Broker Entry Been Filed?]
The manifest has a broker entry filed and a deletion request is processed → The system blocks the deletion operation and generates an error message indicating manifests with broker entries cannot be deleted
[Is Manifest on Train?]
The manifest is assigned to a train and a deletion request is processed → The system blocks the deletion operation and generates an error message indicating manifests on trains cannot be deleted
[Is Carrier Index = 999?]
The manifest has carrier index equal to 999 and a deletion request is processed → The system blocks the deletion operation and generates an error message indicating manifests with carrier index 999 cannot be deleted
[Generate Hold Status Error Message]
The system needs to communicate the blocking reason → The system generates a hold status error message indicating deletion cannot proceed
[Generate AGI-Hold Status Error Message]
The system needs to communicate the blocking reason → The system generates an AGI-hold status error message indicating deletion cannot proceed
[Check Train Reporting - Validate if manifest has been reported on train]
The system checks if the manifest has been reported on a train by evaluating if CDN-CUS-NORTH-TRAIN-ID is not empty → If CDN-CUS-NORTH-TRAIN-ID contains a value, set train reported flag, generate error message 'WB UPDATE NOT APPLIED MANIFEST ON A TRAIN', and block the waybill update; otherwise allow processing to continue
[Check Broker Entry - Validate if broker entry has been filed for manifest]
The system checks if a broker entry has been filed for the manifest → If broker entry is filed, block the update and generate error message 'BROKER UPDATE NOT APPLIED BROKER ENTRY PRESENT', otherwise allow the update to proceed
[Generate Error Message: 'BROKER UPDATE NOT APPLIED BROKER ENTRY PRESENT']
The system needs to communicate the blocking reason to the user → The system generates error message 'BROKER UPDATE NOT APPLIED BROKER ENTRY PRESENT'
[Set Error Flag]
The system sets error flags for the failure condition → The system marks the operation as failed and prepares for error message generation
[Generate Error Message]
The system generates an error message → The system creates a specific error message describing the multi-bill restriction or validation failure
[Generate Error Message]
Any blocking condition is detected (train reported, hold status, broker entry, or followers) → Block the deletion, generate specific error message based on the blocking condition, and log the deletion block
[Set Error Message: Manual Deletion Required]
The system generates the error response → Set error message indicating that manual deletion is required for multi-bill shipments with active followers
[Waybill Valid?]
The system validates the waybill information for completeness and accuracy → If waybill is valid, proceed with car equipment update; if waybill is invalid, block the car update and generate error message
[Set Equipment Mismatch Error]
The system encounters validation errors → Set equipment mismatch error flag and prepare error message indicating the specific validation failure reason
[Generate Error Message]
The system generates error messages → Create descriptive error message indicating the reason for car update failure and send to appropriate error handling system
[Send Error Notification]
The system has generated a specific error message for the blocking condition → The system sends the error notification through the messaging system and terminates the update process
[Status = REJECT?]
The manifest status is REJECT → The system blocks the deletion and returns message 'Rejected Status'
[Generate Error Message: Manual Deletion Required]
The system needs to communicate the restriction to the user → Generate error message indicating manual deletion is required for multi-bill manifests with followers
[Set Error Message]
The system needs to communicate the reason for blocking the deletion → The system sets the error message to 'WB UPDATE NOT APPLIED MANIFEST ON A TRAIN' to inform the user why the deletion was not permitted
[Transmission Successful?]
The system checks transmission status → If transmission is successful, proceed to log success; otherwise handle transmission error
[Handle Transmission Error]
The system handles the transmission error → Log error details, set appropriate error status, and determine retry or alternative notification methods
[Block Update - Multi-Bill Shipment]
The system validates the shipment type and determines it is a multi-bill shipment → The system blocks the update and generates an error message indicating multi-bill update is blocked
[Block Update - Manifest on Train]
The manifest has a non-empty CDN-CUS-NORTH-TRAIN-ID indicating it is on a train → The system blocks the update and generates error message 'WB UPDATE NOT APPLIED MANIFEST ON A TRAIN'
[Block Update - Cargo Arrived]
The cargo has already arrived as indicated by populated arrival indicator → The system blocks the update and generates error message 'WB UPDATE NOT APPLIED CARGO IS ARRIVED'
[Block Update - CSA Delivered]
The manifest status is CSA-DLV indicating CSA delivery has occurred → The system blocks the update and generates error message 'CHANGE NOT APPLIED - CSA MANIFEST ARRIVED'
[Block Update - Broker Entry Present]
A broker entry is already present and the broker names differ for 6105E CCNs, or CCN differs from waybill CCN for non-6105E CCNs → The system blocks the update and generates error message 'BROKER UPDATE NOT APPLIED BROKER ENTRY PRESENT'
[Check Manifest Train Status]
The manifest has CDN-CUS-NORTH-TRAIN-ID populated indicating it is already on a train → The system should set an error flag, generate error message 'WB UPDATE NOT APPLIED MANIFEST ON A TRAIN', and block the waybill update
[Generate Error Message: 'WB UPDATE NOT APPLIED MANIFEST ON A TRAIN']
The system needs to communicate the reason for update failure → The system should generate the error message 'WB UPDATE NOT APPLIED MANIFEST ON A TRAIN'
[Set Status to MANUAL]
The broker is invalid or transmission is not enabled → The manifest status is set to MANUAL
[Block Update - On Train]
The manifest is already assigned to a train (CDN-CUS-NORTH-TRAIN-ID is not empty) → The update is blocked and an error message 'CHANGE NOT APPLIED - MANIFEST ON TRAIN' is generated
[Block Update - Cargo Arrived]
The cargo has arrived (ARRIVAL-IND is populated) → The update is blocked and an error message 'CHANGE NOT APPLIED - CARGO ARRIVED' is generated
[Check Manifest Status]
The system checks manifest transmission eligibility → The manifest is eligible for transmission if status is not DELETED, DELPEND, REJECT, RELEASE, CSA-DLV, or DLACTIV, otherwise transmission is blocked
[Carrier Index Valid?]
The system validates carrier eligibility for transmission → The carrier is valid for transmission if carrier index is not equal to 999, otherwise transmission is blocked for invalid carrier
[Manifest Complete?]
The system validates manifest completeness → Manifest is complete if broker information is present, all required fields are populated, and no validation errors exist, otherwise transmission is blocked for incomplete manifest
[Create Segment 54 - Error Tracking & Data Origin]
Segment 54 creation is initiated → Segment 54 is populated with error message numbers and data origin classification
[Assign CCN Keys to All Segments]
CCN key assignment is performed → All segments are assigned the same CCN as their primary key for data consistency
[Set Error Message Numbers]
Error message assignment is performed → Appropriate error message numbers are assigned to segment 54 for error tracking
[Validate Segment Completeness]
Segment completeness validation is performed → All segments are verified to contain required data and pass validation checks
[Handle Segment Creation Errors]
Error handling is initiated → Errors are logged, appropriate error messages are generated, and corrective actions are taken
[Assign Record Type to Segment 54 Error Messages]
The system processes the segment for database storage → Record type '54' is assigned to the error messages segment and stored in GCSCCS54 database table
[Validate Key Assignment]
The system validates the key assignments → All segments must have valid CCN keys and appropriate record type identifiers before proceeding to database storage
[Create Error Message Segment 54]
The system creates an error message segment → A new segment is created with record type set to 54
[Store Combined Error Numbers in Segment]
The system stores the error information in the segment → All combined error numbers are stored in the error message segment data area
[Validate Transmission Eligibility]
The system performs transmission eligibility validation → The manifest is validated against transmission requirements and eligibility criteria
[Status = DELETED or DELPEND or REJECT?]
The manifest status is DELETED or DELPEND or REJECT → Set transmission eligibility to NO and block transmission with reason 'Status Not Eligible for Transmission'
[Status = RELEASE or CSA-DLV or DLACTIV?]
The manifest status is RELEASE or CSA-DLV or DLACTIV → Set transmission eligibility to NO and block transmission with reason 'Status Not Eligible for Transmission'
[Carrier Index = 999?]
The carrier index equals 999 → Set transmission eligibility to NO and block transmission with reason 'Invalid Carrier Index'
[Generate Pre-Emanifest Status Error]
The system generates a pre-emanifest status error → An error message is created indicating the specific validation failure and the processing returns to customs transmission with error status
[Validate Delivery Requirements]
The system validates the delivery requirements against system capabilities → The delivery requirements validation status is determined
[Validate Delivery Schedule]
The system validates delivery timing requirements → Check broker's delivery schedule preferences (DEFAULT, IMMEDIATE, ARRIVAL-DELIVERY) and validate against business rules
[Generate Duplicate Error]
The system processes the duplicate validation failure → The system generates appropriate duplicate error message and continues with call letters processing
[Cargo Report Found?]
The system checks if a cargo report exists for this cargo control number → If no cargo report is found, generate error message and terminate validation process, otherwise continue with duplicate check
[Generate Error Message]
The system encounters validation errors → Appropriate error message is generated describing the validation failure
[Set Error Flags]
The system processes the error condition → Error flags are set to indicate validation failure and prevent further processing
[Error Message Retrieval - Retrieve error message text from message tables for validation error reporting]
The system needs to retrieve error message text for display → The system should lookup the error message in the MS table using the error number and retrieve the English text
[Clear Message Segment Handle Not Found]
The message lookup fails to find a matching record → The system should clear the message segment and handle the not found condition appropriately
[Lookup Error Message in MS Table]
An error message lookup is requested → The system should search the MS table using the error number to locate the corresponding message record

Detailed EDI User Stories

Module: GCCCANRL 1 Consolidated Epic Story

Module: GCCCBOL 1 Consolidated Epic Story

Module: GCCCCADD 1 Consolidated Epic Story

Module: GCCCCARR 1 Consolidated Epic Story

Module: GCCCCREL 1 Consolidated Epic Story

Module: GCX122A 1 Consolidated Epic Story

Module: EBCLGIO2 1 Consolidated Epic Story

Module: GCCCCIO2 1 Consolidated Epic Story

Module: GCCDESC 1 Consolidated Epic Story

Module: GCCDUPCA 1 Consolidated Epic Story

Module: GCCPERM 1 Consolidated Epic Story

Module: GCX011R 1 Consolidated Epic Story