Anyone have a PA52.1 add in template?

Sort:
You are not authorized to post a reply.
Author
Messages
Sarah
Advanced Member
Posts: 33
Advanced Member
    I have read the articles over on my lawson: 558814, 555550, and 1037326. These have been very helpful but I'm still getting the "Must Inquire before using this function code" and above it, it says "Invalid Date: f62pcteffdt".

    What am I doing wrong?  Here's my data:
    f9origco 80
    f10origee 1395
    f11origaction TER
    f12origeffdt 20120430
    f52pctco 80
    f55pctee 1395
    f58pctaction TER
    f62pcteffdt 20120430
    f63pctactionnbr 1
    _f347_hk 00800000013950000000TER201204301
    f14patfldnbr111 20
    D:1:12: f104:PCT-NEW-VALUE-11 T
    Regena
    New Member
    Posts: 3
    New Member
      When I do a PA52 upload, I have to first submit it as an "Add Only" and then, without changing the spreadsheet, submit it again as "Change Only".  Did you try this?
      Kelly H
      Veteran Member
      Posts: 167
      Veteran Member
        I believe for PA52 you have to run the add-in twice. Once to "inquire" and once to change it.

        We dont use the F62pcteffdt filed, so I can't help you there. What is the "1" at the end of your HK field? Perhaps that is throwing the date off? Our HK field ends with the YYYYMMDD.
        BarbR
        Veteran Member
        Posts: 306
        Veteran Member
          There is a new hidden key, f63 for the action number, which is part of the f348 hidden key and results in the "0001" at the end following the date.
          My add-in has:
          f52 - company
          f55 - employee
          f58 - action code
          f62 - effective date, yyyymmdd
          f63 - action number, 1
          f64 - reason code
          f72 - immediate action, N
          (f105:5 - the field I am changing)
          f9 - orig company
          f10 - org employee
          f11 - orig action code
          f12 - orig eff date, yyyymmdd
          f4 - xmit-hremp-block with value 1000000000
          f348 - hidden key with formula (if it comes across here) - IF(A8="","",RIGHT("0000"&A8,4)&RIGHT("000000000"&B8,9)&LEFT(C8&" ",10)&D8&RIGHT("0000"&E8,4))
          BarbR
          Veteran Member
          Posts: 306
          Veteran Member
            More - I just noticed that your hidden key is still mapped as f347, yet you have the new f63 hidden key and your final hidden key formula attempts to bring in the new action number.
            I think your field number mapping is off. Check each one.
            Regena
            New Member
            Posts: 3
            New Member
              Our HK field also looks different.  The first part is the same as yours, but after the five zeroes that follow the company, we have the Action Code - the one I am looking at has 8 alpha characters - since the field is 10 characters, my action code is followed by two spaced and the the date in YYYYMMDD format.
              Lisa.Cruse
              Basic Member
              Posts: 6
              Basic Member
                This year i did not have to use the hk key if i'm adding only.  on the upload tab where i clicked 'add only'  there's another box to the right where it says 'ignore pre-inquire status'.  If you check mark that, you don't have to have the key and it will upload.  You just have to make sure you have all fields that are included in the key and all data that is required by the personel action.  I also had dates in a yyyymmdd format
                Ja'Tia Thompson
                Advanced Member
                Posts: 22
                Advanced Member
                  Hello ~ I have Lawson Version 9.0.1, and I'm trying to upload pay adjustment actions into PA52.1. I think I have my mapping set correctly, and I'm getting "Add-Complete-Continue". On the surface, it looks like my entries successfully added, but the entries are not appearing in Lawson. I'm not sure why Lawson is giving me Add-Complete-Continue when my entries are not being added. I've tried clicking Add, and then Change, but that doesn't work either. I have my data mapped as follows:

                  f52, Pct-Company
                  f55, Pct-Employee
                  f58, Pct-Action-Code
                  f62, Pct-Effect-Date
                  f66, Pct-Reason11
                  (H),_f9,Orig-Company
                  (H),_f10,Orig-Employee
                  (H),_f11,Orig-Action-Code
                  (H),_f12,Orig-Effect-Date
                  f346,_HK
                  f103:0,Pct-New-Value-11
                  f103:1,Pct-New-Value-12
                  f103:2,Pct-New-Value-13
                  f103:3,Pct-New-Value-14
                  (H),_f14,Pat-Fld-Nbr-111
                  (H),_f15,Pat-Fld-Nbr-122
                  (H),_f16,Pat-Fld-Nbr-133
                  (H),_f17,Pat-Fld-Nbr-144
                  (H),_f4,XMIT-HREMP-BLOCK

                  Is there something that I'm missing?




                  Margie Gyurisin
                  Veteran Member
                  Posts: 538
                  Veteran Member
                    If you send me an e-mail, I will send you ours. mgyurisin@summithealth.org

                    We had to change a number of our field numbers when we went to 901.  I do see that you may have that issue.  For example,our HK is now f350 instead of f346
                    John Henley
                    Senior Member
                    Posts: 3348
                    Senior Member
                      The HK seems to move around, doesn't it?
                      I have done this for another client, and there's was 347 !
                      Suffice to say, you need to re-check these anytime a screen change is made to PA52.
                      Here are some notes I have:
                      Make sure you have the correct PADICT field-number mapped to the PAT-FLD-NBR-xx (I used 62 for PayRate).
                      I recommend uploading one field at a time rather than four at a time.
                      Lastly, on the upload screen, select “Add Only” to upload the selected rows, and “Let Add Ins Decide” under other options.
                      DO NOT USE "IGNORE PRE-INQUIRE STATUS"
                      Thanks for using the LawsonGuru.com forums!
                      John
                      Kelly H
                      Veteran Member
                      Posts: 167
                      Veteran Member
                        Another question in relation to the PA52.1 add in - we have one that works and works well. However, I am currently trying to load new job codes using this addins. We are getting the soft warning "outside of salary range". And then it doesnt load the PA52. Is there any way I can override that soft warning? Unfortunately I about 300 changes coming up and about half will probably be outside of the salary range until we finish their changes.
                        Margie Gyurisin
                        Veteran Member
                        Posts: 538
                        Veteran Member
                          We recently did that. There is a nice KB article with the necessary hidden keys values that are needed to override that message on xtreme.
                          Dave Curtis
                          Veteran Member
                          Posts: 136
                          Veteran Member
                            The field XMIT_HREMP_BLOCK is used to overide or ignore the PA52 warnings.
                            The first digit means ignore ALL 7 warnings.
                            To ignore specific warnings you must format the field accordingly.

                            1 - Ignore ALL (1000000000)
                            2 - SSN is same as another employee (duplicate) (0100000000)
                            3 - Invalid SSN (0010000000)
                            4 - Rate out of Pay Range (Over or Under) (0001000000)
                            5 - Currency with unended PR rates (0000100000)
                            6 - Currency some amounts not changed (0000010000)
                            7 - Tax locator error (0000001000)
                            8 - Work Country is invalid (0000000100)
                            9 - K12 Position Invalid (0000000010)
                            10 - Not Currently Used (Not used)

                            You can mix and match as needed - so if you need to ignore 2 and 4 you would format the field as
                            0101000000

                            Honestly - I have never seen the first spot - Ignore all - actually work like it says it should. Unless I specifically want to allow one of the error messages - I usually put in 1111110000
                            Kelly H
                            Veteran Member
                            Posts: 167
                            Veteran Member
                              Thanks Margie and Dave.  Your suggestions enabled me to run the add-ins. 
                              Merrill
                              Posts: 3
                                Hello... I am reading over the postings and I am still not able to get my Rate Action to add.  I continue to get Must Inquiry first.   Working with Portal in debug to confirm fields and values as we know field numbers appear to change I continue to get Inquiry.  Anyone will to share?
                                Kelly H
                                Veteran Member
                                Posts: 167
                                Veteran Member
                                  merrill - what fields do you have on your add-ins?
                                  stephanie
                                  Veteran Member
                                  Posts: 330
                                  Veteran Member
                                    Here's the one I've used - you'll want to check the field numbers (I don't know what version you're on).  And as multiple peeps said - you need to add the file first, make no changes, then upload again as changes.  Good luck!!
                                    Attachments
                                    Merrill
                                    Posts: 3
                                      What really helped was via portal using the CTRL-SHFT -V on the form to determine the required fields. This pointed out the new requirements of the Action number for the Hidden Fields. Running Portal in debug mode also shows the new value in the hidden key. The challenge than was to confirm the format as Portal was showing all zeros on the load; however, we now the first one is always one. And then adding the action number as field in the upload as well.
                                      Merrill
                                      Posts: 3
                                        What really helped was via portal using the CTRL-SHFT -V on the form to determine the required fields. This pointed out the new requirements of the Action number for the Hidden Fields. Running Portal in debug mode also shows the new value in the hidden key. The challenge than was to confirm the format as Portal was showing all zeros on the load; however, we now the first one is always one. And then adding the action number as field in the upload as well.
                                        Shane Jones
                                        Veteran Member
                                        Posts: 460
                                        Veteran Member
                                          There was a PA52 Webinar put on by Infor back on February 19th and I think they said it was being recorded...    It was very helpful.
                                          Shane Jones
                                          Tools: HR, Payroll, Benefits, PFI, Smart Office, BSI, Portal and Self-Service
                                          Systems: Lawson, Open Hire, Kronos, Crystal Reporting, SumTotal Learning
                                          ** Teach others to fish...
                                          You are not authorized to post a reply.