This action might not be possible to undo. Are you sure you want to continue?
Web Services and Document Templates in CRM o Creating Web Services in CRM (More details) o Creating Document Templates using Web Services in CRM (More details) o Transporting Web Services in CRM (More details) o Transporting Document Templates in CRM (More details) Creation of WEB UI Component and navigation with standard component (More details) NEW
Few more tutorials related to CRM:
Migrating Customer data along with relationships (CRM) using LSMW (More details) Configuration of CRM 7.0 Server with PI 7.0 (More details) Action Profiles in SAP-CRM (More details) Creation and configuration of Business Partners (More details) Adding Web URL (like google.com, yahoo.com) in CRM UI (More details) Configurations for opening an external URL (like SAP.COM) from IC WebClient. (More details) Difference between EEWB and BDT (More details)
Creating Web Services in CRM
By Vijender Sangwan
Go to transaction BSP_WD_CMPWB
Enter WS_DESIGN_TOOL as component and press TEST button. This will open the CRM Web UI in the new Browser.
Click on the New Button to Create a New Web Service, which we will use for Document Templates .
Enter the details as required. Enter the Component for which you want to create the Web Service.
In this Case it is for Business Transactions: i.e.: Agreements for Grant Management. Choose the Root Object also as Business Transaction. Press the Next Button. One important thing here, don‟t forget to click one of the Boxes at the end for Read, Create or Change. In this case we are creating a Web Service to read data from the database to read the Agreement details.
Select Attributes Structure will open where you can select the data you want from the Structure to be fetched when the Web Service is called. Expand the Business Transaction Node and Select the data as shown below.
Once a Node is selected, its attributes opens up on the Right Hand Side. Select the attributes like shown above as required. Once the Selection for a particular node is done, don‟t forget to click on the Confirm Selection Button as shown under the attributes window. If this Button is not clicked the attirbutes will not be selected and will be lost, once you move ahead.
Click on the Expert Mode Button and you will see the details on the Right Side. Press the Next Button. that have been selected. Once the selection is done. click on the Radio Button Exclude in front of that screen and the field will be excluded from the selection. click on the Next Button and it will take to the Maintain Attributes window. where we can review the fields. If there are some extra fields. If any field is missed.Make sure form the BOL Browser you know which fields you need from the Web Services from which node for the Document Templates. Previous Button can be clicked and the field can be selected again. . Once the Review is done fro all the fields.
Press the Activate Button to Activate the Web Service. .Now Click on the Save Button. The Web Services is required to be made active to be available by other Services. Once the Check is done. Once the Web Service is saved. Click on the Check Button to check for any errors or any issues with the Web Service. Press the Productive Button. The activation take some time as all the Function Modules and other related components for a Web Service are created. Once it is Activated.
The Save Button is required to save the Productive state of the Web Service.Once the Web Service status changes to Productive. else this state is lost and Web Service becomes Non Productive. Select Document Templates. Creating Document Templates using Web Services in CRM By Vijender Sangwan Log in to the Web UI and under the Administration tab. Click on the New Button to create a new Template . The Web Service is now ready to be used for other services.
Microsoft Word. We have created the Web Service for Agreements. click on start Designer A new word Document in editable mode is opened. as we are using Word Document template Name – Name of the Document Template Object type – BUS2000271. .The screen like above will be displayed to enter the details. Choose as appropriate. Enter the details as shown above. File Type . Once the details are entered.
Click on the Element showing in the bottom right Corner of the Window As you keep clicking it. . You can put them here in the window for display. it will take you into the Nodes you have selected in the Web Services.
Select all the fields you require for your Document .and design the document as required. Click on the save Button to Save the Document. . Once the Document is designed.
Create transport request for your web service via IMG->CRM-> UI framework -> UI framework definition -> Web services -> web service tool: transport service tools. Transporting Web Services in CRM By Vijender Sangwan You need to perform following steps to use document templates in other clients or in Quality/Production system: 1) Web service created in one client will not be available in other clients by default. close the document. The document is now ready to be used.Once the document is saved. .
Enter the name of Web Request and Press Execute
The TR is created for that Web Service. TR for multiple Web Requests can be created together.
In test client/Quality system /Prod system, you need to get test client open for changes. Go to transaction WSCONFIG; find your web service definition and variant. Click on Create and save default values on next screen.
3) For Quality or Prod system, release and import TR
Transporting Document Templates in CRM
By Vijender Sangwan
1. Select document templates that you want to transport, using Customizing link SPRO => SAP Reference IMG => SAP Implementation Guide => Customer Relationship Management => Basic Functions => Content Management => Transport Document Template
Or Run report 'CRM_KW_TEMPLATE_TRANSPORT' to select templates.
Press 'Transport' button after selecting the templates. Enter the transport request number that you have created. This will show all the Document Templates created for that Business Object.Enter the Business Object of the Document Template and execute the Report. This operation adds logical and physical details of the template to Transport request. You will be asked for correction request upon selecting 'Transport' button. .
Enter source client and transport request and press 'Start immediately to copy the request immediately.g. Go to SAP IMG Customer Relationship Management UI Framework UI Framework Definition Access BSP Component Workbench or transaction BSP_WD_CMPWB Enter component name (e. L&T Infotech Introduction: This document provides the step by step procedure of creating Custom WEB UI Component and navigation of custom component with standard one and vice-versa. Creation of WEB UI Component and navigation with standard component By Narendra Goyal. --BOL Programming --Creation of Windows --Creation of link --Custom Controller --Assigning standard component to custom . At the end. you will be able to do: Creation of Custom WEB UI Component Creation of view – Table view and Empty view Navigation between views and windows Component Controller Assigning custom component to standard component component Step 1. Go to target client in which you would like to import the template and run transaction 'SCC1' (Client Copy).Go to transaction 'SE09' and release transport request or ask the Basis Administrator to release the TR. ZBP) in field component and click on create. Enter the description and window name (e. Creation of WEB UI Component. Prerequisite: Need the basic knowledge SAP CRM. Choose a package and click on continue and provide workbench request.g. Otherwise press 'Schedule as Background Job' to run copy as background task. Your component will looks as given below. MainWindow) and click on continue.
Name – view name (e.g. Name – view name (e.Step 2. A wizard will be displayed. right click on view and choose create. Creation of Window. PARTNER) Model Attribute – Select all by clicking on View Type – Table View Check the checkbox for configurable (For selecting displayed fields from available fields) and click on complete to finish the wizard. PARTNER) Model Node – model node name (e. Creation of view. create another view to display the data with the following data in wizard. Similarly.g.g. Enter the following data in wizard. PARTNERLINK) View Type – Empty View Do not change on following screens and finish the wizard. BOL Entity – BuilHeader . In the component structure browser. Step 3.
A wizard will be displayed. Do not change on the following screen and finish the wizard. lr_window = me->view_manager->get_window_controller( ). method OP_TOLIST. Give outbound plug name (e. double click on partnerlink. <%@extension name="htmlb" prefix="htmlb" %> <htmlb:link id = 'Select' text = 'My Accounts' onClick = 'ONCLICK' /> Step 5.g. . endmethod. right click on outbound plug and choose create.In the component structure browser. For this write the given code. Enter the window name (e. Double click on PARTNERLINK view and in right hand side. Creation of outbound and inbound plug.htm to maintain the link. Step 4. In right hand side. TOLIST) Double click on OP_TOLIST method to implement. LINK). lr_window->call_outbound_plug( iv_outbound_plug = 'TOLIST' ).g. Maintain link in PARTNERLINK view Double click on PARTNERLINK view. DATA: lr_window TYPE REF TO cl_bsp_wd_window. right click on window and choose create.
WHILE lr_param_ent IS BOUND. if lr_result is bound. lr_param_ent TYPE REF TO if_bol_bo_property_access.g. lv_bp = lr_param_ent->get_property_as_string( iv_attr_name = 'BP_NUMBER' ). data: lv_bp type STRING. clear: lv_bp. lt_attr type standard table of char120. refresh: lt_param. lr_qs = cl_crm_bol_query_service=>get_instance( 'BuilHeaderSearch' ). lr_prop_bp TYPE REF TO if_bol_bo_property_access. CALL FUNCTION 'CRM_ERMS_FIND_BP_FOR_USER' EXPORTING IV_USER_ID = sy-uname IMPORTING EV_BUPA_NO = bp. lv_bp = bp. lr_result = lr_qs->get_query_result( ). result TYPE REF TO if_bol_entity_col. lr_param_ent = result->get_first( ). Double click on implementation DO_PREPARE_OUTPUT. if lr_entity is bound. lr_param_ent = result->get_next( ). bp. lr_qs->set_property( iv_attr_name = 'PARTNER' iv_value = LV_bp ). is assigned for this user lr_qs = cl_crm_bol_query_service=>get_instance( 'BuilHeaderSearch' ). bp. "used constant business partner as no bp no. lwa_param type CRMT_NAME_VALUE_PAIR. class of PARTNER view and implement the method method DO_PREPARE_OUTPUT. lv_bp = '404849'. free lr_qs. typed_context->PARTNER->build_table( ). ENDWHILE. data: lt_param type CRMT_NAME_VALUE_PAIR_TAB. lr_col TYPE REF TO if_bol_bo_col. IF lv_bp NE ''. result = lr_entity->get_related_entities( iv_relation_name = 'BuilContactPersonRel' ). lr_entity type ref to cl_crm_bol_entity. lr_entity = result->get_first( ).. lwa_attr type char120. Save and activate. ENDIF. endif. endmethod. bp type bu_partner. . right click on inbound plug and choose create.Double click on PARTNER view and in right hand side. FROMLINK). Give inbound plug name (e. DATA: lr_qs TYPE REF TO cl_crm_bol_query_service. result = lr_qs->get_query_result( ). lr_qs->set_property( iv_attr_name = 'PARTNER' iv_value = LV_bp ). endif. clear: lv_bp. typed_context->partner->collection_wrapper->add_collection( lr_result ). lr_result TYPE REF TO if_bol_bo_col.
Double click on MainWindow and in right hand side.g. Select fields to display from available fields. Step 7. Step 6. Provide the customizing request in the popup. FROMLINK). fire_outbound_plug( iv_outbound_plug = 'TOLIST' ). method OP_TOLIST. endmethod. Give inbound plug name (e. Select the fields which you want to display in output from available fields into displayed fields. Double click on PARTNER view. right click on outbound plug and choose create. OP_TOLIST( ). Click on EDIT. endmethod.g. Give event handler name (e. right click on inbound plug and choose create. Click on Save. In right hand side select configuration tab. ONCLICK) Double click on EH_ONONCLICK method to implement. Give outbound plug name (e.Double click on LINK window and in right hand side. TOLIST) Double click on OP_TOLIST method to implement. right click on event handler and choose create. . Refer from given below screen.g. method EH_ONONCLICK. Double click on PARTNERLINK view and in right hand side. Handling the event.
Now click on display. Go to transaction BSP_WD_CMPWB In the field component enter a name for a standard component (e. You can also create a new enhancement set by providing enhancement set name and click on create Enter the description and click on continue. WCC_SLS_HOME) and in field enhancement set enter a name enhancement set name (e.g. . then maintain enhancement set in cluster view (transaction SM34) BSPWDVC_CMP_EXT and in maintenance view (transaction SM30) BSPWDV_EHSET_ASG for respective client.g. ZEH_SET).Step 9. I am adding custom component (ZBP) in standard component (WCC_SLS_HOME). Adding custom component into standard component. Note: If you created a new enhancement set.
Click on continue. Add custom component ZBP in configuration In component structure browser. Select the custom component ZBP and click on move down button Now.g. . It will show the LINK view as a part of view set.Expand the view set WCC_SLS_HOME\SalesHome and navigate to the View Area.g. Click on save.ZBP/MainWindow). ZBP. But currently if you click on link „My Accounts‟ it will not work as navigation is still remaining. double click on view SalesHome. right-click on View Area and choose Add View. In the field View choose the view which you created (e. if you test standard component WCC_SLS_HOME. right-click on main window and choose Add View. In the field View choose the view which you created (e. Go to configuration tab and click on edit and provide customizing request. Step 10. ZBP. Expand the window and navigate to the main window.ZBP/LINK). Click on continue.
Go to the custom component which you have created in step1 i.g. right click on navigation link and select Add Navigation Link. Enter name (e. BOL Entity BuilHeader). Step 12. ZBP. Controller type (Custom Controller).g. add model attribute by clicking on and select all.g. PARTNER). ). Enter ID (e. ENDCASE. Do not change on the screens and finish the wizard.g.g. If prompted choose a package and enter workbench request.do) and target context node (PARTNER). method GET_P_BP_NUMBER. In component structure browser double click on PARTNER view. If prompted choose a package and enter workbench request. add model attribute by clicking on and select all. ZBP. Click on continue. source view (e.ZBP/LINK). TOLIST). Now. if you test standard component WCC_SLS_HOME. WHEN if_bsp_wd_model_setter_getter=>fp_fieldtype.g. Go to the attribute BP_NUMBER and implement GET_P_BP_NUMBER method. we will create buisness partner field as a link and on clicking on this. A wizard is displayed. CASE iv_property. right click on method WD_USAGE_INITIALIZE and choose redefine. In PARTNER view.g. BPPARTNER). In runtime repository editor. Enter BSP Application (e. Model node (e. ZBP). It will show the LINK view as a part of view set. . Create Navigation Link. As shown in above screen shot. Double click on the method to implement. custom controller (CUCOPARTNER. rv_value = cl_bsp_dlc_view_descriptor=>field_type_event_link. rv_value = 'SELECTION'. Click on save. Creation of a field value as a link in table view. ZBP). endmethod.ZBP/MainWindow) and inbound plug (e.g. CUCOPARTNER). Give plug name (e. Also when you click on link „My Accounts‟ it will show you available buisness partners. Click on continue and finish the wizard. ZBP. In component controller.g.g.e. A wizard is displayed. select radio button of model node and enter BOL Entity (BuilHeader). right click on outbound plug and choose create. FROMLINK). Double click on component controller and right click on context node and choose create. we are able to view details of buisness partner.Step 11. outbound plug (e. TOPARTNER). WHEN if_bsp_wd_model_setter_getter=>fp_onclick. In right hand side expand context node PARTNER. Enter custom controller name (e. Right click on custom controller and choose create. target view (e. following Now right click on context newly created context node BPPARTNER and choose create binding.
lv_usage = me->comp_controller->get_component_usage( iv_usage->usage_name ). endcase. " Implementation class of custom contr oller lr_entity TYPE REF TO cl_crm_bol_entity.method WD_USAGE_INITIALIZE. lr_core TYPE REF TO cl_crm_bol_core. CASE iv_usage->usage_name. DATA: lr_tcc TYPE REF TO ZL_ZBP_BSPWDCOMPONENT_IMPL. lr_cuwrp TYPE REF TO cl_bsp_wd_collection_wrapper. endmethod. . method OP_TOPARTNER. " Implementation class of comp onent controller lr_cuco TYPE REF TO ZL_ZBP_CUCOPARTNER_IMPL. double click on PARTNER view and select the outbound plug method OP_TOPARTNER to implement. lr_cuco ?= me->get_custom_controller( 'ZBP/CUCOPARTNER' ). DATA: lv_usage TYPE REF TO if_bsp_wd_component_usage. CHECK lr_cuco IS BOUND. lr_window TYPE REF TO cl_bsp_wd_window. WHEN 'CUBP'. In component structure browser. lv_guid TYPE bu_partner_guid. CALL METHOD lv_usage->bind_context_node EXPORTING iv_controller_type = cl_bsp_wd_controller=>co_type_component iv_target_node_name = 'BPPARTNER' iv_node_2_bind = 'PARTNER'.
lr_tcc->typed_context->bppartner->collection_wrapper-add( iv_entity = lr_entity iv_set_focus = abap_true ). view_manager->navigate( source_rep_view = rep_view outbound_plug = 'tobp' ). DATA: lv_index TYPE i. lr_core = cl_crm_bol_core=>get_instance( ). me->typed_context->PARTNER->collection_wrapper->find( iv_index = lv_index ). lr_entity ?= lr_cuwrp->get_current( ). method EH_ONSELECTION. CHECK lr_cuwrp IS BOUND. Implement the method EH_ONSELECTION. cl_thtmlb_util=>get_event_info( EXPORTING iv_event = htmlb_event_ex IMPORTING ev_index = lv_index ). CALL METHOD lr_entity->get_property_as_value EXPORTING iv_attr_name = 'BP_GUID' IMPORTING ev_result = lv_guid. SELECTION).lr_cuwrp = me->typed_context->PARTNER->get_collection_wrapper( ).g. op_TOPARTNER( ). run the transaction CRM_UI. endmethod. lr_tcc->typed_context->bppartner->collection_wrapper->clear_collection( ). lr_tcc ?= me->comp_controller. endmethod. . To test all scenarios. lr_entity = lr_core->get_root_entity( iv_object_name = 'BuilHeader' iv_object_guid = lv_guid CHECK lr_entity IS BOUND. Right click on event handler in PARTNER view and create the event handler (e. Click on My Accounts link.
It is a cross-platform component of the SAP system. which are combined according to business criteria instead of individual tables or field contents. Migrating Customer data along with relationships (CRM) using LSMW By Srinivas. The tool migrates user-defined datasets (known as objects). The document mostly covers the practical usage of LSMW with respect to Batch input Recording Method. . This document may be used to gain an insight of LSMW process in SAP CRM environment and may be used as a guide to help the consultants during the initial loading of master data into SAP database tables. 2 LSMW The Legacy System Migration Workbench (LSMW) is a tool that supports data migration from legacy systems (non-SAP systems) to SAP systems. the user-specific objects can be generated. Infosys 1 Introduction This document provides a simple and user-friendly step-by-step approach for working with LSMW. In addition to using standard import techniques. The tool has interfaces with the Data Transfer Center and with batch input and direct input processing as well as standard interfaces BAPI and IDoc.Click on business partner 404848 for detailed view.
The LSMW supports a one-time transfer of data (initial data load) and also offers a restricted support of permanent interfaces. The LSMW. Thus. . This is a hierarchy maintained in LSMW for all the data transfer done. however. Fig : LSMW-Process flow diagram 3 Creation of Project Hierarchy Use the Transaction Code LSMW to go to the initial screen. Create a project. does not include any functions for monitoring of permanent interfaces. The tool does not support any data export interfaces (outbound interfaces). corresponding subproject and object using Edit -> Create entry on menu bar. a periodic transfer of data is possible.
subproject and an object and click on continue.Fig-01: LSMW .create project hierarchy Create a project. The following screen is displayed with the Project hierarchy details: .
.Fig-02: LSMW. For this “User Menu” tab in the tool bar needs to be clicked and all the necessary steps required for data transfer need to be selected.Initial screen Once the project Hierarchy is being created. This can be changed depending on the requirement of the user. an enumeration of steps for data migration is displayed as shown in Fig-03 below.
Fig-03: LSMW initial screen with user menu for selection of various steps. 4 Step by Step Process for uploading BP master data: The screenshot as in Fig-04 displays the fourteen steps required for loading Business partner data along with their relationships: .
1 Maintain Object Attributes In this step a Recording needs to be created (using GOTO -> Recordings overview in menu bar as shown in Fig-05) using Transaction code BP. 4. .Fig-04: Fourteen steps involved in LSMW The following pages describe each of those fourteen steps and key points to be remembered in each step.
Once recordings overview is clicked the following screen as in Fig-06 will be displayed.Fig-05: Create Recording. . Enter a name and description to the recording.
Enter the transaction for which the recording is to be done as shown in Fig-07 .Fig-06: Enter details for the Recording.
Here the Business partner category needs to be chosen.Fig-07: Transaction BP has been entered. under which the customers should be created. Click on Organization as shown in Fig-08: .
Fig-08: Click on Organization Select a Grouping and a Business Partner number in that Grouping and the role under which the customers needs to be created. Enter all the necessary details for business partner that needs to be loaded from the flat file: .
Maintain relationships for the Business partner. Grouping and Role and other details entered. as shown in fig-10 if relationships also need to be mapped from flat file. .Fig-09: Shows Business partner number. “External Grouping for loading the Customers and Accounts” has been used.
Once all the details have been entered save the Business Partner and click on back icon to go to recording that we created. And let the other fields remain same whose values need to be defaulted to existing values.Fig-10: Displays three Relationships of BP number 1100. . Click on the fields displayed in orange color to change the name and default value of the fields.
Fig-11: Displays the first screen of Recording ZRECORDC .
Fig-12: Displays the second screen of Recording ZRECORDC .
Here the data is written into an IDoc and passed to the LSMW to get it imported into the system. Now once recording is done. 3. this is the first step of LSMW menu where the way or method of Import needs to be decided. 2. . There are generally four choices: 1. Standard Batch/ Direct Import Method . So the function module is responsible for the import of data into the system. 4.In this method a Recording of the transaction needs to be created which is later run as a Batch input Session.Direct insertion of data through Batch input programs. Business object Method (BAPI) .Fig-13: Displays the third screen of Recording ZRECORDC asking details for relationships. IDoc (Intermediate documents) . Batch input Recording method .Here the BAPI takes care of the data conversions and updating any database table.
enter a name and description to the source structure and click on continue.However This Document discusses the import of data through Batch input Recording Method. The LSMW system has to have the prior knowledge of what kind of data it is getting from the source that has to be imported into the system. For this reason the following three steps are very important that describe the structure of the files that has to be imported.2 Maintain Source Structure Go to main menu in LSMW as shown in Fig-04 and click on second step: Maintain Source Structure and the following screen as in Fig-15 will be displayed: Click on create icon. Fig-14: Choose the “Batch input recording” radio button and give the name of the recording that has been done earlier. . 4. Then save the object attributes. Then save the source structure and click on Back icon on the top of the screen.
3 Maintain Source Fields Go to LSMW Menu screen as shown in Fig-04 and Go to Third step: Maintain Source Fields. Select the source structure that was created and click on Table maintenance as shown in Fig-16 .Fig-15: Entering details of source structure 4.
. enter Field name. Data type and Length of all the fields under the required structure as it will appear in the input file. Role etc need not be maintained in this table and those fields need not be included in the flat file.Fig-16: Maintain Source Fields Once Table Maintenance has been clicked. Even it is important to keep the sequence of the fields according to their position in the file. that have constant value like Grouping. Give name to the fields and save it. Fields.
Here only the high level correspondence is shown . However the one to one mapping of the fields will take place in the next step.Fig-17: Enter details of source fields and save Generally it is important to keep the data type and size of the fields same as that of the corresponding field in database table. Save it and go to next step. However this might not be possible in all the cases.4 Maintain Structure Relations Go to LSMW Menu screen as shown in Fig-04 and Go to Next step: Maintain Structure Relations. The following screen as shown in Fig-18 will be displayed. then the issue needs to be handled through the conversion routines. 4. Structure relations are the mapping between the structures we have declared in the previous steps with the recording done.
. A simple way to do this is to select the field from recording and press the tab “Assign source field” which will give a list of fields in the source structure and then select the filed that needs to be mapped to field in recording.Fig-18: Structure relationship 4.5 Maintain Filed Mapping and Conversion Rules In the previous step the recording is mapped to the structure. Here each source field needs to be assigned to its corresponding target field in the recording side. There it automatically creates a one to one correspondence with the fields of both the sides and show in this stage as tree structure.
Fig-19: Field Mapping-Initial Screen .
d.7 Specify Files step is mentioning the file path to be selected for importing. c. Translations. User-Defined Routines Here the conversion rules for processing project data need to be defined. the next . b. e. f. fixed values and translation values can be assigned and definite variants for the conversion rules can also be specified here. User-Defined Routines j. Once the previous step of mapping each field to the source structure has been done. h.Fig-20: Field Mapping-Next Screen To maintain constant value to a field select that field in the recording and click on Constant (Ctrl+F9) Icon as shown in Fig-20 and a constant value can be assigned to that field. i. The system generates the conversion program from the structure and field relationships as well as the conversion rules. Fig-21: Maintain Fixed Values. k. The following fields have been assigned constant values as displayed below: a. g. 4. Grouping : 0002(PB Number Account & Customer –External) Role : 000000(Business partner-General) Time zone: PST Relationship category: FBUR001 Overview: A 4.6 Maintain Fixed Values. Translations. Customization required for migration of data also needs to be specified here. That is.
etc. other attributes of the file that is to be imported also need to be specified.8 Assign Files q. Fig-22: Specify the path for the file etc. o. this file needs to be assigned. m. There are other file-paths that can be mentioned. such as the file for imported data. if necessary we can choose to change the existing file path that has been defaulted.l. n. Here apart from the physical path. For example if it is a comma separated or tab delimitated file and if the file contains the field name as Start of File etc. 4. converted data. p. Once the file has been specified as in previous step. .
When it s run. This is a tab delimitated text file with header row. next step is to execute the program as shown in Fig-24 . s. For reference the test file that is imported is given below. Fig-23: Assign file t. However the successful import data can also be seen from the main menu. the above program gives the output as in Fig-25.9 Read/Import Data to import the data from the file and put in the structure maintained earlier. So in this step select source structure and then click on save. 4.r. Once assign the file has been assigned. u.
w. . Fig-25: Result of the execution of import program. Fig-24: Import / Read data x.v. y.
This take care of all the conversion earlier mentioned. Also the converted data can be seen as in Fig-29.ZRECORDC.4.Generate conversion program. it can be displayed using this step. Each row can be selected to see all the details of each customer. Convert data and display converted data.10 Display Read/Imported Data Once the data is imported. Fig-26: Display Imported/Read data 4. .11 Convert Data Once the data is imported to the structure then go to the next step in the main menu that is. system would display the following screen where all the imported data can be seen. This step converts the data executing above program and store it in the filename given earlier. The first step generates the program that converts the data imported into the structure to the structure of Recording . The result is shown as in Fig-27 & Fig 28. Once this step is selected and continue icon is clicked.
Fig-27: Convert Data .
. Once this step is selected and continue icon is clicked.13 Create Batch input session In this step a Batch input session needs to be created.Fig-28: Converted Data 4.12 Display Converted Data Once the data is converted. Each row can be selected to see more details of each customer. Click on execute. Go to main menu in LSMW as shown in Fig-04 and click on next step: Create Batch input session and the following screen will be displayed. Fig-29: Display of Converted Data 4. all the Converted data can be seen in this step. For creating a Batch Input Session. system would display the following screen where all the Converted data can be seen.
system will display the following screen with the number of transactions (Business Partners) being created. . Once execute is clicked.Fig-26: Intermediate screen showing the file path for creating Batch input Session.
So select the line item and click on process icon on top. Processing mode Display errors only has been used which would display any errors encountered during creating business partners.creating a Business Partner). 4.Fig-26: Intermediate screen showing the number of transactions created. For this it takes to the session over view screen as in Fig-27 and asks about the way of execution whether it should execute in the foreground or in the back ground.14 Run Batch input session This is the final step where system processes the session to get all the data upload into the database through the given transaction (here BP. Then the type of processing mode needs to be selected. A new window pops up as shown. .
In this document since BP transaction has been used. .Fig-27: Session overview and selection of Processing Mode. To see the Business Partner data updated in the system use Transaction SE16 and follow the steps as displayed in Fig-28. Fig-29 and Fig-30. Now all the business partners along with their relationship data can be seen that have been uploaded into the CRM System using Transaction BP. so it will create 450 Business Partners in SAP CRM Database tables. system will upload all the 450 Business Partners as in flat file into the respective database tables. Once this step is processed.
Fig-28: Transaction SE16 and enter table BUT000 .
. Enter the criteria and click on execute.Fig-29: Intermediate screen asking for certain criteria to display Business partners.
But XIF (EXTERNAL INTERFACES) is nothing to do with PI/XI in particular. I‟m not discussing the steps that are required for conversion. Configuration of CRM 7. Summery of Configuration details for both servers CRM and PI. this conversion takes place in XIF adapter which is inbuilt in CRM. CRM Server: Logical system name: SAPCRD RFC Destination Port Partner Profile PI Server: Logical system name: LOGSYS001 SAP + CRD (System Name) : PICLNT001 (pointing to PI server) : SAPPID with RFC destination PICLNT001 : Partner No: LOGSYS001 (Logical system of PI) .0 By Praveen Kumar Kurni.0 Server with PI 7. It is inbuilt in CRM which handles conversion part. Yash Technologies As CRM server produces BDoc instead of IDoc.Fig-30: Business partners uploaded into SAP CRM Database tables.
RFC Destination: PICLNT001 Connection Type: 3 ABAP Connection Since we are connecting two SAP Servers we will go for this Connection type. Under Technical Setting provide the following: Target Host: pidev (Server Name) System No: 00 IP address: 10. Beneath Attributes there will be the entries 'gateway hostname' and 'gateway service'. . (Actual IP Address of the PI server) Gateway Host: pidev Gateway Service: sapgw00 (sap + gw + System No) How to find out Gateway Service for any Server? Open transaction SMGW and choose Go to -> Parameters -> Display.RFC Destination IDX1 : SAPCRD : SAPCRD (Must be RFC destination: Probably Logical system name of CRM server) IDX2 Configuration Steps: 1. RFC Destination PICLNT001 in CRM : Maintained .80. RFC Destinations in CRM: Use TCode SM59 Provide the RFC Destination name preferably logical system name of the PI Server.
Provide the port name as SAPPID . Port Configurations in CRM: Use TCode WE21 Select Transactional and press create on the menu. If you test the connection with wrong password 3 times PI server gets locked for this user without your knowledge. 2. This facilitates the authentication to connect PI Server using particular RFC Destination: PICLNT001 Note: Beware with caps lock while providing password.Logon & Security: We provide the login details of the PI server.
US (User) Agent: user name of CRM server . Partner Profile: Use TCode: WE20 Select the Partner type LS and press create. Provide the following details Partner No: LOGSYS001 Partner Type: LS Under post processing permitted agent tab Ty.SAPPID SAP + PID (PI Development) Provide RFC destination which we create in TCode SM59 PICLNT001 3.
Connection type: 3 ABAP Connection. Configurations in PI server: 1. Similarly add message type which you want to receive from PI in the Inbound parameters table Partner Profile: Outbound Parameters Provide the Receiver Port as SAPPID Port name that we defined in TCode WE21 Select the option Transfer IDoc immediately option. Target Host name : crmdev IP Address: 10. With that we finish configuring CRM server. Example: CRMXIF_PARTNER_SAVE_M Note: CRMXIF in the message type this is due to XIF inbuilt adapter available in CRM. (Actual system IP Address of CRM Server) Gateway Host : crmdev System No: 00 Gateway service: sapgw00 . Add the message type which you want to send from CRM to PI in outbound parameters table.80. . Provide the IDoc basic type for the message type. RFC Destination in PI Server: Use TCode: SM59 RFC Destination: SAPCRD.
What happens if you provide you own name instead of RFC name as port name? Please see handling error section of this tutorial. 2. Port: Use TCode: IDX1 Port: SAPCRD RFC Destination : SAPCRD Note: There should be only one port name that should be pointing CRM server with the system details.Login/Security: Provide the Logon details of the CRM system. . Q.
Solution: We send IDocs from system CRD to PI. In the control record (Segment EDIDC40) of the IDoc. The system ID and client are then used to determine a service without party of the type (business-system/business-service) .3. error messages are issued in sending system (TCode SM58) for the function module IDOC_INBOUND_ASYNCHRONOUS. Meta Data Overview for IDOC Adapter: IDX2 Customer Distribution Model in CRM system: BD67 Handling common errors shown in SM58 of CRM 7. As we don‟t configure any sender IDoc adapter in PI server this is where we resolve IDoc related issues in common.0 while sending IDoc’s When we send IDoc from sender CRM server to PI server. the SNDPOR (Sender Port) field contains the value "SAPCRD". Error message: No service for system SAPCRD client 201 in the integration directory Cause: There is no service without party in PI server that represents CRM server with client details. Let‟s discuss common errors cause and solutions for the same. The client of the sending system is determined by the MANDT field of the control record.
As we discussed above Integration Server is determined by the value of the “SNDPOR” field from the IDoc control record. RFC destination Solution: The Integration Server tries to load the IDoc metadata from the sending system. Then Business System can be imported under service without party/update the details existing in PI. Check with system administrator and assign necessary roles for the user. Standard IDoc schemas from the Integration Repository cannot be used because they are release-dependent. This must be unique and matching with RFC destination in CRD (for ex: SAPCRD) please avoid common names like RFCTOPI. Error message: "::000" This error occurs if the central XI system tries to load the IDoc metadata from the sending system by RFC. RFC2PI. Error message: NO_EXEC_PERMISSION: "User" "Business System" Solution: ‘User’ is not in the list of Users list created in the directory who are authorized to use ‘Business System’ 1 INTRODUCTION 1. Verify IDoc type in TCode : WE30 whether New IDoc segments added are released. Transaction IDX1: Port SAPXYZ. Error message. Create a business system for this technical system. so we get the above incomplete error. Data elements that do not exist in the DDIC are assigned to fields in the segment. IDoctyp/Cimtyp cannot be loaded. client 201.In System Landscape Directory (SLD) create a technical system for CRD system and assign a client for the same. Check for the user login details and also which client is used for login. Then it can import the IDoc metadata from the sending system using the “SNDPOR” field neglecting the standard IDoc schema that got imported in to PI. Possible reasons for the above error: 1. This implies sender RFC destination in CRD and Port in Integration Server should be same. Segments that no longer exist in IDoc should be removed. 3. which is similar to that of the RFC Destination created in CRD.1 ACTIONS . 2. Error is not transferred in full by the tRFC completely. user login fails for the sending system. We will create a port in IDX1 in Integration Server. Don‟t forget to assign an “ALE logical system” to the technical system created. Authentication failure for user login. But there might be several reasons for this error.
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. Actions are stored as action definitions within an action profile. We can schedule and start predefined conditions with the Actions component by means of user-definable conditions from transaction and marketing objects. which can be automated with the initiation of outputs. Actions use the Post Processing Framework (PPF). follow-on documents or workflows. Creation date . you can display a list of actions that can be included in the business transaction. create new items. The following information is displayed in the list for each action: Status (action scheduled. a Basis component. You can display a list of actions scheduled for the document on the Actions tab page of a transaction document. or status inheritance by subordinate elements in marketing objects Output in print. action processed) Description (purpose of action) Conditions (settings for action definition and conditions are displayed) Creator. by faxing or e-mail Actions are displayed in transaction documents that support actions and to which an action profile is assigned. Using the Actions tab page within a business document. 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. An action profile is determined from the corresponding transaction type or item category. for example.Actions are used in maintaining and improving business relationships. With actions you can: Create follow-up transactions automatically Execute changes in the transaction or marketing object currently being processed.
You can use the graphics tool. letters. Data retrieval and form logic are separated from one another. You can define your own BADI implementation to adapt actions to your processes and needs. Smart Forms SAP Smart Forms must be used to print. and e-mail) Form CRM_ORDER_LEASING_01 (suitable for faxes. letters. and e-mail) Form CRM_OPPORTUNITY_01 (suitable for faxes. SAP Smart Forms. SAP delivers several Smart Forms for outputs in SAP CRM: Form CRM_ORDER_CONFIRMATION_01 (suitable for faxes.) 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.There are various processing types for actions: Methods (Business Add-Ins) Methods are Business Add-In (BADI) implementations. the application program obtains the relevant data to be used and prints it on the form. letters. a follow-up transaction that includes an approval process. e-mail or fax documents such as an order confirmation. . When you request a printout of a form. and e-mail) SAP Smart Forms offer the advantage of adapting forms without requiring programming knowledge. to design the layout of output forms. thanks to a completely graphical user interface. (EXEC_METHODCALL_PPF is the relevant BADI. for example.
.1 Enter into any SAP-CRM Server and move to Transaction SPRO. 2.SAP Smart Forms replace SAP-Script forms (migration from SAP-Script forms to Smart Forms is supported).0 HOW TO CREATE AN ACTION 2.2 Press SAP Reference IMG -> Customer Relationship Management ->Basic Functions -> Actions -> Actions in Transactions.1. 2.1 STEP-BY-STEP PROCEDURE 2.1.
1.1.3 To create an Action Profile – Click on documentation.4 Now Press the Execute Button to start creating an Action Profile.2. . First read the 2. .
1.5 Click . 2. . Enter the Details to create Action.6 Click .1.2. Enter the Details to create Action Profile.
2. Enter the Details to set Action.7 Click . .1.
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. .In the Processing Time Details. Processing when saving a Document gets started when the document is saved.
9 Click and select the Processing. 2. If not. .2.1. Partner Dependent makes this Action as dependent on Partner. for which the action triggers. The processing that we select is the one on which we want the Action to work on.8 Click . The partner you choose is the one.1. It first checks whether that Partner exists or not. it throws an ERROR. Enter the Details to Set Up Partner Determination.
Processing can be of various types such as:- Select the one you want. For this case select Workflow. .
2.2. .1.1. 2.1.10 Click and Enter the Workflow Number that you want to assign with this Action.12 Click and assign Schedule Condition.11 Click and Enter Action Description.
It is not mandatory to assign a 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. Select anyone that suits your requirement and proceed further. .
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.
and Action Configuration is complete.
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.
Enter a Condition.Click Edit Condition to enter a condition. .
. Save it in the same Transport Request as Earlier.Click „√‟. Click on SAVE.
And hence. Similarly. you define number ranges for business partners. 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. this completes your Action Profile Creation for a Workflow. . It describes the interpretation of the SAP CRM object Business Partner (abbreviated BP). Number ranges for business partners are valid throughout a client. The defined number ranges are assigned to groupings in the Define groupings and assign number ranges activity. Accenture Introduction This document is the Business Process Design of the Business Partner Master data for SAP CRM. we can create Action Profiles for other processing also. Creation and Configuration of Business Partners By Krishna Prathyusha Jataprolu.
Choose Change Intervals 3.Procedure 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 2. Access the activity using one of the following navigation options: 1. . Choose Insert Interval.
Select Check Box Ext if External Number range is required 6. Enter the Interval ID and range 5. Defining Groupings Use Assign each business partner to a grouping when you create the business partner. Save your Entries Result: The Number ranges are defined as needed for different kinds of roles of Business Partner. This grouping determines the number range. Procedure 1. To carry out the activity.4. You cannot change this assignment at a later stage. choose one of the following navigation options: SAP CRM Transaction code IMG path Defining Groupings SPRO CRM Cross-Application Components SAP Business Partner .
To carry out the activity. 3. Result: All the Number Ranges defined are assigned to a group with a particular naming convention. number range and select the check box External. 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 . In the business partner dialog you can select from all of the business partner roles provided.Business Partner Basic Settings Number Ranges and Groupings Define Groupings and Assign Number Ranges 2. 4. Defining Business Partner Roles Definition: Business Partner role Rights and responsibilities that a business partner can have in various business transactions. you can hide the other business partner roles. You can replace the standard title of business partner roles with customer-defined names Procedure 1. which are used in Grouping Tab in Easy Access Screen of Business Partner. Enter the grouping. you make the settings for the properties of business partner roles. description. In this activity. If you only want to display certain business partner roles in the selection list. Save your entries. Choose New Entries. short name.
6. If you want to give the selected business partner role a different title to the standard title. Role Name Category (Person/Org/Group) Employee Person Remarks Use of Standard role Employee . Select the required Business Partner Role. Save your Entries 8. 5. The following roles will be used in SAP CRM: 9. Define the position where the business partner role is to appear in the selection list. enter the required Customer title under Title. Set the indicator Hide if the business partner role is not to appear in the selection list. 4.2. Select New Entries. 7. 3.
11. 13. Procedure 15. 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 14. Result. 10. Checking Business Partners BP Master Data Business Partner Maintain Business Partner Go To create Person . Access the activity using one of the following navigation options: SAP CRM Role Menu Transaction code SAP Menu 16. 2. 1. 12.Contact person Sold to Parry Person Person/Organization Use of SAP standard role contact person 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.
Enter all the required data. like Title. 3. In the field display Role Choose sold to party and in Grouping Choose Customers Grouping 19. 18. Address and also the data as required the other tabs .17. Name.
Accenture 27. Google.com.20. Business Partners are created with required roles. Yahoo. Save the entriy.g. yahoo. Web URL (E. By G. etc) in CRM UI can be launched using transaction launcher 28. 23.Vijayalakshmi. 25. Result. 4. 21. 5. Step1: 29. 22. Adding Web URL (like google. 24. Step1a: Call Transaction SM30. Enter the View name: CRMV_IC_LTX_URL .com) in CRM UI 26. Repeat the same for different roles.
URL: ZGOOGLE (any name starting with Z) Google Get for Non-BSP URL http://www. Request Method: 35.com . Step1b: 32. 31.30. Description: 34. Click radio-button 36. URL ID: 33.google.
IMG path CRM -> UI Framework -> Technical Role Definition -> Configure Transaction Launcher . 39.37. Step2: 40. Step2a: 41. 38. Or 43. Call transaction CRMC_UI_ACTIONWZ 42. Save the entry.
(Any name starting with Z) 48. Launch Trans. Click on Continue. ID : Zlaunch_google. 46.45. Component Set 49. : ALL . Step2b: 47.
53. 56. 54. 51. Activate checkbox for „Stateful‟ to show the URL in a new window. 55. Click on Continue . Description : launch google Class name : ZCL_CRM_LAUNCH_GOOGLE (Any class name starting with Z). 57. Be sure that the checkbox „Raise Veto‟ is deactivated.50. Step2c: 52.
62. Choose URL Transaction (B) as transaction type 61. Continue .58. URL ID: ZGOOGLE created in the URL repository. 59. Step2d: 60.
Step3: 68. Execute Transaction CRMC_UI_NBLINKS 70. Step2e: 65. Or 71.63. 64. End the wizard and press „Complete‟. 67. Skip screen for transaction parameters and activity clipboard by pressing „Continue‟. IMG path CRM -> UI Framework -> Technical Role Definition -> Define Navigation Bar Profile . Step3a: 69. 66.
79. 81. Select „Define Logical Links’ at the dialog structure on the left by double-click. 77. 74. 80. Create a new logical link: 75. 76. 78. Logical Link ID: ZGOOGLE Type: Target ID: Parameter Parameter Class: Title: Description: Launch Transaction EXECLTX ZGOOGLE CL_CRM_UI_LTX_NAVBAR_PARAM Google Google . 73.72.
84. Group Type 89. Create a new entry 95. 98. Group ID 88. Select „Define Direct Link Groups’ 86. Title 90. Logical link ID : ZGOOGLE (Which has been defined in Define Logical Links) 96.82. Step3b: 85. . 91. 92. 83. 99. 94. Position : 10 97. Create a new entry 87. Save the changes. Step3c: 93. Select „Assign Links’ at the dialog structure on the left by double-click. Add the link which was created in Define Logical Links. Description : ZGOOGLE : No Classification : Google : Google. Save the changes.
Click „Assign Direct Link Groups’ at the dialog structure on the left Create a new entry Group ID : ZGOOGLE Position : 30 (any position). 101. 103. .100. 105. 106. 108. 107. Step3d: Select „Define Profile’ Select profile corresponding to web UI 104. 102.
109. 111. . 110. Step4: Execute Transaction CRMC_UI_PROFILE or go to IMG path CRM -> Business Roles -> Define Business Role.
113. Select business role ZWOOSALESPRO (the role which is assigned to user) 114. Double-click on „Visible Direct Group Links‟ at the dialog structure on the left. 116. 115. Click Visible Check Box corresponding to Group ID ZGOOGLE .112.
e ZTXID_SDN . i. 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' . 119.enter the basic details and select 'Launch Trans' radio button and select the transaction id created in step 2 . For this go to 'Define Navigation Bar Profiles' under Basic Functions. Configurations to open an external url (like SAP.e ZSDN.you need to create a URL ID. i. Click on Define Entries .117. Step5: In the Web UI the link appears as shown below. Now you need to map the URL transaction ID to Navigation Bar profile entries.and under details area select the URL ID you have created in step 1. 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 . 118. Complete the wizard.com) from IC WebClient Web URL inside CRM IC Web BSP view can be launched using transaction launcher.
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. views. is used to add/delete/disable fields in the BP transaction only. sections and screens when you enhance an object. 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 . BDT as a separate unit in CRM (TCode BUPT) has several useful tools like BP events which are useful at times. It does not create new objects for the developer to play with. Difference between EEWB and BDT BDT.they both create the field groups. 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. among other things. 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! .
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue listening from where you left off, or restart the preview.