3786385 - Error "Special G/L indicator not defined or incorrect" during TRM posting for intercompany loan (TBB1/process Financial Transactions) - SAP S/4HANA Cloud Public Edition

• Error: "Special G/L indicator not defined or incorrect" when attempting to post an intercompany loan (Product Type P11) in Treasury and Risk Management via the Process Business Transactions app.
• The subject indicates the error occurs during TBB1 posting.
• Principal ledger posting via TBB1 works for paying valuation areas, but errors occur for non-paying valuation areas.
• The same error can appear in TPM10 test run.
• Error code observed in analysis: F5838.

SAP S/4HANA Cloud Public Edition

1. Create or use an intercompany loan (Product Type P11) in Treasury and Risk Management.
2. Run posting via Process Business Transactions app (or TBB1/TPM10 test).
3. Post flows that update interest/bank-clearing (for example, update types similar to MMZ12±) in a non-paying valuation area.
4. Observe the error "Special G/L indicator not defined or incorrect".

• Missing dedicated posting specifications for non-paying valuation areas: subledger posting keys (19/29) are not permitted in non-paying valuation areas, so G/L keys (40/50) must be used and accounts pre-resolved.
• Missing G/L-only (SZART blank) assignments for certain update types (for example, MMZ12±), causing no matching rule when routing only to bank clearing without customer/vendor.
• The Special G/L indicator used is not valid for the account type/posting key combination due to the above configuration gaps.

1. In SSCUI 103014 (Define Account Determination for Treasury and Risk Management), create dedicated posting specifications for non-paying valuation areas that:

• Use document type SA.
• Use G/L posting keys 40 (debit) and 50 (credit), not subledger keys 19/29.
• Resolve to appropriate account symbols (for example, Bank Clearing on one side and Customer/Vendor on the other), retaining the required Special G/L indicator (for example, K) where applicable.

     2. In the “Assignment of Update Types to Posting Specifications” (TRAC_DFTRULE1), maintain:

• G/L-only rows with SZART blank (Payment Transaction unchecked) for update types that can post only between G/L accounts (for example, MMZ12±), assigning suitable G/L bank-clearing posting specs (for example, equivalents of 13100 and 14500).
• Rows with SZART = X and POST_IN_VAL_AREA = N that map to the new non-paying valuation area posting specifications created in step 1.

     3. Verify that for paying valuation areas, existing assignments (for example, posting specs with SZART = X and POST_IN_VAL_AREA = P) remain unchanged.

     4. In Financial Accounting, ensure Special G/L configuration exists for both customers and vendors:

• Table T074 contains valid entries for KOART = D and K with the required Special G/L indicator (for example, UMSKZ = K) for the reconciliation accounts used.

     5. Transport the configuration through the landscape and retest posting via Process Business Transactions (or TBB1/TPM10). Confirm that the error no longer occurs in non-paying valuation areas.

• Refer to: Note 3719928 - Error "Special G/L Indicator Not Defined or Incorrect" during TBB1 posting

TBB1, Process Business Transactions, TRM, Treasury and Risk Management, Special g/l indicator not defined or incorrect, F5838, Non-paying valuation area, Posting specifications, trac_postrule, trac_dftrule1, szart, Intercompany loan, Product type p11, Posting keys 40 50 , KBA , FIN-FSCM-TRM-AC-2CL , Position Management and Accounting (Public Cloud) , Problem