Welcome [ B2BiAxis Sign In / Register ]  
Follow Us

Naming Conventions

Use Your Company’s Naming Conventions Consistently
Naming different versions of the same business process model brings special considerations. For information, see Name Versions Meaningfully on page 6. Retain Service Names in Graphical Process Models Although you can change the names of services in your graphical process models to make them more descriptive, a good practice is to retain the service name within your new name, so that for future reference you can easily see which service you used for that step (changing the name of a service in the GPM changes the display name shown in the workspace for that service, but it does not rename the service configuration used in the process model). Retaining the name of the service is particularly helpful so that when you need to update multiple business process models to use a new service (such as when one that you have been using is retired), you can see the service name in the process model. This saves research time.
Examples of Naming Convention for Business Process for communications
Inbound:
TradingPartnerName_ FrameWork_Protocol_Recv
Example: SIA_Comm_FTP_Recv
Outbound:
TradingPartnerName_ FrameWork_Protocol_Send
SIA_Comm_SFTP_Send
Examples of Naming Convention for Maps:
Inbound:
TradingPartnerName_Standard_Direction_Transaction_Version_ApplicationType
Example: SIA_EDI_Recv_850_004010_ORDERS05
Outbound
TradingPartnerName_ApplicationType_Standard_Direction_Version

Example: SIA_INVOICE01_Send_cXML_InvoiceRequest_1.2.019