- Inbound and Outbound Transfers
PREVIOUS | NEXT
Inbound and Outbound Transfers
A typical Extract, Load and Transform pattern would involve 4 primary stages as illustrated below. Data is first loaded into the EXT Schema typically where it is transformed, cleansed, and validated before being loaded into the Commissions Staging tables. After data is loaded into the staging tables, a flowgraph calls the ODATA API (using ODATA adapter) to execute the Commissions Pipeline to import data from the Staging tables to the main Commissions tables. Users can use monitors to track agents and execution of tasks.
Stage 1: Data Federation
In the first stage, data is federated in the virtual table in DB Explorer from the remote data source.
Pre-requisite: Create a remote source in the HANA tenant database via Web IDE DB Explorer to be able to create virtual tables.
Ensure the following steps are performed:
- Set up SDI DP Agent connection to the SDI DP Server.
- Turn the adapter on.
- Create a remote data source in the HANA DB via Web IDE DB Explorer. The remote source is required to create a virtual table.
- Create a virtual table.
Stage 2: Load Data
In this stage, data is loaded into the EXT schema table from the virtual table. Typically, users create the same table structure in EXT schema as in the source table and then load data. This step is executed using flowgraphs that are built in Web IDE.
Transformations are possible in this stage but are not performed since this is mainly an Extract and Load step.
Stage 3: Transform Data
In this stage, data is transformed and moved from the EXT schema table to the TCMP schema table. This step is executed using flowgraphs that are built in Web IDE.
Stage 4: Invoke OData API
In the final stage, data is moved to the main Commissions table from the TCMP table.
To achieve this, the SAP Commission Pipeline is triggered. Once the Commissions Pipeline is executed, data is moved from the TCMP stage table to TCMP main table.
Commissions Pipeline can be triggered using:
- Option 1: Calling SAP Commission OData API. This option is available with the SAP Commissions 1905 release and the details are illustrated in this topic.
- Option 2: Creating a flowgraph using Web IDE which uses the OData remote source. This option will be available with SAP Commission 1908 release.
Important: WEB IDE Project (Use, Function, Access)
Web IDE project uses the HDI (HANA Deployment Infrastructure) service layer to deploy HANA database artifacts. HDI also introduces HDI container for database. HDI container is essentially a database schema. It abstracts the actual physical schema and provides schema-less development to the Web IDE project. The physical schema is abstracted by the HDI container. Only local object (HDI container schema) access is allowed from the Web IDE application. Two technical users (Object Owner and Schema Owner) are also created. Technical users have access to only the local objects. Any foreign object (such as tables in EXT and TCMP schema) must be accessed via Synonyms and must be granted access by the foreign technical user (tenant database user).
- Create Web IDE project
- Create SAP HANA Service to connect with SAP Commission HANA DB
- Create Synonym for virtual table and EXT schema table
- Build the project and grant access to virtual and physical tables to Object Owner as shown in the below example:
- GRANT SELECT, INSERT, UPDATE, DELETE ON "SCHEMA"."VIRTUAL_TABLE" to TECHNICAL_USER_1#OO;
- GRANT SELECT, INSERT, UPDATE, DELETE ON "SCHEMA"."PHYSICAL_TABLE" to TECHNICAL_USER _1#OO;
Note: To speed up with Web IDE Project and the concepts described in this article, we recommend that you check the following Github Repository for a sample Web IDE project: https://github.com/I027369/commission_sdi. GitHub helps you migrate flat file data (by acting as a data source) to a table in TCMP schema.