In an earlier post I promised to give a quickguide to creating a query in SAP based in transaction SQVI. I’m going to show you how you can quickly build a custom report for reporting Sales Schedule Lines based on different filter criteria and multiple tables (VBAK, VBAP and VBEP: header, item and schedule line data resp.):
There are wonderful reports available in standard SAP’s Information Structures (E.g. MCxx reports). It can be so cruel though when data gets corrupted. You usually end up comparing report figures with whatever reasonable value you find elsewhere in SAP. If you want to be sure about the Information Structure’s reliability it is worthwhile to update an infostructure (say S021 – Production Order), store it under a temporary version ‘&(1’, and finally call this test version in a report that default uses version ‘000’.
To call up another version than ‘000’ go to System > User profile > User parameters and enter the parameter ID ‘MCR’ with the value ‘X’.
Now if you call up a standard analysis like MCP3 – Production Order Analysis a new field is visible for version selection. See picture below.
The major benefit of this procedure is that you don’t have to backup/delete current production data in version ‘000’.
It is also possible to compare the current version ‘000’ with the new test version going to Menu > Edit > Comparisons > Planned/Actual…
A good way of tightening authorization in your procurement organization is using mandatory source lists. In a previous post I explained how you can use source list in a central procurement organization together with MRP. Setting source list as a requirement for procurement you block any Purchase Order from being created if the material/vendor combination is not known to the source list for the purchasing organization, purchasing group and, or plant. This is excellent if rogue buying (i.e. buying without taking advantage of negotiated company discounts) in SAP is an issue in your company. This is how you implement mandatory source lists in your organization: Continue reading
Stock in previous periods can be a useful indicator in analyzing your stock positions through time per material or material group. Standard SAP report MC.9 offers this functionality:
Label printing can be configured in more than one way. It can be done through your regular output determination, but also through SAP’s ‘special’ label printing set up. This post is about the last. If you’re not sure what I’m talking about check out the below screen shot of the labeling settings in the material master’s Plant data 1 tab:
Here I can specify a label type and a label form. What these do exactly you can read further on. Before I move on to the customizing settings involved in label printing, let me warn you that this functionality does not go together with labels designed in SmartForm at all! Also we chose for SapScript label since we want to print on Avery A4 label pages. SmartForm does not support this. For this example I will set up label printing for goods receipt in MIRO.
Independent requirements and dependent requirements are the two main types of requirements you encounter when configuring SAP planning. This is what they are:
It’s possible that a posting needs to be done in the previous period for correction purpose. For this you can use transaction MMRV. This is one of those actions that belongs to Finance. You don’t want to mess with this without their approval (at least in production).
If you ran into this post because you got the message that posting is only allowed in a previous fiscal period, you’re posting periods were not updated in time. To solve this issue you go here.