Nested LPN vs. OBLPN

Summary:

Nested LPN vs. OBLPN

Content (required):

I understand WMS does not support Nested LPN but also know user can create Outbound LPN based on current LPN in the storage locations. My current use case is that, user breaks "Master LPN" into "Child LPNs" during shipping and assign different Child LPNs into different Outbound Shipments. At times, user may need to refer back to the master LPN number from child LPN.

It seems to me that WMS can support this use case. Is that correct? If yes, is there any pitfall that I need to be aware of?

Version (include the version you are using, if applicable):