Applications can reach grantors in different ways. When processing the applications, all important information about the grantee and the grant requested is entered by the processor. An application is always based on a grantor program.
The application forms the basis of the agreement and defines the method of payment and the execution of the grantor management. These can vary greatly depending on the grantor and program, which is why the application processes strongly depend on the Customizing settings. A whole range of example rules, actions, and so on, are delivered, which you can use when Customizing your application.
The application processing is integrated with the Business Rule Framework plus (BRFplus), activity management, funds management in SAP ERP, and CRM Case Management. For information about using multi-funding features, see SAP Library for SAP ERP Central Component on SAP Help Portal at .
You have made all necessary settings in Customizing of business transactions, basic functions, and billing. For more information, see Customizing for Customer Relationship Management
under .
For information on the payment types in particular, see the section here entitled Financial Transactions
.
The program to which the application is assigned must have a status that allows you to create applications. In the standard delivery, this is the status Released
. For more information, see Status
Management in Grants Management.
You have activated the business function BRFplus for Grantor Management (CRM_ISPS_GTRBRFPLUS_1
).
Creating an application
The application in the example delivered is automatically generated from the application form (Web request). The form can be filled out either by an applicant externally over the Internet or internally by a processor who enters the data for the applicant. For more information about Web requests, see Web Requests in Grantor Processing. As soon as the application form is submitted, the application is generated and the data from the application form is copied to the application.
Note
In the example delivered, the applicant must already exist in the system as a business partner. When you enter the business partner, the address data is automatically inserted. The applicant is assigned as the Sold-To Party
.
The application is automatically assigned to a program.
It is also possible to create applications manually.
Evaluation of application form
In the example provided, the evaluation of the application form can take place either by automated scheduled actions or manually. The scheduled actions determine the various amounts based on the program rule set (requested, eligible,
and authorized amount) and create various items if required. In the example, the application status is automatically set to Rejected
if the evaluation shows that the applicant is not eligible.
The sample grantor program T-100
that is delivered uses BRFplus to assess the application. In the application, you can execute a post processing framework (PPF) action that calls BRFplus to determine eligibility and to calculate the grant amount.
A code sample to call BRFplus within the grantor application is available. BRF rules are used in scheduled actions. You can manually assess an application by executing a PPF action that calls Business Object Repository (BOR) method BUS2000270
. To see this BOR
method, you can use transaction Business Object Builder
(SWO1
).
For more information about manual evaluation, see the Evaluation by Survey
section below.
Amounts
In the Customizing for pricing, condition types for three different example amounts are delivered for Grantor Management. The application provides you with an overview of the amounts from the different items:
Requested amount
This amount is taken from the Web request in the example delivered. The requested amount is determined based on the entries in various fields in the Web request (for example, income, energy-saving house). However, entering the amount directly in the form is also possible.
Authorized amount
In the example, the authorized amount is determined using rules from BRFplus and is filled in after the requested and the eligible amounts have been checked. This amount is automatically included in the agreement.
Eligible amount
The eligible amount is also determined from BRFplus and is the amount to which the grantee is entitled according to conditions and rules.
The sum of net amounts from the individual items forms the Net Amount
at header level. This is used for the funds precommitment in funds management in SAP ERP and can later
be used for billing, if this has been defined in Customizing. The Customizing settings also determine which amounts are copied to the agreement.
You can also change the determined amounts manually or add additional items.
Follow-on documents
All documents related to the application are displayed under Document Flow
. You can navigate to the individual documents by using links. You can generate an agreement based on the application with Create
Agreement
. As long as an agreement based on the application has not yet been created, you can withdraw the application. If required, you can also create a case for the application. You automate the creation of cases by using actions.
Actions
The action profile CRM_GAP
is delivered as standard and contains four example action definitions. You can display these under Scheduled Actions
. The actions delivered for creating a case and
a funds commitment are triggered automatically in the example. If required, you can trigger a grant eligibility check or the printing of a letter of rejection.
Status
A new application from a Web request has the status Open
by default. As soon as the request is processed, it receives the status In Process
. If the application is rejected or canceled, the system
status is automatically set to Completed
.
The funds precommitment in the ERP system is updated each time you save the application. If you want to prevent this, you can set the status Distribution Block
at item level until you want distribution to the ERP system to take place.
When all items have the status Completed
, the application automatically receives the status Completed
. Conversely, if the status of an individual item is changed, the entire status at header level is also changed.
You can see all changes that have been made under Change History
.
Dates
The dates are defined in Date Management in Customizing. At header level, there must always be a validity period and at item level, a due date.
Partner
Under Partner
, you can see the business partners involved in the application and their functions. The sold-to party is in this case the grantee. The Bill-To Party
field content is taken from
the master data of the grantee but can be overwritten. By default, the Employee Responsible
is the user who created the application.
Evaluation by survey
You can check the suitability criteria of the grantee using a survey under Evaluation
. The survey is predefined by the program. For more information, see Process
Control.
Attachments
Under Attachments
, you can create notes and documents, such as scanned documents, contracts, or forms that the applicant has submitted.
Notes
Under Notes,
you can add your own personal notes to the application.