Category Archives: Abap programming

Abap programming, EN

Sales order item costing

Leave a comment

There was a task to cost SD order item based on releted purchase order item. No problem..set costing variant with the user exit. There You can search for related PO item via EKKN table. If found, use the value from PO item , recalculate to basic unit . Done.

But…

Purchase order is not created immediatelly in the same period. It may take week or two to have PO item created. I checked first what is the average percentage of material cost. the result was that is about 70% of planned revenue.  So item is costed then with this value , 70% of planned revenues. Then there is a zreport, which shows if Po item exists. If PO item exists, zreport recost the SD order item via batch input .

 

Positive result of the solution: quite small diferencies in planned costs before real PO is created and SD items costed correctly based on existing PO. It can not be costed from material master data, cause average price in material master data is almost zero. If customer “e” stock is in use, sysetm does not update the value of material average price. There is mostly customer “E” stock, and they are getting different discounts for different sales order from their vendor. That is why other type of valuation can not be used.

This solution tok about two months of experiments. If you want to be successful, You need to focus on transactions to be used and correct timing and respect the process.

 

Abap programming, EN, Function modules

K_BALANCE_GET

Leave a comment

This function module is very useful, when you want to check current (or historical) ballance of costs and revenues of any cost object, not settled based on the settlement rule.

You need just determine OBJNR from tables AUFK (co orders), VBAP (SD orders) and PROJ(projects)  for particular co object.

I have used that in zreport which shows those ballances for SD orders or production orders after the closing operation are done on the end of the month. It should be in fact zero ballance, when overhead calculation, result analyse and the settlement is done.

'K_BALANCE_GET' "
  EXPORTING
    objnr =                     " onr00-objnr
*   wrttp = '04'                " cosp-wrttp
*   versn = '000'               " cosp-versn
*   bis_gjahr =                 " cosp-gjahr
*   bis_perio =                 " coep-perio
  IMPORTING
    saldo_k =                   " cosp-wkg001
    saldo_o =                   " cosp-wog001
    saldo_v_k =                 " cosp-wkg001
    saldo_v_o =                 " cosp-wog001
    .  "  K_BALANCE_GET

 

wrttp with value ’04’ means actual postings.

bis_gjahr and bis_perio are parameters used when You need to see that balance for different periods, even current ballance is zero .

 

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.