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 init and full update to BW is generated.
Naming convention:
DataSource 2LIS_
optional
Examples:
2LIS_11_VAITM: 11 = SD Sales VA = sales order, delivery schedule ITM (→
ITEM) = document position
2LIS_02_HDR: 02 = MM purchasing HDR (→ HEADER ) = Document header
Extraction structure MC
where MC is derived from the associated communication structures and
Examples:
MC11VA0ITM: Extraction structure for the DataSource 2LIS_11_VAITM
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)
Example:
Extractton structure: MC11VA0IT ⇒ 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 (= Cancelation) 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 DataSource into the BW (=metadata upload)
5. Assign replicated DataSource to the InfoSource with flexible update
6. Maintain mapping and transfer rules & choose transfer method PSA
When the transfer rules are activated, the BW transfer structure (comprised of
fields from the replicated DataSource) is generated as a mirror image of BW in
the SAP system. With the PSA transfer method, during activation of the transfer
rules, in addition to the transfer structure, a PSA table is generated, the structure
of which is based on the transfer structure.
7. Define update rules for the data target (BasicCube/ODS object) in regard to
the InfoSource with flexible update
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. Fill 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 15).
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 BW-relevant data from the restructuring table to the data
target (BasicCube/ ODS object) using the ETL process (the same is valid for
a full update!). Since the restructuring table is not longer needed after delta
initialization, the content can be deleted (transaction LBWG).
After successful delta initialization, document editing can resume, as long as the
direct delta update method was selected in step 13. This means that BW-relevant
Δ data is written directly to the delta queue.
Note:
If the DataSource supports early-delta initialization, the Δ 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 13. By starting a corresponding job for an
application, the BW-relevant Δ data is read from the update tables or extraction
queue and written to the delta queue.
13. Create an InfoPackage for the DataSource in BW and schedule the Delta Update
in the Scheduler
The BW-relevant Δ data from the delta queue for the DataSource is updated to
the data target (BasicCube/ODS object) using the ETL process.
Extract Structures
2LIS_11_VAHDR – MC11VA0HDR – Sales Document Header
2LIS_11_VAITM – MC11VA0ITM - Sales Document Item
2LIS_11_VASCL – MC11VA0SCL – Sales Document Schedule Line
Setup Tables
2LIS_11_VAHDR - MC11VA0HDRSETUP
2LIS_11_VAITM - MC11VA0ITMSETUP
2LIS_11_VASCL - MC11VA0SCLSETUP
