COMEV and COMPR naming

[Former Member]

Hi Experts,

In IS Utilities, i see the naming pattern for some function modules having ZCOMEV and ZCOMPR.

what actually does that COMEV and COMPR stand for?

Pls explain

Thanks

DAny

[Former Member]

The Z indicates that they are your custom ones as they are not there in our system. But if you look at the function modules that have the pattern COMEV and COMPR, you will notice that they are related to event generation in ISU to pass information or to receive information to and from external systems. Information can vary from master data to service orders to payments.

[Former Member]

Hi Srinivas Adavi ,

Thanks for the reply.

Forget about that Z*...custom ones. I can see few IDoc's / FM's holding the COMEV & COMPR naming patetrn.

So you mean to say that :

COMEV : event generation in ISU to pass information external systems

COMPR : event generation in ISU to RECEIVE information external systems

Contradiction - But i see some IDOCS or FM with naming pattern COMPR's as outbound which means to send information & vice versa.

Please give some insight..

thanks

Dan

Edited by: Dan on Jan 16, 2008 10:21 AM

[Former Member · Accepted solution]

Hi,

COMEV - Communication Event

COMPR - Communication processing

In IDE, we use COMEV and COMPR FM's for processing our logic. From COMEV, depending on the configurations done by us COMPR FM will be determined and will be called from COMEV FM.

[Former Member]

Hi Dan,

COMEV and COMPR function modules are used to post the IDOC to the Middleware and Vice Versa.

This is called as Inbound and Outbound Idocs.

We trigger the COMPR function module by using the COMEV Fm depending upon the configurations done , which will differentiate between outbound and inbound IDocs.

Reward If useful.

Regards,

Chitra