My Oracle Support Banner

Create Autoadjustments (ARXSUBAA.FMB) not ignoring "MO: Default Operating Unit" and throws error "APP-AR-11203: GL date, DD-MON-YY, is not in an open or future-enterable period." (Doc ID 2700490.1)

Last updated on NOVEMBER 20, 2020

Applies to:

Oracle Receivables - Version 12.0.0 and later
Information in this document applies to any platform.


While Creating Autoadjustments giving below error.

APP-AR-11203: GL date, DD-MON-YY is not in an open or future-enterable period

The issue can be reproduced at will with the following steps:

1) Assign MO: Security Profile 'All Operating Unit Profile' which has OU's "XXXX" and "YYYY".

2) Assign MO: Default Operating Unit "YYYY".

3) Verify the period "JAN-12" is closed for "YYYY".

4) Verify the period "JAN-12" is Open for "XXXX".

5) Go to "Create Autoadjustment" form. Here by default OU "YYYY" stamped.

Receivables responsibility: Control---> Adjustments---> Create--> Autoadjustments

6) Select the period "JAN-12" GL Date "30-JAN-2012", getting error "APP-AR-11203: GL date, 30-JAN-12, is not in an open or future-enterableperiod."

This is fine since the JAN-12 period is closed for "YYYY", Hence above error occurring.

7) Now change the Operating Unit to "XXXX" in same Create Autoadjustment form and select period "JAN-12" GL Date "30-JAN-2012" getting same above error "APP-AR-11203: GL date, 30-JAN-12, is not in an open or future-enterable period."

This is error not expected since the JAN-12 period is Open for "XXXX" OU.


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
 1. Bug Summary
 2. Fixed Files
 3. Recommended Patches
 4. Solution Steps
 Still Have Questions?

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