(Glue-2308) Extraction of Advanced DSO

In the simplest scenario of Advanced DSO replication, there are four components forming each of the replication processes – Glue Table, Advanced DSO fetcher, Glue Table consumer, and Extraction Process. These four components represent a configuration – setting up the source object, target object, and transformation rules. Following steps navigate you through the preparation of the whole flow – creating all required objects and executing the load.

  1. Creating Glue table:

    1. Start transaction /DVD/GLUE and click Data Dictionary.

    2. Enter the name of a new table and click Create. You can enter the description of the table.

    3. Under the Attributes tab fill in the Storage ID (for binary storages necessary to fulfill the File storage options, too).

    4. Under the Fields tab field GLREQUEST with data type: DEC, length: 30, dec places: 0 is added automatically.

    5. Under the Fields tab click on Import Fields, choose From InfoProvider and fill in the name of the ADSO. If you check the checkbox Navigational attributes, the fields corresponding to navigational attributes will be also added. The structure from the source Advanced DSO will be imported. You can manually adjust the fields as required.

    6. Click Save. If the table was not saved before, the system will ask you to fill in the Package. If you have a development package created upfront designated for SNP Glue development, you can use that package. Otherwise, for isolated sandbox purposes, $TMP will do.

    7. Activate by clicking on Activate button. Only after you activate the SNP Glue table, it is created on storage.


  2. Creating Advanced DSO Fetcher:

    1. Start transaction /DVD/GLUE and click Object Navigator.

    2. In the context menu (right-click) of the desired package select Create Extractor 2.0 object.

    3. A pop-up appears. Enter the name of the new Fetcher in the Object name.

    4. Select Advanced DSO Fetcher in the Component type dropdown and confirm the pop-up.

    5. Fill in the Advanced DSO by the required Advanced DSO name and press ENTER. For a basic scenario, we will leave the Delta type to FULL. Further options can be found in the detailed fetcher documentation.

    6. The fields from Advanced DSO will be added to part Filter definition. If you want to load data with a selection (filter on some fields), check the checkbox in column Selection for these fields. The section Recordmode selection is related to Delta type: Request, so in this case we can leave it as default.

    7. Activate the fetcher.



  3. Creating Consumer:

    1. Run the transaction /DVD/GLUE and open Object Navigator.

    2. In the context menu(right-click) of the desired package select option Create Extractor 2.0 object.

    3. Enter the name of the new Consumer in the Object name and select Consumer under the Component type dropdown and the GLUE table consumer under the Component implementation dropdown.

    4. Confirm the pop-up.

    5. After creation, the object is in the saved state. Fill in the Glue table name and press ENTER.

    6. Activate the consumer.



  4. Creating Extraction Process:

    1. Start transaction /DVD/GLUE and open Object Navigator.

    2. In the context menu (right-click) of the desired package, select the option Create Extractor 2.0 object.

    3. Enter the name of the new Extraction Process under the Object name.

    4. Select Extraction Process under the Component type dropdown and under the Component implementation dropdown.

    5. Confirm pop-up.

    6. Insert the Fetcher name and Consumer name created in the steps before. Press ENTER.

    7. Suggest transformation mapping button in the toolbar. The mapping between target and source fields is now created in a 1:1 fashion. Further options for modification of the rules are described in the documentation.

    8. Activate extraction process.



  5. Executing Extraction Process:

    1. Click Execute.

    2. Execute(F8) the replication with default settings. Select Background and Immediate in upcoming pop-ups for scheduling SAP jobs.