cancel
Showing results for 
Search instead for 
Did you mean: 

Pricing - Adding new field to pricing catalog

Former Member
0 Kudos

Hi All,

I need to add a field to the pricing field catalog.

In Enterprise IMG

Menu: Sales and Distribution>Basic Function>Pricing>Pricing control->Define price dependencies (condition tables) ->Conditions: Allowed fields

A new field needs to be added to the field catalogue here:

Customer classification(KNA1-KUKLA).

When I am trying to create new entry, I am getting the following error:

'Field KUKLA does not exist in table KOMG, KOMK, or KOMP'.

How can I add this field to the pricing field catalog?

Thanks,

Kumar

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member

Hi Manoj,

Please check below info.

It is most common that one or other time we need to use this function while configuring multi tasking & complex Prcing Architecture.

Here Iam 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.

Thanks & Regards,

CLN

Former Member
0 Kudos

Hi CLN,

Thanks a lot. I was exactly looking for the solution you provided here. Thanks for your timely help.

Regards,

Kumar

Former Member
0 Kudos

Hi Manoj,

As the solution is helpful, request you to reward points.

Thanks & regards,

CLN

0 Kudos

Hello CLN,

its helpful and working for me.

Thanks a lot

BR

Smruti