Billing Generation Issue
Billing Generation Issue
Billing Generation Issue
Communication
02.07.2018 11:55:58 INDIA - Problem Description: module vc (S0010682154)
Dear Team,
Please check accounting document number - 8318054258/2018 for which we are unable to find the billing
document in our production environment SP6 720.
Please treat it as serious matter since it is consuming our tax invoice number series but not generating the
billing document. Also user won't be able to take print of tax invoice since billing is not generated.
Kindly provide the root cause for the said behavior by going through the ABAP code.
Note - This is a random behavior and we can't generate test data or steps to reproduce the same.
Regards,
Prakash Chaliyawala
Mo - 9879105503
Please treat it as serious matter since it is consuming our tax invoice number series but not generating the
billing document. Also user won't be able to take print of tax invoice since billing is not generated.
Step 1: This is a random behavior and we can't generate test data or steps to reproduce the same.
Step 2:
Step 3:
The possible reasons for such gap in the billing document numbers are listed in the following note:
In FB03 you can see that the accounting document was created on 06.05.2018.
For that date I checked SM13 and ST22 transactions but could not find any update terminations or dumps
which could be responsible for the missing
billing document 2172519294.
However, in the SD-FI interface userexit EXIT_SAPLV60B_001 (Include ZXVVFU01) I saw that a "message"
statement is programmed.
Such action should be avoided as it can cause inconsistencies in your system like existing Fi document
without corresponding SD-billing document.
Such message statements should be avoided in userexits as they break tha standard process & program
logic.
Best regards,
Csaba Soltesz
SAP Product Support
Dear Soltesz,
I have gone through your response. Based on that i have done further investigation for the message "
I062(ZSD_MSG)". During the analysis i have found that the said message will trigger only if i am performing
transaction code - VF11 and my billing date < 01.07.2017 which is not a case for the given accounting
document.
Request you to reinitiate further investigation and let us know actual root cause.
Regards,
Prakash Chaliyawala
Mo - 9879105503
In order to find the root cause it would be necessary to replicate the situation.
Since no dump or update termination is available, it is not possible to find the root cause retrospectively.
I can not tell you what have happened in May without evidences.
I suggest to you to reverse the FI document. Please contact your local SAP consultant for that.
Best regards,
Csaba Soltesz
SAP Product Support
Contacts
Secondary
Role Name Time Zone Primary Phone E-Mail
Phone
module vc jitendra.kapadia
Reporter UTC +91-9879101637
(S0010682154) @essar.com
Attachments
module vc 02.07.2018
VF01 issue.docx VF01 issue DOCX 177.9 KB
(S0010682154) 11:55:58 INDIA
KBA/SAP Notes
Action Log
0020751294
module vc
11:55:58 INDIA Incident created 0000338400
(S0010682154)
2018
module vc
11:55:58 INDIA Priority changed Medium High
(S0010682154)
module vc
11:55:58 INDIA Status Not Sent to SAP Sent to SAP
(S0010682154)
SAP Note
14:58:35 INDIA SAP 1579523
add./rem.
Memo/Text
14:58:35 INDIA SAP Reply
changed
module vc
16:24:06 INDIA Status Customer Action Sent to SAP
(S0010682154)
module vc Memo/Text
16:24:06 INDIA Info for SAP
(S0010682154) changed
Memo/Text
19:25:00 INDIA SAP Reply
changed