on 01-04-2013 2:29 PM
Hi,
I am trying to adapt the xslt ProductionOrderRequest (endpoint: ErpProductionOrderService) to allow automatically release of SFC with following parameters
<mein:ShopOrderReleaseInfo>
<me:Starting></me:Starting>
<me:Release>5</me:Release>
</mein:ShopOrderReleaseInfo>
The call is successfull but the SFCs are not released. any idea?
thanks
Hi,
I've just tried in 6.0.3.5 with
<me:ShopOrderReleaseInfo>
<me:Release>2</me:Release>
</me:ShopOrderReleaseInfo>
and 2 of 3 SFCs were released (QuantityToBuild = 3).
Regards,
Sergiy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sergiy
The version I have is the same as yours
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:gdt="http://sap.com/xi/SAPGlobal/GDT" xmlns:meint="http://sap.com/xi/MEINT" xmlns:sch="http://sap.com/xi/ME">
<soapenv:Header/>
<soapenv:Body>
<meint:ProductionOrderUpdateRequest_sync>
<meint:ProductionOrder>
<sch:SiteRef>
<sch:Site>1000</sch:Site>
</sch:SiteRef>
<sch:ShopOrderIn>
<sch:SiteRef>
<sch:Site>1000</sch:Site>
</sch:SiteRef>
<sch:ShopOrder>1000403</sch:ShopOrder>
<sch:ShopOrderTypeRef>
<sch:OrderType>PRODUCTION</sch:OrderType>
</sch:ShopOrderTypeRef>
<sch:StatusRef>
<sch:Status>501</sch:Status>
</sch:StatusRef>
<sch:PlannedItemRef>
<sch:Item>800_103</sch:Item>
<sch:Revision>#</sch:Revision>
</sch:PlannedItemRef>
<sch:Priority>500</sch:Priority>
<sch:PlannedStartDate>2013-01-04T24:00:00</sch:PlannedStartDate>
<sch:PlannedCompleteDate>2013-01-04T24:00:00</sch:PlannedCompleteDate>
<sch:QuantityToBuild>5</sch:QuantityToBuild>
<sch:QuantityOrdered>5</sch:QuantityOrdered>
<sch:PlannedBOMRef>
<sch:Bom>800_103-1-1</sch:Bom>
<sch:Revision>#</sch:Revision>
</sch:PlannedBOMRef>
<sch:PlannedRouterRef>
<sch:Router>50000000-1</sch:Router>
<sch:RouterType>U</sch:RouterType>
<sch:Revision>#</sch:Revision>
</sch:PlannedRouterRef>
<sch:ErpOrder>true</sch:ErpOrder>
<sch:AllowInqueueSfcOnSoClose>true</sch:AllowInqueueSfcOnSoClose>
<sch:ErpUnitOfMeasure>PCE</sch:ErpUnitOfMeasure>
<sch:CustomFieldList>
<sch:CustomField>
<sch:Attribute>AUTO_MODUS</sch:Attribute>
<sch:Value>1</sch:Value>
<sch:Description>Auto or manual mode</sch:Description>
</sch:CustomField>
</sch:CustomFieldList>
</sch:ShopOrderIn>
<sch:BOMIn>
<sch:SiteRef>
<sch:Site>1000</sch:Site>
</sch:SiteRef>
<sch:Bom>800_103-1-1</sch:Bom>
<sch:StatusRef>
<sch:Status>201</sch:Status>
</sch:StatusRef>
<sch:Description>00000003</sch:Description>
<sch:ErpBom>00000003</sch:ErpBom>
<sch:EffectivityControl>R</sch:EffectivityControl>
<sch:CurrentRevision>true</sch:CurrentRevision>
<sch:BomComponentList>
<sch:BomComponent>
<sch:Component>
<sch:Item>300_100</sch:Item>
<sch:Revision>#</sch:Revision>
</sch:Component>
<sch:Sequence>1</sch:Sequence>
<sch:BomComponentType>N</sch:BomComponentType>
<sch:Enabled>true</sch:Enabled>
<sch:Quantity>1</sch:Quantity>
<sch:AssembleAsRequired>false</sch:AssembleAsRequired>
<sch:TestPart>false</sch:TestPart>
<sch:CreateTrackableSFC>I</sch:CreateTrackableSFC>
<sch:BomOperation>
<sch:OperationRef>
<sch:Operation>50000000-1-0-0010</sch:Operation>
<sch:Revision>#</sch:Revision>
</sch:OperationRef>
<sch:Quantity>1</sch:Quantity>
</sch:BomOperation>
</sch:BomComponent>
<sch:BomComponent>
<sch:Component>
<sch:Item>200_101</sch:Item>
<sch:Revision>#</sch:Revision>
</sch:Component>
<sch:Sequence>2</sch:Sequence>
<sch:BomComponentType>N</sch:BomComponentType>
<sch:Enabled>true</sch:Enabled>
<sch:Quantity>1</sch:Quantity>
<sch:AssembleAsRequired>false</sch:AssembleAsRequired>
<sch:TestPart>false</sch:TestPart>
<sch:CreateTrackableSFC>I</sch:CreateTrackableSFC>
<sch:BomOperation>
<sch:OperationRef>
<sch:Operation>50000000-1-0-0010</sch:Operation>
<sch:Revision>#</sch:Revision>
</sch:OperationRef>
<sch:Quantity>1</sch:Quantity>
</sch:BomOperation>
</sch:BomComponent>
<sch:BomComponent>
<sch:Component>
<sch:Item>200_100</sch:Item>
<sch:Revision>#</sch:Revision>
</sch:Component>
<sch:Sequence>3</sch:Sequence>
<sch:BomComponentType>N</sch:BomComponentType>
<sch:Enabled>true</sch:Enabled>
<sch:Quantity>1</sch:Quantity>
<sch:AssembleAsRequired>false</sch:AssembleAsRequired>
<sch:TestPart>false</sch:TestPart>
<sch:CreateTrackableSFC>I</sch:CreateTrackableSFC>
<sch:BomOperation>
<sch:OperationRef>
<sch:Operation>50000000-1-0-0010</sch:Operation>
<sch:Revision>#</sch:Revision>
</sch:OperationRef>
<sch:Quantity>1</sch:Quantity>
</sch:BomOperation>
</sch:BomComponent>
</sch:BomComponentList>
<sch:CustomFieldList>
<sch:CustomField>
<sch:Attribute>ERP_MATERIAL</sch:Attribute>
<sch:Value>800_103</sch:Value>
</sch:CustomField>
</sch:CustomFieldList>
</sch:BOMIn>
<meint:Routing>
<sch:RouterIn>
<sch:SiteRef>
<sch:Site>1000</sch:Site>
</sch:SiteRef>
<sch:Router>50000000-1</sch:Router>
<sch:Revision>A</sch:Revision>
<sch:RouterType>U</sch:RouterType>
<sch:Description>800_103</sch:Description>
<sch:StatusRef>
<sch:Status>201</sch:Status>
</sch:StatusRef>
<sch:EffectivityControl>R</sch:EffectivityControl>
<sch:CurrentRevision>true</sch:CurrentRevision>
<sch:EntryRouterStepRef>
<sch:RouterRef>
<sch:Router>50000000-1</sch:Router>
<sch:RouterType>U</sch:RouterType>
</sch:RouterRef>
<sch:StepId>10</sch:StepId>
</sch:EntryRouterStepRef>
<sch:RouterStepList>
<sch:RouterStep>
<sch:ReportingStep>0010</sch:ReportingStep>
<sch:Rework>false</sch:Rework>
<sch:RouterStepRef>
<sch:StepId>10</sch:StepId>
</sch:RouterStepRef>
<sch:Sequence>1</sch:Sequence>
<sch:RouterOperationList>
<sch:RouterOperation>
<sch:OperationRef>
<sch:Operation>50000000-1-0-0010</sch:Operation>
<sch:Revision>#</sch:Revision>
</sch:OperationRef>
<sch:CustomFieldList>
<sch:CustomField>
<sch:Attribute>SEQUENCE</sch:Attribute>
<sch:Value>0</sch:Value>
</sch:CustomField>
<sch:CustomField>
<sch:Attribute>CONTROL_KEY</sch:Attribute>
<sch:Value>PP01</sch:Value>
</sch:CustomField>
</sch:CustomFieldList>
</sch:RouterOperation>
</sch:RouterOperationList>
<sch:RouterComp>
<sch:RouterOperation>
<sch:RouterStepRef>
<sch:StepId>10</sch:StepId>
</sch:RouterStepRef>
</sch:RouterOperation>
</sch:RouterComp>
<sch:StepId>10</sch:StepId>
<sch:RouterNextStepList>
<sch:RouterNextStep>
<sch:NextStepRef>
<sch:StepId>20</sch:StepId>
</sch:NextStepRef>
</sch:RouterNextStep>
</sch:RouterNextStepList>
</sch:RouterStep>
<sch:RouterStep>
<sch:ReportingStep>0020</sch:ReportingStep>
<sch:Rework>false</sch:Rework>
<sch:RouterStepRef>
<sch:StepId>20</sch:StepId>
</sch:RouterStepRef>
<sch:Sequence>2</sch:Sequence>
<sch:RouterOperationList>
<sch:RouterOperation>
<sch:OperationRef>
<sch:Operation>50000000-1-0-0020</sch:Operation>
<sch:Revision>#</sch:Revision>
</sch:OperationRef>
<sch:CustomFieldList>
<sch:CustomField>
<sch:Attribute>SEQUENCE</sch:Attribute>
<sch:Value>0</sch:Value>
</sch:CustomField>
<sch:CustomField>
<sch:Attribute>CONTROL_KEY</sch:Attribute>
<sch:Value>PP01</sch:Value>
</sch:CustomField>
</sch:CustomFieldList>
</sch:RouterOperation>
</sch:RouterOperationList>
<sch:RouterComp>
<sch:RouterOperation>
<sch:RouterStepRef>
<sch:StepId>20</sch:StepId>
</sch:RouterStepRef>
</sch:RouterOperation>
</sch:RouterComp>
<sch:StepId>20</sch:StepId>
<sch:RouterNextStepList>
<sch:RouterNextStep>
<sch:NextStepRef>
<sch:StepId>30</sch:StepId>
</sch:NextStepRef>
</sch:RouterNextStep>
</sch:RouterNextStepList>
</sch:RouterStep>
<sch:RouterStep>
<sch:ReportingStep>0030</sch:ReportingStep>
<sch:Rework>false</sch:Rework>
<sch:RouterStepRef>
<sch:StepId>30</sch:StepId>
</sch:RouterStepRef>
<sch:Sequence>3</sch:Sequence>
<sch:RouterOperationList>
<sch:RouterOperation>
<sch:OperationRef>
<sch:Operation>50000000-1-0-0030</sch:Operation>
<sch:Revision>#</sch:Revision>
</sch:OperationRef>
<sch:CustomFieldList>
<sch:CustomField>
<sch:Attribute>SEQUENCE</sch:Attribute>
<sch:Value>0</sch:Value>
</sch:CustomField>
<sch:CustomField>
<sch:Attribute>CONTROL_KEY</sch:Attribute>
<sch:Value>PP03</sch:Value>
</sch:CustomField>
<sch:CustomField>
<sch:Attribute>IS_LAST_REPORTING_STEP</sch:Attribute>
<sch:Value>true</sch:Value>
</sch:CustomField>
</sch:CustomFieldList>
</sch:RouterOperation>
</sch:RouterOperationList>
<sch:RouterComp>
<sch:RouterOperation>
<sch:RouterStepRef>
<sch:StepId>30</sch:StepId>
</sch:RouterStepRef>
</sch:RouterOperation>
</sch:RouterComp>
<sch:StepId>30</sch:StepId>
<sch:RouterNextStepList/>
</sch:RouterStep>
</sch:RouterStepList>
<sch:CustomFieldList>
<sch:CustomField>
<sch:Attribute>ERP_MATERIAL</sch:Attribute>
<sch:Value>800_103</sch:Value>
</sch:CustomField>
</sch:CustomFieldList>
</sch:RouterIn>
<sch:OperationListIn>
<sch:Operation>
<sch:Operation>50000000-1-0-0010</sch:Operation>
<sch:Revision>A</sch:Revision>
<sch:Description>0010</sch:Description>
<sch:CurrentRevision>true</sch:CurrentRevision>
<sch:MaxLoop>1</sch:MaxLoop>
<sch:ResourceTypeRef>
<sch:ResourceType>DEFAULT</sch:ResourceType>
</sch:ResourceTypeRef>
<sch:StatusRef>
<sch:Status>201</sch:Status>
</sch:StatusRef>
<sch:Type>N</sch:Type>
</sch:Operation>
<sch:Operation>
<sch:Operation>50000000-1-0-0020</sch:Operation>
<sch:Revision>A</sch:Revision>
<sch:Description>0020</sch:Description>
<sch:CurrentRevision>true</sch:CurrentRevision>
<sch:MaxLoop>1</sch:MaxLoop>
<sch:ResourceTypeRef>
<sch:ResourceType>DEFAULT</sch:ResourceType>
</sch:ResourceTypeRef>
<sch:StatusRef>
<sch:Status>201</sch:Status>
</sch:StatusRef>
<sch:Type>N</sch:Type>
</sch:Operation>
<sch:Operation>
<sch:Operation>50000000-1-0-0030</sch:Operation>
<sch:Revision>A</sch:Revision>
<sch:Description>0030</sch:Description>
<sch:CurrentRevision>true</sch:CurrentRevision>
<sch:MaxLoop>1</sch:MaxLoop>
<sch:ResourceTypeRef>
<sch:ResourceType>DEFAULT</sch:ResourceType>
</sch:ResourceTypeRef>
<sch:StatusRef>
<sch:Status>201</sch:Status>
</sch:StatusRef>
<sch:Type>N</sch:Type>
</sch:Operation>
</sch:OperationListIn>
</meint:Routing>
<meint:ShopOrderReleaseInfo>
<sch:Release languageCode="?">5</sch:Release>
</meint:ShopOrderReleaseInfo>
</meint:ProductionOrder>
</meint:ProductionOrderUpdateRequest_sync>
</soapenv:Body>
</soapenv:Envelope>
I have changed namespace ref at ShopOrderReleaseInfo from sch to meint because sch throws an error. Anyhow, it does not work in both cases. Any idea?
thanks
Please try mine one:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:mein="http://sap.com/xi/MEINT" xmlns:me="http://sap.com/xi/ME" xmlns:gdt="http://sap.com/xi/SAPGlobal/GDT">
<soapenv:Header />
<soapenv:Body>
<mein:ProductionOrderUpdateRequest_sync>
<mein:ProductionOrder>
<me:SiteRef>
<me:Site>SK</me:Site>
</me:SiteRef>
<me:ShopOrderIn>
<me:ShopOrder>SO-0003080973-3</me:ShopOrder>
<me:SiteRef>
<me:Site>SK</me:Site>
</me:SiteRef>
<me:StatusRef>
<me:Status>501</me:Status>
</me:StatusRef>
<me:Priority>500</me:Priority>
<me:PlannedItemRef>
<me:Item>CH001</me:Item>
<me:Revision>A</me:Revision>
</me:PlannedItemRef>
<me:QuantityToBuild>3</me:QuantityToBuild>
</me:ShopOrderIn>
<me:ShopOrderReleaseInfo>
<me:Release>2</me:Release>
</me:ShopOrderReleaseInfo>
</mein:ProductionOrder>
</mein:ProductionOrderUpdateRequest_sync>
</soapenv:Body>
Before sending it, just create manually a material CH001 rev A with a routing assigned in Material Mainteance.
Regards,
Sergiy
Hi Sergiy
I have changed site, shop order and Item to reflects my system. Again I need to change the ShopOrderReleaseInfor from me to mein. If not it has failure. Again it also does not work with the changed namespace ref. It returns no error but no SFCs released ...
The Webservice ME component me~ws has following version 6.0.3.5.46
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:mein="http://sap.com/xi/MEINT" xmlns:me="http://sap.com/xi/ME" xmlns:gdt="http://sap.com/xi/SAPGlobal/GDT">
<soapenv:Header />
<soapenv:Body>
<mein:ProductionOrderUpdateRequest_sync>
<mein:ProductionOrder>
<me:SiteRef>
<me:Site>1000</me:Site>
</me:SiteRef>
<me:ShopOrderIn>
<me:ShopOrder>1000407</me:ShopOrder>
<me:SiteRef>
<me:Site>1000</me:Site>
</me:SiteRef>
<me:StatusRef>
<me:Status>501</me:Status>
</me:StatusRef>
<me:Priority>500</me:Priority>
<me:PlannedItemRef>
<me:Item>800_103</me:Item>
<me:Revision>A</me:Revision>
</me:PlannedItemRef>
<me:QuantityToBuild>3</me:QuantityToBuild>
</me:ShopOrderIn>
<mein:ShopOrderReleaseInfo>
<me:Release>2</me:Release>
</mein:ShopOrderReleaseInfo>
</mein:ProductionOrder>
</mein:ProductionOrderUpdateRequest_sync>
</soapenv:Body>
Return
<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:ProductionOrderUpdateConfirmation_sync xmlns="http://sap.com/xi/SAPGlobal/GDT" xmlns:ns3="http://sap.com/xi/ME" xmlns:ns2="http://sap.com/xi/MEINT">
<ns2:ProductionServiceResponse>
<ns2:ResponseObject>
<ns3:SiteRef/>
<ns3:ShopOrderRef>
<ns3:ShopOrder>1000407</ns3:ShopOrder>
<ns3:SiteRef>
<ns3:Site>1000</ns3:Site>
</ns3:SiteRef>
</ns3:ShopOrderRef>
</ns2:ResponseObject>
</ns2:ProductionServiceResponse>
</ns2:ProductionOrderUpdateConfirmation_sync>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Yes, your request creates the SO but does not release the SFCs. So, it looks as if the namespace should remain as is to make the system release SFCs.
What's the error you have with the default namespace?
Can you create a project in soapUI to generate the default request and check the namespace there?
Can you try my request from soapUI then?
Are you using a standard build of ME or with any customizations?
The default namespace is me's namespace. If I use this namespace I get the following error.
I have customization in the ME, but they are nothing related to MEINT or any MEINT related Webservice.
<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>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Client</faultcode>
<faultstring>ASJ.ejb.005044 (Failed in component: sap.com/me~ear) Exception raised from invocation of public com.sap.me.frame.Data com.sap.me.production.ProductionOrderSOBean.update(com.sap.me.frame.Data,java.util.Map) throws com.sap.me.frame.BasicBOBeanException method on bean instance com.sap.me.production.ProductionOrderSOBean@30bf79b9 for bean sap.com/me~ear*xml|me.production.ejb-6.0.3.5.jar*xml|ProductionOrderSO in application sap.com/me~ear.; nested exception is: javax.ejb.TransactionRolledbackLocalException: ASJ.ejb.005044 (Failed in component: sap.com/me~ear) Exception raised from invocation of public void com.sap.me.demand.ShopOrderBOBean.DXImportUpdate(com.sap.me.frame.Data,com.sap.me.frame.Data,boolean) throws com.sap.me.frame.BasicBOBeanException method on bean instance com.sap.me.demand.ShopOrderBOBean@6af1ec09 for bean sap.com/me~ear*xml|me.demand.ejb-6.0.3.5.jar*xml|ShopOrderBO in application sap.com/me~ear.; nested exception is: javax.ejb.TransactionRolledbackLocalException: ASJ.ejb.005044 (Failed in component: sap.com/me~ear) Exception raised from invocation of public com.sap.me.frame.Data com.sap.me.production.HookBOBean.execute(com.sap.me.frame.Data) throws com.sap.me.frame.BasicBOBeanException method on bean instance com.sap.me.production.HookBOBean@7c5fa3a9 for bean sap.com/me~ear*xml|me.production.ejb-6.0.3.5.jar*xml|HookBO in application sap.com/me~ear.; nested exception is: javax.ejb.TransactionRolledbackLocalException: ASJ.ejb.005044 (Failed in component: sap.com/me~ear) Exception raised from invocation of public com.sap.me.frame.Data com.sap.me.activity.ActivityBOBean.execute(com.sap.me.frame.BOHandle,com.sap.me.frame.Data,java.lang.String) throws com.sap.me.frame.BasicBOBeanException method on bean instance com.sap.me.activity.ActivityBOBean@5bcd314c for bean sap.com/me~ear*xml|me.activity.ejb-6.0.3.5.jar*xml|ActivityBO in application sap.com/me~ear.; nested exception is: This exception is wrapper of javax.xml.ws.soap.SOAPFaultException. com.sap.engine.services.webservices.espbase.client.bindings.exceptions.SOAPFaultException: Angegebene Transaktionsdatei kann nicht gefunden werden; nested exception is: javax.ejb.EJBException: ASJ.ejb.005044 (Failed in component: sap.com/me~ear) Exception raised from invocation of public com.sap.me.frame.Data com.sap.me.activity.ActivityBOBean.execute(com.sap.me.frame.BOHandle,com.sap.me.frame.Data,java.lang.String) throws com.sap.me.frame.BasicBOBeanException method on bean instance com.sap.me.activity.ActivityBOBean@5bcd314c for bean sap.com/me~ear*xml|me.activity.ejb-6.0.3.5.jar*xml|ActivityBO in application sap.com/me~ear.; nested exception is: This exception is wrapper of javax.xml.ws.soap.SOAPFaultException. com.sap.engine.services.webservices.espbase.client.bindings.exceptions.SOAPFaultException: Angegebene Transaktionsdatei kann nicht gefunden werden; nested exception is: javax.ejb.EJBTransactionRolledbackException: ASJ.ejb.005044 (Failed in component: sap.com/me~ear) Exception raised from invocation of public com.sap.me.frame.Data com.sap.me.activity.ActivityBOBean.execute(com.sap.me.frame.BOHandle,com.sap.me.frame.Data,java.lang.String) throws com.sap.me.frame.BasicBOBeanException method on bean instance com.sap.me.activity.ActivityBOBean@5bcd314c for bean sap.com/me~ear*xml|me.activity.ejb-6.0.3.5.jar*xml|ActivityBO in application sap.com/me~ear.; nested exception is: This exception is wrapper of javax.xml.ws.soap.SOAPFaultException. com.sap.engine.services.webservices.espbase.client.bindings.exceptions.SOAPFaultException: Angegebene Transaktionsdatei kann nicht gefunden werden; nested exception is: javax.ejb.EJBException: ASJ.ejb.005044 (Failed in component: sap.com/me~ear) Exception raised from invocation of public com.sap.me.frame.Data
........... very long error
Hi Sergiy,
I am trying to do the same thing, release the order using ErpProductionOrderService WS and through UpdateProductionOrder operation. I have used SOAPUI for testing. In response message I did not get any error by Shop Order is not released. My shop order is already in ME but no SFC is created. Could you please provide your suggestion. I am using ME 6.1.
Here is my Request Message:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:mein="http://sap.com/xi/MEINT" xmlns:gdt="http://sap.com/xi/SAPGlobal/GDT" xmlns:me="http://sap.com/xi/ME">
<soapenv:Header/>
<soapenv:Body>
<mein:ProductionOrderUpdateRequest_sync>
<mein:ProductionOrder>
<me:SiteRef>
<me:Site>PPME</me:Site>
</me:SiteRef>
<me:ShopOrderIn>
<!--You may enter the following 40 items in any order-->
<me:ShopOrder>1007258</me:ShopOrder>
<me:SiteRef>
<me:Site>PPME</me:Site>
</me:SiteRef>
<me:StatusRef>
<!--You may enter the following 2 items in any order-->
<me:Status>501</me:Status>
<!--Optional:-->
</me:StatusRef>
<me:Priority>500</me:Priority>
<!--Optional:-->
<me:PlannedItemRef>
<!--You may enter the following 3 items in any order-->
<me:Item>1181</me:Item>
<!--Optional:-->
<me:Revision>#</me:Revision>
<!--Optional:-->
</me:PlannedItemRef>
<me:QuantityToBuild>2</me:QuantityToBuild>
</me:ShopOrderIn>
<me:ShopOrderReleaseInfo>
<me:Starting>0</me:Starting>
<me:Release>2</me:Release>
</me:ShopOrderReleaseInfo>
</mein:ProductionOrder>
</mein:ProductionOrderUpdateRequest_sync>
</soapenv:Body>
</soapenv:Envelope>
Response Message:
<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:ProductionOrderUpdateConfirmation_sync xmlns="http://sap.com/xi/SAPGlobal/GDT" xmlns:ns3="http://sap.com/xi/ME" xmlns:ns2="http://sap.com/xi/MEINT">
<ns2:ProductionServiceResponse>
<ns2:ResponseObject>
<ns3:SiteRef/>
<ns3:ShopOrderRef>
<ns3:ShopOrder>1007258</ns3:ShopOrder>
<ns3:SiteRef>
<ns3:Site>PPME</ns3:Site>
</ns3:SiteRef>
</ns3:ShopOrderRef>
</ns2:ResponseObject>
</ns2:ProductionServiceResponse>
</ns2:ProductionOrderUpdateConfirmation_sync>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Thanks in Advance
Chandan
Hi Chandan,
Here is schema element for this block:
- <xs:complexType name="ShopOrderReleaseInfo">
<xs:sequence>
<xs:element name="Starting" type="ns1:INTEGERQuantity" />
<xs:element name="Release" type="ns1:Text" />
</xs:sequence>
</xs:complexType>.
I'd recommend using:
<me:ShopOrderReleaseInfo>
<me:Release>all</me:Release>
</me:ShopOrderReleaseInfo>
Br,
Konstantin
Hi Konstantin,
As per your suggestion I have used the below structure but here also same issue. I did not get any error in response message but Shop Order is not released. Please provide your suggestion. I have even tried with different order and plant.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:mein="http://sap.com/xi/MEINT" xmlns:gdt="http://sap.com/xi/SAPGlobal/GDT" xmlns:me="http://sap.com/xi/ME">
<soapenv:Header/>
<soapenv:Body>
<mein:ProductionOrderUpdateRequest_sync>
<mein:ProductionOrder>
<me:SiteRef>
<me:Site>9999</me:Site>
</me:SiteRef>
<me:ShopOrderIn>
<!--You may enter the following 40 items in any order-->
<me:ShopOrder>1006928</me:ShopOrder>
<me:SiteRef>
<me:Site>9999</me:Site>
</me:SiteRef>
<me:StatusRef>
<!--You may enter the following 2 items in any order-->
<me:Status>501</me:Status>
<!--Optional:-->
</me:StatusRef>
<me:Priority>500</me:Priority>
<!--Optional:-->
<me:PlannedItemRef>
<!--You may enter the following 3 items in any order-->
<me:Item>1173</me:Item>
<!--Optional:-->
<me:Revision>#</me:Revision>
<!--Optional:-->
</me:PlannedItemRef>
<me:QuantityToBuild>3</me:QuantityToBuild>
</me:ShopOrderIn>
<me:ShopOrderReleaseInfo>
<me:Release>all</me:Release>
</me:ShopOrderReleaseInfo>
</mein:ProductionOrder>
</mein:ProductionOrderUpdateRequest_sync>
</soapenv:Body>
</soapenv:Envelope>
Response message
<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:ProductionOrderUpdateConfirmation_sync xmlns="http://sap.com/xi/SAPGlobal/GDT" xmlns:ns3="http://sap.com/xi/ME" xmlns:ns2="http://sap.com/xi/MEINT">
<ns2:ProductionServiceResponse>
<ns2:ResponseObject>
<ns3:SiteRef/>
<ns3:ShopOrderRef>
<ns3:ShopOrder>1006928</ns3:ShopOrder>
<ns3:SiteRef>
<ns3:Site>9999</ns3:Site>
</ns3:SiteRef>
</ns3:ShopOrderRef>
</ns2:ResponseObject>
</ns2:ProductionServiceResponse>
</ns2:ProductionOrderUpdateConfirmation_sync>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Thanks in Advance
Chandan
User | Count |
---|---|
85 | |
7 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.