Parties
Party represents any user that has business context within any system that makes use of the Inventory in the enterprise.
It includes both OSS and BSS layers, as well as systems outside the domains. A party is identified with a unique identifier called a partyId. This identifier must be globally unique within the party domain and can be specified externally or generated by the Inventory as required. Typically a party will be used to represent any one of the following types of entities:
Parties often exist in hierarchies, so the Fulfillment Subscriber Inventory system provides the capability of linking parties using parent child relationships. These relationships do not enforce referential integrity and are linked solely on the primary key of each party entity, specifically the partyId.
Fulfillment Subscriber Inventory also provides the ability to manage a limited set of information that describes a party in the form of characteristics. These characteristics are name-value pairs which describe attributes of the party. Each characteristic is identified with a unique identifier called a characteristicId. This identifier must be unique within the scope of any given party instance and can be specified externally or generated by the Inventory as required.
There is also the capability of locking party objects within the Inventory. Each lock is identified with a unique identifier called a key. This identifier must be unique within the scope of any given party instance and must always be specified externally.