The table below provides a comprehensive overview of all fields and relationships for the Payment Request object in Maica. Please refer to the table below for detailed information.
Click here to view and download the complete Payment Request Schema.
Validation Rules
The list below outlines the Validation Rules applied to the Payment Request Object in Maica.
Please refer to the list below for more detailed information on each Validation Rule.
Status Cannot Be Changed When Payment Request Status is Paid
When the Payment Request Status is updated to Paid, the Status on the record cannot be changed.
Validation Rule Detail
Rule Name
x01_Paid_PR_Cannot_Be_Changed
Error Message
You cannot modify a Paid Payment Request. Payment Request Error x01.
The list below outlines the Trigger Handlers applied to the Payment Request Object in Maica.
Please refer to the list below for more detailed information on each Trigger Handler.
Payment Request Initialise Claim Reference
This trigger is designed to initialise the claim reference for payment requests in Maica.
Detail
Load Order
1
Label
PaymentRequestInitClaimReference_MDTM
Execution, Logic & Outcome
Execution of Trigger Logic:
The trigger logic defined in the PaymentRequestInitClaimReference_MDTM class is executed when the trigger conditions are met. The class contains the code that manages the initialization of the claim reference for payment requests.
Trigger Conditions:
When a new payment request (maica__Payment_Request__c) is created.
When an existing payment request is updated.
Any specific field changes that are monitored by the trigger (defined in the handler class).
Logic Explanation
Initialisation:
When a payment request record is created or updated, the trigger is initialised. The PaymentRequestInitClaimReference_MDTM metadata type configuration is loaded, ensuring that the trigger is active (Active__c is true) and has the correct load order (Load_Order__c is 1.0).
Trigger Execution:
Upon initialisation, the trigger executes the logic defined in the PaymentRequestInitClaimReference_MDTM class.
The class methods perform the following steps:
Validation: The payment request data is validated to ensure it is complete and accurate.
Initialisation: Based on predefined criteria, the claim reference is initialised to ensure each payment request has a unique and consistent reference.
Update: The payment request record is updated with the newly initialised claim reference.
Trigger Outcome:
Once executed, the trigger ensures that each payment request has its claim reference initialised correctly, according to the logic specified in the handler class. This helps maintain accurate and consistent claim reference data for payment requests.
Payment Request Initialise ABA Export
This trigger is designed to initialise the ABA export for payment requests in Maica.
Detail
Load Order
1
Label
PaymentRequestInitABAExport_MDTM
Execution, Logic & Outcome
Execution of Trigger Logic:
The trigger logic defined in the PaymentRequestInitABAExport_MDTM class is executed when the trigger conditions are met. The class contains the code that manages the initialization of the ABA export for payment requests.
Trigger Conditions:
When a new payment request (maica__Payment_Request__c) is created.
When an existing payment request is updated.
Any specific field changes that are monitored by the trigger (defined in the handler class).
Logic Explanation
Initialisation:
When a payment request record is created or updated, the trigger is initialised. The PaymentRequestInitABAExport_MDTM metadata type configuration is loaded, ensuring that the trigger is active (Active__c is true) and has the correct load order (Load_Order__c is 1.0).
Trigger Execution:
Upon initialisation, the trigger executes the logic defined in the PaymentRequestInitABAExport_MDTM class.
The class methods perform the following steps:
Validation: The payment request data is validated to ensure it is complete and accurate.
Initialisation: Based on predefined criteria, the ABA export is initialised to ensure each payment request has the necessary export data.
Update: The payment request record is updated with the newly initialised ABA export data.
Trigger Outcome:
Once executed, the trigger ensures that each payment request has its ABA export initialised correctly, according to the logic specified in the handler class. This helps maintain accurate and consistent ABA export data for payment requests.
