cancel
Showing results for 
Search instead for 
Did you mean: 

Back dated MM posting - Historical GI/GR & IV

Former Member
0 Kudos

Hello All,

My scenario is this:

Our client acquired a small part of another company(using SAP). The seller had given the data extract for required SAP tables to us including MKPF and MSEG. Our client need those historical data to be stored in SAP for reference and audit purposes. Client copy is not possible and we are in the process of converting those data through data conversion process. So far we are good in creating materials, PO transactions etc. Now we are stuck in posting goods movement data and invoice verification as unlike FI postings here we cannot open closed MM periods. We have these transactions from year 2007-2011. My queries are here:

Note: We are using a separate client other than production for this historical data migration.

1. Opening previous periods?

One of the dirty ways I got: a) Before doing any posting as a first step delete the assignment of plant to company code via transaction 'OX18'. b) Now via 'OMSY' change the current year and period for the company code. c) Come back to 'OX18' and assign the plant again.

-> Will this way of opening an older period affects anything else other than posting?

3. Does backdated posting affect only stock value, stock qty & moving average price in MM?

2. Stock value, stock qty & moving average price(MAP)?

In a normal scenario backdated postings have the risk of changing the MAP in the current period. However in our case they are actually the posting of the older periods(historical data). SoI suppose whatever stock value, stock qty & MAP reflecting in the current period is correct and valid.

->Is my assumption correct here?

Sorry about asking many questions in a single post! Apart from this even if you have a different better approach for this process please share.

Your valuable inputs are highly appreciated!

Regards,

Manoj

Accepted Solutions (1)

Accepted Solutions (1)

kailas_ugale
Active Contributor
0 Kudos

hI,

As per SAP Notes 487381  Go to Tcode MMPI, then go to menu bar and select system - user profile-owndata.In that screen , under the parameters tab enter MMPI_READ_NOTE in Parameter ID field and enter, then under short description you will get Initialise period. Next Save.

Again go to MMPI enter company code, period and year and execute.

1. Opening previous periods?

One of the dirty ways I got: a) Before doing any posting as a first step delete the assignment of plant to company code via transaction 'OX18'. b) Now via 'OMSY' change the current year and period for the company code. c) Come back to 'OX18' and assign the plant again.

-> Will this way of opening an older period affects anything else other than posting?

This is not correct way to open MM period

3. Does backdated posting affect only stock value, stock qty & moving average price in MM?

2. Stock value, stock qty & moving average price(MAP)?

Yes it will effect valuation  of Material

In a normal scenario backdated postings have the risk of changing the MAP in the current period. However in our case they are actually the posting of the older periods(historical data). SoI suppose whatever stock value, stock qty & MAP reflecting in the current period is correct and valid.

->Is my assumption correct here?

It correct for current period only

you may have different price in previous period

Kailas Ugale

Answers (2)

Answers (2)

Former Member
0 Kudos

I think it is practically impossible. The way to convince them is first to point out the changes you may have to do to org structure and how to justify it, as previous transactions are made in different compnay and not in your company than how can you post transactions in your company. And if you create new co.code again its not part of your entity and hence should not be created in your system. Even if the previous company is ready to provide client copy of their system, it will not work as you will always have that client as a silo client where someone can login and check, but it will not be real time or syncronised with your live system and hence any attempt to maintain these data is futile. May be if your client is sensible than they may be convinced with this arguement.

Regards,

Dakshesh

Former Member
0 Kudos

The part our client had acquired is coming under a single company code and plant. So we already have that org. structure in place. Also we tested 80% of the FI postings (except accounting docs. due to GR/GI/IV) and they look good. It seems we stuck only for Goods movement in our scope and which is long unrelaible process.

Former Member
0 Kudos

You are trying to replicate each and every transaction of previous system (5 years old transactions as well). It is nothing but trying to emulate all transactions as if they were happening sequencially.

I do not know the reason for having details of each and every transactions in your system, but I believe for any audit or compliance purpose you can have data extracted in BI/BW and reported, it will not be each and every transactions but it should be sufficient.

But to answer you exact query, I guess you are having a different system (client) created for this purpose. I do not know how different your org. structure is as compared to the acquired company, but if its more or less simillar or if you are planning to create co. code and plant as if they were not acquired till date, than may be this will work.

You will have to start your system with the oldest period of any of the transactions you wish to upload. Lets us say its 01, 2007, than post all the transactions and that too in the exact sequence as it would have been posted in that system, than close 01, 2007 and open 02, 2007 and repeat the process till you reach current period.

I believe its a huge project in itself, and do not think is worth the pain, as I am sure org. structure will not match, above all you may not create co. code which was not yours before this day.

Just think about the sequencing the data and that too for 60-70 periods, is going to be huge. Also, you have mentioned that its a small part of a company and hence if there is any transactions from your acquired plant to any other non-acquired plant in that system you will not be able to post such transactions directly into your system (as it will require those plants to be created in your system).

In all I think you are trying to copy the client of the acquired company, the difference is you want to do it manually. I would suggest to rationally evaluate your requirements and than think of migrating the required data only and get appropriate reports for audit and complaince.

Regards,
Dakshesh

Former Member
0 Kudos

Hi Dakshesh,

->Yes the best way is to use BI/BW for reporting/auditing, but here we do not have one

->Even we explained to client the same thing that,we may end up spending huge effort in achieving this. In fact we rejected this initially in our scope. However Business is very strong in their requirement.

-> We are uploading all data (MM,PM etc.) that are related only to a single company code and a plant that the seller was using. Though as you rightly mentioned org. structure may differ.

Anyways, if do not see any significant approach for this I just need to convince them!

Regards,

Manoj