GLT3 table is not updated when using IDocs for updating invoices

GLT3 table is not updated when using IDocs for updating invoices

We are using IDoc type FIDCCP02/Msg. Type FIDCC1 for posting Invoice (FB70) and Credit Memo(FB75) information into an SAP R/3 4.6C FI system. When manually creating the invoice using FB70 and FB75, the line item table and totals table (GLT3) are being updated with the Invoice amount for that period.

When posting the IDoc for that same period with the same information, the GLT3 table is not updated, even though the document is created and the line item table is updated.

What is triggering off the updating of the GLT3 table, that only occurs when manually posting the Invoice/Credit memo? This is not happening when an IDoc is submitted. Is there another IDoc that we can use that will update the GLT3 table as well? If not, do we need to add something to the user exit in order for this table to be updated when an IDoc is submitted?

    Requires Free Membership to View

    Login

    When you register, you will start receiving targeted emails from my award-winning team of editorial writers. Our goal is to keep you informed on the hottest topics and biggest challenges faced by SAP professionals today.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSAP.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSAP.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

Looks that you have a special constellation that causes the IDoc processor to behave differently. I suggest that you debug the process. Call WE19 to copy your IDoc, and process it by direct function call with debugging from there. Then you can watch in slow motion what is really happening behind the scenes.

This was first published in August 2005

Back to top