|
Functionality
You can create payment requests with this method.
A payment request is a payment order that is carried out by the paymentprogram for payment requests. You use this method to transfer all datanecessary for the payment. Each time the method is called, only one
payment item is transferred.Notes
The following authorization object is checked with activity 01(create):
- F_PAYRQ,,Authorization object for payment requests
Transfer
You determine how the payment request is created with parametersReleasepost and Releasepay:
- The payment request is updated in cash management and forecast and is
released for payment:
Releasepost "X"
Releasepay "X"
- The payment request is updated in cash management and forecast. The
method PaymentRequest.Release releases the payment request forpayment.
Releasepost "X"
Releasepay " "
- The payment request is parked. Update in cash management and forecast
occurs with method PaymentRequest.Post. Next, release forpayment is effected with method PaymentRequest.Release.
Releasepost " "
Releasepay " "
Processing steps
This method executes the following processing steps:
- Authorization check
- Customer exit for check
- Entry of payment request and completion of data
- Payment request check
- Optional: Entry and check of data for cash management and forecast
- Entry of customer enhancements
- Customer exit for update of own data
- Update of payment request data
- Optional: Update of cash management and forecast data
Update of payment request data and cash management and forecast data isdone using temporary storage. This means that the data is first savedinternally on a temporary basis and written in the database as a tableinsert with COMMIT WORK. Deletion of internal storage is carried outduring ROLLBACK WORK.
Customer enhancements
The method supports the SAP customer enhancement concept. It ispossible to enhance payment request table PAYRQ (BAPI table extension:BAPI_TE_PAYRQ) and to permit this to be updated with table Extensionin.Furthermore, two customer exits exist through which checks and updateof own data can be carried out (SAP enhancement: PRQ_BAPI).
Messages
INCLUDE BAPI_RETFurther information
You can find further information in the SAP Library underFinancials -> Financial Accounting -> Bank Accounting -> PaymentTransactions -> Automatic Payments -> Payment Program for PaymentRequestsDescription
The key number is returned to the user in the field REQUESTID aftersuccessful creation of the payment request. Number assignment happensinternally and the user is not in a position to change it. Description
INCLUDE BAPI_TABLE Value range
Type,,ID ,,Nummer,,Text
E ,,FIBL1 ,,003 ,,No execution authorization for company code &1 andorigin &2
E ,,FICORE,,816 ,,House bank ID & does not exist for company code &
E ,,FICORE,,817 ,,Account ID & does not exist for house bank ID &
E ,,BF00 ,,211 ,,Bank & & does not exist
E ,,PZ ,,300 ,,Address data is incomplete or contains errors
E ,,PZ ,,301 ,,Bank details are incomplete or contain errors
E ,,PZ ,,302 ,,Only account numbers containing up to 18characters are supported
E ,,FICORE,,165 ,,Company code & is not defined
E ,,F5 ,,162 ,,Business area & not supported
E ,,PZ ,,710 ,,Partner number or account type invalid
E ,,PZ ,,711 ,,Bank account transfers only possible with accounttype "S"
E ,,PZ ,,712 ,,You can only specify an alternative payee foraccount types "D" and "K"
E ,,PZ ,,713 ,,Specify a branch only for account types "D" and"K"
E ,,FH ,,005 ,,Account &1 not found in company code &2
E ,,PZ ,,643 ,,Payment currency & missing
E ,,FIBL1 ,,001 ,,Origin indicator &1 does not exist
E ,,PZ ,,706 ,,House bank group &1 with company code &2 does notexist
E ,,PZ ,,014 ,,No payment method has been entered
E ,,FZ ,,009 ,,Payment method & not defined in country &, correctyour entry
E ,,FZ ,,012 ,,Payment method & not defined in company code &,correct your entry
E ,,PZ ,,822 ,,Incorrect import parameters for module &
E ,,F2 ,,403 ,,Payment block & not defined
E ,,00 ,,058 ,,Entry & & & does not exist (check entry)
E ,,69 ,,949 ,,Entry & & & missing in table &
E ,,FIBL1 ,,040 ,,SCB indicator &1 does not exist
E ,,FIBL1 ,,041 ,,DME recipient code &2 is invalid
E ,,FIBL1 ,,042 ,,Instruction key &1 does not exist for any paymentmethod in bank country &2
E ,,B0 ,,252 ,,Company code & accounting clerk & not supported intable T001S
E ,,FB ,,279 ,,Company & not supported
E ,,PZ ,,127 ,,Key number must not be filled in extension table
Other messages can occur during conversion of amounts from businesspartner management, central address management, cash management andforecast, and number range management. Description
This structure contains the accounts required to create the paymentdocument. Payment requests can refer to a concrete vendor/customer orG/L business transaction, but do not have to.
At least both of the following fields have to be filled:
- Account type (field ACCT_TYPE)
If the payment refers to a business transaction in accountspayable/receivable, you enter either "K" or "D". Otherwise you enter an"S" so that the posting can be made to a G/L account.
- Business partner account (field PARTNER_ACCOUNT)
Depending on the business partner, the account and account type have tobe entered here. The clearing document number in the payment documentis posted to this account.
The following fields do not have to be filled/have to be filled only inspecial circumstances:
- Alternative reconciliation account ( field RECONCIL_ACCOUNT)
The alternative reconciliation account can be filled forvendor/customer business transactions. If the field is not filled, thealternative reconciliation account that is stored in the master recordis used.
- Bank clearing account (field BANK_CLEARING_ACCT)
The bank clearing account for the payment document only has to beentered when payment program account determination is not being used.You enter account determination in Customizing under FinancialAccounting -> Bank Accounting -> Business Transactions -> PaymentTransactions -> Payment Handling -> Enter Origin Indicators.
- Bank account number (field PARTNER_ACC_TRANSFER)
The bank account number (G/L account) of the partner's bank is onlyrequired for update of cash management and forecast in the case ofbank-to-bank transfers.
|