SAP Commissions – CDL Custom Inbound file Processing [BYOD]
In the today’s world, there is a growing trend of bringing your own data to load into table for pre-processing and consume. This means that businesses and sales organizations are increasingly taking responsibility for collecting, cleaning, and formatting their own data and inserting to EXT table and transfer it back to TCMP stage tables
There are several reasons for this trend. First, businesses and Sales often have access to datamart that is specific to their industry. This data can be more valuable than third-party data, as it is more likely to be relevant to the specific problem that the business or sales organization is trying to solve.
There are a few challenges associated with bringing your own data to load it table for pre-processing and consume. First, it can be time-consuming and expensive to provide it right format(ODI) to collect, clean, and format the data. Second, it can be difficult to ensure that the data is unbiased. Third, it can be challenging to customize the pre-processing steps for the data transfer to target tables.
Here are some tips for bringing your own data to load it table for pre-processing and consume:
- Start by identifying the data that you need. What data is relevant to your specific problem?
- Collect the data from a variety of sources. This could include social media, customer surveys, and product usage logs.
- Clean and format the data. This involves removing any errors or inconsistencies.
- Pre-process the data. This involves transforming the data to stage table format according to the original file types.
Bringing your own data to load into EXT table for pre-processing and consume can be a complex and time-consuming process. However, it is an important step that can help you to map and insert into Stage tables.
In below example, It is just a described with simple data and follow the steps as shown
Prepare the Sample Data
File name : <TENANT_ID>_CUSTOMUPLOAD_TST.txt
CAR_NAME,CAR_TYPE,STATUS,FLAG BMW,X1,ACTIVE,1 BMW,X5,ACTIVE,1 BMW,X3,ACTIVE,1 BMW,X6,ACTIVE,1
Create a custom HANA table.
CREATE COLUMN TABLE "EXT"."CUSTOM_CDL_UPLOAD"( "CAR_NAME" VARCHAR(255), "CAR_TYPE" VARCHAR(255), "STATUS" VARCHAR(255), "FLAG" VARCHAR(255) ) UNLOAD PRIORITY 5 AUTO MERGE;
Create a custom HANA procedure with one IN parameter as shown below:
Example: With IN Parameter
All custom inbounds require one IN parameter where CDL passes the filename. This can be utilized by the custom procedure as batchname if required.
CREATE PROCEDURE "EXT".SP_CUSTOM_CDL_UPLOAD(IN FILENAME varchar(120)) LANGUAGE SQLSCRIPT SQL SECURITY INVOKER DEFAULT SCHEMA EXT AS BEGIN END;
Define the custom inbound file type
Once you save the custom Inbound file type, it will be shown.
To run the inbound file type, drop a trigger file in the inbound folder of the SFTP Dropbox. The trigger file should have the same file type that is defined in inbound file type settings for the custom inbound file type.
you can preview the data through the table which got loaded.