S29 BB ConfigGuide en de

SAP SCM 4.
1
November 2004
English
Building Block
Capable-to-Promise
Building Block Configuration Guide
SAP AG
Neurottstr. 16
69190 Walldorf
Germany
SAP Best Practices Building Block Capable-to-Promise: Configuration Guide
Copyright
© Copyright 2004 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the
express permission of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components
of other software vendors.
Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390,
OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and
Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other
countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or
registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web
Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented
and implemented by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, and other SAP products and services mentioned herein as
well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in
several other countries all over the world. All other product and service names mentioned are the
trademarks of their respective companies. Data contained in this document serves informational purposes
only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its
affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of
any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only
warranties for SAP Group products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as
constituting an additional warranty.
© SAP AG Page 2 of 28
Icons
Icon Meaning
Caution
Example
Note
Recommendation
Syntax
Typographic Conventions
Type Style Description

Example text Words or characters that appear on the screen. These include field
names, screen titles, pushbuttons as well as menu names, paths and
options.
Cross-references to other documentation.
Example text Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE TEXT Names of elements in the system. These include report names,
program names, transaction codes, table names, and individual key
words of a programming language, when surrounded by body text, for
example, SELECT and INCLUDE.
Example text Screen output. This includes file and directory names and their paths,
messages, source code, names of variables and parameters as well as
names of installation, upgrade and database tools.
EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the
ENTER key.
Example text Exact user entry. These are words or characters that you enter in the
system exactly as they appear in the documentation.
<Example text> Variable user entry. Pointed brackets indicate that you replace these
words and characters with appropriate entries.
Content
1 Purpose.............................................................................................................................. 5
2 Preparation......................................................................................................................... 6
2.1 Prerequisites............................................................................................................... 6
2.2 SAP Notes Building Block Global CTP.......................................................................6
2.3 Uploading the Configuration Role...............................................................................6
3 Configuration Part 1 - Before Data Replication...................................................................8
3.1 Configuration for SAP R/3........................................................................................... 8
3.1.1 Creating the Organization Area...........................................................................8
3.1.2 Creating Requirements Class..............................................................................9
3.1.3 Creating the Requirements Type.......................................................................10
3.1.4 Determining the Requirement Type...................................................................11
3.1.5 Creating Strategy............................................................................................... 12
3.1.6 Defining Strategy Group....................................................................................13
3.1.7 Creating the Check Group.................................................................................14
3.1.8 Defining Material Block......................................................................................15
3.1.9 Performing Control for Availability Check..........................................................15
3.1.10 Assigning the Organization Area.......................................................................17
3.1.11 Changing Material Master Data.........................................................................18
3.2 Configuration in SAP APO Before Data Replication.................................................20
3.2.1 Creating the Organization Area.........................................................................20
4 Configuration Part 2 – After Data Replication...................................................................22
4.1 Maintaining the Check Instruction (SAP APO)..........................................................22
4.2 Verifying Check Control............................................................................................ 23
4.3 Settings for Bucket Oriented Capacity Check...........................................................24
4.3.1 Maintaining PP/DS Buckets of Critical Resources.............................................24
4.3.2 Strategy Profile for Bucket Oriented Capacity Check........................................25
4.3.3 Maintaining Strategy Profile as Default..............................................................26
4.4 Maintaining Product Parameters...............................................................................27
5 Troubleshooting................................................................................................................ 28
5.1 Checking Product Parameters in SAP APO..............................................................28
1 Purpose
The Capable-to-Promise building block is required for setting up the scenario Make-to-Order
with Capacity Check.
This configuration guide provides the information you need to manually set up a rough-cut
capacity check during sales order entry. The configuration guide does not cover the settings for
production planning and detailed scheduling of the resources, which takes place after the rough-
cut capacity check. These settings are covered in the configuration guides of the building blocks
Production Planning and Detailed Scheduling.
2 Preparation
2.1 Prerequisites
Before you start with the installation, make sure that you have successfully set up the relevant
sections of the following building block:
 Building block Connectivity
Note that the building block CTP is not configured all at once. You complete the
configuration of the first part, then you need to set up the building block Replication
SCM before you can proceed with the second configuration part of CTP. Refer to
the scenario installation guide and this configuration guide to carry out all activities
in the correct order.
2.2 SAP Notes Building Block Capable-to-Promise

Please install or read the following SAP notes before you start the installation:
SAP Note System Component Description

783827 APO SCM-APO-ATP-EST Error in ATP overview with missing parts
2.3 Uploading the Configuration Role
Use
Before you start with the configuration according to the manual procedures described in this
configuration guide, you need to upload the configuration role and assign it to your user.
SAP Best Practices provides a configuration role for each component involved in this
configuration, that is, for SAP APO or SAP R/3. The configuration role is a special user menu
that enables you to comfortably access all transactions required for the configuration from the
relevant system. The following roles are available:
Technical name Description

S29_01C Configuration Role for Capable-to-Promise (SAP R/3)
S29_02C Configuration Role for Capable-to-Promise (SAP APO)
Procedure
For details on how to upload configuration roles to the system and how to work with the roles,
refer to the document Essential Information.
3 Configuration Part 1 - Before Data Replication

This section covers all configuration steps that have to be performed in SAP R/3 and SAP APO
before the initial data replication.
3.1 Configuration for SAP R/3
You must finish these configuration steps before you start the data replication with
the Building Block Replication.
3.1.1 Creating the Organization Area
Use
This activity is only required if you are using a configurable product for which the class and
characteristics are defined.
Normally, you specify the class type to determine the scope of the class and characteristic to be
transferred in the integration model. However, by defining an organizational area, you can
further limit the selection area. In this activity, you create an organizational area and then assign
it to the classes and characteristics to be transferred in the customizing of the SAP R/3
classification system.
Procedure
1. Access the activity using one of the following navigation options:
SAP R/3 Role Menu Creating the Organization Area

Transaction Code SPRO
IMG Menu SAP Customizing Implementation Guide  Cross-Application
Components  Classification System  Classes  Maintain
Object Types and Class Types
2. On the Change View “Object Table”: Overview screen, select the following entry from the
table on the right:
Table entry Description R/O/C User action and values Note

MARA Material R Choose the button at the
beginning of the table row to
select the table row
3. Double-click the Class Types folder in the Dialog Structure.

4. Select following table row by choosing the button at the beginning of it.
Table entry Description R/O/C User action and values Note

300 Variants R
5. Double-click the Organizational Areas folder in the Dialog Structure.

6. To create a new entry for the table, choose New entries and enter the following values:
Field name Description R/O/C User action and values Note
Class type R Specify the class type 300
Org.area ind. Organization area R Specify the indicator of the new
indicator organizational area, e.g. A
Org. area Organization area O Enter the description of the new
description organizational area, e.g. APO
7. Choose Save to save your entry.

8. Specify a customizing request or create a new one.
9. Go back.
3.1.2 Creating Requirements Class
Use
Requirements classes are assigned to the requirement type and transferred later as the check
mode in SAP APO. In this activity you create a new requirement class that is used by the CTP
scenario.
Procedure
1. Access the activity using the following navigation options:
SAP R/3 Role Menu Creating requirements class

Transaction Code SPRO or OVZG
IMG Menu SAP Customizing Implementation Guide  Sales and Distribution

 Basic Functions  Availability Check and Transfer of
Requirements  Transfer of Requirements  Define
Requirements Classes
2. On the Change View “Requirements Classes”: Overview screen, select requirement class
047 and choose Copy as… to create a new entry.
Copy 040 if you are not using a configurable product.

3. On the Change View “Requirements Classes”: Details of Selected Set screen, enter the
following data:

Reqmts Requirement R Specify the requirement You can change the
class class class, e.g. YCP description of the
requirements class to,
e.g. MTO + CTP
4. Leave other values unchanged and press Enter

5. The message “Number of entries copied:1” appears
6. Choose Save to save the entry
8. Go back.
3.1.3 Creating the Requirements Type
Use
In this activity, you create a new requirements type and assign to it the requirements class
created in the previous step.
Procedure
SAP R/3 Role Menu Creating the Requirements Type

Transaction Code SPRO or OVZH
Requirements  Transfer of Requirements  Define
Requirements Types
2. On the Change View “Requirements Types”: Overview screen, choose New Entries and
enter the following data:

RqTy Requirements type R Specify the requirements type,
name e.g. YCP
Requirements Requirements type R Specify the description of the
type description requirements type, e.g. Make-
to-order with CTP
ReqCl Requirements class R Specify the requirements class,
e.g. YCP

5. Go back.
3.1.4 Determining the Requirement Type
Use
In the standard system, requirement types are determined according to a specific search
strategy beginning with the material strategy group. For example, the system initially tries to find
a requirement type using the strategy group in the material master data. If the strategy group
has not been maintained, the system determines it using the MRP group and then the material
type, and so on.
In this activity, you maintain settings that ensure the requirement type is always derived from the
strategy group of the material master data.
Procedure)
SAP R/3 Determining the Requirements Type

Role Menu
Requirements  Transfer of Requirements  Determination Of
Requirement Types Using Transaction
2. On the Change View “Assignment of Requirement Types to Transaction”: Overview screen,

select the item category your material uses in the sales order, e.g. TAN.
The item category is determined by the Sales order type, Item category group,
Usage and Higher level item category. You can access it via the menu path SAP
Customizing Implementation Guide  Sales and Distribution  Sales  Sales
Documents  Sales Document Item  Assign Item Categories. You can, for
example, check the item category which is determined by the Sales Order Type OR,
Item category group NORM, Usage and Higher level item category with initial value
(blank).
3. Choose Details.
4. On the Change View “Assignment of Requirement Types to Transaction”: Detail screen,

make the following entries:

RqTy Requirement type R Do not make any entries
Q Origin of R Specify the source of the
requirement type requirement type, 0
5. Save and go back.
3.1.5 Creating Strategy
Use
Create a new strategy that uses the new requirement type as the customer requirement type.
Procedure
SAP R/3 Creating Strategy
Role Menu
IMG Menu SAP Customizing Implementation Guide  Production 
Production Planning  Demand Management  Planned
Independent Requirements  Planning Strategy  Define
Strategy
2. On the Change View “Strategy”: Overview screen, select strategy 25 and choose Copy as…
to create a new entry.
Copy 20 if you are not using a configurable product.

3. On the Change View “Strategy”: Details of Selected Set screen, replace the values with the
following data:
Field name Description R/O/C User action and Note
values
Strategy Strategy name R Specify the You can change the
strategy, e.g. YV description of the strategy
e.g. to Make-to-order
for configurable
material
Reqmts type Requirements R Leave this filed
for indep. type for the blank
reqmts independent
requirement
Reqmt type of Requirements R Specify the
customer type for the customer
reqmt customer requirement, e.g.
requirement YCP
4. Choose Enter.
5. Save your entries.
7. Go back.
3.1.6 Defining Strategy Group
Use
In this activity, you create a strategy group and assign the new strategy as the main strategy.
The strategy group will be allocated to the material master later.
Procedure
1. Access the transaction using one of the following navigation options:
SAP R/3 Creating Strategy Group
Role Menu
IMG Menu SAP Customizing Implementation Guide  Production 
Production Planning  Demand Management  Planned
Independent Requirements  Planning Strategy  Define
Strategy Group
2. On the Change View “Strategy Groups”: Overview screen, choose New Entries and make
the following entries:

Strategy group Strategy group R Specify the strategy group, e.g. YV
name
Description Strategy group R Specify the description of the
description strategy group, e.g. Make-to-
order with CTP
Main plg.straty Main strategy R Specify the main strategy, e.g. YV

5. Go back.
3.1.7 Creating the Check Group
Use
The check group is transferred from SAP R/3 to SAP APO as the ATP group. It is used along
with the checking rule to define the scope of the ATP check.
This is an optional activity, but we recommended that you create a new check group for
scenarios with Capable-to-Promise functions.
Procedure
SAP R/3 Creating the Check Group

Role Menu
Requirements  Availability Check  Availability Check with ATP
Logic or Against Planning  Define Checking Groups
2. On the Change View “Availability Check Control”: Overview screen, select check group 02
and choose Copy as… to create a new entry.
3. On the Change View “Availability Check Control ”: Overview of Selected Set screen, replace
the values with the following data:
Av Check group R Specify the check group,
e.g. YV
Description Description of the O Enter the description, e.g.
check group Individ.requirements
TotalSales Total sales order R Specify the requirement „A“ stands for
requirements type A „Single record“
TotDlvReqs Total delivery R Specify the requirement „A“ stands for
requirements type A „Single record“
Block QtRq Material block in R Leave this box blank
availability check
with transfer of
quantities.
No check No availability check R Leave this box blank
Accumul. Availability check R Specify type 3
with cumulative,
confirmed quantities.
4. Choose Enter.
7. Go back.
3.1.8 Defining Material Block
Use
The function you define in this activity prevents users from simultaneously creating two orders
for the same material.
Procedure
SAP R/3 Defining Material Block

Role Menu
Requirements  Availability Check  Availability Check with ATP
Logic or Against Planning  Define Material Block For Other Users
2. On the Change View “Availability Check: Checking Criteria ”: Overview screen, choose New
entries and enter the following data:

AvailCheck Check group R Enter the check group YV
Initiator R Choose the processing type A A stands for
sales order
Block R Select this checkbox
3. Repeat step 2 to add the entries for the initiator B and C.

6. Go back.
3.1.9 Performing Control for Availability Check
Use
In this activity, you define checking rules for the availability check and allocate them to the new
check group. These settings will be transferred to SAP APO as the check control.
Procedure
SAP R/3 Performing Control for Availability Check

Role Menu
IMG Menu SAP Customizing Implementation Guide  Sales and Distribution 
Basic Functions  Availability Check and Transfer of Requirements
 Availability Check  Availability Check with ATP Logic or Against
Planning  Carry Out Control For Availability Check
2. On the Change View “Availability Check Control”: Overview screen, select the entries with
check group 02 and checking rule AE. Choose Copy as… to create a new entry.
3. On the Change View “Availability Check Control ”: Details of Selected Set screen, replace
the values with the following data:
Field name Description R/O/C User action and Note
values
Availability Check group R Specify the check
check group, e.g. YV
Checking rule Checking rule R Specify the checking
rule e.g. AE
Check without Check R Select this checkbox Do not consider the
RLT availability RLT as an order
without with a delivery date
replenishment after the RLT is
lead time always confirmed
Include sales Include sales R Select this checkbox
reqmts requirement
Include Include the R Select this checkbox
deliveries delivery
Incl. Planned Include planned R Enter the value X
orders order
Incl. Production Include R Enter the value X
orders production order
4. Choose Enter.
7. Go back.
3.1.10 Assigning the Organization Area
Use
This activity is only required if you are using a configurable product for which the class and
characteristics are defined. In this activity, the new organization area is assigned to your
classes. Do not perform this activity if you are working with non-configurable materials.
Procedure
SAP R/3 Assigning the Organization Area

Role Menu
Transaction Code CL02
SAP Menu SAP Menu  Logistics  Central Functions  Classification 
Master Data  Classes
2. On the Class screen, enter the following data:

Field name Description User action and values Notes
Class Specify the name of the class,
e.g. E71_ROBOT
Class type Specify the class type, e.g. 300
3. Choose Change to modify the data.

4. On the Change Class screen, choose the Basic data tab and enter the following data:
Organizational area Specify the organizational area, e.g. A
5. Choose the Char. tab page, and enter the following data for all characteristics in the table:
Org.areas Organizational area Specify the organizational area, e.g. A

7. Repeat steps 2 to 6 to change all your classes.
8. Go back.
3.1.11 Changing Material Master Data
Use
In this activity, you assign the new strategy group, the dependent requirements indicator and the
new availability check group to all materials that you are going to transfer to the APO system
and for which you will perform the capacity check.
Procedure
SAP R/3 Changing Material Master Data

Role Menu
Transaction Code MM02
SAP Menu SAP Menu Logistics  Production Master Data  Material
Master Data Material  Change Immediately
2. On the Change Material (Initial Screen) screen, enter the following data:

Material Material number Specify the material number, e.g. H62-1000
3. Choose Enter.
4. In the Select View(s) dialog box, select MRP3 and MRP4 and choose Enter.
5. In the Organizational Levels dialog box, enter the following data:
Plant Specify the plant, e.g. BP01
6. Choose Enter.
7. On the MRP3 tab, enter the following data:

Strategy group Specify the strategy group, e.g. YV
Availability check Specify the availability check group, e.g. YV
8. Choose the MRP4 tab and enter the following data:
Field name Description User action and values Note

Individual/ Dependent Specify the value 1 if the material is a finished or a
coll. requirement semi-finished good that is also the header material
indicator of a BOM.
Specify the value 2 if the material is a raw material
or a semi-finished good without further BOM.
10. Repeat steps 2 to 9 to change all your materials.
11. Go back.
You can also perform these changes using mass maintenance. To do this, open
transaction MM17, choose the MARC table from the Tables tab and the following
fields from the Fields tab:
 MARC-STRGR
 MARC-MTVFP
 MARC-SBDKZ.
For a detailed description on working with the mass maintenance transaction, refer
to the building block Replication.
Be careful when working with the mass maintenance transaction.
3.2 Configuration in SAP APO Before Data Replication
You must carry out these activities before you start the data replication, otherwise
you will encounter configuration problems. For example, the class and characteristic
assignment will not be made if you start the data replication before you have
completed the following configuration activities.
3.2.1 Creating the Organization Area
Use
This activity is only required when you are using a configurable product for which the class and
characteristics are defined.
Neither the classification customizing nor the characteristic/class groups are transferred by APO
core interface (CIF). This means that the customizing must be assigned to the relevant class
types in SAP APO and all SAP R/3 systems concerned. The organizational areas are parts of
the customizing; therefore, they are not transferred by CIF. They must be created separately in
SAP APO for the relevant class type. If the organization area does not exist, the class and
characteristic assignment is not made.
Procedure
SAP APO Creating the Organization Area
Role Menu
IMG Menu mySAP SCM - Implementation Guide à Cross-Application
Components à Classification System à Classes à Maintain
Object Types and Class Types
2. On the Change View “Object Table”: Overview screen, choose the following entry from the
table in the right screen area:
MARA Material Select the entry by choosing the button
at the beginning of the table row
3. In the Dialog Structure, double-click the Organizational Areas node.

4. Choose New entries to add the following entries to the table.
Class type Specify the class type 300
Org.area ind. Organization Specify the indicator of the new
area indicator organizational area, e.g. A
Org.area Organization Input the description of the new
area description organizational area, e.g. APO

7. Go back.
Result
You have finished the installation of the activities required before you can start the data
replication. Go back to the Make-to Order with Capacity Check scenario installation guide and
proceed with the Data Replication section.
4 Configuration Part 2 – After Data Replication

This section covers all configuration steps that have to be performed after data replication has
taken place. These steps are exclusively performed in SAP APO.
4.1 Maintaining the Check Instruction (SAP APO)
Use
In this activity, you maintain the check instruction that controls the Capable-to-Promise process.
You also need to create a new check instruction used when converting a planned order to a
production order.
Procedure
SAP APO Maintaining the Check Instruction

Role Menu
IMG Menu mySAP SCM - Implementation Guide à Advanced Planning and

Optimization à Global Available-to-Promise (Global ATP) à
General Settings à Maintain Check Instructions
2. On the Change View “Maintain Check Instruction”: Overview screen, select the required
check instruction, e.g. YCP (Check mode)/AE (Business Event).
3. Choose Detail.
4. On the Change View “Maintain Check Instruction”: Details screen, make the following
entries:
Section Field name R/O/C User action and values Note
Maintain Product Check R Select the value First
Check Step
Instructions
Production Start Production R Select the value
Availability Check
First, then
Production
Production Production R Select the value After
Time executing all basic
methods
Production Re-create R Select With this setting, the
receipt receipts created
elements previously will be
deleted and new
elements are
generated in the
ATP check.
5. Choose Save and go back.

6. On the Change View “Maintain Check Instruction”: Overview screen, choose New Entries.
7. On the New Entries: Details of Added Entries screen, make the following entries:

Check Mode Check mode R Enter the same check mode you
have just maintained, e.g. YCP
Business Event Business event R Enter the business event PP

Product Check Product check R Choose the value First Step
8. Choose Save and go back twice.
4.2 Verifying Check Control
Use
In this activity, you verify that the check control is configured correctly to ensure that the
Capable-to-Promise functions work. Note that for scenarios with CTP functions, the scope of
check refers to the ATP check within the planned order or during the conversion of the planned
order to a production order. It does not refer to and does not play any role for the availability
check, which is performed during sales order creation.
Procedure
SAP APO Verifying Check Control

Role Menu

Optimization à Global Available-to-Promise (Global ATP) à
Product Availability Check à Maintain Check Control
2. On the Change View “ATP Check Control: General”: Overview screen, choose the check
control, e.g. YV (ATP Group)/AE (Business Event), then choose Detail and make
sure that the Consider CH checkbox is not selected.
3. Choose Save
4. Choose the check control YV (ATP Group)/AE (Business Event)again, then choose
Copy as…
5. Change the Business Event to PP and choose Enter.
6. In the Specify objects to be copied, choose Copy all.
7. Confirm the information message “Number of dependent entries copied:…”
8. Select the line with the check control you have just defined and double-click the ATP Check
Control: Scope of Check folder.
In the new window, you will see all categories (requirements and receipts) that are taken into
consideration when the ATP check takes place in the planned order or during the conversion
of the planned order to a production order.
9. Choose Save and go back twice.
4.3 Settings for Bucket Oriented Capacity Check

The check of the capacity requirements of an operation against the available bucket capacity is
carried out finitely. If sufficient capacity is available in the required bucket, the system reserves it
for the operation. At the same time, the operation is scheduled infinitely on the time-continuous
capacity
The system repeats the planning steps until it has found sufficient bucket capacity for all
activities of an operation
4.3.1 Maintaining PP/DS Buckets of Critical Resources
Use
In this activity, you maintain the PP/DS bucket capacity of the critical resources. These settings
enable a bucket oriented capacity check of these critical resources during sales order creation.
Procedure
SAP APO Maintaining PP/DS buckets of critical resources

Role Menu
Transaction Code /SAPAPO/RES01
SAP Menu SAP Menu  Advanced Planning and Optimization  Master Data
 Resource  Resource
2. On the Resources screen, make the following entries:
Field name Description User action and values

Resource Name of a resource e.g. WH62WRK1_1000_008
Location Location where the resource is e.g. PLBP01/KD6147
to be changed
Planning Version always specify the version 000
3. Choose Change
4. In the lower part of the screen, go to the PP/DS Bucket Capacity tab and make the following
entries:

Bucket From Time-Continuous
Definition capacity
Bucket Define the size and start time of the Day (Start: 00:00)
Schema PP/DS bucket
Bucket Only relevant when working with
Factor sequence-dependent setup activities
Finite Bucket capacity
Capacity
You should always choose a bucket size that corresponds to the size of the
operation. The bucket size should be several times larger than the duration of the
average operation. The bucket size should be sufficiently large so that even an
operation of a large planned order can be carried out within a bucket. Alternatively,
you can define the maximum lot size in the product master record so that all
operations can be carried out within a bucket
5. Choose Bucket Capacity to display the available capacity of the bucket
6. Choose Check Plans to check that the resource can be included for the bucket oriented
capacity check.
A resource for which you have maintained the parameter PP/DS Bucket Capacity
can only be included in a bucket-oriented capacity check if you have assigned it as
a primary resource in the mode of the activity in the production data structure, and, if
you have set the calendar resource indicator. This indicator determines that the
resource working times are used for the scheduling of the activity. If the resource is
used as a secondary resource and/or the Calendar Resource indicator is not set,
the system schedules infinitely.
7. Choose Save.
8. Repeat the same procedure for the model independent version.
Result
The PP/DS bucket capacity has been maintained.
If the resource to be included in the bucket oriented capacity check is used as a secondary resource
and/or the Calendar Resource indicator is not set, you have to go back to your SAP R/3 system and
maintain the resource as a primary resource in the respective mode of the activity. Afterwards you
need to re-transfer the data to the SAP APO system.
4.3.2 Strategy Profile for Bucket Oriented Capacity Check
Use
It is recommended to work with the standard strategy profile delivered by SAP for the bucket-
oriented capacity check SAP_BCTP.
If you want to work with your own strategy profile, open transaction /SAPAPO/CDPSC1, choose
the profile SAP_BCTP and choose Copy as… and make the appropriate changes.
You can copy this profile to create a strategy profile with your own settings.
4.3.3 Maintaining Strategy Profile as Default
Use
You can determine that the strategy profile for the bucket oriented capacity check is used as the
default strategy profile during sales order entry.
Procedure
SAP APO Maintaining Global Parameters and Defaults

Role Menu
Optimization à Supply Chain Planning à Production Planning &
Detailed Scheduling à Global Settings à Maintain Global
Parameters and Defaults
2. Choose Change.
3. In the Schedule Orders: Strategy Profiles section, assign the strategy profile you have
created:
Field name R/O/C User action and values Note

Capable-to-Promise R Choose following profile e.g. SAP_BCTP
4. Choose Save and go back.
4.4 Maintaining Product Parameters
Use
In this activity, you maintain product parameters that are specific for capable-to-promise
functions, which are used in the SAP Best Practices for SCM scenario Make-to-Order with
Capacity Check.
Procedure
1. Access the transaction choosing one of the following navigation options:
SAP APO Maintaining SAP APO Product Parameters Individually
Transaction code /SAPAPO/MAT1
SAP menu Advanced Planning and Optimization  Master Data  Product
2. On the Product Master screen, enter a product number in the Product field, a location in the
Location field and choose Change.
3. On the Display Product ....for Location screen, go to the PP/DS tab page and make the
following entries:
Field Value
Planning Procedure
For each planning-relevant (3): Cover Dependent Req. immediately:
event that can occur for a Choose this procedure for all finished goods in the CTP
location product, the planning scenario. In addition, enter this procedure for all
procedure defines which components which are critical (consider performance!)
action is executed by Critical products are, for example, those with very long
(PP/DS) if this event occurs. replenishment times
(4): Planning in planning run (usually used)
Choose this procedure for all other materials.
Product Heuristic
Product Heuristic profile to be SAP_PP_003 – Planning of shortage quantities
used for PP/DS (suitable for “Make to Order” products)
4. Choose Save.
5. Repeat steps 2-4 for the remaining location products.
6. Go back.
You can also perform these changes using mass maintenance. To do this, refer to
the section “Maintaining SAP APO Product Parameters using Mass Maintenance” of
this document. In the Components and Attributes to be maintained screen area,
specify the parameters Location-Dependent Data: Heuristic and Location-
Dependent Data: PP Plng Proced.
Be careful when working with the mass maintenance transaction.
Result
You have completed the configuration of the building block Capable-to-Promise. Go back to the
scenario installation guide and proceed with the configuration of the next building block
5 Troubleshooting
5.1 Checking Product Parameters in SAP APO
1. To check product parameters in SAP APO, choose one of the following navigation options:
SAP APO menu SAP menu  Advanced Planning and Optimization  Master data
 Product  Product
Transaction Code /SAPAPO/MAT1
2. In the Product Master. Initial screen, enter your product number and
choose Change.
3. Go to the ATP tab page and make sure that the check mode and ATP group of the products
have been correctly transferred.
4. On the Demand tab page,
 Select the Possible indiv. Cust. Reqt radio button if the material is a finished good or a
semi-finished good that also serves as the header material of a BOM and is produced in
house.
 Select the Always coll. Requirement radio button if the material is an externally
procured component or semi-finished good.

S29 BB ConfigGuide en de

Uploaded by

Copyright:

Available Formats

S29 BB ConfigGuide en de

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

S29 BB ConfigGuide en de

Uploaded by

Copyright:

Available Formats

SAP SCM 4.

© Copyright 2004 SAP AG. All rights reserved.

Oracle is a registered trademark of Oracle Corporation.

Java is a registered trademark of Sun Microsystems, Inc.

MaxDB is a trademark of MySQL AB, Sweden.

Type Style Description

2.2 SAP Notes Building Block Capable-to-Promise

SAP Note System Component Description

2.3 Uploading the Configuration Role

Technical name Description

3 Configuration Part 1 - Before Data Replication

3.1 Configuration for SAP R/3

3.1.1 Creating the Organization Area

SAP R/3 Role Menu Creating the Organization Area

Table entry Description R/O/C User action and values Note

3. Double-click the Class Types folder in the Dialog Structure.

Table entry Description R/O/C User action and values Note

5. Double-click the Organizational Areas folder in the Dialog Structure.

7. Choose Save to save your entry.

3.1.2 Creating Requirements Class

SAP R/3 Role Menu Creating requirements class

IMG Menu SAP Customizing Implementation Guide  Sales and Distribution

Copy 040 if you are not using a configurable product.

Field name Description R/O/C User action and values Note

4. Leave other values unchanged and press Enter

3.1.3 Creating the Requirements Type

SAP R/3 Role Menu Creating the Requirements Type

Field name Description R/O/C User action and values Note

3. Choose Save to save your entry.

4. Specify a customizing request or create a new one.

3.1.4 Determining the Requirement Type

SAP R/3 Determining the Requirements Type

2. On the Change View “Assignment of Requirement Types to Transaction”: Overview screen,

4. On the Change View “Assignment of Requirement Types to Transaction”: Detail screen,

Field name Description R/O/C User action and values Note

5. Save and go back.

3.1.5 Creating Strategy

Copy 20 if you are not using a configurable product.

3.1.6 Defining Strategy Group

Field name Description R/O/C User action and values Note

3. Save your entries.

4. Specify a customizing request or create a new one.

3.1.7 Creating the Check Group

SAP R/3 Creating the Check Group

3.1.8 Defining Material Block

SAP R/3 Defining Material Block

Field name Description R/O/C User action and values Note

3. Repeat step 2 to add the entries for the initiator B and C.

4. Choose Save to save your entry.

3.1.9 Performing Control for Availability Check

SAP R/3 Performing Control for Availability Check

3.1.10 Assigning the Organization Area

SAP R/3 Assigning the Organization Area

2. On the Class screen, enter the following data:

3. Choose Change to modify the data.

6. Choose Save to save your entry.

3.1.11 Changing Material Master Data

SAP R/3 Changing Material Master Data

Field name Description User action and values Notes