ILLEGAL PARENT NUMBER

HI, THIS IS PAVAN
I HAVE BEEN TRYING TO IMPORT CHAT OF ACCOUNTS THROUGH DTW TO SAP B1 THE ERROR I AM GETTING IS
"ILLEGAL PARENT NUMBER"
I AM USING,
SAP BUSINESS ONE 2005 B(7.40.232) SP:00 PL:01
                                         PLZ HELP ME OUT WITH THIS.

Pavan,
Please read the Wiki article which explains the whole CoA import using DTW
https://wiki.sdn.sap.com/wiki/display/B1/SAPBusinessOne...ToGo-10.DataTransfer+Workbench
Suda

Similar Messages

  • Illegal Region Number

    After months of trouble free running, I'm getting "Illegal Region Number" error messages popping up with no clue as to which region or any other information. Usually (but not always) it happens when I've hit stop after recording an audio track.
    It doesn't matter which song I'm in, and I've trashed the preferences.
    This error message doesn't affect anything; nothing is lost, and the arrangements in question play just fine, so I just dismiss the error box and continue.
    But I'm curious - any insights?

    There are a few preferences like lowering undo steps, reducing autmation res and data, as well as emptying (Logic's)trash upon save which free up memory. If you open song information you can see what is taking up memory and what may be expendable. Cutting a region creates multiple regions so removing unused can really help to keep memory low. Leaving lots of room on your sytem drive and upping your RAM will also give you less problems. Committing edits (like if there is a passage with 200 regions and they all have fades on them-gluing them together and removing unused should also free alot of the memory. Some peope really like reorganizing memory, I consider kind of risky. Keeping backups of songs instead of high udos and backups for the glued audio files, etc is another good practice for this problem.
    Come to think of it, I have run into this one. Last I had it was while chopping away at bass takes, creating stacks of cuts fades regions, etc. If you let it continue it just starts making things up, region placement, bad fades, anchor voodoo, just little problems like that which don't matter (!?!-JK). Cleaning house, saving all audio files as SDII or AIFF (whichever the existing ones are not), renaming regions were what I had done to overcome the problem long enough to get everything into another session. The memory situation is IMO a huge limitation in Logic, it really restricts what a user can do and requires us to put on the janitor jumpsuit way too frequently : (
    7.1.1 was also a bad move for me, some people get along with it fine but it just caused more problems than any other version of 7 on my system.
    I would guess this is a Logic issue and not an audio file or system issue and these are the things I do to overcome this problem and related ones. In fact, it is very unlikely IIME that it is anything nut a Logic issue. Good luck and if you see this one start moving things to a new session ASAP.
    J

  • DTW - COA error Illegal parent numberApplication-defined or object-defined

    Hi friends,
    I am getting error "Illegal parent numberApplication-defined or object-defined errorchartOfAccounts"
    while executing DTW - COA.
    I am using country India verson and new company is created with user defined COA option.
    I have used 100000000000000 to 500000000000000 as parent code for 2nd level accounts as the same is standard drawers for Country India version Chart of Account at level 1.
    Can anybody throw some light on this ?
    Thanks,
    Samir Gandhi
    Edited by: Samir Gandhi on Oct 15, 2008 11:51 AM

    Suda,
    Below find the sample in code tag.
    Code     AccountType     AcctCurrency     ActiveAccount     AllowChangeVatGroup     BudgetAccount     CashAccount     DataExportCode     DefaultVatGroup     Details     ExternalCode     FatherAccountKey     ForeignName     FormatCode     LiableForAdvances     LockManualTransaction     Name     ProjectCode     Protected     RateConversion     ReconciledAccount     RevaluationCoordinated     TaxExemptAccount     TaxLiableAccount
    Code     AccountType     AcctCurrency     ActiveAccount     AllowChangeVatGroup     BudgetAccount     CashAccount     DataExportCode     DefaultVatGroup     Details     ExternalCode     FatherAccountKey     ForeignName     FormatCode     LiableForAdvances     LockManualTransaction     Name     ProjectCode     Protected     RateConversion     ReconciledAccount     RevaluationCoordinated     TaxExemptAccount     TaxLiableAccount
                   tNO     tNO     tNO                              100000000000000          10000000          tNO     ASSETS          tNO     tNO     tNO     tNO     tNO     tNO
                   tNO     tNO     tNO                              10000000          10100000          tNO     Fixed Assets          tNO     tNO     tNO     tNO     tNO     tNO
                   tNO     tNO     tNO                              10100000          10101000          tNO     Fixed Assets-Tangible          tNO     tNO     tNO     tNO     tNO     tNO
                   tNO     tNO     tNO                              10101000          10101100          tNO     Free Hold Land          tNO     tNO     tNO     tNO     tNO     tNO
         at_Other     INR     tYES     tNO     tNO                              10101100          10101101          tNO     Free Hold Land          tNO     tNO     tNO     tNO     tNO     tNO
                   tNO     tNO     tNO                              10101000          10101200          tNO     Lease Hold Land          tNO     tNO     tNO     tNO     tNO     tNO
         at_Other     INR     tYES     tNO     tNO                              10101200          10101201          tNO     Lease Hold Land          tNO     tNO     tNO     tNO     tNO     tNO
                   tNO     tNO     tNO                              10101000          10101300          tNO     Factory Building          tNO     tNO     tNO     tNO     tNO     tNO
         at_Other     INR     tYES     tNO     tNO                              10101300          10101301          tNO     Factory Building          tNO     tNO     tNO     tNO     tNO     tNO
                   tNO     tNO     tNO                              10101000          10101400          tNO     Non-Factory Building          tNO     tNO     tNO     tNO     tNO     tNO
         at_Other     INR     tYES     tNO     tNO                              10101400          10101401          tNO     Non-Factory Building          tNO     tNO     tNO     tNO     tNO     tNO
                   tNO     tNO     tNO                              10101000          10101500          tNO     Plant & Machinery          tNO     tNO     tNO     tNO     tNO     tNO
         at_Other     INR     tYES     tNO     tNO                              10101500          10101501          tNO     Plant & Machinery          tNO     tNO     tNO     tNO     tNO     tNO
                   tNO     tNO     tNO                              10101000          10101600          tNO     Electric Supply System          tNO     tNO     tNO     tNO     tNO     tNO
         at_Other     INR     tYES     tNO     tNO                              10101600          10101601          tNO     Electric Supply System          tNO     tNO     tNO     tNO     tNO     tNO
                   tNO     tNO     tNO                              10101000          10101700          tNO     Vehicles          tNO     tNO     tNO     tNO     tNO     tNO
         at_Other     INR     tYES     tNO     tNO                              10101700          10101701          tNO     Vehicles          tNO     tNO     tNO     tNO     tNO     tNO
                   tNO     tNO     tNO                              10101000          10101800          tNO     Furniture & Fittings          tNO     tNO     tNO     tNO     tNO     tNO
         at_Other     INR     tYES     tNO     tNO                              10101800          10101801          tNO     Furniture & Fittings          tNO     tNO     tNO     tNO     tNO     tNO
                   tNO     tNO     tNO                              10101000          10101900          tNO     Office Equipments          tNO     tNO     tNO     tNO     tNO     tNO
         at_Other     INR     tYES     tNO     tNO                              10101900          10101901          tNO     Office Equipments          tNO     tNO     tNO     tNO     tNO     tNO
                   tNO     tNO     tNO                              10100000          10102000          tNO     Fixed Assets-InTangible          tNO     tNO     tNO     tNO     tNO     tNO
                   tNO     tNO     tNO                              10102000          10102100          tNO     "Concessions,Patents,Licences,Trademarks,etc."          tNO     tNO     tNO     tNO     tNO     tNO
         at_Other     INR     tYES     tNO     tNO                              10102100          10102101          tNO     Trade Marks          tNO     tNO     tNO     tNO     tNO     tNO
                   tNO     tNO     tNO                              10102000          10102200          tNO     Goodwill          tNO     tNO     tNO     tNO     tNO     tNO
                   tNO     tNO     tNO                              10100000          10200000          tNO     Accumulated Depreciation - Tangible Assets          tNO     tNO     tNO     tNO     tNO     tNO
                   tNO     tNO     tNO                              10200000          10201100          tNO     Free Hold Land          tNO     tNO     tNO     tNO     tNO     tNO
                   tNO     tNO     tNO                              10200000          10201200          tNO     Lease Hold Land          tNO     tNO     tNO     tNO     tNO     tNO
                   tNO     tNO     tNO                              10200000          10201300          tNO     Factory Building          tNO     tNO     tNO     tNO     tNO     tNO
    Thanks,
    Samir Gandhi

  • "Illegals parent number Application-defined or object defined error65171"

    HI Experts,
    I am trying to import a Chart of Account for a new company and I get this error message "Illegals parent number Application-defined or object defined error65171"
    I have seen a couple of post  on this topic but I can't pick out the exact thing I'm doing wrong. Can anybody please put me through?
    If you can give me an email addres I can send the csv for so you can take a look, it format gets disrupted when I paste it here.
    Waiting to Hear from you.
    Regards

    Dear,
    For your issue, If you are using non-segmentation account, please kindly check whether your
    fatherAccountKey is empty or not, this column is mandatory field for non-segmentation account.
    If you are trying to update chart of account with segmentation, please check the note 942939 below:
    Symptom
    When you try to update chart of account with segmentation, using the
    standard template of DTW 2005, you will receive the error message
    "Cannot find this object in B1 Application-defined or object - defined
    error 65171.
    Other terms
    DTW; update; chart of account; SAP Business One;
    Reason and Prerequisites
    Possible reason:
    1, Field     'Code' is blank.
    In DI API Help file 2005 for OChartofAccount, it says that Field "Code"
    is the Mandatory field in SAP Business One when Not Working with
    Segmentation.
    2, Field     'FormatCode'
    The Account Segment Separator '-'.existed in 'FormatCode' field.
    Solution
    1, Field     'Code' is blank.
    For updating existing chart of account with segmentation, This field is
    mandatory. You must fill it with the account code of that account you
    want to update. You can get the code of each account #_SYS00000000XX#
    from OACT table. Otherwise, we cannot update it.
    It is not covered in DI API Help file 2005.
    2, Field     'FormatCode'
    Please delete the Account Segment Separator '-'. For example, change
    11005-000-00-11 to 110050000011. System will identify automatically.
    Please make sure that the field is a Text format cell. You can change
    the format cell by right click the cell.
    Wish the information above could solve your issue.
    Regards
    Apple

  • Generating Parent Number using Level and Display Number

    I am facing problem in generating parent number using level and dispaly number.
    Here is the table structure
    CREATE TABLE test(
    DISPLAY_NUMBER       NUMBER,
    LEVEL_NUM           NUMBER,
    COMPONENT   VARCHAR2(10))
    INSERT INTO test VALUES (1,1,'A');
    INSERT INTO test VALUES (2,2,'B');
    INSERT INTO test VALUES (3,3,'C');
    INSERT INTO test VALUES (4,4,'D');
    INSERT INTO test VALUES (5,3,'E');
    INSERT INTO test VALUES (6,3,'F');
    INSERT INTO test VALUES (7,2,'G');
    INSERT INTO test VALUES (8,3,'H');Here is the output table structure and required output data format
    CREATE TABLE test1(
    DISPLAY_NUMBER       NUMBER,
    LEVEL_NUM           NUMBER,
    COMPONENT   VARCHAR2(10),
    PARENT VARCHAR2(10))
    INSERT INTO test1 VALUES (1,1,'A',NULL);
    INSERT INTO test1 VALUES (2,2,'B','A');
    INSERT INTO test1 VALUES (3,3,'C','B');
    INSERT INTO test1 VALUES (4,4,'D','C');
    INSERT INTO test1 VALUES (5,3,'E','B');
    INSERT INTO test1 VALUES (6,3,'F','B');
    INSERT INTO test1 VALUES (7,2,'G','A');
    INSERT INTO test1 VALUES (8,3,'H','B');Oracle database version : Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
    Thanks in advance.
    Regards,
    Laxman

    >
    I am facing problem in generating parent number using level and dispaly number.
    >
    Thanks for posting the table DDL and data. I called the tables testa and testb.
    insert into testb
    select a.*, (select component from testa b where b.level_num + 1
      = a.level_num and rownum = 1) parent
    from testa a
    select * from testb
    DISPLAY_NUMBER,LEVEL_NUM,COMPONENT,PARENT
    1,1,A,
    2,2,B,A
    3,3,C,B
    4,4,D,C
    5,3,E,B
    6,3,F,B
    7,2,G,A
    8,3,H,B

  • BOM with Same Parent Number But Different WH

    Hello fellow SAP B1ers!
    I have a question and hope someone can help.  This point has us scratching our heads on how to do this.
    A customer has two warehouses (WH 1 and a newly-built WH5) producing the same product (Product A) but at different costs per warehouses.  They want to create two Bill of Materials (BOM) u2013 one for each warehouse.  For Example: BOM of Product A in WH1 and BOM of Product A in WH5.  The item cost is maintained at the warehouse level and, with it being a new warehouse, of course the item costs are different on the Item Master Data (Inventory Tab).  I cannot believe SAP B1 2007 cannot handle this, as this is Production 101 for any company.   Creating fake new and/or phantom products is certainly not the answer, because that could lead to an unbelievable amount of double work.  Besides, they want to be able to see the Product A information together.
    We have researched both SAP Help and Documentation and in both areas, it says (a direct quote) u2013
    If the parent item already has a Bill of Materials, the components are displayed. However, you can still create a new Bill of Materials for that parent item.
    So, how do we create a NEW Bill of Material for that parent item?
    We have tried to enter a new BOM with the parent item and WH5 and same components, but we receive an error that the item is already on the table.  When we use the duplication drop-down function, change the WH number on the header, and change the WH on the lines for components, the original BOM Product A WH1 is gone.  For some reason it also duplicates the components (but that is easily fixed).  I would imagine that a BOM table would need to have part of the key as ItemCode and WhsCode u2013 maybe a mistake in thinking?
    Can someone help us and tell us what we are missing???
    Many thanks for responses - Zal

    Hi Zal,
    Product Code is same as item code as it is unique so it is not possible to have two BOM  for same one item .
    I think help file to pointing towards special production order where you define new BOM for same product
    But I think it is too much work  if you have a lot.....
    So I think you have to look for add on to solve your issue ...
    A thought for  your problem 
    Thank you
    Bishal

  • Has anyone ever got the error message "illegal region number"?

    it happens everytime i stop recording something, and it never did it before today. and do you guys think this firepod is a perfect match with GB?

    I've only seen that error once in 3+ years of using GB, and it was on a crazy project combining 3 separate projects into a 4th.
    I spent 3 days trying to track down the problem and eventually gave up and reverted to a previous version of my project because I could neither track down the cause, nor fix the problem.
    The one thing I can tell you with absolute certainty is that it has nothing to do with your FirePod.

  • Importing Chart of Accounts using DTW

    Dear Sir/Madam,
    I've a problem While importing chart of accounts, I get error like
    "illegal parent number Application -defined or Object-defined Error65171"
    I'm using SAP Business One 2005 B (7.40.252)  SP: 00  PL: 32
    I kindly request you to provide me a solution as early as possible.
    Regards,
    Murali

    Murali,
    I believe you has posted this question earlier too.  Please check my reponse to that.  I have sent the details to your email
    Suda

  • Error In DTW while importing COA

    Hi experts,
      While importing COA through DTW error is displaying as "illegal parent number application defined or object defined error oCOA.
    Rajesh

    Rajesh,
    Please go through this Wiki chapter on CoA import using DTW and you should be able to understand this better
    https://wiki.sdn.sap.com/wiki/display/B1/SAPBusinessOne...ToGo-10.DataTransfer+Workbench
    Suda

  • DTW-Frage OACT Konten-Titel importieren

    Guten Morgen,
    hat jemand Erfahrung beim Import von Konten-Titel per DTW.
    Es soll eine "eigene" Struktur gemäß Wünschen unseres Finanz-Officers in SAP erstellt/importiert werden.
    Ich habe ein Test-Template vorbereitet, welches bei allen Codes "Illegal Parent Number" als Error zeigt.
    Beispiel:
    Ich wollte zu erst die Titel anlegen lassen, danach per Update mit dem "übergeordneten Konto" in die richtige Struktur bringen.
    Was vergessen oder Ist vielleicht gar nicht möglich, Titel per DTW zu importieren ?
    Vielen Dank für Eure Wissenwerte.
    Gruß Markus

    ... es liegt wohl daran, dass sich Konten ohne das Übergeordnete Konto/Titel zu haben, nicht importieren lassen.
    Wir werden vorerst die SAP-Struktur vom SKR03 beibehalten.
    Euch einen schönen Tag

  • COA - DTW Excel Formatting

    Dear Experts,
    I am facing a problem while importing COA.
    If I am not wrong while we import COA, data in csv or as required should be in tree format. Similar to how it looks in COA.
    For my client we are performing a re-implementation, thus we have exported the current COA and client has modified/deleted/added few accounts and given back to us.
    Now the excel sheet needs to be in form of tree structure similar to that what we see in application for DTW else it gives us a error saying that "illegal parent number"
    As experts I need advice from you is there a work around were I could get the data in excel sheet as look alike as COA.?
    Thanks in advance,
    Regards,
    Lal

    Hi
    For the error illegal parent number. one of the Possibility is The Father key u mention might be set as Active account
    Example:
    Code     AccountType     AcctCurrency     ActiveAccount     AllowChangeVatGroup     BudgetAccount     CashAccount     DataExportCode     DefaultVatGroup     Details     ExternalCode     FatherAccountKey     ForeignName     Segment     FormatCode               LiableForAdvances     LockManualTransaction     Name
    Code     AccountType     AcctCurrency     ActiveAccount     AllowChangeVatGroup     BudgetAccount     CashAccount     DataExportCode     DefaultVatGroup     Details     ExternalCode     FatherAccountKey     ForeignName     Segment     FormatCode               LiableForAdvances     LockManualTransaction     Name
    10000011     at_Other     INR     tNO          tYES     tNO                         100000000000000                                   tNO     Fixed Assets
    10000012     at_Other     INR     tNO          tYES     tNO                         10000011                                   tNO     Intangible Assets
    10000013     at_Other     INR     tYES          tYES     tNO                         10000012          100     10000013     200300     10000013100200300          tNO     Licences
    Regards
    Sandeep

  • Worried about parents. Please help!

    my parents phone has had a fault on it since september 16. Bt has logged the fault and there is an announcement that there is a fault when you ring the number. my parents are pensioners and live in a village. i live abroad and rely on the phone to speak to them. i have emailed bt twice to ask when the phone will be fixed but have not had any reply to either emails. when i ring up bt, the automated line hangs up on me! even though i have dialled in my parents number, the automated line says because 'i am' calling from a non bt line ( yes i live abroad) that i would need to contact MY telephone service provider. which is ridiculous as this issue has nothing to do with them. i just want to know my oarents are ok. could someone at bt contact me (as i have requested twice now) to tell me when my oarents phone will be fixed, and also sort out the ridiculous cut off on the telephone. why have a number specifically for people calling from abroad, if you then cut them off saying if they are not calling from a bt line, you wont deal with them. Please help.

    I have asked a moderator to provide assistance, they will post an invite on this thread.
    They are the only BT employees on this forum.
    Once you get a reply, if you click on their name, you will see a screen like this. Click on the link as shown below.
    Please do not send them a personal message, as they may not be on duty for a long time, and your message will not be tracked properly.
    For your own security, do not post any personal details, on this forum. That includes any tracking number you are give.
    They will respond either by phone or e-mail within 5-6 working days.
    Please use the tracked e-mail, to reply, not via the forum. Thanks
    There are some useful help pages here, for BT Broadband customers only, on my personal website.
    BT Broadband customers - help with broadband, WiFi, networking, e-mail and phones.

  • Logic 10.0.5 is out! Three new drummers, LOADS of fixes.

    I have not yet finished reading the release notes, it is almost 5,000 words...
    http://support.apple.com/kb/TS4498
    Logic Pro X 10.0.5: Release notes
    Symptoms
    Logic Pro X 10.0.5 is an update to Logic Pro X. Logic Pro X is a new paid version of Logic Pro.
    Resolution
    Logic Pro X 10.0.5 update
    New features and enhancements
    Includes 3 new Drummers and 11 new Drum Kit Designer patches.
    Significant enhancements to Channel EQ and Linear Phase EQ plug-ins, including:
    Redesigned, easier-to-use interface that's also accessible within the Smart Controls area
    Double Precision processing provides more accurate filtering, especially for low frequencies
    Oversampling option improves high-frequency clarity
    Option to apply EQ only to stereo left, right, middle, or side signals
    There is now an option to set the Piano Roll to a light background color.
    Selected notes in the Piano Roll are now highlighted by a selection frame.
    When Logic is stopped or in Play mode, the glyph on the Metronome button in the control bar now illuminates to indicate that “Click while recording” is enabled.
    The Shuffle commands are improved (see Logic Pro X Help for details).
    User interface
    There is now a command to assign region names to track names.
    The waveform size in an audio region now adapts to the value of the region gain parameter.
    Loops that belong to the same family can now be selected and changed using a new control in the region header.
    Logic Pro X now assigns region and Mixer channel colors that are closer to the original colors when opening a project created in an earlier version of Logic.
    Option-clicking a disclosure triangle in the Project Audio window now toggles all disclosure triangles in the window.
    The Windows menu again lists all currently open windows.
    The Mixer can now be reliably resized when in All mode.
    Renaming multiple selected Mixer channels now reliably renames all channel strips in the selection.
    When creating a duplicate track, the correct track icon and color are now assigned to the duplicate.
    The song title is now automatically populated in the Share to iTunes dialog when sharing a song created in Logic 9 or GarageBand for iOS.
    It's once again possible to browse or load patches onto the Output channel strip via the Library.
    The View menu items One Track and Selected Regions in the Piano Roll are now disabled when Link mode is disabled.
    Performance
    Improves processor balancing for multi-output software instrument configurations.
    Improves handling of multiple displays on OS X Mavericks v10.9.
    Resolves an issue that in some cases might cause audio clicks and pops when scrolling.
    Moving an automation line while playing no longer spikes in CPU usages, or clicks and pops in the audio output.
    Resolves an issue that could cause clicks and pops in the audio output when adjusting the gain or output level settings during playback in the various plug-ins.
    Logic's interface no longer freezes when using the Native Instruments Maschine controller to adjust two macro controls simultaneously.
    Fixes an issue in which a warning about not enough memory might be displayed when performing Undo after editing a protected track.
    Adjusting the frequency controls while playing audio through the Stereo Spread plug-in no longer causes audible zipper noise.
    Improves the performance of scrolling when dragging regions in the Tracks area beyond the currently visible section.
    Playing notes live into the Arpeggiator plug-in no longer sometimes leads to spikes in CPU usage.
    Fixes an issue that could cause a spike in CPU usage when recording near the end of a project.
    Logic 9 projects that contain a macro object in the Environment now behave more reliably when opened into Logic Pro X.
    Multiple instances of the Scripter plug-in no longer have the potential to cause stuck notes.
    The Scripter plug-in is no longer prone to causing stuck notes when using the Delay Note Until Next Beat preset.
    Switching between presets in the Space Designer plug-in no longer sometimes results in noise.
    General
    Regions copied from a Track Stack can now be muted as expected even when they are within a Track Stack that is muted.
    Deleting an audio Track Stack while it was soloed no longer leaves all the remaining tracks muted.
    Entering a new crossfade value in the Region inspector for multiple selected regions now works as expected.
    Region-based automation data beyond the end of a region is now chased properly even when playback is started after the last automation node within the bounds of the region.
    Logic now maintains the correct relative levels when automation on multiple tracks belonging to the same Group are copied by dragging.
    Resolves an issue in which track automation might be deleted when switching patches.
    The default display setting when showing automation on Track Stacks is now Volume, instead of Display Off.
    A track is now created as expected when using a control surface to set the automation mode of a channel strip not previously assigned to a track.
    Moving a SMPTE locked region can no longer  cause the automation on the track to  move.
    The position of the automation line no longer jumps unexpectedly when it is selected after creating 4 automation points with a Marquee selection.
    Adjacent automation points of the same value are no longer sometimes inadvertently deleted when moving automation points on a grouped track.
    The Repeat Section Between Locators command now includes automation on tracks that contain no regions in the repeated section.
    When using Touch mode, Logic no longer writes unneeded automation points at the held value when holding a fader at the same position where there is an existing automation ramp.
    Writing automation to an Aux not assigned to a track can no longer potentially cause tracks in a Track Stack to be rerouted to that Aux.
    Copying multiple regions where only some affected tracks contain automation no longer activates Automation Read mode on the channel strips that have no automation.
    Chase now works as expected for MIDI controllers on channels other than channel 1.
    Takes are now shortened as expected when the take folder containing them is shortened by an edit operation and No Overlap mode is enabled.
    Fixes an issue in which the visible area might jump unexpectedly when comping in a take folder that was not on the selected track.
    Fixes an issue that caused some audio regions to be immovable when duplicate regions are packed into a take folder.
    Packing regions with names containing non-ASCII characters into a take folder no longer creates garbled take names.
    Numbers assigned to MIDI takes now increment reliably.
    Expanding a take folder no longer potentially causes the playhead to fall out of sync with the audio output.
    When using OS X v10.9, the playhead in the Audio Editor now consistently maintains the correct position when switching from Flex Time to Flex Pitch mode.
    It's now possible to set a loop to a length of less than 1/16 note.
    The position of beat markers in the Global Beat Mapping track are now updated appropriately when using the various Cut/Insert Time commands.
    Inserting a beat marker in the Beat Mapping track no longer creates unexpected tempo events in some circumstances.
    Expanding a take folder no longer potentially causes the playhead to fall out of sync with the audio output.
    Resolves an issue in which some MIDI notes might unexpectedly change position when Beat Mapping.
    Adding a Beat Mapping marker no longer intermittently removes existing tempo events.
    Inserting a fade-in using Shift-Control and the Pointer tool now works consistently.
    Using the Fade tool to set fade-ins on multiple regions in a set of grouped tracks now works reliably.
    Dragging regions on multiple grouped tracks with the Drag Mode set to X-Fade  no longer potentially results in crossfades of varying lengths.
    The Delete command now works as expected on selected regions that are inside a collapsed Group in the Project Audio window.
    It's now possible to add a green Apple MIDI loop to the Tracks area as an audio loop by dragging it from the Loops browser while pressing the Option key.
    Logic Pro X no longer creates separate tracks for non-overlapping regions when unpacking folders in projects created by earlier versions of Logic.
    Using the  menu that appears when pressing the Metronome button in the Control Bar, it's now possible to set the metronome to sound only during count-in.
    Improves the reliability of Undo in several areas.
    The Mixer window  no longer intermittently moves when scrolling past the minimum or maximum value of the fader using a scroll wheel or gesture.
    It's now possible to select or open folder tracks in the Mixer.
    Right-clicking  an Aux or Output channel strip in the Mixer and selecting Create Track now behaves as expected even if the channel strip is not initially selected.
    Command-click again works reliably to  deselect a Mixer channel within a selected group of channels.
    The display of audio waveforms of regions in a track  no longer change unexpectedly when enabling or disabling the Groove status on a track.
    Looped regions inside a folder now update the point they are supposed to stop playing after extending the length of the folder.
    Overwriting an existing project  no longer potentially leaves assets from the original project in place.
    When creating a new project from a Logic 9 template, the default save path is no longer the location of the template.
    Improves the mapping of Smart Controls to channel strip settings created in Logic 9.
    The Follow Tempo parameter in the Region inspector is no longer incorrectly disabled for Apple Loops in songs last saved in GarageBand 6 or earlier.
    Clicking and holding down on the upper-right corner of a region no longer unexpectedly enables looping in the Region inspector, with a loop length of zero.
    The Region Inspector no longer displays a Loop checkbox for selected Track Stack folder regions.
    It's once again possible to disable Quantize in the Region Inspector for a region on a track slaved to a Groove Master track.
    Saving a song created from a template  no longer resets the tempo to 120 BPM.
    Text for alert messages now always displays correctly on control surfaces.
    Changing Region inspector parameters for MIDI regions on the main track of a Track Stack now behaves as expected.
    It's again possible to change the Transpose value in the Region Inspector using the + and - keys.
    Logic now consistently responds to Play or Stop key commands when a floating Region inspector window is open.
    It's no longer possible to give the same name to more than one project alternative.
    MIDI played from the Musical Typing Keyboard and Logic Remote is now routed through the Physical Input object in the Environment, which allows  Environment processing of MIDI as it is being played into Logic from these sources.
    Logic no longer adds 2 extra frames to the value when entering a SMPTE position in a project set to a non-drop frame rate.
    Regions copied by option-dragging in projects with a start position earlier than bar 1 now end  at the desired position.
    Moving the first arrangement marker in a project  no longer inadvertently moves other arrangement markers.
    Resolves a rare issue that could cause the timing of a track in a project with many tempo changes to be altered after turning Flex on and then off.
    Logic now asks the user to save the project when closing a project immediately after entering text into the Project Notes area.
    It's now possible to consistently add, remove, or edit plug-ins on tracks that were frozen in Source Only mode.
    Pressing the Control key while dragging a region with the Snap Mode set to Bar now moves the region by beats instead of ticks, as expected.
    Editing the left border of an audio region now behaves as expected when the Snap setting is set to “Snap Regions to Relative Value”.
    Resizing a region with the Snap setting set to “Snap Regions to Absolute Value” now behaves as expected.
    Resolves an issue that caused an event in the Event List to move later than expected when editing its position.
    The “Capture as Recording” command now works as expected when multiple MIDI tracks are record-enabled.
    It's now possible to preview sections of an audio file outside the current region borders by clicking the area in the Project Audio window.
    The tap-to-click option for trackpads now works reliably with all drop down menus.
    The “Discard Recording and Return to Last Play Position” key command now reliably discards the recording.
    It's again possible to use the Tab key to navigate to the next control while working with plug-ins in Controls view.
    The MIDI Activity display now shows chords as they are played when using Musical Typing.
    All currently found audio files are now reliably saved with a project when using Save As or Save a Copy As with a project in which one or more audio files are missing.
    The name of a project is now correctly updated after saving a  project created from a template.
    Fixes an issue in which clicking on the level LED in the track header did not select the track.
    Resolves an issue in which changes made to the setup for Mackie Control and other MCU-compatible control surfaces were not saved by Logic Pro X.
    Setting the Display Time preference to “SMPTE/EBU with Subframes”, “SMPTE/EBU without Subframes,” or “SMPTE/EBU with Quarter frames” can no longer  cause the time display to jump unexpectedly.
    Saving a project for the first time no longer resets the record path when it was previously set to an external path.
    Performing undo in the Piano Roll or after deleting a flex marker no longer has the potential to unfreeze currently frozen tracks in the project.
    Sample rate, tempo, and key information is now reliably stored within template files.
    Fixes an issue in which the Repeat Regions dialog did not have key focus when opened, making it necessary to click it with the mouse before pressing Return to confirm the operation.
    Individual MIDI Draw points in the Piano Roll are now  easier to grab.
    Deleting a track no longer has the potential to inadvertently delete regions on other tracks.
    Cut/Insert Time edits no longer add unexpected tempo changes.
    Scrubbing the SMPTE display in the LCD no longer moves the playhead to the wrong position.
    Copying an arrangement marker to a position between two other arrangement markers  now moves the end-of-song marker to accommodate the new section, as expected.
    Audio
    Audio regions now appear as expected in the Audio Editor, even when cycle is enabled and there are no audio regions within the cycle area.
    Flex Pitch now correctly detects notes for take regions that have manually inserted flex markers.
    The timing of notes played during the count-in on EXS24 or Drummer tracks is now more reliable.
    Pasting an audio region into a take folder now correctly places the region on the selected take lane.
    When saving an EXS instrument, the default save location is now ~/Music/Audio Music Apps/Sampler Instruments.
    Editing the start point and anchor in the EXS audio editor now consistently alters playback as expected.
    Logic no longer overwrites an existing audio file of the same name when performing a bounce with the option to create a split stereo file enabled.
    Audio tracks assigned to output to a bus now consistently maintain that assignment when imported into a different song.
    User-defined controller assignments now work as expected to control MIDI plug-in parameters.
    The Record Repeat command now deletes the previous recording when used after recording in Cycle mode.
    Quantize now operates reliably on takes that are displayed in the Audio Editor.
    The Tuner window is no longer affected by the Content Link setting of other plug-in windows.
    Audio now plays for multiple cycle iterations when using marquee selection to define the cycle area.
    When the Edit command “Analyze Audio for Flex Editing” is used, Logic now properly resets any existing pitch edits on the selected audio files.
    Command-clicking a selected note in Flex Pitch mode in the Audio Editor now deselects the note, as expected.
    Setting a track to Flex Edit mode with the Slicing algorithm no longer processes the track with Flex if no edits have been applied.
    It's again possible to set Software Instruments to mono.
    Logic no longer creates an extra audio file when merging or format-converting audio files.
    Resolves an issue in which the Mixer did not show the 8th bus send on a channel strip.
    Changing the input format of a stereo output channel strip to mono now creates a second mono output channel strip on the Mixer for the other channel in the stereo pair.
    Setting an external recording path now reliably resets the Audio Assets setting. Conversely, enabling the Audio Assets setting now disables an externally set recording path.
    The compressor meter in the channel strip is now in sync with the meter in the plug-in window.
    Drummer
    Improves the translation of articulations when an Ultrabeat-based patch is assigned to a Drummer track.
    When a project starts on an upbeat, a Drummer region at the project start now automatically creates a fill at the beginning.
    Changes to Drummer regions are now reliably applied when the regions are set to follow a flexed audio track.
    MIDI editors
    The Link mode button is now available for the Piano Roll editor.
    The “Limit Dragging to One Direction” setting now works  as expected in the Piano Roll.
    It's now possible to grab notes shorter than 15 ticks for editing in the Piano Roll.
    Double-clicking a region with MIDI Draw enabled now consistently opens or closes a MIDI editor.
    Resolves an issue in which recently recorded MIDI notes might disappear from view in the Piano Roll when recording with cycle engaged.
    It's again possible to alter the pitch of notes in the Piano Roll via MIDI input.
    Using  Option-Shift  to edit the end points of multiple selected notes to the same position in the Piano Roll Editor now works as expected.
    In the Piano Roll, it's again possible to use Option-Shift in conjunction with the Velocity tool to set all selected notes to the same velocity.
    An Event Float window that is linked no longer switches unexpectedly to the Region level when using arrow keys to move from note to note in the Piano Roll.
    Pasting events in the Piano Roll when the playhead is to the right of the region border will not trigger the error “Illegal Region number”.
    It's now possible to copy a note in the Piano Roll to a different pitch at the same position when the note starts before the left edge of the region.
    It’s now possible to move notes in the Piano Roll by increments smaller than 13 ticks when the “Limit Dragging to One Direction” setting is enabled.
    User-inserted rests no longer incorrectly appear as notes in the Piano Roll.
    Copying a muted note in the Piano Roll now creates a muted copy of the note, as expected.
    Fixes an issue in which some note events might not be selectable in the Step Editor.
    The contents of the Event List are now updated properly when deselecting a region from a multiple selection while Content Link mode is enabled.
    The Event List now displays the correct LSB values for 14-bit pitch bend events.
    Editing Release Velocity values in the Event List now behaves as expected.
    The “Copy selected events” option in the MIDI Transform window now behaves as expected.
    Score Editor
    Fixes an issue that could cause the menu option for switching between Parts and Score view in the Score Sets window to disappear.
    Double-clicking  a region with the All Instruments filter setting active now reliably reveals all regions on that track, rather than just the single region.
    The contents of the Event List editor are more consistently updated when changing the region selection from the Score window.
    Newly inserted key signatures no longer display “xx Major” in some circumstances.
    The Chord Grid Editor now correctly names Add 9 chords.
    The clef menu no longer disappears for a Mapped Instrument staff style set to “No Clef”.
    It's again possible to create a new Chord Grid library that uses an alternate tuning.
    It's  now possible to adjust the Velocity setting in the MIDI Meanings settings window by scrubbing the value with the mouse.
    The length adjustment in the MIDI Meanings settings window can now be adjusted via a pop-up menu.
    In the Staff Style window, the check marks indicating that a style is used in the current song now reliably update to reflect changes when Content Link mode is off.
    Grace notes now scale properly when the scale setting of a Score Set is  less than 100.
    Resolves an issue that prevented reassigning instruments assigned to a Score Set after performing certain other edits.
    Fixes an issue that prevented naming a floating score Part box set.
    Plug-ins
    Solo now works as expected on channel strips using an external I/O plug-in
    Ultrabeat can now find samples that have been relocated from the default install location.
    Ultrabeat now correctly applies the Fine Pitch adjustment to all triggered samples when trigger mode is set to Multi.
    It's now  possible to halve/double the current rate of the Arpeggiator plug-in by clicking the Slow/Fast buttons.
    The ES1 synth plug-in  can now be set to offer 32 and 64 voices per instance.
    The Scripter plug-in now allows System Realtime MIDI events to pass through.
    The Scripter plug-in now offers an option to keep current control values when recompiling a script, rather than resetting all values back to their defaults.
    The Scripter MIDI plug-in now includes a Set Parameter function.
    Switching between Vintage Electric Piano patches while holding notes no longer potentially results in momentary jumps in level.
    The Vintage Electric Piano no longer potentially creates audible pops when switching patches when the Drive is enabled and set to Type II.
    It's now possible to continue working with the Scripter editor window when Logic Pro X is not in focus.
    The Surround Compressor plug-in now properly shows all the new circuit types available in Logic Pro X.
    It's again possible to copy or paste settings in the Space Designer plug-in window.
    The order of controls in the Retrosynth Filter Envelope and Amp Envelope sections has been reorganized to improve usability.
    The plug-in window no longer appears empty for Waves plug-ins opened in projects created in Logic 9.
    Fixes an issue in which inserting a plug-in on multiple stereo Software Instrument channel strips would insert mono versions of the plug-in on some channel strips.
    EXS24 or Kontakt settings are no longer  removed from a song if the Audio Device buffer size is changed before saving the song.
    Resolves an issue in which adjusting parameters on the Channel EQ while playing back might cause minor clicks and pops in the audio signal.
    Moving an Amp Designer instance to a different plug-in slot no longer sometimes changes its sound.
    “Save as Default” for Audio Unit presets again works as expected.
    Video
    It's now possible to exchange movie files in a project by dragging a new movie file into the Movie window or the Movie inspector.
    Logic Pro X can now work with the following professional video codecs, if OS X Mavericks v10.9 and the codecs are installed: Apple Intermediate Codec, Apple ProRes, AVC-Intra, DVCPRO HD, HDV, XDCAM HD / EX / HD422, MPEG IMX, Uncompressed 4:2:2, XAVC.
    There is now a Show/Hide Movie Window command in the View menu when the current project contains a movie.
    Resolves an issue in which some movies that were compatible with QuickTime X did not play in Logic Pro X.
    Exporting audio to a movie with a portrait orientation no longer causes the movie to rotate 90 degrees.
    Logic is now  able to export surround AAC audio to a movie even if the original audio in the movie was originally kept.
    The visible frame of a movie now updates as note lengths in the Piano Roll are changed.
    Import/export fixes and improvements
    XML projects imported from Final Cut Pro X now contain volume and pan automation when opened in Logic Pro X.
    Exporting a project as an Final Cut Pro/XML file with the “Export as Final Cut Compound Clip” option enabled now behaves as expected.
    Includes several improvements to the way Logic handles audio sample-rate conversion when importing Final Cut Pro XML.
    Logic now shows a progress bar when importing large Final Cut Pro XML projects.
    32-bit float audio files in Final Cut Pro XML projects are now converted to 24-bit files during import so they play properly when imported into Logic.
    The start time of imported Final Cut Pro XML projects is now consistently correct.
    It's now possible to export Music XML when the Score window is in linear view mode.
    Logic no longer shows multiple alerts when importing a Final Cut Pro XML project containing videos in a format not supported by Logic.
    Songs created in GarageBand 6 no longer load in Logic Pro X with an extra channel in the Mixer.
    Fixes an issue in which audio in a song imported from GarageBand 6 might play back too fast in Logic Pro X.
    Logic now offers to include embedded tempo and marker information when using Track Import to bring an audio file into a project that contains no other audio regions.
    Simultaneously dragging multiple MIDI files into the Tracks area now behaves as expected when using No Overlap mode.
    The default destination path for exported MIDI files is now the project folder instead of ~/Music/Logic.
    When importing projects, there is now an Add All button in the Aux import dialog.
    The user settings in the Bounce window are now retained after sharing to iTunes.
    Split stereo SD2 files no longer incorrectly import as AIFF files when the WAV file option is enabled.
    The “Share Song to iTunes” command now creates a playlist with the name entered if there is not already an iTunes playlist with that name.
    MIDI events that precede the start point of a region are no longer included when the region is exported as a MIDI file.
    Stability and reliability
    Includes several fixes related to stability and reliability, including to resolve issues that could cause Logic to quit unexpectedly in these circumstances:
    When changing the length of a time-stretched region
    When importing tracks from another project
    When recording with the color palette open
    When bypassing an instance of the Maschine plug-in
    When exporting Music XML after applying Enharmonic Shift to some notes
    When changing the range on an Environment fader whose style was set to Text
    When quitting a project that has a Surround Compressor inserted on a channel strip
    When removing a control surface from the Control Surface setup window when the Logic Remote is also present
    When changing the range value of a Smart Control during playback.
    When reapplying a Time and Pitch operation after undoing a previous one
    When dragging an audio region from a take folder to a new song

    Thanks Erik,
    If nothing else, this huge list of updates and fixes, shows clearly that the Logic Dev team is working hard on fixing and improving LPX to a major degree.... and from the list of fixes done.. show they do read the bug reports submitted!
    As an aside....
    I recall how all the 'naysayers' prior to LPX (and in some cases, since...)  were proclaiming how Logic was dead, the team was being disbanded, we won't see any further development, the Dev team doesn't listen or care... and so on....... I wonder where those people are now?

  • Multiple values from a single function to be used SQL

    I have some pl/sql code that calculates multiple values in the same procedure (multiple out parameters).
    Now I want to use these separate values in an SQL select.
    One way to do it, is creating functions for each separate value.
    Performance wise, I don't want to do so.
    I created an object type with 9 number values.
    A function returns the object type and I select it in a subquery.
    The outer query then selects 3 different values from the object in the subquery.
    Unfortunately, a query with 3 rows still results in the function being called 9 times (3 row x 3 values).
    Is there a way to force the object function being called just once per row ?
    Or is there an alternative way?
    I've tried pipelined functions but then I have trouble with the input values for the function that should be taken from another select.
    result will be a view with a key value and the calculated values
    SELECT key_value, calculated_value1, calculated_value2, calculated_value3
    FROM SOME_TABLE

    DROP TABLE TBL
    CREATE TABLE TBL(
    ID NUMBER(10),
    CODE VARCHAR2(20),
    PARENT NUMBER(10)
    INSERT INTO TBL VALUES(1,'A',1);
    INSERT INTO TBL VALUES(2,'B',1);
    INSERT INTO TBL VALUES(3,'C',1);
    INSERT INTO TBL VALUES(4,'D',2);
    INSERT INTO TBL VALUES(5,'E',2);
    INSERT INTO TBL VALUES(6,'F',2);
    CREATE OR REPLACE PACKAGE pck_test IS
    TYPE t_rec IS RECORD(
    value1 NUMBER,
    value2 NUMBER,
    value3 NUMBER);
    TYPE t_tab IS TABLE OF pck_test.t_rec;
    FUNCTION calculate(i_id NUMBER) RETURN pck_test.t_tab
    PIPELINED;
    END pck_test;
    CREATE OR REPLACE PACKAGE BODY pck_test IS
    FUNCTION calculate(i_id NUMBER) RETURN pck_test.t_tab
    PIPELINED IS
    v_return t_rec;
    BEGIN
    v_return.value1 := 1 * i_id;
    v_return.value2 := 2 * i_id;
    v_return.value3 := 3 * i_id;
    PIPE ROW(v_return);
    RETURN;
    END;
    END pck_test;
    now I can use the pipelined function:
    SELECT 1 id, x.value1, x.value2, x.value3
    FROM TABLE(pck_test.calculate(1)) x
    id is hard-coded in this select with value 1
    I want to use TBL.id as the argument for the calculate function.
    I don't know how. I tried this...
    SELECT parent, ID, multi_values.value1, multi_values.value2, multi_values.value3
    FROM (
    SELECT ID, TABLE(pck_test.calculate(ID)) multi_values
    FROM TBL)
    Then the SELECT will be stored as a view.
    In an application, the view will be queried:
    select value1, value2, value3
    from view
    where parent = :parameter

  • How can I retrieve data from one table to another automatic in SQL?

    Hi, everione,
    I am having a big problem, trying to create datebase.
    I have 3 tables: SUPERAVATAR, MASTERAVATAR, MEGAAVATAR.
    - SuperAvatars are heroes in an online role playing gaming. They have an ID, ‘superavatarID’ which contain an UNIQUE NUMBER NOT NULL PRIMARY KEY to identify them.
    A wisdom – ‘trickster’,’conjuror’,’magician’, etc..
    A current owner… who is the user or player of the game and has that Super Avatar– we associate the link to USERID to know the person.
    SuperAvatars can be fathers or mothers of Mega Avatars.
    -MegaAvatars are the children of SuperAvatars…. They also have an ID UNIQUE NUMBER NOT NULL PRIMARY KEY to indentify them.
    A magic power – it can be a ‘Leader’ or ‘Sheep’…
    A ‘parent’ – parent is the number identifying to know to who Super Avatar belongs.
    e.g.
    SUPERAVAT WISD CURRENTOWNER FATHEROF MOTHEROF
    1 Thick 3 1
    2 Mentally Ch. 11 3
    3 Smart 9 2
    4 Genius 16 4
    5 Thick 19
    MEGAAVATARID MAGICPOWER PARENT
    1 MAGICIAN 1
    2 WIZARD 3
    3 SORCERER 2
    4 MAGICIAN 4
    -We see that MEGAAVATAR 1 has a magic power as Magician and his father is ‘1’. ‘1’ identifies the SUPERAVATAR.
    We see SUPERAVATARID…. who has the number ‘1’? the first in the row… who has wisdom – thick and he belongs to the USER with ID number 3.
    -We see MEGAAVATARID… we choose the number 2…. His magic power is as WIZARD… and his father is the number 3.
    We see SUPERAVATARID now… we look up the SuperavatarID 3…. We can see he has a wisdom – GENIUS… who belongs to the USERID 16 and he is father of MEGAAVATAR number 2.
    The list can carry on and never stop.
    I have this Problems:
    We create in this example 3 tables: Users, SuperAvatar, MegaAvatar
    SQL
    CREATE TABLE users(userID NUMBER CONSTRAINT pk_user PRIMARY KEY,email VARCHAR2(50) NOT NULL UNIQUE,password VARCHAR2(15) NOT NULL UNIQUE,subscription CHAR(8) NOT NULL CHECK (subscription IN('ACTIVE' , 'INACTIVE' ) ) );
    CREATE TABLE superavatar(superavatarID NUMBER CONSTRAINT pk_superavatar PRIMARY KEY, wisdom VARCHAR2(19) NOT NULL CHECK (wisdom IN ('THICK', 'MENTALLY CHALLENGED', 'AWAKE', 'SMART', 'GENIUS')), currentOwner NUMBER NOT NULL, fatherOf NUMBER,motherOf NUMBER);
    CREATE TABLE megaavatar (megaavatarID NUMBER CONSTRAINT pk_megaavatar PRIMARY KEY, magicPower VARCHAR2(12) NOT NULL CHECK (magicPower IN('TRICKSTER','CONJUROR','MAGICIAN','WIZARD','SORCERER')), parent NUMBER);
    Now, the 3 tables are created…..
    What happen when we try to insert values to this table?
    In this case we insert to User Table some examples:
    INSERT INTO users VALUES('3','[email protected]','great78','ACTIVE');
    INSERT INTO users VALUES('9','[email protected]','chrisandra)','ACTIVE');
    Now, we insert to SuperAvatar some examples;
    INSERT INTO superavatar VALUES('1','THICK','3','1','');
    INSERT INTO superavatar VALUES('3','SMART','9','3','');
    |
    |
    ‘9’ is the UserID that we already insert to the User table
    What’s the problem?
    We have to insert manually the data from USERID to CURRENTOWNER as we didn’t match or link CURRENTOWNER from SUPERAVATAR Table to USERID from USER Table with a SQL CODE.
    What happen if we have thousands of USERS that they register to this game…? We will never know to how belongs that SUPERAVATAR but if someone do it manually can spend a year.
    I am trying to fix this problem …. I add in SUPERAVATAR TABLE ‘CHECK’ in currentOwner..
    SQL> CREATE TABLE superavatar
    (superavatarID NUMBER CONSTRAINT pk_superavatar PRIMARY KEY, wisdom VARCHAR2(19) NOT NULL CHECK (wisdom IN ('THICK', 'MENTALLY CHALLENGED', 'AWAKE', 'SMART', 'GENIUS')),
    currentOwner NUMBER NOT NULL CHECK (currentOwner IN(SELECT userID FROM users)),
    fatherOf NUMBER,
    motherOf NUMBER);
    ERROR:
    ORA-02251: subquery not allowed here
    It doesn’t work.
    Please HELP, I have exam tomorrow
    thank you
    Desy

    Hallo,
    you can use trigger on table USER and fill the userid in AVATAR.currentowner,
    but i don't understand, how you join these tables ?
    Which user id must come in which column currentowner ?
    Design problem ?
    Regards
    Dmytro

Maybe you are looking for