How to avoid the problem of duplicate names of some tables caused by importing the Azure SDK.

[yunbozhang-msft]

Hi team,

We are trying to import the Azure SDK in order to develop the function of uploading and downloading blobs, but we found that when importing the Azure SDK, it will report some problems that the Data element of Field used in the tables in the SDK were the same as those used in our system. If the SDK is imported, it will cause conflicts. Is there a way for us to avoid this problem?

For example:

We have a table named ZCOxxxx, and this table has a field UUSER, UUSER data element is ZUNAME, but for Azure SDK, it will also need create a Data Element names ZUNAME, and it will cause conflicts.

cc: @sky5685610
Thanks!

[larshp]

also see #8

workaround would be maintaining a fork where some parts are automatically renamed, https://blogs.sap.com/2021/04/20/automagic-standalone-renaming-of-abap-objects/

[sky5685610]

hi Larshp,

I have installed the tool in my laptop, however, the length of some objects have been the longest which is unable to add prefix, and they are also named not in rule. Are there any ways to import the GitHub coding to our ECC system without influent the z objects existing in our system?

[larshp]

a. Rename all to Y*
b. Open a pull request in this repository with renaming
c. Maintain a fork

[sky5685610]

hi

Y* is just for testing programs in DEV system, all programs should be Z* in our PRD system

[sky5685610]

hi

still error

[larshp]

disable or adjust the settings for https://rules.abaplint.org/object_naming/

renaming of the reference in AUTH might need to be handled manually

[sky5685610]

hi

I disable it and run npm, another error occur

[larshp]

I've opened abaplint/abaplint#2934

[sky5685610]

what do you mean?

[yunbozhang-msft]

Hi team, do we still need to wait for abaplint team to fix this issue? Looks auth-related can not be renamed.
If so, we still do not have any other workaround to rename that? Thanks for your support.
cc: @vikasbansal2022 any suggestions are welcome : )

[larshp]

renaming of AUTH reference fixed in 2.99.6

[vikasbansal2022]

Hi @zhangyunbo1994,

Since SDK has downloaded by customer closing this issue.

Regards,
Vikas