Key rule 2 (target field: M1_SUN): Initial update set

HI
friends,
while creating transformations for my character i gave initial
i am getting this message
Key rule 2 (target field: M1_SUN): Initial update set
initial means blank, so my output values should be blank for material, ple let me know.
regards
suneel.

Hi Suneel,
Normally you would want to load data for an InfoObject, so if you are not, the system just warns you. Like you also get warning when adding or removing nav attr from an InfoObject. Even if you are doing that for a reason, the system will prompt with warnings before activating the object.
Hope this helps...

Similar Messages

  • Key rule 32 (target field: ZCONFDATE): Initial update set

    hi all
    I am facing error while activating the transformations that initial update status set. due to this i m not be able to activate. This is occurring while migrating update rules.
    please suggest solutions.
    amit

    Hi
    If I got your Question properly, while activating the Transformations you are getting the warning messages as Initial values set to Blank. You should always check each Rule details individually (match the same with Transfer Rules/update Rules )(Hope you know that Transformation replaces Transfer&Update Rules and no more Update/Transfer rules seperately) and fill the Initial Values/Constants/Routines to be copy pasted.
    Recheck your entire mappings again and try to activate the same with relevant to Transfer Rules/update Rules, as all Routines may not be migrated to SAP BI 7.0.
    Hope it helps and clear

  • Derivation rule CO-PA, number of target fields

    Hi all,
    is there a possibility to have more than 6 target fields in a CO-PA derivation rule or is the only way to handle more fields with a separate rule based on the same source field?
    thanks for your help
    kind regards
    Adrian

    Dear Adrian,
    If you want to update more than 6 target field in one derivation step, as for I know is not possible but create a new derivation step with same source and additonal target fields, otherwise use exits.
    Regards
    Ravi

  • COPA derivation rule :more than 6 target fields

    Hi ,
    As per client's requirement I need to include 10 target fields in a COPA derivation rule . Now after entering 6 , I can see rest of the rows are greyed out ; it looks like SAP does not allow more than 6 as target .
    I tried to find out if such limitation is mentioned anywhere in SAP documentation but I could not find ; if anyone has any reference doc on that please let me know .
    Secondly , how to meet the requirement ? I can break the same into 2 separate derivation , say 6 target & related rule value in the first and in just next step another 4 targets & rule value ; the source remains same in both the step .
    OR any COPA user exit / enhancement will help me accommodate all 10 targets in a single step of derivation ? as far as my knowledge goes SAP provided COPA user exits (1 to 5) will not be helpful here .  
    Awaiting your help ...
    Regards
    Indranil Sen

    Dear Indranil Sen,
    As per my knowledge it is not possible to mention more than 6 source and target fields for a derivation rule.
    Because for that program, SAP defines that (1+5) fields for that screen.
    That is the reason you are getting the gray color after 6 entries
    Yes we can increase that limit but for that we need the access key.
    If you have access key authorization, you can increase the limit
    Reasons in detail:
    Screen filed what you are looking for is:
    DYNP5400-SRC-NAME-FIELDNAME
    There you can enter (1+5) entries only. enhancement for that field is difficult.
    So you can opt for  2nd option as you said.
    Let see  Mr. Waman Shirwaicar's  views on this issue.
    Regards,
    Pavan Kumar Arvapally

  • Posting rule to be specified in target field of mapping area/Mapping prefix in Search string use?

    Posting rule change using search string configuration
    Hello Friends - I have defined Search string and specified Posting rule in target field of mapping area and set up done on Search search use tab.
    When I imported the Statement, based on text found on statement, Posting rule specified in Search string is determined.
    I see Search strings already maintained in my system that Posting rule is maintained in Search string use tab - Mapping prefix.
    My doubt is that if Posting rule can be maintained in any of the below:
    Either at Posting rule to be specified in target field of mapping area or Mapping prefix in Search string use?
    Thanks

    Hello Kalim - Thanks. I have already configured Search string the way you suggested me last time and imported the statement during testing. It is working fine.
    Can you pls tell me in which scenario "mapping prefix field" should be maintained. Now, I will try to understand this from F1 help.
    For Search Strings already defined in our System long ago that Posting rule is not specified in Target field in mapping field, but maintained Mapping prefix.
    Thanks,
    GT

  • OIM Provisioning - Update target field just under condition

    Hello Experts,
    I need support to modify my SAP Target Provisioning.
    This is my scenario:
    - userA has a Resource SAP ECC.
    - I need that the 'Valid Through' field cannot be update if the SAP ECC resource is in status 'Disabled'.
    Is it possible?
    Thanks in Advance
    Best Regards,
    AT

    Hi Amit,
    thanks for your answer.
    At the moment the task that set our "Valid Through" atribute is linked to an adpter (type process task) that contanis just a "SET VARIABLE".
    We need to introduce an IF condition linked to the SAP Resource Status (Es. if the status is not 'Disabled'-> set variable).
    How can we do it using Design Console > Adapter Factory?
    If, into the Adapter, I add a new Util Task -> Oracle Identity Manager API, I can use an OIM Api method, but is not clear how to save the result value into an adapter variable..
    Could you give us some hints?
    Thanks in advance,
    Regards.
    AT

  • Rule 73 (target field: 0RPA_OID group: 01 Standard Group): Syntax erroer

    Hi All,
    two formulas (to uppercase) in the transfer rules maping
    after the migration of transfer rules,activation of transfermation i am getting this error for two fields.
    Rule 73 (target field: 0RPA_OID group: 01 Standard Group): Syntax error in formula.
    can anybody tell me how to resolve it.

    Hi ,
    This is a common problem which we get after migrating to BI7 .
    Do one thing copy the formula some where and delete the formula save it activate it . then create the formule once again .
    save it and then activate it . You will not get syntax error any more .
    Regards
    Santosh

  • Multi Row Update set fields disabled

    Hi
    I have a multi-row table and the functionality I need is when the user changes a value in a drop down list it either enables or disables certain fields.
    I have set the depends on value for my fields to the drop down list and checked the clear/refresh box. On each field I have tried
    #{bindings.dropdown.inputValue=='codeA'} and also
    #{row.dropdown=='codeA'}
    Each of these work as when the form is first loaded and the first row selected, the correct fields are disabled. However if I add a new row or change the dropdown, nothing happens.
    Any ideas?
    Thanks
    Rich

    Steven,
    I have tried this. It simply adds in row.MyList. Here is the field that in generates
    <af:selectOneChoice id="MinimumEntryFtTerritoryCode" value="#{row.FtTerritoryCode}"
    partialTriggers = "MinimumEntryMetCode" required="#{(bindings.MinimumEntryFtTerritoryCode.mandatory) and (!MinimumEntryCollectionModel.newRow)}" readOnly="#{!(data.StudentsPageDef.StudentsCustomerStatus.inputValue=='ACTIVE')}" disabled="#{row.MetCode!='PRE_ASS'}" valign="top">
    <af:selectItem value="" label="" rendered="#{!((bindings.MinimumEntryFtTerritoryCode.mandatory) and (!MinimumEntryCollectionModel.newRow))}" />
    <!-- DEBUG:BEGIN:DYNAMIC_DOMAIN_OPTIONS : default/item/dynamicDomainOptions.vm -->
    <af:forEach var="row2" items="#{bindings.FndTerritoriesVOLookup.rangeSet}" >
    <af:selectItem label="#{row2.TerritoryShortName}" value="#{row2.TerritoryCode}"/>
    </af:forEach>
    <!-- DEBUG:END:DYNAMIC_DOMAIN_OPTIONS : default/item/dynamicDomainOptions.vm-->
    </af:selectOneChoice>
    It all looks like it should work but when I change MetCode in the list, everything stays disabled.
    Cheers
    Rich

  • How to define keys in target DSO

    hi gurus!!
    ..can you please extrapolate on how to define key in target DSO and transformation logic.. (please refer to below discussion from for scenario from earlier posting)
    thanks in advance
    I have data from 3 datastore objects which I need to update one infocube. However, I need the data to come together to form one line per record. I've found that if I update the cube directly from the 3 DSO I get 3 lines rather than one, and if I update them all to a DSO and then to the cube, the same thing happens because I take the data from the change log.
    If I go via an InfoSet, I can not do a delta upload to the cube.
    I need this to run a min of once an hour.
    Any tips or advice would be greatfully recieved.
    Thanks
    Alice
    answer:::::
    You need to have an common key fields set in all of the three transformations.
    In your case it is probably:
    The key in target DSO is: k1..k3
    ODS1 - updates key k1, leaves k2, k3 empty
    ODS2 - updates key k2, leaves k1, k3 empty
    ODS3 - updates key k3, leaves k1, k2 empty.
    If you have it that way, you will end up with three records, instead of one.
    k1, empty, empty
    empty, k2, empty
    empty, empty, k3
    To resolve this, all of the source DSO must be able to determine and set a common key part in the transformations.
    Target ODS:
    Key K1,
    ODS1 - updates K1, key figures/characteristics from ODS1
    ODS2, updates K1, key figures/characteristics from ODS2
    ODS3, updates K1, key figures/characteristics from ODS3
    result:
    K1, key figures/characteristics from ODS1, then
    K1, key figures/characteristics from ODS2 - result is - previous record's key is overwritten, but the key figures/characteristics are mapped to the correct infoobjects (depending on how you set the transformation....)
    K1, key figures/characteristics from ODS3 - as for ODS2.
    The final result:
    K1, key figures/characteristics from ODS1, key figures/characteristics from ODS2, key figures/characteristics from ODS3.

    Hi,
           As thomas said you maintain your keys same as your source DSO's  in the target DSO.This is how the procedure goes when no specification for the keys are given.So maintain same keys which are in the sources.
    Regards
    Karthik

  • JPA: Attr ... mapped to a primary key column in the DB. Update not allowed.

    Let me just say that I posted a bug report for this here:
    https://glassfish.dev.java.net/issues/show_bug.cgi?id=3937
    But I'm also posting the info here, so that people who search on this forum may get some help:
    TopLink (both Essentials and 11g) has a problem with flushing entities
    containing a self-reference relationship. When flushing, the following exception
    occurs:
    Exception [TOPLINK-7251] (Oracle TopLink Essentials - 2.1 (Build b14-fcs
    (12/17/2007))): oracle.toplink.essentials.exceptions.ValidationException
    Exception Description: The attribute [id] of class [test.jpa.entities.Person] is
    mapped to a primary key column in the database. Updates are not allowed.
    No manual updates have been made to ANY primary key.
    What I'm doing is:
    1. I instantiate a new entity.
    2. I start a transaction
    3. I persist the new entity.
    4. I read an existing entity from the DB.
    5. I let the existing entity point to the new entity via the self-reference
    relationship.
    6. I flush the persistence context.
    7. I issue commit(), and the exception occurs. (I have provided the stack traces for various versions of TopLink below.)
    This is a clear bug.
    Here are some additional observations:
    1. Reproduced on the following versions of TopLink:
    1.1. Oracle TopLink Essentials - 2.0 (Build b58g-fcs (09/07/2007))
    1.2. Oracle TopLink Essentials - 2.1 (Build b14-fcs (12/17/2007))
    1.3. Oracle TopLink - 11g Technology Preview 3 (11.1.1.0.0) (Build 071214)
    2. Reproducible both on Java SE and Java EE. (I tested on Oracle Application Server)
    3. Reproducible with and without class weaving
    4. Reproducible regardless of whether the JPA annotations are on fields or on
    methods
    5. Reproducible regardless of whether "cascade={CascadeType.PERSIST}" is used or
    not.
    6. Reproducible regardless of the fetch type of the self-reference relationship
    (EAGER or LAZY).
    Also:
    1. Without flushing, the bug doesn't occur. That is, if I commit without
    flushing, it works.
    2. Without setting the self-reference relationship, the bug doesn't occur.
    This is an issue that appears when using BOTH self-reference relationship AND
    flushing.
    Best regards,
    Bisser
    The message was edited by bisser:
    Added info that the exception occurs "when I issue commit()" on step 7.

    I'm extremely surprised that you couldn't reproduce the error. It's reproduced each time when I run the Test Scenario that I described above.
    You could download a sample Eclipse project that reproduces the error from here: https://glassfish.dev.java.net/issues/show_bug.cgi?id=3937
    For the log below I used TopLink, version: Oracle TopLink Essentials - 2.0 (Build b58g-fcs (09/07/2007)).
    Could you, please, tell me what version you use and I will try the Test Case on it.
    Here's the FINEST log:
    [TopLink Finest]: 2008.01.09 07:35:58.094--ServerSession(1968077)--Thread(Thread[Main Thread,5,main])--property=toplink.weaving; value=false
    [TopLink Finest]: 2008.01.09 07:35:59.312--ServerSession(1968077)--Thread(Thread[Main Thread,5,main])--property=toplink.orm.throw.exceptions; default value=true
    [TopLink Finer]: 2008.01.09 07:35:59.312--ServerSession(1968077)--Thread(Thread[Main Thread,5,main])--Searching for default mapping file in file:/D:/dev/bull/jpa_pk_bug/bin/
    [TopLink Config]: 2008.01.09 07:35:59.547--ServerSession(1968077)--Thread(Thread[Main Thread,5,main])--The alias name for the entity class [class test.jpa.entities.Person] is being defaulted to: Person.
    [TopLink Config]: 2008.01.09 07:35:59.594--ServerSession(1968077)--Thread(Thread[Main Thread,5,main])--The column name for element [private java.lang.Long test.jpa.entities.Person.id] is being defaulted to: ID.
    [TopLink Config]: 2008.01.09 07:35:59.609--ServerSession(1968077)--Thread(Thread[Main Thread,5,main])--The column name for element [private java.lang.String test.jpa.entities.Person.name] is being defaulted to: NAME.
    [TopLink Config]: 2008.01.09 07:35:59.641--ServerSession(1968077)--Thread(Thread[Main Thread,5,main])--The target entity (reference) class for the many to one mapping element [test.jpa.entities.Person test.jpa.entities.Person.mgr] is being defaulted to: class test.jpa.entities.Person.
    [TopLink Config]: 2008.01.09 07:35:59.703--ServerSession(1968077)--Thread(Thread[Main Thread,5,main])--The primary key column name for the mapping element [test.jpa.entities.Person test.jpa.entities.Person.mgr] is being defaulted to: ID.
    [TopLink Finest]: 2008.01.09 07:35:59.703--ServerSession(1968077)--Thread(Thread[Main Thread,5,main])--end predeploying Persistence Unit Test; state Predeployed; factoryCount 0
    [TopLink Finer]: 2008.01.09 07:35:59.703--Thread(Thread[Main Thread,5,main])--cmp_init_transformer_is_null
    [TopLink Finest]: 2008.01.09 07:35:59.703--ServerSession(1968077)--Thread(Thread[Main Thread,5,main])--begin predeploying Persistence Unit Test; state Predeployed; factoryCount 0
    [TopLink Finest]: 2008.01.09 07:35:59.703--ServerSession(1968077)--Thread(Thread[Main Thread,5,main])--end predeploying Persistence Unit Test; state Predeployed; factoryCount 1
    [TopLink Finest]: 2008.01.09 07:35:59.719--ServerSession(1968077)--Thread(Thread[Main Thread,5,main])--begin deploying Persistence Unit Test; state Predeployed; factoryCount 1
    [TopLink Finest]: 2008.01.09 07:35:59.734--ServerSession(1968077)--Thread(Thread[Main Thread,5,main])--property=toplink.logging.level; value=FINEST; translated value=FINEST
    [TopLink Finest]: 2008.01.09 07:35:59.734--ServerSession(1968077)--Thread(Thread[Main Thread,5,main])--property=toplink.logging.level; value=FINEST; translated value=FINEST
    [TopLink Finest]: 2008.01.09 07:35:59.750--ServerSession(1968077)--Thread(Thread[Main Thread,5,main])--property=toplink.jdbc.user; value=rms
    [TopLink Finest]: 2008.01.09 07:35:59.750--ServerSession(1968077)--Thread(Thread[Main Thread,5,main])--property=toplink.jdbc.password; value=xxxxxx
    [TopLink Finest]: 2008.01.09 07:36:00.766--ServerSession(1968077)--Thread(Thread[Main Thread,5,main])--property=toplink.target-database; value=Oracle; translated value=oracle.toplink.essentials.platform.database.oracle.OraclePlatform
    [TopLink Finest]: 2008.01.09 07:36:00.781--ServerSession(1968077)--Thread(Thread[Main Thread,5,main])--property=toplink.jdbc.driver; value=oracle.jdbc.OracleDriver
    [TopLink Finest]: 2008.01.09 07:36:00.781--ServerSession(1968077)--Thread(Thread[Main Thread,5,main])--property=toplink.jdbc.url; value=jdbc:oracle:thin:@//10.20.6.126:1521/region2
    [TopLink Info]: 2008.01.09 07:36:00.797--ServerSession(1968077)--Thread(Thread[Main Thread,5,main])--TopLink, version: Oracle TopLink Essentials - 2.0 (Build b58g-fcs (09/07/2007))
    [TopLink Config]: 2008.01.09 07:36:00.812--ServerSession(1968077)--Connection(5182312)--Thread(Thread[Main Thread,5,main])--connecting(DatabaseLogin(
         platform=>OraclePlatform
         user name=> "rms"
         datasource URL=> "jdbc:oracle:thin:@//10.20.6.126:1521/region2"
    [TopLink Config]: 2008.01.09 07:36:01.797--ServerSession(1968077)--Connection(4252099)--Thread(Thread[Main Thread,5,main])--Connected: jdbc:oracle:thin:@//10.20.6.126:1521/region2
         User: RMS
         Database: Oracle  Version: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
    With the Partitioning, OLAP and Data Mining options
         Driver: Oracle JDBC driver  Version: 10.2.0.1.0
    [TopLink Config]: 2008.01.09 07:36:01.797--ServerSession(1968077)--Connection(5744890)--Thread(Thread[Main Thread,5,main])--connecting(DatabaseLogin(
         platform=>OraclePlatform
         user name=> "rms"
         datasource URL=> "jdbc:oracle:thin:@//10.20.6.126:1521/region2"
    [TopLink Config]: 2008.01.09 07:36:01.875--ServerSession(1968077)--Connection(5747801)--Thread(Thread[Main Thread,5,main])--Connected: jdbc:oracle:thin:@//10.20.6.126:1521/region2
         User: RMS
         Database: Oracle  Version: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
    With the Partitioning, OLAP and Data Mining options
         Driver: Oracle JDBC driver  Version: 10.2.0.1.0
    [TopLink Config]: 2008.01.09 07:36:01.891--ServerSession(1968077)--Connection(5760373)--Thread(Thread[Main Thread,5,main])--connecting(DatabaseLogin(
         platform=>OraclePlatform
         user name=> "rms"
         datasource URL=> "jdbc:oracle:thin:@//10.20.6.126:1521/region2"
    [TopLink Config]: 2008.01.09 07:36:01.969--ServerSession(1968077)--Connection(5763284)--Thread(Thread[Main Thread,5,main])--Connected: jdbc:oracle:thin:@//10.20.6.126:1521/region2
         User: RMS
         Database: Oracle  Version: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
    With the Partitioning, OLAP and Data Mining options
         Driver: Oracle JDBC driver  Version: 10.2.0.1.0
    [TopLink Config]: 2008.01.09 07:36:01.969--ServerSession(1968077)--Connection(5497095)--Thread(Thread[Main Thread,5,main])--connecting(DatabaseLogin(
         platform=>OraclePlatform
         user name=> "rms"
         datasource URL=> "jdbc:oracle:thin:@//10.20.6.126:1521/region2"
    [TopLink Config]: 2008.01.09 07:36:02.047--ServerSession(1968077)--Connection(5500006)--Thread(Thread[Main Thread,5,main])--Connected: jdbc:oracle:thin:@//10.20.6.126:1521/region2
         User: RMS
         Database: Oracle  Version: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
    With the Partitioning, OLAP and Data Mining options
         Driver: Oracle JDBC driver  Version: 10.2.0.1.0
    [TopLink Config]: 2008.01.09 07:36:02.047--ServerSession(1968077)--Connection(5512041)--Thread(Thread[Main Thread,5,main])--connecting(DatabaseLogin(
         platform=>OraclePlatform
         user name=> "rms"
         datasource URL=> "jdbc:oracle:thin:@//10.20.6.126:1521/region2"
    [TopLink Config]: 2008.01.09 07:36:02.125--ServerSession(1968077)--Connection(5514977)--Thread(Thread[Main Thread,5,main])--Connected: jdbc:oracle:thin:@//10.20.6.126:1521/region2
         User: RMS
         Database: Oracle  Version: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
    With the Partitioning, OLAP and Data Mining options
         Driver: Oracle JDBC driver  Version: 10.2.0.1.0
    [TopLink Config]: 2008.01.09 07:36:02.125--ServerSession(1968077)--Connection(5527528)--Thread(Thread[Main Thread,5,main])--connecting(DatabaseLogin(
         platform=>OraclePlatform
         user name=> "rms"
         datasource URL=> "jdbc:oracle:thin:@//10.20.6.126:1521/region2"
    [TopLink Config]: 2008.01.09 07:36:02.203--ServerSession(1968077)--Connection(5530440)--Thread(Thread[Main Thread,5,main])--Connected: jdbc:oracle:thin:@//10.20.6.126:1521/region2
         User: RMS
         Database: Oracle  Version: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
    With the Partitioning, OLAP and Data Mining options
         Driver: Oracle JDBC driver  Version: 10.2.0.1.0
    [TopLink Config]: 2008.01.09 07:36:02.203--ServerSession(1968077)--Connection(5542993)--Thread(Thread[Main Thread,5,main])--connecting(DatabaseLogin(
         platform=>OraclePlatform
         user name=> "rms"
         datasource URL=> "jdbc:oracle:thin:@//10.20.6.126:1521/region2"
    [TopLink Config]: 2008.01.09 07:36:02.281--ServerSession(1968077)--Connection(5545904)--Thread(Thread[Main Thread,5,main])--Connected: jdbc:oracle:thin:@//10.20.6.126:1521/region2
         User: RMS
         Database: Oracle  Version: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
    With the Partitioning, OLAP and Data Mining options
         Driver: Oracle JDBC driver  Version: 10.2.0.1.0
    [TopLink Finest]: 2008.01.09 07:36:02.312--ServerSession(1968077)--Thread(Thread[Main Thread,5,main])--sequencing connected, state is Preallocation_NoTransaction_State
    [TopLink Info]: 2008.01.09 07:36:02.484--ServerSession(1968077)--Thread(Thread[Main Thread,5,main])--file:/D:/dev/bull/jpa_pk_bug/bin/-Test login successful
    [TopLink Finest]: 2008.01.09 07:36:02.484--ServerSession(1968077)--Thread(Thread[Main Thread,5,main])--end deploying Persistence Unit Test; state Deployed; factoryCount 1
    [TopLink Finer]: 2008.01.09 07:36:02.516--ServerSession(1968077)--Thread(Thread[Main Thread,5,main])--client acquired
    [TopLink Finest]: 2008.01.09 07:36:02.531--UnitOfWork(5663897)--Thread(Thread[Main Thread,5,main])--Execute query DoesExistQuery()
    [TopLink Finest]: 2008.01.09 07:36:02.547--UnitOfWork(5663897)--Thread(Thread[Main Thread,5,main])--PERSIST operation called on: test.jpa.entities.Person@563c8c.
    [TopLink Finest]: 2008.01.09 07:36:02.562--ClientSession(5666151)--Thread(Thread[Main Thread,5,main])--Execute query ValueReadQuery()
    [TopLink Fine]: 2008.01.09 07:36:02.594--ServerSession(1968077)--Connection(5747801)--Thread(Thread[Main Thread,5,main])--SELECT PERSONS_ID_SEQ.NEXTVAL FROM DUAL
    [TopLink Finest]: 2008.01.09 07:36:03.297--ServerSession(1968077)--Thread(Thread[Main Thread,5,main])--sequencing preallocation for PERSONS_ID_SEQ: objects: 1 , first: 5, last: 5
    [TopLink Finest]: 2008.01.09 07:36:03.312--UnitOfWork(5663897)--Thread(Thread[Main Thread,5,main])--assign sequence to the object (5 -> test.jpa.entities.Person@563c8c)
    [TopLink Finest]: 2008.01.09 07:36:03.328--UnitOfWork(5663897)--Thread(Thread[Main Thread,5,main])--Execute query ReadObjectQuery(test.jpa.entities.Person)
    [TopLink Fine]: 2008.01.09 07:36:03.438--ServerSession(1968077)--Connection(4252099)--Thread(Thread[Main Thread,5,main])--SELECT ID, NAME, MGR_ID FROM Persons WHERE (ID = ?)
         bind => [1]
    [TopLink Finest]: 2008.01.09 07:36:03.531--UnitOfWork(5663897)--Thread(Thread[Main Thread,5,main])--Register the existing object test.jpa.entities.Person@3a4484
    [TopLink Finer]: 2008.01.09 07:36:03.625--ClientSession(5666151)--Connection(5763284)--Thread(Thread[Main Thread,5,main])--begin transaction
    [TopLink Finest]: 2008.01.09 07:36:03.625--UnitOfWork(5663897)--Thread(Thread[Main Thread,5,main])--Execute query UpdateObjectQuery(test.jpa.entities.Person@3a57fa)
    [TopLink Finest]: 2008.01.09 07:36:03.641--UnitOfWork(5663897)--Thread(Thread[Main Thread,5,main])--Execute query WriteObjectQuery(test.jpa.entities.Person@563c8c)
    [TopLink Fine]: 2008.01.09 07:36:03.656--ClientSession(5666151)--Connection(5763284)--Thread(Thread[Main Thread,5,main])--INSERT INTO Persons (ID, NAME, MGR_ID) VALUES (?, ?, ?)
         bind => [5, Boss, null]
    [TopLink Fine]: 2008.01.09 07:36:03.688--ClientSession(5666151)--Connection(5763284)--Thread(Thread[Main Thread,5,main])--UPDATE Persons SET MGR_ID = ? WHERE (ID = ?)
         bind => [5, 1]
    [TopLink Finer]: 2008.01.09 07:36:03.703--UnitOfWork(5663897)--Thread(Thread[Main Thread,5,main])--begin unit of work commit
    [TopLink Finest]: 2008.01.09 07:36:03.703--UnitOfWork(5663897)--Thread(Thread[Main Thread,5,main])--Execute query UpdateObjectQuery(test.jpa.entities.Person@563c8c)
    [TopLink Warning]: 2008.01.09 07:36:03.812--UnitOfWork(5663897)--Thread(Thread[Main Thread,5,main])--Local Exception Stack:
    Exception [TOPLINK-7251] (Oracle TopLink Essentials - 2.0 (Build b58g-fcs (09/07/2007))): oracle.toplink.essentials.exceptions.ValidationException
    Exception Description: The attribute [id] of class [test.jpa.entities.Person] is mapped to a primary key column in the database. Updates are not allowed.
         at oracle.toplink.essentials.exceptions.ValidationException.primaryKeyUpdateDisallowed(ValidationException.java:2222)
         at oracle.toplink.essentials.mappings.foundation.AbstractDirectMapping.writeFromObjectIntoRowWithChangeRecord(AbstractDirectMapping.java:750)
         at oracle.toplink.essentials.internal.descriptors.ObjectBuilder.buildRowForUpdateWithChangeSet(ObjectBuilder.java:948)
         at oracle.toplink.essentials.internal.queryframework.DatabaseQueryMechanism.updateObjectForWriteWithChangeSet(DatabaseQueryMechanism.java:1263)
         at oracle.toplink.essentials.queryframework.UpdateObjectQuery.executeCommitWithChangeSet(UpdateObjectQuery.java:91)
         at oracle.toplink.essentials.internal.queryframework.DatabaseQueryMechanism.executeWriteWithChangeSet(DatabaseQueryMechanism.java:390)
         at oracle.toplink.essentials.queryframework.WriteObjectQuery.executeDatabaseQuery(WriteObjectQuery.java:109)
         at oracle.toplink.essentials.queryframework.DatabaseQuery.execute(DatabaseQuery.java:628)
         at oracle.toplink.essentials.queryframework.DatabaseQuery.executeInUnitOfWork(DatabaseQuery.java:555)
         at oracle.toplink.essentials.queryframework.ObjectLevelModifyQuery.executeInUnitOfWorkObjectLevelModifyQuery(ObjectLevelModifyQuery.java:138)
         at oracle.toplink.essentials.queryframework.ObjectLevelModifyQuery.executeInUnitOfWork(ObjectLevelModifyQuery.java:110)
         at oracle.toplink.essentials.internal.sessions.UnitOfWorkImpl.internalExecuteQuery(UnitOfWorkImpl.java:2233)
         at oracle.toplink.essentials.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:952)
         at oracle.toplink.essentials.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:909)
         at oracle.toplink.essentials.internal.sessions.CommitManager.commitChangedObjectsForClassWithChangeSet(CommitManager.java:309)
         at oracle.toplink.essentials.internal.sessions.CommitManager.commitAllObjectsWithChangeSet(CommitManager.java:195)
         at oracle.toplink.essentials.internal.sessions.AbstractSession.writeAllObjectsWithChangeSet(AbstractSession.java:2657)
         at oracle.toplink.essentials.internal.sessions.UnitOfWorkImpl.commitToDatabase(UnitOfWorkImpl.java:1044)
         at oracle.toplink.essentials.internal.ejb.cmp3.base.RepeatableWriteUnitOfWork.commitToDatabase(RepeatableWriteUnitOfWork.java:403)
         at oracle.toplink.essentials.internal.sessions.UnitOfWorkImpl.commitToDatabaseWithChangeSet(UnitOfWorkImpl.java:1126)
         at oracle.toplink.essentials.internal.ejb.cmp3.base.RepeatableWriteUnitOfWork.commitRootUnitOfWork(RepeatableWriteUnitOfWork.java:107)
         at oracle.toplink.essentials.internal.sessions.UnitOfWorkImpl.commitAndResume(UnitOfWorkImpl.java:856)
         at oracle.toplink.essentials.internal.ejb.cmp3.transaction.base.EntityTransactionImpl.commit(EntityTransactionImpl.java:102)
         at oracle.toplink.essentials.internal.ejb.cmp3.transaction.EntityTransactionImpl.commit(EntityTransactionImpl.java:60)
         at test.jpa.TestPkBug.runTest(TestPkBug.java:53)
         at test.jpa.TestPkBug.main(TestPkBug.java:95)
    [TopLink Finer]: 2008.01.09 07:36:03.828--ClientSession(5666151)--Connection(5763284)--Thread(Thread[Main Thread,5,main])--rollback transaction
    [TopLink Finer]: 2008.01.09 07:36:03.844--UnitOfWork(5663897)--Thread(Thread[Main Thread,5,main])--release unit of work
    [TopLink Finer]: 2008.01.09 07:36:03.844--UnitOfWork(5663897)--Thread(Thread[Main Thread,5,main])--initialize identitymaps
    [TopLink Finer]: 2008.01.09 07:36:03.844--ClientSession(5666151)--Thread(Thread[Main Thread,5,main])--client released
    [TopLink Finest]: 2008.01.09 07:36:03.844--ServerSession(1968077)--Thread(Thread[Main Thread,5,main])--begin undeploying Persistence Unit Test; state Deployed; factoryCount 1
    [TopLink Finest]: 2008.01.09 07:36:03.844--ServerSession(1968077)--Thread(Thread[Main Thread,5,main])--sequencing disconnected
    [TopLink Config]: 2008.01.09 07:36:03.844--ServerSession(1968077)--Connection(4252099)--Thread(Thread[Main Thread,5,main])--disconnect
    [TopLink Finer]: 2008.01.09 07:36:03.859--ServerSession(1968077)--Thread(Thread[Main Thread,5,main])--initialize identitymaps
    [TopLink Info]: 2008.01.09 07:36:03.859--ServerSession(1968077)--Thread(Thread[Main Thread,5,main])--file:/D:/dev/bull/jpa_pk_bug/bin/-Test logout successful
    [TopLink Config]: 2008.01.09 07:36:03.859--ServerSession(1968077)--Connection(5747801)--Thread(Thread[Main Thread,5,main])--disconnect
    [TopLink Config]: 2008.01.09 07:36:03.859--ServerSession(1968077)--Connection(5182312)--Thread(Thread[Main Thread,5,main])--disconnect
    [TopLink Config]: 2008.01.09 07:36:03.859--ServerSession(1968077)--Connection(5500006)--Thread(Thread[Main Thread,5,main])--disconnect
    [TopLink Config]: 2008.01.09 07:36:03.875--ServerSession(1968077)--Connection(5514977)--Thread(Thread[Main Thread,5,main])--disconnect
    [TopLink Config]: 2008.01.09 07:36:03.875--ServerSession(1968077)--Connection(5530440)--Thread(Thread[Main Thread,5,main])--disconnect
    [TopLink Config]: 2008.01.09 07:36:03.875--ServerSession(1968077)--Connection(5545904)--Thread(Thread[Main Thread,5,main])--disconnect
    [TopLink Config]: 2008.01.09 07:36:03.891--ServerSession(1968077)--Connection(5763284)--Thread(Thread[Main Thread,5,main])--disconnect
    [TopLink Finest]: 2008.01.09 07:36:03.891--ServerSession(1968077)--Thread(Thread[Main Thread,5,main])--end undeploying Persistence Unit Test; state Undeployed; factoryCount 0
    Exception in thread "Main Thread" javax.persistence.RollbackException: Exception [TOPLINK-7251] (Oracle TopLink Essentials - 2.0 (Build b58g-fcs (09/07/2007))): oracle.toplink.essentials.exceptions.ValidationException
    Exception Description: The attribute [id] of class [test.jpa.entities.Person] is mapped to a primary key column in the database. Updates are not allowed.
         at oracle.toplink.essentials.internal.ejb.cmp3.transaction.base.EntityTransactionImpl.commit(EntityTransactionImpl.java:120)
         at oracle.toplink.essentials.internal.ejb.cmp3.transaction.EntityTransactionImpl.commit(EntityTransactionImpl.java:60)
         at test.jpa.TestPkBug.runTest(TestPkBug.java:53)
         at test.jpa.TestPkBug.main(TestPkBug.java:95)
    Caused by: Exception [TOPLINK-7251] (Oracle TopLink Essentials - 2.0 (Build b58g-fcs (09/07/2007))): oracle.toplink.essentials.exceptions.ValidationException
    Exception Description: The attribute [id] of class [test.jpa.entities.Person] is mapped to a primary key column in the database. Updates are not allowed.
         at oracle.toplink.essentials.exceptions.ValidationException.primaryKeyUpdateDisallowed(ValidationException.java:2222)
         at oracle.toplink.essentials.mappings.foundation.AbstractDirectMapping.writeFromObjectIntoRowWithChangeRecord(AbstractDirectMapping.java:750)
         at oracle.toplink.essentials.internal.descriptors.ObjectBuilder.buildRowForUpdateWithChangeSet(ObjectBuilder.java:948)
         at oracle.toplink.essentials.internal.queryframework.DatabaseQueryMechanism.updateObjectForWriteWithChangeSet(DatabaseQueryMechanism.java:1263)
         at oracle.toplink.essentials.queryframework.UpdateObjectQuery.executeCommitWithChangeSet(UpdateObjectQuery.java:91)
         at oracle.toplink.essentials.internal.queryframework.DatabaseQueryMechanism.executeWriteWithChangeSet(DatabaseQueryMechanism.java:390)
         at oracle.toplink.essentials.queryframework.WriteObjectQuery.executeDatabaseQuery(WriteObjectQuery.java:109)
         at oracle.toplink.essentials.queryframework.DatabaseQuery.execute(DatabaseQuery.java:628)
         at oracle.toplink.essentials.queryframework.DatabaseQuery.executeInUnitOfWork(DatabaseQuery.java:555)
         at oracle.toplink.essentials.queryframework.ObjectLevelModifyQuery.executeInUnitOfWorkObjectLevelModifyQuery(ObjectLevelModifyQuery.java:138)
         at oracle.toplink.essentials.queryframework.ObjectLevelModifyQuery.executeInUnitOfWork(ObjectLevelModifyQuery.java:110)
         at oracle.toplink.essentials.internal.sessions.UnitOfWorkImpl.internalExecuteQuery(UnitOfWorkImpl.java:2233)
         at oracle.toplink.essentials.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:952)
         at oracle.toplink.essentials.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:909)
         at oracle.toplink.essentials.internal.sessions.CommitManager.commitChangedObjectsForClassWithChangeSet(CommitManager.java:309)
         at oracle.toplink.essentials.internal.sessions.CommitManager.commitAllObjectsWithChangeSet(CommitManager.java:195)
         at oracle.toplink.essentials.internal.sessions.AbstractSession.writeAllObjectsWithChangeSet(AbstractSession.java:2657)
         at oracle.toplink.essentials.internal.sessions.UnitOfWorkImpl.commitToDatabase(UnitOfWorkImpl.java:1044)
         at oracle.toplink.essentials.internal.ejb.cmp3.base.RepeatableWriteUnitOfWork.commitToDatabase(RepeatableWriteUnitOfWork.java:403)
         at oracle.toplink.essentials.internal.sessions.UnitOfWorkImpl.commitToDatabaseWithChangeSet(UnitOfWorkImpl.java:1126)
         at oracle.toplink.essentials.internal.ejb.cmp3.base.RepeatableWriteUnitOfWork.commitRootUnitOfWork(RepeatableWriteUnitOfWork.java:107)
         at oracle.toplink.essentials.internal.sessions.UnitOfWorkImpl.commitAndResume(UnitOfWorkImpl.java:856)
         at oracle.toplink.essentials.internal.ejb.cmp3.transaction.base.EntityTransactionImpl.commit(EntityTransactionImpl.java:102)
         ... 3 moreEDIT: Are you using the EXACT Test Case as I have described it in the previous posts? It's important that you commit(), and not rollback(), the transaction after the flush.
    EDIT: Updated the log because I found out that I had made a small change to the original Test Case while I was trying to find a workaround. The current log is produced by the EXACT Test Case I described in my previous posts.
    Message was edited by:
    bisser

  • Issue loading ODS having single Data field when it is set to "No Updpate"

    Hi Gurus,
    I have a standard ODS object with 6 Keyfields & 1 Datafield.
    I am updating it from an Infosouce with help of Update Rules.
    In the Update rules:
    The 6 Keyfields are mapped from the Infosource fields which has relevant data.
    The one Data field needs to be set to "No Update" because there is no relevant field from the Infosource.
    Issue is surfacing with this Data field being set to "No Update"
    when I run the Infopackage even though there are relevant fields in Infosource for the 6 Keyfields none of them are getting updated.
    But when I set the Data field to "Overwrite" and for Update method give some constant or write some Routine and give the Result as 0, the rest 6 Keyfields are also getting updated from the Info source.
    My question is....
    If ODS is having only one Data field, is it mandatory that I have to update it with some value ?
    Can't I set it to "No Update" and load just the Key fields ?
    Thanks in advance,
    Venkat

    Thanks for the inputs.
    Even I had to agree if there is only one Data field in the ODS I have to set to some kind of Update...
    But.....I couldn't find it in writing (in  document) no where from the Web.
    Could anyone point out a document which confirms/explains this ?
    Thanks,

  • Error in BI at Transformation after migration from BW Rule (target :ZDTAPAK

    Hello Gurus,
    I have migrated datasource from BW to BI. The update rule from BW  against transformation in BI has routine.
    I see an error messgae in "Transformation Display"(screen). error msg is
      Rule (target :ZDTAPAKID, group:01 standard Group): syntax error in routine
      Rule (target :ZRECNM, group:01 standard Group): syntax error in routine
      Rule (target :ZRECORDID, group:01 standard Group): syntax error in routine
    Rule (target :ZREQUID, group:01 standard Group): syntax error in routine
    when I double click on field/ Rule Name : ZDTAPAKID,ZRECNM,ZRECORDID & ZREQUID on all the four   field / rule name and go to Rule Details  and against Rule Type : Routine , go to Display Rule  and land in Rule Details .
    There is see routine isa defined, when I  check the syntax of routine I get following error .
    E:Field "G_S_MINFO-DATAPAKID" is unknown. It is neither in one of the
    specified tables nor defined by a "DATA" statement. "DATA" statement
    Note: I get same error for all the 4 fields/rule name  when I try to check the syntax ZDTAPAKID,ZRECNM,ZRECORDID & ZREQUID
    can any one please guide me?
    Thank you
    Ashwaq

    hi check note Note 1052648 - Migrating transfer rules and update rules for BW7.x
    otherwise try to declare the fields in your generated coding
    for example
    TYPE-POOLS: RSSM.
    DATA :
    G_S_MINFO TYPE RSSM_S_MINFO,
    ZDTAPAKID TYPE RSDATAPID,
    ZRECNM TYPE rssm_s_minfo-requnr,
    ZREQUID TYPE RSREQUEST.
    Bye
    Boujema

  • Dynamically  filename is required in CC but not reuired in Target field

    HI,
    my requirement is to create filename dynamically(UDF) in Receiver communication channel but I dont want the name should be populated in the target field as target field is not provided by business.
    I received the below UDF from SDN
       String date = var1[0];
       String RFCL = var2[0] ;
       String FN = RFCL + date  ;
    AbstractTrace trace = container.getTrace();
    trace.addWarning("Test" + FN);
       String NameSpace = "http:/"+"/sap.com/xi/XI/Syatem/File";
    DynamicConfiguration conf =
    (DynamicConfiguration)container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
    DynamicConfigurationKey key = DynamicConfigurationKey.create(NameSpace, "FileName" );
    conf.put(key,FN);
    //trace.addWarning("Test" + var2);
    //trace.addWarning("Test" + RFCL);
    result.addValue(var2);
    Can any one suggest me how I can achieve my requirement
    Thanks

    Hi
    Use the code
    public String getFileName(Container container) throws StreamTransformationException{
    DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
    //For getting filename
    DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");
    // Retrieve the filename
    String FileName = conf.get(key);
    return FileName;}
    Map this to the root node. Do not forget to keep the Adapter Specific Message Attributes(ASMA) checked in the communication channels.
    Set Adapter Specific Message Attributes
    File Name.
    Regards
    Monika

  • SCCM 2012 Endpoint Protection initial update not downloaded

    Hi,
    I'm new to SCCM 2012. I recently started deploying the Endpoint  Protection to all of clients (Windos 7 and XP Pro). 
    I've noticed that some clients have not been updating their initial definitions after the Endpoint Protection Software is installed. 
    Since they are not updating their detonation the client remains unprotected with the status icon in red.
    The odd thing is that some of our computers do the initial update just fine while others are effected. 
    Also if I click update manually then the update goes through no issue, but with 100+ clients not updated its not something I want to do manually. 
    The clients are set to receive auto updates via a auto deployment rule. 
    Also the antimalware policy is set to do updates as well in this order: 
    Config Mgr
    WSUS
    Microsoft Malware Protection Center
    Microsoft Update
    Has anyone seen this before? 
    If I need to upload any specific logs just let me know. 
    Many Thanks

    Do you have Software update configured (and working) thru ConfigMgr or using a standalone WSUS?
    Kent Agerlund | My blogs: blog.coretech.dk/kea and
    SCUG.dk/ | Twitter:
    @Agerlund | Linkedin: Kent Agerlund |
    Mastering ConfigMgr 2012 The Fundamentals

  • COPA Derivation based with target field as non-copa field

    Hello experts,
    There is a requirement to derive the Characteristic maintained in Classification view(AUSP table) in Material master based on material number.The target field into which the characteristic value needs to be populated is not in COPA(it is a non-copa field).
    I tried to use table look up with AUSP table, but it is asking for values of certain key fields like
    ATZHL(Characteristic value counter)  MAFID(Indicator: Object/Class) and
    KLART(Class Type), which are not there in COPA.
    With the Enhancement in KEDR transaction, EXIT_SAPlKEDRCOPA_001 and Include ZXKKEU11, I  created an enhancement step by giving  the material as the key in the source fields.With that material number I can do a select on the AUSP table inside the include ZXKKEU11 and get the characteristic value. The problem i am facing is that the target field which stores the internal characteristic value is not there in COPA?And while creating a derivation rule, I can only select the COPA fields as target fields.
    It's urgent....any suggestions  please? Points will be rewarded for any useful answer.
    Thanks,
    Anky

    Hi,
    As far as I know the derivation functionality in COPA is meant for derivation of characteristic values to store them in a characteristic field.
    If you splitt up the derivation in two steps it might be possible to use the USERTEMP fields, to store the information needed and to pass it on to an other lookup step as a key-reference.
    Regards,
    Roy

Maybe you are looking for