PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 06/09/2015 6:15 PM by  Tim Cochrane
HR11 AGS call
 11 Replies
Sort:
You are not authorized to post a reply.
Author Messages
JimK
Private
Private
Basic Member
(24 points)
Basic Member
Posts:10


Send Message:

--
05/12/2015 2:09 PM

    Hi,

    We have a framework written in .NET (C#) that we've used in the past for adding and updating Lawson billing info.  The framework has allowed us to execute Transaction (AGS) and Data (DME) calls, and has worked very well.

    We now look to take a new hire feed from our Talent Management system, and automatically create HR11 records within Lawson.

    The HR11 AGS call is posing difficulties, though.  It appears that after we make the HR11 call, to form is expecting us to add tax deductions via the PR13.3.  When we manually create HR11 records via portal, the PR 13.3 form appears after you've clicked add - it prompts you to confirm the effective date for the benefits.

    I am able to use MS Add-Ins to create the HR11 records, so it definitely seems like it can be done outside of Portal.  Have tried to look at the AGS call string from within Add-Ins after adding the HR11, but the string appears generic - no data (name, status, etc.) is present from info that was passed in.  It appears that this might be the last of several calls required to perform the HR11 add.

    So, does anyone have any advice on performing and HR11 AGS call to add an employe and then create the tax deductions?

    Thanks!

    Woozy
    Private
    Private
    Veteran Member
    (3487 points)
    Veteran Member
    Posts:707


    Send Message:

    --
    05/12/2015 3:18 PM
    Hi JimK - this doesn't really answer your question, but I'm curious why you wouldn't use the delivered TM to S3 interface. Are you not licensed for IPA? If you don't go that route, I'd still think you'd want to use a PA52 (or LT11) action to create/update the S3 employee so you will have the appropriate security and history tracking.

    If TM is your system of record, trying to manage that with AGS queries is going to be really painful.

    Kelly
    Kelly Meade
    J. R. Simplot Company
    Boise, ID
    JimK
    Private
    Private
    Basic Member
    (24 points)
    Basic Member
    Posts:10


    Send Message:

    --
    05/12/2015 4:11 PM
    Hi Kelly,

    Thanks for the quick response!

    The talent management solution our HR group selected is 'Cornerstone On Demand'. Thus, I do not have a native interface into Lawson. The first module we are implementing is recruiting (think they call it ATS).

    We had Infor Process Automation in the capital budget last year, but unfortunately it was cut. Would have loved to used IPA, though.

    Am drawing a blank about why we are not using the PA52 - am in IT, and will have to loop back with the HRIS manager.

    We currently have a homegrown eRecruiting system that Cornerstone will replace - do believe that the interface for that writes PA52 records. Am thinking HR may have shied away from the PA52 as all requisition and applicant info will originate in and be maintained in Cornerstone.

    Thanks!
    Jim Krzyzewski
    American Medical Association
    Chicago, Illinois
    Woozy
    Private
    Private
    Veteran Member
    (3487 points)
    Veteran Member
    Posts:707


    Send Message:

    --
    05/12/2015 4:32 PM
    Hi Jim,

    That makes sense - when you said "Talent Management" I assumed you meant "Infor Talent Management". Since that isn't the case, the delivered interface wouldn't have helped you anyway. PA52 may not be an option if you aren't licensed for that module. Unfortunately, we strictly avoid doing AGS updates to anything except PA52 (which is challenging enough), so I can't provide any more insight into what you're doing. Hopefully someone else will chime in.

    Good Luck!

    Kelly
    Kelly Meade
    J. R. Simplot Company
    Boise, ID
    Tim Cochrane
    Private
    Private
    Veteran Member
    (450 points)
    Veteran Member
    Posts:154


    Send Message:

    --
    05/12/2015 7:04 PM
    Jim - do you have the "xmit" blocks included in your AGS?? The xmit blocks basically tell Lawson to bypass/ignore any edits, getting around those pesky "are you sure" edits.
    I will PM you a sample in the AM.
    Tim Cochrane - Principal LM/IPA Consultant
    JimK
    Private
    Private
    Basic Member
    (24 points)
    Basic Member
    Posts:10


    Send Message:

    --
    05/13/2015 9:47 AM

    Thanks Tim - appreciate your response!

    Have not used 'XMIT' blocks - am eager to see how this works.

    When I manually add an employe via the HR11, after I click 'Add' on the HR11, it takes me to the PR13.3 to confirm effective date for tax deductions - I don't enter anything, just click on 'OK' to confirm date.

    Think the 'XMIT' will take care of this?

    Thanks!

    Jim K.

    JimK
    Private
    Private
    Basic Member
    (24 points)
    Basic Member
    Posts:10


    Send Message:

    --
    06/04/2015 6:14 PM
    Hi Kelly,

    Am hoping you see this post.

    After no luck with the HR11, am now trying to use the PA52.4 to add the employee.

    Am having issue whereby when I make the 'Add' AGS call to the PA52.4, the message being returned is:

    <_HK>0100000023361HIRE JOB 20150601
    Must inquire on code before adding
    010
    001
    _f1


    Saw a post about needing to pass the '_HK' value in with the call in order to not get this message - still receive same error message. I'm pretty sure the syntax of the '_HK' value is correct, as I copied the value directly from the return shown above.

    When I am creating the AGS call, am passing in the key values (company, applicant, action code, requisition, and effective date), and simply the values I want to set on the tabs (e.g. - 'PCT-NEW-VALUE-1r1=PFA'). I also am doing a direct 'Add' with the call - not an 'Inquire' before hand. Does this sound right?

    Thanks!
    Jim K.
    Tim Cochrane
    Private
    Private
    Veteran Member
    (450 points)
    Veteran Member
    Posts:154


    Send Message:

    --
    06/05/2015 6:56 AM
    JimK - i don't recall what every flag in the xmit-block will bypass...it should be spelled out in the PA52WS, look for the XMIT-BLKs, it'll show how many flags go with each block (i want to say 8 flags/block). There are also 2-3(?) different blocks...1 for PA edits, another for HR edits, etc. Set them all to "1" in your AGS and give it a shot.
    Tim Cochrane - Principal LM/IPA Consultant
    BarbR
    Veteran Member
    (888 points)
    Veteran Member
    Posts:306


    Send Message:

    --
    06/05/2015 7:18 AM
    I have a process flow that successfully adds the New Hire actions to PA52.4. First, it is important to use EVT=CHG, not ADD, with a FC=A. We do not use an HK in our transaction string. Our XMIT block is XMIT-HREMP-BLOCK=0001111100. We also have FROM-WORKFLOW=Y at the very end. I hope this helps.
    JimK
    Private
    Private
    Basic Member
    (24 points)
    Basic Member
    Posts:10


    Send Message:

    --
    06/05/2015 2:26 PM
    Hi Barb and Tim,

    Success! I have the PA52.4 working properly from my AGS call. The trick was to add the '&_EVT=CHG' to the call.

    The weird thing is that on all AGS calls I've previously coded, I did not include this parm, and they worked fine.

    Even when I was running Fiddler to watch the requests and responses, did not ever see the EVT stuff in the call.

    Also, for my call that worked, I did not need the HK, XMIT-HREMP-BLOCK, for FROM-WORKFLOW parms.

    Thanks all for your help - am very excited right now that I have this working!
    JimK
    Private
    Private
    Basic Member
    (24 points)
    Basic Member
    Posts:10


    Send Message:

    --
    06/08/2015 12:32 PM
    A follow-up - was able to finally get the HR11 'Add' AGS call I was originally after to work, as well.

    Determined I needed to include the following field to bypass the PR13.3 form:

    _txnFields += "&PT-FROM-PR134=1";

    Also included the XMIT-HREMP-BLOCK to bypass warning messages:

    _txnFields += "&XMIT-HREMP-BLOCK=1000000000";

    Figured this out by building an HR11.1 Add-Ins 'Upload Query'.

    Then dissected resulting AGS call via ‘View the last Upload Query sent’ to determine which fields it was passing that I was not.

    After that, removed additional fields one by one until I could determine which field did the trick.

    Lo and behold, it was the 'PT-FROM-PR134=1' clause.

    Am very happy now, as I have a programmatic way to successfully execute HR11.1 AGS calls!
    Tim Cochrane
    Private
    Private
    Veteran Member
    (450 points)
    Veteran Member
    Posts:154


    Send Message:

    --
    06/09/2015 6:15 PM
    Good job Jim
    Tim Cochrane - Principal LM/IPA Consultant
    You are not authorized to post a reply.