hah, yes, copying the proc options template separately from the ube, and then going into rda to replace the original template by the copied template will of course not work since you'll lose the link between your report and the PO-variables. I'm pretty sure that's what happened, since i just did a small test, and upon saving & exiting the UBE when the ER are validated (mind you: NOT when running the UBE as the poster led us to believe), the "data structure errors" are thrown (See below).
lovvyrules: delete your copied objects, and re-create them the way daniel described above, and you should have no errors. one more note: although the tool allows you to "share" the same proc option template by two ube's, my advice is to avoid this and always copy the proc option template to a new object when copying a ube. since future changes to one ube might require changes to its proc option template. changes that might not apply to the other ube.
*************************
EVENT RULE VALIDATION LOG
UBE - R5642565 - Print Invoices
Created : Fri May 27 16:00:07 2011
*************************
/* CER ERROR #3007 : Invalid datastructure or member */
Function Name: S1_0_11
Function Description: ER for R5642565_+_S1_0_11
Section: S1 - Phase 1 - Build Work File
Event: 11 - Initialize Section
Seq #: 121
Line #: 118
Line Text: R42565PlugPlayNER
*************************
/* CER ERROR #3003 : Unable to assign to data structure */
Function Name: S1_0_11
Function Description: ER for R5642565_+_S1_0_11
Section: S1 - Phase 1 - Build Work File
Event: 11 - Initialize Section
Seq #: 121
Line #: 118
Line Text: R42565PlugPlayNER
*************************
/* CER ERROR #3007 : Invalid datastructure or member */
Function Name: S1_0_11
Function Description: ER for R5642565_+_S1_0_11
Section: S1 - Phase 1 - Build Work File
Event: 11 - Initialize Section
Seq #: 133
Line #: 130
Line Text: If PO szAsIfCurrencyCode is not equal to <Blank> And PO szAsIfCurrencyCode is not equal to <Null>
*************************
(etc.)