Working with Catalog Requests | Contents | SCVs | Search | Glossary | Reports | Solutions | XML | Index | Processing Catalog Requests (PCAT) |
Entering Catalog Requests (WCAT)
Purpose: Use catalog requests to capture inquiries and manage requests for catalogs from new or existing customers. Creating catalog requests lets you track inquiry information, report on trends with respect to requests for specific catalogs, and quickly print labels in response to those requests.
You use the Work with Catalog Requests Screen when you want to create, change, delete, or display individual catalog requests or when you want to display or print a list of catalog customers whose names are still in the Catalog Request table.
Note: You can also receive catalog requests through the catalog request interface. See Working with the Catalog Request Interface (WCRU).
Catalog request history: The system tracks the total number of catalog requests by source code and date in the Catalog Request History table. This information is available for reporting purposes, such as on the Campaign Performance Report; see Print Campaign Performance Reports (PCPR) for more information. See Catalog Request History Options for additional menu options related to the Catalog Request History table.
Relate customer integration: When you use the Relate customer integration, if you create a customer through a catalog request, CWSerenade sends the customer information to Relate so that the customer records in the two systems are synchronized. See the Relate Customer Integration for more information.
The EC_CAT_REQ job, started through Working with E-Commerce Job Control (EJCT) creates catalog requests through the e-commerce interface.
• If the E-Commerce Catalog Request Message (CWCatRequest) passes validation, a catalog request record is created. You can review and change the catalog request at the Work with Catalog Requests Screen.
• If the E-Commerce Catalog Request Message (CWCatRequest) does not pass validation, a catalog request interface record is created. You can review and correct the catalog request through Working with the Catalog Request Interface (WCRU).
Catalog request response: You can also send an E-Commerce Catalog Request Response Message (CWCatreqResponse) to the web storefront. The catalog request response message indicates the customer number and optionally, individual number, used to create the catalog request. If the customer number in the catalog request response message is blank, the catalog request did not process correctly and needs to be corrected through Working with the Catalog Request Interface (WCRU). Note: The e-commerce customer updates response message is available for XML messages only, not name/value pair messages.
The response_required field in the catalog request message indicates if a catalog request response message is sent to the web storefront.
• 0, blank, or a value other than 1 indicates a catalog request response message is not sent to the web storefront.
• 1 indicates a catalog request response message is sent to the web storefront.
Customer updates: Additionally, if the customer associated with the catalog request does not exist, the system will create a new customer; see Customer Creation/Update Logic in E-Commerce Catalog Requests. In this case, it is useful to send a catalog request response message to the web storefront indicating the newly assigned customer number.
Relate customer integration: When you use the Relate customer integration, if you create a customer through an e-commerce catalog request, CWSerenade sends the customer information to Relate so that the customer records in the two systems are synchronized. See the Relate Customer Integration for more information.
See E-Commerce Catalog Requests for additional processing information.
In this topic:
• Work with Catalog Requests Screen
• Catalog Request Creation Options
• Create Catalog Request Screen
• Select Customer for Catalog Request Screen
• Change Catalog Request Screen
• Ghost Customer Warning Window
Work with Catalog Requests Screen
How to display this screen: Enter WCAT in the Fast path field at the top of any menu or select Work with Catalog Request from a menu.
Field |
Description |
Customer |
A unique number the system assigns to each Sold-to customer on creation of the customer through Order Entry, Customer Maintenance, or catalog requests. Ghost customers: If you enter the customer number of a ghost customer, the scan screen does not display any catalog requests; this is because a merge/purge has assigned any catalog requests using that customer number to the “target” customer. You can identify a ghost customer by the setting of the Ghost flag. Numeric, 9 positions; optional. |
Ofr (Offer) |
Represents the advertising medium that you use to present merchandise to your customers. Your entry is validated against the Offer table. Alphanumeric, 3 positions; optional. |
Source |
A code that identifies a list of customers. The source code drives marketing, forecasting, pricing, and freight information on an order. A source code will appear here only if a source code was entered when the catalog request was created. Alphanumeric, 9 positions; optional. |
Request date |
The date the catalog request was created. Numeric, 6 positions (MMDDYY format); display-only. |
Printed |
A flag that indicates whether you have printed a catalog for the customer. No displays in this field next to a request until the catalog label is printed. Once the catalog label is printed, this value changes to Yes. Records remain on this list, regardless of their printed status, until you delete them selectively, or in batch mode. Values are: • Yes = A catalog label has been printed. • No = A catalog label has not been printed. Optional. |
Screen Option |
Procedure |
Create a catalog request |
Select Create to advance to the Create Catalog Request Screen. |
Change a catalog request |
Select Change for a catalog request to advance to the Change Catalog Request Screen. |
Delete one or more catalog request records |
Select Delete for a catalog request to display a pop-up window containing deletion options. You can delete a request using this method regardless of whether the label has been printed. |
Display catalog request records |
Select Display for a catalog request to advance to the Display Catalog Request Screen. You cannot change any information on this screen. See Change Catalog Request Screen for a sample screen and field descriptions. |
Catalog Request Creation Options
Note: You must have the Enable Catalog Request at Customer Individual Level (H81) system control value selected to enter a catalog request for an individual.
E-commerce catalog requests: If the customer associated with an e-commerce catalog request does not exist, the system will create a new customer; see Customer Creation/Update Logic in E-Commerce Catalog Requests.
Ghost customers: If you enter the customer number of a ghost customer, the system displays the Ghost Customer Warning Window.
Purpose: Use this screen to create a catalog request for a new or existing customer.
How to display this screen: At the Work with Catalog Requests Screen, select Create.
Note: You can also display this screen by selecting Catalog Request from the Select Customer Sold To For Order Screen or at the Customer Selection Screen in Order Entry.
Note: If you are creating a catalog request for an existing customer, do not complete the following fields; instead, select Select Customer to select an existing customer, then complete the Offer, Item, Source, and # of copies fields. See Catalog Request Creation Options for an overview.
Ghost customers: If you enter the customer number of a ghost customer, the system displays the Ghost Customer Warning Window.
Field |
Description |
Indiv name |
The following five fields can hold the individual’s full name: Prefix A title that belongs before the individual’s name (such as "Mrs." or "Dr."). The prefix will print on labels. If the Validate Prefix (I27) system control value is selected, your entry is validated against the Prefix table; see Working with Prefix Codes (WPFX). However, only the three-position prefix code prints on catalog request labels. Alphanumeric, 3 positions; optional if you are creating a new individual, or display-only if you select an existing individual. First Name The individual’s first name. Alphanumeric, 15 positions; optional if you are creating a new individual, or display-only if you select an existing individual. Initial The initial of the individual’s middle name. Alphanumeric, 1 position; optional if you are creating a new individual, or display-only if you select an existing individual. Last Name The individual’s last name. Alphanumeric, 25 positions; optional if you are creating a new individual, or display-only if you select an existing individual. Suffix An addition to the individual’s full name (such as "M.D.," "Fr.," or "III"). Alphanumeric, 3 positions, optional if you are creating a new individual, or display-only if you select an existing individual. |
|
Note: • These fields are displayed if you select Individual or Select Individual to enter individual information. You must have the Enable Catalog Request at Customer Individual Level (H81) system control value selected. • The individual’s name will print on the catalog request label only if the Label 3-Up Printing Program (C84) or the Label 3-Up Printing Program (C84) system control values specify unique programs that support printing the individual information. |
Name |
The following five fields can hold the sold-to customer's full name: Prefix A title that belongs before the customer's name (such as "Mrs." or "Dr."). The prefix will print on labels. If the Validate Prefix (I27) system control value is selected, your entry is validated against the Prefix table; see Working with Prefix Codes (WPFX). However, only the three-position prefix code prints on catalog request labels. Alphanumeric, 3 positions; optional if you are creating a new customer, or display-only if you select an existing customer. First Name The customer's first name. Alphanumeric, 15 positions; optional if you are creating a new customer, or display-only if you select an existing customer. Initial The initial of the customer's middle name. Alphanumeric, 1 position; optional if you are creating a new customer, or display-only if you select an existing customer. Last Name The customer's last name. Alphanumeric, 25 positions; required if company name is not present and you are creating a new customer, or display-only if you select an existing customer. Suffix An addition to the customer's full name (such as "M.D.," "Fr.," or "III"). Alphanumeric, 3 positions, optional if you are creating a new customer, or display-only if you select an existing customer. |
Company |
The name of the company to which the catalog should be mailed, if applicable. Alphanumeric, 30 positions; required if last name is not present and you are creating a new customer, or display-only if you select an existing customer. |
M/F (Male/Female code) |
A code that identifies the customer's gender. The system may default a value to this field based on the Default Male/Female Profile Code (C74) system control value. If you have set this field, the system references the Demographic Profiles table, searches for the default profile option (such as FEMALE or MALE), and loads an F or M to the M/F field on the Create Catalog Request screen. You can, however, override or remove this value. Alphanumeric, 1 position; optional. |
This flag indicates whether the customer wants to receive future catalog mailings from your company. Not to be confused with the Mail code, a three-position, alphanumeric field. Valid values are: • selected = You can mail catalogs to this customer. • unselected = You can not mail catalogs to this customer. May default from the Default Mail Name (D10) system control value, but you can override it. Entity-level override If the Track Customer History at Entity Level (F89) system control value is selected, you can prompt on this field and set the mail flag for each entity within your company. Setting the mail flag for an entity also creates a customer entity record, using a current and original mail type of C, for catalog request. See First Create Sold To Customer Screen. Update to individual Your entry in this field also updates the Mail flag for the individual when you create a new individual through the catalog request; however, it does not update an existing individual on a catalog request. |
|
Rent |
Indicates whether you can sell this customer's name to another company for their catalog mailings. Valid values are: • selected = You can sell this customer's name. • unselected = You can not sell this customer's name. May default from the Default Rent Name (D11) system control value, but you can override it. Update to individual Your entry in this field also updates the Rent flag for the individual when you create a new individual through the catalog request; however, it does not update an existing individual on a catalog request. |
Address |
The customer's street address. This is the primary delivery address. Shipping to a Post Office Box To ship to a Post Office Box, enter POST OFFICE BOX, POST BOX, or any variation of PO BOX (with or without spaces or non-alphabet characters, such as P.O. BOX), and the box number in the customer’s street address. During order processing, the system validates that the carrier can ship to a post office box (as defined in the Ship Via table). Example: Enter P.O. Box 9999 in the Street field to indicate delivery to a post office box instead of a home or company address. Note: If you type POST OFFICE BOX, POST BOX, or any variation of PO BOX in the customer’s street address during order entry or through the Order API, the system automatically selects the PO box field for the customer. However, if you remove this text from the customer’s street address, the system does not automatically unselect the PO box flag. Note: When you create a customer outside of order processing, you need to select the PO box field manually. Alphanumeric, 32 positions; required if you are creating a new customer, or display-only if you select an existing customer. |
Apt./suite |
The apartment number or suite number of the delivery address. To enter an apartment or suite address: 1.Enter APT to indicate an apartment or STE to indicate a suite. 2.Insert a space and enter the number of the apartment or suite (for example, APT 4 or STE 116). Field contents must conform to United States Parcel Service (USPS) address formatting Field Description standards. Always precede the apartment or suite number with the applicable abbreviation (such as APT or STE), to meet USPS regulations and correctly identify this information on labels or reports. Alphanumeric, 10 positions; optional if you are creating a new customer, or display-only if you select an existing customer. |
Address lines 2-4 (Unlabeled fields directly beneath the street address) |
Additional entry fields for the customer's address. The contents of address line 2 of the address must conform to United States Postal Service (USPS) formatting standards. For example, if the address represents a post office box, you must enter P.O. Box on this line to meet USPS regulations and correctly identify this information on labels. Alphanumeric, 30 positions; optional if you are creating a new customer, or display-only if you select an existing customer. |
Position |
This code represents the individual's position within the organization. Position codes are defined in and validated against the Individual Position table; see Working with Individual Positions (WPOS). Note: This field is displayed only if you select Individual to enter individual information or select Select Individual to select an existing individual. You must have the Enable Catalog Request at Customer Individual Level (H81) system control value selected. See Catalog Request Creation Options for an overview. Alphanumeric, 3 positions; required if you are creating a new individual, or display-only if you select an existing individual. |
Department |
This code represents the individual's department within the organization. Department codes are either required, optional, or invalid, depending on how the individual's position code is defined. Department codes are defined in and validated against the Individual Department table; see Working with Individual Departments (WDPM). Note: This field is displayed only if you select Individual to enter individual information or Select Individual to select an existing individual. You must have the Enable Catalog Request at Customer Individual Level (H81) system control value selected. Alphanumeric, 3 positions; may be required, optional, or invalid, depending on the position code selected if you are creating a new individual, or display-only if you select an existing individual. |
Postal code |
The postal or zip code for this customer. The system calls a user-defined program to validate postal code formats outside the CWSerenade environment if you select the External Postal Code Validation (E62) system control value. Required only if the Require postal code? flag is selected for the country. See Setting Up the Country Table (WCTY) for background. If a postal code is required for the country, it is validated against the Zip/City/State (Postal Code) table; see Setting Up the Zip/City/State (Postal Code) Table (WZIP). Scan length: The Postal Code Scan Length (F61) system control value controls how many characters of the postal code to use when searching for a customer. See that system control value for a discussion. Note: If postal codes have been entered into the Postal Code/City/State table, the postal code indicates the City and State to default. If you enter a valid postal code that does not correspond to the city or state you entered, the system changes the city or state information to correspond with the zip code you entered. Numeric, 10 positions; required or optional based on country if you are creating a new customer, or display-only if you select an existing customer. |
City |
The city where the customer lives, or receives mail or shipments. The system will complete this field for you when you enter a valid postal code if the postal code exists in the Postal Code/City/State table. Alphanumeric, 25 positions; required if you are creating a new customer, or display-only if you select an existing customer. |
St (State) |
The state or province where the customer lives, or receives mail or shipments. The system validates that the state you enter is assigned to the SCF in the first three positions of the postal code. State codes are defined in and validated against the State table, which is accessible through the Work with Countries menu option; see Setting Up the Country Table (WCTY). Required only if the Require state? flag is selected for the country. The system completes the state field automatically when you enter a valid postal code if the postal code exists in the Postal Code/City/State table. Alphanumeric, 2 positions; required or optional based on country if you are creating a new customer, or display-only if you select an existing customer. |
Country |
The code for the customer's country. May default from the Default Country for Customer Address (B17) system control value; however, you can override it. Country codes are defined in and validated against the Country table. See Setting Up the Country Table (WCTY). Alphanumeric, 3 positions; required if you are creating a new customer, or display-only if you select an existing customer. |
Delivery code |
This code identifies the address as a business or residential address. This code is used by shippers who charge different rates when shipping to a business or home. Valid values are: • Business • No distinction = Not valid for a UPS shipper • Residential This field may default based on the Default Delivery Code for New Order Entry Customers (D13) system control value, but you can override it. Required. |
Customer class |
A code that categorizes the consumer environment at a high level for reporting purposes. You can use a customer class code to: • direct offerings to a limited customer group • restrict item sales to a group of customers, for example, restricting the sale of guns to minors • set a default for bypassing item reservation for a group of customers • generate a list of customers for reporting purposes, or segment reports by class code |
|
If you enter a new customer class code in this field, the system updates the Customer Sold To table with the code you entered. Required? The Require Customer Class in OE, WCAT, and WCST (H85) system control value defines whether this field is required. Secured? The Maintenance of Customer Class Field (B07) secured feature defines whether you can enter or maintain the customer class field at this screen. Note: If the Require Customer Class in OE, WCAT, and WCST (H85) is selected and the customer does not have a customer class code assigned, a user who does not have authority based on the Maintenance of Customer Class Field (B07) secured feature will not be able to enter a catalog request. See Setting Up the Customer Class Table (WCCL) for information on working with customer classes. Numeric, 2 positions; optional. |
Phone |
The customer's daytime, evening, and fax or mobile telephone numbers. Note: The Third Phone Number Type (L53) system control value determines whether the third phone number is labeled the Fax or Mobile number. Alphanumeric, one 14-position field (phone number) and one 4-position field (phone extension); optional if you are creating a new customer, or display-only if you select an existing customer. |
Ind phn (Individual phone) |
The individual’s daytime, evening, and fax or mobile telephone numbers. Note: The Third Phone Number Type (L53) system control value determines whether the third phone number is labeled the Fax or Mobile number. Note: These fields are displayed only if you select Individual to enter individual information or select Select Individual to select an existing individual. You must have the Enable Catalog Request at Customer Individual Level (H81) system control value selected. See Catalog Request Creation Options for an overview. Alphanumeric, one 14-position field (phone number) and one 4-position field (phone extension); optional if you are creating a new individual, or display-only if you select an existing individual. |
Email address |
The customer's primary email address. This address, along with any other email addresses for the customer, is stored in the Customer Sold To Email table. A plus sign (+) indicates that there are additional email addresses on record for the customer. See Email Address Validation for information on how the system verifies that your entry is formatted correctly. Entering a new email address: If you overwrite the existing email address in this field, the system flags your entry as the primary email address for the customer, but retains the previous email address in the Customer Sold To Email table. In order to delete the previous email address, you need to prompt to display the Select Customer Email Address Screen and delete the previous email address there. See Working with Customer Email Addresses for an overview. Deleting the email address: Similar to entering a new email address, if you delete the email address from this field, the system removes the primary email flag for the address but retains the address in the Customer Sold To Email table. Email notifications: See When Does the System Generate an Email Notification? for an overview. Alphanumeric, 50 positions; optional. |
Opt in |
Determines the preferred method of correspondence for the sold-to customer email address. Valid values are: • O1 (Email) = Email is the preferred method of correspondence. • O2 (Order-only email) = Use email for order-related correspondence only; generate a document for other correspondence. • O3 (No email) = Do not use email for any correspondence; generate a document instead. • O4 (Do not ask the customer) = Do not ask the customer for his/her email address; the customer has already been asked and has declined to provide it. The system does not generate any email correspondence to the customer, even if an email address is specified. Defaults from the Default Opt In/Opt Out Flag (G97) system control value, but you can override it. Note: The above values use the letter O, not the number 0 (zero). The system updates this field when you change the setting of the Opt in/Opt out value at any other screen, such as order entry, order maintenance, or customer maintenance. |
|
Email notifications: See When Does the System Generate an Email Notification? for an overview. Alphanumeric, 2 positions; required. |
Ind email address |
The individual’s email address. See Email Address Validation for information on how the system verifies that your entry is formatted correctly. Note: This field is displayed only if you select Individual to enter individual information or select Select Individual to select an existing individual. You must have the Enable Catalog Request at Customer Individual Level (H81) system control value selected. See Catalog Request Creation Options for an overview. Alphanumeric, 50 positions; optional. |
Ind OptIn (Individual opt in/opt out) |
Indicates the preferred method of correspondence for the individual email address. Valid values are: • All EMail = Email is the preferred method of correspondence. • Order EMail Only = Use email for order-related correspondence only; generate a document for other correspondence. • No EMail = Do not use email for any correspondence; generate a document instead. • Do Not Ask = Do not ask the customer for his/her email address; the customer has already been asked and has declined to provide it. The system does not generate any email correspondence to the customer, even if an email address is specified. If you are creating a catalog request for an existing customer, this value defaults from the Opt in/opt out field for the associated sold-to customer, but you can override it. If you are creating a catalog request for a new customer, this value defaults from the Default Opt In/Opt Out Flag (G97) system control value, but you can override it. Note: The above value uses the letter O, not the number 0 (zero). Note: This field is displayed only if you select Individual to enter individual information or select Select Individual to select an existing individual. You must have the Enable Catalog Request at Customer Individual Level (H81) system control value selected. See Catalog Request Creation Options for an overview. Required. |
Mail stop |
The individual's delivery address within the organization. Note: • This field is displayed only if you select Individual to enter individual information or select Select Individual to select an existing individual. You must have the Enable Catalog Request at Customer Individual Level (H81) system control value selected. • This field will print on the catalog request label only if the Label 2-Up Printing Program (C83) or the Label 3-Up Printing Program (C84) system control values specify unique programs that support printing individual information. Alphanumeric, 32 positions; optional if you are creating a new individual or display-only if you select an existing individual. |
# of copies |
The number of catalogs the customer wants to receive; controls the number of labels printed when you use Processing Catalog Requests (PCAT). For example, if you enter 5 here, the system prints 5 labels for the customer. If you do not have authority to the Allow Number of Copies to Maintain in Catalog Request (A75) secured feature, this field is display-only. Tracking catalog request history: When you print the catalog request label, the system uses the total number of requests rather than the total number of copies when tracking catalog request history in the Source Code table and in the Catalog Request History table. For example, if a customer requests 3 copies of a catalog, the system increases the total by 1, not by 3. You can review the total number of catalog requests for a source code at the Source Code History Screen and on the Campaign Performance Report (PCPR). Numeric, 2 positions; required. |
Source |
A code that identifies a list of names for this catalog mailing. The source code drives marketing, forecasting, pricing, and freight information on an order. Note: You can prompt to view a list of the source codes you can use. Only those source codes set to display in Order Entry and catalog requests appear in the Select Source pop-up window. The first source code you enter on this screen will default for any other catalog requests you create so you can enter them quickly. Once you exit this screen, the Source field will clear. The source code will default in the Source field for alternate address and standard address format. Source codes are defined in and validated against the Source Code table. See Working with Source Codes (WSRC). Alphanumeric, 7 positions; required. |
Offer |
The code for the catalog that the customer is requesting. Offer codes are defined in and validated against the Offer table. See Working with Offers (WOFR). The first offer code you enter on this screen will default for any other catalog requests you create so you can enter them quickly. This field clears when you exit the screen. The offer code will default in the Offer field for alternate address and standard address format. Note: You must enter an offer code or an item/SKU. Numeric, 3 positions; required unless you complete the Item field. |
Item (Item number) |
The code for the item you are sending to the customer with the catalog. Examples would be swatches of material or promotional items printed with your company name. Item numbers are defined in and validated against the Item table. See Performing Initial Item Entry (MITM). Alphanumeric, 12 positions; optional. |
SKUs |
A code for the style of the item, such as its color or size. Alphanumeric, three 4-position fields; required if entering an item that has SKUs. |
Catalog Request Customer Updates
When you create a new customer here, the system creates the new customer in the Customer Sold To table. The current and original mail type fields are set to C (catalog request). If the Track Customer History at Entity Level (F89) system control value is selected, the system also creates a Customer Entity record for the entity associated with the source code. If you create an individual customer at this time, the system creates the new individual in the Customer Individual table.
Relate customer integration: If the Relate Customer Integration (L37) system control value is set to INTERACT, when you create a new customer at this screen, the customer is also created in Relate, and the two customer records are synchronized. See the Relate Customer Integration for more information.
If you select an existing customer and change the value of an existing field, such as the Opt in/opt out field or the Customer class, the system updates the customer table. See Creating and Updating Sold-to Customers (WCST).
When the catalog request label is printed, the Customer Mail History table is updated through the catalog request. The Original source field is updated if you added a new customer. See First Create Sold To Customer Screen. However, if the catalog request includes an individual, only the Individual Mail History table is updated.
If the customer you enter already exists: The system displays the Duplicate Customer window if the customer information you enter matches an existing customer in the Sold To Customer table. The system displays this window based on match code.
You can use the existing customer information and cancel the creation of the new customer, or you can override this message and create the additional customer. You might use the duplicate customer information, for example, if two different people with the same name, such as John Smith, live at addresses that are so similar that the system thinks they are the same person.
If the customer's catalog request already exists: The system displays the Display Duplicate Sold To pop-up window if the customer and offer/item information you enter at the Create Catalog Request Screen matches an existing customer sold to, based on match code. A match code is made up of parts of the customers name, address, and postal code. The match code is a user-defined code defined in the Match Code table; See Setting Up Match Codes (MMCH).
Note: If you do not set up a match code in the Match Code table, the system displays the first sold to customer, based on sold to customer number, as a duplicate each time you enter a new address.
Duplicate catalog requests: The system uses the Edit for Duplicate Catalog Requests (E46) system control value to update duplicate catalog requests. If this value is selected, the system checks for a duplicate when you create a new catalog request; if there is a match, the system replaces the existing request with the new one. If this value is unselected, the system creates a new catalog request without checking the existing records.
Individual updates: If you selected Individual and entered an individual for the sold-to customer, the system creates the new individual for the customer. The individual’s Orig mail type (Original mail type) and Current mail type will be C, the Mail and Rent flags will default from the sold-to customer’s, and the Mail code will default from the Mail flag. If you selected Select Individual to select an existing individual, the system updates the individual’s email address, mail flag, and rent flag if you have changed them.
If the individual you enter already exists: If you selected Individual and entered an individual for the sold-to customer, and the first three positions of the individual’s first name and the first four positions of the individual’s last name match an existing individual for the sold-to customer, you advance to the Display Duplicate Individual Window. You can select the existing individual without update, or create the new individual using the information you just entered.
When you print the catalog request label through Processing Catalog Requests (PCAT), the mail history information in the Individual Mail History table (available for review at the Display Individual Mail History Screen) is updated through the catalog request; the Customer Mail History is not updated if there is an individual on the catalog request.
Also, when you print the catalog request label, the system uses the total number of requests rather than the total number of copies when tracking catalog request history in the Source Code table and in the Catalog Request History table. For example, if a customer requests 3 copies of a catalog, the system increases the total by 1, not by 3. You can review the total number of catalog requests for a source code at the Source Code History Screen and on the Campaign Performance Report (PCPR).
Screen Option |
Procedure |
Enter a catalog request for a new customer |
Complete the fields as described under Create Catalog Request Screen. See Catalog Request Creation Options for an overview. |
Select an existing customer |
Select Customer to advance to the Select Customer for Catalog Request Screen. See Catalog Request Creation Options for an overview. Note: If the Relate Customer Integration (L37) system control value is set to INTERACT, you advance instead to the Customer Scan Screen. See that screen for more information. |
Enter individual customer information |
Select Individual to display additional fields for individual customer creation. The Enable Catalog Request at Customer Individual Level (H81) system control value must be selected. See Catalog Request Creation Options for an overview, or see Create Catalog Request Screen for individual field descriptions. |
Work with products a customer owns |
Select Cust Ownership. • If the customer is currently associated with customer ownership records, you advance to the Work with Customer Ownership Screen. • If the customer is currently not associated with customer ownership records, you advance to the Create Customer Ownership Screen. |
Select an existing individual customer |
Select Select Individual to advance to the Select Customer Individual Screen. The Enable Catalog Request at Customer Individual Level (H81) system control value must be selected. See Catalog Request Creation Options for an overview. Note: The system does not prevent you from entering a catalog request for an individual whose Status is Inactive. |
Add notes for the customer |
Select Notes to advance to the Edit Customer Notes Screen. |
Select Customer for Catalog Request Screen
Purpose: In addition to creating catalog requests for people who are not yet customers, you can also create catalog requests for existing customers from the Create Catalog Request Screen.
When creating a catalog request for an existing customer, the system copies customer information from the Sold To Customer directly into the catalog request. See Catalog Request Creation Options for an overview.
How to display this screen: At the Create Catalog Request Screen, select Select Customer.
Note: If the Relate Customer Integration (L37) system control value is set to INTERACT, you advance instead to the Customer Scan Screen. See that screen for more information.
How to use this screen: Use this screen to advance to scan screens that let you locate existing customer records. If the customer exists, you can select the customer and the system will copy information from the customer into the customer fields on the Create Catalog Request Screen.
Field |
Description |
Customer |
A unique number the system assigns to each customer on creation of the customer through Order Entry, Customer Maintenance, or catalog requests. Ghost customers: If you enter the customer number of a ghost customer, the system displays the Ghost Customer Warning Window. Numeric, 9 positions; optional. |
Postal code |
The postal or zip code that identifies the customer's geographic location. Enter a full or partial code to advance to the Scan Sold To by Postal Code/Company screen. This screen lists all customers by postal code in ascending (lowest to highest) numeric sequence, beginning with the code you entered. If you enter a postal code, last name, and first name, you advance to the Scan Customer Sold To by Postal Code screen, which lists all customers alphabetically beginning with the postal code you entered. Alphanumeric, 10 positions; optional. |
Last name |
The sold-to customer's last name. Enter a last name, first name, and postal code to advance to the Scan Customer by Postal Code/Last Name screen, positioned to the customer with the last name, first name, and postal code you entered. Enter a full or partial name to advance to a Scan Cust Sold To By Last Name screen, which lists all customers alphabetically beginning with the name you entered. You can also include a full or partial first name along with a full (not partial) last name to restrict the scan further. Alphanumeric, 25 positions; optional. |
First name |
The sold-to customer’s first name. Enter the last name, first name, and postal code to advance to the Scan Customer Sold To by Postal Code screen, which lists all customers alphabetically beginning with the postal code you entered. You can also enter just the full (not partial) last name and full or partial first name to advance to the Scan Cust Sold To By Last Name screen. Note: First name must be used in conjunction with Postal code, Last name for scanning. You cannot scan on first name alone, or on first name, last name. Alphanumeric, 15 positions; optional. |
Company |
The name of the company placing the catalog request. Alphanumeric, 30 positions; optional. |
Telephone # |
The customer's daytime, evening, or third (fax or mobile) telephone number. Note: The Third Phone Number Type (L53) system control value determines whether the third phone number is labeled the Fax or Mobile number. Note: Your entry should include any formatting specified by the telephone number format for the country; for example, if the telephone number format for the United States is (111) 111-111, your entry should include the parentheses and hyphen. See Setting Up the Country Table (WCTY), for more information on telephone number formats by country. Alphanumeric, 14 positions; optional. |
Alt cust nbr (Alternate customer number) |
A number to identify the customer, such as a serial number or an old customer number from a system conversion. Enter an alternate customer number to advance to a subsequent scan screen that lists customers by alternate customer number. See Display Alternate Customer Cross Reference Window (I84) for more information. Alternate Customer Number Label Description The field label on this screen is based on the name you enter in the Alternate Customer Number Label Description (H95) system control value; if you do not enter a name in this system control value, the field label is Alt cust nbr. Example: If you enter the field label name MEMBER# in the system control value, the field label on this screen is MEMBER#. Note: Scanning by the alternate customer number of a ghost customer is not currently implemented if the Display Alternate Customer Cross Reference Window (I84) system control value is selected. Alphanumeric, 15 positions; optional. |
Email Address |
An email address for the customer. When you enter a full or partial email address, you advance to the Scan Customer by Email Address screen, where you can scan by any email address on file for a customer. This field is not case sensitive; an email address of abc@example.com matches an entry of ABC@EXAMPLE.COM, and vice versa. Alphanumeric, 30 positions; optional. |
Option |
Procedure |
Select a customer for a catalog request |
Click a customer name to return to the Create Catalog Request Screen with that customer’s name and address defaulted. |
Change a customer’s name and address information |
Select Change for a customer to advance to the Change Cust Sold to Name & Address Screen. |
Display a customer’s name and address information |
Select Display for a customer to advance to the Display Customer Sold To screen. See the See the First Create Sold To Customer Screen for field descriptions. |
Create a catalog request for a new customer |
Select Create to return to the Create Catalog Request Screen without selecting a customer. |
A ghost customer is a customer whose records have been merged with the records of a matching customer through a merge/purge. The ghost customer was the source customer in the merge; records for this customer were merged with the records for a matching target customer. When performing the merge you can elect to flag a source customer as a Ghost. Ghost customer records are retained in the Customer Sold To table for informational purposes, but they do not represent the most recent customer order information from the merged (target customer) records.
When you enter the number of a ghost customer, the pop-up Warning Window presents the information on the ghost customer and target.
Select Continue to advance to the Create Catalog Request Screen with the target customer number entered on the screen. For example, if you enter 202, a ghost customer, the system will display this window informing you that customer 202 has been merged into customer 137. When you continue with the catalog request process, customer 137 will default on the Create Catalog Request screen.
Note: The Ghost Customer Warning pop-up window does not display when you use the Customer Selection Screen.
See Working with Merge/Purge Sold-to Names (MMCS) for more information on the merge/purge function.
Canceling the creation: Once you select a customer from the Select Customer for Catalog Request Screen, you return to the Create Catalog Request Screen, which displays the information from the request you selected. If, on review, you learn that the customer information is incorrect, you can remove it from the screen without creating a catalog request.
Select Create to erase the selected customer information from the Create Catalog Request Screen. The system clears your entries and you can begin again.
Purpose: Use this screen to change the offer number, item number, SKU, source code, or the number of copies for a catalog request.
How to display this screen: At the Work with Catalog Requests Screen, select Change for a catalog request.
Additional fields at this screen:
Field |
Description |
Printed |
A code that identifies whether the catalog mailing label has been printed for a catalog request. The system updates this value when you process the catalog requests; see Processing Catalog Requests (PCAT). If you unselect this flag after the catalog request label is printed, the system decreases the Requests mailed total for the source code. Once you print the label again, the system increases the total again. You can review this total at the Source Code History Screen and on the Campaign Performance Report (PCPR). Values are: selected = The catalog label has been printed. unselected = The catalog label has not been printed. |
Date printed |
The date the catalog label was printed. Numeric, 6 positions (MMDDYY format); display-only. |
Catalog requested on |
The date and time of the catalog request. Date: numeric, 6 positions (MMDDYY format); updated by the system. Time: numeric, 6 positions; HHMMSS (hour/hour, minute/minute, second/second) format, updated by the system. |
Catalog requested by |
The name of the system user who entered or processed the catalog request. Alphanumeric, 10 positions; display-only. |
See Create Catalog Request Screen for a description of the other fields on this screen.
Note: Changing a catalog request from one source code to another does not affect the total quantity for each source code tracked in the Catalog Request History file, or tracked on reports such as the Campaign Performance Report (see Print Campaign Performance Reports (PCPR) for more information).
Working with Catalog Requests | Contents | SCVs | Search | Glossary | Reports | Solutions | XML | Index | Processing Catalog Requests (PCAT) |
WCAT OROMS 5.0 2018 OTN