We are working on the fusion Apps relase 11.7, now to solve some of the batch jobs we have two technology implementation available.
1. Write a BPEL prococess for the job.
2. Write a PLSQL process for the job.
Now my ess job will be called once in a year or twice, which option is best for us, One more question is for plsql API.
What is oracle strategy over the plsql API, is there any chance, a plsql APIs will be withdrawn in the future releases of the FA.
I am not 100% certain I understand your question correctly. The BPEL part of the Fusion Apps techstack is generally used to model and implement business processes. ESS is fundamentally a scheduling tool that lets you create programs designed to run in the background, either adhoc or with a given schedule. ESS jobs are typically implemented in PL/SQL, Java or C/C++.
Without knowing more than "we have to update some of the status on yearly basis", my inclination would be to use ESS to create a scheduled job that runs automatically once a year and updates the desired data in the database. If you were to implement this as a process in BPEL, what would trigger that process?
Not 100% sure what you mean by Oracle withdrawing the PL/SQL API -- do you mean the ability to implement ESS jobs in PL/SQL? I cannot make any statements about future product direction here, but documented APIs have certain support levels (see OER), and of course Oracle ships a number of PL/SQL ESS programs as well.
Does this help?
Happy New Year!
Fusion Apps Developer Relations