A status is an indicator that fulfills two functions:
- It informs you that a particular status has been reached (for example, The order has been released)
- It influences the number of business transactions you can perform.
Order status management determines, for example:
o Which status is defaulted by the system when you open the order.
o Which transactions are allowed or forbidden in a particular status (a transaction is only allowed if it belongs to the transaction group of the order status, and is not prohibited by the system status)
o Whether and when planning documents are written.
o Which attributes the screen fields have during master data maintenance in the given status.
o When you can select the order for deletion
A status can be either active or inactive: A status can
- Allow a business transaction
- Allow a business transaction with a warning
- Prohibit a business transaction
To use a business transaction, the following is required:
- At least one active status must allow the business transaction.
- No active status may prohibit the business transaction.
System status and User status:
System Status
o The system sets a system status informing the user that the system has executed a certain business transaction for an object.
o You can only influence this status by executing a business transaction that changes the system status.
o If you release an internal order, the system automatically sets the Released system status.
User Status
o You can set a user status in addition to the existing system status.
o You specify the user status in a status profile, which you create for each order type in Customizing.
o You can specify and activate any number of user statuses.
o In a production order you can simultaneously set the Released, Pre-costed, Printed, and Finally confirmed statuses.
The system status and the user status influence the business transactions in the same way.
The status profile allows you to:
o Define the user status and document its functions with a corresponding long text.
o Assign a status number that specifies the order in which the system reaches the user statuses.
o Define an initial status, which is then automatically set when an object is created.
o Determine that a user status is automatically set when you execute a business transaction.
o Permit or forbid specified transactions, if a status is active.
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 |
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:
1. - Planning primary costs
2. - Planning overhead
3. - Posting external invoices
4. - Material withdrawals
5. - Allocating internal activities
6. - Posting overhead
7. - Settlement of costs
8. - You can use these transactions to form transaction groups, for example:
9. - Cost planning
10. - Posting preproduction costs (external invoices)
11. - Posting running costs (internal activities, material issues, overheads):
12. - Posting follow-up costs (only external invoices)
13. - Settlement
14. - You can then use these groups to define which transactions are allowed and prohibited at given times:
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.
o The disallowed transaction group limits the allowed transactions.
Each internal order passes through four system statuses, one of which is always active.
- Created - In this status, for example, actual postings are not possible.
- Released - Nearly all business transactions are allowed in this status.
- Technically completed - In this status, for example, you cannot make any planning changes.
- Closed - In this status, for example, no cost-relevant business transactions are allowed.
In addition to the four system statuses already mentioned, further system statuses are set through given business transactions. Examples are:
- Locked - In this status you cannot carry out any business transactions except for resetting the lock.
- Settlement rule created - This status is set automatically by the system if you created a settlement rule.
No comments:
Post a Comment