SAP Replenishment Process Blueprint

SAP Implementation
at
Project Name
Business Blueprint Document

Version No.: 1.20
Effective Date: 05.01.2017
Module: SAP FMS Retail

Process: Replenishment Process at Stores
Document No.: BBD_RET_005_Replenishment
ARVIND / IBM Confidential

Business Blueprint Document – XX Retail (Module) - XX Replenishment (Process
Details)
Document No: BBD_RET_005 Version No: 1.210 Effective Date:
183005.1101.20176 Project Arvind
Table of Contents
1.0 DOCUMENT INFORMATION..........................................................................................................4

1.1 DOCUMENT VERSION.....................................................................................................................4
1.2 DOCUMENT APPROVAL DETAILS.......................................................................................................4
1.3 REFERENCE DOCUMENT DETAILS (IF ANY)..........................................................................................5
1.4 ABBREVIATIONS USED (IF ANY)........................................................................................................ 5
2.0 BUSINESS REQUIREMENT............................................................................................................6

2.1 APPLICABILITY...............................................................................................................................6
2.2 DETAILS OF BUSINESS REQUIREMENT................................................................................................6
2.3 BUSINESS REQUIREMENT FLOW DIAGRAM (IF ANY).............................................................................7
3.0 BUSINESS PROCESS DESCRIPTION...............................................................................................7

3.1 PROCESS DETAILS.......................................................................................................................... 8
3.2 PROCESS MAPS:..........................................................................................................................19
3.3 BUSINESS PROCESS STEPS.............................................................................................................19
3.4 KEY DATA STRUCTURE ELEMENTS...................................................................................................20
3.5 ASSOCIATED MASTER DATA ELEMENTS (IF ANY)...............................................................................20
3.6 INTERFACE MAPS (IF ANY)............................................................................................................ 20
3.7 REPORTS MAPPING (IF ANY)......................................................................................................... 20
3.8 PROCESS VARIATIONS / EXCEPTIONS (IF ANY)...................................................................................20
4.0 INTEGRATION POINTS (IF ANY).................................................................................................20
5.0 KEY BUSINESS IMPROVEMENTS (IF ANY)..................................................................................20
6.0 CHANGES TO EXISTING ORGANIZATION (IF ANY).....................................................................21
7.0 GAPS...........................................................................................................................................21
Arvind/IBM Confidential
Page 2 of 31
Details)
8.0 DEVELOPMENT CONSIDERATIONS (RICEFW)............................................................................22

8.1 DATA CONVERSION CONSIDERATIONS............................................................................................. 22
8.2 INTERFACE CONSIDERATIONS......................................................................................................... 23
8.3 FORM CONSIDERATIONS............................................................................................................... 23
8.4 REPORTING CONSIDERATIONS........................................................................................................23
8.5 FUNCTIONAL ENHANCEMENT CONSIDERATIONS................................................................................ 24
9.0 AUTHORIZATION REQUIREMENTS............................................................................................24
10.0 ANNEXURE (IF ANY)...............................................................................................................25
11.0 FLOW CHART LEGEND............................................................................................................25
1.0 DOCUMENT INFORMATION.........................................................................................................4
1.1 DOCUMENT VERSION...............................................................................................................4
1.2 DOCUMENT APPROVAL DETAILS.............................................................................................4
1.3 REFERENCE DOCUMENT DETAILS (IF ANY)..............................................................................5
1.4 ABBREVIATIONS USED (IF ANY)...............................................................................................5
2.0 BUSINESS REQUIREMENT............................................................................................................6
2.1 APPLICABILITY..........................................................................................................................6
2.2 DETAILS OF BUSINESS REQUIREMENT....................................................................................6
2.3 BUSINESS REQUIREMENT FLOW DIAGRAM (IF ANY)..............................................................7
3.0 BUSINESS PROCESS DESCRIPTION...............................................................................................7
3.1 PROCESS DETAILS.....................................................................................................................8
3.2 PROCESS MAPS:.....................................................................................................................16
3.3 BUSINESS PROCESS STEPS......................................................................................................16
3.4 KEY DATA STRUCTURE ELEMENTS.........................................................................................17
Page 3 of 31
Details)
3.5 ASSOCIATED MASTER DATA ELEMENTS (IF ANY).................................................................17
3.6 INTERFACE MAPS (IF ANY).....................................................................................................17
3.7 REPORTS MAPPING (IF ANY).................................................................................................17
3.8 PROCESS VARIATIONS / EXCEPTIONS (IF ANY).....................................................................17
4.0 INTEGRATION POINTS (IF ANY).................................................................................................18
5.0 KEY BUSINESS IMPROVEMENTS (IF ANY)..................................................................................18
6.0 CHANGES TO EXISTING ORGANIZATION (IF ANY).....................................................................18
7.0 GAPS...........................................................................................................................................18
8.0 DEVELOPMENT CONSIDERATIONS (RICEFW)............................................................................19
8.1 DATA CONVERSION CONSIDERATIONS.................................................................................19
8.2 INTERFACE CONSIDERATIONS...............................................................................................20
8.3 FORM CONSIDERATIONS.......................................................................................................20
8.4 REPORTING CONSIDERATIONS..............................................................................................21
8.5 FUNCTIONAL ENHANCEMENT CONSIDERATIONS.................................................................21
9.0 AUTHORIZATION REQUIREMENTS............................................................................................21
10.0 ANNEXURE (IF ANY)...............................................................................................................22
11.0 Flow Chart Legend..................................................................................................................23
Page 4 of 31
Details)
1.0 Document Information
Document Category Business Blueprint Document

Document Title Replenishment Process at Stores
Author Hemu Rajput
File Name BBP_RET_005_Replenishment Process at Stores_V1.10
Created On 18.11.2016
1.1 Document Version
Date Version No. Author Change Description

11-Nov-2016 1.0 Hemu Rajput Initial Release
Post incorporation of changes in
Blue Print validation
workshopChanges as per the
30-Nov-20-16 2.01.1 Hemu Rajput business meeting on 29.11.16
MOQ Validation level required
04-Jan-2016 1.2 Hemu Rajput at Category and Site level.
1.2 Document Approval Details
Function Name (Designation) Role Sign & Date

Hemu Rajput IBM Team Member
Prepared By
Core Team Member
Abhijit Nag / Naina
Acharya IBM Team Lead
Reviewed By
Process Owner
T Sudhir IBM Project Manager

Abel Correa Arvind Project Manager
Approved By
Page 5 of 31
Details)
1.3 Reference Document Details (If any)

As-Is discussed with the Business Team
Department /
Title of the Document Version No Organization Reference / Remarks
1.4 Abbreviations Used (If any)

Abbreviation Description
TAS The Arvind Store
GED Garments Export Division
AFBL Arvind Fashion Brand Ltd (Old) / Arvind Ltd – Fashion Division
ASPOL Arvind Sports Ltd (Old) / Arvind Ltd – Sports Division
ATBL Arvind True Blue Ltd
APRL Arvind Premium Retail Ltd
ARTL Arvind Ruf & Tuf Pvt Ltd
ROP Reorder Point
TS Target Stock
SP Sales Plan
Page 6 of 31
Details)
2.0 Business Requirement
2.1 Applicability
The process described in this document details Replenishment Process at Stores necessary for
enabling ARVIND’s various business processes defined under Business Blueprint Document for
Retail module.
The document is applicable for following business verticals of Arvind group:

Business Vertical Applicability (Yes/No)
The Arvind Stores YesNo
Fashion division Yes
Sports division Yes
Arvind True Blue Ltd Yes
Arvind Premium Retail Ltd Yes
Arvind Ruff and Tuff Ltd Yes
Arvind Internet Limited NoYes
Garment export division No
2.2 Details of Business Requirement

In the current business scenario for Arvind Limited – Fashion/Footwear /ATBL /ARTPL/APRL Fashion
Division and Sports Division, the replenishment for stores is happening manually in excel files where
the merchandiser prepares the weekly Sales Plan at the Articles/EAN level per store. There are two
types of planning in the business :
IIn Season Planning: Based on the Style and the Rate of the Sales, analysing the Past Sales Data
merchandiser prepares the weekly sales plan for the articles at the EAN level.
Page 7 of 31
Details)
New Planning: This planning is for the new product for which the Past Sales data is not available in the
system, so for this type of planning the merchandiser gives the Target range of coverage for new articles
based on his intelligence and experience.
Below mentioned are the parameters based on which the merchandiser prepares the Sales plan
for the articles at EAN level.
 5 Week Past Sales

 Last one Week Sales.
 Stock on Hand.
 In-transit to Stores – Good which will be coming to the Stores
 Pending Returns – Goods going out of the stores, back to DC or Stores.
 Store Status – Considering the state of the Store if it is Closed or Open or Under
Renovation.
 Number of week coverage – This is target range of coverage for an article.
 Store Grading
 Rate of Sales – This is basically a formula based on the past sales of an article. (Total
Sales/No. of Weeks)
Based on the above parameters, merchandiser will prepare the Sales Plan of an article at EAN
level and runs the replenishment weekly as the idea is to deliver the goods from the warehouse
in the optimised manner.
All the above mentioned calculation is happening manually in excels sheets, this data as per the
current business scenario is not getting calculated in ARS system and the requirement is to
reduce the manual labour with the SAP implementation and SAP should suggest the Sales Plan of
the article at the EAN level considering the target range of coverage and Past Sales Data.
Page 8 of 31
Details)
*** Changes Version 1.1

******Change of version
The business requirement is that the system should find out the Sales Plan for an article at the
particular stores on the basis of the consumption data and allocate the stock from the DC’s based
on the stock availability in the DC.
******End of change

There is a business requirement to put a validation on the total STO quantity that is going to get
generated via replenishment. The business will provide the MOQ (Minimum Order Quantity) at
the Store and Category level and when the STO is going to get created via replenishment then
system should restrict the creation of PO based on the MOQ quantity i.e. STO should not get
created for the quantity less than MOQ quantity.
***End of change
2.3 Business Requirement Flow Diagram (If any)
3.0 Business Process Description

This section describes the SAP functionality and how it maps to the business processes and
requirements.
Page 9 of 31
Details)
The business will provide the Historical Data for the Sales of an article at the EAN level and SAP will
maintain the replenishment related parameters in the article master and system would suggest the
Target dynamic stock on an articles.
3.1 Process Details

Replenishment in standard SAP at Stores:
In the Replenishment process in SAP at store level, to map the current business scenario we
can use the consumption based planning where the system would suggest the Target
Dynamic stock based on the consumption data.
The Article Master has the below replenishment parameters that needs to be maintained per
store and based on these parameters the replenishment will run and would suggest the
dynamic target stock.
Consumption Data:
Let’s say for the ease of calculation we are going to analyse the Sales data for the past 10 days
for a particular article in a particular store, then the consumption data for an article will be
maintained as mentioned in below screen shot.
Date Consumption Data
21.11.2016 100
20.11.2016 90
19.11.2016 85
18.11.2016 0
17.11.2016 90
16.11.2016 100
15.11.2016 90
14.11.2016 85
13.11.2016 10
Page 10 of 31
Details)
12.11.2016 90
11.11.2016 100
Page 11 of 31
Details)
Page 12 of 31
Details)
RP Type:
Key field that determines how the article is planned, in our business scenario we will use the
RP Types as RF-Replenish with dyn.TargetStock (Replenishment with Target Dynamic Stock)
Target Range of Coverage
Control parameter for dynamically calculating the target stock in replenishment planning and
target range of coverage states the range of coverage during which a material is to be
available for customers, in our example we are keeping the target range of coverage as 10
days.
Forecast Model
We are going to use forecast model as the G-Moving Average Price and Period indicator we
can select as Daily (Period Indicator-T)
Page 13 of 31
Details)
Historical Periods
Historical periods are the periods that we need to consider for the past sales data and
execute forecast for how many periods (periods can be daily, weekly, monthly etc. ).) in this
current example we are considering the daily periods.
Page 14 of 31
Details)
Forecast Run:
Once all the above replenishment related parameters are maintained in SAP then before
running the replenishment we need to execute the forecast for that articles, as can be seen in
the below screen shot the No. of historical period value is 10 and system is going to execute
the forecast of 30 periods.
We are considering the Forecast model as moving average price calculation model as shown below:
Page 15 of 31
Details)
The system has calculated the Forecast value as 74 consideing the Sales data of past 10 days
for example if today is 21st November and we are running the forecast today then system will
check the sales data from 11th Nov- to 20th –Nov and average out the value as shown below:
Date Consumption Data
21.11.2016 100
20.11.2016 90
19.11.2016 85
18.11.2016 0
17.11.2016 90
16.11.2016 100
15.11.2016 90
14.11.2016 85
13.11.2016 10
12.11.2016 90
11.11.2016 100
Page 16 of 31
Details)
Total Consumption: From 11th Nov to 20th Nov = 740, divide by 10 = 74 , this is the quantity
suggested by the system.
Now when running the replenishment at the article or at the store level, the system would
multiply this forecasted values of the article with the Target Range of Coverage, here we are
maintaining the target range of coverage as 7 days so the replenishment should be 74*7=518,
as shown below:
Replenishment in standard SAP in transaction WRP1:
Page 17 of 31
Details)
The system is suggesting the replenishment quantity of 518 EA as shown below, the STO’s can
be generated from DC to receiving store based on the below suggested quantity by
generating the follow on documents.
Page 18 of 31
Details)
This is the quantity suggested by system, if someone wants to change the quantity then we
need to select the particular line item and change the quantity in the system manually.
Also in standard SAP we will not be able to see the DC stock in the same screen.
In the above mentioned example, the quantity shown is 518 considering there are no open
STO’s or goods in transit for this article, if there are some open STO’s or goods in transit then
system would consider that incoming quantity and suggest the quantity based on that.
Let’s say for an example if there are some open STO’s, goods in transit or some issues are
there then system would consider these quantities as well as shown in the below screen shot.
Running the replenishment program without the ‘Include forecast Issue’ tick then system
would not consider the forecast values for the next week.
Page 19 of 31
Details)
Running the replenishment:
Page 20 of 31
Details)
Suggested Target Dynamic Stock after subtracting the expected stock would be 518-(Stock on
Hand) – Open STO’s i.e. 518-10-10=498.

**** Change of version
Note:
Apart from the above mentioned model for replenishment i.e. calculating the target dynamic
stock automatically based on consumption data, the business if required can provide the
Target Stock and Re-Order point in the article master manually or via some excel upload and
MRP type – RP can be used for those specific articles, in this case the system would trigger the
replenishment to fulfil the target stock once the stock reaches the Re-Order point quantity or
below.
Page 21 of 31
Details)
Replenishment in the Stores for Arvind Limited: Fashion/Footwear/ATBL/ARTPL/APRL

Sport:
In the standard SAP when the replenishment runs at the store level , the replenishment
quantity calculation for ain store in the systemt system do not consi stock but the business
requirement is slightly different and is mentioned in the below points.
1. The business requirement is to consider the DC stock availability and on the pro-rata basis
allocate the stock from the DC on tto the stores irrespective of the Target Dynamic stock
suggested by the system.
2. There should be rounding off rule applicable on the higher side so that for the articles where
moving average value for quantity is very less then system should suggest replenishment
quantity for those items too.
3. For the new articles where the historical sales consumption data is not available, there should
be a provision to upload the Target Stock and Reorder point in the system and system should
allocate the stock from the DC on the pro-rata basis once the stock is available in the DC.
4. Expectation of the business from the SAP system is that the system should consider all the
open STO’s and any planned delivery order when considering the DC stock i.e. stock which is
available to promise.
5. Open STO’s at store needs to be closed after two weeks if partially delivered, this will be
confirmed by the business.
SAP Limitation in standard replenishment process and to be process:
As in the standard SAP the replenishment process for store do not consider the DC stock
while calculating the replenishment quantity so we will have a custom enhancement program
that will consider the DC stock (available to promise stock) while allocating the quantity from
DC to store on the basis of pro-rata.
For example if the replenishment quantity for Article A1 suggested by the system for Store A
is 25 and for Store B is 50 and total stock available in the DC is 35 then on the pro-rata basis
DC will allocate the 11.7 rounded off to 12 to Store A and to Store B 23.3 rounded off to 23.
New Article Allocation:
The articles which have never been received in the stores are considered as the new articles
as in the standard SAP replenishment process if there is no consumption data available for
the articles then system would not consider these articles in the replenishment run. Tterfore
Page 22 of 31
Details)
to handle this situation business would provide an Article and their corresponding store with
the target stock in an excel file and we will upload this file in the custom table and our
enhancement program will check the entries for the articles in the custom table for new
articles. iIf tries exist then based on the target stock present and DC stock availability
enhancement program will allocate the DC stock for new articles on the pro-rata basis.
****End of change
***Change of version 1.2

We will maintain the MOQ at the Store and Category level in the custom table in SAP and when the
replenishment will run in SAP the enhancement program should consider this MOQ quantity and
system should not allow to create the STO if the total STO quantity is less than the MOQ.
If there is a scenario that the STO quantity is less than the MOQ quantity then system will have a
check not to create the STO and will pop the information message with the reason of STO not
getting created and in this case if there is a need to create the STO even if the STO quantity is less
than the MOQ then STO needs to be created manually.
****End of change
3.2
3.3
3.4 Process Maps:
Store Replenishment
Create Article Master for the Execute Forecast Run replenishment Make changes to Select the required line
season and maintain the with target range for suggested Dynamic target items and create the
Start replenishment parameters of coverage dynamic target stock stock created STO’s from DC to store
SAP FMS
End
Page 23 of 31
Details)
3.5 Business Process Steps
Sr.
Activity TCode Input Output
No.
Maintain the
Article Master
RP Type, Target Range
with Article Master Data will
1. MM42 of Coverage, Forecast
replenishment be changed.
Model, etc.
related
parameters
Forecast Values will be
Execute the Historical Sales Data in
2. MP30/MP38 saved in the article
Forecast the Article Master
master
STO’s will be created
Run the
from DC to Store on the
replenishment Run the replenishment
3. WRP1Z**** basis of Pro-Rata
enhanced at Site or Article level
depends on the stock
program
availability in the DC..
3.6 Key Data Structure Elements

Article Master: Replenishment related fields as explained in the section 3.1
3.7 Associated Master Data Elements (If any)

Master Data fields related to replenishment are explained in the section 3.1.
Page 24 of 31
Details)
3.8 Interface Maps (If any)

N/A
3.9 Reports Mapping (If any)

Stock Report: MMBE, MB51, MB52, RWBE etc.
Open STO’s Report: ME2N, ME2L etc.
Goods in transit report: MB5T
3.10 Process Variations / Exceptions (If any)

N/A
4.0 Integration Points (If any)

N/A
5.0 Key Business Improvements (If any)

N/A
6.0 Changes to Existing Organization (If any)

Planning will happen in SAP system with the standard SAP functionality of consumption based
planning and historical sales data needs to be updated in the article master via some program and
also as and when this data needs to be changed then core team has to update the replenishment
related parameters in the article master.
Page 25 of 31
Details)
7.0 Gaps
Process Reference / Description of Recommendation to fulfil
Reference No. Details Functional Deficits the Gap
Business wants to see the In the standard SAP we
DC stock, purchase price of cannot view the required
an Article, Sales Price of an fields by the business in the
article etc. in the same same screen of
screen where they will see replenishment, so we need
the dynamic target stock to build an enhancement Build an enhancement to view
quantity suggested by the where the required fields the required fields in the same
system. can be seen. screen of replenishment.
BBD_RET_005
Suggested target stock can
be changed if required in
the standard SAP screen for
replenishment but we have We will build the functionality
to select the item similar to excel sheet where the
individually but the business can view the suggested
business wants to change dynamic stock in the single
all the items in a single In the standard SAP screen screen for all the articles and if
screen and later on after the suggested dynamic required can be changed in the
changing the quantity they stock suggested by the SAP single screen and then the
can convert line items in the cannot be changed in the selected quantities can be
STO’s from DC to Store. single screen. converted in the STO’s.
BBD_RET_005
We will have an enhanced
In the standard SAP system program in place that will check
Business wants to allocate do not consider the DC the replenishment quantity and
the stock from the DC on stock while generating the DC stock and then will allocate
the basis of pro-rata to replenishment quantity in the stock from the DC on the
stores. the stores. pro-rata basis.
BBD_RET_005
BBD_RET_005 For the new season articles There will be no historical Business will upload the
planning, there will be no data for the new article so allocation data for the new
historical sales data and forecast cannot be articles in the custom table and
therefore the forecast will executed for these articles. In the same screen, we need to
not be executed for these build a logic in the enhancement
new articles, so we will program to consider new
have to build an articles also for replenishment
enhancement that should which are present in the custom
give an option to manually table and and till the time the
give the quantity for the historical data is not available in
new articles for the system, business can give
replenishment. the suggested target dynamic
stock manually and also if the
characteristic attribute of this
new article is similar to any old
article then we can also use the
Page 26 of 31
Details)
Process Reference / Description of Recommendation to fulfil

Reference No. Details Functional Deficits the Gap
standard functionality of
referencing the old articles. then
allocate the stock from the DC
on the basis of pro-data.
8.0 Development Considerations (RICEFW)
8.1 Data Conversion Considerations

Description of the Data Conversion Method
Objects / Data to be (like LSMW, iDoc, BDC, Reference Development
Reference No. converted etc.) Specification No
Update the Article
Master replenishment
related parameters. LSMW
BBD_RET_005
Build a program to
update the Historical
sales data in the article
master. Program
BBD_RET_005
BBD_RET_005 Build the enhancement Enhancement
to show the DC stock,
stock in transit, pending
returns, suggested
dynamic stock etc. in the
same screen of
replenishment and
Page 27 of 31
Details)
Description of the Data Conversion Method

Objects / Data to be (like LSMW, iDoc, BDC, Reference Development
Reference No. converted etc.) Specification No
create the STO’s from the
same screen after
selecting the required
line items.the program
should consider the DC
stock and allocate the DC
quantities to the store on
the pro-data basis.
Build a program to
update the Historical
sales data in the article
master. Program
BBD_RET_005
8.2 Interface Considerations

Description of the System / Reference Interface Specification
Reference No. Process to be interfaced Document Number
8.3 Form Considerations

Reference Form Development
Reference No. Description of the Forms Specification Document Number
Page 28 of 31
Details)
8.4 Reporting Considerations

Description of the Report Reference Report Development
Reference No. Requirements Specification Document Number
8.5 Functional Enhancement Considerations

Description of the Functional Reference Functional Enhancement
Reference No. Enhancement Requirements Specification Document Number
9.0 Authorization requirements

Authorization to the transaction codes in the SAP System will be based on the role played by the person in
the organization.
Below table is an example of the Authorization Matrix. The users (super user, middle level user, end user)
are assigned with a role in the SAP System.
Transaction Code will be detailed in the Authorization Matrix.
Role 1 Role 2 Role 3

SAP T.Code Transaction Description (Role Name) (Role Name) (Role Name)
MM41 Create Article Master
MM42 Change Articles Master
Page 29 of 31
Details)
Role 1 Role 2 Role 3

SAP T.Code Transaction Description (Role Name) (Role Name) (Role Name)
MM43 Display Article Master
MP30/MP38 Execute forecast
WRP1 Run Replenishment
10.0 Annexure (If any)

 Annexure-1 – KDS Document
 Annexure-2 – BPML Document
Page 30 of 31
Details)
11.0 Flow Chart Legend
(Process Description)
Start/ End
SAP Process
(Responsible Department/ Role)
SAP Background
Process
Manual Process
(Outside SAP)
Decision
Printout/ Form
Other Defined
Process
Page 31 of 31

SAP Replenishment Process Blueprint

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP Replenishment Process Blueprint

Uploaded by

Copyright:

Available Formats

SAP Implementation

Business Blueprint Document

Effective Date: 05.01.2017

Module: SAP FMS Retail

ARVIND / IBM Confidential

1.0 DOCUMENT INFORMATION..........................................................................................................4

2.0 BUSINESS REQUIREMENT............................................................................................................6

3.0 BUSINESS PROCESS DESCRIPTION...............................................................................................7

4.0 INTEGRATION POINTS (IF ANY).................................................................................................20

5.0 KEY BUSINESS IMPROVEMENTS (IF ANY)..................................................................................20

6.0 CHANGES TO EXISTING ORGANIZATION (IF ANY).....................................................................21

8.0 DEVELOPMENT CONSIDERATIONS (RICEFW)............................................................................22

9.0 AUTHORIZATION REQUIREMENTS............................................................................................24

10.0 ANNEXURE (IF ANY)...............................................................................................................25

11.0 FLOW CHART LEGEND............................................................................................................25

1.0 DOCUMENT INFORMATION.........................................................................................................4

1.1 DOCUMENT VERSION...............................................................................................................4

1.2 DOCUMENT APPROVAL DETAILS.............................................................................................4

1.3 REFERENCE DOCUMENT DETAILS (IF ANY)..............................................................................5

1.4 ABBREVIATIONS USED (IF ANY)...............................................................................................5

2.0 BUSINESS REQUIREMENT............................................................................................................6

2.2 DETAILS OF BUSINESS REQUIREMENT....................................................................................6

2.3 BUSINESS REQUIREMENT FLOW DIAGRAM (IF ANY)..............................................................7

3.0 BUSINESS PROCESS DESCRIPTION...............................................................................................7

3.1 PROCESS DETAILS.....................................................................................................................8

3.2 PROCESS MAPS:.....................................................................................................................16

3.3 BUSINESS PROCESS STEPS......................................................................................................16

3.4 KEY DATA STRUCTURE ELEMENTS.........................................................................................17

3.5 ASSOCIATED MASTER DATA ELEMENTS (IF ANY).................................................................17

3.6 INTERFACE MAPS (IF ANY).....................................................................................................17

3.7 REPORTS MAPPING (IF ANY).................................................................................................17

3.8 PROCESS VARIATIONS / EXCEPTIONS (IF ANY).....................................................................17

4.0 INTEGRATION POINTS (IF ANY).................................................................................................18

5.0 KEY BUSINESS IMPROVEMENTS (IF ANY)..................................................................................18

6.0 CHANGES TO EXISTING ORGANIZATION (IF ANY).....................................................................18

8.0 DEVELOPMENT CONSIDERATIONS (RICEFW)............................................................................19

8.1 DATA CONVERSION CONSIDERATIONS.................................................................................19

8.2 INTERFACE CONSIDERATIONS...............................................................................................20

8.3 FORM CONSIDERATIONS.......................................................................................................20

8.4 REPORTING CONSIDERATIONS..............................................................................................21

8.5 FUNCTIONAL ENHANCEMENT CONSIDERATIONS.................................................................21

9.0 AUTHORIZATION REQUIREMENTS............................................................................................21

10.0 ANNEXURE (IF ANY)...............................................................................................................22

11.0 Flow Chart Legend..................................................................................................................23

1.0 Document Information

Document Category Business Blueprint Document

1.1 Document Version

Date Version No. Author Change Description

1.2 Document Approval Details

Function Name (Designation) Role Sign & Date

T Sudhir IBM Project Manager

1.3 Reference Document Details (If any)

1.4 Abbreviations Used (If any)

2.0 Business Requirement

The document is applicable for following business verticals of Arvind group:

2.2 Details of Business Requirement

 5 Week Past Sales

*** Changes Version 1.1

*** Changes Version 1.2

2.3 Business Requirement Flow Diagram (If any)

3.0 Business Process Description

3.1 Process Details