Do you have any question about this error?
Stop Googling SAP errors. Use our Free Essentials plan instead - instant AI help, no credit card needed. Start Now →
Message type: E = Error
Message class: SCPR_ATC - Message class for ATC checks on BC sets
Message number: 013
Message text: Piece list of an object is empty
The object piece list is not correctly maintained in the transaction
SOBJ for the referenced object.
This is also relevant for individual transactions (object type 'T'),
because the data required to create a BC Set can only be read from the
piece list.
BC set activation can lead to data inconsistency.
For object types 'S', 'V' or 'C', use the 'Dictionary Adjustment' option
to create the piece list in SOBJ transaction.
For other object types, the piece list must be maintained
manually.
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.
SCPR_ATC013
- Piece list of an object is empty ?The SAP error message SCPR_ATC013, which states "Piece list of an object is empty," typically occurs in the context of SAP's Advanced Transport Management (ATC) or during transport-related activities. This error indicates that the system is unable to find any components or objects associated with a particular transport request or object.
Causes:
- Empty Transport Request: The transport request may not contain any objects or components. This can happen if the request was created but no objects were added to it.
- Incorrect Object Type: The object type being referenced may not be valid or may not have any associated pieces in the transport request.
- Transport Request Deletion: The transport request might have been deleted or not properly released, leading to an empty piece list.
- Authorization Issues: Lack of proper authorizations to view or access the objects in the transport request can also lead to this error.
- System Configuration Issues: There may be configuration issues in the transport management system that prevent the proper retrieval of objects.
Solutions:
- Check Transport Request: Verify that the transport request is not empty. Open the transport request in the Transport Organizer (SE09 or SE10) and ensure that it contains the necessary objects.
- Add Objects: If the transport request is empty, you may need to add the required objects to it. This can be done by using the "Include Objects" option in the Transport Organizer.
- Release Transport Request: Ensure that the transport request is properly released. If it is in a modifiable state, you may need to release it to make it available for transport.
- Check Authorizations: Ensure that you have the necessary authorizations to view and manage the transport request and its objects.
- Review System Configuration: If the issue persists, review the transport management configuration in your SAP system. This may involve checking the transport routes and settings in transaction STMS.
- Consult SAP Notes: Check for any relevant SAP Notes that may address this specific error. SAP frequently updates its knowledge base with solutions for known issues.
Related Information:
If the problem persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.
Get instant SAP help. Sign up for our Free Essentials Plan.
SCPR_ATC012
Used object is forbidden because of an existing BEFORE EXPORT method
What causes this issue? A Before Export method gets only executed when a transport is released. When you put the data in a BC Set, the Before Export ...
SCPR_ATC011
Switch BC Set contains data from more than one object
What causes this issue? Switch BC Set contains data for more than one customizing object.System Response While BC Sets may contain any number of cus...
SCPR_ATC014
Used Table/View does not exist
What causes this issue? A referenced Table/View may not, or no longer exist in the system.System Response BC set cannot be activated.How to fix this...
SCPR_ATC015
SOBJ piece list for object is not consistent with DDIC piece list
What causes this issue? The piece list (SOBJ) for object does not match the piece list for the object in the Data Dictionary.System Response You can...
Click on this link to search all SAP messages.