User Tables Naming convention / Namespaces

Dear all,
Does anybody know where to get Informations about SBO NameSpace Conventions ?
I have 2 Questions for naming conventions
1) Creating a UserDefinedTable like this
   Table Name  :  Z_NameSpace_MyTableName
   Is it necessary that any FieldName of the
   table uses the NameSpace Prefix ?
   Like this: NameSpace_PosNo
2) Adding UDF to SBO Tables
   Is it necessary that UDF Fields uses the
   NameSpace Prefix ?
Thanks

Thomas,
The NameSpaces are only used while creating a UserDefined Table.
UserDefined Table :
The convention for the name is NameSpace_MyTableName (without the Z_). Its length can't exceed 19 characters.
When adding a user table, SAP Business One automatically adds the symbol @ as a prefix to the table name. For example: if you add a table named "ABC", the resulting table name will be "@ABC".
When referring to a user defined table you must use the name including the prefix @.
UserDefined Field :
you do not have to add the NameSpace in the name of the field. Its length can't exceed 8 characters.
When you create it using the UserFieldsMD object, the character "U_" will be added to its name, and created in the table.
To conclude, the NameSpace is only used for the table.
The DI API will add @ for the table, and U_ for the field.
You can see SAP note 647987 about NameSpace
Sebastien
Message was edited by: Sébastien Danober

Similar Messages

  • Best practices in Internal table naming convention GT ,  GS , LT  ,  LS  ??

    Hi Gurus,
         Are GT_ ,  GS_ ,  LT_  ,  LS_  --- the  Best practices in Internal table naming convention ????
         I  have  seen this  naming convetions adhered in standard programs .
         What each one  of  the  below  signify
         GT_ ,  GS_ ,  LT_  ,  LS_   ??????? 
    Regards
    Jaman
    Message was edited by:
            ABAP Techie

    Hello
    I use the following naming conventions:
    - G = global variable
    - L = local variable
    - T = internal table
    - S = structure
    - D = field
    That's how the combinations look like:
    - GT_ITAB     = global itab
    - GS_STRUC = global structure
    - GD_FIELD   = global field
    - LT_ITAB     = local itab
    - LS_STRUC = local structure
    - LD_FIELD   = local field
    Function module parameters have to stick to the following rules:
    - I = importing
    - E = exporting
    - [C = changing -> never used]
    - IT_ITAB = imported table type (itab)
    - IS_STRUC = imported structure
    - ID_FIELD   = imported field
    - ET_ITAB = exported table type (itab)
    - ES_STRUC = exported structure
    - ED_FIELD   = exported field
    Depending on their semantics TABLES parameters look like:
    - IT_ITAB = imported data
    - ET_ITAB = exported data
    - XT_ITAB = changing data (import & export)
    Here are the conventions for FORM routine parameters:
    - UT_ITAB = using itab (data are usually treated like constants; no changes will be transfer - although possible - to the calling program)
    - CT_ITAB = changing itab (if it is semantically an exporting itab then one of the very
    first statements in the routine is: REFRESH ct_itab. )
    - US_STRUCT
    - UD_FIELD
    - CS_STRUCT
    - CS_FIELD
    Conventions for class/interface parameters:
    - IT_ITAB = importing table type
    - IS_STRUC = importing structure
    - ID_FIELD = importing field
    - ET_ITAB = exporting table type
    - ES_STRUC = exporting structure
    - ED_FIELD = exporting field
    - RT_ITAB = returning table type
    - RS_STRUC = returning structure
    - RD_FIELD = returning field
    Conventions for class/interface attributes:
    - MT_ITAB = table type
    - MS_STRUC = structure
    - MD_FIELD = field
    - MC_CONST = constant
    <b>Question</b>: Are there any advantages of such elaborated naming conventions?
    My answer to this question is: Yes, definitively.
    I believe that the advantage of semantically differentiating TABLES parameters of function modules is quite obvious:
      CALL FUNCTION 'Z_BAD_NAMING'
        TABLES
           itab1 = ...
           itab2 = ...
           itab3 = ... .
      CALL FUNCTION 'Z_GOOD_NAMING'
        TABLES
           it_itab1 = ...
           et_itab2 = ...
           xt_itab3 = ... .
    I also believe that my naming conventions clearly enhance <b>readability </b>and <b>maintainability </b>of my programs.
    Regards
      Uwe

  • BW Table naming convention

    Hello,
    I find the following table naming conventions from the manuals BW systems
    /BIx/E<InfoCube>  - E Fact table
    /BIx/F<InfoCube>  - F Fact table
    /BIx/D<InfoCube>  - Dimension table
    I have the following questions
    1.Could you please let me know whether all the tables starting with '/BIx/D' will be dimension table only or there could be other tables ?
    2. From the description field in SE11, I could not find the details for some of the tables.Please let me know whether there is any other way to identify the table type(Dimension,Fact..)
    3. Also I would like to know the naming convention for aggregate tables.
    Thanks,
    Aravinthan

    Hi ,
    http://www.learnsapbw.blogspot.com/2008/03/naming-convention-in-sap-bw.html
    Antonio Voce

  • PSA Table Naming convention

    Hi Experts,
    Currently I am working on the BW3.5 version. I would like to delete the old PSA req through Process Chain. I need some clarification. Please provide me your suggestions.
    I have collected full list of PSA Table in Development system through excel, then i can filter out by source system.
    While create the Process Chain for the PSA deletion, i want to add the collected PSA tables(Object Name).
    Please refer the screen shot. But i noticed that "differing in naming convention for PSA from Dev to quality & prod!!".
    So if i transport this Process chain to quality & production, this will not work same as in Dev.
    I have already referred the form and found the thread that discuss about the same issue. But resolution not given.
    Please help me to get it this issue resolved. Thanks in advance.
    Similar issue thread:
    psa
    Screen shot:
    http://img818.imageshack.us/img818/3963/psa1.jpg
    Thanks,
    RR

    To explain this I will take the systems with this naming Convension.
    Dev BW: BWD
    Dev ECC: E01
    Quality BW: BWQ
    Quality ECC: Q01
    When we take the conversion in the quality system you should have the below parameters.
    BWD to BWQ
    E01 to Q01
    Q01 to Q01
    FLAT File to FLAT FILE.
    So lets say the source system related object is goign from D to Q lets say transfer rule, the same will be converted to Quality system based on the conversions maintained in this table: RSLOGSYSMAP.
    So the source system related objects will gets converted to the target system objects using the refernce maintained in this place.
    Hope this is clear for you now.
    Thanks
    Murali

  • Naming Convention and way to locate Table Names in B.I

    Hello All,
    I like to know information about
    How to find a table
    Naming convention of table
    Important Tables
    I will be thankful ,if anyone provide this information..

    Hi Path,
       I will provide information what i had got through various sources...
    1) <b>Identifying Table</b>
           The best way to find out from which tables the data source is getting updated is to search in <b>help.sap.com</b> by using the selection criteria<b> "datasource and the name of the data source".</b>
    This displays a table which gives the name of the fields and the table names
    2) <b>Naming Convention</b>
      1./bic/f (cube name) is the fact table of a content cube
    2./bic/D (cube name) P is the package dimension of a content cube
    3./bic/D(cube name) U is the unit dimension of a content cube
    4./bic/D(cube name) T is the time dimension of a content cube
    5./bic/D(cube name) I is the user defined dimension of a content cube
    6./bic/m (object name) master data of object
    7./bic/t (object name) text data of object
    8./bic/H (object name) hierarchy data of object
    9./BIC/I* SID Structure of Hierarchies
    10./BIC/K* Conversion of Hierarchy Nodes - SID
    11./BIC/P* Master Data (Time-Ind.): Characteri
    12./BIC/Q* Master Data (Time-Ind.): Characteri
    13./BIC/S* Master Data IDs: InfoObject
    14./BIC/T* Texts: Char.
    15./BIC/X* Attribute SID Table: InfoObject
    16./BIC/Y* Attribute SID Table (Time-Dep.):
    17./BIC/B* Transfer structure PSA/Changelog
    18./BIC/A* ODS Active records
    19./BIC/F* Info cube F-Fact table
    20.BIC/E* Info cube E-Fact table (compressed records)
    21./BIC/D* info cube dimension tables
    3) <b>Important tables</b>
    I has collected some important tables that may help you..
    authorization:
    RSSTOBJDIR (Management Table for Authorization Objects): Link between specific authorization object and Info source (table used by transaction RSSM)
    InfoPackage
    RSLDPIO Links datasource to infopackages
    RSLDPIOT InfoPackage Text Description
    RSLDPRULE ABAP source code for InfoPackages
    RSLDPSEL Hardcoded selections in InfoPackages
    ProcessChain
    RSEVENTCHAIN Event Chain Processing Event Table
    RSEVENTHEAD Header for the event chain
    RSEVENTHEADT Header for the event chain
    RSPCCHAIN Process chain
    RSPCCHAINATTR Attributes for a Process Chain
    Queries
    RSZELTDIR Directory of the reporting component elements
    RSZELTTXT Texts of reporting component elements
    RSZELTXREF Directory of query element references
    RSRREPDIR Directory of all reports (Query GENUNIID)
    RSZCOMPDIR Directory of reporting components
    Workbooks
    RSRWBINDEX?
    List of binary large objects (Excel workbooks)
    RSRWBINDEXT?
    Titles of binary objects (Excel workbooks)
    RSRWBSTORE?
    Storage for binary large objects (Excel workbooks)
    RSRWBTEMPLATE?
    Assignment of Excel workbooks as personal templates
    RSRWORKBOOK?
    ‘Where-used list’ for reports in workbooks

  • Naming convention table name Java

    Dear expert,
    I know that in the ABAP world, when I create a custom table, it have to start with Z.. or Y.. in the name.
    Is this the same when I need to create a table in the Java schema?
    Thanks for you help.
    Mario

    Hi, Ferruccio,
    In the Java world, table naming conventions apply when you define your tables in the Java Dictionary (which is a metadata representation of a real database).
    The names of tables that are defined in the Java Dictionary should:
    - begin with a prefix (for example, the name of a component ‚FI_*’);
    - not exceed 18 characters (including the prefix);
    - not contain Open SQL keywords (for example, SELECT, INSERT, UPDATE, MODIFY and DELETE);
    - contain only permitted characters, i.e. letters, numbers, and underscores.
    I hope that helps!
    Regards,
    Yordan

  • Checking naming convention of internal tables in code inspector

    Can anyone please explain how in the code inspector can I check names of internal tables (like it_) that I use in a report program ? I know that I can specify it_ in Programming Convention -> Naming Convention->Program Global -> Data but this entry is not specific to internal tables as it also applies to variables and work areas. Apart from this is there any entry I can maintain in the Extended Naming Conventions for Programs(introduced in ECC 6.0)? Kindly reply at the earliest.

    Hi,
    Check these links for implementing the custom conventions in the code inspector
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/nw/how%20to%20build%20a%20new%20check%20for%20the%20code%20inspector
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webas/abap/evaluating%20the%20quality%20of%20your%20abap%20programs%20and%20other%20repository%20objects%20with%20the%20code%20inspector
    hope it helps you.
    Thanks!

  • Naming Convention in Table

    Hi,
    What is the naming conventions in the table which starts with i.e. ( V_, VV_,VC_)
    Regards
    Rajesh

    Hi Rajesh,
    Views will start with the value "V_".
    VV should be view variant not sure. You can post this question in abab forum.
    Regards,
    Brinda

  • Can anyone tell me the naming conventions for PSa tables

    hi all,
    After the data is loaded into the psa. how to look at the records that are there in psa. And can anyone tell me the naming conventions for psa tables.
    like BIC/????
    thanxs in advance
    regds
    hari

    Hi Hari,
    You want to know the naming convention of PSA table. For that there is a simple technique try this.
    Go to - T code SE11
    In the database table check box give  /BI*  and click search
    next window  in the Description Text box give the r data source name(master)  like
    YIO_ID_ATTR which is assigned to infosource. then click OK.
    then you get the psa table structure.
    You can take structure and check in the T code SE 11
    Hope this is fine.
    Regards
    Sreekanth

  • NAMING CONVENTION OF X$ TABLES IN 10GR2

    Hi All
    I want to know if oracle follows any
    naming convention to x$ tables ...and also for the column
    names .if yes what is it.
    Thanks in Advance.....

    Well, I would second to Hemant that for these structures ( they are not tables exactly) , whatever convention Oracle has, its with it only. That said, the tables basically are the representations of the layers that work with the Kernel of Oracle. So the table names follow or represnt the layer on which they are based on. For example, X$KCBWDS is Kernel Cache(cache layer) Buffer Working Set Descriptor. So would be the column names within them , representing what the layer is doing .
    In anyways, its not really important to know the convetion, yes to some extent meanings of these strucutres may help butthat too is limited to some extreme cases only.
    HTH
    Aman....

  • Implement a technical naming convention for queries depending on user

    Hello,
    I'd like to implement a technical naming convention for queries depending on the user, because I want to make sure that the users are taking care of the naming conventions.
    For example a user defines a query and would like to save this query.
    During the save process he should only have the possibility to save the query with the name C_Name-of-Infoprovider_Text.
    The C should be unchageable for the user.
    The Name-of-Infoprovider should set automatically (if possible).
    The Text could be defined by the user.
    Another user would have this naming convention: X_Name-of-Infoprovider_Text
    Is there a possibility to implement such a function? (or just a part of this)
    Thank you.

    Thank you for your answer!
    Your answer helped me to implement a part of the naming conventions.
    Maybe some as an idea to implement the rest of the naming convention.
    --> Technical query name depending on technical name of the InfoProvider.
    Has anyone an idea?

  • Oracle Naming conventions

    Hi everyone,
    I wanted to ask you about Oracle Naming Conventions. I've found a lot of stuff on the internet. Here's a short summary of what I've discovered so far...
    These are absolute:
    1- All names should be between 1 & 30 characters (database names accept 8 characters max)
    2- Names can not be duplicated in the same namespace
    indexes, constraints... are in one "schema" namespace
    tables views... are in another "schema" namespace
    3- Only letters (lower & upper), numbers and $, # & _ are accepted in a name.
    4- Quoted identifier are case sensitive and accept all kind of characters.
    The previous rules can not be violated otherwhise the object won't be created.
    Now they are a lot of naming conventions...
    - Always use a plural names for table (USERS i.o. USER)
    - use a prefix or suffix in constraint, indexes, ...
    USERS_PK, USER_IDX...
    I want to talk about these. What are your own naming conventions?
    Thanks

    user13117585 wrote:
    Hi everyone,
    Well actually I am currently trying to make a document for my company. All the developers will need to follow the rules I'm writing.
    "It's good to be the king!"
    My problem is that, I have many databases with hundreds schemas and I want to normalize everything (no only me want that but the management too). Anyway,
    - Some people are still using only 8 letters for object names (tables, views, constraints...). Names are cryptic. I spend like an hour to understand what means DRPOLDSZ. And table columns are also limited to 8 characters (what could DELLOLCN mean??)
    - Some developers are using other conventions. A good Table example would be:
    TABLE DOSSIERS
    DOS_DOSSIER_ID
    DOS_NUMBER
    DOS_CREATION_DATE
    I hate that prefix in each column too;
    As do I. Going back to data normalization .... the prefix adds nothing.
    >
    - Some developers use other conventions
    some have table names in plural, others singular
    some don't use the _ to separate multiple words object names, some well
    some prefix table id some use postfix (id_table vs table_id)
    etc etc.
    I want to normalize all the databases to use one and only one convention; I already thought about it and wanted to know what you all have in place; how do you manage to have all your developers using the same conventions ?
    About [ http://ss64.com/ora/syntax-naming.html| http://ss64.com/ora/syntax-naming.html] (1) article, I've read it but, I don't agree with the guy on everything. He mostly uses prefix (pk_Table, idx_table, fk_table). When you give some thoughts, isn't it better to use suffix?
    Table_PK, Table_IDX, ...
    When you do a query on ALL_ or USER_OBJECTS, you can order them on OBJECT_NAME and have the name groupped together.
    I also prefer to have in the constraint name the base table and the referenced table. Instead of what the guy propose FK_TABLE_NAME, something like TABLE_NAME_REF_OTHER_TABLE_FK
    Well, you don't have to slavishly follow anyone else's document. Again, you are using those for ideas. In the end, you need to do what makes sense to you. Also realize that having A standard - almost ANY standard - is better and more important that sweating the pros-and-cons of any particular detail. Just make a decision and go with it. Get management to sign off on it as the standard.
    My question is not really a question but more a how do you handle all kind of developers and what is the best way to force them to normalize and use the same conventions...The only way to force it is to take "CREATE object" away from the developers. This is actually done in many shops. If you can't do that, then at least set yourself a task of auditing and going back to violators. If you get some recalcitrant violators, elevate it to management - who you had sign off on it.

  • HR report category naming conventions..

    Hi All,
    As few of you suggested me in my last post, I decided to assign new HR report category to my report for LDB PNP. Now it does not let me change the selection fields of in-built categories which is quite obvious. Now when i create a new one it gives me the error message of choose the key from allowed namespace?
    does anyone know if there is special naming conventions for HR report categories??
    i tried Z but does give me the same error..
    stuck up..
    plz help..
    Reena..

    Hi Reena,
    I checked ur error. For me also it is giving the same error. I analysed & found as below.
    In se38->RDDKOR54 check this report & give table name as T599C.
    This will give you the customer name space for this table.
    So you can give the name starting with only spscified letters in this report.
    So use 0test or anything 0* to 7* it will work.
    All the Best!
    Thanks,
    Sarika.

  • What are the naming conventions we should follow while creating an object

    hi
    what are the naming conventions we should follow while creating an object in ABAP dictionary, i.e while creating zee table.

    Hi,
    Namespaces and Naming Conventions
    SAP has reserved name ranges for customer objects and SAP objects. Use these customer name ranges to make sure that your objects are not overwritten by SAP objects during the import of corrections or an upgrade.
    This documentation lists the customer name ranges for the different system objects.
    Only use the customer name ranges. If you do not keep to the name ranges for customer objects you may lose your development objects.
    SAP delivers a few system objects with names that fall within the customer name range. These objects already existed when the customer name range was extended from YY/ZZ to Y/Z. These objects are listed in table TDKZ.
    Regards

  • Do you have suggestions for naming conventions within AIF?

    Hi Folks!
    Being new to AIF I'm currently in the information gathering phase for myself and colleagues as we are starting to think about implementing interfaces with the help of this toolbox. I already found and read (or at least skimmed!) through various of your discussions as well as the very helpful blog posts from Verena, Michal and Andrey.
    One of the first things we want to do - before we really get started for real - is to come up with some feasible naming conventions for the various customizable bits and pieces like
    Namespace
    Interface Name
    SAP Data Structure (if applicable?)
    We also have some general questions:
    Does it make sense to prepare for one namespace per SAP-module or is it better to have just one and do the separation on the Interface name "level"?
    Is it preferred - even though SAP doesn't seem to enforce this - to start our own names with a "Z"?
    Searching SCN for "naming convention aif" didn't find anything related and while scrolling through the discussion forum I also didn't see any titles which might go into this direction. In order for us to not re-invent the wheel - or to start off in the wrong direction - I'm hoping to get some helpful pointers from you.
    Thanks much for any feedback you have!
    Cheers from Germany
    Baerbel

    Hi Bärbel,
    Your question is very good. We had the same and decided for following own approach:
    Namespace
    A Namespace is a concatenation of business process and SAP module, e.g. O2C_AR, P2P_AP, P2P_MM, R2R_GL.
    We have one global namespace for global objects as checks on currency code, date format value mappings, etc.
    Interface NameEvery interface has its own name. To be honest for inbound interface the names are more a user friendly description, for outbound we follow a little rule that they start with OUT_.
    SAP Data Structure (if applicable?)
    We try to do the structure mapping in the middle-ware and AIF is only responsible for the functional mappings.
    The root structure name is different between raw data and SAP data. But the sub structure and field names are equal. Because of this we can use the move corresponding fields or in some only monitoring interfaces even move corresponding structures.
    We also have some general questions:
    Does it make sense to prepare for one namespace per SAP-module or is it better to have just one and do the separation on the Interface name "level"?Because AIF support and business users differ in different business processes we separated in these processes and modules. In addition the recipients groups are similar to the name spaces.
    Is it preferred - even though SAP doesn't seem to enforce this - to start our own names with a "Z"?For namespaces (six characters) and interface names (10 characters) we don’t.
    Best wishes
    Christoph

Maybe you are looking for

  • Short dump in OLE_FLUSH_CALL

    Hi all, I am getting a runtime error in 'OLE_FLUSH_CALL'  DESTINATION SAPGUI. The exception is "CALL_METHOD_FAILED" from above FM. Strangely the error comes only in production. I have checked & compared the quality & production systems the settings a

  • VA43 working sometimes n sometimes not in call transaction

    I am calling VA43 transaction through ALV report. Input to it is a Contract number form VBAP. But sometime its dispalying correctly and sometimes gives error message. Can anybody tell why it is so?

  • HT201412 Icannot connect to the internet with my iPad.  It worked perfectly, now does not.

    My iPad suddenly is unable to connect to the wireless internet signal I have been using for a week.  What went wrong?

  • Date & hour in stored procedure

    create or replace PROCEDURE library_portal_home(ldt portal_home_non_login_log.logdatetime%TYPE,   COT portal_home_non_login_log.counter%TYPE) IS lv_count NUMBER; BEGIN   SELECT COUNT(1)   INTO lv_count   FROM portal_home_non_login_log   WHERE to_date

  • Integration Model - Resource Transfer to APO

    Hi, When i transfer a resource from R/3 to APO the data is transferred to APO but not to the active version. Instead it sits in APO as model independent version i.e without a version number. Please let me know how this happens and how to overcome thi