cancel
Showing results for 
Search instead for 
Did you mean: 

Statistical Pricing Issue

Former Member
0 Kudos

Hi guys,

I'm currently receiving a frustrating pricing issue. Hoping you may be able to help me.

I've created order type L2DM from TAF. The pricing conditions come through as expected. Then when I create an F2 type billing document condition types PR00 and EK01 are flagged as statistical.

I'm using pricing procedure: RVAA01 and there is no statistical flag set against PR00 & EK01. In analysis both L2DM & F2 are using this pricing procedure.

Any ideas where else this flag could be getting set?

<b>Point awarded for helpful answers as always.</b>

Many Thanks,

Philip Johannesen

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

I have thinking on this issue for a while now.

Is there any user exit coming into picture or any Z routine attached in copy control ?

In standard this should not happen.

Just check if the following exits are used in any way.

USEREXIT_CHANGE_PRICING_RULE (module pool SAPMV61A, program MV61AFZA)

You can use this user exit to change the pricing type that has been predefined in the copying control table in billing.

USEREXIT_XKOMV_BEWERTEN_INIT (module pool SAPLV61A, program RV61AFZB)

This field is used in the formulas and therefore initialized before the loop for the pricing procedure starts.

USEREXIT_XKOMV_BEWERTEN_END (module pool SAPLV61A, program RV61AFZB)

Within a loop for the price components during pricing, specific values can be transferred into the communication structures in pricing to be further processed.

USEREXIT_XKOMV_ERGAENZEN (module pool SAPLV61A, program RV61AFZB)

In change mode, you can change the dynamic part of the condition record (KONVD) that is always redetermined (i.e. it is not stored in database table KONV).

USEREXIT_XKOMV_FUELLEN (module pool SAPLV61A, program RV61AFZB)

This user exit is always called up during a redetermination of all or individual price components. You can change the work fields of the condition line. However, this only applies to conditions that have been determined via a condition record.

USEREXIT_XKOMV_FUELLEN_O_KONP (module pool SAPLV61A, program RV61AFZB)

This user exit is always called up during a redetermination of all or individual price components. You can change the work fields of the condition line. However, this only applies to conditions that have been determined via a condition record. This may include subtotals, manually entered conditions or conditions that have been calculated with a formula.

USEREXIT_PRICING_COPY (module pool SAPLV61A, program RV61AFZA)

You can change the KONV fields for copied price components.

Reward points if useful

Regards,

Amrish Purohit

Former Member
0 Kudos

Hi Amrish,

Thank you for your feedback. I've checked copy control and it's not using any bespoke routines. I've also checked for any active user exits with no luck.

It is very strange I can't why these would come through as statistical values. The only place I know of where you can flag this option is against the pricing procedure. I can't think of anywhere else in config that could flag these condition types to statistical. Especially when all I'm doing is copying the pricing conditions unchanged from the debit memo request.

Many Thanks,

Philip Johannesen

Former Member
0 Kudos

I've had a closer look at <b>PR00 & EK01</b>. I've noticed the following changes to the condition types between <b>L2DM and F2.</b>

<b>In L2DM:

EK01:

Condition Control = C (Changed Manually)

PR00:

Condition Control = A (Adjust for quantity variance)

In F2:

EK01:

Condition Control = E (Condition Value and basis fixed)

PR00:

Condition Control = E (Condition Value and basis fixed)</b>

Do you know where in config this is set-up? I think it may be that because Condition Control is being set to E perhaps it is making the condtion types statistical?

Thanks,

Philip Johannesen

Former Member
0 Kudos

Hi,

This is really a good issue to work with.

Actually i am also not sure how this indicator is being set to the condition type.I assume that you have noticed this change from KONV table for the respective condition type.

In documentation for this field nothing substancial has been given:

Condition control

Indicates whether the prices or values in a condition are fixed or whether they have been changed and, if so, in what way.

Example

The indicator shows, for example, if the prices generated by a condition have been changed manually during processing.

This does not make any sence,when you are just performing copy the data from order to billing.

This has definetly something to do with Pricing type.As you are using G as you said in your earlier thread,just try on DEV server by vhanging this field to say

D (Copy pricing elements unchanged) and let us see what happens.

Else I think you need to dubugg the program.so that will give you a better idea how and why this Statistical indiactor is being set to condition type.

Do revert with observations

Regards,

Amrish Purohit

Former Member
0 Kudos

Hi Amrish,

I managed to figure it out in the end. IS-OIL had been previously implemented in the system. In debug mode the billing engine goes into various IS-OIL related includes. In one of these includes: <b>OI_LV61AFOI_OIA_SPLIT INVOICIN</b> on line 55 the following piece of code was setting the statistical flag <b>KSTAT to 'X'</b>:


* For pro-forma invoice no change to statistical conditions
    IF KOMK-VBTYP NE 'U'.                               "SOGK041278 MMW
      XKOMV-KSTAT = 'X'. XKOMV-OIINCYST = 'X'.

The flag is set if the <b>invoice cycle is blank</b>. I then looked at my item pricing condition details in the billing document and noticed there was an invoice cycle drop down box with no values.

I went to SPRO -><b> Industry Solution Oil & Gas (Downstream) -> EXG (Exchanges) -> Split Invoicing -> Maintain Invoicing Cycle Numbers</b>. Added a new entry.

Then I created a new Sales Order and set the invoice cycle to 1 for PR00 at the item conditions level. Then when I billed it PR00 was no longer statistical and the costs came through.

Thanks again for your help, I've awarded points as promised.

Regards,

Philip Johannesen

Former Member
0 Kudos

Hi Phillip,

Thanks for updating.

Congradulation for cracking the issue.It was a really a brain crashing issue

Cheers

Regards,

Amrish Purohit

Answers (1)

Answers (1)

Former Member
0 Kudos

HI,

i am working on this issue but pls provide some more info.

1. why u are maintaining pricing as stastical purpose

2. whay type of material it is?

3. what is sales process?

4. what type of error you are getting ?

pls provide me these asap.

i will respond u

Regards

Hari Shankar

Former Member
0 Kudos

Hi Hari,

1. Condition types PR00 & EK01 are coming through as statistical when the billing document F2 is generated. I do not want them to come through as statistical. On the previous Sales Document L2DM these condition types are not statistical. Do you know why these pricing conditons are being flagged as statistical?

2. The Item category used is TAD (Service) derived from TAF(Configurable Service)

3. I'm using resource related billing to generate the billing request. A PO is created and assigned to a WBS. This WBS is then attached to the Sales Order. Then I use Tx: DP91 to generate the Debit Memo Request (L2DM). This all works perfectly. It's just the billing phase that is causing the pricing issue.

4. I just want to copy the pricing conditions unchanged from L2DM to F2, but for some reason PR00 & EK01 are coming through as statistical. Therefore no costs are coming through to the billing document. I've set the Pricing Type for TAD to G in copy control.

Any help would be greatly appreciated.

Many Thanks,

Philip Johannesen