VPRS value not flowing to COPA

[former_member195434]

Hi,

VPRS was flowing to COPA properly until a new condition type (ZVAF) was included and added to SD pricing procedure and assigned to KE4I. The value fields assigned to ZVAF and VPRS are different.

There is no dependency of ZVAF and VPRS in the pricing procedure.

Also, when ZVAF was created, the GL account was not made as cost element. So it was not flowing to COPA but at that time VPRS was flowing to COPA.

After the GL account for the condition type was created as cost element (category 12), it started to flow to COPA but now VPRS is not flowing.

Any reason why VPRS shoud not flow?

Thanks

[Former Member]

use user exit COPA0005

[former_member195434]

Hi,

We are debugging with the techincal team.

All the standard configurations are correct.

Is it possible to have an enhancement which prevents a value field to be populated if another value field is getting populated? If yes, can anyone guide me how to find it?

Regards

[eduardo_hinojosa]

Hi

See these notes as a checklist

SAP Note 33178 - INFO: +/- sign logic in CO-PA (SD/FI interface)

SAP Note 37114 - Incorrect setup/reversal of provisions

SAP Note 31601 - Follow-up posting bill. doc.: Reversals missing

SAP Note 74486 - INFO: Overview of consulting notes for CO-PA

I hope this helps you

Regards

Eduardo

[ajaycwa1981]

Hi

I am amazed to see this Q.. Not sure why it would happen

If VPRS condition has a VALUE in VF03 billing doc, it is assigned tin KE4I to a Val Field and it is marked as Statistical in SD Pricing proicedure, it should flow to COPA

Can you check these 3 things?

Br, Ajay M

[former_member195434]

Hi Ajay,

I double checked and all the 3 things are in place.

As i said it was flowing as long as the GL against ZVAF was not created as cost element. Now after the GL account is created as cost element VPRS does not flow.

I am amazed too.

Any other possibility?

[Former Member]

Hi,

Which cost element did you create for GL account? Only works this SD x CO-PA integration with cost element 11 or 12.

RK

[Former Member]

Hi Abhinav

The condition VPRS is standard and if it is configured in KE4I, the integration with CO-PA is mandatory.

Execute tcode KEAT for you Billing document and let us know more details about this SD vs CO-PA integration.

BR,

RK

[former_member195434]

Hi Rudi,

VPRS-COGS mapping is done in KE4I.

In KEAT the difference is visible but it does not explain the cause for the value not flowing.

What exactly should I look for in KEAT? Where can I find further details?

[Former Member]

Hi Abhinav

Check the condition type settings for ZVAF. I believe it has condition category S (Standard Costs) and this MAYBE creating inconsistencies and therefore VPRS is deactivated and ZVAF takes precedence.

Not sure but it maybe standard SAP behaviour to take only once COGS Values to COPA and therefore only ZVAF related valuations flow.

Do check / change and let us know the results. Secondly, is VPRS posted to FI.

Regards

Mustafa

[former_member195434]

Hi Mustafa,

Condition category in ZVAF is blank.

VPRS values is posted to FI at the time of PGI.

Still not able to figure why ZVAF is interrupting with VPRS flow.

[Former Member]

Hi Abhinav

Lets see it from different angle. Lets say ZVAF has no impact.

So what are the other changes introduced offlate.

Can year change (2013->2014) have an impact. Check from this perspective. Let us know if PGI is done in 2013 and Billing in 2014.

Check if standard cost estimate exists for the material for year 2014. It could be a case where prices / costs are redetermined at the time of billing / billing release to accounts and since on that date (posting date, billing date & Service rendered date) no standard cost estimates exists, it has taken zero as a value and therefore no FI & COPA posting. Though VF03 may show updated values in VPRS, however it is quite possible that during release, there was zero value.

Regards

Mustafa Sakerwala

[former_member195434]

Hi Mustafa,

Both the posting (successful and unsuccesful) was was made on the same day, once before creation of cost element, one after.

We are in the testing phase and we tried it several times with both PGI and billing date sa same we got the same result.

Regards

[Former Member]

Hi Abhinav

Few more pointers:

1) Have you by any chance created ZVAF with reference to VPRS or any cost condition types

2) Check the routines / user exists. It may result in inconsistencies if there are some mistaken dependencies created in the code

3) Create New Condition type and its other configurations from scratch and check SAP Behaviour. Is it same as with ZVAF

4) If still getting same issue, report this to SAP immediately by raising OSS Message

Regards

Mustafa Sakerwala