A supplement is any new iteration of a previously accepted ASR. The entry in the SUP field identifies the reason for which the supplement is being issued.
NOTE 1: An entry in the REMARKS field can be used to clarify the request.
VALID ENTRIES: |
|||
|
1 |
= |
Cancel - Indicates that the pending order is to be canceled in its entirety. |
NOTE 1: If the pending order was already completed as ordered, a separate request must be sent instead of the supplement.
NOTE 2: Valid for Service Inquiries and Firm Orders whether or not the ASR has been confirmed by the provider.
NOTE 3: If the ASC-EC changes, a SUP 1 must be issued to cancel the request. A new request is then issued with the new ASC-EC.
2 |
= |
New Due Date - Indicates a change to the Desired Due Date (DDD) and any associated fields as defined by provider customer negotiations. |
NOTE 1: The new DDD may not exceed the limits defined in Provider Access Tariff/practices. The EXP field must be populated when the DDD is less than the standard interval. The EXP field may need to be populated when the DDD is sooner than the existing desired due date.
NOTE 2: Valid only for Firm Orders whether or not the ASR has been confirmed by the provider.
3 |
= |
Other - Any other change to the Firm Order that has been confirmed by the provider. |
NOTE 1: This Supplement Type may affect the previously agreed upon due date.
NOTE 2: This Supplement Type supports partial cancellations.
NOTE 3: If this Supplement Type also includes a change to the DDD, the new date may not exceed the limits defined in Provider Access Tariff/practices. The EXP field must be populated when the DDD is less than the standard interval. The EXP field may need to be populated when the DDD is sooner than the existing DDD.
NOTE 4: Provider Access Tariffs/practices define the allowable set of changes that can be accommodated on this Supplement Type.
NOTE 5: In a Multi-EC environment, the use of a SUP type “3” is to be based on the status of the ASC-EC FOC. Since an OEC FOC status may not necessarily match the ASC-EC FOC status, OECs must be able to accept SUP type “3” regardless of FOC status when the ASC-EC field is populated.
NOTE 6: Used when an OEC is added to or deleted from the Multi-EC Form. Therefore, when the ASC-EC field is populated with an ICSC code other than that of the receiving provider, the receipt of a SUP “3” must be acceptable as the initial ASR to the added OEC.
4 |
= |
Correction - Indicates that this request is being issued to correct a previous request that has not already been confirmed by the provider. |
NOTE 1: Valid for Firm Orders when the ASR has not been confirmed by the provider.
NOTE 2: Valid for Service Inquiries whether or not the ASR has been confirmed by the provider.
NOTE 3: In a Multi-EC environment, the use of a SUP type “4” is to be based on the status of the ASC-EC FOC. Since an OEC FOC status may not necessarily match the ASC-EC FOC status, OECs must be able to accept SUP type “4” regardless of FOC status when the ASC-EC field is populated.
NOTE 4: Used when an OEC is added to or deleted from the Multi-EC Form. When the ASC-EC field is populated with an ICSC code other than that of the receiving provider, the receipt of a SUP “4” must be acceptable as the initial ASR to the added OEC.
USAGE: This field is conditional.
NOTE 1: Prohibited on initial requests.
NOTE 2: Prohibited when changing a Service Inquiry to a Firm Order.
NOTE 3: Prohibited when changing service type, which results in a change to the first character of the REQTYP field.
NOTE 4: Prohibited if the pending order was already completed as ordered or canceled.
NOTE 5: Otherwise required.
DATA CHARACTERISTICS: 1 numeric character
EXAMPLE: |
4 |