How To Fix PSSC_GROSS136 - Delimitation check: A GPI attempts to delimit an already due payment (&2)

PSSC_GROSS136 - Overview

• Message type: E = Error

• Message class: PSSC_GROSS - Gross Entitlement and Payment

• Message number: 136

• Message text: Delimitation check: A GPI attempts to delimit an already due payment (&2)

What causes this issue?

You triggered an activity during which the historic gross payment
document (GPD) item &V3& should have been delimited by an item of this
actual calculation. This activity was stopped because the part of the
item &V3& that should have been delimited represents a past payment.
Delimitation of GPD items is only possible for future parts of a GPD
item.
This situation only occurs in scenarios where a payment frequency was
changed in the sequence of follow-up decisions. All entitlements until
&V2& potentially delimit payment items that are already due, and hence
may result in the same exception.

System Response

The current calculation was stopped.

How to fix this error?

Depending on the scenario, the following options are available:
Scenario 1: First GPD with a new payment frequency in a sequence of
follow-up decisions
Change the decision period, so that the calculation period of the actual
gross payment calculation starts after &V2&.
Scenario 2: For GPDs following a GPD with a new payment frequency
Postpone with the actual calculation until the actual break-date is
later than &V2&.
Given the precondition that all older gross payment items (GPIs) were
delimited within scenario 1, you should be able to execute any GPIs (for
example, without any time constraints) in scenario 2.

Procedure for System Administrators

&V2& = actual break-date of the historic GPD (holding item &V3&)
&V3& = historic GPI

Error message extract from SAP system. Copyright SAP SE.

PSSC_GROSS136 - Details

• The SAP error message PSSC_GROSS136 indicates that there is an issue with a Global Payment Instruction (GPI) attempting to delimit a payment that is already due. This typically occurs in the context of payment processing within SAP, particularly in the Financial Supply Chain Management (FSCM) or Treasury modules.
  
  Cause:
  The error arises when a GPI tries to modify or delimit a payment that has already reached its due date. This can happen due to several reasons:
  
  Timing Issues: The GPI is being processed after the payment has already been scheduled or is due.
  Incorrect Configuration: There may be configuration issues in the payment processing settings that allow for delimitation attempts on due payments.
  Data Integrity Issues: There might be inconsistencies in the data related to the payment or GPI that prevent the system from processing the delimitation correctly.
  
  
  Solution:
  To resolve this error, consider the following steps:
  
  
  Check Payment Status: Verify the status of the payment in question.