SAP S/4 system
Purchasing
NAST vs BRF+ Message Output
S/4HANA Purchasing
S/4HANA Purchasing
The common purpose of the SAP transaction codes ME9F and ME9FF is the mass processing and transmission of Purchase Order (PO) outputs to vendors, which includes printing, emailing, or sending them via EDI.
ME9F
ME9FF
The common purpose of the SAP transaction codes ME9F and ME9FF is the mass processing and transmission of Purchase Order (PO) outputs to vendors, which includes printing, emailing, or sending them via EDI.
ME9F
ME9FF
The common purpose of the SAP transaction codes ME9F and ME9FF is the mass processing and transmission of Purchase Order (PO) outputs to vendors, which includes printing, emailing, or sending them via EDI.
ME9F
ME9FF
S/4HANA Purchasing
S/4HANA Purchasing
The common purpose of both ME91F and ME91FF in SAP is to generate and send dunning letters, reminders, and urging messages (expediters) to vendors for overdue Purchase Orders (POs) or upcoming delivery deadlines.
ME91F
ME91FF
The common purpose of both ME91F and ME91FF in SAP is to generate and send dunning letters, reminders, and urging messages (expediters) to vendors for overdue Purchase Orders (POs) or upcoming delivery deadlines.
ME91F
ME9FF
The common purpose of both ME91F and ME91FF in SAP is to generate and send dunning letters, reminders, and urging messages (expediters) to vendors for overdue Purchase Orders (POs) or upcoming delivery deadlines.
ME91F
ME9FF
S/4HANA Purchasing
S/4HANA Purchasing
ME92F and ME92FF are both SAP transactions used to monitor order acknowledgments and send dunning reminders to vendors.
The primary difference is their user interface and technology:
ME92F
ME92FF
ME92F and ME92FF are both SAP transactions used to monitor order acknowledgments and send dunning reminders to vendors.
The primary difference is their user interface and technology:
ME92F
ME92FF
ME92F and ME92FF are both SAP transactions used to monitor order acknowledgments and send dunning reminders to vendors.
The primary difference is their user interface and technology:
ME92F
ME92FF
S/4HANA Purchasing
S/4HANA Purchasing
Activating BRF+ for ME9FF, ME91FF & ME92FF are done via this configuration in the Cross-Application Component in IMG
Activation on this Application Object Type means
for the Purchase Orders
S/4HANA Purchasing
S/4HANA Purchasing
S/4HANA Purchasing
S/4HANA Purchasing
Business Rules configuration for BRF+
S/4HANA Purchasing
S/4HANA Purchasing
S/4HANA Purchasing
S/4HANA Purchasing
Form Template for
Form Template for
Form Template for
Form Template for
S/4HANA Purchasing
S/4HANA Purchasing
Reminder 2 days before the deadline
Reminder 1 day after the deadline
Reminder 3 days after the deadline
S/4HANA Purchasing
S/4HANA Purchasing
ME92 (NAST) or ME92F (BRF+)
ME91 (NAST) or ME91F (BRF+)
BRF+ don’t show to-print-message outputs
S/4HANA Purchasing
S/4HANA Purchasing
Message Output via ME9F (Method NAST) for Print PO
Message Output via ME9F (Method NAST) for Print PO
is no longer possible
using Fiori App ME9FF or backend t-code ME9FF is the same
using Fiori App ME9FF or backend t-code ME9FF is the same
S/4HANA Purchasing
S/4HANA Purchasing
Message Output via ME91F (Method NAST) for Dunning or Reminder of Late Delivery
Message Output via ME91F (Method NAST) for Dunning or Reminder of Late Delivery
is no longer possible
Message Output via ME91FF (Method BRF+)
for Dunning or Reminder of Late Delivery
can use this FIORI App or the backend t-code
Message Output via ME91FF (Method BRF+)
for Dunning or Reminder of Late Delivery
can use this FIORI App or the backend t-code
S/4HANA Purchasing
S/4HANA Purchasing
Message Output via ME92F (Method NAST) for Missing Order Acknowledgement
Message Output via ME92F (Method NAST) for Missing Order Acknowledgement
is no longer possible
Message Output via ME92FF (Method BRF+)
for missing Order Acknowledgement
can use this FIORI App or the backend t-code
List Untransmitted Message, and in next screen then Generate
Note Message Status