Profit center balance sheet

On this post I would like to look at how the system has been designed to transfer balance sheet items to profit centers using the transactions 1KEH, 1KEI, 1KEJ, 1KEK. Often I have come across situations where the total balance of balance sheet accounts on a report painter report based on the library for GLPCT doesn’t match with the total of the line items on the called up report. This is not a Bug rather this is how the system has been designed.

When the trnasactions 1KEH, 1KEI, 1KEJ, or 1KEK being used, GLPCA table gets updated with the total balance of each object (Customer, Vendor, WIP, Material, F.Asset) for the given period. But GLPCT table update happens based on a delta technique.

Let me explain this logic using the following example.

Imagine that a customer has a constant balance of $200 in periods 1, 2, 3.

Transaction 1KEK for the period 1 would make an entry on GLPCT (Total) for $200 and another entry on GLPCA (Line item) for $200.

For the period 2, since the total balance of the customer for the given period would be updated on GLPCA table, Transaction 1KEK would update $200. But GLPCT will be updated using delta technique hence the value would be $0.

Same procedure would be followed for period 3.

When the user runs the profit center balance sheet for the periods 0-3, total amount based to GLPCT would show the correct amount $200 for the reconciliation account of the given customer. But when the user drills down and calls the standard profit center line item display report, it would show a wrong figure $600.

To correct this mismatch, user has to run the line item report only for period 3 rather than 0-3. A customer development of line item display report with the logic stated above and assignment to the report painter library for profit center reports would solve this issue.

Please feel free to send me your comments. Click on Archives to see my earlier posts.

SAP Business Transaction Events

I’m extremely sorry that I couldn’t write on my blog for some time because of the assignments that I had to finish for my clients! Today I got some free time and decided to talk about SAP business transaction events!

SAP business transaction events are one type of customer enhancements provided by SAP! On this post I’ll talk about how we can change the logic for duplicate vendor invoice check using SAP business transaction events!

We can access the business transaction events using FIBF

Next we have to find the process interface for duplicate invoice check! To do that, follow the following steps.

• Select the menu as stated below

• Execute the info system as stated below

• All the processes will be shown below

• Select the process 1110 and click on “Sample function module” as stated below

• Copy the sample functional module “SAMPLE_PROCESS_00001110” and create “ZSAMPLE_PROCESS_00001110”. Put the customized logic in the functional module “ZSAMPLE_PROCESS_00001110” and activate it!

• Now go back to FIBF and execute the menu as shown below

• Define a new product and activate it

• Now go back to FIBF and execute the menu as shown below

• Assign the function module “ZSAMPLE_PROCESS_00001110” to the process “1110”and the product that was defined in the earlier step.

• Bingo!!!!!! Now every time when a vendor invoice is being posted the invoice check will be carried out using the custom logic built into the function module “ZSAMPLE_PROCESS_00001110”. But make sure that the “double invoice check” tick has been put on the relevant vendor masters!
  

I hope this post about the SAP business transaction events will help your business! Thank you very much for reading my blog! Please feel free to send me your comments!

Allow the company to grow!

Hi guys! I’m really sorry that I couldn’t write anything on my blog during last 3 months. I was really busy with two simultaneous projects. Now one has gone live and the other one is going to cutover in MAY. So I thought I would start writing on my blog from this month again.

Thank you very much for all your comments.

This time I would like to give a small tip. In a business environment, all the companies will eventually grow. A well thought out ERP implementation will never give any problems when the company would like to expand its operations in the future.

For example, we all know that more than one company codes in SAP can be grouped under one controlling area for management accounting purposes. If a controlling area has the currency type company code currency, it’s not possible to have company codes with different local currencies under that controlling area. So if a new company with different local currency has to be added to the same controlling area in the future, it would be impossible.

So it’s always critical to look into future expected development of the company and give room for it when an ERP is being implemented. After all an ERP should never be a bottleneck for the company’s growth.

I wanted to share this with you since I had come across this issue with one of my new clients. I hope this tip would be useful to you.