Prev
Next
Forums Integration / Customization IPA/ProcessFlow

PF AGS Error When Unreleasing a JE Via A Generic PF

 4 Replies
 0 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
LCM
Basic Member
Posts: 8
Basic Member
6/15/2009 8:16 PM

     

    Hi, we are experiencing an error with a PF when we attempt to unrelease a JE via a flow (DS 9.0.0.5). The code that we are trying to use to do this comes from a provided Lawson ProcessFlow solution and is unmodified (but not supported by Lawson). In the Lawson solution for Journal Entry Approval the final node when a JE is rejected unreleases the journal. The call to do this in the Lawson solution is:
     
    _PDL=&_TKN=GL45.1&_EVT=CHG&_RTN=DATA&_LFN=ALL&_TDS=IGNORE&FC=Change&GLC-COMPANY=&GLC-FISCAL-YEAR=&GLC-SYSTEMr0=&GLC-CONTROL-GROUPr0=&PT-GLC-SYSTEM=&PT-GLC-JE-TYPE=&PT-GLC-CONTROL-GROUP=&_DELIM=%09&_OUT=TEXT&_EOT=TRUE&LINE-FCr0=U
     
    All of the variables are derived from the Lawson generic triggers built in to various GL forms and have not been modified in any way by us. A sample of the call with data from our flow is:
     
    Transaction Call String _PDL=PROD81&_TKN=GL45.1&_EVT=CHG&_RTN=DATA&_LFN=ALL&_TDS=IGNORE&FC=Change&GLC-COMPANY=0010&GLC-FISCAL-YEAR=2009&GLC-SYSTEMr0=GL&GLC-CONTROL-GROUPr0=00004000&PT-GLC-SYSTEM=GL&PT-GLC-JE-TYPE=N&PT-GLC-CONTROL-GROUP=00004000&_DELIM=%09&_OUT=TEXT&_EOT=TRUE&LINE-FCr0=U
    Error while Executing activity : Type=AGS, ActivityName=Unrelease, ActivityId=AGS61, WorkUnit=7216 Date:06/15/2009 Time:12:07:45
     
    Then a long error message is returned. The first few lines are below:
     
    AGS error details: com.lawson.tesla.agent.TransactionException: Error occurred while performing transaction          at com.lawson.tesla.exec.Tesla.invoke(Tesla.java:332)          at com.lawson.tesla.agent.ErpTransactionAgent.processRequest(ErpTransactionAgent.java:181)         at com.lawson.ios.agent.container.AgentContainerImpl$AgentWrapper.processRequest(AgentContainerImpl.java:467)   at com.lawson.tesla.broker.TransactionBroker.processRequest(TransactionBroker.java:80)      at
     

    The AGS call to GL41.4 that occurs in the previous node of this PF does correctly update its field so the issue is just with the AGS call to GL45.1.  This PF solution was produced a while ago so my assumption is that there has been a change to GL45.1 since then that would cause this issue but I don't know what to look at.  Have any of you built a PF that can successfully unrelease a journal entry?  I would appreciate any advice that anyone can offer on this issue.  Thanks!

    Gary Davies
    Veteran Member
    Posts: 248
    Veteran Member
    6/16/2009 11:59 AM
      The format of the AGS call is correct and works fine for me on 9.0.1 SP2 environement,  9.0.4 Apps.
      TracyO
      Veteran Member
      Posts: 97
      Veteran Member
      6/16/2009 1:06 PM
        WE aer in the process of upgrading to 9.0 our processflow version is the same as yours 9.0.0.5. In converting my flows, I ran across several issues with AGS calls. I was not specifically doing what you are but think maybe it is related.
        In the AGS calls I am using in my flows I had to change them to include other fields (Lawson says currently you need to include ALL fields in the AGS calls) . What I had to include where the "required" fields when I was doing an add, and I could not use the field name I had to use the f_# for the field. I have had other issues with the query builder and other of my AGS calls.
        After spending several hours trying to figure out what it was that I was not doing right, Lawson said that these are KNOWN problem with the AGS calls in processflow. The have a PT 17360 to fix the AGS calls. I am guessing that when they fix the AGS in processflow your call should work. I would recomend opening an LIS with Lawson, as the more people that are having AGS issues the quicker they may resolve the PT.
        LCM
        Basic Member
        Posts: 8
        Basic Member
        6/16/2009 3:06 PM
          Thanks for the responses Gary and Tracy. Incidentally, I tried this in a different test region in which we have additional environmental patches and got different results using the same flow.

          Original results included in this case:
          Journal Entry not unreleased, error message, flow status = Complete

          Other test region:
          Journal Entry successfully unreleased, similar error message, Flow status = Failed

          Both results are repeatable. So when the AGS update is successful we get a failed message and when it does not work we get a completed message! We have not experienced this issue with any other AGS calls either in this flow or in other flows. I will open a support case with Lawson and look in to the PT. Thanks for all of the information guys. I will report back with the resolution to this issue when it is found.
          LCM
          Basic Member
          Posts: 8
          Basic Member
          6/17/2009 8:19 PM
            There was a CTP that was created specifically for this issue on GL45 (CTP # 44660). I can confirm that the CTP did resolve this issue as the unmodified AGS calls now work.