Online Tutorials & Training Materials | STechies.com
Register Login

Runtime Error in Delivery Processing Interview Questions and Answers

|| || 0

Runtime Error in Delivery Processing Interview Questions and Answers
Stechies

FAQ on Runtime Error in Delivery Processing

1. Runtime error SAPSQL_ARRAY_INSERT_DUPREC in LIPS_VERBUCHEN, what has to be done?

Answer:

Function 'Deliver sales order' and option 'Copy item number' cannot be used together if an item already exists in the delivery which has the same item number as the item to be copied from the order. Deactivate option 'Copy item number' in the Customizing of the copy control (Customizing transaction VTLA).

2. Runtime error SAPSQL_ARRAY_INSERT_DUPREC in SD_PARTNER_UPDATE?

Answer:

The most common cause for this runtime error is an incorrect logic in USEREXIT_SAVE_DOCUMENT_PREPARE or USEREXIT_SAVE_DOCUMENT in include MV50AFZ1.

This can be seen by the fact that, for example, several entries exist for one partner function in internal partner table XVBPA or by the fact that updates on internal tables exist which change the document number or the temporary $ number of a line because the positioning is not correct. The problem can also be caused by changes carried out to other internal tables such as for example XLIPS, XLIKP and must not initially be connected with the partner tables.

3. Runtime error MESSAGE_TYPE_X in FORM routine FV50PFLP LIPS_BEARBEITEN?

Answer:

This runtime error only appears in Release 4.6C when you use 'Deliver sales order' and indicator 'POSVO' in the Customizing of the copy control at the same time.

Read notes 4505 and 406798 and check whether indicator 'POSVO' is set for the combination used in the copy control Order -> Delivery.

In this context, read note 433304.

4. Runtime error DYNPRO_FIELD_CONVERSION in module MV50AO0F 'FELDAUSWAHL'?

Answer:

This runtime error indicates negative quantities in the database tables of delivery processing which can occur in connection with rounding problems. For the correction of the error, contact the SAP support.

5. Runtime error TSV_TNEW_PAGE_ALLOC_FAILED in function module SHP_SD_ORDER_ENQUEUE in transaction VL10?

Answer:

The R/3 memory parameters might be set incorrectly. For more information, refer to notes 166551, 103747, 97497 and 131030.

This runtime error also occurs if a data volume was selected which is too large (see note 565428). Restrict the selection of the orders and stock transport orders further, for example, with the delivery creation date, the delivery number or similar. The restriction of the selection by split criteria such as for example the shipping point or the ship-to-party does not always avoid the runtime error.

6. Runtime error TIME_OUT in transaction VL10, what has to be done?

Answer:

For certain settings in the user role of transaction VL10, the parallel processing is used for the delivery which starts a dialog mode. This dialog mode can terminate if a value which is too small was set for system parameter rdisp/max_wprun_time and this causes the above TIME_OUT runtime error.

First, check whether you can increase the value of system profile parameter 'rdisp/max_wprun_time' to such an extend that the runtime error no longer occurs. If this is not possible or sufficient, restrict the size of the packages which are transferred to the delivery. For information on this topic, refer to note 486028.

7. Runtime error CALL_FUNCTION_NO_RECEIVER in transaction VL10?

Answer:

Set the number of the parallel processes used to at least '1'. You find the corresponding field in the User role -> Max.no.tasks or via transaction VL10CUC. If you use a variant, save it again with the new settings.

8. Runtime error EXPORT_BUFFER_NO_MEMORY in transaction VL10?

Answer:

The export/import buffer can only buffer objects of a certain maximum size, approximately 20-25% of the buffer size rsdb/obj/buffersize, (see note 156957).
Check the size of the export/import buffer. As of Release 4.6, the following standard settings are recommended (note 103747):

rsdb/obj/buffersize 20000 (kB)
rsdb/obj/max_objects 20000
rsdb/obj/large_object_size 8192 (Byte)

If this information does not help and no other additional notes can be found in the SAP notes system, you can create a customer message giving the following information (depending on the runtime error) which you can find by displaying the runtime error with transaction ST22:

SAPSQL_ARRAY_INSERT_DUPREC

* 'Information on where termination occurred' from the runtime error

Example: The termination occurred in ABAP program 'AAAAAA', to be more precise in 'BBBBBB'. The main program was 'CCCCCC'. In the source code, the termination point is in line XY (when choosing the editor: XYZ) of ABAP source 'DDDDDD'. Program 'AAAAAA' was started in the update system.

* Contents of the line in which the termination occurs

Example: INSERT ABCD FROM TABLE ZABCD.

MESSAGE_TYPE_X

* 'Information on where termination occurred' from the runtime error (see above)

* Contents of the line in which the termination occurs

Example: MESSAGE x214 WITH 'AAAAA' 'BBBB'.

* Error analysis -> Technical information on the message:

Example: Message class ... 'GR'
Number............ 214
Variable 1....... 'AAAAA'
Variable 2........ 'BBBB'

TABLE_ILLEGAL_STATEMENT

* 'Information on where the termination occurred' from the runtime error (see above)

* Contents of the line in which termination occurs

TIME_OUT

* 'Information on where the termination occurred' from the runtime error (see above)

* 'What happened?' from the runtime error

* Excerpt from the 'Error analysis' from the runtime error

Example: The maximum runtime of a program is set by the profile parameter "rdisp/max_wprun_time". The current setting is *** seconds.

TSV_TNEW_PAGE_ALLOC_FAILED

* 'Error analysis' from the runtime error

Example: The internal table 'IT_2219' could not be enlarged further. The storage space for internal tables is managed in blocks. A new block with the size of 11776 bytes should be created. However, this storage space was no longer available in the roll area. At this point, table 'IT_2219' had 83952 entries.

* 'How to correct the error' from the runtime error

for example : Roll area................... 7341536
extended memory area (EM) 251045352
fixed storage space (HEAP) 6296208
Short area .................. 8063
Paging area ................. 24576
Max. address space ................. 534555424

* 'Information on where termination occurred' from the runtime error (see above)

* Contents of the line in which the termination occurred

RAISE_EXCEPTION

* 'Information on where termination occurred' from the runtime error (see above)

* Contents of the line in which the termination occurs

* Active calls / events

DYNPRO_SEND_IN_BACKGROUND

* 'Error analysis' from the runtime error

* Example: Current screen: 'SAPLCLFM' 1102.

* Active calls / events


Related Articles