Invoice Load Control Interface Table

This extract file interface is used to control various elements of the invoice loading process. There is only a single record in this file per extract. The record format includes an indication of how many invoice extract file sets make up an extract, an optional dependent hierarchy extract ID and a series of extract file record counts for validation purposes. Data loaded via this interface is primarily bound for the LOAD_CONTROL and DATA_LOAD CXP Customer Experience Platform, or CXP, is MDS Global's self-service app that allows business customers to manage their own accounts and subscriptions. Admin schema tables.

External table name	Schema	Mapped file
invoice_load_control_Interface	Staging	invoice_load_control.dat

 

Invoice load control interface table fields

Column Heading	Type	Length	Description
EXTERNAL_DATA_SOURCE_ID	VarChar2	40	An identifier for the instance of the CRM database from which the hierarchy data has been extracted.
EXTRACT_ID	VarChar2	40	A unique identifier for the current extract. This value will usually be derived by the CRM from a sequence that it controls and tracks.
SET NUMBER	Integer		Identifies data as belonging to a given source database extract set (a sub division within an extract operation allowing multi-threading of the extract job, but not the load job).
NUMBER_OF_ SETS_IN_EXTR ACT	Integer		The total number of extract sets that the extract has been divided into for extraction convenience. This value allows the data loader to recognise when all of the extract sets have been loaded in for an extract so that reconciliation operations can be carried out.
INVOICE_LOAD _CONTROL_CO UNT	Integer		Number of records in the invoice_load_control.dat extract file. Used to confirm that the contents of that extract file have been successfully delivered without truncation.
INVOICE_COU NT	Integer		Number of records in the invoice.dat extract file. Used to confirm that the contents of that extract file have been successfully delivered without truncation.
INVOICE_LINE_ COUNT	Integer		Number of records in the invoice_line.dat extract file. Used to confirm that the contents of that extract file have been successfully delivered without truncation.
USAGE_ITEM_ COUNT	Integer		Number of records in the usage_item.dat extract file. Used to confirm that the contents of that extract file have been successfully delivered without truncation.
DELIVERY_ADD RESS_COUNT	Integer		Number of records in the delivery_address.dat extract file. Used to confirm that the contents of that extract file have been successfully delivered without truncation.
INC_USAGE_A LLOC_COUNT	Integer		Number of records in the inc_usage_alloc.dat extract file. Used to confirm that the contents of that extract file have been successfully delivered without truncation.
INC_USAGE_U NITS_COUNT	Integer		Number of records in the inc_usage_units.dat extract file. Used to confirm that the contents of that extract file have been successfully delivered without truncation.
STATEMENT_COUNT	Integer		Number of records in the statement.dat extract file. Used to confirm that the contents of that extract file have been successfully delivered without truncation.
STATEMENT_T RANS_COUNT	Integer		Number of records in the statement_trans.dat extract file. Used to confirm that the contents of that extract file have been successfully delivered without truncation.
HIERARCHY_N ODE_CHECK _COUNT	Integer		Number of records in the Hierarchy_Node_Check.dat extract file. Used to confirm that the contents of that extract file have been successfully delivered without truncation.
INVOICE_DATE	Date		The financial date associated with each and every invoice in the current extract. This is the date printed on the invoice, the date used to apply tax and is generally the date from which the invoice due date is calculated. Note that every invoice in the extract will have the same invoice date/time. Invoices from different dates/times should be separated out into different sets or extracts. DATE_FORMAT DATE MASK "yyyymmddhh24miss".
INVOICE_PRO DUCTION_ID	VarChar2	40	The identifier used by the CRM for the invoice production run used to create the invoices in the current extract. This value is used to aid data load reconciliation operations.
HIERARCHY_EF FECTIVE_DATE	Date		This date/time is used to synchronise the invoice extract with the effective set of organisation unit hierarchies with which it is associated. That is to say that the date/time here represents a point in time at which the hierarchy structures presented in the invoice extract's 'hierarchy_node_check.dat' extract file can be found in the database in their entirety (all parent/child relationships match) and are effective on this date/time. Notice that each extract set supports only a single hierarchy effective date. Invoices associated with different hierarchy dates should be separated out into different sets or extracts. If an invoice data load is dependent on a customer hierarchy extract data load, then the date/time here would match the hierarchy effective date of the corresponding hierarchy extract (or at least represent a date/time somewhere between the date/time of the desired extract and that of a hierarchy extract that supersedes it). DATE_FORMAT DATE MASK "yyyymmddhh24miss"
EXTRACTION_T IMESTAMP	Date		Date and time that the extract file set was generated. DATE_FORMAT DATE MASK "yyyymmddhh24miss"
DEPENDENT_O N_HIERARCHY _EXTRACT	VarChar2	40	When invoices are loaded, the various elements of the invoice (header, lines, usage, etc) are attached to the organisation units that own them in the organisation unit hierarchy. Customer hierarchy building operations are carried out by a spate data loader (customer hierarchy data loader). If an attempt is made to load invoices for which all owning hierarchy elements have not been previously loaded, then the data load will fail (the invoice extract data will be rejected). The DEPENDENT_ON_HIERARCHY_EXTRACT field allows the invoice data loader to be told that it must check that a particular customer hierarchy extract has been loaded first, before attempting to load the invoices for in this invoice extract. In this way the loading of customer hierarchy data and invoice data can be coordinated to prevent invoice extract rejection. If the invoice loader sees that a prerequisite of loading an invoice extract set is to first load a given customer hierarchy extract, then it will delay loading the invoice set until that has been done.