Professional Documents
Culture Documents
Ranbaxy: User Requirement Specification
Ranbaxy: User Requirement Specification
LABORATORIES LIMITED
SOP: User requirement Specification (DP Staging)
Document No. SCM_BW_URS_1.0 Effective date:
System Name: BW-DP System Version: 3.1 Release:
SDR/SCR Number: Project Owner Manager: Govind Jaju
Name
Designation
Sign/Date
1. Overview
This URS covers the integration aspects between Demand planning module of
APO and BW. Also document provides the details level on Field definitions for
source data form R/3 and Non R/3
These user specifications cover Integration between DP and BW covers the following:
1. Staging of historical data from legacy systems (R/3 and Non R/3)
1.1 Using the Characteristics lying in the R/3 & Non R/3 Material master for
populating the characteristics.
1.2 Using the attribute lying in the R/3 & Non R/3 Material Master to populate the
Attributes.
1.3 Capture Key figures using transactional data ( R/3 and Non R/3) for the
purpose of Demand forecasting
2. Stage data from external sources like IMS, ORG, and Secondary Sales for the
purpose of display in the Interactive Planning book.
3. Capturing the field inputs and stage them in the BW InfoCube for usage in DP.
4. Staging for Data from legacy systems where there is no transaction history
This document provides how the data (master and transactional) will be staged first in
Business Warehouse by Interfacing with R/3 & Non R/3 and then transferred to Demand
Planning in APO.
1
RANBAXY User Requirement Specification
LABORATORIES LIMITED
SOP: User requirement Specification (DP Staging)
Document No. SCM_BW_URS_1.0 Effective date:
System Name: BW-DP System Version: 3.1 Release:
SDR/SCR Number: Project Owner Manager: Govind Jaju
2. Operational Requirements
Step 1 - Master and transaction data is loaded from R/3 and Non-R/3
transaction system into a BW InfoCube.
Step 3 - Data is loaded into the Planning area from the Infocube present in
APO DP.
Step 4 - After the conclusion of the Planning activity the data is extracted
into another Infocube in BW for backup / reporting.
2
RANBAXY User Requirement Specification
LABORATORIES LIMITED
SOP: User requirement Specification (DP Staging)
Document No. SCM_BW_URS_1.0 Effective date:
System Name: BW-DP System Version: 3.1 Release:
SDR/SCR Number: Project Owner Manager: Govind Jaju
Characteristics
Attributes
Key Figures
Long & Medium text descriptions for every characteristics
Characteristics
Characteristics are planning levels at which data can be sliced and planning results can be
viewed and modified. The Characteristics are grouped as dimensions like Product,
Location and time.
Data Source:
The source of the values of the characteristics will be from R/3 and Ron R/3. Give below
is the source of each of the characteristics and the equivalent field in R/3. For the data
comes from Non R/3, it will be in the Flate file to load directly into BW cubes without
R/3 involvement. The attributes of the data elements from Non R/3 should be same as
R/3.
Geography Dimension
9 Global Global Not relevant for R/3 Should be in the
BW InfoCube
(E.g. Transfer
3
RANBAXY User Requirement Specification
LABORATORIES LIMITED
SOP: User requirement Specification (DP Staging)
Document No. SCM_BW_URS_1.0 Effective date:
System Name: BW-DP System Version: 3.1 Release:
SDR/SCR Number: Project Owner Manager: Govind Jaju
rules)
10 Region Region 1A ZMT_CNTREGION- External Z table.
ZMRG This will different
to DF & API
Planning
11 Sub-region Region 1A ZMT_CNTREGION- External Z table.
ZMSRG This will different
to DF & API
Planning
12 Country IN, India T001-LAND1 Location/Plant
Master
13 Distribution 4105, New Delhi VBRP-WERKS Delivery Plant
Center Depot from Billing
document
14 Extra Geography 99 None None
Characteristic
Customer Dimension
14 Division 2250, CHC VBRP-VKORG Sales Org from
Billing document
15 Customer Group In Division 7000 KNVV-KVGR1 Customer Group 1
91, Mckesson from Customer
Master. Each key
99 (For others) customer relevant
for planning will
have one customer
group specific to
Division
16 Customer In Division 7000 KNA1-KUNNR Payer IDs for
91, Mckesson every customer.
The Planning will
99 (For others) be at the Payer
level
17 Extra Customer 99 None None
Characteristic
In addition to the information, details of accessing the fields can also be found in
Appendix 1.
4
RANBAXY User Requirement Specification
LABORATORIES LIMITED
SOP: User requirement Specification (DP Staging)
Document No. SCM_BW_URS_1.0 Effective date:
System Name: BW-DP System Version: 3.1 Release:
SDR/SCR Number: Project Owner Manager: Govind Jaju
Regular Products
Uploading of characteristics for the existing products is a one time activity for 36 months
history. This is required to create the Characteristic value combination (CVC) in Demand
Planning.
New products created between two planning cycles will be created at the end of the
month before the planning cycle.
New Products
All Products which are launched and are made available in the R/3 product master will
need to be populated in the BW Infocube as well.New product Master data combination
will be available in R/3 table ZMI_CVC_T as per the functional specification in
Appendix 1II
The periodicity of the update of the master data for the new products will be before the
planning cycle. This will ensure that the master data is available for planning during the
next cycle.
Products which are not manufactured in India and not maintained in the R/3 Material
master( All Non R/3 Markets) needs to be collected in a template to be provided by the
Business Warehouse team from Non – R/3 markets.
The frequency of this upload will follow the same frequency of the regular products
which are sourced from India.
Attributes
Attributes will be made available in the R/3 Material master in the following fields.
These would be used to populate or upload to the respective Attributes attached to the
Local code (SKU Code). The frequency of upload of this document will be the same as
the characteristics.
5
RANBAXY User Requirement Specification
LABORATORIES LIMITED
SOP: User requirement Specification (DP Staging)
Document No. SCM_BW_URS_1.0 Effective date:
System Name: BW-DP System Version: 3.1 Release:
SDR/SCR Number: Project Owner Manager: Govind Jaju
field)
1 Sales Pack Size S10 MVKE-VRKME Sales Unit. Sales
Pack Unit will be only
one at the market
level. SAP R/3 will be
taken care to avoid diff
sales pack at Dist
channel.
2 Status Regular, P1, … MVKE-MVGR4 Material Group 4.
P7 Division
dependent
3 Regulatory Approved MVKE-MVGR2 Material Group 2.
Division
dependent
4 Product Class A, B, C etc. MVKE-MVGR3 Material Group 3.
Division
dependent
5 Currency INR, USD Country Planning Currency
Currency from pertaining to
country config in Country.
R/3
V_T001-WAERS
6 Combo Molecule Cephalexin + MVKE-PRODH 5 level Product
Cefaclour hierarchy.
7 Dummy Attribute 99 None None
In addition to the information, details of accessing the fields can also be found in
Appendix 1.
6
RANBAXY User Requirement Specification
LABORATORIES LIMITED
SOP: User requirement Specification (DP Staging)
Document No. SCM_BW_URS_1.0 Effective date:
System Name: BW-DP System Version: 3.1 Release:
SDR/SCR Number: Project Owner Manager: Govind Jaju
InfoCubes
This section of the document addresses key design points pertaining to InfoCubes.
Number of InfoCubes
The data that needs to be sourced from transaction / external system via BW are either
available on a daily basis or only at a monthly basis.
Exchange Rate
7
RANBAXY User Requirement Specification
LABORATORIES LIMITED
SOP: User requirement Specification (DP Staging)
Document No. SCM_BW_URS_1.0 Effective date:
System Name: BW-DP System Version: 3.1 Release:
SDR/SCR Number: Project Owner Manager: Govind Jaju
Nine InfoCubes will be used to manage the data between DP and BW. The reason for
using nine InfoCubes is primarily to segregate the update frequency, Hierarchy Level and
source systems to these cubes. The Info cube 1 will be used to update only Master data
using MPOS and other cubes will be loaded into the planning area depending on the
frequency at which it gets uploaded using Load planning area. Attached is the document
of Infocubes
The detailed design in terms of the characteristics and the key figures for each of the cube
has been enclosed
8
RANBAXY User Requirement Specification
LABORATORIES LIMITED
SOP: User requirement Specification (DP Staging)
Document No. SCM_BW_URS_1.0 Effective date:
System Name: BW-DP System Version: 3.1 Release:
SDR/SCR Number: Project Owner Manager: Govind Jaju
Key Figures
Key figures that will be sourced from the Business warehouse application will be divided
into two categories.
Transaction data from Legacy systems
External data like IMS and Secondary sales
The list of key figures that are required to be staged in BW and their frequency of upload
is detailed in in the key fugure list attachments.
9
RANBAXY User Requirement Specification
LABORATORIES LIMITED
SOP: User requirement Specification (DP Staging)
Document No. SCM_BW_URS_1.0 Effective date:
System Name: BW-DP System Version: 3.1 Release:
SDR/SCR Number: Project Owner Manager: Govind Jaju
Day of Month/ Day of Week Num Weekly Proportion Monthly Daily Proportion Monthly % Daily Demand Weekly Demand
Month Year Week (Month Base) % Forecast %
(5 day week)
2500 94.85%
10
RANBAXY User Requirement Specification
LABORATORIES LIMITED
SOP: User requirement Specification (DP Staging)
Document No. SCM_BW_URS_1.0 Effective date:
System Name: BW-DP System Version: 3.1 Release:
SDR/SCR Number: Project Owner Manager: Govind Jaju
Characteristics “Customer” and “Customer Groups” will be used by certain countries like
UK and US for the purpose of forecasting at a SKU + Key account level.
Only a small number (Key accounts) of the customers will be mapped and the rest of
them will be bundled together as one group (customer group 99). This small number of
key accounts is however subject to change over time and the data in the BW / DP needs
to be managed accordingly.
In the illustration above, the key customers A and B are mapped separately as customers
while customers C to F are grouped together as one. This will facilitate working on key
accounts separately and grouping others in one customer group.
Over time the customers will either become key accounts or will fall in the group which
is a cluster of all the customers. This will be handled by changes in the master data in
R/3. The following illustration captures this scenario.
In the above example, Customer B has been merged into the common group and
Customer D has now become a key customer at which planning will be carried out.
These fields are available in the R/3 product master and will map exactly as illustrated
above. As and when the customer groups are changed in the R/3 material master, BW
will pick the master data fields of the customer groups.
11
RANBAXY User Requirement Specification
LABORATORIES LIMITED
SOP: User requirement Specification (DP Staging)
Document No. SCM_BW_URS_1.0 Effective date:
System Name: BW-DP System Version: 3.1 Release:
SDR/SCR Number: Project Owner Manager: Govind Jaju
Over a period of time the individual Key accounts will change and the key
accounts clubbed together also will change in terms of its composition.
12
RANBAXY User Requirement Specification
LABORATORIES LIMITED
SOP: User requirement Specification (DP Staging)
Document No. SCM_BW_URS_1.0 Effective date:
System Name: BW-DP System Version: 3.1 Release:
SDR/SCR Number: Project Owner Manager: Govind Jaju
The key figures required for this purpose of making it available in demand planning
differs in certain geographies and the details are indicated below;
13
RANBAXY User Requirement Specification
LABORATORIES LIMITED
SOP: User requirement Specification (DP Staging)
Document No. SCM_BW_URS_1.0 Effective date:
System Name: BW-DP System Version: 3.1 Release:
SDR/SCR Number: Project Owner Manager: Govind Jaju
Data Archiving
After the completion of the planning run, the planning inputs provided by each of the
entities need to be extracted to a BW InfoCube from APO Infocube.
This is to facilitate a backup strategy in the event of a loss of planning data and reporting
on the forecasting key figures. The scope of archiving would include all the key figures
that are present in the live-cache. The key figures present in the InfoCube do not need to
be backed up as they are anyway sourced from the InfoCube in BW.
List of key figures that need to be archived from each of the planning areas are the ones
that are present in the live cache. This means every key figure other than the ones staged
by BW needs to be archived.
The same concept holds true for API Planning area as well.
14
RANBAXY User Requirement Specification
LABORATORIES LIMITED
SOP: User requirement Specification (DP Staging)
Document No. SCM_BW_URS_1.0 Effective date:
System Name: BW-DP System Version: 3.1 Release:
SDR/SCR Number: Project Owner Manager: Govind Jaju
There will be two Z tables ZBW_LOC_CONFIG & ZBW_LOCALCODE for maintaining Local
codes. If the market is planning based on some legacy code, it will be populated in table
ZBW_LOC_CONFIG. If the market plans at the SAP material level, then the local code will be
prefix with country and division in the second table ZBW_LOCALCODE.
Based on the country key from customer Master, the region and sub-region can be
extracted from the table ZMT_CNTREGION. This will be picked up based on the
material types. For finished goods & API Planning we will have a different Region &
Sub-regions.
Even though the customer group 1 fields available from the Billing table, it is advisable
to bring the customer group 1 field from customer Master table KNVV-KVGR1 so that if
there is a change in the customer group1, it will be taken care of the past records also for
realignment of CVS in BW and APO
1.4 Location:
Location will be picked up from T000 Table. Location idenfitification for CVC
generation will be passed on the material master availability in sales org level in R/3 .
( Division level as per APO terminology)
Based on the company code from Billing table VBRK-BUKRS, Currency needs to be
picked up from V_T001-WAERS and the country can be picked up from V_T001-
LAND1
15
RANBAXY User Requirement Specification
LABORATORIES LIMITED
SOP: User requirement Specification (DP Staging)
Document No. SCM_BW_URS_1.0 Effective date:
System Name: BW-DP System Version: 3.1 Release:
SDR/SCR Number: Project Owner Manager: Govind Jaju
From the table V_T179-PRODH , the first 13 digit ( level 5 ) 0100100100204 defines
the Molecule and the first 16 digit ( level 6) 0100100100204001 will provide the value of
Brand and the 18 digit code ( level 7 ) 010010010020400101 will provide the Dosage
form.
At the market level, the major molecule will be picked up from Z table ZMT_MATMOL
directly. This table will hold both information about major and combo molecule.
1.7 Strength
First pick up the Pack size from MVKE-VRKME and then go to T006A-MSEHL to get
the description. BW will need to keep both the unit and description but only unit will be
moved to APO for planning.
1.9 Attributes:
For all the Attributes (product status, Sales Pack unit, and Regulatory and Division
class) system will filter the materials based on the Sales Org status (MVKE-VMSTA)
which has field values 05, 11, 91 & 92. This can happen between BW & APO for CVC
generation. Ranbaxy requires only active CVC for planning. Any materials has
discontinued status is not required for APO Planning.
Primary pack will be directly picked from R/3 material master at the market level
from MVKE-MVGR1
16
RANBAXY User Requirement Specification
LABORATORIES LIMITED
SOP: User requirement Specification (DP Staging)
Document No. SCM_BW_URS_1.0 Effective date:
System Name: BW-DP System Version: 3.1 Release:
SDR/SCR Number: Project Owner Manager: Govind Jaju
2 Net Sales Quantity This figure is derived by netting out the Saleable Stocks Quantity
returned by the market (Market Returns) from the Gross Invoiced
Sales Quantity, during the same bucket.
The net invoiced sale indicates the net stock which has been
invoiced to the market in that bucket.
This includes -
1. Goods issued under FRS: Free Replacement Scheme
document. Stocks are issued in to settle claims of stockists /
distributors
2. Samples stocks being created out of saleable stock
3. Stocks for trials distributed out of saleable stock
8 Short Dated Qty Sales Quantity sold to salvage stocks from expiry write-off in a time
bucket. The stocks with residual shelf life, may not be acceptable
to the normal sales channel, & may be sold to select distributors /
institutions at a discount / special terms. Such sales are termed as
Short dated sales.
9 Net Sales Orders Quantity The Sales Order history relevant to each bucket at SKU level.
These are sum total of customer orders raised towards Ranbaxy
in that country / location. These sales orders will be the sum of
serviced & un-serviced orders, so as to reflect the SKU demand.
10 Live Back Orders Sales Orders which were to be seviced in the last month, but
could not be serviced for want of stocks and are valid to be
serviced in the current month.
17
RANBAXY User Requirement Specification
LABORATORIES LIMITED
SOP: User requirement Specification (DP Staging)
Document No. SCM_BW_URS_1.0 Effective date:
System Name: BW-DP System Version: 3.1 Release:
SDR/SCR Number: Project Owner Manager: Govind Jaju
14 Secondary Sales Secondary Sales data from the Market which indicates the SKU-
wise sales at the same level of UOM and geographical level at
which forecasting is being done.
The bucket too should be the same for the past history
15 Market Data in Sales Packs Market data in Sales Packs will be given by Country based on the
Characteristic levels identified
The data in Excel format will be uploaded by BW
16 Market Data (KG) Market data of API in Kg (as per label claim) as in DF Sales pack
18 Estimated primary Sales An estimation of Primary Sales based on the stockist' / Dealer'
stock levels, sales in the past month & the status (local or
upcountry)
19 Adjusted History History Used for Forecasting after manual outlier correction in a
data view.
18
RANBAXY User Requirement Specification
LABORATORIES LIMITED
SOP: User requirement Specification (DP Staging)
Document No. SCM_BW_URS_1.0 Effective date:
System Name: BW-DP System Version: 3.1 Release:
SDR/SCR Number: Project Owner Manager: Govind Jaju
21 Final Forecast Previous Cycle Final Forecast Generated in the last Planning Cycle
22 Final Forecast % Deviation Hit Ratio (FF vs Actuals). This will be calculated as (A/FF)
Accuracy computed based on Actuals of M1 generated in M0
24 Base Forecast % Deviation Hit Ratio (BF vs Actuals). This will be calculated as (A/BF)
25 Sales Head Forecast Previous Sales Head Forecast from Previous month
Cycle
26 Sales Head Forecast % Deviation Hit Ratio (SHF vs Actuals). This will be calculated as (A/SHF)
27 SC Head Forecast Previous cycle Supply Chain Head Forecast from Previous month
19
RANBAXY User Requirement Specification
LABORATORIES LIMITED
SOP: User requirement Specification (DP Staging)
Document No. SCM_BW_URS_1.0 Effective date:
System Name: BW-DP System Version: 3.1 Release:
SDR/SCR Number: Project Owner Manager: Govind Jaju
30 Statistical Forecast Previous Statistical forecast generated by the system in the previous cycle
Cycle
33 Statistical Forecast (KG) Statistical Forecast generated by the system as per forecast
profile in Kg of API. KG conversion will be based on strength as
mentioned on Sales Pack/ Label Claim
34 Base Forecast Base Forecast is generated by the RDP in Sales Pack on monthly
basis
20
RANBAXY User Requirement Specification
LABORATORIES LIMITED
SOP: User requirement Specification (DP Staging)
Document No. SCM_BW_URS_1.0 Effective date:
System Name: BW-DP System Version: 3.1 Release:
SDR/SCR Number: Project Owner Manager: Govind Jaju
38 Final Forecast Final consensus forecast in Sales UOM after Business Review
21
RANBAXY User Requirement Specification
LABORATORIES LIMITED
SOP: User requirement Specification (DP Staging)
Document No. SCM_BW_URS_1.0 Effective date:
System Name: BW-DP System Version: 3.1 Release:
SDR/SCR Number: Project Owner Manager: Govind Jaju
44 Final Forecast (Value) Business Approver's Final Forecast in Currency after Business
Review
45 Release Base Forecast Base forecast which will be released to Sales Head after RDP has
generated the Base forecast.
For US - the same is released to the Supply Chain Head
46 Release SCH Forecast Suply Chain Head' forecast which will be released to Sales Head
(only for US)
47 Release Sales Head Forecast Sales Head forecast which will be released to Business Approver
48 Release Final Forecast Final forecast which will be released for Weekly Split & Release to
SNP
22
RANBAXY User Requirement Specification
LABORATORIES LIMITED
SOP: User requirement Specification (DP Staging)
Document No. SCM_BW_URS_1.0 Effective date:
System Name: BW-DP System Version: 3.1 Release:
SDR/SCR Number: Project Owner Manager: Govind Jaju
51 SNP Proportional Factor Split into Calendar Weeks from monthly forecast for release to
SNP
53 Forecast Scenario (KG) New Product Forecast in KG derived as percentage of IMS data
23
RANBAXY User Requirement Specification
LABORATORIES LIMITED
SOP: User requirement Specification (DP Staging)
Document No. SCM_BW_URS_1.0 Effective date:
System Name: BW-DP System Version: 3.1 Release:
SDR/SCR Number: Project Owner Manager: Govind Jaju
24
RANBAXY User Requirement Specification
LABORATORIES LIMITED
SOP: User requirement Specification (DP Staging)
Document No. SCM_BW_URS_1.0 Effective date:
System Name: BW-DP System Version: 3.1 Release:
SDR/SCR Number: Project Owner Manager: Govind Jaju
65 Field Forecast Previous Cycle Field Forecast from the previous planning cycle
67 Net Shipment Qty Net Shipment Qty will be used to minus net shipments from the
forecast before releasing the forecast to supply
68 KG Conversion to API Used for calculating the KG value of the forecsast, where
applicable
25
RANBAXY User Requirement Specification
LABORATORIES LIMITED
SOP: User requirement Specification (DP Staging)
Document No. SCM_BW_URS_1.0 Effective date:
System Name: BW-DP System Version: 3.1 Release:
SDR/SCR Number: Project Owner Manager: Govind Jaju
71 Adjusted History – IMS Adjusted IMS history will be used to run statistical forecasting for
new products. This KF will also then allow like modellin
functionality to be used.
74 Weekly Split Editable Weekly Split Ratio which is editable, before releasing the final
forecast to Supply
26
RANBAXY User Requirement Specification
LABORATORIES LIMITED
SOP: User requirement Specification (DP Staging)
Document No. SCM_BW_URS_1.0 Effective date:
System Name: BW-DP System Version: 3.1 Release:
SDR/SCR Number: Project Owner Manager: Govind Jaju
Functional Description
The objective of this document is to create master data combination in R/3 for the
purpose of generating CVC for APO Demand planning. The master combination
will be populated into Z table initially for the past 12 months and thereafter every 2
weeks.
BW will pick this Masters from the Z table mentioned above for extracting it into
their info cube for new CVC Creation and finally this info cube will populate the
APO info cube which will finally create CVC in Demand planning
Following is the list of Characteristics & logic required from various sources in
R/3.
27
RANBAXY User Requirement Specification
LABORATORIES LIMITED
SOP: User requirement Specification (DP Staging)
Document No. SCM_BW_URS_1.0 Effective date:
System Name: BW-DP System Version: 3.1 Release:
SDR/SCR Number: Project Owner Manager: Govind Jaju
28
RANBAXY User Requirement Specification
LABORATORIES LIMITED
SOP: User requirement Specification (DP Staging)
Document No. SCM_BW_URS_1.0 Effective date:
System Name: BW-DP System Version: 3.1 Release:
SDR/SCR Number: Project Owner Manager: Govind Jaju
Product Dimension
1 SAP Material 1002851 MARA- The material codes are populated
Code MATNR into this Ztable thru two different
ways.
29
RANBAXY User Requirement Specification
LABORATORIES LIMITED
SOP: User requirement Specification (DP Staging)
Document No. SCM_BW_URS_1.0 Effective date:
System Name: BW-DP System Version: 3.1 Release:
SDR/SCR Number: Project Owner Manager: Govind Jaju
in MVKE-MVGR3.
Geography Dimension
1 DC code 1310 MARC - Based on the active sales org, all
MATNR the plants assigned to the sales org
will be picked up from table
TVKWZ-WERKS. Then system
will check the availability of the
above material in those plants from
MARC-MATNR. If available,
then populate the DC code for the
combination of sales org, customer
group, material & plant. If the
material has deletion status in
MARC- LVORM, don’t populate.
If the material is exists in more
than one plant from the above
plants for a specific sales org, then
create a new line item with the
sales org, customer group, and
material & Plant combination.
Note:
30
RANBAXY User Requirement Specification
LABORATORIES LIMITED
SOP: User requirement Specification (DP Staging)
Document No. SCM_BW_URS_1.0 Effective date:
System Name: BW-DP System Version: 3.1 Release:
SDR/SCR Number: Project Owner Manager: Govind Jaju
Now check for those materials created in the past 12 months where the customer
group is blank, then populate those line items with customer group 99. When ever
the line under go changes, please change the date stamp.
31