Lead Creation

hi all
how can create transaction(Lead or Activity) using ELM? for creation of target group iam getting properly. when iam selecting the create transaction it shows prob. any thing required for creation of transaction .which fields is required for mapping for transaction.how can we create lead using ELM plz give me step by step (or) any help
thanks in advance
regads
sreedhar

Hi Sreedhar,
I guess you are going wrong with the campaign id. Please change the campaign id in the notepad before you map the data, so that it matches the campaign id existing in your system.
I.e, instead of C/9100-INT-100 (this is our campaign id), you have to replace this with the campaign id in your system which is already existing.
You will not get any errors if you follow the same process. Only 1 or 2 fields like this might need to be changed according to your system.
Otherwise the process steps in the document would remain the same.
Do appreciate helpful answers with more reward points
Thanks.
Sindhu.

Similar Messages

Parameters not gettin passed while lead creation..........

Hi...
             I am passing the values of the fields SOURCE and IMPORTANCE in the exporting parameter IT_LEAD_H to the FM CRM_ORDER_MAINTAIN while lead creation...When I check the CRM_LEADH table I find that these values arent gettin reflected ...The guid and the leadtype are gettin saved but the values of these two fields are not present...This is the code I'm using.....
CT_ORDERADM_H
    ls_orderadm_h-handle        = '1'.
.   ls_orderadm_h-PROCESS_TYPE = 'LEAD'.
    ls_orderadm_h-mode          = 'A'.
    INSERT ls_orderadm_h INTO TABLE lt_orderadm_h.
build table with change fields
    FREE lt_input_field_names.
    ls_input_field_names-fieldname = 'PROCESS_TYPE'.
    INSERT ls_input_field_names INTO TABLE lt_input_field_names.
    ls_input_field_names-fieldname = 'MODE'.
    INSERT ls_input_field_names INTO TABLE lt_input_field_names.
    CLEAR ls_input_fields.
    ls_input_fields-ref_handle = '1'.
ls_input_fields-objectname = 'ORDERADM_H'.
    ls_input_fields-field_names = lt_input_field_names.
    INSERT ls_input_fields INTO TABLE ct_input_fields.
CRMT_LEAD_H_COMT
IF IT_LEAD_H IS INITIAL.
    ls_lead_h-ref_handle     = '1'.
    ls_lead_h-SOURCE         = '002'.
    ls_lead_h-IMPORTANCE     = '2'.
ENDIF.
    INSERT ls_lead_h INTO TABLE lt_lead_h.
build table with change fields
    FREE lt_input_field_names.
    IF ls_lead_h-SOURCE IS NOT INITIAL.
      ls_input_field_names-fieldname = 'SOURCE'.
      INSERT ls_input_field_names INTO TABLE lt_input_field_names.
    ENDIF.
    IF ls_lead_h-IMPORTANCE IS NOT INITIAL.
      ls_input_field_names-fieldname = 'IMPORTANCE'.
      INSERT ls_input_field_names INTO TABLE lt_input_field_names.
    ENDIF.
    CLEAR ls_input_fields.
    ls_input_fields-ref_handle = '1'.
    ls_input_fields-ref_kind    = 'A'.
    ls_input_fields-objectname = 'LT_LEAD_H'.
    ls_input_fields-field_names = lt_input_field_names.
    INSERT ls_input_fields INTO TABLE ct_input_fields.
IT_STATUS
IF is_status IS INITIAL.
    ls_status-ref_handle     = '1'.
    ls_status-status         = STATUS.
   ls_status-user_stat_proc = 'CRMLEAD'.
    ls_status-activate       = 'X'.
   ls_status-process        = 'ACCI'.
ENDIF.
    INSERT ls_status INTO TABLE lt_status.
build table with change fields
    FREE lt_input_field_names.
    IF ls_status-status IS NOT INITIAL.
      ls_input_field_names-fieldname = 'STATUS'.
      INSERT ls_input_field_names INTO TABLE lt_input_field_names.
    ENDIF.
    IF ls_status-activate IS NOT INITIAL.
      ls_input_field_names-fieldname = 'ACTIVATE'.
      INSERT ls_input_field_names INTO TABLE lt_input_field_names.
    ENDIF.
    CLEAR ls_input_fields.
    ls_input_fields-ref_handle = '1'.
    ls_input_fields-ref_kind    = 'A'.
    ls_input_fields-objectname = 'STATUS'.
    ls_input_fields-field_names = lt_input_field_names.
    INSERT ls_input_fields INTO TABLE ct_input_fields.
ENDIF.
bring changed fields with values to object layer
CALL FUNCTION 'CRM_ORDER_MAINTAIN'
    EXPORTING
      it_lead_h         = lt_lead_h
      it_survey         = it_survey
      it_status         = lt_status
    CHANGING
      ct_orderadm_h     = lt_orderadm_h
      ct_orderadm_i     = lt_orderadm_i
      ct_input_fields   = ct_input_fields
    EXCEPTIONS
      error_occurred    = 1
      document_locked   = 2
      no_change_allowed = 3
      no_authority      = 4
      OTHERS            = 5.
Are there any other parameters that I have to pass?Plz suggest a solution for this......

Hi Francois,
Thank you for looking into the issue. Your first response was did you try get_form_field. Yes I did, and it did not work. I realised later (hopefully correctly) that get_form_field will work only if the field below is treated as an input field within <htmlb:form> and </htmlb:form>.
I shall re-explain the scenario. In default.htm, I enter an IDoc Number(input field) and click submit button. In the <form action > I have mentioned idoc.htm page. In idoc.htm, in On Initialization , I create a tree.
Method of creating tree
a) I create a table of type TVIEWNODE and populate the relevant details, except for the link field. The parameters that needs to be passed to the next page is a structure. In order to achieve this(I found this method in one of the posts in the forum),
Step I -- Serialize the structure data using CL_BSP_UTILITY=>SERIALIZE_DATA and fill a table LT_PARAMETER_LIST.
Step II -- I then construct a URL using CL_BSP_RUNTIME=>IF_BSP_RUNTIME~CONSTRUCT_BSP_URL passing APPLICATION NAME, 'SEGMENT.HTM' and table LT_PARAMETER_LIST.
Step III -- This method returns a URL which is then appended in the TVIEWNODE table and the tree is created.
The tree is created perfectly and the links are perfect as well.
However as mentioned in my earlier post when I click on the link, the URL shows all the attributes but I am not able to fetch the same using GET_ATTRIBUTE method or GET_FORM_DATA method.
Next point mentioned was create an attribute. This is an interesting point that you have mentioned. In page attributes, when I try pa_s_idoc-segnam, it mentions special characters not allowed.
I will explore the possibility of creating fields of internal table as page attributes i.e. using SEGNAM instead of pa_s_idoc-SEGNAM and then pass values to these.
If there are any other solutions do let me know.
Thanks again, Francois.

Lead Creation Error thro ABAP Code

Hi CRM ABAP Experts,
I have written a code for lead creation by referring SDN Code. when i execute code , lead is created and transaction get saved in to system. but atlast one error comes. plz help me. when i pass testrun = 'X' then i am not getting error but lead trasaction is not created. and when i passedtestrun = blank then lead is created but gives below error.Below error i am facing.
Short text
    An exception occurred that was not caught.
What happened?
    The exception 'CX_OS_OBJECT_NOT_FOUND' was raised, but it was not caught
     anywhere along
    the call hierarchy.
    Since exceptions represent error situations and this error was not
    adequately responded to, the running ABAP program
     'CL_METHODCALL_PPF=============CP' has to be
    terminated.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_OS_OBJECT_NOT_FOUND', was not
     caught in
    procedure "IF_MEDIUM_PPF~EXECUTE" "(METHOD)", nor was it propagated by a
     RAISING clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    Could not find the referenced object with the OID
    "00000000000000000000000000000000" (instance GUID) and
My Code is as follows
DATA: it_HEADER type standard table of BAPIBUS2000108_HEADER_INS.
DATA: wa_HEADER like line of it_HEADER.
DATA:it_ORGANISATION TYPE STANDARD TABLE OF     BAPIBUS20001_ORGMAN_INS,
     wa_ORGANISATION LIKE LINE OF it_ORGANISATION.
DATA: it_partner type table of BAPIBUS20001_PARTNER_INS.
DATA: wa_partner like line of it_partner.
DATA:HEADERX TYPE STANDARD TABLE OF     BAPIBUS2000108_HEADER_INSX,
     st_headerx TYPE bapibus2000108_header_insx,
     PARTNERX TYPE STANDARD TABLE OF BAPIBUS20001_PARTNER_INSX,
     st_partnerx TYPE bapibus20001_partner_insx,
     i_orgx TYPE STANDARD TABLE OF BAPIBUS20001_ORGMAN_INSX,
     st_orgx TYPE bapibus20001_orgman_insx,
     i_save TYPE TABLE OF bapibus20001_object_id,
     i_return TYPE TABLE OF bapiret2,
     DATEX TYPE STANDARD TABLE OF BAPIBUS20001_APPOINTMENT_INSX.
DATA:i_itemx TYPE TABLE OF bapibus20001_item_insx,
     i_item TYPE TABLE OF bapibus20001_item,
     st_itemx TYPE bapibus20001_item_insx,
     st_item TYPE bapibus20001_item,
     i_schedulex TYPE TABLE OF bapibus20001_schedlinx,
     i_schedule TYPE TABLE OF bapibus20001_schedlin,
     st_schedulex TYPE bapibus20001_schedlinx,
     st_schedule TYPE bapibus20001_schedlin.
DATA :c_x TYPE char01 VALUE 'X',
      TESTRUN type BAPIFLAG-BAPIFLAG.
data i_input TYPE TABLE OF bapibus20001_input_fields.
data st_input TYPE bapibus20001_input_fields.
DATA:ORG_NO TYPE OBJEKTID,
     PARTNER_NO1 TYPE BU_PARTNER,
     CUST_BP TYPE BU_PARTNER,
     SALE_OFF TYPE CRMT_SALES_ORG_RESP.
DATA:msg TYPE ZRETURN_ERROR.
DATA:w_item TYPE CRMT_ITEM_NO,
     w_handle TYPE CRMT_HANDLE.
CLEAR:st_headerx.
st_headerx-handle = c_x.
st_headerx-process_type = c_x.
st_headerx-DESCR_LANGUAGE = c_x.
st_headerx-POSTING_DATE = c_x.
st_headerx-lead_type = c_x.
st_headerx-importance = c_x.
st_headerx-source = c_x.
APPEND st_headerx TO headerx.
CLEAR wa_header.
wa_HEADER-HANDLE = '0000000001'.
wa_HEADER-PROCESS_TYPE = 'ZCDL'.
wa_HEADER-DESCR_LANGUAGE = 'EN'.
wa_HEADER-POSTING_DATE = '20100603'.
wa_HEADER-IMPORTANCE = '5'.
wa_HEADER-SOURCE = '019'.
wa_HEADER-LEAD_TYPE = '0016'.
APPEND WA_HEADER TO IT_HEADER.
CLEAR:st_input.
st_input-ref_handle = '0000000001'.
st_input-ref_kind = 'A'.
st_input-objectname = 'ORDERADM_H'.
st_input-fieldname = 'PROCESS_TYPE'.
APPEND st_input TO i_input.
CLEAR st_input.
st_input-ref_handle = '0000000001'.
st_input-ref_kind = 'A'.
st_input-objectname = 'LEAD_H'.
st_input-fieldname = 'SOURCE'.
APPEND st_input TO i_input.
st_input-fieldname = 'IMPORTANCE'.
APPEND st_input TO i_input.
st_input-fieldname = 'LEAD_TYPE'.
APPEND st_input TO i_input.
*To fill the Organization X Structure
CLEAR:st_orgx.
st_orgx-ref_handle = c_x.
st_orgx-ref_kind = c_x.
st_orgx-dis_channel = c_x.
st_orgx-sales_org_resp = c_x.
APPEND st_orgx TO i_orgx.
*To fill the Organization Structure
CLEAR:wa_ORGANISATION.
wa_ORGANISATION-ref_handle = '0000000001'.
wa_ORGANISATION-ref_kind = 'A'.
wa_ORGANISATION-dis_channel = '01'.
wa_ORGANISATION-sales_org_resp = 'O 50000041'.
APPEND wa_ORGANISATION TO it_ORGANISATION.
*Fill input fields for Organization data
CLEAR st_input.
st_input-ref_handle = '0000000001'.
st_input-ref_kind = 'A'.
st_input-objectname = 'ORGMAN'.
st_input-fieldname = 'DIS_CHANNEL'.
APPEND st_input TO i_input.
st_input-fieldname = 'SALES_ORG'.
APPEND st_input TO i_input.
*To fill the Partner X Structure
st_partnerx-ref_handle = c_x.
st_partnerx-ref_kind = c_x.
st_partnerx-ref_partner_handle = c_x.
st_partnerx-kind_of_entry = c_x.
st_partnerx-partner_no = c_x.
st_partnerx-partner_fct = c_x.
st_partnerx-no_type = c_x.
st_partnerx-display_type = c_x.
st_partnerx-MAINPARTNER = c_x.
APPEND st_partnerx TO partnerx.
*To fill the Partner Structure
*CLEAR:wa_partner.
*wa_partner-ref_handle = '0000000001'.
*wa_partner-ref_kind = 'A'.
*wa_partner-ref_partner_handle = '0001'.
*wa_partner-kind_of_entry = 'C'.           """""""A
*wa_partner-partner_no = '62563'.
*wa_partner-partner_fct = '00000022'.
*wa_partner-no_type = 'BP'.
*wa_partner-display_type = 'BP'.
*wa_partner-MAINPARTNER = 'X'.
*APPEND wa_partner TO it_partner.
CLEAR:wa_partner.
wa_partner-ref_handle = '0000000001'.
wa_partner-ref_kind = 'A'.
wa_partner-ref_partner_handle = '0001'.
wa_partner-kind_of_entry = 'C'.         """""""A
wa_partner-partner_no = '62564'.
wa_partner-partner_fct = '00000021'.
wa_partner-no_type = 'BP'.
wa_partner-display_type = 'BP'.
wa_partner-MAINPARTNER = 'X'.
APPEND wa_partner TO it_partner.
CLEAR:wa_partner.
wa_partner-ref_handle = '0000000001'.
wa_partner-ref_kind = 'A'.
wa_partner-ref_partner_handle = '0001'.
wa_partner-kind_of_entry = 'C'.    """"""""A
wa_partner-partner_no = '71024'.
wa_partner-partner_fct = 'ZCDLSM'.
wa_partner-no_type = 'BP'.
wa_partner-display_type = 'BP'.
wa_partner-MAINPARTNER = 'X'.
APPEND wa_partner TO it_partner.
*Fill input fields for Partner data
CLEAR st_input.
st_input-ref_handle = '0000000001'.
st_input-ref_kind = 'A'.
st_input-objectname = 'PARTNER'.
*st_input-logical_key = w_logickey_partner.
st_input-fieldname = 'DISPLAY_TYPE'.
APPEND st_input TO i_input.
st_input-fieldname = 'KIND_OF_ENTRY'.
APPEND st_input TO i_input.
st_input-fieldname = 'NO_TYPE'.
APPEND st_input TO i_input.
st_input-fieldname = 'PARTNER_FCT'.
APPEND st_input TO i_input.
st_input-fieldname = 'PARTNER_NO'.
APPEND st_input TO i_input.
st_input-fieldname = 'MAINPARTNER'.
APPEND st_input TO i_input.
*To fill the Item X Structure
st_itemx-handle = c_x.
st_itemx-header_handle = c_x.
st_itemx-ordered_prod = c_x.
st_itemx-number_int = c_x.
st_item-mode = c_x.
APPEND st_itemx TO i_itemx.
*To fill Schedule line X Structure
st_schedulex-item_handle = c_x.
st_schedulex-handle = c_x.
st_schedulex-quantity = c_x.
st_schedulex-logical_key = c_x.
APPEND st_schedulex TO i_schedulex.
CLEAR: w_item, w_handle.
w_item = '0000000010'.
*To fill the Item Structure
w_handle = 1.
st_item-handle = w_handle.
st_item-header_handle = '0000000001'.
st_item-ordered_prod = '400000120' .
st_item-number_int = w_item.
st_item-mode = 'A'.
APPEND st_item TO i_item.
*To fill Schedule line Structure
DATA:qty TYPE CRMT_SCHEDLIN_QUAN VALUE '1'.
st_schedule-item_handle = w_handle.
st_schedule-quantity = qty.
APPEND st_schedule TO i_schedule.
*Fill input fields for Item data
CLEAR st_input.
st_input-ref_handle = w_handle.
st_input-ref_kind = 'B'.
st_input-objectname = 'ORDERADM_I'.
st_input-fieldname = 'MODE'.
APPEND st_input TO i_input.
st_input-fieldname = 'NUMBER_INT'.
APPEND st_input TO i_input.
st_input-fieldname = 'ORDERED_PROD'.
APPEND st_input TO i_input.
Fill input fields for schedule line data
CLEAR st_input.
st_input-ref_handle = w_handle.
st_input-ref_kind = 'B'.
st_input-objectname = 'SCHEDLIN'.
st_input-fieldname = 'LOGICAL_KEY'.
APPEND st_input TO i_input.
st_input-fieldname = 'QUANTITY'.
APPEND st_input TO i_input.
CLEAR testrun.
*Testrun = 'X'.
CALL FUNCTION 'BAPI_LEAD_CREATEMULTI'
EXPORTING
   TESTRUN            = Testrun
TABLES
   HEADERX            = headerx
   PARTNERX           = partnerx
   ORGANISATIONX      = i_orgx
   itemx              = i_itemx
   sched_linx         = i_schedulex
   HEADER             = it_header
   ORGANISATION       = it_ORGANISATION
   PARTNER            = it_partner
   item               = i_item
   SCHED_LIN          = i_schedule
   INPUT_FIELDS       = i_input
   RETURN             = i_return
   SAVED_PROCESS      = i_save .
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
   WAIT          = 'x'.
IF SY-SUBRC = 0.
IF sy-subrc = 0.
ENDIF.
ENDIF.

Hi,
Look at the post. No one will be able to understand anything out of this. Kindly Repaste code using markup.
Regards,
Harsh.
Edited by: Harsh Saxena on Aug 28, 2010 11:40 AM

Estimated Revenue and Probability of Convertion in the Leads Creation Page

Hi ,
Can we have The Fields for the Estimated Revenue and the Probability of Convertion (Manually Entered by the User)in the Leads Creation Page in WEB UI ?
Regards,
Srinivas

Hi Srinivas,
if they are standard fields, they should be available in the UI -> Show Configurable Areas -> Show Available Fields.
Just add them to the screen.
Cheers,
André

Entering Product Group / Category at the Lead Creation Stage

Hi
Our Client requires to capture the Product Group / Category at the Lead Creation Level.
At the lead creation level the sales engineer is not exactly aware of the product pricely which the customer wants to buy but knew which Product Group / Category the customer is interested in. So is there any way to capture the Product Group / Product Category at the Lead Creation Level.
Regards
Punit Kapoor

1. Use TCode 0VVW for creating a Z Item Usage, say, ZPO1
2. Do an item Cat determination in VOV4, as
Sales Doc type
Item Cat Group
Usage
Item Category
OR -
NORM -
ZPO1 -
TAB
3. Maintain Customer Materials Info Record by using VD51.
In item screen for Cust-Mat combination maintain Item usage
Regards
JP

Error in lead creation

Hi Experts,
Has any one used bapi- BAPI_LEAD_CREATEMULTI for creation of lead? I am trying to create lead using BAPI_LEAD_CREATEMULTI but it is throwing one or the other error and the lead is not getting created. I am passing the prospect and contact information as partners. Also, i need to pass text information.
Please check the below code and let me know where I am going wrong.
The code is as follows:
{ loop at i_inputfile into st_inputfile.
   CLEAR: st_header, l_guid, l_handle, l_phandle.
   l_handle = sy-tabix.
   l_phandle = sy-tabix.
GUID Handle
   st_header-handle = l_handle.
   st_headerx-guid = c_x.
   st_header-process_type = c_zald.
   st_headerx-process_type = c_x.
   st_header-description = st_inputfile-description.
   st_headerx-description = c_x.
   st_header-posting_date = sy-datum.
   st_headerx-posting_date = c_x.
   st_header-source = st_inputfile-source.
   st_headerx-source = c_x.
   st_header-lead_type = st_inputfile-lead_type.
   st_headerx-lead_type = c_x.
   st_header-qual_level_man = st_inputfile-qual_level_man.
   st_headerx-qual_level_man = c_x.
   APPEND st_header TO i_header.
   APPEND st_headerx TO i_headerx.
To fill the PartnerX Structure
st_partnerx-ref_handle = c_x.
st_partnerx-ref_kind = c_x.
st_partnerx-ref_partner_handle = c_x.
st_partnerx-kind_of_entry = c_x.
st_partnerx-partner_no = c_x.
st_partnerx-partner_fct = c_x.
st_partnerx-no_type = c_x.
st_partnerx-display_type = c_x.
st_partnerx-mainpartner = c_x.
APPEND st_partnerx TO i_partnerx.
*To fill the Partner Structure
CLEAR:st_partner.
st_partner-ref_handle = l_handle.
st_partner-ref_kind = c_a.
st_partner-ref_partner_handle = l_phandle. "'0001'.
st_partner-kind_of_entry = C_C. "'C'. """""""A
clear: st_pc_exist.
READ TABLE i_pc_exist INTO st_pc_exist with key ext_id = st_inputfile-ext_id
                                                acc_id = st_inputfile-acc_id
                                                cnt_id = st_inputfile-cnt_id BINARY SEARCH.
IF SY-SUBRC = 0.
    st_partner-partner_no = st_pc_exist-prospect.
ELSE.
    st_partner-partner_no = st_inputfile-acc_id.
ENDIF.
st_partner-partner_fct = C_PROSPECT.
st_partner-no_type = C_BP. "'BP'.
st_partner-display_type = C_BP. "'BP'.
st_partner-MAINPARTNER = C_X. "'X'.
APPEND st_partner TO i_partner.
st_partner-ref_handle = l_handle.
st_partner-ref_kind = c_a.
st_partner-ref_partner_handle = l_phandle. "'0001'.
st_partner-kind_of_entry = C_C. "'C'""""""""A
IF st_pc_exist-contact IS NOT INITIAL.
    st_partner-partner_no = st_pc_exist-contact.
ELSE.
    st_partner-partner_no = st_inputfile-acc_id.
ENDIF.
st_partner-partner_fct = C_CONTACT.
st_partner-no_type = C_BP.
st_partner-display_type = C_BP.
st_partner-MAINPARTNER = C_X.
APPEND st_partner TO i_partner.
CLEAR: st_partner.
Fill input fields
CLEAR:st_inputfields.
st_inputfields-ref_handle = l_handle.
st_inputfields-ref_kind = c_a.
st_inputfields-objectname = c_orderadm_h.
st_inputfields-fieldname = c_process_type.
APPEND st_inputfields TO i_inputfields.
CLEAR st_inputfields.
st_inputfields-ref_handle = l_handle.
st_inputfields-ref_kind = c_a.
st_inputfields-objectname = c_lead_h.
st_inputfields-fieldname = c_source.
APPEND st_inputfields TO i_inputfields.
CLEAR st_inputfields.
st_inputfields-ref_handle = l_handle.
st_inputfields-ref_kind = c_a.
st_inputfields-objectname = c_lead_h.
st_inputfields-fieldname = c_qual_level_man.
APPEND st_inputfields TO i_inputfields.
CLEAR: st_inputfields.
st_inputfields-ref_handle = l_handle.
st_inputfields-ref_kind = c_a.
st_inputfields-objectname = c_lead_h.
st_inputfields-fieldname = c_leadtype.
APPEND st_inputfields TO i_inputfields.
CLEAR: st_inputfields.
st_inputfields-ref_handle = l_handle.
st_inputfields-ref_kind = c_a.
st_inputfields-objectname = c_lead_h.
st_inputfields-fieldname = c_description.
APPEND st_inputfields TO i_inputfields.
CLEAR: st_inputfields.
st_inputfields-ref_handle = l_handle.
st_inputfields-ref_kind = c_a.
st_inputfields-objectname = c_lead_h.
st_inputfields-fieldname = c_status.
APPEND st_inputfields TO i_inputfields.
CLEAR: st_inputfields.
st_inputfields-ref_handle = l_handle.
st_inputfields-ref_kind = c_a.
st_inputfields-objectname = c_orderadm_h.
st_inputfields-fieldname = c_posting_date.
APPEND st_inputfields TO i_inputfields.
CLEAR st_inputfields.
clear: st_header, st_inputfile.
endloop.
Simulated test run
CALL FUNCTION 'BAPI_LEAD_CREATEMULTI'
EXPORTING
TABLES
   HEADERX               = i_headerx
ITEMX                 =
   PARTNERX              = i_partnerx
   HEADER                = i_header
ITEM                  =
   PARTNER               = i_partner
   TEXT                 = i_text
   textx                = i_textx
   INPUT_FIELDS          = i_inputfields
   RETURN                = i_return_l
   SAVED_PROCESS         = i_save. }
Help will be appreciated.
Thanks and Regards
Sangeeta.
Edited by: Sangeeta on Nov 4, 2010 5:08 AM
Edited by: Sangeeta on Nov 4, 2010 5:10 AM

Hi Sanggeta,
Samantak replied with a great tip. You can share which error is returned?
Also, you can check SM13 and tell us if there are any update request with error.
Best regards,
Caíque Escaler

Workflow for crm lead creation

Hi,
while creating the lead in crmd_order transaction. i need partnerfunction value in Business object repository. so i have created one subtype for that, then i created the attribute as a data dictonary field then system has asked to generate the code automatically wt is my doubt is is that the correct data system retrieves ( so any body give me the clarity that how to create the attributes and access the attributes in bor )

Hi,
I am not sure about Lead transaction but in general Partner Functions are maintained in IHPA table. You can get the Partners based on the object number for Lead. To fetch the correct Partner you need to know the Object number (OBJNR) and partner funtion (PARVW). You can have multiple values.
In your workflow,
1. Create and generate a subtype(Z-business object) for Lead business object BUS2000108 and deligate the same to standard business object. (as suggested by Saumya)
2. Create an attribute in the subtype. the attribute should be a VIRTUAL ATTRIBUTE.
3. Place the cursor on the attribute and click on program, it will generate some code.
4. between Get_property and End_property for your virtual field write the logic such that you get the object number from Lead tables and fetch partners from IHPA table and fill the final attribute using macros.
swc_set_element container <container Name> object-<Container name>.
4. Once the coding is completed, release the attribute and business object and generate subtype.
Now required Partners will be available in workflow.
Hope this helps you in resolving your issue. If you have any additional queries please feel free to reply to this tread.
Regards,
Gautham Paspala

Error during Lead Creation

Hi,
I had created a lead. When I am going to Evaluation data tab for the questionnaire i am getting the following error.
Hostname 'iwdf9077.wdf.sap.corp' unknown/cpi-c error cm_parameter_error.
please let me know how to resolve this.
Thanks

Check in OVZ1 where for your availability check, the box is checked under the tab "Blocked".
G. Lakshmipathi

Automatic account or contact creation from a lead

Is it possible to automatically create the associated contact record or account record from the lead creation web service?
(assuming the email address is unique)

If you are creating a Lead Record using Webservices then you can also automatically create an Account or Contact Record as well. Make sure that you create the code to search the CRM first to make sure that the account or contact dont already exsist and then if they dont create an account or contact if they dont then the lead should be associated with the Account or Contact.

Creation of Lead

Hi All
Can anyone please help with for creating a lead through BAPI
bapi_lead_createmulti
Please provide the parameters also which are necessary to create it.its urgent
Points will be awarded

Hi Mona,
Refer to : [bapi for lead creation;
If you need further info, let me know,
Regards,
Arjun
pl. do reward points

Follow Up transaction for Leads

Hi Experts,
I am facing an issue in the Web Ic while creating a follow up for Lead. When i am trying to create a followup from lead the Pop Up appears for secting teh transaction type, but it is not showing the Transaction type which had maintained in the Copy control setting, whereas it shows all other transaction which i have not configured.
Any suggestions.
Regards
Arun Kumar

Hi Praveen & Arup,
I am not using any product in my lead creation. Secondly i want to create a follow up as Ztransaction type for Activity where i dont get any item category.
Can you please sugegst. I am using teh Business Role MARKETINGPRO.
Regards
Arun Kumar

4 signs to know that your lead scoring program is working

Getting the science of how your buyers engage with you is key for making revenue generation more predictable. We have worked with many sales and marketing organizations who look to putting in a lead scoring system to better qualify which leads should go to sales, validate that online campaigns are influencing MQL production and to make sales people more efficient. Regardless of whether you are testing the scoring methodology within marketing or have a system that is in place, I wanted to share 4 tips to highlight how you can determine if your current system is working before you make any changes.
Eloqua RPIs are moving in the right direction. Value, Reach, Conversion, Velocity, Return are Eloqua's revenue performance indicators and there is a connection between the output of your scoring system and each indicator. Ensuring that you have a process for scoring leads in your marketing database (reach), monitoring the speed (velocity) at which they move through funnel (conversion), will give you a sense of how well your system is performing and its impact on revenue generation. Value and Return will become clear once you have seen enough scored contacts flow through buying cycles to become customers in order for those to become clear.
Your top ranked leads outperform the other categories. Measuring fit and engagement are among the best practices for building a sound lead scoring system. Fit includes all of the firmographic pieces of information that your buyer gives you or can be appended via Eloqua's AppCloud. Engagement speaks to Digital Body Language or their online buying behavior. You should look at a conversion matrix for A1s down to D4s and look at the % of those MQLs become accepted (Lead Acceptance Rate by Lead Score report via CRM). You should also look at what happens when your target buyer, scores highly, and then becomes part of an opportunity - are there other patterns that are worth noting: opportunity close rates for A leads is x time faster than any other score? Having your own benchmark for what happens when you get an A1 lead will build confidence in your scoring model and drive the right behaviour.
Lead Acceptance rates rise. A good system will invoke sales' trust in marketing and the leads they generate. McAfee, the 2011 Markie Winner in our Clean House category sought after Eloqua's AppCloud tools for data.com and Demandbase when they saw a dual decline in Lead Scores and fewer leads going over to CRM over time. Missing data impacts, routing, lead scoring, segmentation, reporting and trust with your sales team. McAfee addressed the problem and saw an overall WW increase in lead acceptance and a 25% increase in acceptance in one of their global regions. On the behavior side, to ensure that you have the right patterns, you should look at any closed deals that were touched by marketing and look for the campaigns that influenced the buyers (first campaign, last campaign before opp creation) and chat with sales about any tactics that are offline that can be looped into your scoring model. Either way, if sales has trust in the data - both from a fit and engagement perspective, they will work the leads and any hesitation to accept should go away.
Average / Total Opportunity Value rises. Being able to model your buyer's actions into a science may give your sales team an opportunity to cross sell or deepen that initial conversation. 2011 Markie Winner for Integration Innovation, Progress Software experienced a drop in lead creation, but a rise in total opportunity creation and closed won revenue by leveraging Eloqua's AppCloud to pull in buyer attributes to support scoring. If you can instill confidence in your buyer early on, you are more likely to get their trust and be able to create a dialogue that leads to a superior buying experience and more revenue throughout that relationship.
Let me know your thoughts and your experiences with measuring the impact of your lead scoring system. I hope that you continue to look to Topliners for inspiration and to take your usage of marketing automation to the next level!
-Chang

Nice post Adrian.
I think another great indicator is your SAL to SQL rate increases as well. Ultimately, sales wants opportunities from Marketing not qualified leads. Another great indicator is time spent in the Qualifiy stage. Looking at a pipeline aging report, if your lead scored SALs are moving from SAL to SQL quicker than other channels, you know your sales team is having an easy time qualifiying these leads - an indicator that your lead scoring program is doing a good job of finding the right person at the right time.

Parent / Child lead management

Does anyone have experience using parent/child relationships with leads in SalesForce? I am currently looking into setting this up for our organization to answer the need for multiple business units to be able to work/manage their leads while maintaining a unified view of all the interactions with the lead.

Shane, not sure if you've solved this yet, but I see this use case quite often. The most scalable solution, while not the simplest, is to leverage apex triggers in SFDC to control the creation of children leads based on whatever your child-lead-creation criteria are. Visualforce can be used to then display and share activity across all related ( connected ) Leads as a related list, and child Leads can be worked independently by sales reps.
Here's the general scenario:
1. Prospect A submits a form indicating interest in product A.
2. Eloqua creates a PARENT LEAD in SFDC because this person does not already exist. The Lead ID is stored in the Eloqua contact field called Parent Lead ID.
3. Your Apex Trigger creates a CHILD LEAD, associated to the Parent Lead via Reference, based on product A.
4. Prospect A submits a form next week indicating interest in B
5. Eloqua updates the PARENT LEAD with product B (almost like it would with Lead Source - Most Recent).
6. The trigger evaluates that a CHILD LEAD does not exist with product B and creates one, associated to the Parent Lead via Reference, based on product B.
Your PARENT LEAD now has two children, one for product A and one for product B, which can be worked independently by sales reps, with the PARENT always remaining in place.
There's additional logic that needs to be incorporated into the trigger so that updates to the parent can be propagated to the correct child, as well as the need for a custom object in Eloqua to maintain the relationship between the Parent Lead and its Children.
Tom

Agent determination creating lead

In lead creation,if user enters the value in sales representative field then the workitem should trigger to that rerpresentative, By using BOR attribute we can made that salesrepresentative value available in workflow, the problem is how to find the user name of that representative by using rule.

we can made that salesrepresentative value available in workflow
You mean to say you have the PERNR of the representative ? so you want to determine the USERID of the PERNR right?
if this isthe case then you can get the user id of the pernr by using the FM
PTRV_CONVERT_PERNR_TO_USERID

Alerts for Leads

Hello,
I need to create alerts for lead creations. When I create a Lead I distribute it for a employee responsible, and these employee responsible should receive an alert in his Alerts Home Page.
I've created an alert category in T-Code: ALRTCATDEF, and also an Action Profile in T-code: CRMC_ACTION_DEF.
In Alert category I added the role SAP_BC_ALM_ALERT_USER in "Subscription Authorization".
I also added the role SAP_BC_ALM_ALERT_USER to each user, and assigned the alerts in the work list.
Doing this, when I create a lead to one specific employee responsible, every employee that have the role SAP_BC_ALM_ALERT_USER assigned will reseive the alert for the created lead.
How can I restrict the alert for the lead employee responsible?
Regards & Thanks,
Susana Morgado

I would first try to use the action condition technique (scheduling and start conditions) in order to only process the action if the context is correct (so for instance when a certain status is reached).
If this is not possible (for instance because you don't know what has changed when using condition technique), you can see what the action actually does (in abap), and use this code to build a custom function which you can assign in for instance CRMV_EVENT.
More information on the use of CRMV_EVENT can be found [here|http://sapcrmweblog.blogspot.com/2011/08/adding-functions-to-events-using.html].
Hope this helps.
Regards,
Pieter Rijlaarsdam

Lead Creation

Similar Messages

Maybe you are looking for