End Use Basic Preference Profile (P40304/P4210/P42101)

Purpose
Details
 General Information
 Setup (Menu G4231)
 Sales Order Entry Example
 Advanced Pricing Example

Purpose

 This document outlines the steps required to set up and apply the End Use basic preference (Preference Type 04) at Sales Order Entry.

Details

General Information

The End Use preference is used to input 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 system will search through the preference hierarchy until a match is found. The End Use EUSE) and/or Duty Status (DTYS) fields in the Sales Order Detail file (F4211) are updated by this preference.

End Use (Preference Type 04)

Setup (Menu G4231)

1. On menu G4231, select Preference Master (P40070). Inquire on the preference type ‘04’ and take the Row Exit to Preference Hierarchy (P40073).

1

3

For further information regarding Hierarchy set up please view document Preference Hierarchy Functionality for Advanced Pricing (P40073, P4074, P4071, P4072, G4231112 )

2. To add the preference, the user can either take the Row Exit to Profiles (in Preference Master), or go directly to Work with Preference Master (P40304):

5

Note: The fields eligible for input in the header section are dependent on the hierarchy setup for this preference type.


To populate the End Use field, a valid value needs to be setup in UDC Table 40/EU.

7

Populate the Duty Status field with a valid UDC 40/DS value.

9

Complete the required fields with the Preference Status (this needs to be 1 in order to be considered active) and the Effective and Expired Date.

11

13

3. In a version of Preference Process Options (R40400), make sure that the Customer Currency preference is activated by populating a “1”:

15

17

4. Once the preference record is created, Sales Order Entry (P4210) needs to have activated the preference profile so the proper value can be retrieved. In the Preference Tab of the Sales Order Entry (P4210) processing options, make sure Processing Option #1 is populated with a value of 1:

19

5. In the Versions Tab, make sure that the proper version of Preference Process Options (R40400) is populated in the Processing Option #6:

21

Sales Order Entry Example

1. At sales order entry, the preference will be applied and the End Use and/or Duty Status fields will be populated.

23

Advanced Pricing Example

Prerequisites:

• End Use Basic Preference is set up.
• The user should have an understanding of Advanced Pricing on how to set up the pricing based on the business requirement. In this example only part of the set up will be displayed. For further advanced pricing documentation view the information center: Information Center: Using JD Edwards EnterpriseOne Advanced Pricing Product.

1. Order detail group (P4092) setup:

25

Note: In this example both the End Use and Duty Status have been set up, so the adjustment will have both values and the sales order must have the matching values in order to apply the adjustment.

2. Adjustment Detail (P4071) set up:

27

The basic preference for End Use has been set up to populate the End Use field with TRK and the Duty Status field with ‘2’. If the adjustment had a Duty Status field with ‘1’ then the adjustment will not apply to the sales order. However in this example the adjustment will locate the End Use and Duty Status fields within the SO detail (F4211) and if the fields are populate with TRK and 2 then the adjustment will apply.

Sales order example:

1. Enter a Sales order where the basic preference is activated in the processing options:

29

2. Go to the Price history and see that the adjustment is applied:

31

Click OK and save the order.

Note: The End Use and Duty Status field are not price sensitive fields, so if a user goes in and manually changes the values the advanced pricing engine is not recalled. See document id: E1: 45: Advanced Pricing FAQ (P4070/P4071/P4072/R42750) (Doc ID 1366505.1). Question #4 in the General section for a list of price sensitive fields. If any pricing calls to recalculate the price occur (i.e R42950 or a change of the price sensitive field), this change will remove the adjustment and if no adjustment meets the new requirement, no adjustment will be applied. See the example below.

1. Example of the Duty Status changed from ‘2’ to ‘1’:

33

2. Run the R42950 to update the price

35

Note: The Unit Price has been changed.

3. Check the Price History of the Sales order-Adjustment has been removed.

37