Ansicht
Dokumentation

CRM_NETPR_AKTP - Define Action Profiles and Actions

ROGBILLS - Synchronize billing plans   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

In this step, you define actions and action profiles, which are required for processing price lists.
An action profile is used to output documents and is a collection of individual action definitions.

Prerequisites

Before you start defining actions and action profiles, you must assign each action profile to at least one price list type (Assign Price List Types). As soon as you have made this assignment, the system generates the actions for all price lists according to the action profile in question. Every action represents the output of a document as per the parameters defined in the corresponding action definition.

Standard settings

To ensure that you can use action processing properly with price lists, you should work your way through the various steps in the structure on the left of the screen:

When you define action profiles for an application, assign each profile to an object type. For the "CRM Price Lists" application, you must assign the object type "CRM Price List" (corresponds to business object BUS20850) to the action profile.

When you define action profiles for an application, specify that the context class is "Context Class for BEAs" (CL_BEA_CONTENT_PPF) - this will enable you to assign a net price list to all the possible actions in CRM Price Lists.

When you define actions, enter an action summarization of "Max. 1 action per action definition" for the CRM Price List.

When you define processing types, use the standard output media used in CRM Billing. Do this by selecting a permitted processing type for the action in question and choose Make Settings for Processing.
The standard default parameters for all processing classes are:

• Form name of Smart Form: "Invoice Form for CNPL" (BEA_CNPL_BILLING_SF)

• Processing class: "Processing class for BEAs" (CL_BEA_SF_PROCESSING_PPF)

• Processing method: "Implementation of Smart Form Function Module Call" (PROCESS_SMART_FORM)

Activities

When you define actions (see structure on the left-hand side of screen) you define - among other things - the following output parameters for actions:

• Processing time
  This determines when the action is performed (that is, when the document in question is output).

• Scheduling
  This determines whether each action determined should be performed automatically, or whether it can be performed online.

• Modifiable
  This determines whether an action can be changed before it is performed online.

• Partner dependency
  This determines the partner function (for example, bill-to party) to which the output is addressed.

• Determination technique
  This determines the technique (condition type) used for determining actions.

• Action summarization rule
  This determines how newly determined actions can be brought into line with existing actions. Action summarization only occurs for actions that belong to the same billing document.

• You determine the permitted processing types for actions plus all corresponding parameters by clicking the "Processing types" point under the appropriate action definition node in the structure on the left-hand side of the screen.

Example:

If actions are to be processed asynchronously to their generation, you could specify "Process using selection report" as the processing time. This will mean that you can output invoices at night, and thus reduce the system load during the day.

You can choose from the processing types "print", "fax" and "e-mail". Whichever you choose, the system automatically uses the appropriate Smart Form, processing class, processing method and store mode.

TXBHW - Original Tax Base Amount in Local Currency   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 4153 Date: 20240523 Time: 162606     sap01-206 ( 80 ms )