none
Unexpected missing when Biztalk receives Idocs from SAP through WCF-Custom adapter RRS feed

  • Question

  • Hi there

    We utilize WCF-Custom adapter and One way receive port to retrieve Idocs from SAP.

    A big volume Idoc couldn't come through, so we split it into 7 smaller Idocs. There is a job at SAP to send these 7 idocs to Biztalk once a day.

    In transaction code we02, 7 idocs show success(green light). But the weird thing is Biztalk haven't ever received them, nor any warning, error, information logged anywhere.

    We have to resend in transaction code we19 one by one. Biztalk gains them all right after resending.

    Is it caused by the split operation, or some incorrect configuration at Biztalk?

     

    Thanks

    Gou Jun

    Monday, June 21, 2010 8:54 AM

Answers

  • Problem solved.

    As our SAP team explained, the job calls a standard function which doesn't commit, but creates a new record with status 03 in we02 somehow. They don't know why and suspect it's a bug of this function.

    Oliver, appreciate your atttention!

    Thanks

    Gou Jun

    • Marked as answer by Jun Gou[MCTS] Thursday, June 24, 2010 5:51 AM
    Thursday, June 24, 2010 5:51 AM

All replies

  • A green light does not mean anything. Is the status id the same when using we19 and the batch job?
    If you like my post or consider it as a valid answer, please use the buttons to show me - Oliver

    http://biztalk.hauth.me

    Monday, June 21, 2010 12:11 PM
  • Yes, Both status ids are 03.
    Tuesday, June 22, 2010 1:08 AM
  • Is there any chance an Idoc hasn't been sent out, while the status in we02 is 03?
    Tuesday, June 22, 2010 1:20 AM
  • Have a look at SMQ1 (transactional rfc queues). I'm not sure at the moment if the IDOC status is set when they are written to the queue or if they have been sent out.

    Otherwise enable RFC logging on BizTalk and have a look what has been transmitted (there is a post on my blog about it). If this is not enough detail, use a network logger like netmon.


    If you like my post or consider it as a valid answer, please use the buttons to show me - Oliver

    http://biztalk.hauth.me

    Tuesday, June 22, 2010 5:05 AM
  • Problem solved.

    As our SAP team explained, the job calls a standard function which doesn't commit, but creates a new record with status 03 in we02 somehow. They don't know why and suspect it's a bug of this function.

    Oliver, appreciate your atttention!

    Thanks

    Gou Jun

    • Marked as answer by Jun Gou[MCTS] Thursday, June 24, 2010 5:51 AM
    Thursday, June 24, 2010 5:51 AM