How to Register a Custom Concurrent Program in Oracle EBS

How to register a custom concurrent program

1. 1Write and test the underlying code first - a PL/SQL stored procedure in a custom schema (granted execute to APPS and with a public synonym), a SQL*Plus script, a Java concurrent program class, or a Host script - before touching any registration screen.
2. 2In System Administrator, go to Concurrent > Program > Executable, create a new executable with a unique short name, select the correct Execution Method (PL/SQL Stored Procedure, SQL*Loader, Host, SQL*Plus, Java Concurrent Program) matching your code, and enter the exact executable file or package.procedure name.
3. 3Go to Concurrent > Program > Define, create the Program, link it to the Executable just registered, set the Application it belongs to, and mark Enabled.
4. 4On the Parameters tab, define each parameter with a Value Set for validation, mark required parameters, set the correct sequence and display size, and confirm the parameter order matches what your PL/SQL procedure expects positionally.
5. 5Set Output Format (Text or XML Publisher if a BI Publisher layout is attached) and Print Style, and configure Incompatibilities if this program must not run concurrently with another that touches the same data.
6. 6Navigate to Security > Responsibility > Request, find the Request Group tied to the target responsibility, and add your new program to it - without this step the program is fully registered but invisible to end users.
7. 7Test via Submit Request under the actual target responsibility (not just System Administrator), checking both a successful run and a deliberate bad-parameter run to confirm error handling and the log/output files look correct.

Parameter definition and value sets

PROCEDURE run_report (errbuf OUT VARCHAR2, retcode OUT VARCHAR2, p_org_id IN NUMBER, p_period_name IN VARCHAR2) IS
BEGIN
  -- FND standard signature: errbuf, retcode first, then registered parameters in order
  NULL;
END run_report;

Common pitfalls

• !Executable name registered in EBS not matching the actual package.procedure name exactly, including case sensitivity on some platforms.
• !Forgetting to grant execute on the custom package to APPS and create the public synonym, producing a generic routine-not-found failure at runtime.
• !Parameter order in the Define Program form not matching the PL/SQL procedure's positional signature, causing silently wrong parameter values.
• !Registering the program but skipping the Request Group step, leaving it invisible to the responsibility that needs it.
• !Not setting Incompatibilities for programs that update the same tables, allowing two instances to run simultaneously and corrupt data.
• !Testing only as a super-user responsibility, missing MOAC or security-profile-driven differences the real end-user responsibility will hit.