on 09-24-2008 10:27 AM
Hi all,
While i create billing document in VF01 with billing document type ZF2(copy of F2) i can able to modify certain fields like billing date, customer account assignment group in header and material assignment group in item details. My client don't want to be show in modifiable mode, can any body advise me on this issue how i have to keep this fields in diplay mode even in billing document creation.
regards
bvdv
Hi,
You can fulfill this requirement through Transaction Variant and the transaction is SHD0.
Through this you can dispaly, eliminate the fields in billing document.
Regards
Goutham
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
the last action was before two months, so I close this thread
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
You can create a transaction variant in SHD0 for VF01.
http://help.sap.com/saphelp_nw70/helpdata/en/7d/f639f8015111d396480000e82de14a/content.htm
Transaction variants simplify transaction flow by:
-Inserting default values in fields
-Hiding and changing the ready for input status of fields
-Hiding and changing the attributes of table control columns
-Hiding individual menu functions
-Hiding entire screens
Transaction variants are actually made up of a series of screen variants. The field values and field attributes for each screen in a transaction variant are stored in screen variants. Each variant is assigned to a transaction. Variants may, however, contain values for screens in multiple transactions, if transaction flow makes this necessary. The transaction the variant is assigned to serves as its initial transaction, whenever you start the variant.
Both client-specific and cross-client transaction variants exist. Screen variants are always cross-client; they may, however, be assigned to a client-specific transaction.
A specific namespace has been designated for cross-client transaction variants and screen variants and they are both automatically attached to the Change and Transport System. Client-specific transaction variants can be transported manually.
Transaction and screen variants may be created for all dialog and reporting transactions. However, there are certain restrictions that apply to their use, depending on how their corresponding transactions have been realized internally.
Transaction variants may not be created for transactions already containing pre-defined parameters (parameter transactions and variant transactions).
The following sections contain additional information on how to create and maintain transaction variants:
Maintenance
Additional Functions
Transport
Regards,
Srilatha.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
92 | |
11 | |
10 | |
6 | |
5 | |
5 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.