Open Orders not being picked up

Question

Hi All,
I am implementing 2LIS_11_V_ITM to extract the open orders data into BW. I have implemented all the flow and trying to check the extraction using RSA3. I have deleted the setup tables using LBWG and filled them up using oLI7Bw. but when I run the RSA3 it is not returning any records. From which tables does the extractor picks the open orders data? How can I check if there are any open orders??
Thanks,
RPk.

Answer 1

hey rajesh,
You have to fill the set-up tables before to check in RSA3.
Now you can use transaction OLIIBW to carry out a reconstruction for orders using different order categories or OLISBW to execute a reconstruction for service messages/requests (and to fill setup tables, where RSA3 takes data from).
Pls go thru the steps:
LO-EXTRACTION
• T-Code: LBWE
• First we need to check which data source suits the client's
requirements in LBWE.
• Check whether it is in Active version/Modified version. If it is
in M version go to RSA5 and select our data source and press on
Transfer. Then go to RSA6 and see whether the datsource is been
transferred.
• If the datasource is already in active version then we need to
check whether the datsource is already extracting data in to BW.
• If the datasource is extracting the data then we need to check the
data existence in Setup tables (use SE11 to check the setup tables
data. For every extract structure one and only one setup table is
generated whose technical name is Extract structure name+ setup, for
eg. If extract structure name is MC11VAOHDR then set up tables name
is MC11VAOHDRSETUP) and Extraction Queue (LBWQ) and Update tables
(SM13) and Delta Queue (RSA7). If data exists in any of these T-
codes we need to decide whether we need the data in BW or not. If we
need the extract it as we do in LO-Extraction below. I f we don't
need delete the data.
The dataflow from R/3 into BW:
• We nee to generate the extract structure by selecting the fields
from the communication structure in LBWE.
• Generate the datasource and select the selection fields,
cancellation fields, hide fields that we want.
• Replicate it into BW. Then we need to attach Info source(Transfer
rules/communication structure) to the datasource. We got 3 methods
to attach the infosource..
1) Business content:: Business content automatically proposes the
transfer rules and communication structure, we don't have to do
anything manually.
2) Application proposal: Here too proposal is done but some objects
will be missing which we need to assign in the transfer rules.
3) Others: here we need to create the transfer structure, rules,
comm. Strct from the scratch.
• Modeling like infocube, Infosurce attachment,….
• Then activate the extract structure.
• We need to fill the setup tables for the first time loading. In
filling the setup tables we can select between Full load and delta
initialization loads.
Filling Set up table:
T Code : SBIW
Settings for Application-Specific DataSources (PI)->Logistics--
>Managing Extract Structures>Initialization>Filling in the Setup
Table -->Application-Specific Setup of Statistical Data --> in that
Youcan perform the Setup (Example : SD-Sales Orders - Perform Setup)
and execute .. or else direct T Code : OLIBW ( means based on your
application like sales order/billing/ purchase etc)• For setup
tables T-Code is OLI*BW where * equals to application number like 02
fro purchasing,08 for shipment…..
• First we need to decide whether we want delta loads to be
performed in the future. If we want to do delta loads, then we need
to go for Delta Initialization process or else do full load.
• When we perform setup tables extraction, since setup tables are
cluster tables, we can't see the data in the setup tables. So we go
for Extractor checker (RSA3) just to see the setup tables data
(full/delta initialization).
• Then create infopackage and select Full or Delta initialization in
Update tab and schedule it.
• Delete the setup tables data by using LBWG.
• Now we need to do delta loads.
• Delta load data flow differs with various delta update methods. We
got 3 delta update methods as u know.
• If we select "Queued Delta"update method then the data moves to
Extraction queue(LBWQ). Then run Collective update to move the data
from LBWQ into Delta Queue (RSA7). Then schedule the data using the
infopackage by selecting Delta Load in the update tab.
• If we select "Direct delta" then the delta data moves into RSA7
directly.
• If we select "Unserialized V3" method then the data goes
into "Update tables(SM13)", then run Collective update to move the
data from SM13 into RSA7. Schedule the data using infopackage.
• If we click on Maintenance, we can generate the extract structure.
• If we click on 2LIS_02_CGR button, then we we can generate data
source
• Inactive under Update column: we can make a extract structure as
active or inactive.
• If we click on Job control button the we can maintain the
collective update parameters like, start time, and is it hourly once
or dialy once ……
• If we click on Queued delta button under Update mode then we can
select among 3 delta update methods.
Only Full/Delta initialization data loads only moves into setup
tables. Delta load data doesn't move into setup tables.
**RSA3 contains only setup table's data
Only Delta update data moves into RSA7/LBWQ/SM13 no full/delta
initialization loads data.
$$ Assign points dude if if really helps you $$
Hope it helps!