Loadings missing sales documents

[#1]

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?

[Former Member]

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

[Former Member]

The records is not comming when I run RSA3 in the R/3 test enviroment. I find the records in the VBAK/VBAP table, shouldnt these records come in the 2LIS_11_VAITM?

[former_member182470]

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.

[Former Member]

Hi Kjell,

If you have correctly filled the setup tables, the data will absolutely come in RSA3.

Check with Suman's advice to check ahead.

Br,

Arpit

[anindya_bose]

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

[Former Member]

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

[MGrob]

Hi

Your assumptions are correct you should see it via RSA3. To be sure your setup table is filled my suggestion was to check if you get entries in MC11VA0ITMSETUP.

Also RSA3 won't give you all records it will only extract in default 100 x 10 records.

hope it clarifies

Martin

[former_member182470]

Yeah. If the data is in DB tables, then your setup filling should be filled with all the data till now. Hence you can see the data in RSA3 in F mode.

Your LBWe job will move delta data to RSA7.

Did you try to debug your extractor in RSA3 with the help of an ABAPer?

[anindya_bose]

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