FUNCTIONAL SPECIFICATION DOCUMENT

1867 Configuracíon de “layout” de cheques.

Formulario de cheque en SAP. Citibank.

_______________________________________
DOCUMENT ORIGIN

PROJECT / CHANGE ANDES PROJECT

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

DOCUMENT FORMULARIO DE CHEQUE EN SAP. CITIBANK.
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

Page 2 of 15
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

Page 3 of 15
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

Page 4 of 15
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.

Page 5 of 15
 • 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 with two decimal places. 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): Digitized signatures of the people who are registered in the banking
entities to compensate.

CLP check format

USD check format

2.1.5. Proof of Expenditure :

Header data of the egress voucher

Page 6 of 15
 • 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

Page 7 of 15
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

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

Page 8 of 15
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

Page 9 of 15
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>
N/A

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

Page 10 of 15
2.1.18. Parameter table

Check Mapping Information

Imprimir en
Campo Descripción Funcionalidad Lógica Fuente Formato Ventana
pantalla
Pago diferente al
Pagador LFZA-
Pagado A acreedor de cuenta por X
Alternativo EMPFK
pagar
Acreedor que tiene la LFA1-
Pagado A Acreedor X
cuenta por pagar LIFNR
Fecha en que se genera BKPF-
Año Año X
el pago BUDAT
Fecha en que se genera BKPF-
Mes Mes X
el pago BUDAT
Fecha en que se genera BKPF-
Día Día X
el pago BUDAT
Valor de la cuenta por BSEG-
$ Valor X
pagar WRBTR
La suma Valor de la cuenta por
Valor X
de pagar en letras

Imprimir en
Campo Descripción Funcionalidad Lógica Fuente Formato Ventana
pantalla
Nombre
de la
empresa Nombre de la empresa
BSEG-
que Sociedad Fundación Salud X
BUKRS
emite del Bosque
Comprob
ante
Identifica
ción
Tributaria
de la RUT de la
Identificación
empresa empresa X 830.138.802-5
Sociedad
que Fundación Salud
emite del Bosque
Comprob
ante
Dirección
de la
empresa Dirección de la
Dirección de
que empresa Fundación X CLLA 134 7B 41
Sociedad
emite del Salud Bosque
Comprob
ante
Fecha en que se genera BKPF-
Año Año X
el pago BUDAT
Fecha en que se genera BKPF-
Mes Mes X
el pago BUDAT
Fecha en que se genera BKPF-
Día Día X
el pago BUDAT

Page 11 of 15
 Hora de impresión del
Hora Hora X
comprobante
Número clase de Número interno
Comprob RF05L-
documento para documento de pago X
ante XTEXT
pagos SAP SAP
Beneficia LFA1-
Acreedor Beneficiario del pago X
rio LIFNR

Identifica
ción Identificación tributaria LFA1-
RUT Acreedor X
Beneficia del Beneficiario STCD1
rio
Texto de la cuenta por BKPF-
Concepto Texto Cabecera X
pagar BKTXT
Número
de
Número de Número interno
documen
documento en generado por SAP para BKPF-
to en SAP X
SAP de la cuenta el documento contable BELNR
de la
por pagar de la cuenta por pagar
cuenta
por pagar
Número Número de factura del BKPF-
Referencia X
Factura proveedor/acreedor XBLNR
Fecha
Fecha Fecha de
contabiliz BKPF-
contabilización contabilización de la X
ación BUDAT
Factura factura por pagar
Factura
Cuenta Cuenta Bancaria que se BSEG-
Cuenta Contable X
Bancaria afecto HKONT
Texto Texto de
Texto de cabecera BKPF-
cuenta Cabecera de la X
cuenta por pgar BKTXT
por pagar cuenta por pagar
Valor por factura BSEG-
Valor Valor X
cancelado WRBTR
Nombre Usuario que
Preparad BKPF-
Preparado contabilizo la cuenta X
o USNAM
por pagar
Nombre del usuario
que realizo la BKPF-
Revisado Revisado X
contabilización del USNAM
pago
Firma y
Linea para que
sello Campo firma
Firma del beneficiario X el beneficiario
Beneficia Acreedor
firme
rio
Número
Campo para
identifica
relacionar Rut
ción del X RUT
o Cédula
beneficia
manualmente
rio pago

Page 12 of 15
2.2. Origen de la información

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

FBZP

Page 13 of 15
Para pagos manuales se debe utilizar la transacción estándar, F-58.

Para la imprepsion del cheque, utilizar la transacción FBZ5 e indicar el formulario

Page 14 of 15
2.2.1. Reference documents and additional information
<Optional>Should contain identification of any such information related to the customization.
N/A

Page 15 of 15