QM _Inspection Lot Creation with Move ment type-542

Dear All,
The Business Scenario is when ever goods received from Sub contracting vendor with out any processing by 542 movement type the system should create the Inspection lot automatically.
How can achive this function?
Your inputs are valuable.
Regards,
Manis

IMG - Quality management - Quality Inspection - Inspection lot creation - Inspection for goods movements..
You have to add new entry for movement type 542..
complete help is available there..
Also you have to activate the related inspection type in QM view in material master.
You can try this in development server. (I am also not an expert in this area).
Regards,
Amol

Similar Messages

Dynamic destination bin with Mov. Type 311-312 and Storage type 001?

Hello WM experts,
I'm tryng to determine dynamic destination bin with mov. type 311, when trasfering handling units from IM to WM storages (VLMOVE). First 311 transfer to St. type 921, and then 312 transfer from 921 to St. type 001. I don´t want to use a Fixed destination storage bin in St.type 001, I'd like to configure this like movement type 601, that create a dynamic destination bin using outbound delivery. Can be this possible?
Another question I have: Is possible to crearte individivual items with Source target quantity in alternate unit equivalent to 1 unit, in LT03. For example, the item 10 of my outbound delivery says 3 ST of XYZ material. But I want to crear 3 items with Source target qty. 1 ST. Is this possible with customizing or using an enhancement? ...
Why I want to find a way to do any of these things above, because when I have indivial intes in the TO, I can confirm them in RF (LM61) just pressing one button, I don't need to declare any difference, and makes my picking process faster.
Best regads, and thanks for you time and help.
Favio Del Castillo.

Hi Mohit ,
please check below link , you need to perform steps as given
http://help.sap.com/saphelp_470/helpdata/en/4d/2b90b043ad11d189410000e829fbbd/content.htm
also see the sales order subcontracting using the business addon
http://help.sap.com/erp2005_ehp_04/helpdata/en/c7/2587b8dad94c52854ccd28015dceb0/frameset.htm

Follow-on RFx creation with custom transaciton type from shopping cart

Hi,
we have the requirement as below:
1) Custom field is added in Shopping cart as drop down to select the custom RFx type
2) RFx should be created automatically as follow-on document with the Rfx type selected in shopping cart using the dropdown.
Can anyone help me in this regard?
Thanks,
Sivagami R

Hi,Sivagami Rathinam ,
Custom field is added in Shopping cart as drop down to select the custom RFx type.
To achieve this function with Carry out Sourcing.
Sarah

Inspection lot creation for Movement type 531

Dear experts,
following is the procedure
1) Material enter against purchase order SFG
2) Quality checks that and send to unrestricted (its an sampling inspection)
3) Issue this material against production order
4) order is confirmed and GR is done for FG
5) FG material goes to quaity for inspection
6) At the time of inspection of FG it is found that FG is rejected because of vendor material
so we keep that stock in blocked stock. now we create an salvage order by CO07 and issue FG and received SFG vendor material by 531 movement
now my prob is i want to record the defect against vendor material because of which it is rejected and my clint wants the report on reson basis
regards
Sachin

go to OMBS... Here you need to do two things..
1. control reason..here u can mention reason for movement for 531 is requied or optional etc..
2. reason for movement..here u need to maintain the reasons as per ur wish..
like 101---damaged
107--- scratched
etc..
If all these are set, then only you can enter the reasons in the MB11 screen and the same can be viewed in MB51 by adding the reason in the layout...
karthick
Edited by: karthick PP on Jun 4, 2009 5:21 AM

Third Party Sale- Move ment type

Hii,
In third party sale, when e do MIGO what is the movement type we should take. (in case of individual purchase order scenario we take Mov type as 101, where actually we are taking goods into our stock and then delivering it to our customer) but in Third party vendor directly supplies to customer. But he sends an acknowledgement to the company and we do MIGO & MIRO and then directly raise an invoice with ref to order but quantity as per delivery ( billing rev -F). So my doubt is wat movement type we should be taking for thirdparty sale when we do MIGO. (this is only for reference, actually there is inward movement of goods into our stock as the vendor supplies it directly to customer).
Thanks

Dear Venkat Rao,
A small search on SDN SD forum will help you to answer your query.
http://help.sap.com/saphelp_46c/helpdata/en/e6/4a78e39e0311d189b70000e829fbbd/content.htm
THIRD PARTY SALES
http://www.sap-img.com/sap-sd/process-flow-for-3rd-party-sales.htm
http://www.sap.com/services/pdf/BWP_SAP_Best_Practices_for_Wholesale_Distribution.pdf
3rd party biling
http://www50.sap.com/businessmaps/65045A20075E4CFD89DB030BC1C556AD.htm
http://www.saptechies.com/process-flow-for-3rd-party-sales/
Hope this helps you.
Do award points if you found them useful.
Regards,
Rakesh

Lot creation with physical sample

Hi all,
Inspection lots with physical sample not getting created.Error message "Origin 15 not defined" pops up constantly with all materials.The settings in SPRO are maintained:
LO:15
Origin:15
Variant :01
Inspection type:15
Settings in material master: Activated inspection type '15'
No lots with physical samples exist for the material.
Regards
Binesh

I just want to check that you are using the inspection type 15 correctly. That is used to create inspection lots (usually manually), for already exisitng physical samples in your inventory. I.e. usuaully this is used to recheck an old sample after a customer complaint or to check shelf life or stability sample.
So the the physical samples have to be created first. Do you have physical samples created?
You can manually create them but they are usually automatically created via the 01 and 04 lots that use a physical sample-drawing procedure and approporate inspection plans.
FF

Automatic move ment types

hi to all
plz explain my doubt
Which scenario , Automatic movements 641,643, 645, 647 will come?
Plz explain each case ?
what are the procedures for one step and two step scenarios?
thanks and regards
ravi

Dear Ravi,
These movements are related to Stock Transfers through SD route. When you do PGI ( Post Goods Issue), in the back ground these movement types trigger based on one step & two step.
One step is: the stock is removed from issued planr & get updated in in receiving plant as soon as you do the PGI.
Two Step: The stock is removed from issue plant sfter PGI and it will show in reports as "Stock in Transit" . Then when the material is received at receiving plant then that stock has to be taken with 101 mvt. Then only that stock stock get updated in receivng plant.
Two-step procedure to to track stock when it in transport.
Hope you it solves your query, if any more clarification please ask.
If this solves your query, please close the issue.
With Regards,
Krishna reddy

Manual WSDL creation with Complex data types

I'm trying to manually generate a WSDL, for a bpel workflow, so the wsdl constructs do not come from a Java class file, or any of the other normal ways you might generate a WSDL.
I have successfully created a Definition object from the WSDLFactory, with the code shown below, that appears to be correct, based on reverse engineering of a WS compliant WSDL. The reversed engineered WSDL was created by IONA Artix.
When I use file WSDLFactoryImpl.WSDLWriterImpl.writeWSDL() to write the WSDL file I get the wsdl:types and wsdl:service definition objectsin the file, but not the wsdl:message, wsdl:portType or wsdl:binding objects.
The reverse engineered WSDL file has been imported into objects via WSDLReaderImpl, and the resulting Definition object appears correct (based on all system.outs). This definition can be successfully written to file via the same WSDLFactoryImpl.WSDLWriterImpl.writeWSDL(). which results in a correct WSDL file.
I'm hoping someone can spot my problem.
Chris Yoerg
WSDLFactory.java************************************************************************************************
package com.dralasoft.bpel.util;
import java.util.*;
import java.io.*;
import javax.xml.namespace.QName;
import javax.xml.parsers.*;
import javax.wsdl.WSDLException;
import javax.wsdl.extensions.UnknownExtensibilityElement;
import org.w3c.dom.*;
import com.ibm.wsdl.*;
import com.ibm.wsdl.factory.WSDLFactoryImpl;
import com.ibm.wsdl.extensions.soap.*;
/** This class generates a wsdl from scratch
* the way the namespaces have been left seem to be correct in that the individual
* porttype, binding and service objects pick up the message parts as seen in the
* individual system.outs and in the system.out of the definition
* if you use the tns prefix iteration as seen in the comment out "trial" code
* you get an error that the tns namespace does not exist in the definition
* even though it is definitely there
* the non namespace "trial" code also behaves the same way as this iteration,
* aka the stuff shows in the definition outputs, but never ends up outputed to
* file */
//import com.dralasoft.bpel.BPELWorkflow;
public class WSDLFactory {
public WSDLFactory() {
public void makeWorkflowWSDL(){
WSDLFactoryImpl factory = null;
Constants constants = new Constants();
SOAPConstants soapconstants = new SOAPConstants();
try {
factory = (WSDLFactoryImpl) WSDLFactoryImpl.newInstance();
catch (WSDLException we) {
System.out.println("wsdl excepiotn " + we.getMessage());
// get a new definition from the factory
DefinitionImpl definition = (DefinitionImpl) factory.newDefinition();
// add target namespace and additional namespaces that might be there
definition.setTargetNamespace("http://www.yoerg.net");
definition.addNamespace("tns", "http://www.yoerg.net");
definition.addNamespace("soap", "http://schemas.xmlsoap.org/wsdl/soap/");
definition.addNamespace("xsd", "http://www.w3.org/2001/XMLSchema");
definition.addNamespace("wsdl", "http://schemas.xmlsoap.org/wsdl/");
// added for generic purposes
definition.addNamespace("xsi", "http://www.w3.org/2001/XMLSchema-instance");
// specify the service name
QName qname = new QName("http://www.yoerg.net",
"PurchaseOrderProcess");
definition.setQName(qname);
// create types **********************************************************
TypesImpl types = (TypesImpl) definition.createTypes();
// generate a schema in DOM to set into the types object
javax.xml.parsers.DocumentBuilderFactory domfactory =
javax.xml.parsers.DocumentBuilderFactory.newInstance();
javax.xml.parsers.DocumentBuilder builder = null;
try {
builder = domfactory.newDocumentBuilder();
catch (javax.xml.parsers.ParserConfigurationException pce) {
System.out.println("parser config exception " + pce.getMessage());
DOMImplementation dImpl = builder.getDOMImplementation();
// namespace for the schema
String namespaceURI = "http://www.w3.org/2001/XMLSchema";
Document doc = dImpl.createDocument(namespaceURI, "schema", null);
Element schema = doc.getDocumentElement();
//schema.setPrefix("xsd");
schema.setAttribute("xmlns", "http://www.w3.org/2001/XMLSchema");
schema.setAttribute("targetNamespace", "http://www.yoerg.net");
//set other namespaces on schema
// this doesn't make it into the schema at final save, because there
// are no wsdl elements inside the box
schema.setAttribute("xmlns:wsdl", "http://schemas.xmlsoap.org/wsdl/");
// this is not needed
schema.setAttribute("tns", "http://www.yoerg.net");
Element first = doc.createElement("element");
first.setAttribute("name", "sendPurchaseOrder");
first.setAttribute("type", "tns:sendPORequest");
schema.appendChild(first);
Element fourth = doc.createElement("element");
fourth.setAttribute("name", "sendSchedule");
fourth.setAttribute("type", "tns:sendScheduleRequest");
schema.appendChild(fourth);
Element fifth = doc.createElement("element");
fifth.setAttribute("name", "sendInvoice");
fifth.setAttribute("type", "tns:sendInvoiceRequest");
schema.appendChild(fifth);
// now add correlations
Element corfirst = doc.createElement("element");
corfirst.setAttribute("name", "correlations");
corfirst.setAttribute("type", "tns:correlationset");
schema.appendChild(corfirst);
Element second = doc.createElement("element");
second.setAttribute("name", "portType");
second.setAttribute("type", "xsd:string");
schema.appendChild(second);
Element third = doc.createElement("element");
third.setAttribute("name", "partnerLink");
third.setAttribute("type", "xsd:string");
schema.appendChild(third);
// sequence element thats used over and over
Element sequence = null;
Element sixth = doc.createElement("complexType");
sixth.setAttribute("name", "sendPORequest");
sequence = doc.createElement("sequence");
Element part1 = doc.createElement("element");
part1.setAttribute("name", "customerId");
part1.setAttribute("type", "xsd:long");
sequence.appendChild(part1);
Element part2 = doc.createElement("element");
part2.setAttribute("name", "purchaseOrderNumber");
part2.setAttribute("type", "xsd:long");
sequence.appendChild(part2);
Element part3 = doc.createElement("element");
part3.setAttribute("name", "productId");
part3.setAttribute("type", "xsd:long");
sequence.appendChild(part3);
Element part4 = doc.createElement("element");
part4.setAttribute("name", "quantity");
part4.setAttribute("type", "xsd:int");
sequence.appendChild(part4);
sixth.appendChild(sequence);
schema.appendChild(sixth);
Element seventh = doc.createElement("complexType");
seventh.setAttribute("name", "sendScheduleRequest");
sequence = doc.createElement("sequence");
Element part6 = doc.createElement("element");
part6.setAttribute("name", "shipDate");
part6.setAttribute("type", "xsd:dateTime");
sequence.appendChild(part6);
Element part7 = doc.createElement("element");
part7.setAttribute("name", "customerId");
part7.setAttribute("type", "xsd:long");
sequence.appendChild(part7);
Element part8 = doc.createElement("element");
part8.setAttribute("name", "purchaseOrderNumber");
part8.setAttribute("type", "xsd:long");
sequence.appendChild(part8);
seventh.appendChild(sequence);
schema.appendChild(seventh);
Element eighth = doc.createElement("complexType");
eighth.setAttribute("name", "sendInvoiceRequest");
sequence = doc.createElement("sequence");
Element part5 = doc.createElement("element");
part5.setAttribute("name", "price");
part5.setAttribute("type", "xsd:double");
sequence.appendChild(part5);
Element part9 = doc.createElement("element");
part9.setAttribute("name", "customerId");
part9.setAttribute("type", "xsd:long");
sequence.appendChild(part9);
Element part10 = doc.createElement("element");
part10.setAttribute("name", "purchaseOrderNumber");
part10.setAttribute("type", "xsd:long");
sequence.appendChild(part10);
eighth.appendChild(sequence);
schema.appendChild(eighth);
Element ninth = doc.createElement("complexType");
ninth.setAttribute("name", "correlationset");
sequence = doc.createElement("sequence");
Element part11 = doc.createElement("element");
part11.setAttribute("name", "PurchaseOrder");
part11.setAttribute("type", "tns:correlationsetvalues");
sequence.appendChild(part11);
ninth.appendChild(sequence);
schema.appendChild(ninth);
Element tenth = doc.createElement("complexType");
tenth.setAttribute("name", "correlationsetvalues");
sequence = doc.createElement("sequence");
Element part12 = doc.createElement("element");
part12.setAttribute("name", "PurchaseOrderNumber");
part12.setAttribute("type", "xsd:string");
sequence.appendChild(part12);
Element part13 = doc.createElement("element");
part13.setAttribute("name", "customerID");
part13.setAttribute("type", "xsd:string");
sequence.appendChild(part13);
tenth.appendChild(sequence);
schema.appendChild(tenth);
// show the schema w3c element via conversion JDOM Element and coversion to string
org.jdom.input.DOMBuilder jdbuilder = new org.jdom.input.DOMBuilder();
org.jdom.Element jelement = jdbuilder.build(schema);
//System.out.println("\njelement " + jelement);
org.jdom.output.XMLOutputter xmloutput = new org.jdom.output.XMLOutputter();
xmloutput.setIndent(" ");
xmloutput.setNewlines(true);
xmloutput.setTrimAllWhite(true);
xmloutput.setTextTrim(true);
xmloutput.setEncoding("ISO-8859-1");
String strelement = xmloutput.outputString(jelement);
System.out.println("schema in jdom = \n " + strelement);
UnknownExtensibilityElement extel = new UnknownExtensibilityElement();
extel.setElement(schema);
extel.setElementType(new QName(Constants.Q_ELEM_XSD_2001.getNamespaceURI(),
schema.getLocalName()));
types.addExtensibilityElement(extel);
// the above is preferrable to this
//types.setDocumentationElement(schema);
//System.out.println("schema " + schema);
// and set the types definiton back to the definition object
definition.setTypes(types);
// these lines all show null or empty on system.out.println
//System.out.println("\ntypes " + types);
// end of setting the types
// add the messages*******************************************************
MessageImpl message1 = (MessageImpl)definition.createMessage();
QName messageqname= new QName("http://www.yoerg.net", "newMessage");
message1.setQName(messageqname);
PartImpl partma = (PartImpl)definition.createPart();
partma.setName("sendPurchaseOrderBody");
partma.setElementName(new QName("http://www.yoerg.net", "sendPurchaseOrder"));
message1.addPart(partma);
partma = (PartImpl)definition.createPart();
partma.setName("correlationsBody");
partma.setElementName(new QName("http://www.yoerg.net", "correlations"));
message1.addPart(partma);
partma = (PartImpl)definition.createPart();
partma.setName("portTypeBody");
partma.setElementName(new QName("http://www.yoerg.net", "portType"));
message1.addPart(partma);
partma = (PartImpl)definition.createPart();
partma.setName("partnerLinkBody");
partma.setElementName(new QName("http://www.yoerg.net", "partnerLink"));
message1.addPart(partma);
definition.addMessage(message1);
// create new blank message for response, with no parts
MessageImpl message2 = (MessageImpl)definition.createMessage();
QName messageqname2= new QName("http://www.yoerg.net", "sendPurchaseOrderResponseMessage");
message2.setQName(messageqname2);
definition.addMessage(message2);
System.out.println("\nmessage1 " + message1);
System.out.println("\nmessage2 " + message2);
//Map map = message.getParts();
//Element mes = message.getDocumentationElement();
//System.out.println("\nmessage map = " + map);
// done adding messages
// add the porttypes******************************************************
PortTypeImpl porttype = (PortTypeImpl)definition.createPortType();
porttype.setQName(new QName("http://www.yoerg.net", "purchaseOrderPortType"));
OperationImpl operation = (OperationImpl)definition.createOperation();
operation.setName("sendMyPurchaseOrder");
operation.setStyle(javax.wsdl.OperationType.REQUEST_RESPONSE);
InputImpl input = (InputImpl)definition.createInput();
input.setName("sendPurchaseOrderRequest");
input.setMessage(message1);
operation.setInput(input);
OutputImpl output = (OutputImpl)definition.createOutput();
output.setName("sendPurchaseOrderResponse");
output.setMessage(message2);
operation.setOutput(output);
porttype.addOperation(operation);
System.out.println("\nporttype " + porttype);
definition.addPortType(porttype);
// done adding the porttypes
// add the bindings*******************************************************
BindingImpl binding = (BindingImpl)definition.createBinding();
binding.setQName(new QName("http://www.yoerg.net",
"purchaseOrderSOAPBinding"));
binding.setPortType(porttype);
SOAPBindingImpl bindingextension = new SOAPBindingImpl();
bindingextension.setStyle("document");
bindingextension.setTransportURI("http://schemas.xmlsoap.org/soap/http");
//System.out.println("binding extension " + bindingextension);
binding.addExtensibilityElement(bindingextension);
BindingOperationImpl bindingoperation
= (BindingOperationImpl)definition.createBindingOperation();
bindingoperation.setName("sendMyPurchaseOrder");
bindingoperation.setOperation(operation);
// this is not present in the Imported correct version, and these lines of code
// are not necessary, but they also do not hurt or help
//SOAPOperationImpl operationextension = new SOAPOperationImpl();
//operationextension.setStyle("document");
//operationextension.setSoapActionURI("");
///////operationextension.setElementType(new QName("http://www.yoerg.net", "ListenerService"));
//operationextension.setRequired(new Boolean(true));
//bindingoperation.addExtensibilityElement(operationextension);
BindingInputImpl bindinginput
= (BindingInputImpl)definition.createBindingInput();
bindinginput.setName("sendPurchaseOrderRequest");
SOAPBodyImpl inputextension = new SOAPBodyImpl();
inputextension.setUse("literal");
inputextension.setRequired(new Boolean(true));
inputextension.setNamespaceURI("http://www.yoerg.net");
bindinginput.addExtensibilityElement(inputextension);
//System.out.println("\ninputextension " + inputextension);
bindingoperation.setBindingInput(bindinginput);
BindingOutputImpl bindingoutput
= (BindingOutputImpl)definition.createBindingOutput();
bindingoutput.setName("sendPurchaseOrderResponse");
SOAPBodyImpl outputextension = new SOAPBodyImpl();
outputextension.setUse("literal");
outputextension.setRequired(new Boolean(true));
outputextension.setNamespaceURI("http://www.yoerg.net");
bindingoutput.addExtensibilityElement(outputextension);
//System.out.println("\noutputextension " + outputextension);
bindingoperation.setBindingOutput(bindingoutput);
binding.addBindingOperation(bindingoperation);
System.out.println("\nbinding " + binding);
definition.addBinding(binding);
// done adding binding
// adding service*********************************************************
ServiceImpl service = (ServiceImpl)definition.createService();
service.setQName(new QName("http://www.yoerg.net",
"ListenerServiceService"));
PortImpl port = (PortImpl)definition.createPort();
port.setBinding(binding);
port.setName("ListenerService");
SOAPAddressImpl soapaddress = new SOAPAddressImpl();
soapaddress
.setLocationURI("http://localhost:8080/axis/services/ListenerService");
port.addExtensibilityElement(soapaddress);
service.addPort(port);
definition.addService(service);
System.out.println("\nService " + service);
// done adding service
// print def object, and you will see all objects, except types
System.out.println("\ndefinition \n" + definition);
// output to file, just like we would in bpel workflow environment
com.ibm.wsdl.xml.WSDLWriterImpl writer
= (com.ibm.wsdl.xml.WSDLWriterImpl)factory.newWSDLWriter();
File file = new File("c:\\chris\\w.wsdl");
FileOutputStream out = null;
// this has been proven to be correct
try{
out = new FileOutputStream(file);
writer.writeWSDL(definition, out);
catch(FileNotFoundException fnfe){
System.out.println("file not found " + fnfe.getMessage());
catch(IOException ioe){
System.out.println("file not found " + ioe.getMessage());
catch(javax.wsdl.WSDLException we){
System.out.println("wsdl exception " + we.getMessage());
// now bring it back in just for fun
FileInputStream in = null;
byte[] inputfile = null;
org.jdom.Document jdocument = null;
try{
in = new FileInputStream(file);
inputfile = new byte[in.available()];
in.read(inputfile, 0, in.available());
org.jdom.input.SAXBuilder jdombuilder = new org.jdom.input.SAXBuilder();
ByteArrayInputStream byteinput = new ByteArrayInputStream(inputfile);
jdocument = jdombuilder.build(byteinput);
catch(FileNotFoundException fnfe){
System.out.println("file not found " + fnfe.getMessage());
catch(org.jdom.JDOMException jde){
System.out.println("jdom exception " + jde.getMessage());
catch(IOException ioe){
System.out.println("io exception " + ioe.getMessage());
String strdocument = xmloutput.outputString(jdocument);
System.out.println("\nJDOM beautified version \n" + strdocument);
public static void main(String[] args){
WSDLFactory factory = new WSDLFactory();
factory.makeWorkflowWSDL();
End ofWSDLFactory.java*********************************************************************
Desired WSDL output to file******************************************************************
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="PurchaseOrderProcess" targetNamespace="http://www.yoerg.net"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:http-conf="http://schemas.iona.com/transports/http/configuration"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://www.yoerg.net" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<types>
<schema targetNamespace="http://www.yoerg.net"
xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<element name="sendPurchaseOrder" type="tns:sendPORequest"/>
<element name="correlations" type="tns:correlationset"/>
<element name="portType" type="xsd:string"/>
<element name="partnerLink" type="xsd:string"/>
<element name="sendSchedule" type="tns:sendScheduleRequest"/>
<element name="sendInvoice" type="tns:sendInvoiceRequest"/>
<complexType name="correlationsetvalues">
<sequence>
<element name="PurchaseOrderNumber" type="xsd:string"/>
<element name="customerID" type="xsd:string"/>
</sequence>
</complexType>
<complexType name="correlationset">
<sequence>
<element name="PurchaseOrder" type="tns:correlationsetvalues"/>
</sequence>
</complexType>
<complexType name="sendPORequest">
<sequence>
<element name="customerId" type="xsd:long"/>
<element name="purchaseOrderNumber" type="xsd:long"/>
<element name="productId" type="xsd:long"/>
<element name="quantity" type="xsd:int"/>
</sequence>
</complexType>
<complexType name="sendScheduleRequest">
<sequence>
<element name="shipDate" type="xsd:dateTime"/>
<element name="customerId" type="xsd:long"/>
<element name="purchaseOrderNumber" type="xsd:long"/>
</sequence>
</complexType>
<complexType name="sendInvoiceRequest">
<sequence>
<element name="price" type="xsd:double"/>
<element name="customerId" type="xsd:long"/>
<element name="purchaseOrderNumber" type="xsd:long"/>
</sequence>
</complexType>
</schema>
</types>
<message name="newMessage">
<part element="tns:sendPurchaseOrder" name="sendPurchaseOrderBody"/>
<part element="tns:correlations" name="correlationsBody"/>
<part element="tns:portType" name="portTypeBody"/>
<part element="tns:partnerLink" name="partnerLinkBody"/>
</message>
<message name="sendPurchaseOrderResponseMessage"/>
<message name="sendScheduleRequestMessage">
<part element="tns:sendSchedule" name="sendScheduleBody"/>
<part element="tns:correlations" name="correlationBody"/>
<part element="tns:portType" name="portTypeBody"/>
<part element="tns:partnerLink" name="partnerLinkBody"/>
</message>
<message name="sendInvoiceRequestMessage">
<part element="tns:sendInvoice" name="sendInvoiceBody"/>
<part element="tns:correlations" name="correlationsBody"/>
<part element="tns:portType" name="portTypeBody"/>
<part element="tns:partnerLink" name="partnerLinkBody"/>
</message>
<portType name="purchaseOrderPortType">
<operation name="sendMyPurchaseOrder">
<input message="tns:newMessage" name="sendPurchaseOrderRequest"/>
<output message="tns:sendPurchaseOrderResponseMessage"
name="sendPurchaseOrderResponse"/>
</operation>
<operation name="sendMySchedule">
<input message="tns:sendScheduleRequestMessage" name="sendMySchedule"/>
</operation>
<operation name="sendInvoice">
<input message="tns:sendInvoiceRequestMessage" name="sendInvoice"/>
</operation>
</portType>
<binding name="purchaseOrderSOAPBinding" type="tns:purchaseOrderPortType">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="sendMyPurchaseOrder">
<soap:operation soapAction="" style="document"/>
<input name="sendPurchaseOrderRequest">
<soap:body use="literal"/>
</input>
<output name="sendPurchaseOrderResponse">
<soap:body use="literal"/>
</output>
</operation>
<operation name="sendMySchedule">
<soap:operation soapAction="" style="document"/>
<input name="sendMySchedule">
<soap:body use="literal"/>
</input>
</operation>
<operation name="sendInvoice">
<soap:operation soapAction="" style="document"/>
<input name="sendInvoice">
<soap:body use="literal"/>
</input>
</operation>
</binding>
<service name="ListenerServiceService">
<port binding="tns:purchaseOrderSOAPBinding" name="ListenerService">
<soap:address location="http://localhost:8080/axis/services/ListenerService"/>
<http-conf:client/>
<http-conf:server/>
</port>
</service>
</definitions>
End of desired WSDL*************************************************************************************

Adding these statements solved the problem
message1.setUndefined(false);
message2.setUndefined(false);
binding.setUndefined(false);
operation.setUndefined(false);
porttype.setUndefined(false);
This is kind of weird because you explicitly define them thru API calls, and this call seems redundant.
Chris Yoerg

Problem with .mov file type in premier elements 10 on windows 7

My canaon power shot elph movie uses .mov (apple file) which I sent to PE10. When I try to play it in PE10 only audio plays, there is no sink between audio and video. If I move the marker under the vidio the vidio will follow the mark playing. I am on window 7 pc. Any ideas? There is a audo vidil link in CLIP, but if is not hi-lited so I can activate it. I want to do some editing and then burn a DVD to play on my TV. Help!!!!

ri-olson
There is an epidemic of display issues targeting specifically Premiere Elements 10 users whose computer use a NVIDIA video card. For now, the answer is to roll back the video card driver version rather than to assure that you have the latest video card driver installed on your computer. Please check out the following thread in this regard and determine if any this applies to your situation.
http://forums.adobe.com/message/5836037
Once we rule this factor out, we can move on to other troubleshooting schemes.
What John T. Smith has asked is do you have the latest version of QuickTime installed on your computer with your Premiere Elements 10. If you do, the latest version is 7.7.4. You should be able to find confirming information on that in Help Menu/About QuickTime in the opened QuickTime. That is not a codec number. It is the version number (latest version) for the QuickTime program on which Premiere Elements is very dependent.
As for codec, in this case, the question being asked is what is the video compression in your file that has the .mov file extension. If you do not know and do not have access to a video properties reader (such as MediaInfo), perhaps we could get the needed information from the brand/model/settings information for the camera that was used to record the video.
Please review. We will be watching for your progress.
Thanks.
ATR

Move ment types

Hi to all
me ravi kumar
i have doubt
what is difference between 102 and 162?
pl explain
thank u
with regards
ravi kumar

Hi Ravi
102 is used to reverse the results of mvt type 101 i.e. you are taking material out of your inventory which results in decrease in value and qty of material in your stock.
where as while using 162 you are taking material back into your inventory from vendor i.e. material value and qty increases using this mvt type.
Regrds
Yogesh

Acconting doc. for move ment type-501 & trading material

Dear cons
If we receive the material through 501 Which accounting document will hit. Also pl. give process for trading material ( hawa). which accounting will hit for HAWA material type.
nrk

Hi
It entirely depends on whether the material type is maintained as value update in OMS2
If the material type has a value update then follwoing accounting entries are passed during 501
Stock acc Dr
Clearing account Cr
The material will be valuated at Price maintained in Material master
If the material type doesnot have a value update then accounting documnets will not be generated.
Regards
Sandeep

Move ment type

hi to all
i have one doubt. plz explain
how to block movement?
thanks
ravi

Hi,
You can block all goods movements relating to a stock management unit for the purposes of a physical inventory.
The system blocks all the stock management units of the relevant PI document by means of the posting block indicator in the PI document header. In the storage location view of the material master record, the physical inventory block indicator shows the value X (material blocked for movements due to physical inventory).
For that you have to change mode of a physical inventory document, set the posting block indicator.
Reward if useful
Chandru.

Early lot creation

Dear Gurus,
When working with early lot creation, with batch management activated, if I received a partial quantity from an order, it is posted normally to quality, then I make the UD for this lot and it is closed, then if I receive another quantity from the order, it goes unrestricted and do not create a new inspection lot !!!!
Is that normal or there is problem? If normal how can I overcome this?
Regards,
MaX

Dear it is standard procedure system is behaving correct only.
if you want every time stock you do GR for order stock should be posted to QI then in MM QM view keep inspection type control as "each order,batch and storage location" means for 1 order if production do multiple confirmation ( N times) system create only one inspection lot and all the confirmation stock updated to the same inspection lot.
Cheers
KK

Next Inspection Date in case of Mov. Type: 309

Hi,
During Transfer posting using Mov. Type: 309, (Inspection Type: 08) the Next Inspection Date is coming as per our logic of UD Date + 365 (Inspection Interval maintained in Material Mst.).
But our requirement if that, the Next Inspection Date in case of transferred material must be same as from which transfer has been done.
e.g. suppose material ABC is received with GR (Mov. Type:101) and its Its Next Inspection date is coming as 01/01/2012 (as its UD was done on 01/01/2011 + 365 (Inspection Interval maintained in Mtrl Mst).
When we transfer this material to XYZ (with Mov. Type:309), its Next Inspection Date is required that of ABC (01/01/2012). But, as per present logic it is coming UD Date + 365 Days = 23/01/2012 (i.e. if UD is performed on 23/01/2011).
How can I do that ?
Thanx
Vivek

My guess is your batch level is at the plant level. If the batch level is changed to material level or client level, this problem would go away. This can have major impacts in other areas so it must be carefully considered. But if this your requirement, it sounds like you might be at the wrong batch level right now.
FF

Inspection lot creation logic related movement type

Dear QM Guru,
I'm newly for QM module
I would like to know how config of movement type and lot origin under below config relate to inspection lot creation.
Quality Management>Quality Inspection>Inspection for Goods Movements-->Movement Type/Update Control/Inspection Lot Origin
i try to delete all record of customized movement type 949 that i think it copy from movement type 501 in this customizing then try to GR with this movement type, so system still generate inspection as normal.
then i re-insert the movement back into this customizing again then i wonder that system automatic fill in lot origin for me and this field also gray that not changeable
how system know the appropriate lot origin for this customized movement type?
Please anyone explain to me.
Thank in advance
Konnapa

Hi,
Inspection lot origins are assigned to movement types in standart. The assignment is hardcoded and cannot be changed. In this customization step you can only see the origin assigned. When you copy movement types from standart the assigned inspection origin also gets copied, and you also cannot chenge this assignment.
What you can do is to activate inspection for each movement type, or to customize selection of the inspection type within the inspection origin assigned.
Regards.

QM _Inspection Lot Creation with Move ment type-542

Similar Messages

Maybe you are looking for