Symptom
- The 'Reference Key 2' field in a noted item journal entry cannot be changed after the document is created/posted using the app Manage Journal Entries.
- The configuration activity 'Define Journal Entry Change Rules' does not offer 'Reference Key 2' for selection, so the field cannot be opened for changes.
- The clearing process requires an update to 'Reference Key 2', but the field remains non-editable.
Environment
SAP S/4HANA Cloud Public Edition
Reproducing the Issue
- Open the app Manage Journal Entries and select the noted item journal entry.
- Attempt to edit the line item field "Reference Key 2".
- Observe that the field cannot be selected/changed and is not available via 'Define Journal Entry Change Rules'.
Cause
- 'Reference Key 2' at line-item level is not available in SSCUI/CBC activity 'Define Journal Entry Change Rules' (SSCUI 104309.
- Therefore it cannot be changed after posting via document change rules or the change API.
Resolution
- If the clearing process depends on this value, the recommended approach is to populate the required reference during the creation of the noted item or payment request, rather than attempting to update it afterward.
- Use the Payment Reference field and there is no standard warning regarding the use of Payment Reference. As long as the clearing process, matching rules and any dependent custom developments are designed to use Payment Reference, this approach is supported.
See Also
- Business Add-Ins for Substitution for Journal Entries
- 3050143 - "Change of field Reference Key & is not possible. Field is not open for input" while using API Journal Entry - Change (Asynchronous)
Keywords
reference key 2, xref2, noted item, manage journal entries, document change rules, sscui 104309, bkpf-xblnr, line item not editable, clearing, payment reference, api journal entry change, field not open for input, gl accounting, s/4hana cloud public edition , KBA , FI-FIO-GL-TRA-2CL , Transaction Apps (Public Cloud) , Problem
Product
SAP S/4HANA Cloud Public Edition all versions
SAP Knowledge Base Article - Public