|
Home > Archive > BizTalk Server Applications Integration > October 2005 > Debugging SAP Adapter 2.0 within BizTalk
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 |
Debugging SAP Adapter 2.0 within BizTalk
|
|
| vicente_castello@hotmail.com 2005-09-16, 8:47 pm |
| I would like to debug a scenario where IDocs are being sent from
BizTalk to SAP using the SAP Adapter. Within the orchestration, XML
data is being transformed to IDoc data and then sent via a Send Port
tied to the SAP Adapter. When sending IDocs, some of the IDocs are
being lost. I believe that the data is being sent incorrectly and this
is the reason for the data not being persisted to the SAP database.
I've been able to trace the incoming request from within SAP and I know
that the SAP Adapter makes the following RFC calls.
RFC_PING
IDOC_INBOUND_ASYNCHRONOUS
BAPI_TRANSACTION_COMMIT
I have worked with other Microsoft products like DCOM Connector/.Net
Connector and there has always been a means of tracing the request to
SAP.
Please let me know if there is any way to turn on RFC trace within the
SAP Adapter. The underlying RFC library provided by SAP provides
tracing capabilities, but my problem is how to turn it on using the SAP
Adapter within Biztalk. There has to be some means of RFC tracing at
the client.
Any information on the above would be appreciated.
--Vince
| |
|
| I don't think you can do this from the adapter. In my case I had to trace
through the iDoc receipt in SAP to find anything of use.
Of particular use in my iDoc receipt tracing was SAP transaction we05, where
I could see the iDocs that had been created. I could then drill in to each
one and find the errors and try to resolve them. This worked OK for iDocs
that had been received with Errors.
I was also able to make a little use of the HAT messages in the message flow
for each message that left BTS. In my case they would typically enter a
Suspended (resumable) state and I could look at the Error Infor on the
message flow screen to see a little bit of information from SAP. When I gave
those messages to my SAP-aware consultant (I am an SAP idiot) he was able to
resolve those issues.
I'd be interested to find any other tracing information for iDoc/RFC within
BizTalk.
--
Thanks;
cori
"vicente_castello@hotmail.com" wrote:
> I would like to debug a scenario where IDocs are being sent from
> BizTalk to SAP using the SAP Adapter. Within the orchestration, XML
> data is being transformed to IDoc data and then sent via a Send Port
> tied to the SAP Adapter. When sending IDocs, some of the IDocs are
> being lost. I believe that the data is being sent incorrectly and this
> is the reason for the data not being persisted to the SAP database.
>
> I've been able to trace the incoming request from within SAP and I know
> that the SAP Adapter makes the following RFC calls.
>
> RFC_PING
> IDOC_INBOUND_ASYNCHRONOUS
> BAPI_TRANSACTION_COMMIT
>
> I have worked with other Microsoft products like DCOM Connector/.Net
> Connector and there has always been a means of tracing the request to
> SAP.
>
> Please let me know if there is any way to turn on RFC trace within the
> SAP Adapter. The underlying RFC library provided by SAP provides
> tracing capabilities, but my problem is how to turn it on using the SAP
> Adapter within Biztalk. There has to be some means of RFC tracing at
> the client.
>
> Any information on the above would be appreciated.
>
> --Vince
>
>
| |
| artinv 2005-10-04, 5:53 pm |
| There are 3 system variables that you can add to the orch...CPIC_TRACE.(value
1, system.char)..RFC_TRACE (value 1, system.byte) and RFC_TRACE_DIR (value
"c:\directoryoffile"), system.string. You will receive a trace log that will
help you figure out issues.
"vicente_castello@hotmail.com" wrote:
> I would like to debug a scenario where IDocs are being sent from
> BizTalk to SAP using the SAP Adapter. Within the orchestration, XML
> data is being transformed to IDoc data and then sent via a Send Port
> tied to the SAP Adapter. When sending IDocs, some of the IDocs are
> being lost. I believe that the data is being sent incorrectly and this
> is the reason for the data not being persisted to the SAP database.
>
> I've been able to trace the incoming request from within SAP and I know
> that the SAP Adapter makes the following RFC calls.
>
> RFC_PING
> IDOC_INBOUND_ASYNCHRONOUS
> BAPI_TRANSACTION_COMMIT
>
> I have worked with other Microsoft products like DCOM Connector/.Net
> Connector and there has always been a means of tracing the request to
> SAP.
>
> Please let me know if there is any way to turn on RFC trace within the
> SAP Adapter. The underlying RFC library provided by SAP provides
> tracing capabilities, but my problem is how to turn it on using the SAP
> Adapter within Biztalk. There has to be some means of RFC tracing at
> the client.
>
> Any information on the above would be appreciated.
>
> --Vince
>
>
|
|
|
|
|