Last updated on JUNE 10, 2013
Applies to:Oracle Fusion Subledger Accounting - Version 126.96.36.199.0 and later
Oracle Fusion Subledger Accounting Cloud Service - Version N/A and later
Information in this document applies to any platform.
Expected sources are unavailable while defining Subledger Accounting Rules. For example, user need out 'project' segment in the CoA. A segment rule is needed to ensure that for project '123', segment value '123' is used as project value in the accounting/ journal line. It does not look very logical to use a mapping set for this because user has to make a mapping line for each project i.e. for input 123 -> output 123, input 456 -> output 456 etc..
How to tackle this?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms