In Oracle HCM (Human Capital Management) Cloud, Role Mappings are used to create automated rules that automatically assign, reassign, or remove roles from users based on their employment data.

Here is why this is the correct feature for your specific scenario:

• Automating Based on Conditions: A role mapping uses conditions such as Job, Department, Location, and critically for your case, System Person Type (e.g., Employee vs. Contingent Worker) to dictate who gets what role.

• Dynamic Management: When a user's status changes (for instance, if a contingent worker converts into a full employee), the system automatically evaluates the new conditions, removes the old roles that no longer match, and assigns the new ones.

• Scalability: Instead of manually assigning enterprise roles, security roles, or abstract roles to hundreds of workers, role mappings ensure compliance and security happen automatically behind the scenes.

Balances cubes are multidimensional databases that store financial balances for interactive reporting and analysis. A balances cube is created for each unique combination of ledger and currency, and it contains dimensions such as chart of accounts segments, periods, scenarios, and other user-defined attributes. New dimensions can be added to a balances cube by using the Manage Balances Cube Dimensions task in General Ledger. Balances cubes are updated automatically when journals are posted in General Ledger, and they can also be refreshed manually by using the Refresh Balances Cube task. Balances cubes are not affected by the Translation or Revaluation processes, as these processes only update the balances tables in General Ledger. References:

Overview of Oracle General Ledger Balances Cubes1

Considerations for General Ledger Balances Cubes2

Overview of Oracle Essbase Balances Cubes3

According to Oracle documentation1, you should enable geocoding to achieve the requirement of finding points of interest, such as customers, while out on business. Geocoding is the process of assigning geographic coordinates to a physical address. Geocoding enables you to use maps and location-based services to find and visualize points of interest. Therefore, option B is correct. Option A is incorrect because HZ_GEO_IDENTIFIER_SUBTYPE Lookup is not a feature that enables finding points of interest. Option C is incorrect because validation is not a feature that enables finding points of interest. Option D is incorrect because address cleansing is not a feature that enables finding points of interest.

According to Oracle documentation, when there is a business requirement for a subsidiary company to report to the parent company on a monthly basis with different currencies and no requirement to have daily balances, you should recommend Balance level as the data conversion level. A Balance level data conversion level enables you to translate balances from one currency to another at month-end or quarter-end for reporting purposes. A Balance level data conversion level minimizes the data stored in the reporting currency because it does not store daily balances or journal details. Therefore, option D is correct. Option A is incorrect because a Subledger level data conversion level stores daily balances and journal details in the reporting currency. Option B is incorrect because a Journal Level data conversion level stores journal details in the reporting currency. Option C is incorrect because an Adjustment only level data conversion level does not translate balances from one currency to another. Option E is incorrect because a Spreadsheet level data conversion level does not exist.