Mapping input columns to request templates

Column names are defined in the CDMETADATAINFOTP code table:

The metadata information type codes (METADATA_INFO_TP_CD) are associated to the task definitions. Task definitions define the request templates.

For example, two columns named ENTITY_ID,ENTITY_TYPE are defined in the metadata key (METADATA_KEY) of the CDMETADATAINFOTP code table. The METADATA_INFO_TP_CD is 7, which is used for the Persist Entities task, and the task definition ID is 80.

The predefined XML request template for task definition ID 80 in the TASKDEFINITION table is as follows:

<?xml version="1.0" encoding="UTF-8"?>
<TCRMService xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="myTCRM.xsd">
  <RequestControl>
    <requestID>100012</requestID>
    <DWLControl>
      <requesterName>cusadmin</requesterName>
      <requesterLanguage>100</requesterLanguage>
    </DWLControl>
  </RequestControl>
  <TCRMTx>
    <TCRMTxType>persistEntity</TCRMTxType>
    <TCRMTxObject>PersistEntityRequestBObj</TCRMTxObject>
    <TCRMObject>
      <PersistEntityRequestBObj>
        <EntityId><<ENTITY_ID>></EntityId>
        <EntityType><<ENTITY_TYPE>></EntityType>
        <PersistenceMode><<PersistenceMode>></PersistenceMode>
      <PersistEntityRequestBObj>
    </TCRMObject>
  </TCRMTx>
</TCRMService>

• Query inputs must provide ENTITY_ID and ENTITY_TYPE as input to match the defined column names:

  <SQLOverride>
  SELECT DISTINCT CURENTRECNO AS ENTITY_ID, ‘mdmorg’ AS ENTITY_TYPE FROM MPI_ENTLINK_MDMORG WHERE CURENTRECNO NOT IN (SELECT ENTITY_ID FROM CONTACT WHERE PERSON_ORG_CODE = 'O' AND ENTITYLINK_ST_TP_CD = 2)
  </SQLOverride>

• Titled CSV file inputs must provide two columns named ENTITY_ID and ENTITY_TYPE as input. The file defines the column names on the first line:

  ENTITY_ID,ENTITY_TYPE
  100000000,mdmper
  100000001,mdmper
  100000002,mdmorg

The batch processor replaces the appropriate placeholders in the template with values from the two input columns.