My Oracle Support Banner

Cannot Use Source Value Directly In Mapping Set Or Account Rule (Doc ID 2021266.1)

Last updated on DECEMBER 11, 2023

Applies to:

Oracle Fusion Subledger Accounting - Version and later
Oracle Fusion Project Costing Cloud Service - Version and later
Information in this document applies to any platform.


User cannot use source value directly in Mapping Set or Account Rule. In Project Tasks, they did setup for Task Descriptive Flexfield Attribute1 and the account number is stored there. In SLA, they use the Task Descriptive Flexfield Attribute1 as a source value. There's no setup where they can make the field itself as an output value for the account segment. They need to map individual values to a value for the chart of accounts account segment. Basically, the value from the Task Descriptive Flexfield Attribute1 should just be copied into Account Segment of COA, that's the need. Is that possible?


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.