Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Records for Some Pricing Conditions Not Retrieved from common FM's

Former Member
0 Kudos

Hi Gurus,

I have a problem with Function Modules 'PRICING' and 'PRICING_BUILD_XKOMV'.

It seems that records for some pricing conditions (KSCHL) are not retrieved from that Function Module.

Why do you think this is happening?

Is there a workaround? All that I have are data that must be input to the Function Module (I_KOMK, I_KOMP). I dont have the Sales Document data (VBELN).

Thanks!

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Hi,

You said some pricing conditions are not being retrieved. Are they appearing as Initial values in the output table. That is for these particular KSCHL are there blank records in the output table.

Can you check in debug and let me know?

Regards

9 REPLIES 9

Former Member
0 Kudos

Hi,

You said some pricing conditions are not being retrieved. Are they appearing as Initial values in the output table. That is for these particular KSCHL are there blank records in the output table.

Can you check in debug and let me know?

Regards

0 Kudos

Hi,

Sorry for the confusion. Nope, its not that the pricing conditions are there but the records are blank, but that these pricing conditions really are not found in the output table (XKOMV). But when I tried to view the material in VA03 (I was given the test data by my functional contact), and the pricing condition and their correspoinding values (KBETR) can be found.

0 Kudos

Hi Joy,

Try this and let me know if it works.

1. Go to TCODE VOK0 - Conditions: Pricing in Customizing.

2. Click on menu Pricing procedure -> and select Pricing procedure.

3. Now determine your pricing procedure from VA03 ( Click on "Display doc header details" icon , under the Sales tab you will find your pricing procedure).

4. This pricing procedure will be in TCODE VOK0. Click on the pricing procedure and double click on "Controls". Here you will find a list of KSCHL.

5. Check if the disappeared KSCHL is present here. If not ask your Function consultant to create it. If present check if "Print ID for condition lines" (DRUKZ) is 'X'

Check this and let me know

Regards,

Rajvansh

0 Kudos

Hi Rajvansh,

Thanks so much for your help.

I can find the missing KSCHL in VOK0, and in VA03 as well. I cant find however the DRUKZ field in VOK0, I cant check if it's marked 'X'. Can you please tell me how to view that? Thanks again.

Regards,

Joyreen

0 Kudos

Hi Joy,

For a pricing procedure the following fields are displayed for me.

Step

Counter

Ctype

Description'

From

To

Manual (Check box)

Required (Check box)

Staticstics (Check box)

Print----


> DRUKZ should be X

SuTot

.......and few others

The field right after the 3 Checkbox is DRUKZ.

Regards

Rajvansh

Edited by: Rajvansh Ravi on Nov 13, 2008 10:23 AM

0 Kudos

Hi,

Have you tried with FMs;

RV_PRICE_PRINT_HEAD

RV_PRICE_PRINT_ITEM

Regards

Karthik D

0 Kudos

Hi Rajvansh,

The 'Print' field is not marked 'X', but the other pricing conditions that are showing up in the output table of the FM is not marked 'X' also. Maybe that isnt the cause of the problem...

Hi Karthik,

I've already tried that FM also, but I get a blank output table instead ...

I really appreciate your efforts in helping guys...

0 Kudos

Hi Joy,

Just wanted one clarification. In your first post you mentioned "I dont have the Sales Document data (VBELN)". But the pricing procedure that i mentioned in VOK0 is obtained from the header details of the sales document (field is VBAK-KALSM).

How are you searching this pricing procedure (VBAK-KALSM) in VOK0 without the sales document number. Make sure you are using the right pricing procedure. I think different sales document can have different pricing procedure.

Regards

Rajvansh

0 Kudos

Hi Raj/Karthik,

It seems that I already have answers to my question... A user exit to the the FM has been added, where a condition must be satisfied in order for the missing fields to be shown.

Thanks so much for your efforts and your help.

Regards,

Joyreen