Migration of Peoplesoft 3rd Party Objects | PeopleSoft Tutorial

Migration of Peoplesoft 3rd Party Objects

1. Overview

Following are a few major 3rd Party tools that are supported by PeopleSoft Applications. Changes are occasionally made to the delivered code in order to suit the business needs as per the customer’s requirements.

  1. COBOL
  2. SQR
  3. nVision
  4. Crystal

As part of standard requirements, COBOL and SQR program migration needs to be done at both UNIX and Windows, whereas nVision and Crystal migration is performed for Windows only.

2. Assumptions

Listed below is a set of variables that are referred in the document:

  1. CaseID – is the ID that identifies the issue reported.
  2. HOST_PS_HOME : denotes the PeopleSoft home directory for the customer
  3. HOST_PS_HOME/nvision/:  denotes the source directory for nVision reports within the PeopleSoft home directory

3. Migration of COBOL programs

On Windows:

  1. Take the backup of existing COBOL program to folder named backup\CBL in the HOST_PS_HOME directory. If it is one or few COBOL programs, to save disk space,  copy only related files into  backup\CBL folder.
  2. Rename the COBOL programs with the following naming convention COBOL_<<CaseID>>_yyyymmdd.CBL, before moving them to the backup folder.
  3. In case of Tax Updates (where there are multiple COBOL programs, it is recommended to create a sub directory under HOST_PS_HOME\Backup\CBL\<<CaseID>>_yyyymmdd and place the COBOL programs within this directory without renaming them.
  4. Perform a simple OS copy of the COBOL programs from the HOST_PS_HOME/src/cbl/ source to target environment.

On UNIX:

  1. Take the backup of existing COBOL to the folder named backup\CBL in the HOST_PS_HOME directory. . If it is one or few COBOL programs, to save disk space, copy only related files into backup\CBL folder
  2.  Rename the COBOL programs with the following naming convention COBOL_<<CaseID>>_yyyymmdd.CBL, before moving them to the backup folder.
  3. In case there are multiple COBOL programs, it is recommended to create a sub directory under HOST_PS_HOME\Backup\CBL\<<CaseID>>_yyyymmdd and place the COBOL programs within this directory without renaming them.
  4. FTP the COBOL programs from Windows to UNIX.
  5. Ensure that the case of the COBOLS files remains unaltered and it should be migrated to ftped ASCII format and not BINARY format.
  6. As per standards, COBOL programs are always pre-fixed in upper case and file extension is .cbl
  7. In Unix, use the command below to move the COBOL programs:

cp –r <source path> <target path>

4. Migration of SQR programs

On Windows:

  1. Take the backup of existing SQR(s) to a folder named backup\SQR in the HOST_PS_HOME directory.
  2. Rename the SQR programs with the following naming convention:

SQR_<<CaseID>>_yyyymmdd.CBL

, before they are moved to the backup folder.

  1. In case of Tax Updates, where there are multiple SQRs, create a sub directory under HOST_PS_HOME\Backup\CBL\<<CaseID>>_yyyymmdd and move the SQRs to this directory without renaming them.
  2. Perform a simple OS copy of the SQRs from the HOST_SRC_PS_HOME/sqr/ source to target.

On UNIX:

  1. Take the backup of existing SQR to a folder named backup\SQR in the HOST_PS_HOME directory.
  2. Rename the SQR programs with the following naming convention:

SQR_<<CaseID>>_yyyymmdd.CBL

, before they are moved to the backup folder.

  1. In case of Tax Updates, where there are multiple SQRs, create a sub directory under HOST_PS_HOME\Backup\CBL\<<CaseID>>_yyyymmdd and move the SQRs to this directory without renaming them.
  2. FTP the SQR from Windows to UNIX.
  3. As per PeopleSoft standards, the SQR filename should always be in lower case in ASCII format.
  4. In UNIX, use the command below to move the SQRs.

cp –r HOST_SRC_PS_HOME/sqr HOST_TGT_PS_HOME/sqr/<target path>

5. Migration of nVision reports

On Windows only:

  1. Take a backup of the existing nVision to a folder named backup\nVision in the HOST_PS_HOME directory.
  2. Rename the nVision reports programs with the following naming convention:

nVision_<<CaseID>>_yyyymmdd.xls

, before they are moved to the backup folder.

  1. If there are multiple nVision reports, create sub directory under HOST_PS_HOME\Backup\nVision\<<CaseID>>_yyyymmdd and move the nVision reports to this folder without renaming them.
  2. Copy the nVision reports from the HOST_SRC_PS_HOME/nvision/ to target.

6. Migration of Crystal reports (CRW)

On Windows only:

  1. Take a backup of the existing CRW to a folder named backup\CRW in the HOST_PS_HOME directory.
  2. Rename the Crystal reports with the following naming convention: CRW_<<CaseID>>_yyyymmdd.xls,

before they are moved to the backup folder.

  1. If there are multiple Crystal reports, then create a sub directory under HOST_PS_HOME\Backup\CRW\<<CaseID>>_yyyymmdd and move the CRWs to this folder without renaming them.
  2. Copy the CRWs from the source to target.

7. Conclusion

Migration of PeopleSoft 3rd party tools is a small yet important task. It should be carried out accurately in order for the entire PeopleSoft application system to be functionally correct.

 

Prashant
 

>