Question from one of our committee organizations:
We've got a client that has many locations, each with its own name and UID (or code). We want to utilize this tag in a way that accommodates both a name and code for each type of "cost center" - even if there's more than one (e.g. locations, departments, divisions, etc).
We're between two different methods. The first is where we use the type code to create an association between two categories, and the second is where we'd use the name to create that association. Mind telling us which is better?
- <EmploymentInformationUserDefinedCategory>
<CategoryName>Location Name</CategoryName>
<CategoryValueString>Philadelphia, PA</CategoryValueString>
<CategoryTypeCode>Location</CategoryValueString>
</EmploymentInformationUserDefinedCategory>
<EmploymentInformationUserDefinedCategory>
<CategoryName>Location Code</CategoryName>
<CategoryValueString>PHLPA001</CategoryValueString>
<CategoryTypeCode>Location</CategoryValueString>
</EmploymentInformationUserDefinedCategory>
- <EmploymentInformationUserDefinedCategory>
<CategoryName>Location</CategoryName>
<CategoryValueString>Philadelphia, PA</CategoryValueString>
<CategoryTypeCode>Name</CategoryValueString>
</EmploymentInformationUserDefinedCategory>
<EmploymentInformationUserDefinedCategory>
<CategoryName>Location</CategoryName>
<CategoryValueString>PHLPA001</CategoryValueString>
<CategoryTypeCode>Code</CategoryValueString>
</EmploymentInformationUserDefinedCategory>
Are there any existing integrations organizations have developed that have come up with a way to tackle appending a physical location and a code to the same entity?
@Lynda Whitmore @Lyle Griffin @Kailey Rae
#LDEx-General#LDEx-BEM#LDEx-Implementation#LDEx-JSON#LDEx-XML------------------------------
Michael J Grudgings
Business Architect, Data Standards | LL Global, Inc.
300 Day Hill Road, Windsor, CT, 06095
t: (860) 298-3850 |
mgrudgings@limra.com------------------------------