Inventory Management - EBS (MOSC)

MOSC Banner

Impact of changing cache_size of move orders sequence

edited Jul 28, 2011 9:06PM in Inventory Management - EBS (MOSC) 2 commentsAnswered
 

We have a problem in production where some times teh move order # generated is not always incremented by 1 - we have instances where sudddnley the next number is about 900-1000 more than the last number generated.This obviously was due to the cache_size parameter associated with the move order sequence MTL_TXN_REQUEST_HEADERS_S.We are changing that from 1000 to 0 .However is there any negative impact of this change?

Thanks

Rahul

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

EBS Inventory Mgmt 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