Common use of ODUF Pack Rejection Clause in Contracts

ODUF Pack Rejection. 6.4.1 DTM will notify BellSouth within one business day of rejected packs (via the mutually agreed medium). Packs could be rejected because of pack sequencing discrepancies or a critical edit failure on the Pack Header or Pack Trailer records (i.e. out-of-balance condition on grand totals, invalid data populated). Standard ATIS EMI Error Codes will be used. DTM will not be required to return the actual rejected data to BellSouth. Rejected packs will be corrected and retransmitted to DTM by BellSouth.

ODUF Pack Rejection. 6.4.1 DTM CTI will notify BellSouth within one (1) business day of rejected packs (via the mutually agreed medium). Packs could be rejected because of pack sequencing discrepancies or a critical edit failure on the Pack Header or Pack Trailer records (i.e. e.g., out-of-balance condition on grand totals, invalid data populated). Standard ATIS EMI Error Codes error codes will be used. DTM CTI will not be required to return the actual rejected data to BellSouth. Rejected packs will be corrected and retransmitted to DTM CTI by BellSouth.

ODUF Pack Rejection. 6.4.1 DTM DSL will notify BellSouth within one business day of rejected packs (via the mutually agreed medium). Packs could be rejected because of pack sequencing discrepancies or a critical edit failure on the Pack Header or Pack Trailer records (i.e. out-of-balance condition on grand totals, invalid data populated). Standard ATIS EMI Error Codes will be used. DTM DSL will not be required to return the actual rejected data to BellSouth. Rejected packs will be corrected and retransmitted to DTM DSL by BellSouth.