2016 Jun 02 7:23 AM
Hi team,
I cannot use transaction bobx nor eclipse for editing my BO anymore. Both work in read-only mode only and there is a message /bobf/conf_ui 384 that says that the BO has been created in /bobf/conf_ui which is not the case. Apparently I did some change using the old transaction at some point of time. Is there a way how to "unlock" my BO and make it editable from BOBX?
Kind Regards,
Igor.
2016 Jun 02 8:07 AM
Hello Igor,
do you use transaction code BOBF with your BO? If your answer is yes, the customer flag CUSTOMER_BO in the table /BOBF/OBM_BO is unset and from this point it is not possible to edit the BO with TAC BOBX. Set this flag and now it should be possible to edit your BO.
Let us know your results.
Cheers
Stefan
Hi team,
I cannot use transaction bobx nor eclipse for editing my BO anymore. Both work in read-only mode only and there is a message /bobf/conf_ui 384 that says that the BO has been created in /bobf/conf_ui which is not the case. Apparently I did some change using the old transaction at some point of time. Is there a way how to "unlock" my BO and make it editable from BOBX?
Kind Regards,
Igor.
2016 Jun 02 8:07 AM
Hello Igor,
do you use transaction code BOBF with your BO? If your answer is yes, the customer flag CUSTOMER_BO in the table /BOBF/OBM_BO is unset and from this point it is not possible to edit the BO with TAC BOBX. Set this flag and now it should be possible to edit your BO.
Let us know your results.
Cheers
Stefan
2016 Jun 02 8:19 AM
Hi Stefan,
Yes, it works. Thank you a lot.
Could you please guide me to any additional information about this flag? What is it's implication and what consequences might I expect after this change?
Kind Regards,
Igor.
2016 Jun 02 8:32 AM
Hello Igor,
thanks for your reply.
As far as I know is there a difference in the meta model between BOs from TAC BOBX and BOBF. BOBF can read BOBX BOs, but not sure is the other way round.
Cheers
Stefan
2016 Jun 02 11:30 AM
Hi Stefan, hi Igor,
no, there is no difference in the meta model. The difference is that BOBX is restricted to features which are officially released. As soon as you use BOBF to edit your BO, you risk using features which are not released to customers. When switching back to BOBX (by manually setting the customer flag) you do not remove such features from your BO. They are still used, but not visible in Tx BOBX.
By switching to BOBF you are leaving the officially supported track. Switching back to BOBX is safe only if you did not really use any BOBF-spefic features. However, there is no way to check for a given BO if it uses only supported features. So, better do not use BOBF if at all possible.
Kind Regards,
Ivo
2016 Jun 02 12:08 PM
2016 Jun 02 8:13 AM
Hello Igor,
In OSS note 2270184 you'll find a program that you can use to reset the customer flag. After that you'll be able to edit your BO using BOBX or Eclipse.
Best regards
Liesbeth
| User | Count |
|---|---|
| 3 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |