Kontakt

Ansicht
Dokumentation

CRM_ISR_AKTIVITAET - Define Activity Reason for Partner Determination

CRM_ISR_AKTIVITAET - Define Activity Reason for Partner Determination

Fill RESBD Structure from EBP Component Structure   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.
SAP E-Book

In this IMG activity, you use several orders steps to define an activity reason that you can use for partner data and/or organizational data determination in service orders.

Within Web requests, for example, this can be used by the system to enter the responsible processor in a service order, which has been created automatically due to the receipt of a Web request. This enables this processor to call up the orders allocated to him or her directly in his or her work list.

By making the relevant settings for organizational data and partner determination, it is also possible for the service order to be assigned directly to an organizational unit using the activity reason set up within organizational data determination. That is, the service order is assigned directly to a service organization, and within the partner determination an employee of this service organization is determined as responsible processor. Therefore, for example, the Web request for a parking permit can be automatically assigned to the correct authority within a municipality, and then in turn to the responsible employee, who then finds the request in his or her work list.

Within the individual steps for defining the activity reason, you process codes groups with corresponding codes, code group profiles and subject profiles. The definition of activity reasons, that is, 4-character codes and their texts, can be performed as you like to adapt to individual needs. You can, for example, define a code as an activity reason for each request category. Ensure that the short texts for the codes are formulated in such a way, that the meaning of the code is clearly recognizable during later assignment.

You can then assign the defined activity reason to a request category in Customizing for request categories to enable you to use it at request category level in partner and /or organizational data determination. However, you can also provide detailed control in the determination by overriding or resetting the activity reason in a relevant BAdI (see the note below for details). Prerequisite for this is assignment of the subject profile to the transaction type listed under point 5. Ensure that the activity reason does not appear on the interface of a service process.

The activity reason is a three-part identification, which is put together from the ID's for catalog, code group and code. The ID for the catalog is always A1 - Activity Reason and is delivered as standard by SAP. The identifications for code group and code can be added as you like.

  1. Define Code Groups and Codes
    1. Switch to the activity Customer Management -> Basic Functions -> Catalogs, Codes, and Profiles -> Define Code Groups and Codes for Catalogs.
    2. Create a code group for the catalog A1 Activity Reason.
    3. Create codes in this code group for your request categories, or for the detailed control of the activity reason. Enter an expressive short text. You can choose any four-character code.
After this process step, the definition of the activity reason is completed. To use this for partner data- and organizational data determination, perform the following process steps:
  1. Define Code Group Profile
    1. Switch to the activity Customer Management -> Basic Functions -> Catalogs, Codes, and Profiles -> Define Code Group Profiles.
    2. Create an individual code group profile and assign the code group created.
  2. Define Subject Profiles
    1. Switch to the activity Customer Management -> Basic Functions -> Catalogs, Codes, and Profiles -> Define Subject Profiles.
    2. Create a subject profile and assign the code group profile created.
  3. Assign Subject Profile to the Transaction Type
    1. Switch to the Web Requests Customizing Define Transaction Types.
    2. Select the transaction type and then the assigned business transaction category Business Activity.
    3. On the third level Customizing Header, assign the subject profile under Default Data.
  4. Enter Activity Reason in the Request Category
    1. Switch to the Web Requests Customizing activity Define Request Categories.
    2. Assign your activity reason in the detail data for a request category. The prerequisite for this, is that you have assigned the subject profile created (see above) to all of the transaction types that are intended for web requests.
  5. Define Determination Rule for Partner and Organizational Data Determination with Reference to an Activity Reason
  • In this process step, you can define a determination rule for partner or organizational data determination with reference to an activity reason. Perform this process step in the activity Customer Management-> Master Data -> Organizational Management -> Organizational Data Determination -> Change Rules and Profiles -> Maintain Determination Rules.

Note: You can override an activity reason by programming the method DETERMINE CODES correspondingly for the BAdI CRM_SERVICE_WEB_REQ for each request category. To do this, choose the activity Define Request Categories and switch to the detail data for the relevant request category in the User-Defined Control screen area.

Example for an activity reason:

The ID for the catalog is always A1. For this catalog, you create the code group ABC001 with the short text Activity Reason for Web Requests. You create the code WA01 with the short text Request for Parking Permit for the code group ABC001.

You have now defined the activity reason A1-ABC0001-WA01 Request for Parking Permit.






RFUMSV00 - Advance Return for Tax on Sales/Purchases   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 7382 Date: 20240523 Time: 180504     sap01-206 ( 123 ms )