Long to int32 conversion issues in Xcode 5.0.2 when building plugin for Indesign CC 2014

Hi, I am trying to build one of the sample plugin WriteFishPrice from the SDK on mac System
I am using Xcode 5.0.2 as per the documentation, but I am encountering the below errors during compilation.
In UnicodeSavvyString.h
template <class FwdIterator>
inline void UnicodeSavvyString::assign_impl(FwdIterator b, FwdIterator e, size_type nCodePoints, std::forward_iterator_tag)
  const difference_type nCodeValues = std::distance(b, e);
  ASSERT(nCodeValues >= 0);
// Make room for the chars
  code_value* buffer = GetBufferForWriting(nCodeValues);  // <----Implicit conversion loses integer precision long to int
// Copy them into the buffer
  std::copy(b, e, buffer);
// Ensure terminating null
  buffer[nCodeValues] = code_value();
  fUTF16BufferLength = nCodeValues;                         // <----Implicit conversion loses integer precision long to int
// Calculate how many code points we will have at the end
  if (nCodePoints == 0 && nCodeValues)
  fNumChars = CountCharsUtil(buffer, nCodeValues);          // <----Implicit conversion loses integer precision long to int
else
  ASSERT((size_type)CountCharsUtil(buffer, nCodeValues) == nCodePoints);
  fNumChars = nCodePoints;
And similar errors are coming in WideString.h.
Can some one tell me what is wrong with the new SDK? Or if I need to make some changes in these files which surely is not advisable.

Hi kapoor_aman27,
this is just a warning, because the size of the string is stored as an int32 and some function has Argument with type int32. You can change the compiler setting "Treat Warnings as Errors" to "No". Then it is only a warning and you can ignore it as long as you use string with less than 4GB.
Markus

Similar Messages

  • Indesign mac: Plugin Built using Xcode 5.0.2 is not loading in Indesign CC 2014

    Hi,
    I have copied my project files from version 4.5.2 (which I was using for Indesign CC) to XCode 5.0.2.
    After this, I moved the *.plist of my plugin from sources folder to resources folder and then did the release build.
    But when I am opening Indesign CC 2014 version with my Plugin in plugins folder, I am getting Error saying
    that plugin is suitable for Indesign version 9.
    Did some one faced this issue before?

    Are you using InDesign CC 2014 SDK?
    Check the sdk path.

  • Xcode 3.2.6 best build settings for Mac

    Hi!
    I'm using Xcode 3.2.6 on Mountain Lion 10.8.5 to create Applescript based applications.
    They are tiny utilities that needs more complex UI Applescript can provide.
    I''m wondering what's the best build settings for applications aimed to run on Mac OS X
    - since 10.6
    - non universal binary (no PPC code)
    - 64 and 32 bit
    Thanks for your help.

    Mark,
    Now I'm confident about my buids.
    red_menace,
    Ok. That's what I was affraid about. So if I want to go further, I have to learn AppleScriptObjC.
    But the learning curve…
    I'm not a developper. Just a graphic designer.
    Don't have the time to check out this link, but maybe the solution for a smooth transiton to AppleScriptObjC is there:
    http://www.macosxautomation.com/applescript/apps/runner_vanilla.html
    Thanks both of you.

  • Conversion issue in encoding in PI

    Hi,
      I am having a problem in conversion issue for encoding. Let's have a detailed look into the scenario first.
    Scenario: SNC->PI (through Proxy)->MQ (through Receiver JMS adapter)->SeeBeyond (It's a middleware system).
                   Here from SNC, data are coming into PI as in UTF-8 encoding, whereas all the systems shown in the above flow are of ISO 8859_1 format. Hence UTF-8 needs to be converted into ISO 8859_1. PI does this conversion in Receiver JMS adapter. CCSID has been set to 00819 which is for ISO 8859_1 encoding. But the beginning of the xml, it remains still UTF-8, like below:-
      <?xml version="1.0" encoding="utf-8" ?>
    Whereas the content of the xml has already been converted into ISO 8859_1 by Receiver JMS adapter. Now let's see the problem now.
    Problem: After the data been passed in SeeBeyond, the mapping fails in SeeBeyond, since SeeBeyond tries to look at the XML tag from the beginning and it found it's in UTF-8 as per he tag above. Then it tries to map it in UTF-8 format whereas the content is in ISO 8859_1, so mapping fails in SeeBeyond. Please note, here allthe systems except SeeBeyond are just bypassing the data, no mapping been introduced in anywhere in the systems except SeeBeyond.
    Workaround: Is there any other chance where we can change the tag header from UTF-8 to ISO 8859_1 in Receiver JMS adapter itself in PI like this:-
    <?xml version="1.0" encoding="iso 8859_1" ?>
    This might resolve our problem I think. Any suggestions would be appreciated.
    Thanks and Regards
    Soumya

    Hi Stefan,
                Thanks for your reply. I have gone through the link you have specified. Ya, that's the other way to resolve that issue in that case. But here we have asked the receiver system (SeeBeyond) to change the encoding part in their mapping. Because changing the coding part in SeeBeyond is less time consuming than adding a new Bean in JMS adapter. Our problem got resolved by changing the mapping in Receiver end. Thanks anyway for your valuable reply.
    Thanks
    Soumya

  • Umlaut Conversion issue in Sender communication channel SAP PI

    Hi Gurus,
    We are facing issue while conversion.
    umlaut Conversion issue in Sender communication channel that is reason channel not able to pic the file from the path.
    Sender CC error:
    Value of incoming field is too large. Segment:'IMD', Field:'7008', MaxLength:'35', value:'Plssvvkbecher Lübzer 0,4 (1280Stk p' DESCRIPTION: The length of the field value is too big !
    Actually field contains 35 Chars only the value is  : 'Plssvvkbecher Lübzer 0,4 (1280Stk p'
    We tried with “ISO-8859-1” if the field value is less than 35 characters it is able to converting.
    Please help me out from this issue.
    Thank you.
    Regards,
    Jittu.

    Hi Jittu,
    Have you tried using the codepageconversion bean in the modules under the sender?  It would be like:
    AF_Modules/TextCodepageConversionBean with a parameter of Conversion.charset and a value of utf-8.
    Regards,
    Ryan Crosby

  • Language conversion issue in PI7.1

    Hi,
    My sceanrio is file to Idoc. Am facing language conversion issues.
    For example one of the field in the source file is having the value "Différence sur net". And in the IDOC field the value is appearing as "Différence sur net".
    With the same data I have done file to file scenario with and without content conversion and the output is coming correctly as "Différence sur net".
    I have enabled Unicode check box in RFC destination also in XI server. But still its coming "Différence sur net" . Please advice how can I get the target field value same as that of the source field vale.
    Can anyone help me to sort out this issue?
    Thanks.
    Dinesh

    Hi,
    In Channel try with using the File type: text and encoding : UTF-8.
    I think this will solve your issue.
    Thank you,
    Siva

  • Unicode conversion Issue

    Hi,
    We are using excel macros to load vendors.
    VB script in excel will call extenral RFC in SAP to validate and load vendors. SAP being an Unicode system and excel a non unicode system, is giving us issues while loading foreign characters other than english.
    For example, if we populate name in excel as "тест для макса" and once SAP validates the data these characters on excel get converted to "?????".
    Does anyone had similar issue? If yes, how did you deal with it?

    Sounds like something might go wrong with your code pages/used encodings. I.e. if I understand you correct you start off with data in Excel, that you then validate and the data changes? So I'm assuming that you're doing more than just validating...
    Anyhow, I doubt that you can label Excel as a non-Unicode application. E.g. in Excel 2007 you can clearly see that it handles Unicode, when you select some text and then paste it into Excel. However, instead of choosing the paste button, choose Paste special and you will see the option Unicode text. Also, when saving a worksheet in format xslx you can clearly see that the XML files contained in the xlsx archive (you'll see what I mean if you open the xslx file with a tool that you'd normally use for ZIP files) are encoded in UTF-8.
    I've seen some really old comments saying that VBA cannot handle Unicode, but I'm pretty sure that's no longer true (and was only applicable for really old Office versions)...
    I'm wondering if the issue is that your RFC call uses the OS code page, whereas Excel actually does use some Unicode encoding. Unfortunately I couldn't find quickly anything useful (apart from a description in the Office help that explained how to pick the encoding for Word and that Word in general stores data in UTF-8). So I'd personally start with some basic steps:
    <ol>
    <li>Check if you're using the right RFC library (see OSS note [1005832|https://service.sap.com/sap/support/notes/1005832]</li>
    <li>Check if you're setting the code page before calling your RFC; if not consider/try setting it (see OSS note [991572|https://service.sap.com/sap/support/notes/991572])</li>
    <li>Debug coding, possibly activating full trace for RFC and check where results go wrong</li>
    </ol>
    Cheers, harald

  • How do I get to the start of a really long text message conversation without scrolling through them all? Thanks

    Hi. How do I get to the start of a really long text message conversation without having to scroll through and load earlier messages repeatedly?  Thanks

    click on the top of the screen (the top bar/clock sectionish).  Hope i helped

  • A weird installer issue with xcode

    This is a new macbookpro i bought only a few weeks ago. I installed xcode on it, then removed it due to the fact that i needed to put some really huge hd video files, which needed all the hard disk space i could muster. After moving the videos from my mbp to my external hd, i tried to install xcode again. However, xcode's mpkg won't open, no matter how many times i open it with installer. Other mpkgs and pkgs work fine. What's the problem?

    Hi rhonnywhoop, and welcome to the Dev Forum!
    rhonnywhoop wrote:
    I installed xcode on it, then removed it ... i tried to install xcode again.
    There's no such thing as a weird issue with Xcode after an uninstall-install again cycle. Almost anything can go wrong and weird is the rule, not the exception. But yes, most of the strange problems show up after the installation (e.g., Xcode won't open, Xcode starts up but gcc always fails, Interface builder won't read nib files, etc., etc.). If I needed disk space for a video, I'd probably get another drive before I'd uninstall Xcode, but then I use Xcode all the time. Plus it's too late for that advice, so I'll try my best to point you in the right direction.
    A few questions:
    1) Was there any message when the mpkg failed to open? Please post any such message for us;
    2) Did you install from the DVD that came with your MacBook, or did you download a dmg from the Mac or iPhone Dev Center? If you haven't tried downloading the latest Xcode version yet, that might be worth trying;
    3) Did you uninstall from Terminal, using the command given in the Xcode doc (e.g. /Developer/"About Xcode Tools.pdf"? If not, how did you uninstall the prior Dev Tools?
    4) Is any entry made in one of your logs at the time of the failure? E.g., open Console.app (in /Applications/Utilities) and look for the most recent entries in install.log and system.log. If you find anything like that, please post it for us;
    5) Have you tried any additional cleanup besides the recommended uninstall (question 3, above)? Based on case histories in this and other forums, the most powerful trick is to rename /Developer (e.g. to /OldDev). Other tips will be found by searching on terms like "uninstall" or "clean" in this forum.
    In general, we can assume that since your previous installation was successful, the game is to restore your system to its past condition. This may seem like a no-brainer, but it might help to rule out irrelevant conditions as you try one thing after another. In fact, some developers have cleaned up by re-installing the entire system (needless to say, be sure to try restarting your system before resorting to anything that drastic!). On the other hand, some developers have reported that installing a more recent version of the Dev Tools (if any), can clean up a problem when repeated installs of the same system fail.
    I hope something above will lead you to a solution. Several other developers who regularly contribute to this forum know much more than I do about installation problems. For example, if etresoft joins this thread, be sure to follow his instructions completely and before any others.
    \- Ray

  • What can I do if I no longer have the security issues would.

    What can I do if I no longer have the security issues would.

    I don't know what you are trying to ask ?

  • IRecruitment conversion issue for internal applicants

    Hi,
    We are doing conversion from legacy to oracle irecruitment. When converting external applicants, things have gone fine. I used Create_user and registered_user_application API's.
    Now for internal applicants conversion, its giving me lot of problems. If i use registered_user application API, its end dating his existing person and assignment record and creating a new applicant record.
    But i need to update his person record with person_type status to EMP_APL. Is there any way to do this?
    Thanks in advance
    kumar

    Hi,
    Thank you for your reply.
    Actually i tried with hr_applicant_api.apply_for_job_anytime. This API takes person_id and vacancy_id as parameters and updates the person record with person_type status to 'EMP_APL' and creates one more assigment record with user_status 'Active Application'
    Now my issue is resolved.
    Thanks
    Kumar

  • Adobe Pro 9 Extended, Word 07, Windows XP text and line conversion issues (already checked for correct monitor settings)

    I am coverint a 35 page catalog from word 07 ..... it is built with tables listing prodcts, descriptions and prices.   Some text is faded out, some table lines end up thicker, some don't appear at all.   It will primarily be a web doc but I also tried optimizing for print and issues were still there.   Checked all discussions could not locate similar content.  Thanks for your help!!!!!

    For the replace and delete pages, I can only guess that you are messing up some of the bookmarks or links in the page from what I think you have based on the description. I would work on copies between each stage so that you can at least go back to the last success stage. If possible, you are better to go back and do the modifications in the original page and the recreate the PDF. If that is not possible, then maybe a better explanation of how you are creating the PDF would help folks understand your process fully and suggest a solution.
    On the latter, I would do a repair on Acrobat. However, it may be in the process you are using in the conversion from WORD. How are you creating the PDF from WORD? Have you updated AA9 and not simply have 9.0? The confusing point is that you talk about Distiller for getting the PDF from WORD. Distiller is often involved, but only behind the scenes and normally you either print to the Adobe PDF printer, use PDF Maker, or use the MS plugin for PDF creation. So when stating Distiller, it is unclear what process you are using since none of the methods I mention state the use of Distiller even if it is used in the background.

  • Long term Planning - capacity issue

    Does any one have a way of running Long Term Planning in SAP.
    When checking CM38 for production volumes, the start dates of
    the planned orders always fall into the previous month from the
    forecast (the monthly forecast is always placed on the first day
    of the period and due to lead time scheduling the planned orders
    to satisfy that forecast fall into the previous month). If i check the
    capacity it show in same month for different month requirment.( it is clubing the requirment)
    Though capacity scene was created from June to August , system shows loading from May month.
    Month wise loading and availability are shown clubbed in capacity planning sheet.
    Thanks in advanc....

    Mukesh,
    To change the forecast from occuring at start of period ( month) you can always select the Schedule line Tab in MD61,MD62. then select period indicator as Day format as shown below
    Per. Ind          Date              Qty
    D     17.05.2010     30
    D     15.06.2010     40
    D     15.07.2010     50
    System will then plan PIR (forcast) based on dates assigned by user instead of being placed on the first day
    of the period. This will prevent forcast to fall into the previous month. Also it will resolve the capacity issue you are facing.
    If you have more questions please come back.
    thanks,
    Ram

  • Currency conversion issue in SPM. We are getting incorrect results with SPM conversion function from one of the document currency to USD.

    Currently we are using SPM 2.0 version and we have been facing currency conversion issues.
    Please help me in following aspects.
    1) Where actually currency conversion happens in SPM. Is it the global program which does the conversion or other way.
    2) We have conversion issue for one of the currency where conversion function is giving incorrect results when converting from one of the document currency to USD. here The respective document currency is considering the 1:1 ratio with Dollar which is actually incorrect.
    3) We have verified in both BI side(currency tables) and even ECC side.
    Please help me in understanding this issue and let me know if you need more information on this.
    Its an production issue and appreciated your immediate inputs.
    Thanks
    Kiran

    Hi Arun,
    The following information may be helpful to you.The SSA_HELPER_PROGRAM has options regarding currency settings.
    EXCH_RATE_TYPE: This flag governs the exchange rate type which will be used for currency conversion in data management. For example if RSXAADMIN contains an entry EXCH_RATE_TYPE = „ZSPM‟ then the conversion type used for currency conversion is ZSPM. The default value for the exchange rate type is „M‟. More details can be found in the note 1278988.
    CURRENCYCONVERSION: By default data management converts all the measures in transaction currency to reporting currency and copies over to the corresponding measure in reporting currency. If the measure in reporting currency is already available in source it might be desirable to disable the currency conversion. To disable the conversion you can make an entry CURRENCYCONVERSION = „ „ in the table RSXAADMIN. This can also be achieved by running the program SSA_HELPER_PROGRAM with the option DEACTIVATE_CURRENCYCONVERSION. The conversion can be reactivated by running the same program with option ACTIVATE_CURRENCYCONVERSION.
    UNITCONVERSION: Similar to above. To deactivate unit conversion you can use the program with option and DEACTIVATE_UNITCONVERSION and to reactivate ACTIVATE_UNITCONVERSION. By default both the conversions are switched on
    EXTERNAL_CURRENCIES: Normally most of the international currencies are stored with two decimal places however certain currencies do have 0 and 1 decimal place too. For example JPY has 0 decimal places. SAP internal format stores even these currencies with 2 decimal places and at the time of display it changes the value to right decimal places. In case a file from external source is loaded to SPM it might have the format with 0 decimal places in the file. To convert it to SAP standard format post processing needs to be done on this value. If that is the case you can set the flat EXTERNAL_CURRENCIES = „X‟ in the table which will enable the post processing for these values. This flag can also be set and reset using the helper program using the option TURNON_EXT_CURRENCY_FORMAT and TURNOFF_EXT_CURRENCY_FORMAT.
    Kind Regards,
    John Harris
    Senior Support Engineer, SAP Active Global Support

  • File Content Conversion issue in PI 7.1

    Hi Experts
    I am working on a file to Proxy scenario, I am getting a flat file with , separated but my file will have multiple nodes and I need to do the content conversion and map it to the following structure
    Interface Header
      InterfaceName
      UserID
      Date
      Time
    Journal Entries (1 - Unbounded)
        DocumentHeader
           DocumentDate
           DocHeadetext
           postingDate
        DocumentLineItems
          lineItemno
          lineitemText
          postingkey
    InterfaceTrailer
      Noofrecords.
    Here the problem :I have declared the InterfaceHeader, DocumentHeade,DocumentLineItems and Interface trailer but for Journal entries node what are all the parameters to declare in the content conversion
    please let me know if there are any solutions for this coples structure (content conversion)
    Thanks
    PR

    <?xml version="1.0" encoding="UTF-8"?>
    <!-- New document created with EditiX at Thu May 12 18:57:06 EDT 2011 -->
    <xsd:schema targetNamespace="http://pi.dvn.com/fa/app/ecc/journalEntries/10" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://pi.dvn.com/fa/app/ecc/journalEntries/10">
         <xsd:element name="MT_JournalEntryVouchers" type="DT_JournalEntryVouchers"/>
         <xsd:complexType name="DT_JEHeader">
              <xsd:annotation>
                   <xsd:documentation xml:lang="EN">Journal Entry Header structure</xsd:documentation>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="documentDate">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="docHeaderText" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="25"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="postingDate">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="companyCode">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="4"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="currency" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="5"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="documentType">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="2"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="transactionCode">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="20"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="referenceNumber" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="16"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="accrualReasonForReversal" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="2"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="accrualReversalDate" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="taxCalculationFlag" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="1"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
              </xsd:sequence>
         </xsd:complexType>
         <xsd:complexType name="DT_JELineItems">
              <xsd:annotation>
                   <xsd:documentation xml:lang="EN">Journal Entry Line Items structure</xsd:documentation>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="lineItemNumber">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="3"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="lineItemText" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="50"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="postingKey">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="2"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="companyCodeLineitem">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="4"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="accountNumber">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="17"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="transactionAmount">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="13"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="costCenter" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="accountType">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="1"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="wbsElement" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="8"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="quantity" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="13"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="unitOfMeasure" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="3"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="productionDate" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="tradingPartner" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="6"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="materialNumber" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="18"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="paymentKeyTerms" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="4"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="paymentBlockKey" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="1"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="paymentMethod" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="1"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="paymentMethodSupplement" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="1"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="baselineDate" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="witholdingTaxCode" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="2"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="payer_payeeNumber" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="jointVenture" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="6"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="equityGroup" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="3"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="partnerAcctNumber" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="recoveryIndicator" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="2"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="billingIndicator" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="2"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="orderNumber" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="12"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="profitCenter" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="partnerProfitCenter" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="assignment" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="18"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="referenceKey" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="12"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="transactionType" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="2"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="amountInLocalCurrency" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="13"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="amountInGroupCurrency" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="13"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="taxCode" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="2"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="splGLIndicator" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="1"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="assetTransactionType" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="3"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="xref2" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="12"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
              </xsd:sequence>
         </xsd:complexType>
         <xsd:complexType name="DT_JournalEntryRecord">
              <xsd:annotation>
                   <xsd:documentation xml:lang="EN">Record Set for Journal Entry</xsd:documentation>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="InterfaceHeader" type="DT_InterfaceHeader"/>
                   <xsd:element name="journalEntries" type="DT_JEDocument" maxOccurs="unbounded"/>
                   <xsd:element name="InterfaceTrailer" type="DT_InterfaceTrailer"/>
              </xsd:sequence>
         </xsd:complexType>
         <xsd:complexType name="DT_JEDocument">
              <xsd:annotation>
                   <xsd:documentation xml:lang="EN">Journal Entry Document Data Type</xsd:documentation>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="documentHeader" type="DT_JEHeader"/>
                   <xsd:element name="documentLineItems" type="DT_JELineItems" maxOccurs="unbounded"/>
              </xsd:sequence>
         </xsd:complexType>
         <xsd:complexType name="DT_InterfaceTrailer">
              <xsd:sequence>
                   <xsd:element name="numberOfRecords" type="xsd:string" minOccurs="0"/>
              </xsd:sequence>
         </xsd:complexType>
         <xsd:complexType name="DT_JournalEntryVouchers">
              <xsd:annotation>
                   <xsd:documentation xml:lang="EN">Journal Entry Voucher Interface structure</xsd:documentation>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="JournalEntryRecordSet" type="DT_JournalEntryRecord"/>
              </xsd:sequence>
         </xsd:complexType>
         <xsd:complexType name="DT_InterfaceHeader">
              <xsd:sequence>
                   <xsd:element name="interfaceName" type="xsd:string"/>
                   <xsd:element name="userID" type="xsd:string" minOccurs="0"/>
                   <xsd:element name="runDate" type="xsd:string" minOccurs="0"/>
                   <xsd:element name="runTime" type="xsd:string" minOccurs="0"/>
                   <xsd:element name="testRun" type="xsd:string" minOccurs="0"/>
              </xsd:sequence>
         </xsd:complexType>
    </xsd:schema>

Maybe you are looking for