naming conventions

[Former Member]

Generally what naming conventions are used in real time to define design and configuration objects name?

[Former Member · Accepted solution]

It really does depend on the project. Each project has its own defined standards but some examples are below.

Datatype: DT_

Message Type: MT_

Message Interface: MI_<Async/Sync>_<Direction>_

Message Mapping: MM_<SourceMessage>_<TargetMessage>

Message Interface: IM_<SourceMessage>_<TargetMessage>

Communication Channels: CC_<AdapterType>_<Send/Recv>_

Integration Process: IP

These are just a few and should give you some idea... but the main thing is to make sure they are always meaningful and easily distinguishable.

But as I said each project has its own flavour

[nisarkhan_n]

Naming conventions

Namespace https:
<your Interface ID>:<business name>

ex: https:
SCP156:inventorydata

For Configuration

CS_SCP156_inventory_data

actually it depends on the Bunsiness name for the interface or how you fix your naming conventios it might be depending on your business process wht you follow to idetify the interfacess...

[GabrielSagaya]

please visit the article

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/90b213c2-d311-2a10-89bf-956dbb63...

http://help.sap.com/saphelp_nw04/helpdata/en/2a/6b0afe547a11d189600000e829fbbd/frameset.htm