Blocking of Conditions in Purchase Order

[Kunal_Bhattacharya]

In some organizations, business policies restrict the visibility of article purchase costs and net landing cost to specific departments, such as Finance and Merchandise, while excluding others like Store Operations. These policies ensure controlled access to sensitive financial data, aligning with the organization's need to maintain confidentiality and comply with internal governance standards.

In the standard SAP solution, the Net Price field and the Conditions tab in a Purchase Order (PO) are editable for all users with change authorization for POs. However, for some Business this can pose a compliance and confidentiality issue, as users with such access may view sensitive information like margin calculations and terms of trade displayed in the Conditions tab.

To address this, the system needs to implement role-based authorization that allows users to modify specific PO data without granting visibility or editing rights to the Net Price field and the Conditions tab at both the header and item levels. This ensures sensitive financial data remains restricted while enabling users to perform their designated tasks within the PO.

Business Scenario 1: Restricting Condition Changes in Purchase Orders

Users authorized to edit a Purchase Order in ME22N should not have the ability to modify any conditions. All conditions, including those at the header and item levels, should be derived solely from the Purchase Info Record and Master Conditions Maintenance. These users should only have read-only access to the conditions tab to ensure consistency and compliance with business policies.

Business Scenario 2: Suppressing Condition Visibility in Purchase Orders

Users authorized to edit a Purchase Order in ME22N should not be able to view any conditions. All conditions must be derived from the Purchase Info Record and Master Conditions Maintenance. The Conditions tab, at both the header and item levels, should be completely suppressed for these users.

To meet the requirements solely through configuration, a solution involving Function Authorizations and user-specific Parameter Values can be implemented as follows:

For Business Scenario - 1

1. Define Function Authorization code in Transaction OMET.

1. Assign the Function Authorization to the User profile

Enter 01 in the user master record as parameter under the the parameter ID EFB. If the user master record does not contain this parameter, the user has authorization for the full range of functions.

Create/Change a Purchase Order

Create  a Purchase order or go to change a Purchase Order. The conditions tab is in display mode.

For Business Scenario - 2

1. Define Function Authorization code in Transaction OMET. 

1. Assign the Function Authorization to the User profile

Enter 02 in the user master record as parameter under the the parameter ID EFB. If the user master record does not contain this parameter, the user has authorization for the full range of functions.

Create/Change a Purchase Order

Create  a Purchase order or go to change a Purchase Order. The conditions tab is not visible.