|
Home > Archive > BizTalk Server General > April 2006 > BizTalk Adapter v2.0 for mySAP Business Suite sp1
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]
| Author |
BizTalk Adapter v2.0 for mySAP Business Suite sp1
|
|
|
| Hi, any blog tips on SAP adapters?
I am using Biztalk 2004 with the BizTalk Adapter v2.0 for mySAP Business
Suite sp1 using the SAP .NET Connector to send idoc messages to SAP from
Biztalk.
Sending several messages at the same time, I sometimes loose a few. Most of
the time, also when they all arrive, I get the following error message in the
status field of the idoc, looking at the "display idoc" transaction of the
SAP GUI.
"The plant data of the material 500245 is locked by the user BIZTALK
Message no. M3897 "
I have heard people talking about load and delivery issues with this adapter
previously. Is there a hotfix addressing this? I was hoping sp1 would fix
this, but it seems not. Where can I learn more? Do I need to register a
premier support case with Microsoft for each of these problems, just to learn
about the hotfix?
Is this a SAP side problem? I heard the SAP Administrator should configure
background batch jobs to handle incoming idocs to avoid that they end up in a
"not processed" queue.
Best regards,
David
| |
| Dick Dijkstra 2006-04-27, 7:26 am |
| David,
I haven't heard about this problem, however I am familiar with another
issue with the SAP adapter used in a debatching scenario you describe.
When you use a send shape within a loop in an orchestration, and the
send shape is connected directly to a SAP send port, not all messages
go into SAP, but disappear somehow... Workaround for this problem is to
write the messages back into the MsgBox from the orchestration, and
have a send port to SAP, with a subscription on the messagetype.
Hope this helps you with integrating BizTalk and SAP,
Dick Dijkstra
| |
| Sam Vanhoutte 2006-04-27, 7:26 am |
| > Sending several messages at the same time, I sometimes loose a few. Most
> of
> the time, also when they all arrive, I get the following error message in
> the
> status field of the idoc, looking at the "display idoc" transaction of the
> SAP GUI.
>
> "The plant data of the material 500245 is locked by the user BIZTALK
> Message no. M3897 "
>
> Is this a SAP side problem? I heard the SAP Administrator should configure
> background batch jobs to handle incoming idocs to avoid that they end up
> in a
> "not processed" queue.
Hello,
The problem you describe (material data locked by user biztalk) is because
you are sending multiple Idocs or RFC calls simultaneously to SAP from your
BizTalk server. SAP just accepts the Idocs, validates them and does the
real processing asynchronously. If you are sending an Idoc that is
executing a material change on material 500245, for example. And at the
same moment you are executing a goodsmovement on that same Material, you
will get this error message of SAP. This is just because of the locking
system in SAP.
Because of the tight locking system of SAP, we implemented all our
Biztalk-To-Sap calls as Bapi calls. In this way we can have sollicit
response ports and we immediately get the SAP Bapi response back in our
orchestration. In that generic orchestration, we implemented some checks to
see if we need to retry the Bapi call etc...
So as far as I see it, this is not a bug/error in the SAP adapter, but more
a symptom of simultaneously submitting Idocs to SAP.
Best regards
Sam Vanhoutte
www.codit.be
|
|
|
|
|