Field Status variant for creating FB60/65/70/75

Hello everyone,
Our client wants to make Material Group field (V023-MATKL) field mandatory for FI invoices. I looked at the FSV and FSG. It has materials management and below that it has only purchase order etc but no Material Group. I know BSEG does not contain MATKL field at all.
My question to everyone is;
1. is it possible to customize/add the fields under the groups "general" or "material management"?
2. if yes, how (is it code modification?)
3. if not, what is the alternative I have to satisfy the requirement?
Any help will be highly appreciated.
TIA,
Anuj

I would suggest using CO-PA for this.
You can create rules to determine values for material group.
You will need a CO-PA expert to advise you.

Similar Messages

Company code ZG01 is not assigned to a fiELD status variant

HI,
I have created company called 'zg01'.
when i try to create a GL ACCOUNT FOR this company using (FS00) i am getting the following error.
Company code ZG01 is not assigned to a fiELD status variant.
FOR YOUR INFORMATION I HAVE CREATED COA and assign the same to the company ZG01.
Please suggest....
also suggest how to i transport GL Accounts used by other companys of my system to my newly created company code : zg01.
so that i can save creation of GL ACCOUNT.

You have to maintain field status variant and assign it to your company code. This is required for GL master data.
1. Define Field status variant in SPRO>Financial Acctg>Financial Acctg Global Settings>Document>Line Item>Controls>Define Field status variant. You create the field status variant and the field status group.
2. Assign the Field Status group to your company code SPRO>Financial Acctg>Financial Acctg Global Settings>Document>Line Item>Controls>Assign Company Code to Field Status Variants
Once you have defined this you will be able to assign field status group to your GL master data.
The use of Field Status Group is to determine the required/displayed/optional fields during posting transactions.

Custom fields in Field status variant and Posting keys

Hi,
We have defined some custom fields in BSEG table for which we wish to control the field status through Field status groups and Posting keys as well.
Has some one addressed this requirement before? Please provide me some inputs on this.
Regards,
Swapnil

Hello Chakardhar,
Since the same fields for document entry are required for several G/L accounts, you define the status of fields for a group of G/L accounts.
You create the definition under a field status group. Enter the key of the group in the master record of the G/L account. Field status groups are cross-company code, that is, they do not depend on the company code but on the field status variant. In the standard system, a separate variant for field status groups exists for each company code. The name of the variant is the same as the company code. Every company code is assigned to the variant with the same name. You can work in several company codes with identical field status groups as long as these company codes are assigned to the same field status variants. You define the field status for each individual posting key.
Hope I ahd been able to hep you out. Please assign points and let me know if you need anything specific.
Rgds
Manish

SAP report of field status variant, in 4.7

Hello all,
Is there a SAP report that lists a field status variant, its groups, the groups fields, and the entry properties of the fields?
In customization, path /Financial Accounting/Financial Accounting Global Settings/Document/Line Items/Controls/Maintain Field Status Variants - execute
Gets you to the transaction where this is set up. If you have access to this transaction, you can see all of that information, even capture it to a spool or presentation file.
We want to give this information to users who don't have that access.
I am hoping that someone knows of a SAP report with that information, or someone has already created their own report and is willing to share some code.
I started to look at function PREPARE_FIELD_SELECT_STRING, but got lost in the detail. If that is only way to get what I want, well...
Thanks
Bruce

This is my solution. Simple code, once I finished debugging the function module PREPARE_FIELD_SELECT_STRING.
tables: t004f,       " Field status definition groups
        tmodf,       " Groups in Field Selection Bar
        tmodg,       " Name of Groups in Field Selection Bar
        tmodo,       " Items in Field Selection Definitions
        tmodp.       " Name of Items in Field Selection Definitions
data: w_t004f type t004f.
data: i_t004f type table of t004f.
data: begin of gruptab occurs 0,
        ggrup   like tmodo-ggrup,
        ftext   like tmodp-ftext,
        xhell   type c,
      end of gruptab.
data: c500(500)    type c.
data: incoming_string(200).
data: fleng(4)     type n.
data: w_string_position(3) type n.
select-options: s_fstva for w_t004f-bukrs default '0001' obligatory.
selection-screen skip 1.
select-options: s_group for t004f-fstag default 'GT02'.
start-of-selection.
select * from t004f into table i_t004f   "
           where bukrs in s_fstva
             and fstag in s_group.
loop at i_t004f into w_t004f.          " field status groups (FSG)
    skip 1.
    write: / w_t004f-fstag.
    perform get_subgroup_list.
endloop.                                                  " i_t004f
end-of-selection.
form get_subgroup_list .
clear gruptab. refresh gruptab.
incoming_string        = w_t004f-faus1.
incoming_string+90(50) = w_t004f-faus2.
select * from tmodf where fauna = 'SKB1-FAUS1'.
    gruptab-ggrup = tmodf-ggrup.
    select single * from tmodg where spras = sy-langu
                               and   fauna = tmodf-fauna
                               and   ggrup = tmodf-ggrup.
    if sy-subrc = 0.
      gruptab-ftext = tmodg-ftext.
    else.
      gruptab-ftext = text-ngg.
    endif.
    append gruptab.
    skip 1.
    write: /5 gruptab-ftext,
           50 'Suppress',
           60 'Required',
           70 'Optional'.
    perform get_fields.
endselect. " FROM tmodf
endform.
form get_fields .
* ------- Read the item texts
select * from tmodo where fauna = 'SKB1-FAUS1'
                        and ggrup = tmodf-ggrup.
    select single * from tmodp where spras = sy-langu
                               and   fauna = tmodo-fauna
                               and   modif = tmodo-modif.
    write: /10 tmodp-ftext.
* get individual field options
    write tmodp-modif to w_string_position.
    w_string_position = w_string_position - 1.
    case incoming_string+w_string_position(1).
      when '+'.
        write: 60 'X'.             " obligatory
      when '.'.
        write: 70 'X'.             " optional.
      when '-'.
        write: 50 'X'.             " supress
    endcase.
endselect. " FROM tmodp
endform.
Edited by: Bruce Tjosvold on Jun 30, 2011 7:17 PM

Field status variant

HI,
in Tcode OBC5 what is field status variant - use of it
where it is defined & assigned

Hi,
Field status variant is defined in tcode OBC4.
It is the field group which defines which field should be suppressed, mandatory & optional to fill while creating a gl account.
Field group 0001 is the by default from which you can copy for your company purpose & name it as per your requirement. You can also define the new field in the copied field group for your purpose. You can make changes in the copied group by double clicking on them, then it shows the select the group, then double click on anyone you like. It will show the fields from there you can change the setting & highlight the field as per your requirements.
Please let me know if anymore help u need.
Regards,
Prafful Kansal

Field status variant and posting keys.........

posing key can do all the functions of field status variant..............so what is the purpose of defining field status variant.............?

Hello Chakardhar,
Since the same fields for document entry are required for several G/L accounts, you define the status of fields for a group of G/L accounts.
You create the definition under a field status group. Enter the key of the group in the master record of the G/L account. Field status groups are cross-company code, that is, they do not depend on the company code but on the field status variant. In the standard system, a separate variant for field status groups exists for each company code. The name of the variant is the same as the company code. Every company code is assigned to the variant with the same name. You can work in several company codes with identical field status groups as long as these company codes are assigned to the same field status variants. You define the field status for each individual posting key.
Hope I ahd been able to hep you out. Please assign points and let me know if you need anything specific.
Rgds
Manish

Field Status Group for Special G/L Indicators

Could you define different field status group for special G/L indicators? My problem is I am using two different special G/L indicators but their recon accounts are assigned with the same field status group. I used the same posting keys as well. But when it comes to general posting, they have different screen numbers. One SAPMF05A 303 and the other one is SAPMF05A 304. How did this happen?

Hi Noel,
As you have defined Field Status Group for 2 different SPL GL Indicators then it will create 2 different screens only as it wont consider the reconciliation account.
Regards
andrew

Field status variant how it is maintained

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 [email protected]
Thanks in advance
Rupa
Message was edited by:
Rupa Sridhar

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

Transactional dependent field status variant and field status varinat

hi gurus,
can any one please tell me what is transactional dependent field status variant and field status varinat and what is the difference between the both,what this both control?
appreciated if answered.
Regards,
sandeep.ch

Hi
Any field status varinat is a bundle of filed status grouop(FSG). A FSG will control the Screen layout of the Document while you post.Whether a filed is required, optional or suppressed etc.
Transactional dependent data:
Transaction Dependent Control - Field status can also be configured at the master data transaction level i.e. during Create, Change, and Display. Thus, if a user wishes that after creation of master data certain fields should not be changed, same can be set as 'Display'. One such example can be fields like reconciliation account, payment terms etc.So these terms remain constant while posting and user cant change these fields.
Regards
Aravind
Assign points if useful.

Field Status Group For MIRO

Dear Friends
Pls say me where we can get the field status group for Miro header level where i got a problem to make the business area manditory.
Regards
Vinay Bhaskar

Hi vinay
for busienss place we can make the field mandatory thorugh validations it is not possible through FSG
Plz reward the point if it is useflull
Regards

How to How to get FI field status settings for General data

Hello All,
Can you please tell me How can I achieve field status settings for General data.
I have some code to get field status settings for account assignment block but I need General data block data.
Can you please help me with the same.
I got the below code to get field status settings for account assignment block But I need General data block information.
FUNCTION z_fieldstatus_getdetail.
*"*"Lokale Schnittstelle:
*" IMPORTING
*" VALUE(I_BSCHL) TYPE BSCHL
*" VALUE(I_BUKRS) TYPE BUKRS
*" VALUE(I_SAKNR) TYPE SAKNR
*" TABLES
*" T_COBLF STRUCTURE COBLF
*" T_FIELDS STRUCTURE TCOBF OPTIONAL
*" EXCEPTIONS
*" ERROR_MESSAGE
* liefert Feldstatus in Liste t_coblf:
* Feldname (DDIC) nicht in der Liste -> Feld ausgeblendet
* Feldname (DDIC) in der Liste -> Feld eingabebereit
* required = 1:
* Mussfeld;
* required = 0: kein Mussfeld
* active = 0: Feld ausgblendet
* Als Hilfstabelle wird die gesamte Feldliste der Felder (t_fields)
* ausgegeben,
* deren Eingabebereitschaft im Customizing steht
DATA: ls_faus1 LIKE tbsl-faus1.
DATA: ls_faus2 LIKE tbsl-faus2.
* Feldstatus holen
CALL FUNCTION 'FI_FIELD_SELECTION_DETERMINE'
 EXPORTING
 i_bschl = i_bschl
 i_bukrs = i_bukrs
 i_saknr = i_saknr
 IMPORTING
 e_faus1 = ls_faus1
 e_faus2 = ls_faus2
 EXCEPTIONS
 customizing = 1
 OTHERS = 2.
IF sy-subrc <> 0.
 MESSAGE a613(/ssc/comon).
ENDIF.
DATA lv_char.
DATA int_coblf LIKE coblf OCCURS 0 WITH HEADER LINE.
DATA p_cobl LIKE cobl.
DATA: dummy_ktosl LIKE bseg-ktosl.
PERFORM kontierungsblock_ermitteln(sapff001)
TABLES int_coblf
USING lv_char(1)
ls_faus1 ls_faus2 dummy_ktosl.
t_coblf[] = int_coblf[].
SELECT * FROM tcobf INTO TABLE t_fields.
ENDFUNCTION.
Thanks in Adv.
Kaustubh

Hi ,
Looking at the question the first thing that comes to my mind is what is the organization structure that you are following .
As you have mentioned that you have used segment insted of profit center for splitting , what is the scope of profit center in your implementation .
in implementations where locations are devided as profit centes it becomes very necessary to mandatorily split the documents based on profit center .
in your case as you have set it as segment i dont find it an issue of you keeping it as optional as it will not give you and error during your operations , as you have made profit center optional in splitting charcteristics .
hope this suffices .
Regards ,
Dewang

Carrier Details on Field status group for vendor master

Hi,
I have a requirement to make the SCAC and Carrier freight group as required fields on vendor master .
but the standard SAP system requires/ allows three fields : SCAC , carrier freight group and Service agent procedure group as mandatory to be activated under the 'carrier details ' column in the field status group (transaction OB23 and OBD3).
I want to know if there is a way to flag just the SCAC and carrier freight group as required fields for entry in vendor master .
Thanks
Naga Yarramsetty

Hi All,
Thanks for your reply. With user exit and validation, I cannot create mandatory mark in FS00. Actually SAP make this description always mandatory. But there is no mandatory mark in this column. I just want to create mandatory mark in this column. Need you advice.
Thanks,
John

What are the mandatory fields of BAPI for creating a new purchase order?

Hi friends,
I am very new to XI.My Boss has given me task to create a purchase order using BAPI. I want step by step guide to create it.How will i know which fields are mandatory for BAPI_PO_CREATE?

Hi Shweta,
However It depends upon the configuration that which fields to be passed.
But you can check this by running the BAPI in the SAP system by using transaction Se37.
The most commanly used fields are:
HEADER :
DOC_TYPE                       NB
CO_CODE                        9001
PURCH_ORG                    9001
PUR_GROUP                    900
VENDOR                         100000
ITEM
PO_ITEM                        00001
MATERIAL                      MM10
STORE_LOC                   01
MAT_GRP                       01
SHORT_TEXT                  SERVICE (optional )
PLANT                            9001
NET_PRICE                    500
ITEM_SCHEDULE
PO_ITEM                        00001
SERIAL_NO                      0001
DELIV_DATE                     05.04.2008
QUANTITY                                  1.000
You can run the BAPI with some test data... if something is missing the BAPI will ask for it... the Results are displayed in Return Table.
Regrads,
Sachin

Show Purchasing group Field in UI for Create Limit Item

Hello All,
Do you if there is a way without modifying the templates to show Purchasing Group in UI for Create Limit Items in SRM 4.0 ( Classic Scenario)?
-thanks in advance
Shilpa

Hi
Yes. Without modifying the HTML Templates of the Internet Service - BBPSC01,
This is possible by adding a custom field at the Shopping cart item level in the structure. There is no such limitation on the number of customer fields added.
Refer to the following SAP OSS notes
Note 458591 - User-defined fields: Preparation and use
Note 672960 - User-defined fields 2
Refer this link for details ->
Add custom field in SC -Item Level
Which SRM version are you using ? What's your Business requirement ?
Incase you want to transfer some data from catalog to Shopping cart.. you can get this done by using BADI.
Try BBP_DOC_CHANGE_BADI
BBP_DOC_CHECK_BADI
using SE18 Transaction.
Do let me know.
Regards
- Atul

Check G/L field status group for Business area

Hi, when I set the buiness area, I set field status group to required for BA field, the setting always check the BA field on accouting doc. But some G/L is automatic posted, always show "Business area is a required field for G/L account ...",
Can you help me to slove, thanks

Check the following issues
1)Check the status of the other GL accounts field status for business areas.
2)Check if there is any validation for GL accounts which can be given without business area.
Hope this helps.
Regards

Field Status variant for creating FB60/65/70/75

Similar Messages

Maybe you are looking for