The below steps were done & the issue was fixed :
1. Regenerate the services in the target instance.
After the clone, services have to be re-generated. Its mandatory step as the SOA artifacts will have the end point URL which is instance specific. Only re-generate WSDL will update instance specific details. This is the expected behavior
soagenerate.sh can be used to generate multiple WSDL.
a. Prepare a file with the name of all the interfaces you want to regenerated
Example:
vi /tmp/services.lst
FND_USER_PKG
FND_USER_RESP_GROUPS_API
$FND_TOP/bin/soagenerate.sh
Enter the single or multiple generate as S/M :
M
Enter the filename of the interface to be generated :
/tmp/services.lst
2.Re-deploy using the soadeploy.sh
Example:
$FND_TOP/bin/soadeploy.sh
Enter the single or multiple deploy as S/M :
M
Enter the filename of the interface to be deployed:
/tmp/services.lst
1. Regenerate the services in the target instance.
After the clone, services have to be re-generated. Its mandatory step as the SOA artifacts will have the end point URL which is instance specific. Only re-generate WSDL will update instance specific details. This is the expected behavior
soagenerate.sh can be used to generate multiple WSDL.
a. Prepare a file with the name of all the interfaces you want to regenerated
Example:
vi /tmp/services.lst
FND_USER_PKG
FND_USER_RESP_GROUPS_API
$FND_TOP/bin/soagenerate.sh
Enter the single or multiple generate as S/M :
M
Enter the filename of the interface to be generated :
/tmp/services.lst
2.Re-deploy using the soadeploy.sh
Example:
$FND_TOP/bin/soadeploy.sh
Enter the single or multiple deploy as S/M :
M
Enter the filename of the interface to be deployed:
/tmp/services.lst