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

Similar Messages

  • 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.

  • Illegal Regions

    I just started a new tune.
    I put in a drum loop then recorded a guitar track.
    I got "Illegal Regions" message. I clicked OK. It laid down the track OK, apparently.
    I recorded another guitar track and got the "illegal region" message again.
    Anybody know what this is about? I just upgraded to 7.2.0.
    Thanks.

    The "Illegal Regions" message is related to your
    computer's memory.
    Are you running any other programs whilst working in
    Logic? If so, quit them, including turning Airport
    off.
    No airport. I’m usually running Safari, itunes and Mail, oh and the rme fireface Mixer and Settings programs run all the time automatically. But, none of this is any different from my normal work habits before I installed 7.2.
    You can also try to free up your memory by opening
    File > Project > Clean up..., and remove whatever
    files you don't need.
    It says “nothing to remove.”
    Further:
    Go to Preferences > Editing, and lower your "Limit
    Multiple Undo Steps".
    I did this.
    Go to Preferences > Audio > Drivers, and uncheck 64
    Busses.
    This was already unchecked.
    Go to Preferences > Audio > Sample Editor, and reduce
    the number of undo steps.
    Changed from 5 to 3.
    Did you edit your regions after recording? If so,
    remove the ones your are not using any longer.
    No.
    How much free space do you have on your system drive?
    It should be at least 20%, f.e. if you have an 80 GB
    HD, leave at least 16 GB free.
    It’s about 30%
    Your RAM seems to be maxed out for your computer, so
    we can not improve there. But with 2GB you should not
    encounter the problems you have because of a RAM
    issue anyway.
    Your profile states that you are still on Panther.
    You said you recently upgraded to LP 7.2.0. Did you
    also upgrade to Tiger (highly recommended!!!)?
    I am on 10.4.6
    If that is the case, you need to re-install Pro >Application Support:
    I didn’t do this yet but will.
    Good luck and let us know
    I did all of the above minus the proapp install.
    Apparently, the problem is solved.
    Thank you, sonther, for your help
    G5 Dual 2.0 Mac OS X (10.4.6) 2 GB RAM * Logic Pro 7.20

  • 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

  • Illegal region message, Logic Pro X

    Hi all,
    I have a brand new macbook Pro 15 (late 2014) with 16GB memory. I was receiving this message last night when importing and slicing audio. There was very little happening in the project so its hardly down to memory running out!
    Logic Pro X
    Macbook Pro
    Intel Core i7 4770
    I had several instances of battery 4 open with fully loaded palettes.

    Nobody seems to know what it means, but I found some tips on how to get rid of it.
    https://discussions.apple.com/message/1415891?messageID=1415891&amp%3b#1415891

  • 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?

  • How to create tabs in a region

    Can you tell me if it is possible to create a multi tab region. I wish to use the functionality available for tabs at page level but on a region within a page.

    Hi,
    That is actually something that I had to do not very long ago - the form page got so long that users wanted it divided into logical groupings of page items and then have a row of tabs along the top that allowed them to display these grouped items one group at a time.
    What you need is a hidden page item called, as P1_REGION. Then, on your page, create a computation for this item that runs Before Header and sets this to a Static Assignment value of 1 - this computation should be conditional on P1_REGION being null (this just sets it to a default value of 1 when the page is first loaded).
    Then, for each region on your page, you determine a region number that it will use. Make each region conditional on P1_REGION being this number - use the "Value of Item in Expression 1 equals Expression 2" condition - put P1_REGION in Expression 1 and your selected region number in Expression 2.
    Now, on your list's defintion, you set "Set these Items" to P1_REGION and "With these values" to the appropriate region number for each list item.
    Finally, to highlight which region is currently selected, on the list item, in the Current List Entry section, set "List Entry Current for Pages Type" to "Exists SQL Query" and the Condition to:
    SELECT 1 FROM DUAL WHERE :P1_REGION = 1(adjust the value at the end as appropriate for each list item).
    Andy

  • Set focus to a report region after select value (user) report region

    Hello,
    On my page I have 4 report SQL Query report regions (among themselves). After selecting (user) of a value (report region number 3 with column link), the result shown in report region number 4. However, the focus is on report region number 1. The user sees the results do need to scroll down to see the answer(in report region number 4).
    Does anyone have a solution for me with an example. Thanks.

    Hi Varad,
    sorry for the delayed response.
    Please check the page:- 9999 of App:-964
    I have made 2 simple reports with a button in each region.
    SUCCESS MESSAGE of first one:- first process run by first report
    SUCESSS MESSAGE of second one:- Saved Data..process run for second report
    when first process is run by clicking the <b>SUBMIT</b> button in the first region, we will see the same first region back. But, when we click the <b>SAVE</b> button of second region, page submits and we will see the first region and user should scroll down to see the second region.
    so, I am trying to see if I can have user see the same region back[second region,when SAVE button clicked, in this case] if he has done any operations on second region. My actual page has around 6 regions where scrolling down might be pain full for a end user.
    Have created this page in a hurry .. My actual pages and processes are doing some use full job, the page I have given here is only for our testing purpose. please do not mind.
    Thanks a lot for helping me..
    Chaitu..
    Edited by: Chaitu_Apex on Apr 14, 2010 9:51 AM

  • Only Change the DVD Player regions 5 times!?

    Really, is Apple so cheap that it thinks that is relevant?  I travel, I am an NGO, so I could change regions continuously but I am restricted on my Apple to five region changes.  Five!  I have now moved to Europe and cannot use the DVD player because I have changed it five times previously, yet i can buy a PC or a travel DVD player that will play any and all DVDs.  I now have a useless piece of software on my computer and a have to carry another DVD player because Apple are ******* ******.  I actually like Apple but this is ******* me off.  Maybe its time to look at the competition...

    neilfromwashington wrote:
    I have changed it five times previously
    And each time you were warned that, "You can change the region code of a DVD drive only five times (including the original setting); the fifth setting is permanent", weren't you?
    Maybe its time to look at the competition
    Definitely. And please do share the results.
    Below is an excerpt from my Fujitsu Lifebook user guide (capitalisation and stress is theirs):
    • ALL LIFEBOOK DVD PLAYERS ARE SET TO PLAY DVD TITLES WITH REGION CODE NUMBER 1 WHICH IS SPECIFIED FOR THE NORTH AMERICAN MARKET. THE REGION NUMBER IS A REGIONAL RESTRICTION CODE DEFINED BY THE DVD FORUM ACTING ON HOLLYWOOD REQUIREMENTS. DIFFERENT REGION CODES ARE RECORDED ON VIDEO DVD TITLES FOR PUBLICATION IN DIFFERENT AREAS OF THE WORLD. IF THE REGIONAL CODE OF THE DVD PLAYER DOES NOT MATCH THE REGIONAL CODES ON THE TITLES, THEN PLAYBACK IS IMPOSSIBLE.
    • YOU CAN CHANGE THE REGION CODE ON THE DVD PLAYER USING THE PROPERTIES MENU OF THE DVD SOFTWARE. NOTE, HOWEVER, THAT YOU CAN ONLY CHANGE THE REGION CODE UP TO FOUR TIMES. AFTER THE 4TH CHANGE, THE LAST CODE ENTERED BECOMES PERMANENT, AND CANNOT BE CHANGED.

  • Packet allocation

    Hello,
    Using Oracle 11.2.0.1
    Using Windows XP Professional
    create table approver
    approver_id number(4),
    working_place number(2),
    hq_id number(2),
    packet_no1 number(4),
    packet_no2 number(4)   --- if approver got 2 packets due to scarcity of approvers.
    create table contents
    packet_no number(4),
    book_id number(5),
    book_region number(2),
    approver_id number(4)   -- means this packet has been allotted to this approver.
    create table app_rule
    app_region number(2),
    avoid1 number(2),
    avoid2 number(2),
    avoid3 number(2),
    avoid4 number(2),
    avoid5 number(2),
    avoid6 number(2),
    avoid7 number(2),
    avoid8 number(2),
    avoid9 number(2)
    insert into approver values (34,4,1,0,0);
    insert into approver values (35,5,1,0,0);
    insert into approver values (36,7,1,0,0);
    insert into approver values (37,9,1,0,0);
    insert into approver values (38,4,1,0,0);
    insert into approver values (39,2,1,0,0);
    insert into approver values (40,9,1,0,0);
    insert into approver values (41,11,1,0,0);
    insert into approver values (42,22,1,0,0);
    insert into approver values (43,14,18,0,0);
    insert into approver values (44,25,18,0,0);
    insert into approver values (45,17,18,0,0);
    insert into approver values (46,6,18,0,0);
    insert into approver values (47,22,18,0,0);
    insert into approver values (48,30,18,0,0);
    insert into approver values (49,7,18,0,0);
    insert into approver values (50,17,18,0,0);
    insert into approver values (51,25,18,0,0);
    insert into approver values (52,3,11,0,0);
    insert into approver values (53,2,11,0,0);
    insert into approver values (54,1,11,0,0);
    insert into approver values (55,5,11,0,0);
    insert into approver values (56,19,11,0,0);
    insert into approver values (57,26,11,0,0);
    insert into approver values (58,27,11,0,0);
    insert into approver values (59,31,11,0,0);
    insert into approver values (60,16,11,0,0);
    insert into contents values (1240,5170,5,0);
    insert into contents values (1240,5178,5,0);
    insert into contents values (1141,1517,1,0);
    insert into contents values (1141,1507,1,0);
    insert into contents values (1214,4173,4,0);
    insert into contents values (1214,4070,4,0);
    insert into contents values (1214,7181,7,0);
    insert into contents values (1214,7178,7,0);
    insert into contents values (1214,8078,8,0);
    insert into contents values (1214,6678,6,0);
    insert into contents values (1141,19517,19,0);
    insert into contents values (1141,19507,19,0);
    ---If there are more than 9 different book_region in a packet then that packet
    ---has to manually entertained/dispatch.  After allotment those packets rows should be in a seperate table.
    insert into app_rule values (1,1,6,3,10,0,0,0,0,0);
    insert into app_rule values (2,2,11,32,4,6,9,19,0,0);
    insert into app_rule values (3,3,19,2,14,16,15,0,0,0);
    insert into app_rule values (4,4,2,1,0,0,0,0,0,0);
    insert into app_rule values (5,5,22,1,18,8,0,0,0,0);
    insert into app_rule values (6,6,8,7,5,0,0,0,0,0);
    insert into app_rule values (7,7,1,2,0,0,0,0,0,0);
    insert into app_rule values (8,8,9,10,11,12,13,14,15,16);
    insert into app_rule values (9,9,17,18,19,20,21,0,0,0);
    insert into app_rule values (10,10,6,7,8,9,26,0,0,0);
    insert into app_rule values (11,11,22,23,24,0,0,0,0,0);
    insert into app_rule values (12,12,25,26,27,28,29,30,31,32);
    ---Upto 33 regions, means person who is belonging to app_region, will not receive any book from avoid columns.
    ---plus HQ ID regions.Business Rule :
    Complexity Level 0 :
    -Packet of books sent to approver for their reading and any correction as per rule.
    Example :
    First Packet No. 1240 which belongs to region 5, because all books are from region 5. First approver No. 34 whose working region is 4 and HQ is 1. Now, we will scan app_rule for app_region=4 which have 4,2,1 regions for avoid and 5 is not in 4,2,1 so can we allot this packet to this approver ? No, we can not not, because approver's HQ (1) is also in avoid list, which should not.
    Ok, for 35, no it can not, more over it should not because if it happened, then it will be a blunder because approver's working region id is 5 and books are from region 5, so it should not.
    for 36, 7... 7th avoid are 7,1,2.. ok, but 1 is there i.e. approver's HQ.... so it can not.
    for 37 9... 9th avoid are 9,17,18,19,20,21. Yes, it is perfect, because neither 5 is in the list nor 1 (Approver's HQ).
    Complexity Level 1 :
    What about packet no. 1214, the complicated packet because it contains books from 4 different regions i.e. 4,7,8,6; means we will look those approver who is not working in :
    for 4 : 4,2,1
    for 7 : 7,1,2
    for 8 : 8,9,10,11,12,13,14,15,16
    for 6 : 6,8,7,5
    unique : 1,2,4,5,6,7,8,9,10,11,12,13,14,15,16 regions + their HQ ids. Who is from above... ie. first approver id 44 because neither 25 is in this list nor 18.
    Complexity Level 2 :
    Suppose there are 10 packets and we have only say 7 approvers who have sent their consent for this year. So, allotment should be that much smart and flexible who can interchange the packet internally for best fitting the allotment and for rest 3 packets it should double-allot the packet following above rule. Something like suppose packet no. 1000 has not been allotted due to less number of approvers and if packet no. 2000 has been allotted to 100th number approver, but this 2000 packet can be allotted to 1002 too, so allotment should be smart enough like packet number 1000 to 100 and packet no. 2000 to 1002 (internally interchange the packet i.e. best fitting of allotment).
    Please tell me I am clear in my question or I have to provide more clearity on business rule or I have to provide more inserts for the best checking.
    Yes, you can ask me, show us your effort in this regard, this is your job/work, why WE should do your task ?
    My reply will be : Basically, till now I remained busy in the admin part or you can say that I have not got more PL/SQL exposure (zero in PL/SQL) and I don't think that I can do this task without your esteem help in this forum, truly speaking I can not get the work done at my own alone. I am really very sorry, If am "giving" you my task, but its not really giving,
    I am just looking how this task will be done, if you please help me. We are at the designing stage, so if you can suggests any major changes in the design or there is flaw in the design. Rather than asking the question's part, I thought that it would be better to write the question as a whole.
    Regards
    Girish Sharma

    >
    I have just posted the column's definition
    >
    Thanks. Now it would be good if you do not change these again since we are using them as our baseline. Also the denormalized structure and data (e.g. for app_rule) makes it easier to see the data.
    I am using a normalized version of the rulel table I name app_rule1. Here is the DDL and INSERTs for region 4 which I am using to work thru your example for complexity level 0 packet 1240.
    create table app_rule1
    app_region number(2),
    avoid number(2)
    insert into app_rule1 values (4,4);
    insert into app_rule1 values (4,2);
    insert into app_rule1 values (4,1);I'm having trouble with your approver data for this; I think it violates the business rules but perhaps you could explain.
    Approver four data is
    insert into approver values (34,4,1,0,0);approver_id - 34
    working_place - 4 -- should have 'region' in the name because if I understand you correctly this MUST correspond to a region number - please confirm
    hq_id - 1 -- should have 'region' in the name for same reason as above - please confirm
    So in your explanation as to why you cannot use approver 34 for packet 1240 you said
    >
    No, we can not not, because approver's HQ (1) is also in avoid list, which should not.
    >
    My question - since approver 34 is in the avoid list for region 4 why does this approver have '4' for working_place? This '4' is the only thing that points to the rule table but it will always point to a rule record that we cannot use. This means approve 34 as defined by your data could never be used at all.
    If this is true then it should be illegal to attempt to put this approver record into the table.
    Is that analysis correct? My test code blew up with the first effort to follow your packet 1240 example because it tries to link data that shouldn't be linked.
    Related to that - is it your intention that an approver can only point to one 'rule' record? That seems rather limited.
    This code does not work properly because I need to change it based on your comments of the above but I will explain my initial effort
    -- test1
    -- query regions for one packet (could use DISTINCT but may not need to)
    with packet_regions as (
    select book_region from contents
    where packet_no = 1240
    -- query regions to avoid for one approver (including the approvers hq_id)
    avoid_regions as (
    select approver_id, working_place, hq_id avoid_region from approver
    union
    select approver_id, working_place, avoid avoid_region
    from approver a, app_rule1 r
    where a.working_place = r.app_region
    -- query possible approvers
    select approver_id from avoid_regions ar
    where avoid_region not in (select book_region from packet_regions)1. The first query is to query regions represented for one packet
    2. Second query is to select regions to avoid for each approver
    3. Third query is to use the first two to select the list of legal approvers - that is, approvers whose 'avoid' list (including their HQ) is not represented in the regions for the packet.
    Perhaps you can see how much simpler it is to have the app_rule data normalized rather than column-oriented (which would require parsing of some sort).
    I can continue testing when I understand your response to my questions above.

  • Error while saving default data type

    When I try to save system wide Default Data Format of any of the columns, an error pops out. Seems like an XML error:
    The current xml is invalid with the following errors:
    Bad xml instance!
    <?xml version="1.0"?> <sawsavedformat:metadata xmlns:sawsavedformat="com.siebel.analytics.web/savedformat/v1.1"><sawsavedformat:columnSavedFormats><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName="&quot;HT Catalog&quot;.&quot;Item As Was&quot;.&quot;Division Number&quot;"><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName="&quot;HT Catalog&quot;.&quot;Item As Was&quot;.&quot;Group Number&quot;"><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName="&quot;HT Catalog&quot;.&quot;Item As Was&quot;.&quot;Dept Number&quot;"><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName="&quot;HT Catalog&quot;.&quot;Item As Was&quot;.&quot;Class Number&quot;"><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName="&quot;HT Catalog&quot;.&quot;Item As Was&quot;.&quot;Subclass Number&quot;"><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName="&quot;HT Catalog&quot;.&quot;Organization As Was&quot;.&quot;Chain Number&quot;"><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName="&quot;HT Catalog&quot;.&quot;Organization As Was&quot;.&quot;Area Number&quot;"><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName="&quot;HT Catalog&quot;.&quot;Organization As Was&quot;.&quot;Region Number&quot;"><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName="&quot;HT Catalog&quot;.&quot;Organization As Was&quot;.&quot;District Number&quot;"><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName="&quot;HT Catalog&quot;.&quot;Organization As Was&quot;.&quot;Store Number&quot;"><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName="&quot;HT Catalog&quot;.&quot;Business Calendar&quot;.&quot;Fiscal Week&quot;"><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="left" vAlign="top"><saw:dataFormat xsi:type="saw:text" textFormat="plain"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName="&quot;HT Catalog&quot;.&quot;Unit Inventory&quot;.&quot;U BOP&quot;"><saw:displayFormat><saw:formatSpec suppress="repeat" wrapText="true" visibility="visible" hAlign="right" vAlign="top" imagePlacement="right"><saw:dataFormat xsi:type="saw:number" whistlerFormat="#,##0" commas="true" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat></sawsavedformat:columnSavedFormats></sawsavedformat:metadata>
    Line:2, Col:8982, Attribute 'whistlerFormat' is not declared for element 'dataFormat'
    Any suggestions?
    Thanks

    HI,
    Its known bug in obiee11.1.1.5. version try to apply obiee11.1.5.5.BP bug fixes version.
    fyi,
    bug 13370386 - 'THE CURRENT XML IS INVALID WITH THE FOLLOWING ERRORS: BAD XMLINSTANCE!' OCCURS
    bug 13249783 - OBIEE 11G THROWS BAD XML INSTANCE
    Thanks
    Deva

  • 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

  • Difference between text data and attributes in master data?

    Hello,
    a charcteristic in BW maintains texts, hierarchies and attributes.
    What exactly is the difference between texts and attributes?
    Attributes describe master data like a customer. The country where the customer resides, the industry etc. describe and classify the customer. Attributes are not just the structure/metadata of the characteristics. They are also the content. The following table should visualize what i mean:
    customer-no. | name
    112          | mcpherson inc.
    113          | donalds inc.
    Texts contain contain the description of a characteristic. Texts define a characteristic. An example is the customers name. It does not describe the customer but defines him/her.
    Is my understanding about these two parts of master data right?
    What else except the customer's name belongs to the texts?
    If I set up a characteristic like the customer in SAP BW, do I have to create an attribute "name". The name belongs to texts, not to attributes?? If I upload master data then, how does it work?
    Thanks in advance.

    Hi,
    If your analysis includes country and region then country  and region should be included in the Infocube.This is required because only if you include these characteristics then you can restrict your queries for country and region.You may need to select some particular countires/region and show the report.Then you have to restrict your queries to only those countries/region.This is possible only if you have these  characteristic in your infocube.
    I am just envisaging your model like this.
    Characteristic in the Infocube
    Customer
    Country
    Region
    Customer Attributes
    Customer Number (SID which is self generated)
    Customer Address1,2 ,3
    Registration No
    Date of Registration
    Deposit Amount
    etc ...
    Region Attributes
    Region Number (SID)
    Total Customers
    Sale Office Address
    Number of Sales Persons
    Customer Attributes
    Customer Number (SID)
    Total Customers
    Head Office Address
    Number of Sales Persons
    GDP
    Total Population
    So the conclusion is whichever entity you want to restrict or analyse should be a part of Infocube.It is very difficult to do analysis based on attributes as I mentioned in my earlier post that they are only "Display attributes" (u can just show that's it).
    Yes!! there are  methods available for analysis based on characteristics in attributes table and you have to do either with virtual characteristic or replacement path or with writing code in customer exits.But a good design and earlier study of all possible report combination and having a good design will avoid good amount of development time and changes.
    I have suffered  when I had only 0CALDAY in my cube and when I want to take a monthly analysis, I was unable to do it and then I have to redesign my whole cube.
    Please anyone, correct me if I am wrong.
    Regs
    Gopi.

  • Deleting record on basis of master table ID

    Hello,
    SQL> desc news
    Name                                      Null?    Type
    NEWS_ID                                   NOT NULL NUMBER(14)
    NEWS_DATE                                          TIMESTAMP(0)
    SL_ID                                              NUMBER(2)
    HEADING                                            VARCHAR2(3120)
    DESCRIPTION                                        VARCHAR2(3900)
    SQL> desc news_location
    Name                                      Null?    Type
    NEWS_ID                                            NUMBER(14)
    COUNTRY                                            VARCHAR2(32)
    REGION                                             NUMBER(2)
    SQL> desc news_product
    Name                                      Null?    Type
    NEWS_ID                                            NUMBER(14)
    PRODUCT_CATEGORY_ID                       NOT NULL NUMBER(14)
    PRODUCT                                            VARCHAR2(27)
    SQL> desc news_service
    Name                                      Null?    Type
    NEWS_ID                                            NUMBER(14)
    SERVICE_ID                                NOT NULL NUMBER(14)
    SRVIS                                              VARCHAR2(16)
    SQL> desc news_info
    Name                                      Null?    Type
    NEWS_ID                                            NUMBER(14)
    SOURCE                                             VARCHAR2(203)
    ORIGIONAL_NEWS                                     VARCHAR2(3900)
    HEADING                                            VARCHAR2(3110)
    SQL> select count(*) from news where TO_CHAR(news_date,'YYYY') <  2012;
      COUNT(*)
          8759I am trying to delete news that are published before 2012 but detail tables consists child record on basis of news_id. Certainly simple delete query will not work
    Please advise and thanks in anticipation

    Thanks again for favorable replies
    SQL> alter table news_info drop constraint NEWS_INFO_FK;
    Table altered.
    SQL> alter table news_info add constraint NEWS_INFO_FK FOREIGN KEY (news_id) REF
    ERENCES   news(news_id) on delete cascade enable novalidate ;
    Table altered.
    SQL> alter table news_info modify constraint NEWS_INFO_FK validate ;
    Table altered.
    SQL> alter table news_location drop constraint NEWS_LOCATION_FK;
    Table altered.
    SQL> alter table news_location add constraint NEWS_LOCATION_FK FOREIGN KEY (news
    _id) REFERENCES   news(news_id) on delete cascade enable novalidate ;
    Table altered.
    SQL> alter table news_location modify constraint NEWS_LOCATION_FK validate ;
    Table altered.
    SQL> alter table news_PRODUCT drop constraint NEWS_PRODUCT_FK;
    Table altered.
    SQL> alter table news_PRODUCT add constraint NEWS_PRODUCT_FK FOREIGN KEY (news_i
    d) REFERENCES   news(news_id) on delete cascade enable novalidate ;
    Table altered.
    SQL> alter table news_PRODUCT modify constraint NEWS_PRODUCT_FK validate ;
    Table altered.
    SQL> alter table news_SERVICE drop constraint NEWS_SERVICE_FK;
    Table altered.
    SQL> alter table news_SERVICE add constraint NEWS_SERVICE_FK FOREIGN KEY (news_i
    d) REFERENCES   news(news_id) on delete cascade enable novalidate ;
    Table altered.
    SQL> alter table news_SERVICE modify constraint NEWS_SERVICE_FK validate ;
    Table altered.
    SQL> delete from news where TO_CHAR(news_date,'YYYY') <  2008 ON DELETE CASCADE;
    delete from news where TO_CHAR(news_date,'YYYY') <  2008 ON DELETE CASCADE
    ERROR at line 1:
    ORA-00933: SQL command not properly ended
    SQL> select constraint_name, constraint_type, table_name, delete_rule
      2    from user_constraints
      3   where constraint_name= 'NEWS_SERVICE_FK';
    CONSTRAINT_NAME                C TABLE_NAME                     DELETE_RU
    NEWS_SERVICE_FK                R NEWS_SERVICE                   CASCADE
    SQL> select constraint_name, constraint_type, table_name, delete_rule
      2    from user_constraints
      3   where constraint_name= 'NEWS_PRODUCT_FK';
    CONSTRAINT_NAME                C TABLE_NAME                     DELETE_RU
    NEWS_PRODUCT_FK                R NEWS_PRODUCT                   CASCADE
    SQL> select constraint_name, constraint_type, table_name, delete_rule
      2    from user_constraints
      3   where constraint_name= 'NEWS_LOCATION_FK';
    CONSTRAINT_NAME                C TABLE_NAME                     DELETE_RU
    NEWS_LOCATION_FK               R NEWS_LOCATION                  CASCADE
    SQL> select constraint_name, constraint_type, table_name, delete_rule
      2    from user_constraints
      3   where constraint_name= 'NEWS_INFO_FK';
    CONSTRAINT_NAME                C TABLE_NAME                     DELETE_RU
    NEWS_INFO_FK                   R NEWS_INFO                      CASCADE
    SQL> delete from news where TO_CHAR(news_date,'YYYY') <  2008 ON DELETE CASCADE;
    delete from news where TO_CHAR(news_date,'YYYY') <  2008 ON DELETE CASCADE
    ERROR at line 1:
    ORA-00933: SQL command not properly ended
    SQL>Edited by: Christy H. on Jan 17, 2013 1:58 AM
    I removed ON DELETE CASCADE and ran again delete from news where TO_CHAR(news_date,'YYYY') <  2008; Wow deleted!!
    This forum is miracle to learn oracle. Thanks from the bottom of my heart

  • Report a problem

    I have purchased the fax service from Fax App many time, normally I always was charged $0.99 per transaction but in the last 3 transaction how come I was charged double transactions and the last order which is "Order ID: MJ5DGJ092T" it was not successful and display like payment error so I have purchased new fax service from IFax but I was charged them all. could you plese check my purchase history for me?
    Order ID: MJ5DF6VDNZ
    Item
    Seller
    Type
    Unit Price
    Fax App, Up to ten pages
    Report a Problem
    Faxonline GmbH
    In App Purchase
    $0.99
    Fax App, Up to ten pages
    Report a Problem
    Faxonline GmbH
    In App Purchase
    $0.99
    Order ID: MJ5DG1V21M
    Item
    Seller
    Type
    Unit Price
    Fax App, Up to ten pages
    Report a Problem
    Faxonline GmbH
    In App Purchase
    $0.99
    Fax App, Up to ten pages
    Report a Problem
    Faxonline GmbH
    In App Purchase
    $0.99
    Order ID: MJ5DGJ092T
    Item
    Seller
    Type
    Unit Price
    Fax App, Up to ten pages
    Report a Problem
    Faxonline GmbH
    In App Purchase
    $0.99
    Fax App, Up to ten pages
    Report a Problem
    Faxonline GmbH
    In App Purchase
    $0.99
    iFax - Send & Receive Faxes, fax up to 10 pages to a Group A Region number
    Report a Problem
    MAPLEWOODS ASSOCIATES LTD
    In App Purchase
    $1.99

    We cannot do it here on this forum. We are just community that help each other to solve problems.
    You need to conntact apple store directly. You should have the contact info on the statement you get (above)
    also I've noticed you have the option to Report a Problem.
    Did you try that?

Maybe you are looking for

  • How to process Line Selection on ALV Table in ABAP WebDynpro

    Hi there, I have a view with an ALV table whose context node retrieves its data from a Service Call for a method. The method provides certain data of a database table which the ALV displays. Now I would like to be able to select one row of that ALV t

  • HELP: clearing a Vendor F-44

    Hi All, For a certain vendor, I have to clear 3 items all with Special G/L Indicator. The balance is zero. When i launch F-44 and select only items whith Special G/L Indicator, processing the items SAP shows me the three items, but the value of one o

  • How to retrive the old messages in sxmb_moni (integration engine)

    Hi Expert, We were trying to call RFC and send some messages through XI. Due to some connection issue the message was failed in integration engine(MONI). As this messages had failed last week. We are not able to see the messages in MONI. Now we wante

  • Saving from Lightroom to elseware on PC

    Hi There-   I am a very new user to Lightroom and would like to know if you can save an edited or worked on photo from Lightroom to elseware on the computer. I looked for a "save" or "save as" option ion the "file" in the upper toolbar, but it did no

  • CreateClob variable

    Hi I need to create a Clob variable that will be filled with some text. After that I will use this variable in a stored procedure. I'm using the following code: Connection conn = null; Clob c = null; conn = db.getConnection(); c = conn.createClob();