0% found this document useful (0 votes)
10 views6 pages

ZF 180

The document outlines the Business Requirement Document (BRD) for the ZF180 Customer Balance Application, detailing requirements for both customer and HMCL sides. It includes sections on application scope, input and output parameters, process flow, security control, workflow, integration points, and test scenarios. The document is intended for internal use at Hero MotoCorp Ltd. and is classified as confidential.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
10 views6 pages

ZF 180

The document outlines the Business Requirement Document (BRD) for the ZF180 Customer Balance Application, detailing requirements for both customer and HMCL sides. It includes sections on application scope, input and output parameters, process flow, security control, workflow, integration points, and test scenarios. The document is intended for internal use at Hero MotoCorp Ltd. and is classified as confidential.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

BRD – <SAP BW ABAP>

Document Control
Document Name BRD – ZF180
Document No.
Current
Hero Version
MotoCorp Ltd.
Date of Release 27.06.2022
34, Community Centre, Basant Lok,
Security Classification
Vasant Vihar, New Delhi – 110057.
Tel:Document Owner
91-11-46044100, Functional Consultant
26143198
Fax:CRS
26143321,
Reference26143198
No

Version Control
Change from previous Date of CRS
Version No. Author
version change Number
1.0 Draft version 27.06.2022 Shreyosee
Updated after
2.0 27.06.2022 Shreyosee
walkthrough comments
3.0
BRD - <Project Name>

4.0

Contacts

Title Name Email / Phone

1 Table of Contents

1. BUSINESS REQUIREMENT............................................................................................................................ 4

2. APPLICATION SCOPE................................................................................................................................... 4

3. INPUT PARAMETERS................................................................................................................................... 4

4. PROCESS FLOW........................................................................................................................................... 4

4.1 DATA SOURCE.................................................................................................................................................4


4.2 TRIGGER EVENT.............................................................................................................................................. 4
4.3 EXPECTED SYSTEM LOAD...................................................................................................................................4
4.4 ENVIRONMENT / CONFIGURATION......................................................................................................................4
4.5 DEVELOPMENT DEPENDENCIES...........................................................................................................................4

5. OUTPUT PARAMETERS................................................................................................................................ 4

6. SECURITY CONTROL.................................................................................................................................... 4

7. WORKFLOW................................................................................................................................................ 4

8. INTEGRATIONS POINTS............................................................................................................................... 5

9. TEST SCENARIOS......................................................................................................................................... 5

Hero MotoCorp Ltd. Page 2


Internal – Confidential
BRD - <Project Name>

1. Business Requirement

ZF180 – Customer Balance Application

At Customer side application

1. In customer side application need to add date of balance confirmation (Open items at key
date)
-> Add in the table on DI

2. Update the status column with "Updated"

At HMCL side
1. To download multiple dealer supporting and balance confirmation
pdf file.
Name of files should be with the dealer number and dealer name

2. Application Scope
Application scope will define the visibility of the application to the different platform i.e. BI/DI/Fiori Tile
or Non SAP application.

Application BI DI Fiori Non-SAP ECC ASP


X X

3. Input Parameters

Hero MotoCorp Ltd. Page 3


Internal – Confidential
BRD - <Project Name>

4. Process flow
4.1 Data source

4.2 Trigger Event

4.3 Expected system Load

4.4 Environment / Configuration

4.5 Development Dependencies

5. Output Parameters
ZF180 – Customer Balance Application

At Customer side application

1. In customer side application need to add date of balance confirmation (Open items at key
date)
-> Add in the table on DI

2. Update the status column with "Updated"

At HMCL side
1. To download multiple dealer supporting and balance confirmation
pdf file.
Name of files should be with the dealer number and dealer name

6. Security Control
Roles & Authorization

7. Workflow
Process workflow execution

Hero MotoCorp Ltd. Page 4


Internal – Confidential
BRD - <Project Name>

8. Integrations Points

When we Integrating our SAP application output with other application

9. Test Scenarios

Hero MotoCorp Ltd. Page 5


Internal – Confidential
BRD - <Project Name>

Hero MotoCorp Ltd. Page 6


Internal – Confidential

You might also like