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

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
Question: 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 readability and maintainability 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

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

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) Identifying Table
The best way to find out from which tables the data source is getting updated is to search in help.sap.com by using the selection criteria "datasource and the name of the data source".
This displays a table which gives the name of the fields and the table names
2) Naming Convention
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) Important tables
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

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

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

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....

PSA tables

hi all,
while transferring data into BW, a transparent table is created in the PSA for each activated transfer structure. the name for this PSA table is generated by the system. How can i find out this technical name of the PSA table. Do these system generated names of PSA tables follow some naming conventions like some of the other tables in BW??
with regards,
Priyank

Hi Priyank,
Yes, most of the "BW System defined tables" follow a naming convention. I am not sure what but I am pretty sure since I program usually follows a set of logic and that includes creation of tables dynamically.
Btw, why do you need to know it? You can view the contents directly using RSA1. Why bother?
--Jkyle

File name naming convention in File Adapter configuration in ID

Hi All ,
I have a query related to xml filename created in IDOC-XI-FILE scenario based on value of one of IDOC field .
The scenario is like this :
I have to send one xml file per store for material master . In this case how can I define my file name with store name in File adapter configuration in ID .
Naming convention should be
<storename>_date_masterdataname.xmlwhere store name is one of field of IDOC .
Plz help me .
Thanks in Advance
Regards
Prabhat Ranjan

Hi Prabhat,
take a look at this weblog:
/people/jayakrishnan.nair/blog/2005/06/28/dynamic-file-namexslt-mapping-with-java-enhancement-using-xi-30-sp12-part-ii
you have to specify variable substitution
(in the file adapter)
and give the path to the store name (in the variable sustitution table)
you file name schema (from the file communication channel can look like this)
%storename%_date_masterdataname.xml
Regards,
michal
Message was edited by: Michal Krawczyk

Data Modeler - Naming Conventions

I was using Oracle Designer for several year.
This product could drive you crazy because sometimes, but the strength was in my opinion the datamodelling part.
It saved you a lot of time because you kept stuck to the logical model generated your relational model and had all scripts satisfying all naming conventions you needed.
In Data Modeler i really miss the naming conventions and can't understand some parts, sometimes somebody here can help me if i have overseen something or it is just not implemented.
Naming conventions as example:
We work with surrogate keys.
Two well known tables - Employees (abbreviation EMP), Departments (abbreviation DEP)
They have one relation 1:N one department has many employees
In Designer i would define the EMPLOYEE entity, would set the table-abbreviation, the attributes and the primary key.
The same with DEPARTMENT. I would design it WITHOUT any column for the foreign key constraint.
Then i would create a relation between this two tables.
Last step is to generate the relational model.
a) Designer automatically adds ID as surrogate key on every table (you could configure that, it was dependent on a domain)
b) it automatically adds the table abbreviation as prefix on every column (even here it's configurable)
c) it automatically adds the a foreign key column in the child table with the prefix of the master table (f.e. EMP_DEP_ID or DEP_ID if you prefer not to prefix every column... what i do)
It was really easy to get your scripts.
Things i don't understand in Data Modeler:
In a logical model you should design entities, attributes and relations and don't mess around with FK-columns.
Is there any support for surrogate keys? I don't wanna add an ID manually with every table.
In Data Modeler an additional COLUMN(!) is added with every Foreign key relation, i could live with that, but there is no way to tell
Data Modeler to prefix it automatically. The name can just be changed in the Relational View afterward.
P.S.
Surrogate Keys.... There are some pros and cons for/against this out there. I have seen a lot of Oracle Projects and in all except one i always had a surrogate key column. It really makes life
easier. In the one no-surrogate-key-project we began to add surrogate keys after a while...

COLUMN(!) is added with every Foreign key relation, i could live with that, but there is no way to tell
Data Modeler to prefix it automaticallyLook at "General options>Naming Standard>templates" - you can define template for FK columns/attributes and then apply them for whole relational/logical model using "Apply Naming .." functionality from pop-up menu in the browser. For Logical model (FK attributes) - you also need to clear related setting at "General options>Logical>Keep as the name of originating attribute".
Templates are also used when objects are created, thus when new FK is created, then templates are used to generate name for foreign key and FK columns. Well you have to define table and column abbreviation in order to get them used in generated names - Re: Data Modeler: Naming
There is no support for surrogate keys in current release.
Philip

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.

How to create new check for SELECT* , Naming conventions etc..

Hi all,
   I would like have a solution for the below checks are possible or not in ABAP - CODE INSPECTOR. If possible can you please give me the solution..
a). Performance checks i.e, SELECT* , LOOP without field strings, FOR ALL ENTRIES IN SELECT STATEMENT.
b). Custom naming conventions.
c). to check if further modularization can be done in the program,
d). also the coding standards.
PLEASE help me , i am struck with it for long time in getting the solution...

> a). Performance checks i.e, SELECT* , LOOP without field strings, FOR ALL ENTRIES IN SELECT STATEMENT.
> b). Custom naming conventions.
> c). to check if further modularization can be done in the program,
> d). also the coding standards.
the code inspector allows the creation of new checks, you should consult the documentation how to do it.
The main problem of the code inspector are hits, which are actually no problem. And I think this is a problem with your checks:
+ SELECT* this is no performance problem, only in cases when the table is really wide then a field list makes sense, i.e your check
   will find a lot of false hits
+ LOOP without field strings ... you mean fs =field symbols, same as with SELECT *
+ FOR ALL ENTRIES IN SELECT STATEMENT   ???? FOR ALL ENTRIES is fine
+ Custom naming conventions ... hmmm be more precise, I think it can be hard
+ to check if further modularization can be done in the program,
    before you want to program can you please explain how you check manually .... I would be interested
+ also the coding standards.   .... what is that?

PSA Table Naming convention

Similar Messages

Maybe you are looking for