How To Fix FKJO116 - Container &1 cannot be deleted as long as it still contains jobs

FKJO116 - Overview

• Message type: E = Error

• Message class: FKJO - Job Commander Messages

• Message number: 116

• Message text: Container &1 cannot be deleted as long as it still contains jobs

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

FKJO116 - Details

• The SAP error message FKJO116 indicates that a specific container (such as a job or a job class) cannot be deleted because it still contains jobs. This is a common issue when trying to manage job containers in SAP, particularly in the context of background processing.
  
  Cause:
  The error occurs because the container you are trying to delete is not empty; it still has jobs assigned to it. SAP prevents the deletion of containers that contain jobs to avoid data loss and maintain the integrity of job scheduling.
  
  Solution:
  To resolve this error, you need to follow these steps:
  
  
  Check the Container: Identify the container (job class or job) that you are trying to delete. You can do this by checking the name of the container mentioned in the error message (represented by &1).
  
  
  List Jobs in the Container: Use transaction codes like SM37 (Job Monitoring) to list all jobs associated with the container. You can