Hi Stephen,
Thanks a lot for chiming in!
I do think it's always a better option to add your logic in a BAdI too... but sometimes it just takes too much time to find the right spot for something that will take 2 minutes to implement in UI if that covers 100% of business needs (I know, I'm lazy). And I think this is one of those cases: because as far as I understand, those 3 rows need to be inserted automatically once the document is created... so I'm quite sure AXT BAdIs won't help because they will be called too late in the process (remember that Anne wants to prevent lines from being inserted by end users).
IMHO if this kind of logic is to be executed in background too, we would need to put some coding in a place like "AFTER_CREATE" of the parent object... And I guess CRMV_EVENT would be a good choice if "document" in the initial thread meant "business transaction". But I'm not so sure about that.
Anne, may you please confirm which type of CRM object you are enhancing? Because Stephen is definitely right, maybe you could put your logic somewhere else, that would make it work in every situation (not only when users are creating an object from WebUI).
Cheers,
Nicolas.