Duplicate Bp on transport of org changes
Facing a issue on Duplicate ids generated after I transport any changes made in corresponding org unit. I am following below steps:
- making attribute change(custom attribute) for org unit A having a BP number 8XXXXXX123 in dev system
- locking ( entries in t77tr table
- making a TR with change record in RHMOV30 program
- unlocking all above entries from t77tr table
- transporting them in sequence of lock , changes/ unlock to target system
- after that when I check the target system, BP number of Org Unit A is changes from BP number 8XXXXX123 to 8XXXXXXX222.
can you please let me know, is there any way I can transport attribute change without generating a new BP number. it makes no sense of having multiple BP numbers for single org unit.
Appreciate your expert advise. not to mention that i will assign points as well:)