SAP BW Errors and Fixes for Transports

Transport Further to the details mentioned in my first article ‘BW Transport Errors – Part 1’, we will have a look at other transport errors.


Common Transport Errors in Transformations/Update Rules:

Transport Error Log 1:
Error: Syntax Error in routine.
Reason: This error occurs if the transformation is not captured or transported successfully. Sections of the code are not reflected in the target system.
Fix: Recapture the transport in a new TR and send it across.

Transport Error Log 2:
Error: No Authorization
Reason: This error occurs if there is improper authorization in the target system. Especially as in above case a deletion TR was being imported and the ID did not have authorization to delete the objects in the target system.
Fix: Either get the required access to the ID or capture the objects in a ID which has authorization for the same.

Transport Error Log 3:
Error: Error when checking the update rules.
Reason: Correct update rule is not transported.
Fix: Correct any syntax errors in the update rule and re-transport it.

Transport Error Log 4:
Error: No rule exists
Reason: This error mostly occurs if all the related objects are not correctly captured.
Fix: Capture the object again through transport connection and send it across.

Transport Error Log 5:
Error: Syntax Error in the routine
Reason: The routine /transformation transported have syntax errors.
Fix: Correct the syntax errors in the development system and then re-transport the same.

Transport Error Log 6:
Error: Error when activation transformation/Error during generation.
Reason: The routine /transformation transported have syntax errors.
Fix: Correct the syntax errors in the development system and then re-transport the same.

Transport Error Log 7:
Error: Error during generation
Reason: This error might occur due to incorrect support pack version. The error here is in the standard program rather than any routine in the transformation.
Fix: Capture the transformation again in a transport and re-transport.

Transport Error Log 8:
Error: Settings for material number conversion not found.
Reason: This error occurs when trying to transport many transformations and DTP’s in the same TR.
Fix: Split the objects in different TR’s and re-transport.


Common Transport Errors in DTP:

Transport Error Log 1:
Error: Overlapping Selection criteria with DTP
Reason: This error occurs while transporting a DTP. The reason for this is two ‘DELTA’ DTP’s between same source and target cannot exist. There is another DTP in the target system which exists with ‘DELTA’.
Fix: Either deletes the DTP in the target system, or transport a DTP with ‘FULL’ mode or transport the same DTP as exists in the target system.

Transport Error Log 2:
Error: Program Terminated
Reason: The return code 12 could occur for various reasons. This could be if the system logs are full, or if the transport route has some issues. This can be analyzed from the job log or short dump in most cases.
Fix: The error here could be for various reasons; hence the fix can be determined accordingly. One other reason why this error occurs is , if a cube has a BWA index or aggregate built on it and we are trying to transport any changes ( Adding a field or enabling a navigational attribute) to that cube it fails with a similar error. In such cases we can delete the BWA Indexes and Aggregates and then re-import the transport. After the transport has been re-imported we can rebuild the BWA Indexes/Aggregates. This will fix the issue.

Transport Error Log 3:
Error: Operation could not be carried out for a DTP.
Reason: This error mostly occurs if we try to make some changes to the delta DTP.
Fix: Check if the changes to settings are being done is impacting the delta process. If yes, please revisit the changes.

Other Common Transport Errors:

Transport Error Log 1:
Error: Generation Error
Reason: This error mostly occurs when trying to transport a function group when all the related objects in the function group are not correctly captured.
Fix: Capture the related objects all again and re-transport.

Transport Error Log 2:
Error: No Data source with these attributes
Reason: We get this error when we try to transport changes to an object which is actually not available in the target system. In this case it was a data source.
Fix: First transport the data source to the target system and then its changes.