FDQM and SAP Adapter

Hi all,
Is It possible to use FDQM SAP Adapter with following configurations of SAP on the Hyperion 11.1.2.1 version.
SAP Kernel: 18
SAP Basis: 05
SAP ABAP: 05
Kindly let me know if there is any documentation available for it.
Thanks and Regards,
Lakshmikanth..

I do not think that the SAP Kernel,SAP Basis and SAP ABAP mentioned in the SR is supported.
Please find the below information which is obtained from the senior Hyperion Specialists which is officially tested and supported.
SAP 4.6c system:
     Kernel: 2415
     Basis: 53
     ABAP: 53
SAP 4.7 system:
     Kernel: 80
Basis: 61
     ABAP: 61
SAP ECC 6.0 system:
     Kernel: 75
     Basis: 09
     ABAP: 09
Hope this helps.
Thanks and Regards,
Dark..

Similar Messages

Integration between Ariba and SAP R/3 4.7

Hi All,
Have anyone implementing the integration between Ariba Software and SAP R/3 4.7?
In my project has using Ariba TIBCO and SAP Adapter as the integration tool that connect to SAP R/3 4.7 Non-Unicode system (using MDM for Thai language).
I found that when I pull data from SAP through Ariba TIBCO and SAP Adater, the Thai character showed as unreadable character like a garbage character.
Please help me.
Thanks

Hi Bimal,
Please go through this document which contains end to end steps to integrate R/3 HR with CRM
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/84dd0c97-0901-0010-4ab2-9849fba57e31
Best Regards,
Pratik Patel
Reward with Points!

Seeburger FTP Adapter And SAP PI 7.1

Hi Everyone,
Just a few questions about Seeburger FTP adapter please. Bit of background for clarity, we are doing an implementation using Seeburger FTP and sap PI 7.1 picking up EDIFACT (Orders) and returning (DESADV, ORDERSP, INVOICES). However we are not using any BIC, using another tool for EDIFACT -> EDIFACT-XML conversion (conversion agent) and in-house mapping development using graphical mapping.
So couple of things which I haven't been able to figure out from the standard documentation for Seeburger FTP adapter:
1) First is the functional ACK which we are meant to send back to the VAN is that a STANDARD FUNCTIONALITY with Seeburger FTP adapter?
2) Because we are receiving a mix bag EDIFACT interchange on the way IN, I need to split messages accordingly and pass them on to the relevant channels and mappings. By using the standard module Splitter can I achieve that?
3) Lastly some of the standard validations which are applicable to EDIFACT are they supported within the FTP adapter automatically? e.g. Counting number of messages in one interchange etc.
Any help in this regard will be really great.
regards

Now a Good news.
If you are using Seeburger version 2.1 (which you should be as you want it for PI 7.1), then there is an Internal Classifier and Split option for FTP adapter. You just need to tick checkbox "Use built-in splitting" and you are done. Then I believe there won't be any need for considering all these problems. The earlier version of Seeburger with PI 7.0 doesn't have such option and that could be the reason you haven't received any appropriate response yet.
Still I will reply all your questions considering that "your case is of PI 7.0". -> remember PI 7.0
>>even with just splitter we should be able to break it up?????? or am I wrong in thinking this?
No. You even need BIC or an equivalent custom module for achieving this.
>>I can't visualize where to handle the overall message count in one Interchange any suggestions?
You need to write an adapter module for this. Not sure about the code but this module has to be added before the split happens.
>> seeburger ftp adapter it does talk about a lot of reports which are available on sender/reciever actions. e.g. delivered, despatched etc. Are these reports not essentially ACKs?
These reports are the ones used at the receiver side for getting the ACKs from the receiver. Your requirement is at present for sender scenario.
Regards,
Prateek

How to configure for GPlus Adapter with SAP Phone and SAP CRM

Hi All Basis Adm,
Please consider as an urgent basis i need the information that how to configure GPlus Adapter with SAP Phone and SAP CRM . My server is CRM 5.0 (kernel 7) with Oracle Database. This information is require to connect Webclient to Sap Phone with GPlus Adapter (Genesys Adapter 7.1). If u have any document regarding mentioned above than that will be acceptable.
Regds,
Govinda

Hi Prasad,
In you case, it's a file to file scenario.
Go thro' this link for a solution:-
/people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1
/people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2
Regards.
Praveen

How to import seeburger adapter and mdm adapter in sap pi 7.3

Hi all,
how to import seeburger adapter and mdm adapter in sap pi 7.3

Hello
To import the Seeburger adapters, follow the instructions in the Master Installation guide and the individual guides for each of the adapters. These are available with the Seeburger software downloads.
Regarding the MDM adapter, this is the wrong forum for that question. Try the MDM forum (but first, try searching the forum as this is a very basic question).
Regards
Mark

Using Oracle SAP Adapter and IBSE for inbound IDOCs

I have been able to successfully use the Oracle SAP Adapter (e.g., IWAY) using the IWAY Business Services Engine (IBSE) to call a BAPI and have information returned. This use case is well documented and seems to be reliable.
However, I have had difficulty finding any examples where IBSE is used with IDOCS. In my case, I would like to have SAP send an IDOC and receive this IDOC in a Fusion 11g environment. I see conflicting statements in the document. On one hand, Section 3 of this document
http://download.oracle.com/docs/cd/E15523_01/doc.1111/e17057/config.htm#BABBGAAH
States "Events are not applicable when using a BSE configuration."
On the other hand, I see lots of documentation that says that you need to configure an Event in order for the IDOC to be sent to the proper destination. IBSE gives the ability to define events for IDOCs but the events are limited to either RMI or JMS. I have looked at the format of the JMS message and it looks extremely difficult to setup.
Has anyone done this before?

Let me try what ever I can to answer.
Loss of IDOCS should not happen. Are you starting the channels in iWay test tools while the JCA adapter is also running?. That should not be the case. iWay Test tools is only for design time purpose. It is not required for runtime. ie. Create channels and test the IDOCS being received. After that stop the channel and start running the server.
I suspect that starting channel in iWay test tools and JCA adapter/BPEL simultaneously will definitely result in IDOCS loss. Some of the IDOCS will come to iWay test tool while others will go to JCA/BPEL.
Regarding 2, lets us discuss this after this loss of messages is solved.
"Another issue that we have with the JCA approach is the requirement to have have a separate channel and a separate program ID for every IDOC. In our SAP system, we have thousands of IDOCS so having to setup a different channel and program ID for each one is going to be a difficult task".Yes. Initial versions of adapter used to support receiving all idocs on same channel. In your case MATMAS05/IORDER01 are received on same programID and customers used has logic to identify what idoc was coming. It was observed that complexity of the application increases exponentially with increased idocs and the debugging effort.And also the interface is not clean. That is the JCA end point cannot be assocaited with a specific WSDL so you will not what you will receive and of what type. To ease this, later version of adapter supported this feature that each idoc type is assocaited with a specific program ID. MATAS05--PID1, IORDER01--PID2. Adapter will ignore if MATMAS05 is sent on PID2.
In OSB we have concept of AnyXML service but I doubt if BPEL has such concept. If I remember OSB smart connect supported your exact use-case, but in later version it was decided to discontinue AnyXML inbounds.
Are you really planning to use hundreds of IDOCS on same PID?. Did you think of debugging complexity in such application? If you really think this need to be supported, please raise an enhancement request with Support. Product management will review your request for further action.
Thanks
Manoj

Issues with creating and sending BOM XML IDOC to SAP using 2010 WCF-SAP Adapter (without using Biztalk Server)

I'm trying to replace an existing Biztalk 2006 Send BOM IDOC process, and completely remove Biztalk server from the equation. The existing Bizatalk 2006 server receives an input BOM (Bill of Materials) flat file, and using a Biztalk Map (BM08),
and Orchestration, generates an Idoc and sends it to SAP.
In my replacement C# program, I'm using the 2010 WCF-SAP Adapter, and am trying to generate the BOMMAT03 XML IDOC it to SAP.
I generated the BOMMAT03 schema from SAP using the Add Adapter Service in VS 2010. I was able to generate a BM08 XSLT from the existing BMO8 map in the current Biztalk 2006 process. I am able to run a XSLT transform on the input BOM flat
file, and generate an XML file from that.
However, I've run into a few issues. First of which, is that the XML file that is generated from the XSLT transform is NOT the same schema as the BOMMAT03 schema expects. It's somewhat similar, but different enough that I have to manually
translate between the two in my code. I've verified that both the original Bitztalk 2006 process and my replacement program use BOMMAT V3 from SAP. Question--Is Biztalk 2006 server doing some other magic to turn that transormed XML into the BOMMAT03
schema?
I ended writing code which translates the transformed XML into the BOMMAT03 schema (which is a strong typed XML IDOC at this point).
However, when I try to send the BOMMAT03 XML IDOC, I get an exception "Object reference not set to an instance of an object."
idocClient.Send(idocData, ref sadapterTxGuid);
idocData is of type BOMMAT03, and I've verified that the various fields are populated.
Any help is appreciated.

Well, putting in a MSDN subscription support ticket for Biztalk server actually helped with the issue. They didn't find, or fix the issue directly. But one of the examples (https://randypaulo.wordpress.com/tag/idoc/) they sent over, jogged my
memory, and I realized in the code snippet below, I had accidentally deleted the 1st line. Such a simple mistake, yet was easy to overlook. The URL example is almost EXACTLY like my code, but without the transform and translation code to convert
from input XML file to IDOC XML. If someone is interested in that, let me know.
//Forgot the 1st line.
idocClient = new IdocBOMMAT03SIEIS_WED_BOMMAT03V3R700Client(binding, endpointAddress);
idocClient.Send(idocData, ref sadapterTxGuid);
For anyone else interested in knowing, you CAN send a strongly typed IDOC to SAP using C#.NET and the WCF SAP 2010 Adapter, using the IDOC Binding Client class you generated using the Add Adapter Service Reference in VS2010.
The one difference, which no one, not even the tech support from MS could tell me, was why the XSLT which I generated from the original map, did not transform the input BOM XML into the BOMMAT03 XML. Instead, it transformed it into an intermediate
XML, which resembled the BOMMAT03 IDOC XML, but still needed to be translated to the BOMMAT03 IDOC format.
The tech support person swore up and down that it should. But I believe that something happens in Biztalk server, after the Mapping occurs, maybe in the Pipeline, which converts that
intermediate XML into the final BOMMAT03 IDOC XML format.
I do think that the examples are severely lacking in showing how to send a strong typed IDOC using C# and the WCF-SAP Adapter. Even worse, the examples are completely lacking in how to actually generate a weakly typed IDOC. They show how to send
that weakly typed IDOC, but show me, or give me a class to be able to generate it.
I realize that this is not quite the "recommended way" to do it, but in reality, not everyone wants or even needs a full Biztalk installation. For some simple stuff like this, a C#.NET program and WCF-SAP adapter do the trick.

Display SAP R/3 table in a portlet with the SAP Adapter

Hello everybody!
I still can`t figure out the whole pictue of Bea Weblogic`s SAP Adapter.
I installed the SAP Adapter (BEA_SAP_1_0_70.ear) and the Applicaton Explorer,
made an Application View with the generated XML-Schema and the Template example
in the WL Integration Studio. So what`s next??? (I want to make a portlet which
displays a table from a BAPI request.) Any help would be helpful!
Thanks 4 answering !
Kind regards,
uggar

Hi Simon,
Thanks for your inputs.
Why the amount is changed in display mode only for WRBTR and not for DMBTR as both are of CURR datatype and created using same domain. I fail to understand any logic behind this.
I have even created a ABAP report on this table which displys fields DMBTR and WRBTR, and in the report output following values are displayed.
DMBTR 100.05
WRBTR 100.05
If anybody else has come across this before and has any clue please help.
Thanks and Regards
Shilpa

The difference between SOAP adapter and WS adapter in PI 7.1

Hello all,
can anybody explain what is the main difference between SOAP adapter and WS adapter in PI 7.1?
I have checked this [link|http://help.sap.com/saphelp_nwpi71/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm]
but was not able to find the real difference.
Or better, what can I do with WS adapter I can't do with SOAP adapter? What are their advantages/disadvantages?
Thank you all, Igor.

In addition to RM, ws adapter also support other ws standard like SAML which is not available in SOAP adatper. Beside:
if your sender or receiver is SAP system, you can also monitor the message in the sender/receiver in addition to the PI box. This is a very good thing, because sometime the MONI in PI shows nothing wrong, but the MONI in your receiver will show you error message that's only related to the receiver system.
However, if you define ws sender CC, and your ws client doesn't support RM, you will have issue sending ws request.
And ws CC will generate ws runtime in PI box, if your configuration is wrong (like user name and password not correct), even if you correct it, the ws runtime sometime won't be regenated based on the correction. In this case you need to delete the ws CC/agreement, and re-create it with all correct information.
Beside make sure your basis team configured the PI system properly regarding ws. If not, you will have lot of pain to figure the problem which was my case.
Jayson

RFC Sender problem between 46D and RFC adapter

Hi,
I have this simple integration scenario where I want to send data to a archiving system;
SAP -> (tRFC) -> XI -> (MQ) -> BizTalk -> (MQ) Arch.syst.
SAP side ***
A Z-program using a Z func. like;
 CALL FUNCTION 'ZSD_DCF_SEND_TAG'
 IN BACKGROUND TASK
 DESTINATION 'XISYSTEM_TRFC_DCF'
 EXPORTING
 pt_filing_info = gt_filing.
 COMMIT WORK AND WAIT.
XI side ***
Both IR and ID is configured correctly, in the development environment everything works just great. I have created a test program where I can define how many calls I will do, looping over the func. call with a commit inside the loop - 500 or more msgs are ok.
The integration scenario is transported to quality enviroment using CMS, and the RFC sender comm.ch. is configured accordingly.
The problem in quality ***
When sending just 1 msg, everything is just fine, message received and delivered to MQ.
When sending >= 2 msgs, the 1 msg is always ok, BUT all others fails due to the following from Adapter monitor;
RFC_HISTORY
- Error: 2006-01-19 10:55:18 CET: com.sap.aii.af.rfc.afcommunication.RfcAFWException: lookup of alternativeServiceIdentifier via CPA-cache failed for channel 'RFCSender_XI0002' (02d4d30de3593874942ed0659add0827, party '', schema 'TechnicalSystem', identifier 'Q93#120')
- OK: 2006-01-19 10:55:17 CET: Message processed for interface ZSD_DCF_SEND_TAG
My sending system is Q93 CLI 505 so I can understand the error, BUT I cannot understand why the RFC adapter is saying the TechnicalSystem is Q93#120 - it should be Q93#505. My Q XI has client 120...
It seems to me that the RFC adapter is kind of confused about the sender..
I have created a OSS message and SAP has looged on and looked into it with both a XI expert and RFC expert without being able to answer - all is configured correctly.
- The SLD config. for bus.system Q93 is ok -
- The bus.system in ID is showing correct vaues for
Adapter Specific Identifiers (SID Q93, client 505)
- Both Dev. and Qual. environment are running on XI 3.0 SP 14 latest patch, RFC component version on the SAP side is identical between dev. and qual. SAP systems
- It doesn't matter which gw I use (Q93 gw or XI gw), the error is persistent
- It doesn't matter if I increase initial conn, max conn.
I have also tried to use qRFC instead, but with the same result.
Anyone using tRFC for asynch. communication from SAP to XI seeing something similar?
Meanwhile, I will do RFC trace on GW and RFC Adapter on AE....
Please, do not say SP15, oss msg for FAQ RFC adapter or links to RFCAdapter config....
best regards
Torstein

Hi,
SAP Note 730870 FAQ: XI 3.0 RfcAdapter Q.no 15
Q 15: Whats wrong when the error message "lookup of alternativeServiceIdentifier via CPA-cache failed" shows up while sending a RFC call to the RfcAdapter?
A: A RFC sender channel is located beneath a service within the Integration Directory. Within this service choose "Service" -> "Adapter-Specific Identifiers". The values in the fields "R/3 System ID" and "Client" has to be maintained with the correct values of the system, that sends the RFC call to the RfcAdapter. It normaly only makes sense to have these values filled for services of type "Business System". If maintained in SLD, this fields will be filled automaticaly for services of type "Business System" and can be updated with the button "Compare with System Landscape Directory".
- Give correct appserver and gateway service details in XI.
- Open the service holding the RFC adapter you are trying to use. On the top menu, goto Service -> Adapter Specific Identifiers..
Regards,
Prateek

How do ABAP Proxy and XI adapter work?

Hi everybody,
I have a general question about the ABAP proxy and XI adapter.
In order to use the ABAP proxy and XI adapter, I must configure the HTTP Destination between the R/3 system and the XI server. I must also maintain the SLD.
After several hours configurations with our administrator, it failed. At least the HTTP Destinations on both servers don't work correctly. We got always HTTP error message. But a scenario with an ABAP Receiver proxy works! It is really strange and laughable. We're very happy about that but don't know why and what happened. Today we tested the ABAP Sender proxy, it doesn't work.
So we decide to ask the XI experts in this forum to give us a general lessen about the ABAP proxy: how it works, why we should create the HTTP destinations, how do the destinations work and so on.
Thanks a lot in advance!
With best regards
Xiang

Hi
Once you create the interface in XI, you generate the proxies on your R3 system.
Client Proxies -->
This is done for outbound interfaces. You generate the proxy and then write a report that fills in the proxy class with the data and pushes it to XI.
Server proxies -->
Generated for inbound interfaces. Generate the proxy and write the implementation for the exectue method that deals with the data sent from XI to the R3 system
Abap Proxy
ABAP Proxies in XI(Client Proxy)
Smarter Approach for coding ABAP Proxies
The specified item was not found.
ABAP Proxy - XML to ABAP Transformation
http://help.sap.com/saphelp_nw04/helpdata/en/ba/f21a403233dd5fe10000000a155106/frameset.htm
why we should create the HTTP destinations, how do the destinations work and so on.
we create http destiantio because in proxies , adapter is not use so who is goin to send the message to integration server ...by creating http destinatio we create integration engine which send messg to IS . then messg is routed .and all
error in HTTP to file scenario http to file
hope this help's you
Regard's,
Chetan Ahuja

SAP XI 2.0 and SAP XI 3.0

can any one differentiate the feautures of SAP XI 2.0 and SAP XI 3.0??

Hi Gabriel,
SAP XI 3.0 enhances the functional range of SAP XI 2.0 by a lot of new features. The most important new features are:
Cross-component Business Process Management
a.You can model executable integration processes and
store them in the Integration Repository.
b. You can execute integration processes on a Business
Process Engine that is part of the SAP XI runtime
environment.
B2B Integration
a. Collaboration partner data can be maintained in the
Integration Directory.
b. A Partner Connectivity Kit (PCK) allows the
integration of business partners not using SAP XI or
other integration solution.
Industry standard support
a. RosettaNet communication with business partners is
supported through a RosettaNet adapter.
b. The RosettaNet adapter is part of an overall package
to enable SAP solutions to participate in RosettaNet
integration.
Adapter Framework and certification of adapters
a. A JCA-based adapter framework allows the integration
of adapters provided by SAP as well as by partners.
b. The integration of partner adapters is certifiable.
Simplified Configuration by Using Integration Scenarios as Templates
a. You can configure integration scenarios from the
Integration Repository and semi-automatically generate
all relevant configuration objects.
Enhanced Integration Builder functions
a. You can define data-dependent user authorizations
b. You can define an infinite number of change lists for
each user and exchange objects between different
change lists of different users.
Check these links
Re: XI 3.0 vs 2.0
is there any diff between sap xi 2.0 and 3.0?
Documentation of XI2.0 & XI3.0
http://help.sap.com/saphelp_xi20sr1/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
Cheers...
Vasu
** REward POints if found useful **

SRFC-adapter and file adapter with error: no adapter found

Hello,
we have two scenarios here in an XI 3.0 SP12:
First scenario connects two R/3 systems via RFC adapter (outbound / inbound) for an RFC in a standard R/3 function module SUSR_ZBV_GET_REMOTE_PROFILES.
The RFC is synchronous.
Second scenario uses file adapter to send file from A to B.
When starting the RFC call from the sender system the error message in area "call adapter" for XML message in the trace is "exception while reading from SLD:Property sap_xiadapterservice.adapterType does not exist".
Message in RWB:
"Transmitting the message using connection http://abc038.ceu.test.com:8077/sap/xi/engine?type=entry failed, due to: XIServer:AE_DETAILS_GET_ERROR:Property sap_xiadapterservice.adapterType does not: Unable to find any Adapter Engines."
Same problem for file adapter!
Here is the message from the file adapter error log entry in SXMB_MONI:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>
<SAP:P1>af.kx1.test038</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>Property sap_xiadapterservice.adapterType does not: Unable to find any Adapter Engines</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error when reading the access data (URL, user, password) for the Adapter Engine af.kx1.test038</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Looks like an identical problem for both adapter.
What we have done (checked) so far:
- SLD connection is working
- Vis.Admin.: no problems found
(SAP RFC adapter active, file adapter active)
- Component monitoring: no errors, adapters are fine
- all rfc connections checked: ok
- have checked user and pwd and replaced to be sure
- cache refresh: ok
- reimport of SWCV to IR for RFC: done, no result
Does anybody have an idea, how to get rid of that?
Best regards
Dirk

Hello Udo,
in Adapter monitoring all adapters are listed and per adapter (here RFC and FILE) all adapter entries from the scenarios are available (sender / receiver comm. channel entries - in green)!
Pipeline URL in SLD Bus. Syst. is fine ( and an IDOC adapter scenario is running successfully) !
I think this is a really tricky one!
Best regards
Dirk

BizTalk 2009 WCF-SAP Adapter Could not load file or assembly 'Microsoft.Adapters.SAP.SAPGInvoker...' one of its dependencies error

Hello,
I have a BizTalk Server 2009 running on Windows Server 2003 x64. I am installing WCF-SAP adapter and have done the following for the same. However, I am getting an error as mentioned below when I click on the Configure button of WCF-SAP adapter in send
port. I would appreciate if anyone could let me know how to fix this error and make the WCF-SAP adapter working.
TITLE: BizTalk Server 2009 Administration Console
Exception has been thrown by the target of an invocation. (mscorlib)
ADDITIONAL INFORMATION:
Exception has been thrown by the target of an invocation. (mscorlib)
Could not load file or assembly 'Microsoft.Adapters.SAP.SAPGInvoker, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. This application has failed to start because the application configuration is incorrect. Reinstalling
the application may fix this problem. (Exception from HRESULT: 0x800736B1) (Microsoft.Adapters.SAP)
This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem. (Exception from HRESULT: 0x800736B1)
I have copied the following 32 bit & 64 bit unicode DLLs in SysWOW64 and System32 folders respectively.
icudt30.dll
icuin30.dll
icuuc30.dll
librfc32u.dll
libsapu16vc71.dll
libsapucum.dll
Following r3dllinst DLLs are there in System32 folder.
mfc42.dll
mfc42u.dll
mfc71.dll
mfc71u.dll
msvcp60.dll
msvcp71.dll
msvcp80.dll
msvcr71.dll
msvcr80.dll
Following r3dllinst DLLs are there in SysWOW64 folder.
mfc40.dll
mfc40u.dll
mfc42.dll
mfc42u.dll
mfc71.dll
mfc71u.dll
mfc80.dll
mfc80u.dll
msvcp50.dll
msvcp60.dll
msvcp71.dll
msvcp80.dll
msvcr71.dll
msvcr80.dll
I have the following softwares installed on the server.
Microsoft Visual C++ 2008 Redistributable x64
Microsoft Visual C++ 2008 Redistributable x86
WCF LOB Adapter SDK (64-bit)
BizTalk Adapter Pack 2.0 (64-bit)
BizTalk Adapter Pack 2.0 (32-bit)
The following bindings are also present in the machine.config under Framework\v2.0.50727\CONFIG and Framework64\v2.0.50727\CONFIG
<system.serviceModel>
<extensions>
<bindingElementExtensions>
<add name="sapAdapter" type="Microsoft.Adapters.SAP.SAPAdapterExtensionElement, Microsoft.Adapters.SAP, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
</bindingElementExtensions>
</extensions>
<client>
<endpoint binding="sapBinding" contract="IMetadataExchange" name="sap" />
</client>
</system.serviceModel>
Thanks,
Tarun

Have you tried this?
http://geekswithblogs.net/MoonWalker/archive/2013/07/17/could-not-load-file-or-assembly-microsoft.adapters.sap.sapginvoker.dll.aspx
Morten la Cour

XI and BC adapter

Hello
I would like to resplace our SAP Business Connector by
a XI scenario, but I am a bit confused about this is
possible or not. When replacing our BC XI will get Idocs
from R/3 and has to send these to an external BC. Further
this external BC will send Idocs to R/3 via XI. So the
scenario would be like this:
R/3 -> XI -> BC
and
BC -> XI -> R/3
As already mentioned above XI has to send and will receive
Idocs by R/3 and BC.
But in several postings in this forum I have read that
this will be not possible, because the Idoc-XML is not
supported. In the 'FAQ XI 3.0 BC Adapter' (SAP note
774854) there is also written that just RFC-XML will be
supported
Although in XI Configuration Builder I can select Idoc-XML in the receiver and sender adapter.
And finally the are 2 different SAP Help pages with 2
different statements regarding this issue:
http://help.sap.com/saphelp_nw04/helpdata/en/ed/319640c80b3528e10000000a1550b0/content.htm
and
http://help.sap.com/saphelp_nw04s/helpdata/en/ed/319640c80b3528e10000000a1550b0/content.htm
(this makes the difference: help.sap.com/saphelp_nw04s )
So, what is right and what is wrong?
In the case that the BC adapter does not support Idoc-XML. Is there any other solution?
Thanks in advance
Thomas

Hi
Purpose
The SAP Business Connector adapter (BC adapter) supports the B2B protocol of the SAP Business Connector, which is based on HTTP. The BC adapter enables you to replace a business connector with SAP Exchange Infrastructure or the PCK in scenarios where several SAP Business Connectors are used. This ensures guaranteed message delivery by SAP XI.
The Business Connector is a point to point solution that provides messaging and routing. Currently a number of organizations using the Business Connector utilize it to communicate between its partners using XML based messaging. This can be achieved using SAP XI as well, but SAP's strategy is to utilize XI as a central hub for messaging, routing, and communication between all SAP, non-SAP systems as well as partners. As SAP XI is a relatively new solution, organizations that are looking for communicating with their partners to exchange XML based documents or other point-to-point scenarios can still utilize SAP Business connector.
Hoe to used in sap xi:
http://help.sap.com/saphelp_nw04/helpdata/en/6a/3f93404f673028e10000000a1550b0/content.htm
Business connector --
WAS - Business Connector
business connector documentation
SAP Business Connector
Business connector
Will Business Connector 4.6 be affected by new Daylight savings changes
Business connector
More info on XI can be found at https://service.sap.com/xi
Hope this is usefull
Thanks
Saiyog

FDQM and SAP Adapter

Similar Messages

Maybe you are looking for