Assignment Conversion

Hi All,
I have 2 different issues :
1. Do we have any API to convert assignments from legacy system to apps? I have all data from legacy system for assignment in .csv format.
2. After assignment conversion, I want to create an employee using API. When we create employee using API, it creates some default assignment and assigns to employee. I want to pass employee's assignment id in API itself. I am using HR_EMPLOYEE_API to create US employees but this api doesn't have any IN parameter for assignment. It has only OUT param.
Early reply appreciated.
Thanks
CAH

Hi
The sequence for employee and assignment conversion is:
- Create employee (which also creates default primary assignment)
- Update employee primary assignment with correct data, there are two apis with acces to different fields, each, updat_emp_assignment and update_emp_asg_criteria. Here You'll need the assginment_id returned from the create employee api, or query the assigments table for the one for the employee id related.
The assignment API allows for creation of secondary assignments only, the primary is created alongside employee. Also consider that legislation specific fields may be mapped to flexfields and sometimes is hard to map them, in this case try using the legislation specific apis (contains two letter code of legislation, i.e. create_gb_employee).
It will help You to review the HRMS Implementation Guide on the API usage, specially when dealing with effective dates and object version numbers.

Similar Messages

  • Assigning Conversion Exit to a Select-Option on Selection Screen.

    Hi,
    Is it possible to assign Conversion Exit (Like ALPHA) to a Select-Option on a Selection Screen. If so can anyone please tell me how is this achieved.
    Thanks & Regards,
    Goutham.
    P.S.: Points will be definitely awarded.

    Hi Anjaneyulu,
    Thanks for the Reply.
    But the problem comes here, when he enters both the ranges as well as single values, using the extension button provided for the select-option.
    One option i found was in the layout of selection screen, to the select-option i assigned the ALPHA as conversion exit. But it says that this will be over-written once program/screen is generated.
    Kindly let me know if any one has a solution for this.
    Thanks & Regards,
    Goutham.

  • Question about assignment conversion

    JLS Third Edition, chapter 5.2 on page 93 and Discussion (p. 94), states that:
    >
    It is a compile time error if a chain of conversions contains two parametrized types that are not in a subtype relation.
    And in the Discussion the following example is shown:
    Integer -> Comparable<Integer> -> Comparable -> Comparable<String>
    Which rocks, since Integer and String are not in a subtype relation. This is still possible because of support for legacy code (i.e. raw types).
    However I wrote the following dummy code:
    Integer a = 1;
              Comparable<Integer> ci = a;
              Comparable c = ci;
              Comparable<String> cs = c;expecting the compiler to 'trace' the chain of conversions and throw a compile-time error, but all it did was to produce an unchecked conversion warning when the value of the reference variable c is assigned to the reference variable cs.
    Isn't this in contrast with what stated by JLS?

    First, is there any particular reason why you used:
    Integer a = Integer.valueOf(1);while I used
    Integer a = 1; //boxing
    Just to get rid of boxing conversion as a possible issue--which it shouldn't be, but might as well keep it simple.
    Integer a = Integer.valueOf(1);
    Comparable<String> cs1 = a; // errorbecause we are assigning to a Comparable<String> an
    Integer value, and that's illegal, since String and
    Integer are not in a subtype relation (?)Something like that, yes. I'm not sure of the exact clause of the JLS that forbids it.
    >
    Comparable<Integer> ci = a; // ok
    Comparable<String> cs2 = ci; // errorbecause we are assigning to a Comparable<String> a
    Comparable<Integer>, and again, String and Integer
    are not in a subtype relation (?)Yep.
    Comparable<String> cs3 = c1; // warning
    Comparable<String> cs4 = c2; // warningit's what I believe is called 'heap pollution' I forget what that term means, and am too lazy to look it up, so I'll take your word for it.
    and I
    believe that on first use a ClassCastException will
    be thrown Sounds right. Run it and see for yourself.
    (although the compiler behaves correctly by
    flagging an unchecked warning, for compatibility with
    legacy systems, etc)Right.

  • Casting conversion in JLS3 draft

    Seems to be missing a post-boxing widening reference conversion:class C {
      Object o1 = (Comparable<Float>)1.0f; // ok
      Object o2 = (java.io.Serializable)false; // ok
    }Please ignore the Objects on the left-hand-sides - they are there only to give the casts somewhere to exist.
    Anyway, "5.5 Casting Conversion" says: "Casting contexts allow the use of ...a boxing conversion (�5.1.7)." but it there is no optional post-boxing widening reference conversion as there is under assignment conversion and method invocation conversion. Given that fact, it seems that those two statements shouldn't compile, or the jls should change.

    Actually, if you notice, I specifically mention boxing.
    You're right that Float->Object ends up as a nop in the bytecode, and it is allowed by the draft jls3.
    But float->Float->Object does not work out to a nop in the bytecode - a Float is actually allocated.
    In any case, what happens in the bytecode or internally in the compiler is sort of irrelevant, because according to the draft jls3, the two statements in the example should never make it past the compiler.
    You can't have a cast of the form (Type)arg if arg's compile-time type is not convertible to Type via "casting conversion"... and "float" is not casting-convertible to "Object" according to the rules of the draft jls3.
    Of course, it's probably just an omission in the spec itself and not cause for alarm.

  • Error while activating the InfoSource.

    Dear Friends:
    i have the following error when i try to activate an Infosource (0MATERIAL). The error refers to the error log which in SLG1 is as below. According to the error,I did not find any routines in the transfer rules for 0RT_CONFMAT. Please advise what is going wrong and the solution.
    Thanks in advance for all the help
    Raj
    ConvExits for assigned InfoObjects inconsistent: '   ' (KS:0RT_CONFMAT) - MATN1(TS:0RT_CONFMAT)
    Message no. RSAR367
    Diagnosis
    The InfoObject of the communication structure has the conversion exit "' . This InfoObject was assigned a field of the transfer structure as a transfer rule. However, conversion exit MATN1 belongs to this field. Problems and errors could occur later if the conversion exits differ.
    Procedure
    To prevent later problems, select a field with its correctly assigned conversion exit.
    When loading from an R/3 system, you can ignore this message if the transfer structure field has a conversion exit and the InfoObject assigned in the transfer rules has no conversion exit.

    Hi Raj,
    The system is talking about the conversion exit which can be seen in the infoobject definition in RSD1. This message is quite common and as the it mentions, "When loading from an R/3 system, you can ignore this message if the transfer structure field has a conversion exit and the InfoObject assigned in the transfer rules has no conversion exit."
    Are you also loading from R/3?

  • Unit of measurement in recipe management

    Hello All,
    In PLM7.02, NWBC , i have given the the values for the value assignment "Conversion Factor for Piece".  When i input data for formula while creating recipe, "an error Conversion from ML to KG is not possible for specification  xxxx" pops up
    I am not able to create Recipe.  Kindly help me to solve this issue.

    Hi,
    You can find the customizing following this path:
    Logistics(General) --> PLM --> PLM Web User Interface --> Recipe Development --> Recipe --> Status and Action Management --> Define Status Schema
    Select the status and navigate to the Attributes sublevel. New Entries and maintain these three fields:
    Status = <your status>
    Obj Type = 'PLM_RCP'
    Attribute = 'SKIP_FORMULA_CHECK'
    Regards,
    Gergo

  • Loading Flat file - error

    Hi Experts,
    I got a dump as an excel file from a user. I am supposed to load them in BI. When I try to open that file using notepad, I see junk data and when I see the preview of the file - I see Junk data as well.
    The excel file has about 20 columns and 5000 records.
    Which is the best way to load this data.

    Hi,
    Check your default date format (_Transaction SU03 -> Defaults -> Date_).
    Or
    First check the object 0DATE
    You will find Date Type: DATS (YYYYMMDD)
    So you need to load date in this format only...
    Option 1: Change the format to YYYYMMDD in your CSV File if possible. If this is not feasible in your case go for option 2.
    Option 2: In data source, under "fields" tab, you can assign the date field "External" format and assign conversion routine. I am not sure which routine (May be "RSDATu201D)
    Hope it helps you.
    Regards,
    Vishali.G

  • Is the Output shown in JLS 1.0 wrong ?

    This is the code example given in the section [Assignment Conversion|http://java.sun.com/docs/books/jls/first_edition/html/5.doc.html#170768]
    of Java Language Specification 1.0
    class Test {
         public static void main(String[] args) {
              short s = 12;                                   // narrow 12 to short
              float f = s;                                   // widen short to float
              System.out.println("f=" + f);
              char c = '\u0123';
              long l = c;                                   // widen char to long
              System.out.println("l=0x" + Long.toString(l,16));
              f = 1.23f;
              double d = f;                                   // widen float to double
              System.out.println("d=" + d);
    }On the web the Output shown is :
    f=12.0     
    i=0x123
    d=1.2300000190734863which is wrong since , i =0x123,"i" is never printed but the O/P should be :
    f=12.0
    l=0x123
    d=1.2300000190734863If this is a error ,has it been notified earlier ,if not what can be done ?
    Thank you for your consideration.
    Edited by: amtidumpti on May 6, 2009 6:36 PM

    amtidumpti wrote:
    jverd wrote:
    amtidumpti wrote:
    I was comparing all the versions specifications when i found this error.This has been displayed correctly in Version 2.0 and 3.0 respectively.Then if it's correct in 2.0 (which is obsolete) and 3.0 (which is current), who cares if it's wrong in 1.0 (which is WAY obsolete)?Ya,doesn't seem anyone cares,otherwise would have been fixed in Version 1.0 also.Not necessarily. It might not have been noticed. Or people may have cared, but not enough to delay the publishing. All software has bugs, including bugs that the creators know about and have chosen not to fix, and bugs that the creators are unaware of at the time of release. I suspect the same is true of publications.

  • Currency field to be displayed with commas and asterisks(formatting)

    I have a field REGUH-RWBTR in my sap script code. I need to have the currency displayed with commas. And also if the digits are less, then left pad it with asterisks for remaining spaces.
    For eg, If the Digit is 12345678912.23 (max value), it should print as 12345,678,912.23.
    And If the digit is 12345.89, it should print as ******12,345.89
    Please help me to solve this problem.Its urgent.
    Thanks,
    Sandeep.

    Hello,
    You can use the WRITE using EDIT MASK.
    USING { {NO EDIT MASK}|{EDIT MASK mask} }
    Effect
    This addition overrides a conversion routine defined through reference to the ABAP Dictionary. The addition NO EDIT MASK only switches off the execution of an assigned conversion routine. The addition EDIT MASK calls either another conversion routine or defines an edit mask. For mask, a data object of the same name is expected.
    In order to call an arbitrary conversion routine CONV, mask must contain two equals signs, followed directly by the name of the conversion routine: "==CONV". During output, the content of dobj is passed to the function module CONVERSION_EXIT_CONV_OUTPUT, converted there, and then the result is displayed. If the function module is not found, an exception that can be handled is triggered (as of Release 6.10). The statement DESCRIBE FIELD contains an addition in order to fill mask accordingly.
    If the output length is specified explicitly with len, the conversion routine is executed for the specified length; otherwise for the implicit output length. If * or ** is specified for the output length, the appropriate rules are used for the converted result.
    If the first two characters in mask are not equals signs, the content is interpreted as an edit mask in which some characters have a particular meaning. The WRITE statement does not then output the content of dobj directly, but the character string in mask as follows:
    If the first two characters in mask are "LL" or "RR ", these are not output, They control whether the edit mask is left-justified or right-justified. If the first two characters are other characters, the edit mask is left-justified.
    All "_" characters are replaced from the left (in the case of "LL") or from the right (in the case of "RR") with characters for character-type types or numbers for the types p or i from dobj. In the case of fields of type c, closing blanks are ignored. Data objects of type f or x are converted into type c before editing. Superfluous characters "_" in mask are replaced by blanks. Characters from dobj for which there are no characters "_" in mask are not displayed.
    If dobj is of type i or p, the first character from the left "V" in mask is replaced with "-" in the case of a negative number and by blank in the case of a positive number.
    All the other characters of the edit mask are displayed unchanged.
    If no output length is specified, the implicit output length of dobj is used. If len is specified for the output length, the value of len is used. If * is specified for the output length, exactly that length that is required for the list display is set. If, in Unicode systems, characters of the edit mask are replaced by characters that take up more than one column on the list, the output length is increased accordingly and the output is filled with blanks in the list buffer. If ** is specified for the output length, double the length of the edit mask mask is used.
    If other formatting options are specified concurrently for an edit mask, these are used first and then the special characters in the edit mask are replaced by the interim result. The date masks date_mask are an exception to this. If these are specified, the edit mask is ignored.
    Notes
    In Unicode systems, you must remember that a character "_"in the edit mask does not necessarily correspond to a column in the list display since the space required in the display depends on the character to be replaced.
    The minus sign for a negative number is not displayed if no edit character "V" is specified. The decimal separator of a packed number with decimal places must be specified at the required position in the edit mask.
    Example
    Edited output of time duration. In the first output, the function module CONVERSION_EXIT_DURA_OUTPUT is executed. This converts the duration specified in seconds into minutes. In the second output, the edit mask is output according to the above rules. However, the underscore characters "_" are replaced by the characters from time.
    DATA: dura TYPE i,
          time TYPE t VALUE '080000'.
    dura = sy-uzeit - time.
    time = dura.
    WRITE /(30) dura USING EDIT MASK '==SDURA'.
    WRITE /(30) time USING EDIT MASK
                           'RRThe duration is __:__:__'.
    Regards,

  • Casting vs. Widening

    I'm continuing the discussion from a deleted thread of whether or not statements such as the following...A a = new A();...constitute "implicit casting" or "assignment conversion". I'm in the latter camp, by virtue of the JLS, Chapter 5. Others have disagreed; at least I think they've disagreed.
    Thoughts?

    I don't consider that there's any cast going on there.
    There are several notions of casting one could use:
    1) A language level cast, as defined in the JLS. That is quite obviously not present, since, as you pointed out, that kind of cast explicitly uses the cast operator.
    2) A cast--in any sense--inserted into the final bytecode by the compiler. As your javap output in the other thread showed, this is also clearly not happening.
    3) A cast in a more general sense, corresponding to the compiler explicitly turning a B reference into an A reference internally at some intermediate step that's not manifested in the bytecode. This might be happening in some cases, I suppose. You'd have to look at compiler source code to know for sure. However, I think it would be trivial to show via reflection conterexample that it is not necessary to do this in the upcast sense that another poster was going on about in the thread that was, thank goodness, deleted.
    4) A general, cenceptual cast like #3, but without the compiler explicitly doing something. Just a view that "well, since this is an A reference, it must by definition be sort of kind of conceptually casting to A."
    Number 4 is pointless to argue, IMHO. It's like talking about how you can picture passing references by value as passing objects by reference. Sure, you can conceptualize it that way if it helps you to follow what's going on, but it has nothing to do with the JSL or any actual compiler or VM mechanism.
    Number 3 is pointless unless somebody really cares about what the compiler might do in some situations. Since we can show at least one case where it can't possibly do it, then it's not required that it do it, and I believe the original claim was that it was required to do it.
    So 1 and 2 don't occur, 3 is possible but not required, and 4 is irrelevant.
    Therefore, with regard to the claim that an upcast is necessary, I say, no, it's not.

  • Technical content objects  Getwa_not_assigned

    hi friends thanks for pervious replay
    I have assigned the points but i have one more request this regrading technical content objects. plz find the error below and try to help thank you . thnaks in advance .
    infoobjects for technical content is failed with the short dumps
    0TCTIOBJNM,0TCTQUERY,0TCTIFCUBE, plz find the attached file for error
    messages . i am unable to access the querys in the prodution sytem .
    Date Time Message
    2005.06.13 02:56:04 Job started
    2005.06.13 02:56:04 Step 001 started (program SBIE0001, variant
    &0000000000376, user ID BWADMIN)
    2005.06.13 02:56:04 DATASOURCE = 0TCTIFCUBE
    2005.06.13 02:56:04
    2005.06.13 02:56:04 * Current Values for Selected Profile
    Parameters *
    2005.06.13 02:56:04
    2005.06.13 02:56:04 * abap/heap_area_nondia......... 2000000000
    2005.06.13 02:56:04 * abap/heap_area_total.......... 2000000000
    2005.06.13 02:56:04 * abap/heaplimit................ 40000000
    2005.06.13 02:56:04 * zcsa/installed_languages...... E3
    2005.06.13 02:56:04 * zcsa/system_language.......... E
    2005.06.13 02:56:04 * ztta/max_memreq_MB............ 250
    2005.06.13 02:56:04 * ztta/roll_area................ 2000000
    2005.06.13 02:56:04 * ztta/roll_extension........... 2000000000
    2005.06.13 02:56:04
    2005.06.13 02:56:07 ABAP/4 processor: GETWA_NOT_ASSIGNED
    2005.06.13 02:56:07 Job cancelled

    HI MR.Andrzej
    thnaks for ur repaly i tried to do as u said but it gives me waring saying . see below . hope u can help . thanks in advance . i dont understand what to do .
    ConvExits for assigned InfoObjects inconsistent: '   ' (KS:0TCTSYSID) - ALPHA(TS:0TCTSYSID)
    Message no. RSAR367
    Diagnosis
    The InfoObject of the communication structure has the conversion exit "'. This InfoObject was assigned a field of the transfer structure as a transfer rule. However, conversion exit ALPHA belongs to this field. Problems and errors could occur later if the conversion exits differ.
    Procedure
    To prevent later problems, select a field with its correctly assigned conversion exit.
    When loading from an R/3 system, you can ignore this message if the transfer structure field has a conversion exit and the InfoObject assigned in the transfer rules has no conversion exit.

  • Declaring array of T[] - possible bug?

    See the following code:
    class A {}
    class B {}
    public class Test {
         public static void main(String[] args) {
              A a = null;
              foo(a);
         public static <T> void foo(T a) {
              T[] t = (T[]) new Object[10];
              Object[] o = t; // correct. Object[] is parent of T[].
              o[0] = new B(); // correct.  Insert B into object[].
              T val = t[0]; // Type error if T is not A!!
              System.out.println(t[0]);
    }T[] t = (T[]) new Object[10]; is the way of declaring an array of T that people in this forum recommend. However, I've found something
    quite strange. As you can see in the code above , T must be A. However, strangely enough, T val = t[0] succeeded. In this code, T is obviously A, and t[0] is also obviously B. However, JDK raises only one warning about T[] t = (T[]) new Object[10];, saying that "cast from Object[] to T[] is actually checking against erased type Object[]."
    Though the tutorial on generics says that codes are type-safe only when there's no warning, assigning instance of B into the variable whose type is A is quite weird.
    Is this a bug or my mistake?
    TIA.

    T[] t = (T[]) new Object[10];My compiler gives a warning here, which makes sense:     [javac] Compiling 236 source files to C:\cygwin\home\jeff\dev\scratch\classes
        [javac] C:\cygwin\home\jeff\dev\scratch\Test.java:14: warning: [unchecked] unchecked cast
        [javac] found   : java.lang.Object[]
        [javac] required: T[]
        [javac]         T[] t = (T[]) new Object[10];
        [javac]                       ^
        [javac] 1 warning
    Object[] o = t; // correct. Object[] is parent of
    of T[].No, it's not. Object is the parent of T.
    [url http://java.sun.com/docs/books/jls/second_edition/html/arrays.doc.html#40879]JLS 10.8 Class Objects for Arrays: The direct superclass of an array type is Object.
    The conversion works because [url http://java.sun.com/docs/books/jls/second_edition/html/conversions.doc.html#184206]JLS 5.2 Assignment Conversion says:
    Assignment of a value of compile-time reference type S (source) to a variable of compile-time reference type T (target) is checked as follows:
    If S is an array type SC[], that is, an array of components of type SC:
    If T is a class type, then T must be Object, or a compile-time error occurs.
    If T is an interface type, then a compile-time error occurs unless T is the type java.io.Serializable or the type Cloneable, the only interfaces implemented by arrays.
    If T is an array type TC[], that is, an array of components of type TC, then a compile-time error occurs unless one of the following is true:
    TC and SC are the same primitive type.
    TC and SC are both reference types and type SC is assignable to TC, as determined by a recursive application of these compile-time rules for assignability.
    I'm a little disappointed that this doesn't at least produce a warning, but I guess you can't expect generics to catch everything.
    o[0] = new B(); // correct. Insert B into
    to object[].This is why it kind of sucks that the previous statement works.
    T[] t = (T[]) new Object[10]; is the way of declaring
    an array of T that people in this forum recommend.They do? Seems odd, but then, I'm not really on 5.0 yet, so I don't know that much about generics.
    However, I've found something
    quite strange. As you can see in the code above , T
    must be A. However, strangely enough, T val = t[0]
    succeeded. In this code, T is obviously A, and t[0]
    is also obviously B. That may be a bug, or it may just be a limitation of how far generics can go in type checking. Poke through some generics tutorials and white papers, and if you don't find an explanation, submit it to the bug parade.
    Though the tutorial on generics says that codes are
    type-safe only when there's no warning, assigning
    instance of B into the variable whose type is A is
    quite weird.Yeah, but the code that got you there is kind of weird too. Generics provide type safety in a lot of common scenarios, but they can't cover every possibility.
    Is this a bug or my mistake?Not sure. My guess is this is just something that generics are not meant to cover, but it could be a bug.

  • ArrayStoreException by System.arraycopy

    Hi!
    I've made a simple code, which uses System.arraycopy, but it constantly throws ArrayStoreException, even though I can't see any reason for this.
    (I've even run through it and watched the variables at breakpoints.) It seems as if it cannot convert Integer to Integer, but why?
              My code is here:
              import java.lang.reflect.Array;
    public class ArrayHandler {
         public static void main(String[] args) {
              try {
                   Integer[] startArray=new Integer[]{new Integer(1)};
                   Integer[] endArray=new Integer[]{new Integer(2)};
                   Object[] result=new ArrayHandler().appendArray(startArray, endArray);
              }catch(Throwable exception){
                   exception.printStackTrace();
    http://java.sun.com/j2se/1.3/docs/api/java/lang/System.html#arraycopy%28java.lang.Object,%20int,%20java.lang.Object,%20int,%20int%29
    Otherwise, if any of the following is true, an ArrayStoreException is thrown and the destination is not modified:
          * The src argument refers to an object that is not an array.
          * The dst argument refers to an object that is not an array.
          * The src argument and dst argument refer to arrays whose component types are different primitive types.
          * The src argument refers to an array with a primitive component type and the dst argument refers to an array with a reference component type.
          * The src argument refers to an array with a reference component type and the dst argument refers to an array with a primitive component type.
        Otherwise, if any actual component of the source array
        from position srcOffset through srcOffset+length-1
        cannot be converted to the component type of the destination array by assignment conversion,
        an ArrayStoreException is thrown.
        In this case, let k be the smallest nonnegative integer less than length
        such that src[srcOffset+k] cannot be converted to the component type of the destination array;
        when the exception is thrown,
        source array components from positions srcOffset through srcOffset+k-1
        will already have been copied to destination array positions dstOffset through dstOffset+k-1
        and no other positions of the destination array will have been modified.
        (Because of the restrictions already itemized,
        this paragraph effectively applies only to the situation
        where both arrays have component types that are reference types.)
         public Object[] appendArray(Object[] startArray,Object[] endArray) {
              Object[] outputArray=startArray;   
              Class startArrayClass=startArray.getClass();
              System.out.println(startArrayClass);
              Class endArrayClass=startArray.getClass();
              System.out.println(endArrayClass);
              if(startArrayClass !=endArrayClass){
                   //throw new Exception("startArrayClass !=endArrayClass");
              }else{
                   try{
                        outputArray=(Object[])Array.newInstance(startArrayClass, startArray.length+endArray.length);   
                        System.arraycopy(startArray,0,outputArray,0,startArray.length);
                        System.arraycopy(endArray,0,outputArray,startArray.length,endArray.length);
                        return outputArray;
                   }catch(Throwable exception){
                        exception.printStackTrace();
              return outputArray;
         }//appendArray
    }Could anybody share his experience, please.
    My best regards.

    astlanda wrote:(I've even run through it and watched the variables at breakpoints.)Thank's for your time.
    I'm using Eclipse and I know a bit how to debug with it.
    Everything was as expected, but I can't see into a native method like
         * Copies an array from the specified source array, beginning at the
         * specified position, to the specified position of the destination array.
         * A subsequence of array components are copied from the source
         * array referenced by <code>src</code> to the destination array
         * referenced by <code>dest</code>. The number of components copied is
         * equal to the <code>length</code> argument. The components at
         * positions <code>srcPos</code> through
         * <code>srcPos+length-1</code> in the source array are copied into
         * positions <code>destPos</code> through
         * <code>destPos+length-1</code>, respectively, of the destination
         * array.
         * <p>
         * If the <code>src</code> and <code>dest</code> arguments refer to the
         * same array object, then the copying is performed as if the
         * components at positions <code>srcPos</code> through
         * <code>srcPos+length-1</code> were first copied to a temporary
         * array with <code>length</code> components and then the contents of
         * the temporary array were copied into positions
         * <code>destPos</code> through <code>destPos+length-1</code> of the
         * destination array.
         * <p>
         * If <code>dest</code> is <code>null</code>, then a
         * <code>NullPointerException</code> is thrown.
         * <p>
         * If <code>src</code> is <code>null</code>, then a
         * <code>NullPointerException</code> is thrown and the destination
         * array is not modified.
         * <p>
         * Otherwise, if any of the following is true, an
         * <code>ArrayStoreException</code> is thrown and the destination is
         * not modified:
         * <ul>
         * <li>The <code>src</code> argument refers to an object that is not an
         *     array.
         * <li>The <code>dest</code> argument refers to an object that is not an
         *     array.
         * <li>The <code>src</code> argument and <code>dest</code> argument refer
         *     to arrays whose component types are different primitive types.
         * <li>The <code>src</code> argument refers to an array with a primitive
         *    component type and the <code>dest</code> argument refers to an array
         *     with a reference component type.
         * <li>The <code>src</code> argument refers to an array with a reference
         *    component type and the <code>dest</code> argument refers to an array
         *     with a primitive component type.
         * </ul>
         * <p>
         * Otherwise, if any of the following is true, an
         * <code>IndexOutOfBoundsException</code> is
         * thrown and the destination is not modified:
         * <ul>
         * <li>The <code>srcPos</code> argument is negative.
         * <li>The <code>destPos</code> argument is negative.
         * <li>The <code>length</code> argument is negative.
         * <li><code>srcPos+length</code> is greater than
         *     <code>src.length</code>, the length of the source array.
         * <li><code>destPos+length</code> is greater than
         *     <code>dest.length</code>, the length of the destination array.
         * </ul>
         * <p>
         * Otherwise, if any actual component of the source array from
         * position <code>srcPos</code> through
         * <code>srcPos+length-1</code> cannot be converted to the component
         * type of the destination array by assignment conversion, an
         * <code>ArrayStoreException</code> is thrown. In this case, let
         * <b><i>k</i></b> be the smallest nonnegative integer less than
         * length such that <code>src[srcPos+</code><i>k</i><code>]</code>
         * cannot be converted to the component type of the destination
         * array; when the exception is thrown, source array components from
         * positions <code>srcPos</code> through
         * <code>srcPos+</code><i>k</i><code>-1</code>
         * will already have been copied to destination array positions
         * <code>destPos</code> through
         * <code>destPos+</code><i>k</I><code>-1</code> and no other
         * positions of the destination array will have been modified.
         * (Because of the restrictions already itemized, this
         * paragraph effectively applies only to the situation where both
         * arrays have component types that are reference types.)
         * @param      src      the source array.
         * @param      srcPos   starting position in the source array.
         * @param      dest     the destination array.
         * @param      destPos  starting position in the destination data.
         * @param      length   the number of array elements to be copied.
         * @exception  IndexOutOfBoundsException  if copying would cause
         *               access of data outside array bounds.
         * @exception  ArrayStoreException  if an element in the <code>src</code>
         *               array could not be stored into the <code>dest</code> array
         *               because of a type mismatch.
         * @exception  NullPointerException if either <code>src</code> or
         *               <code>dest</code> is <code>null</code>.
        public static native void arraycopy(Object src,  int  srcPos,
                                            Object dest, int destPos,
                                            int length);

  • Color profiles of placed Tiff files

    Hi,
    I'm using CS3 on Mac with 10.4.11. I want to know what happens to a color profile when placed in Illustrator.  My color settings in Illustrator are to "Preserve Embedded Profiles". My guess though is that as soon as I choice to embed the .tif, it is converted to the working space. I realize that when I save out of Illustrator as a EPS there is not a profile attached, but is the info still maintained in the document somehow or is it really converted to the working space? Thanks for any info you can give me!
    Trese

    The way Adobe explains it ( i.e., Designer's Guide to Transparency CS1 ), the "Placed" file is converted to the Illustrator EPS' profile upon mismatch.  I disagree with the previous statement that the EPS is "Profileless".  The Illustrator EPS has an embedded profile setup in the color settings, which is read by a RIP or printer driver.  The key to all of this is to have the "Placed" file's profile match the Illustrator EPS profile, otherwise, there will be a mismatch and the "Placed" file's profile will be converted, or, if yoiu choose, you can assign a profile when you Place the file in Illustrator ( when, if you set it, Illustrator asks you what to do with the profile upon mismatch ).  You will encounter fewer problems by issuing the same profile to both the tiff and the Illustrator EPS.  This is how I've set it up into an established workflow.  There will be deviates, of course, and I think there is enough ways to deal with mismatches when they occur.
    The Color Settings you implement in Illustrator are saved in the file and if you save as an EPS, the color information is saved as Postscript data, which, as I understand it, includes the profile you assigned or setup in the color settings.  To go a step further, the EPS information can then be read by Distiller and saved in a PDF which should also honor the same profile that came in the EPS.  All this comes back to the original tiff's profile, should it not match the Illustrator EPS, then a conversion will take place, but it will be based on the "preserved profile", not some arbitrary assigned conversion, Illustrator just converts based on the embedded profile.  This is how I understand it.  Others may want to chime in.

  • How to suppress certain fields in ALE Outbound INFREC IDOCs?

    Dear All
    Is it possible to suppress certain fields in Outbound ALE IDOCs (for example INFREC IDOCs) ?
    I am in need to send Info Records from one ECC system to another. The problem is, in the sending ECC system the INFREC IDOCs are created with the field E1EINAM-INFNR which carries the Info Record number. But the target ECC system might have a different Info Record already existing (for a different article) with the same Info Record Number. If the INFREC IDOCs are created without the INFNR field (i.e. if the field is blank) and then sent to the target system via ALE, it is successfully processed in the target system and a new Info Record is created with a different Info Record number. This is what is required. How can it be made possible?
    Thanks
    Vignesh Sankaranarayanan

    Use the transactions BD62, BD79 and BD55 to setup and assign conversion rules for your IDOC fields and set a constant '/' for the infnr field.
    Test if that is enough or you might need to take extra care for the name field of info record texts. I am not in a system currently, so I can't check whether long text name is based on info record number or only a mix of info record keyfields (without info record number itself).
    You should also have a look into my blog Stumbling blocks  in purchasing info record migration by LSMW IDOC method
    You will probably hit the one or other issue that I described too.

Maybe you are looking for