FUNCTIONAL SPECIFICATION DOCUMENT

1867 Configuracíon de “layout” de cheques. Formulario de cheque

en SAP..

_______________________________________
DOCUMENT ORIGIN

PROJECT / CHANGE ANDES PROJECT

BUSINESS REQUIREMENT 1867 CONFIGURACÍON DE “LAYOUT” DE CHEQUES.

DOCUMENT FORMULARIO DE CHEQUE EN SAP..
REQUESTER CHEQUE EN SAP.

PROCESS CHEQUES. FORMULARIO DE CHEQUE

ALEX FERNANDEZ
RESPONSIBLE ANALYST

Enock Alves
RESPONSIBLE MANAGER

COMPLEXITY Low Medium High

OBJETC TYPE

Report Interface Conversion ABAP online

Enhancement Form Other

REVISION HISTORY

VERSION DATE REVISIONS CHANGE REQUEST

OR TICKET
NUMBER
CONTENTS

1. BUSINESS AREA VIEW............................................................................4

1.1. Objective and purpose....................................................................................................................... 4

1.2. SAP modules involved....................................................................................................................... 4

1.3. AS IS vs. TO BE................................................................................................................................... 4

1.4. Expected results................................................................................................................................. 4

1.5. Business areas / Divisions impacted and/or involved.....................................................................4

1.6. Processes impacted and/or involved................................................................................................4

2. FUNCTIONAL SPECIFICATION CONTENT.............................................5

2.1. Development....................................................................................................................................... 5
2.1.1. Objects........................................................................................................................... 5
2.1.2. Detailed description of the development.........................................................................5
2.1.3. Formulario Cheque Compensar y el Fundación Salud Bosque......................................6
2.1.4. Comprobante de Egreso Compensar:............................................................................7
2.1.5. Datos cabecera del comprobante egreso Compensar....................................................7
2.1.6. Campo Detalle comprobante de egreso Compensar......................................................8
2.1.7. Comprobante de Egreso Fundación Salud Bosque........................................................8
2.1.8. Datos cabecera del comprobante egreso Fundación Salud Bosque..............................9
2.1.9. Datos detalle del comprobante egreso Fundación Salud Bosque..................................9
2.1.10. Campo pie de página comprobante egreso Fundación Salud Bosque...........................9
2.1.11. Campo Detalle.............................................................................................................. 10
2.1.11.1 Selection screen....................................................................................................... 10
2.1.11.2 Selection screen layout.............................................................................................10
2.1.11.3 Output layout (Form / Report / File)..........................................................................10
2.1.12. Input / Output Files....................................................................................................... 10
2.1.12.1 Interface type............................................................................................................ 11
2.1.12.2 Source and Destination Systems..............................................................................11
2.1.13. Proessing Log............................................................................................................... 11
2.1.14. Access authorization..................................................................................................... 11
2.1.15. Error Log....................................................................................................................... 11
2.1.16. Processing controls and procedures.............................................................................11
2.1.17. Test requirements......................................................................................................... 12
2.1.18. Regression test requirements.......................................................................................12
2.1.19. Parameter table............................................................................................................ 12
2.1.20. Reference documents and additional information.........................................................17
1. BUSINESS AREA VIEW

1.1. Objective and purpose

It is required to configure the check formats in the system in order to print them, for this the following must be taken into account:
• The system will control the consecutive number of checks per remittance. This should be consistent across the print and across the
system.
• Include the name of the user who made the accounting and the name of the user who made the payment application in the
prepared and revised fields of the egress receipt.
• Store in the system the signatures authorized by the treasury and that these can be seen in the printing of the checks as illustrated
in the following image (attachments page 9)

1.2. SAP modules involved

FI-TR - Payment Management

1.3. AS IS vs. TO BE

Chile needs a development that controls payments to suppliers.

1.4. Expected results

The expected result is the check impression

1.5. Business areas / Divisions impacted and/or involved

Finance Treasury Area

1.6. Processes impacted and/or involved

Check Printing - Format

2. FUNCTIONAL SPECIFICATION CONTENT

2.1.1. Development
2.1.2. Objects
A format must be made for printing the check from the bank with the respective proof of payment for the payments made by this
entity.

• The system will control the consecutive number of the checks. This should be consistent across the print and across the
system.

• Include the name of the user who made the accounting and the name of the user who made the payment application in the
prepared and revised fields of the payment receipt.

• Store in the system the signatures authorized by the treasury and that these can be contemplated in the printing of the
checks.

2.1.3. Detailed description of the development

It is necessary to generate a form for the printing of the check and proof of withdrawal from the Bank with digitized signatures, which
applies, to Compensating and form for printing the check and proof of expenditure.

You want to get a check form from the bank that will have the option to print the Check.

The fields that must be taken into account when printing the check are:

• Year: year in which the check is printed

• Month: month in which the check is printed
• Day: day on which the check is printed
• $: Amount to pay of the account payable
• Pay to order: Payee of payment
• The sum of: Value in letters of the value of the account payable
• Authorized signatures (s): Digitized signatures of the people

The fields that must be taken into account when printing the receipt, at the time the option "Print check" is executed, are:

• Year: year in which the account payable was paid.

• Month: month in which the account payable was paid
• Day: day on which the account payable was paid.
• Beneficiary: Beneficiary of the payment
• RUT: Tax identification number of the beneficiary of the payment
• Concept: The generic concepts that are associated before printing the check are mentioned below;

2.1.4. Check Form

The form must print for checks: Arial size 10, all fields must be completed in capital letters.

• Year: year in which the check is printed

• Month: month in which the check is printed
• Day: day on which the check is printed

• $: Value payable of the account payable, at the end of the value. The spaces that are left blank according to the dimension
of each space must be completed with asterisks (****)

• Pay to the order: Beneficiary of the payment, the spaces that remain blank according to the size of each space must be
completed with asterisks (****)
 • The sum of: Value in letters of the value of the account payable, the spaces that are left blank according to the size of each
space must be completed with asterisks (****)
• Authorized signatures (s): Signatures of the person who are authorized by the payment area

CLP check format

USD check format

2.1.5. Proof of Expenditure :

Header data of the egress voucher

• Year: year in which the account payable was paid.

• Month: month in which the account payable was paid
• Day: day on which the account payable was paid.
• Voucher: consecutive type of document to be paid
• Beneficiary: Beneficiary of the payment
• RUT: Tax identification number of the beneficiary of the payment
• Concept: It must be the concept of the header text of the account payable.
2.1.6. Egress receipt detail field

• Number: SAP document number of the account payable.

• Invoice: Invoice number or collection account of the beneficiary of the payment: This list of invoice numbers will only be up
to the top of the predesigned format.
• Invoice date: Date on which the account payable was posted.
• Account payable detail: header text of the account payable
• Account: Number of the bank account that was affected.
• Value field: The sum of the values debited from the account payable and the value credited by the bank Mov field: Empty

2.1.7. Disbursement voucher

This voucher must be prepared with design, titles and details, since the pre-printed form is a blank sheet.

2.1.8. Header data of the egress voucher

•Name
•RUT:
•Direction
• Date and time of printing Proof of egress
 • Proof of Exit: Corresponding Consecutive
• Date of proof of discharge
• Payment concept: The same concept of the account payable

2.1.9. Detail data of the egress voucher

• Account: Number of the bank account that was affected.

• Concept: Number of accounts payable that were affected
• Number: SAP internal document number assigned to account payable
• Invoice: Number of the invoice or collection account of the beneficiary of the payment
• Invoice Date: date of posting of the invoice
• Debit Value: Column with debit values
• Credit Value: Column with Credit values
• Totals: sum of the debit and credit columns

2.1.10. Egress voucher footer field

• Prepared: Name of the person who posted to account payable

• Revised: Name of the user applying the payment
• Authorized: Empty • Space to sign the payment
• Tax identification of the beneficiary of the payment

 Attached documents, with the check format in CLP and USD currency



2.1.10.1 Selection screen

N/A
Use the table below to assist in the definition of the selection screen to be created, if any:
Program:
Requires [ ] Which
translation? Yes languages? [ ] Spanish [ ] English [ ]
Portuguese
[ ] No
Seq. Parameter Parameter Reference Type Search Data entry
Name Description (Table/Field) Help validation
[X] Single
[ ] Multiple
[X] Single
[ ] Multiple
2.1.10.2 Selection screen layout
< Mandatory for Reports and ABAP online><Should contain the layout of the input file, if any>
N/A
2.1.10.3 Output layout (Form / Report / File)
<Mandatory for Reports and ABAP online><Should contain the layout of the output, if any>
Same layout as the current one. Only add the new fields

2.1.11. Input / Output Files

< Mandatory for Interfaces>< Should contain the layout of the output file, if any>
N/A
Use the table below to assist in the definition of the layout file to be created:
Field Name Field Description Type Size

2.1.11.1 Interface type

< Mandatory for interfaces><Should define the type of interface to be used, for example: idoc, web service, RFC, etc.>
N/A
2.1.11.2 Source and Destination Systems
< Mandatory for interfaces><Should contain technical details of the source and destination systems>
N/A
2.1.12. Proessing Log
< Mandatory for Background programs><Inform if a Log is necessary and what format it should have>
NA
2.1.13. Access authorization
N/A
<Optional>< Should contain the rules for conceding access to the development >
Authorization type [ ] Autho. Check [ ] User profile [ ] Other
Reference Authorization Object Authorization rule

2.1.14. Error Log

Does not apply. The form is a result of payments made by check for standard transactions.

2.1.15. Processing controls and procedures

Does not apply.

2.1.16. Test requirements

Funcionamiento Normal – Casos de pruebas que busquen que el desarrollo funciono como debe.
ID Descripción
1 Generar impresión de cheques y comprobante de egreso con vía de pago cheque

2 Impresión de otro tipo de formatos, en la vía de pago es cheque

2.1.17. Regression test requirements

< Mandatory >< Should contain the data necessary for executing the unit regression tests >
N/A

No Test Condition Test script and test data Expected Results

01

2.1.18. Parameter table

Check Mapping Information LOGICA – F110 , F-58

Imp
Campo Descripción Funcionalidad Lógica Fuente

REGUH- VBLNR
Serie Cheque numero de numero de buscar en REGUH- VBLNR, numero de documento PAYR-CHECF
cheque documento de pago PAYR-CHECF Buscar l numero de cheque

X
N de Cta Banco Número de Cuenta de Banco REGUH UBKNT
Número de Numero Cta X
Cuenta
Nombre de la buscar en REGUH y T001 el nombre de la empresa REGUH ZBUKR
Nombre Nombre de la
empresa T001- BUTXT
empresa empresa que
X
emite del
Sociedad
Comprobante
Valor
Valor a pagar
Total a pagar   Importe pagado X
REGUH - RWBTR

Ciudad REGUH ORT01

Cuidad X
Fecha cheque Fecha de emisión del documento REGUH BUDAT
Fecha Doc. X
Nombre Nombre del Beneficiario REGUH - NAME1
Beneficiario X
Beneficiario
Monto en F
Monto X
Palabras Valor a pagar unción monto (Letras) adjunto abajo REGUH RBETR
A la siguiente función vamos a poder pasarle en una variable un monto (importe) y la misma nos devolverá en una estructura

el importe escrito en letras (el monto en texto)

DATA: IMPORTE_LETRAS TYPE SPELL.

CALL FUNCTION ‘SPELL_AMOUNT’

     EXPORTING
        AMOUNT = VG_MONTO    “importe
        CURRENCY = ‘USD’           “moneda
        LANGUAGE = SY-LANGU   “idioma en que devuelve el texto
     IMPORTING
        IN_WORDS = IMPORTE_LETRAS
     EXCEPTIONS
        NOT_FOUND = 1
        TOO_LARGE = 2
        OTHERS = 3.

* IMPORTE_LETRAS-WORD = tendrá el texto de la parte entera

* IMPORTE_LETRAS-IN_WORDS = tendrá el texto de la parte decimal.

Document de Egress

Impri
Campo Descripción Funcionalidad Lógica Fuente
mir en
pantall
a
Beneficiario Beneficiario del Nombre del Beneficiario X REGUH - NAME1
Cheque
Dirección Dirección de X REGUH - STRAS
beneficiario
Ciudad Ciudad X REGUH - ZREGI

Rut Cedula de X REGUH - ZSTC1

Identificación
Comuna Comuna X REGUH - ORT01

Fecha Fecha del Cheque Fecha del Docuemento X REGUH - LAUFD

Voucher Nro de comprobante Numero de Docuemento X REGUP -VBLNR

Numero Nro de factura o NC Numero de Factura o NC X REGUP -XBLNR

Descriocion Descripcion (Glosa) la descripcion es la Glosa que le das X REGUP -SGTXT

al ingresar un compromiso de pago

Monto Bruto Monto Bruto Sumar el campo REGUP-WRBTR X REGUP-WRBTR

cuando fecha ejecución REGUP-
 LAUFD e identificador REGUP-
LAUFI y REGUP-LIFNR sea el 
mismo y que el campo REGUP-
XVORL este marcado con X. y el
campo documento de pago
REGUP- VBLNR está lleno.
Dscrto/Retencion (Monto Nota de Sumar todo los -REGUP PSWBT que X REGUP PSWBT
Credito) contengan el campo campo REGUP
XREBZ.
Monto total Monto total de la Importe pagado Importe pagado X REGUH - RWBTR
linea
Fecha cheque Fecha del Documento X REGUP BLDAT

Recibi conforme Linea de firma X Linea

Finanzas Linea de firma X Linea

Autorizante Linea de firma X Linea

Auxiliar Linea de firma X Linea

Descripción de cómo se deben obtener los datos formulario cheques

La información generada por los pagos realizado por vía de pago cheque del banco que se realicen mediante la transacción estándar F110 para pagos
automáticos , serán los que generen el formulario.

En la siguiente pantalla de la transacción F110, elija el botón “entradas formula” e ingrese el nombre del formulario que se desea asignar en campo formulario
para medio de pago

Ejemplo Funcional Pago F110

Factura

NC

F110
Para pagos manuales se debe utilizar la transacción estándar FBZ5 e indicar el formulario
Ejemplo f-58

En el campo Formulario alternativo, se utilizara el formulario entregado para el ABAP, para F-58
OPAYF-PZFOR
2.1.19. Reference documents and additional information
<Optional>Should contain identification of any such information related to the customization.
N/A
Page 17 of 17