Ansicht
Dokumentation

CRM_GM_CONFIG_BT - Transactions in Grantor Processing

ABAP Short Reference   PERFORM Short Reference  
This documentation is copyright by SAP AG.

This document lists the activities required to configure Grantor Management.

• Define Transaction Types

A transaction type defines the attributes and characteristics of business transaction and the controlling attributes (for example, text determination procedure, partner determination procedure, status profile, organizational data profile). A transaction type controls how a specific business transaction is processed.

For each grantor business transaction, a transaction type is delivered as standard with grantor processing:

• Application: GAP (leading business transaction category: BUS2000270)

• Agreement: GAG (leading business transaction category: BUS2000271)

A transaction type is assigned to one or more business transaction categories. The business transaction category specifies the business context in which a transaction type can be used. For example, for grantor application, the following business transaction categories could be assigned:

• Sales (BUS2000115): This context is used to define the document pricing procedure, which determines the pricing procedure

• Grantor application (BUS2000270): This context is used to define if the transaction type is a grantor application or change request. It also defines the subject profile that will be used to maintain cancellation reasons

• Define Item Categories

An item category specifies the properties and attributes of a business transaction item. For Grantor Management, a set of item categories are delivered as standard:

GAPL (BUS2000275),,Application item - One-time payment
GAPP (BUS2000275),,Application item - Periodic payment

GAGL (BUS2000276),,Agreement item - One-time payment
GAGP (BUS2000276),,Agreement item - Periodic payment

Like transaction types, an item category is assigned to one or more business transaction categories. For example, in the grantor application item:

• Using the Sales business object (BUS2000115), you define the item category as pricing-relevant and set the pricing indicator to active.

• Using grantor application (BUS2000270), you select which condition types are used for requested, eligible and authorized amount.

• Define Item Category Usages

You use this activity to define a payment type for a grantor business transaction item. The following standard payment types are delivered:
GADV: Advance
GPOU: Payment
GPIN: Repayment
GHBCK: Holdback

Any new entry made by a customer implies the implementation of the proper business logic.

• Define Financial Execution

In this activity you define the financial execution types, which determine how the payment is made for a grantor item. The standard delivery item categories for grantor agreement and grantor application items are one-time or periodic.

• Define Item Category Determination

In this activity, you define per business transaction category and item category usage which item categories the system uses as the default for processing business transactions. At the same time, you can define which item categories can alternatively be entered manually as the system default. There is a maximum of three alternative item categories possible.

For grantor application and agreement items, all the settings are provided to cover all the possible business scenarios.

Example for grantor application:

• A main item with payment type Advance could have either GAPL (One-Time) or GAPP (Periodic) as the item category

• Define Number Ranges

The following number range is delivered as standard for Grantor Management:

CRM_GM_GAP for applications. Separate intervals are provided for
CRM_GM_GAG for agreements

• Define Copying Control for Transaction Types

Since the agreement is a follow-on transaction to the application, you need to set up copying control from the application to the agreement that defines which information is copied.

Customers who have requirements for copying control can enhance the conditions according to their needs by writing their own data transfer routines using available BAdI methods.

• Define Copying Control for Item Categories

This activity is used to set up the copying control for item categories. As agreement items could be created with reference to application items, make the copy control entries in accordance with application item categories as the source item category, and the agreement item categories as the target item category. For the Copy Conditions, select Only Copy Manual Conditions and for the Copy Routine select GRM001.

• Define Item Category Determination when Copying

This activity is used to define a specific item category determination which should be run during copying. The item category is used to find the target item category in the source transaction for the transaction type in the target transaction. This means that the transaction type for the source transaction is not relevant for the item category determination.

• Define Expense Types

Expense types in Grantor Management are modeled using a catalog, code groups and codes.

• The catalog is a compilation of expense types with related content. Catalogs for grantor expense types must be of the type 'J'

• The code group is a key that identifies the structure of the catalog

• The code is a key that identifies a unique expense type

A sample catalog containing content called 'J1' is part of the standard delivery.

CL_GUI_FRONTEND_SERVICES - Frontend Services   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 7745 Date: 20240523 Time: 172009     sap01-206 ( 115 ms )