on 07-08-2015 2:09 PM
Hi,
I hope you can help me, I'm doing some modifications to standard Work Manager 6.2 time registration, but still this seems to be a problem coming from the standard. Anyway it's an Agentry problem since it could happen for any app different than work manager.
First I create a time record, and then if I edit the transactions are not merged. Therefore the Update step calling the creation BAPI in SAP is called two times.
This is what I can see in the ATE
In Java CATSRecordEditStepHandler class, when the record edited is LOCAL then the add BAPI is used, and that's why I get 2 records created in the back end.
For the Transactions to merge the EDIT Transaction must have same or fewer properties than ADD. You cannot have additional properties in EDIT Transaction that are not there in ADD. Also in EDIT Transaction definition - please make sure you have selected Merge with any Transaction and Merge similar Transactions options.
thanks,
Chandra
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Marcal,
Try deleting the existing edit transaction, removing it from trash and recreating it with all the correct properties that match the add. Just take the defaults at first to see if you can get it to merge, then go back and fix the initial values, update rules and whatever else if the merge is successful.
If they still wont merge, Try the same with the Add transaction. I have had transactions that were somehow internally corrupt for whatever reason, and I could only correct the merging by recreating one or both.
Jason Latko - Senior Product Developer at SAP
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.