Importing data change requests

In order to effectively and more seamlessly work with third party data, you can import data change requests for third party master systemsData that a customer purchases from an independent data provider that can be used as the master data in the customer's own Network instance. This data is never shared with Veeva OpenData..

Note: You can only update existing DCRs by file import; you cannot create new DCRs.

Third party data change requests are loaded along with the data update from the third party system. When you configure the source subscription for the third party data load, you can also indicate whether DCRs should also be loaded.

When the subscription runs, the provided DCR files are parsed and processed along with the data load. Statistics on the DCRs processed are provided in the data load summary when the job completes. A summary of accepted and rejected DCRs, by entity, is also provided.

DCR import files

The file names for DCR files provided in the Inbound FTP path for a source subscription must begin with “DCR_”. Any files whose names begin with this string will be imported with the source subscription for the third party data, if that subscription is configured to include DCR files.

The additional following considerations apply:

• Each DCR will only be processed once
• Master and custom keys must be provided when accepting DCRs
• File formats and column names are pre-defined
• Delimiters are hardcoded
• DCR import must occur with an incremental data update.

DCR response file:

Column Name	Explanation
DCR ID	Unique identifier of the DCR
DCR SECTION ID	Unique identifier of the DCR section (HCO, HCP, Address, Relation, or License)
DCR TYPE	Describes whether the DCR is an add request or a change request (ADD_REQUEST or CHANGE_REQUEST)
SUBJECT	Subject of the DCR
ENTITY TYPE	Type of added/changed Network entity (HCO, HCP, Address, Relation, License)
ENTITY ID	Unique identifier of the Network entity (can be NULL)
CUSTOM KEY SOURCE	Unique identifier of the third-party master system (must be provided by third-party provider)
CUSTOM KEY TYPE	Name of the entity in the third-party master system (must be provided by third-party provider)
CUSTOM KEY VALUE	Unique identifier of the entity in the third-party master system (must be provided by third-party provider)
RESULT	Final result of the DCR after the DCR is processed (CHANGE_ACCEPTED or CHANGE_REJECTED). Must be provided by third-party provider.
COMMENT	Comment by the third-party data provider