How To Fix /FTI/CUST_ACCESS036 - Association from BCO '&1' to BCO '&2' missing

SAP Error Message - Details

• Message type: E = Error

• Message class: /FTI/CUST_ACCESS -

• Message number: 036

• Message text: Association from BCO '&1' to BCO '&2' missing

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 /FTI/CUST_ACCESS036 - Association from BCO '&1' to BCO '&2' missing ?

  The SAP error message /FTI/CUST_ACCESS036 indicates that there is a missing association between two Business Configuration Objects (BCOs) in the SAP system. This typically occurs in the context of SAP's Financial Transaction Management (FTI) or similar modules where BCOs are used to define relationships and configurations.
  Cause:
  The error message is triggered when the system expects a certain association between two BCOs (denoted as &1 and &2 in the error message) but cannot find it. This can happen due to several reasons:
  
  Configuration Issues: The BCOs may not have been properly configured or linked during the setup process.
  Data Migration Problems: If data was migrated from another system or version, the associations may not have been correctly transferred.
  Custom Development: If there are custom developments or modifications in the system, they might have inadvertently disrupted the expected associations.
  Transport Issues: If the BCOs were transported from one system to another (e.g., from development to production), the associations may not have been included in the transport request.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Configuration: 
  
  Go to the configuration settings for the BCOs involved. Ensure that the associations are correctly defined.
  Use transaction codes like SPRO to access the configuration settings.
  
  
  
  Review Documentation: 
  
  Check the SAP documentation or notes related to the specific BCOs to understand the expected associations and how to set them up.
  
  
  
  Recreate Associations: 
  
  If the associations are missing, you may need to manually create them. This can usually be done through the configuration interface.
  
  
  
  Data Consistency Check: 
  
  Run consistency checks or validation tools provided by SAP to identify any other potential issues with BCOs.
  
  
  
  Transport Request Review: 
  
  If the issue arose after a transport, review the transport request to ensure that all necessary objects and associations were included.
  
  
  
  Consult SAP Notes: 
  
  Search for relevant SAP Notes in the SAP Support Portal that might address this specific error or provide guidance on how to resolve it.
  
  
  
  Contact SAP Support: 
  
  If the issue persists and you cannot find a resolution, consider reaching out to SAP Support for assistance.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes related to BCO management and configuration, such as SPRO, SE80, or SE11.
  SAP Community: Engage with the SAP Community forums where other users may have encountered similar issues and can provide insights or solutions.
  Documentation: Review the official SAP Help Portal for detailed information on BCOs and their associations.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.