on 11-10-2010 10:44 AM
Hi All,
Recently we had a design change in PO data flow.
Earlier the flow was: SAP -> Non-SAP system (oracle datamart) -> BW
Now the design is such that the POs flow directly to BW from SAP.
Due to some issues, the dump taken from the old system were not proper and hence the initial data in the BW itself was not proper.
Now we face the issue of data mismatch between SAP and BW due to the above issue.
Usually the issue is resolve by pulling the affected PO manually by clearing the setup table and filling with the affected PO and running the repair full load in BW. This is possible only if the no. of POs are less.
Is there any way by which we can pull large no. of POs (say over 3-4k) at one go?
regards,
Janmejoy
Hi,
You can use batch input to fill setup tables even for 3k or 4k number of POs. It worked for me with 2k POs.
Create an OLI3BW template for batch manager and then just copy this template for all POs.
I used VBA in excel prepare necassary file. So your input file will have 8*4k lines.
0000 T OLI3BW
RMCENEUA 1000 X
0000 BDC_CURSOR ENDDAT
0000 BDC_OKCODE =ONLI
0000 BELNR_L 26001535
0000 LAUFNAME 26001535
0000 ENDDAT 13.05.2011
0000 ENDZEIT 14:57:27
0000 T OLI3BW
Edited by: Ondrej Vach on Nov 16, 2010 6:24 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
System -> Services -> Batch input -> Recorder
New recording:
MyRecording
OLI3BW
...
Start recording
fill oli3bw params
run oli3bw
and you'll see template - the one in my previous post with correct formating.
Export it to file, copy for e.g. 4k times (in VBA). Don't forget to change run name as well doc. number.
Then import it back and run "Process" in backgorund. It took 15 minutes for 2k POs.
BR
Ondrej
Can anyone help here?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Roy,
You could look at :
1. Create a separate extract on EKPO , EKKO , EKBE and pull in a full repair load into the ODS to load all the POs... or possibly pull the same into a separate ODS and then do a self loop on the main ODS to have a look up...
This would keep the existing delta intact since the load is separate.. also you can possibly have a function module extractor to extract this information using specific selection criterion...
2. Re init and reload all the POs for SAP by filling the setup tables in full..
Hi,
The problem with updating setup tables with many PO numbers as input is that it would go to dump giving some SQL dump stating too long selection condition.
If your data target being fed by this datasource is a DSO, then you can go by an alternate way.
If you have the list of POs that you want to upload, you may sort them which gives you the range for these POs. And then give the range of POs for updating in setup tables. Obviously, there would be POs which already exist that would get updated in setup table. But if the data target is DSO(based on overwrite), then there should not be any issue.
Next, you may go with Repair full load.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.