on 03-25-2015 3:30 PM
Hello all, we occasionally have an issue where an accounting document is created but the related billing document "disappears". I found OSS note 1579523 that looks like it resolves this issue.
Instruction says to check user exits from note 301077. But it doesn't say what to do after that.
Has anyone applied this note? Can you provide insight as to what we need to do once we review the user exists?
Many thanks,
Cheryl
I cannot seem to attach screenshots. If you provide your email I can send to you.
An accounting document was created but the billing document did not get created. According to the OSS note, this is due to a misplaced commit.
The question I have is: Has anyone come across this, and if so, how did you resolve?
Regards,
Cheryl
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Cheryl,
It will be helpful if you can provide screen-shot of any example (flow). That will be helpful to analyze it further.
Regards,
Gaurav
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Gaurav, I'm not sure what you need a flow/example of.
Sales order > PGI > Billing Document > Accounting Document
When you go to display the billing document, it is not there.
The accounting document can't be cancelled because it thinks there is a billing document.
The OSS note referenced says it is tied to an improperly placed Commit.
We have found no such commit in any of the referenced exits.
OSS note does not state what to do if you find a commit.
Was wondering if anyone applied this note. If so, what did they do to fix the improperly placed commit. Or, where else can we look since we did not find any of the user exits active.
Regards,
Cheryl
When you go to display the billing document, it is not there.
This is not a standard functionality of SAP. For information, even if you cancel a billing document, and if you check the document flow for the corresponding sale order or original billing document, system would show the original billing document and also the cancelled document reference. So check the document flow for the corresponding sale order or billing document via VA03 or VF03.
G. Lakshmipathi
Doc flow - note that they created a second invoice (in doc flow) because they didn't see a billing document. This second invoice did post to accounting fine.
Accounting document NOT in doc flow. Note that the sales order is assigned in the line item.
Billing document does not exist. We use same document number for billing and accounting documents.
Also note that I cannot cancel the accounting document because it thinks there is a billing document. I cannot recreate this situation. It is random with no logical reason. That is why we want to apply the OSS note. This has NOTHING to do with our processes, our documents, etc. According to the OSS note, it is an incorrectly placed COMMIT statement. But we have checked all the recommendations in the OSS note and cannot find an active commit statement to cause this. Basically, we can't find anything to fix.
User | Count |
---|---|
95 | |
11 | |
11 | |
6 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.