Key user fields for custom BO

[Former Member]

Hi,

we are developing a solution for many customers in terms of a solution template (former as a scalable). Now, some customers have (as always) specific requirements. We would like to address this using "key user field", so that customers theirselfs are able to add new customer-specific fields without the PDI.

Is it possbile to enable this piece of functionality for custom BOs?

Best regards,

Daniel

[Former Member]

Hi Daniel,

This is a good idea for customer to extend field in custom BO, I was working on solution where we have thought to provide key user field for custom BO but it seems not possible in current version

and I came yo know that SAP key user fields created in adapt mode sits at a different table in backend, and partner content also have different place in repository.

Currently we can create key user field for SAP BOs. I am also interested in this feature and wish that SAP will provide this feature soon.

Regards

sunil

[HenrikeGrötecke]

Hi Daniel,

This functionality was added to the studio in version August 2013 (1308).

Please refer to the topic "Create References to Customer-Specific Fields" in the Studio documentation for 1308.

Best regards,

Henrike Grötecke

[Former Member]

Hi Henrike,

I do not think we are talking about the same use case. I guess you are refering to the use case, a key user created a customer-specific field. At a later point in time you would like to access this field via PDI.

My use case is a bit different. I create a new custom BO (incl. UI) in a customer-specific solution in a customer tenant. Now I want the key user be able to create new customer-specific fields based on the custom BO and this without usage of the PDI.

Best regards,

Daniel

[georg_wilhelm]

Hello Daniel, this requirement is already on our requirements list but it is currently not scheduled for one of the next releases as a lot of other requirements are ranked as more important. If the PDI solution is a one off solution the customer can create the field as a normal BO field in the partner BO himself. So for this cases a reasonable workaround exists. The requirement seems to be more relevant for multi instable partner Add Ons. Please correct me if I am wrong. Best regards Georg

[Former Member]

Hi Georg,

I know only codelist type which customer can configure at the time of fine tuning.

Could you please discuss the workaround, how customer can add a field in custom BO?

Thanks

Sunil

[Former Member]

Hi Georg,

basically you are right. But initially we started our solution as a scalable and only switched to a Solution Template because the scalable use case got temporarily "deactivated". Our solution targets at a broad number of customers and we would like the "core" to stay as it is. That is, why we actually would have liked this feature very much.

Best regards,

Daniel

[georg_wilhelm]

Hello Sunil, the workaround is that you create your field as a normal Partner BO field in PDI. Best regards Georg

[Former Member]

Hello Georg

Could you please explain this workaround how it can be use to generate key user fields at runtime. How can customer add new fields without help of cloud studio in their solution.

Thanks

Sunil

[Former Member]

Hi Sunil,

you cannot. What Georg means, is that the Partner BO is owned by you and thus you can add new elements to your BO at anytime. So if a key user requires a new customer specific field you need to add this in your code via PDI.

In my opinion, this works as long as you do not have a solution that is used by lots of customers. Otherwise maintenance of the solution becomes very tedious.

Best regards,

Daniel