XML Import in BRFplus - Bug or Feature? "The data object is referenced by a structure that is also bound to a structure in the Dictionary."

[ttrapp]

As a result object of a function I have a structure ZSTR1 with complete DDIC binding: ZSTR1 contains a table type ZTAB2 with line type ZSTR2.

The whole application is in system A and a copy in system B. Now I changing the DDIC (and so the DDIC binding) from ZTAB2 to ZTAB3 with line type ZSTR3 in system A and perform an XML import of the application in system B.

The result is the error "The data object is referenced by a structure that is also bound to a structure in the Dictionary" described in OSS note 1575179 - Additional checks for bound data structures. I consider this as a bug since during an XML import this check makes no sense because the import guarantess consistency. What do you think?

Best Regards,

Tobias

[carsten_ziegler · Accepted solution]

Would you pls give is message class and number. Thanks.

[ttrapp · Accepted solution]

It is FDT_CORE 491:

[carsten_ziegler · Accepted solution]

The message comes from CHECK_CLEAR_BINDING which in turn may be called by several methods. Can you post the call stack?

[ttrapp · Accepted solution]

Please be warned - it is NW 7.40 SP7.

The problem occurs here:

METHOD if_fdt_table~set_structure.

* see internal message 002824759 2007

   CHECK iv_structure_id NE if_fdt_table~get_structure( ). ">>>

* we may not call the set and the clear methods when there is no change

* in the structure; UI may call the method over and over again

* just to transport UI values to backend

   check_clear_binding( ). "May throw CX_FDT_INPUT

   set_structure( iv_structure_id ).

* Check whether it is called from the XML Import

* If true then do not clear the DDIC binding.

   IF mv_in_xml_import EQ abap_false.

     clear_gdt_binding( ).

     clear_ddic_binding( ).

   ENDIF.

ENDMETHOD.

At the moment I am a little bit confused because I thought the DDIC binding is valid in the source. In fact the DDIC binding is OK in the data element that caused the trouble.

Here is the stack:

31	CL_FDT_DATA_OBJECT============CP	CL_FDT_DATA_OBJECT============CM024	16	METHOD	CHECK_CLEAR_BINDING
30	CL_FDT_TABLE==================CP	CL_FDT_TABLE==================CM00C	8	METHOD	IF_FDT_TABLE~SET_STRUCTURE
29	CL_FDT_TABLE==================CP	CL_FDT_TABLE==================CM00L	36	METHOD	IF_FDT_DATA_EXCHANGE_INTERNAL~IMPORT_XML
28	CL_FDT_DATA_EXCHANGE==========CP	CL_FDT_DATA_EXCHANGE==========CM003	138	METHOD	IMPORT_ID_FROM_QUEUE
27	CL_FDT_DATA_EXCHANGE==========CP	CL_FDT_DATA_EXCHANGE==========CM002	5	METHOD	HANDLE_OBJECT_ID_AS_ATTRIBUTE
26	CL_FDT_STRUCTURE==============CP	CL_FDT_STRUCTURE==============CM00K	32	METHOD	IF_FDT_DATA_EXCHANGE_INTERNAL~IMPORT_XML
25	CL_FDT_DATA_EXCHANGE==========CP	CL_FDT_DATA_EXCHANGE==========CM003	138	METHOD	IMPORT_ID_FROM_QUEUE
24	CL_FDT_DATA_EXCHANGE==========CP	CL_FDT_DATA_EXCHANGE==========CM010	36	METHOD	IMPORT_OBJECTS
23	CL_FDT_DATA_EXCHANGE==========CP	CL_FDT_DATA_EXCHANGE==========CM01N	476	METHOD	IMPORT_XML
22	CL_FDT_DATA_EXCHANGE==========CP	CL_FDT_DATA_EXCHANGE==========CM00C	93	METHOD	IF_FDT_DATA_EXCHANGE~IMPORT_XML
21	CL_FDT_WD_XML_IMPORT==========CP	CL_FDT_WD_XML_IMPORT==========CM002	54	METHOD	IF_FDT_WD_MODEL~SET_MODEL_BY_NODE
20	CL_FDT_WD_MODEL===============CP	CL_FDT_WD_MODEL===============CM004	9	METHOD	IF_FDT_WD_MODEL~SET_MODEL
19	/1BCWDY/0O2TOIC56OS55158LR1X==CP	/1BCWDY/B_0O2TOIC56OS55185MJQM	510	METHOD	UPLOAD_XML_CONTENT
18	/1BCWDY/0O2TOIC56OS55158LR1X==CP	/1BCWDY/B_0O2TOIC56OS55185MJQM	137	METHOD	IF_COMPONENTCONTROLLER~UPLOAD_XML_CONTENT
17	/1BCWDY/0O2TOIC56OS55158LR1X==CP	/1BCWDY/B_0O2TOIC56OS55185MJWY	1434	METHOD	ONACTIONUPLOAD_XML
16	/1BCWDY/0O2TOIC56OS55158LR1X==CP	/1BCWDY/B_0O2TOIC56OS55185MJWY	257	METHOD	IF_WDR_VIEW_DELEGATE~WD_INVOKE_EVENT_HANDLER
15	CL_WDR_DELEGATING_VIEW========CP	CL_WDR_DELEGATING_VIEW========CM006	6	METHOD	INVOKE_EVENTHANDLER
14	CL_WDR_ACTION=================CP	CL_WDR_ACTION=================CM00A	38	METHOD	IF_WDR_ACTION~FIRE
13	CL_WDR_WINDOW_PHASE_MODEL=====CP	CL_WDR_WINDOW_PHASE_MODEL=====CM00U	99	METHOD	DO_HANDLE_ACTION_EVENTS
12	CL_WDR_WINDOW_PHASE_MODEL=====CP	CL_WDR_WINDOW_PHASE_MODEL=====CM002	95	METHOD	PROCESS_REQUEST
11	CL_WDR_WINDOW=================CP	CL_WDR_WINDOW=================CM00V	12	METHOD	PROCESS_REQUEST
10	CL_WDR_MAIN_TASK==============CP	CL_WDR_MAIN_TASK==============CM00I	77	METHOD	EXECUTE
9	CL_WDR_MAIN_TASK==============CP	CL_WDR_MAIN_TASK==============CM00U	9	METHOD	IF_WDR_RUNTIME~EXECUTE
8	CL_WDR_CLIENT_ABSTRACT_HTTP===CP	CL_WDR_CLIENT_ABSTRACT_HTTP===CM01C	119	METHOD	HANDLE_REQUEST
7	CL_WDR_MAIN_TASK==============CP	CL_WDR_MAIN_TASK==============CM00J	89	METHOD	IF_HTTP_EXTENSION~HANDLE_REQUEST
6	CL_HTTP_SERVER================CP	CL_HTTP_SERVER================CM00I	632	METHOD	EXECUTE_REQUEST
5	SAPLHTTP_RUNTIME	LHTTP_RUNTIMEU02	1427	FUNCTION	HTTP_DISPATCH_REQUEST
4	SAPMHTTP	SAPMHTTP	12	MODULE (PBO)	%_HTTP_START
3			2	PBO MODULE	%_HTTP_START
2	SAPMHTTP		2	PBO SCREEN	10
1			0	TRANSACTION	()

[carsten_ziegler · Accepted solution]

Pls open a message with reference to this forum post.

The binding check must be relaxed. Thanks.

[Former Member · Accepted solution]

Hi Tobias ,

When this is solved , could you please share OSS Note number.

  We are exploring to use XML import in Implemention of BRF+  in our PLM Project.

This may be helpful for us.

Thanking you ,

Regards,

  Satya

[ttrapp · Accepted solution]

I don't think this will help you. Above mentioned problem is very exotic. In general XML import has some problems and you find many OSS notes with problems that are much more common.

Which NW release/SP are you using? A high SP level will help you.

Best Regards,

Tobias

[shwetars]

Note: 2360769 fixes the issue.