APO 3.1 to SCM 5.0 UPRADE ERROR IN PHASE SQLSCREXE_DELSHDTB

Hi
We are getting this error during the upgrade phase SQLSCREXE_DELSHDTB.
STEP 488 of 493.
ERROR: during execution of script :DELDB6TB.XQL. Error found in log
file TPSQLSTD.OUT and DELDB6TB.LOG
Contents of TPSQLSTD.OUT is as below:
hostname:SIDadm 64> pg TPSQLSTD.OUT
BLOCKED SIGNALS: ''
SAPup> Starting subprocess 14964 at 20080929220715
ENV <0x4015a1f8>:
SHLIB_PATH=/usr/sap/SID/SYS/exe/run:/opt/java1.4/jre/lib/PA_RISC2.0:/opt/java1.4/jre/lib/PA_RISC2.0/server:/opt/java1.4/jre/../lib/PA_RISC2.0:/oracle/SID/920_64/lib:/usr/sap/SID/SYS/exe/run
ENV <0x77ff04ef>: ORACLE_PSRV=SID
ENV <0x77ff04ff>:
PATH=/oracle/SID/102_64/bin:/sapdb/programs/bin:/usr/sap/SID/SYS/exe/run:/usr/bin:/opt/ansic/bin:/usr/ccs/bin:/usr/contrib/bin:/opt/nettladm/bin:/opt/fc/bin:/opt/fcms/bin:/opt/upgrade/bin:/opt/pd/bin:/usr/bin/X11:/usr/contrib/bin/X11:/opt/hparray/bin:/opt/resmon/bin:/opt/pred/bin:/opt/ignite/bin:/opt/atok/bin:/opt/egb/bin:/opt/vje/bin:/opt/aCC/bin:/opt/langtools/bin:/opt/hpnp//bin:/usr/sbin/diag/contrib:/opt/graphics/common/bin:/opt/cfg2html:/opt/perf/bin:/opt/scr/bin:/opt/imake/bin:/opt/hpnpl//bin:/opt/java1.4/bin:.
ENV <0x77ff070a>: NLS_LANG=AMERICAN_AMERICA.WE8DEC
ENV <0x77ff0736>: ORACLE_BASE=/oracle
ENV <0x77ff078f>: dbs_ora_tnsname=SID
ENV <0x77ff07a3>: ORACLE_SID=SID
ENV <0x40159df8>: DIR_LIBRARY=/usr/sap/SID/SYS/exe/run
ENV <0x401516a8>: dbs_ora_schema=SAPR3
ENV <0x77ff0853>: JAVA_HOME=/opt/java1.4
ENV <0x77ff089d>:
ORA_NLS33=/oracle/client/92x_64/ocommon/nls/admin/dataENV <0x77ff08f0>:
ORACLE_HOME=/oracle/SID/102_64
ENV <0x77ff092b>: dbms_type=ORA
ENV <0x401512a8>: auth_shadow_upgrade=0
EXECUTING /usr/sap/SID/SYS/exe/run/tp (tp)
pf=/usr/sap/put/bin/DEFAULT.TPP execdbscript SID -x DELDB6TB.XQL
This is /usr/sap/SID/SYS/exe/run/tp version 370.00.09 (release 700)
ERROR: tp_exec_dbscript: cannot open /usr/sap/put/bin/DELDB6TB.XQL
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter DBNAME is no longer used.
Warning: Parameter DBHOST is no longer used.
Warning: Parameter DBCONFPATH is no longer used.
Warning: Parameter STARTDB is no longer used.
Warning: Parameter STOPDB is no longer used.
TPERR- cannot open dbscript /usr/sap/put/bin/DELDB6TB.XQL
tp returncode summary:
TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0212
tp finished with return code: 212
meaning:
could not access file as supposed (see SLOG for more details)
Process with ID 14964 terminated with status 212
(EOF):
Contents of DELSHDTB.LOG log file
hostname 66> pg DELSHDTB.LOG
1 ETQ201XEntering upgrade-phase "SQLSCREXE_DELSHDTB" ("20080929220715")
2 ETQ367 Connect variables are set for standard instance access
4 ETQ399 System-nr = 'xx', GwService = 'sapgwxx'
4 ETQ399 Environment variables:
4 ETQ399 dbs_ora_schema=SAPR3
4 ETQ399 auth_shadow_upgrade=0
4 ETQ380 computing toolpath for request "TP_EXECDBSCRIPT"
4 ETQ382 translates to group "R3UP_TOOL_GROUP_SYS"
4 ETQ383 translates to path "/usr/sap/SID/SYS/exe/run"
4 ETQ276 Executing SQL-script "DELDB6TB.XQL"
4 ETQ399 ext. env.: DIR_LIBRARY=/usr/sap/SID/SYS/exe/run
4 ETQ399 ext. env.:
SHLIB_PATH=/usr/sap/SID/SYS/exe/run:/opt/java1.4/jre/lib/PA_RISC2.0:/opt/java1.4/jre/lib/PA_RISC2.0/server:/opt/java1.4/jre/../lib/PA_RISC2.0:/oracle/SID/920_64/lib:/usr/sap/SID/SYS/exe/run
4 ETQ399 2008/09/29 22:07:15: put_execute: (tp) forkpid:14964
2EETQ278 Errors during execution of SQL-script "DELDB6TB.XQL"
1EETQ203 Upgrade phase "SQLSCREXE_DELSHDTB" aborted with errors
("20080929220716")
We could not find the file DELDB6TB.XQL in /usr/sap/put/bin directory.
SAPup version we are using is
hsotname 69> SAPup -V
Enter the path of your upgrade directory [/usr/sap/put]:
Upgrade directory =
Re-executing SAPup with adapted environment.*
This is SAPup version 7.00/2, build 24.109
Please help on this as our APO upgrade is stuck on this.
Appreciate any help.
Regards,
Sandeep.

Hi Sandeep,
Seems like access issue to the user for /usr/sap/trans/log directory.
please grant 777 rights to this folder. also, before continuing try to restart system as may be ur SLOG file is holded by any process.
regards,
nitin

Similar Messages

Upgrade APO 3.0 to SCM 5.0 SR2 (requirements in source system)

Hello!:
We want to do and upgrade upgrade APO 3.0 to SCM 5.0 SR2
And we have seen the Guides SCM5.0 SR2 and SCM5.0 SR3, but appears info in the page 26 only about check the software requirements from APO 3.0 to SR3, but we want to check the information about APO3.0 to SR2.
Regards,
Alfredo.

Alfredo,
This is not a easy question, since you are several releases behind on APO. I have done upgrade from APO 3.0 to SCM 4.1 and then subsequently to 5.0 so there were lots of learnings specific to the Projects and develoments. The Setup being different in different industries and companies, there is no one answer to this question. Try the following ...
- Read the Release Notes of SCM 3.1, 4.0, 4.1, 5.0. You will see a Host of New Functionalities - Newer in SNP, PPDS, TPVS, Master Data (PDS along with PPMs).
I do not know what functionality you are live with in APO 3.0.
On the Existing Setup that you may find changed, I remember the following big changes ...
- GUI Changes are galore in master data, less
- SNP Side - Changes in TLB Engine & TLB Prioritization.
                 - Deployment Split Functionality
                 - Changes in User Exits (old code would not work). You will find this painfull if you've implemented User Exits. eg : If you were determining OrderTypes in orders sent from APO to R3. TLB User Exits. Lesser changes in Masterdata userexits.
                  - Newer fields in Master Data (eg : SNP Checking Horizon in Product Master and it's implications on Deployment & TLB. ).
                 - Subcontracting Planning in APO.
- Enhancements in VMI.
- Use of Parallel Processing for all Modules planning.
- Enhancements in Aggregated Planning
- Enhancements in Product Interchangeability.
- Several Newer Functionalities like ICH to make/replace the earlier Collaborative Planning better.
- Master Data several changes (eg : PDS)
- Several improvements in CoreInterface Function and Que Issues. In 4.0 onwards there is new functionality around CIF Postprocessing
- Use of Process Chains to streamline Batch Jobs and especially BI Loads into Cubes and Planning Areas.
- Several enhancements in PPDS (newer heuristics), Alerts
- BW underwent a Major change from BW 2.0 to BW 3.0 to now BI 7.0 which impacts Setup for Demand Planning. eg : The InfoCube got renamed to InfoProviders.
I suggest you start with the Release Notes. Form a List of your Test Scenarios, then Upgrade in your Development and start to Test. Don't plan less, but more time for testing since you are undergoing a several releases change. First start to get your Existing Business Scenarios documented as Test Scripts in Order.
I STRONGLY recommend doing a Technical Upgrade Only (i.e : do not upgrade Major Functionality unless there is no other way). In Summary for SURE SCM 5.0 is a Much better and Stable System than APO 3.0.
Hope this helps. Reward Points If you find it usefull.
Regards,
Ambrish Mathur

Step by step screen shots fro APO and SRM, CRM , SCM extractions.

hi friends,
can i get step by step screen shots fro APO and SRM, CRM , SCM extractions.
Thanking u
suneel.

Hi,
I am not sure that you can find something like you asked but from my point of view BI Content is enough.
Regards,
®

BW APO Transport steps (also please look into the error).

Hi all,
We have created data marts from BID to APOD and the loads are fine, I am ready with the trasports from APO dev to APO quality. I captured the replication (datasources), Transfer Structure, comm structure, update rules and infopackage, process chain .. everything is on APODev side..When i trasported orderly,we are getting this error.
Object 'DM' (APCO) of type 'Application' is not available in version 'A'
Message no. RSO252
You wanted to generate an object with the name 'DM' (in transport request APCO) of type 'Application' (TLOGO). This is, however, not available in the BW Repository database. It does not exist in the requested version A. If the version is 'D' then it is possible that an error arose during the delivery or installation. If the version is 'A' then the Object was either not created or not activated.
Please give me the resolution with the above error, please tell me what all i need to capture when i trasnport the datamrts.Do i need to cature anything on BID also...or only in APO DEv.
Thanks
arya

Hi Sam,
They are on different appliction servers, I have done the steps in APO QA some time back..i replicated the data source on APO QA side.. and i tried to move the transports , still i get the error..
I am confused at one point and need some help in clarification. I have ODS on BW side and Cube on APO side, so when i do the generate export data source on BW side. should i send the ODS activation from BID to BIQ as well, My point here is should i transport anything on BW side (BID to BIQ) apart from APO DEV to APO QA,
i have all transports ready on APO Dev side and i am getting the error,
Please let me know if i can give more details.. thanks for your answers

Distribution Planning within SAP - APO 3.0 or SCM 4.0

Hi,
Can do any 'Distribution Planning' within SAP SCM V4.0 or V5.0.
We are trying to improve 'decision-making' associated with selection of a particular warehouse for shipments coming out of a specific plant. The application should be able to produce a recommended set of shipments by week from each plant. Critical inputs that go into the process will be (a) Procurement Forecast; (b) Production Forecast; (c) Warehouse Space; (d) Production Plan etc
Can this be done utilizing SAP APO 3.0, SCM 4.0 or SCM 5.0?
Thanks

Hi Tushar,
APO 3.0, SCM 4.0 nd SCM 5.0 all provide replenishment, distribution and deployement along with basic transportation planning functionalities wihin SNP (Suppluy Network Module) of APO. With SCM 5.0 you get other applications (along with APO) like EWM (Extended Warehouse Management) and better transportation planning features.
Moreover it makes sense to go in for the lastest version of the solution to get the latest set of features. Please check on help.sap.com under my SAP Business Suite >> SCM >> APO >> SNP or http://www.sap.com/solutions/business-suite/scm/featuresfunctions/index.epx for more details.
Thanks,
Somnath

APO livecache logging with SCM 7

I am trying to understand how APO livecache logging works with APO release 7.
OSS Note 385808 suggests that, for APO DP release 3, there is no logging.
But what is the situation with APO release 7, for DP, SNP, PP/DS, GATP?
Thanks for any information on this point...

Hi,
We had upgraded SCM 4.1 to SCM 7.0. No need to change to DTP after upgrade. All the objects of previous version would be there and can be used as usual. But our BW upgrade is from 3.1 to BI 7.0.
Regards,
Saravanan V

Distinguish APO 3.0 and SCM 7.0

Hello Friends,
I need to know, what exactly the link and difference between two, and what are th modules being covered in SCM 7.0. It would be great if someone share's some knowledge !
Thanks and Best Regards.,

Hi PK,
If your requirement is of basic training purpose, then SCM 5.0 itself
will suffice. In any system, compliexity will arise only if you are
going for more enhancements and customisations.
You can also find more information on SCM 5.0 and SCM 7.0 under
the below link
https://websmp110.sap-ag.de/~form/sapnet?_SCENARIO=01100035870000000202&_SHORTKEY=00200797470000065738
Regards
R. Senthil Mareeswaran.

In SCM 5.0 Runtime Errors: DBIF_DSQL2_SQL_ERROR Exception: CX_SY_NATIVE_SQ

Hi,
I am getting following shortdump in my SCM 5.0 system with LiveCache 7.6.03 on AIX 5.3.
Please help me.
Runtime Errors         DBIF_DSQL2_SQL_ERROR
Exception              CX_SY_NATIVE_SQL_ERROR
Date and Time          01.07.2008 09:20:09
Short text
An SQL error occurred when executing Native SQL.
What happened?
The error "-4016" occurred in the current database connection "LCA".
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
How to correct the error
Database error text........: "POS(1) Unknown procedure
name:SIM_SIMSESSION_GET_ACTIVE"
Database error code........: "-4016"
Triggering SQL statement...: "EXECUTE PROCEDURE "SIM_SIMSESSION_GET_ACTIVE""
Internal call code.........: "[DBDS/NEW DSQL]"
Please check the entries in the system log (Transaction SM21).
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"DBIF_DSQL2_SQL_ERROR" "CX_SY_NATIVE_SQL_ERROR"
"/SAPAPO/SAPLOM_CORE" or "/SAPAPO/LOM_COREU23"
"/SAPAPO/OM_SIMSESSION_GET_ALL"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
The exception must either be prevented, caught within proedure
"/SAPAPO/OM_SIMSESSION_GET_ALL" "(FUNCTION)", or its possible occurrence must
be declared in the
RAISING clause of the procedure.
To prevent the exception, note the following:
System environment
SAP-Release 700
Application server... "dewall43"
Network address...... "10.40.16.43"
Operating system..... "AIX"
Release.............. "5.3"
Hardware type........ "00C912FC4C00"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 14
Shortdump setting.... "full"
Database server... "dewall43"
Database type..... "ORACLE"
Database name..... "APO"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Jan 23 2008 21:25:00"
create on........ "AIX 2 5 005DD9CD4C00"
Database version. "OCI_102 (10.2.0.2.0) "
Patch level. 144
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"
Memory consumption
Roll.... 1117168
EM...... 0
Heap.... 0
Page.... 24576
MM Used. 720672
MM Free. 376056
User and Transaction
Client.............. 100
User................ "DDIC"
Language key........ "E"
Transaction......... " "
Transactions ID..... "48692ABF23D6012AE10080000A28102B"
Program............. "/SAPAPO/SAPLOM_CORE"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "/SAPAPO/SAPLOM_CORE" - in
"/SAPAPO/OM_SIMSESSION_GET_ALL".
The main program was "/SAPAPO/OM_DELETE_OLD_SIMS ".
In the source code you have the termination point in line 39
of the (Include) program "/SAPAPO/LOM_COREU23".
The program "/SAPAPO/SAPLOM_CORE" was started as a background job.
Job Name....... "/SAPAPO/OM_DELETE_OLD_SIMSESS"
Job Initiator.. "DDIC"
Job Number..... 08200801
The termination is caused because exception "CX_SY_NATIVE_SQL_ERROR" occurred
in
procedure "/SAPAPO/OM_SIMSESSION_GET_ALL" "(FUNCTION)", but it was neither
handled locally nor declared
in the RAISING clause of its signature.
The procedure is in program "/SAPAPO/SAPLOM_CORE "; its source code begins in
line
1 of the (Include program "/SAPAPO/LOM_COREU23 ".
Source Code Extract
Line
SourceCde
9
*"     REFERENCE(ET_ACTIVE_SIMSESSION) TYPE /SAPAPO/OM_SIMSESSION_TAB
10
*"     REFERENCE(ET_RC) TYPE /SAPAPO/OM_LC_RC_TAB
11
*" EXCEPTIONS
12
*"      LC_CONNECT_FAILED
13
*"      LC_COM_ERROR
14
*"      LC_APPL_ERROR
15
16
17
data_def.
18
create_gen_com_params_default.
19
CLEAR ls_gen_com_params-client.
20
21
Verbindung zum liveCache aufbauen
22
start_function 'OM_SIMSESSION_GET_ALL'.                   "#EC *
23
check_server.
24
connect_to_livecache.
25
IF et_simsession IS REQUESTED.
26
COM-Routine zum Auslesen aller trans. Sim.
27
EXEC SQL.
28
EXECUTE PROCEDURE "SIM_SIMSESSION_GET_ALL" (
29
IN :LS_GEN_COM_PARAMS,
30
OUT :LV_RC,
31
OUT :ET_SIMSESSION)
32
ENDEXEC.
33
Returncodes pruefen und evtl. Exception raisen
34
lv_subrc_sav = sy-subrc.
35
ENDIF.
36
IF et_active_simsession IS REQUESTED.
37
COM-Routine zum Auslesen aller aktiven trans. Sim.
38
EXEC SQL.
>>>>>
EXECUTE PROCEDURE "SIM_SIMSESSION_GET_ACTIVE" (
40
IN :LS_GEN_COM_PARAMS,
41
OUT :LV_RC,
42
OUT :ET_ACTIVE_SIMSESSION)
43
ENDEXEC.
44
Returncodes pruefen und evtl. Exception raisen
45
lv_subrc_sav = sy-subrc.
46
ENDIF.
47
48
end_performance_measure.
49
end_function_no_main om_simsession_get_all.
50
check_returncodes.
51
if iv_get_testguids = gc_false.
52
delete ET_ACTIVE_SIMSESSION where table_line cs '~'.
53
delete ET_SIMSESSION        where table_line cs '~'.
54
endif.
55
ENDFUNCTION.
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
1
SY-DBCNT
0
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
Periodic Deletion of Hanging Simulation Versions
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20080701
SY-UZEIT
092008
SY-XPROG
RSDBRUNT
SY-XFORM
%_INIT_PBO_FIRST
Active Calls/Events
No.   Ty.          Program                             Include                             Line
Name
3 FUNCTION     /SAPAPO/SAPLOM_CORE                 /SAPAPO/LOM_COREU23                    39
/SAPAPO/OM_SIMSESSION_GET_ALL
2 FUNCTION     /SAPAPO/SAPLOM_CORE                 /SAPAPO/LOM_COREU12                    52
/SAPAPO/OM_SIMSESSION_SELECT
1 EVENT        /SAPAPO/OM_DELETE_OLD_SIMS          /SAPAPO/OM_DELETE_OLD_SIMS             67
START-OF-SELECTION
Chosen variables
Name
Val.
No.       3 Ty.          FUNCTION
Name /SAPAPO/OM_SIMSESSION_GET_ALL
IV_GET_TESTGUIDS
X
0
0
5
8
ET_ACTIVE_SIMSESSION
Table IT_9[0x44]
\FUNCTION=/SAPAPO/OM_SIMSESSION_SELECT\DATA=LT_SIMSESSION
Table reference: 2
TABH+ 0(20) = 0000000000000000000000000000000000000000
TABH+ 20(20) = 0000000200000009000000000000002CFFFFFFFF
TABH+ 40(16) = 04000021000026C00010249401800000
store        = 0x0000000000000000
ext1         = 0x0000000000000000
shmId        = 0     (0x00000000)
id           = 2     (0x00000002)
label        = 9     (0x00000009)
fill         = 0     (0x00000000)
leng         = 44    (0x0000002C)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000192
occu         = 16    (0x00000010)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 2     (cmpSingleMcmpR)
occu0        = 1
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
isCtfyAble   = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = Not allocated
pghook       = Not allocated
idxPtr       = Not allocated
shmTabhSet   = Not allocated
id           = Not allocated
refCount     = Not allocated
tstRefCount = Not allocated
lineAdmin    = Not allocated
lineAlloc    = Not allocated
shmVersId    = Not allocated
shmRefCount = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
collHook     = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
ET_RC
Table[initial]
ET_SIMSESSION
Table[initial]
OM_LC_NAME
LCA
000000000000000000000000000000
000000000000000000000000000000
444222222222222222222222222222
C31000000000000000000000000000
GC_OM_SYSUBRC
-16842752
F
E
SY-SUBRC
0
0000
0000
%_SPACE
0
0
2
0
%_VIASELSCR
0
4
OM_LC_APPL_NAME
000000000000000000000000000000
000000000000000000000000000000
222222222222222222222222222222
000000000000000000000000000000
SPACE
0
0
2
0
LS_GEN_COM_PARAMS
DDIC                                 # /SAPAPO/OM_DELETE_OLD_SIMS
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222444422222222222222222222222222222222202254545424454444545444554452222222
0000000000000000000000449300000000000000000000000000000000000F31010FFFDF45C545FFC4F39D30000000
LV_RC
00
00
00
00
GC_OM_SPP_FORECAST_EXT
K
4
B
GC_IMMEDIATE_TRANSFER
65537
0
0
GC_RESOURCE_MULTI
16909060
0
1
GV_SIMSESSION_TYPE
0
0
2
0
OM_MEASURE_PERFORMANCE
0
0
2
0
GC_OM_OBJECT_OUTPUT_NODE
454827294
1
B
OM_AS_KEY
000000000000000000000000000000
000000000000000000000000000000
222222222222222222222222222222
000000000000000000000000000000
%_DUMMY$$
0000
0000
2222
0000
No.       2 Ty.          FUNCTION
Name /SAPAPO/OM_SIMSESSION_SELECT
IV_MIN_AGE_IN_HOURS
1
0000
0001
IV_SAVED_INCLUSIVE
0
0
2
0
ET_OMS_VERSION
Table[initial]
ET_SIMSESSION_DELTA
Table[initial]
SCREEN
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
GC_OM_RPM_PORD_DEL
2004
000D
0074
GC_OM_OBJECT_UNKNOWN
66051
0
0
GC_OM_OBJECT_ORDER
16909060
0
1
GS_OMS_VERSION
00000000                      ########
000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000C
222222222222222222222233333333222222222222222222222200000000
000000000000000000000000000000000000000000000000000000000000
GC_MINTIME
09011000
1700002C
GT_OMS_VERSION
Table[initial]
GC_APPLICATION_BLRG
235868177
0
E
GC_OM_OBJECT_MODE
50595078
0
3
GC_TRUE
X
0
0
5
8
RSJOBINFO
00000000000000                                  ##
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222233333333333333222222222222222222222222222222222200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
GC_OM_OBJECT_RESOURCE
67438087
0
4
LT_SIMSESSION
Table IT_9[0x44]
GC_APPLICATION_CTPE
168496141
0
A
SY-REPID
/SAPAPO/SAPLOM_CORE
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2545454254544454454222222222222222222222
F31010FF310CFDF3F25000000000000000000000
GC_APPLICATION_MATP
185339150
0
B
SYST-REPID
/SAPAPO/SAPLOM_CORE
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2545454254544454454222222222222222222222
F31010FF310CFDF3F25000000000000000000000
GC_ATP_UPD_RPM
R
0
0
5
2
No.       1 Ty.          EVENT
Name START-OF-SELECTION
VARI
###00000000000000      ############
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222200033333333333333222222000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SYST-REPID
/SAPAPO/OM_DELETE_OLD_SIMS
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2545454244544445454445544522222222222222
F31010FFFDF45C545FFC4F39D300000000000000
GC_OM_OBJECT_RPM_GENERIC
791687475
2
F
SY-SUBRC
0
0000
0000
%_VIASELSCR
0
4
SY-REPID
/SAPAPO/OM_DELETE_OLD_SIMS
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2545454244544445454445544522222222222222
F31010FFFDF45C545FFC4F39D300000000000000
SY-MSGID
00000000000000000000
00000000000000000000
22222222222222222222
00000000000000000000
GC_TRANSPORT
y
0
0
7
9
SPACE
0
0
2
0
SY-MSGNO
000
000
000
333
000
SY-MSGV1
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
SY-MSGV2
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
SY-MSGV3
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
SY-MSGV4
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
GC_ITRUE
16777623
0
1
GC_FALSE
0
0
2
0
SYST
###############################################################################T########X ####
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000100000000000000000000000000000000000000000000000E000200
0000000000000000000000000000000000000006000000000000000000000000000000000000010500000001520000
000001010000010000000000010001000000000A00000000000000000000000000000000000006040000000080000C
GC_IFALSE
104192
0
0
GT_OMS_VERSION
Table[initial]
GC_MINTIME
09011000
1700002C
GT_SIMS_DELTA
Table[initial]
SY-XFORM
%_INIT_PBO_FIRST
000000000000000000000000000000
000000000000000000000000000000
254445554454455522222222222222
5F9E94F02FF6923400000000000000
%_DUMMY$$
0000
0000
2222
0000
SCREEN
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Internal notes
The termination was triggered in function "DsqlErrorHandler"
of the SAP kernel, in line 2062 of the module
"//bas/700_REL/src/krn/runt/abexsql.c#2".
The internal operation just processed is "DSQL".
Internal mode was started at 20080701092008.
Internal call code.........: "[DBDS/NEW DSQL]"
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
=> 64 bit R/3 Kernel
=> 64 bit AIX Kernel
=> Heap limit      = unlimited
=> Stack limit     = unlimited
=> Core limit      = 4294965248
=> File size limit = unlimited
=> Heap address = 0x0x1152ede20
=> Stack address = 0xfffffffffff84a0
=> Stack low     = 0xfffffffffff84a0
=> Stack high    = 0xffffffffffff7a0
=> Stack Trace:
     AixStack() at 0x1000c7d94
     CTrcStack2() at 0x1000c7e8c
     rabax_CStackSave__Fv() at 0x1000b2d70
     ab_rabax() at 0x1000af728
     ab_dbdserr__FiPCUsT1T2P9DS_HEADERT2T1Pv() at 0x10057efbc
     DsqlErrorHandler__Fi() at 0x10135b8e8
     ExecuteCall__Fv() at 0x10135b454
     ab_jdsql__Fv() at 0x101356b40
     ab_extri__Fv() at 0x10040d93c
     ab_xevent__FPCUs() at 0x100a9d170
     ab_trigg__Fv() at 0x100a9ce5c
     ab_run() at 0x1014bee48
     N_ab_run() at 0x100d5bca8
     dynpmcal() at 0x100d5aa74
     dynppai0() at 0x100d58a08
     dynprctl() at 0x100d6047c
     dynpen00() at 0x100d52364
     Thdynpen00() at 0x1000e2410
     TskhLoop() at 0x1000e4254
     ThStart() at 0x1000fe324
     DpMain() at 0x10156c770
     nlsui_main() at 0x101a99998
List of ABAP programs affected
Index
Typ
Program
Group
Date
Time
Size
Lang.
0
Prg
/SAPAPO/OM_DELETE_OLD_SIMS
0
28.09.2006
17:13:54
115712
E
1
Prg
SAPMSSY0
1
07.01.2008
17:16:23
92160
E
2
Prg
SAPMSSYD
1
27.09.2006
18:38:20
21504
E
3
Prg
SAPFSYSCALLS
1
03.12.2004
17:45:45
8192
E
4
Prg
RSDBRUNT
0
07.01.2008
17:27:13
254976
E
5
Typ
RSSCR
0
12.10.1999
15:50:05
5120
6
Prg
RSDBSPBL
0
22.02.2005
08:58:45
72704
E
7
Prg
SAPDB__S
0
03.12.2004
17:45:45
19456
E
8
Prg
RSDBSPMC
0
27.09.2006
18:23:16
79872
E
9
Typ
DDSHDESCR
0
28.11.1997
16:26:30
4096
10
Typ
SPPARAMS
0
07.03.1997
14:48:48
2048
11
Prg
SAPLSABE
11
03.12.2004
17:45:46
13312
E
12
Prg
SAPLSECU
12
07.01.2008
17:09:46
87040
E
13
Typ
RSSUBINFO
0
25.02.2000
15:47:23
3072
14
Prg
SAPLSTUP
14
07.01.2008
17:08:20
74752
E
15
Prg
SAPLCNDP
15
13.12.2007
16:41:21
195584
E
16
Prg
SAPLSCNT
16
22.02.2005
08:58:56
30720
E
17
Prg
SAPSHDTV
16
31.01.2005
15:41:11
33792
E
18
Prg
SAPFGUICNTL
1
22.02.2005
08:58:14
24576
E
19
Prg
SAPLOLEA
19
12.12.2007
14:16:36
96256
E
20
Prg
SAPLSGUI
20
07.01.2008
17:16:23
84992
E
21
Prg
SAPLSTTM
21
28.07.2005
11:12:25
69632
E
22
Prg
SAPLSBDC
22
07.01.2008
17:09:02
44032
E
23
Prg
SAPLSFES
23
07.01.2008
17:27:14
260096
E
24
Prg
SAPLTHFB
24
07.01.2008
17:16:23
394240
E
25
Typ
WPINFO
0
08.02.1999
14:18:32
6144
26
Prg
SAPLURFC
26
07.01.2008
17:13:39
22528
E
27
Prg
SAPLSPLUGIN
27
03.12.2004
17:45:46
8192
E
28
Typ
SWCBCONT
0
07.10.1997
12:13:50
3072
29
Typ
OLE_VERBS
0
09.02.1995
13:23:37
2048
30
Typ
OLE_PA
0
13.01.1995
11:06:59
2048
31
Prg
/1BCDWBEN/SAPL/SAPAPO/EN0001
31
08.06.2001
20:33:24
233472
E
32
Prg
SAPLSENA
32
12.12.2007
14:18:37
33792
E
33
Prg
/SAPAPO/SAPLOM_CORE
33
28.07.2005
16:02:32
502784
E
34
Prg
SAPLSAL2
34
07.01.2008
17:15:35
81920
E
35
Typ
/SAPAPO/OM_OMS_VERSIONS_STR
0
16.02.2006
18:01:55
3072
36
Prg
CL_ABAP_CHAR_UTILITIES========CP
36
28.07.2005
11:12:24
13312
E
37
Prg
CX_SY_NATIVE_SQL_ERROR========CP
37
12.12.2007
12:39:14
13312
E
38
Typ
SCX_SRCPOS
0
08.07.2004
09:59:00
2048
39
Prg
CX_SY_SQL_ERROR===============CP
39
28.07.2005
11:12:24
10240
E
40
Prg
CX_DYNAMIC_CHECK==============CP
40
28.07.2005
11:12:24
10240
E
41
Prg
CX_ROOT=======================CP
41
12.12.2007
17:18:15
11264
E
42
Prg
CX_NO_CHECK===================CP
42
28.07.2005
11:12:24
10240
E
43
Prg
CX_SY_NO_HANDLER==============CP
43
28.07.2005
11:12:24
10240
E
44
Prg
%_CSYDES
0
22.02.2005
08:58:46
8192
E
45
Prg
%_CSYDB0
0
22.02.2005
08:58:45
36864
E
46
Typ
RSVAMEMKEY
0
16.12.1996
19:31:50
2048
47
Prg
%_CRSDS
0
22.02.2005
08:58:21
10240
E
48
Prg
%_CSLIS
12
17.02.2006
08:58:39
89088
E
49
Typ
DTC_S_LAYO
0
08.06.2001
15:59:56
6144
50
Typ
CAT_SVARS
0
19.05.2004
16:00:08
3072
51
Typ
SYST
0
03.12.2004
17:45:35
31744
52
Typ
RSJOBINFO
0
09.02.1995
13:25:17
3072
53
Typ
VARI
0
16.12.1996
19:38:11
6144
Directory of Application Tables
Name                                     Date       Time       Lngth
Val.
Program /SAPAPO/OM_DELETE_OLD_SIMS
SYST                                     03.12.2004 17:45:35   00004612
\0\0\0\0\0\x0001\0\x0001\0\0\0\0\0\x0001\0\0\0\0\0\0\0\0\0
VARI                                       . .       : :     00003052
Program /SAPAPO/SAPLOM_CORE
RSJOBINFO                                  . .       : :     00000164

As per note 1619720, drop following two tables and then validate by running t-code lca03.
drop table APPSYSNAME
drop table APPSYSPARAM
dbmcli -d LCSID -n hostname -u superdba,sdbapassword -uSQL SAPSID,password
dbmcli on hostname : SID>sql_execute drop table APPSYSPARAM
OK

SCM WP trace file error message

Hi,
We are getting the below error in our work process trace files for our SCM 5.1 system
Tue Dec 30 17:35:51 2008
***LOG Q0I=> NiPGetHostByName: hostname 'OPTSERVER' not found: gethostbyname [niuxi.c 1470]
At same time, we have system log entries as below:
19:07:34 BTC 031 009 APOADMIN                Q0 I Operating system call gethostbyname failed (error no. 0 )
Documentation for system log message Q0 I :
The specified operating system call was returned with an error.
For communication calls (receive, send, etc) often the cause of errors
are network problems.
It could also be a configuration problem at operating system level.
(file cannot be opened, no space in the file system etc.).
Does anyone know about this?? The RFC connections between APO server and Optimizer server are working fine and there is no issue. However, for any dialog/background process we are getting the error above. Please suggest.
Regards,
Sandeep.

Hi Senthil,
Thanks for your reply. As in the note 388193 that you have mentioned job /SAPAPO/OM_REORG_DAILY is executed daily in our system and there does not seem to be any issue with optimizer installation as optimizer is working fine and there is no connection problem with scm system.
However the SM21 errors keeps coming.
13:48:15 BTC 031 009 APOADMIN                Q0 I Operating system call gethostbyname failed (error no. 0 )
13:54:38 BTC 031 009 APOADMIN                Q0 I Operating system call gethostbyname failed (error no. 0 )
14:01:24 BTC 031 009 APOADMIN                Q0 I Operating system call gethostbyname failed (error no. 0 )
14:07:59 BTC 031 009 APOADMIN                Q0 I Operating system call gethostbyname failed (error no. 0 )
Regards,
Sandeep

Fixing System Control Manager (SCM) Crashing from Unhandled Error in Windows 8

If you get an unhandled error message when rebooting your laptop after installing SCM v10.013.03016 check to see if you have Visual C++ 2012 Redistributable installed on you PC.
If not, download from Microsoft.
I installed version 11.0.51106.1 and SCM seems to be working fine now (apart from my bluetooth which keeps dying every few boots and is probably not related to SCM itself).
This fixed my MSI GT70-0ND Dragon Edition

Try installing Microsoft .NET Framework 4.5 Update for Windows 8: http://www.microsoft.com/en-us/download/details.aspx?id=29185

APO or SCM

Hi All,
Please give the more information about APO 5.0 or SCM.How it is used on Real time and how to Optimiztion of business cost and Planning ...etc.I need How to transfer data from the R/3 to APO system. I have knowledge on SAP-ABAP and some function knowledge.
Thank you,
Durga

Hi Durga,
It's APO till version 3.1 and then SAP merged few more things and then started calling SCM-APO after 4.0.
The real time integration between R/3 and APO is through Core Interface.
You can get more details on CIF in <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/wiki">wiki</a>. Browse for SCM and then for CIF.
The optimization of business cost planning is mostly done in APO-SNP- optimizer and CTM(may be). The integration is all real time with R/3 through CIF.
Hope this helps.

Recommendations/experiences using APO-DP in multi-client SCM environment ?

Hello experts,
we have an SCM5.0 system using DP/SNP etc. Now we want to onboard another company (Joint Venture) and introduce DP first for them. We are investigating what it would mean to setup another client within our existing SCM system or what challenges we could run into (since the underlaying BW is not truly multi-client capable).
SAP Note 1413544 says that theoretically SCM is capable of doing so with some limitations since there can only be 1 "master" BW client in an SCM system. Does somebody have / would kindly share experiences working withe several APO clients within 1 SCM system and preferably using DP.
My questions would be:
1) if I create a new DP PlanningObjectStructure in the additional APO client - do I need to activate it the "master BW client" (since there is an internal InfocCube behind) ? Does this also mean all POS and PAs are visible in all clients or only in the client where I created them ?
2) if I want to use RemoteCube to extract data from a DP (or SNP) planning area (ad-hoc reporting on LiveCache Data)- does this go thru the "master BW client" or thru the additional / new BW client ?
3) Assuming I would create a new DP POS + Planning Area in the additonal client and create planning Books / DataViews - are these PB/DV visible in all clients or only in the one where I created it ?
Regards
Thiomas

Hi Thiomas,
Though I have not worked for this scenario. However as per my understanding,All APO objects as PA, MPOS ,PB, DV should be client specific and will be visible in the specific client only. The Tricky portion would be the BW portion. As this would be single one, So the extraction cube and Planning area datsources should be visible in the main client BW.Hence it can be used in the same BW client .
I hope this should work having the seperate client for DP objects and keeping the same main BW client at the background. Let me also the test results.
Let me know if it helps.
Regards
Gaurav

SCM , APO and Livecache administration

Hi SAP Guru's
Can any one guide me what is role and responsibilities of SCM and APO and Live cache administration as part of Basis.
I will be great help if any one can guide me in SCM and APO and LIVE cache administration.
Waiting for Reply
Farooqui

Hi Farooqui
Since this Forum handling more application related topic, it is better to post your question in different Forum "MaxDB/liveCache ".
Above MaxDB/liveCache is handling more basis and liveCache related topic.
As a general information, SAP provides following documens that describe task and check point related to SCM system and liveCache. So I recommend you to check following 3 documents.
URL : http://service.sap.com/solutionmanagerbp
Number
44            System Monitoring for SAP APO (3.x) / mySAP SCM (4.x/5.0)
34            Monitoring and Administration for SCM / APO
42            Checklist for Recovery of SAP APO liveCache >= 7.4
Also there are some documents that describe liveCache behavior, so for better understanding,
I also recommend you to check following 2 documents. (The information is bit old. but it might be helpful to understand liveCache).
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/66f7351f-0801-0010-96b4-f91d424b9d08
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/72cdbe90-0201-0010-6986-eae36eb6c819best regards
Keiji Mishima

REg Installing APO 5.0/SCM 5.0

i have been told to install APO 5.0
But as per my understainding APO 5.0 is SCM 5.0
Pls tell me the option whihc i have to select in SAPINST to make the installation

you have to select SCM pl refer installation document on https://websmp202.sap-ag.de/instguides --> SAP Business Suite Applications --> SAP SCM --> Using SAP SCM 5.0 Server
Cheers,
-Sunil

APO GATP Backorder processing -- SO's in R/3 not updating -- CIF problem

Issue: After executing backorder processing in APO, the update is stuck in CIF .. error (*"Inbound APOCLNT800: No IModel active for cat. Sale"*)
Note: I am able to create SO's in R/3 and getting commit from APO.
After Saving the SO's the SO's are transferred to APO ( I am able to see the SO's in product view - APO).
I wonder where is the IM not active
Appreciate your inputs

Hi kitkat,
If this is a test of a new functionality, you might just have an old blocked queue. Try deleting the blocked queue and then re-try the BOP.
If this is a new error for a BOP scenario that had been working previously, then check your deltareport. You may have an order in SCM that for whatever reason is no longer being handled by SCM. In this case, you only need to delete the order in SCM.
If these two tries don't work, then you need to start examining your CIFs to see if the product/location/sales ord/stock/ATP/etc etc are consistant with your expectations. Don't forget, in the case of a GATP using location/product substitution, you need to ensure that all possible data that would be needed by BOP is being properly CIFd across.
Best Regards,
DB49

APO 3.1 to SCM 5.0 UPRADE ERROR IN PHASE SQLSCREXE_DELSHDTB

Similar Messages

Maybe you are looking for