Attachments
Enhancement spot | BAdI definition | Interface | Method | Description |
|---|---|---|---|---|
/PACG/ECM_ATTACHMENT | NEW ATTACHMENT HANDLING /PACG/ECM_PROCES_ATTCHM | /PACG/ECM_IF_A_BADI_ATTCHM | I_CHANGE_MAIN_SEGMENT | Inbound - change attachment main segment of IDOC |
I_DETERMINE_BOR_TYPE | Determine BOR Type and Object ID of inbound attachments | |||
O_CHANGE_ATT_LIST | Outbound - change attachment list | |||
I_USER_PROCESSING | Inbound - user processing of inbound attachments | |||
I_ADDITIONAL_REFERENCES | Inbound - additional references to attachment | |||
O_AFTER_SINGLE_SEND | Outbound - after sending single attachment | |||
O_AFTER_SEND | Outbound - after sending all attachments | |||
I_AFTER_RECEIVE | Inbound - after receiving all attachments | |||
I_ADD_REFERENCE_TO_OBJECTS | Inbound - set list of objects for additional references | |||
I_GET_EQUI_FOR_REFERENCE | During processing of an inbound activity attachment, an additional attachment reference can be created - to equipment. See field ‘Link FSM Attachments from Activity to Equipment’ in transaction: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37135497/PACG+ECM+ACTIVE+General+Properties+of+E4C+Activity#Link-FSM-Attachments-from-Activity-to-Equipment Use this BAdI to determine which equipment should the attachment reference be created for. This can be done based on attachment file name, file type or other header data found in an idoc. The following example implementation is provided: retrieve a serial number from the first (out of 3 or more) segment of the attachment’s file name and use it to find equipment in table EQUI. |