You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Preventing FAH from using Key Flexfield Default Value

in Subledger Accounting & Accounting Hub 3 comments

Summary:

FAH using Key Flexfield Default instead of transactions going to an "invalid" status

Content (please ensure you mask any confidential information):

@Gergana Radoutcheva-Oracle @Neil Ramsay-Oracle

How do we prevent FAH from leveraging the default segment value specified in the Key Flexfield Structure Instances for GL? If a value is not found in the mapping set we want to the transaction to go to an invalid status so that it can be reviewed. As of now it is going to the default value(R9999999) when it shouldn't, which is making reconciliation difficult. We are not using any of the suspense accounting mapping approaches discussed in this document

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!