• The extraction structure and the datasource are
  maintained in LBWE
• Maintain extract structure – you can enhance the SAP
  delivered ones
• Maintain Data source – select the selectable fields and
  fields that can be negated
• Activate the extraction structure – when you activate,
  data is written to the extraction structures
  immediately
• Job Control – Schedule the job
• Update mode – how the update should happen from
  the extractor queue to delta queue (Unserialized V3,
  Direct and Queued)
• Initialization/ set up – assign a run name so that it can be restarted after
  termination – this should always run in background.
• Delete set up tables before and after initialization for performance
  reasons
• The extraction structure is filled with the assigned SAP communication
  structure.
• You can only use selected fields from the communication structure
• SAP internal control fields for example, are not available. User appends to
  the communication structure are available.
• SAP already delivers extraction structures, which you can enhance (by
  connecting to the communication structure)
• Every comm struc leads to the generation of a sub struc that belongs to
  the actual extract struc
• Collection run can be triggered by program RMBWV3**, where ** is the
  application.

Steps for LO extraction

Step 1 – Transfer the lo datasource for
transaction data from Business content
-RSA5/RSA6

With the transfer of datasource, the associated extraction
structure is also delivered. Set up table is also generated.

Datasource naming convention –
2LIS_<Application>_<Event><Suffix> e.g. 2LIS_11_VAITM

Extraction structure naming convention –
MC<Application><Event>0<Suffix> – MC11VA0ITM

Set Up table / restructuring table – <extraction
structure>SETUP e.g. MC11VA0ITMSETUP

Step 2 – Maintain extraction structure (LBWE)

Step 3 – Maintain / generate data source (after
enhancing the extract structure, the data source have
to be generated again)

Step 4 – Replicate and activate the data source in BI

Step 5 – Maintain Data Target

Step 6 – maintain transformations between data
source and data target

Step 7 – Create a DTP

Step 8 – Activate extraction structure – LBWE

Step 9 – Fill the set up tables (OLI*BW), before filling, delete the
contents in LBWG, during this process, no documents should be
created or changed in the system. In some applications, it is possible to
fill set up tables in simulation mode. The logs of these can be seen on
LBWF. Once filled, document editing can resume provided that the
unserialized V3 or queued delta is selected as the next step.

Make sure that no V3 collective run is started until the next successful posting of
the info package for delta initialization

Step 10 – Select update method (Unserialized V3 update, Direct or
Queued Delta)

Step 11 – Create an infopackage for the data source and schedule the
delta initialization in the scheduler. This updates the BI relevant data
from the set up table to the PSA. The set up table can now be deleted
in LBWG

Step 12 – Load this data in data targets from the PSA, now the
application document editing can resume if Direct Delta was selected
as the update method

Step 13 – Start V3 collective run (LBWE)

Step 14 – Create an info package for Delta
load and schedule it in BI

Enhancement of Business Content DS

Valid for both master and transaction data

E.g. Enhance 0MATERIAL to include old material codes

Steps –

• Delete the set up tables and outbound queue and delta queue for the
  data source
• Go to LBWE and select a data source. Click on the Maintenance.
  Include the fields needed
• Go to data source maintenance and unhide the fields. Generate the
  DS
• Activate the DS
• Reload the set up tables
• Check in RSA3, if data is coming for the field added
• Replicate the DS in BI and model the field in BI side and load the data

If the fields that need to be enhanced are not
present in the communication structure of the
data source, then we have to follow the below
steps to enhance the data source-

For Standard DS –

1. RSA6 – Double click on the DS – double click on the
   Extract structure – then click on Append structure

2. If the enhancement is done for the first time, you
have to create a new Append struct by specifying a
technical name.

3. Add the new field with prefix ZZ and specify there
component type. Check, save and activate the append
structure.

4. Unhide the fields in the DS

5. Go to CMOD, and choose a project or create a new one
with enhancement RSAP0001.

6. Click on Components – 001 for trans data, 002 for Master
data attributes, 003 for texts, 004 for hierarchies

7. Go to relevant enhancement and double click on include –
write code to include a program -go to se38 and create the
program. Save and activate.

8. Check the data in RSA3

9. BI side replication, modelling and load.

Transport Management of enhanced LO DS

• Make the active DS inactive – TR create – 1st
  request
• Click on DS maintenance button, prompt to
  create a workbench request – 2nd request
• Activate the DS – customizing request -3rd
  request
• Transport the requests in that order – 1st
  request, then 2nd, then 3rd

Checks to be maintained before transporting the requests

• Delete the set up table
• Empty the extraction queue – go to se38 and execute
  the program RMBWV3nn , then check extraction
  queue in LBWQ, the queue MCEXnn should not be
  present here if empty
• Execute the relevant infopackages and empty the
  Delta queue
• All users should be locked during the transport, so that
  there are no new postings to the application tables
  during the transport. Only ALEREMOTE and your own
  user id should be unlocked.

After the DS enhancement Transport

• Replicate the DS in BI
• Monitor the extractor queue (LBWQ) and
  delta queue (RSA7) if these are updated with
  entries or not.
• Execute the delta infopackage