Sales Scheduling Agreement

Transfer Sales Scheduling Agreements to the SAP APO System

You must transfer your sales scheduling agreements to the SAP APO system.

You can transfer the sales scheduling agreements from the SAP R/3 system to the SAP APO system over the Core Interface (CIF). (See SAP R/3 System )

Assign Confirmation and Control Profiles

You can assign confirmation and control profiles to the sales scheduling agreement. You can use these profiles to define which checks the system should carry out on receipt of scheduling agreement releases, or whether you want to send confirmations to customers.

In Customizing for Advanced Planning and Optimization choose Supply Chain Planning → Delivery Schedule Processing for Sales Scheduling Agreement → Profiles → Define Confirmation Profiles (Confirmation Output) and Define Control Profiles and enter your chosen criteria.

Default Profiles for Initial Data Transfer

You can set that default profiles are assigned when sales scheduling agreements are transferred for the first time. In other words, you can define criteria by which default profiles are determined when sales scheduling agreement items are transferred.

The control profile, that you want to assign to a sales scheduling agreement item, can be determined on the basis of customer location, delivery schedule planning and delivery schedule splitting profile.

The customer location of the APO system corresponds to the sold-to party or ship-to party (KUNNR) of the sales scheduling agreement in the R/3 system. The delivery schedule splitting rule in APO corresponds to the planning delivery schedule instruction (PLAVO) of the sales scheduling agreement item in the R/3 system. MRP handling of delivery schedule types is also available in R/3 (ABDIS).

The system tries to determine the control profile as follows:

1. Using all criteria

2. Using delivery schedule planning and delivery schedule splitting profile

3. Using delivery schedule planning only

If a control profile cannot be determined the first time the sales scheduling agreements are transferred, then the control profile SAP1 is used.

The confirmation profile, that you want to assign to a sales scheduling agreement item, can be determined on the basis of the customer location.

The customer location corresponds to the sold-to party or ship-to party (KUNNR) of the sales scheduling agreement in the R/3 system.

If a confirmation profile cannot be assigned based on the criteria entered in Customizing the first time sales scheduling agreements are transferred, then the confirmation profile SAP 1 is used.

Using the enhancement APOCF060 you can change all the data for transferred items from sales scheduling agreements. You can also assign control profiles and confirmation profiles to the scheduling agreement item.

Choose Supply Chain Planning → Sales Scheduling Agreement Processing → Current Settings → Default Profiles for Initial Data Transfer and enter the criteria you want to use.

Delete Sales Scheduling Agreements

You should cancel or delete sales scheduling agreement items in the SAP R/3 system before you delete them in the SAP APO system.The canceled sales scheduling agreement item then becomes inactive in the SAP APO system when the next transfer of data changes over the CIF takes place and can then be deleted in the SAP APO system.

If you deactivate sales scheduling agreement items in the SAP APO system only, then the corresponding sales scheduling agreement item is not deleted, nor is a reason for cancellation available in the SAP R/3 system.

This means that with the next change transfer from the SAP R/3 system the sales scheduling agreement item is reactivated because the sales scheduling agreement was not canceled in the SAP R/3 system.

See Displaying, Maintaining and Deleting Sales Scheduling Agreements

Processing Sales Scheduling Agreements in the Product Planning Table and Product View

Maintain User Settings

Maintain the user settings for the product planning table and the product view accordingly.

Choose Supply Chain Collaboration → Sales Scheduling Agreement Processing → Product Planning Table (Sales Scheduling Agreement) or Production Planning → Interactive Production Planning → Product View

To select a suitable variant for sales scheduling agreement processing (for example, SAP_SCO), choose User Settings , so that for example, the chart Scheduling Agreements (SD) is displayed in the product planning table. To use another variant from Customizing, choose

Choose the Product 2 tab page, then Demands and in the Displayed Qty field set that confirmed quantities and requested quantities should be displayed in the Product View (Periodic) . If you choose an aggregated display then the system also displays the total of the requested quantities and the total of the confirmed quantities if these differ within the period that you are looking at.

On the same page select Display Customer Segment for Sales Scheduling Agreement . This displays the most recently saved confirmed quantities, the difference between the current confirmed quantity and the requested quantity and also the cumulative difference quantity in the Product View: Periodic .

Display Charts in the Product Planning Table

In order to show the charts that are needed for processing sales scheduling agreements in the product planning table, you should select the Product View: Periodic and Scheduling Agreements (SD) charts

In the Product View: Periodic chart the requested quantities and confirmed quantities are displayed in buckets; in the Scheduling Agreements (SD ) chart selected master data and transaction data for the sales scheduling agreement, (for example, the current and transmitted status of the scheduling agreement item) is displayed

Set the Layout of the Product Planning Table

In Customizing, you can set which charts are available or define the pushbutton profile by choosing Supply Chain Planning → Production Planning and Detailed Scheduling (PP/DS) → Product Planning Table → Set Layout.

See Process Sales SA in the Product Planning Table and Product View

Alerts for the Sales Scheduling Agreement Release

See Alert Monitor for the Sales Scheduling Agreement

Authorizations

You can use the authorization object C_APO_SSA to define which activities a user can carry out within Delivery Schedule Processing for the Sales Scheduling Agreement .

For example, you can control whether a user can create releases, output confirmations or change master data.

EDI Inbound Processing of Releases Against Sales Scheduling Agreements

Choose Supply Chain Planning → Sales Scheduling Agreement Processing → Current Settings → IDoc Inbound Processing , to set inbound processing for IDocs (of message type DELINS).

Define inbound release processing

For example, you can define checking criteria for the IDoc inbound processing or use a test run for the processing of operative delivery schedules and/or forecast/planning delivery schedules so that IDoc processing is canceled for all delivery schedules for the sold-to party entered.

For example, you can use the following checking criteria:

Check the order number

If an order number is given by the customer in the IDoc it is compared with the order number in the sales scheduling agreement. If both numbers are identical then IDoc processing is continued.

Check the unloading point

During IDoc inbound processing of scheduling agreement releases the system uses the unloading point to efficiently identify the sales scheduling agreement to which the releases relate.

You can also define that a delivery note prefix and a splitting rule are used.

In addition, you can use a test run for the processing of operative and/or forecast/planning delivery schedules.

If you use a test run the system terminates IDoc processing for all scheduling agreements for the sold-to party you have entered.

Define determination of the sold-to party

For example, you can define which vendor should be assigned to which customer.

You can also enter a partner description that indicates a particular customer plant or warehouse and which is used as a ship-to point.

In addition you can specify a final unloading point.

During IDoc inbound processing of scheduling agreement releases the system uses these criteria to efficiently identify the sales scheduling agreement to which the releases relate.

Assignment of customer (sold-to party) and vendor

You want to assign customer A to vendor B.

Customer A, who sends the IDocs, uses the description B_1 for vendor B.

If customer A sends an IDoc to vendor B he also sends his vendor description in the IDoc, that is, B_1.

Vendor B can now assign the description B_1, which is used by customer A, to customer A.

In this way there is an assignment between customer and vendor within the system.

Implement Customer-specific Enhancements – Business Add-Ins (BAdIs)

Numerous Business Add-Ins (BAdIs) are available for IDoc inbound processing.

For more information about these Business Add-Ins see Business Add-Ins for Sales Scheduling Agreements, Releases and Confirmations .

Customizing

You must make your chosen settings in Customizing for Advanced Planning and Optimization → Supply Chain Planning → Delivery Schedule Processing for Sales Scheduling Agreement.

Due Delivery Schedule with Delivery Schedule Split

To split inbound forecast/planning delivery schedules, you must carry out the following steps:

Create a splitting profile in Customizing for Advanced Planning and Optimization (APO), by choosing Supply Chain Planning → Delivery Schedule Processing for Sales Scheduling Agreement → Delivery Schedule Splitting.

Define the delivery schedule splitting rules.

Assign the delivery schedule splitting rules to the splitting profile.

Assign the delivery schedule splitting profile to the scheduling agreement control profile.

Assign the scheduling agreement control profile you want to use to the sales scheduling agreement item in the master data maintenance for the sales scheduling agreement.

See also Due Delivery Schedule

Admissibility Check

You have made the necessary settings in Customizing for Advanced Planning and Optimization under Supply Chain Planning → Delivery Schedule Processing for Sales Scheduling Agreement.

Under Maintain Heuristicyou can choose between the following Heuristics for the admissibility check:

Admissibility OK Without Check (SAP_CDS_A01)

This means that the new due delivery schedule is admissible without a check being carried out.

Tolerance check (SAP_CDS_A02)

This means that the current due delivery schedule is compared with the last confirmed due delivery schedule.

If you use the tolerance check then you must define a tolerance profile.

You define the tolerance profile by choosing Heuristics →Define Tolerance Profiles for Admissibility Check.

In the tolerance profile you can set an individual or a totals check.

Individual Check

If you want an individual check of quantity and date pairs then you can either choose either an exact-to-the-day or to-the-second check. Select Check Time Stamp.

In this way you can define a more exact check for the near future and a more approximate check for the distant future.

Totals Check

If you want to carry out the totals check for periods in your planning calendar then you must create a planning calendar in Customizing for Advanced Planning and Optimization under Master Data → Calendar → Maintain Planning Calendar (Time Stream), and assign this planning calendar to the tolerance profile.

Assign the tolerance profile to the heuristic SAP_CDS_A02 in the heuristic settings or the control profile.

The system determines which tolerance profile should be used as follows:

If you have maintained the tolerance profile:

For the heuristic and in the control profile

⇒Then the tolerance profile of the heuristic is used, because it has priority.

Neitherfor the heuristic nor in the control profile

⇒Then no check is carried out.

Only for the heuristic or only in the control profile

⇒There is only one tolerance profile; in other words, the tolerance profile used by the system is unique.

Assign the heuristic to the control profile in Customizing under Profiles → Define Control Profiles.

Assign the control profile to the relevant sales scheduling agreements in master data maintenance on the Scheduling Agreement tab page.

Create Your Own Checks

You can create an algorithm (function module) for the admissibility check and assign it in Customizing under Heuristics → Maintain Heuristics

You can assign the heuristic to the control profile and assign the control profile to the sales scheduling agreement in master data maintenance on the Scheduling Agreement tab page.

(See Create Heuristics with Algorithms )

See also Admissibility Check

Feasibility Check

The quantities requested by the customer can be automatically confirmed in the feasibility check.

You have made the necessary settings in Customizing for Advanced Planning and Optimization under Supply Chain Planning → Delivery Schedule Processing for Sales Scheduling Agreement.

Under Maintain Heuristicyou can choose between the following Heuristics for the feasibility check:

Fully confirm without check (SAP_CDS_F01)

Days ’ supply check (SAP_CDS_F02)

Product heuristic with days ’ supply check ( SAP_CDS_F03)

You can define that the feasibility check is only carried out if:

All sales scheduling agreement items for a product have an admissible current status and which statuses you want to allow

The product has a Planning File Entry for the Admissibility Check.

This means that only those products for which an MRP-relevant change has taken place since the last feasibility check are checked.

The days’ supply check within the feasibility check is always carried out on the basis of the requested quantities.

If you use a days’ supply check then you must maintain a days’ supply type. You use the days’ supply type to control which stocks, receipts, requirements and forecasts the system takes into account in the calculation of the actual days’ supply

You maintain the days’ supply type in Customizing for Supply Chain Planning under Production Planning and Detailed Scheduling (PP/DS) → Delivery Schedule Processing for Sales Scheduling Agreement → Heuristics → Maintain Days‘ Supply Types. In the days‘ supply check the system then calculates the days’ supply for each pegging area based on the days‘ supply type.

For each days’ supply type you can define up to three values (in calendar days) as the minimum days’ supply.

The minimum days’ supply is used to trigger alerts that make the planner aware of critical situations in product availability. Different priorities are assigned to the three values (error, warning, information); these priorities then trigger different alerts.

The system generates an alert as soon as the actual days’ supply falls below the minimum days’ supply.

However, the feasibility check only fails if the actual days’ supply falls below the minimum days’ supply (error).

Using the Customer Exit APOCV001 you can define product-dependent minimum days’ supply quantities that are independent of the days’ supply type maintained in Customizing (depending on the checking horizon).

Assign the days’ supply type (DaySupType) either per heuristic or in the control profile.

The system determines which days’ supply type should be used as follows:

You have maintained the days’ supply check:

For the heuristic and in the control profile

⇒The days’ supply type of the heuristic is used, because it has priority.

Neitherfor the heuristic nor in the control profile

⇒Then no check is carried out.

Only for the heuristic or only in the control profile

⇒There is only one days’ supply type; in other words, the days’ supply type used by the system is unique.

Assign the heuristic to the control profile in Customizing under Profiles → Define Control Profiles.

In addition you can choose:

Whether the system should carry out the feasibility check immediately after the admissibility check as a part of inbound processing.

Select Straight After Release Receipt.

Which days’ supply type ( receipt days’ supply / (stock) days’ supply) the system should use to determine the day’ supply.

Assign the control profile to the relevant sales scheduling agreements in master data maintenance on the Scheduling Agreement tab page.

Create Your Own Checks

You can create an algorithm (function module) for the feasibility check and assign it in Customizing under Heuristics → Maintain Heuristics (See Create Heuristics with Algorithms )

See Feasibility Check

Check Admissibility and Feasibility in Automated Production Planning

You can check admissibility and feasibility in automated production planning.

For the production planning run you can define that the system should carry out multiple heuristics, one after the other.

Choose Production Planning → Automated Production Planning and Optimization.

Select the heuristics that you want to use.

For the heuristics for the admissibility or tolerance check select the object2( Orders ).

For the heuristics for the feasibility check select the object4( Products ).

Then enter the necessary selection criteria.

See Production Planning Run and Production Planning Run in the Background .

Check Admissibility and Feasibility Variably in Interactive Production Planning

If you want to execute heuristics in the dialog then you must:

Maintain heuristics

Assign heuristics to the control profile

Maintain the heuristic profile in Customizing ( Delivery Schedule Processing for Sales Scheduling Agreement → Heuristics → Maintain Heuristic Profiles )

The heuristic profile determines the heuristics that you can select in the application by choosing Variable Heuristic or ( Interactive ) Planning → Heuristics .

Assign the heuristic profile in the User Settings in the product view or product planning table (for example SAP_CDS_001 – Profile for Sales Scheduling Agreement )

Check Feasibility Directly After Inbound Processing

If you have chosen Straight After Release Receipt for the feasibility check in the control profile then the feasibility is checked immediately after inbound processing.

Planning procedure

You can use the planning procedure in the location-dependent product master to define for customer requirements whether the requirement quantity or the confirmed quantity is pegging-relevant.

Choose Production Planning and Detailed Scheduling (PP/DS) → Maintain Planning Procedures and define whether the confirmed or the required quantity is pegging-relevant

Assign the corresponding PP planning procedures to the relevant products in the location-dependent master data.

If you carry out planning on the basis of the requested quantity, then customer requirements are planning-relevant when you receive the SA release.

If you carry out planning on the basis of the confirmed quantity, then customer requirements only become planning-relevant when they have been confirmed, regardless of whether this confirmation has been sent to the customer or not.

See Determine the Pegging-Relevant Quantity for Customer Requirements

Backorder Processing

Customizing

Make the following settings in Customizing for the Global Available-to-Promise (Global ATP Check) under Product Availability Check

Define the required scope of check for the ATP group and the corresponding business event (for example, A – SD-Order ) ( Product Availability Check → Maintain Check Control )

For example, the scope of check should include the category Release from Customer in Plant - SD SA (HC) .

Maintain the filter type. ( Tools → Maintain Filter Type )

You use the filter type to define the criteria for selecting orders for backorder processing in the background.

For example, the filter type for backorder processing in the background should include the category Release from Customer in Plant - SD SA (HC) as well as the product.

Maintain the check mode and the check instructions. ( General Settings → Maintain Check Mode and Maintain Check Instructions )

Maintain the check instructions for the check mode and the corresponding business event and if necessary select ATP Alert Active , so that you are informed of any shortages in the Alert Monitor.

Master Data

In the location-specific product master, on the ATP data tab p age, check whether the following data is maintained ( Master Data → Location → Product ):

Check mode

ATP Group

Checking horizon (Requirements after the end of the checking horizon are not checked but are confirmed completely).

You can use the Customer Exit APOBO010 to exclude sales scheduling agreement items with the current status Admissibility not ok from backorder processing, for example.

See also Backorder Processing

 

Confirmations

Generate Full (Compliant) or Partial (Deviating) Confirmation

You can define the circumstances under which a full or a partial confirmation is issued.

In Customizing for Supply Chain Planning choose Delivery Schedule Processing for Sales Scheduling Agreement → Profiles → Define Confirmation Profile

In the determination type define whether requested quantities have to be confirmed to the second, to the hour or to the day, in order for the system to issue a full confirmation.

The determination type that you have set determines whether you or the system have fully or partially confirmed the requested quantities. The result of the check is displayed as the Current Status ( Confirmation status) of the sales scheduling agreement item.

You assign the confirmation profile to the corresponding sales scheduling agreement item in master data maintenance.

You can use the Business Add-In (BAdI) Determine Confirmation Status (/SAPAPO/CMDS_STATDET) to define use your own checks, for example if you want to use a to-the-week check or different checks for different customers.

You can also use the BAdI Compare Two Time Series (/SAPAPO/COMPSCHEDLIN), to compare two time series for example, or to define your own time intervals.

Generate Full (Matching) Confirmation with Schedule Lines

In the Confirmation Profile you can define whether the full confirmation is sent with schedule lines or without schedule lines.

You should note that in a full confirmation that is generated on the basis of a to-the-hour or a to-the-day check, the time stamp of the requested quantity may differ from that of the confirmed quantity.

If your customer needs this quantity and date information then you should send the full confirmation with schedule lines.

The Determination Type in the confirmation profile determines whether the requested quantities are confirmed fully or partially. The result ( Partial or Full Confirmation ) is displayed as the Current Status of the sales scheduling agreement item.

In the confirmation profile you have set a to-the-day check so that the time of the requested or confirmed quantity is not taken into account.

Your customer wants 100 pc on September 24 th at 14.00.

You can only meet the requirement of 100 pc at 21.00.

Because you have defined a to-the-day check, the requirements are fully confirmed.

Output Confirmations (Actions)

In the Confirmation Profile, you have made the following settings for the output of confirmations (actions):

Immediate processing or Processing via Selection Report for the confirmation processing time

Confirmation Sent Only If Variance from Due Delivery Sched. or Confirmation Always Sent for the send type.

Set Actions for Output of Confirmations

If you want to issue confirmations then you must make the necessary settings in Customizing for Supply Chain Planning under Delivery Schedule Processing for SD Scheduling Agreement → Define Actions for Issuing Confirmations.

See also: Setting Message Actions (Confirmation)

Generating and Outputting Confirmations (Vendor)

Business Add-Ins (BAdIs) - Implement Customer-Specific Enhancements

If you want to use Business Add-Ins (BAdIs) for confirmations, then you must implement them in Customizing under Delivery Schedule Processing for SD Scheduling Agreement.

For more information about these Business Add-Ins see Business Add-Ins for Sales Scheduling Agreements, Releases and Confirmations .

 

Carry Out Fiscal Year Change

The fiscal year change process must be set identically in SAP R/3 and SAP APO.

SAP APO - Customizing

After sales scheduling agreement items have been transferred they are assigned to a default control profile that specified an automatic fiscal year change.

In the control profile that you assign, set the procedure that you want to use:

Manual Fiscal Year Change

In the control profile in Fiscal Year Change for the manual fiscal year change choose Manual Reset of CQ at Year Change and assign the control profile to the sales scheduling agreement item in master data maintenance.

In SAP APO you can use the Business Add-In Control the Fiscal Year Change (/SAPAPO/CMDS_RES_CDQ) to control for sales scheduling agreements with manual fiscal year change whether or in which cases a fiscal year change is necessary.

No Fiscal Year Change

Choose No Reset of CQ , this means that the cumulative delivered quantity is not reset at the end of the fiscal year, instead it continues to be added to.

Automatic Fiscal Year Change

Choose Automatic Reset of CQ at Year Change

Manual Fiscal Year Change

When you switch from an automatic to a manual fiscal year change, both release types must be in the same (new) fiscal year.

If the release types are in different fiscal years then you preset an automatic fiscal year change in Customizing and change the fiscal year in the release with the old fiscal year.

The prerequisites for the manual fiscal year change are as follows:

The sales scheduling agreement item has a fiscal year, because otherwise this item is not relevant for a fiscal year change.

As soon as the first outbound delivery for the item is created in the OLTP or SAP R/3 system and transferred to SAP APO then the fiscal year information is also transferred to SAP APO. However, a fiscal year change may still be necessary, for example if the customer has entered outbound deliveries from the last fiscal year in the new fiscal year.

The fiscal year start (day and month) of the sales scheduling agreement must be identical in SAP R/3 and SAP APO.

A deviation may occur if the fiscal year variant for the sales scheduling agreement has been changed in the SAP R/3 system; in other words, if the customer has postponed his fiscal year start so that the outbound deliveries have been adjusted but the related sales scheduling agreements planned in SAP APO have not been adjusted.

Automatic Fiscal Year Change

The automatic fiscal year change set in the control profile only takes place if you do not make a setting in the linked SAP R/3 system or if you use the Customer-Exit V45L0001 Reset the CQ at End of Fiscal Year making the necessary settings.

See Manage Fiscal Year

Migration of Sales Scheduling Agreements

For more information, see the SAP Note 449954.

Sales Scheduling Agreement – Document Type

As a rule, the sales scheduling agreement in the SAP R/3 system is a sales scheduling agreement with the document type LZ ( Scheduling Agreement with Release ).

In the sales scheduling agreement enter the customer material number and the scheduling agreement number and item (in the order num ber and order item fields) of your customer’s scheduling agreement so that the scheduling agreement can be determined on IDoc inbound processing.

Create and Activate Integration Model

Enter an integration model containing material masters, plants, customers, stocks and sales orders (for transferring the delivery) and sales scheduling agreement items. Select the ATP data as well ( ATP Customizing and ATP Check) if you want to use the Global ATP Check in the SAP APO system.

For sales scheduling agreement items that you plan in the SAP APO system, you must also select ATP Check , so that the material is scheduled in the SAP APO system. This ensures that when scheduling agreement releases are created in the SAP R/3 system over the CIF, the same dates (delivery date, goods issue date, loading date, material availability date, and so on) are determined as in the SAP APO system.

Activate the model.

In the SAP R/3 system, choose Logistics → Central Functions → Supply Chain Planning Interface → Core Interface Advanced Planner and Optimizer → Integration Model.

For sales scheduling agreements you must activate the object type SD Scheduling Agreements .

In the SAP R/3 system you cannot receive or enter releases for plant/material combinations (CIF filter object) that are located in an active integration model.

The corresponding scheduling agreement releases are no longer ready for input.

If a release is received against this sales scheduling agreement, then the IDoc is forwarded to the SAP APO system and processed there.

You should note that if the integration model is not active, then the release IDoc is processed in the SAP R/3 system. The release is then not available in SAP APO.

Fiscal Year Change

If the linked OLTP-System is an SAP R/3 system then you can set in the Customer Exit V45L0001 ( Reset the CQ at End or Fiscal Year - EXIT_SAPLV45L_004) whether the cumulative quantities should be reset when the fiscal year changes. If you do not make any setting an automatic fiscal year change is carried out.

The fiscal year change process must be set identically in SAP R/3 and SAP APO.

See Manage Fiscal Year

Customer-Specific Enhancements

As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) with Plug-In 2002.1 you can use the following Business Add-Ins (BAdIs) for sales scheduling agreement items that are to be transferred:

BADI_SCOCONF BAdI Process Customer-Specific Structures (CIF-Inbound) ,

To change the data of the transferred confirmations (which are entered as a JIT delivery schedule or a forecast delivery schedule in the sales scheduling agreement).

You can also transfer customer-specific data.

CIF_SDLSE_001 BAdI Transfer Sales Scheduling Agreement Items (CIF Outbound )

To change the data of the selected sales scheduling agreements.

In addition you can store customer-specific information in an additional structure.

CIF_SDLSE_002 BAdI Filter Object Selection for SSA Items (CIF Outbound )

To carry out the selection of materials and the plants they are related to with additional restrictions.

If you use an SAP R/3 system with release DI 46C2 then, instead of the BAdIs, the following Customer Exits are available:

EXIT_SAPLSDSE_001 (corresponding to BAdI CIF_SDLSE_001)

EXIT_SAPLSDSE_002 (corresponding to BAdI CIF_SDLSE_002)

See Business Add-Ins (BAdIs) for the APO Core Interface (CIF) in the SAP R/3 System (SCM-APO-PPS-CDS)

For more information about the CIF see the SAP Library for Advanced Planning and Optimization under Integration of SAP APO and SAP R/3 .