context sensitive descriptive flexfield setup for forecasts and forecastsets (doc id 90215.1)

Upload: gops989

Post on 06-Jul-2018

217 views

Category:

Documents


0 download

TRANSCRIPT

  • 8/17/2019 Context Sensitive Descriptive Flexfield Setup for Forecasts and ForecastSETS (Doc ID 90215.1)

    1/2

    Context Sensitive Descriptive Flexfield Setup For Forecasts And ForecastSETS (Doc ID 90215.1)

    Modified:  Apr 12, 2011 Type: PROBLEM

    Problem Description

    -------------------

    After setting up (enabling) the Forecast Set Descriptive Flexfield, you

    navigate to the Forecast form and find that both the Forecast Set and the

    Forecast Descriptive Flexfields (DFF) are the same. If data is entered in the

    Forecast Set Header Flexfield field, the same data populates the Forecast

    Flexfields. You want to have two (2) different fields to populate different

    data for the Forecast Set Header and the Forecast Detail.

    Solution Description

    --------------------

    1) In Inventory or System Administrator responsibility, navigate to

      Setup/Flexfields/Descriptive/Segments.

    2) Query MRP_FORECAST_DESIGNATORS.

    3) Unfreeze the Flexfield.

    4) In the Context Field Area:

      - Prompt: Is user-entered (anything you want) i.e., Forecast's DFF.

      - Default Value: Set as one of the Values entered below i.e., Forecast

    Set or Forecast.

      - Reference Field: Can be ignored. It is to reference any other field in

    the Form or Flexfield.

    5) In the Context Field Values Area:

      - Click on Global Data Elements and then the [Segments] button.

      - Ensure DISPLAY and ENABLED are both NOT CHECKED.

      - Close that form.

    6) In the Descriptive Segments Form, Under Global Data Elements, enter the

    following:

      - Name: Forecast Set

      - Description: Anything you Want ie.. Forecast Set DFF(Header)

      - Click on the [Segments] button.

      - Number: 1

      - Name: Forecast Set  - Window Prompt: Defaults to value in Name field.

      - Column: ATTRIBUTE1

      - Ensure that DISPLAY and ENABLED are both CHECKED.

      - Save and Close that Screen.

      - Once back at the Descriptive Flexfield Segments Form,

      - Ensure that the Enabled Checkbox is CHECKED for Forecast Set

    7) In the Descriptive Flexfield Segments Form, under Forecast Set, enter the

    following:

      - Name: Forecast

      - Description: Anything you Want ie.. Forecast DFF(Details)

      - Click on the [Segments] Button.

      - Number: 1

      - Name: Forecast

      - Window Prompt: Defaults to value in Name field.

      - Column: ATTRIBUTE2

      - Ensure that DISPLAY and ENABLED are both CHECKED.

      - Save and Close that Screen.

    8) In the Descriptive Flexfield Segments Form:

      - Ensure that the Enabled Checkbox is CHECKED for Forecast

      Note: If you wish, you can setup a Value Set for each context

    structure separately.

    9) In the Descriptive Flexfield Segments Form:

      - Save and close.

      - Check the Freeze Flexfield Checkbox.

      - Click the [Compile] Button.

    ment https://support.oracle.com/epmos/faces/showdoc?_adf.ctrl-state=

    4/22/2016

  • 8/17/2019 Context Sensitive Descriptive Flexfield Setup for Forecasts and ForecastSETS (Doc ID 90215.1)

    2/2

      - Navigate to the Forecast Form and try it.

    Problem Explanation

    -------------------

    There is only ONE Descriptive Flexfield (DFF) available for Forecast Sets and

    Forecast. This is because both the Forecast Set and Forecasts are defined and

    stored in ONE table. Unless the table has been configured for more than one

    Descriptive Flexfield, the only way to make this seem to be two (2) separate

    flexfields is to set them up using a Context Sensitive configuration available

    for flexfields in general. The setup above allows you to pick which field,

    Forecast Sets or Forecast, that will be populated in the proper place within

    the form.

    Didn't find what you are looking for?

    ment https://support.oracle.com/epmos/faces/showdoc?_adf.ctrl-state=

    4/22/2016