As I see daily on the Manufacturing PP space threads asking for exits or BAdis for specific scenarios, I decided to create this list with the most important user-exits and BAdIs that are available for production and process orders.

Below you can find the main BAdIs for production and process orders and the methods available for each one:

• WORKORDER_UPDATE: This BAdI is called whenever the order is changed, for example, on transaction CO02 or during capacity leveling
  • ARCHIVE_OBJECTS - Archiving Additional Objects
  • AT_DELETION_FROM_DATABASE - Order is deleted from the database (archiving)
  • AT_SAVE Save Order Time: Dialog
  • CMTS_CHECK Check: Configurable Warehouse Order Allowed
  • INITIALIZE Initialization when Importing/Creating Order
  • IN_UPDATE Save Order Time: Update
  • NUMBER_SWITCH Swap Tempory Order Numbers with Final Order Numbers
  • BEFORE_UPDATE Save Order Time: Before Calling Update
  • AT_RELEASE Release Order Time: After SAP Checks, Before Release
  • REORG_STATUS_ACT_CHECK Reorganization of Order: Status Check
  • REORG_STATUS_ACTIVATE Reorganization of Order: Follow-Up Action After Status Set
  • REORG_STATUS_REVOKE Reorganization of Order: Follow-Up Action After Status Reset

• WORKORDER_CONFIRM: This BAdI is called during the order confirmation for additional checks.
  • AT_SAVE - Confirm Order, Time: Dialog
  • BEFORE_UPDATE -Confirm Order, Time: Before Update
  • IN_UPDATE - Confirm Order, Time: Update
  • AT_CANCEL_CHECK - Confirm Order, Time: Check if Cancellation is Possible
  • INDIVIDUAL_CAPACITY - Confirm Order: Preassignment Individual Capacity

• WORKORDER_GOODSMVT: This BAdI can be used to manipulate goods movements that are posted during an order confirmation
  • BACKFLUSH Confirmation: Backflush
  • GOODS_RECEIPT Confirmation: Automatic Goods Receipt
  • MANUAL_GOODS_RECEIPT Manual Goods Receipt for Order
  • IM_CALLED Time after Inventory Management is Called
  • PICKLIST Pick list
  • GM_SCREEN_LINE_CHECK Goods Movement Overview: Line Check
  • GM_SCREEN_OKCODE_CHECK Goods Movement Overview: OK Code Check
  • COGI_AUTHORITY_CHECK Postprocessing: Authorization Check
  • COGI_POST Postprocessing of Incorrect Goods Movements
  • COMPLETE_GOODSMOVEMENT Confirmation: Addition of User Input on Goods Movement
  • GM_WIPBATCH_PROPOSE Goods Movement WIP-Batch: Proposal
  • GM_WIPBATCH_CHECK Goods Movement WIP-Batch: Line Check

• WORKORDER_REWORK: This BAdI is used on a rework scenario, in order to transfer outwards an additional yield when entering a backflush for PP orders. This is added
  • GET_REWORKED_QUANTITY Returns the Reworked Yield

• WORKORDER_INFOSYSTEM: This Business Add-In can be used to fill additional (customer-specific) fields in the order info system (transactions COOIS, COOISPI, COHV...) for production orders and process orders.
  • ORDER_TABLES_MODIFY Processing of order tables
  • PLANNED_ORDER_TABLES_MODIFY Processing of planned order tables
  • AT_SELECTION_SCREEN Is called in the WBS for the PPIO_ENTRY selection screen
  • AT_OUTPUT_SCREEN Is called for every action on the output list
  • OVERVIEW_MODIFY Processing of the object overview
  • TABLES_MODIFY_LAY Processing of Order and Planned Order Tables
  • DETAIL_LIST_LAY Process Detail Lists
  • OVERVIEW_TREE_LAY Process Layout-Based Object Overview
  • AT_OUTPUT_SCREEN_LAY Call When Action is Carried Out on the Output List

Here are the user-exits available for PP order processing:

• PPCO0001
  • EXIT_SAPLCOBT_001 - User Exit PP Order Processing (Non-Order-Type-Specific)

• PPCO0002
  • EXIT_SAPLCORE_001   Set deletion flag
  • EXIT_SAPLCORE_002   Set deletion indicator
  • EXIT_SAPLCORE_003   Technically complete
  • EXIT_SAPLCORO_001   Check exit for function "Set deletion flag"
  • EXIT_SAPLCORO_002   Check exit for function "Set deletion indicator"

• PPCO0003
  • EXIT_SAPLCOEXT_001 - Check Exit for Production Order Change from Assembly Order

• PPCO0004
  • EXIT_SAPLCORE_004 - Mass Processing of Production Orders: General Sort Exit

• PPCO0005
  • EXIT_SAPLCOSD_001 - Storage Location/Backflushing on Order Creation

• PPCO0006
  • EXIT_SAPLCOZF_003 - Exit for Predefining Fields in the Order Header

• PPCO0007
  • EXIT_SAPLCOZV_001 - User Exit for Checking or Changing Header Fields During Order-Type-Specific

• PPCO0008
  • EXIT_SAPLCOMK_006 - Enhancement in the adding and changing of components

• PPCO0009
  • EXIT_SAPLCOSF_001 - Customer Exit: Goods Receipt for Production Order

• PPCO0010
  • EXIT_SAPLCOCOM10_001 - Enhancement in make-to-order production - Unit of measure

• PPCO0012 - Production Order: Display/Change Order Header Data
  • EXIT_SAPLCOKO1_001 - Transfer of Order Data to Customer Enhancement
  • EXIT_SAPLCOKO1_002 - Transfer of Data Changes from Customer Enhancement

• PPCO0013
  • EXIT_SAPLCOMK_008 - Change Priorities for Selection Criteria for Batch Determination

• PPCO0014
  • EXIT_SAPLNWDB_001 - Select process orders for external relationships

• PPCO0015
  • EXIT_SAPLCOSD_002 - Customer Exit: Additional Attributes Document Link

• PPCO0016
  • EXIT_SAPLCODM_001 - User Exit: Generate Document Links from Master Data

• PPCO0017
  • EXIT_SAPLCODD_001 - User Exit: Document Links Dialog Processing

• PPCO0018
  • EXIT_SAPLCOKO1_004 - Check whether changes to order header/item are allowed in th

• PPCO0019
  • EXIT_SAPLCOVG_001 - User Exit for Checks of Operation Changes in the Production

• PPCO0020 - Process order: Display/change order header data
  • EXIT_SAPLCOKO_005 - Transfer of Order Data to Customer Enhancement
  • EXIT_SAPLCOKO_006 - Transfer of Data Changes from Customer Enhancement

• PPCO0021
  • EXIT_SAPLCOZR_003 - Release Control for Automatic Batch Determination: Handling

• PPCO0022
  • EXIT_SAPLCOTX_001 - Determination of Production Memo

• PPCO0023
  • EXIT_SAPLCOMK_014 - Checks Changes to Order Components

User-exits called during the process order confirmation:

• CONF0001  Enhancements in order confirmation
  • EXIT_SAPLCORU_001 - Order Confirmation: Deactivation of Functions

• CONFPI01
  • EXIT_SAPLCORF_401 - Process order conf.: Calculate cust.specific default values

• CONFPI02
  • EXIT_SAPLCORF_402 - Process Order Confirmation: Customer-Specific Input Check Wi

• CONFPI03 
  • EXIT_SAPLCORF_403 - Process Order Conf.: Customer-Specific Checks after Operation

• CONFPI04 
  • EXIT_SAPLCORF_404 - Process Order Confirmation: Customer-Specific Input Checks

• CONFPI05
  • EXIT_SAPLCORF_405 - Process order conf.: Cust. spec. enhancements when saving

• CONFPI06
  • EXIT_SAPLCORF_406 - Process order confirmation: Actual data transfer

User-exits called during the process order confirmation:

• CONFPP01
  • EXIT_SAPLCORF_101 - PP order conf.: Determine customer specific default values

• CONFPP02 
  • EXIT_SAPLCORF_102 - PP order conf.: Customer specific input checks 1

• CONFPP03 
  • EXIT_SAPLCORF_103 - PP order conf.: Cust. specific check after op. selection

• CONFPP04 
  • EXIT_SAPLCORF_104 - PP order conf.: Customer specific input checks 2

• CONFPP05 
  • EXIT_SAPLCORF_105 - PP order conf.: Customer specific enhancements when saving

• CONFPP06 
  • EXIT_SAPLCORF_106 - PP Order Confirmations: Actual Data Transfer

• CONFPP07 - Single Screen Entry: Inclusion of User-Defined Subscreen
  • EXIT_SAPLCORU_S_100 - Transfer Data from SAPLCORU_S to Customer-Defined Screen
  • EXIT_SAPLCORU_S_101 - Return Data from Customer-Defined Screen to SAPLCORU_S

You wonder why a field is filled automatically by the system.  How to make it happen?  Here are some general settings:

1. In the screen level

Firstly find which screen the field belongs to.  Take the field 'process order' in t-code COR6 for example.

Click F1 help on the field. Then click button 'Technical details'.  You will find the screen number and field name on the popup.

In t-code SE51, check the field attributes.  There is a field 'parameter ID' and 2 indicators 'SET parameter' and 'GET parameter'.  They control whether the field can store the field content to an internal parameter or get the content from the parameter.

If you go to t-code COR3 and check the same.  On Screen 5110 of program SAPLCOKO, the field 'process order' also refers to the same parameter ID.

Therefore, if the indicators 'SET parameter' and 'GET parameter' are set for field CORUF-AUFNR, after you dispaly a process order in COR3, then navigate to COR6, the process order number will be shown automatically.

2. In program level

Sometimes the system can set or get a parameter id by coding directly.  It usually occurs in a PBO module.  You can set a breakpoint at 'GET parameter'.

3. In customizing

For some transactions you may be able to control it by customizing settings.  As an example you can check the KBA 2031843.

2031843 - Fields 'Material' 'Plant' and 'Group' are proposed automatically from previous input in transaction code CA01/CA02/CA03

An alternative item group is used to group together alternative items in a BOM. Any of the materials in the alternative item group could be included in the assembly. These items are known as alternative items in the BOM.

You can use alternative items in the following situations:

• Alternative items with a usage probability

    The alternative items are included with a certain usage probability. 

• Material requirements planning (MRP) uses the usage probability to determine dependent requirements for the materials.
• In the production order, dependent requirements are converted to a reservation.

  · The withdrawal posting for the reservation in the production order uses either the usage probability or the 100% availability check according to ATP logic. 

• Alternative items for information: You can enter an alternative item for information only. For example, the item is only relevant to missing parts. The usage probability for the item is 0 .

Please follow the below URL to have a depth insight to this concept.

http://https://help.sap.com/saphelp_470/helpdata/en/ea/e9b3c44c7211d189520000e829fbbd/content.htm

I am going to describe two scenarios with this alternate item group concept in BOM.

Plant - 1000

Finished goods – ALTFERT

Raw material – G1 and G2.

Order type – PP01

Go to Order type control and set the configuration as User can’t release the Order if there are any missing parts. Please see the below screen shots( Tr code OPJK ) :

Case 1: If the requirement is either we may consume G1 or G2 100 % to manufacture ALTFERT based on the stock.

Create a Fert and 2 raw materials in 1000 plant. Create a BOM and Routing in the pant.

For Bom follow the settings:

Then do the settings for Alt group as shown:

Double click on the item no 0010 and then input the alternate group as “A1” and select the arrow.

A new pop up will open as shown below, and then input the parameters as shown.

Double click on the item no 0020 and then input the alternate group as “A1” and select the arrow.

A new pop up will open as shown below, and then input the parameters as shown.

That means for manufacturing 1 qty of ALTFERT we require either G1 or G2 ( any of them ) of 2 qty.

Save the BOM.

Do some stock posting for raw material G1 only (maintain stock for G1 only not for G2.)

Then create Prod. Plan by MD61 and run the mrp.

SAP will create planned orders for the dependent materials.

Then convert the planned order to production order. As one of the material G1 is available so the production order will be release although the availability check is maintained that without mat available no release.

Then Release the Production Order:

Then check the Components list, you can see G1 reqmt showing is 20 and G2 reqmt automatically changed to zero.

CASE 2: If the requirement is to consume G1 or G2 by 80 % and 20% as available in stock to manufacture ALTFERT for its base qty.

Maintain the BOM:

Maintain the total reqmt qty same for both the raw materials.

Then maintain the Alt BOM  Group for G1 :

Then maintain the Alt BOM Group for G2 :

Then create Routing.

Then create PIR for 10 qty and save it. Then run mrp. A planned order for 10qty will be shown in md04 for the Finished Good.

Then automatically SAP will create the planned orders for both.

G1 = 20 * 80/100 = 16

G2 = 20* 20/100 = 4

Check in MD04.

Then convert the planned order to prod order and release it. You can check the Components list it’s changed as per the settings in Alt Bom Group.

Then follow the Standard SAP PP Flow and close the Production Order.

Thanks

Subhrant

Very frequently, problems are observed when deleting a work center on transactions such as CR02, CRC2 or IR02.

The work center can be deleted directly on the mentioned transactions if we choose the menu 'Work center' - 'Delete' or it can be archived using the archiving object PP_WKC (Archiving Work Centers (PP-BD-WKC) - Production Planning and Control (PP) - SAP Library)

However, very frequently a TIME OUT short dump happens when you try to delete the work center directly on the transaction .

The TIME_OUT dump usually occurs when the tables where the work center is being used are huge. That's because, during the work center deletion, system must perform a where-used selection, to find on which tables the work center is being referred. This procedure is necessary in order to prevent database inconsistencies, that means, avoid the deletion of a work center that is still being used on another table or transactions.

For example, if the work center was used on a production and if you delete this work center, you would probably observe a short dump or an inconsistency when trying to open this work center.

Therefore, system must confirm that the work center is nor referenced on the following tables, before the deletion:

• PLKO - Task list - header
• AFRU - Order completion confirmations
• EQUZ - Equipment time segment
• IFLO - Functional Location (View)
• AFIH - Maintenance order header
• ILOA - PM Object Location and Account Assignment
• QMEL - Quality Notification

When there is a lot of data on these tables, the performance of this where-used selection is very bad and the work center cannot be deleted.

In this case, the archiving of unnecessary PM orders and Production orders to reduce the size of those tables is extremely recommended. This procedure will reduce the number of entries in the tables and it should avoid the TIME OUT.

In addition, there may be no suitable access path for the select statement on the tables, such as AFRU. This would not normally be an issue if the size of the order tables were not out of hand.  However, with the large amounts of data in these tables, the unsuitable access path really is a significant issue.  A new table INDEX with the field ARBID can be used, but this is considered as a MODIFICATION. Normally, SAP suggests a MAXIMUM of five indexes for a given table. This minimizes the required tablespace and minimizes the time needed by the Cost Based Optimizer to evaluate the possible access paths.

It is possible, however, to temporarily create the ARBID index, until the size of the order tables can be reduced sufficiently to allow

proper access to these tables or until the deletion of the desired work centers. After that, the index can be removed from the table.

Note 415031 provides more details about this specific issue and the mentioned index.

Another very frequent issue is the error message 'CR002 -  Work center XXXXXXXX in plant XXXX is still being used'.

This error message happens when the work center is still being referenced in one of the mentioned tables and the deletion will not be allowed while such reference still exists.

A quick way to identify where the work center is being referenced is to run transaction CR40 with all the flags checked.

Transaction CR40 will show exactly on which documents the work center is being used and you can proceed with a clean up of these documents.

Only when there is no usage for this work center on transaction CR40 you should be able to delete the work center.

In order to clear the references for this work center, we can replace it on routings and task lists and we should archive existing orders where this work center was used, with a proper archiving object (e.g. archiving object PP_ORDER for production orders).

If RF ID has scanned wrong Serial number for a FG material, then the procedure to replace it with new serial number is as below

Steps

1) Change the production order using CO02 transaction.

2) Click on header and Select Serial numbers.

3) Replace the Serial Number XXXX117571059with new serial number XXXX12073

Click on OK and Press Save

4) Execute the IB52 transaction. Give the Ibase number 1205105 and press Enter

5) Replace the Serial Number XXXX117571059 with new serial number XXXX12073 and Press Save

Note: If you want to confirm the production order with new serial number withoutchanging the serial number of components that are already backflushed

Please do the below steps before confirming the production order.

Execute the IB52 Transaction, give the Ibase number  and press Enter.

  Click on the FG material

Click on activate icon twice to deactivate and activate it

Also, click on the Component

Click on Activate icon twice to deactivate and activate it. Click on Save and IBase is changed successfully.

All the GI components are assigned to the new serial number from old Serial number database

SAP strategy for the digital economy is based on the concept of simplification. The SAP strategy is to accelerate business innovation through radical simplification.

This concept was also used on the new SAP S/4HANA, on-premise edition 1511 and several application scenarios available on the ECC were simplified. The idea is to make the S/4 HANA implementation faster and easier, in order to accelerate the return on investment and also make the life of the consultants easier.

A complete list of the simplified scenarios is available on SAP Help and it is available on the following link:

http://uacp.hana.ondemand.com/http.svc/rc/PRODUCTION/pdfa4322f56824ae221e10000000a4450e5/1511%20000/en-US/SIMPL_OP1511.p…

Between those scenarios, some are specific to Material Requirements Planning and changes were made on functionalities that were part of the standard system for a long time.

Some of the most relevant changes are the following:

1 - Simplified sourcing

The source determination carried out by MRP was completely redesigned for internal and external procurement.

For internal procurement, a BOM selection method is no longer available for selection. Now, the BOM is always selected according to the production version, therefore, it is mandatory to have a production version.

For external procurement, the source list is no longer relevant to MRP and it is enough to have a valid info record, in order to have a vendor selected for a planned order or purchase requisition by MRP.

With these changes, the source determination on MRP is similar to the source determination on APO and, according to SAP, unified source of supply model is the basis for future innovations in sourcing.

2 - Storage location planning

The default option to plan a storage location separately is the storage location MRP area. It means that the option to define on the material master that a storage location will be planned separately or excluded from MRP is no longer available.

With the storage location MRP area, there is a separate planning file entry, which means that the MRP area is planned independently. This is a good thing from a performance point of view, since we don't need to plan the entire material just because a change happened on the storage location planned separately.

Besides that, the storage location planned separately runs a very simple reorder point MRP type, while the MRP are offers almost the same settings available on the material master.

3 - Subcontracting

Planning of components provided to the vendor must be now carried out with MRP areas. A separate stock segment for the vendor is not available anymore and the main reason is the performance. It is also now easier to use subcontracting MRP areas, since we simply need to create them on customizing and they will be available for all the materials.

4 - Planning file

The old planning file entry tables were replaced by the new table PPH_DBVM, with simplified update logic, consistency and for update performance.

There is also a new report and transactions to create and check the consistency of the planning file.

SAP strategy for the digital economy is based on the concept of simplification. The SAP strategy is to accelerate business innovation through radical simplification.

This concept was also used on the new SAP S/4HANA, on-premise edition 1511 and several application scenarios available on the ECC were simplified. The idea is to make the S/4 HANA implementation faster and easier, in order to accelerate the return on investment and also make the life of the consultants easier.

A complete list of the simplified scenarios is available on SAP Help and it is available on the following link:

http://uacp.hana.ondemand.com/http.svc/rc/PRODUCTION/pdfa4322f56824ae221e10000000a4450e5/1511%20000/en-US/SIMPL_OP1511.p…

Between those scenarios, some are specific to Material Requirements Planning and changes were made on functionalities that were part of the standard system for a long time.

Some of the most relevant changes are the following:

1 - Simplified sourcing

The source determination carried out by MRP was completely redesigned for internal and external procurement.

For internal procurement, a BOM selection method is no longer available for selection. Now, the BOM is always selected according to the production version, therefore, it is mandatory to have a production version.

For external procurement, the source list is no longer relevant to MRP and it is enough to have a valid info record, in order to have a vendor selected for a planned order or purchase requisition by MRP.

With these changes, the source determination on MRP is similar to the source determination on APO and, according to SAP, unified source of supply model is the basis for future innovations in sourcing.

2 - Storage location planning

The default option to plan a storage location separately is the storage location MRP area. It means that the option to define on the material master that a storage location will be planned separately or excluded from MRP is no longer available.

With the storage location MRP area, there is a separate planning file entry, which means that the MRP area is planned independently. This is a good thing from a performance point of view, since we don't need to plan the entire material just because a change happened on the storage location planned separately.

Besides that, the storage location planned separately runs a very simple reorder point MRP type, while the MRP are offers almost the same settings available on the material master.

3 - Subcontracting

Planning of components provided to the vendor must be now carried out with MRP areas. A separate stock segment for the vendor is not available anymore and the main reason is the performance. It is also now easier to use subcontracting MRP areas, since we simply need to create them on customizing and they will be available for all the materials.

4 - Planning file

The old planning file entry tables were replaced by the new table PPH_DBVM, with simplified update logic, consistency and for update performance.

There is also a new report and transactions to create and check the consistency of the planning file.

In the older ERP releases, the automatic goods receipt for co-products was not possible for production or process orders. It means that the goods receipt of an order with co-products should be posted manually, which used to generate more manual work and time spent during a confirmation, since an additional transaction should be executed.

However, as of SAP Enhancement Package 6, the automatic goods receipt of a co-product is possible for production and process orders. This functionality must be activated with the business function LOG_PP_CI_1 - Improvements in Manufacturing and it can be very easily implemented. You can find more details about this business function in the following link of SAP Help:

Improvements in Manufacturing - Logistics - SAP Library

After the activation of the business function, the goods receipt of the co-product can be automatically proposed during the order confirmation on transactions such as CO11N (production orders) or COR6N (process orders).

We also need to define in customizing for which order types the goods receipt of a co-product will be proposed when posting a confirmation on the order type confirmation parameters customizing (transaction OPK4N).

The problem is that the the goods receipt quantity is not proposed during the confirmation for the finished product and for the co-product, as we can see on the picture below:

The system behavior, however, can be changed, as of the implementation of the following note:

2201192 - Automatic goods receipt for co-products: Quantity proposal

After the implementation of this note, we can control if the quantity will be proposed or note using the settings for the message type C6 042. The note long text provides the following explanation about the system behavior after implementations of the code corrections:

To activate the quantity proposal, you must define the message type of the new message C6 042 in Customizing ("Define Attributes of System Messages"). To do so, use transaction OPJB or transaction O04C. If no entry exists in the system for the message C6 042, choose "New Entries" and add a new entry with version 00000000 (eight zeros), application area C2, and message number 042. You can set the message category in the "Cat" field. If you set the option "No message" here, the system proposes the quantities for the goods receipt of the co-products proportionally to the goods receipt quantity of the header material. If you set the message category to "W" (warning) or "E" (error message), the system proposes the quantities in accordance with the system design (no quantities for production orders, same quantities for process orders).

If we want to have the co-product goods receipt quantity proposed according to the header material quantity, the settings for the message type should look like the following picture:

After making this change for the message type, the quantity will be proposed by the confirmation, as we can see below:

I encountered several cases that components are assigned to the wrong operation (usually the first operation) eg. 0010 when creating a production order/process order although the component is assigned to another operation eg. 0030 in routing or master recipe.

I summarize all of the cases I encountered and hope they can be helpful if you got the same problem:

Case 1. Components of phantom assemblies are involved.

Have a look at the note 156366. The field PLMZ-KANTE and PLMZ-STLNR_W might be filled incorrectly if your system is upgraded or migrated from an old release like 3.1H. Let me take a small example which shows how the 2 fields are filled.

BOM structure:

                          PP_FERT

                                 |

      PP_HALB                              PP_HALB_PHAN  (phantom assembly)

                                                                  |

                                        PP_RAW1              PP_RAW2

Component allocation in CA02:

Result in table PLMZ:

If you have similar BOMs as in my example and find the field PLMZ-KANTE is empty, you can refer to the note 156366. If you only have one routing with this problem, you can try to delete the component allocations in CA02 and assign them again. The field PLMZ-KANTE should be filled correctly by deletion and reassignment. If you have too many routings with this problem, the report ZBKANTE in note 156366 can be used to correct them.

Case 2. Alternative items are involved

Alternative items in the BOM should be always assigned to the same operation in the routing. Otherwise, you may get wrong component allocation results when creating a order. KBA 2086778 explains it in more details.

Case 3. If multiple BOM alternatives have been maintained and one of the BOM alternatives is named as 'M'

Check if Note 2283128 is implemented on your system. This note corrects a system bug in this case.

Other cases.

Firstly make sure the right routing is selected. You may have defined many routing group counters for the same material. They could have the wrong component allocation.

Secondly try to delete the component allocations and reassign them if it's possible.

Thirdly check if there really is an entry in table PLMZ for the corresponding BOM item. The table relationship is described in this document:

When deletion indicator is set in routing tables PLPO/PLAS/PLFL/PLMZ

At last if components are still assigned to the wrong operations, contact SAP Product Support by reporting an incident in component PP-SFC-PLN-CPT or PP-BD-RTG.

SAP Labs Latin America is located in São Leopoldo, a city in the south of Brazil. In April 1st, this SAP Labs hosted the SAP Inside Track 2016, an event with more than 100 SAP customers, partners, employees and IT professionals. We had more than 15 presentations and the hot topic was S/4 HANA.

]

On this event, I had the chance to talk about the Simplified Scenarios for Materials Planning on S/4 HANA. I had already talked about this subject on my bloghttps://scn.sap.com/community/erp/manufacturing-pp/blog/2016/03/18/mrp-simplification-on-s4-hana and now I'm writing this blog to share the slides of this presentation for those who could not join the event.

Slide 1: Cover.

Slide 2: Simplified sourcing for external procurement - Source determination on previous releases.

Slide 3: Simplified sourcing for external procurement - Source determination on S/4 HANA based on the Info Record.

Slide 4: Simplified sourcing for external procurement - Sequence for MRP source determination on S/4 HANA.

Slide 5: Simplified sourcing for internal procurement - BOM selection method used on previous releases.

Slide 6: Simplified sourcing for internal procurement - Production version is mandatory for BOM explosion on S/4 HANA.

Slide 7: Simplified sourcing for internal procurement.

Slide 8: Subcontracting - Separate stock segment for subcontracting on previous releases

Slide 9: Subcontracting - On S/4 HANA, subcontracting requirements are only possible on MRP area or at plant level.

Slide 10: Storage location planning - Separate stock segment on previous releases.

Slide 11: Storage location planning - Report MRP_AREA_STORAGE_LOC_MIGRATION

Slide 12: Planning file - New table PPH_DBVM and transaction PPH_DBVM.

Slide 13: E-book "Running MRP on SAP HANA".

Slide 14: Closing.

SAP strategy for the digital economy is based on the concept of simplification. The SAP strategy is to accelerate business innovation through radical simplification.

This concept was also used on the new SAP S/4HANA, on-premise edition 1511 and several application scenarios available on the ECC were simplified. The idea is to make the S/4 HANA implementation faster and easier, in order to accelerate the return on investment and also make the life of the consultants easier.

A complete list of the simplified scenarios is available on SAP Help and it is available on the following link:

http://uacp.hana.ondemand.com/http.svc/rc/PRODUCTION/pdfa4322f56824ae221e10000000a4450e5/1511%20000/en-US/SIMPL_OP1511.p…

Between those scenarios, some are specific to Material Requirements Planning and changes were made on functionalities that were part of the standard system for a long time.

Some of the most relevant changes are the following:

1 - Simplified sourcing

The source determination carried out by MRP was completely redesigned for internal and external procurement.

For internal procurement, a BOM selection method is no longer available for selection. Now, the BOM is always selected according to the production version, therefore, it is mandatory to have a production version.

For external procurement, the source list is no longer relevant to MRP and it is enough to have a valid info record, in order to have a vendor selected for a planned order or purchase requisition by MRP.

With these changes, the source determination on MRP is similar to the source determination on APO and, according to SAP, unified source of supply model is the basis for future innovations in sourcing.

2 - Storage location planning

The default option to plan a storage location separately is the storage location MRP area. It means that the option to define on the material master that a storage location will be planned separately or excluded from MRP is no longer available.

With the storage location MRP area, there is a separate planning file entry, which means that the MRP area is planned independently. This is a good thing from a performance point of view, since we don't need to plan the entire material just because a change happened on the storage location planned separately.

Besides that, the storage location planned separately runs a very simple reorder point MRP type, while the MRP are offers almost the same settings available on the material master.

3 - Subcontracting

Planning of components provided to the vendor must be now carried out with MRP areas. A separate stock segment for the vendor is not available anymore and the main reason is the performance. It is also now easier to use subcontracting MRP areas, since we simply need to create them on customizing and they will be available for all the materials.

4 - Planning file

The old planning file entry tables were replaced by the new table PPH_DBVM, with simplified update logic, consistency and for update performance.

There is also a new report and transactions to create and check the consistency of the planning file.

Dear All

1) Stock determination enables you to implement various strategies to withdraw materials for goods issues and stock transfers. You configure these strategies in Customizing. Based on the material requirements entered, the system determines how and when the material should be withdrawn, and from which storage locations and stocks.

Based on the stock determination strategy you predefine, the system makes decisions on material withdrawal depending on the material, plant, and the business process.

You can use stock determination for the following stocks.

2) Batch Determination & issue of Goods can also be done based on Batch Charecterstics define in the Components batch Classification.

But My concern is, in the Process & Production order when we are using the Batch Determination Using Batch Charecterstics. Maximum 10 batch are showing in the system but ( But in inventory we have 100 batch or more).

& second thing is that, we dont have any user exit in that place, i.e. at the time of batch Determination.

My reconmandation is that sap can provided an User Exit in Process & production Order at Batch Determination Level.

That Exit will halp us to customised the Batch Determination Level as per Customer Requirement,s

Kindly give suggestion if any things are avaliable Presently in the system.

Thanks & Regards

Santosh Patil

In previous releases, once you create a plant, you have to activate MRP for this plant via customizing path: IMG -> Production -> MRP -> Planning File Entries -> Activate MRP and Set Up Planning File or transaction code OMDU.

However, in S/4 HANA, this customizing path does not exist any more.

For S/4 HANA it is decided that all plants are by default relevant for MRP. Technically this means that T001W-BEDPL='X' is always set for each plant. For S/4 HANA Cloud, it is set from SAP. For S/4 HANA On Premise, please use the workaround to set relevant flags in t-code OMDU currently.

Also, you can see the customizing path Convert Planning File Entries for MRP Areas does not exist in S/4 HANA either. In S/4 HANA, the report RMDBVM00, RMDBVM10(for conversion MDVM/MDVL into DBVM/DBVL and back) is not available any more.

Do you have any other question about the MRP related customizing? Let's figure it out together one by one.

As of December 21st 2016, my first SAP Press e-book about MRP on HANA is published and available for download on SAP Press website: Running SAP MRP on SAP HANA | E-Book - by SAP PRESS

Since the first optimizations for MRP on HANA were launched, I have been working to help SAP Customers to resolve issues related to the MRP on HANA implementation and I have been also writing several documents and blog posts on SCN, in order to share useful information about this topic with the SCN community. Below you can find some of the blogs that I have already written about this topic:

MRP on HANA: What's new?

Is your system prepared to take advantage of MRP on HANA?

Issues related to MRP on HANA

MRP: Simplification on S/4 HANA | SCN

So what is new on this e-book? This is a complete implementation guide for MRP on HANA, which starts with the business function LOG_PPH_MDPSX_READ, explains the pre-requisites for the implementation, explains in detail the implementation on the ERP releases, provides an overview of the new MRP Live, helps you to optimize your master date to get a better performance, describes in detail the implementation and the simplified scenarios on S/4 HANA and provides an overview of the MRP Fiori APP, also known as the MRP Cockpit.

You can use it during a brand new implementation, on an upgrade or simply when activating MRP on HANA on a live system. The e-book contains 81 pages, with the following chapters:

1. Why MRP on SAP HANA?
2. Activation and Prerequisites
3. Classic MRP transactions
4. MRP Live
5. MRP in SAP S/4 HANA
6. SAP Fiori Apps for MRP

With the help of this book you will have a smooth transition to MRP on HANA, being able to achieve the optimal MRP Live performance and using the MRP Fiori Apps to change the way your business run.

If you still have doubts about the real benefits of MRP on HANA, check this video where on of the first SAP customers to run MRP Live explains the gain on performance that they got with MRP Live:

When a planned order is created by MRP, the basic dates are calculated according to the in-house production time defined on the material master. Additionally, MRP can read and explode the routing to calculate the operation dates. The planned order production dates can be then calculated according to the operation dates and the basic dates can be even adjusted to match the production dates, depending on the customizing settings.

The production dates calculated with the routing data are more accurate than the basic dates, however, this is a complex calculation and, depending on the number of operations defined on the routing, can lead to performance issues and a long MRP execution. The performance is even worse when lead time scheduling is used in combination with planning mode 2 or 3, since the routing of each planned order of each material will be read and scheduling will be carried out again.

The question here is:

Do we really need such accurate dates for a planned order?

Maybe an even better question is:

Is it worth to have a longer MRP execution to have the production dates calculated?

Considering that the planned order is merely a planning element and that it will generally be later converted to production or process orders (unless we are using repetitive manufacturing), it is usually only a big advantage to have the operation dates calculated for a planned order in the following scenarios:

1. Capacity leveling is executed for planned orders;
2. Variant configuration is used and there are dependencies on the routing, which may affect the results of lead time scheduling;
3. Repetitive manufacturing is used with a rate routing/reporting point;

If these scenarios are not used, then we can simply run MRP without lead time scheduling and use the planned order basic dates only, in order to improve the MRP run performance. After the conversion to production or process order, the routing will be exploded and the operation dates will be calculated.

What about the accurate planned order dates calculated with lead time scheduling?

On the material master tab Work Scheduling we have the option to inform the lot size dependent in-house production time, which means that the planned order basic dates will be calculated according to the planned order size.

In addition, transaction CA97N can be used to calculate the in-house production time according to the routing and update this information directly on the material master. It means that the planned order basic dates will as accurate as the basic dates calculated with lead time scheduling.

I need lead time scheduling because I'm running capacity leveling for planned orders!

Ok, in this case lead time scheduling is really necessary. However, capacity leveling is generally carried out on the short term horizon. If this is the case, perhaps you convert planned orders to production or process orders earlier, in order to run capacity leveling only with production/process orders.

That way, you don't need to run lead-time scheduling during the MRP run and the performance can be improved.

If you still decide that it is necessary to run capacity planning with planned orders, on the customizing transaction OPU5 it is possible to define an horizon for detailed scheduling. This horizon should be no longer than the capacity planning horizon. That means, you don't need to run detailed scheduling for a planned order that is 6 months in the future, if you only run capacity leveling for one month in the future.

Where can I find more information about the system behavior?

On the following notes you can find more information about the functionalities mentioned on this blog, such as MRP performance, lead time scheduling and planning mode:

As was discussed in another one of my blog posts, I deem it extremely important that the planning horizons are respected and specific activities are carried out in specific zones. Along those lines I'd like to refer to the mid-term planning horizon where one can execute stimulative MRP. SAP calls the simulative planning module LTP (Long Term Planning, which is a bit confusing as I would only use it for mid term planning).

With SAP-ERP's LTP you can create planning scenarios and attach different versions of a demand program to it. That way you're holding true to still only managing demand in the mid-term and once you find a fitting demand program, you can release it into operative MRP.

To plan these different versions of a demand program or forecast, a simulative MRP Run (the LTP Run with transaction MD02) is carried out and the result can be evaluated and planned in transaction MFS0. You probably never heard about about transaction MFS0 as it is hard to find any mention of it. But it is the mirror transaction to MF50 in operative MRP.

MF50 is often misunderstood and most people think it can only be used in conjunction with repetitive manufacturing. Nothing could be further away from the truth. MF50 is a tabular planning table, perfectly suited to balance supply with demand for any period you choose to look at. It can do so for detailed planning, rate-based planning (which makes it perfect to deal with in the mid term) and even sequencing. Additionally, there is a graphical planning screen available too (like in CM25)

As you are simulating in SAP-LTP you will find that everything is attached to a planning scenario (that's why you will find that object in MS04, MS07 (mirror transactions to MD04 and MD07) and many other LTP transactions. And when you look to plan as in MF50, the planning scenario with its associated demand version, it can be done with transaction MFS0.

Give it a try and have a look... MFS0 is the perfect planning transaction for rate-based, mid-term planning... but only if you use it in the context of an overall system of planning with planning horizons.

The topic of MTS versus MTO comes up often and people have their own opinions about the definition, but it's actually a very straight forward thing... isn't it? Let's review.

The definition that makes most sense to me goes as the following:

In a Make To Stock environment production is triggered BEFORE an actual sales order comes in and any receipt from the production line is put into inventory from where customer orders are fulfilled.

unfortunately, this does not make everything clear and concise. What if I get a customer order three months before I have to deliver to it? In that case you can enter the SO and it will show up in (SAP transaction) MD04. But we're still not producing to it when we're operating in MTS. It simply reduces the forecast that we produce to and gives us additional information about what we'll actually have to deliver, but it does not trigger production.

What if I get a large order today and do not have enough inventory to fulfill it? you'll have to wait until the next period produces enough product and tell the customer to wait. Because... what is produced this period is for customer orders requesting product in the next period. This is an important point to make... look at the following example:

In the graphical display of MD04 we can see that there is a forecast for the next five months. We can also see that the MRP Run has created orders to fulfill those forecasts. Note that MRP generates orders with their latest possible delivery date standing just before the forecast is due (it does assume unlimited capacity).

As we all know there is a another step necessary before we can start producing: the orders (standing all on top of each other at the latest delivery date) will have to be sequenced, leveled and scheduled into the previous period, so that we can build up inventory for next months' fulfillment of sales orders

This situation becomes visible in the next graphic. Orders were distributed and scheduled (according to the capacity situation) for the next two months. What is not displayed here is how the inventory is consumed by incoming sales orders. that is because we're looking into the future here and the system doesn't know how the sales orders come in (if you had sales orders in the system for the second months, it actually would be displayed by a red bar going down and the green line (inventory) going down as well)

Now what's really important here is that when all inventory forecasted for a period is exhausted and an additional sales order comes in (over and above what was forecasted), that sales order can only be fulfilled by safety stock or the customer will have to wait until the next period.

Do not change the production schedule to fulfill the order if the order is part of a Make To Stock strategy !

and this is where many processes and setups fail. A sales order for an MTS part triggers changes in the production schedule and the whole plan falls apart. Set a strategy periodically, know it and stick with it!

I have already seen many threads on this space asking for books to study production planning, therefore, I have decided to share here the books that I consider more relevant on this area.

Starting with the SAP Press "official" books, we can find some intersting topics abou production planning.

If you are just starting to learn production planning and you would like to learn a little bit about process before a deep dive into the technical aspects, a good book to start is The Goal. It is and easy reading book, as it is written as a novel and it provides an overview about the theory of constraints.

Another book that provides an overview of production planning and that may be interesting for someone starting on this area is Fundamentals of Production Planning and Control - Stephen N. Chapman.

A classic book about production planning is Toyota Production System, written by Taiichi Ohno. He is nothing else than the inventor of the Toyota Production System and Lean manufacturing.

You can also find several suggestions of books about this topic on the link Production Planning.com - Latest in Production Planning and Scheduling.

Now considering SAP Press official books, Uwe Goehring, who is a regular contributor of the SAP ERP Manufacturing - Production Planning (SAP PP) space recently wrote the book Materials Planning with SAP. von Uwe Goehring - by SAP PRESS, which provides an overview of Materials Planning on the ERP system. I did not read the book yet, but considering the quality of the content published bu Uwe on SCN, I'm quite sure that it is worth the price.

The SAP Press e-bite Running SAP MRP on SAP HANA | How-To Guide - by SAP PRESS also covers the new MRP topics, such as MRP on HANA, MRP Live, simplified MRP scenarios on S/4 HANA and Fiori Apps.

Another interesting book about PP is Production Planning and Control with SAP ERP. von Jaw - by SAP PRESS. It is more focused on production control and provides an overview about discrete, repetitive and process manufacturing types on the SAP ECC.

SAP Press also publshed the e-book Configuring Kanban in SAP ERP MM and PP - SAP PRESS, which is more specific about the Kanban functionality.

Uwe Goehring also suggested the book Factory Physics: Wallace J. Hopp, Mark L. Spearman and below you can find his testimonial about this book:

'It's a text book and very scientific (not really light reading) and I had to try very hard to keep on reading. But it is very, very useful and provides a solid understanding about the dynamics of manufacturing systems. I consider this understanding absolute necessary  for any consultant who wants to help their customers to make more use of SAP's production scheduling module and generally supply chain management. A good way to get into the inner workings of Factory Physics is through the lighter version written by Ed Pound: Factory Physics for Managers"

At last, there are the official SAP trainings, and the related documentation. Take a look on the following links for more details:

SCM130 - SAP ERP Planning & Manufacturing Overview

SCM240 - Production Planning in ERP

SCM310 - Production Orders in ERP

TSCM40 - Planning/Manufacturing I

TSCM42 - Planning/Manufacturing II

If you know any other interesting book about this topic, please share it on the comments and I'll add to the list.

As I have explained on my previous blog MRP on HANA: What's new?, as of SAP Enhancement Package 7 for SAP ERP 6.0, MRP was completely redesigned to take full advantage of the SAP HANA architecture.

Now there is a new MRP mode called MRP Live, which is executed on a different transaction and that can be much faster than the classic MRP. The new MRP Live is fully executed on HANA and, since it was built from the scratch, there are some scenarios that are still not covered by MRP Live. A complete list of these scenarios can be found on note 1914010.

As explained on my blog MRP on HANA: What's new?, when MRP Live is executed and system finds one of these restrictions, it will automatically change to the classic MRP, where the database reading was optimized to be executed on HANA, but further processing is carried out on the old ABAP logic.

It means that all the materials can be planned on MD01N, even though they cannot be totally planned on HANA. However, in order to achieve the optimal performance on the MRP Live, we must try to avoid those restrictions, so that we can plan as many materials as possible directly on HANA.

In order to help you to estimate how many materials can be planned by MRP Live and exactly which restrictions do you have on your system, SAP delivered note 1975704, which contains report PPH_CHECK_MRP_ON_HANA.

This note is valid as of release 600 and this report is delivered on a support package, even on systems that are not using HANA. With this report, you can estimate the effort to improve your master data focusing a better performance on MRP Live after an upgrade.

The report provides a compact display, with the total number of materials that can be planned by MRP Live by low-level code, and also specifying the number of materials that cannot be planned by MRP Live for a specific restriction.

The report also provides a detailed display, where all the materials are displayed. Here, the report will tell you if the material will be planned in HANA or in ABAP and it will also tell you if there is any specific restriction for this material.

Therefore, if you are considering to use MRP on HANA, you can use this report to improve your master data and reduce the number of restrictions, focusing a better performance on MRP Live.

I also suggest you to take a look on the following note, which provides more information about the MRP on HANA performance:

2023766 - MRP Live/MRP Classic: Performance Information

See also the information from the following SAP Help link for more details:

MRP Live: Incompatible Changes - Carrying Out the Planning Run Using MRP Live - SAP Library

At last, the common issues on this topic are described on Issues related to MRP on HANA and you may also find answers to the frequently asked questions on MRP on HANA FAQ - ERP Manufacturing (PP) - SCN Wiki.

When we are planning a material on an individual stock, such as a sales order stock or a WBS stock, this material is planned on a separate stock segment.

In this case, the existing replenishment elements and the plant stock are not considered by MRP to cover the requirements under this individual stock and new planned orders are created by MRP to cover those requirements.

By default, MRP will consider the standard lot-for-lot logic (similar to lot sizing procedure EX) and it will create replenishment elements to cover exactly the shortage quantity. This standard logic for individual planning was developed, in order to avoid a leftover stock under the individual segment, as it would need an additional goods movement to transfer this leftover from the individual stock to the plant stock.

Considering the example below, where a fixed lot sizing procedure (FX) of 10 was defined for the material. On the Stock/Requirements List (transaction MD04), we can clearly see that MRP created planned orders of 10 EA to cover the Planned Independent Requirements, respecting the lot sizing constraints.

However, for a sales order under the individual sales order stock, a single order planned order of 30 EA was created to cover the sales order requirement, which means that the fixed lot sizing procedure was not considered.

Under specific circumstances, we want to use a different lot sizing procedure under the individual stock, such as a fixed lot sizing procedure or a rounding value for example. In this case, there is a setting on the lot sizing procedure customizing which allows us to choose which logic we want to use under the individual stock segments.

The mentioned customizing can be found in transaction OMI4, as we can see in the image below:

The options available for this customizing setting allow us to simply consider the rounding or to use the same lot sizing procedure used in the Short-Term Horizon.

Now, let's see what happens on the same example if we create a new lot sizing procedure, as a copy of the standard lot sizing procedure FX. Here, we will change the value of the field Lot Size: MtO to 2 - 'Lot size as in short-term period' and set this lot sizing procedure for the same material used on the previous example.

Here, we will observe that the same logic used to calculate the quantity of the planned orders created to cover the PIRs was used for the planned orders created under the individual stock. That means, the fixed lot size of 10 was considered under the individual stock.

Besides a sales order individual stock, the same setting is also valid for a project or WBS individual stock.