hi.. .I'm currently working on a customized interface which will transfer taxable expense items from iExpenses to Payroll through the standard Batch Element Entry API. . .The technical solution has the following elements: . 1)Custom staging table. . 2)PL/SQL Package Procedure. . 3)Concurrent Executable. . 4)Concurrent Program. . .The concurrent executable will call the procedure in the custom package. .The procedure is: .* LOAD_STAGE . This will create records of all taxable expense items in the staging table XXDWP_IEXP_PAY from iExpenses and default the TRANSFER_FLAG to ‘N’. .* LOAD_BEE_FROM_STAGE . This will call the standard PAY_BATCH_ELEMENT_ENTRY_API to validate and transfer records from the staging table to the Batch Element Entries table and set the TRANSFER_FLAG to ‘Y’ once a record is validated and transferred successfully. .* TRUNC_STAGE . This will delete all records in the staging table where the TRANSFER_FLAG = ‘Y’. . .I've already created the package with the API calls. .what i need now is a way of calling it from a concurrent program? .i know the logic i just don't how to actually do it. . .any ideas?

Sounds like you're half-way there. If you've registered the executable (and therein specified that the thing is a pl/sql package) and you've created a concurrent program that uses that executable (and therein specified any parameters to be supplied at runtime etc) then all you need to do after that is register the concurrent program with an appropriate request group. eg the standard one is 'UK HRMS Reports and Processes' - you might want to add it to that one or alternatively if you want access to it to be restricted in some way then you'll need to create a separate request group then a specific responsibility to make use of that request group. Thereafter you should be able to run it.

that's cool.. but how do i actually call the package from the concurrent exec. or program?? i mean the actual place i type in the code? and what's the code itself? is it just: PKG_NAME.PROC_NAME ?? i do expect it to be a bit more complicated than that! oh and by the way i don't have any parameters to pass on. . .cheers.

OK the code has to exist as a compiled package header/body . .The executable definition (done within sysadmin) has to be of a type 'pl/sql package' or whatever it's called exactly. In the field where you say what is being executed you put <package>.<procedure>. Try doing a query within this screen for existing entries with the type 'pl/sql package' to see how they're set up. . .The concurrent program definition allows you to give a 'meaningful' user-friendly label for the process and at the same time which defined executable is to be run. Optionally parameter definitions may also be set up. . .Apart from registering that concurrent program with your chosen request group that really is it!

Agree

oh this was very helpful i've done all that already i just thought there was more to it. you know when it's a simple thing you just feel there's more to it!!! then again maybe it's just me! <img src="/ubbthreads/images/graemlins/smile.gif" alt="" /> .thanks again for clearing it up for me mate. .cheers.