R12.2, Strange Date Format of "Beginning Request Start Time" and "Ending Request Start Time" of "Signon Audit Concurrent Requests" (Doc ID 3033195.1)

Last updated on JULY 25, 2024

Applies to:

Symptoms

Problem

When submitting concurrent program "Signon Audit Concurrent Requests"（FNDSCSRC）, in R12.1.3 the report output is correct. However, in R12.2.12 using the same parameters, data filtering and sort, the concurrent program report output might not be correct ("Beginning Request Start Time"=01-MAY-24, "Ending Request Start Time" =30-MAR-24, DD-MON-RR format).

Specify from 01-MAY-24 to 30-MAR-24 (DD-MON-RR) in R12.2.12

Sample of its output below, the report includes the data of June 2024, sort function does not work correctly.

 In R12.2.12, input 20240501 and 202405030 (RRRRMMDD) the program works fine.

Input 24-APR-19（RR-MON-DD）and it also did fine in customer environments.

Steps

System Administrator > Concurrent > Requests

Select "Signon Audit Concurrent Requests" and input "Beginning Request Start Time" and "Ending Request Start Time" on Concurrent Parameter Form.

Additional Information

System Administrator > Concurrent > Program > Definition

Select "Signon Audit Concurrent Requests", click Parameters, Description of "Beginning Request Start Time" and "Ending Request Start Time" says "Rudimentary date value set.

Does not validate format" but the validation accepts any characters less than 8 length.

Other Sign on Audit Programs would have the same kind of issue.

For example,  can specify "2024 JUN" or "Jun 1st" in date parameter.

 but the concurrent requests complete with Error.

Changes

 Upgrade R12.1.3 to R12.2.12

Cause

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