BN32 Change with Addin

 10 Replies
 0 Subscribed to this topic
 68 Subscribed to this forum
Sort:
Author
Messages
Margar
New Member
Posts: 3
New Member
    We are in process of upgrading from 8.0 apps to 9.0.1. I have an add in to upload BN32 changes for DC plan and it is not working correctly in 9.0.1. Does anyone have an add in for changes to BN32?

    Thanks
    Ashby Judy
    Basic Member
    Posts: 9
    Basic Member
      You may want to check out the following site:

      http://solutions.lawson.com/lu/addins/main.htm
      Karen Ploof
      Veteran Member
      Posts: 118
      Veteran Member
        Have you fixed you BN32 upload? If not, have you remapped the fields? There were fields added to the BN32 reocrd, so it's likely that field numbers changed.
        Shane Jones
        Veteran Member
        Posts: 460
        Veteran Member
          I have had some luck updating records on BN32 but it is one of the more complex forms to update with Add-ins or Processflow. CTRL+SHFT+A ... or is it CTRL+ALT+A... cant remember which but one shows information in portal that is helpful for finding the hidden feilds. for a form.
          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...
          Margar
          New Member
          Posts: 3
          New Member
            Had to add new fields for start/stop dates for the new deduction tab. Is working correctly now. field #'s 72 and 73.

            thanks
            Margarita
            vc727
            Advanced Member
            Posts: 44
            Advanced Member
              I am trying to stop some life plans for a large number of employees but when I follow the mapping in the example I just succeed in stoping the first plan on the screen. How do you get it to look at the correct plan. If I map the plan code field it tells me I can't change it. Did you have more than one benefit on the screen you were stopping?
              Margie Gyurisin
              Veteran Member
              Posts: 538
              Veteran Member
                Could the BN103 work for you by using some of the parameters available in that screen? You could also use it to stop everyone with the csv option and then reload those you still want to be in the plan from the csv file using the BN531.
                vc727
                Advanced Member
                Posts: 44
                Advanced Member
                  What we are trying to do is temporarily stop all Life and disability plans the were added during annual enrollment that will require an Evidence of Insurability/ Personal Health Statement before they can take effect. What we do is put the start and stop date the same and remove the stop date when we are notified by the insurance carrier that they are eligible. That way they are not paying for coverage they don't really have. My understanding is that bn103 would delete the record. We tried that. I can get addins to put a stop date in the first record but these plans are all across the screen. I need help with mapping the correct "Position to" fields the ones in the example only bring up the correct employee and benefit year not the specific benefit.
                  stephanie
                  Veteran Member
                  Posts: 330
                  Veteran Member
                    BN103 doesn't delete the record - it just puts the end date on the benefit. The form help for that program is actually extremely detailed and helpful.
                    Karen Ploof
                    Veteran Member
                    Posts: 118
                    Veteran Member
                      I agree with Stephanie. Unless we're missing something, BN103 should get you what you want with very little work -- unless it deletes the record because the start and stop dates are the same. I've never tried run it where the dates are the same.

                      If you want to continue working with BN32, here are a few thoughts:

                      1) BN32 is one of those forms that require you do an "inquire" before processing any changes, which means there will be hidden fields that need to be mapped to associate the change with the correct record. I would start with the HK field. If it includes the plan type, plan code and enrollmen start date fields, you might get away with mapping just that addiitonal field.

                      2) If mapping the HK field does not work, look for other hidden fields for Plan Type and Plan code and map them along witih the other "Position to" type fields.

                      Let me know how it goes.
                      MARCO3535
                      Advanced Member
                      Posts: 25
                      Advanced Member
                        FYI --> the link noted in this topic has been disabled...