on 09-12-2011 7:10 PM
Hello all.
I made copy from one version, like 000.
The result is Version A1 and A2. I copied everything(Master Data and Transaction Data).
For each version, i ran a MRP. But in differents periods. Like October and November.
After MRP, i have a lot Planning Orders in A1 and A2. But in differents months.
My question is: I want to merge A1 and A2 in another version(Merge only Planning Orders). How i can do this?
Using /SAPAPO/MVM or /SAPAPO/VERCOP i can copy all data from source to target. But always delete previous data.
Thanks
Best Regards.
Marcelo
In SNP area, we do have /SAPAPO/VERMER - Planning Version Merge. Is it helpful? Best regards/Tiemin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This isn't the answer you WANT to hear. But there's no way to my knowledge to achieve your requirement using standard version copy functionality in APO.
One way to preserve the data for alternate / merged versions that I've found useful is to use the /SAPAPO/REL_TO_OLTP transaction to send volume data to the ECC client. If you are loading both inactive versions to BW, then you should be able to release that data from BW to ECC inactive/"long-term" simulation versions where it can be aggregated. That is to say, you could send A1 and A2 separately and they will simply add to one another, not overwrites (delete and re-create).
This being said, requirements using this transaction are sent as planned ind. requirements in ECC. This may not be the desired outcome that you're looking for, so you might have to be careful which key figure you send to represent volumes.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
One thing I've always wanted to try is using a custom data view and some custom macros to copy from one version to the other (using the alternate planning version functionality). Of course I'm not sure how this would work because you can't really select an alternate variable planning version when performing background processing......
User | Count |
---|---|
12 | |
4 | |
3 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.