Skip to Content

Summary

This blog describes an example for integrating a standard sales order field from ECC into the Lean Order Interface so that it can be displayed in the CRM Web UI.

There are essentially 5 steps required: 

  1. Extend the ECC communication structures
  2. Configure the ECC mapping table
  3. Register the field in PAI logic to allow save of changed data to ECC
  4. Extend the CRM structures
  5. Configure the CRM layout

In the following example we want to display the ‘Your reference’ field of the order (VBKD-IHREZ) in the Web-UI, however the same process can be used to trensfer bespoke fields.

 

1. Extend the ECC communication structures

First of all we need to identify the correct communication structure of the LORD interface. The following options are available:

  • TDS__COMV
    • This contains fields that could be changed
  • TDS__COMR
    • This contains read only fields
  • TDS__COMC
    • This is a CHAR 1 indicator for each field that is used to derive the correct input status and flags the fields as changed

is variable depending on the data you are dealing with. In our case we are dealing with header data that need to be able to be changed and therefore we will be applying our enhancements to TDS_HEAD_COMV and TDS_HEAD_COMC.

The following append structures were added to the respective data types in ECC:

image image

 

2. Configure the LORD Mapping Table

The next thing we need to do on ECC is to tell the system which field needs to be mapped to our communication structure. This is done by maintaining table LORD_MAPPING.

image

In here you need to reference the VA03 screen and set the display attributes which are picked up by the *_COMC structure and passed back to CRM to determine the input-readiness.

3. Extend the PAI logic in ECC

Despite the fact that we are dealing with a standard ECC field, we still need to register the fields for PAI processing. This essentially allows the data to be updated in ECC when passed in via the APIs. If this step is not done the changes will be passed to ECC but the new data will be ignored and no update will take place for your field.

There is a BADI available to implement this – BADI_LORD_DO_PAI. Implementing Method IF_BADI_LORD_DO_PAI~ADD_SUPPLY_LIST allows you to register ‘new’ fields to the processing logic.

 

method IF_BADI_LORD_DO_PAI~ADD_SUPPLY_LIST.

  data: ls_supply type tds_field_supply.

  if iv_object_id eq ‘HEAD’.
    clear ls_supply.
    ls_supply-field = ‘ZZIHREZ’.
    ls_supply-check = ‘N’.
    append ls_supply to ct_supply.
  endif.

endmethod.

4. Extend the CRM structures

The next step is to use the AET (Application Enhancement Tool) to automatically extend the ERP order header field in the UI configuration.

image

5. Configure the layout

Once you have the field available you can configure the layout as normal to display the field in the Web UI.

And then the ECC value is automatically displayed in the UI

image

 

 

To report this post you need to login first.

7 Comments

You must be Logged on to comment or reply to a post.

  1. Hanlie Combrinck

    Hello, Thanks for the informative posting. It helped us, but I just want to mention that

    activation of Enterprise Business Functions LOG_SD_CI_01 and LOG_SD_SIMP_02 in ECC are required before LORD enhancements will work.

    Kind regards

    Hanlie

    (0) 
  2. Benoît Sabys

    Hello,

    I’d like to do the same with more “complicated” fields.

    So I am wondering, how can we know which program/screen can be used ?

    For instance I’d like to manage fields in program SAPLATP4, screen 500 (Availability control)

    Thanks

    (0) 

Leave a Reply