Pricing feild catalog

[Former Member]

Hi all,

In feild catalog for pricing suppose you want to add new field from field catalog to allowed feild, lets take example of plant (WERKS). when you goto feild catalog to select and add the feild, it will come in three tables KOMG(Maintenance), KOMK ( Determination header) and KOMP( Determination item).

Please explain the relevance of same what the three tables means

[Former Member · Accepted solution]

Hi Komal,

Please find the below and probably you are looking for the same information as per my understanding.This helps you to understand how the pricing fields behave in the sales order.

During the condition table creation required fields can be selected. Only the fields present in the field catalogue are available for selection in the condition table. Fields present in the KOMG table can be added to the field catalogue. By default SAP does not add all the fields of KOMG to field catalogue. KOMG table is a union of KOMP, KOMK tables. KOMK table contains the header information of the document (Sales order or Billing), KOMP contains item level information of the document (Sales order / Billing). New fields can be added to the KOMP, KOMK structures. To add the new fields to these structures, an append structure should not be created. To add a field to KOMP structure, field should be added to KOMPAZ structure, which is an include in KOMP structure. Similarly fields should be added to KOMKAZ structure.

If it is required to create a condition table with a custom field the following steps should be followed.

Add the field in KOMKAZ or KOMPAZ structure. If the field is at the header level, add the field to KOMKAZ, and if the field is at the item level add to KOMPAZ structure. This step should be done SE11 transaction.

Activate the structure.

Add the new field to field catalog.

Create the condition table.

Adding the field to field catalog and condition table creation can be done VOK0 transaction.

At run time the custom field should be filled with the appropriate value. To to this the following user exits should be used.

USEREXIT_PRICING_PREPARE_TKOMK in RV60AFZZ .

USEREXIT_PRICING_PREPARE_TKOMP in RV60AFZZ.

(In order processing you find the user exit in Include MV45AFZZ, and in billing document processing you find it in Include RV60AFZZ)

Please let me know your thoughts.

Thanks and Regards,

Satheesh Durgi

[Former Member]

Hi,

VBAK and VBAP are the header and item for Sale order transactions.

KOMG is a field catalogue structure containing tables KOMK(Header Pricing Data ) and KOMP(Item Pricing Data ).

The Pricing Procedure is linked to the Transaction data through these tables KOMK and KOMP.Hence these tables are called communication Structures. used to communicate transaction data with Pricing Procedure.

Hope you got the Point.