Ansicht
Dokumentation
RFKORDP3 - Printout of Customer Statements (Philippines)
TXBHW - Original Tax Base Amount in Local Currency Fill RESBD Structure from EBP Component StructureThis documentation is copyright by SAP AG.
Description
This program prints customer statements and open item lists as letters for customers and vendors. The customer statement is a special type of account statement.
A customer statement lists all clearing procedures between two key dates, for example, the date of the last statement and the current statement date. There then follows the open item list at the current statement key date and the balance at the key date.
An open item list contains all open items at a key date and the balance at that key date.
The customer statement and the open item lists can be supplemented by totals specifications for due items, open item sorted lists and specifications for noted items.
As a rule, the print program is only carried out directly during system configuration for testing purposes. Otherwise, the call is carried out automatically by means of higher-level correspondence programs.
This report is a version of report RFKORD11 that has been modified for use in the Philippines as follows.
Firstly, the statement shows the balance carried forward on the first key date, broken down into currencies. This is followed by the open items list and the balance on the second key date, which is also divided into different currencies.
The list of open items is divided into three groups. All the invoices are listed on the left of the form, with each invoice on a separate line. The payments are shown in the center of the list. If it is not clear which invoice a payment is related to, the payment is shown in a separate line. Down payments on invoices are shown directly opposite the invoices. Multiple down payments for the same invoice are listed together.
On the right side of the document, the balance of each item is shown. If more than one down payment has been made against an invoice, the balance is shown on the same line as the last down payment. Assuming the down payments and the invoice were all entered in the same currency, the balance will also be shown in this currency, otherwise, the balance will be shown in the local currency.
The list of items cleared between the two key dates has been modified only slightly, with a few changes to the way the information is laid out.
After that, the list shows the withholding tax data, covering all withholding tax line items for all the open and cleared items shown. Where the withholding tax was paid with the invoice, the invoice document is shown. If, on the other hand, the tax was not posted until the payment, the payment document is shown instead.
The list also includes a legend with a description of the document types used for the open and cleared items, and a list of the amounts overdue grouped according to the number of days overdue.
The way the document numbers are shown has also been modified slightly, so that the Sales and Distribution (SD) document number is shown, where available, instead of the Financial Accounting (FI) document number. You can also display the official receipt number instead, if you want, by changing all of the following variables in the SAPscript form F140_CUS_STAT_P1 as follows:
- GF_??NUM to GF_ORNUM
- GF_??NOP to GF_ORNOP
- GF_??NOC to GF_ORNOC
The question mark (?) is a wildcard character denoting any letter.
Requirements
Before you can print customer statements and open item lists within the correspondence function, the following requirements must be met.
- Configuration
- Make the basic settings for correspondence in the "Financial accounting global settings" Implementation Guide. You can find more detailed explanations on the standard settings further on in this program 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 (F140_CUS_STAT_P1).
The following restrictions apply to the creation of customer statements and open item lists:
- No statements can be created for one-time customers.
- Even in the case of head offices with local processing, customer statements and open item lists are addressed to the head office and not to the branch.
- Correspondence types for customer statements or open item lists with individual text cannot be used for the periodic account statements created by means of the program RFKORK00.
Output
A customer statement or an open item list is output for each customer or vendor. A separate spool request is created for each company code. For test purposes, the data can be displayed on the screen. If you do not specify for the print program on which printer the correspondence should 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, i.e. 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 should specify a printer for the log in the print program or the print program variant. If you do not make this specification, the program reacts as above (as for the printer for the correspondence). 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 maybe the correspondence type and/or the company code.
If the print program is carried out directly and a printout issued, then a log with the created spool requests is issued for each program run. If you do not specify for the print program on which printer the log should 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 carried out online, the log is displayed on the screen. If the program is planned as a job, the spool request name of the log 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 (for example, trigger for correspondence or periodic account statements).
Information about the Standard Form and Text Symbols
Information on the form layout
Information on the text symbols
Example
Make the settings for correspondence in the "Financial accounting global settings" Implementation Guide. 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 special company code exist. If you do not want this, you should only make
table entries with which the company code is predefined. For the relevant tables, there is a note below on the default entry company code.
The correspondence types, forms and standard texts which start with a Z are examples of customer-specific objects which are not delivered in the standard system.
1. "Financial Accounting global settings": Correspondence settings:
For customer statements or open item lists, the settings are to be made as follows.
1.1. Examples of the correspondence types:
A single statement means a statement which is issued for individual accounts as opposed to consolidated statements over several accounts. Currently only single statements are available.
SAP13 Customer statement (single statement)
X Account necessary
Number date specif... 2
Meaning date 1....... last statement
Meaning date 2....... current statement
SAP14 Open item list (single)
X Account necessary
Number date specif... 1
Meaning date 1....... OI at key date
SAP16 Open item list with payment advice (group)
X Account necessary
Number date specif... 1
Meaning date 1....... OI at key date
ZAP12 Individual customer statement (single)
X Account necessary
X Individual text
Number date specif... 2
Meaning date 1....... last statement
Meaning date 2....... current statement
ZAP13 Individual open item list (single)
X Account necessary
X Individual text
Number date specif... 1
Meaning date 1....... OI at key date
1.2. Examples of program allocation:
The entries for both single or all company codes, whether made manually and/or as default values, must be blank.
CCode CorID Program Variant Default text
----------------------------------------------------
0001 SAP13 RFKORD11 SAP13
0001 SAP14 RFKORD11 SAP14
0001 SAP16 RFKORD11 SAP16
0001 ZAP12 RFKORD11 ZAP12 ZF140_CUS_STAT
0001 ZAP13 RFKORD11 ZAP13 ZF140_OPI_LIST
1.3. Examples of default texts:
The default texts must be stored as a standard text with the text ID FIKO. For the use of individual texts, there must always be a standard text, which is entered during program allocation. A standard text must contain at least one comment line (format line = /*). Default texts can be maintained in the detail screen for program allocation via Goto -> Text editor or, in the initial menu, via Tools -> Word processing -> Standard text.
With the transaction SO10, you can check whether standard texts exist in the client in which you need them. The text ID is FIKO. You can copy standard texts from other clients with the transaction SO10 (Menu -> Utilities -> Copy from client).
Everyone wanting to use the text ID FIKO requires the necessary authorization. The authorization object for which the authorization must be defined is called "standard text". In the standard system, it is contained in the profile S_SACHBEARB and authorizes for every text ID. However, everyone needs the authorization for at least the text ID ST and FIKO.
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 an empty editor to enter the text.
Default text ZF140_CUS_STAT, TEXT-ID FIKO
Format Text area
/* Text for individual account statement
T5 Acct statement from &RF140-DATU1& to &RF140-DATU2&
T5
T5
Default text ZF140_OPI_LIST, TEXT-ID FIKO
Format Text area
/* Text for individual open items list
T5 Open item list for &RF140-STIDA&
T5
T5
If you want to enter individual text passages at several positions in the form, you can create the default text as in the following example:
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
T5 Text 1
/: ENDIF.
/: IF &RF140-ELEMENT& = 'YYY'.
/* Text in the text element YYY
T5 Text 2
/: ENDIF.
XXX and YYY represent numbers of text elements.
This option, however, cannot be applied in windows that do not contain events (text elements indicated by numbers).
If, however, you want to use certain individual text passages not only in the MAIN window but also simultaneously in, for example, the INFO window, you must add the following to all the text elements in your form that contain individual text passages:
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, whose names are
made up of the identification code F140, the user ID, the date of request and the time of 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 or are to be left blank as default for company code.
CCode Program Fo Form
--------------------------------------
0001 RFKORD11 F140_CUS_STAT_02
0001 RFKORD11 IT ZF140_CUS_STAT_2
0001 RFKORD11 VB F140_CUS_STAT_04
With the 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 copy the missing forms from client 000 with the transaction SE71 (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".
If you want to use a correspondence type for an open item list with payment advice on the basis of the form F140_CUS_STAT_02, you must change the text and the variable RF140-DATU2 to RF140-STIDA in the PAGE2 window.
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 translate the forms using the transaction SE63.
In the standard form for account statements and open items lists, preparations are made for the usage of individual texts or the direct usage of a standard text in the following text elements:
Form Window Text elements
F140_CUS_STAT_01 MAIN 510, 511
F140_CUS_STAT_02 MAIN 510, 511
In principle, however, you can use the individual texts at any position of a form.
Examples of form modifications:
Form ZF140_CUS_STAT_2
a.) Create the form ZF140_CUS_STAT_2 and copy
the form F140_CUS_STAT_02 into the form ZF140_CUS_STAT_2.
b.) Modify the text elements in the window MAIN as follows:
Format text area
/E 510
/* Acct stmnt from &RF140-DATU1& to &RF140-DATU2&
/: INCLUDE&RF140-TDNAME& OBJECT BKORM ID FIKO LANGUAGE
&RF140-TDSPRAS&
/E 511
/* Open item list for &RF140-STIDA&
/: INCLUDE&RF140-TDNAME& OBJECT BKORM ID FIKO LANGUAGE
&RF140-TDSPRAS&
During output, the variable RF140-TDNAME receives in each case the name of the individual text belonging
to a correspondence request. The variable RF140-TDSPRAS contains the entry language or output language of the text. The entire letter is issued in this language.
1.5. Sender details:
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 Program TXTID Header text Footer text Signature
Sender
-----------------------------------------------------------------------
0001 RFKORD11 ADRS_HEADER ADRS_FOOTER ADRS_SIGNATURE
ADRS_SENDER
With the transaction SO10, you should 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 copy the missing texts from client 000 with the transaction SO10 (Menu -> Utilities -> Copy from client).
If, on account of 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. Paymt DocNo. Act
------------------------------------------------------------------------
0001 SAP13 Customer statement (single) X X X X
0001 SAP14 Open item list (single) X X X X
0001 SAP16 Open item list (group) X X X X
0001 ZAP12 Indiv. cust. statement (single) X X X X
0001 ZAP13 Indiv. open item list (single) X X X X
1.7. Sort Variants for Correspondence:
There must be at least one sort variant defined for correspondence for customer statements and open item lists. You use the correspondence sort variants to determine the sequence in which the customer statements or the open item lists 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 sequence of 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 select contains a selection of fields from the master record tables KNA1, KNB1, LFA1 and LFB1. 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 fields "Document number" and "Fiscal year" 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, that are not yet in table RF140V, into table RF140VZZ: KNA1, KNB1, LFA1 and LFB1. When doing so, you must take care to use the field names and data elements from the standard tables, as the fields in table RF140VZZ are supplied using the names from the master records. After you have added these fields, you must 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 and then from KNB1 or LFB1.
For this reason, fields that have the same name in tables KNA1 and KNB1 or LFA1 and LFB1 may be overwritten.
1.8 Sort variants for line items:
There must be at least one sort variant for the OI list and for customer statements as well as one sort variant for clearing procedures. You can use the sort variants for line items to determine the sequence in which the line items are displayed.
Sort variant Name
Sequence Field name Name Offset length
P1 Document date, ref.or doc.no.
1 BLDAT Document date 8
2 HBELN Ref.no.otherwise doc.no. 16
3 BUZEI Item 3
P2 Sp.G/L ind.,doc.date, doc.no.
1 UMSKZ Special G/L indicator 1
2 BLDAT Document date 8
3 HBELN Ref.no. otherwise doc.no. 16
4 BUZEI Item 3
P3 Document date, document number
1 BLDAT Document date 8
2 BELNR Document number 10
3 BUZEI Item 3
P4 Document date, reference
1 BLDAT Document date 8
2 XBLNR Reference 16
3 BUZEI Item 3
P5 Clearing date, clearing document
1 AUGDT Clearing date 8
2 AUGBL Clearing document 10
3 BLDAT Document date 8
4 HBELN Reference without document number 16
5 BUZEI Item 3
P6 Group open items
1 KONTO Account 10
2 BLDAT Document date 8
3 XBLNR Reference 16
4 BUZEI Item 3
P7 Group clearing procedures
1 KONTO Account 10
2 AUGDT Clearing date 8
3 AUGBL Clearing document 10
4 BLDAT Document date 8
5 HBELN Reference otherwise document number 16
Objects are always sorted initially by company code and thereafter in the sequence of the fields in the sort variant being used. If the sort variant for line items contains the field UMSKZ in one of its five sort fields, the standard system issues a sub-heading with the name of the special G/L indicator in cases where the special G/L indicator has changed for lists of open items or open noted items. If you do not require this, you can deactivate the appropriate heading lines from the form for account statements or open item lists by using the format column (enter "/*").
To obtain a list of the fields by which the objects are sorted, select "Possible entries" (F4). This list of fields that the user can select from contains a range of fields from the document tables BKPF and BSEG. The field HBELN contains the reference number in case this is needed; otherwise it contains the document number.
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 tables BKPF and BSEG, that are not yet in table RF140W, into table RF140WZZ. When doing so, you must take care to use the field names and data elements from the standard tables, as the fields in table RF140WZZ are supplied using the names from the documents. After you have added these fields, you must activate table RF140WZZ. 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 BKPF data and then from the BSEG data.
For this reason, fields that have the same name in tables BKPF and BSEG may be overwritten.
2. Account statements:
You make the following settings under "Correspondence" in the "Accounts Receivable and Accounts Payable" Implementation Guide.
2.1. Period types:
The definition of the period types is used for the validation and the PF4 help for the customer master
record field "Account statement" and with the parameter for indicators in the master record of the program, for periodic account statements.
Acct Statement Text
---------------------------------------
1 weekly account statement
2 monthly account statement
2.2. Examples of program variants for customer statements:
Program RFKORD11
SAP13 Correspondence sorting K1
OI list sorting P1
Clearing procedure sorting P5
Statement also w/o items X
Key date for due days _______ Standard 1
Net due date sorted list X
Overdue sorted list X
Due date sorted list ___ 30 60 ___ ___
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)
SAP14 Correspondence sorting K1
OI list sorting P1
Open item list X
Statement also w/o items X
Key date for due days _______ Standard 1
Net due date sorted list X
Overdue sorted list X
Due date sorted list ___ 30 60 ___ ___
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)
SAP16 Form set VB
Correspondence sorting K1
OI list sorting P6
Open item list X
Buying group X
Statement also w/o items X
Key date for due days _______ Standard 1
Net due date sorted list X
Overdue sorted list X
Due date sorted list ___ 30 60 ___ ___
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)
ZAP12 Form set IT
Correspondence sorting K1
OI list sorting P1
Clearing procedure sorting P5
Statement also w/o items X
Key date for due days _______ Standard 1
Net due date sorted list X
Overdue sorted list X
Due date sorted list ___ 30 60 ___ ___
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)
ZAP13 Form set IT
Correspondence sorting K1
OI list sorting P1
Open item list X
Statement also w/o items X
Key date for due days _______ Standard 1
Net due date sorted list X
Overdue sorted list X
Due date sorted list ___ 30 60 ___ ___
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)
RFUMSV00 - Advance Return for Tax on Sales/Purchases BAL Application Log Documentation
This documentation is copyright by SAP AG.
Length: 67550 Date: 20240601 Time: 053243 sap01-206 ( 476 ms )
