Please be informed that we must be cautious to extract large volumes of data directly from ECC systems as it may impact on the performance of the system.If possible, we should utilize the data warehouse (BW)
Please be informed that we must be cautious to extract large volumes of data directly from ECC systems as it may impact on the performance of the system.
If possible, we should utilize the data warehouse (BW)
The connection to SAP PF1 is already in the context g_CNX_SAP_PF1
The connection to SAP WP1 is already in context g_CNX_SAP_WP1
From the ECC, we can extract only information from the table. To get metadata it is highly recommended to get if from
1.1 Retrieve metata
Metadata > SAP Connection > (Server) > right click and select Retrieve SAP Table
Search the table and click finish
1.2 Copy the reference job ECC_Table_to_GCS to the new job
1.3 The only change is on the table object tSAPTableInput
Drag and drop the metadata table object to the new job and ensure that the schema, table name, filter, number of records are correct.
1.4. Click on the sync column to get the new schema on tLogRow if you want to see the output during the run of the job or delete this job
1.5 Add the context g_CNX_SAP_xxx on the server that need to be connected.
1.6 Enter the parameter context to connect to GCP
| CONTEXT VARIABLE | MEANING |
|---|---|
| l_VAR_FILE | local folder to save the output from the extraction |
| l_VAR_GCS_CSV_TO_STAGING_BUCKETNAME | It is the name of the bucket containing the file to download. |
| l_PATHDIR_GCS_CSV_TO_STAGING_SERVICE_ACCOUNT_PATH | location of the JSON file to access the GCS |
The rest of the job will extract the data from SAP and generate the file on the local folder, then upload it to the bucket that we enter in point 1.6