Release No.

Number that uniquely identifies a release for a scheduling agreement

Release Type

Release classification

SAPSNC distinguishes between the following release types:

JIT delivery schedule (1)

Forecast delivery schedule (2)

Forecast delivery schedule for kanban processing (3) (see Kanban )

Date of Release

Date on which the customer created the release in the customer system

Release Horizon

Time period in which the release is valid

SAP SNC displays the end of the release horizon.

Reference Document

Number of the scheduling agreement in the customer system

Scheduling Agreement Number

Number of the scheduling agreement to which the release belongs

Scheduling Agreement Item Number

Item number in the scheduling agreement to which the release belongs

Release No.

Number of the current release

First Due Date

Number of days until the next delivery date of a schedule line

Backlog/Immediate Requirement

See Level of Commitment .

Acknowledged

Date on which the supplier confirmed the receipt of the release

Rejected

Date on which the supplier rejected the release

Printed

Date on which the supplier printed the release

Downloaded

Date on which the supplier downloaded the release as a table

Kanban Indicator

The kanban indicator shows whether a release is a forecast delivery schedule in kanban processing. The kanban indicator is transferred toSAPSNC with the release. The supplier cannot create ASNs inSAPSNC for a forecast delivery schedule in kanban processing.

Confirmation

Indicates whether scheduling agreement confirmations are mandatory, optional, or forbidden for the scheduling agreement release according to confirmation control

For more information, see Confirmation Control

Cumulative Received Quantity

Cumulative received quantity (CRQ) of the customer from the release.

The meaning of the CRQ depends on the control category for cumulative quantities that is set in the customer system that creates the scheduling agreement releases. The control category for cumulative quantities defines whether the customer system, when creating a release, considers only the goods receipt quantities that have actually been posted or the complete quantities notified by the supplier. This depends on whether the customer or the supplier wants to synchronize their cumulative quantities by means of goods receipts or inbound deliveries. Depending on the setting for the control category, the CRQ is the cumulated quantity of all goods receipts, or the cumulative quantity of all deliveries that the supplier notified byASN

Number of the LastASN

Number of the most currentASNknown in the customer system when the release was created

The customer transfers the number in the release toSAPSNC.

Supplier Cumulative Quantity

Supplier cumulative quantity from theASNinSAPSNC that was known in the customer system at the time of release creation

For more information, see Supplier Cumulative Quantity .

Delivery Date

Date on which the supplier is to deliver the product to the customer location or to the ship-to location (in the case of TPOP)

Shipping Date

Date on which the supplier is to send the product from the ship-from location

The field displays the shipping date from the release (DeliveryScheduleNotification). If theDeliveryScheduleNotificationdoes not contain a shipping date,SAPSNC can calculate the shipping date during the validation of the inboundDeliveryScheduleNotification. For this,SAPSNC uses theREL_SHIPDATE_SCHEDULINGvalidation check that performs backwards scheduling from the delivery date. For scheduling,SAPSNC uses the lead time of a means of transport assigned to the relevant transportation lane. For more information, see Lead Time .

Schedule Line Quantity

Quantity that the supplier is to deliver

Due Quantity

Schedule line quantity that is not yet covered by ASNs

For more information, see Determination of Due Schedule Lines

Commitment Level

See Level of Commitment .

Cumulative Scheduled Quantity

Sum of the quantities of the release schedule lines and the CRQ from the release history

SAPSNC calculates this cumulative quantity when a release arrives.

Change Number

Number with which a customer identifies the change status of a product in his or her system

The change number is only relevant in a scenario with anSAPback-end system if you use a DIMP system orSAPERP with activated Service Parts Management.

Action Code, Purpose Code

Classification of a release:

Both fields show, as follows, whether a release is an original release or whether it replaces a preceding release:

A release, which the customer sends to reconcile the cumulative quantities between the customer and the supplier (for example, after a fiscal year change), is an original release (action code 01, purpose code 00).

A follow-up release to an original release is a substitution release (action code 04, purpose code 05).

The purpose code corresponds to the EDI standard and is only relevant in the service parts planning scenario. The action code corresponds to the SAP XML standard. In inbound message processing, SAP SNC maps the action code from theDeliveryScheduleNotificationto the purpose code.

Kanban Indicator

The kanban indicator shows whether a release is a forecast delivery schedule in kanban processing. The kanban indicator is transferred toSAPSNC with the release. The supplier cannot create ASNs inSAPSNC for a forecast delivery schedule in kanban processing.

Entry Location POD

EOQ period of the entry location

This is the time period for which the economic order quantity (EOQ) of the entry location suffices.

This field is only relevant for the service parts planning scenario.

Lead Time

Scheduled time span between sending a delivery from the ship-from location and the arrival in the receiving location (customer location or ship-to location)

For more information, see Lead Time

Confirmation by ASN

This field displays whether ASNs are forbidden, obligatory, or optional (standard) according to confirmation control.

Confirmation by SA Confirmation

This field displays whether scheduling agreement confirmations are forbidden, obligatory, or optional (standard) according to confirmation control.

Current ASN Number

Number of the most currentASNinSAPSNC

Customer Cumulative Quantity

Customer cumulative quantity from the most currentASNinSAPSNC

This field is only relevant for the service parts planning scenario.For more information, see Customer Cumulative Quantity .

Supplier Cumulative Quantity

Supplier cumulative quantity from the most currentASN

Cumulative Received Quantity

Cumulative received quantity (CRQ) from the most currentASNinSAPSNC

This field is only relevant for the service parts planning scenario. The meaning of the CRQ depends on the control category that is set for cumulative quantities in the customer back-end system (SAPERP with activated Service Parts Management). The cumulative quantity control category defines whether the customer system only considers the goods receipt quantities that have actually been posted or the complete quantities notified by the supplier. This depends on whether the customer and the supplier want to synchronize their cumulative quantities by means of goods receipts or inbound deliveries). Depending on the setting for the control category, the CRQ is the cumulated quantity of all goods receipts, or the cumulative quantity of all deliveries that the supplier notified byASN

Cumulative Quantity in Transit *

The cumulative quantity in transit is the difference between the customer cumulative quantity from the most currentASN(see above) and the CRQ from the most currentASN(see above).

This field is only relevant for the service parts planning scenario.

Cumulative Quantity Difference

Difference between the supplier cumulative quantity from the most currentASN(see above) and the customer cumulative quantity from the most currentASN(see above)

Backlog

Sum of the due quantities of release schedule lines that lie in the past

Trade-OffZone End

End of the trade-off zone

Firm Zone End

End of the firm zone

Supplier Cumulative Quantity

Supplier cumulative quantity from theASNinSAPSNC that was known in the customer system at the time of release creation

Cumulative Received Quantity

CRQ from the release that the customer system considered at release creation

For more information, see under "Cumulative Received Quantity" in the "Release History" table.

Fixed Cumulative Scheduled Quantity

Sum of schedule line quantities from fixed schedule lines

Max.CumMatGAQty

Maximum cumulative material go-ahead quantity

The maximum cumulative material go-ahead quantity is the sum of the cumulative received quantity from the release and the demand quantities of the release schedule lines until the end of the trade-off zone.

The maximum cumulative material go-ahead quantity contains the maximum cumulative production go-ahead quantity.

Max.CumPrdGAQty

Maximum cumulative production go-ahead quantity

The maximum cumulative production go-ahead quantity is the sum of the cumulative received quantity from the release and the demand quantities of the release schedule lines until the end of the production go-ahead period.

Last ASN No.

Number of the most currentASNinSAPSNC that was known in the customer system at the time of release creation.

The field displays the sameASNnumber as in the release history.