What you are seeing (with regards to however the Delivery - oregon Order - Address behaves successful the PO) is close - this code tract is utilized for the actual delivery itself, but its besides imaginable to participate any code here, (including the Vendors ain address, if its a Business Partner - this relation covers aggregate directions / possibilities arsenic to what is simply a Business Partner).
In the modular system, (and besides successful your scenario), the Delivery Address successful the PO tin beryllium manually changed to immoderate code entered by the user, erstwhile they person entree to the ME21N / ME22N transactions.
Access to create, update, oregon presumption is done successful ME21N, ME22N, and ME23N - Create PO, Change PO, and View PO respectively.
If a idiosyncratic has the enactment to update (via ME22N), they tin alteration the Delivery Address *as it's not validated if changing the code successful the supra scenario*.
If you privation to unit a cheque / bounds entries connected POs Delivery Address, this tin beryllium acceptable via customized coding User Exit BADI ME_PROCESS_PO_CUST,
(However, the code would request to beryllium acceptable successful the archetypal lawsuit erstwhile creating the PO successful ME21N, and redeeming - Your ABAPers whitethorn beryllium capable to marque Delivery Address mandatory astatine PO instauration successful ME21N to seizure it.)
Do enactment nevertheless limiting entree to this tract volition forestall you from shipping to your / the concern partners address - which tin hap successful real-world scenarios.
Hope this helps!