SAP WEBSERVICE soap in Rpc-style and Document-style

RPC is describing Webserivce in a method invocation, that is, you have to make clear the method that is called and the name and value of each parameter. To describe this stuff. The SOAP message is going to have a uniform specification that says that part is the method name. Which part is the parameter and which part is the return value.
Other words. The SOAP message format for RPC mode calls is rule-based and fixed. For example Each parameter must correspond to a Part,part name must match the name of the participant.

It can be seen that the document form is more flexible-especially when there is a need to transfer XML documents in a particular format, while RPC SOAP messages can actually be simulated in document form (only if the schema is properly defined). So the document approach is now more widely used (and the default in. net).
To namespace, I think there should be no obvious difference between the two. Primarily, RPC is typically used in conjunction with the encoding pattern, which refers to the namespace of soap, and the document simply refers to the XmlSchema namespace definition type.

SAP WEBSERVICE soap in Rpc-style and Document-style