Integration Repository: change XSD type in data types

Hi,
we created data types for our interface where we used the XSD type float and integer. We built on that Message types and Message interfaces and used them as abstract types in a BPM scenario.
During our test phase we encountered errors with these XSD types and found out that it is better to switch the XSD type to string to get correct values.
However the changes in XSD types are obviously only visible in the Integration Repository. XI creates on Application Server side in the XML Object Type Builder an object which doesn't notice this change. And because of that we get still errors.
So does anyone know how to get this XML Object Type changed? We don't want to delete everything and create new message types?
Thanks in advance,
Christina

Hi Christina,
First go to SXI_CACHE -> Refresh the cache.
Also check for the Repository Cache Refresh/Notifciations..
You mean you have changed the xsd in the External Definition ...
If so , just go to Message Interfaces and just select the External definition once again and activate the same.
If you change the Data types then , if there is a change in field length/type then try to redo/reselect the datat types for the message types and activate once again.
For BPM just change something.. and activate once again..
Also check this blog- to activate Runtime version of the BPM
/people/krishna.moorthyp/blog/2005/11/28/inactive-integration-process-ip-at-run-time
Hope this helps,
Regards,
Moorthy
Message was edited by: Krishna Moorthy P

Similar Messages

Regarding Changing the Namespace And Data Type in XSD File

Hi All,
I am Doing File -
IDOC Interface.
I have XSD File For File Sysyetm and IDOC For ECC.
In XSD File I Have Different Name Space And Data Type ,
I Created the Data Type as Same as the XSD File Data type
I Have Namespaces Are Different,
So,I Changed the Namespace in the XSD File with the New Namespace Which I created in IR.
I Changed in Two Places Like this
<b><xsd:schema targetNamespace="http://Sample1.com/xi/file;" xmlns="http://Sample1.com/xi/file;"</b>
But it is giving Error lik this
<b>Cannot load schema with the target namespace http://xxx.com/xi/xx/vamsi/100 to namespace http://Sample1.com/xi/file;</b>
Regards
Vamsi

Hi Vasanth,
Thats what I am Asking
I want to Import XSD File in Data Type
Before I Import the XSD File into Data type I changed the Namespace in the XSD to My Namespace Which is in IR. And I Created the Data Type Name in IR Which I Have in XSD FIle .
So I Am Getting this Error
Please Let me Know Wat to do
Regards
Vamsi

XSD imported as Data Type

Hi All!
I am very new to XI. As in this is my first project.   I did look for this question in the forum, but I probably missed it as the wording would have to be close to my own. Anyway-
I am trying to import an XSD into a data type.   I keep getting an error:
Attribute "name" of element "/schema/element("Name") has the value "Name" that has already been used in the element "/schema". Ensure all attributes and elements of each element have unique names when using the xsd editor.
Well - I'm very confused. This is the XSD that I was given for an outbound process.   Any suggestions on what to do? XSD is below.
Thank you!
Michelle
XSD:
<xsd:schema xmlns:xsd='http://www.w3.org/2001/XMLSchema'>
<xsd:element name='ShipperLoadPlan'>
<xsd:complexType>
   <xsd:sequence>
    <xsd:element ref='LoadNumber'/>
    <xsd:element ref='LeanLoadID'/>
    <xsd:element ref='Canceled'/>
    <xsd:element ref='DirectionCategory'/>
    <xsd:element ref='TrailerNumber' minOccurs='0' maxOccurs='1'/>
    <xsd:element ref='ReferenceNums' minOccurs='0' maxOccurs='1'/>
    <xsd:element ref='Carrier' minOccurs='0' maxOccurs='1'/>
    <xsd:element ref='Stops' minOccurs='0' maxOccurs='1'/>
   </xsd:sequence>
   <xsd:attribute name='CreateDate' type='xsd:string' use='optional'/>
   <xsd:attribute name='ExecutionEvent' type='xsd:string' use='optional'/>
   <xsd:attribute name='ExecutionEventID' type='xsd:string' use='optional'/>
</xsd:complexType>
</xsd:element>
<xsd:element name='ReferenceNums'>
<xsd:complexType>
   <xsd:sequence>
    <xsd:element ref='Reference' maxOccurs='unbounded'/>
   </xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name='Reference'>
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base='xsd:string'>
   <xsd:attribute name='type' type='xsd:string' use='required'/>
   </xsd:extension>
   </xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element name='Stops'>
<xsd:complexType>
   <xsd:sequence>
    <xsd:element ref='Stop' maxOccurs='unbounded'/>
   </xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name='Stop'>
<xsd:complexType>
   <xsd:sequence>
    <xsd:element ref='StopNumber'/>
    <xsd:element ref='StopType'/>
    <xsd:element ref='CalcDueDate' minOccurs='0' maxOccurs='1'/>
    <xsd:element ref='DueDate' minOccurs='0' maxOccurs='1'/>
    <xsd:element ref='Appt' minOccurs='0' maxOccurs='1'/>
    <xsd:element ref='ETADate' minOccurs='0' maxOccurs='1'/>
    <xsd:element ref='ArrivalDate' minOccurs='0' maxOccurs='1'/>
    <xsd:element ref='DepartureDate' minOccurs='0' maxOccurs='1'/>
    <xsd:element ref='Location'/>
    <xsd:element ref='LoadDates' minOccurs='0' maxOccurs='1'/>
    <xsd:element ref='ReferenceNums' minOccurs='0' maxOccurs='1'/>
    <xsd:element ref='OrderNums'/>
   </xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name='LoadDates'>
<xsd:complexType>
   <xsd:sequence>
    <xsd:element ref='LoadDate' maxOccurs='unbounded'/>
   </xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name='LoadDate'>
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base='xsd:string'>
   <xsd:attribute name='DateTypeID' type='xsd:string' use='required'/>
   <xsd:attribute name='TimeZone' type='xsd:string' use='optional'/>
   </xsd:extension>
   </xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element name='OrderNums'>
<xsd:complexType>
   <xsd:sequence>
    <xsd:element ref='OrderNum' maxOccurs='unbounded'/>
   </xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name='OrderNum' type='xsd:string'>
</xsd:element>
<xsd:element name='Carrier'>
<xsd:complexType>
   <xsd:sequence>
    <xsd:element ref='SCAC'/>
    <xsd:element ref='Name'/>
    <xsd:element ref='VendorNumber' minOccurs='0' maxOccurs='1'/>
    <xsd:element ref='TenderSCAC' minOccurs='0' maxOccurs='1'/>
   </xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name='Location'>
<xsd:complexType>
   <xsd:sequence>
    <xsd:element ref='LocationRef'/>
    <xsd:element ref='Name'/>
    <xsd:element ref='Address1' minOccurs='0' maxOccurs='1'/>
    <xsd:element ref='Address2' minOccurs='0' maxOccurs='1'/>
    <xsd:element ref='Address3' minOccurs='0' maxOccurs='1'/>
    <xsd:element ref='City' minOccurs='0' maxOccurs='1'/>
    <xsd:element ref='State' minOccurs='0' maxOccurs='1'/>
    <xsd:element ref='Zip' minOccurs='0' maxOccurs='1'/>
    <xsd:element ref='Country' minOccurs='0' maxOccurs='1'/>
    <xsd:element ref='IsPoolPoint' minOccurs='0' maxOccurs='1'/>
   </xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name='LoadNumber' type='xsd:string'>
</xsd:element>
<xsd:element name='Canceled' type='xsd:string'>
</xsd:element>
<xsd:element name='LeanLoadID' type='xsd:string'>
</xsd:element>
<xsd:element name='DueDate'>
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base='xsd:string'>
   <xsd:attribute name='Start' type='xsd:string' use='optional'/>
   <xsd:attribute name='End' type='xsd:string' use='optional'/>
   <xsd:attribute name='TimeZone' type='xsd:string' use='optional'/>
   </xsd:extension>
   </xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element name='Appt'>
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base='xsd:string'>
   <xsd:attribute name='From' type='xsd:string' use='optional'/>
   <xsd:attribute name='To' type='xsd:string' use='optional'/>
   <xsd:attribute name='TimeZone' type='xsd:string' use='optional'/>
   <xsd:attribute name='ApptRef' type='xsd:string' use='optional'/>
   </xsd:extension>
   </xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element name='ETADate'>
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base='xsd:string'>
   <xsd:attribute name='TimeZone' type='xsd:string' use='optional'/>
   </xsd:extension>
   </xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element name='ArrivalDate'>
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base='xsd:string'>
   <xsd:attribute name='TimeZone' type='xsd:string' use='optional'/>
   </xsd:extension>
   </xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element name='DepartureDate'>
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base='xsd:string'>
   <xsd:attribute name='TimeZone' type='xsd:string' use='optional'/>
   </xsd:extension>
   </xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element name='CalcDueDate'>
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base='xsd:string'>
   <xsd:attribute name='TimeZone' type='xsd:string' use='optional'/>
   </xsd:extension>
   </xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element name='SCAC' type='xsd:string'>
</xsd:element>
<xsd:element name='Name' type='xsd:string'>
</xsd:element>
<xsd:element name='VendorNumber' type='xsd:string'>
</xsd:element>
<xsd:element name='TimeZone' type='xsd:string'>
</xsd:element>
<xsd:element name='CreateDate' type='xsd:string'>
</xsd:element>
<xsd:element name='ExecutionEvent' type='xsd:string'>
</xsd:element>
<xsd:element name='TenderSCAC' type='xsd:string'>
</xsd:element>
<xsd:element name='ExecutionEventID' type='xsd:string'>
</xsd:element>
<xsd:element name='TrailerNumber' type='xsd:string'>
</xsd:element>
<xsd:element name='DateTypeID' type='xsd:string'>
</xsd:element>
<xsd:element name='StopNumber' type='xsd:string'>
</xsd:element>
<xsd:element name='StopType' type='xsd:string'>
</xsd:element>
<xsd:element name='DirectionCategory' type='xsd:string'>
</xsd:element>
<xsd:element name='LocationRef' type='xsd:string'>
</xsd:element>
<xsd:element name='Name' type='xsd:string'>
</xsd:element>
<xsd:element name='Address1' type='xsd:string'>
</xsd:element>
<xsd:element name='Address2' type='xsd:string'>
</xsd:element>
<xsd:element name='Address3' type='xsd:string'>
</xsd:element>
<xsd:element name='City' type='xsd:string'>
</xsd:element>
<xsd:element name='State' type='xsd:string'>
</xsd:element>
<xsd:element name='Zip' type='xsd:string'>
</xsd:element>
<xsd:element name='Country' type='xsd:string'>
</xsd:element>
<xsd:element name='IsPoolPoint' type='xsd:string'>
</xsd:element>
</xsd:schema>

Hi ,
I don't know your requirement in detail , If you are using XSD, no need to create data type message type , upload this XSD to ' EXTERNAL DEFINITIONS' , you can use this XSD directly in Message mapping ( MM) .

[Access 2010] Change default formats for data types

Whenever I import data, the default format for Boolean data types is "-1,0." I know how to subsequently change this format to "Yes/No," but I'd like to change the default
setting to "Yes/No." Is this possible?
Thanks in advance.

Hi,
I found you post the same question in other place and got the advice. I agree with Mr. Kees suggestion. The data type is a build-in default setting with Access, we can't change it. We may try the workaround via VBA to test.
http://forums.cnet.com/7723-6129_102-627633/access-2010-change-default-formats-for-data-types/#message5617496
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Have a good time.
Regards,
George Zhao
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

How to Transfer IDoc Type to Data Type in XI

Dear All,
I am working on scenario to transfer data(IDoc) from SAP System to Non SAP system through XI.
While Defining "Data Type" in XI i want to create Data Type as of IDoc type(CREMAS05).There is any direct method to import IDoc type into "Data Type" in XI.
thanks,
RP

Hi Rp,
External definitions enable you to import WSDL, XSD, and DTD documents to the Integration Repository so that you can access the message definitions they contain as external messages.
If a description of the message structure already exists in one of the above formats, you can use it in the Integration Repository by importing it as an external definition rather than re-entering it manually using the data type editor.
Prerequisites
The document to be imported must conform to the WSDL, XSD, or DTD standard.
Chk out all the details + how to import Ext Def:
http://help.sap.com/saphelp_nw04/helpdata/en/26/9e97b0f525d743882936c2d6f375c7/content.htm
Also refer...
Connection Using Adapters and Imported Interfaces
http://help.sap.com/saphelp_nw04/helpdata/en/4a/576d219c340844aaa12ce9bbc2c3ee/frameset.htm
Incase u want to chk out the details of Idoc scenario.....
IDoc to File:
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
Handling different partners for IDoc:
/people/sravya.talanki2/blog/2005/08/17/outbound-idocs--work-around-using-party
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/file%2bto%2bidoc
Hope this was helpful..
kanan

Unicode - "DMBTR" must be a character-type field (data type C,N,D or T)

Greetings Experts!
I am trying to convert legacy code to Unicode for a current ERP6.0 reinstallation and have encountered the syntax error "DMBTR" must be a character-type field (data type C,N,D or T)
The field is part of a structure and the fields attributes are as follows:
COMPONENT = DMBTR
COMPONENT TYPE = DMBTR
DATA TYPE = CURR
LENGTH = 13
DECIMALS = 2
DESCRIPTION = Amount in Local Currency
The code in question is as follows:-
macro Move_Zoned.
Converts a numeric variable to zoned format and moves it to a
target variable.
DEFINE move_zoned.
     &1 - source variable
     &2 - Number of Decimal Places
     &3 - 'To'
     &4 - Target Variable.
write &1 to w_zoned no-grouping decimals &2.
condense w_zoned.
     Remove the Decimal Points.
search w_zoned for '...'.
while sy-subrc = 0.
    move sy-fdpos to w_to_point.
    if w_to_point = 0.
      w_to_point = 1.
    endif.
    compute w_from_point = sy-fdpos + 1.
    concatenate w_zoned+0(w_to_point)
                w_zoned+w_from_point
           into w_zoned.
    search w_zoned for '...'.
endwhile.
shift w_zoned right deleting trailing space.
translate w_zoned using ' 0'.
call function 'Z_TRANSLATE_ZONED_DECIMALS'
    exporting
      i_input              = w_zoned
    importing
      i_output             = w_zoned
    exceptions
      x_invalid_zoned_char = c_invalid_zoned_char
      x_numeric_info_lost = c_numeric_info_lost
      others               = c_other_zoned_error.
     Get the length of the recipient field so we don't truncate the
     numbers....
describe field &4      length w_flength in character mode.
describe field &4      type   w_type.
describe field w_zoned length w_zoned_len in character mode.
if w_zoned_len <= w_flength.
    move w_zoned to &4.
    shift &4 right deleting trailing space.
    translate &4 using ' 0'.
else.
        Get the start position....
        If it's a packed field allow for values up to 6 figures
    compute w_zoned_len = w_zoned_len - w_flength.
    if w_type = 'P'.
      subtract 2 from w_zoned_len.
      clear w_type.
    endif.
    move w_zoned+w_zoned_len &3 &4.
endif.
END-OF-DEFINITION. "Move_zoned
LOOP AT t_single_kunnr.
    move_zoned t_single_kunnr-postamt 2
            to t_single_kunnr-dmbtr.
    DIVIDE t_single_kunnr-dmbtr BY 100.
    MODIFY t_single_kunnr.
ENDLOOP.
Is there a solution to get past this syntax error as I would rather not change the datatype of the field in the structure.
Much Obliged
Elphick.

Type X is not allowed in Unicode. When a field is declared as Type X with Value u201809u2019 or any other value, it can be resolved by using classes.
Before Unicode
                  CONSTANTS: c_hex TYPE x VALUE '09'.
Resolution:
Itu2019s work for any value of x.
First a temporary field of Type c should declare. Following class will convert Type x variable into type c.
Example:
CONSTANTS: c_hex TYPE x VALUE '09'.
DATA: LV_TEMP TYPE STRING.
DATA: LV_TMP TYPE C.
TRY.
CALL METHOD CL_ABAP_CONV_IN_CE=>UCCP
EXPORTING
UCCP   = c_hex
RECEIVING
CHAR   = LV_TMP   .
CATCH CX_SY_CONVERSION_CODEPAGE.
CATCH CX_PARAMETER_INVALID_TYPE.
CATCH CX_SY_CODEPAGE_CONVERTER_INIT.
ENDTRY.
CONCATENATE I_OUTPUT-BKTXT I_OUTPUT-BVORG
I_OUTPUT-BUDAT I_OUTPUT-MESSAGE INTO
SEPARATED BY LV_TMP.
I_BUFFER = LV_TEMP.
CLEAR LV_TEMP.
CLEAR LV_TMP.
OR
Note: It works only for type x value 09.
CLASS cl_abap_char_utilities DEFINITION LOAD.
CONSTANTS: c_hex TYPE c VALUE
                         abap_char_utilities=>HORIZONTAL_TAB.

Cardinality between Message Type and Data Type

Hi SAP gurus,
Could anyone please tell me the cardinality between the Message Type and Data Type?
Thanks,
Adnan Abbasi

1:1
Sameer

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

Changing domain-defined Timestamp data type to logical Date doesn't persist

Hi:
Version 3.1.0.691 on Windows 7 Enterprise 64-bit SP1
I imported a domain from Designer, and then imported a schema from a database, all into the same model, in that order. I then changed the data type on several columns from non-domain, logiical Date data types to Domain-defined Timestamp Wth Time Zone data types. After having done this, I decided that I wanted to leave them as they were and tried to change them back. I went into the relational model section for each table/column and de-selected the domain radio button, chose Logical, and then set the data type to Date. I clicked apply, OK, and then saved the entire model. I closed Data Modeler, re-opened it, and then checked the data type change. I found that the change from domain to logical was saved, but the data type remained as Timestamp With Time Zone instead of remaining as Date like I'd set it. I've tried changing from Timestamp With Time Zone to other data types and then to Date but it didn't work.
Am I doing something wrong or is this a bug?
Thanks!
Doc

Hi:
One final comment. I set the domain back to unknown and clicked appy, but left the Column Properties dialog box open. I then clicked the button next to Datatype (which showed UNKNOWN{Unknown}, changed the radio button from Domain to Logical Type, and then selected Date from the list box and clicked OK. Immediately after having clicked OK, the Logical Type dialog box remained open and the Logical Type value within the Logical Type dialog box reverted back to Unknown. I re-selected Date from the list box, clicked OK, and after this second try it kept the change without the "double clutch."
Doc

Core data: Versioned model migration with change in existing attribute data types.

Hi ,
I want to upgrade my ios app with app store version with enhancement of new functionality related to core data features in the app.
-In new upgarde version, I want to change data types of attribute which is already present in core data model of existing app store version.
e.g.In Version 1.0 ,Attribute "date" datatype is "NSDate", New change required to change datatype "NSDate" to "NSString" with new version model.
I followed Lightwaight migration, but as per documentation , Lightwaigh migration not support for change data type of any existing attribute/entity of core data model.
Please suggest optimized solution for migration of database along with change in data type of exsiting attribute of the entity in core data.
If required in further info ,please ask.
Thanks in advances.
Regards,
Laxmikant

More Info: The two entries are actually pointing to the same object. If I save the context and restart, I only have one entry (I can also see this by looking at the XML store).
It seems that the NSTableView is getting messed up somehow after the FetchRequest. Still stumped.

How to define IDOC as 'type' in 'Data types' ?

Hi all,
I am trying to define a data type which accepts multiple occurences of IDOC type in the same message. The required XML should be like this...
<All_IDOCs>
   <ZUPFIN_>                 <--- this is the IDOC imported into XI
       <IDOC>...
       </IDOC>
   </ZUPFIN>
   <ZUPFIN_>                 <--- this is the IDOC imported into XI
       <IDOC>...
       </IDOC>
   </ZUPFIN>
<All_IDOCs>
Now, there are more than 800 fields under <ZUPFIN_> IDOC. So I am trying to find out an easy solution to create the above data type without manuall adding each element.
Any idea ?
Thanks.
- Atul

Hi Ahmad,
As I have already mentioned above, I do not want multiple occurences of 'IDOC' element. Instead I want the multiple occurences of 'ZUPFIN_' (in Michael's blog you given by link, it is 'MBGMCR02'). So the example does not help here as roots cannot occur more than once.
I cannot have anything changed on R/3 side.
Thanks.
- Atul

How to call user define data type as data type for concurrent parameter

Hi All,
i find some difficulty while creating the concurrent program.
i.e.
i have one of the parameter of table type i.e. user define data type at PLSql program
now i need to register same PLSQL program into oracle applications as concurrent program
but while i am creating Parameters for concurrent program
How could i define that user define data type at database level in oracle applications using 'Value set' ?
any one save me from this Problem
thanks and Regards,
sai krishna@cavaya.

Don't think this can be done..
One way I can think of is to wrap your PL/SQL program under another procedure/package that can accept "normal" parameter,and use/register this wrapper instead of your original pl/sql program.
HTH

JDBC TYPES.Integer Data Type--Oracle seems useless

I have a set of applications that work on every database I've
tried it on except Orocle. They rely very heavily on making a
query and then grabbing the correct data type (e.g., getInt() vs.
getString()) based on the int value returned in the
ResultSetMetaData. The problem here is that the type returned
for Integer columns, however, is always NUMBER and therefore
always has a decimal place and gets automatically converted into
a double. This wreaks havoc on all of the classes which assume
that certain columns will be int's (e.g., primary keys). Also,
since I'm programming servlets, I am often throwing the values
into forms where the values will be retrieved and have an
Integer.parseInt() run on them--Integer.parseInt() will not work
on Strings with decimal points.
I realize why Oracle does this (because an integer is a number
with no decimals) and what the workaround is (use a
NumberFormatter instead of Integer.parseInt() or use Oracle's
extensions to preset the datatype). But why should I have to
hack up my code just because Oracle programmers can't figure out
how to get its JDBC drivers to return the proper Type code?
Is there any other w
null

I have a set of applications that work on every database I've
tried it on except Orocle. They rely very heavily on making a
query and then grabbing the correct data type (e.g., getInt() vs.
getString()) based on the int value returned in the
ResultSetMetaData. The problem here is that the type returned
for Integer columns, however, is always NUMBER and therefore
always has a decimal place and gets automatically converted into
a double. This wreaks havoc on all of the classes which assume
that certain columns will be int's (e.g., primary keys). Also,
since I'm programming servlets, I am often throwing the values
into forms where the values will be retrieved and have an
Integer.parseInt() run on them--Integer.parseInt() will not work
on Strings with decimal points.
I realize why Oracle does this (because an integer is a number
with no decimals) and what the workaround is (use a
NumberFormatter instead of Integer.parseInt() or use Oracle's
extensions to preset the datatype). But why should I have to
hack up my code just because Oracle programmers can't figure out
how to get its JDBC drivers to return the proper Type code?
Is there any other w
null

Can I change Calendar type to Date type?

Hi Gentlemen,
Here is the scenario.
A user enters a date as string.
I pass that string to a class named DateStamp
where I get this string say [s]
and parse it,then I create a date object.
here is the code for it.
public Date setThisDate(String s) {
DateFormat format = new SimpleDateFormat("yyyy/mm/dd");
Date d=null;
try{
d = format.parse(s);
}catch(ParseException pe) {
pe.printStackTrace();
//Calendar date = new GregorianCalendar();
//date.setTime(d);
System.err.println(d.toString());
return d;
the error I got is,
Unparseable date
can some one guide me please.

Your program is trying (and failing) to convert a String to a Date. So why do you keep asking how to convert a Calendar to a Date? That's not your problem. Your problem is that your SimpleDateFormat expects to be given a String containing a 4-digit year field, a slash (or dash), a 2-digit minute field, a slash (or dash), and a 2-digit day field. That doesn't make any sense, and that's why you get the error. It would work better if you specified a month field instead of a minute field:
DateFormat format = new SimpleDateFormat("yyyy/MM/dd");

What type of data type would I use for this situation?

I have a class which connects to Oracle, but each connection may be to a different database. Each database has it's own user name and password.
I'd like to pass one key value and then the class would get the user name and password and url from that but not sure how to do it.
Right now, for the function I pass it the url, username, password which then calls a connection function and passes it the same value. This seems messy keep passing values around.
Is there some kind of enumerations or something ?

You might consider putting the URLs, usernames and password into a properties file.
The properties file might contain:
all.databases=database1,database2,database3
database1.user=user1
database1.password=dingbat
database1.url=jdbc:oracle:thin:dohdah:base1
database2.user=someone
database2.password=toad
database2.url=jdbc:oracle:thin:xyx:dsds
Then use ResourceBundle.getBundle() to load the properties and you can just do
Connection con = DriverManger.getConnection(bundle.getString(key + ".url"),bundle,getString(key + ".user"), bundle.getString(key + ".password");

Integration Repository: change XSD type in data types

Similar Messages

Maybe you are looking for