Use this form set rule to import a file which consists of one or more XML transactions into the GenData program for processing. Using this file, the GenData program creates the recipient batch, NAFile, POLFile, and NewTrn files that you can print, archive, or both using the GenPrint and GenArc programs.
Note | If you are running Documaker from IDS, use the ImportXMLExtract rule to bring in XML in standard Documaker XML format, such as from Documaker Desktop or iDocumaker. Use the UseXMLExtract rule to convert a loaded extract file into an XML tree, which you can then use to query data. |
You append multiple export files to create the import XML file. The export files are created using the Documaker Desktop XML Export option. This illustration shows an example file comprised of export files appended to one another:
Transaction 1
<?xml version="1.0"?>
<Document Type="Oracle Universal" Version="5.0">
<DocSet>
<ArcEffectiveDate></ArcEffectiveDate>
<Library Name="Oracle Insurance"></Library>
<Key1 Name=”Company”>SkyInsur</Key1>
<KeyY2 Name=”Lob”>Package Policy</Key2>
<TransactionID Name="PolicyNum">1010j</TransactionID>
…
…
Transaction 2
<?xml version="1.0"?>
<Document Type="Oracle Universal" Version="5.0">
<DocSet>
<ArcEffectiveDate></ArcEffectiveDate>
<Library Name="Oracle Insurance"></Library>
<Key1 Name=”Company”>SkyInsur</Key1>
<KeyY2 Name=”Lob”>Package Policy</Key2>
<TransactionID Name="PolicyNum">1110j</TransactionID>
…
…
Transaction 3
<?xml version="1.0"?>
<Document Type="Oracle Universal" Version="5.0">
<DocSet>
<ArcEffectiveDate></ArcEffectiveDate>
<Library Name="Oracle Insurance"></Library>
<Key1 Name=”Company”>SkyInsur</Key1>
<KeyY2 Name=”Lob”>Package Policy</Key2>
<TransactionID Name="PolicyNum">1210j</TransactionID>
…
…
Option |
Description |
SP |
Include the SP option to suppress the pagination portion of the import. This lets you run rules and other form set manipulations before calling a rule to paginate the form set, such as the PaginateAndPropogate rule. |
Note | You can only use this rule for single-step processing. |
Keep in mind...
< XMLTags2GVM >
GVM = XMLTag, (Req/Opt)
where GVM is the name of the GVM variable and XMLTag is the tag name in the XML file. Include Req or Opt to specify whether it is required or optional. If it is required and is omitted from the XML file, processing stops. Here is an example:
< XMLTags2GVM >
Key1 = Key1, Req
Key2 = Key2, Req
KeyID = TransactionID, Opt
Assume you have the following items defined in your master resource library. See XML File Format for an example of an import file in the standard XML file format.
Here is an example of the INI options you need in your FSISYS.INI file:
< Data >
AFGJOBFile = .\deflib\afgjob.jdt
ExtrFile = .\extract\extrfile.xml
< ExtractKeyField >
SearchMask = 1,<?xml
< Key1Table >
XML = XML
< Key2Table >
XML = XML
< KeyIDTable >
XML = XML
< Trigger2Archive >
Key1 = Key1
Key2 = Key2
KeyID = KeyID
RunDate = RunDate
< TRN_Fields >
Key1 = 3,3,N
Key2 = 3,3,N
KeyID = 3,3,N
< TRN_File >
BinaryExt = N
MaxExtRecLen = 175
< XMLTags2GVM >
Key1 = Key1,Req
Key2 = Key2,Req
KeyID = TransactionID,Opt
Here is an excerpt from a sample AFGJOB.JDT file:
< Base Rules >
;RULStandardJobProc;;;
…
< Base Form Set Rules >
;NoGenTrnTransactionProc;;;
;BuildFormList;;;
;ImportXMLExtract;;;
…
…
© Copyright 2014, Oracle and/or its affiliates. All rights reserved. Legal notices.