Creating RosettaNet data types in XI 2.0: 'xml:lang' attribute

Has anybody successfully created a RosettaNet interface in XI 2.0?
I am working with the PIP 3A2 messages, but some of the elements have an attribute named 'xml:lang', which is a standardized attribute from the W3C's XML namespace. The attribute name is declared as 'xml:lang' because it's still a DTD-based PIP. Normally, in schema, this is handled by declaring an import of the xml.xsd file provided by W3C and defining the namespace alias 'xml' to point to it in the RosettaNet schema. The xml.xsd provided by W3C boils down to the following declaration, to support 'xml:lang' as an attribute...
<xs:schema targetNamespace="http://www.w3.org/XML/1998/namespace" xmlns:xs="http://www.w3.org/2001/XMLSchema" xml:lang="en">
<xs:attribute name="lang" type="xs:language">
</xs:attribute>
</xs:schema>
I'm trying to create this interface in the XI 2.0 data type editor, but...
1. I can't create attributes as standalone data types in alternate namespaces (to simulate the declarations in W3C's xml.xsd).
2. I can't link a standalone attribute declaration from another namespace to an attribute in the editor.
3. The editor prohibits use of a colon in the attribute name (as it should), so I can't declare the attribute name to be 'xml:lang'.
4. I can't figure out how to control the addition of a new namespace alias to 'xml'. The editor wants to use default names like 'p0' when I bring in types from other namespaces.
Can anyone suggest where I should look for an answer?
--Dan King
Capgemini

Hi Dan,
You can design and Test Rosettanet PIPS Messages in XI-3.0 only.
Regards
Prasad
SAP Netwaver RIG-XI
SAP Labs LLC, USA

Similar Messages

Create dynamic data type in structure

Hi Experts,
I am new to ABAP.
In my scenario data type is varying for the field. for that I need to create dynamic data type in structure, this structure I am using for internal table for OVS search input.
Please suggest the solution for this.
Advance thanks,
Regards,
BBC

Thanks for your quick reply,
I used your logic like this.
data:
ls_component type abap_componentdescr,
lt_component type abap_component_tab.
*... (1) define structure components :
clear ls_component.
ls_component-name = 'NVALUE'.
ls_component-type ?= cl_abap_typedescr=>describe_by_name( <fs_seg_v>-fieldname ).
insert ls_component into table lt_component.
*... (2) create structure
data lr_strucdescr type ref to cl_abap_structdescr.
data lr_data_struc type ref to data.
lr_strucdescr = cl_abap_structdescr=>create( lt_component ).
create data lr_data_struc type handle lr_strucdescr.
field-symbols <fs> TYPE any.
assign lr_data_struc->* to <fs>.
your logic is working fine.
here I am getting feild name (<fs_seg_v>-fieldname) from internal table.
But I need to assign same field name structure to query parameter.
FIELD-SYMBOLS: <ls_query_params> TYPE lty_stru_input.
Please can you suggest how I can refer the field name structure?
Regards,
BBC

How to create the Data Type for the receiver end?

Hello Expertise
I wanted to Create a Data type for Receiver end in PI.
Sender end is ECC.
Receiver end is SRM
Here's the Data type for Sender end as
Can anyone help to create the Data type for Receiver end i.e SRM.
Thanks in advance.
Regards
karan

Hi Karan,
Please don't call Sir, we are just trying to help each other.
Please go through below scenario's and check your configuration.
ABAP Client Proxy to ABAP Server Proxy Scenario - Process Integration - SCN Wiki
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0ac1a33-debf-2c10-45bf-fb19f6e15649?overridelayout=true
http://wiki.scn.sap.com/wiki/display/XI/Step-by-step+FTP+to+ABAP+Proxy
regards,
Harish

Scripting Crash- "Create from Data Type" on Typedef Enum

I just encountered a crash that I can duplicate in both LabVIEW 2013 and 2012 (student).
Attached is a project that contains the code I used on 2012. Run the target VI.
(I can get the project I had in 2013, if needed, sometime next week)
Basic steps:
Create a type def enum
Place it on a VI
Use scripting to get ahold of the Control Terminal and get the data type
"Create from Data Type"

Haha, I saved your code and ran it while I still had another project open... didn't really think that one through. Thank you, Auto-save.
So it looks like the crash happens at the Create node. I can get rid of the crash by removing the Type Def link from the enum.
I'm not at all an expert in scripting and have only used it a few times. Could a workaround be to get a reference to all of the Controls on the FP and copy the Control with the same Label "Enum" (instead of loading the terminal and creaing a new terminal)? Maybe creating a typedef by data type is what's causing the crash, but copying an already existing control will work.

Create Characteristics, Data Type - Currency

Hi All,
I am trying to create characteristics in transaction CT04 for our PO release strategy.
Data type is Currency. After giving all required details when I press enter the value range becomes NNNNNNNNNNNNN.NN. So I am unable to select value in release strategy classification tab.
Does anybody have any idea that why values are getting converted to NNNNNNNNNNNNN.NN.
Is any configuration missing?
Is the problem with template?
Regards
sapmm1234

I have done the following settings:
Charateristrics PO_Value
Valid from Today Date
Decription Total Net Order Value
Status Released
Data Type Currency
Number of Class 15
Decimal Places 2
Currency QAR
Template I ahve not selected anything but defaults it is taking NNNNNNNNNNNNN.NN
Even If I delete this when I press enter It is taking NNNNNNNNNNNNN.NN
Multiple values & Interval Values allowed
Additional Data:
Table CEKKO
Field GNETW
Not Ready for Input Checked
Unformatted Entry Checked
Propose Template is not checked
Values
<= 2500
> 2500
<= 10000
> 10000
After giving this value when I press enter all values becomes
<= NNNNNNNNNNNNN.NN QAR
> NNNNNNNNNNNNN.NN QAR
<= NNNNNNNNNNNNN.NN QAR
>= NNNNNNNNNNNNN.NN QAR
So I could not select any value in RElease strategy --> Classification tab
Any Idea why Value are getting converted into this format.
Regards
sapmm1234

Creating runtime data types

Hi
I need to dynamically create input fields with specified lengths(so that user cannot enter values beyond this length).
I do it like this.
IWDAttributeInfo attributeInfo =
    nodeName
    .getNodeInfo()
    .addAttribute(attributeName,
       "ddic:com.sap.dictionary.string");
IWDInpuField inputField =
   (IWDInpuField)viewHandle
                  .createElement
                  (IWDInputField.class,null);
int length = getLengthFromSomeMethod();
inputField.bindValue(attributeInfo);
inputField.setLength(length);
The input field added is of specified length, but still the user is able to enter value beyond this length. This i guess is due to the fact that attribute bound to the field is of type "ddic:com.sap.dictionary.string".
Can i create data types at runtime so that i might add attributes with this data type to a node at run time?
Is there any other way to solve this problem?

kaushal,
Try this:
attributeInfo.getModifiableSimpleType()
.setMaxLength(length);
"Length" of InputField declares (average) width of control in characters.
VS

Creating own data types

Hi,
How can i create my own data types????
Thanks,
Mohit.

Hi,
Through TYPES statement you can create your own datatypes. And through Type-pools you can create global data.
Re: type pools
Reward if useful!

How to create LOB data type in table?

what is syntax to create LOB type in a table?
Thanks
Yash

can u send me the query for the insert image into the data base plz.................
mail id is
[email protected]
if u know please send me it is urgent to me plzzzzzzzzzzzz................
thanks..............

Can we create java_object data type in oracle procedure

i want to construct java_object like data stucture in oracle procedure, then i have to retrieve the object
via callable statement. is it possible? or any other solutions?

i want to construct java_object like data stucture in
oracle procedure, then i have to retrieve the object
via callable statement. is it possible? No.
or any other
solutions?Of course. Return the data, and construct it in java.

Data type change made to schema.xml of comments list which is part of blog site template is not reflecting in the existing site but working fine when new site is created.

Hi,
I have created a blog site with the available site template few days back. Now we have the requirement of having the attachments in the body of the comments section.
So, I updated the schema.xml of the comments list available under ../templates/blog/lists/comments/schema.xml to have rich text for the Body field.
With this change, I created a new site and it was working fine. Change is reflected in the new blog site.
However, this particular change is not reflected in the existing blog site. Any changes made to the schema.xml is not effecting the old blog site.
Can anyone suggest what can be done for the change to be reflected in the old blog site?
Thanks in Advance,
Regards, Keerthi Suryadevara

Hi,
According to your post, my understanding is that you wanted to add attachments in the body of the comments section.
You can add the the Code inside the Default list pages. For more information, you can refer to:
Enable Attachment in SharePoint Blog post list and display the list Attachments
In addition, you can add an enhanced rich text field to the comment list and remove the body field. Then you can insert files into comments, too.
Here is a similar thread for your reference:
http://sharepoint.stackexchange.com/questions/77194/how-to-add-attachments-for-comments-list-in-sharepoint-blog-2010
Best Regards,
Linda Li
Linda Li
TechNet Community Support

New Effective CAL essay: How do I create an abstract data type in CAL?

How do I create an abstract data type in CAL? An abstract data type is one whose internal representation can be changed without needing to modify the source code of client modules that make use of that type. For software maintainability, it is a good idea to make a type that is subject to change or enhancement into an abstract data type. Another reason to create an abstract data type is to enforce invariants for values of the type that can only be ensured by using constructor functions (i.e. functions that return values of that type). In principle it is simple to create an abstract data type in CAL. For an algebraic data type, make the type constructor public and all data constructors private. For a foreign data type, make the type constructor public and the implementation scope private. If a scope qualifier is omitted, the scope is taken to be private. For example, the Map algebraic data type has the public type constructor Map and the data constructors Tip and Bin are each private, so it is an abstract data type. /** A map from keys (of type {@code k@}) to values (of type {@code a@}). */ data public Map k a = private Tip | private Bin size :: !Int key :: !k value :: a leftMap :: !(Map k a) rightMap :: !(Map k a); There are a number of invariants of this type: the size field represents the number of elements in the map represented by its Bin value. The keys in leftMap are all less than key, which in turn is less than all the keys in rightMap. In particular, non-empty Map values can only be created if the key parameter type is a member of the Ord type class. Values of the Map type can be created outside the Cal.Collections.Map module only by using constructor functions such as insert: insert :: Ord k => k -> a -> Map k a -> Map k a; public insert !key value !map = ... The owner of the Cal.Collections.Map module must ensure that all invariants of the Map type are satisfied, but if this is done, then it will automatically hold for clients using this function. Some examples of foreign abstract data types are Color, StringNoCase and RelativeDate: data foreign unsafe import jvm private "java.awt.Color" public Color; data foreign unsafe import jvm private "java.lang.String" public StringNoCase; data foreign unsafe import jvm private "int" public RelativeDate; The private implementation scope for Color means that a foreign function whose type involves Color can only be declared in the Cal.Graphics.Color module where the Color type is defined. A foreign function declaration involving the Color type relies on the compiler knowing that the Color type corresponds to java.awt.Color to resolve the corresponding Java entity i.e. it must know about the implementation of the Color type. Having a private implementation scope means that the Color type can be changed to correspond to a different Java class, or indeed to be an algebraic type, without the risk of breaking client code. In all these three cases there are useful, and different, design reasons to adopt a private implementation scope: For RelativeDate, the Java implementation type int represents a coded Gregorian date value in the date scheme used by Crystal Reports. Not all int values correspond to valid dates, and the algorithm to map an int to a year/month/day equivalent is fairly complicated, taking into account things like Gregorian calendar reform. Thus, it is desirable to hide the implementation of this type. For StringNoCase, the implementation is more straightforward as a java.lang.String. The reason to adopt a private implementation scope is to ensure that all functions involving StringNoCase preserve the semantics of StringNoCase as representing a case-insensitive string value. Otherwise it is very easy for clients to declare a function such as: foreign unsafe import jvm "method replace" replaceChar :: StringNoCase -> Char -> Char -> StringNoCase; which does not handle case-insensitivity correctly, but is a perfectly valid declaration. This declaration results in a compilation error when it is placed outside the module in which StringNoCase is defined because of the private implementation scope of StringNoCase. For Color, the issue is somewhat more subtle. The java.awt.Color implementation type is semantically the same as the CAL Color type. The problem is that java.awt.Color is mutable (since it can be sub-classed to create a mutable type). It is preferable for a first-class CAL type to not be mutable, so we simply make the implementation scope private to ensure that this will be the case. A somewhat less encapsulated kind of abstract data type can be created using friend modules and protected scope. For example, if an algebraic type is public, and all its data constructors are protected, then the data constructors can be accessed in the friend modules of the module in which the type is defined. Effectively this means that the implementation of the semantics of the type stretches over the module in which the type is defined, and all of its friend modules. These must all be checked if the implementation of the type is modified. Given the merits of abstract data types discussed above, it is perhaps surprising that most of the core types defined in the Prelude module are not abstract data types. For example: Boolean, Char, Int, Double, String, List, Maybe, Either, Ordering, JObject, JList, and all record and tuple types are non-abstract types. There are different reasons for this, depending on the particular type involved. For example, Boolean, List, Maybe, Either and Ordering are all rather canonical algebraic data types with a long history in functional languages, with many standard functions using them. They are thus guaranteed never to change. In addition, their values have no particular design invariants that need to be enforced via constructor functions. Exposing the data constructors gives clients some additional syntactic flexibility in using values of the type. For example, they can pattern match on the values using case expressions or let patterns. Essentially the same explanation holds for record and tuple types. Although non-tuple record types are less canonical, they do correspond to the fundamental notion of an anonymous named-field product type. The "anonymous" here simply means that the programmer can create an entirely new record type simply by creating a value; the type does not have to be declared anywhere prior to use. Char, Int, Double, String, JObject and JList are foreign types where in fact part of the semantics of the type is that we want clients to know that the type is a foreign type. For example, we want clients to know that Prelude.Int is essentially the Java primitive unboxed int type, and has all the semantics you would expect of the Java int type i.e. this is quite different from RelativeDate which is using int as its implementation type in a very tactical way that we may choose to change. One can think of a public foreign type declaration with public implementation scope as simply introducing the Java type into the CAL namespace. One interesting point here is with CAL's naming convention for public foreign types. We prefix a type name by "J" (for "Java") for foreign types with public implementation type such that the underlying Java type is mutable. This is intended as mnemonic that the type is not a pure functional type and thus some caution needs to be taken when using it. For example, Prelude.JObject has public Java implementation type java.lang.Object. In the case where the underlying Java type is not mutable, we do not use the prefix, since even though the type is foreign; it is basically a first class functional type and can be freely used without concern. For example, Prelude.String has public Java implementation type java.lang.String. In the case where the implementation type is private, then the fact that the type is a foreign type, whether mutable or not, is an implementation detail and we do not hint at that detail via the name. Thus Color.Color has as its private Java implementation type the mutable Java type java.awt.Color. When creating abstract data types it is important to not inadvertently supply public API functions that conflict with the desired public semantics of the type. For example, if the type is publicly a pure-functional (i.e. immutable) type such as Color, it is important not to expose functions that mutate the internal Java representation. A more subtle case of inadvertently exposing the implementation of a type can occur with derived instances. For example, deriving the Prelude.Outputable and Prelude.Inputable type classes on a foreign type, whose implementation type is a mutable Java reference type, allows the client to gain access to the underlying Java value and mutate it
(by calling Prelude.output, mutating, and then calling Prelude.input). The solution in this case is to not derive Inputable and Outputable instances, but rather to define a custom Inputable and Outputable instance that copies the underlying values.

Hi Pandra801,
When you create a the external content type, please try to add a filter based on your select statement.
http://arsalkhatri.wordpress.com/2012/01/07/external-list-with-bcs-search-filters-finders/
Or, try to create a stored procedure based on your select statement, then create ECT using the SQL stored procedure.
A step by step guide in designing BCS entities by using a SQL stored procedure
http://blogs.msdn.com/b/sharepointdev/archive/2011/02/10/173-a-step-by-step-guide-in-designing-bcs-entities-by-using-a-sql-stored-procedure.aspx
I hope this helps.
Thanks,
Wendy
Wendy Li
TechNet Community Support

How to do create data type for coulmn name as QS$FGD .

hi ,
In my database i have a column as QS$FGD.
How do i map it in XI , since $ is not accepted when u create a data type.
One way is to give alias at the databse level for the column . is there any other way to slove it .
Thanks
amit

Hi Amit,
Were you able to solve your issue? I'm facing the similar issue now. My DB table contains field names with '.' i.e. say xyz.abc. How to solve this??
I feel SP could be an alternative??
Thanks,
Hussain.

Error while creating data type

Hi
I am creating data type for the scenario from File to IDOC
Namespace urn:xiworkshop:groupxx:legacy is not defined in the software component version NEWPRODUCT , 100 of sap Object Message Type Vendor | urn:xiworkshop:groupxx:legacy references the inactive object Data Type Vendor | urn:xiworkshop:groupxx:legacy
Please help me

Hi;
First activate your namespace and then create the data type.
Namespace + default datatypes should be activated together.
Then your data type
Mudit

Import XSD to create Data type in Design

hi,
I know that we can import XSD in Design and create data type,my question is:
1. Can i import an XSD thats been created in message mapping and use that to create my data type in design.
(or)
2.Should i have to write an XSD on my own and then import it to create my data type, and is there any standard format to write it.

Hello Prashanth,
For your first question: i don't know exactly what you mean that the the xsd you create in the data mapping steps. So can you explain it in details?
For your 2nd question: Sure you can write your own XSD to create a data type. And i will give you an example xsd file format. Then you can import it in the XSD tab view.
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://sap.com/xi/XI/hansteel" targetNamespace="http://sap.com/xi/XI/hansteel">
 <xsd:complexType name="CustomerInfo">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 a6c26c80000f11dac45e00096b1669b3
 </xsd:appinfo>
 </xsd:annotation>
 <xsd:sequence>
 <xsd:element name="ID">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 dfe699c0e7bc11d9c736d51c0a0013e1
 </xsd:appinfo>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:length value="10" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="NAME">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 dfe82060e7bc11d9b2efd51c0a0013e1
 </xsd:appinfo>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:length value="35" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="CUSTTYPE">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 dfe82061e7bc11d9c193d51c0a0013e1
 </xsd:appinfo>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:length value="4" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="POSTCODE">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 e93039a0e7bc11d9c7c6d51c0a0013e1
 </xsd:appinfo>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:length value="10" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="CITY">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 f0122850e7bc11d99189d51c0a0013e1
 </xsd:appinfo>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:length value="35" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 </xsd:sequence>
 </xsd:complexType>
</xsd:schema>
Hope this will be helpful.
Eric Ma

Can't use Data type created with External Definition

Hi,
In the repository, I would like to transport a very complexe DataType from one XI system to an other one. As I don't want to spend a week to create data types, I created a new External Definitions and loaded my XSD schema (that I exported as XSD from Source system) with Messages parameter set to "From All Available Global Elements". I don't set the "Source". I can see the "Imported Document" and "WSDL", but the Messages and External References tabs are empty. Furthermore, I can't use my new message type in a Outbound Asyncrhronous Message Interface.
Here is a very small XSD file that I use to test my scenario.
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://veilleux.1" targetNamespace="http://veilleux.1">
 <xsd:complexType name="SimpleType1">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 bdfdbef1df9711daa2c9001125f86068
 </xsd:appinfo>
 </xsd:annotation>
 <xsd:sequence>
 <xsd:element name="Name" type="SimpleType2">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 bdfdbef0df9711daa821001125f86068
 </xsd:appinfo>
 </xsd:annotation>
 </xsd:element>
 </xsd:sequence>
 </xsd:complexType>
 <xsd:complexType name="SimpleType2">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 0fecc852df9811da899a000f206d294f
 </xsd:appinfo>
 </xsd:annotation>
 <xsd:sequence>
 <xsd:element name="Name" type="xsd:string">
 <xsd:annotation>
 <xsd:appinfo source="http://sap.com/xi/TextID">
 ac58afc0df9711da86af001125f86068
 </xsd:appinfo>
 </xsd:annotation>
 </xsd:element>
 </xsd:sequence>
 </xsd:complexType>
</xsd:schema>
Any one can help me please.
Thanks, Davy

Hello Moorthy,
My XSD is correct since it's XI itself that generated it from real Data Type on my source System (but I tested it in Internet Explorer and it looks fine).
I tried to select my ExternalDefinition as source in MessageMapping, but XI doesn't let me specify it (Apply button is disabled when I select my ExternalDefinition).
I'm pretty sure that it is related to the fact that I should have a Data Type in "Messages" and "External References" tabs and I have nothing. My XSD is legal, but it seems that XI can't automatically create the data type from it.
Do you have any other idea?
Thanks, Davy

Creating RosettaNet data types in XI 2.0: 'xml:lang' attribute

Similar Messages

Maybe you are looking for