Upload
madhu
View
82
Download
8
Tags:
Embed Size (px)
Citation preview
[Type text]
Financial Data Migration 8.8 to 9.0Technical Design Documentation
[Type text]
Revision History
Date Version Description Author Reviewed By
11th Aug 2011
1 Initial Document Ravichandan Kumar
[Type text]
1. OVERVIEW...............................................................................................................................................4
1.1 Functional Requirement.............................................................................................41.2 Design Overview.......................................................................................................4
2. DATA FLOW DIAGRAM.........................................................................................................................4
3. IMPACTED OBJECTS.............................................................................................................................5
3.1 Objects List................................................................................................................53.2 Functionality..............................................................................................................5
3.2.1 Migrate the Project Costing Details to Patni......................................................53.3 Rules for migration....................................................................................................73.4 Utilities......................................................................................................................8
3.4.1 Excel to CI Utility...............................................................................................83.4.2 Data Mover Scripts.............................................................................................83.4.3 File Layouts........................................................................................................83.4.4 Application Engine.............................................................................................83.4.5 SQL scripts for ETL...........................................................................................93.4.6 Third Party Application......................................................................................9
3.5 Technical Details.....................................................................................................10Source System...........................................................................................................10ETL............................................................................................................................28Target System............................................................................................................28
3.6 Report Layout..........................................................................................................29
4. ISSUES AND ASSUMPTIONS................................................................................................................29
1. OVERVIEW
1.1 Functional RequirementAfter the iGATE-Patni Merger, as both iGATE and Patni uses PS Financial System for their internal operations, there is a need to integrate both the systems to create one single internal system to be used. As such, all the data residing in iGATE PS Financial systems need to be migrated to Patni PS Financial system.
1.2 Design OverviewAs per the functionality, we need to use some data migration strategies and tools to migrate the data between the systems for the PS objects to achieve the requirements for the business to work. This design document will capture the very common data migration details including the migration tools and conditions for migration of data. We will have the specific design documents, for any major changes to the functionality or a new functionality addition. This document is divided into sections, where in each migration tool and development effort will be captured with the individual technical details.
2. DATA FLOW DIAGRAM
3. IMPACTED OBJECTS
3.1 Objects List
SLNo Object Name Object Type New/Update
3.2 Functionality
3.2.1 Migrate the Project Costing Details to PatniAs part of the data migration from the source 8.8 PS system to target 9.0 PS systems, the project details being maintained in the PS 8.8 system has to be migrated over to PS 9.0 system. This includes the Projects, activities, transaction, project team, project roles information also.
3.2.1.1 NavigationModule Data
ElementSource System Target System
PC Integration Template
Main Menu > Set Up Financials/Supply Chain > Product Related > Project Costing > Project Options > Integration Templates
PC Project Types Main Menu > Set Up Financials/Supply Chain > Product Related > Project Costing > Project Options >Project Types
PC Status Types Main Menu > Set Up Financials/Supply Chain > Product Related > Project Costing > Project Options >Status Types
PC Project Roles Main Menu > Set Up Financials/Supply Chain > Product Related > Project Costing > Project Options >Project Roles
PC Activity Types
Main Menu > Set Up Financials/Supply Chain > Product
Related > Project Costing > Activity Options > Activity Types
PC Employee Rates
Main Menu > Set Up Financials/Supply Chain > Product Related > Project Costing > Pricing Structure > Rates by Employee
PC Projects Main Menu > Project Costing > Project Definition > General Information
PC Team Main Menu > Project Costing> Project Definition> Team
PC Organization Main Menu > Project Costing > Project Definition> Organization
PC Status Main Menu > Project Costing > Project Definition > Status
PC Activities Main Menu > Project Costing > Activity Definition > General Information
3.2.1.2 Component(s)The following data elements from PS 8.8 system will be moved to PS 9.0 system using the component interface extraction and loading.
Module Data Element Source System Target SystemPC Projects PROJECT_GENERALPC Organization PSA_ORGPRJ_DEFNPC Team PROJECT_TEAM1PC Status PC_PRJ_STATUS_PNLGPC Activities PROJECT_ACTIVITYPC Transactions INTFC_PROJ_EXPRESS
3.2.1.3 Component Interface(s)The following component interfaces will be used for extracting data from PS 8.8 system that will be moved to PS 9.0 system.
Module Data Element Source System Target SystemPC Projects PROJECT_GENERAL PROJECT_INTFC_PROJPC Organization FO_PSA_DEFN FO_PSA_DEFN
PC Activities PROJECT_ACTIVITY PROJECT_INTFC_ACTPC Transactions PROJECT_STG_RESOURCES
3.2.1.4 Record(s)The following data elements from PS 8.8 system will be moved to PS 9.0 system using the sql based data extraction and loading.
Module Data Element Source System Target SystemPC Project Types PROJ_TYPE_TBL,PROJ
_TYPE_RATE, PROJ_TYPE_LANG
PROJ_TYPE_TBL,PROJ_TYPE_RATE, PROJ_TYPE_LANG
PC Activity Types PROJ_ACT_TBL, PROJ_ACT_LANG
PROJ_ACT_TBL, PROJ_ACT_LANG
PC Project Roles PROJ_ROLE, PROJ_ROLE_LANG
PROJ_ROLE, PROJ_ROLE_LANG
PC Employee Rates PC_RATE_EMPL PC_RATE_EMPLPC Integration Template PC_INT_TMPL;PC_INT_
TMPL_LNG;PC_INT_TMPL_GL; PC_INTMPL_GL_LG;
PC_INT_TMPL;PC_INT_TMPL_LNG;PC_INT_TMPL_GL; PC_INTMPL_GL_LG;
3.3 Rules for migration 1. Only Active Projects to be migrated to INDIA business unit of 9.0. The project
effective status should be either 'A' or if the end date of the project >= 1st Nov 2011.
2. Project Opportunity details to be loaded into the custom place holders in 9.0.3. The project organization chartfield values to be moved are: business_unit_gl,
department, operating unit, end customer and service operation. End Customer and Service Operation to be derived.
4. Only Active Activities for the above active projects to be moved. CONSULTING activity map to PROJECT PLAN. The bill plan details will be used to create project milestone activities. Percent Complete to be derived from Budgeting.
5. Project transactions for billing worksheet data needs to be migrated with the condition of transaction status being not distributed for invoice generation.
6. Other project transactions marked as billable however Final Invoice is not generated.
7. All team members in the above active projects.8. While moving the team members, map the Project Manager to the PM role, all
other members will be moved with a default project role being used in PS 9.0.9. Project security details are migrated to contract support team tables in PS 9.0.
3.4 Utilities
3.4.1 Excel to CI Utility
3.4.1.1 Connection Information
Source System Target System
3.4.1.2 CI NameSource System Target System
3.4.1.3 Data File
3.4.2 Data Mover Scripts
3.4.2.1 DMS File
3.4.2.2 DAT File
3.4.3 File Layouts
3.4.3.1 Record NamesSource System Target System
Record DetailsName : New/Updated : NewRecord Type : SQL tableSl No. Field Name Type Length Edit Key
3.4.4 Application EngineCreate the application engine IGS_DM_PRJAE which will be used to extract the data from the following component interfaces described in the source system columns:
Projects refer: 3.2.1.3Activities refer: 3.2.1.3
Transactions refer: 3.2.1.3Organization refer: 3.2.1.3
Create the application engine PAT_DM_PRJAE which will be used to extract the data from the target records of ETL into the interface tables of 9.0 using the following component interfaces described in the target system columns.
Projects refer: 3.2.1.3Activities refer: 3.2.1.3Transactions refer: 3.2.1.3Organization refer: 3.2.1.3
3.4.4.1 State Record(s)Record Name
Record DetailsName : New/Updated : NewRecord Type : SQL tableSl No. Field Name Type Length Edit Key
3.4.4.2 Temporary Record(s)Record Name
Record DetailsName : New/Updated : NewRecord Type : SQL tableSl No. Field Name Type Length Edit Key
3.4.5 SQL scripts for ETL
3.4.6 Third Party Application
3.4.6.1 Integration Broker
MessageSource System Target System
Service OperationSource System Target System
External Node DetailsSource System Target System
WSDL FileSource System Target System
3.5 Technical Details
Source System1. Application engine to be created as described in section 3.4.4 above.2. Logic for the application engine: Extract the projects data using the project CI described in 3.2.1.3 above. Logic should be written to extract project which are either active or whose end date is
greater than or equal to ’01-nov-2011’. The percent complete data for all the projects to be overridden with the data provided
by support. Also the Project Manager data from 8.8 should be moved into the
PROJECT_MANAGER field in 9.0 CI. Once the projects are loaded, update the Opportunity details in the following custom
place holders: Extract all the team members from the project team. The project manager should be
moved using the project manager role PM DEL. Extract the organization details for projects and add additional chartfield values of
‘End Customer’ being derived from contract project association and ‘Service Offering’ provided by Delivery.
Extract the activities for the above projects using the activity CI described in 3.2.1.3 above.
Also if the project activity is associated to a contract line, which has milestone events associated, those milestones will become activities as follows:
a. Two additional levels of activities will be created. At the second level we have to create activity id 'BILLING_MIL' below the 'Project plan' activity.
b. Below the ‘BILLING_MIL' activity, all the milestones will be created as activities having the activity id in the format of 'MILESTONE_1',
'MILESTONE_2' and so on, with the same description. The end date for these activities will be the 'EVENT DATE' defined for the milestone in the bill plan.
c. The milestones marked as completed will all be consolidated into one single activity, with the activity end date of 31-dec-2011 and start date being the minimum of the milestone event date.
As the activity structure is changed from 8.8 to 9.0, derive the level numbers and WBS ID for the activities and associate them with the relevant field in the CI.
Additional activity should be created for all the projects with activity ID and description of ‘TRASH_ACTIVITY’.
Transactions to be moved using the criteria:o Project transactions for billing worksheet data needs to be migrated with the
condition of transaction status being not distributed for invoice generation. ANALYSIS_TYPE in ’BIL’,’BWK’; BI_DISTRIB_STATUS in ‘W’,’N’; EX_DOC_TYPE = 'B'; PM_REVIEW_FLAG = 'Y'.
o Other project transactions marked as billable however Final Invoice is not generated should also be migrated. ANALYSIS_TYPE in ’BIL’; BI_DISTRIB_STATUS in ‘W’,’N’; PM_REVIEW_FLAG = 'Y'.
Project security details are migrated to contract support team tables in PS 9.0. Support team members should be moved according to the mapping of the support team roles.
Source to Target record field mapping
Projects
Target Field Name Type Description Source Record Source Field Name
INTFC_ID Number Batch interface identifier. 99999INTFC_LINE_NUM Number Unique batch line identifier. Calculated valueBUSINESS_UNIT Character Prompts from the SP_BU_PC_NONVW table. PROJECT BUSINESS_UNITPROJECT_ID Character Unique project identifier. PROJECT PROJECT_IDINTEGRATION_TMPL Character Must be a value from the Integration Template
table (PC_INT_TMPL). Default value is INTE-GRATION_TMPL.OPR_DEF_TBL_PC if not pro-vided in the source file.
PROJECT INTEGRATION_TMPL
DESCR Character Project description up to 30 characters. PROJECT DESCRPROJECT_TYPE Character Prompts from the PROJ_TYPE_TBL table. PROJECT PROJECT_TYPE
Note. The default value of the rate set or rate plan is based on the project type if you associate a predefined rate set or rate plan with the project type and include the project type in the source file.
DESCR254 Character Project description up to 254 characters. PROJECT_DESCR DESCR254TEAM_MEMBER Character Must be a value from the PROJ_TEAM_VW ta-
ble.PROJ_TEAM_SCHED TEAM_MEMBER
PROJ_ROLE Character Project team member's project role. Prompts from the Project Role table (PROJ_ROLE).
PROJ_TEAM_SCHED PROJ_ROLE
EMAILID Character Project team member's email ID. PROJ_TEAM_SCHED EMAILID
MANAGER_EFFDT Date MANAGER_EFFDT and MANAGER_START_DT must have the same date and must both be between the project start and end dates; otherwise, an error message ap-pears. MANAGER_EFFDT, if left blank, is popu-lated with the current date. PROJECT_MGR
EFFDT
PROJECT_MANAGER Character If PROJECT_MANAGER is populated, PROJ_ROLE, MANAGER_START_DT, and MANAGER_END_DT are required to save the page; otherwise, an error message appears.
PROJECT_MGR
PROJECT_MANAGER
ROLE_TYPE Character Project team member's role type. If PROJECT_MANAGER is populated, this field is required to save the page. PROJECT_MGR
ROLE_TYPE
MANAGER_START_DT Date MANAGER_EFFDT and MANAGER_START_DT must have the same date and must both be between the project start and end dates; otherwise, an error message ap-pears. PROJECT_MGR
START_DT
MANAGER_END_DT Date If PROJECT_MANAGER is populated, this field is required to save the page. PROJECT_MGR
END_DT
STATUS_EFFDT Date Project's status effective date. Populated with %Date (current server date) if not provided in the source file. PROJ_STATUS_TBL
EFFDT
PROJECT_STATUS Character Must be a value from the PROJ_STATUS_TBL table If a project status is provided in the source file, it must be previously defined against a pro-cessing status in the PROJ_STATUS_TBL table. If a project status is not provided, the default is based on the PC_STAT_DEFAULT table.
PROJ_STATUS_TBL
PROJECT_STATUS
START_DT Date Project team member's start date. PROJ_TEAM_SCHED START_DTEND_DT Date Project team member's end date. PROJ_TEAM_SCHED END_DTPERCENT_COMPLETE Number Percent project is completed. PROJECT PERCENT_COMPLETEPROJECT_USER1 Character User-definable field. PROJECT PROJECT_USER1PROJECT_USER2 Character User-definable field. PROJECT PROJECT_USER2PROJECT_USER3 Character User-definable field. PROJECT PROJECT_USER3PROJECT_USER4 Character User-definable field. PROJECT PROJECT_USER4PROJECT_USER5 Character User-definable field. PROJECT PROJECT_USER5PROJECT_USER_DT6 Date User-definable field. PROJECT PROJECT_USER_DT6PROJECT_USER_DT2 Date User-definable field. PROJECT PROJECT_USER_DT2PC_USER_CURRENCY Character User-definable field. Prompts from the CUR-
RENCY_CD_TBL table.PROJECT PC_USER_CURRENCY
PROJECT_USERAMT1 Sign User-definable field. PROJECT PROJECT_USERAMT1PROJECT_USERAMT2 Sign User-definable field. PROJECT PROJECT_USERAMT2PROJECT_USERAMT1 Sign User-definable field. PROJECT PROJECT_USERAMT1SET_OVERRIDE Character Populated from the SP_SETID_NONVW table.
General ledger uses this setID for prompting and the Journal Edit process. The field is required if PeopleSoft General Ledger is installed or you use Projects Budgeting.
PROJECT SET_OVERRIDE
EARLY_START_DT Date Early start date. PROJECT EARLY_START_DTEARLY_FINISH_DT Date Early finish date. PROJECT EARLY_FINISH_DT
ACTUAL_START_DT Date Actual start date. PROJECT ACTUAL_START_DTACTUAL_FINISH_DT Date Actual finish date. PROJECT ACTUAL_FINISH_DTBASELINE_START_DT Date Baseline start date. PROJECT BASELINE_START_DTBASELINE_FINISH_DT Date Baseline finish date. PROJECT BASELINE_FINISH_DTLATE_START_DT Date Late start date. PROJECT LATE_START_DTLATE_FINISH_DT Date Late finish date. PROJECT LATE_FINISH_DTPC_SCH_PRODUCT Character Third-party product code is a text field with no
edit. The field is used for informational purposes only and can help reference the source system for the transaction.
FS 8.8
PC_SCH_FIELD1 Character Third-party project ID. If you import from a third-party product, this field is used to store the project ID that is from the third-party product.
PROJECT PROJECT_ID
PC_SCH_FIELD2 Character Third-party project description up to 40 charac-ters.
PROJECT DESCR
SUMMARY_PRJ Character Flag that designates if the project is a summary or a detail project. Default value is N (no).
PROJECT SUMMARY_PRJ
ENFORCE Character Identifies the enforce project team option, such as PeopleSoft Expenses only, PeopleSoft Time and Labor only, Expenses and Time and Labor, or do not enforce. Default value is BUS_UNIT_OPT_PC.ENFORCE.
PROJECT ENFORCE
ENFORCE_TYPE Character Identifies the enforce project and activity team option, such as project and activity team, project team only, decide at the project level, or do not enforce. Default value is BUS_UNIT_OPT_PC.ENFORCE_TYPE.
PROJECT ENFORCE_TYPE
PC_PROCESS_STATUS Character Provide a processing status value of A (active), I (inactive), or P (pending). If the source file does not contain a processing status, the default value is based on the Processing Status field on the Project Status Defaults page.
A
PROJ_REQUEST_ID Character Project request ID. PROJECT PROJ_REQUEST_IDPPK_PROJ_VERSION Character Project request version. PROJECT PPK_PROJ_VERSIONPGM_SCHED_METHOD Character Schedule method, such as fixed units, duration,
and work. Default value is BUS_UNIT_OPT_PC.PGM_SCHED_METHOD.
PROJECT PGM_SCHED_METHOD
PC_PERCENT_DTTM Date/Time Percent complete date and time. PROJECT PC_PERCENT_DTTMHOLIDAY_LIST_ID Character Holiday calendar. Default value is
BUS_UNIT_OPT_PC.HOLIDAY_LIST_ID.PROJECT HOLIDAY_LIST_ID
PLAN_STARTDT Date Planned start date. PROJ_TEAM_SCHED PLAN_STARTDTPLAN_ENDDT Date Planned end date. PROJ_TEAM_SCHED PLAN_ENDDTPLAN_PROJROLE Character Primary project role. Prompts from Project Role
table (PROJ_ROLE).PROJ_TEAM_SCHED PLAN_PROJROLE
PC_CALCULATE_SW Character Calculate manually, delay calculations until save, or calculate in real time. Default value is BUS_UNIT_OPT_PC.PC_CALCULATE_SW.
PROJECT PC_CALCULATE_SW
CHARGING_LEVEL Character The level of WBS activities that are available for charging, such as all detail activities, level 1, level 2, and level 3. Default value is from BUS_UNIT_OPT_PC.CHARGING_LEVEL.
PROJECT CHARGING_LEVEL
Activities
Target Field Name Type Description Source Record Source Field Name
INTFC_ID Number Batch interface identifier. 88888INTFC_LINE_NUM Number Unique batch line identifier. Calculated valueBUSINESS_UNIT Character Prompts from the
SP_BU_PC_NONVW table.PROJ_ACTIVITY BUSINESS_UNIT
PROJECT_ID Character You can bulk load projects and use the system's autonumber functionality to generate the next PROJECT_ID. In this case PROJECT_IDs are not re-quired. However, if you perform up-date to projects, or incrementally add activities to projects, PROJECT_IDs are required and are validated against the PROJECT table.
PROJ_ACTIVITY PROJECT_ID
ACTIVITY_ID Character Activity IDs are to be moved as is. Only the CONSULTING activity ID will be mapped to PROJECT_PLAN activ-ity. Mapping will be done in ETL. Also milestone activities will be derived and moved.
PROJ_ACTIVITY ACTIVITY_ID
ACTIVITY_DESCR Character Activity description up to 30 charac-ters.
PROJ_ACTIVITY ACTIVITY_DESCR
ACTIVITY_TYPE Character Prompts from the PROJ_ACT_TBL table. Default value is CODE.
PROJ_ACTIVITY ACTIVITY_TYPE
PERCENT_COMPLETE Number Schedule status percent complete. Calculated value
EARLY_START_DT Date Early start date. PROJ_ACTIVITY EARLY_START_DTLATE_START_DT Date Late start date. PROJ_ACTIVITY LATE_START_DTACTUAL_START_DT Date Actual start date. PROJ_ACTIVITY ACTUAL_START_DT
EARLY_FINISH_DT Date Early finish date. PROJ_ACTIVITY EARLY_FINISH_DTLATE_FINISH_DT Date Late finish date. PROJ_ACTIVITY LATE_FINISH_DTACTUAL_FINISH_DT Date Actual finish date. PROJ_ACTIVITY ACTUAL_FINISH_DT
BASELINE_FINISH_DT Date Baseline finish date. PROJ_ACTIVITY BASELINE_FINISH_DT
BASELINE_START_DT Date Baseline start date. PROJ_ACTIVITY BASELINE_START_DT
ACTIVITY_USER1 Character User-definable field. PROJ_ACTIVITY ACTIVITY_USER1ACTIVITY_USER2 Character User-definable field. PROJ_ACTIVITY ACTIVITY_USER2ACTIVITY_USER3 Character User-definable field. PROJ_ACTIVITY ACTIVITY_USER3ACTIVITY_USER4 Character User-definable field. PROJ_ACTIVITY ACTIVITY_USER4ACTIVITY_USER5 Character User-definable field. PROJ_ACTIVITY ACTIVITY_USER5PC_ACT_USER_DT1 Date User-definable field. PROJ_ACTIVITY PC_ACT_USER_DT1
PC_ACT_USER_DT2 Date User-definable field. PROJ_ACTIVITY PC_ACT_USER_DT2
PC_USER_CURRENCY Character User-definable field. Prompts from the CURRENCY_CD_TBL table.
PROJ_ACTIVITY PC_USER_CURRENCY
PC_ACT_USERAMT1 Sign User-definable field. PROJ_ACTIVITY PC_ACT_USERAMT1
PC_ACT_USERAMT2 Sign User-definable field. PROJ_ACTIVITY PC_ACT_USERAMT2
PC_ACT_USERAMT3 Sign User-definable field. PROJ_ACTIVITY PC_ACT_USERAMT3
DESCR254 Character Activity description up to 254 charac-ters.
PROJ_ACT_DESCR DESCR254
ACTIVITY_STATUS Character Activity status. Prompts from the PROJ_STATUS_TBL table. Latest ef-fective status.
PROJ_ACT_STATUS ACTIVITY_STATUS
ACT_STATUS_EFFDT Date Activity status effective date. Popu-lated with %Date (current server date) if not provided in the source file. Lat-est status effective date.
PROJ_ACT_STATUS EFFDT
START_DT Date Activity start date. PROJ_ACTIVITY START_DTEND_DT Date Activity end date. PROJ_ACTIVITY END_DTACTIVITY_PRIORITY Number Activity priority. PROJ_ACTIVITY ACTIVITY_PRIORITY
ACT_PCT_COMPLETE Number Activity percentage complete. PROJ_ACTIVITY ACT_PCT_COMPLETE
PC_MILESTONE_FLG Character Indicates if activity is a milestone. PROJ_ACTIVITY PC_MILESTONE_FLG
AFUDC_ACT_SW Character Allows interest calculations for this project activity.
PROJ_ACTIVITY AFUDC_ACT_SW
PC_DURATION Number Duration. PROJ_ACTIVITY PC_DURATIONENFORCE Character Identifies the enforce project team op-
tion, such as PeopleSoft Expenses only, PeopleSoft Time and Labor only, Expenses and Time and Labor, or do not enforce.
PROJ_ACTIVITY ENFORCE
PC_CHC_ACT_SW Character Enables change control. Default value is PROJECT.PC_CHC_SW.
PROJ_ACTIVITY PC_CHC_ACT_SW
PGM_SCHED_METHOD Character Schedule method, such as fixed units, duration, and work. Default value is PROJECT.PGM_SCHED_METHOD.
PROJ_ACTIVITY PGM_SCHED_METHOD
WBS_ID Character Coded hierarchy identifier for each activity.
Calculated
HGRID_LEVEL_SBR Subrecord Hierarchy grid subrecord.
Calculated
LEVEL1 Number CalculatedLEVEL2 Number CalculatedLEVEL3 Number CalculatedLEVEL4 Number CalculatedLEVEL5 Number CalculatedLEVEL6 Number CalculatedLEVEL7 Number Calculated
LEVEL8 Number CalculatedLEVEL9 Number CalculatedLEVEL_NUM Number CalculatedDEADLINE_DT Date Deadline date. PROJ_ACTIVITY DEADLINE_DTCONSTRAINT_DT Date Constraint date. PROJ_ACTIVITY CONSTRAINT_DTCONSTRAINT_TYPE Character Constraint type. PROJ_ACTIVITY CONSTRAINT_TYPE
COSTING_ACT_SW Character Activity costing flag. Indicates whether an activity is available for charging.
PROJ_ACTIVITY COSTING_ACT_SW
PC_ACT_OWNER Character Activity owner. Prompts from PC_TEAM_PROM_VW table.
PROJ_ACTIVITY PC_ACT_OWNER
CURRENCY_CD Character Default value is PROJECT.CUR-RENCY_CD.
PROJ_ACTIVITY CURRENCY_CD
PC_ACT_DEF_CALC_MT Character Activity calculation method. Default value is PROJECT.PC_ACT_DEF_CALC_MT.
PROJ_ACTIVITY PC_ACT_DEF_CALC_MT
Transactions
Target Field Name Type Description Source Record Source Field
INTFC_ID Number Batch interface identi-fier.
77777
INTFC_LINE_NUM Number Unique batch line identi-fier.
Calculated
PC_RES_INTF_SBR Subrecord
BUSINESS_UNIT Character Prompts from the SP_BU_PC_NONVW table.
PROJ_RESOURCE BUSINESS_UNIT
PROJECT_ID Character Prompts from the SP_PROJ_NONVW ta-ble.
PROJ_RESOURCE PROJECT_ID
ACTIVITY_ID Character Prompts from the PROJ_ACT_VW table.
PROJ_RESOURCE ACTIVITY_ID
RESOURCE_ID Character Resource ID. PROJ_RESOURCE RESOURCE_ID
RESOURCE_ID_FROM Character Resource ID from. PROJ_RESOURCE RESOURCE_ID_FROM
BUSINESS_UNIT_GL Character Prompts from the SP_BUPCIT_NONVW table.
PROJ_RESOURCE BUSINESS_UNIT_GL
BUSINESS_UNIT_PC Character Project business unit. PROJ_RESOURCE BUSINESS_UNIT
JOURNAL_ID Character Journal ID. PROJ_RESOURCE JOURNAL_ID
JOURNAL_DATE Date Journal date. PROJ_RESOURCE JOURNAL_DATE
UNPOST_SEQ Number Unpost sequence. PROJ_RESOURCE UNPOST_SEQ
JOURNAL_LINE Number General ledger journal line number.
PROJ_RESOURCE JOURNAL_LINE
FISCAL_YEAR Number Fiscal year. PROJ_RESOURCE FISCAL_YEAR
ACCOUNTING_PERIOD Number Accounting period. PROJ_RESOURCE ACCOUNTING_PERIOD
ACCOUNT Character Prompts from the GL_ACCT_BUGL_VW table.
PROJ_RESOURCE ACCOUNT
ALTACCT Character Prompts from the ALT_BUGL_VW table.
Derived
DEPTID Character Prompts from the DEP-TID_BUGL_VW table.
PROJ_RESOURCE DEPTID
CF16_AN_SBR Character ChartField subrecord.
OPERATING_UNIT Character Prompts from the OPE-RUNT_BUGL_VW table.
PROJ_RESOURCE OPERATING_UNIT
PRODUCT Character Prompts from the PRODUCT_BUGL_VW table.
Derived
FUND_CODE Character Prompts from the FUND_BUGL_VW table.
Derived
CLASS_FLD Character Prompts from the CLASSCF_BUGL_VW table.
Derived
PROGRAM_CODE Character Prompts from the PRO-GRAM_BUGL_VW ta-ble.
Derived
BUDGET_REF Character Prompts from the BUD_REF_BUGL_VW table.
Derived
AFFILIATE Character Prompts from the AFFIL-IATE_VW table.
PROJ_RESOURCE
AFFILIATE_INTRA1 Character Intraunit affiliate 1. Derived
AFFILIATE_INTRA2 Character Intraunit affiliate 2. Derived
CHARTFIELD1 Character Prompts from the CF1_BUGL_VW table.
Derived
CHARTFIELD2 Character Prompts from the CF2_BUGL_VW table.
Derived
CHARTFIELD3 Character Prompts from the CF3_BUGL_VW table.
Derived
BUS_UNIT_GL_FROM Character Prompts from the Inte-gration Template Gen-eral Ledger table (PC_INT_TMPL_GL).
PROJ_RESOURCE BUS_UNIT_GL_FROM
CURRENCY_CD Character Prompts from the Cur-rency Codes table (CURRENCY_CD_TBL).
PROJ_RESOURCE CURRENCY_CD
STATISTICS_CODE Character Prompts from the STAT_BUGL_VW table.
PROJ_RESOURCE STATISTICS_CODE
LEDGER_GROUP Character Prompts from the SP_LEDGPC_NONVW table.
PROJ_RESOURCE LEDGER_GROUP
ANALYSIS_TYPE Character Analysis type. PROJ_RESOURCE ANALYSIS_TYPE
RESOURCE_TYPE Character Prompts from the Project Resource Type table (PROJ_RES_TYPE).
PROJ_RESOURCE RESOURCE_TYPE
RESOURCE_CATEGORY Character Category. PROJ_RESOURCE RESOURCE_CATEGORY
RESOURCE_SUB_CAT Character Subcategory. PROJ_RESOURCE RESOURCE_SUB_CAT
RES_USER1 Character Transaction user 1. PROJ_RESOURCE RES_USER1
RES_USER2 Character Transaction user 2. PROJ_RESOURCE RES_USER2
RES_USER3 Character Transaction user 3. PROJ_RESOURCE RES_USER3
RES_USER4 Character Transaction user 4. PROJ_RESOURCE RES_USER4
RES_USER5 Character Transaction user 5. PROJ_RESOURCE RES_USER5
TRANS_DT Date Transaction date. PROJ_RESOURCE TRANS_DT
ACCOUNTING_DT Date Accounting date. PROJ_RESOURCE ACCOUNTING_DT
JRNL_LN_REF Character Journal line reference. PROJ_RESOURCE JRNL_LN_REF
OPEN_ITEM_STATUS Character Prompts from the field's translate values.
PROJ_RESOURCE OPEN_ITEM_STATUS
LINE_DESCR Character Journal line description. PROJ_RESOURCE LINE_DESCR
JRNL_LINE_STATUS Character Prompts from the field's translate values.
PROJ_RESOURCE JRNL_LINE_STATUS
JOURNAL_LINE_DATE Date Journal line date. PROJ_RESOURCE JOURNAL_LINE_DATE
FOREIGN_CURRENCY Character Prompts from the FRGN_CURR_VW ta-ble.
PROJ_RESOURCE FOREIGN_CURRENCY
RT_TYPE Character Prompts from the Mar-ket Rate Data Types ta-ble (RT_TYPE_TBL).
PROJ_RESOURCE RT_TYPE
FOREIGN_AMOUNT Sign Foreign amount. PROJ_RESOURCE FOREIGN_AMOUNT
RATE_MULT Sign Rate multiplier. PROJ_RESOURCE RATE_MULT
RATE_DIV Number Rate divisor. PROJ_RESOURCE RATE_DIV
CUR_EFFDT Date Currency effective date. PROJ_RESOURCE CUR_EFFDT
PC_DISTRIB_STATUS Character Prompts from the field's translate values.
PROJ_RESOURCE PC_DISTRIB_STATUS
GL_DISTRIB_STATUS Character Prompts from the field's translate values.
PROJ_RESOURCE GL_DISTRIB_STATUS
PROJ_TRANS_TYPE Character Prompts from the Project Transaction Types table (PROJ_TRANS_TYPE).
PROJ_RESOURCE PROJ_TRANS_TYPE
PROJ_TRANS_CODE Character Prompts from the Project Transaction Codes table (PROJ_TRANS_CODE).
PROJ_RESOURCE PROJ_TRANS_CODE
RESOURCE_STATUS Character Transaction status. PROJ_RESOURCE RESOURCE_STATUS
DESCR Character Description. PROJ_RESOURCE DESCR
UNIT_OF_MEASURE Character Prompts from the Units of Measure table (UNITS_TBL).
PROJ_RESOURCE UNIT_OF_MEASURE
EMPLID Character Prompts from the PROJ_TEAM_VW table.
PROJ_RESOURCE EMPLID
EMPL_RCD Number Employee record num-ber.
PROJ_RESOURCE EMPL_RCD
SEQ_NBR Number Sequence number. PROJ_RESOURCE SEQ_NBR
TIME_RPTG_CD Character Time reporting code. PROJ_RESOURCE TIME_RPTG_CD
JOBCODE Character Job code. PROJ_RESOURCE JOBCODE
COMPANY Character Company. PROJ_RESOURCE COMPANY
BUSINESS_UNIT_AP Character Prompts from the SP_BU_AP_NONVW ta-ble.
PROJ_RESOURCE BUSINESS_UNIT_AP
VENDOR_ID Character Prompts from the PROJ_VENDOR_VW table.
PROJ_RESOURCE VENDOR_ID
VOUCHER_ID Character Voucher ID. PROJ_RESOURCE VOUCHER_ID
VOUCHER_LINE_NUM Number Voucher line number. PROJ_RESOURCE VOUCHER_LINE_NUM
APPL_JRNL_ID Character Prompts from the Jour-nal Generator template table (JRNLGEN_APPL_ID).
PROJ_RESOURCE APPL_JRNL_ID
PYMNT_CNT Number Payments. PROJ_RESOURCE PYMNT_CNT
DST_ACCT_TYPE Character Prompts from the field's translate values.
PROJ_RESOURCE DST_ACCT_TYPE
PO_DISTRIB_STATUS Character Prompts from the field's translate values.
PROJ_RESOURCE PO_DISTRIB_STATUS
BUSINESS_UNIT_PO Character Prompts from the SP_BU_PM_NONVW table.
PROJ_RESOURCE BUSINESS_UNIT_PO
REQ_ID Character Requisition ID. PROJ_RESOURCE REQ_ID
REQ_LINE_NBR Number Requisition line number. PROJ_RESOURCE REQ_LINE_NBR
REQ_SCHED_NBR Number Requisition schedule number.
PROJ_RESOURCE REQ_SCHED_NBR
REQ_DISTRIB_NBR Number Requisition distribution number.
PROJ_RESOURCE REQ_DISTRIB_NBR
PO_ID Character Purchase order number. PROJ_RESOURCE PO_ID
DUE_DATE Date Delivery due date from. PROJ_RESOURCE DUE_DATE
LINE_NBR Number Line number. PROJ_RESOURCE LINE_NBR
SCHED_NBR Number Schedule number. PROJ_RESOURCE SCHED_NBR
DISTRIB_LINE_NUM Number Distribution line. PROJ_RESOURCE DISTRIB_LINE_NUM
AM_DISTRIB_STATUS Character Prompts from the field's translate values.
PROJ_RESOURCE AM_DISTRIB_STATUS
BUSINESS_UNIT_AM Character Prompts from the SP_BU_AM_NONVW table.
PROJ_RESOURCE BUSINESS_UNIT_AM
ASSET_ID Character Prompts from the PROJ_ASSET_VW ta-ble.
PROJ_RESOURCE ASSET_ID
PROFILE_ID Character Prompts from the PRO-FILE_PCAM_VW table.
PROJ_RESOURCE PROFILE_ID
COST_TYPE Character Prompts from the Asset Cost Type Definition ta-ble (COST_TYPE_TBL).
PROJ_RESOURCE COST_TYPE
BOOK Character Asset book name. PROJ_RESOURCE BOOK
INCENTIVE_ID Character Prompts from the PC_PROJ_GNT_VW ta-ble.
PROJ_RESOURCE INCENTIVE_ID
MSTONE_SEQ Number Milestone sequence. PROJ_RESOURCE MSTONE_SEQ
CONTRACT_NUM Character Prompts from the CA_CONTRACT_VW table.
PROJ_RESOURCE CONTRACT_NUM
CONTRACT_LINE_NUM Number Contract line number. PROJ_RESOURCE CONTRACT_LINE_NUM
CONTRACT_PPD_SEQ Number Prepaid add sequence. PROJ_RESOURCE CONTRACT_PPD_SEQ
BI_DISTRIB_STATUS Character Prompts from the field's translate values.
PROJ_RESOURCE BI_DISTRIB_STATUS
BUSINESS_UNIT_BI Character Prompts from the SP_BU_BI_NONVW ta-ble.
PROJ_RESOURCE BUSINESS_UNIT_BI
BILLING_DATE Date Billing date. PROJ_RESOURCE BILLING_DATE
INVOICE Character Invoice. PROJ_RESOURCE INVOICE
REV_DISTRIB_STATUS Character Prompts from the field's translate values.
PROJ_RESOURCE REV_DISTRIB_STATUS
BUSINESS_UNIT_AR Character Prompts from the SP_BUARED_NONVW table.
PROJ_RESOURCE BUSINESS_UNIT_AR
CUST_ID Character Prompts from the PROJ_CUST_VW table.
PROJ_RESOURCE CUST_ID
ITEM Character Prompts from the ITEM_OPEN_PC_VW table.
PROJ_RESOURCE ITEM
ITEM_LINE Number Item line. PROJ_RESOURCE ITEM_LINE
ITEM_SEQ_NUM Number Item sequence number. PROJ_RESOURCE ITEM_SEQ_NUM
DST_SEQ_NUM Number Distribution sequence. PROJ_RESOURCE DST_SEQ_NUM
EX_DOC_ID Character PeopleSoft Expenses document ID.
PROJ_RESOURCE EX_DOC_ID
EX_DOC_TYPE Character Prompts from the field's translate values.
PROJ_RESOURCE EX_DOC_TYPE
RESOURCE_QUANTITY Sign Quantity. PROJ_RESOURCE RESOURCE_QUANTITY
RESOURCE_AMOUNT Sign Project business unit amount.
PROJ_RESOURCE RESOURCE_AMOUNT
BUDGET_HDR_STATUS Character Prompts from the field's translate values.
PROJ_RESOURCE BUDGET_HDR_STATUS
KK_AMOUNT_TYPE Character Prompts from the field's translate values.
PROJ_RESOURCE KK_AMOUNT_TYPE
KK_TRAN_OVER_FLAG Character Override transaction. PROJ_RESOURCE KK_TRAN_OVER_FLAG
KK_TRAN_OVER_OPRID Character Override user ID. PROJ_RESOURCE KK_TRAN_OVER_OPRID
KK_TRAN_OVER_DTTM DtTm Override date. PROJ_RESOURCE KK_TRAN_OVER_DTTM
BUDGET_OVER_ALLOW Character Budget overrun allowed. PROJ_RESOURCE BUDGET_OVER_ALLOW
BUDGET_LINE_STATUS Character Prompts from the field's translate values.
PROJ_RESOURCE BUDGET_LINE_STATUS
BUDGET_DT Date Budget date. PROJ_RESOURCE BUDGET_DT
LEDGER Character Prompts from the SP_LEDPC_NONVW table.
PROJ_RESOURCE LEDGER
BD_DISTRIB_STATUS Character Prompts from the field's translate values.
PROJ_RESOURCE BD_DISTRIB_STATUS
BUSINESS_UNIT_BD Character Prompts from the SP_BUPCBD_NONVW table.
PROJ_RESOURCE BUSINESS_UNIT_BD
FA_STATUS Character F&A status. PROJ_RESOURCE FA_STATUS
TIME_SHEET_ID Character Time report ID. PROJ_RESOURCE TIME_SHEET_ID
SHEET_ID Character Report ID. PROJ_RESOURCE SHEET_ID
DT_TIMESTAMP DtTm Date timestamp. PROJ_RESOURCE DT_TIMESTAMP
VCHR_DIST_LINE_NUM Number Distribution line number. PROJ_RESOURCE VCHR_DIST_LINE_NUM
PM_REVIEWED Character Prompts from the field's translate values.
PROJ_RESOURCE PM_REVIEWED
PRICED_RATE Sign Priced rate. PROJ_RESOURCE PRICED_RATE
ACTIVITY_ID_DETAIL Character Prompts from the Activ-ity ID Detail Prompt ta-ble (PC_ACT_DETAIL).
PROJ_RESOURCE ACTIVITY_ID_DETAIL
CST_DISTRIB_STATUS Character Prompts from the field's translate values.
PROJ_RESOURCE CST_DISTRIB_STATUS
TXN_LMT_TRANS_ID Character Transaction limit ID. PROJ_RESOURCE TXN_LMT_TRANS_ID
EVENT_NUM Number Event number. PROJ_RESOURCE EVENT_NUM
CA_FEE_STATUS Character Prompts from the field's translate values.
PROJ_RESOURCE CA_FEE_STATUS
FMS_WHO_SBR Subrecord Date, time and operator subrecord.
PROJ_RESOURCE
FMS_DTTM_STAMP DtTm Date/time stamp. PROJ_RESOURCE FMS_DTTM_STAMP
FMS_OPRID Character Operator ID. PROJ_RESOURCE FMS_OPRID
FMS_LASTUPDDTTM DtTm Last update date/time. PROJ_RESOURCE FMS_LASTUPDDTTM
FMS_LASTUPDOPRID Character Last update user ID. PROJ_RESOURCE FMS_LASTUPDOPRID
PROJ_ROLE Character Project role. Prompts from the PROJ_ROLE_SECVW table.
PROJ_RESOURCE PROJ_ROLE
START_DATE Date Start date for Gen Stand.
PROJ_RESOURCE START_DATE
END_DATE Date End date. PROJ_RESOURCE END_DATE
ETL
Create the records listed and described in section 3.2.1.4 above, in the source and target data structure for ETL.
Use the SQL scripts for ETL described in section 3.4.5 to migrate the data in the source records for ETL.
Update the business unit to ‘INDIA’ from ‘100’ in the output. Map the ‘CONSULTING’ activity ID to PROJECT_PLAN activity. Other project setup mapping details to be finalized………. Once all the above activities are finished, load the data into the target structures for
ETL. Move the setup data from the target structures of ETL into the destination 9.0 PS
records for setups as described in the section 3.2.1.4 above.
Target System Write an application engine described in section 3.4.4 above to extract all the data from the
target ETL records into a csv file. Use the CI described in section 3.2.1.3 target system column (for projects and activities), to
load the data present in the above csv files to the respective project and activity interface tables. Update the interface ID to 99999 for projects and 88888 for activities and increment the interface line number starting with 1.
Once the above application engine loads data into INTFC_PROJ_GEN and INTFC_ACT_GEN records, navigate to PROJECT COSTING > Third Party Integration > Load Project and Activities.
Run the process providing appropriate run control ID and selecting the run control option: ‘Both Projects and Activities’ and interface option ‘All’.
Navigate to PROJECT COSTING > Third Party Integration > Review Project Details, and provide the interface id 99999 to find if any rows of data has gone into error.
Navigate to PROJECT COSTING > Third Party Integration > Review Activity Details, and provide the interface id 88888 to find if any rows of data has gone into error.
Once all the projects and activities are loaded successfully, use the CI described in section 3.2.1.3 for loading the project organization.
Use the CI described in section 3.2.1.3 target system column (for transactions), to load the data present in the above csv files to the transaction interface table.
Update the interface ID to 77777 and increment the interface line numbers starting with 1. Once the above application engine loads data into INTFC_PROJ_RES record, navigate to
PROJECT COSTING > Third Party Integration > Load Transactions. Run the process providing appropriate run control ID and selecting the default run control
options for all the fields. Navigate to PROJECT COSTING > Third Party Integration > Review Transaction Details,
and provide the interface id 77777 to find if any rows of data has gone into error. Finally migrate the project delivery manager, engagement manager and field manager into
the project support team of 9.0
3.6 Report LayoutN/A
4. ISSUES AND ASSUMPTIONS
Issues:1. No movement of bench and management projects and their resources. They will be
tracked using the cost codes in PS 9.0 system.2. Business will provide the additional details for End Customer and Service offering and
they will be moved as part of Organization structure for Projects.3. Project Managers have to create the project plan; once the projects are moved into PS 9.0
from PS 8.8 including assigning team members to activities.4. Communication for employee expenses transactions to be closed by December 2011 for
projects ending earlier than 31-Oct-2011 as those projects will not be migrated to new environment.
5. By mid November, project managers are given training and demo instances to evaluate the effort required for managing projects in the new PS 9.0 system.
6. PS 8.8 finance support team to provide the percent completion numbers for migration.7. Derive the region and rate for project resources using the project roles being maintained
in PS 8.8. PS 8.8 finance support team to do the same and provide to data migration team. PS 9.0 team to provide the data structure to move the same.