!!!EXTRACT BENEFIT PLANS
The Extract Benefit Plans (XBPN) screen is designed to extract benefit plans including their coverages from an [{$applicationname}] database.

The following information will be extracted with XBPN:
*Benefit Calendars
*Remittance Reports
*Benefit Plan Types
*Frequencies
*Change Reasons
*Employment Statues
*BC Rules
*Benefit Components
*Plan Definitions

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.

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. 

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. 

Other items that are not extracted are the plan's entry in the Benefit Schedule ([IBSC]) screen as well as any association to an Event for Open Enrollments. These can be added after the [LMDATA] has been run.

Once the XBPN function has been run, it will have created an .xml and .data file, it is suggested that the user reviews the .xml file to ensure the correct data was extracted.

The user will then load this data file into the receiving database via the [LMDATA] process.