New Fields For Free Goods Determination

Basic Information for Modifications to Free Goods Determination

 The following communication structures are relevant for free goods determination:
 KOMK (Free goods determination - Communication header)
 KOMP (Free goods determination - Communication item)
 KOMG (Free goods determination - Permitted fields)
For technical reasons, communications structure KOMG is used to display the totals from KOMK and
KOMP. It contains all the fields that can be used for the material determination. If new fields are added to
KOMK or KOMP, they are automatically added to KOMG.
 New fields for free goods determination are added in the following INCLUDES:
 Header data in KOMKZ (INCLUDE in KOMK, KOMG)
 Item data in KOMPZ (INCLUDE in KOMP, KOMG)
 The routines for adding new fields in sales order processing can be found in Member MV45AFZ4. Use
the following user exits:
 USEREXIT_MOVE_FIELD_TO_KOMK (header fields)
 USEREXIT_MOVE_FIELD_TO_KOMP (item fields)
An example of a statement for adding new header fields to free goods determination could be:
FORM USEREXIT_MOVE_FIELD_TO_KOMK.
MOVE VBAK-FFELDXY TO KOMK-ZZFELDXY.
ENDFORM.

Add a field to a new condition table in Pricing (Condition Technique):-

I will explain you the process with below example...Please follow steps in below
sequence-

Try to add the filed from the field catalog. In case the required combination field is
not there, you can add the field through the following process to filed catalog and
create the condition table. It is most common that one or other time we need to use
this function while configuring multi tasking & complex Pricing Architecture.

Here I'm giving a simple guide to add fields to the Pricing Field Catalogues:

For example you want to use field PSTYV ('Sales document item category') that is
included in structure KOMP ('Pricing Communication Item') as a key for a condition
table.

When you create a condition table (Transaction V/03), however, the system does not
propose the field in the field catalog.

Condition access, field catalog, allowed fields, KOMG, KOMK, KOMP, KOMPAZ,
KOMKAZ, PSTYV are the other terms which we need to know about, to add Fields.
Reason and Prerequisites:
For technical reasons, field PSTYV was included in structure KOMP, however, not in
structure KOMG ('Allowed Fields for Condition Structures').

Proceed as follows:
1. Call up the ABAP Dictionary (Transaction SE11) and create data type ZZPSTYV.
Choose PSTYV as a domain.As a short text, you can use, for example, 'ZZ - sales
document item category' and as a field label, you can use the field labels of
PSTYV.Save, check and activate your entries.

2. Call up structure KOMPAZ in the ABAP Dictionary (Transaction SE11) in the

change mode and make the following entry:
Component Component type:
ZZPSTYV ZZPSTYV
Save, check and activate the change you made.

3. Note:Because of the change in structure KOMPAZ, field ZZPSTYV is now known

in structures KOMG and KOMP because structure KOMPAZ is included in both
structures.

4. Call up Transaction SPRO. Navigate to 'Sales and Distribution -> Basic Functions -
> Pricing -> Pricing Control' and execute 'Define Condition Tables'.
Choose 'Conditions: Allowed fields' and include ZZPSTYV as a new entry.

5. Note:Now you can use field ZZPSTYV as a key field when you create a condition
table Axxx.

6. Supply the new field you defined by including the following source code line in
USEREXIT_PRICING_PREPARE_TKOMP:
MOVE xxxx-PSTYV TO TKOMP-ZZPSTYV.
In order processing you find the user exit in Include MV45AFZZ, and in billing
document processing you find it in Include RV60AFZZ.

Consider that you can also use this note as a help if you want to use other customer-
specific fields as key fields in a condition table.

For header fields, use structure KOMKAZ instead of structure KOMPAZ and
USEREXIT_PRICING_PREPARE_TKOMK instead of
USEREXIT_PRICING_PREPARE_TKOMP.
For more information, see Transaction SPRO via the path 'Sales and Distribution ->
System Modifications -> Create New Fields (Using Condition Technique) -> New
Fields for Pricing' and OSS Note 21040. *-- Manoj Mahajan