Your company has been working with Fusion in development for some time and has decided to move to production. After configuring part of the production setup data, your supervisor decides to import…

Question

Options

• AIndustry in production will remain unchanged.
• BIndustry In production will be updated with values from development.
• CTax in production will remain unchanged.
• DTax In production will be deleted.
• ETerritory will be synchronized between development and production.
• FTerritory in production will be updated with the values from development.
• GTerritory in production will remain unchanged.

• A
  12% (5)
• B
  74% (31)
• D
  7% (3)
• F
  5% (2)
• G
  2% (1)

Explanation

In the target application instance, the setup import process will insert all new data from the source configuration package that does not already exist and update any existing data with changes from the source. Setup data that exists in the target instance but not in source will remain unchanged. Note:Almost all Oracle Fusion application implementations require moving functional setup data from one instance into another at various points in the lifecycle of the applications. For example, one of the typical cases in any enterprise application implementation is to first implement in a development or test application instance and then deploy to a production application instance after thorough testing. Setup Data: Explained

No community discussion yet for this question.