cancel
Showing results for 
Search instead for 
Did you mean: 

Bug while creating an activity (wrong business partners)

Former Member
0 Kudos

Hello,

Found a bug while creating an activity from mobile device.

Well, here is the code which exists in  /MSA/TA_BUPA_MAP_I2E

** read partner functions from the download parameters.
       READ TABLE lt_activity_d INTO ls_activity_d WITH KEY process_type = is_orderadm_h-process_type.
       IF sy-subrc = 0.
         lv_pkfct1_d = ls_activity_d-act_partner_1.
         lv_pkfct2_d = ls_activity_d-act_partner_2.
         lv_pkfct3_d = ls_activity_d-act_partner_3.
         lv_pkfct4_d = ls_activity_d-act_partner_4.
       ENDIF.
** if no download parameters are maintained, read from the upload parameters
       READ TABLE lt_activity_u INTO ls_activity_u INDEX 1.
       IF sy-subrc = 0.
         lv_pkfct1_u = ls_activity_u-act_partner1.
         lv_pkfct2_u = ls_activity_u-act_partner2.
         lv_pkfct3_u = ls_activity_u-act_partner3.
         lv_pkfct4_u = ls_activity_u-act_partner4.
       ENDIF.

Bolded area contains bug. I have update parameters in lt_Activity_u but it tries to read form index1.

It should read like this ;

READ TABLE lt_activity_u INTO ls_activity_u WITH KEY process_type = is_orderadm_h-process_type.

because first index doesn't contains the correct key i have a process_type to read the related business patterns.

When i fixed it via debug, it works great.

Same bug happens in lead and oppt creating. But if you have only 1 type of these objects (1 lead type, 1 oppt type ) you can not encore with the bug.

Is there any patch for this  or i should repair it ?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

My package levels:

CRM :

MOB_CRMS2000000     -SAP CRM Sales 2.0 Addon 2.0

Mobile :

SAP_BASIS7100014SAPKB71014SAP main component
CRMSPGWY1100007SAPK-11007INCRMSPGWYGateway to SAP NW Mobile 1.1
masa_139
Product and Topic Expert
Product and Topic Expert
0 Kudos

FYI. MOB_CRMS 200 SP02 is available since April 2012.

Former Member
0 Kudos

yea fixed after patch.

Answers (0)