To read data from an SAP S/4HANA application, configure an SAP ODP object as the Source transformation in a mapping.
Specify the name and description of the SAP ODP source. Configure the source and advanced properties for the source object.
The following table describes the SAP ODP Extractor source properties that you can configure in a Source transformation:
Property
Description
Connection
Name of the source connection.
Source Type
The source type.
Select from one of the following types:
- Single. Select to specify a single SAP ODP object.
- Parameter. Select to specify the SAP ODP object as a parameter.
Source Object
Source object for the task.
Select the source object from the list.
Preview Data
Not applicable
The following table describes the SAP ODP Extractor advanced source properties:
Property
Description
Data Fetch Mode
The data fetch mode used while reading records from ODP.
You can select from the following options:
0-Full
Reads all the records for the selected ODP.
1-Delta Plus
Reads all records of the ODP from the SAP system and also initializes the Operational Delta Queue (ODQ) for the selected ODP in the subscriber that you defined in the SAP system when you run the mapping for the first time using this mode. Subsequently, use this mode to read delta data of the ODP from the SAP system.
2-Delta Only
Initializes the Operational Delta Queue (ODQ) for the selected ODP in the subscriber that you defined in the SAP system when you run the mapping for the first time using this mode. Subsequently, when you use this mode and run the mapping, the Secure Agent reads delta data of the ODP from the SAP system.
3-Repetitive
Extracts delta records of the last delta run.
For example, use this mode when the mapping with the Delta Plus or Delta Only option fails, and you want to read the last delta again.
Parameter
Use this option when you want to parameterize the data fetch mode values. Specify a valid data fetch mode value in the Parameter Name for Data Fetch Mode field.
Parameter Name for Data Fetch Mode
The parameter name that you defined for the Data Fetch Mode property in the parameter file.
You can specify the following values for the data fetch mode:
- 0 for Full
- 1 for Delta Plus
- 2 for Delta Only
- 3 for Repetitive
If you pass any other value, the jobs fail when you run the mapping.
Job Timeout
Defines the maximum amount of time in minutes while processing the mapping during which the Secure Agent machine must wait before it receives communication from SAP and get the data packets.
Default is 120.
The timeout applies only when the Secure Agent machine waits for SAP to send the data packets. Do not modify the default value.
Packet size in MB
The packet size of each SAP data packet while reading data from SAP S/4HANA.
Default is 8 MB.
To increase the default packet size, you need to increase the Java heap memory for the Secure Agent machine.
Sets the amount of detail that appears in the log file.
You can choose terse, normal, verbose initialization or verbose data.
Default is normal.
Increasing the heap size
To increase performance and avoid run-time environment memory issues, you need to increase the Java heap size for the Secure Agent machine.
1Select Administrator > Runtime Environments.
2On the Runtime Environments page, select the Secure Agent machine that runs the mapping.
3Click Edit.
4In the System Configuration Details section, select Data Integration Server as the Service and DTM as the Type.
5Edit the JVMOption1 system property and set the value to Xmx512m.
6Click OK to save the changes.
Operators in source filter expressions
To filter data from SAP ODP source objects, you need to add the required operator in a filter expression and define the filter expression in the task.
You can use the following operators in a filter expression:
•= (Equal to)
•<> (Not equal to)
Consider the following guidelines to add operators in a filter expression:
•You can't filter data when you use the < (Less than) or > (Greater than) operator.
•To filter values within a range, you need to add both the <= (Less than or equal to) and >= (Greater than or equal to) operators together. But when you add the <= (Less than or equal to) or >= (Greater than or equal to) operators separately, the mapping doesn't filter values.
For example, to filter values within a range of >=3 and <=10 from the FFLTP field of the ZINFA_ALLDATATYPES object when the SAP ODP source is available in the DataSources or SAP Extractors context, add operators in the following format:
- DataSources or SAP Extractors/ZINFA_ALLDATATYPES.FFLTP >= '3'
- DataSources or SAP Extractors/ZINFA_ALLDATATYPES.FFLTP <= '10'
The following image shows the configured data filters that filter values within a range of >=3 and <=10 from the FFLTP field:
Rules and guidelines for SAP ODP source objects
Consider the following rules and guidelines for SAP ODP objects used as sources in mappings and mapping tasks:
•Only the available contexts in the selected SAP system appear as packages.
•Ensure that the required ODP is activated in the SAP system before you can use in Data Integration. Only the activated ODPs appear in the browser list of the SAP ODP Extractor Connector.
•If the ODP name contains namespace (“/”) characters at the beginning, the Secure Agent replaces those characters with T__. Every subsequent namespace character in the ODP name is replaced by “__”. For example, if the ODP name is /IMO/CMSD17, it appears in the browser list as T__IMO__CMSD17.
•If the field name of the selected ODP has a namespace character (“/”), that character is replaced with an underscore (_) character.
•Do not edit the field metadata as it might corrupt the extracted data.
•Partitioning is not applicable with filters and hierarchal data sources.
•You can read delta data for ODPs that are supported in the SAP system. If you try to run the delta mode for ODPs where the ODQ is not maintained in the SAP system, a runtime error occurs. If the ODQ is not applicable for contexts such as HANA and ABAP CDS views, delta data fetch modes are not applicable.
•You can apply filters only for the selected fields of the ODPs. You can identify those fields with the attribute Filterable marked as Y. If you apply filters on any other fields, it results in a runtime error.
•Sorting of data is not applicable.
•You cannot use more than one SAP ODP source in a Joiner transformation.
•To search SAP ODP source objects that contain similar string in the object name, enter a string of the object name that you want to search and add the asterisk wild card character to the beginning or end of the search string based on the search requirement.
For example, to search for all SAP ODP source objects that contain the string 0BUCKET in the object names, enter 0BUCKET* in the Search field.
