This page (revision-8) was last changed on 26-Nov-2021 10:22 by Kevin Higgs

This page was created on 26-Nov-2021 10:22 by JEscott

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
8 26-Nov-2021 10:22 2 KB Kevin Higgs to previous
7 26-Nov-2021 10:22 4 KB jtolentino to previous | to last Changed Apostrophe on Rec 30, Field 1 of first IDIF.
6 26-Nov-2021 10:22 4 KB jtolentino to previous | to last Added approvals, loading requirements, and override information.
5 26-Nov-2021 10:22 4 KB rmorrell to previous | to last
4 26-Nov-2021 10:22 4 KB khiggs to previous | to last
3 26-Nov-2021 10:22 2 KB JEscott to previous | to last
2 26-Nov-2021 10:22 2 KB RForbes to previous | to last
1 26-Nov-2021 10:22 2 KB JEscott to last

Page References

Incoming links Outgoing links
LOADING ELECTIONS AND COMPONENT AMOUNTS INTO IBEL
LOADING ELECTIONS AND COMPONENT AMOUNTS INTO IBEL

Version management

Difference between version and

At line 1 changed one line
Here is the minimum set up required to load elections with a BC code value via [LBEN]. The load file is a comma delimited format.
This is a sample of theminimum set up required to load elections with a BC code value via [LBEN].
At line 3 changed one line
If Approval Required is set to 'Approval Required' on IBPN, an approval is needed before a plan is enrolled.
*The load file in the sample is a comma delimited format, but fixed position files are also supported.
*If 'Approval Required' has been set up on IBPN, the approval process must be established on [IDAP] prior to the load taking place.
*Loading benefits is limited to only the current employment. This can include employments with a termination date.
*This interface will only allow 1 BC code to be updated. If more than 1 BC code is to be populated - the LBEN process cannot be used.
\\
At line 5 changed 3 lines
__Note__: Loading is limited to only the current active employment only. Loading will also not work if there is a Termination Date. Attempting to load another Benefit Component overage amount will override the previous amount, even if it is a different Benefit Component.
__SAMPLE INTERFACE__
At line 21 removed one line
Here is an example of an interface that was done for a specific client. The load file is a fixed format, and is used to load employee elections and component amounts into [IBEL].
At line 23 removed 22 lines
||Rec\\#||Field\\#||Name||Beg\\Pos||End\\Pos||Constant\\Value||Derivation\\Expression||Notes
|0| 0| HEADER RECORD*| 0| 0| | |Since there is 1 header record in the file, one field must be defined in the interface for the header record.
|1| 1| BEL.BPN_ID.PLAN_CODE| -1|-1| |{{{P2K_SMGLX('GWRS_PLAN_TRNSLT',~)}}}|The derivation will translate the policy number in the file to the plan code using a user defined lexicon.
|1| 2| BEL.EEM_ID.EID_ID.PERSON_CODE| -1|-1| |{{{ LTRIM(~,'0')}}}|The person code will be trimmed of any leading zeros.
|1| 3|BEL.EEM_ID.TERMINATION_DATE|-1 |-1| ‘’| |The constant value of two quotation marks (no space) is used to determine a NULL termination date which will be the ACTIVE employment
|1| 4| BEL.ELECTION_STATUS| -1 |-1| 00| | The election status will be hard coded to Not Yet Elected, LBEN will then elect and enroll the employee. Since this field does not have a value within the file, it has been defined with -1.
|1| 5| BEL.BCG_ID.COVERAGE_CODE| -1| -1| |{{{ P2K_SMGLX('GWRS_PLAN_TRNSLT',~)}}}| Since both coverage code and plan code are the same for these plans, the derivation expression from plan code field may be used. Since this field does not have a value within the file, it has been defined with -1.
|1| 6| BELC.BBC_ID.BC_CODE| -1| -1| B1000| | Hard coded to B1000 so the system know which BC Code to update. Since this field does not have a value within the file, it has been defined with -1.
|1| 7 |BELC.AMOUNT_OVERRIDE |-1| -1| |{{{ TO_NUMBER(~)/10}}} |This field will pick up the amount from the flat file.
|1| 8 |BEL.BE_EFFECTIVE_DATE|-1|-1| |{{{NLV2(~,(to_char(to_date(rtrim(~),\\’YYYMMDD’),’DD-Mon-YYYY’)),’01-Jan-0001’)}}} |
|1| 9| BEL.F_QUALIFIER*** |-1| -1| TRUE| {{{ CASE
When (:BELC.AMOUNT_OVERRIDE)=’0000’
then ‘FALSE’
else ‘TRUE’
end }}}|Do not process records with zeros – these are for unenrollments
|2| 0| TRAILER RECORD**| 0| 0| | | Since there is 1 trailer record in the file, one field must be defined in the interface for the trailer record.
;:*Record 0, Field 0 must have a Record Type of 'Header Record'
;:**Record 2, Field 0 must have a Record Type of 'Trailer Record'
;:***Record 1, Field 9 must have a Record Type of 'Qualify Record'
This page (revision-8) was last changed on 26-Nov-2021 10:22 by Kevin HiggsTop