Anyone use BN531 to import new plan?

 3 Replies
 0 Subscribed to this topic
 68 Subscribed to this forum
Sort:
Author
Messages
Sarah
Advanced Member
Posts: 33
Advanced Member
    My question is...what fields are needed in order to do the BN531 ?

    We are taking two suplife insurance plans and combining them into 1 suplife plan so we can utilize automation rules because the only reason these two plans existed was to identify the executives with the correct limit amount.  We have been able to nest the exe rules within 1 plan and planned to roll this new plan out OE 2012. 

    The suplife plan isn't really changing it's just how we have the information warehoused; plan A and plan B(exe) are how they are set up and assigned to ee's in Lawson today with plan B being the executives plan.  We want to combine them into 1 plan, plan C, so that we can use automation rules if someone gets promoted or demoted to an executive level Lawson would still give them the proper limit amts.

    EOI is our issue...if we wait till OE and have all of our ee's elect suplife even if they already have say, 4x their salary, since they are selecting a new plan (it looks new to Lawson) for 4x their salary, Lawson is going to think this ee needs EOI and they don't.  So, to avoid this issue of EOI we want to end date the current plans effective dated 09/30/2011 and start with the new plan C effective start date 10/01/2011 which is a month before our OE.
    I am testing the BN103 to mass enddate the old plans and that appears to work okay and I can export these ee's to a csv file.  I read in the Benefits Administration Guide 9.01 ch 17, page 276, that you can use the BN103 in conjunction with the BN531 to end date an existing plan and import the new plan.  Just curious about the fields for the BN531 and if anyone has done this?

    TIA,

    S
    Margie Gyurisin
    Veteran Member
    Posts: 538
    Veteran Member
      You can run the BN103 with the option to create csv. This file will be in the format needed for import via the BN531 with some changes to the file. You will need to change the start date, remove the end date, most likely change the plan name etc. If you compare it to the file specs for the BN531, you will see what I mean. I would also make sure to test the process bedore running in LIVE.
      Sarah
      Advanced Member
      Posts: 33
      Advanced Member
        Thank you Margie. I've changed the plan code name, removed the stop dates but left the field, changed the start date and saved it as a csv file. Now, I just need to figure out where Lawson pulls this import from.
        Margie Gyurisin
        Veteran Member
        Posts: 538
        Veteran Member
          That should also be in the conversion documentation. I believe it is the work directory BNBATCH by default. Depending on your setup, you can change the default directory per job name.