Skip to content

Latest commit

 

History

History

ex2

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
images
images
 
 
README.md
README.md
 
 

README.md

Exercise 1.5 - 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. In case your pipeline EPM_SalesOrder_Replication_Enrich_to_S3 from exercise 1.4 is still running, you can directly go to step 5. In case you have stopped the pipeline, click on 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 'EPM_SalesOrder_Replication_Enrich_to_S3' 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).

    When searching for your pipeline, make sure you have selected the category da281 in the available categories.





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

  3. Make sure a Wiretap operator exists between the Get Header and To File Operator and the Sales Order to S3 Write File Operator:

    Note: In case you have kept the Wiretap Operator between Get Header and Write File before as described in Exercise 1.4 Step 4. you can ignore this step. In case you have removed it, please add the Wiretap operator inside your pipeline and add it between the Get Header and Write File Operator.



  4. Save the graph and now Run it



  5. If you see that the Pipeline changes to a running status, open the Wiretap UI.



  6. 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.



  7. Now create your own Pipeline for generating EPM Sales Order records like already shown in Deep Dive 2.2.
    In order to not have you navigating back and forth, all steps of that Deep Dive session for creating the Pipeline for EPM Sales Order creation are also included in this exercise document.

  8. In the DI Modeler, make sure you are in the Graphs tab (see left side) and click the + symbol and select Use Generation 1 Operators in order to create a new Pipeline.



  9. A new Pipeline canvas opens and the design focus automatically changes to the Operators tab (see left side). Drag the Custom ABAP Operator icon from the Operator list and drop it onto the canvas. Then do one click on the Custom ABAP Operator node in the canvas and open the configuration panel by clicking on the related symbol.



  10. In the configuration panel on the right side, select the ABAP Connection (RFC or Websocket RFC connection) to the SAP S/4HANA system that provides the ABAP Operator. If done, click on the selection button of the field for the ABAP Operator.



  11. From the pop-up window, select the custom ABAP Operator that you want to call from the Pipeline. In our case, it's the ABAP Operator that triggers the execution of a specific ABAP Report variant on the S/4HANA system, and sends a confirmation back to the DI pipeline. Hence, choose Operator Class: Creation of EPM Sales Order and click OK



  12. As you can see, the ABAP Operator node in the Pipeline canvas gets automatically updated with the operator's name in S/4HANA and the ports that we have defined in the previous section of this Deep Dive demo. (The GET_INFO( )method in our operator's ABAP class provides the corresponding meta information.)



  13. For verifying the functionality of the ABAP Operator call, we'll be using a Terminal Operator in the Pipeline. This operator allows the sending of user inputs and the reception of the results. Drag the Terminal icon from the Operator list and drop it onto the Pipeline canvas. Then

    • connect the output port of the ABAP Operator with the input port of the Terminal Operator and
    • connectthe output port of the Terminal Operator with the input port of the ABAP Operator.
    • Save the Pipeline.



  14. When saving the Pipeline, you are prompted for the name of the pipeline (including namespace information), a description, and the category under which the Pipeline can be found in the Graphs tab of the Modeler. Please 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: da281.
    • Finally click OK.



  15. You can now start the Pipeline by clicking the Play symbol in the menue bar.



  16. Change back to the Status tab of the status section in the Modeler UI. Once the status has turned to running, click one time on the Terminal node and open the Terminal UI with a click on the corresponding icon.



  17. In the lower section of the Terminal UI (the Input Prompt), you can now enter any input or just press Return in order to send a trigger signal to the ABAP Operator in S/4HANA. As a response for each input from our custom ABAP Operator, you will receive a confirmation message in the upper section of the Terminal UI, what proves our ABAP operator code functionality and the integration success.
    Now produce several Sales Order records.


  18. In the Browser tabs, 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.



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



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



  21. Click on the Connection "DI_DATA_LAKE" and drill further down to the folders "shared" --> "DA281" --> that of your user (e.g. "TA99").





  22. Browse into the specified folder inside your user folder Enriched Sales Order.



  23. Inside the folder, you will now see that a new CSV file has been generated for the changes that were triggered via the custom operator. Click on the More Actions menu (the three dots) of the newly created file - that contains the delta records - and click on View Fact Sheet.



    Please Note: In case you have stopped the pipeline after exercise 1.4 and restarted it in this exercise as defined in exercise 1.5, you will see an additional file in the S3 storage that represent a second initial load of our enriched Sales Order Data. The reason for this is that the second start of the pipeline using the Replication mode has triggered an additional initial load after starting the pipeline for the second time.



  24. You can now see that also the processing of the delta data within the Pipeline to the DI Data Lake 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.



  25. After checking the data that has been replicated to The DI Data Lake in the Metadata Explorer, please stop your running pipelines.



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.

Please proceed now to Exercise 2 - Integrate ABAP CDS Views in SAP Data Intelligence Replication Management Flow


Table of Contents / Navigation