Do you have any question about this error?
Message type: E = Error
Message class: GG - Messages for FI-SL customizing
Message number: 786
Message text: Entries for sets cannot be deleted from the order
You have chosen the function "Delete from Requests". However, this
function is not possible for
<DS:GLOS.352A629061025CD5E10000009B38F974>Report-Writer</>
<DS:GLOS.3526BA3DAFAB52B9E10000009B38F974>Sets</>,
<DS:GLOS.3526BA42AFAB52B9E10000009B38F974>Variables</> and objects.
The entries have not been deleted from the transport order
Remove the entries from the transport request manually in transaction
<DS:TRAN.SE09>SE09</> or <DS:TRAN.SE10>SE10</>.
Error message extract from SAP system. Copyright SAP SE.
GG786
- Entries for sets cannot be deleted from the order ?The SAP error message GG786 indicates that there are entries for sets that cannot be deleted from the order. This typically occurs in the context of production orders, maintenance orders, or other types of orders where sets (which can be groups of components or operations) are involved.
Cause:
- Set Entries Exist: The primary cause of this error is that there are existing set entries associated with the order that prevent deletion. Sets are often used to group related components or operations, and if they are still linked to the order, the system will not allow deletion.
- Status of the Order: The order may be in a status that does not permit changes, such as being released or completed.
- Dependencies: There may be dependencies or relationships with other objects (like production orders, maintenance tasks, etc.) that prevent the deletion of the set entries.
Solution:
- Check Set Entries: Review the set entries associated with the order. You can do this by navigating to the order details and checking the components or operations linked to the set.
- Change Order Status: If the order is in a status that does not allow changes, consider changing the status to a more permissive one (e.g., from "Released" to "Created") if business processes allow it.
- Remove Dependencies: If there are dependencies, you may need to resolve them first. This could involve unlinking components or operations that are tied to the set.
- Use Transaction Codes: Utilize relevant transaction codes (like CO02 for changing production orders) to make the necessary adjustments.
- Consult Documentation: Refer to SAP documentation or help resources for specific instructions related to your version of SAP and the type of order you are working with.
Related Information:
By following these steps, you should be able to identify the cause of the GG786 error and take appropriate action to resolve it.
Get instant SAP help. Start your 7-day free trial now.
GG785
Check field &
What causes this issue? You are using field &V1& in table &V2&. This field uses domain PS_POSNR. This domain is used in the project s...
GG784
Same data element for fields & and &
What causes this issue? Fields &V1& und &V2& (receiver field and sender field) in summary table &V4& use the same data elemen...
GG787
Error when deleting index & of table &
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
GG788
Index & has been deleted and therefore cannot be created again
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.