Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Cost Management - EBS (MOSC)

Cost Manager updating potentially unmatched flag = 'Y' in CRRL table for few SO.

Oct 9, 2015 9:22AM edited Oct 17, 2015 10:00AM in Cost Management - EBS (MOSC) 2 commentsAnswered

Hi All,

Could you please explain what role Cost Manager plays in updating the potentially unmatched flag in the CRRL table for records which

are not yet COGS Recognized.

Initially for every SO issue, a record is inserted in CRRL table with potentially unmatched flag = 'U'.

Later when processed by Generate COGS events, this flag is changed to NULL on successful completion.

We are observing in our scenario that Cost Manager is updating the potentially unmatched flag to 'Y' for few SO's

with potentially unmatched flag = 'U' preventing them from getting COGS Recognized.

Based on the record status, I understand that (Courtesy: -> Metalink search)

0

Howdy, Stranger!

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

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

Category Leaderboard

Top contributors this month