Does new 1402 Activity object in Cloud for Customer have wrong data type namespaces?

[gregory_root]

I see that the individual "activity" objects (e.g., ActivityTask, AppointmentActivity, etc) are being deprecated as of 1405 and moving to a new Activity object with a TypeCode. That makes a lot of sense.

In reviewing this new Activity object, I've noticed that many of the node elements utilize Data Types in the http://sap.com/xi/Common/DataTypes namespace instead of the http://sap.com/xi/AP/Common/GDT. For example, the root node element UUID has a data type UUID in the http://sap.com/xi/Common/DataTypes namespace, unlike all the other objects in the Public Solution Model.

There are many more elements in this new Activity object that are mismatched like this to other common usage in other objects. Is this a new trend or a mistake?

[gregory_root · Accepted solution]

FYI, this impacts coding because the data types don't match and extra work needs to be done to ensure they DO match.

[Former Member · Accepted solution]

This is a new trend and you have to modify your custom bo accordingly

[HorstSchaude · Accepted solution]

Hello Gregory, Alessandro,

just for clarification:

SAP wanted to eliminate the superflous supplementary components from the data types used in the Business Objects.

Take the GDT Identifier as an example. It has the following supplementary components:

• SCHEME_ID
• SCHEME_VERSION_ID
• SCHEME_AGENCY_ID
• SCHEME_AGENCY_SCHEME_ID
• SCHEME_AGENCY_SCHEME_AGENCY_ID
• CONTENT

You very seldom need the SCHEME_ID or the SCHEME_AGENCY_ID (if the ID is a GTIN or DUNS number then you need them). I never came over a situation to use the SCHEME_AGENCY_SCHEME_AGENCY_ID.

So the data types from the "new" namespace omit those components. But SAP noticed the effort to adapt all the coding.

Therefore it was decided that only new objects will use the data types from the new namepace.

In the case of the ActivityTask, AppointmentActivity, etc. this wil requires - as Alessandro mentioned - some adoption effort.

HTH,

      Horst

[gregory_root · Accepted solution]

Hello ,

Thank you for the detailed clarification.

Would it be a fair to say that SAP's official recommendation is to say that from now on, all new custom business objects created with the SAP Cloud Applications Studio should use the http://sap.com/xi/Common/DataTypes namespace as well, and avoid the http://sap.com/xi/AP/Common/GDT namespace unless absolutely necessary?

And, will the SAP Cloud Applications Studio be updated so that the templates for new BO's and new events have the new import statements?

Regards,

Greg

[HorstSchaude · Accepted solution]

Hello Greg,

Due to the fact that the effort to adapt all SAP BOs to the new data types was too big, the "migration" process was stopped.

Therefore you will not find all data types in both namespaces.

This can be seen with the new Activity BO; elements are typed with data types from both namespaces.

As consequence the template for the BO stayed with the old namespace.

For your own BOs, I suggest to go the "keep it easy" approach (like in the Activity BO):

     Wherever a (simplified) data type from the new namespace is available, take that one.

HTH,

    Horst