Distribution - JDE1 (MOSC)

MOSC Banner

E1 TMS - LTL Lookup Type 2

edited Feb 11, 2015 10:00AM in Distribution - JDE1 (MOSC) 3 commentsAnswered

I have a client that insists on creating point-to-point LTL rates by zip/postal code.  NOT range of zip codes but specific origin to single zip codes for lookup type 2.   I do NOT recommended this approach for future growth, maintenance and knowledge of the limit for Lookup type 2 to a maximum of 999 rows.  None of my other TMS clients have ever taken this approach.  What are some other limits and downside if this - origin to single zip code approach is taken that I can use to persuade the client from this approach?

Once lookup type 2 is established can an additional single zip code value be added to the lookup type definition successfully - such as when a new customer is created with a zip code not in the existing Lookup Type 2 definition?

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

E1 Distribution Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center