Remittance Advice

Development Specification

Development ID GDEVWR0003933

Brief development description Remittance Advice NPP UK – Form Layout

Gap ID FITGAP0011803

Business Process Level 3 or 4Level 4 Execute Payment Run and Create Payment File

Functional Owner Janet Ure

Technical Owner Lisa Howdle

Author Sean McCarthy

Reference Documents Appendix Z

Workstream GLOBE Template

Process Stream Finance && Control

mySAP component /module R3

Type of development User Exit or Enhancement

Template Version 1.5

Global / Market UK

Status Work in Progress

document.doc

GCC Application Development

Page 1 of 35 Created: 20.04.200404.09.2003

Printed: 08.04.2004 17:00

Version Control<Template instructions in red, please delete>Provide details of all updates made. After sign-off, every change must have a CHR/TPR number.

Revision History:Section Reference

Version No.

Description of change (including the reason for the change)

Reference Change Request

Changed By

Date

FS 1.0 Initial draft JU 25/61.1 QA review LH 01/08/031.2 Updates for foreign currency SM 11/09/031.3 Second review LH 12/09/031.4 Signed Off JU 23/10/031.5 Change request LW 08/04/04

TS 1.0 Tech section added LH 22/10/031.11.21.3

UTP 1.01.11.21.3

FS – Functional SpecificationTS – Technical SpecificationUTP – Unit Test Plan

Sign-off<Please delete where appropriate>Approved by Name Signature DateCustom Development Team Lead (Interfaces only)(TO)Process Team Lead (FO)Complimentary Application Team LeadAD Development Coordinator (2 names: On+Off-Site)Developer (FO)QA Reviewer (TO)CD-Middleware (MW)ALE Configuration TeamApproved by (Applicable for Messaging Only)Cross Application Team Lead (TOM)Custom Development Team Lead (where development required)(TO)Messaging Configurer (TOM)QA Reviewer (TOM/TOD)

IMPORTANT: All paragraphs titles have been marked with a 'code', defining which stakeholder is responsible for completing the paragraph. Please find below explanation of the codes, as well as their roles in the process flow

FO Functional Owner

TO Technical Owner – AD Development Coordinator (On-site and Off-Site)

QA QA reviewer (for messaging: both Messaging and AD)

DEV Developer

MWTO Middleware Technical Owner

MWQA Middleware QA Reviewer

MWDEV Middleware Developer

TOM Technical Owner Messaging – Messaging Coordinator

TOD Technical Owner Development – AD Development Coordinator

Complete Functional

Sections

Initial Walkthrough +

QAFS Workshop

FS Final QA + Sign-Off

CompleteTechnival Sections

TS QA

FO TO FO + TO TO TO QA + MWQA

Complete Functional

Sections

Initial Walkthrough +

QAFS Workshop

FS Final QA + Sign-Off

CompleteTechnival Sections

TS QA

FO TO FO + TO TO TO QA + MWQA

For Messaging Only:

An assigned TOM and TOD are working very closely for the entire development lifecycle. For sections where TO is responsible to complete, the responsibility in general will fall with the TOM being responsible for the overall technical solution. TOD is responsible in documenting any coding logic

Table of contents

1 Management Summary (FO)...........................................................................6

2 Process Flow / Context (FO)........................................................................7

3 Functional Requirements (FO).....................................................................83.1 DESCRIPTION OF THE DEVELOPMENT (FO)..........................................................................8

3.2 HOW THE DEVELOPMENT WILL WORK (FO)..........................................................................8

3.3 SAP GENERAL REQUIREMENTS (FO)..................................................................................9

3.4 ASSUMPTIONS/DEPENDENCIES/CONSTRAINTS (FO)...........................................................10

3.5 QUALITY ASSURANCE REMARKS/SIGN-OFF OF SECTION (TO)............................................11

4 Overall Development Design (TO).............................................................124.1 COMPLEXITY, ESTIMATES AND DEADLINES........................................................................12

4.2 BRIEF TECHNICAL OVERVIEW...........................................................................................12

5 Appendix B: SapScript/Forms...................................................................135.1 FORM DETAILED DESCRIPTION (FO).................................................................................13

5.2 EXISTING SAP LAYOUT SET (FO).....................................................................................13

5.3 NEW REQUIREMENTS (FO)...............................................................................................14

5.4 FORM LAYOUT (FO)........................................................................................................14

5.5 DATA MAPPING MATRIX (FO + TO).................................................................................17

5.6 STANDARD TEXTS (IF SAPSCRIPT) (FO + TO).................................................................24

5.7 TEXT MODULES (IF SMARTFORMS) (FO + TO)..................................................................24

5.8 LAYOUT DETAIL (FO)......................................................................................................24

5.9 TECHNICAL DETAILS FOR DEVELOPING THE FORM (TO)....................................................24

5.10 SMARTFORMS TECHNICAL GLOBAL SETTINGS (TO)............................................................25

5.11 STYLES (TO)................................................................................................................... 25

5.12 QUALITY ASSURANCE REMARKS/SIGN-OFF OF SECTION (TO + QA)..................................27

6 Appendix M: Security (TO).........................................................................28

7 Appendix N: Testing...................................................................................297.1 FUNCTIONAL TEST CASES (FO)........................................................................................29

7.2 TECHNICAL TEST CASES (TO)..........................................................................................30

8 Appendix Z: Reference Documentation....................................................338.1 SAMPLE SAP Data Relationship Diagram....................................................................33

1 Management Summary (FO)

Once an AP payment run has been made and the ledgers updated, a print run is scheduled to create the BACS (UK) file for the bank, the vendor payment advices and the necessary reports.

For Foreign and Domestic Transfers, only reports and payment advices are created. There is no file.

For Netting payments, a file is created for the Nestle Netting system together with reports and payment advices.

The Remittance Form to be used for the vendor payment advices is set in configuration for each Paying Company Code and Payment Method. An alternative payment advice form can be specified in the program variant used to set the print parameters for individual payment runs. This will then take precedence over the form set in configuration for that run.

SAP provides a standard international sapscript form F110_IN_AVIS and specific forms for some named countries. There is no specific form for the UK or Ireland but the standard form does not meet market requirements and needs to be customised.

Different texts are required on the Advices according to the Company Code and Payment Method used for the payment run.

The Remittance form will have headed information with the logo and the address of the company. The e- sent as a PDF file to the vendor e-mail address.The facility should exist to print the form if e-mail does not work

2 Process Flow / Context (FO)

Amendment made to diagram

3 Functional Requirements (FO)

3.1 Description of the development (FO)

3.1.1 Overview of development (FO)

A payment proposal is created to select invoices for payment, grouped by vendor. This is approved and a payment run is made to post payments to the ledgers. The print run is then scheduled. For the BACS or EMTS run, using Program RFFOGB_T, this creates:

a) BACS or EMTS File for transmission to bankb) Reports c) Vendor Payment Advices

For Foreign and Domestic Transfers, using Program RFFOD__V, only Reports and Payment Advices are produced. There is no file.

For the netting run, using Program RFFOM100, the following are created:

a) Netting file for upload to Nestle Netting Systemb) Reports c) Vendor Payment Advices

A single file per run containing multiple advices is created in the user’s output spooler. Advices are then printed out onto the appropriate headed notepaper for the Company Code, folded into window envelopes and posted to the vendors. It is believed that the technical development will be such that an individual spool request will be created for each vendor and that this in turn will trigger an e-mail of the remittance form to be sent to the vendor e-mail address.

Different texts are required on the Advices according to the Company Code and Payment Method used for the payment run.

At the top of the form the company name, address and logo will appear

16 documents to be listed per page followed by carry forward to next sheet.

3.2 How the development will work (FO)

3.2.1 Where this development will be run (FO)

Geographically Global Development, will be run in all markets Local Development, will be run in the following market(s): UK Purina

Environments – Components MDR HR R/3 Core

Financial System (Distributed Architecture only) Commercial System (Distributed Architecture only) Manufacturing System (Distributed Architecture only) SEM (Distributed Architecture only) Global ATP (Distributed Architecture only) Restitution System (Distributed Architecture only)

CRM

APO DP (Distributed Architecture only) PPDS/SNP (Distributed Architecture only)

R&D EBP WPS Other: Please specify

3.2.2 How the development will be run (FO)

Development will be run in the following ways On-line by end user - From within SAP transaction (s): F110 - Payments (Schedule Print) On-line - Via a development-specific menu path . Please specify the applicable end user roles (e.g. CS-0057

Order Entry Clerk) In background - Scheduled at regular intervals/time: Please specify frequency (e.g. Midnight on workdays) In background - Triggered by a certain event: Please specify event. (e.g. Release of Purchase Order) Other: Please specify (e.g. this transaction is only run in the development environment)

Comments – Specific Variations

3.2.3 Security (FO)

How should access to run the development be restricted. No specific restrictions Restriction on authorization on development-specific transaction code only Restrictions based on certain criteria. Access also based on Company Code Other: Please specify

Comments:

Security will be set for the standard transaction F110 and no new security should be required for this form.

3.3 SAP General Requirements (FO)

3.3.1 Data Volumes (FO)

Country/Market Frequency Volume per runUK Daily One spool of up to 1500 Payment Advices per runMallow Payments 2 runs per month 60 per monthIreland Payments Once weekly 100 per weekComments:

3.3.2 Language considerations (FO)

Language considerations No language considerations Master Data – Related considerations: Please specify (e.g. Material texts in report need to be displayed in user

logon language)Translation requirements

No translation requirements – Development will be used in English only Translation required:

Comments

3.3.3 Currency and Units of Measure (FO)

Payments for which Remittances will be produced will be in GBP, Euros, Swiss Francs or US Dollars. The Local Currency for GB Company Codes is GBP and for IE Company Codes it is EUR.

For GB Company Codes, the local currency will change if the Euro is adopted as the UK currency in the future.

For foreign currency payments the currency could vary.

3.4 Assumptions/Dependencies/Constraints (FO)

– The logon language will be English

– The Remittances will be created by SAP Standard Programs RFFOGB_T, RFFOD__V, and RFFOM100 and the advice name will be configured as a form for use with the Program and payment method or set up as an alternative form in the program variant.

– One Spool containing all Remittance Advices is created from each run (up to 1500 documents).

– An separate spool request will be sent for each individual vendor which will then generate an e-mail to each vendor.

– Invoice values can be up to 12 characters long.

– One payment run can include different currencies, one currency per remittance.

– All invoices to be paid in foreign currency will have payment method N or T in the document or in the vendor master record

– Printed on headed notepaper for each company code. This will be available for development and testing.

– SAP standard form copied and renamed according to GLOBE naming conventions.

– Payment Runs for the UK and Ireland Company Codes will be separate.

– Ireland remittance advice documents will be e-mailed – In the legacy system the print program RFFOGB_T has been changed for Nestlé UK so that in can be

run for foreign transfers (T) with no file being produced. This will not be required in GLOBE as program RFFOD__V will be used instead.

3.5 Quality Assurance Remarks/Sign-Off of Section (TO)

QA Reviewer Lisa HowdleQA Date 01/08/2003

Subject Yes No N/A Comments

General InformationDevelopment ID is correctReference documents providedMarket has been clearly specifiedDocument contents'Management Summary' complete and clearProcess Flow / Context complete and clearDescription of development complete and clear'How the development will work' complete Data volumes have been providedCurrency and UoM details have been specifiedLanguage requirements have been specifiedSecurity requirements have been specified All assumptions have been documentedSecurity Spreadsheet has been completed Input required from securities teamAll Test Cases have been described in Appendix N

Overall: Functional Section Approved

Comments

4 Overall Development Design (TO)

4.1 Complexity, Estimates and Deadlines

Complexity MediumEstimate 4 daysExpected Delivery Date

4.2 Brief Technical Overview

One layout set will be required for both UK and Ireland. The layout is very similar, only the addresses are different, which should be managed using the company code and standard texts.

The full layout and details of the data elements required are listed in section 5 below. No new fields are required to be selected and the SAP standard print program can be used.

There is a different page layout required if the remittance advice goes over more than one page. Asummary report should be printed after all remittance advice documents have been output to act as an audit trail for the total number and value of the remittances from the payment run.


5 Appendix B: SapScript/Forms

5.1 Form Detailed Description (FO)

The Remittance Advice lists payment advices for a vendor. It is made up of the following windows:Header – reserved space to allow for headed notepaper.Page – page number.Address – address of vendor.Info – shows date, account number of vendor and payment number.Main – lists payment advices. Also includes bank, account number and sort code details.Carryfwd – total for page carried forward to next page.Total – final total for all payment advices listed.Summary – shows the number of payment advices output and the total net amount. This is needed to be

printed as an audit trail of a summary of the total remittances that were e-mailed.

The total field (REGUD-SWNET) is determined as follows: if there is only one page of details, the total at the bottom will be the Net total, with the Total window being displayed. If there is more than one detail page, the Carryfwd window will be displayed instead, showing the total amount listed up to that point; a brought forward total will then be included in the Main window of the following page. The Total window will be displayed on the last detail page.

The first detail page will include the Header, Page, Address, Info and Main windows, together with either the Carryfwd or Total window. Any continuation pages will show only the Header, Page, Main and Carryfwd windows, with the latter replaced by the Total window on the last detail page. On these the Main window will be extended in length.

A summary page will be printed at the end of the report. This will include only the Summary window. This is required as a reconciliation for the total amount that has been processed and to reconcile to the BACS amount.

5.2 Existing SAP Layout set (FO)

Output type Remittance AdviceProgram Name SAPF110V (Print programs RFFOGB_T and RFFOD__V )Layout Form Name Z110_GB_ADVICE_2; Z110_GB_ADVICE_F; Z110_IE_ADVICE_FIMG path to access output type and layout set assignment

Path to assign layout set

Type of solution (Standard R/3, custom ABAP)

Standard R/3, SapScript

Owner of existing solution SAP

5.2.1 Printing Existing Solution (FO)

Menu Path for transaction: Accounting, Financial Accounting, Accounts Payable, Periodic Processing, Payments

Values to be used and output type: 1) BACS or EMTS payments Parameter Tab: Company Code NPPUK (UK) Payment Method ‘1’

Printout/data medium tab: Program RFFOGB_T with appropriate variant entered alongside

Form: Z110_GB_ADVICE_2

document.doc Page 13 of 35


2) Foreign Transfers (UK) Parameter Tab: Company Code NPPUK Payment Method ‘3’ Printout/data medium tab: Program RFFOGB_T with appropriate variant entered alongside (Program RFFOD__V will be used in GLOBE)

Form: Z110_GB_ADVICE_F

3

Printout/data medium tab: Program RFFOD__V with appropriate variant entered alongside

Form: Z110_IE_ADVICE_F

Printout/data medium tab: Program RFFOD__V with appropriate variant entered alongside (Program RFFOM100 will be used in GLOBE)

Form: Z110_IE_ADVICE_F

Actions to be taken: Return to the Status tab and press Printout

5.3 New requirements (FO)

Output type(s): Remittance AdviceForm Types: Remittance Advice NPP UK Transmission medium: E-mail PDF format Legal requirements:Type of printer: PostScriptPaper Size: A4Orientation: Portrait/Landscape: PortraitSpecial stationery to be used :

5.4 Form Layout (FO)

The changes are required in the header information on all of the layouts Company name Company address Company Telephone number Company Fax number Nestle Purina Logo

Single page layout GB_ADVICE_2_layout1 GB_ADVICE_F_layout1



Multiple page layout GB_ADVICE_2_layout2 GB_ADVICE_F_layout2

Single page layout

Multiple page layout

Summary page layout (all forms)

5.4.1 Page break requirement

Page break at natural page break.



5.5 Data Mapping Matrix (FO + TO)

Label R/3 Field Functionality Calculation Logic Print-on-Page Label Position Font Output Format Font Format

Table:Screen:

Note A Note B Note C Note D Note F Note E

A1 V_T001-BUTXT Standard Text If NestléPurina UK Company then UK address.

all pages 0 Arial 14

A2 ADDR1_DATA-NAME1

Standard Address format (do not include country)

If Nestlé Purina UK Company then UK address.

all pages 0 Arial 8 CAPS

A3 Text Telephone All pages 0 Arial 8 CAPS

SZA1_D0100-TEL_NUMBER

Include area codeStandard text

Telephone no All pages 0 Arial 8 CAPS

A4 Text Fax no All pages 0 Arial 8 CAPS

SZA1_D0100-FAX_NUMBER

Standard text Fax no All pages 0 Arial 8 CAPS

A5 Standard text Nestlé Purina logoZ_PURINA_LOGO

All pages mid way Left aligned

Nestlé logo including bird’s nest

35

A6 Text Remittance advice All pages mid way Left aligned

Arial 12 Bold

1 Text Page All pages except last

Courier 12 Bold

2 Page No All pages except last

Courier 12

3 Address fields from REGUH

All address fields in country format

1st page 5 characters from left, 9 lines from

Courier 12

document.doc Page 17 of 35 Created: 20.04.200404.09.2003

Printed: 08.04.2004 17:00


top (to align with envelope window)

4 Text Date 1st page Courier 12 Bold

5 REGUH-ZALDT 1st page Courier DD.MM.YYYY 12

6 Text Your Account No. 1st page Courier 12 Bold

7 REGUH-LIFNR 1st page Courier 12

8 Text Payment No. 1st page Courier 12 Bold

9 REGUH-VBLNR 1st page Courier 12

10 Standard Text Text for BACS payment

1st page (see below)

Courier 12

11 Text Bank: 1st page and summary

Courier 12

12 REGUD-ZBNKA 1st page Courier 12

13 Text Account No: 1st page Courier 12

14 REGUH-ZBNKN 1st page Courier 12

15 Text Sort Code: 1st page Courier 12

16 REGUH-ZBNKL 1st page Courier 12

17 Standard Text Text for alternative payee (see below)

1st page Courier 12

18 Address fields for See below 1st page Courier 12


Printed: 08.04.2004 17:00


alternative payee from REGUH

19 Underline All pages except summary

Courier Length 78 12

20 Text Document Number All pages except summary

Courier 12 Bold

21 Text Invoice Number All pages except summary

Courier 12 Bold

22 Text Invoice Date All pages except summary

Courier 12 Bold

23 Text Discount All pages except summary

Courier 12 Bold

24 Text Net Amount All pages except summary

Courier 12 Bold

25 REGUP-BELNR All pages except summary

Should appear under label 20

Courier 12

26 REGUP-XBLNR All pages except summary


Courier Right justified 12

27 REGUP-BLDAT All pages except summary


Courier XX.XX.XXRight justified

12

28 REGUD-WSKTO All pages except summary



29 REGUD-WNETT All pages except summary



30 Standard Text ZFGBFC_NPP_ADVICE_TEXT1

Last detail page Courier 12 Bold

31 Standard Text Z110_GB_ADVICE_TEXT2

Last detail page Courier 12

32 Text Net Total Last detail page Courier 12 Bold


Printed: 08.04.2004 17:00


33 Text £ Last detail page Courier 12 Bold

34 L_TOTAL All pages except summary


Courier Right justified 12 Bold

35 Standard Text Text for foreign currency payment (see below)

1st page Courier 12

36 Text National Code: 1st page Courier 12

37 REGUH-STRAS 1st page Courier 12

38 REGUH-ORT01 1st page Courier 12

39 Text Swift Code: 1st page Courier 12

40 REGUH-ZSWIF 1st page Courier 12

41 REGUH-PSTLZ 1st page Courier 12

42 REGUD-WAERS All pages (see below)

Courier 12

43 Text ( All pages except summary

Courier 12

44 Text ) All pages except summary

Courier 12

45 Standard Text Text for EFT payment

1st page (see below)

Courier 12

46 REGUD-SWNET All pages except summary


Courier Right justified 12 Bold

47 Text Carryfwd: All detail pages except last

Courier 12 Bold


Printed: 08.04.2004 17:00


48 Text Broughtfwd: All detail pages except first

Courier 12 Bold

49 REGUH-HBKID Summary page Courier 12

50 Text Report summary Summary page Courier 12

51 T042Z-TEXT1 Summary page Courier 12

52 Text Company code: Summary page Courier 12

53 REGUH-ZBUKR Summary page Courier 12

54 Text Payment method Summary page Courier 12

55 REGUH-RZAWE Summary page Courier 12

56 Underline Summary page Courier Length 55 12

57 Text Number of Pmnt advices printed

Summary page Courier 12

58 REGUD-AVISE Summary page Courier 12

59 Text Total net amount in Summary page Courier 12

60 REGUD-HWAER/ REGUP-WAERS (see below)

Summary page Courier 12

61 REGUD-SUMME Summary page Courier 12

Notes:


Printed: 08.04.2004 17:00


1. Label 10 text will read “This is a BACS payment to be made direct to your nominated bank account.”2. Labels 17 and 18 will only be displayed if the Alternative Payee Indicator (REGUD-XABWZ) is ‘X’. Text for label 17 is ‘The items listed below are managed on the

following account:’. The address will be displayed as follows: REGUH-NAME1 REGUH-NAME2REGUH-STRAS REGUH-ORT01

3. Label 30: Z110_GB_ADVICE_TEXT1 reads as follows:“This is a combined payment for all Nestlé Purina UK locations, with a detailed breakdown of this payment provided. In the event of a query please contact the Shared Service Centre on Tel: 00800 6355 6355, Fax: +44 (0) 208 715 1450, or E-mail [email protected].”Label 31: Z110_GB_ADVICE_TEXT2 reads as follows:“Business should only be transacted if you are in receipt of a valid Purchase Order. Failure to quote a purchase order will result in a delay in payment.”

4. Label 35 text will read “This payment will be made directly into your nominated bank account.”5. Label 45 text will read “This is an EFT payment to be made direct to your nominated bank account.”6. Label 60 will show REGUD-HWAER for Z110_GB_ADVICE_2, and REGUP-WAERS for Z110_GB_ADVICE_F.

5.6 Standard Texts (if SAPscript) (FO + TO)

N/A

Description of use Text Name Text ID Error CasePurina Logo from bitmap Z_PURINA_LOGO ST

ZFGBFC_GB_ADVICE_TEXT_2 ZEFCZFGBFC_GB_ADVICE_TEXT_3 ZEFC

This is a combined payment for all Nestlé Purina UK locations, with a detailed breakdown of this payment provided. In the event of a query please contact the Shared Service Centre on Tel: 00800 6355 6355, Fax: +44 (0) 208 715 1450, or E-mail [email protected].”

ZFGBFC_NPP_ADVICE_TEXT1 ZEFC

Business should only be transacted if you are in receipt of a valid Purchase Order. Failure to quote a purchase order will result in a delay in payment.

ZFGBFC_GB_ADVICE_TEXT2 ZEFC

Broughtfwd: ZFGBFC_BROUGHTFWD ZEFC


Printed: 08.04.2004 17:00


Carryfwd: ZFGBFC_CARRYFWD ZEFCDate ZFGBFC_DATE ZEFCYour Account No ZFGBFC_ACC_NO ZEFCPayment No ZFGBFC_PAY_NO ZEFCPage ZFGBFC_PAGE ZEFCNet Total ZFGBFC_NET_TOTAL ZEFCReport Summary ZFGBFC_SUM_REP ZEFCBank ZFGBFC_BANK ZEFCCompany Code ZFGBFC_SUM_CCODE ZEFCPayment method ZFGBFC_SUM_PMETHOD ZEFCNumber of pmnt advices printed ZFGBFC_SUM_ADV_PTD ZEFCTotal net amount in ZFGBFC_SUM_TOT_NET ZEFCThe items listed below are managed on the following account

ZFGBFC_GB_ADVICE_LABEL17 ZEFC

This payment will be made directly into your nominated bank account

ZFGBFC_GB_ADVICE_LABEL35 ZEFC

Document ZFGBFC_DOC ZEFCNumber ZFGBFC_DNO ZEFCInvoice Number ZFGBFC_INVOICE_NO ZEFCInvoice ZFGBFC_INV ZEFCDate ZFGBFC_DATE_11 ZEFCDiscount ZFGBFC_DISCOUNT ZEFCNet Amount ZFGBFC_NET_AMT ZEFC


Printed: 08.04.2004 17:00


5.7 Text Modules (if Smartforms) (FO + TO)

N/A

5.8 Layout Detail (FO)

Position of Left Margin (Specify Unit)

See Appendix Z

Position of Right Margin(Specify Unit)

See Appendix Z

Position of Nestle Logo(Specify Unit)

Contained within pre-printed stationery

Position of Main Window(Specify Unit)

See Appendix Z

5.9 Technical Details for Developing the Form (TO)

5.9.1 SAPscript or Smartforms ? (TO)

Use the same SapScript as used for GDEVWR0002161: /EUR/FGB_F110_AD or create a new one: /EUR/FGB_F110_PUThe layout is designed using SAP Script.

5.9.2 SAP Data Relationship Diagram (TO)

<Template instructions in red, please delete>The purpose of the diagram is to show the database tables used in the development and the relevant data for the report and the relationships between them.


Printed: 08.04.2004 17:00


Refer to Appendix Z on a sample SAP Data relationship Diagram that should be included this section.

5.9.3 Data Processing (TO)

<Template instructions in red, please delete>This section should be used to give a detailed processing and logic description.

5.10 Smartforms Technical Global settings (TO)

5.10.1 Form Attributes (TO)

<Template instructions in red, please delete>Please describe here the general attributes (Development class, language, translation) and the output options ( Page format (e.g. DINA4), characters per inch (e.g. 10,00), lines per each (e.g. 6,00), Style (e.g. ZRCH0003), etc

5.10.2 Form Interface (TO)

<Template instructions in red, please delete>Please briefly describe here the Import, Export, Tables and Exceptions sections of the function module that will be generated by Smartforms.

5.10.3 Global Definitions (TO)

<Template instructions in red, please delete>Please briefly describe here the Global data, Types, Field Symbols, Initialization and Form routines sections.


Printed: 08.04.2004 17:00


5.11 Styles (TO)

<Template instructions in red, please delete>Please describe here the Style(s) that need to be created and attached to the development transport request with the SAPscript or the Smartforms. We have two possibilities :

- Styles can be created and maintained via transaction code SE76. They contain the Paragraph and Character formats. They are assigned to Standard Texts.

- Styles can be created and maintained via transaction code SMARTFORMS. They contain the Paragraph and Character formats. They are assigned to Text modules.

Style name Style description Standard settings

Paragraph format Character format

Note A Note B Note C Note D Note E

Note A: e.g. /EUR/RCH_EXP_INV_ST01Note B: e.g. Default styleNote C: Indicate the Standard paragraph, the Characters per Inch (e.g. 10,00), the Tab stop (e.g. 1,00 CM), the Lines par Inch (e.g. 6,00) , the Font (Family, size and style), if underlined and/or color. Note D: e.g. P1 (to be detailed in the following table)Note E: e.g. C2 (to be detailed in the following table)

Paragraph Format

Description Indents and spacing

Font Tabs Numbering and outline

Note A Note B Note C Note D Note E Note F

Note A: e.g. P1Note B: e.g. Left margin 0.5 with tabs Note C: If needed, specify the alignment (e.g. Left-aligned), the indents (left and right margin), the spacing (space before, space after, line spacing), the text flow (page protection, next paragraph same page).Note D: Font family (e.g. HELVE), font size (e.g. 8pt), font style (e.g. Bold) , underline, color. Note E: If needed, indicate the tabs with number, position number, unit and alignment (Centered, Left or right or decimal point aligned, …).Note F: If relevant, indicate the top outline paragraph, the numbering type and numerator.


Printed: 08.04.2004 17:00


Character format

Description Standard settings Font

Note A Note B Note C Note D

Note A: e.g. C2Note B: e.g. Bold size 8 Note C: If needed, indicate the effects (Superscript, Subscript) the barcode (width and height). Note D: Font family (e.g. HELVE), font size (e.g. 8pt), font style (e.g. Bold) , underline, color.


Printed: 08.04.2004 17:00


5.12Quality Assurance Remarks/Sign-Off of Section (TO + QA)

QA Reviewer Lisa HowdleQA Date 01/08/2003

Subject Yes No N/A Comments

Functional Section Form description complete and clearExisting solution specifiedForm layout specifiedData mapping providedStandard texts provided Use existing GLOBE standard texts where possibleUser interaction requirements specifiedError handling specified

Technical DetailsSAP Date Relationship has been providedData processing steps complete and clear

Comments


Printed: 08.04.2004 17:00



Printed: 08.04.2004 17:00


6 Appendix M: Security (TO)

<Template instructions in red, please delete>This section should contain the technical details about the security objects requested in the functional specification.

The downloading of payment media and creation of Payment Advices is a Treasury Back Office function.

document.doc


Page 30 of 35 Created: 20.04.200404.09.2003

Printed: 08.04.2004 17:00


7 Appendix N: Testing

7.1 Functional Test Cases (FO)

Test Case Test Case Description Expected Result CD Comments1 BACS AP – create AP payment run for a GB

Company Code using F110 and payment method ‘E’. Progress to create payment media using program RFFOGB_T. Do not select the Print Immediately option in the program variant

One spool of multiple vendor payment advices is created in the user’s output spooler

2 Print spool created in Test 1 onto Nestlé UK Ltd headed notepaper

Text is correct for Company Code, Currency and BACS payment and fits headed paper and window envelope when folded

3 EMTS AP – create AP payment run for an IE Company Code using F110 and payment method ‘E’. Progress to create payment media using program RFFOGB_T. Do not select the Print Immediately option in the program variant

One spool of multiple vendor payment advices is created in the user’s output spooler

4 Print spool created in Test 3 onto Nestlé Ireland headed notepaper

Text is correct for Company Code, Currency and EMTS payment and fits headed paper and window envelope when folded

5 Foreign Currency Advices with no payment media – create AP payment run for foreign currency payments for a GB Company Code using F110 and payment method ‘T’. Progress to schedule print using program RFFOD__V. Do not select the Print Immediately option in the program variant

One spool of vendor payment advices is created in the user’s output spooler

6 Print spool created in Test 5 onto Nestlé UK headed notepaper

Text is correct for Company Code, Currency and Foreign Transfer payment and fits headed paper and window envelope when folded

7 Foreign Currency Advices with no payment media – create AP payment run for foreign currency payments for an IE Company Code


document.doc


Page 31 of 35 Created: 20.04.200404.09.2003

Printed: 08.04.2004 17:00


using F110 and payment method ‘T’. Progress to schedule print using program RFFOD__V. Do not select the Print Immediately option in the program variant

8 Print spool created in Test & onto Nestlé Ireland headed notepaper

Text is correct for Company Code, Currency and Foreign Transfer payment and fits headed notepaper and window envelope when folded

9 Netting Advices – create AP payment run for a GB Company Code using F110 and payment method ‘N’. Progress to schedule print using program RFFOM100. Do not select the Print Immediately option in the program variant


10 Print spool created in Test 9 onto headed notepaper

Text is correct for Company Code, Currency and Netting payment and fits headed paper and window envelope when folded

11 Netting Advices – create AP payment run for an IE Company Code using F110 and payment method ‘N’. Progress to schedule print using program RFFOM100. Do not select the Print Immediately option in the program variant


12 Print spool created in Test 11 onto Nestlé Ireland headed notepaper

Text is correct for Company Code, Currency and Netting payment and fits headed paper and window envelope when folded

7.2 Technical Test Cases (TO)

<Template instructions in red, please delete>In this section, the technical owner will attach any extra information on how to test the cases described above, as well as any additional technical testing that he thinks needs to be done, such as ALE-Config/Error handling testing.

In this section, the actual execution of the testing should be documented as well.

Test Case Description Steps Test Data Expected Result Actual Result/Remarks Executed By/Date

document.doc


Page 32 of 35 Created: 20.04.200404.09.2003

Printed: 08.04.2004 17:00


Test Case Description Steps Test Data Expected Result Actual Result/Remarks Executed By/Date

document.doc


Page 33 of 35 Created: 20.04.200404.09.2003

Printed: 08.04.2004 17:00


8 Appendix Z: Reference Documentation

NOTE: INFORMATION CONTAINED WITHIN SECTION IS TO BE USED AS REFERENCE MATERIAL ONLY, NOT TO BE COMPLETED

8.1 SAMPLE SAP Data Relationship Diagram

This is sample Data Relationship diagram to show the database tables used in the development and the relevant data for the report and the relationships between them.

document.doc


Page 35 of 35 Created: 20.04.200404.09.2003

Printed: 08.04.2004 17:00