Namespace Reservation in SLD ??

I have the JDI sp13 and I'm trying to configure it.
I'm arrived at point that the Installation Guide speas about "Registering the Reserved Prefix for the Name Reservation Service"
and I'm dubious about the meaning of this stuff.
It's really necessary ?
I'm not going to use the prefix "sap.com" or my developents so why they should be overvritten ?
Regards

Hi,
thank you for this thread!
Coming from
[Name Reservation Issue|Name reservation issue]
[Technical Implications|Name Prefix Reservation - Technical Implications]
I am missing some detailed technical examples according to the interrelationship between
the procedure given by the SAP Marketplace Link
[Request Namespaces for Development|http://service.sap.com/namespaces] and the SLD
name space procedure.
Namespace / Description are fields related to ABAP Workbench, I think so.
But what is typically given to the field Name Server? The Namespace Prefix? Something like
rig.com/mydc as stated in the document
How to ... Get started with the SAP Netweaver Development Infrastructure v1.00 - July 2006 ??
What is effected by activating the option: Object Generators?
Is that all  a one step procedure, or have I to give as many requests as I want to use the different
possibilities in the namespace reservation of the SLD?
I am in need of an explanation of that matter. Thank you.
Regards
Christian

Similar Messages

  • Activation of the activity fails u0096 no source files in the active workspace

    Dear All,
    I’m working on a NWDI installation since last month. The NWDI server (NW2004s) has been installed and configured with the following parameters:
    Some Details:
    -     Java Stack on SPS 12
    -     No complete Developer Workplace, we only use the Studio (SPS 12)
    -     OS: WIN 2003
    -     DB: Oracle 10g
    -     SDK: 2 SDK, Standard Edition x64 1.4.2_15
    Installation Usages Types: DI, AS Java, EP Core, EP (EP for the Visual Composer)
    Performed configuration steps:
    -     adaptation of VM parameter in the Visual Admin
    -     patched the NWDI Server and the Studio from SPS 9 to support package stack 12 + available single patches
    -     run the template installer => NWA with type “DI Allinone – run all post installation Steps for DI, CBS, CMS, DTR”
    -     Oracle Parameters changed, User and Authorizations created and assigned (UME, J2EE Security roles, DTR => ACL List), SLD (Creation of a new Landscape), Configuration of the CBS with the VA
    -     Configuration of the Studio (SAP J2EE Engine (fill in the NWDI engine), Proxy Settings, Development Configuration Pool)
    Development Steps for an example:
    -     Creation of a new software product (SLD)
    -     Namespace reservation on SLD => Application Context Root, Development Component Name
    -     Created a Domain and a Track on CMS
    -     Attached all Software components to the track (my own dc, SAP-JEE, SAP_Buildt, SAP_JTechs)
    -     Check-In the Software Components on Transport studio => CMS
    -     Moved the development configuration into Studio
    -     Created a ear- and a web-project => Display a JSP File (It’s the same example like in the SAP Course TADM10)
    -     Check-in the activity under “Open activities” => Activate
    My problem appears during the check-in phase in the studio. I was able to check-In the source files in to the inactive Workspace on the DTR, but the activation of the activity fails. (I thought that the build process runs automatically after the activation - also the movement from the source files from the inactive to the active workspace?).
    I received no error message, but I can’t find any source files in active workspace. The activity seems to be pending. I locate the request in the CBS, the request state is “failed” regarding the request type “activate”.
    At the moment there is no separate runtime system assigned to the NWDI System.
    Questions:
    1.     Have I forgotten an important configuration step?
    2.     Can I use the NWDI Server also as a runtime environment (DEV System)?
    Please let me know if somebody has an idea.
    Thanks.
    Christoph

    Hello Michael,
    thanks a lot for your answer.
    I found the following error messages in the <b>request log</b>:
    <i>Calculate all combinations of components and variants to be built...
         "xxxtest.com/math/calc/webdc01" variant "default"
              "xxxtest.com/math/calc/webdc01" variant "default" cannot be built. Activation will fail.
              INVALID dependency is declared to public part: default.
              [DC 247 variant "default"][SC 65 "xxxtest.com_TASCHENRECHNER_1"] using [PP default of DC 6 at Build-Time Dependency]
         "xxxtest.com/math/calc/eardc03" variant "default"
              "xxxtest.com/math/calc/eardc03" variant "default" cannot be built. Activation will fail.
              The required Build Plugin "sap.com/tc/bi/bp/enterpriseApplication/enterpriseApplication" IS UNKNOWN. None of the compatments contains a suitable plugin for this component.
              [DC 248 variant "default"][SC 65 "sanofitest.com_TASCHENRECHNER_1"] using [BP sap.com/tc/bi/bp/enterpriseApplication/enterpriseApplication]
    Prepare build environment in the file system... started at 2007-09-04 06:13:54.316 GMT
    Prepare build environment in the file system... finished at 2007-09-04 06:13:54.316 GMT and took 0 ms
    ===== Pre-Processing =====  finished at 2007-09-04 06:13:54.332 GMT and took 406 ms
    Change request state from PROCESSING to FAILED
    ERROR! The following problem(s) occurred  during request processing:
    ERROR! The following error occurred during request processing:Activation failed due to component "xxxtest.com/math/calc/webdc01" variant "default". The component is BROKEN.
    ERROR! The following error occurred during request processing:Activation failed due to component "xxxtest.com/math/calc/eardc03" variant "default". The component is BROKEN.
    REQUEST PROCESSING finished at 2007-09-04 06:13:54.332 GMT and took 422 ms</i>
    The <b>Build Log</b> was empty.
    Thank you in advance.
    Best regards
    Christoph

  • Namespace is not shown in MWDS

    Hi Experts,
    I have created a namespace in the sld in the following manner
    In SLD, Name Reservation--> Name Prefixes, i have provided  Name Category as "Development Component Name " and on clicking New Name Prefix i have created a new name space.
    But this does'nt get  in my NWDS, When i do Create New DC... in my SC , the vendor remains editable and the drop down does'nt show anything.
    I have updated by CMS, and i have restarted my server. No Luck...
    What should be done more?
    I have already created some DC's in my SC and then i have configured the namespace... Will this be a problem?
    Before Creating my first DC in my SC should i define the namespace?
    Thanks,
    Gopal.

    Opps...
    At the last i was able to find the Names in NWDS.
    In the Name Server Configuration in DTR WebUI, i added the same Name Server Information once again in the second name server, and by doing this i was able to find my Namespace in the NWDS.
    Then i delete the first Name server in the Name Server Configuration and it  to be works fine now...
    I found the solution from this thread
    asynchronous reserve finally failed: missing name server configuration
    In which they say...
    The solution is to define your name server a second time with a slightly different URL. The first entry you already defined probably uses the fully qualified hostname, e.g. http://<host>.mycompany.com:50000/sld/cimom. Define the same name server again but without the domain and without the /sld/cimom path, e.g. http://<host>:50000/. Actually it should correspond to what's shown in the error message, e.g. "operation will be retried name reservation : name server=http://<host>:50000/,". When you click Save Configuration, the pending items in the queue will be processed.
    Though its working fine...  i would like to know what has happened in myscenario and how it was succesful now... What the  PENDING,_SUCCEEDED and *_FAILED  reperesent in the Name Reservation List and its importance?
    Thanks
    Gopal

  • B1DE namespace support

    I understand that from January 2009, SAP are only letting partners register for namespaces over 5 characters.  The installation of the B1DE does not support namespaces longer that 4 characters.  Does anyone know when the B1DE will be updated to support the longer namespaces?
    Many Thanks

    Hi Robert,
    There must be some misunderstanding:
    I just checked with the owner of the namespace reservation process @SAP - and he told me that there has bee NO change!
    Please note that you will never use the "/"es which you have to fill into the namespace field when requesting a namespace!
    I.e. the namespace you want would be: "ROB", but you have to fill in "/ROB/" into the field - just there - no where else!
    Regards,
    Frank

  • Object Server Name registration for SolMan

    I am installing SolMan 4.0, am now at the point where it asks question to configre the local SLD. It is asking for the ABAP namespace reserved in the marketplace. I do not know if my predecessors reserved said namesapce or noit. Does anyone know how to check that ( I looked at regiestered onbjects, 192 pages does not sound like a fun way to spend the day) quickly ?? If I do not have, how do I register that ??

    Hi,
    Follow this link <b>https://websmp207.sap-ag.de/inbox</b>, You will have a Tab <b>Keys & Requests</b>, there you will have <b>Development Namespaces</b>, just click on request Namespace and proceed to give the details.
    Hope this will solve your problem, feel free to revert back.
    --Ragu

  • Adds a ~home~ string in my project name

    Hi
    I am creating a new project in remote DC. It gives me 2 vendors to select from while creating project. One is sap.com and other is mycompany.com. If i select mycompany.com and create a project, it automatically adds a home string in my project name !!
    then if i try to rename it from package explorer it is not allowing me to do so.
    How can i remove/avoid this home string in my project name.
    Thanks.

    Hi
    Could you please review SAP notes 710315 and 876701?
    Can you please also review note 935245 ?
    According to the note one needs to add a new namespace in the SLD
    Database Namespace, then import from the default sld/active into the new
    namespace. From there one should be able to have a choice of vendor in
    Developer Studio when we wish to create a new DC.
    try these steps
    First, review some of the steps to create a name server and
    creat a name server on your SLD box through "New Technical System"
    and checked the "Name Server" box.
    Then add your officially reserved prefix in "Software Component
    Name" category of the SLD and add your reserved name in the same
    category in the "Name Reservation" area of the SLD.
    Afterwards, you should be able to create normally new Development Components
    (DC) in Developer Studio with an access to Web Dynpro components.

  • Can I use Non-standard XSD Data Types in my XSD; if so how?

    Please help if you can, this is a complex question, so bear with me.
    Also note that I am in Livecycle 8.2 ES (not ES2 or higher).
    I am working on creating XSD schemas to map to form objects.
    I have created one master schema document that is wired into multiple forms, and I have one separate schema for reusable form objects, that I refer to as a "common node".
    All of my individual form schemas are brought together in this one Master Schema via the use of include statements.
    EXAMPLE: This is like my Master Schema
    <?xml version="1.0" encoding="UTF-8"?>
    <!--W3C Schema written by Benjamin P. Lyons - Twin Technologies July 2010-->
    <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified" >
    <xs:include schemaLocation="./commonElementsNode.xsd" />
    <xs:include schemaLocation="./form1111.xsd" />
    <xs:include schemaLocation="./form2222.xsd" />
    <xs:include schemaLocation="./form3333.xsd" />
    <xs:element name="form">
    <xs:complexType>
      <xs:sequence>
       <xs:element ref="commonElementsNode" />
       <xs:element ref="form1111" />
       <xs:element ref="form2222" />
       <xs:element ref="form3333" />
      </xs:sequence>
    </xs:complexType>
    </xs:element>
    </xs:schema>
    This works fine.
    I can load this up in Designer in the Data View and everything appears in the Data View hierarchy correctly, with "form" as the top node.
    And as long as I use standard "xs:" data types - everything works great.  So if I go into LiveCycle Designer and I go to File --> Form Properties --> Preview --> Generate Preview Data and generate dummy XML data - it respects my XSD conventions.
    Now here is where the problem arises:
    In these schemas, I need to define the data types.
    The client I am working for needs me to use their data types.
    These data types are not standard xs: data types, like "xs:string" or "xs:date".
    Rather, the data types are ones that have been defined in other schemas and reserved to a namespace.
    For instance, rather than use xs:date I need to use something like:  "myns:DateType"
    This "myns:DateType" is defined as:
    <xs:complexType name="DateType">
      <xs:simpleContent>
       <xs:extension base="xs:date">
        <xs:attribute name="format" type="xs:string" use="optional">
         <xs:annotation>
          <xs:documentation xml:lang="en">
           <mydoc:Name>Date Format Text</mydoc:Name>
           <mydoc:Definition>The format of the date content</mydoc:Definition>
           <mydoc:PrimitiveType>string</mydoc:PrimitiveType>
          </xs:documentation>
         </xs:annotation>
        </xs:attribute>
       </xs:extension>
      </xs:simpleContent>
    </xs:complexType>
    Note that I have redacted this data type slightly and changed the namespace to protect the anonymity of my client, but we can assume that their data type is valid and currently in use with other systems.
    It conforms to W3 standards.
    Note also how this type is an enumeration of the base type "xs:date".
    This is defined in a schema called something like "MyCoreTypes.xsd"
    There is a namespace reservation in this file that looks something like this:
    <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified"
    xmlns:myns="http://clinetname.com/schemas/mycoretypes" >
    So there is a name space reservation there.
    In my aforementioned "Master Schema" file, I have an include statement that looks like this:
    <xs:include namespace="http://clinetname.com/schemas/mycoretypes" schemaLocation="./MyCoreTypes.xsd" />
    (let's assume that the schema is in the same folder, as the Master Schema, so we can use the "./" relative path.)
    Now the problems is that in all my forms, where I have a myns:DateType (e.g.:  in form1111, a "Date of Birth" element that looks like this: <xs:element name="OwnerBirthDt" type="myns:DateType"/> ) the XSD is not respected when the XML dummy data is generated in LiveCycle Designer implying that the XSD's data types are not being recognized properly.
    Has anyone had this problem before?
    Is there a solution?
    Is it even possible to use these kind of include or import references in LiveCycle to define a data type other that the standard "xs:" data types?
    Please let me know - it would be greatly appreciated.
    I am more than willing to clarify the question further if others are willing to help.
    Thanks -
    Ben Lyons

    prf.kishorekumar wrote:
    i came here with a hope that I would definitely get some help.
    pls.. some one reply1) You got some help. No where do I see thanks or acknowledgment for the information given.
    2) Please remember that people on the forum help others voluntarily, it's not their job.
    3) Google can often help you here if the forum can't. Using Google I found this interesting link:
    http://today.java.net/pub/a/today/2004/05/24/html-pt1.html
    It discusses the Swing HTML EditorKit as well as some other free HTML renderers.
    Edited by: petes1234 on Oct 24, 2007 7:29 PM

  • Creating a new DC in existing software component

    Hi,
    I am trying to create new DC in a software component that is custom developed.
    You can consider this as a totally build product and I want to extend the features implementing new DC.
    I am able to import the development components, and when I try to create a new DC in the configuraition pool, I am anot able to select the vendor from the Vendor dropdown.
    Can some one explain how to do this?
    Is it possible to keep the software component as is, but copy the same to a custom namespace (with new vendor name newvendor.com) and create a dc in it. This way i can change the sc as is and make changes on new SC.
    Please suggest.
    Thanks and regards,
    Chinnu

    Hi Satya,
    Thankyou for quick response.
    I did not create any namespace prefixes in SLD.
    Can you give me some clarity about name spaces? I am not very clear about the same.
    About the SC i am trying to modify, it is not SAP deliverd SC, instead created under custom vendor name and I am able to import the DCs and hopefully check in the same.
    Also, after seeing your reply, I checked for any available namespaces in SLD, and all I can see is sap.com/home etc., which are owned by SAP.
    Do I have to create a new namespace with the vendor name to create new DCs?
    Also, I get this error message when trying to create a new DC:
    Syntax of 'sap.com/home/NewDC' is not valid: Name suffix must be spelled lower case: home/NewDC
    Please suggest.
    Thanks and regards,
    Chinnu
    Edited by: Chinnu on Aug 14, 2009 10:06 AM

  • Error while check-in CAF DC on NWDI "No prefix found"

    Hi experts!
    I receive The following error when I try to Check-in a CAF DC on NWDS.
    FAILED: No prefix found for development component "mycompany/name/caf/dictionary"
    Appropriate development component prefix should be configured in SLD (Restart IDE after reconfiguring SLD).;
    I already tried the solutions described on this threads:
    Error while Check-in DC's on NWDI: No Prefix found for DC
    Problem With Checkin
    CAF check-in to NWDI error
    No prefix found for development component
    None solved to me.
    After I receive that error message I did:
    - Reserved the name prefix "mycompany/name/caf" on SLD on category "Development Component Name" with purpouse "Used everywhere"
    - Enabled the option "Enable this SLD as Name Server for NWDI"
    - Registered the NWDI on SLD as "Landscape" with type "NWDI Systems" and two systems, one with type CMS and another with type SLD.
    - Stop/Start SLD
    - Stop/Start NWDI
    - Update CMS on NWDI.
    The problem is still happening. The NWDI version is 7.1 SP4.
    Any ideas?

    Thanks Jan! It solved!
    I have already created another workspace after all the tests just to be sure that the problem wasn´t on NWDS.
    It solved to me when I removed the reservation on SLD and recreated.
    Thank you so much!
    Gabriela

  • Internal Error while creating new DC

    Hi Exerts,
    I am facing issue in creating a new DC in new SC.Intenral error occurred,which says that DC is already present.
    I have tried all options like deleting from DTR all .dcref files.Also I am creating for the first time but still the message says it is  already there.
    what could b ethe reason for it.It i svery critical and my deliverables are in trouble.
    I have searched SDN and no post helped me to resolve the issue.could you please suggest me to solve it .
    Thanks,
    Anupama

    Hi Anupama,
    Please consider Ervin's inputs, they are always fruitful.
    Note:
    If you have already deleted your DC properly with all the references.
    Then i would recomend you to check one more reference in the Name Reservations in SLD as below...
    1) http://<host>:<port>/sld
    2) Name Reservations >> Names >> choose "Development Component Name" in Name Category.
    Check whether your DC name is present in the table or not?
    If Yes, then you need to delete that entry.
    When you are working in NWDI empowered landscape, you have a very nice options in SLD that allows you to control the Development Component (DC) names that you will be creating in your Developer studio.
    This concept is called as Name Reservations.
    So, if you have defined a Name Prefix in the SLD, then in your Track inside developer studio you can only create DCs that start with the Name Prefix that you have defined in Name Reservations.
    To Create the Name Reservations, pelase go through the bellow mentioned procedure...
    Please open the below mentioned URL.
    http://<host>:<port>/sld
    Check if the Naming Service enabled or not?
    Assuming it is enabled then...
    Goto,
    1) Name Reservations >> Name Prefixes >> choose "Development Component" Name in name category.
    2) Here, you will be able to see all the allowed names for DC creation.
    3) You can also create a new name prefix that you desire (e.g. abc.com/test)
    4) Once, you have added the desired Prefix in the Name reservations.
    5) Open the CMS Web UI from following URL...
    http://<host>:<port>/webdynpro/dispatcher/sap.com/tcSLCMS~WebUI/Cms
    6) Goto,
    Landscape Configurator >> Select Any Track inside "Tracks" Table >> Domain Data >> Click "Change" Button >> Click "Update CMS button"
    7) In NWDS remove your previously loaded development configurations >> Import the same development Configurations once again and now try creating a new DC. It will reflect the same vendor name that you have defined in the SLD Name Reservations.
    Let us know about the results.
    Regards,
    Shreyas Pandya

  • Performance tuning questions

    i am fresher in sap-abap. so i have some doubts.
    how to increase performance in a report. what r the minimum steps to follow.
    expecting the answer more clearly

    Hi Josh,
    Here is a detailed document for performance check:
    <b>AWARD POINTS IF IT HELPS:</b>
    5.1     SQL 
         In order to enhance the performance of your ABAP code a number of useful guidelines can be used.
    •     Use SELECT SINGLE wherever possible to retrieve up to one row of information.  It is important to specify all the key fields to ensure a unique record.
    •     Be careful using the FOR ALL ENTRIES addition since this is very bad for very large datasets (10,000+ records)
    •     Joins and subqueries are good
    •     Do not use SELECT * statement unless the program needs ALL columns from the table. Instead, only specify the fields you require. This will also avoid unnecessary network transports.  The addition INTO CORRESPONDING FIELDS of the INTO clause of the SELECT statement is worthwhile to use only for large amounts of data where the external table and destination fields have the same names. Consider the use of the DISTINCT option in the case of many duplicate entries.
         The following example compares selecting all fields to selecting only the document number, the item number and the material.
         Avoid:.  select   *      from vbap
                                         where vbeln in s_docno.
                   endselect.
         Use:     select vbeln posnr matnr
         into (wa_vbap-vbeln, wa_vbap-posnr, wa_vbap-matnr)
         from vbap
         where vbeln in s_docno.
                   endselect.
    Important Points:
         The order of the fields retrieved must match the order of the destination fields in the field list.
    •     Use the SELECT...WHERE clause to restrict data rather than retrieve all rows and use a CHECK or IF statements to filter data.
         Avoid:     select  vbeln  posnr matnr
         into (wa_vbap-vbeln, wa_vbap-posnr, wa_vbap-matnr)
         from vbap.
                      check s_docno.
                   endselect.
         Use:     select vbeln  posnr matnr
         into (wa_vbap-vbeln, wa_vbap-posnr, wa_vbap-matnr)
         from vbap
         where vbeln in s_docno.
                   endselect.
    Important Points:
         Order the columns in the where clause of a select in the same order as the key or index table.
    •     WHERE Clause Tips
    o     Exploit the indexes of  the database tables for an efficient use of the WHERE clause. To do so check all index fields with the equality operator (EQ, =) and concatenate these checks by AND. The primary key of a database table makes up its primary index automatically. Secondary indexes for a database table can be created in the ABAP Dictionary.
    o     If possible, include all columns of the key or an index in the where clause. Use a default or appropriate value. If the column(s) is not included, the database may not be able to fully utilise the index.
    o     Avoid complex WHERE clauses. The system must split up those into single statements for the database system.
    o     Do not use the logical NOT in WHERE clauses but inverted operators instead. The logical NOT is not supported by the database indexes.
    •     Try to avoid the select … endselect  programming construct. Rather select all the required records from the database directly into an internal table and loop at the table to process the entries.  This is usually faster than the select … endselect code, and also allows easier debugging of the code.
         Avoid:     select vbeln  posnr matnr
         into (wa_vbap-vbeln, wa_vbap-posnr, wa_vbap-matnr)
         from vbap
         where vbeln in s_docno.
                       write:/ wa_vbap-vbeln, wa_vbap-posnr, wa_vbap-matnr.
                   endselect.
    Use:     select vbeln posnr matnr into table ts_vbap
                   from vbap
                   where vbeln in s_docno.
              loop at ts_vbap into wa_vbap.
                   write:/ wa_vbap-vbeln, wa_vbap-posnr, wa_vbap-matnr.
              Endloop.
    •     Avoid nested select statements if possible as they generally have  poor performance.  It is preferable to select all the entries for each table directly into an internal table and use nested internal table loops to process all the entries. 
    •     Check runtime analysis tips and tricks for detailed comparisons in select performance (SM30). SELECT statements.
    •     Use aggregate expressions in the SELECT clause to perform calculations instead of transporting great amounts of data and calculating thereafter.  This distributes the processing load and minimises the network data transfer.  Valid aggregate functions include: MAX, MIN, AVG, SUM and COUNT.
    •     The storage of database tables in local buffers can lead to significant time savings. Use the buffering of database tables whenever possible. Use the addition BYPASSING BUFFER only if it is really necessary.
    If DISTINCT, SINGLE FOR UPDATE, and aggregate expressions are used in the SELECT clause, buffering should be turned off.
    •     Provide the appropriate selection criteria to limit the number of data base reads. Force users to provide selection criteria by evaluating the selection criteria entered on the selection screen during the AT SELECTION-SCREEN event.
    •     Create indices where needed to enhance query performance. This should be used in large table lookups to increase efficiency. For example, SELECT…WHERE FieldA = ‘001’. In this case FieldA is not a key field, therefore an index should be created to improve the efficiency of the select statement.  Beware that there is always an additional processing system overhead for indices.  Therefore, only create indices if a major performance benefit will be realised, especially if the program concerned is executed many times throughout the day and is business critical.
    5.1.1     SQL Checklist
    •     Keep the selected dataset small
    •     Keep the transferred data small
    •     Keep the number of database accesses small
    •     Use database buffers
    •     Create views for table joins instead of using multiple selects.
    •     Select data only one time where possible (i.e., don’t have multiple selects against the same table - get the data one time and store it in an internal table).
    •     Remove unused indexes from tables.
    5.2     General Programming Techniques
         Detailed below are a number of additional programming techniques that should be borne in mind when implementing ABAP code.
    •     When testing fields "equal to" something, one can use either the nested IF or the CASE statement.  The CASE is better for two reasons.  It is easier to read and the performance of the CASE is more efficient.
    •     Do not use MOVE CORRESPONDING unless the data is contiguous.
    •     When records a and b have the exact same structure, it is more efficient to MOVE a TO b than to MOVE-CORRESPONDING a TO b, if records a and b have the exact same structure.
                   MOVE  BSEG TO *BSEG.  is better than
                   MOVE-CORRESPONDING BSEG TO *BSEG.
    •     Do not use the COLLECT statement with large internal tables as this can be very CPU intensive.
    •     When reading a single record in an internal table, the READ TABLE WITH KEY is not a direct READ on a on a sorted table.  Therefore, SORT the table and use READ TABLE WITH KEY BINARY SEARCH.
    •     Use the SORT...BY when sorting internal tables.
              SORT ITAB BY FLD1 FLD2.  is more efficient than
                   SORT ITAB.
    •     Avoid hard-coding and use of literals in ABAP code. Use reference tables to drive processing to support business change flexibility and reduce ongoing maintenance costs.  If hard-coding and literals are required, be sure to include these as constants.
    •     The Tips & Tricks function is very useful in comparing different methods of coding without going to the trouble of coding both and then performing your own run-time analysis. System > Utilities > Runtime Analysis > Tips & Tricks.
    5.3     Logical Databases
    Use logical databases and ‘GET’ events wherever reads on parent/child segments need to be performed e.g. require data from both MARA then MARD table - use GET MARA then GET MARD. (Note you do not need to use an LDB if data from only the MARA or MARD table is required.)
    Where an LDB is used provide defaults or checks for the standard selection-options/parameters wherever possible.
    Avoid use of  logical data bases as much as possible - use SELECT  statements instead. (Logical databases are good as a reference tool to look up database hierarchies).
         &#61558;     Logical database should only be used when there are no other options.
    &#61558;     Use of Logical database in ABAP programs must be approved by a DEVELOPMENT TEAM LEAD
    &#61558;     Due to strategic importance of LDB’s and the potential impact on system performance, careful consideration should be made before creating new LDB’s. Consequently no LDB’s should be created without approval from the Development Team Lead
    5.4     Debugging
    When testing ABAP, use of the debugging tool plays an essential role in checking the value of variables during the execution of the program.  This tool should be used during the unit testing to ensure programs are executing as desired.
    You can use the debugging tool by selecting Program > Debugging from the ABAP program Development Initial screen.
    In addition to the static programming of breakpoints, ABAP’s on-line debugging tools also allow you to set breakpoints and interrupt conditions dynamically.  This makes the whole process of debugging reports much more flexible and the consequent advantage is that you do not have to change your code. Watchpoints can now be set based on the value a field takes (like R/2).
    Once you have stopped the report processing, you can view the contents of all the fields (up to 8), internal tables and database tables referenced in the report.  The system fields SY-TABIX and SY-DBCNT are now displayed at the bottom of the screen along with SY-SUBRC.
    Finally, you can change the contents of fields for debugging purposes and then resume report processing, with the changed data.  To set breakpoints select Breakpoints > Set from the ABAP: Editor screen.  Then execute the program.
    Beware that in order to debug SAPscript programs, hard-coded breakpoints are often required. Be sure to remove these once testing is complete and the program transported. Use the syntax BREAK username, rather than BREAK-POINT, as this will ensure the code only stops when running under the specified username.
    6     SAPscript Techniques
    6.1     Good Practice
    •     Always copy the SAP standard print programs where available and, in most instances, the layout set. Never start a complex SAPscript (e.g. Invoice, Purchase Order) from the beginning, as this will require far more development time to complete.
    •     When creating a new layout set by copying a SAP standard, always change the original language from D to E and then activate.
    6.2     Standards
    •     Naming convention for layout sets – this will follow the same as the program name, except the version number will be prefixed L. For example a purchase order layout set would be:
    ZMM_DESC where
    Z          First character of the program
    MM          SAP R/3 module/component
    DESC          Meaningful description i.e. PO printing, INVOICE.
    •     When copying SAP standard print programs ensure they have a standard header block as defined earlier. Also ensure that any code that is added, removed or changed is commented in the standard fashion.
    6.3     Standard Texts
    •     These should be of the following format:
         ZXX_DESC
    Where:
    Z          First character of the program
         XX          Module name
         DESC          Meaningful description.
    6.4     Tips
    •     Text elements must be maintained individually for each layout set language. Any other changes to the layout set i.e. window size or paragraphs, will be copied from the original language to the other languages.
         &#61558;     As layout sets are client-dependant they must be ‘transported’ between clients on the same box. To do this use the ‘Copy from Client’ function from within the ‘target’ client. This is language specific.
    &#61558;     Always ACTIVATE the layout set each change and in each language before transporting.
    &#61558;     The SAPscript debugger can be sent useful, this is turned on at the front screen on transaction SE71.
    &#61558;     Standard text used within a layout set must be assigned to a transport request using the program RSTXTRAN. Once assigned the transport request can be released in the usual manner via SE10.
    7     Changing the SAP Standard
    •     You can adjust the R/3 System to meet your needs in the following ways:
    o     Customizing: This means setting up specific business processes and functions for your system according to an implementation guide. The need for these changes has already been foreseen by SAP and an implementation procedure has been developed.
    o     Personalization: This means making changes to certain fields' global display attributes (setting default values or fading fields out altogether), as well as creating user-specific menu sequences.
    o     Modifications: These are changes to SAP Repository objects made at the customer site. If SAP delivers a changed version of the object, the customer's system must be adjusted to reflect these changes. Prior to Release 4.0B these adjustments had to be made manually using upgrade utilities. From Release 4.5A, this procedure has been automated with the Modification Assistant.
    o     Enhancements: This means creating Repository objects for individual customers that refer to objects that already exist in the SAP Repository.
    o     Customer Developments: This means creating Repository objects unique to individual customers in a specific namespace reserved for new customer objects.
    •     If your requirements cannot be met by Customizing or personalization, you may either start a development project or try using a CSP solution (= Complementary Software Product).
    •     A development project falls into the customer development category if the SAP standard does not already contain functions similar to the one you are trying to develop. If, however, a similar SAP function exists, try to assimilate it into your development project by either enhancing or modifying it, by using a user exit, or simply by making a copy the appropriate SAP program.
    •     Modifications can create problems, as new versions of SAP objects must be adjusted after an upgrade to coincide with modified versions of SAP objects you have created. Prior to Release 4.0B these adjustments had to be made manually using upgrade utilities. From Release 4.5A, this procedure has been automated with the Modification Assistant.
    •     Thus, you should only make modifications if:
    •     Customizing or personalizing cannot satisfy your requirements
    •     Enhancements or user exits are not planned
    •     It would not make sense to copy the SAP object to the customer namespace.
    7.1     Originals and copies
    •     An object is original in only one system.  In the case of objects delivered by SAP, the original system is at SAP itself. These objects are only copies in customer systems.  This applies to your development system and all other systems that come after it.
    •     If you write your own applications, the objects that you create are original in your development system.  You assign your developments to a change request, which has the type Development/Correction.
    This request ensures that the objects are transported from the development system into the subsequent systems
    7.2     Corrections and repairs
    •     Changes to an original are called corrections.  They are recorded in a change request whose tasks have the type "Development/correction". 
    •     If, on the other hand, you change a copy (an object outside its own original system), the change is recorded in a task with the type "Repair". Repairs to SAP objects are called modifications. 
    •     When you repair your own objects (for example, if something goes wrong in your production system), you can correct the original in your development system straight away. When you change copies, you must correct the original immediately!
    •     However, you cannot do this with SAP objects, because they are not original in any of your systems.
    •     You should only modify the SAP standard if the modifications you want to make are absolutely necessary for optimizing workflow in your company. Be aware that good background knowledge of application structure and flow are important prerequisites for deciding what kind of modifications to make and how these modifications should be designed.
    7.3     Modifications and upgrades
    During an upgrade or an import of R/3 Support Packages, new objects delivered overwrite existing objects of the SAP standard. In order to help customers keep those objects that have been modified in a previous release, SAP now offers upgrade adjustment for all objects being upgraded in the form of transactions SPAU and SPDD. These transactions allow customers to enter their modifications into the corresponding new objects being delivered at upgrade. The Modification Assistant supports this process of adopting customer modifications. In general, objects altered using the Modification Assistant can now be automatically accepted into the upgraded system if the modifications undertaken in the original version do not directly overlap those made in the customer version. If collisions occur between the two versions at upgrade (naming collisions, or if SAP has deleted an object modified by a customer), the system offers semi-automatic adjustment support. In some cases, however, you may still have to manually adjust objects using ABAP Workbench tools.
    •     Whenever you upgrade your system, apply a support package, or import a transport request, conflicts can occur with modified objects.
    •     Conflicts occur when you have changed an SAP object and SAP has also delivered a new version of it.  The new object delivered by SAP becomes an active object in the Repository of your system.
    •     If you want to save your changes, you must perform a modification adjustment for the objects.  If you have a lot of modified SAP objects, your upgrade can be slowed down considerably.
    •     To ensure consistency between your development system and subsequent systems, you should only perform modification adjustments in your development system.  The objects from the adjustment can then be transported into other systems.
    7.4     Modifications Procedures
    •     A registered  developer must register changes to SAP objects. Exceptions to this registration are matchcodes, database indexes, buffer settings, customer objects, patches, and objects whose changes are based on automatic generation (for example, in Customizing). If the object is changed again at a later time, no new query is made for the registration key. Once an object is registered, the related key is stored locally and automatically copied for later changes, regardless of which registered developer is making the change. For the time being, these keys remain valid even after a release upgrade.
    •     How do you benefit from SSCR (SAP Software Change Registration)?
    o     Quick error resolution and high availability of modified systems
    All objects that have been changed are logged by SAP. Based on this information, SAP's First Level Customer Service can quickly locate and fix problems. This increases the availability of your R/3 system.
    o     Dependable operation
    Having to register your modifications helps prevent unintended modification. This in turn ensures that your R/3 software runs more reliably.
    o     Simplification of upgrades
    Upgrades and release upgrades become considerably easier due to the smaller number of modifications.
    7.5     Modifications Assistant
    The aim of the Modification Assistant is to make modification adjustments easier. This is because (among other reasons) the modifications are registered in a different layer
    •     If you want to change an SAP object, you must provide the following information:
    o     SSCR key
    o     Change request
    •     The system informs you that the object is under the control of the Modification Assistant. Only restricted functions are available in the editor.
    •     You can switch the Modification Assistant on or off for the entire system by changing the R/3 profile parameter eu/controlled_modification. SAP recommends that you always work with the Modification Assistant.
    •     You can switch off the Modification Assistant for single Repository Objects.  Once you have done so, the system no longer uses the fine granularity of the Modification Assistant.
    •     In modification mode, you have access to a subset of the normal editor tools.  You can access these using the appropriate pushbuttons.  For example, in the ABAP Editor, you can:
    o     Insert
    The system generates a framework of comment lines between which you can enter your source code.
    o     Replace
    Position the cursor on a line and choose Replace.  The corresponding line is commented out, and another line appears in which you can enter coding.  If you want to replace several lines, mark them as a block first.
    o     Delete
    Select a line or a block and choose Delete.  The lines are commented out.
    o     Undo modifications
    This undoes all of the modifications you have made to this object.
    o     Display modification overview
    Choose this function to display an overview of all modifications belonging to this object.
    7.6     Restoring the original
    You can reset all of the modifications that you have made to the current object using the Modification Assistant by choosing this function.  The record of the modifications is also deleted.
    Remember that you cannot selectively undo modifications to an object.  You can only undo modifications based on the "all or nothing" principle.
         &#61558;     Any modifications in standard SAP object will require proper justification and needs to be documented. The rights of modification the standard SAP object is limited to PROJECT MANGER only.
    Cheers,
    ashish.

  • Error message installing BI Statistics. Any help?

    Hi,
    Ok, I am following the link: http://help.sap.com/saphelp_nw04/helpdata/en/8c/131e3b9f10b904e10000000a114084/content.htm
    to install BI Statistics (0BWTCT_STA).
    In rsa1, Bi Content, InfoArea, I collected 0BWTCT_STA to the right pane, and followed the Procedure in the link by choosing “grouping function for necessary objects only”
    the next step is to install. (Procedure 1 b. in the link).
    (The instruction does not indicate which objects to “check” for installation or not, so I left the default check marks)
    But I got the message below.
    I cancelled on seeing this message 2 times, but on the third attempt, I did not get the message and there was a prompt for transport request.
    1. If I continue now, with a transport request, will it install?
    2. Why did it stop giving the error?
    3. Can this installation cause any problem in the environment?
    4. What is the significance of this message I got?
    Message and details----
    Make repairs in foreign namespaces only if they are urgent                                                                               
    Message no. TR852                                                                               
    Diagnosis                                                                               
    The object being edited is in a namespace reserved for objects belonging
         to SAP or another software producer.                                   
         This system is supplied with this namespace.                                                                               
    System Response                                                                               
    The function continues.                                                                               
    Procedure                                                                               
    Only perform urgent repairs and only after consulting with or on       
         instruction from the owner of the namespace.

    Hello Amanda,
    Please see this OSS Note 431126 -  Activating characteristics that are document attributes.
    Thanks
    [Chandran|http://chandranonline.blogspot.com/]

  • Check - In CAF Development Components in NWDI: appropriate prefix not found

    Hi,
    I am developing CAF on the Composition Environment and use an NWDI structre.
    If I create a CAF DC on the track and define CAF Components(Business Object, Application Service...) in the DC, check in of these Activities throws me the following error and activation fails.
    Invalid name: appropriate prefix not found; choose another name or another name server
    com.sap.lcr.namealloc.api.NameSyntaxViolation: Invalid name: appropriate prefix not found; choose another name or another name server
         at com.sap.lcr.namealloc.NameServerUtil.checkForAllowedNamePrefix(NameServerUtil.java:1463)
         at com.sap.lcr.namealloc.NameAllocator.allocateName(NameAllocator.java:1022)
         at com.sap.lcr.namealloc.NameAllocator.reservePreliminary(NameAllocator.java:1283)
         at com.sap.ide.dii05.lib.internal.namereservation.NameReservation.reserve(NameReservation.java:134)
         at com.sap.ide.dii05.lib.internal.namereservation.NamereservationUtil.reservePackagesForDc(NamereservationUtil.java:222)
         at com.sap.ide.dii05.ui.internal.listener.NameReservationListener.reservePackages(NameReservationListener.java:79)
         at com.sap.ide.dii05.ui.internal.listener.NameReservationListener.validateNameReservation(NameReservationListener.java:72)
         at com.sap.ide.dii05.lib.internal.namereservation.VetoListener.beforeOperation(VetoListener.java:134)
         at com.tssap.dtr.client.lib.util.impl.VetoEventHandler.fireEventBeforeOperation(VetoEventHandler.java:46)
         at com.tssap.dtr.client.lib.vfs.impl.VersionedFileSystemManager.fireEventBeforeOperation(VersionedFileSystemManager.java:1693)
         at com.tssap.dtr.client.lib.vfs.impl.VfsActivity.checkIn(VfsActivity.java:1722)
         at com.tssap.dtr.client.lib.vfs.impl.VfsActivity.checkIn(VfsActivity.java:1661)
         at com.tssap.dtr.client.lib.vfs.impl.VfsCheckInOperation.perform(VfsCheckInOperation.java:33)
         at com.tssap.dtr.client.lib.vfs.impl.VFSOperationsGroup.performNew(VFSOperationsGroup.java:226)
         at com.tssap.dtr.client.lib.vfs.impl.VFSOperationsGroup.perform(VFSOperationsGroup.java:121)
         at com.tssap.dtr.client.lib.vfs.actions.CheckinAction.execute(CheckinAction.java:117)
         at com.tssap.dtr.client.eclipse.ui.actions.VfsObjectSelectionAction$5.doDtrJobInWorkerThread(VfsObjectSelectionAction.java:606)
         at com.tssap.dtr.client.eclipse.job.DtrJob.doInWorkerThread(DtrJob.java:49)
         at com.sap.ide.dii05.util.api.job.JdiJob$1.doInWorkerThread(JdiJob.java:75)
         at com.sap.ide.dii05.util.internal.job.InternalJdiJob$3$1.run(InternalJdiJob.java:224)
         at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1797)
         at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1779)
         at com.sap.ide.dii05.util.internal.job.InternalJdiJob$3.run(InternalJdiJob.java:233)
         at com.sap.ide.dii05.util.internal.job.BusyBackgroundIndicator.showWhile(BusyBackgroundIndicator.java:74)
         at com.sap.ide.dii05.util.internal.job.InternalJdiJob.internalRun(InternalJdiJob.java:214)
         at com.sap.ide.dii05.util.internal.job.InternalDiiJob.run(InternalDiiJob.java:275)
         at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
    I am generating, building and compiling the CAF DC before check-in the activity.
    Can you please help me about this issue?
    Regards,
    Yasar

    Thanks Jan! It solved!
    I have already created another workspace after all the tests just to be sure that the problem wasn´t on NWDS.
    It solved to me when I removed the reservation on SLD and recreated.
    Thank you so much!
    Gabriela

  • EU_IMPORT ERROR: during UPG from 4.7ee TO ECC6.0

    hello masters
                I am getting error while upg from 4.7ee to ecc6.0 on oracle under SapUp ,
    >>EU_IMPORT ERROR:, log file "EX000015.DPR": only 0 times "R3load.exe: job completed" found.
    Analyze the log file EX000015.DPR for error messages or program abort.
    D:\usr\sap\put\exe\R3load.exe: START OF LOG: 20090224011912
    D:\usr\sap\put\exe\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
    D:\usr\sap\put\exe\R3load.exe: version R7.00/V1.4
    Compiled Sep  1 2006 00:30:56
    D:\usr\sap\put\exe\R3load.exe -i D:\usr\sap\put\exchange\compack\EX000015.COD -p D:\usr\sap\put\log\EX000015.DPR -s D:\usr\sap\put\log\EX000015.DST -datacodepage 1100 -dbcodepage auto -nametab DDNTT~ DDNTF~ -t 4987
    (DB) INFO: connected to DB
    (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC
    (SQL) INFO: SSEXC.SQL not found
    (DB) INFO: REPOSRC~ created #20090224011912
    (RFF) ERROR: invalid checksum in data file "E:\UPGRADESOFT\Export2\Export2\UPG12\DBINDEP\EX000015.001"
                 current table was "REPOSRC~"
    (DB) INFO: REPOSRC^0 created #20090224012304
    (DB) INFO: disconnected from DB
    D:\usr\sap\put\exe\R3load.exe: job finished with 1 error(s)
    D:\usr\sap\put\exe\R3load.exe: END OF LOG: 20090224012304

    Hi,
    1. Check whether DB is running or not
    2. R3trans -d (here what is the return code)
    3. post the following logs from the put/log
    EU_IMP1.ELG
    EU_IMP1.LOG
    Phase List for the Upgrade to SAP ERP 2005 700
    PREPARE Modules:
    Parameter input
    Initialization
    Import
    Extension
    Integration
    Installation
    General checks
    Activation checks
    Necessary checks for conversions
    Optional checks for conversions
    Modification support
    Pre-processing
    Upgrade Phase Groups:
    Import and Modification Transfer
    Shadow System Installation
    Shadow System Operations: SPDD and Activation
    Shadow Import
    Downtime phases I: Switch tables and Kernel
    Downtime phases II: Conversion, Main Import, XPRAs
    Post Processing
    Explanations
    u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2013
    PREPARE Modules
    PREPARE Module: Parameter input (Mandatory)
    Phase Duration PREPARE Actions Log Files User Actions
    BEGIN_PRE < 10s Checks upgrade directory
    KEY_CHK < 1% Prompts for keyword from SAP main upgrade note KEYCHK.LOG
    Check for upgrade correction package and enter upgrade keyword
    EXTRACTKRN_PRE < 10s Extracts kernel EXTRKRN.LOG
    none
    INITPUT_PRE dial Initializes R3up
    DB2 UDB for z/OS and OS/390:
    Tests JCL Submission
    Enter parameters
    DB2 UDB for z/OS and OS/390:
    Test JCL Submission
    DBCHK_PRE < 10s Determines database version and SAP release
    CONFCHK_IMP < 10s Tests operating system and database version Upgrade operating system and database to the required version, if necessary
    SOLMAN_CHK < 1% Prompts for keyword from solution manager SOLMANCHK.LOG
    Enter keyword generated by solution manager
    CHKSYSTYPE < 10s Determines if system is SAP or customer CHKSYSTYPE.LOG
    TOOLVERSION_INI < 10s Determines and checks the tool version TOOLVERS.LOG
    Upgrade tools if necessary
    DBCONNCHK_INI < 10s Tests if new tools can connect to the database DBCONNCHK.LOG
    J2EE_CHK < 10s As of start release 620:
    Checks if J2EE is also running J2EECHK.LOG
    info
    REQ_J2EEUPG < 1% CBU: Requests j2ee prepare and upgrade
    SETSYNC_PREP_STARTED dial events for sync with Jump
    REQ_READNOTE < 1% CBU: Requests cbu specific parameters
    INIT_CBU < 1% CBU: Requests cbu specific parameters
    CHECKGROUP_END0 < 1% End of module
    PREPARE Module: Initialization (Mandatory)
    Phase Duration PREPARE Actions Log Files User Actions
    INITCURENV < 10s Initializes internal administration information
    DBCHK_INI < 10s Determines database version and SAP release
    RFCCHK_INI < 10s Tests RFC connection RFCCHK_INI.LOG
    VERSCHK_INI < 10s Checks SAP release Upgrade to a valid source release, if necessary
    VALCHK_INI < 10s Tests target system: Is it a preliminary version? (Cannot upgrade the system) VALCHK.LOG
    UNICODE_CHK_PRE < 10s Checks, if DB is UNICODE UNICPTCP.LOG
    UNICHK.LOG
    SETSYNC_INFO_FINISHED dial events for sync with Jump
    UCMIG_DECISION < 10s For start release 46C to 46D:
    Check for combined Upgrade and Unicode Conversion UCMIGDEC.LOG
    CLNT_CHK_INI < 1% Checks whether clients are locked for SAP system upgrade EXECCT.LOG
    CLNTOUT.LOG
    Unlock clients for SAP system upgrade, if necessary
    PATCH_CHK1 < 1% Finds unconfirmed Support Packages and displays the result PATCHOUT.LOG
    EXECPT.LOG
    Call transaction SPAM to confirm any unconfirmed Support Packages, if necessary
    INTCHK_INI < 10s Checks whether the inactive nametab is empty
    ADJ_CNTRANS 1% ( Resolves inconsistencies in TABART-TABSPACE mapping ADJCNTRANS.LOG
    ADJCNTRANS.ELG
    INIT_CNTRANS < 10s Initializes the container name translator SELTAIA.LOG
    SELDBS.LOG
    INICNT.LOG
    Fix inconsistencies in TABART-TABSPACE mapping, if necessary. Additional informations are given in SAP Note 541542
    CNTRANS_PRE < 10s Makes adjustments to scripts for MCOD systems CNTPRE.LOG
    DMPSPC_INI < 10s Dumps database size DMPSPC_INI.LOG
    CHK_DB6_REG_PRE dial DB2 UDB for UNIX and Windows:
    Checks DB6 registry parameters
    SPACECHK_INI < 10s Checks database free space DBFPREP.LOG
    Extend the database, if necessary
    KRNCHK_DEST < 10s For start release 30D to 31I:
    Checks the SAP kernel version for the destination release KRNCHK.LOG
    Import kernel for the destnation release, if necessary
    DBPREP_CHK < 10s DB2 UDB for z/OS and OS/390:
    Performs DB2/390-specific checks DB2 UDB for z/OS and OS/390:
    Make preparations as described in SAP Note 400565
    EXECCV < 10s As of start release 46C:
    Reads cvers table EXECCV.LOG
    EXECAV < 1% Finds add-ons EXECAV.LOG
    COMPINFO_INI < 10s As of start release 46C:
    Get the component information after the addon selection COMPINFOINI.LOG
    ADDON_CHK dial Checks the current Add-on versions against the ranges in IS_RANGE.LST ADDONCHK.LOG
    ADDON_INFO dial print add-on information ADDONINFO.LOG
    ADDON_SPEC1 dial Requests add-on information ADDONSPEC1.LOG
    ADDON_TREAS dial Special actions for treasury ADDONTREAS.LOG
    ADDON_WFM dial As of start release 620:
    Special actions for wfmretail ADDONWFM.LOG
    ACE_CHK dial For start releases 620:
    Special actions for CRM ACECHK.LOG
    CRM_BILL dial For start release 610 to 620:
    Requests note handling CRMBILL.LOG
    PR_DBPAR dial ORACLE:
    Checks Oracle parameters PRDBPAR.LOG
    CHECKGROUP_END1 < 1% End of module
    PREPARE Module: Import (Mandatory)
    Phase Duration PREPARE Actions Log Files User Actions
    REQIMPORT dial Displays question Confirm execution of Import module
    READDATA 1% Reads data files from the upgrade CDs Mount each requested upgrade CD
    READDATA_EXT < 1% Reads additional data files from the upgrade CDs Mount each requested upgrade CD
    TOOLFIX_CHK < 1% Integrates the Upgrade Correction Package TOOLFIXCHK.LOG
    Unpacks the fix archive again to patch files from READDATA_EXT.
    CPYFIL0_CBU < 1% CBU: Copy files CBUCPY0.LOG
    EXEC_CPYFIL1_CBU < 1% CBU: Copy cbu specific files CBUCPY1.LOG
    FRP_CHK < 1% For start releases 640:
    Unpacks the FRP to the kernel directory FRPCHECK.LOG
    UNICODELIB_CHK1 < 10s Checks for missing UNICODE libs in kernel directory UCLIBCHK.LOG
    CNV_CHK_IMP < 10s Finds outstanding conversions and restart logs of terminated conversions Make conversions (after discussion with SAP consultant), if necessary
    ICNVCHK_IMP < 10s As of start release 40A:
    Checks whether incremental conversion from previous upgrade has finished ICNVEX.LOG
    ICNVLIST.LOG
    ICNVCHK.LOG
    Complete incremental conversion with transaction ICNV, if necessary
    SCRIPT_CHK_TOOL3 < 10s For start releases up to 31I:
    Avoids critical conversions in tool import CNVTST.LOG
    CLCNVTAB.LOG
    SCRIPTCHK.LOG
    SCRIPT_CHK_TOOL4 < 10s As of start release 40A:
    Avoids critical conversions in tool import CNVTST.LOG
    CLCNVTAB.LOG
    SCRIPTCHK.LOG
    SCRIPT2_TST_RESTART < 10s Performs actions for restart handling UPGPARAM.LOG
    REPTST.LOG
    SCRTREST.LOG
    TRBATCHK_IMP < 10s Checks whether table TRBAT is empty Perform any actions specified by R3up
    CLNT_CHK_IMP < 1% Checks whether clients are locked for SAP system upgrade EXECCT.LOG
    CLNTOUT.LOG
    Unlock clients for SAP system upgrade, if necessary
    INTCHK_IMP < 10s Checks whether the inactive nametab is empty
    SPACECHK_IMP < 10s Checks database free space DBFPREP.LOG
    Extend the database, if necessary
    PATCH_CHK2 < 10s Finds unconfirmed Support Packages and displays the result PATCHOUT.LOG
    EXECPT.LOG
    Call transaction SPAM to confirm any unconfirmed Support Packages, if necessary
    NTHISTCRE < 10s For start releases up to 40B:
    Creates tables for nametab administration so that new tools have access NTABHIST.LOG
    ALTER_TO < 1% Deletes tables that describe the delivery ALTER_TO.LOG
    TOOLIMPD1 2% For start release 30D to 31I:
    Prepares ABAP Dictionary for upgrade tools TOOLIMPD.ELG
    TOOLIMPD2 2% For start release 40A to 40B:
    Prepares ABAP Dictionary for upgrade tools TOOLIMPD.ELG
    TOOLIMPD3 2% For start release 45A to 46D:
    Prepares ABAP Dictionary for upgrade tools TOOLIMPD.ELG
    TOOLIMPD4 2% As of start release 610:
    Prepares ABAP Dictionary for upgrade tools TOOLIMPD.ELG
    MVNTAB_TOOL < 1% Activates nametabs for upgrade tools MVNTTOOL.ELG
    MVNTTOOL.LOG
    TOOLIMPI 1% Imports tools for the SAP system upgrade TOOLIMPI.ELG
    TOOLIMPM < 1% Imports tools for the SAP system upgrade TOOLIMPM.ELG
    TOOLIMP4_FIX < 1% For start releases up to 46D:
    Imports tools for the SAP system upgrade TOOLFIX.ELG
    TOOLIMP6_FIX < 1% As of start release 610:
    Imports tools for the SAP system upgrade TOOLFIX.ELG
    TOOLIMP4_UCMIG < 1% For start releases up to 46D:
    Imports tools for the combined Upgrade and Unicode Conversion TOOLUCMIG.ELG
    NPREPCRE0 3% Imports tables that describe the delivery from Upgrade CD1 PREPIMP.ELG
    JOB_RSUVSAVE < 1% Saves old entries of table UVERS PSUVSAVE.ELG
    PSUVSAVE.LOG
    UVERS_PREIMP < 10s As of start release 46B:
    Writes entry in table UVERS UVERSINI.LOG
    UVERS_INIT < 10s As of start release 46B:
    Writes entry in table UVERS UVERSINI.LOG
    SQLDB_UVERS_INIT (var For start releases up to 46A:
    Cleans tables for unicode conversion UVERSINS.LOG
    UVERS_CHK_IMP < 10s Checks consistency of table UVERS UVERSCHK_IMP.LOG
    BATCHCHK_IMP < 1% Tests whether the background server can access the upgrade directory BATCHCHK_IMP.LOG
    UCMIG_STATUS_SET0 < 10s Set status for combined Upgrade and Unicode Conversion UCMIGSETSTAT0.LOG
    JOB_RSCVINIT < 1% Initializes table CVERS PSCVINIT.ELG
    PSCVINIT.LOG
    RUN_RSPTBFIL_PREP < 1% Creates PUTTB and PUTTB_SHD tables RSPTBINI.ELG
    RSPTBINI.LOG
    READPUTTB_INI < 10s Reads table PUTTB and places it in the file system RDPUTTB.LOG
    JOB_RDDGENRS < 1% Generates tool reports RDDGENRS.LOG
    RUN_RDDITCUG < 1% For start release 30D to 31I:
    Generates GUIs PDDITCUG.ELG
    PDDITCUG.LOG
    RUN_RSINCGEN_IMP < 1% Adapts ABAP include RSTABINC to the system PSINCGEN.ELG
    PSINCGEN.LOG
    TR_BUF2HEAP_INSTIMP < 10s Moves upgrade requests from the INSTIMP.BUF buffer to the R3up buffer TPSHBUF.LOG
    TRB2H.LOG
    TR_EXT2HEAP < 10s Moves additional upgrade requests to the R3up buffer TREXT2HEAP.LOG
    TR_MODACT_IMP < 1% Calculates the amount of data from the upgrade requests TRMAIMP.LOG
    TRMAIMP.ELG
    SQLSCREXE_UPGPAR < 10s Makes parameter settings for the upgrade procedure PARAMSHD.LOG
    UPGPAR.ELG
    UPGPAR.LOG
    SQLDB_PARAMCOMP < 10s Makes parameter settings for the component upgrade procedure PARAMCOMP.LOG
    JOB_RDDPURI2 < 1% Does various cleanups PDDPURI2.ELG
    PDDPURI2.LOG
    CHECKGROUP_END2 < 1% End of module
    PREPARE Module: Extension (Mandatory)
    Phase Duration PREPARE Actions Log Files User Actions
    RUN_RSTODIRM_CLEAN < 1% Check delivery catalog for inconsistencies RSTODIRM.ELG
    RSTODIRM.LOG
    MULTSPC_UC < 10s Adapts space requirements
    ADDSPAREQ_0 < 10s Prepares space check on the database
    EXECLANG < 1% Determines installed languages EXECLG.LOG
    LANG_CHK < 10s Checks whether the new release supports the installed languages LANGOUT.LOG
    Delay upgrade until next release, if necessary
    LANG_SELECT 1% Copies data for the language import into the upgrade directory LANGSEL.LOG
    LANGSEL.ELG
    RUN_RSUPGSLI < 1% Configures the selective-language-import option RSUPGSLI.ELG
    RSUPGSLI.LOG
    SPAM_CHK_INI < 1% Checks SPAM version SPAMCHK.LOG
    UPLOAD_REQUEST dial Prompts you to retrieve packages UPLOADREQ.LOG
    Retrieve packages that are required, if necessary
    JOB_CBUPIFCHK < 1% CBU: Checks PIF file CBUPIFCHK.ELG
    CBUPIFCHK.LOG
    NCVERS_READ < 10s Determines components contained in the delivery NCVERSOUT.LOG
    COMPINFO_EXP < 10s Get the component information concerning export components COMPINFOEXP.LOG
    IS_MV_CHK1 < 10s Checks version of IS_MOVES.LST file ISMVCHK1.LOG
    NAVERS_READ < 10s Initializes NAVERS from delivered and customer addon components NAVERSOUT.LOG
    IS_INIT < 10s Initialize for IS phases IS_INIT.LOG
    IS_INST_BICONT < 10s For start releases up to 620:
    Fake BI_CONT installation IS_INST_BICONT.LOG
    IS_INST_LIST < 10s Fake addon Installations from list (if needed) IS_INST_LIST.LOG
    IS_MOVEMENT < 10s Determine/decide Add-on movements IS_MOVEMENT.LOG
    COMPINFO_ISMV < 10s Get the component information after the addon movements COMPINFOISMV.LOG
    SFW_MOVEMENT < 10s SFW Addon Movements SFW_MOVEMENT.LOG
    COMPINFO_SFWMV < 10s Get the component information after the sfw movements COMPINFOSFWMV.LOG
    ADDONSPEC_OIL dial For start releases up to 640:
    Special actions for IS_OIL ADDONSPEC_OIL.LOG
    ADDONSPEC_ISPSCA dial For start releases up to 640:
    Special actions for IS_PS-CA ADDONSPEC_ISPSCA.LOG
    RUN_RSUPGSFW < 1% For start releases up to 640:
    SFW only: Determines active BF(S) according to installed Addons RSUPGSFW.ELG
    RSUPGSFW.LOG
    IS_TABDMP < 1% Dump addon tables to file IS_DUMPTABLES1.LOG
    IS_SELECT dial Decide about all Add-ons IS_SELECT.LOG
    Decide what to do with the add-ons during the upgrade
    COMPINFO_ADDON < 10s Get the component information after the addon selection COMPINFOADDON.LOG
    ADDON_QCALC < 1% Calculates queue for selected add-ons ADDONQCALC.LOG
    SPDA_ADDONQCALC.LOG
    IS_MV_CHK2 < 10s Checks version of IS_MOVES.LST file ISMVCHK2.LOG
    TR_EXPPKG2HEAP < 10s Moves export packages to the R3up buffer TREXPPKG2HEAP.LOG
    PATCHK_EQUI < 10s Determines Support Package level for target release that corresponds to the level of the source release PATCHKEQUI.LOG
    PATCH_CHK3 < 1% Find unconfirmed Support Packages and checks whether the source release contains Support Packages that are more recent than the version of the target release PATCHOUT.LOG
    EXECPT.LOG
    Call transaction SPAM to confirm any unconfirmed Support Packages
    Call SAP Note 073510 to check whether you can upgrade the system or which Support Packages are equivalent to those in the target release.
    EXEC_CPYFIL3_CBU < 1% CBU: Copys PIF files CBUCPY3.LOG
    BIND_PATCH dial Includes Support Packages for the target release PATCHINT.LOG
    SPDA_PATCHINT.LOG Include Support Packages in the upgrade, if necessary
    COMPINFO_SPP < 10s Get the component information after the support package selection COMPINFOSPP.LOG
    ADDON_LANGINC < 1% Include Add-on language packages ADDONLANGINC.LOG
    SPDA_ADDONLANGINC.LOG
    TR_CMDIMPORT_FDTASKS < 10s Imports command files for full and delta tasks PCMDIMPFD.ELG
    PCMDIMPFD.LOG
    IS_MERGE < 10s Adds Supplement Tasks (without AOS) to the TRStorage IS_MERGE.LOG
    TR_QUEUE2HEAP < 10s Moves the upgrade requests of the queue to the R3up buffer TRQUEUE2HEAP.LOG
    TR_CMDIMPORT_PREPARE < 1% Imports piece lists for included Support Packages PCMDIMP.ELG
    PCMDIMP.LOG
    JOB_RDDIT020 < 1% Merges transports for add-ons in NAVERS PDDIT020.ELG
    PDDIT020.LOG
    IS_SYNC_20 < 1% Synchronizes NAVERS in file system ISSYNC20.LOG
    CONFLICT_CHECK < 1% Checks for conflicts according to transaction SPAM CONFLCHK.LOG
    SPDA_CONFLCHK.LOG
    ADJUSTPRP dial Prepares adjustment calculation: Imports command file flagged in other system, if necessary ADJUSTPRP.ELG
    Select command file, if necessary
    INTEG_PATCH < 1% Selects the Support Package integration file and imports the requests contained in it INTGPTCH.LOG
    UCMIG_REQINC < 10s Ask for customer request for preparation of Unicode Conversion UCMIGREQINC.LOG
    ICNVXRQ < 1% Checks prerequisites for ICNV DDICNV.LOG
    ICNVXRQ.ELG
    ICNVXRQ.LOG
    CHECKGROUP_END3 < 1% End of module
    PREPARE Module: Integration (Mandatory)
    Phase Duration PREPARE Actions Log Files User Actions
    IS_MERGE_I < 10s For start release 30D to 31I:
    Adds Supplement Tasks (without AOS) to the TRStorage IS_MERGE.LOG
    TR_CMDIMPORT_PREPARE_31I < 1% For start release 30D to 31I:
    Imports piece lists for included Support Packages PCMDIMP.ELG
    PCMDIMP.LOG
    RUN_RSTODIRM_BIND < 1% Preparation of the delivery directory RSTODIRM.ELG
    RSTODIRM.LOG
    TR_TODIR_MERGE_PATCH < 1% Merges included Support Packages with the delivery directory
    JOB_RDDIT021 < 1% Merges add-ons in the delivery list PDDIT021.ELG
    PDDIT021.LOG
    UVERS_UP_T < 1% Changes the status in table UVERS
    TR_MODACT_ADD < 1% Calculates the amount of data in add-on and language requests TRADIMP.LOG
    TRADIMP.ELG
    TR_MODACT_DISC < 1% Calculates the amount of data in additional Support Package requests TRDIIMP.LOG
    TRDIIMP.ELG
    TR_COLLTABS_PREP < 1% Totals data TRCOLLTA.LOG
    TRCOLLTA.ELG
    TABSPC_PREP 2-10 Calculates which tables are part of import into old tables TABSPCP.LOG
    TABSPCP.ELG
    ADDSPAREQ_N < 10s Prepares space check on the database
    ADDSPAREQ_S < 10s Prepares space check on the database
    ADDSPAREQ_T < 10s Prepares space check on the database
    CHECKGROUP_END10 < 1% End of module
    PREPARE Module: Installation (Mandatory)
    Phase Duration PREPARE Actions Log Files User Actions
    INITSHD dial Prompts for shadow parameters Enter shadow parameters
    SHDINST_CRE < 10s Creates directory structure for the shadow instance SHDINST_CRE.LOG
    SHDINST_CPY < 10s Copies the profiles SHDINST_CPY.LOG
    SHDINST_ADAPT < 10s Adapts the profiles to the shadow instance SHDINST_ADAPT.LOG
    SHDINST_MOD < 10s Adapts the system settings ALPSHDIN.LOG
    ALPSHDDF.LOG
    SHDINST_REQ < 10s Checks ports for shadow instance SHDINST_REQ.LOG
    Perform actions from CHECKS.LOG, if necessary
    SHDINST_OS < 10s Performs operating system-specific actions SHDINST_OS.LOG
    Perform actions from CHECKS.LOG , if necessary
    SHDINST_SDB_CHK < 10s Checks database-specific settings MaxDB: Adjust the database parameters MAXLOCKS and MAXUSERTASKS, if necessary
    SHDINST_DB_PREP < 1% Checks database-specific settings SHDUSREX.LOG
    SHDUSRCRE.LOG
    SHDDBPRP.LOG
    Perform actions from CHECKS.LOG, if necessary
    SHDINST_SWT_HOST < 10s Adjusts the profile of the shadow instance, if necessary SHDINST_SWT.LOG
    SHDINST_PFPAR < 10s Checks with sappfpar the shadow instance profile SHDINST_PFPAR.LOG
    Perform actions from CHECKS.LOG, if necessary
    RUN_RSUPGRFC < 1% Creates RFC connection SAP_UPGRADE_SHADOW_SYSTEM PSUPGRFC.ELG
    PSUPGRFC.LOG
    CHECKGROUP_END11 < 1% End of module
    PREPARE Module: General checks (Mandatory)
    Phase Duration PREPARE Actions Log Files User Actions
    CONFCHK < 1% Tests operating system and database version Upgrade operating system and database to the required version, if necessary
    DB_ACTION_RUN_PRE < 1% DB2 UDB for UNIX and Windows:
    Remove volatile flags DBACTRUN.LOG
    CHK_DB6_PAR_PRE dial DB2 UDB for UNIX and Windows:
    Checks DB6 parameters
    SPACECHK_GEN < 1% Checks database free space DBFPLUSD.LOG
    Extend the database, if necessary
    TOOLVERSION_EXE < 10s Determines and checks the tool version of the new kernel TOOLVRSEXE.LOG
    Upgrade $(PUTPATH)/exe if necessary
    UNICODELIB_CHK2 < 10s Checks for missing UNICODE libs in kernel directory UCLIBCHK.LOG
    FREECHK < 1% Checks disk space for logs and SAP kernel
    Checks whether the SAP kernel can be overwritten Increase disk space, if necessary
    Check SAP kernel write authorization, if necessary
    LC_CHECK < 1% Checks Livecache LCCHECK.LOG
    Checks Livecache
    PROFSET < 10s For start releases up to 46C:
    Sets DDIC autorizations PROFSET.LOG
    DB_ACTION_PRE < 1% ORACLE:
    Performs database-specific actions SELDBSL.LOG
    ALTDBS.LOG
    DBACTPRE.LOG
    DB_ACTION_EXTMAN < 1% ORACLE:
    Determines extent management on database Oracle EXTMAN.LOG
    DBACTEMA.LOG
    REPACHK < 1% Finds SAP objects locked in repairs or requests REPACHK.LOG
    Release repairs and requests, if necessary
    CNV_CHK_GEN < 1% Finds outstanding conversions and restart logs of terminated conversions Make conversions (after discussion with SAP consultant), if necessary
    TRBATCHK_GEN < 1% Checks whether table TRBAT is empty Perform any actions specified by R3up
    CLNT_CHK_GEN < 1% Checks whether clients are locked for SAP system upgrade EXECCT.LOG
    CLNTOUT.LOG
    Unlock clients for SAP system upgrade, if necessary
    SCRIPT_TST_DDART < 1% Checks entries in table TA and IA CUSTTA.LOG
    SCRPTDDA.LOG
    If errors occur, see SAP Note 500252
    JOB_RSAUCHK_DUP < 1% Checks for double F rules RSAUCHKD.ELG
    RSAUCHKD.LOG
    See SAP Note 431886
    JOB_RSAODSACTIVATE_PRE < 1% Performs TADIR cleaning PSATADIR.ELG
    PSATADIR.LOG
    JOB_RSTLIBG < 1% Checks TADIR objects RSTLIBG.ELG
    RSTLIBG.LOG
    JOB_STRU_TADIR_GEN_1 < 1% Performs TADIR insert PSTRUGEN.ELG
    PSTRUGEN.LOG
    JOB_SDLINIT_TABLES_70 < 1% Performs SDLINIT preparations PSDLINIT.ELG
    PSDLINIT.LOG
    JOB_RSUPGRCHECK_PRE < 1% Checks consistency of generated repository PSUPGCHK.ELG
    PSUPGCHK.LOG
    JOB_RSMD_UPGR_PRE < 1% Performs component-specific checks PSMDCHK.ELG
    PSMDCHK.LOG
    JOB_RSODSO_GUID_CHK < 1% As of start release 610:
    Performs component-specific checks PSODCHK.ELG
    PSODCHK.LOG
    JOB_CRM_UPGRADE50 < 1% For start release 610 to 620:
    Removes duplicate table entries CRM_UPGRADE50.ELG
    CRM_UPGRADE50.LOG
    JOB_SDLINIT_TABLES_PRE < 1% As of start release 620:
    Performs BW specific checks RSSM_SDLINIT.ELG
    RSSM_SDLINIT.LOG
    JOB_CHECK_RSMONICDP_PRE < 1% As of start release 610:
    Performs BW specific checks RSSM_RSMONICDP.ELG
    RSSM_RSMONICDP.LOG
    JOB_DROP_TMPOBJ_PRE < 1% Deletes invalid nametab entries RSDR_NAMT_CL.ELG
    RSDR_NAMT_CL.LOG
    JOB_TS_UPG41 < 1% For start releases up to 620:
    Performs index check TSUPG41.ELG
    TSUPG41.LOG
    NTACT_CHK 2% Checks the consistency of the nametab entries NTCHK.ELG
    NTCHK.LOG
    Perform any actions specified by R3up
    INTCHK_GEN < 1% Checks whether the inactive nametab is empty
    SINXCHK < 1% Checks the consistency of the indexes in the substitution tables SINXCHK.LOG
    Delete indexes, if necessary
    VIEWCHK < 1% Checks for conflicts between customer tables in the SAP name range and delivered views VIEWCHK.LOG
    Delete tables, if necessary
    ENVCHK_PRE < 10s Checks whether profiles of user adm can be modified Assign write authorization to the user profiles, if necessary
    FRONTREQ_PRE < 10s Displays information about the upgrade of the front end software Upgrade the front end software, if necessary
    UVERS_CHK_GEN < 10s Checks consistency of table UVERS UVERSCHK_GEN.LOG
    BATCHCHK_GEN < 1% Tests whether background server can access the upgrade directory BATCHCHK_GEN.LOG
    PROFCHK < 10s Checks whether the profile names specified in phase INITPUT correspond with the names used by the SAP system PROFCHK.LOG
    Correct entries with R3up set stdpar, if necessary
    JOB_RXPRECHK_PRE < 1% For start release 30D to 31I:
    Performs preliminary checks for the XPRA RLXPRA40 PXPRECHK.ELG
    PXPRECHK.LOG
    JOB_RSVBCHCK_PRE < 1% Checks whether outstanding updates tasks and queued RFCs exist PSVBCHCK.ELG
    PSVBCHCK.LOG
    Check outstanding update tasks with transaction SM13 and queued RFCs with transaction SMQ1
    RUN_RSCHECKEXC < 1% For start release 610 to 6ZZ:
    Find tables in exchange table space that are not exchanged ( SAP Note 674070) RSCHECKEXC.ELG
    RSCHECKEXC.LOG
    SCRIPT_TST_TCPDB < 1% Checks code page settings TCPDB.LOG
    SCRTCPDB.LOG
    See SAP Note 015023, if necessary
    SCRIPT_TST_TCPDB_UC < 1% Checks code page settings TCPDB.LOG
    SCRTCPDB.LOG
    See SAP Note 015023, if necessary
    REMEMBER_N410963 < 10s ORACLE, for start releases up to 46D:
    Checks Oracle start release REMN410.LOG
    See SAP Note 410963, if necessary
    JOB_SRM_PRE_CHECKS_1 < 1% SRM specific checks PSRMPRE.ELG
    PSRMPRE.LOG
    JOB_J_3GJUPGCD < 1% As of start release 40B:
    DIMP specific checks PJ_3GJUPGCD.ELG
    PJ_3GJUPGCD.LOG
    CHECKGROUP_END4 < 1% End of module
    PREPARE Module: Activation checks (Mandatory)
    Phase Duration PREPARE Actions Log Files User Actions
    JOB_RADDRCHK < 1% For start releases up to 40B:
    Prepares for renaming of data elements PADDRCHK.ELG
    PADDRCHK.LOG
    Correct naming conflicts as described in SAP Note 096905
    ACTREF_CHK < 1% Checks whether activation errors might occur during the upgrade RSTODIRX.LOG
    RSTODIRX.ELG
    Remove references to SAP data elements and domains
    RUN_RSUPGDEC_PRE < 1% Checks if current structure extensions collide with the DDIC enhancement category of the target release RSUPGDEC.ELG
    RSUPGDEC.LOG
    Adjust include or consider help from SAP SAP Note 493387
    CHECKGROUP_END5 < 1% End of module
    PREPARE Module: Necessary checks for conversions (Mandatory)
    Phase Duration PREPARE Actions Log Files User Actions
    CNV_AVOID < 1% For start release 30C to 31I:
    Finds tables that can be reduced in size before the upgrade to speed up the conversion Reduce the size of the tables as described in SAP Note 076431
    JOB_RSCNVADR < 1% For start releases up to 40B:
    Prepares address data conversion PSCNVADR.ELG
    PSCNVADR.LOG
    Start the report for preparing the address data conversion as described in SAP Note 082167 and SAP Note 097032 as well as adaptions to number ranges as described in SAP Note 319986 and SAP Note 379769
    REQ_APOUPG0 dial Prompts for checks for the LiveCache Save the live cache: follow the instructions given in the manual
    JOB_MC01_CACL_CDP_PRE < 1% For start releases up to 610:
    Performs consistence check CDPCON.ELG
    CDPCON.LOG
    CHECKGROUP_END6 < 1% End of module
    PREPARE Module: Optional checks for conversions (Optional)
    Phase Duration PREPARE Actions Log Files User Actions
    CNV_LIST < 1% Finds tables that are converted during the upgrade (if known to SAP) and lists them in a file
    ADDSPAREQ_AD < 10s Summarizes the results of all space checks
    DYNSPCADD < 1% Checks the database space requirements dynamically:
    Space needed temporarily for conversion
    Space for new secondary indexes
    DYNSPC.LOG
    SPACECHK_OPT < 1% Checks database free space DBFPLUSD.LOG
    Extend the database, if necessary
    CHECKGROUP_END7 < 1% End of module
    PREPARE Module: Modification support (Optional)
    Phase Duration PREPARE Actions Log Files User Actions
    SETPAR_PDIFFEXP_PRE < 1% Sets parameters for RDDIT006 SQLPDIFP.LOG
    SETPDIFP.LOG
    SETPDIFP.ELG
    RUN_RDDIT006_PRE < 1% Finds conflicts with central SAP Web Application Server objects DIFFCALC.ELG
    DIFFCALC.LOG
    Contact SAP to get modifications to central SAP Web Application Server objects, if necessary
    ADJUSTCHK_PRE < 1% Finds objects to be adjusted - preparation for transactions SPDD and SPAU ADJUSTCP.LOG
    ADJUSTCP.ELG
    Call transaction SPDD or SPAU to display modifications
    CHECKGROUP_END8 < 1% End of module
    PREPARE Module: Pre-processing (Optional)
    Phase Duration PREPARE Actions Log Files User Actions
    RUN_RSWBO230_PRE < 1% Deletes SAP requests from previous upgrades PSWBO230.ELG
    PSWBO230.LOG
    SAVE_VAR_CHK dial As of start release 40B:
    Requests SAVE_VAR information SAVEVARCHK.LOG
    Answer SAVE_VAR prompt
    JOB_RASUVAR1 < 1% As of start release 40B:
    save variants, see note 712297 PASUVAR1.ELG
    PASUVAR1.LOG
    CHECKGROUP_END9 < 1% End of module
    u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2013
    Upgrade Phase Groups
    Upgrade Phase Group: Configuration and Initialization
    Phase Duration Upgrade Actions Log Files User Actions
    BEGIN < 10s Checks upgrade directory
    INITPUT dial Initializes R3up
    DB2 UDB for z/OS and OS/390:
    Checks parameters and JCL submission service DB2 UDB for z/OS and OS/390:
    Enter parameters
    DBCHK < 1% Determines database version and SAP release
    SETSYNC_UPGR_STARTED dial events for sync with Jump
    SETSYNC_PREUP_STARTED dial events for sync with Jump
    VERSCHK < 1% Checks SAP release Upgrade to a valid source release first, if necessary
    UVERS_CHK < 1% Checks consistency of table UVERS UVERSCHK.LOG
    BATCHCHK < 1% Tests whether background server can access the upgrade directory BATCHCHK.LOG
    PATCH_CHK < 1% Finds unconfirmed Support Packages and displays the result PATCHOUT.LOG
    EXECPT.LOG
    Call transaction SPAM to confirm any unconfirmed Support Packages, if necessary
    CLNT_CHK < 1% Checks whether clients are locked for SAP system upgrade EXECCT.LOG
    CLNTOUT.LOG
    Unlock clients for SAP system upgrade, if necessary
    INTCHK < 1% Checks whether the inactive nametab is empty
    TOOLVERSION_UPG < 1% Determines all tool version TOOLVERS.LOG
    Upgrade tools if necessary
    ADDON_SPEC2 dial Requests add-on information ADDONSPEC2.LOG
    ADDONKEY_CHK < 1% Prompts for keyword for industry solution, if necessary
    ADDONKEY.LOG
    Enter keyword for industry solution, if necessary
    JDKCHK_UPG < 1% Checks availability of JDK JDKCHK.LOG
    Install JDK, if necessary
    SHDINST_CHK1 < 1% Checks the shadow instance SHDINST_CHK1.LOG
    INITSUBST < 1% Initializes for System Switch Upgrade Enter parameters
    FRONTREQ < 1% Informs users that they must import a new version of the SAP GUI Confirm
    CONFCHK_X < 1% Tests operating system and database version Upgrade operating system and database to the required version, if necessary
    VIEWCHK1 < 1% Finds conflicts between delivered views and customer tables in the SAP name range VIEWCHK1.LOG
    Delete tables, if necessary
    REPACHK1 < 1% Finds SAP objects locked in repairs or requests REPACHK1.LOG
    UCMIG_STATUS_CHK1 < 10s Check status of Unicode Conversion Preparations on the start release UCMIGCHKSTAT1.LOG
    JOB_RSVBCHCK2 < 1% Checks whether outstanding updates tasks and queued RFCs exist PSVBCHCK.ELG
    PSVBCHCK.LOG
    Check outstanding update tasks with transaction SM13 and queued RFCs with transaction SMQ1
    RUN_RSWBO230 0-2% Deletes SAP requests from previous upgrades PSWBO230.ELG
    PSWBO230.LOG
    JOB_RXPRECHK < 1% For start release 30D to 31I:
    Makes preliminary checks for the XPRA RLXPRA40 PXPRECHK.ELG
    PXPRECHK.LOG
    JOB_RS_OLTPSOURCE < 1% Performs OLTP source cleaning PSOLTPSC.ELG
    PSOLTPSC.LOG
    JOB_RSAODSACTIVATE < 1% Performs TADIR cleaning PSATADIR.ELG
    PSATADIR.LOG
    TABSPC_UPG < 1% Checks database version if it was too low during PREPARE TABSPCU.LOG
    TABSPCU.ELG
    CHK_DB6_REG_UPG dial DB2 UDB for UNIX and Windows:
    Checks DB6 registry parameters
    DB_ACTION_RUNSTATS 1% DB2 UDB for UNIX and Windows:
    Remove volatile flags DBACTRUN.LOG
    CHK_DB6_PAR_UPG dial DB2 UDB for UNIX and Windows:
    Checks DB6 parameters
    SPACECHK_ALL < 1% Checks free space on the database DBFPLUSD.LOG
    Extend the database, if necessary
    FREECHK_X < 1% Checks free space in the file system Confirm
    Enlarge the file system, if necessary
    DMPSPC_X < 1% Provides information on freespace in the database DMPSPC_X.LOG
    JOB_BTCTRNS0 < 1% As of start release 45A, strategy Resource-minimized:
    Deschedules background jobs BTCTRNS1.ELG
    BTCTRNS1.LOG
    UCMIG_STATUS_CHK21 < 10s Strategy Resource-minimized:
    Check status of Unicode Conversion Preparations on the start release UCMIGCHKSTAT2.LOG
    SETPAR_PDIFFEXP < 1% Sets parameters for RDDIT006 SQLPDIFU.LOG
    SETPDIFU.LOG
    SETPDIFU.ELG
    RUN_RSPTBFIL_INIT 1% Enters source release information in table PUTTB_SHD RSPTBINI.ELG
    RSPTBINI.LOG
    READPUTTB_UPG < 1% Reads table PUTTB and places it in the file system RDPUTTB.LOG
    SQLDB_SWITCH_DOCU < 1% enabling of shadow import for docu objects PUTTBDOKTL.LOG
    LOCKEU_PRE < 1% Strategy downtime-minimized: Prompts for time from when ABAP Workbench is locked LOCKEUPR.LOG
    Strategy downtime-minimized: Respond to prompt for lock time
    CHECKCDMOUNTS < 1% Checks whether all required CDs for the EU_IMPORT phases are available If a CD is missing, change the mount directories or, if you do not use mount directories, ignore the prompt
    Upgrade Phase Group: Import and Modification Transfer
    Phase Duration Upgrade Actions Log Files User Actions
    DB_ACTION_UPG < 1% Performs database-specific actions SELDBSU.LOG
    ALTDBS.LOG
    DBACTUPG.LOG
    CNTRANS_TPL < 10s MCOD only: Adapts container names in R3load CNTTPL.LOG
    SQLSCREXE_UPGEU1 < 1% Performs actions for restart handling PARAMEU1.LOG
    UPGPAREU.ELG
    UPGPAREU.LOG
    JOB_MC01_CACL_CDP_POST1 < 1% For start releases up to 610, strategy Resource-minimized:
    Performs consistence check CDPCON1.ELG
    CDPCON1.LOG
    REQSTOP_APO1 dial Strategy Resource-minimized:
    Prompts, if system may be stopped Confirm, that the system may be stopped
    LOCKSYS_APO1 < 1% Strategy Resource-minimized:
    Locks SAP system for user access LOCKSYSAPO.LOG
    STOPSAP_LCD1 < 1% Strategy Resource-minimized:
    Stops SAP system Isolate the central instance and stop all application servers
    STARTSAP_LCD1 < 1% Strategy Resource-minimized:
    Starts SAP system
    REQ_APOUPG1 dial Strategy Resource-minimized:
    Prompts to save the live cache Save the live cache: follow the instructions given in the manual
    SETSYNC_PREUP_FINI_R1 dial Strategy Resource-minimized:
    events for sync with Jump
    GETSYNC_PREUP_FINI_R1 dial Strategy Resource-minimized:
    events for sync with Jump
    SETSYNC_DOWN_START_R1 dial Strategy Resource-minimized:
    events for sync with Jump
    SETSYNC_EULCK_START_R1 dial Strategy Resource-minimized:
    events for sync with Jump
    JOB_GN_BEF_UPG_CRM40_1 < 1% Strategy Resource-minimized, as of start release 610:
    Performs consistence check MWCRM1.ELG
    MWCRM1.LOG
    EU_IMPORT1 1-2% Copies substitution set from Upgrade CD to the shadow tables EU_IMP1.ELG
    EU_IMP1.LOG
    Mount requested Upgrade CD, if necessary
    NTACT_NODBPOS < 1% Cleans up nametab NTSHDNDB.ELG
    NTSHDNDB.LOG
    NTACT_CONV_UC < 1% Generates nametabs of shadow tables in shadow nametab conv_uc NTSHDCUC.ELG
    NTSHDCUC.LOG
    SHADOW_NTACT_CP < 1% Generates nametabs of shadow tables in the shadow nametab NTSHDCP.ELG
    NTSHDCP.LOG
    SQLDB_SHDI_DOC31I_ON1 < 1% For start releases up to 31I:
    enabling of shadow import for docu objects, special handling startrelease 3.1I SHDI_DOC31I.LOG
    EU_IMPORT2 5-8% Copies substitution set from Upgrade CD to the shadow tables EU_IMP2.ELG
    EU_IMP2.LOG
    Mount requested Upgrade CD, if necessary
    EU_IMPORT3 2-5% Copies substitution set from Upgrade CD to the shadow tables EU_IMP3.ELG
    EU_IMP3.LOG
    Mount requested Upgrade CD, if necessary
    READDATA_EU4 < 1% Copies substitution set from Upgrade CD to the shadow tables, if necessary Mount requested upgrade CD, if necessary
    EU_IMPORT4 6-10 Copies substitution set from Upgrade CD to the shadow tables EU_IMP4.ELG
    EU_IMP4.LOG
    Mount requested Upgrade CD, if necessary
    EU_IMPORT5 15-2 Copies substitution set from Upgrade CD to the shadow tables EU_IMP5.ELG
    EU_IMP5.LOG
    Mount requested Upgrade CD, if necessary
    EU_IMPORT6 < 10s Copies substitution set from Upgrade CD to the shadow tables EU_IMP6.ELG
    EU_IMP6.LOG
    Mount requested Upgrade CD, if necessary
    EU_IMPORT7 < 10s Copies substitution set from Upgrade CD to the shadow tables EU_IMP7.ELG
    EU_IMP7.LOG
    Mount requested Upgrade CD, if necessary
    EUVIEWIMP < 1% Imports views for shadow tables ALTER34V.LOG
    INDQUE_CHK < 1% SAP DB:
    Checks for indexes INDQUECHK.LOG
    TR_APPENDBUF_UPG1 < 10s Moves upgrade requests from the R3up buffer to the hyperbuffer TRAPPB.LOG
    SHADOW_IMPORT_UPG1 1-6% Imports upgrade and language data into the shadow tables (no new tables) SHDUPGIMP1.ELG
    STARTSAP_IMP < 1% Starts SAP system if it was stopped during phase EU_IMPORT1
    REPACHK2 < 1% Finds SAP objects locked in repairs or requests REPACHK2.LOG
    Confirm locks for ABAP Workbench if not yet done in phase LOCKEU_PRE
    SETSYNC_EULCK_START_D1 dial Strategy Downtime-minimized:
    events for sync with Jump
    SETSYNC_EULCK_START_R2 dial Strategy Resource-minimized:
    events for sync with Jump
    UVERS_UP_U < 1% Changes the status in table UVERS
    CNV_CHK_XT < 1% Finds outstanding conversions and restart logs for conversions that have not been completed Make conversions (after discussion with SAP consultant), if necessary
    TRBATCHK_XT < 1% Checks whether table TRBAT is empty Perform any actions specified by R3up, if necessary
    LIST_LOAD < 1% Generates list of programs that need to be generated LISTLOAD.LOG
    JOB_RDDTAXIT < 1% Selects generated objects SYSPREP.ELG
    SYSPREP.LOG
    JOB_STRU_TADIR_GEN_2 < 1% Performs TADIR insert PSTRUGEN.ELG
    PSTRUGEN.LOG
    JOB_RSGENYTT < 1% Copies nametabs to table DDYTT/F PSGENYTT.ELG
    PSGENYTT.LOG
    SUBSTNT_INS < 1% Creates nametab entries for the new substitution tables STBNTINS.LOG
    RUN_RSINCGEN < 1% Generates include program for accessing substitution tables PSINCGEN.ELG
    PSINCGEN.LOG
    JOB_SRM_PRE_CHECKS_2 < 1% SRM specific checks PSRMPRE.ELG
    PSRMPRE.LOG
    RUN_RDDIT006 1-3% Determines deviations of the current system from the future standard SAP system (objects and modifications that need to be copied) DIFFCALC.ELG
    DIFFCALC.LOG
    ADJUSTCHK < 1% Determines ABAP Dictionary objects that need to be adjusted ADJUSTCK.LOG
    ADJUSTCK.ELG
    Confirm R3up message, if necessary
    JOB_RSPUSCAD < 1% Exports documentation created or modified by customer PSPUSCA4.ELG
    PSPUSCA4.LOG
    DB_ACTION_LOWQ1 < 1% Performs switch for DIFFEXP phases LOWERQ.LOG
    DBACTLQ1.LOG
    DIFFEXPADDE (var Exports content of add-on objects not stored in shadow tables DIFFEXPA.ELG
    DIFFEXPA.LOG
    SQLDB_LOCKFLAG_CCI (var Perform database correction after export LOCKFLAGRESET_CCI.LOG
    DIFFEXPADD (var Copies Dictionary part for add-on objects to the shadow tables DIFFEXPA.ELG
    DIFFEXPA.LOG
    DIFFEXPPKGE (var Exports content of support package ects not stored in shadow tables DIFFEXPP.ELG
    DIFFEXPP.LOG
    SQLDB_LOCKFLAG_CCP (var Perform database correction after export LOCKFLAGRESET_CCP.LOG
    DIFFEXPPKG (var Copies Dictionary part for support package objects to the shadow tables DIFFEXPP.ELG
    DIFFEXPP.LOG
    DIFFEXPLAN (var Exports language content of support packages not stored in shadow tables DIFFEXPL.ELG
    DIFFEXPL.LOG
    SQLDB_LOCKFLAG_CCL (var Perform database correction after export LOCKFLAGRESET_CCL.LOG
    DIFFEXPGEN 2% Copies Dictionary part of generated objects to the shadow tables DIFFEXPG.ELG
    DIFFEXPG.LOG
    DIFFEXPMOD < 1% Copies unsent modified objects to the shadow tables DIFFEXPR.ELG
    DIFFEXPR.LOG
    DIFFEXPCUSTE (var Export content of customer developments not stored in shadow tables DIFFEXPC.ELG
    DIFFEXPC.LOG
    SQLDB_LOCKFLAG_CCC (var Perform database correction after export LOCKFLAGRESET_CCC.LOG
    DIFFEXPCUST (var Copies Dictionary part of customer developments to the shadow tables DIFFEXPC.ELG
    DIFFEXPC.LOG
    DIFFEXPDDIV < 1% Exports inactive ABAP Dictionary versions DIFFEXPD.ELG
    DIFFEXPD.LOG
    DIFFEXPDOCU < 1% Exports customer extensions to SAP object documentation DIFFEXPO.ELG
    DIFFEXPO.LOG
    DIFFEXPCDOC < 1% Exports documentation for customer objects DIFFEXCO.ELG
    DIFFEXCO.LOG
    DIFFEXPTSAP < 1% Exports local private objects and test objects in the SAP name range DIFFEXPT.ELG
    DIFFEXPT.LOG
    DB_ACTION_UPQ1 < 1% Performs switch for DIFFEXP phases UPPERQ.LOG
    DBACTUQ1.LOG
    JOB_RDDSAVTE < 1% Copies technical settings in the ABAP Dictionary PDDSAVTE.ELG
    PDDSAVTE.LOG
    RUN_RDDCP4TB < 1% Copies non-delivered TADIR entries to the shadow tables PDDCP4TB.ELG
    PDDCP4TB.LOG
    RUN_RDDDL4TB < 1% Deletes entries for deleted objects from the shadow table TADIR PDDDL4TB.ELG
    PDDDL4TB.LOG
    RUN_RSTRESNC < 1% Copies namespace reservations to the shadow tables PSTRESNC.ELG
    PSTRESNC.LOG
    JOB_RDDINDPR < 1% Finds all secondary indexes INXPREP.ELG
    INXPREP.LOG
    Upgrade Phase Group: Shadow System Installation
    Phase Duration Upgrade Actions Log Files User Actions
    ALTEXT_MAXALL < 1% ORACLE:
    Sets tablespace extents as unlimited SELALTAB.LOG
    DBACTGRA.LOG
    DBACTGRA.ELG
    SQLSCREXE_MLI4 < 10s For start releases up to 46D:
    Creates the license for the shadow instance CPMLICHK.LOG
    SQLEXEML.ELG
    SQLEXEML.LOG
    SQLSCREXE_MLI6 < 10s As of start release 610:
    Creates the license for the shadow instance CPMLICHK.LOG
    SQLEXEML.ELG
    SQLEXEML.LOG
    SQLDB_CPUSR < 10s Initializes authorizations SQLEXUS.LOG
    PSCRGEN_ALIAS < 10s Generates scripts for aliases/views/synonyms SQLGENAL.ELG
    SQLGENAL.LOG
    SCRGEN_ALI_ORG < 10s Generates scripts for shadow instance SGALORG.ELG
    SGALORG.LOG
    DB_ACTION_GRANT < 1% SAP DB:
    Generates grant scripts SELTAB.LOG
    DBACTGRA.LOG
    SQLSCREXE_GRANT < 1% SAP DB:
    Grants privileges PTBALIGR.LOG
    SQLEXEGR.ELG
    SQLEXEGR.LOG
    SCEXEC_GRANT 1% Except SAP DB:
    Grants privileges SQLEXEGR.LOG
    SCEXEC_ALIAS 1% Creates aliases/views/synonyms SQLEXEAL.LOG
    SQLSCREXE_GRA_ORG < 1% Executes scripts for shadow instance ALORGR.LOG
    SEGRORG.ELG
    SEGRORG.LOG
    SQLSCREXE_ALI_ORG < 1% Executes scripts for shadow instance ALORDC.LOG
    SEDCORG.ELG
    SEDCORG.LOG
    SQLSCREXE_SEQ < 10s Creates sequence SEQUE.LOG
    SQLEXESE.ELG
    SQLEXESE.LOG
    VIEWIMP_BAS < 1% Creates views for the SAP Web Application Server VIEWIMP.ELG
    VIEWIMP.LOG
    TR_TRK2HEAP_INIT < 10s Copies requests to the R3up buffer TRSHDIN.LOG
    TP_ACTION_CP2SINI < 1% Copies a small number of control entries to shadow tables CP2SHDI.ELG
    CP2SHDI.LOG
    SHADOW_NTACT_DEL < 1% Deletes nametabs of shadow tables in the shadow nametab NTSHDDEL.ELG
    NTSHDDEL.LOG
    SQLDB_SHDI_DOC31I_OFF1 < 1% For start releases up to 31I:
    enabling of shadow import for docu objects, special handling startrelease 3.1I SHDI_DOC31I.LOG
    EXEC_SMOFF_SHD < 10s Switches off the Session Manager for the upgrade EXECSMF.LOG
    JOB_GN_BEF_UPG_CRM40_2 < 1% Strategy Resource-minimized, as of start release 610:
    Performs consistence check MWCRM2.ELG
    MWCRM2.LOG
    JOB_MC01_CACL_CDP_POST2 < 1% For start releases up to 610, strategy Resource-minimized:
    Performs consistence check CDPCON2.ELG
    CDPCON2.LOG
    REQSTOPPROD < 1% Strategy Resource-minimized:
    Stops production operation Confirm R3up prompt
    JOB_BTCTRNS2 < 1% As of start release 45A, strategy Resource-minimized:
    Deschedules background jobs BTCTRNS1.ELG
    BTCTRNS1.LOG
    UCMIG_STATUS_CHK22 < 10s Strategy Resource-minimized:
    Check status of Unicode Conversion Preparations on the start release UCMIGCHKSTAT2.LOG
    UCMIG_STATUS_CHK23 < 10s Strategy Downtime-minimized:
    Check status of Unicode Conversion Preparations on the start release UCMIGCHKSTAT2.LOG
    REQSTOP_APO2 dial Strategy Resource-minimized:
    Prompts, if system may be stopped Confirm, that the system may be stopped
    LOCKSYS_APO2 < 1% Strategy Resource-minimized:
    Locks SAP system for user access LOCKSYSAPO.LOG
    STOPSAP_LCD2 < 1% Strategy Resource-minimized:
    Stops SAP system Isolate the central instance and stop all application servers
    STARTSAP_LCD2 < 1% Strategy Resource-minimized:
    Starts SAP system
    REQ_APOUPG2 dial Strategy Resource-minimized:
    Prompts to save the live cache Save the live cache: follow the instructions given in the manual
    JOB_DROP_TMPOBJ_UPG1 < 1% Strategy Resource-minimized:
    Deletes temporary BW objects RSDR_NAMT_CL.ELG
    RSDR_NAMT_CL.LOG
    JOB_SDLINIT_TABLES_UPG1 < 1% Strategy Resource-minimized, as of start release 620:
    Deletes invalid nametab entries RSSM_SDLINIT.ELG
    RSSM_SDLINIT.LOG
    JOB_RDDPURIF_R < 1% Strategy Resource-minimized:
    Deletes inconsistent values from tables PDDPURIF.ELG
    PDDPURIF.LOG
    JOB_KEYIDX1_R < 1% Strategy Resource-minimized, MSSQL, for start releases up to 45B:
    Component-specific actions RKEYIDX1.ELG
    RKEYIDX1.LOG
    JOB_RSVBCHCK_R < 1% Strategy Resource-minimized:
    Checks whether outstanding updates tasks and queued RFCs exist PSVBCHCK.ELG
    PSVBCHCK.LOG
    Check outstanding update tasks with transaction SM13 and queued RFCs with transaction SMQ1
    INTCHK_SW < 1% Checks whether the inactive nametab is empty
    SETSYNC_PREUP_FINI_R2 dial Strategy Resource-minimized:
    events for sync with Jump
    GETSYNC_PREUP_FINI_R2 dial Strategy Resource-minimized:
    events for sync with Jump
    SETSYNC_DOWN_START_R2 dial Strategy Resource-minimized:
    events for sync with Jump
    STOPSAP_PROD < 1% Strategy Resource-minimized:
    Stops the production system
    Upgrade Phase Group: Shadow System Operations: SPDD and Activation
    Phase Duration Upgrade Actions Log Files User Actions
    CONFCHK_BAS < 1% Tests operating system and database version
    SHD_FIX_IMP < 1% Imports repair requests for shadow system SHD_FIX.ELG
    PORT_IMP_SHD < 1% Transports add-on-specific imports into the shadow system PORT_SHD.ELG
    SHDINST_CHK2 < 1% Checks the shadow instance SHDINST_CHK2.LOG
    START_SHDI_FIRST < 1% Starts the shadow system DEVTRACE.LOG
    STARTSFI.LOG
    STOP_SHDI_SW1 < 1% Stops shadow instance STOPSHDI.LOG
    SETSYNC_PREUP_FINI_SW dial events for sync with Jump
    GETSYNC_PREUP_FINI_SW dial events for sync with Jump

  • Call HANA Procedure via AMDP

    Hi,
    I wrote a procedure on HANA and i want to call via AMDP. As i saw from examples, developers generally writing the content of the procedure here but i wnt to call pre-written HANAprocedure via here.
    Is it possible ?
    My scenario is like that;
    CLASS ZBPC_AMDP_TEST IMPLEMENTATION.
      METHOD RUN_PACKAGE BY DATABASE PROCEDURE FOR HDB
                            LANGUAGE SQLSCRIPT.
    call Z_SP_TEST(:IN_A, :IN_B, :IN_C, ET_DATA  )  with overview;
      ENDMETHOD.
    ENDCLASS.
    I dont want to put all my select statement here and also it doesnt support local temporary tables.
    Is there a way ?

    Hi Bilen,
    how was the procedure Z_SP_TEST created? If...
    you (or your colleague) created it via CREATE PROCEDURE..., e.g. from the SQL console or via native SQL in the ABAP, you only have a catalog object residing in SAP<SID>. In this case you can not simply write the CALL in your AMDP. The reason is that the AMDP runtime either allows
    a. the usage of procedures residing in another database schema like SYS_BIC or MY_SCHEMA with a full qualified path name (as mentioned by Jens in his response at  Apr 10, 2014 4:05 PM) or
    b. the usage of other AMDPs, which reside in the SAP<SID> schema. In this case you have to mention the AMDP in the using clause and you have to omit the schema
    you (or your colleague) created the procedure as content object in the HANA database, you should have a catalog object already in the SYS_BIC schema and you can use this object in the AMDP.
    If the procedure is created via ADBC (or other native SQL tools), you rather create the procedure in a dedicated namespace like /1BCAMDP/ (namespace reserved for generated objects as in you example). However, as Jens already mentioned, you have to take care about the lifecycle of this generated object, i.e. you have to make sure that the generation is performed before you first call your AMDP (especially the target system), otherwise you'll get a runtime error when the AMDP is executed and you try to call the non-existing procedure Z_SP_TEST.
    Cheers,
      Jasmin

Maybe you are looking for

  • Sync no longer works on ipod

    up until 02nov13 i was able to sync without any hassles! however when i added new songs to specific playlist & did the sync process my ipod only shows the old playlist & not the new additions and/or new order of songs! tried to sync many times & read

  • Where do i get soap.jar file to download from ?

    I am writing a SOAP client class in java and am looking for a place where I can download soap.jar file. Can somebody inform where it is. Thanks

  • Adding last line to pdf form

    hi i am creating a pdf form and i want to add a signature box (it will appere empty and the user will have to fill it after he print the page ) only at the last page is there any way to do it ? thanks

  • Vertical alignment in text form

    Been trying set vertical alignment so that text will align with the top of the form box, and having a frustrating result. It will only align if the box is one line only. A multi-line box will not expand vertically to accomodate long text; an expanded

  • Sound and picture did not match?

    After recording the presentation it was OK and I could show it. But the fourth time I would show the presentation the sound and animation did not match the pictures? t.i. Keynote did not move to next picture (e.g. I was in picture No. 3 and it shoud