Configuration dumping while saving the PO CUIB1 X699

[Aparna_Ajayan]

Dear All,

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

We are using plant-based configuration and when i am trying to change the plant after saving the PO it is dumping with the error message CUIB1 X699.

Runtime Errors MESSAGE_TYPE_X

Date and Time 

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.

Regards,
Aparna

[rattaiah88]

This is Very Common Error which we are getting for all executions. So please double check Configuration once again