SAP Program RFKORD20 - Print Program: Charges for a Bill of Exchange

Description
This program prints bill of exchange charges statements for customersand vendors. You can also choose to have the transfer posting printedas well when an untransferred bill of exchange is extended.
You only directly execute this print program for testing purposesduring configuration. The higher-level correspondence programs executeit automatically.

Precondition
Before you can print statements of bill of exchange charges withincorrespondence, the following requirements must be met:
Configuration
The basic settings for correspondence must be made in the "FinancialAccounting Global Settings" IMG. You can find more detailedexplanations of the standard settings further on in this programdocumentation.
Defining forms
Forms must be defined and activated in the system so that you can printthe required letters. The standard system provides a form you can copyand correspondingly adapt to your requirements.
The form F140_BILL_CHA_01 is used in the standard system.
RESET N1
The following restrictions apply to the creation of bill of exchangecharges statements:
Bill of exchange charges statements can only be output as long as thebill of exchange liability is not yet cleared.
Intercompany transactions are not supported.
Even with head offices with local processing, bill of exchange chargesstatements are also addressed to the head office and not to the branch.
Clearings between customers and vendors are not considered. Customersand vendors receive separate letters.

Output
For customer or vendor of a document for which bill of exchange chargeswere incurred, a bill of exchange charges statement is created. Aseparate spool request is created for each company code. For testpurposes, the data can be displayed on the screen. If you do notspecify for the print program on which printer the correspondenceshould be printed, the program may take the printer specified in theuser master of the user who started the program or the printerspecified when the job is scheduled.
If minor errors occur during the program run, i.e. errors that do notlead to a program termination, these are listed after the run in anerror list. If you want these error lists to be printed on a certainprinter, you should specify a printer for the log in the print programor the print program variant. If you do not make this specification,the program reacts as above (as for the printer for thecorrespondence). If the program is run online, the error list isdisplayed on the screen. If, however, the program is scheduled as ajob, the job request name for the error list is composed of theidentifier F140ER, the printer name and maybe the correspondence typeand/or the company code.
If the print program is carried out directly, a log with the createdspool request is output for each program run if a print request wascarried out. If you do not specify for the print program on whichprinter the log should be printed, the program may take the printerspecified in the user master of the user who started the program or theprinter specified when the job is scheduled. If the program is carriedout online, the log is output on the screen. If the program is plannedas a job, the spool request name of the log is made up of theidentifier F140, the printer destination, the date of creation and theprogram ID KORD. If the print program is started by a higher-levelcorrespondence program, the log entry is carried out by thehigher-level program (trigger for correspondence).

Information about the Standard Form and Text Symbols
INCLUDE FI_RFFO_SAPSCRIPT_LAYOUT_SET OBJECT DOKU ID TX
Information on form layout
Information on text symbols
INCLUDE FI_RFFO_SAPSCRIPT_MAINTAIN OBJECT DOKU ID TX

Example
Customizing for bill of exchange charges statements is explained belowby means of the standard system.

Customizing:
Make the settings for correspondence in the "Financial accountingglobal settings" Implementation Guide. There you maintain thesuboptions in accordance with the following guidelines.
Note:
With tables in which a default entry without company code is allowed,the default entry is accessed if no entries for the special companycode exist. If you do not want this, you should only make table entrieswith which the company code is predefined. With the relevant tables,there is a note on the default entry company code blank below.

1. "Financial Accounting global settings": Correspondence settings:
For bill of exchange charges statements, the base parameters are to bemaintained as follows.
For bill of exchange charges statements, the call options are not to bemaintained since bill of exchange charges statements are alwaysrequested automatically.
SAP07 is predefinded as a correspondence type for bill of exchangecharges statements.
1.1. Example of the correspondence types:
SAP07 Bill of exchange charges statement
X Document necessary
1.2. Example of program allocation:
The entries are to be left blank either explicitly for individual orall company codes or as a default for company code.
CCode CorID Program Variant Default text
----------------------------------------------------
0001 SAP07 RFKORD20 SAP07
1.3. Example of the forms:
The entries are to be left blank either explicitly for individual orall company codes or as a default for company code.
CCode Program Fo Form
--------------------------------------
0001 RFKORD20 F140_BILL_CHA_01
With the transaction SE71, you should check whether the standard formexists in the client in which you need it. If standard forms do notexist, you can copy the missing forms from client 000 using thetransaction SE71 (Menu -> Utilities -> Copy from client).
You can create your own forms by copying the standard form and changingthe layout set text (generally in the MAIN window). Your forms muststart with "Y" or "Z". The form name should contain the identificationcode "F140".
Your own forms or standard forms in clients not equal to 000 might haveto be adapted during release changeovers according to the standard formin client 000.
If you need the standard form or a form you created in languages forwhich no translation exists, you can translate the forms using thetransaction SE63.
Example for including document long texts:
If you have entered texts for a document and want them to be printed inthe correspondence, proceed as follows:

  • Copy the standard form into an individual customer form.

  • Determine the window and, if necessary, the text element in which you
  • want to print the document text.
    • Determine which data is available when printing the window or text
    • element by using the program documentation (for example, tables BKPF,BSEG, BSID, BSIK, RF140 fields)
      • Define the text ID of the document long text which you want to print
      • (for example, 001) within Financial Accounting customizing via Businesstransactions -> Base parameters -> Texts -> Document texts.
        • Then insert two lines similar to the following lines at the required
        • position on the form.
          /: DEFINE &TEXTNAME& := '&BKPF-BUKRS(*)&&BKPF-BELNR(*RF0)&&BKPF-GJAHR&'
          /: INCLUDE &TEXTNAME& OBJECT BELEG ID 0001 LANGUAGE &RF140-SPRAS&
          1.4. Sender details:
          The entries are to be left blank either explicitly for individual orall company codes or as a default for company code.
          CCode Program TXTID Header text Footer text Signature
          Sender
          -----------------------------------------------------------------------
          0001 RFKORD20 ADRS_HEADER ADRS_FOOTER ADRS_SIGNATURE
          ADRS_SENDER
          Using the transaction SO10, you should check whether standard textsexist in the client in which you need them. The text ID is ADRS. Ifstandard texts do not exist, you can copy the missing texts from client000 using the transaction SO10 (Menu -> Utilities -> Copy from client).
          If you do not need individual specifications, such as header text andfooter text due to printed company paper, you can leave the respectivefields in the table blank. Normally, however, at least the standardtext is required for the signature. You should, however, enter adefault entry (company code = blank and name of the print program) inthe table to avoid error messages if you do not want to use texts.
          1.5. Examples of Sort Variants:
          There must be at least one sort variant defined for correspondence forbill of exchange charges statements. You use the correspondence sortvariants to determine the sequence in which the bill of exchangecharges statements are printed.
          Sort variant Name
          Sequence 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
          All objects are sorted first by company code and then in the sequenceof fields specified in the sort variant being used.
          To display a list of the fields by which an object can be sorted by,select "Possible entries" (F4). This list of the fields you can selectcontains a selection of fields from the master record tables KNA1,KNB1, LFA1 and LFB1. The fields KOART, KONTO, KTOGR (KNA1-KTOKD orLFA1-KTOKK)and KTOZE (KNB1-KNRZE or LFA1-LNRZE) are filled inaccordance with the account type, which is taken from the master recordtables. The fields "Document number" and "Fiscal year" are only filledin the case of document-related correspondence, such as paymentnotices.
          You can extend this list of selectable fields in order to meet yourrequirements. To do so, you can use a repair correction to importfields from the following tables, that are not yet in table RF140V,into table RF140VZZ: KNA1, KNB1, LFA1 and LFB1. When doing so, you musttake care to use the field names and data elements from the standardtables, as the fields in table RF140VZZ are supplied using the namesfrom the master records. After you have added these fields, you mustactivate table RF140VZZ. The sort fields are then supplied inaccordance with their names and in a pre-defined sequence as follows:
          The sort fields are drawn first from the KNA1 or LFA1 data and thenfrom KNB1 or LFB1.
          For this reason, fields that have the same name in tables KNA1 and KNB1or LFA1 and LFB1 may be overwritten.

          2. Bill of Exchange Charges Statement:
          You define the variants in the "Accounts Receivable and AccountsPayable" Implementation Guide under the "Bill of exchange chargesstatement correspondence" option.
          Program RFKORD20
          SAP07 Correspondence sorting K1
          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)

1377767FB 561 for print program for bill of exchange charges
145200Correspondence: data from central address management
366042Expiring currencies processes FI
362277Expiring currencies: correspondence