This document covers the bulk document upload process to upload bulk data into the document management table.
An entry on JWA37 will have the path to the bulk upload file. The JWA37 Control Id is BULKUPLOAD, currently pointing to c:\inpensions\bulk on the Application Server.
The following is the file layout of the bulk file:
|
|
Field Name |
Field Size |
DEC |
ATTR |
O/M |
Start |
End |
Description / Value |
|
1 |
File indicator |
4 |
|
Char |
M |
1 |
4 |
DOCU |
|
2 |
FundNumber |
7 |
|
Char |
M |
5 |
11 |
Scheme code |
|
3 |
MemberNumber |
20 |
|
Char |
M |
12 |
31 |
Principal member reference number |
|
4 |
Document type |
15 |
|
Char |
M |
32 |
46 |
AUGMENTATION BENEFIT LETTER BENEFITSTATEMNT BENFCRY ID DOCS CLAIM FORM DEATH CERT DISABILITY ASS ELIGIBILITY FIN STATEMENTS FLEXIBLE LETTER FUND MEMBER GEN CORRSPNDNCE LABLTY SETTLMNT MI PRIORITY E MI PRIORITY H MI PRIORITY N NOTATION OTHER MEMBSHIP PRF OF BNK DTLS PUBLICATIONS RECONTN OF TRF REIN BEN CLM FM RESERVE BANK SMS STATUS DATE TAX DIR APPLCTN TAX DIRECTIVE TERMINATING TRUST PAYMENT TRUSTEEDECISION VALUATION |
|
5 |
FileName |
100 |
|
Char |
M |
47 |
146 |
Location of file to be uploaded. This will be the directory on the CD. The file could be on either the server or network share. |
|
6 |
Description/GUID |
100 |
|
Char |
O |
147 |
246 |
Unique ID on source system |
|
7 |
Source |
15 |
|
Char |
O |
247 |
261 |
If the instruction is REF or TARGET, then this value points to the system were the file is saved and fetched, using the GUID as file id. This functionality is not usable as no source system exists yet. Users to leave blank as it is ignored.
Where to find the file if the GUID is provided – like Sybrin or Content Manager – UDPV.
Note: For more information, refer to Field Descriptions table below. |
|
8 |
Instruction |
6 |
|
Char |
O |
262 |
267 |
Load only the reference to the member record – REF Load the reference and document to – REFDOC Load the reference and document to the source system – TARGET
Note: For more information, refer to Field Descriptions table below. |
|
9 |
Purpose |
15 |
|
Char |
O |
268 |
282 |
INTERNAL/EXTERNAL UDPV.
Note: Currently, everything is treated as INTERNAL. Note: For more information, refer to Field Descriptions table below. |
|
10 |
File Company |
15 |
|
Char |
O |
283 |
297 |
File Company Code on Infrastructure |
|
11 |
Region |
15 |
|
Char |
O |
298 |
312 |
Region Code on Infrastructure |
|
12 |
Box Number |
30 |
|
Char |
O |
313 |
342 |
Box Number where the document is stored. |
O = Optional field
M = Mandatory
The files will be placed in a directory on the server. This directory is a setting on the global settings.
The file will be uploaded and once the file is read by the program, the Instruction field (see below), will advise the program what must be done:
Field Descriptions
|
Field |
Value |
Description |
|
Source |
|
The system that the document will be stored in when it is not stored in the Document Manager.
This field may be blank. This field is only required when the Instruction field = “TARGET”, i.e. the file is to be sent to another system. |
|
Instruction |
REF |
The document has been uploaded to an external system and the file is loading the reference to the document and source on the member’s record so that the member can see this document from the member web site or the Administrator can view the document.
Note: This functionality is not usable as no source system exists yet. |
|
REFDOC |
The document is being loaded to the Document Manager and hence the directory on the global settings will be used to find the file using the filename. |
|
|
TARGET |
The document must be uploaded to an external system as defined by the field in source and the reference to the document and source must be stored on the member’s record. The source field must be used to establish which interface to call to upload the physical document from the directory using the Filename.
Note: This functionality is not usable as no source system exists yet. |
|
|
Purpose |
|
Advises whether the member can see this document from the member web site or the Administrator can view the document. The Administrator will be able to see all external and internal documents.
Note: Currently, everything is treated as INTERNAL. |
The bulk Document Uploader will read the bulk file and for the scheme code member ref combination, upload a file from path file name into the document table. Once the file is uploaded, program SJU7AK will be called to link the document id to the member.
The actual upload page is located under Processes>File Transfer>Bulk Document Upload.
Once the file is uploaded, the batch process is submitted to upload each file name in the document to the relevant member.
Any errors will be reported in the Technical log.