Xml name space for generated types

By default the autotype or the servicegen ant task seem to be creating a namespace
from the java package name (like java:com.ventaso.external.common) for xml mapping
of user defined java classes. Is there a way to change this to name space I want
? Specifying the targetnamespace doesn't seem to help.
Thanks,
Siva

The targetNamespace is for webservice and not for the user defined classes.
Sorry for the confusion
Ajay
"Ajay" <[email protected]> wrote in message
news:[email protected]..
There is a targetNamespace attribute in the autotyp ant task. But there
was a bug in 8.1. Contact the support for a patch.
The following mail explains that
This looks like a bug. There is an undocument, not officially
supported workaround: add the following java doc
to yours source code -
* @wlws:webservice targetNamespace="http://foo.bar"
public class MyService {
Details here:
http://www.manojc.com/tutorial/sample3/source2wsdd.html
Regards,
-manoj
http://manojc.com
"Mark Fine" <[email protected]> wrote in message
news:[email protected]..
The attribute targetNamespace (of the autotype task) doesn't seem to putany
information into the types file and later my deployment descriptor (viathe
source2wsdd task) contains an invalid targetNamespace attribute with a
http://tempuri.org:
eg.
<web-services>
<web-service name="IndexService"
targetNamespace="http://tempuri.org/"
uri="/IndexWebService">
I don't think this causes any problems but there should be a way tospecify
the namespace.
Has anyone else seen this is WLS8.1?
"Siva" <[email protected]> wrote in message
news:[email protected]..
By default the autotype or the servicegen ant task seem to be creating anamespace
from the java package name (like java:com.ventaso.external.common) for
xml
mapping
of user defined java classes. Is there a way to change this to name
space
I want
? Specifying the targetnamespace doesn't seem to help.
Thanks,
Siva

Similar Messages

What is SAP name space for different objects.

Hi Guys,
Kindly let me know the SAP name spaces for different objects.
Thanks

hi,
Naming Conventions in ABAP Objects
Global classes and interfaces that you create in the Class Builder are stored in the class library and administered by the R/3 Repository: they therefore have the same namespace as all other Repository objects (database tables, structures, data elements, and so on).
It is therefore necessary to have naming conventions for object types and their components and to use them uniformly within program development.
The following naming convention has been conceived for use within the SAP namespace:
If you do not observe the naming conventions for object types (classes and interfaces), conflicts will occur when the system creates persistent classes, since it will be unable to generate the necessary co-classes.
Namespace for Components
A single namespace within a class is shared by:
All components of the class itself (attributes, methods, events, constructors, interfaces, internal data types in the class, and aliases)
All public and protected components of the superclasses of the class.
Method implementation has a local namespace. The names of the local variables can obscure those of class components.
Naming Convention
The naming convention has been kept as general as possible to avoid adversely influencing the naming of objects.
General Remarks
When you choose names for development objects, you should:
Use English names
Use glossary terms when possible
For example, CL_COMPANY_CODE instead of BUKRS
In compound names, use the underscore character (_) as a separator. Since names are not case-sensitive, this is the only character that you can use to separate names.
Example: CL_COMPANY_CODE, CL_GENERAL_LEDGER_ACCOUNT
Names should describe the action, not the implementation of the action.
Example: PRINT_RECTANGLE, not RECTANGLE_TO_SPOOL
Conventions for Object Types
Class and interface names in the class library belong to the same namespace as data elements, tables, structures, and types. They are maintained centrally in table TADIR.
Class in the class library
CL_<class name>
The class name should be made up of singular nouns.
CL_COMPANY_CODE, CL_GENERAL_LEDGER_ACCOUNT
Interfaces in the class library
IF_<interface name>
The same naming convention applies to interfaces as to classes.
IF_STATUS_MANAGEMANT, IF_CHECKER
Local classes in programs
(recommendation)
LCL_<class name>
The class name should be made up of singular nouns.
LCL_TREE_MANAGEMENT
Local interfaces in programs
(recommendation)
LIF_<interface name>
The sane naming convention applies to interfaces as to classes.
LIF_PRINTER
Recommended naming conventions are not compulsory. However, if you use prefixes for these class and interface names, you should use those listed above.
Conventions for Components
Method name
<method name>
Method names should begin with a verb:
GET_STATUS, CREATE_ORDER, DETERMINE_PRICE
Events
<event name>
Event names should have the form
<noun>_<participle>:
BUTTON_PUSHED, COMPANY_CODE_CHANGED, BUSINESS_PARTNER_PRINTED
Local type definitions within a class
(recommendation)
TY_<type name>
TY_INTERNAL_TYPE, TY_TREE_LIST
Data definitions (variables)
<variable name>
When you name variables within a class (CLASS-DATA or DATA), avoid using verbs at the beginning of the name (to avoid conflicts with method names).
LINE_COUNT, MARK_PRINTED, MARK_CHANGED, STATUS
Data definitions (constants)
(recommendation)
CO_<constant name>
CO_MAX_LINE, CO_DEFAULT_STATUS, CO_DEFAULT_WIDTH, CO_MAX_ROWS
Recommended naming conventions are not compulsory. However, if you use prefixes for these class and interface names, you should use those listed above..
Concrete Method Descriptions
Attribute access
SET_<attribute name>, GET_<attribute name>
Methods that access attributes of any kind should be prefaced with GET_ or SET_.
GET_STATUS, SET_USE_COUNT
Event handler methods
ON_<event name>
Methods that handle events should begin with ON, followed by the name of the event that they handle.
ON_BUTTON_PUSHED, ON_BUSINESS_PARTNER_PRINTED
Methods that perform type conversions
AS_<new type>
AS_STRING, AS_ISOCODE
Methods that return a Boolean value
These methods may not return any exceptions.
Recommendation: Use SPACE and 'X' to represent false and true respectively.
IS_<adjective>
IS_OPEN, IS_EMPTY, IS_ACTIVE
Check methods
CHECK_<objective>
CHECK_AUTHORIZATION, CHECK_PROCESS_DATE
Local Conventions Within Methods
For parameters
The parameters are regarded from the point of view of the method that implements them:
IMPORTING parameters
IM_<parameter name>
EXPORTING parameters
EX_<parameter name>
CHANGING parameters
CH_<parameter name>
RESULT
RE_<result>
Using prefixes is NOT compulsory. However, if you do use them, use those listed above.
For exceptions
The following table contains a series of possible exception names, that can also be used generically (for example, NOT_FOUND could also be used as DATE_NOT_FOUND)
EXCEPTION
Meaning
ACTION_NOT_SUPPORTED
The requested action or function code is not supported.
CANCELLED
If a method uses a dialog to find out what has to be dome (for example, a list of choices), and the user chooses "Cancel", you can set this exception.
EXISTING
A new object that you want to create already exists in the database.
FAILED
The method could not be executed because of the current environment. This exception is intended for cases where the method cannot be executed because of variable system circumstances.
..._FAILED
Part of the method could not be completed because of the current environment. (OPEN_FAILED, CLOSE_FAILED, SELECTION_FAILED, AUTHORIZATION_FAILED)
FOREIGN_LOCK
Data is locked by another user.
INCONSISTENT
Object data in the database is inconsistent.
..._INCONSISTENT
The component data for of an object in the database is inconsistent.
INVALID
The object data entered is incorrect (for example, company code does not exist). Compare NOT_QUALIFIED.
..._INVALID
The component data entered for an object is incorrect. Compare NOT_QUALIFIED.
INTERNAL_ERROR
Last resort. Only use this exception if you cannot be more precise about the nature of the error.
NOT_AUTHORIZED
The user does not have the required authorization.
NOT_CUSTOMIZED
The object requested is not correctly customized.
..._NOT_CUSTOMIZED
The component of the requested object is not correctly customized.
NOT_FOUND
Unable to find the requested object.
..._NOT_FOUND
Unable to find component of the requested object.
NOT_QUALIFIED
The combination of input parameters is insufficient to run the method. Compare INVALID.
..._NOT_QUALIFIED
One parameter of the method is not qualified.
NUMBER_ERROR
Error assigning a number.
SYSTEM_ERROR
This exception is set if the Basis system returns an unexpected error message.
regards,
sudheer.

How to create an extension for generated type idoc

Hi all,
Can u please look into this
How to create an extension for generated type idoc ? for example Idoc type BATMAS02

Enter transaction WE30 (ALE->Extension-> IDOC types->Maintain Idoc type)
- Type in your name of the extended IDOC type (usually starting with 'Z') and click on the Basic IDoc type, click the create icon.
- Click on Create new and enter a description and press enter.
- Click on ZIDOCTYPE01 and then on the Create icon.
- Enter ZIDOCTYPE as the segment type, click on Segment Editor.
- Enter a description for your segment type and create.
- Enter a description for your segment, enter each field required in your IDoc and press enter to validate.
- Save and generate, press back
- To release the segment choose Goto, Release from the menu.
- Check the box on the line of your segment.
- Save, back and enter.
- Your Idoc type structure should be displayed with your new segment.
- Save and back.
- To release the Idoc type choose Extras, Release type from the menu and Yes.
ALE FUNCTION MODULE ENHANCEMENTS
Having extended the IDOC type to contain additional fields for an inbound or outbound application, you now want to enhance ALE function modules for populating the additional segment on the outbound or applying the additional segment data on the inbound application.
The core working code for ALE processes for a given application area is always encapsulated in ABAP/4 function modules. These function modules are associated with such control information as message types and process codes. So the ALE process checks this control information and derives the name of the function module to invoke for that particular IDOC processing from certain database tables. These function modules contain objects known as customer functions, which can be considered SAP Enhanced user exits. A function module is called at a particular point during the processing of the main program or function module, and it can be used to influence data processing at that point by adding code to the customer function. The customer function behaves like a normal function module and has import and export parameters, tables (internal tables) statement, and exception processing. Unlike a conventional user exit, customer functions give you the ability to modify only data available to you by the function moduleâs parameters and internal tables. While most ALE/EDI function modules are supported by customer functions, there are ALE/EDI processes that still use conventional user exits. There are a few ways to determine which function module to enhance for a given message type/process code:
For master data distribution, from SALE go to Extensions -> Master data distribution -> Setup additional data for message types. Search for message type DEBMAS in this example. You see an entry for DEBMAS associated with function module MASTERIDOC_CREATE_SMD_DEBMAS. This data is stored on table TBDME. The function module names for all master data message types follow this pattern: MASTERIDOC_CREATE_SMD_messagetype. This function module calls another function module of name MASTERIDOC_CREATE_DEBMAS or MASTERIDOC_CREATE_messagetype. Search for the words customer function, and you find several hits that can be used to add code to the function module.
From WEDI got to Control -> Inbound process codes -> Inbound with ALE service -> Processing by function module (transaction WE42), or from WEDI go to Control -> Outbound process codes -> Outbound with ALE service -> With function module (transaction WE41). There will be function modules associated with the process codes. For inbound, the function modules usually follow this pattern: IDOC_INPUT_messagetype: for example, IDOC_INPUT_CHRMAS for inbound characteristics master.
Use transaction WE57 or from WEDI go to Development -> Message/Application Object. The entries list the function module, Business Object, message type, and IDOC type that are used for inbound ALE/EDI interfaces.
Customer functions are not specific only to ALE and EDI but also to all programs/modules in SAP R/3. Customer function is a SAP enhancement component; the other two types are menu and screen enhancements.
All customer function exits are maintained in SAP enhancements and are found by using transaction SMOD. After executing transaction SMOD, pull down (F4) on the enhancement name field, and execute again. This provides you with a list of all SAP enhancements available. SAP enhancements are grouped by development class pertaining to an application area. Choose Application development R/3 SD master data distribution for development class VSV to lead to a screen that lists VSV00001 as an enhancement (see Figure 5). Press Component +/- to display its function exit components. There are four possible components listed, all of which are function exits (and are function modules) that are called from the ALE function modules in the form Call Customer Function Î001â. This is a special occurrence of the ABAP statement Call. Go to item Exit_SAPLVV01_ 001, which you need to enhance for the Customer Master outbound example of an IDOC extension. In the ALE-function module MASTERIDOC_CREATE_DEBMAS, the statement CALL Customer Function 001 is translated in the background to call component EXIT_SAPLVV01_001. Although this function exit can be edited using transaction SE37, you will use a simpler approach.
When you use SAP enhancements and their components, you manage them with an SAP object known as a project, which is like an envelope containing the selected enhancements and their components. A project can be used to control the execution of components and to transport them to other clients and instances in SAP. Basically, the process involves creating a project, including enhancements and components that are to be enhanced, editing the components, and then activating the project. The following process creates a project for our example Customer Master IDOC extension:
Execute transaction CMOD.
Enter name of project, say CSTMAST1.
Click on Create.
Enter a description of the project.
Save.
Click on SAP Enhancements.
Enter VSV00001 for Enhancement.
Save.
Once youâve created the project, edit the function exit components and activate the project. Remember that the code in the function exit enhancement will execute only if the project is activated. In fact, this is a convenient SAP enhancements feature, whereby the work in progress (developing code in the customer function) will not affect users of that application. When the code is completed, the project can be activated so the enhanced functionality takes effect. It can also be deactivated for maintenance.
As mentioned earlier, customer functions (function exits) are embedded in ALE function modules and can be used to influence the creation and modification of IDOC data on an outbound application or to post additional or modified IDOC data to an inbound R/3 application. Function exits are similar to regular function modules, with import/export parameters, tables (internal tables), and exceptions.
The two important factors to consider while developing the customer function are:
1. The point in the ALE function module where the function exit occurs
2. The data made available by the customer function that can be modified or posted to the R/3 application, based on the direction.
Because some function modules have several customer functions, it is critical to choose the function exit best suited for that particular enhancement. Do not attempt to perform activities that the function exit is not designed for. The importance of this point is illustrated by the following description of enhancing function modules for outbound and inbound ALE interfaces.
Outbound interfaces. In an outbound ALE interface you use function exits (customer functions) to populate additional segments created by an IDOC extension or to modify the existing IDOC data segments as per business requirements. Previously, you identified that enhancement VSV00001 has a component EXIT_SAPLVV01_001 (function exit), which can be used for populating the additional data segment Z1SADRX that you created in the IDOC extension ZDEBMASX (IDOC type ZDEBMASZ, based on Basic IDOC type DEBMAS02). You also learned that the ALE function module that calls this function exit is MASTERIDOC_CREATE_DEBMAS, which has a statement Call Customer Function 001.
Browse the function module MASTERIDOC_CREATE_DEBMAS using transaction SE37. You will find that this customer function is invoked for every segment of IDOC type DEBMAS02. In fact, the function exit is called soon after the creation of an existing segment has been populated with data and appended to the IDOC data table (internal table). Also, the function exit is exporting the message type, IDOC type, and the segment name and is importing the IDOC extension type. It is also passing the IDOC data internal table. This indicates that the ALE function module is allowing you to populate additional segments for every existing segment and modify the existing segmentâs data.
Letâs write ABAP/4 code to accomplish the task of populating IDOC segment Z1SADRX with a contact personâs business address:
From SE37, display function module MASTERIDOC_CREATE_ DEBMAS.
Find Customer Function 001.
Double-click on 001.
The function EXIT_SAPLVV01_001 will be displayed.
Double-click on INCLUDE ZXVSVU01.
You will be asked to create a new include object. Proceed as desired.
Enter code (as in Listing 1).
Be sure to perform a main program check (Function Module -> Check -> main program) and extended program check (Function module -> Check -> Extended check).
Now that you have extended the IDOC and enhanced the ALE function module based on the requirements for the contact personâs business address on the Customer Master, letâs test the interface. You should create a logical system and define a port for this interface. You should also configure the Customer Distribution Model to indicate that message type DEBMAS is being distributed to this logical system. The only difference in configuration between a regular outbound ALE interface and an enhanced one is the partner profile definition. While maintaining the outbound parameters of the partner profile, make sure the IDOC type is ZDEBMASZ. The fields for Basic IDOC type and extension type are automatically populated with DEBMAS02 and ZDEBMASX, respectively.
To maintain the contact personâs business address of a customer:
Use transaction BD12 or from BALE go to Master Data ->Customer -> Send and send that Customer Master record by executing the transaction after filling in the relevant fields such as customer number, message type, and logical system.
Use transaction WE02 or WE05 to verify the IDOC created. You should see the new segment Z1SADRX populated with the correct data.
With SAP releases below 4.5B, you cannot capture changes to business address through change pointers because a change document object is not available for capturing business address changes, and also earlier releases have not been configured to write change documents for a contact personâs business address. If you would like this functionality, you can either create change document objects, generate function modules to create change documents, and perform ALE configuration to tie it in, or make a cosmetic change to the contact person screen data while changing the contact personâs business address so that it gets captured as a change to the Customer Master. Subsequently, the ALE enhancement that you performed captures the contact personâs business address.
Inbound interfaces. The process for enhancing inbound ALE interfaces is similar for outbound, with a few exceptions; specifically in the coding of customer functions (function exits) for the ALE/EDI function modules.
The first step is to create an IDOC extension for the specific Basic IDOC type by adding new segments at the appropriate hierarchy level: that is, associated to the relevant existing segment. Populate the data fields on the new segments with application data by the translator or external system/program before importing them into the R/3 System. Then, find the ALE function module that is invoked by the inbound processing. By browsing through the code or reading the documentation on the function exit enhancements using the SMOD transaction, identify the function exit in which you should place your code. The technique used in the code to post the additional or modified IDOC data to the application can vary based on the application rules and requirements, the data available at that point in processing, and the application function modules available to update the application tables. It is important to search first for application modules that process the data and see if they can be called within the function exit. If the additional data in the extended segments in specific to a custom table or resides in nonkey fields of a single or small set of tables, you may be able to update it directly by SQL statements in the function exit. This approach should be carefully evaluated and is certainly not highly recommended.
Another option is to use Call Transaction from within the function exit to process the additional data. For example, in the case of message type WMMBXY for inbound goods movements from a warehouse management system, the standard interface creates batches for materials, but does not update its characteristics. In such a case, you can use Call Transaction MSC1 to create the batch and assign characteristic values to it from within the function exit provided.
regards,
srinivas

Hide name space of generated xml from xml bean

Hi,
how can i hide the namespace of the generated xml from xml bean, cause im having problems with jaxb parses.

The targetNamespace is for webservice and not for the user defined classes.
Sorry for the confusion
Ajay
"Ajay" <[email protected]> wrote in message
news:[email protected]..
There is a targetNamespace attribute in the autotyp ant task. But there
was a bug in 8.1. Contact the support for a patch.
The following mail explains that
This looks like a bug. There is an undocument, not officially
supported workaround: add the following java doc
to yours source code -
* @wlws:webservice targetNamespace="http://foo.bar"
public class MyService {
Details here:
http://www.manojc.com/tutorial/sample3/source2wsdd.html
Regards,
-manoj
http://manojc.com
"Mark Fine" <[email protected]> wrote in message
news:[email protected]..
The attribute targetNamespace (of the autotype task) doesn't seem to putany
information into the types file and later my deployment descriptor (viathe
source2wsdd task) contains an invalid targetNamespace attribute with a
http://tempuri.org:
eg.
<web-services>
<web-service name="IndexService"
targetNamespace="http://tempuri.org/"
uri="/IndexWebService">
I don't think this causes any problems but there should be a way tospecify
the namespace.
Has anyone else seen this is WLS8.1?
"Siva" <[email protected]> wrote in message
news:[email protected]..
By default the autotype or the servicegen ant task seem to be creating anamespace
from the java package name (like java:com.ventaso.external.common) for
xml
mapping
of user defined java classes. Is there a way to change this to name
space
I want
? Specifying the targetnamespace doesn't seem to help.
Thanks,
Siva

Xml name space issue

Hi,
My xsd starts like this
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
And my expected output is
<Rootelement xmlns:xsi="http://www.w3.org/2001/XMLSchema" xsi:noNamespaceSchemaLocation="myxsd_v1.0.xsd">
but currently my output is
<Rootelement>
How to acheive my required output. I tried using xml anonymiser bean with accept namespaces as http://www.w3.org/2001/XMLSchema ''
and anonymiser quote as '
Anonymiser bean is above callsapadapter
But still the output is not differing . how to get my expetecd output??

Hi,
For the target structure, try to use the External Definition.
or
In the Message type , please remove the namespace.....
Hope this will solve your isssue...
Regards,
Jude.

Java mapping - XML name space

Hi experts,
I doing a java mapping to meet my requirement. I use the following code to produce the target XML
String transactionId = ........................................
            DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
            DocumentBuilder builder = factory.newDocumentBuilder();
//               Create the output DOM
            Document docOut = builder.newDocument();
            Element dashboardInputTypeNode = docOut.createElement("dashboardInputType");
            docOut.appendChild(dashboardInputTypeNode);
           Element transactionIdNode = docOut.createElement(transactionId);
            dashboardInputTypeNode.appendChild(transactionIdNode);
            Text transactionIdText = docOut.createTextNode("transactionId");
            transactionIdNode.appendChild(transactionIdText);
           // transform the new xml to the output stream
            TransformerFactory tf = TransformerFactory.newInstance();
            Transformer transform = tf.newTransformer();
            transform.transform(new DOMSource(docOut), new StreamResult(out));
This code produces me the following XML
<?xml version="1.0" encoding="UTF-8" ?>
<dashboardInputType>
      <transactionId>transactionId</transactionId>
</dashboardInputType>
But, I need the XML to be produced with the following namespace
<?xml version="1.0" encoding="UTF-8" ?>
<ns1:dashboardInputType xmlns:ns1="http://www.watercorporation.com.au/dashboard">
      <ns1:transactionId>transactionId</ns1:transactionId>
</ns1:dashboardInputType>
what changes do I need to make in my code to get tge desired output?
Reward points for the right answer or doco.
Thanx heaps....
Sabbir

try this .
docOut.setAttributeNS("http://www.w3.org/2000/xmlns/","xmlns:ns1","http://www.watercorporation.com.au/dashboard"");

NAME SPACE CHANGING

Hi ,
i want to change the existed namespace .. is it possible to change the existed name space..because after created all the scenarios we got a new requirement to change the new name space for all the scenarios..
can any body tell the steps for changing the namespaces..
thanks
babu

Babu,
In my project also we have faced same problem.after developing almost objects of a interface..clients asked 4 the namespace change. thats the problem...with XI and PI...i dont know wheather PI 7.1 will having the option to copy whole namespace.....We have found the only possibility is to create a new namespace .And manually copy all the objects...into the new namespace...
u can copy directly Message interfaces...(u need not copy data type and Message type) <b>and remember to check the option "With all dependency"</b>..
then automatically data type and Message type will be copied...
u can't copy Interface mapping and Message mapping :(..
u have to do it agian.......
Regards
Biplab

Name Space in Webservice Response is not parsed in BI Publisher

Hi,
I have built the report in BI Publisher with Data Source as Web Service by giving WSDL URL and method Name. I have got the response for the method call, but it has name space for all tag elements. Like
<ns:FirstName>Daniel</ns:FirstName>
<ns:LastName>Victor</ns:LastName>
My report template unable to pick the value from tags as it is taking Name Space also as tag name. It is not parsing name spaces. I tried another report by keeping file as my report source, just by removing the name spaces from the WSDL response message, it worked.
How do I make BI Publisher to parse the name space, such that WSDL response can be utilized as such?
Edited by: [email protected] on Mar 4, 2009 2:58 PM

Hi,
Did you follow all the steps in the Install guide:
http://download.oracle.com/docs/cd/E12844_01/doc/bip.1013/e12690/T434820T487784.htm
Regards,

Can not generate one xsd file for message type in xi

Dear Experts.
I am not able to generate one XSD file from message type from XI 3.0, When i select message type and go to XSD tab then click on export xsd to file, it is generating two xsd files MainSchema.xsd, Schema1.xsd into one zip file, but i need only one xsd file to import it into MDM.
Could you please help
Thanks and Regards.
Sravya.
The following are the two files. MainSchema.xsd, Schema1.xsd .

Hi Harsha,
Thanks lot for the immediate response. Appreciate it.
Now I am able to generate the one xsd with your inputs , but i am not able to load it into mdm with out any changes in the generated XSD from Message Type. the below is only the original root tag, where modification required.
Original Element : MDM_CUST_MASTER_FILE_REQUEST_MT
==============
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:abc.com:MDM_Customer_Master_ECC" targetNamespace="urn:abc.com:MDM_Customer_Master_ECC">
<xsd:element name="MDM_CUST_MASTER_FILE_REQUEST_MT" type="MDM_CUST_MASTER_FILE_REQUEST_DT" />
etc.
Case :.When i modify the above element as below with out xmlns, targetNamespace
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="MDM_CUST_MASTER_FILE_REQUEST_MT" type="MDM_CUST_MASTER_FILE_REQUEST_DT" />
I can import xsd into mdm with the above modification.
The generated XML out put File from mdm is having message type tag like below
?xml version="1.0" encoding="UTF-8"?>
<MDM_CUST_MASTER_FILE_REQUEST_MT>
<CUSTOMER> </customer> ...
note: no namespace for message type
Result:
1.When i send this xml file into XI it is failing in message mapping because it doesn't have namespace attached to it and failing in message mapping.
Finally i need your help to generate the xsd or data file like below to avoid mapping problem in xi.
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MDM_CUST_MASTER_FILE_REQUEST_MT xmlns:ns0=urn:abc.com:MDM_Customer_Master_ECC>
Appreciate your help.
Thanks and Regards.
Sravya.

Inbound IDOC error (Name MARA is not in the namespace for generated BW Metaobjects)

Hi everybody,
we are currently having some issues with importing idocs into our ERP DEV System and i cannot figure out what the problem could be.
I am trying to import an IDOC Type ARTMAS (5) but i keep getting the following error "Name MARA is not in the namespace for generated BW Metaobjects"
The system is a ERP only system with no BI content activated at all.
I don´t find any more errors nor any dumps or SLG1 entries related to this issue.
Did someone already experienced that kind of problem, or do some of you maybe have an idea where to have a deeper look.
thanks & best regards
Peter
EDIT:
Running on ERP 6.0 EHP 7 SPS 4

Hi Ganesh,
I guess there is something wrong with the data in the ODS.
Check this post:
Re: error 18 in the update!
Bye
Dinesh

BPEL - not generating correct SOAP packet for complex types

Hi,
Below is a snippet from wsdl, correct SOAP request and reply packet (generated using a SOAP test tool) and finally BPEL generated SOAP request and error response (captured using TCP packet monitor)
The problem is with element 'XActivationPackageArray', which is getting enclosed
by itself again from Oracle BPEL PM.
------------------------W S D L S T A R T----------------------------------------------------
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" .......>
     <types>
          <schema>
               <complexType name="XActivationPackageArray">
                    <sequence>
                         <element name="XActivationPackage" type="tns2:XActivationPackage" maxOccurs="unbounded"/>
                    </sequence>
               </complexType>
               <element name="XActivationPackageArray" type="tns2:XActivationPackageArray"/>
               <complexType name="XActivationPackage">
                    <sequence>
                         <element name="activationPackage" nillable="true" type="xsd:string"/>
                    </sequence>
               </complexType>
               <complexType name="XActivationResponse">
                    <sequence>
                         <element name="unitId" nillable="true" type="xsd:string"/>
                         <element name="serviceId" nillable="true" type="xsd:string"/>
                    </sequence>
               </complexType>
               <element name="XActivationResponse" type="tns2:XActivationResponse"/>
          </schema>
     </types>
     <message name="activateServiceRequest">
          <part name="userId" type="xsd:string"/>
          <part name="companyCd" type="xsd:string"/>
          <part name="customerCd" type="xsd:string"/>
          <part name="stockAccountId" type="xsd:string"/>
          <part name="orderNumber" type="xsd:string"/>
          <part name="serviceType" type="xsd:string"/>
          <part name="location" type="xsd:string"/>
          <part name="unitId" type="xsd:string"/>
          <part name="serviceIdPool" type="xsd:string"/>
          <part name="serviceId" type="xsd:string"/>
          <part name="XActivationPackageArray" element="tns2:XActivationPackageArray"/>
     </message>
     <message name="activateServiceResponse">
          <part name="XActivationResponse" element="tns2:XActivationResponse"/>
     </message>
</definitions>
------------------------W S D L E N D----------------------------------------------------
------------------------Correct SOAP packet ----------------------------------------------------
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:sf2pwrapper.ws.sf2.p1.com">
<soapenv:Body>
<urn:activateService>
<userId>XYZ</userId>
<companyCd>999</companyCd>
<customerCd>ABCDE</customerCd>
<stockAccountId>FGHIJ</stockAccountId>
<orderNumber>888999</orderNumber>
<serviceType>AA</serviceType>
<location>A</location>
<unitId/>
<serviceIdPool>XXX</serviceIdPool>
<serviceId/>
<XActivationPackageArray>
               <XActivationPackage>
                    <activationPackage>MMGG</activationPackage>
               </XActivationPackage>
</XActivationPackageArray>
</urn:activateService>
</soapenv:Body>
</soapenv:Envelope>
------------------------Correct reply ----------------------------------------------------
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<activateServiceResponse xmlns="urn:sf2pwrapper.ws.sf2.p1.com">
<ns1:XActivationResponse xmlns:ns1="urn:model.sf2pwrapper.ws.sf2.p1.com">
<unitId xmlns="">0642342</unitId>
<serviceId xmlns="">83753710</serviceId>
</ns1:XActivationResponse>
</activateServiceResponse>
</soapenv:Body>
</soapenv:Envelope>
------------------------BPEL generated SOAP packet--------------------------------------------------
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<ns1:activateService soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="urn:sf2pwrapper.ws.sf2.p1.com">
<userId xmlns:def="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="def:string">XYZ</userId>
<companyCd xmlns:def="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="def:string">999</companyCd>
<customerCd xmlns:def="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="def:string">ABCDE</customerCd>
<stockAccountId xmlns:def="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="def:string">FGHIJ</stockAccountId>
<orderNumber xmlns:def="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="def:string">888999</orderNumber>
<serviceType xmlns:def="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="def:string">AA</serviceType>
<location xmlns:def="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="def:string">A</location>
<unitId xmlns:def="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="def:string"></unitId>
<serviceIdPool xmlns:def="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="def:string">XXX</serviceIdPool>
<serviceId xmlns:def="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="def:string"></serviceId>
<XActivationPackageArray>
<XActivationPackageArray xmlns="urn:model.sf2pwrapper.ws.sf2.p1.com">
<XActivationPackage xmlns="">
<activationPackage>MMGG</activationPackage>
</XActivationPackage>
</XActivationPackageArray>
</XActivationPackageArray>
</ns1:activateService>
</soapenv:Body>
</soapenv:Envelope>
------------------------BPEL error--------------------------------------------------
<?xml version="1.0" encoding="utf-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server.userException</faultcode>
<faultstring>org.xml.sax.SAXException: Invalid element in com.p1.sf2.ws.sf2pwrapper.model.XActivationPackage - XActivationPackage</faultstring>
<detail>
<ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">c7g7mrs</ns1:hostname>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>

t

Example of storing a prefix name space xml file in XML DB ?

I have lots of XML file pass to me with prefix name space all over the file. Is there any example of how to stored and retrieved this type of XML file to XML DB?
Example of the XML file:
<?xml version="1.0" encoding="UTF-8"?>
<ddms:Resource xmlns:ddms="http://metadata.dod.mil/mdr/ns/DDMS/1.3/" xmlns:ICISM="http://metadata.dod.mil/mdr/ns/DDMS/1.3"
     xmlns:gml="http://metadata.dod.mil/mdr/ns/DDMS/1.3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://metadata.dod.mil/mdr/ns/DDMS/1.3/ ../DDMS-v1_3_1033.xsd">
<ddms:identifier ddms:qualifier="http://metadata.dod.mil/mdr/ns/MDR/0.1/MDR.owl#URI"
          ddms:value="http://www.whitehouse.gov/news/releases/2005/06/20050621.html"/>
</ddms:Resource>

Hi
What is the error you get if you try to load the file ?
May be you have to change the schema location of the xsd to an absolute path in your exable it is relative
xsi:schemaLocation="http://metadata.dod.mil/mdr/ns/DDMS/1.3/ ../DDMS-v1_3_1033.xsd"
regards Patrick

Generate xml source file for Oracle Order Capture Print Quote

Hi,
I am new to xml and need to work on creating templates for Print Quote.
I am trying to generate the xml source file for which I enabled the report in system administrator and set the output to XML and assigned to Quoting Reports responsiblity. I then assigned XML Report Publisher to the same responsiblity.
I ran the report (Print Quote) and then I am trying to run the XML Report Publisher but I cannot get the request id in the list of values.
I am able to generate xml source file for other reports like Printed Purchase Order etc.,
The view output for the (Print Quote) report is as follows:
<?xml version="1.0" ?>
- 
<ASOPQTER />
How do I get the xml source file? Or are there seeded templates that I can use to create more templates? Any help would be appreciated. Thanks Ravi

Hi, I am in the same position - did this issue ever ger resolved by anyone. I have done a few XMLP reports successfully now using the Word add-in, but customising the Quote output differs from other standard reports.
If you look at the data definition for Quote it is a 'dummy' definition and has no XML file attached. Does anyone know how I can get the XML format for the report output?
Also the template uses XSL-FO ?!?!?! rather than RTF - not sure how to work with this, the Oracle docs are not very helpful in this regard either.
Has anyone successfully managed to customise the Quote print report? Many thanks,
Roger

Error message in WAD: "No name is specified for modification type 'Module'"

Hi All,
We have created a WAD template with one analysis item and a button and have single module of type generic module in it.
While executing it following error message is displayed "No name is specified for modification type 'Module'"
Please Can anyone help with this error.
Regards,
Shweta.

Hello,
I am currently facing same issue and I have no idea how to get rid of this message on top of the page.
I'm pretty sure that this error message comes from the ANALYSIS_ITEM define in my Web Template but I have defined alias name for the different modules I created:
Who is able to help ?

Goods Receipt PO (Service Type) for generate accruals

Hi,
Just wonder that Service type of Goods Receipt PO possible write to the G/L or not? for item type of Goods Receipt PO, it can generated accruals.
I want to generate accruals by Goods Receipt PO., else how am i going to generate accruals?
Thanks.
Regards,
Danny

Subject is discussed in this link with no answer
Generating Accruals from Service type Goods Receipt PO's

Xml name space for generated types

Similar Messages

Maybe you are looking for