Fonction SAP BAPI_PAYMENTREQUEST_RELEASE - Payment Request Released for Payment

Paramètre Reférence Type Long. Valeur par déf. Facultatif Description
REQUESTID BAPI2021_KEYNO-REQUESTID C 10 Key Number for Payment Request
TESTRUN BAPI2021_HELP-TESTRUN C 1 X Switch to Simulation Session for Write BAPIs

Paramètre Reférence Type Long. Description
RETURN BAPIRET2 u 548 Return Parameter

Functionality
You can use this method to release for payment a payment requestcreated with method PaymentRequest.Create and posted with methodPaymentRequest.Post.
This method is a part of the Payment Handling with Release
process. You can use the following three methods to visuallyreproduce this process. Minimum requirement is the inclusion of methodsCreate and Release:

  • PaymentRequest.Create (Create payment request)

  • PaymentRequest.Post (Update cash management)

  • PaymentRequest.Release (Release for payment)

  • Only one payment request can be entered each time the method is called.

    Notes
    The following authorization object is checked with activity 02(change):

    • F_PAYRQ,,Authorization object for payment requests

    • Processing steps
      The method carries out the following processing steps:
      • Determination of payment request status

      • Authorization check

      • Customer exit for data check

      • Customer exit for update of user data

      • Update of payment request data

      • Update of data uses temporary storage. This means that the data isfirst saved internally and then written to the database as table insertthrough COMMIT WORK. Deletion of internal storage occurs duringROLLBACK WORK.
        Customer enhancement
        The method contains two customer exits that you can use for your ownchecks and to update your own data.
        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 execution authorization for company code &1 andorigin &2
        E ,,PZ ,,129 ,,Payment request &1 is canceled already in temporarystorage
        E ,,PZ ,,134 ,,Payment request &1 is currently being processed
        E ,,PZ ,,110 ,,Data for payment request selection is notsufficient
        E ,,PZ ,,090 ,,Payment request & does not exist
        E ,,PZ ,,093 ,,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 ,,Several payment requests exist for reference<(>&1/&2/&3<)>
        E ,,PZ ,,146 ,,Payment request &1 has status &2, thereforerelease is not possible

        Description
        Used to check instance details in write BAPIs before actual creation ofobject instance on the database. Creation of object instance is onlysimulated and the data us not updated (posted).

        Value range
        The following values are possible:

        • "" (no value)

        • No value means that posting occurs. This is the default setting andcorresponds to the normal expectations of the caller.
          • "X"

          • This value means that this BAPI is only called in simualtion mode: Noposting occurs when called.