Ansicht
Dokumentation
RFKORDJ2 - Receipt Before Payment (Japan)
ABAP Short Reference Addresses (Business Address Services)This documentation is copyright by SAP AG.
Description
This report prints receipts for payments in cash, bills of exchange, or checks that have not been cleared. The report creates the receipts in exactly the same way as RFKORDJ1, but the open items are not cleared yet. Depending on the transaction, receipts can be created as incoming payments via the noted item. The noted items must also be cleared when you post an incoming payment.
In Japan, the receipt is subject to tax. The tax, INSHI-ZEI, depends on the amount in the receipt. The system automatically determines the (stamp) tax and prints the tax amount on the receipt. An internal (or external) number is assigned for each receipt.
The report divides the payment amount into several receipts:
For example, for a 10,000,000 Yen payment, two receipts can be created
to the amount of 5,000,000 Yen.
You can select two methods for outputting the receipt.
- Optimized receipts Type = SAPQ4
For each payment document, the system automatically determines the smallest total tax amount and the minimum output number for the receipt. The receipt number is, however, limited to a maximum of three digits.
You enter a highest amount for each receipt as a report parameter.
- Individual receipts Type = SAPQ5
You can distribute the payment amount into several receipts manually. The system determines the stamp tax for the receipt amount you enter.
Requirements
Before you can print payment notices within the correspondence function, the following requirements must be met.
- Configuration
- Make the basic settings for correspondence in Customizing for "Financial Accounting Global Settings". More detailed information about the standard settings is given below in this documentation.
- Defining forms
- Forms must be defined and activated in the system so that you can print the required letters. The standard system provides a form that you can copy and adapt to meet your own requirements.
- Form F140_RECEIPT_J1 is used in the standard system.
The following restrictions apply to the creation of payment notices:
- The system only supports postings created by functions that have a payment amount set in at least one customer line item of the incoming payment document. At present, these functions include "Internal transfer posting with clearing", "Incoming payments", "Incoming payments fast entry", and "Outgoing payments". To ensure that the system determines a payment amount when these functions are used, all bank accounts, bank sub-accounts, bank clearing accounts, and the reconciliation account for bills of exchange must be marked as relevant to cash flow within the G/L account master record. These accounts are posted to when the above functions are used.
- Cross-company code transactions are not supported.
- Even for head offices with local processing, payment notices are addressed to the head office and not to the branch.
- In the case of document extracts sent to one-time customers, business transactions can be posted in a document for one customer only.
- With clearings between customers and vendors, a payment notice addressed to the customer is created for each customer/vendor pair if the corresponding flag is set in the master records.
Output
Receipts are created for each customer with a document.
For test purposes, this can be displayed on the screen. If you do not print a receipt, the number allocated to it is lost.
If you do not specify for the print program on which printer the correspondence is to be printed, the program may take the printer specified in the user master of the user who started the program, or the printer specified when the job is scheduled.
If minor errors occur during the program run, that is errors that do not lead to a program termination, these are listed after the run in an error list. If you want these error lists to be printed on a certain printer, you need to specify a printer for the log in the print program or the print program variant. If you do not specify for the print program on which printer the log is to be printed, the program may take the printer specified in the user master of the user who started the program or the printer specified when the job is scheduled. If the program is run online, the error list is displayed on the screen. If, however, the program is scheduled as a job, the job request name for the error list is composed of the identifier F140ER, the printer name, and possibly the correspondence type and/or the company code.
If the print program is run directly and a printout issued, then a log with the spool requests created is issued for each program run. If you do not specify for the print program on which printer the log is to be printed, the program may take the printer specified in the user master of the user who started the program or the printer specified when the job is scheduled. If the program is run online, the log is displayed on the screen. If the program is planned as a job, the spool request name of the error list is made up of the identifier F140, the printer destination, the date of creation, and the program ID KORD. If the print program is started by a higher-level correspondence program, the log entry is made by means of the higher-level program (trigger for correspondence).
Explanation of the Standard Form
In the standard system, this is the form F140_RECEIPT_J1. The name is structured as follows: Program identification code_form name_number.
The form consists of the pages FIRST (first page).
The windows in the letter
The following windows must be defined for the letter:
- HEADER
- The standard text you store for the company code is used for the header in the letter.
- ADDRESS
- The address window consists of the customer's address and the standard text you store for the company code for the sender details. The address format complies with postal regulations.
- INFO
- General information is displayed here, for example, receipt number, date of issue, amount of stamp tax.
- FOOTER
- The footer of the opening page of the letter consists of the appropriate standard text for the company code.
- MAIN
- The main window defines the content and appearance of the text by using its text elements.
Text Elements for the Correspondence
The following elements are for the MAIN window: For example: text elements 701
Text elements 701 are used for issuing summary specifications for the payment transaction.
Text element 590 concludes the letter with a complimentary close and signature.
The following elements are for the INFO window:
Text element 710 displays the receipt number, the date of issue, and the stamp tax amount.
Text Symbols Available
When you set up forms with SAPscript, the system inserts the text symbols into the text, replacing them with the current values when the print programs are run. The fields you can use for this are defined in the Data Dictionary and are set up in the following order according to the program flow:
- Output for a company code
- Data from the company code table (table T001)
- Company code address (internal structure RAADR)
- Sender details (table T001G)
- Letter and reply
- The following are always available during the output of the letter and reply:
- Letter recipients = customer, one-time customer, vendor, one-time vendor from document (internal structure DKADR)
- Accounting clerk (table T001S)
- Account with which items were cleared: Vendor, one-time vendor from
- document (internal structure DKAD2)
- Accounting clerk (table *T001S)
- In addition to the structures listed above, you can use master record data from the fields in tables KNA1, KNB1, LFA1, and LFB1, depending on the combination of the letter recipient and clearing account.
- If the letter recipient is a one-time customer or one-time vendor, you can use data from the fields in table BSEC.
- Address data of the issuer of the payment document (table USR03)
- The following RF140 fields are available: RF140-TDNAME, RF140-TDSPRAS, RF140-SPRAS, RF140-ZALBT, RF140-AUGBT, RF140-SKTBT, RF140-TLZBT, RF140-RPOBT, RF140-ACOBT, RF140-BRTBT (= RF140-AUGBT + RF140-TLZBT), RF140-DIFBT (= RF140-RPOBT + RF140-ACOBT), RF140-UMBBT (= RF140-BRTBT - RF140-ZALBT - RF140-SKTBT - RF140-DIFBT)
- The RF140-ELEMENT field contains the three-digit number of each text element to be printed.
- If the field BSEG-SGTXT, BSID-SGTXT, or BSIK-SGTXT can be used in a text element, a text is only output if there is a * at the beginning of the line item text.
- E-mail body: 140-BELEGNUM
Example
Customizing for payment notices is explained below according to the standard system and based on examples of customer-specific enhancements.
Customizing:
In the configuration menu for Financial Accounting, choose Business volume -> Correspondence. There you maintain the suboptions in accordance with the following guidelines.
Note:
For tables in which a default entry without a company code is allowed, the default entry is
accessed if no entries for a specific company code exist. If you do not want this, you should only make
table entries in cases where the company code is predefined. For the relevant tables, a note exists further down on the default entry company code.
The correspondence types, forms, and standard texts that start with a Z are examples of customer-specific objects that are not delivered in the standard system.
1. Financial Accounting Global Settings: Correspondence Settings:
For payment notices, the settings are to be made as follows.
1.1. Examples of the types:
SAPQ4 Optimization of tax and number of receipts
X Document necessary
SAPQ5 Individual amounts and number of receipts
X Document necessary
1.2. Examples of program assignment:
The entries are to be left blank either for individual or explicitly for all company codes, and/or are to be left blank as default for company code.
CCode CorID Program Variant Default text
----------------------------------------------------
0001 SAPQ4 RFKORDJ2 SAPQ4 F140_RECEIPT_J1
0001 SAPQ5 RFKORDJ2 SAPQ5 F140_RECEIPT_J1
In the standard text, you may only use the paragraph formats that are defined for the relevant form.
If you enter a language for the correspondence request into which the default text is not translated, you receive a blank text editor to enter the text.
Default text ZBEISPIEL, TEXT-ID FIKO
Format Text Area
/* Example of several individual text passages
/: IF &RF140-ELEMENT& = 'XXX'.
/* Text in the text element XXX
AF Text 1
/: ENDIF.
/: IF &RF140-ELEMENT& = 'YYY'.
/* Text in the text element YYY
AF Text 2
/: ENDIF.
XXX and YYY represent numbers of text elements
This option cannot be applied, however, in windows that do not contain events (text elements indicated by numbers).
If, however, you want to use individual text passages in, for example, the INFO window as well as in the MAIN window, you must complete all text elements in your form for which individual text passages are to be issued according to the following example:
Text element in INFO window
Format Text Area
/E XXX
/: DEFINE &RF140-ELEMENT& ="XXX"
/: INCLUDE &RF140-TDNAME& OBJECT BKORM ID FIKO LANGUAGE
&RF140-TDSPRAS&
Text element in MAIN window
Format Text Area
/E YYY
/: DEFINE &RF140-ELEMENT& ="YYY"
/: INCLUDE &RF140-TDNAME& OBJECT BKORM ID FIKO LANGUAGE
&RF140-TDSPRAS&
Individual texts are then created from default texts for each correspondence request. The names of these
texts are made up of the identification code F140, the user ID, the date of request, and the time of the text creation. These texts can be changed with the maintenance transaction for correspondence requests.
1.4. Examples of the forms:
The entries are to be left blank either for individual or explicitly for all company codes, and/or are to be left blank as default for company code.
CCode Program Fo Form
--------------------------------------
0001 RFKORDJ2 F140_RECEIPT_J11
0001 RFKORDJ2 IT Z140_RECEIPT_J11
0001 RFKORDJ2 ZR Z140_RECEIPT_J12
With transaction SE71, you should check whether the standard forms exist in the client in which you need them. If standard forms do not exist, you can use transaction SE71 to copy the missing forms from client 000 (Menu -> Utilities -> Copy from client).
You can create your own forms by copying the standard form and changing the layout set text (generally in the MAIN window). Your forms must start with a "Y" or a "Z". The form name should contain the identification code "F140".
Your own forms or standard forms in clients not equal to 000 might have to be adapted during release changeovers according to the standard form in client 000.
If you need the standard form or a form created by you in languages for which no translation exists, you can use transaction SE63 to translate the forms.
In the standard form for payment notices, preparations are made for the use of individual texts or the direct use of a standard text in the following text elements:
Form Window Text elements
F140_RECEIPT_J1 MAIN 701, 590
In principle, however, you can use the individual texts at any position of a form.
Examples of form modifications:
Form ZF140_RECEIPT_J1
a.) Create form ZF140_RECEIPT_J1 and copy
form F140_RECEIPT_J11 into form ZF140_RECEIPT_J1.
b.) Modify text elements 701 and 590 in the MAIN window.
1.5. Sender details:
The entries are to be left blank either for individual or explicitly for all company codes, and/or are to be left blank as default for company code.
CCode Program TXTID Header text Footer text Signature
Sender
-----------------------------------------------------------------------
0001 RFKORDJ2 ADRS_HEADER ADRS_FOOTER ADRS_SIGNATURE
ADRS_SENDER
You should use transaction SO10 to check whether standard texts exist in the client in which you need them. The text ID is ADRS. If standard texts do not exist, you can use transaction SO10 to copy the missing texts from client 000 (Menu -> Utilities -> Copy from client).
If, due to company stationery, you do not require individual specifications - such as the header text
and the footer text - you can leave the respective fields in the table blank. Normally, however, at
least the standard text for the signature is needed. You should, however, make a default entry (company
code = blank and name of the print program) in the table to avoid error messages if you do not want to use texts.
1.6. Call options:
The entries are to be left blank either for individual or explicitly for all company codes, or are to be left blank as default for company code.
CCode Type of correspondence DocEnt. DocDis Act
-----------------------------------------------------------------------
0001 SAPQ4 Receipt optimized before clearing X
0001 SAPQ5 Individual receipt before clearing X
1.7. Sort Variants for Correspondence:
Sort variants enable you to specify the order in which payment notices are output.
Sort variant Name
Seq. Field name Name Offset length
K1 Sort by postal code
1 LAND1 Country 3
2 HPSTL Postal code of P.O.box or PSTLZ 10
3 KOART Account type 1
4 KONTO Account 10
K2 Sort by account number
1 KOART Account type 1
2 KONTO Account 10
K3 Sort by document number
1 BELNR Document number 10
2 GJAHR Fiscal year 4
Objects are always sorted initially by company code and thereafter in the sequence of the fields in the sort variant being used.
To display a list of the fields by which an object can be sorted, select "Possible entries" (F4). This contains a selection of fields from the master record tables KNA1, KNB1, LFA1, and LFB1, as well as from the table for one-time account data BSEC. The fields KOART, KONTO, KTOGR (KNA1-KTOKD or LFA1-KTOKK), and KTOZE (KNB1-KNRZE or LFA1-LNRZE) are filled in accordance with the account type, which is taken from the master record tables. The "Document number" and "Fiscal year" fields are only filled in the case of document-related correspondence, such as payment notices.
You can extend this list of selectable fields in order to meet your requirements. To do so, you can use a repair correction to import fields from the following tables, which are not yet in table RF140V, into table RF140VZZ: KNA1, KNB1, LFA1, LFB1, and BSEC. You must, however, make sure the field names and data elements from the standard tables are used because the fields in table RF140VZZ are filled according to the names in the master record data and one-time customer data. After adding to these fields, you need to activate table RF140VZZ. The sort fields are then supplied in accordance with their names and in a pre-defined sequence as follows:
The sort fields are drawn first from the KNA1 or LFA1 data, then from the KNB1 or LFB1 data, and finally from the BSEC data, if necessary.
Thus, fields that have the same name in tables KNA1, KNB1, and BSEC, or LFA1, LFB1, and BSEC, may be overwritten.
2.1. Examples of report variants:
You make the settings for the report variants under the "Payment notices" option in the "Accounts Receivable and Accounts Payable" Implementation Guide.
Report RFKORDJ1
SAPQ4 Special G/L indicator J1
Noted items X
Correspondence sorting K1
Data from trigger table X
Correspondence SAPQ4 :obligatory
Receipt lot Q001
Tax from original document X
Country code for tax JP
Tax code A1
SAPQ5 Special G/L indicator J1
Noted items X
Correspondence sorting K1
Data from trigger table X
Correspondence SAPQ5 :obligatory
Receipt lot Q001
Tax from original document X Country code for tax JP Tax code A1
CL_GUI_FRONTEND_SERVICES - Frontend Services RFUMSV00 - Advance Return for Tax on Sales/Purchases
This documentation is copyright by SAP AG.
Length: 32075 Date: 20240601 Time: 062128 sap01-206 ( 332 ms )
