Adding field to field catalog

[Former Member]

Dear All,

We have requirement of adding new partner function Agent to Field catalog for Pricing so that we can create new condition tablecan anyone suggect Note number for the same.

[Former Member]

Hi Deepak

For adding field into Field catalogue:

I shall give an example. But you should first identify the field for Profit Center (Design ID) and then do as follows:

For example if 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.

Prerequisites:

For technical reasons, field PSTYV was included in structure KOMP, however, not in structure KOMG ('Allowed Fields for Condition Structures').

To solve the problem, 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 Note 21040.

For creating a condition Table:

1) There are almost all the regularly used Conditon Table predefined in the system from 001 to 500.

See what best you can use the Standard Tables to avoid further errors.

2) In case you should define the new condtion Table,

a) Goto TCode: V/03

b) Give a Table any number from 501-999

Press execute and reach to next screen.

c) Check up whether the field you are looking is already added in Field catalogue.

d) Double click on the fields you want to make a Table..one by one. Note that the sequence here is important in higher hierarchical to lower..

Eample : Sales Org, DC, Division, Customer and then Material etc..,

e) After selecting, click on the Techincal View buttin (redone) and reach to next screen.

7) Check which key should be in header and which key should be footer. Use check and uncheck functionalities there..

😎 Once you are through with all the above steps ..click on generate button.

Check the Table is generated or not.

You can check it at V/04 or V/05 or in SE11.

Reward if useful to u

[Former Member]

Hi Guys,

I have similar requirement where i wanted to add field Order channel(BSARK) in VBKD into the price catalog.. I performed follwoing steps..

1. Add the field in the KOMG structure - (u2018Allowed Fields for Condition Structuresu2019).

2. Add the field in the KOMK structure -(Communication Header for Pricing)

3. Add the field in the KOMP structure -(Pricing Communication Item)

Point 2 and 3 are done since order channel can be maintained in the header and line item

Also we need to write a following code in both the exisiitng exists

USEREXIT_PRICING_PREPARE_TKOMP( for item)

USEREXIT_PRICING_PREPARE_TKOMK (for header)

Code: MOVE VBKD-BSARK TO TKOMP-BSARK

MOVE VBKD-BSARK TO TKOMK-BSARK

Also i have created a neccesary condition tables with order channel and assigned to pricing conddition type access sequence.

Now when in create order, i maintain the order channel field then enter the line item, Pricing is picking up from the new access having order channel..

But when i enter the material , In this case pricing related to new access will not pickup.. This also fine

Then if i mainatin the order channel in header or line item , then go and click update pricing in the pricing tab, the condition record is not picking up.. If you go and check the analysis tab , the field order channel will be of warning message symbol( means no value)

I would like resolve this issue... Am i missing any thing here

Thanks and regards

Sriram

[Manoj_Mahajan78]

Deepak,

Below is an example...follow below procedure-

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.

Regds

MM

[former_member227476]

dear deepak

check it

When the field is not available in the field catalog we can include that field by going to

Conditions allowed field option – going to new entries and specify the field name Ex: KLABC

This is for customer classification.

If the field KLABC doest exist means

KOMK – communication header for pricing

KOMP – pricing communication item

KOMG – allowed fields for condition structure

[It is the combination of KOMP and KOMK] when the field is not available ABAPer has to include the field in any one of the structure.

Path: IMG  SD  System modifications  User exits  User exits for price determination.

Or

IMG  SD  System modifications  Create new fields using condition technique 

New fields for pricing

Use include for new fields in the dictionary, specify the data base table – KOMG

Click on display

Click on append structure – on menu bar

Click on new append structure (F6)

Specify the name of append structure Ex: ZKLABC and continue

Specify description ZKLABC

Enter component KLABC

Enter component type KLABC -- enter – save it

And click on activate icon

rewards pls

siva

[Former Member]

Hi

Use T-Code VOK0, goto environment> condition table> field catalog

or

T-Code: OV24

SPRO -> Sales and Distribution -> Basic Functions -> Pricing -> Pricing Control -> Define Condition tables -> Conditions: Allowed Fields -> New Entries and enter the field name you require.

[Former Member]

hi,

Yes u add by ading the field in communication structure.

regards,

Arunprasad

Message was edited by:

arun prasad

[Former Member]

Hi

As per the cllient requirement u can add new fields to the field to define the new conditio table

here the communication structure for the header is KOMK and the communicatin sructure for the Item is the KOMP

Path:Imgsales and distributionsytem modificationscreate new fields for condition techniquecreate new fields for pricinguse INCLUDE for new fields in the data dictionaryenter the data base table in which u want to add the field suppose

let say it is partner function and u have to enter in the vbpa

and click on the append structure and enter the append structure as ZAVBPA and click on the enter and also include the same in the pricing communication structure and the KOMK and KOMP and KOMG

then the field may reflect in the condition field catalogue

thanks

rewards if useful