Enterprise Resource Planning Blogs by Members
Gain new perspectives and knowledge about enterprise resource planning in blog posts from community members. Share your own comments and ERP insights today!
cancel
Showing results for 
Search instead for 
Did you mean: 
mickaelquesnot
Active Participant

Transfer of Requirements in SAP S/4HANA


https://youtu.be/rFdhdqCGgRg

 

By means of the transfer of requirements, the MRP department is informed about the quantities and deadlines by which incoming orders should be delivered. The system checks the availability of the goods based on the requested delivery date of the customer and creates MRP records which contain all necessary information for passing on to materials planning. The transfer of requirements ensures that the goods are available in time for the delivery. Materials planning transfers the reported requirements and creates production orders or purchase requisitions from them, for example.

The following sections on the transfer of requirements describe how to control the transfer of requirements.

The transfer of requirements is basically dependent upon the following factors:

  • requirements type



  • requirement class



  • check group



Note

The transfer of requirements is controlled globally using the requirements class which is derived from the requirements type for all sales document types. For the sales document types, fine tuning is also possible at schedule line level. This fine tuning is described in the section "Defining the procedure for each schedule line category".

Note that the requirements classes are also used in production so you should coordinate  any changes to the requirements classes with production. The requirements type and, eventually, requirements class are determined in the strategy group so all changes made there should also be coordinated with production.

Requirements transferred to planning are further processed in the module MM. You must, therefore, coordinate the transfer of requirements with the module MM.

Requirements

For controlling transfer of requirements, you have to carry out the following steps:

  1. Each requirement type has to be allocated to one requirement class only.

  2. The transfer of requirements must be switched on at requirements class level, the sales documents at schedule line level.

  3. You must define a check group. It is possible to have this check group proposed for the initial creation of a material master record.

  4. Note that a plantmust exist for transfer of requirements to be carried out at document item level.


Note

Requirements transferred to planning are further processed in the module MM. You must, therefore, coordinate the transfer of requirements with the module MM.

 

 

 

 

 

 

 

Va02

 

 

Md04

 

 

 

 

 

 

Assign Schedule Line Categories


In this menu option, you assign schedule line categories to item categories. This allocation of schedule line categories is carried out depending on the MRP type that is specified in the material master record for a material. At the same time, you can enter a maximum of three schedule line categories with which the system default can be manually overwritten during document processing.

Actions

  1. Assign the schedule line categories to the item categories depending on the MRP type. In this case, indicate the schedule line categories that are to be proposed during document entry.

  2. If necessary, specify schedule line categories with which the automatically determined schedule line category can be overwritten in the document.


 

 

 

 

 

 

 

 

Determine Requirement Type by Item Category and MRP Type


In the standard system, requirements types are determined according to a specific search strategy beginning with the material strategy group.

Strategy for Determining the Requirements Type

  1. First, an attempt is made to find a requirements type using the strategy group in the material master.


 

 

  1. If the strategy group has not been maintained, the system will determine it using the MRP group.


 

 

  1. If the MRP group has not been defined, the system uses the material typeinstead of the MRP group when accessing the corresponding control tables.


 

 

 

  1. If no requirements type is found here, the system assumes a special rule and attempts to find a requirements type with the aid of the item category and the MRP type.


 

 

 

  1. If this is not possible, a last attempt is made to find a requirements type with the item category only.


 

  1. If the last attempt fails, the system declares the transaction as not relevant for the availability check or transfer of requirements.


Note

You can select an alternative search strategy in the 'Source' field, for example a transaction-related procedure for determining requirements type (source = 1 or 2).

Example

There are business transactions, such as consignment stock processing, in which the material with its planning characteristics is not important, rather the transaction itself. An issue from the customer's consignment stock should not trigger an availability check against planning at the plant as layed down by the planning strategy but rather against special stock.

Actions

  1. Assign the item categories and MRP type to the requirements types.

  2. Select an alternative search strategy in the 'Source' field if necessary.


Notes for determining requirements types in releases previous to 3.0

Up to and including Release 2.0, requirements types were determined using the document item category and MRP type of the material in the relevant plant.

As of release 2.1, this specification is carried out identically for Logistics by means of the MRP group of the material which specifies a strategy from which the requirements type is determined.

 

 

 

 

 

 

 

 

Define Strategy Group


In this step, you specify which strategies are to be grouped together into a strategy group. You can determine a main strategy as well as a maximum of seven alternative strategies.

Note

The main strategy is proposed in demand management or sales order management but it can be overwritten by another planning strategy defined in the strategy group, if necessary.

You can assign the strategy group to the material directly in the material master record or you can first assign the strategy group to an MRP group and then in a second step, you can assign the MRP group to the material in the material master record.

Default settings

In the standard SAP system, the strategy groups are preset.

Actions

  1. Check the strategy groups contained in the standard SAP System.

  2. Specify new strategy groups, if necessary.


 

 

 

 

 

Define Strategy


The planning strategy represents a procedure to be used for planning a material.

It is defined by;



  • a combination of both that makes sense


Default settings

The planning strategies are predefined in the standard SAP system.

Recommendation

SAP recommends that you use the standard SAP planning strategies.

Actions

Enter new planning strategies, if necessary.

 

 

 

 

 

 

Assign MRP Group to Strategy Group In this step, you allocate a strategy group to the MRP group.


If an MRP group is maintained for a material, the strategies specified in the strategy group are allowed for this material.

In order to find the correct requirements type in demand management and in sales order management, you have to:

  1. a) allocate the strategy groups to the MRP groups, and

  2. b) allocate the MRP groups to the materials to be planned in the material master record.


or

Enter the strategy group directly in the material master record of the material to be planned

Actions


Maintain the allocation of strategy groups to MRP groups.

 

 

 

 

 

Define Procedure For Each Schedule Line Category


In this IMG step, you specify for the respective schedule line categories of the sales documents whether an availability check and/or transfer of requirements should be carried out. These configurations are only relevant for the sales documents.

The fine tuning of the availability check for sales documents that you carry out here depends on their global configuration at requirements class level: You can only deactivate an option selected at requirements class level, but you cannot activate it. You can only activate an an option if it is already activated at requirements class level.

Example

You want to implement an availability check without transfer of requirements for sales information. At requirements class level, the availability check and the transfer of requirements must be active. You therefore deactivate the transfer of requirements in the corresponding schedule line category.

Requirements

The schedule line categories must already have been defined (see section Defining and allocating schedule line categories). The defined schedule line categories are automatically displayed for maintaining.

Actions

  1. Specify for each schedule line category whether an availability check and/or a transfer of requirements should be carried out.


Keep in mind that the configuration that you set depends on the global configurations at requirements class level.

 

 

 

 

Configure Requirement Types


In this IMG step, you change or define requirements types which identify the different requirements, such as sales order requirements, delivery requirements or individual customer requirements. The requirements types can be changed, for example, in order to represent customer-specific terms.

Together with the item category and the MRP type of the material, an allocation to the individual transactions in sales and distribution is carried out by means of the requirements typerequirements type. Every requirements type is allocated to a requirements class with its corresponding control features.

While a requirements type is allocated to a single requirements class, a requirements class can be allocated to several requirements types. As a result, it is possible to control different transactions in a uniform manner with regard to their technical procedure.

Note

The requirements type is displayed in the sales document and can be changed there.

Actions

  1. Check first whether the requirements types available in the standard version are sufficient for your demands.

  2. If necessary, enter an alphanumeric key for a requirements type, which can have up to four characters, and a description.

  3. Allocate a requirements class to the requirements type.


 

 

 

 

 

 

Configure Requirement Classes


In this menu option, you define and maintain the requirement classes with which you control all functions relevant to requirements in logistics.

The requirement class controls the MRP and the requirements consumption strategy as well as the relevancy for planning. Specifications on the settlement of the requirement class, for example, the settlement profile and the results analysis key, are preferably used by Materials Management and do not have to be used when configuring the availability check and transfer of requirements.

The requirement class specifies the following points:

  • whether an availability check and a transfer of requirements is carried out for a transaction (for sales documents, fine tuning using the schedule line category is possible, see note),



  • whether the requirements are relevant for MRP,




  • whether an item is to be settled to an auxiliary account assignment,



  • the settlement profile,



  • the results analysis key.


Note

The availability check and transfer of requirements are controlled globally using the requirement class for all sales document types. For the sales document types, fine tuning is also possible at schedule line level. The specifications from the requirement class are transferred to the schedule lines as a default value and can be overwritten. Fine tuning of the sales document types using the schedule line category is described in the section "Defining the procedure for each schedule line category".

For information on independent requirements allocation and independent requirements reduction, see the manual "SD Sales". The configurations for independent requirements allocation are described in the Implementation Guide for Production Planning in the chapter "Demand Management".

Actions

  1. Check first whether the requirement classes available in the standard version are sufficient for your demands.

  2. If necessary, enter a new key for the requirement class, which can have up to three characters, and a description.

  3. Specify whether an availability check and/or a transfer of requirements should be carried out for the requirement class. At requirements class level, the availability check can only be activated at the same time as the transfer of requirements. On the other hand, the transfer of requirements can be activated independently of the availability check.

  4. Specify whether a requirement is relevant for MRP.

  5. Specify for the allocation indicator whether a settlement of customer requirements with planned independent requirements should be carried out by allocating a consumption strategy to the requirement class. The allocation indicator corresponds to the settlement indicator which is maintained in planned independent requirements management. Customer requirements can only be settled with planned independent requirements types to which the same consumption strategy was allocated in independent requirements planning.

  6. Specify the indicator for requirements reduction, if necessary.


Notes


You can make the settings for the requirements class which concern costing and account assignment in the following activity: Sales and Distribution -> Basic Functions -> Account Assignment/Costing -> Maintain requirements classes for costing/account assignment.

 

 

 

 

 

 

Configure Availability Check Reaction to Delivery Blocks


Use

When requirements are transferred to MRP, the confirmed quantity is also reserved for confirmed sales documents. If a transaction is blocked for delivery, the required quantity will be blocked to prevent it being used elsewhere. You can use this Customizing activity to block the transfer of requirements.

If set, the requested quantity is still transferred as a requirement but the quantity is not reserved. This is visible in the sales document when no confirmed quantities or subitems (in the case of Alternative-Based Confirmation (CA-ATP-ABC)) are available after saving.

When the delivery block is removed, the system automatically executes an availability check.

Note

You can carry out availability checks at any time, despite the blocks, if the transaction permits. The system then creates temporary schedule lines with confirmed quantities which are then removed when the document is saved. Furthermore, the system creates temporary subitems for ABC which are also removed when the document is saved.

For more information about defining blocking reasons, see Define Blocking Reasons for Shipments.

Prerequisites

Delivery blocks must already be defined in your system. For more information, see Define Blocking Reasons in Sales.

Actions

Check if it is necessary to block the transfer of requirements for blocked order items in your company.

 

 

 

Maintain Requirements For Transfer Of Requirements


In this step you can maintain your own requirements for the transfer of requirements.

The order quantity is always copied as a requirement in planning. With requirements, you can prevent quantity reservations and with them confirmed quantities. You can recognize this after saving a document: confirmed quantities will no longer exist (see initial screen).

Standard settings

In the standard SAP System, requirement 102 prevents reservations from being created in the event of a credit block.

 

 

 

Maintain Requirements For Purchase And Assembly Orders


In this step you can maintain your own requirements for creating purchase requisitions.

Standard settings

In the standard SAP System, requirement 101 prevents purchase requisitions from being created in the event of a credit block.

 

 

 

Result

 

 

 

 

 

 

 

 

Requirements type


The requirements type determines the planning strategy to be used for a particular requirement.

 

 

 

 

Schedule line category


A classification that distinguishes between different kinds of schedule line. The category determines how the system processes the schedule line.

Use


The schedule line category determines, for example, whether the system passes on requirements to materials requirements planning (MRP).

 

 

 

 

 

 

 

 

 

 

Next step > GU_SAP S4 HANA_Availability Check with ATP Logic or Against Planning
Labels in this area