New inquiry levels

You can add or update an inquiry level configuration using Administration services (transactions).

About this task

To configure a new inquiry level:

Procedure

Use the Administration Services to add or update an inquiry level configuration. Be aware of the following points when configuring new inquiry levels:

Allowed and Reserved Ranges: The permitted numeric range of integers for new inquiry levels is from 100 and up. Levels 99 and under are reserved for internal use by the IBM® InfoSphere® Master Data Management product.
Note: Do not use or change the existing configurations of any of the reserved ranges.
- Expiring Inquiry Level and Child Groups: The inquiry level for an object and the child objects they retrieve for an object may be expired using the expiry_dt field. If an Inquiry Level is expired, that record is not made available to the system for further processing. Only active Inquiry Levels are retrieved by the system for use.
- Cumulative Inquiry Levels: Inquiry levels may be cumulative. This means that particular level includes ALL objects configured for every inquiry level below it, regardless of whether or not any of the lower levels are cumulative . For example, if level 120 has cumulative_ind = Y or is cumulative, all groups configured for level 120 down to level 100 are returned as the set of child objects to return for that particular object. In sum, levels are not skipped when one is defined as cumulative.
Note: Client-defined inquiry levels (level 100 and above) are not cumulative to include product-defined inquiry levels (0-99).
- Configure only the child Groups to be returned for the parent Group: There is no need to configure the Group for the Person, Organization or Contract object as a child of the inquiry level for itself. By definition, inquiry level objects are child objects so, at a minimum, the parent object itself is always be returned. For example, there is no need to configure Contract level 1 to contain child Contract, to ensure its return.
- Configuration Warning Messages: It is possible to configure an inquiry level incorrectly. When this happens, Status 5 warning messages indicate which objects for the inquiry level are in error. For example, if an inquiry level is defined for Person, say 101, that returns child objects PersonName, PartyIdentification, and IncomeSource, when running a getParty() transaction (level 101), a configuration warning is returned, stating that the parent of the IncomeSource object is configured incorrectly. IncomeSource requires the FinancialProfile to be configured for Party as well, because IncomeSource, PartyChargeCard, PartyBankAccount, and TCRMPartyPayrollDeductionBObj are within the processing of FinancialProfile. These dependencies are noted in the charts supplied detailing the current configuration of the IBM InfoSphere Master Data Management objects (Contract, Organization, Person) and their inquiry levels. The following is an example of the warning message:
```
<DWLStatus>
  <Status>5</Status>
  <DWLError>
    <ComponentType>10</ComponentType>
    <ComponentTypeValue>DWLErrorMessageComponent</ComponentTypeValue>
    <Detail>Parent object of ContractPartyRoleIdentifier was not configured 
      properly for inquiry level. Add record for parent object of 
      ContractPartyRoleIdentifier in table INQLVLGRP.</Detail>
    <ErrorMessage>Some objects may not be returned due to inquiry level 
      configuration errors in table INQLVLGRP</ErrorMessage>
    <LanguageCode>0</LanguageCode>
    <ReasonCode>15204</ReasonCode>
    <Severity>5</Severity>
  </DWLError>
</DWLStatus>
```
- Use the transaction documentation: Consult the transaction reference documentation for out-of-the-box details on the objects returned for inquiry levels for getParty (getPerson (Person object), getOrganization (Organization object), and getContract (Contract object).