Information Steward naming conventions

Hi Experts,
Are there any naming conventions or standard guidelines for information steward.

I usually try to get those from the client. Usually if you are using a ticketing system I would put: (ticket number _ short description _ CP for column profile or Scorecard).
But as Dirk Pointed out there is no permanent format. Usually as short as possible would be best. The main goal would be for you to be able to easily reference and understand what a task or rule is doing.
Hope this helps.

Similar Messages

Storage Location Naming Convention without WM!

Dear all
We are facing serious problem in our Storage Location for Raw Material.
We have 4 types of Raw Material Seating (S), Panel (P), Metal (M), Wood (W). And they are all stored under Storage Location: RWSL.
Requirement:
Although we have visual guideline as to which industrial rack will store the type of Material, it is insufficient. We need a more refined storage location down to which BIN of the rack we will put the Raw Material.
Due to limited time and resource, we cannot have WM implemented right now. Thus, we have come out with 2 alternative to overcome this problem:
Alternative 01:
We will use the Fixed Bin field in Storage Data 02 by putting the Bin number assigned to each Rack.
E.g. For Seating material code:SEAT01, we will maintain the Fixed Bin as R12A01/A02, it means this Seating material SEAT01 will be stored at Rack 12, fixed bin A01 or A02.
Question to Alternative 01: Will it cause problem in GR, GR, Transfer Posting and Stock Count?
Alternative 02:
Instead of going into details to put Fixed Bin field in Storage Data 2, we will abandan the existing Storage Location RMSL by introducing new format for Storage Location
Here is the example of Alternative 02:
For raw materials, we will use 4 digits location numbers, consistent with other Storage locations, the 4 digits storage location will start with u201CR _ _ _u201D to represent each location
And,
R _ _ _ is:
R = Raw materials
2nd digit = Division (S= Seating, P =Panel, W=Wood, M=Metal and W=Wood)
3rd digit = Rack Number (A, B, C, Du2026 and etc.)
4th digit = Rack Zone - each rack will broken down into zone, each rack can possibility have 2 to 3 zone. 1 Zone can be 1 colume of the Rack
An example of a possible location and its meaning will be
RSA1 = Raw materials warehouse, Seating division, Rack A, Zone 1
RPB3 = Raw materials warehouse, Panel Division, Rack B, Zone 3
The challenge of this is that instead of having 1 Raw Material Storage Location like RMSL, we will have a lot more storage locations each for division of Raw material due to the Rack Number we have as well as the Rack Zone.
Question to Alternative 02:
If we use this alternative, will it impact our future implementation of WM? From design wise, is it feasible?
Please advise what is the best approach and the feasible design on it.
Many thanks in advance.
Edited by: Daimos on May 13, 2009 10:15 AM

Hi, here is the Pro and Co of both approaches:
Method 01: Use existing SLOC and add the Storage Bin info
e.g. SLOC: STM1
         Storage Bin: RSC3, where RS = Rack Seating, C3 = column 3
Pro 01:
It will cause less effort as we only need to use LSMW for material master to add in the Storage Bin data for all material of SCM.
Pro 02:
I have tested out that in TCode MIGO, apart from SLOC, the pertaining Storage Bin data also appear. Based on my discuss with Xian Chen, sometimes they use MB1C(GR), MB1A(GI) rather than MIGO due to speed issue, I will need to check the field status if can have Storage Bin field APPEAR, if can, it will solve the problem
Con 01:
The Storage Bin information will only appear in MMBE (Stock Overview) but will not appear in the standard SAP Inventory Report (e.g. MB52 Warehouse Stock). To view it from SAP Inventory Report, we may need to customize the standard report to show the new field Storage Bin. It needs Abap effort.
Con 02:
We must have a very good naming convention for Storage Bin. And again, in the above example, if a material is put in SLOC STM1 at Storage Bin RA A1 or C4, it will set a very rigid rule in the future if we need to change it, as I fear that one the Storage Bin has been used up. It will not allow us to change (need to do testing to find out)
Con 03:
Do we have the time to define all the Storage Bin for each SLOC? Operation wise, the store personnel needs to design it
Method 02: Use the new SLOC
Pro 01:
RSA1 = Raw materials warehouse, Seating division, Rack A, Zone 1. More organized. Easy to tell the material is at which Rack and which Zone of the Rack.
Assumption:
01. we must not have too many rack for one Seating division and also not too many Zone for each
      Division, else it will cause confusion
02. 1 material should stick to 1 Rack 1 zone as much as possible, else later the PP consultant will
     have hard to to perform GI due to too many SLOC assigned to a material.
Pro 02:
In report wise, we are able to show the SLOC in inventory report. No need to enhance the existing inventory report as we do not use Storage Bin.
Con 01:
If there are too many SLOC creation due to it. It may cause problem for PP perform GI as too many selection available for a material. This can be avoided if stick to the General Rule that one material is tied with one SLOC.
Edited by: Daimos on May 16, 2009 5:07 AM

Inconsistent naming conventions for Adobe Reader in software scan

I just want to see if anyone knows why Adobe's free pdf Reader appears both as "Adobe Reader" AND "Adobe Acrobat Reader". I manage software licenses for an organization of 400+, and it's difficult to know if, for instance Adobe Acrobat - Reader 6.0.2 Update - 6.0.2, should or should not be counted as a purchased license without actually visiting each workstation to verify. I've spoken with our network operations personnel and they confirmed that it is not manually entered by our personnel, but that it is something in the software. ??
Furthermore, why are the naming conventions not consistent even among those that can be identified easily? The list below is what I see when I run a report for all Adobe software on our network.
Adobe Acrobat - Reader 6.0.2 Update - 6.0.2
Adobe Acrobat 4.0 - 4.0
Adobe Acrobat 5 -- SC Install
Adobe Acrobat 5.0
Adobe Acrobat 5.0 - 5.0
Adobe Acrobat 5.0 - 5.1
Adobe Acrobat 5.0 SC Support
Adobe Acrobat 6.0 Professional - 006.000.000
Adobe Acrobat 6.0 Standard - 006.000.000
Adobe Acrobat 6.0.1 Professional - 006.000.001
Adobe Acrobat 6.0.1 Standard - 006.000.001
Adobe Acrobat 7.0 Professional - 7.0.0
Adobe Acrobat 7.0.1 and Reader 7.0.1 Update - 7.0.2
Adobe Acrobat 7.0.2 and Reader 7.0.2 Update - 7.0.3
Adobe Acrobat 7.0.3 and Reader 7.0.3 Update - 7.0.4
Adobe Acrobat 7.0.5 Professional - 7.0.5
Adobe Acrobat 7.0.7 Professional - 7.0.7
Adobe Acrobat 7.0.8 Professional - 7.0.8
Adobe Acrobat and Reader 6.0.3 Update - 6.0.3
Adobe Acrobat and Reader 6.0.4 Update - 6.0.4
Adobe Acrobat and Reader 6.0.5 Update - 6.0.5
Adobe Acrobat Reader 3.01
Adobe Acrobat Reader for Pocket PC 1.0
Adobe Reader 6.0 - 6.0
Adobe Reader 6.0.1 - 006.000.001
Adobe Reader 7.0 - 7.0.0
Adobe Reader 7.0.5 - 7.0.5
Adobe Reader 7.0.5 Language Support - 7.0.5
Adobe Reader 7.0.7 - 7.0.7
Adobe Reader 7.0.8 - 7.0.8
Adobe Reader Chinese Simplified Fonts - 1.0
Adobe Reader Japanese Fonts - 1.0
Adobe Reader Korean Fonts - 1.0
If anyone can answer this, I'd appreciate it. Thanks.

Junlie et al,
Starting with Acrobat 9 (announced on 6/2/08), Adobe will support the new ISO/IEC 19770-2 standard for universal software tagging. The new standard will allow customers to correctly identify the name, version, type and licensing status of Adobe software (starting with the Acrobat 9 family and later on as new versions of the products are introduced later this and next year).
I DO understand your frustration with the in consistencies in the naming of our software, but the problem of software discovery goes well beyond our lack of discipline. This is one of the many reasons why Adobe invested time and effort with the industry group defining the new open standard, and in software asset management in general.
More information about tagging standard can be found here: http://www.agnitioadvisors.com/info/content/view/44/1/
- Juan-Carlos

No error generated if batch process load file uses wrong naming convention

Another interesting one...
When using the batch processing functionality of FDM, which can be executed by either:
- FDM Workbench (manually)
- Hyperion FDM Task Manager (scheduled)
- upsShell.exe (scheduled and executed from a batch script)
..., one has to name the data file (to be loaded) using a specific file naming convention (i.e. "A~LOCATION~CATEGORY~PERIOD~RA.csv" format, for example). However, if one does not name the file correctly and then tries to process the file using batch processing functionality using any of the above three methods, FDM happily moves the file out of the OpenBatch folder and into a new folder, but the file is not loaded as it does not know where to map it to (as expected). However, there are no errors in Outbox\Logs\<username>.err to inform the user, so one is non the wiser that anything has gone wrong!
When using FDM Workbench, an error is displayed on the screen (POV - "Batch Completed With Errors, ( 1 ) Files Contained Errors"), but this is the only indication of any error. And normally, one would be scheduling the load using upsShell.exe or Hyperion FDM Task Manager anyway...
Has anyone else noticed this, or am I doing something wrong here? :-)

Yes, as per my original post the only feedback on any POV errors appears to be when using the FDM Workbench Batch Processing GUI.
Regarding the "Batch Process Report in FDM" you mentioned, are you referring to Analysis | Timeline accessible via FDM web client? Unfortunately this does not appear to provide much in the way of detail or errors, only general events that occurred. I cannot locate any batch process report, other than the log output I defined when calling upsShell.exe. However, this contains no POV errors...

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

JSP Naming Convention in JIT/JFF

Any kind of naming standards they follow in naming the JSPs ? I'm finding pretty long named confusing JSP file names. The first 3 character was the module name "qot" , that was one information i could understand from :-)

yes i tried . it is working . but it looks very odd in the URL and i did not see any site that contains the _(underscore )
in their file name.
But still i am not sure whether i use it or not . Because I have less idea about naming convention of jsp apges

Adobe Interactive Forms - Standards & Naming Conventions

Does anyone know where I can locate any documentation pertaining to recommended standards and naming conventions for interactive forms within the SAP NetWeaver '04 platform?

Hi David,
I suggest you start here: https://www.sdn.sap.com/sdn/developerareas/was.sdn?page=AdobeForms.htm. This is where we have collected background information, demos, eLearning materials, and links to the standard documentation for the integrated forms solution. We work together with Adobe on the content of this site.
In due course, we will provide more tips & tricks and best practices.

Question about Best Practices - Redwood Landscape/Object Naming Conventions

Having reviewed documentation and posts, I find that there is not that much information available in regards to best practices for the Redwood Scheduler in a SAP environment. We are running the free version.
1) The job scheduling for SAP reference book (SAP Press) recommends multiple Redwood installations and using export/import to move jobs and other redwood objects from say DEV->QAS->PROD. Presentations from the help.sap.com Web Site show the Redwood Scheduler linked to Solution Manager and handling job submissions for DEV-QAS-PROD. Point and Shoot (just be careful where you aim!) functionality is described as an advantage for the product. There is a SAP note (#895253) on making Redwood highly available. I am open to comments inputs and suggestions on this issue based on SAP client experiences.
2) Related to 1), I have not seen much documentation on Redwood object naming conventions. I am interested in hearing how SAP clients have dealt with Redwood object naming (i.e. applications, job streams, scripts, events, locks). To date, I have seen in a presentation where customer objects are named starting with Z_. I like to include the object type in the name (e.g. EVT - Event, CHN - Job Chain, SCR - Script, LCK - Lock) keeping in mind the character length limitation of 30 characters. I also have an associated issue with Event naming given that we have 4 environments (DEV, QA, Staging, PROD). Assuming that we are not about to have one installation per environment, then we need to include the environment in the event name. The downside here is that we lose transportability for the job stream. We need to modify the job chain to wait for a different event name when running in a different environment. Comments?

Hi Paul,
As suggested in book u2018job scheduling for SAP from SAPu2019 press it is better to have multiple instances of Cronacle version (at least 2 u2013 one for development & quality and other separate one for production. This will have no confusion).
Regarding transporting / replicating of the object definitions - it is really easy to import and export the objects like Events, Job Chain, Script, Locks etc. Also it is very easy and less time consuming to create a fresh in each system. Only complicated job chains creation can be time consuming.
In normal cases the testing for background jobs mostly happens only in SAP quality instance and then the final scheduling in production. So it is very much possible to just export the verified script / job chain form Cronacle quality instance and import the same in Cronacle production instance (use of Cronacle shell is really recommended for fast processing)
Regarding OSS note 895253 u2013 yes it is highly recommended to keep your central repository, processing server and licencing information on highly available clustered environment. This is very much required as Redwood Cronacle acts as central job scheduler in your SAP landscape (with OEM version).
As you have confirmed, you are using OEM and hence you have only one process server.
Regarding the conventions for names, it is recommended to create a centrally accessible naming convention document and then follow it. For example in my company we are using the naming convention for the jobs as Z_AAU_MM_ZCHGSTA2_AU01_LSV where A is for APAC region, AU is for Australia (country), MM is for Materials management and then ZCHGSTA2_AU01_LSV is the free text as provided by batch job requester.
For other Redwood Cronacle specific objects also you can derive naming conventions based on SAP instances like if you want all the related scripts / job chains to be stored in one application, its name can be APPL_<logical name of the instance>.
So in a nutshell, it is highly recommend
Also the integration of SAP solution manager with redwood is to receive monitoring and alerting data and to pass the Redwood Cronacle information to SAP SOL MAN to create single point of control. You can find information on the purpose of XAL and XMW interfaces in Cronacle help (F1).
Hope this answers your queries. Please write if you need some more information / help in this regard.
Best regards,
Vithal

Naming conventions in EP

Hi all,
we are currently in the process of preparing for Buisness Package certification in Enterprise Portal.
While going through the Test Plan provided by SAP describing the guidelines and the naming conventions.
Is there any thing that should be especially noted when we do the naming of EP folders and other EP components.Any help on these naming conventions is welcome.
Regards
Rohit.

Hi Rohit,
Please refer to the Vendor Structuring Guide (a.k.a. How to Certify Portal Content document) for more information on the naming conventions. You should have received this together with the test plan.
If you cannot locate this document, please contact your assigned integration consultant and/or complete and return the project registration document as much as you can so that the consultant can get back to you with any corrections that might be necessary.
Regards,
Mustafa.

Naming Conventions for Workflow

Hello,
does anybody have a document for Naming Conventions for Workflow.
I found nothing the last hour.
Thanks in advance for any help ...
Stefanie

Hi,
I am sending you naming convention which we followed in our project.
Workflow Template & Standard Task:
SAP/R3 Limitations:
Workflow Template & Standard Task names are limited to 12 bytes.
Standard:
Bytes 1-3 of the Workflow Template & Standard Task (see following table) are intended to give an overview of general information regarding the Workflow Template & Standard Task.
Characters 4-12 of the name should be chosen to impart some idea of the Workflow Template & Standard Tasku2019s use and/or contents. (The portion of the Workflow Template & Standard Task name that forms the unique identifier may, or may not, contain underscores characters to enhance Workflow Template & Standard Task name readability.)
Position     Description     Sample Values     Sample Meanings
1     Table system life     Z/Y                Permanent/Temporary
2     Application Type     *                    See Application Designators (Appendix B)
3     OPCO/Region     *                    See OpCo Initial Chart (Appendix A)
4-12     Unique identifier     text                     Unique identifier; may include underscores
Example: ZS7_IDEL9 (I:-Inbound, DEL: - OILDEL 9:- Original)
Business Object:
SAP/R3 Limitations:
Business Object names are limited to 10 bytes.
Standard:
Bytes 1-3 of the Business Object (see following table) are intended to give an overview of general information regarding the Business Object.
Characters 4-12 of the name should be chosen to impart some idea of the Business Objectu2019s use and/or contents. (The portion of the Business Object name that forms the unique identifier may, or may not, contain underscores characters to enhance Business Object name readability.)
Position     Description     Sample Values     Sample Meanings
1     Table system life     Z
Y     Permanent
Temporary
2     Application Type     *     See Application Designators (Appendix B)
3     OPCO/Region     *     See OpCo Initial Chart (Appendix A)
4-12     Unique identifier     text     Unique identifier; may include underscores
Example: ZS7_OILDEL (Business Object for OILDEL Message Type)
Methods
Method names should begin with a verb:
Examples: GET_STATUS, CREATE_ORDER, DETERMINE_PRICE
For Parameters:
IMPORTING parameters     IM_<parameter name>
EXPORTING parameters     EX_<parameter name>
CHANGING parameters     CH_<parameter name>
RESULT     RE_<result>
Events
Event names should have the form
<noun>_<participle>:
Examples: BUTTON_PUSHED, COMPANY_CODE_CHANGED, BUSINESS_PARTNER_PRINTED
Note: There is no specific naming convention for Container Variables in workflow & for Key Fields & Attributes in Business Object. These variables name should be chosen to impart some idea of the variablesu2019 use and/or contents.
Appendix A
ABAP Programming Standards: OpCo/Region Initial Chart
Old #     Company Name                               Proposed #     Accounting Location
98     Common                                                     A              San Ramon
95     FSC                                                     B              San Ramon
80     Chevron Chemical Company                      C              San Ramon
89     Chevron USA-Downstream & General     D     Walnut Creek
75     Chevron Real Estate Management      E     San Francisco
76     Chevron Information Technology Company      F     San Ramon
77     Gulf Oil Great Britain                                    G     London
85     Corporation (Acct. by Corp.)                    H     San Francisco
83     Chevron International Oil company              J     San Ramon
87     Chevron U. K. Limited                               K     England
86     Corporation (Acct. - Local Office)                    L     Various
96     P&M Coal & Mining Company                   M     Denver
94     Corporation (New York)                   N     New York
90     Chevron Pipeline Company                    P     San Ramon
79     Chevron Canada Resources, Ltd.              R      Calgary
92     Chevron Shipping Company                  S                     San Francisco
81     Chevron Petroleum & Tech Co.                  T                     Houston
91     Chevron USA Upstream                  U                     Concord
78     Chevron Canada, Ltd.                              V                     Vancouver
93     CUSA Warren Petroleum                  W     Tulsa
84     Chevron Overseas Petroleum, Inc.            X                     San Ramon
88     Chevron Research & Tech. Company        Y      Richmond
-     Corp. GLX Common validations                   Z      San Ramon
-     PCA                                                   3                     San Ramon
-     Tax                                                   4                     San Ramon
-     Audit                                                   5                     San Ramon
-     Asia-Pacific                                   6                     Global
-     Africa                                                   7                     Global
-     Latin America                                   8                     Global
Appendix B
ABAP Programming Standards: Application Designators
A     Assets Accounting
C     PPC
D     DASS (control station)
E     RIVA/IS-Oil
F     Financial Accounting (incl. Joint Venture)
G     General Ledger
H     Human Resources Planning
I     Plant Maintenance
J     Publishing
K     Cost Accounting
L     Inventory Management
M     Materials Management
N     Hospital
O     unassigned
P     Human Resources
Q     QSS (Quality assurance)
R     PRA (Prod & Revenue Acctg)
S     Basis
T     Projects
U     Enterprise Data Model
V     Sales
W     MMS (Merchandise mgt. System)
X     unassigned
Y     Customer head office
Z     Customer branch
<inappropriate content removed by moderator>
Thanks
Yogesh Sharma
Edited by: Mike Pokraka on Jul 2, 2008 10:34 AM

Naming convention thru Code Inspector

Hi Friends,
Can we use code inspector to check the naming conventions?.
Thanks in advance.
Regards,
saravanan.D

Hi,
The code inspector can of course be used to check for adherence of the ABAP code to your naming conventions.
You can find information about Code inspector <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://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">at this link</a>.
Regards,
Anand Mandalika.

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

Naming Convention (Naming Rule) for CAF GP

Hi, all.
Is there any naming convention for CAF GP?
For its process, action, callable object so and so.
Web Dynpro for Java has very good naming convention like the following.
http://help.sap.com/saphelp_nw2004s/helpdata/en/e4/d7fb402eb5f76fe10000000a1550b0/frameset.htm
Could someone provide the information?
Best Regards.

Hi Sejoon,
Sometimes I see GP provided coding examples and it seems that GP does not have some specific naming convention. It's clear that they use sdandart java naming convention. So, you can use it too.
Best regards,
Aliaksei

Standard Naming Conventions in XI

Hello,
Pls send pdfs/links for Naming Conventions in XI
Regards

Hi Henry,
These r the naming conventions to be followed in XI :
1) For Software Component, the naming convention should be :
   SAP_<SID>
where <SID> is the system ID if the applicable system
2) For Software Component Version, the naming convention should be :
    X.X
which shows the applicable version as of this date. Eg. SAP_ECC is at version 5.0
3) For Namespace the naming convention should be :
http://ERPGenie.COM/xi/<SCENARIO>/<SID>
where scenario refers to the interface being developed for and <SID> is the component where that object has relevance.
Eg. http://ERPGenie.COM/xi/OrderOutput/ECC will contain all the objects relevant to the Order Output scenario in the ECC system.
4) In Interface Objects ,
a) Message Interface should have the following naming convention :
MI_<meaningful name>_<IN/OUT/AB>
where:
IN = Inbound
OUT = Outbound
AB = Abstract (For BPM)
Remember to evaluate the IN and OUT based on the point of view from the source system to the target system. Eg. If we send an XML message from xEXTERNAL to an IDoc in ECC, then the XML Message is an OUT and the ECC is an IN interface.
b) Message Type should have the following naming convention :
MT_<meaningful name>
c) Fault Message Type should have the following naming convention :
FMT_<meaningful name>
d) Data Type should have the following naming convention :
DT_<meaningful name>
e) Data Type Enhancements should have the following naming convention :
DTE_<meaningful name>
f) Context Object should have the following naming convention :
CO_<meaningful name>
g) External Definition should have the following naming convention :
ED_<meaningful name>
5) In Mapping Objects,
a) Message Mapping should have the following naming convention :
MM_<meaningful name>_<source type>_<target type>
Eg. MM_ORDERSCENARIO_ORDERS05_OrderXML
b) Interface Mapping should have the following naming convention :
IM__<meaningful name>_<source type>_<target type>
Eg. IM_ORDERSCENARIO_ORDERS05_OrderXML
c) Mapping Templates should have the following naming convention :
MT__<meaningful name>_<source type>_<target type>
d) Imported Archives should have the following naming convention :
IA_<meaningful name>
6) In Services
a) Business Systems should have the following naming convention :
SAP<SID>
Where <SID> is the relevant system ID number
E.g.. SAPECC, SAPCRM, SAP46C
b) Business Services should have the following naming convention :
SRV_<XXXXXX>
Where XXXXXX is up to 6 characters to describe the type of service.
E.g. SRV_MAIL, SRV_FTP, SRV_SEEBRG
7) In Adapter Objects,
a) Adapter Meta Data should have the following naming convention :
AM_<meaningful name>
b) Communication Channel should have the following naming convention :
CC_<meaningful name>_<sender/receiver>
            E.g. CC_MAIL_SENDER
8) In Integration Objects,
a) Integration Process should have the following naming convention :
IP_<meaningful name> (Keep to 10 or less characters ALL CAPS)
            Store these in namespace http://ERPGenie.COM/xi/<SCENARIO>
b) Actions should have the following naming convention :
<meaningful name>
Use Send_ or Receive_ to denote the sending or receiving of messages
Store these in namespace http://ERPGenie.COM/xi/<SCENARIO>/<SID> where <SID> is system where the action is to be performed.
c) Integration Scenarios should have the following naming convention :
IS_<meaningful name> (Keep to 10 or less characters ALL CAPS)
The following web-sites may be helpful for complete naming standards in XI :
http://tsr.strain.at/space/SAP+XI(This web-site gives all detailed information about XI)
http://www.erpgenie.com/sap/netweaver/xi/namingconventions.htm
*********Please reward points if u find this useful.
cheers,
gyanaraj

Powershell naming conventions for functions

There is a lot of information about the Verb-Noun naming convention for cmdlets. I am trying to understand what the recommendation / best practice is for naming functions. Personally, I like the idea that if I see Verb-Noun, I know it's
a cmdlet, and it supports the standard parameters. However, I'm not sure I see the entire picture.
Thanks!

There are as many opinions around this as there are people. TechNet has some good recommendations for naming conventions, but you should adopt whatever standard you are most comfortable with. In the end it doesn't much matter which convention
you adopt, as long as you stick to it and keep it consistent. Most corporate code doesn't get outside or shared with other businesses and vendors, so the whole purpose of standards and conventions is to keep things straight for YOUR people. As
long as you consistently apply your conventions, it doesn't matter.
I trust that answers your question...
Thanks
C
|
RSS |
http://crayveon.com/blog |
SharePoint Scripts | Twitter |
Google+ | LinkedIn |
Facebook | Quix Utilities for SharePoint

Information Steward naming conventions

Similar Messages

Maybe you are looking for