SCN: Message List

HI Naresh,

S&OP supports two methods to transport Model Configuration from Source to Target Systems. These are DU based transport and SQL based transport. SQL based transport is preferred method if you want to copy model between two systems.

Caution: The Transport mechanism is a beta feature. We cannot support any issues encountered using this feature. This is only intended for expert users only with access to SAP HANA Studio or XS Studio. Always backup your database before performing such action.

SQL based Export/Import

Export:

1. Open Chrome and Log onto the SAP S&OP web UI with a user who has "REPO EXPORT" system privilege
2. Make sure that the planning area you want to export is activated
3. Open a new tab in the same browser as you logged into and provide the following URL:

https://<server>/sap/sop/sopfnd/services/model_transport/modelCopy.xsjs?action=copyModel&oldPrefix=SM1&newPrefix=SM1&oldPlarea=SAPMODEL1&newPlarea=SAPMODEL1&newTPID=1

4. Provide the parameters values for oldPrefix , newPrefix, oldPlarea and newPlarea. For example, oldPrefix is usually the 3 letter prefix for attributes and Master Data Types. eg SM1 for SAP delivered SAPMODEL1. You can have the same value for new and old prefixes, and new and old planning areas and the same TPID to export and import the same model.

5.In your browser, you need to select "view page source" to view the result page as text, then copy and paste the SQL into a file.

The URL will return a file with SQL statements that will construct an inactive version of the model in target system.

Import:

1. Back up the database before you import the planning area. This prevents accidental deletion of configuration or data.

2. Use HDB Studio or the SAP Hana XS IDE Catalogue tool to run the SQL statements in the target system.

3. Run the SQL statements with SOPADMIN (or a similarly privileged user). This deletes the inactive entries in the target system if the same planning model, master data types, and attributes already exist.

If the SQL is long, split it to 500 sqls per SQL run.

4. Activate the model by activating Master Data Types , Time Profile and Planning Area.

Note for On Demand customers: Web access XS IDE is not enabled for customer production systems. Import is currently only allowed by SAP for production systems. File a support ticket if you need the model exported.

We are working on making this transport feature more robust.

Hope this information helps.

Thanks,

Raghav

Hi Midhun,

I am using a standard released BAPI i.e. BAPI_ALM_NOTIF_CLOSE.

Saurabh

Hi Anil,

while you are copying the wage type an entry would be created automatically in T52EZ. If it isn't, create a new entry in T52EZ.

That would remove the error.

Thanks

Madhav.

@Jurgen - Thanks, Please find below the detailed process and what i planned.

1. When the vendor bring the goods to, We will create a purchase order with consignment (Consignment Info Record = 1 USD - temporarily)

each line item entered considered as Pallet i.e if the same article has 2 pallets with 55 Cartons and 60 Cartons each,then the user will create two line items

2.The batch will be created for each line item through BAPI for each pallet (1 Line Item = 1 Batch = 1 Pallet ) the same will be printed as barcode label will be printed

3. In the receiving area the user will scan the pallet barcode will make goods receipts against purchase order,the stock will be moved to consignment (One Pallet = One GR ) since this will be done via RF Devices , the user will hand held device to receive each pallet

4. When auction is performed and sold a sales order will be created for each batch = Pallet and immediately through BAPI material document will be posted (411 K) ,here through user exit new selling price will be passed - HOPE THIS WILL WORK

5.This stock will be delivered to customer ,the catch here i can not post this in a via background job ,since the pallets has to be delivered immediately to the respective stalls.means as soon as auction performed the pallet will be moved to the respective stall(Customers Stall) existing in the Trade Center

Is the above is possible or we may need to do additional 2nd PO to receive the goods ,please advice

Hi Praveen,

as working with sap abap you must get enough exposure in basic modules like SD or MM, so why not you try with these options too, ok if you thinks about BI, BODS or HANA, remember HANA is a database related tool,

SAP BI : According to the standard definition of BI ,SAP BusinessObjects business intelligence (BI) solutions simplify data manipulation, allowing users to access, navigate, analyze, format, and share information across a corporate environment. The products allow a wide range of processes, from search and navigation to advanced analytics, enterprise query, reporting and analysis, dashboards and visualization, and information infrastructure management.

BODS : BODS is an ETL tool by SAP used for integration with all types of disparate systems, extracting data from them, transforming them into meaningful information and loading them into all types of systems.

SAP HANA : SAP HANA converges database and application platform capabilities in-memory to transform transactions, analytics, text analysis, predictive and spatial processing so businesses can operate in real-time

So, please search about these modules and see in which module you find yourself more explanatory in terms of understandings and manipulating, if you will judge yourself then i think it will be more fruitful to you in shaping your career and future.

Where is the tomcat cache that I can delete it?

Thanks.

Simon

Hi experts

Would you have any experience/best practice in designing for cycle count process for your clients?

By cycle count, I mean for frequent counting (daily) for specific item category / exceptional count request.

My client want to implement a cycle count process to minimize the effort for full stock take which happen around 3 times per year.

They are using SAP as the core system to keep track of inventory, and using external store system, so some considerations would be on, for example:

- whether the count variance or counted quantity shall be interfaced back to SAP

- whether SAP should be the source to initiate a stock count process or POS initiate

It would be very nice if you can share some best practice as in the process flow, system information flow, etc.

Best regards

Dominic

hi all,

I found the solution for above problem while going through Jose's Discussion on Creation of Addons for SAP Business One Studio( Creation of Addons for SAP Business One Studio )

it has been due to the argument parameter number pass to instantiate a instance of SAPbouiCOM.Framework.Application class...

it seem's the default index given when project creation is incorrect...

Many thanks to Jose Karlo Martinez and Edy Simon...

I have basic problems. I am not able to find right sample codes. I have two simple forms. When I click on the button of the form1, it creates new form2. But form2 is not able to find the grid on the form. Both forms are attached. I am using Visual Studio for SAP Business One.

Option Strict Off

Option Explicit On

Imports SAPbouiCOM.Framework

Namespace SBOAddonProject1

<FormAttribute("SBOAddonProject1.Form1", "Form1.b1f")>

Friend Class Form1

Inherits UserFormBase

Public Sub New()

End Sub

Public Overrides Sub OnInitializeComponent()

Me.Button0 = CType(Me.GetItem("Item_0").Specific, SAPbouiCOM.Button)

Me.Grid0 = CType(Me.GetItem("Item_1").Specific, SAPbouiCOM.Grid)

End Sub

Public Overrides Sub OnInitializeFormEvents()

End Sub

Private WithEvents Button0 As SAPbouiCOM.Button

Private Sub Button0_ClickBefore(sboObject As System.Object, pVal As SAPbouiCOM.SBOItemEventArg, ByRef BubbleEvent As System.Boolean) Handles Button0.ClickBefore

Dim frm As Form2

frm = New Form2()

frm.Show()

End Sub

Private WithEvents Grid0 As SAPbouiCOM.Grid

End Class

End Namespace

Option Strict Off

Option Explicit On

Imports SAPbouiCOM.Framework

Namespace SBOAddonProject1

<FormAttribute("SBOAddonProject1.Form2", "Form2.b1f")>

Friend Class Form2

Inherits UserFormBase

Public Sub New()

End Sub

Public Overrides Sub OnInitializeComponent()

Me.Grid0 = CType(Me.GetItem("Item_0").Specific, SAPbouiCOM.Grid)

End Sub

Public Overrides Sub OnInitializeFormEvents()

AddHandler LoadAfter, AddressOf Me.Form_LoadAfter

End Sub

Private WithEvents Grid0 As SAPbouiCOM.Grid

Private Sub Form_LoadAfter(pVal As SAPbouiCOM.SBOItemEventArg)

Dim frm As SAPbouiCOM.Form

frm = Application.SBO_Application.Forms.Item(1)

Dim dt As SAPbouiCOM.DataTable

Try

dt = frm.DataSources.DataTables.Item("dt1")

Catch ex As Exception

frm.DataSources.DataTables.Add("dt1")

dt = frm.DataSources.DataTables.Item("dt1")

dt.Columns.Add("Column1", SAPbouiCOM.BoFieldsType.ft_AlphaNumeric, 254)

dt.Columns.Add("Column2", SAPbouiCOM.BoFieldsType.ft_AlphaNumeric, 254)

dt.Columns.Add("Column3", SAPbouiCOM.BoFieldsType.ft_AlphaNumeric, 254)

End Try

dt.Rows.Add(1)

dt.SetValue("Column1", 0, "Value1 - row 1")

dt.SetValue("Column2", 0, "Value2 - row 1")

dt.SetValue("Column3", 0, "Value3 - row 1")

dt.Rows.Add(1)

dt.SetValue("Column1", 1, "Value1 - row 2")

dt.SetValue("Column2", 1, "Value2 - row 2")

dt.SetValue("Column3", 1, "Value3 - row 2")

Grid0.DataTable = dt

End Sub

End Class

End Namespac

Hi All,

I have to configure an scenario of sender JDBC to receiver RFC wherein SAP PI will be pulling data from third party database (Oracle).

Since I am configuring such scenario of sender JDBC, I want help on every important key aspects/prerequisites of configuring sender JDBC adapter/channel. I want to understand about Database Connection, Processing Parameters, etc. details while configuring sender JDBC channel and their significance/relevance.

Also I need guidelines about the source data structure (message type or external definition) to be used/created in ESR.

How sender JDBC channel and receiver JDBC channel differs from each other?

Please guide me on this.

Thanks & Regards,

Amit Patil

Hi Zhang

You can try changing in the substituion exit the same but you wil have to make sure the sum of credit and debit remains the same else it wont post

Nabheet

Sunil,

What is the full message text including message number?

PeteA

Hi Friends,

I am facing a problems in ECC 6.0 , while accessing ST02 - history getting following dump . can you please help me. when ever iam executing the sto2 tcode immediately getting the dump . please find the below dump details: Runtime Errors please help me to sort out of this issue

Regards

suresh m

Find abap dump error

Runtime Errors COMPUTE_BCD_OVERFLOW

Exception CX_SY_ARITHMETIC_OVERFLOW

Runtime Errors	COMPUTE_BCD_OVERFLOW
Exception	CX_SY_ARITHMETIC_OVERFLOW
Date and Time	03.04.2014 09:40:59

Short text
	Overflow during the arithmetical operation (type P) in program "RSTUNE50".

What happened?
	Error in the ABAP Application Program

	The current ABAP program "RSTUNE50" had to be terminated because it has
	come across a statement that unfortunately cannot be executed.

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.

Error analysis
	An exception occurred that is explained in detail below.
	The exception, which is assigned to class 'CX_SY_ARITHMETIC_OVERFLOW', was not
	caught in
	procedure "WRITE_MAIN_LINE" "(FORM)", nor was it propagated by a RAISING
	clause.
	Since the caller of the procedure could not have anticipated that the
	exception would occur, the current program is terminated.
	The reason for the exception is:
	An overflow was discovered in an ongoing arithmetical operation with
	operands of type P. Possible causes are:

	1. The result field of type P is too small for the result.

	2. The result or a intermediate result has more than 31 decimal places.

How to correct the error
	The result field must be enlarged, if this is still possible. It may
	also be possible to break up the current process into subprocesses so
	that only smaller values occur.


	There may already be a solution to the error in the SAP notes system.
	If you have access to the SAP notes system first try searching with the
	following keywords:
	"COMPUTE_BCD_OVERFLOW"
	"BCD_FIELD_OVERFLOW" (Until release 4.0a, this runtime error occurred at this
	position)
	"RSTUNE50" or "UNE50F01_ALV"
	"WRITE_MAIN_LINE"

	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
	"WRITE_MAIN_LINE" "(FORM)", 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... "psprd1"
	Network address...... "192.168.0.190"
	Operating system..... "Windows NT"
	Release.............. "5.2"
	Hardware type........ "8x AMD64 Level"
	Character length.... 16 Bits
	Pointer length....... 64 Bits
	Work process number.. 0
	Shortdump setting.... "full"

	Database server... "PSPRD1"
	Database type..... "MSSQL"
	Database name..... "PRD"
	Database user ID.. "prd"

	Char.set.... "C"

	SAP kernel....... 700
	created (date)... "Jun 12 2012 22:57:20"
	create on........ "NT 5.2 3790 Service Pack 2 x86 MS VC++ 14.00"
	Database version. "SQL_Server_8.00 "

	Patch level. 347
	Patch text.. " "

	Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
	SAP database version. 700
	Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
	NT 6.0, Windows NT 6.1, Windows NT 6.2"

	Memory consumption
	Roll.... 16192
	EM...... 16759360
	Heap.... 0
	Page.... 40960
	MM Used. 5861120
	MM Free. 6705328

User and Transaction

	Client.............. 600
	User................ "BASIS"
	Language key........ "E"
	Transaction......... "ST02 "
	Transactions ID..... "F5E5BAE3AE80F1CB9D5D001A6466DE70"

	Program............. "RSTUNE50"
	Screen.............. "SAPMSSY0 1000"
	Screen line......... 6

Information on where terminated
	Termination occurred in the ABAP program "RSTUNE50" - in "WRITE_MAIN_LINE".
	The main program was "RSTUNE50 ".

	In the source code you have the termination point in line 1403
	of the (Include) program "UNE50F01_ALV".
	The termination is caused because exception "CX_SY_ARITHMETIC_OVERFLOW"
	occurred in
	procedure "WRITE_MAIN_LINE" "(FORM)", but it was neither handled locally nor
	declared
	in the RAISING clause of its signature.

	The procedure is in program "RSTUNE50 "; its source code begins in line
	1323 of the (Include program "UNE50F01_ALV ".

Source Code Extract
Line	SourceCde
1373 ENDIF.
1374 IF LINE_CMD = 'EXIM'.
1375	MOVE 'Export/import' to GS_OUTTAB-NAME.
1376 ENDIF.
1377 IF LINE_CMD = 'ESM'.
1378	MOVE 'Exp./ Imp. SHM' to GS_OUTTAB-NAME.
1379 ENDIF.
1380 *END OF CODING BY C5056319 ON 07/08/2004*
1381 if sy-subrc <> 0.
1382	move-corresponding buffer_statistic to buffer_statistic_64.
1383 endif.
1384
1385 move-corresponding buffer_statistic_64 to tunehd64.
1386 move-corresponding buffer_statistic_64 to sapbufqual.
1387 if tunehd64-frame_size = 0.	"buffer doesn't use frames
1388	free_size = tunehd64-avail_size - tunehd64-used_space.
1389 else.
1390	free_size = ( ( tunehd64-avail_size * 1024 ) - "-> bytes
1391	( tunehd64-alloc_frms * tunehd64-frame_size ) ) / 1024.
1392 endif.
1393 if ( buffer ne 'TABL' ) and
1394	( buffer ne 'FTAB' ) and
1395	( buffer ne 'TTAB' ) and
1396	( buffer ne 'SNTAB' ) and
1397	( buffer ne 'IRBD' ).
1398	free_dir	= tunehd64-max_objcts - tunehd64-act_objcts.
1399 else.
1400	free_dir	= tunehd64-max_objcts - tunehd64-con_objcts.
1401 endif.
1402 if tunehd64-avail_size ne 0.
>>>>>	free_size_p = free_size * 100 / tunehd64-avail_size.
1404 else.
1405	free_size_p = 0.
1406 endif.
1407 free_dir_p = free_dir * 100 / tunehd64-max_objcts.
1408
1409 *START OF COMMENTING BY C5056319 ON 05/08/2004*
1410 * write: (2) space,
1411 *	(8) sapbufqual-hitratio decimals 2
1412 *	color col_normal intensified off,
1413 *	'' no-gap,
1414 *	(12) tunehd64-alloc_size
1415 *	color col_normal intensified off.
1416 *END OF COMMENTING BY C5056319 ON 05/08/2004*
1417
1418 *START OF CODING BY C5056319 ON 05/08/2004*
1419 move: sapbufqual-hitratio to GS_OUTTAB-HITRATIO,
1420	tunehd64-alloc_size to GS_OUTTAB-ALLOC_SIZE.
1421 *END OF CODING BY C5056319 ON 05/08/2004*
1422 if free_size <= 0.

Contents of system fields
Name		Val.
SY-SUBRC 0
SY-INDEX 0
SY-TABIX 4
SY-DBCNT 1
SY-FDPOS 255
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY
SY-UCOMM
SY-TITLE Tune Summary (psprd1_PRD_00)
SY-MSGTY E
SY-MSGID DA
SY-MSGNO 300
SY-MSGV1 DDNTF
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO 0
SY-DATUM 20140403
SY-UZEIT 094059
SY-XPROG SAPLSCSMROUTE
SY-XFORM %_INIT_PBO_FIRST

Active Calls/Events
No. Ty.	Program	Include	Line
	Name
	4 FORM	RSTUNE50	UNE50F01_ALV	1403
	WRITE_MAIN_LINE
	3 FORM	RSTUNE50	UNE50F01_ALV	1005
	WRITE_MAIN_LIST
	2 FORM	RSTUNE50	UNE50F01_ALV	176
	WRITE_LIST
	1 EVENT	RSTUNE50	UNE50E01_ALV	10
	START-OF-SELECTION

Chosen variables
Name
	Val.
No.	4 Ty.	FORM
Name WRITE_MAIN_LINE
BUFFER
	IRBD
	45442
	92240
	00000
	00000
SYST-REPID
	RSTUNE50
	5555443322222222222222222222222222222222
	2345E55000000000000000000000000000000000
	0000000000000000000000000000000000000000
	0000000000000000000000000000000000000000
RSJOBINFO
	00000000000000	##
	2222222222222222222222222222222233333333333333222222222222222222222222222222222200
	0000000000000000000000000000000000000000000000000000000000000000000000000000000000
	0000000000000000000000000000000000000000000000000000000000000000000000000000000000
	0000000000000000000000000000000000000000000000000000000000000000000000000000000000
GT_FIELDCAT1
	Table[initial]
COUNT_RETN
	0
	0000
	0000
GC_SET_PF_STATUS_MEM_DETAILS
	SET_PF_STATUS_MEM_DETAILS
	545554555455554445445444522222
	354F06F341453FD5DF45419C300000
	000000000000000000000000000000
	000000000000000000000000000000
GC_STRUC_ALLOC2
	GT_MEMORY_ALLOC_PROC2
	455444455544444555443222222222
	74FD5DF29F1CCF3F02F32000000000
	000000000000000000000000000000
	000000000000000000000000000000
TUNEHD64-AVAIL_SIZE
	###########
	00000000000
	0000000060C
SPACE

	2
	0
	0
	0
FREE_SIZE
	####C#P#s#M
	00104959794
	0081380432D
FREE_SIZE_P
	########
	00000000
	0000000C
FREE_DIR
	###########
	00000000011
	0000000070C
TUNEHD64-MAX_OBJCTS
	#########u#
	00000000070
	0000000095C
FREE_DIR_P
	########
	00000000
	0000000C
GC_STRUC4
	GT_MEMORY_DETAIL
	455444455544544422222222222222
	74FD5DF29F45419C00000000000000
	000000000000000000000000000000
	000000000000000000000000000000
GS_OUTTAB-HITRATIO
	####
	0000
	000C
SAPBUFQUAL-HITRATIO
	##q#
	0971
	631C
No.	3 Ty.	FORM
Name WRITE_MAIN_LIST
GT_OUTTAB
	Table IT_138[4x152]
	\PROGRAM=RSTUNE50\DATA=GT_OUTTAB
	Table reference: 19
	TABH+ 0(20) = A02E0100DF070000000000000000000000000000
	TABH+ 20(20) = 130000008A0000000400000098000000FFFFFFFF
	TABH+ 40(16) = 040000002009000010000000C1308001
	store	= 0xA02E0100DF070000
	ext1	= 0x0000000000000000
	shmId	= 0	(0x00000000)
	id	= 19	(0x13000000)
	label	= 138 (0x8A000000)
	fill	= 4	(0x04000000)
	leng	= 152 (0x98000000)
	loop	= -1	(0xFFFFFFFF)
	xtyp	= TYPE#000034
	occu	= 16	(0x10000000)
	access	= 1	(ItAccessStandard)
	idxKind	= 0	(ItIndexNone)
	uniKind	= 2	(ItUniqueNon)
	keyKind	= 1	(default)
	cmpMode	= 8	(cmpManyEq)
	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	= 0x50915100DF070000
	pgHook	= 0x0000000000000000
	idxPtr	= 0x0000000000000000
	shmTabhSet = 0x0000000000000000
	id	= 130 (0x82000000)
	refCount	= 0	(0x00000000)
	tstRefCount = 0	(0x00000000)
	lineAdmin	= 16	(0x10000000)
	lineAlloc	= 16	(0x10000000)
	shmVersId	= 0	(0x00000000)
	shmRefCount = 1	(0x01000000)
	>>>>> 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
GS_OUTTAB
	Initial records ##########################################IRBD	####
	22466766627666767222000000000000000000000000000000000000000000454422222200FF
	009E9491C0253F2430000000000C00000000C0000000000C00000000C00000922400000000FF
	00000000000000000000000000000000000000000000000000000000000000000000000000FF
	000000000000000000000C0000000000C00000000C00000000C0000000000C000000000000FF
LINE_CMD
	IRBD
	4544222222222222222222222222222222222222222222222222222222222222222222
	9224000000000000000000000000000000000000000000000000000000000000000000
	0000000000000000000000000000000000000000000000000000000000000000000000
	0000000000000000000000000000000000000000000000000000000000000000000000
BUFFERED_TABLES_64[]
	Table IT_21[3671x624]
	\PROGRAM=RSTUNE50\DATA=BUFFERED_TABLES_64[]
	Table reference: 18
	TABH+ 0(20) = 20C95000DF070000B0260100DF07000000000000
	TABH+ 20(20) = 1200000015000000570E000070020000FFFFFFFF
	TABH+ 40(16) = 04000000901D000010000000C1248001
	store	= 0x20C95000DF070000
	ext1	= 0xB0260100DF070000
	shmId	= 0	(0x00000000)
	id	= 18	(0x12000000)
	label	= 21	(0x15000000)
	fill	= 3671 (0x570E0000)
	leng	= 624 (0x70020000)
	loop	= -1	(0xFFFFFFFF)
	xtyp	= TYPE#000143
	occu	= 16	(0x10000000)
	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	= 0xE0830200DF070000
	pgHook	= 0xF0080200DF070000
	idxPtr	= 0x0000000000000000
	shmTabhSet = 0x0000000000000000
	id	= 29	(0x1D000000)
	refCount	= 0	(0x00000000)
	tstRefCount = 0	(0x00000000)
	lineAdmin	= 4096 (0x00100000)
	lineAlloc	= 3680 (0x600E0000)
	shmVersId	= 0	(0x00000000)
	shmRefCount = 1	(0x01000000)
	>>>>> 1st level extension part <<<<<
	regHook	= 0x0000000000000000
	collHook	= 0x0000000000000000
	ext2	= 0x40260100DF070000
	>>>>> 2nd level extension part <<<<<
	tabhBack	= 0xE0250100DF070000
	delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
	pb_func	= 0x0000000000000000
	pb_handle	= 0x0000000000000000
BUFFERED_TABLES_64
	###########################<####################?#############################################
	0000000000000000000000000003000000000000000000000000000000000000000000000000000000000000000000
	00000C0000000000C0000000000C0000000000C0000000000C0000000000C0000000000C0000000000C0000000000C
	0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
	0000000000C0000000000C0000600000C0000000000C0000200000C0000000000C0000000000C0000000000C000000
TABLE_QUALITIES[]
	Table IT_19[3671x78]
	\PROGRAM=RSTUNE50\DATA=TABLE_QUALITIES[]
	Table reference: 16
	TABH+ 0(20) = 20B00200DF07000090240100DF07000000000000
	TABH+ 20(20) = 1000000013000000570E00004E000000FFFFFFFF
	TABH+ 40(16) = 04000000201E000010000000C9248001
	store	= 0x20B00200DF070000
	ext1	= 0x90240100DF070000
	shmId	= 0	(0x00000000)
	id	= 16	(0x10000000)
	label	= 19	(0x13000000)
	fill	= 3671 (0x570E0000)
	leng	= 78	(0x4E000000)
	loop	= -1	(0xFFFFFFFF)
	xtyp	= TYPE#000146
	occu	= 16	(0x10000000)
	access	= 1	(ItAccessStandard)
	idxKind	= 1	(ItIndexLinear)
	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	= 0x70BF0100DF070000
	pgHook	= 0x70C40100DF070000
	idxPtr	= 0x80B49300DF070000
	shmTabhSet = 0x0000000000000000
	id	= 109 (0x6D000000)
	refCount	= 0	(0x00000000)
	tstRefCount = 0	(0x00000000)
	lineAdmin	= 4016 (0xB00F0000)
	lineAlloc	= 3760 (0xB00E0000)
	shmVersId	= 0	(0x00000000)
	shmRefCount = 1	(0x01000000)
	>>>>> 1st level extension part <<<<<
	regHook	= 0x0000000000000000
	collHook	= 0x0000000000000000
	ext2	= 0x20240100DF070000
	>>>>> 2nd level extension part <<<<<
	tabhBack	= 0xC0230100DF070000
	delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
	pb_func	= 0x0000000000000000
	pb_handle	= 0x0000000000000000
GS_OUTTAB-NAME
	Initial records
	22466766627666767222
	009E9491C0253F243000
	00000000000000000000
	00000000000000000000
KERNEL64
	X
	5
	8
	0
	0
No.	2 Ty.	FORM
Name WRITE_LIST
CURRENT_LIST

	2222222222
	0000000000
	0000000000
	0000000000
GT_MEMORY_ALLOC_PROC
	Table[initial]
GT_RP_LINE
	Table[initial]
GT_MEMORY_DETAIL
	Table[initial]
GT_DB_REQUESTS
	Table[initial]
SY-UCOMM

	2222222222222222222222222222222222222222222222222222222222222222222222
	0000000000000000000000000000000000000000000000000000000000000000000000
	0000000000000000000000000000000000000000000000000000000000000000000000
	0000000000000000000000000000000000000000000000000000000000000000000000
ROWS_64
	###################H2#########U$<########1#########W#d#
	0000000008000000000438000000005230000000830900000005260
	0000000071C0000000082C0000000154C0000002213C0000001734C
GT_WRITE_EM_BLOCKLIST
	Table[initial]
GC_FORMNAME_TOP_OF_PAGE
	TOP_OF_PAGE
	545544554442222222222222222222
	4F0FF6F01750000000000000000000
	000000000000000000000000000000
	000000000000000000000000000000
CURR_BUFF

	2
	0
	0
	0
GV_COUNT
	0
	0000
	0000
LC_X
	X
	5
	8
	0
	0
ON_SQLS
	X
	5
	8
	0
	0
No.	1 Ty.	EVENT
Name START-OF-SELECTION
%_VIASELSCR
	#
	0
	4
SY-XPROG
	SAPLSCSMROUTE
	5454545454554222222222222222222222222222
	310C333D2F545000000000000000000000000000
	0000000000000000000000000000000000000000
	0000000000000000000000000000000000000000

Internal notes
	The termination was triggered in function "ab_bcdArithmeticOverflow"
	of the SAP kernel, in line 72 of the module
	"//bas/700_REL/src/krn/runt/abcalc.c#8".
	The internal operation just processed is "CALC".
	Internal mode was started at 20140403094059.

Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
SAP (R) - R/3(TM) Callstack, Version 1.0
Copyright (C) SAP AG. All rights reserved.
Callstack without Exception:
App	: disp+work.EXE (pid=6752)
When	: 4/3/2014 9:40:59.193
Threads : 2
Computer Name	: PSPRD1
User Name	: SAPServicePRD
Number of Processors: 8
Processor Type: EM64T Family 6 Model 15 Stepping 7
Windows Version	: 5.2 Current Build: 3790
State Dump for Thread Id 16b4
FramePtr	ReturnAd	Param#1	Function Name
0000000008784870 0000000077d704ef 0000000000313ad0 ntdll!ZwWaitForSingleObject
0000000008784910 00000000017b1331 00000000000001d4 kernel32!WaitForSingleObjectEx

0000000008784b60 0000000000629bf5 0000000000000001 disp+work!NTDebugProcess [ntstcdbg.c (509)]

0000000008784b90 0000000000b40c9c 0000000000000001 disp+work!CTrcStack [dptstack.c (182)]

0000000008784be0 0000000000b462b1 0000000000000001 disp+work!rabax_CStackSave [abrabax.c (7334)]

00000000087855c0 000000000092bf35 0000000001d4f2f8 disp+work!ab_rabax [abrabax.c (1280)]

0000000008785600 0000000000930254 000007fff1e7ff70 disp+work!ab_bcdArithmeticOverflow [abcalc.c (7

0000000008785890 0000000000869e38 0000000000000000 disp+work!ab_jcald [abcalc.c (1110)]
00000000087859f0 0000000000a51c92 0000000000000001 disp+work!ab_extri [abextri.c (527)]
0000000008785a40 0000000000a52634 0000000000000001 disp+work!ab_xevent [abrunt1.c (281)]
0000000008785ae0 0000000000bc583c 0000000000000000 disp+work!ab_trigg [abrunt1.c (68)]
0000000008785b80 0000000000691156 000007df00000021 disp+work!ab_run [absubmit.c (408)]
0000000008785d10 00000000006961de 000007df000c3c8c disp+work!dynpmcal [dymainstp.c (2383)]
0000000008785db0 000000000069548a 0000000000000000 disp+work!dynppai0 [dymainstp.c (1114)]
0000000008785e60 000000000064be63 0000000000000000 disp+work!dynprctl [dymainstp.c (361)]
000000000878fc20 00000000004faa82 0000000000000013 disp+work!dynpen00 [dymain.c (1940)]
000000000878fea0 0000000000432511 0000000000000000 disp+work!TskhLoop [thxxhead.c (4700)]
000000000878fee0 000000000040108d ffffffff00000003 disp+work!DpMain [dpxxdisp.c (1221)]
000000000878ff10 0000000001a94181 0000000000000000 disp+work!nlsui_main [thxxanf.c (84)]
000000000878ff70 0000000077d5969c 0000000000000000 disp+work!wmainCRTStartup [crtexe.c (498)]
000000000878ffa0 0000000000000000 0000000001a94010 kernel32!BaseProcessStart
State Dump for Thread Id 1e44
FramePtr	ReturnAd	Param#1	Function Name
000000000f86fe40 0000000077d5f6e1 00000000088239e0 ntdll!NtFsControlFile
000000000f86feb0 0000000001971a1f 0000000000000000 kernel32!ConnectNamedPipe
000000000f86ff40 000007ff7fc411c4 0000000000000000 disp+work!SigIMsgFunc [signt.c (679)]
000000000f86ff70 0000000077d6b70a 0000000077d6b6d0 msvcrt!endthreadex
000000000f86ffa0 0000000000000000 0000000000000000 kernel32!BaseThreadStart

List of ABAP programs affected
Index	Typ Program	Group	Date		Time	Size	Lang.
	0 Prg RSTUNE50		0 13.05.2008 17:12:25	174080 E
	1 Prg SAPMSSY0		1 13.05.2008 17:12:24	92160 E
	2 Prg SAPMSSYD		1 12.09.2006 11:33:31	23552 E
	3 Prg SAPFSYSCALLS		1 09.09.2004 14:18:32	7168 E
	4 Prg RSDBRUNT		0 13.05.2008 17:25:15	254976 E
	5 Typ RSSCR		0 30.03.2005 10:21:45	5120
	6 Prg RSDBSPBL		0 30.03.2005 10:21:58	72704 E
	7 Prg SAPDB__S		0 30.03.2005 10:22:01	19456 E
	8 Prg RSDBSPMC		0 12.09.2006 11:25:01	79872 E
	9 Typ DDSHDESCR		0 03.09.1997 03:05:16	7168
	10 Typ SPPARAMS		0 07.05.1997 13:10:38	2048
	11 Prg SAPLSABE		11 09.09.2004 14:18:36	12288 E
	12 Prg SAPLSECU		12 13.05.2008 17:04:40	87040 E
	13 Typ RSSUBINFO		0 14.10.1999 22:01:03	3072
	14 Prg SAPFSPOR		1 12.05.2008 08:54:50	14336 E
	15 Prg SAPLSCNT		15 18.02.2005 14:16:06	30720 E
	16 Typ DYCBOX		0 20.08.1998 11:16:53	3072
	17 Prg SAPLSVSM		17 18.02.2005 14:16:06	28672 E
	18 Prg SAPLSGUI		18 13.05.2008 17:12:24	84992 E
	19 Prg SAPLSTTM		19 05.07.2005 13:10:18	69632 E
	20 Prg SAPLSBDC		20 13.05.2008 17:03:53	44032 E
	21 Prg CL_DATAPROVIDER===============CP		21 28.02.2005 21:00:46	49152 E
	22 Prg %_CCNTL		21 18.02.2005 14:15:08	15360 E
	23 Typ OBJ_RECORD		0 14.02.1998 08:30:43	2048
	24 Prg SAPLSTUP		24 13.05.2008 17:03:03	74752 E
	25 Prg SAPLCNDP		25 11.05.2008 20:28:29	195584 E
	26 Prg SAPSHDTV		15 05.01.2005 16:26:16	35840 E
	27 Prg SAPFGUICNTL		1 18.02.2005 14:15:08	24576 E
	28 Prg SAPLOLEA		28 11.05.2008 18:44:29	96256 E
	29 Prg SAPLSFES		29 15.05.2008 09:47:06	261120 E
	30 Prg SAPLSPLUGIN		30 09.09.2004 14:18:36	8192 E
	31 Typ ARFCRDATA		0 13.02.2005 18:20:24	7168
	32 Prg SAPLGRFC		32 13.02.2005 18:20:25	16384 E
	33 Typ SWCBCONT		0 15.11.2000 17:55:11	3072
	34 Typ OLE_VERBS		0 04.04.1995 16:02:20	2048
	35 Typ OLE_PA		0 04.04.1995 16:02:19	2048
	36 Prg SAPLSTUB		36 15.05.2008 09:45:57	233472 E
	37 Prg CL_ABAP_CHAR_UTILITIES========CP		37 05.07.2005 13:10:15	13312 E
	38 Typ TUNEHD		0 22.10.1994 10:51:14	7168
	39 Typ SAPBUFQUAL		0 22.10.1994 10:49:15	2048
	40 Typ TUNEHDWQ		0 15.11.2000 17:58:13	8192
	41 Typ TUNEHDWQ64		0 06.11.2003 20:32:30	9216
	42 Typ DBSTATDEC		0 20.08.1998 11:15:08	10240
	43 Typ DBSTATDEC64		0 06.11.2003 20:27:39	10240
	44 Typ SAPTUNEBFN		0 06.11.2003 20:30:43	2048
	45 Typ TABBUFQUAL		0 20.08.1998 11:05:38	2048
	46 Typ CCSTATS		0 19.12.1994 15:02:54	4096
	47 Typ EMCONTEXT		0 14.02.1998 07:14:57	4096
	48 Typ MEMALLOC		0 28.08.1997 08:53:45	2048
	49 Typ MEMMODETAB		0 29.03.2001 16:07:48	4096
	50 Typ CTABSTAT_64		0 06.11.2003 20:27:31	10240
	51 Prg SAPLSYDB		51 11.05.2008 20:30:15	63488 E
	52 Prg SAPLSDNT		52 11.05.2008 20:28:28	219136 E
	53 Prg SAPLSUGS		53 31.03.2006 11:23:11	47104 E
	54 Prg SAPLSALR		54 15.05.2008 09:47:20	535552 E
	55 Typ ALMTNAME_L		0 07.05.1997 12:39:59	2048
	56 Typ ALNAMESPLT		0 04.06.1997 19:14:50	3072
	57 Prg SAPLSALC		57 15.05.2008 09:47:20	664576 E
	58 Prg SAPLSRFC		58 07.02.2006 10:16:57	37888 E
	59 Prg SAPLSCSMROUTE		59 15.05.2008 09:47:20	384000 E
	60 Typ CSMSEGM		0 18.05.2004 14:07:28	5120
	61 Prg SAPLSALS		61 15.05.2008 09:47:20	157696 E
	62 Typ ALMONSE40B		0 09.11.2000 14:03:52	10240
	63 Typ ALCACHECNF		0 04.12.2000 14:55:58	2048
	64 Prg SAPLSCSM_UTILITIES		64 09.09.2004 14:18:36	9216 E
	65 Typ ALCONSEG		0 18.05.2004 14:07:05	7168
	66 Typ CSM_UPD_C		0 18.05.2004 14:07:23	6144
	67 Typ ALSYSTEMS		0 18.05.2004 14:07:04	4096
	68 Typ CSM_UPD_A		0 18.05.2004 14:07:23	4096
	69 Typ CSM_UPD_S		0 18.05.2004 14:07:23	5120
	70 Typ CSMCONTX		0 18.05.2004 14:07:28	5120
	71 Typ CSMSEGMX		0 18.05.2004 14:07:26	5120
	72 Prg SAPLTHFB		72 15.05.2008 09:46:22	394240 E
	73 Typ MSXXLIST_V6		0 13.02.2005 18:20:27	4096
	74 Typ ALGTIDLNRC		0 04.06.1997 19:14:45	4096
	75 Typ ALRFCLNAME		0 18.05.2004 14:07:26	11264
	76 Typ ALPERFTYPE		0 09.11.2000 14:03:57	11264
	77 Typ ALGLOBTID		0 04.06.1997 19:14:45	3072
	78 Typ ALRFCTID		0 18.05.2004 14:07:26	9216
	79 Typ TTZCU		0 30.01.1996 13:46:43	2048
	80 Prg SAPLSBUF		80 13.05.2008 17:09:37	128000 E
	81 Prg SAPLSEM1		81 09.09.2004 14:18:36	45056 E
	82 Typ MSXXLIST		0 07.12.2000 13:34:00	3072
	83 Prg SAPLSMEM		83 13.05.2008 17:07:29	19456 E
	84 Typ CST_EM_MONITOR_ALV		0 08.12.2004 17:58:42	5120
	85 Typ TUNEHD64		0 06.11.2003 20:32:30	8192
	86 Prg CX_SY_ARITHMETIC_OVERFLOW=====CP		86 05.07.2005 13:10:16	10240 E
	87 Typ SCX_SRCPOS		0 18.05.2004 14:07:11	2048
	88 Prg CX_SY_ARITHMETIC_ERROR========CP		88 05.07.2005 13:10:16	10240 E
	89 Prg CX_DYNAMIC_CHECK==============CP		89 05.07.2005 13:10:16	10240 E
	90 Prg CX_ROOT=======================CP		90 11.05.2008 19:49:47	11264 E
	91 Prg CX_NO_CHECK===================CP		91 05.07.2005 13:10:16	10240 E
	92 Prg CX_SY_NO_HANDLER==============CP		92 05.07.2005 13:10:16	10240 E
	93 Typ RSJOBINFO		0 29.04.1992 14:52:25	3072
	94 Typ SYST		0 09.09.2004 14:18:12	31744

Directory of Application Tables
Name	Date	Time	Lngth
	Val.
Program RSTUNE50
SYST	09.09.2004 14:18:12 00004612
	\0\0\0\0\x0004\0\x000C\0\0\0\0\0\0\0\0\0\0\0\0\0\x0001\0ÿ
RSJOBINFO	. .	: :	00000164
	00000000000000
TUNEHD64	. .	: :	00000434
	\0\0\0\0E\x009C\0\0\0\x0600\x0C00\0\0\0\0\0\x000C\0\0\0
SAPBUFQUAL	. .	: :	00000008
	?\x1C71?\x1C71\|
Program SAPLSTUB
TUNEHD	. .	: :	00000204
	\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0
SAPBUFQUAL	. .	: :	00000008
	\0\x0C00\0\x0C00\|