or the transaction requesting an override action.

the the details of

Detail

Unit

32 chars

Bug - 35635687: The heading levels are incorrect on Review Budget Entries page.

Bug - 35332804: Budget segment selection throws an error when creating a control budget in screen reader mode.

Bug - 35635623: Vertical spacing on Budget Transfer Form is insufficient for Justification field

Bug - 35531169: Table links navigate to incorrect links unless the corresponding row is selected.

Bug - 35634564: Budget account table actions are not available on Edit Budget Account Group page when redered in screen reader mode.

Bug - 35634623: Budget account group funds availability percentage values reset on save when in screen reader mode.

Bug - 35332724: IDs are not unique on Review Budget Entry Details page.

Technically not feasible to implement. Two different technologies, the BO - Tree and tree version coming from two different sources per page.

FND_VS_VALUES_B & TL: Dimension Members

Display Name Plural or Label PluralUse "DisplayNameResource"

For the BO fields : Reuse the strings that are defined in the classic EO attribute (identified by label  property on the EO )

If the utility can keep

Needs to be Converted

If the utility can keep

dimensionmember name (segment value code)hierarchy i.e., tree version (including the faux hierarchy)

simulate

Dimension

Based on the cube-based unique members name, it is not always possible

[Intercompany]@[Intercompany Level 30 Code]|[0000]

Changes made via FND UIs will not be reflected in GL Balances AV

New combination of COA and Calendar should be used.

Create single tree and tree version for AV from Upload Chart of Accounts FSM task using RI sheet

using RI sheet

Maintaining sort order while updating Tree Versions

Manage Primary/Secondary Ledgers

Yes, parity can be achieved

Accounted Currency  Currency Currency/Currency type implemented in AVEntered CurrencyCurrency TypeCurrency/Currency type implemented in AV

Language aliases are not supported

Modeling Scenarios

add to FRC task drawer

Self Serviceview  published reportsProfessionalall  ?

Generate Allocations (Ess )

after accounting configuration is successful.

FND/Applcore UI's for hierarchy Creation (once the AV is created) and Maintenance will not be supported at all for this analytic view solution for hierarchy maintenance (change management). Only either Rapid Implementation solution or FBDI Hierarchy Maintenance solution will be supported for hierarchy creation and maintenance. ( Specific UI Ref which is not supported: Manage Account Hierarchies page or the Manage Trees and Trees Versions page)

Create General Ledger Balances Cube

Journal Posting

You can use the same revenue ChartField combination to fund multiple expenditures and the revenue method can be different for each association. The only requirement is that the sum of the revenue percentages cannot exceed 100 percent for any given revenue ChartField combination.

Enter the ChartField values and budget period that designate the expenditure budget whose available budget balance is increased by the associated revenue budget on the same line. You can enter the same expenditure budget more than once if you want more than one revenue budget to increase its available budget balance.

Lower Limit for Revenues as % of Current Budget (RIB)

92534-8 Retention Invoice:  92534-8 Retention Amount:$76338.00Location:Marina Point HOAVendor:Varsity PaintingAccount:Union Bank OperatingPay By:CheckPay Date:On Final ApprovalStatus:CAM ApprovalLast Change:Change:RejectedBy:Gail GayerDate:Oct 08, 2021Internal Notes:Reject - needs BOD approval please. GGLine Items:97820Miscellaneous Repairs & Maintenance$76338.00 Marina Point HOA Varsity Painting $76,338.00 97820-Miscellaneous Repairs & Maintenance ($76338.00) 09/30/21   10/08/2021 3:51 PM CheckUnion Bank Operating

XCC_BI_INVLD_DS_SBT_SBN

GL_BUDGET_CURRENCY_INVALID

XCC_BI_PS_CLOSED

XCC_BI_BCE_FAILED

XCC_BI_NO_CB_MATCHES

XCC_BI_BCCID_CREATION_FAILED

TRANSACTION_TYPE_CODE/SOURCE_ACTION_CODE

SBT, SB, DS, Scenario

XCC_BUDGET_INTERFACE(single period)

WCAG 2.1 - 2.5.2 Pointer Cancellation (Level A): For functionality that can be operated using a single pointer, at least one of the following is true:No Down-Event: The down-event of the pointer is not used to execute any part of the function;Abort or Undo: Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion;Up Reversal: The up-event reverses any outcome of the preceding down-event;Essential: Completing the function on the down-event is essential.Note 1: Functions that emulate a keyboard or numeric keypad key press are considered essential. Note 2: This requirement applies to web content that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).HighUnderstanding 2.5.2The product was tested for (select as appropriate):When an operation uses a single pointer, the down-event of the pointer is not used to execute any part of the functionWhen an operation uses a single pointer, completion of the function is on the up-event, and a mechanism is available to abort the function before completion or undo the function after completionWhen an operation uses a single pointer, the up-event reverses any outcome of the preceding down-eventThere are no single pointer operations Tool: Manual test Method: Verify that when an operation uses a single pointer at least one of the following is true:The down-event of the pointer is not used to execute any part of the functionCompletion of the function is on the up-event, and a mechanism is available to abort the function before completion or undo the function after completionThe up-event reverses any outcome of the preceding down-event

PassORFail - bug#ORN/A

Budgetary Control Dashboard: Budget Monitor

Check any CB is not in "In use" status (Incompatibile status) from the list (xcc_refresh_tree_history)

Check any CB is not in "In use" status (Incompatibile status) from the list (xcc_refresh_tree_history)

If any CB using the tree version and which is not 'PERMANENTLY_CLOSED','NOT_READY_FOR_USE','DEFINITION_INCOMPLETE'

Explanation and Pros / Cons Analysis of Existing vs. New Approaches

no XCC Balances for the impacted CBs period range

Now with this new enhancement, since Refresh program will detect tree changes that do not require recalc we can programmatically bring down the CBs only when recalculation is required.

Suggested Change

Fail - Bug ?????? Ledger, a client-side LOV field, has missing labelNon-Accessibility Bug ?????? - Ledger, a client-side LOV field, displays Ledger ID instead of Ledger Name  Result ( X )

WCAG 2.1 - 2.5.3 Label in Name (Level A): For user interface components with labels that include text or images of text, the name contains the text that is presented visually. Note: A best practice is to have the text of the label at the start of the name.HighUnderstanding 2.5.3The product has been tested for (select as appropriate):User interface components that include text or images of text and have a label, have a name that contains the text that is presented visually.There are no user interface components labeled with text or images of text. Tool:  Form tool from the Oracle Accessibility Toolbar - OATB Method: Label/Forms tool on the Oracle Accessibility Toolbar - OATBUse the Form tool from the Oracle Accessibility Toolbar - OATB to ensure controls have the same label in the Form Helper window as the visually associated label in the application page

WCAG 2.1 - 1.4.12 Text Spacing (Level AA): In content implemented using markup languages that support the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property:Line height (line spacing) to at least 1.5 times the font size;Spacing following paragraphs to at least 2 times the font size;Letter spacing (tracking) to at least 0.12 times the font size;Word spacing to at least 0.16 times the font size.Exception: Human languages and scripts that do not make use of one or more of these text style properties in written text can conform using only the properties that exist for that combination of language and script.MediumUnderstanding 1.4.12The product was tested for:When the following attributes and no others are modified there is no loss in functionality or content:Line height (line spacing) to 1.5 times the font sizeSpacing following paragraphs to 2 times the font sizeLetter spacing (tracking) to at 0.12 times the font sizeWord spacing to 0.16 times the font size Tool: Text Spacing tool on the Oracle Accessibility Toolbar - OATB Method: The Text Spacing tool on the Oracle Accessibility Toolbar - OATB changes the following four font attributesLine height (line spacing) to 1.5 times the font sizeSpacing following paragraphs to 2 times the font sizeLetter spacing (tracking) to at 0.12 times the font sizeWord spacing to 0.16 times the font sizeWhen changing only the above criteria (and no others) verify that there is no loss of functionality. In some cases (primarily FA) it will be necessary to navigate away from and back to the tested page via the application’s navigation for the page to adjust to the text spacing.

WCAG 2.1 - 1.4.10 Reflow (Level AA): Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for:Vertical scrolling content at a width equivalent to 320 CSS pixels;Horizontal scrolling content at a height equivalent to 256 CSS pixels.Except for parts of the content which require two-dimensional layout for usage or meaning.Note 1: 320 CSS pixels is equivalent to a starting viewport width of 1280 CSS pixels wide at 400% zoom. For web content which are designed to scroll horizontally (e.g. with vertical text), the 256 CSS pixels is equivalent to a starting viewport height of 1024px at 400% zoom.Note 2: Examples of content which require two-dimensional layout are images, maps, diagrams, video, games, presentations, data tables, and interfaces where it is necessary to keep toolbars in view while manipulating content.MediumUnderstanding 1.4.10The product was tested for (select as applicable):Text information reflows so that only one direction of scrolling is required while at 400% zoom.An alternative mobile user interface is available and is accessed from the main application.Content that requires two-dimensional layout only presents scroll bars in the component used to present the two-dimensional content.Tool: Reflow tool on the Oracle Accessibility Toolbar - OATB Method: The Reflow tool on the Oracle Accessibility Toolbar Enhancements Tab - OATB changes the following browser attributes. 1280x1024 aspect ratio400% zoomEnsure that content is presented without loss of information or functionality.Tool: Manual & Browser function Method: When testing on a desktop, on a screen with vertical scrolling, set content at a width equivalent to 320 CSS pixels, and horizontal scrolling content at a height equivalent to 256 CSS pixels, or the equivalent starting viewport height of 1024px at 400% zoom. There are many ways to control the width and height of the view port of the user agent, the most common approach is to use responsive design mode of the user agent.NOTE: As of February 2020, mobile browsers lack support for magnified reflow, and cannot be used for testing at this time.

WCAG 2.1 - 1.3.4 Orientation (Level AA): Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential.Note: Examples where a particular display orientation may be essential are a bank check, a piano application, slides for a projector or television, or virtual reality content where binary display orientation is not applicable.MediumUnderstanding 1.3.4The product was tested for (select as applicable):Text is displayed in both device orientations without loss of functionality or visibility of the text.A fixed display orientation is required for essential functionality. Tool:  Manual & Browser function Method: When testing in the browser, turn on the simulator. When testing with a mobile device, flip the device. Test that content does not restrict its view and operation to a single display orientation, such as portrait or landscape.

Method: The Form tool on the Oracle Accessibility Toolbar - OATB displays all form elements and the associated labels on a page. Use this button and verify whether all controls on the page are listed and are appropriately mapped with a label describing the purpose of the associated field. Also manually verify if any other content that requires user input has the appropriate label or instruction.

Instead of relying on setup, hard-code the filtering logic to not load revenue account types into XCC (they are loaded to General Ledger though)

Actual transaction amounts for revenue budgets may need to be recorded in an "Actual Revenue" bucket, separated from the Commitment, Obligation, Other Consumption, and Expenditure buckets.*** subject to technical decision ***

Carried From 20C:GL Mandate - CSSVS - Verify VFRAP Changes in 20CGL changes in 20CProduct Teams Impact Analysis and UptakeGL FDD RO CSSVSJimNew Info as of 20D:CSSVS is obsolete (not to exposed to any customers other than BofA, not even UCLA). What is in the pipeline (undetermined release perhaps after 20D) is to includes CSSVS + RW vs. RO access for BofA.In theory, if and when there is a customer who needs CSSVS and/or RW vs RO access, budget import (BC or GL) could ignore RO access. But it can add messiness to the already messy SVS in budget import.If and when RW vs RO access is implemented, we have to pass the parameter value in our API call. Tej (GL) confirms that if we don't uptake, we get RW + RO access (i.e., DEV work is not needed if we do not observe RO access).Jim (unless we have QA): Sanity regression testing is needed that even if RO vs RW policies are implemented, budget can access from both RO + RW policies

Simplify Budget Import IVGL/XCC out of sync detect/restore (no longer needed)Impact on Hyperion integration (not EPMCloud) FINXCC-683 - How to handle GL cube go out of synch in REST API case Open FINXCC-385 - Impact on Existing EPM Init Budget Integration Closed JimHandling all account types by flipping signage of budget amounts before passing on to GLWhether XCC will store credit account balances in the first cut - TBDBHC> "GL/XCC out of sync detect/restore" is no longer needed because Adj REST API will call GL Cube Load API in synchronous manner.BHC> Not clear what is the impact for existing Hyperion integration other than what we completed in 20C.No deliverables

WCAG 2.1 - 1.4.11 Non-text Contrast (Level AA): The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent color(s):User Interface Components: Visual information required to identify user interface components and states, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author;Graphical Objects: Parts of graphics required to understand the content, except when a particular presentation of graphics is essential to the information being conveyed.HighUnderstanding 1.4.11The product was tested for:Non-text items have a contrast ratio of at least 3:1 Tool: Eye dropper testing tool such as TPG Colour Contrast Anaylser,  WebAIM Contrast Checker or the Firefox tool ('Grab a color from the page' in the Developer Tools). Method: Manually inspect for graphic content and user component graphics (used to convey states and boundaries) that are difficult to see, then use the eye dropper tests to evaluate the contrast and ensure that graphic content and user components have a 3:1 contrast ratio with their background and/or adjacent content.

WCAG 2.1 - 1.3.5 Identify Input Purpose (Level AA): The purpose of each input field collecting information about the user can be programmatically determined when:The input field serves a purpose identified in the Input Purposes for User Interface Components section; andThe content is implemented using technologies with support for identifying the expected meaning for form input data.MediumUnderstanding 1.3.5The product was tested for (select as applicable):Text fields which collect information about the user contain the appropriate autocomplete content attribute.There are no text fields that collect information about the user. Tool: Label/Forms tool on the Oracle Accessibility Toolbar - OATB Method: Label/Forms tool on the Oracle Accessibility Toolbar - OATBThe Label/Form tool from the Oracle Accessibility Toolbar - OATB lists Form controls on the page.  Use this tool to verify that an input that collects information about the user has the appropriate input purpose.   Ensure this by confirming the value in the Input Purpose column is appropriate.  The w3 has provided a list of common input purposes Input Purposes for User Interface Components section.

WCAG 2.1 - 2.5.4 Motion Actuation (Level A):  Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation, except when:Supported Interface: The motion is used to operate functionality through an accessibility supported interface;Essential: The motion is essential for the function and doing so would invalidate the activity.HighUnderstanding 2.5.4The product was tested for (select as appropriate):Functionality that is operated by device motion or user motion can also be operated by user interface componentsResponding to the motion can be disabled, except when the motion is used to operate functionality through an accessibility supported interface OR the motion is essential for the function.There are no functions that require motion of the device. Tool: Manual test Method: Verify that:Functionality that can be operated by device motion or user motion can also be operated by user interface componentsResponding to the motion can be disabled to prevent accidental actuation, except when the motion is used to operate functionality through an accessibility supported interface OR the motion is essential for the function and doing so would invalidate the activity.

WCAG 2.1 - 2.5.1 Pointer Gestures (Level A): All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.Note: This requirement applies to web content that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).HighUnderstanding 2.5.1The product was tested for (select as appropriate):Multipoint or path-based gesture actions can be completed using a different input modality.The multipoint or path-based gesture actions are essential.There are no multipoint or path-based gesture actions. Tool: Manual test Method: If the product has multipoint or path-based gestures, ensure the task can be done with another input modality. The only exception is if it's essential (such as a signature).

WCAG 2.1 - 2.1.4 Character Key Shortcuts (Level A): If a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then at least one of the following is true:Turn off: A mechanism is available to turn the shortcut off;Remap: A mechanism is available to remap the shortcut to use one or more non-printable keyboard characters (e.g. Ctrl, Alt, etc);Active only on focus: The keyboard shortcut for a user interface component is only active when that component has focus.MediumUnderstanding 2.1.4The product was tested for (select as appropriate):Single character keyboard shortcuts can be turned off.Single character keyboard shortcuts can be remapped.Single character keyboard shortcuts are only active when that component has focus.There are no single character keyboard shortcuts. Tools: Manual test Method: Verify that shortcut keys which use only a single letter (including upper- and lower-case letters), punctuation, number, or symbol can do at least one of the following:The user can turn off the shortcutThe user can remap the shortcutThe shortcut is active for the component and only when that component has focus