on 08-22-2007 12:55 PM
hi,
With regard to field status variant how it is determined from the fico point of view how it is to be checked for mm,pp,sd
kindly send me a guide regarding the same
my mail id is rupasridhar1@yahoo.com
Thanks in advance
Rupa
Message was edited by:
Rupa Sridhar
Hi
Check the following T.codes:OB52,OMSY,MMPV and MMRV
Regards
Prasad
Accenture
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Pls check this link for details on field status variant
http://help.sap.com/saphelp_erp2005/helpdata/en/c7/a88b2743dd11d182b30000e829fbfe/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/96/8b3ded43ce11d189ee0000e81ddfac/frameset.htm
https://www.sdn.sap.com/irj/sdn/profile?userid=3627132
Hope this helps
assign points if helpful
regards,
radhika
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Field Status Definition
You have to define field status outside of the master record. Mark the field status you need for each field or field group under a field status group. Then assign the field status group to individual G/L accounts in the G/L account master records.
Field status groups are independent of company code, attaching instead to the field status variant. A separate variant exists in each company code for field status groups in the standard delivered system. The variant name is the same as the company code, and each company code is assigned to this variant.
You can work with the same field status groups in more than one company code, as outlined below:
Maintain field status variant
Assign company code to field status variant.
If you do not maintain the field status, all fields will be hidden.
Example of a field status group
You defined a separate field status group for bank accounts because you always need the same fields for posting to bank accounts. Within this group, the allocation number, text, and value date fields are optional. You have specified that all other fields be suppressed.
Other factors
Besides the field status group in the account master record, your posting key specifications also affect posting. For each posting key, you can decide what status any fields should have with a key when posting. But because there are only two posting keys for posting to G/L accounts in the standard system, you should use the field status groups from accounts in the master record for your screen layouts. The field status definition for posting keys 40 (debit posting to G/L accounts) and 50 (credit posting to G/L accounts) have optional status for each field in the delivered system. Do not change this.
Some fields are controlled by other specifications. If you work with business areas, show the field centrally using company code specifications. The component documentation for general ledger accounting (FI-GL) as well as accounts receivable and payable (FI-AP/FI-AR) explains in greater detail when fields can be suppressed or shown independently of a field status group.
Field status groups and reconciliation accounts
You must also enter field status groups in reconciliation accounts. These specifications affect the customer or vendor account during posting. You cannot enter any field status groups in the master records for these accounts.
Assign Points
Zia
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
108 | |
12 | |
11 | |
6 | |
5 | |
4 | |
3 | |
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.