ImportNAPOLFile
Use this form set level rule to import a single transaction, stored in a WIP/NA/POL export file, from Documaker Desktop into the GenData program.
Note | If you use the SCH option, you can import multiple Documaker Desktop WIP/NA/POL export files. |
Syntax
There are several ways to specify the import file in the option parameter:
Option |
Description |
FILE = file name |
Enter the name and path of the import file. |
INI = INI control group, option |
Enter the INI control group and option in which the import file is defined. |
SCH = offsetofmask, <searchmask> offsetofdata, lengthofdata |
This indicates the file name is contained in a record of the extract file. The offsetofmask is the offset of the search mask, offsetofdata is the offset where the file name starts, and lengthofdata is the length of the file name. |
GVM = GlobalVariableName |
GlobalVariableName defines the GVM that contains the file name and path information. |
The INI and FILE options normally import the same file for each transaction. The SCH and GVM options let you import a different file for each transaction.
Keep in mind:
- For each field that comprises a section (whose data comes from the combined WIP/NA/POL export data), you must create or have a DDT record with the field rule set to one of these field rules:
- If you use the NoOpFunc rule for any field rule associated with the combined WIP/NA/POL export data, you must insert the ReplaceNoOpFunc rule in the <Base Rules> section of the AFGJOB.JDT file.
- Place the ImportNAPOLFile rule in the <Base Form Set Rules> section of the AFGJOB.JDT after the BuildFormList rule or any custom rule that creates a form set.
- The LoadRcpTbl and RunSetRcpTbl or GetCo and GetLOB rules are not required unless you use the SCH option.
Assume you have the following items defined in your master resource library. Keep in mind:
- The ReplaceNoOpFunc rule is required in the AFGJOB.JDT file because one of the fields in the sample DDT uses the NoOpFunc rule.
- Trn_Fields control group options are based on items in the first record of the combined WIP/NA/POL Export data file.
Here is a sample combined WIP/NA/POL import file named IMPORT.DAT:
WIP="SAMPCO ""LB1 ""NAPOL FILE # 1 ""NB ""P"
;SAMPCO;LB1;LETTER2;Second Letter;RD;;q1snam|D3<Insured>/q1fl2a|D3S<Insured>/q1b302|D3S<Insured>/q1ba36…;
\ENDDOCSET\
\NA=q1snam,LN=1,DUP=OFF,SIZE=C,TRAY=U,X=0,Y=0,PA=1,OPT=D3\
\ENDIMAGE\
\NA=q1fl2a,LN=1,DUP=OFF,SIZE=C,TRAY=U,X=0,Y=3360,PA=1,OPT=D3S\
FDate;235;3913;12012;;;\January 1, 2000
FLessee_NAME;235;4806;12012;G;;\Morris Sander
FLessee_addr;235;5212;12012;G;;\3200 Windy Hill Road
FLessee_city;235;5636;12012;G;;\Atlanta, GA 30339
\ENDIMAGE\
…
\ENDFORM\
\ENDDOCSET\
Here is a sample DDT file:
<Image Field Rules Override>
;0;0;Date;0;0;Date;0;25;; NoOpFunc;;N;N;N;…
;0;0;Lessee_Name;0;9;Lessee_Name;0;25;; MapFromImportData;;N;N;N;…
;0;0;Lessee_addr;0;25;Lessee_addr;0;25;; MapFromImportData;;N;N;N;…
;0;0;Lessee_city;0;25;Lessee_city;0;25;; MapFromImportData;;N;N;N;…
Here are sample INI settings:
< TRN_Fields >
Key1 = 1,3,N
Key2 = 6,6,N
KeyID = 26,20,N
< TRN_File >
BinaryExt = N
<ExtractKeyField>
< Data >
Example
The following examples illustrate the different ways you can define the import file when you use this rule.
Using the File option
This example imports information from the IMPORT1.DAT file in the \import directory and uses that information to create the GenData files which the GenPrint program uses to create the print output files.
Here is an excerpt from a sample AFGJOB.JDT file:
<Base Rules>
…
;ReplaceNoOpFunc;;;
/* Every form set in this base uses these rules. */
<Base Form Set Rules>
;NoGenTrnTransactionProc;;;
;ResetOvFlw;;;
;BuildFormList;;;
;ImportNAPOLFile;;File=.\Import\Import1.dat;
…
Using the INI option
This example imports information based on the Import_File option in the Import_Data control group. Using this information, the GenData program creates the files the GenPrint program uses to create the print output files.
Here are the sample INI settings:
< Import_Data >
Import_File = .\Import\Import1.dat\
Here is an excerpt from a sample AFGJOB.JDT file:
<Base Rules>
…
;ReplaceNoOpFunc;;;
/* Every form set in this base uses these rules. */
<Base Form Set Rules>
;NoGenTrnTransactionProc;;;
;ResetOvFlw;;;
;BuildFormList;;;
;ImportNAPOLFile;;INI=Import_Data,Import_File;
…
Using the SCH option
This example imports multiple WIP/NA/POL export files based on the content of a line in the extract file. Using this information, the GenData program creates the files the GenPrint program uses to create the print output files.
Here is an excerpt from a sample extract file named EXTRFILE.DAT:
;CWNG;CIS;1;NB;W ;; TXT .\Import\impt1file.dat
;CWNG;CIS;1;NB;W ;; TXT .\Import\impt2file.dat
…
For this example, use these INI options:
< Data >
< TRN_Fields >
Key1 = 2,4,N
Key2 = 7,3,N
KeyID = 35,22,N
< ExtractKeyField >
Here is an excerpt from a sample AFGJOB.JDT file:
<Base Rules>
…
;ReplaceNoOpFunc;;;
/* Every form set in this base uses these rules. */
<Base Form Set Rules>
;NoGenTrnTransactionProc;;;
;ResetOvFlw;;;
;BuildFormList;;;
;ImportNAPOLFile;2;SCH=30,TXT 35,22;
Using the GVM option
This example imports data from an import file based on a GVM variable called Import_File. Using this information, the GenData program creates the files the GenPrint program uses to create the print output files. Any valid GVM variable can be used no matter how it is created or assigned. Here is an excerpt from a sample AFGJOB.JDT file:
<Base Rules>
…
;ReplaceNoOpFunc;;;
/* Every form set in this base uses these rules. */
<Base Form Set Rules>
;NoGenTrnTransactionProc;;;
;ResetOvFlw;;;
;BuildFormList;;;
;ImportNAPOLFile;;GVM=Import_File;
See also
© Copyright 2020, Oracle and/or its affiliates. All rights reserved. Legal notices.