Do you have any question about this error?
Message type: E = Error
Message class: RSSM_TT - Transfer Tool
Message number: 012
Message text: &1(&2) contains source requests that have not been extracted
The Object &V1&(&V2&) contains Requests which are not extracted by all
Delta-DTPs and extracting Delta-ODP/ODQ
All extracting Delta-DTPs and Delta-ODP/ODQ must have extracted all
source Requests from Obuject &V1&(&V2&)
Execute all extracting Delta-DTPs and Delta-ODP/ODQ for Object &V1&(&V2&
)
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
RSSM_TT012
- &1(&2) contains source requests that have not been extracted ?The SAP error message RSSM_TT012 indicates that there are source requests in a DataSource that have not been extracted. This typically occurs in the context of SAP BW (Business Warehouse) when you are trying to load data into a target InfoProvider, but the source requests (the data that should be loaded) have not been processed or extracted yet.
Cause:
- Incomplete Data Extraction: The source requests from the source system have not been fully extracted into the BW system. This can happen if the extraction process was interrupted or if there are issues with the source system.
- Data Transfer Issues: There may be issues with the data transfer process, such as network problems or configuration errors.
- Request Status: The requests may be in a status that does not allow them to be processed (e.g., they are still in the "New" or "In Process" status).
- DataSource Configuration: The DataSource may not be properly configured, leading to issues in data extraction.
Solution:
- Check Source Requests: Go to the Data Warehousing Workbench (transaction RSA1) and check the status of the source requests. Ensure that they are in a status that allows for extraction (e.g., "Ready").
- Re-extract Data: If the source requests are not extracted, you may need to re-extract the data from the source system. This can be done by executing the relevant InfoPackage or data load process.
- Monitor Data Transfer: Use transaction RSMO to monitor the data transfer process and check for any errors or issues that may have occurred during extraction.
- Check for Errors: Review the logs for any errors that may have occurred during the extraction process. This can provide insights into what went wrong.
- DataSource Settings: Verify the settings of the DataSource to ensure that it is correctly configured for data extraction.
- Request Management: If necessary, manage the requests in the process chain or InfoPackage to ensure that they are processed correctly.
Related Information:
By following these steps, you should be able to identify the cause of the error and take appropriate actions to resolve it.
Get instant SAP help. Start your 7-day free trial now.
RSSM_TT011
ADSO &1 contains source requests that have not been extracted
What causes this issue? The ADSO &V1& contains Requests which are not extracted by all Delta-DTPs and extracting Delta-ODP/ODQSystem Response...
RSSM_TT010
Data mart status for object &3(&4) is not complete
What causes this issue? Datamart Status for Object &V3&(&V4&) is not complete In the Object &V3&(&V4&) active Request...
RSSM_TT013
PartProvider InfoCube &1 contains requests that have not been extracted
What causes this issue? The Infocube &V1& which is a partprovider of &V2&(&V3&) contains Requests which are not Delta-transfe...
RSSM_TT014
Object &3(&4) contains ADSOs and InfoCubes as PartProviders
What causes this issue? Object &V3&(&V4&), which is a MultiProvider, HybridProvider, or a semantically partitioned object, is a sourc...
Click on this link to search all SAP messages.