SAP ME92F Monitor Order Confirmations
Efficient management of delivery commitments
Transaction ME92F in SAP is used to monitor order confirmations as part of the procurement process.
Why use SAP ME92F?
Monitoring order confirmations is a crucial step in supply chain management to ensure delivery commitments are met and procurement processes run smoothly. SAP ME92F provides a powerful solution for the efficient management and monitoring of order confirmations.
SAP ME92F enables companies to seamlessly integrate and monitor the entire process of order confirmations. Automating tasks minimizes manual errors and significantly improves visibility into supply chain management.
Path: ME92F – Purchase -> Order -> News -> Overw. Order back.
|Transaction code: ME92F
|Transaction Text: Monitor Order Confirmation
|Authorization object: M_BEST_EKO
What is the date logic for generating (ME92f) and sending AUFB confirmation reminder messages for orders?
In transaction ME92f, the reference date (reference date) is decisive for calculating when a message is to be generated as a reminder in the selection logic.
The logic for selecting the relevant transactions in transaction ME92f behaves differently depending on Customizing.
You can find essential settings in Customizing “Set Confirmation Control” for transaction OLME, for the view: V_T163L with transaction SM30, or for the view: VC_T163G with transaction SM34.
Order Confirmation Obligation – Confirmation Obligation and Confirmation Tax Key
You have the option of working either via the Confirmation Obligation indicator and/or via the Confirmation Control Key .
The confirmation control key is maintained in the purchasing value key .
Both the Confirmation Obligation indicator and the purchasing value key are maintained in the purchasing info record.
If you create a purchase order with reference to the contract, the confirmation control key from the contract is transferred to the purchase order.
Working with and without a confirmation control key
If you only work with the confirmation obligation and without a confirmation control key , a reminder will be sent if there is no order confirmation. Regardless of the date. The system simply checks whether the confirmation number is entered in the item in the Confirmations tab. If this number is not available, a reminder will be issued.
With confirmation control keys , the date calculation logics described below must be observed. If the sum of the quantity of all order confirmations is less than the ordered quantity, a reminder is generated.
Monitoring Time in Confirmation Control Key
This value is defined in Customizing “Set Confirmation Control”. It is maintained in the confirmation control key and is used as part of the date logic to calculate when an AB is to be dunned. It specifies in days when a confirmation for a purchase order item must be received.
Logic 1 – Order Date plus Monitoring Time
With this logic, there must be a schedule line in the purchase order whose creation date (order date) plus the monitoring time is earlier than the reference date (today).
If you set this parameter and the monitoring time is set to 10 days, then the confirmation must arrive 10 days after the order date. If there is no confirmation at this time, this order item appears in the evaluation for monitoring confirmations.
Formula: (Reference Date – Monitoring Time) greater than the order date of the schedule line or (Order date of the schedule line + Monitoring time) less than the reference date
ABAP: Function module ME_CHECK_PO_FOR_DUNNING_CONF … HDATUM = P_DATLO – T163G-WDVOR.
Example: 1/20/2025 (reference date) – 10 days (monitoring time) = 10.1. 2025 / if the order date is less than 10.1. 2025, the purchase order item is selected
Logic 2 – Delivery date minus monitoring time
If you set this parameter and the monitoring time is set to 10 days, then the confirmation must arrive 10 days before the delivery date. If there is no confirmation at this time, this order item appears in the evaluation for monitoring confirmations.
Formula: (Reference date + monitoring time) greater than the delivery date of the schedule line or (Schedule line delivery date – monitoring time) less than the reference date
ABAP: Function module ME_CHECK_PO_FOR_DUNNING_CONF … HDATUM = P_DATLO + T163G-WDVOR.
Example: 1/1/2025 (reference date) + 10 days (monitoring time) = 11.1. 2025 / if the delivery date is less than 11.1. 2025, the purchase order item is selected
Therefore, you should not change the reference date in transaction ME92F
SAP always recommends that you always use the current date in the reference date field of ME92f, as you are very likely to process the AUFB output with the current date as well.
Background – Logic in the print program differs
After you have been able to generate an AUFB output for the purchase order using the logic described above, it is not certain that you will be able to send this message to the supplier.
The SAP standard print program SAPFM06P contains the following logic: Depending on the “Monitoring Time” field mentioned above, the processing of AUFB can behave differently.
Order date plus monitoring time
then this means that there must be a schedule line in the order whose creation date is the day or earlier than today (the day on which you try to send the AUFB message) – monitoring days.
Delivery date minus monitoring time
then it means that there must be a schedule line with the quantity >0, whose delivery date is the day or earlier than today (the day you try to send the AUFB message) + monitoring days.
Contact us today to learn more about how SAP ME92F can help your organization proactively monitor order confirmations and ensure the smooth running of your procurement processes.