basic configuration for rba

8/11/2019 Basic Configuration for RBA

http://slidepdf.com/reader/full/basic-configuration-for-rba 1/24

Basic Configuration for RBA

Define the Condition Table:

Maintain Field Catalog: Like fields of Tables (Master Data)

Name of the condition field

This indicator specifies fields that you can choose when creating or maintaining a condition table.

Use

When you create or maintain a condition table, you only see the fields specified for a specificcombination of use and application. These fields are also used by the access sequences whensearching for valid condition records during the processing of the conditions.

Example

Using the field catalog, you determine which fields can be used for the condition technique. Forexample, when the field values of the sales order correspond to the condition records at runtime,the condition record that was found specifies the rule to be used in the availability check.



Create Condition Table



Condition Table

Definition

Combination of specific fields which creates the key of a condition record.

Use

In a rule strategy, you define the sequence of condition types. An access sequence can beassigned to the respective condition type. This specifies where exactly the system should searchfor the condition records which are relevant to a certain condition type.

Every access in the access sequence refers to a condition table. Using the fields (of the key, thatis) defined in the table, the system can trace the valid condition records.

The condition tables are used in rules-based ATP (use "O") or in transportation and shipmentscheduling (use "U").

Procedure

When creating a condition table, define one or several target fields as a table key. In addition, youmust enter information into the system as to where it should take the target field value from. Todo this, specify a source field. Source field and target field are identical as a rule, but can also bedifferent.

If the target field "customer" is part of the key, you can determine, for example, that the systemshould use "ship-to party" as a source field and should adopt the value found there.



Change Condition Table: To Change Condition Table

Enter a Table and enter



Change and then Generate

Display Condition Table



Maintain Access Sequence

Select one Access Sequence and go to Accesses Tab

Select and go to Fields Tab



Source of specific value

Value with which a field is filled by the system when accessing a condition record.

Access Type to a Key Field in Access

Specifies the type of access to a key field within an access in an access sequence.

Use

You can assign the following access types to a key field:

• Fixed key field

For fields to which you have assigned the access type fixed key field , you must definevalues in rule determination.

• Free key field

For fields to which you have assigned the access type free key field , you do not have todefine values in rule determination. However, you must assign these fields a priority.

The system can use the access type to also determine a rule if no suitable values for free keyfields have been transferred from the sales order, provided the following conditions have beenfulfilled:

• The values of the fixed key fields match the values from the sales order.

• You have not defined any values for all the free key fields that do not match the values

from the sales order.

At the start, the fixed key field access type is automatically assigned to all key fields of the access.

Prerequisites

You have marked the field so that it appears as an item on the fast entry screens.

Example



You have created a condition table with the following fields:

• Fixed key fields

o Order type AUART

o Sales organization VKORG

• Free key fields

o Customer group KUGRP

o Customer KUNNR

o Region REGIO

In this case, in rule determination, you must define values for the order type and salesorganization fields. You can define values for the customer group, customer, and region fields.

Characteristic: Initial value allowed

The initial inicator has two functions in Customizing for access sequences. Firstly, it controls thatthe system also accesses the condition if the field in the document header/item is blank or 0.Secondly, it allows an initial value to be returned during the automatic return transfer of data,which was determined in the access.

Access sequence - Access number

Sequential number for access within the access sequence.



Maintain Condition Type

Define the condition type and assign the access sequence to the condition type

Condition Type

Use

The condition type is used for different functions. By using the condition type in pricing, forexample, different discounts, different output types in the output determination, such as orderconfirmations or delivery notes, as well as different strategy types in the batch determination are

defined.

In the rules-based availability check, the rule strategy refers to one or more condition types. Eachcondition type is assigned to exactly one access sequence. The access sequence contains a listof accesses to condition tables.

The system searches the condition tables for the matching key combination.



Maintain Rule Strategy

Rule Strategy

The rule strategy refers to one or more condition types in the rules- based availability check.

Use



Exactly one access sequence is assigned to each condition type. An access sequence contains alist of accesses, which are also referred to as condition tables. Each condition table contains oneor more fields.

Comparison values, which lead to the determination of the rule based on the condition type andcondition table, are saved for the relevant tables in the rule determination.

Rule Strategy Type

Indicates one of the following rule strategies:

• Inclusive rule strategy

• Exclusive rule strategy

Use

The system uses inclusive rule strategies to determine substitution lists for the rules-basedavailability check.

The system uses exclusive rule strategies to determine which location products to remove fromthe substitution lists of inclusive rule strategies. In addition, you can use exclusive rule strategiesto define exceptions and alternatives to exclusions.

• Exceptions to exclusions ( exclusive rules in exclusive rule strategies)

If an exclusive rule strategy also contains exclusive rules, these are applied to theinclusive rules of this rule strategy as exclusions. This means that these substitutions are

deleted from the inclusive rules. The remaining substitutions from the inclusive rules ofthe exclusive rule strategy are then applied to inclusive rule strategies as exclusions.

• Alternatives to exclusions ( alternative rules in exclusive rule strategies)

An alternative rule is only evaluated in exclusive rule strategies. This rule is only used asa location alternative for exceptions when exclusive rule strategies are applied toinclusive rule strategies.

Dependencies

Exclusive rule strategies define exclusions within inclusive rule strategies. For that reason, thesystem can only evaluate exclusive rule strategies within the context of a rule strategy sequence that also contains inclusive rule strategies.

Rule Strategy Defines Number of Substitutions

Indicates that the system determines the number and entity of the substitutions by means ofevaluation of the rule strategy and not by means of evaluation of the rules.



Use

If you set this indicator, the settings that you specify here for the number and entity of thesubstitutions apply to all rules in this rule strategy. The system overwrites the settings for thenumber and entity of the substitutions that you have made, as necessary, in integrated rulemaintenance.

Note

The system only takes account of this indicator in inclusive rule strategies.

Select one entry and select Control Data to assign the condition type to the rule strategy

Rule Strategy

The rule strategy refers to one or more condition types in the rules- based availability check.

Use

Exactly one access sequence is assigned to each condition type. An access sequence contains alist of accesses, which are also referred to as condition tables. Each condition table contains oneor more fields.

Comparison values, which lead to the determination of the rule based on the condition type andcondition table, are saved for the relevant tables in the rule determination.

Level number

Number that determines the sequence of condition types within the rule strategy.

Condition Counter

Sequential number of the conditions within a step in a calculation procedure.



Use

The sequence defined by the counter is adopted for automatic price determination.

Condition Type

Use

The condition type is used for different functions. By using the condition type in pricing, forexample, different discounts, different output types in the output determination, such as orderconfirmations or delivery notes, as well as different strategy types in the batch determination aredefined.

In the rules-based availability check, the rule strategy refers to one or more condition types. Eachcondition type is assigned to exactly one access sequence. The access sequence contains a listof accesses to condition tables.

The system searches the condition tables for the matching key combination.

Condition

Determines under which circumstances an access from the system to a specific condition type isexcluded.

Examples

One possible condition could be, for example, that no access to the condition type is made if thedocument currency is the same as the local currency.

Maintain Rule Strategy Sequence

To determine which rule strategies the system evaluates together and the sequence in which thesystem evaluates these rule strategies



Rule Strategy = Technical Scenario + Action Type + Business Transaction

Select an item and go to Control Tab



Rule Strategy Sequence

A rule strategy sequence specifies the sequence in which rule strategies are evaluated within arules-based ATP check.

Use

Rule strategy sequences can be used to define and improve the structure of complex searchareas (products and locations) for the ATP check.

The following special cases can only be mapped using rule strategy sequences:



Number of Rule Strategy

Indicates the sequence in which the system evaluates the inclusive rule strategies of a rulestrategy sequence.

Since the system always evaluates the exclusive rule strategies before the inclusive rulestrategies, the rule strategy number only applies to the inclusive rule strategies.

Rule Strategy

A rule strategy determines all rules for a rules-based ATP check.

The following rule strategy types exist:

• Inclusive rule strategies

• Exclusive rule strategies

Rule Strategy Type

Indicates one of the following rule strategies:

• Inclusive rule strategy

• Exclusive rule strategy

Use

The system uses inclusive rule strategies to determine substitution lists for the rules-basedavailability check.



The system uses exclusive rule strategies to determine which location products to remove fromthe substitution lists of inclusive rule strategies. In addition, you can use exclusive rule strategiesto define exceptions and alternatives to exclusions.


If an exclusive rule strategy also contains exclusive rules, these are applied to theinclusive rules of this rule strategy as exclusions. This means that these substitutions aredeleted from the inclusive rules. The remaining substitutions from the inclusive rules ofthe exclusive rule strategy are then applied to inclusive rule strategies as exclusions.


An alternative rule is only evaluated in exclusive rule strategies. This rule is only used asa location alternative for exceptions when exclusive rule strategies are applied toinclusive rule strategies.

Dependencies

Exclusive rule strategies define exclusions within inclusive rule strategies. For that reason, thesystem can only evaluate exclusive rule strategies within the context of a rule strategy sequence that also contains inclusive rule strategies.

Assign Rule Strategy or Rule Strategy Sequence



Rules-based ATP: Technical Scenario

The technical scenario of the process that calls the rules-based availability check.

Use

You can control in which technical scenarios a rules-based availability check is executed.

Examples

User transactions, EDI, internet functions or batch processing

Note

This value is determined from the calling application when calling from the R/3 System. You canuse your own values for simulations in APO.

Rules-Based ATP: Business Transaction

The business transaction that calls the rules-based availability check.

Use

You can control for which business transactions a rules-based availability check is executed.

Examples

A rush order usually does not execute a rules-based availability check.

Note

When calling from the R/3 System, this value is determined using the order category of the callingsales order. You can use your own values for simulations in APO.

Rules-based ATP: Action Type

Action type that calls the rules-based availability check.

Use

You can control for which action types a rules-based availability check is carried out.

Examples



Create, change, copy

Note


Rule Strategy Sequence

A rule strategy sequence specifies the sequence in which rule strategies are evaluated within arules-based ATP check.

Use

Rule strategy sequences can be used to define and improve the structure of complex searchareas (products and locations) for the ATP check.

The following special cases can only be mapped using rule strategy sequences:



Rule Strategy





Handling Calculation Profiles

Substitute or supplement the calculation profile for the rules-based availability check.

Use

You use this field to control how several calculation profiles that can be derived from successiveaccesses are used. You can choose if a subsequent profile overwrites or supplements itspredecessor.



Example

You want to make the delivery date tolerance dependent on the customer. However, theconsumption limit, which lies in the past and protects your inventory, should only be determinedby the production location. In this example, you specify two accesses and choose add .

Preselection of Suitable Substitutions

Determines that the preselection of suitable substitutions is allowed.

Use

If you set this indicator, you switch on preselection of suitable substitutions. You are then able toselect the most suitable substitution from the substitution list.

If you do not set this indicator, you do not switch on preselection of suitable substitutions.

Dependencies

For the system to preselect suitable substitutions, you must also make this setting in the checkinstructions. For more information, see the Implementation Guide (IMG) of SAP SCM underMaintain Check Instructions.

Create Business Transaction for Multilevel ATP Check



Rules-based ATP: Technical Scenario

The technical scenario of the process that calls the rules-based availability check.

Use

You can control in which technical scenarios a rules-based availability check is executed.

Examples

User transactions, EDI, internet functions or batch processing

Note




Use




Examples


Note


Rules-based ATP: Action Type

Action type that calls the rules-based availability check.

Use

You can control for which action types a rules-based availability check is carried out.

Examples

Create, change, copy

Note


Check Mode

The check mode derived from the product master record and the business event determine thetype and scope of the checks to be carried out. In addition, the check mode controls consumptionusing the forecast.

The SD (R/3) uses the requirements class of the requirement as a check mode. As of R/3 Plugin2000.1, the requirements class (via the strategy group in the material master) is transferred to thelocation-specific APO product master (tab page ATP). No plausibility check takes place. Youshould therefore not enter any other check mode in the product master, as the check mode in theproduct master must match the requirements class from the SAP R/3 system.

Use

You assign a check mode to the business transaction for the multilevel ATP check.

Dependencies

Note that the multilevel ATP check must be set in the check mode.





Use

You define a business transaction for the multilevel ATP check to enable a rules-based ATPcheck at component level.

Dependencies

When the multilevel ATP check is called, another rule strategy is generally used. This rulestrategy leads to evaluation of rules that you defined specifically for the components. For moreinformation see Create Business Transaction for Multilevel ATP Check.

Activate Multi-Item Single Delivery Location





Use


Examples


Note


Characteristic Value

Specifies the value of a characteristic. This is supplied from the sales order.

Use

• Product allocationThe product allocation used for the current order is determined using the characteristicsof a product allocation group (characteristics combination).

If a characteristics combination is not found in the characteristics directory, the systemtries to determine a collective product allocation using the wildcard character.

• Rules-based availability checkThe characteristic values are used to determine the rules of the current requirement.

• Transportation and shipment schedulingThe characteristic values are used for date determination.

• Event-driven quantity assignment

The characteristic values are used to check the validity of the activity and thus the

process category.

Note

Most characteristic values are supplied by the calling system.Special characteristics must be determined via a user exit in the calling system from the salesorder and the master data. They must also be updated in the list.

Characteristic values of user-specific characteristics must be updated by the user exit.



Activate Multi-Item Single Delivery Location

Determines whether the multi-item single delivery location is active or not.

Use

If you set this indicator, you activate the multi-item single delivery location. As a result, you enablethe requirements grouping to be delivered from one location.

Rule Strategy





basic configuration for rba

Documents