List of Enhancements

The following table lists all available ProMassOperation enhancements. For customer exits, a function module as template is available in the function library /PRONOVIA/MSCEXA, including decryption of parameters.

Enhancement Type Template "Customer Exit"	Usage

Enhancement Type Template "Customer Exit"	Usage
Checking start object Customer Exit /PRONOVIA/MSC_X_CHECK_STARTOBJ	Customer exit checks whether the start object is valid. By default ProMassOperation will indicate a warning when start object is not the highest object (e.g. the object has also other usages). See also ProMassOperation, User Manual about default checks which will run before this customer exit.
Definition status change Customer Exit /PRONOVIA/MSC_X_STATUS_DEF	Customer exit allows to change table of status changes which has been defined by customizing of ProMassOperation, SAP-DMS and eventually. ProNovia SAP PLM ProcessManager PRM. Depending on the mass operation the table of material status or document status is filled.
Checking validity one object Customer Exit /PRONOVIA/MSC_X_CHECK_OBJ	Customer exit will be called for each object after it has been checked whether it can be used.
Reading bill of material BADI	Can be used for alternative reading of bill of material instead of ProMassOperation default BOM explosion (all levels). If the BOM is read by the BADI, this must be signaled to ProMassOperation by setting the export parameter EV_READING_DONE to ABAP_TRUE.
Reading document structure BADI	Can be used for alternative reading of document structure instead of ProMassOperation default BOM explosion (all levels). If the BOM is read by the BADI, this must be signaled to ProMassOperation by setting the export parameter EV_READING_DONE to ABAP_TRUE.
Before user dialog Customer Exit /PRONOVIA/MSC_X_BEFORE_DIALOG	Customer exit will be called before each main dialog. Unlimited additional objects can be added. The hierarchy must be regarded. Therefore it is required to maintain field NODE_ID (node of key) and PARENT (superior node) of table lines in PTX_OBJECTS correctly.
Definition of own columns Customer Exit /PRONOVIA/MSC_X_DEF_COL	Enables to define extra columns and adjustment of ProMassOperation default columns in the display tree. See also next paragraph.
Filling own data for display Customer Exit /PRONOVIA/MSC_X_DEF_ITEM	In case own columns have been defined with exit „Definition of own columns", the cell content must be filled with this exit. All possibilities of a SAP column tree can be used (CL_GUI_COLUMN_TREE), but so far no options are provided to react to input fields or check boxes.It is also possible to change cell contents filled by ProMassOperation (some columns are protected and will not be handed to the customer exit).
On action on object (double click) Customer Exit /PRONOVIA/MSC_X_OBJECT_ACTION	With this Customer Exit own actions can be executed on double click or single click on object keys. This is required for self-inserted objects. By default ProMassOperation supports only document and material objects. If this action is performed by the customer exit, it must be indicated with exception IGNORE.
Click on customer specific checkbox Customer Exit /PRONOVIA/MSC_X_CUST_CHECKBOX	This Customer exit is called, when a customer specific checkbox is clicked (defined in "Filling own data for display").
Before displaying context menu Customer Exit /PRONOVIA/MSC_X_CTX_BUILD	Customer exit with which additional functions can be added to the context menu.
Before executing context menu Customer Exit „/PRONOVIA/MSC_X_CTX_EXEC	Customer exit which enables processing of own commands from the context menu (see paragraph before).
On change on actions flags Customer Exit PRONOVIA/MSC_X_CHKBOX_CHNG	Customer exit will be called when an object has been selected or deselected for an action, or if one of the three check boxes for a clone operation has been selected.
Own check of replacement material / document Customer Exit /PRONOVIA/MSC_X_OBJ_REPL_CHK	Customer exit will allow execution of own checks and actions, if objects (material/document) have been replaced in the clone operation or a position has been added. With appropriate signalization ProMassOperation checks can be suppressed completely.
Before start of mass operation Customer Exit /PRONOVIA/MSC_X_BEFORE_ACTION	Customer exit will be called before actual execution of mass operation and allows further changes in the object selection.
Before creating a material master Customer Exit /PRONOVIA/MSC_X_CREATE_MAT	Customer exit will be called just before creating a new material master record or material master view (cloning).
Before creating BOM Customer Exit /PRONOVIA/MSC_X_CREATE_BOM	Customer exit will be called directly before creating BOM (cloning).
Before updating a BOM Customer Exit /PRONOVIA/MSC_X_UPDATE_BOM	Customer exit will be called directly before changing BOM. (post processing after cloning).
Selection of routings to copy /PRONOVIA/MSC_X_SEL_ROUTINGS	Customer exit to select which routings shall be copied or to disable copying completely.
Before creating a single routing Customer Exit /PRONOVIA/MSC_X_CREATE_ROUTING	Customer exit will be called just before a routing is created (cloning).
Before creating a document info record Customer Exit /PRONOVIA/MSC_X_CREATE_DOC	Customer exit will be called directly before creating a document info record (cloning).
Before creating a document structure Customer Exit /PRONOVIA/MSC_X_CREATE_DST	Customer exit will be called directly before creating a document structure (cloning).
Before updating a document structure Customer Exit /PRONOVIA/MSC_X_UPDATE_DST	Customer exit will be called directly before changing a document structure (cloning).
After cloning an object Customer Exit /PRONOVIA/MSC_X_AFTER_CLONE	Customer exit will be called directly after cloning an object, but before the object has been checked in completely cloned into the protocol.
After completing all clone operations Customer Exit /PRONOVIA/MSC_X_CLONE_JOB_END	Customer exit will be last action in a clone job after all objects have been cloned or the cloning has been aborted after an error.
After completing all status and client operations Customer Exit /PRONOVIA/MSC_X_JOB_END	Customer exit is called as last action in a job (except clone jobs), e.g. after set status / start change / execute client actions. After program abort because of error, the customer exit will be called, too, but parameter PF_ERROR indicates the error.
Execute customer specific actions Customer Exit /PRONOVIA/MSC_X_CUST_ACTION	This customer exit is used to implement client specific actions See also Enhancements for Client Specific Actions for Client Specific Actions.