Quantcast
Channel: SCN : All Content - Process Integration (PI) & SOA Middleware
Viewing all articles
Browse latest Browse all 7030

Issue with Extended CREMAS05 Idoc

$
0
0

Hi All,

 

I am working on standard ECC sourcing integration, interface is: supplier data.

 

We are receiving CREMSA.CREMAS05 standard Idoc from ECC and posing Supplier data to Sourcing.

 

In addition to this there was a requirement to post vendor contact data to Sourcing from ECC.

 

As the first name and last name were not coming in standard CREMAS05 Idoc, we have added one optional Z segment having first name and last name to standard Idoc, and added extension to standard Idoc ZCREMAS05.

 

Now our partner profile looks like

 

Msg Type : CREMAS

Basic Type : CREMAS05

Extension Type : ZCREMAS05

 

In PI : for vendor cotact interface, we have done ESR development using new Idoc CREMAS. CREMAS05. ZCREMAS05

 

Now, whenever CREMAS Idoc is triggered from ECC, its coming to PI with root node as ZCREMAS05, therefore our custom vendor contact
interface is executing successfully however standard vendor interface is failing as its configured with CREMAS05 Idoc not the std one.

 

What setting is required in ECC or PI so as to eliminate this issue?

 

Thanks,

Ruchi


Viewing all articles
Browse latest Browse all 7030

Trending Articles



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