Request to Recalculate Usage Actor/Role: MDM Authorized User Description: An authorized user may wish to recalculate the usage transaction if new data has been received or if edits were made to the existing data. By selecting recalculate, the usage transaction will go back to the “Calculate” status. Business Object (Y/N) Business Object Request to Approve Usage Actor/Role: MDM Authorized User Description: An authorized user can request that the usage transaction is approved so that downstream processing can continue. Business Object (Y/N) Business Object Group: Usage Transaction (Parent) Update UT to “Approved” state Actor/Role: MDM Description: Once an authorized user has provided approval, the status of the usage transaction will be updated to “Approve.” The application will monitor for Usage Transactions in the “Approve” status and automatically transition them to the next status of “Sent.” Process Plug-in enabled (Y/N) Available Algorithm(s): F1-AT-RQ Business Object (Y/N) Business Object Update UT to “Sent” Status Actor/Role: MDM Description: The final status in the normal lifecycle is “Sent.” When a usage transaction enters this status the Send Usage algorithm will be triggered to send the results to the usage recipient. While in this status, the user has the ability to change the status to “Subsequent Correction”. D2-SEND-USG Process Plug-in enabled (Y/N) Available Algorithm(s): Business Object (Y/N) Business Object Group: Usage Transaction (Parent) Determine Usage Recipient Actor/Role: MDM Description: The service provider (i.e., usage recipient) is determined from the usage subscription or usage subscription type Process Plug-in enabled (Y/N) Available Algorithm(s): D2-SEND-USG Business Object (Y/N) Business Object
Request to Recalculate Usage Actor/Role: MDM Authorized User Description: An authorized user may wish to recalculate the usage transaction if new data has been received or if edits were made to the existing data. By selecting recalculate, the usage transaction will go back to the “Calculate” status. Business Object (Y/N) Business Object Request to Approve Usage Actor/Role: MDM Authorized User Description: An authorized user can request that the usage transaction is approved so that downstream processing can continue. Business Object (Y/N) Business Object Group: Usage Transaction (Parent) Update UT to “Approved” state Actor/Role: MDM Description: Once an authorized user has provided approval, the status of the usage transaction will be updated to “Approve.” The application will monitor for Usage Transactions in the “Approve” status and automatically transition them to the next status of “Sent.” Process Plug-in enabled (Y/N) Available Algorithm(s): F1-AT-RQ Business Object (Y/N) Business Object Update UT to “Sent” Status Actor/Role: MDM Description: The final status in the normal lifecycle is “Sent.” When a usage transaction enters this status the Send Usage algorithm will be triggered to send the results to the usage recipient. While in this status, the user has the ability to change the status to “Subsequent Correction”. Process Plug-in enabled (Y/N) Available Algorithm(s): D2-SEND-USG Business Object (Y/N) Business Object Group: Usage Transaction (Parent) Determine Usage Recipient Actor/Role: MDM Description: The service provider (i.e., usage recipient) is determined from the usage subscription or usage subscription type Process Plug-in enabled (Y/N) Available Algorithm(s): D2-SEND-USG Business Object (Y/N) Business Object