SAP Documentation for NWDI Naming convention

Hi,
I need SAP documentation for NWDI Naming convention, Produt, unit, SC etc..
Thanks

Hi,
This is the link for SAP NWDI
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/e0b2b146-5776-2910-4a8f-9b3190eab060&overridelayout=true
Regards,
Niraj

Similar Messages

SAP documentation for t.code F.05

Hi All,
could anyone paste here the SAP documentation for t.code F.05 (Foreign currency valuation) in 4.7 release?
Thanks a lot
G.

Hi,
the documentation is available in help.sap.com:
[Foreign Currency Valuation|http://help.sap.com/saphelp_470/helpdata/en/96/8b3c2d43ce11d189ee0000e81ddfac/frameset.htm]
(choose Foreign Currency Valuation in the left side of the screen)

Best Practices for farm naming conventions

Hi
I wanted to get some basic best practices and recommendations for farm naming conventions when setting up multiple farms in our environment.
what are the do's and don'ts?

First, figure out why you need multiple farms :-)
I generally name machine accounts based on purpose and location, with a numeral. For example, a SharePoint server in Redmond might be:
REDSP01, REDSP02, REDSP03...
And a SQL Server dedicated to this SharePoint farm might be:
REDSPSQL01, REDSPSQL02...
If using a SQL cluster, I might use:
REDSPSQL01A, REDSPSQL01B...
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

NWDI naming conventions

Hi,
does anybody know about documentation with proposals of naming conventions for
- products
- software units
- Software components
- Tracks
and so on?
Would be great to get a link.
Thanks in advance
Norbert

Hi Norbert,
there are not much conventions for naming of that entities. The most obviuos and well known ones are given/referenced below.
the very first and the most important is namespace (aka vendor aka prefix - depending on the context)
in order to avoid any collisions it is always strongly recommended to use a reverse internet domain reserved by your company as a vendor or prefix for all named entities.
in that way for SAP the vendor/prefix should be "com.sap", for MSFT - "com.microsoft", for W3C - "org.w3" etc.
Further constraints you might find in SLD:
- help
- namereservation dialogs contain additional information
- you might also have a look at <a href="http://help.sap.com/saphelp_nwce10/helpdata/en/45/5a1babec592a4de10000000a11466f/frameset.htm">NW CE 7.1 SP3 help</a> (the rules are about the same for other releases)
A few more hints
- it is not recommended to repeat the vendor/prefix in the main part of the name,
instead of vendor "org.demo.my", name "my.org.demo.abc"
recommended: vendor "org.demo.my", name "abc"
- there is no need to include entity type in the name, e.g.
instead of name "my.demo.org.DC.my.application"
recommended: vendor "my.demo.org", name "my.application"
- if necessary (only you may now if it is the case), define a prefix per product and use it consistently in all entities those belong to the product. That would be particularly hepful if you plan to develop more than one product
- pay attention to the case(!)
If the information is too generic - you might give few examples those would help you to get better feeling.

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?

SAP documentation for working with BExRepositorySheet?

Can someone point me to where I can find some documentation for programmatically working with the BExRepositorySheet, in particular reading from and writing to the embedded XML script within that sheet.
As I wrote in an earlier thread (BEx 7.0 -- SAPBEXqueries hidden sheet gone -- where is the data stored now?), what I'm trying to do is re-program a very elaborate Excel VBA solution we built for BEx 3.5 to automate the processing of BEx reports by reading the stored variable values in the SAPBEXqueries sheet, but with that sheet gone in BEx 7.0 now, and all that meta-data being stored in BExRepositorySheet XML script instead, I need to be pointed in the right direction as to how to work with the BExRepositorySheet in BEx 7.0.
Thank you kindly for any information.

Hi Stephan,
please see link [http://wiki.sdn.sap.com/wiki/display/VC/WhatisWebAPI|http://wiki.sdn.sap.com/wiki/display/VC/WhatisWebAPI] that contains a reference to a 300+ pages PDF document describing the Web API commands. It is describing the ABAP Web Runtime for BW 3.5 which also exists in BW 7.0.
Best regards
Matthias

Looking for SAP Documentation for B2B Adapater

Hi
I am looking for the following SAP documentation. I have the other documents in the series but cannot find those documents. Could anyone advise where these can be found?
Regards

Thanks Dieter,
I actually looked at my screen and saw the documentation link :-) So all downloaded now but I still can't find the documnetation I want. Specifically the learning guides. All the documents, and SAP help, are very straightforward guides. The learning series provides a more detailed overview into the functionality and a practical guide to the implementation.
The document ' SAP NetWeaver Process Orchestration, business to business add-on 1.0 SP00 How to Proceed Guide' contains a reference to the documents I require at the back on Page 9. Yet they are knowwere to be found. Even in the Process Orchestration Resource Center: SAP B2B Add-on Wiki has some documents, but nothing that I actually need.
I think the only thing I can do is raise a customer message. Its so frustrating.
Regards
Rob

Forcing naming convention for queries and views

Hello Friends,
Can anyone tell me how to Force user to save queries with starting letter 'Q' and all views with 'V'.
I know how to restrict queries ..
Please tell me how to Froce Views to save with first letter 'V'.
Thanks,
Ram

you need these values in your role to restrict them save queries with starting letter 'Q' and all views with 'V'.
S_RS_COMP
         RSZCOMPID-Q*
         RSZCOMPTP - REP
S_RS_COMP
         RSZCOMPID-V*
         RSZCOMPTP - QVW
S_RS_COMP1
         RSZCOMPID-Q, V
         RSZCOMPTP - REP,QVW
and as you know activity will be 01 for giving create ability, don't forget to restrict on infocube and infoarea. one thing you have to rethink is why you want to use Q, V as a starting letter, I would prefer Y,Z.
and lot of companies do restrict for different naming conventions on different infoarea/infoprovider. just a casual suggestion, it will be better for your company in future, if you restrict the reporting component's naming conventions more specific. something like Zinfoprovider name_reporting component_*.
regards
Message was edited by:
        Keerti Vemulapalli

Need naming convention for ESB

Can somebody help me with any document or suggestions for the naming convention in ESB.
I need it urgently as we need to build the design document in which we have to mention the naming convension for ESB

The only thing I can come up with wright now is that you need to use the 'localhost' name for the wsdl-files, endpoints, esb settings, etc. because otherwise when moving from development to test, ... the ESB-services, BPEL-processes won't work anymore because he can't find the endpoints during deployment because your servername/computername was added in the endpoint.
Another best-practice would be to add a 'IN'- or 'OUT' suffix to the routing services giving the developer, end_user the possibility to know what the esb's aim is, to get data or to feed data.

Logical System Naming Convention

Hi Guruz,
Is it mandatory to name your logical system starting with SAP system name. I went through SAP Documentation for creating logical system, it says <sap system name>CLNT<client number>. I didn't put my SAP system name for the first part<sap system name> instead some random letters. I know this question may sound stupid but I am right now in the middle of the integration so, I don't want to change it. Please confirm.

I'm work for the customer who has ~4000 logical systems defined (not all represent SAP boxes though). Which I find quite a lot, yet given the rules of naming convention helps a lot.
I would say that having the system name should be used whenever we talk about Logical Systems representing SAP boxes. But in case of external non-SAP applications, it is helpful to represent them by the external system.
Say, you have 20 SAP installations, each sending interface to application A. Then it is easier to monitor in XI/PI interfaces for single receiving logical system 'A'. But if you want to find out messages from given sending SAP system, then using SAP system name is recommended to extract such data quickly.
Regards,
Dominik Modrzejewski

Naming conventions in XI !

Hi,
do we have any pdf or blog or links for the naming conventions to be followed in XI?
are there any standard naming conventions suggested or set by SAP for XI?
thank you,
regards,
Babu

Satish,
thank you for quick reply.
this link doesnt work;
http://media.sdn.sap.com/html/submitted_docs/Implementation_Roadmap_XI/index.htm .
I have downloaded ASAP zip file from one of the link,if you think this is not useful then its fine otherwise can you give me the correct one.
thanks.
Babu

.tpz files naming convention / export from PI 7.0

Hi,
When I export the repository or Directory content from PI 7.0 the naming convention PI gives its own naming convention. Starting wit XI3_0 * .tpz
Why does it start with XI3_0*.tpz for we have PI 7.0?
Do we need to change any Visual admin or exchange profile parameter to get the naming convention to PI7_0*.tpz
Thanks
Sachin

Hi,
The import and export functionality of XI 7.0 uses the expression 'XI 3.0' instead of 'XI 7.0' in all transport screens of the Integration Builder. Furthermore the name of XI 7.0 exports will always start with the prefix 'XI_3_0' and not 'XI_7_0'.
Reason and Prerequisites
The reason for this behaviour is that the transport code and format of XI 7.0 and XI 3.0 is identical.
Solution
There is no fix for the naming convention, but there is a positive consequence: XI 3.0 export files can be produced by XI 3.0 and XI 7.0 and can be imported into XI 3.0 and XI 7.0.
Refrence Note
Note 936254 - XI 3.0 Imports and Export in XI 7.0
Award points if helpful.
Thanks,
Tanuj

SAP Documentation Download/Order ECC6

Hi,
i'm looking for a possibility to order/download
the SAP-Documentation for ECC6.
Thanks,
Regards, Dieter

use the following link to order free CD for SAP help
https://pgwshop.sap-ag.de/scripts/wgate/ww204b5c14d6/flN0YXRlPTIyNjM0LjAwMS4wMi4wNA==?okcode=WCLG&target=_top&forcetarget=yes
once u go o this page u see the right hand sideoverview bar here locate the R/3 and click on EP 470, Ext. Set 1.1
the list will open
look for the english/german version adn add to your cart
the price is zero

MSI naming convention

I just got a K7T266 Pro2-UL (MS-6593). Searching in MSI's web I found that there is another mobo with the same reference (MS-6593): KT3 Ultra2-C. They are clearly different, even one is based on KT333 chipset while mine is based on KT266A chipset.
After I realize this is not the only case. This fact is really inconvenient because it could cause serious problems (I read in another forum some cases of wrong BIOS updating due to very similar motherboard names).
Is there any reason for that naming convention?

Hi,
Yep, you are right, the naming of MSI boards is really bad :D
The example you gave is a good one, but the 2 boards are a different version.
It's even a bigger mess then that :D
We asked MSI a long time ago to give at least very board a unique MS-XXXX number so that there can be little confusion.
But it still didn't change....
At the moment there is just 1 way to be sure of what BIOS you need for what board....
And that is by checking the MS-XXXX and Version number, only then you can be sure you get the right BIOS..

SAP Naming Conventions for DB Data Files

Hi Everyone!
We are about to install a SAP ECC 6.0 SR3 ABAP on Windows Server 2008 (R2) & SQL Server 2008 SP1 and we want to name the DB data files as follows:
<sid>DB_Data_001.MDF/NDF
Do you see any problem with this or think this could lead to a problem in the future?
We were unable to find a SAP note or SAP recommendation about this, we only found SAP Note 27428 but itu2019s for Oracle.
Thanks in advance!
Best Regards,
Nicolas

Hi Nicolas,
I thought about all corners where this could possibly lead to a problem (e.g. monitoring, DB13, ...) but couldn't think of a single report or transaction where this would cause problems.
To the database itself the names of the files do not matter at all and in the SAP transactions the datafiles are only read to display them in monitoring transactions like DB02 or RZ20. These transaction do not expect a certain naming convention so I don't see anything that would count against using different filenames.
Regards,
Beate Grötschnig

SAP Documentation for NWDI Naming convention

Similar Messages

Maybe you are looking for