| ShortName |
Name |
Type |
Description |
Required? |
Read only? |
Cardinality |
XML Attribute? |
Implementation Notes |
| name |
Name |
String |
Short name of the LO to LO relationship type. This is primarily to be used by developers and may end up translated in the end system. |
|
|
One |
No |
| desc |
Desc |
String |
Narrative description of the LO to LO relationship type. |
|
|
One |
No |
| revName |
Rev Name |
String |
Name for the reverse LO to LO relationship type. This is primarily to be used by developers and may end up translated in the end system. |
|
|
One |
No |
| revDesc |
Rev Desc |
String |
Description of the reverse of the LO to LO relationship type |
|
|
One |
No |
| effectiveDate |
Effective Date |
Date |
Date and time that this LO to LO relationship type became effective. This is a similar concept to the effective date on enumerated values. When an expiration date has been specified, this field must be less than or equal to the expiration date. |
|
|
One |
No |
| expirationDate |
Expiration Date |
Date |
Date and time that this LO to LO relationship type expires. This is a similar concept to the expiration date on enumerated values. If specified, this should be greater than or equal to the effective date. If this field is not specified, then no expiration date has been currently defined and should automatically be considered greater than the effective date. |
|
|
One |
No |
| attributes |
Attributes |
Map |
List of key/value pairs, typically used for dynamic attributes. |
|
|
One |
No |
| key |
Key |
String |
Unique identifier for the LO to LO relation type. |
|
|
One |
Yes |