Category Archives: EN

EN, How to

How to trace the activity?

Leave a comment

ST05 is very  effective tool for abap developers. When can be used?

– if You want to find tables . For example, You know that some data are shown in standard transaction. Run ST05 , activate the trace and then run the standard transaction in other window.  When done, go back to ST05 and show trace. In 95% of issues , You will see all relevant tables.

– If You want to check the performance. If the report created by You got performance issue, or the same cn be with the standard SAP program, run ST05 , activate the trace and run your report or another transaction. When done, run ST05 again and show the trace. You will see the performance of tables.

 

 

 

Abap programming, CO, EN, PP, SAP modules

Costing master data

Leave a comment

I was realy tired from the same kind of questions: “Why this material can not be costed without errors via CK11N?”. There is one phase of the costing via CK11N where user can  got just error message “Not costed”. Nothing else. Imagine, that there is about 500 itesm transferred from another system via PDR. There is no way to chcek them in very short period.

Basic master data errors

– no costing screen in mat. master data (MM02)

– wrong procurement type

– missing bill of material

– missing routing

– missing inforecord for subcontracting

– average price zero

etc…

I have collected those and more issues in one zreport called check costing master data. Then users can simply run this transaction/report for one or more material. It shows list of potencional problems with their master data. This reduced number of  “small incidents” rapidly .

Abap programming, EN, Function modules, MM, SAP modules

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

Leave a comment

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.

 

Abap programming, EN, MM, SAP modules

Monthly material consumption

Leave a comment

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