9 About Requests
In Oracle Enterprise Data Management Cloud, all changes to data are made by using requests. Requests can be user-generated or system-generated by using subscriptions, and they can occur across hierarchies within a single application or across applications depending on how you structure the view in which the request is made. These changes to data are organized into request items. A request item is a group of change actions for a specific node. Requests also enable you to visualize changes before you commit them.
Videos
| Your Goal | Watch This Video |
|---|---|
|
Learn more about using requests to make changes to data. |
|
Change actions that can be performed in requests are:
- Add, insert, move, reorder, remove, and delete nodes
- Add and insert top nodes
- Update properties
There are three ways to make changes to data in Oracle Enterprise Data Management Cloud:
- Interactively (manual changes to viewpoints). For example, in Oracle Enterprise Data Management Cloud, you add node Florida as a child node of Southeast-US and you move node Georgia from parent South-US to parent Southeast-US. With each change you make in the user interface, an item is added to the request. See Making Changes Interactively.
- By subscribing a target viewpoint to a source viewpoint. For example, you subscribe an Entity viewpoint in your Planning application to an Entity viewpoint in your General Ledger application. When a cost center is added in the Entity viewpoint in the General Ledger application, the system generates a request to add that cost center in the Entity viewpoint in your Planning application as well. See Subscribing to Viewpoints.
- Loaded from a file. For example, you are creating a new United States hierarchy and need to add 50 new nodes (one to represent each state). Each change in the load file is a separate item in the request. In this scenario, there would be 50 items in the request, one for each state node being added. See Making Changes Using a Load File.
Whether you make changes interactively, through a subscription, or by using a load file, all proposed changes are visualized in the viewpoints where you are making the changes or loading the file. Changes are visible in unique colors and icons so that you can see which parts of the hierarchy or list were changed and what areas may be affected by the change.
While making changes to viewpoints, the system performs validation checks to determine the validity of the changes that are being proposed. If items in the request have validation issues, you can see the reason for the failure and decide how to resolve the issue.
When a request is submitted, validation checks run again, the changes are committed, and the viewpoint is updated with the changes.
You cannot perform any request actions in time labeled viewpoints. See Working with Time Labeled Viewpoints.