Programme SAP RFKORDJ2 - Receipt Before Payment (Japan)

Description
This program prints receipts for payments in cash, bills of exchange orchecks which have not been cleared. The program creates the receipts inexactly the same way as RFKORDJ1, but the open items are not clearedyet. Depending on the transaction, receipts can be created as incomingpayments via the noted item. The noted items must also be cleared whenyou post an incoming payment.
The receipt is subject to tax in Japan. The tax, INSHI-ZEI, isdependent on the amount in the receipt. The system automaticallydetermines the (stamp) tax and prints the tax amount on the receipt. Aninternal (or external) number is assigned for each receipt.
The program 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 issuing the receipt.

  • Optimized receipts Type = SAPQ4

    • The system determines the smallest total tax amount and minimum andminimal number of issues of the receipt per payment document. Thenumber of receipts is, however, limited to a maximum of three.
    You enter a highest amount per receipt as a program 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 entered.

      Precondition
      Before you can print payment notices within correspondence, thefollowing requirements must be met:
      Configuration
      Make the basic settings for correspondence in the "Financial AccountingGlobal Settings" Implementation Guide. You can find more detailedexplanations on 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 adapt to your own requirements.
      In the standard system, the form F140_RECEIPT_J1 is used.
      RESET N1
      The following restrictions apply to the creation of payment notices:
      Only postings which are created by means of functions in which apayment amount is set in at least one customer line item of theincoming payment document are supported. The corresponding functionsare at present "Internal transfer posting with clearing", "Incomingpayments", "Fast entry of incoming payments" and "Outgoing payments".For a payment amount to be determined by the system for thesefunctions, all bank accounts, bank subaccounts, bank clearing accountsor bill of exchange reconciliation accounts to which postings are madewithin the framework of these functions must be flagged as cashflow-relevant in the G/L account master record.
      Intercompany transactions are not supported.
      Even for head offices with local processing, payment notices areaddressed to the head office and not to the branch.
      In the case of document extracts sent to one-time customers, businesstransactions can be posted in a document for one customer only.
      With clearings between customers and vendors, a payment noticeaddressed to the customer is created for each customer/vendor pair ifthe corresponding flag is set in the master records.

      Output
      Receipts are created for each customer of a document.
      For test purposes, the receipts can be displayed on the screen. If youdo not print a receipt, however, the receipt number entered is lost.
      If you do not specify a printer for the correspondence in the printprogram, the printer is selected from the user master of the person whostarted the program or the printer specified when scheduling the job istaken.
      If errors occur during a program run which are not serious enough tocause termination of the processing, an error list is issued at the endof the program run. If error lists are to be printed on a particularprinter, then you must determine a printer for the log for the printprogram or the variants of the program. If you do not specify a printerfor the log in the print program, the printer is selected from the usermaster of the person who started the program or the printer specifiedwhen scheduling the job is taken. If the program is carried out online,then the error list is displayed on the screen. If the program isscheduled as a job, the spool request name of the error list consistsof the identifier F140ER, the printer name and, if necessary, thecorrespondence type as well as the company code.
      If the print program is carried out directly and a printout takesplace, a log with the created spool orders is issued for each programrun. If you do not specify a printer for the log in the print program,the printer is selected from the user master of the person who startedthe program or the printer specified when scheduling the job is taken.If the program is carried out online, the log is displayed on thescreen. If the program is scheduled as a job, the spool request name ofthe log is made up of the identifier F140, the printer name, the dateof creation and the program ID KORD. If the print program is started bya higher-level correspondence program, the log is issued by means ofthe higher-level program (trigger for correspondence).

      Explanation of the standard form
      In the standard system, this is the form F140_RECEIPT_J1. The name ismade up of: Program identification code_form name_number.
      The form consists of the pages FIRST (first page).

      The windows in the correspondence
      The following windows must be defined for the correspondence:
      HEADER
      The company code-dependent standard text you have stored in the systemis used in the letter header.
      ADDRESS
      The company code-dependent standard text for the sender details storedin the system and the customer's address are inserted in the addresswindow. The formatting of the address complies with postal regulations.
      INFO
      General information is shown here - for example, receipt number, dateof issue, amount of stamp tax.
      FOOTER
      In the footer of the opening page of the letter, the appropriatecompany code-dependent standard text is inserted.
      MAIN
      By means of its text elements, the main window defines the contents andappearance of the letter text.

      The text elements for the correspondence
      There are the following elements for the "MAIN" window:
      The text element 701 is used for issuing summary details for thepayment transaction.
      The complimentary closing and the signature (text element 590) concludethe letter.
      The following elements exist for the "INFO" window:
      Text element 710 issues the receipt number, the date of issue and theamount of the stamp tax.

      Text symbols you can use
      When the forms are set up with SAPscript, text symbols are included inthe text, which are then replaced by the appropriate values when theprint programs are run. The fields that can be used for this purposeare defined in the Repository and can be used in the following order asthe program runs:

      • Company code details

        • Company code table data (table T001)
        Company code address (internal structure RAADR)
        Sender details (table T001G)
        • Letter and reply

          • During the whole time of the output of the letter and of the reply, thefollowing can be used:
          Letter recipient = customer, one-time customer, vendor, one-time vendorfrom document (internal structure DKADR)
          Accounting clerk (table T001S)
          Account with which items were cleared: vendor, one-time vendor fromdocument (internal structure DKAD2)
          Accounting clerk (table *T001S)
          Depending on the combination of letter recipient and clearing account,you can, in addition to the structures listed above, use master recorddata in the fields belonging to tables KNA1, KNB1, LFA1 and LFB1.
          If the letter recipient is a one-time customer or one-time vendor, youcan use data from the fields belonging to table BSEC.
          Address data of the creator of the payment document (table USR03)
          The following RF140 fields: 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 field RF140-ELEMENT contains the three-digit number of the textelement to be printed.
          If the field BSEG-SGTXT, BSID-SGTXT or BSIK-SGTXT can be used in a textelement, then a text is only issued if there is a * at the beginning ofthe line item text.
          Letter: 140-BELEGNUM

          Example
          Customizing for payment notices is explained below by means of thestandard system, with examples of customer-specific enhancements.

          Customizing:
          Make the settings for correspondence in the "Financial accountingglobal settings" Implementation Guide. Make the settings for thepayment notices under the "Payment notices" option in the "AccountsReceivable and Accounts Payable" Implementation Guide. There youmaintain 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 codeexist. If you do not want this, you should only make table entries incases where the company code is predefined. For the relevant tables,there is a note further down on the default entry company code blank.
          The correspondence types, forms and standard texts which start with a Zare examples of customer-specific objects which are not delivered inthe standard system.

          1. "Financial Accounting global settings": Correspondence settings:


          For payment notices, make the settings as follows:
          1.1. Examples of the correspondence 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 allocation:
          The entries are to be left blank for single or explicitly for allcompany codes or are to be left blank as a 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 which aredefined for the relevant form.
          If you enter a language for the correspondence request, into which thedefault text is not translated, you receive an empty editor to enterthe text.
          Default text ZEXAMPLE, 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 containtext elements (text elements are 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 alltext elements in your form for which individual text passages are to beissued 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 eachcorrespondence request, whose names are made up of the identificationcode F140, the user ID, the date of request and the time of the textcreation. These texts can be changed with the maintenance transactionfor correspondence requests.
          1.4. Examples of the forms:
          The entries are to be left blank either for individual company codes orexplicitly for all company codes and/or as a 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 formsexist in the client in which you need them. If standard forms do notexist, you can copy the missing forms from client 000 with 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 a "Y" or a "Z". The form name should contain theidentification code "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 created by you in languages forwhich no translation exists, you can translate the forms using thetransaction SE63.
          In the standard form for payment notices, preparations are made for theusage of individual texts or the direct usage of a standard text in thefollowing text elements:
          Form Window Text elements
          F140_RECEIPT_J1 MAIN 701, 590
          In principle, however, you can use the individual texts at any positionof a form.
          Examples of form modifications:
          Form ZF140_RECEIPT_J1
          a.) Create the form ZF140_RECEIPT_J1 and copy
          the form F140_RECEIPT_J11 into the form ZF140_RECEIPT_J1.
          b.) Modify the text elements 701 and 590 in the MAIN window
          1.5. Sender details:
          The entries are to be left blank either for individual or explicitlyfor all company codes or are to be left blank as default for companycode.
          CCode Program TXTID Header text Footer text Signature
          Sender
          -----------------------------------------------------------------------
          0001 RFKORDJ2 ADRS_HEADER ADRS_FOOTER ADRS_SIGNATURE
          ADRS_SENDER
          With 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 with the transaction SO10 (Menu -> Utilities -> Copy from client).
          If, on account of company stationery, you do not require individualspecifications - such as the header text and the footer text - you canleave the respective fields in the table blank. Normally, however, atleast the standard text for the signature is needed. You should,however, make a default entry (company code = blank and name of theprint program) in the table to avoid error messages if you do not wantto use texts.
          1.6. Call options:
          The entries are to be left blank either for individual or explicitlyfor all company codes or are to be left blank as default for companycode.
          CCode Type of correspondence DocEnt.Pmnt DocDsp Act
          -----------------------------------------------------------------------
          0001 SAPQ4 Receipt optimized before clearing X
          0001 SAPQ5 Individual receipt before clearing X
          1.7. Correspondence sort variants:
          You determine the order in which the payment notices are issued usingthe sort variants for correspondence.
          Sort variant Name
          Order Field name Name Offset length
          K1 Sorting by postal code
          1 LAND1 Country 3
          2 HPSTL P.O.box post.code otherwise post.code 10
          3 KOART Account type 1
          4 KONTO Account 10
          K2 Sorting by account number
          1 KOART Account type 1
          2 KONTO Account 10
          K3 Sorting 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 as well as table BSEC for one-time account data.The fields KOART, KONTO, KTOGR (KNA1-KTOKD or LFA1-KTOKK)and KTOZE(KNB1-KNRZE or LFA1-LNRZE) are filled in accordance with the accounttype, which is taken from the master record tables. The fields'Document number' and 'Fiscal year' are only filled in the case ofdocument-related correspondence, such as payment notices.
          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, LFB1 and BSEC. When doing so,you must take care to use the field names and data elements from thestandard tables, as the fields in table RF140VZZ are supplied using thenames from the master records or one-time account data. After you haveadded these fields, you must activate table RF140VZZ. The sort fieldsare then supplied in accordance with their names and in a pre-definedsequence as follows:
          The sort fields are drawn first from the KNA1 or LFA1 data and thenfrom KNB1 or LFB1 and finally from BSEC data.
          For this reason, fields that have the same name in tables KNA1, KNB1and BSEC or LFA1, LFB1 and BSEC may be overwritten.
          2.1. Examples of program variants:
          You make the settings for the program variants under the "Paymentnotices" option in the "Accounts Receivable and Accounts Payable"Implementation Guide.
          Program 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