Sct Erp607 Bb Configguide en Xx

BB Configuration Guide

EHP7 for SAP ERP 6.0

April 2014EnglishEnglish

Availability Check Settings (SCT)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyBuilding Block Configuration Guide

Copyright 2014 SAP AG or an SAP affiliate company. 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 or an SAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG (or an SAP affiliate company) in Germany and other countries. Please see http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP AG or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP AG or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP AG or SAP affiliate company 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.

In particular, SAP AG or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP AGs or its affiliated companies strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP AG or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

Icons

IconMeaning

Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type StyleDescription

Example textWords 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 textEmphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXTNames 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 textScreen 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 TEXTKeys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example textExact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

Content

51Purpose

52Preparation

52.1Prerequisites

53Configuration

53.1Availability Check Settings

53.1.1Defining Requirements Classes

63.1.2Defining Requirements Types

73.1.3Defining Strategy

93.1.4Defining Strategy Group

93.1.5Defining Checking Groups

Availability Check Settings1 Purpose

This configuration guide provides you with the information you need to set up the configuration of this building block manually.

If you do not want to configure manually and prefer an automated installation process using BC Sets and other tools, refer to the SAP Best Practices Quick Guide, located on this packages SAP Note.2 Preparation

2.1 Prerequisites

Before you start installing this building block, you must install prerequisite building blocks. For more information, see the Building Block Prerequisite Matrix located on the HTML DVD on the Technical ( Content Library page.3 Configuration3.1 Availability Check Settings3.1.1 Defining Requirements ClassesUse

Requirements classes are assigned to the requirement type and transferred later as the check mode in SAP SCM. In this activity, you create a new requirement class for each global ATP scenario that you want to use.The following scenarios can be implemented:S60Global Available-to-Promise (Global ATP) with Product Availability Check (PAC)

S61Global Available-to-Promise (Global ATP) with Check against Product Allocation (PAL)

S62Global Available-to-Promise (Global ATP) with Rules-Based Availability Check (RBA)

Procedure

1. Access the activity using the following navigation options:Transaction codeSPRO or OVZG

SAP ERP IMG menuSAP 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, choose New Entries and create the following entries:Scenario:S60Global Available-to-Promise (Global ATP) with Product Availability Check (PAC)

Field nameValue

Reqmts classYA1

DescriptionSale from stock PAC

AvailabilityX

Req. transferX

Allocation ind.1

Prod.allocation

Ind.req.reductn

No MRP

3. Choose Save.4. Specify a customizing request or create a new one.

5. Go back.Repeat steps 2. To 5. For the following data according to your selected scenario:S61Global Available-to-Promise (Global ATP) with Check against Product Allocation (PAL)

Field nameValue

Reqmts classYA2

DescriptionSale from stock PAL

AvailabilityX

Req. transferX

Allocation ind.1

Prod.allocationX

Ind.req.reductn

No MRP


Field nameValue

Reqmts classYA3

DescriptionSale from stock RBA

AvailabilityX

Req. transferX

Allocation ind.1

Prod.allocation

Ind.req.reductn

No MRP

3.1.2 Defining Requirements Types

Use

In this activity, you create a new requirements type and assign to it the requirements class you created in the previous step.

Procedure

1. Access the activity using the following navigation options:Transaction codeSPRO or OVZH

SAP ERP IMG menuSAP Customizing Implementation Guide ( Sales and Distribution ( Basic Functions ( Availability Check and Transfer of Requirements ( Transfer of Requirements ( Define Requirements Types

2. On the Change View Requirements Types: Overview screen, choose New Entries and enter the following data:S60Global Available-to-Promise (Global ATP) with Product Availability Check (PAC)

Field nameDescriptionValue

RqTyRequirements type nameYA1

Requirements typeRequirements type descriptionSale from stock PAC

ReqClRequirements classYA1

3. Choose Save to save your entry.

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



Field nameDescriptionValue


Requirements typeRequirements type descriptionSale from stock PAL

ReqClRequirements classYA2


Requirements typeRequirements type descriptionSale from stock RBA


3.1.3 Defining Strategy

Use

Create a new strategy that uses the new requirement type as the requirement type of customer requirement.

Procedure1. Access the activity using the following navigation option:Transaction codeSPRO

SAP ERP IMG menuSAP Customizing Implementation Guide ( Production ( Production Planning ( Demand Management ( Planned Independent Requirements ( Planning Strategy ( Define Strategy

2. On the Change View Strategy: Overview screen, choose New Entries.3. On the New Entries: details of Added Entries screen, create the following entries:S60Global Available-to-Promise (Global ATP) with Product Availability Check (PAC)

Field nameValuesDescription

StrategyYASale from stock PAC

Reqmts type for indep.reqmtsVSF

Reqmt type of customer reqmtYA1

4. Choose Enter.

5. Save your entries.




StrategyYBSale from stock PAL





StrategyYCSale from stock RBA



3.1.4 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. The strategy in the material master determines among other factors the procedure of the availability check.Procedure1. Access the activity using the following navigation option:Transaction codeSPRO

SAP ERP IMG menuSAP 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:S60Global Available-to-Promise (Global ATP) with Product Availability Check (PAC)

Field nameValues

Strategy groupYA

DescriptionSale from stock PAC

Main StrategyYA

3. Save your entries.




Field nameValues

Strategy groupYB

DescriptionSale from stock PAL

Main StrategyYB

Strategy groupYC

DescriptionSale from stock RBA

Main StrategyYC

3.1.5 Defining Checking GroupsUse

The checking group specifies whether and how the system checks availability. It is transferred from SAP ERP to SAP SCM as the ATP group. For products with rules-based ATP check it is recommended to use a specific ATP group and therefore, it is necessary to create a new checking group in SAP ERP. The purpose of this step is to create a new checking group in ERP, if it is already created by other scenario, please check the settings.

For the following scenarios it is optional to create a new Checking Group.

S60Global Available-to-Promise (Global ATP) with Product Availability Check (PAC)

S61Global Available-to-Promise (Global ATP) with Check against Product Allocation (PAL)

Procedure

1. Access the activity using the following navigation option:Transaction codeSPRO

SAP ERP IMG menuSAP Customizing Implementation Guide ( Sales and Distribution Basic Functions ( Availability Check and Transfer of Requirements ( Availability Check ( Availability Check with ATP Logic or Against Planning ( Define Checking Groups

2. On the Change View Availability Check Control: Overview screen, choose New Entries.3. On the New Entries: Overview of Added Entries screen create the following entries:S60Global Available-to-Promise (Global ATP) with Product Availability Check (PAC)

Field nameValuesNote

AvYA

DescriptionIndivid. requirements

TotalSalesAA stands for Single Record

TotDlvReqsAA stands for Single Record

Block QtRqXBlock on the material which is only in place during the availability check.

Accumul.33Required quantity when created, conf. qty when changed

4. Choose Save to save your entry and go back.Repeat steps 2 to 4 for Checking Groups YB and YC with the same entries as above for the following scenarios:S61Global Available-to-Promise (Global ATP) with Check against Product Allocation (PAL)


Documents

Sct Erp607 Bb Configguide en Xx