Significance of /sapapo/om_delete_old_simsess
Hi Gurus,
Could you pls explain me the significance of the report "/sapapo/om_delete_old_simsess".
can i use the same to solve the DP locking problems?
Thanks,
Vignesh
Hi Vignesh,
The basic purpose of this programme is to delete periodically the hanging
transactional Simulations.
Whenever user carries out simulations in transactional level, sometimes
data will get locked or hanged depending upon the situation.
Such scenarios can be corrected using this programme
Regards
R. Senthil Mareeswaran.
Similar Messages
-
/SAPAPO/OM_DELETE_OLD_SIMSESS - Fails
hi,
/SAPAPO/OM_DELETE_OLD_SIMSESS - periodic job fails says as below log. I could not find OSS note in my search.
Looks to me, the lock corresponds to a simulation version is missing. Job tries to delete simulation version/ lock together.. however it fails.
If this is the case, how to clear old SIMM versions?
Job Log:
07/21/2011 08:31:13 JYKhRvRmN6dX0000f6VRCW lock does not exist
07/21/2011 08:31:14 Cannot delete simulation version
07/21/2011 08:31:14 Job cancelled after system exception ERROR_MESSAGE
Thanks,
RajSHi Nathalia,
Hope you are doing great!!
We have similar issue as above and i am SAP customer and i already logged a message long back on this issue please check this message ( 1012512 / 2012 ) and let us know your thoughts.
Thanks
Ravi -
Hi folks,
I have an issue with transaction LCA03 in SCM 5.0. It shows a red light at "Critical logging event" --> ReorgDaily. When I check the log, I can see that the background job /SAPAPO/OM_REORG_DAILY is terminating every night with the following error message:
"No planning version active in current client" and then "Job cancelled after system exception ERROR_MESSAGE."
We work in client 100. In client 100, I checked transaction /SAPAPO/MVM and there is planning version 000 active.
When I check SM36 --> standard jobs, there are several background jobs (standard jobs) scheduled and running, but all seem to run in Client 000. One of these is /SAPAPO/OM_REORG_DAILY.
How can I get this fixed? Do I have to delete the standard job /SAPAPO/OM_REORG_DAILY and create it again, in client 100? What about the other jobs, that are running fine in Client 000 (/SAPAPO/OM_DELETE_OLD_SIMSESS, SLCA_LCK_SYNCHOWNERS)? Do they make sense there? Or does it not matter, in which client these jobs run?
Sorry, but the client concept is new to me and I couldn't find info on this with regard to these jobs.
Thank you for helping, MatthiasHi, thanks for your answers!
I first checked the job log in transaction SM36 for /SAPAPO/OM_REORG_DAILY. From there comes the error message I provided.
/SAPAPO/OM11 shows all occurences for /SAPAPO/OM_REORG_DAILY, they all failed and only ran in client 000. Also, DelOldRegs (/SAPAPO/OM_DELETE_OLD_SIMSESS) are shown with a yellow light, all are shown for client 000 only.
I now ran the job /SAPAPO/OM_REORG_DAILY manually on client 100 from transaction SE38.
It first shows an information window which says: /sapapo/om_reorg_daily Scheduled Daily: 100 --> See /sapapo/om13.
Then a new Informtion windows with: Analysis of LC and LCA objects shows errors.
If I go again to transaction LCA03, there are only two red traffic lights:
-/sapapo/om_reorg_daily 100 (I think I just have to schedule the job for client 100 here daily, since now it is only scheduled in client 000)
-Critical logging event: This shows the error, that /SAPAPO/OM_REORG_DAILY failed in the last nights (when it was running in client 000. It failed with the error message given earlier.)
What to do? Just schedule the job for client 100 and delelte the standard job for client 000? Because I cannot schedule two standard jobs with the same program to be executed.
Thanks again, Matthias
Message was edited by:
Matthias Sartor -
Hi folks,
we run SCM 5.00 (Level 0010) with LiveCache (2005_700, Level 0005).
We already scheduled /SAPAPO/OM_REORG_DAILY and /SAPAPO/OM_DELETE_OLD_SIMSESS as regularily running background jobs in the only liveCache relevant client 100. Do we have to schedule the job /SAPAPO/OM_LCAALERTS for this client as well, or is it obsolete for our version?
Thanks in advance, MatthiasHi Raghu,
thanks! The Job /SAPAPO/OM_LCAALERTS is currently scheduled and running in client 000 - which is not LiveCache relevant. Does it really matter in which client this job runs - is it client-dependent? LCA03 shows no red lights, but I don't know if it makes sense to let the job run in client 000. Please help...
Thanks,
Matthias
Message was edited by:
Matthias Sartor -
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 . . : : 00000164As 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 -
What is the Role of R/3 BASIS administrator in SAP-APO
Hi can any one tell me, what is the role of a BASIS admin. in SAP-APO. Please list the responsibilities.
Thanks in advance.
Regards,
bompally.Thank you very much manish,
Actually I am a BASIS admin. I want to explore the BASIS -APO administration side. What do you suggest on this.
Please provide me some more information on the following also.
CIF Performance Questions.
What is CIF?
1) Check and ensure that same qRFC versions and supplements are used in both R/3 and APO Side. Make sure that latest available qRFC Version and supplement is being used.
2) Review the Integration models used currently and identify if they can be reorganized to reduce the duplication?
3)Review the background processes for Activation and generation of the integration models.
4)Identify if there are any bottlenecks in the CIF queues.
5)Review the process of transferring the Product/Material master changes? Are the change pointers being used or BTE's?
6)Review and check the schedule of the following background jobs: (Which transaction we use to do these functions?)
Deleting old integration models?
Deleting old application logs.
Processing of change pointers.
Deletion of old change pointers.
Live Cache consistency Check jobs.
Planning area consistency checks.
Reorganize OMS Data (/SAPAPO/OM_REORG_DAILY and /SAPAPO/OM_DELETE_OLD_SIMSESS)
7)Monitor the QRFC Tables-ARFCSSTATE, ARFCSDATA, ARFCRSTATE,
TRFCQDATA, TRFCQIN, TRFCQOUT and TRFCQSTATE.
8)Monitor the Optimization server performance.
Thanks and Regards,
Pradeep -
Problems with liveCache in APO
Hi experts,
I have an issue with regards to liveCache in APO and I hope someone can help me.
Whenever I try to create a Planning Version within a Model (via transaction /SAPAPO/MVM) the following
error message is provided: "General error in model / version management planning".
Through some research I found a document that makes the following recommendation: "Sometimes when you work in a multi-client system, you maybe encounter the following error message: "General error in model/planning version management". This error is due to the fact that in LiveCache the planning version already exists but it cannot be found on database. As a remedy, you have to remove this inconsistency by using the transaction /SAPAPO/OM17. For detailed information, please refer to SAP Note 519014."
Then, as recommended, I tried to execute the transaction /SAPAPO/OM17. But when I tried to execute this transaction another error message was released: "Connection to liveCache failed. Message no. /SAPAPO/OM000".
Moreover, the result of the transaction /SAPAPO/OM13 ( Analyze liveCache and LCA Objects ) shows the following errors and warnings:
Item
Check
Connection to LCA
with errors
liveCache Stat. from LCA - ???
with errors
liveCache Initialization - 001
with errors
Old simulation versions
with warnings
/sapapo/om_reorg_daily - 001
with errors
/sapapo/om_delete_old_simsess
with errors
/sapapo/om_lcaalerts
with errors
Number of LC Sessions - 0
with errors
Thanks in advance for help.
Greetings,
Francisco Fonseca.Hi sai balakavi,
initially, thanks for the fast help.
As suggested, the issue was escalated to the BASIS team and the procedure chosen was as follows:
Shutdown SAP APO and liveCache (ECC + SE6) services
Shutdown DB Oracle (ORCL + ECC + APO + SE6) services
Logs verification
Restart server
Restart SAP APO and liveCache (ECC) services
Restart DB Oracle (ORCL + ECC + APO + SE6) services
However, the previous problems still persist. So, in order to get more information about the problem, I exported a full report (at the end of this message) on the result of the transaction /SAPAPO/OM13 ( Analyze liveCache and LCA Objects ).
Is there any other action to be taken in addition to shutdown and restart of liveCache services?
Thanks in advance for help.
Greetings,
Francisco Fonseca.
EXPORTED REPORT
Versions
Current ABAP SP : LCAPPS 2005_700: patch 0003
Import Date of SP : 28.09.2006
Import Time of SP : 17:14:18
Runtime Environment Vers.:
liveCache Connection : titanidas-LCA
Module ReleaBuildPatch OpSys Change DLL Date Size D
Number of LCA Routines : 0
dbsdbslib : (Cannot determine) Patch
SQLDBC Release :
Times
Application Server : 16.10.2008 06:00:16
liveCache Server :
LCA Object :
Checks
liveCache Connection LCA : X OK
liveCache Connection LDA : X OK
liveCache Connection LEA : X OK
Connection to LCA : ERROR
liveCache Status from LCA: ??? ERROR
liveCache Initialization : 001 ERROR
Number of Active Traces : 0 OK
Number of Active Checks : 0 OK
No. of Old Trans. Sim. : 0 Warning
Initialize Follow-Up : ERROR
/sapapo/om_reorg_daily Scheduled Daily: 001 ERROR
/sapapo/om_delete_old_simsess scheduled regularly: ERROR
/sapapo/om_lcaalerts Scheduled Daily: ERROR
Number of Work Processes : 13 ERROR
Number of LC Sessions : 0 ERROR
RFC Connections : OK
Clients with Errors : OK
MAXLOCKS : 0 Warning
OMS_HEAP_LIMIT : 0 Warning
OMS_HEAP_THRESHOLD : 0 Warning
OMS_VERS_THRESHOLD : 0 Warning
REQUEST_TIMEOUT : 0 Warning
Critical Logging Event : OK
Network
Server titanidas
Client titanidas
Thu Oct 16 06:00:52 2008
***LOG Q0I=> NiPConnect2: connect (10061: WSAECONNREFUSED: Connection re
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 0 / sock 1916
(SI_ECONN_REFUSE/10061; I4; ST; 172.16.28.148:3298) [nixxi.cpp 27
*** ERROR => NiTClientLoop: NiHandle (rc=-10) [nixxtst.cpp 2839]
* ERROR partner '172.16.28.148:3298' not reached
* TIME Thu Oct 16 06:00:52 2008
* RELEASE 700
* COMPONENT NI (network interface)
* VERSION 38
* RC -10
* MODULE nixxi.cpp
* LINE 2770
* DETAIL NiPConnect2
* SYSTEM CALL connect
* ERRNO 10061
* ERRNO TEXT WSAECONNREFUSED: Connection refused
* COUNTER 1
Process died with exitcode -1
Current Messages
knldiag - Start
Error when reading the KNLDIAG file
knldiag - End
Error Messages
knldiag.err - Last Message
knldiag.err - Last Initialization
knldiag.err - Last Start
Log Initialization
lcinit.log - Start
Error when reading the LCINIT.LOG file
lcinit.log - End
Logging for Log - /SAPAPO/OM11
Date Time Event Cl. Message
Data Cache
Pages Megabyte
Cache Sizes 0 0
OMS Data 0 0
OMS History/Undo 0 0
SQL Data 0 0 Used (%)
Overall 0 0 0,00
Accesses Hit Rate (%) Overall Failed
OMS Data 0,00 0 0
OMS History/Undo 0,00 0 0
SQL Data 0,00 0 0 -
LiveCache lock server is not installed
Hi All,
Job /SAPAPO/OM_DELETE_OLD_SIMSESS has been failed:
Job log says:
Job started
Step 001 started (program /SAPAPO/OM_DELETE_OLD_SIMSESS, variant , user ID BATCHSCHE)
evaluate oms_versions
evaluate simsession delta
obsolete transactional simulations
<b>liveCache lock server is not installed</b>
Job cancelled after system exception ERROR_MESSAGE
Same was finished successfully and its job log says:
Job started
Step 001 started (program /SAPAPO/OM_DELETE_OLD_SIMSESS, variant , user ID BATCHSCHE)
evaluate oms_versions
evaluate simsession delta
obsolete transactional simulations
Job finished
liveCache lock server is not installed seems to be extra.Any hint?
Thanks in advance.
Regards,
TusharHello,
Just forgot to give server details:
KERNEL 7.6.01 BUILD 009-123-141-487
DBMServer 7.6.01 Build 009-123-141-487
SCM basis 700 sp 11
Regards,
Tushar -
Hi people,
I´m setup up the SCM/APO with livecaché. I´ve connected the LCA database with the scm system. But when I go to the LCA03 tcode for do the test I get four red messages.
/sapapo/om_reorg_daily
/sapapo/om_delete_old_simsess
/sapapo/om_lcaalerts
For this last, I follow the step of made the jobs. I do it, but when refresh the tcode LCA03 it´s is same. The other two jobs are equal.
And the last error is Lc sessions account, which indicates the MAXUSERTASKS. Where can i do to set up this parameter?Hi,
The third point is correct.
The erros are that /sapapo/om_reorg_daily, /sapapo/om_delete_old_simsess, /sapapo/om_lcaalerts are with red check. I follow the steps for to do them and when i back to the realized the test I get the same errors.
I read in one thread that there are to execute /sapapo/opt_inst, for to see the RFC connections. I get the diferent connections on red. It´s possible that this affected the before step???
Edited by: Ruben Torres on Apr 9, 2009 12:10 PM
Another question. In the sm36 I select the standart jobs and push standar prevision, then when I back to the tcode LCA03 don´t show me the screen with the diferentes options with the checks greens or reds. Only show me one message that says "liveCache-test onLCA finished without errors". It´s normal?? Not should be show me the screen with the diferents checks????
More thanks
Edited by: Ruben Torres on Apr 9, 2009 1:06 PM -
Issue with /SAPAPO/OM_LC_UPGRADE_70 in SCM 7.0 prepare
Hi,
We are running an SCM upgrade from 5.1-> 7.0
We upgraded our dev system fine. We are now in QA and running the prepare at phase PREP_CNVCHECKS/REQ_APOUPG0.
Option # 3 of section A of /SAPAPO/OM_LC_UPGRADE_70 runs job name SYNC_LC_DB_DP, program /SAPAPO/OM_SYNC_LC_DB. Most planning versions run ok, but for ZDP01, this one has been running for over 30,000 seconds and it looks like it is not doing anything in liveCache or the SCM database.
Is there some way to determine what is going on with this job? We'd like to move on with the prepare...
Thanks,
MargaretHi Natalia,
thanks for your response.
1. We have opened message 35265
2. the job is running in sm37 start time 01-13-2011, 14:51:42
a. sm50 information shows program /SAPAPO/SAPLOM_SYNC in DB-PROC SAPTS_OBJECTS_GET_ALL
b. liveCache IO operations do not show any significant change since start of this job
c. There are liveCache SQL locks for the application server PID that is running the background job
521 10158214 us6qa1a02.na.cokecce.com row_share
521 10158214 us6qa1a02.na.cokecce.com row_share
521 10158214 us6qa1a02.na.cokecce.com tab_share
521 10158214 us6qa1a02.na.cokecce.com tab_share
521 10158214 us6qa1a02.na.cokecce.com tab_share
521 10158214 us6qa1a02.na.cokecce.com tab_share
521 10158214 us6qa1a02.na.cokecce.com tab_share
521 10158214 us6qa1a02.na.cokecce.com tab_share
521 10158214 us6qa1a02.na.cokecce.com tab_share
d There is a task in liveCache
521 10,158,214 us6qa1a02.na.cokecce.com share 00018AE98905 17,152,861 01-13-2011 14:51:42
e. The dec_w36 file is contains information just from the initial connection u2013 no errors
A Thu Jan 13 14:51:42 2011
A **GENER Trace switched off ***
M SosICreateNewAnchorArray: sos_search_anchor_semantics = 1
E Profile-Parameter: enque/deque_wait_answer = FALSE
E Profile-Parameter: enque/sync_dequeall = 0
B dbtran INFO (init_connection '<DEFAULT>' [DB2:700.08]):
B max_blocking_factor = 10, max_in_blocking_factor = 35,
B min_blocking_factor = 3, min_in_blocking_factor = 6,
B prefer_union_all = 1, prefer_join = 0,
B prefer_fix_blocking = 1, prefer_in_itab_opt = 1,
B convert AVG = 1, alias table FUPD = 0,
B escape_as_literal = 0, opt GE LE to BETWEEN = 0,
B select * =0x0b, character encoding =SBCS / <none>:-,
B use_hints = abap->1, dbif->0x3, upto->2147483647, rule_in->0,
B rule_fae->0, concat_fae->0, concat_fae_or->0
M SecAudit(RsauShmInit): WP attached to existing shared memory.
M SecAudit(RsauShmInit): addr of SCSA........... = 700000040000000
M SecAudit(RsauShmInit): addr of RSAUSHM........ = 700000040000450
M SecAudit(RsauShmInit): addr of RSAUSLOTINFO... = 700000040000488
M SecAudit(RsauShmInit): addr of RSAUSLOTS...... = 700000040000494
B create_con (con_name=LCA)
B Loading DB library '/usr/sap/QA1/SYS/exe/run/dbsdbslib.o' ...
B Library '/usr/sap/QA1/SYS/exe/run/dbsdbslib.o' loaded
B Version of '/usr/sap/QA1/SYS/exe/run/dbsdbslib.o' is "700.08", patchlevel (0.247)
B New connection 1 created
B Connect to LCA as SAPPL1 with us6pa1d02.na.cokecce.com-PL1
C
C DBSDBSLIB : version 700.08, patch 0.247 (Make PL 0.254)
C MAXDB shared library (dbsdbslib) patchlevels (last 10)
C (0.247) Use SCHEMANAME instead of OWNER for MaxDB 7.8 (note 1353266)
C (0.211) MVCC support for MaxDB (note 1332203)
C (0.204) Sapinst on windows/maxdb stop with error (note 1323436)
C (0.202) NUMC conversion corrected (note 1288313)
C (0.189) Default value for max. input variables is 2000 (note 655018)
C (0.189) Profile parameter to define max. input variables (note 655018)
C (0.188) Switch SQLMODE after CREATE INDEX SERIAL (note 1267841)
etc....
3. the user reports that the program was run with repair option. We will also submit one to do just checking, no repair. -
Split SNP PDS using BADI /SAPAPO/CURTO_SNP Method CIF_IMPORT
Hello APO ABAP experts,
The requirement is to split SNP PDS based on the number of modes. Meaning, the PDS should have only Mode per Activity in the Operations.
My plan was to change the changing internal tables in the method CIF_IMPORT to create number of SNP PDS depending up on Modes. But, i am not sure whether it is possible or not. Please suggest.
Note: BADI will be triggered once per each PDS.
Thanks,
Shaun.Saurabh,
Let me explain you what i am doing:
Since i need to split one PDS into multiple PDS, I am changing the fields EXT_PLANNR and EXT_NAME just by appending a counter. Once after i change them, adding the entries to the changing internal tables (CT_*). At the end of CIF_IMPORT, i am deleting the original PDS entries.
Example code:
LOOP AT ct_planactz INTO ls_planactz.
ls_planactz-ext_plannr = lv_new_ext_plannr.
APPEND ls_planactz TO lt_planactz.
ENDLOOP.
APPEND LINES OF lt_planactz TO ct_planactz.
Right now, for testing purpose - i am not splitting the PDS. I am just trying to create 2 SNP PDS by using one PDS. I want to test my code first to create multiple PDS.
When doing this, i get the following error:
Error: Activity 250006007010001-012 000600000004 P does not exist
Message no. /SAPAPO/CURTO005
Piece of standard code cuasing the problem:
LN 64 in method GET_APO_GUIDS.
READ TABLE ct_cif_planactz INTO ls_cif_planactz
WITH KEY actnr = ls_apo_planactz-r3actnr
plnkn = ls_apo_planactz-plnkn
zaehl = ls_apo_planactz-zaehl
phasenr = ls_apo_planactz-phasenr
uvorn = ls_apo_planactz-uvorn
BINARY SEARCH.
Call stack:
METHOD GET_APO_GUIDS
METHOD CREATE_RTO
METHOD CREATE_SNP_RTO
FUNCTION /SAPAPO/CUSLNTRTO_CREATE_RTO
Question:
May i know what is the significance of other fields in internal table ct_cif_planactz ? Since i am chaning only EXT_PLANNR field, above binary search is picking up the same entries and ignoring my second PDS.
I would appreciate if you can share your ideas.
Thanks,
Shaun. -
9ASVTTY (Safety Days Supply) UoM in table '/sapapo/tspaplob'
Hello All,
We faced an issue whereby the safety days supply was being displayed in Base UoM of the product like 'EA'. After further exploring this issue and comparing with standard SAP Planning Areas we found that a value of '10' has to be maintained against 9ASVTTY for field UOM_PLAN in table /sapapo/tspaplob.
After making this change the safety days supply is being displayed in DAYS again. Although the issue is resolved I still want to know what is the significance of maintaining this value '10' in the table. Also can we maintain a unit like 'D' or 'H'. After maintaining this value in the table I dont see any corresponding change in the Planning Area for 9ASVTTY, field 'UoM'.
An early reply is highly appreciated.
Thank You.
Abhi.Hi All,
There is this function module called by the Planning Administration view, called CONVERSION_EXIT_CUNIT_INPUT. Below is a code extract pointing to where exactly does the system equate D to "10"
IF sw_use_buffer EQ space
OR language NE sy-langu.
SELECT * FROM t006a UP TO 1 ROWS WHERE spras EQ language
AND mseh3 EQ input.
output = t006a-msehi.
ENDSELECT.
ELSE.
t006a_s_tab-mseh3 = input.
READ TABLE t006a_s_tab WITH KEY t006a_s_tab-mseh3 BINARY SEARCH.
output = t006a_s_tab-msehi.
ENDIF.
PERFORM get_t006b USING language mseh3
CHANGING output l_return_code.
From this code extract, we see that the value mapping of UoM is actually in table T006A. If you equate the UOM_PLAN field in the Planning Area field, with MSEHI of table T006A, the value at field MSEH3 or table T006A would reflect in the planning book.
Hope this helps -
/SAPAPO/BP1 - Transfer of forecast
Hello,
I would like to transfer the forecast from APO to third party system.
Can I use /sapapo/bp1 ?
Thank you
Regards
PratapThis transaction is sending the the transaction data, If it serve your purpose please use it.
Send Transaction Data
You can use this function to select and transfer transaction data (orders, stocks, and so on) to external (non-SAP) systems.
This function can be used to transfer data that was created by an external system (or an SAP system) or locally in SAP APO. (The function is not meant for transferring data to SAP systems. To do this, use the relevant CIF transfer functions.)
You can specify the following for the transfer:
The objects (for example, sales orders, external procurement orders, and so on) that are selected and transferred, and the criteria used to do this.
Possible Selection Criteria
You can enter the product or locations to select the data. You can choose whether to use external names (as they are used in the BAPIs or the external system, for example) or internal names (as they are used in SAP APO). Only master data that is either known to or defined in the logical system or system group specified is selected.
Alternatively, the data can be selected using order numbers. Note that in this case only objects can be selected that can have order numbers. (Stocks or planned independent requirements, for example, cannot then be transferred). Note also that there can also be many orders (for example, generated by SNP) without an order number. Orders that have been created by external systems are selected using the logical system specified. That is, only orders for the logical system specified are selected. All orders that are local to SAP APO (order type 8) are selected.
Specify also which planning version is to be used and which objects (for example, stocks, orders, and so on) are to be transferred.
Specify also whether the transfer is to be direct or whether the objects to be transferred should only be selected and displayed at first. If you set the indicator "Display Selections" the objects are selected and displayed. You can then transfer them in a later step.
2. Extended Selection Criteria
When selecting by location product you can also use the following selection criteria:
By default, only orders that were created locally in SAP APO or transferred from the logical system specified are selected. In the case of planned independent requirements and stocks, all objects that exist in the system group specified are selected. You can also specify in the extended selections whether orders that are in the same system group but which were transferred from a different logical system are also to be selected.
When selecting by location product (not order number), the following selection parameters are also available. In this case, only objects where at least one location product meets these criteria are selected.
Selection by certain ATP categories. Note that you can only enter individual values for these selection criteria. You cannot enter intervals or exclude elements.
You can specify whether only location products for certain planners are to be selected.
Furthermore, you can also specify whether to select by receipt element only, requirements element only, or according to both. This is only possible for orders and not for stocks or planned independent requirements, for example. By default, the system searches for receipt and requirements elements. If you specify that the system is only to search for receipt elements, only orders/schedule lines are selected where the location products from the selection appear in the receipt elements. With the exception of VMI orders, selecting sales orders/deliveries in this way does not usually return useful results, since these consist solely of requirements elements.
If, instead, you want to select by requirements element only, only orders/schedule lines are selected where the location products from the selection appear in the requirements elements. For stock transfers this means, for example, that you can also specify whether the selection should be based on requirements or receipts.
For the "self-defined selection", you can enter any values that you want. Their interpretation depends on the customer implementation (BAdI implementation). Further technical details are provided at the end of this document.
Selection by certain order types. Note that when entering values for these selection criteria you can only enter individual values. You cannot enter intervals or exclude elements.
Selection by time interval. Only orders/planned independent requirements that lie either completely or partially within this time interval are transferred. This does not affect the transfer of stocks using object "StockAPS". The following information is necessary to specify a time interval:
The type of time interval: That is, is a calendar day, calendar week, or a relative period of time entered.
The start and end of the interval. The entry must be made in accordance with the type of time interval. For more information, see the F1 help for the time interval. Note that you cannot use the input help (F4) for this.
You can optionally specify which time zone is used. The time stamps for the interval start and end are calculated from the interval specified and displayed in UTC time.
When using a time interval to transfer requirements/receipt elements, note that making a selection according to start and/or end time only delivers useful results for objects that have actual dates/ times. Since stocks, for example, do not have dates/times, you are not advised, as a rule, to use these selection parameters for stocks.
Specifying the selection mode: This is only possible in certain application cases, since restrictions exist. You must note these restrictions. For more information, see the F1 help for the selection mode.
3. Log/Technical Transfer Parameters
You can use these to specify how the data is to be sent and where is it to be sent to. You can also configure whether the selected data is to first be displayed before the transfer and then transferred in another step, or whether the transfer is to take place immediately.
Send mode:
You use the send mode to specify whether the data is to be sent as IDocs, tRFC, or both (if configured in Customizing).
Target system:
If you want to send the data to a particular target system, specify it here. The target system must be entered in Customizing correctly. The target system does not need to be specified if the distribution model is used, since the target systems are determined automatically in this case.
Use distribution model:
If the distribution model is used, the ALE distribution model is read and the target systems are determined automatically. If you do not want to send data to all target systems entered, specify the target system as described above.
Display selections
Here you can specify whether the selection results are displayed before the data is transferred. The data is then transferred in another step. This can be helpful when checking the size of the data selected, the correctness of the data, and the target systems that were found.
The items "performance/packaging/error checks" and "transfer details" are dealt with later on.
Integration
Standard BAPIs are used for selecting and transferring the objects. The technical integration requires that you understand these BAPIs and objects (for example, which objects and data are selected and how the transfer works from a technical point of view, which fields are available, and so on).
1.Which data can be selected and transferred:
You can select and transfer the following objects or data. The transaction data must be available in SAP APO liveCache.
"SalesOrderAPS" (BUS10501). This corresponds to sales orders, deliveries, and so on.
The entire order (that is, with all items/schedule lines) is always transferred, as soon as an item matches the selection criteria.
"ProcurementOrderAPS" (BUS10502). This corresponds to external procurement orders such as purchase orders, stock transfers, and so on.
The entire order (that is, with all items/schedule lines) is always transferred, as soon as an item matches the selection criteria.
"ManufactOrderAPS" (BUS10503). This corresponds to in-house production orders such as planned orders or production orders.
The entire order is always transferred. If there are RPM components, these are also selected and transferred.
"StockAPS" (BUS10504). This corresponds to stocks.
"PlannedIndReqmtsAPS" (BUS10020). This corresponds to planned independent requirements.
Requirements/receipt elements. This roughly corresponds to a requirements/stock list or product view.
You can find the relevant interfaces (parameters, fields) for the "Receive" methods and the business objects in the BAPI Explorer. There you can also find the relevant ALE interfaces and function module interfaces for the "Receive" methods.
2. How is the data transferred:
The data is transferred using the interface objects or the following BAPIs (or ALE message types for the BAPIs):
"ProductAPS.GetList2" is used to determine the location products for the object selection.
Sales orders, deliveries,and so on:
"SalesOrderAPS.GetList2" or "SalesOrderAPS.RequestList2" is used to select the data. The data is transferred using "IF10501.ReceiveList2".
External procurement orders:
"ProcurementOrderAPS.GetList2" or "ProcurementOrderAPS.RequestList2" is used to select the data. The data is transferred using "IF10502.ReceiveList2".
In-house production orders:
"ManufactOrderAPS.GetList2" or "ManufactOrderAPS.RequestList2" is used to select the data. The data is transferred using "IF10503.ReceiveList2".
Stocks:
"StockAPS.GetList2" or "StockAPS.RequestList2" is used to select the data. The data is transferred using "IF10504.ReceiveList2".
Planned independent requirements:
"PlannedIndReqmtsAPS.GetList" or "PlannedIndReqmtsAPS.RequestList" is used to select the data. The data is transferred using "IF10020.ReceiveList".
Requirements/receipt elements:
"PPDSServiceAPS.GetReqsReceipts" or "PlannedIndReqmtsAPS.RequestReqsReceipts" is used to select the data. The data is transferred using "IF10500.ReceiveReqsReceipts".
If user exits or BAdI implementations are used within the BAPIs mentioned, you must take these into account since they are also run through. This can influence the result. You can also find more information about the named selection methods in the BAPI Explorer.
3. What must be taken into account for the selection and transfer of data:
The factors packaging, transfer type and error handling play an important role when selecting and transferring large volumes of data, in particular. Without packaging, for example, performance problems, memory overflows, or terminations can occur in the case of large volumes of data. This must be taken into account for both the sending (SAP APO) system and the receiving system. The main reason for this is that the entire volume of data is selected and transferred at once if packaging is not used. This may be desired and possible for a small number of objects. However, packaging is recommended for medium and large volumes of data. Since the package size depends on the data constellations, there is no "optimum" package size. For this reason, you must check which package size is most optimal for each scenario and data volume. When using ALE IDocs it is not recommended that you send IDocs with several thousand segments.
3.1. You can use the setting "Performance/Packaging/Error Checks" to control the package size.
You can specify a package size for location products when selecting data using location products. If the entry made is > 0, objects for the selected location products are transferred in various packages. If an order contains various location products, it is not split into several packages. Instead, an internal decision is made about the package or location product to which it is assigned for packaging.
Package size per object type. Here you can specify the maximum number of orders, stocks, and so on that are to be contained within a package. This packaging occurs in addition to the packaging by location product described above. For example, 30,000 in-house production orders can exist for a location product. If packaging by location product, all 30,000 orders would be sent in one package. By packaging the orders per object type, the package containing 30,000 orders is split into smaller packages (for example, 300 * 100 orders). If no entry is made here, packaging does not occur for the relevant object type.
Packaging for in-house production, external procurement, and sales orders/deliveries occurs on order level. That is, a package size of one means that one order is contained in one package.
Packaging for planned independent requirements occurs on schedule line level (SCHEDID). That is, a package size of one means that one planned independent requirement for a location product is contained in one package.
Packaging for stocks occurs on stock level. That is, a package size of one means that one stock for a location product is contained in one package.
Packaging for requirements/receipt elements occurs on schedule line level, That is, a package size of one means that one schedule line (related to parameter IO_ELEMENTS) is contained in one package. Note that in the dependent parameters (for example, if order details or order headers for the schedule lines are transferred) redundant data may be transferred.
You must also consider error handling, that is, how the system is to react to messages that may be generated. You can distinguish between three different error or message situations:
Errors/messages during preselection
Before the data is transferred, a preselection of objects is made to determine the objects to be transferred and to give the user an overview of the objects that match the selection. This preselection is displayed, for example, if you have chosen "Display Selections". If errors occur during the preselection, you can choose "Termt. If Select. Error Occurs" to specify that no objects are to be transferred and that the entire transaction is to be terminated.
It is not usually advisable to transfer data if a serious error has occurred during the selection, since this would falsify the selection result. To nevertheless force the data to be transferred, you can deactivate "Termt. If Select. Error Occurs". This can be useful, for example, when errors occur that you know are not relevant to the transfer.
If you do deactivate "Termt. If Select. Error Occurs", you must ensure that no incorrect selection results are transferred.
Errors during object details selection
When the transfer has been started, the detailed data for the objects orders, stocks, and so on) is read according to the preselection quantity. (Error) messages can occur here. These messages are transferred by default to the target system in parameter RETURN_MESSAGES.
You can control whether these messages are to be considered and, if so, how they are considered. The same is true for logging and displaying the messages.
"Add to Log" specifies that these messages are added to the log. If they are not added, the user in the sending SAP APO cannot see if errors have occurred during the selection. The errors are simply transferred to the target system. The method of simply transferring the errors to the target system can be used if only the target system is to deal with error handling and not the sending system.
If these messages are added to the log, you can also specify whether the messages are to determine whether or not the relevant package (for which errors have occurred) is to be transferred or not. The option "Always Transfer" means that messages do not influence the transfer. "No Transfer if Error or Termination Messages Occur" means that the relevant data package is not transferred, if these message types occur during the object details selection. A termination message for this package is then added to the log to show that the package was not transferred.
"No Duplicate Messages" means that the number of messages in the log is reduced. If conversion errors occur, the same message can occur for several orders. This means that the message appears in the log several times, but contains different order numbers. To make it easier to see the errors in the log, you can suppress multiple duplicated messages.
Errors during the technical transfer
These include errors when generating IDocs or other errors of a technical nature that prevent the data package from being transferred or created. The relevant data package is displayed with a termination message in the log.
In some cases you need to terminate processing, for example, when almost every package has errors (for example, caused by general system problems). It is then probably not advisable to continue processing as this would lead to long runtimes and many log errors (for the packages with errors). To avoid such situations, you can use the parameter "Max. Faulty Packages" to specify that processing is to be terminated once a certain number of faulty packages is exceeded. Note that this only refers to the number of packages that were not transferred and not to the error (messages) that have occurred in general.
3.2. Transfer details
A lot of data can exist for one object (for example, order, stock, and so on). An in-house production order, for example, has header data, receipt information, requirements, operations, activities, pegging information, and much other data that is contained in separate parameters in the interface. It takes time and memory space to read and transfer all of this data. In many cases, transferring all this detailed data is not necessary or desired. You can specify in the transfer details which detailed data is to be transferred or not transferred for which object or indeed for all objects. In this way, you can specify that pegging information for all objects is not to be transferred, for example.
For performance reasons you are advised to only transfer the data that you actually need.
By default, only the minimal data for the objects is transferred (for example, for in-house production orders only the order header data is transferred and no operations, activities, and so on are transferred).
3.3 Miscellaneous
Only errors that occur during the selection or creation of the packages are displayed in the log. The packages are considered to have been transferred or created successfully, as soon as it was possible to transfer them to the relevant middleware, (for example, IDoc was generated, tRFC was generated, and so on). If errors occur later on in processing (for example, IDoc could not be sent or tRFC could not be sent, because the target system is not available, and so on), these messages are not displayed in the log. Instead you must use the relevant monitoring option (depending on the transfer technique/middleware in use), for example IDoc Monitoring, or tRFC Monitoring, and so on).
When packaging data by object type it can be the case (especially when sending requirements/stock lists) that data for an order is distributed across several packages. If, for example, when sending the requirements/stock list a package size of 1 is configured and an order exists with two items for the same location product, these two are shared between two packages. Since the same detailed data for the entire order (that is, both items) can be contained in each package, it could be the case that partially redundant information is contained in the packages that are transferred.
BAdI definition "APO_BAPI_SENDTRANS" is available for enhancements.
BAdI definitions (for example, "APO_BAPI_BUS10503" for in-house production) are also available in the RECEIVE interfaces. You can use these, for example, to implement a receive function (if the data is not to be sent to an external system, for example).
Prerequisites
You must specify the target system(s) to transfer the data. Depending on the means with which you want to transfer the data, you must be familiar with RFC or ALE Customizing. The following information is only meant as overview and does not go into details about the individual Customizing settings.
A logical system must exist that represents the target system.
In the ALE distribution model (transaction BD64) you must have configured which "Receive" calls are used for which target systems. For example, you can enter "IF10503.ReceiveList2" for in-house production orders. To do this, use "Insert BAPI". (Do not use "Insert Message Type".)
Define an RFC destination (transaction SM59) for the target system, if the data is to be transferred using RFC.
If the data is to be transferred using tRFC or RFC (that is, not transferred using ALE message types), assign an RFC destination to the BAPI method calls (for example, "IF10503.ReceiveList2"). You can do this in ALE Customizing (transaction BD97).
When using ALE message types for the BAPI method calls, you must also make additional Customizing settings for partner agreements, ports, and so on.
You must have authorization to display the planning version (C_APO_VERS) and for the transaction.
Output
Logging
All objects that match the selection and can be transferred are written into the log. When using simulation mode, the selection result can be displayed before the data is transferred. An entry is created in the log for each object to be transferred. For objects that have multiple elements (for example, stock transfers or in-house production orders), not all components or location products are logged, for example. In the case of manufacturing orders, for example, not all components are logged. Instead one entry is made. In the case of stock transfers, for example, the source and destination are not logged. Instead one entry is made. The location product that was contained in the selection criteria is the one that is logged. If several location products from the selection are contained in an order, the location product from the selection that has the most "significance" is used, for example, the main product for in-house production orders or the receipt element for stock transfers.
The location product that is specified in the log for an order/schedule line also determines the package in which this order is processed (for example, for packaging by location product).
You should delete obsolete logs at regular intervals.
How and to which target systems these objects are to be sent.
Whether all detailed data for an object is to be transferred or only parts of it (for example, no characteristics information is transferred).
These points will now be considered in detail. -
Significance of Interfaces in ABAP Objects
Hi Guys, here I have a query -
Why do we use Interfaces in ABAP Objects?, and what is the significance of Interfaces in ABAP Objects?
Please clarify the above with a suitable example.Moderator message - Welcome to SCN.
But
Moderator message - But this isn't a training forum. Please ask a specific question - post locked -
Message /SAPAPO/SDP_PAR023: "Some CVCs cannot be processed in block..."
Hi,
We are using SAP SCM release 5.1, the component Demand Planning. We are running macros in background jobs, e.g. a macro that populates a key figure by summarizing other key figures etc. We are using parallel processing, configured based on recommendation from SAP. When the number of CVCs to be processed by the macros becomes very high (we are processing ~300.000 CVCs at the moment), we get the following message in the job log in SM37:
"Some CVCs cannot be processed in block 2 ", message number /SAPAPO/SDP_PAR023. Obviously the block number varies, and in our case we have had the above message for up to 19 blocks. Users have spotted CVC's that were not updated by the background job, but we don't have a specific list of the CVCs that were not processed.
OSS notes mentioning this behaviour:
Note 1282811 - Error processing 1 CVC, terminates the Parallel Profile
Note 1501424 - DP Job with parallel processing - job status message
Note 1494099 - DP Job with parallel processing - job status
The question below is only to those who have encountered the same message in a DP background job:
Did you find a log of the CVCs that were not processed, and what did you do to overcome the problem?
Thanks in advance!
Kind regards,
Geir KronkvistHi Rico,
Thanks for your reply! The spool consists of 23.145 pages so I looked for the word "Lock" using the "Find in request" in the "Spool request" menu. The searched found two entries where there was a message stating that a CVC was locked. It must be noted that no users are logged on while our background job is running, and there are no other processes (background or dialog) running in parallel. When checking transaction SM12 prior to running the job, there are no locks in the system.
Our job schedule consists of a nightly process chain transferring data from BI to liveCache, and a monthly job that prepares historical data and calculates the forecast. We are now running the monthly job.
Is it possible that the parallel processing may cause the locking by itself?
Kind regards,
Geir Kronkvist
Maybe you are looking for
-
Best partitioning strategy for OS 8.6?
Hello, I have two hard drives on my beige 233 MHz G3 minitower (rev 1): 4 GIG SCSI 80 GIG ATA I need to install OS 8.6. I was considering using both drives but I do not know what I should put on each drive. Should I install OS 8.6 onto the 4 GIG driv
-
Does anyone know how to do this? Open one file in Photoshop by Script? Bellow the Script. tell application "Adobe Photoshop CS" activate open every file of pasta_meio end tell tell application "Adobe Photoshop CS" do action "Bordado" from "Bmp" end t
-
How do I transfer emails from a non-active superseded inbox to local files.
I have changed servers and cancelled my old server (email service). I want to transfer all my old emails from my old inbox into local folders so I can delete the old account. I have a new account and a new inbox which is working fine. When I try to t
-
Best practice for Retina display folios
Creating a brand new app from scratch, optimised for retina display, but compatible with older iPads, what is the best page dimensions and image resolutions to use? Thanks
-
Querying data from External Source from FORMS
I have a form that is built based on Oracle tables. But I need to get data from external Data source from within Forms and use it fro validation. I need to execute a Select statement via ODBC from within Forms procedures. This is going to a SQL Serve