|
Home > Archive > BizTalk Server Applications Integration > September 2004 > SAP adapter issue
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Srikanth 2004-09-23, 5:51 pm |
| We are using the latest MS SAP adapter and cant fiqure out how to use one
biztalk server instance to talk to one SAP system (client ID, SAP Gateway
Service and Program ID being same) to pick up different iDOCs which need to
be processed by different Orchestrations.
Right now, we have generated the schemas and all of them have the same root
node and namespace, but differ on some internal fields like iDOC type and
message type. Hence we had to build a different assembly for the schema and
reference that schema from the individual assemblies that use them. We also
could not use differnt receive locations as the system complains that one
already exists with the same credentials. So, we are using only one receive
location and all the different iDOCs come through that.
Our problem is that, we want to use different receive locations as each of
the iDOCs need different custom pipelines.
| |
| Hans Valcke 2004-09-28, 3:06 am |
| Hi,
If you want to receive on different locations, you can create multiple
Logical systems on SAP en multiple Partner profiles. Then you can specify
which Idoc goes to which patner profile.
Then on the Biztalk side you must link the SAP port the the receive
location.
I hope this helps ...
"Srikanth" <Srikanth@discussions.microsoft.com> schreef in bericht
news:5C3E1D96-92BD-419C-B1E6-2098919E2141@microsoft.com...
> We are using the latest MS SAP adapter and cant fiqure out how to use one
> biztalk server instance to talk to one SAP system (client ID, SAP Gateway
> Service and Program ID being same) to pick up different iDOCs which need
to
> be processed by different Orchestrations.
>
> Right now, we have generated the schemas and all of them have the same
root
> node and namespace, but differ on some internal fields like iDOC type and
> message type. Hence we had to build a different assembly for the schema
and
> reference that schema from the individual assemblies that use them. We
also
> could not use differnt receive locations as the system complains that one
> already exists with the same credentials. So, we are using only one
receive
> location and all the different iDOCs come through that.
>
> Our problem is that, we want to use different receive locations as each of
> the iDOCs need different custom pipelines.
|
|
|
|
|