Working with the Catalog Request Interface (WCRU)

Purpose: Use the Work with Catalog Request menu option to review the records that have been uploaded to the Catalog Request Interface table (IXCRIN), to correct any errors, and to generate catalog requests from the interface records. You might use the Catalog Request Interface table as a means to collect catalog requests you receive from various sources, and make sure that you have complete information for each of them before you attempt to create the catalog requests in Order Management System.

The catalog request interface also creates new customer sold to records, and you can use the interface to create a customer record without actually processing a catalog request.

Use the following steps to create a catalog request from an external system.

1.

Create a text file that contains the records to upload to the Catalog Request Interface table. You can use the sample data below to create records in the upload text file.

34 SAMPLE STREET|APT123|ADDRESS LINE 2|ADDRESS LINE 3|ADDRESS LINE 4|WESTBOROUGH|01581||MA|US|5085550100||thomasbrown@example.com|O1|R|COMPANY NAME|SOURCE7|7|1150417|207|5085550101||5085550102||MS.|MARY|M|JOHNSON||MARYJOHNSON@EXAMPLE.COM||5085550104|5085550105|5085550106|1|1|O1

Note: If you wish to leave any field in the upload file blank, pass a space in an alphanumeric field and a 0 in a numeric field so that the file can be processed without errors. Leaving a field with no space or 0 is interpreted as null in the database and causes errors.

2.

Populate the Catalog Request Interface table by:

• Using the File Storage API to upload the contents of the file in the FILE_STORAGE table, and then run the UPCATRQ Upload Catalog Request File (Program name PFR0134, Parameter IXCRIN) periodic function, or

• Place the file in the CWDIRECTCP_UPLOAD_ DIRECTORY if the file storage API is not enabled, and then run the UPCATRQ Upload Catalog Request File (Program name PFR0134, Parameter IXCRIN) periodic function, or

• Use the Work with File Uploads (WUPL) menu option to upload the file and populate the table.

3.

Select Submit at the Work with Catalog Request Interface Screen to process the requests. When you process:

• Each valid record is deleted from the interface table, and a customer sold to and/or catalog request is created as appropriate. Also, the Catalog Request History table is updated.

• Each invalid record is flagged with an error (E) status. You can use the Change Catalog Request Screen to correct errors.

• The Print Request Interface Report and the Print Catalog Request Interface Errors Report are generated.

4.

Once the catalog requests are generated, you can process and print them like any other requests. See Entering Catalog Requests (WCAT).

E-Commerce catalog requests: You can use this menu option to review and correct catalog requests received through the e-commerce catalog request process that are in error. If a catalog request received through the e-commerce catalog request process does not contain errors, you can review and process the catalog request using the Work with Catalog Requests menu option; see Entering Catalog Requests (WCAT).

Note: If you receive a catalog request from e-commerce that has errors, and customer ownership information has been defined for the sold to customer on the catalog request, the system does not retain the customer ownership information when you correct the errors and reprocess the catalog request.

Oracle Retail Customer Engagement customer integration: When you use the Oracle Retail Customer Engagement customer integration, if you create a customer through the catalog request interface, Order Management System sends the customer’s name, address, email address, phone numbers, and contact permissions to Oracle Retail Customer Engagement so that the customer records in the two systems are synchronized. See the Customer Engagement Customer Integration for more information.

In this chapter:

Work with Catalog Request Interface Screen

Change Catalog Request Screen

Processing Requests

- Catalog Request Interface Errors

- Catalog Request Related System Control Values

- Creating a New Customer

Print Request Interface Report

Print Catalog Request Interface Errors Report

Work with Catalog Request Interface Screen

How to display this screen: Enter WCRU in the Fast path field on any menu or select Work with Catalog Request Interface from a menu.

Field

Description

Type

Indicates the source of the catalog request.

Note: If this field is blank, the catalog request is in error status and you cannot change it through this menu option. You need to delete the record and recreate it, either by populating the Catalog Request Interface table directly or by entering the catalog request through Entering Catalog Requests (WCAT).

E-Commerce catalog requests: Catalog requests received through the e-commerce catalog request process have a type of PHR0062.

Alphanumeric, 10 positions; optional.

Source

The source code assigned to the catalog request, indicating how the customer came to contact you. If the source code is not specified in the Catalog Request Interface table, the system assigns the Default Source Code for Batch Catalog Requests (D37) system control value when you select Submit to submit the interface records for processing.

Alphanumeric, 9 positions; optional.

Name

The customer's last and first names, separated by a column.

Last name: alphanumeric, 25 positions; display-only.

First name: alphanumeric, 15 positions; display-only.

Date

The date specified in the Catalog Request Interface table indicating when the request was received.

Numeric, 6 positions (in user date format); optional.

St (Status)

Indicates the current status of the catalog request.

Valid values are:

E = One or more errors are preventing the interface record from being processed. You must correct the record before you resubmit the records for processing. However, if the Type field is not populated, you cannot correct the record; you need to delete it and recreate it.

P = The CATALOGREQ job is currently running; you cannot work with the record until this job is complete.

• blank = The record is currently open. When you select Submit to submit the interface records for processing, the CATALOGREQ job evaluates the record for errors and, if it is error-free, the job performs the processing described Processing Requests.

Alphanumeric, 1 position; optional.

Screen Option

Procedure

Change a catalog request interface record

Select Change for a record to advance to the Change Catalog Request Screen.

Delete a catalog request interface record

Select Delete for a record to delete it.

Display a catalog request interface record

Select Display for a record to advance to the Display Catalog Request Screen.

Submit the catalog request records for processing

Select Submit. See Processing Requests.

Change Catalog Request Screen

Purpose: Use this screen to change a record in the Catalog Request Interface table and to correct errors. When you select OK, the system validates the entries on the screen and highlights the field that contains an error.

Once you correct the errors on this screen, the record’s status changes from E to blank, and it is eligible for processing.

How to display this screen: Select Change for a catalog request record at the Work with Catalog Request Interface Screen.

Note: If the Type field for the catalog request record is blank, you advance first to a key screen and you cannot correct any other errors for the record. You need to delete the record and recreate it (for example, using Entering Catalog Requests (WCAT)).

Field

Description

Name

The following fields are available for the customer's full name:

Prefix

A title (such as “Mrs.” or “Dr.”) that precedes the customer's name. The prefix prints on labels, reports, etc.

Alphanumeric, 3 positions; optional.

First Name

The Sold-to customer's first name

Alphanumeric, 15 positions; optional.

Initial

The initial of the customer's middle name.

Alphanumeric, 1 position; optional.

Last Name

The customer's last name.

Alphanumeric, 25 positions; required if company name is not specified.

Suffix

An addition to the customer's full name (such as “M.D.,” “Fr.,” or “III”). The suffix prints on labels, reports, etc., but is not accessible to scans.

Errors: The record is in error status if both the last name and the company field are blank.

Alphanumeric, 3 positions, optional.

Company

The name of the company associated with the customer placing the order.

Errors: The record is in error status if both the last name and the company field are blank.

Alphanumeric, 30 positions; required if last name is not specified.

Street

The customer's street address. This is the primary delivery address.

Errors: The record is in error status if this field is blank.

Alphanumeric, 32 positions; required.

Apt./suite (Apartment/suite)

The apartment number or suite number associated with the customer's delivery address.

Follow these steps to enter an apartment or suite address:

• Enter APT to indicate an apartment or STE to indicate a suite.

• Insert a space and enter the number of the apartment or suite, for example: APT 4 or STE 116.

Addresses must conform to United States Parcel Service (USPS) address formatting field description standards. For example, always precede the apartment or suite number with the appropriate abbreviation (for example, APT or STE).

Alphanumeric, 10 positions; optional.

Address

Three additional lines of the customer's delivery address. If the address represents a post office box, you must enter P.O. Box on the first line to meet USPS delivery regulations.

Alphanumeric, three 30-position lines; optional.

Postal code

The postal or zip code for this customer. This code represents a delivery area.

Required? A postal code is required only if the Require postal code? flag for the country is selected; see Setting Up the Country Table (WCTY).

Postal code validation: If a postal code is required, it is validated against the Zip/City/State (Postal Code) table; see Setting Up the Zip/City/State (Postal Code) Table (WZIP).

Errors: The record is in error status if the Require postal code? flag for the country is selected and the SCF of the postal code is blank or invalid, or if the postal code does not match the state. See Catalog Request Interface Errors.

Alphanumeric, 10 positions; required or optional based on country.

City

The city where the customer lives or receives mail or shipments.

Alphanumeric, 25 positions; required.

St (State)

The state or province where the customer lives or receives mail or shipments.

Defined where? State codes are defined in and validated against the State table, accessible through the Work with Countries menu option; see Setting Up the Country Table (WCTY).

Required? A state is required only if the Require state? flag for country is selected. See Setting Up the Country Table (WCTY).

SCF validation: If the Require postal? flag for the country is selected, the system validates that the state you enter is assigned to the SCF associated with the postal code. See Working with SCF Codes (WSCF) for background.

Errors: The record is in error status if the Require state? flag for country is selected and there is not a valid state code. State codes must be in uppercase.

Alphanumeric, 2 positions; required or optional based on country.

Country

The code for the customer's country. Country codes are defined in and validated against the Country table.

The Default Country for Customer Address (B17) system control value defaults here when you submit the catalog request for processing if the country code was not already specified for the record.

Errors: The record is in error status if there is not a valid country code. Country codes must be in uppercase.

See Setting Up the Country Table (WCTY).

Alphanumeric, 3 positions; required.

Delivery code

Identifies a business (commercial) or residential address. Used to calculate shipping charges for shippers that use rate tables (such as U.P.S.).

Business = Business rate table determines shipping charges.

Residential = Residential rate table determines shipping charges.

No distinction = No distinction between business and residence.

Errors: The record is in error if the delivery code is blank or invalid. Delivery codes must be in uppercase.

Required.

Phone numbers

The customer's day, evening, and third (fax or mobile) phone 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, 14 positions each; optional.

Ext (Extension)

The extension of the customer's day, evening, and third (fax or mobile) phone number.

Note: The extension for the third phone number is not updated through the catalog request upload process.

Numeric, 4 positions; optional.

Email address

The customer's email address.

Alphanumeric, 30 positions; optional.

OptIn (Opt in/opt out)

Indicates the preferred method of correspondence for the customer email address.

Valid values are:

All Emails = Email is the preferred method of correspondence.

Order Emails Only = Use email for order-related correspondence only; generate a document for other correspondence.

No Emails = 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.

Defaults from the Opt in/opt out field for the sold-to customer, and if blank, 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).

Required.

Create catalog request?

Indicates whether to create a catalog request. Valid values are:

selected = Create a catalog request.

unselected = Do not create a catalog request.

Regardless of the setting in this field, the system may still create a new customer sold to; see the Perform duplicate check field.

Errors: The record is in error status if this field is not set to a valid value.

Perform duplicate check?

Indicates whether to perform a match code check to determine whether the catalog request represents a new customer. Valid values are:

selected = Perform a duplicate check based on match code. If the catalog request matches an existing customer based on match code, do not create a new customer; use the existing customer record without updating it. If more than one existing customer has the same match code, use the first match.

unselected = Do not perform a duplicate check based on match code; create a new customer record using the information in the catalog request.

Errors: The record is in error status if this field is not set to a valid value.

See Setting Up Match Codes (MMCH) for more information on match codes and duplicate checking.

File type

Indicates the source of the catalog request. This information is not validated against any tables in Order Management System.

Errors: The record is in error status if this field is blank. In this case, you cannot correct the record at this screen; instead, you can delete the record and recreate it, or update the table directly.

Alphanumeric, 10 positions; display-only.

Request date

The date when you received the request. The system does not update this field. If a date was indicated in the catalog request interface record, it appears here; however, you can change it.

Numeric, 6 positions (in user date format); optional.

Source

A code that identifies a list of names for this catalog mailing. The source code drives marketing, pricing, and freight information on an order.

Overrides: When you submit the requests for processing, the system assigns the Default Source Code for Batch Catalog Requests (D37) system control value if a valid source is not specified for the catalog request. In this situation, the offer for the record is reset, if necessary, to match the default source code.

Source codes are defined in and validated against the Source Code table. See Working with Source Codes (WSRC).

Alphanumeric, 9 positions; required.

Offer

The code for the catalog that the customer is requesting.

Overrides: The system defaults or overrides the offer in the catalog request record when you submit the requests for processing so that it matches the source code. If the offer is not specified, the job defaults the offer associated with the source code. If the offer does not match the source code, the job replaces this offer with the offer associated with the source code.

Errors: The record is in error status if both source code and offer are blank when you submit the records for processing. However, the record is corrected the next time you submit records for processing. The reason this correction occurs is that, the first time you submit the records, the job sets the source code field to the Default Source Code for Batch Catalog Requests (D37). The second time you submit the records, the job updates the Offer field to match the assigned source code.

Offer codes are defined in and validated against the Offer table. See Working with Offers (WOFR) for more information.

Alphanumeric, 3 positions; required.

Entity

The business unit in your company associated with the catalog request.

If the Track Customer History at Entity Level (F89) system control value is selected: When you submit the requests for processing, the system creates a Customer Sold To Entity record for the entity specified for the catalog request, if any. If no entity is specified for the catalog request, the system creates a Customer Entity record for the entity associated with the Default Source Code for Batch Catalog Requests (D37) system control value. (An entity is associated with a source code through the division assigned to the source code.).

Errors: The record is in error status if this field is not set to a valid entity. If the entity is not specified for the record, the system resets the entity to match the source code.

Entity codes are defined in and validated against the Entity table. See Working with Entities (WENT).

Numeric, 3 positions; required.

Display Catalog Request Screen

To display: Select Display for a record at the Work with Catalog Request Interface Screen to advance to the Display Catalog Request screen. You cannot change any information on this screen. See Change Catalog Request Screen for field descriptions.

Processing Requests

Purpose: Select Submit at the Work with Catalog Request Interface Screen to submit requests for processing. The system submits the job CATALOGREQ, which:

• Checks each open record in the Catalog Request Interface table for errors. Each record that has an error is flagged with an error status (E).

• Checks for duplicates:

- If the record's Perform duplicate check? flag is selected, the job checks the catalog request against existing customer sold to records based on match code. If the catalog request's match code is the same as an existing customer's, the job does not create a new customer; instead, it uses the existing customer. (If more than one customer record has the same match code, the job uses the first matching customer it finds.) See Setting Up Match Codes (MMCH).

- If the record's Perform duplicate check? flag is unselected, or if no customer records match the catalog request, the job creates a new sold to customer. See Creating a New Customer.

• Creates the catalog request. The job creates a catalog request only if the record's Create catalog request? flag is selected. You can review or process these catalog requests through the Work with Catalog Request menu option; see Entering Catalog Requests (WCAT).

• Creates the Print Request Interface Report and the Print Catalog Request Interface Errors Report.

• Deletes each processed record from the Catalog Request Interface table.

Catalog Request Interface Errors

The following conditions put a catalog request in an error (E) status:

• Type field is blank

• Invalid postal code or SCF, or postal code does not match state

• State is not valid, or does not match country

• Country code is invalid

• Both last name and company name are blank

• No street address

• Entity is invalid

• Delivery code is invalid or blank

Create catalog request? flag is invalid or blank

Perform duplicate check? flag is invalid or blank

• Both offer and source code are blank (but this error is corrected when you next submit the records for processing if the Default Source Code for Batch Catalog Requests (D37) is assigned to the record)

• Offer is invalid

• Source is invalid

Certain errors, such as a missing source code, country, or entity, are corrected by the batch job during processing based on system control value defaults. See Change Catalog Request Screen.

Catalog Request Related System Control Values

System Control Value

Description

Default Country for Customer Address (B17)

If a country code is missing from the catalog request, Order Management System defaults the country code defined in this system control value to the catalog request.

Default Delivery Code for New Order Entry Customers (D13)

If a delivery code is missing from the catalog request, Order Management System defaults the delivery code defined in this system control value to the catalog request.

Default Source Code for Batch Catalog Requests (D37)

If both a source code and offer code have not been defined for the catalog request, Order Management System defaults the source code defined in this system control value to the catalog request. The source code indicates the offer (catalog) to mail to the customer.

Default Country for International Address Format (D69)

If a country code is missing from an catalog request for an international address, Order Management System defaults the country code defined in this system control value to the catalog request.

Edit for Duplicate Catalog Requests (E46)

Defines whether Order Management System checks for duplicate records when you create a new catalog request. If a duplicate is found, Order Management System does not create a new catalog request and instead uses the existing request, resetting the Printed flag to No if necessary.

Duplicate Checking for Customers (F71-F77, H88 and I11)

Defines whether a catalog request received through the e-commerce qualifies as a match to an existing record based on match code, even if the first name is not exactly the same.

Default Opt In/Opt Out Flag (G97)

Defines the value that defaults to the Opt-in/Opt-out field for the catalog request and customer sold to record. The opt-in flag indicates whether e-mail is the preferred method of correspondence for a customer.

If the catalog request includes a value in the bill_to_opt_in flag, the system defaults this value to the catalog request and the customer sold to record. If the customer sold to record already has an opt-in value, the system overrides this value with the opt-in value passed in the catalog request.

If the catalog request does not contain a value in the sold_to_opt_in flag, the system defaults the value defined in the Default Opt In/Opt Out Flag (G97) system control value.

Default Customer Class in Order Entry (D63)

If the Require Customer Class in OE, WCAT, and WCST (H85) system control value is selected, this customer class is assigned to new customers you create through the catalog request interface.

Creating a New Customer

If the catalog request does not match an existing customer based on match code, or if match code duplicate checking was not selected for the catalog request, the system creates a new sold to customer based on the information in the catalog request. The system uses the following information to create the new customer:

From the catalog request:

• Name and address information

• Delivery code

• Daytime, evening, and third (fax or mobile) phone numbers, and the extensions for the daytime and evening numbers

• Mail code and mail flag: from the allow_mail setting

• Rent flag: from the allow_rent setting

• Opt in/opt out: from the bill_to_opt_in setting

The country and source code may have defaulted from the Default Country for Customer Address (B17) and Default Source Code for Batch Catalog Requests (D37) settings in the System Control table.

Additional defaults from the System Control table:

• Associate flag: uses the setting from the Default Associate Code (D09) system control value

• Mail flag: uses the setting from the Default Mail Name (D10) system control value if it was not specified in the catalog request

• Rent flag: uses the setting from the Default Rent Name (D11) system control value if it was not specified in the catalog request

• Mail code: uses the setting from the Default Mail Name (D10) system control value if the allow_mail setting was not specified in the catalog request

• Opt-in/opt-out flag: uses the setting from the Default Opt In/Opt Out Flag (G97) system control value if it was not specified in the catalog request

• Customer class: uses the setting from the Default Customer Class in Order Entry (D63) system control value if the Require Customer Class in OE, WCAT, and WCST (H85) is selected

The Current mail type and Original mail type fields are set to C (catalog request).

Oracle Retail Customer Engagement customer integration: When you use the Oracle Retail Customer Engagement customer integration, if you create a customer through the catalog request interface, Order Management System sends the customer’s name, address, email address, phone numbers, and contact permissions to Oracle Retail Customer Engagement so that the customer records in the two systems are synchronized. See the Customer Engagement Customer Integration for more information.

WCRU OMSCS 19.0 December 2019 OHC