KOMP, KOMK, and KOMG relevance in pricing

[Former Member]

Can some one tell me what is the importance of the tables KOMG, KOMK or KOMP with reference to SD Pricing .

And how can i add a new field to field catalog?

Will reward points..Thanks in advance

Arpita

[Former Member · Accepted solution]

Hi,

KOMG is nothing but combination of KOMK and KOMP.These are the tables that provide the details to the header and item data in pricing.

These are generally called as KOMX because they act as a bridge to communicate the transaction data with the pricing procedure.

To create a new field,

IMG - S & D - System Modification - create new fields - new fields for pricing.

You have to have some abap knowledge so that the field reflects in the required table. If u want to include the field in the header, u have to use include table KOMKAZ in KOMK else KOMPAZ in KOMP for Item table.

HOPE this adds information

Mohan

Award points if it adds information.

[Former Member]

Hi,

The field catalog is a structure KOMG that consists of two tables KOMK and KOMP. These tables contain the header and item data for the pricing. They are called KOM'x' coz they are communication structures used to communicate the transaction data with the pricing proc. Table KOMG contains the fields of tables KOMK and KOMP.

If you require a field that is not in KOMG, it means that it is nnot in KOMK or KOMP. This means that the field you require cannot be used in the pricing coz there is no communication of this field frm the transaction to the pric. proc viat the communication structures.

To use a field not defined in the field catalog, you need to add this field to the KOMK or KOMP structures and then write abap code to transfer the data in field from the transactiontables to the communication structures.

Create the field in KOMK and KOMP tables using the standard includes provied for this requirement.

write the code in the user exit to read the tranasction data and trasfer it to the KOM'x' structures.

USEREXIT_PRICING_PREPARE_TKOMP In MV45AFZZ.

Hope it helps. Please reward if useful.

Thanks & Regards

Sadhu Kishore

[Former Member]

Hi,

KOMP, KOMK and KOMG are structure not table. They holds the pricing information while document is being created / changed. But <b>KONV</b> is the <b>table</b> for pricing related information. For reading KONV take the condition record number for any document at header level. for example,

VBAK-KNUMV ( sales documents condition record number )

VBRK-KNUMV (billing doc cond. record number )

EKKO-KNUMV ( PO condition record number ) etc..

KNUMV is first key field in table KONV. Take the number from any of the table given above and find the condition records from table KONV.

To use new field for pricing go to SPRO and go to path <b>Sales and Distribution --> System modification --> Create new fields (using condition technique) --> New field for pricing</b>. If you select this path it will just take you to SE11. But to understand how to create a new field, refer to the documentation of last node ( <b>New field for pricing</b> ).

To use this field, you will have to implement a user-exit for this. To do that go to SPRO and go to path <b>Sales and Distribution --> System modification --> User Exits --> User Exits for Pricing Determination</b>. If you select this path it will just take you to SE38. But to understand how to create a new field, refer to the documentation of last node ( <b>User Exits for Pricing Determination</b> ).

Feel free to ask if you need further information.

Regards,

RS

[Former Member]

just to add to the above update when we assign field while we define a Access sequence the data is stored in a Internal table, KOMK,KOMP etc are some of those tables.

Hope this helps.

Regards

[Former Member]

HI;

These are not tables but structures.

Regards.