on ‎2013 Sep 04 8:59 AM
Hi,
I am loading my test environment but are facing some issues. The datasource I extract from is 2LIS_11_VAITM, but in the test environment I am missing sales documents. These are of a specific sales order type, and I am missing sales documents >= 70000000.
This is working just fine in production, and in the VBAK table all sales documents are there. Have tried to delete the setup tables (LBWG) and reload them (oli7bw) but still the records wont be loaded into BW. The only filter I use is on year, but there is alot of records with >=70000000 and the sales order types for the selected periods.
Have tried initial load with data transfer and full load on my info package, but nothing seems to do it.
Does someone have any suggestions for whats causing this problem?
Request clarification before answering.
Hi
I don't think you have an extraction problem here. Since the documents are comming your approach is correct. You said the sales documents past 7000000 are of a specific sales order type.
Have you checked the setuptable itself? Tx Se16 MC11VA0ITMSETUP are the docuuments of that range in there?
I recommend to check with a function if the customizing is done the same for that sales order type. Maybe in Tx OVAZ its not allowed for that salesorg
hope it helps
Martin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi and thanks for answer. In OVAZ the sales order type is there and it should not cause any problems.
And for SE16 i cant currently check this when I have to refill setup tables.
Additional information to Suman Chakravarthy K:
In production where it works fine, queued delta is set as update mode as well.
Hi,
If you filled the setup table then first check in MC11VA0ITMSETUP setup table in SE16. If the document is present here then pull the record in INIT WITH DATA TRANSFER in BW.
If the record is not present then there is some problem in filling setup table. Check in SM37 whether the setup table filling is completed successfully.
Regards,
Debabrata
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Take the help of any ABAPer and use rsa3 extraction through ABAP debugger. Put some breakpoint in the code. You would be able to understand whether the records are being extracted or not and if yes then where are they getting removed. This will help you surely to pin point the issue. Many a times when issue like these come, we debug through rsa3 and we get the list of data being processed and if we find some data missing then we are able to find the point of the code.
Hope this helps.
Mohamed Shadab
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Try to fill the setup tables for small - small chunks. use the selection fields when you filling the setup tables with the help of Sales Organization, Company code and SD document.
Try it ones may be it will help you.
Regads,
Satendra
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kjell,
Can you try to take any one missing document number for the testing and check whether its coming in RSA3 extractor after deleting and filling up the relevant setup tables.
The outcome of this activity will define the our next course of actions.
Br,
Arpit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Again the same suggestion from my end. How are you trying to run in RSA3 in F or D mode?
F will bring from Setup tables.
D will bring from RSA7. Have you scheduled job in LBWE to move delta from SMQ1 to RSA7?
You will have to debug your extractor in RSA3, if the data really doesn't come in RSA3.
Hi KJell
To solve the setup table filling problem...
1. Either maintain all conversion factor with the help of your functional guy.
Else.,
2. Discard those Sales Order by selection of range in OLI7BW where you have missing Conversion ratio problem
I would say fill up setup table with company code selection to break the problem into smaller set of data.
for a queued delta, you need to run RMBWV311 report from Se38 to bring records from extraction queue to delta queue... and you are running RSA3/InfoPackage in full mode, then it reads from setup table.
Cheers
Anindya
I am running RSA3 in F mode. I get some records but still missing >7000000. There is scheduled a job every hour in LBWE (queded delta), and there seems to be no errors. I am quite new to BW and especially extraction of data, so sorry if my understanding isn't 100 percent on this topic.
But if there is a job moving data from SMQ1 to RSA7 and I delete setup tables (LBWG) and then fill the setup tables (OLI7BW). The data I am missing is in VBAK/VBAP table, shouldn't this data then be filled in the setup tables, and visible in RSA3 for datasource 2LIS_11_VAITM? (if it was working correctly)
To Martin Grob
Se16: MC11VA0ITMSETUP
I dont understand what I should be looking for here?
MANDT/ RELID/ ID / STFR2 / CLUSTR is the fields
Hi
MC11VA0ITMSETUP is a cluster table, you cannot see data directly here..
RSA3 has a field called Data Records / Calls and Display Extr calls... are they in default settings?
of 100 and 10 respectively? Then RSA3 would only extract 100X10 = 1000 records.
A report RMCEX_SETUP_ENTRIES ( from SE38) can give you number of records in setup table per application component, but there might not be one to one mapping with extractor checker.
Cheers
Anindya
Hi ,
1. Verify whether the documents that you are looking for are they available in the application tables you are testing.
2. If yes then Fill setup tables and then run the extractor in RSA3 with full mode to check if the same are coming or not.
3. If it is coming in RSA3 then there is no reason why the same will not come to BW.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Run RSA3 in F mode to see records are coming?
Run init W/O transfer
Then run repair full with out specifying data selection.
Have you scheduled V3 job(JOb Control in LBWE) for delta loads to BW?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Now i have problems filling setup tables, but anyway. The update mode is set to queued delta not unserialzed V3 update, should I change this?
I currently have this error filling setup tables for application 11: Error converting quantity: unit EA numerator 0 denominator 0. (http://scn.sap.com/thread/1733038)
If I fix this I will try your way to load and see what happens.
Hi ,
Seems like units may not be maintained properly at ecc side. Pls take source team help and maintain the units. later you can try to fill setup tables.
At production level V3 updates not changeable. bit risky one. need to lock ecc system. change at dev system and move to production
if your atuhorisation prod you can do(without down time). but might be chance of missing delta records.
Thanks
Hope you are in touch with your Functional team about the Exchange rates. After they assign it in SPRO in ECC, you have to do Transfer exchange Rates and Transfer Global Setting on your Source system in RSA1 in BW.
To take a decision on Update method : http://scn.sap.com/people/roberto.negro/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-th...
| User | Count |
|---|---|
| 9 | |
| 8 | |
| 5 | |
| 4 | |
| 4 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.