Output message type AUFB Dunning Order Confirmation

Skip to end of metadata

 Created by NADIA ORLANDI, last modified by Diana Dai on Dec 07, 2015
Go to start of metadata
Purpose
The purpose of this wiki is to clarify the system behavior in relation to Message Output type AUFB.

Overview
This document shows prerequisites for output message type AUFB and explains in which cases it is possible to send an order confirmation to the vendor.

Prerequisites
In case we create an our own message type by copying it from message type AUFB, in Customizing we have to
 Set the “Indicator: Print operation” to 7 for the message type in OLME> Messages> Output Control > Messages Types > define Messages Type for

PO > Fine-Tuned Control: Purchase Order.

 Insert the program, form routine, form in Maintain Message Types for PO > Processing Routines (Standard: Program SAPFM06P, Form Routine

ENTRY_AUFB, Form MEDRUCK).

 Insert the message type in the Procedure RMBEF1 in transaction M/36.

Output message type AUFB is generated if

 A condition record for message type AUFB is created in MN04.

 In PO TAB Confirmation a confirmation control key is maintained and the flag ”Order Acknowledgment requirement” is set on.

 The PO is printed (Output message type NEU is used here).

Dunning order confirmation

If the vendor doesn’t send an order confirmation within a date, it is possible to send a reminder to him using the message type AUFB.

Working with Confirmation control key

In this example we work with the confirmation control key 0001 and Reference date 2. Confirmation control key is defined in Customizing transaction OLME >

Confirmations > Set Up Confirmation Control.

The field “Monitoring period for vendor confirmation” is the number of days and the field “Reference date” takes the value 1 or 2. If the field Reference date is 1

(PO date plus monitoring time) the system computes the following operation “PO date + 10 days”, it means that the vendor has to send me a confirmation within

the date X= PO date + 10 days. If the field Reference date is 2 (Delivery date minus monitoring time) the system computes the following operation “Delivery date in

PO - 10 days”, it means that the vendor has to send me a confirmation within the date X= Delivery date in PO - 10 days.

Steps to be followed:

1. We create a PO with delivery date 10.10.2012 and confirmation control key

0001.
A reminder can be generated, if the vendor doesn’t send a confirmation within the 30.09.2012 (= 10.10.2012 – 10 days).
2. The PO is printed via ME9F and output message type NEU is successfully

processed.

3. In order to see the reminder’ list that could be generated, we run transaction ME2A. If we run ME2A before the 30.09.2012 system doesn’t find reminders and

error message ME260 comes up. If we run ME2A after 30.09.2012, for example on 01.10.2012, we get the following

information:
It means that we can generate a reminder i.e. an output message AUFB. Remark: With ME2A it is possible to see a list of reminders, it is not possible to create

reminders.

4. In order to generate the message AUFB we run transaction ME92F.

We click on push button Generate Messages and we

save.
Via push button Messages, system jumps in the message screen on the PO

header.

5.Now it is possible to send the reminder AUFB to the vendor via ME9F.
6. Print preview for the message type NEU appears as

Print preview for the message type AUFB