Fonction SAP BKK_RFC_PAYM_ORDER_POST - Post Payment Order

Paramètre Reférence Type Long. Valeur par déf. Facultatif Description
I_SENDER IBKKRFCPOSND u 535 Ordering Party Data
I_X_NO_PREPOST BKK_XFELD C 1 X X Field

Paramètre Reférence Type Long. Description
E_PAORN IBKKPOHD-PAORN N 12 Payment Order Number
E_RETURN IBKK_MISC-RC C 2 Return Code

Paramètre Reférence Long. Facultatif Description
T_PAYM_NOTE IBKKRFCPONT 81 X Payment Note Data
T_RECEIVER IBKKRFCPORCV 479 Recipient Data

Functionality
Transferring (to Bank Customer Accounts), checking and posting paymentitems by using RFC.
The function module is used for converting the figure display fromexternal to internal format (payment amounts), checking the paymentorder, and checking the authorization for execution.
The payment items are created and checked from the payment order, andposted if there are no errors.
If there are no errors, the payment order is posted. If there areerrors, the system response is rejection for formal errors, andotherwise, the items are parked.

Description
Number with which the payment order was posted in the system.

Description
Result of the payment order processing

Value range
Possible return codes:

  • 00 No errors

  • 01 Forwarded for release

  • 03 In postprocessing

  • 04 Processing not possible

  • 99 No execution authorization
  • Further information

    Structure I_SENDER

    The import structure of the ordering party data must be depicted asfollows:


    Field Name ,,Required ,, Type,,Length,,Description
    BANKS,,X,,CHAR,, 3,,Country key of the bank
    BANKL,,X,,CHAR,,15,,Bank key
    ACEXT,,X,,CHAR,,35,,Account number
    ACIBAN,,,,CHAR,,35,,International Bank Account Number
    NAME,,,,CHAR,,35,,Account holder name
    REFNO_CR,,,,CHAR,,20,,Reference number of author
    REFNO_PAYM,,,,CHAR,,20,,Reference number - previous system
    REFNO_PN,,,,CHAR,,12,,Daybook
    DATE_CR,,,,DATS,, 8,,Creation date
    DATE_VALUE,,,,DATS,, 8,,Value date
    DATE_POST,,,,DATS,, 8,,Posting date
    TCUR,,X,,CUKY ,, 5,,Transaction currency
    T_AMOUNT,,X ,,CHAR ,,25,,Amount in TCUR
    T_CHARGE,,,,CHAR,,25,,Charge in TCUR
    MEDIUM,,X,,CHAR,, 4,,Medium
    PAYMETHOD,,X,,CHAR,, 4,,Payment method
    TRNSTYPE,,X,,CHAR,, 4,,Transaction type
    ITEMCNT,,,,NUMC,, 5,,Number of recipients
    XCRED,,X,,CHAR,, 1,,Indicator: Credit
    PUBLIC_CONT_L1,,CHAR ,,35 ,,public field length 35
    PUBLIC_CONT_L2,,CHAR ,,35 ,,public field length 35
    PUBLIC_CONT_L3,,CHAR ,,35 ,,public field length 35
    PUBLIC_CONT_L4,,CHAR ,,35 ,,public field length 35
    PUBLIC_CONT_S1,,CHAR ,,20 ,,public field length 20
    PUBLIC_CONT_S2,,CHAR ,,20 ,,public field length 20
    Generally, all fields must be entered left-aligned. There are thefollowing exceptions:
    ACEXT and CHEQUE_NO must be specified right-aligned with leading zeros.
    Fields specified in Customizing as '0001', for example, must betransferred in this way to the interface.
    The POSNO field describes the position within the payment orders. Itis defined that the ordering party always has position '00001' and the
    recipients are counted consecutively from position '00002'.
    A date is transferred in a DATS-type field. The date is displayed asyyyymmdd.
    Example: 12/24/1997 is displayed as 19971224 (initial value is00000000).
    Numbers are transferred in NUMC-type fields. These are character fieldsthat only permit numbers (digits). Numbers must be displayed withleading zeros.
    Example: Number 13 is displaced in a NUMC field, length 4 as 0013.
    Note: At SAP, counters always begin with 1 and not with 0.This means, for example, if you are transferring 2 payment note lines,
    these must be numbered 001 and 002.
    Amounts are displayed in character fields, length 25. They are displayedleft-aligned, without +/- sign and without punctuation marks after thethousands. Places before and after the decimal point are separated bya period.
    The +/- sign is represented by the XCRED field. The field reflects value'X' when a credit is involved.
    Example: An amount of 1,327.11 is displayed as 1327.11
    Note:,,You can only create orders in the account currency.
    Functionality of the container fields:
    Using the container fields it is possible to supply additional,customer-specific information about payment items and payment orders inthe payment transaction operations.
    The details contained in the fields are stored, and can be output withthe bank statement.
    The Customizing settings for the container fields are in the IMG in
    the basic functions for account management:
    - Maintain Field Description for Customer Fields
    - Maintain Default Values for Customer Fields

    Description
    If this indicator is set, the function module's behavior from beforeRelease 4.63 is retrieved. If errors occur in the ordering party check,the payment order is rejected and not forwarded to postprocessing.

    Description
    Table of payment notes.

    Value range
    Field Name,,Type,,Length,,Description
    POSNO,,NUMC,,5,,Payment order position
    NOTNO,,NUMC,,3,,Payment note number
    PAYM_NOTE,,CHAR,,65,,Payment notes
    Digits are transferred in fields of the NUMC type. These arecharacter fields that only permit digits. Digits must be depicted withleading zeros.
    Example: In a NUMC field of length 4, the number 13 is depicted as#0013.

    Table T_RECEIVER
    Further information

    Data structure for the table of recipient data
    Field Name ,,Required ,,Type ,,Length ,,Description
    POSNO,,X,,NUMC,, 5,,Payment order item
    BANKS,, X ,,CHAR,, 3 ,,Country key of bank
    BANKL ,,X ,,CHAR ,,15 ,,Bank key
    ACEXT ,,X ,,CHAR ,,35 ,,Account number
    ACIBAN ,,,,CHAR ,,35 ,,International Bank Account Number
    NAME ,,,,CHAR ,,35 ,,Account holder name
    DATE_VALUE ,,,,DATS ,,8 ,,Value date
    TCUR ,,X ,,CUKY ,,5 ,,Transaction currency
    T_AMOUNT,, X ,,CHAR ,,25 ,,Amount in TCUR
    T_CHARGE ,,,,CHAR ,,25 ,,Charge in TCUR
    TRNSTYPE,, X ,,CHAR ,,4 ,,Transaction type
    CHEQUE_NO,,,,CHAR,,20,,Check number
    XCRED,, X ,,CHAR ,,1 ,,Indicator: Credit
    Generally, all fields must be entered left-aligned. There are thefollowing exceptions:
    ACEXT and CHEQUE_NO must be specified right-aligned with leading zeros.
    Fields specified in Customizing as '0001', for example, must betransferred in this way to the interface.
    The POSNO field describes the position within the payment orders. Itis defined that the ordering party always has position '00001' and therecipients are counted consecutively from position '00002'.
    A date is transferred in a DATS-type field. The date is displayed asyyyymmdd.
    Example: 12/24/1997 is displayed as 19971224 (initial value is00000000).
    Numbers are transferred in NUMC-type fields. These are character fieldsthat only permit numbers (digits). Numbers must be displayed withleading zeros.
    Example: Number 13 is displaced in a NUMC field, length 4 as 0013.
    Note: At SAP, counters always begin with 1 and not with 0.This means, for example, if you are transferring 2 payment note lines,these must be numbered 001 and 002.
    Amounts are displayed in character fields, length 25. They are displayedleft-aligned, without +/- sign and without punctuation marks after thethousands. Places before and after the decimal point are separated bya period.
    The +/- sign is represented by the XCRED field. The field reflects value'X' when a credit is involved.
    Example: An amount of 1,327.11 is displayed as 1327.11
    Note:,,You can only create orders in the account currency.