Page Comparison

/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 attachattachments

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.

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.

I_ADJUST_REFERENCE_DATA_BDS

When attachments are added in FSM and are meant to be stored in SAP using BDS, it was not possible to select valid ‘bds document type’ (see field ‘AR_OBJECT’ in table TOAOM). In FSM Connector it is selected based on file type and cloud object type:

Image Added

However, the BDS document type is a more ‘logical object’ than ‘technical’ factor and it is used to assign or segregate files by their business usage. With this badi definition method

(called in /PACG/ECM_CL_A_ATTACHMENTS->/PACG/ECM_IF_A_ATTACHMENTS~SET_REFERENCES), it is possible to modify the TOAOM record based on available properties. 

/PACG/ECM_CHECKLIST

/PACG/ECM_CHECKLIST_BEF_COMMIT

/PACG/ECM_IF_A_BADI_CHECKLIST2

DATA_BEFORE_COMMIT

Since this BAdI is used when saving the checklist instance object in the database, the implementation is called under various scenarios - for example generating a new checklist or closing an existing one. If, as part of this BAdI definition, you plan to implement a custom code that should run when closing the checklist instance, it is recommended to additionally check at the beginning of the BAdI implementation whether the instance is closed. This can be done using the CS_CLTDH-CLOSED EQ ABAP_TRUE code.

/PACG/ECM_CHECKLIST

/PACG/ECM_IF_A_BADI_CHECKLIST

DATA_BEFORE_INSERT

Checklist Data - called just before Insert into the database.

/PACG/ECM_UDF

/PACG/ECM_UDF_IN_UDOVALUE

/PACG/ECM_IF_S_BADI_UDFI_UDOV

SET_UDF

Set UDF. Implement custom logic for processing of inbound UDO values.

Image Added

If the BADI is not implemented UDO value is confirmed from FSM perspective and IDoc goes into status 53.