Name: Transferring Data to the TCMP Schema in SAP SuccessFactors Incentive Management
Uploaded: 2020-8-7
Duration: 224 s
Description: This video will introduce you to two ways to move data from the staging table to the main table in the Commissions HANA database. One way is through the SAP SuccessFactors Incentive Management Web Application and the other is to validate and/or transfer the data through the OData API.

Share feedback

<p><u><strong>Planned maintenance of Practice Systems</strong></u></p>

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Choose your subscription

Manage your subscription

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div><div><div>This video will introduce you to two ways to move data from the staging table to the main table in the Commissions HANA database. One way is through the SAP SuccessFactors Incentive Management Web Application and the other is to validate and/or transfer the data through the OData API.  </div></div></div></div>

Transferring Data to the TCMP Schema in SAP SuccessFactors Incentive Management

Hi!  My name is Lily!  In this video, I’ll introduce you to two ways to move data from the staging table to the main table in the SAP Commissions HANA database. Once developers have added or changed data in the EXT schema, the data needs to be transferred to the staging table in the TCMP schema. Developers only have visibility into the EXT schema and the stage table. A Commissions pipeline is used to move the data from the stage table to the main table in the SAP Commissions HANA database. There are two ways to move this data. One way is through the Commissions Web Application to create a pipeline, which will validate and/or transfer data from the stage table to the main table. The second way is to validate and/or transfer the data through the OData API. I’ll give you a quick overview of each of the processes. I’ll start with the Commissions Web Application. I’ll select Run, then Pipeline. I’ll select the Run a Pipeline icon. I’ll select Import data from stage. I’ll enter a batch name. Then, I’ll select Validate and Transfer. You can also select only Validate or only Transfer. I’ll select the type of data to transfer. In this example, I’ll select New and modified organization data. Then, I’ll select the data I want to move from the stage table to the main table. A new pipeline run has been created. Once this is executed, the data will be moved from the stage schema to the main schema. The second way to create a Commissions pipeline is to move the data from the stage table to the main table by using the OData API. This is done by creating a flowgraph in Web IDE development. When the flowgraph is executed, it executes Create operation of OData API. This operation creates a new pipeline entry similar to the one created in the Web Application. I’ll show you an example. First, we need to create the remote source in the HANA Tenant database via DB Explorer. Second, we need to create a virtual table on the OData Entity. This virtual table works as a proxy for the Commission OData Pipeline entity. This is an example of a virtual table that shows the same pipeline entries as those in the Commissions solution. Note that only the first 1000 records are shown. The next step is to create a pipeline entry in the virtual table. Once the Commission application works on the pipeline entry, it moves the data from the TCMP stage table to the main table. This pipeline entry can be created using an SQL procedure. This procedure is created using DB Explorer. Once the procedure is executed, it creates a new entry in the virtual table to tell the Commissions application to validate and transfer the data for a specific module. In this example, we’re telling the Commission application to validate and transfer the data in the Classification Data module, in the Main Monthly calendar, and the start data is current or immediately. This is the same process as we saw in the Commissions web application. To execute this SQL procedure, we create a single node flowgraph and then connect it to the SQL procedure. Once this flowgraph is run, it’s called the SQL procedure execution. The SQL procedure logic creates a new pipeline entry run in the Commissions application. The data that I want to import from my stage table will be moved when the pipeline runs. In this video, I introduced you to two ways to transfer data from the EXT schema to the staging table in the TCMP schema. Thanks for watching!