Validation while create data type

HI All ,
I have a pop-up in my report that user can create data type in didc,
There is a simple way to support validation for data types ,
I have pop-up where the user need to provide name of attribute
he need to create and the data type for it (char ,string ,int etc )
and he also need to provide the leng of the attribute he want to create
(e.g. char10 ) and also decimal places .
the issue here that i need to do some validation in the pop-up
for e.g. if user choose
case 1
name     - attribute1
datatype - string
leng   - in this case he dont need to provide leng (string )
dec - dont need to provide (string )
case 2
name     - attribute1
datatype - char
leng   - 10
dec - dont need to provide (char )
Any idea how to do this validation in a simple way (maybe to use standard functionlity)
Regards
Alex

HI Keshav.
What i did is created a popup with FM in the popup i have 4 field
the field with the data type which i want to trigger event to it is domain and not ref to FM
The ppoup have 4 field
attr name
datatype
length
decimal
so from what you are say there is not option to trigger event when the user press F4
and choose a entry from it ,
since what i want to do is that if user for instance chose string i want that the next to fields (length and dec ) will be
remove from the popup since he dont need them .
and for he choose char the the decimal field will remove from the popup
Any idea how to solve this issue ?
Regards
Alex
Edited by: Alex Dean on Oct 12, 2010 3:02 PM

Similar Messages

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

Error While Creating Date type condition query

Hi All,
I am getting following error while creating a multiple condition query.
ERROR:java.lang.IllegalArgumentException: Unexpected field type for D: java.lang.String
I am pasting the scrap of the code for review below.
pls note after removing the condition cond6; it works fine, and cond6 is for date type field.
for(int j=1;j<7;j++){
fd[j] =trd.getFieldDescriptor(arrayHeaderFieldNames[j]);
BasisFieldType bft1 = fd[j].getFieldType();
if (bft1 == BasisFieldType.C) {
filterOperator[j] = RelationalOperatorType.CONTAINS; }
else{
filterOperator[j] = RelationalOperatorType.EQUALS;
order[j] =queryFactory.createSortOrder(fd[j],true);
cond1 =queryFactory.createCondition(fd[1], filterOperator[1], values[0]);
cond2 =queryFactory.createCondition(fd[2], filterOperator[2], values[1]);
cond3 =queryFactory.createCondition(fd[3], filterOperator[3], values[2]);
cond4 =queryFactory.createCondition(fd[4], filterOperator[4], values[3]);
cond5 =queryFactory.createCondition(fd[5], filterOperator[5], values[4]);
cond6 =queryFactory.createCondition(fd[6], filterOperator[6], values[5]);
Condition cond = queryFactory.createCondition(new Condition[]{cond1,cond2,cond3,cond4,cond5,cond6},LogicalOperatorType.AND);
Please Help!
Thanks n regards,
Kapoorchand.

Hi,
well that problem is a long time back -. I only have in mind that the date I had to transfer to the quesry was in a "strange" format. Have a lock into the documentation for the date field - your date field is not recognised as a date field from the quesry engine and so this fails - but unfortunately I have no idea at the moment how I fixed it last time - how I converted my date field......
Sorry, thast I can not give you the real point - but I will have a lock into the old code - hopefully I find it soon.
Regards,
Oliver

Error While creating Data type from a XSD

Hi,
I am trying to import a XSD into my Data type. I have changed the namespace in the XSD to match that of the target namespace. I am getting the following error.
Global definition Element: http://ls.sbc.com/OMS/ProcessSalesOrderEFE004,   orderRequest in the schema to be edited will be ignored
Schema to be edited defines qualified element names (elementFormDefault = 'qualified')
Could any help me out in this regard. I don't have much knowledge about XML and XSD.
Regards,
Ravikanth

Hi Ravi,
please check once again your XSD file.
it should be like this.
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://ls.sbc.com/OMS/ProcessSalesOrderEFE004, " targetNamespace="http://ls.sbc.com/OMS/ProcessSalesOrderEFE004, ">
     <xsd:complexType name="DTO_Data type">
          <xsd:annotation>
               <xsd:appinfo source="http://sap.com/xi/TextID">
               725b8b10c99e11dc8ff3001cc43a8a68
               </xsd:appinfo>
Please check the name of data type u mentioned in XSD while imporitng.
regards
mahesh..

Getting error while creating condition type in SPRO

Hi ,
can somebdy tell me why i am getting the following error while creating condition type in SPRO
No valid change license available for message /sapcnd/
and also while rule determination using condition type we are getting the following error.
system error:system cannot read the structure for table
reg
venkat

Hi Venkat,
Do you have the error number code!?
Regards,
Michel Bohn

CREATE DATA TYPE TABLE

Hi Colleagues,
regarding my IDOC viewer project I'm facing a question regarding the SAP release. I started with some success on Release 471, now I tried to continue on 46C.
CREATE DATA gr_ref
TYPE lvc_t_fcat."STANDARD TABLE OF LVC_S_FCAT.
works in both releases, while
CREATE DATA ls_seg_dat-ref
TYPE STANDARD TABLE OF (<edid4>-segnam).
compiles on 471, but generates syntax error in 46C.
The error message "Unable to interpret "TABLE". Possible causes of error: Incorrect spelling or comma error."
does not help too much.
Does this mean that there is no way to create tables dynamically on release 46C?
Hope for a solution!
regards,
C.

Hello,
the only possibility I found was to use available table types in the dictionary. This works on a 4.6C system:
DATA: lf_type(20)          TYPE c VALUE 'MARA',
        lf_table_type(20)    TYPE c VALUE 'MARA_TAB'.
DATA: wa_data              TYPE REF TO data,
        lt_data              TYPE REF TO data.
FIELD-SYMBOLS: <structure> TYPE ANY,
                 <field>     TYPE ANY,
                 <table>     TYPE TABLE.
CREATE DATA wa_data TYPE (lf_type).
ASSIGN wa_data->* TO <structure>.
ASSIGN COMPONENT 'MATNR' OF STRUCTURE <structure> TO <field>.
<field> = 'My Material'.
CREATE DATA lt_data TYPE (lf_table_type).
ASSIGN lt_data->* TO <table>.
APPEND <structure> TO <table>.
Little curious: An internal table type defined with "TYPES ty_mara_tab TYPE TABLE OF mara" is not accepted by CREATE DATA, but the dictionary type is. So even generating a little top include dynamically with the needed type as a table type will not work on 4.6C
Best regards,
Stefan Kozlowski

Creating data types

Hi
How do u create a data type when u get an input file.
How do u know when to create header , footer n all?
Can some one tell me or send a url on how to create data types. would be of great help!
Thanks!

HI,
Generally identifying the structure from the input file need some analysis work.
You may refer some of the below tips while creating the data types
1. List down the input structure of data fields from input file.
2. Decide the Header and detail information based on the data and go for sub-structure.
3. With File adapter try to maintain the structure level max. upto 2.
i.e. Root>Header>Fields etc.
4. Try to avoid the substructure for the internal fields.
5. Decide the Occurances fo every root and sub structures and fields.
6. Identify if there any relations within Header and detail fields.etc.
Check with SAP Help for various activities
http://help.sap.com/saphelp_nw04/helpdata/en/a5/04623c4f69b712e10000000a114084/content.htm
Thanks
Swarup

InfoPath - "Schema validation found non-data type errors." at XmlWriter.Close()

Greetings,
I'm creating a form that allows for emailing attachments however I am having an issue. When I try to attach a file, I get an "Schema validation found non-data type errors." error message. It seems like it's something with the XML structure and
I cannot find anything wrong.
Here is the code:
string myNamespace = NamespaceManager.LookupNamespace("my");
using (XmlWriter writer = MainDataSource.CreateNavigator().SelectSingleNode("/my:myFields/my:Email/my:AttachmentGroup", NamespaceManager).AppendChild())
//Write to XML
InfoPathAttachmentEncoder myEncoder = new InfoPathAttachmentEncoder(currentFile);
writer.WriteStartElement("Attachments", myNamespace);
writer.WriteElementString("attachment", myNamespace, myEncoder.ToBase64String());
writer.WriteElementString("attachmentCheckbox", myNamespace, "false");
writer.WriteEndElement();
writer.Close();
Here is the structure of the XML (root node is myFields):
<my:Email>
<my:AttachmentGroup>
<my:Attachments>
<my:attachment xsi:nil="true"></my:attachment>
<my:attachmentCheckBox>false</my:attachmentCheckBox>
</my:Attachments>
</my:AttachmentGroup>
<my:emailAddress>[email protected]</my:emailAddress>
<my:subject>Paychex ESR Services Paperwork</my:subject>
<my:body/>
<my:selectAll>false</my:selectAll>
</my:Email>
Attachments is the repeating group in this case.
Can anyone spot where the error is coming from?
Thanks!

HI,
I fixed it:
Below code is used to fix:
[CODE]
XPathNavigator xfield = null;
DateTime dtmyRecievedDate;
dtmyRecievedDate = Convert.ToDateTime(objInfopathFormcData.myRecievedDate);
if (objFormcData.FcCompletionDate != null)
xfield = myRoot.SelectSingleNode("/my:myFields/my:field97", NamespaceManager);
DeleteNil(xfield);
xfield.SetValue(dtmyRecievedDate.GetDateTimeFormats().GetValue(5).ToString());
// method to delete xsi:nil
private void DeleteNil(XPathNavigator nav1)
if (nav1.MoveToAttribute("nil", "http://www.w3.org/2001/XMLSchema-instance"))
nav1.DeleteSelf();
[/CODE]
Thank you

SQL Error while creating data Owner certification in SRM 5.0.3

Hi , In SRM 5.0.3, while creating data Owner certification by choosing data owner, I m getting the following error. database i upgraded and the migration script is also run.
java.sql.SQLException: Violation of PRIMARY KEY constraint 'pk_id_attr_val_users'. Cannot insert duplicate key in object 'dbo.id_attr_val_users'. Since Primary key is clustered(cert_id,user_id,attr_val_id) and we have updated currentvalue of CertificationID in sequences table, We are not sure if SRM is trying to enter duplicate attribute value for same user in D.O certification. Any pointers regarding this error will be of great help, thanks.

Solved but not happy!
VIN is not compatible with a web UI that uses standard ports, i.e. TCP 80 and 443. No notes (at least that I seen) in the documents stating this as a requirement.
KB 2065986
VMware KB: VMware vRealize Infrastructure Navigator is not accessible when the vSphere Web Client is not running on …

Hello Guru's Error MSG while creating Material Type HERS

Hello Guru's,
While creating material type HERS the system is showing the following error *"The field orign acceptance is defined as a required field; it does't contain an entry'"* will any one give solution.
even i have filled orign field in info record also still it is giving same error message, will anyone give solution.
full points for the answer.

hers is for the mpn
note the techincal name of that field and then go to oms9 and there make that filed for the filed selection key of hers as optional
u can get the field selcton key of hers from the tcode oms2

Error while creating data warehouse tables.

Hi,
I am getting an error while creating data warehouse tables.
I am using OBIA 7.9.5.
The contents of the generate_clt log are as below.
>>>>>>>>>>>>>>>>>>>>>>>>>>
Schema will be created from the following containers:
Oracle 11.5.10
Universal
Conflict(s) between containers:
Table Name : W_BOM_ITEM_FS
Column Name: INTEGRATION_ID.
The column properties that are different :[keyTypeCode]
Success!
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
There are two rows in the DAC repository schema for the column and the table.
The w_etl_table_col.KEY_TYPE_CD value for DW application is UNKNOWN and for the ORA_11i application it is NULL.
Could this be the cause of the issue? If yes, why could the values be different and how to resolve this?
If not, then what could be the problem?
Any responses will be appreciated.
Thanks and regards,
Manoj.

Strange. The OBIA 7.9.5 Installation and Configuration Guide says the following:
4.3.4.3 Create ODBC Database Connections
Note: You must use the Oracle Merant ODBC driver to create the ODBC connections. The Oracle Merant ODBC driver is installed by the Oracle Business Intelligence Applications installer. Therefore, you will need to create the ODBC connections after you have run the Oracle Business Intelligence Applications installer and have installed the DAC Client.
Several other users are getting the same message creating DW tables.

"Schema validation found non-data type errors" error when passing a string value to date field in infopath

Hi,
I have an infopath web brower enabled form. In the form i have a date field.
I am passing the data from the database to that field using the C# code.
But, as the field from database is coming as string, i am getting an error, and i am not able to assign the value.
I get the date value from database as "3/25/2011 12:00:00 AM"
I used the below code:
[CODE]
if (objInfopathFormcData.myRecievedDate != null)
myRoot.SelectSingleNode("/my:myFields/my:field97", NamespaceManager).SetValue(objInfopathFormcData.myRecievedDate);
[/CODE]
I am getting the error as "Schema validation found non-data type errors".
How to set the value for a date field in Infopath.
Thank you

HI,
I fixed it:
Below code is used to fix:
[CODE]
XPathNavigator xfield = null;
DateTime dtmyRecievedDate;
dtmyRecievedDate = Convert.ToDateTime(objInfopathFormcData.myRecievedDate);
if (objFormcData.FcCompletionDate != null)
xfield = myRoot.SelectSingleNode("/my:myFields/my:field97", NamespaceManager);
DeleteNil(xfield);
xfield.SetValue(dtmyRecievedDate.GetDateTimeFormats().GetValue(5).ToString());
// method to delete xsi:nil
private void DeleteNil(XPathNavigator nav1)
if (nav1.MoveToAttribute("nil", "http://www.w3.org/2001/XMLSchema-instance"))
nav1.DeleteSelf();
[/CODE]
Thank you

Not enough memory for Data Provider-Error while creating Data Source

Hi,
I am loading data into Master Data_Attribute InfoObject I am getting following error message while creating Data Source under "Proposal" Tab
"Not enough memory for Data Provider"
My Master Data InfoObject having 65 attributes
My CSV file having 15,00000 records
I am using BI 7.0 version
If anybody faced this problem. Please share with me
Thanks.

Hi
Here the problem with the space so plz contact ur BASIS people to increase the spae for particular object.

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

Why should we create data type

Hi all,
I have a basic question!
why do we create data type and then wrap it as message type?
why dont we directly create a message type and use that ?
please give the answers. Thanks in Advance.

Hi Seshu,
Please go through below links, you get answer
message type and datatype
Difference between Data type and Message type - Process Integration - SCN Wiki
Regards,
Krupa

Validation while create data type

Similar Messages

Maybe you are looking for