Detailed EDI User Stories

As an EDI Gateway Service,
I want to orchestrate and execute all GCCADDCD 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 Root Segment]
Root segment structure needs initialization → The EMTZ-ROOT-SEGMENT should be initialized to default state
[Initialize FWCARGET Parameters]
The system initializes FWCARGET parameters → All search criteria are set to include all waybill types except 98-99, all status types, exclude EDI incomplete records, include temporary waybills, exclude corrector waybills, return lead waybills, and use latest waybill date
[Initialize GCSCCRT Segment]
The retrieve next cargo process begins → The GCSCCRT cargo record segment is initialized to clear any previous data
[Initialize GCX101 Input Structure]
The message structure is being set up → The GCX101 input structure for the current index must be initialized to clear any previous data
[Initialize GCX101 Input Structure]
Message preparation begins → The GCX101 input structure for the current index is initialized to clear any existing data
[Initialize Message Input Structure]
The system initializes the message input structure → The system clears all fields in the message input structure for the current message index
[Initialize GCX101 Input Structure]
The message structure needs to be prepared → The GCX101 input structure for the current index is initialized to clear any existing data
[Initialize GCX101 Input Structure]
The system prepares the message structure → The GCX101 input structure is initialized to clear any previous data
[Call CIMS to Initialize Message]
The system needs to establish communication with customs → The system calls CIMS with CHNG function and ALT-PCB to initialize the message channel
[Initialize Message Structure]
The message processing system has been initialized → The WRITMSGL utility must be called with the message code, message content, message length, and module name to transmit the message to external customs systems
[Initialize Return Status Flag]
The system prepares for MERLIN communication → The EMI return status flag is initialized to clear any previous status

Core Acceptance Criteria

[8:Build Report Detail Lines]
Waybill is not found:
no cargo is found
detour manifest is required but not found
→ Build report with appropriate detail and message lines
[19:Retrieve Container from Flat Car]
Container is not found → Use root key to retrieve flat car container relationship, then retrieve container equipment, otherwise retrieve container equipment directly. If flat car relationship exists without container equipment, generate system error. If no flat car relationship exists, set message eleven and increment report index
[21:Finalize Report Processing]
No errors exist in report AND spawn processing is required → Process all pre-spawn entries and set error count to spawn count, otherwise when errors exist AND spawn processing is required, convert message twenty-eight to message nineteen and increment error count
[22:Spawn Customs Messages]
Spawn processing is executed → Move input record to customs message, call customs interface system, write message to customs queue, and purge customs interface
[24:Send Report to Customs]
Report transmission is initiated → Set customs user codes, set destination filename to 'REQUEST', populate subject with user ID and train information and timestamp, call email send service with report table, and purge interface system
[25:Determine Return Status]
Information message count is greater than zero → Set status to no waybill, otherwise when error message count is greater than zero, set status to errors and send report to customs, otherwise set status to OK and return report table
[Call FWCARGET Module for Car Data]
The system invokes FWCARGET module with parameters set to include all types except 98-99, all statuses, exclude EDI incomplete, include temporary waybills, exclude corrector waybills, return lead waybills, and get latest waybill date → The module returns waybill information in SHIPROOT segment for the specified car
[Retrieve Waybill by Root Key]
The system calls FWCWBIO service with SHIPROOT segment type, equal operator, and container equipment key → The waybill information is retrieved and stored in SHIPROOT segment
[Check for Multiple Waybill Versions]
The system checks if there are multiple waybill versions by evaluating haulage right carrier, EDI completion status, and feedback key → Continue processing until a valid waybill is found or no more versions exist
[More Waybill Versions?]
If CARGET-ERROR or CARGET-NOT-FOUND is true, or if HAULAGE-RIGHT-CARRIER is spaces, or if EDI-COMP-418-RELEASE equals 'Y', or if CARGET-FWBX-KEY-FEEDBACK matches previous feedback key → Stop processing if any termination condition is met, otherwise continue with previous status waybill date and update feedback key
[Select Latest Valid Waybill]
The system processes each version and finds one with valid haulage right carrier, completed EDI release, and unique feedback key → Set the processing flag to previous status waybill date and store the feedback key for comparison
[Set Previous Status Date]
The system prepares for the next search iteration → Previous status waybill date flag is set and the current FWBX key feedback is stored for duplicate detection
[Set Search Parameters for All Waybill Types]
The system initializes waybill search parameters → Search parameters are set to include all waybill types except 98-99, exclude EDI incomplete waybills, include temporary waybills, exclude corrector waybills, include returned lead waybills, and search for latest waybill date
[Same as Previous Version?]
The system compares the current waybill feedback key with the previous version → If the feedback keys match, mark as not found and stop processing, otherwise continue to search previous versions
[Set to Search Previous Version]
The system needs to search for previous waybill versions → Search parameters are updated to previous status waybill date and feedback key is stored for comparison
[Accept Current Waybill Version]
The system completes waybill validation → The current waybill version is accepted and version checking process ends
[Call Z320-GN-CCRT-SEG to Get Next Cargo Record]
The system needs to get the next cargo record → The Z320-GN-CCRT-SEG routine is called to retrieve the next cargo record from the Canadian Customs Cargo Records database
[Generate Message 27: Detour Manifest Missing]
If error message generation conditions → Generate message 27 indicating detour manifest is missing AND include the detour CCN key in the error message
[Generate Message 28: Transit Code Mismatch - Return]
If Canadian border crossing transit code conditions → Generate message 28 indicating transit code mismatch AND prepare GCT1011E change message for border crossing processing
[Generate Message 28: Transit Code Mismatch - Outbound]
If Canadian border crossing transit code conditions → Generate message 28 indicating transit code mismatch AND prepare GCT1011E diversion message for border crossing processing
[Prepare GCT1011E Change Message]
The system prepares border crossing messages → Set spawn flag to true AND increment pre-spawn index AND initialize GCX101 input structure AND set security byte to high values AND move cargo CCN key to message AND set Canadian flag to true AND set change flag to true AND move train crossing name and port to message
[Prepare GCT1011E Diversion Message]
The system prepares border crossing messages → Set spawn flag to true AND increment pre-spawn index AND initialize GCX101 input structure AND set security byte to high values AND move cargo CCN key to message AND set Canadian flag to true AND set diversion flag to true AND move train crossing name and port to message
[Prepare GCT1011E Change Message for Customs]
Error message 28 is set for the mismatch → Prepare GCT1011E message with change flag, Canadian flag, CCN key, border name, and border code for customs processing
[Prepare GCT1011E Diversion Message for Customs]
Error message 28 is set for the mismatch → Prepare GCT1011E message with diversion flag, Canadian flag, CCN key, border name, and border code for customs processing
[Set GCX101 Spawned Flag to True]
The system begins preparing the GCT1011E change message → The GCX101 spawned flag must be set to true to enable message generation
[Increment Pre-Spawn Index Counter]
The message preparation process begins → The pre-spawn index counter must be incremented by 1 to track this message
[Set Security Byte to High Values]
Security settings are being configured → The security byte must be set to high values to indicate maximum security level
[Move CCN Key to Message]
The change message is being populated → The cargo's CCN key must be moved to the message CCN field
[Set Canadian Flag to True]
Message classification is being set → The Canadian flag must be set to true to identify this as a Canadian border crossing message
[Set Change Message Type Flag]
Message type classification is being set → The change flag must be set to true to identify this as a change message type
[Move Train Crossing Name to Border Name]
Location details are being populated → The train crossing name must be moved to the border name field in the message
[Move Train Crossing Port to Border Code]
Port identification is being populated → The train crossing port code must be moved to the border code field in the message
[Set GCX101 Spawned Flag to True]
The diversion message preparation process begins → The GCX101 spawned flag is set to true to indicate message processing has started
[Increment Pre-Spawn Index Counter]
The message preparation process starts → The pre-spawn index counter is incremented by 1 to track the new message
[Set Security Byte to High Values]
Security settings are configured → The security byte in the GCX101 input structure is set to high values for maximum security clearance
[Move CCN Key to Message]
The diversion message is being populated → The CCN key from the cargo record is moved to the GCX101 CCN field in the message
[Set Canadian Flag to True]
Message routing flags are set → The Canadian flag in the GCX101 input structure is set to true
[Set Diversion Flag to True]
Message type classification is performed → The diversion flag in the GCX101 input structure is set to true
[Move Train Crossing Name to Border Name]
Border location information is populated in the message → The train crossing name is moved to the border name field in the GCX101 input structure
[Move Train Crossing Port to Border Code]
Border processing information is populated in the message → The train crossing port code is moved to the border code field in the GCX101 input structure
[Waybill Found?]
System checks the waybill indicator status → If waybill found, set waybill found status, otherwise proceed to generate no waybill messages
[Equipment is Container?]
System checks if the equipment is a container → If container, generate container-specific message, otherwise generate car-specific message
[Generate Message: No Waybill for Container]
System generates error messages for missing waybill → System sets message type 10 indicating no waybill found for container
[Generate Message: No Waybill for Car]
System generates error messages for missing waybill → System sets message type 12 indicating no waybill found for car
[Generate Message: No Cargo Found for Loaded Equipment]
System validates cargo consistency for loaded equipment → System sets message type 15 with waybill root key and date information
[Set Message Seventeen - Cargo Already Attached]
The system processes the train attachment validation → Set message seventeen flag to true for the current report index to indicate cargo is already attached to another train
[Prepare GCT1011E Change Message]
Error message 28 is triggered → Prepare GCT1011E message with change type, Canadian flag, CCN, border name and port for customs processing
[Prepare GCT1011E Diversion Message]
Error message 28 is triggered → Prepare GCT1011E message with diversion type, Canadian flag, CCN, border name and port for customs processing
[Manifest TO Transit Code ≠ Train Crossing Port?]
The system compares the manifest TO transit code with the train crossing port code → The system prepares a change message if the codes are different, otherwise checks outbound manifest codes
[Manifest FROM Transit Code ≠ Train Crossing Port?]
The system compares the manifest FROM transit code with the train crossing port code → The system prepares a diversion message if the codes are different, otherwise completes processing without border crossing messages
[Build Change Message for GCT1011E]
The system builds a GCT1011E change message → The system sets spawned flag, increments counter, initializes message structure, sets security level, copies CCN key, sets Canadian flag, sets change message type, and copies border crossing details
[Build Diversion Message for GCT1011E]
The system builds a GCT1011E diversion message → The system sets spawned flag, increments counter, initializes message structure, sets security level, copies CCN key, sets Canadian flag, sets diversion message type, and copies border crossing details
[Set Message as Spawned]
The system begins message preparation → The system sets the spawned status flag to indicate messages are being prepared
[Set Security Level to High Values]
The system sets the security level for the message → The system assigns high values to the security byte field to indicate maximum security clearance required
[Copy CCN Key to Message]
The system copies cargo identification data → The system moves the CCN key from the cargo record to the message CCN field
[Set Canadian Flag]
The system sets processing flags for the message → The system sets the Canadian flag to indicate this message requires Canadian customs processing
[Set Change Message Type]
The system sets the message type for change processing → The system sets the change flag to indicate this is a destination change message
[Set Diversion Message Type]
The system sets the message type for diversion processing → The system sets the diversion flag to indicate this is an origin diversion message
[Copy Border Crossing Name]
The system copies border crossing identification data → The system moves the train crossing name to the message border name field
[Copy Border Crossing Port Code]
The system completes location identification data → The system moves the train crossing port code to the message border code field
[Increment Message Counter]
The system finalizes message preparation → The system increments the pre-spawn message counter by 1 to track the total number of messages prepared
[Set GCX101 Spawned Flag to True]
The system begins building the change message → The GCX101 spawned flag is set to true to indicate message processing is active
[Increment Pre-Spawn Index Counter]
The message building process starts → The pre-spawn index counter is incremented by 1 to track the new message
[Set Security Byte to High Values]
Security level needs to be assigned to the message → The security byte is set to high values to indicate maximum security level
[Move CCN Key to Message]
The cargo identification needs to be included in the message → The CCN key from the cargo record is moved to the GCX101 message structure
[Set Canadian Flag to True]
The message destination needs to be specified → The Canadian flag in the message is set to true
[Set Change Message Type Flag]
The message type needs to be specified → The change flag in the GCX101 message is set to true
[Move Train Crossing Name to Border Name]
Location identification needs to be included in the message → The train crossing name is moved to the border name field in the message
[Move Train Crossing Port to Border Code]
Port identification needs to be included in the message → The train crossing port code is moved to the border code field in the message
[Set GCX101 Spawned Flag to True]
The system begins building a diversion message → The GCX101 spawned flag is set to true to indicate message processing is active
[Increment Pre-Spawn Index Counter]
The system needs to track multiple diversion messages → The pre-spawn index counter is incremented by 1
[Set Security Byte to High Values]
Security level needs to be assigned to the message → The security byte is set to high values to ensure maximum security clearance
[Move CCN Key to Message]
The diversion message is being populated with cargo information → The CCN key is moved to the diversion message structure
[Set Message Type to Canadian]
The message type needs to be specified → The message type is set to Canadian to indicate Canadian border processing
[Set Message Type to Diversion]
The specific message category is being assigned → The message type is set to diversion to indicate route change processing
[Move Train Crossing Name to Border Name]
The border name field needs to be populated → The train crossing name is moved to the border name field in the message
[Move Train Crossing Port to Border Code]
The border code field needs to be populated → The train crossing port code is moved to the border code field in the message
[Retrieve FWSWRWR Segment]
The system queries the FWSWRWR database segment → Retrieve the waybill relationship record that links flat cars to containers
[Get FWSWREQ Segment for Container Details]
The system queries the FWSWREQ database segment → Retrieve the container equipment record containing detailed container information
[Set Container Not Found Message]
No container relationship is found for the given root key → Set message eleven indicating container relationship not found and add to report
[Is this a Message Line?]
The system checks if the line contains a message → The system identifies whether this is a message line requiring categorization
[Type 28 Message?]
The message type indicator equals 28 → The system routes this message for pre-spawn count processing instead of regular error count
[Add 1 to Pre-Spawn Count]
The system processes the special message type → The pre-spawn count is incremented by 1
[Warning Message?]
The system checks the message warning indicator → The system determines if this is a warning message requiring warning processing
[Informational Message?]
The system checks the message informational indicator → The system determines if this is an informational message requiring info processing
[Add 1 to Info Count]
The system processes the informational message → The information count is incremented by 1
[Request Message?]
The system checks if the message has a request indicator → The system determines if this message requires request error count processing
[Increment Report Index]
The system advances to the next report line → The report index is incremented by 1
[Set Maximum Reached Message]
The system needs to indicate capacity exceeded → Message type 9 is set for the current report line
[Any Messages to Spawn?]
The system checks for messages requiring spawn processing → If pre-spawn messages exist, process each spawn message, otherwise complete report processing
[Process Each Spawn Message]
The system processes spawn messages → Each pre-spawn input is moved to the processing structure and spawn processing is performed
[Send GCT1011E Message to Customs]
The system processes the spawn message → The GCT1011E message is sent to customs via CIMS and WRITMSGL calls
[Any Messages to Spawn?]
The system checks for spawn processing requirements → If pre-spawn messages exist, review each report line for message type conversion, otherwise complete report processing
[Review Each Report Line]
The system reviews report lines → Each report line from 1 to last line is examined for message type indicators
[Is Message Type 28?]
The system checks the message type indicator → If message type is 28, convert to message type 19 and increment error count, otherwise continue to next line
[Convert to Message Type 19]
The system processes the message conversion → Message type 28 is converted to message type 19
[Check Report Status]
The system checks if there are any errors in the report → The system determines whether to proceed with spawning customs messages or convert error messages
[Pre-spawn Messages Exist?]
The system checks if PRE-NO-SPAWN condition is false → If pre-spawn messages exist, process them for customs notification, otherwise complete spawn process
[Loop Through Pre-spawn Messages]
The system processes messages from index 1 to PRE-IDX → Each message in the queue is processed sequentially for customs notification
[Prepare GCT1011E Message Structure]
The system moves WS-GCX101-INPUT data to GCX101-INPUT structure → The message structure is prepared for customs system processing
[Send Message to Customs via CIMS]
The system calls CIMS with CHNG function and ALT-PCB → The message is sent to the customs system for processing
[Write Message Log Entry]
The system calls WRITMSGL with message details → The message transmission is logged with message code, content, length and module name
[Purge Message Queue]
The system calls CIMS with PURG function → The message queue is purged to prepare for next message
[More Messages to Send?]
The system checks if SPN-IDX is less than or equal to PRE-IDX → If more messages exist, continue processing, otherwise proceed to update error count
[Prepare GCT1011E Message Structure]
The system needs to send a message to customs → The system moves the prepared input data to the GCT1011E message structure
[Clear Accept Status]
The system prepares to initialize communication → The system clears the accept status to ensure clean communication channel
[Call WRITMSGL to Write Message]
The system needs to transmit the message to customs → The system calls WRITMSGL with message code, content, length and module name to write the message to customs queue
[Call CIMS to Purge Message Queue]
The message transmission is complete → The system calls CIMS with PURG function to purge the communication channel and clean up resources
[Move GCX101 Input Data to GCT1011E Message]
The system needs to notify customs of cargo status changes → The GCX101 input data must be moved to the GCT1011E message structure to prepare for customs transmission
[Clear Accept Status]
The message initialization process begins → The accept status field must be cleared to spaces to indicate a fresh transaction state
[Call CIMS with CHNG Function]
The message has been prepared and status cleared → The CIMS system must be called with CHNG function, communication control block, and alternate PCB to initiate message processing
[Message Ready for Processing]
The message transmission is complete → The CIMS system must be called with PURG function and alternate PCB to purge the message transaction and release system resources
[Move GCX101-INPUT to GCT1011E-MSG]
The system needs to format the message for transmission → The GCX101 input data should be moved to the GCT1011E message structure
[Clear Accept Status]
The system prepares to send the message → The accept status should be cleared to spaces to initialize communication state
[Call CIMS with CHNG Function]
The system initiates message processing → A CIMS change transaction should be started using the alternate PCB
[Call WRITMSGL to Write Message]
The system needs to transmit the message to customs → The WRITMSGL service should be called with message code, message text, message length, and module name
[Call CIMS with PURG Function]
The message processing is complete → A CIMS purge transaction should be executed to commit the message
[Are there messages to spawn?]
The system checks for available pre-spawn messages → The system determines whether to proceed with message conversion logic based on spawn message availability
[Loop through all report lines]
The system processes each report line sequentially → Each report line is evaluated for message type conversion requirements
[Convert message type 28 to message type 19 Warning]
The system performs error message conversion during error handling → The message type 28 is converted to message type 19 warning status
[Set MERLIN Message Parameters]
The system prepares MERLIN message parameters → The from user code is set to OM01247, to user code is set to OM01247, and destination filename is set to REQUEST
[Build Message Subject with Train and Timestamp]
The system builds the message subject → The subject includes ACF2 user ID, train number, year, month, day, hour, and minute from system timestamp
[Call MERLIN Messaging System]
The system establishes MERLIN connection → CCISCOM utility is called with CCCOM and ISCOM parameters to establish messaging connection
[Send Report Table via EMCSEND2]
The system transmits the report → EMCSEND2 utility is called with from user code, destination filename, to user code, copy user code, subject, keywords, report table, return status flag, segment numbers, and item type parameters
[Purge Message Queue]
The system completes MERLIN communication → ISCCCOM utility is called with ISCOM and CCCOM parameters, accept status is initialized, and CIMS is called with PURG function to purge the alternate PCB message queue
[System Abend - Send Failed]
The system detects transmission failure → The abend message is set to 'SEND TO MERLIN FAILED' and system abend procedure is performed
[Get Current User ID from System]
The system processes the message subject creation → The current ACF2 user ID is extracted from the system control block and assigned to the message subject
[Extract Train Number from Input]
The system builds the message subject → The train number is extracted from the input parameters and assigned to the message subject
[Extract Year Component]
The system processes the date components → The current year is extracted from the system control block and assigned to the message subject
[Extract Month Component]
The system processes the date components → The current month is extracted from the system control block and assigned to the message subject
[Extract Day Component]
The system processes the date components → The current day is extracted from the system control block and assigned to the message subject
[Extract Hour Component]
The system processes the time components → The current hour is extracted from the system control block and assigned to the message subject
[Extract Minute Component]
The system processes the time components → The current minute is extracted from the system control block and assigned to the message subject
[Combine Train and Timestamp into Subject]
The system creates the final message subject → All components are combined into the MERLIN-SUBJECT field for the customs notification message
[Extract Year from System Date]
Preparing to send a report to customs system → The year component from machine date is extracted and stored for message subject formatting
[Extract Month from System Date]
Preparing to send a report to customs system → The month component from machine date is extracted and stored for message subject formatting
[Extract Day from System Date]
Preparing to send a report to customs system → The day component from machine date is extracted and stored for message subject formatting
[Extract Hour from System Time]
Preparing to send a report to customs system → The hour component from machine time is extracted and stored for message subject formatting
[Extract Minutes from System Time]
Preparing to send a report to customs system → The minutes component from machine time is extracted and stored for message subject formatting
[Format Time Components for Message Subject]
Creating the complete message subject for customs notification → All components are formatted into the MERLIN-SUBJECT field for transmission to customs system
[Check Information Message Count]
The system checks if any informational messages were generated during processing → If informational message count is greater than zero, set return status to NO-WAYBILL and terminate processing
[Set Return Status to OK]
The system determines that processing completed without issues → Set return status to OK indicating successful processing

Structural Validations

[3:Retrieve Waybill Information]
Car ID formatting is successful → Use formatted car ID to retrieve shiproot car waybill, otherwise generate invalid car ID error message
[11:Generate Error Messages]
Detour manifest is required AND detour manifest is not found → Set message twenty-seven with detour CCN information
[11:Generate Error Messages]
Waybill is not found AND container is found → Set message ten, otherwise when waybill is not found AND container is not found, set message twelve
[11:Generate Error Messages]
Waybill is found AND no cargo is found AND container is not found AND equipment is not conveying car → Set message fifteen with root key and waybill date
[11:Generate Error Messages]
Cargo status is pending:
error
reject
deleted
→ Set message sixteen, otherwise when user security level is not 'S' AND cargo status is blank OR reject OR error, set message sixteen, otherwise when cargo is linehaul AND status is manual, set message sixteen
[11:Generate Error Messages]
Canadian customs north train ID is not spaces → Set message seventeen
[11:Generate Error Messages]
Cargo is in return transit status AND CCN key starts with '6105E' AND manifest to transport code does not equal train crossing port → Set message twenty-eight and Execute pre-spawn processing for change, otherwise when cargo is not in return transit status AND CCN key starts with '6105E' AND manifest from transport code does not equal train crossing port, set message twenty-eight and Execute pre-spawn processing for diversion
[11:Generate Error Messages]
Pre-spawn processing is initiated → Set spawn status to true, increment pre-index, initialize input record, set security byte to high values, populate CCN key, set Canadian flag, set diversion flag, and populate border name and code from train crossing information
[11:Generate Error Messages]
Pre-spawn processing is initiated → Set spawn status to true, increment pre-index, initialize input record, set security byte to high values, populate CCN key, set Canadian flag, set change flag, and populate border name and code from train crossing information
[23:Handle Error Conditions]
Spawn processing is required → For each report line with message type twenty-eight, convert to message nineteen and increment error count
[Retrieve Waybill for Current Equipment]
Car ID formatting is successful → Use formatted car ID for shiproot car retrieval, otherwise generate invalid car ID error message
[Generate Invalid Car ID Error Message]
The system needs to handle the validation failure → The system moves the error message 'ERR>>>> INVALID CAR ID' to the report line and performs report index addition
[Generate Invalid Car ID Error]
GCCARFM-RC-SUCCESS is not true → Generate error message 'ERR>>>> INVALID CAR ID' in the report line and increment report index
[Handle FWCARGET Error]
FWCARGET returns an error status → The system creates an error message containing FWCARGET parameters and terminates processing
[Check Haulage Right Carrier]
The system checks the haulage right carrier field → If haulage right carrier is empty (spaces), the waybill is accepted; otherwise, additional EDI validation is required
[Check EDI Completion Status]
The system checks the EDI completion status → If EDI completion release flag is 'Y', the waybill is accepted; otherwise, duplicate key validation is performed
[Check for Duplicate Key]
The system compares the current FWBX key feedback with the previously processed key → If the keys match, set waybill as not found to terminate processing; otherwise, continue with previous status date processing
[Exclude EDI Incomplete Records]
The system sets the EDI completeness criteria → Car search excludes records with incomplete EDI data
[EDI Complete Release = 'Y'?]
The system checks the EDI completion release flag → If EDI completion release equals 'Y', the waybill is accepted, otherwise version checking continues
[Generate Invalid Car ID Error Message]
The formatting operation does not return a success status → An error message 'ERR>>>> INVALID CAR ID' is generated and added to the report
[Handle Equipment Classification Error]
The system receives an unsuccessful response from the equipment classification service → The system should create an error message containing the service name and parameters, then Execute system termination procedures
[Generate GCCCARTP Failure Error]
The system processes the failure condition → An error message is constructed with failure details and interface parameters, and system termination is performed
[Generate Message 10: Container Without Waybill]
If waybill validation conditions → Generate message 10 indicating container exists without proper waybill documentation
[Generate Message 12: Car Without Waybill]
If waybill validation conditions → Generate message 12 indicating car exists without proper waybill documentation
[Generate Message 15: No Cargo for Loaded Equipment]
If cargo validation conditions → Generate message 15 indicating no cargo found for loaded equipment AND include the root key and waybill date in the error message
[Generate Message 16: Invalid Cargo Status]
If cargo status validation conditions → Generate message 16 indicating invalid cargo status prevents processing
[Generate Message 17: Cargo Already on Train]
If cargo train assignment conditions → Generate message 17 indicating cargo is already assigned to another train
[Check Status: Pending]
The cargo status is PENDING → Generate message sixteen indicating invalid cargo status
[Check Status: Error]
The cargo status is ERROR → Generate message sixteen indicating invalid cargo status
[Check Status: Reject]
The cargo status is REJECT → Generate message sixteen indicating invalid cargo status
[Check Status: Deleted]
The cargo status is DELETED → Generate message sixteen indicating invalid cargo status
[Check User Security Level]
The cargo status is BLANK or REJECT or ERROR → Generate message sixteen indicating invalid cargo status due to security restrictions
[Check Additional Status Conditions]
The cargo status is MANUAL → Generate message sixteen indicating invalid cargo status
[User Security Level = 'S'?]
The cargo status is BLANK, REJECT, or ERROR → The system should set error message MSG-SIXTEEN to deny access
[Is Cargo Already Attached to Another Train?]
The cargo has a Canadian Customs North Train ID that is not empty spaces → Set Message 17 indicating the cargo is already attached to another train
[Is Cargo Linehaul Type? AND Is Cargo Status Manual?]
The cargo is linehaul type AND the cargo status is manual → Set Message 16 indicating linehaul manual status error
[Manifest TO Transit Code ≠ Train Crossing Port?]
The system compares manifest TO transit code with train crossing port → If manifest TO transit code does not equal train crossing port, set error message 28 and prepare change message for customs
[Manifest FROM Transit Code ≠ Train Crossing Port?]
The system compares manifest FROM transit code with train crossing port → If manifest FROM transit code does not equal train crossing port, set error message 28 and prepare diversion message for customs
[Set Error Message 28 - Transit Code Mismatch]
Either manifest TO or FROM transit code does not match train crossing port → Set message type 28 indicating transit code mismatch error
[Equipment has Cargo Records?]
System checks for associated cargo records → If no cargo records found, generate no cargo message, otherwise continue processing
[Generate Error: Invalid Car ID Format]
System processes the formatting failure → System generates error message 'ERR>>>> INVALID CAR ID' and adds to report
[Status = Pending?]
The cargo status is checked and found to be pending → The system sets error message MSG-SIXTEEN to indicate invalid cargo status
[Status = Error?]
The cargo status is checked and found to be error → The system sets error message MSG-SIXTEEN to indicate invalid cargo status
[Status = Reject?]
The cargo status is checked and found to be reject → The system sets error message MSG-SIXTEEN to indicate invalid cargo status
[Status = Deleted?]
The cargo status is checked and found to be deleted → The system sets error message MSG-SIXTEEN to indicate invalid cargo status
[User Security Level ≠ 'S'?]
The cargo status is blank, reject, or error → The system sets error message MSG-SIXTEEN to indicate invalid cargo status for the user's security level
[Cargo Status Valid - Continue Processing]
The cargo status is manual → The system sets error message MSG-SIXTEEN to indicate invalid cargo status
[Check CDN CUS North Train ID Field]
The system checks the Canadian Customs North Train ID field in the cargo record → If the field is not empty (contains spaces), set message seventeen indicating the cargo is already attached to another train
[Check for linehaul manual manifest status and generate errors if found]
The cargo is found AND the shipment is classified as linehaul type AND the cargo status is set to manual → The system generates error message MSG-SIXTEEN and sets an error flag to indicate the shipment requires manual intervention
[Check Return Status Transit Code]
The manifest TO transit code is compared with the train crossing port → If codes do not match, trigger error message 28 and prepare change message; if codes match, continue normal processing
[Check Non-Return Status Transit Code]
The manifest FROM transit code is compared with the train crossing port → If codes do not match, trigger error message 28 and prepare diversion message; if codes match, continue normal processing
[Check Cargo Status]
The system checks if cargo data has been found and loaded → The system proceeds to transit status validation only if cargo is found, otherwise skips border crossing message preparation
[CCN Key = '6105E'?]
The system checks if the CCN key starts with '6105E' → The system proceeds with Canadian border crossing validation if CCN starts with '6105E', otherwise skips border crossing message preparation
[Container Relationship Found?]
The system checks the query results → If container relationship is found, proceed to retrieve container equipment data, otherwise set container not found message
[Generate Missing Container Relation Error]
No container relation record is found in FWSWRWR database → Set message eleven error flag and add to report index
[Generate System Error - Missing Equipment]
Container equipment details are not found in FWSWREQ database → Generate abend message indicating FWSWRWR segment exists without FWSWREQ segment and Execute system abend
[Error Message?]
The system checks the message error indicator → The system determines if this is an error message requiring error processing
[Add 1 to Error Count]
The system processes the regular error message → The error count is incremented by 1
[Add 1 to Error Count]
The system processes the warning message → The error count is incremented by 1
[Add 1 to Request Error Count]
The system processes the request message → The request error count is incremented by 1
[Add 1 to Request Error Count]
The system processes the capacity exceeded condition → The request error count is incremented by 1
[Any Errors in Report?]
The system checks for errors in the report → If no errors exist, proceed to spawn message processing, otherwise proceed to error handling path
[Set Error Count from Spawn Count]
All spawn messages are completed → The pre-spawn count is moved to the report error count
[Increment Error Count]
The conversion is completed → The report error count is incremented by 1
[Any Errors Found?]
If RPT-NO-ERROR condition is true → If no errors exist, proceed with customs message spawning, otherwise convert error messages to warnings
[Update Error Count with Spawn Count]
The system completes the spawn processing loop → The PRE-SPAWN-CNT is moved to RPT-ERROR-CNT to reflect spawned message count
[Convert Error Messages to Warnings]
The system finds message type 28 in the report lines → Message type 28 is converted to message type 19 and error count is incremented
[Is message type 28 Transit Code Error?]
If the message type indicator for the current report line → The system determines if the message is type 28 requiring conversion to a warning message
[Increment error count by 1]
The system updates error tracking counters → The total error count is incremented by one to reflect the converted message
[Message Send Successful?]
The system checks transmission status → If EMI return status is not successful, the system prepares for abend with 'SEND TO MERLIN FAILED' message
[Check Error Message Count]
The system checks if any error messages were generated during processing → If error message count is greater than zero, set return status to ERRORS, otherwise proceed to success processing
[Set Return Status to ERRORS]
The system determines that errors occurred during processing → Set return status to ERRORS and invoke customs reporting process to send error details to external customs system

As an EDI Gateway Service,
I want to orchestrate and execute all GCCE358 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 Root Segment Structure]
The root segment creation process begins → The A9RT transmission segment structure is initialized to empty values
[Initialize Root Segment with Transmission Number and Transaction Set '358']
The system initializes the root segment → The transmission number is set from machine time, transaction set is set to '358', and the root segment is prepared for insertion
[Initialize M10 Segment Structure]
M10 manifest processing begins → The M10 segment structure is initialized to clear any previous data
[Initialize P4 Segment Structure]
P4 segment processing begins → The P4 segment structure is initialized and the identifier is set to 'P4'
[Initialize VID Segment Structure]
The system starts processing equipment data → The VID segment structure is initialized and the identifier is set to 'VID'
[Initialize MBL Segment]
The system begins MBL processing for the equipment → A new MBL segment structure is initialized and the MBL identifier is set to 'MBL'
[Initialize MBL Segment Structure]
The system begins MBL segment creation → The MBL segment structure is initialized to clear any previous data
[Initialize Security Parameters]
Security parameters are being configured → The system sets the security byte to HIGH-VALUES for secure transmission
[Initialize Message as Empty]
No specific message content is required → The system initializes the message field to spaces

Core Acceptance Criteria

[2:Generate Transmission Number]
Generating transmission number → Use prefix 106 for FOREGROUND mode or prefix 110 for BACKGROUND mode, combined with machine time
[10:Create VID Equipment Segment]
Creating VID equipment segment → Populate VID segment with equipment type, initial, processed equipment number, and determined load status
[11:Process Bill of Lading Records]
Processing bill of lading records → Extract SCAC and BOL/Waybill information from equipment data for MBL segment creation
[14:Create MBL Bill Segment]
Creating MBL bill segment → Populate MBL segment with SCAC, BOL/Waybill number, and determined response code
[15:Start EDI Send Function]
Starting EDI send function → Invoke EDI send function with transmission number and high-values security setting
[16:Start Log Update Function]
Starting log update function → If FOREGROUND mode use foreground action code and transaction name, if BACKGROUND mode use background action code and transaction name, include user ID, current date and time
[Check Processing Mode]
The system checks the processing mode indicator → If the mode is foreground, set transmission prefix to 106, otherwise if the mode is background, set transmission prefix to 110
[Get Current Machine Time]
The system needs to create a transmission number → Retrieve the current machine time and use it as the base transmission number
[Combine Prefix + Machine Time to Create Transmission Number]
The system creates the transmission number → Combine the prefix with the machine time to form the complete transmission number
[Set Transmission Number from Generated Value]
Creating the EDI root segment → The transmission number is assigned to the A9RT transmission number field
[Set Transaction Set to '358']
Setting the transaction set identifier → The transaction set code is set to '358'
[Attempt to Insert Root Segment into EDI Database]
Inserting the segment into the EDI database → The system attempts to insert the A9RT segment using database insert operation
[Increment Transmission Number by 1]
Resolving the transmission number collision → The transmission number is incremented by 1 and assigned to the root segment
[Root Segment Successfully Created]
Attempting to insert the root segment again → The system continues the insertion retry loop until the status code is blank indicating success
[Attempt to Insert Root Segment into EDI Database]
The system attempts to insert the root segment into the EDI database → The insertion is attempted and the result status is captured for evaluation
[Insert Successful?]
The insertion fails due to duplicate transmission number → The system detects the failure and initiates the duplicate resolution process
[Increment Transmission Number by 1]
The system needs to resolve the conflict → The transmission number is incremented by 1 and the insertion process is retried
[Set M10 Identifier]
The segment identifier needs to be set → The identifier is set to 'M10'
[Set SCAC Code to 'CPRS']
The SCAC code needs to be assigned → The SCAC code is set to 'CPRS' for Canadian Pacific Railway
[Set Transport Type Code to 'R' for Rail]
The transport type code needs to be assigned → The transport type code is set to 'R' to indicate rail transport
[Set Country Code to 'CA' for Canada]
The country code needs to be assigned → The country code is set to 'CA' for Canada
[Set Vessel Name from Train ID]
The vessel name needs to be assigned → The vessel name is set to the customer train ID from the train list
[Set Voyage Number from Train Creation Date]
The voyage number needs to be assigned → The voyage number is set to the train creation date from the train list
[Set Quantity from Bill of Lading Count]
The quantity needs to be assigned → The quantity is set to the total count of bills of lading
[Set Manifest Type Code to 'S' for Standard]
The manifest type code needs to be assigned → The manifest type code is set to 'S' for standard manifest
[Set Conditional Response Code to 'Y']
The conditional response code needs to be assigned → The conditional response code is set to 'Y' to indicate response is required
[Set Record Type to 'TRAIN']
The record type needs to be assigned → The record type is set to 'TRAIN'
[Set Record Number from Train ID]
The record number needs to be assigned → The record number is set to the customer train ID from the train list
[Insert M10 Segment into EDI Database]
The segment needs to be stored for EDI transmission → The M10 segment is inserted into the EDI database with proper sequence numbering
[Set Departure Location ID from Train Data]
P4 segment is being populated with location details → The departure location ID is set from the train's origin service center
[Extract Estimated Departure Date]
P4 segment requires departure date information → The estimated departure date is extracted and moved to temporary date field for processing
[Set Quantity from Bill of Lading Count]
P4 segment quantity field needs to be populated → The quantity is set to the bill of lading count value
[Set Estimated Time of Arrival]
P4 segment time field needs to be populated → The time field is set from the train's estimated time of arrival
[Set FIRMS Code from Train Data]
P4 segment ID code field needs to be populated → The ID code field is set from the train's FIRMS code
[Insert P4 Segment into EDI Database]
P4 segment is ready for EDI transmission → The P4 segment is inserted into the EDI transmission database with proper sequence numbering
[Equipment ID Different from Last Processed?]
The system compares the current equipment ID with the last processed equipment ID → If the equipment IDs are different, the system should proceed to create a new VID segment, otherwise skip VID creation for this equipment
[Set Equipment Description Code]
The equipment description code needs to be populated → The system should copy the equipment type from the train list equipment data to the VID equipment description code field
[Set Equipment Initial]
The equipment initial needs to be populated → The system should copy the equipment initial from the train list equipment data to the VID equipment initial field
[Is Equipment CP or Has No Car Number?]
The system needs to determine the equipment number for the VID segment → If the US-CCN-KEY starts with 'CPRS' OR the cargo car number is spaces, then use the train list equipment number, otherwise use the cargo database car number
[Insert VID Segment to EDI Data]
The segment needs to be added to the EDI transmission → The system should insert the VID segment into the transmission data with an incremented sequence number
[Status Code = 'H'?]
The equipment load/empty status code is 'H' (Hold) → The status code should be converted to 'E' (Empty) for the EDI transmission
[Set Database Access Parameters]
The system prepares to access the cargo database → The system sets segment type to GCSUSRT, function type to GU (Get Unique), and index usage to not used
[Set Equipment Description Code from Train List]
The system processes VID segment creation → The equipment description code is set from the train list VID01 equipment type field
[Set Equipment Initial from Train List]
The system processes VID segment creation → The equipment initial is set from the train list VID02 equipment initial field
[Is Equipment CP-owned or No Foreign Car Number?]
The system needs to determine the equipment number source → If the US-CCN-KEY starts with 'CPRS' OR the 350-CAR-NUMBER is spaces, use equipment number from train list, otherwise use the foreign car number from cargo database
[Use Equipment Number from Train List]
The system sets the equipment number in VID segment → The equipment number is set from the train list VID03 equipment number field
[Use Foreign Car Number from Cargo Database]
The system sets the equipment number in VID segment → The equipment number is set from the cargo database 350-CAR-NUMBER field
[Insert VID Segment into EDI Data]
The system completes VID segment creation → The VID segment is moved to transmission data and inserted into the EDI data structure
[Extract Carrier SCAC Code from Equipment]
Processing MBL segment creation → The carrier SCAC code is extracted from the equipment's MBL01-M1309-US-CCN-SCAC field and assigned to MBL-01-SCAC
[Extract Bill of Lading Number from Equipment]
Processing MBL segment creation → The bill of lading number is extracted from the equipment's MBL02-M1304-US-CCN-ID field and assigned to MBL-02-BOL-WAYBILL
[Insert MBL Segment into EDI Data]
All MBL processing is complete → The MBL segment is moved to the transmission data structure and inserted into the EDI data stream
[Retrieve SS Segment Data]
The system processes the lookup result → The SS segment data should be moved from the table buffer to the working storage area
[Automated Carrier Flag = 'Y'?]
The system checks the automated carrier flag → If the automated carrier flag equals 'Y', the carrier supports automation; otherwise, it does not
[Clear SS Segment Data]
The system handles the lookup failure → The SS segment data area should be cleared to spaces to indicate no data available
[Set MBL Identifier to 'MBL']
The segment identifier needs to be set → The identifier is set to 'MBL' to indicate this is a Master Bill of Lading segment
[Extract SCAC Code from Equipment Record]
The SCAC code is needed for the MBL segment → The SCAC code is extracted from the equipment record's CCN SCAC field
[Extract Bill of Lading Number from Equipment Record]
The bill of lading number is needed for the MBL segment → The bill of lading number is extracted from the equipment record's CCN ID field
[Is SCAC Code 'CPRS'?]
The SCAC code equals 'CPRS' → The response code is set to 'Y' indicating automated processing for CP Rail
[Look up SCAC in SS Table for Port]
The SCAC code is not 'CPRS' → The system performs a table lookup using table ID 'SS', the SCAC code, and the origin port to determine carrier automation status
[Is Equipment Empty with Bill Type 23?]
The equipment load/empty status is 'E' AND the CCN key is not spaces AND the bill type code is 23 → The response code is overridden to 'Y' for special ER processing requirements
[Insert MBL Segment into EDI Data]
The segment is ready for transmission → The MBL segment is inserted into the EDI transmission data structure
[Set EDI Send Function Name]
The EDI send process is started → The system sets the EDI send function name flag to true to identify the correct processing function
[Set Security Authorization]
Security authorization is being configured → The system sets the security byte to high-values to enforce maximum security protection
[Add Transmission Number to Message]
The EDI message is being prepared → The system adds the transmission number to the message structure for identification
[Prepare EDI Message for Transmission]
The message preparation process is executed → The system moves the complete input structure to the message output text for transmission
[Send Message to EDI Queue]
The message is being sent to the EDI queue → The system sets the EDI send function length flag to ensure proper message sizing
[Send Message to EDI Queue]
The message insertion process is initiated → The system performs the insert purge message operation to queue the message for transmission
[Set Log Update Function Name]
The log update process is initiated → The system sets the function name to LOG-UPDT-FUNC-NAME to identify the logging service
[Set Train ID from Train List]
Train identification is required for the log → The system sets the train identifier using the US customer train ID from the train list
[Processing Mode?]
The processing mode is background → The system uses the background action code
[Set Foreground Action Code and Transaction Name / Set Background Action Code and Transaction Name]
The processing mode is background → The system uses the background transaction name
[Set User ID from System]
User identification is required for audit purposes → The system captures and records the ACF2 user ID from the system
[Set Current Date from System]
The current date needs to be recorded → The system concatenates the machine century and machine date to create a complete date stamp
[Set Current Time from System]
The current time needs to be recorded → The system records the machine time from the system

Structural Validations

[1:Validate Processing Mode]
The processing mode is checked → Processing continues only if mode is FOREGROUND or BACKGROUND, otherwise sets wrong mode indicator
[3:Insert EDI Root Segment]
Attempting to insert EDI root segment → If transmission number already exists, increment by 1 and retry until unique number is found
[Transmission Number Generated]
The system attempts to create a transmission record → If the transmission number already exists, increment the number by 1 and retry until a unique number is found
[Insert Successful?]
The database insert operation completes → If the status code is not blank, the insertion failed due to duplicate transmission number
[Root Segment Successfully Inserted]
The insertion is successful without conflicts → The root segment is successfully stored in the EDI database and the process continues

As an EDI Gateway Service,
I want to orchestrate and execute all GCCS309 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 M10 Segment]
The system begins M10 header creation → The M10 segment is cleared and identifier is set to 'M10'
[Initialize N9 Table and Counter]
The initialization process begins → The N9 table counter is set to 1 and the N9 table is cleared
[Initialize M10 Segment]
The system begins M10 segment creation → The segment is cleared, sequence number is incremented, M10 identifier is set, and segment structure is prepared for data population
[Initialize P4 Segment]
The P4 segment needs to be prepared for data population → The dependent segment should be cleared, sequence number should be incremented by 1, and P4 segment should be initialized to spaces
[Initialize LX Segment]
LX segment processing begins → System clears dependent segment area, increments sequence number, and initializes LX segment structure to spaces
[Initialize Second LX Segment]
Processing second LX segment → System clears dependent segment area, increments sequence number, and initializes second LX segment structure
[Initialize M13 Segment]
M13 segment initialization is performed → M13 segment is cleared and identifier is set to 'M13'
[Initialize M11 Segment]
The system begins M11 segment creation → The segment is cleared, sequence number is incremented, and M11 identifier is set
[Initialize N3 Segment]
The system begins N3 segment creation → The N3 segment structure is cleared and initialized with spaces
[Initialize N4 Segment]
The system begins N4 segment creation → The N4 segment is cleared to spaces and the identifier is set to 'N4 '
[Initialize ABI Routing Message]
Preparing broker notification → Initialize GCX105 input structure with high security byte and cargo type settings
[Initialize Return Code Message Pointer]
The return code parameters are being initialized → The message pointer is set to null
[Initialize Broker Notification Message]
The system initializes the broker notification message → The message should be initialized with high-value security byte, US CCN key, action code 'ZZZ', and sending transaction 'GCCS309'
[Initialize M12 Segment]
The M12 segment structure needs to be created → The segment is initialized with spaces, M12 identifier is set, and sequence number is incremented
[Initialize Description Variables]
The system begins N10 segment processing → All description variables, marks and numbers, and quantity totals are cleared to spaces or zero
[Initialize H2 Segment]
The system begins processing the H2 segment → The system should initialize dependent segment area, increment sequence number, and prepare H2 segment structure
[Initialize Log Message Structure]
The system begins transaction logging → The log message structure GCX105-INPUT is cleared and initialized to spaces
[Initialize Root Record A9RT-TRANSMISSION-SEGMENT]
The system prepares to create the database record → The A9RT-TRANSMISSION-SEGMENT structure is initialized with the transmission number
[Initialize GCT109 Parameters]
The system prepares to spawn GCT109 transaction → GCT109 input parameters are initialized with default values
[Initialize Line Counter to Zero]
The system begins initialization → The assigned number counter is set to zero
[Initialize Description Variables]
Description processing begins → All description working variables are cleared to spaces and counters are reset to zero
[Initialize LX Segment]
The system begins LX segment creation → The dependent segment area is cleared and LX segment structure is initialized with spaces
[Initialize Root Transmission Record]
The system prepares to create the root transmission record → The transmission segment is initialized with the transmission number, read-and-delete flag is set to spaces, and transaction set is set to '309'

Core Acceptance Criteria

[2:Bill Owner Validation]
If RT43 created status AND follower manifest:
M1109 master manifest
M1109 export manifest
RT10 cargo pending/error status
non-US CCN SCAC CPRS without bill owner CPRS
→ Halt EDI Processing. Otherwise, continue.
[Processing Action Type?]
Action type is PRELIMINARY:
(UPDATE AND transmission type is GCX111/GCX106/GCX113/GCX101/GCX107)
DELETE
ADD
→ Route to corresponding processing section: A200 for PRELIMINARY, A500 for UPDATE, A400 for DELETE, A300 for ADD
[4:Preliminary Manifest Processing]
The RT33 EDI sent electronically flag is not already set to true → Set RT33 EDI sent electronically flag to true and update GCSUSRT record
[8:Manifest Header Processing]
Transmission type is GCX101, GCX106, GCX107, GCX111, or GCX113 → Set transmission prefix to 101, 106, 107, 111, or 113 respectively, otherwise set to 998, and combine with machine time for transmission number
[8:Manifest Header Processing]
Vessel name position 23 equals 'T' AND transport is export AND vessel2 name is not spaces or low-values → Use vessel2 name and RT40 flight voyage number, otherwise use standard vessel name and M1006 flight voyage number
[8:Manifest Header Processing]
Original country code is CA, US, or MX → Use original country code, otherwise if location ID is 2304 use MX, else default to CA
[8:Manifest Header Processing]
Action is UPDATE:
(transmission is GCX106 AND action is ADD)
(transmission is GCX111/GCX113/GCX107 AND action is DELETE)
→ Set manifest type code to 'Y', otherwise use original M1009 manifest type code
[8:Manifest Header Processing]
Vessel name position 23 equals 'T' AND manifest is for returned goods AND action is preliminary → Set vessel name to 'TRAIN' and manifest type code to 'P'
[12:Manifest Details Processing]
Manifest is special manifest:
broker bond is true
→ Set BOL type code to '00', otherwise use original M1109 BOL type code
[12:Manifest Details Processing]
Office code is not '99' AND line release number position 1 is not 'C4 FILED BY BROKER' AND line release number position 2 is not spaces → If line release number position 2 is not spaces, set BOL type code to '25'
[11:Amendment Type Processing]
Action is DELETE:
(action is UPDATE and in delete mode)
→ Set amendment type code to 'D', when action is UPDATE and in add mode set to 'A', otherwise use original amendment type code
[11:Amendment Type Processing]
Transmission is GCX106 and action is DELETE → Set amendment code to '02', when transmission is GCX106 and action is UPDATE or ADD set to '03', otherwise use original amendment code or default to '01' if empty
[15:OB Reference Number Processing]
Reference number qualifier equals 'OB' → Add to N9 table with qualifier and reference number, increment N9 counter
[17:General Reference Number Processing]
Reference number qualifier is not OB and not BN AND (N9 data is not spaces:
(FEN value AND immediate export AND Laredo location))
→ Add to N9 table and create N9 segment, set FDA shipment flag if qualifier is ZZ with 2K FDA reference or qualifier is 2K
[19:Residue Description Processing]
Processing N9 segments → Create N9 segment with qualifier 'ZF' and residue description as reference number
[20:AES Data Processing]
SED data is not spaces or low-values AND SED does not start with 'IB ' → Create N9 segment with first 3 characters as qualifier and remaining 29 characters as reference number
[26:Broker Processing]
Broker is not unknown AND not marked as not required AND office code is not '99' → Create N1 segment with broker details, lookup broker table for routing codes, and send broker notification message
[28:Customs Data Processing]
M12 data is not spaces AND not broker bond → Process M12 segment with in-bond type code conversion using lookup table and set FDA indicator
[30:Vehicle Identification Processing]
Equipment is empty type → Set load/empty status to 'E', when BOL type is 23 or ER threshold found set to 'L'
[33:Commodity Description Processing]
Processing N10 segments with numeric quantities → Sum all numeric quantities from positions 10-15 and use total for first N10 segment
[42:Idler Manifest Processing]
Processing manifest data → Save current CCN, retrieve idler manifests by lead CCN, process VID/N10/H1-H2 segments for each idler, then restore original cargo data
[47:EDI Status Flag Updates]
Current status is preliminary and not train type → Set status to amendment and update GCSUSRT, when current status is amendment and is train type set to preliminary and update GCSUSRT
[21:Entity Name Processing]
Transmission type is not GCX106 → Send customer notification message with action type (ADD/UPDATE/DELETE) and CCN information
[Set Default Processing Flag to Send EDI]
The system sets the default processing behavior → The EDI send processing flag is set to true to allow EDI transmission
[Check if Follower Manifest Created]
The cargo has RT43 created status AND is a follower manifest → The system sets the flag to skip EDI processing
[Check if Master Manifest]
The cargo manifest type is M1109 master → The system sets the flag to skip EDI processing
[Check if Export Manifest]
The cargo manifest type is M1109 export → The system sets the flag to skip EDI processing
[Validate Bill Owner is CPRS]
The cargo does not have US CCN SCAC CPRS authorization → The system checks if the bill owner is CPRS - if not CPRS, skip EDI processing; if CPRS, continue with EDI processing
[Is Follower Manifest?]
The manifest is identified as RT43 created AND it is a follower manifest → The system sets the flag to prevent EDI processing
[Is Master M1109?]
The manifest type is M1109 master → The system sets the flag to prevent EDI processing
[Is Export M1109?]
The manifest type is M1109 export → The system sets the flag to prevent EDI processing
[Is SCAC Code CPRS?]
The SCAC code is US CCN SCAC CPRS → The system allows EDI processing to continue
[Assign FDA Indicator to Customs Data]
The M12 customs segment is being prepared for EDI transmission → The FDA indicator value is assigned to the M12-12-FDA-IND field in the customs data
[EDI Status Already Sent?]
The manifest EDI status is not already set to electronically sent → Set the EDI status to electronically sent and update the manifest record
[Generate Transmission Number]
The transmission type is GCX101, GCX106, GCX107, GCX111, or GCX113 → Set transmission prefix to 101, 106, 107, 111, or 113 respectively, otherwise set to 998, and use machine time as transmission number
[Process M10 Manifest Header]
Creating the M10 manifest header segment → Set SCAC code, transport type, country code, vessel name, flight/voyage number, reference number, quantity, and manifest type code based on action type and transmission conditions
[Process M10 Manifest Header]
The transmission is GCX106 and action is ADD → Set conditional response code to Y and manifest type code to Y
[Process P4 Port Information]
Creating the P4 port information segment → Set location ID, ETA date, and quantity from manifest data
[Process LX Line Number]
Creating an LX line number segment → Increment the assigned number and set to 00001
[Process General Reference Numbers]
A reference number is not empty and not OB or BN qualifier, or is FEN value for immediate export at Laredo → Add the reference number to the N9 table and create N9 segment, and detect FDA shipment for ZZ or 2K qualifiers
[Bill Type = 23?]
The BOL type code is 23 → Create N9 segment with ZF qualifier and residue description
[Process AES Export Data]
SED data exists and is not empty or does not start with IB → Create N9 segment with SED qualifier and reference number from SED data
[Process Entity Information N1-N3-N4-PER]
Entity data exists for cargo records → Create N1, N3, N4, and PER segments for each entity with complete information
[Process Entity Information N1-N3-N4-PER]
Broker is not unknown or not required and office code is not 99 → Create N1 segment with broker information, lookup broker details, and send broker notification
[Customs Data Available?]
M12 customs data exists and is not broker bond → Process the M12 customs segment
[Process M12 Customs Data]
In-bond type code exists → Look up the corresponding EDI value in the conversion table, or set to ?? if not found
[Process M12 Customs Data]
Creating M12 segment → Set FDA indicator based on whether FDA shipment was detected during reference number processing
[Process N10 Commodity Descriptions]
Office code is 99 → Sum all numeric quantities from all cargo records and use total in first N10 segment
[Process N10 Commodity Descriptions]
Office code is not 99 and additional line release data exists → Create additional N10 segments for each line release with appropriate commodity codes and descriptions
[Process Idler Manifests]
Idler manifests exist for the same lead CCN → Process VID, N10, and H1-H2 segments for each idler manifest until no more idlers found
[Log Transmission Activity]
All segments have been processed → Create log entry with action code, CCN, transaction details, and timestamp
[Spawn GCT109 Follow-up]
All processing is complete → Send transmission number to GCT109 transaction for follow-up processing
[Set SCAC Code from Manifest]
M10 segment is being populated → The SCAC code is copied to M10-01-SCAC field
[Set Transport Type Code]
M10 segment is being populated → The transport type code is assigned to M10-02-TRANSP-TYP-CDE
[Set Reference Number and Quantity]
Populating M10 segment → Reference number is assigned to M10-07-REF-NUM and quantity to M10-08-QUANTITY
[Set Record Type to CARGO]
Setting record identification → M10-12-RCD-TYPE is set to 'CARGO' AND M10-12-RCD-NUM is set from M1012 reference number
[Clean Segment Data]
Finalizing the segment → All underscore characters are replaced with spaces AND segment is inserted into database
[Set Vessel Name in M10 Segment]
The vessel name has been determined through the selection logic → The system should set position 24 of the vessel name field to a space character before placing it in the M10 segment
[Check Vessel Name Position 23 = 'T'?]
The vessel name position 23 contains 'T' indicator AND transport type is export AND secondary vessel name is available and not empty → Use secondary vessel name and secondary flight/voyage number for manifest transmission
[Use Primary Vessel Name]
The vessel name position 23 does not contain 'T':
transport type is not export
secondary vessel name is not available
empty
→ Use primary vessel name and primary flight/voyage number for manifest transmission
[Use Original Country Code]
The country code validation passes → The original country code is moved to the M10 segment country code field
[Set Country Code to MX]
The location-based default logic is applied → The country code is set to MX for the M10 segment
[Set Country Code to CA]
The location-based default logic is applied → The country code is set to CA for the M10 segment
[Assign Country Code to M10 Segment]
The country code assignment is finalized → The country code is moved to the M10-03-COUNTRY-CDE field for EDI transmission
[Set Manifest Type Code to 'Y' Set Conditional Response Code to 'Y']
The processing action is ADD → The manifest type code should be set to 'Y' and the conditional response code should be set to 'Y'
[Set Manifest Type Code to 'Y']
The processing action is DELETE → The manifest type code should be set to 'Y'
[Update EDI Status Flag if Not GCX106, Update EDI Status Flag]
The transmission type is not GCX106 and the EDI sent electronically flag is not already set → The system sets the EDI sent electronically flag to true and updates the cargo record
[Generate Transmission Number]
The system needs to generate a transmission number → The system determines the prefix (101 for GCX101, 106 for GCX106, 107 for GCX107, 111 for GCX111, 113 for GCX113, or 998 for others) and combines it with the machine time to create the transmission number
[Create Root Transmission Record]
The system needs to create the root transmission record → The system initializes the transmission segment with the transmission number, sets transaction set to '309', and creates the record, retrying with incremented transmission number if creation fails
[Process M10 Manifest Header]
The M10 manifest header segment is being created → The system sets the manifest type code to 'Y' to indicate an update operation and populates all required manifest header fields including SCAC code, transport type, country code, vessel information, and reference numbers
[Set M13 Delete Mode]
The first M13 segment is being processed → The system sets the M13 processing mode to delete mode and sets the amendment type code to 'D' for deletion
[Process M13 Amendment - Delete]
The M13 amendment segment is being created for deletion → The system creates the M13 segment with amendment type code 'D', populates SCAC code, location ID, BOL number, quantity, and appropriate amendment codes for the deletion operation
[Process LX2 Line Number 2]
The system needs to create the second line number segment → The system creates an LX segment with assigned number '00002' and increments the sequence number
[Set M13 Add Mode]
The second M13 segment needs to be processed → The system sets the M13 processing mode to add mode and sets the amendment type code to 'A' for addition
[Process M13 Amendment - Add]
The M13 amendment segment is being created for addition → The system creates the M13 segment with amendment type code 'A', populates SCAC code, location ID, BOL number, quantity, and appropriate amendment codes for the addition operation
[Process Reference Numbers]
Reference numbers are being processed → The system processes N9 segments for OB qualifiers first, then BN qualifiers, then all other reference number qualifiers, and creates special ZF segments for BOL type 23 with residue descriptions
[Process Idler Manifests if Train]
The system checks for idler manifest processing requirements → The system saves the current CCN key and processes all associated idler manifests including their VID, N10, and hazardous material segments
[Spawn GCT109 Processing]
The system needs to initiate downstream processing → The system creates a GCT109 transaction with the transmission number and submits it for processing via CIMS or EXCI depending on the runtime environment
[Update Manifest Status]
The system needs to update the manifest status → If the current status is preliminary and not a train operation, the system sets the status to amendment; if the current status is amendment and it is a train operation, the system sets the status to preliminary
[Process General Reference Numbers]
The system encounters reference numbers that are not spaces, not excluded values, and not OB or BN qualifiers, or when FEN value exists with immediate export at Laredo location → The general reference qualifier and number are stored in the N9 table and the counter is incremented
[Create N9 EDI Segment]
The system creates EDI segments for transmission → N9 segments are created with the stored reference qualifiers and numbers, replacing underscores with spaces
[FDA Reference Check]
The system encounters reference qualifier 'ZZ' with reference number starting with '2K FDA' or reference qualifier '2K' → The FDA shipment indicator is set to true for proper regulatory processing
[Process General Reference Numbers]
The system processes AES references that are not spaces, low-values, or internal broker references starting with 'IB' → N9 segments are created with the first 3 characters as qualifier and remaining 29 characters as reference number
[Process General Reference Numbers]
The system processes reference numbers for this shipment type → A special N9 segment is created with qualifier 'ZF' and the residue description as the reference number
[N3 Address Data Available?]
The system checks for address information availability → Address segment is processed if N3 address data is not empty, otherwise address processing is skipped
[N4 Location Data Available?]
The system checks for location information availability → Location segment is processed if N4 location data is not empty, otherwise location processing is skipped
[PER Contact Data Available?]
The system checks for contact information availability → Contact segment is processed if PER contact data is not empty, otherwise contact processing is skipped
[Generate ABI Routing Message]
The system generates ABI routing message → ABI routing code is constructed using broker alternative US code if available, otherwise using district code, filer code, and office code combination
[Spawn Broker Notification]
The system dispatches broker notification → Notification message is sent through BPE external call interface if running in BPE environment, otherwise through CIMS messaging system
[Update EDI Status Flag to Electronic]
The transmission type is not GCX106 and the EDI status is not already set to electronic transmission → The system updates the EDI status flag to electronic and saves the cargo record
[Generate Transmission Number]
The system needs to create a transmission identifier → The system generates a transmission number using the appropriate prefix (101 for GCX101, 106 for GCX106, 107 for GCX107, 111 for GCX111, 113 for GCX113, or 998 for others) combined with machine time
[Set Amendment Mode to ADD]
The system prepares to process M13 amendment segments → The system sets the amendment processing mode to ADD
[Process M13 Amendment Segment]
The system determines the amendment type code → The system assigns amendment type code 'A' for addition operations
[Process M13 Amendment Segment]
The operation is ADD → The system assigns amendment code '03'
[Process M11 Manifest Details]
The manifest is a special manifest or involves a broker bond → The system sets the BOL type code to '00'
[Process M11 Manifest Details]
The office code is not '99' and line release number second occurrence is not spaces and first occurrence is not 'C4 FILED BY BROKER' → The system sets the BOL type code to '25'
[Process General Reference Numbers]
A reference number is not OB or BN qualifier and either the N9 data is not spaces/excluded values, or it's a FEN value for immediate export at Laredo location → The system processes the reference number and creates an N9 segment
[Process N9-ZF Residue Description]
The BOL type code equals 23 → The system creates an N9 segment with qualifier 'ZF' and residue description
[Process AES Export Data]
The SED data is not spaces, low-values, or starts with 'IB ' → The system creates N9 segments with the first 3 characters as qualifier and remaining 29 characters as reference number
[Process M12 Customs Data]
M12 data is not spaces and the transaction does not involve a broker bond → The system processes the M12 customs segment with FDA indicator
[Log Cargo Transmission Activity]
All segments have been processed successfully → The system logs the transmission activity with action code for cargo sent automatically
[Spawn GCT109 Follow-up Transaction]
The transmission has been logged → The system spawns GCT109 transaction with the transmission number
[Reference Data Available?]
The location ID is the Laredo location ID → The processing continues instead of being skipped
[Create N9 EDI Segment]
Creating the N9 EDI segment → The N9 segment is created with the reference qualifier and reference number from the N9 table entry
[Insert N9 Segment to Database]
The segment is ready for storage → The N9 segment is inserted into the database transmission table
[Process Entity Identification N1]
The system processes entity identification information → Create N1 segment with entity ID code, name, ID code qualifier, and ID code from the entity data
[Shipper Entity?]
The system checks the entity identification code → Trigger customer validation if entity ID code equals 'SH' (shipper)
[Process Address Information N3]
The system checks for address information availability → Create N3 segment with address line 1 and address line 2 if address data is not empty spaces
[Process City State Postal N4]
The system checks for city and state information availability → Create N4 segment with city name, state/province code, postal code, and country code if city/state data is not empty spaces
[Process Contact Information PER]
The system checks for contact information availability → Create PER segment with contact function code 'IC', contact name (first 23 characters), communication number qualifier, and communication number if contact data is not empty spaces
[Process Broker Entity]
The system processes broker entity information → Create N1 segment with entity ID 'CB', broker short name, ID qualifier '17', and construct broker routing code
[Create Broker N1 Segment]
The system constructs the broker ABI routing code → Use broker alternative US code + filer code + office code if alternative code exists, otherwise use district code + filer code + office code
[Generate ABI Routing Message]
The system generates broker routing message → Create message with text 'ABI ROUTING CODE ' followed by the constructed routing code and send via messaging system
[Retrieve Broker Segment Data]
Table service returns success code '0' → Move returned table segment data to broker segment structure for further processing
[Clear Broker Segment Data]
Table service returns failure code (not '0') → Clear broker segment data by moving spaces to broker segment structure
[Generate Transmission Number]
The system determines the transmission type (101, 106, 107, 111, 113, or default 998) → The system creates a transmission number using the appropriate prefix and current machine time
[Process M10 Manifest Header]
The M10 manifest header segment is being created → The system sets manifest type code to 'Y' for updates and applies vessel name and country code business rules
[Process M13 Amendment - Delete]
The M13 amendment segment is being created → The system sets amendment type code to 'D' for deletion and processes the cargo removal
[Process LX Line Number 2]
The second LX line number segment is being created → The system assigns line number '00002' and increments the sequence counter
[Process M13 Amendment - Add]
The M13 amendment segment is being created for the add operation → The system sets amendment type code to 'A' for addition and processes the new cargo data
[Process Idler Train Cars]
The cargo record has RT43 created status → The system saves the CCN key and processes all associated idler manifest records including VID, N10, and hazardous material segments
[Process General Reference Numbers]
The shipment is immediate export type and the location is Laredo → The reference number processing continues instead of being skipped
[Create N9 EDI Segment]
Creating the N9 EDI segment → The N9 segment is populated with the reference qualifier and reference number from the table, formatted with proper spacing
[Insert N9 Segment to Database]
The segment is ready for transmission → The N9 segment is inserted into the EDI transmission database with proper sequence numbering
[Loop Through Entity Records]
Processing entity information for EDI transmission → System loops through each entity record from 1 to maximum sequence minus 1 or until empty record is found
[Process Standard Entities]
Processing standard entities or when broker is unknown/not required/office code 99 → System processes each entity record through N1-N3-N4-PER segment creation, and processes special broker record at maximum sequence position if broker is unknown/not required/office code 99
[Process Broker Entity]
Processing broker entity information → System creates N1 segment with CB entity code, broker short name, qualifier 17, constructs ABI routing code from district/filer/office codes or alternative US code, and sends broker notification message
[Create N1 Entity Segment]
Creating N1 entity identification segment → System creates N1 segment with entity ID code, name, ID code qualifier, and ID code from entity data
[Shipper Entity? / Trigger Customer Validation]
Entity ID code equals 'SH' (Shipper) → System triggers customer validation process for the shipper entity
[Create N3 Address Segment]
N3 address data is not spaces → System creates N3 segment with address information line 1 and line 2
[Create N4 Location Segment]
N4 location data is not spaces → System creates N4 segment with city name, state/province code, postal code, and country code
[Create PER Contact Segment]
PER contact data is not spaces → System creates PER segment with contact function code 'IC', contact name (first 23 characters), communication number qualifier, and communication number
[Update EDI Status to Electronic]
The EDI status is not already set to electronic → The system sets the EDI status to electronic and updates the cargo record
[Generate Transmission Number]
The system needs to create EDI transmission → The system generates transmission number using machine time and creates transmission record
[Process M10 Manifest Header]
The system creates the M10 manifest header segment → The system sets manifest type code to Y and populates all required M10 fields including SCAC code, transport type, country code, vessel information, and record type as CARGO
[Process P4 Port Information]
The system creates the P4 port information segment → The system populates P4 segment with location ID, ETA date, and quantity information
[Process LX Line Number Assignment]
The system creates the LX line number segment → The system assigns line number 00001 and increments the assigned number counter
[Set Delete Mode Flag]
The system prepares to create M13 amendment segment → The system sets the delete mode flag to true
[Process M13 Amendment with Delete Code]
The system creates the M13 amendment segment → The system sets amendment type code to D, populates SCAC code, location ID, BOL number, quantity, amendment code, and action code
[Log Transmission Activity]
The action is pure delete and not part of an update operation → The system logs the transmission activity with automatic cargo sent status
[Spawn GCT109 Follow-up Processing]
All deletion segments have been created → The system invokes GCT109 program with the transmission number for follow-up processing
[Set SCAC Code from Manifest]
M10 segment is being populated → The SCAC code from manifest record M1001 field is assigned to M10-01-SCAC field
[Set Transport Type Code]
M10 segment is being populated → The transport type code from manifest record M1002 field is assigned to M10-02-TRANSP-TYP-CDE field
[Set Reference Number and Quantity]
M10 segment is being populated with reference data → Reference number from M1007-REF-NUM is assigned to M10-07-REF-NUM and quantity from M1008-QUANTITY is assigned to M10-08-QUANTITY
[Processing Mode?]
Action is UPDATE → Manifest type code is set to 'Y', when action is ADD with GCX106 transmission, manifest type code is set to 'Y', otherwise standard manifest type code from M1009-MANIF-TYP-CDE is used
[Conditional Response Required?]
Transmission is GCX106 AND action is ADD → Conditional response code is set to 'Y' and manifest type code is set to 'Y', otherwise standard conditional response code from M1011-COND-RESP-CDE is used
[Set Manifest Type for Update]
The delete operation is being processed → Manifest type code is set to 'Y' regardless of original value
[Set Record Type to CARGO]
Record type needs to be specified → Record type field M10-12-RCD-TYPE is set to 'CARGO'
[Set Record Number]
M10 segment record number field needs to be populated → Record number from M1012-REF-NUM is assigned to M10-12-RCD-NUM field
[Clean Segment Data]
Segment data needs to be cleaned for storage → All underscore characters in M10-SEGMENT are replaced with space characters
[Insert M10 Segment to Database]
Segment data is ready for storage → M10 segment data is moved to transmission data field and inserted into database via Z1010-ISRT-GCSA9DP procedure
[Set P4 Identifier]
The segment identifier needs to be set → The P4 identifier field should be set to 'P4 '
[Extract Location ID from Cargo Data]
P4 segment is being populated with location details → The location ID from GCUSRT-P401-LOCATION-ID should be moved to P4-01-LOCATION-ID
[Extract ETA Date from Cargo Data]
P4 segment is being populated with timing details → The ETA date from GCUSRT-P402-ETA-DATE should be moved to P4-02-ETA-DATE
[Extract Quantity from Cargo Data]
P4 segment is being populated with quantity details → The quantity from GCUSRT-P403-QUANTITY should be moved to P4-03-QUANTITY
[Store P4 Segment Data]
The segment data needs to be prepared for database insertion → The P4 segment should be moved to A9DP-TRANSMISSION-DATA
[Insert P4 Segment into Database]
The segment needs to be persisted in the transmission database → The Z1010-ISRT-GCSA9DP procedure should be performed to insert the P4 segment
[Set LX Identifier]
Setting segment identifier → System assigns 'LX ' as the segment identifier
[Increment Assigned Number Counter]
Assigning line numbers → System increments the assigned number counter by 1
[Assign Line Number 00001]
Assigning line number → System assigns '00001' as the assigned number
[Store LX Segment Data]
Preparing segment for transmission → System moves LX segment to transmission data area
[Insert LX Segment to Database]
Storing segment data → System calls database insert function to store LX segment
[Second LX Required?]
Checking if additional LX segment is needed → System requires second LX segment only for update transactions, otherwise completes LX processing
[Set Second LX Identifier]
Setting second segment identifier → System assigns 'LX ' as the second segment identifier
[Increment Assigned Number Counter Again]
Assigning second line number → System increments the assigned number counter by 1 again
[Assign Line Number 00002]
Assigning second line number → System assigns '00002' as the assigned number
[Store Second LX Segment Data]
Preparing second segment for transmission → System moves second LX segment to transmission data area
[Insert Second LX Segment to Database]
Storing second segment data → System calls database insert function to store second LX segment
[Set SCAC Code]
SCAC code assignment is performed → Primary SCAC code from cargo M1301 field is assigned to M13-01-SCAC
[Set Location ID]
Location ID assignment is performed → Location ID from cargo P401 field is assigned to M13-02-LOCATION-ID
[Set Secondary SCAC Code]
Secondary SCAC code assignment is performed → Secondary SCAC code from cargo M1309 field is assigned to M13-09-SCAC
[Replace Underscores with Spaces]
Segment formatting is performed → All underscore characters in M13 segment are replaced with spaces
[Insert M13 Segment to Database]
Database insertion is performed → M13 segment is inserted into transmission data and database insert operation is executed
[Set BOL/Waybill Number]
M11 segment is being populated → The BOL waybill number is copied to M11-01 field
[Set Location ID]
M11 segment is being populated → The location ID is copied to M11-02 field
[Set Quantity and Unit Code]
M11 segment is being populated → The quantity is copied to M11-03 field and manifest unit code is copied to M11-04 field
[Set Weight and Weight Unit Code]
M11 segment is being populated → The weight is copied to M11-05 field and weight unit code is copied to M11-06 field
[Special Manifest or Broker Bond?]
The cargo is marked as special manifest:
involves broker bond
→ The BOL type code is set to '00' regardless of original value
[Set Place of Receipt]
M11 segment is being populated → The place of receipt is copied to M11-10 field
[Set Additional BOL/Waybill Number]
M11 segment is being populated → The additional BOL waybill number is copied to M11-11 field
[Set Primary SCAC Code]
M11 segment is being populated → The primary SCAC code is copied to M11-12 field
[Replace Underscores with Spaces]
Segment formatting is performed → All underscore characters in the segment are replaced with space characters
[Insert M11 Segment to Database]
Segment insertion is performed → The M11 segment is stored in the transmission data structure
[Set Primary SCAC Code from M1112-SCAC-1]
The system processes the M11 segment for EDI transmission → The primary SCAC code from M1112-SCAC-1 is assigned to M11-12-SCAC field
[Set Second SCAC Code in M11-14-SCAC]
The system processes the second SCAC code for EDI transmission → The second SCAC code from M1114-SCAC-2 is assigned to M11-14-SCAC field
[Set Third SCAC Code in M11-15-SCAC]
The system processes the third SCAC code for EDI transmission → The third SCAC code from M1115-SCAC-3 is assigned to M11-15-SCAC field
[Skip OB and BN Qualifiers?]
The system processes reference numbers for N9 segment creation → References with OB or BN qualifiers are skipped and not processed in the general N9 processing loop
[Add Reference to Processing Table]
The system processes the reference for N9 segment creation → The reference qualifier and reference number are added to the N9 processing table and the table index is incremented
[Create N9 Segment]
The system creates an N9 segment → The segment is initialized with spaces, sequence number is incremented, segment identifier is set to 'N9', and dependent segment structure is prepared
[Set Reference Qualifier]
The system populates the N9 segment with reference data → The reference number qualifier from the processing table is moved to the N9 segment qualifier field
[Set Reference Number]
The system completes the N9 segment population → The reference number value from the processing table is moved to the N9 segment reference number field
[Set FDA Shipment Flag]
The system processes FDA shipment detection → The FDA shipment indicator flag is set to true for subsequent M12 segment processing
[Insert N9 Segment to Transmission]
The system finalizes the N9 segment for transmission → Underscores are replaced with spaces, the segment is moved to transmission data, and the segment is inserted into the EDI transmission structure
[Create N9 Segment with ZF Qualifier]
The system processes residue description requirements → The system should create an N9 segment and set the reference number qualifier to 'ZF'
[Set Residue Description]
The system sets the reference number field → The system should populate the reference number with the residue description from working storage
[Insert N9 ZF Segment]
The system processes the segment for transmission → The system should insert the N9 ZF segment into the EDI transmission data structure
[Extract SED Qualifier - First 3 Characters]
The system processes the SED field for N9 segment creation → The system should extract the first 3 characters of the SED field as the reference number qualifier
[Extract SED Reference - Characters 4-29]
The system processes the SED field for N9 segment creation → The system should extract characters 4 through 29 of the SED field as the reference number
[Create N9 Segment with AES Data]
The system creates an N9 segment for AES data → The system should populate the N9 segment with 'N9 ' identifier, the extracted qualifier, and the extracted reference number
[Insert N9 Segment to Transmission]
The system processes the N9 segment for transmission → The system should insert the N9 segment into the EDI transmission data
[Process N1 Entity Segment]
System processes the N1 entity segment → N1 segment is created with entity ID code, name, ID code qualifier, and ID code, and segment is written to transmission data
[Process N3 Address Segment]
System processes the N3 address segment → N3 segment is created with address info 1 and address info 2, and segment is written to transmission data
[Process N4 Location Segment]
System processes the N4 location segment → N4 segment is created with city name, state/province code, postal code, and country code, and segment is written to transmission data
[Process PER Contact Segment]
System processes the PER contact segment → PER segment is created with function code 'IC', contact name (truncated to 23 characters), communication qualifier, and communication number, and segment is written to transmission data
[Process Broker Entity]
System processes broker entity → N1 segment is created with entity ID 'CB', broker short name, ID qualifier '17', and ID constructed from district code, filer code, and office code
[Generate ABI Routing Message]
System generates ABI routing message → Message is created with 'ABI ROUTING CODE' prefix followed by appropriate code combination, and message is sent via BPE or TPE communication method
[Process N1 Entity Identification]
The system processes the entity identification segment → N1 segment is created with entity ID code, name, ID code qualifier, and ID code from the entity data
[Is Entity Type Shipper?]
The system checks the entity ID code → Customer validation is triggered if entity ID code equals 'SH', otherwise processing continues to address validation
[Process N3 Address Information]
The system processes the address segment → N3 segment is created with primary address info and secondary address info from the entity data
[Process N4 City/State/Postal]
The system processes the location segment → N4 segment is created with city name, state/province code, postal code, and country code from the entity data
[Process PER Contact Details]
The system processes the contact segment → PER segment is created with contact function code 'IC', contact name (first 23 characters), communication number qualifier, and communication number from the entity data
[Set N3 Identifier]
The system sets the segment identifier → The N3 identifier is set to 'N3 ' to identify this as an address segment
[Move Primary Address Line]
The system processes address information → The primary address information is moved to the first address field of the N3 segment
[Move Secondary Address Line]
The system continues address processing → The secondary address information is moved to the second address field of the N3 segment
[Replace Underscores with Spaces]
The system performs format standardization → All underscore characters in the N3 segment are replaced with space characters
[Store N3 Segment Data]
The system prepares for data transmission → The N3 segment data is stored in the transmission data area
[Insert Address Segment]
The system performs segment insertion → The N3 address segment is inserted into the EDI transmission sequence
[Move City Name to N4]
Processing N4 segment data assignment → The city name is moved to the N4-01-CITY-NAME field
[Move State/Province Code to N4]
Processing N4 segment data assignment → The state or province code is moved to the N4-02-STATE-PROV-CDE field
[Move Postal Code to N4]
Processing N4 segment data assignment → The postal code is moved to the N4-03-POSTAL-CDE field
[Move Country Code to N4]
Processing N4 segment data assignment → The country code is moved to the N4-04-COUNTRY-CDE field
[Replace Underscores with Spaces]
Preparing the segment for EDI transmission → All underscore characters in the N4 segment are replaced with spaces
[Store N4 Segment for Transmission]
Storing the segment for EDI transmission → The N4 segment is moved to the transmission data field
[Set Contact Function Code to 'IC']
The contact function code field needs to be populated → The contact function code is set to 'IC' indicating an information contact
[Extract Contact Name - First 23 Characters]
The contact name is being extracted for PER segment → Only the first 23 characters of the contact name are used in the PER segment
[Set Communication Number Qualifier]
The PER segment communication number qualifier field is being populated → The communication number qualifier from the source data is assigned to identify the type of communication method
[Set Communication Number]
The PER segment communication number field is being populated → The communication number from the source data is assigned to the PER segment
[Replace Underscores with Spaces]
The segment data is being prepared for transmission → All underscore characters in the PER segment are replaced with space characters
[Insert PER Segment into Transmission]
The segment is ready for EDI transmission → The PER segment data is inserted into the transmission data structure for processing
[Skip Validation for GCX106]
The transmission type is GCX106 → The customer validation process is skipped and control returns to the calling process
[Call External Validation via CIMS]
The external validation service needs to be invoked → The validation request is sent using CIMS interface with message queuing and proper transaction handling
[Check Broker Status]
The broker is not unknown AND broker is required AND office code is not '99' → Proceed with broker N1 segment creation and processing
[Create Broker N1 Segment]
Creating broker N1 segment → Set entity ID code to 'CB' for customs broker
[Set Broker Short Name]
Setting broker name information → Use broker short name from cargo record RT01 field
[Set Broker Short Name]
Setting identification code qualifier → Set ID code qualifier to '17' for broker identification
[Insert N1 Segment to Database]
Storing segment data → Insert N1 segment into GCSA9DP transmission data table
[Create ABI Routing Code Message]
Creating ABI routing message → Format message as 'ABI ROUTING CODE ' + alternative US code + filer code + office code
[Create ABI Routing Code Message]
Creating ABI routing message → Format message as 'ABI ROUTING CODE ' + district code + filer code + office code
[Spawn via EXCI]
Sending broker notification message → Use CSIEXCI call to spawn GCT1051E transaction with broker message
[Spawn via CIMS]
Sending broker notification message → Use CIMS calls to spawn GCT1051E transaction with broker message
[Look up Broker Alternative US Code from Broker Table]
The system looks up broker information in the broker table using broker short name and location ID as key → The system retrieves the broker segment containing alternative US code information
[Create ABI Routing Code Message String]
The system creates the ABI routing code message → The message contains 'ABI ROUTING CODE ' followed by alternative US code, filer code, and office code
[Create ABI Routing Code Message String]
The system creates the ABI routing code message → The message contains 'ABI ROUTING CODE ' followed by district code, filer code, and office code
[Set Message Parameters with CCN Key and Action Code]
The system sets up message parameters → The message includes CCN key, ZZZ action code, GCCS309 sending transaction, ACF2 user ID, and high security byte
[Add Date, Time, and User Information]
The system adds timestamp information → The message includes current machine date with century prefix and current machine time
[Spawn External Transaction via EXCI]
The broker notification message needs to be sent → The system uses EXCI interface to transmit the message to external transaction GCT1051E
[Spawn External Transaction via CIMS]
The broker notification message needs to be sent → The system uses CIMS interface to transmit the message to external transaction GCT1051E
[Setup EXCI Transaction Call]
Setting up external transaction call → The system configures EXCI transaction name, communication length, message data, call data length, and initializes message pointer to null
[Setup CIMS Transaction Call]
Setting up transaction call → The system prepares CIMS call with common area, change function, alternate PCB, and transaction message parameters
[Write Message Log]
Logging transaction message → The system calls WRITMSGL with common area, alternate PCB, message code, message content, message length, and module name
[Purge Transaction]
Completing TPE transaction processing → The system calls CIMS with common area, purge function, and alternate PCB to clean up transaction
[Calculate Communication Area Length]
The communication area is being prepared → The communication length is calculated as message length plus 4 bytes for header
[Move Message Data to Communication Area]
The communication area is being populated → The message content is moved to the EXCI communication data field
[Calculate Total Call Data Length]
The total call data length needs to be determined → The call data length is calculated as the sum of communication header length and message length
[Calculate Communication Area Length]
The system calculates communication area length for EXCI call → The EXCI communication length is set to message length plus 4 bytes AND the total call data length is calculated as header length plus message length
[Set Success Return Code]
The transaction status needs to be set → The return code is set to success status
[Create Broker N1 Segment]
The system creates a broker N1 segment → The segment should be initialized with spaces, sequence number incremented, segment identifier set to 'N1', entity ID code set to 'CB', broker short name populated, and ID code qualifier set to '17'
[Lookup Broker Alternative US Code]
The system performs a table lookup for broker alternative US code using broker short name and location ID → The system should retrieve the broker segment data or set it to spaces if lookup fails
[Insert Broker N1 Segment]
The system processes the segment for insertion → The segment should have underscores replaced with spaces and be inserted into the EDI transmission
[Create ABI Routing Code Message]
The system creates the ABI routing code message → The message should contain 'ABI ROUTING CODE ' followed by the appropriate routing code (either alternative US code or district code) concatenated with filer code and office code
[Set Transaction Details]
The system sets transaction details → The message should include ACF2 user ID, machine date (century + date), and machine time
[Running in BPE Environment?]
The system checks the processing environment → If running in BPE environment, use EXCI interface; otherwise use CIMS interface for message transmission
[Set In-Bond Type Code]
In-bond type code needs to be assigned to the M12 segment → The in-bond type code from the customs record is moved to the M12 segment field
[In-Bond Type Code Empty?]
The in-bond type code field is evaluated for content → If empty or spaces, skip conversion lookup; if populated, proceed with conversion lookup
[Lookup In-Bond Type Conversion]
The system searches the conversion table for matching internal code → The lookup table is searched to find the corresponding EDI standard code
[Set Converted In-Bond Type]
A matching conversion is found in the lookup table → The EDI standard in-bond type code from the lookup table is assigned to the M12 segment
[Set Entry Number]
Entry number needs to be populated in M12 segment → The entry number from customs record is moved to M12 entry number field
[Set Location IDs]
Location identifiers need to be populated → Both location ID 1 and location ID 2 from customs record are moved to corresponding M12 fields
[Set Customs Shipment Value]
Customs shipment value needs to be populated → The customs shipment value from customs record is moved to M12 customs shipment value field
[Set In-Bond Control Number]
In-bond control number needs to be populated → The in-bond control number from customs record is moved to M12 control number field
[Set Reference Number Qualifier]
Reference number qualifier needs to be populated → The reference number qualifier from customs record is moved to M12 reference qualifier field
[Set Reference Number]
Reference number value needs to be populated → The reference number from customs record is moved to M12 reference number field
[Set Transport Type Code]
Transport type code needs to be populated → The transport type code from customs record is moved to M12 transport type field
[Set Vessel Name]
Vessel name needs to be populated → The vessel name from customs record is moved to M12 vessel name field
[Set FDA Indicator]
FDA indicator needs to be populated → The FDA shipment indicator flag is moved to M12 FDA indicator field
[Insert M12 Segment to Database]
The segment needs to be persisted for EDI transmission → The M12 segment is inserted into the transmission database and processing completes successfully
[Search In-Bond Type Lookup Table]
The system processes the in-bond type code for EDI transmission → The system initializes lookup table index to 1 and searches the GCSUSS99-M1201-ARRAY table for matching CPRAIL value
[Convert to EDI Format Using Table Value]
The system finds a matching CPRAIL value in the GCSUSS99-M1201-ARRAY → The system converts the code to EDI format using the corresponding GCSUSS99-M1201-EDI309-VALUE from the lookup table
[Create VID Segment]
VID segment is being created → System initializes VID segment with identifier 'VID' and populates equipment description code, equipment initials, equipment number, primary seal number, and secondary seal number from cargo data
[Set Load Status to Empty]
The cargo has empty equipment flag set (88-GCUSRT-M1109-EMPTY-EQUIP is true) → System sets VID load/empty status code to 'E' indicating empty equipment
[Set Load Status to Loaded]
Bill of lading type code equals 23:
emergency response threshold is found (GCUSRT-ER-THRES-FOUND)
→ System sets VID load/empty status code to 'L' indicating loaded equipment
[Insert VID Segment to Transmission]
VID segment processing is complete → System replaces underscores with spaces in VID segment, assigns it to transmission data, and inserts it into the EDI transmission queue
[Set Load Status to 'E' - Empty]
The empty equipment flag is set to true → The vehicle load/empty status code should be set to 'E'
[Set Load Status to 'L' - Load]
The bill of lading type code equals 23:
the environmental threshold found flag is set
→ The vehicle load/empty status code should be set to 'L'
[Create VC Segment]
VC segment is created → The segment should be initialized with spaces, populated with 'VC ' identifier, vehicle ID number, and factory car order number
[Format VC Segment]
The segment is formatted for transmission → All underscores should be replaced with spaces and the segment should be inserted into the transmission data
[Load Additional Description Data]
Processing extended description information → The system loads data from N10 more data fields and all huge description segments up to the maximum sequence limit
[Office Code = 99?]
The office code is '99' → The system applies special quantity totaling logic across multiple segments, otherwise uses standard single quantity
[Calculate Total Quantities]
Calculating total quantities → The system iterates through all segments, validates numeric quantities, and accumulates the total quantity
[Create First N10 Segment]
Creating the primary N10 segment → The system creates an N10 segment with sequence number, identifier, and transmission data
[Set Primary Quantity]
The manifest is an idler manifest → The system sets quantity to '000000000000000', otherwise uses calculated total for office 99 or standard quantity for other offices
[Set Description and Marks]
Setting description and marks fields → The system uses the first description line or '.' if empty, and uses the first marks and numbers or stores for reference
[Set Commodity Codes]
Setting commodity codes and related information → The system populates commodity code qualifier, harmonized commodity code, customs shipment value, weight unit code, weight, country code, and line release number from the first occurrence
[Additional Descriptions Exist?]
Checking for additional description content → The system determines if description lines 2-12 or marks lines 2-12 contain non-space content requiring separate segments
[Create Extended N10 Segments]
Creating extended N10 segments → The system creates N10 segments with zero quantity, description content or '.', marks content or '.', and proper sequence numbering for each non-empty line
[Multiple Line Release Codes?]
Checking for additional line release processing → The system determines if description lines 13 and beyond contain content requiring separate N10 segments
[Process Multi-Occurrence N10s]
Processing multi-occurrence line release numbers → The system iterates through segments starting from the second occurrence, creating N10 segments with appropriate quantities, descriptions, and line release numbers
[Create Separate N10 for Each Code]
Creating individual N10 segments for each line release → The system creates N10 segments with specific quantities, shared descriptions and marks, individual line release numbers, and commodity codes when available
[Create Extended N10 Segments]
Creating continuation N10 segments → The system creates N10 segments with zero quantity, the description content, '.' for marks, and proper sequence numbering until all non-space lines are processed
[Move Additional Description Data]
The system processes additional description sources → Additional description data and extended description segments are loaded into the consolidated work area
[Load Extended Description Segments]
The system processes extended description segments up to the maximum sequence limit → Each extended description segment is loaded into its corresponding indexed position in the work area
[Calculate Total Quantity Across All N10 Occurrences]
Creating N10 segment with quantity information → Calculate total quantity by iterating through all N10 occurrences and summing numeric quantity values, then use this total as the N10 segment quantity
[Use Individual N10 Quantity]
Creating N10 segment with quantity information → Use the quantity from the first N10 occurrence directly without any calculation or aggregation
[Set Quantity to Zero]
Setting quantity for N10 segment creation → Override any calculated or individual quantity and set N10 quantity to zero with 15 digits
[Set Line Release Number]
Office code != 99 → Set the N10 line release number from the first occurrence of line release data
[Create N10 Segment]
Processing additional N10 occurrences with line release data → Create additional N10 segments for each occurrence, using individual quantities and line release numbers, with shared description and marks from primary segment
[Insert N10 Segment to Database]
N10 segment creation is complete → Insert the N10 segment into the transmission database and increment sequence number
[Office Code = '99'?]
The office code equals '99' → The line release number field is not populated in the primary N10 segment
[Line Release Number = 'C4 FILED BY BROKER'?]
The line release number equals 'C4 FILED BY BROKER ' → The line release number is cleared to spaces in the N10 segment
[Process Multiple Line Release Occurrences]
Processing line release numbers for N10 segments → Each non-empty line release number occurrence generates a separate N10 segment with the corresponding line release number
[Set Default Values for Empty Data]
Creating the N10 segment for that occurrence → Quantity is set to '0000000000', description is set to '.', and marks and numbers is set to '.'
[Consolidate Description Text from Multiple Sources]
The system processes N10 segments → Description text is consolidated from GCUS-N1002-LONG-DESC, GCSUSS10-N10-MORE-DATA, and GCSUSS12-N10-HUGE-DESC into a unified description array
[Create First N10 Segment with Primary Description]
The system creates the first N10 segment → For office code '99', quantity is totaled from all occurrences; for other offices, quantity comes from first occurrence; description uses first consolidated description line; marks and numbers default to '.' if empty
[Loop Through Extended Descriptions - Index 2 to 12]
Either description text or marks and numbers are not empty for a given index → An N10 segment is created with quantity '0000000000', description text (or '.' if empty), and marks and numbers (or '.' if empty)
[Continue Loop for Remaining Descriptions - Index 13 to 500]
Description text is not empty for indexes in this range → N10 segments are created with quantity '0000000000', the description text, and marks and numbers set to '.'
[Set Quantity to 0000000000]
The system processes indexes 2 through 500 → The quantity field is set to '0000000000' for all extended description segments
[Create First N10 Segment with Primary Description]
The system processes the first N10 segment → Quantity is totaled from all numeric quantity fields across all sequences and occurrences, and the total is used in the primary N10 segment
[Set Default Values]
The system processes the line release code for N10 segment creation → The system sets quantity to '0000000000', customs shipment value to '0000000000', weight to '0000000000', weight unit code from saved value, free form description to '.', and marks and numbers to '.'
[Use Actual Quantity and Line Release Code]
The system processes the line release code for N10 segment creation → The system uses the actual quantity value, saved description, saved marks and numbers, and the specific line release number for the occurrence
[Add Commodity Code to Segment]
The system creates the N10 segment → The system includes the harmonized commodity code and commodity code qualifier in the segment
[Insert N10 Segment with Line Release Code]
The system processes the line release code → The system creates an N10 segment with incremented sequence number, replaces underscores with spaces, and inserts the segment into the transmission data
[Extract Hazmat Code]
The system extracts the hazmat code from the H101 field → The hazmat code is moved to the H1 segment identifier field for EDI transmission
[Extract Hazmat Description]
The system processes the H104 hazmat description field → The description is moved to the H1 segment description field for EDI transmission
[Extract Hazmat Contact Information]
The system processes the H105 hazmat contact field → The contact information is moved to the H1 segment contact field for EDI transmission
[Create H1 Segment]
The system creates an H1 segment with identifier 'H1' and populates all hazmat fields → The H1 segment is formatted, sequence numbered, and inserted into the EDI transmission database
[Additional Hazmat Description Exists]
The system checks if the H201 extended description field contains data → An H2 segment is created if extended description exists, otherwise processing moves to the next hazmat record
[Create H2 Segment with Extended Description]
The system creates an H2 segment with identifier 'H2' and the extended description → The H2 segment is formatted, sequence numbered, and inserted into the EDI transmission database
[Set H2 Identifier]
The system sets up the segment identifier → The system should assign 'H2 ' as the segment identifier
[Move Hazmat Description to H2 Segment]
The system processes hazardous material description data → The system should move the hazardous material description from the source occurrence to the H2 segment description field
[Replace Underscores with Spaces]
The system formats the segment for transmission → The system should replace all underscore characters with spaces in the H2 segment
[Insert H2 Segment into Transmission]
The system completes H2 segment processing → The system should move the H2 segment to transmission data and insert it into the EDI transmission structure
[Process Vehicle Identification for Idler]
Vehicle identification processing is required → The system executes the VID segment processing routine to handle vehicle identification data for the idler manifest
[Process Commodity Description for Idler]
Commodity description processing is required → The system executes the N10 segment processing routine to handle commodity description data for the idler manifest
[Process Hazardous Material for Idler]
Hazardous material processing is required → The system executes the H1-H2 segment processing routine to handle hazardous material data for the idler manifest
[Process Vehicle Data for Follower]
The system processes vehicle-related segments for the follower → Vehicle identification data is processed and added to the EDI transmission
[Process Commodity Data for Follower]
The system processes commodity-related segments for the follower → Commodity descriptions and classifications are processed and added to the EDI transmission
[Process Hazmat Data for Follower]
The system processes hazardous materials segments for the follower → Hazmat classifications and descriptions are processed and added to the EDI transmission
[Is Vessel Name ends with 'T'?]
The system processes the M10 segment for vessel identification → The system uses the secondary vessel name for M10-05-VESSEL-NAME field instead of the primary vessel name
[Use Secondary Flight/Voyage Number for M10-06]
The system processes the M10 segment for flight/voyage number → The system uses the secondary flight/voyage number for M10-06-FLIGHT-VOYAGE-NUM field instead of the primary flight/voyage number
[Use Primary Vessel Name for M10-05]
The system processes the M10 segment for vessel identification → The system uses the primary vessel name for M10-05-VESSEL-NAME field
[Use Primary Flight/Voyage Number for M10-06]
The system processes the M10 segment for flight/voyage number → The system uses the primary flight/voyage number for M10-06-FLIGHT-VOYAGE-NUM field
[Set Prefix to 101]
The transaction type is GCX101 → The transmission prefix should be set to 101
[Set Prefix to 106]
The transaction type is GCX106 → The transmission prefix should be set to 106
[Set Prefix to 107]
The transaction type is GCX107 → The transmission prefix should be set to 107
[Set Prefix to 111]
The transaction type is GCX111 → The transmission prefix should be set to 111
[Set Prefix to 113]
The transaction type is GCX113 → The transmission prefix should be set to 113
[Set Default Prefix to 998]
The transaction type is not GCX101, GCX106, GCX107, GCX111, or GCX113 → The transmission prefix should be set to default value 998
[Generate Transmission Number Using Machine Time]
The transmission number needs to be generated → The system should use the machine time from the common control block to create the transmission number
[Set Action Code to LOG-CARGO-SENT-AUTOMATICALLY]
The system sets the action code for the log entry → The action code is set to LOG-CARGO-SENT-AUTOMATICALLY to indicate automatic cargo transmission
[Set Cargo CCN Key]
The system sets the cargo identifier → The cargo CCN key from GCWS309-US-CCN-KEY is assigned to GCX105-TRAIN-OR-US-CCN
[Set Security Level to High]
The system sets the security level → The security byte is set to HIGH-VALUE to indicate high security level
[Set Cargo Type to US-CARGO]
The system sets the cargo type indicator → The cargo type is set to GCX105-US-CARGO to indicate US cargo classification
[Set Sending Transaction ID]
The system sets the sending transaction identifier → The transaction code from CC-TRANS-CODE is assigned to GCX105-SENDING-TRANSACTION
[Set User ID from System]
The system sets the user identification → The ACF2 user ID from CC-ACF2-USERID is assigned to GCX105-ACF2-ID
[Format Current Date]
The system formats the current date → The date is formatted by concatenating CC-MACHINE-CENTURY and CC-MACHINE-DATE-X into GCX105-DATE
[Set Current Time]
The system sets the current time → The machine time from CC-MACHINE-TIME-X is assigned to GCX105-TIME
[Prepare Log Message]
The system prepares the message for transmission → The GCX105-INPUT is moved to GCT1051E-MSG and CC-ACCEPT-STATUS is set to spaces
[Runtime Environment?]
The system checks the runtime environment → If IS-RUNNING-IN-BPE is true, use EXCI interface; otherwise use CIMS interface
[Send via EXCI Interface]
The system sends the message via EXCI interface → The message is transmitted using CSIEXCI call with GCT1051E transaction name and proper error handling
[Send via CIMS Interface]
The system sends the message via CIMS interface → The message is transmitted using CIMS calls with CHNG, WRITMSGL, and PURG operations
[Update EDI Sent Electronic Flag]
The system processes the manifest transmission → The EDI sent electronic flag should be set to true AND the manifest record should be updated in the database
[Update EDI Sent Electronic Flag]
If whether to update the EDI sent electronic flag → The EDI sent electronic flag update should be skipped for this transmission type
[Set Amendment Status]
The system updates the manifest status after transmission → The manifest status should be changed from preliminary to amendment AND the manifest record should be updated in the database
[Set Preliminary Status]
The system updates the manifest status after transmission → The manifest status should be changed from amendment to preliminary AND the manifest record should be updated in the database
[Check Processing Action]
If whether to proceed with status updates → The status update process should be skipped and processing should exit
[Determine Transaction Type]
If the transaction type flags (GCX101, GCX106, GCX107, GCX111, GCX113) → The corresponding transmission prefix is set (101, 106, 107, 111, 113, or default 998)
[Set Transmission Prefix 101 GCX101 Transaction]
The transaction type is identified as GCX101 → The transmission prefix is set to 101
[Set Transmission Prefix 106 GCX106 Transaction]
The transaction type is identified as GCX106 → The transmission prefix is set to 106
[Set Transmission Prefix 107 GCX107 Transaction]
The transaction type is identified as GCX107 → The transmission prefix is set to 107
[Set Transmission Prefix 111 GCX111 Transaction]
The transaction type is identified as GCX111 → The transmission prefix is set to 111
[Set Transmission Prefix 113 GCX113 Transaction]
The transaction type is identified as GCX113 → The transmission prefix is set to 113
[Set Default Prefix 998 Unknown Transaction]
The transaction type does not match any known types (GCX101, GCX106, GCX107, GCX111, GCX113) → The transmission prefix is set to default value 998
[Generate Transmission Number Using Machine Time]
The system needs to create a unique transmission identifier → The machine time is used to generate the transmission number
[Set Transaction Set to '309']
The transaction set field needs to be populated → The transaction set is set to '309' indicating EDI manifest transaction type
[Set Read/Delete Flag to Spaces]
The read and delete flag field needs to be set → The flag is set to spaces indicating a new active record
[Attempt Database Insert GCSA9RT Record]
The system attempts to insert the record into GCSA9RT database → The database insert operation is executed
[Increment Transmission Number]
The system needs to generate a new unique number → The transmission number is incremented by 1
[Retry Database Insert]
The system retries the database insert → A new insert attempt is made with the updated transmission number
[Prepare Dependent Segment Data]
The system initiates segment data preparation → The dependent segment area is cleared to spaces and transmission data structure is initialized
[Set Sequence Number]
The system needs to assign a sequence number → The sequence number is incremented by 1 and assigned to the segment
[Move Segment Data to Transmission Buffer]
The system needs to transfer data to transmission buffer → The formatted segment data is moved to the transmission data field
[Call Database Insert Function]
The system needs to store the segment in the database → The Z1010-ISRT-GCSA9DP function is called to Execute the database insertion
[Insert EDI Segment into GCSA9DP Database]
The system executes the database insert operation → The EDI segment data is inserted into GCSA9DP database using CIMS ISRT operation with dependent segment and unqualified SSA
[Segment Successfully Inserted]
The database insert operation completes successfully → The system exits the insert procedure and returns control to the calling process
[Set Transmission Number]
GCT109 transaction parameters are being set → The transmission number is assigned to GCT109 input parameters for transaction correlation
[Prepare GCT109 Message]
The system prepares the transaction message → GCT109 input is moved to message structure and accept status is cleared
[Spawn via CIMS Interface]
GCT109 transaction execution is initiated → Transaction is executed via CIMS calls for message handling and purging
[Set Manifest Type Code to 'Y']
The action type is ADD → The manifest type code should be set to 'Y' and conditional response code should be set to 'Y'
[Set Manifest Type Code to 'Y']
The action type is DELETE → The manifest type code should be set to 'Y'
[Keep Base Manifest Type Code]
No special action or transmission type conditions are met → The manifest type code should remain as the base value from GCUSRT-M1009-MANIF-TYP-CDE
[SW-PROCESS-EDI-SEND Flag Set?]
The system checks the EDI send processing flag → Processing continues to action type evaluation if flag is set to true, otherwise processing is skipped
[Action Type Evaluation]
The action type is GCWS309-ACT-PRELIMINARY → The system routes the request to preliminary processing (A200-PROCESS-PRELIMINARY)
[Action Type Evaluation]
The action type is GCWS309-ACT-UPDATE AND the transmission type is one of GCX111, GCX106, GCX113, GCX101, or GCX107 → The system routes the request to update processing (A500-PROCESS-UPDATE)
[Action Type Evaluation]
The action type is GCWS309-ACT-DELETE → The system routes the request to delete processing (A400-PROCESS-DELETE)
[Action Type Evaluation]
The action type is GCWS309-ACT-ADD → The system routes the request to add processing (A300-PROCESS-ADD)
[Transaction Type GCX101?]
The transaction type is GCX101 → The transmission prefix code should be set to 101
[Transaction Type GCX106?]
The transaction type is GCX106 → The transmission prefix code should be set to 106
[Transaction Type GCX107?]
The transaction type is GCX107 → The transmission prefix code should be set to 107
[Transaction Type GCX111?]
The transaction type is GCX111 → The transmission prefix code should be set to 111
[Transaction Type GCX113?]
The transaction type is GCX113 → The transmission prefix code should be set to 113
[Assign Default Prefix Code 998]
The transaction type is not GCX101, GCX106, GCX107, GCX111, or GCX113 → The transmission prefix code should be set to 998 as the default value
[Generate Transmission Number Using Machine Time]
The transmission number generation process is executed → The transmission number should be set to the current machine time value from the system
[Is Vessel Name Train Export? Check position 23 = 'T']
The system processes vessel name for M10 segment AND position 23 of the vessel name equals 'T' → The system identifies this as a train export vessel
[Use Secondary Vessel Name RT36-VESSEL2-NAME]
Vessel name position 23 equals 'T' AND transport type is export AND secondary vessel name is available → The system uses RT36-VESSEL2-NAME as the vessel name for M10 segment
[Use Secondary Flight/Voyage Number RT40-FLIGHT-VOYAGE-NUM]
The system processes flight/voyage number for the secondary vessel → The system uses RT40-FLIGHT-VOYAGE-NUM as the flight/voyage number for M10 segment
[Use Primary Vessel Name M1005-VESSEL-NAME]
Vessel is not train export:
transport type is not export
secondary vessel name is not available
→ The system uses M1005-VESSEL-NAME as the vessel name for M10 segment
[Use Primary Flight/Voyage Number M1006-FLIGHT-VOYAGE-NUM]
The system processes flight/voyage number for the primary vessel → The system uses M1006-FLIGHT-VOYAGE-NUM as the flight/voyage number for M10 segment
[Set Vessel Name in M10 Segment]
The system populates the M10 segment with vessel information → The selected vessel name is moved to M10-05-VESSEL-NAME field
[Set Flight/Voyage Number in M10 Segment]
The system populates the M10 segment with voyage information → The selected flight/voyage number is moved to M10-06-FLIGHT-VOYAGE-NUM field
[Set Conditional Response Code to 'Y']
The transmission type is GCX106 AND the action is ADD → The conditional response code should be set to 'Y'
[Set Manifest Type Code to 'Y']
The action is ADD → The manifest type code should be set to 'Y'
[Use Standard Conditional Response Code from GCUSRT-M1011-COND-RESP-CDE]
The transmission type is NOT GCX106:
the action is NOT ADD
→ The conditional response code should be taken from GCUSRT-M1011-COND-RESP-CDE
[Set Manifest Type Code to 'Y']
The transmission type is GCX111:
GCX113
GCX107
→ The manifest type code should be set to 'Y'
[Set Record Type to 'CARGO']
The record type needs to be assigned for the M10 segment → The record type should be set to 'CARGO' to identify this as cargo manifest data
[Use Secondary Vessel Name for Train Export]
The system processes the M10 segment vessel information → The secondary vessel name and flight/voyage number should be used instead of the primary vessel information
[Use Primary Vessel Name]
The system processes the M10 segment vessel information → The primary vessel name and flight/voyage number should be used
[Set Vessel Name to 'TRAIN' and Set Manifest Type Code to 'P']
The system processes the M10 segment for train returned goods → The vessel name should be set to 'TRAIN' AND the manifest type code should be set to 'P' for preliminary
[Create LX Segment]
The system needs to create a line assignment segment → An LX segment is created with proper formatting and identifier
[Increment Line Counter by 1]
The system processes the line assignment → The assigned number counter is incremented by 1
[Set Line Number to 00001]
The system assigns the line number → The line number is set to 00001
[Insert LX Segment to Database]
The system processes the segment for storage → The LX segment is inserted into the transmission database
[Is Update Transaction?]
If the transaction type → If the transaction is an update operation, a second LX segment is required, otherwise processing is complete
[Create Second LX Segment]
The system creates the second line assignment segment → A second LX segment is created with proper formatting
[Increment Line Counter by 1]
The system processes the second line assignment → The assigned number counter is incremented by 1
[Set Line Number to 00002]
The system assigns the second line number → The line number is set to 00002
[Insert Second LX Segment to Database]
The system processes the second segment for storage → The second LX segment is inserted into the transmission database
[Generate Transmission Number]
The transmission type is determined (GCX101=101, GCX106=106, GCX107=107, GCX111=111, GCX113=113, or default=998) → Set the transmission prefix to the corresponding number and use machine time as the transmission number
[Process M13 Amendment - DELETE]
The action is UPDATE and switch is set to M13-DELETE-MODE → Set the amendment type code to 'D' for deletion
[Process M13 Amendment - ADD]
The action is UPDATE and switch is set to M13-ADD-MODE → Set the amendment type code to 'A' for addition
[Process M13 Amendment - DELETE]
The action is DELETE → Set the amendment code to '02', otherwise if action is UPDATE or ADD, set amendment code to '03'
[Log Transaction]
All amendment segments have been created → Log the transmission with action code for cargo sent automatically including CCN, transaction details, user ID, date and time
[Spawn Follow-up Processing]
The transmission is ready for further processing → Spawn GCT109 transaction with the transmission number for follow-up processing
[Process N1 Entity Identification]
System processes N1 entity data including entity ID code, name, ID code qualifier, and ID code → N1 segment is created and inserted into EDI transmission data
[Process N3 Address Information]
System processes address information including primary and secondary address lines → N3 segment is created and inserted into EDI transmission data
[Process N4 City State Postal]
System processes geographic information including city name, state/province code, postal code, and country code → N4 segment is created and inserted into EDI transmission data
[Process PER Contact Information]
System processes contact information with function code 'IC', contact name (limited to 23 characters), communication number qualifier, and communication number → PER segment is created and inserted into EDI transmission data
[Continue to Next Entity]
System checks if broker is unknown, not required, or office code equals '99' → Final entity record is processed if conditions met, otherwise broker processing is performed
[Entity ID Code = 'SH' Shipper?]
The entity ID code equals 'SH' indicating a shipper entity → The system triggers customer validation processing for the shipper
[Continue Processing]
The entity ID code != 'SH' → The system continues normal processing without triggering customer validation
[Send Customer Validation Request]
The transmission type is GCX106 → The system exits customer validation without processing
[Create Broker N1 Segment]
The system creates the broker N1 segment → The segment is initialized with spaces, sequence number is incremented, entity ID is set to 'CB', and broker short name is populated from cargo record
[Set Entity ID to 'CB']
The entity identification code needs to be set → The entity ID code is set to 'CB' indicating customs broker
[Set Broker Short Name]
The broker name field needs to be populated → The broker short name is retrieved from the cargo record RT01 field and assigned to the N1 name field
[Set ID Code Qualifier to '17']
The ID code qualifier needs to be set → The ID code qualifier is set to '17' as per EDI standards for broker identification
[Retrieve Broker Data]
The system processes the lookup results → The table segment data is moved to the broker segment structure for further processing
[Set Empty Broker Data]
The system processes the failed lookup → The broker segment is set to spaces indicating no broker data available
[Complete N1 Segment]
The segment needs to be finalized → All underscore characters in the segment are replaced with spaces and the segment is moved to transmission data
[Insert Broker Segment]
The segment needs to be added to the EDI transmission → The Z1010-ISRT-GCSA9DP procedure is performed to insert the segment into the transmission
[Generate ABI Routing Message]
An ABI routing message needs to be generated → If alternative US code was used, message includes alternative code with filer and office codes; otherwise message includes district code with filer and office codes, and the message is sent via GCT105 transaction
[Look up Broker Information in Table]
The system looks up broker information in the BK table using the broker short name and location ID combination → The system retrieves the broker segment data including alternative US code information
[Create ABI Routing Code Message]
The system creates the message content → The message is formatted as 'ABI ROUTING CODE ' followed by the constructed routing code
[Send Broker Notification Transaction]
The system processes the broker notification → The notification transaction GCT1051E is submitted through the appropriate processing environment (BPE or TPE)
[Execute CIMS Call]
An external transaction needs to be spawned → The system executes CIMS call, sends message via WRITMSGL, and purges the transaction
[Calculate Communication Length]
Communication length needs to be determined → Communication length is calculated as message length plus 4 bytes for header
[Prepare Message Data]
Message data needs to be prepared for transmission → Message data is moved to EXCI communication area and call data length is calculated as header length plus message length
[Set Transaction Change Mode]
The system needs to set up transaction change mode → The CIMS call is executed with CHNG mode using CCCOM control block and ALT-PCB message queue
[Write Message to Log]
The WRITMSGL operation is called → The message is written with message code, message text, message length, and module name to the ALT-PCB queue
[Execute Purge Operation]
The system needs to clear the message queue → The CIMS call is executed with PURG mode using CCCOM control block and ALT-PCB to purge the queue
[Setup CIMS Parameters]
The runtime environment is BPE (Batch Processing Environment) → Use EXCI (External CICS Interface) for transaction processing, otherwise use standard CIMS calls
[In-Bond Type Code Empty?]
The in-bond type code from GCUSRT-M1201-IN-BOND-TYP-CDE is spaces → Set the EDI in-bond type code to spaces without further conversion
[Search CP Rail to EDI Conversion Table]
The system searches the GCSUSS99-M1201-ARRAY conversion table for the CP Rail code → The system locates the matching entry in the conversion table or determines no match exists
[Get Corresponding EDI Code from Table]
The GCSUSS99-M1201-CPRAIL-VALUE matches the input code → Assign the corresponding GCSUSS99-M1201-EDI309-VALUE to the M12 EDI segment
[Apply Converted EDI Code to M12 Segment]
The processed code is ready for EDI transmission → Move the processed in-bond type code to M12-01-IN-BOND-TYP-CDE field in the M12 segment
[FDA References Found During N9 Processing?]
A reference number qualifier equals 'ZZ' and the reference number starts with '2K FDA':
the reference number qualifier equals '2K'
→ The system sets the FDA shipment indicator to TRUE for subsequent customs processing
[Assign FDA Indicator to M12-12-FDA-IND Field]
Processing the M12 customs segment for EDI transmission → The system assigns the FDA shipment indicator value to the M12-12-FDA-IND field in the customs data
[Create VC Segment]
The system creates a VC segment → The system assigns a sequence number, sets the VC identifier, populates the vehicle ID number and factory car order number from the current occurrence data, and inserts the segment into the transmission
[Look up Broker in Table]
The system performs a broker table lookup using table ID 'BK' and concatenated broker name with location ID → The system retrieves the broker segment data and makes alternative US code information available for subsequent processing
[Alternative US Code Available?]
The system checks if the broker alternative US code field contains data (not spaces) → The system selects either alternative US code path or default code combination path for broker ID construction
[Generate Broker N1 Segment]
The system generates the broker N1 segment → The system creates N1 segment with entity ID 'CB', broker short name, ID code qualifier '17', and the constructed broker ID code
[Generate Broker N1 Segment]
The system creates the ABI routing code message → The system generates message with 'ABI ROUTING CODE ' prefix followed by the appropriate code combination (alternative US code or district code with filer and office codes)
[Create ABI Routing Code Message]
The system creates the ABI routing code message → The message content includes 'ABI ROUTING CODE ' followed by the alternative US code, filer code, and office code
[Create ABI Routing Code Message]
The system creates the ABI routing code message → The message content includes 'ABI ROUTING CODE ' followed by the district code, filer code, and office code
[Prepare Message for Broker Notification]
The system prepares the message for broker notification → The message includes action code 'ZZZ', US cargo designation, sending transaction 'GCCS309', user ID, current date and time
[Send Message via External Transaction]
The system sends the message via external transaction → If running in BPE environment, use EXCI transaction call; otherwise use CIMS message processing
[Process N1 Entity Identification]
System processes N1 entity identification segment → N1 segment is created with entity ID code, name, ID code qualifier, and ID code, and customer validation is performed if entity is a shipper
[Process N3 Address Information]
System processes N3 address segment → N3 segment is created with primary address information and secondary address information
[Process N4 City/State/Postal]
System processes N4 location segment → N4 segment is created with city name, state/province code, postal code, and country code
[Process PER Contact Information]
System processes PER contact segment → PER segment is created with contact function code 'IC', contact name (first 23 characters), communication number qualifier, and communication number
[Process N1 Entity Identification]
Entity ID code equals 'SH' (shipper) → System invokes customer validation process for the shipper entity
[Search CP Rail Lookup Array]
The system needs to convert CP Rail in-bond type code to EDI format → Search the GCSUSS99-M1201-ARRAY lookup table using the CP Rail in-bond type code as the search key
[Convert to EDI Format Code]
The system performs the code conversion → Convert the CP Rail code to its corresponding EDI format code using the GCSUSS99-M1201-EDI309-VALUE from the lookup table
[Assign Converted Code to M12 Segment]
The system builds the M12 EDI segment → Assign the processed in-bond type code to the M12-01-IN-BOND-TYP-CDE field in the EDI segment
[Set FDA Indicator = 'Y' in M12-12-FDA-IND]
FDA indicator assignment is performed for the M12 segment → FDA indicator field M12-12-FDA-IND is set to the value of WS-FDA-SHIPMENT-IND flag
[Set Status to 'E' - Empty]
The cargo manifest has the empty equipment flag set to true → The vehicle load/empty status code should be set to 'E' indicating empty equipment
[Set Status to 'L' - Load]
The bill of lading type code equals 23:
environmental threshold conditions are detected
→ The vehicle load/empty status code should be set to 'L' indicating loaded equipment
[Continue with Default Status]
The bill of lading type code is not 23 AND no environmental threshold conditions are detected → The vehicle load/empty status code should remain at its default value without modification
[Create VC Segment]
The system creates a VC segment for EDI transmission → A VC segment is initialized with spaces, sequence number is incremented, and VC identifier is set
[Set Vehicle ID Number]
The system populates vehicle identification information → Vehicle ID number from occurrence data is moved to VC segment vehicle ID field
[Set Factory Car Order Number]
The system populates factory car order information → Factory car order number from occurrence data is moved to VC segment factory car order field
[Format VC Segment Data]
The system formats the segment for transmission → All underscore characters in the VC segment are replaced with space characters
[Insert VC Segment to Transmission]
The system adds the segment to transmission data → VC segment is moved to transmission data area and inserted into EDI transmission structure
[Load Commodity Description Data]
The system loads description data → Long description is moved from GCUS-N1002-LONG-DESC if available, otherwise from GCUS-N1002-FREE-FORM-DESC first occurrence, and additional description data is loaded from GCSUSS10 and GCSUSS12 segments
[Process STC Container Logic]
The system processes the container description → The appropriate standard container text is added: 'IN 20FT CNTR SAID TO CONTAIN' for 20ft, 'IN 40FT CNTR SAID TO CONTAIN' for 40ft, 'IN 45FT CNTR SAID TO CONTAIN' for 45ft, 'IN 48FT CNTR SAID TO CONTAIN' for 48ft, or 'IN 53FT CNTR SAID TO CONTAIN' for 53ft containers
[Create First N10 Segment]
The system creates the primary N10 segment → For manifest idler, quantity is set to '000000000000000', otherwise for office code '99' the total quantity is calculated from all occurrences, otherwise the first occurrence quantity is used, and the segment includes description, marks, commodity code, customs value, weight, country code, and line release number
[Loop Through Additional Segments 2-12]
The system processes additional description segments → For each segment from 2 to 12, if description data or marks data is not spaces, an N10 segment is created with quantity '0000000000', the description text (or '.' if empty), and marks text (or '.' if empty)
[Loop Through Extended Segments 13-500]
The system processes extended description segments → For each segment from 13 to 500, if description data is not spaces, an N10 segment is created with quantity '0000000000', the description text, and marks set to '.'
[Create First N10 Segment]
The system processes multi-line release numbers → Additional N10 segments are created for each line release number occurrence, using the same description and marks from the first segment, with quantity from each occurrence or '0000000000' if quantity is spaces, and including commodity codes when available
[Set Total Quantity in N10 Segment]
The system prepares the N10 segment for transmission → The total quantity is moved to the N10 quantity field, replacing leading spaces with zeroes
[Commodity Code Available?]
The system checks if commodity code qualifier is not spaces → If commodity code qualifier is available, both harmonized commodity code and commodity code qualifier should be added to the N10 segment
[Add Commodity Code and Qualifier]
The system processes the N10 segment → The harmonized commodity code should be moved to N10 commodity code field and the commodity code qualifier should be moved to N10 commodity code qualifier field
[Insert N10 Segment to Database]
The system inserts the N10 segment → The N10 segment should be inserted into the database with underscores replaced by spaces
[Extract Hazmat Code, Extract Hazmat Description, Extract Hazmat Contact Info]
Creating H1 segment for hazmat transmission → Extract hazmat code to H1-01, hazmat description to H1-04, and contact info to H1-05
[Create H1 Segment, Insert H1 Segment to Transmission]
Processing hazmat occurrence for EDI transmission → Create H1 segment with identifier 'H1 ', populate fields, replace underscores with spaces, and insert into transmission
[H2 Description Available?]
Checking for additional hazmat description data → Process H2 segment if H201 hazmat description field is not empty
[Extract Additional Hazmat Description, Create H2 Segment, Insert H2 Segment to Transmission]
Processing H2 segment for current hazmat occurrence → Create H2 segment with identifier 'H2 ', populate description field, replace underscores with spaces, and insert into transmission
[Increment Sequence Number]
Sequence numbering is required for EDI transmission → The sequence number counter is incremented by 1 and assigned to the segment
[Set LX Identifier]
EDI segment identifier needs to be set → The segment identifier is set to 'LX ' with trailing space
[Increment Assigned Number Counter]
Line item numbering is required → The assigned number counter is incremented by 1
[Store LX Segment Data]
Segment data needs to be prepared for transmission → The LX segment is moved to the transmission data area
[Insert LX Segment to Database]
Segment needs to be stored for EDI transmission → The segment is inserted into the GCSA9DP database table
[Set Amendment Code '02' for Delete]
The system assigns amendment codes → The amendment code is set to '02'
[Set Amendment Code '03' for Add/Update]
The system assigns amendment codes → The amendment code is set to '03'
[Process Vehicle Data for Follower]
The system processes the follower manifest data → The VID segment processing is performed for the follower manifest
[Process Commodity Data for Follower]
The system continues processing the follower manifest data → The N10 segment processing is performed for the follower manifest
[Process Hazmat Data for Follower]
The system continues processing the follower manifest data → The H1-H2 segment processing is performed for the follower manifest
[Is Transaction Type GCX106?]
The transmission type is GCX106 → Customer validation processing should be skipped and control should return immediately
[What is Processing Action Type?]
The processing action type is UPDATE → The action code should be set to 'UPD' for customer validation
[Send Customer Validation Request]
All validation data is ready for submission → The customer validation request should be sent to the processing system based on the runtime environment
[Set Delete Amendment Type Code]
The system assigns amendment type codes → The delete amendment type code (88-GCUS-M1303-DEL-A-BOL) is set to true and action code is cleared to spaces
[Set Add Amendment Type Code]
The system assigns amendment type codes → The add amendment type code (88-GCUS-M1303-ADD-A-BOL) is set to true and action code is cleared to spaces
[Determine Transaction Type]
The system determines the transaction type from GCWS309 flags → The appropriate transmission prefix is assigned: 101 for GCX101, 106 for GCX106, 107 for GCX107, 111 for GCX111, 113 for GCX113, or 998 for any other type
[Generate Transmission Number Using Machine Time]
The system needs to create a unique transmission identifier → The transmission number is set to the current machine time value from the system
[Retry Database Insert]
The system detects the insert was unsuccessful with a non-space status code → The transmission number is incremented by 1 and the database insert is retried until successful
[Set Transaction Set to 309]
The system sets up the transaction identification → The transaction set field is set to '309' to identify this as a cargo manifest EDI transaction
[Retrieve Lead Manifest by CCN]
The system attempts to retrieve the lead manifest data → The lead manifest record is fetched using the CCN as the search key with all cargo data segments
[Process Vehicle Information]
The manifest is being processed as part of idler handling → Vehicle identification segments are generated and added to the EDI transmission
[Process Commodity Descriptions]
The manifest is being processed as part of idler handling → Commodity description segments are generated with proper formatting and container logic applied
[Process Hazardous Materials]
The manifest is being processed as part of idler handling → Hazardous materials segments are generated for the EDI transmission
[Is Transaction Type GCX106?]
The transmission type is GCX106 → Customer validation processing is skipped and control exits immediately
[What is Processing Action Type?]
The processing action type is UPDATE → The action code 'UPD' is assigned for customer validation
[Send Customer Validation Request]
All validation parameters are set → The customer validation request is sent to the processing system for validation
[Setup EXCI Transaction]
An external transaction needs to be processed → The system sets up EXCI transaction name, calculates communication length, and prepares message data for EXCI processing
[Calculate Communication Length]
Communication parameters need to be established → The system computes EXCI-COMM-LL as message length plus 4 and EXCI-CALL-DATA-LEN as header length plus message length
[Setup CIMS Transaction]
An external transaction needs to be processed → The system calls CIMS service with CHNG function, followed by WRITMSGL for message logging, and CIMS with PURG function
[Call CIMS Service]
CIMS services are invoked → The system sequentially calls CIMS with CHNG function, WRITMSGL with message parameters, and CIMS with PURG function

Structural Validations

[Check if Cargo Pending/Error Status]
The cargo status is RT10 cargo pending:
RT10 cargo error
→ The system sets the flag to skip EDI processing
[Is Cargo Pending/Error?]
The cargo status is RT10 CPCARGO pending:
RT10 CPCARGO error
→ The system sets the flag to prevent EDI processing
[Is Bill Owner CPRS?]
The bill owner is not CPRS → The system sets the flag to prevent EDI processing
[Is Country Code CA, US, or MX?]
The country code is CA, US, or MX → The original country code is retained and used for the M10 segment
[Process M13 Amendment Segment]
The amendment code is spaces, low-values, or high-values → The system assigns default amendment code '01'
[Call Table Service GCCTBIO - Execute table lookup service with function code, key values, and return flag processing including error handling]
The system needs to retrieve broker information for EDI transmission processing → The system calls the table service with function code GU, constructs a table key using broker name and location, retrieves broker segment data if successful, or sets broker segment to spaces if lookup fails
[Return Flag = '0'?]
Processing the result of the broker table lookup → If return flag equals '0', move the retrieved table segment to broker segment structure, otherwise set broker segment to spaces indicating no data found
[Process General Reference Numbers]
The reference number data is spaces or contains not-required values, except for FEN value with immediate export at Laredo location → The reference number processing is skipped and moves to the next reference
[Check EDI Status]
The EDI status is NULL or MANUAL → The system exits deletion processing without performing any operations
[Replace Underscores with Spaces]
The segment needs to be formatted for EDI transmission → All underscore characters in the P4 segment should be replaced with space characters
[Check if M1114-SCAC-2 ≠ 'ZZZZ']
If whether to include the second SCAC code in the M11 segment → The second SCAC code is only assigned to M11-14-SCAC if M1114-SCAC-2 is not equal to 'ZZZZ'
[Check if M1115-SCAC-3 ≠ 'ZZZZ']
If whether to include the third SCAC code in the M11 segment → The third SCAC code is only assigned to M11-15-SCAC if M1115-SCAC-3 is not equal to 'ZZZZ'
[Reference Data Available?]
The system checks if reference data is available for processing → Processing continues only if data exists and is not spaces, low-values, or specifically excluded values like FEN qualifier with immediate export at Laredo location
[N3 Address Data Available?]
N3 address data is evaluated for availability → Processing continues to address segment creation if data exists, otherwise address processing is skipped
[PER Data Available?]
The PER data field is evaluated for content → Processing continues only if PER data contains actual information and is not empty spaces
[EXCI Call Success?]
Checking EXCI response codes and status → The system considers call successful if response code is zero, response2 is zero, abend code is space, and message length is zero
[Display Error Message]
Processing EXCI error response → The system displays program name, response codes, abend code to system error output and displays error message if message pointer is not null
[Check EXCI Response Codes]
The response needs to be validated → The call is considered successful if response code is zero AND response2 code is zero AND abend code is space AND message length is zero
[Error Message Available?]
Additional error details need to be checked → The system verifies if the message pointer is not null indicating error message availability
[Display Error Message Details]
Detailed error information needs to be displayed → The system displays the error message content up to the message length to system error output
[Check Abend Code = Space?]
The EXCI abend code is evaluated → Processing continues to check message length if abend code is space, otherwise error handling is initiated
[Check Message Length = 0?]
The EXCI message length is evaluated → Transaction is marked as successful if message length equals zero, otherwise error handling is initiated
[Display Primary Error Information]
Error information needs to be communicated → Primary error details including response codes and abend code are displayed
[Error Message Pointer Available?]
The error message pointer is evaluated → Detailed error message extraction is performed if pointer is not null, otherwise failure status is set directly
[Extract Error Message from Pointer]
Detailed error information is needed → The error message content is extracted from the pointer location
[Display Detailed Error Message]
Complete error information needs to be communicated → The detailed error message is displayed to provide comprehensive error context
[Display EXCI Error Message Text]
The EXCI message pointer is not null → The system displays the EXCI error message text to the system error stream
[Check EXCI Response Codes]
The EXCI response code equals zero AND the EXCI response2 code equals zero AND the EXCI abend code equals space AND the EXCI message length equals zero → The system sets the return code to success
[Check EXCI Response Codes]
The EXCI response code is not zero:
the EXCI response2 code is not zero
the EXCI abend code is not space
the EXCI message length is not zero
→ The system sets the return code to fail
[Vehicle ID Number Present?]
The system validates the vehicle ID number → VC segment creation proceeds only if the vehicle ID number is not spaces and the vehicle data is not spaces
[Set Description to Period]
The primary description from first occurrence is empty or spaces → Set the N10 free form description field to a single period character as default value
[Clear Line Release Number]
Processing line release number assignment → Clear the line release number field by setting it to spaces
[Set Marks and Numbers to Dot if Empty]
The system creates an N10 segment → The marks and numbers field is set to '.' as a default placeholder
[Commodity Code Available?]
The commodity code qualifier field is not empty → Set both the harmonized commodity code and the commodity code qualifier in the N10 segment
[Check if Hazmat Data Exists]
The system checks for hazardous material data in the shipment records → Processing continues to hazmat segment creation if data exists, otherwise hazmat processing is skipped
[H2 Hazmat Description Available?]
The system encounters hazardous material description data in the H2 segment → The system should check if H2 hazardous material description exists and is not empty
[Record Contains Valid Data]
The record data is checked for validity → The system should verify the record contains non-empty, non-low-value data before proceeding with manifest processing
[Check retrieved record data against spaces and low-values to determine if valid cargo data exists for processing]
The system checks if the record data equals SPACES or LOW-VALUES → The record is marked as invalid and skipped from processing if it contains only spaces or low-values, otherwise it is marked as valid for EDI processing
[Set Record as Invalid]
A cargo data record equals SPACES or LOW-VALUES → The system skips processing that record and continues to the next record in the sequence
[Set Record as Invalid]
A vehicle data record equals SPACES or LOW-VALUES → The system skips processing that vehicle record and continues to the next record
[Set Record as Invalid]
A hazardous material data record equals SPACES or LOW-VALUES → The system skips processing that hazardous material record and continues to the next record
[Set Record as Valid for Processing]
A vehicle ID number is populated → The system processes that vehicle ID and generates the corresponding VC segment data
[Is Country Code CA, US, or MX?]
The country code is CA, US, or MX → The existing country code is retained and used for the M10 segment
[Insert Successful?]
The insert fails due to duplicate transmission number → The system increments the transmission number and retries the insert
[Root Record Created Successfully]
The insert is successful without errors → The root transmission record is confirmed as created and ready for dependent segments
[Transaction Successful?]
If transaction execution results → If EXCI response codes are zero, response2 is zero, abend code is space, and message length is zero, then transaction is successful; otherwise it failed
[Display Error Message]
The system processes transaction failure → Error message is displayed with EXCI response codes, response2, and abend code, and if error message pointer exists, the error message content is also displayed
[Check EDI Status]
The EDI electronic transmission status is not already set → Set the EDI electronic transmission status to true and update the cargo record
[EXCI Call Successful?]
The system checks the response codes → Transaction is successful when EXCI response is zero, response2 is zero, abend code is space, and message length is zero
[Log EXCI Error]
Response codes indicate failure or error message is present → The system displays error information including response codes and abend code, logs error message if available, and sets return code to failure status
[Validate EXCI Response]
Response validation is performed → If response code equals zero AND response2 equals zero AND abend code is space AND message length equals zero, then processing is successful, otherwise it is a failure
[Display Error Message]
Additional error information needs to be displayed → Error message content is displayed to system error output using the message length
[Set EDI Code to '??' - Unknown Code]
The search of GCSUSS99-M1201-ARRAY reaches the end without finding a match → Set the EDI in-bond type code to '??' to indicate an unknown or invalid code
[Vehicle ID Number Present?]
The system checks if the vehicle record data is not spaces AND the vehicle ID number at the current occurrence is not spaces → The system proceeds to create a VC segment if both conditions are met, otherwise skips to the next vehicle occurrence
[N3 Address Data Available?]
System checks if N3 address data is not spaces → N3 address processing proceeds if data exists, otherwise skips to N4 processing
[In-Bond Type Code Empty?]
The system processes the M12 segment for in-bond information → If the in-bond type code is empty or spaces, set the EDI code to spaces without further processing
[Set Error Code '??']
The system attempts to convert the code → Set the EDI in-bond type code to '??' to indicate an unknown or invalid code
[Check WS-FDA-SHIPMENT-IND Flag]
Reference qualifier is 'ZZ' and reference number starts with '2K FDA':
reference qualifier is '2K'
→ WS-FDA-SHIPMENT flag is set to TRUE indicating this is an FDA shipment
[Log Error Message]
Error logging is required → The system displays EXCI error details including response codes and abend code, and if error message pointer is not null, displays the error message content

As an EDI Gateway Service,
I want to orchestrate and execute all GCCS309C 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

[2:Initialize manifest data retrieval]
The system initializes manifest data retrieval → The system should fetch all manifest segments and set up data structures for processing
[Initialize Root Transmission Segment]
The system prepares the root transmission segment → The system initializes A9RT-TRANSMISSION-SEGMENT to clear any previous data
[Initialize ST segment structure]
The ST segment processing begins → The ST segment structure is initialized, sequence number is incremented by 1, and ST identifier is set to 'ST '
[Initialize P4 segment structure]
The system begins P4 segment creation → The P4 segment structure is initialized to empty values and the segment identifier is set to 'P4'
[Initialize LX segment structure]
The system begins LX segment creation → The LX segment structure is initialized to clear any previous data
[Initialize M13 segment structure]
The M13 segment processing begins → The M13 segment structure should be initialized to clear any previous data
[Initialize M11 segment structure]
M11 segment processing begins → The M11 segment structure should be initialized to clear any previous data
[Initialize M12 segment structure]
The system begins M12 segment creation → The M12 segment structure is initialized to clear any previous values
[Initialize M7 segment]
The system starts processing a group of up to 4 seals → Initialize the M7 segment structure to clear any previous data
[Initialize N10 segment]
The N10 processing begins → The N10 segment structure is initialized to empty values
[Initialize H1 Segment AND Set Full UN Number in H1-01 AND Set Last 4 Digits of UN Number in H1-01 AND Set Commodity Danger Description in H1-04 AND Clear Contact and Packing Group Fields]
The system creates H1 hazardous material segment → Initialize H1 segment, set appropriate UN number format in H1-01, set commodity danger description in H1-04, and clear contact and packing group fields to spaces
[Process H2 Description Segments AND Initialize H2 Segment AND Description Line Available? AND Set Description in H2-01]
The system processes H2 description segments → For each available description line up to 8 lines, initialize H2 segment and set description text in H2-01 field
[Initialize GCX121 Input Parameters]
The system begins transaction completion finalization → The GCX121 input parameters are initialized to default values
[Initialize N9 Segment]
The system needs to create an N9 reference segment → The N9 segment structure is initialized to clear any previous data
[Initialize M7 segment]
A new M7 segment needs to be created → Initialize M7 segment structure and set identifier to 'M7'

Core Acceptance Criteria

[1:Manifest from 66MASTER station?]
The manifest from station equals '66MASTER' → The system should exit processing immediately without performing any manifest operations
[33:Broker Notification Processing]
The notify broker flag is set to true → The system should prepare broker message with action code 'ZZZ' and spawn GCT1051E transaction
[5:Transmission Number Generation]
The transaction type is 'GCT036', 'GCT0021E', 'GCT1251E', 'GCT0111E', or other → The system should assign transmission prefix 036, 002, 125, 011, or 901 respectively
[6:Destination Address Setup]
The notify customs flag is true AND the manifest is not a pre-emanifest → The system should set destination to 309-DESTINATION-5040, otherwise set to 309-DESTINATION
[7:Root Transaction Creation]
The system creates the root transaction → The system should create transaction root with transmission number, transaction set '309', and handle duplicate transmission numbers by incrementing
[8:ST Segment Processing]
The ST segment is created → The system should create ST segment with identifier 'ST', destination address, and transaction code '309'
[9:M10 Segment Processing]
The arrival indicator is 'Y':
program name is 'GCX148'
→ The system should set manifest type code to 'A' for arrival, otherwise evaluate Canadian customs train ID and program name to set 'C' for customs or 'P' for pre-manifest, with special case of spaces for 5040 destination
[9:M10 Segment Processing]
The action code is '04', '05', or '06' AND border arrival date is not blank AND manifest is not pre-emanifest → The system should set transaction purpose code to 'CO' and set post-emanifest amendment flag to true, otherwise use the action code as transaction purpose code
[9:M10 Segment Processing]
The in-transit status is 'T' → The system should set application type to '29', otherwise set to '27'
[10:P4 Segment Processing]
The destination is 309-DESTINATION → The system should use current machine date, otherwise use border arrival ETA or calculate from waybill date plus configured days if ETA is blank
[11:LX Segment Processing]
The LX segment is processed → The system should create LX segment with identifier 'LX' and assigned number '000001'
[32:Post-Emanifest Amendment Flag?]
The post-emanifest amendment flag is set to true → The system should process the M13 amendment segment
[12:M13 Segment Processing]
The M13 segment is processed → The system should create M13 segment with SCAC 'CPRS', manifest from station name, CCN key, and amendment code '60' if blank or use existing amendment code
[13:M11 Segment Processing]
The consolidated indicator is 'Y' → The system should set bill of lading type code to 'Y', otherwise set to spaces
[13:M11 Segment Processing]
The weight unit qualifier is 'KG ' or ' KG' → The system should set weight unit code to 'K', otherwise set to 'L'
[14:N9 Reference Processing]
The in-transit status is 'T':
(status is 'L' AND origin country is not 'CA' AND table lookup is successful)
(status is 'E' AND origin country is not 'CA')
→ The system should create N9 segment with qualifier 'KD' and reference number 'IN-TRANSIT'
[18:M12 Segment Processing]
The M12 segment is created → The system should set in-bond type code to '61'
[19:R4 Port Processing]
Multiple R4 segments are created for origin, border crossing, and destination → The system should assign function codes 'O'/'J' for origin (based on destination type), '3' for border crossing, '4' for destination border, and 'E'/'R' for final destination (based on destination type)
[21:M7 Seal Processing]
Seal numbers are available in the manifest data → The system should create M7 segments with up to 4 seal numbers per segment, processing up to 20 total seal numbers
[22:N10 Description Processing]
An idler car is found in the shipment → The system should set quantity to zero for the N10 segment, otherwise use the lading quantity from the manifest
[Hazardous Material?]
The UN number is blank:
starts with 'NA'
commodity description danger field is blank
→ The system should skip hazardous material processing, otherwise process H1-H2 segments
[24:H1-H2 Hazardous Material Processing]
The destination is 309-DESTINATION → The system should use the full UN number, otherwise use positions 3-4 of the UN number
[25:Idler Car Processing]
Additional idler cars are found in the consist → The system should process VID segments for each idler car and include N10 and H1-H2 segments based on destination type and hazardous material presence
[30:Transaction Completion]
The transaction completion phase is reached → The system should finalize the EDI transaction structure
[34:Transaction Completion Notification]
The transaction completion notification is triggered → The system should spawn GCT1211E transaction with the transmission number
[Check if manifest is from 66MASTER station and exit if true]
The manifest origin station is '66MASTER' → The system should immediately exit without performing any manifest processing or transmission activities
[Continue to next process]
The manifest origin station is not '66MASTER' → The system should continue with initialization and subsequent manifest processing steps
[Call Database Access Module GCCCCIO2]
The system needs to retrieve manifest data → The system calls the GCCCCIO2 module with all required parameters including CCCOM, GCWCCIO2, manifest segments, and working storage arrays
[Move Retrieved Manifest Data to Working Storage]
Manifest data needs to be loaded into working storage → The system moves the first occurrence of GCSCCS53 data from the working storage array to the GCSCCS53 segment
[Move Additional Segment Data to Working Storage]
Additional segment data needs to be loaded into working storage → The system moves the first occurrence of GCSCCS55 data from the working storage array to the GCSCCS55 segment
[Set Action Code from Input]
The system needs to set the action code for processing → The system moves the action code from the input parameter GCWS309C-ACT-CDE to the working storage action field WS-ACTION
[Set Fetch All Segments Flag]
The system configures the database query scope → The fetch all segments flag is set to true to retrieve complete manifest information
[Call GCCCCIO2 Module]
The system needs to retrieve manifest data from the database → The GCCCCIO2 module is called with all required parameters including CCCOM, GCWCCIO2, and all segment arrays
[Move GCSCCS53 Data from Array]
The system processes the retrieved segment arrays → The first element of WS-GCSCCS53-DATA array is moved to GCSCCS53 segment
[Move GCSCCS55 Data from Array]
The system processes the retrieved segment arrays → The first element of WS-GCSCCS55-DATA array is moved to GCSCCS55 segment
[Set Prefix to 036 for GCT036]
The transaction type is 'GCT036' → The transmission prefix should be set to 036
[Set Prefix to 002 for GCT0021E]
The transaction type is 'GCT0021E' → The transmission prefix should be set to 002
[Set Prefix to 125 for GCT1251E]
The transaction type is 'GCT1251E' → The transmission prefix should be set to 125
[Set Prefix to 011 for GCT0111E]
The transaction type is 'GCT0111E' → The transmission prefix should be set to 011
[Set Prefix to 901 for Other Transactions]
The transaction type is not 'GCT036', 'GCT0021E', 'GCT1251E', or 'GCT0111E' → The transmission prefix should be set to 901
[Get Machine Time from System]
The system needs to generate a unique transmission number → The current machine time should be retrieved from the system
[Combine Prefix with Machine Time]
The system generates the transmission number → The transmission number should be created by combining the prefix with the machine time
[Set Broker EDI Address as Destination]
The broker notification flag (GCWS309C-NOTIFY-BROKER) is set to true → The system should set the broker EDI address (GCWS309C-X12-BROKER) as the work destination and log EDI address
[Pre-Emanifest Status?]
The customs notification flag (GCWS309C-NOTIFY-CUSTOMS) is true and the manifest is not a pre-emanifest (GCCC-NOT-PRE-EMANIFEST) → The system should set the destination to 309-DESTINATION-5040, otherwise set it to 309-DESTINATION
[Move Destination to ST Segment]
Processing the ST segment for EDI transmission → The system should move the work destination to the ST-01-DESTINATION field
[Evaluate Transaction Type]
If the transaction type from GCWS309C-TRANSACTION → The system assigns transmission prefix 036 for GCT036, 002 for GCT0021E, 125 for GCT1251E, 011 for GCT0111E, or 901 for any other transaction type
[Use Machine Time as Base Transmission Number]
The system creates a new transmission → The system uses the current machine time from CCCOM as the transmission number
[Set Transaction Set to '309']
The system sets up the transaction details → The system assigns '309' as the transaction set type in A9RT-TRANSACTION-SET
[Clear Read and Delete Flag]
The system configures transmission properties → The system sets A9RT-READ-AND-DELETE-FLAG to spaces to prevent automatic deletion
[Creation Successful?]
The system receives a non-space status code from CCCOM indicating failure → The system increments TRANSMISSION-NUMB by 1 and retries the creation process until successful
[Attempt to Create Root Transaction]
The system needs to create the root transaction → The system calls A200-CREATE-TRANS-ROOT to persist the transmission segment
[Notify Customs?]
The system checks if GCWS309C-NOTIFY-CUSTOMS flag is set → If customs notification is required, proceed to emanifest type check, otherwise skip to transaction type setting
[Pre-Emanifest or Post-Emanifest?]
If GCCC-NOT-PRE-EMANIFEST flag → If GCCC-NOT-PRE-EMANIFEST is true, set destination to 5040 (309-DESTINATION-5040), otherwise set destination to standard (309-DESTINATION)
[Set transaction type to '309']
The transaction type needs to be assigned → The transaction type is set to '309' in the ST-02-TRANSACTION field
[Move destination to ST-01 field]
The ST segment fields need to be populated → The WORK-DESTINATION value is moved to ST-01-DESTINATION field and '309' is moved to ST-02-TRANSACTION field
[Create ST segment in transmission]
The segment needs to be added to the transmission → The ST segment is moved to transmission data, sequence number is assigned, and the segment is created in the transmission via C200-CREATE-TRANS-DEPT
[Set SCAC code to 'CPRS']
The M10 segment is being created → The SCAC code field is set to 'CPRS'
[Set transport type code to 'R' for Rail]
The M10 segment transport type is being set → The transport type code is set to 'R' indicating rail transportation
[Set country code from manifest origin country]
The M10 segment country code is being set → The country code is set to the value from the manifest origin country field
[Set vessel name to 'TRAIN']
The M10 segment vessel name is being set → The vessel name is set to 'TRAIN'
[Set quantity to 1]
The M10 segment quantity is being set → The quantity is set to 1
[Set reference number to CCN key]
The M10 segment reference number is being set → The reference number is set to the CCN key value
[Replace underscores with spaces in segment]
The segment is being prepared for transmission → All underscore characters in the segment are replaced with spaces
[Add segment to EDI transmission]
The segment is ready for transmission → The segment is added to the EDI transmission with an incremented sequence number
[Destination Type = 5040?]
The destination type is 309-DESTINATION-5040 → The manifest type code should be cleared and set to spaces
[Set location ID from manifest from-station name]
The system sets the location identifier → The P4 location ID field is populated with the manifest from-station name
[Check destination type]
If the destination type for ETA date assignment → If destination is 309-DESTINATION, use current machine date; otherwise, use border arrival ETA logic
[Set ETA date to current machine date]
The system assigns the ETA date → The P4 ETA date is set to the concatenation of current machine century and machine date
[Calculate ETA by adding days to waybill date]
The system calculates a new ETA date → The system adds WS-DAYS-FOR-ETA to the waybill date using date calculation service and updates the border arrival ETA if successful
[Use existing border arrival ETA]
The system assigns the ETA date → The P4 ETA date is set to the existing border arrival ETA value
[Set quantity to 1]
The system sets the quantity field → The P4 quantity field is set to 1
[Clear ID code and time fields]
The system sets optional fields → The P4 ID code and time fields are set to spaces
[Add sequence number]
The system assigns sequence numbering → The sequence number is incremented by 1 and assigned to the P4 segment
[Replace underscores with spaces]
The system formats the segment for transmission → All underscore characters in the P4 segment are replaced with spaces
[Store P4 segment data]
The system prepares for transmission → The P4 segment data is moved to the transmission data field
[Create transmission department record]
The system creates the transmission record → The system calls the transmission department creation process with proper status code
[Create assigned number segment for shipment grouping]
The system processes the LX segment for shipment grouping → An LX segment is created with segment identifier 'LX' and assigned number '000001'
[Set segment identifier to 'LX']
The system sets the segment identifier → The segment identifier is set to 'LX' to comply with EDI standards
[Set assigned number to '000001']
The system assigns the line number for shipment grouping → The assigned number is set to '000001' as the first and only shipment group
[Increment sequence number]
The system processes the segment for transmission → The transmission sequence number is incremented by 1 and assigned to the segment
[Move LX segment to transmission data]
The system prepares the segment for transmission → The LX segment data is moved to the transmission data structure
[Create transmission department record]
The system creates the transmission record → A transmission department record is created for the LX segment
[Set segment identifier to 'M13']
The segment identifier needs to be set → The segment identifier should be set to 'M13'
[Set SCAC code to 'CPRS']
The carrier identification needs to be specified → The SCAC code should be set to 'CPRS' for Canadian Pacific Railway
[Set location ID from manifest from-station name]
Creating an M13 amendment segment → The location ID should be populated with the manifest from-station name
[Set BOL/WB number from CCN key]
Creating an M13 amendment segment → The BOL/WB number should be set to the CCN key value
[Amendment code exists?]
The amendment code needs to be determined → If amendment code exists and is not spaces or low-values, use the existing code; otherwise use default code '60'
[Use existing amendment code from manifest]
Creating an M13 amendment segment → The existing amendment code from the manifest should be used
[Set default amendment code to '60']
Creating an M13 amendment segment → The amendment code should be set to default value '60'
[Increment sequence number]
The segment needs to be sequenced → The sequence number should be incremented by 1
[Store M13 segment in transmission data]
The segment is ready for transmission → The M13 segment should be stored in the transmission data structure
[Create transmission department record]
The segment needs to be processed through the transmission system → A transmission department record should be created
[Set segment identifier to 'M11']
The segment identifier needs to be set → The segment identifier should be set to 'M11'
[Set BOL/Waybill number from CCN key]
Creating the M11 segment for bill of lading information → The CCN key should be assigned as the BOL/Waybill number
[Set location ID from manifest from-station name]
Creating the M11 segment location information → The manifest from-station name should be assigned as the location identifier
[Set lading quantity from manifest data]
Creating the M11 segment quantity information → The manifest lading quantity should be assigned to the M11 segment
[Set manifest unit code from quantity qualifier]
Creating the M11 segment unit information → The lading quantity qualifier should be assigned as the manifest unit code
[Set weight from manifest data]
Creating the M11 segment weight information → The manifest weight should be assigned to the M11 segment
[Set place of receipt from origin station name]
Creating the M11 segment place of receipt information → The origin station name should be assigned as the place of receipt
[Set SCAC code to 'CPRS']
Setting the primary SCAC code → The SCAC code should be set to 'CPRS'
[Clear additional SCAC fields]
Processing the M11 segment → The additional SCAC fields should be set to spaces
[Add sequence number]
The segment needs a sequence number → The sequence number should be incremented by 1 and assigned to the segment
[Replace underscores with spaces in segment]
Preparing the segment for transmission → All underscore characters should be replaced with spaces
[Store M11 segment in transmission data]
Storing the segment data → The M11 segment should be moved to the transmission data field
[Create transmission department record]
The segment is ready for transmission → A transmission department record should be created through the C200-CREATE-TRANS-DEPT procedure
[Destination Type Check]
The destination type is 309-DESTINATION-5040 → Skip ETA and CSA indicator N9 segment creation and proceed directly to previous CCN processing
[Create ETA Reference N9 Segment]
Processing N9 reference segments → Create N9 segment with identifier 'N9', reference qualifier '76', reference number 'ETD', and border arrival ETA date
[CSA Indicator Status]
The CSA indicator is on (GCCC-CSA-IND-ON is true) → Set N9 reference number to '01', otherwise set to '00'
[Access Export Destination Table]
Processing in-transit status validation → Access table with function code 'GU', table ID 'EX', and destination station number as sequence ID
[Transit Status Validation]
In-transit status is 'T', or (status is 'L' and origin country is not 'CA' and table lookup is successful), or (status is 'E' and origin country is not 'CA') → Create N9 segment with identifier 'N9', reference qualifier 'KD', and reference number 'IN-TRANSIT'
[Previous CCN Exists?]
Previous CCN (GCCC-PREV-CCN) is not spaces → Create N9 segment with identifier 'N9', reference qualifier 'XP', and previous CCN as reference number
[Loop Through Additional Previous CCNs]
Processing additional previous CCNs from index 1 to 4 → For each non-space CCN, create N9 segment with same reference qualifier 'XP' and the CCN as reference number
[Loop Through Stored N9 References]
Processing stored references from index 1 to 10 and reference qualifier is not spaces, high-values, or low-values → Create N9 segment with identifier 'N9', stored reference qualifier, and stored reference number
[In-Transit Status = 'T'?, Status = 'L' AND Origin Country ≠ 'CA' AND Table Found?, Status = 'E' AND Origin Country ≠ 'CA'?]
The system processes N9 reference segments → The system creates an N9 segment with reference qualifier 'KD' and reference number 'IN-TRANSIT'
[Destination type check]
If the destination type → The system classifies as 4040 destination if 309-DESTINATION is true, otherwise as 5040 destination
[Create N1 entity segment with ID and name]
The system creates the N1 entity segment → The system populates the N1 segment with identifier 'N1', entity ID code, entity name, ID code qualifier, and ID code from the entity record
[N3 address data exists?]
The system checks for N3 address data availability → The system proceeds to create N3 segment if address information (GCSCCS55-N3-DATA) is not spaces, otherwise skips to N4 processing
[Create N3 address segment]
The system creates the N3 address segment → The system populates the N3 segment with identifier 'N3', primary address line, and secondary address line from the entity record
[N4 city/state data exists?]
The system checks for N4 location data availability → The system proceeds to create N4 segment if location information (GCSCCS55-N4-DATA) is not spaces, otherwise continues to next entity
[Create N4 location segment with city, state, postal code, country]
The system creates the N4 location segment → The system populates city name, postal code, and country code in standard positions, but maps state/province code to position 2 for 309-DESTINATION or position 7 for other destinations
[Create Canadian Pacific Railway entity]
The system creates the railway entity segment → The system creates an N1 segment with identifier 'N1', entity ID code 'RR', and name 'CANADIAN PACIFIC RAILWAY'
[Create CPR address segment]
The system creates the CPR address segment → The system creates an N3 segment with identifier 'N3' and address '7550 OGDENDALE RD S.E.'
[Create CPR location segment]
The system creates the CPR location segment → The system creates an N4 segment with city 'CALGARY', country 'CA', postal code 'T2C 4X9', and maps province code 'AB' to position 2 for 309-DESTINATION or position 7 for other destinations
[Destination Type Check]
The system needs to validate entity information → Check if 309-DESTINATION flag is set to determine validation path - 4040 validation for 309-DESTINATION or 5040 validation for other destinations
[Process N1-N3-N4-PER Segments]
Entity processing is executed → Execute N2063-EACH-N1-N3-N4-PER procedure to create N1, N3, N4, and PER EDI segments for the entity
[Add Railway Entity - Canadian Pacific]
Standard railway entity needs to be added → Create N1 segment with entity ID 'RR' and name 'CANADIAN PACIFIC RAILWAY'
[Create Railway N3 Address Segment]
Railway address information is added → Create N3 segment with address '7550 OGDENDALE RD S.E.'
[Create Railway N4 Location Segment]
Railway location information is added → Create N4 segment with city 'CALGARY', country 'CA', postal code 'T2C 4X9', and state/province 'AB' in position 02 for 309-DESTINATION or position 07 for other destinations
[Destination Type Check]
The system checks the destination flag 309-DESTINATION → If 309-DESTINATION is true, apply 4040 validation rules, otherwise apply 5040 validation rules
[Process Entity Segments]
The entity contains valid data and meets destination requirements → The system calls N2063-EACH-N1-N3-N4-PER to create transmission segments
[Accept Complete Address]
All validation checks are successful → The system processes the entity address data for transmission
[Get Entity Record from Database]
The system processes entity records for N1-N3-N4 segment creation → Entity records are retrieved from GCSCCS55 cargo data array up to maximum sequence number
[Destination Type Check]
If the destination configuration → If 309-DESTINATION flag is set, apply 4040 validation rules, otherwise apply 5040 validation rules
[Valid N1 Code for 4040?]
If the validation result → If the entity code is valid for 4040 destination, proceed to create segments, otherwise skip the entity
[Create N1-N3-N4 Segments]
The system creates address segments → N1, N3, N4, and PER segments are created through N2063-EACH-N1-N3-N4-PER procedure
[Continue to Next Entity]
The system moves to process the next entity → Processing continues with the next entity record in the GCSCCS55 array until maximum sequence is reached
[Set in-bond type code to '61']
The system creates the M12 segment → The in-bond type code is set to '61'
[Set segment identifier to 'M12']
The system populates the segment identifier → The segment identifier is set to 'M12'
[Prepare transmission data]
The system prepares the segment for transmission → The M12 segment data is moved to the transmission data structure
[Increment sequence number]
The system assigns sequence numbering → The sequence number is incremented by 1 and assigned to the M12 segment
[Create M12 segment for customs processing]
The system creates the segment for transmission → The M12 segment is created in the transmission system for customs processing
[Set Port Function Code 'O' for Origin / Set Port Function Code 'J' for Junction]
The system checks the destination type (309-DESTINATION vs other) → If destination type is 309-DESTINATION, set port function code to 'O' (Origin), otherwise set port function code to 'J' (Junction)
[Use Manifest From Trans Code / Use Manifest To Trans Code]
The system checks the CSA indicator status → If CSA indicator is ON, use manifest from transaction code as location identifier, otherwise use manifest to transaction code as location identifier
[Set Sub-Location Code as Terminal Name]
The destination type is NOT 309-DESTINATION → Set the sub-location code as the terminal name in the R4 segment
[Set Port Function Code 'E' for Export / Set Port Function Code 'R' for Rail]
The system checks the destination type (309-DESTINATION vs other) → If destination type is 309-DESTINATION, set port function code to 'E' (Export), otherwise set port function code to 'R' (Rail destination)
[Set Destination Station State Code]
The system processes state/province codes for different destination types → For 309-DESTINATION, assign origin station state code to R4-08-PROV-STATE-CODE for origin segment, and for non-309 destinations, assign origin station state code to R4-08-PROV-STATE-CODE for origin segment and destination station state code to R4-08-PROV-STATE-CODE for final destination segment
[Set Port Function Code 'O' for Origin]
The destination type is 309-destination → The port function code should be set to 'O' for origin
[Set Port Function Code 'J' for Junction]
The destination type is not 309-destination → The port function code should be set to 'J' for junction and the origin station state code should be added to province/state code field
[Set Port Function Code '3' for Customs District]
Processing the second R4 segment for customs district → The port function code should be set to '3' and location qualifier should be set to 'CD'
[Use From-Station Trans Code]
The CSA indicator is on → The location identifier should use the manifest from-station transaction code
[Use To-Station Trans Code]
The CSA indicator is off → The location identifier should use the manifest to-station transaction code
[Set Port Function Code '4' for Destination]
Processing the third R4 segment for destination port → The port function code should be set to '4' and location qualifier should be set to 'CD'
[Add Terminal Name if Not 309-Destination]
The destination type is not 309-destination → The sub-location code should be added to the terminal name field
[Set Port Function Code 'E' for Export]
The destination type is 309-destination → The port function code should be set to 'E' for export
[Set Port Function Code 'R' for Rail]
The destination type is not 309-destination → The port function code should be set to 'R' for rail and the destination station state code should be added to province/state code field
[CSA Indicator Processing]
The system processes R4 port function code 4 segment for destination border crossing → If CSA indicator is ON, use the from-station transaction code as the location identifier, otherwise use the to-station transaction code as the location identifier
[Set Equipment Description to 'CN' - Container / Set Equipment Description to 'RR' - Rail Car]
The system checks the conveying car field in the manifest data → If conveying car field contains data, set equipment description code to 'CN' for container, otherwise set to 'RR' for rail car
[Set Equipment Initial from Manifest]
The equipment initial field is populated from manifest data → The equipment car initial from manifest is assigned to the VID equipment initial field
[Set Equipment Number from Manifest]
The equipment number field is populated from manifest data → The equipment car number from manifest is assigned to the VID equipment number field
[Set Load/Empty Status from Manifest]
The load empty status field is populated from manifest data → The load empty status from manifest is assigned to the VID load empty status code field
[Clear Seal Number Fields]
Seal number fields need to be initialized → Set both seal number fields to spaces as seal data is processed in separate segments
[Set M7 identifier]
The system needs to identify the segment type → Set the M7 identifier to 'M7 ' to indicate this is a seal number segment
[Format M7 segment]
The system prepares the segment for transmission → Replace all underscore characters with spaces in the M7 segment
[Create M7 transmission segment]
The system creates the transmission segment → Move the M7 segment to transmission data, set accept status to spaces, and Execute transmission creation
[Set lading quantity from manifest]
Processing the N10 segment for quantity data → The manifest lading quantity is assigned to the N10 quantity field
[Set shipper load and count description]
Processing the N10 segment description field → The shipper load and count data is assigned to the N10 free form description field
[Set weight unit code to 'K' for KG]
Determining the weight unit code for N10 segment → The weight unit code is set to 'K'
[Set weight unit code to 'L' for LB]
Determining the weight unit code for N10 segment → The weight unit code is set to 'L'
[Set weight unit code to 'E' for other]
Determining the weight unit code for N10 segment → The weight unit code is set to 'E'
[Set weight from manifest]
Processing the N10 segment weight field → The manifest weight value is assigned to the N10 weight field
[Set quantity to zero for idler]
Setting the quantity for the N10 segment → The quantity is set to zero regardless of the original lading quantity
[Keep original lading quantity]
Setting the quantity for the N10 segment → The original lading quantity from the manifest is retained
[Set manifest unit code]
Processing the N10 segment unit code field → The lading quantity qualifier is assigned to the N10 manifest unit code field
[Create primary N10 segment]
Creating the primary N10 transmission segment → The N10 segment is created and added to the transmission with incremented sequence number
[Extract lading description from manifest]
Processing description data for additional N10 segments → The lading description is extracted and prepared for segment creation
[Process description array]
Processing the description array for N10 segments → Each non-empty description line is identified for individual N10 segment creation
[Create additional N10 segment]
Creating additional N10 segments for description data → A new N10 segment structure is initialized for description-only content
[Set quantity to zero for description]
Setting the quantity field for the description N10 segment → The quantity is set to zero since this segment contains only descriptive text
[Set description text]
Setting the description field for an N10 segment → The description line text is assigned to the N10 free form description field
[Create description N10 segment]
Creating the description N10 transmission segment → The N10 segment is created and added to the transmission with incremented sequence number
[Create N10 segment for description]
The system processes the description content → A new N10 segment is created to hold the description data
[Set segment identifier to 'N10']
The segment identifier field needs to be populated → The segment identifier is set to 'N10' to comply with EDI standards
[Set quantity to zero]
The quantity field needs to be populated → The quantity is set to zero since this segment contains only descriptive information
[Move description text to free form description field]
The N10 segment is being populated with content → The description text is moved to the free form description field of the N10 segment
[Increment sequence number]
The segment needs to be assigned a sequence number → The sequence number is incremented by 1 to maintain proper EDI transmission ordering
[Create dependent segment in transmission]
The segment is ready for transmission → The segment is created as a dependent segment in the EDI transmission structure
[Destination Type Check]
The system processes H1 hazardous material segment → If destination is 309-DESTINATION, use full UN number in H1-01 field, otherwise use only last 4 digits of UN number
[Format Single Character Descriptions]
The system formats the H2 description field → Append a period after the single character to create proper formatting (e.g., 'A' becomes 'A.')
[Notify Customs?]
The system checks notification requirements → The system verifies that customs notification flag GCWS309C-NOTIFY-CUSTOMS is enabled
[Create VID Segment for Follower]
The system processes the follower car equipment information → The system creates a VID (Vehicle Identification) segment containing the follower car details
[Destination Type?]
If the destination configuration → If the destination is 309-DESTINATION type, the system proceeds with N10 description processing, otherwise skips to next follower
[Create N10 Description Segment]
The system processes the follower car cargo description → The system creates an N10 segment containing quantity and description information for the follower car
[Has Hazardous Material?]
The system checks for hazardous material indicators → If UN-NUMBER is not SPACES and not starting with 'NA' and commodity danger description is not SPACES, the system identifies hazardous material presence
[Create H1-H2 Hazmat Segments]
The system processes the hazardous material information → The system creates H1 and H2 segments containing the UN number, hazard class, and danger descriptions for the follower car
[Continue to Next Follower]
The system prepares for the next iteration → The system changes the database function to GN (Get Next) and returns to retrieve the next follower car
[Create VID Equipment Segment for Follower Car]
The system processes the follower car for EDI transmission → A VID segment is created with the follower car's equipment information including car initial, number, and load status
[Destination Type Check]
The system checks if the destination is 309-DESTINATION type → If 309-DESTINATION, additional N10 and hazmat segments are processed; otherwise only basic VID segment is created
[Create N10 Description Segment for Follower]
The system creates commodity description segments → An N10 segment is generated with quantity set to zero for follower cars and commodity description details
[Create H1-H2 Hazardous Material Segments for Follower]
The system processes hazardous material data → H1 segment is created with UN number and hazmat description, followed by H2 segments for additional hazmat details
[Is Follower Manifest Car?]
If the car should be included in manifest processing → The car is processed for manifest segments if it qualifies as a follower manifest car, otherwise it is skipped
[Process VID Segment for Follower]
The system processes vehicle information for the follower car → A VID segment is generated containing the follower car's equipment details
[Process N10 Description for Follower]
The system processes description and quantity information for the follower car → An N10 segment is generated containing the follower car's cargo description and quantity details
[Process H1-H2 Hazmat for Follower]
The system processes hazardous material information for the follower car → H1 and H2 segments are generated containing the follower car's hazardous material classification and description
[Store Export Destination Information]
Transit status is 'T':
(transit status is 'L' and origin country is not CA and export destination lookup is successful)
(transit status is 'E' and origin country is not CA)
→ Add reference segment with qualifier 'KD' and value 'IN-TRANSIT'
[Retrieve Station Name and State Code]
SC table record is found and Canadian station code is not 0000 → The system should retrieve and store the station segment information
[Is CCN Creation Date Numeric and Not Zero?]
The CCN creation date is not numeric or equals zero → Use current machine century and date for EDI processing
[Extract Year from CCN Creation Date]
Processing date for EDI transmission → Move CCN creation date to year-month-day format for century determination
[Call ISCDATCV Date Conversion Module]
Date conversion is required for EDI transmission → Call ISCDATCV module with function codes 2 for input and 1 for output format
[Date Conversion Successful?]
Conversion module returns success status → Use converted output date for EDI flight voyage number field
[Use Converted Date for EDI Format]
Populating EDI M10 segment → Move conversion output to M10-06-FLIGHT-VOYAGE-NUM field
[Is Border Arrival ETA empty?]
The system checks if GCCC-BORDER-ARRIVAL-ETA is empty or contains low-values → If GCCC-BORDER-ARRIVAL-ETA is spaces or low-values, proceed to calculate new ETA, otherwise use the existing GCCC-BORDER-ARRIVAL-ETA value
[Use calculated ETA date]
The system processes the calculated result → Move DTCAL-NEW-DATE to GCCC-BORDER-ARRIVAL-ETA for use in P4 segment
[Set ETA date in P4 segment]
The system builds the P4 segment for transmission → Move GCCC-BORDER-ARRIVAL-ETA to P4-02-ETA-DATE
[Override Country Code to 'CA']
The in-transit status equals the return status indicator → The country code should be overridden to 'CA' (Canada) in the R4 segment
[Keep Original Country Code]
The in-transit status does not equal the return status indicator → The original country code from the manifest should be preserved in the R4 segment
[Move Transmission Number to GCX121]
Transaction completion notification is being prepared → The transmission number is associated with the completion request parameters
[TPE Environment: Use CIMS Call]
Transaction completion needs to be executed → The system uses CIMS call mechanism with message logging and purging operations
[Calculate Communication Length]
Communication parameters need to be sized → The communication length is calculated as message length plus 4 bytes for header
[Move Message Data to Communication Area]
Message data needs to be transferred for external processing → The message data is moved to the communication area for the external call
[Set Failure Return Code]
The system needs to record the failed completion → The return code is set to failure status and error message pointer is processed if available
[Move GCX121 Input to GCT1211E Message]
Message content needs to be prepared for internal processing → The GCX121 input parameters are moved to the GCT1211E message structure
[Change Alt-PCB Status]
Message queue status needs to be updated → The alternate PCB status is changed using CIMS call
[Write Message Log Entry]
Transaction completion needs to be logged → A message log entry is written with completion details including message code, content, length, and module name
[Purge Alt-PCB]
Message queue cleanup is required → The alternate PCB is purged using CIMS call
[Check if Broker Notification Required]
The system checks the broker notification flag GCWS309C-NOTIFY-BROKER → The system should proceed to broker notification processing if the flag is true, otherwise skip broker notification
[Set Broker as Destination Address]
The system processes the broker notification setup → The system should set GCWS309C-X12-BROKER as both WORK-DESTINATION and LOG-EDI-ADDRESS
[Set Action Code to ZZZ]
The system sets up the action code for the broker message → The system should assign 'ZZZ' to GCX105-ACTION-CODE
[Set Message Content]
The system assigns message content → The system should move LOG-EDI-MESSAGE to GCX105-MESSAGE
[Set Sending Transaction ID]
The system sets the sending transaction identifier → The system should assign 'GCCS309C' to GCX105-SENDING-TRANSACTION
[Set User ID and Timestamp]
The system captures user and timing information → The system should assign CC-ACF2-USERID from CCCOM to GCX105-ACF2-ID
[Set Date and Time Information]
The system processes date and time configuration → The system should move CC-MACHINE-CENTURY and CC-MACHINE-DATE from CCCOM to WS-GCX105-CC and WS-GCX105-YYMMDD respectively, then move WS-GCX105-CCYYMMDD to GCX105-DATE and CC-MACHINE-TIME to GCX105-TIME
[Spawn GCT1051E Transaction]
The system initiates broker notification transmission → The system should Execute Z600-SPAWN-GCT1051E to execute the broker EDI transaction
[EDI Transmission Finalized]
The system needs to send completion notification → Initialize GCX121 input parameters and set security byte to high values
[Move Transmission Number to GCX121]
Preparing completion notification → Move the transmission number from A9RT-TRANSMISSION-NUMBER to GCX121-TRANSMISSION-NUMBER
[Move Input to GCT1211E Message]
Processing completion notification → Move GCX121-INPUT to GCT1211E-MSG and set CC-ACCEPT-STATUS to spaces
[Change Message Status]
Updating message status → Call CIMS using CCCOM, CHNG, ALT-PCB, and GCT1211E
[Write Message to Log]
Logging the completion notification → Call WRITMSGL using CCCOM, ALT-PCB, GCT1211E-MSG-CODE, GCT1211E-MESSAGE, GCT1211E-MSG-LGTH, and GCT1211E-MOD-NAME
[Purge Message Queue]
Finalizing completion notification → Call CIMS using CCCOM, PURG, and ALT-PCB
[Set N9 Identifier]
The system prepares the segment for transmission → The segment identifier is set to 'N9' to comply with EDI standards
[Move Reference Number Qualifier to N9-01]
The system builds the N9 segment for broker transmission → The reference number qualifier is moved to the N9-01 field of the segment
[Move Reference Number to N9-02]
The system builds the N9 segment for broker transmission → The reference number is moved to the N9-02 field of the segment
[Create N9 Segment for Broker]
The system needs to add this segment to the transmission → The segment is added to the transmission queue with an incremented sequence number and proper status code
[Add seal number 1 to M7 segment]
The system assigns the seal number to the M7 segment → Move the seal number to M7-01-SEAL-NUMBER field
[Add seal number 2 to M7 segment]
The system assigns the seal number to the M7 segment → Move the seal number to M7-02-SEAL-NUMBER field
[Add seal number 3 to M7 segment]
The system assigns the seal number to the M7 segment → Move the seal number to M7-03-SEAL-NUMBER field
[Add seal number 4 to M7 segment]
The system assigns the seal number to the M7 segment → Move the seal number to M7-04-SEAL-NUMBER field
[Create M7 segment with validated seal numbers]
The system creates the segment for transmission → Replace underscores with spaces, increment sequence number, and create transmission department record

Structural Validations

[15:N1-N3-N4 Entity Processing]
The destination is 309-DESTINATION → The system should validate N1 codes against 4040 table, otherwise validate against 5040 table and require city name, country code, and postal/state codes for US/CA addresses
[Display Database Error Message]
The system needs to handle the database error → The system sets the error message to 'UNABLE TO LOCATE MANIFEST IN DATABASE' and calls the error handler 'CERR'
[Set Error Message: Unable to Locate Manifest]
The system prepares error information for the user → The error message is set to 'UNABLE TO LOCATE MANIFEST IN DATABASE'
[Call Error Handler CERR]
The system needs to handle the error condition → The CERR error handler is called with CCCOM parameter
[Border arrival ETA exists?]
The system checks for existing border arrival ETA → If border arrival ETA is spaces or low-values, calculate new ETA; otherwise, use existing ETA
[Replace underscores with spaces in segment]
The system prepares the segment for EDI transmission → All underscore characters in the LX segment are replaced with spaces
[Replace underscores with spaces in segment]
Preparing the segment for transmission → All underscore characters should be replaced with spaces
[Set Entity Code for 4040 Validation]
Entity validation is required → Move GCCS-N101-ENTITY-ID-CDE to WS-4040-N1-CODE for validation
[Set Entity Code for 5040 Validation]
Entity validation is required → Move GCCS-N101-ENTITY-ID-CDE to WS-4040-N1-CODE for 5040 validation processing
[Default Equipment Initial to 'NONZ']
The equipment car initial field in manifest data is empty or spaces → Set the equipment initial to default value 'NONZ'
[Default Equipment Number to '00000000']
The equipment car number field in manifest data is empty, spaces, or contains zeros → Set the equipment number to default value '00000000'
[Description index > 500?]
The description index reaches or exceeds position 500 → The description expansion process terminates to prevent exceeding system limits
[Is Follower Manifested?]
The system checks the follower manifest indicator → If GCCC-FOLLOWER-MFST is true, the car is processed for EDI segments, otherwise it is skipped
[Follower Has Hazardous Material?]
The system checks for hazardous material indicators → If UN number is not spaces, not 'NA', and commodity danger description exists, hazmat segments are created
[Retrieve Station Code Entry for From-Station]
SC table entry is not found:
Canadian station code is '0000'
→ Generate error message indicating SC table entry not found for the station
[Generate Station Code Error Message]
SC table record is not found:
Canadian station code equals 0000
→ The system should Throw error: indicating SC table entry not found for the station
[Set Error Message for Invalid Date]
Date conversion fails → Set error message 'MODULE ISCDATCV SAID INPUT DATE IS INVALID' in common communication area
[Clear Date Field]
Preparing EDI segment with invalid date → Move spaces to M10-06-FLIGHT-VOYAGE-NUM field
[EXCI Call Successful?]
The system needs to determine call success → The call is considered successful if response code is zero, response2 is zero, abort code is space, and message length is zero
[Generate station not found error message]
The system needs to report the validation failure → The system generates an error message indicating the SC table entry for the station was not found

As an EDI Gateway Service,
I want to orchestrate and execute all GCCS309E 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 M10 Segment]
The system begins M10 segment processing → The M10 segment is initialized with spaces and the identifier 'M10' is set
[Initialize EDI Segment Structure]
The system begins creating the LX segment → The dependent segment structure is cleared and sequence number is incremented by 1
[Initialize M13 Segment]
The M13 segment processing begins → The system initializes the M13 segment structure, increments the sequence number, and sets the M13 identifier
[Initialize M11 Segment]
The system begins creating the M11 segment → The segment is initialized with spaces, sequence number is incremented by 1, and M11 identifier is set
[Initialize N1 Segment]
The system begins creating an N1 segment → The N1 segment structure is initialized with spaces and sequence number is incremented
[Initialize N3 Segment Structure]
The system initializes the N3 segment processing → The system should clear the dependent segment area, increment the sequence number, set the N3 identifier, and clear the N3 segment structure
[Initialize N4 Segment Structure]
The N4 segment processing begins → The N4 segment structure is initialized with spaces
[Initialize PER Segment]
The system begins PER segment creation → A new PER segment is initialized with spaces and sequence number is incremented
[Initialize VID Segment]
The system begins VID segment creation → The system clears dependent segment area, increments sequence number, initializes VID segment with spaces, and sets VID identifier
[Initialize H2 Segment Structure]
The system prepares to create an H2 segment → The dependent segment area is cleared, sequence number is incremented by 1, and H2 segment structure is initialized with spaces
[Initialize Log Message Structure]
The system begins transaction logging → The log message structure (GCX105-INPUT) is cleared and initialized to spaces
[Initialize Transaction Status]
The system prepares to submit the transaction → The acceptance status is cleared to initialize the transaction state
[Initialize Transmission Root Record]
The system begins the transmission storage process → A transmission root record is initialized with empty values, transmission number is set, transaction set is set to '309', and read-and-delete flag is set to spaces
[Initialize Description Variables]
The system begins multi-segment description processing → All description variables (WS-DESC, WS-N1002-DESC, WS-N1003-MARKS-AND-NUM, WS-N1001-TOTAL1-7) are set to spaces and WS-N1001-TOTAL8-15 is set to zero
[Initialize H2 Segment Structure]
The system begins H2 segment creation → The H2 segment structure is cleared and initialized with spaces
[Initialize Root Record]
The system prepares to create the transmission root record → The system initializes the transmission segment, sets the transmission number, assigns transaction set to '309', clears the read and delete flag to spaces, and prepares the record for database insertion
[Initialize Transmission Record]
The initialization process begins → The transmission number is set from the current transmission number, read-and-delete flag is set to spaces, and transaction set is set to '309'
[Initialize Dependent Segment Structure]
The system prepares to store the segment as a dependent record → The dependent segment structure is initialized with spaces to clear any previous data

Core Acceptance Criteria

[4:Processing Eligibility Validation]
The manifest status is RT43 CREATED AND the manifest type is FOLLOWER → Set the processing flag to prevent EDI send processing
[4:Processing Eligibility Validation]
The manifest type is M1109 MASTER → Set the processing flag to prevent EDI send processing
[4:Processing Eligibility Validation]
The cargo status is RT10 CPCARGO PENDING:
RT10 CPCARGO ERROR
→ Set the processing flag to prevent EDI send processing
[1:Main Control Flow - Action Type?]
The action type is PRELIMINARY, UPDATE with specific transmission types, DELETE, or ADD → Route to the corresponding processing section: A200 for PRELIMINARY, A500 for UPDATE with GCX111/GCX106/GCX113/GCX101/GCX107, A400 for DELETE, or A300 for ADD
[5:Preliminary Manifest Processing]
The EDI sent status is not already set to electronic → Set the EDI sent status to electronic and update the manifest record
[6:Add Manifest Processing, 8:Update Manifest Processing]
The transmission type is not GCX106 AND the EDI sent status is not already electronic → Set the EDI sent status to electronic and update the manifest record
[7:Delete Manifest Processing]
The EDI sent status is not already electronic → Set the EDI sent status to electronic and update the manifest record
[9:Transmission Number Generation]
The transmission type is GCX101, GCX106, GCX107, GCX111, or GCX113 → Assign prefix 101 for GCX101, 106 for GCX106, 107 for GCX107, 111 for GCX111, 113 for GCX113, or 998 for any other type
[10:M10 Manifest Header Processing]
The vessel name ends with 'T' AND transport type is EXPORT AND a secondary vessel name exists → Use the secondary vessel name and flight voyage number, otherwise use the primary vessel name and flight voyage number
[10:M10 Manifest Header Processing]
The action is UPDATE:
(transmission is GCX106 AND action is ADD)
(transmission is GCX111/GCX113/GCX107 AND action is DELETE)
→ Set manifest type code to 'Y'
[10:M10 Manifest Header Processing]
The vessel name ends with 'T' AND the action is PRELIMINARY → Set manifest type code to 'P'
[13:M13 Amendment Processing]
The action is DELETE:
(action is UPDATE AND in delete mode)
→ Set amendment type code to 'D', when action is UPDATE AND in add mode set to 'A', otherwise use existing amendment type code
[13:M13 Amendment Processing]
The transmission is GCX106 AND action is DELETE → Set amendment code to '02', when transmission is GCX106 AND action is UPDATE or ADD set to '03', otherwise use existing amendment code or default to '01' if empty
[14:M11 Bill of Lading Processing]
The equipment type is empty equipment → Set BOL type code to '69', otherwise set to '00'
[15:N9 OB Reference Processing]
A reference number qualifier is 'OB' → Add the OB reference to the N9 table with highest priority processing
[16:N9 BN Reference Processing]
A reference number qualifier is 'BN' AND not 'OB' → Add the BN reference to the N9 table for processing
[17:N9 General Reference Processing]
A reference number qualifier is not 'OB', 'BN', 'KCM', 'FEN', or SPACES → Create an N9 segment with the reference qualifier and number
[18:N9 Empty Residue Processing]
The BOL type code is 23 → Create an N9 segment with qualifier 'ZF' and residue description
[19:AES Data Processing]
The SED (Shipper's Export Declaration) data is not SPACES or LOW-VALUES → Create an N9 segment with the first 3 characters as qualifier and remaining 29 characters as reference number
[20:Entity Information Processing]
Entity data is not SPACES or LOW-VALUES → Create N1 segment for entity identification, N3 for address, N4 for city/state/postal, and PER for contact information when data exists
[20:Entity Information Processing]
The entity ID code is 'SNP' AND SCAC code exists → Set ID code qualifier to '02', otherwise set to '17'
[26:M12 In-bond Processing]
The movement type is US-CANADA-US, MULTI-TRANSIT, or TRANSPORT-EXPORT AND not broker bond AND M12 data exists → Process M12 in-bond segment, otherwise skip in-bond processing
[26:M12 In-bond Processing]
The internal in-bond type code exists in the mapping table → Use the corresponding EDI value from the mapping table, otherwise use SPACES
[27:VID Equipment Processing]
VID equipment data is not SPACES → Create a VID segment with equipment description, initial, number, seal numbers, and load/empty status
[28:VC Vehicle Processing]
Vehicle ID data is not SPACES or LOW-VALUES → Create VC segments for each vehicle ID number
[29:N10 Commodity Processing]
The harmonized commodity code exists AND movement type is IMMEDIATE EXPORT or TRANSPORT EXPORT → Set commodity code qualifier to 'J'
[29:N10 Commodity Processing]
The manifest is identified as an idler manifest → Set the quantity to '000000000000000'
[32:H1 Hazardous Material Processing]
H1 hazardous material data is not SPACES or LOW-VALUES → Create H1 segment with hazmat code, description, and contact information, and create H2 segment if additional description exists
[34:Idler Car Processing]
The manifest has associated idler cars linked by lead manifest CCN → Process VID, N10, and H1-H2 segments for each idler car until no more idlers are found or lead CCN changes
[Check EDI Processing Flag]
The system checks the EDI send processing flag (SW-PROCESS-EDI-SEND) → If the flag is TRUE, proceed to action type evaluation; if FALSE, skip all EDI processing
[Action Type?]
If the action type from GCWS309 → Route to PRELIMINARY processing if GCWS309-ACT-PRELIMINARY is true, UPDATE processing if GCWS309-ACT-UPDATE is true, DELETE processing if GCWS309-ACT-DELETE is true, or ADD processing if GCWS309-ACT-ADD is true
[Execute PRELIMINARY Processing]
The system initiates preliminary processing → Execute the A200-PROCESS-PRELIMINARY procedure to create initial manifest transmission
[Execute UPDATE Processing]
The system initiates update processing → Execute the A500-PROCESS-UPDATE procedure to modify existing manifest transmission
[Execute DELETE Processing]
The system initiates delete processing → Execute the A400-PROCESS-DELETE procedure to remove manifest transmission
[Execute ADD Processing]
The system initiates add processing → Execute the A300-PROCESS-ADD procedure to create new manifest transmission
[Set Default: Process EDI Send]
EDI processing flag needs to be set → EDI send processing is enabled by default
[Set Flag: Don't Process EDI Send - Follower Manifest]
The manifest is also classified as a follower manifest → EDI send processing is disabled for this manifest
[Set Flag: Don't Process EDI Send - Master Manifest]
The manifest is classified as M1109 master type → EDI send processing is disabled for this manifest
[Set Segment to All Cargo Data]
The system sets the segment scope → All cargo segments are marked for retrieval
[Set Move Underscore to No Operation]
The system sets underscore processing mode → Underscore characters are preserved without modification
[Is Follower Manifest with RT43 Created?]
The manifest has RT43 created status AND the manifest is a follower manifest → EDI processing should be disabled for this manifest
[Is Master M1109 Manifest?]
The manifest is classified as M1109 master type → EDI processing should be disabled for this manifest
[Set Default: Process EDI Send = TRUE]
The processing eligibility validation begins → The system should set EDI processing flag to enabled by default
[Generate Transmission Number]
The system needs to assign a transmission number → Generate transmission number using appropriate prefix (101 for GCX101, 106 for GCX106, 107 for GCX107, 111 for GCX111, 113 for GCX113, or 998 for others) combined with machine time
[Process M10 Manifest Header]
Creating the M10 manifest header segment → Set manifest type code to 'P' if vessel name ends with 'T' and action is preliminary, otherwise use standard manifest type code logic
[Process M10 Manifest Header]
The vessel name needs to be determined for the M10 segment → If vessel name ends with 'T' and transport is export and secondary vessel name exists, use secondary vessel name and voyage number, otherwise use primary vessel name and voyage number
[Process M11 Bill of Lading]
The equipment type needs to be classified → If equipment is marked as empty, set BOL type code to '69', otherwise set to '00'
[Process N9 OB References]
Processing N9 reference segments → Process OB reference qualifier types first before other reference types
[Process N9 BN References]
Processing N9 reference segments in sequence → Process BN reference qualifier types after OB references but exclude OB types from BN processing
[Check BOL Type = 23?]
Checking if empty residue processing is required → If BOL type code equals 23, process N9 empty residue segment with ZF qualifier
[Process AES Data]
Processing export documentation segments → If AES SED data is not empty or low values, create N9 segment with first 3 characters as qualifier and remaining 29 characters as reference number
[Process M12 In-bond Information]
Checking M12 segment creation requirements → Process M12 segment only if transport type is US-Canada-US, multi-transit, or transport-export and M12 data is not empty and not broker bond type
[Process N10 Commodity]
Processing N10 commodity segments → Detect container sizes (20FT, 40FT, 45FT, 48FT, 53FT) with 'said to contain' patterns, remove original text, and append standardized format at end of description
[Process N10 Commodity]
Creating the first N10 commodity segment → Sum all numeric N1001 quantity values across all sequences and use total as the quantity for the first N10 segment
[Set Manifest Status]
Updating the manifest status after EDI transmission → If current status is preliminary and not a train manifest, change status to amendment, otherwise if status is amendment and is a train manifest, change status to preliminary
[Create N9 EDI Segment]
The system processes the general reference → An N9 EDI segment is created with the reference qualifier and number, and the segment is inserted into the transmission data
[Process AES Data References]
The SED (Shipper's Export Declaration) field contains data and is not spaces or low-values → An N9 segment is created with the first 3 characters as qualifier and characters 4-29 as the reference number
[Create ZF Reference Segment]
The system processes the shipment references → A ZF reference segment is created with qualifier 'ZF' and the residue description as the reference number
[Update EDI Sent Status]
The transaction type is not GCX106 AND the EDI sent status is not already set to electronic → The EDI sent status should be updated to electronic and the manifest record should be updated
[Generate Transmission Number]
The transmission number needs to be generated → The system should assign the appropriate prefix (101 for GCX101, 106 for GCX106, 107 for GCX107, 111 for GCX111, 113 for GCX113, or 998 for others) and append the current machine time
[Set M13 ADD Mode Flag]
The M13 amendment segment needs to be created → The system should set the M13 mode flag to ADD mode
[Process M13 Amendment with ADD Code]
The amendment type code needs to be determined → The system should set the amendment type code to 'A' for ADD operations
[Process M13 Amendment with ADD Code]
The action is ADD or UPDATE → The system should set the amendment code to '03', otherwise use the existing amendment code or default to '01' if empty
[Process M11 Bill of Lading]
The equipment status needs to be determined → The system should set BOL type code to '69' if equipment is empty, otherwise set to '00'
[Process N9 Reference Numbers]
The references are being processed for transmission → The system should process OB qualifier references first, then BN qualifier references, then all other references except KCM and FEN types
[Process N9 Reference Numbers]
The BOL type code equals 23 → The system should create an N9 segment with qualifier 'ZF' and residue description
[Process M12 In-bond Data]
The transport type is US-CANADA-US, MULTI-TRANSIT, or TRANSPORT-EXPORT AND M12 data is not empty AND not broker bond → The system should create the M12 segment with in-bond type code, entry number, location IDs, customs shipment value, and FDA indicator
[Process Idler Car Data]
The manifest status is RT43 CREATED → The system should save the CCN key and process associated idler car VID, N10, and H1-H2 segments
[Log Transaction]
The transaction needs to be logged → The system should create a log entry with action code for cargo sent automatically, CCN key, transaction details, and timestamp
[Spawn EDI Processing]
EDI processing needs to be initiated → The system should spawn GCT109 program with the transmission number for further EDI processing
[Create N9 EDI Segment]
The system processes the reference for EDI transmission → An N9 segment is created with the reference qualifier and number, stored in the N9 table, counter is incremented, and the segment is inserted into the transmission data
[Process AES Data References]
The SED field is not spaces or low-values → An N9 segment is created with the first 3 characters as reference qualifier and characters 4-29 as reference number
[Process Empty Residue N9]
The system processes reference numbers for the cargo → A ZF reference segment is created using the residue description as the reference number
[Update EDI Status to Electronic]
The EDI status is not already set to electronic → The system updates the EDI sent status to electronic and updates the manifest record
[Generate Transmission Number]
The system needs to create a transmission number → The system assigns a transmission prefix based on the transmission type (101 for GCX101, 106 for GCX106, 107 for GCX107, 111 for GCX111, 113 for GCX113, or 998 for others) and combines it with the current machine time to create a unique transmission number
[Create Transmission Root Record]
The system attempts to create the transmission root record → The system creates a transmission record with transaction set '309', and if a duplicate transmission number exists, it increments the number and retries until a unique number is found
[Process M10 Manifest Header]
The M10 manifest header segment is created → The system sets the manifest type code to 'Y' for GCX111, GCX113, or GCX107 transmission types with DELETE action, uses vessel name logic (secondary vessel if vessel name ends with 'T' and is export transport), validates country code (defaults to 'CA' if not US, CA, or MX), and sets record type to 'CARGO'
[Process P4 Location Information]
The P4 location segment is processed → The system creates a P4 segment with the location ID and ETA date from the manifest data
[Process LX Line Number]
The LX line number segment is processed → The system increments the assigned number counter and sets the LX assigned number to '00001'
[Set M13 DELETE Mode]
The M13 amendment segment mode is set → The system sets the M13 processing mode to DELETE mode to ensure proper amendment type code assignment
[Process M13 Amendment Segment]
The M13 amendment segment is processed → The system sets amendment type code to 'D' for DELETE action, assigns amendment code '02' for GCX106 DELETE or '01' for default cases, uses the manifest CCN ID as BOL/WB number, and includes SCAC codes and location information
[Log Transmission Details]
The system determines whether to log the transmission → If the action is not UPDATE, the system logs the transmission with action code for automatic cargo sent, otherwise it skips logging to avoid duplicate entries during update operations
[Spawn EDI Processing Transaction]
The EDI processing transaction is spawned → The system calls the GCT109 transaction with the transmission number to process the EDI transmission, handling both BPE and TPE environments appropriately
[Update EDI Sent Status]
The transmission type is not GCX106 and the EDI sent status is not already set to electronic → The EDI sent status should be updated to electronic
[Generate Transmission Number]
The transmission type is determined (GCX101, GCX106, GCX107, GCX111, GCX113, or other) → A transmission number should be generated with the appropriate prefix (101, 106, 107, 111, 113, or 998) combined with machine time
[Process M10 Manifest Header]
The M10 segment is being created → The manifest type code should be set to 'Y' for update actions
[Set DELETE Mode for M13]
The M13 amendment segment processing begins → The processing mode should be set to DELETE mode and amendment type code should be set to 'D'
[Set ADD Mode for M13]
The M13 amendment segment processing continues → The processing mode should be set to ADD mode
[Process N9 Reference Numbers]
N9 reference segments are being processed → OB reference qualifiers should be processed first, followed by BN reference qualifiers, then all other reference qualifiers except KCM and FEN types
[Process AES Data]
AES data segments are being processed → N9 segments should be created with the first 3 characters as reference qualifier and remaining 29 characters as reference number
[Process M12 In-bond Data]
M12 in-bond data processing is evaluated → M12 segment should be created only if transport type is US-CANADA-US, MULTI-TRANSIT, or TRANSPORT-EXPORT and M12 data is not empty and not broker bond
[Process VID Equipment]
VID equipment segments are being processed → Equipment should be classified with load/empty status code from the manifest data
[Process N10 Commodity]
N10 commodity segments are being processed → Container descriptions containing 'SAID TO CONTAIN' should be detected for container types (20FT, 40FT, 45FT, 48FT, 53FT) and moved to the end with standardized format
[Check for Idler Cars]
The manifest type is RT43 created → Associated idler cars should be processed for VID equipment, N10 commodity, and H1-H2 hazmat segments
[Log Transmission]
All segments have been processed → A log entry should be created with action code for cargo sent automatically, including manifest key, transaction details, and timestamp
[Spawn EDI Processing]
All manifest segments have been created and logged → The GCT109 EDI processing program should be invoked with the transmission number
[Process General References]
The reference qualifier and number are valid → The reference is stored in the N9 table, N9 counter is incremented, and an N9 EDI segment is created with the reference qualifier and number
[Create ZF Reference Segment]
The BOL type code equals 23 → A ZF reference segment is created with qualifier 'ZF' and the residue description as the reference number
[Process AES Data Loop]
The SED (Shipper's Export Declaration) field is not spaces or low-values → An N9 segment is created with the first 3 characters of SED as the reference qualifier and characters 4-29 as the reference number
[Set Prefix = 101 GCX101 Transaction]
The transaction type is GCX101 → The transmission number prefix is set to 101
[Set Prefix = 106 GCX106 Transaction]
The transaction type is GCX106 → The transmission number prefix is set to 106
[Set Prefix = 107 GCX107 Transaction]
The transaction type is GCX107 → The transmission number prefix is set to 107
[Set Prefix = 111 GCX111 Transaction]
The transaction type is GCX111 → The transmission number prefix is set to 111
[Set Prefix = 113 GCX113 Transaction]
The transaction type is GCX113 → The transmission number prefix is set to 113
[Set Prefix = 998 Default/Unknown Transaction]
The transaction type is not GCX101, GCX106, GCX107, GCX111, or GCX113 → The transmission number prefix is set to 998 as default
[Get Current Machine Time]
The system needs to create a unique transmission identifier → The current machine time is retrieved from the system
[Combine Prefix + Machine Time Create Unique Transmission Number]
The system creates the final transmission number → The transmission number is formed by combining the prefix with the machine time to ensure uniqueness
[Set SCAC Code from Manifest]
The M10 segment is being populated → The SCAC code from the manifest is assigned to the M10 segment SCAC field
[Set Transport Type Code]
The M10 segment is being populated → The transport type code from the manifest is assigned to the M10 segment transport type field
[Use Manifest Country Code]
The M10 segment country code is being set → The manifest country code is assigned to the M10 segment
[Default to 'CA']
The M10 segment country code is being set → The country code is defaulted to 'CA'
[Set Reference Number]
The M10 segment is being populated → The reference number from the manifest is assigned to the M10 segment reference field
[Set Quantity]
The M10 segment is being populated → The quantity from the manifest is assigned to the M10 segment quantity field
[Set Manifest Type to 'Y' for Amendment]
The M10 segment manifest type is being determined → The manifest type code is set to 'Y'
[Set Manifest Type to 'P' for Preliminary]
The M10 segment manifest type is being determined → The manifest type code is set to 'P'
[Use Secondary Vessel Name]
The M10 segment vessel name is being set → The secondary vessel name is used instead of the primary vessel name
[Use Primary Vessel Name]
The M10 segment vessel name is being set → The primary vessel name from the manifest is used
[Set Flight/Voyage Number]
The M10 segment flight/voyage number is being set → If secondary vessel is used, use secondary flight/voyage number, otherwise use primary flight/voyage number
[Set Record Type to 'CARGO']
The record type field is being populated → The record type is set to 'CARGO'
[Set Record Number]
The M10 segment record number is being set → The record number from the manifest is assigned to the M10 segment
[Set Application Type to '28']
The application type field is being populated → The application type is set to '28'
[Clean Segment Data]
The segment data is being finalized → All underscore characters in the segment are replaced with spaces
[Store M10 Segment to Database]
The segment is ready for storage → The M10 segment is inserted into the database transmission data
[Generate Next Sequence Number]
The system needs to assign a sequence number to the P4 segment → The system increments the current sequence number by 1 and assigns it to the P4 segment
[Set P4 Segment Identifier]
The system initializes the segment structure → The system sets the segment identifier to 'P4 '
[Extract Location ID from Manifest]
The system processes P4 segment creation → The system copies the location ID from GCUSRT-P401-LOCATION-ID to P4-01-LOCATION-ID
[Extract Estimated Time of Arrival Date]
The system processes P4 segment creation → The system copies the ETA date from GCUSRT-P402-ETA-DATE to P4-02-ETA-DATE
[Store P4 Segment in Database]
The system needs to store the segment for EDI processing → The system moves the P4 segment to transmission data field and calls the database insert routine Z1010-ISRT-GCSA9DP
[Create LX Segment Identifier]
The system creates the segment identifier → The segment identifier is set to 'LX '
[Assign Line Number '00001']
The system assigns the line number → The assigned number is set to '00001' and the assigned number counter is incremented by 1
[Store LX Segment in Database]
The system stores the segment → The LX segment data is moved to transmission data and inserted into the database
[Set Basic M13 Fields]
Basic field assignment is performed → The system sets SCAC code from M1301, location ID from P401, BOL/WB number from CCN ID, quantity from M1305, and secondary SCAC code from M1309
[Set Amendment Type = 'D' for Delete]
The action is DELETE or the action is UPDATE with delete mode enabled → The system sets the amendment type code to 'D' in the M13 segment
[Set Amendment Type = 'A' for Add]
The action is UPDATE and add mode is enabled → The system sets the amendment type code to 'A' in the M13 segment
[Set Amendment Code = '02' for GCX106 Delete]
The action is DELETE → The system sets the amendment code to '02' in the M13 segment
[Set Amendment Code = '03' for GCX106 Add/Update]
The action is UPDATE or ADD → The system sets the amendment code to '03' in the M13 segment
[Use Default Amendment Code]
The transmission type is not GCX106 → The system uses the existing amendment code from GCUS-M1306-AMENDMENT-CDE
[Set Basic M13 Fields]
The action code needs to be assigned → The system sets the action code from GCUS-M1307-ACTION-CDE to M13-07-ACTION-CDE
[Store M13 Segment to Database]
The segment is ready for storage → The system replaces all underscores with spaces in the M13 segment and stores it to the transmission database
[Set Bill of Lading Number]
The M11 segment is being populated → The bill of lading number is copied from GCUSRT-M1101-BOL-WB-NUM to M11-01-BOL-WB-NUM
[Set Location ID]
The M11 segment location field is being populated → The location ID is copied from GCUSRT-M1102-LOCATION-ID to M11-02-LOCATION-ID
[Set Quantity Information]
The M11 segment quantity field is being populated → The quantity is copied from GCUSRT-M1103-QUANTITY to M11-03-QUANTITY
[Set Manifest Unit Code]
The M11 segment unit code field is being populated → The manifest unit code is copied from GCUSRT-M1104-MANIF-UNIT-CDE to M11-04-MANIF-UNIT-CDE
[Set Weight Information]
The M11 segment weight field is being populated → The weight is copied from GCUSRT-M1105-WEIGHT to M11-05-WEIGHT
[Set Weight Unit Code]
The M11 segment weight unit field is being populated → The weight unit code is copied from GCUSRT-M1106-WEIGHT-UNIT-CDE to M11-06-WEIGHT-UNIT-CDE
[Set Place of Receipt]
The M11 segment place of receipt field is being populated → The place of receipt is copied from GCUSRT-M1110-PLACE-OF-RECEIPT to M11-10-PLACE-OF-RECEIPT
[Set Primary SCAC Code]
The M11 segment primary SCAC field is being populated → The primary SCAC code is copied from GCUSRT-M1112-SCAC-1 to M11-12-SCAC
[Clean Segment Data]
The segment data needs to be cleaned for transmission → All underscore characters ('_') in the M11 segment are replaced with space characters
[Store M11 Segment to Database]
The segment is ready for database storage → The M11 segment data is moved to transmission data field and database insert operation is performed
[More Reference Qualifiers to Process?]
The system checks the current occurrence counter against the maximum allowed occurrences → The system continues processing if the counter is less than or equal to the maximum N9 occurrences by sequence, otherwise terminates the loop
[Create N9 EDI Segment]
N9 segment creation is initiated → A new N9 segment is created with identifier 'N9', reference qualifier in position 01, reference number in position 02, underscores replaced with spaces, and stored in transmission data
[Check for FDA Shipment Indicators]
The reference qualifier is 'ZZ' and the reference number starts with '2K FDA' → The shipment is flagged as FDA-regulated
[Check for FDA Shipment Indicators]
The reference qualifier is '2K' → The shipment is flagged as FDA-regulated
[Check Bill of Lading Type Code]
The bill of lading type code equals 23 (indicating empty residue project) → An N9 segment should be created with reference qualifier 'ZF' and the residue description as the reference number
[Set Reference Number Qualifier to 'ZF']
Creating the N9 segment for the empty residue project → The reference number qualifier should be set to 'ZF' and the reference number should contain the residue description from working storage
[Store N9 Segment in EDI Transmission]
Preparing the segment for EDI transmission → The N9 segment should be formatted by replacing underscores with spaces and stored in the transmission data structure
[Create N9 Segment for AES Data]
The system creates an N9 segment for AES data → An N9 segment is formatted with 'N9 ' identifier, extracted qualifier, and reference number with underscores replaced by spaces
[Store N9 Segment in EDI Transmission]
The system stores the segment in EDI transmission → The N9 segment is inserted into the transmission dependent segment structure with proper sequence numbering
[Process Each Entity Record]
The system processes entity records sequentially from 1 to maximum sequence minus 1 → Each non-empty entity record is processed for N1, N3, N4, and PER segments
[N3 Address Information Processing]
The system processes the address data → Create N3 segment with address line 1 and address line 2 information
[N4 Geographic Information Processing]
The system processes the geographic data → Create N4 segment with city name, state/province code, postal code, and country code
[PER Contact Information Processing]
The system processes the contact data → Create PER segment with function code 'IC', contact name (first 23 characters), and communication number if name is empty but number exists
[Broker Information Processing]
The system processes broker information → Create N1 segment with entity ID 'CB', broker short name, and construct ABI routing code using alternative US code or district/filer/office combination, then generate broker routing notification message
[N1 Entity Identification Processing]
The entity ID code is 'SH' (Shipper) → Invoke customer check processing to validate shipper information
[Create N1 Entity Identification Segment]
The system creates N1 segment with entity ID code, name, and determines ID code qualifier based on entity type → N1 segment is populated with entity identification code, name, appropriate ID code qualifier (02 for SCAC if SNP entity with SCAC available, 17 for SNP without SCAC, or original qualifier for other entities), and corresponding ID code
[Create N3 Address Information Segment]
The system creates N3 segment → N3 segment is populated with primary address information and secondary address information from entity data
[Create N4 City/State/Postal/Country Segment]
The system creates N4 segment → N4 segment is populated with city name, state/province code, postal code, and country code from entity data
[Create PER Contact Information Segment]
The system creates PER segment → PER segment is populated with contact function code 'IC', contact name (first 23 characters), and if communication number exists but name is empty, includes communication number qualifier and communication number
[Create N1 Entity Identification Segment]
The entity ID code is 'SH' (Shipper) → The system invokes customer export validation process
[Set Entity ID Code from Source Data]
Processing N1 segment creation → The entity ID code is copied from source data to N1 segment
[Set Entity Name from Source Data]
Processing N1 segment creation → The entity name is copied from source data to N1 segment
[Entity Type = 'SNP'?]
The entity ID code is 'SNP' → Special logic is applied to determine the ID code qualifier based on M13 SCAC availability
[Replace Underscores with Spaces]
Preparing segment for transmission → All underscore characters in the segment are replaced with space characters
[Entity Type = 'SH' Shipper?]
The entity ID code is 'SH' indicating a shipper → Customer authorization validation is performed
[Store N1 Segment in Database]
Segment processing is complete → The N1 segment is inserted into the transmission database for EDI processing
[Extract Primary Address Line]
The system processes the N3 address segment → The system should move the primary address information to the N3-01-ADDRESS-INFO field
[Extract Secondary Address Line]
The system processes the N3 address segment → The system should move the secondary address information to the N3-02-ADDRESS-INFO field
[Store N3 Address Segment]
The system completes N3 segment processing → The system should move the N3 segment to the transmission data area A9DP-TRANSMISSION-DATA
[Set N4 Segment Identifier]
The segment identifier needs to be set → The N4 identifier field is populated with 'N4 '
[Extract City Name from Entity Data]
The N4 segment is being populated with geographic data → The city name from the entity data is moved to the N4 city name field
[Extract State/Province Code from Entity Data]
The N4 segment is being populated with geographic data → The state/province code from the entity data is moved to the N4 state/province code field
[Extract Postal Code from Entity Data]
The N4 segment is being populated with geographic data → The postal code from the entity data is moved to the N4 postal code field
[Extract Country Code from Entity Data]
The N4 segment is being populated with geographic data → The country code from the entity data is moved to the N4 country code field
[Store N4 Geographic Segment for EDI Transmission]
The segment is ready for EDI transmission → The N4 segment is moved to the transmission data structure
[Set Contact Function Code to 'IC']
The contact function code needs to be set → The contact function code is set to 'IC' (Information Contact)
[Communication Number Available?]
The system checks for communication number availability → Communication number is processed only if it exists and contact name is missing
[Set Communication Number Qualifier]
The PER segment communication fields are being populated → The communication number qualifier from the contact record is assigned to the PER segment
[Set Communication Number]
The PER segment communication fields are being populated → The communication number from the contact record is assigned to the PER segment
[Clean Segment - Replace Underscores with Spaces]
The segment is being prepared for transmission → All underscore characters in the PER segment are replaced with spaces
[Store PER Segment in Transmission Data]
The segment is ready for transmission → The PER segment is moved to the transmission data area and stored in the database
[Check Broker Status]
The broker is unknown:
broker is not required
the office code is '99'
→ The system skips broker processing and continues with the next processing step
[Create N1 Customs Broker Segment]
The system processes broker information → An N1 segment is created with entity ID 'CB' and the broker short name from the manifest
[Retrieve Broker Details from Table]
The system needs broker table information → The system calls GCCTBIO to retrieve broker details using broker short name combined with location ID (M1203 if available, otherwise P401)
[Log ABI Routing Code Information]
The broker processing is completed → The system creates a log message containing 'ABI ROUTING CODE' followed by the constructed routing code and sends it via GCT105 transaction
[Validate Customer Authorization]
The transmission type is not GCX106 → The system calls GCT140 transaction to validate customer authorization with the appropriate action code (UPD for update, DEL for delete, ADD for add or default)
[Create N1 Broker Segment Header]
The system creates the N1 broker segment → The entity ID code is set to 'CB' and ID code qualifier is set to '17'
[Set Entity ID Code to 'CB']
The entity identification code is assigned → The entity ID code is set to 'CB' to indicate customs broker
[Get Broker Short Name from Manifest]
The broker segment is being populated → The broker short name is retrieved from the manifest RT01 broker short name field
[Set ID Code Qualifier to '17']
The ID code qualifier is assigned → The ID code qualifier is set to '17' as the standard broker identifier
[Look Up Broker Table 'BK']
The system performs a table lookup with table ID 'BK' → The broker information is retrieved if found, otherwise the segment remains empty
[Get Alternative US Code from Table]
The alternative US code is accessed → The alternative US broker code is extracted from the table segment
[Store N1 Broker Segment]
The segment is finalized → The N1 segment is stored in the transmission data and inserted into the EDI stream
[Log ABI Routing Code Message]
The broker processing is completed → A log message containing the ABI routing code is created and sent to the logging system
[Check M12 Data Available?]
The M12 data field contains spaces or low values → The system skips M12 in-bond processing and continues with next processing step
[Set Entry Number]
Entry number data is available in the manifest → The system moves the entry number to M12-02-ENTRY-NUMBER field
[Set Origin Location]
Origin location identifier is available in the manifest → The system moves the location ID1 to M12-03-LOCATION-ID field
[Set Destination Location]
Destination location identifier is available in the manifest → The system moves the location ID2 to M12-04-LOCATION-ID field
[Set Customs Shipment Value]
Customs shipment value is available in the manifest → The system moves the customs shipment value to M12-05-CUSTOMS-SHIPM-VALUE field
[Set In-bond Control Number]
In-bond control number is available in the manifest → The system moves the in-bond control number to M12-06-IN-BOND-CTRL-NUM field
[Set Reference Number & Qualifier]
Reference number qualifier and reference number are available in the manifest → The system moves the reference number qualifier to M12-08-REF-NUM-QUAL field and reference number to M12-09-REF-NUM field
[Set Transport Type Code]
Transport type code is available in the manifest → The system moves the transport type code to M12-10-TRANSP-TYP-CDE field
[Set Vessel Name]
Vessel name is available in the manifest → The system moves the vessel name to M12-11-VESSEL-NAME field
[Set FDA Indicator]
FDA shipment indicator has been determined during processing → The system moves the FDA shipment indicator to M12-12-FDA-IND field
[Create M12 EDI Segment]
M12 segment creation is initiated → The system formats the M12 segment by replacing underscores with spaces and prepares it for EDI transmission
[Store M12 Segment]
M12 segment storage is initiated → The system stores the M12 segment in the transmission data structure and calls the insert routine to add it to the EDI transmission
[Set Equipment Description Code]
The system processes equipment description information → The equipment description code from cargo data is assigned to VID segment field 01
[Set Equipment Initialization]
The system processes equipment initialization information → The equipment initialization code from cargo data is assigned to VID segment field 02
[Set Equipment Number]
The system processes equipment number information → The equipment number from cargo data is assigned to VID segment field 03
[Set Primary Seal Number]
The system processes primary seal information → The primary seal number from cargo data is assigned to VID segment field 04
[Set Secondary Seal Number]
The system processes secondary seal information → The secondary seal number from cargo data is assigned to VID segment field 05
[Set Load/Empty Status Code]
The system processes load/empty status information → The load/empty status code from cargo runtime data is assigned to VID segment field 10
[Format VID Segment]
The system prepares VID segment for transmission → All underscore characters in the VID segment are replaced with spaces
[Store VID Segment in Database]
The system stores the VID segment → The VID segment is moved to transmission data area and inserted into the database
[Create VC Segment]
The system processes the vehicle for EDI transmission → A VC segment is created with identifier 'VC ', the vehicle ID number is moved to VC-01-VEHICLE-ID-NUM, underscores are replaced with spaces, and the segment is stored in the EDI transmission
[Consolidate Commodity Descriptions from Multiple Sources]
The system processes commodity descriptions → All description data from different segments is consolidated into a single working description area for unified processing
[Office Code = 99?]
The office code equals '99' → The system calculates total quantities by summing all line item quantities across sequences, otherwise it uses individual line item quantities
[Calculate Total Quantity from All Line Items]
The system processes quantity calculations → All numeric quantity values from positions 10-15 of each line item are summed together to create a total quantity for the primary N10 segment
[Use Individual Line Item Quantity]
The system processes quantity for N10 segment creation → The system uses the individual quantity from the first line item without summing across multiple line items
[Create Primary N10 Segment with Quantity]
The system creates the primary N10 segment → The N10 segment is created with the calculated or individual quantity, processed commodity description, marks and numbers, commodity code qualifier, harmonized commodity code, customs shipment value, weight unit code, and weight
[Additional Description Lines Exist?]
Additional description lines exist beyond the first line or additional marks and numbers exist → The system creates additional N10 segments for each additional description line or marks and numbers entry
[Create Additional N10 Segments for Multi-line Descriptions]
Additional description lines need to be processed (lines 2-12 with content or lines 13+ with content) → The system creates additional N10 segments with zero quantity, the continuation description text, and appropriate marks and numbers or placeholder dots
[Set Quantity to Zero for Additional Lines]
The system processes continuation lines beyond the primary segment → All additional N10 segments have their quantity field set to '0000000000' since quantity is only reported on the first segment
[Store N10 Segment in Database]
The segment is ready for transmission → The system stores the N10 segment in the GCSA9DP database with proper sequence numbering and transmission data formatting
[Create First N10 Segment]
The system creates the first N10 segment → N10 segment is created with sequence number increment, quantity field populated from first occurrence or calculated total, first description line content, marks and numbers from first occurrence, commodity code qualifier, harmonized commodity code, customs shipment value, weight unit code, and weight value
[More Description Lines Available?]
The system checks for additional description content → If description lines 2 through 12 contain non-space content OR marks and numbers lines 2 through 12 contain non-space content OR description lines 13 through 500 contain non-space content, then additional processing is required
[Create Additional N10 Segment]
The system processes lines 2 through 12 → For each line with content, create N10 segment with sequence number increment, quantity set to '0000000000', description content from current line or placeholder dot if empty, and marks and numbers content from current line or placeholder dot if empty
[Create Additional N10 Segment]
The system processes lines 13 through 500 → For each line with non-space content, create N10 segment with sequence number increment, quantity set to '0000000000', description content from current line, and marks and numbers set to placeholder dot
[Add Description Content]
The system populates the description field → If current description line contains non-space content, use the description content, otherwise set description field to placeholder dot
[Set Marks/Numbers to Placeholder]
The system populates the marks and numbers field → If current marks and numbers line contains non-space content, use the marks and numbers content, otherwise set field to placeholder dot. For lines 13 and above, always set field to placeholder dot
[Store N10 Segment]
The system stores the segment → The N10 segment is moved to transmission data structure and inserted into the dependent segment database
[Create N10 Segment]
Processing a valid commodity occurrence beyond the first record → Create N10 segment with sequence number, identifier 'N10', quantity from current occurrence, saved description as free-form description, and saved marks and numbers
[Loop Through Each Hazmat Occurrence]
The system processes occurrences from 1 to maximum occurrences limit per sequence → Each occurrence is evaluated for H1 hazmat data content before segment creation
[Create H1 Hazmat Segment]
The system creates an H1 segment → A new H1 segment is initialized with proper sequence number and identifier 'H1 '
[Set Hazmat Code]
The system sets the hazmat code field → The H1-01 hazmat code field is populated with the source hazmat code value
[Set Hazmat Description]
The system sets the hazmat description field → The H1-04 hazmat description field is populated with the source hazmat description value
[Set Hazmat Contact Information]
The system sets the hazmat contact field → The H1-05 hazmat contact field is populated with the source hazmat contact value
[Store H1 Segment in Database]
The system stores the segment → The H1 segment is formatted by replacing underscores with spaces and inserted into the transmission database
[Create H2 Additional Description Segment]
The system creates an H2 segment → A new H2 segment is initialized with proper sequence number and identifier 'H2 '
[Set Additional Hazmat Description]
The system sets the additional hazmat description field → The H2-01 additional hazmat description field is populated with the source H2 description value
[Store H2 Segment in Database]
The system stores the H2 segment → The H2 segment is formatted by replacing underscores with spaces and inserted into the transmission database
[Create H1 Hazardous Material Segment]
The system processes the hazmat record → An H1 segment is created with sequence number incremented and segment identifier set to 'H1'
[Move Hazmat Code to H1-01]
The system populates hazmat information → The hazmat code from the occurrence is moved to H1-01-HAZ-MAT-CDE field
[Move Hazmat Description to H1-04]
The system populates hazmat information → The hazmat description from the occurrence is moved to H1-04-HAZ-MAT-DESC field
[Move Hazmat Contact to H1-05]
The system populates hazmat information → The hazmat contact from the occurrence is moved to H1-05-HAZ-MAT-CONTACT field
[Store H1 Segment in Database]
The system completes H1 segment processing → The H1 segment is stored in the transmission database
[Create H2 Additional Description Segment]
The system processes the H2 segment → An H2 segment is created with sequence number incremented and segment identifier set to 'H2'
[Move Additional Description to H2-01]
The system populates H2 information → The additional hazmat description from the occurrence is moved to H2-01-HAZ-MAT-DESC field
[Store H2 Segment in Database]
The system completes H2 segment processing → The H2 segment is stored in the transmission database
[Set H2 Segment Identifier]
The system sets up the segment identifier → The segment identifier is set to 'H2 ' (H2 followed by space)
[Move Additional Hazmat Description to H2 Segment]
The system populates the hazmat description field → The additional hazmat description from the current occurrence is moved to the H2-01 hazmat description field
[Clean Up Segment Format]
The system performs format cleanup → All underscore characters in the H2 segment are replaced with space characters
[Store H2 Segment in Transmission Data]
The system stores the segment for transmission → The H2 segment is moved to the transmission data area and the database insertion routine Z1010-ISRT-GCSA9DP is performed
[Process Idler Car Equipment - VID Segment]
The system processes the idler car → The system should create VID segments containing equipment description, initialization, number, seal numbers, and load/empty status
[Process Idler Car Commodity - N10 Segment]
The system continues processing the idler car → The system should create N10 segments containing quantity, commodity description, marks and numbers, commodity codes, customs value, and weight information
[Process Idler Car Hazmat - H1/H2 Segments]
The system continues processing the idler car → The system should create H1 segments for hazardous material codes, descriptions, and contacts, followed by H2 segments for additional hazmat descriptions
[Process VID Equipment Segments]
The system processes equipment information → The system calls the VID processing routine to create equipment segments
[Process N10 Commodity Segments]
The system processes commodity information → The system calls the N10 processing routine to create commodity segments
[Process H1/H2 Hazmat Segments]
The system processes hazardous material information → The system calls the H1-H2 processing routine to create hazmat segments if hazardous materials are present
[Enable All Segment Fetching]
System needs complete manifest information including all segments → All segment fetching is enabled for comprehensive data retrieval
[Set Idler Car Processing Mode]
The get next idler car process is initiated → The system sets idler car processing mode to true, sets database function to Get Next, configures fetch parameters for all segments, enables underscore handling, and sets index to lead CCN
[Set Action Code to 'Cargo Sent Automatically']
The transaction log is being prepared → The action code is set to LOG-CARGO-SENT-AUTOMATICALLY to indicate automatic cargo transmission
[Capture Manifest CCN Key]
Transaction logging is performed → The manifest CCN key (GCWS309-US-CCN-KEY) is captured and stored in the log message (GCX105-TRAIN-OR-US-CCN)
[Record Sending Transaction Code]
The cargo type needs to be specified → The cargo type indicator (GCX105-US-CARGO) is set to TRUE to identify this as US cargo
[Record Sending Transaction Code]
Transaction logging is performed → The sending transaction code (CC-TRANS-CODE) is captured and stored in the log message (GCX105-SENDING-TRANSACTION)
[Capture User ID from System]
Transaction logging is performed → The user's ACF2 ID (CC-ACF2-USERID) is captured and stored in the log message (GCX105-ACF2-ID)
[Generate Time Stamp from Machine Time]
A time stamp needs to be generated for logging → The machine time (CC-MACHINE-TIME-X) is captured and stored in the log message (GCX105-TIME)
[Format Complete Log Message]
The log message needs to be prepared for transmission → The complete log input structure (GCX105-INPUT) is moved to the transmission message format (GCT1051E-MSG)
[Check Runtime Environment]
A log message needs to be transmitted → The system checks the runtime environment flag (IS-RUNNING-IN-BPE) to determine the transmission method
[Send Log via BPE Interface]
The log transmission is initiated → The system uses CSIEXCI interface to transmit the log message with transaction name GCT1051E
[Send Log via TPE Interface]
The log transmission is initiated → The system uses CIMS and WRITMSGL calls to transmit the log message through the alternate PCB
[Set Security Authorization]
The system prepares to spawn the EDI processing transaction → The security byte is set to high-value to establish maximum authorization level
[Assign Transmission Number to EDI Transaction]
The system prepares the EDI transaction message → The transmission number is assigned to the EDI transaction input structure
[Prepare EDI Transaction Message]
The system prepares to send the transaction message → The EDI input data is moved to the transaction message structure
[Submit EDI Transaction for Processing]
The system needs to submit the EDI transaction for processing → The system calls external transaction interface with transaction name, message length, and communication data
[Submit EDI Transaction for Processing]
The system needs to submit the EDI transaction for processing → The system calls message interface to change message queue, writes message to queue, and purges the message
[Set Amendment Type Code to 'D' - Delete BOL]
The action type is delete (GCWS309-ACT-DELETE is true) → The amendment type code is set to delete BOL (88-GCUS-M1303-DEL-A-BOL is set to true)
[Set Amendment Type Code to 'A' - Add BOL]
The action type is not delete (GCWS309-ACT-DELETE is false) → The amendment type code is set to add BOL (88-GCUS-M1303-ADD-A-BOL is set to true)
[Set Amendment Code to '02' - Delete]
The transaction type is GCX106 (GCWS309-TRANSM-GCX106 is true) and the action is delete (GCWS309-ACT-DELETE is true) → The amendment code is set to '02'
[Set Amendment Code to '03' - Add/Update]
The transaction type is GCX106 (GCWS309-TRANSM-GCX106 is true) and the action is either update (GCWS309-ACT-UPDATE is true) or add (GCWS309-ACT-ADD is true) → The amendment code is set to '03'
[Update Amendment Data in Database]
The amendment processing is complete → The GCSUSS01 segment is updated in the database through the GCCUSIO program
[Set Transmission Number]
The transmission root record is being prepared for storage → The transmission number is assigned to the root record transmission number field
[Set Transaction Set to '309']
The transaction set type needs to be specified → The transaction set field is set to '309' to identify this as a customs manifest transmission
[Set Status to 'II' - Insert Intent]
The system prepares to insert the record into the database → The accept status is set to 'II' to indicate insert intent
[Store EDI Segment Data]
Each EDI segment needs to be stored in the database → A dependent segment record is created with sequence number, segment data is moved to the transmission data field, and the record is inserted as a child of the root transmission
[Handle Transmission Number Conflicts]
The database insert fails due to a duplicate transmission number conflict (status code is not SPACE) → The system increments the transmission number by 1 and retries the database insert operation until successful
[Set Status to 'II' - Insert Intent]
The insert operation is initiated → The system sets the database accept status to 'II' to indicate insert intent
[Insert Successful?]
The database operation completes → If the status code equals SPACE, the insert was successful; otherwise it failed due to a conflict
[Increment Transmission Number]
The system detects the conflict → The transmission number is incremented by 1 to create a new unique identifier
[Move Primary SCAC Code to M11-12]
The system processes M11 segment creation for EDI transmission → The primary SCAC code is moved to position M11-12-SCAC in the EDI segment
[Move Secondary SCAC Code to M11-14]
The system processes secondary SCAC code for EDI transmission → The secondary SCAC code is moved to position M11-14-SCAC in the EDI segment
[Move Third SCAC Code to M11-15]
The system processes third SCAC code for EDI transmission → The third SCAC code is moved to position M11-15-SCAC in the EDI segment
[Get Country Code from Manifest]
The system processes the manifest for EDI transmission → The country code is retrieved from the manifest M1003 country code field
[Use Original Country Code]
The system processes the country code for the M10 segment → The original country code from the manifest is used without change
[Default to CA Country Code]
The system processes the country code for the M10 segment → The country code is set to 'CA' as the default value
[Set Country Code in M10 Segment]
The M10 segment is being constructed for EDI transmission → The country code is assigned to the M10-03-COUNTRY-CDE field
[Check Equipment Status]
If the equipment status indicator (88-GCUSRT-M1109-EMPTY-EQUIP) → The system assigns BOL type code '69' for empty equipment or '00' for loaded cargo
[Check Office Code]
The system checks the office code in the cargo record → If office code equals '99' then initiate quantity totaling process, otherwise use the first occurrence quantity directly
[Convert Total to Display Format]
The quantity totaling process completes → Replace all spaces in the total quantity with zeroes and format for N10 segment usage
[Use Calculated Total for N10 Segment]
Creating the N10 segment quantity field → Use the calculated total quantity instead of the first occurrence quantity
[Use Secondary Vessel Name]
The system processes the M10 segment for vessel information → The secondary vessel name should be used instead of the primary vessel name
[Use Secondary Voyage Number]
The system processes the voyage number for the M10 segment → The secondary voyage number should be used instead of the primary voyage number
[Use Primary Vessel Name]
The system processes vessel information for the M10 segment → The primary vessel name and voyage number should be used
[Set Manifest Type to 'P']
The system assigns the manifest type code in the M10 segment → The manifest type code should be set to 'P'
[Combine All Description Data into Working Storage]
The system combines description data from all sources → Move GCUS-N1002-LONG-DESC to WS-DESC-US07, move GCSUSS10-N10-MORE-DATA to WS-DESC-US10, and iterate through all GCSUSS12 segments to move GCSUSS12-N10-HUGE-DESC to corresponding WS-DESC-US12 array elements
[Create First N10 Segment with Primary Description]
The system creates the first N10 segment → If manifest is idler type, set quantity to '000000000000000', otherwise if office code is '99' calculate total quantity by summing all N1001 quantities across sequences, else use the first N1001 quantity value, set description to first description line or '.' if empty, set marks and numbers from first N1003 value, set commodity code qualifier to 'J' if harmonized commodity code exists and transaction is immediate or transport export, and store the complete N10 segment
[Create Additional N10 Segment]
Additional description lines or marks and numbers exist for the current line → Create N10 segment with quantity '0000000000', set description to current line or '.' if empty, set marks and numbers to current line value or '.' if empty, and store the segment
[Create Additional N10 Segment]
Description line is not empty → Create N10 segment with quantity '0000000000', set description to current line content, set marks and numbers to '.', and store the segment
[More Description Lines Available?]
Second line release number is not spaces or low-values and first line is not 'C4 FILED BY BROKER' → Process multi-line N1009 data by iterating through sequences starting from sequence 2, create N10 segments with quantity from each sequence, use saved description and marks/numbers from primary processing, and store each segment
[Create N10 Segment with Marks Data]
The system creates an N10 segment → The segment is initialized with spaces, assigned a sequence number, set with N10 identifier, quantity set to '0000000000', description field populated from current position or set to '.' if empty, and marks field populated from current position or set to '.' if empty
[Set Marks Field to Current Marks Entry]
The marks field needs to be populated → If marks occurs data at current position is empty, the marks field is set to '.', otherwise it is set to the marks occurs data at the current position
[Set Default Marks Field to '.']
The marks field in N10 segment needs to be populated → The marks field is set to the default value of '.'
[Store N10 Segment to Database]
The segment is ready for storage → The N10 segment is moved to transmission data area and stored to the database through the insert operation
[Move to Next Marks Entry]
Description data exists at positions 13 through 500 → For each position with description data, create an N10 segment with quantity '0000000000', description from current position, and marks field set to '.'
[Use Alternative Broker Code + Filer + Office]
Constructing the ABI routing code for the N1 segment → The system combines the alternative US broker code with the filer code and office code to create the identification code
[Use District + Filer + Office Codes]
Constructing the ABI routing code for the N1 segment → The system combines the district code, filer code, and office code to create the identification code
[Store Constructed Code in N1 Segment]
Populating the N1 segment for broker information → The system stores the constructed ABI routing code in the N1-04 identification code field of the N1 segment
[Set Equipment Description Code]
The system processes equipment description information → The equipment description code from GCUS-VID01-EQUIP-DESC-CDE is assigned to VID-01-EQUIP-DESC-CDE
[Set Equipment Initialization]
The system processes equipment initialization information → The equipment initialization from GCUS-VID02-EQUIP-INIT is assigned to VID-02-EQUIP-INIT
[Set Equipment Number]
The system processes equipment number information → The equipment number from GCUS-VID03-EQUIP-NUM is assigned to VID-03-EQUIP-NUM
[Set Primary Seal Number]
The system processes primary seal number information → The primary seal number from GCUS-VID04-SEAL-NUM-1 is assigned to VID-04-SEAL-NUM
[Set Secondary Seal Number]
The system processes secondary seal number information → The secondary seal number from GCUS-VID05-SEAL-NUM-2 is assigned to VID-05-SEAL-NUM
[Set Load/Empty Status Code]
The system processes load/empty status information → The load/empty status code from GCUSRT-VID10-LOAD-EMPTY-CDE is assigned to VID-10-LOAD-EMPTY-STATUS-CDE
[Clean Segment Data]
The system performs data cleaning operations → All underscore characters in the VID segment are replaced with spaces
[Store VID Segment]
The system stores the segment for transmission → The VID segment is moved to transmission data and stored via Z1010-ISRT-GCSA9DP
[Create VC Segment]
The system creates a VC segment → A new VC segment is initialized with proper sequence numbering and segment structure
[Set VC Identifier to 'VC']
The system sets the segment identifier → The VC identifier field is set to 'VC ' (VC followed by space)
[Move Vehicle ID Number to VC-01]
The system assigns the vehicle ID data → The vehicle ID number from the current occurrence is moved to the VC-01-VEHICLE-ID-NUM field
[Replace Underscores with Spaces]
The system formats the segment for transmission → All underscore characters in the VC segment are replaced with space characters
[Store VC Segment in Database]
The system stores the segment → The VC segment is inserted into the transmission database as dependent segment data
[Description segments 2-12 have data?]
Processing multi-line commodity descriptions for segments 2-12 → Create N10 segment with quantity set to '0000000000' AND move description text to free form description field AND move marks and numbers to marks and numbers field AND store the N10 segment
[More description lines 13-500?]
Processing multi-line commodity descriptions for segments 13-500 → Create N10 segment with quantity set to '0000000000' AND move description text to free form description field AND set marks and numbers to '.' AND store the N10 segment
[Set quantity to '0000000000']
Creating an N10 segment for additional description lines → Set the quantity field to '0000000000' for all multi-line description segments
[Set marks and numbers to '.']
Creating N10 segments for extended description lines → Set the marks and numbers field to '.' as the default value
[Move Primary Marks and Numbers to First N10 Segment]
The system creates the first N10 segment → The marks and numbers data is moved from GCUS-N1003-MARKS-AND-NUM to N10-03-MARKS-AND-NUMBERS field
[Create Additional N10 Segments for Extra Marks]
The marks and numbers data at index I is not spaces AND the description data is also present → A new N10 segment is created with the marks and numbers moved to N10-03-MARKS-AND-NUMBERS field
[More Marks to Process?]
Index I is less than:
equal to 12 AND marks and numbers data exists at WS-N1003-OCCURS-X45(I)
description data exists at WS-DESC-X45(I)
→ The system continues processing and creates additional N10 segments for the remaining marks and numbers data
[Extract Hazmat Code]
The system extracts hazmat information → The hazardous material code from field H101 is moved to the H1 segment hazmat code field
[Extract Hazmat Description]
The system extracts hazmat information → The hazardous material description from field H104 is moved to the H1 segment description field
[Extract Contact Information]
The system extracts hazmat information → The hazardous material contact information from field H105 is moved to the H1 segment contact field
[Create H1 Segment]
The system creates an H1 segment → An H1 segment is created with identifier 'H1 ', all underscores are replaced with spaces, and the segment is prepared for database storage
[Store H1 Segment in Database]
The system stores the segment → The H1 segment is inserted into the database with an incremented sequence number and proper dependent segment structure
[Process H2 Additional Description]
The system checks for additional hazmat description → If H201 hazmat description field is not empty, an H2 segment is created with identifier 'H2 ', formatted by replacing underscores with spaces, and stored in the database with incremented sequence number
[Set H2 Segment Identifier]
The system sets up the segment identifier → The segment identifier is set to 'H2 ' to identify this as an H2 segment type
[Move Additional Hazmat Description to H2 Segment]
The system processes the additional hazmat description data → The additional hazmat description is moved to the H2-01 hazmat description field
[Clean Up Segment Format - Replace Underscores with Spaces]
The system performs format cleanup on the segment → All underscore characters in the H2 segment are replaced with space characters
[Store H2 Segment in EDI Transmission Data]
The system prepares the segment for EDI transmission → The H2 segment is moved to the EDI transmission data field
[Save H2 Segment to Database]
The system saves the segment to the database → The Z1010-ISRT-GCSA9DP routine is called to insert the H2 segment into the database
[LX Segment Creation]
The system begins creating a new LX segment → The LX segment data structure is cleared and set to spaces
[Sequence Management]
The system processes the line assignment segment → The sequence number is incremented by 1 and assigned to the segment
[LX Segment Creation]
The segment identifier needs to be set → The identifier is set to 'LX ' (LX followed by a space)
[Sequence Management]
The system creates an LX segment → The assigned line number counter is incremented by 1
[LX Segment Creation]
The assigned line number field needs to be populated → The line number is set to the fixed value '00001'
[Data Storage]
The segment is ready for transmission → The LX segment data is moved to the transmission data field
[Data Storage]
The segment needs to be persisted for EDI processing → The system performs an insert operation to store the segment in the database
[Update Manifest Record in Database]
A database update is required → The system performs a replacement update on the GCSUSRT segment using the GCCUSIO program with GCWUSIO-FUNC-REPL and GCWUSIO-SEG-GCSUSRT flags
[Set Amendment Type to DELETE]
The action type is DELETE (GCWS309-ACT-DELETE is true) → The amendment type code is set to delete a bill of lading (88-GCUS-M1303-DEL-A-BOL is set to TRUE)
[Update Amendment Data in Database]
The amendment type code setting process is complete → The system updates the GCSUSS01 segment in the database with the new amendment data
[Determine Transaction Type]
If the transmission type from the input parameters → The system assigns prefix 101 for GCX101 type, prefix 106 for GCX106 type, prefix 107 for GCX107 type, prefix 111 for GCX111 type, prefix 113 for GCX113 type, or default prefix 998 for any other or unknown transmission type
[Get Machine Time]
The system needs to create a unique transmission identifier → The system retrieves the current machine time and combines it with the transmission prefix to form the complete transmission number
[Handle Transmission Number Conflicts]
The database insert operation fails due to a duplicate transmission number → The system increments the transmission number by 1 and retries the insert operation until successful
[Retry Database Insert]
The transmission number is incremented by 1 → The system performs another database insert attempt with the new transmission number
[Set Sequence Number]
The system assigns a sequence number to the segment → The sequence number is incremented by 1 and assigned to the dependent segment sequence number field
[Move Segment Data to Transmission Buffer]
The system transfers the segment data to the transmission buffer → The formatted segment data is moved to the transmission data field of the dependent segment structure
[Call Database Insert Function]
The system calls the database insert function → The CIMS insert function is called with the database control block, GCA9-PCB, dependent segment data, and unqualified SSA to store the segment as a dependent record
[Process Follower Equipment Data]
Equipment data processing is required → The system processes VID equipment segments for the follower manifest
[Process Follower Commodity Data]
Commodity data processing is required → The system processes N10 commodity segments for the follower manifest
[Process Follower Hazmat Data]
Hazardous material data processing is required → The system processes H1-H2 hazmat segments for the follower manifest
[Skip GCX106 Transmission?]
The transmission type is GCX106 → Customer authorization validation is skipped and processing continues without validation checks
[Set Action = 'UPD']
The manifest operation action is UPDATE → The validation action code is set to 'UPD' for the customer authorization request
[Set Action = 'DEL']
The manifest operation action is DELETE → The validation action code is set to 'DEL' for the customer authorization request
[Set Action = 'ADD']
The manifest operation action is ADD → The validation action code is set to 'ADD' for the customer authorization request
[Set Action = 'ADD' Default]
The manifest operation action is not UPDATE, DELETE, or ADD → The validation action code defaults to 'ADD' for the customer authorization request

Structural Validations

[7:Delete Manifest Processing]
The EDI sent status is NULL:
MANUAL
→ Skip delete processing and exit the delete section
[10:M10 Manifest Header Processing]
The country code is CA, US, or MX → Use the existing country code, otherwise default to CA
[Valid UPDATE Transaction Type?]
The system checks the transmission type → Proceed with UPDATE processing only if transmission type is GCX111, GCX106, GCX113, GCX101, or GCX107; otherwise skip processing
[Set Flag: Don't Process EDI Send - Cargo Pending/Error]
The cargo status is RT10 CP cargo pending or RT10 CP cargo error → EDI send processing is disabled for this cargo
[Is CP Cargo Pending or Error?]
The cargo status is RT10 CP cargo pending:
the cargo status is RT10 CP cargo error
→ EDI processing should be disabled for this manifest
[Check EDI Status]
The system checks the current EDI sent status → If the manifest has not been sent electronically, update the status to electronic before proceeding
[Process N9 General References]
Creating N9 segments for non-OB and non-BN references → Exclude reference qualifiers OB, BN, KCM, FEN and empty spaces from processing
[Exclude Special Types?]
The qualifier is 'OB', 'BN', spaces, 'KCM', or 'FEN' → The reference is excluded from general N9 EDI segment creation
[Exclude Special Types?]
If the reference qualifier for general processing → References with qualifiers 'OB', 'BN', spaces, 'KCM', or 'FEN' are excluded from creating N9 EDI segments
[Check EDI Status]
The manifest EDI status is NULL or MANUAL → The delete processing is terminated and the system exits without performing any deletion operations
[Exclude Specific Types?]
The reference qualifier is 'OB' or 'BN' or 'KCM' or 'FEN' or is spaces → The reference is excluded from general N9 segment creation and processing continues to the next reference
[AES SED Data Present?]
The SED field is spaces or low-values → No N9 segment is created and processing continues to the next AES sequence
[Format Segment Data]
The system prepares the segment for EDI transmission → The system replaces all underscore characters with spaces in the P4 segment
[Set Default Amendment Code = '01']
The amendment code is spaces, low-values, or high-values → The system sets the amendment code to '01' as the default value
[Is Qualifier Valid?]
The reference qualifier is not spaces or empty → The reference is considered valid for N9 segment creation
[Check N1 Entity Data Available?]
The system checks if N1 entity data is not empty or spaces → The system proceeds to create N1 entity identification segment if data exists, otherwise skips entity processing
[Check N3 Address Data Available?]
The system checks if N3 address data is not empty or spaces → The system proceeds to create N3 address segment if data exists, otherwise continues to next segment check
[Check N4 Geographic Data Available?]
The system checks if N4 geographic data is not empty or spaces → The system proceeds to create N4 geographic segment if data exists, otherwise continues to contact information check
[Check PER Contact Data Available?]
The system checks if PER contact data is not empty or spaces → The system proceeds to create PER contact segment if data exists, otherwise completes entity processing
[Clean Special Characters]
The system formats the address segment for transmission → The system should replace all underscore characters with spaces in the N3 segment
[Clean Segment Data - Replace Underscores with Spaces]
The segment data needs to be cleaned for EDI transmission → All underscore characters in the N4 segment are replaced with spaces
[Extract Contact Name - First 23 Characters]
The contact name is being assigned to the PER segment → Only the first 23 characters of the contact name are used
[Map In-bond Type Code]
The internal in-bond type code is found in the conversion lookup table → The system maps the internal code to the corresponding EDI format code for M12 segment
[Process Marks and Numbers for Additional Lines]
Either the description field or marks and numbers field is empty or spaces → The system inserts a single dot '.' as a placeholder in the empty field to maintain proper segment structure
[Set Quantity to Zero]
The system sets the quantity field → The quantity field is set to '0000000000' to indicate no additional quantity counting
[H1 Hazmat Data Not Empty?]
The system checks if H1 hazmat data is not empty spaces → H1 segment creation proceeds if data exists or processing moves to next occurrence if empty
[H2 Additional Description Available?]
The system checks for H2 additional description data → H2 processing continues if description exists or processing moves to next occurrence if no H2 data available
[Check if Additional Description Exists]
The system checks for additional hazmat description → H2 processing continues only if H201 hazmat description is not empty or spaces
[Root Creation Successful?]
The database insert fails due to duplicate transmission number (status code is not space) → The transmission number is incremented by 1 and the root record creation is retried until successful
[Is Secondary SCAC Code = 'ZZZZ'?]
If the secondary SCAC code for EDI inclusion → If the secondary SCAC code equals 'ZZZZ' then exclude it from EDI transmission, otherwise include it in position M11-14-SCAC
[Is Third SCAC Code = 'ZZZZ'?]
If the third SCAC code for EDI inclusion → If the third SCAC code equals 'ZZZZ' then exclude it from EDI transmission, otherwise include it in position M11-15-SCAC
[Check if Additional Marks Exist?]
Processing marks entries starting from position 2 through position 12 → If marks data exists at the current position OR marks occurs data exists at the current position, the system proceeds to create N10 segments, otherwise it sets default marks field
[Check Equipment Data Available?]
The system checks for equipment data availability in GCSUSS05-VID-DATA → Processing continues to VID segment creation if data exists, otherwise VID processing is skipped
[Vehicle ID Number Not Empty?]
The system validates the vehicle ID number → VC segment creation proceeds if the ID is not spaces or low-values, otherwise continues to next occurrence
[Set Default Period if Empty]
The marks and numbers data at WS-N1003-OCCURS-X45 index I equals spaces → The N10-03-MARKS-AND-NUMBERS field is set to a period character '.'
[Check if Additional Hazmat Description Exists]
The system checks for additional hazmat description in the current occurrence → The system determines if H2 segment processing should proceed or be skipped
[Insert Successful?]
The database insertion fails due to a duplicate transmission number → The system increments the transmission number by 1 and retries the insertion process until a successful insertion occurs with a unique transmission number
[Transmission Record Created Successfully]
A database insert operation completes without status code conflicts → The transmission record creation process is considered successful and processing continues

As an EDI Gateway Service,
I want to orchestrate and execute all GCCS358C 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 A9RT Transmission Segment]
Creating a root transmission segment → The A9RT transmission segment should be initialized to clear any previous data
[Initialize ST Segment Structure]
The ST segment initialization process begins → The ST segment definition structure is initialized and the ST identifier is set to 'ST'
[Initialize M10 Segment Structure]
The system starts building the M10 segment → The M10 segment is initialized and the identifier is set to 'M10'
[Initialize P4 Segment Structure]
The system begins building the P4 segment → The P4 segment structure is initialized and the identifier is set to 'P4'
[Initialize Flat Car Processing Variables]
The flat car and container combination is identified → Initialize FLATCAR-VID-SEGMENT, IM-UNIT-VID-SEGMENT, and IM-UNIT-VID12-ELEMENT variables and store the current VID segment as flat car data
[Initialize VID Segment Structure]
The VID segment initialization is performed → The VID segment structure is initialized and the identifier is set to 'VID'
[Initialize MBL Segment Structure]
The system begins dummy MBL segment creation → The MBL segment structure is initialized to clear any previous data
[Initialize MBL Segment Structure]
The dummy MBL processing begins → The MBL segment structure is initialized to clear any previous data
[Initialize M13 Segment Structure]
The M13 segment initialization is triggered → The M13 segment structure is cleared and ready for data population
[Initialize VID Segment]
A new VID segment needs to be created → The system initializes the VID segment and sets the identifier to 'VID'
[Initialize Flat Car VID Segment]
The flat car and container pairing is identified → Initialize flat car VID segment, container VID segment, and container location element to prepare for data storage
[Initialize Container VID Segment]
Container VID segment needs to be paired with flat car → Initialize container VID segment, store container location ID, and prepare for flat car data transfer
[Initialize VID Segment Structure]
VID segment initialization is required → VID segment structure is cleared and ready for data population
[Initialize N9 Segment Structure]
The N9 segment creation process begins → The N9 segment structure is initialized to clear any previous data
[Initialize MBL Segment Structure]
The system needs to create a dummy MBL segment → The MBL segment structure should be initialized to empty values

Core Acceptance Criteria

[Build ST Header Segment]
If the post-emanifest flag in the train list → If post-emanifest is true, set destination to 'CACUSTOMS2-ST-O', otherwise set destination to 'CACUSTOMS-ST-O'
[Determine EDI Version Processing]
If the post-emanifest flag → If post-emanifest is true, use 5040 version processing (B231-LOAD-VID-MBL-5040), otherwise use 4040RAIL version processing (B230-LOAD-VID-MBL)
[Handle Special SCAC Assignment]
If the CCN key prefix → If CCN key starts with '2156', set SCAC to 'CFFO', otherwise set SCAC to 'CPRS'
[Handle Revenue Transit Status]
The system processes the Master Bill of Lading segment → Set BOL/Waybill to 'NA', set response code to 'N', and if post-emanifest, set exception code to '08'
[Process Haulage Rights]
The system processes the Master Bill of Lading segment → Set SCAC to the haulage rights SCAC code and set response code to 'N'
[Build Dummy MBL Segment]
No cargo key exists for the equipment but amendment processing is required → Create a dummy MBL segment with SCAC 'CPRS', BOL/Waybill 'NA', and exception code '06'
[Build M13 Amendment Segment]
The system needs to document the amendment → Create M13 segment with SCAC 'CPRS', location ID from station code, BOL/WB number from train key, and amendment code '60'
[Build N9 Reference Segment]
The system creates reference information → Create N9 segment with reference qualifier '76', reference number 'EDT', date from EDA with machine century, time from ETA with '00' seconds, and time code 'ES'
[Generate Transmission Number]
If the processing mode → If foreground mode, use prefix 147. If foreground-02 mode, use prefix 2. If background mode, use prefix 146. Append machine time to create unique transmission number
[Save Current Program Name]
The system begins processing the transaction → The current program name from the control block is saved to a temporary variable
[Set Module Name in Control Block]
The EDI 358 processing begins → The module name is assigned to the program field in the control block
[Continue to Main Processing]
A valid processing mode is confirmed → The AA200-358-PROCESS routine is executed to handle the EDI transaction processing
[Restore Program Name]
The system is preparing to return control to the caller → The saved program name is restored to the control block program field
[Set Prefix to 147 Foreground Mode]
The processing mode is set to foreground (GCWS358C-FOREGROUND is true) → The transmission prefix should be set to 147
[Set Prefix to 2 Foreground-02 Mode]
The processing mode is set to foreground-02 (GCWS358C-FOREGROUND-02 is true) and not foreground mode → The transmission prefix should be set to 2
[Set Prefix to 146 Background Mode]
The processing mode is neither foreground nor foreground-02 (default to background) → The transmission prefix should be set to 146
[Get Current Machine Time]
The system needs to create a unique transmission number → The current machine time should be retrieved and combined with the prefix to form the transmission number
[Set Prefix 147 for Foreground]
The processing mode is foreground → The transmission prefix should be set to 147
[Set Prefix 2 for Foreground-02]
The processing mode is foreground-02 → The transmission prefix should be set to 2
[Set Prefix 146 for Background]
The processing mode is background → The transmission prefix should be set to 146
[Use Machine Time as Counter]
A transmission number needs to be generated → The machine time should be used as the transmission number base
[Set Transaction Set to 358]
Setting up the transmission for customs manifest data → The transaction set should be set to '358'
[Insert Root Segment to Database]
The segment is ready for database storage → The root segment should be inserted into the GCA9RT transmission database
[Set Transaction Code to '358']
The transaction code needs to be assigned → The transaction code is set to '358' to identify this as a customs manifest transaction
[Check Post-Emanifest Flag]
The post-emanifest flag is evaluated → If post-emanifest is true, the destination is set to 'CACUSTOMS2-ST-O', otherwise the destination is set to 'CACUSTOMS-ST-O'
[Prepare Segment for Transmission]
The segment needs to be prepared for database insertion → The ST segment data is moved to the transmission data structure and the dependent segment is initialized
[Insert ST Segment into Database]
The database insertion process is invoked → The ST segment is inserted into the GCA9DP transmission database with proper sequencing
[Set SCAC Code to 'CPRS', Assign Standard CPRS SCAC Code]
The SCAC code needs to be assigned → The SCAC code is set to 'CPRS'
[Set Transport Type Code to 'R']
The transport type code needs to be assigned → The transport type code is set to 'R' for rail
[Set Country Code to 'US']
The country code needs to be assigned → The country code is set to 'US'
[Set Vessel Name from Train Key]
The vessel name needs to be assigned → The vessel name is set to the value from the train key
[Convert Current Date to Julian Format]
The flight/voyage number needs to be calculated → The system converts the current date from Gregorian to Julian format using date conversion service
[Set Manifest Type Code to 'S']
The manifest type code needs to be assigned → The manifest type code is set to 'S' for ship manifest
[Set Reference Number to 'TRAIN']
The reference number needs to be assigned → The reference number is set to 'TRAIN'
[Set Purpose Code to '00' - Add]
The transaction purpose code needs to be determined → The purpose code is set to '00'
[Set Purpose Code to '04' - Change]
The transaction purpose code needs to be determined → The purpose code is set to '04' and amendment flag is set to false
[Set Purpose Code to 'CO' - Amendment]
The transaction purpose code needs to be determined → The purpose code is set to 'CO' and amendment flag is set to true
[Set Purpose Code to '03' - Delete]
The transaction purpose code needs to be determined → The purpose code is set to '03'
[Set Application Type to '27']
The application type needs to be assigned → The application type is set to '27'
[Insert M10 Segment into Transmission]
The segment needs to be added to the transmission → The M10 segment is inserted into the transmission data queue
[Retrieve Canadian Station Information]
The system needs to build the P4 location segment → The system retrieves station information using the train's departure station code
[Set Canadian Station Code as Location ID]
The P4 location segment is being populated → The Canadian station code is assigned as the location identifier
[Set Estimated Departure Year, Set Estimated Departure Month, Set Estimated Departure Day]
The P4 location segment date fields need to be populated → The estimated departure year, month, and day are set from the train list data
[Copy Location ID to ID Code Field, Set Time Field to Spaces]
The remaining P4 segment fields need to be set → The location identifier is copied to the ID code field and the time field is set to spaces
[Insert P4 Segment into Transmission]
The segment needs to be added to the transmission data → The P4 segment is inserted into the transmission data structure
[Extract Equipment Type, Initial, Number]
Equipment data needs to be extracted for VID segment creation → Equipment type, initial, and number are extracted from GCWB4TL fields at SUB-TL position
[Handle Flat Car Logic for Container Cars]
Current equipment is a flat car type (BG, CA, ET, GS, ID, LO, RR, SK, TN) and next equipment is a container type (CC, CH, CM, CN, CX, CZ, LS, OT, PL, PT, RL, RT, TL) → Store flat car information and process both flat car and container as a combined unit with special VID segment handling
[Create VID Segment]
VID segment needs to be created for the equipment → VID segment is initialized and populated with equipment identifier 'VID', equipment description code, equipment initial, equipment number, and load/empty status code
[Create N9 Reference Segment for First Equipment]
Processing the first equipment in the list → Create N9 segment with identifier 'N9', reference number qualifier '76', reference number 'EDT', estimated departure date, estimated time of arrival, and time code 'ES'
[Process Bill of Lading if Loaded]
Equipment processing requires bill of lading information → Process MBL segment with cargo details, SCAC code, bill of lading number, and response codes
[Process Bill of Lading or Dummy MBL]
Equipment has cargo key → Process regular MBL segment, otherwise if this is the first equipment and an amendment, create dummy MBL with exception code '06' and M13 amendment segment
[Extract Equipment Type from GCWB4TL-VID01-EQUIPMENT-TYPE]
Processing equipment data for VID segment creation → The equipment type code should be extracted from the train list and stored in the VID equipment description code field
[Extract Equipment Initial from GCWB4TL-VID02-EQUIPMENT-INIT]
Processing equipment data for VID segment creation → The equipment initial should be extracted from the train list and stored in the VID equipment initial field
[Extract Equipment Number from GCWB4TL-VID03-EQUIPMENT-NUM]
Processing equipment data for VID segment creation → The equipment number should be extracted from the train list and stored in the VID equipment number field
[Does Flat Car Data Exist?]
The current equipment is a container type and FLATCAR-VID-SEGMENT is populated → Store current VID segment as container unit, preserve location ID, process flat car segment first, then process container unit segment, and generate MBL segment if equipment is loaded with cargo
[Process Equipment Normally]
The equipment is not part of a flat car-container sequence or is processed individually → Generate VID segment using standard processing and create MBL segment if equipment is loaded with cargo
[Current Equipment is Container Type? AND Flat Car Segment Exists?]
The current equipment type is CC, CH, CM, CN, CX, CZ, LS, OT, PL, PT, RL, RT, or TL AND a flat car segment has been previously stored → Store current VID as container unit segment, copy container location ID to flat car, and process both flat car and container unit VID segments
[Process Equipment Normally]
The equipment is not part of a flat car-container combination:
is the last equipment in the list
→ Process the equipment using standard VID segment processing and load MBL segment if equipment is loaded with cargo
[Set Equipment Description Code from Train List]
Equipment description code needs to be set → The equipment description code from the train list is assigned to VID-01-EQUIP-DESC-CDE
[Set Equipment Initial from Train List]
Equipment initial needs to be set → The equipment initial from the train list is assigned to VID-02-EQUIP-INIT
[Set Equipment Number from Train List]
Equipment number needs to be set → The equipment number from the train list is assigned to VID-03-EQUIP-NUM
[Equipment Marked as Loaded?]
Equipment is marked as loaded AND cargo key is present → Load status is set to 'L' (Loaded)
[Set Load Status to 'E']
Equipment is not marked as loaded:
cargo key is not present
→ Load status is set to 'E' (Empty)
[Insert VID Segment to Database]
VID segment is ready for transmission → VID segment is inserted into the transmission database for EDI processing
[CCN Key = '6105I'?]
The cargo CCN key starts with '6105I' → The system skips all MBL segment processing and proceeds to the next step
[CCN starts with '2156'?]
The CCN key starts with '2156' → The system sets the SCAC code to 'CFFO', otherwise sets it to 'CPRS'
[Set CCN as Bill of Lading Number]
The equipment has a valid CCN key → The system assigns the CCN key as the Bill of Lading/Waybill number
[Set Condition Response Code]
The equipment record contains a condition response code → The system copies the condition response code to the MBL segment
[Response Code Empty?]
The Bill of Lading number is not empty → The system sets the response code to 'Y', otherwise sets it to 'N'
[First Equipment and Amendment?]
This is the first equipment item being processed → The system creates an M13 amendment segment with amendment code '60'
[No CCN and Amendment?]
The equipment has no CCN key and this is the first equipment → The system creates a dummy MBL segment with Bill of Lading 'NA', exception code '06', and follows with M13 amendment segment
[CCN Key Starts with '2156'?]
The system processes the MBL segment for SCAC code assignment → If the CCN key starts with '2156', assign SCAC code 'CFFO', otherwise assign SCAC code 'CPRS'
[Check if Amendment Processing Required]
The system checks if this is the first equipment item (SUB-TL = 1) and the amendment flag is set to true → Amendment processing should be initiated for MBL segment creation
[Process Regular MBL Segment]
The system processes the MBL segment for this equipment → The regular MBL processing function (B240-LOAD-MBL-SEG) should be invoked
[Create Dummy MBL Segment]
The system determines that a dummy MBL is needed for amendment purposes → The dummy MBL creation process (B250-LOAD-DUMMY-MBL-SEG) should be initiated
[Set MBL Identifier to 'MBL']
The system initializes the MBL segment structure → The MBL identifier field should be set to 'MBL'
[Set SCAC Code to 'CPRS']
The system sets the SCAC (Standard Carrier Alpha Code) → The SCAC code should be set to 'CPRS' for Canadian Pacific Railway
[Set Bill of Lading to 'NA']
The system sets the bill of lading/waybill number → The bill of lading field should be set to 'NA' indicating not applicable
[Set Exception Code to '06']
The system sets the exception code for the MBL → The exception code should be set to '06' to indicate this is a dummy MBL for amendment processing
[Insert Dummy MBL into Transmission]
The system processes the MBL for transmission → The dummy MBL segment should be inserted into the transmission data structure (A9DP-TRANSMISSION-DATA)
[Create M13 Amendment Segment]
The system creates amendment documentation → An M13 amendment segment should be created and initialized
[Set M13 Identifier to 'M13']
The system initializes the M13 segment structure → The M13 identifier field should be set to 'M13'
[Set SCAC Code to 'CPRS']
The system sets the SCAC (Standard Carrier Alpha Code) for the amendment → The SCAC code should be set to 'CPRS' for Canadian Pacific Railway
[Set Location ID from Station Code]
The system sets the location identifier for the amendment → The location ID should be set to the Canadian station code (GCSTBRT-SC-CDN-STAT-CODE-X)
[Set Bill/Waybill Number from Train Key]
The system sets the bill/waybill number for the amendment → The bill/waybill number should be set to the train key (GCWB4TL-KEY)
[Set Amendment Code to '60']
The system sets the amendment code → The amendment code should be set to '60' to indicate the specific type of manifest amendment
[Insert M13 Amendment into Transmission]
The system processes the M13 for transmission → The M13 amendment segment should be inserted into the transmission data structure (A9DP-TRANSMISSION-DATA)
[Amendment MBL Processing Complete]
The system completes the amendment processing workflow → The amendment MBL processing should be marked as complete and control should return to the main processing flow
[Set MBL Identifier to 'MBL']
The segment identifier needs to be set → The MBL identifier is set to 'MBL'
[Set Bill of Lading to 'NA']
The bill of lading waybill number needs to be set → The bill of lading waybill is set to 'NA'
[Clear Load Found Flag]
The load found flag needs to be reset → The load found flag is cleared to spaces
[Set Exception Code to '06']
The exception code needs to be assigned → The exception code is set to '06'
[Insert MBL Segment into Transmission]
The segment needs to be added to the transmission → The MBL segment is inserted into the transmission data structure
[Build M13 Amendment Segment]
Amendment processing continues → The M13 amendment segment is built and processed
[Set Bill of Lading to 'NA']
The bill of lading waybill field needs to be populated → The bill of lading waybill is set to 'NA'
[Clear Load Found Flag]
The load found flag needs to be reset → The load found flag is set to spaces
[Configure Exception Code '06']
The exception code needs to be configured → The exception code is set to '06'
[Insert MBL Segment into Transmission]
The segment needs to be added to the transmission → The MBL segment is moved to transmission data and inserted into the data stream
[Trigger M13 Amendment Segment Creation]
Amendment processing is required → The M13 amendment segment creation process is triggered
[Set M13 Identifier]
The segment identifier needs to be set → The M13 identifier is set to 'M13'
[Set SCAC Code to CPRS]
The SCAC code field needs to be set → The SCAC code is set to 'CPRS'
[Set Location ID from Station Code]
The location ID field needs to be populated → The location ID is set to the Canadian station code from GCSTBRT station table
[Set Bill of Lading/Waybill Number from Train Key]
The bill of lading/waybill number field needs to be populated → The bill of lading/waybill number is set to the train key from GCWB4TL
[Set Amendment Code to 60]
The amendment code field needs to be set → The amendment code is set to '60'
[Insert M13 Segment into Transmission]
The segment needs to be added to the transmission → The M13 segment is inserted into the A9DP transmission data structure
[Check Post-Emanifest Flag]
The system checks the post-emanifest flag (GCWB4TL-POST-EMANIFEST) → The system evaluates the flag to determine routing to appropriate EDI version processing
[Route to 5040 Version Processing]
The post-emanifest flag (GCWB4TL-POST-EMANIFEST) is set to true → The system routes processing to B231-LOAD-VID-MBL-5040 for enhanced equipment processing with 5040 version capabilities
[Route to 4040RAIL Version Processing]
The post-emanifest flag (GCWB4TL-POST-EMANIFEST) is not set or is false → The system routes processing to B230-LOAD-VID-MBL for standard equipment processing with 4040RAIL version capabilities
[Process All Equipment in Train List]
The system begins equipment processing → The system iterates through all equipment entries (SUB-TL) in the train list until an empty equipment ID is encountered, processing each equipment entry using the selected processing method
[Get Cargo Information for Equipment]
The system processes the equipment for manifest creation → The system retrieves the corresponding cargo information using the CCN key and sets cargo found flag to true, or initializes empty cargo segment if no cargo exists
[Set Equipment Type from Train List]
Equipment type information is available in the train list → The system copies the equipment type code from the train list to the VID equipment description code field
[Set Equipment Initial from Train List]
Equipment initial information is available in the train list → The system copies the equipment initial from the train list to the VID equipment initial field
[Set Equipment Number from Train List]
Equipment number information is available in the train list → The system copies the equipment number from the train list to the VID equipment number field
[Store Flat Car VID Data]
The flat car VID segment is created → The system stores the flat car VID segment data and initializes container VID structures for subsequent processing
[Create Flat Car VID with Container Location]
Container VID segment is being created → The system creates a flat car VID segment with container location information, then creates the container VID segment, and processes MBL segment if equipment is loaded with cargo
[Create Standard VID Segment]
VID segment processing is performed → The system creates a standard VID segment and processes MBL segment if equipment is loaded with cargo
[Equipment Has CCN and is Loaded?]
If MBL processing requirements → The system creates an MBL segment if the equipment is loaded and has an associated CCN key (cargo control number)
[Store Flat Car Information]
The flat car and container car pairing is identified → The flat car VID segment is stored for later processing with the container car's location information
[Create VID Segment for Flat Car]
The container car is processed and has location information → Two VID segments are created - one for the flat car using the container's location ID and one for the container car
[Process as Regular Equipment]
The equipment is processed individually → A single VID segment is created for the equipment and MBL segment is created if the equipment is loaded with cargo
[Create MBL Segment if Loaded]
The equipment VID segments are created for the pairing → An MBL segment is created for the loaded equipment with cargo details
[Store Flat Car Information in FLATCAR-VID-SEGMENT]
Flat car-container pairing condition is met → Current VID segment information is stored in FLATCAR-VID-SEGMENT for later retrieval and container information storage areas are initialized
[Process Flat Car with Container Location]
Container location information is captured and flat car data is retrieved from storage → Flat car VID segment is processed with container location ID and both segments are transmitted as a paired unit
[Generate MBL Segment for Pair]
Container is loaded and has valid cargo key (CDA-CCN-KEY not is empty) → MBL segment is generated for the paired equipment unit
[Process as Regular Equipment]
Equipment is not a flat car followed by container, or is not a container with stored flat car, or is at end of equipment list → Equipment VID segment is transmitted as individual unit and MBL is generated if equipment has loaded cargo
[Store Current VID as Flat Car]
The current equipment is a flat car type → Copy the current VID segment data to the flat car VID segment storage
[Does Flat Car VID Exist?]
The flat car VID segment is not empty → Process the container as part of a flat car-container pair
[Copy Flat Car VID to Current VID]
Processing flat car-container pair → Copy flat car VID segment data to current VID segment
[Apply Container Location ID to Flat Car]
Processing flat car-container pair → Move the stored container location ID to the VID location field
[Insert Flat Car VID Segment]
Flat car-container pair processing is complete → Insert the flat car VID segment into the transmission data
[Reset VID to Container Data]
Processing the container portion of flat car-container pair → Initialize current VID segment and copy container VID segment data to current VID segment
[Insert Container VID Segment]
Container portion of flat car-container pair is ready → Insert the container VID segment into the transmission data
[Equipment Has CCN and is Loaded?]
The equipment is loaded and has a cargo control number (CCN) that is not spaces → Process the MBL segment for the container
[Process MBL Segment for Container]
MBL processing is required for the container → Execute MBL segment loading procedure for the container
[Insert Single VID Segment]
VID segment is populated and not empty → Insert the VID segment into the transmission data
[Equipment Has CCN and is Loaded?]
The equipment is loaded and has a cargo control number (CCN) that is not spaces → Process the MBL segment for the equipment
[Process MBL Segment]
MBL processing is required for the equipment → Execute MBL segment loading procedure for the equipment
[CCN Key = '6105I'?]
The CCN key starts with '6105I' → Skip MBL segment generation and check if first equipment requires amendment processing
[CCN starts with '2156'?]
The CCN starts with '2156' → Set SCAC code to 'CFFO', otherwise set SCAC code to 'CPRS'
[Set CCN as Bill of Lading Number]
The equipment has a valid CCN key → Set the CCN key as the bill of lading waybill number in the MBL segment
[Set Condition Response Code]
The equipment record contains a condition response code → Set the MBL condition response code to the equipment's condition response code value
[Response Code Empty?]
The bill of lading waybill number is not empty → Set response code to 'Y', otherwise set response code to 'N'
[Cargo Status = 'R' 'Revenue'?]
The cargo in-transit status is 'R' (Revenue) → Set bill of lading to 'NA', set response code to 'N', and if post-emanifest then set exception code to '08'
[Haulage Rights Exist?]
The cargo has haulage rights defined → Set SCAC code to the haulage rights SCAC and set response code to 'N'
[First Equipment & Amendment?]
This is the first equipment (SUB-TL = 1) and the transaction is an amendment → Generate an M13 amendment segment with amendment code '60'
[Check CCN Key Prefix]
If the CCN key prefix during MBL segment creation → CFFO SCAC code is assigned if CCN starts with '2156', otherwise CPRS SCAC code is assigned
[Haulage Rights Exist?]
The cargo has haulage rights defined with a specific SCAC code → The haulage rights SCAC code overrides the standard CCN-based SCAC assignment and response code is set to 'N'
[Set Exception Code '08']
The system processes the MBL segment for this revenue transit cargo → The exception code should be set to '08' to indicate post-emanifest revenue transit processing
[Override Bill of Lading to 'NA']
The system processes the MBL segment → The bill of lading waybill field should be set to 'NA' regardless of the original cargo CCN key
[Set Response Code to 'N']
The system processes the MBL segment → The yes/no response code should be set to 'N' to indicate negative response
[Set Equipment Identifier to 'VID']
Equipment identifier needs to be set → VID identifier is set to 'VID'
[Copy Equipment Type from Train List]
VID segment requires equipment type → Equipment type is copied from train list VID01 field to VID equipment description code
[Copy Equipment Initial from Train List]
VID segment requires equipment initial → Equipment initial is copied from train list VID02 field to VID equipment initial
[Copy Equipment Number from Train List]
VID segment requires equipment number → Equipment number is copied from train list VID03 field to VID equipment number
[Insert VID Segment to Database]
VID segment insertion is performed → VID segment is stored in transmission database with proper sequence number
[Process N9 and MBL Segments]
Associated segment processing is required → N9 reference segments and MBL bill of lading segments are processed based on equipment and cargo conditions
[Equipment Marked as Loaded?]
The equipment load indicator shows loaded status → Check for cargo documentation to confirm load status
[Set Status to 'E' - Empty]
Equipment load indicator shows empty status → Set equipment status to 'E' for empty
[Set Reference Qualifier to '76']
The reference qualifier needs to be assigned → The reference qualifier is set to '76'
[Set Reference Number to 'EDT']
The reference number field needs to be assigned → The reference number is set to 'EDT'
[Extract Departure Date from Train Data]
The N9 segment date field needs to be populated → The departure date from train data is extracted and assigned to the N9 date field positions 3-8
[Format Date with Century Prefix]
The date is being formatted for the N9 segment → The machine century is added to positions 1-2 of the N9 date field
[Extract Departure Time from Train Data]
The N9 segment time field needs to be populated → The departure time from train data is extracted and assigned to positions 1-4 of the N9 time field
[Set Time Code to 'ES' - Eastern Standard]
The time code field is being assigned → The time code is set to 'ES' for Eastern Standard time
[Insert N9 Segment into Transmission]
The segment needs to be added to the transmission → The N9 segment is inserted into the transmission data structure and the dependent segment insertion process is performed
[CCN Key starts with '6105I'?]
The cargo control number (CCN) key starts with '6105I' → The system skips MBL segment creation and proceeds to check for amendment processing requirements
[CCN starts with '2156'?]
The cargo control number starts with '2156' → The system sets the SCAC code to 'CFFO', otherwise it sets the SCAC code to 'CPRS'
[Set CCN as Bill of Lading Number]
The equipment has an associated cargo control number → The system sets the CCN as the bill of lading waybill number
[Set Condition Response Code from Equipment]
Equipment data contains a condition response code → The system transfers the equipment condition response code to the MBL segment
[Response Code Empty?]
The bill of lading waybill number is present → The system sets the response code to 'Y', otherwise it sets the response code to 'N'
[Haulage Rights Exist?]
The cargo has haulage rights with a haulage rights SCAC code → The system overrides the SCAC code with the haulage rights SCAC and sets the response code to 'N'
[First Equipment and Amendment?]
This is the first equipment item being processed and the transaction is an amendment → The system creates an M13 amendment segment with amendment code '60'
[Set Exception Code '08']
The MBL segment is being created for the cargo → The system sets exception code '08' in the MBL segment
[Continue MBL Processing]
The MBL segment is being processed → The system sets the BOL waybill field to 'NA'
[Continue MBL Processing]
The MBL segment response code is being determined → The system sets the yes/no response code to 'N'
[Handle Special SCAC Assignment - Assign CFFO SCAC for CCN starting with 2156, otherwise use CPRS]
If the CCN prefix to determine the appropriate SCAC code → If the CCN starts with '2156', assign CFFO SCAC code, otherwise assign CPRS SCAC code to the MBL segment
[Set MBL Identifier to 'MBL']
The segment identifier needs to be set → The MBL identifier should be set to 'MBL'
[Set SCAC Code to 'CPRS']
The SCAC code needs to be assigned → The SCAC code should be set to 'CPRS'
[Set Bill of Lading to 'NA']
The bill of lading number needs to be set → The bill of lading should be set to 'NA' to indicate not applicable
[Set Exception Code to '06']
The exception code needs to be assigned → The exception code should be set to '06'
[Insert MBL Segment into Transmission Data]
The segment needs to be added to the transmission → The MBL segment should be inserted into the transmission data structure
[Build M13 Amendment Segment]
Amendment processing continues → An M13 amendment segment should be created
[Set M13 Identifier]
The segment identifier needs to be set → The M13 identifier field is populated with 'M13'
[Set SCAC Code to CPRS]
The SCAC code needs to be assigned → The SCAC code field is populated with 'CPRS'
[Set Location ID from Canadian Station Code]
The location identifier needs to be populated → The location ID field is populated with the Canadian station code from the station reference table
[Set Bill of Lading/Waybill Number from Train Key]
The bill of lading/waybill number needs to be assigned → The bill of lading/waybill number field is populated with the train key identifier
[Set Amendment Code to 60]
The amendment code needs to be assigned → The amendment code field is populated with '60' to indicate train amendment
[Insert M13 Segment into Transmission]
The M13 segment needs to be added to the transmission → The M13 segment is inserted into the transmission data structure for EDI processing
[Store Canadian Station Code]
The station lookup operation completes successfully → The table segment containing the Canadian station code is stored for subsequent processing
[Set EDI Send Function Name]
The EDI send function is being prepared → The system sets the EDI send function name flag to true to identify the correct function type
[Set Security Parameters]
Security parameters need to be configured → The system sets the security byte to high-values to establish maximum security level
[Set Transmission Number]
The EDI transmission structure is being populated → The system assigns the workspace transmission number to the EDI transmission number field
[Prepare Message Output]
The message needs to be formatted for output transmission → The system moves the GCX121 input data to the message output text field
[Set Function Length]
Function length parameters need to be configured → The system sets the EDI send function length flag to true
[Insert Purge Message]
The message needs to be queued for transmission → The system calls the purge message insertion process to queue the message
[Set Security Parameters]
Security parameters need to be established → The security byte should be set to high-values for maximum security
[Prepare Log Entry for Transmission]
The log entry needs to be prepared for transmission → The complete log input structure should be moved to the message output text field
[Send Log Entry to System]
The message length needs to be specified → The log update function length flag should be set to true to indicate proper message sizing
[Send Log Entry to System]
The log entry needs to be transmitted → The system should Execute the insert purge message operation to send the log entry to the logging system
[Database Insert Failed?]
The database insert fails with a non-space status code → Increment the transmission number by 1 and retry the insert operation until successful
[Message Write Failed?]
The message write operation fails with a non-zero return code → Build message write error and terminate processing with error handler

Structural Validations

[Valid Processing Mode?]
The system checks the processing mode flags → If none of the valid processing modes (foreground, background, or foreground-02) are set, the system sets wrong FB indicator and exits processing
[Retrieve Station Information]
The system looks up the station code in the station table → If station code is not found or returns '0000', generate error message indicating station not found. Otherwise, use the retrieved station information
[Retrieve Cargo Information]
The system attempts to retrieve cargo information → If cargo root is not found, generate error message indicating cargo not found for CCN. Otherwise, set cargo flag to true and use retrieved cargo information
[Check Processing Mode]
The system checks the processing mode configuration → The transaction must be set for foreground, background, or foreground-02 mode, otherwise processing is terminated with an error indicator
[Increment Transmission Number]
The transmission number already exists in the database → The transmission number should be incremented by 1 and insertion should be retried
[Current Equipment is Flat Car Type? AND Next Equipment is Container Type?]
The current equipment type is BG, CA, ET, GS, ID, LO, RR, SK, or TN AND the next equipment type is CC, CH, CM, CN, CX, CZ, LS, OT, PL, PT, RL, RT, or TL → Initialize flat car processing variables and store current VID as flat car segment for paired processing
[Equipment has CCN?]
The system checks the CDA-CCN-KEY field for the equipment → If the CCN key is not spaces, the equipment has cargo data, otherwise it has no cargo data
[Is Stored Flat Car Available?]
FLATCAR-VID-SEGMENT contains previously stored flat car information (not is empty) → Stored flat car is available for pairing and container pairing process is initiated
[Generate Error Message]
The system cannot access the Canadian cargo database or encounters retrieval failures → The system generates an error message indicating cargo retrieval failure and terminates processing
[Generate Station Not Found Error]
The system processes the lookup failure → An error message is generated containing 'SC TABLE ENTRY FOR [station] NOT FOUND RC=' with the station identifier and return code
[Clear Message Field]
The message field needs to be initialized → The message field should be set to spaces to ensure clean data
[Station Table Entry Found?]
The station table entry is not found:
the Canadian station code is '0000'
→ Build error message with station identifier and terminate processing with error handler
[Cargo Record Found?]
The cargo record is not found in the database → Build error message with the cargo control number and terminate processing with error handler
[Call Error Handler CERR]
Error message has been built for the specific error condition → Call the CERR error handling program to terminate processing

As an EDI Gateway Service,
I want to orchestrate and execute all GCCUSCN2 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 Loop Counter J = 1]
P5 location processing begins → Loop counter is initialized to 1 to start processing from first occurrence
[Initialize Location ID to '?']
The system begins location ID conversion processing → The M11 location ID field is set to all question marks as default value

Core Acceptance Criteria

[Segment ID Type?]
Processing conversion is initiated → System should route to P4 processing for 'P4', P5 processing for 'P5', M11 processing for 'M11', M12 processing for 'M12', Broker processing for 'BRO', N10 processing for 'N10', or Hazardous Material processing for 'HAZ'
[2:Process P4 Border Crossing Data]
Location ID name is not empty → System should lookup SE and MC tables, and if location is border port with crossing point implemented, extract US state exit code positions 2-4 as location ID, otherwise set location ID to question marks
[3:Process P5 Port Location Data]
Each location search key is not empty → System should lookup SD table for each key and assign corresponding port code, or set to question marks if not found
[4:Process M11 Origin Location Data]
Either location name or province/state code is not empty → System should first try combined lookup in SK table, if not found try province/state code alone, and assign city code if found or question marks if not found
[5:Process M12 Destination Location Data]
Location 1 name is not empty:
route is US-Canada-US with no P4 location
location 2 name is not empty
→ System should lookup SD table for location 1, clear location 2 for US-Canada-US routes without P4, or lookup SK table then KS table as fallback for location 2
[6:Process Broker Information]
Broker name is empty, unknown, not required, or valid name → System should continue for empty, clear codes for unknown/not required, or lookup BK table for valid names and extract district/office/filer codes with office code cleared if '00'
[7:Process N10 Commodity Data]
Commodity code exists and either description is empty or harmonized code is empty → System should validate numeric commodity code, lookup CMDTY table for description, and lookup harmonized codes with fallback to HZCMD table if needed
[10:Process Hazardous Material Data]
Hazmat commodity code is not empty → System should validate numeric code, lookup HZCMD table for description, and extract UN codes based on regulatory authority priority
[Lookup SE Table - Border Crossing Points]
SE table lookup is performed using the location ID name → Border crossing point data is retrieved if found in SE table
[Lookup MC Table - Border Port Information]
MC table lookup is performed using the location ID name → Border port data is retrieved if found in MC table
[Store SE segment data]
The system processes the successful lookup result → The system should move the retrieved table segment data to SE segment storage area
[Clear SE segment data]
The system handles the lookup failure → The system should clear the SE segment data by setting it to spaces
[Retrieve SE Table Data, Retrieve MC Table Data]
The system retrieves SE table data for crossing point information and MC table data for border crossing details → Both SE and MC table segments are populated with reference data for the specified location
[Is Border Port = 'Y'?]
The system checks the border port indicator in the MC segment → The location is classified as a border port if the MC border port field equals 'Y', otherwise it is not considered a border port
[Is Crossing Point Implemented?]
If the crossing point implementation status from the SE segment → The crossing point is considered implemented if the SE crossing point implemented flag is true, enabling US status exit code extraction
[Set Port Code from SD Table Result]
System processes the successful lookup result → Port code from SD table segment is assigned to P5 location port code field for occurrence J
[Extract Port Code from SD Segment]
The system processes the returned SD table segment → The port code value is extracted from the SD segment data structure
[Set Port Code in Output Field]
The system updates the output data structure → The extracted port code is moved to the designated port code output field
[Clear SD Segment Data]
The system handles the lookup failure → The SD segment data is cleared to spaces to indicate no valid data was retrieved
[Combine Location Name + Province/State Code]
The system prepares to search the SK table → A combined search key is constructed by concatenating the origin location ID name and origin province/state code
[Combine Location Name + Province/State Code into Search Key]
Both location name and province/state code are provided → System concatenates location name and province/state code into a single search key
[Receive Location Name and Province/State Code]
Location name is not empty:
province/state code is not empty
→ System initiates location ID lookup process and initially sets location ID to '????'
[Extract City Code from SK Record]
The system processes the retrieved SK table record → The city code is extracted from the SK table record segment
[Extract Port Code from SD Table]
The system processes the retrieved SD table data → The system extracts the port code from the SD table segment
[Clear SK Table Segment]
The system performs cleanup operations → SK table segment data is cleared to spaces
[Extract City Code from KS Table]
The lookup is successful (return flag equals '0') → The city code should be extracted from the KS table segment and used to update Location ID2, and the location name should be updated from the KS table name field
[For Each Commodity Code]
Processing N10 commodity data → System loops through each commodity code entry from 1 to maximum occurrences by sequence
[Table Data Retrieved Successfully]
The system processes the successful lookup result → The retrieved table segment data is moved to the appropriate working storage area for use by the calling process
[Table Data Not Found]
The system processes the unsuccessful lookup result → The table segment area is cleared to spaces to indicate no data was found
[Extract 4-digit code from US Status Exit Code]
The location is identified as a border port and crossing point is implemented → Extract characters 2-4 from the MC US state exit code and assign to P401 location ID
[Move port code to output field]
The port code is found in the SD table → Move the SD port code to the P503 location ID port code field
[Move city code to output field]
The city code is found in the SK table → Move the SK city code to the M1102 location ID field
[Format District Code]
The broker information is found in the BK table → Move the BK broker district code to the RT02 district code field
[Format Office Code]
The broker information is found in the BK table → Move the BK broker office code to the RT02 office code field
[Format Filer Code]
The broker information is found in the BK table → Move the BK broker filer code to the RT02 filer code field
[Move commodity name to description field]
The commodity information is found in the CMDTY table → Move the commodity name to the N1002 free form description field
[Move hazardous material name to description field]
The hazardous material information is found in the HZCMD table → Move the hazardous material name to the H104 hazardous material description field

Structural Validations

[Location ID Name provided?]
The location ID name field is checked → Processing continues only if location ID name is not empty, otherwise P4 processing is skipped
[Location ID Name Provided?]
The system checks if the location ID name field contains data → Processing continues only if the location ID name is not empty, otherwise P4 processing is skipped
[Clear MC Segment Data, Set Location ID to Error Indicator]
The system determines the location cannot be processed as a valid border crossing → The MC segment data is cleared to spaces and the P4 location ID is set to '????' to indicate processing failure
[Set Error Indicator '?' in Port Code Field]
The system sets error indicators for the failed lookup → The port code output field is filled with '?' characters to indicate lookup failure
[Origin Location Name or Province/State Code Present?]
If the presence of origin location ID name or origin province/state code → Processing continues only if either origin location ID name is not spaces or origin province/state code is not spaces
[Location ID1 Name Not Empty?]
The system checks the location ID1 name field → Processing continues to SD table lookup if the location ID1 name is not empty, otherwise skips to transaction type validation
[Location ID1 Name Not Empty?]
The system checks Location ID1 name field → Processing continues only if Location ID1 name is not empty, otherwise skip location processing
[Check Location ID2 Name Not Empty]
The system checks if Location ID2 name is not empty → Processing continues if name exists, otherwise processing is skipped
[Commodity Code Not Empty?]
Checking commodity code for processing → System only processes entries where commodity code is not spaces
[Handle Query Error]
The SQL query returns an error response (SQLCODE is not successful or not found) → The system should set error message to 'DB2 ERROR- SQL OPEN CMDTY-VERSIONS' and Execute database error handling
[Clear Related Segments]
Related data segments may contain outdated or invalid information → The related data segments are cleared to spaces to ensure data consistency
[Set error indicator '?']
The location is not a border port or crossing point is not implemented or table lookup fails → Set the P401 location ID to all question marks to indicate invalid data
[Set error indicator '?']
The SD table lookup fails or returns no results → Set the P503 location ID port code to all question marks to indicate lookup failure
[Set error indicator '?']
Both combined location name plus province code lookup and province code only lookup fail in SK table → Set the M1102 location ID to all question marks to indicate lookup failure
[Set error indicator '?']
The BK table lookup fails or returns no results → Set the RT02 district code, office code, and filer code to all question marks to indicate lookup failure
[Format Error Message with SQLCODE]
The system needs to create an error message → The system formats the database error code and combines it with descriptive error text to create a complete error message
[Set Error Message in Common Area]
The system needs to make the error information available to other components → The system stores the complete error message in the common communication area
[Call Error Handler CERR]
The system needs to handle the critical error condition → The system calls the CERR error handling routine with the common communication area

As an EDI Gateway Service,
I want to orchestrate and execute all GCCCARID 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

[Start from position after leading spaces]
The system begins extracting alphabetic characters → The extraction starts from the position immediately after all leading spaces
[Is current character a space?]
The current character at position I1 is evaluated → If the character is a space, numeric portion processing must stop immediately
[Start scanning from position after initials and spaces]
The system needs to count numeric characters → Scanning starts from the position immediately after the initials and spaces (position I2)
[Move numeric characters to output format right-justified]
The numeric portion needs to be formatted in the output car ID structure → Each numeric character should be moved to the numeric field starting from the rightmost position (position 7) and filling leftward, maintaining the original sequence of digits

Structural Validations

[Character Type Check - Is character non-alphabetic?]
A non-alphabetic character is encountered at the current position → The initial extraction process should terminate immediately
[Letter Count Check - Have 5 letters been extracted?]
The counter for extracted initials reaches 5 characters → The initial extraction process should terminate to prevent exceeding the maximum allowed initials
[Position Boundary Check - Is I1 > 12?]
The system needs to extract a character from the car ID at the current position → The system must verify that the position I1 is not greater than 12 (the maximum field length) before proceeding with character extraction

As an EDI Gateway Service,
I want to orchestrate and execute all GCCCCIO 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

[Is Creation Timestamp Empty?]
The creation timestamp field is empty (spaces) → The system should proceed to set new creation information including date, time, terminal and user
[Use Secondary Index Search]
The secondary index option is selected → The system builds secondary index SSA using the secondary key and executes database call to retrieve the record
[Use Primary Key Search]
The primary key option is selected and secondary key is valid → The system builds primary key SSA using GCSCCS00-KEY and executes database call to retrieve the record
[Attempt to Retrieve Existing Record]
The system attempts to retrieve the existing record using GHU function → The system determines if the record exists based on the database response status
[Attempt to Retrieve Existing GCSCCS00 Record]
The system needs to check if a GCSCCS00 record already exists → The system performs a Get Hold Unique operation to retrieve the existing record and sets the status code accordingly
[Delete Request for GCSCCS00 Record]
The system processes the delete operation → The system should save current record data and set up for record retrieval to validate existence before deletion
[Skip Insert Operation]
The cargo data field contains all spaces, all low-values, or all underscore characters → The insert operation should be skipped and no database call should be made
[Delete Existing Record]
The cargo data field contains all spaces, all low-values, or all underscore characters → The existing record should be deleted from the database
[Continue with Insert]
The cargo data field contains values other than all spaces, all low-values, or all underscore characters → The insert operation should proceed normally and the record should be added to the database
[Continue with Update]
The cargo data field contains values other than all spaces, all low-values, or all underscore characters → The replace operation should proceed normally and the record should be updated in the database
[Process Normal Update]
The cargo data field contains values other than all spaces, all low-values, or all underscore characters → The operation should be converted to an insert and the new record should be added to the database
[Database Segment Type?]
The segment type is GCSCCRT → The system routes to primary database function processing
[Database Segment Type?]
The segment type is GCSA2RT → The system routes to secondary database function processing
[Primary Function Code?]
The function code is ISRT (Insert) → The system routes to insert processing for primary segment
[Primary Function Code?]
The function code is REPL (Replace) → The system routes to replace processing for primary segment
[Primary Function Code?]
The function code is DLET (Delete) → The system routes to delete processing for primary segment
[Index Usage?]
The index usage indicator is NOT-USED → The system routes to primary key retrieval processing
[Index Usage?]
The index usage indicator is not NOT-USED → The system routes to secondary index retrieval processing
[Secondary Function Code?]
The function code is ISRT (Insert) → The system routes to insert processing for secondary segment
[Secondary Function Code?]
The function code is REPL (Replace) → The system routes to replace/update processing for secondary segment
[Secondary Function Code?]
The function code is DLET (Delete) → The system routes to delete processing for secondary segment
[Index Type?]
The index usage indicator is SECN-KEY → The system routes to secondary key retrieval processing
[Index Type?]
The index usage indicator is not SECN-KEY → The system routes to primary key retrieval processing

Structural Validations

[1:Parameter Validation]
The segment name is not GCSCCRT (primary segment) and not GCSA2RT (secondary segment) → The system marks parameters as invalid and sets error message to 'SEGMENT NAME INVALID'
[1:Parameter Validation]
The function code is not GU (Get Unique) and not GN (Get Next) and not ISRT (Insert) and not REPL (Replace) and not DLET (Delete) → The system marks parameters as invalid and sets error message to 'FUNCTION CODE INVALID'
[1:Parameter Validation]
The index usage indicator is not NOT-USED and not WAYBILL and not CAR-ID and not DESTINATION and not ERROR and not PRINT and not LEAD-CCN and not SECN-KEY → The system marks parameters as invalid and sets error message to 'INDEX USAGE INDICATOR INVALID'
[2:Primary Database Record Retrieval]
The CCN key is empty spaces → The system marks parameters as invalid and sets error message to 'GCCC-CCN-KEY EQUAL SPACES'
[6:Secondary Database Record Retrieval]
The secondary key is empty spaces → The system marks parameters as invalid and sets error message to 'SECN-KEY EQUAL SPACES'
[Segment Name Valid?]
The segment name is not GCSCCRT (primary segment) and not GCSA2RT (secondary segment) → The system sets parameter invalid flag and displays error message 'SEGMENT NAME INVALID'
[Function Code Valid?]
The function code is not GU (Get Unique) and not GN (Get Next) and not ISRT (Insert) and not REPL (Replace) and not DLET (Delete) → The system sets parameter invalid flag and displays error message 'FUNCTION CODE INVALID'
[Index Usage Indicator Valid?]
The index usage indicator is not NOT-USED and not WAYBILL and not CAR-ID and not DESTINATION and not ERROR and not PRINT and not LEAD-CCN and not SECN-KEY → The system sets parameter invalid flag and displays error message 'INDEX USAGE INDICATOR INVALID'
[Build Primary Key SSA]
The CCN key is empty spaces → The system sets parameter invalid status AND sets error message 'GCCC-CCN-KEY EQUAL SPACES'
[Secondary Key Empty?]
The secondary key (GCSCCS00-KEY) is empty → The system sets parameter invalid status and returns error message 'SECN-KEY EQUAL SPACES'
[Compare Primary Key with Retrieved Key]
The system compares the retrieved CCN key with the original key value used for the search → The system sets the data-in-range flag to true if keys match, otherwise sets data-not-in-range flag to true

As an EDI Gateway Service,
I want to orchestrate and execute all GCCCROS2 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

[Clear Crossing Table Segment Area]
The system continues environment initialization → All fields in the crossing table segment area are cleared to spaces
[Clear Crossing Table Segment]
The system begins building a crossing table key → The crossing table segment is cleared to spaces to remove any previous data
[Set Shipper CHOP Code in Key]
The system builds the crossing table key → The shipper CHOP code is moved to the corresponding key field in the crossing table segment
[Set Consignee CHOP Code in Key]
The system builds the crossing table key → The consignee CHOP code is moved to the corresponding key field in the crossing table segment
[Set Origin Station in Key]
The system builds the crossing table key → The origin station code is moved to the corresponding key field in the crossing table segment
[Set Destination Station in Key]
The system builds the crossing table key → The destination station code is moved to the corresponding key field in the crossing table segment
[Set Origin SPLC Code in Key]
The system builds the crossing table key → The origin SPLC code is moved to the corresponding key field in the crossing table segment
[Set Destination SPLC Code in Key]
The system builds the crossing table key → The destination SPLC code is moved to the corresponding key field in the crossing table segment
[Set Commodity Code in Key]
The system builds the crossing table key → The commodity code is moved to the STCC field in the crossing table segment
[Prepare Database Query Key]
The system needs to prepare the database query key for crossing table lookup → The system clears the crossing table segment, moves all input parameters to their corresponding key fields, and creates an indexed key for database search
[Clear Output Data Area]
The system processes the unsuccessful query result → The system moves spaces to the crossing table segment to clear any residual data

Structural Validations

None explicitly identified in logic extraction.

As an EDI Gateway Service,
I want to orchestrate and execute all GCCIH 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 Control]
The system begins message processing → The current program name is saved and the module name becomes the active program identifier

Core Acceptance Criteria

[3:Format CCN Status Message]
The CCN status message is being formatted → The 91-byte input data is moved to positions 2-91 of the message structure and the formatted input is copied to the message area
[3:Format CCN Status Message]
The message is prepared for transmission → The accept status is set to spaces to indicate a cleared/ready state
[4:Send Initial IMS Message]
The message is sent for initial processing → The CIMS service is invoked with change operation parameters to process the message
[5:Write Message Log]
The message logging is performed → The WRITMSGL service is invoked with message code, content, length, and module name for complete audit logging
[6:Purge IMS Message]
The cleanup operation is performed → The CIMS service is invoked with purge operation to remove the processed message from the system
[Move CCN Data to Input Structure Position 2-92]
Security initialization is performed → The security byte is set to HIGH-VALUES indicating maximum security level
[Transfer Formatted Input to IH Message Structure]
Message structure transfer is initiated → The complete formatted input is transferred to GCT1531E-MSG for IH processing
[Execute CIMS Call with CHNG Function]
System calls CIMS program with CHNG function using CCCOM, ALT-PCB, and GCT1531E parameters → IMS message processing is initiated for the prepared message
[Prepare Log Parameters]
The system prepares logging parameters → The message code, message content, message length, and module name are made available for the logging operation
[Call WRITMSGL Program]
The system calls the WRITMSGL program with message code, message content, message length, and module name → The WRITMSGL program is invoked to log the CCN status notification message
[Execute PURG Function]
System initiates message cleanup process → CIMS program is called with PURG function to purge the message
[Complete Message Processing]
All message operations are completed → System returns control to the calling program to complete the process

Structural Validations

None explicitly identified in logic extraction.

As an EDI Gateway Service,
I want to orchestrate and execute all GCCTIB 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

[3:Retrieve Car ID Configuration]
Configuration lookup is performed using table ID 'ID' and the carrier ID as sequence key → If lookup succeeds, carrier configuration segment is loaded, otherwise configuration is initialized as empty
[Execute Database Lookup]
The database lookup operation is executed → The system attempts to retrieve the corresponding table segment data
[Configuration Found?]
The lookup return status is evaluated → If successful, load the retrieved table segment data, otherwise initialize empty configuration
[Load Car Configuration Data]
Loading the configuration data → The table segment data is moved to the car ID configuration segment
[Set Empty Configuration]
No configuration data is found for the car ID → The car ID configuration segment is initialized to empty values

Structural Validations

None explicitly identified in logic extraction.

As an EDI Gateway Service,
I want to orchestrate and execute all GCX110 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 US Cargo Segment]
The system begins cargo processing → The US cargo segment (GCSUSRT-SEGMENT) is initialized to empty values
[Initialize Email Parameters]
The email construction process begins → The system clears all email text message content and initializes return status flags to prepare for new message construction
[Initialize Line Counter]
Line processing begins → The system sets line counter to zero and establishes no-more-email flag to control message flow
[Initialize New Email Message]
Continuation message is needed → The system clears email text message content and resets line counter to zero
[Initialize Enhanced Report Format]
The system begins report initialization → All enhanced report message fields are cleared and email parameters are reset to spaces
[Initialize Continuation Report]
The system initializes continuation report → Email message content is cleared and line counter is reset to zero
[Initialize Container Processing]
System initializes container processing → Container record found flag is set to true, container index is reset to zero, and system prepares for sequential container retrieval
[Initialize Email Parameters]
The email processing begins → The system should clear the email message buffer, reset return status flags, set sender as OM01247, clear recipient and copy fields, clear keywords and subject fields, clear item sequence numbers, set item width to 080 characters, and prepare the message structure for content
[Initialize Line Counter to Zero]
Starting to process report lines → The system should set the line counter to zero and prepare to count lines as they are added to the email message
[Initialize Train Header Information]
The system begins storing the train list in the database → The train header information is initialized with empty values for all equipment and segment data
[Initialize Enhanced Report Structure]
The enhanced report generation process begins → The system initializes the email message structure, clears return status flags, sets message parameters to spaces, sets item width to 132 characters, and resets equipment sequence counter to zero
[Initialize FEN and KCM Flags as Not Found]
The system begins checking for FEN and KCM reference qualifiers → Both FEN-NOT-FOUND and KCM-NOT-FOUND flags are set to true as initial state
[Initialize Communication Segment]
The system begins the communication data retrieval process → The communication segment structure is cleared and initialized to empty values
[Initialize Empty Communication Segment]
The database read operation fails to locate valid SHIPCOMM segment data → The system initializes an empty communication segment structure to maintain consistent processing flow

Core Acceptance Criteria

[1:Request Validation]
System validates request permissions → If action is not permitted, generate error message MSG-ONE and increment report index
[2:User Authorization Validation]
System validates SCAC access using user ID and determined train SCAC (CP for non-9089 origins, UPRR for 9089 origin) → If SCAC access is invalid, generate error message MSG-THIRTY and increment report index
[16:Special Manifest Processing]
System evaluates special manifest requirements → Create special manifest for: TE bonds needing export detour, TR bonds needing port change, export bills needing detour, original CA-CA movements, or US-US movements with residue weight. Generate appropriate warning messages and spawn manifest creation processes
[20:Pedimento Processing]
System processes pedimento information → If cargo has DSP hold application, use DSP hold indicator as pedimento value. For other stations, mark pedimento as not applicable
[32:EDI Transmission to Customs]
System transmits manifest to customs using GCCE358 module → Successfully transmit train manifest data to customs authority. If transmission fails, abort processing with error message
[Read Input Message]
An input message is available in the queue → The system reads the message and extracts the request parameters for processing
[Message Available?]
The input message indicator shows no more messages (WS-NO-MORE-INPUT-MSG) → The system stops processing and exits the main loop
[Extract Request Type from Message]
The request type equals the AEI request type constant (CST-AEI-REQ-TYPE) → The system sets AEI-TRAIN-SEND-YES flag to true, otherwise sets AEI-TRAIN-SEND-NO flag to true
[Validate User Access for SCAC]
The system calls the security validation module with the user ID and SCAC code → If SCAC access is invalid then set authorization error message and add error to report, otherwise continue with normal processing
[Extract Station Segment Data]
The system successfully retrieves the record → The system moves the general table segment data to the station segment for further processing
[ETA within -30 to +5 Days Range?]
ETA date is not between 30 days before current date and 5 days after current date → The system should set error message 'ETA Outside Send Range'
[ETA within -2 to +2 Days Range?]
ETA date is not between 2 days before current date and 2 days after current date → The system should set error message 'ETA Outside Notify Range'
[Read General Table GCSTBRT-AD]
The system attempts to read the general table → The GCSTBRT table is accessed using the AD key to retrieve application data segment
[Extract AD Segment Data]
The system processes the retrieved data → The GCSTBRT-AD segment is moved to the application data segment for further processing
[Access General Table LT with Terminal ID]
The system accesses the general table LT segment with the terminal ID → The system performs a database read operation to retrieve the originator reference data
[Move General Table Segment to LT Segment]
Valid segment data is returned from the general table → The system moves the retrieved general table segment to the LT segment for further processing
[Set LT Segment to Spaces]
No valid segment data is returned from the general table → The system sets the LT segment to spaces to indicate missing originator reference information
[Process Current Cargo Record]
The system processes the current cargo record → The system performs segment data extraction (Z350-FETCH-SEG07), builds report information (B500-BUILD-REPORT), and if the request action is SEND with no errors, attaches the cargo (B400-ATTACH-CARGO)
[IT Bond Type?]
The bond type code equals 'IT' (Immediate Transit) → Set TR bond found flag to true and check TR created for IT status
[Special Manifest Original?]
The special manifest original flag is set → Set SPLC-IT found flag to true for immediate transit special processing
[Mark as Proceeding Cargo]
The status equals 'PROCEED' or 'PROCEED-HOLD-DEST' → The cargo should be counted as proceeding cargo
[Mark as Proceeding Cargo]
The bond type code equals 'IT', 'TE', or 'TR' → The cargo should be counted as proceeding cargo
[Use Line Release Number as Entry Number]
The line release number in segment 07 is not empty → The line release number should be used as the entry number
[Check for FEN and KCM Qualifiers in Segment 02]
System begins checking for FEN and KCM qualifiers → FEN and KCM flags are set to 'Not Found' status
[Loop Through N9 Data Elements]
System processes N9 data elements sequentially → Each N9 element is examined until maximum occurrences reached or empty element found
[Station = Laredo TX?]
Station code equals Laredo TX station identifier → Special Laredo pedimento processing rules are applied
[DSP Hold Applies?]
DSP hold applies to the cargo → Pedimento is set to DSP hold indicator value
[Set Pedimento to 'X' 'Not Applicable']
Station is not Laredo TX → Pedimento is set to 'X' indicating not applicable
[MSG-34: Send Location Mismatch with Special Manifest]
Station code does not match cargo location for non-transit, non-export cargo → Generate message type 34 and create special manifest for location change processing
[MSG-31: IT Export Special Manifest]
Request is for send action and user is authorized for special manifests → Generate message type 31 and create special detour manifest for processing
[MSG-32: Detour Report Required]
Request is for report action or send action with authorization issues → Generate message type 32 indicating detour report is required
[MSG-43: User Not Authorized for Special Manifest]
Request is for send action but user is not authorized for special manifests → Generate message type 43 indicating user lacks authorization for special manifest creation
[Get Load/Empty Indicator from Waybill]
Load/empty indicator needs to be determined → Load/empty indicator is retrieved from the waybill root segment
[Bond Type = TR? and Status = RELEASE or EXPORT?]
The cargo status is not RELEASE and not EXPORT → Set message twelve indicating transit bond issue and continue validation
[Bond Type = MT? and Vessel Name ≠ TRAIN and Location Match?]
The vessel name is not TRAIN or SPACES and the train origin station code matches the cargo location → Set message twenty-five indicating multi-transit bond issue and continue validation
[Multi-Transit Bond? and Vessel Name ≠ TRAIN?]
The vessel name does not indicate TRAIN in the appropriate position → Set message seventeen indicating vessel name issue and continue location validation
[Action = SEND? and Set Message Thirty-Four - Port Change Required]
The cargo requires port change processing → Set message thirty-four indicating port change required and trigger special manifest creation
[Export Bill with Wrong Status?]
The cargo status indicates export processing is required → Set message thirty-two indicating export issue and mark cargo as processing eligible
[Multi-Transit Bond?]
The vessel name is not TRAIN and the origin station code equals the current location ID → Generate MSG-SEVENTEEN error message for multi-transit bond violation
[Validate SCAC Code Access]
The system validates SCAC access through GCCSCAC module → If SCAC access is invalid for the user, set SCAC access error message
[Generate Message 32 - TIB Report Warning]
The system processes TIB validation failure for REPORT action → Generate message 32 as TIB report warning and increment report index
[Process IT Export Requirements]
The cargo requires IT export processing AND TR bond is not found → Generate appropriate error message and set TR bond not found status
[Process TE Export Requirements]
The cargo requires TE export processing AND TE bond is not found → Generate appropriate error message and set TE bond not found status
[Process TR Bond Requirements]
The cargo requires TR bond processing AND SPLC TR is not found → Generate appropriate error message and set SPLC TR not found status
[Process USMX-88 Requirements]
The cargo requires USMX-88 processing AND SPLC TR is not found → Generate appropriate error message and set USMX-88 found status
[Request Action Type?]
If the request action type → The system routes to report message generation for REPORT action or user authorization check for SEND action
[Generate Report Message]
The system generates the report message → The system creates message thirty-two, adds to report index, and continues processing
[User Authorized for Special Manifest?]
The system checks user authorization for special manifest → The system allows special manifest creation if user is authorized, otherwise generates authorization error message
[Generate Send Message with Special Manifest Creation]
The system processes the send action → The system creates appropriate message (thirty-one or thirty-four), adds to report index, and performs special manifest creation
[Add Equipment Type Code]
Processing equipment type information → Call external equipment type validation service (GCCCARTP) and if successful, populate equipment type code in report, otherwise generate equipment error message and set equipment error flag
[Add Bond Type Information]
Processing bond type information for cargo → For bill types 00, 10, or 99 with segment 7 data, if line release number exists set bond to 'LR', otherwise use in-bond type code; for other bill types, use the bill type code directly as bond type
[Add Entry Number]
Determining entry number for cargo report → If segment 7 exists and line release number is present, use line release number; if bill type is 10, use entry number if available otherwise use in-bond control number; for other cases, use broker entry number
[Check for Business Rule Violations]
Evaluating cargo against established business rules → Check for waybill/cargo mismatches, validate multi-transit requirements, verify returned goods processing, ensure proper vessel naming conventions, and flag violations with appropriate warning or error messages
[Add Warning Messages]
Evaluating conditions for warning message generation → Generate warnings for cargo sent to CPRS with blank/error USCS status, location mismatches in transit processing, and other business rule deviations that require user awareness
[Add Information Messages]
Generating informational messages for user notification → Create information messages for successful processing, status updates, and operational confirmations that help users understand processing results
[Count Total Equipment]
Calculating total equipment count for summary reporting → Count all non-message, non-spacer report lines that contain valid equipment information and increment total equipment counter
[Count Proceeding Cargo]
Calculating proceeding cargo counts for status summary → For cargo with US Customs status of 'PROCEED' or 'PROCEED HOLD DEST', increment proceed counter; for cargo with 'ARRIVED' status and bond types IT, TE, or TR, also increment proceed counter
[Set REPORT Report Headers]
Setting up REPORT-specific report headers → Set REPORT header indicator, configure result indicators based on error and warning status, and include warning and error counts if messages exist
[Call Equipment Type Module]
The equipment type validation module GCCCARTP is called with the equipment information → If validation fails, an equipment error message is added to the report and processing stops for this equipment item
[Set Cargo Status Fields]
Bond type information is being determined → If bill of lading type is '00', '10', or '99' and segment 7 exists with blank line release number, bond type is set to in-bond type code, if line release number exists, bond type is set to 'LR', otherwise bond type is set to bill of lading type code
[Check Pedimento Requirements]
Processing entry and pedimento information for cargo → Check pedimento requirements, get entry number, and set entry status based on load/empty code and customs ship value
[Set Bond Type to Line Release]
Processing bond type display information → Set the report bond type to 'LR' for Line Release
[Set Bond Type from In-Bond Code]
Processing bond type display information → Set the report bond type to the in-bond type code value
[Build Report Info from Station Data]
Processing report information string building → Process station table entries and set report info string to SFI type description for US entries
[Check for Line Release Number]
The line release number in position 1 is not blank/spaces → Use the line release number as the entry number for the cargo
[Check DSP Hold Indicator]
DSP hold applies to the cargo → Set pedimento field to the DSP hold indicator value
[Set Pedimento Status to X]
The station is not Laredo TX:
DSP hold does not apply
→ Set pedimento status to 'X' indicating standard processing
[Check if DSP Hold applies to cargo]
The crossing station is Laredo Texas station (CST-LAREDO-TX-STATION) and DSP hold applies to the cargo (GCUSRT-DSP-HOLD-APPLY is true) → The DSP hold indicator (GCUSRT-DSP-HOLD-IND) should be set in the pedimento field (RPT-PEDIMENTO)
[Is crossing at Laredo TX Station?]
The station code (GCSTBRT-SC-US-STAT-CODE-X) equals the Laredo Texas station code (CST-LAREDO-TX-STATION) → DSP hold validation should be performed, otherwise set pedimento field to 'X' for other stations
[Continue without DSP hold]
The crossing station is not Laredo Texas station → The pedimento field (RPT-PEDIMENTO) should be set to 'X' indicating standard processing
[Set Warning Message Flags]
If the message content and MSG-WRN flag is true → The message is classified as a warning message and warning counter is incremented
[Set Info Message Flags]
If the message content and MSG-INF flag is true → The message is classified as an informational message and info counter is incremented
[Set Overflow Message]
The current report index (RPT-IDX) is greater than or equal to 1981 → An overflow message (MSG-NINE) is set and request error counter is incremented
[Build Message Detail Line]
The system processes the message content → Message text is formatted with appropriate prefixes, status indicators, and line formatting
[Copy to Email Text Line]
The line is designated for email transmission → The report line content is copied to the corresponding email text line structure
[Set Line Type Indicators]
The system finalizes the line processing → Appropriate line type indicators are set based on content type (header, detail, message, spacer, etc.)
[Extract Routing Information from Waybill]
The system processes the equipment routing → Routing information is extracted from RUT-INFO fields in SHIPROOT waybill segment
[Move RUT-INFO from SHIPROOT to Working Storage]
The system begins routing validation → RUT-INFO data from positions 1, 2, and 3 is moved to working storage routing arrays
[Parse SCAC and Junction Data]
The system processes routing segments → SCAC codes and junction information are extracted from current and next routing array positions
[Set Train Status to SENT]
The system sets the train status → The train status is set to SENT to indicate successful transmission
[Process Each Report Line]
The system processes each report line sequentially → Each line from index 8 to the last report line is examined until the maximum equipment limit is reached
[Check Line Type]
The system checks the line type → The line is identified as an equipment line if it is not a message line, not an end report line, and not a spacer line
[Copy Train Details to Manifest]
Train manifest is ready for transmission → Train status is set to sent
[Check Line Type]
Checking the line type → Line is identified as equipment line if it is not a message line, end report line, or spacer line
[Set Background Processing Mode]
The EDI transmission process is initiated → The system sets the processing mode to background for the GCCE358 EDI module
[Call GCCE358 Module for EDI Transmission]
The system calls the GCCE358 EDI transmission module → The module is invoked with the common communication area, EDI parameters, and train list data
[Send Train List to US Customs in EDI Format]
The system processes the train list transmission → The train list data is sent to US Customs in the required EDI format
[Log AEI Send Activity]
The system checks if AEI train send flag is set to yes → The system performs AEI send logging activity to record the transmission
[Add Line to Email Message]
The system adds the line to the email → The report line content is moved to the email message line and the line counter is incremented by 1
[Line Count > 699?]
The system checks if the line count exceeds the limit → If line count is greater than 699 then the current email batch is sent and a new batch is started, otherwise processing continues
[Send Current Email Batch]
The system sends the current email batch → The email is transmitted using EMCSEND3 module with current message content
[Reset Email Message]
The system resets the email message → The email text message is cleared and the line counter is reset to zero
[Add Continuation Header]
The system adds continuation headers → Continuation message, header 1A or standard header, and detail header 2 are added to the new email batch
[Send Final Email Batch if Needed]
The system checks for final email batch transmission → If there is remaining email content then the final batch is sent using EMCSEND3 module
[Purge IMS Message Queue]
The system performs cleanup operations → The IMS message queue is purged using CIMS with PURG function and alternate PCB
[Line Count > 699?]
The system checks the current line count → If line count exceeds 699 then send current email batch, reset message content, add continuation header with report headers, and reset line counter to 3, otherwise continue adding lines to current message
[Set Email Headers - From/To/Subject]
Email headers are being set → The system sets FROM usercode to OM01247, TO usercode to OM01247, clears copy and keyword fields, sets subject to train report header line, and clears item sequence numbers
[Set Message Width and Format]
Message format parameters are being set → The system sets item width to 080 characters for standard reports or 132 characters for new format reports to Merlin destination
[Start Processing Report Lines]
Email content processing starts → The system begins processing report lines sequentially, handling both message lines and equipment detail lines with appropriate formatting
[More Report Lines?]
The system checks for remaining report lines → The system continues processing if report lines contain non-blank content and line index is within maximum limit of 1981 lines
[Add Line to Email Message]
Line processing occurs → The system adds the report line to email text message at current line position and increments line counter
[Send Current Email Message]
Message segmentation is triggered → The system calls EMCSEND3 to transmit current email message with all established parameters and handles any transmission failures
[Add Continuation Header]
Continuation header is added → The system adds 'CONTINUATION OF REPORT....' message as first line and increments line counter
[Add Column Headers]
Headers are being added → The system adds saved header information and detail header lines to provide column context for continued report data
[Send Final Email Message]
Final transmission occurs → The system calls EMCSEND3 to send final email message and handles any transmission failures with error reporting
[Purge Message Queue]
Queue cleanup occurs → The system initializes accept status and calls CIMS with PURG function to clear message queue
[Process Equipment Line]
The system processes an equipment line → If line is a message line then message content is copied to new report line, otherwise line counter is incremented, equipment sequence counter is incremented, and more email flag is set to true
[Increment Equipment Sequence]
The system increments equipment sequence → Equipment sequence counter is incremented by 1 and assigned to the current equipment line sequence number field
[Format Equipment Details]
The system formats equipment details → Equipment type is copied from report line to new report format, load/empty indicator is copied from report line, customs control number is copied from report line, and formatted line is added to email message
[Send Current Report Batch]
The system sends current report batch → Email send function is called with current message content, no more email flag is set to true, and send operation is performed
[Add Continuation Headers]
The system adds continuation headers → Continuation message is added as first line, column headers are added as second line, underline separator is added as third line, and line counter is incremented by 3
[Add Equipment Line to Report]
The system adds equipment line to report → Formatted equipment line is added to email message at current line position and processing continues to next equipment line
[Send Final Report Batch]
The system sends final report batch → Email send function is called with remaining message content and final transmission is completed
[Purge Message Queue]
The system purges message queue → Accept status is initialized and purge operation is called on alternate PCB
[Skip Notification]
If whether to send originator notification → The system should skip all notification processing and exit the originator notification section
[Set Report Type Based on Action]
The system determines the report classification → If RPT-ERROR-APPEND is true, set GCSTONLY-TRAIN-ERROR; if REQ-ACTION-SEND, set GCSTONLY-TRAIN-SENT; if REQ-ACTION-REPORT, set GCSTONLY-TRAIN-REPORT; if REQ-ACTION-NOTIFY, set GCSTONLY-TRAIN-NOTIFY and set destination terminal to 'ISTS'
[Send All Report Lines]
If the report filtering strategy → If RPT-ALL-REPORT is true, send all report lines from 1 to RPT-LAST-LINE; if RPT-NO-WRN is true, send only header lines 1 to 4; otherwise send header lines 1 to 7 plus all warning message lines, then send the last line
[Send Report Wrap Command]
The report transmission is being finalized → The system should set CC-USER-FUNC-CODE to 'WRAP', set RPT-IDX to 1, and Execute the GCSTONLY call to complete the transmission
[Log AEI Send Transaction]
The system completes train list creation and sending → The system logs transaction with train ID, user ID, timestamp, and AEI send message to audit trail
[Set Train List AEI Send Flag]
The system determines the AEI send status from request classification → The system sets GCWTL-AEI-SEND flag to true if AEI train send is YES, otherwise sets GCWTL-NOT-AEI-SEND flag to true
[Create GCX112 Message]
System creates the arrival notice message → US CCN key from the cargo report line is moved to GCX112-TRAIN-OR-US-CCN field and GCX112-INPUT is moved to MESSAGE-OUTPUT-TXT for transmission
[Send Message to Queue]
System sends the message → Z720-ISRT-PURGE-MESSAGE procedure is performed to insert and purge the message to the queue
[Set GCX141 Message Function Name]
The system initiates the Canadian export report generation process → The GCX141 message function name should be set to identify this as an export report generation request
[Insert GCX141 Message for Processing]
The export report is ready for submission to regulatory authorities → The GCX141 message should be inserted into the processing queue for Canadian export reporting compliance
[Lookup SCAC in General Table SS]
The system needs to determine port processing type → The system looks up the carrier SCAC code in the general table SS segment
[Retrieve Container Information from FWSWREQ]
The system processes the FWSWREQ segment for container details → Container ID, platform position, slot position, and well position are extracted and stored
[Set Message to 'CAR ADDED LOG MESSAGE']
The system sets the log message content → The message is set to the standard 'CAR ADDED LOG MESSAGE' text
[Write Message to Log Database]
The system persists the audit information → The audit log message is written to the log database using the WRITMSGL function
[Write Customer Report Message]
The system persists the customer report → The customer report message is written to the database using the WRITMSGL function
[Email Send Failure]
The email system returns a failure status → The system immediately performs an abnormal termination as the notification mechanism has failed
[Set GCWTL-AEI-SEND Flag in Train List]
The system creates or updates the train list record → The system sets GCWTL-AEI-SEND flag to TRUE in the train list to enable AEI transmission
[Set GCWTL-NOT-AEI-SEND Flag in Train List]
The system creates or updates the train list record → The system sets GCWTL-NOT-AEI-SEND flag to TRUE in the train list to disable AEI transmission
[Special Manifest Processing Required?]
If user authorization for special manifests → If user is authorized, allow special manifest creation; if not authorized, block creation and generate authorization error message
[Parse Route SCAC Codes and Junction Points]
The system processes route validation → First and second route SCAC codes and junction R260 information are extracted from routing arrays
[Valid CPRS-CSXT-DET Route?]
The system validates the routing pattern → Route is valid if first SCAC is 'CPRS', second SCAC is 'CSXT', and junction R260 is 'DET'
[Retrieve Container from FWSWREQ Segment]
The system processes the equipment segment → Container ID, platform position, slot position, and well position are extracted and stored
[Is Request Action = REPORT?]
The system processes the cargo secondary segments → The system should only process FDA reference extraction if the request action is REPORT, otherwise skip FDA processing
[More N9 Data Segments?]
The system checks for more N9 data segments to process → The system should continue processing if more segments exist and FDA reference has not been found, or stop if no more segments exist or FDA reference is already found
[Reference Qualifier = '2K'?]
The system checks the reference number qualifier → The system should identify the reference as FDA-related only if the qualifier equals '2K', otherwise continue searching other references
[Process Cargo Information]
The system processes cargo information → US CCN key should be stored, load/empty code should be set from cargo data, entry status should be determined, broker information should be processed, bond type should be set, status information should be updated, entry numbers should be processed, and pedimento information should be handled
[Build Report Info String]
The system builds report information → Station table should be retrieved using commodity code, and SFI type descriptions for US country should be used to populate report info string
[Set Cargo Description and Bond Type]
The system processes bond type → If segment 7 exists and line release number is blank, bond type should be set from in-bond type code; if line release exists, bond type should be 'LR'; otherwise bond type should be the bill type code
[Process Entry Numbers]
The system processes entry numbers → If segment 7 exists with line release number, use line release; if bill type is '10' and entry number exists, use entry number; if bill type is '10' and no entry number, use in-bond control number; otherwise use broker entry number
[Process Pedimento Information]
The system processes pedimento information → The DSP hold indicator should be stored in the pedimento field
[Process Pedimento Information]
The system processes pedimento information → The pedimento field should be set to 'X' indicating not applicable
[Set Bond Type = 'LR']
Line release number in segment 7 is not blank → Set bond type display to 'LR'
[Set Bond Type = In-Bond Type Code]
Line release number in segment 7 is blank → Set bond type display to the in-bond type code
[Set Bond Type = BOL Type Code]
Segment 7 data is not available → Set bond type display to the BOL type code
[Check FDA Reference for Reports]
The system processes cargo segments → The system should search through segment 02 occurrences for reference number qualifier '2K' and populate report info string with the FDA reference number if found
[Build Report Information]
The system processes segment 07 information → The system should retrieve station table entries and populate report info string with SFI type description for US country entries
[Include Line in Report]
The system decides on line inclusion → The system should include the line in report output and copy to EMI text line for transmission
[Process FDA Reference Data]
System searches through reference data segments for FDA qualifier '2K' → FDA reference number is extracted and stored in report info string when found
[Set Bond Type Display]
Bill of lading type is '00', '10', or '99' and segment 7 exists with line release number → Bond type displays 'LR' for line release, otherwise displays the bill of lading type code or in-bond type code
[Special TR Bond Created?]
Cargo has TR-CREATED-FOR-IT flag set to 'Y' → Current report line is saved as IT line for special processing and line is cleared for message processing
[Set Equipment Not Found Message]
Waybill is not found and container is found, or waybill is not found and equipment is loaded but not SBU van → Message type 10 (equipment not found) is set for the report line
[Set Cargo Status Messages]
Cargo status is pending, deleted, or error → Message type 16 (cargo status issue) is set for the report line
[Set Bond Type Messages]
In-bond type is 'TR' and cargo status is not 'RELEASE' or 'EXPORT' → Message type 12 (transit bond issue) is set for the report line
[Set Location Mismatch Messages]
Train origin is specified and cargo location does not match station code and cargo is not export type and not bill type '15' → Message type 33 (location mismatch) for reports or type 34 for send actions is set
[Combine Equipment and Message Lines]
Cargo has special conditions (TR created, TE created, special manifest, or USMX 88) and line is not a spacer line → Saved equipment line is restored, equipment count is incremented, and both equipment and message lines are added to report
[Equipment Data Available?]
The line contains equipment data (not message line, not end report, not spacer line) → The line is classified as an equipment line and equipment processing is performed
[Fill Equipment Details]
The bill type is '00', '10', or '99' and segment 7 data exists → Bond type is set to 'LR' if line release number exists, otherwise set to in-bond type code; for other bill types, use the bill type code directly
[Message Conditions Met?]
The line meets specific message conditions such as waybill not found, cargo status issues, or validation errors → The line is classified as a message line and appropriate message processing is performed
[Add to Report Index]
The line needs to be added to the report → The report index is incremented if below maximum limit (1981), otherwise Message 9 error is set
[Get Container from Waybill Root Key]
Container index is incremented and within maximum container limit → System retrieves container using container key from waybill segments
[Get Container Equipment Segments]
Equipment segment is successfully retrieved → System extracts container ID, platform, slot, well information and calculates container ordering sequence
[Search Inquiry Database as Fallback]
Fallback processing is initiated → System searches FWCIROOT segment using equipment ID for inquiry database records
[Set MSG-TEN for Missing Waybill with Loaded Equipment]
Waybill is not found AND container is found:
waybill is not found AND container is not found AND equipment is loaded AND equipment is not a special unit van
→ Set MSG-TEN message indicator to true and set MSG-TEN-ON flag to true
[Set MSG-TWENTY-SIX for Database Access Issues]
Waybill is not found AND waybill status is not definitively not found → Set MSG-TWENTY-SIX message indicator to true and set MSG-TWENTY-SIX-ON flag to true
[Set MSG-FIFTEEN for Missing Cargo with Valid Waybill]
Waybill is found AND no cargo is found AND idler indicator is not spaces:
waybill is found AND no cargo is found AND container is found AND equipment load indicator is 'E'
waybill is found AND no cargo is found AND container is not found AND equipment is loaded AND not a conveying car AND idler indicator is not 'I'
→ Set MSG-FIFTEEN message indicator to true, move waybill root key to message root key field, move waybill date to message date field, and set MSG-FIFTEEN-ON flag to true
[Set MSG-FIFTEEN for Missing Cargo with Valid Waybill]
Waybill is found AND no cargo is found AND residue weight is greater than 0:
weight threshold indicators are set AND equipment is empty AND idler indicator is not 'I'
→ Set MSG-FORTY-FOUR message indicator to true, move waybill root key to message root key field, move waybill date to message date field, and set MSG-FORTY-FOUR-ON flag to true
[Set MSG-TWELVE for TR Bond Type Issues]
Cargo is found AND bond type is 'TR' AND USCS cargo status is not 'RELEASE' AND USCS cargo status is not 'EXPORT' → Execute send message twelve procedure to set MSG-TWELVE indicator and MSG-TWELVE-ON flag
[Set MSG-TWENTY-FIVE for Multi-Transit Issues]
Cargo is found AND bond type is 'MT' AND vessel name is not 'TRAIN' AND vessel name is not spaces AND station US code equals cargo location ID → Set MSG-TWENTY-FIVE message indicator to true and set MSG-TWENTY-FIVE-ON flag to true
[Set MSG-THIRTY-FOUR for Border Code Mismatch in Sends]
Cargo is found AND train origin is not spaces AND bond type is not 'TR' AND bill type is not '15' AND not export type AND station US code != cargo location ID AND request action is send → Set MSG-THIRTY-FOUR message indicator to true, set MSG-THIRTY-FOUR-ON flag to true, and execute pre-spawn procedure for special manifest creation
[Set MSG-TWELVE for TR Bond Type Issues]
Send message twelve procedure is called → If request action is not send then set MSG-TWELVE indicator to true and MSG-TWELVE-ON flag to true, else set MSG-TWELVE indicator to true and MSG-TWELVE-ON flag to true
[Set WS-TR-CREATED-FOR-IT Flag]
Report line is spacer line AND cargo is found AND (immediate transport bond type:
US-Canada-US bond type
default export type) AND TR created for IT equals 'Y'
→ Set WS-TR-CREATED-FOR-IT flag to true
[Container Found from Previous Processing?]
The system checks if container was already found in previous processing steps → If container was already found, skip to next container processing, otherwise proceed with container retrieval from waybill segments
[Retrieve Container from Waybill Segments]
System performs container retrieval from waybill segments using FWSWRWR segment → Container information is retrieved if found in waybill segments, otherwise status indicates container not found
[Get Next Container from Waybill Sequence]
System performs next parent retrieval for FWSWREQ segment → Next container record is retrieved if available, otherwise end of container sequence is reached
[Use Inquiry Database as Fallback Source]
System switches to inquiry database fallback processing → Inquiry root segment is accessed using waybill information from car inquiry root for container cross-reference lookup
[Search for Container Cross-Reference Records]
System searches inquiry bottom line segments for container cross-reference records → Container cross-reference records are retrieved and processed to build container table with waybill and container ID information
[Retrieve Container from Inquiry Segments]
System retrieves container from inquiry root using cross-reference waybill information → Container information is retrieved from inquiry segments if waybill exists in inquiry database
[Set Container Information from Inquiry]
System maps inquiry container information to shipment structure → Container information including road number, waybill number, car ID, load/empty indicator, TOFC/COFC indicator, waybill date, and station number are mapped from inquiry root to shipment root
[Set Container Not Found Status]
System sets final container status → Container status is set to not found and inquiry-not-found flag is activated
[Send Train List via EDI to Customs]
The system initiates EDI transmission to customs → The system calls the EDI transmission module (GCCE358) in background mode with the complete train list data and logs AEI send activity if the request is AEI-enabled
[Send Cargo Arrival Notices]
The system processes arrival notifications → The system creates arrival notice messages (GCX112) with cargo arrival action code, destination port code, and cargo identification for each qualifying cargo record, then transmits these notices through the message queue system
[Send Report to Originator]
The system sends the report to the originator → The system determines the destination terminal, sets appropriate call letters (TRAIN-NOTIFY for notifications, TRAIN-REPORT for reports), sends either the complete report or a filtered version based on warning status, and wraps up the transmission with proper termination codes
[Send Train List to US Customs via EDI]
The system initiates customs transmission → The system calls GCCE358 module to send train manifest via EDI and logs AEI transmission if applicable
[Spawn Export Report]
The system processes export reporting → The system spawns GCX141 message to generate export report in background
[Send Cargo Arrival Notices]
The system identifies cargo marked for arrival notice → The system creates GCX112 messages for each qualifying cargo and sends arrival notifications to the destination port
[C300: Send Train List via EDI to Customs]
The system initiates EDI transmission → Train manifest is queued for transmission to customs via GCCE358 module in background mode
[C530: Log AEI Send Activity]
The system performs AEI audit logging → Audit log entry is created with train ID, timestamp, user ID, and AEI send message
[D100: Spawn Export Report]
The system initiates export report generation → Background process is spawned to generate export report via GCX141 message queue
[C500: Send Report to Originator]
The system sends report to originator → Processing results, error messages, and acknowledgment information are transmitted to originating terminal
[Z860: Send Audit Logs for Added Cargo]
The system performs cargo audit logging → Audit log entry is created for each added cargo with CCN, timestamp, user ID, and addition message
[Set AEI Send Flag]
The request type indicates AEI transmission is required → Set AEI send flag to true, otherwise set to false
[Set Train Status to SENT]
The system completes train list preparation → Set train status to SENT to indicate the manifest is ready for transmission
[Is Line Equipment Entry?]
Examining each report line → Process as equipment if line is not a message, spacer, or end report marker
[Skip Message/Spacer Lines]
Processing report lines → Skip to next line without processing current line as equipment
[Set Report Header Line 4 with Train Details]
The system processes header line 4 configuration → The header line 4 flag is set to true and train details including US customs train ID and ETA information are populated in the header
[Process Report Lines for Email]
The report lines are being processed for email transmission → Each non-empty report line is added to the email message, line counters are maintained, and when line count exceeds 699, the current email batch is sent and a new continuation email is started with appropriate headers
[Send Current Email Batch]
The current email batch needs to be sent → The email is transmitted using EMCSEND3, the email message is cleared, line counter is reset, continuation header 'CONTINUATION OF REPORT ....' is added, column headers are included, and line counter is set to 3
[Purge Message Queue]
Message queue cleanup is required → The system initializes the accept status and calls CIMS with PURG function to clear the alternate PCB message queue
[Add Report Line to Email Message]
Processing each report line that is not spaces or low-values and line index is within bounds (1 to 1981) → The system should increment the line counter, move the report line to the email message line at the current counter position, and set the more-email flag to true
[Send Current Email Message]
Sending the current message → The system should call EMCSEND3 with current message parameters including sender, destination, recipient, subject, keywords, message content, item details, and return status
[Clear Email Message Buffer]
Preparing for continuation message → The system should clear the email text message buffer and reset the line counter to zero
[Add Continuation Header]
Starting a new continuation message → The system should add 'CONTINUATION OF REPORT ....' as the first line of the new message
[Add Column Headers to New Message]
Setting up continuation message structure → The system should add the header line (WS-HEADER-1A) as the second line and the detail header (EMI-DET-HEADER-2) as the third line of the continuation message
[Set Line Counter to 3]
Resuming report line processing → The system should set the line counter to 3 to account for the continuation header and column headers already added
[Send Final Email Message]
Completing email processing → The system should call EMCSEND3 to send the final email message with all accumulated content
[Purge Email Queue]
Completing the email transmission process → The system should initialize accept status, call CIMS with PURG function to purge the alternate PCB queue, and complete the email processing
[Is Equipment Line?]
The system checks if the line is an equipment line → If the line is not a message line and not an end report line and not a spacer line, then it is identified as an equipment line
[Set Background Processing Mode]
The EDI transmission process is initiated → The system sets the processing mode to background to enable non-blocking EDI operations
[Call GCCE358 Module for EDI Processing]
The system calls the GCCE358 EDI processing module with train manifest data → The module processes the train list for EDI transmission to customs authorities
[AEI Train Send Request?]
The system checks if the train send request is of AEI type → If it is an AEI train send request, proceed to log AEI activity, otherwise complete the EDI transmission
[Log AEI Send Activity]
The system processes the AEI train send activity → The system logs the AEI send activity with appropriate details for audit and tracking purposes
[Complete EDI Transmission]
The system finalizes the EDI transmission process → The EDI transmission to US Customs is completed successfully
[Process Equipment Line - Increment Sequence Number - Add Equipment Type - Add Load/Empty Indicator - Add US CCN Number]
Processing an equipment line that is not a message line → The system increments the equipment sequence counter, populates sequence number, equipment type, load/empty indicator, and US CCN number for the equipment line
[Skip Message Line Processing]
A line is identified as a message line rather than equipment data → The system skips processing the message line and continues to the next line without incrementing sequence counters or adding equipment data
[Report Size Limit Reached?]
The report line count reaches 699 lines → The system sends the current report batch, initializes a new continuation report with continuation header message, adds column headers again, and resets the line counter to 3
[Send Final Report Batch]
No more equipment lines remain to process → The system sends the final report batch via email service and purges the message queue to complete the enhanced report generation
[Add Report Line to Email Message]
The system processes each non-empty report line → Each report line should be added to the email message buffer, line counter should be incremented, and more-email flag should be set to indicate content exists
[Line Count > 699?]
The line counter exceeds 699 lines → The system should set no-more-email flag, send the current email batch, reset the message buffer, add continuation header, add column headers, and reset line counter to 3
[Send Current Email Batch]
The system sends the email batch using EMCSEND3 service → The email should be sent with sender OM01247, destination filename, recipient OM01247, copy user, subject, keywords, message text, sequence numbers, item type, width, and return status should be checked for success
[Purge Message Queue]
The system performs cleanup operations → The accept status should be initialized and CIMS should be called with PURG function to purge the alternate PCB message queue
[Skip MST Message for NOTIFY with No Message Flag]
The originator notification process evaluates message requirements → The system should skip the MST message processing and exit the notification process
[Set Message Type Based on Request Action]
The system determines the message type for originator notification → If error condition exists, set TRAIN-ERROR; if SEND action, set TRAIN-SENT; if REPORT action, set TRAIN-REPORT; if NOTIFY action, set TRAIN-NOTIFY and route to ISTS terminal
[Send Header Lines '1-7' Plus Warning Lines]
The system processes filtered report output → The system should send header lines 1 through 7, then scan through all report lines and send any line marked as warning along with its preceding line
[Send Report Wrap Command]
The report transmission is complete → The system should set user function code to 'WRAP', reset report index to 1, and call the report sending routine to finalize transmission
[Start New Email Continuation]
The system prepares for continuation email → The system should clear email text, reset line counter to 1, and add continuation header message
[Add Report Line to Email]
The system processes a report line for email inclusion → The system should copy the report line to email message line at current counter position and increment line counter
[Set Audit Message: AEI SEND]
The system sets audit message content → The system should set action code to ZZZ, sending transaction to GCT1101E, user ID from CCCOM, current date and time, train ID, and AEI send log message
[Write Audit to Log Database]
The system writes to audit database → The system should move GCX105 input to message structure, call CIMS with CHNG function, call WRITMSGL to write message, and call CIMS with PURG function
[Purge Message Queue]
The system performs cleanup operations → The system should initialize accept status and call CIMS with PURG function to clear message queue
[Set Container ID and Load/Empty Status]
The system identifies the equipment as a container type → The container ID is set from the equipment ID and the load/empty indicator is set from the waybill root segment
[Get Station Table Data]
The system needs to build report information from segment data → Station table data is retrieved using the communication code ID from segment 7
[Set Container ID and Load/Empty Status]
The equipment type is container → Set the container ID from equipment ID, set load/empty indicator from waybill root segment, and mark as container type for equipment classification
[Set Bond Type]
Bill type is '00', '10', or '99' and segment 7 exists → Set bond type to in-bond type code if line release number is blank, otherwise set to 'LR' for line release, but if segment 7 doesn't exist then use bill type code directly
[Set Entry Number]
Segment 7 exists and line release number is not blank → Use line release number as entry number, otherwise if bill type is '10' use entry number if available or in-bond control number, otherwise use broker entry number
[Process Station Table Entries]
Processing station table entries for SFI information → Iterate through up to 3 station table entries, find entry with type code 'SFI' and country 'US' or blank, and extract the description
[Set Message Flags]
Initializing message flags → Set all message flags (MSG-TEN through MSG-FORTY-FOUR) to OFF state
[Set Appropriate Message Type]
Waybill is not found and container is found, or waybill is not found and container is not found but equipment is loaded and not unit train car → Set message 10 flag to ON
[Set Appropriate Message Type]
Waybill status is neither found nor not-found → Set message 26 flag to ON
[Set Appropriate Message Type]
Idler indicator is not blank → Set message 15 flag to ON with waybill root key and date, otherwise evaluate for detour processing based on origin/destination country codes and equipment load status
[Set Appropriate Message Type]
Cargo status is pending, deleted, or error → Set message 16 flag to ON
[Set Appropriate Message Type]
USCS cargo status is not 'RELEASE' and not 'EXPORT' → Set message 12 flag to ON
[Set Appropriate Message Type]
Multi-transit bond with vessel name not 'TRAIN' and location matches origin, or returned goods without train vessel name, or regular cargo without train vessel name → Set message 17 flag to ON
[Set Appropriate Message Type]
Transit bond with location not matching origin (message 38), or non-transit/non-paper/non-export bond with location not matching origin → Set message 33 for REPORT action or message 34 for SEND action
[Set Appropriate Message Type]
CPRS cargo status is 'SENT' and USCS cargo status is 'BLANK' or 'ERROR' → Set message 28 flag to ON
[Set Appropriate Message Type]
No error or warning conditions are detected → Generate default message 28 (success message)
[Combine Equipment and Message Lines]
Cargo is found and TR-CREATED-FOR-IT or special manifest flags are set → Save equipment line separately and clear report line, otherwise copy equipment line to message line and increment equipment total
[Add to Report Index]
Report index is less than 1981 → Increment report index by 1, otherwise set message 9 flag and increment request error count
[Extract Routing Information from Waybill]
The system extracts routing information → Routing information is copied from waybill root segments 1, 2, and 3, exclamation marks are replaced with spaces, and routing validation is initiated
[Set Hazmat Indicator if Applicable]
The system checks for hazmat requirements → Hazmat flag is set to 'Y' if segment 8 data exists indicating hazardous materials
[BOL Type 00/10/99?]
The cargo BOL type is '00', '10', or '99' → Check for line release availability and segment 7 data to determine appropriate bond type display, otherwise use standard BOL type
[Line Release Available?]
Checking for line release number availability → If line release number is not blank, use 'LR' as bond type, otherwise use in-bond type code
[Set Bond Type to Line Release LR]
Line release number is not blank → Set the report bond type field to 'LR'
[Set Pedimento Information]
Processing pedimento information → If station is Laredo TX and cargo has DSP hold applied, set pedimento to DSP hold indicator, otherwise set pedimento to 'X'
[Process Haulage Rights]
Processing haulage information → Check if automated haulage with CPRS carrier to determine processing path
[Check BOL Type Code]
The system processes bond type determination → If line release number exists in segment 7, set bond type to 'LR', otherwise use the in-bond type code
[Set Bond Type = 'LR' for Line Release]
The system processes bond type determination for standard BOL types → The bond type is set to 'LR' to indicate line release processing
[Set Bond Type = In-Bond Type Code]
The system determines the bond type for display → The bond type is set to the cargo's in-bond type code value
[Send Current Email Message]
The system needs to send the current message before continuing with remaining lines → The system transmits the email message using EMCSEND3 service and sets continuation flag
[Reset Email Message]
The system needs to prepare for continuation message processing → The system clears the email message content and resets message structure
[Add Continuation Header]
The system needs to add identification that this is a continuation message → The system adds 'CONTINUATION OF REPORT ....' as the first line of the new message
[Add Column Headers]
The system needs to maintain report structure in the continuation message → The system adds the appropriate column headers based on train origin (header-1A for origin 9089, header-1 for others) and detail header-2
[Reset Line Counter to 3]
The system needs to track the current line count for the new message → The system sets the line counter to 3 to account for the continuation header and two column header lines already added
[Send Final Email Message]
No more report lines need to be processed → The system sends the final email message using EMCSEND3 service
[More Report Lines?]
The system needs to determine if more lines exist to be processed → The system checks if the current mail subscription index is within bounds and if report lines contain data (not spaces or low-values)
[Is Current Line a Message Line?]
If the line type → The system identifies if the line is a message line based on message line indicators
[Increment Equipment Sequence Counter by 1]
The line requires a sequence number assignment → The equipment sequence counter is incremented by 1
[Assign Current Counter Value to Equipment Item]
The equipment item needs a sequence number → The current counter value is assigned as the sequence number for the equipment item
[Check MSG-MESSAGE-LINE Flag]
If the line type and the MSG-MESSAGE-LINE flag is set to true → The line is classified as a message line for proper report formatting
[Classify as Equipment Line]
The line is not a spacer line and not an end report line → The line is classified as an equipment line containing car or container data
[Check RPT-SPACER-LINE Flag]
The RPT-SPACER-LINE flag is set to true for the line → The line is classified as a spacer line for report formatting purposes
[Check RPT-END-REPORT Flag]
The RPT-END-REPORT flag is set to true for the line → The line is classified as the end report line marking the conclusion of the report
[Set Message Line Indicators]
The message line contains an error indicator (MSG-ERR flag is true) → The system increments the error count by 1 unless it is a spawn-related error (types 31, 34, or 43) which increments the pre-spawn count instead
[Set Message Line Indicators]
The message line contains a warning indicator (MSG-WRN flag is true) → The system increments the warning count by 1
[Set Message Line Indicators]
The message line contains an information indicator (MSG-INF flag is true) → The system increments the information count by 1
[Set Message Line Indicators]
The message line has a request error indicator (MSG-REQUEST flag is true) → The system increments the request error count by 1
[Has Warnings?]
The system checks if there are no warning messages present → The report filtering logic proceeds to show only header lines (lines 1-4)
[Send Header Lines Only Lines 1-4]
The system determines the report content to display → Only the first 4 header lines are sent to the originator, excluding detailed equipment and cargo information
[Send Header and Detail Lines Lines 1-7]
The system determines the report content to display → The first 7 lines including headers and detail column headers are sent to provide context for the warnings
[Scan Each Report Line]
The system processes each line sequentially from line 8 to the last report line → Each line is evaluated to determine if it contains warning messages that should be included in the filtered report
[Is Warning Message?]
If the message type indicator for the current line → The line is identified as a warning message if it has the warning flag set, triggering inclusion of both the previous context line and the warning line
[Include Previous Line]
The system processes the warning for display → The previous report line is included to provide context about the equipment or cargo that generated the warning
[Include Current Warning Line]
The system continues processing the warning message → The current warning line is included in the report output to display the specific warning information to the user
[Skip Non-Warning Line]
The system is generating a filtered report that only shows warnings → The non-warning line is skipped and not included in the report output sent to the user
[Apply Report Wrapping]
The system finalizes the report for transmission → Report wrapping is applied using the 'WRAP' function code to properly format and transmit the complete report to the originator
[Skip MST Message for NOTIFY]
The system processes the report wrapping logic → The system should skip the normal report processing and exit immediately
[Send Header and Warning Lines]
The system processes report line filtering → The system should send header lines (1-7) and iterate through remaining lines to send only warning message lines plus their preceding lines
[Check if SEG7 exists AND Line Release Number present?]
Segment 7 data exists AND the first line release number field is not blank → The line release number from segment 7 is selected as the entry number for display
[Check if BOL Type = '10'?]
The BOL type code equals '10' → The system checks for entry number availability to determine the appropriate number to display
[Use Broker Entry Number from RT022]
The BOL type code != '10' → The broker entry number from RT022 is selected as the entry number for display
[Use Line Release Number from SEG7]
Entry number display processing is executed → The line release number from segment 7 first occurrence is moved to the entry number display field
[Use Broker Entry Number from RT022]
Entry number display processing is executed → The broker entry number from RT022 is moved to the entry number display field
[Scan Segment 2 Reference Data]
The system performs a loop from index 1 to maximum occurrences until data is spaces or low-values → Each reference entry is examined for qualifier codes FEN and KCM
[Station = Laredo TX?]
The US station code equals the Laredo TX station constant → Special DSP hold processing rules are applied, otherwise default pedimento display is used
[DSP Hold Applies?]
The cargo record indicates DSP-HOLD-APPLY is true → The DSP hold indicator value is used for pedimento display
[Set Pedimento to DSP Hold Indicator]
The system sets the pedimento display value → The pedimento field is populated with the DSP hold indicator value
[Set Pedimento to Default Display]
The system sets the pedimento display value → The pedimento field is set to 'X' as the default display indicator
[Station is Laredo TX CST-LAREDO-TX-STATION]
The station code equals Laredo TX station (CST-LAREDO-TX-STATION) AND the cargo has DSP hold apply flag set to true → The system should apply the DSP hold indicator to the cargo's pedimento field
[Set Standard Pedimento Indicator]
The station code != Laredo TX station (CST-LAREDO-TX-STATION) → The system should set the standard pedimento indicator (X) for the cargo
[Is Message Line?]
The system checks if the line contains a message using MSG-MESSAGE-LINE function → The system identifies whether the line is a message line requiring further error categorization or continues with normal processing
[Increment Pre-Spawn Count]
The system processes the pre-spawn error → The system adds 1 to the PRE-SPAWN-CNT counter to track errors requiring special manifest processing
[Add 1 to RPT-WARNING-CNT]
The system processes the warning message → The system adds 1 to the RPT-WARNING-CNT counter to track total warnings in the report
[Add 1 to RPT-INFO-CNT]
The system processes the informational message → The system adds 1 to the RPT-INFO-CNT counter to track total informational messages in the report
[Add 1 to RPT-IDX]
The system increments the report position → The system adds 1 to RPT-IDX to move to the next available report line for subsequent processing
[Increment Proceed Count]
The system processes cargo with status 'PROCEED', 'PROCEED-HOLD-DEST', or 'ARRIVED' with bond type 'IT', 'TE', or 'TR' → The system increments the proceeding cargo count by 1
[Waybill Not Found and Empty Equipment?]
The waybill was not found in the previous processing and the TIB equipment load/empty indicator is 'E' (empty) → The system should generate message 37 indicating a TIB empty car error
[Generate Message 32: TIB Report Warning]
The request action is REPORT → The system should generate message 32 as a TIB report warning
[Generate Message 32: TIB Report Warning]
TIB validation fails → The system should generate message 32 indicating TIB report warning
[Generate TIB Missing Message for SEND]
TIB validation fails → If waybill was not found previously and equipment is empty, generate MSG-THIRTY-SEVEN, otherwise generate MSG-THIRTY-ONE and create special manifest request
[Generate TIB Missing Message for REPORT]
TIB validation fails → MSG-THIRTY-TWO should be generated and added to report
[Extract Container Details]
The system processes the container for sequencing → The container ID, platform position (A-E), well number (1-4), and slot position (T/B) are extracted and stored
[Get Routing Information from FWIQINFO Segment]
The system needs detailed routing information → FWIQINFO segment is accessed with segment type 'B1' to retrieve routing data
[Parse Routing Fields from 34-byte String]
The system processes the routing data string → The 34-byte string is parsed field by field, with each field terminated by spaces, and field length is calculated for each component
[Extract SCAC Code 1, Extract SCAC Code 2, Extract SCAC Code 3, Extract SCAC Code 4]
The system processes routing field sequence → SCAC codes are extracted in order: field 1 as SCAC1, field 3 as SCAC2, field 5 as SCAC3, and field 7 as SCAC4
[Extract Junction Point 1 R260, Extract Junction Point 2 R260]
The system processes routing field sequence → Junction points are extracted in order: field 2 as Junction1-R260, field 4 as Junction2-R260, and field 6 as Junction3-R260
[Retrieve Equipment Routing Information]
The system needs complete equipment routing details → Access the inquiry information segment to retrieve routing data and populate the routing information fields in the waybill record
[Read Container Equipment Data]
The system processes container equipment data → Container ID, platform, slot, and well information are extracted from equipment segments
[Get Routing Information from FWIQINFO]
Routing information is requested → The system retrieves routing details from FWIQINFO using segment type 'FWIQINFO' and key 'B1'
[Parse Routing Fields - SCAC Codes and Junction Points]
Routing field parsing is initiated → The system parses routing information to extract up to 4 SCAC codes and their corresponding junction points (R260 codes) from the 34-character routing field
[Access Inquiry Database]
The system needs container information → The system should access the FWIQROOT segment in the inquiry database using the waybill key
[Read FWIQBOTL Segments]
The system processes inquiry data → The system should read FWIQBOTL segments and scan bottom line records for T/C XREF entries
[Set Message to 'CAR-ADDED-LOG-MESSAGE']
The audit message content is being assigned → The message should be set to the predefined 'CAR-ADDED-LOG-MESSAGE' constant to describe the operation
[Prepare Message for Database]
The message is being prepared for database storage → The complete audit log input structure should be moved to the database message format
[Change Database Function]
Database operations are being initiated → A CHNG (change) function should be called on the alternate PCB to prepare for message insertion
[Write Audit Log Message]
The audit log entry is being written to the database → The WRITMSGL service should be called to write the audit message with proper message code, content, length, and module name
[Prepare GCT1401E Message]
The report message needs to be formatted for transmission → The GCX140 input data is moved to GCT1401E message format
[Change Message Function]
Message transmission needs to be initiated → The message function is changed to active status for transmission
[Write Customer Report Message]
Report needs to be transmitted to recipients → The customer report message is written to the message queue for delivery
[Purge Message Queue]
Message transmission needs to be finalized → The message queue is purged to complete the transmission process
[Access Waybill Database for SHIPCOMM Segment]
The system attempts to access the waybill database for communication data → The system performs a database read operation on the SHIPCOMM segment using the waybill key
[Communication Data Found?]
If the result of the database access → The system determines if communication data is available based on whether the database status indicates successful retrieval
[Retrieve Shipment Communication Information]
The database read operation successfully locates the SHIPCOMM segment → The shipment communication information is retrieved and made available for further processing

Structural Validations

[3:Train Origin Validation]
System validates train origin → If origin is blank, or station not found in GCSTBRT-SC table, or US station code is blank, generate error message MSG-TWO and increment report index
[5:Train Destination Validation]
System validates train location → If train location is blank, or location not found in GCSTBRT-SD table, or port code is blank, generate error message MSG-TWENTY and increment report index
[6:US Customs Train ID Management]
System checks for existing train with same ID → If train exists and is marked for deletion, delete the existing record. If train exists and not marked for deletion, generate error message MSG-SIX and increment report index
[49:Equipment Limit Validation]
System validates equipment count → If first equipment item indicates no more equipment OR equipment count exceeds 500 items, generate error message MSG-FIVE and increment report index
[Is Permitted Action?]
The request action is not one of the permitted actions (SEND, REPORT, NOTIFY) → The system sets error message MSG-ONE and adds it to the report index to indicate invalid action
[Train Origin Empty?]
The train origin field is empty or contains only spaces → The system sets an error message indicating invalid train origin and stops validation
[Table Record Found?]
The system searches the general table GCSTBRT with table type SC (Station Code) using the train origin as the search key → If no matching record is found, the system sets an error message for invalid train origin
[US Station Code Exists?]
The system extracts the station segment data and checks the US station code field → If the US station code is empty or spaces, the system sets an error message for invalid train origin
[ETA Date = '000000'?]
The ETA date field contains '000000' (empty date) → The system should set error message 'ETA Date Required' and stop ETA validation
[Date/Time Valid?]
Date conversion fails:
ETA time is not numeric
ETA hour is not between 00-23
ETA minute is not between 00-59
→ The system should set error message 'Invalid ETA Format'
[Train Location Empty?]
The train location field (REQ-TRAIN-LOCATION) is empty or contains only spaces → The system should set error message MSG-TWENTY indicating train location is required and mark validation as failed
[Location Found in General Table?]
The search operation completes → If the location is not found in the table, the system should proceed to set an invalid location error message
[Port Code Exists for Location?]
The system checks the port code field (GCSTBRT-SD-PORT-CODE) for the location → If the port code is empty or spaces, the system should set error message MSG-TWENTY indicating invalid train location
[Set Error Message: Invalid Train Location]
The validation error is detected → The system should set error message MSG-TWENTY and increment the report index to record the validation failure
[Table Read Successful?]
The system checks the operation result → If the read was successful, the AD segment data is extracted, otherwise an error is set
[Merlin ID Present?]
The system checks the Merlin ID field → If the Merlin ID is spaces or missing, an error message is set indicating missing customs ID
[Set Error Message: Merlin ID Missing]
The validation check fails → Error message MSG-SEVEN is set indicating customs ID configuration problem
[Set Error Message: Merlin Database Not Found]
The database is found to be unavailable or not accessible → Error message MSG-EIGHT is set indicating Merlin database connectivity problem
[Get Originator Terminal ID from CCCOM]
The originator terminal ID from CCCOM is spaces, high-values, or low-values → The system assigns default terminal ID '9999' for general table lookup
[Set Container Error Message MSG-41]
Failed equipment is container type → Container equipment error message MSG-41 is set and equipment error flag is activated
[Set Car Error Message MSG-42]
Failed equipment is railcar type → Railcar equipment error message MSG-42 is set and equipment error flag is activated
[TR Bond Not Found and TR Created for IT?]
TR bond was not found during processing → Generate message 35 indicating TR bond issue and add to report with equipment details
[TE Bond Not Found and TE Created for TE?]
TE bond was not found during processing → Generate message 39 indicating TE bond issue and add to report with equipment details
[USMX-88 Found and SPLC-TR Not Found?]
SPLC-TR was not found during processing → Generate message 46 indicating USMX-88 issue and add to report with equipment details
[Generate Message 46 - USMX-88 Missing TR]
USMX-88 is found but SPLC-TR is not found → The system should generate message 46 indicating missing transit manifest for USMX-88 cargo
[Generate Message 45 - TE Missing IT]
SPLC-TE is found but SPLC-IT is not found → The system should generate message 45 indicating missing in-transit manifest for transport export cargo
[Generate Message 39 - TE Bond Missing]
TE is created for TE but TE bond is not found → The system should generate message 39 indicating missing TE bond
[Set Processing Ineligible Flag]
The cargo status is pending, deleted, or error → A message should be generated indicating the cargo cannot be processed normally
[Check for FEN and KCM Qualifiers in Segment 02]
System checks for Segment 02 availability → Processing continues only if Segment 02 data is present
[Equipment Type Valid?]
The equipment type validation service is called with the equipment details → If validation fails, generate appropriate error message based on whether it's a container or car, increment error count, and mark as equipment error
[MSG-40: Container Type Error]
The equipment validation service returns unsuccessful status for a container → Set message type 41 (container type error), add to report index, and mark as equipment error
[MSG-41: Car Type Error]
The equipment validation service returns unsuccessful status for a car → Set message type 42 (car type error), add to report index, and mark as equipment error
[MSG-10: Loaded Equipment No Waybill]
No waybill is found for the equipment and no container is found → Generate message type 10 indicating loaded equipment without waybill documentation
[MSG-26: Waybill Database Error]
The waybill database returns an error status (not found vs access error) → Generate message type 26 indicating waybill database access problems
[MSG-15: No US Cargo Found]
Cargo search returns no results and equipment is not a conveying car → Generate message type 15 with waybill root key and date indicating missing US cargo documentation
[MSG-44: Empty Car with Residue Weight]
No US customs cargo is found and equipment is not an idler car → Generate message type 44 with waybill information indicating empty car with residue weight
[MSG-16: Cargo Pending/Deleted/Error]
Cargo status is pending, deleted, or error in the CPRS system → Generate message type 16 indicating cargo cannot be processed due to status
[MSG-12: TR Bond Status Invalid]
US customs cargo status is not 'RELEASE' and not 'EXPORT' → Generate message type 12 indicating invalid transit bond status for processing
[MSG-25: MT Bond Vessel Mismatch]
Vessel name is not 'TRAIN' or spaces and station code matches cargo location → Generate message type 25 indicating vessel name mismatch for multi-transit bond
[MSG-17: Non-Train Vessel]
Cargo is not multi-transit and vessel name does not indicate train transport or returned goods vessel requirements are not met → Generate message type 17 indicating non-train vessel designation issue
[MSG-38: TR Bond Location Mismatch]
Train origin station code does not match cargo location ID → Generate message type 38 indicating transit bond location mismatch
[MSG-33: Report Location Mismatch]
Station code does not match cargo location and cargo is not export type or bill type 15 → Generate message type 33 indicating location mismatch in report mode
[MSG-35: IT Bond Missing]
TR-CREATED-FOR-IT flag is set but no TR bond was found during processing → Generate message type 35 indicating missing in-transit bond documentation
[MSG-39: TE Bond Missing]
TE-CREATED-FOR-TE flag is set but no TE bond was found during processing → Generate message type 39 indicating missing transport export bond documentation
[MSG-45: TE Special Manifest Missing]
SPLC-TE-FOUND flag is set but SPLC-IT-NOT-FOUND flag is also set → Generate message type 45 indicating missing transport export special manifest
[MSG-46: USMX-88 Special Manifest Missing]
USMX-88-FOUND flag is set but SPLC-TR-NOT-FOUND flag is also set → Generate message type 46 indicating missing US-Mexico special manifest
[MSG-37: Empty Car TIB Required]
Waybill was not found in previous processing and car is empty → Generate message type 37 indicating TIB validation is required for empty car
[Error Type Classification]
Message type indicates error, warning, or informational status → Increment appropriate counter (error, warning, or info) and classify for processing
[MSG-9: Report Overflow]
Report index exceeds 1981 lines → Generate message type 9 indicating report overflow and increment request error count
[Generate Container Error Message MSG-41]
The system handles the classification failure → The system generates error message MSG-41 indicating container equipment type determination failure
[Generate Car Error Message MSG-42]
The system handles the classification failure → The system generates error message MSG-42 indicating car equipment type determination failure
[Generate Container Error Message]
Error message generation is required → System generates message forty-one indicating container classification error
[Generate Car Error Message]
Error message generation is required → System generates message forty-two indicating car classification error
[Generate Equipment Error Message]
Classification module returns failure status → Equipment error flag is set and appropriate error message is generated based on container or car classification type
[Status = PENDING, DELETED, or ERROR?]
The cargo status is PENDING, DELETED, or ERROR → Set message sixteen indicating invalid cargo status and continue with bond type validation
[Train Origin ≠ Cargo Location? and Action = REPORT?]
The request action is REPORT → Set message thirty-eight indicating location mismatch and continue validation
[Bond Type = TR?]
The US cargo status is not RELEASE and not EXPORT → Generate MSG-TWELVE error message indicating TR bond status violation
[Bond Type = MT?]
The vessel name is not TRAIN and not SPACES and the origin station code equals the current location ID → Generate MSG-TWENTY-FIVE error message for MT bond vessel validation failure
[Returned Goods Bond?]
The vessel name first character is not T → Generate MSG-SEVENTEEN error message for returned goods vessel validation failure
[Default Bond Processing?]
The vessel name is not TRAIN → Generate MSG-SEVENTEEN error message for default bond vessel validation failure
[Send MSG-TWELVE - TR Bond Status Error]
The request action is not SEND → Set MSG-TWELVE message flag and continue processing
[Generate TR Bond Status Error Message]
The error message needs to be generated → Set MSG-TWELVE error flag and MSG-TWELVE-ON status for both SEND and non-SEND actions
[Does Origin Station Match Current Location?]
The origin station code is compared with the current cargo location → Error message is generated if station codes match, otherwise processing continues normally
[Validate Train Origin Station]
The system validates the train origin station → If train origin is blank, set station code error message, OR if train origin is not found in station code table, set station code error message, OR if station has no valid US station code, set station code error message
[Validate Train Destination Location]
The system validates the train destination location → If train location is blank, set location error message, OR if train location is not found in station destination table, set location error message, OR if location has no valid port code, set location error message
[Generate Message 37 - TIB Empty Car Error]
The system processes TIB validation failure → Generate message 37 indicating TIB empty car error and increment report index
[Generate Message 31 - TIB Validation Error]
The system processes TIB validation failure for SEND action → Generate message 31 for TIB validation error, increment report index, and create pre-spawn request for TIB manifest processing
[Generate Authorization Error Message]
The system processes the authorization failure → The system creates message forty-three, adds to report index, and continues processing
[Check for Equipment Errors]
Checking for equipment-related errors → If equipment type validation failed, generate appropriate error message (MSG-FORTY-ONE for containers, MSG-FORTY-TWO for cars), set equipment error flag, and increment report index
[Check for Cargo Validation Errors]
Checking cargo against validation rules → Validate cargo status (pending, deleted, error states), check bond type requirements, verify vessel name compliance, validate location matching for transit bonds, and generate appropriate error messages for violations
[Equipment Type Valid?]
The GCCCARTP module is called to validate and retrieve equipment type → If successful, the equipment type code is stored in the report, if unsuccessful, an equipment error flag is set and appropriate error message is added based on container or car type
[Add Equipment Error Message]
Error message generation is triggered → Message 41 is set if the equipment is a container, Message 42 is set if the equipment is a car, equipment error flag is set, and report index is incremented
[Generate Equipment Type Error Message]
The equipment type classification call fails → The system generates either container error message (MSG-FORTY-ONE) or car error message (MSG-FORTY-TWO) based on equipment type and sets equipment error flag
[Scan Segment 02 for FEN/KCM Qualifiers]
A reference number qualifier equals 'FEN' → Set FEN found flag to true indicating foreign entity number is present
[Scan Segment 02 for FEN/KCM Qualifiers]
A reference number qualifier equals 'KCM' → Set KCM found flag to true indicating KCM reference is present
[Set Error Message Flags]
If the message content and MSG-ERR flag is true → The message is classified as an error message and error counter is incremented
[Increment Request Error Counter]
The message is flagged as a request error (MSG-REQUEST flag is true) → The request error counter is incremented by 1
[Check Report Index Limit]
The current report index (RPT-IDX) is less than 1981 → The report index is incremented by 1 and processing continues
[Equipment Type Call Successful?]
If the service call return status → Processing continues with type assignment if successful or generates error message if failed
[Generate Equipment Error Message]
The system processes the failed classification → Appropriate error message is generated based on whether equipment is container or car type and equipment error flag is set
[Generate Equipment Error Message]
Processing the failed classification result → Container type error message (Message 41) is generated and equipment error flag is set
[Generate Equipment Error Message]
Processing the failed classification result → Rail car type error message (Message 42) is generated and equipment error flag is set
[Generate Equipment Error Message]
The system processes the failed classification response → The system should generate message forty-one for container equipment or message forty-two for car equipment, set equipment error flag, and increment report index
[Generate Container Error Message]
Generating error response → Container-specific error message is created and error index is incremented
[Generate Car Error Message]
Generating error response → Car-specific error message is created and error index is incremented
[EDI Module Call Successful?]
The module execution completes → The system checks if the EDI module call was successful based on the return status
[Parameters Valid?]
The system validates the EDI parameters → If parameters are invalid, the system prepares for abend with error message about invalid module parameters
[System Abend - Invalid Parameters]
The system determines that the EDI module parameters are invalid → The system sets error message to 'GCCE358 MODULE PARAMETERS INVALID' and performs system abend
[Email Send Successful?]
The system validates the email send operation → If email return status is not successful then system abends with error message, otherwise processing continues normally
[Abend with Error Message]
The system handles the email failure → An error message 'SEND TO FILE OF OM01247 FAILED' is set and the system abends
[Email Send Successful?]
The system checks the email send status → If email send is not successful then trigger system error with message 'SEND TO FILE OF OM01247 FAILED', otherwise proceed to purge IMS message queue
[Line Count > 699?]
Line count reaches the limit → The system checks if line count exceeds 699 lines and triggers email segmentation if limit is reached
[Send Error Notification to Support]
The system detects email send failure → The system sends error notification to default Merlin ID and AEI9999 support ID with failure details
[Validate Cargo Status = SENT]
System checks cargo transmission status → Cargo is eligible only if CPRS cargo status description (GCUSRT-RT10B-CPCARGO-STAT-DSC) equals 'SENT'
[GCCUTRIO Database Error]
The operation returns invalid parameters, no equipment found, or too many equipment items → The system formats an error message with return code and train ID for further processing
[GCCUSIO Database Error]
The operation returns a non-blank and non-zero error number → The system formats an error message with return code and error message for further processing
[DB2 SQL Error]
The SQL code indicates a database error condition → The system formats an error message with the SQL code and sends email notification to support
[Format Error Message]
Error details need to be communicated → The system builds a formatted error message string containing the module name, return code, and relevant key information
[First Equipment Empty OR Last Equipment Not Empty?]
The system checks equipment array boundaries and finds either the first equipment item is marked as 'no more equipment':
the 500th equipment item is not marked as 'no more equipment'
→ The system should set an invalid equipment range error message (MSG-FIVE) and add it to the error report
[Generate Authorization Error Message]
The system blocks the special manifest creation → Generate message forty-three indicating insufficient authorization for special manifest processing
[Set Container Error Message MSG-41]
The system processes the classification failure → The system sets message type 41 indicating container classification error
[Set Car Error Message MSG-42]
The system processes the classification failure → The system sets message type 42 indicating car classification error
[Is Segment Type = '02'?]
The system checks the segment type → The system should only proceed with FDA reference extraction if the segment type is '02', otherwise skip FDA processing
[Generate Equipment Error Message]
The system processes the classification failure → If container equipment, message 41 should be set; if car equipment, message 42 should be set; and equipment error flag should be activated
[Generate Container Error Message MSG-FORTY-ONE]
The system processes the failed response → The system should generate error message MSG-FORTY-ONE indicating container equipment type determination failure
[Generate Car Error Message MSG-FORTY-TWO]
The system processes the failed response → The system should generate error message MSG-FORTY-TWO indicating car equipment type determination failure
[Add Error to Report Index]
The system processes the equipment error for reporting → The system should increment the report index counter to ensure proper sequencing of error messages in the final report
[Process Message Validation Rules]
The system processes message validation rules → The system should evaluate waybill found/not found conditions, cargo status conditions, bond type validations, location mismatches, and generate appropriate error, warning, or informational messages based on the specific combination of conditions
[Line Has Errors/Warnings?]
The system assesses line status → The system should identify lines with message indicators set for errors, warnings, or informational messages
[Equipment Error?]
Equipment error condition is detected (WS-EQUIPMENT-ERROR is true) → Equipment error flag is set and message line construction is terminated early
[Set Hazmat Flag if Present]
Cargo contains segment 8 data indicating hazardous materials → Hazmat flag is set to 'Y' in the report line
[Error Conditions?]
The GCCCARTP call for equipment type validation is not successful → Message 41 error is set and equipment error flag is activated
[Error Conditions?]
The GCCCARTP call for equipment type validation is not successful → Message 42 error is set and equipment error flag is activated
[Set Error Message Flag]
Waybill is not found and either container is found or equipment is loaded and not an SBU van → Message 10 error flag is set
[Set Error Message Flag]
Waybill is neither found nor confirmed as not found (system access issue) → Message 26 error flag is set
[Set Error Message Flag]
No cargo is found and idler indicator is not spaces → Message 15 error flag is set with waybill root key and date information
[Set Error Message Flag]
Cargo status is pending, deleted, or error → Message 16 error flag is set
[Set Warning Message Flag]
In-bond type is 'TR' and cargo status is neither 'RELEASE' nor 'EXPORT' → Message 12 warning flag is set
[Set Warning Message Flag]
Multi-transit bond with non-train vessel at same location, or returned goods with non-train vessel, or regular cargo with non-train vessel → Message 17 warning flag is set
[Set Error Message Flag]
Train origin is not spaces, in-bond type is 'TR', and station code does not match cargo location → Message 38 error flag is set
[Set Error Message Flag]
Train origin is not spaces, in-bond type is not 'TR', bill type is not '15', not export type, and station code does not match cargo location → Message 33 is set for report action or Message 34 is set for send action with pre-spawn processing
[Set MSG-SIXTEEN for Pending/Deleted/Error Cargo Status]
Cargo is found AND cargo status is pending:
deleted
error
→ Set MSG-SIXTEEN message indicator to true and set MSG-SIXTEEN-ON flag to true
[Set MSG-SEVENTEEN for Non-Train Vessel Issues]
Cargo is found AND ((multi-transit bond type AND not train vessel value AND station US code equals cargo location ID):
(not multi-transit bond type AND returned goods type AND not train vessel value AND vessel name position 23 is not 'T')
(not multi-transit bond type AND not returned goods type AND not train vessel value))
→ Set MSG-SEVENTEEN message indicator to true and set MSG-SEVENTEEN-ON flag to true
[Set MSG-THIRTY-EIGHT for Location Mismatch in TR Bonds]
Cargo is found AND request action is report AND train origin is not spaces AND bond type is 'TR' AND station US code != cargo location ID → Set MSG-THIRTY-EIGHT message indicator to true and set MSG-THIRTY-EIGHT-ON flag to true
[Set MSG-THIRTY-THREE for Border Code Mismatch in Reports]
Cargo is found AND train origin is not spaces AND bond type is not 'TR' AND bill type is not '15' AND not export type AND station US code != cargo location ID AND request action is report → Set MSG-THIRTY-THREE message indicator to true and set MSG-THIRTY-THREE-ON flag to true
[Set MSG-TWENTY-EIGHT for Cargo Status Issues in Reports]
Request action is report AND cargo is found AND ((CPRS cargo status is sent AND USCS cargo status is blank):
(CPRS cargo status is sent AND USCS cargo status is error))
→ Set MSG-TWENTY-EIGHT message indicator to true
[Container Found in Waybill?]
System checks the container status indicator → If container status is spaces (found), proceed with container processing, otherwise use inquiry database as fallback
[Container Found in Inquiry?]
System checks the status code from inquiry retrieval → If status code is spaces (success), proceed with inquiry container setup, otherwise mark container as not found
[Check for Duplicate Equipment]
The system scans for duplicate equipment up to 1980 report lines → The system compares each equipment car ID against the previously held car ID, retains the first occurrence of each unique car ID, and clears the car ID and equipment type fields for any subsequent duplicate entries while preserving error, warning, and information message lines
[Send Error Report to Originator]
The system sends error notification to the originator → The system sets the call letters to TRAIN-ERROR, includes all error messages and details in the report, and transmits the error report to the originating terminal via GCSTONLY module
[Check Line Type]
Processing each report line for train manifest creation → Include only lines that are not message lines, end report markers, or spacer lines in equipment processing
[Email Send Successful?]
The email transmission result is evaluated → If the email return status indicates failure, the system generates an error message 'SEND TO FILE OF OM01247 FAILED' and terminates processing
[Line Count > 699?]
The line counter exceeds 699 lines → The system should trigger email message transmission and prepare for continuation message processing
[Abort - Equipment Overflow]
The system encounters equipment overflow → The system abends with the message 'TRAIN LIST TABLE (GCWUTRLS) OVERFLOW'
[Abort - Storage Failed]
The database storage fails with an already exists condition → The system abends with the message 'ISRT OF GCSUTRT FAILED'
[EDI Module Call Successful?]
The system checks the return status from the EDI module → If the module call was not successful, the system proceeds to parameter validation, otherwise continues with AEI processing check
[Validate EDI Parameters]
The system validates the EDI processing parameters → If parameters are invalid, the system abends the EDI transmission process
[EDI Transmission Failed - Abend]
The system encounters invalid EDI processing parameters → The system abends the EDI transmission process and reports the failure
[Email Send Successful?]
The system checks the email send return status → If the email send was not successful, the system should trigger an error with message 'SEND TO FILE OF OM01247 FAILED' and Execute system abort processing
[Generate Equipment Error Message]
The classification service fails to return a valid equipment type code → An error message is generated (MSG-FORTY-ONE for containers, MSG-FORTY-TWO for cars), equipment error flag is set, and processing continues
[Info String Empty]
The system checks the report info string → If the info string is empty or contains only low values, segment data processing is initiated, otherwise equipment status counting begins
[Generate Equipment Error Message]
The classification call fails → Generate message 41 for container classification failure or message 42 for car classification failure, set equipment error flag, and increment report index
[Generate Equipment Error Message]
The system processes the classification failure → Error message MSG-FORTY-ONE is set for containers or MSG-FORTY-TWO is set for cars, equipment error flag is set, and report index is incremented
[Check Equipment Routing Validation]
The system validates equipment routing → Routing validation is performed for up to 9 routing segments until valid routing is found or all segments are checked
[Line Count > 699?]
The system checks if the current line count exceeds 699 lines → The system determines whether to continue adding lines or split the message
[Add to Report Index]
The report index (RPT-IDX) is less than 1981 → The system increments the report index by 1, otherwise it sets message type 9 error and increments request error count
[Segment 2 Data Available?]
The system checks for segment 2 data availability using 88-SEG2 condition → Processing continues to scan reference data if segment 2 exists, otherwise pedimento processing is skipped
[Error Type?]
If the message type using MSG-ERR, MSG-WRN, and MSG-INF indicators → The system classifies the message as either an error requiring special handling, a warning, or an informational message
[Error Type 31, 34, or 43?]
The system checks if the message type indicator equals 31, 34, or 43 → The system determines whether to increment the pre-spawn count or the regular error count
[Increment Regular Error Count]
The system processes the regular error → The system adds 1 to the RPT-ERROR-CNT counter to track standard processing errors
[Request Error?]
The system checks if the message is flagged as MSG-REQUEST type → The system determines whether to increment the request error counter in addition to the standard message counters
[Add 1 to RPT-REQ-ERROR-CNT]
The system processes the request error → The system adds 1 to the RPT-REQ-ERROR-CNT counter to track errors specifically related to request processing
[Report Index < 1981?]
The system checks if the current RPT-IDX is less than 1981 → The system either safely increments the index or handles the overflow condition by setting an overflow error message
[Set Overflow Error Message]
The system attempts to add another message line → The system sets MSG-NINE error message and increments the request error count to indicate report overflow condition
[Generate Message 31: TIB Validation Error]
The equipment does not qualify for empty car error processing → The system should generate message 31 for TIB validation error and Execute pre-spawn GCT1011E processing
[Generate Message 37: TIB Empty Car Error]
TIB validation fails → The system should generate message 37 indicating TIB empty car error
[Generate Message 31: TIB Validation Error]
TIB validation fails → The system should generate message 31 for TIB validation error and create a pre-spawn TIB record
[Routing Data Available?]
The system checks routing data availability → If routing information is spaces or low-values, equipment is marked as having no routing available
[Routing Info Available?]
The system checks routing information availability → If routing information is available and not spaces or low-values, proceed to parse routing fields; otherwise build complete equipment record without routing details
[Inquiry Root Found?]
The FWIQROOT segment lookup is performed → If the inquiry root is not found, container retrieval should fail, otherwise proceed to read bottom line segments
[Train Origin Code Empty?]
The train origin code field is empty or contains only spaces → The system sets an error message indicating train origin is required and stops further validation
[Station Code Found in Table?]
The system queries the station codes table with the train origin code → If the station code is not found in the table, the system sets an error message for invalid train origin
[US Station Code Present?]
The system checks the US station code field in the retrieved station record → If the US station code field is empty or spaces, the system sets an error message for invalid train origin

As an EDI Gateway Service,
I want to orchestrate and execute all GCCB4RIO 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 and Equipment Counters, Initialize Segment Counter and Equipment Counter]
The system begins equipment retrieval → Both segment quantity counter and equipment quantity counter are set to zero

Core Acceptance Criteria

[Train List Replacement]
The equipment quantity is not zero and not exceeding 2500 → The system deletes existing root record, inserts new root record, and then inserts equipment data if successful
[Equipment Segmentation]
The equipment quantity is divided by 50 → The system creates the required number of segments and pads the last segment with spaces if there's a remainder
[Route to DELETE TRAIN-LIST Operation]
The system processes the request → The system performs D100-DLET-ROOT and if successful sets DELETE-PENDING and DELETED-CONFIRM flags, performs B100-ISRT-ROOT, and if successful sets equipment quantity to zero and initializes equipment segments
[Execute Database Query for Train Root Segment]
The system executes the database query for train root segment → The system performs a database get operation on the GCSB4RT segment using the configured parameters
[Copy Train Header Data to Output Structure]
The system copies train header data to output structure → The train root segment data from the database is moved to the train header field in the train list structure
[Get Next Equipment Segment from Database]
The system requests the next equipment segment → Database operation is performed to get next parent equipment segment
[Store Equipment Segment Data]
The segment data is available → The equipment segment data is moved to the corresponding position in the train list equipment segments array
[Calculate Equipment Count in Last Segment]
The system needs to determine total equipment count → The system counts non-space equipment entries in the last segment up to position 50
[Clear Unused Segment Slots]
There are unused segment positions beyond the last retrieved segment → All unused segment positions are cleared with spaces
[Calculate Total Equipment Count]
Total equipment calculation is required → Total equipment equals (number of segments multiplied by 50) plus the count of items in the final segment
[Calculate Equipment Count in Last Segment]
The system needs to determine the actual count of equipment in the last segment → The system iterates through equipment positions starting from position 1, increments counter for each non-empty position, stops when an empty position is found or maximum 50 positions is reached, and returns the actual equipment count by subtracting 1 from the final counter value
[Total Count = 0?]
The calculated total equipment count (segments × 50 + remaining equipment) equals zero → Set NO-EQP status to indicate no equipment is present
[Read First Equipment Segment]
The system needs to read equipment segments → Equipment segment data is retrieved from the database
[Store Equipment Segment Data]
The segment data needs to be processed → The equipment segment data is stored in the train list structure
[Read Next Equipment Segment]
More segments need to be processed → The system reads the next equipment segment from database
[Increment Segment Counter]
The segment counter needs to be updated → The segment counter is incremented by one
[Count Equipment in Last Segment]
Equipment count in the final segment needs to be determined → The system counts non-empty equipment positions in the last segment
[Calculate Total Equipment Count]
Total equipment count needs to be determined → Total equipment count equals (number of segments × 50) + remaining equipment count
[Copy Train Header Data to Database Segment]
The system prepares to insert the train header record → The train header data from the working list is copied to the database segment structure
[Copy Updated Record Back to Train List]
The system processes the insertion result → The database segment data is copied back to the train header working area
[Calculate Number of Segments Needed]
The system processes equipment for insertion → The system divides the total equipment quantity by 50 to determine the number of segments needed and calculates any remainder
[Equipment Count Divides Evenly by 50?]
There is a remainder greater than zero → The system adds one more segment to accommodate the remaining equipment items
[Add One More Segment for Remainder]
The system processes the remainder → The system increments the segment count by 1 and increments the equipment position by 1
[Fill Remaining Slots with Spaces]
The system processes equipment positions from the last equipment position to position 50 → The system fills all remaining positions in the segment with spaces
[Process Each Equipment Segment]
The system processes equipment segments → The system iterates through each segment from 1 to the total segment count
[Move Equipment Data to Segment]
The system processes a specific segment → The system moves the equipment data from the train list segment to the database equipment structure
[Set Segment Number]
The system prepares the segment for database insertion → The system assigns the current segment index as the segment key number
[Insert Equipment Segment to Database]
The system executes the database insertion → The system calls the database insert function for the equipment segment
[Train Record Deleted Successfully]
The system processes the successful deletion → Set delete pending and confirmed flags to true, reinsert the train record, reset equipment quantity to zero, and initialize equipment segments to spaces
[Clear Equipment Segments]
The system finalizes the logical deletion process → All equipment segment data must be initialized to empty values
[Calculate Number of Segments Needed]
System needs to determine storage segments required → System divides equipment quantity by 50 to get number of segments and remainder items
[Equipment Count Divisible by 50?]
There is a remainder greater than zero → System adds one additional segment to accommodate remaining equipment
[Add One Additional Segment]
System processes the remainder calculation → System adds 1 to the segment quantity
[Calculate Remainder Equipment in Last Segment]
System needs to pad remaining positions → System adds 1 to remainder quantity to get starting position for space padding
[Fill Empty Positions with Spaces]
System processes the segment for storage → System fills remaining positions from remainder position plus 1 through position 50 with spaces
[Process Each Segment]
System processes segments for database insertion → System iterates through segments from 1 to total segment quantity
[Set Segment Number]
System prepares segment for database storage → System assigns current segment index as the segment key number
[Store Equipment Segment to Database]
System executes database storage operation → System inserts the equipment segment into the database
[More Segments to Process?]
System checks for remaining segments → System continues processing if current segment index is less than or equal to total segment quantity, otherwise completes processing

Structural Validations

[Equipment Segmentation]
The number of equipment segments reaches 50 → The system stops processing additional segments and sets 'Too Many Equipment' status
[Train Record Found?]
The system checks if the train record was found → If the database operation was successful, the train record is considered found, otherwise the train record is considered not found
[Reached 50 Segments Limit?]
The segment index reaches 50 → The system stops retrieving additional segments to enforce the maximum limit
[Set Error: Too Many Equipment]
More than 50 equipment segments were found in the database → The system sets the 'too many equipment' error flag
[Equipment Position Empty?]
The system checks if the equipment position contains data → The system determines the position is empty if it contains spaces, otherwise it contains valid equipment data
[Retrieved All Segments Successfully?]
Equipment retrieval reaches the maximum of 50 segments and more segments still exist in the database → Set TO-MANY-EQP status to indicate equipment count exceeds processing limit
[Reached 50 Segments Limit?]
The segment index reaches 50 → The system stops processing additional segments
[Equipment Position Empty?]
An equipment position is examined → The system determines if the position contains equipment data or is empty (spaces)
[Set Too Many Equipment Flag]
More than 50 equipment segments are found in the database → The system sets the too many equipment flag to indicate excessive equipment data

As an EDI Gateway Service,
I want to orchestrate and execute all GCCDESCU 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 Counter to 1]
The system initializes the segment processing loop → The segment counter is set to 1 and the more-segments flag is set to true

Core Acceptance Criteria

[6:US12 Multi-Segment Description Retrieval]
The system processes US12 records with sequential counter from 1 to 46 → The system retrieves each existing US12 record's huge description data and stops when no more records are found or maximum 46 records are processed
[11:US12 Multi-Segment Description Management]
The system processes each of 46 possible US12 segments and evaluates record existence and input data meaningfulness → For each segment, the system deletes record if it exists and input data is empty, updates record if it exists and input data is meaningful, or creates new record if it doesn't exist but input data is meaningful
[Move Description to Output Segment]
The system processes the valid description → The system moves the US12 huge description content to the output description array at the current counter position
[Loop Through 46 Segments]
System begins US12 segment processing → System iterates through all segment numbers from 1 to 46 sequentially, processing each segment individually
[US12 Segment Exists?]
System processes individual US12 segment during replace operation → System retrieves US12 record using CCN key, record type 12, and current segment sequence number to check existence
[Delete US12 Segment]
Replace operation is performed with empty segment data → System deletes the existing US12 segment record
[Update US12 Segment]
Replace operation is performed with valid segment data → System updates US12 segment huge-description field with the replacement data for that specific segment
[Create New US12 Segment]
Replace operation is performed → System creates new US12 segment record with CCN key, record type 12, current segment sequence, and populates huge-description field with input segment data
[Segment Counter ≤ 46?]
The system checks whether to continue processing the next segment → Processing continues if segment counter is 46 or less AND more segments are available, otherwise processing stops
[Set Database Key with CCN and Segment Number]
The system prepares to access a US12 segment record → The database key is set with the customer control number, record type '12', and the current segment counter as the sequence number
[Access US12 Segment Record]
The system attempts to access the segment record from the database → The database operation is executed and the system receives a status indicating whether the record was found or not
[Clear Segment Content]
The segment record is being processed for deletion → All description content in the segment is cleared to spaces
[Delete Segment Record]
The segment record needs to be removed → The segment record is permanently deleted from the database
[Extract Segment Description Data]
The system processes the segment in retrieve mode → The description data is extracted from the segment record
[Store in Description Array]
The system stores the segment data for output → The description data is placed in the description array at the position corresponding to the current segment counter
[Delete Existing Segment]
The system processes the segment for replacement → The existing segment record is deleted from the database
[Update Segment with New Content]
The system processes the segment for replacement → The existing segment record is updated with the new input description content
[Create New Segment Record]
The system processes the segment for replacement → A new segment record is created with the customer control number, record type '12', current sequence number, and input description content
[Increment Segment Counter]
The system prepares to process the next segment → The segment counter is incremented by 1
[Record Found?]
A segment record is not found in the database → The more-segments flag is set to false to stop further processing
[Counter ≤ 46?]
The system checks if the current segment counter is less than or equal to 46 → Processing continues for the current segment if counter is 46 or less, otherwise processing terminates
[Setup US12 Segment Key with Counter]
The system sets up the segment key using CCN identifier, record type '12', and current counter as sequence number → The key is properly configured with CCN from input, type '12', and counter value for database access
[Attempt to Retrieve US12 Segment]
The system attempts to retrieve the segment using database get operation → The system returns success status if segment exists or failure status if segment does not exist
[Segment Exists?]
The system checks the operation status code → Segment is considered to exist if status code is spaces (success), otherwise segment does not exist
[Delete Empty US12 Segment]
The system processes the empty input content for the existing segment → The existing US12 segment is deleted from the database
[Update US12 Segment with New Content]
The system processes the meaningful input content for the existing segment → The existing US12 segment is updated with the new content from the input
[Create New US12 Segment with Content]
The system processes the meaningful input content for the non-existing segment position → A new US12 segment is created in the database with the CCN, type '12', sequence number, and input content
[Increment Counter]
The system needs to move to the next segment position in the sequence → The counter is incremented by 1 to process the next sequential US12 segment position

Structural Validations

[US12 Data Valid?]
System evaluates whether to create new US12 segment record → System creates record only if segment data is not all spaces, not all low-values, and not all underscores
[Segment Has Valid Content?]
If the segment content for meaningful data → The segment is considered valid if the description content is not all spaces, not all low-values, and not all underscores
[Input Segment Empty?]
If the input segment content → The input is considered empty if it contains all spaces, all low-values, or all underscores
[Input Segment Content Empty?]
If the input content equals all spaces, all low-values, or all underscores → Content is considered empty if it matches any of these patterns, otherwise it contains meaningful data
[Input Segment Has Content?]
If the corresponding input content != all spaces, all low-values, and all underscores → Content is considered meaningful if it contains data other than these empty patterns, otherwise no action is needed

As an EDI Gateway Service,
I want to orchestrate and execute all GCCSNOT3 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 Email Message Structure]
The system begins email message preparation → The communication structure is initialized, email text is cleared, car ID is stored in error context, and standard error message lines 1, 2, 4, and 5 are populated
[Initialize EMI-TEXT Array to Spaces]
The email message is being prepared → The car ID is stored in the error context field for reference

Core Acceptance Criteria

[5:Handle Configuration Lookup Failure]
The table lookup returns a non-zero status indicating failure → System clears the configuration segment and sets default notification recipient to 'OM01247'
[4:Retrieve Notification Configuration]
The table lookup returns zero status indicating success → System uses the retrieved table segment data for notification configuration
[8:Send Email Notification]
The system initiates email sending process → System calls email service to send the notification and receives a status flag indicating success or failure
[Email Structure Ready for Use]
Error message content needs to be loaded → Five predefined error message lines are loaded into the email text array
[Load Configuration Data from T3 Table]
The lookup returns successful status (return flag equals '0') → The retrieved table segment data is loaded into the notification configuration structure
[Use Retrieved Configuration Data]
The lookup operation returns successfully with return flag equal to '0' → The system uses the retrieved table segment data as the notification configuration
[Clear Configuration Segment]
The lookup operation fails with return flag not equal to '0' → The system clears the configuration segment by setting it to spaces
[Set Email Recipients - Assign notification user codes from configuration table to email recipient list]
The system needs to populate the email recipient list for duplicate manifest billing notification → The system assigns the first notification user code to recipient position 1, the second notification user code to recipient position 2, the third notification user code to recipient position 3, the fourth notification user code to recipient position 4, and the fifth notification user code to recipient position 5
[Execute Email Send Operation]
The email send operation is executed → The system dispatches the duplicate billing notification email to the configured recipients with the prepared subject and message content

Structural Validations

[3:Determine Country-Specific Error Message]
The system determines the error message content for line 3 → If country is CA, Canadian-specific error message is used; otherwise US-specific error message is used
[Set Car ID in Error Message]
The system builds an error message → The car ID must be included in the error message structure
[Add Standard Error Line 1, Add Standard Error Line 2, Add Standard Error Line 4, Add Standard Error Line 5]
The system adds standard error content → Standard error lines 1, 2, 4, and 5 must be populated with their respective predefined content
[Check Country Type, Add Canadian-Specific Error Line 3, Add US-Specific Error Line 3]
The system determines the content for error message line 3 → If the country code is 'CA', then Canadian-specific error line 3 content must be used, otherwise US-specific error line 3 content must be used
[Determine Country-Specific Error Message - Select appropriate error message text based on whether the car is Canadian (CA) or US]
The country code is 'CA' → The system selects the Canadian-specific error message text for line 3 of the notification
[Determine Country-Specific Error Message - Select appropriate error message text based on whether the car is Canadian (CA) or US]
The country code is not 'CA' → The system selects the US-specific error message text for line 3 of the notification

As an EDI Gateway Service,
I want to orchestrate and execute all GCX010 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 Status Arrays and Work Fields]
The system initializes work areas → All status arrays are initialized, message areas are cleared, error flags are reset, and trip message counter is set to zero
[Initialize US Status Array]
The system prepares for US data processing → The US status array is initialized, US trip message counter is reset to zeros, US Merlin counter is set to 1, and US Merlin message area is cleared to spaces
[Initialize N9 Segment]
The N9 segment is initialized with train reference data → The N9 segment should contain identifier 'N9', reference qualifier 'TG', customs train ID as reference number, arrival date, and arrival time
[Initialize First R4 Segment]
The first R4 segment is created for gateway function → The R4 segment should contain identifier 'R4', port function code 'G' for gateway, location qualifier 'CD' for city, and the Canadian station code as location identifier
[Initialize Second R4 Segment]
The second R4 segment is created for destination function → The R4 segment should contain identifier 'R4', port function code 'D' for destination, location qualifier 'CD' for city, and the same Canadian station code as location identifier
[Initialize A9RT Transmission Segment]
Transmission record needs to be created → A9RT transmission segment is initialized to clear any existing data
[Initialize Train Segment]
The train record creation process begins → The train segment data structure is cleared and initialized to spaces
[Initialize Train Segment]
A new train record needs to be created → The train segment should be initialized with blank/space values
[Initialize ST Segment Definition]
The ST segment needs to be created → Initialize ST segment definition, set sequence number to 00001, retrieve transmission number from table, set ST identifier, set destination code, and insert ST segment to EDI transmission
[Initialize B2A Segment Definition]
The B2A segment is being created → Initialize B2A segment definition, set B2A identifier, set transaction set purpose code to 00, set sequence number to 00002, and insert B2A segment to EDI transmission
[Initialize Message Index]
The system initializes message processing parameters → The message index is set to 1 to start processing from the first message element
[Initialize MST Message Index]
The system initializes message processing → The MST message index should be set to 1
[Initialize US Status Counter to 1]
System begins processing US status messages → System sets US status counter to 1 to start from first message

Core Acceptance Criteria

[1:Message Retrieval and Routing]
The message customer code is 'S' or 'V' → The message is routed to customs security processing (GCT1461E) with customs security text and message content
[4:Administrative Merlin ID Retrieval]
The system looks up the AD table with ADMINID sequence → Public Merlin ID and DC-P Merlin ID are retrieved from the administrative segment
[5:Location Terminal Merlin ID Retrieval]
The originating terminal is provided or defaults to '9999' if blank → Alternate terminal and supervisor Merlin ID are retrieved from the location terminal segment
[12:EDI Header Creation]
EDI header is created → N9 segment with customs train ID and arrival details, and R4 segments with location codes are generated
[15:EDI Header Writing]
Header writing is performed → Transmission record is created with transmission number and transaction set '311'
[16:EDI Transmission Number Management]
Transmission number is requested → Current transmission number is retrieved, incremented by 1, and updated in the system
[34:Train ID Conflict Resolution]
Train assignment conflict is detected → If same origin station or stations 3375/3377 (interchangeable), error 13 is generated; otherwise, movement is marked as US-CAN-US-CAN type
[43:EDI Transmission Finalization]
Transmission finalization is performed → ST segment with destination and B2A segment with purpose code '00' are added to complete transmission
[44:Application Type Setting]
Application type is determined → If train transit status is 'T' (in-transit), application type is set to '29'; otherwise, application type is set to '27'
[45:Confirmation Message Sending]
Confirmation is sent → Confirmation message includes customs train ID, originating terminal, user ID, and is sent unless trip sheet only mode is active
[Start Message Processing Loop]
The message processing loop is initiated → The system should continue retrieving and processing messages until the return code indicates no more messages are available
[Read Input Message from Queue]
The READQ service is called with communication control block and message parameters → The system should retrieve the next available message and populate the input message structure
[Check Message Type]
The message customer code is evaluated → If customer code equals 'S' or 'V', classify as customs security message; otherwise, classify as regular train message
[Extract Customs Security Data]
The customs security data extraction is performed → The system should clear the first message field, concatenate customs security text with message text into the first field, and move the second message text to the second field
[Route to GCT1461E Spawn Process]
The message routing decision is made for customs security messages → The system should invoke the Z700-SPAWN-GCT1461E process to handle the customs security message
[Route to Train Processing]
The message routing decision is made for train messages → The system should proceed with initialization, input validation, train report generation, and conclusion processing
[Continue Message Loop]
The message processing is completed → The system should return to the beginning of the message processing loop to check for additional messages
[Exit Message Processing]
The loop termination condition is evaluated → The system should exit the message processing loop, restore the original program name, call the commit routine, and terminate the program
[Extract Input Message Text]
The system processes the message → The message text is extracted and stored in the working storage area for further validation
[Execute Table Segment I/O]
The table segment I/O operation is executed → The system attempts to retrieve the administrative record from the GCSTBRT table
[Extract Public Merlin ID]
Public Merlin ID needs to be extracted → The public Merlin ID is copied from the administrative segment to the working storage variable
[Extract DC-P Merlin ID]
DC-P Merlin ID needs to be extracted → The DC-P Merlin ID is copied from the administrative segment to the working storage variable
[Execute Table Segment Search]
The table segment search is executed → The system attempts to retrieve the location terminal data from the database
[Extract LT Segment Data]
The retrieved data needs to be processed → The table segment data is moved to the location terminal segment structure
[Get Supervisor Merlin ID]
Supervisor communication configuration is needed → The supervisor Merlin ID is extracted from the LT segment and stored for validation
[Get Alternate Terminal ID]
Alternate communication path configuration is processed → The alternate terminal ID is extracted from the LT segment for potential use
[Extract Train ID Number from Input]
The system processes the train identification components → The train ID number is extracted from the input header and assigned to the CP train ID number field
[Extract Train ID Day from Input]
The system processes the train identification components → The train ID day is extracted from the input header and assigned to the CP train ID day field
[Extract From Station from Input]
The system processes the train identification components → The from station code is extracted from the input header and assigned to the CP train ID from station field
[Extract To Station from Input]
The system processes the train identification components → The to station code is extracted from the input header and assigned to the CP train ID to station field
[Extract Consist Number from Input]
The system processes the train identification components → The consist number is extracted from the input header and assigned to the CP train ID consist number field
[Extract Train ID Number from Input]
The system processes the input to generate a status report header → The train ID number is extracted from the customs train ID and assigned to the status report
[Extract Train ID Day from Input]
The system processes the input to generate a status report header → The train ID day is extracted from the customs train ID and assigned to the status report
[Extract From Station from Input]
The system processes the input to generate a status report header → The from station code is extracted from the customs train ID and assigned to the status report
[Extract To Station from Input]
The system processes the input to generate a status report header → The to station code is extracted from the input header and assigned to the status report
[Extract Consist Number from Input]
The system processes the input to generate a status report header → The consist number is extracted from the customs train ID and assigned to the status report
[Build Status Report Line 1 with Train Details]
The system builds the status report header → The first report line is populated with train ID number, day, from station, to station, and consist number
[Store N9 Segment in EDI Table Position 1]
The segment is stored in the EDI transmission table → The segment should be assigned sequence number 3 and placed in position 1 of the EDI data table
[Store First R4 Segment in EDI Table Position 2]
The segment is stored in the EDI transmission table → The segment should be assigned sequence number 4 and placed in position 2 of the EDI data table
[Store Second R4 Segment in EDI Table Position 3]
The segment is stored in the EDI transmission table → The segment should be assigned sequence number 5 and placed in position 3 of the EDI data table
[Get EDI Transmission Number]
A transmission number is required for the EDI transmission → The system should retrieve the current transmission number from table '10', increment it by 1, and update the table with the new value
[Write EDI Header to Transmission]
The EDI header is written to the transmission system → A transmission record should be created with the transmission number and transaction set '311', and all header segments should be sent to the EDI system
[Set Next EDI Sequence Number to 6]
The EDI header creation process is completed → The next available EDI sequence number should be set to 6 for any additional segments
[Search Station Code Table SC]
The system searches the station code table with table ID 'SC' and the from station as sequence ID → The station segment data is retrieved if the station exists in the table
[Set Transmission Number from Table]
Transmission number needs to be assigned → Transmission number is retrieved from GCSTBRT table and assigned to A9RT-TRANSMISSION-NUMBER
[Set Transaction Set to '311']
Transaction set type needs to be defined → A9RT-TRANSACTION-SET is set to '311' to indicate customs manifest transaction type
[Insert A9RT Transmission Record]
Transmission record needs to be persisted → A9RT transmission record is inserted into the database via Z013-ISRT-GCA9RT
[Set EDI Index to 1]
EDI data processing needs to begin → WS-EDI-IDX is set to 1 to start processing from first EDI data element
[Send EDI Header Data]
EDI header data needs to be transmitted → X400-SEND-EDI procedure is performed to transmit the header data
[Set Next EDI Sequence to 6]
System needs to prepare for next EDI segments → WS-EDI-SEQ is set to 6 to continue sequence numbering for additional EDI segments
[Retrieve Current Transmission Number from Table 10]
The system attempts to retrieve the current transmission number from table 10 with table ID '10' and sequence ID ' ' → The current transmission number is successfully retrieved from GCSTBRT-10-TRANSMISSION-NUM field
[Increment Transmission Number by 1]
The system needs to generate the next transmission number → The system adds 1 to GCSTBRT-10-TRANSMISSION-NUM to create the next sequential number
[Update Transmission Number in Table 10]
The system performs a replace operation on table 10 with table ID '10' and sequence ID ' ' → The updated transmission number is stored back in the GCSTBRT-10-SEGMENT
[Set Sent Information]
Setting transmission audit trail information → Record the current machine date, converted machine time, originating terminal, and user ID in the sent fields
[Set Estimated Arrival Information]
Creating a train record → The estimated arrival date and time should be stored in the train record
[Set Sent Timestamps]
Setting sent status audit information → The sent date, time, terminal, and user ID should be recorded from current system values
[Set Current Status to SENT]
Setting the current status → The current status should be set to SENT
[Access FWCIROOT Segment]
The system accesses the FWCIROOT segment → The waybill data is retrieved and made available for processing
[Access FWIIROOT Segment]
The system accesses the FWIIROOT segment → The intermodal waybill data is retrieved and made available for date comparison
[Perform Y2K Date Conversion on FWCI Date]
The system performs Y2K date conversion on the FWCI date → If the year is less than 70, the century is set to 20 (20xx), otherwise the century is set to 19 (19xx)
[Perform Y2K Date Conversion on FWII Date]
The system performs Y2K date conversion on the FWII date → If the year is less than 70, the century is set to 20 (20xx), otherwise the century is set to 19 (19xx)
[Compare Full Dates]
The system compares the full dates from both waybill segments → If FWCI date is greater than FWII date, equipment is processed as box car; if FWCI date is less than FWII date, equipment is processed as flat car; if dates are equal, intermodal indicator determines processing type
[Access FWCIROOT Segment]
The system accesses the FWCI database segment → The waybill data is retrieved and made available for processing
[Access FWIIROOT Segment]
The system accesses the FWII database segment → The intermodal waybill data is retrieved and made available for processing
[Extract FWCI Waybill Date]
The system processes the FWCI waybill data → The waybill date is extracted from FWCI segment and stored for comparison
[Extract FWII Waybill Date]
The system processes the FWII waybill data → The waybill date is extracted from FWII segment and stored for comparison
[Intermodal Indicator = 'I'?]
The intermodal indicator in FWII segment equals 'I' → Equipment is classified for flat car processing, otherwise classified for box car processing
[Set Waybill Not Found Flag]
No waybill data is found in either FWCI or FWII segments → The waybill not found flag is set and equipment proceeds to no-waybill processing logic
[Operation Type?]
The system checks the operation type → If operation is ADD, the system builds equipment record, adds to trip sheet and EDI transmission; If operation is VERIFY, the system generates status report and loads into Merlin system
[Add Equipment to EDI Transmission]
The system prepares EDI transmission → Equipment data is formatted and included in the EDI transmission
[Check US Origin and Destination Cargo]
USRT record is not found (USRT-FOUND flag is 'N') → The system adds US warning message 6 to the status array and increments the status counter
[Process US Status Array Messages]
Processing US status messages → The system moves each status line to the report, increments report index and status counter until all messages are processed
[Clear US Status Array]
US status message processing is complete → The system clears the US status array by moving spaces to it
[Add US Warning Message to Status Array]
The system validates US cargo requirements → US warning message 6 is added to the status array and US status counter is incremented
[Generate US Warning Message]
The system processes the cargo for US reporting requirements → A US warning message (US-WARN-MESSAGE6) is added to the status array and the status count is incremented
[Generate US Report Output]
The system processes US reporting requirements → Generate US report output and load US Merlin message
[Add Status Messages to Report Lines]
The system completes US status processing → Add each non-blank status array line to report lines, increment report index, and clear the status array
[Train ID Conflict Exists?]
System checks for train assignment conflicts → If CCN train origin matches current train origin (including 3375/3377 interchange), generate error 13, otherwise mark as cross-border movement
[Add to EDI Transmission]
System generates EDI transmission → Equipment information is formatted and added to EDI transmission data
[Add to EDI Transmission]
System prepares EDI transmission → Equipment details are added to EDI transmission data
[Process Equipment with Cross-Border Flag]
The system processes the equipment for train documentation → Build equipment record, add to trip sheet with 'US-CA-US-CA' designation, and include in EDI transmission
[Process Equipment Normally]
The system processes the equipment for train assignment → Update CCN record with current train information, build equipment record, add to trip sheet, and include in EDI transmission
[Check Special Station Pairs]
The stations are 3375 and 3377 in either direction (3375 to 3377 or 3377 to 3375) → The system allows the cross-border movement as these stations are interchangeable
[Process Equipment Normally]
The system processes the equipment for train assignment → The system continues with normal equipment processing including trip sheet addition and EDI processing
[Update Cross-Border Flag]
The CCN is being assigned to a train from a different origin station (not same or 3375/3377 interchange) → The system should set the US-CAN-US-CAN flag to 'Y' indicating cross-border movement
[Process CCN Successfully]
The CCN has no existing train assignment or passes conflict checks → The system should update the CCN with new CP train ID information and process for trip sheet and EDI
[Update CCN with Train ID]
Processing ADD operation and CCN has no existing CP train ID → Update CCN record with current train information and process for trip sheet and EDI
[Set Cross-Border Flag]
The CCN CP train ID from station is different from current train from station AND not interchangeable stations → The US-CAN-US-CAN flag is set to 'Y' indicating cross-border movement
[Add to EDI Equipment Segment]
The container has valid CCN information → An EDI equipment segment is generated for electronic customs transmission
[Add to EDI Transmission]
This is an ADD operation → The container information should be added to the EDI transmission for electronic customs reporting
[Set CCN Message: 'CCN REPORTED AS INTERMODAL']
The conveying car field is not empty → The system should set the CCN message to 'CCN REPORTED AS INTERMODAL' and add it to the status report
[Set CCN Message: 'CCN REPORTED AS CARLOAD']
The conveying car field is empty → The system should set the CCN message to 'CCN REPORTED AS CARLOAD' and add it to the status report
[Check CP Train ID Conflict]
The system checks for train ID conflicts → If the CCN train origin station matches current train origin station or stations 3375/3377 are interchangeable, generate error 13; otherwise mark as cross-border US-CAN-US movement
[Add to EDI Transmission]
The system adds equipment to EDI transmission → The system should include equipment and CCN information in the electronic data interchange transmission for customs authorities
[ADD Operation]
The equipment is classified as empty, idler, or exempted → Build equipment record, add to trip sheet report, and add to EDI equipment segment
[Generate Output Report]
Processing empty or exempted equipment → Generate output report and load Merlin message
[Check Input Operation Type]
If the input message type flags → The operation is classified as ADD, VERIFY, US, or Invalid based on the presence of specific input flags
[Execute ADD Processing Path]
The system routes to processing paths → Execute EDI header creation, trip sheet header generation, train record creation, CCN record updates, trip sheet reports, and confirmation messages
[Route to EDI Header Creation]
EDI processing is initiated → Create N9 segment with customs train ID and arrival information, create R4 segments for station codes, and generate transmission number
[Send to Supervisor]
The supervisor Merlin ID is found and marked as valid ('Y') → The system sends the error message to the supervisor Merlin ID as the primary recipient
[Send to DC-P]
The DC-P Merlin ID is found and marked as valid ('Y') → The system sends the error message to the DC-P Merlin ID as the secondary recipient
[Send to Customs Default]
Error message delivery is required → The system sends the error message to the default customs ID as the final fallback recipient
[Train Transit Status?]
The train transit status is evaluated → If train transit status equals 'T' then set application type to 29 for in-transit, otherwise set application type to 27 for non-transit
[Check Train Transit Status]
If the train transit status to set the B2A application type → If the train transit status equals 'T' (in-transit), then the application type is set to '29', otherwise the application type is set to '27'
[Build Confirmation Message Line 1]
The system builds the confirmation message header → The customs train ID is inserted into the first line of the confirmation message template
[Build Confirmation Message Line 2]
The system builds the confirmation message user context line → The originating terminal ID and user ID are inserted into the second line of the confirmation message template
[Set Message Type as Confirmation]
The system prepares the message for transmission → The message type is set to confirmation and the header literal is set to confirmation header
[Send Message to MST System]
If whether to transmit the confirmation message → If US trip sheet only flag is not 'Y', the message is sent to the MST system, otherwise message transmission is skipped
[Add End of Report Message]
Finalizing the trip sheet report → Add the message ' *** END OF REPORT *** ' to the report at the current report index position
[Set Report Text to EMI-TEXT]
Preparing to send the trip sheet report → Move the complete report content (TB-RPT-MESSAGE) to the transmission text field (EMI-TEXT)
[Set Trip Sheet Header Literal]
Setting up message headers → Assign the trip sheet header literal (CST-LIT-TRIP-HDR) to the message subject field (EMI-SUB-LIT)
[Send Report via Merlin System]
Executing the report transmission → Invoke the Merlin messaging system (X300-SEND-MERLIN) to deliver the trip sheet report
[Set Status Report Message Type]
The system needs to configure the message type → The message type should be set to status report constant
[Set Status Report Header Literal]
The system configures the message header → The header literal should be set to the status report header constant
[Send Status Report to MST System]
The system sends the status report → The status report should be transmitted to the MST system using the configured message type and header
[Set US-Only Processing Mode]
The system processes the train request → The system should activate US-only processing mode and skip standard MST system messages
[Skip MST System Messages]
The system would normally send MST system messages → The system should skip MST message generation and proceed with US-only processing
[Route to Standard Processing]
The system processes the train request → The system should route to standard processing and send messages to both MST and Merlin systems
[US Status Array Has Data?]
The system checks the US-STATUS-ARRAY for data → The system should determine if US warning messages need to be added to the output
[Add US Warning Messages]
The system processes US status messages → The system should add the US warning messages to the report output
[Route US Messages to Merlin Only]
The system routes the messages → The system should send US messages only to Merlin system and not to other messaging systems
[Send End of Report Message]
The system finalizes US processing → The system should generate an 'END OF REPORT' message for US processing completion
[US Message Count > 1?]
The system checks US-MERLIN-CNT counter → The system should determine if the message count is greater than 1 to decide on counter reset
[Reset Message Counter]
The system processes US message counter management → The system should reset US-MERLIN-CNT to 1 and increment US-TRIP-MSG-CNT by 1
[Send US Merlin Message]
The system is ready to send the US Merlin message → The system should Execute the US Merlin message transmission
[Supervisor Merlin ID Available?]
The system checks for available Merlin IDs in priority order (Supervisor first, then DC-P, then Customs as default) → The error message is sent to the first available valid Merlin ID in the hierarchy
[US Trip Sheet Only?]
The system checks if processing is in US trip sheet only mode → If not in US trip sheet only mode, error messages are also sent to MST system; otherwise MST distribution is skipped
[Is Supervisor Available?]
The supervisor Merlin ID is found and validated as available → The error message should be routed to the supervisor Merlin ID
[Is DC&P Available?]
The DC&P Merlin ID is found and validated as available → The error message should be routed to the DC&P Merlin ID
[Add Customs Train ID]
The customs train ID information is added to the error message → The system includes the formatted customs train ID in error header line 2
[Add Terminal and User Information]
Audit information is added to the error message → The system includes the originating terminal ID and user ID in error header line 3
[Add CCN Key and Equipment ID]
The error message is being formatted → The system includes the CCN key in the error message, adds the error line to the error table, increments the error index, and sets the next error number to 27
[Extract Train ID from Input]
The system needs to create an error message header → The train ID from the input header should be extracted and placed in the first line of the error message
[Extract From Station from Input]
The system extracts station information from the input → The from station code from the input header should be included in the error message line 1
[Extract To Station from Input]
The system extracts destination information from the input → The to station code from the input header should be included in the error message line 1
[Extract Consist Number from Input]
The system extracts consist information from the input → The consist number from the input header should be included in the error message line 1
[Car Status Flags?]
Empty car flag is set to 'Y' → Display 'EMPTY CAR - NO WAYBILL' message, clear asterisk field, set description to 'N/R', clear bond field, and set load/empty status to 'E'
[Process US Status Array]
US status array contains messages → Process each US status message and add to report until all messages processed or maximum count reached
[US Status Messages?]
The system checks if US status array contains messages → If US status array is not blank, process each message line until all messages are processed or maximum count reached, then clear the status array
[US Status Array Contains Messages?]
System checks if US status array contains any messages → System proceeds to process messages if array is not empty, otherwise skips processing
[Get Current US Status Message from Array]
System needs to process current US status message → System retrieves the message at the current counter position from US status array
[Add US Status Message to Report Line]
System processes the US status message → System adds the US status message to report line at current report index position
[Increment Report Index]
System completes adding message to report → System increments report index by 1 to point to next available report line
[Increment US Status Counter]
System completes processing current message → System increments US status counter by 1 to point to next message in array
[More Messages in Array?]
System checks for more messages to process → System continues processing if US status array line at current counter position is not empty
[Clear US Status Array]
System completes US status message processing → System clears US status array by moving spaces to it
[Include GCX0101 Module]
The X003-ADD-EDI-EQUIP section is executed → The GCX0101 module must be included and executed to handle EDI equipment segment creation
[Calculate MAX-SUB-CAR-ID]
The system processes multiple carload shipments → The maximum sub-car ID is set to the equipment sequence number plus one
[Both Origin and Destination US?]
The system processes the cargo classification → The system adds a warning message to the status array indicating missing US reporting requirements
[Invalid Status Found]
The system processes the CCN during train manifest verification → The system sets CCN waybill error flag to 'Y', sets CCN message to 'NO CCN FOUND FOR THIS CAR', and adds the record to status report
[Is Status = 'T'?]
The in-transit status equals 'T' (Transit) → The CCN is flagged for US processing and Merlin message loading
[Load Merlin Message]
The system processes transit status CCNs → Merlin message loading routine is performed for communication purposes
[Set EDI Application Type to '29' for In-Transit]
The system generates EDI transmission data → EDI application type is set to '29' for in-transit processing
[Set EDI Application Type to '27' for Non-Transit]
The system generates EDI transmission data → EDI application type is set to '27' for standard processing
[Train ID Conflict Detected]
The system detects this conflict condition → Generate error code 13 with equipment car ID, CCN key, conflicting train ID number, and conflicting train day populated in error message
[Generate US Report Output]
The system processes the cargo for reporting → Execute report output generation (0000-OUT-REPORT) and load messages to Merlin system (0000-LOAD-MERLIN)
[Process US Status Array Messages]
The system processes status report generation → For each non-empty message line in the US status array (up to 90 lines), move the message to the report line at current report index, increment report index by 1, and increment status counter by 1, then clear the US status array
[Add US Warning Message 6 to Array]
The system processes US cargo classification → US warning message 6 is added to the US status array line at the current counter position and the US status counter is incremented by 1
[Move US Status Array Line to Report]
The system processes US status messages for reporting → Each US status array line at the current counter position is moved to the report line at the current report index, both the report index and US status counter are incremented by 1, and processing continues until the US status array line is empty or the counter exceeds 90
[Clear US Status Array]
US status array processing is complete → The US status array is cleared to spaces
[Check Train ID Station Compatibility]
The CCN record has a CP Train ID that is not spaces → The system should check if the CP Train ID from station matches the current train's from station or if stations 3375 and 3377 are interchangeable
[Set US-CAN Flag to 'Y']
The CCN from station does not match the current train from station and is not a 3375/3377 interchange → The US-CAN flag should be set to 'Y' to indicate cross-border movement
[Process Equipment with Cross-Border Flag]
The equipment processing continues for ADD operations → The system should build GCTNDP record, add to trip sheet, and add to EDI equipment with cross-border status
[Update CCN Record with Train Info]
ADD operation is being performed → The system should replace the CCN record with current train information, build GCTNDP record, add to trip sheet, and add to EDI equipment
[Set EDI Application Type to '29' for In-Transit]
The final train transit status is 'T' (In-Transit) → The EDI application type should be set to '29'
[Set EDI Application Type to '27' for Non-Transit]
The final train transit status is not 'T' (Not In-Transit) → The EDI application type should be set to '27'
[Check Train Transit Status]
If the train transit status to determine the appropriate application type code → If the train transit status equals 'T' (in-transit), the application type is set to '29', otherwise the application type is set to '27' for non-transit movements
[Set Application Type = '29' In-Transit]
The train transit status equals 'T' → The B2A EDI segment application type field is set to '29' to indicate in-transit movement
[Set Application Type = '27' Non-Transit]
The train transit status does not equal 'T' → The B2A EDI segment application type field is set to '27' to indicate non-transit movement
[Send Confirmation to MST]
The US Trip Sheet Only flag is not set to 'Y' → The system sends a confirmation message to the MST system with train details and user information
[Skip MST Confirmation]
The US Trip Sheet Only flag is set to 'Y' → The system skips sending confirmation message to MST system
[Send Status Report to MST]
The US Trip Sheet Only flag is not set to 'Y' → The system sends a status report message to the MST system
[Add to EDI Transmission]
The system processes EDI transmission requirements → Equipment data is formatted according to EDI standards and added to electronic transmission queue
[Process US Status Messages]
Status report line has been built → Each US status message is processed and added to the report, then the US status array is cleared

Structural Validations

[41:Error Rollback Processing]
Error rollback is triggered → All database changes are rolled back, error messages are prepared, and normal processing is terminated
[49:Error Message Distribution]
Error distribution is performed → Error messages are sent to supervisor ID if valid, otherwise to DC-P ID if valid, otherwise to customs ID, with error header and details
[Message Retrieved Successfully?]
The communication control block return code is evaluated → If return code equals zero, message retrieval was successful; otherwise, no message was retrieved
[Check Operation Type]
The system validates the operation type → If the operation is not ADD, VERIFY, or US, the invalid input flag is set to YES
[Set Error Flag - Cannot Retrieve Number]
The retrieval operation fails and GCCTBIO-RETURN-FLAG is not SUCCESSFUL → The system sets rollback flag to 'Y', sets error number to 15, and processes the error condition
[Set Error Flag - Cannot Update Number]
The update operation fails and GCCTBIO-RETURN-FLAG is not SUCCESSFUL → The system sets rollback flag to 'Y', sets error number to 16, and processes the error condition
[Transmission Number Ready for Use]
Both retrieval and update operations complete successfully → The GCSTBRT-10-TRANSMISSION-NUM is available for creating new EDI transmission records
[Equipment at Position 181?]
Equipment is found at consist position 181 → The system should reject the train as exceeding maximum length and set error code 28
[Waybill Found?]
The system checks if waybill data was found in either FWCI or FWII segments → The waybill found flag is set to YES if data exists, otherwise set to NO
[Add US Warning Message to Status Array]
No US route table record is found for the cargo → US warning message 6 is added to the status array and US status counter is incremented
[Add US Warning Message]
No US reporting records are found for the cargo → A US warning message is added to the status array for reporting
[Both Origin and Destination US?]
The system validates US cargo reporting requirements → Add US warning message to status array indicating missing US reporting
[US Status Records Found?]
US status records are searched and USRT-FOUND flag equals 'N' and WS-NINES-WB-IDX-FOUND is not 'Y' → Add US warning message 6 to the status array and increment status count by 1
[Add US Warning Message 6 to Status Array]
The system validates US reporting requirements → Add US warning message 6 to the status array and increment the status counter
[Check CP Train ID Conflicts]
CCN CP Train ID from station equals current train from station:
stations are 3375 and 3377 (interchangeable)
→ System generates error code 13 for duplicate train assignment conflict
[Set CCN WB Error Flag = Y]
The CCN current status is not ERROR, REJECT, SENT, RETURN, MANUAL, or RELEASE → Set CCN waybill error flag to Y and add 'NO CCN FOUND FOR THIS CAR' message to status report
[Generate Train ID Conflict Error]
The system detects a station match or 3375/3377 special case during ADD operation → Set rollback flag, assign error number 13, populate error message with equipment ID, CCN key, existing train ID number and day, and process the error
[Generate Train ID Conflict Error]
The stations are not the same and not the special interchangeable pair 3375/3377 → The system generates error code 13 with equipment details including car ID, CCN, existing train ID and day
[Set Train ID Conflict Error]
Attempting to assign the same CCN to the current train → Set rollback flag to true, set error number to 13, populate error message with car ID, CCN, existing train ID and day, and trigger error processing
[CP Train ID Conflict Check]
The CCN is being assigned to a different train from the same origin station:
stations 3375 and 3377 (which are interchangeable)
→ The system should generate error code 13 with car ID, CCN, and existing train information
[Check Train ID Conflict]
The existing train from station matches current train from station:
stations 3375 and 3377 are interchangeable
→ Generate error code 13 with car ID, CCN, existing train ID and day information
[Set CCN WB Error Flag]
Processing a VERIFY operation → Set CCN WB error flag to Y, set CCN message to 'NO CCN FOUND FOR THIS CAR', and add to status report
[Set CCN WB Error Flag = Y]
The current status is not SENT, RETURN, MANUAL, RELEASE, ERROR, or REJECT → Set CCN WB error flag to Y, set CCN message to 'NO CCN FOUND FOR THIS CAR', and add to status report
[Invalid/Unknown Status, Generate Error Message - Invalid CCN Status, Set Rollback Flag]
The system processes the CCN status validation → The system generates error message 24 for invalid CCN status, sets rollback flag to YES, and terminates processing
[Compare From Station with Current Train]
The from station of existing train equals current train's from station:
the stations are the special interchange pair 3375 and 3377
→ Identify this as a train ID conflict requiring error handling
[Set Train ID Conflict Error]
The system detects a train ID conflict during ADD operation → Set rollback flag, generate error code 13 with equipment car ID, CCN key, existing train ID number and day, and stop processing
[Check CP Train ID Conflicts]
The CCN CP train ID is not empty AND the CCN CP train ID from station equals the current train from station:
the stations are interchangeable (3375 and 3377)
→ The system generates error code 13 with car ID, CCN, train ID, and train day information
[Check CP Train ID Conflict]
The CCN CP train ID is NOT empty AND this is an ADD operation AND the CCN CP train ID from-station does NOT match the current train from-station AND the stations are NOT the interchangeable pair 3375/3377 → The system should generate error 13 with car ID, CCN key, train ID number, and train day
[Flag as Carload Error]
The system detects this configuration error → Set error flag and prepare error message indicating the CCN is reported as carload when it should be intermodal
[Send Error Message]
The system processes the error condition → Generate error code 33, set rollback flag, populate error message with equipment details, and terminate container processing
[Generate Error Message: CCN REPORTED AS CARLOAD]
The conveying car validation fails → The system should set CCN message to 'CCN REPORTED AS CARLOAD' and add it to the status report
[Validate Train Station Compatibility]
The system attempts to assign the CCN to the current train during ADD operation → The system generates error 13 with CCN details and sets rollback flag to prevent duplicate assignment
[Invalid Operation Type]
The input is not ADD operation AND not VERIFY operation AND not US operation → The invalid input flag is set to YES and processing is terminated
[Build Error Message Header]
Error processing begins → The system builds an error message header containing train ID, from station, to station, consist number, customs train ID, terminal, and user ID information
[Add Equipment-Specific Error Information]
The error message is being formatted → The system adds the relevant equipment ID, CCN number, ETA date, or container information to the error message based on the specific error type
[Send Error to Merlin System]
Error message transmission is initiated → The system sends the error message through the Merlin system with error header literal and formatted error text
[Send Error to MST System]
MST error message transmission is initiated → The system sends the error message to MST system with error message type and error header literal
[Build Error Header with Train Details]
The system builds the error message header → The header includes train ID, from station, to station, consist number, customs train ID, terminal, and user ID
[Add Equipment and CCN Error Details]
The system processes error details for equipment numbers 8-13, 20-24, or specific CCN errors (24-27, 32-33) → The equipment ID is added to the error message for equipment-related errors, and specific CCN or date information is included for CCN-related errors
[Send Error Message to Merlin]
The system sends the error message to Merlin system → The error message is transmitted to the selected recipient (Supervisor, DC-P, or Customs) via Merlin system with error header literal
[Send Error Message to MST System]
The system sends error message to MST system → The error message is transmitted to MST system with error message type and error header literal for MST
[Route Error to Customs]
The error routing process reaches the default fallback option → The error message should be routed to the customs Merlin ID
[Send Error via Merlin System]
The error message is ready to be transmitted → The error message should be sent via the Merlin messaging system to the designated recipient
[Send Error via MST System]
The MST error message transmission is required → The error message should also be sent via the MST system
[Build Error Header with Train Details]
The error header construction process is initiated → The system builds error header line 1 with train ID, from station, to station, and consist number from the input message
[Set Error Index to 4]
The system prepares to add specific error details → The error message index is set to 4 to position for the next error line
[Add Equipment ID to Error Message]
The error message is being formatted → The system includes the equipment ID in the error message template for the specific error number
[Add Equipment ID for Intermodal Error]
The error message is being formatted → The system includes the equipment ID in the intermodal error message template
[Add Equipment and Container IDs]
The error message is being formatted → The system includes both the equipment ID and the container equipment ID in the error message
[Add CCN Key to Error Message]
The error message is being formatted → The system includes the CCN key in the error message template
[Add ETA Date to Error Message]
The error message is being formatted → The system includes the input ETA date in the error message template
[Add Equipment ID to Error Message]
The error message is being formatted → The system includes the equipment ID in the error message template
[Format Complete Error Message Line]
The error message formatting is completed → The system formats the complete error message line using the error message template for the specific error number
[Add Error Line to Error Table]
The error message is ready for storage → The system stores the formatted error message in the error table at the current error index position and increments the error index for the next error
[Build Error Message Line 1 with Train Details]
The system constructs the first line of the error message → The error message line 1 should be formatted with train ID, from station, to station, and consist number in the predefined error message template
[Build Error Message Line 2 with Customs Train ID]
The system constructs the second line of the error message → The error message line 2 should be formatted with the customs train ID in the predefined error message template
[Build Error Message Line 3 with Terminal and User Details]
The system constructs the third line of the error message → The error message line 3 should be formatted with terminal ID and user ID in the predefined error message template
[Set Error Index to Line 4 for Subsequent Error Details]
The system completes the error header creation → The error index should be set to 4 to indicate the next available line for adding specific error detail messages
[Add Equipment ID to Error Message]
The system processes the error message → The equipment ID is added to the corresponding error message template
[Add Equipment ID to Intermodal Error]
The system processes the intermodal error message → The equipment ID is added to the intermodal error message template
[Add Equipment and Container IDs to Error]
The system processes the container error message → Both the equipment ID and the container equipment car ID are added to the error message template
[Add CCN to Error Message]
The system processes the CCN status error message → The CCN key is added to the error message template
[Add ETA Date to Error Message]
The system processes the ETA validation error message → The input ETA date is added to the error message template
[Add CCN to Manual/Release Error]
The system processes the manual/release error message → The CCN key is added to the error message, the message is added to the error table, the error index is incremented, and the error number is set to 27 for additional processing
[Add Car ID to Error Message]
The system processes the equipment error message → The equipment ID is added to the error message template as the car ID
[Add Error Message to Error Table]
The system completes error message preparation → The formatted error message is added to the error table at the current error index position
[Increment Error Index]
The system completes the error message addition → The error index is incremented by 1 to point to the next available position in the error table
[Counter Exceeds Maximum?]
System validates counter bounds → System stops processing if US status counter exceeds 90, otherwise continues processing
[Check GCCC-CONVEYING-CAR Field]
The conveying car field contains data indicating intermodal processing → The system should reject the CCN for carload processing and generate appropriate error or status message based on operation type
[Record Error: CCN Reported as Intermodal]
The CCN record contains conveying car information → The system should set CCN message to 'CCN REPORTED AS INTERMODAL' and add to status report
[Is Conveying Car Empty?]
The conveying car field is empty or contains spaces → The system should reject the CCN for container processing and generate appropriate error or status message based on operation type
[Record Error: CCN Reported as Carload]
The CCN record has empty conveying car information → The system should set CCN message to 'CCN REPORTED AS CARLOAD' and add to status report
[Add US Warning Message to Array]
The system validates US status requirements → Add US warning message 6 to the status array at current counter position and increment the US status counter by 1
[Set Cross-Border Flag Error]
The current train is from the same station or a compatible station (3375/3377 interchange) → The system should set rollback flag to yes, set error number to 13, populate error message fields with car ID, CCN key, train ID number and train day, and Execute error processing
[Send Error to Supervisor Merlin]
The Supervisor Merlin ID is found and valid → The system sends error messages to the Supervisor Merlin ID
[Send Error to DC-P Merlin]
The Supervisor Merlin ID is not found or invalid AND the DC-P Merlin ID is found and valid → The system sends error messages to the DC-P Merlin ID
[Send Error to Customs Merlin]
Both Supervisor Merlin ID and DC-P Merlin ID are not found or invalid → The system sends error messages to the Customs Merlin ID
[Send Error to MST System]
Error distribution to Merlin is complete → The system sends error messages to the MST system
[Skip MST Error Message]
The US Trip Sheet Only flag is set to 'Y' → The system skips sending error messages to MST system
[Process Error for Invalid CCN]
The system processes invalid CCN error → Appropriate error message is generated, rollback flag is set, and processing continues to next CCN record
[Error Number 9-12?, Error Number 21-23?]
Building the error message line → The equipment ID must be added to the error message template for that specific error number
[Error Number 32?, Error Number 27?]
Building the error message line → The equipment ID must be moved to the car ID field in the error message template
[Error Number 33?]
Building the error message line → The equipment ID must be moved to the car ID field and the CCN equipment car information must be moved to the container field in the error message template
[Error Number 24?]
Building the error message line → The CCN key must be moved to the CCN field in the error message template
[Error Number 25?]
Building the error message line → The input header estimated arrival date must be moved to the ETA field in the error message template
[Error Number 26?]
Building the error message line → The CCN key must be moved to the error message template, the error line must be added to the error table with incremented index, and error number 27 must be set for additional processing
[Move Error Message Template to Error Line]
Finalizing the error message line → The completed error message template must be moved to the error line table at the current error index position
[Increment Error Line Index]
Completing the error message line processing → The error line index must be incremented by 1 to point to the next available error line position

As an EDI Gateway Service,
I want to orchestrate and execute all GCX101 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 New US Manifest Structure]
Preparing to create new manifest record → The system should initialize all manifest segments and clear status fields to prepare for new data
[Initialize GCX111 Message Fields]
The system begins detour processing → The system clears the GCX111 message fields, sets high-values to filler, sets DOM-DETOUR action flag, and sets BACKGROUND environment flag
[Initialize Audit Message]
The system needs to create an audit trail for the invalid broker condition → The system initializes the audit message structure (GCX105-INPUT) to prepare for error logging
[Initialize Empty Broker Segment]
No broker information is found in the broker table → The system initializes empty broker and B1 segments to prevent processing errors
[Initialize GCX108 Input for Next Use]
The message processing is complete → The GCX108 input structure is initialized to clear previous data for next use
[Initialize Queue Status]
Queue status is being initialized → The accept status is set to spaces to clear any previous status
[Initialize GCX108 Input Structure]
The message preparation process begins → The GCX108 input structure should be initialized to clear any previous data
[Initialize Queue Management]
Queue management initialization is requested → Accept status is set to blank spaces to clear any previous status
[Initialize SCAC Codes Across Segments]
Setting up carrier identification → The CPRS SCAC code is assigned to SCAC-1, main SCAC code, and customs SCAC code fields, bill/waybill number is set from CCN ID number, and transport type is set to train with preliminary status
[Initialize First S07 Segment]
Preparing for final S07 processing steps → Move the first S07 segment data from array to working segment
[7150: Initialize M13 Record Structure]
The system initializes the M13 record structure → Initialize the GCSUSS01 segment, set the US CCN key, record type to '01', and sequence to '0001'
[Initialize Secondary Communication]
The system needs to use secondary communication for audit logging → Secondary communication is initialized and configured for detour audit message processing
[Initialize Broker Segment - Invalid Broker]
System cannot find valid broker configuration in broker table → System initializes empty broker segments, performs invalid broker processing, sets cargo status to reject, and creates error notification message
[Initialize Empty Broker Segment]
Both port-specific and default port broker lookups fail → Initialize empty broker segment and B1 segment data structures
[Initialize In-House Message Structure]
The system begins in-house notification processing → The system initializes the in-house message structure and sets the cargo type to Canadian cargo
[Initialize Empty SK Segment]
The system needs to assign city code values → The system initializes empty SK segment with default values
[Initialize Empty Broker Segment]
No broker information is found in the BK table → The system should initialize empty BK-SEGMENT and B1-SEGMENT and exit broker lookup process
[Initialize Empty Broker Segment]
No valid broker information can be retrieved → The system should Execute broker invalid error processing
[Initialize Broker Segment if Not Found]
The system performs a second lookup using the same broker name and Canadian flag with default port '000' → The system retrieves broker information if found with default port, or initializes empty broker segment if both lookups fail
[Initialize SCAC Codes]
SCAC codes are being set in the manifest structure → CPRS SCAC code is assigned to M1112-SCAC-1, M1001-SCAC-CDE, M1301-SCAC-CDE1, and M1309-SCAC-CDE2 fields
[Initialize Segment Fields to Spaces]
The segment initialization process begins → All segment index fields, creation fields, modification fields, waybill keys, bond indexes, destination indexes, and flag indicators are cleared to spaces
[Initialize M13 Segment Structure]
The system initializes the M13 segment structure → The M13 record is set with cargo CCN as key, record type '01', and sequence number '0001'

Core Acceptance Criteria

[Cargo Data Copying]
A segment is not empty → The system should update the segment CCN key to the new work CCN key
[Country Type Check]
If the cargo country type → The cargo is classified as either Canadian, US, or invalid for further processing routing
[Create Audit Message for Border Change]
The system creates an audit trail → An audit message should be generated with action code 'ZZZ' and message text 'AUTO CHG BORD FROM [old_port_name] TO [new_border_name]' for the Canadian cargo
[Set New CCN Key in All Segments]
Copying new Canadian key data → The work CCN key is assigned to GCCC-CCN-KEY, GCSCCS52-KEY-CCN, and NEW-CDN-CCN
[Update All Segment Arrays with New CCN]
Inserting new Canadian cargo → For each non-empty segment in the array, the CCN key is updated to the new value, record type is set to '53', and sequence number is assigned
[Replace Canadian Cargo in Database]
Performing database insert operation → GCCCCIO2 is called with REPL function to insert all segments, and first segment data is moved back to working storage
[Create Audit Trail Message]
Creating audit trail → GCX105 input is initialized with new CCN, cargo type is set to Canadian, action code is set to 'ZZZ', and message is set to 'SPECIAL MANIFEST AUTOMATICALLY CREATED'
[Lookup Border Table MC]
Looking up border information for Canadian manifest → The system performs a table lookup using function code 'GU', table ID 'MC', and the border name as sequence ID to retrieve border segment data
[Set US Port Exit Code]
Processing valid border information → The table segment is moved to GCSTBRT-MC-SEGMENT and the US exit code (GCSTBRT-MC-US-STAT-EXIT-CD) is assigned to GCCC-US-PORT-OF-EXIT-CODE
[Create Audit Log Message]
The system creates the audit trail → An audit message is constructed with the format 'AUTO CHG DEST FROM [old port name] TO [new manifest-to station name]' and the action code is set to 'ZZZ'
[Spawn Audit Transaction GCT1051E]
The system finalizes the audit process → A GCT1051E audit transaction is spawned with the port change details for system logging
[Set Diverted Flag]
The system processes the diversion request → Set the cargo status to diverted
[Lookup Broker at New Border]
The system looks up broker information using broker short name and new border code → Retrieve broker segment data from the broker table
[Create Invalid Broker Message]
The system creates audit messages → Generate message 'DIVERTED TO INVALID BROKER AT [border-name]' with action code ZZZ
[Create Audit Log Message]
The system creates audit documentation → Generate audit message 'AUTO DIVERTED FROM [old-port-name] TO [new-border-name]' with action code ZZZ
[Broker Found at Border?]
If the lookup results → If broker is not found, cargo error status is set and invalid broker message is created, otherwise broker segment data is retrieved
[Create Invalid Broker Message]
The system creates audit trail messages → An audit message is created stating 'DIVERTED TO INVALID BROKER AT [border-name]'
[Get Broker Segment Data]
The system processes valid broker information → The broker segment data is retrieved and stored for further processing
[Office Code = '00'?]
The system processes broker office code information → If broker office code is '00', the office code is cleared to spaces, otherwise the broker office code is assigned to the cargo
[C220: Read All US Cargo Data]
Creating new bill from existing manifest → The system should read all US cargo segments (S01-S15) and populate working arrays
[Set Equipment ID & Waybill Data]
Building new US manifest structure → The system should format car ID using ISCCARID program and set waybill numbers and dates in appropriate segments
[Propagate New CCN to All Segments]
Finalizing new manifest structure → The system should update all non-empty segments (S01-S15) with the new CCN number
[Propagate New CCN to All Segments]
Processing segment data → The system should clear line release numbers and quantities for the first two entries
[8530: Insert New US Cargo Record]
Inserting new cargo record → The system should insert all segments (S00-S15) as a complete new US cargo record
[7310: Create Audit Log Entry]
Completing the new bill creation process → The system should create audit log entry with message 'SPECIAL MANIFEST AUTOMATICALLY CREATED' and new CCN information
[Access Counter Table CW]
The system accesses the counter table using table ID 'CW' → The counter table segment is retrieved successfully or an error is returned
[Set New US CCN Key to All Segments]
The manifest data structure is being initialized → The new US CCN key is assigned to car ID index, waybill index, car-waybill index, and the main US CCN key field
[Update Each S07 Segment with New CCN]
Each S07 segment is processed up to the maximum sequence → For each non-empty S07 segment, the new US CCN key is assigned to the segment key field and the segment is updated in the working array
[Clear Line Release Data]
S07 segment data is being processed → Line release numbers for positions 1 and 2 are cleared to spaces and quantity fields for positions 1 and 2 are cleared to spaces
[Set Default Quantity Values]
Default quantity values need to be set → The manifest quantity field value is assigned to the first position quantity field in the S07 segment
[Process S08 Segments]
Each S08 segment is processed up to maximum sequence → For each non-empty S08 segment, the new US CCN key is assigned to the segment key field and the segment is updated in the working array
[Process S03 Segments]
Each S03 segment is processed up to maximum sequence → For each non-empty S03 segment, the new US CCN key is assigned to the segment key field and the segment is updated in the working array
[Process S06 Segments]
Each S06 segment is processed up to maximum sequence → For each non-empty S06 segment, the new US CCN key is assigned to the segment key field and the segment is updated in the working array
[Update S10-S14 Segments]
Each S12 segment is processed up to maximum sequence → For each non-empty S12 segment, the new US CCN key is assigned to the segment key field and the segment is updated in the working array
[Lookup Tax Table 'TX']
The tax table lookup is performed using table ID 'TX' → The system retrieves the CPRS tax number from the tax table segment
[Lookup City Code from SK Table]
The system looks up the border name in the SK table → If found, the city code is retrieved from the SK segment, otherwise the SK segment is initialized as empty
[Create Audit Log Message]
Creating audit documentation → An audit message is created with format 'AUTO DIV BOND DEST FROM [old port name] TO [new border name]' and action code 'ZZZ'
[Lookup Border Name in SK Table]
The system looks up the border name in the SK table using the determined border name as the search key → If the SK table entry is found successfully, the system should load the SK segment data, otherwise initialize an empty SK segment
[Update M1204 Location with City Code]
The SK segment contains valid city code information → The system should update M1204-LOCATION-ID2 with the city code from SK table and M1204-LOC-ID2-NAME with the border name
[Generate Audit Message]
The system needs to create an audit trail of the changes made → The system should generate an audit message with action code 'ZZZ' containing the text 'AUTO DIV BOND DEST FROM [old-port-name] TO [new-border-name]' and spawn the audit transaction
[C220: Read All US Cargo Data]
The system needs to copy cargo data to new manifest → All cargo segments should be retrieved and bill type, bond type, and bond number should be saved for reference
[C450: Set Up TE Bond Data for Mexico]
The system sets up TE bond data → Set transport export flag to true, determine re-entry point, set Mexico destination codes (MX/20100 or CA/88888), clear N10 segments except first, and ensure harmonized commodity code is not empty or 999999
[Clear Line Release Numbers]
The system processes export line release data → Clear line release numbers and quantities in positions 1 and 2 of the N1009 and N1001 segments
[Copy Cargo Data to New Manifest]
The system copies cargo data to new manifest → Update all segment CCN keys with new US CCN, copy equipment and waybill information, set creation timestamps, and maintain all cargo detail segments with new CCN references
[8530: Insert New US Cargo Record]
The system inserts the new cargo record → Insert all cargo segments into database and handle any insertion errors with appropriate error messages
[Generate Audit Messages]
The system generates audit messages → Create audit message for new manifest indicating bill type and creation purpose, create audit message for original manifest indicating new bill creation, and send GCT011 message for bond movement tracking
[Lookup SK Table for Re-Entry Port Details]
The system looks up the port in the SK table using the re-entry port name → The system retrieves the complete port segment data including city codes and location details
[Clear N10 Segment Data]
The system prepares to process N10 segment data → All N10 segment arrays are cleared and the first segment data is moved to working storage
[Process N10 Segment with GCCUSCN2]
The commodity code identifier is not spaces or low-values → The system calls GCCUSCN2 to process the N10 segment with segment ID 'N10' and record type '07'
[Update Segment Arrays]
The system finalizes transportation export data configuration → The processed segment data is moved back to the first position of the working storage segment array
[Search Junction Table for Mexico Routing]
The system searches for junction matches in the routing table → If a matching junction code is found in the Rule 260 table, the junction and rail information are captured for further processing
[Lookup Junction in SD Table]
The system looks up the junction in the SD table using table ID 'SD' → Station destination segment data is retrieved if the junction exists in the SD table
[Get Port Code from SD Table]
The system extracts port information from the SD segment → The SD port code is assigned to the cargo location and re-entry code fields
[Lookup Port in DS Table]
The system looks up the port code in the DS table using table ID 'DS' → Destination station segment data is retrieved if the port code exists in the DS table
[Set Mexico Destination Port Name]
The system extracts port name information from the DS segment → The DS port name is assigned to the cargo location name and re-entry name fields
[Log Junction Not Found on SD Table]
The SD table lookup fails for the junction → An error message is logged indicating the junction was not found on SD table and processing continues to next junction
[Log Port Not Found on DS Table]
The DS table lookup fails for the port code → An error message is logged indicating the port was not found on DS table and processing continues to next junction
[Call GCCCROS2 crossing table lookup]
Performing crossing table lookup for SNP data → Call GCCCROS2 program with crossing table parameters and crossing table segment to retrieve SNP information
[7350: Spawn GCT1113E Canadian Manifest]
The system creates the Canadian manifest notification → The system sets the border name and re-entry name in the GCM111 message and spawns the GCT1113E transaction
[US-US or CA-CA Detour Decision]
The system prepares the US manifest message → For US-US detours, the system sets the US action code, and for CA-CA detours, the system sets the RT action code
[7340: Spawn GCT0111E US Manifest]
The system creates the US manifest notification → The system sets the manifest from/to border names, waybill number and date, and car ID in the GCX011 message and spawns the GCT0111E transaction
[Set Action Code to DOM-DETOUR]
The system creates a GCM111 domestic detour message → The system should set the action code to DOM-DETOUR to identify the message type
[Set Environment to Background]
The system sets up the processing environment → The system should configure the environment for background processing
[Populate Waybill and Car ID]
The system populates the message fields → The system should include the waybill key and car ID from the original detour request
[Set Border and Re-Entry Names]
The system populates the GCM111 message location fields → The system should set the border name as RT04 location and re-entry name as M1203 location
[Spawn GCT1113E Transaction]
The system needs to notify about the domestic detour → The system should spawn a GCT1113E transaction with the prepared message
[Set US Action Code]
The detour type is US-to-US detour → The system should set the US action code in the manifest message
[Set RT Action Code]
The detour type is Canada-to-Canada detour → The system should set the RT action code in the manifest message
[Set Border as Manifest From]
The system populates the routing information → The system should set the border name as the manifest from location
[Set Re-Entry as Manifest To]
The system populates the routing information → The system should set the re-entry name as the manifest to location
[Populate Waybill Details]
The system populates the waybill details → The system should include waybill number, waybill date, and car ID in the message
[Spawn GCT0111E Transaction]
The system needs to track the manifest movement → The system should spawn a GCT0111E transaction with the prepared manifest message
[Get B1 Table Segment]
The system retrieves additional broker configuration → The system looks up the B1 table segment for internet address information, initializing empty segment if not found
[Send X12 EDI Notification]
The broker's X12 usage flag is set to 'Y' → The system sends X12 EDI notification using the broker's X12 header and the cargo CCN key
[Send Internet Notification]
The broker's internet usage flag is set to 'Y' → The system creates a print job using the internet address from B1 segment and the cargo CCN with high-value security byte
[X12 EDI Enabled?]
The broker's X12 usage flag is set to 'Y' → The system sends X12 EDI notification using the broker's X12 header information and the cargo CCN key through the GCCS309C program
[Internet Enabled?]
The broker's internet usage flag is set to 'Y' → The system sends internet notification using the B1 segment's internet address and cargo CCN through the 7320-SPAWN-GCT0191E-PRINT procedure
[Set CCN for Audit Trail]
The audit message is being prepared → The system sets the cargo control number (GCX101-CCN) as the train or US CCN identifier (GCX105-TRAIN-OR-US-CCN) in the audit message
[Set Cargo Type as Canadian]
The audit message cargo type needs to be specified → The system sets the cargo type indicator to Canadian cargo (GCX105-CA-CARGO) in the audit message
[Set Action Code to ZZZ]
The audit message action code needs to be assigned → The system sets the action code to 'ZZZ' (GCX105-ACTION-CODE) to indicate an error condition
[Create Audit Log Entry]
The audit log entry needs to be created → The system calls the audit logging function (7310-SPAWN-GCT1051E) to create the permanent audit record
[Port Change Message]
The border change operation is completed successfully → The system constructs message 'AUTO CHG BORD FROM [old-port-name] TO [new-border-name]' AND creates audit trail with action code 'ZZZ'
[Port Change Message]
The destination port change is completed → The system constructs message 'AUTO CHG DEST FROM [old-port-name] TO [new-destination-name]' AND creates audit trail with action code 'ZZZ'
[Cargo Diversion Message]
The diversion operation completes successfully → The system constructs message 'AUTO DIVERTED FROM [old-port-name] TO [new-border-name]' AND creates audit trail with action code 'ZZZ'
[Port Change Message]
The bond destination change is completed → The system constructs message 'AUTO DIV BOND DEST FROM [old-port-name] TO [new-border-name]' AND creates audit trail with action code 'ZZZ'
[Bond Creation Message]
The new bond bill is created and notifications are sent → The system creates first message '[bond-type] BILL CREATED FOR [original-bond-type] BILL [original-ccn]' for new CCN AND creates second message '[bond-type] BILL [new-ccn] CREATED FOR [original-bond-type] BILL' for original CCN
[Get Border Crossing Name]
The system needs to format location details in messages → The system looks up the Canadian border name using the border code from the ports table AND uses the retrieved name in message construction
[Construct Multi-part Message]
The system constructs the final message string → The system concatenates message parts using STRING operations with 'DELIMITED BY SIZE' AND ensures proper message structure and completeness
[Combine Components with Delimiters]
The system constructs the final message string → The system uses STRING operation to combine components with 'AUTO CHG BORD FROM', 'AUTO CHG DEST FROM', 'TO', and other descriptive text delimited by SIZE into the target message field
[Format Message Components]
The system processes each character position in the CCN → The system copies non-space and non-zero characters to destination, processes numeric sequences when found, and maintains proper positioning for compressed CCN format
[STRING 'AUTO CHG BORD FROM ' + OLD-PORT-NAME + ' TO ' + BORDER-NAME]
The system needs to create an audit trail message for the border change → Construct a message by concatenating 'AUTO CHG BORD FROM ' + old port name + ' TO ' + new border name and store it in the message field
[STRING 'AUTO CHG DEST FROM ' + OLD-PORT-NAME + ' TO ' + DEST-NAME]
The system needs to create an audit trail message for the destination change → Construct a message by concatenating 'AUTO CHG DEST FROM ' + old port name + ' TO ' + new destination station name and store it in the message field
[STRING 'AUTO DIVERTED FROM ' + OLD-PORT-NAME + ' TO ' + BORDER-NAME]
The system successfully processes the diversion → Construct a message by concatenating 'AUTO DIVERTED FROM ' + old port name + ' TO ' + new border name and store it in the message field
[STRING 'AUTO DIV BOND DEST FROM ' + OLD-PORT-NAME + ' TO ' + BORDER-NAME]
The system processes a bond destination change → Construct a message by concatenating 'AUTO DIV BOND DEST FROM ' + old port name + ' TO ' + new border name and store it in the message field
[STRING BOND-TYPE + ' BILL CREATED FOR ' + SAVE-BOND-TYPE + ' BILL ' + CCN]
The system creates a new bond bill from an existing bond → Construct a message by concatenating the new bond type + ' BILL CREATED FOR ' + original bond type + ' BILL ' + original CCN and store it in the message field
[STRING BOND-TYPE + ' BILL ' + NEW-CCN + ' CREATED FOR ' + SAVE-BOND-TYPE + ' BILL']
The system creates a new bond bill and needs to update the original bill with audit information → Construct a message by concatenating the new bond type + ' BILL ' + new CCN + ' CREATED FOR ' + original bond type + ' BILL' and store it in the message field
[MOVE 'SPECIAL MANIFEST AUTOMATICALLY CREATED' TO MESSAGE]
The system needs to create an audit message for the automatically created manifest → Set the message field to 'SPECIAL MANIFEST AUTOMATICALLY CREATED'
[Prepare GCT0191E Message]
The system prepares the GCT0191E message for Merlin notification → The system transfers the GCX019 input data to the GCT0191E message structure
[Clear Accept Status]
The system initializes the message queue processing → The system sets the accept status to spaces to clear any previous status
[Change Message Queue Status]
The system prepares to send the Merlin notification → The system calls CIMS with CHNG function to change the alternate PCB queue status for GCT0191E message type
[Write Message to Queue]
The system delivers the Merlin notification → The system calls WRITMSGL to write the message with message code, content, length and module name to the alternate PCB queue
[Purge Message Queue]
The system completes the message delivery process → The system calls CIMS with PURG function to purge the alternate PCB queue
[Send X12 EDI Notification]
The broker's USE-X12 flag is set to 'Y' → Send X12 EDI notification using the broker's X12 header and cargo control number
[Get Broker Delivery Schedule]
The system needs to validate delivery schedule requirements → The system extracts the broker delivery schedule value from the broker segment
[Validation Passed - Continue Processing]
The delivery schedule is either DEFAULT-DELIVERY or IMMEDIATE-DELIVERY → The system continues with broker notification processing
[Validation Failed - Skip Broker Notification]
The delivery schedule is neither DEFAULT-DELIVERY nor IMMEDIATE-DELIVERY → The system skips broker notification and exits the validation process
[Check Broker at Border Location]
The system searches the BK broker table using concatenated broker short name and border code → The system should retrieve broker segment data if found in the table
[Broker Valid at Border?]
The broker table search fails to find matching broker at border location → The system should set CPCARGO error status and create diverted to invalid broker audit message
[Call GCCS309C - Send to CCRA]
The system executes the CCRA notification → The GCCS309C interface is called to transmit the notification to CCRA
[Prepare Audit Message]
An audit trail needs to be created → The system prepares audit message parameters for logging
[Set CCN for Audit Trail]
The audit trail needs cargo identification → The CCN is assigned to the audit trail record
[Set Cargo Type as Canadian]
The cargo type needs to be specified in the audit trail → The cargo type is set as Canadian cargo
[Search Routing Junctions for Mexico-bound Cargo]
The system iterates through up to 10 routing junction entries in the routing table → The system searches each junction entry against the Rule 260 table to find a matching routing path
[Search GCSPORTS-PORTS Table]
The system searches for a matching port entry → The system finds a match when the border code equals either the US port code or the Canadian port code in any table entry, and extracts the corresponding Canadian and US port names from that matched entry
[Set Transmission Prefix to '98']
The transaction type has been determined → The transmission prefix should be set to '98'
[Get US CCN Key]
The transmission parameters are being set → The US CCN key from the cargo record should be assigned to the customs message
[Call GCCS309E for Export Processing]
The border port is classified as an export port → The GCCS309E export processing service should be called with the customs message parameters
[Call GCCS309 for Standard Processing]
The border port is NOT classified as an export port → The GCCS309 standard processing service should be called with the customs message parameters
[Is Export Manifest?]
The port location is found in the SE table AND the cargo is an export manifest → The system uses the special CBP export service GCCS309E, otherwise uses standard customs service GCCS309
[Use Special CBP Export Service GCCS309E]
The system determines special CBP export processing is required → The system calls the GCCS309E service for specialized export manifest processing
[Use Standard Customs Service GCCS309]
The system determines standard customs processing is required → The system calls the GCCS309 service for standard customs manifest processing
[Lookup B1 Table for Additional Info]
The system looks up additional information in B1 table → Load B1 segment if found, otherwise initialize empty B1 segment
[Set US CCN Key in Message]
The system prepares the notification message → The US CCN key from the cargo record is assigned to the message CCN field
[Set Security Byte to High Value]
Security authorization needs to be established → The security byte is set to high value to grant full access privileges
[Change Message Queue to GCT1081E]
The message queue is being configured → The system changes the message queue to use GCT1081E transaction type
[Write Message to Queue with: - Message Code - Message Content - Message Length - Module Name]
The system writes the message to the queue → The message is transmitted with message code, content, length, and module name included
[Purge Message Queue]
The transmission process is complete → The system purges the message queue to clear processed messages
[Prepare Message Components]
The system prepares message components → Message code, content, length, and module name are set appropriately for the specific message type
[Set Message Code]
The message code is being set → The message code is set to GCT1051E-MSG-CODE
[Set Message Code]
The message code is being set → The message code is set to GCT0191E-MSG-CODE
[Set Message Code]
The message code is being set → The message code is set to GCT1081E-MSG-CODE
[Set Message Code]
The message code is being set → The message code is set to GCT0111E-MSG-CODE
[Set Message Code]
The message code is being set → The message code is set to GCT1113E-MSG-CODE
[Set Message Content]
The message content is being set → The message content includes sending transaction, ACF2 user ID, security byte, date, time, CCN, cargo type, and action code
[Set Message Content]
The message content is being set → The message content includes CCN, security byte, and delivery method (Merlin ID, Internet address, or FAX number)
[Set Message Content]
The message content is being set → The message content includes US CCN, security byte, and delivery method details (Merlin ID, Internet address, or FAX number)
[Set Message Content]
The message content is being set → The message content includes action code, CP number, origin station, waybill number, waybill date, manifest from/to locations, old CDN CCN, and car ID
[Set Message Content]
The message content is being set → The message content includes action code, environment setting, waybill key, car ID, location names, and routing details
[Set Message Length]
The message length is being calculated → The message length is set to the predefined length constant for the specific message type (GCT1051E-MSG-LGTH, GCT0191E-MSG-LGTH, GCT1081E-MSG-LGTH, GCT0111E-MSG-LGTH, or GCT1113E-MSG-LGTH)
[Set Module Name]
The module name is being set → The module name is set to the predefined module name constant for the specific message type (GCT1051E-MOD-NAME, GCT0191E-MOD-NAME, GCT1081E-MOD-NAME, GCT0111E-MOD-NAME, or GCT1113E-MOD-NAME)
[Call CIMS for Queue Management]
Queue management is invoked → CIMS is called with CHNG operation and appropriate PCB for the message type to prepare the queue
[Call WRITMSGL for Message Write]
Message write operation is executed → WRITMSGL is called with message code, message content, message length, and module name to write the message to the queue
[Purge Queue Buffer]
Queue cleanup is performed → CIMS is called with PURG operation and appropriate PCB to purge the queue buffer
[Set Security Byte to High-Value]
Security parameters need to be established → The security byte should be set to high-value to authorize transmission
[Assign US CCN Key to Message]
The message structure needs cargo identification → The US CCN key should be assigned to the message US CCN field
[Set Merlin ID Parameters]
Message communication parameters are being configured → Merlin ID should be populated and Internet and Fax fields should be cleared
[Set Internet Address Parameters]
Message communication parameters are being configured → Internet address should be populated and Merlin ID and Fax fields should be cleared
[Set Fax Number Parameters]
Message communication parameters are being configured → Fax number should be populated and Merlin ID and Internet fields should be cleared
[Set Diversion Information]
Broker notification message is being prepared → The diversion flag should be set to true in the message
[Set Diversion Port Code and Name]
Diversion port data needs to be included → The original port code and port name should be populated in the diversion port fields
[Set Previous Border Port Name]
Previous border port data needs to be recorded → The new border name should be set as the previous border port name
[Purge Existing Queue Messages]
PURG command is executed on the queue → All existing messages in the specified queue are removed
[Change Queue Status/Connection]
CHNG command is executed on the queue → Queue status is changed and connection is established for message processing
[Write Message to Queue Buffer]
WRITMSGL is called with message code, message content, message length and module name → Message is written to the queue buffer for transmission
[Clean Up Queue Resources]
Final PURG command is executed on the queue → Queue resources are cleaned up and freed for subsequent operations
[Access Counter Table CW]
The system accesses the counter table with table ID 'CW' → The counter table segment is retrieved containing the next available CPRS and bond numbers
[Process Segment Arrays S03-S14]
The system processes each segment in the S53 array up to the maximum sequence → For each non-empty segment (not spaces, low-values, or underscores), the new CCN key is assigned, record type '53' is set, and the sequence number is updated, while empty segments are cleared to spaces
[Update Segment with New CCN Key]
The segment data is not spaces, low-values, or all underscores → The segment CCN key is updated to the new CCN, the record type is set to '53', and the sequence number is assigned from the array index
[Complete Data Structure Setup]
Processing segments S01, S02, S04, S05, S06, S07, S08, S10, S11, S12, S13, and S14 → For each non-empty segment, the CCN key is updated to the new work US CCN key, and for equipment segments, the car initial and number are set from the formatted car ID
[Process Equipment ID with Compression]
Setting up equipment information for the new cargo record → The car ID is processed through ISCCARID compression with size 12, and the compressed output is stored in car ID number indexes and equipment car field
[Set Waybill Information in Indexes]
Setting up waybill tracking for the new cargo record → The waybill number is stored in waybill number indexes, the first 15 characters proceed to the root key, car sequence is set to '01', and waybill date is stored in the waybill date field
[Set Border Crossing Location Data]
Setting up location information for the new cargo record → The Canadian border name is determined from the border code, stored in the location ID name field, and the border code is stored in the location ID field and customs location ID field
[Process S07 Segment Array]
Processing segment arrays for the new cargo record → For each non-empty S07 segment entry up to maximum sequence, if the segment is not empty, the new US CCN key is assigned to the segment key field
[Propagate CCN Keys to All Segment Arrays]
Updating segment keys for the new cargo record → If S01 segment is not empty, the new US CCN key is assigned to S01 key field; if S02 segment is not empty, the new US CCN key is assigned to S02 key field
[Set Equipment Data in S05 Segment]
Setting up equipment information in segments → If S05 segment is not empty, the new US CCN key is assigned to S05 key field, equipment initialization is set from compressed car ID, and equipment number is set from compressed car ID number
[Process S08 Segment Array with CCN Keys]
Processing S08 segment array for CCN key updates → For each S08 segment entry up to maximum sequence, if the entry is not empty or low-values, and the segment is not empty, the new US CCN key is assigned to the S08 segment key field
[Process S03 Segment Array with CCN Keys]
Processing S03 segment array for CCN key updates → For each S03 segment entry up to maximum sequence, if the entry is not empty or low-values, and the segment is not empty, the new US CCN key is assigned to the S03 segment key field
[Process S06 Segment Array with CCN Keys]
Processing S06 segment array for CCN key updates → For each S06 segment entry up to maximum sequence, if the entry is not empty or low-values, and the segment is not empty, the new US CCN key is assigned to the S06 segment key field
[Process S12 Segment Array with CCN Keys]
Processing S12 segment array for CCN key updates → For each S12 segment entry up to maximum sequence, if the entry is not empty or low-values, and the segment is not empty, the new US CCN key is assigned to the S12 segment key field
[Set Final Segment Keys S10, S11, S13, S14]
Completing the CCN key propagation process → If S10 segment is not empty, assign new US CCN key to S10; if S11 segment is not empty, assign new US CCN key to S11; if S13 segment is not empty, assign new US CCN key to S13; if S14 segment is not empty, assign new US CCN key to S14
[More S07 Segments to Process?]
Processing S07 segments in sequence → Continue processing while index is within maximum sequence limit and segment contains data
[Update S07 with New US CCN Key]
Processing the segment for CCN key updates → Update the S07 segment CCN key with the new work US CCN key
[Clear Line Release Numbers and Quantities]
The operation type is IT Export or Export Transit → Clear line release numbers for positions 1 and 2 and clear quantities for positions 1 and 2
[Store Updated S07 Back to Array]
Completing processing for the current segment → Store the updated S07 segment back to its position in the array
[Update S07 CCN Key]
Processing the S07 segment array for new US cargo creation → The S07 segment CCN key is updated with the new work US CCN key
[Clear Line Release Data for Export Operations]
Processing S07 segment data during new US cargo creation → Clear line release numbers for positions 1 and 2 and clear quantities for positions 1 and 2
[Update S08 CCN Key]
Processing the S08 segment array for new US cargo creation → The S08 segment CCN key is updated with the new work US CCN key
[Update S03 CCN Key]
Processing the S03 segment array for new US cargo creation → The S03 segment CCN key is updated with the new work US CCN key
[Update S06 CCN Key]
Processing the S06 segment array for new US cargo creation → The S06 segment CCN key is updated with the new work US CCN key
[Update S12 CCN Key]
Processing the S12 segment array for new US cargo creation → The S12 segment CCN key is updated with the new work US CCN key
[Update Single Segments S10/S11/S13/S14]
Processing single segments during new US cargo creation → Update the respective segment CCN key with the new work US CCN key
[Clear Line Release Data for Export Operations]
Processing quantity data during S07 segment updates → Transfer the master quantity picture 9 value to the commodity quantity picture 9 field for position 1
[Set SCAC Code to 'CPRS']
The system sets the SCAC code fields → Set both M1301 SCAC code 1 and M1309 SCAC code 2 to 'CPRS'
[Get Port Code from GCSTBRT-SD-PORT-CODE]
The system extracts port routing information → The port code is retrieved from GCSTBRT-SD-PORT-CODE field in the SD table segment
[Get Port Name from GCSTBRT-DS-NAME]
The system extracts port name information → The port name is retrieved from GCSTBRT-DS-NAME field in the DS table segment
[Extract Port Code from SD Table]
The system processes the SD table segment data → The port code is extracted and assigned to the cargo location and re-entry code fields
[Set Mexico Destination Port and Name]
The system processes the DS table segment data → The port name is assigned to the cargo location name and re-entry name fields
[Log Junction Not Found in SD Table]
No valid port code mapping is found for the junction → The SD table segment is initialized to default values and processing continues with default settings
[Get Port Code from SD Entry]
Port information is extracted → The port code is retrieved from the SD segment and stored for DS table lookup
[Display Port Not Found Message]
Port lookup fails → Display error message indicating port not found on DS table with the port code
[Display Junction Not Found Message]
Junction lookup fails → Display error message indicating junction not found on SD table with the junction value
[Lookup Junction in SD Table]
The system performs an SD table lookup using the junction value → If the SD table entry is found successfully, extract the port code from the SD segment and update the manifest location ID
[Extract Port Name from DS]
The system searches the DS table using the port code → If the DS table entry is found, extract the port name from the DS segment and update both the manifest location name and re-entry name fields
[Restore Primary Communication]
The system finishes writing detour audit messages → Primary communication channel is restored for normal processing operations
[Purge Message Queue]
The system prepares to write audit trail entries → The message queue is purged to ensure clean audit message delivery
[Change Message Destination]
The system needs to route the audit message to the correct destination → Message destination is configured based on the audit type and routing requirements
[Write Message to Log]
The system executes the audit logging operation → The audit message is written to the designated audit log with proper formatting and message length
[Complete Audit Entry]
The system completes the audit logging process → Final cleanup operations are performed and the audit entry is marked as complete
[Delivery Schedule Valid?]
The system checks the broker's delivery schedule preference → Notification proceeds only if delivery schedule is 'DEFAULT-DELIVERY' or 'IMMEDIATE-DELIVERY', otherwise notification is skipped
[Get B1 Table Data]
The system retrieves B1 table data for the broker → B1 segment data is loaded if found, otherwise B1 segment is initialized to spaces
[X12 EDI Enabled?]
The broker's X12 EDI usage flag is set to 'Y' → The system calls GCCS309C with notify-broker flag and broker's X12 header information
[Broker Table Lookup - BK]
The system searches the broker table (BK) with the specific port code → If broker is found at specific port, load broker segment data, otherwise attempt lookup with default port '000'
[Try Default Port 000]
The system searches the broker table (BK) using default port '000' → If broker is found at default port, load broker segment data, otherwise initialize empty broker segment
[Broker Details Table - B1]
The system searches the B1 table for additional broker details → If B1 record is found, load B1 segment data, otherwise initialize empty B1 segment
[Border/Port Table - MC]
The system searches the MC table using the border name as key → If border is found, load border segment data and set US port exit code, otherwise return border not found error
[Station Table - SK]
The system searches the SK table using the border name as key → If station is found, load station segment data and set city code, otherwise initialize empty station segment
[Call GCCTBIO with Parameters: - Function Code - Table ID - Sequence ID - Key Values]
The system calls the table lookup service with the provided parameters → The system executes the table lookup operation and returns the appropriate data segment or error status
[Load Table Segment Data into Working Storage]
The lookup returns valid table segment data → The system loads the retrieved table segment data into working storage variables for application use
[Try Default Port 000 Lookup]
The system performs a secondary lookup using port code '000' as fallback → If fallback lookup succeeds, use the default broker configuration; if it fails, initialize empty broker segment and continue processing
[Include CCN and Context Details]
The system detects the failure condition → Format error message including the CCN being processed and specific error context, then call error handler CERR
[Send X12 EDI Notification to Secondary Broker]
The broker configuration has USE-X12 set to 'Y' → Send X12 EDI notification using the broker's X12 header information and the cargo CCN key
[Broker Validation Required?]
Broker validation is required and no valid broker was found → Execute invalid broker handling process
[Handle Invalid Broker]
Broker validation fails → Create audit message 'DIVERTED TO INVALID BROKER AT [border-name]', set cargo status to reject, and update cargo record
[Proceed with Broker Notification]
Broker notification is required → Process notifications via X12 EDI, Merlin system, Internet, FAX, or paper based on broker's communication preferences and update batch print call letters if paper notification is used
[Copy CCN Status to Message]
The system populates the message with cargo information → The system copies the current cargo status to the CCN status field in the message
[Copy Equipment ID to Message]
The system continues populating the message with cargo details → The system copies the equipment ID from the cargo record to the car ID field in the message
[Copy Waybill Number to Message]
The system continues populating the message with cargo details → The system copies the first 15 characters of the waybill key to the waybill field in the message
[Copy CCN Key to Message]
The system continues populating the message with cargo identifiers → The system copies the complete CCN key to the CCN field in the message
[Search for CN Reference Number]
The system needs to find the shipment ID from reference numbers → The system initializes a counter to zero and begins iterating through up to 10 reference number entries
[Copy Reference Number as Shipment ID]
The system identifies this as the Canadian shipment reference → The system copies the reference number value to the shipment ID field in the in-house message
[Call GCCIH Program for In-House Processing]
The system completes message preparation → The system calls the GCCIH program to process the in-house notification with the cargo message
[Generate Invalid Broker Message]
The system generates audit messages → An audit message is created stating 'DIVERTED TO INVALID BROKER AT [border-name]'
[Lookup Border Name in SK Table]
The system looks up the border name in the SK (Station/City) table → The system attempts to retrieve the corresponding city code segment from the reference table
[Assign City Code to M1204-LOCATION-ID2]
The system assigns location identifiers for transport export cargo → The city code from the SK segment is assigned to the cargo's M1204-LOCATION-ID2 field
[Call SNP Lookup Service]
Calling the SNP lookup service → Execute GCCCROS2 program with SNP parameters and crossing table segment to retrieve notify party information
[Extract Waybill Number and Date from Input]
The system needs to search for existing Canadian manifests → The waybill number and waybill date are extracted from the input and stored in working storage variables for search operations
[Format Waybill Key for Search]
The system prepares to search the Canadian manifest database → The waybill number and date are combined into a formatted search key that matches the database index structure
[Search Routing Junctions for Mexico-bound Cargo]
The system processes Mexico destination routing and searches through GCSUSS13 routing segments for Rule 260 junction matches → The system iterates through up to 10 routing segments and identifies matching junctions in the Rule 260 table
[Lookup Junction in SD Table]
The system performs a lookup in the SD table using the junction as the search key → The system retrieves the SD segment containing port code information for the junction
[Extract Port Code from SD Segment]
The system processes the SD segment data → The system extracts the port code from the SD segment and assigns it to the manifest location and re-entry code fields
[Lookup Port Details in DS Table]
The system performs a lookup in the DS table using the port code as the search key → The system attempts to retrieve detailed port information from the DS table
[Assign Mexico Port Name and Code to Manifest]
The system processes the DS segment containing port name information → The system assigns the port name to the manifest location name field and updates the re-entry name
[Call GCCCROS2 for SNP crossing table lookup]
System needs to retrieve notify party SCAC codes → Call GCCCROS2 program with SNP parameters and crossing table segment to get notify party data
[Fallback to Default Port 000]
Looking up broker in BK table with broker name, Canadian flag 'C', and default port '000' → Return broker configuration if found, otherwise initialize empty broker segments
[X12 EDI Enabled?]
The broker X12 usage flag is 'Y' → Send X12 EDI notification using GCCS309C with broker X12 header and CCN key
[Lookup Broker in BK Table by Port]
The system looks up the broker in the BK table using broker name, Canadian flag 'C', and the specific port code from positions 2-3 of the manifest-to-trans-code → The system attempts to retrieve the broker configuration segment from the table
[Lookup Broker at Default Port 000]
The system performs a second lookup using the same broker name and Canadian flag 'C' but with default port '000' → The system attempts to retrieve the broker configuration segment using the default port settings
[Lookup B1 Table for Additional Info]
The system looks up the B1 table using table ID 'B1' → The system retrieves additional broker configuration information if available, or initializes empty B1 segment if not found
[X12 EDI Method Enabled?]
The system processes X12 EDI notifications → The system sets notify-broker flag, assigns the broker's X12 header information, sets the CCN key, and calls GCCS309C for X12 EDI transmission
[Internet Method Enabled?]
The system processes Internet notifications → The system initializes GCX019 input, sets the CCN, security byte to high-values, assigns the Internet address from B1 segment, and calls 7320-SPAWN-GCT0191E-PRINT
[Broker Uses X12 EDI?]
The system checks broker communication preferences for X12 EDI → The system should proceed with X12 EDI notification if the broker uses X12 EDI, otherwise skip to next notification method
[Set Notification Type to Broker]
The system prepares X12 EDI notification parameters → The system should set the notification type to broker notification mode
[Validate Broker X12 Header]
The system prepares X12 EDI notification → The system should assign the broker's X12 header to the EDI message parameters
[Set CCN Key for Message]
The system prepares X12 EDI notification parameters → The system should assign the cargo control number to the EDI message key
[Set Action Code from Spawn Action]
The system prepares X12 EDI notification parameters → The system should assign the spawn action code to the EDI message action code field
[Call GCCS309C for X12 Transmission]
The system initiates X12 EDI transmission → The system should call the GCCS309C program to transmit the X12 EDI message to the broker
[Broker Uses X12?]
The system checks if the broker uses X12 EDI transmission → The system should proceed with X12 notification if broker X12 usage is set to 'Y', otherwise skip X12 processing
[Set Notification Parameters]
The system prepares X12 notification parameters → The system should set the notification type to broker notification mode
[Move Broker X12 Header to Parameters]
The system prepares X12 transmission parameters → The system should copy the broker's X12 header to the transmission parameter structure
[Move CCN Key to Parameters]
The system prepares X12 transmission parameters → The system should copy the CCN key to the transmission parameter structure
[Call GCCS309C for X12 Transmission]
The system initiates X12 EDI transmission → The system should call the GCCS309C program to send the X12 EDI message to the broker
[Prepare GCX019 Input Message]
The system begins preparing the notification message → The GCX019 input message structure is initialized to clear any previous data
[Move CCN to Message]
The system processes the notification for the cargo → The CCN from the cargo record is copied to the GCX019-CCN field in the notification message
[Set Security Byte to High-Value]
The system configures security settings for the message → The security byte is set to high-values to grant full authorization privileges
[Copy Input to GCT0191E Message]
The system prepares to send the notification → The complete GCX019-INPUT content is copied to the GCT0191E-MSG field
[Clear Accept Status]
The system prepares the message queue for transmission → The CC-ACCEPT-STATUS is set to spaces to clear any previous status
[Call CIMS - Change PCB]
The system needs to configure the message queue for transmission → The CIMS service is called with CHNG parameter to modify the ALT-PCB queue configuration
[Call WRITMSGL - Send Message]
The system transmits the notification message → The WRITMSGL service is called with the ALT-PCB queue, message code, message content, message length, and module name to send the GCT0191E notification
[Call CIMS - Purge PCB]
The system completes the message transmission process → The CIMS service is called with PURG parameter to purge the ALT-PCB queue and clean up resources
[Get B1 Table for Additional Info]
The system looks up additional information in B1 table → If B1 table information is found, load it into broker segment; otherwise initialize B1 segment to spaces
[Broker Found in BK Table?]
The system searches the BK table for broker information → If broker is not found (return flag not equal to '0'), initialize empty broker segment and exit, otherwise proceed with found broker data
[Get B1 Table for Additional Info]
The system needs extended broker information for notification methods → Lookup B1 table for additional broker configuration, if found use the data otherwise initialize empty B1 segment
[Lookup B1 Table for Extended Info]
The system looks up extended information in B1 table → Load B1 segment if found, otherwise initialize empty B1 segment
[Use Merlin = Y?]
The system processes communication preferences → Prepare Merlin message with broker Merlin ID and send via GCT1081E
[Use Internet = Y?]
The system processes communication preferences → Set Internet address from B1 segment and send via GCT1081E
[Clear Message Fields]
The system completes the notification → Clear all message input fields to prepare for next processing
[Lookup Additional Broker Info from B1 Table]
The system queries B1 table using table ID 'B1' → The system should retrieve additional broker details and populate B1-SEGMENT if found, otherwise initialize empty B1-SEGMENT
[Retrieve Broker Information from BK Table]
The system looks up broker information in the BK table using broker name, Canadian flag 'C', and port code from manifest-to-trans-code positions 2-3 → The system retrieves the broker segment if found, or attempts lookup with default port '000' if initial lookup fails
[Broker Validation Required?]
The system cannot find a valid broker and broker validation is required → The system marks the broker as invalid, sets cargo status to reject, and creates an error message for invalid broker at the specified border
[Send X12 EDI Notification via GCCS309C]
The broker X12 usage flag is set to 'Y' → Send X12 EDI notification using GCCS309C with broker X12 header and CCN key
[Lookup US Broker in BK Table]
Looking up broker in BK table using broker short name and destination location ID if available, otherwise origin location ID → Retrieve broker configuration details or initialize empty broker segment if not found
[Get B1 Table Information]
The system needs additional broker configuration → The system should retrieve B1 table information for the broker, initializing empty B1 segment if not found
[Send X12 EDI Notification via GCCS309C]
The system processes broker notifications → The system should send X12 EDI notification using GCCS309C with broker's X12 header and CCN key
[Retrieve Current Bond Number Counter]
The system needs the current bond number for assignment → The system should move the next bond number from the CW segment to the working storage bond number variable
[Increment Bond Number Counter]
The system needs to prepare for the next bond number assignment → The system should add 1 to the next bond number field in the CW segment
[Update Counter Table with New Value]
The system needs to persist the updated counter value → The system should replace the CW counter table record with the updated segment containing the new bond number counter
[Process Manifest Segments S07]
Processing segments from index 1 to maximum S07 sequence number → For each non-empty S07 segment, the new US CCN key is assigned to the segment's CCN field, and the updated segment is stored back in the array
[Update All Segment Arrays]
Segment array processing is performed for S01, S02, S03, S04, S05, S06, S08, S10, S11, S12, S13, and S14 segments → For each non-empty segment in each array type, the new US CCN key is assigned to the segment's CCN field, and equipment initialization and compression data are set for S05 segments
[Set New US CCN Key in Primary Segments]
Primary segment keys need to be updated → The new US CCN key is assigned to RT071, RT072, RT073 index segments and the main US CCN key field
[Set Waybill Information in Segments]
Waybill data needs to be propagated to segments → The waybill number is assigned to RT072 and RT073 waybill index fields, the first 15 characters are assigned to RT082 root key, car sequence is set to '01', and waybill date is assigned to RT082 waybill date field
[Process Segment Arrays S03, S06, S07, S08, S12]
Each segment array is processed for CCN key updates → For each non-empty segment (not spaces or low-values), if the segment is not marked as empty, the new US CCN key is assigned to the segment's CCN key field
[Process Individual Segments S01, S02, S04, S05, S10, S11, S13, S14]
Each individual segment is checked for activity → For each segment that is not marked as empty, the new US CCN key is assigned to the segment's CCN key field
[Set Equipment Data in S05 Segment]
Equipment information needs to be set in the S05 segment → Car ID initialization code is assigned to VID02 equipment init field and car ID number is assigned to VID03 equipment number field
[Process Broker Notifications - X12 EDI]
The broker's use-X12 flag is set to 'Y' → Set notify-broker flag, populate X12 broker header information, and call GCCS309C with the CCN key
[Process Broker Notifications - Internet]
The broker's use-Internet flag is set to 'Y' → Initialize GCX019 input with CCN, security byte, and internet address from B1 table, then spawn GCT0191E print process
[Set Default SCAC Codes]
SCAC codes are being set → CPRS SCAC code is assigned to M1112 SCAC-1, M1001 SCAC code, M1301 SCAC code 1, and M1309 SCAC code 2 fields
[Process Segment Arrays]
Segment array processing occurs → For each non-empty segment in arrays S03, S06, S07, S08, S09, S12, the new US CCN key is assigned to the segment's CCN key field, and for border/export bill types with IT export or export transit, line release numbers and quantities are cleared
[Propagate CCN Keys]
CCN key propagation occurs → For all non-empty segments (S01, S02, S04, S05, S10, S11, S13, S14), the new US CCN key is assigned to the segment's CCN key field, and for S05 segments, compressed equipment initial and number are also assigned
[Assign Tax Number to US Manifest M1209 Field]
Tax number assignment is performed → The CPRS tax number from TX table segment is moved to M1209-REF-NUM field
[Set SCAC Code to CPRS]
The system sets the SCAC code values → Both M1301 SCAC Code 1 and M1309 SCAC Code 2 fields are set to 'CPRS'
[Loop Through Routing Junctions GCSUSS13-RT-INDEX 1 to 10]
Junction analysis is performed for Mexico destinations → System loops through junction entries from index 1 to 10 or until a valid junction is found
[Lookup SD Table with Junction Code]
SD table lookup is performed using table ID 'SD' and junction code as sequence ID → System retrieves SD table segment if junction code exists in the table
[Extract Port Code from SD Segment]
Port information is extracted → Port code is extracted from SD segment port code field for DS table lookup
[Update M1203 Location ID and Re-entry Code]
Cargo manifest location data is updated → M1203 location ID field and working re-entry code are set to the extracted port code
[Lookup DS Table with Port Code]
DS table lookup is performed using table ID 'DS' and port code as sequence ID → System retrieves DS table segment if port code exists in the table
[Extract Port Name from DS Segment]
Port name information is extracted → Port name is extracted from DS segment name field
[Update M1203 Location Name and Re-entry Name]
Cargo manifest location name data is updated → M1203 location name field and working re-entry name are set to the extracted port name
[Process S07 Segment Array]
Processing S07 segments and the segment data is not empty or low-values → Update the CCN key in each S07 segment and clear line release numbers and quantities for border export or export transit operations
[Process S08 Segment Array]
Processing S08 segments and the segment data is not empty or low-values → Update the CCN key in each S08 segment
[Process S03 Segment Array]
Processing S03 segments and the segment data is not empty or low-values → Update the CCN key in each S03 segment
[Process S06 Segment Array]
Processing S06 segments and the segment data is not empty or low-values → Update the CCN key in each S06 segment
[Process S12 Segment Array]
Processing S12 segments and the segment data is not empty or low-values → Update the CCN key in each S12 segment
[Update Single Segments S01, S02, S04, S05, S10, S11, S13, S14]
Processing individual segments and the segment data is not empty → Update the CCN key in each individual segment including equipment initialization and number for S05 segment
[Clear Line Release for Export Operations]
The bill type is border export with IT export flag or export bill type with export transit flag → Clear the line release numbers and quantities in the N1009 and N1001 segments

Structural Validations

[Canadian New Bill Creation]
The sequence counter is less than 50 → The system should set error message to 'CAN NOT CREATE NEW CCN' and call error handling
[US Cargo Diversion]
The SCAC code is not CPRS or EDI is not sent electronically or broker is unknown/not required or diversion location already exists → The system should skip diversion processing and continue to location update
[US Cargo Diversion]
The system looks up broker information using broker short name and border code → If broker is not found, the system should set cargo error status and create invalid broker message, otherwise update broker office code information
[Canadian Broker Notification]
The broker delivery schedule is not default delivery or immediate delivery → The system should skip broker notification processing
[Invalid Input Error]
The cargo is neither Canadian nor US type, or the operation type is not recognized for the cargo type → An error message 'GCX101 INVALID INPUT' is set and error handling is invoked
[Error: Cannot Create New CCN]
The sequence counter becomes less than 50 → The system sets error message 'CAN NOT CREATE NEW CCN' and calls error handler CERR
[Lookup Border Table for US Port Code]
Looking up border information in MC table → If border is found, US port of exit code is set from table; if not found, error message 'BORDER NOT FOUND' is set and CERR is called
[Error: Cannot Create New CCN]
The sequence counter falls below 50 → Terminate CCN creation process and generate error message 'CAN NOT CREATE NEW CCN'
[Error: Border Not Found]
Border information is required but not found → An error message 'BORDER NOT FOUND' is set in CC-ERROR-MESSAGE and the error handling routine CERR is called
[Is EDI Sent Electronically?]
The system checks if EDI has been sent electronically → If EDI has not been sent electronically, skip diversion processing and proceed to border name determination
[Is Broker Known and Required?]
The system checks the broker status → If broker is unknown or not required, skip diversion processing and proceed to border name determination
[Has Location ID?]
The system checks for existing diversion location → If diversion location already exists, skip diversion processing and proceed to border name determination
[Is EDI Sent Electronically?]
The system checks if EDI has been sent electronically → Processing continues only if EDI was sent electronically, otherwise diversion processing is skipped
[Is Broker Known and Required?]
The system checks broker status → Processing continues only if broker is not unknown and not marked as not required, otherwise diversion processing is skipped
[Is M1203 Location Empty?]
The system checks the M1203 location field → Processing continues only if M1203 location is empty, otherwise diversion processing is skipped
[Generate New CPRS CCN Number]
Attempting to generate new US CCN → The system should generate error message 'NEW CPRS NUMBER CREATION FAILED' and terminate processing
[C220: Read All US Cargo Data]
Attempting to read cargo data for copying → The system should Throw error: with the CCN and terminate processing
[Assign Default Quantity & Weight Values]
Setting up new manifest data → The system should set default weight to '00001000' in both detail and manifest segments
[7142: Set Up Bonding Data for IT-EXPORT]
Looking up CPRS tax number → The system should generate error message 'TX TABLE RECORD NOT FOUND' and terminate processing
[8530: Insert New US Cargo Record]
Attempting to create new US cargo record → The system should generate error message with return code and error details, then terminate processing
[Counter Table Found?]
The counter table access fails (return flag is not '0') → An error message 'NEW CPRS NUMBER CREATION FAILED' is set and the error handling routine is called
[Counter Update Successful?]
The system checks the update result → If the update failed, an error message 'NEW CPRS NUMBER CREATION FAILED' is set and error handling is invoked
[Update All Segment Arrays with New CCN]
Segment arrays are being updated with new CCN → The new US CCN key is assigned to the S01 segment key field
[Update All Segment Arrays with New CCN]
Segment arrays are being updated with new CCN → The new US CCN key is assigned to the S02 segment key field
[Update All Segment Arrays with New CCN]
Segment arrays are being updated with new CCN → The new US CCN key is assigned to the S04 segment key field
[Set Equipment Information in S05]
Equipment information is being set in S05 segment → The new US CCN key is assigned to S05 segment key, car ID initial portion is assigned to equipment initial field, and car ID number portion is assigned to equipment number field
[Update S10-S14 Segments]
These segments are being updated with new CCN → For each non-empty segment among S10, S11, S13, and S14, the new US CCN key is assigned to the respective segment key field
[Error: Tax Table Not Found]
The tax table lookup fails to return successful results → The system generates error message 'TX TABLE RECORD NOT FOUND' and calls error handling
[Weight is Numeric?]
The system attempts to calculate value from weight → The system should verify that the weight field contains numeric data before proceeding with calculation
[Re-Entry Port Found?]
The port information is not found in the SK table → The system initializes an empty SK segment with default values
[Skip - Invalid Broker]
The system cannot locate the broker in either specific port or default port lookup → The system creates an invalid broker error message, sets cargo status to reject, and updates the cargo record
[Delivery Schedule Valid?]
The broker's delivery schedule is checked → The system only proceeds with notification if the delivery schedule is 'DEFAULT-DELIVERY' or 'IMMEDIATE-DELIVERY'
[Secondary Schedule Valid?]
The secondary broker's delivery schedule is checked → The system only proceeds with secondary notification if the delivery schedule is 'DEFAULT-DELIVERY' or 'IMMEDIATE-DELIVERY'
[Delivery Schedule Valid?]
The broker's delivery schedule is checked → The system only continues processing if the delivery schedule is set to DEFAULT-DELIVERY or IMMEDIATE-DELIVERY, otherwise it exits the procedure
[Build Error Message]
An error message needs to be constructed for the audit trail → The system concatenates 'DIVERTED TO INVALID BROKER AT ' with the border crossing name (GCX101-BORDER-NAME) and stores it in the audit message (GCX105-MESSAGE)
[Invalid Broker at Border]
The system needs to create an error message for invalid broker → The system constructs a message 'DIVERTED TO INVALID BROKER AT [border-name]' AND sets the cargo status to error AND spawns an audit trail message
[Format Message Components]
The system builds audit or error messages → The system formats CCN information, location names, and action codes according to standard message templates AND ensures proper spacing and delimiters
[Parse CCN Structure]
The system processes CCN structure for compression and validation → The system moves CCN type to work area, moves carrier code to work area, moves equipment indicator to work area, assigns equipment ID and waybill date to work areas, and sets sequence counter for processing
[Border Code Available?]
The system needs to resolve location names → The system checks if border code is not spaces or low-values before proceeding with table lookup operations
[STRING 'DIVERTED TO INVALID BROKER AT ' + BORDER-NAME]
The system cannot find valid broker information for the diversion location → Construct an error message by concatenating 'DIVERTED TO INVALID BROKER AT ' + border name and store it in the message field
[Delivery Schedule Valid?]
The broker's delivery schedule is either DEFAULT-DELIVERY or IMMEDIATE-DELIVERY → Continue with notification processing, otherwise exit without sending notifications
[Broker Found?]
The system checks if broker information was found → If broker information is not found, the system initializes an empty broker segment and skips broker notification
[Schedule = DEFAULT-DELIVERY or IMMEDIATE-DELIVERY?]
The system validates the delivery schedule → If the delivery schedule equals DEFAULT-DELIVERY or IMMEDIATE-DELIVERY, validation passes and broker notification continues, otherwise validation fails and broker notification is skipped
[Create Error Message for Canada]
No valid broker configuration is found for the cargo → The system should create diverted to invalid broker audit message and set cargo status to reject
[Broker Found?]
The system checks if broker information was found → If broker not found, initialize empty broker segment and exit processing
[Error: CCN Creation Failed]
CCN generation fails due to table access issues → An error message 'NEW CPRS NUMBER CREATION FAILED' is set and error handling is invoked
[Error: Counter Creation Failed]
The error condition is detected → An error message 'NEW CPRS NUMBER CREATION FAILED' is set and error handling is invoked to terminate the process
[Copy Border Crossing Data]
The system looks up the border name in the MC table → If the border is found in the table, the US port exit code is copied from the MC segment, otherwise an error 'BORDER NOT FOUND' is generated
[S07 Segment Empty or Low-Values?]
The segment data equals spaces or low-values → Skip processing this segment and move to next segment
[Error: TX Table Not Found]
The TX table record is not found → An error message 'TX TABLE RECORD NOT FOUND' should be generated and error handling should be invoked
[Broker Validation Result?]
The broker lookup fails for the combination of broker name and border code in the broker table → The cargo status is set to reject AND an invalid broker error message is created
[Load Broker Segment Data]
The system checks the broker delivery schedule → Continue processing only if delivery schedule is DEFAULT-DELIVERY or IMMEDIATE-DELIVERY, otherwise exit
[Invalid Broker at Border Crossing]
The broker table lookup returns a not found status for the broker-border combination → Set cargo status to CPCARGO-ERROR, generate error message indicating invalid broker at border location, and spawn audit log entry
[Sequence Counter Exhausted]
The sequence counter decrements below 50 without successfully creating a unique CCN → Return error message 'CAN NOT CREATE NEW CCN' and terminate the creation process
[CCN Not Found Error]
The database lookup returns a status indicating the CCN was not found → Generate error message 'CCN NOT FOUND' and call error handler to terminate processing
[Insert/Update Operation Failed]
The operation returns an error status with error number and message → Format comprehensive error message including operation type, error code, and error description, then call error handler
[Delivery Schedule Allows Default/Immediate?]
The broker delivery schedule is not DEFAULT-DELIVERY and not IMMEDIATE-DELIVERY → Skip secondary broker notification processing and continue to completion
[Delivery Schedule = DEFAULT or IMMEDIATE?]
System checks broker delivery schedule setting → Broker notification proceeds only if delivery schedule is DEFAULT-DELIVERY or IMMEDIATE-DELIVERY, otherwise notification is skipped
[Schedule Allows Default or Immediate Delivery?]
The broker delivery schedule is either 'DEFAULT-DELIVERY' or 'IMMEDIATE-DELIVERY' → Proceed with broker notification process
[Is EDI Sent Electronically?]
The system checks the EDI transmission status → Processing continues only if EDI has been sent electronically, otherwise normal processing continues
[Is Broker Unknown or Not Required?]
The system checks the broker status → Processing continues only if broker is not unknown and is required, otherwise normal processing continues
[Is M1203 Location Empty?]
The system checks for existing diversion location in M1203 field → Diversion processing continues only if M1203 location is empty, otherwise normal processing continues
[Junction Found in Routing Table?]
A junction from GCSUSS13 routing segment matches a value in the Rule 260 table → The system sets the junction found flag to true and captures the junction and rail information
[SD Table Entry Found?]
The table lookup operation completes → The system checks if the return flag indicates successful retrieval of SD segment data
[DS Table Entry Found?]
The table lookup operation completes → The system checks if the return flag indicates successful retrieval and logs appropriate messages for found or not found conditions
[Delivery Schedule Valid?]
The broker delivery schedule is 'DEFAULT-DELIVERY' or 'IMMEDIATE-DELIVERY' → Continue with notification processing, otherwise skip broker notifications
[Delivery Schedule Valid?]
The broker's delivery schedule is either 'DEFAULT-DELIVERY' or 'IMMEDIATE-DELIVERY' → The system continues with the notification process, otherwise it exits without sending notifications
[Broker Found in BK Table?]
The system checks if broker information was found → If broker not found, initialize empty broker segment and exit; otherwise load broker configuration
[Schedule Allows Default or Immediate?]
The broker delivery schedule is checked → The system should only proceed with notification processing if delivery schedule equals DEFAULT-DELIVERY or IMMEDIATE-DELIVERY, otherwise exit broker processing
[Schedule = DEFAULT-DELIVERY or IMMEDIATE-DELIVERY?]
The system checks the broker delivery schedule value → The system allows broker notification to continue if schedule equals DEFAULT-DELIVERY or IMMEDIATE-DELIVERY, otherwise skips broker notification
[Delivery Schedule Valid?]
The broker delivery schedule is 'DEFAULT-DELIVERY' or 'IMMEDIATE-DELIVERY' → Continue with notification processing, otherwise skip notifications
[Delivery Schedule Valid?]
The system checks the broker's delivery schedule → The system should only proceed with notifications if the delivery schedule is 'DEFAULT-DELIVERY' or 'IMMEDIATE-DELIVERY', otherwise exit notification processing
[Error: Counter Table Access Failed]
The table access return flag is not '0' → The system should set error message 'NEW CPRS NUMBER CREATION FAILED' and call error handling
[Schedule Allows Default or Immediate Delivery?]
The broker's delivery schedule is not 'DEFAULT-DELIVERY' or 'IMMEDIATE-DELIVERY' → Skip broker notification processing and proceed to secondary broker check
[Set Default Harmonized Code to '999999']
The harmonized commodity code field is spaces, low-values, or contains the value '999999' → The system sets the harmonized commodity code to '999999' as the default value
[Is Quantity Missing or Zero?]
The quantity field (GCUS-N1001-QUANTITY) is either spaces or all zeroes → The system sets the quantity to default value '000000000000001' in the N1001 segment and '000001' in the M1103 segment
[Error: TX Table Record Not Found]
TX table record is not found (return flag is not SUCCESSFUL) → System sets error message 'TX TABLE RECORD NOT FOUND' and calls error handler

As an EDI Gateway Service,
I want to orchestrate and execute all GCX140 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 Secondary Segment as Empty]
The system needs to handle the missing segment → The GCSCCS52 segment is initialized with spaces to ensure processing can continue
[Initialize Report Data]
The report building process starts → The system sets sequence number to '00001' and initializes all report data fields to spaces
[Initialize Key Values and Flags]
The system prepares for broker table lookup → All key values, flags, and broker segment data are cleared and initialized to ensure clean validation state
[Initialize Database Access Parameters]
The system initializes database access parameters → The system sets move underscore to no operation, function to get unqualified, index to not used, and all segments flag to true for the first segment
[Initialize GCCUSIO2 Parameters]
Database access parameters are being configured → The system sets move underscore to no operation, function to get unique, index to not used, and all segments flag to true
[Initialize Report Data]
The report building process starts → The report data structure should be initialized with sequence number '00001' and cleared report data fields
[Initialize Transmission Report Data]
The notification process begins → The transmission sequence number is set to '00001' and the report data structure is initialized to spaces
[Initialize Key Fields]
Key field initialization is performed → All key values, PCB flags, and SSA flags are cleared to spaces to ensure clean table access
[Initialize Transmission Data]
The system begins transmission record creation process → The transmission sequence number is set to '00001' and all report data fields are cleared to spaces

Core Acceptance Criteria

[Security Valid?]
The security byte is evaluated → Processing continues only if security byte equals HIGH-VALUES, otherwise the process terminates
[2:Special Action Processing]
The action code equals 'XXX' → The system sets up notification parameters with car ID and country code, calls GCCSNOT3 service, and terminates processing
[3:Canadian Cargo Data Retrieval]
The system attempts to retrieve cargo report segment → The cargo data is successfully retrieved or an error 'CCN NOT FOUND' is generated for respawn processing
[13:US Cargo Data Retrieval]
The system attempts to retrieve US cargo data → All cargo segments are successfully retrieved or an error message is generated for respawn processing
[15:US Broker Information Retrieval]
Broker information is requested → The system retrieves broker details from the broker name segment
[23:Transmission Number Generation]
Transmission number generation is requested → The system retrieves current transmission number from table ID '11', increments it by 1, updates the stored value, and uses the new number for the transmission
[Call READQ to Read Incoming Message]
The system attempts to read the message using READQ function → The message content is retrieved and stored in GCX140-INPUT structure with INPUT-MESSAGE-LENGTH
[Check Action Code]
The action code equals 'XXX' → The system should extract the car identification number and country code from the message and proceed with special notification processing
[Extract Car ID from Message]
Car identification needs to be extracted → The system should move the US CCN value from the input message to the notification car ID field
[Extract Country Code from Message]
Country code needs to be extracted → The system should move the CA-US value from the input message to the notification country field
[Continue Normal Processing]
The action code != 'XXX' → The system should proceed with the normal processing flow for the given action
[Set CCN Key from Input Message]
The system processes Canadian cargo data retrieval → The US-CCN from the input message is assigned as the CCN key for cargo report lookup
[Retrieve Primary Cargo Report Segment]
The system attempts to retrieve the primary cargo report segment → The system calls the database with 'GE' acceptance status to get the cargo report segment using the CCN key
[Set Additional Segment Parameters]
The system prepares to retrieve additional segment information → The CCN key is assigned to A2RT-KEY-CCN, segment ID is set to '52', and segment sequence is set to '0001'
[Retrieve Secondary Segment GCSCCS52]
The system attempts to retrieve the GCSCCS52 segment → The system calls the database with 'GE' acceptance status to get the secondary segment using the A2RT parameters
[Secondary Segment Found?]
If the database operation result → If the status code is spaces (successful), continue with the retrieved segment, otherwise initialize the segment as empty
[Set CCN Key from Input Message]
The system processes the cargo report retrieval request → The CCN key is set from the input message US CCN field for database lookup
[Set Segment ID to '52' and Sequence to '0001']
The system prepares to access the cargo report database → The segment ID is set to '52' and segment sequence is set to '0001' to identify the primary cargo report segment
[Retrieve Primary Cargo Report Segment]
The system executes the cargo report segment retrieval → The system attempts to fetch the cargo report segment from the GCCC-CARGO-REPORT-SEGMENT data source
[Retrieve Additional Segment GCSCCS52]
The system processes additional cargo data requirements → The system attempts to retrieve the GCSCCS52 additional segment from the GCA2 database
[Clear Additional Segment Data]
The system handles the missing additional segment → The GCSCCS52 data structure is cleared to SPACES to ensure clean data state
[Set Segment Parameters]
The system needs to retrieve secondary segment GCSCCS52 with segment ID '52' and sequence '0001' → The system should set up the segment parameters with CCN key, segment ID '52', and segment sequence '0001' for database retrieval
[Call Database for GCSCCS52]
The system executes the database call for GCSCCS52 segment → The system should Execute a database query using CIMS with GU operation on GCA2-PCB to retrieve the segment data
[Segment Found?]
The system checks the database operation status → If the status code is SPACES, the segment was found successfully, otherwise the segment was not found
[Use Retrieved Segment Data]
The segment data is available for processing → The system should continue with the retrieved segment data intact for subsequent business logic processing
[Clear Segment Data]
The segment is not found in the database → The system should clear the GCSCCS52 segment data area by moving SPACES to it
[Extract Notify Party Name from Cargo Data]
Processing notify party report for Canadian cargo → The notify party name is extracted from GCCC-NOTIFY-PRT-NAME field
[Retrieve Broker Information for Notify Party]
System needs broker information for the notify party → Broker details are retrieved from GCT2 broker name segment using GCCUSIO call
[Build Transmission Report with Notify Party Details]
Building transmission report for notify party → Report data structure is initialized and populated with notify party details including consignee name, broker name, border and destination information
[Set Equipment and CCN Information]
Building notify party transmission report → Equipment ID is set from GCCC-EQUIPMENT-ID-FOR-INDEX and CCN is set from GCCC-CCN-KEY or master manifest CCN if follower manifest
[Apply Machine Date and Time Stamps]
Date and time information needs to be recorded → Machine time is applied to GCTM-TIME and machine date with century is applied to GCTM-DATE
[Set Sequence Number for Report Type]
Setting sequence number for the transmission → Sequence number is set to 'CCRGO' for actions ADD, UPD, DEL, or ARR, otherwise set to 'CCTRN'
[Create Transmission Root Record]
Creating the transmission record → Root transmission segment is inserted into the database using CIMS call
[Create Department Record]
Creating the department record for notify party → Department segment is inserted into the database using CIMS call
[Retrieve Broker Information for Consignee]
Processing consignee report → GCCUSIO program is called to retrieve broker information from broker name segment
[Build Consignee Transmission Report]
Building transmission report → Report data is initialized and consignee name is moved to shipper field in transmission report
[Set Equipment and CCN Details]
Building transmission report → Equipment ID is moved to car number field and appropriate CCN is moved to CCN field based on follower manifest status
[Apply Machine Date and Time Stamps]
Building transmission report → Machine time is moved to report time field and machine date with century is formatted and moved to report date field
[Get Transmission Number]
Getting transmission number → Current transmission number is retrieved, incremented by 1, and updated back to the table segment
[Create Transmission Root Record]
Creating transmission root record → CIMS program is called with ISRT function to insert transmission segment
[Create Department Record]
Creating department record → CIMS program is called with ISRT function to insert dependent segment
[Set Segment Type to GCST2RT]
The system sets up database access parameters → The segment type is set to GCST2RT for broker name segment retrieval
[Call GCCUSIO to Get Broker Details]
The system executes the broker information retrieval → The GCCUSIO program is called with the communication area, working storage parameters, and broker name segment
[Retrieve Broker Name Segment]
The system processes the retrieved broker data → The Canadian report building process is performed using the broker information
[Set Equipment Car Number]
Building the transmission report → The system copies the equipment ID for index to the car number field in the report
[Set Broker Information]
Building the transmission report → The system sets broker name, manifest from station name as border, and manifest to station name as destination
[Apply Machine Date and Time Stamps]
Date and time information is needed → The system uses machine time for time field and combines machine century and date for the date field
[Determine Sequence Number Type]
The action code is ADD, UPD, DEL, or ARR → The system sets sequence number to 'CCRGO', otherwise sets it to 'CCTRN'
[Generate Transmission Number]
Generating the transmission number → The system retrieves the current transmission number from table segment 11, increments it by 1, and updates the table
[Create Transmission Root Record]
Creating the transmission record → The system inserts the transmission segment as a root record using the transmission PCB
[Create Transmission Department Record]
Creating the department record → The system inserts the dependent segment as a department record using the transmission PCB
[Set US Port Code]
Transport type is immediate transport or transport export → Use destination location ID, otherwise use origin port location ID
[Get Transmission Number]
Obtaining transmission tracking number → The system retrieves the current transmission number from the broker table, increments it by 1, and assigns it to the notification
[Create Transmission Root Record]
Creating the transmission record → A transmission root record is inserted into the transmission database with all the prepared notification data
[Create Transmission Department Record]
Creating the associated department record → A transmission department record is inserted as a dependent record linked to the root transmission record
[Generate Transmission Number]
Transmission number is required → The system should retrieve and increment the transmission number from table segment 11
[Create Transmission Root Record]
Transmission records need to be created → The system should create transmission root record and transmission department record in the database
[Generate Transmission Number for Haulage]
Haulage transmission records need to be created → The system should generate transmission number and create transmission root and department records
[Check Reference Number 1-10 for OB Qualifier]
The system needs to extract the Ocean Bill of Lading number → The system searches positions 1-10 sequentially for qualifier 'OB' and uses the first match found, stopping immediately when found
[Check Reference Number 1-10 for BM Qualifier]
The system searches for Ocean Bill of Lading number using fallback logic → The system searches positions 1-10 sequentially for qualifier 'BM' and uses the first match found, stopping immediately when found
[Get Transmission Number]
Creating the transmission records → A transmission number is obtained from the broker table segment and assigned to the notification
[Create Transmission Root Record]
Creating the database records → A transmission root record is inserted into the transmission database
[Create Department Record]
Completing the database record creation → A department record is inserted into the transmission database
[Determine Location Based on Bond Type]
Determining location for broker notification → If bond type is immediate transport or transport export, use M1203 location ID1 in positions 15-18, otherwise use P401 location ID in positions 15-18
[Get Transmission Number]
Generating transmission number → Retrieve and increment the transmission number from table segment 11
[Create Transmission Root Record]
Creating transmission records → Insert the transmission root segment using the prepared transmission data
[Create Transmission Department Record]
Creating department transmission record → Insert the transmission department segment as a dependent record
[Set Shipper Information]
Building the border notification report → The system should copy the consignee name (GCUS-N102-NAME) to the shipper field (GCTM-SHIPPER) in the transmission report
[Set Equipment Car Number]
Building the border notification report → The system should copy the equipment car number (GCUSRT-RT081-EQUIPMENT-CAR) to the car number field (GCTM-CAR-NUM) in the transmission report
[Set CCN Key]
Building the border notification report → The system should copy the first 16 characters of the US CCN key (GCUSRT-US-CCN-KEY) to the CCN field (GCTM-CCN) in the transmission report
[Set Broker Name]
Building the border notification report → The system should copy the broker short name (GCUSRT-RT01-BROKER-SHORT-NAME) to the broker field (GCTM-BROKER) in the transmission report
[Build Broker Report Notification]
Building the notification identifier → The system should set spaces to GCTM-BK-NOTIFY, set 'BKRPT=' to positions 1-6, set filer code (GCUSRT-RT02-FILER-CDE) to positions 7-9, and if transport type is immediate transport (88-GCUSRT-M1201-IMM-TRANSP) or transport export (88-GCUSRT-M1201-TRANSP-EXPORT) then set destination location ID (GCUSRT-M1203-LOCATION-ID1) to positions 15-18, otherwise set origin location ID (GCUSRT-P401-LOCATION-ID) to positions 15-18
[Build Haulage Rights Notification]
Building the notification identifier → The system should set spaces to GCTM-BK-NOTIFY, set 'HAUL=' to positions 1-5, set haulage rights SCAC (GCUSRT-HAULAGE-RIGHTS-SCAC) to positions 6-9, and if transport type is immediate transport (88-GCUSRT-M1201-IMM-TRANSP) or transport export (88-GCUSRT-M1201-TRANSP-EXPORT) then set destination location ID (GCUSRT-M1203-LOCATION-ID1) to positions 15-18, otherwise set origin location ID (GCUSRT-P401-LOCATION-ID) to positions 15-18
[Get Transmission Number]
Assigning a transmission number → The system should Execute get transmission number process (D100-GET-TRANS-NUMBER) and copy the transmission number (GCSTBRT-11-TRANSMISSION-NUM) to the transmission number field (GCTM-TRANSMISSION-NUMBER), and set spaces to the read and delete flag (GCTM-READ-AND-DELETE-FLAG)
[Create Transmission Records]
Creating the transmission records → The system should set spaces to accept status, Execute create transmission root process (Z100-CREAT-TRANS-ROOT), set spaces to accept status again, and Execute create transmission dependent process (Z200-CREAT-TRANS-DEPT)
[Determine Location Code]
Determining location for haulage notification → If bond type is immediate transport or transport export, use destination location code, otherwise use border location code
[Use Destination Location]
Setting location code for haulage notification → Destination location ID is assigned to positions 15-18 of the notification code
[Use Border Location]
Setting location code for haulage notification → Border location ID is assigned to positions 15-18 of the notification code
[Broker Valid?]
Processing validation results → If broker validation is not successful, end haulage notification processing, otherwise continue with transmission generation
[Get Transmission Number]
Preparing to create haulage notification transmission → Transmission number generation service is called to obtain unique identifier
[Create Transmission Root Record]
Creating haulage notification transmission → Transmission root record creation service is called to establish the main notification record
[Create Department Record]
Completing haulage notification transmission → Department record creation service is called to establish the departmental notification record
[Set Broker Notification Key as Sequence ID]
The system prepares to lookup broker information → The broker notification key should be assigned as the sequence ID for table lookup
[Call Table Segment Retrieval]
The system calls the table segment retrieval function → The system should attempt to retrieve the broker record from the broker table
[Load Broker Segment Data]
The system processes the successful lookup result → The broker segment data should be loaded from the table segment into the broker record structure
[Set Consignee as Shipper]
The system populates the shipper information → The consignee name from the cargo manifest is copied to the shipper field in the transmission report
[Set Equipment Car Number]
The system populates equipment information → The equipment ID for index from the cargo data is copied to the car number field in the transmission report
[Set CCN Key]
The system sets the cargo control number → The CCN key from the cargo data is copied to the CCN field in the transmission report
[Set Broker Name]
The system populates broker information → The broker name from the cargo data is copied to the broker field in the transmission report
[Action Type Check]
If the action type → If action is 'OFT', set train status to 'REMOVED FROM TRAIN' with spaces for train date; if action is 'ONT', set train status to 'ON TRAIN' with train ID and spaces for train date; for other actions (ADD/UPD/DEL/ARR), set corresponding status messages
[Set Broker Long Name as Shipper]
The system updates the shipper information → Copy the broker long name from the broker table segment to the shipper field in the transmission report
[Get Transmission Number]
The system generates the transmission number → Retrieve the current transmission number from the broker table segment, increment it by 1, and assign it to the transmission report
[Create Transmission Root Record]
The system creates the database records → Insert the transmission segment as a root record in the transmission database
[Create Transmission Department Record]
The system creates the dependent records → Insert the transmission dependent segment as a department record linked to the root transmission record
[Build Key: 'BKRPT=' + Filer Code + Location Code]
The system builds the broker notification key → The key is constructed with 'BKRPT=' prefix in positions 1-6, filer code in positions 7-9, and location code in positions 15-18 determined by bond type (destination location for immediate transport/transport export, otherwise origin location)
[Build Key: 'HAUL=' + Haulage Rights SCAC + Location Code]
The system builds the broker notification key → The key is constructed with 'HAUL=' prefix in positions 1-5, haulage rights SCAC in positions 6-9, and location code in positions 15-18 determined by bond type (destination location for immediate transport/transport export, otherwise origin location)
[Determine Location Code Based on Bond Type]
The system determines the location code → If bond type is immediate transport or transport export, use destination location code, otherwise use origin location code
[Call Broker Table Lookup]
The system calls the table lookup function Z300-GET-TABLE-SEGMENT → The system should attempt to retrieve the broker segment from the broker table
[Load Broker Segment Data]
The lookup returns successful status indicating broker was found → The system should load the retrieved table segment data into the broker segment structure (GCSTBRT-BK-SEGMENT)
[Keep Return Flag as Not Found]
The lookup returns unsuccessful status indicating broker was not found → The system should keep the return flag as not successful without loading any broker segment data
[Set Consignee Name as Shipper]
The system populates shipper information → Set the consignee name from cargo data as the shipper in the transmission report
[Set Equipment Car Number]
The system populates equipment information → Set the equipment ID for index from cargo data as the car number in the transmission report
[Set CCN Key]
The system populates cargo control information → Set the CCN key from cargo data as the CCN in the transmission report
[Clear Bond Type and Number]
The system populates bond information → Set both bond type and bond number fields to spaces in the transmission report
[Set Broker Name]
The system populates broker information → Set the broker name from cargo data as the broker in the transmission report
[Set Border and Destination Stations]
The system populates location information → Set the manifest from station name as border and manifest to station name as destination in the transmission report
[Set Broker Long Name as Shipper]
The system assigns broker information → Set the broker long name from broker table as the shipper in the transmission report
[Generate Transmission Number]
The system generates transmission number → Retrieve and increment transmission number from table segment 11, then assign the incremented number to the transmission report
[Create Transmission Root Record]
The system creates transmission records → Clear read and delete flag, set accept status to spaces, and create transmission root record using transmission segment
[Create Transmission Department Record]
The system creates department record → Set accept status to spaces and create transmission department record using dependent segment
[Use US Location Based on Bond Type]
The system determines the location code → The location selection depends on whether it is immediate transport or transport export
[Use M1203 Location ID]
The system selects the location for haulage rights notification → The M1203 destination location ID is used in the notification key
[Use P401 Location ID]
The system selects the location for haulage rights notification → The P401 origin location ID is used in the notification key
[Clear Return Flag and Broker Segment]
The system prepares validation parameters → The return flag is cleared and broker segment data is initialized to spaces
[Call Table Segment Retrieval]
The system needs to validate the broker code → The table segment retrieval function is called to search the broker table
[Load Broker Segment Data]
The system processes the successful lookup result → The broker segment data is loaded from the table segment into working storage
[Set US CCN Key from Input Message]
The system processes the US cargo data retrieval request → The US CCN from the input message is assigned to the cargo record key for database lookup
[Call GCCUSIO2 to Retrieve US Cargo Data]
The system calls the GCCUSIO2 service → The system retrieves US cargo root segment, all related cargo segments (GCSUSS00 through GCSUSS15), and their corresponding working storage arrays
[Move Retrieved Segment Data to Working Storage Arrays]
The system processes the retrieved segment arrays → The first occurrence of segments GCSUSS03, GCSUSS06, GCSUSS07, GCSUSS08, GCSUSS09, and GCSUSS12 are moved from their respective working storage arrays to individual segment areas
[Set US CCN Key from Input Message]
The system prepares to retrieve cargo data → The US CCN key is set from the input message cargo control number
[Call GCCUSIO2 to Retrieve US Cargo]
The system executes the cargo data retrieval → GCCUSIO2 is called with all cargo segments and working storage arrays to retrieve complete cargo information
[Move Retrieved Segment Data to Working Storage Arrays]
The system processes the retrieved data → The first occurrence data from working storage arrays for segments 03, 06, 07, 08, 09, and 12 is moved to the corresponding main segment structures
[Extract US Cargo Segment Data]
The system needs to process shipper information → The first occurrence of cargo segment data (GCSUSS03) should be extracted from the working storage array and made available for processing
[Extract Shipper Name from N102-NAME]
Shipper information needs to be processed for reporting → The shipper name should be extracted from the N102-NAME field and stored in working storage
[Set Target Segment to Broker Name Table]
The system sets the target data segment → The target segment is set to GCST2RT (broker name table segment)
[Move Broker Long Name to Search Key]
The system sets up the search criteria → The working storage broker long name is moved to the search key field
[Call Broker Information Service]
The system executes the broker lookup → The GCCUSIO service is called with communication control, search parameters, and broker name segment
[Retrieve Broker Details from GCT2-BROKER-NAME-SEGMENT]
The system processes the retrieved data → Broker details are available from the GCT2-BROKER-NAME-SEGMENT for subsequent processing
[Set Shipper Information]
Building the transmission report → The shipper name from the US cargo segment should be copied to the transmission report shipper field
[Set Equipment Car Number]
Building the transmission report → The equipment car number should be copied from US cargo data to the transmission report car number field
[Follower Manifest?]
The manifest type needs to be determined → If it is a follower manifest, use the lead manifest CCN; otherwise use the original US CCN key
[Set Bond Type and Number]
Building the transmission report → Set bond type from in-bond type code, and use entry number if available, otherwise use in-bond control number
[Set Bond Owner]
Building the transmission report → The bond owner should be copied from US cargo data to the transmission report
[Set Broker Information]
Building the transmission report → The broker short name should be copied to the transmission report broker field
[Set Border and Destination]
Building the transmission report → Set border from location ID name, and if destination location name is empty, use border location as destination and set port from P401 location ID, otherwise use destination location name and M1203 location ID
[Apply Machine Date/Time]
Date and time information needs to be recorded → Set report time from machine time, and construct report date using machine century, machine date, and machine time
[Report Type = TRAIN?]
The report type has been determined → If report type equals 'TRAIN=', process as train movement; otherwise process as cargo action
[Action Type?]
Setting the sequence number identifier → If action is 'ADD', 'UPD', or 'DEL', use 'CARGO' sequence; otherwise use 'TRAIN' sequence
[Build Broker Notification Key]
Building the broker notification key → Copy broker short name to notification key positions 1-14 and set port code from hold-US-port to positions 15-18
[Set Shipper from Broker Name]
Setting final shipper information → Copy the broker's long name from the validation result to the transmission report shipper field
[Get Transmission Number]
Obtaining a transmission number → Get current transmission number from table segment, increment by 1, update the table, and assign to report transmission number
[Create Transmission Records]
Creating the transmission records → Insert transmission root record and transmission dependent record into the database
[Get In-Bond Type Code from US Cargo Data]
The system processes bond information for a US cargo shipment → The in-bond type code should be retrieved from the US cargo segment and assigned to the bond type field
[Set Bond Owner Information]
The system processes bond details for customs reporting → The bond owner information should be retrieved from the cargo segment and assigned to the bond owner field
[Set Location/Port Code]
Setting location code for notification key → If transport type is immediate transport or transport export, use destination location code, otherwise use origin port location code
[Load Broker Segment Data]
The broker lookup returns successful results → The complete broker segment data is loaded from the table segment into the working storage
[Set Sequence Number: TRAIN]
Setting sequence number for transmission → Set sequence number to 'TRAIN'
[Bond Type Check]
Determining location for broker notification code → If bond type is immediate transport or transport export, use M1203-LOCATION-ID1 for positions 15-18, otherwise use P401-LOCATION-ID for positions 15-18
[Get Transmission Number]
Creating transmission for US broker border notification → Get next transmission number and assign to GCTM-TRANSMISSION-NUMBER
[Create Transmission Root Record]
Creating transmission records for US broker border notification → Clear read and delete flag, set accept status to spaces, and create transmission root record
[Create Transmission Department Record]
Completing transmission records for US broker border notification → Set accept status to spaces and create transmission department record
[US Broker Border Notification]
Building the broker notification code for US broker border notification → The system should set prefix to 'BKRPT=' AND use filer code from US cargo data AND IF bond type is immediate transport OR transport export THEN use final destination port ELSE use border entry port AND create notification code in format: 'BKRPT='[FilerCode][PortCode]
[US Haulage Rights Notification]
Building the broker notification code for US haulage rights notification → The system should set prefix to 'HAUL=' AND use haulage rights SCAC code AND IF bond type is immediate transport OR transport export THEN use final destination port ELSE use border entry port AND create notification code in format: 'HAUL='[SCACCode][PortCode]
[Get Transmission Number]
Getting the transmission number → The system retrieves the current transmission number from table segment '11', increments it by 1, and updates the table segment
[Create Transmission Root Record]
Creating the transmission record → The system inserts the transmission segment as a root record and creates the dependent segment record
[Get Transmission Number]
A transmission number is needed → Get the current transmission number from the broker table and assign it to the report
[Create Transmission Root Record]
Creating the transmission records → Insert the transmission segment as the root record in the transmission database
[Create Transmission Department Record]
Completing the transmission record creation → Insert the transmission dependent segment as a child record in the transmission database
[Set Consignee Name as Shipper]
Building the haulage rights notification report → The consignee name from the cargo record is copied to the transmission report shipper field
[Set Equipment Car Number]
Building the haulage rights notification report → The equipment ID for index is copied to the transmission report car number field
[Set CCN Key]
Building the haulage rights notification report → The CCN key from the cargo record is copied to the transmission report CCN field
[Clear Bond Type and Number]
Setting up the transmission report data → Both bond type and bond number fields are set to spaces
[Set Broker Name]
Building the haulage rights notification report → The broker name from the cargo record is copied to the transmission report broker field
[Apply Machine Date and Time Stamps]
Building the haulage rights notification report → The machine time is copied to the transmission time field and the formatted date (century + date) is constructed and copied to the transmission date field
[Generate Transmission Number]
Generating the transmission → The system calls the transmission number generation process and assigns the generated transmission number to the transmission report
[Create Transmission Root Record]
Creating the transmission records → The system creates a transmission root record with spaces for read and delete flag and blank accept status
[Create Transmission Department Record]
Completing the transmission record creation → The system creates a transmission department record with blank accept status
[Get Transmission Number]
Getting the transmission number → Retrieve and increment the transmission number from the table segment
[Create Transmission Root Record]
Creating the transmission record → Insert the transmission root record into the transmission database
[Create Transmission Department Record]
Creating the department record → Insert the transmission department record into the transmission database
[Set Shipper Name from US Cargo]
Building the broker border notification report → Set the shipper field to the consignee name (GCUS-N102-NAME) from the US cargo segment
[Set Bond Owner]
Building the broker border notification report → Set the bond owner field to the bond owner from routing segment (GCUSRT-RT50-BOND-OWNER)
[Set Location ID Based on Bond Type]
Setting the location ID in the broker notification → If bond type is immediate transport (M1201-IMM-TRANSP) OR transport export (M1201-TRANSP-EXPORT) then use destination location ID (M1203-LOCATION-ID1), otherwise use origin location ID (P401-LOCATION-ID)
[Broker Validation Successful?]
The broker validation is successful → Set the shipper field to the broker long name and proceed with transmission generation
[Get Transmission Number]
Preparing to create the transmission → Execute the D100-GET-TRANS-NUMBER procedure to obtain the transmission number
[Create Transmission Root Record]
Creating the transmission records → Execute the Z100-CREAT-TRANS-ROOT procedure to create the root transmission record
[Create Transmission Department Record]
Completing the transmission record creation → Execute the Z200-CREAT-TRANS-DEPT procedure to create the department transmission record
[Set Shipper Name from US Cargo]
The system builds the haulage rights notification → The shipper name from US cargo segment is assigned to the transmission report shipper field
[Set Equipment Car Number]
The system builds the haulage rights notification → The equipment car number from US cargo segment is assigned to the transmission report car number field
[Set CCN Key]
The system builds the haulage rights notification → The first 16 characters of the US CCN key are assigned to the transmission report CCN field
[Set Bond Owner Information]
The system builds the haulage rights notification → The bond owner from US cargo segment is assigned to the transmission report bond owner field
[Set Broker Short Name]
The system builds the haulage rights notification → The broker short name from US cargo segment is assigned to the transmission report broker field
[Set Vessel Name as Train]
The system processes vessel information → The vessel name from US cargo data is assigned to the transmission report train field
[Use OB Reference Number]
The system assigns the OBL value → The reference number corresponding to the OB qualifier position is assigned to the transmission report OBL field
[Use BM Reference Number]
The system assigns the OBL value → The reference number corresponding to the BM qualifier position is assigned to the transmission report OBL field
[Set Empty OBL]
The system assigns the OBL value → The transmission report OBL field is set to spaces
[Bond Type: Immediate Transport or Transport Export?]
The system determines location for broker notification → If bond type is immediate transport or transport export, destination location ID is used, otherwise border location ID is used
[Use Destination Location ID]
The system sets the location in broker notification → The destination location ID is assigned to positions 15-18 of the broker notification key
[Use Border Location ID]
The system sets the location in broker notification → The border location ID is assigned to positions 15-18 of the broker notification key
[Set Broker Long Name as Shipper]
The system updates shipper information → The broker's long name from the broker table is assigned to the transmission report shipper field
[Get Transmission Number]
The system generates transmission number → A unique transmission number is obtained and assigned to the transmission report
[Create Transmission Root Record]
The system creates the transmission record → The transmission root record is created with all prepared data
[Create Transmission Department Record]
The system creates the department record → The transmission department record is created to complete the notification
[Retrieve Broker Details]
The return flag equals SUCCESSFUL → The system moves the table segment data to the broker segment structure to retrieve broker details
[Set Location Based on Bond Type]
Determining location for haulage rights notification key → If bond type is immediate transport or transport export, use M1203 location ID, otherwise use P401 location ID
[Get Transmission Number]
Preparing to create transmission records → A unique transmission number is generated and assigned to the transmission number field
[Create Transmission Root Record]
Creating transmission records for haulage rights notification → Transmission root record is created with the prepared report data
[Create Transmission Department Record]
Completing transmission record creation for haulage rights notification → Transmission department record is created to complete the notification process
[Use US Location Based on Bond Type]
The bond type is immediate transport or transport export → The M1203 location ID is used as the location code, otherwise P401 location ID is used
[Clear Broker Segment Data]
The system prepares to validate a broker code → All broker segment data fields are cleared to spaces to ensure no residual data affects the validation
[Load Broker Segment Data]
The broker validation is successful → The complete broker segment data is loaded from the table for use in processing
[Retrieve Current Transmission Number from System Table]
The system accesses the system table with table ID '11' and empty sequence ID → The current transmission number is retrieved from the GCSTBRT system table
[Increment Transmission Number by 1]
The transmission number increment operation is performed → The transmission number value is increased by 1
[Update System Table with New Number]
The system performs a replace operation on the system table with table ID '11' → The system table is updated with the new transmission number value
[Return New Transmission Number]
The transmission number generation process completes successfully → The new transmission number is made available for transmission record creation
[Set Function Code to GHU - Get Hold Unique]
The transmission number retrieval process is initiated → The function code is set to GHU (Get Hold Unique) to obtain exclusive access to the transmission number record
[Set Table ID to '11']
Table identification is required → The table ID is set to '11' to identify the transmission number system table
[Set Sequence ID to Spaces]
Sequence identification is required → The sequence ID is set to spaces to access the main transmission number record
[Call Table Segment Retrieval]
Table segment retrieval is executed → The system calls the table I/O routine to retrieve the transmission number segment
[Extract Current Transmission Number]
The current transmission number needs to be accessed → The system moves the table segment data to the transmission number structure to extract the current value
[Increment Transmission Number by 1]
The number needs to be prepared for the next transmission → The system adds 1 to the current transmission number to generate the next sequential number
[Set Function Code to REPL - Replace]
The updated number needs to be saved back to the table → The function code is set to REPL (Replace) to update the existing table record
[Update System Table with New Number]
The table update operation is executed → The system calls the table I/O routine to replace the old transmission number with the new incremented value
[Retrieve Current Transmission Number from Table 11]
The system attempts to retrieve the current transmission number from table 11 with table ID '11' and empty sequence ID → The current transmission number is retrieved from the system table
[Increment Transmission Number by 1]
The number increment operation is performed → Add 1 to the current transmission number value
[Update Table 11 with New Number]
The system performs a replace operation on table 11 with table ID '11' and empty sequence ID → The table segment is updated with the new transmission number
[Set Broker Notification Code as Sequence ID]
Preparing to validate the broker code → The broker notification code (GCTM-BK-NOTIFY) is assigned as the sequence ID for table lookup
[Call Table Segment Retrieval]
The table segment retrieval function is called → The system attempts to retrieve the corresponding broker segment from the broker master table
[Set Accept Status to Blank]
The system prepares to create the transmission root record → The accept status is set to blank spaces (' ')
[Create Transmission Root Record]
The system executes the root record creation → A transmission root record is inserted into the transmission root table using the transmission segment data
[Reset Accept Status to Blank]
The system prepares to create the transmission department record → The accept status is reset to blank spaces (' ')
[Create Transmission Department Record]
The system executes the department record creation → A transmission department record is inserted into the transmission department table using the dependent segment data
[Create Transmission Root Record]
The system needs to create a new transmission root record → The system sets the accept status to blank and inserts the transmission root segment into the database using the transmission PCB and unqualified search arguments
[Insert Department Segment into Database]
The system processes a request to create a transmission department record → The system inserts the department segment into the database using the transmission PCB and department selection criteria
[Set Accept Status to Blank]
The department record creation process begins → The system sets the accept status to blank spaces in the communication control block
[Query MC Table with Destination]
The system performs the table segment retrieval → The system should call the table access routine and return the location data if found
[Retrieve Full Location Name]
The system processes the retrieved table segment → The complete US station exit name (positions 1-18) should be extracted from the MC segment
[Update Destination with Full Name]
The system updates the destination information → The GCTM-DESTINATION field should be updated with the complete US station exit name from positions 1-18 of the MC segment
[Current Notification = Saved Notification?]
The current notification key matches the previously saved notification key → The system skips the duplicate notification processing and exits without creating transmission records
[Save Current Notification]
The current notification key does not match any previously saved notification key → The system saves the current notification key and continues with transmission processing
[Continue with Transmission Processing]
The notification key has been saved for future duplicate checking → The system generates transmission number, creates transmission root record, and creates transmission dependent record
[Current Attempt Count = '1'?]
The attempt counter management process is executed → The attempt count should be incremented to '2' and country code should be set to 'US'
[Current Attempt Count = '2'?]
The attempt counter management process is executed → The attempt count should be incremented to '3' and country code should be set to 'US'
[Reset Attempt Count to '1']
The attempt counter management process is executed → The attempt count should be reset to '1' and country code should be set to 'US'
[Current Attempt Count = '1'?]
The attempt counter management process is executed → The attempt count should be incremented to '2' and country code should be set to 'CA'
[Current Attempt Count = '2'?]
The attempt counter management process is executed → The attempt count should be incremented to '3' and country code should be set to 'CA'
[Reset Attempt Count to '1']
The attempt counter management process is executed → The attempt count should be reset to '1' and country code should be set to 'CA'
[Security Byte = HIGH-VALUES?]
The system checks the security byte field in the message → If the security byte does not equal HIGH-VALUES, the system terminates processing and exits the program without performing any cargo operations
[Continue to Main Processing]
The security byte equals HIGH-VALUES indicating proper authorization → The system continues to main processing by calling A200-MAINLINE to handle cargo operations
[Apply Time to Report Time Field]
The system applies timestamps to the report → The current machine time is copied to the report time field
[Apply Time to Report Date Field Position 2-6]
The system applies date timestamps to the report → The current machine time is copied to positions 2-6 of the report date field
[Apply Century to Report Date Field Position 1-2]
The system applies date timestamps to the report → The current machine century is copied to positions 1-2 of the report date field
[Apply Date to Report Date Field Position 3-6]
The system applies date timestamps to the report → The current machine date is copied to positions 3-6 of the report date field

Structural Validations

[1:Message Reading and Validation]
The system attempts to read the input message → The message is successfully read or an error is reported for further handling
[Message Read Successfully?]
The system checks the return code from the message reading operation → If return code is not zero, the system triggers error handling; if return code is zero, processing continues
[Call Error Handler CERR]
The system detects the failure condition → The system calls the CERR error handler and terminates processing with GOBACK
[Security Byte = HIGH-VALUES?]
The system checks the GCX140-SECURITY-BYTE field in the message → If the security byte equals HIGH-VALUES, processing continues; if not equal to HIGH-VALUES, processing terminates
[Cargo Report Found?]
The system checks the status of the database operation → If the status code is spaces (successful), proceed with secondary segment retrieval, otherwise trigger CCN not found error processing
[Set Error Message: CCN NOT FOUND]
The system needs to communicate the failure reason → The error message 'CCN NOT FOUND' is set in the communication area for error processing
[Trigger Error Processing]
The system needs to handle the error condition → The error processing routine Z900-RESPAWN-GCT1401E is executed to manage the error scenario
[Additional Segment Found?]
If the retrieval result → If the status code is SPACES, the additional segment is available, otherwise it is not available
[Set Error: CCN NOT FOUND]
The system handles the missing cargo report → The error message is set to 'CCN NOT FOUND' to indicate the cargo control number does not exist
[Duplicate Check]
The notification key matches the previously saved notification key → The notification process is terminated without creating transmission records
[Set Error Message with CCN]
The system handles the retrieval error → The system sets an error message containing the US CCN that could not be found and initiates the error respawn process
[Set Error Message with CCN]
The system handles the error condition → The cargo control number is moved to the error CCN field and a predefined error message is set for error processing
[Duplicate Notification?]
Checking for duplicate notifications → If the current broker notification key equals the saved broker notification key, the system skips processing, otherwise it continues with transmission creation
[Duplicate Notification Check]
The current notification key matches the previously saved notification key → Skip the notification process and exit without creating transmission records
[Validate Broker Code]
Validating the broker code → The broker long name is copied to the transmission report shipper field
[Transmission Number Found?]
The system table lookup operation completes → The system checks if the return flag indicates successful retrieval of transmission number record
[Report Missing Transmission Number Error]
The return flag indicates the transmission number record was not found → The system sets error message 'MISSING 11 SEGMENT' and calls error handler
[Update Successful?]
The system table replace operation completes → The system checks if the return flag indicates successful update of the transmission number record
[Report Update Failed Error]
The return flag indicates the update was not successful → The system sets error message 'REPLACE 11 SEGMENT FAILED' and calls error handler
[Transmission Number Found?]
The retrieval operation completes → The system checks if the return flag indicates successful retrieval of the transmission number segment
[Update Successful?]
The update operation completes → The system checks if the return flag indicates successful update of the transmission number in the table
[Log Error - Missing Transmission Segment]
The segment is not found in the system table → The system logs an error message indicating the missing transmission segment and calls the error handler
[Log Error - Update Failed]
The replace operation is unsuccessful → The system logs an error message indicating the update failure and calls the error handler
[Number Retrieved Successfully?]
The retrieval operation completes → If the return flag indicates success, proceed with number increment; otherwise report missing table segment error
[Report Missing Table Segment Error]
The return flag does not indicate successful retrieval → Set error message to 'MISSING 11 SEGMENT' and call error handler
[Update Successful?]
The update operation completes → If the return flag does not indicate success, report update failed error
[Report Update Failed Error]
The return flag does not indicate successful update → Set error message to 'REPLACE 11 SEGMENT FAILED' and call error handler
[Move Retrieved Segment to Broker Segment]
The broker lookup returns valid broker information → The retrieved table segment data is moved to the broker segment working storage area

As an EDI Gateway Service,
I want to orchestrate and execute all GCX146 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 Interface]
The system initializes the CIMS interface → The system establishes connection to CIMS and prepares for message command processing
[Initialize Customer Report Message]
The system begins customer report processing → The customer report message structure is initialized with default values and proper message formatting
[Initialize EDI Header Setup]
The EDI transmission process begins → The system initializes EDI header with train ID, timestamp, and transmission control information
[Initialize Report Message Buffer]
The system prepares to format the report for email → The system should initialize the message buffer and prepare report content for processing
[Initialize Email Message Buffer]
The system begins email report processing → Initialize email message buffer, clear previous content, and prepare for new report data
[Initialize Line Counter WS-LINE-SUB]
The system begins processing report lines for email transmission → The line counter should be initialized to zero to start counting from the beginning
[Initialize Message Buffer]
The message preparation process begins → The message buffer is cleared and initialized with default values
[Initialize Line Counter WS-LINE-SUB = 1]
The system begins processing email content → The line counter is set to 1 to begin tracking from the first line
[Initialize Equipment Sequence Counter]
The system begins processing equipment records → The equipment sequence counter is set to 1 to track the first equipment position
[Initialize Customer Report Message]
The system begins customer report database operations → The customer report message structure is initialized with default values
[Initialize Line Counter]
The system starts processing report lines → The line counter is set to zero and message buffer is initialized
[Initialize US Trip Sheet Equipment Records]
The system begins processing equipment records → Equipment counters are reset to zero and processing flags are initialized
[Initialize New Message Segment]
The system initializes a new message segment → Message buffer is reset and prepared for additional equipment data with appropriate headers
[Initialize Report Message Format]
The system begins report message creation process → The report message format is initialized and ready to receive content

Core Acceptance Criteria

[1:Input Message Retrieval]
The system attempts to retrieve the next input message from the queue → If a message is available, processing continues; if no message is available, processing terminates
[22:EDI Transmission Processing]
The system transmits EDI transactions → EDI transactions are sent to appropriate trading partners and customs authorities with train and equipment information
[24:Confirmation Message Generation]
The system generates confirmation messages → Successful operations generate confirmation messages to originating terminals; failed operations generate error notifications with appropriate error codes
[26:Status Report Generation]
The system generates status reports → Status report includes equipment totals by category, detailed status information, transit status indicators, and up to 90 lines of US status messages
[28:Email/FAX Distribution]
The system processes email and FAX distribution → Email messages are limited to 699 lines per message; larger reports create continuation messages with 'CONTINUATION OF REPORT...' header; failed emails are sent to support team (OM01247, AEI9999)
[Call READQ to Access Message Queue]
A READQ call is made to access the message queue → The system attempts to read the next available message from the IMS message queue
[Move Message to INPUT-MESSAGE Buffer]
The message needs to be prepared for processing → The message content is moved to the INPUT-MESSAGE buffer
[Get Message Length]
The system needs to know the message boundaries → The message length is determined and stored for processing validation
[Set Return Code to Continue Processing]
The system needs to indicate processing should continue → The return code is set to zero to signal continuation of the message retrieval loop
[Set Return Code to Stop Processing]
The system determines the queue is empty → The return code is set to non-zero to signal termination of the message retrieval loop
[Proceed to Message Validation]
The return code indicates continuation of processing → The system proceeds to the next phase of message validation and processing
[End Message Retrieval Loop]
The return code indicates processing should stop → The message retrieval loop is terminated and the system exits the input processing phase
[Extract User ID from Input Message]
The system begins SCAC access validation → The user ID is extracted from the input message for authorization checking
[Request Type = ADD?]
The request type field equals 'ADD' → The system sets the AEI-TRAIN-SEND flag and establishes ADD processing mode
[Request Type = VERIFY?]
The request type field equals 'VERIFY' → The system sets the AEI-TRAIN-SEND flag and establishes VERIFY processing mode
[Request Type = NOTIFY?]
The request type field equals 'NOTIFY' → The system sets the AEI-TRAIN-SEND flag and establishes NOTIFY processing mode
[Extract PUBLIC Merlin ID]
The system processes Merlin ID extraction → The PUBLIC Merlin ID is extracted from the admin table and stored for validation
[Extract DC-P Merlin ID]
The system processes Merlin ID extraction → The DC-P Merlin ID is extracted from the admin table and stored for validation
[Extract SUPERVISOR Merlin ID]
The system processes Merlin ID extraction → The SUPERVISOR Merlin ID is extracted from the terminal table and stored for validation
[Extract ALTERNATE Merlin ID]
The system processes Merlin ID extraction → The ALTERNATE Merlin ID is extracted from the terminal table and stored for validation
[Merlin ID Validation Failed]
Any Merlin ID validation fails (PUBLIC, SUPERVISOR, CUSTOMS, DC-P, or SYSTEM-FAX) → The system stops the validation process and reports the specific validation error without proceeding to customs reporting operations
[Extract Train Number from Input]
The system processes the train ID construction request → The train number component is extracted from the input message and stored for further processing
[Extract Train Day from Input]
The system processes the train ID construction request → The train day component is extracted from the input message and stored for further processing
[Extract From Station Code]
The system processes the train ID construction request → The from station code is extracted from the input message and stored for further processing
[Extract To Station Code]
The system processes the train ID construction request → The to station code is extracted from the input message and stored for further processing
[Extract Consist Number]
The system processes the train ID construction request → The consist number is extracted from the input message and stored for further processing
[Search Station Configuration Table]
The system searches the station configuration table for the station code → The system retrieves the corresponding station data if found, or proceeds to validation checks if not found
[Process Equipment Segment]
Processing equipment segment for train consist → Equipment segment data is processed including waybill lookup, CCN validation, and status determination
[Extract Equipment ID from Input]
The system processes the equipment data from the input message → The equipment ID is extracted from the input message and made available for further processing
[Format Equipment ID for Database Search]
The system needs to prepare database search keys → The equipment ID is formatted and assigned to search key fields for FWIIROOT, SHIPROOT, and inquiry database lookups
[Extract Equipment Details]
The system extracts equipment details from the waybill data → All relevant equipment information should be parsed and structured for subsequent business rule processing
[Get Car Type Description from VI Segment]
Car type description is needed for processing or reporting → System retrieves car type description from VI segment using the car type code
[Add Status Message: CCN Not Found]
The system updates status messaging → A status message indicating 'CCN Not Found' is added to the equipment processing record
[Add Status Message: CCN Found Not Usable]
The system updates status messaging → A status message indicating 'CCN Found Not Usable' is added to the equipment processing record
[Add Unusable Status Message]
The system needs to communicate the unusable status → An unusable status message is added to the processing results
[Parse Container ID Field]
The system processes the container data → The system parses the container ID field to extract the container identifier
[Set Equipment Type Message]
Status reporting is required → The appropriate equipment type message is set (EMPTY, IDLER, or EXEMPTED) for display in reports and status inquiries
[Call GCCCARTP Module for Equipment Type]
The system calls the GCCCARTP module to determine equipment type → The equipment type is classified and returned for further processing
[Set Container Equipment Type Code]
The system processes the equipment for EDI transmission → The equipment type code is set to container classification for EDI record
[Set Trailer Equipment Type Code]
The system processes the equipment for EDI transmission → The equipment type code is set to trailer classification for EDI record
[Set Car Equipment Type Code]
The system processes the equipment for EDI transmission → The equipment type code is set to car classification for EDI record
[Assign Load/Empty Status Indicator]
If the cargo content status of the equipment → The load/empty status indicator is assigned to reflect whether equipment is loaded or empty
[Set CCN Key for EDI Manifest]
The system prepares the EDI manifest record → The CCN key is set in the EDI equipment record for customs identification
[Build EDI Equipment Record Structure]
The system builds the EDI equipment record → A complete EDI record structure is created with all required data elements populated
[Queue EDI Record for Transmission]
The system processes the valid record → The EDI record is queued for transmission to customs
[Prepare Next Equipment Record]
The system continues processing the train consist → The next equipment record is prepared for EDI processing
[More Equipment?]
The system checks for remaining equipment in the train consist → Processing continues if more equipment exists or proceeds to transmission if complete
[Transmit EDI Data to Customs]
The system initiates EDI transmission to customs → All queued EDI records are transmitted to customs authorities
[Log EDI Transmission Status]
The system completes the transmission process → The transmission status is logged for audit and monitoring purposes
[Report > 699 Lines?]
The report contains more than 699 lines → The system activates continuation logic to split the report into multiple email messages
[Prepare Standard AEI Report]
The system prepares the report for email transmission → The system formats the report as a single email message without continuation headers
[Prepare Report with Continuation Logic]
The system prepares the report for email transmission → The system splits the report into batches of 699 lines or fewer with continuation headers
[Send Current Report Batch]
The system processes the current batch → The system transmits the batch via EMCSEND3 email service to the configured recipients
[Reset Message Buffer]
The system prepares for the next batch of data → The system clears the message buffer and resets line counters for the next batch
[Add Continuation Header]
The system prepares a continuation batch after the first message → The system adds the header 'CONTINUATION OF REPORT....' to identify the message as a continuation
[Process Next Batch]
The system processes the next batch → The system prepares up to 699 lines for the next email message with appropriate continuation headers
[Send AEI Report via EMCSEND3]
The system initiates email transmission → The system calls EMCSEND3 service to deliver the report to the configured email recipients
[Use Fallback Email Recipients]
The system needs to ensure report delivery → The system configures fallback recipients (OM01247 and AEI9999) for report transmission
[Send to OM01247/AEI9999]
The system uses fallback recipients → The system sends the AEI report to OM01247 and AEI9999 as backup recipients
[Handle Email Failure]
The system processes the failure → The system logs the failure and initiates fallback transmission procedures
[Log AEI Train Send Activity]
The system finalizes the AEI process → The system logs the train send activity with timestamp, user information, and transmission status
[Determine Message Type]
If the processing outcome → The system selects success confirmation message type if no errors occurred, otherwise selects error confirmation message type
[Create Success Confirmation Message]
The system creates a confirmation message → The system generates a GCT1051E success message with train processing details
[Format Message Content]
The system formats the message content → The system includes train identification, processing status, error details if applicable, and relevant business data in the message format
[Set Message Routing]
The system sets message routing parameters → The system assigns ALT-PCB routing, sets message priority, and determines recipient terminals based on message type and business requirements
[Queue Message via CSISER]
The system queues the message via CSISER → The system adds the message to the processing queue using the appropriate CSISER interface methods
[Add Message Command to Queue]
The system adds the message command to the queue → The system queues the appropriate operation (CHNG for changes, WRITMSGL for message logging, or PURG for purging) based on message type and processing requirements
[Process Queued Commands]
The system processes queued commands → The system executes all queued CIMS commands in sequence for message delivery and processing
[Send Message to Recipients]
The system sends the message to recipients → The system delivers the confirmation message to all specified terminals and recipients according to the established routing
[Update Message Status]
The system updates message status → The system records the delivery status, timestamp, and any delivery confirmation information
[Log Confirmation Activity]
The system logs confirmation activity → The system creates audit trail entries with message details, processing timestamps, and delivery status for compliance and tracking
[Calculate Equipment Totals]
Equipment totals calculation is initiated → Totals are calculated for released equipment (RELEASE/CSA-DLV status), transit equipment (T status), held equipment (HOLD/AGI-HOLD status), and proceeding equipment (different from/to stations)
[Extract Train Components from Input]
The system processes the train information → Train number, day, from station, to station, and consist number are extracted from the input message
[Set IDLER Message]
The equipment is identified as idler equipment (non-revenue generating) → The system sets the equipment message to 'IDLER' to indicate special handling requirements
[Set UNIT Message]
The equipment is identified as unit equipment (part of unit train) → The system sets the equipment message to 'UNIT' to indicate unit train handling requirements
[Set Standard Message]
The equipment is not identified as idler or unit equipment → The system sets a standard equipment message for normal processing and handling
[Build Equipment Entry Line]
A complete equipment entry line needs to be constructed → The system combines equipment ID, type code, load status, and status messages into a single formatted equipment entry line
[Process US Status Messages]
Processing status messages for the report → US status messages are processed and included in the report up to a maximum of 90 lines
[Identify Distribution Recipients]
The system needs to determine who should receive the error notification → The system identifies appropriate recipients based on error type, user roles, and notification requirements
[Distribute via Message Queues]
The messaging system processes the queued messages → The system distributes error messages to all identified recipients via IMS message queues
[Email Users Found?]
Email addresses are found for the station → The system should proceed with AEI report email distribution, otherwise proceed to Merlin transmission
[Send Complete Report]
Email distribution is initiated → The system should send the complete report in a single email message
[Send Report with Continuation]
Email distribution is initiated → The system should split the report and prepare continuation messages
[Add Continuation Header]
Continuation messages are created → The system should add 'CONTINUATION OF REPORT....' header to each continuation message
[Send Remaining Lines]
Remaining report lines need to be sent → The system should send the remaining lines in subsequent email messages with proper headers
[Primary Email Failed?]
Primary email delivery fails → The system should use fallback email addresses, otherwise proceed to Merlin transmission
[Setup Merlin Transmission]
Merlin transmission is required → The system should setup Merlin transmission parameters
[Set Copy IDs for FAX]
Copy IDs need to be assigned for FAX distribution → The system should set appropriate copy IDs for FAX transmission
[Send via Merlin System]
Report distribution via Merlin is initiated → The system should send the report through Merlin messaging system
[Format Equipment Type Messages]
The system formats the equipment information → Equipment details are structured according to US customs trip sheet message format requirements
[Build Merlin Transmission Lines]
The system builds transmission lines → Message lines are constructed in Merlin format with proper headers and equipment details
[Format Trip Sheet Data for US Customs]
The system formats the complete trip sheet → Trip sheet data is structured according to US customs specifications with all required fields populated
[Segment Large Messages]
The system segments the message → Message is divided into multiple segments with proper sequencing and continuation headers
[Transmit via Merlin Communication]
The system initiates transmission via Merlin → Trip sheet data is sent through Merlin communication system to designated US customs recipients
[Transmission Successful?]
If the transmission result → Transmission status is determined as either successful or failed based on system response
[Generate Transmission Confirmation]
The system generates confirmation → Confirmation message is created indicating successful transmission with timestamp and reference information
[Send Notification]
The system sends the notification → The GCT1481E transaction is queued for transmission to customs processing system
[Log Missing Data Warning]
The system encounters missing or incomplete data during population → The system must log a warning message indicating which data elements are missing and continue processing
[X12 EDI Channel Available?]
If available communication channels → The system should use X12 EDI channel if the broker has X12 EDI capability configured
[Send X12 EDI Notification via GCCS309C]
The system processes the notification transmission → The system should invoke GCCS309C to send the notification in X12 EDI format to the broker
[Merlin Channel Available?]
If remaining communication channels → The system should use Merlin channel if the broker has Merlin communication capability configured
[Send Merlin Notification via GCX019]
The system processes the notification transmission → The system should invoke GCX019 to send the notification through Merlin system to the broker
[Send Internet Notification via GCX019]
The system processes the notification transmission → The system should invoke GCX019 to send the notification via Internet to the broker
[Send FAX Notification via GCX019]
The system processes the notification transmission → The system should invoke GCX019 to send the notification via FAX to the broker
[Determine Notification Channels]
If available notification channels → The system should identify all configured channels including X12 EDI, Merlin, Internet, FAX, and Paper based on broker preferences
[Call GCCS309C for X12]
The system processes X12 notifications → The system should call GCCS309C program to send X12 EDI notifications to the primary broker
[X12 EDI Channel Available?]
If available notification channels → X12 EDI channel is selected as the first priority if available
[Send via X12 EDI - GCCS309C]
The system initiates X12 EDI transmission → GCCS309C program is invoked to process the X12 EDI notification
[Merlin Channel Available?]
If the next available notification channel → Merlin channel is selected if available as the second priority option
[Send via Merlin - GCX019]
The system initiates Merlin transmission → GCX019 program is invoked to process the Merlin notification
[Internet Channel Available?]
If the next available notification channel → Internet channel is selected if available as the third priority option
[Send via Internet - GCX019]
The system initiates Internet transmission → GCX019 program is invoked to process the Internet notification
[FAX Channel Available?]
If the next available notification channel → FAX channel is selected if available as the fourth priority option
[Send via FAX - GCX019]
The system initiates FAX transmission → GCX019 program is invoked to process the FAX notification
[Generate Paper Notification]
The system needs to complete broker notification → Paper notification is generated as the final fallback option
[Repeat Channel Priority for Secondary Broker]
The system processes secondary broker notification → The same channel priority sequence (X12 EDI, Merlin, Internet, FAX, Paper) is applied for secondary broker
[Log Failed Transmission]
The system detects the transmission failure → The failed transmission is logged before attempting the next fallback channel
[Prepare CCN Data for X12 Format]
The system needs to send broker notification via X12 EDI → The CCN data is formatted according to X12 EDI message structure with broker-specific routing information
[Call GCCS309C Module]
The system is ready to transmit the broker notification → The GCCS309C module is called to process the X12 EDI transmission
[Log Successful X12 Transmission]
The transmission completes successfully → The system logs the successful transmission details including timestamp and broker information
[Set Broker Notification Complete Flag]
The notification process completes → The broker notification complete flag is set to indicate successful delivery
[Handle X12 Transmission Failure]
The GCCS309C module returns a failure status → The system initiates failure handling procedures to manage the unsuccessful transmission
[Continue to Next Notification Channel]
The current notification attempt is complete → The system continues processing to attempt notification through the next available channel (Merlin, Internet, FAX, or Paper)
[Retrieve CCN Record from Database]
The system needs to prepare CCN data for X12 transmission → The system retrieves the complete CCN record from the GCCCRT database
[Format CCN for X12 Structure]
The system prepares the CCN for X12 transmission → The system formats the CCN data according to X12 EDI structure specifications
[CCN Format Valid?]
If the validation results → The system determines if the CCN format is valid for transmission or if format errors exist
[Set X12 CCN Field]
The system processes the valid CCN → The system assigns the CCN to the appropriate X12 message field
[Prepare Equipment ID for X12]
The system prepares X12 message data → The system formats equipment ID according to X12 requirements
[Format Waybill Information]
The system prepares X12 message components → The system formats waybill information according to X12 EDI standards
[Set Cargo Status Code]
The system prepares X12 message data → The system assigns the appropriate cargo status code for X12 transmission
[Prepare Shipper/Consignee Data]
The system builds X12 message components → The system formats shipper and consignee data according to X12 requirements
[Build X12 Message Structure]
The system builds the complete X12 message → The system assembles all components into proper X12 EDI message structure
[Prepare GCX019 Input Parameters]
The system prepares GCX019 input parameters → The broker Merlin ID, notification message content, and message type are configured for the GCX019 module call
[Set Notification Message Content]
The system sets up notification message content → The appropriate message content is formatted and configured for broker notification
[Set Message Type for Broker]
The system needs to classify the message type → The correct message type is determined and set for the broker notification
[Set Message Priority]
Message priority needs to be determined → The system sets priority level based on cargo characteristics and delivery requirements in GCX019 parameters
[GCX019 Module Reference Found]
The system attempts to process internet notification → The system references GCX019 module but cannot execute the internet transmission logic due to missing implementation
[Prepare FAX Message Content]
The system prepares the FAX message content → The system should format the notification data into appropriate FAX message format
[Set FAX Routing Parameters]
The system sets FAX routing parameters → The system should configure transmission settings including destination FAX number and routing information
[Call GCX019 for FAX Transmission]
The system calls GCX019 for FAX transmission → The system should invoke GCX019 program to handle the actual FAX transmission
[FAX Send Successful?]
If the transmission result → The system should determine success or failure based on GCX019 return status
[Log FAX Transmission Success]
The system logs the transmission success → The system should create audit trail entry recording successful FAX delivery
[Update Broker Notification Status]
The system updates broker notification status → The system should mark the broker notification as successfully delivered via FAX
[Alternative Available?]
The system checks for alternative FAX methods → The system should determine if backup FAX numbers or alternative transmission methods are configured
[Mark FAX Notification Failed]
The system marks FAX notification as failed → The system should update broker notification status to indicate FAX delivery failure
[Set FAX Routing Parameters]
The system sets up FAX routing parameters → The system should configure destination routing, delivery options, and transmission parameters for the FAX
[Configure Copy IDs for FAX]
The system configures copy IDs for the FAX transmission → The system should assign unique copy identifiers for tracking and distribution management
[Prepare FAX Header Information]
The system prepares FAX header information → The system should format sender information, recipient details, transmission date/time, and document identification in the FAX header
[Format Message Content for FAX]
The system formats message content for FAX transmission → The system should format the message content to meet FAX layout requirements, character limitations, and transmission standards
[Set FAX Transmission Flags]
The system sets FAX transmission flags → The system should configure transmission priority, delivery confirmation requirements, and retry options
[FAX Config Valid?]
If FAX configuration validity → If configuration is valid, mark FAX message as ready; if invalid, prepare alternative routing options
[Skip FAX Preparation]
The system processes the skip FAX preparation path → The system should bypass all FAX configuration steps and proceed to message completion
[X12 EDI Channel?]
The notification channel is evaluated → X12 EDI notification is sent via GCCS309C if X12 EDI channel is selected, otherwise check next available channel
[Send X12 EDI Notification via GCCS309C]
The notification transmission is initiated → The system invokes GCCS309C program to send X12 EDI notification and returns success or failure status
[Merlin Channel?]
The notification channel is evaluated for Merlin → Merlin notification is sent via GCX019 if Merlin channel is selected, otherwise check next available channel
[Send Merlin Notification via GCX019]
The notification transmission is initiated → The system invokes GCX019 program to send Merlin notification and returns success or failure status
[Internet Channel?]
The notification channel is evaluated for Internet → Internet notification is sent via GCX019 if Internet channel is selected, otherwise check next available channel
[Send Internet Notification via GCX019]
The notification transmission is initiated → The system invokes GCX019 program to send Internet notification and returns success or failure status
[FAX Channel?]
The notification channel is evaluated for FAX → FAX notification is sent via GCX019 if FAX channel is selected, otherwise check next available channel
[Send FAX Notification via GCX019]
The notification transmission is initiated → The system invokes GCX019 program to send FAX notification and returns success or failure status
[Paper Channel?]
The notification channel is evaluated for Paper → Paper notification is generated via batch print if Paper channel is selected, otherwise complete notification process
[Log Notification Success]
The notification result is processed → The system logs the successful notification transmission for audit and tracking purposes
[Log Notification Failure]
The notification result is processed → The system logs the failed notification transmission for audit and error tracking purposes
[Generate Warning Messages]
The system generates warning messages → The system creates appropriate warning messages for conditions such as IT bond type warnings, train vessel warnings, location mismatches, or TIB date warnings
[Update Status Information]
The system updates status information → The system records the customs status, warning messages, and related information in the equipment record for reporting and further processing
[Add 'CCN FOUND NOT USABLE' Status Message]
The system processes the unusable CCN for VERIFY operation → The system adds 'CCN FOUND NOT USABLE' status message to the response
[Request Type = VERIFY?]
The system checks the request type → If request type is VERIFY, add status message, otherwise continue processing without message
[Set Report Format to GCT1401E]
The system configures the report format → The report format is set to GCT1401E transaction type for customer advice processing
[Configure Message Queue Routing]
The system configures message queue routing → The message routing is configured to use ALT-PCB2 queue for proper customer report delivery
[Move Report Content to Message Buffer]
The system prepares the report for transmission → The report content is moved to the message buffer for processing and distribution
[Execute CIMS CHNG Operation]
The system executes CIMS change operation → The CIMS CHNG operation is performed to process the customer report message
[Execute WRITMSGL Operation]
The system executes write message operation → The WRITMSGL operation is performed to send the customer report message
[Execute PURG Operation]
The system executes purge operation → The PURG operation is performed to clean up the message queue
[Store Audit Trail]
The audit record creation process needs to be completed → The system handles message queuing operations and purges completed audit transactions to finalize the audit trail storage
[Retrieve Car Type Description from VI Segment]
The system needs car type description information → The car type description is retrieved from the VI segment using the car type code
[Access VI Segment Table]
The system needs to retrieve the car type description → The system accesses the VI segment table using the car type code and retrieves the corresponding car type description for display purposes
[Set Equipment Type Code for EDI]
The system needs to set EDI equipment type codes → The system assigns the appropriate EDI equipment type code based on the car type classification for electronic transactions
[Generate Bond Type Warning]
System generates bond type warning → Warning message is created indicating invalid bond type and potential customs compliance issue
[Generate Location Warning]
System generates location warning → Warning message is created indicating location inconsistency and potential routing issue
[Generate Vessel Warning]
System generates vessel warning → Warning message is created indicating vessel name inconsistency with rail transportation mode
[Set US Status Message]
System sets the US status message → Status message includes validation results, warnings, and current customs status for the equipment
[Update Equipment Status]
System updates equipment status → Equipment record is updated with US customs status, bond information, and any validation warnings
[Generate Equipment Type Message IDLER]
The system generates equipment type messages → An equipment type message with IDLER designation is generated
[Include in Trip Sheet without CCN]
The system creates trip sheet reports → Idler equipment is included in the trip sheet without CCN data requirements
[Report > 699 Lines?]
The report contains more than 699 lines → The system initiates large report processing with continuation logic, otherwise uses standard single-message processing
[Process Standard AEI Report]
The system processes the report for email transmission → The system prepares the entire report as a single email message without continuation headers
[Process Large Report with Continuation]
The system processes the report for email transmission → The system splits the report into multiple email messages, each containing up to 699 lines with appropriate continuation headers
[Send Current Batch via EMCSEND3]
The system initiates email sending → The system calls EMCSEND3 service to transmit the email message to the configured recipients
[Reset Message Buffer]
More lines remain to be processed in a large report → The system clears the current message buffer to prepare for the next continuation segment
[Add Continuation Header]
The system prepares continuation messages after the first message → The system adds 'CONTINUATION OF REPORT....' header to identify the message as part of a multi-part report
[More Lines to Process?]
The system checks for remaining content → If more lines exist beyond the current batch, the system continues processing with the next batch, otherwise completes the report transmission
[Email Successful?]
If the transmission status → If transmission failed, the system initiates fallback email procedures, otherwise proceeds with normal AEI logging activities
[Use Fallback Email OM01247/AEI9999]
The system needs to ensure report delivery → The system sends the AEI report to fallback email addresses OM01247 and AEI9999 to ensure delivery to support personnel
[Log AEI Transmission Activity]
The system finalizes the transmission process → The system creates audit log entries recording the AEI transmission activity, including transmission status and recipient information
[Update AEI Send Status]
The system completes the AEI send process → The system updates the AEI send status in the relevant system records to reflect the completion of the transmission process
[Configure Merlin Transmission]
The system configures Merlin transmission → Merlin transmission parameters are set up for report delivery
[Handle Report Continuation]
The system handles report continuation → The system creates multiple email messages with continuation headers and distributes the complete report across multiple messages
[Transmit to Authorized Recipients]
The system transmits to authorized recipients → Trip sheets are transmitted to all authorized recipients including brokers, agents, and other stakeholders
[Send Status Report via Email]
The report exceeds 699 lines → Split the report into multiple email messages with continuation headers 'CONTINUATION OF REPORT....' for subsequent messages
[Prepare Merlin Message Format]
The system prepares the message format using validated Merlin IDs from EMTZ table → Format the report content according to Merlin communication standards with proper headers and routing information
[Send Status Report via Merlin]
The system sends the report through Merlin communication channels → Transmit the report to designated Merlin terminals with proper routing and confirmation handling
[Setup FAX Routing Information]
The system retrieves FAX configuration from station settings → Setup routing information including FAX numbers, transmission parameters, and delivery options from station configuration
[Send Status Report via FAX]
The system initiates FAX transmission → Send the status report via FAX to configured recipients with proper formatting and delivery confirmation
[Log Distribution Activity]
The system finalizes the distribution process → Log all distribution activities including transmission methods used, recipients contacted, success/failure status, and timestamps for audit trail
[Identify Distribution Recipients]
The system needs to determine who should receive the error notification → The system identifies the appropriate recipients including supervisors and designated personnel based on the error type and current user context
[Route to Supervisor via ALT-PCB]
Error message routing to supervisor is initiated → The system routes the error message to supervisors using the ALT-PCB communication channel with supervisor contact information from GCSTBRT
[Designated Personnel Notification?]
If whether additional designated personnel require notification → The system determines if designated personnel notification is needed and either routes to Merlin communication system or proceeds to message queuing
[Route to Merlin Communication System]
Error message routing to designated personnel is initiated → The system routes the error message through the Merlin communication system using communication IDs from EMTZ-ROOT
[Send via IMS Message Queues]
The system initiates message distribution → The system sends the error messages via IMS message queues to ensure reliable delivery to all identified recipients
[Extract Border Information]
Special manifest processing requires border details → Border code and station name are extracted from the train border segments
[Port Fix Message Generation Not Found]
The provided COBOL code summary is analyzed for port fix message generation logic → No specific port fix message generation business process can be identified in the available code
[Generate Equipment Summary Lines]
Report generation requires equipment summary information → Formatted summary lines are generated showing totals for released, held, proceeding, and other equipment categories
[Set Equipment Type Codes]
Processing equipment for EDI transmission → The system invokes GCCCARTP module to determine and assign appropriate equipment type codes for each piece of equipment
[Assign Load/Empty Status]
Processing equipment status for EDI transmission → The system assigns 'L' for loaded equipment with cargo and 'E' for empty equipment without cargo
[Set CCN Keys for Manifest]
Processing equipment for customs manifest transmission → The system assigns valid CCN keys to each equipment record for customs identification and tracking
[Process Container Equipment]
Processing container equipment for EDI transmission → The system extracts container-specific data including container IDs, cross-references, and formats them according to EDI container standards
[Process Trailer Equipment]
Processing trailer equipment for EDI transmission → The system extracts trailer-specific data and formats it according to EDI trailer equipment standards
[Process Rail Car Equipment]
Processing rail car equipment for EDI transmission → The system extracts rail car specific data including car type, specifications, and formats them according to EDI rail car standards
[Build EDI Equipment Record]
Building individual EDI equipment records → The system constructs complete EDI records with equipment ID, type, status, CCN, and all required customs fields in proper EDI format
[Add to EDI Transmission Buffer]
Adding records to transmission buffer → The system adds each completed equipment record to the EDI transmission buffer maintaining proper sequence and format
[More Equipment?]
Checking for remaining equipment to process → The system continues processing if more equipment records exist, otherwise proceeds to finalize the EDI message
[Finalize EDI Message]
Finalizing the EDI message for transmission → The system adds EDI trailer records, calculates control totals, and prepares the complete message for customs transmission
[Transmit to Customs Systems]
Transmitting to customs systems → The system sends the complete EDI message to the designated customs systems using established communication protocols
[Log EDI Transmission]
Logging transmission activity → The system records transmission timestamp, message identifier, equipment count, and transmission status in audit logs
[Gather Train Summary Data]
The system gathers train summary data → Train identification, station information, and processing details are collected for message formatting
[Compile Equipment Totals]
The system compiles equipment totals → Equipment counts are calculated by status (released, held, proceeding, haulage, documents not required) for confirmation reporting
[Format Confirmation Message]
The system formats the confirmation message → Message is structured with proper headers, train details, equipment summaries, and processing timestamps in standard confirmation format
[Include Train Identification]
The system includes train identification → Train ID, origin station, destination station, and customs train ID are included in the confirmation message
[Include Equipment Count Summary]
The system includes equipment count summary → Equipment totals by status (total equipment, released, held by CCRA, held for documents, proceeding, haulage, documents not required) are included in confirmation message
[Include Processing Timestamp]
The system includes processing timestamp → Current processing date, time, and user identification are included in confirmation message for tracking and audit purposes
[Set Message Priority]
The system sets message priority → Message priority is assigned based on confirmation message type and distribution requirements
[Queue Confirmation Message]
The system queues the confirmation message → Message is placed in distribution queue for delivery to originating terminal and other designated recipients
[Send to Message Distribution]
The system sends to message distribution → Message is processed through distribution system and delivered to designated terminals and recipients
[Log Confirmation Activity]
The system logs confirmation activity → Confirmation generation, message content summary, distribution status, and timestamp are recorded in system audit log
[Set Equipment Type for EDI]
EDI processing is required → The validated equipment type code is set for EDI transmission
[Set EDI Load/Empty Indicator]
EDI transmission requires load/empty indicator → Convert the internal status to the appropriate EDI load/empty indicator format
[Report Exceeds 699 Lines?]
If the report exceeds 699 lines → If the report has more than 699 lines, the system should initiate batch processing, otherwise proceed with single email transmission
[Send Current Report Batch via Email]
The system sends the current report batch via email → The system should transmit the current batch using EMCSEND3 email service to the configured recipients
[Reset Message Buffer]
The system needs to prepare for the next batch → The system should reset the message buffer and clear previous content to prepare for continuation processing
[Add Continuation Header Message]
The system prepares a continuation email message → The system should add the header 'CONTINUATION OF REPORT....' to indicate this is a continuation of the previous message
[Email Send Successful?]
The system checks the email transmission status → If the email was successful, proceed to log the transmission, otherwise initiate fallback email procedures
[Use Fallback Email Recipients]
The system activates fallback email recipients → The system should prepare to use the fallback email addresses OM01247 and AEI9999 for report delivery
[Log Email Transmission]
The system logs the email transmission → The system should record the transmission details including recipients, timestamp, and delivery status for audit purposes
[AEI Report Distribution Complete]
The AEI report distribution process concludes → The system should mark the distribution as complete and finalize the process
[Email Distribution Failed]
The email distribution fails completely → The system should mark the distribution as failed and handle the error condition appropriately
[Add Report Header Lines]
The system begins building the email report content → Add report header lines including report identification, date, time, and relevant train or processing information
[Process Equipment Report Lines]
The system processes equipment data for the report → Generate detailed report lines for each equipment item including status, location, and relevant business information
[Add Equipment Details to Email]
The system processes equipment details for inclusion → Add equipment details including car ID, status, location, and other relevant business information to the email message
[More Equipment?]
The system checks for additional equipment in the report queue → If more equipment exists, continue processing next item, otherwise proceed to finalize the email message
[Finalize Email Message]
The system finalizes the email message → Add any closing information, format the message properly, and prepare for email transmission
[Send Email via EMCSEND3]
The system calls EMCSEND3 to send the email → Attempt to transmit the email to configured recipients using the email service
[Email Send Successful?]
The system checks the transmission result → If email send was successful, log successful transmission, otherwise attempt fallback email delivery
[Log Successful Email Transmission]
The system processes the successful transmission → Log the successful email transmission with timestamp, recipient information, and report details for audit trail
[Try Fallback Email Address OM01247/AEI9999]
The system attempts fallback email delivery → Send the email report to fallback support addresses OM01247 and AEI9999 to ensure report delivery
[Fallback Send Successful?]
The system checks the fallback transmission result → If fallback send was successful, log successful transmission, otherwise log email failure
[Log Email Failure]
The system processes the failed transmission attempts → Log the email failure with error details, attempted recipients, and report information for troubleshooting
[Set Fallback Email Recipients]
The system sets up fallback email recipients → Alternative email recipients are configured to ensure message delivery
[Finalize Email User List]
The system finalizes the email user list → The email user list is prepared and ready for message distribution
[Line Counter > 699?]
The line counter exceeds 699 lines in the current email message → The system should trigger continuation processing to send the current batch and prepare for the next message segment
[Send Current Email Batch]
The continuation processing is triggered → The system should send the current email batch using the email delivery service
[Reset Message Buffer]
Preparing for continuation message processing → The system should reset the message buffer to empty state
[Add Continuation Header Message]
The message buffer has been reset for continuation processing → The system should add the header message 'CONTINUATION OF REPORT ....' to identify this as a continuation message
[Reset Line Counter]
Starting to process remaining report lines for the new message → The system should reset the line counter to zero to begin counting lines for the new message segment
[Continue Processing Remaining Lines]
There are remaining report lines to be processed → The system should continue processing the remaining lines in the new message segment
[Add Line to Email Buffer]
The line is ready to be included in the email message → The system should add the line to the current email message buffer
[Increment Line Counter]
The line addition is complete → The system should increment the line counter by one to maintain accurate count of lines in current message
[Send Final Email Batch]
The final email message batch is ready for transmission → The system should send the final email batch containing the remaining report content
[Reset Message Buffer]
The system needs to prepare for additional report lines → The message buffer should be cleared and reset for the next email segment
[Add CONTINUATION OF REPORT Header]
A new email segment is being prepared after the first segment → A 'CONTINUATION OF REPORT' header should be added to identify the segment as a continuation
[Reset Line Counter]
The system starts processing lines for the new segment → The line counter should be reset to zero to track lines in the new segment
[Set NO-MORE-EMAIL Flag]
There are no more lines to process in the report → The NO-MORE-EMAIL flag should be set to indicate completion of email processing
[Check Auto-FAX Configuration]
The system checks the station configuration in GCSTBRT → The auto-FAX capability flag is retrieved and evaluated to determine if FAX routing should be enabled
[Setup FAX Routing Parameters]
The system prepares for message transmission → FAX routing parameters are configured including destination settings and transmission options
[Send Standard Merlin Message]
The system initiates transmission → The complete message is sent as a single transmission unit
[Split Message for Continuation]
The system processes the oversized message → The message is divided into multiple batches with the first batch containing up to 699 lines
[Send First Message Batch]
The system transmits the first batch → The first 699 lines are sent as the initial message segment
[Add Continuation Header]
The system prepares subsequent message batches → Each remaining batch is prefixed with 'CONTINUATION OF REPORT....' header
[Send Remaining Message Batches]
The system processes remaining batches → Each batch is transmitted sequentially until all message content is delivered
[Call EMCSEND3 for Transmission]
The system calls EMCSEND3 service → The message is transmitted through the Merlin communication channel
[Transmission Successful?]
The system receives transmission response → If transmission is successful, proceed to logging, otherwise handle transmission error
[Log Successful Transmission]
The system processes the success response → Transmission details are logged including timestamp and delivery confirmation
[Set Up FAX Routing Parameters]
The system sets up FAX routing parameters → The system should configure copy IDs for distribution, set external FAX addressing, prepare Merlin transmission parameters, and call EMCSEND for FAX routing
[Call EMCSEND for FAX Routing]
The system calls the EMCSEND service for FAX routing → The external FAX routing service should be invoked to handle the transmission
[Configure Copy Distribution IDs]
The system configures copy distribution parameters → The system sets up copy distribution IDs for proper FAX message routing
[Set External FAX Addressing]
The system sets up external FAX addressing → The system configures external FAX address parameters for proper message delivery
[Set Message Type and Headers]
The system determines the message type and required headers → The appropriate message type identifier and standard headers are set in the message buffer
[Format Train Information]
Train information needs to be formatted for the message → Train ID, date/time, and operational details are formatted and added to the message content
[Add Station Names to Message]
Station information needs to be included → From and to station codes and names are added to the message content
[Format Equipment Details]
Equipment details need to be formatted → Equipment IDs, car types, and related information are formatted for inclusion in the message
[Format Container Information]
Container information needs to be formatted → Container-specific details including container IDs and attributes are formatted for the message
[Format Equipment Type Messages]
Equipment type messages need to be formatted → Car type descriptions and related equipment type messages are formatted and added to the message
[Segment Message for Transmission]
Message segmentation is required → The message is divided into appropriate segments for separate transmission
[Add Continuation Headers]
Continuation headers need to be added → Appropriate continuation headers are added to indicate the message sequence and relationship
[Format Message Lines for Merlin]
Final message line formatting is applied → Message lines are formatted according to Merlin system specifications
[Set FAX Routing Information]
FAX routing information needs to be configured → Station-specific FAX routing parameters are set based on system configuration
[Prepare Final Message Buffer]
The final message buffer needs to be prepared → All message components are assembled into the final transmission-ready buffer
[Message Ready for Transmission]
Message preparation is complete → The message is marked as ready for transmission with all required components properly formatted
[Apply Line Segmentation]
The system applies line segmentation → The message is split into segments of maximum 699 lines each for separate transmission
[Add Continuation Header]
The system processes continuation segments → Each continuation segment includes header 'CONTINUATION OF REPORT ....' to identify it as part of original message
[Reset Message Buffer]
The system prepares for the next message segment → The message buffer is reset to prepare for new content
[Send Current Message Batch]
The system initiates transmission process → The EMCSEND3 email service is invoked to deliver the message
[Apply Merlin Transmission Rules]
The system applies Merlin transmission rules → Message is formatted according to Merlin system requirements for proper transmission
[More Lines to Process?]
The system checks for remaining unprocessed lines → If more lines exist, processing continues; otherwise, message formatting is finalized
[Finalize Message Format]
No more lines remain to be processed → The system finalizes the message format and prepares it for transmission
[Check Auto-FAX Configuration]
The system checks the Auto-FAX configuration settings → The system identifies whether Auto-FAX is enabled or disabled for routing decisions
[Set FAX Routing Parameters]
The system prepares FAX routing parameters → FAX-specific routing configuration is applied to the message
[Set External FAX Addressing]
The system sets up external addressing → External FAX addresses are properly configured for message delivery
[Prepare Merlin Message Format]
The system prepares the message format → The message is formatted according to Merlin transmission specifications
[Set Message Type and Routing]
The system configures message type and routing → Appropriate message type classification and routing information is assigned
[Apply Line Segmentation Rules]
The system applies line segmentation rules → Message content is properly segmented according to transmission line limits
[Create Message Segments]
The system creates message segments → The message is divided into multiple segments that each comply with line limit requirements
[Add Continuation Headers]
The system adds continuation headers → Each continuation segment includes appropriate headers indicating it is part of a multi-part message
[Set Merlin Transmission Parameters]
The system sets Merlin transmission parameters → All necessary transmission parameters are configured for Merlin delivery
[Route to Primary Merlin ID]
The system routes to the primary Merlin ID → The message is directed to the primary Merlin ID for delivery
[Route to Backup Merlin ID]
The system routes to backup Merlin ID → The message is redirected to the backup Merlin ID for delivery
[Apply Message Priority Rules]
The system applies message priority rules → Appropriate priority level is assigned to the message for transmission scheduling
[Set Delivery Confirmation]
The system sets delivery confirmation → Delivery confirmation requirements are configured according to message priority and business rules
[Execute Merlin Transmission]
The system executes Merlin transmission → The message is transmitted via Merlin with the configured parameters and routing
[Log Transmission Activity]
The system logs transmission activity → Transmission details are recorded in the system log for audit trail and monitoring
[Configure FAX Routing with Copy IDs]
The system configures FAX routing → The system sets up FAX routing parameters with appropriate copy IDs for message distribution
[Set External FAX Addressing]
The system sets up external addressing → The system configures external FAX addressing parameters for proper message delivery
[Apply Line Segmentation Rules]
The system processes the email content for transmission → The content is segmented into batches of maximum 699 lines each with proper continuation headers for subsequent segments
[Call X280-CALL-EMCSEND3 to Send Current Batch]
The segment transmission is triggered → The EMCSEND3 service is invoked to send the current email batch
[Reset Message Buffer]
The system prepares for the next segment → The message buffer is reset to empty state for new content
[Add CONTINUATION OF REPORT Header]
The message buffer is reset for continuation → A 'CONTINUATION OF REPORT' header is added to indicate this is a follow-up segment
[Reset Line Counter for Next Batch]
The system starts processing the next batch of lines → The line counter is reset to account for the continuation header and begin fresh counting
[More Lines to Process?]
The system completes processing a portion of content → The system checks if more lines remain to be processed for continuation or completion
[Increment Line Counter]
A line is processed and more lines remain → The line counter is incremented by 1 to track progress within current segment
[Send Final Batch]
The final segment is ready for transmission → The final email batch is sent containing the remaining content
[Set NO-MORE-EMAIL Flag]
The final segment transmission is complete → The NO-MORE-EMAIL flag is set to indicate processing completion
[Additional Cars in Bunch Bill?]
The system checks for bunch bill processing requirements → If additional cars exist in the bunch bill, processing continues with the additional car sequence, otherwise equipment segment processing is complete
[Process Equipment Segment]
Processing equipment for manifest building → Each equipment segment is processed sequentially with proper error handling
[Assign Equipment Type Code]
Assigning equipment type codes for manifest → Appropriate type code is assigned based on equipment classification (container/trailer/car) with corresponding type messages
[Set Message Format to GCT1401E]
The system configures message format → The message format is set to GCT1401E transaction type
[Configure ALT-PCB2 for Message Queuing]
The system configures message queuing → ALT-PCB2 is configured for customer report message control and queuing
[Move Report Content to Message Buffer]
The system transfers report content → Report content is moved from GCX140-INPUT to the message buffer
[Execute CIMS CHNG Operation]
The system executes CIMS CHNG operation → Database change operation is performed for customer report update
[Execute CIMS WRITMSGL Operation]
The system executes CIMS WRITMSGL operation → Customer report message is written to the message queue
[Execute CIMS PURG Operation]
The system executes CIMS PURG operation → Temporary message data is purged from the system
[Build Merlin Transmission Lines]
The system builds Merlin transmission lines → Message lines are constructed with proper formatting, sequencing, and transmission headers for Merlin system delivery
[Prepare Equipment Type Messages]
The system prepares equipment type messages → Messages are customized with equipment-specific information, status codes, and regulatory data appropriate for each equipment type
[Segment Message for Transmission]
The message exceeds transmission system limits → The message is segmented into multiple parts with proper continuation headers and sequence numbering to ensure complete delivery
[More Equipment?]
The system checks for additional equipment in the train consist → If more equipment exists, processing continues with the next equipment record; otherwise, processing moves to finalization
[Ready for Merlin Transmission]
The system prepares for Merlin transmission → Trip sheet is formatted for Merlin system delivery with proper transmission headers, routing information, and delivery confirmation requirements
[Line Available?]
The system checks for line availability → If lines are available, continue processing; if no lines available, finalize current message
[Format Line for Merlin Transmission]
The system formats the line for Merlin transmission → The line is formatted according to Merlin protocol specifications
[Add Line to Current Message Buffer]
The system adds the line to the message buffer → The line is appended to the current message buffer
[Increment Line Counter]
The system updates the line counter → The line counter is incremented by one
[Create Continuation Message]
The system needs to add more lines → A new continuation message is created to handle additional lines
[Reset Message Buffer]
The system resets the message buffer → The message buffer is cleared and line counter is reset to zero
[Add Continuation Header]
The system adds the continuation header → The header 'CONTINUATION OF REPORT....' is added to the beginning of the new message
[Process Equipment Type Messages]
The system processes equipment type messages → Each equipment type (IDLER, UNIT, VAN, ETU) is processed according to its specific requirements
[More Lines to Process?]
The system checks for more lines to process → If more lines exist, continue processing; if no more lines, finalize the current message
[Finalize Current Message]
The system finalizes the current message → The message buffer is prepared for transmission with proper formatting and headers
[Send Message via Merlin]
The system sends the message via Merlin → The message is transmitted through the Merlin system to the intended recipients
[Equipment Type?]
If the equipment type for message assignment → The system classifies the equipment as IDLER, UNIT, VAN, ETU, Container, Trailer, or standard Car based on the car type code patterns
[Assign IDLER Message]
The system processes the equipment for message assignment → The system assigns the appropriate IDLER equipment message format
[Assign UNIT Message]
The system processes the equipment for message assignment → The system assigns the appropriate UNIT equipment message format
[Assign VAN Message]
The system processes the equipment for message assignment → The system assigns the appropriate VAN equipment message format
[Assign ETU Message]
The system processes the equipment for message assignment → The system assigns the appropriate ETU equipment message format
[Assign Container Message]
The system processes the equipment for message assignment → The system assigns the appropriate container equipment message format
[Assign Trailer Message]
The system processes the equipment for message assignment → The system assigns the appropriate trailer equipment message format
[Assign Car Message]
The system processes the equipment for message assignment → The system assigns the standard car equipment message format
[Equipment Status?]
If the equipment status for message assignment → The system determines if the equipment is Load, Empty, Transit, Release, or Held status
[Assign Load Status Message]
The system processes the equipment status for message assignment → The system assigns the appropriate load status message
[Assign Empty Status Message]
The system processes the equipment status for message assignment → The system assigns the appropriate empty status message
[Assign Transit Status Message]
The system processes the equipment status for message assignment → The system assigns the appropriate transit status message
[Assign Release Status Message]
The system processes the equipment status for message assignment → The system assigns the appropriate release status message
[Assign Held Status Message]
The system processes the equipment status for message assignment → The system assigns the appropriate held status message
[Special Processing Required?]
If special processing requirements → The system determines if equipment needs Bunch Bill, Flat Car Container, Return CCN, or standard processing
[Assign Bunch Bill Message]
The system processes the equipment for bunch bill message assignment → The system assigns the appropriate bunch bill message format
[Assign Flat Car Container Message]
The system processes the equipment for flat car container message assignment → The system assigns the appropriate flat car container message format
[Assign Return CCN Message]
The system processes the equipment for return CCN message assignment → The system assigns the appropriate return CCN message format
[Format Equipment Information]
The system formats the equipment information → The system creates properly formatted equipment information message ready for storage
[Store Message Assignment]
The system stores the message assignment → The system saves the equipment message assignment data for subsequent processing steps
[Format Equipment Type Messages]
The system processes the equipment record → Equipment details are formatted according to US customs requirements including car type, waybill information, and cargo details
[Format IDLER Equipment Message]
The system formats the equipment message → IDLER equipment is formatted with car identification and basic details without cargo information
[Format UNIT Equipment Message]
The system formats the equipment message → UNIT equipment is formatted with complete details including car ID, waybill number, shipper, consignee, origin, destination, and cargo description
[Format VAN Equipment Message]
The system formats the equipment message → VAN equipment is formatted with van identification and cargo details appropriate for van shipments
[Format ETU Equipment Message]
The system formats the equipment message → ETU equipment is formatted with tank unit identification and empty status indication
[Format Other Equipment Message]
The system formats the equipment message → Equipment is formatted using standard formatting rules with available car and cargo information
[Add Equipment to Merlin Message Buffer]
The system adds the equipment to the message buffer → Equipment information is appended to the current message buffer and line counters are updated
[More Equipment?]
The system checks for remaining equipment records → Processing continues if more equipment exists, otherwise proceeds to message finalization
[Message Size Exceeded?]
If the message size against limits → Message segmentation is triggered if size exceeds limits, otherwise processing continues normally
[Segment Message for Transmission]
The system segments the message → Current message content is prepared for transmission as a complete segment
[Send Current Message Segment]
The system sends the message segment → Message segment is transmitted to US customs through Merlin communication system
[Continue with Remaining Equipment]
The system continues equipment processing → Remaining equipment records are processed and added to the new message segment
[Finalize Complete Message]
The system finalizes the message → Message is prepared for final transmission with appropriate headers and footers
[Transmit Final Message to US Customs]
The system transmits the final message → Complete trip sheet data is sent to US customs via Merlin communication system
[Log Transmission Activity]
The system logs the transmission → Transmission details including timestamp, message count, and status are recorded for audit trail
[Data Complete?]
If data completeness → System determines if data is complete for immediate use or requires fallback to inquiry database
[Extract Shipper Information from Waybill]
The system processes return CCN data assembly → The shipper name and address information is extracted and populated in the CCN record
[Extract Consignee Information from Waybill]
The system processes return CCN data assembly → The consignee name and address information is extracted and populated in the CCN record
[Send X12 EDI Notification via GCCS309C]
The system processes broker notification distribution → The system invokes GCCS309C program to send X12 EDI notification to the primary broker
[Send X12 EDI to Secondary Broker via GCCS309C]
The system processes secondary broker notification distribution → The system invokes GCCS309C program to send X12 EDI notification to the secondary broker
[Broker Communication Preference Available?]
If broker communication preferences → The system selects the appropriate channel (X12 EDI, Merlin, Internet, FAX, or Paper) based on broker configuration
[Access US Customs Route Information]
The system attempts to access US route data using the cargo's customs control number → The system retrieves US customs route segment data if it exists
[US Route Data Found?]
The system checks if US route segment data was successfully retrieved → If US route data exists, proceed with bond type validation, otherwise skip US customs validation
[IT Bond Type]
The system processes the IT bond type cargo → Generate appropriate warning messages for in-transit bond requirements and restrictions
[TR Bond Type]
The system processes the TR bond type cargo → Apply transportation bond specific validation rules and generate appropriate status messages
[TE Bond Type]
The system processes the TE bond type cargo → Apply temporary export bond validation rules and generate export-related status messages
[MT Bond Type]
The system processes the MT bond type cargo → Apply merchandise in transit bond validation rules and generate transit-related status messages
[Generate Train Vessel Warning]
The system processes train vessel cargo → Generate train-specific warning messages related to rail transportation requirements and restrictions
[Generate Other Vessel Warning]
The system processes non-train vessel cargo → Generate vessel-specific warning messages appropriate for the transportation method
[Generate Bond Type Warning Message]
The system encounters a bond type that is not IT, TR, TE, or MT → Generate a warning message indicating invalid bond type and potential compliance issues
[Generate Location Warning Message]
The system detects location validation failure → Generate a warning message indicating location mismatch or invalid transit location
[Generate In-Transit Warning Message]
The system processes in-transit cargo with identified problems → Generate comprehensive warning messages covering all in-transit related issues and compliance requirements
[Compile All Warning Messages]
All individual warning messages have been created → Compile all warning messages into a single comprehensive report for the cargo shipment
[Check Broker Preferences]
The system checks the broker's communication channel preferences → The system identifies which channels (X12 EDI, Merlin, Internet, FAX, Paper, Email) are available for this broker
[Send X12 EDI Notification]
The system processes the notification through X12 EDI → The system invokes GCCS309C module to send the X12 EDI notification
[Setup FAX Routing]
The system sets up FAX routing → The system configures FAX routing parameters and copy IDs for automatic transmission
[Send via FAX with Copy IDs]
The system processes auto-FAX transmission → The system invokes EMCSEND module to send FAX with copy IDs
[Send Standard Email]
The system processes standard email transmission → The system invokes EMCSEND3 module to send the complete email notification
[Send Email with Continuation]
The system processes large email transmission → The system sends first 699 lines and creates continuation messages with header 'CONTINUATION OF REPORT...' for remaining content using EMCSEND3 module
[Add Continuation Header Message]
The system prepares the next email message segment → The system must add a continuation header message 'CONTINUATION OF REPORT....' to identify it as a follow-up message
[Reset Message Buffer]
The system needs to prepare for the next message segment → The system must reset the message buffer to prepare for additional report content
[More Lines to Process?]
The system checks for remaining content after sending a message batch → If more lines exist to be processed, the system must continue adding lines to the email buffer, otherwise proceed to send the final email batch
[Access GCSTBRT VI Segment]
The system needs to retrieve the corresponding car type description → The system should access the VI segment of the GCSTBRT table using the car type as the lookup key
[Set Message Type to GCT1401E]
The system sets up the message structure → The message type is configured as GCT1401E for proper routing and processing
[Configure Message Queue Routing]
The system configures message routing → The message queue is configured to use ALT-PCB2 for proper distribution routing
[Move Report Content to Message Buffer]
The system prepares to queue the message → The report content is moved to the message buffer for distribution
[Queue Message for Distribution]
The system processes the message for distribution → The message is queued in the distribution system for delivery to recipients
[Process Message Queue Commands]
The system executes queue processing commands → The queued message commands are processed to complete the distribution
[Purge Temporary Message Data]
The system completes message distribution → Temporary message data is purged to clean up system resources

Structural Validations

[3:Request Type Validation]
The system examines the request type flags → The request must be classified as ADD, VERIFY, or NOTIFY; if none of these flags are set, the input is marked as invalid
[27:Error Message Processing]
The system processes error messages → Error messages are formatted with appropriate error codes and descriptions, then distributed to supervisors and originating terminals for resolution
[36:CCN Usability Validation]
The system validates CCN usability → CCN is usable if equipment ID matches saved equipment ID AND (waybill number matches OR new bond created flag = 'Y'); if CCN exists with same equipment but different waybill and no new bond created, it's marked unusable; for VERIFY operations, 'CCN FOUND NOT USABLE' status message is added
[Message Available in Queue?]
The system checks the return code from the READQ operation → If return code is zero, a message is available; if return code is non-zero, no message is available
[Set INVALID-INPUT-FLAG]
The request type is not ADD, VERIFY, or NOTIFY → The system sets the INVALID-INPUT-FLAG to indicate unsupported request type
[Replace Spaces with Zeros in All Components]
Any component contains spaces → All spaces in train number, day, from station, to station, and consist number are replaced with zeros
[Check Equipment ID Format]
The system checks the equipment ID format for valid characters → The equipment ID should contain only alphanumeric characters and be properly formatted
[Container ID Valid?]
The system validates the container ID → The system determines if the container ID is valid based on format and content requirements
[Validate EDI Record Completeness]
The system validates the record for completeness → The record is confirmed to contain all mandatory data elements required for customs transmission
[Handle EDI Transmission Error]
The system encounters the error condition → Appropriate error handling procedures are executed to manage the failure
[Email Send Successful?]
The system receives the transmission response → The system evaluates the response to determine if the email was successfully delivered
[Create Error Confirmation Message]
The system creates a confirmation message → The system generates either a GCT1011E error message or customer report message depending on the error type
[Validate Message Parameters]
The system validates message parameters → The system checks for valid parameters, proper formatting, and required data elements, marking the message as valid or invalid
[Handle Message Errors]
The system handles message errors → The system identifies the error type (invalid parameters, queue full, or system error) and routes to appropriate error handling procedures
[Replace Spaces with Zeros in Train Number]
The train number component contains one or more space characters → All space characters in the train number component are replaced with zero characters
[Replace Spaces with Zeros in Train Day]
The train day component contains one or more space characters → All space characters in the train day component are replaced with zero characters
[Replace Spaces with Zeros in From Station]
The from station component contains one or more space characters → All space characters in the from station component are replaced with zero characters
[Replace Spaces with Zeros in To Station]
The to station component contains one or more space characters → All space characters in the to station component are replaced with zero characters
[Replace Spaces with Zeros in Consist Number]
The consist number component contains one or more space characters → All space characters in the consist number component are replaced with zero characters
[Calculate Proceeding Cargo Total]
The system processes equipment with status 'RETURN' or where manifest from station differs from manifest to station and status is not error, reject, or deleted → The TOTAL-PROCEED counter is incremented by one for each qualifying equipment piece
[Report Total Calculation Error]
The validation fails → An error message is generated indicating total calculation inconsistency and the summary generation continues with available totals
[Calculate Total Proceeding Equipment]
Equipment has status 'RETURN' or manifest from station differs from manifest to station and status is not error, reject, or deleted → The TOTAL-PROCEED counter is incremented by one
[Format Error Message]
The error message needs to be prepared for distribution → The system formats the error message with error code, description, and relevant context information
[Queue Error Message]
The error message is ready for distribution → The system queues the error message in IMS message queues for delivery to all identified recipients
[FAX Configuration Valid?]
FAX configuration needs validation → The system should verify FAX configuration is valid and proceed to external FAX setup if valid, otherwise proceed directly to Merlin system send
[Message Size Check]
The system checks the message size → Message is classified as either normal size for direct transmission or large message requiring segmentation
[Handle Transmission Error]
The system handles the transmission error → Error is logged, appropriate notifications are sent, and retry or alternative delivery methods are initiated
[Waybill Data Available?]
The system accesses the waybill database for the specified equipment → The system must verify waybill data exists before proceeding with shipper and consignee information extraction
[X12 Transmission Successful?, Merlin Transmission Successful?, Internet Transmission Successful?]
The system checks the transmission result → If successful, primary notification is marked complete, otherwise fallback to next channel
[FAX Transmission Successful?]
The system checks the transmission result → If successful, primary notification is marked complete, otherwise fallback to paper notification
[X12 EDI Transmission Successful?]
The transmission process completes → The system determines if the transmission was successful or failed based on the module response
[Log X12 Error Details]
Error handling is initiated → The system logs detailed error information including failure reason and transmission details
[Validate CCN Format]
The system validates the CCN format → The system checks that the CCN format complies with X12 EDI standards
[Check Broker FAX Configuration]
The system checks the broker's FAX configuration → The system should verify FAX number is available and valid before proceeding
[Handle FAX Transmission Error]
The system handles the transmission error → The system should process the error and determine if alternative FAX methods are available
[Validate FAX Configuration]
The system validates the FAX configuration → The system should verify that all required FAX parameters are present, valid, and compatible for successful transmission
[Generate Error Message]
The system encounters validation failures → The system generates appropriate error messages indicating the specific validation failure
[CHNG Successful?]
The system checks the operation result → If CIMS change operation is successful, proceed to write message; otherwise handle error
[Write Successful?]
The system checks the write operation result → If write operation is successful, proceed to purge operation; otherwise handle error
[Purge Successful?]
The system checks the purge operation result → If purge operation is successful, customer report generation is complete; otherwise handle error
[Car Type Code Found?]
The system looks up the car type code in the VI segment table → If the car type code is found, continue with description retrieval, otherwise flag as equipment type error
[Valid Equipment Type?]
The system validates the equipment type classification → If the equipment type is valid and recognized, proceed with EDI code assignment, otherwise flag as equipment type error
[Check Email Transmission Status]
The system receives the transmission response → The system evaluates the response to determine if the email was successfully delivered or if fallback procedures are needed
[Large Report?]
The system checks the report size → The system determines if the report exceeds 699 lines requiring continuation message handling
[Generate Error Message Content]
The system needs to create a human-readable error message → The system generates error message content that describes the error condition in business terms including relevant context information
[Queue Error Message for Distribution]
The system prepares to distribute the error message → The system queues the error message for distribution through the messaging infrastructure
[Skip Confirmation - Errors Exist]
If confirmation generation eligibility → Confirmation message generation is skipped and processing proceeds to completion without sending confirmation due to processing errors
[Status Assignment Error]
Status cannot be determined or is invalid for the equipment type → Generate appropriate error message and handle the equipment record according to error processing rules
[Within Line Limit ≤ 699 lines?]
The system checks the current line count in the email message → If line count is 699 or less, continue adding equipment details, otherwise finalize current message and prepare for continuation
[Line Counter > 699?]
The line counter exceeds 699 lines in the current email segment → The current email batch should be sent and a new email segment should be prepared
[Reached Maximum 1981 Lines?]
The total number of lines processed reaches 1981 lines → The maximum lines reached flag should be set and no additional lines should be processed
[Check Message Size]
The system counts the total number of message lines → If message exceeds 699 lines, it is flagged for continuation processing, otherwise it proceeds as standard transmission
[Handle Transmission Error]
The system receives error response from EMCSEND3 → Error details are logged and appropriate error handling procedures are initiated
[Message Line Limit Reached?]
The system checks the current message line count → If the line limit has been reached, the message is prepared for segmentation, otherwise formatting continues
[Line Count > 699?]
The system counts the number of lines in the message → If line count exceeds 699 lines, the system triggers message segmentation process
[Message Exceeds Line Limit?]
The system checks if the message exceeds the line limit → The system determines whether message segmentation is required based on line count limits
[Primary Routing Success?]
The system checks primary routing success → The system determines whether the primary routing succeeded or failed
[Line Counter > 699?]
The line counter exceeds 699 lines in the current segment → The current segment must be sent and a new segment must be started
[Equipment Record Found?]
The system checks the return status from the database call → If the return code is zero, the equipment record exists and processing continues, otherwise an equipment segment error occurs
[CHNG Operation Successful?]
The system checks operation status → If CHNG operation is successful, proceed to message write operation, otherwise handle database operation error
[Format Equipment Car IDs]
The system formats equipment car IDs → Car identification numbers are standardized with proper length, character formatting, and validation according to railroad and customs standards
[Check Line Length Limits]
The system checks the current line count in the message → If the message has 699 or more lines, create a continuation message; otherwise add line to current message
[Check Message Size Limits]
The system checks the current message size → Message line count and size are validated against maximum transmission limits
[Location Valid?]
The system validates the current location information against expected transit locations → If location is valid, proceed with vessel validation, otherwise generate location warning message
[X12 EDI Channel Available?]
The system checks if X12 EDI channel is available for the broker → The system returns true if X12 EDI is configured and available, otherwise false
[Line Count > 699?]
The system counts the number of lines in the current email message → If the line count exceeds 699 lines, the system must send the current batch and prepare for continuation
[Email Send Successful?]
The system receives the email send response → If the email send is successful, complete the distribution process, otherwise activate fallback email recipients
[Customer Report Message Ready for Distribution]
The system completes all message preparation steps → The customer report message is confirmed ready for distribution to designated recipients

As an EDI Gateway Service,
I want to orchestrate and execute all GUMLER2 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

[3:Format Database Query Key]
The system needs to format the database query key → The car ID is routed to the appropriate database segment (UMSF0RT through UMSF9RT) based on the last digit of the car ID (0-9)
[Format Database Query Key - Determine correct database segment based on car ID last digit (0-9)]
The system needs to format the database query key → The system extracts the last digit from the car ID and sets the query key for the corresponding database segment (digit 0 routes to segment 0, digit 1 routes to segment 1, and so on through digit 9 routing to segment 9)
[Determine Car ID Last Digit]
The system needs to determine which database segment to query → The system routes to the appropriate UMSFXRT segment (0-9) based on the car ID's last digit
[Query UMSF0RT Segment - Digit 0, Query UMSF1RT Segment - Digit 1, Query UMSF2RT Segment - Digit 2, Query UMSF3RT Segment - Digit 3, Query UMSF4RT Segment - Digit 4, Query UMSF5RT Segment - Digit 5, Query UMSF6RT Segment - Digit 6, Query UMSF7RT Segment - Digit 7, Query UMSF8RT Segment - Digit 8, Query UMSF9RT Segment - Digit 9]
The system executes a query against the selected UMSFXRT segment → The system retrieves car information from the appropriate segment and populates the long UMLER IO area
[AAR Code Within Valid Range?]
The system compares the car type AAR code with the segment low AAR code from the reference table → If car type AAR code is greater than or equal to the segment low AAR code, assign the segment series code to output, otherwise no series code is available
[Use Reference Table Series Code]
The system needs to assign a car series code → The segment series code from the reference table is moved to the car series output area
[Extract Series Code from Reference Table and Set Car Series Code in Output]
The system processes the series code assignment → The segment series code from the reference table is moved to the car series output area
[AAR Code Within Valid Range?]
The system compares the car type AAR code with the segment low AAR code from the reference record → If car type AAR code is greater than or equal to segment low AAR code then the range is valid, otherwise the range is invalid and no series code is assigned
[Extract Series Code from Reference Record]
The system processes the series code assignment → The segment series code from the reference record is assigned to the car series output area

Structural Validations

[12:AAR Code in Valid Range?]
The system compares car type AAR code with segment low AAR code → If car type AAR code is greater than or equal to segment low AAR code, assign the segment series code to car series output area
[AAR Code >= Low Range Value?]
The system compares the car type AAR code with the segment low range value → If the AAR code is greater than or equal to the segment low AAR code value, the validation passes and series code assignment proceeds

Detailed EDI User Stories

Module: GCCADDCD 1 Consolidated Epic Story

Module: GCCE358 1 Consolidated Epic Story

Module: GCCS309 1 Consolidated Epic Story

Module: GCCS309C 1 Consolidated Epic Story

Module: GCCS309E 1 Consolidated Epic Story

Module: GCCS358C 1 Consolidated Epic Story

Module: GCCUSCN2 1 Consolidated Epic Story

Module: GCCCARID 1 Consolidated Epic Story

Module: GCCCCIO 1 Consolidated Epic Story

Module: GCCCROS2 1 Consolidated Epic Story

Module: GCCIH 1 Consolidated Epic Story

Module: GCCTIB 1 Consolidated Epic Story

Module: GCX110 1 Consolidated Epic Story

Module: GCCB4RIO 1 Consolidated Epic Story

Module: GCCDESCU 1 Consolidated Epic Story

Module: GCCSNOT3 1 Consolidated Epic Story

Module: GCX010 1 Consolidated Epic Story

Module: GCX101 1 Consolidated Epic Story

Module: GCX140 1 Consolidated Epic Story

Module: GCX146 1 Consolidated Epic Story

Module: GUMLER2 1 Consolidated Epic Story