cancel
Showing results for 
Search instead for 
Did you mean: 

BBP_CCM_CHAR_MAINT

Former Member
0 Kudos

I have the following scenario: srm -> xi -> srm-mdm-catalog and I want to send product data to catalog.

I´ve configured the BADI BBP_CCM_CHAR_MAINT to send some fields from SRM to XI. This fields are into the XML, but I cannot see this fields in the Import Manager.

Need I to do others configurations?

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

Please read the documentation for the BADI carefully:

Short Text

Transfer of Additional Characteristics to SAP CCM

Use

This Business Add-In (BAdI) is used in the SAP Enterprise Buyer (SRM-EBP) component.

When you transfer SRM product data to SAP Catalog Content Management (SAP CCM), this BAdI enables you to also transfer additional item characteristics contained in the product master data in SAP Enterprise Buyer. These characteristics are then available in the SRM product catalog in SAP CCM.

<b>This BAdI is called when you run the report BBP_CCM_TRANSFER_CATALOG</b>.

<b>Note: When you transfer SRM product data to SAP CCM, the attributes that correspond to the following SAP CCM characteristics are transferred automatically. The item ID and item short texts are also transferred automatically. If you want to transfer values for these characteristics only, you do not need to use this BAdI:</b>

/CCM/PRODUCT_GUID

/CCM/PRODUCT_ID

/CCM/IS_SERVICE

/CCM/LOG_SYS

/CCM/PRODUCT_GROUP

/CCM/BASE_UOM

/CCM/PARTNER_GUID (for any product-vendor (PRDVND) interlinkage entry)

/CCM/SUPPLIER_ID (for any PRDVND interlinkage entry)

/CCM/SUPPLIER_NAME (for any PRDVND interlinkage entry)

/CCM/SUPPLIER_PART_NO (for any PRDVND interlinkage entry)

/CCM/PRICE

/CCM/PRICE_BASIS_QUANTITY

Standard settings

In the standard system, this BAdI is not activated.

The BAdI is delivered with a default implementation.

The BAdI is filter-dependent: You implement it on a client-specific basis.

This BAdI is not reusable.

Activities

After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.

If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:

1. In the dialog box, enter a name for the implementation of the Add-In and choose Create.

The system displays the initial screen for creating Business Add-In implementations.

2. On this screen, enter a short description for you implementation in the Implementation Short Text field.

3. If you choose the Interface tab, you will notice that the system has filled in the Name of the Implementing Class field automatically, by assigning a class name based on the name of your implementation.

4. Save your entries and assign the Add-In to a package.

5. To edit a method, double-click its name.

6. Enter your implementation code between the method <Interface Name>~<Name of Method>. and endmethod. statements.

7. Save and activate your code. Navigate back to the Change Implementation screen.

Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not carry out the following step:

8. Choose Activate.

When the application program is executed, the system carries out the code in the method you wrote.

Also see the foll notes:

Note 850613 - Maintaining the BBP_CCM_CHAR_MAINT BAdI using Customizing

Note 875039 - BBP_CCM_CHAR_MAINT: Valuating predefined characteristics

BR,

Disha.

Pls reward points for useful answers.

Former Member
0 Kudos

I´m already using this BADI for four new fields (Loked, Deleted, Client and Product Text - Long description ).

I created this fields in the MDM Console and I added them in BADI.

For the method ENHANCE_CTY_DEF, was added:


  DATA:
    ls_char_definition TYPE bbp_ccm_char_definition.

  ls_char_definition-char_name          = '/CCM/CLIENT'.
  ls_char_definition-char_datatype      = 'CHAR'.
  ls_char_definition-multival_indicator = ''.                  "abap_true
  APPEND ls_char_definition TO et_char_definition.

  ls_char_definition-char_name          = '/CCM/LOCKED'.
  ls_char_definition-char_datatype      = 'CHAR'.
  ls_char_definition-multival_indicator = ''.                  "abap_true
  APPEND ls_char_definition TO et_char_definition.

  ls_char_definition-char_name          = '/CCM/DELETED'.
  ls_char_definition-char_datatype      = 'CHAR'.
  ls_char_definition-multival_indicator = ''.                  "abap_true
  APPEND ls_char_definition TO et_char_definition.

  ls_char_definition-char_name          = '/CCM/PRODUCT_TEXT'.
  ls_char_definition-char_datatype      = 'CHAR'.
  ls_char_definition-multival_indicator = ''.                  "abap_true
  APPEND ls_char_definition TO et_char_definition.

For the method VALUATE_PRODUCT, was added:


  ls_char_valuation-char_name       = '/CCM/CLIENT'.
  ls_char_valuation-char_value      = sy-mandt.
  ls_char_valuation-multival_index  = 0.
  APPEND ls_char_valuation TO et_char_valuation.

  ls_char_valuation-char_name       = '/CCM/LOCKED'.
  ls_char_valuation-char_value      = lo_prod_stats->bloqueado.
  ls_char_valuation-multival_index  = 0.
  APPEND ls_char_valuation TO et_char_valuation.

  ls_char_valuation-char_name       = '/CCM/DELETED'.
  ls_char_valuation-char_value      = lo_prod_stats->excluido.
  ls_char_valuation-multival_index  = 0.
  APPEND ls_char_valuation TO et_char_valuation.

  ls_char_valuation-char_name       = '/CCM/TPRODUCT_TEXT'.
  ls_char_valuation-char_value      = 'TEST'.
  ls_char_valuation-multival_index  = 0.
  APPEND ls_char_valuation TO et_char_valuation.

I can see this data at the XI:



<PropertyValuation>
 <PropertyReference>/CCM/CLIENT</PropertyReference> 
 <PropertyValues>
 <SimpleValue>
 <NameSpecification>430</NameSpecification> 
 </SimpleValue>
 </PropertyValues>
</PropertyValuation>
<PropertyValuation>
 <PropertyReference>/CCM/LOCKED</PropertyReference> 
 <PropertyValues>
 <SimpleValue>
 <NameSpecification></NameSpecification> 
 </SimpleValue>
 </PropertyValues>
</PropertyValuation>
<PropertyValuation>
 <PropertyReference>/CCM/DELETED</PropertyReference> 
 <PropertyValues>
 <SimpleValue>
 <NameSpecification></NameSpecification> 
 </SimpleValue>
 </PropertyValues>
</PropertyValuation>
<PropertyValuation>
 <PropertyReference>/CCM/PRODUCT_TEXT</PropertyReference> 
 <PropertyValues>
 <SimpleValue>
 <NameSpecification></NameSpecification> 
</SimpleValue>

But I cannot see them in the MDM Import Manager. When I run the MDIS, only the standard fields are imported.

Thanks.

Evandro

Former Member
0 Kudos

Hi

<u>Please go through this -></u>

Note 724097 - Search of the comp. in case of structured characteristics

Regards

- Atul

Former Member
0 Kudos

Thanks for your response, but my problem is how to put the data non-standard into the MDM. I already have the data in the XML.

I want to use the MDIS for put the data into MDM. Need I to do anything at the MDM Console (xml schemas) ?

Fields as "short description" and "service item" are imported, but the new fields (Client, Locked, Deleted and product text) are not.