How To Fix FDM_AR036 - Origin &1 not supported when you create using Enterprise Service

SAP Error Message - Details

• Message type: E = Error

• Message class: FDM_AR - Dispute Management (Process Integration)

• Message number: 036

• Message text: Origin &1 not supported when you create using Enterprise Service

What causes this issue?

Origin &V1& is not supported when you create a case using the Enterprise
Service. The following are supported
'01':,,Biller Direct
'03':,,Enterprise Service

System Response

The case is not created.

How to fix this error?

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

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FDM_AR036 - Origin &1 not supported when you create using Enterprise Service ?

  The SAP error message FDM_AR036 with the description "Origin &1 not supported" typically occurs in the context of the Financial Data Management (FDM) module when you are trying to create or process a document using an Enterprise Service. This error indicates that the system does not recognize the specified origin for the transaction or document you are trying to create.
  Cause:
  
  Unsupported Origin: The origin specified in the request is not configured or recognized by the system. This could be due to a typo, an incorrect value, or the origin not being set up in the system.
  Configuration Issues: The system may not have the necessary configuration to handle the specified origin. This could be due to missing entries in the relevant customizing tables.
  Version Mismatch: If you are using an outdated version of the service or if there are compatibility issues between the service and the SAP system, it may lead to this error.
  
  Solution:
  
  Check the Origin Value: Verify the value of the origin being passed in the request. Ensure that it is correct and matches the expected values configured in the system.
  Configuration Review: 
  
  Go to the relevant customizing settings in SAP (transaction SPRO) and check the configuration for the Financial Data Management module.
  Ensure that the origin you are trying to use is defined and supported in the system.
  
  
  Update or Correct the Service: If you are using a custom or third-party service, ensure that it is up to date and correctly configured to work with your SAP system.
  Consult Documentation: Review the SAP documentation for the specific Enterprise Service you are using to ensure that you are following the correct procedures and using the correct parameters.
  Contact SAP Support: If the issue persists after checking the above points, consider reaching out to SAP support for further assistance. They may provide insights specific to your system configuration or version.
  
  Related Information:
  
  Transaction Codes: You may want to use transaction codes like SE80 (Object Navigator) or SE37 (Function Module) to investigate the service or function module being called.
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  Logs and Traces: Review application logs (transaction SLG1) or trace files to gather more context about the error and identify any additional issues that may be contributing to the problem.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.