How To Fix FSBP_MIGID035 - No assignment to identification number category &1 found

SAP Error Message - Details

• Message type: E = Error

• Message class: FSBP_MIGID - Messages for Migration of Additional Partner Numbers

• Message number: 035

• Message text: No assignment to identification number category &1 found

What causes this issue?

From Release SAP ABA 7.10, the <LS>additional partner numbers</> for the
business partner are replaced and transferred to <LS>identification
numbers</> for the business partner. Before you can convert the data,
you have to assign the <DS:DE.BU_ID_TYPE> identification types</> and
<DS:DE.BU_ID_CATEGORY> categories</> for <LS>identification numbers</>
to the <DS:DE.BP_IDTYPE> identification number categories</> for
<LS>additional partner numbers</>. This allocation has either not been
made or the identification number category used has not been created in
Customizing.

System Response

The system stops distributing the data for the <LS>additional partner
numbers</>.

How to fix this error?

Read the documentation for the report FSBP_MAINTAIN_IDTYPE_MAPPING (
<LS>assign identification categories and types to identification number
categories</>) and ensure that all assigments are made. See SAP note
871590.
To distribute <LS>additional partner numbers</> in other systems, you
have to ensure that systems in a release prior to S AP ABA 7.10 are also
aware of these assignments.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FSBP_MIGID035 - No assignment to identification number category &1 found ?

  The SAP error message FSBP_MIGID035 indicates that there is no assignment to the identification number category specified in the error message. This typically occurs during processes related to the migration of identification numbers, such as when working with business partner data or customer/vendor master data.
  Cause:
  The error is usually caused by one of the following reasons:
  
  Missing Configuration: The identification number category you are trying to use has not been configured in the system.
  Incorrect Mapping: The mapping between the identification number category and the relevant business partner or customer/vendor data is not set up correctly.
  Data Migration Issues: During data migration, the identification number category may not have been included or was incorrectly defined.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Configuration:
  
  Go to the configuration settings for identification number categories in your SAP system. This can typically be found in the customizing settings under SPRO -> Cross-Application Components -> Master Data Synchronization -> Define Identification Number Categories.
  Ensure that the identification number category you are trying to use is defined and properly configured.
  
  
  
  Review Assignments:
  
  Check if there are any assignments for the identification number category to the relevant business partner roles or customer/vendor types.
  Make sure that the identification number category is assigned to the correct business partner roles.
  
  
  
  Data Migration Check:
  
  If you are performing a data migration, review the migration files or templates to ensure that the identification number category is included and correctly defined.
  Validate the data being migrated to ensure it adheres to the expected formats and categories.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for specific guidance on the identification number categories and their configurations.
  
  
  
  Testing:
  
  After making the necessary changes, test the process again to see if the error persists.
  
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like BP (Business Partner) or XD01/XK01 (Customer/Vendor) to check the configurations and data.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance.
  Support: If the issue persists after checking the configuration and assignments, consider reaching out to SAP support for further assistance.
  
  By following these steps, you should be able to identify the root cause of the error and implement the necessary changes to resolve it.