The Palantir Foundry Connector 2.0 for SAP Applications ("Connector") provides methods to extract data from ABAP reports or transaction codes which are assigned to an ABAP report in the SAP Application Server. Only reports which use ABAP List Viewer are supported.
Only reports using ABAP List Viewer (ALV) are supported.
tcode syncs can only be created from the Advanced tab of the sync configuration UI.
Use the tcode object type to extract data generated by transaction codes.
If you know the transaction coed name, provide it as a value to the obj parameter.
Example sync configuration:
Copied!1 2 3type: magritte-sap-source-adapter sapType: tcode obj: ZTEST_ALV
If you only know the program name of the report, you can provide the program name as the obj parameter and set the programType parameter to program.
Example sync configuration:
Copied!1 2 3 4type: magritte-sap-source-adapter sapType: tcode obj: RSUSR200 programType: program
Additional parameters are supported when configuring transaction code extraction:
Multiple parameters can be defined in the same sync.
The filter parameter is used to pass the user inputs for selection screen variables. It not act as an arbitrary filter on any output fields of the report.
Example sync configuration:
Copied!1 2 3 4type: magritte-sap-source-adapter sapType: tcode obj: ZTEST_ALV filter: p_spras=EN
The selectionVariant parameter is used to pass the selection screen variants of the program. Selection screen variants are predefined filters created in the selection screen of the program.
If the selectionVariant and the filter parameters are defined at the same time, the filter will overwrite the existing values of selection screen parameters in the variant.
Example sync configuration:
Copied!1 2 3 4 5type: magritte-sap-source-adapter sapType: tcode obj: RSUSR200 programType: program selectionVariant: USER_DISKOVER
The outputVariant parameter is used to pass the layout name of the program, changing the output of the data. Only programs having a layout parameter defined on SAP's selection screen.
Example sync configuration:
Copied!1 2 3 4type: magritte-sap-source-adapter sapType: tcode obj: ZTEST_ALV outputVariant: /COMMERCIAL
The ingestionType parameter can be used to send the output of a report to a printer queue before ingesting it, commonly known as a "spool request". Setting ingestionType to spool is recommended for reports producing data that exceeds the limit of SAP's internal tables.
By default (if ingestionType is not specified), the output of a report is ingested on the fly and sent to Foundry.
Due to the nature of spool requests, when using the spool ingestion type, all columns will have type String when ingested to Foundry.
Example sync configuration:
Copied!1 2 3 4type: magritte-sap-source-adapter sapType: tcode obj: ZTEST_ALV ingestionType: spool