E1: 41F: PCW10 Shows Local Size Range Only By User Instead of By Customer (Doc ID 2194044.1)

Last updated on OCTOBER 17, 2016

Applies to:

JD Edwards EnterpriseOne Apparel Management - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

EnterpriseOne 9.2

Style Matrix form PCW03 has been defined with some blank and some "EU" Localization Country Codes in the LCTR field. These are UK and EU sizes for shoes. When the LCTR field is blank, this is intended to mean that UK sizes are the default. EU is defined for European sizes.

The problem is that you can only get those alternative shoe sizes to appear in Sales Order Entry on the PCW10 Matrix Entry form IF that Localization Code is affixed to the User signed on to JD Edwards (JDE) EnterpriseOne. This is not realistic for Customer Services where the preference of the Customer has NOTHING to do with the JDE user. The JDE User may take an order from a UK Customer and a German Customer in the same period. The UK Customer requires the UK Size options. The German needs the European Size options. It is unrealistic to require that Customer Services require a dedicated sales order entry person for every region of the world by Size. The request is to map the LCTR field to the Customer, not the User.

The proposal is that mapping is done in the Customer Address Book (P01012) in the same way that the UDC 41F/00 uses "SPLITC" to map an Address Book Category Code for the quantity splits. Please insert a new value (for example "LCLSZ") which your clients can then map to a Customer Address Book Category Code. The PCW10 may well need another Processing Option allowing the mapping to be by Ship To or Sold To. There may need to be an override on the screen so that the Customer Service Representative can switch off this localization while the customer is on the phone if that specific customer requests, say, a US Size range for an apparel item. If there is no Localization code for that Customer the system then reverts back to the User Profile setting.

This is a significant and functional gap as localization is dependent upon the Customer, not the User, not the other way around.

Business Impact:
The problem prevents customers from being able to enter Sales Orders in the size ranges preference of the Customer. The Customer Service Representative would need to have two system logons: one for UK and another for EU. They would then ask which preference the Customer has and make the Customer wait while they log out and in again to make the Customer preference for local size active via the User Preference. This is not practical.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms