Functionality
One payment request can be canceled each time the method iscalled. A cancelation indicator is assigned for the payment request andboth cancelation reason and date are added. A payment request can notbe paid after it has been canceled.
A payment request cannot be canceled if it is contained within apayment proposal.

Notes
The following authorization object is checked with activity 85(cancel):

• F_PAYRQ,,Authorization object for payment requests

After a payment request is canceled, no new instance is createdon the database. The payment request to be canceled is uniquelyidentifiable via its key number.
The method carries out the following processing steps:

• Check whether cancelation is permitted


• Authorization check


• Cash management and forecast data entry and check


• Customer exit for user data update


• Update of payment request data


• Update of cash management and forecast data

Payment request data and cash management and forecast data aretemporarily saved first of all, then they are written to the databaseas a table insert through COMMIT WORK. Deletion of internal storage iscarried out during ROLLBACK WORK. This method checks whether thepayment request to be deleted is stored in temporary storage. It is notpossible to cancel a payment request that exists merely in temporarystorage. It is not possible to create a payment request in a LogicalUnit of Work and then delete it (without a COMMIT in between).
Customer enhancements
The method supports the SAP customer enhancement concept. Two customerexits are available with which checks and update of user data can becarried out (SAP enhancement PRQ_BAPI).
Messages
INCLUDE BAPI_RET

Further information
You can find further information in the SAP Library underFinancials -> Financial Accounting -> Bank Accounting -> PaymentTransactions -> Automatic Payment -> Payment Program for PaymentRequests.

Description
INCLUDE BAPI_TABLE

Value range
Type ,,ID ,,Number ,,Text
E ,,FIBL1,,003 ,,No authorization for execution in company code &1and origin &2
E ,,PZ ,,129 ,,The payment request &1 is already canceled intemporary storage
E ,,PZ ,,134 ,,The payment request &1 is currently beingprocessed
E ,,PZ ,,110 ,,Data for payment request selection is notsufficient
E ,,PZ ,,090 ,,Payment request & does not exist
E ,,PZ ,,093 ,,A payment request for document &1/&2/&3 from &4does not exist
E ,,PZ ,,102 ,,No payment request exists for reference <(>&<)>1/
<(>&<)>2/&3
E ,,PZ ,,091 ,,Several payment requests exist for document
<(>&<)>1/<(>&<)>2/&3 from &4
E ,,PZ ,,104 ,,More than one payment request exists forreference <(>&<)>1/<(>&<)>2/&3
E ,,F0 ,,601 ,,State reason for reversal
E ,,F0 ,,602 ,,Reversal reason & is not defined. Correct yourentry
E ,,PZ ,,096 ,,Payment request &1 has been cleared. Reversal notpossible
E ,,PZ ,,097 ,,Payment request &1 already reversed
S ,,F5 ,,135 ,,Period & adjusted in line with posting date &
E ,,PZ ,,029 ,,Payment request &1 contained in payment proposal<(>&<)>2/&3
Further messages might occur when you update cash management andforecast.

Description
Specifies the date on which the payment request is canceled. This entryis mandatory.

Description
Specifies why the payment request is being canceled. The reason forreversal is stored in the payment request. This entry is mandatory.

Description
INCLUDE BAPI_KEYFIELD

Description
Means that cancelation can be simulated right up to the actual posting.In particular, checks are carried out.