1. Conducting a Study
  2. Batch Loading Data
  3. Using the Batch Data Loader
  4. Creating and Viewing Data File Entries
  5. Creating Data File Entries for Standard Batch Data Loads

Creating Data File Entries for Standard Batch Data Loads

If your data files have multiple DCMs per DCI or you want to process files from different studies at the same time, use Out of Study Batch Data Load instead; see Creating Data File Entries for Out of Study Batch Data Loads.

To specify the file for a standard Batch Data Load:

  1. From the Conduct menu, select Batch Data Load, then select Batch Load Data Files.

    The Maintain Load Data File window opens. The system automatically populates the Creation TS field for the data file name with the current date and time and the Status field with LOAD. You cannot change these fields; they change automatically as the data files are processed.

    Note:

    For test mode, from the Definition menu, select Test a Study, choose Batch Data Load, and then select Batch Data Load Files.
  2. Set your study context to the study you want to work with.
  3. Enter a data file group name in the Name field.
  4. Enter a separate record for each data file to be loaded.
    To select files from a directory, see Selecting Data Files.
  5. Enter the appropriate Format Mask for the files.
  6. Save your input.

To continue, go to Loading Data.

Table 7-4 Maintain Batch Load Data File Field Details

Name Description Size; Data Type
Name

Data file group name.

Mandatory.

 30; CHAR
Creation TS

Timestamp.

 20; DATE
Status

Whether the group file has completed all transfer of data.

 15; CHAR
Data File Name

Name of the data file, used internally by Oracle Clinical. The same data file name can be used subsequently for a different Received date. The name controls subsequent processing and therefore should be meaningful. Follow your company's naming policies.

Not updatable once the data file is processed.

 30; CHAR
Received

Date Oracle Clinical received the data file. Default value: current date and time. Not updatable once the data file is processed.

 18; Date
OS File Name

Operating system file name used to load this data file. Full file name and path (including disk name) should be specified.

The directory path must match the one entered in the BDL_ROOT setting of the OCL_STATE local reference codelist plus the user-specific subdirectory if BDL_USERDIRS in OCL_STATE is set to Y. The subdirectory name must be your username minus "OPS$" (if your username includes "OPS$"). The path cannot include quotation marks (" ").

Not updateable once the data file is processed.

 200; CHAR
Data File Status

Current status of the data file during load. It is system generated but you can change the Data File Status value to repeat an unsuccessful step of the batch load process. The following changes are allowed: from BAD LOAD to RECEIVED, from BAD REPAIR to DATA LOADED or RECEIVED, and from BAD TRANSFER/INSERT/UPDATE to PREPARED, DATA LOADED, or RECEIVED. Statuses include:

  • RECEIVED = 'Data file is received and is ready for load operation.
  • DATA LOADED = Load stage successfully completed.
  • BAD LOAD = Load stage unsuccessful, processing stopped.
  • PREPARED = Prepare stage successfully completed.
  • PART-PREPARED = Prepare stage successfully completed for some documents within the file.
  • BAD PREPARE = Prepare stage unsuccessful, processing stopped.
  • INSERTED = Transfer stage (insert) successfully completed.
  • BAD INSERT = Transfer stage (insert) unsuccessful, processing stopped.
  • UPDATED = Transfer stage (update) successfully completed.
  • BAD UPDATE = Transfer stage (update) unsuccessful, processing stopped.
  • BAD TRANSFER = Transfer unsuccessful.
  • COMPLETE = Transfer successful.
 15; CHAR
Lab

Code identifying the lab that is the data source — from the electronic file.Not updateable once the data file is processed.

 10; CHAR
Format Mask

Specifies the format for this data file load. LOV displays all active masks.

 N/A
Load TS

Date and time the file is loaded into the system. Not updateable once the data file is processed.

 18; DATE
Insert Status

Status of the insert. For example:

INSERTED = Transfer insert successful.

BAD INSERT = Insert failed.

PENDING = Prepare complete, awaiting Transfer.

NONE = Nothing to insert.

UNKNOWN = Initial setting.

 15; CHAR
Insert TS

Date and time the insert data in the file was transferred to the Oracle tables.

 18; DATE
Update Status

Status of the update. For example:

UPDATED = Transfer update successful.

BAD UPDATE = Update failed.

PENDING = Prepare complete, awaiting Transfer.

NONE = Nothing to update.

UNKNOWN = Initial setting.

 15; CHAR
Update TS

Date and time the update data in the file was transferred to the Oracle tables.

 18; DATE
Comment Text Free form comment text. Not updateable once the data file is processed. 200; CHAR

Parent topic: Creating and Viewing Data File Entries