A member can have one active pension record and any number of deferred or pensioner records. During the phased migration period, a member could have a record on Vision and a record on Penserver. If the member has a record on Vision and records on Penserver, any changes in the member personal details must be updated on Vision via SAP and a file of the changes created and interfaced to Penserver.
Two separate files will be created for member data updates and address data updates.
The following values are available for selection from the Interfaces Parameter Sub-Type:
- MEMDATAPENSERV
- ADDRESSPENSERV
- PENSERVCONTROL
The following Global Parameters with a Parameter Type of INTERFACES and the following Parameter Sub-Types are available:
- MEMDATAPENSERV
- ADDRESSPENSERV
- PENSERVCONTROL
The following Batch Parameters have been created to define each of the directories in which to create the Member Data and Address Data files respectively:
- MEMDATAPENSERV
- ADDRESSPENSERV
- PENSERVCONTROL
The following translation values are used to translate the values from the Vision value to the PenServer value:
|
Translation Purpose |
Source System ID |
Source System Attribute |
Target System ID |
Target System Attribute |
|
INTERFACE1 |
IN.PENSIONS |
TITLE |
PENSERVER |
TITLE |
|
INTERFACE1 |
IN.PENSIONS |
SEX |
PENSERVER |
SEX |
|
INTERFACE1 |
IN.PENSIONS |
MARITAL STATUS |
PENSERVER |
MARITAL STATUS |
|
INTERFACE1 |
IN.PENSIONS |
ADDRESS TYPE |
PENSERVER |
ADDRESS TYPE |
|
INTERFACE1 |
IN.PENSIONS |
ADDR COUNTRY |
PENSERVER |
ADDR COUNTRY |
Extract
A batch job will run daily after the Daily Confirm on Payroll to extract the changes to Person Details.
When the batch job runs, the system will find all of the Personal Detail records on the Interface to Core table for which the timestamp is greater than the Timestamp on the Global Parameter record with a Parameter Type of INTERFACES and a Parameter Sub- Type of MEMDATAPENSERV.
The system will find the Membership records linked to the Person and read the Notation records linked to the Membership. If a Notation Record is found with a Type of OTHER MEMBSHIP and for which the Status is not COMPLETED, the following details will be extracted:
- Member Number (Line Text of Note Detail of Notation record)
- Identity Number
- Surname
- First Name 1
- First Name 2
- First Name 3
- Title
- Sex
- Marital Status
- DOB
- Preferred Name
The Member Number of the linked membership will be contained in the first Line Text of the Note Detail linked to the Notation record with a Type of OTHER MEMBSHIP.
Note:
A note header of OTHER MEMBSHIP is used to highlight that a member has a record on another system. The first note detail line must ONLY contain the reference number and it must be in the first position with no leading spaces. Once memberships have been migrated from Penserver, a bulk upload of Notes will be done with a Header of OTHER MEMBSHIP and the reference number in the first detail line, and a Status of COMPLETED.
File
A batch parameter with a Transaction Code of MEMDATAPENSERV and Description of DTUIP59385_ will be used.
A CSV file with the name; MemberABSACCYYMMDD_Sq.csv prefixed with the value for the batch parameter MEMDATAPENSERV will be created, where:
- CCYYMMDD = The day of the month that the file is created
- Sq = The sequence number of the file.
Note:
This sequence number is stored in the same place as the existing outgoing SAP interface sequence numbers.
Example: DTUIP59385_MemberABSA20100716_123.csv
The sequence number is used to ensure that the file is received in the correct sequence and is only loaded once. The sequence number will be stored on the Global Parameter with a Parameter Type of INTERFACES and Parameter Sub-Type of MEMDATAPENSERV, and will be incremented each time a file is created.
Each file must contain a header record (record type 1) and individual record details (record type 2).
No trailer record is required. A separate control file needs to be sent together with the file.
Header Record
The header record must be the first record in the file and in the format as per the table below.
|
Data Item |
Data Type |
Length |
Description |
Default Value |
Mandatory/Optional |
|
Record Identifier |
Integer |
2 |
|
01 |
M |
|
Importer Identifier |
String |
15 |
Used to indicate who has submitted the file |
ABSA |
M |
|
Sequence |
Numeric |
15 |
File sequence number |
|
M |
|
File Creation Date |
Date DDMMCCYY |
8 |
Date that the file was created |
|
M |
|
File Creation Time |
Time HHMMSS |
6 |
Time that the file was created |
|
M |
|
Resubmitted Indicator |
Logical |
1 |
Logical indicator that indicates if the file has been resubmitted. This would be a manual intervention if a Y. |
N |
O |
Header Example: 01,ABSA,01,07062010,070059,N
Member Data Record
The Member Data records must be in the format as per the table below.
|
Data Item |
Data Type |
Length |
Vision / Default Value |
Mandatory/Optional |
|
Record Identifier |
Integer |
2 |
02 |
M |
|
Member Number |
Number |
22 |
Value in the first detail line of the notation record with the header of ‘OTHER MEMBSHIP’. Place the number into this field. If there is an error in the conversion from text to numeric, then write out an error to the error log and stop the process as there would be no other way to re-extract this data. |
M |
|
National Insurance Number |
Varchar2 |
9 |
Identity Number |
M |
|
Surname |
Varchar2 |
25 |
Surname |
M |
|
First forename |
Varchar2 |
17 |
First Name 1 |
M |
|
Second forename |
Varchar2 |
17 |
First Name 2 |
O |
|
Third forename |
Varchar2 |
17 |
First Name 3 |
O |
|
Title |
Varchar2 |
4 |
Read the Translation Value with a Translation Purpose of INTERFACE1 and with a Source System ID and Source System Attribute of IN.PENSIONS and TITLE, and a Target System ID and Target System Attribute of PENSERVER and TITLE. Find the Target System value for the Source System Value equal to the value extracted for Title. |
M |
|
Current sex/Gender |
Varchar2 |
1 |
Read the Translation Value with a Translation Purpose of INTERFACE1 and with a Source System ID and Source System Attribute of IN.PENSIONS and SEX, and a Target System ID and Target System Attribute of PENSERVER and SEX. Find the Target System value for the Source System Value equal to the value extracted for Sex. |
M |
|
Marital status |
Varchar2 |
2 |
Read the Translation Value with a Translation Purpose of INTERFACE1 and with a Source System ID and Source System Attribute of IN.PENSIONS and MARITAL STATUS, and a Target System ID and Target System Attribute of PENSERVER and MARITAL STATUS. Find the Target System value for the Source System Value equal to the value extracted for Marital Status. |
M |
|
Member’s date of birth |
Date |
10 |
DOB (DD/MM/CCYY) |
M |
|
Member’s preferred name |
Varchar2 |
27 |
Preferred Name |
M |
Note:
Where no entry is required in a particular field this must be populated with asterisks e.g. if no entry is required in the Third Forename field it must be populated with 17 asterisks. If it is not filled with asterisks the original value will remain in Penserver.
The system will read the batch parameter MEMDATAPENSERV and create the file within the directory defined in the batch parameter.
Once the file is successfully created in the defined directory, the timestamp will be updated for the next extract.
Extract
A batch job will run daily after the Member Data Change file extract batch job to extract the changes to Address Details on the Interface to Core table.
When the batch job runs, if the Client Address is linked to a Membership or to a Natural Person that is linked to a Membership, the system will read the Notation records linked to the Membership. If a Notation record is found with a Type of OTHER MEMBSHIP and for which the Status is not COMPLETED then the address details will be extracted. The following details will be extracted:
- Scheme Code/Membership Reference Number (First Line Text of Note Detail of Notation record)
- Address Type
- Line 1
- Line 2
- Line 3
- Line 4
- Line 5
- Country
- Postal Code
- Telephone Country Code 1
- Telephone Area Code 1
- Telephone Number 1
- Effective Date
The Member Number of the linked membership will be contained in the first Line Text of the Note Detail linked to the Notation record with a Type of OTHER MEMBSHIP.
File
A CSV file with the name; AddressABSACCYYMMDD_Sq.csv prefixed with the value for the batch parameter MEMDATAPENSERV will be created, where:
- CCYYMMDD = The day of the month that the file is created
- Sq = The sequence number of the file.
Example: DTUIP59385_AddressABSA20100716_123.csv
The sequence number will be used to ensure that the files are received in the correct sequence and are only loaded once.
Each file must contain a header record (record type 1) and individual record details (record type 2).
No trailer record is required. A separate control file needs to be sent together with the file.
Header Record
The header record must be the first record in the file and in the format as per the table below.
|
Data Item |
Data Type |
Length |
Description |
Default Value |
Mandatory/Optional |
|
Record Identifier |
Integer |
2 |
|
01 |
M |
|
Importer Identifier |
String |
15 |
Used to indicate who has submitted the file |
ABSA |
M |
|
Sequence |
Numeric |
15 |
File sequence number |
|
M |
|
File Creation Date |
Date DDMMCCYY |
8 |
Date that the file was created |
|
M |
|
File Creation Time |
Time HHMMSS |
6 |
Time that the file was created |
|
M |
|
Resubmitted Indicator |
Logical |
1 |
Logical indicator that indicates if the file has been resubmitted |
N |
O |
Header Example: 01,ABSA,01,07062010,070059,N
Address Data Record
The Address Data records must be in the format as per the table below.
|
Data Item |
Data Type |
Length |
Vision / Default Value |
Mandatory/Optional |
|
Record Identifier |
Integer |
2 |
02 |
M |
|
Member Number |
Number |
22 |
Value in the first detail line of the notation record with the header of ‘OTHER MEMBSHIP’. Place the number into this field. If there is an error in the conversion from text to numeric, then write out an error to the error log and stop the process as there would be no other way to re-extract this data. |
M |
|
Name code |
Varchar2 |
2 |
MB |
M |
|
Type of Address |
Varchar2 |
2 |
Read the Translation Value with a Translation Purpose of INTERFACE1 and with a Source System ID and Source System Attribute of IN.PENSIONS and ADDRESS TYPE, and a Target System ID and Target System Attribute of PENSERVER and ADDRESS TYPE. Find the Target System value for the Source System Value equal to the value extracted for the combination of Type of Address and Status. See Note 1 below. |
M |
|
1st line of address |
Varchar2 |
34 |
Line 1 |
M |
|
2nd line of address |
Varchar2 |
34 |
Line 2 |
O |
|
3rd line of address |
Varchar2 |
34 |
Line 3 |
O |
|
4th line of address |
Varchar2 |
34 |
Line 4 |
O |
|
5th line of address |
Varchar2 |
34 |
Line 5 |
O |
|
Postcode |
Varchar2 |
10 |
Postcode |
M |
|
Country |
Varchar2 |
20 |
Read the Translation Value with a Translation Purpose of INTERFACE1 and with a Source System ID and Source System Attribute of IN.PENSIONS and ADDR COUNTRY, and a Target System ID and Target System Attribute of PENSERVER and ADDR COUNTRY. Find the Target System value for the Source System Value equal to the value extracted for Country. |
O |
|
Main telephone number |
Varchar2 |
16 |
Concatenation of Country Code 1 / Area Code 1 / Telephone Number 1 |
O |
|
Date of notification of change of address |
Date |
8 10 |
Effective Date (DD/MM/CCYY) |
M |
Note:
Where no entry is required in a particular field this must be populated with asterisks e.g. if no entry is required in the 5th line of address field it must be populated with 34 asterisks. If it is not filled with asterisks the original value will remain in Penserver.
The system will read the batch parameter ADDRESSPENSERV and create the file within the directory defined in the batch parameter.
Once the file is successfully created in the defined directory, the timestamp will be updated for the next extract.
After the Member Data Change File and the Address File batch jobs have completed, the number of Member data change records in the Member Data Change File and the number of address changes in the Address file will be counted and a CSV file will be created as per the following tables.
If there were no Member data changes or no address changes a value of zeroes will be included in the Control file.
When the file has been created the value on the Global Parameter with a Parameter Type of INTERFACES and a Parameter Sub-Type of PENSERVCONTROL will be updated.
The system will read the batch parameter PENSERVCONTROL and create the file within the directory defined in the batch parameter.
Header Record
The header record must be the first record in the file and in the format as per the table below.
|
Data Item |
Data Type |
Position |
Description |
Default Value |
|
Identification |
|
1 |
|
HEADER |
|
Provider Code |
|
2 |
Used to indicate who has submitted the file |
ABSA |
|
Effective Date |
Date DD/MM/CCYY |
3 |
Date that the file was extracted |
|
|
Previous Effective Date |
Date DD/MM/CCYY |
4 |
Date the last previous file was extracted |
Read the date of the Timestamp on the previous Global Parameter record with a Parameter Type of INTERFACES and a Parameter Sub-Type of PENSERVCONTROL. |
|
Date Generated |
Date DD/MM/CCYY |
5 |
Date file created |
|
|
Time Generated |
Time HHMMSS |
6 |
Time that the file was created |
|
Header Example: HEADER,ABSA,07/06/2010,06/06/2010/07/06/2010,07:00:59
Data Record
The data records in the must be in the format as per the table below.
|
Data Item |
Data Type |
Position |
Description |
Default Value |
|
Identification |
|
1 |
|
BASIC for the Member Data Changes file ADDRESS for the Address file. |
|
Record Count |
8 characters filled with leading zeroes. |
2 |
Number of member data records contained in the Member Data Changes file and number of address records in the Address file. |
Number of Member data change records in the Member Data Change file or number of address records in the Address file. Zero filled if there were no changes i.e. no file was created. |
Example: BASIC,00000020
ADDRESS,00000000
When a Notes file is uploaded and a record is found for a Membership for which the Note Header is OTHER MEMBSHIP and the value in the first line of the Note Text (Member Number) is equal to the value for Note Text in the file and there is a value of COMPLETED for Status in the file, the Status on the Notation record will be updated to COMPLETED.