Do you have any question about this error?
Message type: E = Error
Message class: RSSM_TT - Transfer Tool
Message number: 036
Message text: &1(&2) is not a corporate memory; compress all requests in &1(&2)
Object &V1&(&V2&) is not a corporate memory.
Only objects, which belong to the first entry layer, are corporate
memories. Thus, for corporate memory objects there must be a DataSource
that loads directly into these objects.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Objects<(>,<)> which are no corporate memories, must be compressed
completely. All requests in non-corporate memories have to be
compressed.
Error message extract from SAP system. Copyright SAP SE.
RSSM_TT036
- &1(&2) is not a corporate memory; compress all requests in &1(&2) ?The SAP error message RSSM_TT036 indicates that there is an issue with the corporate memory in the context of the SAP BW (Business Warehouse) system. This error typically arises when you are trying to compress requests in a DataStore Object (DSO) or InfoCube, but the system is unable to recognize the specified object as a valid corporate memory.
Cause:
- Invalid Object Type: The object you are trying to compress is not recognized as a corporate memory. This could happen if the object is not set up correctly or if it is not a valid DSO or InfoCube.
- Request Status: The requests you are trying to compress may not be in a state that allows for compression. For example, if the requests are still in a "new" or "in process" state, they cannot be compressed.
- Technical Issues: There may be underlying technical issues with the BW system, such as inconsistencies in the metadata or issues with the database.
Solution:
- Check Object Type: Ensure that the object you are trying to compress is indeed a DSO or InfoCube and is set up correctly in the system.
- Verify Request Status: Check the status of the requests you are trying to compress. Make sure they are in a state that allows for compression (e.g., "loaded" or "successful").
- Reprocess Requests: If the requests are in an invalid state, you may need to reprocess them or delete and reload them.
- Check for Errors: Look for any other error messages or logs that might provide more context about the issue. This can help identify if there are any underlying problems with the data or the system.
- Consult Documentation: Refer to SAP documentation or notes related to the specific version of BW you are using for any known issues or additional troubleshooting steps.
- Contact SAP Support: If the issue persists and you cannot resolve it, consider reaching out to SAP support for assistance.
Related Information:
By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.
Get instant SAP help. Start your 7-day free trial now.
RSSM_TT035
&1(&2) contains too many requests (&3); reduce request list in target
What causes this issue? Object &V1&(&V2&) contains &V3& requests.System Response Only 1.000 requests are allowed in a data t...
RSSM_TT034
&1 &2 &3 &4
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RSSM_TT037
Object &1(&2) contains yellow request &3(&4); process or delete request
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RSSM_TT038
DTP &1 is part of a closed loop; it writes back to its source
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.