Hi
SAPu2019S GENERAL STATUS MANAGEMENT FUNCTIONALITY
General Status Management replaced order status management functionality in recent SAP releases (4.6C). This discussion will address general status management, as this is how SAP allows user statuses for controlling objects in this and future releases.
General Status Management applies to internal orders, project definitions, WBS elements, production orders and many other objects in SAP. For the purposes of this discussion we will concentrate on status management for internal orders and WBS elements. A list of all objects relevant for status management will be made available upon request.
A status is an indicator that fulfills two functions. First, it informs you that a particular status has been reached. For example, an internal order has been created and released; a settlement rule has been entered; a particular business transaction has been executed, etc. Second, it influences the business transactions you can perform for a particular status. A status can allow a business transaction; allow a business transaction but issue a warning message; or prohibit a business transaction altogether. If a warning message is issued it is up to the user whether the business transaction is carried out or not.
Statuses can be used to control and communicate. Statuses can be used in reporting (show me a report of all internal orders with a status of TECO, or technically complete). Statuses can be used as selection criteria (select all internal orders with a status of CLSD, or closed). Statuses can communicate the state of an object (ready for archiving, not ready for settlement execution).
There are SAP standard delivered statuses that apply to all object types. These are known as SYSTEM STATUSES. CRTD, REL, SETC, TECO are examples of SAP standard system statuses. SAP standard system statuses cannot be removed from use. You cannot override the SAP system status with a user status. You cannot change the behavior of an SAP system status.
User statuses (or user defined statuses) exist in addition to SAP standard statuses. User statuses are intended to augment or refine SAP standard statuses, not replace them. There is no limitation to the number of user statuses that can be created. Both system and user statuses influence business transactions in the same way.
An object can have multiple statuses active at the same time. A plant maintenance order can have released, preliminarily costed, work order printed and confirmed statuses all at the same time. For SAP display purposes only one status can be displayed on the status line in master data screens, but it is possible to see all active statuses for an object at one time by drilling down into the master data screens.
A STATUS PROFILE, or user status profile, contains individual user statuses and the business transaction rules defined for those statuses. There is no limit to the number of user status profiles that can be maintained in SAP. A user status profile is assigned to an order type or a project profile in configuration. This user status profile is then defaulted into all objects that reference that order type or project profile. A users status profile can be overwritten (or deleted) in an individual object (via native master data screens), but only if a user status has yet to be activated for that particular object. Once a user status has been activated for that object the user status profile cannot be changed.
HOW STATUS MANAGEMENT WORKS
When an object (internal order, WBS element, production order) is created SAP assigns the system status CRTD. MIT automatically releases the order, so the system status REL is also activated. If there is a user status profile defined in the order type (or project profile) this is carried over into the internal order (or WBS element). If not, only the SAP system statuses will apply to this object.
When a user executes a business transaction for this object, SAP checks the user status to see if that business transaction can be executed without any additional influence from a user status, can be executed but with a warning message being issued, or cannot be executed at all. SAP also checks whether the business transaction sets or deletes any other user statuses within the user status profile.
A user status may also be maintained directly in the object master data. Accessing the master data screens allows a user to manually maintain user statuses. If necessary, an authorization code can be assigned to a user status to ensure that no unauthorized persons can change the status of an object. Once changed, the new user status is fully active and acts no differently than if a business transaction set the user status.
Status management and business transaction control only work with standard SAP transactions. Z transactions will not show up on the business transaction list for an object. The business transaction table is configurable, but SAP strongly recommends not changing that table. SAP directly updates that table via support packs and it is often impacted during upgrades.
Authorization codes / keys are available in user statuses. The authorization code is checked only when user statuses are being set manually, from within the objectu2019s master data screens. This ensures the user has the proper authorization to set that status for that particular object. However, it is important to understand that SAP sets a user status in reaction to a business transaction it does not perform an authorization check.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.