CHD Enhancements with Business Add-Ins

ProChangeDoc provides enhancements using Business Add-Ins (BAdi) at various points.
Only SAP users with appropriate authorizations and registered as system developers can integrate / activate BAdis. ABAP Workbench know-how is also required.

The BAdi must be implemented using the BAdi-builder (transaction SE19). The implementation name is freely selectable in the client's name space (acc. to the SAP documentation BC-CTS-NAM, namespace and naming conventions). The definition to be used is /PRONOVIA/CHD.

After the implementation, the code of the BAdis can be maintained with the object navigator (transaction SE80). All parameters and exceptions can be displayed using push button Signature:

Possible enhancements:

Method	Usage

Method	Usage
AFTER_CHANGE_STATUS	Called up on status change of the leading document if relevant for ProChangeDoc. At the time of the call, checks and actions are not yet initiated. Using the exception Ignore the enhancement is able to suppress it.
AFTER_CREATE_DOCUMENT	After creation and versioning a change document.
BEFORE_CREATE_DOCUMENT	Before creation of a new change document.
BEFORE_CREATE_DOCVS	Before creation of a new version of a change document.
BEFORE_PROCESS_ORIGINAL	Before displaying or editing an original document of the change document. Set IGNORE if the action shall be canceled without message.
DEFINE_LANG_TYPE	To define whether the document language presents the primary or secondary language.
DEFINE_STORAGE_CAT	Defines storage category for the original document.
GET_CHANGE_DOC_FILE	Gets original (or display application for change document). Possibilities: Disables original assignment (RAISE IGNORE). Run standard procedure (SDF template). Returns a file name, referring to the original to be filed. Returns an original in a buffer in the DMS DRAO format. Returns an original in a buffer in the SAP Script OTF Format. Using option c, d and e, the original being returned will be checked in by ProChangeDoc. Using option e, the OTF format will be converted in the PDF format before checking in. Attention: For scenarios using user interfaces different to SAP Gui (i.e. Webdynpro, UI5, ...), option c is not available and will return an error! Options a, b, d and e should work as intended.
LINK_MULTI_CHANGE_DOC	Before a multiple used change document is assigned to a PRM family.
POPUP_CREATE_CHANGE_DOC	Before query whether change document shall be created. Allows changing the text to be displayed or direct response setting.
PROCESS_ORIGINAL	Alternatively displaying or editing of an original.
SELECT_CHANGE_DOCUMENT	If a change document for leading document is created, this BAdi can influence the selection oft the possible change documents or the creation can be suppressed. If transfer table PTX_CHD is reduced to one set, no selection dialog will be displayed, otherwise the user must select the desired change document. No new lines can be inserted into the transfer table and field CHD-INDEX must not be changed.
STO_ADD_DATA	Preparing data for stocking the change document with SDF. For more information please refer to the ProChangeDoc, Customizing Manual.