Field is missing in Create condition table screen

We are going through one minor issue.We are trying to configure output types for billing docs.I am trying to create a condition table with sold to party field.It is displaying in field catalog,but not displaying in create condition table screen.Any idea how to get it?
Thanks

Hi VCS
As you want to create a condition table at billing level and at  billing level for sold to party it is KUNAG  where as in sales order level it is KUNNR.
VBRK- KUNAG (SOLD TO PARTY AT BILLING LEVEL )
VBAK- KUNNR  (SOLD TO PARTY AT SALES ORDER LEVEL )
so you need to select the sold  to party KUNAG and if that sold to party is not available , create that sold to party feild (KUNAG) . and save it
Now when you cerate a condtion table check wheather that cerated feild is there are not . sometimes it will be there and sometimes it wont be there . if that feild is not there then , we need to take the help of ABAPer's and they will  copy the standard table into Z table and in that they will write the ALV report  or any program . so that it gets triggered in that feild catlog.
example :
KUNAG is availabe in VBRK table
so ABAP'ers will be copying hte standard VBRK table in ZVBRK table  and in that ZVBRK table they will write the program where this feild KUNAG is also inserted.
so when you create a condtion table then you can see this KUNAG feild, in the list of feild catlog,if that feild is not there just maintain . the feild. automatically it gets triggered in the feild catlog
Reward if useful
Regards
Srinath

Similar Messages

  • Add fields in fieldctlg in Create condition table in SPRO

    Hi Experts,
    How can we add more fields in fieldCatlg table which appears in 'Create Condition Table' in Sales Distribution head in SPRO.
    Please Suggest.
    Rajiv Ranjan

    Hi Rajiv
    Please go through this extract from documentation:
    Creating New Data Fields in a Communication Structure
    Data fields are created in the Data Dictionary. You create data elements and fields in the Data Dictionary as well as integrate them in the relevant structures. Use following check list when you create new data fields:
    1. Check whether an identical data field already exists in the standard system
    If you want to use the order reason (AUGRU) for pricing, for example,
    the data element already exists.
    If you want to use parts of the product hierarchy, for example, you must create a new data element (e.g. ZZPRODH1).
    Remember that new data fields must begin with the letter "ZZ" or "YY" because SAP has selected this name convention to protect modifications of the customer during a release changeover. Create a new domain for the new data element.
    If you want to use a new partner function, such as a selling agent (Z1) you have to create a new partner function (Z1) and a new data element (ZZVRTZ1) in Customizing.
    2. Using the source tables, check wether the field is used at header or at item level, which determines the structure in which the field is included. The source tables are listed in the section "Supplying Fields Within the Communication Structure and Using Them in Condition Tables" below.
    The order reason, for example, is included in table VBAK, the product hierarchy in table VBAP.
    3. Integrate the field in the appropriate communication structure by means of an INCLUDE.
    For pricing, for example, you include header fields in KOMKAZ, item fields in KOMPAZ: For the field name enter the field description new fields and make sure that they begin with ZZ or YY. For example, enter ZZAUGRU, ZZPRODH, and ZZVRTZ1 and assign them to the SAP data element AUGRU, or the new data elements you have just created ZZPRODH1 and ZZVRTZ1.
    The description of the individual functions will inform you about the structures into which the fields must be integrated.
    4. Activate the structure.
    5. Include a new field in table T681 and allocate it to the application in which is to be used.
    Example
    A new field for pricing, has the allocation A, V, 001.
    When you have succesfully added the new fields in the communication structure, you will be able to find the same in FIELD CATALOG under the acess squences definition. Please check the same...
    Regards
    Eswar

  • Fields in Field Catalog not available when creating condition table

    I  see that field HIEBO01 to HIEBO12 are available in Field Catalog, but I don't see these fields when creating condition table
    Please let me know what I am missing here.
    Any insight on this would be really helpful.  Thanks guys!

    you need to get them added to the pricing structure KOMKAZ or KOMPAZ based on whether you need @ header level or @ item level respectively.
    and then add the logic in the sales order user exit for these added field in the pricing_prepare_TKOMK or pricing_prepare_TKOMP...again based on header level or item level.....
    Then go back to the field catalog and select from the respective structure and add them, Then you can see them when creating cond tables.
    Hope this helps. Hope i havent misunderstood your query.,
    Regards
    Sai

  • Create condition table

    Can anybody explain how to create a condition table in a detailed manner step by step?
    Thanks in advance for the answers.

    HI
    You can change and maintain the condition tables in the standard system. You can also create new condition tables to meet the needs of your own organization. You create and maintain condition tables in Customizing.
    From the initial screen of Customizing for Sales and Distribution, you reach the condition table screens by choosing Basic functions --> Pricing -->Pricing Control -->Define condition tables. Then select the mode you want to work with (create, change, display).
    ou can create new condition tables to meet the pricing needs of your organization. When you create a new condition table, you select a combination of fields from the list of allowed fields. The selected fields define the key for the subsequent condition records.
    Before you select the fields for the key, there are two things to consider:
    The sequence (or hierarchy) of the fields
    Which fields you want to appear in the header and item areas of the corresponding fast-entry screens
    Important Fields
    In sales, the fields you should take into consideration are Sales organization and Distribution channel. The sales organization is nearly always used as a criteria in pricing, because different sales organizations often want to use their own prices, discounts, and surcharges. If you use the sales organization as a criterion in pricing, you should also use the distribution channel. If you do not want to establish different prices, discounts, and surcharges for each distribution channel, use the field anyway. In Customizing for Sales, you can use one distribution channel as a reference for all others (thereby sharing the same pricing data).
    Deciding the Sequence of Fields
    The order of the fields in a condition table affects the performance of the system during pricing. Two general guidelines will help you create an efficient condition table:
       1. If you select fields that are connected to the structure of your organization (for example, sales organization and distribution channel), assign the fields according to the level of general applicability: Put the most general field, for example, the sales organization in the highest position and the most specific field in the lowest.
       2. After organizational fields, place fields from the document header before those that come from the item level. (For example, Customer comes before Material)
    After you have selected the fields for the key on the screen where you maintain and define condition tables, choose F16 Generate to generate the table in the system. Generation prepares the condition table for storing condition data.

  • Excise rates not reflecting in PO based on values entered in newly created condition table in TAXINN.

    Dear SAP Gurus,
    I have created a new condition table using t.code m/03 by taking a copy of existing standard condition table. I have assigned the newly created condition table to access sequence. After assignment of condition table i have entered the relevant excise rates in excise condition types using the newly created key combination through t.code FV12. When i enter the Tax Code in PO, excise duty rates are not reflecting in PO. When i am entering the excise rates in any other standard key combination, excise rates are reflecting in PO.
    Following are the fields in newly created key combination (Condition Table)
    1) Country
    2) Plant
    3) Control Code
    4) Tax Code
    Kindly help me in resolving the issue.
    Regards,
    Vinay

    HI,
    Check whether you have maintained the rates for the new tax code in FV11 also whether you have assigned the tax code to the company code ?
    Compare the tax code which is working in PO with the one which is not & find out if there is any difference.
    If you want to post the tax values to the new G/L in OB40 then maintain the same settings for the tax code which is working in PO.
    Thanks & Regards,

  • What is the purpose of the release status in creating condition table

    hi gurus,
    can you please tell me the purpose of the release status and validity date in creating condition table for pricing?
    thanks,
    Paul

    Dear John
    The release status controls in which scenarios the condition records are found.
    If the status is set at 'B', for example, then the corresponding records  are taken into account during a pricing simulation, but are not used in current documents.
    The release status can only be maintained directly for agreements (sales deals). For condition records, this is done via the processing status.
    thanks
    G. Lakshmipathi

  • Creating Condition Table.. Key fields and line items

    dear all
    I am creating a Condition table and have 6 fields, I want to make 5 of them as key fields and also header line fields.
    I want my 6th field as line item field but I am unable to do that. My last key field is also shoiwing in line item.
    Please help.
    Thank you.
    Madhu.

    Hi,
    Check this thread
    Re: VK11
    Regards,
    Chandra

  • Addition of field to field catalog in order to create condition table

    hi,
       I need to add field to SAP 5.0 Field Catalog to allow for creation of custom Condition Table. A field named “Serial no. profile”  exists in SAP 4.6c. The equivalent should be added or created in the SAP 5.0 Field Catalog.
    How do i do this. Plz help.

    Thank you. i've got the solution

  • How to delete a field from a Dynamically created internal table

    Hi friends,
    I have got a requirement in which, I will be entering the table name and Excel file from seletion-screen.
    based on the Table I have entered in the selection-screen I need to create a dynamic internal table so that I can fill that Execel data into that internal table and later i using BDC i can I can fill the database table using SM30 transaction.
    here. my problem is that, When I am creating internal table dynamically, MANDT filed is also getting created in the internal table.
    please, help in deleteing the filed MANDT from the internal able.
    following is the code which creates the dynamic internal table.
    CREATE DATA dy_table TYPE TABLE OF (p_tabname).
    assign dy_table->* to <dyn_table>.
    please provide, if any sample code is available.
    Regards,
    Xavier.P

    Hi,
    You can use this logic,
    While creating the Dynamic filed catalog try to avoid MANDT field.
    Ex:
    *Dynamic creation of a structure
      CREATE DATA LP_STRUCT TYPE (V_TABLE).
      ASSIGN LP_STRUCT->* TO <FS>.
    *Fields Structure
      OF_SDESCR ?= CL_ABAP_TYPEDESCR=>DESCRIBE_BY_DATA( <FS> ).
    LOOP AT OF_SDESCR->COMPONENTS ASSIGNING <COMPONENTS>.
    *Field MANDT not displayed
        IF SY-TABIX = 1 AND <COMPONENTS>-NAME = 'MANDT'.
          CONTINUE. " Next loop
        ENDIF.
    *Build Fieldcatalog
        LS_LVC_CAT-FIELDNAME = <COMPONENTS>-NAME.
        LS_LVC_CAT-REF_TABLE = V_TABLE.
        APPEND LS_LVC_CAT TO LT_LVC_CAT.
        CLEAR LS_LVC_CAT.
      ENDLOOP.

  • Create condition table for account determination

    I would like to create a condition table which contains customer number as the key. However, I can only find the follow fields in field catalog.
    Acct Key
    AcctAsgnmt
    AcctAssgGr
    Cond. Type
    Distr. Chl
    Division
    Ord. reason
    Plant
    Sales org.
    Tax Code
    Vendor
    Is it possible to extend the field catalog? I have tried to added fields in KOMG according to note 21040, but it seems not work.

    Hi
    some additional information:
    please check the documentation under customizing path:
    IMG -> Sales and Distribution -> System Modifications ->
    Create New Fields (Using Condition Technique) ->
    New Fields For Account Determination
    click on the icon
    Notice that the userexits USEREXIT_ACCOUNT_PREP_KOMKCV and
    USEREXIT_ACCOUNT_PREP_KOMPCV are useful only for revenue
    account determination.
    For reconciliation account determination you should use the userexit
    EXIT_SAPLV60B_011 (enhancement SDVFX011) to fill the custom field.
    The System modification documentation exaplins to add the new field
    in the structure include KOMKCZ of KOMPCZ.
    Notice that KOMKCZ is included in KOMKCV and KOMCV; KOMPCZ is included
    in KOMPCV and KOMCV.
    regards,
    Ramana

  • Create condition table V/57

    Hi all,
    I'm trying to create a new condition table for output determination and need it to be based on the Sales office, and the customer account group KTOKD.
    However, the field KTOKD is not available as an allowed field when creating the condition table. 
    Can anyone tell me if it is possible to add extra fields into the allowed fields list in V/57 so that I can include the customer account group?
    many thanks
    Phil

    Hi Shiva,
    thank you for responding so quickly.  We have added the field KTOKD into the structure and activated it as per the note.  However, when I modify the access sequence and add in the new condition table, I get the error VT510 "Select a document field for KTOKD". 
    The system is asking me to assign a document field to the newly added field, when I click on the "field catalogue" button at the bottom a list of fields is displayed and the Customer Account group is not an option.
    Thanks again for your help
    Regards
    Phil

  • Creating New condition table.

    Hi all,
    I want to create conndition table with new fields. I have added those Zfields to VBAP, KOMPAZ.
    Do i need to code anything in userexit_pricing _prepare_tkomp for populating the fields in list of allowed fields while creating while creating condition table?
    Thanks & regards,
    NarsiReddy.

    If any field to be considered for condition table, the same would be done via V/03 where you can add any fields that are missing from standard.  But once you save, system will ask for Access Key without which, it won't flow in condition table.  Hence, user exit is not necessary.  But it would be ideal if you explain the business process as to why you were looking for adding some new fields.  Hope, you are not reinventing the wheel.
    G. Lakshmipathi

  • Return item (RETPO) as a key field in condition table

    Hi,
    I would like to know how we can utilize return item indicator as one of the key fields in the PO pricing condition table.
    [Requirement]
    Condition record
    Use Retrun item as a key
    e.g.) Table A999: POrg | Vendor | Return item | condition rate
    #1: 1000 | M123456789 |blank | 3%
    PO pricing
    If the PO item is NOT marked as return, #1 should be applied to that item.
    If the PO item is marked as return, no condition record should be determined.
    [Question]
    Though I've configured as above, return item indicator seems to be ignored.
    When I tick the initial indicator in access sequence, the condition rate is always applied to the PO item for both with and without return item indicator.
    When I tick-off the initial indicator in access sequence, the condition rate is not applied to the PO item for both with and without return item indicator.
    Why does it happen?
    Is it possible to apply the condition record only to the PO without return item?
    I'd like to know how to make it effective in the condition table, RETPO=blank.
    As long as searched, I couldn't find any similar question.
    Your help would be much appliciated.
    Best Regards,
    Mari

    Hi Manosij,
    Thank you for your reply.
    I've already done as your instruction.
    However, the result is not what I'm expecting.
    I believe I'm right to creating the condition table.
    But I think something wrrong in access sequence...
    Though I do as your instruction, creating the condition record in MEK1 only for blank one, the record is applied to those with X when creating PO.
    If you have another clue on my question, it would be much appreciated.
    Best Regards,
    Mari

  • I am receiveing error while creating Z table: Entry in table TAORA missing

    Hi Experts,
    I am receiving "Entry in table TAORA missing" while creating Z table.
    Please help
    Edited by: N_niki on Jun 11, 2011 9:22 AM

    Hi
    1) Check for the DB System. The Table name in  "Entry in table TAORA missing", meant to save the "DATA CLASS of the ORACLE application"., OR
    2) check for the Data Class you Selected, on Creation of the Z Table, for which an Entry exists in the TAORA or the Available DATA CLASS in the TAORA Table to fix it.
    Regards
    Gopu

  • Entries missing for Condition tables in TADIR

    Hi,
    I have downloaded certain pricing condition tables from ECC (customizing download). They got generated successfully and were visible as 'Active' in SPRO and ABAP Dictionary (SE11).
    When I ran the customizing download again, all the tables had become 'Inactive' in SPRO>Customer Relationship Management>Basic Functions>Pricing>Define Settings for Pricing--> Create Condition Tables.
    But at the same time, these tables are appearing as 'Active' in SE11 and condition records are also flowing for them from ECC to CRM.
    Having checked the log in Transaction SLG1, there are visibly few errors stating 'Entry not found in TADIR' for some condition tables.
    Any pointers to identify the source/cause of this error or how to resolve the same?
    Thanks & Regards,
    Vartika

    Hi Vartika,
    The note 457711 will be helpful for you.
    Generally these errors on TADIR coversion will not cause any problems on your conditions download..These errors can be ignored.
    Please check for inconsistencies between R/3 ad CRM using the note 664815 and correct them. There are reports attached to it for 4 diferent cases.
    Thanks
    Abishek
    Edited by: Abishek Kumar Thiagarajan on Jun 11, 2009 8:58 AM

Maybe you are looking for