Show TOC

Process documentationCase Management in Grants Management for Grantor

 

To effectively manage a grantor file, the program manager can use case management. This provides you with a central place for all documents related to a single application and its follow-on transactions. Grantor programs have varying degrees of complexity. Within a simple program, a case may be generated on an exception basis to manage a payment dispute, for example. In more complex programs, for example, a multi-year grant, a case may be required for every approved application generated. You then have an easy overview of all related internal (for example, SAP BOs) and external (for example, scanned application document) documents.

Prerequisites

Before working with cases in grantor management, you should implement the note 969142.

Process

In Grantor Management, a sample process is delivered as standard. In this sample process, we have the following objects that can be assigned to a case:

  • Business partners

  • Grantor programs

  • Application

  • Agreement

  • FMRE (earmarked fund) document (pre-commitment, commitment)

  • Account documents

  • Business activities

  • Tasks

  • Billing documents

These can either be assigned manually or automatically when you save a released application.

There are two business transactions used in Grantor Management: GAP (grantor application) and GAG (grantor agreement).

Two action profiles are delivered:

  • GRM_GAP – Assigned to the GAP transaction (this creates the case and links the program, applications, FMRE documents and business partners with the partner function "sold-to", "contact person" or "employee responsible" from the application to the case)

  • GRM_GAG – Assigned to the GAG transaction (links the agreement, FMRE and billing documents to the case)

These contain the following actions:

  • Action RELEASE_APPLICATION: Once the application is released and saved, a case is automatically created and the program, application and business partners are linked.

  • Action SAVE_APPLICATION: This action is triggered when the grantor application is saved. This checks if the application has been distributed to ERP. It then checks the document flow of the application and tries to link the ear-marked funds (pre-commitment documents) to grantor cases.

  • Action RELEASE_AGREEMENT: This checks if a case already exists for this agreement and the associated applications. If a case exists, it links this agreement.

  • Action SAVE AGREEMENT: This action is triggered when the grantor agreement is saved. This checks if the agreement has been distributed to ERP.

To make changes to the Customizing for actions, see Customizing for Start of the navigation path Customer Relationship Management Next navigation step Basic Functions Next navigation step Actions Next navigation step Actions in Grantor Management. End of the navigation path

The automatic process includes:

  • The automatic creation of a case. This is always triggered when the application is saved and will only be scheduled when the application is released.

  • The automatic linking of the program, application, business partners, agreement, account and billing documents.

  • The retrieval of key attributes for linked objects

For more information on case management functionality, see Case Management.