<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic error 'NOT_AL_INPUT_DATA_PROCESSED' in BAPI_SALESORDER_CREATEFROMDAT2 in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/error-not-al-input-data-processed-in-bapi-salesorder-createfromdat2/m-p/6828542#M1471111</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Iu2019ve problems with creating sales orders with multi-level configured materials. &lt;/P&gt;&lt;P&gt;An internal error u2018NOT_ALL_INPUT_DATA_PROCSSES u2018 occurs .&lt;/P&gt;&lt;P&gt;The tables&lt;/P&gt;&lt;P&gt; CFGS_REF, CFGS_INST, CFGS_PART_OF, CFGS_VALUE   are filled according note 549563 u2013 Bapi filling config structures . &lt;/P&gt;&lt;P&gt;But I have my doubts about the items and sched lines .  Do the subitems be mentioned in those ?  They donu2019t have to be visible in the sales order .&lt;/P&gt;&lt;P&gt;In following overview of tables are ment to create an sales order with a material (non-KMAT)  item 10 material 000000000007041300&lt;/P&gt;&lt;P&gt;With a KMAT-material item 20 material 000000000008001556&lt;/P&gt;&lt;P&gt;This is an multilevel material with 2 subitems of kmat  000000000008001558&lt;/P&gt;&lt;P&gt; A trace is also mentioned .&lt;/P&gt;&lt;P&gt;Items in &lt;/P&gt;&lt;P&gt;Itm_number hg_lv_item  p_itm_no  material&lt;/P&gt;&lt;P&gt;000010	000000			000000000007041300&lt;/P&gt;&lt;P&gt;000020	000000	000020	000000000008001556&lt;/P&gt;&lt;P&gt;Items inx&lt;/P&gt;&lt;P&gt;Itm_number Flag  p_itm_no  material&lt;/P&gt;&lt;P&gt;000010	I			X&lt;/P&gt;&lt;P&gt;000020	I		X	X&lt;/P&gt;&lt;P&gt;Schedule IN&lt;/P&gt;&lt;P&gt;Itm_number     sched_line &lt;/P&gt;&lt;P&gt;1	000010	0010&lt;/P&gt;&lt;P&gt;2	000020	0020&lt;/P&gt;&lt;P&gt;Schedule inx&lt;/P&gt;&lt;P&gt;Itm_number     sched_line 		flag&lt;/P&gt;&lt;P&gt;000010	0010				I&lt;/P&gt;&lt;P&gt;000020	0020				I&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CFGS_REF&lt;/P&gt;&lt;P&gt;Posex		config_id	root_id	&lt;/P&gt;&lt;P&gt;000020	000001	00000001&lt;/P&gt;&lt;P&gt;("        gs_order_cfgs_ref-SCE       = '1'.&lt;/P&gt;&lt;P&gt;"        gs_order_cfgs_ref-KBNAME    =  gs_cbase_data-type_of-object_key.&lt;/P&gt;&lt;P&gt;"        gs_order_cfgs_ref-KBVERSION = '001'.    Filled gives a communication error) &lt;/P&gt;&lt;P&gt;CFGS_INST&lt;/P&gt;&lt;P&gt;Config_id  inst_id    obj type cl_type   obj_key&lt;/P&gt;&lt;P&gt;000001	00000001	MARA		300	000000000008001556&lt;/P&gt;&lt;P&gt;000001	00000002	MARA		300	000000000008001558&lt;/P&gt;&lt;P&gt;000001	00000003	MARA		300	000000000008001558&lt;/P&gt;&lt;P&gt;Cfgs_part_of &lt;/P&gt;&lt;P&gt;Config_id  parent_id  inst_id   part  obj type cl_type   obj_key&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;000001	00000001	00000002	0020	MARA	 300	000000000008001558&lt;/P&gt;&lt;P&gt;000001	00000001	00000003	0020	MARA	 300	000000000008001558&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CFGS_VALUE &lt;/P&gt;&lt;P&gt;000001	00000001	CH_COLOR		6005&lt;/P&gt;&lt;P&gt;000001	00000001	CH_PALLET_DIMENSION		1500X2000&lt;/P&gt;&lt;P&gt;000001	00000002	CH_WING_TYPE		ROB_09_ZW&lt;/P&gt;&lt;P&gt;000001	00000002	CH_WING_LATCH_LOCK		G&lt;/P&gt;&lt;P&gt;000001	00000003	CH_WING_TYPE		ROB_09_ZW&lt;/P&gt;&lt;P&gt;000001	00000003	CH_WING_LATCH_LOCK		S&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In SAPLCUXC                       / LCUXCF03&lt;/P&gt;&lt;P&gt;FORM                           / CHECK_ALL_INPUT_PROCESSED&lt;/P&gt;&lt;P&gt;GL_CURR_CFG_XINST_TAB[]                              processed &lt;/P&gt;&lt;P&gt;000001	00000001	MARA	300	000000000008001556     X&lt;/P&gt;&lt;P&gt;000001	00000002	MARA	300	000000000008001558&lt;/P&gt;&lt;P&gt;000001	00000003	MARA	300	000000000008001558&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Trace : &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;000052  28      574   Value 60X40X1,5 entered for characteristic 0000014388&lt;/P&gt;&lt;P&gt;000053&lt;/P&gt;&lt;P&gt;000054  CX   I  330&lt;/P&gt;&lt;P&gt;000055  CX   I  331&lt;/P&gt;&lt;P&gt;000056  CX   I  330&lt;/P&gt;&lt;P&gt;000057  CX   I  331&lt;/P&gt;&lt;P&gt;000058  CX   I  330&lt;/P&gt;&lt;P&gt;000059  CX   I  331&lt;/P&gt;&lt;P&gt;000060  CX   I  330&lt;/P&gt;&lt;P&gt;000061  CX   I  331&lt;/P&gt;&lt;P&gt;000062  CX   I  330&lt;/P&gt;&lt;P&gt;000063  CX   I  331&lt;/P&gt;&lt;P&gt;000064  CX   I  330&lt;/P&gt;&lt;P&gt;000065  CX   I  331&lt;/P&gt;&lt;P&gt;000066  CX   I  330&lt;/P&gt;&lt;P&gt;000067  CX   I  331&lt;/P&gt;&lt;P&gt;000068  CX   I  330&lt;/P&gt;&lt;P&gt;000069  CX   I  331&lt;/P&gt;&lt;P&gt;000070  CX   I  330&lt;/P&gt;&lt;P&gt;000071  CX   I  331&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for a reply&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 07 Apr 2010 12:43:22 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2010-04-07T12:43:22Z</dc:date>
    <item>
      <title>error 'NOT_AL_INPUT_DATA_PROCESSED' in BAPI_SALESORDER_CREATEFROMDAT2</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/error-not-al-input-data-processed-in-bapi-salesorder-createfromdat2/m-p/6828542#M1471111</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Iu2019ve problems with creating sales orders with multi-level configured materials. &lt;/P&gt;&lt;P&gt;An internal error u2018NOT_ALL_INPUT_DATA_PROCSSES u2018 occurs .&lt;/P&gt;&lt;P&gt;The tables&lt;/P&gt;&lt;P&gt; CFGS_REF, CFGS_INST, CFGS_PART_OF, CFGS_VALUE   are filled according note 549563 u2013 Bapi filling config structures . &lt;/P&gt;&lt;P&gt;But I have my doubts about the items and sched lines .  Do the subitems be mentioned in those ?  They donu2019t have to be visible in the sales order .&lt;/P&gt;&lt;P&gt;In following overview of tables are ment to create an sales order with a material (non-KMAT)  item 10 material 000000000007041300&lt;/P&gt;&lt;P&gt;With a KMAT-material item 20 material 000000000008001556&lt;/P&gt;&lt;P&gt;This is an multilevel material with 2 subitems of kmat  000000000008001558&lt;/P&gt;&lt;P&gt; A trace is also mentioned .&lt;/P&gt;&lt;P&gt;Items in &lt;/P&gt;&lt;P&gt;Itm_number hg_lv_item  p_itm_no  material&lt;/P&gt;&lt;P&gt;000010	000000			000000000007041300&lt;/P&gt;&lt;P&gt;000020	000000	000020	000000000008001556&lt;/P&gt;&lt;P&gt;Items inx&lt;/P&gt;&lt;P&gt;Itm_number Flag  p_itm_no  material&lt;/P&gt;&lt;P&gt;000010	I			X&lt;/P&gt;&lt;P&gt;000020	I		X	X&lt;/P&gt;&lt;P&gt;Schedule IN&lt;/P&gt;&lt;P&gt;Itm_number     sched_line &lt;/P&gt;&lt;P&gt;1	000010	0010&lt;/P&gt;&lt;P&gt;2	000020	0020&lt;/P&gt;&lt;P&gt;Schedule inx&lt;/P&gt;&lt;P&gt;Itm_number     sched_line 		flag&lt;/P&gt;&lt;P&gt;000010	0010				I&lt;/P&gt;&lt;P&gt;000020	0020				I&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CFGS_REF&lt;/P&gt;&lt;P&gt;Posex		config_id	root_id	&lt;/P&gt;&lt;P&gt;000020	000001	00000001&lt;/P&gt;&lt;P&gt;("        gs_order_cfgs_ref-SCE       = '1'.&lt;/P&gt;&lt;P&gt;"        gs_order_cfgs_ref-KBNAME    =  gs_cbase_data-type_of-object_key.&lt;/P&gt;&lt;P&gt;"        gs_order_cfgs_ref-KBVERSION = '001'.    Filled gives a communication error) &lt;/P&gt;&lt;P&gt;CFGS_INST&lt;/P&gt;&lt;P&gt;Config_id  inst_id    obj type cl_type   obj_key&lt;/P&gt;&lt;P&gt;000001	00000001	MARA		300	000000000008001556&lt;/P&gt;&lt;P&gt;000001	00000002	MARA		300	000000000008001558&lt;/P&gt;&lt;P&gt;000001	00000003	MARA		300	000000000008001558&lt;/P&gt;&lt;P&gt;Cfgs_part_of &lt;/P&gt;&lt;P&gt;Config_id  parent_id  inst_id   part  obj type cl_type   obj_key&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;000001	00000001	00000002	0020	MARA	 300	000000000008001558&lt;/P&gt;&lt;P&gt;000001	00000001	00000003	0020	MARA	 300	000000000008001558&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CFGS_VALUE &lt;/P&gt;&lt;P&gt;000001	00000001	CH_COLOR		6005&lt;/P&gt;&lt;P&gt;000001	00000001	CH_PALLET_DIMENSION		1500X2000&lt;/P&gt;&lt;P&gt;000001	00000002	CH_WING_TYPE		ROB_09_ZW&lt;/P&gt;&lt;P&gt;000001	00000002	CH_WING_LATCH_LOCK		G&lt;/P&gt;&lt;P&gt;000001	00000003	CH_WING_TYPE		ROB_09_ZW&lt;/P&gt;&lt;P&gt;000001	00000003	CH_WING_LATCH_LOCK		S&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In SAPLCUXC                       / LCUXCF03&lt;/P&gt;&lt;P&gt;FORM                           / CHECK_ALL_INPUT_PROCESSED&lt;/P&gt;&lt;P&gt;GL_CURR_CFG_XINST_TAB[]                              processed &lt;/P&gt;&lt;P&gt;000001	00000001	MARA	300	000000000008001556     X&lt;/P&gt;&lt;P&gt;000001	00000002	MARA	300	000000000008001558&lt;/P&gt;&lt;P&gt;000001	00000003	MARA	300	000000000008001558&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Trace : &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;000052  28      574   Value 60X40X1,5 entered for characteristic 0000014388&lt;/P&gt;&lt;P&gt;000053&lt;/P&gt;&lt;P&gt;000054  CX   I  330&lt;/P&gt;&lt;P&gt;000055  CX   I  331&lt;/P&gt;&lt;P&gt;000056  CX   I  330&lt;/P&gt;&lt;P&gt;000057  CX   I  331&lt;/P&gt;&lt;P&gt;000058  CX   I  330&lt;/P&gt;&lt;P&gt;000059  CX   I  331&lt;/P&gt;&lt;P&gt;000060  CX   I  330&lt;/P&gt;&lt;P&gt;000061  CX   I  331&lt;/P&gt;&lt;P&gt;000062  CX   I  330&lt;/P&gt;&lt;P&gt;000063  CX   I  331&lt;/P&gt;&lt;P&gt;000064  CX   I  330&lt;/P&gt;&lt;P&gt;000065  CX   I  331&lt;/P&gt;&lt;P&gt;000066  CX   I  330&lt;/P&gt;&lt;P&gt;000067  CX   I  331&lt;/P&gt;&lt;P&gt;000068  CX   I  330&lt;/P&gt;&lt;P&gt;000069  CX   I  331&lt;/P&gt;&lt;P&gt;000070  CX   I  330&lt;/P&gt;&lt;P&gt;000071  CX   I  331&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for a reply&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Apr 2010 12:43:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/error-not-al-input-data-processed-in-bapi-salesorder-createfromdat2/m-p/6828542#M1471111</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-04-07T12:43:22Z</dc:date>
    </item>
    <item>
      <title>Re: error 'NOT_AL_INPUT_DATA_PROCESSED' in BAPI_SALESORDER_CREATEFROMDAT2</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/error-not-al-input-data-processed-in-bapi-salesorder-createfromdat2/m-p/6828543#M1471112</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Via the function BAPISDORDER_GETDETAILEDLIST  for a order with a multi_level material the data as the should be in the CFGS-tables can be found .   Then it is the matter to fill them correctly for the BAPI .   In this case the problem was the bom-item-number in the cfgs_part_of number .&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Apr 2010 08:51:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/error-not-al-input-data-processed-in-bapi-salesorder-createfromdat2/m-p/6828543#M1471112</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-04-08T08:51:43Z</dc:date>
    </item>
  </channel>
</rss>

