ABAP development namespace prefix and XI naming

Hi,
while going to establish company wide SAP XI naming conventions the question arised, if there should be any relationship between naming for XI design and configuration objects and the so called "reserved development namespace prefix" known from ABAP programming. Is it, e.g. advisable to use the reserved ABAP namespace prefix as part of XI repository namespaces?
Any experiences?
Thanks and best regards,
Barbara

Hi Barbara,
Setting up XI naming conventions for a company needs a holistic approach looking what is already out there for java, abap, xml etc. so there is no easy answer to any question regarding naming conventions, only ideas. You have to look at how these ideas fit into your existing conventions, so let me give you my idea on that:
if your company has its own reserved ABAP namespace like /COMP/, you should definitely use that in Proxy Generation as prefix. However a usage in XI namespaces depends on what the Abap NS looks like. SAPs suggestion is to use a namespace like http://company.com/xi/... and i think, it is a very good suggestion, so i would definitely use something similar. Normally i would use the URL similar to the companies website e.g. if the website is http://www.company.com, i would just delete the www out of it. Now you might have a company with a very long name and even website URL and namespaces are restricted to 60 characters so you possibly run into length issues and decide to use an abbreviation, in that case i would definitely use an existing abap namespace as abbreviation if the namespace is somehow descriptive.
Regards
Christine

Similar Messages

SAP Netweaver ABAP Development 7.0 and Kaspersky IS 2010

Hi All,
Iu2019m trying to figure out how to make KIS 2010 and SAP Netweaver work together but so far I couldnu2019t find a u201Cgoodu201D solution.
The only way that I figured out so far, to make it work, is turn off the u201CApplication Controlu201D on KIS2010.
Do you know some exceptions that I can insert to u201Copenu201D the kaspersky for the SAP applications?
Thank you very much in advance.
Regards
Antonio Centenaro

Hi,
You should ask Kaspersky support about this issue. It is not a SAP problem !
Regards,
Olivier

Namespace prefix in SOAP Elements causes problems in XI

Hi guys,
I'm using code generated by NW Developer Studio for use inside Portal components acting as a web service consumer. The problem is that the code generated includes a namespace prefix for each element in the body of the message, but XI doesn't like the namespace prefixes and throws back a DeliveryException.
The SOAP message created by the generated NWDS code is:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wn3="http://www.w3.org/1999/XMLSchema" xmlns:wn2="http://www.w3.org/2000/10/XMLSchema" xmlns:wn1="http://www.w3.org/2001/XMLSchema" xmlns:wn0="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wn4="http://allieddomecq.com/poc" xmlns:tns="http://allieddomecq.com/poc">
     <SOAP-ENV:Body>
          <wn4:PortalSOAP_MT_Request>
               <wn4:CustomerIdentifier>0001000064</wn4:CustomerIdentifier>
               <wn4:SalesOrganization>ES50</wn4:SalesOrganization>
               <wn4:SystemIdentifier>R3D</wn4:SystemIdentifier>
          </wn4:PortalSOAP_MT_Request>
     </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
The problem is the "wn4" prefixes on the CustomerIdentifier, SalesOrganization, and SystemIdentifier tags. When we send the soap request from XML Spy without the prefixes, the response comes back OK with the expected data.
I've had a very good look around the generated code - the serializers for creating the soap request - but could not find what exactly might be changed to leave off the prefixes.
Alternatively, is there something I could ask our XI consultant to do, to make his component accept the request with the redundant prefixes in the tags?
Many thanks for any advice/help,
Laura

Hi Laura,
you have to realize that the two documents
<ns:CustomerRecord xmlns:ns="http://company.com">
<ns:CustomerNumber> </ns:CustomerNumber>
<ns:CustomerDetails> </ns:CustomerDetails>
</ns:CustomerRecord>
and
<ns:CustomerRecord xmlns:ns="http://company.com">
<CustomerNumber> </CustomerNumber>
<CustomerDetails> </CustomerDetails>
</ns:CustomerRecord>
from an XMl point of view have totally fifferent structure. Thus, a mapping which is able to deal with the first structure will fail for the second and vice versa.
Surely, both structures somehow can carry the same information, but they do this with different languages (Maybe you can compare this to the fact, that you may deliver the same information in English or in German language).
When you model the structure in Integration Repository using datatypes and message types (what I think you did), you will always get a structure that looks like the second one. This is just a convention (like the convention that all information in this forum should be presented in English). When defining a message mapping for this structure it also relies on this fact and thus will not understand the other kind of document.
External Definitions are more flexible. They are also able to understand structures that are modelled the other way. This greater flexibility is due to the fact that External Definitions were designed to understand structures that come from an external world where different conventionts might be used.
To come to a conclusion: If the structure you have to deal with has been defined externally then it is not intended that you model it inside the Integration Builder using datatypes and message types. In this case the external source should provide a description of the message as XSD, WSDL, or DTD. You upload this as External Definition, and everything works fine.
If you have designed the structure yourself, you can model it with datatypes and message types. But then you will always get a structure which looks like the second one. In this case you should make sure that all other participants in the game also stick to that structure. Then everything will be fine, too.
Greetings Stephan

How are you using the Namespace Prefix?

As the subject says...
The top-level namespace prefix looks very useful for segregating projects into their own namespaces...is this what this is for, or does SAP have another recommended use for this prefix?
The vendor name already makes the namespace unique to a corporate entity (if you use the domain name), so anything after that is really only of importance to the internal development environment...

Even if your development isn't that big, using the 'name space prefix' would allow you to further segregate your codebase.
This also becomes important when your domain name is rather long - 15 characters. Take away four or so more for the namespace prefix, and you're left with 20 characters for the DC name. Add in a few separators, and you're down to 12-15 characters.
Obviously, readability can suffer when you start to abbreviate too much, so I'm looking for best practices when it comes to the namespace prefix.
Thanks for your comment.

Disable namespace prefixes in Transformer

hi
I am stuck in a cyclic problem. JAXP XSLT and SchemaValidator do not work together. (Java 1.5 and 1.6)
I have a XSD with a namespace.
When I generate the XML using an XSLT I specify namespace using the namespace attribute of xsl:element
The JAXP transformer always generate the namespace prefix and equate the prefix with the actual URI
Is there a way to disable this behavior, that is, I do want the xmlns URI in the root element but not the prefix?
There are two reasons for wanting an XML without prefixes:
1) The Schema Validator provided with JRE is not able to validate the message with prefix, but it works fine with xmlns URI
<rootelem xmlns="urn:xmlns:xyz.abc.com"> validates fine
but
<ns0:rootelem xmlns:ns0="urn:xmlns:xyz.abc.com"> fails validation with error:
org.xml.sax.SAXParseException: cvc-elt.1: Cannot find the declaration of element 'ns0:rootelem'.
I am able to generate the first case when I use Saxon based OrangeXSLT plugin for Eclipse but JAXP based transformer always generate the second case.
2) More importantly, I have XML consumers that could use parsing without namespace support and prefixed element will not work there.
I am using StreamResult in the Transformer.transform() call and my guess is that the internal implementation of Transformer might be using a SAX ContentHandler (XML Serializer) to write XML to the outputStream and I guess one way to get around could be that I write a custom ContentHandler and use a SAXResult in the transform call. I am not sure if I am thinking in the right direction.
If I am correct in my guess, could someone please point to some implementation of XMLSerializer that could be overridden just to disable namespace prefixing behavior?
I have removed the namespace from the XSD for things to work. I would appreciate any help with this.

Moving to latest Xalan and Xerces solved the problem.
But a new one surfaced.
Xalan's latest transformer does not handle StreamSource correctly and throws some exception internally (IOException related to end of stream), with the message:
SystemId Unknown; Line #-1; Column #-1; Premature end of file.
It work correctly if a DOMSource is provided as the input. This does not make sense, since the InputStream my code is using for StreamSource is ByteArrayInputStream for an in-memory XML and such error would happen if this stream is read more than once without calling a reset in between.
Please let me know if this seems like a valid bug or if I am doing something wrong.

Namespace declaration and W3C standart

Hello,
W3C has following specs for Namespace declaration in XQuery:
http://www.w3.org/TR/xquery/#id-namespace-decls
"[117] NamespaceDecl ::= "declare" "namespace" NCName "=" StringLiteral
A namespace declaration declares a namespace prefix and associates it with a namespace
URI, adding the (prefix, URI) pair to the set of in-scope namespaces. The string
literal used in a namespace declaration must be a valid URI, and may not be a
zero-length string.[err:XQ0046] The namespace declaration is in scope throughout
the query in which it is declared, unless it is overridden by a namespace declaration
attribute in an element constructor.
The following query illustrates a namespace declaration:
declare namespace foo = "http://example.org";
<foo:bar> Lentils </foo:bar> "
BNF production grammar requires "declare" token to be placed before namespace,
while
Liquid Data reports parsing error if the word is there.
How close Liquid Data XQuery grammar to the W3C standart?
Also, does "of type" exist in XQuery ?
Sincerely,
Benjamin.

Thank you for quick answer.
Sorry, my fault - didn't notice that fact.
Benjamin.
"Mike Reiche" <mreiche@news_group_only.com> wrote:
LD 8.1 was released in July 2003 (before the August 2003 spec). It adheres
to
http://www.w3.org/TR/2001/WD-xquery-20011220/#id-namespace-decls-and-schemas
http://e-docs.bea.com/liquiddata/docs81/prodover/concepts.html
- Mike Reiche
"Benjamin Shrom" <[email protected]> wrote:
Hello,
W3C has following specs for Namespace declaration in XQuery:
http://www.w3.org/TR/xquery/#id-namespace-decls
"[117] NamespaceDecl ::= "declare" "namespace" NCName
"=" StringLiteral
A namespace declaration declares a namespace prefix and associates it
with a namespace
URI, adding the (prefix, URI) pair to the set of in-scope namespaces.
The string
literal used in a namespace declaration must be a valid URI, and may
not be a
zero-length string.[err:XQ0046] The namespace declaration is in scope
throughout
the query in which it is declared, unless it is overridden by a namespace
declaration
attribute in an element constructor.
The following query illustrates a namespace declaration:
declare namespace foo = "http://example.org";
<foo:bar> Lentils </foo:bar> "
BNF production grammar requires "declare" token to be placed beforenamespace,
while
Liquid Data reports parsing error if the word is there.
How close Liquid Data XQuery grammar to the W3C standart?
Also, does "of type" exist in XQuery ?
Sincerely,
Benjamin.

Conversion Agent - Namespace prefix missing

Hi Guys,
Trying to use CA to convert a flat file to nested XML. I managed to succesfuly build a script that converts the flat file to XML.
The problem I am facing here is that, the converted XML is not having a namespace prefix and hence my mappings fail.
Can you please let me know if there is some setting which allows me to add the namespace prefix in the output XML generated?
Thanks
Jai
Just a bump
Edited by: Jaishankar on Mar 12, 2010 10:09 AM

In your TGP file you have one option "allow_empty_values".
Use that for optional fields.
example will be as below :
Content<optional, allow_empty_values>(OffsetSearch(StaticInt()), TextSearch(StaticString("")), null_searcher, XPath("/X12/s/s1/TS_850/s/REF/*s/REF02")),

How can I change namespace prefix for JAX-RPC client request?

I'm creating a JAX-RPC client to invoke a RPC/encoded web service. The service was generated from a ColdFusion program and for some reason when the SOAP namespace prefix is anything but "soapenv" it returns text/html instead of text/xml. Currently the client is sending requests with the prefix "env" and I'd like to change it to "soapenv".
I created a type of javax.xml.rpc.handler.GenericHandler and attempted to do the follow:
@Override public boolean handleRequest(MessageContext p1) {
     SOAPMessage msg = ((SOAPMessageContext) p1).getMessage();
     try {
          SOAPPart part = msg.getSOAPPart();
          SOAPEnvelope envelope = part.getEnvelope();
          envelope.setPrefix("soapenv");
          msg.saveChanges();
     } catch(SOAPException ex) {
          // TODO
          return false;
     return true;
However I get the following exception:
java.rmi.RemoteException: SOAPFaultException - FaultCode [{http://schemas.xmlsoap.org/soap/envelope/}Server] FaultString [UNIMPLEMENTED ] FaultActor [null] Detail [<detail><bea_fault:stacktrace xmlns:bea_fault="http://www.bea.com/servers/wls70/webservice/fault/1.0.0">java.lang.AssertionError: UNIMPLEMENTED
at weblogic.xml.domimpl.NodeImpl.setPrefix(NodeImpl.java:173)
at test.MyHandler.handleRequest(MyHandler.java:33)
at weblogic.wsee.handler.JaxrpcHandlerChain.handleRequest(JaxrpcHandlerChain.java:58)
at weblogic.wsee.ws.dispatch.server.JaxrpcChainHandler.handleRequest(JaxrpcChainHandler.java:102)
at weblogic.wsee.handler.HandlerIterator.handleRequest(HandlerIterator.java:141)
at weblogic.wsee.handler.HandlerIterator.handleRequest(HandlerIterator.java:107)
at weblogic.wsee.ws.dispatch.client.ClientDispatcher.dispatch(ClientDispatcher.java:132)
at weblogic.wsee.ws.WsStub.invoke(WsStub.java:87)
at weblogic.wsee.jaxrpc.StubImpl._invoke(StubImpl.java:341)
at test.Approvedsuppliers_Wrap_Stub.echo(Approvedsuppliers_Wrap_Stub.java:31)
at test.Approvedsuppliers_WrapPortClient.echo(Approvedsuppliers_WrapPortClient.java:130)
at test.Approvedsuppliers_WrapPortClient.main(Approvedsuppliers_WrapPortClient.java:43)
Is there any workaround? I appreciate any feedback.
Thanks, Bill

What I ended up doing is converting the SOAP message to a string, replacing the namespace prefix and converting it back to a SOAP message.
@Override
   public boolean handleRequest(MessageContext messageContext) {
      SOAPMessageContext soapMessageContext = (SOAPMessageContext) messageContext;
      SOAPMessage soapMessage = soapMessageContext.getMessage();
      String soapString = convertSOAPToString(soapMessage);
      soapString = soapString.replaceAll("env:", "soapenv:");
      soapString = soapString.replaceAll("xmlns:env", "xmlns:soapenv");
      SOAPMessage newSoapMessage = convertStringToSOAP(soapString);
      MimeHeaders mimeHeader = newSoapMessage.getMimeHeaders();
      mimeHeader.setHeader("SOAPAction", "");
      soapMessageContext.setMessage(newSoapMessage);
      return true;
   private String convertSOAPToString(SOAPMessage soapMessage) {
      StringWriter stringWriter = null;
      try {
         stringWriter = new StringWriter();
         StreamResult streamResult = new StreamResult(stringWriter);
         TransformerFactory transformFactory = TransformerFactory.newInstance();
         Transformer transformer = transformFactory.newTransformer();
         transformer.transform(new DOMSource(soapMessage.getSOAPPart()), streamResult);
      } catch (TransformerException e) {
         throw new RuntimeException(e);
      } finally {
         close(stringWriter);
      return stringWriter.toString();
   private SOAPMessage convertStringToSOAP(String soapString) {
      SOAPMessage soapMessage = null;
      ByteArrayInputStream byteInputStream = null;
      try {
         MessageFactory msgFactory = MessageFactory.newInstance();
         soapMessage = msgFactory.createMessage();
         SOAPPart soapPart = soapMessage.getSOAPPart();
         // Load the SOAP text into a stream source
         byte[] buffer = soapString.getBytes();
         byteInputStream = new ByteArrayInputStream(buffer);
         StreamSource source = new StreamSource(byteInputStream);
         // Set contents of message
         soapPart.setContent(source);
      } catch (SOAPException e) {
         throw new RuntimeException(e);
      } finally {
         close(byteInputStream);
      return soapMessage;
   private void close(Closeable closeable) {
      if(closeable != null) {
         try {
            closeable.close();
         } catch (IOException e) {
            // TODO

ABAP Development and "End User License"

Hi all,
I'm happy to join to SDN!!!
I newbe in the forum, and therefore I don't know if I post in the right section.
I'm a Netweaver Architect and ABAP Developer.
In the past I worked as java developer, and with other programming languages.
I have a doubt: is it possible (or forbidden by SAP AG??) to develop an ABAP package (which, obiousvly, contains Z / Y Abap objects) and apply an "End User License" on it, i.e. on the ABAP code written? (I mean that the copryrights are mine, and I give an "End User License" to my customers (that buy the license), in order to get and run my abap code). I would avoid to sell my Abap package, but, if possibile, I would only give it according a "Use License".
May I do this thing without any problems, or have I to consider other aspects, like ask to SAP to reserve a namespace, or obtain SAP Netweaver certification for my ABAP solution, or other things?
(Infact the "End User License" that I mean is different from "SAP End User License")
Please, let me know your opinion and how or who could solve my matter.
Many thanks to all.
Best Regards,
Albert

Hello,
Can you point us there in this thread please?
Kind regards
Ash Thomas
Sap Consultant
<a href=http://www.ashpeople.com>Sap Consultancy</a>
<a href=http://www.ashpeople.com>www.ashpeople.com</a>

ABAP development license and AAK install

Hello,
What is the ABAP development license? Is it a license that has to be registered within our SAP system that our development is done on? Or is it just a license number that we reference on our test reports, certification etc? Just wondering what work, if any, is involved here.
AAK install. Is this just a typical install through SAINT?
Thanks.
Regards,
Scott

Hello Roy, Scott and Abraham,
Yes, indeed you will have to maintain such a development landscape, purchasing development license is not sufficient. Every customer Add-on must be delivered using a development namespace (i.e. /ABC/<name_of_object>), it is not advisable to delivered Add-on in customer namespace (i.e. starting with Z***).
AAK or Add-on Assembly Kit will be delivered to only those vendors who sign up for ABAP Add-on certification with ICC.
Hope this helps.
Regards,
Srini

Roles and Responsibilities of an ABAP developer in Blueprint Phase

Hi All ,
I am about to get into HR implementation project Where its in the blueprint phase , I just want to know what are the roles and responsibilities of an ABAP Developer in this phase ? Is there something to be done on the functional part .

Hi Hope you helpful this followings
Getting the business Requirement document from functional consultant / functional analyst.
Analyse the business Requirement.
Analyse the estimated time for development.
Development of Object (ABAP Application).
Unit Testing by Developer.
Releasing the object to testing environment.
Prepare technical document of the development.

DBMS_XMLDOM - add namespaces attributes and prefix

Hi,
try to add a prefix and a namespace to the root node of an XML structure. Have tried the following code but i failed to add both.
XML-structure before:
<PERSON>
<NAME>something</NAME>
</PERSON>
XML-structure desired:
<pk:PERSON xmlns:pk="http://www.test.com">
<NAME>something</NAME>
</pk:PERSON>
Any help is greatly appreciated.
THX
--------------- BEGIN ---------------------------
declare
var XMLType;
buf clob;
l_xmldoc dbms_xmldom.DOMDocument;
l_docelem dbms_xmldom.DOMElement;
l_root dbms_xmldom.DOMNode;
l_attr dbms_xmldom.DOMAttr;
begin
var := xmltype('<PERSON> <NAME>something</NAME> </PERSON>');
-- Create DOMDocument handle:
l_xmldoc := dbms_xmldom.newDOMDocument(var);
l_docelem := DBMS_XMLDOM.getDocumentElement(l_xmldoc);
-- set prefix
l_root := dbms_xmldom.makenode(l_docelem);
DBMS_XMLDOM.setPrefix(l_root, 'pk');
l_docelem := DBMS_XMLDOM.makeElement(l_root);
dbms_output.put_line('Prefix: '||dbms_xmldom.getPrefix(l_root));
dbms_output.put_line('l_root: '||dbms_xmldom.getNodeName(l_root));
dbms_output.put_line('-----');
-- add namespace attribute
l_attr := DBMS_XMLDOM.createAttribute(l_xmldoc, 'xmlns:pk');
DBMS_XMLDOM.setValue(l_attr, 'http://www.test.com');
l_attr := DBMS_XMLDOM.setAttributeNode(l_docelem, l_attr);
-- after
dbms_xmldom.writetobuffer(l_xmldoc, buf);
dbms_output.put_line('OUT:');
dbms_output.put_line(buf);
end;
--- OUTPUT ----- OUTPUT ----- OUTPUT --
Prefix: pk
l_root: pk:PERSON
OUT:
<PERSON xmlns:pk="http://www.test.com">
<NAME>something</NAME>
</PERSON>
------------------- END -----------------------

Seems to me you're hitting bug 2904964. I have the same problem using these functions.

Difference between ECC5.0 and SAP 4.7 (ABAP developer point of view)

dear experts,
can anyone tell me the mian difference between ECC5.0 and SAP 4.7 from an abap developer view point.
thanks in advance

Hi,
From an ABAP perspective, there are not many changes, but addition of new classes, methods etc.
Please refer to the link - http://solutionbrowser.erp.sap.fmpmedia.com/
The above link tells about both of the versions.
For more information, you can refer to release notes of ECC 5.0.
Thanks,
Srinivas

Creation of developement class,package and access key

COULD ANYBODY EXPLAIN about
creation of developement class,package and access key
and who will create them?

Working With Development Objects
Any component of an application program that is stored as a separate unit in the R/3 Repository is called a development object or a Repository Object. In the SAP System, all development objects that logically belong together are assigned to the same development class.
Object Lists
In the Object Navigator, development objects are displayed in object lists, which contain all of the elements in a development class, a program, global class, or function group.
Object lists show not only a hierarchical overview of the development objects in a category, but also tell you how the objects are related to each other. The Object Navigator displays object lists as a tree.
The topmost node of an object list is the development class. From here, you can navigate right down to the lowest hierarchical level of objects. If you select an object from the tree structure that itself describes an object list, the system displays just the new object list.
For example:
Selecting an Object List in the Object Navigator
To select development objects, you use a selection list in the Object Navigator. This contains the following categories:
Category
Meaning
Application hierarchy
A list of all of the development classes in the SAP System. This list is arranged hierarchically by application components, component codes, and the development classes belonging to them
Development class
A list of all of the objects in the development class
Program
A list of all of the components in an ABAP program
Function group
A list of all of the function modules and their components that are defined within a function group
Class
A list of all of the components of a global class. It also lists the superclasses of the class, and all of the inherited and redefined methods of the current class.
Internet service
A list of all of the componentse of an Internet service:
Service description, themes, language resources, HTML templates and MIME objects.
When you choose an Internet service from the tree display, the Web Application Builder is started.
See also Integrating Internet Services.
Local objects
A list of all of the local private objects of a user.
Objects in this list belong to development class $TMP and are not transported. You can display both your own local private objects and those of other users. Local objects are used mostly for testing. If you want to transport a local object, you must assign it to another development class. For further information, refer to Changing Development Classes
http://help.sap.com/saphelp_46c/helpdata/en/d1/80194b454211d189710000e8322d00/content.htm
Creating the Main Package
Use
The main package is primarily a container for development objects that belong together, in that they share the same system, transport layer, and customer delivery status. However, you must store development objects in sub-packages, not in the main package itself.
Several main packages can be grouped together to form a structure package.
Prerequisites
You have the authorization for the activity L0 (All Functions) using the S_DEVELOP authorization object.
Procedure
You create each normal package in a similar procedure to the one described below. It can then be included as a sub-package in a main package.
To create a main package:
1.       Open the Package Builder initial screen (SE21 or SPACKAGE).
2.       In the Package field, enter a name for the package that complies with the tools Naming Conventions
Within SAP itself, the name must begin with a letter from A to S, or from U to X.
3.       Choose Create.
The system displays the Create Package dialog box.
4.       Enter the following package attributes:
Short Text
Application Component
From the component hierarchy of the SAP system, choose the abbreviation for the application component to which you want to assign the new package.
Software component
Select an entry. The software component describes a set of development objects that can only be delivered in a single unit. You should assign all the sub-packages of the main package to this software component.
Exception: Sub-packages that will not be delivered to customers must be assigned to the HOMEsoftware component.
Main Package
This checkbox appears only if you have the appropriate authorization (see Prerequisites).
To indicate that the package is a main package, check this box.
5.       Choose Save.
6.       In the dialog box that appears, assign a transport request.
Result
The Change package screen displays the attributes of the new package. To display the object list for the package in the Object Navigator as well, choose from the button bar.
You have created your main package and can now define a structure within it. Generally, you will continue by adding sub-packages to the main package. They themselves will contain the package elements you have assigned.
See also
Adding Sub-Packages to the Main Package
http://help.sap.com/saphelp_nw04/helpdata/en/ea/c05d8cf01011d3964000a0c94260a5/content.htm
access key used for change standard program.
www.sap.service.com

Problem with namespace prefix

Dear all,
I'm using code generated by NW Developer Studio 2004s for use inside Portal components acting as a web service consumer. The problem is that the code generated includes a namespace prefix for each element in the body of the message, but ECC (ERP 6.0) doesn't like the namespace prefixes (the namespace was not recognised by the ECC mapping tool.)and throws back a DeliveryException.
The SOAP message created by the generated NWDS code is:
<?xml version="1.0" encoding="UTF-8" ?>
- <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wn3="http://www.w3.org/1999/XMLSchema" xmlns:wn2="http://www.w3.org/2000/10/XMLSchema" xmlns:wn1="http://www.w3.org/2001/XMLSchema" xmlns:wn0="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wn4="urn:sap-com:document:sap:rfc:functions" xmlns:tns="urn:sap-com:document:sap:rfc:functions">
- <SOAP-ENV:Body>
- <wn4:Z_APPOINTMENT_GET_JCO_ORG>
<wn4:DATE_FROM>2007.01.01</wn4:DATE_FROM>
<wn4:DATE_TO>2008-02-02</wn4:DATE_TO>
<wn4:USERID>EGREO</wn4:USERID>
</wn4:Z_APPOINTMENT_GET_JCO_ORG>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
I've had a very good look around the generated code - the serializers for creating the soap request - but could not find what exactly might be changed to leave off the prefixes.
I am using portal server 2004s
Many thanks for any advice/help
Reza

I find out how should I do that.
/Reza

ABAP development namespace prefix and XI naming

Similar Messages

Maybe you are looking for