ESP Workload Automation

Expand all | Collapse all

ESP jobs failing with operating unit issue after Oracle EBS upgrade to 12.2

  • 1.  ESP jobs failing with operating unit issue after Oracle EBS upgrade to 12.2

    Posted Aug 22, 2017 04:59 PM

    After upgrade of Oracle Applications to 12.2, we are noticing some of the concurrent programs failing with the message " Problem with OA job data Operating Unit is mandatory or required field for ..." .   when submitted from ESP. 

     

    In the oa.log, we notice that this message shows up after running the SQL "select multi_org_category from fnd_concurrent_programs_vl where concurrent_program_name='<PROGRAM SHORT NAME>'. 

     

    Please let me know if you have seen any identical issues and provide inputs in fixing the issue. 



  • 2.  Re: ESP jobs failing with operating unit issue after Oracle EBS upgrade to 12.2

    Broadcom Employee
    Posted Aug 26, 2017 09:19 PM

    Hi,

    Are you able to login to EBS and manually submit the same request?

    Use the same user ID that you have defined in your job and test it manually.

     

    Thank you,

    Nitin Pande

    CA Technologies



  • 3.  Re: ESP jobs failing with operating unit issue after Oracle EBS upgrade to 12.2

    Posted Aug 26, 2017 11:14 PM

    Hi Nitin,

     

    Thanks for your response. We submitted the request manually from that user ID and it's completing normal.

    We are facing issues only when the request is submitted from ESP (user ID remains the same).

     

    We also noticed that the requests that require output post processing are also failing when they are submitted from ESP.

     

    Please let us know what needs to be done to fix the issue.



  • 4.  Re: ESP jobs failing with operating unit issue after Oracle EBS upgrade to 12.2

    Broadcom Employee
    Posted Aug 27, 2017 08:22 PM

    Hi,

    Can you tell us what is the exact agent and plugin version?

    For Oracle EBS 12.2, you will need to be on 11.3.04 or 11.3 SP4.  We recommend to first upgrade the system agent to SP4 or above.  Then upgrade the Oracle EBS plugin to SP4 as well.

    Also, make sure that the permissions of the user is not an issue here.  If you notice any SQL errors in the oa.log, then you will need to make sure that the user has all the recommended table access.

     

    Thank you,

     

    Nitin Pande

    CA Technologies



  • 5.  Re: ESP jobs failing with operating unit issue after Oracle EBS upgrade to 12.2

    Posted Sep 06, 2017 12:30 PM

    Hello Nitin - We are upgraded to SP4 for System Agent now.. Can you let us know what do we need to request CA for Oracle EBS Plugin Upgrade to SP4. Enabling OA Log, we see below error -

    OAPlugin.oa Internal Thread.OaDbHandler.getAccessMode[:633] - Query: select multi_org_category from fnd_concurrent_programs_vl where concurrent_program_name='PAXTRTRX'
    OAPlugin.oa Internal Thread.CybWOBRunOaHandler.processWob[:125] -
    Problem with OA job data Operating Unit is mandatory or required field for PAXTRTRX.

     

    From Log, it looks like there is validation post above query which compares a variable against being NULL. Is there a way to find what variable is it comparing against.

     

    Appreciate your help!!



  • 6.  Re: ESP jobs failing with operating unit issue after Oracle EBS upgrade to 12.2

    Broadcom Employee
    Posted Sep 06, 2017 01:23 PM

    Hi,

    Please visit CA Support site (login required).  Under Download management, search for "CA Workload Automation DE - Business Agents (dSeries)".  You will see Oracle EBS options listed in the search result, download the SP4 version for your OS.  If you are experiencing issues, then please contact CA Support and we would be happy to help.

     

    As for the error "OA job data Operating Unit is mandatory or required field for PAXTRTRX.", this looks something needs to be fixed in you project.  You can have look at this doc from Oracle, which discusses the PAXTRTRX module.  This will require you to contact your Oracle Applications admin or Oracle.

     

    Thank you,

     

    Nitin Pande

    CA Technologies



  • 7.  Re: ESP jobs failing with operating unit issue after Oracle EBS upgrade to 12.2

    Posted Sep 06, 2017 03:40 PM

    Thanks Nitin.. From our enterprise login we could not locate Download menu in site. We will work with CA Support to download SP4 version. But reading the "CA Workload Automation DE - Business Agents (dSeries)" document, it doesn't look to be a EBS Plugin document. Anyhow we will pursue it with support.

     

    The reason "OA Job data" error looks to be ESP specific is; same job is working through application. Any thoughts where can see base code for OaDbHandler/OAPlugin. We can crack validation from it..

     

    Thanks,

    Shobhit



  • 8.  Re: ESP jobs failing with operating unit issue after Oracle EBS upgrade to 12.2

    Broadcom Employee
    Posted Sep 07, 2017 11:56 AM

    Hi Shobhit,

    The CA Agent mainly uses the API's as provided by Oracle.  As for your initial problem, you may want to check this blog and make necessary changes to your program (PAXTRTRX).

     

    Thank you,

     

    Nitin Pande

    CA Technologies



  • 9.  Re: ESP jobs failing with operating unit issue after Oracle EBS upgrade to 12.2

    Posted Sep 07, 2017 04:02 PM

    Hello Nitin,

     

    Debugging further we were able to narrow down error log to OAJobData.class

    orgName = p_dataExtractor.getFieldValue("OPRUNIT"); We are tracking it down through other .class files.

     

    If we know how to resolve “OPRUNIT” field or source of “OPRUNIT”, which is passed to OA_Job from z/OS, then it should resolve our issue..

     

     



  • 10.  Re: ESP jobs failing with operating unit issue after Oracle EBS upgrade to 12.2

    Broadcom Employee
    Posted Sep 07, 2017 05:09 PM

    As stated earlier, you need to be on 11.3 SP4 Agent for Oracle E-Business Suite which support passing the Operating Unit from the job so should be supported by the scheduler. You can open a case with support if not already.

    Support for Passing the Operating Unit



  • 11.  Re: ESP jobs failing with operating unit issue after Oracle EBS upgrade to 12.2

    Posted Sep 07, 2017 05:51 PM

    Thanks Olusegun!!

     

    We are working with support on 11.3 SP4 Agent for Oracle E-Business Suite installation.. Release doc does not specify the placeholder in OA_Job to pass Org Id; unlike Agent, OAUser. Can you please share if any new specification is available for OA_Job in SP4? Or is it derived from responsibility?

     

     OA_JOB FGAP141X
       AGENT lenlauat01
       OAUSER XXXXESP
       RESPNAME '*** AP Rent'
       PROGRAM ***_FOCUS_LOC_EXT_LX_INTFC
       APPLDISPLNAME '*** Payables'
       ARGDEFAULTS Y
       ARGS NULL
     ENDJOB

     

    Appreciate your help!!



  • 12.  Re: ESP jobs failing with operating unit issue after Oracle EBS upgrade to 12.2

    Broadcom Employee
    Posted Sep 08, 2017 11:47 AM

    I research on the org Id and found that the agent looks up the org id based on the org name.

    Query executed: select organization_id from hr_all_organization_units where name=<orgName>

    You can check with your OA admin the contents of your hr_all_organization_units table.

    Default org name can be specified at the agent level.

    Support is working with Sam on this issue via the Case.

    Thanks!



  • 13.  Re: ESP jobs failing with operating unit issue after Oracle EBS upgrade to 12.2

    Posted Sep 08, 2017 12:40 PM

    First of all, appreciate all your help in helping this with us.. Much Thanks!!

     

    Sam is working with support on same and now we are on Version R11.3, Service Pack 4, Maintenance Level 0, Build 717; as suggested. But we are still not able to crack, how to set Operating Unit which is specific to each program/job. Defaulting at agent is not feasible since it can have different value for different job and hr_all_organization_units is only validating it..

    The OPRUNIT field should store value but we are not sure how to set its value..

    orgName = p_dataExtractor.getFieldValue("OPRUNIT");

     

    Thanks,

    Shobhit