Quantcast
Channel: SCN : Unanswered Discussions - Process Integration (PI) & SOA Middleware
Viewing all articles
Browse latest Browse all 6719

Custom / Specific inbound ADRMAS IDoc

$
0
0

Hi,

I would like to use a Custom / Specific IDoc Message for ADRMAS (e.g ZADRMAS) with IDoc type ADRMAS03.

I did my ALE config as usual, but when ECC receives an inbound IDoc ZADRMAS.ADRMAS03, I have this error "The IDoc interface is not complete for message type ZADRMAS".

 

Question: For ADRMAS03 (Customer/Vendor Address), can we define and use a specific IDoc Message like ZADRMAS ? or can we only use the standard one: ADRMAS ?

 


In detail, here's what I did:

WE81 – Message Type: ZADRMAS

 

WE82 – IDoc Type / Message:  ZADRMAS + ADRMAS03 + (no extension) + version = 640.

 

WE57 – Assign FM to Logical Message and IDoc Type:

Function Module = BAPI_IDOC_INPUT1

Function Type =  Function Module

Basic Type =ADRMAS03

Message Type = ZADRMAS

Direction = Inbound

 

in WE42 - For inbound process code "BAPI" I also added my IDoc Message (ZADRMAS), but with or w/o this entry, there is no difference, that does not work.

 

WE20 - Partner Profile (for an Inbound Idoc)

Message Type = ZADRMAS

Process Code = BAPI (as I already used for ADRMAS itself)

 

BD64 - Distribution Model.

 

regards

Mickael


Viewing all articles
Browse latest Browse all 6719

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>