Ansicht
Dokumentation
/BGLOCS/FI_RFKORD80 - Print Program: Cash Documents
ROGBILLS - Synchronize billing plans ABAP Short ReferenceThis documentation is copyright by SAP AG.
Description
You can use this program to print cash documents.
The program can only be used with the cash journal transaction. It uses the cash journal data for selection and printing. FI documents are therefore not necessary.
As a rule, the print program is only run directly during system configuration for testing purposes. Otherwise the program is called automatically by the cash journal transaction or other higher-level correspondence programs.
Requirements
The following prerequisites must be fulfilled before you can print cash documents in correspondence:
- 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.
- The form F140_CASH_DOC_01 is used in the standard system.
Output
Each cash document is printed separately. A separate spool request is created for each company code. For test purposes, this can be displayed on the screen. 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 is issued by that higher-level program (for example, trigger for correspondence or internal documents).
Information About Standard Forms and Text Symbols
Example
Customizing for cash documents is explained below using the standard system.
Customizing:
Make the basic settings for correspondence in Customizing for "Financial Accounting Global Settings". 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:
Maintain the base parameters for cash documents as follows.
You do not have to maintain the call options since the correspondence request has to be triggered by the cash journal transaction.
1.1. Examples of the correspondence types:
SAP18 Cash document
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 SAP18 RFKORD80 SAP18
1.3. 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 RFKORD80 F140_CASH_DOC_01
You should use transaction SE71 to see whether the standard form is available in the client you require. 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 form text (usually 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.
1.4. 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 RFKORD80 ADRS 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.5. Examples of Sort Variants:
For cash documents, you have to define at least one sort variant for the documents. The sort variants determine the sequence in which the documents are output.
Sort variant Name
Seq. Field name Name Offset length
B1 Document number, Fiscal year
1 BELNR Document number 10
2 GJAHR Fiscal year 4
B2 Reference, Fiscal year
1 XBLNR Reference 16
2 GJAHR Fiscal year 4
B3 Document type, Document number, Year
1 BLART Document type 2
2 BELNR Document number 10
3 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 list of the fields you can select contains a selection of fields from the document header table BKPF.
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 table BKPF, which are not yet in table RF140V, into table RF140UZZ. However, you must ensure that you use the field names and data elements from the standard tables, since the fields in table RF140UZZ are supplied using the names from the document header table. After you have added these fields, you must activate table RF140UZZ.
1.6 Create program variants
Examples of program variants:
Program RFKORD80
SAP18 Sorting correspondence B1
Output to printer Define printer (for each company code
if necessary)
Log to printer Define printer for error
list (for each company
code if necessary)
BAL_S_LOG - Application Log: Log header data BAL Application Log Documentation
This documentation is copyright by SAP AG.
Length: 15926 Date: 20240328 Time: 134759 sap01-206 ( 186 ms )