How To Fix CC318 - At least one allocated package is not technically released

CC318 - Overview

• Message type: E = Error

• Message class: CC - ECM: Messages

• Message number: 318

• Message text: At least one allocated package is not technically released

What causes this issue?

You want to release a <DS:GLOS.leading_change_master_record>leading
change master record</> either globally or for production.

System Response

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

How to fix this error?

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.

Procedure for System Administrators

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message 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)