SAP Blanket Purchase Order

Advertisement

SAP Blanket Purchase OrderAn SAP blanket purchase order is used for purchasing consumables or services from a vendor which can be repeatedly procured during a specific period of time. Consumables include office or shop items such as pens, stationery, nuts or screws and services like routine repair work and other maintenance. A limit is set on the blanket purchase order and multiple Invoices can be processed provided that the total of all the invoices does not exceed the overall limit. In this tutorial, as part of our free SAP MM training, we explore the creation of an SAP blanket purchase order.

SAP Blanket Purchase Order

The basic components of the SAP blanket purchase order process are as follows:

  1. Create Framework Purchase Order
  2. Create Invoice

We walk through these components in the following sections.

Advertisement

Create Framework Purchase Order

Create the SAP blanket purchase order via transaction code ME21N.

Header Section

In the header section of the purchase order, enter the following information for each blanket item for the selected vendor:

  1. Choose document type FO – Framework Order to categorize the order as a blanket purchase order. Every purchase order is assigned a document type to identify the purpose and functionality of the order.
  2. Enter the vendor master number in the Vendor field. For our example, we use vendor 9001 – Michaela Meier.
  3. Click the Additional Data tab in the header section and enter Validity Start and Validity End dates for the blanket purchase order. The validity dates provide the duration during which purchases can be made against the order. In our example, we set a one year validity period, starting on 09/26/2017 and ending on 09/26/2018.

Our example header data can be seen below:

Blanket Purchase Order Header Data
Blanket Purchase Order Header Data

Item Section

In the item section of the SAP blanket purchase order, enter the following details:

  1. Select account assignment category K – Cost center to denote that a cost center should be specified and that all invoices should be charged to that cost center. The account assignment category list may contain standard and customized categories.
  2. Choose item category B – Limit. The item category of a purchase order identifies which type of procurement is taking place and triggers certain features. Item category B, for example, defaults a PO quantity of 1. This item category also switches off the goods receipt requirement for the blanket PO.
  3. Enter text for the item.
  4. Specify the plant for the procurement. In our example, we use plant 9001 – Berlin Distribution.

Our example item data can be seen below:

Blanket Purchase Order Item Data
Blanket Purchase Order Item Data

Item Details

Click the Item Detail button to expand the section. Enter the following information:

  1. Click the Limits tab and enter the overall limit value. The total of all procurements for this purchase order during the validity period cannot exceed this value. Select the No limit tickbox if there should not be a maximum spend for the blanket order. In our example, we set a limit of 5000 EUR as can be seen below:
Blanket Purchase Order Limits Item Details
Blanket Purchase Order Limits Item Details
  1. Click the Account Assignment tab. Based on the account assignment indicator K specified in the item section, specify the cost center and G/L account that all invoices should post to. In our example below, we specified cost center 1000 and G/L account 400000.
Blanket Purchase Order Account Assignment Item Details
Blanket Purchase Order Account Assignment Item Details

Press Enter then Save . The purchase order will be saved as a framework order:

Blanket Purchase Order Created
Blanket Purchase Order Created

Create Invoice

Now that we have an SAP blanket purchase order, we can begin posting invoices straightaway. Remember that the item category B disables the goods receipt requirement. Post invoices referencing the PO number via transaction code MIRO.

Advertisement

Once invoices have been posted, the invoice receipts will appear on the Purchase Order History tab. In our example we have created three invoices which total 5000 EUR, as shown below:

Blanket Purchase Order History
Blanket Purchase Order History

Remember that our blanket purchase order limit was set to 5000 EUR. An attempt to create an additional invoice that exceeds the limit will result in the below error message:

Blanket Purchase Order Limit Error Message
Blanket Purchase Order Limit Error Message

Did you like this SAP MM tutorial? Have any questions or comments? We would love to hear your feedback in the comments section below. It’d be a big help for us, and hopefully it’s something we can address for you in improvement of our free SAP MM tutorials.

Navigation Links

Advertisement

Go to next lesson: SAP Source List

Go to previous lesson: SAP MMBE Stock Overview

Go to overview of the course: SAP MM Training

4 thoughts on “SAP Blanket Purchase Order”

    1. Blanket purchase orders are used for simplified procurement of consumable materials or services. This process has different auditing requirements compared to the traditional procurement process for stock materials.

      1. I realize that the auditing process would be different. Because SAP does not allow a GR on a Framework PO, I was looking for suggestions on how to explain that, how to “sell” the process in which the traditional 3-way match is no longer used, at least not technically. We are implementing ReadSoft and plan to use an “approval” workflow, and use the fact that the user approved it (which is recorded) in place of the traditional GR.

        1. You don’t need 3-way match if you procure things like consumables. They are relatively cheap and don’t even have individual material master records. If you don’t bother with creation of master records, then why should you use functionality like 3-way match?

Leave a Reply

Do you have a question and want it to be answered ASAP? Post it on our FORUM here --> SAP FORUM!

Your email address will not be published. Required fields are marked *