Category Archives: SAP modules

ABAP programování, ABAP řešení, CO, PM, SAP moduly

Vytvoření skupiny zakázek PM

Leave a comment

Po implementaci modulu Pm vyvstal požadavek založení skupiny PM zakázek (transkace KOH1, KOH2) pro následný reporting nákladů v transakci S_ALR_87012998. Úkol se zdál poměrně snadným, ale …

Ve standardu sapu by bylo potřeba neustále zadávat nové a nové zakázky do skupiny takázek v dané hierarchii. Toto nebylo možné aplikovat, protože zakázky různých druhů mají společný interval a skupina zakázek se zakládá pomocí uvedení seznamu zakázek. Toto je uživatelsky neudržitelná věc. Navíc požadavek byl, aby se zakázky zakládaly ve vazbě na vybavení.

Continue reading →

Abap programming, EN, MM, SAP modules

Purchase orders confirmation

Leave a comment

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.

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.