/BGLOCS/FI_RFKORD80 - Print Program: Cash Documents

BAL_S_LOG - Application Log: Log header data   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Description

You can use this program to print cash documents.

The program can only be used in conjunction with the cash jounal transaction. It uses the cash journal data for selection and printing. FI documents are therefore not necessary.

The print program is usually only carried out directly for test purposes during system configuration.Otherwise the program is automatically called up by the cash journal transaction or other higher level correspondence programs.

Requirements

The following prerequisites must be fulfilled before you can print cash documents:

1. System configuration

You make the basic settings for correspondence in "Financial Accounting Global Settings" in Customizing. For more information about standard configuration, see details below in this program documentation.

1. Defining forms

Forms must be defined and activitated in the system so that they can print the correspondence required.A form is delivered with the standard system. You can copy this form and adapt it in accordance with your 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.You can display the document on screen for test purposes. If, in the print program, you do not specifythe printer on which correspondence should be printed, either the printer from the user master of the person that started the program, or the printer specified when the job was scheduled is selected.

If minor errors occur during the program run, these are displayed in an error list at the end of theprogram run. The program does not terminate. If you want error lists to be printed on a specific printer,define the printer for the log in the print program or the variant for the print program. If you donot specify a printer, the system selects either the printer from the user master of the person thatstarted the program, or the printer specified when the job was scheduled. If the program is run online,the error list is displayed on the screen. If the program was scheduled as a job, the spool requestname of the error list consists of the indicator F140ER, the printer name, and possibly the correspondence type, and/or the company code.

If the print program is run directly with print output, a log of the spool requests is output per programrun. If you do not specify a printer for the log in the print program, the system selects either theprinter from the user master of the person that started the program, or the printer specified when thejob was scheduled. If the program is run online, the log is displayed on the screen. If the programis planned as a job, the spool request name consists of the indicator F140, the printer name, the issuedate, and the program ID KORD. If the program is started by a higher level correspondence program, the log output is triggered by the higher level program (for example, trigger for correspondence or internal documents).

Information about the standard form and the available text symbols

Information about form layout

Information about the text symbols

Example

Customizing for cash documents is explained below using the standard system.

Customizing:

You make the basic settings for correspondence in Customizing for Financial Accounting Global Settings. There you can maintain the suboptions for the following programs.

Note:
For tables in which a default entry without company code is permitted, if no specific companycode has been entered, the system uses the default entry. If this is not what you require, you shouldonly make table entries that specify the company code. For the relevant tables, there is a note below about the blank company code default entry.

The correspondence types, forms, and standard texts that begin with Z are examples of customer-specific objects that are not delivered with the standard system.

1. Financial Accounting Global Settings: Correspondence:

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 for correspondence types:

             SAP18  Cash document

                    X Document necessary

1.2. Examples for program assignment:

Make entries either for individual or all company codes explicitly, and/ or as a default for blank company code.

                   CoCde   CorID  Program   Variant   Default text

----------------------------------------------------

                   0001    SAP18  RFKORD80  SAP18

1.3. Examples for forms:

Make the entries either for individual or for all company codes explicitly, and/or as a default for blank company code.

        CoCd Program  Fo       Form

        --------------------------------------

        0001 RFKORD80          F140_CASH_DOC_01

Using transaction SE71, check whether the standard form is available in the client for which you needthe form. If the standard forms are not available, you can copy the missing forms from client 000 using transaction SE71. (Menu -> Utilities -> Copy from client).

You can also create your own forms by copying the standard forms and changing the text of the form (usually in MAIN window). Your forms must start with 'Y' or 'Z'. The form name should contain the identifier F140.

Your own and standard forms in clients other than 000 must be adapted to correspond with the standard form in client 000 when there is a new release.

If you need the standard or one of your own forms in a language that the form has not yet been translated into, you can translate the form using transaction SE63.

1.4. Sender details:

Make the entries either for individual or all company codes explicitly, and/or as default for blank company code.

CoCd Program  TXTID Header text      Footer text      Signature

                    Sender

-----------------------------------------------------------------------

0001 RFKORD80 ADRS  ADRS_HEADER      ADRS_FOOTER      ADRS_SIGNATURE

                    ADRS_SENDER

Using transaction SO10, check whether the standard texts are available in the clients for which yourequire them. The text ID is ADRS. If standard texts are not available, you can copy missing texts from client 000 using transaction SO10. (Menu -> Utilities -> Copy from client).

If you do not require certain details because they are already on the company stationery, for example,the header and footer text, you can leave the fields blank in the table. Usually, at least the standardtext for the signature is required. If however, you do not want to use a text, you should still make a default entry in the table to avoid error messages being issued (company code = blank and name of print program).

1.5. Examples for sort variants:

For cash documents, you have to define at least one sort variant. The sort variants determine the sequence in which the documents are output.

Sort variant           Name

Sequence  Field name   Name                           Offset Length

B1                     Doc. 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                     Doc.type, doc. number, year

1         BLART        Document type                         2

2         BELNR        Document number                       10

3         GJAHR        Fiscal year                         4

The sorting is first carried out by company code, and then in the field sequence of the relevant sort variant.

You can obtain a list of fields that you can sort by using the possible entries help (F4). The list contains a selection of fields from the document header table BKPF.

You can expand the list of fields for selection in accordance with your requirements. Using a repaircorrection, you can transfer fields that do not yet exist in table RF140U to table RF140UZZ. You mustensure however, that you are using the field names and data elements from the standard tables, sincethe fields from table RF140UZZ are provided with information corresponding to the name from the document header table. After you have expanded the fields, you have to activate table RF140UZZ.

1.6 Create report variants

Examples for report variants:

        Program RFKORD80

        SAP18  Sorting correspondence         B1

               Output to printer              Define printer, per

                                             company code if required

               Log to printer                 Define printer for error

                                             log, per company code if

                                             required

BAL Application Log Documentation   General Material Data  
This documentation is copyright by SAP AG.


Length: 14957 Date: 20120523 Time: 002140     triton ( 300 ms )