SAP - Edit registry of table

Old School Way:

1. SE11 --> Utilities --> Table Content --> Display the record --> Double Click --> Turn on debugging using "/H" --> Change the code to "DELE".

New School Way:

1. SE16N --> Table Name (from which data needs to be deleted) --> Use the t-code "&SAP_EDIT" & press enter --> Choose the entry to be deleted & press the "Delete" icon.

Mais informações

Brbackup - ORA-01017

Problema

BR0051I BRBACKUP 7.40 (22)

BR0055I Start of database backup: betuhkhq.anf 2016-08-08 14:52:38

BR0484I BRBACKUP log file: /oracle/TST/sapbackup/betuhkhq.anf

BR0280I BRBACKUP time stamp: 2016-08-08 14:52:39

BR0301E SQL error -1017 at location BrDbConnect-3, SQL statement:

'CONNECT /'

ORA-01017: invalid username/password; logon denied

BR0310E Connect to database instance TST failed

BR0280I BRBACKUP time stamp: 2016-08-08 14:52:39

BR0301E SQL error -1017 at location BrDbConnect-3, SQL statement:

'CONNECT /'

ORA-01017: invalid username/password; logon denied

BR0310E Connect to database instance TST failed

Mais informações

SCU0 - Table Comparison

Solução

https://scn.sap.com/docs/DOC-46814

DTecno Consultoria SAP - Suporte SAP Remoto sob Demanda

Keywords: Consultoria SAP, Consultor SAP, SAP Remoto, SAP Basis, Suporte SAP Remoto, SAP FI, Consultor FI, Consultor MM, SAP MM

Mais informações

ORA-00059: maximum number of DB_FILES exceeded

Problema

BR0280I BRSPACE time stamp: 2015-06-01 11:15:55

BR1088I Extending tablespace PSAPBTABI ...

BR0280I BRSPACE time stamp: 2015-06-01 11:16:34

BR0301E SQL error -59 at location BrSqlExecute-1, SQL statement:

'/* BRSPACE */ alter tablespace PSAPBTABI add datafile '/oracle/TST/sapdata4/btabi_28/btabi.data28' size 5000M autoextend on next 20M maxsize 6000M'

ORA-00059: maximum number of DB_FILES exceeded

BR1017E Execution of SQL statement '/* BRSPACE */ alter tablespace PSAPBTABI add datafile '/oracle/TST/sapdata4/btabi_28/btabi.data28' size 5000M autoextend on next 20M maxsize 6000M' failed

BR0280I BRSPACE time stamp: 2015-06-01 11:16:34

BR0669I Cannot continue due to previous warnings or errors - you can go back and repeat the last action

BR0671I Enter 'b[ack]' to go back, 's[top]' to abort:

Referencia

398927 - ORA errors because dimensions of parameters are too small

8812 - Increasing max. number of data files in Oracle

https://community.oracle.com/thread/434447

Solução

You do not need to recreate control file. See below:

SQL> sho user
SYS
SQL> select * from v$version;

BANNER

--------------------------------------------------------------------------------

Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production

PL/SQL Release 11.2.0.3.0 - Production

CORE    11.2.0.3.0      Production

TNS for IBM/AIX RISC System/6000: Version 11.2.0.3.0 - Production

NLSRTL Version 11.2.0.3.0 - Production

SQL> sho parameter db_files

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
db_files integer 200
SQL> alter system set db_files = 512 scope = spfile;

SQL> shutdown immediate
SQL> startup
SQL> sho parameter db_files

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
db_files integer 512

Mais informações

Terminal XXXXX in status DISC

Problema
- Na SM21.
Terminal 00075 in status DISC

Solução
- Verifique a conexão de rede do SAP Logon com o servidor.

DTecno Consultoria SAP - Suporte SAP Remoto sob Demanda

Keywords: Consultoria SAP, Consultor SAP, SAP Remoto, SAP Basis, Suporte SAP Remoto, SAP FI, Consultor FI, Consultor MM, SAP MM

Mais informações

ERROR: The executable R3trans in /usr/sap/SID/SUM/abap/exe is too old

Problema

ERROR: The executable R3trans in /usr/sap/<SID>/SUM/abap/exe is too old.
It needs a release date of 06.06.14 or later.

Download the new tools according to SAP Note 19466 and put the archives into the download directory.

Solução

- Faça download da última versão do tp e do R3trans.

- Deixe os arquivos *.SAR no diretório de download.

DTecno Consultoria SAP - Suporte SAP Remoto sob Demanda

Keywords: Consultoria SAP, Consultor SAP, SAP Remoto, SAP Basis, Suporte SAP Remoto, SAP FI, Consultor FI, Consultor MM, SAP MM

  

Mais informações

List all users from a specific profile

1- Access the SUIM tcode.

2- Open tree User

3- If your SAP system uses CUA, open Cross-System Information (Central User Administration), If doesn't, open Users by complex Selection Criteria

4- In both options, click on By Profiles

5- In the field Profile Name, insert the profile name

6- Execute (F8)

DTecno Consultoria SAP - Suporte SAP Remoto sob Demanda

Keywords: Consultoria SAP, Consultor SAP, SAP Remoto, SAP Basis, Suporte SAP Remoto, SAP FI, Consultor FI, Consultor MM, SAP MM

Mais informações

OCS Package XXXXXX, tp step "I" return code 0016

Problema 1

SQL error 24374 occured: ORA-24374: define not done before fetch or execute and fetch

Problema 2

The installation was stopped, since an error occurred during the phase

IMPORT_PROPER, which the Add-On Installation Tool is unable to resolve

without your input.

After you have corrected the cause of the error, continue with the

import by choosing Continue in the queue display.

The following details help you to analyze the problem:

    -   Error in phase: IMPORT_PROPER

    -   Reason for error: TP_STEP_FAILURE

    -   Return code: 0016

    -   Error message: OCS Package SAPK-10004INUIINFRA, tp step "I",

        return code 0016

Solução

- Aplique os últimos patches no kernel, incluindo o executável tp.

DTecno Consultoria SAP - Suporte SAP Remoto sob Demanda

Keywords: Consultoria SAP, Consultor SAP, SAP Remoto, SAP Basis, Suporte SAP Remoto

Fonte

- SAP Support

Mais informações

Outstanding DB conversions found

Issue

-No SUM, na fase Extraction

Conversion Check

WARNING: Outstanding DB conversions found:

Entry

ENQU/UI5/E_REP 0CNVI 20140728DDIC

Remove all converter entries as described in the guide and repeat this phase. 

Solution

Solution indicated for SUM version SP11. For older versions consult the correct update guide, in section Cleaning Up Terminated Conversions in the DB Conversion Phases

1. Determine the objects that are affected.

1. Start the database utility transaction (transaction SE14) and choose DB Requests Mass Processing .

2. Choose All requests.

The worklist of the conversion program appears. This worklist was generated by developments or modifications in your SAP system, but has not yet been processed.

3. Choose DB requests Created with import .

The worklist that was not processed correctly during the last update appears.

2. Check the meaning and status of the requests.

In contrast to the procedure for the message Restart logs of DB conversions found, this procedure can also include requests for indexes, views and matchcode objects. The requests that are found are not always terminated. They might not even have been started.

1. Ask the last person who changed the object if the request should still be processed.

2. If the user does not want it to be processed, select the request and choose Delete selected.

This removes the objects from the worklist of the conversion program.

Do not remove requests from the last update.

3. Process the outstanding requests.

You can select the requests from the list of mass processing requests and schedule a job for execution with the

function Schedule selections.

1. Go to the detailed display of the object by double-clicking it in the list of requests created by the import.

2. Schedule the request, or continue it. Since you do not know how long this takes, choose processing type Background.

DTecno Consultoria SAP - Suporte SAP Remoto sob Demanda

Keywords: Consultoria SAP, Consultor SAP, SAP Remoto, SAP Basis, Suporte SAP Remoto

Referencia

https://websmp201.sap-ag.de/~sapidb/011000358700000783632011E

Mais informações

Could not open the ICU common library

Problema 1 
SAPup> Starting subprocess with PID 9633946 in phase 'TOOLVERSION_UNI' at 20140730101422
    ENV: DIR_LIBRARY=/usr/sap/TST/DVEBMGS00/exe
    ENV: JAVA_HOME=/usr/java14_64
    ENV: LIBPATH=/usr/sap/TST/DVEBMGS00/exe:/usr/sap/TST/SUM/jvm/jre/lib/ppc64/server:/usr/sap/TST/SUM/jvm/jre/lib/ppc64:/usr/sap/TST/SU
M/jvm/jre/../lib/ppc64:/usr/sap/TST/SUM/jvm/jre/lib/ppc64/jli:/usr/sap/TST/SUM/jvm/jre/../lib/ppc64/jli:/usr/lib:/lib:/usr/sap/TST/SYS/e
xe/run:/oracle/client/11x_64/instantclient
    ENV: NLS_LANG=AMERICAN_AMERICA.UTF8
    ENV: ORACLE_BASE=/oracle
    ENV: ORACLE_HOME=/oracle/TST/112_64
    ENV: ORACLE_SID=TST
    ENV: PATH=/usr/sap/TST/DVEBMGS00/exe:/oracle/TST/112_64/bin:/usr/java14_64/bin:.:/home/tstadm:/usr/sap/TST/SYS/exe/run:/usr/bin:/etc
:/usr/sbin:/usr/ucb:/usr/bin/X11:/sbin:/usr/java5/jre/bin:/usr/java5/bin
    ENV: SAPDATA_HOME=/oracle/TST
    ENV: SAPSYSTEMNAME=TST
    ENV: dbms_type=ORA
    ENV: dbs_ora_schema=SAPSR3
    ENV: dbs_ora_tnsname=TST

EXECUTING /usr/sap/TST/DVEBMGS00/exe/tp  -V
Could not open the ICU common library.
   The following files must be in the path described by
   the environment variable "LIBPATH":
   libicuuc40.a, libicudata40.a, libicui18n40.a [nlsui0.c 1548] pid = 9633946
LIBPATH is currently set to /usr/sap/TST/DVEBMGS00/exe:/usr/sap/TST/SUM/jvm/jre/lib/ppc64/server:/usr/sap/TST/SUM/jvm/jre/lib/ppc64:/usr
/sap/TST/SUM/jvm/jre/../lib/ppc64:/usr/sap/TST/SUM/jvm/jre/lib/ppc64/jli:/usr/sap/TST/SUM/jvm/jre/../lib/ppc64/jli:/usr/lib:/lib:/usr/sa
p/TST/SYS/exe/run:/oracle/client/11x_64/instantclient  [nlsui0.c 1551] pid = 9633946
SAPup> Process with PID 9633946 terminated with status 255 at 20140730101422!

Problema 2
SAPup> Starting subprocess with PID 12320986 in phase 'TOOLVERSION_UNI' at 20140730110321
    ENV: DIR_LIBRARY=/usr/sap/TST/DVEBMGS00/exe
    ENV: JAVA_HOME=/usr/java14_64
    ENV: LIBPATH=/usr/sap/TST/DVEBMGS00/exe:/usr/sap/TST/SUM/jvm/jre/lib/ppc64/server:/usr/sap/TST/SUM/jvm/jre/lib/ppc64:/usr/sap/TST/SU
M/jvm/jre/../lib/ppc64:/usr/sap/TST/SUM/jvm/jre/lib/ppc64/jli:/usr/sap/TST/SUM/jvm/jre/../lib/ppc64/jli:/usr/lib:/lib:/usr/sap/TST/SYS/e
xe/run:/oracle/client/11x_64/instantclient
    ENV: NLS_LANG=AMERICAN_AMERICA.UTF8
    ENV: ORACLE_BASE=/oracle
    ENV: ORACLE_HOME=/oracle/TST/112_64
    ENV: ORACLE_SID=TST
    ENV: PATH=/usr/sap/TST/DVEBMGS00/exe:/oracle/TST/112_64/bin:/usr/java14_64/bin:.:/home/tstadm:/usr/sap/TST/SYS/exe/run:/usr/bin:/etc
:/usr/sbin:/usr/ucb:/usr/bin/X11:/sbin:/usr/java5/jre/bin:/usr/java5/bin
    ENV: SAPDATA_HOME=/oracle/TST
    ENV: SAPSYSTEMNAME=TST
    ENV: dbms_type=ORA
    ENV: dbs_ora_schema=SAPSR3
    ENV: dbs_ora_tnsname=TST

EXECUTING /usr/sap/TST/DVEBMGS00/exe/tp  -V
ERROR in child process: Cannot execute '/usr/sap/TST/DVEBMGS00/exe/tp': Exec format error

SAPup> Process with PID 12320986 terminated with status 27 at 20140730110321!

Solução
- Stopsap
- Com o usuário root logado, execute o comando.
> ps -ef | grep sapstartsrv

- Finalize o processo com o comando
> kill -9 <sapstartsrv pid>

- Com o usuário <sid>adm, execute os comandos
> sapcpe pf=/usr/sap/<sid>/SYS/profile/<SID>_DVEBMGS0_<hostname>
> sapcpe pf=/usr/sap/<sid>/SYS/profile/START_SCS<NR>_<hostname>

- Inicie o SAP
>startsap

DTecno Consultoria SAP - Suporte SAP Remoto sob Demanda

Keywords: Consultor SAP, SAP Remoto, SAP Basis, Suporte SAP Remoto

Referencia
http://vinbasis.wordpress.com/2012/10/10/sap-kernel-upgrade-700-to-720-on-unix-anix/

Mais informações

SUM - Stack.xml - Incorrect input; provide the correct path to the directory.

Problema 1

<!--LOGHEADER[START]/-->

<!--HELP[Manual modification of the header may cause parsing problem!]/-->

<!--LOGGINGVERSION[2.0.7.1006]/-->

<!--NAME[/usr/sap/SLM/<SID>/sdt/log/SUM/DEFINE-TARGET-SOURCE_07.LOG]/-->

<!--PATTERN[DEFINE-TARGET-SOURCE_07.LOG]/-->

<!--FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%6s]: %m)]/-->

<!--ENCODING[UTF8]/-->

<!--LOGHEADER[END]/-->

Jul 21, 2014 11:10:27 AM [Info  ]: The detected system topology is DUAL_STACK

Jul 21, 2014 11:10:28 AM [Info  ]: Dialog eliminator inboxOpEliminator does not allow to omit dialog DefineTargetDialog

Jul 21, 2014 11:10:28 AM [Info  ]: Dialog eliminator stackOpEliminator does not allow to omit dialog DefineTargetDialog

Jul 21, 2014 11:10:28 AM [Info  ]: Dialog eliminator ContentLocationDialogEleiminator does not allow to omit dialog DefineTargetDialog

Jul 21, 2014 11:10:28 AM [Info  ]: Dialog eliminator DownloadSMPEliminator allows to omit dialog DefineTargetDialog

Jul 21, 2014 11:11:04 AM [Info  ]: Setting catalog key inbox.option to value true into shared input catalog.

Jul 21, 2014 11:11:04 AM [Info  ]: Setting catalog key stack.option to value false into shared input catalog.

Jul 21, 2014 11:11:05 AM [Error ]: The provided Stack file or Directory: /midias/stack.xml, is not valid.

Jul 21, 2014 11:11:05 AM [Info  ]: Dialog eliminator inboxOpEliminator does not allow to omit dialog DefineTargetDialog

Jul 21, 2014 11:11:05 AM [Info  ]: Dialog eliminator stackOpEliminator does not allow to omit dialog DefineTargetDialog

Jul 21, 2014 11:11:05 AM [Info  ]: Dialog eliminator ContentLocationDialogEleiminator does not allow to omit dialog DefineTargetDialog

Jul 21, 2014 11:11:05 AM [Info  ]: Dialog eliminator DownloadSMPEliminator allows to omit dialog DefineTargetDialog

Problema 2

- Incorrect input; provide the correct path to the directory.

Problema 3

 Some of the archives defined in the stack configuration file were not found in the download directory.

Solução

- Crie a MPOZ e faça o download do arquivo stack.xml

- Faça o download dos arquivos apontados na MPOZ via SAP Download Manager.

- Crie um diretório no servidor e deixe os arquivos baixados junto com o stack.xml.

- Inicie o SUM.

- Quando solicitado no step “Select Target System Version”, selecione o arquivo stack.xml no diretório criado e marque a opção Stack configuration file (XML).

DTecno Consultoria SAP - Suporte SAP Remoto sob Demanda

Keywords: Consultor SAP, SAP Remoto, SAP Basis, Suporte SAP Remoto

Mais informações

Solman - SMSY - Product version is inconsistent with software components

Problema
- No Solution Manager 7.0 Ehp 1, na transação SMSY, nos Product Systems.
- No campo Product Version, com status 

 Product version is inconsistent with software components

Solução

1. Select the inconsistent product system in the overview tree.
2. Choose Change Product Assignment in the Header Data tab.
3. Select the new product version of the product system, and set the Active flag.
   The logical component is inconsistent, because the product versions of the logical componente and its assigned systems, differ.
4. Create a where-used list with Product System.
   Click on the name of the logical component.
   You go to the logical component.
5. Put the new product version into the logical component.
6. Save your changes.
7. Repeat the steps above for all systems down Product System tree. After the exclamation icon will disappear.

DTecno Consultoria SAP - Suporte SAP Remoto sob Demanda

Keywords: Consultor SAP, SAP Remoto, SAP Basis, Suporte SAP Remoto

Fonte: http://help.sap.com/saphelp_sm71_sp01/helpdata/en/15/2345932f024bd78fd1e14cc877149d/content.htm
SAP Note: 1516431 - Unexpected yellow exclamation points in SMSY

Mais informações

Restart work process

Problema
- Work process com status stopped.

Solução
1- Acesse a transação SM50.
2- Selecione o work process e clique em Administration->Process->Restart After Error-> Yes.
3- Finalize o wp clicando em Administration->Process->Cancel With Core.
4- Aceite a finalização do wp e ele será automaticamente reiniciado como a configuração no passo 2.


Fonte: http://www.ehow.com/how_12094889_restart-work-process-sap.html

Mais informações

Transação que utiliza um determinado objeto de autorização

Problema
Encontrar uma transação a partir de um objeto de autorização.

Solução
- Acesse a transação SU53.
- Entre na aba Authorization Object

- Insira o nome do objeto no campo Authorization Object, deixe a opção Transaction selecionada e clique em Execute(F8).

Mais informações

Low Hit Ratio for Initial Records buffer

The hit ratio is significant only if the number of requests is many times greater than the capacity of the buffer. A low hit ratio for relatively few accesses to the buffer is therefore normal and does not indicate poor performance.

It is important to observe the number of "Swaps". If the ratio of this number to the number of requests is very high, this indicates that the configuration of the buffer is too small. In this case, you should increase the parameter "rsdb/ntab/entrycount". The maximum number of entries in the "Initial Records" buffer ("Directory Entries Available") is derived from this parameter. It is "rsdb/ntab/entrycount" / 4.

Reference
1250278 - Low "Hit Ratio" for "Initial Records" buffer

Mais informações

SAPLogon.ini default path

The paths for Windows XP/Vista/7/8 are as follows:

• Windows XP: C:\Documents and Settings\<username>\Application Data\SAP\Common
• Windows Vista/7/8: C:\Users\<username>\AppData\Roaming\SAP\Common

Fonte: http://wiki.scn.sap.com/wiki/display/NWTech/SAP+GUI+Logon+Configuration

Mais informações

Learn more about SAP SL ToolSet

Mais informações

Start Stop SAP via Script

Start SAP
#/usr/bin/su - <SID>adm -c startsap

Stop SAP
#/usr/bin/su - <SID>adm -c stopsap

Mais informações

SUM - The file /usr/sap//SUM/sdt/.lock could not be locked. Check the write permissions and whether the controller is already started.

Problema

maq1:maqadm 23> STARTUP

*** Checking if C++ runtime is installed ...

*** Starting from /usr/sap/<SID>/SUM/sdt...

** Checking username "maqadm" for compliance...

Mar 17, 2014 1:42:04 PM [Error]: The file /usr/sap/<SID>/SUM/sdt/.lock could not be locked. Check the write permissions and whether the controller is already started.

Mar 17, 2014 1:42:04 PM [Fatal]: Error during controller startup.

Mar 17, 2014 1:42:04 PM [Fatal]: SL Controller exiting.

Solução

- Exclua os arquivos:

 -> /usr/sap/<SID>/SUM/sdt/data/.sdt_keystore

 ->/usr/sap/<SID>/SUM/sdt/data/.sdt_storage

- Inicie o SUM normalmente.

Mais informações

Notas SDCC RFC e OSS

763561 - Service Data Control Center (SDCCN) - FAQ
216952 - Service Data Control Center (SDCC) - FAQ

Mais informações