4.5 Program Documentation

Project Name:	Novartis Enterprise Limited (NEL).
Document Name:	Program Documentation for XXXX
Document ID:	NOVAR_PD01_SD001-C014			Version:	1.0
Prepared by:	XXXX (SD Consultant)	Contact No.	1234	Date:	05.11.01
Reviewed by:	XXXX (Project Manager)	Contact No.	4567	Date:	08.11.01
Approved by:	XXXX (Project Manager)	Contact No.	4567	Date:	09.11.01
Released by:	XXXX(SD Consultant)	Contact No.	1234	Date:	09.11.01

Revision History

Sr. No.	Version No.	Date of Revision	Section Number	Description of Change	Reason for Change	Change made by	reviewed by

SAP_ ABAP_PROGRAM DOCUMENTATION

1. Program Details
Program name:	Reqcpt.htm
Title:	BSP for Displaying – Total CR’s for teams & Applications & the Mandays for development.
Reference Functional Specification:			FS01_CRM_CR990117			Version:	1.0
Deviation from Functional Specification:			NA
Server Name:	E88	Server IP address:		mchh2u9a.mchh.siemens.de		Client:	888
Development class:	/SIE/MNH_2D_ART		Transaction code: (for this program)		ZSD_PACKING
Authorisation Group:			Transport Request:		E88K903478
Program type:	( ) Report Interactive ( ) Report ( ) Standard Modification ( X ) Online program
Characteristics	( ) Drill-down ( ) Push buttons ( ) Sort ( ) Entry files ( ) Others: BSP Application.
Type:	( ) Creation ( X ) Change
Technique:	( ) Report Painter ( ) Report Writer ( ) ABAP Query ( X ) ABAP Program ( ) Info System
Priority:	( X ) high-mandatory ( ) medium-recommended ( ) low-optional
Technical description:	BSP for Displaying – Total CR’s for teams & Applications & the Mandays for development.

1. Selection criteria

Project /SIE/MNH_2DPROJS – TITLE Project No. from /SIE/MNH_2D_CR- PROJECT Project No. To /SIE/MNH_2D_CR- PROJECT Application /SIE/MNH_2D_CR – APPL Team /SIE/MNH_2D_CR – TEAM Date of creation from. /SIE/MNH_2D_CR-ERDAT Date of creation To. /SIE/MNH_2D_CR-ERDAT Request Category /SIE/MNH_2D_CR – CR_TYPE Project type /SIE/MNH_2DPROJS -PRART Requesting Department /SIE/MNH_2D_CR – REQ_DEPT Request Status /SIE/MNH_2D_CR -STATUS You can choose multiple status – out of [Erfasst ] V [Bewertet ] [Freigegeben ] [Konzipiert ] [Realisiert ] Requests Overdue /SIE/MNH_2D_CR -STATUS .Use Hardcoded Options for populating the dropdown1.Yes - Default2.No YES - display all the "overdue" requests For the selection made in the Request Status NO - displayed all the "due" requests For the selection made in the Request Status View Status Team(number of requests)Application(number of requests)Team(number of man days)Application(man days / requests)

2. Proposed Data Gathering / Processing Logic

Data Gathering

Data must be gathered in an table and filtered based on the selection criteria and later displayed in HTML.

Processing Logic

1. Based on the View selection criteria the data is displayed in different formats The views are – 1. Status View [Default] 2. Team (Number of requests) 3. Application (Number of requests) 4. Team (Number of man days) 5. Application (Number of man days) Depending on the selection the output is displayed different table layouts. This function is used to retrieve the data from the multiple selects Application & status and create a “;” delimited string from the same. function buttonclick() For the Default status view we use the internal table GT_Count This table provides us with the data from the /SEI/MNH_2D_CR it also has to look into table /SEI/MNH_2D_STAT to retrieve the MAX time for a particular table depending on which the due and overdue is calculated. gt_count cnt_cr_gesamt cnt_cr_gesamt_due cnt_cr_gesamt_over For displaying the views 2. Team (Number of requests) 3. Application (Number of requests) 4. Team (Number of man days) 5. Application (Number of man days) The internal tables gt_creq & gt_ctreq is used to display the total request per status. The internal table given below is used to retrieve the count per status gt_creq gt_creq–teamappl : Gives the title of the team/application gt_creq-cnt_total : Gives the total count of all the requests gt_creq-cnt_cmpl : Gives the count of all the completed requests gt_creq-cnt_process : Gives the count of all the inprocess requests gt_creq-cnt_overdue : Gives the count of all the requests which are inprocess but overdue gt_creq-cnt_due : Gives the count of all the inprocess requests which are due gt_creq-cnt_rtest : Gives the count of all the requests which are in the testing phase gt_creq-cnt_fa : Gives the count of all the requests which are in fa gt_creq-cnt_hold : Gives the count of all the requests which are on hold gt_creq-cnt_assessed : Gives the count of all the requests which have been assessed. gt_creq-cnt_mandays : Gives the count of the mandays effort required. The internal table given below is used to retrieve the total count for each of the status. gt_ctreq gt_ctreq–teamappl : Gives the title of the team/application gt_ctreq-cnt_total : Gives the total count of all the requests gt_ctreq-cnt_cmpl : Gives the total count of all the completed requests gt_ctreq-cnt_process : Gives the total count of all the inprocess requests gt_ctreq-cnt_overdue : Gives the total count of all the requests which are inprocess but overdue gt_ctreq-cnt_due : Gives the total count of all the inprocess requests which are due gt_ctreq-cnt_rtest : Gives the total count of all the requests which are in the testing phase gt_ctreq-cnt_fa : Gives the total count of all the requests which are in fa gt_ctreq-cnt_hold : Gives the total count of all the requests which are on hold gt_ctreq-cnt_assessed : Gives the total count of all the requests which have been assessed.