This is tricky as it's different than updating other records (like WORKORDER) where you can specify an add/change action and it won't try and drop children records that are not provided. In the case of PO because you're creating a revision, you really need to have all the lines but can't as it's in a completely separate message. Because it's in a separate message, I'm honestly not sure the best way to handle that as you can't write a user exit or anything to access other messages.
Assuming SAP can delete lines, you can't just assume everything is an addition. If the SAP side can never delete lines, and you will never a line number conflict on the PO lines (IE while they're sending them in separate transactions, PR1-Line1 is always line 1, PR1-Line2 is always line 2, PR2-Line1 is always line 3, etc.), and your integration is sequential in (continuous queue would be problematic as it processes multiple messages at once, meaning the lines you need may not have been processed yet), you could potentially create an automation script on your enterprise service to add in the lines referenced previously on the revision. But that's a lot of conditions that I don't expect will be true.
Without that, I honestly don't know best course of action. You may need some sort of staging middle ground where you can take and combine the messages into a single message into Maximo.
------------------------------
Steven Shull
Projetech
------------------------------