Support Packs installations

Support Packs
Support pack installations are mini-upgrades, the purpose of a Support Pack is to provide a bundle of fixes that have all been tested together. A Support Package corrects errors in the SAP System or makes necessary adjustments, for example, due to legal changes. The objects affected are replaced in your system.Each Support Package is valid for only one release (but for all databases and operating systems) and requires an exactly defined number of predecessors.

The following types of Support Packages are available:

• SPAM/SAINT Update: A SPAM/SAINT Update (PAT) contains updates and improvements to the SAP Patch Manager and the SAP Add-On Installation Tool.
• FCS Support Package: An FCS Support Package (FFD) updates an FCS system to its General Availability release so that other Support Packages can be imported.
• Component Support Package: This type of Support Package (COP) is valid for one software component (SAP_BASIS, SAP_HR, SAP_APPL) and contains corrections to errors in the Repository and Dictionary in this software component only.
• BW Support Package: A BW Support Package (BWP) is a Support Package for the software component SAP Business Information Warehouse (SAP_BW) and only contains corrections for this component.
• Add-On Support Package: An Add-On Support Package (AOP) is valid for an add-on with a particular release and contains corrections for this add-on.
• Conflict Resolution Transport: A Conflict Resolution Transport CRT is exclusively used for add-ons, for example, IS-IS or IS-OIL. It resolves conflicts that can occur between Support Packages and an add-on.

Before going to applying support packages you should follow the some prerequisites:

1. SPAM/SAINT should be latest version( always apply support packages to the level n-1)
2. No aborted packages in your system
3. Minimum two background work process are available
4. Free space in EPS directory
5. Must read the note for following sequence of support packs
6. Latest Kernel version (Upgrade "Kernel")

Update Saint Tool:

1. Download required version
2. Uncar and keep in eps/in
3. Go to SPAM
4. Go to Support Package
5. Click import saint/spam update
6. This step will take some time and then  click on green ok button
7. Some time it will throw error ….no need to worry just go to spam steps 5 again and the version will change  
8. http://www.sapbasistuts.com/home/abap-stack/abap-stack-wiki/sap-spam-saint-update

SPAM Steps 
The SAP Patch Manager informs you of the status of the step currently being executed in the status bar. If you want to know which steps are executed for which scenario, run the program RSSPAM10.
The following list explains the steps executed by SPAM in the order in which they are performed.
1.PROLOGUE: In this step, the system checks if you are authorized to import Support Packages.
2.CHECK_REQUIREMENTS: In this step, various requirements are checked for importing a Support Package, for example, the transport control program tp logging on to your system.
3.DISASSEMBLE: In this step, files from the corresponding EPS parcels are disassembled, or unpacked, and stored in the directory.
4.ADD_TO_BUFFER: In this step, the queue is put into the transport buffer of your system.
5.TEST_IMPORT: In this step, the system checks if there are still objects in tasks that have not yet been released and are overwritten when the Support Package is imported.
6.IMPORT_OBJECT_LIST: In this step, the object lists for the Support Packages in the queue are imported into the system.
7.OBJECTS_LOCKED_?: In this step, the system checks if there are still objects in tasks that have not yet been released and are overwritten when the Support Package is imported.
8.SCHEDULE_RDDIMPDP: In this step, the transport daemon (program RDDIMPDP) is scheduled.
9.ADDON_CONFLICTS_: In this step, the system checks if there are conflicts between objects in the queue and installed add-ons.
10.SPDD_SPAU_CHECK: In this step, the system checks if a modification adjustment is necessary (Transactions SPDD/SPAU).
11.DDIC_IMPORT: In this step, all the ABAP Dictionary objects of the queue are imported.
12.AUTO_MOD_SPDD: In this step, the system checks if modifications to the ABAP Dictionary objects can be adjusted automatically.
13.RUN_SPDD_: In this step, you are asked to adjust your modifications to the ABAP Dictionary objects by calling Transaction SPDD.
14.IMPORT_PROPER: In this step, all the Repository objects and table entries are imported. Then actions such as distribution, conversion, activation and generation occur.
15.AUTO_MOD_SPAU: In this step, the system checks if modifications can be adjusted automatically.
16.RUN_SPAU_: In this step, you are asked to adjust your modifications to the Repository objects by calling Transaction SPAU.
17.EPILOGUE: In this step, the import of the Support Package is ended. The system checks if the queue has been completely processed.

• Log files will be under /usr/sap/trans/log. Log files are not created for all the phases.
• If you want to know which steps are executed for which scenario, run the program RSSPAM10 

Steps to applying SAP Support packages

1. Login from DDIC and enter Tcode SPAM, Click on Package level to know the existing level of the support packs and the add-ons.
2. Go to transaction SPAM and Load the support packages from frontend if it is < 10 MB. The support packages which are in the form of .car will be decompressed into eps/in directory.  
3. If the size is > 10mb, copy the support packages to /trans directory and uncar the support packages using the below command 
4. cmd>cd usr\sap\trans
5. sapcar –xvf .car
6. The command SAPCAR will decompress the CAR file and put two files (with extensions .ATT and .PAT in the /usr/sap/trans/EPS/in directory.
7. Go to SPAM from DDIC and client 000 and click on Display/define A box will appear with the Support Package categories, Click on the category for the support packages that you uploaded and it will list them in order. You can apply them individually or the whole list at one time.
8. Go to support package click import queue (or) Click on truck icon.
9. Click on continue after importing in to the Queue.
10. Click Continue.

Note: - While applying support packages it triggers two phases SPAU and SPDD 

• SPDD

When the support packages contain any changes in the data dictionary then this phase is invoked.

• SPAU

When the support packages contain the changes related to repository objects SPAU phase is invoked.  it prompts whether to keep to existing changes modified by notes or adapt to changes.

Modification Adjustment during Import of Support Packages Use: - If SAP modified objects that have also been modified by the customer, a modification adjustment is executed in the transactions SPDD and SPAU during import of Support packages.

Procedure

• As far as the modification adjustment is concerned, you use the common procedure described below to import Support Packages:
• Create two change requests in the Workbench Organizer (transaction SE09), one for the modification adjustment with transaction SPDD and the other one for the modification adjustment in transaction SPAU.
• Create a task for each developer who is involved in the modification adjustment.
• The developers must use transactions SPDD and SPAU to determine whether to retain or delete the modifications.
• After modification adjustment is finished, the developers must release their tasks.
• Use transaction SPAM to access the SAP Patch Manager.
• Choose Patch -> Import Patch Queue. A confirmation dialog window appears.
• Choose Enter to finish the import process of the Support Package.
• Release the change requests that result from the modification adjustment using transactions SPAU and SPDD.

It prompts you the Queue is imported successfully and asks to confirm the queue.
Go to -> SPAM -> Support Package -> Confirm the Queue
This shows the support package has implemented for the one of the queue and you need to do the same as for the other queue (software components).

Post processing for support package 

1. Check if any alerts or error messages in SICK and SM21.
2. Release all the background jobs (BTCTRNS2).
3. Unlock all the users.
4. Run SGEN (SGEN compiles all programs.SGEN reduces abap load on the system).

ABAP Stack SP Upgrade:

1. Download required sp's from service marketplace.
2. Extract downloaded files to your "saptranshost"
3. Logon your system (client 000) with user that has "SAP-ALL" authorization.
4. Run transaction SPAM, define queue, and start import.

JAVA Stack SP Upgrade:

1. Download required sp's from marketplace.
2. Unpack the files or move them to the "saptranshost" depending of your release.
3. Run SAPINST or JSPM depending on your release.

ABAP+JAVA Dual Stack systems SP Upgrade:

• Patch ABAP Stack as described.
• Patch JAVA Stack as described.

Question and answer:
Q. When you will apply patches? Give short of examples the situation, where to troubleshoot you have applied patches!
Q.Why it`s required to shut down all SAP, Database instances & services during kernel up-gradation.
A. Because SAP system and database uses kernel service starsapsrv.exe for their functioning, if the service file to be updated is in use, kernel upgrade is not possible then. 
Q. Why it`s required to keep all instances up during the updating hot package?
A. Because SAP system process the system tables/object and modifying them during updating hot package besides hot packages are the most basis packages required for SAP system to work fine. 
Q. Can we apply higher version Patch Level using lower version of SPAM? 
A. NO
Q. What is importance of Import Queue?
Maintain the support packs selected. 
Check the dependency, actually queue can’t be defined unless the dependencies of selected components meet and let them apply in order. 
Q. Can we apply higher level of HR or other Financial Patch with lower version of ABAP/BASIS patch level?
A. Never. Because SAP Basis/ABAP are the most basic components that need to be updated before you can update any components. 
Q. Is there any sequence to apply hot packages?
A. Means, BASIS – ABAP – HR – FIN or HR – FIN – ABAP – BASIS vice versa Basis and ABAP should be at first then others. 
Q. BASIS and ABAP patch level should be same. So first which patch level should be updated ABAP or BASIS? If BASIS then why? If ABAP then why?
A. Not necessary for them to be at same patch level. Though standard says they should be at same level.  Generally we apply BASIS and ABAP together. If we have to apply one at first, it should be basis. 
Q. Why you update SPAM version before applying other patches? What is the logic behind this?
A. A SPAM/SAINT Update (PAT) contains updates and improvements to the SAP Patch Manager and the SAP Add-On Installation Tool. 
Q. How you will decompress the downloaded compressed patch files? After decompression what are the two files generated. State the names of that files & type of the files? 
A. SAPcar –xvf filename.sar
They will contain PTT and ATT files.
Q. Why we login as DDIC user at the time of patch administration? If we logged as different user, what will the problem?
A. Users are locked generally for SPAM upgrade. Hence use DDIC, its standard SAP user. 
Q. Updating the patch level means Updating of SAP system or Upgrading SAP system?
A. Updating the SAP system
Q. Why Support packages are required
A. A support packages is a quantity of corrected SAP objects.
Support packages are required to correct errors in various components. This is done by replacing erroneous objects with corrected versions of these objects.
Each software component has a separate sequence of Support Packages. 
Q. How from Client 000, all clients exists in SAP system get effected?  In which table these stored?
A. It updates standard table’s objects and data dictionary objects which are accessible by all the clients.

Knowledge Management - Introduction

With the Knowledge Management functional unit, SAP NetWeaver provides a central, role-specific point of entry to unstructured information from various data sources. This unstructured information can exist in different formats such as text documents, presentations, or HTML files. Workers in an organization can access information from different source such as file servers, their intranet, or the World Wide Web. A generic framework integrates these data sources and provides access to the information contained in them through the portal.

The Knowledge Management functional unit supports you in structuring information and making it available to the correct target audience. You can use the different functions on all content of integrated data sources, as long as the technical conditions are met.

• Knowledge Management is a part of SAP NetWeaver Enterprise Portal.
• The entire functional scope and configuration of the Knowledge Management capabilities are available in portal iViews.
• To run Knowledge Management, you also require the standalone engine Search and Classification (TREX).

Knowledge Management comprises the following functions:

Function	Description
Integrating Repositories	Unstructured information is stored in various types of repository such as file servers or document management systems. You can use preconfigured repository managers to integrate repositories and make their content accessible through a central entry point in the portal. Open programming interfaces (APIs) allow customers and partners to develop repository managers for other storage systems. You can also store documents in one of KM's own repositories.
Navigating in Folders	Portal users can navigate in the folders of all integrated repositories and access the documents they contain. Access to folders and documents is controlled using permissions. The user interface for navigating in folders can be configured flexibly and modified to suit various roles. Portal users can personalize the presentation of the user interface. Open interfaces allow you to extend the user interface by integrating your own functions into the standard system.
Search	The search function finds documents in all integrated repositories. The system displays only documents for which the current user has read permission in the results list. You can also include the content of Web sites in your indexes using Web crawlers. This information is then also available through the search function in your portal.
Taxonomies and classification	A taxonomy is a hierarchical structure of categories in which you classify documents according to content, organizational, or other criteria. Documents that are stored in different repositories can be included in the same category. Taxonomies portal users to navigate in a uniform structure throughout an organization even if information is stored in heterogeneous storage locations. After the initial configuration has taken place, the system automatically classifies new and changed documents.
Knowledge Management services	Knowledge Management services enable functions that you can use on the content of all connected repositories as long as technical conditions are met. These services include subscriptions, ratings, public reviews, feedback, and personal notes. You can also import documents into KM repositories from external sources by using the content exchange service.
Document creation and publishing	Every portal user can create information in the portal, provided he or she has the necessary permissions. You can upload documents that you created using a PC application directly to a KM folder. You can also use forms to create information directly in the Web browser. The publishing process is supported by various functions such as the approval workflow. You can assign metadata to documents and other objects to make the knowledge available in your company more usable.

Web Page Composer - Introduction

Web Page Composer is a tool for business users that facilitates the creation and management of portal pages that can combine business applications with user-generated Web content and static content. In this way, major content creation activities can be performed directly by business users, enabling IT personnel to focus on core tasks and innovation.

Web Page Composer provides an intuitive work environment that is fully based on standard portal capabilities. Applications and content can be integrated from SAP and non-SAP sources. Portal pages can be enriched with applications and user-generated, unstructured content such as articles, news, documents, and banners.

1. Administrators perform configuration tasks to set up and maintain Web Page Composer.

   .

2. Business users work in the Web Page Composer staging area to create and maintain areas and pages as well as the Web content that they can contain.

   
   

3. Developers can extend Web Page Composer capabilities. For example, you can enable connecting between content items in a page ("mashups"), extend the standard notification mechanism, or implement a custom content provider.

   
   

Client is not Available in this System

Symptom

You get an error " Client is not available in this system" when trying to login to the SAP system.

Solution

Login to the SAP system using client 000. Execute transaction code SCC4 to check all the client list that are available in the system.

Recommended Buffer Quality in SAP System

The following describes how the buffer quality of the SAP buffers should be in a SAP System with good performance.

Repository buffers (nametab buffers)

The qualities of the Repository buffers can reach 99.9% in a system that has been running for a few days. If the buffer quality is less than 95%, you should investigate the situation further. Check the:
• Available freespace
• Available directories
• Object swaps
• Buffer history

Program buffer

The program buffer contains the generated ABAP programs (load). Critical effects on the program buffer is transports. Every time a new source is transported into the system using the R3trans program, all entries in the program buffer are invalidated, and all other buffers are cleared (equivalent to the $SYNC command). Unlike the other buffers, the program buffer is not empty after transport, but is filled with invalid programs. Therefore, it is better to execute as few transports as possible and to collect data to do several transports at once.

Presentation and calendar buffers

The quality should also be above 95%. Also check available freespace and the freespace history.

Table buffers

The quality of the single key buffer increases very slowly from system startup. Therefore, bad quality (< 90%) should only be of concern if there is no freespace left in the buffer. The quality of the generic key buffer should be greater than 95% and can be up to 99%.

Known Errors in Support Package Manager

 

PROLOGUE

In this phase, a dialog box prompts you to confirm the import of the Support Package. If you are not authorized to use the Support Package Manager or the current queue has not yet been confirmed, the Support Package Manager stops with an appropriate message.

 

CHECK_REQUIREMENTS

This phase checks various requirements for importing a Support Package. This phase may terminate for the following reasons:

¡        TP_CANNOT_CONNECT_TO_SYSTEM: tp cannot log on to the database of the system.

¡        QUEUE_NOT_EMPTY: There are incompletely processed OCS requests in the tp buffer. Use the following tp command to display these requests:
     tp SHOWBUFFER <SID> -D SOURCESYSTEMS= TAG=SPAM
You can only continue to import the queue after these requests have been completely processed, or deleted from the tp buffer.

 

DISASSEMBLE

In this phase, files from the corresponding EPS parcels are unpacked and stored in the directory /usr/sap/trans/data (UNIX). It generates the command files (cofiles) from the accompanying files and saves them to the directory /usr/sap/trans/cofiles (UNIX). This phase may terminate for the following reasons:

¡        CANNOT_SKIP_ATTRIBUTE_RECORD: The attributes could not be read in the EPS parcel. The file cannot read, either because it has been deleted or you do not have the correct authorizations at the operating system level.

¡        CANNOT_DETERMINE_EPS_PARCEL: The EPS parcel is not in the EPS Inbox, because it may have been deleted. You must load the appropriate Support Package again.

¡        CANNOT_DETERMINE_DATA_FILES: The name of a data file could not be determined, because a profile parameter was not correctly configured. Use the report RSPARAM to check the settings.

¡        CANNOT_DISASSEMBLE_R_DATA_FILE: An R3trans data file could not be unpacked. Possible errors include a missing EPS parcel or a data file that could not be written to. An error occurred when transmitting a 20K block from the EPS Inbox to the directory /usr/sap/trans/data(UNIX).

¡        CANNOT_DISASSEMBLE_D_DATA_FILE: An ADO data file could not be unpacked. The reasons are the same as for CANNOT_DISASSEMBLE_R_DATA_FILE.

¡        CANNOT_CREATE_COFILE: The cofile could not be created from the corresponding data file. One possible error source is that <sid>adm does not have write authorization for the directory/usr/sap/trans/cofiles (UNIX). Check whether the data file was created. If it was not created, check that the option Create new data file is activated in the settings.

 

ADD_TO_BUFFER

This phase places the queue in the transport buffer of your system. This phase may terminate for the following reasons:

¡        TP_INTERFACE_FAILURE: The tp interface could not be called. There is an RFC error.

¡        CANNOT_ADD_PATCH_TO_BUFFER: A Support Package could not be included in the transport buffer. For more information, see the SLOG log file in the directory /usr/sap/trans/log(UNIX).

¡        CANNOT_MODIFY_BUFFER: An unsuccessful attempt was made to modify the transport buffer.

 

MODIFY_BUFFER

This phase prepares the transport buffer for correct processing of the following import phases. This phase may terminate for the following reasons:

¡        TP_INTERFACE_FAILURE: The tp interface could not be called. There is an RFC error.

¡        CANNOT_ADD_PATCH_TO_BUFFER: A Support Package could not be included in the transport buffer. For more information, see the SLOG log file in the directory /usr/sap/trans/log(UNIX).

¡        CANNOT_MODIFY_BUFFER: An unsuccessful attempt was made to modify the transport buffer.

 

TEST_IMPORT

This phase checks whether there are objects that are overwritten by the import, and that are still in unreleased tasks. You can find the source of error in the log of the test import.

You can skip test import errors and continue the import by choosing Extras ® Ignore Test Import Errors. However, depending on the type of error, this may cause the error to reappear during the real import with very serious consequences. For this reason, you must always check test import errors first, and correct them if possible.

                                                   

IMPORT_OBJECT_LIST

This phase imports the object lists for the Support Packages in the queue into the system. This phase may terminate for the following reasons:

¡        TP_INTERFACE_FAILURE: The tpinterface could not be called.

¡        TP_FAILURE: The program tp could not be executed. For more information, see the SLOG or ALOG log files.

¡        COMMAND_FILE_IMPORT_FAILURE: The object list for one or more Support Packages could not be imported. You can find the source of error in the log of the command file import.

 

OBJECTS_LOCKED_?

This phase checks whether there are objects that are overwritten by the import, and that are still in unreleased requests. This phase may terminate for the following reasons:

¡        CANNOT_GET_OBJECT_LIST: The object list for a Support Package could not be found, because the Support Package does not exist.

¡        CANNOT_CHECK_LOCKS: An error occurred when checking the locks of an object in the queue.

¡        OBJECTS_LOCKED_IN_REQUESTS: Objects were found that are still in requests that have not yet been released. Release these requests before you continue with the import of the Support Packages.

 

ADDON_CONFLICTS_?

This phase checks whether there are conflicts between objects in the queue and any installed add-ons. If there are any conflicts, the Support Package Manager stops and asks you to import the relevant Conflict Resolution Transports (CRTs). This phase may terminate for the following reasons:

¡        CANNOT_GET_OBJECT_LIST: The object list for a Support Package could not be determined, because the Support Package does not exist.

¡        CANNOT_GET_LAST_UPGRADE_INFO: The information about the component upgrade could not be determined.

¡        UNRESOLVED_ADDON_CONFLICTS: Conflicts with add-ons could not be resolved, because the relevant CRTs are missing from the queue.

 

SCHEDULE_RDDIMPDP

This phase schedules the transport daemon (program RDDIMPDP). This phase may terminate for the following reasons:

¡        CANNOT_SCHEDULE_RDDIMPDP: The job RDDIMPDP could not be scheduled. Call transaction SM37 (job selection), enter the following parameters and then choose Continue:

Job name	RDDIMPDP
User name	<User name>
Trigger event	SAP_TRIGGER_RDDIMPDP

Select the job that was terminated and display the job log.

¡        Problems with the SAP lock mechanism: Call transaction SM12 and make sure that there are no programs listed with the name RDDIMPDP.

 

CREATE_VERS_BEFORE

This phase creates versions in the version database of the objects that you want to import and of which versions can be created (ABAP coding, screens, and DDIC objects). This phase may terminate for the following reasons:

¡        TP_INTERFACE_FAILURE: The tpinterface could not be called.

¡        TP_FAILURE: The program tp could not be executed. For more information, see the SLOG or ALOG log files.

If the return code is 0152 (nothing done), check in the configuration of the transport tools in the Transport Management System (transaction STMS) whether the VERS_AT_IMP parameter is set asALWAYS. If this is not the case, set this value and then continue to import the queue.

¡        TP_STEP_FAILURE: The tp step CREATE_VERS_BEFORE could not be performed successfully. To find the exact cause of the error, choose Goto ® Log ® Queue, and look at the version log.

 

SPDD_SPAU_CHECK

In this phase, the system checks if a modification adjustment is necessary (transactions SPDD/SPAU).

 

DDIC_IMPORT

This phase imports the ABAP Dictionary. This phase may terminate for the following reasons:

¡        TP_INTERFACE_FAILURE: The tp interface could not be called.

¡        TP_FAILURE: The program tp could not be executed. For more information, see the SLOG or ALOG log files.

¡        CANNOT_IMPORT_DDIC: The ABAP Dictionary could not be imported. You can find the source of error in the Dictionary import log.

 

AUTO_MOD_SPDD

This phase checks whether all modifications to ABAP Dictionary objects can be adjusted automatically.

 

RUN_SPDD_?

In this phase, you are asked to adjust your modifications to the ABAP Dictionary objects by calling transaction SPDD.

 

LOCK_EU (only for import mode downtime-minimized)

This phase locks the development environment. This phase may terminate for the following reasons:

-          TP_INTERFACE_FAILURE: The tpinterface could not be called.

-          TP_FAILURE: The program tp could not be executed. For more information, see the SLOG or ALOG log files.

 

DDIC_ACTIVATION

This phase activates the imported ABAP Dictionary objects. This phase may terminate for the following reasons:

¡        TP_INTERFACE_FAILURE: The tp interface could not be called.

¡        TP_FAILURE: The program tp could not be executed. For more information, see the SLOG or ALOG log files.

¡        TP_STEP_FAILURE: The tp step DDIC_ACTIVATION could not be executed successfully. To view the cause of the error in the activation log, choose Goto ® Log ® Queue.
If you import two or more Support Packages in a queue, activation errors can result from an incorrect activation sequence for Dictionary objects. If this is the case, the activation errors disappear if the objects are activated again. To do this, choose Support Package ® Import queue.

 

 

INACTIVE_IMPORT (only for import mode downtime-minimized)

This phase imports program code and program texts in an inactive state. This phase may terminate for the following reasons:

-          TP_INTERFACE_FAILURE: The tpinterface could not be called.

-          TP_FAILURE: The program tp could not be executed. For more information, see the SLOG or ALOG log files.

-          TP_STEP_FAILURE: The tp step INACTIVE_IMPORT could not be executed successfully. The cause of the error is in the corresponding log (SAPBxxxxxx.<SID>). This log is in the log subdirectory of the transport directory. To display this file, execute treport RSPUTPRT, or call transaction AL11.

 

IMPORT_PROPER

This phase imports all Repository objects and table entries. This phase may terminate for the following reasons:

¡        TP_INTERFACE_FAILURE: The tpinterface could not be called.

¡        TP_FAILURE: The program tp could not be executed. For more information, see the SLOG or ALOG log files.

¡        TP_STEP_FAILURE: A tp step could not be performed successfully. You can find the source of error in the relevant log, for example, in the import log.

If a tp step 6, N or S is in the termination message, it is a step independent of the transport request. The corresponding logs are in the log overview are under the node Import steps not specific to the transport request.

You can also find these logs in the following files in the log subdirectory of your transport directory (usually /usr/sap/trans/log):

tp step 6: P<YY><MM><DD>.<SID>

tp step N: N<YY><MM><DD>.<SID>

tp step S: DS<YY><MM><DD>.<SID>

To display these files, execute treport RSPUTPRT, or call transaction AL11.

 

PREPARE_XPRA

This phase prepares the execution of the XPRAs and after-import methods. This phase may terminate for the following reasons:

¡        TP_INTERFACE_FAILURE: The tp interface could not be called.

¡        CANNOT_MODIFY_BUFFER: The tpprogram could not change the corresponding buffer file. For more information, see the SLOG log file.

 

UNLOCK_EU (only for import mode downtime-minimized)

This phase unlocks the development environment. This phase may terminate for the following reasons:

-          TP_INTERFACE_FAILURE: The tpinterface could not be called.

-          TP_FAILURE: The program tp could not be executed. For more information, see the SLOG or ALOG log files.

 

AUTO_MOD_SPAU

This phase checks whether modifications can be adjusted automatically.

 

XPRA_EXECUTION

This phase executes the XPRAs and after-import methods. This phase may terminate for the following reasons:

¡        TP_INTERFACE_FAILURE: The tpinterface could not be called.

¡        TP_FAILURE: The program tp could not be executed. For more information, see the SLOG or ALOG log files.

¡        TP_STEP_FAILURE: The tp step XPRA_EXECUTION could not be performed successfully. To find the cause of the error, see the method execution log. To view the cause of the error in the log, chooseGoto ® Log ® Queue.

¡        CANNOT_READ_BUFFER: The tp program could not open the corresponding buffer file. For more information, see the SLOG log file.

¡        CANNOT_MODIFY_BUFFER: The tp program could not change the corresponding buffer file. For more information, see the SLOG log file.

 

ABAP_GENERATION

This phase generates the runtime objects for the imported Repository objects (ABAP source texts and screens). This phase may terminate for the following reasons:

¡        TP_INTERFACE_FAILURE: The tpinterface could not be called.

¡        TP_FAILURE: The program tp could not be executed. For more information, see the SLOG or ALOG log files.

¡        TP_STEP_FAILURE: The tp step could not be executed successfully. To view the cause of the error in the generation log, choose Goto ® Log ® Queue.

 

Remember that objects delivered in Support Packages have already been imported completely. If the return code is 0008, all objects have been generated that contained no syntax errors.

There may be various reasons for any remaining syntax errors:

§         Systems that have been developed for a long period of time often contain many objects that are not longer used or maintained. These objects are still active in the Repository and can reference or use other objects (such as includes). If these includes are modified, syntax errors might occur in the obsolete objects. However, these errors have no effect on the SAP System, and can be ignored.

§         Generated includes or programs can contain syntax errors after an import. You can usually ignore these errors, since the source code of the generated objects is generated again when the corresponding transactions are started (a special generation transaction might exist).

§         If SAP objects have been modified, or if customer objects use SAP objects, there are may also be syntax errors in the modified SAP objects and the customer objects. If this is the case, you must adjust the modifications or customer developments.

§         Buffer synchronization problems can also cause generation errors. For more information, see SAP Note 40584.

Generation errors do not necessarily indicate inconsistencies in the system. However, you should investigate them using the criteria above. If the errors are non-critical, or temporary, ignore them by choosingExtras ® Ignore generation errors, and continue the import of the queue. Choose Support Package ® Import queue.

¡        CANNOT_READ_BUFFER: The tp program could not open the corresponding buffer file. For more information, see the SLOG log file.

¡        CANNOT_MODIFY_BUFFER: The tp program could not change the corresponding buffer file. For more information, see the SLOG log file.

 

RUN_SPAU_?

This phase prompts you to adjust your modifications to Repository objects by calling transaction SPAU.

 

CLEAR_OLD_REPORTS (only for import mode downtime-minimized)

This phase deletes the obsolete versions of program code and program texts from the system. This phase may terminate for the following reasons:

-          TP_INTERFACE_FAILURE: The tpinterface could not be called.

-          TP_FAILURE: The program tp could not be executed. For more information, see the SLOG or ALOG log files.

-          TP_STEP_FAILURE: The tp step CLEARREPORTS could not be performed successfully. The cause of the error is in the corresponding log (PZ<yy><mm><dd>.<SID>). This log is in the log subdirectory of the transport directory. To display this file, execute treport RSPUTPRT, or call transaction AL11.

 

EPILOGUE

This phase completes the import. The system checks if the queue has been completely processed. If the queue has been completely processed, there should be no more transport buffer entries for the queue. This phase may terminate for the following reasons:

¡        TP_INTERFACE_FAILURE: The tpinterface could not be called.

¡        TP_FAILURE: The program tp could not be executed. For more information, see the SLOG or ALOG log files.

¡        QUEUE_STILL_IN_BUFFER: The queue has not been processed completely, since there are still incomplete Support Packages of the queue in the transport buffer.