Hi Rajesh,
The Naming Conventions followed in most of the cases might be project specific. I have summarized a few basic naming conventions below:
<u><b>For PCD Content:</b></u>
Content objects include iViews, Pages, Layouts, Worksets, and Roles. Each content object is required to have a Name, ID and an ID Prefix (or namespace).
<b>ID Prefix (Namespace)</b>
The ID Prefix (also called a Namespace) is used to categorize objects, and is used as part of the full unique identifier for an object.
• ID Prefixes are required for all objects.
• ID Prefixes for project content objects use the format: urcompany.project.subCategories.objectType.subType
o project := The project acronym (prefered) or full project name.
o subCategories := 0 to n optional sub categorization levels within the project.
o objectType := The type of content object (iview, page, workset, role, etc).
o subType := If the object inherits from a template a sub-type must be included.
• ID Prefixes for enterprise objects use the format: urcompany.enterprise.subCategories.objectType.subType
• ID Prefixes for global objects use the format: urcompany.objectType.subType
• ID Prefixes must be entirely lowercase (for ease in searching, and to prevent mismatched casing).
• Acceptable characters include alpha-numeric characters and underscores to substitute for spaces.
<b>ID</b>
The ID of an object is used with the Namespace and Folder to create a unique identifier to the object. The combination of Namespace, Folder Location and ID must be unique. Make sure when performing a copy or a delta-link copy that you right click and perform a “Change ID” operation.
• IDs should be similar to the Name provided for the object.
• IDs must be entirely lowercase (for ease in searching).
• IDs should be concise, yet descriptive. There is a 40 character limit.
• Acceptable characters include alpha-numeric characters, dashes, and underscores to substitute for spaces.
<b>Name</b>
Names are used in the Portal Content Directory (PCD) view, but more importantly are displayed as navigation links and titles to end-users.
• Names should be concise yet descriptive, describing the purpose or function of the content within it.
• Acceptable characters include alpha-numeric characters, spaces, apostrophes, parentheses, dashes.
• Names should follow Title-Casing rules – Capitalize all words unless it is an article (a, an, the), coordinating conjunction (and, but, for, or, nor), prepositions regardless of length (unless they are the first or last word).
• Names should follow SAP naming conventions of “action-object” or “verb-noun” unless there is a compelling argument not to due so. (“Edit Timesheets” instead of “Timesheet Editor”).
<b>Description</b>
Descriptions are useful for searching for content objects, and provide a short description useful for conveying the intent or purpose of the object. Descriptions should be in sentence form.
• Descriptions are required for all objects.
• Descriptions should contain descriptive, but concise, functional and technical information about the object.
<b>Folders</b>
Folders can be seperated into two categories in the portal. There are Portal Content Directory (PCD) folders used for design-time organization, and folders within roles and worksets for run-time content organization.
• Folders will not be given ID Prefixes.
• Folder descriptions must always be provided.
• Acceptable characters include alpha-numeric characters, spaces, apostrophes, parentheses, dashes.
• Folder names should follow Title-Casing rules – Capitalize all words unless it is an article (a, an, the), coordinating conjunction (and, but, for, or, nor), prepositions regardless of length (unless they are the first or last word).
<b>System Landscape Objects</b>
System landscape objects are defined once for each distinct system connection that is needed to drive iView content. In the future, system connectors may be presented to users for entering user mapping details. At this time there is no convention for naming Connectors. Please contact the portal team if a system landscape needs to be created.
• System Landscapes will follow the naming conventions for content objects, unless otherwise indicated below.
• System Names will be the name of the system in the corresponding environment landscape (Dev, QA, Prod).
• System Landscapes will be given the ID Prefix: nvidia.system.templateID
o templateID := The ID of the template used to create the system.
• System aliases will be a generic identifier to describe the functionality of the system, regardless of environment (Dev, QA, Prod).
• Systems can contain multiple aliases depending on the need.
o Example: A business package comes configured to use the system “SAP_R3_HumanResources”. The system alias should be added to the appropriate system.
For more info you need to refer SAP EP Best Practices.
Hope this helps.
Regards,
Pooja.
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.