Customization for Activity in Sybase CRM sales

[Former Member]

Hi ,

I am implementing Sybase CRM sales application.

I need to make some customization's for Activity. I need to display Appointment Reasons for activity. There are 6 Appointment Reasons and i need to display these as a drop down in the mobile application.

So is it recommended to do such customizations?

If yes, Since this is not a field already displayed in the standard application i will need to make changes in the BADI so that the changes are reflected in the CE tables in DOE. But CE tables have only key value pairs.

But since i need multiple values please let me know how to display multiple values

Regards,

Madhu

[sivasatyaprasad_yerra · Accepted solution]

I think these customizations are distributed to device using MAS_CUSTOMIZATION object not the MAS_ACTIVITY.

Create these appointment reasons in CRM system

Perform load for MAS_CUSTOMIZATION object using the initial download for transaction data option

With these steps you should be able to show the drop down.

[Former Member · Accepted solution]

Hi Siva,

Thanks for the reply.

Appointment reasons are created in the CRM and then i did a initial load from CRM.

But i do not see see these reasons in the DOE under MAS_CUSTOMIZATION data object.

Let me know in which node will these values be present in the MAS_CUSTOMIZATION data object.

regards,

Madhu.

[Former Member · Accepted solution]

Hi Madhu,

First thing, there are no appointment reasons in MAS_CUSTOMIZATION object.

How you can achive this:

1. You need to implement lr_badi_gen->crm_gen_cust_mobile_getdetai which is called inside CRM_GEN_CUST_MOBILE_GETDETAIL function module to get appointment reasons.

2. Now the next question is, which structure to use. You can use any one of the CE structures to fill these values. Since they are just reason codes along with their descriptions which you want to show them in your application dropdown, you can use name value pairs.

All the enhancement structures use CRMS_MOBILE_CUST_ENHANCE_1O. In this all you need to do is, fill Reason code in field

FIELD_NAME and its description in FIELD_VALUE. You can use any of the CE structure but remember you have to query the same in your mobile applicatoin.

3. Once you are done with BADI implementation, you need to execute delta download from DOE.

4. Modify your mobile application to show these values in dropdown. But if you want the selected value to be created in CRM backend, then you also need to implement BADI " crm_activity_mob_smartphone" - create and change methods.

Best Regards,

Siva.

[Former Member · Accepted solution]

Hi Siva ,

Correct me if I'm wrong

DATA :ls_ce_bupa_hdr TYPE crms_mobile_cust_enhance,

lt_ce_bupa_hdr TYPE STANDARD TABLE OF crms_mobile_cust_enhance,

ce_str type crmt_cust_mob_units_ml.

ls_ce_bupa_hdr-field_name = 'R1'.

ls_ce_bupa_hdr-field_value = 'Account Maintenance'.

APPEND ls_ce_bupa_hdr TO lt_ce_bupa_hdr.

CLEAR ls_ce_bupa_hdr.

ls_ce_bupa_hdr-field_name = 'R2'.

ls_ce_bupa_hdr-field_value = 'Relationship Building'.

APPEND ls_ce_bupa_hdr TO lt_ce_bupa_hdr.

CLEAR ls_ce_bupa_hdr.

ls_ce_bupa_hdr-field_name = 'R3'.

ls_ce_bupa_hdr-field_value = 'Opportunity Qualification'.

APPEND ls_ce_bupa_hdr TO lt_ce_bupa_hdr.

CLEAR ls_ce_bupa_hdr.

ls_ce_bupa_hdr-field_name = 'R4'.

ls_ce_bupa_hdr-field_value = 'Opportunity Recommendation'.

APPEND ls_ce_bupa_hdr TO lt_ce_bupa_hdr.

CLEAR ls_ce_bupa_hdr.

ls_ce_bupa_hdr-field_name = 'R5'.

ls_ce_bupa_hdr-field_value = 'Opportunity Commitment'.

APPEND ls_ce_bupa_hdr TO lt_ce_bupa_hdr.

CLEAR ls_ce_bupa_hdr.

ls_ce_bupa_hdr-field_name = 'R6'.

ls_ce_bupa_hdr-field_value = 'Opportunity Validation'.

APPEND ls_ce_bupa_hdr TO lt_ce_bupa_hdr.

CLEAR ls_ce_bupa_hdr.

ct_cust_priorities[] = lt_ce_bupa_hdr[]. ? //how to assign to CE structure

IN badi :

we have many value parameters

VALUE( CT_CE_ML_CUST_BPTITLE )

VALUE( CT_CE_ML_CUST_CURRENCY )

VALUE( CT_CE_ML_CUST_PROC_CATEG )

VALUE( CT_CE_ML_CUST_GOAL )

VALUE( CT_CE_ML_CUST_STATUS )

VALUE( CT_CE_ML_CUST_PRIORITIES )

Also please let me know whcih CE structure should be used.

Regards,

Madhu.

[Former Member · Accepted solution]

Hi Madhu,

You are correct.

You can use any one of them. Should not be an issue.

The way you can assign is CT_CE_ML_CUST_BPTITLE[] = lt_ce_bupa_hdr.

Best Regards,

Siva.

[Former Member · Accepted solution]

Hi siva,

I have a similar query ..

in appointment reasons ,if in mobile we select 'Account Maintenance' ,then in CRM how it updates..

like in change BADI(activity) we nee dto read the value..

read ce into lhdr where name ="r1"

value =account maintainece"

or set a vaiable

v1 ='x'.

in CRM...in change activity BADI..BAPI_ACTIVITYCRM_CHANGEMULTI

we have two parametrs

REASON STRUCTURE BAPIBUS2000110_REASON_INS OPTIONAL

REASONX STRUCTURE BAPIBUS2000110_REASON_INSX OPTIONAL

How to populate these REASON STRUCTURE?

Thanks,

Anitha.

[Former Member · Accepted solution]

Hi,

I have checked by ruuning the FM CRM_GEN_CUST_MOBILE_GETDETAIL ,badi getting triggered .

But the LT_CE_BUPA_HDR[] is having the correct values.but not getting correct values in ce structure (Improper )

CT_CE_CUST_BPTITLE[]

field text datatype

000000000000 Accou ntMa intena nce

000000000000 Relat ions hip Bu ilding

000000000000 Oppor tuni ty Qua lifica

000000000000 Oppor tuni ty Rec ommend

000000000000 Oppor tuni ty Com mitmen

000000000000 Oppor tuni ty Val idatio

Anything wrong in the code?

[Former Member · Accepted solution]

Hi Madhu,

Looks like something went wrong in your code. Without looking at the code, I cannot comment. Please check your code once.

Best Regards,

Siva.

[Former Member · Accepted solution]

Hi Siva,

Now its working fineu2026

Structures which I used were different so stuck up with error.

Now if we select any value in drop down in mobile.

How to change the value in CRM? if i have to use a change BADI, which one should be used ?

Regards,

Madhu

[Former Member · Accepted solution]

Hi Madhu,

For that you need to implement the BADI in Activity change BAPI wrapper. Go to Activity change BAPI wrapper and in the end you will see a call to BADI. Implement the BADI and try to update the Activity of type Appointment in your BADI code.

Best Regards,

Siva.