You can define custom attributes for the entities used in DQM: Party, Address, Contact, and Contact Point. Up to 30 custom attributes are available in each entity.

Procedure

1. Write a custom procedure that obtains the custom attribute.

   When a CUSTOM_ATTRIBUTE column needs information about a party, address, contact, or contact point, DQM calls a procedure with this signature:

   FUNCTION <custom_attribute_proc>
        p_record_id     IN     NUMBER,
        p_entity_name   IN     VARCHAR2,
        p_attrib_name   IN     VARCHAR2,
        p_context       IN     VARCHAR2)
   RETURN VARCHAR2; 

   • p_record_id: The p_record_id value in the signature is the primary key of the table where the CUSTOM_ATTRIBUTE_PROCEDURE is defined.

     This table displays the appropriate p_record_id value for each entity attribute.

     Entity Attribute	p_record_id
     Party	PARTY_ID
     Address	PARTY_SITE_ID
     Contact	ORG_CONTACT_ID
     Contact Point	ORG_CONTACT_POINT_ID

   • p_context: The p_context value, STAGE or SEARCH, indicates whether the attribute is to be used in the context of staging or searches.

2. Define the custom attribute using one of the available CUSTOM ATTRIBUTE values. Enter your custom PL/SQL procedure and define transformations for the attribute. See: Defining Attributes and Transformations.

   Note: If you do not plan to transform the party information for a custom attribute, then use an Exact transformation.