Ansicht
Dokumentation

CRMC_GPM_ACT_DEF - Define Action Profiles and Actions

BAL Application Log Documentation   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

In this activity, you define action profiles and actions that are required for action processing in the Grantor Program Management application.

Actions are used for postprocessing grantor programs, for example, for printing, creating e-mails or calling customer-specific coding (BAdIs).

Action profiles are collections of several actions that have certain attributes in common. In the Grantor Program Management application, one action profile can be assigned to a program. All actions contained in that profile can then be executed for the program.

Requirements

Your own action profiles and action definitions should be created in the customer namespace (that is, they should begin with Y or Z) as this namespace is not overwritten by any SAP imports.

Activities

To create an action profile with actions, proceed as follows:

1. Choose New Entriesin the Action Profile view and enter a name and description for the action profile.

Assign the context class CL_CRM_GPM_CONTEXT_PPF in the field Context Class.

If you plan to use the attributes of a grantor program (for example, program type or validity dates) for specifying scheduling and start conditions for actions, you need to assign an appropriate business object type to your action profile: set the Category of Object Type to Business Object Repositoryand enter the Object Type NameBUS2100010.

2. Go into the Action Definition screen and choose New Entries.

The screen for defining actions appears.

3. Enter a name and description for the action.

4. Specify the default values for the action. Consider the following:

Processing time period:

- Immediate processing - the action is started as soon as the start condition is fulfilled.

- Processing when saving document - the action is started directly after the update.

- Processing using selection report - the action is started by the report RSPPFPROCESS. You can run the report manually using transaction SPPFP or schedule it as a background job.

If you select the indicator Partner-Dependent, you can define a partner function or partner function category for which the action is valid. For example, you can use partner function categories if you want a reminder e-mail to be sent to all business partners that are involved in the transaction and assigned to the specific partner function category. You can use partner functions to trigger an action for a specific partner function, for example, to send a reminder e-mail to the employee responsible for the transaction.

Select the indicator Schedule Automaticallyto enable automatic scheduling of actions when their schedule condition is fulfilled.

Select the indicator Delete After Processing to automatically delete actions that have been processed successfully.

Select the indicator Changeable in Dialog if you want to allow the user to manually schedule the actions on the Actions tab page of the Grantor Program Management application.

Select the indicator Executable in Dialog if you want the user to be able to execute the action manually on the Actions tab page.

In the Determination Technique field, choose Determination using conditions that can be transported.

In the field Action Merging, choose:

- Max. 1 Action for Each Action Definition if you want to allow a maximum of one action for this action definition. Once an action for this definition has been scheduled, no other actions can be scheduled for this definition anymore.

- Max. 1 Unprocessed Action for Each Action Definition if you want to allow a maximum of one unprocessed action for this action definition. After an action for this definition has been executed, another action can be scheduled.

- Max. 1 Unprocessed Action for Each Processing Type if you want to allow a maximum of one unprocessed action for each processing type (see below for setting the processing type).

- Set Highest Number of Processed Actions if none of the other options for action merging suits your requirements. When selecting this option, a new tab Action Merging appears. Here you can configure the number of processed and unprocessed actions.

5. Go to the Processing Types screen to set up the kind of postprocessing the action should perform.

6. Choose New Entries and enter a processing type (alert, method call, workflow, external sending or Smart Forms). If you wish to define several processing types, you can select a standard one by setting the default indicator.

7. Select the processing type and choose Set Processing.

- For the processing type Alert:

Enter an existing alert category or create a new one by pressing the corresponding button

- For the processing type Method Call:

Select a method (Business-Add-In) in the Filter Value field.

If you choose Display Implementation, you can display the coding for the selected method. If you choose Create New Implementation, you can define your own methods (BAdI).

Define the processing parameters (container) and maintain the standard values.

- For the processing type Workflow.

Enter a workflow dummy.

- For the processing type External Sending:

(...)

- For the processing type Smart Forms:

Choose print, fax or e-mail and enter a form name, a processing class and a processing method.

8. Repeat the steps 2 to 7 for each action you wish to define.

Further Notes

If you wish to specify multiple output for the same object type, you must define them in the same action profile.

You can find information about the BAdI implementation in the SAP Library under mySAP Technology Components → ABAP Workbench → BC - ABAP Workbench: Tools → Other Concepts → Business Add-Ins

You can find information about the SAP Business Workflow in the SAP Library under mySAP Technology Components → Business Management (BC-BMT) → WebFlow Engine (BC-BMT-WFM)

Fill RESBD Structure from EBP Component Structure   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 7882 Date: 20240523 Time: 152326     sap01-206 ( 118 ms )