Applying Country Extension and Bundles

This Blog is regarding the steps to be followed while applying Country extensions and GP Bundles #8 and #9 in UAT and PROD instances considering the china Bolton issue encountered in DEV and DMO instances.
UAT and PROD are now at MP6 ML stage, Country extensions followed by GP Bundle #8 and #9 has to be applied. Following are the steps to be followed to apply Country extensions and GP Bundles in UAT and PROD instances:

1. Run SYSAUDIT and DDDAUDIT reports and make sure that they are clean.

2. Refer: 1-7,1-10 and 1-11 in “Installing_HRMS_Campus_Solutions_9[1].0_Applications.pdf”.

Note: This step may include bouncing application server regarding which CHRIS team has to be informed 2 Hrs prior to the action.

3. For country extensions, follow “HC9_MP6_GP_ML.pdf”. Please maintain a copy of all the log files.

4. China Bolt-on is prerequisite for China Country Extension. Follow “GP_China_bolton.pdf” for China Bolton. It is suggested not to use the record structure in China Bolton, as suggested in SR 3-970069241. Because China Bolt-on, which was released before GP Bundle 4, is having older version of Record Structures compared to MP6 ML. Instead skip the Project download step in China Bolton and proceed with Rule and Non Rule packages steps Page 22 “Installing Global Payroll for China Extensions” and page 26 “Installing the Global Payroll for China Extensions Multilingual Portion”.
HC9_MP6_GP_ML.pdf will be present in MP6 zip file. Unzip MP and follow the path: “MP6\HC9_MP6_ML\Cumulative\upd774233ml\upd774233_install_ml”.
China Bolt-on and China Bolt-on ML Zip folder and Installation guide can be found in Shared folders “\HRIS_HRMS\hcm9phase2\2000-Implement\070-Patches\China Bolt-on”

a. While Applying Non-Rule Package "CNSYS" as part of China Bolt-on, CNSYS_RECORDS_IMP.DMS throws Error: "SQL duplicate rows in SET_CNTRL_REC 1". Resolution would be to execute “DELETE FROM PS_SET_CNTRL_REC WHERE SETCNTRLVALUE = 'CHN' AND SETID <> 'CHN' “ followed by commit and rerun CNSYS_RECORDS_IMP.dms.

b. We will encounter error in “cnsyszhs_records_imp.dms” as part of Non-Rule Package “CNSYSZHS”. The error will be because of the mismatch in the record structure of “GPCN_PSLP_LANG”. The Script “cnsyszhs_records_imp.dms” will be looking for only 5 fields in the record whereas system will have 11 Fields.
Resolution would be:

i. In App designer record GPCN_PSLP_LANG will have 11 fields. Delete all the 6 fields GPCN_LBL_ACUM1 to GPCN_LBL_ACUM6.

ii. Alter the Table (with Build and Execute Option) and rerun “cnsyszhs_records_imp.dms”. Complete the China Bolt-on Rule and Non-Rule packages.

iii. in App designed add all 6 deleted fields in the record GPCN_PSLP_LANG, Alter the Table (with Build and Execute Option). Continue with the steps specified for China Country Extension.

5. Run DDDAUDIT and SYSAUDIT reports and make sure that both are clean.

6. Apply Bundle #8 and #9 after country extensions. Zip folders can be found in shared folders “\HRIS_HRMS\hcm9phase2\2000-Implement\070-Patches\Bundles\Bundle Zip folders”
GP Bundle #8: upd734686.zip
GP Bundle #9: upd765610.zip

a. We will encounter one more issue while applying GP Bundle #9. “Createviews.sql” throws error while attempting to create view “PS_GPFR_DA_SIT_VW”. It is because the view “PS_GPFR_DA_SIT_VW“ will be built on one of the non existing Records “PS_GPFR_AF_EE_SIT” in the system. We can ignore this View as it is related to Country France Global Payroll. Resolution would be to delete the steps related to the view “PS_GPFR_DA_SIT_VW” in “Createviews.sql” and run the script for the remaining views.

7. Run DDDAUDIT and SYSAUDIT reports and make sure that both are clean.

8. In DDDAUDIT report records with name PS_GPDE_SI_ACCDT will appear in database and Application Designer. This record is supposed to be deleted in GP Bundle 9 both from Database and application designer. But in application designer it is deleted but not from Database (we got the same record in all the instances in which Bundle 9 is applied). Drop the table from database. After deleting the table, make sure that DDDAUDIT is clean.