Issues Defaulting Contract Header Context Segment From Contract Type
(Doc ID 2945616.1)
Last updated on AUGUST 21, 2023
Applies to:
Oracle Fusion Enterprise Contracts Management Cloud Service - Version 11.13.23.01.0 and laterInformation in this document applies to any platform.
Symptoms
On : 11.13.23.01.0 version, Functional Setup Manager
ACTUAL BEHAVIOR
---------------
Issues Defaulting Contract Header Context Segment from Contract Type.
Following instructions here as a guideline, but modifying for the business purpose.
By using the task 'Manage Contract Descriptive Flexfields' and using the Default Type set to SQL there is a need to create a mapping between some element on the Contract or Contract Type and these Contexts. The application, however, does not allow to use parameters in the SQL code area.
EXPECTED BEHAVIOR
-----------------------
Assign context segments based on the Contract Type by providing the CHR_TYPE as a parameter
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
- Navigate to the task 'Manage Contract Descriptive Flexfields'.
- Select 'Contract Headers', edit.
- In the Context Segment section, for the Default Type LOV, select SQL.
- For the Default value write the SQL query with a where clause on the 'CHR_TYPE' field that uses a parameter.
- Notice that it is not possible to pass that parameter.
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |