Chapter 31: Forerunner IF/SO Interface (EFOR, DFOR) | Contents | SCVs | Search | Glossary | Reports | XML | Index | Chapter 33: Initializing the IS Report (IISR) |
Chapter 32: Generating the Forecast*21 Interface (GFOR)
Purpose: Use the Generate Forecast*21 Interface to send CWDirect information to the Forecast*21 system.
You can also specify an FTP application to send the interface files to the Forecast*21 system.
Generating the Forecast*21 Interface using a periodic process: You can generate the Forecast*21 Interface by running the F21EXTRACT periodic process. This periodic process includes the following periodic functions:
• F21PROD: This periodic function generates the Item and Product Information Interface. The program name is PFR0054.
• F21ORDT: This periodic function generates the Order Transaction Interface. The program name is PFR0057.
• F21SPOS: This periodic function generates the Stock Position Interface. The program name is PFR0059.
• F21KEYC: This periodic function generates the Key Code Interface. The program name is PFR0058.
• F21FTP: This periodic function calls an FTP application to send the interface files to the Forecast*21 system. The program name is PFR0060.
In this chapter:
• Generate Forecast*21 Extract Files Screen
• Item and Product Information Interface
• Offer Product SKU File (F21OPS)
• Component Demand File (F21CPD)
• Inventory Position File (F21IVP)
For more information: Refer to your Forecast*21 documentation for more information specific to the Forecast*21 system.
Generate Forecast*21 Extract Files Screen
Purpose: Use this screen to submit a batch program to populate the Forecast*21 Extract files associated with the Interfaces you selected.
Report sort sub-total: The error message Offer must have ’Report sort sub-total’ value before proceeding displays if the Report sort sub-total field in the offer file is blank.
Default settings: When you press F7, the system saves the setting of each field on this screen to the Default Options file, and the saved setting defaults the next time you advance to this screen. See Chapter 33: Working with Default Options (WDFT) for background.
How to display this screen: Enter GFOR in the Fast path field at the top of any menu or select Generate Forecast*21 Extract Files from a menu.
FCR0179 ENTER Generate Forcast 2/02/12 9:12:53 KAB Co2 Karen Bottger Company
Create Item and Product Information Interface . . . Y (Y/N) Include source records?. . N (Y/N) Include Offer records? . . N (Y/N) Offer Start Date 10112 FTP Application .
Create Order Transaction Interface . . . . . . . . (Y/N) Transactions from to FTP Application .
Create Stock Position Interface . . . . . . . . . . N (Y/N) FTP Application .
Process complete FTP Application .
F3=Exit F7=Save Options F9=Submit F12=Cancel |
Field |
Description |
Create item and product information interface |
This field indicates whether you wish to generate the Item and Product Information Interface. Valid values are: Y = Generate the Item and Product Information Interface. The system populates the Vendor Master File (F21VND), Item Master File (F21ITM), Vendor Item File (F21VIT), and Components File (F21CPT). The system also populates the Offer File (F21OFR), Offer Product File (F21OFP), and Offer Product SKU File (F21OPS) if the Include Offer records field is selected. N = Do not generate the Item and Product Information Interface. Your setting from the last time you pressed F7 defaults. Alphanumeric, 1 position; required. |
Include source records? |
This field indicates whether you wish to include source records in the Item and Product Interface. Valid values are: Y = Include source records in the Item and Product Interface. The system populates the Offer File (F21OFR), Offer Product File (F21OFP), and Offer Product SKU File (F21OPS). N = Do not include source records in the Item and Product Interface. The system does not populate the Offer, Offer Product, and Offer Product SKU extract files. Your setting from the last time you pressed F7 defaults. Alphanumeric, 1 position; required. |
Include offer records? |
This field indicates whether you wish to include offer records in the Item and Product Interface. Valid values are: Y = Include offer records in the Item and Product Interface. The system populates the Offer File (F21OFR), Offer Product File (F21OFP), and Offer Product SKU File (F21OPS). N = Do not include offer records in the Item and Product Interface. The system does not populate the Offer, Offer Product, and Offer Product SKU extract files. Your setting from the last time you pressed F7 defaults. Alphanumeric, 1 position; required. |
Offer start date |
The date you wish the system to use to select offers for the Item and Product Information Interface. All offers whose start date falls on or after the date you define are included in the extract. If you leave this field blank, the system includes all active offers. Your setting from the last time you pressed F7 defaults. Numeric, 6 positions (MMDDYY format); optional. |
FTP application |
The FTP application code that defines the FTP script you wish to execute after all of the extract files for the Item and Product Interface have been populated. The FTP script executes an FTP file transfer to the Forecast*21 system. If you do not define an FTP application code, you must manually transfer the extract files to the Forecast*21 system. FTP application codes are defined in and validated against the File Transfer Protocol file. Your setting from the last time you pressed F7 defaults. Alphanumeric, 3 positions; optional. |
Create order transaction interface |
This field indicates whether you wish to generate the Order Transaction Interface. Valid values are: Y = Generate the Order Transaction Interface. The system populates the Demand File (F21DMD), Component Demand File (F21CPD), Cancellations File (F21CNL), Backorders File (F21BKO), Shipments File (F21SHP), and Returns File (F21RTN). N = Do not generate the Order Transaction Interface. Your setting from the last time you pressed F7 defaults. Alphanumeric, 1 position; required. |
Transactions from/to |
The date range you wish the system to use to select order transactions for the Order Transaction Interface. All order transactions within the date range you defined are included in the extract. Your setting from the last time you pressed F7 defaults. An error message such as the following indicates if you enter a date in the “to” field that is later than the date in the “from” field: From date cannot be > To date. Numeric, 6 positions (MMDDYY format); optional. |
FTP application |
The FTP application code that defines the FTP script you wish to execute after all of the interface files for the Order Transaction Interface have been populated. The FTP script executes an FTP file transfer to the Forecast*21 system. If you do not define an FTP application code, you must manually transfer the interface files to the Forecast*21 system. FTP application codes are defined in and validated against the File Transfer Protocol file. Your setting from the last time you pressed F7 defaults. Alphanumeric, 3 positions; optional. |
Create stock position Interface |
This field indicates whether you wish to generate the Stock Position Interface. Valid values are: Y = Generate the Stock Position Interface. The system populates the Audit Record File (F21AUD), Inventory Position File (F21IVP), On Order File (F210NO), and On Backorder File (F210BO). N = Do not generate the Stock Position Interface. Your setting from the last time you pressed F7 defaults. Alphanumeric, 1 position; required. |
FTP application |
The FTP application code that defines the FTP script you wish to execute after all of the interface files for the Stock Position Interface have been populated. The FTP script executes an FTP file transfer to the Forecast*21 system. If you do not define an FTP application code, you must manually transfer the interface files to the Forecast*21 system. FTP application codes are defined in and validated against the File Transfer Protocol file. Your setting from the last time you pressed F7 defaults. Alphanumeric, 3 positions; optional. |
Create key code interface |
This field indicates whether you wish to generate the Key Code Interface. Valid values are: Y = Generate the Key Code Interface. The system populates the Audit Record File (F21AUD) and Key Code File (F21KYC). N = Do not generate the Key Code Interface. Your setting from the last time you pressed F7 defaults. Alphanumeric, 1 position; required. |
FTP application |
The FTP application code that defines the FTP script you wish to execute after all of the interface files for the Key Code Interface have been populated. The FTP script executes an FTP file transfer to the Forecast*21 system. If you do not define an FTP application code, you must manually transfer the interface files to the Forecast*21 system. FTP application codes are defined in and validated against the File Transfer Protocol file. Your setting from the last time you pressed F7 defaults. Alphanumeric, 3 positions; optional. |
Process complete FTP application |
The FTP application code that defines the FTP script you wish to execute after all of the interface files for all of the Interfaces have been populated. The FTP script executes an FTP file transfer to the Forecast*21 system. If you do not define an FTP application code, you must manually transfer the interface files to the Forecast*21 system. FTP application codes are defined in and validated against the File Transfer Protocol file. Your setting from the last time you pressed F7 defaults. Alphanumeric, 3 positions; optional. |
Screen Option |
Procedure |
Save the value you have defined in each field |
Press F7to have the system save the current setting of each field to the Default Options file. The saved settings default the next time you advance to this screen. If you press F7when any fields are blank, the system overwrites the previous Default Option setting (if any) with a blank setting. See Chapter 33: Working with Default Options (WDFT) for background. |
Submit a batch program to populate the Interface files and transfer the files to the Forecast*21 system, using the FTP application code you defined |
Press F9. The system displays a message similar to the following indicating the batch program has been submitted: |
Item and Product Information Interface
When you generate the Item and Product Information Interface, the system populates the:
• Vendor Master File (F21VND): new or updated information on vendors.
• Item Master File (F21ITM): new or updated information on SKUs.
• Vendor Item File (F21VIT): new or updated information on purchased items.
• Components File (F21CPT): new or updated information on component items.
• Offer File (F21OFR): new or updated information on offers.
• Offer Product File (F21OFP): items advertised in a specific offer.
• Offer Product SKU File (F21OPS): SKUs advertised in a specific offer.
Once all of the extract files for the Item and Product Information Interface have been populated, the system copies the files into a file named IP.XFR and creates a file named DONE.IP to indicate the process is complete.
Include offer records? The system populates the Offer File (F21OFR), Offer Product File (F21OFP), and Offer Product SKU File (F21OPS) only if the Include offer records field on the Generate Forecast*21 Extract Files Screen, or the Default Options file if you executed the F21PROD periodic function, is set to Y.
The system includes only offers whose start date falls on or after the offer start date you defined in the Offer start date field on the Generate Forecast*21 Extract Files Screen, or the Default Options file if you executed the F21PROD periodic function. If you did not define an offer start date, the system includes all active offers, where the current date is within the offer’s start and end dates.
The Vendor Master file contains vendor level information.
Field |
Position |
Format |
Description |
VM_REC_TYPE |
1-4 |
X(4) |
Set to VM. |
VM_SEQUENCE |
5-10 |
9(6) |
Set to 0. |
VM_COMPANY_ID |
11-12 |
X(2) |
The last 2 positions of the CWDirect company code. From the Company field in the Vendor file. |
VM_VENDOR_ID |
13-22 |
X(10) |
A code for the vendor. Right justified and zero-filled to 7 positions; for example: 0000012. From the Vendor # field in the Vendor file. |
VM_NAME |
23-52 |
X(30) |
The name of the vendor or the vendor’s company. From the Name field in the Vendor file. |
VM_CONTACT |
53-82 |
X(30) |
The name of the primary contact at the vendor site. From the Contact name field in the Vendor file. |
VM_ADDRESS1 |
83-112 |
X(30) |
The first 30 positions of the street address. From the Address line 1 field in the Vendor file. |
VM_ADDRESS2 |
113-142 |
X(30) |
The first 30 positions of address line 2. From the Address line 2 field in the Vendor file. |
VM_ADDRESS3 |
143-172 |
X(30) |
The first 30 positions of address line 3. From the Address line 3 field in the Vendor file. |
VM_CITY |
173-197 |
X(25) |
The city defined for the vendor’s address. From the City field in Vendor file. |
VM_STATE |
198-217 |
X(20) |
The state code defined for the vendor’s address. From the State field in the Vendor file. |
VM_COUNTRY |
218-227 |
X(10) |
The country code for the vendor’s address. From the Country field in the Vendor file. |
VM_POSTAL_CODE |
228-239 |
X(12) |
The postal code for the vendor’s address. From the Zip field in the Vendor file. |
VM_PHONE |
240-259 |
X(20) |
The vendor’s telephone number. From the Telephone number field in the Vendor file. |
VM_EXTENSION |
260-265 |
X(6) |
The telephone number extension. From the Extension field in the Vendor file. |
VM_FAX |
266-285 |
X(20) |
The vendor’s fax number. From the Fax number field in the Vendor file. |
VM_TERMS |
286-305 |
X(20) |
The first 20 positions of the terms code description. Not currently implemented. From the APT description field in the Vendor file. |
VM_CHANGE_FLAG |
306-306 |
X(1) |
Set to A (Add). |
VM_TERMS_CODE |
307-310 |
X(4) |
A code for the terms and conditions for payment to the vendor, such as 30 days after invoice date or at the end of the month. From the APT Code in the Terms file. |
Note: The following fields are not currently available in the CWDirect Forecast*21 integration. |
|||
VM_EMAIL |
311-360 |
X(50) |
Not currently implemented. |
VM_FREIGHT_ON_BOARD |
361-390 |
X(50) |
Not currently implemented. |
VM_SHIP_VIA_CODE |
391-394 |
X(4) |
Not currently implemented. |
VM_ORDER_PROCESS |
395-398 |
X(4) |
Not currently implemented. |
VM_TRANSIT_LEAD_TIME |
399-402 |
X(2) |
Not currently implemented. |
VM_RECEIVING_LEAD_ TIME |
403-406 |
X(4) |
Not currently implemented. |
VM_TOTAL_LEAD_TIME |
407-410 |
X(4) |
Not currently implemented. |
The Item Master file contains SKU level information.
Field |
Position |
Format |
Description |
IM_REC_TYPE |
1-4 |
X(4) |
Set to IM. |
IM_SEQUENCE |
5-10 |
9(6) |
Set to 0. |
IM_COMPANY_ID |
11-12 |
X(2) |
The last 2 positions of the CWDirect company code. From the Company field in the SKU file. |
IM_SKU |
13-32 |
X(20) |
The item number. If the item contains SKUs, the item number is followed by the SKU code, with a space between the item and each SKU code; for example: SKU ROSE WMNS SMLL. From the Item number and SKU code fields in the SKU file. Note: The system truncates this value to 20 positions. |
IM_UOM |
33-36 |
X(4) |
Set to 1. |
IM_DESCRIPTION |
37-86 |
X(50) |
• If the item is a non-SKUed item, the system populates this field with the item description. From the Item description field in the Item file. • If the item contains split SKUs, the system populates this field with the first 30 positions of the item description, followed by the SKU element 1 description, SKU element 2 description, and SKU element 3 description, with a space between each description; for example: PIMSKU3 DESCRIPTION CRANBERRY WOMENS DEPT SMALL. From the SKU description field in the SKU file, SKU element 1 description field in the SKU Element 1 file, SKU element 2 description field in the SKU Element 2 file, and SKU element 3 description field in the SKU Element 3 file. • If the item contains non-split SKUs, the system populates this field with the SKU description. From the SKU description field in the SKU file. |
IM_CATEGORY |
87-90 |
X(4) |
The item class defined for the item. From the Item class field in the Item file. |
IM_SUB_CATEGORY |
91-94 |
X(4) |
The long SKU department defined for the item. From the ITC category field in the SKU file. |
IM_STD_PRICE |
95-103 |
9(7)v9(2) |
The list price defined for the item/SKU. From the List price field in the SKU file. |
IM_STD_COST_EA |
104-113 |
9(6)v9(4) |
The standard cost defined for the item/SKU..0000 defaults if a standard cost is not defined. From the Standard cost field in the SKU file. |
IM_COST_EA |
114-123 |
9(6)v9(4) |
The average, standard, or FIFO cost, based on the value defined in the Costing Method system control value • If using average costing, from the Average cost field in the SKU file. • If using standard costing, from the Standard cost field in the SKU file. • If using FIFO costing, from the FIFO cost field in the SKU file. |
IM_STD_LEAD_TIME |
124-126 |
9(3) |
The lead days for the primary vendor defined for the item. From the Lead days field in the Vendor Item file. |
IM_BUYER |
127-136 |
X(10) |
A code for the buyer defined for the item. From the Buyer field in the Item file. |
IM_SCHEDULER |
137-146 |
X(10) |
A code for the buyer defined for the item. From the Buyer field in the Item file. |
IM_PRODUCT_ENGINEER |
147-156 |
X(10) |
Blank-filled. |
IM_ITEM_TYPE |
157-160 |
X(4) |
The kit type defined for the item. • SKU = No kit type defined. • KIT = Kit type S Set, C Continuity, or V Variable Set. • MFR = Kit type F Finished Good. Based on the Kit type field in the Item file. |
IM_DEFAULT_VENDOR |
161-170 |
X(10) |
The primary vendor defined for the item. From the Vendor number field in the Item file. |
IM_CREATION_DATE |
171-178 |
9(8) |
Blank filled. |
IM_CLASSIFICATION_CODE |
179-196 |
X(18) |
Blank filled. |
IM_MS_STYLE |
197-216 |
X(20) |
The item code. From the Item number field in the Item file. |
IM_MS_DESCRIPTOR1 |
217-226 |
X(10) |
The second SKU element defined for the item. From the SEW Code field in the SKU file. * or NONE defaults if the item is a non-SKUed item or you are not using split SKUs (the Split SKU Inventory (A26) system control value is set to N). |
IM_MS_DESCRIPTOR2 |
227-236 |
X(10) |
The first SKU element for the item. From the SEO Code field in the SKU file. * or NONE defaults if the item is a non-SKUed item or you are not using split SKUs (the Split SKU Inventory (A26) system control value is set to N). |
IM_MS_DESCRIPTOR3 |
237-246 |
X(10) |
The third SKU element for the item. From the SET Code field in the SKU file. * or NONE defaults if the item is a non-SKUed item or you are not using split SKUs (the Split SKU Inventory (A26) system control value is set to N). |
IM_CHANGE_FLAG |
247-247 |
X(1) |
Set to A (Add). |
IM_SUB_PRODUCT_CODE |
248-251 |
X(4) |
Set to DFLT. |
IM_SKU_STATUS |
252-252 |
X(1) |
Defines whether the item is active. • A = Active. The Restrict orders field in the SKU file is N. • I = Inactive. The Restrict orders field in the SKU file is Y. |
IM_DROP_SHIP_FLAG |
253-253 |
X(1) |
Defines whether the item is a drop ship item. • T = The item is a drop ship item. The Drop ship field in the Item file is Y. • F = The item is not a drop ship item. The Drop ship field in the Item file is N. |
IM_CLASS_CODE |
254-261 |
X(8) |
Blank-filled. |
IM_CUSTOMIZATION_CODE |
262-265 |
X(4) |
Blank-filled. |
IM_ALTERNATE_SKU |
266-285 |
X(20) |
Blank-filled. |
IM_ADDTL_COST |
286-293 |
9(8) |
Set to .0000. |
IM_ADDTL_SHIP_COS |
294-301 |
9(8) |
Set to .0000. |
IM_WEIGHT |
302-309 |
9(8) |
The shipping weight of the item. From the Ship weight field in the Item file. |
IM_LENGTH |
310-314 |
9(5) |
The length measurement of the item. From the Length field in the Item file. |
IM_WIDTH |
315-319 |
9(5) |
The width measurement of the item. From the Width field in the Item file. |
IM_DEPTH |
320-324 |
9(5) |
The height measurement of the item. From the Height field in the Item file. |
IM_USER1 |
325-334 |
9(10) |
Blank-filled. |
Note: The following fields are not currently available in the CWDirect Forecast*21 integration. |
|||
IM_USER2 |
335-344 |
9(10) |
Not currently implemented. |
IM_USER3 |
345-354 |
X10) |
Not currently implemented. |
IM_USER4 |
355-364 |
X(10) |
Not currently implemented. |
IM_USER5 |
365-374 |
X(10) |
Not currently implemented. |
IM_USER6 |
375-384 |
X(10) |
Not currently implemented. |
IM_USER7 |
385-394 |
X(10) |
Not currently implemented. |
IM_USER8 |
395-404 |
X(10) |
Not currently implemented. |
IM_INVENTORY_VARIANCE_EA |
405-414 |
9(6)v9(4) |
Not currently implemented. |
IM_DIRECT_LABOR_EA |
415-424 |
9(6)v9(4) |
Not currently implemented. |
DEFAULT_WAREHOUSE_ID |
425-426 |
X(2) |
Not currently implemented. |
This file transfers new or updated information on purchased items to the Forecast*21 system.
Field |
Position |
Format |
Description |
VI_REC_TYPE |
1-4 |
X(4) |
Set to VI. |
VI_SEQUENCE |
5-10 |
9(6) |
Set to 0. |
VI_COMPANY_ID |
11-12 |
X(2) |
The last 2 positions of the CWDirect company code. From the Company field in the Vendor Item file. |
VI_VENDOR_ID |
13-22 |
X(10) |
A code to identify the vendor. From the Vendor # field in the Vendor Item file. |
VI_SKU |
23-42 |
X(20) |
The item number and SKU code. • If this is a non-SKUed item, from the Item number field in the Vendor Item file. • If this is a SKUed item, from the Item number and SKU code fields in the Vendor Item file, with a space between the item and each SKU code. Note: The system truncates this value to 20 positions. |
VI_VENDOR_PART_ID |
43-62 |
X(20) |
The vendor item number. From the Item field in the Vendor Item file. |
VI_VENDOR_PART_DESC |
63-112 |
X(50) |
A description of the vendor item number. From the Description field in the Vendor Item file. |
VI_COST_EA |
113-122 |
9(6)v9(4) |
The vendor’s price for each unit of the item. From the Price field in the Vendor Item file. If a unit of measure if also defined for the vendor item, the system uses this calculation to determine the vendor’s price: Vendor unit of measure / vendor price = vendor cost per unit. Based on the Price and Unit of measure fields in the Vendor Item file. |
VI_LEAD_TIME |
123-125 |
9(3) |
The lead days defined for the vendor item. From the Lead days field in the Vendor Item file. |
VI_UOM |
126-129 |
X(4) |
The unit of measure for the vendor item. From the Unit of measure field in the Vendor Item file. |
VI_MOQ |
130-137 |
9(8) |
The minimum quantity for the vendor item. From the Minimum quantity field in the Vendor Item file. |
VI_FREIGHT_EA |
138-145 |
9(4)v9(4) |
The total additional charges for the vendor item. From the Unit amount percent field in the Vendor Item Additional Charges file. If the charge is defined as a percent, the system calculates the unit charge using the percent and vendor price. |
VI_CHANGE_FLAG |
146-146 |
X(1) |
Set to A (Add). |
VI_LOT_SIZE |
147-152 |
9(6) |
Not currently implemented. |
This file transfers new or updated component item information to the Forecast*21 system.
The system retrieves component item information from the following files in CWDirect:
• Set and Set Detail files for sets (S kit type).
• Variable Set and Variable Set Detail files for variable sets (V kit type).
• Continuity Header and Continuity Detail files for continuity sets (C kit type).
• Kit and Kit Detail for finished good sets (F kit type)..
Field |
Position |
Format |
Description |
CPNT_REC_TYPE |
1-4 |
X(4) |
Set to CPNT. |
CPNT_SEQUENCE |
5-10 |
9(6) |
A unique sequence number assigned to each record in the file, beginning with 1. |
CPNT_COMPANY_ID |
11-12 |
X(2) |
The last 2 positions of the CWDirect company code. From the Company field in the Set Detail, Continuity Detail, or Kit Detail file. |
CPNT_COMPONENT_SKU |
13-32 |
X(20) |
The component item number. If the component item contains SKUs, the item number is followed by the component SKU code, with a space between the item number and each SKU code; for example: CMP ROSE XSML WMNS. From the Component item number and Component SKU code fields in the Set Detail, Variable Set Detail, Continuity Detail, or Kit Detail file. Note: The system truncates this value to 20 positions. |
CPNT_QUANTITY |
33-42 |
9(4)v9(6) |
The number of units of the component item to include in one set. From the Quantity field in the Set Detail, Variable Set Detail, Continuity Detail, or Kit Detail file. |
CPNT_SKU |
43-62 |
X(20) |
The item number that represents the main set item that is made up of the component items. If the set item contains SKUs, the item number is followed by the SKU code, with a space between the item number and each SKU code; for example: SET ROSE XSML WMNS. From the Item number and SKU code fields in the Set Detail, Variable Set Detail, Continuity Detail, or Kit Detail file. Note: The system truncates this field to 20 positions. |
CPNT_CHANGE_FLAG |
63-63 |
X(1) |
Set to A (Add). |
This file transfers new or updated information on offers to the Forecast*21 system.
The system looks at the Offer file for offers whose start date falls on or after the specified offer start date. If an offer start date has not been defined, the system includes all offers, where today’s date falls within the offer start and end dates.
Field |
Position |
Format |
Description |
OFFR_REC_TYPE |
1-4 |
X(4) |
Set to OFFR. |
OFFR_SEQUENCE |
5-10 |
9(6) |
A unique number assigned to each record in the file. |
OFFR_COMPANY_ID |
11-12 |
X(2) |
The last 2 positions of the CWDirect company code. From the Company field in the Offer file. |
OFFR_DIVISION_ID |
13-14 |
X(2) |
The division code for the default source code associated with the offer. From the Division field in the Source file. |
OFFR_OFFER_ID |
15-24 |
X(10) |
The offer code. From the Offer number field in the Offer file. |
OFFR_OFFER_YEAR |
25-28 |
9(4) |
The accounting period in which the offer start date falls. From the Accounting period year field in the Accounting Period file. |
OFFR_DESCRIPTION |
29-58 |
X(30) |
The description of the offer. From the Description field in the Offer file. |
OFFR_NUMBER_PAGES |
59-62 |
9(4) |
The number of pages in the offer. From the # of pages field in the Offer file. |
OFFR_VEHICLE_ID |
63-66 |
X(4) |
Blank-filled. |
OFFR_SEASON_ID |
67-70 |
X(4) |
The season defined for the offer. From the Season field in the Offer file. |
OFFR_MEDIA_ID |
71-74 |
X(4) |
Blank-filled. |
OFFR_MACRO_CIRCULATION |
75-83 |
9(9) |
The total gross circulation for all source codes associated with the offer. From the Net circulation field in the Source file. |
OFFR_MACRO_ORDERS |
84-92 |
9(9) |
Blank-filled. |
OFFR_MACRO_UNITS |
93-101 |
9(9) |
Blank-filled. |
OFFR_MACRO_REVENUE |
102-113 |
9(10)V9 (2) |
Blank-filled. |
OFFR_ANTICIP_DROP_DTE |
114-121 |
9(8) |
The start date of the offer, in MMDDYY format. From the Start date field in the Offer file. |
OFFR_ANTICIP_PERIOD_1_DTE |
122-129 |
9(8) |
The start date of the offer, in MMDDYY format. From the Start date field in the Offer file. |
OFFR_ANTICIP_END_DATE |
130-137 |
9(8) |
The end date of the offer, in MMDDYY format. From the Offer Stop date field in the Offer file. |
OFFR_ACTUAL_DROP_ DTE |
138-145 |
9(8) |
Blank-filled. |
OFFR_ACTUAL_PERIOD_1_DTE |
146-153 |
9(8) |
Blank-filled. |
OFFR_ACTUAL_END_DTE |
154-161 |
9(8) |
Blank-filled. |
OFFR_CHANGE_FLAG |
162-162 |
X(1) |
Set to A (Add). |
OFFR_USER_FIELDS |
163-196 |
X(34) |
Blank-filled. |
OFFR_TYPE |
197-206 |
X(10) |
Not currently implemented. |
This file transfers new or updated information on the products in the specified offer to the Forecasting*21 system.
The system looks at the Item Offer and SKU Offer files for offers whose start date falls on or after the specified offer start date. If an offer start date has not been defined, the system includes all offers, where today’s date falls within the offer start and end dates.
Field |
Position |
Format |
Description |
OP_REC_TYPE |
1-4 |
X(4) |
Set to OP. |
OP_SEQUENCE |
5-10 |
9(6) |
A unique number assigned to each record in the file. |
OP_COMPANY_ID |
11-12 |
X(2) |
The last 2 positions of the CWDirect company code. From the Company field in the Item Offer or SKU Offer file. |
OP_DIVISION_ID |
13-14 |
X(2) |
The division code for the default source code associated with the offer. From the Division field in the Source file. |
OP_OFFER_ID |
15-24 |
X(10) |
The offer code. From the Offer number field in the Item Offer or SKU Offer file. |
OP_OFFER_YEAR |
25-28 |
9(4) |
The accounting period year in which the offer start date falls. From the Accounting period year field in the Accounting Period file. |
OP_PRODUCT |
29-48 |
X(20) |
The item number. From the Item number field in the Item Offer or SKU Offer file. |
OP_DESCRIPTION |
49-98 |
X(50) |
The description of the item. From the Item description field in the Item file. |
OP_CATEGORY |
99-102 |
X(4) |
The long SKU class defined for the item. 0000 displays. From the Item class field in the Item file. |
OP_SUBCATEGORY |
103-106 |
X(4) |
The long SKU department defined for the item. From the Item category field in the SKU file. |
OP_THEME |
107-110 |
X(4) |
Blank-filled. |
OP_PAGE_NO |
111-118 |
X(8) |
The page number for the item. The page number is limited to 3 positions, left justified, and padded with leading zeros. Example: Page 5 displays as 005. From the Page field in the Item Offer or SKU Offer file. |
OP_PAGE_PERCENT |
119-125 |
9(1)V9(6) |
.000000 defaults. |
OP_PAGE_POSITION |
126-128 |
X(3) |
Blank-filled. |
OP_MULTIPAGE_PERCENT |
129-135 |
9(1)V9(6) |
.000000 defaults. |
OP_CHANGE_FLAG |
136-136 |
X(1) |
Set to A (Add). |
OP_CURVE_ID |
137-140 |
X(4) |
Not currently implemented. |
Offer Product SKU File (F21OPS)
This file transfers new or updated information on the SKUs in the specified offer to the Forecasting*21 system.
The system looks at the Item Offer and SKU Offer files for offers whose start date falls on or after the specified offer start date. If an offer start date has not been defined, the system includes all offers, where today’s date falls within the offer start and end dates.
Field |
Position |
Format |
Description |
OPS_REC_TYPE |
1-4 |
X(4) |
Set to OPS. |
OPS_SEQUENCE |
5-10 |
9(6) |
A unique number assigned to each record. |
OPS_COMPANY_ID |
11-12 |
X(2) |
The last 2 positions of the CWDirect company code. From the Company field in the SKU Offer or Item Offer file. |
OPS_DIVISION_ID |
13-14 |
X(2) |
The division code for the default source code associated with the offer. From the Division field in the Source file. |
OPS_OFFER_ID |
15-24 |
X(10) |
The offer code. From the Offer number field in the SKU Offer or Item Offer file. |
OPS_OFFER_YEAR |
25-28 |
9(4) |
The accounting period year in which the offer start date falls. From the Accounting period year field in the Accounting Period file. |
OPS_SKU |
29-48 |
X(20) |
The item number and SKU code. • If this is a non-SKUed item, from the Item number field in the SKU file. • If this is a SKUed item, from the Item number and SKU code fields in the SKU file, with a space between the item and each SKU code. Note: The system truncates this field to 20 positions. |
OPS_PRODUCT |
49-68 |
X(20) |
The item number. From the Item number field in the SKU Offer or Item Offer file. |
OPS_DESCRIPTOR1 |
69-78 |
X(10) |
The second SKU element for the item. From positions 6-9 of the SKU code field in the SKU Offer or Item Offer file. NONE defaults if this is a non-SKUed item or does not contain split SKUs (the Split SKU Inventory (A26) system control value is set to N). |
OPS_DESCRIPTOR2 |
79-88 |
X(10) |
The first SKU element for the item. From positions 1-4 of the SKU code field in the SKU Offer or Item Offer file. NONE defaults if this is a non-SKUed item or does not contain split SKUs (the Split SKU Inventory (A26) system control value is set to N). |
OPS_DESCRIPTOR3 |
89-98 |
X(10) |
The third SKU element for the item. From positions 11-14 of the SKU code field in the SKU Offer or Item Offer file. NONE defaults if this is a non-SKUed item or does not contain split SKUs (the Split SKU Inventory (A26) system control value is set to N). |
OPS_DESCRIPTION |
99-148 |
X(50) |
A description of the item. • If this is a non-SKUed item, from the Item description field in the Item file. • If this is a SKUed item, from the first 30 positions of the Item description field in the Item file + the SKU element 1 description field in the SKU Element 1 file + the SKU element 2 description field in the SKU Element 2 file + the SKU element 3 description field in the SKU Element 3 file, with a space between each description. • If split SKUs are not used, from the SKU description field in the SKU file. |
OPS_UNIT_PRICE |
149-155 |
9(5)V9(2) |
The price of the item. From the Price field in the SKU Price file; if a SKU price is not defined, from the Price field in the Item Price file. Note: The system uses the price with a quantity break of 1 and the most recent effective date. |
OPS_CHANGE_FLAG |
156-156 |
X(1) |
Set to A (Add). |
OPS_SH_COST_EA |
157-164 |
9(4)V9(4) |
.0000 |
OPS_SH_REVENUE_EA |
165-172 |
9(4)V9(4) |
.0000 |
OPS_BAD_DEBT_PERCENT |
173-178 |
V9(6) |
.000000 |
OPS_VARIABLE_COST_ PERCENT |
179-184 |
V9(6) |
.000000 |
OPS_RETURNS_PERCENT |
185-190 |
V9(6) |
From the Expected return percent field in the SKU Offer or Item Offer file. |
OPS_RETURN_SH_COST_ EA |
191-198 |
9(4)V9(4) |
.0000 |
OPS_RETURN_SH_ REVENUE_EA |
199-206 |
9(4)V9(4) |
.0000 |
Note: The following fields are not currently available in the CWDirect Forecast*21 integration. |
|||
OPS_EXCESS_COST_EA |
207-214 |
9(4)V9(4) |
Not currently implemented. |
OPS_BACKORDER_COST_EA |
215-222 |
9(4)V9(4) |
Not currently implemented. |
OPS_RETURNS_ PROCESSING_COST_EA |
223-230 |
9(4)V9(4) |
Not currently implemented. |
OPS_ADMIN_COST_EA |
231-238 |
9(4)V9(4) |
Not currently implemented. |
OPS_PLANT_VAR_COST_ EA |
239-246 |
9(4)V9(4) |
Not currently implemented. |
OPS_PLANT_VAR_LABOR_COST_EA |
247-254 |
9(4)V9(4) |
Not currently implemented. |
OPS_ORDER_PROCESSING_COST_EA |
255-262 |
9(4)V9(4) |
Not currently implemented. |
OPS_FACILITY_COST_EA |
263-270 |
9(4)V9(4) |
Not currently implemented. |
OPS_CREDIT_COST_EA |
271-278 |
9(4)V9(4) |
Not currently implemented. |
When you generate the Order Transaction Interface, the system populates:
• Demand File (F21DMD): order demand information.
• Component Demand File (F21CPD): order information, such as the number of units ordered and the total price.
• Cancellations File (F21CNL): information on canceled orders.
• Backorders File (F21BKO): information on backordered items.
• Shipments File (F21SHP): information on immediate shipments, backordered shipments, and future shipments.
• Returns File (F21RTN): information on returned items.
Once the extract files for the Order Transaction Interface have been populated, the system copies the files into a file named OP.XFR.
The first record in each interface file is an audit record that contains the following information.
Field |
Type |
Position |
Format |
Description |
Sequential file number |
Number |
1-6 |
9(6) |
From the number assignment file. |
Date created |
Number |
7-14 |
YYYYMMDD |
Current date in YYYYMMDD format. |
Time created (military) |
Number |
15-18 |
HHMM |
Current time in HHMM format. |
Number of records |
Number |
19-26 |
9(8) |
Total number of records in the OT.XFR file (including the audit record). |
Extended price total |
Number |
27-36 |
9(8)V9(2) |
Sum of all: DMND_EXT_PRICE CNCL_EXT_PRICE BACK_EXT_PRICE SHIP_EXT_PRICE RETN_EXT_PRICE |
Interface version used |
Number |
37-41 |
9(5) |
00271 |
The system populates the Demand file with order detail line information from CWDirect. The system updates the Demand file using the following information:
• passed company.
• the order detail line falls within the passed transaction date range.
• the quantity ordered is greater than 0 (this excludes returns entered as new order lines).
• all order detail line statuses are included (open, closed, canceled, sold out, held, and express billed).
• order detail lines representing components are not sent to the Demand Interface file. Set master items are sent. Demand for component item is sent in a separate interface file. You can identify an order detail line for a set component by the set sequence number is greater than 0 and the set main item is set to N.
The system creates one demand interface record for each order detail line.
Field |
Position |
Format |
Description |
DMND_REC_TYPE |
1-4 |
X(4) |
Set to DMND. |
DMND_REC_ACTION |
5 |
X(1) |
Set to A (Add). |
DMND_SEQUENCE |
6-11 |
9(6) |
The next available sequence number from the Forecast21 Order Transaction Sequence Number number assignment value. |
DMND_COMPANY_ID |
12-13 |
X(2) |
The last 2 positions of the CWDirect company code. From the Company field in the Order Detail file. |
DMND_DIVISION_ID |
14-15 |
X(2) |
The division code for the source code defined for the order line or order header. From the Division field in the Source file. |
DMND_ORDER_NUM |
16-30 |
X(15) |
The order number and ship to number, separated by a hyphen. Example: 99999999-999. From the Order # and Ship to # fields in the Order Detail file. |
DMND_ORDER_LINE |
31-36 |
9(6) |
The order detail sequence number. From the Sequence # field in the Order Detail file. |
DMND_OFFER_ID |
37-46 |
X(10) |
The offer defined for the order line. From the Offer field in the Order Detail file. |
DMND_OFFER_YEAR |
47-50 |
9(4) |
The accounting period year in which the offer start date falls. From the Accounting period year field in the Accounting Period file. |
DMND_KEY_CODE |
51-70 |
X(20) |
The source code defined for order line; if not defined at the order line level, the source code defined for the order header. From the Source code field in the Order Detail file or Order Header file. |
DMND_TRANS_DATE |
71-78 |
9(8) |
The entry date for the order line, in MMDDYYYY format. From the Entered date field in the Order Detail file. |
DMND_SKU |
79-98 |
X(20) |
The item number and SKU code on the order line. • If this is a non-SKUed item, from the Item number field in the Order Detail file. • If this is a SKUed item, from the Item number and SKU code fields in the Order Detail file, with a space between the item and each SKU code. Note: The system truncates this field to 20 positions. |
DMND_PRODUCT |
99-118 |
X(20) |
The item number on the order line. From the Item number field in the Order Detail file. |
DMND_DESCRIPTOR1 |
119-128 |
X(10) |
The second SKU of the item on the order line. From positions 6-9 of the SKU Code field in the Order Detail file. NONE defaults if the item is a non-SKUed item or does not contain split SKUs (the Split SKU Inventory (A26) system control value is set to N). |
DMND_DESCRIPTOR2 |
129-138 |
X(10) |
The first SKU of the item on the order line. From positions 1-4 of the SKU Code field in the Order Detail file. NONE defaults if this item is a non-SKUed item or does not contain split SKUs (the Split SKU Inventory (A26) system control value is set to N). |
DMND_DESCRIPTOR3 |
139-148 |
X(10) |
The third SKU of the item on the order line. From positions 11-14 of the SKU Code field in the Order Detail file. NONE defaults if this item is a non-SKUed item or does not contain split SKUs (the Split SKU Inventory (A26) system control value is set to N). |
DMND_CUST_SOLD |
149-164 |
X(16) |
The sold to customer number on the order. From the Customer # field in the Order Header file. |
DMND_CUST_SHIP |
165-180 |
X(16) |
The ship to customer number defined for the order; if a ship to customer is not defined, the sold to customer on the order header defaults. From the Customer # field in the Order Ship To file; otherwise, from the Customer # field in the Order Header file. |
DMND_QUANTITY |
181-188 |
9(8) |
The quantity ordered on the order line. From the Qty ordered field in the Order Detail file. |
DMND_QTY_SIGN |
189-189 |
X(1) |
Set to +. |
DMND_EXT_PRICE |
190-199 |
9(8)V9(2) |
Calculated field: quantity ordered x order detail price = demand extended price |
DMND_EXT_PRICE_SIGN |
200-200 |
X(1) |
Set to +. |
DMND_EXTENDED_COST |
201-210 |
9(8)V9(2) |
Calculated field: quantity ordered x average cost, standard cost, or FIFO cost The system uses the cost override on the order detail line if the cost is greater than zero. Note: The cost method is based on the value defined in the Costing Method (A25) system control value. |
DMND_EXT_COST_SIGN |
211-211 |
X(1) |
Set to +. |
DMND_DEMAND_FROM |
212-213 |
X(2) |
The order type on the order. From the Order type field in the Order Header file. |
DMND_DEMAND_TYPE |
214-217 |
X(4) |
Demand type. Valid values: • ORIG = The Promotion used and Upsell/Cross-sell fields in the Order Detail file are blank or N. • CRSL = The Upsell/Cross-sell field in the Order Detail file is A or C. • UPSL = The Upsell/Cross-sell field in the Order Detail file is T or the Promotion used field is populated and the Upsell/Cross-sell field in the Order Detail file is blank. • MISC = The Upsell/Cross-sell field in the Order Detail file is Y, or the demand type cannot be determined. |
DMND_DISPOSITION |
218-221 |
X(4) |
Blank-filled. |
DMND_DISPOSITION_DATE |
222-229 |
9(8) |
The entry date for the order line, in MMDDYY format. From the Entered date field in the Order Detail file. |
DMND_DISPOSITION_OTH |
230-233 |
X(4) |
Blank-filled. |
DMND_SH_COST |
234-245 |
9(8)V9(4) |
.0000 defaults. |
DMND_SH_COST_SIGN |
246-246 |
X(1) |
+ defaults. |
DMND_SH_REVENUE |
247-258 |
9(8)V9(4) |
.0000 defaults. |
DMND_SH_REVENUE_SIGN |
259-259 |
X(1) |
+ defaults. |
DMND_SHIP_METHOD |
260-263 |
X(4) |
Blank-filled. |
DMND_PAY_METHOD |
264-265 |
X(2) |
Blank-filled. |
Note: The following fields are not currently available in the CWDirect Forecast*21 integration. |
|||
DMND_TOTAL_CREDIT |
266-277 |
9(8)V9(4) |
Not currently implemented. |
DMND_TOTAL_CREDIT_ SIGN |
278-278 |
X(1) |
Not currently implemented. |
DMND_SALESPERSON |
279-288 |
X(10) |
Not currently implemented. |
DMND_LIST_PRICE |
289-300 |
9(8)V9(4) |
Not currently implemented. |
DMND_LIST_PRICE_SIGN |
301-301 |
X(1) |
Not currently implemented. |
Component Demand File (F21CPD)
The system populates the Component Demand file with order detail information from CWDirect. The system selects order detail information based on:
• passed company.
• the order detail line falls within the passed transaction date range.
• the quantity ordered is greater than zero (this excludes returns entered as new order lines).
• all order detail statuses are included (open, closed, canceled, sold out, held, express billed).
• only order detail lines representing component items are included. Set master items are sent in the demand interface. You can identify a component item by the set sequence number is greater than zero and the set main item is set to N.
One component demand interface record is created for each order detail line selected.
Field |
Position |
Format |
Description |
DCMP_REC_TYPE |
1-4 |
X(4) |
Set to DMND. |
DCMP_REC_ACTION |
5 |
X(1) |
Set to A. |
DCMP_SEQUENCE |
6-11 |
9(6) |
A unique number assigned to each record in the file. |
DCMP_COMPANY_ID |
12-13 |
X(2) |
The last 2 positions of the CWDirect company code. From the Company field in the Order Detail file. |
DCMP_DIVISION_ID |
14-15 |
X(2) |
The division code for the source code defined for the order line or order header. From the Division field in the Source file. |
DCMP_ORDER_NUM |
16-30 |
X(15) |
The order number and ship to number on the order line, separated by a hyphen. Example: 99999999-999. From the Order # and Ship to # fields in the Order Detail file. |
DCMP_ORDER_LINE |
31-36 |
9(6) |
The order line sequence number. From the Sequence # field in the Order Detail file. |
DCMP_OFFER_ID |
37-46 |
X(10) |
The offer defined for the order line. From the Offer field in the Order Detail file. |
DCMP_OFFER_YEAR |
47-50 |
9(4) |
The accounting period year in which the offer start date falls. From the Accounting period year field in the Accounting Period file. |
DCMP_KEY_CODE |
51-70 |
X(20) |
The source code on the order line; otherwise, the source code on the order header. From the Source code field in the Order Detail file or Order Header file. |
DCMP_TRANS_DATE |
71-78 |
9(8) |
The entry date on the order line, in MMDDYYYY format. From the Entry date field in the Order Detail file. |
DCMP_SKU |
79-98 |
X(20) |
The item number and SKU code. • If this item is a non-SKUed item, from the Item number field in the Order Detail file. • If this item is a SKUed item, from the Item number and SKU code fields in the Order Detail file, with a space between the item and each SKU code. Note: The system truncates this field to 20 positions. |
DCMP_PRODUCT |
99-118 |
X(20) |
The item number on the order line. From the Item number field in the Order Detail file. |
DCMP_DESCRIPTOR1 |
119-128 |
X(10) |
The second SKU of the cancelled item. From positions 6-9 of the SKU Code field in the Order Detail file. NONE defaults if the item is a non-SKUed item or does not contain split SKUs (the Split SKU Inventory (A26) system control value is set to N). |
DCMP_DESCRIPTOR2 |
129-138 |
X(10) |
The first SKU of the cancelled item. From positions 1-4 of the SKU Code field in the Order Detail file. NONE defaults if the item is a non-SKUed item or does not contain split SKUs (the Split SKU Inventory (A26) system control value is set to N). |
DCMP_DESCRIPTOR3 |
139-148 |
X(10) |
The second SKU of the cancelled item. From positions 11-14 of the SKU Code field in the Order Detail file. NONE defaults if the item is a non-SKUed item or does not contain split SKUs (the Split SKU Inventory (A26) system control value is set to N). |
DCMP_CUST_SOLD |
149-164 |
X(16) |
The sold to customer number on the order. From the Customer # field in the Order Header file. |
DCMP_CUST_SHIP |
165-180 |
X(16) |
The ship to customer number on the order; if not defined, the sold to customer number on the order defaults. From the Customer # field in the Order Ship To file or Order Header file. |
DCMP_QUANTITY |
181-188 |
9(8) |
The quantity ordered on the order line. From the Quantity ordered field in the Order Detail file. |
DCMP_QTY_SIGN |
189 |
X(1) |
Set to +. |
DCMP_EXT_PRICE |
190-199 |
9(8)V9(2) |
Set component items are not priced in order entry, only the set master item. .00 defaults. |
DCMP_EXT_PRICE_SIGN |
200 |
X(1) |
Set to +. |
DCMP_EXTENDED_COST |
201-210 |
9(8)V9(2) |
The extended cost of the item. Calculated field: quantity ordered x average cost, standard cost, or FIFO cost The system uses the cost override on the order detail line if the cost is greater than zero. Note: The cost method is based on the value defined in the Costing Method system control value. |
DCMP_EXT_COST_SIGN |
211 |
X(1) |
Set to +. |
DCMP_DEMAND_FROM |
212-213 |
X(2) |
The order type on the order. From the Order type field in the Order Header file. |
DCMP_DEMAND_TYPE |
214-217 |
X(4) |
The demand type. Valid values: • ORIG = The Promotion used and Upsell/Cross-sell fields in the Order Detail file are blank or N. • CRSL = The Upsell/Cross-sell field in the Order Detail file is A or C. • UPSL = The Upsell/Cross-sell field is T, or the Promotion used field in the Order Detail file is populated and the Upsell/Cross-sell field is blank. • MISC = The Upsell/Cross-sell field in the Order Detail file is Y, or the demand type cannot be determined. |
DCMP_DISPOSITION |
218-221 |
X(4) |
Blank-filled. |
DCMP_DISPOSITION_DATE |
222-229 |
9(8) |
The entry date for the order line, in MMDDYYYY format. From the Entry date field in the Order Detail file |
DCMP_DISPOSITION_OTH |
230-233 |
X(4) |
Blank-filled. |
DCMP_SH_COST |
234-245 |
9(8)V9(4) |
Not currently implemented. |
DCMP_SH_COST_SIGN |
246 |
X(1) |
Not currently implemented. |
DCMP_SH_REVENUE |
247-258 |
9(8)V9(4) |
Not currently implemented. |
DCMP_SH_REVENUE_SIGN |
259 |
X(1) |
Not currently implemented. |
DCMP_SHIP_METHOD |
260-263 |
X(4) |
Not currently implemented. |
DCMP_PAY_METHOD |
264-265 |
X(2) |
Not currently implemented. |
DCMP_PARENT_SKU |
266-285 |
X(20) |
The set master item defined for the component item contains the same set sequence number as the component, but the set master item flag is Y. • If this is a non-SKUed item, from the Item number field in the Order Detail file. • If this is a SKUed item, from the Item number and SKU code fields in the Order Detail file, with a space between the item and each SKU code. Note: The system truncates this field to 20 positions. |
DCMP_PARENT_LINE_# |
286-291 |
9(6) |
The order line sequence number of the set master item defined for this component item. From the Sequence # field in the Order Detail file. |
The system populates the Cancellations file with order line history information from CWDirect. The system selects order line history information based on:
• passed company.
• passed transaction date range.
• activity code (C = canceled, O = sold out).
One cancellation interface record is created for each order line history record selected.
Field |
Position |
Format |
Description |
CNCL_REC_TYPE |
1-4 |
X(4) |
Set to CNCL. |
CNCL_SEQUENCE |
5-10 |
9(6) |
A unique number assigned to each record. |
CNCL_COMPANY_ID |
11-12 |
X(2) |
The last 2 positions of the CWDirect company code. From the Company field in the Order Line History file. |
CNCL_DIVISION_ID |
13-14 |
X(2) |
The division code for the source code defined for the order line or order header. From the Division field in the Source file. |
CNCL_ORDER_NUM |
15-29 |
X(15) |
The order number and ship to number for the order line, separated by a hyphen. Example: 99999999-999. From the Order # and Ship to # fields in the Order Line History file. |
CNCL_ORDER_LINE |
30-35 |
9(6) |
The order line number for the canceled item. From the Line # field in the Order Detail file. |
CNCL_OFFER_ID |
36-45 |
X(10) |
The offer on the order line. From the Offer field in the Order Detail file. |
CNCL_OFFER_YEAR |
46-49 |
9(4) |
The accounting period year in which the offer start date falls. From the Accounting period year field in the Accounting Period file. |
CNCL_KEY_CODE |
50-69 |
X(20) |
The source code on the order line; otherwise, the source code on the order header. From the Source code field in the Order Detail file or Order Header file. |
CNCL_TRANS_DATE |
70-77 |
9(8) |
The cancel transaction date, in MMDDYYYY format. From the Date field in the Order Line History file. |
CNCL_SKU |
78-97 |
X(20) |
The item number and SKU code of the cancelled item. • If this item is a non-SKUed item, from the Item number field in the Order Detail file. • If this item is a SKUed item, from the Item number and SKU code fields in the Order Detail file, with a space between the item and each SKU code. Note: The system truncates this field to 20 positions. |
CNCL_PRODUCT |
98-117 |
X(20) |
The item number cancelled. From the Item number field in the Order Detail file. |
CNCL_DESCRIPTOR1 |
118-127 |
X(10) |
The second SKU of the cancelled item. From positions 6-9 of the SKU Code field in the Order Detail file. NONE defaults if the item is a non-SKUed item or does not contain split SKUs (the Split SKU Inventory (A26) system control value is set to N). |
CNCL_DESCRIPTOR2 |
128-137 |
X(10) |
The first SKU of the cancelled item. From positions 1-4 of the SKU Code field in the Order Detail file. NONE defaults if the item is a non-SKUed item or does not contain split SKUs (the Split SKU Inventory (A26) system control value is set to N). |
CNCL_DESCRIPTOR3 |
138-147 |
X(10) |
The third SKU of the cancelled item. From positions 11-14 of the SKU Code field in the Order Detail file. NONE defaults if the item is a non-SKUed item or does not contain split SKUs (the Split SKU Inventory (A26) system control value is set to N). |
CNCL_CUST_SOLD |
148-163 |
X(16) |
The sold to customer number on the order header. From the Customer # field in the Order Header file. |
CNCL_CUST_SHIP |
164-179 |
X(16) |
The ship to customer on the order. If a ship to customer is not defined, the sold to customer number defaults. From the Customer # field in the Order Ship To file or Order Header file. |
CNCL_QUANTITY |
180-187 |
9(8) |
The quantity cancelled. From the Quantity field in the Order Line History file. |
CNCL_QTY_SIGN |
188=188 |
X(1) |
Set to +. |
CNCL_EXT_PRICE |
189-198 |
9(8)V9(2) |
The extended price of the cancelled item. Calculated field: order line history quantity x order detail price = extended price |
CNCL_EXT_PRICE_SIGN |
199-199 |
X(1) |
Set to +. |
CNCL_CANCEL_CODE |
200-203 |
X(4) |
• CICU displays to represent a cancel quantity. • CICO displays to represent a sold out quantity. |
The system populates the Backorders file with order detail information from CWDirect. The system selects order detail information based on:
• passed company.
• the order detail line date falls within the passed transaction date range.
• the order detail status is open or held.
• the backorder reason is U, I, N, or O.
• the quantity ordered is greater than quantity reserved + quantity shipped + quantity cancelled.
The system creates one backorder interface record for each order detail selected.
Field |
Position |
Format |
Description |
BACK_REC_TYPE |
1-4 |
X(4) |
Set to BACK. |
BACK_SEQUENCE |
5-10 |
9(6) |
A unique number assigned to each record in the file. |
BACK_COMPANY_ID |
11-12 |
X(2) |
The last 2 positions of the CWDirect company code. From the Company field in the Order Detail file. |
BACK_DIVISION_ID |
13-14 |
X(2) |
The division code for the source code defined for the order line or order header. From the Division field in the Source file. |
BACK_ORDER_NUM |
15-29 |
X(15) |
The order number and ship to number for the order line, separated by a hyphen. Example: 99999999-999. From the Order # and Order ship to # fields in the Order Detail file. |
BACK_ORDER_LINE |
30-35 |
9(6) |
The order detail line number for the backordered item. From the Line # field in the Order Detail file. |
BACK_OFFER_ID |
36-45 |
X(10) |
The offer on the order line. From the Offer field in the Order Detail file. |
BACK_OFFER_YEAR |
46-49 |
9(4) |
The accounting period year in which the offer start date falls. From the Accounting period year in the Accounting Period file. |
BACK_KEY_CODE |
50-69 |
X(20) |
The source code associated with the item on backorder. From the Source code field in the Order Detail file or Order Header file. |
BACK_TRANS_DATE |
70-77 |
9(8) |
The backorder transaction date, in MMDDYYYY format. From the Entered date field in the Order Detail file. |
BACK_SKU |
78-97 |
X(20) |
The item number and SKU code on backorder. • If this item is a non-SKUed item, from the Item number field in the Order Detail file. • If this item is a SKUed item, from the Item number and SKU code fields in the Order Detail file, with a space between the item and each SKU code. Note: The system truncates this field to 20 positions. |
BACK_PRODUCT |
98-117 |
X(20) |
The item number on backorder. From the Item number field in the Order Detail file. |
BACK_DESCRIPTOR1 |
118-127 |
X(10) |
The second SKU of the item on backorder. From positions 6-9 of the SKU code field in the Order Detail file. NONE defaults if the item is a non-SKUed item or does not contain split SKUs (the Split SKU Inventory (A26) system control value is set to N). |
BACK_DESCRIPTOR2 |
128-137 |
X(10) |
The first SKU of the item on backorder. From positions 1-4 of the SKU code field in the Order Detail file. NONE defaults if the item is a non-SKUed item or does not contain split SKUs (the Split SKU Inventory (A26) system control value is set to N). |
BACK_DESCRIPTOR3 |
138-147 |
X(10) |
The third SKU of the item on backorder. From positions 11-14 of the SKU code field in the Order Detail file. NONE defaults if the item is a non-SKUed item or does not contain split SKUs (the Split SKU Inventory (A26) system control value is set to N). |
BACK_CUST_SOLD |
148-163 |
X(16) |
The sold to customer on the order. From the Customer # from the Order Header file. |
BACK_CUST_BACK |
164-179 |
X(16) |
The ship to customer number on the order. If a ship to customer is not defined, the sold to customer number defaults. From the Customer # field in the Order Ship To file or Customer # field in the Order Header file. |
BACK_QUANTITY |
180-187 |
9(8) |
The quantity on backorder. Calculated field: quantity ordered - (quantity reserved + quantity shipped + quantity canceled) = backorder quantity |
BACK_QTY_SIGN |
188-188 |
X(1) |
Set to +. |
BACK_EXT_PRICE |
189-198 |
9(8)V9(2) |
The extended price of the item on backorder. Calculated field: quantity backordered x price = extended price |
BACK_EXT_PRICE_SIGN |
199-199 |
X(1) |
Set to +. |
The system populates the Shipments file with order line history information from CWDirect. The system selects order line history information based on:
• the passed company.
• the passed transaction date range.
• the activity code (S = shipment, B = express billed)
The system creates one shipment interface record for each order line history record selected.
Field |
Position |
Format |
Description |
SHIP_REC_TYPE |
1-4 |
X(4) |
Set to SHIP. |
SHIP_SEQUENCE |
5-10 |
9(6) |
A unique number assigned to each record in the file. |
SHIP_COMPANY_ID |
11-12 |
X(2) |
The last 2 positions of the CWDirect company code. From the Company field in the Order Line History file. |
SHIP_DIVISION_ID |
13-14 |
X(2) |
The division code for the source code defined for the order line or order header. From the Division field in the Source file. |
SHIP_ORDER_NUM |
15-29 |
X(15) |
The Order # and Ship to # from the Order Line History file separated by a hyphen. Example: 99999999-999 |
SHIP_ORDER_LINE |
30-35 |
9(6) |
The order detail line number. From the Line # field in the Order Detail file. |
SHIP_OFFER_ID |
36-45 |
X(10) |
The Offer field from the Order Detail file. |
SHIP_OFFER_YEAR |
46-49 |
9(4) |
The Accounting period year from the Accounting Period file. The system uses the accounting period year in which the offer start date falls. |
SHIP_KEY_CODE |
50-69 |
X(20) |
• The Source code defined at the order detail line. • If a source code has not been defined at the order detail line, the Source code defined at the order header displays. |
SHIP_TRANS_DATE |
70-77 |
9(8) |
The Date from the Order Line History file in MMDDYYYY format. |
SHIP_SKU |
78-97 |
X(20) |
• If this item is a non-SKUed item, from the Item number field in the Order Detail file. • If this item is a SKUed item, from the Item number and SKU code fields in the Order Detail file, with a space between the item and each SKU code. Note: The system truncates this field to 20 positions. |
SHIP_PRODUCT |
98-117 |
X(20) |
The Item number from the Order Detail file. |
SHIP_DESCRIPTOR1 |
118-127 |
X(10) |
The second SKU of the item shipped. From positions 6-9 of the SKU code field in the Order Detail file. NONE defaults if the item is a non-SKUed item or does not contain split SKUs (the Split SKU Inventory (A26) system control value is set to N). |
SHIP_DESCRIPTOR2 |
128-137 |
X(10) |
The first SKU of the item shipped. From positions 1-4 of the SKU code field in the Order Detail file. NONE defaults if the item is a non-SKUed item or does not contain split SKUs (the Split SKU Inventory (A26) system control value is set to N). |
SHIP_DESCRIPTOR3 |
138-147 |
X(10) |
The third SKU of the item on backorder. From positions 11-14 of the SKU code field in the Order Detail file. NONE defaults if the item is a non-SKUed item or does not contain split SKUs (the Split SKU Inventory (A26) system control value is set to N). |
SHIP_CUST_SOLD |
148-163 |
X(16) |
The Customer # from the Order Header file. |
SHIP_CUST_SHIP |
164-179 |
X(16) |
The ship to customer on the order; if a ship to customer is not defined, the sold to customer defaults. From the Customer # field in the Order Ship To file or Order Header file. |
SHIP_QUANTITY |
180-187 |
9(8) |
The quantity shipped. From the Quantity field in the Order Line History file. |
SHIP_QTY_SIGN |
188-188 |
X(1) |
Set to +. |
SHIP_EXT_PRICE |
189-198 |
9(8)V9(2) |
Calculated field: order line history quantity x order detail price = extended ship price. |
SHIP_EXT_PRICE_SIGN |
199-199 |
X(1) |
Set to +. |
SHIP_EXTENDED_COST |
200-209 |
9(8)V9(2) |
Calculated field: order line history quantity x average, standard, or FIFO cost = ship extended cost Use the cost override on the order detail line if it is greater than zero. The cost is based on the value defined in the Costing Method (A25) system control value. |
SHIP_EXT_COST_SIGN |
210-210 |
X(1) |
Set to +. |
SHIP_CODE |
211-214 |
X(4) |
SHBO defaults if the Backorder reason from the Order Detail file is U, I, N, or O; otherwise, SHIM defaults. |
SHIP_SH_COST |
215-226 |
9(8)V9(4) |
.0000 |
SHIP_SH_COST_SIGN |
227-227 |
X(1) |
Blank |
SHIP_SH_REVENUE |
228-239 |
9(8)V9(4) |
.0000 |
SHIP_SH_REVENUE_SIGN |
240-240 |
X(1) |
Blank |
The system populated the Returns file with order line history information from CWDirect. The system selects order line history information based on:
• the passed company.
• the passed transaction date range.
• the activity code (R = returned, E = exchanged).
The system creates one returns interface record for each order line history record selected.
Field |
Position |
Format |
Description |
RETN_REC_TYPE |
1-4 |
X(4) |
Set to RETN. |
RETN_REC_ACTION |
5-5 |
X(1) |
Set to A. |
RETN_SEQUENCE |
6-11 |
9(6) |
A unique number assigned to each record in the file. |
RETN_COMPANY_ID |
12-13 |
X(2) |
The last 2 positions of the CWDirect company code. From the Company field in the Order Line History file. |
RETN_DIVISION_ID |
14-15 |
X(2) |
The division code for the source code defined for the order line or order header. From the Division field in the Source file. |
RETN_ORDER_NUM |
16-30 |
X(15) |
The order number and ship to number, separated by a hyphen. Example: 99999999-999 From the Order # and Ship to # fields in the Order Detail file. |
RETN_ORDER_LINE |
31-36 |
9(6) |
The order detail line number for the returned item. From the Line # field in the Order Detail file. |
RETN_OFFER_ID |
37-46 |
X(10) |
The offer on the order line. From the Offer field in the Order Detail file. |
RETN_OFFER_YEAR |
47-50 |
9(4) |
The Accounting period year from the Accounting Period file. The system uses the accounting period year in which the offer start date falls. |
RETN_KEY_CODE |
51-70 |
X(20) |
• The Source code defined on the order detail line. • If a source code is not defined at the order detail line, the Source code at the order header defaults. From the Source code field in the Order Detail file or Order Header file. |
RETN_TRANS_DATE |
71-78 |
9(8) |
The date the item was returned, in MMDDYYYY format. From the Date field in the Order Line History file. |
RETN_SKU |
79-98 |
X(20) |
• If this item is a non-SKUed item, the Item number from the Order Detail file displays. • If this item is a SKUed item, the Item number and SKU code from the Order Detail file displays with a space between the item and each SKU code. Note: The system truncates this field to 20 positions. |
RETN_PRODUCT |
99-118 |
X(20) |
The Item number from the Order Detail file. |
RETN_DESCRIPTOR1 |
119-128 |
X(10) |
The second SKU of the item shipped. From positions 6-9 of the SKU code field in the Order Detail file. NONE defaults if the item is a non-SKUed item or does not contain split SKUs (the Split SKU Inventory (A26) system control value is set to N). |
RETN_DESCRIPTOR2 |
129-138 |
X(10) |
The first SKU of the item shipped. From positions 1-4 of the SKU code field in the Order Detail file. NONE defaults if the item is a non-SKUed item or does not contain split SKUs (the Split SKU Inventory (A26) system control value is set to N). |
RETN_DESCRIPTOR3 |
139-148 |
X(10) |
The third SKU of the item shipped. From positions 11-14 of the SKU code field in the Order Detail file. NONE defaults if the item is a non-SKUed item or does not contain split SKUs (the Split SKU Inventory (A26) system control value is set to N). |
RETN_CUST_SOLD |
149-164 |
X(16) |
The sold to customer on the order. From the Customer # field in the Order Header file. |
RETN_CUST_SHIP |
165-180 |
X(16) |
The ship to customer on the order. If a ship to customer is not defined, the sold to customer defaults. From the Customer # field in the Order Ship To file or Order Header file. |
RETN_QUANTITY |
181-188 |
9(8) |
The returned quantity. From the Quantity field in the Order Line History file. |
RETN_QTY_SIGN |
189-189 |
X(1) |
Set to +. |
RETN_EXT_PRICE |
190-199 |
9(8)V9(2) |
The extended price of the returned item. Calculated field: order line history quantity x order detail price = return extended price |
RETN_EXT_PRICE_SIGN |
200-200 |
X(1) |
Set to +. |
RETN_EXTENDED_COST |
201-210 |
9(8)V9(2) |
The extended cost of the returned item. Calculated field: order line history quantity x average, standard, or FIFO cost = return extended cost Use the cost override on the order detail line if it is greater than zero. The cost is based on the value defined in the Costing Method (A25) system control value. |
RETN_EXT_COST_SIGN |
211-211 |
X(1) |
Set to +. |
RETN_RESELL_QTY |
212-219 |
9(8) |
If the activity code is R, the system checks the Defective flag and Return to vendor flag on the return reason code. • If the Defective flag or Return to vendor flag is Y, the resell quantity is 0. • If both Defective flag and Return to vendor flag are N, the resell quantity is the order line history quantity. If the activity code is E, the system checks the Defective flag and Return to vendor flag on the exchange reason code. • If the Defective flag or Return to vendor flag is Y, the resell quantity is 0. • If both Defective flag and Return to vendor flag are N, the resell quantity is the order line history quantity. |
RETN_RETURN_CODE |
220-223 |
X(4) |
• If the activity code is R, the system uses the Return reason code from the Order Line History file. • If the activity code is E, the system uses the Exchange reason code from the Order Line History file. |
RETN_ACTION |
224-227 |
X(4) |
Valid values: • RFND = the activity code is R. • EXCH = the activity code is E. |
RETN_SH_COST |
228-239 |
9(8)V9(4) |
.0000 |
RETN_SH_COST_SIGN |
240-240 |
X(1) |
Blank |
RETN_SH_REVENUE |
241-252 |
9(8)V9(4) |
.0000 |
RETN_SH_REVENUE_SIGN |
253-253 |
X(1) |
Blank |
Note: The following fields are not currently available in the CWDirect Forecast*21 integration. |
|||
RETN_ALT_TRACKING_ID |
254-267 |
X(15) |
Not currently implemented. |
RETN_ALT_TRACKING_ORD_LINE |
268-273 |
9(6) |
Not currently implemented. |
RETN_SALES_TAX_REFUND |
274-285 |
9(8)V9(4) |
Not currently implemented. |
RETN_RESTOCK_CHARGE |
286-297 |
9(8)V9(4) |
Not currently implemented. |
RETN_PAY_METHOD |
298-299 |
X(2) |
Not currently implemented. |
RETN_TOTAL_CREDIT |
300-311 |
9(8)V9(4) |
Not currently implemented. |
RETN_TOTAL_CREDIT_SIGN |
312-312 |
X(1) |
Not currently implemented. |
RETN_SALESPERSON |
313-322 |
X(10) |
Not currently implemented. |
RETN_RETURN_TYPE |
323-323 |
X(1) |
Not currently implemented. |
When you generate the Stock Position Interface, the system populates:
• Audit Record File (F21AUD): indicates the number of records included in the Stock Position Interface.
• Inventory Position File (F21IVP): lists SKUs currently in inventory.
• On Order File (F210NO):details all purchase orders which have been placed but have not yet arrived.
• On Backorder File (F210BO): lists SKUs currently on backorder.
Once the extract files for the Stock Position Interface have been populated, the system copies the files into a file named POS.XFR.
The first record in each interface file is an audit record that contains the following information.
Field |
Type |
Position |
Format |
Description |
Sequential file number |
Number |
1-6 |
9(6) |
The sequential file number from the order transaction audit record. If the order transaction audit record does not exist or its date created does not match the stock position file’s date created, the next available number from the number assignment file is used. |
Date created |
Number |
7-14 |
YYYYMMDD |
Current date |
Time created (military) |
Number |
15-18 |
HHMM |
Current time |
Number of records |
Number |
19-26 |
9(8) |
Total number of records in the POS.XFR file (including the audit record). |
Interface version used |
Number |
37-41 |
9(5) |
00271 |
Inventory Position File (F21IVP)
The system populates the Inventory Position file with item warehouse information from CWDirect. The system selects item warehouse information based on:
• the passed company.
• whether the warehouse is allocatable.
Inventory position interface records summarize item warehouse records by:
• company
• item number
• SKU
Field |
Position |
Format |
Description |
INVP_REC_TYPE |
1-4 |
X(4) |
Set to INVP. |
INVP_SEQUENCE |
5-10 |
9(60 |
A unique number assigned to each record. |
INVP_COMPANY_ID |
11-12 |
X(2) |
The last 2 positions of the CWDirect company code. From the Company field in the Item Warehouse file. |
INVP_SKU |
13-32 |
X(20) |
• If this item is a non-SKUed item, the Item number from the Item Warehouse file displays. • If this item is a SKUed item, the Item number and SKU code from the Item Warehouse file displays with a space between the item and each SKU code. Note: The system truncates this field to 20 positions. |
INVP_STATUS |
33-36 |
X(4) |
AVAL (stock is available for new orders). |
INVP_QUANTITY |
37-44 |
9(8) |
Calculated field: on hand - (reserved + backordered + protected from the Item Warehouse file) = available stock If the quantity available is less than zero, 0 displays. |
The system populates the On Order file with purchase order detail information from CWDirect. The system selects on order information based on:
• the passed company.
• the PO detail is in an open status.
On-order interface records are at the PO detail level.
Field |
Position |
Format |
Description |
ONOR_REC_TYPE |
1-4 |
X(4) |
Set to ONOR. |
ONOR_SEQUENCE |
5-10 |
9(6) |
A unique number assigned to each record in the file. |
ONOR_COMPANY_ID |
11-12 |
X(2) |
The last 2 positions of the CWDirect company code from the Company in the PO Detail file. |
ONOR_SKU |
13-32 |
X(20) |
• If this item is a non-SKU’ed item, the Item number from the PO Detail file displays. • If this item is a SKU’ed item, the Item number and SKU code from the PO Detail file displays with a space between the item and each SKU code. Note: The system truncates this field to 20 positions. |
ONOR_PO_NUM |
33-52 |
X(20) |
The purchase order number. From the PO # field in the PO Detail file. |
ONOR_PO_LINE |
53-57 |
9(5) |
The purchase order line number. From the Line # field in the PO Detail file. |
ONOR_ORDER_DATE |
58-65 |
9(8) |
The purchase order date in MMDDYYYY format. From the Entered date field in the PO Header file. |
ONOR_VENDOR_ID |
66-75 |
X(10) |
The vendor code on the purchase order. From the Vendor number field in the PO Header file. |
ONOR_QUANTITY |
76-83 |
9(8) |
The quantity ordered. Calculated field: PO detail order quantity - PO detail received quantity = on order quantity |
ONOR_ORIG_EXCEPT_ RCPT_DATE |
84-91 |
9(8) |
The expected receipt date in MMDDYYYY format. From the Due date field in the PO Detail file. |
ONOR_REVISED_EXP_RCPT_DATE |
92-99 |
9(8) |
The revised expected receipt date in MMDDYYYY format. From the Due date field the PO Detail file. |
ONOR_COST_EA |
100-109 |
9(6)V9(4) |
The cost per unit of the item. From the Price field in the PO Detail file. |
ONOR_TOTAL_COST |
110-121 |
9(10)V9(2) |
The total cost of the PO line. Calculated field: PO detail open quantity x PO detail price = on order total cost |
ONOR_REQ_NUMBER |
122-129 |
9(8) |
0 |
The system populates the On Backorder file with order detail information from CWDirect. The system selects order detail information based on:
• the passed company.
• the order detail status is open or held.
• the backorder reason is U, I, N, or O.
• the quantity ordered is greater than quantity reserved + quantity shipped + quantity canceled.
Backorder interface records summarize order detail records by:
• company
• entered date
• item number
• SKU
Field |
Position |
Format |
Description |
BO_REC_TYPE |
1-4 |
X(4) |
Set to BO. |
BO_SEQUENCE |
5-10 |
9(6) |
A unique sequence number assigned to each record. |
BO_COMPANY_ID |
11-12 |
X(2) |
The last 2 positions of the CWDirect company code. From the Company field in the Order Detail file. |
BO_SKU |
13-32 |
X(20) |
• If this item is a non-SKUed item, the Item number from the Order Detail file displays. • If this item is a SKU’ed item, the Item number and SKU code displays with a space between the item and each SKU code. Note: The system truncates this field to 20 positions. |
BO_DATE |
33-40 |
9(8) |
The Entered date from the Order Detail file in MMDDYYYY format. |
BO_QUANTITY |
41-48 |
9(8) |
The quantity on backorder. Calculated field: quantity ordered - (quantity reserved + quantity shipped + quantity canceled) = quantity backordered |
When you generate the Key Code Interface, the system populates the Key Code extract file, which lists source codes for an offer.
Once the Key Code extract file for the Key Code Interface has been populated, the system copies the file into a file named KEYC.XFR.
The first record in the interface file is an audit record that contains the following information.
Field |
Type |
Position |
Format |
Description |
Sequential file number |
Number |
1-6 |
9(6) |
From the number assignment file. |
Date created |
Number |
7-14 |
YYYYMMDD |
Current date |
Time created (military) |
Number |
15-18 |
HHMM |
Current time |
Number of records |
Number |
19-26 |
9(8) |
Total number of records in the KEYC.XFR file (including the audit record). |
Interface version used |
Number |
37-41 |
9(5) |
00271 |
The system populates the Key Code file with source code information from CWDirect. The system selects source code information based on passed company.
Field |
Position |
Format |
Description |
KEYC_REC_TYPE |
1-4 |
X(4) |
Set to KEYC. |
KEYC_SEQUENCE |
5-10 |
9(6) |
The system uses the value defined in the Forecast21 Key Code Sequence Number number assignment value to determine the next available sequence number. |
KEYC_COMPANY_ID |
11-12 |
X(2) |
The last 2 positions of the CWDirect company code. From the Company field in the Source file. |
KEYC_KEY_CODE |
13-32 |
X(20) |
The source code. From the Source code field in the Source file. |
KEYC_DESCRIPTION |
33-82 |
X(50) |
A description of the source code. From the Description field in the Source file. |
KEYC_DIVISION_ID |
83-84 |
X(2) |
The division code associated with the source code. From the Division field in the Source file. |
KEYC_OFFER_ID |
85-94 |
X(10) |
The offer code associated with the source code. From the Offer # field in the Source file. |
KEYC_OFFER_YEAR |
95-98 |
9(4) |
The Accounting period year from the Accounting Period file. The system uses the accounting period year in which the offer start date falls. |
Note: The following fields are not currently available in the CWDirect Forecast*21 integration. |
|||
KEYC_COST |
99-110 |
9(8)V9(4) |
Not currently implemented. |
KEYC_MAIL_DATE |
111-118 |
9(8) |
Not currently implemented. |
KEYC_CIRCULATION |
119-127 |
X(9) |
Not currently implemented. |
KEYC_CROSS_REF |
128-147 |
X(20) |
Not currently implemented. |
KEYC_CHANGE_FLAG |
148-148 |
X(1) |
Not currently implemented. |
Chapter 31: Forerunner IF/SO Interface (EFOR, DFOR) | Contents | SCVs | Search | Glossary | Reports | XML | Index | Chapter 33: Initializing the IS Report (IISR) |
MK03_10 CWDirect 18.0 August 2015 OTN