File

This code indicates both the table where the change takes place and the DW Staging table to update when you process changes. For example, a code of CST indicates a new or changed record in the Customer Sold To table; when you process changes, CWSerenade creates a record in the DW Customer Sold To table (or changes an existing record, if an additional transaction takes place before you have process changes).

Not all changes and activity are tracked through the DW Capture Transaction table. For example, a change to your company address is tracked in the DW Company table.

See CWSerenade Activities Captured in the DW Capture Transaction Table for more information on the CWSerenade activities that create a DW capture transaction record and the file code assigned to the DW capture transaction record, based on the CWSerenade table(s) referenced.

Alphanumeric, 3 positions; optional.

Capture date

The date that the activity took place, creating the record in the DW Capture Transaction table.

Numeric, 6 positions (MMDDYY); optional.

Capture time

The time that the activity took place, creating the record in the DW Capture Transaction table.

Numeric, 6 positions (HHMMSS); display-only.

Original process date

The date when the DW Capture Transaction record was processed, creating the record in the related DW Staging table; for example, this is the date that a CST record was processed, creating a record in the DW Customer Sold To table.

Numeric, 6 positions (MMDDYY); display-only.

Original process time

The time that the DW Capture Transaction record was processed, creating the record in the related DW Staging table; for example, this is the date that a CST record was processed, creating a record in the DW Customer Sold To table.

Numeric, 6 positions (HHMMSS); display-only.

Last process date

This date is the same as the original process date.

Numeric, 6 positions (MMDDYY); display-only.

Last process time

This time is the same as the original process time.

Numeric, 6 positions (HHMMSS); display-only.

From

The program that processed the transaction or activity creating the DW Capture Transaction record; for example, if you change a customer at the Change Customer Sold To screen, the program ID identifying that screen (CSR0078) appears here.

Alphanumeric, 10 positions; display-only.

A/C (Add/Change)

This flag indicates whether the activity represented creation of a new record, a change to an existing record, or a delete to an existing record. Valid values are:

A (Add) = A new record was added.

C (Change) = An existing record was modified.

D (Delete) = An existing record was deleted.

Note: Deletions are only captured for customer sold to records and customer bill to records.

Alphanumeric, 1 position; display-only.

Key

The key field information to uniquely identify the updated record. For example, if you change a Customer Sold To, the key might be 027000000317, where 027 indicates the company, and 000000317 indicates the customer number. Numeric fields are right-justified and zero-filled.

See What Key Data is Captured for each DW Capture Transaction Record? for more information on the key data captured in the File key field, based on the CWSerenade table(s) referenced in the File code field for the DW capture transaction record and the DW Staging table updated.

Alphanumeric, 80 positions; display-only.

Clear previously staged data

This field indicates whether to clear the DW Staging tables as part of the initial load. Normally, you would not need to clear this information, as the Relic program clears these tables after transferring the staging data to the CWData server; however, you might choose to clear data created through testing.

Valid values are:

Selected = Clear the data warehouse staging tables.

Unselected (default) = Do not clear the staging tables.

Process all files

This field indicates whether to download all supporting tables which are not related to customers or orders. These tables include reference information such as vendors, codes, financial and business structures, and the company itself. Normally, you would download these tables before downloading customer and order information.

Valid values are:

Selected (default)= Download all supporting tables not related to customers or orders.

Unselected = Do not download the supporting tables.

Starting with customer #

Use this field to indicate the first customer sold to number to include in the download. By specifying the first and last customer numbers to download, you can control the total number of records downloaded at one time and better allocate system resources. For example, if you have 5 million customer records, you can download these records in stages by first specifying the range of 1 to 1,000,000, then the range of 1,000,000 to 2,000,000, and so on.

Normally, you would begin downloading customers after you have downloaded the supporting tables, but before you begin the order download.

Note: The system does not validate that the starting and ending numbers are valid (that is, currently assigned to a customer sold to).

Numeric, 9 positions; optional.

Ending with customer #

Use this field together with the Starting with customer # field to specify the range of customers to download at this time.

Numeric, 9 positions; required if you specify a starting #.

Starting with order date

Use this field to download order-related tables by indicating the first order date to include in the download. By specifying the first and last order dates to download, you can control the total number of records downloaded at one time and better allocate system resources. For example, if you have 10 million orders, you can download these records in stages by first specifying a range of dates to include 2 million orders, then the next range of dates to include the next 2 million, and so on.

Normally, you would begin downloading order-related information after the supporting and customer table downloads are complete.

Note: The system does not validate that you have orders taken on the starting and ending dates.

Quotes: The system does not download quotes until they are converted to orders; see Entering Pre-Order Quotes.

Numeric, 6 positions (MMDDYY format); optional.

Ending with order date

Use this field together with the Starting with order date field to specific the range of order-related information to download at this time.

Numeric, 6 positions (MMDDYY format); required if you enter a starting order date.

Scheduled submit

This field indicates whether to schedule the change processing for a later time, or submit the job immediately. Valid values are:

Selected = Schedule the job for a later time; you will need to complete the Process time and Process date fields

Unselected (default) = Submit the job immediately

Process time

The time to submit the job, if you select to schedule the job for a later time.

Numeric, 6 positions (HH:MM:SS format); required if you select to schedule the job.

Process date

The date to submit the job, if you select to schedule the job for a later time. The current date defaults.

Numeric, 6 positions (MMDDYY format); required if you select to schedule the job.

From date

The starting date CWSerenade uses to clear the Original processed date field so that the records can be resubmitted during the next incremental load.

All records whose Original processed date was equal to or greater than the From date and less than or equal to the To date are reprocessed.

Numeric, 6 positions; required.

To date

The ending date CWSerenade uses to clear the Original processed date field so that the records can be resubmitted during the next incremental load.

All records whose Original processed date was equal to or greater than the From date and less than or equal to the To date are reprocessed.

Numeric, 6 positions; required.

File name

The name of the table containing records you wish to reprocess. Leave this field blank if you want to reprocess records based on date range alone.

Valid values are:

ACP = Accounting Period

ADD = Additional Charge

ADR = Add Reason Code

APD = A/R Payment Detail

APT = Terms

ARI = A/R Open Item

ART = A/R Type

BNK = Bank

BUY = Buyer

CAF = Customer Affinity

CBT = Customer Bill To

CCL = Customer Class

CCM = Customer Company

CEM = Customer Sold To Email

CHE = Customer Ship To Ent

CHH = Correspondence History

CIF = Customer Individual

CMP = Company

CNR = Cancel Reason

CNT = Country

CPL = Customer Profile

CRQ = Catalog Request

CSE = Customer Sold To

CSH = Customer Ship To

CSM = Customer Membership

CSO = Customer Ownership

CST = Customer Sold To

CWT = Customer Warranty

DIV = Division

DRN = Dispute Reason

ECA = E-Commerce Catalog

EIC = E-Commerce It

ENT = Entity

EXR = Exchange Reason

GZF = Geographic Zone

HAZ = Hazard

IAA = Item Attribute

IAT = Item Attribute

IAV = Item Attribute

ICC = Item Cycle

ICL = Item Class

IOF = Item Offer

IST = Item Status

ITC = Item Category

ITH = Item Transaction History

ITM = Item

ITW = Item Warehouse

LCL = Location Class

LDV = Long SKU Division

LNG = Language

LOB = Line of Business

LSC = Long SKU Class

LSD = Long SKU Description

LST = List Source

MCC = Mail/Call Code

MUA = Manifest Upload

ODT = Order Detail

OFR = Offer

OHD = Order Header

OPM = Order Payment Method

OST = Order Ship To

OTY = Order Type

PAY = Pay Type

PDA = Profile Data

PDT = PO Detail

POH = PO Header

POR = Price Override

PRD = RI Price Change Detail

PRH = RI Price Change Header

PRM = Promotion

PRP = Prep Code

RCY = Recency

RTC = Retail Class

RTR = Return Reason

SCG = Source Category

SEA = Season

SEO = SKU Element 1

SET = SKU Element 3

SEW = SKU Element 2

SKO = SKU Offer

SKU = SKU

SLC = Soldout Control

SLS = Salesman

SRC = Source

SXR = SKU Cross Reference

TRC = Item Transaction

TRR = Item Transaction

UPC = Item (SKU) UPC

USR = User

VIA = Ship Via

VIT = Vendor Item

VND = Vendor

WHS = Warehouse

Alphanumeric, 3 positions; optional.