Prev
Next
Forums S3 Customization/Development

Invoking PR36

Sort:
You are not authorized to post a reply.
Author
Messages
Garry Ferwerda
Basic Member
Posts: 20
Basic Member
7/26/2012 6:52 PM
    Hi all: I am writing a 4gl program to take multiple hours only pay code time records and creating one or more 'pay' time records out of them.  I was hoping to invoke PR36 to create the time records.  The form seems fairly uncomplicated with only a minimum number of fields required.   But I cannot get it to work,  I invoke the form and I can retrieve the employee name so I know that the form did something but I get a return code fo zero and no time records created.   Has anyone invoked on PR36 before?   What did you have to do to get the form work?
    Karen Sheridan
    Veteran Member
    Posts: 141
    Veteran Member
    7/26/2012 7:31 PM
      Garry,
      I have never done this. But, I do have a couple of questions. Lawson delivers a batch timerecord import (PR530). Could your 4GL program create a CSV file instead. Since INVOKE doesn't include field editing, that might be the safer way to approach it.

      From the App Dev workbench standards:
      At this time, INVOKE processing does not include field editing, defaulting, or form rule
      processing that is implicit to using the Lawson Presentation Manager (lapm) or the
      Lawson Portal. It is essential that all of the $TRANS fields are correctly loaded or
      initialized before activating a program using an INVOKE statement.

      Having said that - did you check to make sure the PR36 INVOKE flag in pgmdef is set to yes? Our is not - we are 9.0.0 APPS

      Karen
      Ragu Raghavan
      Veteran Member
      Posts: 468
      Veteran Member
      7/26/2012 7:47 PM
        Are you by any chance INITIALIZING PR36F1 before the INVOKE ?

        Try forcing in a value of 11 into PR36F1-DETAIL-SIZE and if that is not enought 1 into PR36F1-DETAIL-SIZE-FN.
        Garry Ferwerda
        Basic Member
        Posts: 20
        Basic Member
        8/1/2012 11:59 AM
          That is the approach I eventually took.   I was trying to avoid adding more steps to the payroll process.  My final solution was to create a multi-step job for my custom program and the pr530.  And then Payroll will have to run another pr137 to release the newly created batch.
          Garry Ferwerda
          Basic Member
          Posts: 20
          Basic Member
          8/1/2012 12:01 PM
            I was doing an initial inquiry with just the company and employee values.  I hadn't tried setting the detail area size and FN.   I will have to try that just to see if that works.

            Thanks.
            LauraP
            Advanced Member
            Posts: 28
            Advanced Member
            8/3/2012 1:16 PM
              Gary -

              I have written several Lawson programs that do invokes to various Lawson forms (Payroll, Inventory Control, Order Entry screens for example).

              I'd be more than happy to try to help you offline if you want to email me directly.

              lpatena@yakeecandle.com

              Thanks,
              Laura
              You are not authorized to post a reply.