Ansicht
Dokumentation

CRM_ICM_BWIF_ACT05 - Assign Source of Information for ICM Batch Interface Parameter

Vendor Master (General Section)   ABAP Short Reference  
This documentation is copyright by SAP AG.

The ICM Interface structures are filled with data from the BI Query. If the field names of the Query do notmatch the fieldnames in the Interface Structures, you use this activity to map the BI field name, a constant value, or a user-defined function module to the ICM structure and field name.

Additionally, you have the option of specifying different mapping for the header and the detail records. If you specify header mapping, the interface creates a header record. Unless your ICM application has a hierarchy defined, you should create only detail mapping records.

You have created the BI-ICM transfer application and technical BI Query.

Optionally, you can utilize a mapping file in .csv format to map the BI field name to the ICM field name.

This activity allows you to map BI fieldnames or constant values manually to the fixed ICM structure and field name.

Note that header level mapping applies only to Commission Case Object Data records. Additionally, there are situations where you might have different mapping requirements for header and detail records.

For example, if you structure your business object design within your ICM commission application with the following format:

Subobject type	9301 - Commission Case Header
|
- 9302 - Commission Case Detail

• The PARENT_TYPE field in the structure has to be filled for the detail record but not for the header record. In this case, mapping is required only for the detail record.

• The BUSOBJ_TYPE field in the structure has to be filled for both detail and header records. In this case, mapping is required for both header and detail records, even if the source of the data is the same BI field for both records.

You have the option to upload a file in .csv format with the mapping data, rather than performing the mapping manually. The following information describes this process.

Format of User-Defined Function Module

Import and Export parameters are required within a user-defined function module. They have the following requirements:

Import Parameters:,,

QRY_RESULT Like

Export Parameters:,,

Output Like

For example, the Function Module ZFILL_CASE_TEXT has the parameters:

Import Parameters:

QRY_RESULT Like ZCRMT_CRMBW RESULTS

Export Parameters:,,

	Output Type CRMT_BWIFTRICASETXT

Note: You can look up the name of the Query result structure from the application log by using transaction /nSLG1, object = 'CRM_ICM', subobject = 'QRY_RSLT_GEN'.

Input Requirements

You have the option to load the mapping of ICM fields to BI fields manually. You can upload the mapping by using the transaction CRM_ICM_BWIF_007. The input for this transaction is:

• BI-ICM transfer application

• Technical BI Query Name

• An input filename in .csv format

Deleting Existing Records

You have the option to delete existing records by using the checkbox. Unless you select the checkbox, the existing records are modified and any new records are added to the database.

.csv File Description

The .csv format input file can be either on the local PC or on an application server. The file format for the .csv file is as follows:

• Type:

• 1 = BW Field mapping

• 2 = Constant

• 3 = User-Defined Function Module

• BI Field Name

• ICM Structure Suffix:

Permitted values are:

CAS,,,,Commission Case

PAR,,,,Commission Case Participation

INV,,,,Commission Case Participants

REL,,,,Participant Relations in a Commission Participation

ACT,,,,Commission Case Activities

OBJ,,,,Commission Case Object Data

LIN,,,,Variant Commissions

BDL,,,,Rebundling Order for Triggering Subobjects

DOCHD,,Commission Document Header

DOCVA,,Commission Document, Valuation

DOCRE,,Commission Document, Remuneration and Liability

DOCDT,,Comn: Detail Items for Remuneration Rows

DOCSE,,Commission Document: Due Dates

DOCPAR,,Participation of Commission Document

DOCINV,,Participant in Commission Document

DOCREL,,Commission Document: Relationships Between Participants,,,,

DOCACT,,Commission Document: Activities

DOCOBJ,,Commission Document: Object Data

• ICM fFeld Name

• User-Defined Function Module

• Record Level

• Permitted values are:

H,,,,Header

D,,,,Detail

• Description (Optional),,

If the ICM field name value is ** NONE, then that record is not uploaded.

After loading information using this transaction, the data has to be manually transported.

Authorization

To be able to upload data using transaction CRM_ICM_BWIF_007, the user requires authorization object CRMICM_APP and activity 16.

 

Transfer Application	BI Query	Record Level	ICM Struct Suffix	ICM Field Name	User Value	BI Field Name	Function Module
CRMBW	Query1	Header	Commission Document Object Data	DIVISION0		DIVISION0
CRMBW	Query1	Header	Commission Document Object Data	TRI_OBJ_TYPE		0PARENT_TYPE
CRMBW	Query1	Detail	Commission Document Object Data	PARENT_TYPE		0PARENT_TYPE
CRMBW	Query1	Detail	Commission Case	ROLE_COMMSHAR	100
CRMBW	Query1	Detail	Commission Case	CASE_TXT		ZFILL_CAS_TXT

,,,,,,

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

Length: 9101 Date: 20240523 Time: 181031     sap01-206 ( 85 ms )