How To Fix /SAPAPO/MSDP_DIS036 - Different factory calendar from header resource &1 and subresource &2

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPAPO/MSDP_DIS -

• Message number: 036

• Message text: Different factory calendar from header resource &1 and subresource &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 /SAPAPO/MSDP_DIS036 - Different factory calendar from header resource &1 and subresource &2 ?

  The SAP error message /SAPAPO/MSDP_DIS036 indicates that there is a mismatch between the factory calendars assigned to a header resource and its subresource in the Advanced Planning and Optimization (APO) module. This can occur in scenarios where production planning or scheduling is being performed, and it is essential for the header resource and its subresources to have consistent factory calendars to ensure accurate planning and scheduling.
  Cause:
  The error is caused by the following:
  
  Different Factory Calendars: The header resource (e.g., a production line or machine) and its subresource (e.g., a specific tool or workstation) are assigned different factory calendars. This can lead to inconsistencies in availability and working times.
  Configuration Issues: There may be a configuration issue in the resource master data where the factory calendars are not aligned.
  Data Maintenance Errors: Manual errors during data entry or maintenance of resource master data can lead to this mismatch.
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Check Resource Master Data:
  
  Go to the resource master data in the SAP system (transaction code C223 for changing resources).
  Check the factory calendar assigned to both the header resource and the subresource.
  
  
  
  Align Factory Calendars:
  
  If you find that the factory calendars are different, you need to align them. You can either:
  
  Change the factory calendar of the subresource to match that of the header resource.
  Change the factory calendar of the header resource to match that of the subresource, depending on your business requirements.
  
  
  
  
  
  Consistency Check:
  
  After making changes, perform a consistency check to ensure that all related resources have the correct and consistent factory calendars.
  
  
  
  Re-run Planning:
  
  Once the factory calendars are aligned, re-run the planning or scheduling process to see if the error persists.
  
  
  
  Related Information:
  
  Factory Calendar: A factory calendar defines the working days and hours for a resource. It is crucial for scheduling and planning activities in production.
  Resource Master Data: This includes all the information related to production resources, including their capacities, availability, and calendars.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as C223 (Change Resource), C202 (Display Resource), and C201 (Create Resource) for managing resource data.
  
  By ensuring that the factory calendars are consistent across all related resources, you can avoid this error and ensure smooth production planning and execution in SAP APO.