Share all details about your problem, including any error messages you may have received.
We are trying to do CREATE provisioning for Oracle E-Business connector. The CREATE provisioning policy is added and we were able to get successful provisioning result. But when checked with Oracle DBA team, they mentioned the account is created in EBS application but not in DB.
What does this mean?
Do we need a separate insert query to insert the record in the DB as well like we do for JDBC connector?
@aseelvn07 - As part of SailPoint IdentityIQ provisioning, the Oracle E-Business Suite connector is expected to create the user at the application level in the FND_USER table (not necessarily as a separate Oracle database login in DBA_USERS). Could you please verify whether the user record has been created in the FND_USER table in the EBS schema? If possible, kindly confirm the result of this check and let me know whether DBA expectation is for SailPoint to provision only the EBS application user (FND_USER) or also to create a dedicated Oracle database account for the same user?
We do create provisioning for an identity and its successful as shown in Sailpoint. Oracle DB team confirmed the user got created in EBS app and not in the database.
We aggregated existing accounts from the application and we could see EMPLOYEE_ID is populated for these accounts.
But when we do CREATE provisioning, how can this attribute be populated. I saw in some posts that the EMPLOYEE_ID is the Person ID from another table that needs to created/ fetched during CREATE provisioning.
As per requirement, we need the record to be inserted into the PER_ALL_PEOPLE_F table as well