A. C, B, A

B. A, B, C

C. A, C, B

D. B, A, C

E. B, C, A

F. C, A, B

A. Effective Periods are used for standalone selling prices and for creating journal entries.

B. You cannot have overlapping periods.

C. Effective Periods only define the rage where standalone selling prices of an item should be effective.

D. Gaps between periods are not allowed.

E. If effective periods are not defined, Revenue Management uses the General Ledger calendar.

A. Manage contracts in "Pending Review" status.

B. Edit Contract Identification Rules.

C. Manage contracts in "Pending Allocation" status.

D. Review Observed Standalone Selling Prices.

E. Review Performance Satisfaction Plans.

F. Review Revenue Price Profiles.

A. a promise to a customer on which either party has acted

B. a combination of customer type and product code

C. a promise to a customer

D. a product code or SKU

A. the ability not to revise previously reported revenue for revision, corrections, and other changes

B. the fair value of each performance obligation

C. an allocation of the expected consideration over the performance obligations as if you had sold them separately

D. the maximum amount of revenue you can recognize soonest, postponing the minimum until later

A. Because they are Revenue Management Descriptive Flexfields.

B. Because they are needed for integration with Product Management.

C. Because they are needed for the VRM_SOURCE_DOCUMENTS table to populate extensible attributes.

D. Because they provide uniqueness to the Source Document Types.