Header Footer PA

35
Document type High Level Definition Title HLD_0020176082_SEPA Payment advice customer direct debit and vendor Version 1.0 Document status Final /RELEASED Status 07.06.2013

description

Header footer

Transcript of Header Footer PA

Page 1: Header Footer PA

Document type

High Level Definition

Title

HLD_0020176082_SEPA Payment advice customer direct debit and vendor

Version

1.0

Document status

Final/RELEASED

Status

07.06.2013

Page 2: Header Footer PA

For any document control issues pertaining to this document or for information about its access and location please notify the following contact:

Responsible Kalpana Nagabhiru

Phone <Phone +91 40 67055545>

E-mail [email protected]

Name of document HLD_0020176082_SEPA – Payment advice customer direct debit and vendor

Current released version 1.0

Last released version approved by

Document History

Date Version Changed chapter

Changed by Comment

31.05.2013

1.0 Creation Kalpana Nagabhiru

Document created

03.06.2013

1.0 Reviewed Nandakishore KVP

HLD reviewed

06.06.2013

1.0 Created Mohammad Asif Hussain

Technical Specification added

06.06.2013

1.0 Reviewed Vidya Sagar Techncal Specification review

Page 3: Header Footer PA

Contents1 Introduction.............................................................................................................................42 Business Context.....................................................................................................................5

2.1 Affected Organizational Units....................................................................................................52.2 Supported Business Processes....................................................................................................5

2.2.1 Business Process...................................................................................................................................52.2.2 Posting Records Business Process <A>...............................................................................................6

3 System Context........................................................................................................................73.1 <Neighbor System A>..................................................................................................................7

4 System User Roles...................................................................................................................85 Functional System Features...................................................................................................96 System Requirements Outline...............................................................................................11

6.1 Usage Concept Outline..............................................................................................................116.1.1 Use Case 1..........................................................................................................................................11

6.2 Conceptual Data Model Outline...............................................................................................126.2.1 Business Objects.................................................................................................................................126.2.2 Relationships......................................................................................................................................12

6.3 User Interfaces Outline.............................................................................................................136.3.1 Dialog Type Specifications................................................................................................................136.3.2 Report Type Specifications................................................................................................................136.3.1 Form Specifications............................................................................................................................136.3.2 Help System.......................................................................................................................................136.3.3 Internationalization.............................................................................................................................146.3.4 Other user interfaces aspects..............................................................................................................14

6.4 System Operations Outline.......................................................................................................146.4.1 System Operation #SYSOP.<Name>.................................................................................................14

6.5 Technical Interfaces Outline.....................................................................................................156.5.1 Technical Interface:............................................................................................................................15

6.6 Access and Authorization Concept Outline.............................................................................166.6.1 Identification and Authentification....................................................................................................166.6.2 User Groups, Roles and Rights..........................................................................................................166.6.3 Other Security Measures....................................................................................................................16

6.7 Nonfunctional System Requirements Outline.........................................................................16

7 Technical Solution Outline...................................................................................................187.1 Solution Approach Outline.......................................................................................................187.2 System Release Roadmap..........................................................................................................18

7.2.1 System Release <Name>....................................................................................................................18

7.3 Deployment Concept..................................................................................................................187.4 Technical Constraints Outline..................................................................................................19

7.4.1 Target Environment............................................................................................................................197.4.2 Infrastructure & Operations Requirements........................................................................................19

8 Agreed Omissions..................................................................................................................20

Page 4: Header Footer PA

Appendix.......................................................................................................................................21

Page 5: Header Footer PA

HLD_0020176082_SEPA – Payment advice customer direct debit and vendor

1 Introduction

This chapter is a brief introduction to the purpose of this document as well as content and addressed audience.

This document defines the profile of the system to be developed in the software development project “HLD_20176082_SEPA – Payment advice customer direct debitand vendor” and serves as the basis for a class “A“ estimation1. CoFiCo has an estimation variance of 50%.

It defines the functional profile of the system as seen from a "higher level", i.e a business and usage perspective. This document describes the embedding of the future software system in its business, system and usage environment, defines all features the system will provide and outlines central system requirements, detailed enough for a Class A estimation.

Therefore, it is not as concrete as a software requirements specification (SRS), but is detailed and complete enough as needed for the first cost estimation.

In case of a demand for a system change this document comprises only system aspects which are subject to change. In such cases, it might not be necessary to fill out all of the following chapters.

All chapters need to be edited. In case a chapter or sub-chapter is not relevant comment “Not applicable” has to be placed.

Please save this document following this nomenclature:

HLD_[CR Number]_[Title]_V[Version].doc

(E.g.: HLD_0020176082_SEPA – Payment advice customer direct debit and vendor V1.0.doc)

1 A class ”A“ estimate has an estimation variance of 30-50%

Daimler AG Seite 5 von 32

Page 6: Header Footer PA

HLD_0020176082_SEPA – Payment advice customer direct debit and vendor

2 Business Context

Currently MBFrance is using form /DCFC/FIXX_F110P for printing payment advice for customers as well as vendors on preprinted paper and send by post to the customers. Due to the implementation of SEPA regulation,it is required to send a prenotification to the customer. So, it is necessary to add a new information with the mandate number and the ICS number in the existing payment advice form.

2.1 Affected Organizational Units

MBF Co.Codes:0017,0018,0019,1893,2987,3804,3845,3846,4294,4295,FR01 and FR02

2.2 Supported Business Processes

2.2.1 Business Process

The implementation of SEPA is mandatory by 1st of February 2014 for the Euro area countries. For this reason, the SEPA payments of all CoFiCo entities have to follow the SEPA-regulations for SEPA Credit Transfer and SEPA Direct Debit.

Need to do below changes to meet the business requirement:

1. MB France is decided to change the value of Header and Footer data in the existing payment advice form /DCFC/FIXX_F110P where the payment runs are having new SEPA payment methods:B,M,N and Z.

The payment method must be linked to the form in the customization is as below,

Daimler AG Seite 6 von 32

Page 7: Header Footer PA

HLD_0020176082_SEPA – Payment advice customer direct debit and vendor

Currently payment advices are taking printouts on the pre-printed stationary.May be because of this reason payment advice is generating in the SAP without Header and footer details.Please find below the current payment advice format in SAP for reference.

Need to do the changes for the header and footer of payment advice form to meet the given business requirement.Please find below the documents to update the payment advice form with header and footer for specific MB France Co.code,

2. Required to do below changes in the body of the payment advice.

a) Needs to add the information: Bordereau de prélèvement in the below gray box,

b) In this box it is also necessary to add a new line ONLY WHEN THE PAYMENT METHOD is B, M, N or Z

sentence need to fetch in the file is -Votre compte chez nous - Référence unique de mandat numéro (SEPA Mandate ID need to be fetched from table SEPA_MANDATE field MNDID)

Daimler AG Seite 7 von 32

Page 8: Header Footer PA

HLD_0020176082_SEPA – Payment advice customer direct debit and vendor

c) Need to replace the IBAN number for bank account number in the body for SEPA payment methods.

Note:

Please find below file for payment advice body changes for reference.

2.2.2 Posting Records Business Process <A>

Not applicable

Daimler AG Seite 8 von 32

Page 9: Header Footer PA

HLD_0020176082_SEPA – Payment advice customer direct debit and vendor

3 System Context

This chapter describes coarsely the system’s connections to other systems. For illustration purposes, e.g. a System Context Diagram can be used. Technical details of the realized software interfaces which are called from external systems are not described here, see chapter 6.5.

3.1 <Neighbor System A>

Short description of the technical neighbor system

Technical Information

Information about the underlying technology and middleware

NA

Used Interfaces

Summary of all interfaces between the system and the <Neighbor System A> which are affected by the demand (changed or used)

NA

Table 1: System Context System <A>

Daimler AG Seite 9 von 32

Page 10: Header Footer PA

HLD_0020176082_SEPA – Payment advice customer direct debit and vendor

4 System User Roles

Identification of all future system user roles; description of the impact on user/system authorizations.Future system users will act in the following system user roles:

Roles Description Count

Name Description of the role and its typical tasks relating to system usage

Expected User Count

Table 2: System User Roles & Authorizations

NA

Daimler AG Seite 10 von 32

Page 11: Header Footer PA

HLD_0020176082_SEPA – Payment advice customer direct debit and vendor

5 Functional System Features

This chapter documents all required concrete functional characteristics (also called “functional service requirements”) of the system in terms of its “core features”, each documented in one single sentence, which is also understandable for people with no or little project background.Use structuring mechanisms as appropriate (clustering according to supported business processes, process steps, information objects, supported user roles, usage domains, feature sets etc.).Add a unique id, attributes and reference information as appropriate (i.e. add information about the business requirements from which these requirements are derived, e.g. build a “cross-functional traceability matrix”).

#FT.1

MB France is decided to change the value of Header,some filed values in the body and Footer data in the existing payment advice form /DCFC/FIXX_F110P where the payment runs are having new SEPA payment methods:B,M,N and Z.

Summary

SAP Fit Analysis

SAP Module FI-AR

Functionality SEPA

Dependencies & Prerequisites

Not Applicable

Are SAP standard programs or functions available? If Yes, what are the functions and how they can be used?

Not Applicable (as this is existing form enhancement)

Daimler AG Seite 11 von 32

Page 12: Header Footer PA

HLD_0020176082_SEPA – Payment advice customer direct debit and vendor

Customizing Requirements

Each individual process should be documented with customizing requirements. E.g. documents type, tax code, etc.

Not applicable

Training activities

Not applicable

Table 3: Summary Functional Requirement

In case existing SAP functions or data are the basis or are representing a workaround/alternative, attached table needs to be filled:

Similar Process

An existing program which will form the basis of development,

Report name Not applicable

Menu path Not applicable

Transaction code

Not applicable

Explanation Not applicable

Table 4: Reference Functions

Alternative & Workaround

An existing program which can be used as an alternative/workaround. It is a transaction used to manually enter / maintain / display data.

Report name Not Applicable

Menu path Not Applicable

Transaction code

Not Applicable

Explanation Not Applicable

Table 5: Alternative/Workaround Functions

Daimler AG Seite 12 von 32

Page 13: Header Footer PA

HLD_0020176082_SEPA – Payment advice customer direct debit and vendor

Daimler AG Seite 13 von 32

Page 14: Header Footer PA

HLD_0020176082_SEPA – Payment advice customer direct debit and vendor

6 System Requirements Outline

Preliminary sketch of all main system requirements, all concrete and binding system requirements will be detailed and finalized later on in the respective system requirements specifications of the single system releases (see system release roadmap in chapter 7.2).

6.1 Usage Concept Outline

This chapter documents the system’s usage concept. It describes all system usage scenarios to be enabled by the project. In the following we use the widely known concept of use cases. The use case description is the framework to used to define the functional test cases.

Use cases are short structured “stories” describing co-operations of one or more human or technical actors and the software system which provide a specific business value. Use cases thus define function and interaction related system requirements.

6.1.1 Use Case 1

The name of the Use Case is a short heading which summarizes the use case in very few words. E.g. “Register User” or “Send Invoice”.

Actors

User roles conducting this use case. The first role is the one who initiates the use case.Users who executes Automatic payment program for SEPA Payment methods

Goal

Describe the goal of the initiating actor in this use case.Payment advice letter needs to be generated with the specified Header,body and Footer details for the specified MBF Co.codes.

Happy Flow

Outline the needed sequence of interactions between use case actors and the system to achieve the use case target.1)Post customer/vendor invoices with the SEPA payment methods B,N,M and Z in the above mentioned MBF specific company codes2)Execute automatic payment program with the option payment advice generation 3)Check spool generated for payment advice 4) payment advice needs to be generated with the Header and Footer details as spefied for the MBF Co.code.

Daimler AG Seite 14 von 32

Page 15: Header Footer PA

HLD_0020176082_SEPA – Payment advice customer direct debit and vendor

Post-Condition

Describe the final states of the system and the actors after the use case is finished.Not Applicable

6.2 Conceptual Data Model Outline

This chapter describes all information objects (also called “Entities” or “Business Objects”) and their relationships which are used or processed in/by the software system.The focus here is on the abstract conceptional level. No logical or physical data modeling is needed. Also use a visual diagram if appropriate (e.g. a UML class diagram - http://en.wikipedia.org/wiki/Class_diagram - or an ER-diagram for representation -http://en.wikipedia.org/wiki/ER_diagram-).Not Applicable

6.2.1 Business Objects

Describe the information objects the system has to handle, together with all its attributes. Add information about expected data quantities as basis for system architecture considerations.Not Applicable

6.2.2 Relationships

Describe all relationships between business objects which the system has to handle.

Especially include information about the multiplicity (1-n) of all participating objects! Not Applicable

Daimler AG Seite 15 von 32

Page 16: Header Footer PA

HLD_0020176082_SEPA – Payment advice customer direct debit and vendor

6.3 User Interfaces Outline

The User Interface is the interface between human users and the system. The graphical user interface should be described here as well as all the other interfaces, e.g. a command line language, reports, print layouts, email layouts etc.For a class A estimate the focus lies on the quantity structure. It is not necessary to specify each interface on its own.Not Applicable

6.3.1 Dialog Type Specifications

This chapter consists of a description of each UI dialog type and its quantities: How many dialogs of these types need to be implemented? Specify the dialog types on an abstract level.Not Applicable

6.3.1.1 <Dialog Type>

Outline of the dialog type (layout, number and type of used components, number and type of possible interactions etc.) and expected quantities.Not Applicable

6.3.2 Report Type Specifications

This chapter consists of descriptions of each system report and its quantities: How many reports of these types need to be implemented? Specify the report types on an abstract level.Not Applicable

1.1.1 Form Specifications

As part of this RFC form /DCFC/FIXX_F110P has to be ehnaced with the changes provided in the section 7.Technical Solution Outline

6.3.2.1 <Report Type>

Outline of the report type (print layout, filter possibilities, data processing requirements, sorting criteria etc.) and expected quantities.Not Applicable

6.3.2.2 <Form Type>

Sap Script

Daimler AG Seite 16 von 32

Page 17: Header Footer PA

HLD_0020176082_SEPA – Payment advice customer direct debit and vendor

6.3.3 Help System

Not Applicable

6.3.4 Internationalization

Internationalization requirements (e.g. which languages need to be supported). Not Applicable

6.3.5 Other user interfaces aspects

Abstract specifications of other interface components’ types and aspects like customizability requirements, email-Notifications, print layouts, sound processing requirements etc.Include expected quantities!Not Applicable

6.4 System Operations Outline

System operations are autonomously running processing units which generate a noticeable benefit for system users or its business and technical environments. Possible system operations are e.g. complex processing algorithms (e.g. accounting transactions over night), batch jobs, system functions called by external systems etc.System operations are triggered through the user interface or through internal or external technical interfaces (see technical interfaces), or may be started autonomously by the system itself (e.g. according to a configurable schema).Only give an outline of each operation here. Not Applicable

6.4.1 System Operation #SYSOP.<Name>

Describe the operation and its purpose here.

Input/Output Data

Which data is needed by the operation? Which data is produced by the operation? Remember that output data can also be written as a side effect into the registry, data files, data base etc.Not Applicable

Processing/Post conditions

What is achieved through this operation?Example: How is the input data processed in order to get the return and output data?Not Applicable

Daimler AG Seite 17 von 32

Page 18: Header Footer PA

HLD_0020176082_SEPA – Payment advice customer direct debit and vendor

Daimler AG Seite 18 von 32

Page 19: Header Footer PA

HLD_0020176082_SEPA – Payment advice customer direct debit and vendor

6.5 Technical Interfaces Outline

Not Applicable

6.5.1 Technical Interface:

Describe the interface and its purpose here.Not Applicable

6.5.1.1 Technology

Specify its technology. The selection of its technology is the basis for the specification of the interface (network type, standard, communication protocol, used media, technical constraints, etc.).

Not Applicable

6.5.1.2 Specification

A concrete single functionality of the interface is specified here, e.g. a working file used for import/export or a service method callable from external systems etc. In the following you will find a possible template for the specification of active interface functionalities. In case of a passive functionality like an import/export file you will have to specify its file structure instead (e.g. CSV-Struktur, DTD, XML-Schema,).

Not Applicable

Input Data

Description of data types, contents, and data volumes Not Applicable

Processing

Description of needed data processingNot Applicable

Output Data

Description of data types, contents, and data volumesNot Applicable

Daimler AG Seite 19 von 32

Page 20: Header Footer PA

HLD_0020176082_SEPA – Payment advice customer direct debit and vendor

6.6 Access and Authorization Concept Outline

Describe user groups and roles, definitions of the resources which need to be protected, methods of identification and authentication, administration and authorization, remote access, data security, etc.

NotApplicable

Security Requirements

Do special authorization requirements exist? Yes No

Are the authorization requirements covered by SAP standard? Yes No

Does CoFiCo need to prepare own authorization objects? Yes No

Table 6: Security Requirement

6.6.1 Identification and Authentification

Identification and authentication of users and external systems. Consider e.g. login dialogs, chip cards, biometric profiles, remote access, check of IP/MAC addresses etc.Not Applicable

6.6.2 User Groups, Roles and Rights

This chapter describes the various user groups, roles, and rights which are distinguished in the access and authorization concept. See chapter 4 for details about user roles.Not Applicable

6.6.3 Other Security Measures

Describe all other concrete security measures to be implemented. E.g.: Resources to be protected (functions, data, or interfaces), data encryption, regulations according to project environment and processes (e.g. security measures concerning staging, test, and operation environments).Not Applicable

Daimler AG Seite 20 von 32

Page 21: Header Footer PA

HLD_0020176082_SEPA – Payment advice customer direct debit and vendor

6.7 Nonfunctional System Requirements Outline

Describe the global requirements which do not directly relate to system functionality but describe constraints, characteristics, or the expected “quality” of system functions and other project deliverables (e.g. documentation). Examples: Requirements for usability, documentation, efficiency, security, reliability, robustness, portability, response time behavior, data and transaction volumes, serviceability and maintenance, operation, etc.

Requirement

Description How to validate

#NFR.<Name>

<Detailed specification of the requirement>

<How should it be validated?>

...

Table 7: Nonfunctional System Requirements

Daimler AG Seite 21 von 32

Page 22: Header Footer PA

HLD_0020176082_SEPA – Payment advice customer direct debit and vendor

7 Technical Solution Outline

This RFC can be divided into two requirements :

Requirement 1 : Logo and Footer Changes

The header and footer for the existing form /DCFC/FIXX_F110P has to be changed for the payment runs with new SEPA payment method : B,M,N and Z.

Requirement 2 : Body changes in Info window

Changes in the body in the form /DCFC/FIXX_F110P in the info window.

Below section will elaborate on above two requirements:

Requirement 1 : Logo and Footer Changes

Logo and Footer images for the below company codes are already developed as part of ECOMM RFC 11147721.

Company Code

Header Logo Footer Logo Remarks

0018 /DCFC/FIXX_FRANCE_18_HEADER /DCFC/FIXX_FRANCE_18_FOOTER NA

0019 /DCFC/FIXX_FRANCE_19_HEADER /DCFC/FIXX_FRANCE_19_FOOTER NA

3804 /DCFC/FIXX_FRANCE_3804_HEADER

/DCFC/FIXX_FRANCE_3804_FOOTER

Footer provided in this BRD is different compared to ECOMM

3845 /DCFC/FIXX/PARIS_HEAD_3845 /DCFC/FIXX/PARIS_FOOT_3845 „

3846 /DCFC/FIXX/PARIS_HEAD_3846 /DCFC/FIXX/PARIS_FOOT_3846 „

4294 /DCFC/FIXX/PARIS_HEAD_4294 /DCFC/FIXX/PARIS_FOOT_4294 NA

4295 /DCFC/FIXX/PARIS_HEAD_4295 /DCFC/FIXX/PARIS_FOOT_4295 NA

The Below company codes need to be considered as part SEPA .

Daimler AG Seite 22 von 32

Page 23: Header Footer PA

HLD_0020176082_SEPA – Payment advice customer direct debit and vendor

Upload the logo and footer images provided in the Section 2.2.1 with the below naming convention.

Company Code

Header Logo Footer Logo Remarks

0017 /DCFC/FIXX_0017_Header

/DCFC/FIXX_0017_Footer

Logo and Footer image is yet to be provided

1893 /DCFC/FIXX_1893_Header

/DCFC/FIXX_1893_Footer

2987 /DCFC/FIXX_2987_Header

/DCFC/FIXX_2987_ Footer

FR02 /DCFC/FIXX_FR02_Header

/DCFC/FIXX_FR02_ Footer

FR01 /DCFC/FIXX_FR01_Header

/DCFC/FIXX_FR01_ Footer

Create a new table to maintain the Logo and Footer images based on company code and SEPA payment methods

Table Name /DCFC/FIXX_SEPA_FORM

Table Description

Flexible table for all SEPA forms

Table Type Customizing Table

Field Data Type

Description Example Remarks

MANDT* MANDT Client 010 This table is client dependent

BUKRS* BUKRS Company Code 3485 Company Code for which the SEPA changes are applicable

PAYMTD* ZWELS Payment Method Z Payment method for which SEPA form changes are applciation

Daimler AG Seite 23 von 32

Page 24: Header Footer PA

HLD_0020176082_SEPA – Payment advice customer direct debit and vendor

FORMNAME* Char30 Form Identifier or Form Name

/DCFC/FIXX_F110P

Maintain the form name for which Logo and footer needs to be maintained

POSITION* CHAR 15 Identifier for the Object

'LO' for LOGO and 'FT' for Footer

Position of Logo, Footer or text

Object CHAR 70 Name of the object

/DCFC/PT_LOGO or T

SE78. The position for Logo is G1

s

Maintain the Logo & Footer images in the table /DCFC/FIXX_SEPA_FORM aganist the Company code, payment method and 'FT' for the Footer images and 'LO' for the Logos

In the header and footer windows of the script /DCFC/FIXX_F110P :

Use PERFORM GET_SEPA_DATA IN PROGRAM /DCFC/FIAR_CONF2 in the script /DCFC/FIXX_F110P and fetch the logo names from the above mentioned table.

Requirement 2 : Body changes in Info and main window

Enhance the Info window in the SAP script /DCFC/FIXX_F110P

Condition based on payment method

Text required

IF &REGUH-RZAWE& = 'B' Bordereau de prélèvement

IF &REGUH-RZAWE& = 'M' Bordereau de prélèvement

IF &REGUH-RZAWE& = 'N' Bordereau de prélèvement

IF &REGUH-RZAWE& = 'Z' Bordereau de prélèvement

IF &REGUH-RZAWE& = 'F' Bordereau de règlement

Enhance the main window with below text

610-B

------------------ TEXTE PRELEVEMENT -----------------------------------

Daimler AG Seite 24 von 32

Page 25: Header Footer PA

HLD_0020176082_SEPA – Payment advice customer direct debit and vendor

Mesdames, Messieurs,

Veuillez trouver ci-dessous la justification de notre prélèvement

no &REGUH-VBLNR& sur votre compte

&REGUD-ZBANK& &REGUH-ZIBAN&

Prélèvement à partir du &REGUH-AUSFD&

610-M

------------------ TEXTE PRELEVEMENT -----------------------------------

Mesdames, Messieurs,

Veuillez trouver ci-dessous la justification de notre prélèvement

no &REGUH-VBLNR& sur votre compte

&REGUD-ZBANK& &REGUH-ZIBAN&

Prélèvement à partir du &REGUH-AUSFD&

610-N

------------------ TEXTE PRELEVEMENT -----------------------------------

Mesdames, Messieurs,

Veuillez trouver ci-dessous la justification de notre prélèvement

no &REGUH-VBLNR& sur votre compte

&REGUD-ZBANK& &REGUH-ZIBAN&

Prélèvement à partir du &REGUH-AUSFD&

610-Z

------------------ TEXTE PRELEVEMENT -----------------------------------

Mesdames, Messieurs,

Veuillez trouver ci-dessous la justification de notre prélèvement

no &REGUH-VBLNR& sur votre compte

&REGUD-ZBANK& &REGUH-ZIBAN&

Prélèvement à partir du &REGUH-AUSFD&

610-F

------------------ TEXTE VIREMENT --------------------------------------

Daimler AG Seite 25 von 32

Page 26: Header Footer PA

HLD_0020176082_SEPA – Payment advice customer direct debit and vendor

Mesdames, Messieurs,

Nous vous informons que nous avons donné l'ordre à notre banque

de virer le montant ci-dessous à votre compte

,,,,&REGUD-ZBANK&

&REGUH-ZIBAN&

IF &REGUH-ZBUKR& = '3845'

INCLUDE TEXTE3845 OBJECT TEXT ID SDTP

ENDIF

When the payment method is B, M, N or Z, this row must be completed

All the information for the payment method “D” must be copied for the payment method B, M, N and Z

All the information for the payment method “V” must be copied for the payment method F

Daimler AG Seite 26 von 32

Page 27: Header Footer PA

HLD_0020176082_SEPA – Payment advice customer direct debit and vendor

In the box in grey, please add the following information : Bordereau de prélèvement

In this box it is also necessary to add a new line ONLY WHEN THE PAYMENT METHOD is B, M, N or Z

Below the sentence Votre compte chez nous

The information is Référence unique de mandat numéro

ID mandate Table SEPA_MANDATE field MNDID else derive from standard function module SEPA_MANDATES_API_GET

7.1 Solution Approach Outline

This chapter is optional. Outline of the overall development strategy (e.g. development all at once or iterative/agile development; design rational for the release roadmap, decisions about prototyping usage and pilots; in house development or external supplier; overall acceptance procedures; program/project setup; etc.)Not Applicable

7.2 System Release Roadmap

Definition of all discrete system stages for consecutive roll-outs.The development for this RFC is done in DF1 010.

Once the development is complete it will be moved for Quality test in QF1 system, all the workbench and customising objects will be moved to QF1 010

Once approved in QF1 the RFC will be moved to IF1 in the same manner as we moved objects from DF1 to QF1.

After which the developed workbench objects are moved to PF1 010 during the release/rollout.

7.2.1 System Release <Name>

Definition of time frame and feature scope of this release. Time frame for development and rollout for each system stage must not exceed one year.

Daimler AG Seite 27 von 32

Page 28: Header Footer PA

HLD_0020176082_SEPA – Payment advice customer direct debit and vendor

This RFC is planned for REL 28.

7.3 Deployment Concept

This chapter is optional. Outline of the deployment strategy for the first system stage (e.g. needed data migrations, chosen system migration scenarios like big bang, concurrent operation etc.)Not Applicable

Migration Scope

Is there the necessity to convert application or administrative data within CoFiCo based on new/change functionality?

Yes No

Table 8: Migration Scope

Not Applicable

7.4 Technical Constraints Outline

This chapter documents all constraints concerning the technical and organizational embedding of the software system and its components into its operational environment.It mainly includes all requirements about the system's operation environment, but may optionally also include requirements concerning the technical implementation concept; e.g. the system architecture to be implemented (e.g. internal logical system parts/subsystems and their interfaces) or all system components to be used (e.g. PAI components, client-server components, etc.).Not Applicable

7.4.1 Target Environment

Document all requirements concerning the technical target environment in which the future software system will be operated. Which technical (sub)systems and/or components are to be developed and deployed?Not Applicable

Daimler AG Seite 28 von 32

Page 29: Header Footer PA

HLD_0020176082_SEPA – Payment advice customer direct debit and vendor

7.4.2 Infrastructure & Operations Requirements

Requirements concerning the future operational environment of the software system (e.g. needed service time, availability, reaction time, etc.)Not Applicable

Daimler AG Seite 29 von 32

Page 30: Header Footer PA

HLD_0020176082_SEPA – Payment advice customer direct debit and vendor

8 Agreed Omissions

All agreed omissions are documented here. Filling of those gaps is left to the future system requirements documentation phase.This document has the following explicit omissions that have to be supplemented in later phases:

No.

Agreed Omission Reason

Not Applicable

Table 9: Agreed omissions

Daimler AG Seite 30 von 32

Page 31: Header Footer PA

HLD_0020176082_SEPA – Payment advice customer direct debit and vendor

Appendix

Open Issues

Here, open issues can be listed which still have to be discussed, decided, or agreed on.

Not Applicable

Daimler AG Seite 31 von 32

Page 32: Header Footer PA

HLD_0020176082_SEPA – Payment advice customer direct debit and vendor

Documentation References

Document Author Date Version

NA

Figures

Fehler! Es konnten keine Einträge für ein Abbildungsverzeichnis gefunden werden.

Tables

Table 1: System Context System <A> 6

Table 2: System User Roles & Authorizations 7

Table 3: Summary Functional Requirement 8

Table 6: Reference Functions 9

Table 4: Interface Definition 14

Table 5: Security Requirement 15

Table 6: Nonfunctional System Requirements 16

Table 7: Migration Scope 17

Table 8: Agreed omissions 19

Daimler AG Seite 32 von 32