How To Fix PSSC_TOOLS036 - No active BAdI implementation for due date modifier &1

SAP Error Message - Details

• Message type: E = Error

• Message class: PSSC_TOOLS - Message Class for Periods & Due Date Tools

• Message number: 036

• Message text: No active BAdI implementation for due date modifier &1

What causes this issue?

There is no active BAdI implementation of the BAdI definition
BADI_PSSC00_DUE_DATE_CALC.

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?

Check your active BAdI implementations using the <LS>BAdI Builder</>
transactions (SE18 and SE19) and activate the required BAdI
implementations.
New BAdI implementations need to have a filter value that is defined in
Customizing for <LS>Public Sector Management </>under <LS>Social
Services -> Basic Settings -> Periods and Due Date Rule Settings ->
Period and Due Date Rule Setting Enhancement ->
<DS:SIMG.V_PSSC_DDR_MTYPE>Maintain Due Date Rule Modifier Types</>.</>

Procedure for System Administrators

The following are the details of the BAdI definition:
Enhancement spot: ES_PSSC00_PERIOD_TOOLS
BAdI definition: BADI_PSSC00_DUE_DATE_CALC
Interface: IF_EX_PSSC00_DUE_DATE_CALC
BAdI filter: PSSC_DDR_MOD_TYPE (due date rule modifier)
Default implementations:
PSSC_DDR_MOD_TYPE_BOP (first day of the payment period is due date)
PSSC_DDR_MOD_TYPE_EOP (Last day of the payment period is due date)

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message PSSC_TOOLS036 - No active BAdI implementation for due date modifier &1 ?

  The SAP error message PSSC_TOOLS036 indicates that there is no active Business Add-In (BAdI) implementation for the specified due date modifier. This error typically occurs in the context of SAP applications that utilize BAdIs for enhancing standard functionality, particularly in areas like payment processing, billing, or other financial transactions.
  
  Cause:
  
  Missing BAdI Implementation: The most common cause is that the required BAdI implementation for the specified due date modifier has not been created or activated in the system.
  Incorrect Configuration: The due date modifier being referenced may not be correctly configured or may not exist in the system.
  Transport Issues: If the BAdI implementation was recently transported from another system, it may not have been activated in the target system.
  
  
  Solution:
  
  
  Check BAdI Implementation:
  
  Go to transaction SE18 (BAdI Definition) and check if the BAdI related to the due date modifier is defined.
  If it is defined, go to transaction SE19 (BAdI Implementation) to see if there is