This post is an extension to a previous post on Credit Checks exceeded. When you are in a testing environment it is common that it’s difficult to quickly process sales orders and/or deliveries because the credit check is exceeded for a customer. Credit is building up, since so many sales orders and deliveries are entered but are usually not going through the whole process including payment processing. To quickly clear a blocked order got to transaction VKM1.
VKM1 - Blocked SD Documents
In the main screen enter a common criterion like Credit account (usually sold-to) and hit the execute button (F8). In the report screen that follows, select the document to be unblocked and press the green flag button followed by saving the approval. Now you can continue processing the order or delivery.
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.
MCP3 - New version field
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