Identifying Common Attribute for RMCS Contract Grouping In Fusion — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Identifying Common Attribute for RMCS Contract Grouping In Fusion

in Enterprise Contracts 4 comments

Summary:

In Fusion, what field from the Contract module can populate VRM_SOURCE_DOCUMENTS.SRC_ATTRIBUTE_CHAR60 so that RMCS can use it to correctly identify and group the revenue contract?

According to Doc ID 2825636.1, there is currently no common field between Order Management (DOO) and Fusion Contracts (OKC) that both modules can use to populate an attribute recognized by RMCS for creating a unified revenue contract.

For example, if a Master Agreement Number is used across both sources:

In Order Management, the field DOO_HEADERS_EFF_B.ATTRIBUTE_CHAR20 can be mapped to SRC_ATTRIBUTE_CHAR60 in RMCS, and RMCS is able to create a revenue contract based on that value.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!