PeopleSoft Installation: Change from host-only to bridged to enable internet in VM

When you deploy Linux based PeopleSoft VM on Virtual Box, system enables Host-Only Adapter so that host and guest can communicate with each other. Most likely, guest machine is assigned an IP 192.168.56.101 though it might differ also.
But the issue with this type of setup is that, guest machine can't communicate with external network which means Web Services to communicate with third part systems can't be created and to deal with this we need to change the adapter setting in Virtual Machine so that it can communicate both with host and external network. The best contender for the same is Bridged Adapter but that's not just enough as we have to also do couple of other things for this to work so lets get started.

Change network setting

Change the network type form host only to bridged adapter under network setting in Virtual Box as shown below:

Obtain new IP address of VM

Restart the VM and check the new IP address by issuing ifconfig command and note down new IP address

The new IP address of VM is 192.168.100.60

Changes in host system

Do following changes in the host machine

tnsnames.ora file

File Location - C:\oracle\product\12.1.0\client_1\network\admin

change the IP address to new IP address i.e. from 192.168.56.101 to 192.168.100.60

Hosts file

File Location - C:\Windows\System32\drivers\etc
change the IP address to new IP address i.e. from 192.168.56.101 to 192.168.100.60 for host hcm92.ps.com

Change in guest machine

Login into VM and change the IP address to new IP address i.e. from 192.168.56.101 to 192.168.100.60 for hcm92.ps.com
Hosts file location - /etc/hosts

Segmentation not created for a payee in PeopleSoft Global Payroll

Recently we had an issue when payroll wasn't creating segments for a new country for which we were implementing GP. We spend nearly two days trying to figure out what exactly was causing this.

These are possible reasons:

Unprocessed Iterative Triggers

If one or more iterative triggers of previous period are in unprocessed state then segmentation for those employees will not be processed. If so then delete those triggers using below SQL
DELETE FROM PS_GP_RTO_TRGR WHERE COUNTRY = <payee's country> AND EMPLID = <emplid> AND TRGR_STATUS = 'U' AND CAL_RUN_ID <> <Current Calendar Group>;

There might also be unprocessed iterative triggers created for the country other than payee's country which will cause this hence delete those triggers too.

Unprocessed Retro Triggers

If one or more retro triggers for other countries are in unprocessed state then segmentation for those employees will not be processed. If so then delete those triggers using below SQL
DELETE FROM PS_GP_ITER_TRGR WHERE COUNTRY <> <payee's country> AND EMPLID = <emplid> AND ITER_TRGR_STATUS = 'U';

Segmentation Triggers

If one or more segmentation triggers for other countries exist and are active for those employees then segmentation will not be processed.
DELETE FROM PS_GP_SEG_TRGR WHERE COUNTRY <> <payee's country> AND EMPLID = <emplid> AND SEG_TRGR_STATUS = 'A';

In our case, all above where the reasons so we basically deleted all those unwanted triggers (Iterative, Retro and Segment) using SQL script and it resolved the issue. The segmentation was processed.