You are on page 1of 12

eekly Committed backlog

January 29, 2008 Business Information Warehouse

Weekly Committed Backlog


Technical Design Document
Business Information Warehouse (BIW)

Stream Business Process

Sales & Distribution Backlog

Report Name Requestor Name Business Analyst Author Functional Document Status
[open, in progress, reviewed, finished]

QRY_COMMITTED_BACKLOG_WEEKLY: Weekly Committed backlog Date created Last change 01.29.2008 02.13.2008

In Progress

Change History
Change Date Author Comment
Page 1 of 12

Weekly Committed Backlog

eekly Committed backlog

2008-02-13 2008-01-29 2008-03-17

Added requested Backlog to the report Initial version 0DLV_Block, Requested Backlog for Blocked Orders & Committed Backlog for Blocked Orders added.

Weekly Committed Backlog

Page 2 of 12

eekly Committed backlog

CHANGE HISTORY.....................................................................................................................................1 1 BUSINESS REQUIREMENTS..................................................................................................................4 2.0 CONCEPTUAL DESIGN........................................................................................................................5 3.0 TECHNICAL DESIGN............................................................................................................................6 3.5CUSTOMER EXITS.................................................................................................................................7 4.0QUERY PROPERTIES..........................................................................................................................10 5.0 UNIT TESTING......................................................................................................................................11 6.0 OUTSTANDING QUESTIONS............................................................................................................12

Weekly Committed Backlog

Page 3 of 12

eekly Committed backlog

1 Business Requirements
1.1 Business Process
The Weekly Committed Backlog report provides the Committed backlog and requested backlog figures week wise for the current quarter for consumers belonging to NCSA and EMEA.

1.2 Report Objective


The objective of this report is to provide the Committed and Requested backlog figure week wise for the current quarter.

1.3 Report Content


In the default layout, the report displays the committed and Requested backlog figures week wise for the sales organizations 1101 and 2101.

1.4 Reporting users

1.5 Other Information


There is no candidate query to modify to meet these requirements, therefore, a new query, QRY_COMMITTED_BACKLOG_WEEKLY, will be developed in 04s to meet the weekly committed backlog business need.

1.6 Report Reconciliation


The data from the new report must exactly match the data from the daily BBB committed and requested backlog reports in the BW.

1.7 Report Availability


This report will available as a a) stand-alone Bex query b) Will be sent via information broadcasting to Ajay Birla on every Monday.

1.8 Performance Requirements


According to the Business Requirements, query response times should be between 1 5 minutes, depending on the complexity of the query.

Weekly Committed Backlog

Page 4 of 12

eekly Committed backlog

2.0 Conceptual Design


The following section explains, at a high level, the query design. All the data required for this query will be available via a MultiProvider ZBBB_ITM. This is the default layout of the report generated by this new query.

Weekly Committed Backlog

Page 5 of 12

eekly Committed backlog

3.0 Technical Design


The following sections describe details needed to build the new 04s query QRY_COMMITTED_BACKLOG_WEEKLY, Weekly Committed backlog.

3.1 InfoProvider
Use MultiProvider ZBBB_ITM.

3.2 Rows
Characteristic Fiscal week/year Technical Name T_FISWK1 Display As Key Suppress Result Rows Never

3.3 Columns
Characteristic Sales Organization Technical Name 0SALESORG Display As Key & Text Suppress Result Rows Never

Key Figure Name


Requested Backlog Committed Backlog Committed Backlog >QTR Requested Backlog for blocked orders Committed Backlog for blocked orders

Technical Name
Z_REQBKLG Z_COMBKLG Z_COMOQTR Z_REQBLOCK Z_COMBLOCK

Key Figure Type RKF RKF RKF RKF RKF

Formula

Weekly Committed Backlog

Page 6 of 12

eekly Committed backlog

3.4

Restricted Key figures

Committed Backlog

Requested backlog

3.5

Customer Exits

WHEN 'ZCUR_QTRD'. IF I_STEP = 2. Clear: w_fyear, w_date. w_date = sy-datum - 1.

Weekly Committed Backlog

Page 7 of 12

eekly Committed backlog


CALL FUNCTION 'Z_GET_FISC_QTR' EXPORTING DATE = w_date FISCVAR = 'M0' IMPORTING FISCQTRYR = w_fyear. L_s_range-low = w_fyear. L_s_range-sign = 'I'. l_s_range-opt = 'EQ'. APPEND l_s_range TO e_t_range. Exit. ENDIF.

WHEN 'Z_CRD_LASTDAY'. IF I_STEP = 2. clear : w_date,w_buper,w_qtr,w_gjahr,w_num. LOOP AT i_t_var_range INTO xtab WHERE vnam = 'ZCUR_QTRD'. w_qtr = xtab-low.w_gjahr = w_qtr+0(4).w_num = w_qtr+4(1). case w_num. when 1. w_buper = 003. when 2. w_buper = 006. when 3. w_buper = 009. when 4. w_buper = 012. endcase. CALL FUNCTION 'LAST_DAY_IN_PERIOD_GET' EXPORTING I_GJAHR = w_gjahr I_PERIV = 'M0' I_POPER = w_buper IMPORTING E_DATE = w_date. l_s_range-low = w_date. l_s_range-sign = 'I'. l_s_range-opt = 'EQ'. APPEND l_s_range TO e_t_range. exit.

Weekly Committed Backlog

Page 8 of 12

eekly Committed backlog

endloop. ENDIF.

WHEN 'Z_CMTDT_LSTDT'. IF I_STEP = 2. clear : w_date,w_buper,w_qtr,w_gjahr,w_num. LOOP AT i_t_var_range INTO xtab WHERE vnam = 'ZCUR_QTRD'. w_qtr = xtab-low.w_gjahr = w_qtr+0(4).w_num = w_qtr+4(1). case w_num. when 1. w_buper = 003. when 2. w_buper = 006. when 3. w_buper = 009. when 4. w_buper = 012. endcase. CALL FUNCTION 'LAST_DAY_IN_PERIOD_GET' EXPORTING I_GJAHR = w_gjahr I_PERIV = 'M0' I_POPER = w_buper IMPORTING E_DATE = w_date. l_s_range-low = w_date. l_s_range-sign = 'I'. l_s_range-opt = 'EQ'. APPEND l_s_range TO e_t_range. exit. endloop. ENDIF.

Weekly Committed Backlog

Page 9 of 12

eekly Committed backlog

4.0

Query Properties

Weekly Committed Backlog

Page 10 of 12

eekly Committed backlog

5.0 Unit Testing


The data for this report comes from InfoProvider ZBACK_ORD. For unit testing, this report data may be reconciled with the contents of that InfoProvider: 1. Using LISTCUBE, compare BW report data with LISTCUBE results. several variations and combinations of input variables. 2. Tally the standard weekly committed backlog report with the daily BBB committed and requested backlog report in BW. 3. Execute any additional tests to prove functionality. Run for

Weekly Committed Backlog

Page 11 of 12

eekly Committed backlog

6.0 Outstanding Questions


The report will be used to get the figures only for the current quarter.

Weekly Committed Backlog

Page 12 of 12

You might also like