DUMP in VELO Transaction
Hi,
In VELO Transaction, when I select all the vehicle models, and choose the VIEW = Additional Search, and give a Sales Hirarchy value...the system goes to a dump.
The short text of the dump is "No more storage space available for extending an internal table, You attempted to extend an internal table, but the required space was not available".
The number of records which the program is trying to append to an internal table is '1328618'. But at the middle of the process of appending we get the dump.
Below is the Error Analysis in the dump:
The internal table "\FUNCTION-POOL=VELO02\FORM=VELO_SEARCH_VEHI_CONTROL\DATA=
CDIAVEHICONF_LT" could not be further extended. To enable
error handling, the table had to be delete before this log was written.
As a result, the table is displayed further down or, if you branch to
the ABAP Debugger, with 0 rows.
At the time of the termination, the following data was determined for
the relevant internal table:
Memory location: "Session memory"
Row width: 3272
Number of rows: 1121828
Allocated rows: 1121828
Newly requested rows: 4 (in 1 blocks)
Following is the extract in 'How to correct the error' section of the dump:
The amount of storage space (in bytes) filled at termination time was:
Roll area...................... 7722352
Extended memory (EM)........... 2002747344
Assigned memory (HEAP)......... 4000079472
Short area..................... " "
Paging area.................... 6668288
Maximum address space.......... 4294967295
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:
"TSV_TNEW_PAGE_ALLOC_FAILED" " "
"SAPLVELO13" or "LVELO13U16"
"VELO13_PROCESS_CATEGORIES"
Please let me know what exactly is the problem. Do the BASIS people need to do something like increase the memory size ?
Thanks in Advance.
Hi Dagny,
Its the problem with SAP Internal Memory Size.
There might not be any space available for holding that many number of internal table records.
Probably BASIS needs to do something for rectifying this problem.
Chk this OSS Note 1260912.
It says that whenever an internal table with data of size exceeds 2GB it throws a dump bcoz ABAP memory is limited to 2 GB
Regards,
Lakshman.
Similar Messages
-
Dump in the transaction J2I6 in ECC 6.0
Dear all,
I am getting a dump in the transaction J2I6 when i select the radiobutton RG23D and then give the excise group,start date and enddate.When I select the radiobutton Excel Format ,it throws a dump as follows:-
Packed field contains incorrect BCD format.
Error anakysis says that ''An arithmatic operation in the current program J_2IRG23 attemps to process a field of type P that contains an invalid BCD format.
What can i do?plz helpHi,
There are some OSS notes related to your problem.
Pls check the OSS NOte 1096189. It may resolve your problem. Other related notes are 1155341.
Please check which one is relevant to your system.
Regrads,
Lokesh./
Edited by: Lokesh Tarey on Apr 22, 2010 3:24 PM -
Short dump in every transaction during support pack import - Solution Mgr
I am in the middle of applying support packs SP13 and SP14 for Solution Manager. In SPAM, during the import, I received short dumps. I get short dump for all transactions. The error message is 'Syntax error in program "SAPLWB_CUSTOMIZING", Field "G_DC_TABSTR" is unknown in INCLUDE LWB_CUSTOMIZINGDEV'.
Please help. Thanks !Hi
My first question, would be, why are you performing other activities while importing patches?
This is not recommended.
Rahul -
CONNE_IMPORT_WRONG_COMP_TYPE short dump in DB02OLD transaction
Hi,
We have recently upgraded to SAP ECC 6.0 and in solution manager system, I am getting CONNE_IMPORT_WRONG_COMP_TYPE short dump for DB02OLD transaction (Program RSORAT5M).
I searched few notes like 657981 and others but all are applicable for DB02 transaction. If anyone encountered same problem, please let me know how to resolve the issue.
Thanks in advance,
Ni3Solved on my own
-
Short dumps in every transaction during the Support pack import
I am in the middle of applying support packs SP12 on NetWeaver 7.0. In SPAM, during the import, I received short dumps. I get short dump for all transactions i excute now. I am unable to go to SPAM to continue the SPAM, all I get short dumps. This is our new training system that we are building. I had same issues before, and I got help from SAP for this issue, where they suggested tp command wiht lots of options to run at the OS level. Since I moved company I am not able access the same ticket. Do anyone of you guys know the OS tp command to continue the SPAM import phase?
Please and thanks
KumarHi,
SAP does not recommend to run SP's at OS level. Most of time when u r running SAP_BASIS , u will receive ABAP dumps. then option is to run SP at using tp command & you have to analyze many things before running this command.
<removed_by_moderator>
Please read the Rules of Engagement
Edited by: Juan Reyes on Jul 28, 2008 10:12 AM -
ABAP dump while executing transaction *PC00_M99_CIPE*
Hi,
Getting ABAP dump while executing transaction PC00_M99_CIPE ,hence cannot do payroll posting .
Information on where terminated
Termination occurred in the ABAP program "CL_HRFPM_CD_CLOSING_HANDLER===CP" -
in "GET_FM_POS_CHECK_DATA".
The main program was "RPCIPE00 ".
In the source code you have the termination point in line 13
of the (Include) program "CL_HRFPM_CD_CLOSING_HANDLER===CM00E".
We have recently upgraded our patch level.
SAP_OCS(SPAM/SAINT) SAPKD70026 SAPKD70033
SAP_ABA SAPKA70012 SAPKA70018
SAP_BASIS SAPKB70012 SAPKB70018
PI_BASIS SAPKIPYJ7B SAPKIPYJ7I
SAP_BW SAPKW70012 SAPKW70020
SAP_AP SAPKNA7008 SAPKNA7015
SAP_APPL SAPKH60009 SAPKH60015
SAP_HR SAPKE60028 SAPKE60039
EA-HR SAPKGPHD07 SAPKGPHD26
Kindly guide me.
Regards,
Rachelthanks for the quick response.
By applying note 1137655,problem got resoved.
FORM CHECK_CMTNT_UPDATE_CLOSED
Delta001
Context Block
FORM check_cmtnt_update_closed
USING
u_key_date TYPE begda
CHANGING
c_flg_cmtnt_closed.
Delete Block
DATA ls_encumb_iv TYPE t77hrfpm_encumb.
DATA l_gsval TYPE t77s0-gsval.
DATA ls_fm_pos_key TYPE hrfpm_fm_doc_pos-key_pos.
DATA lx TYPE REF TO cx_hrfpm.
STATICS so_closing_handler TYPE REF TO cl_hrfpm_cd_closing_handler.
CLEAR c_flg_cmtnt_closed .
*--- old switch from note??? active?
*--- if so: use the old logic
cl_hr_t77s0=>read_gsval(
EXPORTING
grpid = 'HRFPM'
semid = 'CHKAC'
IMPORTING
returnvalue = l_gsval ).
TRY.
IF NOT l_gsval IS INITIAL .
TRY.
c_flg_cmtnt_closed = 'X'.
Insert Block
DATA: ls_encumb_iv TYPE t77hrfpm_encumb.
STATICS:
s_gsval TYPE t77s0-gsval,
s_gsval_read TYPE flag.
IF s_gsval_read IS INITIAL .
SELECT SINGLE gsval
FROM t77s0
INTO s_gsval
WHERE grpid = 'HRFPM'
AND semid = 'CHKAC' .
s_gsval_read = 'X'.
ENDIF.
CLEAR c_flg_cmtnt_closed .
TRY.
c_flg_cmtnt_closed = 'X'.
Delta002
Context Block
CATCH
cx_hrfpm_db_operation
cx_hrfpm_ad_customizing .
Delete Block
ENDTRY.
ELSE.
*--- using closed period functionality of PBC
IF so_closing_handler IS INITIAL .
CREATE OBJECT so_closing_handler.
ENDIF.
IF so_closing_handler->consumption_in_closed_period(
i_key_date = u_key_date
is_fm_pos_key = ls_fm_pos_key )
IS INITIAL.
c_flg_cmtnt_closed = 'X'.
ENDIF.
ENDIF.
CATCH cx_hrfpm INTO lx.
lx->raise_sy_message( ).
ENDTRY.
ENDFORM. "check_cmtnt_update_closed
Insert Block
ENDTRY.
ENDFORM. "check_cmtnt_update_closed -
Short Dump in CO02 Transaction
Hi ,
I am getting short Dump in CO02 Transaction . Please see following detail .
Runtime Errors MESSAGE_TYPE_X
Trigger Location of Runtime Error
Program SAPLCOKO1
Include LCOKO1F4H
Row 614
Module type (FORM)
Module Name ORDER_CHANGE
>>>>> MESSAGE x901. "n779835
Please help me.
Thanks in Advance.
SaiHi Sai,
I get an similar Error after I have upgrade from 6.20 to ERP6 EHP4. Could you solve your problem?
Tanks
Bernd
Syntax error in program "SAPLCOKO1 ".
The current ABAP program "????????????????????????????????????????" had
terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "SAPLCOKO1 " in include "LCOKO1FW2 " in line 27:
"The data object "LS_REF" down not have a component called "OBMAT"." -
Restore ASE - Dump of open transaction-log required?
Hi experts,
I am still doing some restore tests.
What about the following case.
Last transaction log was done at 1 o'clock and next will be at 4 o'clock.
At 3 o'clock we detect that we have to restore two 2 o'clock.
So for this restore, I need the transaction log which isn't dumped yet.
My question is, do I have to dump the current transaction log also to a file for the restore procedure?
Or is there another way to included in the restore the current-log file?
In other words, when will the log-file be touched first?
After "online database" command?
If so, I can also do the restore using the original-logfile, right?
Kind regardsChristian,
You are right.
Let me tell you what is the practice I reccommend to follow:
1. Take full backup daily during your off business hours if you have the infrastructure like tape/disk or SAN and the data is very critical may be production or development
2 During the business hours take hourly or half an hour once take the transaction backup may be between 9-6 as per your time zone :)
3 This mostly helps you to minimise the tran log loss.
4 As you have the week end reorg and update stats running I prefer just before start of production hours on Monday take a full backup and keep it safe so that the data is super clean and secure
If there is any confusion let me know I will explain you still clearly in simpler words
PS:One full backup per day is fine if you can preserve and retain for 7-10 days and delete it later point if you don't need it and don't have infrastructure and disk cost problems :P ;)
Cheers
Kiran K Adharapuram -
hi
what is velo transaction. i am not getting this transaction in my system. what would be the reasonHi .
U R VELO Transaction Will Come Under Following Scenario.
Vehicle
Definition
A vehicle is a business object (BUS1200) in the SAP system.
A vehicle is the result of using a create action in VMS to create a vehicle for a vehicle model. It is therefore, an instance of a vehicle model, in other words, an individual object. A configuration is always created for a vehicle; the characteristics in the configuration may have not yet had any values assigned to them, partly have had values assigned or have had all values assigned. You can identify the vehicle by its vehicle number and define it further using a batch, valuation type and, where appropriate, an equipment number.
Use
The vehicle is a central object in the Vehicle Management System. Vehicle searches and actions for the business processes involved always relate to at least one vehicle. The only exception is the function Assignment of Vehicles to Sales Documents, which does not start from the vehicle but from the sales document.
Structure
Assigning Values
When you create a vehicle it receives an internal vehicle number. This number is the also the batch number and the valuation type number. Each vehicle, therefore, has its own batch and valuation type. You can display valuated stock using transaction MMBE Stock Overview.
You are recommended to use valuation for a single batch with VMS. The valuation of sales order stock is not supported by VMS.
Create a purchasing info. record manually for each vendor. Leave the field Valuation type under Purchasing organization 1 empty. Do not use the Customizing setting (Customizing for Materials Management) under Purchasing ® Environment Data ® Define Default Values for Buyers, indicator InfoUpdate Purchase order), which defines that a purchasing info. record is created automatically when a purchase order is created. The field Valuation Type is filled when this Customizing setting has been made. This leads to problems when you want to create vehicles.
You can find further information in the documentation for Logistics General under Batch Management (LO-BM), especially Valuation for a Single Batch.
Vehicle Data
A vehicle is characterized by its vehicle data (vehicle master, see table VLCVEHICLE). The following belong to the vehicle data:
GUID
Global Unique Identifier. A 22-character technical key assigned by the system when the importer creates the vehicle.
This key is unique and therefore also differentiates between vehicles that have been created in different systems. The GUID serves only internal technical control purposes and does not appear on the interface.
Internal vehicle number
An identification number from an internal number range. It is assigned by the system when the importer creates the vehicle.
The vehicle number is created independently of the vehicle identification number (VIN).
External vehicle number
Identification number assigned by the manufacturer (for example, production number, vehicle number)
Vehicle identification number (VIN)
17-character number that identifies a vehicle and is created when the vehicle is assembled, for example, during the assembly process in the manufacturers production system.
The VIN is an international standard.
Batch (only for vehicles that can be assigned values)
A vehicle represents exactly one batch. The batch number is the same as the internal vehicle number (see above).
Valuation type (only for vehicles that can be assigned values)
Each vehicle has a valuation type (Valuation for a Single Batch). The valuation type number is the same as the internal vehicle number (see above).
Plant
Location, organizational unit of importer
Storage location
Actual storage location of the finished vehicle in the importers plant
Vehicle Model
Basic type of a vehicle that can be varied.
Vehicle models are created as configurable materials in the SAP system.
A vehicle model can be a general vehicle type or a vehicle type for which specific characteristic values have been predefined using object dependencies.
Configuration
Characteristics and assigned characteristic values (for example: color: blue; special features: radio, air conditioning).
Primary Action Control, primary status + date + time, secondary action control, secondary status + date + time
The action control defines (in an action matrix) which actions can follow one another when dealing with vehicles and which vehicle status change is connected with this.
Example: a vehicle that the importer has ordered from the manufacturer receives the status Ordered. After the manufacturer has confirmed the purchase order, in other words has performed the action Confirm purchase order, the status changes automatically to Purchase order confirmed.
You can distinguish between primary and secondary action controls, depending on the process that is being represents by the action control. The primary action control usually represents the procurement process (ordering the vehicle from the manufacturer) and the secondary action control the sales process (sale of the vehicle to the dealer). However, a subdivision into a logistics and a financial process is also possible.
Availability status
Status that displays whether the vehicle is available for sale (for example: Not released, Available, Reserved, Sold).
The status changes automatically depending on the action you perform.
The availability status can remain the same for a series of different vehicle statuses. Example: a vehicle that receives the statuses Vehicle created, Vehicle ordered, Purchase order confirmed and Transit confirmed retains the availability status Not released.
The availability status is only for information purposes and has no controlling effect.
Address
Address (from central address management) where the vehicle is to be found.
This address can be the address of a vendor, customer, end customer or of any other location defined in Customizing for VMS.
Production date (time stamp)
Date on which the vehicle is produced.
The importer enters the planned production date that he has agreed on with the manufacturer in the appropriate field when the vehicle is created or the vehicle data is changed. The manufacturer updates this date regularly during the production process using data transfer per external interface. The production date thus changes from being a planned date to being an actual production date.
This time stamp contains data on the construction year and month, which are required for the trade-in.
Planned delivery date (time stamp)
Date on which the vehicle is planned to arrive at the dealer/end customer.
The system determines this date automatically from the appropriate Customizing settings.
Gross list price + currency
Price that results from the vehicle configuration.
This price is independent of business partner-specific discounts.
The gross list price changes if the vehicle configuration is changed later.
You must create an organizational role with the key GROS (see: Calculating the Gross List Price Using Organizational Roles) if you want the system to be able to calculate the gross list price.
Vehicle usage
Planned usage for the vehicle, for example, use as end customer vehicle, in fleet sales, as demonstration car and so on.
This data can be used to help you prioritize cars when processing purchase orders and can be transferred to the manufacturer.
Sales campaign
Campaign for a specific length of time for the sale of a specific vehicle model or configuration at a reduced price. You can assign a sales campaign to a vehicle using the action CAMP.
Examples: sale of old models for which the new model is already on the market, sale of old stock with unusual configurations etc.
You can trigger special pricing functions in the sales documents of vehicles that belong to a sales campaign. There are two options:
· You can add the field as an object characteristic to the vehicle configuration (see: Adding Object Characteristic to Configuration)
· You can use the options for flexible enhancements to SD pricing
Visibility
Indicator in the vehicle table that can be used to influence whether a vehicle can be seen by dealers during the vehicle search or not.
This indicator is controlled by the actions SHOW and HIDE.
There are two options for removing a vehicle form the hit list of the vehicle search:
· You can use the visibility dependently of the Organization Role as parameter when selecting vehicles from the database (BAdI VLC_SEARCH_ADAPTION)
Example: a VMS user at the importers can display all the vehicles but a VMS user at the dealers can only display the vehicles that are visible for all the dealers and additionally all the vehicles (also not visible) for which he/she has created a sales order/offer or for which, for example, he/she has been assigned as customer during the reservation process.
· You can use the visibility according to the selection in Category Management as parameter. This second option has the disadvantage that the performance is not as good, since many vehicles are selected that are then filtered out later.
Customer
Business partner to whom the vehicle is sold.
This is usually the dealer. It may, however, also be an end customer, for example, a car rental/hire company that wants to buy an entire fleet of cars from the importer, or an employee of the importer who wants to buy a vehicle directly from the importer.
You can manage one-time customers, for example the employees of the importer, using a CpD one-time/suspense account in the customer master record.
End customer
End customer for the vehicle.
The data for the end customer are stored in the functions for business partner management. You can assign an end customer by using action BUPA or by using the function End Customer, which is available in several actions.
Dealers can create end customer data; this end customer data is then assigned to the appropriate dealer and can only be viewed by him/her.
Vendor
Business partner from whom the vehicle is procured.
This is usually the manufacturer (OEM). In cases where there is multi-level procurement, it may be an intermediate vendor, for example a distribution center.
When a used vehicle is being exchanged for cash, the vendor can also be, for example, a rent-a car company or any other person. Such a business partner may also be managed at the same time as a customer in the system.
You can manage one-time vendors, for example the previous owner when exchanging a vehicle for cash, using a CpD one-time/suspense account in the customer master record.
Vehicle Search Area
Geographical or organizational area in which vehicles are made available and searched for.
This area defines the outermost limit within which a vehicle search can take place. You can assign a vehicle search area using action SMOD.
A vehicle search area can include more than one sales organization.
Each vehicle can only belong to exactly one vehicle search area.
You can define rules for the vehicle search and search areas in Category Management and thus represent a uniform policy. Prerequisite: all the vehicles within one vehicle search area are technically compatible and allowed in every other geographical region.
Sharing Level
In a scenario in which more than one dealer, SD organization etc. can access the same vehicle stock (defined by the vehicle search area), you can increase or decrease the availability of a vehicle for other dealers, sales organizations etc. by using the sharing level.
The sharing level is used as a parameter in Category Management.
Created by
System user who created the vehicle.
Registration date
Counter/meter reading + unit
You can display this vehicle data. Choose transaction VELO (Vehicle Manager), perform a vehicle search, choose a vehicle and then choose the tab page Detail.
The vehicle data is the result of actions that have been performed for a vehicle. The data is enhanced and updated continuously. Example: the following data is entered and determined on creating a vehicle: internal vehicle number, plant, vehicle model, configuration, primary action control, primary status, availability status, gross list price and, where appropriate, production date and vendor. When the purchase order is created, this data is completed with entries for the vendor and the location.
Most of the vehicle data is also available as a parameter for the vehicle search.
You can define further vehicle data according to your requirements. To do this, choose Customizing for the Vehicle Management System (VMS) ® Enhancements ® Define Additional Data for Vehicle (transaction OVELO4). If you are dealing with qualifiers in the additional table, you can display the data separately (transaction VELO, tab page Detail, screen Vehicle Data, function Addnl Data). If you are dealing with vehicle attributes in the vehicle table, they are displayed as fields in the lists of the vehicle overview and the vehicle details. You can find further information under Programming Your Own Actions.
You can enter and store documents for each vehicle (action ADDO Assign documents) and display them (transaction VELO, tab page Detail, screen Vehicle Data, pushbutton Documents). You can find further information under Business Document Navigator -
How to get the dump of a transaction output
hi gurus,
my requirement is to take the dump of the output produced by a transaction (sm58).
does any one know the way to copy the output of the transaction into an internal table?
please help me out. <REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Apr 22, 2008 1:53 PMHi Rambo..
Can you explain clearly whats your problem...
you can see the dump details in st22 t-code...
Regards,
Rahul -
Short Dump in MIGO transaction
When executing the transaction MIGO the transaction ends with the short dump as follows.
is it because of SAPNOTE 385830 ?
short text of error message : GET_SYTEM_BUSINESS_ERROR An error occurred while determining the business system ( No_business_system)
Technical information of error message
messgae class 00
number 001
variable 1 GET_SYTEM_BUSINESS_ERROR An error occurred while
variable 2 determining the business system ( No_business_system)
T CODE : migo
PROGRAM : SAPLMBWL
sceen no saplmigo 0001
screen line 18
the dump occurs at the line marked with -
>.
function mb_post_goods_movement.
""Local Interface:
*" IMPORTING
*" VALUE(XBLNR_SD) OPTIONAL
*" EXPORTING
*" VALUE(EMKPF) LIKE EMKPF STRUCTURE EMKPF
data: l_mem_id(10) type c. " 641365
Wurde zuvor eine Lieferung erzeugt, so ist kein MB_POST... nötig "HUM
check not xdeliv = x. "HUM
Control posting for external WM: Exit if BFWMS = 1 (Create delivery)
check not mkpf-bfwms = 1. "357661
read table xmseg index 1.
if not sy-subrc is initial.
message a260.
endif.
if xmkpf-mblnr is initial.
message a260.
endif.
xcommit = x. "Performance
if not xblnr_sd is initial.
xmkpf-xblnr = xblnr_sd.
xmkpf-le_vbeln = xblnr_sd. "XAN-SPM
modify xmkpf index 1.
when a goods movement for an inbound or outbound delivery is posted
directly from VL31N/ VL01N, XBLNR is not yet known when we call
CKMV_AC_DOCUMENT_CREATE, but the number is supposed to be stored in
BKPF as well. There is no other way to forward XBLNR to FI as not
every document is posted by MB_CREATE -> a new function module in
MBWL for transferring the information, called by FI, meant to load
the complete function group for all MBxx postings when this isn't
required (Performance). Would be the better way to transport the
information after switching off MBxx in later release.
corresponding IMPORT ... FROM MEMORY ... can be found in
AC_DOCUMENT_POST (FORM FI_DOCUMENT_PREPARE (LFACIF5D))
l_mem_id = 'MKPF-XBLNR'. " 641365
export xblnr = xblnr_sd to memory id l_mem_id. " 641365
endif.
if xmkpf-xabln is initial. "note 434093
call function 'MB_XAB_NUMBER_GET'. "note 434093
endif. "note 434093
enhancement-point mb_post_goods_movements_01 spots es_saplmbwl static.
$$-Start: MB_POST_GOODS_MOVEMENTS_01----
$$
enhancement 26 dimp_general_saplmbwl. "active version
data: l_statics_lock type c.
endenhancement.
$$-End: MB_POST_GOODS_MOVEMENTS_01----
$$
enhancement-point mb_post_goods_movements_02 spots es_saplmbwl.
$$-Start: MB_POST_GOODS_MOVEMENTS_02----
$$
enhancement 25 dimp_general_saplmbwl. "active version
read table xvbfa index 1.
if sy-subrc is initial and
g_vbtyp_v = '7'.
perform get_mdiff_kenz(sapmm07m) changing l_statics_lock.
endif.
endenhancement.
$$-End: MB_POST_GOODS_MOVEMENTS_02----
$$
call function 'MB_CREATE_MATERIAL_DOCUMENT_UT'
exceptions
error_message = 4.
As soon as we have started to put things into UPDATE TASK, we must
ensure that errors definitely terminate the transaction.
MESSAGE A is not sufficient because it can be catched from
external callers which COMMIT WORK afterwards, resulting in
incomplete updates. Read note 385830 for the full story.
if not sy-subrc is initial.
message id sy-msgid type x number sy-msgno with "385830
sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
MESSAGE A263.
endif.
Optische Archivierung
Spaete Erfassung mit Barcode
Redesign of barcode handling -> note 780365
perform barcode_update(sapmm07m) using xmkpf-mblnr
xmkpf-mjahr
barcode.
move-corresponding xmkpf to emkpf.
call function 'MB_MOVEMENTS_REFRESH'
exceptions
error_message = 4.
move-corresponding xmkpf to emkpf.
call function 'MB_MOVEMENTS_REFRESH'
exceptions
error_message = 4.
if not sy-subrc is initial.
message id sy-msgid type x number sy-msgno with "385830
sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
MESSAGE A261.
endif.
perform buchen_initialisieren(sapmm07m).
clear emkpf-subrc.
clear global fields when COMMIT WORK "Performance
if not sy-oncom = p.
perform clear_xcommit on commit.
else.
perform clear_xcommit. "if this FB is called on commit
endif.
perform clear_xcommit on rollback. "note 303392
endfunctionhi
check SAP Note 556000 - Short dump due to note 385830
Summary
Symptom
Consider the subsequent note 561872 ! *
You want to post a goods receipt for a reference document (for example purchase order, delivery ...). The checks do not cause any error. Nevertheless, the system generates a short dump which is deliberately triggered by note 385830.
One known scenario is a stock transfer process via a delivery: You have entered a stock transport order assigned to a sales order and post a goods receipt for the delivery via transaction MIGO. The sales order must be in valuated. The material to which postings are to be made is valuated separately and to be handled in batches. And the batch, which was assigned via the delivery, already exists with a valuation type in the receiving plant which is different from the one specified in the purchase order.
Other terms
MB_CREATE_GOODS_MOVEMENT, MIGO, MCHA, BWTAR.
Reason and Prerequisites
Prerequisites: see above. This is a program error.
Solution
Implement the attached program corrections.
Then implement the subsequent note 561872.
After the implementation of the note, checks are carried out in the program flow - if a batch and a valuation type were entered for a goods movement (for instance with reference to the purchase order or delivery) - on whether the assignment of the batch and valuation type is correct.
regards
KI -
Short dump in Z transaction code
Hi,
We have a Z transaction code 'ZPROFIT' for a report. After executing the report from output screen of report if i type 'se38' in command bar and if I press enter key it is going to short dump. But if I type '/nse38' it is working fine.The short dump description is as follows .
ShrtText
An exception that could not be caught occurred.
What happened?
The exception 'CX_SALV_OBJECT_NOT_FOUND' was raised but was not caught at any
stage in the
call hierarchy.
Since exceptions represent error situations, and since the system could
not react adequately to this error, the current program,
'CL_SALV_FUNCTIONS=============CP', had to
be terminated.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assinged to the class 'CX_SALV_OBJECT_NOT_FOUND', was
not caught,
which led to a runtime error.
The reason for this exception is:
No text available for this exception
Trigger Location of Exception
Program CL_SALV_FUNCTIONS=============CP
Include CL_SALV_FUNCTIONS=============CM00J
Row 28
Module type (METHOD)
Module Name IS_SALV_FUNCTION
Source Code Extract
Line SourceCde
1 method is_salv_function.
2 data: l_name type string.
3 data: l_msgtext type string.
4 data: ls_message type scx_t100key.
5
6 *get item
7 try.
8 call method get_item
9 exporting
10 function = name
11 importing
12 salv_function = value.
13 catch cx_salv_object_not_found.
14 try.
15 call method get_group
16 exporting
17 group = name
18 importing
19 salv_function = value.
20 catch cx_salv_object_not_found.
21 l_name = name.
22 message w026(salv_exception)
23 with 'CL_SALV_FUNCTIONS' 'IS_SALV_FUNCTION' 'Function: ' l_name
24 into l_msgtext. "#EC NOTEXT
25
26 ls_message-msgid = sy-msgid.
27 ls_message-msgno = sy-msgno.
>>>>> raise exception type cx_salv_object_not_found
29 exporting
30 textid = ls_message
31 object = 'Function'
32 key = l_name
33 class = 'CL_SALV_FUNCTIONS' "#EC NOTEXT
34 method = 'IS_SALV_FUNCTION'. "#EC NOTEXT
35 endtry.
36 endtry.
37
Please let me know how we can solve this?
Is there anything wrong in report source code?
Thanks in advance.
Regards,
Brahma Reddyhi brahma,
try to reinstall ur Front End...
it's not a error from ur Program, I think it's dumb because SAP GUI it's not all right working,
try to remove and install SAP GUI, maybe it's can solve ur problem...
Regards
Allan Cristian -
Short Dump with VA22 transaction in ECC 6
Hi All,
We are on ECC 6 and facing a short dump whenever we are trying to save some quotation. We are getting the following error.
There is probably an error in the program "SAPLSYDB". The program is triggered in the update task. There, the following ABAP/4 statements are not allowed:
CALL SCREEN
CALL DIALOG
CALL TRANSACTION
SUBMIT
"POSTING_ILLEGAL_STATEMENT" " "
"SAPLSYDB" or "LSYDBU27"
"DB_COMMIT".
Is there a sap note for this. Any link or pointer to this will be highly appreciated.
Regards,
JayantHello,
This looks like a problem for SAP. I assume that you have not modified the
program SAPLSYDB. I also assume that you have searched the Service Marketplasce
for any OSS notes. My next step would be to create a message to SAP to get them to
have a look.
Regards
Greg Kern -
Short dump with the transaction CJ02
Hello, this is my first thread in the forum. I hope to solve my problem.
It is necesary to say you that my english is very poor, is not so good. Sorry for that.
When i use the transaction CJ02 to finish or close a project, appears an error when i save it. The steps are the followings:
1- Run the transaction CJ02 with a WBS element
2- Mark the line of the WBS element
3- Select then button Settlement rule
4- Fill 4 items in the next screen to distribution rules (the % is 100)
5- Back with green arrow
6- Fill the field Cost Center Req
7- Save
After a few seconds appears the dump:
<b>ABAP runtime errors MESSAGE_TYPE_X
Occurred on 20.11.2006 at 11:07:09
>> Short dump has not been completely stored. It is too big.
The current application triggered a termination with a short dump.
Error analysis
Short text of error message:
Nested call of PERFORM ON COMMIT:
Long text of error message:
Diagnosis
During processing of a routine called using PERFORM ... ON COMMIT,
the system attempted to call PERFORM ... ON COMMIT again. Nesting
of this is not allowed.
System Response
Procedure
The program indicated after "Caller:" must be changed. This is the
program that calls the routine indicated after "Form:" during
COMMIT processing. This routine is part of the program indicated
after
"Program:".
Procedure for System Administration
Technical information about the message:
Message classe...... 00
Number.............. 081
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
If the error is in one of your own ABAP programs or an SAP program that
you have modified, try to correct it.
If the error occurred in a non-modified SAP program, you may be
able to find a solution in the SAP note system.
If you have access to the note system yourself, use the following
search criteria:
"MESSAGE_TYPE_X"
"SAPMSSY0 " or "SAPMSSY0 "
"%_ORDER_FORM_FOR_ROLLBACK"</b>
There are several notes that apparently solve the problem with support packages that are applied in our system (for example 397011 or 614553). Inthis case our system is updated.
Can you help me please.
Thanks
Gabriel.-Hi
Are you really sure https://websmp101.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=397011&_NLANG=E
is applied correctly ?
Try downloading with snote and see if it gets marked 'not relevant',
( are you on release 4.6 ? )
Given the nature of the problem ( and the fact that this issue is known ) , the best seems log an OSS support request
rgds
Dirk -
Short dump during ME23N transaction due to missing field in KOMP table
Hi All,
We have just upgraded to Business Suite 7.0 and are experiencing the following error:
Short dump during processing of transaction ME23N - error is in program SAPLV61A when the system calls the following field: KOMP_SERVICE_PARAM2 (this does not exist in KOMP). We need to get this resolved as soon as possible, It appears that SAP have removed this field from the table KOMP but the standard programme is still looking for this field. Can anyone provide an oss note number or insight into how to resolve this issue please.
Many Thanks
AmandaDear,
This problem is caused by a missing initialization of the structure KOMP in the program SAPLV61A.
The problem may also occur during , when the "Create PO automatically" indicator (TVAP-ALEKZ) is set for the relevant item category in the item category Customizing (transaction VOV7). In this case, the data of the purchase order item that was previously processed is used for the back update of the sales order from the purchase order in KOMP.
Add the following import parameter to the function module RV_KONV_SELECT:
Parameter name COMM_ITEM_I
Typing LIKE
Associated type KOMP
Optional X
Pass Value X
Please refer the OSS note 1261566.
Regards,
R.Brahmankar
Maybe you are looking for
-
Flag de NFe impressa no monitor
Bom dia! Pessoal, ao analisar os campos do monitor, verifiquei que o campo Imprimida fica em branco, mesmo que a nota ja tenha sido impressa. Verifiquei que esse campo fica na tabela j_1bnfe_active e não é o mesmo campo que esta na J_1BNFDOC-PRINTD.
-
How to install adobe reader to my site [spam link removed] so that pdf file can be read directly in my site instead of getting downloaded ?
-
Keynote to quicktime movie no sound?
I have a keynote presentation which consists of several embedded video clips. When playing this presentation live to my class there is no problem at all and everything functions perfectly. When exporting to QuickTime to put on my classroom website, t
-
Crystal Reports version 13 managed api's run slower than native version 11
Hello, I am a senior engineer, working in a project of porting client code written in C++ using Crystal 11. It uses the native COM api like shown approximately in the following code fragment:- IApplicationPtr pApplication; pApplication.CreateInstance
-
"Quartz Scheduler failed to initialize" error in application log
We are BIPublisher 10.1.3.4 as J2EE app and I am getting this error in the application log. I have created myDS datasource to get rid of the following error. But no success.. Please Help.. Thanks! Srini 09/01/09 15:13:43.298 [ecid: 10.39.38.45:96428: