- Difference between EEWB and BDT
- Configurations for opening an external URL (like SAP.COM) from IC WebClient.
- Adding Web URL (like google.com, yahoo.com) in CRM UI
- Creation and Configuration of Business Partners
- Action Profiles in SAP-CRM
Tuesday, August 30, 2011
Customer Relationship Management (CRM),
Difference between EEWB and BDT
Difference between EEWB and BDT
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!
Configurations for opening an external URL (like SAP.COM) from IC WebClient.
Configurations to open an external url (like SAP.com) from IC WebClient
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.
Adding Web URL (like google.com, yahoo.com) in CRM UI
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: ZGOOGLE (any name starting with Z)
Description: Google
Request Method: Get
Click radio-button for Non-BSP URL
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 : ALL
Click on Continue.
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: Launch Transaction
Target ID: EXECLTX
Parameter ZGOOGLE
Parameter Class: CL_CRM_UI_LTX_NAVBAR_PARAM
Title: Google
Description: Google
Save the changes.
Step3b:
Select ‘Define Direct Link Groups’
Create a new entry
Group ID : ZGOOGLE
Group Type : No Classification
Title : Google
Description : 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
Save the changes.
Add the link which was created in Define Logical Links.
Step3d:
· Select ‘Define Profile’
· Select profile corresponding to web UI
· 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.
· Select business role ZWOOSALESPRO (the role which is assigned to user)
· Double-click on ‘Visible Direct Group Links’ at the dialog structure on the left.
· Click Visible Check Box corresponding to Group ID ZGOOGLE
Step5: In the Web UI the link appears as shown below.
Creation and Configuration of Business Partners
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
Defining Number Range
In this activity, you define number ranges for business partners.
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 | Defining Number Range for Org Business Partners |
Transaction code | SPRO |
IMG Path | Cross-Application Components à SAP Business Partner à Business Partner à Basic Settings à Number Ranges and Groupings à Define Number Ranges |
2. Choose Change Intervals
3. Choose Insert Interval.
4. Enter the Interval ID and range
5. Select Check Box Ext if External Number range is required
6. Save your Entries
Result:
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 | Defining Groupings |
Transaction code | SPRO |
IMG path | CRM à Cross-Application Components à SAP Business Partner à Business Partner à Basic Settings à Number Ranges and Groupings à Define Groupings and Assign Number Ranges |
2. Choose New Entries.
3. Enter the grouping, short name, description, number range and select the check box External.
4. 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 | Defining Groupings |
Transaction code | SPRO |
IMG path | CRM à Cross-Application Components à SAP Business Partner à Business Partner à Basic Settings à Business Partner Roles à Properties of Business Partner Roles |
2. Select New Entries.
3. Select the required Business Partner Role.
- 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.
- Save your Entries
The following roles will be used in SAP CRM:
Role Name Category (Person/Org/Group) Remarks
Employee | Person | Use of Standard role Employee |
Contact person | Person | Use of SAP standard role contact person |
Sold to Parry
| Person/Organization
| Use of SAP standard role sold-to party
|
Prospect | Person/Organization
| Use of SAP standard role prospect |
Ship to Party | Person/Organization | Use of SAP standard role Ship to Party
|
Bill to Party | Person/Organization | Use of SAP standard role Bill to Party
|
Retailer | Person/Organization | This role will be used to register the retailers.
|
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 client’s requirement.
Creating a Business Partners
Procedure
1. Access the activity using one of the following navigation options:
SAP CRM Role Menu | Checking Business Partners |
Transaction code | BP |
SAP Menu | Master Data à Business Partner à Maintain Business Partner |
2. Go To create Person
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.
Business Partners are created with required roles.Action Profiles in SAP-CRM
1 INTRODUCTION
1.1 ACTIONS
Actions are used in maintaining and improving business relationships. 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.3 To create an Action Profile – Click on . First read the documentation.
2.1.4 Now Press the Execute Button to start creating an Action Profile.
2.1.5 Click . Enter the Details to create Action Profile.
2.1.6 Click . Enter the Details to create Action.
2.1.7 Click . Enter the Details to set Action.
In the Processing Time Details, there are 3 Options.
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 . Enter the Details to Set Up Partner Determination.
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.
Processing can be of various types such as:-
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 and Enter Action Description.
2.1.12 Click and assign Schedule Condition.
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.
Select anyone that suits your requirement and proceed further.
2.1.13 Click and assign Start Condition.
Start Condition is checked before an action is executed. The Action is executed only if the Start Condition is satisfied.
Here you won’t be able to assign a Start Condition; there is another tab in Actions where we can assign Start Condition.
2.1.14 Click and Action Configuration is complete.
Click and save it in a Transport Request.
2.1.15 To assign Start Condition -> Go-to step 2.1.2 -> Click on Change Actions and Conditions -> Define Conditions.
In Scheduling of Actions, find your Action – Test an Action Profile.
It shows you the entire Action that you created till now.
To assign start condition, Click on Start Condition Tab.
Click Edit Condition to enter a condition.
Enter a Condition.
Click ‘√’.
Click on SAVE. Save it in the same Transport Request as Earlier.
And hence, this completes your Action Profile Creation for a Workflow.
Similarly, we can create Action Profiles for other processing also.
Automation Testing
- Manual and Automation testing Challenges
- What you need to know about BVT (Build Verification Testing)
- BVT types
- Learning basics of QTP automation tool and preparation of QTP interview questions
- QuickTest Pro - QTP Functional testing tool review
- Tips you should read before automating your testing work
- Choosing Automation tool for your organization
Blog Archive
-
▼
2011
(392)
-
▼
August
(94)
- Customer Relationship Management (CRM),
- Difference between EEWB and BDT
- Configurations for opening an external URL (like S...
- Adding Web URL (like google.com, yahoo.com) in CRM UI
- Creation and Configuration of Business Partners
- Action Profiles in SAP-CRM
- Production Planning (PP)
- Difference between Co-Product and Bi-Product with ...
- Types of Subcontracting
- Routing Vs Task list Vs Work Procedure
- Converting Planned Orders to Purchase Requisitions...
- Production Order Splitting
- Repetitive Manufacturing Cycle
- Typical Production cycle in Process Industry
- MRP Run in background for all Network Plants
- SAP Financials (FI)
- Check duplicate creation of Vendor Master that hav...
- Validation rules in FI
- Defining Asset Number Range
- Steps to configure Document text in Customer Invoi...
- Understanding Lockbox
- Information on FICA (Finance and Contract Accouting)
- Difference between MTS and MTO
- Comparison of FI and FICA
- Sales And Distribution (SD),
- Configuring "Availability Check"
- SD Terms "Sales Organization", "Distribution Chann...
- Maintaining Multi-level packaging in the delivery
- Enterprise Structure Configuration
- Configuration of Pricing Procedure
- Difference between CASH SALES and RUSH ORDER
- Order to Cash Cycle
- Differences between Credit Note, Credit Memo and C...
- Credit Card payment configuration for the orders
- Temporarily extending/reducing the credit limit
- MRP: PR to PO conversion
- Maintaining Shipping instructions
- Understanding "Material Determination"
- Assigning different customer number ranges for dif...
- Variant Configuration for a BOM
- Scheduling agreement to invoice cycle
- Output determination configuration
- Business Process Procedure for standard third part...
- Material Listing and Exclusion
- Automatic Printing of a Sales Order Document immed...
- Configuration steps for: Automatic batch determina...
- Configuration steps for: Automatic Packaging
- Configuration steps for: Automatic Picking
- SD Questionnaire
- Solution Manager
- Experience from Implementation
- Billing
- Cross-application customization
- Pricing
- Shipping
- Master data
- Sales
- Enterprise Structure
- Letter of credit process in Export
- Condition Exclusion
- Condition value from Custom Routine for Sales Orde...
- Release strategy for sales document using status p...
- Prevent adding extra materials during the creation...
- SQL Topics
- SQL: VIEWS
- Oracle/PLSQL: Foreign Keys
- Oracle/PLSQL: Primary Keys
- SQL Topics: Tables
- SQL: DELETE Statement
- SQL: UPDATE Statement
- SQL: INSERT Statement
- SQL: MINUS Query
- SQL: UNION ALL Query
- SQL: INTERSECT Query
- SQL: UNION Query
- SQL: Joins
- SQL: ORDER BY Clause
- SQL: GROUP BY Clause
- SQL: HAVING Clause
- SQL: BETWEEN Condition
- SQL: EXISTS Condition
- SQL: "IN" Function
- SQL: Combining the "AND" and "OR" Conditions
- SQL: LIKE Condition
- SQL: "OR" Condition
- SQL: WHERE Clause
- SQL: "AND" Condition
- SQL: MIN Function
- SQL: MAX Function
- SQL: COUNT Function
- SQL: SUM Function
- SQL: DISTINCT Clause
- SQL: SELECT Statement
- SQL: Data Types
-
▼
August
(94)