Kontakt

Ansicht
Dokumentation

CRM_IPM_SPOT_SE_RAA - Notes on Implementation

CRM_IPM_SPOT_SE_RAA - Notes on Implementation

RFUMSV00 - Advance Return for Tax on Sales/Purchases   General Material Data  
This documentation is copyright by SAP AG.
SAP E-Book

All Business Add-Ins (BAdIs) grouped under this structure node belong to enhancement spot CRM_IPM_SPOT_SE_RAA.

These BAdIs allow you to override the existing mapping for the enterprise services for the rights availability analysis by using inbound processing and outbound processing methods. You can create mappings for the following services:

If activated, these BAdIs are called when the user inputs the RAA request information.

If the BAdI definitions are not activated, the system uses the existing mapping mechanisms.

The BAdIs within this enhancement spot all have the following methods:

  • INBOUND_PROCESSING
  • OUTBOUND_PROCESSING
  • SKIP_STANDARD_MAPPING_IN
  • SKIP_STANDARD_MAPPING_OUT

For more information, see below.

INBOUND_PROCESSING

This method receives the service-specific proxy inbound structure as input and maps it to the API inbound table format. It has a log parameter to record the activities in the form of a table of messages, and a Boolean changing parameter, CV_SKIP_MAPPING TYPE CRMT_IPM_BOOLEAN. This allows you to specify whether the system should use the SAP standard mapping, or the mapping that you have specified within the method. Set the indicator for this parameter to TRUE to use your own mapping.

For the Simulate Inquiry Confirmation Rights Group service BAdI, this method contains the following parameters:

IMPORTING PARAMETER: IS_INPUT ,,TYPE IPM_IPRAI_CONF_RGSIMQ

CHANGING PARAMETER:  CS_APPLDATA TYPE CRMT_IPM_SE_RAA_API_INBOUND

               ,,,,  CT_LOG ,,TYPE APPLMSGTAB

OUTBOUND_PROCESSING

In this method you can map the API outbound table (input parameter) to the service-specific outbound proxy structure. This method has a log parameter to record the activities in the form of a table of messages.

For the Simulate Inquiry Confirmation Rights Group service BAdI, this method contains the following parameters:

IMPORTING PARAMETER: IS_APPLDATA ,,TYPE CRMT_IPM_SE_RAA_API_OUT_GLB

CHANGING PARAMETER:  CS_OUTPUT ,,TYPE IPM_IPRAI_CONF_RGSIMR

,,,,,, CT_LOG        ,,TYPE APPLMSGTAB

SKIP_STANDARD_MAPPING_IN

In this method, you can specify whether the system uses the standard inbound mapping, or the mapping that you have specified in the INBOUND_PROCESSING method of this BAdI.

To use your own mapping, set the CV_SKIP_MAPPING changing parameter to ABAP_TRUE.

SKIP_STANDARD_MAPPING_OUT

In this method, you can specify whether the system uses the standard outbound mapping, or the mapping that you have specified in the OUTBOUND_PROCESSING method of this BAdI.

To use your own mapping, set the CV_SKIP_MAPPING changing parameter to ABAP_TRUE.

BAdI Sorter

The BAdI sorter is available to determine the sequence of calls for the various implementations in the multiple-use BAdIs. You can call the sorter and modify the order of the calls to methods.

In the standard system, there are no activated BAdI implementations.

These BAdIs are not filter-dependent and are designed for multiple use. All activated implementations are called and executed.

Implementation Classes

The following example implementation classes are available:

CL_CRM_IPM_RAA_BADI_CHCK_SMPL

This is an example implementation class for BAdI definition CRM_IPM_RAA_SE_CHCK, which is the BAdI for the Simulate Inquiry Confirmation Rights Group service.

CL_CRM_IPM_RAA_BADI_CBULK_SMPL

This is an example implementation class for BAdI definition CRM_IPM_RAA_SE_CBULK, which is the BAdI for the Simulate Inquiry Confirmation Rights Group (Bulk)service.

CL_CRM_IPM_RAA_BADI_SIM_SMPL

This is an example implementation class for BAdI definition CRM_IPM_RAA_SE_SIM, which is the BAdI for the Simulate Inquiry Productservice.

The example implementation classes use a simple mapping of the Rights Market Segment global data type (GDT) into the SAP CRM back-end rights dimensions. The following behavior applies:

  • The default mapping mechanism is skipped.
  • The supplementary components are ignored.
  • The CountryCode GDT is not supported.
  • The RegionCode GDT is mapped to CRMT_IPM_TERRI, the LanguageCode GDT to CRMT_IPM_LANGU, and the IntellectualPropertyExploitationTypeCode GDT to CRMT_IPM_MARKET.
  • The system sends the code values directly to the rights dimension fields in the back-end system and back to the service again, without any additional ISO mapping.






PERFORM Short Reference   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 7614 Date: 20240523 Time: 154551     sap01-206 ( 124 ms )