Background Info: We were doing OID - EBS registration and as part of this process, ran the below command to register EBS with OID component.
$FND_TOP/bin/txkrun.pl -script=SetSSOReg -registeroid=yes
As the above command results are successful and also logs are showing that registration went successful and also checked on OID level @ DIP component and provision profile created and syncing option are enabled.
However DIP Profile ( OID - EBS) status is shows as "Not Available" instead of Scheduled.
To correct this, we have followed the below approach.
1. De-registered the EBS instance.
$FND_TOP/bin/txkrun.pl -script=SetSSOReg -deregisteroid=yes
2. Removed the references at EBS end.
$FND_TOP/bin/txkrun.pl -script=SetSSOReg -removereferences=yes
3. Register again EBS with OID along with additional parameters ( appname & svcname).
$FND_TOP/bin/txkrun.pl -script=SetSSOReg -registeroid=yes -appname=EBSNEW
-svcname=EBSTESTNEW
Note: In this step, we used different name than EBS Instance Application name for parameters ( appname & svcname). These 2 arguments are for just identification at DIP level.
After these steps, we were able to see DIP Profile ( OID - EBS) status as "Scheduled" and User provisioning working as expected. We were able to see the records which are created at OID level are showing in EBS end (fnd_user table).
