Hi Julia,
It is the mysterious world of OMW.
It is a great tool, while you handle only REAL Object Librarian type of objects. Unfortunately, JDE tried to handle other kind of "animals" the same way. For example:
1.) Batch and Interactive versions are a "bit" other kind of animals. E.g. "normal" users do not create and modify Object Librarian objects, but can create and modify versions - so it requires different handling
2.) UDCs, Menus are also another kind of animals, like User Overrides too, further Workflows too.
3.) At last, but not least Data Dictionary Items are totally other kind of animals.
Let see your scenario:
1.) If you signed on PY, then BV and OMW try to Check-In your Batch Version (BV) to PY (independently of the project status)
2.) If the template UBE still do not exist on PY, then BV and OMW can not Check-In the version.
What can I suggest:
1.) If it is possible, sign on DV and test there (NOTE: while your UBE had never been checked-in DV, the BV check-in will fail too).
2.) If your development rules allow, then Check-In the UBE, promote it to PY (status 26) and test on PY. If it is required, step back to 21 programing status to modify the UBE, Check-In again and promote again to PY.
Maybe a good practice in your scenario to handle BV and UBE in separate project.
If you are familiar in OMW configuration, then maybe you can try to set up special configurations, which fits to your needs.
Regards,
Zoltán