Vous êtes sur la page 1sur 9

Procurement with Manufacturer

Part Number and Approved

Manufacturer Parts List (AMPL)
SAP Best Practices Healthcare (U.S.)

SAP Best Practices

Scenario Overview 1

Purpose and Benefits

Why Use MPN Functionality?
For many commodity-type materials, maintaining and tracking data at the Supplier
level (with a Supplier Part Number, price, etc.) is sufficient. However, there also
are many materials (blood products, pharmaceuticals, implants, prostheses, etc.)
where it is the Manufacturer data, not Supplier data, that is most important.
If the Supplier is the Manufacturer, then the standard Vendor Master functionality
is sufficient; However, where the Supplier is a distributor who may handle
multiple Manufacturers versions of a part, then the standard Vendor Master
approach isnt sufficient, and MPN functionality is required.
Manufacturer Part Number functionality enables the use of Manufacturer Part
Number and Manufacturer information in Supply Chain Management processes,
thus extending Materials Management functional data beyond merely the
supplier/distributor level.
Furthermore, even though a Supplier may list multiple Manufacturers versions
of a part under a single Vendor Part Number, pricing and other differences
may exist at the Manufacturer Part Number level, so maintaining and using
data at the MPN level can be critically important
Scenario Overview 1

Purpose and Benefits

This enhanced capability is made possible by functionality that enables the user to:
Identify Material by utilizing Manufacturer-level information via a MPN Profile in Purchasing View,
which defines the manner in which MPN processing can be performed (e.g., using a
Manufacturer-level, rather than Supplier-level, Purchasing Info Record and using an Approved
Manufacturer Parts List to validate inventory and purchasing management transactions).
Create and link an unlimited number of MPN materials records to a single Internal Material
Master record, even for the same Manufacturer (see MPN Hierarchy on another slide)
Cross-reference one or more MPNs with a Material Number, using MPN search helps (e.g.,
Manufacturer, MPN, and MPN description)
Link a MPN to one or more Suppliers, using Purchasing Info Records (with the optional ability to
maintain pricing conditions by Manufacturer within Supplier)
Maintain Manufacturer records in the Vendor Master, using a new Account Group type, MNFR
Link one or more Manufacturing Plants to a Manufacturer
View MPN information in a separate pop-up window
Optionally, create a list of approved Manufacturer Part Numbers for a Material that controls
validity periods for specific MPNs and Manufacturers plants
Users can define and maintain their own rules in the AMPL governing exchangeability and validity of
parts, and can run checks against those rules via user exits.
Utilize MPN in Purchasing (Purchasing Info Record, PReq, PO, Source List, Order
Acknowledgement, Quota Arrangement, Advanced, Shipping Notification), inventory (Goods
Receipt), MRP, QM, and Invoice Verification functions
Scenario Overview 1

Purpose and Benefits

In addition to the standard benefits of using SAP MM, MPN functionality offers:
Ability to maintain data, perform procurement and inventory functions and monitor
activity at the Manufacturer Part, not merely Supplier Part, Number level; this works
for regular (stock and non-stocki) and consignment materials.
Identification of parts using the Manufacturer Part Number (MPN) issued by the
The system also finds, identifies, and displays materials by using manufacturer-
specific details -- the Manufacturer Part Number (MPN) and the Manufacturer
Number. These materials are Inventory-Managed Manufacturer Parts that have
Material Master records and stock.
Ability to perform replenishment at the MPN level
Ability to perform Quality Management at the MPN level
Management of part interchangeability
Different manufacturers may manufacture parts that have the same technical
properties (including Revision Levels). In Purchasing, Inventory Management,
MRP, and the Availability Check; such parts are interchangeable with each other
and are held with their own stock.
Enables control from which manufacturers plants materials can be procured, as
well as to tell supplier which manufacturers plant(s) is(are) to supply the material.
The Manufacturers Part Number (MPN) and description, as well as the specific
manufacturing plant (if applicable), are included in the data sent to the supplier
with the Purchase Order.
Scenario Overview 1

Key Process Flows

Key Process Flows Covered

Manually Create (or generate via MRP) Purchase Requisition for MPN material
Display and assign source of supply to Purchase Requisition
Convert Purchase Requisition to Purchase Order
Change Purchase Order --e.g., MPN (optional)
Receive MPN material from supplier; update inventory level for stock MPN and
expense nonstock MPN
Scenario Overview 2

SAP Applications Required:

SAP ECC 6.0 EhP3

Company roles involved in process flows

Scenario Overview 3

Detailed Process Description:

Perform Configuration and Master Data set-up

Nonstock MPN Material

A Purchase Requisition for an MPN material either is created manually by a requestor or

generated via the Material Requirements Planning (MRP) process by a purchaser.

If sources of supply havent been assigned automatically to the PReq lines, then the
purchaser assigns a source of supply to the Purchase Requisition lines and converts the
Purchase Requisition into one or more Purchase Orders, which may be changed and also
may be subject to approval, based on their own predefined rules.

Once the PO is approved (either automatically or manually), it is sent to the supplier.

The supplier ships the ordered goods, which are received at the hospital, and a Goods
Receipt is entered and the MPN material is expensed to the requestors Cost Center.

The supplier sends the invoice to the hospital, where the invoice is entered.

During the payment run, the invoice is selected for payment, which is sent to the supplier

Stock MPN Material

A requestor creates an Inventory Reservation for an MPN material, and a Pick List is run in
Central Supply, which picks the material, sends it to the requestor, and records the Goods
Issue (which creates an expense to the requestors Cost Center).
Process Flow Diagram
Procurement with Manufacturer Part Number and AMPL

Symbol Description Usage Symbol Description Usage Comments



Band: Identifies a user role, such as Accounts Role band To next / From last Diagram: Leads Flow chart continues on the next /
Payable Clerk or Sales Representative. This band contains tasks to the next / previous page of the previous page
can also identify an organization unit or group, common to that
rather than a specific role. role. Connection
The other process flow symbols in this table go into
these rows. You have as many rows as required to
cover all of the roles in the scenario.
Hardcopy / Document: Identifies a Does not correspond to a task
printed document, report, or form step in a document; instead, it is
Hardcopy / used to reflect a document
External Events: Contains events that start or end the Document generated by a task step; this
to SAP

scenario, or influence the course of events in the shape does not have any outgoing
scenario. flow lines

Financial Actuals: Indicates a Does not correspond to a task

Flow line (solid): Line indicates the normal sequence Connects two financial posting document step in a document; instead, it is
of steps and direction of flow in the scenario. tasks in a used to reflect a document
scenario Financial
Flow line (dashed): Line indicates flow to infrequently- Actuals generated by a task step; this
process or a shape does not have any outgoing
used or conditional tasks in a scenario. Line can non-step event flow lines
also lead to documents involved in the process flow.

Budget Planning: Indicates a Does not correspond to a task

budget planning document step in a document; instead, it is
Business Activity / Event: Identifies an action that Does not used to reflect a document
either leads into or out of the scenario, or an outside correspond to a Budget generated by a task step; this
Business Process that happens during the scenario task step in the Planning shape does not have any outgoing
Activity / document flow lines

Manual Process: Covers a task Does not generally correspond to

Unit Process: Identifies a task that is covered in a Corresponds to that is manually done a task step in a document;
step-by-step manner in the scenario a task step in Manual instead, it is used to reflect a task
the document Proces that is manually performed, such
Unit Process s as unloading a truck in the
warehouse, which affects the
process flow.

Process Reference: If the scenario references another Corresponds to Existing Version / Data: This block Does not generally correspond to
scenario in total, put the scenario number and name a task step in covers data that feeds in from an a task step in a document;
Process here. the document
Existing external process instead, this shape reflects data
Reference Version / coming from an external source;
this step does not have any
Data incoming flow lines
Sub-Process Reference: If the scenario references Corresponds to
Sub- another scenario in part, put the scenario number, a task step in
name, and the step numbers from that scenario here the document System Pass / Fail Decision: This Does not generally correspond to
Reference System block covers an automatic a task step in the document;
Pass/F decision made by the software instead it is used to reflect an
ail automatic decision by the system
Decisio that is made after a step has been
Process Decision: Identifies a decision / branching Does not executed.
point, signifying a choice to be made by the end usually n
Proces user. Lines represent different choices emerging correspond to a
s from different parts of the diamond. task step in the
Decisio document;
n Reflects a
choice to be
made after step