Martin Maruskin blog (something about SAP): BW transport error: Object ABC needs object XYZ; latter is not in a request

Monday, August 3, 2020

BW transport error: Object ABC needs object XYZ; latter is not in a request

Today one more blog post about BW transports. While releasing the BW transport there can be below error message:

Object ABC needs object XYZ; latter is not in a request Message No. RSO657

Diagnosis

The required object XYZ is not in a request. The request should not be released.

System Response

The object ABC would result in an error during import since the required object XYZ cannot exist in the target system.

Procedure

Write the required object IOBJ XYZ in a request.

Issue is very clear from the BW system consistency standpoint. It identified the missing object and it does not want to allow the transport be released as it would lead to inconsistency. However in most of the cases it is obvious that object that the system is complaining about is already existing for quite some and was transported across a landscape. That means it object XYZ doesn’t need to be in the transport.

According the SAP Notes such as 1801262 the error message can be ignored. It means that import to target BW system can be performed with an option of "Release despite errors? While doing it in person via dialog mode in t-code SE10. However there is no such an option in case there is an change management tool (e.g. Solman CHaRM) used in the landscape. In such a case, it make sense to put particular transport into the table RSTPCHECKEXC (Exception Table: Before Export Check). The table hold in information about all the transports that are to be exceptioned from “Before Export Check” phase of the transports while it is being released.

The report RSO_TLOGO_CHECK_REQUEST also using this table while executing the transport consistency check for before export check phase of releasing the transport.