SAP ABAP IMG Activity BWLIS_COCKPIT_LBWE (Activate/Edit Extraction Structures)
Hierarchy
SAP_APPL (Software Component) Logistics and Accounting
   LO-LIS (Application Component) Logistics Information System (LIS)
     RS_IMG_LIS (Package) OLTP-IMG LIS (Logistics Information System)
IMG Activity
ID BWLIS_COCKPIT_LBWE Activate/Edit Extraction Structures  
Transaction Code S_AX6_42000029   IMG Activity: BWLIS_COCKPIT_LBWE 
Created on 19990930    
Customizing Attributes BWLIS_COCKPIT_LBWE   Logistics Extraction Structures Customizing Cockpit 
Customizing Activity BWLIS_COCKPIT_LBWE   Logistics Extraction Structures Customizing Cockpit 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name BWLIS_COCKPIT_LBWE    

The aim is to manage extract structures, used to transfer Logistics movement data from OLTP into the BW.

The extract structures are completed using the communication structures in the Logistics Information System (LIS).

The Cockpit contains the following functions, entered in the following sequence:

  1. Maintenance of extract structures

    Each extract structure can be maintained by SAP or by you. The extract structures are provided from the assigned communication structures. You can only use selected fields from the communication structures. SAP already delivers extract structures. You can enhance these. After creating the extract structure, they are automatically generated. During this process, the missing fields (related units and features) are completed. The extract structure is created hierarchically in accordance with the communication structures. Each communication structure leads to the generation of a sub-structure of the actual extract structure.

  2. Maintaining InfoSources

    At this point, call up general maintenance of InfoSources. Here you can set the selection of selectable fields and the negativability of fields.

  3. Activating the update

    By setting as active, data is written into the extract structures, both online as well as during completion of setup tables. (see below).

  4. Job control
  5. Depending on the Update Mode you have set (see next section), a job may have to be scheduled, with which the updated data is transferred in the background into the central delta management.
  6. Update Mode

    Here, you can set how the incurred data is updated during delta posting:

    1. Serialized V3 Update
    2. This is the normal update method. Here, document data is collected in the order it was created and transferred into the BW as a batch job.
      The transfer sequence is not the same as the order in which the data was created in all scenarios.
    3. Direct Delta
    4. In this method, extraction data is transferred directly from document postings into the BW delta queue.
      The transfer sequence is the same as the order in which the data was created.
    5. Queued Delta
    6. In this method, extraction data from document postings is collected in an extraction queue, from which a periodic collective run is used to transfer the data into the BW delta queue.
      The transfer sequence is the same as the order in which the data was created.
    7. Unserialized V3 Update
    8. This method is almost exactly identical to the serialized update method. The only difference is that the order of document data in the BW delta queue does not have to be the same as the order in which it was posted. We only recommend this method when the order in which the data is transferred is not important, a consequence of the data target design in the BW.

Example

Requirements

Standard settings

Recommendation

Activities

Further notes

For Release 4.0b and 4.5b set the cursor on the corresponding line for each step and press the relevant button. As from Release 4.6a, all steps go directly via the links.

If the communcation structures are to be extended to new fields, using Customer exits and append technologies, these can also be recorded in in the extract structures. If you select such a new field, an append structure is created to the extract structure.

Business Attributes
ASAP Roadmap ID 207   Establish Reporting 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 1   Critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG BWLIS_COCKPIT_LBWE 0 HLA0006426 Data Collection 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
IMGDUMMY D - Dummy object LBWE BWLIS01 Logistics Extraction Structures Customizing Cockpit 
History
Last changed by/on SAP  20110112 
SAP Release Created in