Purchasing Data Not Tying Up between BW and R/3.

Question

Hi,
As a part of our project, we reloaded the all the data related to Purchasing through the extractors   
2LIS_02_SCL
2LIS_02_ITM
2LIS_02_HDR
As these were corrupted due to patch application.
We took all the possible care during reloading of all the data from R/3 like locking the user from making any transactions, Deleting the setup tables etc in a step by step process etc.
But however, after the extraction the data is not tying up between R/3 and BW Purchasing ODS.
Is there some thing wrong did we do or How can we get that missing records into BW again.
Appreciate your help.
Thanks.

Answer 1

Hi......
Did u fill the set up table with any selection...........?.....Previously no of records picked was larger than this time........right?..........Hav u checked RSA3 in the source system..........is it showing correct no of records........? if yes............then check the selection tab of the IP..whether u hav maintained any selection there.........
If no..........then......first check the selection in the set up table..............then the function module....which is extracting the data..........u will get the function module in RSA2.........there just double click on the Extractor.........u will get the function module  name........
Anyways.........did u know which records r missed.........then just fill the set up table for those values only.........then do full load......
Anyways,............I think u know the steps in LO Extraction...........still for ur reference..........
1. Transfer the logistics DataSource for transaction data from Business Content
With the transfer of the DataSource, the associated extraction structure is
also delivered, but the extraction structure is based on LIS communication
structures. Furthermore, based on the extraction structure for the DataSource,
a restructuring table that is used for the initialization and full update to BI
is generated.
Naming convention:
DataSource 2LIS_<Application>_<Event><Suffix>; where <Event> is
optional
Examples:
2LIS_02_HDR: 02 = MM purchasing HDR (u2192 HEADER ) = Document
header...
Extraction structure MC<Application><Event/group of
events>0<Suffix>; where MC is derived from the associated communication
structures and <Suffix> is optional
Examples:
MC02M_0HDR: Extraction structure for the DataSource 2LIS_02_HDR,
where M_ indicates the group for the events MA (order), MD (delivery
schedule), ME (contact) and MF (request).
Restructuring table (= setup table) <Extraction structure>SETUP
Example:
Extraction structure: MC11VA0IT u21D2 Restructuring table:
MC11VA0ITSETUP
2. Maintain extraction structure (transaction LBWE)
This means that fields can be added to the extraction structure that is
delivered with the DataSource without modifying anything. On the one
hand, fields from the LIS communication structures that are assigned to the
extraction structure can be used, that means standard fields that SAP has
not selected, and on the other hand, customer fields that were attached to
the LIS communication structures with the append technique can be used.
After the extraction structure is created, it is generated automatically and the
associated restructuring table is adapted.
3. Maintain/generate DataSource
In the DataSource maintenance, you can assign the properties Selection,
Hide, Inversion (= Cancellation) and Field Only Known in Customer Exit to
the fields of the extraction structure. After enhancing the extraction structure,
the DataSource always has to be generated again!
4. Replicate and activate DataSource in SAP BI (=metadata upload)
5. Maintain Data Target (Data Store Object, InfoCube)
6. Maintain Transformations between DataSource and Data Target
7. Create a Data Transfer Process
the Data Transfer Process will be used later to update the data from the PSA
table into the Data Target.
8. Set extraction structure for updating to active (transaction LBWE)
In this way, data can be written to the restructuring table or the delta queue
from then on using the extraction structure (see following steps).
9. Filling the restructuring table/restructure (OLI*BW)
During this process, no documents should be created or changed in the
system! In some applications, it is possible to fill the restructuring table
beforehand in simulation mode. These results are listed in a log (transaction
LBWF). Before filling the restructuring table, you must ensure that the
content of the tables is deleted (transaction LBWG), preventing the table
from being filled multiple times. Once the restructuring tables are filled,
document editing can resume as long as Unserialized V3 Update or Queued
Delta is selected in the next step. Be absolutely sure that no V3 collection
run is started until the next successful posting of an InfoPackage for delta
initialization (see step 11).
10. Select update method
• Unserialized V3 update
• Queued delta
• Direct delta
11. Create an InfoPackage for the DataSource and schedule the Delta
Initialization in the Scheduler
This updates the BI-relevant data from the restructuring table to the
PSA table. Since the restructuring table is no longer needed after delta
initialization, the content can be deleted (transaction LBWG).
Use the Data Transfer Process created in step 7 to update the data from
the PSA table into the Data Targets. After successful delta initialization,
document editing can resume, as long as the direct delta update method
was selected in step 13. This means that BI-relevant delta data is written
directly to the delta queue.
Note:
If the DataSource supports early-delta initialization, the delta data can
be written to the delta queue during delta initialization. This feature is
controlled with an indicator in the Scheduler.
12. Start V3 collection run (transaction LBWE)
This step is only necessary when the update method unserialized V3 Update
or Queued Delta was selected in step 10. By starting a corresponding job for
an application, the BI-relevant delta data is read from the update tables or
extraction queue and written to the delta queue.
13. Create an InfoPackage for the DataSource in BI and schedule the Delta
Update in the Scheduler
The BI-relevant delta data from the delta queue for the DataSource is updated
to the PSA table. Use the Data Transfer Process created in step 7 to update
the data from the PSA table into the Data Targets.
Hope this helps.......
Regards,
Debjani...