Variant Length 45 char limit - Help

Friends,
Iam developing a program to download all variants from current environment which are to be uploaded on other environment. Im using RS_VARIANT_CONTENTS FM. Problem is : when I Extract I get only 45 length limit for the variable value on the selection screen. This issue is with RSPARAMS structure which holds only upto 45 chars.
Is there any other way to download and upload variants other than above FM. Like  for downloading program we use READ REPORT....anything as such (internal commands) exists for variants too....???????
If any of you have faced this issue, please do pour in your valuable inputs.
thanks

Rob,
Seems you might be thinking that my requirement is little wierd......lemme explain you in detail.
We are moving from a Windows system to a Unix based as part of Upgrade. Because of this I have to change all the variants from
P06XXXX\VAROPT\ to /var/opt/ps1/ and we are expecting variant file path's to have more than 45 characters but when its changed to Unix path for sure max chars would be 43 (below our 45 limit).
My approach for this is :
1) Use the code in OSS Note to download all variants from Windows box and upload in new Unix box (paths would still be
P06XXXX\VAROPT\ ).
2) Once all variants all loaded in their old format, I would now extract the selection screen strucutre (using FM), I could use FM to extract values also but again 45 char limit is haunting.
3) Loop at the structure and IMPORT each variable. change variable content to Unix form and upload them using FM (RS_VARIANT_VALUE_CHANGE or similar).
Now my problem : I am not able to use IMPORT statement in a LOOP.
i.e.
LOOP AT OBJECTS.
  IMPORT objects-name TO T_VAR FROM DATABASE VARI(VA) ID ST_KEY.
ENDLOOP.
Please help with this....
thanks

Similar Messages

  • Set variables with data of varying lengths?

    I am sending data collected from a CVP application back to ICM in the array variable user.microapp.FromExtVXML(0).  Now I want to parse the data and put it into ECC Variables.  I can do all this but one issue:  how do I handle data that can have varying lengths?   For example, the first piece of data is an account number which can either be 7 or 10 digits.  Each piece of data is separated by a comma, so if I could extract using that as a separator, it would be ideal.
    Here's an example to show you what the data looks like from the ECC:
    1234567,1,G,Smith,Mary
    =Account # (can be 7-10 digits), Authentication Flag (always 1 digit), Tier (always 1 digit), Last Name (varied length), First Name (varied length)
    Appreciate your help on this.
    Walter

    The way I usually do these complicated parsing operations is to simply use Call Tracer to send a dummy call through a test script. Have a SET node that sets up a test string into PV1 - say "Account=1234567,Flag=1,Tier=G,Last=Smith,First=Mary" (stay under 40) then feed it into a SET node that sets another PV using a formula, then have an IF node that tests the value of the PV against the expected result. No need to make a real call. Then keep fiddling with the formula in the SET node until you get it to sing and dance.
    Once you understand how the if(), find(), after() etc functions all work and your SET node is working, you can easily turn it into a custom function and then try the custom function again with Call Tracer.
    This is way faster than actually making calls through CVP. Many script writers try to develop the whole enchilada rather than taking the easy way out with Call Tracer.
    Regards,
    Geoff

  • Help! I need a simple powershell command to display all folders & files over the 260 char limit

    Can anyone help me please? I'm trying in vain to identify any files or folders I have in a directory over the 260 char limit.
    my powershell knowledge is quite limited so I've hit the wall with ideas.
    Any help appreciated.
    Thanks

    Would running this command on its own within powershell work?
    Or do I need to add this to your script?
    get-folderitem | Where {
    $_.fullname.length -gt 260

  • Howto overcome the 255 char limit in XSLT when outputting using method=text

    Hi, I am facing a problem in my XSLT program to output a CSV file. The header line is exceeding 255 char limit, seems built into the editor and looks like it repeats the 255th character into the next line where it finishes the rest of the line. Now this screws the columns in the CSV file. I have tried different combinations of <xsl:text></xsl:text> tags but to no avail.
    Is there a way to overcome this problem, spanning a line onto multiple lines in SAP but getting a single line in the output ?
    Thanks in advance.
    Swapan

    I should have known better to searched in SAP provided documentation instead here first. I needed to end the line with &> chars to continue into the next line.
    http://help.sap.com/saphelp_erp2004/helpdata/en/50/b6463c32a3fe13e10000000a114084/frameset.htm

  • My app won't scroll to my intended length. Please help.

    My app won't scroll to my intended length. Please help.

    Oh, iPhysics. I set it to scroll to 3500 pixels, but it won't go past 800.

  • Char limit for .mov format?

    Originally posted in the iTunes for Mac forum but to no avail; I would really like to know if there is a char limit in the comments fields of the movie .mov format? When typing in comments for a .mov I find that only a certain amount save leading me to believe either:
    a) iTunes enforces a char limit
    b) .mov has a char limit
    Either way its a disaster for my media handling, I'm quite verbose.

    Hamper..don't hold your breath for a fix since 255 sounds horribly like a limit defined by the underlying architecture... Chances are that there is a single data byte that is used to tell iTunes just how many characters there are in the Comments field. As you may/may not know, one byte can only record a max of 255 characters.

  • Variant .. Please Help

    Hi guru's
    I created varaints for selection screen (FBL5N) customer line items. My problem is tht i want these selection varaint to be come default depanding on specific user...Please tell me is it possible ??
    Please help and if possible please let me know !!
    Many thanks in advance..sure points
    Regards
    Inder

    dear friend
    please try out with the following
    VARIANT CONFIGURATIONS:
    Slide 1: VARIANT CONFIGURATION OVERVIEW Prepared by Arun prasad C R *Please place your comments
    Slide 2: Variant Configuration Introduction: • Variant Configuration is useful if you have a large number of combination of parts that go into a product. It means different permutations and combinations of the parts for same material. • If you maintain a unique material code for each possible combination of parts, you require a large number of material numbers. • Usually involves Make to Order Production Process Variant Configuration Examples: • A customer ordering a computer can choose different combinations of monitor, CPU, keyboard. • A customer ordering a car can choose different combinations of accessories and color. • In a business involving steel manufacturing, the customer may order steel involving different physical properties like tensile strength, diameter. Source: SAP
    Slide 3: Industries for Configurable Products Variant Configuration Source: SAP
    Slide 4: Cross Module Integration Variant configuration is integrated with the following applications: CA Classification LO Material Master PP Bill of Material PP Routings PP Material Requirements Planning (MRP) PP Production Orders PP–PI Master Recipes Variant Configuration CO Costing SD Sales SD Conditions MM Purchasing Source: SAP
    Slide 5: Overview of Terms Variant Configuration Source: SAP
    Slide 6: Overview of Terms • A configurable material has a special bill of material called the Super BOM in which all possible combinations are stored. • The product is configured in the sales order by choosing the required Characteristic Values. • The requirements are passed on Production Planning. On Explosion of the Bill of Material, the system selects the components assigned to the characteristics values in the order. Variant Configuration • After production, the material is assigned as sales order stock for delivery to customer. Source: SAP
    Slide 7: • Sales Order Processing
    Slide 8: IDES Demo Process Steps to be used in the demo: • Creating a Sales Order • Checking Requirements Using MRP • Requirements Planning • Converting the Planned Order into a Production Order • Confirming the Production Order • Checking the Production Order Settlement Variant Configuration • Creating a Delivery • Creating a Billing Document Source: SAP
    Slide 9: Enterprise Structure used for demo Company Code 1000 Sales Org 100 Distribution Channel 12 Variant Configuration Division 00 Plant 1000 Storage Location 0001 Shipping Point 1000 Source: SAP
    Slide 10: MTO Process Overview Make-To-Order Production With a Configurable Product: In this process, you create a sales order in SD and transfer the requirements to PP. The requirements are checked using MRP, before a production order is generated. This production order is created in PP. Shipping and billing both occur in SD. Finally, you check the costs and revenues in CO. Variant Configuration Source: SDN
    Slide 11: Creating a Sales Order (T Code :VA01) • After entering the sales data, a configuration screen pops up. • Configure the material by selecting the characteristics. • Note that the value of Variant Conditions changes as per selection. Variant Configuration Source: SAP
    Slide 12: Creating a Sales Order (VA01) • The system allows analysis of Object Dependencies and Variant Conditions. • Item Category determined in Sales Order is TAC. • Note the Material Availability Date and save the sales order (for test11048 and 11059). Variant Configuration Source: SAP
    Slide 13: • Configuration for VC
    Slide 14: Configuration Details: Material Type OMS2: In definition of KMAT Material Type, indicator ‘Material is Configurable’ is set Other material types like FERT (Finished Product) can also be used if the indicator is set in material master Variant Configuration Source: SAP
    Slide 15: Configuration Details: Item Category in sales order VOV4: Item Category determination is set to determine item category TAC Variant Configuration VOV8: Item Category TAC Source: SAP
    Slide 16: Configuration Details: Condition type for Pricing Condition types VA00 and VA01 (%) are available in Standard SAP for Variant Pricing Variant Configuration Source: SAP
    Slide 17: Configuration Details: Requirement type KEK The requirement class controls the MRP and the requirements consumption strategy as well as the relevancy for planning, settlement profile for costing. Requirements type KEK is determined for strategy group 25 and also for item category TAC. Variant Configuration Source: SAP
    Slide 18: Classification System: Characteristics Mayback 57 S Engine Color Rear wheel Seat Exhaust Antitheft device Variant Configuration Other Options Source: SAP
    Slide 19: Classification System: Characteristics Variant Configuration Source: SAP
    Slide 20: Classification System: Characteristics Variant Configuration Source: SAP
    Slide 21: Classification System: Characteristics CT04: Create characteristics • Data type can be CHAR, NUM, DATE, TIME, CURR Variant Configuration List of values and default value for characteristics can be stored in Value tab. Source: SAP
    Slide 22: Reference Characteristics Reference characteristics are characteristics that refer to table fields. Variant Configuration Tables / Structures whose filed values can be changed by dependencies: SDCOM - Communication between SD and Variant Configuration VCSD_UPDATE - Table for Updating Sales Documents from the Configuration MMCOM, STPO, PLPO, PLFH, PLFL Tables / Structures whose filed values can be read by dependencies: VBAK, VBAP, VBKD, VBPA_AG, VBPA_WE, VBPA_RE, VBPA_RG VEDA, MAEPV, MAAPV Source: SAP
    Slide 23: Classification System: Characteristics CT04: Create characteristics • Object dependencies like pre conditions, selection condition, action, procedures can be created for characteristics • Object dependencies like pre conditions, action, procedure can be created for characteristic values Variant Configuration Source: SAP
    Slide 24: Classification System: Class CL01 /CL02: Create class under class type 300 for Variants Variant Configuration Assign the characteristics to the class. During Material Master creation for Super BoM, this class will be used in the Classification view. Source: SAP
    Slide 25: Material Master of Super BoM (MM02) • Basic Data 2 Screen: Set ‘Material is Configurable’ Indicator • To determine item category TAC in sales order, maintain a suitable item category group such as 0002 • MRP 2 View: Procurement type ‘E: In house Production’ • MRP 3 View: Strategy Grp. ’25: Make-to-order for configurable’ used for demo • MRP3 View: Availability Check ’02: Individual Requirement’ • Classification view: Attach the variant class Variant Configuration Source: SAP
    Slide 26: Bill of Materials (CS01 / CS02 / CS03) Variant Configuration Source: SAP
    Slide 27: Object Dependency in BoM (CS02) Components in Production Order can be selected using Object Dependency type Selection Condition Variant Configuration Source: SAP
    Slide 28: Routings (CA02) Operations in Production Order can be selected using Object Dependency type Selection Condition Variant Configuration Source: SAP
    Slide 29: Configuration Profile: Process Planned/production Order; explosion indicator None (others Single level or Multiple level) The material has a BOM that is not relevant to the sales order. Only the characteristics that describe the variant are required. The components are determined later during material requirements planning or production, so there is no need to explode the BOM in the sales order. Sales order (SET): See next slide also In the sales order, sales-relevant components are shown as sub-items of the header material. Requirements are transferred and pricing is calculated at component level, not at header material level. Order BOM You create a sales order. In order BoM, you can insert extra items or delete items manually. The Variant Configuration changed BOM is stored as a separate BOM for the sales order. Source: SAP CU42
    Slide 30: Configuration Profile: SET This processing form means that in the sales order you can only process sales-relevant BOM items. You can use the item category group like 0004 at configurable material level to define that requirements transfer and pricing are at component level. For example, a PC is made up of the components monitor, CPU, keyboard, and printer. These components are all salable materials that are manufactured separately. In the sales order, you want to see the individual components that make up the computer as order items, as well as the whole computer. In the sales order, these products are grouped together in a SET. For this reason, this type of processing is also referred to as set processing. Variant Configuration Source: SAP
    Slide 31: Configuration Profile: Dependencies Dependencies like Actions and Procedure can be assigned to Configuration Profile. Variant Configuration Source: SAP
    Slide 32: Configuration Profile: Variant Table • Tables are used to store combinations of values for different characteristics • A table HD_1300_COLOR_PR is created in CU62 transaction. It has 2 fields: HD_COLOR (key field) and SURCHARGE. The selected characteristic will be transferred to HD_COLOR and surcharge to SURCHARGE2. • The table contents are given below (see transaction CU60) Variant Configuration VK30: Has description entries for the surcharge column listed above VK12: Will pick up pricing value based on condition type VA00 Source: SAP
    Slide 33: Pricing Check definition of characteristic SURCHARGE2 – Additional data tab -> reference table and field Variant Configuration Simple method to achieve Variant Pricing is given below: • Create multiple value characteristic SURCHARGE2 referring to SDCOM-VKOND. • Put this characteristic in the class HD-000 which was used for the configurable material • Now go to CT04 and change the Characteristic HD_COLOR Go to values tab and select Red. Go to Extras-> Object Dependencies->Editor and then select Procedure. In front of 000010 Enter $self.surcharge2='HD-003_03'. Similarly Select Black to enter $self.surcharge2='HD-003_02‘. Same way 'HD-003_01’ for Silver • VK30: Has description entries for the surcharge column listed above • VK12: Will pick up pricing value based on condition type VA00 Source: SAP
    Slide 34: Pricing VK30: Maintain descriptions for variant price conditions (optional step; done while creating dependencies for surcharges; maintains consistencies of configuration) Variant Configuration VK11 / VK12: Maintain actual condition record for variant price surcharges Source: SAP
    Slide 35: Pricing Factors Pricing factors can only be maintained on characteristic level. The syntax of pricing factors is as follows: $SET_PRICING_FACTOR ($SELF, <characteristic>, <variant key>, <factor>) This expression contains the following information: • The characteristic that refers to structure SDCOM, in which variant conditions are defined. • The variant key used to infer the condition for a characteristic value. Variant Configuration • The factor by which the surcharge increases. Source: SAP
    Slide 36: Material Variant • For variants that are required frequently, create material variants, which can be produced without a sales order and kept in stock. • When a sales order is received, check whether the variant is in stock and deliver immediately. • The material master record of a material variant is linked to the configurable material and configured using the characteristics of the configurable material. Variant Configuration Source: SAP
    Slide 37: Material Variant in Sales Order On the value assignment screen, you can check whether the values assigned match the configuration of a material variant. Variant Configuration Source: SAP
    Slide 38: Material Variant Replacement of configurable material by a material variant Variant Configuration Source: SAP
    Slide 39: Material Variant Item category gets changed to TAN; Pricing will also change as per new MTS product. Variant Configuration Source: SAP
    Slide 40: Summary of day 1 By now, you should be comfortable with the following topics: • Explain what Variant Configuration is and its use in make to order scenario • Using Variant Configuration during sales order processing • Configuration details like item category and condition types • Classification System - Characteristics and Classes • Super BoM, Configuration Profile, Object Dependencies • Pricing Surcharges in sales order processing Variant Configuration • Using Material Variants for make to stock scenario Source: SAP
    Slide 41: • Day 2: Understanding Object Dependencies in detail
    Slide 42: Dependency Types Variant Configuration Source: SAP
    Slide 43: Pre Condition Variant Configuration Only if the model specified is racing, the bicycle can have 21 gears. 1. Create a precondition with the following source code: MODEL eq 'Racing' and Specified MODEL 2. Allocate the precondition to value 21 of characteristic GEARS Source: SAP
    Slide 44: Selection Condition A selection condition is allocated to each component and each operation. This selection condition determines which components and operations are selected for a variant. Variant Configuration Source: SAP
    Slide 45: Changing Master Data with Dependencies In variant configuration, you can use reference characteristics with dependencies to change field values of tables for bills of material (BOMs), task lists, and master recipes. Table names and fields are given below for reference. Table STPO field MENGE can be used to change component quantities of BoM. Table PLPOD field VGW01 can be used to change setup time of Operation. Variant Configuration Source: SAP
    Slide 46: Procedures Procedures can set default values for a characteristic (can be overwritten by the user) Variant Configuration Source: SAP
    Slide 47: Procedures • Set default values: $SET_DEFAULT ($SELF, <characteristic>, <term>) For example: ( $SET_DEFAULT ($SELF, COLOR_CHAR, 'BLUE'), $SET_DEFAULT ($SELF, GLOSS_CHAR, 'NONE') ) IF $root.PC_CASING_CHAR = 'TOWER' • Delete default values: $DEL_DEFAULT ($SELF, <characteristic>, <term>) Variant Configuration Produce a sum of the values for a characteristic in a multi-level configuration: $SUM_PARTS ($SELF, <characteristic>) It can be used to calculate the weight of components and transfer the same to structure VCSD_UPDATE, gross weight field BRGEW • Add the components of a BOM together: $COUNT_PARTS (<$SELF>) • Surcharge for variant conditions in Pricing: $SET_PRICING_FACTOR ($SELF, <characteristic>, <variant key>, <factor>) Source: SAP
    Slide 48: Constraints and Dependency Net The main purpose of a constraint is to monitor the consistency of a configuration. There are four sections in a constraint. 1. OBJECTS: Declaration of all classes and objects used. 2. CONDITION: Pre requisite for processing the constraint. 3. RESTRICTIONS: For interdependencies and consistency check; check and set values. 4. INFERENCES: Enter the characteristics for which characteristic values are to be inferred. Variant Configuration Constraints are grouped together in dependency nets. The dependency net can be allocated to a configuration profile. Example: The hard disk can only have the value ‘1620’ for a tower, or ‘850’ for a mini tower. OBJECTS: PC IS_A (300) PC RESTRICTIONS: PC.HARD_DISK = ‘1620’ if PC.CASING = ‘Tower’, PC.HARD_DISK = ‘850’ if PC.CASING = ‘Mini tower’. Source: SAP
    Slide 49: Actions Actions can be used to infer values for characteristics. Actions can also be used to change field values in BOM items or operations in routings. Procedures can set default values for a characteristic, which can be overwritten by the user. The user cannot overwrite values that are set by an action. For new developments, use Procedures rather than Actions (to become obsolete) Variant Configuration Source: SAP
    Slide 50: Object Variables used in Multi level configurations Variant Configuration Source: SAP
    Slide 51: Allowed Dependency Types • Preconditions are allowed for characteristics and characteristic values. • Selection conditions are allowed for characteristics, BOM items, operations, and production resources/tools. • Procedures & Actions are allowed for characteristics, characteristic values, BOM items, operations, and configuration profiles. • Constraints can only be linked to a configuration profile via dependency nets. Variant Configuration Source: SAP
    Slide 52: Processing Sequence for Dependencies • Each time you enter a value for a characteristic on the value assignment screen and confirm the value, the system processes all the dependencies. • The dependencies are processed in the following sequence: 1. All actions several times, until no more values can be inferred. 2. All procedures exactly once in the following sequence: a) Procedures for the configuration profile in the order you defined b) Procedures for characteristics Variant Configuration c) Procedures for characteristic values The procedures for each characteristic or value are processed in the order you defined. 3. Actions Values set by procedures can also trigger actions. For this reason, all actions are processed again. 4. Preconditions 5. Selection conditions for characteristics Constraints are processed in parallel with points 1–3, if all the objects in the OBJECTS section are present, and if all the conditions in the CONDITIONS section are fulfilled Source: SAP
    Slide 53: • Transfer to Production Planning (Demo)
    Slide 54: 2. Checking Requirements Using MRP (T Code :MD04) Step1 to create sales order has already been discussed earlier. 2. Stock Requirements List: • The sales order is displayed as a separate planning segment (sales order stock required on material availability date and sales order). Variant Configuration Source: SAP
    Slide 55: 3. Requirements Planning (T Code :MD50) The sales order will now be converted into a planned order. Planned Orders represent the first step toward an actual production schedule for the Shop Floor. Variant Configuration Source: SAP
    Slide 56: 4. Convert the Planned Order into a Production Order (MD04) • Planned Orders are a result of MRP run and serve to provide an initial Production Schedule. • Production Orders contain comprehensive information to support a shop floor schedule and provide a method to confirm operations performed. • Production orders can be created with reference to a Planned Order. Variant Configuration Source: SAP
    Slide 57: 4. Convert the Planned Order into a Production Order (MD04) Object Dependency: BoM Selection Condition ensures only necessary material components are taken. Variant Configuration Source: SAP
    Slide 58: 4. Convert the Planned Order into a Production Order (MD04) Object Dependency: Routing Selection Condition ensures only necessary operations are taken. Variant Configuration Source: SAP
    Slide 59: 4. Convert the Planned Order into a Production Order (MD04) Prior to release of order, it is not possible for anyone to enter confirmations for the operations in the order. Release the Order and Save it.  Gantt chart.&#61614; Graphic &#61614;Display the operation scheduling overview, choose Goto  Variant Configuration Source: SAP
    Slide 60: 4. Convert the Planned Order into a Production  Analysis Variant&#61614; Costs &#61614;Order (MD04) Display the planned costs, choose Goto  Configuration Source: SAP
    Slide 61: 5. Confirming Production Order (CO11N) Production  Time Ticket Variant&#61614; For Operation &#61614; Enter &#61614; Confirmation &#61614;Control  Configuration Source: SAP
    Slide 62: 5. Confirming Production Order (CO11N) • Back flushing (posting of an issue of components or material withdrawals) • Storage of the finished product in the warehouse to sales order stock • Goods Movements are posted (errors if any can be corrected in COGI) • Actual costs are calculated • Just in case, to close the order without yielding a product, perform Restrict Processing -> Technical Completion for Production Order in CO02. Variant Configuration Source: SAP
    Slide 63: 5. Confirming Production Order (CO11N) • Sample Material Document and FI document entries are shown below Variant Configuration Source: SAP
    Slide 64: 6. Checking the Settlement of the Production Order &#61614; Settlement &#61614;From the Production Control node, choose Period-End Closing  Individual Processing (KO88) Perform order settlement to transfer the costs of the production order to sales order. Analyze the current cost situation for the Production Order Variant Configuration Source: SAP
    Slide 65: 7. Creating a Delivery (VL10G for delivery due list, VL01N for single delivery) Assign a serial number to the material. Pick and post the goods issue. Movement type will be 601 E indicating delivery from sales order stock. Accounting document will be generated to capture the change in inventory. Variant Configuration Source: SAP
    Slide 66: 8. Creating Billing Document (VF04/VF06 for due list, VF01 for single invoice) VF01: Create the invoice – sample accounting entries (without tax) are shown below F-28: Receive the payment from the customer Variant Configuration Source: SAP
    Slide 67: Other Information • CRM: It is possible to have configurable products among your Online Store offerings using the IPC (Internet Pricing and Configurator). It allows customers to interactively choose product options via an easy-to-use interface. Customers can mix- and-match these options to build the exact product they wish to purchase. • ECC 5.0: Single transaction PMEVC – Modeling Environment for VC Variant Configuration Source: SAP
    Slide 68: Summary By now, you should be comfortable with the object dependencies and the following topics: • Pre conditions • Selection conditions • Procedures • Actions • Constraints and Dependency Net Variant Configuration • Transfer of sales order requirements to PP • Delivery from sales order stock • Invoicing the customer Source: SAP
    Slide 69: Variant Configuration
    regards,
    amlan

  • How can I convert an array with varying length into a cluster

    Hi,
    I need to convert an array of n elements into a cluster. Usually, it only involves the "Array to Cluster" function. But since the array length is not constant and the number of elements in the function is constant and can not be changed programaticaly, I need to find another way to do that.
    Any ideas?
    Thanks.

    Hi,
    I also tried to do this but without success. I think that's not possible.
    For me it's a general problem using labview. I often wanted to generate standard controls dynamically which is not possible (or I haven't found the solution yet). So I think that's the reason why you can't create a cluster during runtime (the program would have to add controls dynamically to the cluster).
    Do you have an upper limit for your array-size? Although it needs a lot more memory, it would be a possibility to create the cluster with the maximum number of elements.
    If you don't have a maximum, you will have to look for another way, I'm afraid.
    Thomas
    Using LV8.0
    Don't be afraid to rate a good answer...

  • Over limit - help with options

    I have a wedding dvd that is 4.59 GB so it's just a hair over the limit. I need it to be best quality for viewing - so the encoding is set right now at "Best Performance." I have menus at 780 MB (they have motion and audio - audion is only like 5 MB, motion I already reduced menu as a QT menu to play in background - it's only 21 MB, so that's not going to get me there by eliminating).
    I don't think I want to change quality of encoding - or is there a setting that is less that won't change viewing quality on DVD?
    Or, how many minutes do I need to cut? If I cut video, then how do I replace the video on iDVD. Everything is all set and customized, not a standard theme, so I don't want to redo. Would like to replace the movie for "Play movie" and will chapters all stay set pulling from the movie?
    ARGH - so close!
    Thanks for your help -
    Alexa

    Or, how many minutes do I need to cut?
    Did you check project info ? For example .....
    Click Here:
    If DL is supported on your Burner then you should be ok provided iDvd can see the settings for DL as opposed to SL.
    Burning to a DVD+R DL (Double Layer) disc
    Newer SuperDrive optical drives in Macintosh computers can burn discs in DVD+R DL (Double Layer) format. Double-layer discs store almost twice as much content as single-layer discs, making them a great choice for large projects.
    To see whether your computer’s SuperDrive can burn DVD+R DL discs, choose Project > Project Info. If you see 8.0 GB (Double Layer) in the DVD Type pop-up menu, you can use DVD+R DL discs for your project.
    To burn a project to a DVD+R DL disc:
    With the finished project open in iDVD, choose Project > Project Info and then choose Double Layer (DL) from the DVD Type pop-up menu.
    Select the encoder setting you want to use. If you have more than 120 minutes of content, select High Quality.
    Click the Burn button (shown below).
    When prompted, insert a DVD+R DL disc into the drive.
    You can use your internal SuperDrive or an external third-party drive.
    If the disc isn’t blank, iDVD asks whether you want to erase the disc.
    If your project is small enough to fit on a single-layer disc and you insert a double-layer disc, you see a dialog giving you the option to change the media type. You can cancel the burn and start again, or insert a single-layer disc and continue.
    You should always burn double-layer discs directly from iDVD and not from a disc image. Double-layer discs burned from a disc image may cause playback issues in some DVD players, such as freezing during playback.
    NOTE: After burning, to eject a disc from your computer’s internal disc drive, press the Media Eject key on your keyboard, if there is one. On keyboards with no Media Eject key, hold down the F12 key until the eject icon appears and your disc is ejected.
    Hope this helps but if not just come on back.

  • Jeode 255 char. limit

    I have the Jeode EVM on my PDA. I have to execute a code for which I have to list 9 jar files. The entire .ink file is around 400 characters. Could someone please tell me if there is a way to increase the 255 character limit or if I could change the class path to point to there jar files. I tried looking for this in regedit but did not know what command to tweek.
    Could someone please help me. I am stuch up here and need help desperately.
    Thanks

    It is possible to get parameters from file (and setting up classpath by this), when calling evm (in .lnk). Now I can't check what the parameter is (-f ?). It should allow omit the 256 characters limit in .lnk. Try to run evm with parameter which show all options (maybe advanced options). If you couldn't find this, I will check it later and give you detailed information.
    regards,
    prusak

  • SQLLOADER: Large Data Loads: 255 CHAR limit?

    Issue: I'm trying to load a delimited text file into an Oracle table
    with data that execeeds 255 characters and it's not working correctly.
    The table fields are set to VARCHAR2 2000 - 4000. No problem. Some of
    the data fields in the file have over 1000 characters. Ok. When running
    a load, SQLLOADER seems to only want to handle 255 characters based on
    it's use of the CHAR datatype as a defult for delimited file text
    fields. Ok. So, I add VARCHAR(2000) in the .ctl file next to the fields
    that I want to take larger datasets. That does not seem to work.
    When I set a field in the control file to VARCHAR(2000), the data for
    that field will get into the table. That's fine but, the issue is
    SQLLOADER does not just put just that field's data into the table, but
    it puts the remainder of the record into the VARCHAR(2000) field.
    SQLLOADER seems to fix the length of the field and forgets I want
    delimiters to continue to work.
    Anyone know how to get SQLLOADER to handle multiple >255 data fields in
    a delimited file load?
    jk
    Here is my control file:
    load data
    infile 'BOOK2.csv'
    append into table PARTNER_CONTENT_TEMP
    fields terminated by ',' optionally enclosed by '^' TRAILING NULLCOLS
    (ctlo_id,
    partners_id,
    content2_byline ,
    content2 varchar(4000),
    content3 varchar(2000),
    content9 varchar(1000),
    submitted_by,
    pstr_id,
    csub_id)
    null

    I have been sucessful using char instead of varchar. But having
    the optionally enclosed by value in the data has always solved
    the problem.

  • CAMA_DEPENDENCY_MAINTAIN - Char limit

    Hi Gurus!
    I'm using FM CAMA_DEPENDENCY_MAINTAIN to update/create objects dependencies for my boms.
    I'm facing now a problem: i cannot upload dependencies with source longest than 50 chars!
    The  SOURCE table of FM accepts sources up to 72 chars, as standard sap transaction, but when i try to update them, they are trunked!
    I'm working on ECC 6.0 and i looked for some Sap Notes but nothing seems to help me.
    Have you any suggestion?

    Solved.
    The problem was due by the information the user put in the input file.

  • .mov comments tagging char limit??!!

    Adding comments to .mov files in iTunes I notice that upon finishing the dialogue disappears as if everything is okay.. but its not as there seems to be a limit to the amount of characters one can use in the comments field.
    The problem I have it that no notification is given to signify the cut off point, like a ticker with remaining chars left, or that the whole of the text written is not embedded. This is quite unsettling, can anybody please confirm if there is a limit.

    I just received a reply from a metadata pro telling me that the mov format has no char restrictions for the comments field and it must be iTunes that is restricting the comments I can leave. Humf.
    I emailed Apple about this, I think that comments should be infinite in size, I like a good story with my movies, that I shot. On the other hand (unlike the iPhone v2.0 software) he said that as mov is an Apple format that there would be no data corruption from tagging with iTunes :))

  • Maximumn char limit for Ebz  instance naming ?

    Hi ,
    Can anyone tell me what is the max length for R12 instance name ?

    Thanks Hussain.
    From the note that you and helios send .It appears that database name can have 8 or more than 8 chars.
    I think OID has limits for db_name more then 8 chars it doesn't recognize.
    Does it mean for Rac , I can set db name 8 chars and instance name 9 chars ?
    Looks like instance name can set upto 16 chars. Pls advise.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
    Data Mining and Real Application Testing options
    SQL> desc v$instance;
    Name Null? Type
    INSTANCE_NUMBER NUMBER
    INSTANCE_NAME VARCHAR2(16)

  • 200 Char Limit on Forms Messages solved

    Is it possible to fit more then the default 200 characters in to a custom error message? Any help would be appreciated, thanks
    Message was edited by:
    Yachera

    Creating a new database table or using text_io is completely unnecessary!
    You could create a separate form and open the form as a modal window to display the error of any length.
    But easiest might be to create a separate canvas with a control block item that can contain up to 32767 characters. Then just set the value of the item to whatever error message you need, then force the canvas to display by moving focus to that item with Go_Item.

Maybe you are looking for