Assemble Components Web Service - Material does not exist message 17873

[Former Member]

Hello all,

Trying to run teh webservice to assemble components however when porcessing the request using SOAP UI version 3.6.1 I get the error message: Material does not exist message 17873.

It clearly exists in SAP ME (5.2.6.10) as well as the Inventory ID information. It comes up fine within the As-Built Configuration.

Was wonderig if anyone else has had this problem and figured out what the problem was.

Here is the saop message:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:me="http://sap.com/xi/ME" xmlns:gdt="http://sap.com/xi/SAPGlobal/GDT">
   <soapenv:Header/>
   <soapenv:Body>
      <me:AssembleComponentsRequest_sync>
         <me:AssembleComponentsRequest>
            <me:CheckOperation>false</me:CheckOperation>
            <me:Event>baseFinished:AssemblyPoint</me:Event>
            <me:AssembleIdentifier>
               <me:AssyDataValue>
                  <me:Attribute>INVENTORY_ID</me:Attribute>
                  <me:Value>0000044E4110A00167098</me:Value>
               </me:AssyDataValue>
               <me:Identifier>0000044E4110</me:Identifier>
               <me:Quantity>1</me:Quantity>
               <me:RefDes>C1</me:RefDes>
               <me:Revision>A</me:Revision>
            </me:AssembleIdentifier>
            <me:OperationRef>
               <me:SiteRef>
                  <me:Site>1000</me:Site>
               </me:SiteRef>
               <me:Operation>PLACEMENT</me:Operation>
               <me:Revision>A</me:Revision>
            </me:OperationRef>
            <me:ParentSfc>
               <me:Sfc>MV220170</me:Sfc>
               <me:SiteRef>
                  <me:Site>1000</me:Site>
               </me:SiteRef>
            </me:ParentSfc>
            <me:ResourceRef>
               <me:SiteRef>
                  <me:Site>1000</me:Site>
               </me:SiteRef>
               <me:Resource>CXA_LINE1</me:Resource>
            </me:ResourceRef>
            <me:SiteRef>
               <me:Site>1000</me:Site>
            </me:SiteRef>
            <me:UserRef>
               <me:SiteRef>
                  <me:Site>1000</me:Site>
               </me:SiteRef>
               <me:UserId>XML_USER</me:UserId>
            </me:UserRef>
         </me:AssembleComponentsRequest>
      </me:AssembleComponentsRequest_sync>
   </soapenv:Body>
</soapenv:Envelope>

Here is the responce:

<SOAP-ENV:Envelope xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <SOAP-ENV:Body>
      <ns2:AssembleComponentsConfirmation_sync xmlns:ns2="http://sap.com/xi/ME" xmlns="http://sap.com/xi/SAPGlobal/GDT">
         <ns2:AssembleComponentsResponse>
            <ns2:InvalidIdentifier>
               <ns2:Error>Material "0000044E4110" does not exist (Message 17873)</ns2:Error>
               <ns2:Identifier>0000044E4110</ns2:Identifier>
               <ns2:RefDes>C1</ns2:RefDes>
            </ns2:InvalidIdentifier>
         </ns2:AssembleComponentsResponse>
      </ns2:AssembleComponentsConfirmation_sync>
   </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Any help would be greatly appreciated.

Thanks,

Mike

[former_member196557]

Mike,

Since ProductionXML and the UI will allow the assembly, the config in ME is correct. At this point you can either set up SQL tracing in ME/Netweaver, to see where the the SQL transactions launched by the WS request is failing to retrieve the information, or just log a support ticket with SAP.

- Steve

[Former Member]

Hi Sergiy and Steve,

Yes I agree that the ME System is setup correctly, that is why this is so wierd.

I turned on SQL Trace and I also did enable the logging in NetWeaver and there are no error messages displayed. The only ones logged are two INFO types:

The first one says: LOGIN OK USER MESYS

The second one talks about the Authentication and succeeded

I also had the Trace set to ALL for com.sap.me and suprizingly nothing gets generated to the defaultTrace_00.trc file.

In looking through the forum I noticed another post where there was a similar error message: Link []

Sergiy: Could you see if a ticket was created and what the resolution was?

Thank you,

Mike

[sergiy_katerinich]

Mike,

The root cause was that Ref Des was specified in ASSEMBLE_COMPONENTS request, though the actual definition of the component in the BOM did not have Ref Des. So, it is worth checking the BOM component definition.

Regards,

Sergiy

[Former Member]

Hi Sergiy,

I checked and the BOM is set up correctly.

It has the Ref Des, component and quantity all set.

I have also tried the webservice call on the same SFC with a different Part and different RefDes locations and recieve the same message that the material does not exist.

I have also tried the webservice call on a different SFC using the same BOM getting the same results.

To exhaust all possibilities I even tried the webservice call on a completely different SFC with a completely different BOM and recieved the same message that the material does not exist.

Thank you,

Mike

[sergiy_katerinich]

Mike,

Thanks for your efforts. So, I will wait for a ticket from you.

Regards,

Sergiy

[Former Member]

Hi Sergiy,

I have created a ticket.

Thanks,

Mike

[Former Member]

Hello all,

Just in case others have had this same problem I wanted to follow up with the solution.

It turns out that the problem was code related and this issue has been addressed in SAP ME 5.2 SP06 Patch 12. The CheckOperation was always checking even it the value was set to false.

So if anyone else is having this problem be sure to get the latest version of code.

I hope that this helps!

Thank you,

Mike

[former_member196557]

Mike,

Look at the Material in Material Maintenace, on the Build Tab. What is the value of the 'Data to Collect on Assembly' entry? The AssyDataValue::Attribute must match this base value (i.e., INV in this field is INVENTORY_ID in request, INV_SFC is INVENTORY_ID_SFC in the request). The request values are for the AssyDataTypes are defined in Data Type Maintenance.

- Steve

[Former Member]

Hello,

Yes I already checked that as well.

Within the Material Maintenance for this material the "Data to Collect on Assembly" is set to the Data Type of "INV". When looked up in Data Type Maintenance matches up with the Data Field INVENTORY_ID marked as required and browse.

The really weird part is I can even add this same component within the As-Built Configuration for this SFC. Shows that the component was added by me.

I can also add this same part going through the "manufacturing-xml" page via the "Production XML Client":

<PRODUCTION_REQUEST>
  <ASSEMBLE_COMPONENTS>
    <USER>XML_USER</USER>
    <SITE>1000</SITE>
    <PARENT_SFC>MV220170</PARENT_SFC>
    <OPERATION>PLACEMENT</OPERATION>
    <RESOURCE>CXA_LINE1</RESOURCE>
    <CHECK_OPER>false</CHECK_OPER>
    <EVENT>baseFinished:AssemblyPoint</EVENT>
    <IDENTIFIER_LIST>
      <IDENTIFIER_OBJECT>
        <IDENTIFIER>0000044E4110</IDENTIFIER>
        <REVISION>A</REVISION>
        <QTY>1</QTY>
        <REF_DES>C1</REF_DES>
        <ASSY_DATA_VALUES>
          <ASSY_DATA>
            <DATA_FIELD>INVENTORY_ID</DATA_FIELD>
            <DATA_ATTR>0000044E4110A00167098</DATA_ATTR>
          </ASSY_DATA>
        </ASSY_DATA_VALUES>
      </IDENTIFIER_OBJECT>
    </IDENTIFIER_LIST>
  </ASSEMBLE_COMPONENTS>
</PRODUCTION_REQUEST>

Shows that the component was added by XML_USER.

Any other thoughts?

Thank you,

Mike

[sergiy_katerinich]

Mike,

Please try to remove revision of operation from WS.

Regards,

Sergiy

[Former Member]

Hello Sergiy,

I removed the Revision from the Operation and it still produced the same error message.

Mike