How To Fix WS_RRLE056 - FI document type &1 is not relevant for settlement doc. lists for &2

SAP Error Message - Details

• Message type: E = Error

• Message class: WS_RRLE - Settlement Document List

• Message number: 056

• Message text: FI document type &1 is not relevant for settlement doc. lists for &2

What causes this issue?

In
<DS:SIMG.W_WLFA_054>Customizing</>, no group of settlement document
list types has been assigned to the FI document type and to the partner.

System Response

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

How to fix this error?

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 WS_RRLE056 - FI document type &1 is not relevant for settlement doc. lists for &2 ?

  Certainly! Here's a detailed explanation for the SAP error message:
  
  SAP Error Message:
  WS_RRLE056 FI document type &1 is not relevant for settlement doc. lists for &2
  
  Meaning / Cause:
  This error occurs during settlement processing (e.g., in Asset Accounting, Project System, or other modules where settlement is used) when the system tries to include an FI document type in a settlement document list, but that FI document type is not configured as relevant for settlement document lists for the specified object or process.
  In other words, the system expects certain FI document types to be marked as relevant for settlement, but the document type you are trying to settle with is not flagged accordingly.
  
  Common Causes:
  
  The FI document type used in the transaction is not assigned as relevant for settlement document lists in the configuration.
  Custom or standard FI document types have not been maintained properly in the settlement settings.
  The settlement profile or the object (e.g., asset, WBS element) expects only certain FI document types to be settled, and the current document type is not among them.
  
  
  Solution / How to Fix:
  
  
  Check FI Document Type Settings:
  
  Go to transaction SPRO ? Financial Accounting (New) ? Financial Accounting Global Settings (New) ? Document ? Document Types ? Define Document Types.
  Verify the document type &1 mentioned in the error.
  
  
  
  Maintain Settlement Document List Relevance:
  
  The key configuration is to mark the FI document type as relevant for settlement document lists.
  Use transaction OKO7 or navigate via SPRO:
  
  Controlling ? Internal Orders ? Settlement ? Basic Settings ? Maintain Document Types Relevant for Settlement Document Lists
  
  
  Here, assign the FI document type &1 as relevant for the settlement document list for the controlling object type &2 (e.g., internal order, asset, WBS element).
  
  
  
  Check Settlement Profile:
  
  Ensure the settlement profile assigned to the object allows the FI document type in question.
  Sometimes, the settlement profile restricts document types.
  
  
  
  Reprocess the Settlement:
  
  After making the configuration changes, re-run the settlement process.
  
  
  
  
  Additional Information:
  
  &1 = FI Document Type (e.g., SA, KR, etc.)
  &2 = Controlling Object Type or Settlement Object (e.g., Internal Order, Asset, WBS Element)
  This error is common in Asset Accounting settlements or Internal Order settlements where document types are strictly controlled.
  If you are unsure which document types are relevant, check the standard SAP settings or consult your FI/CO configuration team.
  
  
  Summary:
  
  
  
  Aspect
  Details
  
  
  
  
  Error Message
  WS_RRLE056 FI document type &1 is not relevant for settlement doc. lists for &2
  
  
  Cause
  FI document type not flagged as relevant for settlement document lists for the object
  
  
  Solution
  Maintain FI document type as relevant for settlement document lists in configuration
  
  
  Transaction Codes
  SPRO, OKO7
  
  
  Modules Affected
  FI, CO (Internal Orders, Asset Accounting, Project System)
  
  
  
  
  If you provide the actual document type and object type from your error message, I can help you with more specific guidance.