EDI Logic Deep-Dive Specification

🔍

Module: GCCINARR 314 EDI Rules Found

R-GCCINARR-cbl-00004 4:Manifest Station Validation

Validation Rules

Business View: <EXCLUSION CRITERIA> If user access is validated and all-ports processing is not enabled, and station location validation is required occurs during the '4:Manifest Station Validation' routine, then the system must guarantee that look up manifest station in mc table, set processing flags based on match results, and extract port code if found.

EXCLUDING

User access is validated and all-ports processing is not enabled

When

Station location validation is required

Then

Look up manifest station in MC table, set processing flags based on match results, and extract port code if found

R-GCCINARR-cbl-00016 16:Cargo Arrival Business Rules Validation

Policy Rules

Business View: Assuming cargo needs arrival processing during the '16:Cargo Arrival Business Rules Validation' routine, when business rules validation is performed, the system executes logic to ensure that exclude cargo with return/transit status, us-ca export, empty non-canadian origin, csa bonded, same from/to stations, existing arrival date, missing border procedures for type 6 carrier 105, error status, or process follower/master manifest relationships.

Given

Cargo needs arrival processing

When

Business rules validation is performed

Then

Exclude cargo with return/transit status, US-CA export, empty non-Canadian origin, CSA bonded, same from/to stations, existing arrival date, missing border procedures for type 6 carrier 105, error status, or process follower/master manifest relationships

R-GCCINARR-cbl-00018 23:Port Code Calculation

Computation Rules

Business View: Assuming cargo arrival processing is required during the '23:Port Code Calculation' routine, when port code calculation is performed, the system executes logic to ensure that use destination station port code if manifest to-station is 'iis-a6' or spaces, otherwise use manifest to-station port code.

Given

Cargo arrival processing is required

When

Port code calculation is performed

Then

Use destination station port code if manifest to-station is 'IIS-A6' or spaces, otherwise use manifest to-station port code

R-GCCINARR-cbl-00019 28:CLV Report Generation

Process Rules

Business View: Assuming processing was called from clv during the '28:CLV Report Generation' routine, when report generation is initiated, the system executes logic to ensure that create report with header information, process results for each equipment item, include container details, and handle access/validation error messages.

Given

Processing was called from CLV

When

Report generation is initiated

Then

Create report with header information, process results for each equipment item, include container details, and handle access/validation error messages

R-GCCINARR-cbl-00020 29:AEI Email Report Generation

Action Rules

Business View: Assuming aei report is required during the '29:AEI Email Report Generation' routine, when email report generation is initiated, the system executes logic to ensure that create email with exception details, send to up to 5 merlin email addresses, include equipment and container information with exception messages, and send to backup address if primary distribution fails.

Given

AEI report is required

When

Email report generation is initiated

Then

Create email with exception details, send to up to 5 Merlin email addresses, include equipment and container information with exception messages, and send to backup address if primary distribution fails

R-GCCINARR-cbl-00021 Initialize Communication Areas

Process Rules

Business View: Assuming the program is starting execution during the 'Initialize Communication Areas' routine, when the initialization process begins, the system executes logic to ensure that all communication areas (iscom, gcsccrt, gcstbrt segments) and working storage areas are cleared to spaces or initial values.

Given

The program is starting execution

When

The initialization process begins

Then

All communication areas (ISCOM, GCSCCRT, GCSTBRT segments) and working storage areas are cleared to spaces or initial values

R-GCCINARR-cbl-00036 User Record Found?

Validation Rules

Business View: Assuming user security table lookup has been executed during the 'User Record Found?' routine, when the system evaluates the database search results, the system executes logic to ensure that if the lookup is successful, the system retrieves the user permission segment, otherwise sets no user access flag for missing record.

Given

User security table lookup has been executed

When

The system evaluates the database search results

Then

If the lookup is successful, the system retrieves the user permission segment, otherwise sets no user access flag for missing record

R-GCCINARR-cbl-00037 Retrieve User Permission Segment

Process Rules

Business View: Assuming a user security record has been found in the table during the 'Retrieve User Permission Segment' routine, when the system needs to access the user's permission details, the system executes logic to ensure that the system moves the retrieved table segment data to the user security segment structure for permission evaluation.

Given

A user security record has been found in the table

When

The system needs to access the user's permission details

Then

The system moves the retrieved table segment data to the user security segment structure for permission evaluation

R-GCCINARR-cbl-00038 User has Cargo Arrival Access?

Authorization Rules

Business View: Assuming user permission segment has been retrieved from the security table during the 'User has Cargo Arrival Access?' routine, when the system checks the user's cargo arrival access level, the system executes logic to ensure that if the user has super user access or standard user access for cargo arrival, set user has access flag, otherwise set no user access flag.

Given

User permission segment has been retrieved from the security table

When

The system checks the user's cargo arrival access level

Then

If the user has super user access or standard user access for cargo arrival, set user has access flag, otherwise set no user access flag

R-GCCINARR-cbl-00041 Set No User Access Flag - No Record

Authorization Rules

Business View: Assuming user security table lookup was unsuccessful and no user record was found during the 'Set No User Access Flag - No Record' routine, when the system handles the missing user record condition, the system executes logic to ensure that the system clears the user security segment and sets the no user access flag to true.

Given

User security table lookup was unsuccessful and no user record was found

When

The system handles the missing user record condition

Then

The system clears the user security segment and sets the no user access flag to true

R-GCCINARR-cbl-00042 Set No User Access Flag - Invalid SCAC

Authorization Rules

Business View: <EXCLUSION CRITERIA> If scac access validation has failed for the user and cp scac code combination, and the system processes the invalid scac access result occurs during the 'Set No User Access Flag - Invalid SCAC' routine, then the system must guarantee that the system sets the no user access flag to true without proceeding to user permission table lookup.

EXCLUDING

SCAC access validation has failed for the user and CP SCAC code combination

When

The system processes the invalid SCAC access result

Then

The system sets the no user access flag to true without proceeding to user permission table lookup

R-GCCINARR-cbl-00046 Terminal Record Found?

Process Rules

Business View: Assuming the location terminal table has been queried with a terminal id during the 'Terminal Record Found?' routine, when the database operation completes successfully and returns terminal data, the system executes logic to ensure that the terminal segment information is stored and the terminal found status is maintained.

Given

The Location Terminal table has been queried with a terminal ID

When

The database operation completes successfully and returns terminal data

Then

The terminal segment information is stored and the terminal found status is maintained

R-GCCINARR-cbl-00047 Set Terminal Not Found Status

Process Rules

Business View: Assuming the location terminal table has been queried with a terminal id during the 'Set Terminal Not Found Status' routine, when the database operation fails to find a matching terminal record, the system executes logic to ensure that the terminal segment is cleared and terminal not found status is set.

Given

The Location Terminal table has been queried with a terminal ID

When

The database operation fails to find a matching terminal record

Then

The terminal segment is cleared and terminal not found status is set

R-GCCINARR-cbl-00048 Initialize MC Table Search Parameters

Process Rules

Business View: Assuming the system needs to validate a manifest station against the mc table during the 'Initialize MC Table Search Parameters' routine, when the manifest station validation process begins, the system executes logic to ensure that all mc table search parameters are cleared and initialized to spaces, and table type is set to mc (manifest control).

Given

The system needs to validate a manifest station against the MC table

When

The manifest station validation process begins

Then

All MC table search parameters are cleared and initialized to spaces, and table type is set to MC (Manifest Control)

R-GCCINARR-cbl-00049 Get Manifest Station from CLV Input

Action Rules

Business View: Assuming clv input contains manifest upon station information during the 'Get Manifest Station from CLV Input' routine, when the system prepares to search the mc table, the system executes logic to ensure that the manifest upon station from clv input is moved to the mc table port name search key.

Given

CLV input contains manifest upon station information

When

The system prepares to search the MC table

Then

The manifest upon station from CLV input is moved to the MC table port name search key

R-GCCINARR-cbl-00050 Search MC Table by Port Name

Action Rules

Business View: Assuming mc table search parameters are initialized and manifest port name is set during the 'Search MC Table by Port Name' routine, when the system executes mc table lookup, the system executes logic to ensure that the system searches the mc table using the port name as the key and returns the matching record if found.

Given

MC table search parameters are initialized and manifest port name is set

When

The system executes MC table lookup

Then

The system searches the MC table using the port name as the key and returns the matching record if found

R-GCCINARR-cbl-00051 Set MC Table Match Flag to TRUE

Decision Rules

Business View: Assuming mc table lookup has been performed for a manifest station during the 'Set MC Table Match Flag to TRUE' routine, when a matching mc table entry is successfully found, the system executes logic to ensure that mc table match flag is set to true and process for clv flag is set to true.

Given

MC table lookup has been performed for a manifest station

When

A matching MC table entry is successfully found

Then

MC table match flag is set to TRUE and process for CLV flag is set to TRUE

R-GCCINARR-cbl-00052 Extract Sub-location Code from MC Record

Action Rules

Business View: Assuming a valid mc table record has been retrieved for the manifest station during the 'Extract Sub-location Code from MC Record' routine, when the system processes the mc table record data, the system executes logic to ensure that the sub-location code is extracted from the mc segment and the canadian customs code (positions 2-4) is extracted as the port code for gcx148 processing.

Given

A valid MC table record has been retrieved for the manifest station

When

The system processes the MC table record data

Then

The sub-location code is extracted from the MC segment and the Canadian customs code (positions 2-4) is extracted as the port code for GCX148 processing

R-GCCINARR-cbl-00053 Set MC Table Match Flag to FALSE

Decision Rules

Business View: Assuming mc table lookup has been performed for a manifest station during the 'Set MC Table Match Flag to FALSE' routine, when no matching mc table entry is found, the system executes logic to ensure that mc table match flag is set to false, don't process for clv flag is set to true, and mc segment data is cleared to spaces.

Given

MC table lookup has been performed for a manifest station

When

No matching MC table entry is found

Then

MC table match flag is set to FALSE, don't process for CLV flag is set to TRUE, and MC segment data is cleared to spaces

R-GCCINARR-cbl-00077 Mark Cargo as Found and Eligible for Arrival

Decision Rules

Business View: <EXCLUSION CRITERIA> If a cargo record has been found and passes all validation checks (not deleted, not arrived, has train id), and the system determines cargo processing eligibility occurs during the 'Mark Cargo as Found and Eligible for Arrival' routine, then the system must guarantee that the cargo is marked as found, the cargo report segment is saved as previous, the waybill date index is saved, and the cargo is marked as eligible for arrival processing.

EXCLUDING

A cargo record has been found and passes all validation checks (not deleted, not arrived, has train ID)

When

The system determines cargo processing eligibility

Then

The cargo is marked as found, the cargo report segment is saved as previous, the waybill date index is saved, and the cargo is marked as eligible for arrival processing

R-GCCINARR-cbl-00087 Save Cargo Record as Latest Candidate

Process Rules

Business View: Assuming a cargo record has the latest waybill date among all evaluated records during the 'Save Cargo Record as Latest Candidate' routine, when the system identifies this as the most recent cargo record, the system executes logic to ensure that the entire cargo record segment should be saved as the previous cargo record for potential arrival processing.

Given

A cargo record has the latest waybill date among all evaluated records

When

The system identifies this as the most recent cargo record

Then

The entire cargo record segment should be saved as the previous cargo record for potential arrival processing

R-GCCINARR-cbl-00094 34:Container Information Parsing - Parse container IDs and waybill info

Process Rules

Business View: Assuming container details have been extracted from relationship records during the '34:Container Information Parsing - Parse container IDs and waybill info' routine, when the system processes each container's information, the system executes logic to ensure that the system stores container initial, number, and waybill information in the container table, replacing spaces with zeroes in waybill fields, and increments the container counter.

Given

Container details have been extracted from relationship records

When

The system processes each container's information

Then

The system stores container initial, number, and waybill information in the container table, replacing spaces with zeroes in waybill fields, and increments the container counter

R-GCCINARR-cbl-00103 Search First Cargo Record by Waybill

Action Rules

Business View: Assuming waybill search parameters have been configured during the 'Search First Cargo Record by Waybill' routine, when the system searches for the first cargo record by waybill index, the system executes logic to ensure that if a cargo record is found, it is loaded into the cargo report segment, otherwise the no more cargo flag is set.

Given

Waybill search parameters have been configured

When

The system searches for the first cargo record by waybill index

Then

If a cargo record is found, it is loaded into the cargo report segment, otherwise the no more cargo flag is set

R-GCCINARR-cbl-00109 Search Next Cargo Record by Waybill

Action Rules

Business View: Assuming a cargo record has been processed for the current waybill during the 'Search Next Cargo Record by Waybill' routine, when the system searches for the next cargo record by waybill index, the system executes logic to ensure that if another cargo record is found, it is loaded into the cargo report segment, otherwise the no more cargo flag is set.

Given

A cargo record has been processed for the current waybill

When

The system searches for the next cargo record by waybill index

Then

If another cargo record is found, it is loaded into the cargo report segment, otherwise the no more cargo flag is set

R-GCCINARR-cbl-00114 All Ports Processing?

Decision Rules

Business View: <EXCLUSION CRITERIA> If the system is processing cargo arrival eligibility and all ports processing flag is set to yes (either aei or clv), and the cargo is evaluated for arrival processing and the cargo is not customer bonded occurs during the 'All Ports Processing?' routine, then the system must guarantee that the system sets the cargo as needing arrival processing without checking sub-location matching rules.

EXCLUDING

The system is processing cargo arrival eligibility and all ports processing flag is set to YES (either AEI or CLV)

When

The cargo is evaluated for arrival processing and the cargo is not customer bonded

Then

The system sets the cargo as needing arrival processing without checking sub-location matching rules

R-GCCINARR-cbl-00115 AEI Sub-location Matches Cargo Sub-location?

Validation Rules

Business View: <EXCLUSION CRITERIA> If the system is called from aei program and all ports processing is not enabled, and the system loops through up to 10 aei sub-locations and finds a match with the cargo sub-location code occurs during the 'AEI Sub-location Matches Cargo Sub-location?' routine, then the system must guarantee that the system sets the cargo as needing arrival processing.

EXCLUDING

The system is called from AEI program and all ports processing is not enabled

When

The system loops through up to 10 AEI sub-locations and finds a match with the cargo sub-location code

Then

The system sets the cargo as needing arrival processing

R-GCCINARR-cbl-00116 MC Sub-location Matches Cargo Sub-location?

Validation Rules

Business View: <EXCLUSION CRITERIA> If the system is called from clv program and all ports processing is not enabled, and the mc table sub-location code matches the cargo sub-location code occurs during the 'MC Sub-location Matches Cargo Sub-location?' routine, then the system must guarantee that the system sets the cargo as needing arrival processing.

EXCLUDING

The system is called from CLV program and all ports processing is not enabled

When

The MC table sub-location code matches the cargo sub-location code

Then

The system sets the cargo as needing arrival processing

R-GCCINARR-cbl-00126 Retrieve MC Sub-location Code from Station Validation

Action Rules

Business View: Assuming the request is confirmed to originate from clv system during the 'Retrieve MC Sub-location Code from Station Validation' routine, when the system needs to validate cargo location eligibility, the system executes logic to ensure that retrieve the mc sub-location code from the gcstbrt mc segment for comparison with cargo sub-location.

Given

The request is confirmed to originate from CLV system

When

The system needs to validate cargo location eligibility

Then

Retrieve the MC sub-location code from the GCSTBRT MC segment for comparison with cargo sub-location

R-GCCINARR-cbl-00139 Skip Cargo - CSA/Transit/Return/Export Rules

Decision Rules

Business View: Assuming a cargo record is being evaluated for arrival processing during the 'Skip Cargo - CSA/Transit/Return/Export Rules' routine, when the cargo in-transit status is 'return' or the cargo in-transit status is 'transit', the system executes logic to ensure that the system skips cargo arrival processing and displays appropriate message.

Given

A cargo record is being evaluated for arrival processing

When

The cargo in-transit status is 'Return' OR the cargo in-transit status is 'Transit'

Then

The system skips cargo arrival processing and displays appropriate message

R-GCCINARR-cbl-00140 Skip Cargo - CSA/Transit/Return/Export Rules

Decision Rules

Business View: Assuming a cargo record is being evaluated for arrival processing during the 'Skip Cargo - CSA/Transit/Return/Export Rules' routine, when the cargo is identified as us-canada export cargo, the system executes logic to ensure that the system skips cargo arrival processing and displays appropriate message.

Given

A cargo record is being evaluated for arrival processing

When

The cargo is identified as US-Canada export cargo

Then

The system skips cargo arrival processing and displays appropriate message

R-GCCINARR-cbl-00141 Skip Cargo - CSA/Transit/Return/Export Rules

Decision Rules

Business View: <EXCLUSION CRITERIA> If a cargo record is being evaluated for arrival processing, and the cargo in-transit status is 'empty' and the cargo origin country is not equal to 'ca' occurs during the 'Skip Cargo - CSA/Transit/Return/Export Rules' routine, then the system must guarantee that the system skips cargo arrival processing and displays appropriate message.

EXCLUDING

A cargo record is being evaluated for arrival processing

When

The cargo in-transit status is 'Empty' AND the cargo origin country is not equal to 'CA'

Then

The system skips cargo arrival processing and displays appropriate message

R-GCCINARR-cbl-00142 Skip Cargo - Bonded at FPOA

Policy Rules

Business View: Assuming a cargo record is being evaluated for arrival processing during the 'Skip Cargo - Bonded at FPOA' routine, when the csa indicator is on, the system executes logic to ensure that the system skips cargo arrival processing and displays message 'cargo bonded at fpoa'.

Given

A cargo record is being evaluated for arrival processing

When

The CSA indicator is ON

Then

The system skips cargo arrival processing and displays message 'CARGO BONDED AT FPOA'

R-GCCINARR-cbl-00143 Skip Cargo - Already Arrived

Decision Rules

Business View: <EXCLUSION CRITERIA> If a cargo record is being evaluated for arrival processing, and the manifest from-station name equals the manifest to-station name and the manifest to-station name is not equal to 'iis-a6' occurs during the 'Skip Cargo - Already Arrived' routine, then the system must guarantee that the system skips cargo arrival processing and displays message 'cargo already arrived'.

EXCLUDING

A cargo record is being evaluated for arrival processing

When

The manifest from-station name equals the manifest to-station name AND the manifest to-station name is not equal to 'IIS-A6'

Then

The system skips cargo arrival processing and displays message 'CARGO ALREADY ARRIVED'

R-GCCINARR-cbl-00148 Process Follower Manifest

Process Rules

Business View: Assuming a cargo record is being evaluated for arrival processing during the 'Process Follower Manifest' routine, when the cargo is identified as follower manifest, the system executes logic to ensure that the system sets follower flag, retrieves master ccn, and processes the cargo accordingly.

Given

A cargo record is being evaluated for arrival processing

When

The cargo is identified as follower manifest

Then

The system sets follower flag, retrieves master CCN, and processes the cargo accordingly

R-GCCINARR-cbl-00149 Process Master Manifest

Process Rules

Business View: Assuming a cargo record is being evaluated for arrival processing during the 'Process Master Manifest' routine, when the cargo is master manifest and the cargo arrival date is spaces, the system executes logic to ensure that the system checks for master already arrived, performs report area setup, and calls gcx148 arrival transaction if not already processed.

Given

A cargo record is being evaluated for arrival processing

When

The cargo is master manifest AND the cargo arrival date is SPACES

Then

The system checks for master already arrived, performs report area setup, and calls GCX148 arrival transaction if not already processed

R-GCCINARR-cbl-00487 Skip Arrival - Return Cargo

Decision Rules

Business View: Assuming a cargo record is being processed for arrival during the 'Skip Arrival - Return Cargo' routine, when the cargo in-transit status is 'return', the system executes logic to ensure that the system skips arrival processing and displays 'csa cargo, do not arrive' message.

Given

A cargo record is being processed for arrival

When

The cargo in-transit status is 'RETURN'

Then

The system skips arrival processing and displays 'CSA CARGO, DO NOT ARRIVE' message

R-GCCINARR-cbl-00488 Skip Arrival - Transit Cargo

Decision Rules

Business View: Assuming a cargo record is being processed for arrival during the 'Skip Arrival - Transit Cargo' routine, when the cargo in-transit status is 'transit', the system executes logic to ensure that the system skips arrival processing and displays 'csa cargo, do not arrive' message.

Given

A cargo record is being processed for arrival

When

The cargo in-transit status is 'TRANSIT'

Then

The system skips arrival processing and displays 'CSA CARGO, DO NOT ARRIVE' message

R-GCCINARR-cbl-00489 Skip Arrival - Transit Cargo

Decision Rules

Business View: Assuming a cargo record is being processed for arrival during the 'Skip Arrival - Transit Cargo' routine, when the cargo is marked as us-ca export cargo, the system executes logic to ensure that the system skips arrival processing and displays 'csa cargo, do not arrive' message.

Given

A cargo record is being processed for arrival

When

The cargo is marked as US-CA export cargo

Then

The system skips arrival processing and displays 'CSA CARGO, DO NOT ARRIVE' message

R-GCCINARR-cbl-00490 Skip Arrival - Empty Non-CA Origin

Decision Rules

Business View: <EXCLUSION CRITERIA> If a cargo record is being processed for arrival, and the cargo in-transit status is 'empty' and the origin country is not equal to 'ca' occurs during the 'Skip Arrival - Empty Non-CA Origin' routine, then the system must guarantee that the system skips arrival processing and displays 'csa cargo, do not arrive' message.

EXCLUDING

A cargo record is being processed for arrival

When

The cargo in-transit status is 'EMPTY' AND the origin country is not equal to 'CA'

Then

The system skips arrival processing and displays 'CSA CARGO, DO NOT ARRIVE' message

R-GCCINARR-cbl-00776 Check Return Status

Decision Rules

Business View: Assuming a cargo record is being evaluated for arrival processing during the 'Check Return Status' routine, when the cargo has in-transit status of 'return', the system executes logic to ensure that the cargo is marked as csa cargo and excluded from arrival processing with appropriate message displayed.

Given

A cargo record is being evaluated for arrival processing

When

The cargo has in-transit status of 'Return'

Then

The cargo is marked as CSA cargo and excluded from arrival processing with appropriate message displayed

R-GCCINARR-cbl-00777 Check Transit Status

Decision Rules

Business View: Assuming a cargo record is being evaluated for arrival processing during the 'Check Transit Status' routine, when the cargo has in-transit status of 'transit', the system executes logic to ensure that the cargo is marked as csa cargo and excluded from arrival processing with appropriate message displayed.

Given

A cargo record is being evaluated for arrival processing

When

The cargo has in-transit status of 'Transit'

Then

The cargo is marked as CSA cargo and excluded from arrival processing with appropriate message displayed

R-GCCINARR-cbl-00778 Check US-CA Export Flag

Decision Rules

Business View: Assuming a cargo record is being evaluated for arrival processing during the 'Check US-CA Export Flag' routine, when the cargo is flagged as us-ca export cargo, the system executes logic to ensure that the cargo is marked as csa cargo and excluded from arrival processing with appropriate message displayed.

Given

A cargo record is being evaluated for arrival processing

When

The cargo is flagged as US-CA export cargo

Then

The cargo is marked as CSA cargo and excluded from arrival processing with appropriate message displayed

R-GCCINARR-cbl-00779 Check Empty Status and Origin Country

Decision Rules

Business View: <EXCLUSION CRITERIA> If a cargo record is being evaluated for arrival processing, and the cargo has in-transit status of 'empty' and the origin country is not equal to 'ca' occurs during the 'Check Empty Status and Origin Country' routine, then the system must guarantee that the cargo is marked as csa cargo and excluded from arrival processing with appropriate message displayed.

EXCLUDING

A cargo record is being evaluated for arrival processing

When

The cargo has in-transit status of 'Empty' AND the origin country is not equal to 'CA'

Then

The cargo is marked as CSA cargo and excluded from arrival processing with appropriate message displayed

R-GCCINARR-cbl-00780 Display CSA Cargo Message

Process Rules

Business View: Assuming a cargo record has been identified as csa cargo during the 'Display CSA Cargo Message' routine, when the system processes the csa cargo determination, the system executes logic to ensure that an informational message 'csa cargo, do not arrive' is displayed to indicate the cargo exclusion reason.

Given

A cargo record has been identified as CSA cargo

When

The system processes the CSA cargo determination

Then

An informational message 'CSA CARGO, DO NOT ARRIVE' is displayed to indicate the cargo exclusion reason

R-GCCINARR-cbl-00493 Manifest From Station = Manifest To Station?

Validation Rules

Business View: <EXCLUSION CRITERIA> If a cargo record with manifest from station and manifest to station information, and the manifest from station equals the manifest to station and the manifest to station is not 'iis-a6' occurs during the 'Manifest From Station = Manifest To Station?' routine, then the system must guarantee that the cargo should be marked as already arrived and not processed for arrival.

EXCLUDING

A cargo record with manifest from station and manifest to station information

When

The manifest from station equals the manifest to station AND the manifest to station is not 'IIS-A6'

Then

The cargo should be marked as already arrived and not processed for arrival

R-GCCINARR-cbl-00644 Check if manifest from-station equals to-station

Decision Rules

Business View: <EXCLUSION CRITERIA> If a cargo record with manifest from-station and to-station fields, and the manifest from-station equals the manifest to-station and the to-station is not 'iis-a6' occurs during the 'Check if manifest from-station equals to-station' routine, then the system must guarantee that the cargo is considered already arrived and arrival processing is skipped.

EXCLUDING

A cargo record with manifest from-station and to-station fields

When

The manifest from-station equals the manifest to-station AND the to-station is NOT 'IIS-A6'

Then

The cargo is considered already arrived and arrival processing is skipped

R-GCCINARR-cbl-00645 Is to-station 'IIS-A6'?

Policy Rules

Business View: Assuming a cargo record where manifest from-station equals manifest to-station during the 'Is to-station 'IIS-A6'?' routine, when the manifest to-station is 'iis-a6', the system executes logic to ensure that continue with arrival processing despite station matching.

Given

A cargo record where manifest from-station equals manifest to-station

When

The manifest to-station is 'IIS-A6'

Then

Continue with arrival processing despite station matching

R-GCCINARR-cbl-00646 Is manifest to-station 'IIS-A6' or SPACES?

Decision Rules

Business View: Assuming a cargo record requiring port code calculation for arrival processing during the 'Is manifest to-station 'IIS-A6' or SPACES?' routine, when the manifest to-station is 'iis-a6' or the manifest to-station is spaces, the system executes logic to ensure that use destination port code calculation method.

Given

A cargo record requiring port code calculation for arrival processing

When

The manifest to-station is 'IIS-A6' OR the manifest to-station is SPACES

Then

Use destination port code calculation method

R-GCCINARR-cbl-00647 Use manifest port code calculation

Decision Rules

Business View: Assuming a cargo record where manifest to-station is neither 'iis-a6' nor spaces during the 'Use manifest port code calculation' routine, when port code calculation is required for arrival processing, the system executes logic to ensure that use manifest to-station port code calculation method.

Given

A cargo record where manifest to-station is neither 'IIS-A6' nor SPACES

When

Port code calculation is required for arrival processing

Then

Use manifest to-station port code calculation method

R-GCCINARR-cbl-00648 Retrieve destination station from CM table

Action Rules

Business View: Assuming a cargo record requiring destination port code calculation during the 'Retrieve destination station from CM table' routine, when the destination station lookup is performed in the cm table, the system executes logic to ensure that extract the port code from the cm segment for the destination station.

Given

A cargo record requiring destination port code calculation

When

The destination station lookup is performed in the CM table

Then

Extract the port code from the CM segment for the destination station

R-GCCINARR-cbl-00649 Retrieve manifest station from MC table

Action Rules

Business View: Assuming a cargo record requiring manifest port code calculation during the 'Retrieve manifest station from MC table' routine, when the manifest to-station lookup is performed in the mc table, the system executes logic to ensure that extract the canadian customs code (positions 2-4) from the mc segment as the port code.

Given

A cargo record requiring manifest port code calculation

When

The manifest to-station lookup is performed in the MC table

Then

Extract the Canadian customs code (positions 2-4) from the MC segment as the port code

R-GCCINARR-cbl-00781 Use destination port code calculation - Retrieve destination station details from CM table, validate station existence, and extract port code for arrival processing

Action Rules

Business View: Assuming a cargo record exists with a destination station number and the manifest to-station is iis-a6 or spaces during the 'Use destination port code calculation - Retrieve destination station details from CM table, validate station existence, and extract port code for arrival processing' routine, when the system needs to determine the port code for arrival processing, the system executes logic to ensure that the system should initialize cm table search parameters, retrieve station details using the cargo destination station number as the search key, and if the station is found in the cm table, extract and assign the cm port code to the arrival transaction.

Given

A cargo record exists with a destination station number and the manifest to-station is IIS-A6 or SPACES

When

The system needs to determine the port code for arrival processing

Then

The system should initialize CM table search parameters, retrieve station details using the cargo destination station number as the search key, and if the station is found in the CM table, extract and assign the CM port code to the arrival transaction

R-GCCINARR-cbl-00787 Extract Station Segment Data

Process Rules

Business View: Assuming a station record has been successfully retrieved from the cm table during the 'Extract Station Segment Data' routine, when processing the retrieved station information, the system executes logic to ensure that the system should move the complete table segment data to the cm station segment structure for access to station details.

Given

A station record has been successfully retrieved from the CM table

When

Processing the retrieved station information

Then

The system should move the complete table segment data to the CM station segment structure for access to station details

R-GCCINARR-cbl-00788 Assign CM Port Code to Arrival Transaction

Process Rules

Business View: Assuming the cm station segment data has been successfully extracted and contains port code information during the 'Assign CM Port Code to Arrival Transaction' routine, when finalizing the port code for the arrival transaction, the system executes logic to ensure that the system should move the cm station port code to the arrival transaction port code field.

Given

The CM station segment data has been successfully extracted and contains port code information

When

Finalizing the port code for the arrival transaction

Then

The system should move the CM station port code to the arrival transaction port code field

R-GCCINARR-cbl-00886 Retrieve Station Segment Data

Process Rules

Business View: Assuming a successful database query has returned station information during the 'Retrieve Station Segment Data' routine, when the system processes the query result, the system executes logic to ensure that the station segment data is moved from the database result to the cm segment structure.

Given

A successful database query has returned station information

When

The system processes the query result

Then

The station segment data is moved from the database result to the CM segment structure

R-GCCINARR-cbl-00887 Extract Port Code from Station Record

Process Rules

Business View: Assuming station segment data has been successfully retrieved from the database during the 'Extract Port Code from Station Record' routine, when the system extracts port information from the station record, the system executes logic to ensure that the port code is obtained from the cm station segment for further processing.

Given

Station segment data has been successfully retrieved from the database

When

The system extracts port information from the station record

Then

The port code is obtained from the CM station segment for further processing

R-GCCINARR-cbl-00789 Initialize MC Table Search Parameters

Process Rules

Business View: Assuming the system needs to calculate port code using manifest destination station during the 'Initialize MC Table Search Parameters' routine, when the manifest port code calculation process is initiated, the system executes logic to ensure that all mc table search parameters are cleared and initialized to spaces, table type is set to mc, and search flags are reset.

Given

The system needs to calculate port code using manifest destination station

When

The manifest port code calculation process is initiated

Then

All MC table search parameters are cleared and initialized to spaces, table type is set to MC, and search flags are reset

R-GCCINARR-cbl-00791 Move Manifest Destination Station to Search Key

Process Rules

Business View: Assuming the table type has been set to mc and manifest destination station name is available during the 'Move Manifest Destination Station to Search Key' routine, when the system prepares the search key for station lookup, the system executes logic to ensure that the manifest destination station name is moved to the mc table search key field.

Given

The table type has been set to MC and manifest destination station name is available

When

The system prepares the search key for station lookup

Then

The manifest destination station name is moved to the MC table search key field

R-GCCINARR-cbl-00792 Retrieve MC Station Details from Database

Action Rules

Business View: Assuming mc table search parameters are configured with manifest destination station name during the 'Retrieve MC Station Details from Database' routine, when the system executes the database retrieval operation, the system executes logic to ensure that the mc table is queried using the station name and database operation is performed.

Given

MC table search parameters are configured with manifest destination station name

When

The system executes the database retrieval operation

Then

The MC table is queried using the station name and database operation is performed

R-GCCINARR-cbl-00793 Station Found in MC Table?

Validation Rules

Business View: Assuming database retrieval operation has been executed for the manifest destination station during the 'Station Found in MC Table?' routine, when the system evaluates the database operation result, the system executes logic to ensure that if the operation is successful, station data extraction proceeds, otherwise the port code calculation process ends.

Given

Database retrieval operation has been executed for the manifest destination station

When

The system evaluates the database operation result

Then

If the operation is successful, station data extraction proceeds, otherwise the port code calculation process ends

R-GCCINARR-cbl-00794 Extract Station Segment Data

Process Rules

Business View: Assuming the manifest destination station has been successfully found in the mc table during the 'Extract Station Segment Data' routine, when the system processes the retrieved station record, the system executes logic to ensure that the complete station segment data is extracted and moved to the mc segment working area.

Given

The manifest destination station has been successfully found in the MC table

When

The system processes the retrieved station record

Then

The complete station segment data is extracted and moved to the MC segment working area

R-GCCINARR-cbl-00795 Extract Canadian Customs Code from Position 2-4

Computation Rules

Business View: Assuming station segment data has been successfully extracted from the mc table during the 'Extract Canadian Customs Code from Position 2-4' routine, when the system processes the canadian customs code field, the system executes logic to ensure that characters in positions 2 through 4 of the canadian customs code are extracted and assigned as the port code.

Given

Station segment data has been successfully extracted from the MC table

When

The system processes the Canadian customs code field

Then

Characters in positions 2 through 4 of the Canadian customs code are extracted and assigned as the port code

R-GCCINARR-cbl-00891 Move Manifest Station Name to Search Key

Process Rules

Business View: Assuming the table type is set to mc station and manifest destination station name is available during the 'Move Manifest Station Name to Search Key' routine, when the search key is configured with manifest station name, the system executes logic to ensure that the manifest destination station name is assigned as the mc port name search key.

Given

The table type is set to MC station and manifest destination station name is available

When

The search key is configured with manifest station name

Then

The manifest destination station name is assigned as the MC port name search key

R-GCCINARR-cbl-00892 Execute Database Table Lookup

Action Rules

Business View: Assuming database parameters are initialized, table type is set to mc station, and search key contains manifest station name during the 'Execute Database Table Lookup' routine, when database table lookup is executed, the system executes logic to ensure that the system attempts to retrieve mc station record from the database using the provided search criteria.

Given

Database parameters are initialized, table type is set to MC station, and search key contains manifest station name

When

Database table lookup is executed

Then

The system attempts to retrieve MC station record from the database using the provided search criteria

R-GCCINARR-cbl-00894 Retrieve MC Station Segment Data

Process Rules

Business View: Assuming mc station database lookup completed successfully during the 'Retrieve MC Station Segment Data' routine, when a matching mc station record is found, the system executes logic to ensure that the system retrieves and stores the complete mc station segment data from the database result.

Given

MC station database lookup completed successfully

When

A matching MC station record is found

Then

The system retrieves and stores the complete MC station segment data from the database result

R-GCCINARR-cbl-00895 Extract Canadian Customs Code

Computation Rules

Business View: Assuming mc station segment data has been successfully retrieved from the database during the 'Extract Canadian Customs Code' routine, when canadian customs code extraction is performed, the system executes logic to ensure that the system extracts characters 2 through 5 from the mc station canadian customs code field and stores it as the port code.

Given

MC station segment data has been successfully retrieved from the database

When

Canadian customs code extraction is performed

Then

The system extracts characters 2 through 5 from the MC station Canadian customs code field and stores it as the port code

R-GCCINARR-cbl-00897 Clear Station Segment Data

Process Rules

Business View: Assuming mc station database lookup completed unsuccessfully during the 'Clear Station Segment Data' routine, when no matching mc station record is found, the system executes logic to ensure that the system clears the mc station segment data to ensure no invalid data remains.

Given

MC station database lookup completed unsuccessfully

When

No matching MC station record is found

Then

The system clears the MC station segment data to ensure no invalid data remains

R-GCCINARR-cbl-00898 Set Table Match Flag to False

Process Rules

Business View: Assuming mc station segment data has been cleared due to failed lookup during the 'Set Table Match Flag to False' routine, when table match status is updated, the system executes logic to ensure that the system sets the mc table match flag to false to indicate lookup failure.

Given

MC station segment data has been cleared due to failed lookup

When

Table match status is updated

Then

The system sets the MC table match flag to false to indicate lookup failure

R-GCCINARR-cbl-00499 Set NOT-ARRIVED-BORDER status

Action Rules

Business View: Assuming a cp cross-border cargo with empty border arrival date during the 'Set NOT-ARRIVED-BORDER status' routine, when the border arrival date validation fails, the system executes logic to ensure that set the cargo status to not-arrived-border and assign exception message rep-msg-5.

Given

A CP cross-border cargo with empty border arrival date

When

The border arrival date validation fails

Then

Set the cargo status to NOT-ARRIVED-BORDER and assign exception message REP-MSG-5

R-GCCINARR-cbl-00501 Set NOT-ACK-AT-BORDER status

Action Rules

Business View: Assuming a cp cross-border cargo with border arrival date but no acknowledgment during the 'Set NOT-ACK-AT-BORDER status' routine, when the border acknowledgment validation fails, the system executes logic to ensure that set the cargo status to not-ack-at-border and assign exception message rep-msg-9.

Given

A CP cross-border cargo with border arrival date but no acknowledgment

When

The border acknowledgment validation fails

Then

Set the cargo status to NOT-ACK-AT-BORDER and assign exception message REP-MSG-9

R-GCCINARR-cbl-00503 Follower Manifest Processing

Process Rules

Business View: Assuming a cargo record exists with follower manifest indicator set during the 'Follower Manifest Processing' routine, when the system processes the cargo for arrival, the system executes logic to ensure that the system should retrieve the master manifest ccn, process the master cargo record, and if master cargo is found then process it for arrival, otherwise set ignore cargo flag.

Given

A cargo record exists with follower manifest indicator set

When

The system processes the cargo for arrival

Then

The system should retrieve the master manifest CCN, process the master cargo record, and if master cargo is found then process it for arrival, otherwise set ignore cargo flag

R-GCCINARR-cbl-00504 Master Manifest CCN Retrieval

Action Rules

Business View: Assuming a follower manifest cargo record with a master manifest ccn reference during the 'Master Manifest CCN Retrieval' routine, when the system needs to process the master manifest, the system executes logic to ensure that the system should retrieve the master ccn record from gccc database using the master manifest ccn key, and if successful load the master cargo segment, otherwise set ignore cargo flag.

Given

A follower manifest cargo record with a master manifest CCN reference

When

The system needs to process the master manifest

Then

The system should retrieve the master CCN record from GCCC database using the master manifest CCN key, and if successful load the master cargo segment, otherwise set ignore cargo flag

R-GCCINARR-cbl-00505 Master Manifest Processing

Process Rules

Business View: Assuming a cargo record with master manifest indicator and no arrival date during the 'Master Manifest Processing' routine, when the system processes the cargo for arrival, the system executes logic to ensure that the system should check for duplicate processing, track the ccn number, and if not already processed then proceed with arrival processing, otherwise skip duplicate processing.

Given

A cargo record with master manifest indicator and no arrival date

When

The system processes the cargo for arrival

Then

The system should check for duplicate processing, track the CCN number, and if not already processed then proceed with arrival processing, otherwise skip duplicate processing

R-GCCINARR-cbl-00506 Master Manifest CCN Tracking

Validation Rules

Business View: Assuming a master manifest cargo record being processed for arrival during the 'Master Manifest CCN Tracking' routine, when the system checks for duplicate processing, the system executes logic to ensure that the system should search through up to 1000 stored master ccn numbers to determine if the current ccn has already been processed.

Given

A master manifest cargo record being processed for arrival

When

The system checks for duplicate processing

Then

The system should search through up to 1000 stored master CCN numbers to determine if the current CCN has already been processed

R-GCCINARR-cbl-00507 Master CCN Duplicate Prevention

Decision Rules

Business View: Assuming a master manifest ccn that matches an already processed ccn in the tracking list during the 'Master CCN Duplicate Prevention' routine, when the duplicate check is performed, the system executes logic to ensure that the system should set the master already arrived flag and skip further arrival processing for this ccn.

Given

A master manifest CCN that matches an already processed CCN in the tracking list

When

The duplicate check is performed

Then

The system should set the master already arrived flag and skip further arrival processing for this CCN

R-GCCINARR-cbl-00650 Initialize Loop Counter J = 1

Process Rules

Business View: Assuming a master manifest ccn needs to be tracked for duplicate prevention during the 'Initialize Loop Counter J = 1' routine, when the system begins the ccn tracking process, the system executes logic to ensure that the loop counter is initialized to position 1 in the tracking array.

Given

A master manifest CCN needs to be tracked for duplicate prevention

When

The system begins the CCN tracking process

Then

The loop counter is initialized to position 1 in the tracking array

R-GCCINARR-cbl-00154 Has border arrival date?

Policy Rules

Business View: Assuming a cargo record has ccn type '6', carrier '105', and ccn-e 'e' during the 'Has border arrival date?' routine, when the system checks if the border arrival date is spaces (empty), the system executes logic to ensure that the system should set not-arrived-border status and generate border arrival exception message if date is empty, otherwise proceed to border acknowledgment validation.

Given

A cargo record has CCN type '6', carrier '105', and CCN-E 'E'

When

The system checks if the border arrival date is SPACES (empty)

Then

The system should set NOT-ARRIVED-BORDER status and generate border arrival exception message if date is empty, otherwise proceed to border acknowledgment validation

R-GCCINARR-cbl-00155 Is border arrival acknowledged?

Policy Rules

Business View: <EXCLUSION CRITERIA> If a cargo record has ccn type '6', carrier '105', ccn-e 'e', and has border arrival date, and the system checks if the border arrival acknowledgment flag is not set occurs during the 'Is border arrival acknowledged?' routine, then the system must guarantee that the system should set not-ack-at-border status and generate border acknowledgment exception message if not acknowledged, otherwise continue with normal cargo processing.

EXCLUDING

A cargo record has CCN type '6', carrier '105', CCN-E 'E', and has border arrival date

When

The system checks if the border arrival acknowledgment flag is not set

Then

The system should set NOT-ACK-AT-BORDER status and generate border acknowledgment exception message if not acknowledged, otherwise continue with normal cargo processing

R-GCCINARR-cbl-00156 Generate border arrival exception message

Action Rules

Business View: Assuming a cargo record with ccn type '6', carrier '105', ccn-e 'e' has no border arrival date during the 'Generate border arrival exception message' routine, when the system sets not-arrived-border status, the system executes logic to ensure that the system should generate and store the appropriate border arrival exception message for reporting.

Given

A cargo record with CCN type '6', carrier '105', CCN-E 'E' has no border arrival date

When

The system sets NOT-ARRIVED-BORDER status

Then

The system should generate and store the appropriate border arrival exception message for reporting

R-GCCINARR-cbl-00157 Generate border acknowledgment exception message

Action Rules

Business View: Assuming a cargo record with ccn type '6', carrier '105', ccn-e 'e' has border arrival date but no acknowledgment during the 'Generate border acknowledgment exception message' routine, when the system sets not-ack-at-border status, the system executes logic to ensure that the system should generate and store the appropriate border acknowledgment exception message for reporting.

Given

A cargo record with CCN type '6', carrier '105', CCN-E 'E' has border arrival date but no acknowledgment

When

The system sets NOT-ACK-AT-BORDER status

Then

The system should generate and store the appropriate border acknowledgment exception message for reporting

R-GCCINARR-cbl-00161 Set Report Area for Error

Process Rules

Business View: Assuming cargo has been flagged as being in error status during the 'Set Report Area for Error' routine, when the system prepares error reporting information, the system executes logic to ensure that the report area is configured with appropriate error message and reporting flags.

Given

Cargo has been flagged as being in error status

When

The system prepares error reporting information

Then

The report area is configured with appropriate error message and reporting flags

R-GCCINARR-cbl-00163 Is cargo a follower manifest?

Decision Rules

Business View: Assuming a cargo record is being processed for arrival during the 'Is cargo a follower manifest?' routine, when the cargo has follower manifest indicator set, the system executes logic to ensure that the system identifies it as a follower manifest requiring master processing.

Given

A cargo record is being processed for arrival

When

The cargo has follower manifest indicator set

Then

The system identifies it as a follower manifest requiring master processing

R-GCCINARR-cbl-00164 Retrieve Master Manifest CCN

Process Rules

Business View: Assuming a follower manifest cargo record is identified during the 'Retrieve Master Manifest CCN' routine, when the system needs to process the associated master manifest, the system executes logic to ensure that the master manifest ccn is retrieved from the follower cargo record.

Given

A follower manifest cargo record is identified

When

The system needs to process the associated master manifest

Then

The master manifest CCN is retrieved from the follower cargo record

R-GCCINARR-cbl-00165 Read Master Manifest from Database

Action Rules

Business View: Assuming a master manifest ccn has been identified from a follower manifest during the 'Read Master Manifest from Database' routine, when the system performs a database lookup using the master ccn, the system executes logic to ensure that the master manifest cargo record is retrieved from the cargo control database.

Given

A master manifest CCN has been identified from a follower manifest

When

The system performs a database lookup using the master CCN

Then

The master manifest cargo record is retrieved from the cargo control database

R-GCCINARR-cbl-00166 Master manifest found?

Validation Rules

Business View: Assuming a database lookup has been performed for a master manifest ccn during the 'Master manifest found?' routine, when the database query completes, the system executes logic to ensure that the system determines whether the master manifest record was successfully found.

Given

A database lookup has been performed for a master manifest CCN

When

The database query completes

Then

The system determines whether the master manifest record was successfully found

R-GCCINARR-cbl-00167 Set Ignore Cargo Flag

Decision Rules

Business View: <EXCLUSION CRITERIA> If a follower manifest is being processed, and the associated master manifest record is not found in the database occurs during the 'Set Ignore Cargo Flag' routine, then the system must guarantee that the ignore cargo flag is set to exclude this follower manifest from further processing.

EXCLUDING

A follower manifest is being processed

When

The associated master manifest record is not found in the database

Then

The ignore cargo flag is set to exclude this follower manifest from further processing

R-GCCINARR-cbl-00168 Process Master Manifest as Cargo

Process Rules

Business View: Assuming a master manifest record has been successfully retrieved from the database during the 'Process Master Manifest as Cargo' routine, when the follower manifest processing requires master manifest arrival, the system executes logic to ensure that the master manifest is processed through the standard cargo arrival processing logic.

Given

A master manifest record has been successfully retrieved from the database

When

The follower manifest processing requires master manifest arrival

Then

The master manifest is processed through the standard cargo arrival processing logic

R-GCCINARR-cbl-00169 Cargo arrival date empty?

Validation Rules

Business View: Assuming a master manifest cargo record is being processed during the 'Cargo arrival date empty?' routine, when the system checks the cargo arrival date field, the system executes logic to ensure that if arrival date is not empty (spaces), skip master manifest processing and complete, otherwise continue with master ccn tracking.

Given

A master manifest cargo record is being processed

When

The system checks the cargo arrival date field

Then

If arrival date is not empty (SPACES), skip master manifest processing and complete, otherwise continue with master CCN tracking

R-GCCINARR-cbl-00170 Master CCN already processed?

Process Rules

Business View: Assuming a master manifest cargo with a specific ccn key is being processed during the 'Master CCN already processed?' routine, when the system searches through the master ccn tracking array (up to 1000 entries) for the current ccn key, the system executes logic to ensure that if the ccn key is found in the tracking array, set master already arrived flag to true, otherwise continue with adding ccn to tracking list.

Given

A master manifest cargo with a specific CCN key is being processed

When

The system searches through the master CCN tracking array (up to 1000 entries) for the current CCN key

Then

If the CCN key is found in the tracking array, set master already arrived flag to true, otherwise continue with adding CCN to tracking list

R-GCCINARR-cbl-00171 Add CCN to Master Tracking List

Process Rules

Business View: <EXCLUSION CRITERIA> If a master manifest ccn has not been processed before and tracking array has available space, and the system adds the ccn key to the master ccn tracking array occurs during the 'Add CCN to Master Tracking List' routine, then the system must guarantee that the ccn key is stored in the next available position (j) in the master ccn number array if j is less than 1000.

EXCLUDING

A master manifest CCN has not been processed before and tracking array has available space

When

The system adds the CCN key to the master CCN tracking array

Then

The CCN key is stored in the next available position (J) in the master CCN number array if J is less than 1000

R-GCCINARR-cbl-00172 Skip Duplicate Processing

Process Rules

Business View: Assuming a master manifest ccn has been identified as already processed (master already arrived flag is true) during the 'Skip Duplicate Processing' routine, when the system evaluates the master already arrived condition, the system executes logic to ensure that continue without executing cargo arrival transaction and complete master manifest processing.

Given

A master manifest CCN has been identified as already processed (master already arrived flag is true)

When

The system evaluates the master already arrived condition

Then

Continue without executing cargo arrival transaction and complete master manifest processing

R-GCCINARR-cbl-00173 Execute Cargo Arrival Transaction

Action Rules

Business View: <EXCLUSION CRITERIA> If a master manifest cargo has arrival date empty, is not already processed, and has been added to tracking list, and the system processes the master manifest for arrival occurs during the 'Execute Cargo Arrival Transaction' routine, then the system must guarantee that call gcx148 program to execute the cargo arrival transaction.

EXCLUDING

A master manifest cargo has arrival date empty, is not already processed, and has been added to tracking list

When

The system processes the master manifest for arrival

Then

Call GCX148 program to execute the cargo arrival transaction

R-GCCINARR-cbl-00174 Current CCN Already in Array?

Validation Rules

Business View: Assuming a master manifest cargo is being processed and a master ccn array exists with up to 1000 entries during the 'Current CCN Already in Array?' routine, when the system checks if the current ccn key matches any existing ccn number in the master array by looping through all stored entries, the system executes logic to ensure that if a match is found, set the master already arrived flag to true, otherwise continue to add the ccn to the array.

Given

A master manifest cargo is being processed and a master CCN array exists with up to 1000 entries

When

The system checks if the current CCN key matches any existing CCN number in the master array by looping through all stored entries

Then

If a match is found, set the master already arrived flag to true, otherwise continue to add the CCN to the array

R-GCCINARR-cbl-00175 Array Position Available?

Process Rules

Business View: <EXCLUSION CRITERIA> If a master manifest ccn is not already in the tracking array and needs to be added, and the system checks if the current array position is less than 1000 entries occurs during the 'Array Position Available?' routine, then the system must guarantee that if space is available, add the current ccn key to the master ccn array at the current position.

EXCLUDING

A master manifest CCN is not already in the tracking array and needs to be added

When

The system checks if the current array position is less than 1000 entries

Then

If space is available, add the current CCN key to the master CCN array at the current position

R-GCCINARR-cbl-00176 Set Master Already Arrived Flag

Decision Rules

Business View: Assuming the current master manifest ccn key matches an existing entry in the master ccn tracking array during the 'Set Master Already Arrived Flag' routine, when a duplicate ccn is detected during the array comparison loop, the system executes logic to ensure that set the master already arrived flag to true to skip duplicate processing.

Given

The current master manifest CCN key matches an existing entry in the master CCN tracking array

When

A duplicate CCN is detected during the array comparison loop

Then

Set the master already arrived flag to true to skip duplicate processing

R-GCCINARR-cbl-00177 Loop Through Existing Master CCN Array

Process Rules

Business View: Assuming a master manifest cargo needs to be checked against existing processed ccn numbers during the 'Loop Through Existing Master CCN Array' routine, when the system loops through the master ccn array from position 1 to 1000 or until an empty entry is found or master already arrived flag is set, the system executes logic to ensure that continue checking each array position until loop termination condition is met.

Given

A master manifest cargo needs to be checked against existing processed CCN numbers

When

The system loops through the master CCN array from position 1 to 1000 or until an empty entry is found or master already arrived flag is set

Then

Continue checking each array position until loop termination condition is met

R-GCCINARR-cbl-00179 All Ports Processing?

Decision Rules

Business View: Assuming a cargo arrival transaction requires port code assignment during the 'All Ports Processing?' routine, when the system checks if all-ports processing is enabled for aei or clv, the system executes logic to ensure that if all-ports processing is enabled, the system should calculate port code based on manifest destination, otherwise use the pre-calculated port code from mc table lookup.

Given

A cargo arrival transaction requires port code assignment

When

The system checks if all-ports processing is enabled for AEI or CLV

Then

If all-ports processing is enabled, the system should calculate port code based on manifest destination, otherwise use the pre-calculated port code from MC table lookup

R-GCCINARR-cbl-00181 Manifest Destination is IIS-A6 or Empty?

Decision Rules

Business View: Assuming a cargo arrival transaction requires dynamic port code calculation during the 'Manifest Destination is IIS-A6 or Empty?' routine, when the system evaluates the manifest to-station name, the system executes logic to ensure that if manifest to-station is 'iis-a6' or spaces, the system should calculate port code from destination station, otherwise calculate from manifest station.

Given

A cargo arrival transaction requires dynamic port code calculation

When

The system evaluates the manifest to-station name

Then

If manifest to-station is 'IIS-A6' or SPACES, the system should calculate port code from destination station, otherwise calculate from manifest station

R-GCCINARR-cbl-00182 Calculate Port Code from Destination Station

Action Rules

Business View: Assuming a cargo with manifest destination of 'iis-a6' or empty during the 'Calculate Port Code from Destination Station' routine, when the system needs to determine the port code for arrival processing, the system executes logic to ensure that the system should look up the cargo destination station number in the cm table and extract the port code from the cm segment.

Given

A cargo with manifest destination of 'IIS-A6' or empty

When

The system needs to determine the port code for arrival processing

Then

The system should look up the cargo destination station number in the CM table and extract the port code from the CM segment

R-GCCINARR-cbl-00183 Calculate Port Code from Manifest Station

Action Rules

Business View: <EXCLUSION CRITERIA> If a cargo with manifest destination that is not 'iis-a6' or empty, and the system needs to determine the port code for arrival processing occurs during the 'Calculate Port Code from Manifest Station' routine, then the system must guarantee that the system should look up the manifest to-station name in the mc table and extract positions 2-4 of the canadian customs code as the port code.

EXCLUDING

A cargo with manifest destination that is not 'IIS-A6' or empty

When

The system needs to determine the port code for arrival processing

Then

The system should look up the manifest to-station name in the MC table and extract positions 2-4 of the Canadian customs code as the port code

R-GCCINARR-cbl-00184 Send Transaction to Message Queue

Action Rules

Business View: Assuming a fully prepared gcx148 transaction with all required parameters during the 'Send Transaction to Message Queue' routine, when the system executes the cargo arrival transaction, the system executes logic to ensure that the system should call cims to change message status, call writmsgl to write the transaction message, and call cims to purge the message queue.

Given

A fully prepared GCX148 transaction with all required parameters

When

The system executes the cargo arrival transaction

Then

The system should call CIMS to change message status, call WRITMSGL to write the transaction message, and call CIMS to purge the message queue

R-GCCINARR-cbl-00513 All Ports Processing?

Decision Rules

Business View: Assuming port code needs to be determined for cargo arrival processing during the 'All Ports Processing?' routine, when either all-ports-yes flag is set for aei or clv processing, the system executes logic to ensure that system proceeds to calculate port code based on manifest information.

Given

Port code needs to be determined for cargo arrival processing

When

Either all-ports-yes flag is set for AEI or CLV processing

Then

System proceeds to calculate port code based on manifest information

R-GCCINARR-cbl-00514 Calculate Port Code Based on Manifest

Computation Rules

Business View: Assuming all-ports processing is authorized during the 'Calculate Port Code Based on Manifest' routine, when port code calculation is required, the system executes logic to ensure that system calculates port code using manifest destination or manifest-to station information.

Given

All-ports processing is authorized

When

Port code calculation is required

Then

System calculates port code using manifest destination or manifest-to station information

R-GCCINARR-cbl-00517 Calculate Port Code Dynamically

Computation Rules

Business View: <EXCLUSION CRITERIA> If transaction did not originate from clv or no pre-calculated port code exists, and port code determination is required occurs during the 'Calculate Port Code Dynamically' routine, then the system must guarantee that system dynamically calculates port code using current manifest information.

EXCLUDING

Transaction did not originate from CLV or no pre-calculated port code exists

When

Port code determination is required

Then

System dynamically calculates port code using current manifest information

R-GCCINARR-cbl-00518 Prepare Transaction Message

Process Rules

Business View: Assuming all gcx148 transaction parameters have been configured during the 'Prepare Transaction Message' routine, when message preparation is required, the system executes logic to ensure that transaction input parameters are formatted into the message structure for queue transmission.

Given

All GCX148 transaction parameters have been configured

When

Message preparation is required

Then

Transaction input parameters are formatted into the message structure for queue transmission

R-GCCINARR-cbl-00519 Send Transaction to Message Queue

Action Rules

Business View: Assuming transaction message has been prepared with all required parameters during the 'Send Transaction to Message Queue' routine, when transaction needs to be submitted for processing, the system executes logic to ensure that message is sent to cims processing queue, written to message log, and queue is purged.

Given

Transaction message has been prepared with all required parameters

When

Transaction needs to be submitted for processing

Then

Message is sent to CIMS processing queue, written to message log, and queue is purged

R-GCCINARR-cbl-00520 Manifest destination is IIS-A6 or SPACES?

Decision Rules

Business View: Assuming a cargo record with manifest destination station information during the 'Manifest destination is IIS-A6 or SPACES?' routine, when the manifest destination station is 'iis-a6' or contains spaces, the system executes logic to ensure that the system should calculate the destination port code using the destination station lookup.

Given

A cargo record with manifest destination station information

When

The manifest destination station is 'IIS-A6' or contains SPACES

Then

The system should calculate the destination port code using the destination station lookup

R-GCCINARR-cbl-00523 Look up manifest station in MC table

Action Rules

Business View: <EXCLUSION CRITERIA> If a cargo record with manifest destination station that is not 'iis-a6' or spaces, and the system needs to determine the manifest port code occurs during the 'Look up manifest station in MC table' routine, then the system must guarantee that the system should look up the manifest destination station in the mc table.

EXCLUDING

A cargo record with manifest destination station that is not 'IIS-A6' or SPACES

When

The system needs to determine the manifest port code

Then

The system should look up the manifest destination station in the MC table

R-GCCINARR-cbl-00524 Extract Canadian customs code from MC table

Computation Rules

Business View: Assuming a successful lookup of manifest station in mc table during the 'Extract Canadian customs code from MC table' routine, when the mc table contains a matching record for the manifest station, the system executes logic to ensure that the system should extract the canadian customs code from positions 2-4 of the customs code field and assign it as the port code.

Given

A successful lookup of manifest station in MC table

When

The MC table contains a matching record for the manifest station

Then

The system should extract the Canadian customs code from positions 2-4 of the customs code field and assign it as the port code

R-GCCINARR-cbl-00659 CM Station Table Lookup - Retrieve destination station details from CM table and extract port code for cargo arrival processing

Action Rules

Business View: Assuming a cargo record with a destination station number exists and requires port code determination for arrival processing during the 'CM Station Table Lookup - Retrieve destination station details from CM table and extract port code for cargo arrival processing' routine, when the system performs cm station table lookup using the cargo destination station number, the system executes logic to ensure that the system retrieves the cm station segment and extracts the port code from the cm record for assignment to the cargo arrival transaction.

Given

A cargo record with a destination station number exists and requires port code determination for arrival processing

When

The system performs CM station table lookup using the cargo destination station number

Then

The system retrieves the CM station segment and extracts the port code from the CM record for assignment to the cargo arrival transaction

R-GCCINARR-cbl-00665 Retrieve CM Station Segment

Process Rules

Business View: Assuming a cm table lookup successfully found a matching station record for the destination station number during the 'Retrieve CM Station Segment' routine, when the system processes the successful lookup result, the system executes logic to ensure that the system retrieves and stores the complete cm station segment data from the found record.

Given

A CM table lookup successfully found a matching station record for the destination station number

When

The system processes the successful lookup result

Then

The system retrieves and stores the complete CM station segment data from the found record

R-GCCINARR-cbl-00666 Extract Port Code from CM Record

Computation Rules

Business View: Assuming a cm station segment has been successfully retrieved containing station details during the 'Extract Port Code from CM Record' routine, when the system processes the cm station segment data, the system executes logic to ensure that the system extracts the port code field from the cm station record for use in cargo arrival processing.

Given

A CM station segment has been successfully retrieved containing station details

When

The system processes the CM station segment data

Then

The system extracts the port code field from the CM station record for use in cargo arrival processing

R-GCCINARR-cbl-00797 Initialize Search Parameters

Process Rules

Business View: Assuming a cm table lookup operation is initiated during the 'Initialize Search Parameters' routine, when the system prepares to search the cm table, the system executes logic to ensure that all search parameters, table keys, flags, and segment areas are cleared and initialized to empty values.

Given

A CM table lookup operation is initiated

When

The system prepares to search the CM table

Then

All search parameters, table keys, flags, and segment areas are cleared and initialized to empty values

R-GCCINARR-cbl-00801 Query Successful?

Validation Rules

Business View: Assuming a cm table database query has been executed during the 'Query Successful?' routine, when the system evaluates the query results, the system executes logic to ensure that if the query returns successful status, the system proceeds to retrieve cm segment data, otherwise the lookup process terminates.

Given

A CM table database query has been executed

When

The system evaluates the query results

Then

If the query returns successful status, the system proceeds to retrieve CM segment data, otherwise the lookup process terminates

R-GCCINARR-cbl-00802 Retrieve CM Segment Data

Process Rules

Business View: Assuming a cm table query has completed successfully during the 'Retrieve CM Segment Data' routine, when the system processes the query results, the system executes logic to ensure that the cm table segment data is retrieved and stored for further processing.

Given

A CM table query has completed successfully

When

The system processes the query results

Then

The CM table segment data is retrieved and stored for further processing

R-GCCINARR-cbl-00803 Extract Port Code from CM Table

Process Rules

Business View: Assuming cm table segment data has been successfully retrieved during the 'Extract Port Code from CM Table' routine, when the system processes the cm segment information, the system executes logic to ensure that the port code value is extracted from the cm table segment for assignment to the transaction.

Given

CM table segment data has been successfully retrieved

When

The system processes the CM segment information

Then

The port code value is extracted from the CM table segment for assignment to the transaction

R-GCCINARR-cbl-00900 Execute Database Query - Perform CM table lookup with station key and handle success/failure conditions

Action Rules

Business View: Assuming a cargo record exists with a destination station number during the 'Execute Database Query - Perform CM table lookup with station key and handle success/failure conditions' routine, when the system performs a cm table lookup using the cargo destination station number as the key, the system executes logic to ensure that if the lookup is successful, the system extracts the port code from the cm segment and assigns it to the arrival transaction, otherwise the system continues processing without a port code.

Given

A cargo record exists with a destination station number

When

The system performs a CM table lookup using the cargo destination station number as the key

Then

If the lookup is successful, the system extracts the port code from the CM segment and assigns it to the arrival transaction, otherwise the system continues processing without a port code

R-GCCINARR-cbl-00668 Initialize MC Table Search Parameters

Process Rules

Business View: Assuming a manifest station lookup is required during the 'Initialize MC Table Search Parameters' routine, when the system initializes mc table search parameters, the system executes logic to ensure that all search keys, flags, and return indicators are cleared to ensure clean lookup operation.

Given

A manifest station lookup is required

When

The system initializes MC table search parameters

Then

All search keys, flags, and return indicators are cleared to ensure clean lookup operation

R-GCCINARR-cbl-00669 Set Table Type to MC

Action Rules

Business View: Assuming a manifest station lookup is being performed during the 'Set Table Type to MC' routine, when the system sets the table type for lookup, the system executes logic to ensure that the table type is configured to mc to access manifest and customs station data.

Given

A manifest station lookup is being performed

When

The system sets the table type for lookup

Then

The table type is configured to MC to access manifest and customs station data

R-GCCINARR-cbl-00670 Move Manifest To-Station Name to Search Key

Process Rules

Business View: Assuming a manifest contains a destination station name during the 'Move Manifest To-Station Name to Search Key' routine, when the system prepares to search the mc table, the system executes logic to ensure that the manifest destination station name is used as the search key for mc table lookup.

Given

A manifest contains a destination station name

When

The system prepares to search the MC table

Then

The manifest destination station name is used as the search key for MC table lookup

R-GCCINARR-cbl-00671 Execute MC Table Lookup

Action Rules

Business View: Assuming mc table search parameters are configured with manifest station name during the 'Execute MC Table Lookup' routine, when the system executes the mc table lookup, the system executes logic to ensure that the system attempts to retrieve the corresponding mc table record for the station.

Given

MC table search parameters are configured with manifest station name

When

The system executes the MC table lookup

Then

The system attempts to retrieve the corresponding MC table record for the station

R-GCCINARR-cbl-00672 MC Table Record Found?

Validation Rules

Business View: Assuming an mc table lookup has been executed for a manifest station during the 'MC Table Record Found?' routine, when the system checks the lookup result, the system executes logic to ensure that the system determines if a valid mc table record was found for the station.

Given

An MC table lookup has been executed for a manifest station

When

The system checks the lookup result

Then

The system determines if a valid MC table record was found for the station

R-GCCINARR-cbl-00673 Retrieve MC Segment Data

Process Rules

Business View: Assuming a valid mc table record has been found for the manifest station during the 'Retrieve MC Segment Data' routine, when the system retrieves the record data, the system executes logic to ensure that the complete mc segment data is extracted and made available for port code processing.

Given

A valid MC table record has been found for the manifest station

When

The system retrieves the record data

Then

The complete MC segment data is extracted and made available for port code processing

R-GCCINARR-cbl-00674 Extract Canadian Customs Code from Position 2-4

Computation Rules

Business View: Assuming mc segment data has been retrieved with canadian customs code field during the 'Extract Canadian Customs Code from Position 2-4' routine, when the system extracts the customs code, the system executes logic to ensure that characters from position 2 through 5 of the canadian customs code field are extracted as the port code.

Given

MC segment data has been retrieved with Canadian customs code field

When

The system extracts the customs code

Then

Characters from position 2 through 5 of the Canadian customs code field are extracted as the port code

R-GCCINARR-cbl-00806 Set Table Type to MC

Definitional Rules

Business View: Assuming database search parameters are initialized during the 'Set Table Type to MC' routine, when the system prepares to query for manifest station information, the system executes logic to ensure that the table type is set to mc to target the correct database table.

Given

Database search parameters are initialized

When

The system prepares to query for manifest station information

Then

The table type is set to MC to target the correct database table

R-GCCINARR-cbl-00807 Set Manifest Station as Search Key

Process Rules

Business View: Assuming the table type is set to mc and a clv manifest upon station is provided during the 'Set Manifest Station as Search Key' routine, when the system prepares the database query parameters, the system executes logic to ensure that the manifest upon station name is assigned as the port name search key.

Given

The table type is set to MC and a CLV manifest upon station is provided

When

The system prepares the database query parameters

Then

The manifest upon station name is assigned as the port name search key

R-GCCINARR-cbl-00808 Execute Database Query

Action Rules

Business View: Assuming search parameters are configured with mc table type and manifest station key during the 'Execute Database Query' routine, when the system executes the database query, the system executes logic to ensure that the database lookup is performed using the configured search parameters.

Given

Search parameters are configured with MC table type and manifest station key

When

The system executes the database query

Then

The database lookup is performed using the configured search parameters

R-GCCINARR-cbl-00810 Store MC Segment Data

Process Rules

Business View: Assuming a successful mc table database query result during the 'Store MC Segment Data' routine, when the system processes the query response, the system executes logic to ensure that the returned mc segment data is stored in the mc segment area.

Given

A successful MC table database query result

When

The system processes the query response

Then

The returned MC segment data is stored in the MC segment area

R-GCCINARR-cbl-00811 Extract Port Code from MC Record

Computation Rules

Business View: Assuming mc segment data is successfully retrieved and stored during the 'Extract Port Code from MC Record' routine, when the system processes the mc table information, the system executes logic to ensure that the canadian customs code characters 2 through 4 are extracted and stored as the temporary port code.

Given

MC segment data is successfully retrieved and stored

When

The system processes the MC table information

Then

The Canadian customs code characters 2 through 4 are extracted and stored as the temporary port code

R-GCCINARR-cbl-00813 Clear MC Segment Data

Process Rules

Business View: Assuming an mc table database query has failed during the 'Clear MC Segment Data' routine, when the system processes the failed query response, the system executes logic to ensure that the mc segment data area is cleared to empty values.

Given

An MC table database query has failed

When

The system processes the failed query response

Then

The MC segment data area is cleared to empty values

R-GCCINARR-cbl-00901 Initialize Database Query Parameters

Process Rules

Business View: Assuming a manifest station lookup is required during the 'Initialize Database Query Parameters' routine, when the system initializes database query parameters, the system executes logic to ensure that all database query fields are cleared and flags are reset to prepare for mc table access.

Given

A manifest station lookup is required

When

The system initializes database query parameters

Then

All database query fields are cleared and flags are reset to prepare for MC table access

R-GCCINARR-cbl-00902 Set Table Type to MC

Definitional Rules

Business View: Assuming database query parameters are initialized during the 'Set Table Type to MC' routine, when the system configures the table type for lookup, the system executes logic to ensure that the query is set to access the mc table type for manifest station data.

Given

Database query parameters are initialized

When

The system configures the table type for lookup

Then

The query is set to access the MC table type for manifest station data

R-GCCINARR-cbl-00903 Set Manifest Station as Search Key

Process Rules

Business View: Assuming the mc table type is configured and manifest upon station is available during the 'Set Manifest Station as Search Key' routine, when the system sets the search key for database lookup, the system executes logic to ensure that the manifest upon station name is assigned as the port name search key for mc table query.

Given

The MC table type is configured and manifest upon station is available

When

The system sets the search key for database lookup

Then

The manifest upon station name is assigned as the port name search key for MC table query

R-GCCINARR-cbl-00904 Execute Database Query

Action Rules

Business View: Assuming database query parameters are configured with mc table type and manifest station search key during the 'Execute Database Query' routine, when the system executes the database query, the system executes logic to ensure that the database lookup is performed against the mc table to find matching station records.

Given

Database query parameters are configured with MC table type and manifest station search key

When

The system executes the database query

Then

The database lookup is performed against the MC table to find matching station records

R-GCCINARR-cbl-00907 Extract Sub-location Code

Process Rules

Business View: Assuming mc table query was successful and station data is available during the 'Extract Sub-location Code' routine, when the system extracts configuration data from the mc table segment, the system executes logic to ensure that the sub-location code is retrieved from the mc segment for subsequent location validation processing.

Given

MC table query was successful and station data is available

When

The system extracts configuration data from the MC table segment

Then

The sub-location code is retrieved from the MC segment for subsequent location validation processing

R-GCCINARR-cbl-00908 Extract Port Code for Processing

Process Rules

Business View: Assuming mc table segment data is available with station configuration during the 'Extract Port Code for Processing' routine, when the system extracts port code information, the system executes logic to ensure that the canadian customs code characters 2 through 4 are extracted and stored as the port code for processing.

Given

MC table segment data is available with station configuration

When

The system extracts port code information

Then

The Canadian customs code characters 2 through 4 are extracted and stored as the port code for processing

R-GCCINARR-cbl-00911 Clear MC Segment Data

Process Rules

Business View: Assuming mc table lookup failed and no valid station data was found during the 'Clear MC Segment Data' routine, when the system handles the lookup failure, the system executes logic to ensure that the mc segment data area is cleared with spaces to prevent processing with invalid station information.

Given

MC table lookup failed and no valid station data was found

When

The system handles the lookup failure

Then

The MC segment data area is cleared with spaces to prevent processing with invalid station information

R-GCCINARR-cbl-00912 Set Processing Flag to Stop

Authorization Rules

Business View: Assuming mc table lookup failed and no valid station configuration is available during the 'Set Processing Flag to Stop' routine, when the system determines processing authorization, the system executes logic to ensure that the clv processing flag is set to stop preventing cargo arrival processing from proceeding.

Given

MC table lookup failed and no valid station configuration is available

When

The system determines processing authorization

Then

The CLV processing flag is set to stop preventing cargo arrival processing from proceeding

R-GCCINARR-cbl-00525 Initialize GCX148 Input Parameters

Process Rules

Business View: Assuming a cargo arrival transaction needs to be executed during the 'Initialize GCX148 Input Parameters' routine, when the system prepares to send the transaction message, the system executes logic to ensure that all gcx148 input parameters are initialized to blank values.

Given

A cargo arrival transaction needs to be executed

When

The system prepares to send the transaction message

Then

All GCX148 input parameters are initialized to blank values

R-GCCINARR-cbl-00535 Prepare Message for Queue

Process Rules

Business View: Assuming all transaction parameters have been set including port code during the 'Prepare Message for Queue' routine, when the message needs to be prepared for queue submission, the system executes logic to ensure that the gcx148 input structure is moved to the message area for queue processing.

Given

All transaction parameters have been set including port code

When

The message needs to be prepared for queue submission

Then

The GCX148 input structure is moved to the message area for queue processing

R-GCCINARR-cbl-00536 Call CIMS to Change Message Queue Status

Action Rules

Business View: Assuming a transaction message is ready to be sent to the queue during the 'Call CIMS to Change Message Queue Status' routine, when the message queue needs to be prepared for transmission, the system executes logic to ensure that the cims program is called with chng function to change the queue status using the alternate pcb.

Given

A transaction message is ready to be sent to the queue

When

The message queue needs to be prepared for transmission

Then

The CIMS program is called with CHNG function to change the queue status using the alternate PCB

R-GCCINARR-cbl-00537 Write Message to Queue via WRITMSGL

Action Rules

Business View: Assuming the message queue status has been changed and message is prepared during the 'Write Message to Queue via WRITMSGL' routine, when the transaction message needs to be transmitted, the system executes logic to ensure that the writmsgl program is called to write the message with its code, content, length and module name to the queue using alternate pcb.

Given

The message queue status has been changed and message is prepared

When

The transaction message needs to be transmitted

Then

The WRITMSGL program is called to write the message with its code, content, length and module name to the queue using alternate PCB

R-GCCINARR-cbl-00538 Purge Message Queue via CIMS

Action Rules

Business View: Assuming the transaction message has been successfully written to the queue during the 'Purge Message Queue via CIMS' routine, when queue cleanup is required, the system executes logic to ensure that the cims program is called with purg function to purge the queue using the alternate pcb.

Given

The transaction message has been successfully written to the queue

When

Queue cleanup is required

Then

The CIMS program is called with PURG function to purge the queue using the alternate PCB

R-GCCINARR-cbl-00185 Manifest destination is IIS-A6 or SPACES?

Decision Rules

Business View: Assuming a cargo manifest with a destination station name during the 'Manifest destination is IIS-A6 or SPACES?' routine, when the manifest destination station name is 'iis-a6' or contains spaces, the system executes logic to ensure that the system should calculate port code based on the destination station method.

Given

A cargo manifest with a destination station name

When

The manifest destination station name is 'IIS-A6' or contains SPACES

Then

The system should calculate port code based on the destination station method

R-GCCINARR-cbl-00186 Calculate Port Code Based on Destination

Action Rules

Business View: Assuming a cargo manifest where destination station name is 'iis-a6' or spaces during the 'Calculate Port Code Based on Destination' routine, when port code calculation is required, the system executes logic to ensure that the system should invoke the destination station port code calculation method.

Given

A cargo manifest where destination station name is 'IIS-A6' or SPACES

When

Port code calculation is required

Then

The system should invoke the destination station port code calculation method

R-GCCINARR-cbl-00187 Calculate Port Code Based on Manifest

Action Rules

Business View: <EXCLUSION CRITERIA> If a cargo manifest where destination station name is not 'iis-a6' and not spaces, and port code calculation is required occurs during the 'Calculate Port Code Based on Manifest' routine, then the system must guarantee that the system should invoke the manifest station port code calculation method.

EXCLUDING

A cargo manifest where destination station name is not 'IIS-A6' and not SPACES

When

Port code calculation is required

Then

The system should invoke the manifest station port code calculation method

R-GCCINARR-cbl-00191 Look up Manifest Station in MC Table

Action Rules

Business View: Assuming a cargo with a manifest destination station name during the 'Look up Manifest Station in MC Table' routine, when using manifest station method for port code calculation, the system executes logic to ensure that the system should query the mc table using the manifest destination station name as the key.

Given

A cargo with a manifest destination station name

When

Using manifest station method for port code calculation

Then

The system should query the MC table using the manifest destination station name as the key

R-GCCINARR-cbl-00192 Station found in MC table?

Validation Rules

Business View: Assuming a manifest destination station name has been used to query the mc table during the 'Station found in MC table?' routine, when the table lookup operation completes, the system executes logic to ensure that the system should determine if the station was successfully found in the mc table.

Given

A manifest destination station name has been used to query the MC table

When

The table lookup operation completes

Then

The system should determine if the station was successfully found in the MC table

R-GCCINARR-cbl-00193 Extract Canadian Customs Code from MC Table

Computation Rules

Business View: Assuming a manifest station that exists in the mc table during the 'Extract Canadian Customs Code from MC Table' routine, when the mc table lookup is successful, the system executes logic to ensure that the system should extract the canadian customs code from positions 2 through 4 of the mc table record.

Given

A manifest station that exists in the MC table

When

The MC table lookup is successful

Then

The system should extract the Canadian customs code from positions 2 through 4 of the MC table record

R-GCCINARR-cbl-00195 Manifest destination is IIS-A6 or SPACES?

Decision Rules

Business View: Assuming a cargo manifest requires port code assignment for arrival processing during the 'Manifest destination is IIS-A6 or SPACES?' routine, when the manifest destination station is 'iis-a6' or contains no value (spaces), the system executes logic to ensure that the system uses destination port code calculation logic.

Given

A cargo manifest requires port code assignment for arrival processing

When

The manifest destination station is 'IIS-A6' or contains no value (SPACES)

Then

The system uses destination port code calculation logic

R-GCCINARR-cbl-00196 Look up Destination Station in CM Table

Action Rules

Business View: Assuming destination port code logic is selected and cargo has a destination station number during the 'Look up Destination Station in CM Table' routine, when the system performs a lookup in the cm table using the destination station number, the system executes logic to ensure that the system attempts to retrieve the corresponding port code from the cm table segment.

Given

Destination port code logic is selected and cargo has a destination station number

When

The system performs a lookup in the CM table using the destination station number

Then

The system attempts to retrieve the corresponding port code from the CM table segment

R-GCCINARR-cbl-00198 Look up Manifest Station in MC Table

Action Rules

Business View: Assuming manifest port code logic is selected and cargo has a manifest destination station name during the 'Look up Manifest Station in MC Table' routine, when the system performs a lookup in the mc table using the manifest destination station name, the system executes logic to ensure that the system attempts to retrieve the corresponding port information from the mc table segment.

Given

Manifest port code logic is selected and cargo has a manifest destination station name

When

The system performs a lookup in the MC table using the manifest destination station name

Then

The system attempts to retrieve the corresponding port information from the MC table segment

R-GCCINARR-cbl-00199 Extract Canadian Customs Code

Computation Rules

Business View: Assuming mc table lookup was successful and returned customs code information during the 'Extract Canadian Customs Code' routine, when the system processes the canadian customs code from the mc table segment, the system executes logic to ensure that the system extracts characters 2 through 4 from the canadian customs code field.

Given

MC table lookup was successful and returned customs code information

When

The system processes the Canadian customs code from the MC table segment

Then

The system extracts characters 2 through 4 from the Canadian customs code field

R-GCCINARR-cbl-00200 Assign MC Port Code to GCX148

Action Rules

Business View: Assuming mc table lookup was successful and canadian customs code was extracted during the 'Assign MC Port Code to GCX148' routine, when the system completes the manifest port code processing, the system executes logic to ensure that the system assigns the extracted canadian customs code to the gcx148 port code field for arrival processing.

Given

MC table lookup was successful and Canadian customs code was extracted

When

The system completes the manifest port code processing

Then

The system assigns the extracted Canadian customs code to the GCX148 port code field for arrival processing

R-GCCINARR-cbl-00206 Retrieve CM Segment Data

Process Rules

Business View: Assuming the station table lookup was successful during the 'Retrieve CM Segment Data' routine, when the system processes the table response, the system executes logic to ensure that the cm segment data is moved from the table response to the working storage area.

Given

The station table lookup was successful

When

The system processes the table response

Then

The CM segment data is moved from the table response to the working storage area

R-GCCINARR-cbl-00207 Extract Port Code from CM Segment

Process Rules

Business View: Assuming the cm segment data has been retrieved successfully during the 'Extract Port Code from CM Segment' routine, when the system processes the segment data, the system executes logic to ensure that the port code is extracted from the cm segment port code field.

Given

The CM segment data has been retrieved successfully

When

The system processes the segment data

Then

The port code is extracted from the CM segment port code field

R-GCCINARR-cbl-00208 Assign Port Code to Transaction

Process Rules

Business View: Assuming a valid port code has been extracted from the cm segment during the 'Assign Port Code to Transaction' routine, when the system completes the port code assignment process, the system executes logic to ensure that the port code is assigned to the transaction's port code field.

Given

A valid port code has been extracted from the CM segment

When

The system completes the port code assignment process

Then

The port code is assigned to the transaction's port code field

R-GCCINARR-cbl-00209 Initialize Table Access Parameters

Process Rules

Business View: Assuming the system needs to lookup manifest port code information during the 'Initialize Table Access Parameters' routine, when the manifest port code assignment process begins, the system executes logic to ensure that all table access parameters are cleared including gcstbrt key, gcstbdp key, second pcb flag, unqualified ssa flag, and return flag.

Given

The system needs to lookup manifest port code information

When

The manifest port code assignment process begins

Then

All table access parameters are cleared including GCSTBRT key, GCSTBDP key, second PCB flag, unqualified SSA flag, and return flag

R-GCCINARR-cbl-00210 Set Table Type to MC - Manifest Code

Definitional Rules

Business View: Assuming table access parameters have been initialized during the 'Set Table Type to MC - Manifest Code' routine, when the system prepares to lookup manifest port information, the system executes logic to ensure that the table type is set to gcstbrt-table-mc to access the manifest code table.

Given

Table access parameters have been initialized

When

The system prepares to lookup manifest port information

Then

The table type is set to GCSTBRT-TABLE-MC to access the Manifest Code table

R-GCCINARR-cbl-00211 Extract Manifest To-Station Name from Cargo

Process Rules

Business View: Assuming a cargo record with manifest information exists during the 'Extract Manifest To-Station Name from Cargo' routine, when the system needs to determine the port code for manifest processing, the system executes logic to ensure that the manifest to-station name is extracted from the cargo record and assigned to the mc port name lookup key.

Given

A cargo record with manifest information exists

When

The system needs to determine the port code for manifest processing

Then

The manifest to-station name is extracted from the cargo record and assigned to the MC port name lookup key

R-GCCINARR-cbl-00212 Search MC Table by Port Name

Action Rules

Business View: Assuming the mc table type is set and the manifest to-station name is available during the 'Search MC Table by Port Name' routine, when the system executes the table lookup operation, the system executes logic to ensure that a database search is performed against the mc table using the port name as the lookup key.

Given

The MC table type is set and the manifest to-station name is available

When

The system executes the table lookup operation

Then

A database search is performed against the MC table using the port name as the lookup key

R-GCCINARR-cbl-00214 Retrieve MC Segment Data

Process Rules

Business View: Assuming an mc table entry has been successfully found for the port name during the 'Retrieve MC Segment Data' routine, when the system processes the successful lookup result, the system executes logic to ensure that the complete mc segment data is retrieved and stored from the table lookup result.

Given

An MC table entry has been successfully found for the port name

When

The system processes the successful lookup result

Then

The complete MC segment data is retrieved and stored from the table lookup result

R-GCCINARR-cbl-00215 Extract Canadian Customs Code from Position 2-4

Computation Rules

Business View: Assuming mc segment data has been successfully retrieved during the 'Extract Canadian Customs Code from Position 2-4' routine, when the system processes the customs code information, the system executes logic to ensure that characters 2 through 5 are extracted from the canadian customs code field in the mc segment.

Given

MC segment data has been successfully retrieved

When

The system processes the customs code information

Then

Characters 2 through 5 are extracted from the Canadian customs code field in the MC segment

R-GCCINARR-cbl-00216 Assign Port Code to GCX148 Transaction

Process Rules

Business View: Assuming the canadian customs code has been successfully extracted from the mc segment during the 'Assign Port Code to GCX148 Transaction' routine, when the system prepares the arrival transaction data, the system executes logic to ensure that the extracted customs code is assigned to the port code field in the gcx148 transaction.

Given

The Canadian customs code has been successfully extracted from the MC segment

When

The system prepares the arrival transaction data

Then

The extracted customs code is assigned to the port code field in the GCX148 transaction

R-GCCINARR-cbl-00218 Set Lifted Early Flag

Action Rules

Business View: Assuming equipment has tyes code '1' indicating lifted early condition during the 'Set Lifted Early Flag' routine, when the system processes the lifted early exception, the system executes logic to ensure that the system sets aei report as required and assigns lifted early exception message.

Given

Equipment has TYES code '1' indicating lifted early condition

When

The system processes the lifted early exception

Then

The system sets AEI report as required and assigns lifted early exception message

R-GCCINARR-cbl-00219 Set Not Lifted Flag

Action Rules

Business View: <EXCLUSION CRITERIA> If equipment has tyes code '2' indicating not lifted condition, and the system processes the not lifted exception occurs during the 'Set Not Lifted Flag' routine, then the system must guarantee that the system sets aei report as required and assigns not lifted exception message.

EXCLUDING

Equipment has TYES code '2' indicating not lifted condition

When

The system processes the not lifted exception

Then

The system sets AEI report as required and assigns not lifted exception message

R-GCCINARR-cbl-00220 Set Not Set Out Flag

Action Rules

Business View: <EXCLUSION CRITERIA> If equipment has tyes code '4' indicating not set out condition, and the system processes the not set out exception occurs during the 'Set Not Set Out Flag' routine, then the system must guarantee that the system sets aei report as required and assigns not set out exception message.

EXCLUDING

Equipment has TYES code '4' indicating not set out condition

When

The system processes the not set out exception

Then

The system sets AEI report as required and assigns not set out exception message

R-GCCINARR-cbl-00221 Set Not On 9PLAN Flag

Action Rules

Business View: <EXCLUSION CRITERIA> If equipment has tyes code '5' indicating not on 9plan condition, and the system processes the not on 9plan exception occurs during the 'Set Not On 9PLAN Flag' routine, then the system must guarantee that the system sets aei report as required and assigns not on 9plan exception message.

EXCLUDING

Equipment has TYES code '5' indicating not on 9PLAN condition

When

The system processes the not on 9PLAN exception

Then

The system sets AEI report as required and assigns not on 9PLAN exception message

R-GCCINARR-cbl-00222 Set Container Exception Message

Process Rules

Business View: <EXCLUSION CRITERIA> If equipment processing involves containers and exception conditions exist, and the system assigns exception messages for containers occurs during the 'Set Container Exception Message' routine, then the system must guarantee that the system places the appropriate exception message in the container exception message field based on the exception type.

EXCLUDING

Equipment processing involves containers and exception conditions exist

When

The system assigns exception messages for containers

Then

The system places the appropriate exception message in the container exception message field based on the exception type

R-GCCINARR-cbl-00223 Set Equipment Exception Message

Process Rules

Business View: <EXCLUSION CRITERIA> If equipment processing involves non-container equipment and exception conditions exist, and the system assigns exception messages for equipment occurs during the 'Set Equipment Exception Message' routine, then the system must guarantee that the system places the appropriate exception message in the equipment exception message field based on the exception type.

EXCLUDING

Equipment processing involves non-container equipment and exception conditions exist

When

The system assigns exception messages for equipment

Then

The system places the appropriate exception message in the equipment exception message field based on the exception type

R-GCCINARR-cbl-00224 Set AEI Report Required

Action Rules

Business View: <EXCLUSION CRITERIA> If equipment has border arrival issues such as not arrived at border or not acknowledged at border, and the system processes border arrival exceptions occurs during the 'Set AEI Report Required' routine, then the system must guarantee that the system sets aei report as required and assigns appropriate border-related exception messages.

EXCLUDING

Equipment has border arrival issues such as not arrived at border or not acknowledged at border

When

The system processes border arrival exceptions

Then

The system sets AEI report as required and assigns appropriate border-related exception messages

R-GCCINARR-cbl-00225 Set AEI Report Required

Action Rules

Business View: Assuming equipment has cargo in error status during the 'Set AEI Report Required' routine, when the system processes cargo error exceptions, the system executes logic to ensure that the system sets aei report as required and assigns cargo error exception message.

Given

Equipment has cargo in error status

When

The system processes cargo error exceptions

Then

The system sets AEI report as required and assigns cargo error exception message

R-GCCINARR-cbl-00226 Set AEI Report Required

Action Rules

Business View: Assuming equipment is a follower manifest and the master manifest has already arrived during the 'Set AEI Report Required' routine, when the system processes master arrived follower exceptions, the system executes logic to ensure that the system sets aei report as required and assigns master arrived exception message.

Given

Equipment is a follower manifest and the master manifest has already arrived

When

The system processes master arrived follower exceptions

Then

The system sets AEI report as required and assigns master arrived exception message

R-GCCINARR-cbl-00230 Check access conditions

Authorization Rules

Business View: Assuming clv report generation is in progress and access validation has been performed during the 'Check access conditions' routine, when the system evaluates access control conditions, the system executes logic to ensure that if scac access is invalid, display scac invalid message with carrier code; if user has no access rights, display user access denied message; if mc table entry is not found, display no mc table entry message with manifest location; otherwise proceed with normal equipment processing.

Given

CLV report generation is in progress and access validation has been performed

When

The system evaluates access control conditions

Then

If SCAC access is invalid, display SCAC invalid message with carrier code; if user has no access rights, display user access denied message; if MC table entry is not found, display no MC table entry message with manifest location; otherwise proceed with normal equipment processing

R-GCCINARR-cbl-00231 Process equipment detail lines

Process Rules

Business View: Assuming clv report has valid access and equipment array contains arrival details during the 'Process equipment detail lines' routine, when the system processes equipment entries up to 999 items, the system executes logic to ensure that for each non-empty equipment entry, format equipment number and exception message, assign sequence number from array index, create equipment detail line with type space, and send to terminal.

Given

CLV report has valid access and equipment array contains arrival details

When

The system processes equipment entries up to 999 items

Then

For each non-empty equipment entry, format equipment number and exception message, assign sequence number from array index, create equipment detail line with type space, and send to terminal

R-GCCINARR-cbl-00232 Has containers?

Process Rules

Business View: Assuming an equipment item is being processed and may have associated containers during the 'Has containers?' routine, when the system checks for container information up to 30 containers per equipment, the system executes logic to ensure that for each non-empty container entry, format container number and exception message, assign sequence number from container index, create container detail line with type 'c', and send to terminal.

Given

An equipment item is being processed and may have associated containers

When

The system checks for container information up to 30 containers per equipment

Then

For each non-empty container entry, format container number and exception message, assign sequence number from container index, create container detail line with type 'C', and send to terminal

R-GCCINARR-cbl-00233 Send equipment detail line

Action Rules

Business View: Assuming a formatted report line is ready for transmission and destination terminal is determined during the 'Send equipment detail line' routine, when the system sends the report line, the system executes logic to ensure that call gcstonly service with destination terminal, common communication area, alternate pcb, call letters, and formatted line content.

Given

A formatted report line is ready for transmission and destination terminal is determined

When

The system sends the report line

Then

Call GCSTONLY service with destination terminal, common communication area, alternate PCB, call letters, and formatted line content

R-GCCINARR-cbl-00553 Check SCAC Access Status

Authorization Rules

Business View: <EXCLUSION CRITERIA> If a clv report generation request is initiated, and the system checks scac access status and finds it is invalid occurs during the 'Check SCAC Access Status' routine, then the system must guarantee that the system should set the carrier scac code in the error message, generate scac invalid message, and send the error to the terminal.

EXCLUDING

A CLV report generation request is initiated

When

The system checks SCAC access status and finds it is invalid

Then

The system should set the carrier SCAC code in the error message, generate SCAC invalid message, and send the error to the terminal

R-GCCINARR-cbl-00554 Check User Access Status

Authorization Rules

Business View: Assuming scac access is valid for clv report generation during the 'Check User Access Status' routine, when the system checks user access status and finds the user has no access permissions, the system executes logic to ensure that the system should generate a user no access message and send the user access error to the terminal.

Given

SCAC access is valid for CLV report generation

When

The system checks user access status and finds the user has no access permissions

Then

The system should generate a user no access message and send the user access error to the terminal

R-GCCINARR-cbl-00555 Check MC Table Match Status

Validation Rules

Business View: Assuming user has valid access permissions for clv report generation during the 'Check MC Table Match Status' routine, when the system checks mc table match status and finds no matching entry exists, the system executes logic to ensure that the system should set the manifest station in the error message, generate mc table entry missing message, and send the mc table error to the terminal.

Given

User has valid access permissions for CLV report generation

When

The system checks MC table match status and finds no matching entry exists

Then

The system should set the manifest station in the error message, generate MC table entry missing message, and send the MC table error to the terminal

R-GCCINARR-cbl-00683 Include SCAC Code in Error Message

Validation Rules

Business View: Assuming scac access is invalid and clv report generation is required during the 'Include SCAC Code in Error Message' routine, when error message needs to be generated, the system executes logic to ensure that the system includes the cp scac code in the clv invalid access error message.

Given

SCAC access is invalid and CLV report generation is required

When

Error message needs to be generated

Then

The system includes the CP SCAC code in the CLV invalid access error message

R-GCCINARR-cbl-00684 Display SCAC Invalid Message

Process Rules

Business View: Assuming scac error message has been generated with scac code details during the 'Display SCAC Invalid Message' routine, when clv report is being created, the system executes logic to ensure that the system displays the scac invalid access message in the report output.

Given

SCAC error message has been generated with SCAC code details

When

CLV report is being created

Then

The system displays the SCAC invalid access message in the report output

R-GCCINARR-cbl-00695 Display User Has No Access Message

Process Rules

Business View: Assuming a user has been denied access to cargo arrival processing functionality during the 'Display User Has No Access Message' routine, when the system generates the clv report, the system executes logic to ensure that the system displays a 'user has no access' message in the report instead of processing cargo arrival data.

Given

A user has been denied access to cargo arrival processing functionality

When

The system generates the CLV report

Then

The system displays a 'user has no access' message in the report instead of processing cargo arrival data

R-GCCINARR-cbl-00822 Check CCF Arrive Permission Level

Authorization Rules

Business View: Assuming a user security segment with ccf arrive permission field during the 'Check CCF Arrive Permission Level' routine, when the ccf arrive permission equals super user access or user access, the system executes logic to ensure that the system grants user access, otherwise denies access.

Given

A user security segment with CCF arrive permission field

When

The CCF arrive permission equals super user access or user access

Then

The system grants user access, otherwise denies access

R-GCCINARR-cbl-00824 User Record Found?

Decision Rules

Business View: <EXCLUSION CRITERIA> If a search operation on user security table, and the user record is not found in the table occurs during the 'User Record Found?' routine, then the system must guarantee that the system clears user security segment and sets no user access flag.

EXCLUDING

A search operation on user security table

When

The user record is not found in the table

Then

The system clears user security segment and sets no user access flag

R-GCCINARR-cbl-00914 Clear Return Flags and Segments

Validation Rules

Business View: Assuming a table operation is about to be executed during the 'Clear Return Flags and Segments' routine, when the system prepares for the table call, the system executes logic to ensure that return flags and table segment areas are initialized to prevent data contamination from previous operations.

Given

A table operation is about to be executed

When

The system prepares for the table call

Then

Return flags and table segment areas are initialized to prevent data contamination from previous operations

R-GCCINARR-cbl-00917 Table Record Retrieved Successfully

Process Rules

Business View: Assuming a table search operation completed successfully during the 'Table Record Retrieved Successfully' routine, when the gcwtbio-successfull flag indicates success, the system executes logic to ensure that the returned table segment data is moved from gcwtbio-gctab-segment to the appropriate target segment area for further processing.

Given

A table search operation completed successfully

When

The GCWTBIO-SUCCESSFULL flag indicates success

Then

The returned table segment data is moved from GCWTBIO-GCTAB-SEGMENT to the appropriate target segment area for further processing

R-GCCINARR-cbl-00918 Table Record Not Found

Process Rules

Business View: <EXCLUSION CRITERIA> If a table search operation has been executed, and the gcwtbio-successfull flag indicates the record was not found occurs during the 'Table Record Not Found' routine, then the system must guarantee that target segment areas are cleared to spaces and appropriate not-found flags are set to indicate the unsuccessful search result.

EXCLUDING

A table search operation has been executed

When

The GCWTBIO-SUCCESSFULL flag indicates the record was not found

Then

Target segment areas are cleared to spaces and appropriate not-found flags are set to indicate the unsuccessful search result

R-GCCINARR-cbl-00696 Search MC Table for Station

Validation Rules

Business View: Assuming a manifest station name from clv equipment processing during the 'Search MC Table for Station' routine, when the system searches the mc table using the manifest station as the key, the system executes logic to ensure that the system retrieves the station record if it exists in the mc table.

Given

A manifest station name from CLV equipment processing

When

The system searches the MC table using the manifest station as the key

Then

The system retrieves the station record if it exists in the MC table

R-GCCINARR-cbl-00697 Set MC Table Match True

Decision Rules

Business View: Assuming a successful mc table lookup for a manifest station during the 'Set MC Table Match True' routine, when the station record is found in the mc table, the system executes logic to ensure that the system sets mc table match flag to true, enables clv processing, and extracts the sub-location code and port code from the station record.

Given

A successful MC table lookup for a manifest station

When

The station record is found in the MC table

Then

The system sets MC table match flag to true, enables CLV processing, and extracts the sub-location code and port code from the station record

R-GCCINARR-cbl-00698 Set MC Table Match False

Decision Rules

Business View: <EXCLUSION CRITERIA> If an unsuccessful mc table lookup for a manifest station, and the station record is not found in the mc table occurs during the 'Set MC Table Match False' routine, then the system must guarantee that the system sets mc table match flag to false and disables clv processing for the equipment.

EXCLUDING

An unsuccessful MC table lookup for a manifest station

When

The station record is not found in the MC table

Then

The system sets MC table match flag to false and disables CLV processing for the equipment

R-GCCINARR-cbl-00699 Extract Sub-location Code

Action Rules

Business View: Assuming a successful mc table lookup with a valid station record during the 'Extract Sub-location Code' routine, when the system processes the mc table segment data, the system executes logic to ensure that the system extracts the sub-location code and port code from positions 2-4 of the canadian customs code field.

Given

A successful MC table lookup with a valid station record

When

The system processes the MC table segment data

Then

The system extracts the sub-location code and port code from positions 2-4 of the Canadian customs code field

R-GCCINARR-cbl-00825 Initialize Search Parameters

Process Rules

Business View: Assuming a request to search mc table for manifest station during the 'Initialize Search Parameters' routine, when the search process begins, the system executes logic to ensure that all search parameters are cleared and mc table type flag is set.

Given

A request to search MC table for manifest station

When

The search process begins

Then

All search parameters are cleared and MC table type flag is set

R-GCCINARR-cbl-00827 Move Manifest Station to Search Key

Process Rules

Business View: Assuming mc table type is configured and manifest upon station is available during the 'Move Manifest Station to Search Key' routine, when preparing the search key for mc table lookup, the system executes logic to ensure that the manifest upon station value is assigned as the mc port name search key.

Given

MC table type is configured and manifest upon station is available

When

Preparing the search key for MC table lookup

Then

The manifest upon station value is assigned as the MC port name search key

R-GCCINARR-cbl-00828 Execute MC Table Lookup

Action Rules

Business View: Assuming mc table search is configured with manifest station as search key during the 'Execute MC Table Lookup' routine, when executing the mc table lookup, the system executes logic to ensure that the system calls the table lookup service to search for the manifest station.

Given

MC table search is configured with manifest station as search key

When

Executing the MC table lookup

Then

The system calls the table lookup service to search for the manifest station

R-GCCINARR-cbl-00829 Set MC Table Match True

Decision Rules

Business View: Assuming mc table lookup is executed during the 'Set MC Table Match True' routine, when the manifest station is found in the mc table, the system executes logic to ensure that the system sets mc table match flag to true and enables processing for clv.

Given

MC table lookup is executed

When

The manifest station is found in the MC table

Then

The system sets MC table match flag to true and enables processing for CLV

R-GCCINARR-cbl-00830 Extract MC Segment Data

Process Rules

Business View: Assuming mc table lookup is successful and match flag is set to true during the 'Extract MC Segment Data' routine, when processing the found mc table entry, the system executes logic to ensure that the system extracts the mc segment data from the lookup result.

Given

MC table lookup is successful and match flag is set to true

When

Processing the found MC table entry

Then

The system extracts the MC segment data from the lookup result

R-GCCINARR-cbl-00831 Extract Port Code from Customs Code

Computation Rules

Business View: Assuming mc segment data is extracted from successful table lookup during the 'Extract Port Code from Customs Code' routine, when processing the mc segment information, the system executes logic to ensure that the system extracts characters 2 through 4 from the canadian customs code as the port code.

Given

MC segment data is extracted from successful table lookup

When

Processing the MC segment information

Then

The system extracts characters 2 through 4 from the Canadian customs code as the port code

R-GCCINARR-cbl-00832 Set MC Table Match False

Decision Rules

Business View: <EXCLUSION CRITERIA> If mc table lookup is executed, and the manifest station is not found in the mc table occurs during the 'Set MC Table Match False' routine, then the system must guarantee that the system sets mc table match flag to false and disables processing for clv.

EXCLUDING

MC table lookup is executed

When

The manifest station is not found in the MC table

Then

The system sets MC table match flag to false and disables processing for CLV

R-GCCINARR-cbl-00833 Clear MC Segment Data

Process Rules

Business View: Assuming mc table lookup fails and match flag is set to false during the 'Clear MC Segment Data' routine, when handling the failed lookup result, the system executes logic to ensure that the system clears the mc segment data to spaces.

Given

MC table lookup fails and match flag is set to false

When

Handling the failed lookup result

Then

The system clears the MC segment data to spaces

R-GCCINARR-cbl-00919 Execute MC Table Lookup - Perform database search with manifest station key and process found/not found results

Validation Rules

Business View: Assuming a manifest station name is provided from clv input during the 'Execute MC Table Lookup - Perform database search with manifest station key and process found/not found results' routine, when the system searches the mc table using the manifest station as the key, the system executes logic to ensure that if mc table record is found, set processing flags to allow clv processing and extract port code; if not found, set flags to prevent clv processing.

Given

A manifest station name is provided from CLV input

When

The system searches the MC table using the manifest station as the key

Then

If MC table record is found, set processing flags to allow CLV processing and extract port code; if not found, set flags to prevent CLV processing

R-GCCINARR-cbl-00920 Initialize Database Search Parameters

Process Rules

Business View: Assuming mc table lookup is required during the 'Initialize Database Search Parameters' routine, when the system prepares for database search, the system executes logic to ensure that clear all search keys, flags, and segment areas to ensure clean search parameters.

Given

MC table lookup is required

When

The system prepares for database search

Then

Clear all search keys, flags, and segment areas to ensure clean search parameters

R-GCCINARR-cbl-00922 Move Manifest Station to Search Key

Process Rules

Business View: Assuming mc table type is configured and manifest station name is available during the 'Move Manifest Station to Search Key' routine, when the system prepares the search key, the system executes logic to ensure that move the clv manifest station name to the mc port name search field.

Given

MC table type is configured and manifest station name is available

When

The system prepares the search key

Then

Move the CLV manifest station name to the MC port name search field

R-GCCINARR-cbl-00923 Execute Database Search

Action Rules

Business View: Assuming all search parameters are configured with mc table type and manifest station key during the 'Execute Database Search' routine, when the system executes the database search, the system executes logic to ensure that perform table lookup operation and return success or failure status.

Given

All search parameters are configured with MC table type and manifest station key

When

The system executes the database search

Then

Perform table lookup operation and return success or failure status

R-GCCINARR-cbl-00924 MC Table Record Found

Decision Rules

Business View: Assuming mc table search is executed during the 'MC Table Record Found' routine, when a matching mc table record is found for the manifest station, the system executes logic to ensure that set mc table match flag to true, enable clv processing, store mc segment data, and extract port code from canadian customs code.

Given

MC table search is executed

When

A matching MC table record is found for the manifest station

Then

Set MC table match flag to TRUE, enable CLV processing, store MC segment data, and extract port code from Canadian customs code

R-GCCINARR-cbl-00925 MC Table Record Not Found

Decision Rules

Business View: Assuming mc table search is executed during the 'MC Table Record Not Found' routine, when no matching mc table record is found for the manifest station, the system executes logic to ensure that set mc table match flag to false, disable clv processing, and clear mc segment data.

Given

MC table search is executed

When

No matching MC table record is found for the manifest station

Then

Set MC table match flag to FALSE, disable CLV processing, and clear MC segment data

R-GCCINARR-cbl-00558 Move Equipment Number to Detail Line

Process Rules

Business View: Assuming an equipment record is being processed for clv report during the 'Move Equipment Number to Detail Line' routine, when the system formats the equipment detail line, the system executes logic to ensure that move equipment number, exception message, and formatted sequence number to the detail line structure.

Given

An equipment record is being processed for CLV report

When

The system formats the equipment detail line

Then

Move equipment number, exception message, and formatted sequence number to the detail line structure

R-GCCINARR-cbl-00562 Move Container Number to Detail Line

Process Rules

Business View: Assuming a container record is being processed for clv report during the 'Move Container Number to Detail Line' routine, when the system formats the container detail line, the system executes logic to ensure that move container number, container exception message, and formatted container sequence number to the detail line structure.

Given

A container record is being processed for CLV report

When

The system formats the container detail line

Then

Move container number, container exception message, and formatted container sequence number to the detail line structure

R-GCCINARR-cbl-00702 Move Exception Message to Detail Line

Process Rules

Business View: <EXCLUSION CRITERIA> If an equipment record has an associated exception message in the arrival array, and formatting the equipment detail line occurs during the 'Move Exception Message to Detail Line' routine, then the system must guarantee that the exception message should be moved to the detail line message field.

EXCLUDING

An equipment record has an associated exception message in the arrival array

When

Formatting the equipment detail line

Then

The exception message should be moved to the detail line message field

R-GCCINARR-cbl-00705 Format Complete Detail Line Structure

Process Rules

Business View: <EXCLUSION CRITERIA> If all individual components (equipment type, equipment number, exception message, sequence number) have been formatted, and creating the final detail line for output occurs during the 'Format Complete Detail Line Structure' routine, then the system must guarantee that the complete clv report detail line structure should be assembled and ready for output.

EXCLUDING

All individual components (equipment type, equipment number, exception message, sequence number) have been formatted

When

Creating the final detail line for output

Then

The complete CLV report detail line structure should be assembled and ready for output

R-GCCINARR-cbl-00709 Retrieve Container Exception Message

Process Rules

Business View: <EXCLUSION CRITERIA> If a container has been processed and may have associated exception messages, and the system formats container details for reporting occurs during the 'Retrieve Container Exception Message' routine, then the system must guarantee that the exception message must be retrieved from ws-arr-cont-excp-message array using the current equipment count and container sub-index.

EXCLUDING

A container has been processed and may have associated exception messages

When

The system formats container details for reporting

Then

The exception message must be retrieved from WS-ARR-CONT-EXCP-MESSAGE array using the current equipment count and container sub-index

R-GCCINARR-cbl-00710 Format Container Detail Line

Process Rules

Business View: <EXCLUSION CRITERIA> If container type indicator, sequence number, equipment number, and exception message are available, and the system creates a container detail line for the report occurs during the 'Format Container Detail Line' routine, then the system must guarantee that all container information must be formatted into the standard clv report detail line structure (ws-clv-report-det-line).

EXCLUDING

Container type indicator, sequence number, equipment number, and exception message are available

When

The system creates a container detail line for the report

Then

All container information must be formatted into the standard CLV report detail line structure (WS-CLV-REPORT-DET-LINE)

R-GCCINARR-cbl-00235 Initialize Email Parameters

Process Rules

Business View: Assuming an aei report needs to be generated during the 'Initialize Email Parameters' routine, when the email report generation process starts, the system executes logic to ensure that all email parameters are initialized to spaces or zero values including sender, recipients, subject, text, keywords, and message counters.

Given

An AEI report needs to be generated

When

The email report generation process starts

Then

All email parameters are initialized to spaces or zero values including sender, recipients, subject, text, keywords, and message counters

R-GCCINARR-cbl-00245 Format Equipment Number and Message

Computation Rules

Business View: <EXCLUSION CRITERIA> If equipment item has aei exception and needs to be reported, and formatting the equipment exception details occurs during the 'Format Equipment Number and Message' routine, then the system must guarantee that the equipment type is set to spaces, equipment number and exception message are populated, sequence number is derived from the last 3 digits of the equipment index, and the formatted line is added to the report.

EXCLUDING

Equipment item has AEI exception and needs to be reported

When

Formatting the equipment exception details

Then

The equipment type is set to spaces, equipment number and exception message are populated, sequence number is derived from the last 3 digits of the equipment index, and the formatted line is added to the report

R-GCCINARR-cbl-00248 Format Container Number and Message

Computation Rules

Business View: <EXCLUSION CRITERIA> If container has exception information and needs to be reported, and formatting the container exception details occurs during the 'Format Container Number and Message' routine, then the system must guarantee that the container type is set to 'c', sequence number is derived from the last 3 digits of the container index, container number and exception message are populated, and the formatted line is added to the report.

EXCLUDING

Container has exception information and needs to be reported

When

Formatting the container exception details

Then

The container type is set to 'C', sequence number is derived from the last 3 digits of the container index, container number and exception message are populated, and the formatted line is added to the report

R-GCCINARR-cbl-00565 Initialize Email Parameters

Process Rules

Business View: Assuming aei report generation is required during the 'Initialize Email Parameters' routine, when email setup process begins, the system executes logic to ensure that all email parameters including sender, recipients, subject, text, and message counters are cleared to spaces or zero.

Given

AEI report generation is required

When

Email setup process begins

Then

All email parameters including sender, recipients, subject, text, and message counters are cleared to spaces or zero

R-GCCINARR-cbl-00576 Initialize Email Parameters

Process Rules

Business View: Assuming an aei report needs to be generated during the 'Initialize Email Parameters' routine, when the report generation process starts, the system executes logic to ensure that all email parameters are initialized to spaces or zero and message counter is reset.

Given

An AEI report needs to be generated

When

The report generation process starts

Then

All email parameters are initialized to spaces or zero and message counter is reset

R-GCCINARR-cbl-00588 Add Equipment Detail Line

Process Rules

Business View: <EXCLUSION CRITERIA> If equipment has exceptions to report, and adding equipment detail to report occurs during the 'Add Equipment Detail Line' routine, then the system must guarantee that equipment line includes blank type indicator, equipment number, exception message, sequence number (last 3 digits of index), and line counter is incremented.

EXCLUDING

Equipment has exceptions to report

When

Adding equipment detail to report

Then

Equipment line includes blank type indicator, equipment number, exception message, sequence number (last 3 digits of index), and line counter is incremented

R-GCCINARR-cbl-00590 Add Container Detail Line with Type Indicator

Process Rules

Business View: Assuming equipment has containers to report during the 'Add Container Detail Line with Type Indicator' routine, when adding container detail to report, the system executes logic to ensure that container line includes 'c' type indicator, container number, exception message, sequence number (last 3 digits of container index), and line counter is incremented.

Given

Equipment has containers to report

When

Adding container detail to report

Then

Container line includes 'C' type indicator, container number, exception message, sequence number (last 3 digits of container index), and line counter is incremented

R-GCCINARR-cbl-00716 Move Exception Message to Report Line

Process Rules

Business View: <EXCLUSION CRITERIA> If an equipment item with an exception is being formatted for the aei report, and the exception message needs to be included in the report line occurs during the 'Move Exception Message to Report Line' routine, then the system must guarantee that the exception message from the equipment array should be moved to the report detail message field.

EXCLUDING

An equipment item with an exception is being formatted for the AEI report

When

The exception message needs to be included in the report line

Then

The exception message from the equipment array should be moved to the report detail message field

R-GCCINARR-cbl-00718 Format Equipment Detail Line

Process Rules

Business View: Assuming equipment type, number, message, and sequence have been populated during the 'Format Equipment Detail Line' routine, when the equipment detail line needs to be formatted for the report, the system executes logic to ensure that the aei report detail line should be constructed with all equipment information.

Given

Equipment type, number, message, and sequence have been populated

When

The equipment detail line needs to be formatted for the report

Then

The AEI report detail line should be constructed with all equipment information

R-GCCINARR-cbl-00726 Move Container Exception Message to Report Line

Process Rules

Business View: <EXCLUSION CRITERIA> If a container with an exception is being formatted for the aei report with equipment index x and container index ws-cn-sub, and the container exception message needs to be included in the report line occurs during the 'Move Container Exception Message to Report Line' routine, then the system must guarantee that the container exception message from the container array should be moved to the report detail message field.

EXCLUDING

A container with an exception is being formatted for the AEI report with equipment index X and container index WS-CN-SUB

When

The container exception message needs to be included in the report line

Then

The container exception message from the container array should be moved to the report detail message field

R-GCCINARR-cbl-00727 Format Container Detail Line

Process Rules

Business View: Assuming container type, number, message, and sequence have been populated during the 'Format Container Detail Line' routine, when the container detail line needs to be formatted for the report, the system executes logic to ensure that the aei report detail line should be constructed with all container information.

Given

Container type, number, message, and sequence have been populated

When

The container detail line needs to be formatted for the report

Then

The AEI report detail line should be constructed with all container information

R-GCCINARR-cbl-00837 Extract Exception Message from Array

Process Rules

Business View: <EXCLUSION CRITERIA> If an equipment item has an associated exception message in the arrival array, and the system formats the equipment detail line occurs during the 'Extract Exception Message from Array' routine, then the system must guarantee that the exception message is extracted from the arrival exception message array at the equipment index position.

EXCLUDING

An equipment item has an associated exception message in the arrival array

When

The system formats the equipment detail line

Then

The exception message is extracted from the arrival exception message array at the equipment index position

R-GCCINARR-cbl-00839 Construct Standardized Equipment Detail Line

Process Rules

Business View: <EXCLUSION CRITERIA> If equipment number, sequence number, and exception message are available, and the system formats the equipment detail line occurs during the 'Construct Standardized Equipment Detail Line' routine, then the system must guarantee that a standardized equipment detail line is constructed using the clv report detail line format.

EXCLUDING

Equipment number, sequence number, and exception message are available

When

The system formats the equipment detail line

Then

A standardized equipment detail line is constructed using the CLV report detail line format

R-GCCINARR-cbl-00845 Extract Container Exception Message

Process Rules

Business View: <EXCLUSION CRITERIA> If a container has an associated exception message in the arrival container array, and the system formats the container detail line occurs during the 'Extract Container Exception Message' routine, then the system must guarantee that the exception message is extracted from the arrival container exception message array using the equipment index and container sub-index.

EXCLUDING

A container has an associated exception message in the arrival container array

When

The system formats the container detail line

Then

The exception message is extracted from the arrival container exception message array using the equipment index and container sub-index

R-GCCINARR-cbl-00847 Construct Standardized Container Detail Line

Process Rules

Business View: <EXCLUSION CRITERIA> If container number, sequence number, and exception message are available, and the system formats the container detail line occurs during the 'Construct Standardized Container Detail Line' routine, then the system must guarantee that a standardized container detail line is constructed using the clv report detail line format.

EXCLUDING

Container number, sequence number, and exception message are available

When

The system formats the container detail line

Then

A standardized container detail line is constructed using the CLV report detail line format

R-GCCINARR-cbl-00930 Extract Exception Message from Array

Action Rules

Business View: Assuming equipment number has been extracted for position x during the 'Extract Exception Message from Array' routine, when the system extracts additional equipment data, the system executes logic to ensure that move ws-arr-exception-message at position x to ws-aei-det-message field.

Given

Equipment number has been extracted for position X

When

The system extracts additional equipment data

Then

Move WS-ARR-EXCEPTION-MESSAGE at position X to WS-AEI-DET-MESSAGE field

R-GCCINARR-cbl-00932 Format Equipment Detail Line

Action Rules

Business View: <EXCLUSION CRITERIA> If equipment number, exception message, and sequence number have been prepared, and the system formats the equipment detail line occurs during the 'Format Equipment Detail Line' routine, then the system must guarantee that set ws-aei-det-typ to spaces and move ws-aei-report-det-line to sd3-item-lines at position i.

EXCLUDING

Equipment number, exception message, and sequence number have been prepared

When

The system formats the equipment detail line

Then

Set WS-AEI-DET-TYP to SPACES and move WS-AEI-REPORT-DET-LINE to SD3-ITEM-LINES at position I

R-GCCINARR-cbl-00937 Extract Container Exception Message

Action Rules

Business View: Assuming container number has been extracted for equipment position x and container sub-position during the 'Extract Container Exception Message' routine, when the system extracts additional container data, the system executes logic to ensure that move ws-arr-cont-excp-message at equipment position x and container sub-position to ws-aei-det-message field.

Given

Container number has been extracted for equipment position X and container sub-position

When

The system extracts additional container data

Then

Move WS-ARR-CONT-EXCP-MESSAGE at equipment position X and container sub-position to WS-AEI-DET-MESSAGE field

R-GCCINARR-cbl-00939 Format Container Detail Line with 'C' Type

Action Rules

Business View: <EXCLUSION CRITERIA> If container number, exception message, and sequence number have been prepared, and the system formats the container detail line occurs during the 'Format Container Detail Line with 'C' Type' routine, then the system must guarantee that set ws-aei-det-typ to 'c' and move ws-aei-report-det-line to sd3-item-lines at position i.

EXCLUDING

Container number, exception message, and sequence number have been prepared

When

The system formats the container detail line

Then

Set WS-AEI-DET-TYP to 'C' and move WS-AEI-REPORT-DET-LINE to SD3-ITEM-LINES at position I

R-GCCINARR-cbl-00852 Get Container Equipment Number, Get Container Exception Message, Move Container Data to Report Line Fields

Process Rules

Business View: Assuming container data exists in the equipment and container arrays for a specific equipment index and container sub-index during the 'Get Container Equipment Number, Get Container Exception Message, Move Container Data to Report Line Fields' routine, when the container detail line is being constructed, the system executes logic to ensure that the container equipment number must be retrieved from ws-arr-cont-number array and the container exception message must be retrieved from ws-arr-cont-excp-message array using the current equipment count and container sub-index.

Given

Container data exists in the equipment and container arrays for a specific equipment index and container sub-index

When

The container detail line is being constructed

Then

The container equipment number must be retrieved from WS-ARR-CONT-NUMBER array and the container exception message must be retrieved from WS-ARR-CONT-EXCP-MESSAGE array using the current equipment count and container sub-index

R-GCCINARR-cbl-00853 Construct Formatted Container Report Line, Add Container Line to Report

Process Rules

Business View: <EXCLUSION CRITERIA> If all container report fields have been populated with type indicator, sequence number, equipment number, and exception message, and the container detail line formatting is completed occurs during the 'Construct Formatted Container Report Line, Add Container Line to Report' routine, then the system must guarantee that the formatted container report line must be constructed and added to the report item lines array at the current report line position.

EXCLUDING

All container report fields have been populated with type indicator, sequence number, equipment number, and exception message

When

The container detail line formatting is completed

Then

The formatted container report line must be constructed and added to the report item lines array at the current report line position

R-GCCINARR-cbl-00944 Extract Container Exception Message

Process Rules

Business View: Assuming a valid container array entry at the current position during the 'Extract Container Exception Message' routine, when the system processes container data for reporting, the system executes logic to ensure that the system should extract the container exception message from the array and assign it to the report detail message field.

Given

A valid container array entry at the current position

When

The system processes container data for reporting

Then

The system should extract the container exception message from the array and assign it to the report detail message field

R-GCCINARR-cbl-00737 Initialize Container Exception Message

Process Rules

Business View: Assuming a container is being prepared for processing during the 'Initialize Container Exception Message' routine, when exception message storage needs to be initialized, the system executes logic to ensure that the container exception message field is set to spaces in the arrival report array.

Given

A container is being prepared for processing

When

Exception message storage needs to be initialized

Then

The container exception message field is set to spaces in the arrival report array

R-GCCINARR-cbl-00604 Add Equipment Exception Details to Email

Process Rules

Business View: Assuming equipment items are processed and some are marked for aei reporting during the 'Add Equipment Exception Details to Email' routine, when the system builds detailed email content, the system executes logic to ensure that for each equipment marked for aei reporting, equipment details and exception messages are added, followed by any associated container details and their exception messages.

Given

equipment items are processed and some are marked for AEI reporting

When

the system builds detailed email content

Then

for each equipment marked for AEI reporting, equipment details and exception messages are added, followed by any associated container details and their exception messages

R-GCCINARR-cbl-00270 Initialize Database Status and Segment

Process Rules

Business View: Assuming a waybill relationship lookup is about to be performed during the 'Initialize Database Status and Segment' routine, when the system prepares for database access, the system executes logic to ensure that the system initializes the database status code and relationship segment variables to clear any previous values.

Given

A waybill relationship lookup is about to be performed

When

The system prepares for database access

Then

The system initializes the database status code and relationship segment variables to clear any previous values

R-GCCINARR-cbl-00271 Call Database to Get Next Container Equipment Record

Action Rules

Business View: Assuming a waybill relationship database connection is established during the 'Call Database to Get Next Container Equipment Record' routine, when the system requests the next container equipment record using gnp function, the system executes logic to ensure that the system retrieves the next available container equipment segment from the database.

Given

A waybill relationship database connection is established

When

The system requests the next container equipment record using GNP function

Then

The system retrieves the next available container equipment segment from the database

R-GCCINARR-cbl-00289 Read Next Container Cross-Reference Record

Action Rules

Business View: Assuming container processing is in progress and more containers flag is true during the 'Read Next Container Cross-Reference Record' routine, when the system attempts to read the next container cross-reference record from fwiqbotl segment, the system executes logic to ensure that the next available container cross-reference record is retrieved or no-more-containers flag is set if no records remain.

Given

Container processing is in progress and more containers flag is true

When

The system attempts to read the next container cross-reference record from FWIQBOTL segment

Then

The next available container cross-reference record is retrieved or no-more-containers flag is set if no records remain

R-GCCINARR-cbl-00322 Initialize CCN Array Index to 1

Process Rules

Business View: Assuming a master manifest cargo has been identified for processing during the 'Initialize CCN Array Index to 1' routine, when the system begins tracking ccn numbers to prevent duplicates, the system executes logic to ensure that the array index j is set to 1 to start from the first position.

Given

A master manifest cargo has been identified for processing

When

The system begins tracking CCN numbers to prevent duplicates

Then

The array index J is set to 1 to start from the first position

R-GCCINARR-cbl-00324 CCN Already in Array?

Decision Rules

Business View: Assuming a master manifest ccn is being processed during the 'CCN Already in Array?' routine, when the system compares the current ccn key with existing entries in the master ccn array, the system executes logic to ensure that if the ccn key matches an existing array entry, the system identifies it as a duplicate.

Given

A master manifest CCN is being processed

When

The system compares the current CCN key with existing entries in the master CCN array

Then

If the CCN key matches an existing array entry, the system identifies it as a duplicate

R-GCCINARR-cbl-00325 Set Master Already Arrived Flag

Action Rules

Business View: Assuming a master manifest ccn is found to already exist in the tracking array during the 'Set Master Already Arrived Flag' routine, when the system detects a duplicate ccn, the system executes logic to ensure that the ws-master-already-arr flag is set to true to skip duplicate processing.

Given

A master manifest CCN is found to already exist in the tracking array

When

The system detects a duplicate CCN

Then

The WS-MASTER-ALREADY-ARR flag is set to TRUE to skip duplicate processing

R-GCCINARR-cbl-00329 Store CCN in Array Position J

Action Rules

Business View: <EXCLUSION CRITERIA> If an available array position has been identified and the ccn is not a duplicate, and the system stores the new master manifest ccn occurs during the 'Store CCN in Array Position J' routine, then the system must guarantee that the ccn key is moved to the master ccn array at position j.

EXCLUDING

An available array position has been identified and the CCN is not a duplicate

When

The system stores the new master manifest CCN

Then

The CCN key is moved to the master CCN array at position J

R-GCCINARR-cbl-00341 Format Equipment Detail Line

Process Rules

Business View: Assuming equipment arrival data exists in the array during the 'Format Equipment Detail Line' routine, when the system processes equipment details up to 999 items, the system executes logic to ensure that each equipment item is formatted with equipment number, exception message, and a 3-digit sequence number derived from the array index, and the detail line is sent to output.

Given

Equipment arrival data exists in the array

When

The system processes equipment details up to 999 items

Then

Each equipment item is formatted with equipment number, exception message, and a 3-digit sequence number derived from the array index, and the detail line is sent to output

R-GCCINARR-cbl-00342 Format Container Detail Line

Process Rules

Business View: Assuming an equipment item has associated containers in the arrival array during the 'Format Container Detail Line' routine, when the system processes containers for the equipment up to 30 containers per equipment, the system executes logic to ensure that each container is formatted with type indicator 'c', container sequence number, container number, exception message, and sent to output until all containers are processed or empty entries are encountered.

Given

An equipment item has associated containers in the arrival array

When

The system processes containers for the equipment up to 30 containers per equipment

Then

Each container is formatted with type indicator 'C', container sequence number, container number, exception message, and sent to output until all containers are processed or empty entries are encountered

R-GCCINARR-cbl-00343 Generate Header Lines

Authorization Rules

Business View: Assuming user access validation has been performed during the 'Generate Header Lines' routine, when the system generates clv report content and access validation failed, the system executes logic to ensure that if scac access is invalid, display scac invalid message; if user has no access, display no access message; if mc table match failed, display no mc table entry message with manifest location.

Given

User access validation has been performed

When

The system generates CLV report content and access validation failed

Then

If SCAC access is invalid, display SCAC invalid message; if user has no access, display no access message; if MC table match failed, display no MC table entry message with manifest location

R-GCCINARR-cbl-00347 Format AEI Equipment Line

Process Rules

Business View: Assuming an equipment item qualifies for aei reporting during the 'Format AEI Equipment Line' routine, when the system formats the aei equipment detail line, the system executes logic to ensure that equipment line is formatted with blank type indicator, equipment number, exception message, and 3-digit sequence number, then added to email content with line count tracking.

Given

An equipment item qualifies for AEI reporting

When

The system formats the AEI equipment detail line

Then

Equipment line is formatted with blank type indicator, equipment number, exception message, and 3-digit sequence number, then added to email content with line count tracking

R-GCCINARR-cbl-00348 Format AEI Container Line

Process Rules

Business View: Assuming an equipment item in aei report has associated containers during the 'Format AEI Container Line' routine, when the system formats aei container detail lines, the system executes logic to ensure that each container line is formatted with type indicator 'c', container sequence number, container number, container exception message, and added to email content up to 30 containers per equipment or until line limit of 700 is reached.

Given

An equipment item in AEI report has associated containers

When

The system formats AEI container detail lines

Then

Each container line is formatted with type indicator 'C', container sequence number, container number, container exception message, and added to email content up to 30 containers per equipment or until line limit of 700 is reached

R-GCCINARR-cbl-00349 Finalize Report

Action Rules

Business View: Assuming aei report content is formatted and ready for transmission during the 'Finalize Report' routine, when the system sends the email report, the system executes logic to ensure that email is sent using emcsend3 service, and if return status is '2' indicating failure, a second attempt is made to backup recipient 'aei9999om01247', followed by message queue purge.

Given

AEI report content is formatted and ready for transmission

When

The system sends the email report

Then

Email is sent using EMCSEND3 service, and if return status is '2' indicating failure, a second attempt is made to backup recipient 'AEI9999OM01247', followed by message queue purge

R-GCCINARR-cbl-00350 Finalize Report

Process Rules

Business View: Assuming all clv report content has been generated and sent during the 'Finalize Report' routine, when the system finalizes the clv report, the system executes logic to ensure that user function code is set to 'wrap' and master header record is sent as final message to complete the report transmission.

Given

All CLV report content has been generated and sent

When

The system finalizes the CLV report

Then

User function code is set to 'WRAP' and master header record is sent as final message to complete the report transmission

R-GCCINARR-cbl-00351 Initialize Email Parameters

Process Rules

Business View: Assuming aei report generation is required during the 'Initialize Email Parameters' routine, when email distribution setup begins, the system executes logic to ensure that all email parameters are cleared and set to default values including sender, recipients, subject, and message content.

Given

AEI report generation is required

When

email distribution setup begins

Then

all email parameters are cleared and set to default values including sender, recipients, subject, and message content

R-GCCINARR-cbl-00363 Construct Report Header Line 1

Authorization Rules

Business View: <EXCLUSION CRITERIA> If report generation is in progress and security validation has been performed, and the system encounters invalid scac access occurs during the 'Construct Report Header Line 1' routine, then the system must guarantee that set carrier scac in clv report scac field and display clv scac invalid message.

EXCLUDING

Report generation is in progress and security validation has been performed

When

The system encounters invalid SCAC access

Then

Set carrier SCAC in CLV report SCAC field and display CLV SCAC invalid message

R-GCCINARR-cbl-00364 Construct Report Header Line 1

Authorization Rules

Business View: Assuming report generation is in progress and user access validation has been performed during the 'Construct Report Header Line 1' routine, when the system encounters user without access permissions, the system executes logic to ensure that display clv user has no access message.

Given

Report generation is in progress and user access validation has been performed

When

The system encounters user without access permissions

Then

Display CLV user has no access message

R-GCCINARR-cbl-00365 Construct Report Header Line 1

Validation Rules

Business View: Assuming report generation is in progress and location table validation has been performed during the 'Construct Report Header Line 1' routine, when the system encounters mc table match failure, the system executes logic to ensure that set clv manifest upon location from input and display clv no mc table entry message.

Given

Report generation is in progress and location table validation has been performed

When

The system encounters MC table match failure

Then

Set CLV manifest upon location from input and display CLV no MC table entry message

R-GCCINARR-cbl-00366 Process Equipment Detail Lines

Process Rules

Business View: Assuming equipment arrival details exist in the arrival detail area and report construction is in progress during the 'Process Equipment Detail Lines' routine, when the system processes equipment detail lines up to 999 items, the system executes logic to ensure that for each non-empty arrival detail area entry, initialize detail type to spaces, set equipment number from arrival area, set exception message from arrival area, calculate 3-digit sequence number from index, and construct clv report detail line.

Given

Equipment arrival details exist in the arrival detail area and report construction is in progress

When

The system processes equipment detail lines up to 999 items

Then

For each non-empty arrival detail area entry, initialize detail type to spaces, set equipment number from arrival area, set exception message from arrival area, calculate 3-digit sequence number from index, and construct CLV report detail line

R-GCCINARR-cbl-00367 Process Container Detail Lines

Process Rules

Business View: Assuming equipment has associated containers and container detail processing is required during the 'Process Container Detail Lines' routine, when the system processes up to 30 containers per equipment item, the system executes logic to ensure that for each non-empty container entry, set detail type to 'c', calculate 3-digit sequence from container index, set container number from arrival container array, set container exception message from arrival container array, and construct clv report detail line.

Given

Equipment has associated containers and container detail processing is required

When

The system processes up to 30 containers per equipment item

Then

For each non-empty container entry, set detail type to 'C', calculate 3-digit sequence from container index, set container number from arrival container array, set container exception message from arrival container array, and construct CLV report detail line

R-GCCINARR-cbl-00382 Include Container Exception Message

Process Rules

Business View: <EXCLUSION CRITERIA> If a container has associated exception messages, and the system generates container report entries occurs during the 'Include Container Exception Message' routine, then the system must guarantee that the container exception message is included in the report detail line.

EXCLUDING

A container has associated exception messages

When

The system generates container report entries

Then

The container exception message is included in the report detail line

R-GCCINARR-cbl-00390 Store Equipment in Processing Array

Process Rules

Business View: Assuming equipment id is formatted and arrival equipment count is incremented during the 'Store Equipment in Processing Array' routine, when the system stores equipment for processing, the system executes logic to ensure that equipment number is stored in arrival equipment number array at current arrival equipment count position and exception message is initialized to spaces.

Given

Equipment ID is formatted and arrival equipment count is incremented

When

The system stores equipment for processing

Then

Equipment number is stored in arrival equipment number array at current arrival equipment count position and exception message is initialized to spaces

R-GCCINARR-cbl-00403 Add Equipment Detail Line to Report

Computation Rules

Business View: <EXCLUSION CRITERIA> If equipment has aei exceptions requiring reporting, and adding equipment detail to report occurs during the 'Add Equipment Detail Line to Report' routine, then the system must guarantee that equipment line contains blank type indicator, equipment number, exception message, and sequence number derived from the last 3 digits of the equipment index.

EXCLUDING

equipment has AEI exceptions requiring reporting

When

adding equipment detail to report

Then

equipment line contains blank type indicator, equipment number, exception message, and sequence number derived from the last 3 digits of the equipment index

R-GCCINARR-cbl-00405 Add Container Detail Line with Exception Message

Computation Rules

Business View: <EXCLUSION CRITERIA> If container is associated with equipment having aei exceptions, and adding container detail to report occurs during the 'Add Container Detail Line with Exception Message' routine, then the system must guarantee that container line contains 'c' type indicator, container number, container exception message, and sequence number derived from the last 3 digits of the container index.

EXCLUDING

container is associated with equipment having AEI exceptions

When

adding container detail to report

Then

container line contains 'C' type indicator, container number, container exception message, and sequence number derived from the last 3 digits of the container index

R-GCCINARR-cbl-00609 Initialize Email Parameters

Process Rules

Business View: Assuming the system needs to prepare for email report generation during the 'Initialize Email Parameters' routine, when email parameter initialization is triggered, the system executes logic to ensure that all email fields are cleared including sender, recipients, copy recipients, subject, keywords, text content, item sequences, item type, and message counter is reset to zero.

Given

The system needs to prepare for email report generation

When

Email parameter initialization is triggered

Then

All email fields are cleared including sender, recipients, copy recipients, subject, keywords, text content, item sequences, item type, and message counter is reset to zero

R-GCCINARR-cbl-00625 Add Equipment Detail Line with Number and Exception Message

Process Rules

Business View: Assuming equipment has aei report flag set to yes during the 'Add Equipment Detail Line with Number and Exception Message' routine, when adding equipment details to email, the system executes logic to ensure that an equipment detail line is added containing equipment type (spaces), equipment number, exception message, and sequence number (last 3 digits of equipment index).

Given

Equipment has AEI report flag set to Yes

When

Adding equipment details to email

Then

An equipment detail line is added containing equipment type (spaces), equipment number, exception message, and sequence number (last 3 digits of equipment index)

R-GCCINARR-cbl-00628 Add Container Detail Line with Container Number and Exception

Process Rules

Business View: Assuming a container is being processed for an equipment item during the 'Add Container Detail Line with Container Number and Exception' routine, when adding container details to email, the system executes logic to ensure that a container detail line is added containing container type 'c', container number, exception message, and sequence number (last 3 digits of container sub-index).

Given

A container is being processed for an equipment item

When

Adding container details to email

Then

A container detail line is added containing container type 'C', container number, exception message, and sequence number (last 3 digits of container sub-index)

R-GCCINARR-cbl-00632 Complete Email Content Assembly

Process Rules

Business View: Assuming all equipment items are processed or line limit is reached during the 'Complete Email Content Assembly' routine, when completing email assembly, the system executes logic to ensure that the email content assembly process is marked as complete and ready for transmission.

Given

All equipment items are processed or line limit is reached

When

Completing email assembly

Then

The email content assembly process is marked as complete and ready for transmission

R-GCCINARR-cbl-00758 Format Equipment Detail Line

Process Rules

Business View: Assuming equipment requires aei reporting and detail formatting is needed during the 'Format Equipment Detail Line' routine, when creating equipment detail line for email content, the system executes logic to ensure that the system should set type indicator to blank, extract equipment number, extract exception message, generate sequence number from equipment array position, and format complete detail line.

Given

Equipment requires AEI reporting and detail formatting is needed

When

Creating equipment detail line for email content

Then

The system should set type indicator to blank, extract equipment number, extract exception message, generate sequence number from equipment array position, and format complete detail line

R-GCCINARR-cbl-00761 Extract Exception Message

Process Rules

Business View: Assuming equipment detail line is being formatted during the 'Extract Exception Message' routine, when populating exception information, the system executes logic to ensure that the exception message should be extracted from the arrival exception message array at the current equipment position.

Given

Equipment detail line is being formatted

When

Populating exception information

Then

The exception message should be extracted from the arrival exception message array at the current equipment position

R-GCCINARR-cbl-00766 Format Container Detail Line

Process Rules

Business View: Assuming container exists for current equipment and requires formatting during the 'Format Container Detail Line' routine, when creating container detail line for email content, the system executes logic to ensure that the system should set type indicator to 'c', extract container number, extract container exception message, generate container sequence number, and format complete container detail line.

Given

Container exists for current equipment and requires formatting

When

Creating container detail line for email content

Then

The system should set type indicator to 'C', extract container number, extract container exception message, generate container sequence number, and format complete container detail line

R-GCCINARR-cbl-00769 Extract Container Exception Message

Process Rules

Business View: Assuming container detail line is being formatted during the 'Extract Container Exception Message' routine, when populating container exception information, the system executes logic to ensure that the exception message should be extracted from the arrival container exception message array at the current equipment and container position.

Given

Container detail line is being formatted

When

Populating container exception information

Then

The exception message should be extracted from the arrival container exception message array at the current equipment and container position

R-GCCINARR-cbl-00775 Complete Detail Assembly

Process Rules

Business View: Assuming all equipment items have been processed or line limit reached during the 'Complete Detail Assembly' routine, when completing the detail assembly process, the system executes logic to ensure that the email content should contain all formatted equipment and container detail lines ready for transmission.

Given

All equipment items have been processed or line limit reached

When

Completing the detail assembly process

Then

The email content should contain all formatted equipment and container detail lines ready for transmission

R-GCCINARR-cbl-00862 Extract Exception Message from Array

Process Rules

Business View: <EXCLUSION CRITERIA> If an equipment array with exception messages at specific index positions, and processing equipment for report detail line formatting occurs during the 'Extract Exception Message from Array' routine, then the system must guarantee that the exception message at the current index position is extracted and assigned to the detail line message field.

EXCLUDING

An equipment array with exception messages at specific index positions

When

Processing equipment for report detail line formatting

Then

The exception message at the current index position is extracted and assigned to the detail line message field

R-GCCINARR-cbl-00866 Format CLV Report Detail Line

Process Rules

Business View: <EXCLUSION CRITERIA> If all detail line fields populated with equipment number, exception message, sequence number, and type indicator, and processing a clv report request occurs during the 'Format CLV Report Detail Line' routine, then the system must guarantee that the clv report detail line record is constructed and moved to the output line for report generation.

EXCLUDING

All detail line fields populated with equipment number, exception message, sequence number, and type indicator

When

Processing a CLV report request

Then

The CLV report detail line record is constructed and moved to the output line for report generation

R-GCCINARR-cbl-00867 Format AEI Report Detail Line

Process Rules

Business View: <EXCLUSION CRITERIA> If all detail line fields populated with equipment number, exception message, sequence number, and type indicator, and processing an aei report request occurs during the 'Format AEI Report Detail Line' routine, then the system must guarantee that the aei report detail line record is constructed and added to the email report item lines array.

EXCLUDING

All detail line fields populated with equipment number, exception message, sequence number, and type indicator

When

Processing an AEI report request

Then

The AEI report detail line record is constructed and added to the email report item lines array

R-GCCINARR-cbl-00960 Extract Exception Message from Array

Process Rules

Business View: Assuming equipment number has been extracted for an equipment entry during the 'Extract Exception Message from Array' routine, when the system continues extracting equipment data for report formatting, the system executes logic to ensure that the exception message should be retrieved from the arrival exception message array at position x and assigned to the aei detail message field.

Given

equipment number has been extracted for an equipment entry

When

the system continues extracting equipment data for report formatting

Then

the exception message should be retrieved from the arrival exception message array at position X and assigned to the AEI detail message field

R-GCCINARR-cbl-00961 Generate Sequence Number from Counter

Computation Rules

Business View: <EXCLUSION CRITERIA> If equipment number and exception message have been extracted, and the system generates a sequence number for report display occurs during the 'Generate Sequence Number from Counter' routine, then the system must guarantee that the equipment counter x should be moved to a temporary sequence field, and the last 3 characters should be extracted and assigned to the aei detail sequence field.

EXCLUDING

equipment number and exception message have been extracted

When

the system generates a sequence number for report display

Then

the equipment counter X should be moved to a temporary sequence field, and the last 3 characters should be extracted and assigned to the AEI detail sequence field

R-GCCINARR-cbl-00962 Format Equipment Detail Line

Process Rules

Business View: <EXCLUSION CRITERIA> If equipment number, exception message, and sequence number have been prepared, and the system formats the equipment detail line occurs during the 'Format Equipment Detail Line' routine, then the system must guarantee that the equipment type should be set to spaces, and the complete aei report detail line should be formatted with all extracted equipment data.

EXCLUDING

equipment number, exception message, and sequence number have been prepared

When

the system formats the equipment detail line

Then

the equipment type should be set to SPACES, and the complete AEI report detail line should be formatted with all extracted equipment data

R-GCCINARR-cbl-00872 Retrieve Container Exception Message

Process Rules

Business View: <EXCLUSION CRITERIA> If a container has been processed and may have associated exception conditions, and the system formats the container detail line for reporting occurs during the 'Retrieve Container Exception Message' routine, then the system must guarantee that the corresponding exception message is retrieved from the container exception message array.

EXCLUDING

A container has been processed and may have associated exception conditions

When

The system formats the container detail line for reporting

Then

The corresponding exception message is retrieved from the container exception message array

R-GCCINARR-cbl-00873 Construct Container Detail Line

Process Rules

Business View: <EXCLUSION CRITERIA> If container identifier, type indicator, sequence number, and exception message are available, and the system creates a container detail line for the report occurs during the 'Construct Container Detail Line' routine, then the system must guarantee that all container information is assembled into the standardized report line format.

EXCLUDING

Container identifier, type indicator, sequence number, and exception message are available

When

The system creates a container detail line for the report

Then

All container information is assembled into the standardized report line format

R-GCCINARR-cbl-00970 Extract Container Exception Message

Action Rules

Business View: Assuming a container with a specific equipment count and container sequence number during the 'Extract Container Exception Message' routine, when the system extracts the exception message, the system executes logic to ensure that retrieve the exception message from the container exception message array using the equipment count and container sequence as indices.

Given

A container with a specific equipment count and container sequence number

When

The system extracts the exception message

Then

Retrieve the exception message from the container exception message array using the equipment count and container sequence as indices

R-GCCINARR-cbl-00971 Format Container Detail Line

Process Rules

Business View: <EXCLUSION CRITERIA> If container type indicator, sequence number, container identifier, and exception message are available, and the system formats the container detail line occurs during the 'Format Container Detail Line' routine, then the system must guarantee that combine all container information elements into the standard report detail line format.

EXCLUDING

Container type indicator, sequence number, container identifier, and exception message are available

When

The system formats the container detail line

Then

Combine all container information elements into the standard report detail line format

R-GCCINARR-cbl-00633 Prepare Email Parameters

Process Rules

Business View: Assuming an aei report needs to be sent and email parameters are being prepared during the 'Prepare Email Parameters' routine, when the system initializes email transmission parameters, the system executes logic to ensure that all email fields are cleared, sender is set to aei report sender, and email configuration parameters are established.

Given

An AEI report needs to be sent and email parameters are being prepared

When

The system initializes email transmission parameters

Then

All email fields are cleared, sender is set to AEI report sender, and email configuration parameters are established

R-GCCINARR-cbl-00635 Call EMCSEND3 to Send Email

Action Rules

Business View: Assuming email parameters are configured with recipients, subject, and report content during the 'Call EMCSEND3 to Send Email' routine, when the system calls emcsend3 to transmit the email, the system executes logic to ensure that the email transmission is attempted with all configured parameters including sender, recipients, subject, and aei report content.

Given

Email parameters are configured with recipients, subject, and report content

When

The system calls EMCSEND3 to transmit the email

Then

The email transmission is attempted with all configured parameters including sender, recipients, subject, and AEI report content

R-GCCINARR-cbl-00636 Check Return Status Flag

Decision Rules

Business View: Assuming email transmission has been attempted via emcsend3 during the 'Check Return Status Flag' routine, when the system checks the return status flag from the email service, the system executes logic to ensure that the return status flag value is evaluated to determine transmission success or failure.

Given

Email transmission has been attempted via EMCSEND3

When

The system checks the return status flag from the email service

Then

The return status flag value is evaluated to determine transmission success or failure

R-GCCINARR-cbl-00637 Status Flag = '2' Failed?

Decision Rules

Business View: Assuming email transmission return status has been received during the 'Status Flag = '2' Failed?' routine, when the return status flag equals '2', the system executes logic to ensure that the system identifies this as a failed email delivery requiring fallback processing.

Given

Email transmission return status has been received

When

The return status flag equals '2'

Then

The system identifies this as a failed email delivery requiring fallback processing

R-GCCINARR-cbl-00638 Set Fallback Recipient AEI9999OM01247

Process Rules

Business View: Assuming primary email delivery has failed with status flag '2' during the 'Set Fallback Recipient AEI9999OM01247' routine, when the system processes the delivery failure, the system executes logic to ensure that the recipient is changed to the fallback address 'aei9999om01247' for retry transmission.

Given

Primary email delivery has failed with status flag '2'

When

The system processes the delivery failure

Then

The recipient is changed to the fallback address 'AEI9999OM01247' for retry transmission

R-GCCINARR-cbl-00639 Call EMCSEND3 with Fallback Recipient

Action Rules

Business View: Assuming primary email delivery failed and fallback recipient is configured as 'aei9999om01247' during the 'Call EMCSEND3 with Fallback Recipient' routine, when the system calls emcsend3 for the second transmission attempt, the system executes logic to ensure that the email is sent to the fallback recipient with the same report content and parameters.

Given

Primary email delivery failed and fallback recipient is configured as 'AEI9999OM01247'

When

The system calls EMCSEND3 for the second transmission attempt

Then

The email is sent to the fallback recipient with the same report content and parameters

R-GCCINARR-cbl-00640 Log Final Email Status

Process Rules

Business View: Assuming fallback email transmission has been completed during the 'Log Final Email Status' routine, when the system receives the final return status from the fallback transmission, the system executes logic to ensure that the final email transmission status is logged for audit and monitoring purposes.

Given

Fallback email transmission has been completed

When

The system receives the final return status from the fallback transmission

Then

The final email transmission status is logged for audit and monitoring purposes

R-GCCINARR-cbl-00425 Add Equipment Detail Line

Process Rules

Business View: <EXCLUSION CRITERIA> If equipment has exceptions and line limit allows, and adding equipment details to the report occurs during the 'Add Equipment Detail Line' routine, then the system must guarantee that the equipment detail line should be formatted with sequence number, equipment number, and exception message and added to the report content.

EXCLUDING

equipment has exceptions and line limit allows

When

adding equipment details to the report

Then

the equipment detail line should be formatted with sequence number, equipment number, and exception message and added to the report content

R-GCCINARR-cbl-00428 Add Container Detail Line

Process Rules

Business View: Assuming container exists and line limit allows during the 'Add Container Detail Line' routine, when adding container details to the report, the system executes logic to ensure that the container detail line should be formatted with 'c' type indicator, container sequence number, container number, and exception message and added to the report content.

Given

container exists and line limit allows

When

adding container details to the report

Then

the container detail line should be formatted with 'C' type indicator, container sequence number, container number, and exception message and added to the report content

R-GCCINARR-cbl-00433 Set AEI Report Required - Assign Message: Equipment lifted early

Action Rules

Business View: Assuming equipment has been flagged as lifted early during the 'Set AEI Report Required - Assign Message: Equipment lifted early' routine, when the system processes the lifted early exception, the system executes logic to ensure that the system marks aei report as required, assigns lifted early message to equipment or container exception message, and sets report flag to 'y'.

Given

Equipment has been flagged as lifted early

When

The system processes the lifted early exception

Then

The system marks AEI report as required, assigns lifted early message to equipment or container exception message, and sets report flag to 'Y'

R-GCCINARR-cbl-00434 Set AEI Report Required - Assign Message: Equipment not lifted

Action Rules

Business View: <EXCLUSION CRITERIA> If equipment has been flagged as not lifted, and the system processes the not lifted exception occurs during the 'Set AEI Report Required - Assign Message: Equipment not lifted' routine, then the system must guarantee that the system marks aei report as required, assigns not lifted message to equipment or container exception message, and sets report flag to 'y'.

EXCLUDING

Equipment has been flagged as not lifted

When

The system processes the not lifted exception

Then

The system marks AEI report as required, assigns not lifted message to equipment or container exception message, and sets report flag to 'Y'

R-GCCINARR-cbl-00435 Set AEI Report Required - Assign Message: Equipment not set out

Action Rules

Business View: <EXCLUSION CRITERIA> If equipment has been flagged as not set out, and the system processes the not set out exception occurs during the 'Set AEI Report Required - Assign Message: Equipment not set out' routine, then the system must guarantee that the system marks aei report as required, assigns not set out message to equipment or container exception message, and sets report flag to 'y'.

EXCLUDING

Equipment has been flagged as not set out

When

The system processes the not set out exception

Then

The system marks AEI report as required, assigns not set out message to equipment or container exception message, and sets report flag to 'Y'

R-GCCINARR-cbl-00436 Set AEI Report Required - Assign Message: Equipment not on 9PLAN

Action Rules

Business View: <EXCLUSION CRITERIA> If equipment has been flagged as not on 9plan, and the system processes the not on 9plan exception occurs during the 'Set AEI Report Required - Assign Message: Equipment not on 9PLAN' routine, then the system must guarantee that the system marks aei report as required, assigns not on 9plan message to equipment or container exception message, and sets report flag to 'y'.

EXCLUDING

Equipment has been flagged as not on 9PLAN

When

The system processes the not on 9PLAN exception

Then

The system marks AEI report as required, assigns not on 9PLAN message to equipment or container exception message, and sets report flag to 'Y'

R-GCCINARR-cbl-00437 Set AEI Report Required - Assign Border-related Messages

Action Rules

Business View: <EXCLUSION CRITERIA> If equipment has border arrival issues (not arrived at border or not acknowledged at border), and the system processes the border arrival exception occurs during the 'Set AEI Report Required - Assign Border-related Messages' routine, then the system must guarantee that the system marks aei report as required, assigns appropriate border-related message to equipment or container exception message, and sets report flag to 'y'.

EXCLUDING

Equipment has border arrival issues (not arrived at border or not acknowledged at border)

When

The system processes the border arrival exception

Then

The system marks AEI report as required, assigns appropriate border-related message to equipment or container exception message, and sets report flag to 'Y'

R-GCCINARR-cbl-00438 Set AEI Report Required - Assign Message: Cargo in error

Action Rules

Business View: Assuming equipment has cargo in error status during the 'Set AEI Report Required - Assign Message: Cargo in error' routine, when the system processes the cargo error exception, the system executes logic to ensure that the system marks aei report as required, assigns cargo error message to equipment or container exception message, and sets report flag to 'y'.

Given

Equipment has cargo in error status

When

The system processes the cargo error exception

Then

The system marks AEI report as required, assigns cargo error message to equipment or container exception message, and sets report flag to 'Y'

R-GCCINARR-cbl-00439 Set AEI Report Required - Assign Message: Master manifest processed

Action Rules

Business View: Assuming equipment has master manifest that was already processed (master arrived and follower condition) during the 'Set AEI Report Required - Assign Message: Master manifest processed' routine, when the system processes the master manifest exception, the system executes logic to ensure that the system marks aei report as required, assigns master manifest processed message to equipment or container exception message, and sets report flag to 'y'.

Given

Equipment has master manifest that was already processed (master arrived and follower condition)

When

The system processes the master manifest exception

Then

The system marks AEI report as required, assigns master manifest processed message to equipment or container exception message, and sets report flag to 'Y'

R-GCCINARR-cbl-00440 Assign Message: Equipment processed successfully

Action Rules

Business View: Assuming equipment processing completed with no arrival errors during the 'Assign Message: Equipment processed successfully' routine, when the system assigns the final processing message, the system executes logic to ensure that the system assigns successful processing message to equipment or container exception message.

Given

Equipment processing completed with no arrival errors

When

The system assigns the final processing message

Then

The system assigns successful processing message to equipment or container exception message

R-GCCINARR-cbl-00441 Set Lifted Early Message REP-MSG-1

Action Rules

Business View: <EXCLUSION CRITERIA> If a container is being processed and aei lifted early exception condition exists, and the system processes the container exception message assignment occurs during the 'Set Lifted Early Message REP-MSG-1' routine, then the system must guarantee that the lifted early message (rep-msg-1) should be assigned to the container exception message field in the container array.

EXCLUDING

A container is being processed and AEI lifted early exception condition exists

When

The system processes the container exception message assignment

Then

The lifted early message (REP-MSG-1) should be assigned to the container exception message field in the container array

R-GCCINARR-cbl-00442 Set Not Lifted Message REP-MSG-2

Action Rules

Business View: <EXCLUSION CRITERIA> If a container is being processed and aei not lifted exception condition exists, and the system processes the container exception message assignment occurs during the 'Set Not Lifted Message REP-MSG-2' routine, then the system must guarantee that the not lifted message (rep-msg-2) should be assigned to the container exception message field in the container array.

EXCLUDING

A container is being processed and AEI not lifted exception condition exists

When

The system processes the container exception message assignment

Then

The not lifted message (REP-MSG-2) should be assigned to the container exception message field in the container array

R-GCCINARR-cbl-00443 Set Not Set Out Message REP-MSG-3

Action Rules

Business View: <EXCLUSION CRITERIA> If a container is being processed and aei not set out exception condition exists, and the system processes the container exception message assignment occurs during the 'Set Not Set Out Message REP-MSG-3' routine, then the system must guarantee that the not set out message (rep-msg-3) should be assigned to the container exception message field in the container array.

EXCLUDING

A container is being processed and AEI not set out exception condition exists

When

The system processes the container exception message assignment

Then

The not set out message (REP-MSG-3) should be assigned to the container exception message field in the container array

R-GCCINARR-cbl-00444 Set Not on 9PLAN Message REP-MSG-4

Action Rules

Business View: <EXCLUSION CRITERIA> If a container is being processed and aei not on 9plan exception condition exists, and the system processes the container exception message assignment occurs during the 'Set Not on 9PLAN Message REP-MSG-4' routine, then the system must guarantee that the not on 9plan message (rep-msg-4) should be assigned to the container exception message field in the container array.

EXCLUDING

A container is being processed and AEI not on 9PLAN exception condition exists

When

The system processes the container exception message assignment

Then

The not on 9PLAN message (REP-MSG-4) should be assigned to the container exception message field in the container array

R-GCCINARR-cbl-00445 Set Not Arrived at Border Message REP-MSG-5

Action Rules

Business View: <EXCLUSION CRITERIA> If a container is being processed and border arrival exception condition exists, and the system processes the container exception message assignment occurs during the 'Set Not Arrived at Border Message REP-MSG-5' routine, then the system must guarantee that the not arrived at border message (rep-msg-5) should be assigned to the container exception message field in the container array.

EXCLUDING

A container is being processed and border arrival exception condition exists

When

The system processes the container exception message assignment

Then

The not arrived at border message (REP-MSG-5) should be assigned to the container exception message field in the container array

R-GCCINARR-cbl-00446 Set Not ACK at Border Message REP-MSG-9

Action Rules

Business View: <EXCLUSION CRITERIA> If a container is being processed and border acknowledgment exception condition exists, and the system processes the container exception message assignment occurs during the 'Set Not ACK at Border Message REP-MSG-9' routine, then the system must guarantee that the not ack at border message (rep-msg-9) should be assigned to the container exception message field in the container array.

EXCLUDING

A container is being processed and border acknowledgment exception condition exists

When

The system processes the container exception message assignment

Then

The not ACK at border message (REP-MSG-9) should be assigned to the container exception message field in the container array

R-GCCINARR-cbl-00447 Set Cargo in Error Message REP-MSG-6

Action Rules

Business View: <EXCLUSION CRITERIA> If a container is being processed and cargo error exception condition exists, and the system processes the container exception message assignment occurs during the 'Set Cargo in Error Message REP-MSG-6' routine, then the system must guarantee that the cargo in error message (rep-msg-6) should be assigned to the container exception message field in the container array.

EXCLUDING

A container is being processed and cargo error exception condition exists

When

The system processes the container exception message assignment

Then

The cargo in error message (REP-MSG-6) should be assigned to the container exception message field in the container array

R-GCCINARR-cbl-00448 Set Master Arrived Message REP-MSG-7

Action Rules

Business View: <EXCLUSION CRITERIA> If a container is being processed and master arrived with follower exception condition exists, and the system processes the container exception message assignment occurs during the 'Set Master Arrived Message REP-MSG-7' routine, then the system must guarantee that the master arrived message (rep-msg-7) should be assigned to the container exception message field in the container array.

EXCLUDING

A container is being processed and master arrived with follower exception condition exists

When

The system processes the container exception message assignment

Then

The master arrived message (REP-MSG-7) should be assigned to the container exception message field in the container array

R-GCCINARR-cbl-00449 Set Default Arrived Message REP-MSG-8

Action Rules

Business View: Assuming a container is being processed and no arrival error condition exists during the 'Set Default Arrived Message REP-MSG-8' routine, when the system processes the container exception message assignment, the system executes logic to ensure that the default arrived message (rep-msg-8) should be assigned to the container exception message field in the container array.

Given

A container is being processed and no arrival error condition exists

When

The system processes the container exception message assignment

Then

The default arrived message (REP-MSG-8) should be assigned to the container exception message field in the container array

R-GCCINARR-cbl-00450 Is this a container?

Decision Rules

Business View: <EXCLUSION CRITERIA> If equipment is being processed for exception message assignment, and the system checks the equipment type occurs during the 'Is this a container?' routine, then the system must guarantee that if the equipment is identified as a container, container-specific exception message processing should be applied, otherwise standard equipment exception processing should be used.

EXCLUDING

Equipment is being processed for exception message assignment

When

The system checks the equipment type

Then

If the equipment is identified as a container, container-specific exception message processing should be applied, otherwise standard equipment exception processing should be used

R-GCCINARR-cbl-00451 Set AEI Report Required Flag

Process Rules

Business View: <EXCLUSION CRITERIA> If a container exception has been processed and message assigned, and the system completes container exception message assignment occurs during the 'Set AEI Report Required Flag' routine, then the system must guarantee that the aei report required flag should be set to true to trigger report generation.

EXCLUDING

A container exception has been processed and message assigned

When

The system completes container exception message assignment

Then

The AEI report required flag should be set to true to trigger report generation

R-GCCINARR-cbl-00452 Mark Container for AEI Reporting

Process Rules

Business View: <EXCLUSION CRITERIA> If a container has been assigned an exception message, and the system processes the container for reporting occurs during the 'Mark Container for AEI Reporting' routine, then the system must guarantee that the container should be marked with 'yes' flag for aei reporting to ensure it appears in the generated report.

EXCLUDING

A container has been assigned an exception message

When

The system processes the container for reporting

Then

The container should be marked with 'YES' flag for AEI reporting to ensure it appears in the generated report

R-GCCINARR-cbl-00453 Master Manifest CCN Retrieval - Retrieve master manifest cargo records using CCN numbers for follower manifest processing

Action Rules

Business View: Assuming a follower manifest cargo record exists with a master manifest ccn reference during the 'Master Manifest CCN Retrieval - Retrieve master manifest cargo records using CCN numbers for follower manifest processing' routine, when the system attempts to retrieve the master manifest cargo record using the master ccn number, the system executes logic to ensure that the system should successfully retrieve the master manifest cargo record and make it available for processing.

Given

A follower manifest cargo record exists with a master manifest CCN reference

When

The system attempts to retrieve the master manifest cargo record using the master CCN number

Then

The system should successfully retrieve the master manifest cargo record and make it available for processing

R-GCCINARR-cbl-00454 Set Ignore Cargo Flag

Decision Rules

Business View: Assuming a follower manifest cargo references a master manifest ccn during the 'Set Ignore Cargo Flag' routine, when the master manifest cargo record cannot be retrieved from the database, the system executes logic to ensure that the system should set the ignore cargo flag to prevent further processing of the follower cargo.

Given

A follower manifest cargo references a master manifest CCN

When

The master manifest cargo record cannot be retrieved from the database

Then

The system should set the ignore cargo flag to prevent further processing of the follower cargo

R-GCCINARR-cbl-00455 Set up inquiry database parameters

Process Rules

Business View: Assuming a waybill lookup request needs to be processed during the 'Set up inquiry database parameters' routine, when the system initializes the inquiry database parameters, the system executes logic to ensure that the segment type is set to 'fwiqroot', user function code is set to 'gu', and accept status is set to 'gegb'.

Given

A waybill lookup request needs to be processed

When

The system initializes the inquiry database parameters

Then

The segment type is set to 'FWIQROOT', user function code is set to 'GU', and accept status is set to 'GEGB'

R-GCCINARR-cbl-00462 Prepare for container cross-reference reading

Process Rules

Business View: Assuming valid container traffic waybill has been found in the inquiry database during the 'Prepare for container cross-reference reading' routine, when the system prepares to read container details, the system executes logic to ensure that initialize status code, set segment type to 'fwiqbotl', clear secondary key, set function code to 'gnp', and set accept status to 'ge'.

Given

Valid container traffic waybill has been found in the inquiry database

When

The system prepares to read container details

Then

Initialize status code, set segment type to 'FWIQBOTL', clear secondary key, set function code to 'GNP', and set accept status to 'GE'

R-GCCINARR-cbl-00479 Load Cargo Record Data

Process Rules

Business View: Assuming a cargo record has been successfully retrieved from database during the 'Load Cargo Record Data' routine, when the cargo data needs to be made available for processing, the system executes logic to ensure that the cargo report segment is moved to the gcsccrt structure.

Given

A cargo record has been successfully retrieved from database

When

The cargo data needs to be made available for processing

Then

The cargo report segment is moved to the GCSCCRT structure

R-GCCINARR-cbl-00484 Load Next Cargo Record

Process Rules

Business View: Assuming an additional cargo record has been found during the 'Load Next Cargo Record' routine, when the cargo data needs to be loaded for evaluation, the system executes logic to ensure that the cargo report segment is moved to the gcsccrt structure.

Given

An additional cargo record has been found

When

The cargo data needs to be loaded for evaluation

Then

The cargo report segment is moved to the GCSCCRT structure

← Return to Categories

EDI Logic Deep-Dive Specification

Category: CA Cargo_Train

Module: GCCINARR 314 EDI Rules Found