Explanation
A usage transaction is a record that stores the usage information for a usage subscription. A usage transaction can be created by an external source or MDM, which uses the usage calculation engine to generate a final value. VEE can be configured and usage transaction is saved.
It is not true that a usage transaction is created by an external source or MDM, which uses the usage calculation engine to generate usage values. Usage values are intermediate values that are used to calculate the final value.
It is not true that a usage transaction is created by an external source or MDM, which uses the usage calculation engine to generate a final value. VEE can be configured but when called in real time, usage transaction may not be saved. VEE can be configured and usage transaction is always saved.
It is not true that a usage transaction must be created by an external system and it must be stored in the database. A usage transaction can be created by MDM and it can be deleted from the database.

Explanation
A virtual meter is a meter that does not physically exist but is used to represent the usage of a group of meters or a portion of a meter. A virtual meter can be used to perform various calculations or adjustments on usage data, such as aggregation, derivation, allocation, or net metering. According to the Oracle Utilities Meter Data Management Business User Guide, to bill the university correctly for a new fast food restaurant that is being installed at the center of the university and whose usage will also be included in the university's master meter, the correct step is:
* Use derivation algorithms to exclude the restaurant's usage from the master meter. This can be done by creating a virtual meter that represents the master meter minus the restaurant's meter and applying a derivation algorithm that subtracts the restaurant's usage from the master meter's usage. The virtual meter's usage can then be used for billing the university.
References: Oracle Utilities Meter Data Management Business User Guide, Chapter 3: Asset Management, Section 3.4: Virtual Meters

Explanation
To configure equipment that attaches to an asset, such as a communication module attached to a meter, you should set up a component. A component is a part of an asset that can be installed and removed independently of the asset. You can define component types and associate them with asset types. For example, you can define a communication module component type and associate it with a meter asset type2.
You do not need to create a master child asset, which is a relationship between two assets that are installed at different service points but are functionally related. For example, you can define a transformer as a master asset and a meter as a child asset2. A master child asset is not suitable for equipment that attaches to an asset.
You do not need to add a sub-asset, which is an asset that is installed at the same service point as another asset but has its own measuring components and usage subscriptions. For example, you can define a meter as a sub-asset of another meter if they share the same service point but have different measurements2. A sub-asset is not suitable for equipment that attaches to an asset.
You do not need to add a constituent part, which is an attribute of an asset that cannot be installed or removed independently of the asset. For example, you can define a battery as a constituent part of a meter if it is embedded in the meter and cannot be replaced . A constituent part is not suitable for equipment that attaches to an asset.

Explanation
To set up the Cloud Service Payload Processing configuration, you should perform the following steps:
* File system directory SFTP setup: This is used to configure the secure file transfer protocol (SFTP) settings for transferring files between Oracle Utilities Smart Grid Gateway and Oracle Utilities Meter Data Management. You need to specify the SFTP host name, port number, user name, password, and directory path for inbound and outbound files.
* Key rings and key pairs: This is used to configure the encryption and decryption settings for payload files. You need to create key rings and key pairs for each communication type and associate them with message senders and receivers.
* Object Storage locations: This is used to configure the object storage settings for storing payload files in Oracle Cloud Infrastructure. You need to specify the object storage URL, bucket name, user name, password, and encryption key for each communication type.
You do not need to set up head-end systems (HES), which are external systems that communicate with smart meters and devices. Head-end systems are configured in Oracle Utilities Smart Grid Gateway, not in Oracle Utilities Meter Data Management.

Explanation
To convert natural gas volume to energy at the measuring component level, you should perform the following configuration steps:
* Set up a factor to hold the conversion values: A factor is a value that is used to adjust or convert measurements based on certain criteria. You need to set up a factor to hold the conversion values that are used to convert natural gas volume to energy. For example, you can set up a factor that holds the heating value of natural gas in different units of measure (UOM).
* Configure a value derivation algorithm by using Groovy: A value derivation algorithm is a rule that is used to calculate derived values from raw measurements based on certain factors or formulas. You need to configure a value derivation algorithm by using Groovy scripting language to define how natural gas volume is converted to energy by applying the conversion factor.
* Create value identifiers for the energy UOM on the measuring component type: A value identifier is an attribute that is used to store measurement or derived values in different UOMs. You need to create value identifiers for the energy UOM on the measuring component type that is used for natural gas devices. For example, you can create value identifiers for energy in British thermal units (BTU) or kilowatt-hours (kWh).
You do not need to create value identifiers for the energy UOM on the device, which is an instance of a device type that is installed at a service point. Value identifiers are defined at the measuring component type level, not at the device level.
You do not need to configure a value derivation algorithm by using Java, which is a programming language that is used to develop custom applications or extensions. Value derivation algorithms are configured by using Groovy scripting language, not Java.