Ansicht
Dokumentation

J_3RFZKR_PDF - Print Payment Orders (Russia)

J_3RFZKR_PDF - Print Payment Orders (Russia)

Addresses (Business Address Services)   ABAP Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

Description

Using the program J_3RFZKR_PDF, you can print payment orders for:

  • normal vendor invoice document
  • parked document (BKPF-BSTAT = V)
  • payment requests (BKPF-BSTAT = S, BSEG-UMSKZ = P)
  • down payment requests (BKPF-BSTAT = S, BSEG-UMSKZ = F)

in accordance with the conditions of the legislation of the Russian Federation.

Printing is carried out:

  • on an open item or on already cleared/paid document (if the document clearing date is specified)
  • on documents in a currency specified on the selection screen
  • in the currency other than the document currency (if the Payment currency field is defined on the selection screen)

The program uses the F110_RU_PLATPORU or J_3RF110_PDF (Adobe) standard forms. If required, forms can be copied and adjusted to specific customer needs.

To receive additional information from forms using the PERFORM operator, call up routines included in the RFFOSCRP (form F110_RU_PLATPORU) or J_3RFSCP_PDF (formular J_3RF110_PDF) modular pool.

Attention! Correlation between payment requests and the issued invoice is not tracked.

Payment order number

To assign numbers to payment orders, use:

  • either the First payment document number field on the selection screen (if it's not blank),
  • or the FI document number (field BKPF-BELNR). The algorithm defined in the NUMER_PLATPORU routine converts the internal number of an accounting document into a 6-digit payment order number in which last three digits should be other than "000". Since the payment order number is formed by the accounting document number, it is not recommended to process documents that contain several vendor/customer line items using this report.

Requirements

The report partially uses settings of the standard automatic payment program:

  • The AUST1, AUST0, AUST2 and AUST3 fields of the table T042E (Company code payment method -> Form data -> Issuer on the form) are used for displaying a name of the payer in the payment order. Search within the table is carried out by the payment method specified in the document (field BSEG-ZLSCH). If this field in the document is blank, select a table row which corresponds to the first of payment methods defined for the given company code.
  • In case the Supplement to payment method field is activated, it becomes available for entering values in the document (BSEG-UZAWE field). Upon entering values in the field,
  • the first symbol is used as a "Payment priority" requisite;

  • the second symbol is used for filling out the "Payment type" requisite in the payment order header, and also as an attribute for calling up the RU_ADDCORRDATA routine. The RU_ADDCORRDATA routine defines correspondent bank data and is called up from the J_3RF110 form, if L, M, or W letters are used as the second symbol.

What to enter in the provided fields


Details Information source

Date Current date or the document posting date (if
it's greater than the current date)

VAT registration Value of the T001Z-PAVAL field for the SAPR01
number of the payer parameter from the "Additional data" section
found in the company code description.
Customizing the T001I, T001J, T001Z tables is
required.

POC of the payer Value of the "Tax number 3" (LFA1-STCD3) field
from the vendor master record. The field is used
for all company codes. An accounting text from
the vendor master record with the KPP1 "Vendor's
POC for the company code" identifier is used for
maintenance of various POCs for several company
codes. If this text is not filled out, the
content of the "Tax number 3" field is displayed.
Menu path for customizing the text:
SAP Customizing Implementation Guide: ->
Financial Accounting -> Accounts Receivable and
Accounts Payable -> Vendor Accounts -> Master
data -> Preparations for Creating Vendor Master
Data -> Define Text IDs for Accounting Texts
(Vendors)
The "Relevant text" indicator should be activated

VAT registration Value of the LFA1-STCD1 field from the vendor
number of the master record.
recipient

Payee Values of the LFA1-NAME1, LFA1-NAME2, LFA1-NAME3,
LFA1-NAME4 fields from the vendor/alternative
payee master record. Similar fields from the BSEC
table are used for one-time account vendors.
The program correctly processes data on the
alternative payee both in the document and in the
vendor master record.
Also, the name of the vendor branch bank taken
from the bank address version (the NAME1 - NAME4
fields) is displayed in the "Payee" field. Branch
banks (subsidiaries) and the bank head office are
maintained in the system as individual bank
master records; branch banks (subsidiaries) use
details (correspondent account and bank
identification code) of the head office.

Bank details To define a house bank unambiguously, use settings
of the payment program for the corresponding
payment method in the company code, and values of
the fields from the House bank (BSEG-HBKID) and
Payment method (BSEG-ZLSCH) documents.
To define a vendor bank precisely, it is
recommended to fill out the Partner bank type
field (BSEG-BVTYP) upon posting. Assign a unique
"partner bank type" (LFBK-BVTYP) to each of vendor
clearing accounts in the vendor master record.
If the fields are blank, use the first of house
banks that has a bank account for the payment in
corresponding currency, and the first appropriate
partner bank.
Bank names (BNKA-BANKA), their BIC (the BNKA-BNKLZ
bank code), and cities (BNKA-ORT01) are displayed
in the form (Reference to bank data - LFBK-BKREF;
for accounts of different persons, or if the
LFBK-BKREF field is blank -> BNKA-BRNCH branch
bank). Vendor clearing account is read from the
"Bank control code" (LFBK-BKONT) and "Account
number" (LFBK-BANKN) fields.Similar fields from
the T012K table are used for the output of house
bank data.

Purpose of the Information from "long" texts: "Correspondence",
payment "Payment advise note data" (BELEG text objects
with identifiers 0001 and 0003, correspondingly).
Menu path upon entering the document: Additional
information -> Texts.
Data on VAT is defined in the TAXFORM1 module (in
the J_3RFSCP and RFFOSCRP programs).
VAT amount is defined for normal or parked
documents, payment and down payment requests.
Documents with several tax rates are processed.
Attention! VAT calculation for the payment
request on an account with several VAT rates is
not performed.
The "Incl. VAT 0%" VAT line is generated upon
printing payment requests on documents with the
VAT code that has a rate of 0%. If the VAT code
with a rate of 0% for untaxable transactions is
specified in the document, it is necessary to
enter this VAT code in the T007K Table for
Grouping Tax Basis Balances table upon printing
the "Exempt from VAT" line in the form:
Menu path:
SAP Customizing Implementation Guide (IMG): ->
Financial Accounting -> General Ledger Accounting
-> Business Transactions -> Closing -> Reporting
-> Sales/Purchases Tax Returns -> Group Tax Base
Balances.

Example of filling out a line of the T007K Table for Grouping Tax Basis Balances table:

Country code: RU

Tax group version: PAY


Tx Description Pro Tx.bs
N0 Deliveries and services exempt from input VAT VST 4

Example of filling out the report selection screen:


Vendor account 1 - 9999
Company Code A001 - z001
Open items at key date 27.03.1999
Clearing date -
Document number 1400000003 - 1800056987
Document currency DEM - USD
Payment currency RUB
Process standard documents X
Process parked documents X
Process prepayment orders X
Printer xxxx
Spool name J110
Suffix 1 Spool
Suffix 2 Spool
Number of copies 1
Print preview X
Print immediately X
New SPOOL-request X
Layout set J_3RF110

Printing

Printing is carried out via the transaction SE38. The user system logon language is used in the output.

For all documents are also issued long texts, produced as

Example






General Material Data   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 11507 Date: 20240531 Time: 113809     sap01-206 ( 89 ms )