Object connection transformation based on the Document Class

​@HoiIndikW the object connection transformation rules are define between 2 LUs (logical units) and It doesnt depend on the document class.

Also if you setup a rule between the Purchase order and manual supplier invoice, it will transfer all documents. maybe you might need to investigate the possibility to customize this. In core application this is not supported.

Else you need 2 rules from Purchase order confirmation and the supplier invoice to manual supplier invoice page, instead from purchase order. But you need to evaluate and decide whether it suits your business flow.

Pls refer documentation for more details.

…/Documentation/en//DefineSystemBasics/AboutObjectConnectionTrans.htm

...in addition to the answer from diwelk. To pass on only certain documents, you can also use an event action configuration. In this case, a further object link can be executed directly in the document revision under the desired condition. This increases flexibility.

Thanks ​@diwelk and ​@MikeCH for your inputs. 

​@MikeCH We also thought of creating a custom event/BPA to block transfers of Purchase order confirmation related document revisions from purchase order page to supplier invoice page. Could you please describe more about the event action configuration solution you have suggested? 

​@diwelk Another thing to add to the documentation perhaps?

should’nt this be added for an evolution of the object connection transformation rules as this is a legitimate business requirement,  that shouldnt need a customization. 

Feel free to add an idea about this in the Ideas section here in IFS Community so that it can be taken into consideration and also be prioritized.

Also, just because it's a valid business requirement, doesn't mean it's what we should focus on. We have more requirements that we and our customers want to have than what we have resources to develop. Also, sometimes a requirement fits badly in the original design, so it can be costly to implement.