Technical Information on the Transaction Variants 
Technical Information on the Transaction Variants
Use
The technical information on the transaction variants in backflushing is directed at the system administration of a company who is responsible for creating and assigning transaction variants for the users.
Features
The creation of transaction variants is a general function which can be carried out in every component of the SAP system.
Please also refer to the online manual Transactions and Screen Variants.
Activities
Transferring existing transaction variants:
Transaction name |
Description of the screen after accessing the transaction variant |
STOCK_ALL |
Only make-to-stock production, all fields visible |
ORDER_ALL |
Only make-to-order production, all fields visible |
SEIBAN_ALL |
Only production by lots |
STOCK_MIN |
Only make-to-stock production, extremely simplified |
STOCK_MIN_RP |
Only make-to-stock production, extremely simplified with reporting point backflushing |
RESTRICTIVE |
For demonstration: Only make-to-stock production, fill in fields/not ready for input, deactivate status function |
MAXIMUM |
Copy template: No change of the screen; contains screen variants for the most important screens in backflushing (transaction MFBF) including the component backflush, the document-specific reversal and the collective entry |
DEFAULT_MFBF |
As above without document-specific reversal and collective entry |
Creating your own transaction variants from existing ones
A series of transaction variants exist for backflushing which you can use as a template. A transaction variant consists of several screen variants. It is assigned to the transaction whereas the screen variant is assigned to the screen.
You can create your own screen variants to suit your needs. To do this, you copy existing screen variants and simply change the field values to create new transaction variants.
Creating your own variants:
You can also create your own transaction and screen variants without using any existing ones (transaction SDH0). Here, it is important to know the screens that are assigned to the transactions. You also require test data in the system as you must actively proceed through the screens in order to create the variants.
Program |
Screen |
Description |
SAPLBARM |
800 |
Subscreen container, contains logic, status, if necessary, GUI-xT-Script |
SAPLBARM |
801 802 803 |
Make-to-stock production tag pages Make-to-order production tab pages Production by lot tab pages |
SAPLBARM |
811 812 813 815 |
Yield backflush Scrap backflush Excess component consumption / scrap Excess activity consumption / scrap |
SAPLBARM |
160 |
Selection of production versions |
SAPLBARM |
181 |
Selection of reporting points |
SAPLCOWB (Component screen) |
803 540 130 |
Header information Component backflush Pushbuttons |
SAPLBARM |
400 500 505 |
Reversal (MF41), initial screen Collective entry: Overview Details |
Dynamic function key (not a fixed assignment)
FCODE |
Description |
REVR |
Document-neutral reversal |
TOGG |
Yield/scrap toggle |
ISTDA |
Post with correction |