Ansicht
Dokumentation

SOLMAN_RM_BADI_CONS - BAdI: Implement Consistency Checks in Requirements Management

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

For each condition in the customer namespace (Y*, Z*), a filter value now exists for which you can implement the BAdI definition SOCM_CHECK_CONDITION.

Apart from causing a condition to be called implicitly when a status is saved, you can also use a PPF action to include the action directly in transaction processing as a function of the PPF toolbar. To do so, you have to use the PPF method HF_CHECK_STATUS.

The condition has been defined for Change Request Management.

1. For the implementation, either assign a new name, or reuse an implementation that you have already created.
2. Enter the filter value (the condition ID) as the parameter FLT_VAL.
3. Implement the method CHECK_CONDITION.
4. The standard proxy instance is transmitted with the interface IF_SOCM_INSTANCE_ATTRIBUTES. You have to use the parameter CONDITIONS_OK to inform the caller whether the condition is met.

Fill RESBD Structure from EBP Component Structure   General Material Data  
This documentation is copyright by SAP AG.

Length: 1039 Date: 20240606 Time: 130804     sap01-206 ( 24 ms )