E1: 49: Working with Route Entry (P4950) Prevent Default Branch Plant from Populating MCU Field

(Doc ID 2383446.1)

Last updated on MAY 31, 2018

Applies to:

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

Symptoms

When adding routes, if the user has a default BP (set in P400951), this BP value defaults into the P4950/F4950 MCU field, regardless of the Origin and Destination entered. When the user does NOT have a default BP, the P4950/F4950 field remains blank.

Where the client’s route uses the Origin Address and either the Destination Address or the Destination Country, the MCU value is not required. As some users have a default branch in the P400951, and others do not, browsing the F4950 records is confusing - some records have the MCU populated and others do not.

Requesting that the user creating the route in P4950 either be given the option to indicate when routes are / are not to be based on the MCU, possibly via a processing option….or just modify P4950 so that the user’s MCU does not default - allowing it to be manually entered when required, so that it has a deliberately entered value when needed. This would ensure that the F4950 MCU contains deliberately specified data and makes sense when reviewing the records.

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