Do you have any question about this error?
Message type: E = Error
Message class: CC - ECM: Messages
Message number: 318
Message text: At least one allocated package is not technically released
You want to release a <DS:GLOS.leading_change_master_record>leading
change master record</> either globally or for production.
The system checks whether
All subordinate <DS:GLOS.change_package>change packages</> have been
released.
You release a change package by releasing it technically. You release a
package that has been created as a change order by setting the
<LS>Release request</> system status.
The <DS:DE.CC_AEHI_LATE>Late packages supported</> indicator is set
You receive this message as either an error message or a warning.
Error message
The <ZH>Late packages supported</> indicator is not set in Customizing.
If you want to release the leading change master record globally or for
production, you must release all subordinate packages first.
Warning message
The <DS:DE.CC_AEHI_LATE>Late packages supported</> indicator is set in
Customizing.
Check the packages that have not been released (<LS>Logistics ->
Central functions -> Engineering change management -> Environment ->
Product structure</>).
If you want to release the leading change master record, confirm the
warning.
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.
CC318
- At least one allocated package is not technically released ?The SAP error message CC318, which states "At least one allocated package is not technically released," typically occurs in the context of SAP's Change and Transport System (CTS) when dealing with transport requests and packages. This error indicates that one or more of the packages associated with the transport request are not in a state that allows them to be transported.
Cause:
- Package Status: The package associated with the transport request is not released. In SAP, packages must be in a "released" state to be included in transport requests.
- Development Class: The development class (package) may be in a state that restricts its transport, such as being marked as "not transportable."
- Transport Layer Issues: There may be issues with the transport layer configuration that prevent the package from being released.
- Authorization Issues: The user may not have the necessary authorizations to release the package.
Solution:
Check Package Status:
- Go to transaction SE80 (Object Navigator) or SE21 (Transport Organizer) and check the status of the package.
- Ensure that the package is set to "Released." If it is not, you can release it by navigating to the package and using the "Release" option.
Release the Package:
- If you have the necessary authorizations, you can release the package by:
- Going to transaction SE21.
- Selecting the package.
- Choosing the "Release" option.
Review Development Class Settings:
- Ensure that the development class is set to be transportable. You can check this in transaction SE80 or SE21.
- If it is not transportable, you may need to change its settings or create a new transportable package.
Check Transport Layer:
- Verify that the transport layer is correctly configured. You can check this in transaction SE03 (Transport Organizer Tools) and ensure that the transport layer is active and correctly set up.
Authorization Check:
- Ensure that you have the necessary authorizations to release the package. You may need to consult with your SAP Basis or security team if you lack the required permissions.
Consult Documentation:
- If the issue persists, consult SAP documentation or support for further troubleshooting steps specific to your SAP version and configuration.
Related Information:
By following these steps, you should be able to resolve the CC318 error and successfully transport your changes.
Get instant SAP help. Start your 7-day free trial now.
CC317
Change number &1 does not exist in object &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CC316
Release key is used in current change numbers
What causes this issue? You want to change or delete the settings for a release key.System Response The system checks whether the release key has be...
CC319
Release key cannot be reset
What causes this issue? You want to change a release key.System Response The system checks whether the chosen release key is defined in such a way t...
CC320
*** TOPIC: DIGITAL SIGNATURE
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.