Business Transaction Control Through Status Management

  • by Kaushik Choudhury, Senior SAP Supply Chain Consultant
  • February 21, 2014
Learn how to use status management functionality to support business process requirements that are not supported by SAP ERP Central Component (SAP ECC). This approach can save time and money during the implementation, support, and upgrade phases of a project.
Learning Objectives

By reading this article, you will learn how to:

  • Address business requirements through status management
  • Set up configurations to control business transactions through status management
Key Concept

Status management controls the business transactions that can be performed (with or without warning) or prohibited for an object (such as production order, inspection lot, or quality notification) with a particular status (or combination of statuses). The status of an object can be set by the system, based on some business transaction triggered by a user or set manually by a user.

During the requirement-gathering phase of a project, businesses share a number of processes that at first glance appear unsupported by standard SAP ERP Central Component (SAP ECC). Many functional experts start exploring user exits, Business Add-Ins (BAdIs), or customization to support these processes without any further attempt to meet these requirements using standard SAP functionality. Customizations and implementation of user exits not only involve time and budget during the implementation phase of a project but also are costlier to maintain during the support and upgrade phases of a project.

I discuss business process requirements that are not supported by SAP ECC, but that can be supported through status management. This approach avoids the development of custom objects, resulting in faster realization and lower maintenance/support and upgrade costs.

Object Status

The status of an object indicates the business processes that are completed and controls which activities are allowed (with or without warning) and which are prohibited.

An SAP system includes two status types: system status and user status. System status is set by the system when a particular business transaction is completed. Changing the system status configurations is not recommended as per SAP best practice. Any change in system status affects all the object types where the status is being used. For instance, if you change the behavior of system status CRTD for a business requirement related to a production order, it also affects the maintenance order and other objects in which this status is used by the SAP system. User status can be configured to be set for an object manually or configured to be set upon completion of a particular business transaction.


Kaushik Choudhury

Kaushik Choudhury is a senior consultant in the supply chain management field with more than a decade of experience in supply chain consulting in principal positions for leading brands across the globe. His focus is on business transformation, business reengineering, proof of concept and solution design, and end-to-end implementation. He has a proven track record of delivering in alignment with business expectations and possesses a unique combination of profound business process understanding, consulting skills, hands-on SAP system experience, and effective management capabilities. Kaushik has operated seamlessly in highly agile and iterative environments in which solutions are implemented incrementally with ongoing design changes. He has extensive experience in Agile and Waterfall delivery methodologies in large SAP supply chain implementation programs.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.