Naming Standards for SAP's Component Model Objects....

In using SAP's Component Model, Scenario 3, there's a great deal of confusion in trying to version tracks, sc's, dc's, etc.
Since SAP does not currently have Best Practices for the use of the NWDI and the Component Model, can someone else provide me with some advice?
Thank you

Hi Peggy,
to find out more about all the NWDI terms it is a good idea to first read the <a href="http://help.sap.com/saphelp_nw04/helpdata/en/01/9c4940d1ba6913e10000000a1550b0/frameset.htm">architecture manual</a> about NWDI/JDI.
Regards,
Benny

Similar Messages

  • Naming standards for reports in Business Objects?

    Dear colleagues,
    I am about to start development of universes, queries and reports in Business Object for a client. Does anyone of you have any tips on naming standards for the reports? The source system that the dataware house is based on is a fund system. Often the name can be some letters and some numbers. Is there any logic behind this that I can follow?
    I will sign points!
    Kind regards
    Silje

    Hi Silje,
    Naming convetions should really tie in with your own processes. So it hard to say there is one for all.
    I generally create a report library. This is a simple list in Excel of the reports. It will contain the following
    Report Id: A number that is unique to each report, e.g. 1000
    Report Name: A short descriptive name, Monthly_Returns
    Report Location: The folder path to the report
    Report Description: A full descriptive name
    Report Contact: The person to contact about the report, developer or support person
    Report Owner: Business Owner of the report
    In WebI I would then call the report 1000_Monthly_Returns. I generally use the folder name to point to the area, so in the case of funds this report would be in the Funds folder.
    Hope this helps
    Alan

  • How to set naming standards for SQL Developer

    I am using SQL Developer version 3.0.04.
    In the newly integrated and very useful Data Modeler, we can set preferences for the naming standards to be applied when creating logical and relational model objects ( primary keys, foreign keys, et cetera). I would like to know if there is a way to set naming standards for the relational objects we create in SQL Developer on existing tables ( ( primary keys, foreign keys, et cetera).
    Any help in setting such preferences would be appreciated.

    Hi,
    If you want to set up a diagram for an existing database, you can use File/Data Modeler/Import/Data Dictionary to import its definitions.
    Alternatively you can open a Data Modeler Browser (using View/Data Modeler/Browser), expand the node for Design "Untitled_1",
    expand the node for Relational Models, and select Show from the Right-click drop-down menu for "Relational_1" to create a Relational Model diagram.
    You can then drag Tables from SQL Developer's Connections tree onto the diagram.
    Once you have a Relational Model you can reverse engineer it to an Entity-Relationship model using the << button in the button bar
    (or by selecting "Engineer to Logical Model" from the drop-down menu for the Relational Model).
    Note that there is now a separate forum for SQL Developer Data Modeler topics: SQL Developer Data Modeler
    David

  • Naming standards for BW queries

    where could i get the naming standards for BW queries? Can somebody email me at singhpra(at)yahoo.com. thank you.

    Hi Prakash,
    in our company we use the following convention:
    <Project_ID>_<CUBE>_Q<authorization>N
    The Project ID is a 2-digit code for the project, the cube consists of 5 digits. After the Q there's one letter for special authorization purposes, N is a 2-digit-number starting at 01.
    Example: P1_STMX1_QA01
    This works fine for all our cases.
    Greetings,
    Daniel

  • NAMING STANDARDS FOR WEB DYNPRO ABAP

    Hi All,
    Do we need to follow any naming standards in WebDynpro ABAP, could you please send some documents or any links for Naming Standards .
    Thanks,
    Raju.

    Hi Raju,
    This is a very good question which we cant answer as we are not working in your company.
    Well, the naming conventions standards vary based on different company Standards. So the best I could say is, check out your company Standards documents to get to understand the Naming Convention standards.
    Regards
    Raja Sekhar

  • Naming standard for creating a interface

    Hi,
    This question to be silly but i want to know
    Is there any naming standards to create any interface
    like in staging i defined WC_Dim_DS ( warehousecustom table_name dimension staging )
    how normally a ODI project naming conventions......?
    For interfaces/packages
    Any suggestions?
    thanks,
    saichand.v

    My Suggestion is
    I_<Target DB>_<Target Schema>_<Target Table>
    But if you are loading the table with 2 or more interfaces then you should add an explanation at the end. Explanation can be source system or purpose.
    I_<Target DB>_<Target Schema>_<Target Table>_<Explanation>
    And definitely schema and table name should contain some kind of metadata. For example divide staging table and final target tables into different schema such as STG and DWH.

  • CMS import  for SAP ESS component(SP 15) fails with fatal error.

    Hi,
    We are working on EP 7.0 SP 15. We have a requirement for changes to be made to SAP delivered ESS codes. We have set up the NWDI and and from the checkin tabn of CMS, the components SAP-JEE (7.00 SP18 ), SAP_JTECHS(7.00 SP18 ), SAP_PCUI-GP(SP 18), EP_BUILDT (7.00 SP18 )and SAP_BUILDT (7.00 SP18 )have been imported successfully to the development tab. But when we try to import the SAP ESS 600(SP level 15) from Checkin tab to the Development tab, the import fails. The exception chain as checked by clicking Details button in teh Develepoment tab of CMS shows the details as:
    20090610145206 Info   :Starting Step Repository-check at 2009-06-10 14:52:06.0283 +5:00
    20090610145206 Info   :Component:sap.com/SAP_ESS
    20090610145206 Info   :Version  :MAIN_ERP05PAT_C.20090427083436
    20090610145206 Info   :1. propagation request is of type TCSSoftwareComponent
    20090610145206 Info   :Propagatable:d647b419330511de9f130030057116fe exists allready in the repository. No import necessary.
    20090610145232 Fatal  :VcmFailure received
    20090610145232 Fatal  :caused by Exception:com.tssap.dtr.client.lib.deltavlib.VcmFailure: Internal Server Error [(pre||post)-condition failed: Internal Server Error]:Internal Server Error [(pre||post)-condition failed: Internal Server Error]
    com.tssap.dtr.client.lib.deltavlib.VcmFailure: Internal Server Error [(pre||post)-condition failed: Internal Server Error]
         at com.tssap.dtr.client.lib.deltavlib.impl.AbstractCommand.checkedExecute(AbstractCommand.java:196)
         at com.tssap.dtr.client.lib.deltavlib.impl.VersionSet.integrate(VersionSet.java:160)
         at com.tssap.dtr.client.lib.deltavlib.impl.VersionSet.integrate(VersionSet.java:148)
         at com.sap.cms.tcs.client.DTRCommunicator.integrateChangelist(DTRCommunicator.java:544)
         at com.sap.cms.tcs.core.RepositoryImportTask.integrateResource(RepositoryImportTask.java:816)
         at com.sap.cms.tcs.core.RepositoryImportTask.processRepositoryImport(RepositoryImportTask.java:367)
         at com.sap.cms.tcs.core.RepositoryImportTask.process(RepositoryImportTask.java:651)
         at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
         at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:206)
         at com.sap.cms.tcs.core.TCSManager.checkPropagationRequests(TCSManager.java:517)
         at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:179)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:500)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImportCheck(ImportQueueHandler.java:130)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImportCheck(CmsTransportProxyBean.java:720)
         at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0_0.startImportCheck(LocalCmsTransportProxyLocalObjectImpl0_0.java:1844)
         at com.sap.cms.ui.wl.Custom1.ImportCheck(Custom1.java:9968)
         at com.sap.cms.ui.wl.wdp.InternalCustom1.wdInvokeEventHandler(InternalCustom1.java:3156)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingCustomController.invokeEventHandler(DelegatingCustomController.java:89)
         at com.sap.tc.webdynpro.clientserver.event.CustomEventProcessor.handleServerEvent(CustomEventProcessor.java:45)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleServiceEvent(WindowPhaseModel.java:361)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:128)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processPhaseLoop(WebDynproWindow.java:345)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:152)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    20090610145232 Fatal  :caused by Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailure received: Internal Server Error [(pre||post)-condition failed: Internal Server Error]:communication error: VcmFailure received: Internal Server Error [(pre||post)-condition failed: Internal Server Error]
    com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailure received: Internal Server Error [(pre||post)-condition failed: Internal Server Error]
         at com.sap.cms.tcs.client.DTRCommunicator.integrateChangelist(DTRCommunicator.java:563)
         at com.sap.cms.tcs.core.RepositoryImportTask.integrateResource(RepositoryImportTask.java:816)
         at com.sap.cms.tcs.core.RepositoryImportTask.processRepositoryImport(RepositoryImportTask.java:367)
         at com.sap.cms.tcs.core.RepositoryImportTask.process(RepositoryImportTask.java:651)
         at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
         at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:206)
         at com.sap.cms.tcs.core.TCSManager.checkPropagationRequests(TCSManager.java:517)
         at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:179)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:500)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImportCheck(ImportQueueHandler.java:130)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImportCheck(CmsTransportProxyBean.java:720)
         at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0_0.startImportCheck(LocalCmsTransportProxyLocalObjectImpl0_0.java:1844)
         at com.sap.cms.ui.wl.Custom1.ImportCheck(Custom1.java:9968)
         at com.sap.cms.ui.wl.wdp.InternalCustom1.wdInvokeEventHandler(InternalCustom1.java:3156)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingCustomController.invokeEventHandler(DelegatingCustomController.java:89)
         at com.sap.tc.webdynpro.clientserver.event.CustomEventProcessor.handleServerEvent(CustomEventProcessor.java:45)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleServiceEvent(WindowPhaseModel.java:361)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:128)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processPhaseLoop(WebDynproWindow.java:345)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:152)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    20090610145232 Info   :Step Repository-check ended with result 'fatal error' ,stopping execution at 2009-06-10 14:52:32.0796 +5:00
    The above log is displayed when I click the import -check button on the development tab of CMS. The same error is displayes when the import button is clicked  with only the last sentence changed to:
    Step Repository-check ended with result 'fatal error'
    Can anyone help me on this.... ?
    Thanks,
    Sonali.
    Edited by: Sonali M S on Jun 10, 2009 1:16 PM

    Hi Bala,
    The problem still remails even after making changes in Visual Admin as per the thread Re: Assembly finished with errors
    Also from http://<server>:<port>/nwa we have run the configuration task for "Initial setup of functional unit Development Infrastructure (DI all-in-one)" and there we donot have the option for individual CBS, CMS and DTR installations as told in the thread.
    The other thread import into devlopment failed tells about the SAP note: 988010 iin which it is mentioned that this has been fixed in SP 11 for 7.00 version. We are already on SP 18. So it is assumable that this thing has already been fixed.
    Can there be any other reason for this?
    Thanks,
    Sonali.

  • Prigramming Logic details for SAP APO Planning Models

    Hi All,
    I need to learn more about different model available in SAP APO - DP, SNP and their behaviour.
    Request to please share any link or document associated with programming logic in different planning models available in APO.
    Thanks in Advance.

    Hi Senthil,
    Thanks dear for your response.
    What I am looking in programming details of exisiting DP forecasting models like Trend Analysis, Linear Regression.
    What I know about MLR is that system uses below equation
    Yi = bo + b1X1 + b2X2... + bn Xn
    where Yi = Sales History
    bo = Mean
    b2 = co-efficients
    x2 = causal factor etc.
    Do you have document which details out how the figures are computed using these planning models?
    Once again thanks for your quick reply brother.

  • Naming changes for SAP business systems

    Hello
    I have developed my interfaces in which most of them are from SAP to third party. We have SAP configured with its SID as the business system (e.g. DC1). Now we are planning to change the name of all the business systems in SLD. I deleted the previous business system from the SLD and created the new one according to newer standard and configured receivers based on it.
    My problem is when I am posting the message through ABAP proxy its still taking the SID as the sender. As a result its not finding the receiver. Do I need to configure the sender in my source ECC system?
    Thanks in advance.
    Regards
    Rajeev Patkie

    Hi Rajeev,
    The Business system details like the client and logical system etc, help the proxy to know where it has to go.
    Not for the sender system from where you are executing the PRoxy will have a Business system .Please check if the information is for the Business system can be seen correctly in the ID>BS>service-->Adpater specific identifiers.
    Also you sender XI adapter is attched to this Business system.
    No what is your receiver? You haven't specified that?
    Also, you can just reactivate the PROXY once.
    Cache refresh??
    Regards
    Vijaya

  • Naming standards for Document Routing ID

    I was wondering if there are any standards or edits in place for the Document Routing ID? While setting up the X12/EDIFACT Tutorials, it mentioned filling these in, but I did not see anything on how this is used or what format the data should be in.
    I ran into an issue trying to use the value of '204' as a Document Routing ID. When this document would be processed by B2B, I would fine errors in the log stating it could not write to the IP_IN_QUEUE because of an "Invalid Agent '204'". Once I changed this value to X12_4010_204, this issue went away.
    Since setting up the initial Tutorials, I have figured out how this Routing Id is useful in processing, but still wonder why the value '204' wouldn't work.
    Thanks in advance for you input.

    Hello,
    Can you please try your setup with X12_204.
    Rgds,Ramesh

  • WSDL Standard for SAP NetWeaver 7.0 SP 15

    Hi all,
    I want to know, what WSDL-Standard is supported by NetWeaver 7.0 SP15. 1.1? 1.0?
    Thanks

    Hello Florian,
    Netweaver 7.0 supports the WSDL 1.1 standard:
    http://help.sap.com/saphelp_nw70/helpdata/en/44/624479f7e608fae10000000a422035/content.htm
    part of the main article "Web Services":
    http://help.sap.com/saphelp_nw70/helpdata/en/9b/dad1ae3908ee44a5caf57e10918be9/frameset.htm
    wsdl 1.1 @ w3c:
    http://www.w3.org/TR/wsdl
    Good luck and have fun.

  • DataModeler v3.3.0 - Naming standards template for surrogate keys creation

    I'm using DM 3.3.0.734 and in the logical model we now can define in the entity properties to "Create Surrogate Key".
    When we use Engineer to relational model, for each entity is automatically created a new column using the naming template {entity}_ID as NUMERIC (without precision) and is defined as primary key.
    My questions are:
    Is possible to define a different naming standard for surrogate key creation?. We define id_{entiry}
    Is possible to set the precision of NUMERIC surrogate key?
    If we define entity's column as Primary UID, these columns are included in an unique constraint, but are using the naming standards for PK.
    As consequence are created the following:
    Unique constraint name: entity_PK
    Primary key(surrogate)name: entity_PKv1
    There is any way to define naming standards like "{entity}_UID" for unique constraints, or even, "{entity}_SK" for surrogate primary key name?
    Can anyone help with some of these topics?
    Regards,
    Ariel.

    Hi Ariel,
    Naming standards template for surrogate keys creation I logged enhancement request for that.
    How to change those bad names (going to change them one by one is not an option):
    1) If those "transformed" unique keys are the only ones you have in relational model then simply can apply naming standards
    2) You can write transformation script to do that for you
    3) you can use new functionality - search, export to excel file, change the names there (using find/replace will be faster) and return changed data back to relational model
    you can find description for that here:
    https://apex.oracle.com/pls/apex/f?p=44785:24:13179871410726::NO:24:P24_CONTENT_ID,P24_PREV_PAGE:6621,16
    http://www.thatjeffsmith.com/archive/2012/11/sql-developer-data-modeler-v3-3-early-adopter-search/
    http://www.thatjeffsmith.com/archive/2012/11/sql-developer-data-modeler-v3-3-early-adopter-collaborative-design-via-excel/
    You should search for _PK, then filter result on Index and you can export result using report functionality (to XLS or XLSX output format). You can create template and include only table and name (of index) as properties to be included into report.
    Regards,
    Philip

  • NAMING STANDARDS

    Hi,
    What are the standard naming rules for SAP in BI?
    I am configuring cubes and i need to get an idea what is standards are used on other projects.
    Thanks

    Hi Daniel,
    It differs from one company to other. For example in one company they will use ZC_... for Custom cubes, Z_.. for custom char etc... but when you go to other company they may use a different set altogether. Its better to do a thorough research on the documentation of your company and I am sure you will be coming to know their terminology.

  • Naming standards within the NWDI

    As we're getting ready to dive into a development project with the JDI/NDWI/whatever-it's-called-this-week, I'm working on a set of naming standards.
    What are other folks using for naming standards for SCs, DCs, Tracks, and so forth?  Sap has published some guidelines, but nothing really substantial that could be morphed into a Best Practices document.
    Regarding DC names, SAP seems to be all over the map - sometimes the name of the DC is reflected in the package naming withing the public jar files, sometimes there doesn't seem to be any obvious relationship.
    A thread such as this could be very useful both for me, and anyone else who is just starting to use the Developer Infrastructure, so let's get a bunch of ideas out in the open, and get a discussion going.

    Hi Ken,
    Great innitiative. I'll try to start the ball rolling:
    I have noticed that the DC name (without SC name) is apparently the key in SDM, i.e. you cannot deploy two DCs with the same name even if these are in different SCs. This means that reflecting at least part of your package hierarchy in the DC names is essential.
    Regards,
    Thorsten

  • How to set naming standard that sets max number of words in column name?

    Hi all,
    Is it possible to set naming standard that sets max number of words in colum (or table) name?
    I was looking video (1:08min)
    http://download.oracle.com/otn_hosted_doc/sqldev/UserDefinedDesignRules/UserDefinedDesignRules.html
    And here you can see how rule is triggered.
    "...Name has 2 words; Max permitted - 1".
    Thanks a lot

    Hi,
    you need to create glossary and set it in naming standards for your design.
    This document is still valid - http://www.oracle.com/technetwork/developer-tools/datamodeler/datamodelernamingstandards-167685.pdf
    Naming standard settings are located :
    - DM 3.x - "Preferences>Data Modeler>Naming Standard"
    - DM 4.0 - Design dialog>Settings>Naming Standard
    If you want only check on number of words then glossary can be empty and you can set "Incomplete modifiers" option in that glossary.
    Philip

Maybe you are looking for