Ansicht
Dokumentation

CRM_WEC_PSP_ORDCHANG - BAdI: Field Selection

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

This Business Add-In (BAdI) is used in the Basic Functions for Business Transaction (CRM-BTX-BF) component. It is available as a replacement for the classic BAdI CRM_ORDER_FIELDCHECK and offers improved performance compared to the classic BAdI, while providing the same logic.

You can use this BAdI to influence the ready for input status of fields in the business transaction according to user-defined logic.

Note that this BAdI can only be used to reset the ready for input status of fields beyond the standard delivery. A field that is set as not ready for input in the standard system cannot subsequently be made ready for input.

The active implementations of the BAdI CRM_ORDER_FIELDCHECK_NEW are called at runtime from the function module CRM_ORDER_GENERAL_CHECKS_FC.

Performance Considerations

This BAdI is called at the following points in time:

• For each roundtrip in edit mode, to visualize on the UI whether a field is ready for input

• Directly before a certain field is changed to check whether it a change is possible

Furthermore, the BAdI is called for each object, and your implementation should take this into consideration and avoid unnecessary checks being executed.

Since this BAdI is called very often, it is particularly important that the code ensures good performance. You should avoid nested loops, avoid memory-intensive database selects, and implement buffering logic, for example).

For more information about the standard settings (filters, single or multiple uses), see the Enh. Spot Element Definitions tab in the BAdI Builder (transaction SE18).

• CRM_ONE_OFF_ITEM_FC

This implementation is used for one-off charges. It makes fields non-editable after their contents have been transferred to convergent invoicing.

For information about the implementation of BAdIs in the context of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.

If you have previously implemented the classic BAdI and want to use the new BAdI instead, you need to do the following:

• Recreate your implementations of the classic BAdI by copying their logic to a new implementation for the new BAdI.

• Deactivate existing implementations of the classic BAdI.

If you have previously implemented the classic BAdI and do not want to use the new BAdI, no action is necessary; the system continues to process your existing implementations.

The following implementation example blocks for input the External Reference of Sold-To Party field that belongs to the SALES set:

method IF_EX_CRM_ORDER_FIELDCHECK~FIELDCHECK .

  data: ls_input_field_names type crmt_input_field_names.

  if iv_object_name eq 'SALES'.
    ls_input_field_names-changeable = 'A'.
    modify ct_input_field_names
           from ls_input_field_names
           transporting changeable
           where fieldname = 'PO_NUMBER_SOLD'.
  endif.

endmethod.

BAdI method documentation:

FIELDCHECK

RFUMSV00 - Advance Return for Tax on Sales/Purchases   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 4471 Date: 20240523 Time: 170243     sap01-206 ( 120 ms )