Configuring LO Cockpit in BW4HANA

Logistics Data Extraction Configuration

Below figure illustrates the logistics data flow from ECC tables to BW

Customizing Cockpit: LBWE

The extraction structure and DataSources are maintained in the logistics extraction structures’ Customizing cockpit in transaction SBIW.

Maintain Extraction Structure: Example

During this step, one can select which fields needs to be transferred to BW. One can add or remove fields from the extract structure.

Maintaining DataSources

Note:

The extract structure for LO cockpit cannot be enhanced using SAPI function enhancement. Instead one can assign fields from communication structure or use enhancement options provided by LIS communication structure.

The logistics extraction structure customizing cockpit (LBWE) contains following functionality:

• Maintaining extraction structure
• Maintenance of Datasources
• Activation of updating
• Job control
• Update mode
• Initialization/Setup
• Deleting content from restructuring tables (setup tables)

Maintaining Extraction Structure:

The extraction structure is filled with the assigned communication structures. You can only use selected fields from
the communication structures. SAP already delivers extraction structures, which you can also enhance. After you set up the extraction structure, the system automatically generates it.

Maintenance of DataSources:

Here you can select field if any should be hidden or if any should be allowed for selection of values.

Activation of updating:

Activate so that the structures start filling with data (either through online jobs or set up table filling)

Job Control:

Schedule jobs to run in background to fill the delta queue

Update mode:

Here you can set how data is updated to delta queue.

Initialization/Setup:

Set up tables are filled which are read during initialization. To enable the restructuring to be restarted after termination, assign a name to each background run of filling the set up tables.

The restructuring should run in the background.

Deleting content from the restructuring tables:

Always delete set up tables before filling them.

Maintaining DataSources (2):

There is a DataSource (for example, 2LIS_11_VAITM) with extraction structure (for example, MC11VA0ITM) in the OLTP system. A maintenance screen is displayed in which you can assign other properties to the fields of the extraction structure.

The following options are available:

● Selection fields
● Hide fields
● Cancellation fields (field is inverted when canceled (*-1))

Logistics Data Extraction to SAP BW

It is important that no one generates or changes application data during the initialization phase.

By using selective initialization of the Delta Process, the time needed to suspend application loading can be minimized.

Initialization Simulation

When you extract transaction data with the LO method, you need a restructuring.

The data is stored in cluster tables (_SETUP) from where they are read during the initialization run.

Filling the Restructuring Table

The restructuring process fills restructuring tables that are read during the initialization.

SAP recommends that you run this in simulation mode beforehand (the simulation mode is only possible in some application areas: SD customer sales orders, LE deliveries, SD billing documents).

A full update into SAP BW is also performed with the restructuring tables.

DTP: Delta Initialization

If you want to transfer data in delta mode, the process must be initialized at some point. To do this, simply run the DTP with Extraction Mode set to Delta . Assuming you do want to transfer data, do not select Data Init Without Data .

LO Cockpit Update Modes

The LO Cockpit has the following Update Mode options:

● Direct Delta
● Queued Delta
● Unseralized V3 update

Direct Delta

With this update mode, the extraction data is transferred directly to the delta queue with
every document posting. The sequence of the transfer therefore corresponds with the
chronological order of data creation.

Queued Delta

With queued delta, new and changed records are collected in an Extraction Queue and then
updated to the Operational Delta Queue with an update collection run. Depending on the
application, up to 10,000 records can be included in a LUW (Logical Unit Of Work) in the delta
queue per DataSource.

The logistics queue overview function (transaction LBWQ) is available for monitoring the
extraction queue.

Unserialized V3 Update

The extraction data is written to update tables with V3 update mode without consideration of sequence when transferred to ODQ.

Note: This method is generally not used.

Steps for LO data extraction

1. Transfer LO datasource from BI content (RSA5 and RSA6)
2. Maintain the extract structure (tcode LBWE)
3. Maintain the datasource and generate it again.
4. Create datasource in ODP SAP source system
5. Maintain aDSO
6. Maintain transformation between datasource and aDSO
7. Create a DTP with Extraction Mode set to Delta for example
8. Set the extraction structure for updating to active (transaction LBWE).
9. Fill the restructuring table (OLI*BW)
10. Select the update method (V3 or direct delta)
11. Execute the DTP to update from set up tables
12. Start V3 collection run (tcode LBWE) (this step is not required for direct delta update mode)
13. Schedule the Delta DTP in a process chain.
14. Delete the contents of the set-up table. (tcode LBWG)