Naming conventions pdf

Can someone please send me the naming conventions pdf found on the following link to my email please? I am not able to download it .
https://websmp101.sap-ag.de/~sapdownload/011000358700004455192006E/NameConventions.pdf
Thank you

Sorry can you send it to
[email protected]
thank you

Similar Messages

  • AppleScript To Save Messages As PDFs With Specific Naming Convention

    I am looking for an Applescript that:
    1: Prompts and allows the user to select one or more Apple Mail email messages from within Mail (10.4, 10.5, 10.6).
    2: Prompts and allows the user to select a save-to folder.
    3: For each message, saves it as a PDF file in the save-to folder, using the following naming convention for the PDF file:
    "YYYY-MM-DD HH.MM.SS Email From FIRSTNAME LASTNAME - SUBJECT",
    "YYYY-MM-DD HH.MM.SS Email To FIRSTNAME LASTNAME - SUBJECT",
    where in the email date-sent stamp (if I am the sender) or date-received stamp (if I am the recipient):
    YYYY = the year
    MM = the two-digit month
    DD = the two-digit day
    HH = the two-digit hour (in 24-hour time)
    MM = the two-digit minute
    SS = the two-digit second
    FIRSTNAME is the email sender's first name for email that I receive (or is the email recipient's first name for email that I send)
    LASTNAME is the email sender's last name for email that I receive (or is the email recipient's first name for email that I send)
    SUBJECT = the email's subject line
    For example: 2010-04-10 16.32.48 Email From Kris Ryan - Status Of Payroll Updates.pdf
    For example: 2010-04-10 16.33.55 Email To Sue Anderson - RE Status Of Payroll Updates.pdf (Colon omitted after "RE".)
    4: For each attachment to the message, saves it as a PDF file in the same directory using the naming convention:
    "YYYY-MM-DD HH.MM.SS Email From FIRSTNAME LASTNAME Z Attachment - NUMBER - FILENAME",
    where:
    YYYY-MM-DD HH.MM.SS Email From FIRSTNAME LASTNAME = as above
    NUMBER = an integer representing the attachment number (1, 2, ...) sorted according to filename alphabetical order
    FILENAME = the name of the file attached to the email, including its extension (.docx, .xlsx, etc.)
    The letter "Z" sorts the attachment PDFs after its respective parent email in the directory.
    For example: 2010-04-10 16.32.48 Email From Kris Ryan Z Attachment - 1 - List Of Suggestions To Moore.doc.pdf
    For example: 2010-04-10 16.32.48 Email From Kris Ryan Z Attachment - 2 - Proposed Salary Adjustments.xls.pdf
    For example: 2010-04-10 16.32.48 Email From Kris Ryan Z Attachment - 3 - Salary History.pps.pdf
    Note: The email attachment may consist of a PDF or MS Office file (Word, Excel, Power Point); however, a smart implementation will be able to handle any attachment kind. If the attachment is a PDF file, then save it "as is" using the stipulated naming convention, without passing it through Distiller.
    Thank you.
    Kurt Todoroff

    Well, that's quite a spec sheet.
    Here's a start, you can easily edit the script to get what you need:
    <pre style="
    font-family: Monaco, 'Courier New', Courier, monospace;
    font-size: 10px;
    font-weight: normal;
    margin: 0px;
    padding: 5px;
    border: 1px solid #000000;
    width: 720px; height: 340px;
    color: #000000;
    background-color: #E6E6EE;
    overflow: auto;"
    title="this text can be pasted into the AppleScript Editor">
    Set a Mail Rule to Save Message and Attachment to Desktop.
    To save attachments to another another folder on the desktop (i.e. Attachments) create the folder and then
    change tell application "Finder" to set pathToAttachments to (path to desktop folder as string) & "Attachments:"
    using terms from application "Mail"
    on perform mail action with messages theMessages
    tell application "Finder" to set ptd to (path to desktop folder) as string
    tell application "Finder" to set pathToAttachments to (path to desktop folder) as string
    tell application "Mail"
    repeat with theMessage in theMessages
    set d_recd to date received of theMessage as string
    set d_recd to ReplaceText(d_recd, ":", " ") of me
    set d_recd to ReplaceText(d_recd, ",", " ") of me
    set theText to content of theMessage
    if theMessage's mail attachments is not {} then
    repeat with theAttachment in theMessage's mail attachments
    set theFileName to pathToAttachments & (theMessage's subject) & " (Attachment From " & (theMessage's sender) & " Sent " & d_recd & ")" & space & theAttachment's name
    try
    save theAttachment in theFileName
    on error errnum
    end try
    end repeat
    end if
    set theFile to ptd & (theMessage's subject) & " (From " & (theMessage's sender) & " Sent " & d_recd & ")" & ".txt"
    set theFileID to open for access file theFile with write permission
    write theText to theFileID
    close access theFileID
    end repeat
    end tell
    end perform mail action with messages
    end using terms from
    on ReplaceText(theString, fString, rString)
    set current_Delimiters to text item delimiters of AppleScript
    set AppleScript's text item delimiters to fString
    set sList to every text item of theString
    set AppleScript's text item delimiters to rString
    set newString to sList as string
    set AppleScript's text item delimiters to current_Delimiters
    return newString
    end ReplaceText</pre>

  • What are the best practices in naming a PDF

    Using underscores, spaces, dashes, commas, etc. What is the best way to name a PDF so it can be opened on all browsers and all platforms?

    Hi Gina D 3333,
    Best-practice file-naming conventions for PDF files are the same as for any other file. I found this article on Apple's website that contains some useful pointers to consider when you're naming files that will be used on multiple platforms: OS X: Cross-platform filename best practices and conventions
    I hope this helps!
    Best,
    Sara

  • 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

  • Variable naming conventions

    Hi all,
    I come from a mostly JAVA background. Big emphasis in that arena on encapsulation and modularization of code to help facilitate ease of maintenance and reuse...in theory I sometimes struggle with variable naming conventions within my ABAP code because I'm not all together certain there are any. In C or C++ I might use a derivation of Hungarian notation to name varaibles...and in JAVA I might observe certain object oriented rules regarding varaible naming...I find myself using a combination of those two protocols in my ABAP code. Does anyone have any suggestions for how I might name global and lcoal variables within my code?
    regards,
    Mat

    Hi,
    Please check this links perhaps they may help.
    http://help.sap.com/saphelp_nw04/helpdata/en/92/c2b084bc1d11d2958700a0c94260a5/content.htm
    https://websmp101.sap-ag.de/~sapdownload/011000358700004455192006E/NameConventions.pdf
    http://help.sap.com/saphelp_nw04/helpdata/en/2a/6b0b1f547a11d189600000e829fbbd/content.htm
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/011ccf90-0201-0010-92a7-b319adf89b73
    http://web.mit.edu/sapr3/dev/newdevstand.html
    Regards,
    Ferry Lianto

  • Oracle BPEL standard, best practice and naming convention

    Hi, folks,
    Is there any standard or best practice associated with Oracle BPEL, regarding development, performace, what to avoid, etc? And is there any naming convention for the process, variable partner link name, etc? Similar to naming convention in writing Java code?
    Thanks
    John

    Hi,
    Here is the best practice guide:
    http://download.oracle.com/technology/tech/soa/soa_best_practices_1013x_drop3.pdf
    Thanks & Regards,
    Dharmendra
    http://soa-howto.blogspot.com

  • EP Naming Conventions and Best Practices

    Hi all
    Please provide me EP Naming Conventions and Best Practices documents
    Thanks
    Vijay

    Hi Daya,
    For SAP Best Practices for Portal, read thru these documents :-
    [SAP Best Practices for Portal - doc 1 |http://help.sap.com/bp_epv170/EP_US/HTML/Portals_intro.htm]
    [SAP Best Practices for EP |http://www.sap.com/services/pdf/BWP_SAP_Best_Practices_for_Enterprise_Portals.pdf]
    And for Naming Conventions in EP, please go through these two links:-
    [Naming Conventions in EP|naming standards;
    [EP Naming Conventions |https://websmp210.sap-ag.de/~sapidb/011000358700005875762004E]
    Hope this helps,
    Regards,
    Shailesh
    Edited by: Shailesh Kumar Nagar on May 30, 2008 4:09 PM

  • Naming conventions included for linked files?

    Perhaps a simple question but... if a file is only going to serve as a downloadable link (save as) do the standard naming conventions still apply? (lowercase, no spaces)  the files i am working with are dwg, pdf, zmt, jpeg, png...  my assumption is yes but thought i would ask.
    thank you in advance,

    All lowercase is nice, and easier since URLs are case-sensitive. Spaces are always best avoided. Completely. Some systems handle them, but there are no guarantees. Underscores (_) are a good alternative.

  • 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

  • Naming convention of Org Units, Position

    What is the naming convention used for Org Units, Positions, Jobs and other OM objects. Pls send document if any of you have.
    Max points promised!

    Namming conventions are made based on the company strategry. That means it varies from one organisation to another. I can find one convention  which is availabe in net.
    http://www.jhu.edu/hopkinsone/Secure_Private/Library/Blueprint/HumanResources_Sect9_18.pdf#search=%22sap%20hr%20Org%20Units%20Jobs%20Positions%20naming%20conventions%22
    ~thomas

  • 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

  • Publication\Zip file naming convention

    Hi Folks,
    In XI3.1 when you schedule a Publication and select zip file package as format the documents inside the Publication get named like: "tempWebiArtifact35744728274_2.PDF" 
    Any idea why we have this unusual naming convention?
    Kind regards,
    John

    Developers of this feature think that is normal to have files named like "blablablah", but customers dont think so.

  • What are the naming convention rules for BAPI and types

    what are the naming convention rules for BAPI
    points will be rewarded,
    thank you,
    Jagrut BharatKumar Shukla

    Hi,
    plz go through the following links....
    Business application Prograaming Interface is nothing but the Method of a Business object.
    BAPI-step by step
    http://www.sapgenie.com/abap/bapi/example.htm
    list of all bapis
    http://www.planetsap.com/LIST_ALL_BAPIs.htm
    for BAPI's
    http://www.sappoint.com/abap/bapiintro.pdf
    http://www.sappoint.com/abap/bapiprg.pdf
    http://www.sappoint.com/abap/bapiactx.pdf
    http://www.sappoint.com/abap/bapilst.pdf
    http://www.sappoint.com/abap/bapiexer.pdf
    http://service.sap.com/ale
    http://service.sap.com/bapi
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE8/BCFESDE8.pdf
    http://www.planetsap.com/Bapi_main_page.htm
    http://www.topxml.com/sap/sap_idoc_xml.asp
    http://www.sapdevelopment.co.uk/
    http://www.sapdevelopment.co.uk/java/jco/bapi_jco.pdf
    Also refer to the following links..
    www.sappoint.com/abap/bapiintro.pdf
    www.sap-img.com/bapi.htm
    www.sap-img.com/abap/bapi-conventions.htm
    www.planetsap.com/Bapi_main_page.htm
    www.sapgenie.com/abap/bapi/index.htm
    Checkout !!
    http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
    http://techrepublic.com.com/5100-6329-1051160.html#
    http://www.sap-img.com/bapi.htm
    http://www.sap-img.com/abap/bapi-conventions.htm
    http://www.sappoint.com/abap/bapiintro.pdf
    u can check the below the material also
    what is BAPI?
    BAPI stands for Business API(Application Program Interface).
    I have answered this question before..
    A BAPI is remotely enabled function module ie it can be invoked from remote programs like standalone JAVA programs, web interface etc..
    You can make your function module remotely enabled in attributes of Function module but
    A BAPI are standard SAP function modules provided by SAP for remote access. Also they are part of Businees Objest Repository(BOR).
    BAPI are RFC enabled function modules. the difference between RFc and BAPI are business objects. You create business objects and those are then registered in your BOR (Business Object Repository) which can be accessed outside the SAP system by using some other applications (Non-SAP) such as VB or JAVA. in this case u only specify the business object and its method from external system in BAPI there is no direct system call. while RFC are direct system call Some BAPIs provide basic functions and can be used for most SAP business object types. These BAPIs should be implemented the same for all business object types. Standardized BAPIs are easier to use and prevent users having to deal with a number of different BAPIs. Whenever possible, a standardized BAPI must be used in preference to an individual BAPI.
    The following standardized BAPIs are provided:
    Reading instances of SAP business objects
    GetList ( ) With the BAPI GetList you can select a range of object key values, for example, company codes and material numbers.
    The BAPI GetList() is a class method.
    GetDetail() With the BAPI GetDetail() the details of an instance of a business object type are retrieved and returned to the calling program. The instance is identified via its key. The BAPI GetDetail() is an instance method. BAPIs that can create, change or delete instances of a business object type
    The following BAPIs of the same object type have to be programmed so that they can be called several times within one transaction. For example, if, after sales order 1 has been created, a second sales order 2 is created in the same transaction, the second BAPI call must not affect the consistency of the sales order 2. After completing the transaction with a COMMIT WORK, both the orders are saved consistently in the database.
    Create( ) and CreateFromData! ( )
    The BAPIs Create() and CreateFromData() create an instance of an SAP business object type, for example, a purchase order. These BAPIs are class methods.
    Change( )
    The BAPI Change() changes an existing instance of an SAP business object type, for example, a purchase order. The BAPI Change () is an instance method.
    Delete( ) and Undelete( ) The BAPI Delete() deletes an instance of an SAP business object type from the database or sets a deletion flag.
    The BAPI Undelete() removes a deletion flag. These BAPIs are instance methods.
    Cancel ( ) Unlike the BAPI Delete(), the BAPI Cancel() cancels an instance of a business object type. The instance to be cancelled remains in the database and an additional instance is created and this is the one that is actually canceled. The Cancel() BAPI is an instance method.
    Add<subobject> ( ) and Remove<subobject> ( ) The BAPI Add<subobject> adds a subobject to an existing object inst! ance and the BAPI and Remove<subobject> removes a subobject from an object instance. These BAPIs are instance methods.
    http://help.sap.com/saphelp_nw2004s/helpdata/en/7e/5e114a4a1611d1894c0000e829fbbd/frameset.htm
    http://www.sapgenie.com/abap/bapi/example.htm
    http://help.sap.com/saphelp_46c/helpdata/en/9b/417f07ee2211d1ad14080009b0fb56/frameset.htm
    http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
    http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
    http://techrepublic.com.com/5100-6329-1051160.html#
    http://www.sap-img.com/bapi.htm
    http://www.sap-img.com/abap/bapi-conventions.htm
    http://www.sappoint.com/abap/bapiintro.pdf
    http://www.sapgenie.com/abap/bapi/example.htm
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE8/BCFESDE8.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
    http://techrepublic.com.com/5100-6329-1051160.html#
    http://www.sap-img.com/bapi.htm
    http://www.sap-img.com/abap/bapi-conventions.htm
    http://www.sappoint.com/abap/bapiintro.pdf
    BAPI
    http://help.sap.com/saphelp_46c/helpdata/en/9b/417f07ee2211d1ad14080009b0fb56/frameset.htm
    http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
    Checkout !!
    http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
    http://techrepublic.com.com/5100-6329-1051160.html#
    http://www.sap-img.com/bapi.htm
    http://www.sap-img.com/abap/bapi-conventions.htm
    http://www.sappoint.com/abap/bapiintro.pdf
    http://www.sapgenie.com/abap/bapi/example.htm
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE8/BCFESDE8.pdf
    List of all BAPIs
    http://www.planetsap.com/LIST_ALL_BAPIs.htm
    http://www.sappoint.com/abap/bapiintro.pdf
    http://www.sappoint.com/abap/bapiprg.pdf
    http://www.sappoint.com/abap/bapiactx.pdf
    http://www.sappoint.com/abap/bapilst.pdf
    http://www.sappoint.com/abap/bapiexer.pdf
    http://service.sap.com/ale
    http://service.sap.com/bapi
    http://www.geocities.com/mpioud/Abap_programs.html
    http://www.sapdevelopment.co.uk/reporting/reportinghome.htm
    ***do reward if usefull
    vijay

  • SAP Recomended Naming Convention?

    Hi all,
    I've just started picking up XI not too far back. Now having to recently gone into my second XI project, i'm starting to wonder if there's a naming convention recomended by SAP?
    if not, can everyone share their ideas/experiences in XI development objects naming scheme?
    many thanks fellow integrators.
    cheers,
    Ryan.

    Here the standard <a href="https://websmp102.sap-ag.de/~sapdownload/011000358700004455192006E/NameConventions.pdf">SAP XI naming convention guide</a>: I suggest to read it with attention because it is helpful to understand the software organization philosophy under XI developments.
    Maybe you can need the <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/2791db90-0201-0010-dea7-ec869d783f9c">ASAP Methodlogy for XI</a>
    Regards,
    Sandro

  • XI naming conventions

    Hello,
    can anybody send me a naming conventions document that could be used for  XI development?
    my email id is [email protected]
    Thanks a ton,
    Arjun.

    Arjun,
    Go through this ASAP methodology where you will find with explanations:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/2791db90-0201-0010-dea7-ec869d783f9c
    https://websmp207.sap-ag.de/~sapidb/011000358700004455192006E/NameConventions.pdf
    Please go through this urls where you can find some documentation of your query:
    /people/michal.krawczyk2/blog/2005/04/09/xi--saps-document-templates
    /people/thorsten.nordholmsbirk/blog/2006/07/25/structuring-integration-repository-content--part-1-software-component-versions
    /people/alwin.vandeput2/blog/2006/06/07/d-xie-soap-part-4-xi-software-component-architecture-for-point-to-point-scenarios
    /people/sap.india5/blog/2005/11/03/xi-software-logistics-1-sld-preparation
    Also go thru this blog from Michal- go to Documents Section-
    /people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
    Go through this threads also:
    Naming convention in a real time XI project
    Building XI
    Re: XI Documentation
    ---Satish

Maybe you are looking for