Manual de Aplicacao de Hot Packages

Cliente : Emissão :10/04/2023

Desenv. por:Syntacom

Aplicação:Produç. Iguaçú

Documento No : 003

Manual : Manual de Hot Package Versão3.0

Data24/11/99

StatusFinal Página: 1 de 25

Projeto

Responsável

Gerente de Consultoria

Aplicação de Hot Packages

Este documento estabelece as necessidades básicas para a aplicação de notas em um projeto de implantação SAP/R3, e os requisitos poderão ser revisados durante o projeto.É de responsabilidade do cliente prover os requisitos definidos abaixo, para o perfeito desenvolvimento do projeto.

Este documento destina-se exclusivamente a “Cliente”, para registro dos serviços executados pela SYNTACOM do Brasil Ltda. a esta empresa.É vedada a cópia ou distribuição de seu conteúdo, no todo ou parte, por qualquer processo ou meio, sem a expressa autorização da SYNTACOM do Brasil Ltda., bem como o uso para outros fins.

pág. 1/25

Fase 1

Logotipo do Cliente




Documento No : 003


Data24/11/99


Legal Change Patches (LCP)

LPC Number Aplicado por Data Instance

pág. 2/25




Documento No : 003


Data24/11/99


Procedimento instalação LCP / HP

ATENÇÃO

Antes da aplicação de qualquer Hot Package / LCP, é desejado que seja feito um Backup Full offline antes e depois da alteração. Certifique-se também de que não há nenhum usuário logado na máquina. (para travar/destravar a utilização da máquina, digitar tp locksys <SID> / tp unlocksys <SID>, respectivamente)

1) Verificar a versão corrente do SPAM (arquivo KD000018, versão XXXX). Se a versão instalada no sistema for antiga, fazer o Update da versão. Caso a versão seja atual, obter os arquivos LCP’s ou HP via Internet sapnet ou CD e executar os itens abaixo.

2) Entrar no sapserver e fazer download* da última versão dos arquivos: tp e R3trans. Atualizar no servidor, diretório: /sapmnt/<SID>/exe.

Verificar as versões / patch level dos arquivos:R3trans –vtp –v

*Para fazer o download dos arquivos, utilizar o procedimento: “Acesso ao SAPSERV4 para Download de arquivos.doc”.

3) Entrar no diretório /USR/SAP/TRANS/, copiar para esse diretório os arquivos dos LCP (*.CAR) e digitar: CAR –xvf < FILE.CAR >. Deste modo, o utilitário CAR descompactará os arquivos *.PAT e *.ATT para o diretório /usr/sap/trans/EPS/in.

4) Logar no Client 000, em inglês e com o usuário DDIC.

5) Entrar na Transação SPAM.

pág. 3/25




Documento No : 003


Data24/11/99


6) Entrar no menu PATCH -> UPLOAD

pág. 4/25




Documento No : 003


Data24/11/99


7) Mensagem: Want to Upload ? -> Dar enter8) Serão visualizados todos os LCP’s descompactados. Quando o utilitário CAR é

executado, ele coloca na memória do R/3 os pacotes não aplicados

ATENÇÃO

Devido ao grande número de alterações que a aplicação de Hot Packages/LCP’s efetuam, é desejado que o ARCHIVE LOG MODE seja desligado.

9) Selecione o pacote, clique em CHECK e depois EXECUTE.

10) Após o processamento, selecione PATCH -> APPLY -> QUEUE

pág. 5/25




Documento No : 003


Data24/11/99


ATENÇÃO

O R/3 apresentará uma mensagem que o LCP será aplicado com o Cenário S. Isto significa que ele aplicará totalmente o LCP. Para fazer um teste antes, modifique no menu EXTRAS -> SETTINGS -> SCENARIO para a opção T. Deste modo, será realizado um teste. Para aplicar efetivamente, volte o cenário para S.

11) O LCP será aplicado. Este processamento poderá demorar de 40 minutos até 2 horas. Se ocorrerem problemas, verifique as observações abaixo, juntamente com o Log de erro apresentado na SPAM.

12) Caso a aplicação seja efetuada com sucesso, o status da SPAM ficará amarelo. Selecione PATCH -> CONFIRM para confirmar a aplicação. Neste momento, o sinal ficará verde.

13) Verifique os logs. Caso haja Warnings (tp code 0004) não se preocupe.

Undo – disaplying Hot Packages

- Entre no menu DETAILS -> UNDO. ATENCAO: pacotes confirmados não podem ser desaplicados.

PROBLEMAS ENCONTRADOS NA APLICAÇÃO DE LCP’S

- Programas em Repair

Quando existem programas em Repair, as tabelas Oracle relacionadas com este programa ficam com status LOCKED. Neste caso não é possível aplicar o LCP, pois o mesmo tenta modificar uma tabelas que já está sendo modificada.

O seguinte procedimento pode ser efetuado:

pág. 6/25




Documento No : 003


Data24/11/99


1) Verifique no log de erro da SPAM que tabelas estão locadas (mensagem exemplo R3TRFUGRMR1M was repaired in this system)

2) Entre na transação SM313) Digite no campo TABLE a tabela TADIR4) No campo REPAIR FLAG, digite R e depois EXECUTE5) O R/3 exibirá todas as tabelas com status R (Repair). Verifique qual CR está

associada pelo SINTESE DO OBJETO.6) Dê release nas Change Requests. ATENCAO: o status de repair das CR’s tem

que estar CONFIRMED.

pág. 7/25




Documento No : 003


Data24/11/99


- Erro: Table XXXX não está totalmente aplicada

No log de erro da SPAM é apresentado um erro que a table X não pode ser alterada por não estar totalmente ativada.

1) Verifique o nome das tabelas no log de erro2) Entre na SE113) Digite o nome da tabela4) Clique em CHANGE5) Verifique o campo STATUS. Entre no menu TABLE -> ACTIVATE.6) Continue a aplicacao do LCP

- Error CANNOT_ANALYSE_EXPORT_RC

Ver nota 114.298. (criar e executar programa específico)

pág. 8/25




Documento No : 003


Data24/11/99


Veja também

- Veja nota 33525, 104465, 84962, 97660, 97630, 82264, 104128, 104664, 63974.

SPAM Update Patch

With SPAM updates, you can obtain improvements to the SAP Patch Manager. As with Hot Packages, you can download SAP updates from OSS and SAPNet.

To apply a SPAM update, choose: Patch-> Apply -> SPAM update

You can obtain the appropriate logs with Goto -> Log -> SPAM update

You can obtain the status with Goto -> Status -> SPAM update

SPAM updates are confirmed automatically once they have been applied successfully.SAP Patch Manager Updates follow the same naming convention:

SAPKD<fixed number> For example, SAPKD00013 only applies to a 3.1H R/3 release.

The SAP Patch Manager Update patch is available for SAP R/3 Release 3.1H and higher.

pág. 9/25




Documento No : 003


Data24/11/99


Informações sobre SPAM na Internet (Sapnet)

SPAM StepsSPAM 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 shows and 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 apply patches.

2. CHECK_REQUIREMENTS In this step, various requirements are checked for applying a patch, for example, the transport control program tp logging on to your system.

3. DISASSEMBLE In this step, files from the corresponding EPS parcels are unpacked and stored in the directory.

4. ADD_TO_BUFFER

In this step, the patch 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 patch is applied.

6. IMPORT_OBJECT_LIST In this step, the object lists for the patches in the queue are imported in 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 patch is applied.

8. SCHEDULE_RDDIMPDP In this step, the transport daemon (program RDDIMPDP) is scheduled.

9. GENERATE_BACKUP In this step, a backup copy of the objects is generated that are overwritten when the patch is applied.

10. ADDON_CONFLICTS_? In this step, the system checks if there are conflicts between objects in the patch queue and installed add-ons.

11. SPDD_SPAU_CHECK In this step, the system checks if a modification adjustment is necessary (Transactions SPDD/SPAU).

12. DDIC_IMPORT In this step, all the ABAP Dictionary objects of the ptach queue are imported.

pág. 10/25




Documento No : 003


Data24/11/99


13. AUTO_MOD_SPDD In this step, the system checks if modifications to the ABAP Dictionary objects can be adjusted automatically.

pág. 11/25




Documento No : 003


Data24/11/99


14. RUN_SPDD_? In this step, you are asked to adjust your modifications to the ABAP Dictionary objects by calling Transaction SPDD.

15. IMPORT_PROPER In this step, all the Repository objects and table entries are imported. Then actions such as distribution, conversion, activation and generation occur.

16. AUTO_MOD_SPAU In this step, the system checks if modifications can be adjusted automatically.

17. RUN_SPAU_? In this step, you are asked to adjust your modifications to the Repository objects by calling Transaction SPAU.

18. EPILOGUEIn this step, the patch application is ended. The system checks if the patch queue has been completely processed.

TroubleshootingWhile the patch is being applied, the SAP Patch Manager goes through various steps. If errors occur, SPAM terminates the process to ensure the consistency of the application. After you have corrected the error, you can continue applying the patch. If the process terminates, a dialog box appears informing you at which step and why the process was terminated.You can also get to this dialog box by choosing Goto Status ...( Display Patch Status) Depending on the step where the error occurred, you receive more specific help on how to correct the problem.You may also have to Reset the Patch Status.NoteIf you have any problems downloading patches from OSS, refer to the R/3 Note 34376.If problems occur while working with SPAM, refer to Note 97630, which gives you an overview of known problems and their solutions.You can find a list of the most important Notes from the Online Correction Support (OCS) in Note 97620, which is regularly updated.If you cannot solve your problem using these Notes or with the following information, send a an error message in OSS using the information from the error dialog box and send it to the component BC-UPG-OCS. Also look at Note 97660 when creating your error message.See also:Errors at GenerationErrors in SPAM Steps

pág. 12/25




Documento No : 003


Data24/11/99


pág. 13/25




Documento No : 003


Data24/11/99


Displaying the Patch StatusUseYou can display the status of the patch application and the patch status of your system.

ProcedureDisplaying the Application StatusTo display the patch application status, choose Goto Status. A dialog pox appears telling you if the patch was applied successfully.Displaying the Patch Status of the SystemTo display the patch status of your system, under Directory select one of the following checkboxes:

New patches (have not been applied yet) Aborted patches (have not been successfully applied) Applied patches (have been successfully applied) All patches

A list is displayed with information about the selected patches. For more information on the patches displayed, choose View Change view.

GenerationUseFor performance reasons, SPAM is set up by default so that no generation can occur when a patch is being applied. The relevant programs are generated only when they are called. However, you can set up SPAM so that generation does occur when a patch is being applied.SPAM may return error messages during generation, for example, because a report written by the customer or a modification of an existing report has incorrect syntax and refers to an object that is applied as part of the patch queue.

pág. 14/25




Documento No : 003


Data24/11/99


It is usually best to ignore the generation error at first and then correct it after the patch has been applied.

pág. 15/25




Documento No : 003


Data24/11/99


RequirementsYou are able to apply patches.

ProcedureSwitching Generation On and OffTo switch on or off generation, choose Extras Settings.Ignoring Generation ErrorsTo ignore the generation errors when the patch is applied, choose Extras Ignore gen. errors.

Errors in SPAM StepsIf an error is recognized in a step, the SPAM transaction stops the processing until the error is corrected. You can get information about the reason the SPAM transaction was stopped and in which step by choosing Status.Error TypesHere are the following types of error messages:

1. Security checks for transaction SPAM A typical example is the step OBJECTS_LOCKED?. If objects are still locked requests that should be overwritten by the patch queue, the SPAM transaction stops processing.

2. Error messages from the programs tp and R3trans You can always find the cause of the error in the relevant transport log. A typical example is the step TEST_IMPORT. A check is made whether there are unconfirmed repairs to objects that should be overwritten by the patch queue. The relevant objects are listed in the test import log.

3. Incorrect setup of the transport system.Often the errors here are not having the relevant authorizations to files of the transport system, or using old program versions of tp or R3trans . Check the correct function of the transport tools by choosing Utilities Check transport tools.A typical example is the step DISASSEMBLE. If <sid>adm does not have write authorization for

the directory /usr/sap/trans/data (UNIX), SPAM stops at the step DISASSEMBLE with

CANNOT_DISASSEMBLE_R_DATA_FILE .The SPAM transaction requires that the Workbench Organizer (WBO) and the transport system are set up. You can find more information on this topic under BC Change and Transport Organizer.

pág. 16/25




Documento No : 003


Data24/11/99


You can find more information on known problems in the Notes 97630 and 97620.

pág. 17/25




Documento No : 003


Data24/11/99


Known ProblemsPROLOGUEIn this step, you are asked via a dialog box to confirm the patch application. If you are not authorized to execute the SPAM transaction or the current patch queue has not yet been confirmed, the SPAM transaction is stopped with a corresponding message.CHECK_REQUIREMENTSIn this step, various requirements for the patch application are checked. The following messages explain why this step may be terminated:

TP_CANNOT_CONNECT_TO_SYSTEM : tp cannot log onto the system’s database.DISASSEMBLEIn this step, files from the corresponding EPS parcels are unpacked and stored in the directory /usr/sap/trans/data (UNIX). The command files (cofiles) from the accompanying files are

generated and are stored in the directory /usr/sap/trans/cofiles (UNIX). The following messages explain why this step may be terminated:

CANNOT_SKIP_ATTRIBUTE_RECORD : The attributes could not be read in the EPS parcel. The file cannot be opened for reading, because it may have been deleted in the meantime.CANNOT_DETERMINE_EPS_PARCEL : The EPS parcel is not in the EPS Inbox, because it

may have been deleted. You must download the relevant patch again (for example, Hot Package).CANNOT_DETERMINE_DATA_FILES : The name of a data file could not be determined,

because a profile parameter was not correctly configured. Check the settings using the report RSPARAM.CANNOT_DISASSEMBLE_R_DATA_FILE : An R3trans data file could not be unpacked. A

possible error source is that the relevant EPS parcel was not found. The data file could not be opened for writing. 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 with the message CANNOT_DISASSEMBLE_R_DATA_FILE .CANNOT_CREATE_COFILE : The cofile could not be created from the relevant data file. One

possible error source is that <sys>adm does not have write authorization for the directory

/usr/sap/trans/cofiles (UNIX). You can find more information on this topic in Note 70752.ADD_TO_BUFFERIn this step, the patch queue is put into the transport buffer of your system. The following messages explain why this step may be terminated:

TP_INTERFACE_FAILURE : The tp interface could not be called. There is an RFC error.CANNOT_ADD_PATCH_TO_BUFFER : A patch could not be included in the transport buffer. You can find more information in the SLOG system 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

pág. 18/25




Documento No : 003


Data24/11/99


In this step, the system checks if there are still objects in tasks which have not yet been released and are overwritten when the patch is applied. You can find the source of error in the log of the test import. For further information, see the Note 42379.IMPORT_OBJECT_LISTIn this step, the object lists for the patches in the queue are imported in the system. The following messages explain why this step may be terminated:

pág. 19/25




Documento No : 003


Data24/11/99


TP_INTERFACE_FAILURE : The tp interface could not be called.TP_FAILURE : The program tp could not be executed. You can find more information in the SLOG and/or the ALOG log file.COMMAND_FILE_IMPORT_FAILURE : The object list for one or several patches could not be

imported. You can find the source of error in the log of the command file import.OBJECTS_LOCKED_?In this step, the system checks if there are still objects in requests that have not yet been released and are overwritten when the patch is applied. The following messages explain why this step may be terminated:

CANNOT_GET_OBJECT_LIST : The object list for a patch could not be found, because the patch does not exist.CANNOT_CHECK_LOCKS : An error occurred when checking the locks of an object in the patch queue.OBJECTS_LOCKED_IN_REQUESTS : Objects were found that are still in requests that have

not yet been released. Before continuing with applying the patch, release these requests.SCHEDULE_RDDIMPDPIn this step, the transport daemon (program RDDIMPDP) is scheduled. The following messages explain why this step may be terminated:

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 RDDIMPDPUser name <User name>Trigger event SAP_TRIGGER_RDDIMPDP

Select the job that was terminated and display the job log.Problems with the SAP locking mechanism: Call Transaction SM12 and ensure that there are no programs listed with the name RDDIMPDP. For further information, see the Note 11677.

GENERATE_BACKUPIn this step, a backup copy of the objects is generated that are overwritten when the patch is applied. The following messages explain why this step may be terminated:

CANNOT_FIND_BACKUP : Using the first patch in the patch queue, it is determined whether a

backup already exists. If the step is terminated, the patch does not exist. Therefore the backup cannot be determined.CANNOT_CREATE_EMPTY_BACKUP : An unsuccessful attempt was made to generate a backup.CANNOT_COPY_PATCH_TO_BACKUP : For each list in the patch queue, the object list is

copied to the backup. This action terminates for a particular patch.CANNOT_SORT_N_COMPRESS_BACKUP : The complete object list in the backup is sorted and

compressed before the export. An error occurred here.CANNOT_EXPORT_BACKUP : The backup could not be exported successfully. The reason for

the step being terminated is in the message that tp returns to the SAP Patch Manager.CANNOT_ANALYSE_EXPORT_RC : The tp return code could not be analyzed successfully.

pág. 20/25




Documento No : 003


Data24/11/99


CANNOT_ADD_BACKUP_TO_BUFFER : After the backup has been generated, it is saved to the

SAP transport buffer to protect it from being unintentionally deleted. The reason for the step being terminated is in the message that tp returns to the SAP Patch Manager.

ADDON_CONFLICTS_?In this step, the system checks if there are conflicts between objects in the patch queue and installed add-ons. If there are any conflicts, SPAM terminates and asks you to import the relevant Conflict Resolution Transports (CRTs). The following messages explain why this step may be terminated:

pág. 21/25




Documento No : 003


Data24/11/99


CANNOT_GET_OBJECT_LIST : The object list for a patch could not be determined, because the patch does not exist.CANNOT_GET_LAST_UPGRADE_INFO : The information about the last Repository switch upgrade could not be determined.UNRESOLVED_ADDON_CONFLICTS : Conflicts with add-ons could not be resolved, because the relevant CRTs are missing from the patch queue.

SPDD_SPAU_CHECKIn this step, the system checks if a modification adjustment is necessary (Transactions SPDD/SPAU).DDIC_IMPORTIn this step, the ABAP Dictionary is imported. The following messages explain why this step may be terminated:

TP_INTERFACE_FAILURE : The tp interface could not be called.TP_FAILURE : The program tp could not be executed. You can find more information in the SLOG and/or the ALOG log file.CANNOT_IMPORT_DDIC : The ABAP Dictionary could not be imported. You can find the source of error in the Dictionary import log.

AUTO_MOD_SPDDIn this step, the system checks if modifications to the ABAP Dictionary objects can be adjusted automatically.RUN_SPDD_?In this step, you are asked to adjust your modifications to the ABAP Dictionary objects by calling Transaction SPDD.IMPORT_PROPERIn this step, the Repository including all table entries is imported The following messages explain why this step may be terminated:

TP_INTERFACE_FAILURE : The tp interface could not be called.TP_FAILURE : The program tp could not be executed. You can find more information in the SLOG and/or the ALOG log file.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 or generation log. If the generation is terminated ( tp step G), you can correct the error either immediately or after the patch has

been applied. In the second case, you must perform the following steps:1. To ignore the generation errors, choose Extras Ignore gen. errors.2. Continue applying the patch.

Generation errors can also be caused by buffer synchronization problems. For further information, see the Note 40584.If a tp step is listed in a termination message, it concerns a step that is independent of the

transport request. The step’s log cannot be displayed using the pushbutton Log. In this case, analyze the following files:tp step 6: P<YY><MM><DD>.<SID>tp step N: N<YY><MM><DD>.<SID>tp step S: DS<YY><MM><DD>.<SID>All the logs are located in /usr/sap/trans/log . You can display them using the report RSPUTPRT or Transaction AL11.

pág. 22/25




Documento No : 003


Data24/11/99


AUTO_MOD_SPAUIn this step, the system checks if modifications can be adjusted automatically.

pág. 23/25




Documento No : 003


Data24/11/99


RUN_SPAU_?In this step, you are asked to adjust your modifications to the Repository objects by calling Transaction SPAU.EPILOGUEIn this step, the patch application is ended. The system checks if the patch queue has been completely processed. In this case, there should be no more transport buffer entries for the queue. The following messages explain why this step may be terminated:

TP_INTERFACE_FAILURE : The tp interface could not be called.TP_FAILURE : The program tp could not be executed. You can find more information in the SLOG and/or the ALOG log file.QUEUE_STILL_IN_BUFFER : The patch queue is not fully processed, because incomplete patches of the queue are still in the transport buffer.CANNOT_RESET_FCS_FLAG : If an FCS Final Delta Patch (FFDP) is in the patch queue, the

system is marked as Final State after the patch is applied. In this case, this operation could not be successfully performed.

Resetting the Patch StatusUseIf you have to reapply a patch because errors occurred or a SPAM update is necessary, then reset its status.

Resetting the status does not mean that the system has the old status.

ProcedureTo reset a patch or a patch queue, choose Extras Reset status.

Result

pág. 24/25




Documento No : 003


Data24/11/99


The corresponding entries are deleted in the cofile and in the log file after the status has been updated. You have to completely apply the patch again. Transaction SPAM starts the application with the step CHECK_REQUIREMENTS.

pág. 25/25

Documents

Manual de Aplicacao de Hot Packages