In Oracle Manufacturing Cloud and related financial applications, managerial accounting plays a significant role in tracking and managing costs across supply chain and manufacturing activities. The following is a breakdown of the correct statements:
Statement A: Receipt Accounting is the application that performs accrual accounting for all types of receipts - Receipt Accounting is a crucial module in Oracle Cloud that supports the tracking of costs and performs accruals related to receipts. This includes processes such as procurement receipts, interorganization transfers, and supplier shipments. This allows organizations to recognize and account for the expenses associated with these receipts.
Reference:
Statement B: Landed Cost Management gives organizations financial visibility into their extended supply chain costs - Landed Cost Management is designed to capture additional costs that arise during the transportation, handling, and processing of goods. This includes costs like shipping, insurance, and customs duties. By including these in the overall cost, it provides a more comprehensive view of the actual costs of goods in the supply chain.
Statement D: Cost method can be defined with granularity down to individual items - In Oracle Manufacturing Cloud, costing methods can be assigned not only at the organization level but also at a granular level down to individual items. This provides flexibility in defining different costing strategies for different products depending on their nature, manufacturing process, or market conditions.
Incorrect Statements:
Statement C: Supply Chain Orchestration automatically selects the correct process based on user-defined Subledger Accounting rules when a supply creation is initiated - While Supply Chain Orchestration automates various supply chain processes, it does not select processes based on Subledger Accounting rules. The orchestration system is more focused on managing and coordinating supply chain processes rather than determining accounting rules.

In Oracle Manufacturing Cloud, managing Units of Measure (UOM) is critical to ensuring that transactions, measurements, and conversions are handled accurately. Below is a detailed explanation of the correct statements:
Statement A: You must define the unit of measure class with a base unit of measure - This is a fundamental setup in Oracle Manufacturing Cloud. Every UOM class must have a base unit of measure defined because it serves as the reference for all conversions within the class. The base UOM acts as a standard, and all other UOMs within the class are defined relative to it.
Reference:
Statement B: If you want to transact items in units of measure that belong to classes other than their primary UOM class, you must define conversions between the base units of measure in different UOM classes - This is true. If an item's UOM belongs to one class, but you need to transact in another UOM from a different class, a conversion must be defined between the base UOMs of the two classes. This ensures seamless inter-class transactions and measurement consistency.
Statement E: A unit of measure conversion is a mathematical relationship between two different units of measure - UOM conversions in Oracle Cloud are defined mathematically, typically by specifying a conversion factor. This relationship is used by the system to automatically convert quantities between different units of measure, whether for inter-class or intra-class conversions.
Incorrect Statements:
Statement C: A unit of measure standard conversion specifies the conversion factor by which the unit of measure is equivalent to the unit of measure class - This statement is incorrect because a standard conversion relates two UOMs directly, not between a UOM and the class itself. Conversions operate between specific UOMs, not between a UOM and its class.
Statement D: Conversions between classes are unique for each item; the conversion rate varies for intraclass units of measure - This is not accurate because conversions between UOM classes are not unique for each item. Once a UOM conversion is established between classes, it applies globally unless there are specific item-level conversions.
This ensures a consistent approach to defining, transacting, and converting units of measure across different manufacturing and inventory processes within Oracle Manufacturing Cloud.