Category Archives: MM

Purchase orders confirmation

This application was a “Christmas gift” for members from purchase department. I have seen that edi connection via idocs  was not established with all of vendors and many of purchase orders/items  had to be confirmed manually. If you know how standard ME22N transaction works, You have to admit that this part of the activity is very time consuming. Users have to open particular Po item by item and confirm it in item detail. Imagine that there can be up to 100 or more items to be confirmed for one PO.

Because a large part of the confirmation is in fact a constant (reference, delievery date) and confirmed quantity mostly corresponds with required delievry time from PO already recorded in Po , i have created zreport for Po confirmations.

This report reads at first all items of particular PO and shows items on the screen (ALV layout) . Report also allows to specify constant data on the selection screen. Then user can easily udjust data on the screen and the Po is confirmed almost in one shot.

The big advantage is here when some Po is confirmed , and then confirmed later on  again with different data. The report can overwrite old confirmed items with new data .

Here I can see real benefit of zreport. Simply it saves a lot of time.

How to read an idoc and how to understand what is wrong?

Work with IDOC is not fun on the user side. Incomming and outcomming idoc , few hundreds per day. Some of them are not correctly created and can not be processed without additional maitenance. User can use standard transaction as WE02 or WE05. But there is an requirement to understand to idoc technology and its structure.

We have connceted our sap system with another third party application. Since that day , number of questions why the idoc can not be processed was increased dramatically. If there is an error, system shows just the first one. You can correct the segment in idoc, or missing master data..but when processed again, new errors are comming again.

Then i made a decision to implement the function module IDOC_READ_COMPLETELY into new zreport.  It reads specified types of  idoc messages and shows all potencional problems in one shot. For example idoc message received from the customer. It contains data for new sales order to be created . number of items can be up to 100 or more.

The report called show_idoc_data can provide simple job. The program compares data from idoc segment with material and vendor master data. If there is an inconsistency (vendor does not exist for sales organisation, material master data ar not complete for plant..etc) users can see it immediatelly. Thne they can update master data and process the idoc again.

 

Believe me, this was real time saving development.

 

Monthly material consumption

Monthly material consumption report is a report which shows monthly consumption of material bssed on selected material movement (101,102,201,261, 601 etc.. movements between storage locations are not shown). Report shows also material description, materila master data for planning .

The main problem to solve was the performance. Cause the report is based on MSEG table, data can not be read directly. Solution has two parts,  archive of mat. movements creation and the report . As we know that when the period is closed, no new material movements can be created for that period. It makes no sense to search for those material movements every time when the report is running. Monthly archive creation takes about one hour . The data reading then takes few seconds , subotals per material movements are stored.

The report shows material consumption per material for last 12 periods. It shows average consumption and it is easy to to compare with planning parameters from MRP data as safety stock, average delievry time and so on.

Main usage of the report:

-check monthly consumption

-check planning parameters , for example if safety stock has a reasonable value

-check number of receipts and issues per material and plant

-compare current stock with average consumption