Working with Valid Intersections in Forms

Data source type: Oracle Planning and Budgeting Cloud

See also:

Example 7-3

  1. Open a form.

    The form renders with member selections as specified in the form definition, adhering to your access rights for dimensions, and applies valid intersection groups with the most recently used as current selections.

  2. Verify that the form is enabled for valid intersections by looking for the <Clear Selection> option at the bottom of a Page drop-down list.
  3. Enter and submit data in writable cells at valid intersections.

    In Figure 7-8, with the member 420:Sales East selected for the Entity dimension, cells for each product are writable. The cells for P_TP1:Computer Equipment and P_TP2:Computer Accessories are not writable as these cells roll up the total of the data in the product cells.

    Figure 7-8 Form with Writable Cells, No Invalid Intersections


    Shows a form with no invalid intersections; cells for each product are writable. Cells for product category totals are not writable.

Example 7-3 Working with Valid Intersections in Forms

  • Similar to the examples shown in Working with Valid Intersections in Page Drop-down Lists, when the 410:International Sales member is selected in the Entity dimension, the Product dimension members, P_260:Game, P_270:Camera, and P_280:Television are not available for editing. In Figure 7-9, cells at those intersections are signified as not editable by #Missing.

    Other cells in the form are editable and considered valid intersections.

    Figure 7-9 Form Showing Non-Editable Cells for Three Products


    The 410:International Sales member is selected in the Entity dimension The Product dimension members, P_260:Game, P_270:Camera, and P_280:Television are not available for editing. Those cells are signified as not editable by #Missing.
  • Again, similar to the examples shown in Working with Valid Intersections in Page Drop-down Lists, when the 421:Sales NorthEast member is selected in the Entity dimension, the Product dimension members, P_220:Software Suite and P_250:Network Card are not available for editing. In Figure 7-9, cells at those intersections are signified as not editable by #Missing.

    Other cells in the form are editable and considered valid intersections.

    Figure 7-10 Form Showing Non-Editable Cells for Two Products


    The 421:Sales NorthEast member is selected in the Entity dimension. The Product dimension members, P_220:Software Suite and P_250:Network Card are not available for editing. Those cells are signified as not editable by #Missing.