Procure-to-Pay (P2P)

A Purchase-to-Pay simulation event log.

Download the dataset here:

Short Description #

This process describes the Procure-To-Pay (P2P) procedure within an organization, starting from the initiation of a purchase requirement up to the execution of payment. This simulation extensively uses genuine SAP transactions and object types to offer a realistic representation of the P2P process.

Overview #

Within our simulated organization:

• Procurement Initiatives: The procurement journey begins when a department or individual recognizes a need and creates a Purchase Requisition using transaction ME51N.

• Approval Process: Before the purchase can proceed, the requisition must be approved. This is carried out using transaction ME54N. Given the nature of our simulation, there may be instances where the approval process takes an unusually long time, exemplifying the Lengthy Approval Process behavior.

• Vendor Interactions:

  • Upon approval, a Request for Quotation is sent out to potential vendors using transaction ME41.
  • Vendors then submit their quotations, which are maintained in the system using transaction ME47.

• Purchase Order Creation: Once a vendor’s quotation is selected, a Purchase Order is created using transaction ME21N. The purchase order is then subjected to an internal approval process (ME29N). Occasionally, maverick buying—where purchases are made without proper authorization—can be observed.

• Goods & Invoice Management:

  • When the goods are received, a Goods Receipt is recorded using transaction MIGO.
  • Invoices from vendors are then received and recorded. A three-way match, which checks the purchase order, goods receipt, and invoice for discrepancies, is performed using transaction MRBR.

• Payment: Once everything is verified, payments are executed using transaction F110. However, there may be instances of Duplicate Payments in our simulation, where the system mistakenly pays the same invoice more than once.

Special Behaviors: #

• Maverick Buying: Unauthorized purchases, bypassing the standard procedure.
• Duplicate Payments: An error leading to the same invoice being paid multiple times.
• Lengthy Approval Process: Delays in approving purchase requisitions or purchase orders, which might lead to operational inefficiencies.

General Properties #

An overview of log properties is given below.

Authors #

Gyunam Park and Leah Tacke genannt Unterberg

Contributing #

To contribute, drop us an email! We are happy to receive your feedback.