Assigning an identifier

I have the following table TEST3 with data as shown below.
I need to identify the records that have the same XLS and LORENTION values, but under one condition.
The condition is that if you look at the data ordered by seq asc, the records where seq in
(148206, 148207) should have a different identifier than the record where seq = 148215, although they all
have the same XLS and LORENTION values. The reason is because they are separated by a different XLS and LORENTION
set of records (seq in (148211, 148212, 148213, 1482114)).
In other words, I need a way to read record by record in ascending order of SEQ, assign an identifier for the same XLS and LORENTION values until it hits a different set of XLS and LORENTION values.
Any help will be much appreciated.
CREATE TABLE TEST3
SEQ NUMBER(28,7),
XLS VARCHAR2(255 BYTE),
CANS VARCHAR2(255 BYTE),
LORENTION VARCHAR2(255 BYTE),
COLOR VARCHAR2(255 BYTE)
Insert into test3
(SEQ, XLS, CANS, lorention, COLOR)
Values
(148206, 'Roucotine -Rs', 'Atscks, Sams', 'terss', 'required');
Insert into test3
(SEQ, XLS, CANS, lorention)
Values
(148207, 'Roucotine -Rs', 'Atscks, Polaris ', 'terss');
Insert into test3
(SEQ, XLS, CANS, lorention, COLOR)
Values
(148207, 'Roucotine -Rs', 'Atscks, Polaris ', 'terss', 'yellow');
Insert into test3
(SEQ, XLS, CANS, lorention, COLOR)
Values
(148207, 'Roucotine -Rs', 'Atscks, Polaris ', 'terss', 'dark red');
Insert into test3
(SEQ, XLS, CANS, lorention, COLOR)
Values
(148207, 'Roucotine -Rs', 'Atscks, Polaris ', 'terss', 'red');
Insert into test3
(SEQ, XLS, CANS, lorention, COLOR)
Values
(148211, 'Roucotine -Rs', 'Gdse', 'tebbbbbb', 'not used');
Insert into test3
(SEQ, XLS, CANS, lorention)
Values
(148212, 'Roucotine -Rs', 'Gdse, ee', 'tebbbbbb');
Insert into test3
(SEQ, XLS, CANS, lorention)
Values
(148213, 'Roucotine -Rs', 'Gdse, Right', 'tebbbbbb');
Insert into test3
(SEQ, XLS, CANS, lorention)
Values
(148214, 'Roucotine -Rs', 'Gland, rrt5', 'tebbbbbb');
Insert into test3
(SEQ, XLS, CANS, lorention, COLOR)
Values
(148215, 'Roucotine -Rs', 'Rews', 'terss', 'required');
Insert into test3
(SEQ, XLS, CANS, lorention, COLOR)
Values
(148215, 'Mac', 'Rews', 'terss', 'dark red');
Insert into test3
(SEQ, XLS, CANS, lorention, COLOR)
Values
(148215, 'Roucotine -Rs', 'Rews', 'terss', 'red');

version: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bi
This is the source:
select seq, xls, lorention, cans, color from test3 order by seq;
I need something like:
select seq, xls, lorention, cans, color, max(seq) over (partition by xls, lorention) id from test3 order by seq;
The first 5 records should have one id because the xls and lorention are the same, then the next record, since lorention value changes, it should have a different id for rows 6 - 9. row 10 should have a different id because lorention value changes. Row 11 should have a different id because xls value changes. row 12 should have a different ID because xls changes. If you look at it, row 10 and row 12 have the same xls and lorention values as rows 1-5, but they need a different id because there are other xls and lorention values in between. In the example above, I used max(seq) as the identifier, but this won't work because rows 10 -12 should have different id but have the same seq values.

Similar Messages

  • How can i assign an identifier to a movieclip using AS2 ???

    Hey guys, i'm using the scrolling pane component in my
    project. i used to enter in the content path, the identifier of the
    movieclip which i set through the library. But now i wanna give it
    a movie clip that i've created in my code...so how can i assign an
    identifier to a movieclip using AS2 so that i can use it with my
    componenets ???? THANX

    I'm trying to make a script that goes through a folder recursively, checks for every folder if it's name is "template", and if so it changes the icon of that folder to an icon
    I chose.
    I searched for an answer here, and I've only managed to find a way to assign an icon to a shortcut, but not to an existing file.
    Thanks in advance (:

  • Assigning Numeric Identifiers Based on Group

    Hi there,
    Currently I have a set of data consisting of an unique identifier (ID), four product properties (Brand.1.1, Brand.1.2, ...), and a preference.
    What I would like to do is for each product category (i.e. Brand, Price, and Preference) is assign numeric identifiers to values - that is, common values will be assigned the same identifier within each category. If possible, I would also like a legend to be
    created automatically. It is possible that the same input exists in different categories, but they should not be seen as equivalent to each other.
    My current method involves creating a chart of unique values for each category and using lookup functions but this is a slow process when I have multiple product categories to go through (Size, Price, Brand, Warranty, Features, Delivery, etc.).
    Example:
    ID
    Brand.1.1
    Brand.1.2
    Price.1.1
    Price.1.2
    Preference
    ID001
    Apple
    Cereal
    50
    25
    Cereal
    ID002
    Cereal
    Bread
    32
    41
    Cereal
    ID003
    Bread
    Apple
    50
    32
    Apple
    ID004
    Cereal
    Eggs
    41
    25
    Eggs
    Assign numeric values:
    Brand.1.1
    Brand.1.2
    Price.1.1
    Price.1.2
    Preference
    ID001
    1
    3
    1
    2
    1
    ID002
    3
    2
    3
    4
    1
    ID003
    2
    1
    1
    3
    2
    ID004
    3
    4
    4
    2
    3
    Legend:
    Brand:
    Apple - 1
    Bread - 2
    Cereal - 3
    Eggs -4
    Price:
    $50 - 1
    $25 -2
    $32 -3
    $41 -4
    Preference: (Notice how it has same input-values as Brand but doesn't necessarily assign the same numbers since it's a different category)
    Cereal -1
    Apple -2
    Eggs -3
    I imagine VBA will be required but any thoughts/help would be appreciated.

    Hi,
    If you don't want to use VLOOKUP function, also ,you'd like the legend to be created automatically. The only way I can think is VBA code.
    As this forum is for discussing Office Client issue, to help you better, I suggest you submit a new case on MSDN forum as they will be more professional on your issue.
    http://social.msdn.microsoft.com/Forums/office/en-US/home?forum=exceldev
    Thanks for your understanding.
    Wind Zhang
    TechNet Community Support

  • Assign group identifier during ETL? Need suggested approach

    Ok, so I need to pull in some data to a "staging" table.  During the process that loads the destination db, I need to assign a value to a field that will be a unique identifier for a group of records that share the same values for a set of
    columns.
    The overall process looks like kinda like this
    Database A -> ETL -> Staging Database B -> ETL -> Database C
    I suppose one way to do this is to simply use a calculated column in the statement that selects the data to be loaded into C.  
    In  a staging  table in B, there will be records that are related to one another based on a set of columns.  Its this set of column values that I would want to use to generate a "calculated" group identifier in the destination table
    in C.
    Suggestions?  I suppose my main concern is the generation of the group id, but what to do with those records that couldnt be assigned a group id?

    I need to assign a value to a field that will be a unique identifier for a group of records that share the same values
    for a set of columns.
    Sounds like using DENSE_RANK function to generate unique value for each group of values.
    You can also use HASHBYTES function passing the concatenated list of columns and generated byte value corresponding to
    them to identify the group of records
    see an example here
    http://visakhm.blogspot.in/2014/06/ssis-tips-implementing-scd.html
    Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

  • Disk Utility assigns incorrect identifier to external drive

    Hi, I am running 10.7.5, I backup my notebook to a 500GB drive using Time Machine, after a recent backup my 2TB drive is labled as the 500GB BACKUP drive in disk utility and not mounted under finder.  I tried everything.  I am unable to unmount the drive in disk utility, disk info insists it is a 500GB drive, TERMINAL drive info insists the drive is also a 500GB drive.
    I am assuming drive data is stored somewhere on my local OS and this reference table became corrupted, there is no way a 2TB drive can now become a 500GB BACKUP drive overnight.  Using TERMINAL I can open and view the content on the disk.  Funny thing is the 2TB drive is a WD and the 500GB is a Seagate, Disk Utility gets this info right, but otherwise insists the drive is my Time Machine backup drive and Time Machine wants to write a backup <- I turned this off for now in fear that Time Machine will reformat the disk and I will loose data on my 2TB drive.  Reformating the 2TB drive is not an option, verifying the disk claims it requires repair, not an option.  All I need is the drive to lablled correctly so all the processes can assume as normal.
    I am 100% sure Apple has terminal command to repair the local OS disk reference table so all external drives can be relisted (meaning reidentified) correctly.

    Also worth noting that, if your drive has a FireWire interface, use that instead of USB. While the theoretical max speed of USB2 is faster than FireWire 400, in real-world conditions FW will blow the socks off USB. And if you're purchasing an external drive, it repays on the long run to pay a little more to purchase one with FW. And, of course, if FW400 is faster, FW800 is out of sight.

  • Assigning identifiers automatically or using the base value in rules

    The question is rather simple. I want to order the instances of an entity. How these instances are ordered is unimportant. The problem is that the only information available about the instances is the age, which may be the some for multiple instances and thus makes it impossible to order. Is there anyway to assign an identifier automatically to apply this ordering, say from 0 ... the number of instances - 1 or is it possible to use the base value of an instance in rules?

    Once we get into the realm of "assign randomly" we're outside the scope of "repeatable business rules" which is what OPA is trying to allow you to automate.
    That said "out of the box" features to do either/both:
    1) random number generation;
    2) unique entity identification
    have both come up before. It would be worth communicating with your Oracle product rep to make sure they know about how desirable you would find those features.
    But it still sounds like you might be able to do this with rules...
    Is the "discount" variable or is a voucher simply for "free tickets"? If all vouchers are always just for "whole free tickets" then they can be treated anonymously very easily. You can then look at how many tickets you have and how many you can get for free and work sequentially down the list and remove the X most expensive tickets from the total price. If the last "free ticket" is the same price as some other ticket then from a "final price for all tickets perspective" there's no difference between getting all tickets at that price at number free/total number at that price * price and getting the number free for free + full price for the rest.
    So again, so long as you don't need to know which ticket and which voucher it is all possible. The major complexity is probably in constructing a "rank" but this can be done using an inferred relationship to identify a "rank" (ie the relationship identifies the set of other tickets with a greater value and then you can do an instancecount on the relationship to give you a rank).
    I'm assuming you're using 10.4?
    By "rank" I mean that the set (1, 2, 5, 5, 7, 9) would have the following "rank order" (1, 2, 3, 3, 5, 6) when ranking from smallest to largest.

  • CannotUser execute task -- " anonymous " has not been assigned task

    Hi,
    I'm trying to build a prototype a workflow using WLI Integration(WLPI).
    I've created a workflow using WLPI Studio and am able to start the instances using
    JMS messages. However, when I try to execute one of the task which I 've assigned
    to user "admin" I get the following error. Please note that I have connected to
    WLPI using "admin" user only and got a handle to worklist. It seems to be an issue
    with security realm but I'm not able to figure out what it is...Can somebody help
    me on it???
    <Mar 26, 2003 5:46:55 PM EST> <Error> <BPM> <500212> <<wlpirequest>
    <started>2003-03-26 17:46:55.332</started>
    <requestor><anonymous></requestor>
    <templateid>1</templateid>
    <template-name>Test</template-name>
    <templatedefinitionid>1</templatedefinitionid>
    <instanceid>22001</instanceid>
    <actions>
    <error time="2003-03-26 17:46:55.362">WorkflowException: User "<anonymous>"
    has not been assigned task "Identify Samp
    les".</error>
    </actions>
    <completed>2003-03-26 17:46:55.372</completed>
    </wlpirequest>
    >
    User "<anonymous>" has not been assigned task "Identify Samples".
    User "<anonymous>" has not been assigned task "Identify Samples".

    Firstly Thanks for the response Chris.
    I'm not using any combination of older version of WLS and 7.0. I've downloaded
    the trial version of weblogic platform 7.0 and working on it.
    I forgot to mention one thing that in order to fix the problem I have modified
    the wlpi-ejb.jar to removethe method permissions.
    Chris Stead <[email protected]> wrote:
    Vinkal,
    Since I see the requester identified as <anonymous>, I am assuming you
    are trying some combination of inter operability between older versions
    of WLS and 7.0. If that is the case, the following link may provide
    some insight for your problem:
    http://edocs.bea.com/wls/docs70/upgrade/upgrade6xto70.html#1050157
    The only caveat is the fact that you are logged in as admin, which
    should be an authenticated user for BPM, therefore not represented by
    the guest user...Have you modified the permissions of the admin user?
    Specifically removed the Execute_Template permission from admin?
    Cheers,
    Chris
    Vinkal wrote:
    Hi,
    I'm trying to build a prototype a workflow using WLI Integration(WLPI).
    I've created a workflow using WLPI Studio and am able to start theinstances using
    JMS messages. However, when I try to execute one of the task whichI 've assigned
    to user "admin" I get the following error. Please note that I haveconnected to
    WLPI using "admin" user only and got a handle to worklist. It seemsto be an issue
    with security realm but I'm not able to figure out what it is...Cansomebody help
    me on it???
    <Mar 26, 2003 5:46:55 PM EST> <Error> <BPM> <500212> <<wlpirequest>
    <started>2003-03-26 17:46:55.332</started>
    <requestor><anonymous></requestor>
    <templateid>1</templateid>
    <template-name>Test</template-name>
    <templatedefinitionid>1</templatedefinitionid>
    <instanceid>22001</instanceid>
    <actions>
    <error time="2003-03-26 17:46:55.362">WorkflowException: User "<anonymous>"
    has not been assigned task "Identify Samp
    les".</error>
    </actions>
    <completed>2003-03-26 17:46:55.372</completed>
    </wlpirequest>
    User "<anonymous>" has not been assigned task "Identify Samples".
    User "<anonymous>" has not been assigned task "Identify Samples".

  • Identifier in AS3

    Hello!
    I have just started with AS3, I have written in AS2 before.
    In AS2 I would just create a movieclip to the library and then put an identifier on it, after that i would code and use that identifier to add the movieclip to the stage.
    Usually in AS2 it would be this:
    attachMovieClip("Identifier", "New name", index);
    or
    addChild()
    But in AS3 how am i supposed to do it? Is there some kind of way to assign an identifier to a movieclip that is in the library for me to use in as3?
    Damn migration issues -_-.
    Thanks in advance!

    In As3 you take similar steps to set the object up, giving it a Class ID just like you would in AS2 after selecting Export for Actionscript in the Linkage interface.  THen, to bring an instance to the stage you just add a new one.  Let's say you assign the object a Class ID of "Thing"
    var newOne:Thing = new Thing();
    addChild(newOne);

  • Button order and routing from PS menu not working

    Ugh, this is driving me crazy.
    When authoring a Blu-ray, I've gone through the same steps since I started but all of a sudden the menus I'm creating in PS CS5 for Encore CS5 are not working and for the life of me I can't figure out why.
    The problem I'm having is that I set everything up in Photoshop then import the menu into Encore however when using the navigation of a remote, scrolling down skips some buttons and doesn't cycle through them normally.
    For example, let's say I have eight buttons defined in a PSD.
    1
    2
    3
    4
    5
    6
    7
    8
    When I preview or do a test burn, the highlight will stop on 1 and 2 but skip 3 and 5 and other random button definitions.  And then when it gets to the last, it doesn't cycle back to the first.
    I have everything set up correctly as far as I know - group layers prefaced with (+), highlight cursor prefaced with (=1), etc.  And the order looks good in Encore.
    Extremely frustrated, anyone else having this problem in CS5?  I can up the PSD if anyone wants to check it out.
    Thanks,
    Tom

    Can you post a screenshot of the menu with button routing on?
    I second Stanley's request, and please Crop into that area, and also Save your JPEG, or PNG, with adequate resolution for people to see the numbers on your Button Routing. Also, if you have any specific desires for the order of your Button Routing, please define that.
    Note that En will Automatically Route Buttons, based on their Layer Set Order in PS. If you have done some moving around of the order of Button Layer Sets, or have done some Copy/Duplicate, then what you think the order should be, but it might not be so. En will start at the bottom of the Layers Panel, and assign the identifier, Button 1 (regardless of what name you might have assigned), to the lowest Button, and working up, one Button Layer Set at a time, until it reaches the top. Can you also post a screen-cap of your Button Layer Sets (can be closed for a clear shot of the entire Palette), with the Layers Palette showing clearly, and the image with the Buttons showing near by? That could also be very helpful.
    Good luck,
    Hunt

  • How to have both Single and Mutilple Selection in a table?

    Hi ,
    I have a page with an advanced, there is a multiple selection for the table for deleting row. Now I want to have a single selection column for other purpose. But it does not seem that we can have both in a table.
    If I implement SingleSelection myself by using OAMessageRadioButton, from dev guide, I need to programmatically assign radio btton all the same
    name by calling setName() for each radio button and also assign an identifying value for each bean. I can radio for radio button, but how can I assign value for each radio button bean when they are in a table? Will it possible to use View Attribute of radio button bean property?
    thanks
    Lei

    Lei, its possible to have both in ur table! You can add a single selection child to your table. Then u can add messagecheckbox as last column of table, which can be attached to a transient VO attribute.
    --Mukul                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • How to change default page in webclient

    Hi,
    For business role Ic_agent, the default page is identify account when you login. I wanna change the default page to interaction record.How to configure? Thanks!
    BR,
    ROBERT

    Hi Robert
    1. check which is the Navigation bar assigned to the profile assigned to Agent.
    2.. follow path : Customer Relationship Management  Interaction Center WebClient Basic Functions Define Navigation Bar Profiles, look for the navigation assigned to your profile.
    3. selecting your Navigation bar profile from Define Profiles and goto Assign Entries to Profiles, here you have Navigation Bar ID and Tittle. Against each of the navigation bar id a position has been assigned.
    4. The lowest position assigned to Navigation bar Id will be set as default.
    In your profile lowest position has been assigned to Identify Account, you assign even lower position to whichever ID you want to assign as default.
    Hope this will help.
    Rgds
    Mallikarjun

  • Using local session bean interface from web container using EJB 3.0

    Hi,
    How can you use a local session bean interface from Java (rather than data controls) in a web container using EJB 3.0?
    I can use a remote interface by looking up InitialContext, but I can't find a local interface this way (even from another session EJB). I can use a local interface from an EJB using annotation "EJB", but as I understand, this is not available in the web container.
    If I try to add an ejb-jar.xml file, these seems to mess up by project...
    Hope you can help.
    Roger

    The portable way to retrieve an EJB reference in Java EE is to either inject it or look it up via the
    component's private naming environment. The simplest way is :
    @EJB
    private DocumentManager dm;
    The global JNDI name is only used as an implementation specific way to uniquely assign an
    identifier to a specific Remote EJB. It's best for this not to appear directly in the source code.
    There's more on global JNDI names in our EJB FAQ :
    https://glassfish.dev.java.net/javaee5/ejb/EJB_FAQ.html
    The alternative to annotations is to use an ejb-ref to declare the ejb dependency. The ejb-ref
    is declared in the standard deployment descriptor corresponding to the component doing the
    lookup. Each ejb-ref has an ejb-ref-name, e.g. <ejb-ref-name>DM_ref</ejb-ref-name>
    The code looks up the ejb-ref-name relative to the java:comp/env namespace to retrieve the
    EJB reference.
    DocumentManager dm = (DocumentManager)
    new InitialContext().lookup("java:comp/env/DM_ref");

  • IDOC Error Number:29 : Error in ALE service

    Hi Experts,
    Already checked & read couple of threads on this but no help.
    I have a scenario to send Vendors information out from my ECC system to MDM via XI.
    I am using IDOC Extension ZCREMAS to do so.
    Steps already done:
    Sender System: ECC Dev System
    Receiver Syste: XI Dev system
    Port Config: SAPXI ( RFC Destination as XI system )
    Partner Profile: XI Dev system->Outbound Parameters -> CREMAS & SYNCH ( CREMAS -> Configured the Z extension & Message Function )
    Business Distribution Model : Defined Sender, Receiver & Message Type as Above.
    When I try to Generate the partner profile it gives message 'No messages have been defined for the selection conditions in the model' with Status ICON as Green.
    Now if I go to BD14 and try to execute the program for message type CREMAS it says :
    63 master IDocs set up for message type CREMAS.
    0 communication IDoc(s) generated for message typeCREMAS
    If I try to debug I find the problem in FM ALE_MODEL_DETERMINE_IF_TO_SEND  While calling ALE Distribution model where it failes to determine the Sending system as : DEV.
    However, I am not sure how to resolve this error or am I missing any other setting in ECC?
    If I try to generate test IDOC via WE19 it works fine.
    Thanks,
    Abhinav.

    Your sender destination is wrong, check with SCC4, i.e. make sure that you have given correct logical sytem name in sender and receiver in the model view.
    Also... be sure that the LS identifier you're using is actually assigned to the client you expect (SCC4 transaction let's you look at the clients and their assigned LS identifiers)

  • Disk Information Shown in Disk Utility

    Hi MP Folks
    My 2012 Mac Pro got 4 physical disks installed, 1 x SSD + 3 x HDD. All  bays are used. As you know, clicking the blue Info button at the top of the Disk Utility window may bring your the basic facts and extra information about the disks listed in the left pane.
    I thought the information given there should be same kind of data in the same format, but on my Mac Pro only the first 15 items are the same, the remaining information varies from disk to disk, as shown below for the disks from Bay 1 to 4.
    As you can see above, after S.M.A.R.T Status, the items are different. I got a few questions here.
    1. Why does the APPLE HDD HDS723020ALA640 in Bay 2 have no further information while all others have more reliability data collected?
    2. Why does the WDC WD10EAVS-00D7B0 in Bay 4 have a different Partition Map Scheme: "Apple Partition Map" instead of "GUID Partition Table"? I did use the same way that I did on other disks to partition and initialise this 1TB disk.
    3. In stead of assigning Disk Identifier in the order of drive bay, why does "Bay 2" have "disk3" and "Bay 4" have"disk1"?
    Thank heaps in advance.
    Regards,
    B

    Data are recorded on the disk surface with a semi-redundant error-correcting code. Hardware and firmware in the drive are used to accomplish correction, if possible. Small bursts of errors are often correctable, but sometimes it takes many, many re-tries to obtain correctable data. Failure to obtain correctable data after many re-tries produces an I/O Error.
    I/O Error tells you the data pattern in a particular block you are trying to read is very difficult to read [most likely], or possibly was written wrong or partially over-written with other data if the power failed while writing [extremely unlikely].  This is most often caused by subtle changes to the magnetic regions that make up the physical data, causing  a few bits to flip.
    Getting an actual I/O Error is a desperate situation, much more extreme than the accumulation of minor data errors in the counter. There are data there, but they cannot be read. A drive with I/O Error has Bad Blocks, or may be failing completely. A drive with an accumulation of read errors means some blocks needed to be re-tried before correctable data were read.
    The drive notes these problems, and maintains a "suspect list" of block numbers that are candidates for block substitution, and reports how many are on this list in its SMART status (accessible from Internally-mounted drives only). The drive is capable of substituting a spare block nearby, but cannot substitute another block unless and until new data are supplied, because doing so may poke a hole in the middle of a file.
    Re-Writing the drive [traditionally with one pass of Zeroes] supplies that new data, and gives the drive an opportunity to check for proper data retention immediately after writing. Any blocks found not able to retain the new data have spares substituted, up to a maximum number of blocks in one pass (typically ten blocks).
    Large scale studies performed by google in their servers indicate that drives that develop Bad Blocks in 24/7 use will typically need to be removed for too many Bad Blocks within 6 months.

  • XPath Expression in document definition

    I am trying to use "XPath Expression1" for 894 in the document definition under XPath in order to retrieve invoice number so that, it would be used in BAM but I am not getting successful in putting exact XPath expression for invoice number. I am using as below
    /Transaction-894/Segment-G82/Element-861
    Pls suggest is there any wrong in the XPath?
    Regards,
    Suneel Jakka

    Here is the XSD for which I am trying XPath for the "Element-861" under "Segment-G82"..
    Pls suggest me..
    <?xml version="1.0" encoding="UTF-8"?>
    <!-- Automatically generated by EDIFECS SpecBuilder (http://www.edifecs.com) -->
    <xsd:schema xmlns="http://www.edifecs.com/xdata/200" targetNamespace="http://www.edifecs.com/xdata/200" xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="1.0" elementFormDefault="qualified">
         <xsd:annotation>
              <xsd:appinfo>
                   <FileName>C:\Documents and Settings\jakkasun\Desktop\11g\X12_5010_894.ecs</FileName>
                   <InternalID>{0840BE5F-3518-463D-A128-D73D96D4A5D2}</InternalID>
              </xsd:appinfo>
         </xsd:annotation>
         <xsd:element name="Transaction-894" type="Transaction-894"/>
         <xsd:complexType name="Transaction-894">
              <xsd:annotation>
                   <xsd:documentation>This X12 Transaction Set contains the format and establishes the data contents of the Delivery/Return Base Record Transaction Set (894) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to enable a Direct Store Delivery (DSD) vendor to communicate the details of a DSD delivery and is to be used during the check-in procedure. </xsd:documentation>
                   <xsd:appinfo>
                        <UNMKey>Full|CodeList|-&lt;Parent Node ID&gt;.&lt;Index&gt;|Composite|-&lt;Node ID&gt;|Element|-&lt;Node ID&gt;|Loop|-&lt;Node ID&gt;|Segment|-&lt;Node ID&gt;|Transaction|-&lt;Node ID&gt;|ReplacementCharacter|_|InternalSeparator|-</UNMKey>
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="Internal-Properties" type="Internal-Properties" minOccurs="0"/>
                   <xsd:element name="Segment-ST" type="Segment-ST"/>
                   <xsd:element name="Segment-G82" type="Segment-G82"/>
                   <xsd:element name="Segment-N9" type="Segment-N9" minOccurs="0" maxOccurs="unbounded" nillable="true"/>
                   <xsd:element name="Loop-LS" type="Loop-LS" minOccurs="0" nillable="true"/>
                   <xsd:element name="Segment-G72" type="Segment-G72" minOccurs="0" maxOccurs="20" nillable="true"/>
                   <xsd:element name="Segment-G23" type="Segment-G23" minOccurs="0" maxOccurs="20" nillable="true"/>
                   <xsd:element name="Segment-G84" type="Segment-G84"/>
                   <xsd:element name="Segment-G86" type="Segment-G86"/>
                   <xsd:element name="Segment-G85" type="Segment-G85"/>
                   <xsd:element name="Segment-SE" type="Segment-SE"/>
              </xsd:sequence>
              <xsd:attribute name="Type" default="Transaction" type="xsd:string"/>
              <xsd:attribute name="ID" default="894" type="xsd:string"/>
              <xsd:attribute name="Name" default="Delivery/Return Base Record" type="xsd:string"/>
              <xsd:attribute name="XDataVersion" fixed="2.0" type="xsd:string"/>
              <xsd:attribute name="Standard" fixed="X12" use="required" type="xsd:string"/>
              <xsd:attribute name="Version" default="V5010" type="xsd:string"/>
              <xsd:attribute name="GUID" type="GUID"/>
              <xsd:attribute name="CreatedBy" type="xsd:string"/>
              <xsd:attribute name="CreatedDate" type="xsd:dateTime"/>
         </xsd:complexType>
         <xsd:simpleType name="GUID">
              <xsd:restriction base="xsd:string">
                   <xsd:pattern value="\{[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{12}\}"/>
              </xsd:restriction>
         </xsd:simpleType>
         <xsd:complexType name="EDI-Element-String-Type">
              <xsd:simpleContent>
                   <xsd:extension base="xsd:string">
                        <xsd:attribute name="Type" default="Element" type="xsd:string"/>
                        <xsd:attribute name="EDIDataType" type="xsd:string"/>
                        <xsd:attribute name="Macro" type="xsd:string" use="optional"/>
                        <xsd:attribute name="ApplicationInfo" type="xsd:string"/>
                        <xsd:attribute name="ID" type="xsd:string"/>
                        <xsd:attribute name="Name" type="xsd:string"/>
                   </xsd:extension>
              </xsd:simpleContent>
         </xsd:complexType>
         <xsd:complexType name="EDI-Element-Integer-Type">
              <xsd:simpleContent>
                   <xsd:extension base="xsd:integer">
                        <xsd:attribute name="Type" default="Element" type="xsd:string"/>
                        <xsd:attribute name="EDIDataType" type="xsd:string"/>
                        <xsd:attribute name="Macro" type="xsd:string" use="optional"/>
                        <xsd:attribute name="ApplicationInfo" type="xsd:string"/>
                        <xsd:attribute name="ID" type="xsd:string"/>
                        <xsd:attribute name="Name" type="xsd:string"/>
                   </xsd:extension>
              </xsd:simpleContent>
         </xsd:complexType>
         <xsd:complexType name="EDI-Element-Decimal-Type">
              <xsd:simpleContent>
                   <xsd:extension base="xsd:decimal">
                        <xsd:attribute name="Type" default="Element" type="xsd:string"/>
                        <xsd:attribute name="EDIDataType" type="xsd:string"/>
                        <xsd:attribute name="Macro" type="xsd:string" use="optional"/>
                        <xsd:attribute name="ApplicationInfo" type="xsd:string"/>
                        <xsd:attribute name="ID" type="xsd:string"/>
                        <xsd:attribute name="Name" type="xsd:string"/>
                   </xsd:extension>
              </xsd:simpleContent>
         </xsd:complexType>
         <xsd:complexType name="EDI-Element-hexBinary-Type">
              <xsd:simpleContent>
                   <xsd:extension base="xsd:hexBinary">
                        <xsd:attribute name="Type" default="Element" type="xsd:string"/>
                        <xsd:attribute name="EDIDataType" type="xsd:string"/>
                        <xsd:attribute name="Macro" type="xsd:string" use="optional"/>
                        <xsd:attribute name="ApplicationInfo" type="xsd:string"/>
                        <xsd:attribute name="ID" type="xsd:string"/>
                        <xsd:attribute name="Name" type="xsd:string"/>
                   </xsd:extension>
              </xsd:simpleContent>
         </xsd:complexType>
         <xsd:complexType name="EDI-Element-base64Binary-Type">
              <xsd:simpleContent>
                   <xsd:extension base="xsd:base64Binary">
                        <xsd:attribute name="Type" default="Element" type="xsd:string"/>
                        <xsd:attribute name="EDIDataType" type="xsd:string"/>
                        <xsd:attribute name="Macro" type="xsd:string" use="optional"/>
                        <xsd:attribute name="ApplicationInfo" type="xsd:string"/>
                        <xsd:attribute name="ID" type="xsd:string"/>
                        <xsd:attribute name="Name" type="xsd:string"/>
                   </xsd:extension>
              </xsd:simpleContent>
         </xsd:complexType>
         <xsd:complexType name="EDI-Element-Any-Type">
              <xsd:simpleContent>
                   <xsd:extension base="xsd:string">
                        <xsd:attribute name="Type" default="Element" type="xsd:string"/>
                        <xsd:attribute name="EDIDataType" type="xsd:string"/>
                        <xsd:attribute name="Macro" type="xsd:string" use="optional"/>
                        <xsd:attribute name="ApplicationInfo" type="xsd:string"/>
                        <xsd:attribute name="ID" type="xsd:string"/>
                        <xsd:attribute name="Name" type="xsd:string"/>
                   </xsd:extension>
              </xsd:simpleContent>
         </xsd:complexType>
         <xsd:complexType name="Internal-Properties">
              <xsd:sequence>
                   <xsd:element name="Data-Structure" type="Data-Structure" minOccurs="0" maxOccurs="unbounded"/>
              </xsd:sequence>
         </xsd:complexType>
         <xsd:complexType name="Data-Structure">
              <xsd:sequence>
                   <xsd:element name="Lookup" type="Lookup" minOccurs="0" maxOccurs="unbounded"/>
                   <xsd:element name="Property" type="Property" minOccurs="0" maxOccurs="unbounded"/>
                   <xsd:element name="Data-Structure" type="Data-Structure" minOccurs="0" maxOccurs="unbounded"/>
              </xsd:sequence>
              <xsd:attribute name="Name" type="xsd:string"/>
              <xsd:attribute name="GUID" type="GUID"/>
         </xsd:complexType>
         <xsd:complexType name="Lookup">
              <xsd:simpleContent>
                   <xsd:extension base="xsd:string">
                        <xsd:attribute name="Name" type="xsd:string"/>
                   </xsd:extension>
              </xsd:simpleContent>
         </xsd:complexType>
         <xsd:complexType name="Property">
              <xsd:simpleContent>
                   <xsd:extension base="xsd:string">
                        <xsd:attribute name="Name" type="xsd:string"/>
                   </xsd:extension>
              </xsd:simpleContent>
         </xsd:complexType>
         <xsd:complexType name="Segment-ST">
              <xsd:annotation>
                   <xsd:documentation>To indicate the start of a transaction set and to assign a control number</xsd:documentation>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="Element-143" type="Element-143"/>
                   <xsd:element name="Element-329" type="Element-329"/>
                   <xsd:element name="Element-1705" type="Element-1705" minOccurs="0" nillable="true"/>
              </xsd:sequence>
              <xsd:attribute name="Type" default="Segment" type="xsd:string"/>
              <xsd:attribute name="ID" default="ST" type="xsd:string"/>
              <xsd:attribute name="Name" default="Transaction Set Header" type="xsd:string"/>
         </xsd:complexType>
         <xsd:complexType name="Element-143">
              <xsd:annotation>
                   <xsd:documentation>Code uniquely identifying a Transaction Set </xsd:documentation>
              </xsd:annotation>
              <xsd:simpleContent>
                   <xsd:restriction base="EDI-Element-String-Type">
                        <xsd:enumeration value="100"/>
                        <xsd:enumeration value="101"/>
                        <xsd:enumeration value="102"/>
                        <xsd:enumeration value="103"/>
                        <xsd:enumeration value="104"/>
                        <xsd:enumeration value="105"/>
                        <xsd:enumeration value="106"/>
                        <xsd:enumeration value="107"/>
                        <xsd:enumeration value="108"/>
                        <xsd:enumeration value="109"/>
                        <xsd:enumeration value="110"/>
                        <xsd:enumeration value="111"/>
                        <xsd:enumeration value="112"/>
                        <xsd:enumeration value="113"/>
                        <xsd:enumeration value="120"/>
                        <xsd:enumeration value="121"/>
                        <xsd:enumeration value="124"/>
                        <xsd:enumeration value="125"/>
                        <xsd:enumeration value="126"/>
                        <xsd:enumeration value="127"/>
                        <xsd:enumeration value="128"/>
                        <xsd:enumeration value="129"/>
                        <xsd:enumeration value="130"/>
                        <xsd:enumeration value="131"/>
                        <xsd:enumeration value="132"/>
                        <xsd:enumeration value="133"/>
                        <xsd:enumeration value="135"/>
                        <xsd:enumeration value="138"/>
                        <xsd:enumeration value="139"/>
                        <xsd:enumeration value="140"/>
                        <xsd:enumeration value="141"/>
                        <xsd:enumeration value="142"/>
                        <xsd:enumeration value="143"/>
                        <xsd:enumeration value="144"/>
                        <xsd:enumeration value="146"/>
                        <xsd:enumeration value="147"/>
                        <xsd:enumeration value="148"/>
                        <xsd:enumeration value="149"/>
                        <xsd:enumeration value="150"/>
                        <xsd:enumeration value="151"/>
                        <xsd:enumeration value="152"/>
                        <xsd:enumeration value="153"/>
                        <xsd:enumeration value="154"/>
                        <xsd:enumeration value="155"/>
                        <xsd:enumeration value="157"/>
                        <xsd:enumeration value="158"/>
                        <xsd:enumeration value="159"/>
                        <xsd:enumeration value="160"/>
                        <xsd:enumeration value="161"/>
                        <xsd:enumeration value="163"/>
                        <xsd:enumeration value="170"/>
                        <xsd:enumeration value="175"/>
                        <xsd:enumeration value="176"/>
                        <xsd:enumeration value="179"/>
                        <xsd:enumeration value="180"/>
                        <xsd:enumeration value="185"/>
                        <xsd:enumeration value="186"/>
                        <xsd:enumeration value="187"/>
                        <xsd:enumeration value="188"/>
                        <xsd:enumeration value="189"/>
                        <xsd:enumeration value="190"/>
                        <xsd:enumeration value="191"/>
                        <xsd:enumeration value="194"/>
                        <xsd:enumeration value="195"/>
                        <xsd:enumeration value="196"/>
                        <xsd:enumeration value="197"/>
                        <xsd:enumeration value="198"/>
                        <xsd:enumeration value="199"/>
                        <xsd:enumeration value="200"/>
                        <xsd:enumeration value="201"/>
                        <xsd:enumeration value="202"/>
                        <xsd:enumeration value="203"/>
                        <xsd:enumeration value="204"/>
                        <xsd:enumeration value="205"/>
                        <xsd:enumeration value="206"/>
                        <xsd:enumeration value="210"/>
                        <xsd:enumeration value="211"/>
                        <xsd:enumeration value="212"/>
                        <xsd:enumeration value="213"/>
                        <xsd:enumeration value="214"/>
                        <xsd:enumeration value="215"/>
                        <xsd:enumeration value="216"/>
                        <xsd:enumeration value="217"/>
                        <xsd:enumeration value="219"/>
                        <xsd:enumeration value="220"/>
                        <xsd:enumeration value="222"/>
                        <xsd:enumeration value="223"/>
                        <xsd:enumeration value="224"/>
                        <xsd:enumeration value="225"/>
                        <xsd:enumeration value="227"/>
                        <xsd:enumeration value="228"/>
                        <xsd:enumeration value="240"/>
                        <xsd:enumeration value="242"/>
                        <xsd:enumeration value="244"/>
                        <xsd:enumeration value="245"/>
                        <xsd:enumeration value="248"/>
                        <xsd:enumeration value="249"/>
                        <xsd:enumeration value="250"/>
                        <xsd:enumeration value="251"/>
                        <xsd:enumeration value="252"/>
                        <xsd:enumeration value="255"/>
                        <xsd:enumeration value="256"/>
                        <xsd:enumeration value="259"/>
                        <xsd:enumeration value="260"/>
                        <xsd:enumeration value="261"/>
                        <xsd:enumeration value="262"/>
                        <xsd:enumeration value="263"/>
                        <xsd:enumeration value="264"/>
                        <xsd:enumeration value="265"/>
                        <xsd:enumeration value="266"/>
                        <xsd:enumeration value="267"/>
                        <xsd:enumeration value="268"/>
                        <xsd:enumeration value="269"/>
                        <xsd:enumeration value="270"/>
                        <xsd:enumeration value="271"/>
                        <xsd:enumeration value="272"/>
                        <xsd:enumeration value="273"/>
                        <xsd:enumeration value="274"/>
                        <xsd:enumeration value="275"/>
                        <xsd:enumeration value="276"/>
                        <xsd:enumeration value="277"/>
                        <xsd:enumeration value="278"/>
                        <xsd:enumeration value="280"/>
                        <xsd:enumeration value="283"/>
                        <xsd:enumeration value="284"/>
                        <xsd:enumeration value="285"/>
                        <xsd:enumeration value="286"/>
                        <xsd:enumeration value="288"/>
                        <xsd:enumeration value="290"/>
                        <xsd:enumeration value="300"/>
                        <xsd:enumeration value="301"/>
                        <xsd:enumeration value="303"/>
                        <xsd:enumeration value="304"/>
                        <xsd:enumeration value="309"/>
                        <xsd:enumeration value="310"/>
                        <xsd:enumeration value="311"/>
                        <xsd:enumeration value="312"/>
                        <xsd:enumeration value="313"/>
                        <xsd:enumeration value="315"/>
                        <xsd:enumeration value="317"/>
                        <xsd:enumeration value="319"/>
                        <xsd:enumeration value="322"/>
                        <xsd:enumeration value="323"/>
                        <xsd:enumeration value="324"/>
                        <xsd:enumeration value="325"/>
                        <xsd:enumeration value="326"/>
                        <xsd:enumeration value="350"/>
                        <xsd:enumeration value="352"/>
                        <xsd:enumeration value="353"/>
                        <xsd:enumeration value="354"/>
                        <xsd:enumeration value="355"/>
                        <xsd:enumeration value="356"/>
                        <xsd:enumeration value="357"/>
                        <xsd:enumeration value="358"/>
                        <xsd:enumeration value="361"/>
                        <xsd:enumeration value="362"/>
                        <xsd:enumeration value="404"/>
                        <xsd:enumeration value="410"/>
                        <xsd:enumeration value="412"/>
                        <xsd:enumeration value="414"/>
                        <xsd:enumeration value="417"/>
                        <xsd:enumeration value="418"/>
                        <xsd:enumeration value="419"/>
                        <xsd:enumeration value="420"/>
                        <xsd:enumeration value="421"/>
                        <xsd:enumeration value="422"/>
                        <xsd:enumeration value="423"/>
                        <xsd:enumeration value="424"/>
                        <xsd:enumeration value="425"/>
                        <xsd:enumeration value="426"/>
                        <xsd:enumeration value="429"/>
                        <xsd:enumeration value="431"/>
                        <xsd:enumeration value="432"/>
                        <xsd:enumeration value="433"/>
                        <xsd:enumeration value="434"/>
                        <xsd:enumeration value="435"/>
                        <xsd:enumeration value="436"/>
                        <xsd:enumeration value="437"/>
                        <xsd:enumeration value="440"/>
                        <xsd:enumeration value="451"/>
                        <xsd:enumeration value="452"/>
                        <xsd:enumeration value="453"/>
                        <xsd:enumeration value="455"/>
                        <xsd:enumeration value="456"/>
                        <xsd:enumeration value="460"/>
                        <xsd:enumeration value="463"/>
                        <xsd:enumeration value="466"/>
                        <xsd:enumeration value="468"/>
                        <xsd:enumeration value="470"/>
                        <xsd:enumeration value="475"/>
                        <xsd:enumeration value="485"/>
                        <xsd:enumeration value="486"/>
                        <xsd:enumeration value="490"/>
                        <xsd:enumeration value="492"/>
                        <xsd:enumeration value="494"/>
                        <xsd:enumeration value="500"/>
                        <xsd:enumeration value="501"/>
                        <xsd:enumeration value="503"/>
                        <xsd:enumeration value="504"/>
                        <xsd:enumeration value="511"/>
                        <xsd:enumeration value="517"/>
                        <xsd:enumeration value="521"/>
                        <xsd:enumeration value="527"/>
                        <xsd:enumeration value="536"/>
                        <xsd:enumeration value="540"/>
                        <xsd:enumeration value="561"/>
                        <xsd:enumeration value="567"/>
                        <xsd:enumeration value="568"/>
                        <xsd:enumeration value="601"/>
                        <xsd:enumeration value="602"/>
                        <xsd:enumeration value="620"/>
                        <xsd:enumeration value="625"/>
                        <xsd:enumeration value="650"/>
                        <xsd:enumeration value="715"/>
                        <xsd:enumeration value="753"/>
                        <xsd:enumeration value="754"/>
                        <xsd:enumeration value="805"/>
                        <xsd:enumeration value="806"/>
                        <xsd:enumeration value="810"/>
                        <xsd:enumeration value="811"/>
                        <xsd:enumeration value="812"/>
                        <xsd:enumeration value="813"/>
                        <xsd:enumeration value="814"/>
                        <xsd:enumeration value="815"/>
                        <xsd:enumeration value="816"/>
                        <xsd:enumeration value="818"/>
                        <xsd:enumeration value="819"/>
                        <xsd:enumeration value="820"/>
                        <xsd:enumeration value="821"/>
                        <xsd:enumeration value="822"/>
                        <xsd:enumeration value="823"/>
                        <xsd:enumeration value="824"/>
                        <xsd:enumeration value="826"/>
                        <xsd:enumeration value="827"/>
                        <xsd:enumeration value="828"/>
                        <xsd:enumeration value="829"/>
                        <xsd:enumeration value="830"/>
                        <xsd:enumeration value="831"/>
                        <xsd:enumeration value="832"/>
                        <xsd:enumeration value="833"/>
                        <xsd:enumeration value="834"/>
                        <xsd:enumeration value="835"/>
                        <xsd:enumeration value="836"/>
                        <xsd:enumeration value="837"/>
                        <xsd:enumeration value="838"/>
                        <xsd:enumeration value="839"/>
                        <xsd:enumeration value="840"/>
                        <xsd:enumeration value="841"/>
                        <xsd:enumeration value="842"/>
                        <xsd:enumeration value="843"/>
                        <xsd:enumeration value="844"/>
                        <xsd:enumeration value="845"/>
                        <xsd:enumeration value="846"/>
                        <xsd:enumeration value="847"/>
                        <xsd:enumeration value="848"/>
                        <xsd:enumeration value="849"/>
                        <xsd:enumeration value="850"/>
                        <xsd:enumeration value="851"/>
                        <xsd:enumeration value="852"/>
                        <xsd:enumeration value="853"/>
                        <xsd:enumeration value="854"/>
                        <xsd:enumeration value="855"/>
                        <xsd:enumeration value="856"/>
                        <xsd:enumeration value="857"/>
                        <xsd:enumeration value="858"/>
                        <xsd:enumeration value="859"/>
                        <xsd:enumeration value="860"/>
                        <xsd:enumeration value="861"/>
                        <xsd:enumeration value="862"/>
                        <xsd:enumeration value="863"/>
                        <xsd:enumeration value="864"/>
                        <xsd:enumeration value="865"/>
                        <xsd:enumeration value="866"/>
                        <xsd:enumeration value="867"/>
                        <xsd:enumeration value="868"/>
                        <xsd:enumeration value="869"/>
                        <xsd:enumeration value="870"/>
                        <xsd:enumeration value="871"/>
                        <xsd:enumeration value="872"/>
                        <xsd:enumeration value="873"/>
                        <xsd:enumeration value="874"/>
                        <xsd:enumeration value="875"/>
                        <xsd:enumeration value="876"/>
                        <xsd:enumeration value="877"/>
                        <xsd:enumeration value="878"/>
                        <xsd:enumeration value="879"/>
                        <xsd:enumeration value="880"/>
                        <xsd:enumeration value="881"/>
                        <xsd:enumeration value="882"/>
                        <xsd:enumeration value="883"/>
                        <xsd:enumeration value="884"/>
                        <xsd:enumeration value="885"/>
                        <xsd:enumeration value="886"/>
                        <xsd:enumeration value="887"/>
                        <xsd:enumeration value="888"/>
                        <xsd:enumeration value="889"/>
                        <xsd:enumeration value="891"/>
                        <xsd:enumeration value="893"/>
                        <xsd:enumeration value="894"/>
                        <xsd:enumeration value="895"/>
                        <xsd:enumeration value="896"/>
                        <xsd:enumeration value="920"/>
                        <xsd:enumeration value="924"/>
                        <xsd:enumeration value="925"/>
                        <xsd:enumeration value="926"/>
                        <xsd:enumeration value="928"/>
                        <xsd:enumeration value="940"/>
                        <xsd:enumeration value="943"/>
                        <xsd:enumeration value="944"/>
                        <xsd:enumeration value="945"/>
                        <xsd:enumeration value="947"/>
                        <xsd:enumeration value="980"/>
                        <xsd:enumeration value="990"/>
                        <xsd:enumeration value="993"/>
                        <xsd:enumeration value="996"/>
                        <xsd:enumeration value="997"/>
                        <xsd:enumeration value="998"/>
                        <xsd:enumeration value="999"/>
                        <xsd:attribute name="EDIDataType" fixed="ID" type="xsd:string"/>
                        <xsd:attribute name="ID" fixed="143" type="xsd:string"/>
                        <xsd:attribute name="Name" fixed="Transaction Set Identifier Code" type="xsd:string"/>
                   </xsd:restriction>
              </xsd:simpleContent>
         </xsd:complexType>
         <xsd:complexType name="Element-329">
              <xsd:annotation>
                   <xsd:documentation>Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set </xsd:documentation>
              </xsd:annotation>
              <xsd:simpleContent>
                   <xsd:restriction base="EDI-Element-String-Type">
                        <xsd:minLength value="4"/>
                        <xsd:maxLength value="9"/>
                        <xsd:attribute name="EDIDataType" fixed="AN" type="xsd:string"/>
                        <xsd:attribute name="ID" fixed="329" type="xsd:string"/>
                        <xsd:attribute name="Name" fixed="Transaction Set Control Number" type="xsd:string"/>
                   </xsd:restriction>
              </xsd:simpleContent>
         </xsd:complexType>
         <xsd:complexType name="Element-1705">
              <xsd:annotation>
                   <xsd:documentation>Reference assigned to identify Implementation Convention </xsd:documentation>
              </xsd:annotation>
              <xsd:simpleContent>
                   <xsd:restriction base="EDI-Element-String-Type">
                        <xsd:minLength value="1"/>
                        <xsd:maxLength value="35"/>
                        <xsd:attribute name="EDIDataType" fixed="AN" type="xsd:string"/>
                        <xsd:attribute name="ID" fixed="1705" type="xsd:string"/>
                        <xsd:attribute name="Name" fixed="Implementation Convention Reference" type="xsd:string"/>
                   </xsd:restriction>
              </xsd:simpleContent>
         </xsd:complexType>
         <xsd:complexType name="Segment-G82">
              <xsd:annotation>
                   <xsd:documentation>To transmit identifying numbers, dates, and other basic data relating to the transaction set</xsd:documentation>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="Element-478" type="Element-478"/>
                   <xsd:element name="Element-861" type="Element-861"/>
                   <xsd:element name="Element-860" type="Element-860"/>
    Regards,
    Suneel Jakka

Maybe you are looking for

  • How do i connect my iPod touch to a new Laptop/Pc ?

    When i plug my iPod into my pc and try and get it to connect to iTunes it doesn't connect and does not show 'Cieran's iPod' (Name of iPod) under iTunes Store. ? My laptop that use to connect to my iPod and had all the data on, has now broke and i'm t

  • I cant download itunes 10.7 for windows 7

    i recently upraged my ipod touch to ios 6 now when i try to snyc it to my computer it says i have to download the new itunes 10.7 and every time it alwways has an error 2324 and says ithas to stop installing

  • Problem - Bursting information in Xml file

    Hello All, Can you please guide me How to burst a BIP stand alone version report with all the email(bursting) information coming as XML file source. In other words, I've a report with Data model as file source(xml file) and would like to burst it, bu

  • I'm replacing my motherboard for ane9220yl pavilion elite. I'm looking for a wiring diagram

     I'm replacing my motherboard for HP pavilion Elite e9220yl. I need a wiring diagram to help me make sure I'm rewiring correctly. This question was solved. View Solution.

  • How to use ADF Active Data Service

    Hi All, I have one requirement. I have one BPEL Webservice which is generating some Events, after that the data is going to save in Database. Now i want to display this data on UI whenever there is new event is occurred. So I am going to use ADS. Ple