Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Run Time Error causing problem!

Former Member
3,073

Dear All,

I am getting the following error when i am trying to save my sales order.

We have maintained the Credit Limit on delivery in our organisation and this run time error is coming during saving the sales order:

Runtime Errors MESSAGE_TYPE_X

Date and Time 14.10.2011 11:04:22

Short text

The current application triggered a termination with a short dump.

What happened?

The current application program detected a situation which really

should not occur. Therefore, a termination with a short dump was

triggered on purpose by the key word MESSAGE (type X).

Error analysis

Short text of error message:

Duplicate owners: Contact LO-VC development

Long text of error message:

Technical information about the message:

Message class....... "CUIB1"

Number.............. 699

Variable 1.......... " "

Variable 2.......... " "

Variable 3.......... " "

Variable 4.......... " "

Trigger Location of Runtime Error

Program CL_CBASE_SPECIAL_ERP==========CP

Include CL_CBASE_SPECIAL_ERP==========CM006

Row 51

Module type (METHOD)

Module Name IF_CBASE_CHECK~CHECK_OWNER

ce Code Extract

SourceCde

1 it_owner = lt_owner

2 IMPORTING

3 et_instance_owner = lt_inst_owner ).

4

5 LOOP AT lt_inst_owner REFERENCE INTO ls_inst_owner

6 WHERE instance <> iv_root_instance

7 AND del_flag IS INITIAL.

8

9 TRY.

0 * check configuration is marked for deletion

1 cl_cbase=>get_current_cbase_by_instance(

2 EXPORTING

3 iv_instance = ls_inst_owner->instance

4 iv_check_only_buffer = ggc_true

5 IMPORTING

6 eo_cbase = lo_cbase ).

7

8 * no deletion

9 CHECK lo_cbase->marked_for_deletion( ) IS INITIAL.

0 * no owner change

lo_cbase->get_owner_of_cfg(

EXPORTING

iv_instance = ls_inst_owner->instance

IMPORTING

es_owner = ls_other_owner ).

CHECK ls_other_owner = is_owner.

CATCH cx_cbase_error . "#EC NO_HANDLER

ENDTRY.

MESSAGE x699(cuib1).

ENDLOOP.

CATCH cx_cbase_error . "#EC NO_HANDLER

ENDTRY.

ENDMETHOD.

Kindly help me out to find a possible solution for this as i have very less idea to solve this because i m SD Consultant.

Regards,

Ashu

7 REPLIES 7

koolspy_ultimate
Active Contributor
0 Kudos
521

Hi ashu,

see oss notes 1172946

To view this link you need to have market place user id & password[Click here|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1172946]

Regards,

koolspy.

0 Kudos
521

Dear Koolspy,

How to solve this issue.

Please suggest.

Regards,

Ashu

0 Kudos
521
CHECK ls_other_owner = is_owner.
CATCH cx_cbase_error . "#EC NO_HANDLER
ENDTRY.

MESSAGE x699(cuib1).
ENDLOOP.

Replace your code as Message E699(cuib1)

0 Kudos
521

Hi,

consult your basis admin to apply the above note.

( Did you open that link which i had given earlier. )

That note must be applied by basis admin only.

So that your problem will be solved.

Regards,

Koolspy.

deepak_dhamat
Active Contributor
0 Kudos
521

Hi ,

Note 1172946 - Dump in sales order after configuration change using BAPI

below is Describtion

Summary

Symptom

You block the configuration profile of a configurable material, for example, to change the configuration profile. However, the configurable material has already been used in sales orders.
In this situation, you use the BAPI_SALESORDER_CHANGE to change the configuration of one of these orders. In spite of the blocked configuration profile, the system processes the BAPI without issuing an error message.
After unblocking the configuration profile, you open the relevant order in transaction VA02 and perform further characteristic value assignments.
If you then save the order, the short dump "MESSAGE_TYPE_X" occurs and the system issues message CUIB1 699 ("Duplicate owners: Contact LO-VC development").


Other terms

VBAP-CUOBJ, CUOBJ, MESSAGE_TYPE_X, CUIB1699, CUIB1 699, owner, IBINOWN, configuration, BAPI_SALESORDER_CHANGE, BAPI


Reason and Prerequisites

This problem is due to a program error.

During the processing of the BAPI, CUOBJ is deleted from the order item due to the blocked configuration, but the owner in IBINOWN is not deleted. After a new characteristic value assignment in VA02, the system tries to write a further entry for the owner to the table IBINOWN. However, since the old entry still exists, a short dump occurs.


Solution

Implement the attached program corrections.

regards

Deepak.

0 Kudos
521

Hi ,

Tell your BASIS Guy to implement Above Note using Snote :

if you want to confirm The latest code in your Standard include FV45SFCO_CONFIGURATION_PROCES1 .

Check This code is there or NOt

Find code

if da_conf_subrc > 0.

    clear vbap-stdat.
    clear vbap-cuobj.
    if not call_bapi is initial and
     not *vbap-cuobj is initial and
     not vbak-vbeln is initial.
     call function 'CUCB_GET_OWNER_OF_CFG'
         exporting
              i_instance = *vbap-cuobj
         importing
              e_owner    = da_owner
         exceptions
              others     = 1.
     if sy-subrc = 0.
       da_key(10) = vbak-vbeln.
       da_key+10(6) = xvbap-posnr.
       if da_owner-object_type eq config_vbps and
          da_owner-object_key  eq da_key.
         call function 'CUCB_CHECK_AND_DELETE_CONF'
              exporting
                   root_instance       = *vbap-cuobj
                   owner               = da_owner
              exceptions
                   invalid_instance    = 1
                   not_a_root_instance = 2
                   invalid_owner       = 3
                   not_registered      = 4
                   others              = 5.
       endif.
     endif.
   endif.
    message i360 with us_matnr da_conf_subrc.

Former Member
0 Kudos
521

Thanks to all for help..