SAP ABAP Data Element RBACONTROL (Control of Rules-Based ATP Check)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM-BTX-BF-IF (Application Component) R/3 Interface for Business Transactions
     ⤷ VA (Package) Application development R/3 Sales
Basic Data
Data Element RBACONTROL
Short Description Control of Rules-Based ATP Check  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type RBACONTROL    
Data Type CHAR   Character String 
Length 1    
Decimal Places 0    
Output Length 1    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 RBA Ctrl 
Medium 15 RBA Control 
Long 20 RBA Control 
Heading 3 RBA 
Documentation

Definition

Use

This field is relevant if you run the availability check for items with the same item category using the global availability check in SAP Advanced Planning and Optimization (SAP APO). In this field, you control the rules-based ATP check at item category level. You specify whether SAP APO is allowed to carry out a rules-based ATP check (RBA) for items of this item category, and how the substitutions confirmed by the RBA are processed.

SAP APO is allowed to run an RBA if you choose one of the following options:

  • Subitems Allowed, Plant Substitution in Item Not Allowed (space)

    You use this option if you want to use the classical RBA, which is allowed to create subitems or stock transfers for confirmed product and location substitutions. It is not possible to carry out a plant substitution directly in the item with this classical RBA.

    Whether or not the RBA creates subitems depends on the check instructions, the rules that were found, and the availability situation.

  • Subitems and Plant Substitution in Item Not Allowed (C)

    You use this option if you want to make absolutely sure that the RBA does not create subitems or carry out a plant substitution in the item, regardless of how the RBA is configured in SAP APO. This option is relevant if, for example, you only want to allow stock transfers in the RBA. Product substitution is not possible with this option.

  • Subitems Not Allowed, Plant Substitution in Item Allowed (D)

    You use this option if the RBA is not permitted to create subitems for a plant substitution, but the plant substitution has to take place directly in the item, regardless of how the RBA is configured in SAP APO. Stock transfers and product substitution are not possible with this option.

  • Subitems and Plant Substitution in Item Allowed (E)

    You use this option if you want to allow both RBA variants for the item category; that is the classical RBA, which corresponds to the option Subitems Allowed, Plant Substitution in Item Not Allowed (space), as well as plant substitution in the item, which corresponds to the option Subitems Not Allowed, Plant Substitution in Item Allowed (D).

    Depending on the check instructions, the rules, and the availability situation, the RBA decides whether to substitute the plant in the item, or to create a subitem.

You use option Rules-Based ATP Check Not Allowed (N) if SAP APO is not permitted to run an RBA.

Sales Bills of Materials

For sales bills of materials, only the RBA variant Plant Replacement is available in the item. However, plant replacement in the item is only available for main items with subitems from item category group LUMF that are relevant for requirements, and not for main items with subitems from item category group ERLA. Therefore, only options C, D, and E are relevant for sales bills of materials. You make the settings for the item category of the main item.

Dependencies

For SAP SCM to be able to process values other than Subitems Allowed, Plant Substitution in Item Not Allowed (space), version SAP SCM 7.0 or higher is required. In addition, for SAP SCM 7.0 EHP2 and earlier versions, you must have implemented SAP Note 1832839 (or the corresponding support package).

Example

History
Last changed by/on SAP  20130529 
SAP Release Created in 607