Do you have any question about this error?
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
There is no active BAdI implementation of the BAdI definition
BADI_PSSC00_DUE_DATE_CALC.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
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</>.</>
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.
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 an active implementation for the BAdI. If not, you may need to create one.
Create/Activate BAdI Implementation:
- If there is no active implementation, you can create one in transaction SE19. Make sure to implement the necessary logic as per your business requirements.
- After creating the implementation, ensure it is activated.
Check Configuration:
- Verify the configuration settings related to the due date modifier in the relevant customizing transactions (e.g., in Financial Accounting or Controlling).
- Ensure that the due date modifier you are trying to use is valid and correctly set up.
Transport Management:
- If the BAdI implementation was transported, check the transport logs to ensure that it was successfully imported and activated in the target system.
Consult Documentation:
- Review SAP documentation or notes related to the specific BAdI and due date modifier for any additional configuration steps or prerequisites.
Related Information:
If the issue persists after following these steps, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
Get instant SAP help. Start your 7-day free trial now.
PSSC_TOOLS035
No active BAdI implementation for frequency mapping category &1
What causes this issue? There is no active BAdI implementation of the BAdI definition BADI_PSSC00_FRQ_MAPPING.System Response The system issues an e...
PSSC_TOOLS034
Frequency mapping category &1 is not valid
What causes this issue? The frequency mapping category defined in Customizing cannot be handled in the active frequency mapping BAdI implementation.S...
PSSC_TOOLS037
Payment period for due date calculation not specified
What causes this issue? Minimum date (01.01.1900) or maximum date (31.12.9999) of the calendar has been reached during date calculation using the per...
PSSC_TOOLS038
Due date rule type or Customizing for due date calculation not defined
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.