Acord Format

[Anerol]

Morning,

I am searching for information about the Acord format. When searching on the net I get the official Acord website, but I am mostly wanting a forum where folks discuss details.

I'm starting to think that it simply doesnt exist but in the small chance that it does, any direction would be good.

My job is requiring me to create an Acord format xml using an xsl with our current xml. Though I understand the basic idea of Acord and I use a tool to help with the structure, it's the more detailed things within the framework that I find myself with many questions and no source for answers.

If nothing comes up here I will most likely go ask to take some training courses somewhere, I'm sure they exist.

Thanks for your time.

~Lorena

 

[k5tm]

Lorena,

First of all, Welcome to Tek-Tips!

Since Acord is a combination of specifications (from my brief visit there) you can probably get most answers here, and some in the SOAP forum: forum781. In some ways these are overlapping forums.

So, you have XML documents, and XSL can be used to transform them to the XML documents specified by Acord.

Start asking...

Tom Morrison

http://www.liant.com

 

[Anerol]

Not sure if you have the answer to this one but here is my current problem, and thanks for the welcome btw!

The tool that I use displays the Acord format in a hierarchy. Within the tool while selecting certain elements so to speak, I get additional information of what codes, if applicable should be used there along with a brief description of it's purpose.

Now for the issue. This is Homeowners Insurance, while looping through the coverages that the insured has chosen, these must be mapped to the Acord.

Before XML

cov#1
{
code="PP"
limit="20000"
prem="299"
}

cov#2
{
code="POLDED"
limit="250"
prem="0"
}

cov#3
{
code="MOLD"
limit="20"
prem="8"
}

After running it through my xsl I get:

<Coverage number="1">
<CoverageCd>PP</CoverageCd>
<Limit>20000</Limit>
<Premium>299</Premium>
</Coverage>
<Coverage number="2">
<CoverageCd>POLDED</CoverageCd>
<Deductible>250</Deductible>
<Premium>0</Premium>
</Coverage>
<Coverage number="3">
<CoverageCd>MOLD</CoverageCd>
<Limit>20</Limit>
<Premium>8</Premium>
</Coverage>
------------------------------------------------

That part is pretty much cut and dry. My issue is with the MOLD coverage #3. The "limit" is coming across as 20, because this amount is actually a precentage it is not bridging correctly in the AS400 system.

Searching in the Acord I cannot figure out how I should be sending it. Here is some of the Hierarchy, I broke out Option because I think it might go there:

Coverage
- CoverageCd
- Limit
- Deductible
- Option
- OptionTypeCd
- A code identifying the Type of Option being
applied. This element uses the <codelist
ref="OptionBenefit">OptionBenefit</codelist> code
list. Please refer to the Code List Guide.
Example Codes: Bene1 - Benefit 1
Bene2 - Benefit 2
Misc1 - Miscellaneous
- OptionCd
- A code whose usage is based upon the coverage code,
coverage subcode, or subject options title code.
This element uses the <codelist
ref="CoverageOption">CoverageOption</codelist> code
list. Please refer to the Code List Guide.
Example Codes: AF - Additional Farm
AP - All Physical Damage
- OptionValue
- A value to be used for <el
ref="NumberOf">NumberOf</el> or <el
ref="YNIndicator">YNIndicator</el>. When the <el
ref="OptionCd">OptionCd</el> value is APIP, this
element contains the APIP option number.
- CurrentTermAmt
- NetChangeAmt

------------------------------------------------------

This may look like a complete mess, i tried to give as much info as possible but since it deals directly with the Acord layout i might have troubles finding an answer from someone who isnt familar. I'm going to keep searching around and ask a few heads around the department even though I'm pretty sure I'm the most experienced.. sad times for sure.

Thanks and Be Back Laters.

 

[k5tm]

Lorena,

So, are you saying that the XSL needs to compute a <limit> value for MOLD as a percentage of another <limit> value? If so, please show the input document (before it is run through the XSL process) as well as the XSL document itself.

(Hint: click on the Process TGML link to show how you can place these documents' contents nicely inside [ignore]

...

[/ignore] tags so that they will be displayed a bit more neatly.)

Tom Morrison

http://www.liant.com