Skip to content
This repository has been archived by the owner on Jul 2, 2022. It is now read-only.

Latest commit

 

History

History

ex2

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
images
images
 
 
pipelines
pipelines
 
 
README.md
README.md
 
 

README.md

Exercise 2 - Triggering the execution of a function module in a remote S/4HANA system

So far, we have missed to proof whether or not our ABAP CDS Views and the consuming Data Intelligence Pipelines are really providing delta information. This would require access to the S/4HANA system in order to conduct changes on the data basis, hence on the Business Partner table or on the Sales Order object.

The Enterprise Procurement Model (EPM) demo application comes with a report that allows you to generate EPM Sales Order data. This report SEPM_DG_EPM_STD_CHANNEL can be started with the transaction SEPM_DG in S/4HANA.

Here is an example of how the Report looks like in the SAP GUI:



As a matter of fact, we couldn't provide an SAP GUI based access to the connected S/4HANA system. For still being able to trigger changes on EPM data in that system, we have created a variant of the above report SEPM_DG_EPM_STD_CHANNEL and a Custom ABAP Operator customer.teched.socreate which executes this report variant.

FYI, the following lines in the Local Class lcl_process, which instantiated by the NEW_PROCES( ) method of the Operator Class ZCL_DHAPE_OPER_CREATE_SO, implements this functionality:

  METHOD on_data.
    DATA lv_data TYPE string.
    mo_in->read_copy( IMPORTING ea_data = lv_data ).

    SUBMIT SEPM_DG_EPM_STD_CHANNEL USING SELECTION-SET 'SEPM_TECHED_SO' AND RETURN.
    lv_data = ' --> One additional EPM Sales Order with five related Sales Order Items created.'.

    mo_out->write_copy( lv_data ).
  ENDMETHOD.

You are asked to leverage this Custom ABAP Operator in this exercise with the goals to - experience how the execution of ABAP Function Modules in a remote S/4HANA system can be triggered from SAP Data Intelligence Pipeline and - finally have an approach to change data on the Enterprise Procurement Model in S/4HANA in order to verify the delta capabilities of the ABAP CDS Views and your Pipeline implementations.

Important Note
Please consider that we are working on the same central data basis (the EPM tables in S/4HANA) which is used by all workshop participants. Hence, Sales Order records that you create by using the Custom ABAP Operator will become change data for all session participants.

Exercise 2.1 - Making custom ABAP Operators available in SAP Data Intelligence

After completing these steps you will have created a Pipeline that triggers the execution of a Function Module in the connected S/4HANA for EPM data generation.

  1. Log on to SAP Data Intelligence and enter the Launchpad application. Then start the Modeler application.

  2. Make sure you are in the Graphs tab of the Modeler UI (see left side). Then click the + symbol in order to create a new Pipeline.



  3. Now a new Pipeline canvas is opened on the right side and the Modeler UI automatically switches to the Operators tab (see left side). In the list of operators, drag the Custom ABAP Operator and drop it into the Pipeline canvas. Click the ABAP CDS Reader node in the canvas one time and then click the configuration icon.



  4. In the configuration panel for the Custom ABAP Operator, specify the S/4HANA Connection: Select S4_RFC_TechEd. Then click on the ABAP Operator selection icon.



  5. In the pop-up windows, select the "Creation of EPM Sales Order" option. Then click OK.



  6. From the list of Operators, drag the Terminal operator into the Pipeline canvas. Connect the output port of the Custom ABAP Operator with the input port of the Terminal operator. Then connect the output port of the Terminal operator with the input port of the Custom ABAP Operator.
    With this Pipeline setup, we can - from the Terminal UI - trigger the ABAP Operator call and the reception of confirmation message at the same time.



  7. Save the Pipeline and enter the following parameters prompted in the pop-up windows:

    • Name: teched.XXXX.EPM_FM_Call_SO_Generator, where XXXX is your user name, for example "teched.TA99.EPM_FM_Call_SO_Generator"
    • Description: XXXX - Generate EPM SO data via ABAP FM call, where XXXX is your user name, for example "TA99 - Generate EPM SO data via ABAP FM call"
    • Category: `dat262'.

  8. Run your Pipeline. After the Pipeline status has changed from pending to running, right-click on the Terminal operator and click on Open UI.



  9. In the Terminal UI, put the cursor to the prompt line ('SDH >') on the lower section of the UI and press RETURN. In the upper part of the UI, you can then see the confirmation from the S/4HANA ABAP Operator than one Sales Order Header record and five related Sales Order Items have been generated.



Congratilations, you have successfully implemented a Data Intelligence Pipeline that triggers the execution of a function module in S/4HANA and allows direct interaction! In the next section, you can leverage this remote data generation option to verify the delta capabilities of our previously built Pipelines for ABAP CDS View based data replication.

Exercise 2.2 - Using a custom ABAP Operator to verify your Delta Replication of EPM Sales Orders

You can now test the delta processing capabilities of the ABAP CDS View based data extraction. A nice task would be to check if Pipeline for Sales Orders replications and enrichment that you have built in Exercise 1.4 - Extend the Pipeline for joining Sales Order with Customer data for each change in Sales Orders and persist results in S3 is really processing the delta records from EPM in S/4HANA.

  1. For so doing, change to the Graphs tab of the Modeler UI (see left side). Then enter your user name in the search field (if you made your user name a part of the Pipeline names or descriptions) and start the search. You will now get a list of the Pipelines that you have implemented. Click on your 'Sales Order Replication and Enrichment' Pipeline icon. If the displayed name is too short to recognize a unique name, just hover with your mouse over the Pipeline icons (see below).



  2. The Pipeline is opened in the canvas area of the Modeler UI. Run it.



  3. If you see that both of your Pipelines (data generating as well as data replication and enrichment) are in a running status, open the Wiretap UI.



  4. You can see now that the initial load from the ABAP CDS View in S/4HANA was successfully conducted. Please leave the Wiretap UI open.



  5. On the tab bar of the canvas area, switch to the Data Generation Pipeline and open the Terminal UI.



  6. Put the cursor on the prompt of the lower part (input part) of the Terminal UI and press RETURN. You will see the confirmation from the ABAP Operator about the records created in the EPM demo app.



  7. In the Browser switch back to the Wiretap UI of your Replication and Enrichment Pipeline. You should now see that a message with new records came in, which all have the "U" indicator for Updates. This verifies the delta-enablement of the ABAP CDS View and the immediate integration with Data Intelligence.



  8. Now please throw one last inspecting glance at the files on S3. Here, you can again use the data browser feature in the Data Intelligence Metadata Explorer. Open the application via the Launchpad.



  9. In the Metadata Explorer main screen, click on Browse Connections.



  10. Click on the Connection "TechEd2020_S3" and drill further down to the folders "DAT262" and that of your user (e.g. "TA99").



  11. Click on the More Actions menue (the three dots) of the file Enriched_Sales_Orders - that contains the delta records - and click on View Fact Sheet.
    (Remark: this file get overwritten with each data update as S3 does not provide append capabilities. If you would like to preserve the complete history, you can still add a File Reader and then a File Writer operator the to Pipeline behind the Structured File Writer. The latter does appends in memory and writes back the completed full recordset to S3.)



  12. You can now see that also the processing of the delta data within the Pipeline to S3 worked seamlessly. The delta records contain the enrichments and the "U" indicator that with which updates are flagged by the ABAP CDS View CDC framework.



Very well done! You successfully followed the integration approach for data processing and functional execution between S/4HANA and SAP Data Intelligence and know how to realize such implementations.

Summary

In the Deep Dive demos and in the Exercises, we have jointly worked on the implementation of delta-enabled data sources and remote functionality in S/4HANA and have leveraged these features directly in SAP Data Intelligence. We could now extend these use cases for more complex scenarios. The general implementation approaches and the support that the Data Intelligence applications provide would then still be the same.

In case you have asked yourself if there are similar options for the integration with other ABAP systems such as ECC or BW, the answer is 'yes'! In these cases, you can make use of the unmodifying DMIS add-on, which provides the ABAP Pipeline Engine also for these systems.

This given, you can realize real-time replication scenarios via SLT integration to SAP Data Intelligence, leverage the ODP Reader operators, and also trigger function module execution on ECC or BW systems, too.

More information can be found here.

THANK YOU VERY MUCH for having participated in this Deep Dive and Hands On workshop. We hope you have enjoyed it!

Bengt Mertens and Tobias Koebler

Related TechEd2020 Lectures and Workshops




Table of Contents / Navigation