<?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 Re: Regarding BOM items overwrite in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-bom-items-overwrite/m-p/3983505#M951588</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Changing a Material BOM&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the standard system, you use the following function modules to change a material BOM:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CSAP_MAT_BOM_OPEN&lt;/P&gt;&lt;P&gt;CSAP_BOM_ITEM_MAINTAIN&lt;/P&gt;&lt;P&gt;CSAP_MAT_BOM_CLOSE&lt;/P&gt;&lt;P&gt;Open BOM: CSAP_MAT_BOM_OPEN&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This function module is used to open a BOM for changes. The BOM is imported with the relevant valid-from date and is locked. Provided that no error occurs opening the BOM, the result returned by the module is the BOM header data, a table of BOM items, and a table of object dependencies.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;INPUT:&lt;/P&gt;&lt;P&gt; Material (MATERIAL)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  Plant (PLANT)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  BOM usage (BOM_USAGE)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  Valid-from date (VALID_FROM)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  Change number (CHANGE_NO)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  Revision level (REVISION_LEVEL)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  Indicator FL_NO_CHANGE_DOC (do not write change documents)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;OUTPUT:&lt;/P&gt;&lt;P&gt; BOM header data (O_STKO)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  Table T_STPO (BOM items)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  Table T_DEP_DATA (object dependencies basic data)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  Table T_DEP_DESCR (object dependencies descriptions)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  Table T_DEP_ORDER (object dependencies allocation)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  Table T_DEP_SOURCE (object dependencies source code)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  Table T_DEP_DOC (object dependencies document)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Maintain BOM Items: CSAP_BOM_ITEM_MAINTAIN&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once you have opened a BOM successfully (without errors), you can use this function module to process the individual BOM items.&lt;/P&gt;&lt;P&gt;You can:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create new items&lt;/P&gt;&lt;P&gt;The fields for item node and item counter must be initial when you create a new item.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Change items&lt;/P&gt;&lt;P&gt;From the table of BOM items, select the item you want to change, and transfer the changed data. The fields for item node and item counter must contain a value, because these are the fields used to uniquely identify an item in a BOM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Delete items&lt;/P&gt;&lt;P&gt;From the table of BOM items, select the item you want to delete, and set the deletion indicator. The fields for item node and item counter must contain a value.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Maintain object dependencies&lt;/P&gt;&lt;P&gt;If you want to change or delete a local object dependency for a BOM item that has more than one dependency, enter the internal name of the dependency.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You cannot use the external name that you entered when you created the dependency to identify the data belonging to a local dependency.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;INPUT:&lt;/P&gt;&lt;P&gt; BOM item (I_STPO) &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  Table T_DEP_DATA (object dependencies basic data)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  Table T_DEP_DESCR (object dependencies descriptions)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  Table T_DEP_ORDER (object dependencies allocation)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  Table T_DEP_SOURCE (object dependencies source code)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  Table T_DEP_DOC (object dependencies document)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You cannot change the item category of an existing item.&lt;/P&gt;&lt;P&gt;You can only change each item once in one session (between when you open and close the BOM).&lt;/P&gt;&lt;P&gt;If you see the error message "Item cannot be changed" in the log, the following reasons may apply:&lt;/P&gt;&lt;P&gt;The item is not valid on the valid-from date entered, because it becomes valid at a later date. &lt;/P&gt;&lt;P&gt;Object dependencies are allocated to the item, but the change number you used to open the BOM is not active for object dependencies. &lt;/P&gt;&lt;P&gt;The item has already been processed with another change number on the valid-from date entered.&lt;/P&gt;&lt;P&gt;Close BOM: CSAP_MAT_BOM_CLOSE&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once you have made your changes, use this function module to close the BOM. This saves the changes, unlocks the BOM, and writes the log.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The BOM is only saved if at least one item was changed successfully.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please note the following points when changing BOMs:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is no function module for changing header data.&lt;/P&gt;&lt;P&gt;The same restrictions apply as for creating a BOM.&lt;/P&gt;&lt;P&gt;You can only process one alternative or variant. If you do not enter an alternative when you call function module CSAP_MAT_BOM_OPEN, the function module opens alternative "01".&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 09 Jun 2008 05:43:17 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-06-09T05:43:17Z</dc:date>
    <item>
      <title>Regarding BOM items overwrite</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-bom-items-overwrite/m-p/3983504#M951587</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;I have a requirement to overwrite the BOM components with the new components.The program should just overwrite the existing components.The program is not required to check the existing components it should just overwrite with the new structure to the existing BOM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am trying with the function module CSAP_BOM_ITEM_MAINTAIN but I am not succeeding on this.&lt;/P&gt;&lt;P&gt;Please suggest somebody how to do this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Mahesh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Jun 2008 05:35:41 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-bom-items-overwrite/m-p/3983504#M951587</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-09T05:35:41Z</dc:date>
    </item>
    <item>
      <title>Re: Regarding BOM items overwrite</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-bom-items-overwrite/m-p/3983505#M951588</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Changing a Material BOM&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the standard system, you use the following function modules to change a material BOM:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CSAP_MAT_BOM_OPEN&lt;/P&gt;&lt;P&gt;CSAP_BOM_ITEM_MAINTAIN&lt;/P&gt;&lt;P&gt;CSAP_MAT_BOM_CLOSE&lt;/P&gt;&lt;P&gt;Open BOM: CSAP_MAT_BOM_OPEN&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This function module is used to open a BOM for changes. The BOM is imported with the relevant valid-from date and is locked. Provided that no error occurs opening the BOM, the result returned by the module is the BOM header data, a table of BOM items, and a table of object dependencies.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;INPUT:&lt;/P&gt;&lt;P&gt; Material (MATERIAL)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  Plant (PLANT)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  BOM usage (BOM_USAGE)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  Valid-from date (VALID_FROM)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  Change number (CHANGE_NO)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  Revision level (REVISION_LEVEL)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  Indicator FL_NO_CHANGE_DOC (do not write change documents)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;OUTPUT:&lt;/P&gt;&lt;P&gt; BOM header data (O_STKO)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  Table T_STPO (BOM items)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  Table T_DEP_DATA (object dependencies basic data)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  Table T_DEP_DESCR (object dependencies descriptions)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  Table T_DEP_ORDER (object dependencies allocation)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  Table T_DEP_SOURCE (object dependencies source code)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  Table T_DEP_DOC (object dependencies document)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Maintain BOM Items: CSAP_BOM_ITEM_MAINTAIN&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once you have opened a BOM successfully (without errors), you can use this function module to process the individual BOM items.&lt;/P&gt;&lt;P&gt;You can:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create new items&lt;/P&gt;&lt;P&gt;The fields for item node and item counter must be initial when you create a new item.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Change items&lt;/P&gt;&lt;P&gt;From the table of BOM items, select the item you want to change, and transfer the changed data. The fields for item node and item counter must contain a value, because these are the fields used to uniquely identify an item in a BOM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Delete items&lt;/P&gt;&lt;P&gt;From the table of BOM items, select the item you want to delete, and set the deletion indicator. The fields for item node and item counter must contain a value.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Maintain object dependencies&lt;/P&gt;&lt;P&gt;If you want to change or delete a local object dependency for a BOM item that has more than one dependency, enter the internal name of the dependency.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You cannot use the external name that you entered when you created the dependency to identify the data belonging to a local dependency.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;INPUT:&lt;/P&gt;&lt;P&gt; BOM item (I_STPO) &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  Table T_DEP_DATA (object dependencies basic data)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  Table T_DEP_DESCR (object dependencies descriptions)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  Table T_DEP_ORDER (object dependencies allocation)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  Table T_DEP_SOURCE (object dependencies source code)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  Table T_DEP_DOC (object dependencies document)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You cannot change the item category of an existing item.&lt;/P&gt;&lt;P&gt;You can only change each item once in one session (between when you open and close the BOM).&lt;/P&gt;&lt;P&gt;If you see the error message "Item cannot be changed" in the log, the following reasons may apply:&lt;/P&gt;&lt;P&gt;The item is not valid on the valid-from date entered, because it becomes valid at a later date. &lt;/P&gt;&lt;P&gt;Object dependencies are allocated to the item, but the change number you used to open the BOM is not active for object dependencies. &lt;/P&gt;&lt;P&gt;The item has already been processed with another change number on the valid-from date entered.&lt;/P&gt;&lt;P&gt;Close BOM: CSAP_MAT_BOM_CLOSE&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once you have made your changes, use this function module to close the BOM. This saves the changes, unlocks the BOM, and writes the log.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The BOM is only saved if at least one item was changed successfully.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please note the following points when changing BOMs:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is no function module for changing header data.&lt;/P&gt;&lt;P&gt;The same restrictions apply as for creating a BOM.&lt;/P&gt;&lt;P&gt;You can only process one alternative or variant. If you do not enter an alternative when you call function module CSAP_MAT_BOM_OPEN, the function module opens alternative "01".&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Jun 2008 05:43:17 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-bom-items-overwrite/m-p/3983505#M951588</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-09T05:43:17Z</dc:date>
    </item>
  </channel>
</rss>

