RFKORDP2 - Printout of Official Receipts Before Payment (Philippines)

ROGBILLS - Synchronize billing plans   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.
SAP E-Book

Description

You use this report to create official receipts from invoices prior to payment, as required in the Philippines. Users in Singapore can also use this report to create invoices for customers directly from Financial Accounting (FI).

Use in the Philippines

In the Philippines, you can use the report to create official receipts for invoices, and print copies of them later on. When you create an official receipt, the system assigns it a number automatically. When you print a copy of an invoice, you have to enter the number of the receipt that you want reprint (or enter the invoice number instead). In both cases, you must enter a receipt lot.

Use in Singapore

In Singapore, you use the report to create invoices from FI. In this case, the numbering functions are not activated.

As a rule, the print program is only carried out directly, for test purposes, during the system configuration. In all other cases, it is called up automatically by higher-level correspondence programs.

Requirements

Before you print internal documents for correspondence purposes, the following requirements must be met.

  1. 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.
  1. Define forms
Forms must be defined and activated so that you can print the correspondence you require. A form is delivered in the standard system which you can copy and adjust as necessary.
In the standard system, forms F140_INT_PHIL_01 and F140_INT_SING_01 are used.
  1. Correspondence types for internal documents with individual texts cannot be used for the internal documents created with program RFKORB00.

Output

Every document is issued separately. A separate spool request is created per company code. For test purposes, documents can also 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, a log of the generated spool requests is printed per 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 run online, the log is displayed on the screen. If the program is planned as a job, the spool request name of the log consists of the ID F140, the printer name, 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 program (for example, trigger for correspondence or internal document).

Information about the Standard Form and Text Symbols

Information on form layout

Information on text symbols

Example

Customizing for internal documents is described in the following, on the basis of the standard delivery system, with an example of customer-specific adaptations.

Customizing:

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 the company code is permitted, the system refers back to the default entry if there are no entries available for a specific company code. If you do not want this, you should make sure that you only make table entries for which the company code is specified. A note on the default entry company code blank is available further down in the relevant tables.

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

1. "Financial Accounting Global Settings": Correspondence Settings:

For internal documents, maintain the base parameters as follows.

Do not maintain the sender details, since the internal documents are not sent in letter form.

1.1. Examples of the various correspondence types:

             SAP09  Internal document

                    X Document required

             ZAP08  Internal documents with individual note

                    X Document required

                    X Individual text

1.2. Examples of program allocation

The entries should be made either explicitly for individual company codes or all company codes or as a default for company code blank.

                    CoCde  CorID  Program  Variant   Proposed text

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

                   0001    SAP09  RFKORD30  SAP09

                   0001    ZAP08  RFKORD30  ZAP08    ZF140_INT_DOCU

1.3. Examples of text proposals

The text proposals must be stored as a standard text with the text ID FIKO. For individual texts, a text reference must exist which is entered during program allocation. A text reference must contain at least one comment line (format line = /*). Text proposals can be maintained in the detail screen for program allocation via Goto -> Text editor or in the configuration menu via Tools -> Word processing -> Standard text.

With Transaction SO10 you can check to see whether standard texts are available in the client in which you need them. The text ID is FIKO. You can use Transaction SO10 to copy standard texts from other clients (Menu -> Utilities -> Copy from client).

You need the relevant authorization to use Text ID FIKO. The authorization object for which the authorization must be defined is called "Standard text". In the standard system it is included in the profile S_SACHBEARB and authorizes you to use all text ID's. However, everyone needs authorization for at least text ID's ST and FIKO.

In the standard text you can only use those paragraph formats which have been defined for the corresponding form.

If you enter a language on requesting correspondence, into which the text proposal has not been translated, the system displays an empty text editor in which you can enter your text.

Text proposal ZF140_INT_DOCU, TEXT-ID FIKO

Format  Text area

/*      Individual note on internal document

AF      &ULINE(72)&

AF

If you want to enter individual passages at various points in the text, you can create a text proposal based on the following example:

Text proposal ZEXAMPLE, TEXT-ID FIKO

Format  Text area

/*      Example for several individual text passages

/:      IF &RF140-ELEMENT& = 'XXX'.

/*      Text in text element XXX

AF      Text 1

/:      ENDIF

/:      IF &RF140-ELEMENT& = 'YYY'

/*      Text in text element YYY

AF      Text 2

/:      ENDIF.

XXX and YYY represent numbers of text elements.

In windows which contain no text elements marked by numbers, this possibility cannot be used however.

On the basis of the text proposals, individual texts whose name consists of the ID F140, the user name, the request date and the time the text was created, are then generated per correspondence type. These texts can be changed with the maintenance transaction for correspondence requests.

1.4. Examples for the forms

The entries are either made explicitly for individual or all company codes or as a default for company code blank.

        CoCd Program FS        Form

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

        0001 RFKORD30          F140_INT_DOCU_01

        0001 RFKORD30 IT       ZF140_INT_DOCU_1

With transaction SE71 you should check to see whether the standard form is available in the client you require. If standard forms are not available, you can copy the missing forms from client 000 with transaction SE7 1 (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 "Y" or "Z". The form name should contain the ID "F140".

Your own forms or standard forms in clients other then client 000, may need to be modified to comply with the standard form in client 000 when there are release changes.

If you need the standard form or an individually created form in languages for which there are, as yet, no translations, you can translate the forms using transaction SE63.

In the standard form for internal documents, provision has been made for the use of individual texts or the direct use of a standard text in the following text elements:

        Form                Window  Text elements

        F140_INT_DOCU_01    MAIN     510

On principle, however, you can use the individual texts at any place in the form.

Examples of form modifications

Form ZF140_IND_DOCU_1

a.) Create the form ZF140_IND_DOCU_1. Transfer form F140_IND_DOCU_01 to form ZF140_IND_DOCU_1.

b.) Modify text element 510 in the MAIN window as follows:

    Format Text area

    /E     510

    /:     INCLUDE &RF140-TDNAME& OBJECT BKORM ID FIKO LANGUAGE

           &RF140-TDSPRAS

On output, the variable RF140-TDNAME contains the name of the individual text belonging to a correspondence request. Variable RF140-TDSPRAS contains the input or output language of the text. The entire letter is issued in this language.

Example for including document long texts:

If you have entered texts for a document and want them to be printed in the 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 the "Financial Accounting global settings" Implementation Guide in the "Define text IDs for documents" step.
  • 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.5. Call options

The entries should be made either explicitly for individual or all company codes or as a default for company code blank.

CoCd Type of correspondence                     DocEnt No.   DocDis Act

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

0001 SAP09 Internal document                    X             X     X

0001 ZAP08 Internal document with indiv. note   X             X     X

1.6. Examples of Sort Variants:

For internal documents, you must define at least one sort variant for the internal documents. You use the sort variants to determine the sequence in which the internal documents are printed.

Sort variant           Name

Sequence  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

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 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, that are not yet in table RF140V, into table RF140UZZ. When doing so, you must take care to use the field names and data elements from the standard tables, as the fields in table RF140UZZ are supplied using the names from the master records. After you have added these fields, you must activate table RF140UZZ.

1.6 Examples for report variants

        Program RFKORD30

        SAP09  Correspondence sorting        B1

               No. of lines in address       3

               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)

        ZAP08  Form set                      IT

               Correspondence sorting        B1

               No. of lines in address       3

               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)






Vendor Master (General Section)   PERFORM Short Reference  
This documentation is copyright by SAP AG.


Length: 26478 Date: 20140917 Time: 173154     sap01-206 ( 97 ms )

consolut Transport Check

The consolut Transport Check is a simple and reliable tool that helps you identify dependencies between transport orders.

consolut Transport Check