Manufacturing - JDE1 (MOSC)

MOSC Banner

Wrong Actual Units CLUN in Production Cost F3102 with issues/completions decimal precision past two-

edited Sep 13, 2017 1:04PM in Manufacturing - JDE1 (MOSC) 7 commentsAnswered ✓

I am encouraged to see some action on F3102.CLUN in https://support.oracle.com/epmos/faces/BugDisplay?parent=DOCUMENT&sourceId=2027619.1&id=21346793 as this has been a known issue for some time.  We learned to always use primary UOM to avoid it.

However, this does not fix the basic problem reported in Xe, 8.9, 8.12, and 9.0 (and I'm sure is also in 9.1) where the business functions which update CLUN only write two-decimals precision when the base file carries four-decimals precision (e.g. 1.2345 issue/completion is truncated to 1.23).  Since this field drives virtually all actual manufacturing accounting reporting functionality, this is a critical miss which causes incorrect material variances on every work order processed.  I run into it all the time because we issue many components to four-decimal precision and also produce some bulk finished goods to the same (not just

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 Manufacturing 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