on 03-13-2018 1:46 PM
Hi,
Check consistency of generated tables in FMDERIVE (via ABADRCHECK program). Sometimes, the tables are not generated with sufficient index information which might cause problems during transport. Also, check OSS note for some additional information:
1231815 - Predefined FMDERIVE tables are renamed during transport/CC
Regards,
Eli
P.S. In all my projects, I was reluctant to transport FMDERIVE tables/strategies. I always applied the approach of creating the rules directly in the target system with optional replica in development instance.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for confirming Eli! I actually was able to find the underlying cause for this. We will be opening an OSS message for this one as I am not able to regenerate the table.
I created step 15 above but the transport error is pertaining to a missing nametab for step 9.
For the transport procedure, in case of new steps, is my understanding correct - you also maintain the step (rule) directly? or just the step (rule) values?
No, also the step itself, not only the values.
You can try and regenerate step 9, i.e. re-defining the rule, putting aside the values and then reimporting them.
This is not unusual what happens to you. I don't think OSS would provide other solution, but in case they do, please, update your thread for the benefit of the others 🙂
Hi,
I recommend to follow the instructions on this:
1730981 - Error ABADR013 or Runtime Error in SAPMABADR: Exception condition "SYSTEM_ERROR" raised
Best Regards,
Vanessa.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
16 | |
3 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.