General Ledger - EBS (MOSC)

MOSC Banner

Journal Import errors out with signal 11

Hi There!

We RANDOMLY started getting Signal 11 error on Journal Imports. Prior to getting Signal 11, Journal Import process used to Complete with Warning which allowed us to see which account code combination was causing a problem (with status: EF04) which allowed user to make a correction in the front end thru GL responsibilty.

Has anyone experienced the similar issue? We have been on R12.2.7 since 2019 and up-to-date on our patches.

Looks like Oracle has a solution to this which is setting Profile "Flexfeilds: Validate On Server" @ Site level to YES.

I am trying to find out why we never had SIgnal11 error on a Journal Import and all of a sudden started seeing the issue randomly.

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

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center