Skip to Content
author's profile photo Former Member
Former Member

Create new field catalog within SD

Hi everyone,

I'm trying to create a new condition table with standard conditions (e.g. Departure country, Destination country) and a condition I can't seem to add onto the list of allowed fields (Indicator: Triangular deal within the EU ?).

The field name for this is XEGDR and sits on table VBAK.

Does anyone know how I can include this field onto my custom condition table please?

Thanks in advance.

John

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • Best Answer
    Posted on Oct 05, 2009 at 02:38 PM

    Hi John

    As you want to add the feild VBAK-XEGDR , Which is not there in the allowed fields then firstly go to VBAK table and add the feild XEGDR.Take the help of ABAP'er to add the feild in the VBAK table. After adding the feild in VBAK table, then you can add the feild with the key combination's you want to maintain.

    Regards

    Srinath

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Srinath

      Thanks for coming back to me.

      For clarification, are you suggesting I add field XEGDR to table VBAK? Only this field already exists in VBAK table via SE11.

      For more info, I'm trying to create a condition table via IMG>SD>Basic Functions>Pricing>Pricing control>Define Condition tables>Conditions: Allowed fields. However, I cannot find this field to use in my custom table.

      Any thoughts would be welcome.

      Thanks

      John

  • author's profile photo Former Member
    Former Member
    Posted on Oct 06, 2009 at 09:51 AM
    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 05, 2009 at 06:01 PM

    John, Here is the doc from SAP on enhancing pricing for new fields and examples: -

    New Fields for Pricing

    Basics of modification in pricing

    The following communication structures are relevant in pricing:

    KOMK (pricing communication header)

    KOMP (pricing communication item)

    KOMG (allowed fields for condition structures)

    For technical reasons, communication structure KOMG is used. It combines the fields from KOMK and KOMP that are relevant for pricing in the standard system and are offered in the field catalog of condition tables. If you want to use a new field in the field catalog, you must add the field to KOMP or KOMK in the following INCLUDES:

    header data in INCLUDE KOMKAZ in KOMK

    item data in INCLUDE KOMPAZ in KOMP

    When you use INCLUDES, the field is automatically added to KOMG and the field catalog.

    The routines for assigning values to the new fields in order processing are found in member MV45AFZZ. Use the following user exits:

    USEREXIT_PRICING_PREPARE_TKOMK (header fields)

    USEREXIT_PRICING_PREPARE_TKOMP (item fields)

    The routines for assigning values to the new fields in billing are found in member RV60AFZZ. Use the following user exits:

    USEREXIT_PRICING_PREPARE_TKOMK (header fields)

    USEREXIT_PRICING_PREPARE_TKOMP (item fields)

    Examples for using new fields in pricing

    Example 1

    In the first example, parts of a document field are to be used in pricing. You want to use the first three digits of the product hierarchy (PRODH) for pricing, for example. Proceed as follows:

    1. Check the data elements in the standard system.

    2. Since there is no such data element you have to create the new data element ZZPRODH1. Also create a domain with the length "3" and the data type "CHAR" for the new data element.

    Remember that new data fields must start with the letters "ZZ" or "YY", since SAP reserved these letters to protect them from being overwritten during a release upgrade.

    3. Check whether the product hierarchy (PRODH) is found at header or at item level.

    In table VBAP, document field PRODH is defined as an item field.

    4. Integrate the field name ZZPRODH in the communication structure KOMP using the INCLUDE KOMPAZ and allocate the data element PRODH to it.

    5. Activate the structure.

    6. Check in which table the field PRODH exists.

    The field is in table VBAP (sales document: item data).

    7. Assign a value to the new field in the FORM routines for sales order processing and billing using the appropriate user exits:

    In sales order processing the user exit is found in member MV45AFZZ. The complete statement is:

    FORM USEREXIT_PRICING_PREPARE_TKOMP.

    MOVE VBAP-PRODH(3) TO TKOMP-ZZPRODH.

    ENDFORM.

    The routines for assigning a value to the new fields in billing are found in member RV60AFZZ. The statement is as follows:

    FORM USEREXIT_PRICING_PREPARE_TKOMK

    MOVE XVBRP-PRODH(3) TO TKOMP-ZZPRODH.

    ENDFORM.

    8. Allocate the specifications A, V and 001 to the field ZZPRODH in table T681F. Use "E" has been added for fields in rebate processing.

    Example 2

    In the second example, you want to use a partner function, created in Customizing for partner maintenance, for pricing.

    Assume that the partner function was created for a sales representative of the partner type PE. Z1 is defined as a mandatory function for the customer master record, therefore automatically set in the document and available in the internal partner table XVBPA.

    To use the new partner function for pricing, proceed in the same way as for the previous examples.

    9. Create a new data element, in this example, data element ZZVRTZ1 with domain PERNR.

    10. Include the field ZZVRTZ in KOMK using KOMKAZ and allocate data element ZZVRTZ1 to it.

    For order processing, a value is assigned to the field in the user exit for member MV45AFZZ. The entries in the user exits are protected during a release upgrade. The statement is as follows:

    FORM USEREXIT_PRICING_PREPARE_TKOMK.

    PERFORM XVBPA_LESEN (SAPFV45K) USING 'Z1' VBAP-POSNR SY_TABIX.

    MOVE XVBPA-PERNR TO TKOMK-ZZVRTZ.

    ENDFORM.

    For billing, a value is assigned to the field in the user exit of member RV60AFZZ. The entries in the user exits are protected during a release upgrade. The statement is as follows:

    FORM USEREXIT_PRICING_PREPARE_TKOMK.

    PERFORM_XVBPA_SELECT_USING'Z1'.

    MOVE XVBPA-PERNR TO TKOMK_ZZVRTZ1.

    ENDFORM.

    Edited by: Matthew Menzies on Oct 5, 2009 8:03 PM

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.