How To Fix RESCBC036 - No cost collector is generated for &1 for period &2

SAP Error Message - Details

• Message type: E = Error

• Message class: RESCBC - Errors During Posting of Settlement

• Message number: 036

• Message text: No cost collector is generated for &1 for period &2

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message RESCBC036 - No cost collector is generated for &1 for period &2 ?

  The SAP error message RESCBC036 indicates that no cost collector has been generated for a specific object (identified by &1) for a given period (identified by &2). This error typically occurs in the context of controlling and project systems, particularly when dealing with cost accounting and internal orders.
  Cause
  The error can arise due to several reasons, including:
  
  
  Missing Configuration: The cost collector may not be properly configured in the system. This could be due to missing settings in the controlling area or project definition.
  
  
  Period Closing: The period for which you are trying to generate the cost collector may be closed. In SAP, once a period is closed, no further postings can be made to that period.
  
  
  Incorrect Object Type: The object for which you are trying to generate the cost collector may not be valid or may not have been set up correctly in the system.
  
  
  No Actual Costs: There may be no actual costs posted to the cost collector for the specified period, which would prevent its generation.
  
  
  Authorization Issues: The user may not have the necessary authorizations to create or view cost collectors.
  
  
  Solution
  To resolve the error, you can take the following steps:
  
  
  Check Configuration: Verify that the cost collector is correctly configured in the system. Ensure that all necessary settings in the controlling area and project definition are in place.
  
  
  Open Period: Check if the period is open for posting. If the period is closed, you may need to reopen it (if allowed) or wait until the next open period.
  
  
  Validate Object: Ensure that the object (e.g., internal order, project) for which you are trying to generate the cost collector is valid and correctly set up in the system.
  
  
  Post Actual Costs: If there are no actual costs posted, consider posting some costs to the cost collector to trigger its generation.
  
  
  Check Authorizations: Ensure that the user has the necessary authorizations to create and manage cost collectors.
  
  
  Review Logs: Check the application logs for any additional error messages or warnings that may provide more context about the issue.
  
  
  Related Information
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CJI3 (Project Actual Line Items), KOB1 (Order Actual Line Items), and CJI5 (Project Actual/Plan/Variance).
  SAP Notes: Look for SAP Notes related to this error message for any patches or updates that may address known issues.
  Documentation: Review SAP documentation on cost collectors and controlling to ensure compliance with best practices.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a functional consultant who specializes in controlling and project systems.