Reset Check Reason in Repayment Request
Application component: Contract Accounts Receivable and Payable
App type: SAP GUI
Description:  If you are carrying out postings or reversals, you can keep them in a status that has to be confirmed. A workflow is triggered for the confirmation; the last step in the workflow is an approval or rejection.
Key features:  Checks and approvals are supported for the following transactions: Posting documents Reversing documents Changing Documents Creating Installment Plans Creating repayment requests Creating, changing, or reversing requests or standing requests Write-off Creating and changing payment specifications Creating or changing promises to pay Creating or changing a receivables adjustment  If a confirmation is required for the transaction, the function module returns a check reason. The check reason is used to determine the addressees of the workflow, and to define which activities are still permitted for the document until the check has taken place. In these events, you can register the workflows that trigger the confirmation procedure. In addition to the check reason, the system can return the number of checks/authorizations required and three additional parameters that are then available for the role resolution in the workflow. If these parameters are used, for example, to determine the addressees of the workflow, a company code or amount category can be returned here. The number of checks required determines whether for example, the dual control principle (one additional check), or further checks are to be carried out. The maximum permitted value is 9, meaning that a total of 10 checks have to be carried out. If a posting has to be confirmed, the document to be checked is created, the check reason is assigned, and the document is locked for the following editing processes depending on the check reason: Payments Clearing Dunning notices Calculation of interest on arrears Document changes Posting and reversing documents  Event 5500 is processed for each posting, and event 5502 is processed every time the posting is reversed. The function modules defined for these events transfer all data of the document to be posted or reversed. If a check reason is returned by the modules for event 5500 or 5502, then for posting, the event ApprovalRequired is triggered, and for reversals, the event ReverseApprovalRequired of object category CA_DOC is triggered. SAP provides the workflow samples WS21000088 for postings, and WS21000089 for reversals. You can use role 21000056 for role resolution. For a posting or reversal in the dialog transactions Post Document or Reverse Document, the system requires you to enter a reason for the posting or reversal. If a reversal has to be confirmed, the reversal document is not created. The check reason is entered in the document to be reversed. Depending on the check reason, this document is also locked for the editing processes stated above. Changing Documents The function module defined for event 5504 runs for document changes. Using the document data, it checks whether the change has to be confirmed and released by other clerks in a workflow. If a check is required, the module returns a check reason that is stored in the document to be changed. Event ChangeApprovalRequired of object category CA_DOC is triggered. In the document display, processors who are assigned to the appropriate role in the workflow can do the following: Display the original document and the planned changes using the Planned Changes function Accept or reject the document change using function keys  SAP delivers the sample workflow 21000093 FICA_DCHAPPR. Role 21000056 FICA_DOCAPPR is used for the role resolution. Creating Installment Plans If, for example, you do not want to grant installment plans to customers with poor credit without subjecting them to a check and approval first, define a customer-specific function module for event 5506 in Customizing. This module runs when you create installment plans. If the module returns a check reason, event ApprovalRequired of object category INSTMNTPLN is triggered. SAP delivers the role 21000062 FICA_INSTPL and the sample workflow 21000094 INSTPL. You can change or deactivate an installment plan waiting for approval until it is approved. The installment plan is only locked while changes are made, in which the end of approval of the installment plan is in progress. If an approved installment plan is changed, it is deactivated and a new installment plan is created from the changes. If this new installment plan is approved, it is valid. If rejected, the previously deactivated installment plan becomes valid again. The late payment charge is forwarded when the installment plan waiting for approval is changed. When the installment plan is rejected, the late installment charge document is not activated and it is then deleted. Temporary interest calculation documents are assigned to the new installment plan and if the installment plan is rejected they are assigned to the old installment plan. This is also the case for charge document. Repayment Requests In order to check and approve repayment requests in a workflow, you have to enter a customer-specific function module for event 5508 in Customizing. If the module returns a check reason, event ApprovalRequired of object category CA_RPAYREQ is triggered. SAP delivers the role 21000063 FICA_RPAYREQ and the sample workflow 21000095 FICA_RPAYREQ. Requests and Standing Requests See Workflow for Checking and Approving Requests. Write-off See Checking and Approving Write-Offs. Payment Specifications See Approval and Release of Payment Specifications by Workflow. Promises to Pay See Approval and Release of Promises to Pay by Workflow. Adjustment of Receivables See Approval and Release of Receivables Adjustment by Workflow.