Value mapping in the ERP system during IDOC creation

[Former Member]

We have a PI File-IDOC scenario.

We can translate simple mappings such as currency or unit of measure in PI(7.1) using the Value Mapping function. For complicated mappings involving business logic (e.g. Tax code which is derived from multiple fields) we want to perform these mapping in the ERP (ECC6) system. Is there an approved generic SAP standard process where these value mappings can be done in the IDOC creation which is still valid when re-processing?

e.g. a specific BADI or enhancement point recommended for these mapping?

There might also be a requirement to add segments based on value mapping logic for example when a tax record segment is only required for a non-zero tax code which is mapped via business logic.

Can someone please direct me in the right direction.

[Former Member]

Thanks for your answers but I assumed that using a user exit / Enhancement point was obvious. What I'd like to know is a generic entry point that I can estabolish a IDOC enhancement framework. Somewhere I can call a class containing methods linked to IDOC message types

e.g. Call similar to my prototype (this will be where dependant on mappings certain segments will need to be inserted such as tax segments.

ASSIGN control-mestyp TO <mestyp>.

CALL METHOD (<mestyp>)

EXPORTING

control = control

data = data

IMPORTING

have_to_change = have_to_change

protocol = protocol

new_entries = new_entries.

The "entry point" must be processed both at creation and reprocess. We are also dealing with Inbound IDOCs not outbound

[Former Member]

Hi,

I agree with Ravi..Normally User exits will be preferred for these kind of conversions...

for your case if changes are minor identfy user exits for the same ...if the idoc itself is new then new function module can be written for the same..in that you can handle all these validations...

HTH

Rajesh

[former_member181962]

Hi,

Although i am not sure if SAP mentioned a recommended approach for this, what people usually do is to identify a suitable user exit in the Outbound Idoc processing function module and implement your code in there.

For example, for MATMAS IDOC, you can write your code in user exit: EXIT_SAPLMV01_002.

Best Regards,

Ravikanth Talagana