R/3 Enterprise:
Three Steps to Ensure Parked Invoices Are Verified

  • by Sachidanand Padgaonkar, SAP Senior Consultant, Infosys Technologies, Ltd.
  • April 1, 2005
Events occurring in a purchasing cycle might require the system to perform tasks out of sequence. Invoices, for example, sometimes must be parked in the system while awaiting goods receipts. While this happened automatically in early versions of R/3, you must maintain the system to allow this functionality when upgrading to R/3 Enterprise. Here’s how.
Key Concept
R/3 Enterprise adds a transaction to provide an overview of invoices. MIR6 also allows you to maintain settings so that parked invoices can be marked for background verification in the system.
Your R/3 system processes the various steps in a purchasing cycle and accommodates any variations that may arise. A purchasing cycle usually starts with placing an order for raw materials based on the demand requirements of the finished goods. The raw material is valued at a moving average price, which is determined and set when the vendor actually supplies the material. As the cycle continues, a goods receipt is made against the purchase order, and the vendor books the liability by sending the invoice against the material dispatched.

It is not uncommon for vendors to submit an invoice before dispatching material. In these instances, the system "parks" the invoice and doesn't process it. After allowing for certain conditions required to receive the goods, such as the shipment transit time, the parked invoice is posted in the system. After posting, the invoice is matched with a goods receipt and verified, and the payment is sent to the vendor.

Prior to the release of R/3 Enterprise 4.7, the system processed invoice verifications based on goods receipts using program RMBABG00. The program automatically posts parked invoices once a goods receipt is generated via a background job set for RMBABG00 or by executing SE38 manually. In the R/3 Enterprise environment, however, the procedure has changed.

I will share with you the experiences I had as I helped a client upgrade from R/3 4.5B to Enterprise 4.7 and detail some of the issues we encountered processing parked invoices. I will explain how a key functionality has changed in the Enterprise upgrade and how process modifications must be made to accommodate the change.

Sachidanand Padgaonkar

Sachidanand Padgaonkar is an SAP Senior Consultant at Infosys Technologies Ltd. with 10 years of consulting experience executing the diverse modules of SAP Financials, Sales and Distribution, and Logistics, with a special focus on the SAP Retail industry solution. Sachidanand is currently a consultant in the SAP space for leading high-tech companies in the San Francisco Bay Area. He has a degree in electrical engineering and an MBA in finance. He has published many articles in international publications and was a speaker at ASUG 2006 in Orlando.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.