Skip to Content

SAP EHP 5 – New Procurement Functionalities – business function “LOG_MM_CI_3”

In this blog, we will discuss only about most commonly used  enhancement package 5 for Procurement business function “LOG_MM_CI_3” which offers customers greater long-term value and an easier methodology.

Activation of business function using SFW5 transaction


After activation, we will be able to see  a) Park Button

b) Templates button        c) Document Flow Indicator

d) blocking reason            e) Retail (required only for IS-Retail) in PR & PO.

Park Button:/wp-content/uploads/2012/03/2_80963.jpg

Use  :  We can park and hold purchase orders and purchase requisitions for materials and services:

Holding of Purchasing Documents : Creating a purchasing document with missing information at that point in time,

or may be interrupted when creating the document. In this case, we can still put, for example, an incomplete purchase order on hold,

and finish it at a later point in time before saving.

Parking of Purchasing Documents  :  If we want to create a purchasing document, the document may be complete from

the materials management point of view, but some financial information may still be missing at that point in time (FI view).

In such cases, we can then provisionally save (park) the purchasing document and continue processing it at a later point in time

before saving.

This function is available in the following transactions:

—  Create Purchase Order (ME21N) and Change Purchase Order (ME22N)

—  Create Purchase Requisition (ME51N) and Change Purchase Requisition (ME52N)

—  Pushbuttons for park and hold have been added to the user interface. The visibility of these pushbuttons depends on the processing stage of the purchasing document. If we want to exit the creation process before it is finished, we can choose the relevant pushbutton, and the system saves accordingly.

Configuration Path to activate Park & Hold button :



—  Public Templates in Purchase Orders and Requisitions (New)

Use  : We can create purchase requisitions and purchase orders more efficiently by using templates. We can use the following functions:

—  Create, use, and delete user-specific templates

—  Create, use, and delete public templates, which are available to all users 

—  We can use entered data as a template without having to save the document first. From the templates we create, we can copy either header and item data or only item data to a purchasing document.

This function is available in the following transactions:

—  Create Purchase Order (ME21N) and Change Purchase Order (ME22N)

—  Create Purchase Requisition (ME51N) and Change Purchase Requisition (ME52N)

—  In these transactions, there are two additional pushbuttons: Save as Template and Load from Template. To create templates that are available to all users, we need the appropriate authorizations (authorization object Create/Change/Delete Public Templates M_TEMPLATE).

Note : When we copy a user, the user-specific templates of the user we are copying are also copied to the new user master record.

—  Entering of Blocking Reasons in Purchase Orders (New)

Use   We can save the reasons for blocking a purchase order item in purchase orders.

—  In Customizing for Materials Management, we can create various blocking reasons with language-dependent texts, which are available in a dropdown box when we block purchase orders. When we block a purchase order item, we can select a suitable blocking reason in the item details. We also define in Customizing whether the text for a blocking reason ID can only be copied unchanged, or whether we can overwrite the text with our own reason. If we overwrite the text for a blocking reason ID in the purchase order, we lose the language dependency. 

Effects on Existing Data:

—  In the transactions ME21N (Create Purchase Order), ME22N (Change Purchase Order), ME23N (Display Purchase Order), and ME29N (Release Purchase Order), there are new fields for selecting and displaying a blocking reason when blocking purchase order items. The system displays the following fields for blocked purchase order items in the item details on the Purchase Order History tab page:

                 Blocking reason ID (BLK_REASON_ID)

                Blocking reason text (BLK_REASON_TXT)

Blocking Reason Config Path:



PO Item Level Screen:


—  Extended Document Flow in MM and SD Documents (New)

Use  :

—  We can display all the related purchasing and sales documents in purchase requisitions, purchase orders, inbound deliveries, and outbound deliveries with the business function Materials Management – Enhancements in Procurement (LOG_MM_CI_3),

—  In the item overview, we can use the new pushbutton Extended Document Flow. This pushbutton enables us to display purchasing and sales documents that are related to the selected purchasing or sales item. For example, we can display the sales documents related to a purchase requisition or purchase order item, or the purchasing documents related to delivery items. We can only call the extended document flow for deliveries that reference a purchase order.

Effects on Existing Data

In the item overview of the following transactions, we can use the new pushbutton Extended Document Flow:

—  ME52N and ME53N for changing and displaying purchase requisitions

—  ME22N and ME23N for changing and displaying purchase orders

—  VL02N and VL03N for changing and displaying outbound deliveries

—  VL32N and VL33N for changing and displaying inbound deliveries

  Document flow example:


Important Side-effects note:

—  1653977 – ME22N – AM 250 Address errors when creating new items

—  1625040 Template Selection for Purch. not possible

—  1602965 – MAA2: Commitment, VL09 VL622, and serial numbers (Side effect note : Note 1667310 – MAA2: Short dump when releasing GR blocked stock w/ MIGO 105)

—  1563462 – ME21n: Activating allocation table fields in retail tab to remove retail tab:

For more info:

You must be Logged on to comment or reply to a post.