Unauthorized Access Error when Direct-Connecting to ECC

This behavior is actually expected and typically indicates that the ECC security integration with EBS is working correctly. Users are required to access the ECC framework only through the Oracle EBS login interface, generally via the associated responsibility (like Payables Manager or ECC Developer). When you attempt to connect directly to the ECC managed server URL, the system correctly denies access because the request is not authenticated via the EBS session. You should access the ECC configuration UI through the ‘ECC Developer’ responsibility within EBS.

If you have performed the necessary steps to assign the product-specific roles and responsibilities but the function is still missing, the issue is often related to caching in EBS. You should try clearing the EBS cache using the Functional Administrator responsibility. If the function remains missing afterward, you should carefully review the steps under the ‘Providing users access to ECC’ section to ensure that the correct product-specific roles (e.g., `UMX|ONT_ECC_ROLE` for Order Management) were successfully assigned to the responsibility using either manual steps or the `UMX_ENDECA_RBACAuto.sh` script.

You absolutely can automate mass role assignment using the `UMX_ENDECA_RBACAuto.sh` script, which should be executed from the EBS run filesystem. This script utilizes a CSV file (e.g., `UMX_ENDECA_RBAC.csv`) that maps the `PERMISSION_SET_CODE`, `RESPONSIBILITY_CODE`, and the required `ENDECA_ROLE_CODE`. By preparing a comprehensive CSV file listing all necessary assignments (such as the extensive list provided in the documentation for various modules like FA, CST, and WIP), you can provision access to all Command Centers quickly and programmatically.