How to use custom action parameter in campaings for multilanguage system?

[former_member671802]

Hello, dear experts.

I principally try to use standard functionality of SAP Marketing on premise 1909 and want to ask about actions parameters in campaings.

Extensibility Guide SAP Marketing says, that in method SET_ACTION_PARAMETER action_parameter_type controls how the parameter is rendered on the UI. The following values are supported:

• Edm.String: Parameter is rendered as a text field.
• Edm.Date: Parameter is rendered as a date field.
• Edm.Time: Parameter is rendered as a time field.
• Edm.Boolean: Parameter is rendered as a checkbox.

Talk about last one - checkbox. As known, for multilanguage we can use table cuans_mktorc_ap and corresponding text table cuans_mktorc_apt, where for each action ID and action parameter ID we set the name of the last for corresponding language. But CUANS_MKTORC_AP-UI_CONTROL_TYPE has only tree types:

• TEXT Text Field
• DDLB Drop Down List Box
• AREA Text Area

Thus we can conclude, to replace the code

DATA: lv_param_name TYPE TEXT40.
IF sy-langu = 'D'.
lv_param_name = 'Parametername in Deutsch'.
ELSE.
lv_param_name = 'English parameter name'.
ENDIF.
APPEND VALUE #( action_parameter = 'ZOC_CHECK'
 action_parameter_name = lv_param_name
 action_parameter_type =
if_cuan_mkt_orch_constants=>action_param_type-boolean ) TO
et_action_parameter.

we can not? Or is there a way to set the boolean type in UI_CONTROL_TYPE of the parameter 'ZOC_CHECK' to not be used IF statement in code?

The same question about DATE and TIME data types.

Thanks,

Anton Mazets.

[former_member248660]

Hello Anton,

Could you please share more context on what do you want to achieve? It would be even better if you could share the section in the extensibility guide you are making reference to. With that we would have a better picture of your requirement.

Best regards,

Christian

[former_member226]

Hi,

Method SET_ACTION_PARAMETER of BADI CUAN_CPG_OPN_CHNL_PARAMETER and field UI_CONTROL_TYPE of table CUANS_MKTORC_AP, both serve a different purpose. Former defines the field behavior for open channel implementation use cases whereas later one defines the new custom action parameter to the campaign. They both follow a different framework.

But from the explanation you gave above I see that you are trying to mix both approaches. And in my opinion, code you have written will not even trigger since this BADI is a filter badi and would need a open-channel implementation filter value "IMPLEMENTATION" defined and has no relation to what is defined in CUANS_MKTORC_AP.

So to solve your issues, either you should be using openchannel implementation and in such a case you can very well define boolean field just by using the code along with defining the filter value from the BADI CUAN_CPG_OPN_CHNL_DEFINITION.

Or else if using CUANS_MKTORC_AP then only 3 UI controls TEXT,DDLB,AREA can be defined.