Standard purchase order pricing is based on date of purchase order creation. Some vendors let their sales prices be determined by the date on which they deliver the goods (i.e. delivery date). SAP offers standard configuration for this through Pricing date category.
Pricing date categories
The two most relevant pricing date alternatives probably are delivery date and goods receipt (GR) date. You can set this category on different locations:
- Vendor Master – Purchasing tab (MK01)
- Contracts – Item: Additional data tab (ME31K)
- Inforecords – Purchasing Org Data 1 tab (ME11)
Since pricing date is usually determined per vendor, setting the pricing date category on vendor level is often sufficient as the value is copied at time of inforecord/contract creation.
A suitable lot-size for continuous production can be hard to come up with. Picture the situation of a mineral oils manufacturer that refines crude oil to 3 co-products. The planner wishes to control the process flow to align the production with demand (i.e. the refinery is not continuously refining at the same speed as it would in make-to-stock). Another requirement for ATP is that the production quantities are issued on a daily basis. Hence we want MRP to come up with weekly planned orders that are distributed on a daily basis. In abundance: 1 planned/process order per week, with equal quantities released per day.
MRP and Consumption-based planning are two fundamental SAP planning types that can be used to determine a product’s requirements. To avoid any confusion on the subject: I am not talking about the MRP run that is executed through MD01 and MD02. I’m talking about planning types that are set in the Material Master’s MRP1 tab. The MRP type is used in the MRP run to determine HOW procurement and/or production quantities are calculated.
The dead stock report often leads to misinterpretations. Hence a little guidance on the dead stock report.
The dead stock report analyses what part of stock is never touched in a defined period of time. If you look at the below graph you will see stock level through time.
Stock level through time
In analyzing stock movement between period 1 and 5, stock never drops below 30. 30 is your dead stock. It’s the part of stock that was never touched. Now what does this tell you? That’s not easy to say:
NETCH, NETPL and NEUPL are three fundamentally different ways to schedule your MRP run:
- NETCH – Net Change Planning
- NETPL – Net Change Planning within Planning Horizon
- NEUPL – Regenerative Planning
MRP Processing Keys
I will elaborate on these three options and their workings:
End-users can get confused about the difference between MD04 – Stock/requirement List and MD05 – MRP List. This post will give you the answer on when to use what report and why:
Last week I spent some time finding out how to implement barcode printing in SAP. As usual I googled the internet and a couple of alternatives were flung at me: middleware, hardware vendor applications, installing fonts, etc.
Interestingly enough there is one very simple solution: using the standard barcode font that SAP standard offers for SmartForms. You wonder why there are so many alternatives while SAP already includes the easiest one. The main requirements for printing barcodes this way are: