44 Set Up Preferences
This chapter contains these topics:
All preferences share standard preference information that applies to all of the preference types in a category. You enter this information for each preference in the header portion of the Preference Revisions form.
There are also fields that are unique to each preference where you enter specific preference information. You enter this information for each preference in the detail portion of the Preference Revisions form.
If you set up multiple preferences for a customer and item combination, you can specify a sequence number that the system uses to search the preferences to process the order.
| Topic | Description |
|---|---|
| Using the Profiles by Customer/Item form | You can perform the same setup tasks from the Profiles by Customer/Item form as you can from the Preference Profiles form. |
44.1 Entering Header Preference Information
From Sales Order Management (G42), choose hidden selection 27
From Sales Order Advanced & Technical Ops (G4231), choose Preference Profiles
All preferences share common fields, called key fields, where you enter standard preference information. You must enter this information for each preference in the header portion of the Preference Profiles Revisions form.
When entering header preference information, you can also specify a sequence number that the system uses to search for preference records. For example, to set up a preference for a customer and item combination and vary the preference by an additional key field, you need to sequence your preference records. If you set the sequence for a preference with Branch/Plant A at 1, the sequence for Branch/Plant B at 2, and all other branch/plants at 999, you can ensure that the system searches for the preferences for Branch/Plants A and B before using the preference that applies to all other branch/plants.
Consequently, you need to use care when sequencing preference records. If the preference that applies to all branch/plants has a sequence number of 1, the system will not find the more specific preferences for Branch/Plants A and B, because the system first finds the preference that applies to all branch/plants. If you set up sequence numbers in increments, you can insert new preferences at a later date.
To enter preference information
On Preference Profiles
-
Choose a preference.
-
To access the Preference Inquiry form, choose the Inquiry option.
-
On Preference Inquiry, access the Preference Revisions form.
Figure 44-2 Payment Terms screen with Preference Information
Description of "Figure 44-2 Payment Terms screen with Preference Information"
-
On the Preference Revisions form, complete one or more of the following fields:
-
Customer Number
-
Customer Group
-
Item Number
-
Item Group
-
Sequence Number
-
Preference Status
-
-
Complete the following fields, if available on the form:
-
Effective From
-
Effective Thru
-
Quantity From
-
Quantity Thru
-
Unit of Measure
-
-
Complete the steps to enter detail preference information described below.
| Field | Explanation |
|---|---|
| Preference Status | A value that states whether the preference is Active (1) or Inactive (2). The valid statuses are maintained in UDC table (40/PT). |
| Quantity From, Quantity Through and Unit of Measure | The quantity from and through at which a preference or price adjustment becomes valid. The unit of measure to be used in the preference search.
Form-specific information If you do not enter a quantity, the system uses 0. Use the Enable Effective Quantity (Y/N) field on Preference Master to activate or deactivate the display of these fields. |
| Effective From | The date on which a transaction, text message, contract, obligation, or preference becomes effective.
Form-specific information Leave this field blank if you want the preference to become effective today. Use the Enable Effective Dates (Y/N) field on Preference Master to activate or deactivate the display of this field. |
| Effective Thru | The date on which a transaction, text message, agreement, obligation, or preference has expired or been completed.
Form-specific information If you do not enter a date in this field, the system enters a date that you defined during system setup. If you want the preference in effect for an unlimited amount of time, leave this field blank and allow the system to enter the default. The system checks for the effective period during sales order processing. Use the Enable Effective Dates (Y/N) field on Preference Master to activate or deactivate the display of this field. |
| Sequence Number | A sequence or sort number that the system uses to process records in a user defined order.
Form-specific information Use this field when you have multiple preferences for the same customer/item combination, effective period, and quantity range. The sequence determines the order that the system searches for preference records with otherwise identical fields. The system searches records in ascending numerical order, that is, from lowest to highest. |
| Quantity Thru | The quantity at which a preference becomes invalid.
Form-specific information If you do not enter a quantity, the system enters a number defined during system setup. Use the Enable Effective Quantity (Y/N) field on Preference Master to activate or deactivate the display of this field. You must also enter the unit of measure for the quantity in the unmarked field next to Quantity Thru. If the preference is in effect for all quantities, leave the Quantity From and Thru fields blank. The system supplies the default minimum and maximum quantities. You must enter a valid unit of measure for the quantities. |
44.1.1 What You Should Know About
44.2 Entering Detail Preference Information
From Sales Order Management (G42), choose hidden selection 27
From Sales Order Advanced & Technical Ops (G4231), choose Preference Profiles
All preferences have unique fields where you enter specific preference information. You enter this information for each preference in the detail portion of the Preference Profile Revisions form. These specific preference fields are:
-
Search fields
-
Definitions fields
Search fields are marked with a greater than (>) sign next to the field name. The system uses these fields in the same way as it uses key fields. Each preference has search fields unique to its requirements. These fields are found in the detail portion of each preference's Preference Profiles Revisions form. Search fields are optional. You use these fields to further narrow the search criteria specified by key fields. For example, if you indicate that the search field called Branch/Plant should be used as additional selection criteria, the system selects sales orders that match the unique combination of customer, item, and branch/plant criteria.
Preference definition fields are the fields that the system uses to resolve the preferences. Each preference has one or more definition fields unique to its requirements. These fields are found in the detail portion of each preference's Preference Profiles Revisions form. Definition fields are required, although in some cases a valid value can be a blank. Typically, the system uses the values you input in these fields to override or add information on a sales order.
To enter detail preference information
After you enter header preference information, you can enter information that is specific to each preference in the detail portion of the screen under the '….Preference Information' heading.
On Preference Profiles
-
Choose a preference.
-
Access the Preference Inquiry form.
-
On the Preference Inquiry form, access the Preference Profile Revisions form.
Figure 44-4 Print Messages screen with Preference Information
Description of "Figure 44-4 Print Messages screen with Preference Information"
-
On the Preference Profile Revisions form, complete the specific preference information in the detail portion for each preference.
The following describes each preference in greater detail. The descriptions in this chapter are presented in alphabetical order.
44.2.1 Container Deposit/Rental Preference
Use the Container Deposit/Rental preference to specify three aspects of Container Management:
| Item | Description |
|---|---|
| Deposit or Rental for a Customer/Item | You can specify that a customer/item combination is billed for rentals or deposits on the containers. |
| Transaction or Summary Level Billing | You can specify that a customer/item combination is billed for container deposits on a transaction basis or on a summary period. You can specify summary periods over a given period (set up in the Invoice Cycle preference) for the empty container. |
| Override the G/L Offset from the Item Master | When you define a Container Deposit/Rental preference, Container Management uses the preference's G/L offset in the sales order it creates for container deposits and rentals. The system uses this G/L offset instead of that defined in the Item Master. This allows you to separate potential sales of empty containers from the actual deposits. |
-
Ensure that you create the G/L offset account for container deposits and rentals
44.2.2 Customer Currency Preference
Use the Customer Currency preference to assign a currency code to a customer number or to a customer group. Unlike other preferences, this preference does not include the item or item group, because the currency code must be the same for all items on an order.
This preference overrides the default currency code from Customer Master Information in the order header record. You must still include the customer currency in the Customer Master Information. This is because accounts receivable processing does not check preferences. Instead, it uses currency from each order detail line.
The header currency code applies to all detail lines in the order. Therefore, when you rely solely on the Customer Currency preference to set the order's currency code, you can have only one currency code per order.
The Customer Currency preference can be defined for a specific selling branch/plant or for all branch/plants. For example, if your company sells jet fuel to international airlines, the order might be in French francs from a depot in France and British pounds from a depot in the United Kingdom.
-
Activate foreign currency to process this preference
-
Set up exchange rates for the foreign currency to the base currency
44.2.3 Delivery Date Preference
You can use the Delivery Date preference to have the system calculate the delivery date based on the number of days that your items are in transit.
A sales order has several dates that the system uses to determine a delivery date:
| Date | Description |
|---|---|
| Order date | The date that you enter the order into the system or the date that you want on the order. |
| Requested date | The date the customer requests to receive the order. You can enter a single date for the entire order or several dates for individual detail lines. |
| Pick date | The date that warehouse personnel picks the items from inventory. |
| Ship date | The date that you promise to ship the order. You can enter dates for individual detail lines. |
| Delivery date | The date that you tell the customer that the order will arrive. |
The system calculates the ship and delivery dates under the following circumstances:
-
Preferences are activated.
-
One or more of the Branch/Plant, Route Code, Mode of Transport, Priority Code, and Carrier Number fields match the key fields of the preference.
Except for the Mode of Transport field, the fields display in the order detail from either the Inventory Commitment preference or the Customer Billing Instructions. If they are blank, no match is necessary for the system to calculate dates.
-
Work Day Calendar is set up to calculate planned shutdowns, holidays, and weekends.
When you set up this preference, you must define:
-
The minimum number of days between order entry and scheduled load date
-
The number of days that goods are in transit between load and delivery
-
Verify that the priority code information for the customer is set up in Customer Billing Instructions
44.2.3.1 Example: Applying Dates for Products
You must set up the Work Day calendar to calculate load dates for bulk product orders. The system then adds the delivery lead time to the load date.
The following examples are based on the November 1998 Route Work Day calendar and assume that four lag days and five lead time transit days are specified in the preference.
| Action | Result |
|---|---|
| Order taker manually enters a load date | The program enters the promised date in advance:
The system calculates the promised date by adding the lead time transit days to the load date. |
| Order taker manually enters a promised date | The program back schedules the load date. The system subtracts the lead time transit days from the promised date to calculate the load date:
A warning appears if the ship date is prior to today. |
| Order taker leaves Promised Date and Load Date fields blank | The program calculates the promised date by adding the lag days to the lead time transit days from the preference to the sales order date:
Promised Date Calculated: Saturday 11/14/17 |
| System calculates a load date that is less than the sales order entry date | The program schedules the promised date in advance by placing the order date plus the lag time into the load date and then adding the lead time to the load for the promised date:
The system recalculates to indicate the actual load and promise dates:
Promised Date Calculated: Tuesday 11/17/17 |
44.2.4 Document Distribution Preference
Use the Document Distribution preference to define how many extra copies of a delivery document you want printed and who you want to the receive copies. For a customer and item combination, you define:
-
The trip depot
-
The document code of the document to be printed
-
The person who will receive each copy
-
The number of copies to print
You use this preference to control printing of delivery tickets, priced delivery tickets, and invoices. You can also use this preference to print custom documents (those not programmed by JD Edwards World), such as certificates of analysis.
The system applies Document Distribution preferences either during the Bulk/Packaged Load Confirm process or at Preprint Delivery Documents.
The system allows you to specify this preference with multiple line entries. In this case, you should include the sequence number with the unique preference information in place of the standard information fields.
44.2.4.1 Example: Document Distribution Preference
As defined in the sample form above, the system applies the following preference setup whenever customer "500" orders item "UNL".
| Shipped By | Shipped From | Documents | Number of Copies | To Whom | Where |
|---|---|---|---|---|---|
| Truck | Depot1 | Bulk Delivery Ticket | 1 copy | Address 500 | Printer attached to JDEHOLD |
| Rail | 419 | Bulk Invoice | 2 copies | Address 500 | Printer attached to JD5779754 |
See Also:
-
JD Edwards World Load and Delivery Management Guide for information on the Bulk/Packaged Load Confirm Process and the Preprint Delivery Documents process.
44.2.5 Document Set Preference
Use the Document Set preference to identify the set of delivery documents for a particular customer and item combination. The Document Set name is linked to the Document Set Assignment form where the individual document sets are assigned.
If you are using delivery documents, you must define at least one Document Set preference. How you define the preference depends on types of products, such as bulk or lubes, or whether your customer is foreign or domestic. You can also vary the preference by branch/plant.
The system applies Document Set preferences when documents print during the following stages:
-
Bulk/Packaged Load Confirm
-
Preprint Delivery Documents
At the end of each stage, you can view or change the document set information on the Document Selection form.
44.2.5.1 Example: Document Set Preference
Generally, companies create separate Document Set preferences for bulk and packaged products. This example summarizes an efficient method to set up two Document Set preferences so that the appropriate document sets are shipped with each product.
-
Create an item group for bulk products.
-
Assign a Document Set preference to the bulk item group.
-
Set up another Document Set preference for all items and all customers by leaving the Customer, Customer Group, Item, and Item Group fields blank.
-
Set up the preference hierarchy for the Document Set (ECS) preference so that:
-
Item Group/All Addresses is first in the hierarchy.
-
All Items/All Addresses is second in the hierarchy.
-
When the system processes the Document Set preference during Load Confirm, the preference hierarchy causes the system to first search for an Item Group preference. If the item in the sales order line is a bulk item and you have assigned it to the item group, the system uses the document set for bulk products. Otherwise, the system uses the default values and issues the document set for all items and all customers. In this case, the system uses the document set for packaged products because you have not assigned packaged products to the bulk product item group.
See Also:
-
Creating Document Sets and Creating a Document Set Preference in the JD Edwards World Load and Delivery Management Guide for information on creating document set codes.
44.2.6 End Use Preference
Use the End Use preference as system criteria for applying price adjustments. You can also use this preference to set up a paid or free status for stock that is commingled for duty.
End use refers to the customer's end use of the product. For example, you might be required to charge different prices for the same item depending on its end use. A product specific to aviation might have a special duty applied in which the amount of duty might depend on end use (in this case, different duty amounts that are based on different airports).
End Use and Duty Status are key fields. You can create different End Use preferences to assign values for various customer and item combinations. You can then assign the applicable End Use and Duty Status field values for each customer and item combination to suit your business needs.
44.2.7 Freight Preference
Use the Freight preference to link the sales order detail line to a freight table. The system uses freight tables to determine freight charges based on distance, zone, or fixed fee. The system also uses freight tables to determine whether the freight is billable, payable, or both. Use the Freight preference to specify a freight table for a customer/customer group and item/dispatch group.
The Freight preference differs from other preferences in that it does not have an Item Group selection. Instead, it uses the same dispatch groups that are used by the Load and Delivery Management system to group products for dispatch.
The Freight preference works in conjunction with freight tables. You define your Freight preferences based on your distance-based, zone-based, or fixed-fee-based freight tables. You can specify one or more freight tables, for example, if you charge a customer a fixed fee and an additional distance-based fee for the same item or dispatch group.
You must also designate whether the freight charge is billable to customers, payable to contractors, or both. Branch/Plant and Mode of Transport are optional search fields.
The system applies the Freight preferences when you run the Customer Freight Calculator and Supplier Freight Calculator batch programs to determine billable and payable freight charges. Normally, this is part of end-of-day processing. However, billable freight charges can also be calculated prior to printing delivery documents.
-
Before setting up Freight preferences, determine the following:
-
Whether freight is billable to the customer, payable to a contractor, or both
-
If freight will be calculated by each delivery to a customer, by each sales detail line, or for each trip by a contractor
-
If the distance-based, zone-based, fixed-fee-based, or a combination of freight tables will be used
-
If the tariff code will be used for any of the freight tables in this preference
-
See Also:
-
Creating Freight Tables and How Does the System Calculate Freight? in the JD Edwards World Load and Delivery Management Guide.
44.2.8 Grade and Potency Preference
Use the Grade and Potency preference to select inventory for a customer that is based on a specific grade or potency range for an item. You can set up base pricing by an item's grade or potency. You could use this preference if a customer requires a grade/potency range that differs from the standard range that you define for an item through item branch/plant information.
Note:
Because bulk products cannot be selected by grade or potency or load confirmed by lot, you should use this preference only for packaged products.The Grade and Potency preference works in conjunction with the Inventory Commitment preference and the commitment method to determine the availability of products. The preference causes the system to ensure that available quantities are within a customer's specified grade/potency parameters.
In addition, the system uses the value that you enter in the Days Expired Before field of the Grade and Potency preference to determine if the expiration date is within the customer's allowable days. This ensures that the availability of product will be the quantity of the grades or potencies that the customer allows that are within the expiration date.
You can only use the Grade and Potency preference if either the Potency Control or the Grade Control is activated for the item. This is done on the Plant Manufacturing Data form that is part of the Item Branch/Plant Information. You typically use this preference only if a customer requires a grade or potency range that differs from the standard ranges that are set up in the Item Branch/Plant Information.
You cannot specify both grade and potency for the same item. However, when you create the Grade and Potency preference, the system displays both the Grade and Potency fields. This display occurs regardless of the status of the Potency Control and Grade Control setting on the Plant Manufacturing Data form.
The system does not check the status of the activation settings in the Plant Manufacturing Data form when you create a Grade and Potency preference. Therefore, you will not be prevented from entering values into the From Grade, Thru Grade, From Potency, or Thru Potency fields. You could also enter data in both fields. In either case, the system will not apply preference information that conflicts with activation settings or data entry rules.
44.2.8.1 Example: Applying a Grade and Potency Preference for Grades
If a customer preference is set to accept grades A and B only, the system checks for product availability of those grades only. For example:
-
Location 1 has 500 quantity available of Grade A stock.
-
Location 2 has 1000 quantity available of Grade B stock.
-
Location 3 has 2000 quantity available of Grade C stock.
Only Locations 1 and 2 have product available for this customer. The quantity available is 1500 because this customer does not accept grade C. The system performs availability checking using the values of the Grade and Potency fields. The system eliminates any grades or potencies that are not within the range.
44.2.8.2 Example: Applying a Grade and Potency Preference for Potency
When you set up a potency preference, you define the allowable percentage of active ingredients for an item. The From Potency field should contain a smaller percentage than the Thru Potency field. For example:
-
From Potency: 60.000
-
Thru Potency: 75.000
The system commits inventory for this customer and item combination only for lots when the potency is greater or equal to 60 percent and less than or equal to 75 percent.
See Also:
-
Section 37.5, "Defining Base Prices" for information on pricing by grade or potency.
44.2.9 Inventory Commitment Preference
Use the Inventory Commitment preference to:
-
Specify that each order line be filled from one or more branch/plants based on customer/customer group or item/item group
-
Specify the branch/plants from where you want products shipped
-
Determine the percentage of the order to be filled from each branch/plant
-
Specify the mode of transport and carrier information in the sales detail line
If you use this preference to specify the branch/plants from where you want products shipped, use the Sequence Number and Branch/Plant fields to control the product's Ship From location. You can then sequence the preferences to establish a priority order.
If you use this preference to determine the percentage of the order to be filled from each branch/plant, use preference sequences to establish an order. If you are unable to fill the order from any branch, the system creates a backorder on the branch/plant with the lowest sequence number. Normally, only packaged products, not bulk products, are backordered.
The system applies this preference during sales order entry or when you hard-commit items. You can view the specified source branch/plant in the Branch/Plant field in the fold area of an order detail line. This preference also allows you to populate the route code, mode of transportation, and carrier number into the sales order.
44.2.9.1 Example: Inventory Commitment Preference
The Percent To Fill field provides you with the flexibility to fill an order line from one or more branch/plants. The Inventory Commitment preferences work in conjunction with the system's normal checking that is done for quantity available, and adds a check on all branches that are defined in the preference.
As each branch is checked, the order will be shipped from any one branch that can fill the entire order. Depending upon the number in the Percent To Fill field, a portion of the order line can be filled from one or more branch/plants.
Percent-To-Fill Value and Related System Actions
If the percent-to-fill value is zero percent, the system performs normal processing. The system performs no checking for the quantity on hand, and regardless of the quantity on hand, it is shipped to fill the order.
If the percent-to-fill value is between 1 and 99 percent, the system requires that any branch must be able to fill the percentage that is specified. If the branch can fulfill the percentage, the quantity available is shipped and the remainder is transferred to the next branch. The system checks each branch to determine if the quantity can be shipped.
If you specify a percent-to-fill value of 100 percent for each of several branch/plants, an order can only be filled from a single branch/plant that has sufficient quantity to fill the order. If no branch/plant has sufficient quantity to fill 100 percent of the order, the system will ship the available quantity from the first preference branch/plant and backorder the remainder.
If the percent to fill value is 100 percent, the system requires that the branch must be able to ship the entire quantity. This prevents shipping from multiple branches, but allows the system to check all branches to determine if the entire quantity can be shipped. If you specify a percent-to-fill value of 100% for each of several branch/plants, an order can only be filled from a single branch/plant that has sufficient quantity to fill the order. If no branch/plant has sufficient quantity to fill 100 percent of the order, the order is backordered or partially shipped from the first preference.
The following table shows an example of an order that is placed for a quantity of 500.
| Branch/Plant: quantity available | Percent-to-fill as set up on preference | Minimum order quantity available | Result |
|---|---|---|---|
| Branch/Plant A: 100 | 50percent | 200 | Do not ship from this branch because the available branch/plant quantity is less than the minimum order quantity. |
| Branch/Plant B: 400 | 80percent | 400 | Ship 400 from this branch. |
| Branch/Plant C: 96 | 95percent | 95 | Ship 96 from this branch because the available branch/plant quantity is at least 95% of the order balance of 100. |
The system backorders the remaining quantity of 4 to Branch/Plant B.
-
Verify that the sales order entry preference options for inventory commitment are blank
When a sales order is entered, the first commitment preference branch that is actually used is defaulted into the detail line. If a branch is manually entered in the detail branch field on the sales order header and it is different from the header branch, the detail branch entered will default into every detail line. Since all the detail lines have effectively had their branch manually added, the inventory commitment preference will not change the detail branch on any of the order lines. Manually changing the branch sets the Preference Commitment Indicator (SDSO06) on the Sales Order Detail file (F4211). This flag is normally set to signify that an order line has been run through the inventory commitment preference process ensuring that it is only run once.
When an order quantity has been backordered, the quantity must remain at the branch since the order line cannot be run through the inventory commitment preference. However, when a future committed quantity is released, the order line may be run through the inventory commitment preference.
| Topic | Description |
|---|---|
| Activating the Inventory Commitment preference | You must activate the Inventory Commitment preference through processing option 71 in the Sales Order Entry program (P4211). |
| Working with kits and configured items | The Inventory Commitment preference does not function with kits or configured items. For kits you can achieve this functionality by setting the desired branch/plant in the fold of the components in the bill of materials. |
| Programs using the Inventory commitment preference | The following programs use this preference:
|
44.2.10 Invoice Cycle Preference
You can set up customer billing schedules, such as weekly or monthly, that are based on customer and item combinations. For example, you might have a customer who receives weekly shipments but prefers to receive only one invoice at the end of each month.
By setting up an invoice cycle preference for a customer, you create an interim step between shipment confirmation and invoicing that the system uses to determine when to print invoices.
After you confirm the shipment of orders, the system processes them through the Schedule Invoice Cycle program. This program accesses the invoice cycle preference information and, using the Invoice Cycle Calculation Rule program, calculates the scheduled invoice date using the following information:
-
Invoice cycle
-
Invoice calculation rules
-
Invoice date ranges
If the scheduled invoice date is prior to or equal to the system date, the system does not create any deferred entries. However, if the scheduled invoice date is later than the system date, the system creates deferred entries for COGS, revenue, and the unbilled accounts receivable during sales update. Then, during journal entry, these amounts are allocated into the appropriate accounts.
Example: Invoice Cycle Preference
In the following example, an item with a price of 100.00, a cost of 50.00, and an invoice cycle date that is later than the current date creates the following entries:
Account entries based on invoice cycle date:
-
Deferred COGS = 50.00
-
Unbilled accounts receivable = 100.00
-
Inventory = (50.00)
When you run sales update, the system creates offsetting entries for any entries that are deferred, as well as the usual journal entries for accounts receivable, COGS, and revenue:
Account entries created during sales update:
-
Accounts receivable = 100.00
-
Deferred revenue = 100.00
-
COGS = 50.00
-
Revenue = (100.00)
-
Unbilled accounts receivable = (100.00)
See Also:
-
Chapter 30, "Work with Invoice Cycles" for complete information about setting up the Schedule Invoice Cycle.
44.2.11 Line of Business Preference
Use this preference to specify a customer's line of business, such as aviation. Line of business preferences can be set for customer and item combinations.
Your business can derive useful data for sales analysis when you define line of business preferences. You can write your own World Writer reports to produce reports by line of business. Price adjustments can be based on line of business using order detail groups.
This preference is applied during sales order entry and is used to update the Line of Business field (LOB) on the Sales Order Detail file (F4211). Unless you activate ECS this preference is the only way to update the Line of Business field.
44.2.12 Next Order Status Preference
Use the Next Order Status preference to skip or insert processing steps after sales order entry. The processing flow is determined by the order activity rules. The Next Order Status preference overrides the next step in the order activity rules. You should only use this preference to change the steps after you enter an order.
For example, you might want to send an Electronic Data Interchange (EDI) order acknowledgement for a specific customer and item combination. For another customer, you might want to skip the trip maintenance and load confirmation steps defined in the order activity rules.
The order activity rules determine which steps you can skip. For example, to skip from Enter Sales Order (Status 520) to another status step, you must choose one of the Other Allowed status codes. You could not skip from Enter Sales Order to Cycle Billing (Status 580) because the order activity rules stipulate that the next status can only be 562 or 564.
Caution:
During preference setup, the system does not prohibit you from entering invalid activity/status codes. However, during sales order processing, the system highlights fields on the sales order to indicate that you have entered an invalid activity/status code.-
Determine the order activity rules and the steps that can be skipped in the process flow.
-
Verify that the order activity rules and the Other Allowed status information are valid. The Other Allowed codes for order activity rules can vary by company. Anyone with authority to set up a Next Order Status preference should have the rules and information available.
44.2.13 Order Preparation Days Preference
You can set up information about the amount of time that it takes to prepare an order for shipping in the Order Preparations Days preference. This helps you to accurately determine the number of days that it takes to deliver your sales orders from the date that the customer places the order. The Order Days preference is most often used in conjunction with the Delivery Days Preference.
Order preparation days are the number of days that it takes to pick and pack the items on the sales order, prior to shipping. The system uses the priority code that you set up for your customer in the Customer Billing Instructions to determine the amount of preparation time. However, you can override the priority code for a single order on Order Detail Information during order entry.
When you enter an order, the system uses information in the Order Preparation Days preference and first attempts to obtain dates by back scheduling. Back scheduling involves calculating the pick, ship, and delivery dates for an order, starting with the delivery date and working backwards.
If the pick date is before the current date, the system forwards schedules starting with the order date to obtain pick, ship, and delivery dates.
This preference is applied during sales order entry when it enables the Promised Ship Date (PDDJ) on the order line to be automatically calculated.
44.2.13.1 Preference Detail Fields
The driver fields for this preference (Branch/Plant, Route Code, Mode of Transport, Carrier Number, and Priority Code) must match the sales order values or be blank to have the Order Preparation Days preference take effect. These fields default into the sales order detail from either the Inventory Commitment preference or the Customer Billing Instructions.
The Edit for Workday field determines whether and how to use the Workday Calendar.
44.2.14 Payment Terms Preference
Use the Payment Terms preference to identify payment terms and instruments for specific customer and item combinations. The system applies payment terms only at the item detail level. For any items that are not included in this preference, the system applies the payment terms from the customer master information at the order level. The preference defaults the Payment Terms (PTC) and/or the Payment Instrument (RYIN) into the Sales Order Detail file (F4211).
44.2.15 Price Adjustment Schedule Preference
Use the Price Adjustment Schedule preference in conjunction with the Advanced Pricing system. You can use this preference to assign a different price adjustment schedule for items sold to a specific customer. You can also use this preference to create penalty schedules for agreements with business partners.
This preference overrides the default schedule from Customer Billing Instructions. The system applies this preference during sales order entry.
44.2.16 Pricing Unit of Measure Preference
Use the Pricing Unit of Measure preference for the following:
-
To override the Pricing Unit of Measure field (UOM4) defaulted into sales detail line.
The system completes the sales detail line based on information in the Item Master. You might use this preference when your company has negotiated a price with a customer in a specific unit of measure. You then need to set up pricing for the customer and item in that unit of measure and enter a Pricing Unit of Measure preference to ensure that the system automatically adds the pricing unit of measure to the order. The pricing unit of measure can differ from the transaction unit of measure and can vary by branch/plant.
-
To override the Sales Price Based On Date field (in system constants)
The Sales Price Based On Date field determines how the system updates the Price Effective Date field in the sales order detail tables
-
To calculate the Price at Ambient/Standard
The system uses this flag at the time of delivery confirmation to re-extend the price using the standard or ambient temperature, depending on which value you choose.
-
Set the sales price retrieval unit of measure in system constants. See Section 49.3, "Defining System Constants."
-
Confirm that a base price record exists for the pricing unit of measure to be entered in this preference.
See Also:
44.2.17 Print Messages Preference
Use the Print Messages preference to choose the messages you want to automatically print on documents for a particular customer and item combination. This preference provides several key fields to use in conjunction with the customer/item combination.
The system applies this preference when a document is printed, not during order entry. The Print Messages preference does not override any other messages you set up in Customer Billing Instructions and Item Branch/Plant information.
Unlike other preferences, the system applies print messages cumulatively. The system selects all messages that match the customer and item selection criteria and prints them on documents. Print messages are also cumulative for all levels in the preference hierarchy. For example, if you choose three hierarchy levels and set up multiple preferences at each hierarchy level, the system applies all print messages at all hierarchy levels that match the customer and item combination you enter on an order.
Note:
Leaving any of the key fields blank indicates you want to specify all valid values for that field. For example, a blank in the Business Unit field causes the system to apply the Print Messages preference to all business units.-
You must create print messages before you can use this preference
44.2.18 Product Allocation Preference
Use the Product Allocation preference to restrict the amount of an item or item group that a customer or customer group can purchase. For example, use this preference if the demand for a product exceeds the supply or if government regulations restrict limits for certain products.
You can set quantity limits to define the quantity that a customer or customer group is allowed to purchase or the quantity of each item or item group that is allowed to be sold. The system checks for allocation limits before it checks availability. Product allocation indicates how product is distributed among customers. Product availability indicates how much of any product is at any branch/plant location.
Product allocations can be set up as either:
-
A fixed number of item units
-
A percentage of the available product
If the order quantity exceeds allocated quantity, a warning message appears when you enter a sales order. At that time, you can put the order on hold or reduce order quantity to the allowable or available quantity.
Each time you place an order for an allocated product, the quantity ordered during the effective date range accumulates toward the allocation limit. The system updates the Quantity Sold field each time you enter an order. This field shows the quantity that was ordered at the time the allocation went into effect. When you change or cancel an order, the system subtracts the quantity from the running total. The system applies the product allocation preference before checking availability.
Caution:
You should disable the Quantity From and Quantity Thru fields on Preference Master for the Product Allocation preference. This enables the system to automatically perform unit of measure conversions for this preference.When you enter an order that exceeds the Product Allocation preference information, you can access the Product Allocation Information window to adjust the information.
-
You must identify the product allocation hold code in the sales order entry processing options if both of the following apply:
-
You create Product Allocation preferences
-
You want to place orders on hold if a customer's order exceeds their allocation
-
| Topic | Description |
|---|---|
| Working with kits and configured items | The Product Allocation preference does not function for kits and configured items. |
| Setting the allocation method | If you choose Allocation Method 1, enter the Quantity Limit and leave Percentage of Pool and Quantity Pool Size fields blank.
If you choose Allocation Method 2, enter the Percentage of Pool and Quantity Pool Size fields. The system will then automatically calculate the Quantity Limit. |
| Quantity sold and balance calculations | The balance column on the Product Allocation inquiry form updates with the quantity available to purchase if one of the following apply:
If you place an order on hold because it exceeds the allocated amount, the balance will show as a negative amount for either Allocation Method 1 or 2. |
| Quantity limit exceeded in order entry | When the quantity limit is exceeded during Sales Order Entry (P4211), the item will be highlighted and a warning message is issued. Press F7 to display the warning and option 2 (referenced program) will bring up the Allocation Information window. This window shows the Item Number, Line Number, Quantity Balance, Quantity Ordered, Quantity over the limit the order will cause, Quantity Limit and Quantity Sold. You have a choice of two options:
|
| Processing options on Sales Order Entry | Processing option 28 on P4211 is where you set the specific hold code to be used for product allocation holds. |
| Programs using the Product Allocation preference | The following programs use this preference:
|
44.2.19 Quality Management Preference
Use a Quality Management preference to either request or require that a test be run and certain quality standards be met for a particular customer and item combination.
The system applies the preference when confirming a bulk load by trip. If a test is requested or required, you can either exit to On Vehicle Sampling/Quality or return to the menu to enter test results.
-
Set up test specifications, which require the system to run a test or set a quality standard. See Set Up the Vehicle Master in the JD Edwards World Load and Delivery Management Guide.
44.2.20 Revenue Cost Center Preference
Use the Revenue Cost Center preference to recognize revenue for a business unit that is different from the central business unit. This preference allows you to override the default accounting branch/plant cost center from the Branch/Plant or Detail Branch/Plant fields. The Revenue Cost Center preference does not apply to interbranch sales.
Figure 44-7 Revenue Cost Center Preference Process
Description of "Figure 44-7 Revenue Cost Center Preference Process"
Additionally, you can use this preference for a salesperson that might be located at the revenue business unit that is associated with the preference.
Example: Revenue Cost Center Preference
This example summarizes how to set up the Revenue Cost Center preference to ship items from multiple sites while posting revenue to a single site.
-
Create a Southwest customer group for an item.
-
Set up a Revenue Business Unit preference.
-
Set the preference hierarchy for the Revenue Business Unit preference at the intersection of Ship to Customer Group and Item Number.
-
In the Business Unit field on the Revenue Business Unit form, enter a branch/plant.
-
In the Revenue Business Unit field on the Revenue Business Unit form, enter a different branch/plant than you entered in the Business Unit field.
-
Set the Update Customer Sales processing option to blank or 3 to specify the revenue business unit.
| Topic | Description |
|---|---|
| Sales Update (P42800) | Sales Update (P42800) will accommodate this Revenue Cost Center preference processing. For the revenue journal entry to reflect the Revenue Cost Center specified in the preference, the following setup must exist:
|
| Non stock items | The Revenue Cost Center preference does not work for sales lines with non stock items. |
| Header Business Unit field (EMCU) in F4211 | During Sales Order Entry (P4211) the preference value is populated into EMCU on the Sales Order Detail line. |
| Programs using the Revenue Cost Center preference | The following programs use this preference:
|
44.2.21 Sales Commission Preference
Use the Sales Commission preference to set up sales personnel and commission rates based on customer and item combinations. Line of Business and Branch/Plant are additional search fields for this preference. You can assign different commission preferences for various customer and item combinations based on the line of business and branch/plant values.
The system normally provides default values from Customer Billing Instructions for the sales commission fields in the sales order header. If the billing instructions Rate fields are blank for the Commission Royalty Information, the system can provide default values for the commission rate. Normally, the system provides default values for each line on the sales order. The preference overrides the header information at the line level.
-
You must set up all salespeople in the address book and on the Commission/Royalty Information form before you can enter them on a preference. See Chapter 54, "Set Up Commission Information."
44.2.22 User Defined Price Code Preferences
Use the User Defined Price Code preferences to define your own codes and use them for your unique pricing needs.
Price codes can be used in the Advanced Pricing system to define price adjustments. They can also be used for your reporting requirements.
For example, you might use a price code for temporary pricing. You define a price code to identify order lines that need to be repriced when commodity prices are published for a specific period. If you don't want the price code to be manually changed during order entry, use the Price Code 3 preference.
See Also:
| Topic | Description |
|---|---|
| Sales Order Detail File (F4211) | This preference is used to default the price codes into the Sales Order Detail file. When the preference is used the Price Code 1 (UPC1), Price Code 2 (UPC2) and Price Code 3 (UPC3) fields will be updated onto the Sales Order Detail file depending upon which preference was employed. |
| Programs using the User Defined Code Pricing preferences | The following programs use this preference:
|
44.2.23 End Use Preference
The End Use preference is used to default the end use and/or duty status fields into the Sales Order Detail (F4211) file. It can be used as a reporting code or as a parameter for pricing adjustments. The End Use (EUSE) and/or Duty Status (DTYS) fields will be updated on the Sales Order Detail file.
| Topic | Description |
|---|---|
| Programs using the End Use preference | The following programs use this preference:
|