Understanding data preparation job sequencers

As mentioned previously, in BIL, there is a way to turn off validation altogether.

When validation is turned off (when no validation logic is to be executed for any RT/ST), all the data preparation jobs need to be run together in order to prepare datasets pertaining to all the Record-type/Sub-types in order to prepare the datasets for Key Assignment and Load.

This task is orchestrated by two job sequences:

  • BL_020__PREP_PARTY_DS - Runs the Party preparation jobs
  • BL_021__PREP_CONTRACT_DS - Runs the Contract preparation jobs

Both job sequences are invoked from the master sequence BL_000_BASIC_LOAD.

An image of a portion of the BL_000_BASIC_LOAD master sequence. The squares highlight the Party and Contract PREP job sequences.

The BL_020__PREP_PARTY_DS job sequence is responsible for performing the data preparation logic for the Party stream. The job sequence is comprised of the 6 Party specific preparation jobs and 5 Routine Activity stages.

An image of the BL_020_PREP_PARTY_DS job sequence

For some Party sub-types (namely Alert, LobRel, MiscValue, OrgName, PersonName and PrivPref), the output dataset is produced by simply renaming the input dataset with appropriate prefix (from Parse_* to ErrCon_* as expected by the Key Assignment and Load jobs). This task is performed by a routine called ECRenameFile which is invoked by the corresponding Routine Activities (see the preceding figure).

For the rest of the Party sub-types (namely Address, ContactMethod, Contact, ContactRel and Identifier), more work is required to ensure that specific interrelated metadata is properly provided to assist the Key Assignment and Load phase. These tasks are handled by the corresponding Party Preparation jobs.

The BL_021__PREP_CONTRACT_DS job sequence is responsible for performing the data preparation logic for the Contract. The job sequence is comprised of the 7 Contract specific preparation jobs

An image of the BL_021__PREP_CONTRACT_DS job sequence