Forum Replies Created
-
AuthorPosts
-
June 17, 2010 at 12:42 PM in reply to: Is my SAP Adapter 2.0 in BizTalk 2004 SP2 compatible with SAP ECC 5.0 #25001
Hi,
Sorry I can’t be of much further help. This is something that a person, who has experience with and is knowledgeable in SAP and the SAP adapters in BizTalk, can better answer for you and provide you with further insight.
Good luck,
Daniel.
Hi,
If you are still getting that error, then check the following blog:
http://sandeepshewale.spaces.live.com/blog/cns!597AD44E67439214!212.entry
If it’s a data issue, then correct it or have your partner (who sent this file) correct this issue.
Daniel.
June 17, 2010 at 12:21 PM in reply to: Is my SAP Adapter 2.0 in BizTalk 2004 SP2 compatible with SAP ECC 5.0 #24999Hello,
I have had the same assumption but I am just trying to look for more details and information on compatability and procedures to develop.
Thanks a lot
Dear Daniel,
It is small update. My schema doesn’t receive an error like the following: ‘Unexpected data found while looking for: \r\n’ But data of lacking columns is terrible. I mean they get from the rest columns that have value.
Regards,
Dear Daniel,
Thank you so much for quick help. My current schema has already been set “allow_early_termination=”true”/. Unfortunately, it doesn’t work. Do you have any advice?
Thank you
ok. when i tried the following code:
Message_1.Load(‘<ns0:Root xmlns:ns0=”http://BizTalkMonthlyUpdateSalesExpiration.SchemaInitialSelectMessage”> <ns1:Select xmlns:ns1=”http://schemas.microsoft.com/Sql/2008/05/ViewOp/dbo/View_biztalk_salesExpiration_getOR_RYG_ADP”> <ns1:Columns>ns0:Columns_0</ns1:Columns> <ns1:Query>ns0:Query_0</ns1:Query> </ns1:Select></ns0:Root>’);
I got error: too many characters in character literal
Message_1 is the message I have created against the initial select schema.
Even when i tried this:
Message_1.Load(‘<root><test></test></root>’);
I got same error: too many characters in character literal
Hi Lynn,
I assume you have a schema associated with your initial message, right? So you can generate an instance of that schema from your project, by first right-clicking on the schema file and choosing Properties option, this will bring the up the schema’s Property Pages window, specify the value for the Output Instance Filename property in the General section, save your changes. Then right-click again on the schema file and choose Generate Instance option. Go and file the XML file generated that represents the instance of your schema, copy its contents, then in the Expression shape, write the following line of code:
xDocument.Load(“<Contents of XML file instance>“);
Where you replace <Contents of XML file instance> with what you copied form the schema instance file…
Then, further down in your orchestration, you can assign this variable to your message in a Message Assignment shape, like this:
messageRequest = xDocument;
Daniel.
Hi,
Have you tried setting the attribute allow_early_termination to true in the annotation node of your flat file schema? If you can’t do it in Visual Studio, you’ll have to use a text editor to change that setting.
See this blog for more information (even though it was written for version 2004, but I think it’s still applicable to 2009):
http://blogs.msdn.com/b/skaufman/archive/2004/05/07/127899.aspx
Daniel.
[quote user="xman71"]
Hi Lynn,
Open your Biztalk project in Visual Studio, then open your orchestration file, the Orchestration View tab will come up, and you will see a “Messages” folder in the top panel. Right-click on Messages and select New Message option, and specify System.XML.XmlDocument in the Message Type property (in the Properties tab).
Daniel.
[/quote]
Denial,
Ok. I have created serveral messages like that. But those messages seem to serve as message type. how do you use it as an instance or variable so that you may assign the initial message to it?
Thank you very much!
Lynn
Hi Lynn,
Open your Biztalk project in Visual Studio, then open your orchestration file, the Orchestration View tab will come up, and you will see a “Messages” folder in the top panel. Right-click on Messages and select New Message option, and specify System.XML.XmlDocument in the Message Type property (in the Properties tab).
Daniel.
[quote user="xman71"]
1) You define the variable xDocument (of type System.XML.XmlDocument) in your orchestration
[/quote]
Daniel,
Thank you for replying. But how exactly to define the variable in orchestration? I have created messages in orchestration but those messages seem to serve as message types.
Lynn
The Xman, but this does not provide any help. I want to subscribe an outgoing synchronous MDN but all these post they talk about inbound sync/async MDN’s. I have also posted this query MSDN forum but zero answer’s till date. Has some worked on such scenarios ??
Regards,
Hi Iberan,
I can answer your above questions on behalf of Yonathan:
1) You define the variable xDocument (of type System.XML.XmlDocument) in your orchestration, and load the XML instance into that variable in an Expression shape.
2) You assign xDocument to the message msgSqlRequest in a Message Assignment shape.
Best,
Daniel.
June 16, 2010 at 8:06 PM in reply to: Is my SAP Adapter 2.0 in BizTalk 2004 SP2 compatible with SAP ECC 5.0 #24985Hi Ajay,
This is the description from the webpage that downloads the Microsoft BizTalk Adapter v2.0 for mySAP Business Suite:
“The Microsoft BizTalk Adapter v2.0 for mySAP Business Suite integrates SAP data seamlessly (meaning no custom code required) from SAP R/3 4.X and R/3 6.20 (Enterprise) systems with BizTalk Server 2004. This Adapter supports BAPI, RFC & IDocs from SAP Server. The Microsoft BizTalk Adapter v2.0 for mySAP Business Suite provides an all points configuration property grid in a BizTalk Server 2004 Visual Studio project that incorporates configuration of the SAP .Net Connector, routing configuration, and schema conversion.“
I assume that SAP ECC 5.0 is an upgrade from the SAP R/3 platform, so my best guess is: at worst, SAP ECC 5.0 is not compatible with the SAP adapter of BizTalk 2004, and, at best, you might need to do custom coding to make the integration work, but then, this would definitely not be supported by Microsoft if you run into any issues…
Hope this helps,
Daniel.
June 16, 2010 at 3:02 PM in reply to: An internal server error was encountered while attempting to transmit the message #24984One thing that just caught us. You probably should use System.IO.Stream Msg = pInMsg.BodyPart.Data (not GetOriginalDataStream() because exiting the component will dispose of the stream in some cases before the next component can read it. Using.Data will clone the incoming message.
John
-
AuthorPosts