Ansicht
Dokumentation

CRM_CLA_VS_MAP_VALUE - BAdI: Map SAP NetWeaver BW Values to Claim Fields

ABAP Short Reference   CPI1466 during Backup  
This documentation is copyright by SAP AG.

This Business Add-In (BAdI) is used in the Validation Sheet (CRM-CLA-VWS) component.

If you are using a new planning profile, you use this BAdI to maintain the mapping relationships between the InfoObjects and the resolution fields that they update.

There is an assignment block in the validation sheet called Volumes and Spends (for a single-customer scenario) and Spends(for a multi-customer scenario). This assignment block shows the data that you can maintain that is persisted in SAP NetWeaver Business Warehouse (SAP NetWeaver BW). Some of this data reflects values that you can find in the resolution assignment block of the claim. The values used in the assignment blocks are used to update the claim resolution assignment block. The data that you can see is dependent on how you have implemented the planning profile.

You can execute additional checks on a project basis. For example, depending on some value amount, the value must be synchronized to different resolution fields. For example, if the method GET_BI_CLAIM_MAPPING has SAP BW data as an input parameter, and includes the value Claimed Amount, you can apply logic to define a limit. If the value does not exceed the limit, it is used to update the claim resolution field. If the value exceeds the limit, it is not used to update the claim resolution field.

The fields that can be maintained in the validation sheet are read only in the claim resolution assignment block. You can enter these amounts in only one of the following places: the validation sheet or the claim resolution UI.

The BAdI is filter dependent. The current planning profile name is used as the filter. If a new planning profile is given a name that does not fit the available filters, a new enhancement implementation must also be provided. If a new planning profile needs to be created, and this planning profile should not use the available enhancement implementation, the chosen name may not fit the available filters.

The BAdI contains the following methods:

• GET_BI_CLAIM_MAPPING

This method returns the mapping table for InfoObjects and claim fields. The mapping table is of type CRMT_CLA_VS_KFP_MAP_VALUES, which relies onstructure CRMS_CLA_VS_KFP_MAP_VALUES, which has the components INFO_OBJECT_NAME and CLAIM_FIELD_NAME.

For INFO_OBJECT_NAME, you must provide the InfoObject name that represents the appropriate value in either the Volumes and Spends or the Spends assignment block. For CLAIM_FIELD_NAME, you must provide the appropriate field in the resolution block to be adapted by the InoObject value. For example, if you want to update the claim resolution field CLAIMED_AMOUNT with InfoObjectX, you assign the value InfoObjectX to INFO_OBJECT_NAME and assign the value CLAIMED_AMOUNT to CLAIM_FIELD_NAME.

CLAIM_FIELD_NAME can be one of the following values: CLAIMED_AMOUNT, VALIDATED_AMOUNT or REJECTED_AMOUNT.

The input parameters are the Claim ID and the business intelligence (BI) data. These input parameters can be used by the user to implement some additional checks to determine which mapping should be used. The method returns a table which identifies the current mapping. This is the changing parameter.

• IS_FIELD_MAINT_IN_VS

This method is called from the claim resolution assignment block to check if a particular field should be set to read-only in the resolution assignment block. The import parameter of this method is a value that identifies a claim field in the resolution assignment block.

CLAIM_FIELD_NAME can be one of the values described above.

If the value can be maintained in the validation sheet (if the value is part of the mapping table - see above), the method must return ABAP_TRUE, otherwise it must return ABAP_FALSE. This is the changing parameter. If this method is not implemented and the mapping table has some content, the values can be changed in the resolution assignment block and by the validation sheet.

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_CLA_VS_MAP_VALUES_SCS

Used for the planning profiles that are used in a single-customer scenario. The filter accepts planning profile names that match the pattern 4VSMP*.

• CRM_CLA_VS_MAP_VALUES_MCS

Used for the planning profiles that are used in a multi-customer scenario. The filter accepts planning profile names that match the pattern 4VMP*.

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.

The following is an example of the CRM_CLA_VS_MAP_VALUES_MCS implementation that implements the class CL_CRM_CLA_VS_MAP_VALUES_MCS:

METHOD create_base_map_tab.

  DATA: ls_base_map_tab TYPE crms_cla_vs_kfp_map_values,

        lt_base_map_tab TYPE crmt_cla_vs_kfp_map_values.

  CLEAR ls_base_map_tab.

  CLEAR lt_base_map_tab.

  ls_base_map_tab-info_object_name = '0VS_VAMT'.

  ls_base_map_tab-claim_field_name = 'CLAIMED_AMOUNT'.

  APPEND ls_base_map_tab TO lt_base_map_tab.

  ls_base_map_tab-info_object_name = '0VS_OKAMT'.

  ls_base_map_tab-claim_field_name = 'VALIDATED_AMOUNT'.

  APPEND ls_base_map_tab TO lt_base_map_tab.

  rt_base_map_tab = lt_base_map_tab.

ENDMETHOD.

METHOD if_ex_crm_cla_vs_map_values~is_field_maint_in_vs.

  DATA: lt_base_map_tab TYPE crmt_cla_vs_kfp_map_values.

  lt_base_map_tab = create_base_map_tab( ).

  READ TABLE lt_base_map_tab WITH KEY claim_field_name = iv_claim_field_name TRANSPORTING NO FIELDS.

  IF sy-subrc = 0.

    cv_is_field_maint = abap_true.

  ENDIF.

ENDMETHOD.

METHOD if_ex_crm_cla_vs_map_values~get_bi_claim_mapping.

  ct_map_tab = create_base_map_tab( ).

ENDMETHOD.

ROGBILLS - Synchronize billing plans   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 8036 Date: 20240523 Time: 152122     sap01-206 ( 185 ms )