542785170.

doc 1/56

Project System Configuration Tasks

For the following Project System configuration tasks:

o Log on to the target system server, choose the 010 client

o On the” SAP Easy Access” page, enter/invoke the SPRO transaction,
o On the “Customizing: Execute Project” page, click on the “SAP Reference IMG” button

(A.) Project System Configuration Check List:

(1.) Create “User Status” Profile
o Menu path: Project System, Structures, Operative Structures, Work Breakdown Structure (WBS), WBS User Status.
Then, click on the “Create Status Profile” IMG activity
o Click on the “new entry” button, and add the following Status Profiles:
o Status Profile Text
 DPSC1 DPS Client Project Status Prof
 DPSI1 Internal Project User Status
o For the DPSC1 status profile, add the following “user statuses”:
o Status Status Short Init Lowest Highest Posn Priority
o Number Text Status Status# Status#
o 1 INIT Initial Status  1 6 1 1
o 2 NOTF Notification Sent  2 3 1 1
o 3 APRE Approval Requested  2 4 1 1
o 4 APVD Approved  3 5 1 1
o 5 CLRQ Close Requested  1 6 1 1
o 6 APCL Close Approved  5 7 1 1
o 7 CLPR Close In Progress  6 8 1 1
o 8 CLSD Closed  1 8 1 1

o On Sept 8th, 2004, we were asked to change the values of the “Lowest Status Number” and Highest Status Number”
attributes as follows:
o Status Status Short Init Lowest Highest Posn Priority
o Number Text Status Status# Status#
o 1 INIT Initial Status  1 8 1 1
o 2 NOTF Notification Sent  1 8 1 1
o 3 APRE Approval Requested  1 8 1 1
o 4 APVD Approved  1 8 1 1
o 5 CLRQ Close Requested  1 8 1 1
o 6 APCL Close Approved  1 8 1 1
o 7 CLPR Close In Progress  1 8 1 1
o 8 CLSD Closed  1 8 1 1

o On Nov 1st, 2004, (ref. Defect #742), we were asked to delete the “CLPR” user status (from the DPSC1 status profile),
re-number the “CLSD” from “8” to “7”, and change the “highest status nbr” from “8” to “7”.
o Status Status Short Init Lowest Highest Posn Priority
o Number Text Status Status# Status#
o 1 INIT Initial Status  1 7 1 1
o 2 NOTF Notification Sent  1 7 1 1
o 3 APRE Approval Requested  1 7 1 1
o 4 APVD Approved  1 7 1 1
o 5 CLRQ Close Requested  1 7 1 1
o 6 APCL Close Approved  1 7 1 1
o 7 CLSD Closed  1 7 1 1

o After adding the above 8 user statuses, double-click on each status, and set the Business Transaction “influences”
exactly the same way as the corresponding setup in the most recently configured system, except for DPSC1/INIT,
“Actual Activity Allocation” and “Actual Inverse Activity Allocation”, which should be set to “Forbidden”.
/conversion/tmp/activity_task_scratch/542785170.doc 1/56
542785170.doc 2/56

o On Sept 1st 2005 - Added new user status CANC (which is a copy of CLSD) to indicate when a WBS set-up is canceled
or rejected.

o For the DPSI1 status profile, add the following “user statuses”:
o Status Status Short Init Lowest Highest Posn Priority
o Number Text Status Status# Status#
o 1 INIT Initial Status  1 2 1 1
o 2 NOTF Notification Sent  2 3 1 1
o 3 CLRQ Close Requested  3 4 1 1
o 4 CLSD Closed  1 4 1 1
o After adding the above 4 user statuses, double-click on each status, and set the Business Transaction “influences”
exactly the same way as the corresponding setup in SBX/010.
o On Nov. 1st, 2004 (ref. Defect #742), we were asked to go into user statuses “CLRQ” & “APCL” (for Status Profile
DPSC1), and set the “FI:Postings” business transaction to “forbidden”. This was accomplished by double-clicking on
the user status, finding the FI:Postings txn, and clicking in the “forbidden” button. The CLRQ user status did not
contain a bus txn for FI:Postings, so it was added by clicking on the “new entries” toolbar button. We were also asked
to go into user status CLRQ (for system status DPSI1), and make the FI:Postings bus txn “forbidden”.
o On Nov. 11th, 2004, (ref. Defect #742) we were informed by Carlton that the Project Close Request process is not
working and the reason is - we have disallowed FI postings for user status CLRQ within the DPSC1 status profile. The
custom Project Close request program posts some FI transactions in the process and CLRQ is not allowing it. We will
need to allow FI postings for CLRQ for DPSC1.The settings for APCL are fine and need no change.
o On Sept 1st 2005 - Added new user status CANC (which is a copy of CLSD) to indicate when a WBS set-up is canceled
or rejected.
o We were also asked to revise the “lowest status” values and “highest status” values as follows:
o Status Status Short Init Lowest Highest Posn Priority
o Number Text Status Status# Status#
o 1 INIT Initial Status  1 4 1 1
o 2 NOTF Notification Sent  1 4 1 1
o 3 CLRQ Close Requested  1 4 1 1
o 4 CLSD Closed  1 4 1 1

(2.) Define Partner Determination Procedures and Roles

o Menu path: Project System, Structures, Operative Structures, Work Breakdown Structure (WBS). Then, click on the
“Define Partner Determination Procedures and Roles” IMG activity.
o Double-click on “Definition of Partner Roles” (or single-click and then click “choose”). In addition to the standard
SAP-delivered partner definitions, add the following 19 Deloitte-specific partner definitions:
Funct Name NoTy Unique HighPartFunct
Z2 Advisory Partner PE 
Z3 Project Partner PE 
Z4 Project Manager PE  Z3
Z5 Project Controller PE 
Z6 Billing Partner PE 
Z7 Billing Manager PE  Z6
Z8 Delegate PE 
Z9 Billable Resource PE 
ZA Approving Partner PE 
ZB Functional Lead PartnrPE 
ZC Cost Center Leader PE 
ZD Alliance Partner KU  (renamed to Alliance Vendor on
2/15/2005)
ZE Investment Partner KU  (renamed to Equity Investor on
2/15/2005)
ZF Project Sponsor PE 
ZG Division Manager PE 
ZH Additional Mgmt PE 
ZI Intl Contact Person AP 
ZK Senior Staff PE 
ZL Financial Analyst PE 

/conversion/tmp/activity_task_scratch/542785170.doc 2/56
542785170.doc 3/56

o Double-click on “Define Partner Determination Procedures and Partner Roles” (or single-click and then click “choose”).
Click on New Entries and add the following Partner Determination Procedures:
o ParPr Description
o DPS1 DPS Partner Det Proc
o DPS2 Mgmt Projects
o DPS3 Firm and Local Project
o DPSP DPS PRD Partner Det Proc (added 9/20/2004)
o After the above Partner Procedures have been added, set up the Partner Functions in Procedure” for each procedure by
highlighting the Partner Procedure, then double-clicking on the Partner Functions in Procedure” in the ‘dialog structure’
area to the left of the screen. Populate the partner procedures as follows:
o PartnDet.Proc. DPS1
Funct Name No Change Mandatory Unique
Z3 Project Partner   
Z4 Project Manager   
Z5 Project Controller    (added on 8/25/2004)
Z6 Billing Partner   
Z7 Billing Manager   
ZD Alliance Partner   
ZE Investment Partner    (ZE ptnr function removed from DPS1 on
6/13/2005 per TD#1842)
ZK Senior Staff   

PartnDet.Proc. DPS2
Funct Name No Change Mandatory Unique
ZC Cost Center Leader   
ZC Financial Analyst    (added on 5/9/2005, TD#1349)

PartnDet.Proc. DPS3
Funct Name No Change Mandatory Unique
Z4 Project Manager   
Z5 Project Controller   
ZC Cost Center Leader   
ZC Financial Analyst    (added on 5/9/2005, TD#1349)

PartnDet.Proc. DPSP (added on 9/20/2004)

Funct Name No Change Mandatory Unique
Z3 Project Partner   
Z4 Project Manager   
Z5 Project Controller   
ZD Alliance Partner   
ZE Investment Partner    (ZE ptnr function removed from DPSP on
6/13/2005 per TD#1842)
ZK Senior Staff   

(3.) Create Project Types

o Menu path: Project System, Structures, Operative Structures, Work Breakdown Structure (WBS). Then, click on the
“Create Project Types for WBS Elements” IMG activity.
o As of Sept 2004, the following 35 project types have been defined. Click on “New Entries” if others are needed. (We
have been informed that “01 Structured” and “02 Unstructured” will not be included in the production release of
SAP/DPS as this legacy functionality is being discontinued going forward).

Typ Description
CE Client Engagements
CM Client Products
CP Client Engagements with PRD
DE Deloitte Internal Chargeable Proj (XYZ) (name chgd to Project B/w Deloitte U.S. Entities
(XYZ) on 4/28/2005, RICE2081, CR277, Project Terminology changes, SPDK963903)
FA Firm
FB Firm - Practice Development (PRD)
FC Firm - Continuing Education (CED)
FD Firm - Marketing and Promotional (MKT)
FE Firm - Counseling & Personnel Devl (CNS)
FF Firm - Professional Activities (PRA)
/conversion/tmp/activity_task_scratch/542785170.doc 3/56
542785170.doc 4/56

FG Firm - General & Administration (GAA)

FH Firm - Legal (LGL)
FI Firm - Recruiting (REC)
FK Firm - Volunteer Non-Profit (VLT)
LA Local
LB Local - Practice Development (PRD)
LC Local - Continuing Education (CED)
LD Local - Marketing & Promotional (MKT)
LE Local - Counseling & Personnel Dev (CNS)
LF Local - Professional Activities (PRA)
LG Local - General & Administration (GAA)
LH Local - Legal (LGL)
LI Local - Recruiting (REC)
LK Local - Volunteer Non-Profit (VLT)
LZ Local Project with no cost transfers
MA Management
MB Management - Practice Development (PRD)
MC Management - Continuing Education (CED)
MD Management-Marketing & Promotional (MKT)
ME Management-Counseling & Prsnnl Dev (CNS)
MF Management-Professional Activities (PRA)
MG Management-General & Administration(GAA)
MH Management - Legal (LGL)
MI Management - Recruiting (REC)
MK Management - Volunteer Non-Profit (VLT)
o In April 2005, the following two project types were added for the Federal Practice project (refer to RICE id# 2026) and
released for transport (SPDK963272):
 CF Client Federal Practice Engagements
 ML Management-Fed Pract Entertainment (ETM)
o On 2005/05/18, per DPS Re-Plan Change Request #15, project type ML was removed and released for transport
(SPDK964487):
 DELETED ML Management-Fed Pract Entertainment (ETM)

(4.) Define Parameters for WBS Scheduling

o Menu path: Project System, Dates, Date Planning in WBS. Then, click on the “Define Parameters for WBS
Scheduling” IMG activity.
o The following two scheduling profiles have been defined, and need to be present on the initial “Control Parameters for
WBS Scheduling Overview” screen:
o Profile Description
o DPSC1 DPS SCHEDULING PROFILE
o ZDDT Deloitte & Touche WBS Scheduling Profile
o Press enter if profiles have been added, or else proceed to highlight each profile one at a time, click on the “Details”
button, and add the following info:
o DPSC1 (see illustration below)
Scheduling Type [1 Forwards]
Start in Past [5]
Schedul. Method [WBS Determine Dates]
 Autom. Schedul.

/conversion/tmp/activity_task_scratch/542785170.doc 4/56
542785170.doc 5/56

o ZDTT (see illustration below)

Scheduling Type [1 Forwards]
Start in Past [999]
Schedul. Method [WBS Determine Dates]

/conversion/tmp/activity_task_scratch/542785170.doc 5/56
542785170.doc 6/56

(5.) Specify Graphic Profile for WBS Date Planning

o Menu path: Project System, Dates, Date Planning in WBS. Then, click on the “Specify Graphic Profile for WBS Date
Planning” IMG activity.
o On the “Settings for Hierarchy Graphic/Time Scheduling” Detail screen, add the following items (see illustration
below):
o Time schd. prof [DPSC1] [DPS SCHEDULING PROFILE]
o Display
Display Options [1]
Display Options [1]
 Act./WBS Display

/conversion/tmp/activity_task_scratch/542785170.doc 6/56
542785170.doc 7/56

(6.) Create Project Profiles

o Menu path: Project System, Structures, Operative Structures, Work Breakdown Structure (WBS). Then, click on the
“Create Project Profiles” IMG activity.
o Make sure the following project profiles have been defined. If not, click on “New Entries” and add as necessary.
o Project Description
o Profile
o General profile (model)
o DPSC1 DPS Client Project Profile
o DPSC2 DPS US Intra-Firm (XYZ) Profile (name chgd to Project B/w Deloitte U.S. Entities (XYZ)
on 4/28/2005 RICE2081, CR277, Project Terminology changes, SPDK963903)
o DPSC3 DPS Client PRD Project Profile
o DPSC5 DPS Client Federal Practice Profile (added April 2005, see note below)
o DPSC4 DPS Product Project Profile
o DPSIF DPS Firm and Local Project Profile
o DPSIP DPS Management Project Profile
o Z000001 D&T Standard Profile
o After the project profile entries have been defined, “highlight” (one at a time) each of the Deloitte-specific profiles listed
above in blue, click on the “details” icon, and review, compare and update where needed the various attributes on the
four tabs (‘Control’, ‘Organization’, ‘Planning Board’, ‘Controlling’). Use the most recently configured system as the
benchmark for comparison.
o In April 2005, the following new project profile was added for the Federal Practice project (see RICE ID#2026) and
released for transport (SPDK963272). The profile was modeled after DPSC1.
o DPSC5 DPS Client Federal Practice Profile
o On 8/1/2005, the company code entry for DPSC5 was cleared for TD#3477. Request #SPDK966734.
o Also, please note, as of August 2005, it has been decided to “clear” the company code entries for all project profiles to
allow subsequent client projects to be created in any company code, and not be restricted to what is pre-defined in the
project profile.

/conversion/tmp/activity_task_scratch/542785170.doc 7/56
542785170.doc 8/56

(7.) Create layout of WBS Element Screens (Internal Projects only)

o Menu path: Project System, Structures, Operative Structures, Work Breakdown Structure (WBS ), User Interface
Settings, Layout of WBS Element Detail Screens. Then, click on the “Define Layout of WBS Element Detail Screens”
IMG activity.
o Click on “New Entries” and add the following items:
Project Act. Tab Tab Page Icon Active 1st Tab Dtl Screen 1
Profile Cat PageID Title Page
DPSIF * TAB01 Project Data icon_dispo_level   2
DPSIF * TAB02 Created/updated by icon_system_administrator   7
DPSIF * TAB03 Org data icon_ppe_assy_head   5
DPSIF * TAB06 Deloitte Data icon_simulate   19
DPSIP * TAB01 Project Data icon_dispo_level   2
DPSIP * TAB02 Created/updated by icon_system_administrator   7
DPSIP * TAB03 Org Data icon_ppe_assy_head   5
DPSIP * TAB06 Deloitte Data icon_simulate   19
o After adding the above entries, then click each one individually, click the “details” icon, then fill in the fields with the
same values/info as found in the most recently configured environment.
o On 10/28/2004, we received a request from Jeff Gibbs to add the above 4 tabs to the following 4 external project (i.e.
“client”) project profiles: DPSC1, DPSC2, DPSC3, DPSC4 (ref. Test Director defect #743, transport request
SPDK960811).
Project Act Tab Tab Page Icon Active 1st Tab Dtl Screen 1
Profile Cat PageID Title Page
DPSC1 * TAB01 Project Basic Data icon_dispo_level   2
DPSC1 * TAB02 Created/Updated by icon_system_administrator   7
DPSC1 * TAB03 Org Data icon_ppe_assy_head   5
DPSC1 * TAB06 Deloitte Data icon_simulate   19
DPSC2 * TAB01 Project Basic Data icon_dispo_level   2
DPSC2 * TAB02 Created/Updated by icon_system_administrator   7
DPSC2 * TAB03 Org Data icon_ppe_assy_head   5
DPSC2 * TAB06 Deloitte Data icon_simulate   19
DPSC3 * TAB01 Project Basic Data icon_dispo_level   2
DPSC3 * TAB02 Created/Updated by icon_system_administrator   7
DPSC3 * TAB03 Org Data icon_ppe_assy_head   5
DPSC3 * TAB06 Deloitte Data icon_simulate   19
DPSC4 * TAB01 Project Basic Data icon_dispo_level   2
DPSC4 * TAB02 Created/Updated by icon_system_administrator   7
DPSC4 * TAB03 Org Data icon_ppe_assy_head   5
DPSC4 * TAB06 Deloitte Data icon_simulate   19
o After adding the above entries, then click each one individually, click the “details” icon, then fill in the fields with the
same values/info as in the internal project profile tabs.
o In April 2005, the following new tabs were added for the Federal Practice project (see RICE ID#2026) and released for
transport (SPDK963272).
DPSC5 * TAB01 Project Basic Data icon_dispo_level   2
DPSC5 * TAB02 Created/Updated by icon_system_administrator   7
/conversion/tmp/activity_task_scratch/542785170.doc 8/56
542785170.doc 9/56

DPSC5 * TAB03 Org Data icon_ppe_assy_head   5

DPSC5 * TAB06 Deloitte Data icon_simulate   19

o Please note that there is a current known bug in SAP that does not allow adds/changes/deletes
to these tabs to be transported without manual intervention. As a result of this limitation,
we have been asking Erik Horsman to help get these types of changes transported. As of
2005/05/18, Erik is preparing a special procedure to be distributed to the Master Data Team for
getting these types of changes effectively transported.
 As of May 2007, here are the latest instructions for ‘modifying’ a transport (that contains configuration done
in the Define Layout of WBS Element Detail Screens IMG activity) in order to ensure a smooth migration of
the config throughout the landscape:


/conversion/tmp/activity_task_scratch/542785170.doc 9/56
542785170.doc 10/56




Here are the detailed instructions for modifying/adjusting the transport (resulting from doing configuration in the Define Layout of WBS
Element Detail Screens IMG activity ) to ensure that such config is actually moved/migrated throughout the landscape when the transport
is submitted/released:

(i.) Enter this entry on the transport:

/conversion/tmp/activity_task_scratch/542785170.doc 10/56
542785170.doc 11/56

/conversion/tmp/activity_task_scratch/542785170.doc 11/56
542785170.doc 12/56

(ii.) Double-click the Object-Name to get a blank screen.

/conversion/tmp/activity_task_scratch/542785170.doc 12/56
542785170.doc 13/56

(iii.) Now double-click on the first blank row to open the key pop-up.

/conversion/tmp/activity_task_scratch/542785170.doc 13/56
542785170.doc 14/56

(iv.) Look at earlier failed transport for details.

/conversion/tmp/activity_task_scratch/542785170.doc 14/56
542785170.doc 15/56

(v.) SE16N for the table and detail:

/conversion/tmp/activity_task_scratch/542785170.doc 15/56
542785170.doc 16/56

(vi.) Make entries from above like below.

(8.) Define Field Selections for Project Definition and WBS Elements (Internal Projects only)
o Menu path: Project System, Structures, Operative Structures, Work Breakdown Structure (WBS ), User Interface
Settings. Then, click on the “Define Field Selections for Work Breakdown Structures” IMG activity.
o In the “Choose Activity” dialog box that pops up, click on “Field Selection: Project Definition”, and click “choose”.
o On the “Field Selection: Modifiable Fields” page, click on the “influencing” icon.
o On the “Field Selection: Influencing Fields” page, double click on the “Project Profile” influencing field.
o In the “Contents” box, choose the DPSIF profile, press enter, and set the radio buttons per the configuration in the most
recently configured environment. Here are the Project Definition settings for the influencing field “Project Profile”, and
the contents “DPSIF”:

/conversion/tmp/activity_task_scratch/542785170.doc 16/56
542785170.doc 17/56

/conversion/tmp/activity_task_scratch/542785170.doc 17/56
542785170.doc 18/56

o Repeat for DPSIP. Here are the Project Definition settings for the influencing field “Project Profile”, contents “DPSIP”:

/conversion/tmp/activity_task_scratch/542785170.doc 18/56
542785170.doc 19/56

/conversion/tmp/activity_task_scratch/542785170.doc 19/56
542785170.doc 20/56

o Go back to the “Choose Activity” box, click on “Field Selection: WBS Element”, and repeat the above process for
DPSIF & DPSIP. Here are the WBS Element settings for influencing field “Project Profile” and contents “DPSIF”.

/conversion/tmp/activity_task_scratch/542785170.doc 20/56
542785170.doc 21/56

/conversion/tmp/activity_task_scratch/542785170.doc 21/56
542785170.doc 22/56

/conversion/tmp/activity_task_scratch/542785170.doc 22/56
542785170.doc 23/56

o Here are the WBS Element settings for influencing field “Project Field” and contents “DPSIP”.

/conversion/tmp/activity_task_scratch/542785170.doc 23/56
542785170.doc 24/56

/conversion/tmp/activity_task_scratch/542785170.doc 24/56
542785170.doc 25/56

(9.) Maintain Validations (refer to RICE 427) aka ZEMVALID table maintenance:
o In the SAP R/3 transaction window, enter SM30.
o Enter ZEMVALID in the table view box.
o Click on “maintain” button, and check to make sure the following 30 entries exist as follows:

/conversion/tmp/activity_task_scratch/542785170.doc 25/56
542785170.doc 26/56

o In April 2005, the following entries were added to the ZEMVALID table for the Federal Practice project (see RICE
ID#2026) and released for transport (SPDK963272).

o On April 29, 2005, the account assignment indicator was removed from the following three table entries to fix a
problem with the data conversion project.
o
o
o

o On May 18, 2005, per CR#12 (refer to Sharepoint functional spec TEC_OtherDev-F_CCB12_Create contract with
Client PRD.doc) the Billing Indicator was activated for table entries DPSC1-CP-1, DPSC3-CP-1 to resolve an issue
involving contract setup on Client/PRD Level 1 WBS elements (SPDK964481).
o
o
o On May 31st, 2005, per Test Director defect #2037, added the CE project type to project profile DPSC3 (client/PRD
projects) to allow billable, client-facing WBS elements to be added to client/PRD projects. (Transported as
SPDK964756).

/conversion/tmp/activity_task_scratch/542785170.doc 26/56
542785170.doc 27/56

o On July 12, 2005, we were asked to remove the CE project type capability from the DPSC3 (Client w/PRD) project
profile (SPDK965995).
o On Aug 1st, 2005, we added the following three “CM” entries for TD#3477, to allow products WBS elements to be
added to Federal Practice projects. SPDK966736:

(10.) Enhancement for Project Definition and WBS elements (refer to RICE 198)
o Menu path: Project System, Structures, Operative Structures, Work Breakdown Structure (WBS ), User Interface
Settings. Then, click on the “Include User-Defined Detail Screens” IMG activity.
o Check and confirm that the following 15 entries exist as follows:

(11.) Define Time Profiles

o Menu path: Project System, Structures, Project Planning Board. Then, click on the “Define Time Profiles” IMG
activity.
o Make sure the following three time profiles are defined:

/conversion/tmp/activity_task_scratch/542785170.doc 27/56
542785170.doc 28/56

o Then, check to make sure the following values are defined for each time profile:

/conversion/tmp/activity_task_scratch/542785170.doc 28/56
542785170.doc 29/56

/conversion/tmp/activity_task_scratch/542785170.doc 29/56
542785170.doc 30/56

(12.) Define Profiles for the Project Planning Board

o Menu path: Project System, Structures, Project Planning Board. Then, click on the “Define Profiles for the Project
Planning Board” IMG activity.
o Make sure the ZSP1000 (ISP: Service Provider Plng board profile) is defined with the following values and settings:

/conversion/tmp/activity_task_scratch/542785170.doc 30/56
542785170.doc 31/56

/conversion/tmp/activity_task_scratch/542785170.doc 31/56
542785170.doc 32/56

(13.) Define Text Types for the PS Texts (still determining if there is a business need) (not needed for Release 1).
(14.) Manual Cost Planning in WBS (not needed based on new decision).
(15.) Budget Profile (can do, but not required for Release 1).
(16.) Determine Strategy for Settlement Rule (shared activity with CO) (not needed per Carlton Langley).
o Menu path: Project System, Costs, Automatic and Periodic Allocations, Settlement, Settlement Rule for Work
Breakdown Structure Element. Then, click on the “Determine Strategy for Settlement Rules” IMG activity.
o Click on “New Entries” and add the following items:
o Strategy Description
o Settlement to a PSG (profitability segment)
o After adding the entry, press enter. Then select the row, and double-click on “settings” in the dialog structure, and
populate the “strategy settings” as follows:
Billing AA No Acct Org. Settle Acct Asst N:1 RA
elem. elem. Asst Change Prof Cat SD-PS Key
    Z1 
    Z1 
    Z1 1  DTTM

(17.) Assign Strategy to Project Profile (shared activity with CO) (not needed per Carlton Langley).
o Menu path: Project System, Costs, Automatic and Periodic Allocations, Settlement, Settlement Rule for Work
Breakdown Structure Element. Then, click on the “Assign Strategy to Project Profile” IMG activity.
o Currently we are only assigning strategy to DPSC1 & DPSC2 as follows:
Proj Description Strategy Description
Profile
DPSC1 DPS Client Project Profile 02 Settlement to a PSG
DPSC2 DPS Internal Chargeable (XYZ) Profile 02 Settlement to a PSG
DPSIF DPS Firm Project Profile
DPSIP DPS Mgmt and Local Project Profile

/conversion/tmp/activity_task_scratch/542785170.doc 32/56
542785170.doc 33/56

(18.) BADI Generation of Settlement Rule (probably used at ‘go-live’).

(19.) Maintain Product Hierarchy Codes. If Product Hierarchy Codes (aka ‘Service Classification Codes’) need to be verified or
edited, enter transaction code OVSV in the R/3 txn window, and double click on “Maintain: Product Hierarchy” to access the
codes. On a “go-forward” basis, the Pricing & Billing Team has agreed to maintain this table.

o When adding, changing, or deleting SCC codes (see below), it is necessary to “save” the change before
proceeding to the next table entry.

/conversion/tmp/activity_task_scratch/542785170.doc 33/56
542785170.doc 34/56

o The product hierarchy table continues to be maintained by the Pricing & Billing Team, however, on 2005/04/27,
we received a request to add two ‘level 1’ and two ‘level 2’ entries to this table so fix a data conversion
problem. Refer to Test Director defect #1711.

(20.) Maintain the Integrated Service Offering (ISO) table codes.

o Enter transaction code ‘SM30’ in the R/3 txn window to access the ISO codes.
o Enter “ZEM_ISOCODES” in the ‘Table/View’ box.
o Click on the ‘Display’ button to view the codes, or click on the ‘Maintain’ button to edit the codes.
o The following ISO codes are currently being maintained:

/conversion/tmp/activity_task_scratch/542785170.doc 34/56
542785170.doc 35/56

o On April 7th 2005, we received a request from the BW Team to revise the codes being used in the
ZEM_ISOCODES table to match those being used in the BW and CRM systems. Refer to Test Director defects
#1679 & #1691.
o In addition, we received a small request from Tia Narciso (ISO codes business owner) to modify the name of the
RFID entry from ‘RFID’ to ‘RF Solutions’, and to relocate the ‘Not Applicable For This Project’ entry to the
bottom of the table, and to re-name the description to ‘Not Applicable’.
o The revised table was changed as follows (in SPD/010 on 2005/04/16) and submitted for transport as
SPDK963528. Please note that while the ‘ NA’ entry appears 1st in the table due to the leading space in the ISO
code, it is displayed ‘last’ in the R/3 & UI dropdown boxes due to the leading underscore in the ISO name. We
were asked by the BW team to use leading space in the ISO code for the ‘ NA’ entry to prevent having to modify
all of the existing data in the BW system.

/conversion/tmp/activity_task_scratch/542785170.doc 35/56
542785170.doc 36/56

(21.) Maintain the Business Incentive table codes.

o Enter transaction code ‘SM30’ in the R/3 txn window to access the ISO codes.
o Enter “ZEMBINC” in the ‘Table/View’ box.
o Click on the ‘Display’ button to view the codes, or click on the ‘Maintain’ button to edit the codes.
o The following Business Incentive codes are currently being maintained:

(22.) Maintain the ‘Valid Project Prefix’ table codes.

o Enter transaction code ‘SM30’ in the R/3 txn window to access the ISO codes.
o Enter “ZEMVAL_PRNO” in the ‘Table/View’ box.
o Click on the ‘Display’ button to view the codes, or click on the ‘Maintain’ button to edit the codes.
o The following Valid Project Prefix codes are currently being maintained:

/conversion/tmp/activity_task_scratch/542785170.doc 36/56
542785170.doc 37/56

/conversion/tmp/activity_task_scratch/542785170.doc 37/56
542785170.doc 38/56

o In April 2005, the following entries were added to the ZEMVAL_PRNO table for the Federal Practice project (see RICE
ID#2026) and released for transport (SPDK963272).

(23.) Maintain the ‘Standard Project Profile” table codes.

o Enter transaction code ‘SM30’ in the R/3 txn window to access the ISO codes.
o Enter “ZEM_STD_PROJPROF” in the ‘Table/View’ box.
o Click on the ‘Display’ button to view the codes, or click on the ‘Maintain’ button to edit the codes.
o The following Standard Project Profile codes are currently being maintained:
o For each standard defined in this table, a corresponding project template must be established in the SAP client using
T-code CJ91 or else an error will occur when transporting this table.
o Note that an unlimited number of standard projects can be created using CJ91 *without* a defined profile in this
table, but for the profiles that are defined in this table, they each *must* have a project standard created in R/3.
/conversion/tmp/activity_task_scratch/542785170.doc 38/56
542785170.doc 39/56

o In April 2005, the following entries were added to the ZEM_STD_PROJPROF table for the Federal Practice project (see
RICE ID#2026) and released for transport (SPDK963272).

(24.) Maintain selected ‘System Statuses” using T-Code “BS22”.

o Enter transaction code ‘BS22’ in the R/3 txn window to access the system statuses.
o The settings for the vast majority of the 500+ system statuses are OK as delivered by SAP.
o We have been asked to make a few overrides to the business transactions within the REL & CRTD system statuses.
o After starting the BS22 transaction, this is the first screen that appears:

/conversion/tmp/activity_task_scratch/542785170.doc 39/56
542785170.doc 40/56

o Double-click on the word “REL” in the Stat box depicted above. The following screen will appear:

/conversion/tmp/activity_task_scratch/542785170.doc 40/56
542785170.doc 41/56

o We have been asked to check & verify the settings of the PSNC (Change WBS Number) transaction. To do this,
enter PSNC in the empty box at the bottom left of the screen above and press the ENTER key. Verify that the
“Forbidden” radio button has been selected. See following screen shot.

o Now, click on the “back” button to return to the “System Status Maintain” page, click on the “page up” button to get
to the top of the list of system statuses, and double-click on the word “CRTD” in the Stat column.

/conversion/tmp/activity_task_scratch/542785170.doc 41/56
542785170.doc 42/56

/conversion/tmp/activity_task_scratch/542785170.doc 42/56
542785170.doc 43/56

o Enter the word “RFBU”(FI Postings txn) in the small data entry window at the bottom left of the screen and press
the ENTER key. Check to make sure the “Forbidden” radio button is selected. Repeat for the TRVL (travel details)
transaction. This should also be set to Forbidden. See following two screen shots.

/conversion/tmp/activity_task_scratch/542785170.doc 43/56
542785170.doc 44/56

(25.) Maintain/Verify the ZEM_PROJ_ACCT table.

o Enter transaction code ‘SM30’ in the R/3 txn window to access the ISO codes.
o Enter “ZEM_PROJ_ACCT” in the ‘Table/View’ box.
o Click on the ‘Display’ button to view the codes, or click on the ‘Maintain’ button to edit the codes.
o The following “project type/partner function/account group” combinations need to be contained in this table:
o Added the following entries on 2/15/2005 for the new ZD01 ‘Deloitte Assisted Deployment’ account group project:
Removed these entries on 2/16/2005 per request from Ben O, who stated that they are not needed for the Assisted
Deployment project.
 CE/SP/ZD01 (removed from zem_proj_acct table on 2/16/2005)
 CE/BP/ZD01 (removed from zem_proj_acct table on 2/16/2005)
 CE/PY/ZD01 (removed from zem_proj_acct table on 2/16/2005)
 CE/SH/ZD01 (removed from zem_proj_acct table on 2/16/2005)
 CM/SP/ZD01 (removed from zem_proj_acct table on 2/16/2005)
 CM/BP/ZD01 (removed from zem_proj_acct table on 2/16/2005)
 CM/SH/ZD01 (removed from zem_proj_acct table on 2/16/2005)
 CM/PY/ZD01 (removed from zem_proj_acct table on 2/16/2005)
 CP/SP/ZD01 (removed from zem_proj_acct table on 2/16/2005)
 CP/BP/ZD01 (removed from zem_proj_acct table on 2/16/2005)
 CP/PY/ZD01 (removed from zem_proj_acct table on 2/16/2005)
 CP/SH/ZD01 (removed from zem_proj_acct table on 2/16/2005)
 DE/SP/ZD01 (removed from zem_proj_acct table on 2/16/2005)
 DE/BP/ZD01 (removed from zem_proj_acct table on 2/16/2005)
 DE/PY/ZD01 (removed from zem_proj_acct table on 2/16/2005)
 DE/SH/ZD01 (removed from zem_proj_acct table on 2/16/2005)
 In April 2005, the following entries were added to the ZEM_PROJ_ACCT table for the Federal Practice project (see
RICE ID#2026) and released for transport (SPDK963272).

/conversion/tmp/activity_task_scratch/542785170.doc 44/56
542785170.doc 45/56

 On 6/7/2005, added the following three entries to the table per Test Director defect 2089, SPDK964968. This will allow
the Acct Group 0009 ‘international member firms’ to be visible/available when adding supplemental ‘Service At’
locations in the ‘Creat Client Project’, ‘Create Product Project, & ‘Create Federal Practice Project’.




/conversion/tmp/activity_task_scratch/542785170.doc 45/56
542785170.doc 46/56

 On 8/1/2005, we added the following five entries to the Zem_Proj_Acct table per Test Director defect 3508,
SPDK966742. This will allow the “billing address” clients (aka “bill to” clients) to function as “payer” clients’ in CE,
CP, CF, CM, & DE projects. See following screen shot:

(26.) Maintain/Verify the ZEM_PROCESS_CODE table.

o Enter transaction code ‘SM30’ in the R/3 txn window to access the ISO codes.
o Enter “ZEM_PROCESS_CODE” in the ‘Table/View’ box.
o Click on the ‘Display’ button to view the codes, or click on the ‘Maintain’ button to edit the codes.
o The following “Business Rules / Process Codes need to be contained in this table:

/conversion/tmp/activity_task_scratch/542785170.doc 46/56
542785170.doc 47/56

(27.) Maintain/Verify the ZEM_PROJ_CONT table.

o Enter transaction code ‘SM30’ in the R/3 txn window to access the ISO codes.
o Enter “ZEM_PROJ_CONT” in the ‘Table/View’ box.
o Click on the ‘Display’ button to view the codes, or click on the ‘Maintain’ button to edit the codes.
o The following “Project Type /Contract Types need to be contained in this table:

/conversion/tmp/activity_task_scratch/542785170.doc 47/56
542785170.doc 48/56

 In April 2005, the following entries were added to the ZEM_PROJ_CONT table for the Federal Practice project (see
RICE ID#2026) and released for transport (SPDK963272).

(28.) Maintain/Verify the ZEM_PROJ_WBS_ROL table.

o Enter transaction code ‘SM30’ in the R/3 txn window to access the ISO codes.
o Enter “ZEM_PROJ_WBS_ROL” in the ‘Table/View’ box.
o Click on the ‘Display’ button to view the codes, or click on the ‘Maintain’ button to edit the codes.
o The following “User Roles” need to be contained in this table with the following settings:

/conversion/tmp/activity_task_scratch/542785170.doc 48/56
542785170.doc 49/56

o On Wed. July 6th 2005, we were asked to add the partner function Z3 (‘project partner’), (which was previously
missing from this table in the SPD010 client), and set the ‘Contract Access Allowed’, ‘Project Access Allowed’, and
‘WBS Access Allowed’ attributes to ‘Yes’ (i.e. checkbox activated). TD#2767, SPDK965835.

(29.) FYI, SPECIAL TRANSPORT TIP:

 Here's how to check to see if a transport has moved to the other environments:

 Log on to the SAP R/3 GUI. Enter “SE10” in the transaction window and press enter, or double-click on the entry in
the favorites menu to start the Transport Organizer transaction.

 In the initial Transport Organizer screen, press the F5 function key.


/conversion/tmp/activity_task_scratch/542785170.doc 49/56
542785170.doc 50/56

 In the dialog box that appears, enter the transport request number (not the task number).

 Sinle-click in the top-level transport number (i.e. the ‘request number’, spdk964465 below) , and single-click the
display log button ( ) (i.e., the button with a sheet of paper and small eyeglasses).

 After clicking the Display Log button, the Log Report is generated. This shows whether the transport made it to the
other environments or not. Two examples of the Transport Logs are shown below.

/conversion/tmp/activity_task_scratch/542785170.doc 50/56
542785170.doc 51/56

/conversion/tmp/activity_task_scratch/542785170.doc 51/56
542785170.doc 52/56

(B.) Project System Non-Transportable Configuration Check List:

(1.) Configure the “Z_PRRID” object (define a number range interval):
o For each new SAP R/3 client that is being built/activated/deployed, it will be necessary to add/define one number range
interval into object Z_PRRID in order for the Z_EM_RPR (Project Reinstatement Request) transaction to function properly.
This configuration task is not transportable, and needs to be performed separately, in each client, as part of the sequence
document check list.
 In the R/3 SAP/GUI transaction window, enter SNRO for the transaction code (see following screen shot):

/conversion/tmp/activity_task_scratch/542785170.doc 52/56
542785170.doc 53/56


 In the object box, enter “Z_PRRID” for the object name (see following screen shot):

/conversion/tmp/activity_task_scratch/542785170.doc 53/56
542785170.doc 54/56


 Click on the ‘Number Ranges” button, directly below the SAP transaction window (see following screen shot):


 Click on the “Change Intervals” button.
/conversion/tmp/activity_task_scratch/542785170.doc 54/56
542785170.doc 55/56


 Click on the “Insert Interval” button, directly below the SAP transaction window (see following screen shot):


 In the ‘Insert Interval’ dialog box, tab out of the first window, and get into the ‘New Interval’ window. Enter ‘01” in the
‘No’ column, enter ‘0010000000’ in the ‘From Number’ column, and enter ‘0099999999’in the ‘To Number’ column.
When done, click the ‘Insert’ button at the bottom of the dialog box to finish entering the number range interval data.
Then click the ‘Save’ button to store the new number range interval in the object. See the following screen shot.

/conversion/tmp/activity_task_scratch/542785170.doc 55/56
542785170.doc 56/56

/conversion/tmp/activity_task_scratch/542785170.doc 56/56