Hierarchy

⤷

⤷

⤷

IMG Activity
ID | SIMG_CFMENUORKAKOV2 | Define Transaction Groups for Order Status Management |
Transaction Code | S_ALR_87005259 | IMG Activity: SIMG_CFMENUORKAKOV2 |
Created on | 19981222 | |
Customizing Attributes | SIMG_CFMENUORKAKOV2 | Define Transaction Groups for Order Status Management |
Customizing Activity | SIMG_CFMENUORKAKOV2 | Define Transaction Groups for Order Status Management |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMG_CFMENUORKAKOV2 |
The business functions that you can use in the SAP System are called business transactions.
In status management, there are two ways of controlling which business transactions are allowed or disallowed for an order:
- Using the order status
The order status determines the business transactions that can be used on the order.
- Using the Disallowed TranGroup field
In the order master, you can enter a business transaction group as a "disallowed transaction group". The business transactions contained in this group can no longer be used on the order.
This enables you to lock the order individually for business transaction groups.
You can thus use a business transaction if the order status allows it, or if it does not belong to the group of disallowed transactions.
Example
When you make a posting for a G/L account, the system internally sets the RFBU business transaction (FI postings).
When you plan primary costs in cost centers or orders, the system sets the RKP1 business transaction (Cost planning).
Requirements
To be able to implement this transaction control, you need to define business transaction groups.
Standard settings
The SAP System contains the following business transaction groups which have defined business transactions:
- Group ALL
Contains all business transactions possible for internal orders.
- Group ABSL
Contains all business transactions needed for monthly closing (such as settlments).
- Group NOPL
Contains all business transactions possible for internal orders except for planning transactions.
- Group PLAN
Only contains business transactions for planning.
- Group RECH
Contains business transactions which allow the posting of primary costs and overhead rates.
Note
Business transaction groups must be unique within a particular client. This means a business transaction group must have the same meaning in all controlling areas.
You can split a system status up into more than one status, and then assign the business transactions to each individual status.
Example
You wish to limit business transactions to a certain time. External invoices are only to be posted before order settlement. You can do this by applying the Released system status and assigning the business transaction to exactly where it is to be allowed.
Activities
RESET N1
- Check whether the standard business transaction groups meet your requirements.
- Change the standard business transaction groups as required.
- Create new business transaction groups as required.
Business Attributes
ASAP Roadmap ID | 203 | Establish Master Data |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | SIMG_CFMENUORKAKOV2 | 0 | HLA0001399 O HLA0001475 |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
COVG | L - Logical transport object | KOV2 | 01 | Controlling CO: Transaction groups | ||
KOV2 | T - Individual transaction object | KOV2 | 9999999999 | Maintain Transaction Grps for Orders |
History
Last changed by/on | SAP | 19981222 |
SAP Release Created in |