This page (revision-7) was last changed on 26-Nov-2021 10:22 by jmyers

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
7 26-Nov-2021 10:22 3 KB jmyers to previous LOAD DATA FLDR ==> LOAD DATA FLDR(System_Preference)
6 26-Nov-2021 10:22 3 KB jmyers to previous | to last EXTRCT DATA FLDR ==> EXTRCT DATA FLDR(System_Preference)
5 26-Nov-2021 10:22 3 KB jmyers to previous | to last ATTACHMENTS FLDR ==> ATTACHMENTS FLDR(System_Preference)
4 26-Nov-2021 10:22 3 KB JEscott 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 JEscott to previous | to last
1 26-Nov-2021 10:22 2 KB JEscott to last

Page References

Incoming links Outgoing links
XBPN
XBPN

Version management

Difference between version and

At line 2 added one line
The Extract Benefit Plans (XBPN) screen is designed to extract benefit plans including their coverages from an [{$applicationname}] database.
At line 3 removed 3 lines
!!Processing Information
The Extract Benefit Plans (XBPN) screen is designed to extract benefit plans including their coverages from an Personality database.
At line 17 changed one line
Before the XBPN can be run there are [site preferences|SYSTEM PREFERENCE] that must be defined. Within the [IMST] screen, the administrator must define where the Extract and Load files are located and where the load functions are to write the exception files to. These locations are used by the functions to create and retrieve information. The customer can modify these values to represent any directory on their system.
Before the XBPN can be run there are site preferences that must be defined. Within the [IMST] screen, the administrator must define where the Extract and Load files are located and where the load functions are to write the exception files to. These locations are used by the functions to create and retrieve information. The customer can modify these values to represent any directory on their system.
At line 19 changed one line
The extract directory is defined using the [EXTRCT DATA FLDR|EXTRCT DATA FLDR(System_Preference)] preference. The load directory is defined using the [LOAD DATA FLDR|LOAD DATA FLDR(System_Preference)] preference. The [ATTACHMENTS FLDR|ATTACHMENTS FLDR(System_Preference)] must be specified so the load functions know where to write the report exceptions log to.
The extract directory is defined using the EXTRCT DATA FLDR preference. The load directory is defined using the LOAD DATA FLDR preference. The ATTACHMENTS FLDR must be specified so the load functions know where to write the report exceptions log to.
At line 21 changed one line
Lexicons, [UserCalcs|USERCALC], [pay components|PAY COMPONENTS], and [elements|PAY ELEMENTS] are not extracted with the XBPN. This means that prior to running the [LMDATA] to load the new benefit plan, any lexicons (e.g. Plan Election Set), [UserCalcs|USERCALC], [pay components|PAY COMPONENTS] or [elements|PAY ELEMENTS] associated to the benefit plan must already exist in the receiving database, otherwise the [LMDATA] will fail to load. Lexicons may be extracted via the [XMLN] function and user calcs may be extracted via the [XMUC] function. Once they have been extracted they must be loaded into the other database using the [LMDATA] prior to the new benefit plan being loaded. [Pay components|PAY COMPONENTS] or [elements|PAY ELEMENTS] will have to be entered manually.
Lexicons, UserCalcs, pay components, and elements are not extracted with the XBPN. This means that prior to running the [LMDATA] to load the new benefit plan, any lexicons (e.g. Plan Election Set), UserCalcs, pay components or elements associated to the benefit plan must already exist in the receiving database, otherwise the [LMDATA] will fail to load. Lexicons may be extracted via the [XMLN] function and user calcs may be extracted via the [XMUC] function. Once they have been extracted they must be loaded into the other database using the [LMDATA] prior to the new benefit plan being loaded. [Pay components|PAY COMPONENTS] or [elements|PAY ELEMENTS] will have to be entered manually.
At line 28 removed 16 lines
----
!!Report Parameters & Filters
||Report Parameters||
|File Name|Mandatory\\This is the name of the file that will be created by the XBPN.\\ The name should be representative of the data that is to be extracted.
||Report Filters||
|Entity|Optional, LOV Available\\This will narrow the list of benefit plans to the Entity selected.
|Remit Report|Optional, LOV Available\\This will narrow the list of benefit plans tied to the Remittance Report selected.
|Plan Type|Optional, LOV Available\\This will narrow the list of benefit plans to those tied to the selected Plan Type.
|Plan|Optional, LOV Available\\This will narrow the list of benefit plans extracted to those that are selected.
----
![Notes|Edit:Internal.XBPN]
[{InsertPage page='Internal.XBPN' default='Click to create a new notes page'}]
This page (revision-7) was last changed on 26-Nov-2021 10:22 by jmyersTop