SAP ABAP IMG Activity DRP_VERFUG1 (DRP_VERFUG1)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ PP-SOP-DRP (Application Component) Distribution Requirements Planning
     ⤷ MDRP (Package) Distribution Resource Planning
IMG Activity
ID DRP_VERFUG1  
Transaction Code     (empty) 
Created on 19981222    
Customizing Attributes DRP_VERFUG1    
Customizing Activity DRP_VERFUG1    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name DRP_VERFÜG1    

In this IMG section you define checking groups with which you specify the type of requirements records the system is to create when processing sales orders or deliveries. Sales order requirements and delivery requirements can be controlled separately.

You can create the following requirements records:

  • Individual requirements records

    In individual requirements records, a requirement is created for each SD document. The respective entry in the stock/ requirements overview identifies the order quantity and the document which gave rise to the requirement.

  • Summarized requirements records

    Summarized requirements records group together or update several requirements under certain conditions in the material master record (plant, date, procedure, requirement class). There are two types of summarized requirements records:

    • Summarized requirements records for each day
    • Summarized requirements records for each week

      Monday of the current week or Monday of the following week is regarded as a requirement date.

Availability check taking cumulated confirmed quantity into account

If confirmed quantities are not cumulated, the following problem may occur:

Starting from the delivery date of the sales order and working backwards, the system checks whether ATP quantities exist. If such quantities do exist, the new sales order will reduce these ATP quantities. Here, sales orders can only reduce the ATP quantities if they lie before the delivery date.

In this logic, the system does not take the confirmed quantity of sales orders that have already been created into account. If, in the past, receipts were either moved forward or backward and/or they were reduced, it is possible that the ATP quantity of the receipt that lies directly before a sales order which has already been confirmed is no longer sufficient to cover the requirement.

The following example should clarify this point:

MRP elemt    Recpt/Reqmt    ATP qty    Cumul.ATPqty    Confirmed qty

Stock    100    0    0    -

SALES ORD 1    -200    -100    -100    -200

PLND ORD    100    0    0    -

SALES ORD 2    -100    0    0    100

In this example, the first sales order was completely confirmed when the planned order lay before sales order 1 on the time axis. Then, the planned order was rescheduled out so that it now lies after the delivery date of sales order 1 on the time axis. For the new sales order 2, the ATP check comes up with an ATP quantity of 100 as the rescheduled planned order is now completely available again and according to the ATP logic, sales order 1 cannot be covered by this receipt.

In this particular example, the confirmation situation is no longer up-to-date as the planned order has been rescheduled. Therefore, the sum of all the confirmed quantities exceeds the sum of all receipts.

To solve this problem, you have the following options:

  • carry out the planning run
  • reschedule
  • carry out backorder processing

With the cumulation of quantities, you can avoid such inconsistencies asyou can control exactly how the system is to carry out the check:

  • Availability check taking cumulated confirmed quantity into account

When creating/changing a new sales order, the system includes all the quantities confirmed to date when calculating the cumulated ATP quantity. This means that the new sales orders can only be confirmed if the sum of the receipts exceeds the sum of the confirmed quantities.

  • Availability check taking cumulated requirements quantities into account

When creating/changing a new sales order, the system includes the sum of all open requirements quantities when calculating the cumulated ATP quantity. This means that new sales orders can only be confirmed if the sum of the receipts exceeds the sum of the requirements quantities.

You can make the following settings for this new ATP checking logic when creating/changing a sales order:

  • cumulate the confirmed quantities when creating and changing
  • cumulate the requirements quantity when creating, no cumulation when only making changes
  • cumulate the requirements quantity when creating and cumulate the confirmed quantity when making changes
  • no cumulation (old checking logic)

Determining the checking group

The checking group is determined depending on the material type and plant and is proposed in the material master record. The section "Define the checking group for each material type" describes how to allocate checking group to material type and plant. Together with the checking rule, the checking group determines the scope of the availability check.

Note

For procedures relevant to requirements which lead to special stock (e.g. make-to-order production), the system automatically creates individual requirements records, even if the configuration was set in the material master record or via the checking group for summarized requirements records.

Warning

You can use either summarized requirements or individual requirements for each checking group. Changing the method of summing up requirements results in a change in the information contained in the record. When you change from individual to summarized requirements, you lose the assignment to sales orders, for example.

Actions

  1. Check to what extent you can use the configurations set for the checking groups in the standard version of the SAP System.
  2. Enter the method of summing up for each checking group when creating a sales order document or a delivery.
  3. If necessary, activate the cumulation of confirmed quantities.

Business Attributes
ASAP Roadmap ID 203   Establish Master Data 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG DRP_VERFÜG1 0 HLA0006235 Distribution Requirements Planning 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
V_TMVF V - View SM30 DRP01 Availability Check Control 
History
Last changed by/on SAP  19981222 
SAP Release Created in