Ansicht
Dokumentation

Change Request (New) ( RELNCRM_51_GTR_CHANGEREQ )

BAL Application Log Documentation   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Short text

Change Request (New)

Use

This release note is only relevant if upgrading from SAP CRM 5.0.

You can now use a change request to manage the process of changing your agreements. Commonly, the agreement is a legally binding document, and restrictions exist on the changes that can be made once it has been approved and released. However, since changes are still possible in certain circumstances, a change management system with predefined processes is available. Custom settings determine which fields on the agreement invoke the change management process. Some fields, for example agreement description, may not require the triggering of a review and assessment effort.

If a grantee requests a change to the authorized amount or the validity date after the agreement has been released, the grantee or a responsible grantor employee can fill out a change form and submit it as a Web request.

Additionally, the employee responsible is determined via a workflow. The employee receives a workflow message that contains the change request ID and the instruction to check the request and to release or reject it. The employee can either manually check whether the required criteria are met or, if the appropriate rules are implemented, trigger a check using the Business Rule Framework (BRF).

Alternatively, a completely automated check of the request using the Business Rule Framework (BRF) is possible. For this purpose, the BRF rule 7CHANGE_REQUE is delivered in the application class 7GRANTOR, which checks whether a newly changed date is still within the validity period of the program, for example. You can define additional rules for checking the change request yourself.

Once the request has been approved or rejected, a message is sent to the author of the change request via a workflow, an action sets the change request status to Released, and approved changes are displayed in the agreement.

If the effective date of the change request is in the future, the original and the changed amounts remain visible as items in the agreement until the effective date is reached.

Agreement versions are generated as PDF documents for internal tracking. A sample PDF for external processing of agreements and agreement amendments is also provided.

Effects on Existing Data

Effects on Data Transfer

Effects on System Administration

Effects on Customizing

Example processes for changing the validity date and authorized amount are delivered in Customizing under Customer Relationship Management → Industry-Specific Solutions → Public Sector → Grantor Management → Grantor Processing → Change Process Management. To define processing for additional fields, you need to enter them here and implement them using a BAdI.

Further Information

General Material Data   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 3227 Date: 20240520 Time: 203145     sap01-206 ( 73 ms )