Hi,
SLD Software Catalogs "SAP based
Third-Party Product" Vendor <URL of mycompany> 20 cognizant.com
Name <MYCOMPANY>_<SAP PRODUCT NAME> 30 All Caps COGNIZANT_SAP_BASIS
Version Same as of related SAP product 1.0 or 4.6C
Its Software Components Vendor <URL of mycompany> 20 cognizant.com
Name <MYCOMPANY>_<SAP PRODUCT NAME> 30 All Caps COGNIZANT_SAP_BASIS
Version Same as of related SAP SWCV 1.0 or 4.6C
"Non SAP based
Third-Party Product" Vendor <URL of mycompany> 20 cognizant.com
Name <MYCOMPANYNAME>_<VENDOR of third-party product>_<NAME of product> 30 All Caps COGNIZANT_IBM_DB2
Version Same as of standard third-party product 3.0
Its Software Components Vendor <URL of mycompany> 20 cognizant.com
Name <MYCOMPANYNAME>_<VENDOR of third-party product>_<NAME of product> 30 All Caps COGNIZANT_IBM_DB2
Version Same as of third-party Software Component 3.0
Technical Systems "Web AS ABAP
Web AS Java" Name System ID 3 CXI
"Standalone Java Sytems
Third-Party Systems" Name System Host Name or Naming depends on Type of the System
Business Systems Name <Role of System>_ <Company name>_<Type of System>_<Environment><optional: suffix> MASTERDATA COGNIZANT_SAPR3 PIND
Role of System Business or functional area where the system is used
Company name if some business system reside outside of the own company
Type of system Type of technical system
Environment "If one central SLD is used within the company
Use D - for Development Landscape
Q - for Quality Assurance
P - for Production"
ALE If already a naming convention in the company is in place follow this convention.
"SAP Systems
(with ABAP instance)" <SID>CLNT<client number> 10 CXICLNT100
"SAP Systems
(without ABAP instance) or Non-SAP Systems" <Short Business System Name><Environment> 10 DB2MASTERP
IR Namespace Name "URL reference as http://<URL of company>/<software component name>/<business process>/<business sub process>
or
http://<URL of company>/<software component name>/<business area>/<department> " "http://cognizant.com/sales/internal
or
http://cognizant.com/db2/training/academy "
"Integration Scenarios
and Actions" Name "Self-explanatory names
Concatenate words in upper camel case" CalculateGoodsMovements
Integration Process "Integration Processes
Container Elements
Correlations " Name "Self-explanatory names
Concatenate words in upper camel case" "ChangeOrders
OrderCount
BookingOrder"
"Receive,
Send,
Fork,
Wait,
Loop or Switch " Step Name "<step name><object/subprocess name>
Concatenate words in upper camel case" ReceivePurchaseOrder
"Receiver Determination,
Transform,
Control,
Container Operation,
Block
or Undefined " Step Name "<real sub process name><object name>
Concatenate words in upper camel case" "SplitInvoice
IncreaseCounter"
Interface Objects Message Interface Name "<message name>_<Interface's_Catagory>
IB - Inbound Interface
OB - Outbound Interface
ABS - Abstract Interface" SalesOrder_IB
Data Type Name "Self-explanatory names
Concatenate words in upper camel case" OrderHeader, OrderItem
Message Type Name "Self-explanatory names
Concatenate words in upper camel case" BookingOrderRequest
External Definitions Name Follow the naming conventions of Message Type
Data Type Enhancements Name "Define a name for the specific enhancement.
Concat name of standard SAP interface with the name of the enhancement separated by an underscore." MATMAS05_ModifiedSUM
Context Objects Name Use self-explanatory names instead of the object‘s technical name Plant instead of IDoc element WERKS
Mapping Objects Interface Mapping Name "* Concat source interface name with target interface name (without their category) separated by ""to"".
In case of more than one source and/or target interfaces concat their names by ""_and_“.
If involved Interface is in different SWCV, add SWCV in front of the Interface." "CognizantSAPR3_SalesOrder_to_SalesOrder
InvoiceHeader_and_InvoiceItems_to_CognizantSAPR3_Invoicing"
Message Mapping Name "* Concat source Message name with target Message name separated by ""to"".
If involved Message is in different SWCV, add SWCV in front of the Message." CognizantDB2_CustomerInvoice_to_Invoice
Mapping Template Name "* Add the name of the source SWCV in front
Concat the name of the source and the target type with separated by ""to""
Add as extension ""_TMPL""" CognizantDB2_Address_to_Adress_TMPL
Imported Archives Archive Name "* Add the name of the SWCV in front of the interface’s name
if the archive is not stored within the same SWCV .
Concat the name of the source and the target interface name
with separated by ""to"".
Add an extension for the type of mapping
""_Java"" for Java mappings
""_XSLT"" for XSLT mappings
""_JavaForXSLT"" for Java files which are used by XSLT mappings " BookingOrders_to_CognizantOracle_BookingOrders_Java
"Java / XSLT
Main file Name" Same as Archive name
Dependent Files Self-explanatory names with mapping type appended ConvertCountryCodes_JavaForXSLT
ID Configuration Scenarios Scenario Name "<scenario ID>_<self-explanatory name>)
Create a unique identifier for configuration scenarios
Choose a descriptive naming using upper camel case
Concat the unique identifier with the configuration scenario‘s name" 000153_OrderBilling
Party Name As name of the Party use the unit's name CognizantsDelivery
Business Service Name <name of business unit>_BUSS OrderAcknowledgement_BUSS
Business System (Service) Name Business System name from SLD
Business Process Name <BPM name>_BPM MultipleOrders_BPM
Communication Channel Name <type>_<direction>_<optional> JDBC_out_DBMaterials
SAP XI naming convention guide:
https://websmp102.sap-ag.de/~sapdownload/011000358700004455192006E/NameConventions.pdf
XI - SAP's document templates
Naming Conventions for XI Content Packages Used for Certification
Naming Conventions
http://www.erpgenie.com/sap/netweaver/xi/namingconventions.htm
Regards,
Vinod.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.