Konp table

[Former Member]

Hello friends,

What is the use of the following tables,

VBRK and KONP.

is there any difference between

KONP-KNUMH AND VBRK-KNUMV.

aNY HELP ON THIS WILL BE HELPFUL.

Shejal Shetty.

[Former Member]

VBRK table to store BILLING header details.

KONP-pricing conditions record header.

a billing document, can have a pricing record. if a billing document have a pricing record, then it will be stored in that KONP table.

vbrk-knumv is the condition record number for that billing document.

that condition record is stored in KONV and KONP as KNUMH field.

KONV-condition record header

KONP-condition record items.

Regards

srikanth

Message was edited by: Srikanth Kidambi

[Former Member]

hi Shejal,

VBRK - Billing Document: Header Data

KONP - Pricing Conditions of Item data..

Regards,

Santosh

[Former Member]

Thanks Srikanth and Santosh,

is there any difference between

KONP-KNUMH AND VBRK-KNUMV.

Shejal.

[Former Member]

They are the same. VBRK-KNUMV is your link into the condition tables (KONH, KONP). The same is true for VBAK-KNUMV and others.

[Former Member]

Thanks Michael,

Is there a way to figure the link between two tables.. For eg

In this case VBRK-KNUMV is the link into the condition tables (KONH, KONP).

Shejal Shetty.

[Former Member]

they both are same it is just for establishing a link between two tables ...

[Former Member]

hi,

while creating a BILLING document, if the line items have any condition records, then that no will be populated here. so this is storing as KNUMV as VBRK table.(as condition record number).

this CONDITION record have been maintained in KONP and KONH tables. these are the master tables to store condition records.

Normally first we create COndition records.master tables for them is KONP(items) and KONH(header)

while doing sales order,billing document etc.. if we have any pricing condition(already if maintained ) we use that condition record.

Hope you got some idea now.

regards

srikanth

Message was edited by: Srikanth Kidambi

[Former Member]

Hi

It's easy:

KNUMV is the key for the pricing of the bill (table KONV)

KNUMH is the number of condition record (table KONP)

So u can find out the value of a condition of a bill by KNUMV (from KONV) and the value of a condition of SD pricing by KNUMH (from KONP).

When a bill is beeing created the system calculates the value of a condition getting from KONP and stores it in KONV.

Max