Beruflich Dokumente
Kultur Dokumente
We can schedule and start predefined conditions with the Actions component by means of user-definable conditions from transaction and marketing objects. Actions use the Post Processing Framework (PPF), a Basis component, which can be automated with the initiation of outputs, follow-on documents or workflows. Using the Actions tab page within a business document, you can display a list of actions that can be included in the business transaction. An action profile is determined from the corresponding transaction type or item category. Actions are stored as action definitions within an action profile. You can control action processing using different settings and parameters: Action changeable or executable in dialog Action displayed in toolbar (SAP GUI) Processing time (when saving the document or via selection report) Partner dependence Determination technique Action merging Processing types (with entry of the desired form name)
1.2 FEATURES OF ACTIONS You can define actions dependent on conditions so that the system automatically schedules and starts them when the conditions are fulfilled. With actions you can: Create follow-up transactions automatically Execute changes in the transaction or marketing object currently being processed, for example, create new items, or status inheritance by subordinate elements in marketing objects Output in print, by faxing or e-mail
Actions are displayed in transaction documents that support actions and to which an action profile is assigned. You can display a list of actions scheduled for the document on the Actions tab page of a transaction document. The following information is displayed in the list for each action: Status (action scheduled, action processed) Description (purpose of action)
Conditions (settings for action definition and conditions are displayed) Creator, Creation date
There are various processing types for actions: Methods (Business Add-Ins) Methods are Business Add-In (BADI) implementations. You can define your own BADI implementation to adapt actions to your processes and needs. (EXEC_METHODCALL_PPF is the relevant BADI.) Examples for standard methods include the following: COPY_DOCUMENT (create a follow-up document) COMPLETE_DOCUMENT (set status completed within document) CREDIT_MEMO (create credit memo item) REPAIR_ITEM (create a repair item) 1O_EVENT_CREATE (create a workflow event)
SAP Business Workflow This is suitable for more complex processes, for example, a follow-up transaction that includes an approval process.
Smart Forms SAP Smart Forms must be used to print, e-mail or fax documents such as an order confirmation. You can use the graphics tool, SAP Smart Forms, to design the layout of output forms. SAP delivers several Smart Forms for outputs in SAP CRM: Form CRM_ORDER_CONFIRMATION_01 (suitable for faxes, letters, and e-mail) Form CRM_ORDER_LEASING_01 (suitable for faxes, letters, and e-mail) Form CRM_OPPORTUNITY_01 (suitable for faxes, letters, and e-mail)
SAP Smart Forms offer the advantage of adapting forms without requiring programming knowledge, thanks to a completely graphical user interface.
When you request a printout of a form, the application program obtains the relevant data to be used and prints it on the form. Data retrieval and form logic are separated from one another. SAP Smart Forms replace SAP-Script forms (migration from SAP-Script forms to Smart Forms is supported). 2.0 HOW TO CREATE AN ACTION 2.1 STEP-BY-STEP PROCEDURE 2.1.1 Enter into any SAP-CRM Server and move to Transaction SPRO.
2.1.2 Press SAP Reference IMG -> Customer Relationship Management ->Basic Functions -> Actions -> Actions in Transactions.
2.1.5 Click
2.1.6 Click
2.1.7 Click
Processing Using Selection Report gets started after a selection report is executed if the start condition has been fulfilled. Immediate Processing gets started as soon as the start condition is fulfilled. Processing when saving a Document gets started when the document is saved.
2.1.8 Click
Partner Dependent makes this Action as dependent on Partner. The partner you choose is the one, for which the action triggers. It first checks whether that Partner exists or not. If not, it throws an ERROR. 2.1.9 Click and select the Processing. The processing that we select is the one on which we want the Action to work on.
Select the one you want. For this case select Workflow.
2.1.10 Click
and Enter the Workflow Number that you want to assign with this Action.
2.1.11 Click
2.1.12 Click
Schedule Condition decides whether an action should be scheduled for processing or not. An action is therefore generated only if the schedule condition is met. It is not mandatory to assign a schedule condition.
2.1.13 Click
Start Condition is checked before an action is executed. The Action is executed only if the Start Condition is satisfied. Here you wont be able to assign a Start Condition; there is another tab in Actions where we can assign Start Condition.
2.1.14 Click
Click
2.1.15 To assign Start Condition -> Go-to step 2.1.2 -> Click on Change Actions and Conditions -> Define Conditions.
It shows you the entire Action that you created till now. To assign start condition, Click on Start Condition Tab.
Enter a Condition.
Click .
And hence, this completes your Action Profile Creation for a Workflow. Similarly, we can create Action Profiles for other processing also.
Introduction
This document is the Business Process Design of the Business Partner Master data for SAP CRM. It describes the interpretation of the SAP CRM object Business Partner (abbreviated BP).
Objectives
The aim of this document is to acquire all information needed for the customizing object BP in SAP CRM.
Business Partner
The defined number ranges are assigned to groupings in the Define groupings and assign number ranges activity. Number ranges for business partners are valid throughout a client.
Procedure
1. Access the activity using one of the following navigation options:
1. SAP CRM Role Menu Transaction code IMG Path Defining Number Range for Org Business Partners
SPRO Cross-Application Components SAP Business Partner Business Partner Basic Settings Number Ranges and Groupings Define Number Ranges
3.
4. Enter the Interval ID and range 5. Select Check Box Ext if External Number range is required
The Number ranges are defined as needed for different kinds of roles of Business Partner.
Defining Groupings Use Assign each business partner to a grouping when you create the business partner. This grouping determines the number range. You cannot change this assignment at a later stage. Procedure
1. To carry out the activity, choose one of the following navigation options: SAP CRM Transaction code IMG path
Defining Groupings
SPRO
CRM Cross-Application Components SAP Business Partner Business Partner Basic Settings Number Ranges and Groupings Define Groupings and Assign Number Ranges
2. 3. 4.
Choose New Entries. Enter the grouping, short name, description, number range and select the check box External. Save your entries.
Result: All the Number Ranges defined are assigned to a group with a particular naming convention, which are used in Grouping Tab in Easy Access Screen of Business Partner. Defining Business Partner Roles
Definition: Business Partner role Rights and responsibilities that a business partner can have in various business transactions.
In this activity, you make the settings for the properties of business partner roles. In the business partner dialog you can select from all of the business partner roles provided. If you only want to display certain business partner roles in the selection list, you can hide the other business partner roles. You can replace the standard title of business partner roles with customer-defined names Procedure
1. To carry out the activity, choose one of the following navigation options SAP CRM Transaction code IMG path
Defining Groupings
SPRO
CRM Cross-Application Components SAP Business Partner Business Partner Basic Settings Business Partner Roles Properties of Business Partner Roles
2.
3.
4. 5. 6. 7.
Set the indicator Hide if the business partner role is not to appear in the selection list. Define the position where the business partner role is to appear in the selection list. If you want to give the selected business partner role a different title to the standard title, enter the required Customer title under Title.
The following roles will be used in SAP CRM: Role Name Employee Contact person Sold to Parry Prospect Ship to Party Bill to Party Retailer Result. All the Business Partner roles those the client wants to appear in the Easy access Screen are defined and all those that are unwanted are hidden. The Business Partner Roles are named in accordance with the clients requirement. Category (Person/Org/Group) Person Person Person/Organization Person/Organization Person/Organization Person/Organization Person/Organization Remarks Use of Standard role Employee Use of SAP standard role contact person Use of SAP standard role sold-to party Use of SAP standard role prospect Use of SAP standard role Ship to Party Use of SAP standard role Bill to Party This role will be used to register the retailers.
In the field display Role Choose sold to party and in Grouping Choose Customers Grouping
3.
Enter all the required data, like Title, Name, Address and also the data as required the other tabs
4. Save the entriy. 5. Repeat the same for different roles. Result.
Web URL (E.g. Google, Yahoo, etc) in CRM UI can be launched using transaction launcher Step1: Step1a: Call Transaction SM30. Enter the View name: CRMV_IC_LTX_URL
Step1b: URL ID: Description: Request Method: Click radio-button URL: ZGOOGLE (any name starting with Z) Google Get for Non-BSP URL http://www.google.com
Save the entry. Step2: Step2a: Call transaction CRMC_UI_ACTIONWZ Or IMG path CRM -> UI Framework -> Technical Role Definition -> Configure Transaction Launcher
Step2b: Launch Trans. ID : Zlaunch_google.(Any name starting with Z) Component Set Click on Continue. : ALL
Step2c: Description : launch google Class name : ZCL_CRM_LAUNCH_GOOGLE (Any class name starting with Z). Activate checkbox for Stateful to show the URL in a new window. Be sure that the checkbox Raise Veto is deactivated. Click on Continue
Step2d: Choose URL Transaction (B) as transaction type URL ID: ZGOOGLE created in the URL repository. Continue
Step2e: Skip screen for transaction parameters and activity clipboard by pressing Continue. End the wizard and press Complete. Step3: Step3a: Execute Transaction CRMC_UI_NBLINKS Or IMG path CRM -> UI Framework -> Technical Role Definition -> Define Navigation Bar Profile
Select Define Logical Links at the dialog structure on the left by double-click. Create a new logical link: Logical Link ID: ZGOOGLE Type: Target ID: Parameter Parameter Class: Title: Description: Launch Transaction EXECLTX ZGOOGLE CL_CRM_UI_LTX_NAVBAR_PARAM Google Google
Save the changes. Step3b: Select Define Direct Link Groups Create a new entry Group ID Group Type Title Description : ZGOOGLE : No Classification : Google : Google.
Step3c: Select Assign Links at the dialog structure on the left by double-click. Create a new entry Logical link ID : ZGOOGLE (Which has been defined in Define Logical Links) Position : 10
Click Assign Direct Link Groups at the dialog structure on the left Create a new entry Group ID : ZGOOGLE Position : 30 (any position).
Step4: Execute Transaction CRMC_UI_PROFILE or go to IMG path CRM -> Business Roles -> Define Business Role.
Double-click on Visible Direct Group Links at the dialog structure on the left. Click Visible Check Box corresponding to Group ID ZGOOGLE
Web URL inside CRM IC Web BSP view can be launched using transaction launcher. Follow the steps below:
First create URL ID using the path IMG->CRM->IC WebClient-> Basic Functions-> Transaction Launcher-> Define URL's and Parameters Here by clicking on New Entries ,you need to create a URL ID, select 3rd radio button Non BSP URL and enter your web URL there. To keep it simple copy the existing URL ID SAP into your own with your web URL for ex ZSDN Now go back to Transaction Launcher and start the "Configure Transaction Launcher" Wizard In the Wizard when it prompts for Launch Transaction ID ,enter new transaction ID for ex ZTXID_SDN and click on 'continue ' and enter transaction class name for ZCL_TX_SDN In the next screen under 'Transaction launcher Type' select 'URL Transaction' ,and under details area select the URL ID you have created in step 1. i.e ZSDN. Complete the wizard. Now you need to map the URL transaction ID to Navigation Bar profile entries. For this go to 'Define Navigation Bar Profiles' under Basic Functions. Click on Define Entries ,enter the basic details and select 'Launch Trans' radio button and select the transaction id created in step 2 . i.e ZTXID_SDN Add the above create entry to your Navigation Bar profile Update IC Web Client profile with your Navigation bar profile Launch IC web and you would see Web URL Navigation bar entry under Navigation Bar.
BDT, among other things, is used to add/delete/disable fields in the BP transaction only. It does not create new objects for the developer to play with. BDT as a separate unit in CRM (TCode BUPT) has several useful tools like BP events which are useful at times. Whereas EEW can extend several transactions in CRM including BP and it extends the business object by creating several z-objects like an active BADi implementation, middleware objects like z-function modules which you can use for coding your custom logic. But there's a lot in common for BDT and EEW - they both create the field groups, views, sections and screens when you enhance an object. You can use BDT to change titles such as tab name or section name after you have created the easy enhancement project for a particular object!