Skip to Content

Operation Mapping does not show up in the Interface Determination

Oct 18, 2017 at 02:25 AM


avatar image

when i give IDOC in the sender interface of the Interface Determination then I do not get my Operation Mapping, whereas,

when i give my outbound service interface then I get the operation mapping.

but then I have a problem that receiver is not detected.

in other words.......

When I give service interface in the receiver determination and interface determination THEN I can select OM , it DOES NOT detect receiver in Moni. Receiver is blank, moni is in error.

When I give idoc in the receiver determination and interface determination THEN I cannot select OM, so I leave it blank. Then it DOES detect receiver in Moni, but it does not do the OM and xml valid outbound payload still shows idoc, no mapping done.

so how can i get it to select my operation mapping even after giving idoc in the sender interface of interface determination ? it is seen hardcoded in the search criteria and the search result does not show my OM even if its using the same idoc.

great help needed,

thanks in advance,


10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Evgeniy Kolmakov Oct 18, 2017 at 06:40 AM

Hi Bhakti!

While creating Operation mapping you select SCV/Interface/Interface namespace values for sender side and the same for receiver side. So, when you create Interface determination, in which you gonna use that OM, the sender system should have source SCV assigned to it in SLD (in case of Bussiness System) or source outbound (abstract) interface set as Sender Interface (for Bussiness Component). The same applies to receiver side.

If you want to use IDoc interface/message type in your integration scenario, you should import that IDoc definition either in standard SAP SCV (for example, SAP APPL) and assign that component to respective BS/BC as described above or in your own SCV, which is used in your integration process.

Regards, Evgeniy.

10 |10000 characters needed characters left characters exceeded