Order Status Management 
Order Status Management
Use
You should not use this form of status management, as it is obsolete and no longer included in general SAP status management.
You define the old order status management for each
order type. Each order type has its own status management, which you can more or less structure according to the function of the orders.General business practice often requires a detailed subdivision of the order cycle, based on the business transactions that take place on the order.
The business transactions for a trade fair order are displayed below.
There are different business transactions in the Released system status: Posting preproduction costs (external invoices), and posting production costs. Posting follow-up costs in the Technically completed system status involves posting external invoices.
Status |
Business transaction |
Created |
Planning |
Released |
Posting |
Released |
Posting |
Technically complete |
Posting |
Closed |
None |
It is likely that you will want to limit business transactions to given periods. For example, posting external invoices would only be possible before the order has been settled. Or, you do not allow any more internal activities after the order is technically complete.
You can do this by subdividing your Released status and assigning the transactions to where they are to be allowed.
You can subdivide a system status into more than one status. You can subdivide a system status into more than one status.
Unlike the general SAP status management, the system status is not changed using a function in order status management. The system status is directly linked to the order status and is thus automatically changed when the status changes.
Business Transaction Group
You can define business transaction groups by grouping more than one business transaction together, in Customizing, under Controlling -> Internal Orders -> Master Data in Internal Orders -> Status Management in Internal Orders -> Order Status Management.
The transactions for a trade fair could consist of the following actions:
Business transactions are allowed on an order, depending on whether you assign a status to the transaction group that they belong to. If a transaction is not assigned to a status, then it is prohibited in this status.
Disallowed Transaction Group
To prohibit business transactions for individual orders, define these as a transaction group, and store it in the order as a disallowed transaction group.
A disallowed transaction group can be identical to the currently allowed transaction group. It can also consist of only part of the transactions from the allowed transaction group. The disallowed transaction group limits the allowed transactions.
Order status management determines, for example:
The following graphic shows a status overview for trade fair orders. In this example, we have defined six statuses (from 10 to 60) for the order type.
The columns contain the following:
Order Status
The first two columns from left to right contain the
order status number and a description.LSt, HSt
(lowest status, highest status)These two columns determine how you can change the status in the order. The next example provides you with a detailed description.
Crt, Rel, Cmp, Cls
(created, released, technically completed, closed)These four columns contain check boxes for the different system statuses. To assign the order status to a system status, mark the appropriate column. When you do this, you need to follow the sequence from left to right. You also need to use the numerically ascending sequence for the status.
TranGrp
(transaction group)This column contains the transaction group allowed for each respective status.
PlD
(planning documents)In this column, indicate whether you want to log planning changes in this status. This enables the system to write line items (that you can display) for each change in order planning. Of course, the allowed transaction group must also include planning actions, otherwise you cannot plan, and the indicator has no effect.
Dst
(default status)Select the default status in this column. This is the status that the orders of this order type should have when they are created, and is usually the status with the lowest number.
The default status is only a default value, and can be overtyped if required.
The following example illustrates how status management can affect an order.
You have planned your order in status 10 and now want to release it.
The HSt column shows that you can set the order in status 20 only (setup costs). You therefore change the status in your order to 20.
This causes the following:
If, for example, you now want to return to the planning status, which is allowed according to LSt (lowest status = 10), the system sets the Released date.
From status 20, you can set status 30, where all actual postings are allowed (transaction group ALL). If you make any planning changes now, they are recorded in planning documents according to column PlD.
If you do not expect follow-up costs, you can set status 50 while in status 30, thus skipping status 40. At the same time, you have again changed the system status, which also sets the Technically completed date. You can now settle the order.
Then you realize that one of your employees has not yet submitted his travel expenses. As you cannot post this in status 50, because it only allows settlement, you need to reset the status in the order again.
The lowest status (LSt) determines that you can only go back as far as status 40 from the settlement status. The system notes the highest status that the order has reached to this point. The lowest status to which you can return, therefore always remains the same. Thus, you cannot return from status 40 to status 30, although according to
After you posted the follow-up costs, you can change the status to 50 again, and settle the order.
As soon as the order is settled completely, you can set the deletion flag, as this column is selected for status 50.
You can also set the order to status 60 after it is settled. As indicated in the
LSt and HSt columns, you now cannot make any further status changes.You can no longer post to the order at this point. You can, however, still use it for evaluations in reporting.