cancel
Showing results for 
Search instead for 
Did you mean: 

VA43 and VA42 billing plan values showing different values

Former Member
0 Kudos

Hi,

I have a strange issue received from my user, when checking in VA42 the values showing correct and the document number checked in display mode VA43 system showing different value than VA42, Please check the below document for ref.

VA43.

va42 showing the 17431.87 USD  only

thanks,

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Fyi,

VA42 screen shot of the same document. Please let me know if you need any more details?

Shiva_Ram
Active Contributor
0 Kudos

Check whether the OSS 565589 - Billing document values in periodic billing plan incorrect

covers your issue or not. This note is applicable upto version 4.7.

Regards,

Former Member
0 Kudos

Hi Shiva,

Thank you for your reply. fyi.  My current version of the system is EHP6 and the company code is USA.

Since i am not much aware of the Maintenance contract and Periodic billing, i could not understand much of the given note and at the same time also its talking about Argentina company code if understood correctly.

My doubts:

As you mentioned, this NOTE is applicable upto 4.7 version, is it advisable implementing the coding corrections mentioned in the NOTE for my current version EHP6?  if NOT what is the alternative?

i have replicated a fresh contact in Pre quality system, showing both VA42 and Va43 same values

And for your information: the same production document is refreshed into Pre quality system there the same document showing the same as Production values. Where as like i mentioned above when created a fresh VA41 system showing same values in VA42 and VA43.

thanks,

Shiva_Ram
Active Contributor
0 Kudos

No this note is not applicable to your version, since your version is higher, the corrections should have been already covered.

From your response, last paragraph, the new documents created does not show this issue. I recommend testing in your test system for few more times and if it is not happening again, then you can consider this as one-off scenario. I could not find any other OSS note for this issue. You can raise the issue to SAP support and see what their response would be.

Until they respond back, you can ask ABAP resource to check in debugg mode for that field value. Probably they may bring a clue on the issue. Does any user exit get activated at billing plan level?

Regards,

Former Member
0 Kudos

thanks you Shiva for your reply.

My colleague has done some R&D and after checking the blow mentioned filed system automatically corrected the 3rd billing plan value.

.

thanks,