SAP Knowledge Base Article - Public

3578194 - Trading Partner is missing in Journal Entries posted via Manage Recurring Journal Entries after upgrade to CE2502

Symptom

  • After the upgrade to CE2502 when checking Journal Entries posted via the Manage Recurring Journal Entries app the trading partner field is missing.
  • If the trading partner field is mandatory for a G/L Account when attempting to post the JE via the Manage Recurring Journal Entries app the system will report an error stating the mandatory field 'Trading Partner' is required.  This posting will be blocked.

Environment

SAP S/4HANA Public Cloud CE2502

Reproducing the Issue

There are two scenarios whereby the issue can be reproduced.

Scenario 1: Missing Trading Partner:

  1. Manage Recurring Journal Entries.
  2. A recurring entry has existed prior to the upgrade.
  3. This recurring journal entry has the trading partner maintained.
  4. All Journal Entries posted prior to the upgrade have the Trading Partner field maintained.
  5. Following the upgrade to CE2502 the recurring journal entry does not have the trading partner field maintained.

Scenario 2: Blocked for Posting:

  1. Manage Recurring Journal Entries.
  2. A recurring entry has existed prior to the upgrade.
  3. This recurring journal entry has the trading partner maintained.
  4. Following the upgrade to CE2502 the Recurring Journal Entry results in an error stating the field Trading Partner is missing.
  5. The Journal Entry is not posted due to the error. 

Cause

Regression issue with the release of CE2502

Resolution

For the postings with missing trading partners;

  1. SAP suggest reversing the journal entries with empty trading partner.  
  2. As a workaround post the same in Post General Journal Entries, Upload General Journal Entries app or via the Post Journal Entry API with correct trading partner. 
  3. Once the hotfix arrives, please edit the recurring journal entries with the correct trading partner and save it. The postings will be with the correct trading partner after then.

Reversal Posting:

The reversal should be posted in the same period the incorrect posting occurred for example February 02.25 (Fiscal Year Variant K4). 
If the current period is period 03.25 and the posting period 02.25 is closed it will not be possible to create a recurring journal entry in the closed period, please follow the workaround stated;

  1. Reverse the incorrect journal entry with missing trading partner.  
  2. Post the same in Post General Journal Entries, Upload General Journal Entries app or via the Post Journal Entry API with correct trading partner. 
  3. Once the hotfix arrives, please edit the recurring journal entries with the correct trading partner and save it.


For the postings blocked by the empty trading partners:

  1. Once the hotfix arrives, please edit the recurring journal entries with the correct trading partner, and save it. The postings will be with the correct trading partner after then.
  2. As a workaround post the same in Post General Journal Entries, Upload General Journal Entries app or via the Post Journal Entry API with correct trading partner.

The hotfix for this issue is currently being prepared for release. 

See Also

SAP S/4HANA Cloud Public Edition, 3-System Landscape – Upgrade & Maintenance Schedule

SAP S/4HANA Cloud Public Edition, 2-System Landscape & SAP Marketing Cloud – Upgrade & Maintenance Schedule

Keywords

F1598, RASSC, ACDOCA, Trading Part., Trd., regression, [R], (R), 2502, bug, missing, null, inconsistent, inconsistency, wrong,   , KBA , FI-FIO-GL-TRA-2CL , Transaction Apps (Public Cloud) , Problem

Product

SAP S/4HANA Cloud Public Edition 2502