1Z0-588 Practice Questions

Your organization has two ERPs: PeopleSoft (PS) and SAP. Each ERP has its own chart of accounts. Each chart of accounts is mapped to a consolidated chart of accounts. The Finance department maintains the consolidated account hierarchy, For both the SAP and PS account properties, users should be able to select from a drop-down list the correct accounts that should be mapped to the consolidated account. Many SAP or PS accounts could be mapped to a single consolidated account. What property type should you set for the SAP Account Property and PS Account Property, assuming that you have built the SAP and PS chart of account hierarchies in DRM?

Choose three validations that are often implemented for downstream systems.

The Time Balance property definition is applicable to the Account hierarchy only and is not valid for any other hierarchy. You would like to simplify the view for end users so they do not see the Time Balance property for the Entity dimension. What method will achieve this requirement?

A department may only have 10 cost centers. How can you address this requirement?

Review the example below: Product All Products Alternate Product Hierarchy All Products High Calorie, Sugar Filled Products Your target Essbase database requires an alternate of the Product, rolling up product SKUs by Caffeinated and NonCaffeinated. You currently maintain this value as a property. Once a valid export is built, what are the two ways you can create the new hierarchy in an existing version?

Your budget office is preparing the Entity dimension for the upcoming year with organisation changes. They are working in a version called '"Budget". This version has a Working status until the Entity hierarchy is finalized. The budget office user has received new information from management that requires him to back out the numerous changes he has made over the last five days. The AllowAsOf system preference is set to True. What is the next step?

You decide to implement node type? for the Account dimension. What are the required steps that must be completed to implement a node type? 1. Under Administer, create node types with valid assigned DRM elements. 2. Create a hierarchy property that contains a list of values that matches the node types defined. 3. Create a local node property called "HierarchyNodeType". 4. For version, set the HierarchyNodeType to "Dimension". 5. For the hierarchy, set the Dimension property to the desired Node type value (for example. Account dimension type for the Account hierarchy). 6. Upload a glyph for each node type.

Identify three common issues that are addressed by DRM out of the box.

Identify the true statements about the DRM Change Tracking properties.