cancel
Showing results for 
Search instead for 
Did you mean: 

Pricing Determination by Material Group 1

Former Member
0 Kudos

Hi,

I have created a pricing condition table with field : RVE_MVGR1. MVGR1 is the Material group 1 field (Maintained in Materials master Sales view). This field is copied to the Additional data view of the sales order line item (Field : VBAP-MVGR1)

Pricing conditions have been maintained for the created table. However the sales order is unable to determine pricing. Pricing Analysis : Access not made (initialized field)

Any reason for this to happen. I know we can use User Exit for moving the document value to the pricing communication structure. Thats working fine.

However MVGR1 being a std SAP field, is there any reason for not determing the document value in the pricing communication structure without using user exit.

Appreciate a quick response.

Best regards,

Jr.SD

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

I suggest to check the field name for MG1....as it is RKE_MVGR1 not the one you have used.....Try to change and check....Anis

Former Member
0 Kudos

In field catalog, I can see only RKE_MVGR1 for Material Group 1.

Former Member
0 Kudos

I got this in this Brilliant Forum. May be it is helpful to you-

For adding field into Field catalog:

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.

Rgds

Sai

Answers (0)