Working with Entities (WENT)

Purpose: Use the Entities function to add or maintain entities and their descriptions. Entities are an important component of the CWDirect sales reporting hierarchy, and can represent the business units within your company (for example, mail order, retail, wholesale). Every sale, return, exchange, discount, and write-off is attributed to an entity. Entities should represent any organization within your company that is held accountable for sales performance.

You must create at least one entity.

Email options: You can set entity-level overrides for email notifications generated by the system, including the text of the email template, the “from” email address, and whether to generate a generic XML message which can be reformatted by an external system rather than sending an actual email directly to the customer.

You can also set up system control value overrides at the entity level.

In this topic:

• CWDirect Sales Reporting Hierarchy

• Related System Control Values and Settings

• Work with Entities Screen

• Create Entity Screen

• Change Entity Screen

• Display Entity Screen

• Work with Entity SCV Overrides Screen

• Edit Pricing Values Screen

• Work with Entity Return Address Screen

• Working with Entity Email Overrides

• Directory Address (“From” Email Address) Override at Entity Level

• Email Template Override at Entity Level

• Work with Entity Email Overrides Screen

• Change Email Override Screen

• Display Email Override Screen

CWDirect Sales Reporting Hierarchy

Related System Control Values and Settings

These system control values allow you to define additional settings related to the use of entity in your company.

• Display Entity Description (F84): If this system control value is set to Y, the entity related to an order displays in order inquiry and at the Customer Selection Screen in order entry. An entity is related to an order through the source code on the order header; when you create a source code, you must associate it with a division, and each division points to an entity. See the CWDirect Sales Reporting Hierarchy chart for an illustration.

Note: Only the first five characters of the entity description display on the CTI Customer Selection screen.

• Shadow posting for multi currency: If you process orders in multiple currencies (the Multi Currency by Offer (E03) system control value is set to Y), you must define a shadow entity for each currency except your local currency. The shadow entity enables the system to make a posting to the General Ledger Interface file for each order entry, order maintenance, cash receipts, or returns transaction in the currency of the order, in addition to the posting in your local currency. The shadow entity inherits the chart of accounts defined for the actual entity associated with the division. See Working with Currency (WCUR).

• Track Customer History at Entity Level (F89): If this system control value is set to Y, the system tracks each customer's order history separately based on the entity associated with the source code on the order header. You might choose to break out customer history by entity if you have multiple catalogs with distinct identities, yet sharing the same customer list and inventory.

• Pass Entity Code to Vertex (F69): If this system control value is set to Y, the system passes the entity code to Vertex when requesting tax information.

• Tax API Default Entity (L67): If the Pass Entity Code to Vertex (F69) is system control value is set to Y, the Tax API specifies this entity when requesting tax information from Vertex.

Work with Entities Screen

Use this screen to review the entities in your company, or to create, change, delete, or display an entity.

How to display this screen: Enter WENT in the Fast Path field at the top of any menu or select Work with Entities from a menu.

ACR0013 DISPLAY Work with Entities 3/29/04 10:17:04 EZK Mail Order Opt Entity Description Type options, press Enter. 2=Change 4=Delete 5=Display 7=Control value overrides 10=Return address 11=Email overrides 98=User field 1 ROBOTS ALIVE 2 A DOG'S LIFE 3 SPECIAL KIDS 4 CANADIAN SHADOW ENTITY 5 ITALIAN SHADOW ENTITY 11 ITALIAN ENTITY F3=Exit F6=Create F12=Cancel F21=Print list F24=Select company

Field	Description
Entity	A code that represents the entity. Numeric, 3 positions; optional.
Description	The description of the entity code. Alphanumeric, 25 positions; optional.

.

Screen Option	Procedure
Create a new entity code	Press F6 to advance to the Create Entity Screen.
Change entity information	Enter 2 next to an entity to advance to the Change Entity Screen.
Delete entity information	Enter 4 next to an entity to delete it. The system does not display an additional warning if you have taken orders for this entity; use care in deleting.
Display entity information	Enter 5 next to an entity to advance to the Display Entity Screen.
Work with system control value overrides by entity	Enter 7 next to an entity to advance to the Work with Entity SCV Overrides Screen.
Enter or change the return address for printing on customer return labels from the web storefront	Enter 10 next to an entity to advance to the Work with Entity Return Address Screen.
Work with entity-level overrides for email notifications	Enter 11 next to an entity to advance to the Work with Entity Email Overrides Screen.
Work with user defined fields	Enter 98 next to an entity to advance to the Work with User Fields Screen.

Create Entity Screen

Purpose: Use this screen to create an entity code.

How to display this screen: Press F6 at the Work with Entities Screen.

ACR0008 ENTER Create Entity 2/11/99 10:34:11 EZK Mail Order Entity . . . . . Description . . . Name . . . . . . Address . . . . . City/St/Postal . Country . . . . . Phone#/Ext . . . Retail Brand F3=Exit F12=Cancel

Field	Description
Entity	A code that represents an entity. Entities are an important component of the CWDirect sales reporting hierarchy. Entities can represent the business units within your company (for example, mail order, retail, wholesale). Every sale, return, exchange, discount, and write-off is attributed to an entity. Entities should represent any organization within your company that is held accountable for sales performance. You must create at least one entity. Numeric, 3 positions. Create screen: required. Change screen: display-only.
Description	The description of the entity. Alphanumeric, 25 positions; required.
The following address fields may appear on printed forms if your unique printing programs support it.
Name	The name of the entity. Alphanumeric, 30 positions; optional.
Address	Two lines of address information. You must enter at least one line of address information if you complete any of the remaining address fields. Alphanumeric, 32 positions each; required if you complete any of the address fields.
City	The city where the entity is located. Alphanumeric, 25 positions; required if you complete any of the address fields.
St (State)	The state where the entity is located. The system validates that this is a valid state associated with the Country you enter. See Setting Up the Country File (WCTY). Alphanumeric, 2 positions; required if you complete any of the address fields.
Postal (Postal code)	The zip or postal code where the entity is located. Your entry is not validated against the Postal Code file, and no formatting is applied. Alphanumeric, 10 positions; required if you complete any of the address fields.
Country	The country where the entity is located. Your entry is validated against the Country file; see Setting Up the Country File (WCTY). Alphanumeric, 3 positions; required if you complete any of the address fields.
Phone number/Extension	The phone number and extension. You can define a telephone number format to map to the phone numbers operators enter into the system. Telephone number formats are defined by arranging numbers and special characters such as hyphens and parenthesis in the same order and position as the numbers in a phone number would display. When an operator enters a phone number, the system compares the number of numeric characters in the phone number with the telephone number formats you have defined. In order to match a format, the phone number must have the same number of numeric positions as a telephone number format. If the system cannot find a match, the phone number does not map to a telephone number format and is saved as it was entered by the operator.
	Telephone Number Format Examples An operator enters a phone number containing 10 numbers: 5084293197 The telephone number format used in the United States to represent an area code, local exchange and local phone number is: (508) 429-3197 When an operator enters a phone number containing 10 numbers (as in the example), the phone number displays so that the first 3 positions are in parenthesis and a hyphen is between the sixth and seventh numbers, regardless of how the operator entered it into the system. If an operator enters a phone number containing 6 numbers, for example 4293197 and no format exists for 6 numbers, the phone number would display as it was entered (4293197). See Setting Up the Postal Code File (WZIP). The system calls a user-defined program to validate phone numbers outside of CWDirect if you set the External Validation for Phone Number (E64) system control value to Y.
	The system provides a “hook” to the program when an operator presses Enter on a screen containing a phone number associated with a country. This program can be used to validate country phone number rules for a specific country, for example, if a phone number for a country should only contain 6 numbers and more than 6 numbers are entered, an error message displays. Phone numbers that are not associated with a country, for example, phone numbers in the Bank, Salesman, Warehouse and Ship Via files, are not validated. The program validates phone numbers based on the following parameters: • Company • Country • State • City • Phone Number Alphanumeric, 14 positions (phone number) and 4 positions (phone extension); optional.
Retail Brand	The retail brand associated with the entity. Retail brands are used by the CWCollaborate Interface for drop ship processing to identify the retail brand to CWCollaborate. A retail brand may be associated with one or more entities. Retail brands are defined in and validated against the Retail Brand file. See Working with Retail Brands (WRBD). This field displays on your screen only if system control value Use Collaborative Shipping Framework is set to Y. See Drop Ship Integration Values Screen (H20). Alphanumeric, 3 positions; required.

Change Entity Screen

To change: Enter 2 next to an entity code at the Work with Entities Screen to advance to the Change Entity screen. At this screen you can change anything but the entity code. See Create Entity Screen for field descriptions.

Display Entity Screen

To display: Enter 5 next to an entity at the Work with Entities Screen to advance to the Display Entity screen. You cannot change any information on this screen. See Create Entity Screen for field descriptions.

Work with Entity SCV Overrides Screen

Purpose: Use this screen to work with overrides to System Control file settings based on entity.

Note: Currently, only pricing values are available for override at the entity level.

How to display this screen: Enter 7 next toan entity at the Work with Entities Screen.

ACR0454 DISPLAY Work with Entity SCV Overrides 12/22/03 13:50:50 EZK Mail Order Entity : 1 AVIAN CREATIONS Op SCV App Grp Description-Value Active Type options, press Enter. 2=Change 5=Display B31 O/E PRI Pricing Values N F3=Exit F8=View history F12=Cancel F21=Print List

Field	Description
Entity	The entity you selected at the Work with Entities screen. Numeric, 3 positions; display-only.
Description	The description of the selected entity. Alphanumeric, 25 positions; display-only.
SCV	A number that identifies the system control value to the system. This is an internal code that programs reference when checking a specific system control value. Alphanumeric, 3 positions; optional.
App (Application area)	The application area (for example, Order Entry or O/E) to which this system control value belongs. Application areas are used to categorize similar control values, secured features, and menu options by functional area. Once an application area has been assigned to a control value, it cannot be changed. Alphanumeric, 3 positions; optional.
Grp (Application group)	The application group to which this system value relates. Application groups further define functions within an application area and are used to categorize similar control values, secured features, and menu options. Examples of application groups with the Order Entry application area are pricing (PRI) and tax. Alphanumeric, 3 positions; optional.
Description-value	The description of the system control value. Alphanumeric, 60 positions; display-only.
Active	This field indicates whether the Active override flag for the entity-level system control value has been set to Y. If you set this flag to Y, the system updates the Entity System Control Value file. Also, the entity-level settings will override your company-wide entries in the System Control file for any activity within this entity. Valid values are: Y = Entity-level settings override company-wide system control value settings. N = Entity-level settings are not in effect. Alphanumeric, 1 position; display-only.

Screen Option	Procedure
Change an entity-level system control value setting	Enter 2 next to system control value to advance to the Edit Pricing Values Screen.
Display an entity-level system control value setting	Enter 5 next to a system control value to advance to the Edit Pricing Values Screen.
View the history of changes to system control value overrides for this entity	Press F8 to advance to the Display All System Control Value History Screen. See Display System Control Value History Screen for a discussion of the System Control Value History file.

Edit Pricing Values Screen

Purpose: Use this screen to work with entity-level overrides to your company-wide pricing values in the System Control file. Pricing values control how the system determines item price in order entry and order maintenance.

How to display this screen: Enter 2 next to the Pricing Values system control value at the Work with Entity SCV Overrides Screen.

ACR0455 ENTER Edit Pricing Values 2/11/99 11:36:27 Sarah`s Joke Shop Entity . . . . . : 200 Application Code . . : O/E Active Override . . N (Y/N) Application Group . : PRI Best Way Pricing . . . . . . . . . . N (Y/N) Search Offers for Price . . . . . . N (Y/N) Offer price Sequence # . . . . . . . Quantity Break By SKU Sequence # . . Column Sequence # . . . . . . . . . Special By Source Sequence # . . . . Contract Sequence # . . . . . . . . Customer Discount Sequence # . . . . Coupon Item Sequence # . . . . . . . Price Table Sequence # . . . . . . . End of Order Pricing Options: Item Volume Discount . . . . . . . . N (Y/N) Quantity Break/Item . . . . . . . . N (Y/N) Price Codes . . . . . . . . . . . . N (Y/N) Price Tables . . . . . . . . . . . . N (Y/N) F3=Exit F12=Cancel

Note: Each of the pricing values are described in Installation Setting Up Order Entry Values.

Field	Description
Entity	The entity you selected at the Work with Entities screen. Numeric, 3 positions; display-only.
Application code	The application area (for example, Order Entry or O/E) to which this system control value belongs. Application areas are used to categorize similar control values, secured features, and menu options by functional area. Once an application area has been assigned to a control value, it cannot be changed. Alphanumeric, 3 positions; display-only.
Active override	If you set this flag to Y, the system updates the Entity System Control Value file. Also, the entity-level settings will override your company-wide entries in the System Control file for any activity within this entity. Valid values are: Y = Entity-level settings override company-wide system control value settings. N (default) = Entity-level settings are not in effect. Alphanumeric, 1 position; required.
Application group	The application group to which this system value relates. Application groups further define functions within an application area and are used to categorize similar control values, secured features, and menu options. Examples of application groups with the Order Entry application area are pricing (PRI) and tax. Alphanumeric, 3 positions; display-only.

Instructions:

1. Set the Active override flag to Y to have the entity-level pricing values override the company-wide settings.

2. Optionally, complete each of the pricing values. See Installation Setting Up Order Entry Values.

How the system determines how to price orders: When you enter an order, the system determines how to select prices at the time you complete the order header information, including the source code. The system checks the Active override setting for the entity associated with the division specified for this source code. If the Active override flag is set to Y, the system uses the entity-level pricing values to determine the price of each item on the order. If the Active override flag is set to N, the system uses the company-wide pricing levels defined in the System Control file.

Work with Entity Return Address Screen

Purpose: Use this screen to create or edit the entity address to print on return labels. The system uses this address only if your web storefront supports printing these labels for return authorizations when customers enter returns on the storefront. See the E-Commerce Interface for more information.

If there is no entity return address: The system uses the address you specify for the company at the Work with Company Return Address Screen if you do not define a return address for the entity associated with an order. An order is associated with an entity through the division assigned to the source code on the order header.

If there is no entity or company return address: If a return address is not specified for the entity associated with the order or for the company, the system uses the address for the Default Warehouse (A04).

How to display this screen: Enter 10 next to an entity at the Work with Entities Screen.

ACR0504 CHANGE Work with Entity Return Address 7/17/00 17:42:07 EZK Mail Order Entity . . . . . : 2 A DOG'S LIFE Name . . . . . . . A DOG'S LIFE Street Address . . 24 PRIME PARK WAY City/St/Postal Code NATICK MA 01760 Country . . . . . . USA Phone # . . . . . . F3=Exit F11=Delete F12=Cancel

Completing this screen: Enter the address to appear on return labels for use when customers enter returns through your web storefront. See the Work with Company Return Address Screen for field descriptions. To delete the return address, press F11.

Working with Entity Email Overrides

Purpose: Use this screen to review and work with order-related email notification overrides for an entity.

Note: Entity-level email overrides do not apply to purchase orders emailed to vendors.

Directory Address (“From” Email Address) Override at Entity Level

Note: The “from” address is the email address that appears to have generated the email, although it does not need to be an actual email address. For example, you could use a “from” address of customer_service@abccompany.com and include a note in your email template advising the customer not to reply to the email.

About the directory address: The “from” email address is normally the SMTP user ID and SMTP domain specified for the directory entry. For example, if the SMTP user ID is rkaplan, and the SMTP domain is commercialware.com, the “from” email address is rkaplan@commercialware.com. Provided you have sufficient authority, you can use the Work with Directory Entries screen, available by entering WRKDIRE at a command line, to review and work with directory entries. The Directory address at this screen should match the Address displayed at the Work with Directory Entries screen and entered at the Change Email Override Screen.

Note: The system does not confirm that the Directory address you enter at the Change Email Override Screen is valid.

Directory address hierarchy for order-related emails:

1. Entity and notification type: The system uses the email address for the directory address specified for the order-related email notification type and entity, if any; otherwise,

2. System control value for company: If the directory address at the email notification type/entity level is blank, the system uses the Confirmation Email Directory Address (I19) system control value; otherwise,

3. System default: If the directory address specified through the system control value is blank, but there is a directory entry with an address of EMAIL, the system uses the email address for this entry.

4. Otherwise, if there is no directory entry with an address of EMAIL, the system does not send an email notification.

Note:

• If the system finds a directory address that is invalid, rather than blank, at any point while going through this hierarchy, it uses the email address of the user who started the async jobs; however, if the system finds a user profile that is disabled, it advances to the next level in the hierarchy.

• The entity-level directory address does not apply to purchase order emails, since you cannot set up a purchase order email template override at the entity level.

• The “from” email address is not included in the Outbound Email XML Message (CWEmailOut), generated if the Use email API flag for the template is set to Y.

Varying the “from” email address: Using a different “from” email address based on entity for various notifications, such as the loyalty membership activation or deactivation notice, might be confusing to your customers if the same customers commonly place orders in multiple entities within your company. In this situation, the “from” email address on an activation or deactivation email might not match the entity where the customer places the majority of his or her orders.

For example, a customer might qualify for a loyalty membership based on orders placed in entity 1, and receive a loyalty activation notice using the “from” email address for this entity. Then the customer places an order in entity 2 that makes him eligible for a higher loyalty program. In this situation, it is possible for him to receive a deactivation notice for the first loyalty membership using the “from” email address from entity 1, and an activation notice for the second loyalty membership using the “from” email address from entity 2.

Note: Loyalty deactivation takes place only if the Evaluate Loyalty Eligibility within Qualifying Order (J34) system control value is set to N.

For more information: See Working with E-Mail Notification Templates (WEMT) for an overview on email notifications.

Important: The “from” email address is not included in the Outbound Email XML Message (CWEmailOut). See the discussion of the Outbound Email API for more information.

Email Template Override at Entity Level

You can override the template for an order-related email notification at the entity level. If there is any information entered for an order-related email notification at the entity level, the system uses the entity-level information when it generates the notification; otherwise, it uses the information at the company level, as set up through Working with E-Mail Notification Templates (WEMT). To set up a template override at the entity level, you use the Change Email Override Screen.

Note: You cannot set up an entity-level email template override for purchase order emails.

What does the template consist of? The email template can include:

• the “from” email override address

• the setting of the Use email API flag, described below

• the lines of text to include before and after any specific information that the system inserts into the email. For example, in the case of an order notification, the template consists of the text to include before and after order summary information such as items and dollar totals.

If you enter any entity-level text to include either before or after the item information, the system uses just the entity-level text rather than the company-level text. For example, if you have set up a company-level template that includes text both above and below the item information, but the entity-level template includes just the text above the items, the generated email notification includes just the entity-level text above the items; it does not include the company-level text below the items.

Defaulting the company-level template text: At the Change Email Override Screen, you can default any company-level template text by pressing F8. You can then edit the text as needed to make it appropriate for the specific entity. This feature is useful if the company-level text serves as a good starting point for the entity-level text. Alternatively, you can enter the entity-level text without deriving it from the company-level default.

Note: Once you default the company-level text and press Enter, the system overwrites the previously-entered entity-level text. To restore it, you need to enter the text again.

Use Email API setting: Order, shipment, return, soldout, stored value card, and backorder notifications have the option of generating the Outbound Email API rather than an actual email. Generating the XML message enables you to produce a reformatted HTML email and include additional promotional information. The system uses the entity-level setting of the Use Email API flag if there is also an entity-level template override. For example:

• If there is any entity-level text entered for the template and the Use Email API flag is set to Y: Generate the Outbound Email XML Message (CWEmailOut).

• If there is any entity-level text entered for the template and the Use Email API flag is set to N: Do not generate the Outbound Email XML Message (CWEmailOut), regardless of the setting of the Use Email API flag at the company level; generate an actual email.

• If there is no entity-level text: Use the setting of the Use Email API flag at the company level to determine whether to generate the Outbound Email XML Message (CWEmailOut); ignore the setting of this flag at the entity level.

Note: The system generates the Outbound Email XML Message (CWEmailOut) only if the system control value specifying the related email generation program is not blank. For example, in order to generate the order confirmation through the Outbound Email XML Message (CWEmailOut), make sure that the Order Acknowledgement Program (G50) is not blank.

See the Outbound Email API for more information.

Work with Entity Email Overrides Screen

How to display this screen: Enter 11 next to an entity at the Work with Entities Screen.

ACR0523 DISPLAY Work with Entity Email Overrides 5/25/05 16:32:11 EZK Mail Order Entity . : 1 AVIAN CREATIONS Directory Opt Type Address Type options, press Enter. 2=Change 5=Display Backorder 1st Notice EMAIL1 Backorder 2nd Notice Backorder Continue Notice C/C Credit Acknowledgment Gift Certificate Loyalty Activate Notice Loyalty Deactivate Notice Maintenance Success + F3=Exit F12=Cancel

Field	Description
Entity	The entity you selected at the Work with Entities Screen. The description of the entity displays to the right. Entity: numeric, 3 positions; display-only. Description: alphanumeric, 30 positions; display-only.
Type	The email notification type to use the “from” email address specified for the Directory address and the template text. Email notification types are: • Backorder 1st Notice • Backorder 2nd Notice • Backorder Continue Notice • C/C Credit Acknowledgment • Gift Certificate • Loyalty Activate Notice • Loyalty Deactivate Notice • Maintenance Success • Maintenance Failure • Order Confirmation • Return Confirmation • Shipment Confirmation • Stored Value Card Notification • Soldout Notification Note: With the exception of the purchase order email, all notification types are listed, regardless of whether you use the notification in this entity or in your company. Alphanumeric, 27 positions; display-only.
Directory address	The directory address associated with the “from” email address and template text to use for generated email notifications. The “from” email address is normally the SMTP user ID and SMTP domain specified for the directory entry. For example, if the SMTP user ID is rkaplan, and the SMTP domain is commercialware.com, the “from” email address is rkaplan@commercialware.com. Provided you have sufficient authority, you can use the Work with Directory Entries screen, available by entering WRKDIRE at a command line, to review and work with directory entries. Alphanumeric, 10 positions; optional.

Option	Procedure
Change the entity-level override of the “from” email address and/or template for an email notification type	Enter 2 next to an email notification type to advance to the Change Email Override Screen.
Display the entity-level override of the “from” email address and/or template for an email notification type	Enter 5 next to an email notification type to advance to the Display Email Override Screen.

Change Email Override Screen

Purpose: Use this screen to enter entity-level email override information. See Working with Entity Email Overrides for a discussion.

How to display this screen: Enter 2 next to an email notification type at the Work with Entity Email Overrides Screen.

ACR0524 CHANGE Change Email Override 5/25/05 16:36:59 Mail Order Company Entity. . . : 100 ENCORE ENTITY Directory address. . . Notice Type : Order Confirmation Use Email API (Y/N). . N Text To Print Above Items: Text To Print Below Items: F3=Exit F8=Default from Comp F12=Cancel

Field	Description
Directory address	The Directory address for the directory entry that is associated with the correct “from” email address. See Directory Address (“From” Email Address) Override at Entity Level for a discussion. Note: The system does not confirm that your entry represents a valid Directory address. If you enter a value here, and your entry here does not represent a valid directory address, the system uses the email address of the user who started the async jobs as the “from” address. Setting a directory address override works independently from the email template override. For example, you can override the directory address and not the template, or vice versa. Alphanumeric, 10 positions; optional.
Use email API	Indicates whether to generate the Outbound Email XML Message (CWEmailOut) rather than an actual email notification for notices generated for this entity. This XML message includes additional information that is not included in the standard email notice. You might choose to generate the XML message so that you can use the information to produce a reformatted HTML email that includes promotional material. Valid values are: Y = Generate the Outbound Email XML Message (CWEmailOut) rather than an actual email N = Generate the email notification rather than the outbound XML message Note: • The system uses the setting of this flag at the entity level only if there is also text entered for the email template at the entity level. Also, this option is available only for the order, shipment, return, stored value card, soldout, and backorder notification templates. • The system generates the Outbound Email XML Message (CWEmailOut) only if the system control value specifying the related email generation program is not blank. For example, in order to generate the order confirmation through the Outbound Email XML Message (CWEmailOut), make sure that the Order Acknowledgement Program (G50) is not blank. For more information: See Outbound Email API for an overview, and see Email Template Override at Entity Level for a discussion of when the system uses this setting as an override at the entity level. Alphanumeric, 1 position; optional.
Text to print above items	The standard text to appear in each email above the information specific to the order. See the Sample Notification. If you enter any information at the entity level, it overrides any information in the company-level template set up through Working with E-Mail Notification Templates (WEMT). Setting a directory address override works independently from the email template override. For example, you can override the directory address and not the template, or vice versa. Alphanumeric, ten 60-position lines; optional.
Text to print below items	The standard text to appear in each email below the information specific to the order. See the Sample Notification. If you enter any information at the entity level, it overrides any information in the company-level template set up through Working with E-Mail Notification Templates (WEMT). Note: If you enter entity-level text to include above or below the item information, the system includes just the entity-level text; it does not include the company-level text if the corresponding fields at the entity level are blank. Alphanumeric, three 60-position lines; optional.

Option

Procedure

Copy email template information from the company-level template for this email notification type

Press F8 to copy the text set up at the company level for this notification type through the Working with E-Mail Notification Templates (WEMT) option. Note: When you copy the text from the company-level template, it overrides any text currently entered at the entity level. If you then press Enter, the system overwrites the previous entity-level text. To restore the text, you need to enter it again.

Display Email Override Screen

Purpose: Enter 5 next to an email template at the Work with Entity Email Overrides Screen to review the overrides to the email template or “from” email address, if any. You cannot change any information on this screen.

See the Change Email Override Screen for field descriptions, and see Working with Entity Email Overrides for a discussion of entity-level overrides.