Fields in sales order item level for pricing

[Former Member]

01.02.2011

Hi friends,

I have a requirement wherein i need at least 3 additional fields at the item level in the Sales Order for pricing determination i.e i want this field to be used in the condition table. Since these fields should have list of values also, I find the fields Material group1, material group2 and material group3 ideal ones. I wont be using this field in the material master but inputting some data in these fields through development at the sales order level. How can i get these fields in the catalog? Please suggest.

Regards,

Uday

[Former Member]

hi,

please check this link:

http://www.sap-basis-abap.com/sd/how-to-add-new-fields-to-field-catalog.htm

hope this clears your issue.

balajia

[murali127]

Hi Uday,

As you may aware about in field catelog there are standard sufficient fields available in field catelogs,

in this case better you can create the fields according to the requirements with the help of abaper we can link the same and this can be used for pricing determination.

Hope this may helps,

Thanks and Best regards,

Muralidharan S

[Former Member]

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.