Common use of ODUF Pack Rejection Clause in Contracts

ODUF Pack Rejection. 6.4.1 Esodus 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 (e.g., out-of-balance condition on grand totals, invalid data populated). Standard ATIS EMI error codes will be used. Esodus will not be required to return the actual rejected data to BellSouth. Rejected packs will be corrected and retransmitted to Esodus by BellSouth.

ODUF Pack Rejection. 6.4.1 Esodus E2 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 (e.g., i.e. out-of-balance condition on grand totals, invalid data populated). Standard ATIS EMI error codes Error Codes will be used. Esodus E2 will not be required to return the actual rejected data to BellSouth. Rejected packs will be corrected and retransmitted to Esodus E2 by BellSouth.

ODUF Pack Rejection. 6.4.1 Esodus eXpeTel 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 (e.g., i.e. out-of-balance condition on grand totals, invalid data populated). Standard ATIS EMI error codes Error Codes will be used. Esodus eXpeTel will not be required to return the actual rejected data to BellSouth. Rejected packs will be corrected and retransmitted to Esodus eXpeTel by BellSouth.