Use the following rules and guidelines when you configure SAP ADSO targets:
•Only the activated ADSOs appear in the browser list of the SAP ADSO Writer Connector. Ensure that the required ADSO is activated in the SAP system before you can use in Data Integration.
•If the ADSO name has namespace (“/”) characters at the beginning, the Secure Agent replaces those characters with T__. Every subsequent namespace character in the ADSO name is replaced by “__”. For example, if the ADSO name is /IMO/CMSD17, it appears in the browser list as T__IMO__CMSD17.
•Do not edit the field metadata as it might corrupt the extracted data.
•If the field name of the selected ADSO has a namespace character (“/”), the Secure Agent replaces it with an underscore “_” character.
•When you define a mapping, you must select the operation as Insert. While activating, SAP BW/4HANA uses its algorithm to handle loaded data. You do not need to set any additional property in Data Integration to perform update or delete operation. Operations such as update and delete are handled at the SAP BW/4HANA layer itself.
•Ensure that data with the different data types that you load to BW/4HANA is correct. The activation of the loaded packet might fail if the inserted data is incorrect.
•The Secure Agent does check the validity of the data according to the supported transformation data type. However, if the data is incorrect, the Secure Agent loads the data to SAP BW/4HANA, but fails during the data activation. Ensure that the data is valid according to the data type of the fields.
•The default packet size to write data is 8 MB. When you set the packet size value equal to greater than 8 MB and you encounter out-of-memory issues, you can increase the Java heap memory for the Secure Agent. In the System Configuration Details section of the Secure Agent properties, select DTM and set the JVMOption1 property to the following value: Xmx512m. Click OK to save the change and then restart the Secure Agent. Adjust the value for the JVMOption1 property based on the amount of records you want to write and the available memory on the Secure Agent machine.
•The default precision for variable length data types such as STRING and RAWSTRING is set to a higher value of 1333. To manage the optimal record length, you must, however, set the length for these data types in the of the mapping based on the expected length of the actual data.