The Palantir Foundry Connector 2.0 for SAP Applications ("Connector") supports the ingestion of various SAP object types within Foundry:
The table object type is used to extract data from database tables and views in an SAP Application Server. All tables and views in the SAP ABAP data dictionary are supported. It is also possible to extract from custom Z* tables.
Example sync configuration:
Copied!1 2 3type: magritte-sap-source-adapter sapType: table obj: MARA
The infoprovider object type is used to extract data from an SAP BW system. InfoProvider is the general description of the following objects:
The InfoProvider object uses standard SAP BW access methods; all authorization concepts from SAP BW are inherited.
Example sync configuration:
Copied!1 2 3type: magritte-sap-source-adapter sapType: infoprovider obj: Z3_C01
The bex object type is used to extract data from BEx queries.
See how to configure BEx queries for more details.
Example sync configuration:
Copied!1 2 3type: magritte-sap-source-adapter sapType: bex obj: ZCM_COMM_PRI
The slt object type is used to extract data from an SLT ODP Queue. SLT is a trigger-based replication tool from SAP Applications to target systems. The SLT ODP Queue is a target system in this object. The CDC (change data capture) mechanism is built into SLT. The Connector only adds timestamp information to the records coming from SLT.
Example sync configuration:
Copied!1 2 3 4 5type: magritte-sap-source-adapter sapType: slt obj: MARA context: SLT~P40 incrementalField: pointer
The extractor object type is used to extract data from SAP ERP Business Content extractors. Business Content extractors are ready-to-use structures designed to extract data from SAP applications. All business logic is included in the extractor, along with a CDC (change data capture) mechanism. If the extractor supports delta extraction, the APPEND transaction type should be used to ingest data incrementally.
See how to configure extractors for more details.
Example sync configuration:
Copied!1 2 3type: magritte-sap-source-adapter sapType: extractor obj: 0GL_ACCOUNT_ATTR
The function object type is used to extract data from SAP Applications with remote-enabled functions and BAPIs (Business APIs). SAP functions are a set of instructions for certain tasks in SAP, such as currency conversion, master data listing, and more.
See how to configure function extraction for more details.
Example sync configuration:
Copied!1 2 3 4type: magritte-sap-source-adapter sapType: function obj: BAPI_USER_GETLIST paramName: USERLIST
The data model object type is used to extract the relationships between ERP tables. These table relations are based on a standard primary key / foreign key model. A depth parameter can be set to indicate how many levels of relationships to follow when extracting the data model for a given table.
Example sync configuration:
Copied!1 2 3type: magritte-sap-source-adapter sapType: datamodel obj: T006
The tcode object type is used to extract data generated by SAP reports.
Only reports using ABAP List Viewer (ALV) are supported.
tcode syncs can only be created from the Advanced tab of the sync configuration UI.
See how to configure transaction code extraction for more details.
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
The hanaview object type is used to extract data from HANA Views enabled in the application layer.
See how to configure HANA views extraction for more details and pre-requisites.
hanaview syncs can only be created from the Advanced tab of the sync configuration UI.
Copied!1 2 3type: magritte-sap-source-adapter sapType: hanaview obj: ZEXT_SBOOK
The CDS view object type is used to extract data from ABAP CDS (Core Data Services) Views. ABAP CDS makes it possible to define semantic data models on the central database of the application server. The entities of these models provide enhanced access functions when compared to existing database tables and views defined in the ABAP Dictionary, making it possible to optimize Open SQL-based applications.
When connected via a remote connection, objects can be accessed in the same way as their "non-remote" equivalent with the same functionality. The only changes to make are:
remote to the object typecontext parameter to identify the remote systemExample sync config for a remote table:
Copied!1 2 3 4type: magritte-sap-source-adapter sapType: remotetable obj: MARA context: T50
Example sync config for a remote BEx query:
Copied!1 2 3 4type: magritte-sap-source-adapter sapType: remotebex obj: PAL16Q context: T50