Business Connector Combine MATMAS & CLFMAS

Hello.
I'm wondering what's the best way to combine a matmas and clfmas in business connector 4.7?
Is there a way only sending 1 idoc from sap with the matmas+clfmas content? This would eliminate my combination problem in business connector.
sorry for posting this in th xi forum but i don't see where to put my question else.
rgds,
jeroen

Jeroen,
In SAP you can send out both MATMAS and CLFMAS. You have to set the "Send material in full" check box. You will need to have both MATMAS, CLFMAS and DOLMAS in your partner profile.
You can ignore the DOLMAS.
You then should have both IDocs in SAP BC (you may need to set the packet size to get them together).
If not build your self a simple queue by using the repository store and storing the first IDoc using the link (MATNR) as the key.
Regards,
Simon

Similar Messages

Business connector server on Virtual Server

Hi,
Currently our 4.6 release Business Connector servers running on Windows NT Operating system. We would like to upgrade them to BC release 4.7 on Windows 2000 operating system on Virtual servers.
Are there any known issues/disadvantages if we install Business connector servers on Virtual Server rather than a Physical server?
These virtual servers will be in the same domain as that of SAP systems. Host names of the upgraded Virtual servers will be same as the current production BC hosts.
Thanks,
Srini

Technical Data
These functions are:
Changed, new, deleted
For Release
   Software Component
·        Component: SAP Business Connector (external)
·        Release: 4.7
Assignment to Application Component
BC-MID-BUS (SAP Business Connector)
Country Setting
Valid for all countries
Use
The following information provides you with an overview of the new features in SAP BC Release 4.7: It also tells you about incompatible changes that you need to know about before performing an upgrade.
SAP BC 4.7 is based on Integration Server 4.6 from webMethods. However, the SAP BC elements in Integration Server 4.6 have been redeveloped (see below for details).
Features
Additional Functions in SAP BC Developer
As well as SAP BC Administrator GUI, you can now use SAP BC Developer to perform typical development tasks. You do not need administrator authorizations in SAP BC Developer to do this. For example, with SAP BC 4.7 you can use SAP Lookup to generate elements for the Developer. This enables you to gather information about function modules, structures (tables), BAPIs and IDocs in an SAP system, and then generate outbound maps or records for these objects directly.
SAP BC Developer contains a new menu, SAP, which contains the following functions:
·        Look up a function module and generate an outbound map
·        Look up a structure definition and generate a record.
·        Lookup a business object.
·        Look up an IDoc and creating a Record.
·        Browser for Function Maps.
In addition, the Developer now also supports the following actions:
·        Generate an SAP inbound map if you want an SAP system to run a service in SAP BC.
·        Generate an SAP outbound map to execute a function module in an SAP system.
·        Generate a record based on an SAP ABAP Dictionary structure.
·        Generate a record based on an SAP IDoc.
SAP BC Developer now also supports a proxy bypass list. This means that you no longer need to define whether a connection runs through a proxy; instead, the bypass list performs this task.
New Public Services on SAP BC Server
pub.string:gzip
Compresses the specified input string and generates a check total (optional). For measurements or for statistical purposes, the lengths of the zipped and unzipped strings are provided as output.
·        pub.string:ungzip
Decompresses a specified input string, which was compressed with pub.string:gzip, and verifies the check total (optional).
·        pub.string:numericParse
Analyzes a number in accordance with a given number pattern.
·        pub.math:randomLong
Generates a pseudo random number and sends its string representation in a pipeline variable. You can use this number as a universal identifier with an acceptable level of security, as long as it is used in non-distributed scenarios and for a small number of variables.
·        pub.file:head
Shows the start of a given file.
·        pub.file:tail
Shows the end of a given file.
·        pub.flow:sleep
Puts the current service into sleep mode for the specified period (in seconds).
Restructuring of the WmPartners Package
The WmPartners package in SAP BC Server has been completely restructured and now offers the following enhancements:
·        Improved status information in the messages displayed in the Transaction Store and the Audit Log. This solves a range of problems, such as incorrect status information being displayed by IDocs.
·        Improved search and sort options for transactions in the file system of the Message Store. In the Transactions menu, SAP BC Administrator GUI offers you a new option, Message Store Query Settings, which enables you to select and delete transactions. In Release 4.7, the Message Store can also be displayed on separate pages, which makes it easier to edit large numbers of transactions.
·        Improved search and sort options for Routing Rules. In the Routing Rules menu, SAP BC Administrator GUI offers you a new option, Routing Rule Filter Settings, which enables you to restrict the number of routing rules that are displayed, and to sort the display. The filter accepts all combinations of characters, and the placeholders '*' (string of characters) and '?' (one character). This makes it easier to sort and search for routing rules, especially if you need to process a large number of communication partners and message types.
·        Forwarding the "Confirm Event" tRFC (triggered by an SAP system) to the next receiver (for the following transports: B2B Service, ALE (R/3 IDoc), and XML (only if another SAP BC is the receiver)) and triggering "Confirm Event" from an external client. Both of these cases can be significant if the final receiver is an SAP system. In this case, "Confirm Event" removes the transaction ID from the ARFCRSTATE table, which can improve system performance significantly when a large number of tRFCs are being processed.
Support for Distributed Statistic Records (DSRs)
SAP BC has supported the generation of DSRs since Release 4.7 DSRs enable you to monitor the performance of each SAP system and its components. In this way, you can check how much system load is produced by each individual component, and how many resources are being used. This enables you to identify "performance leaks" and optimize system performance.
The DSR support integrated in SAP BC also allows you to measure the total retention period of a process in SAP BC. To evaluate the DSRs, you require additional SAP software, including specific versions of the SAP Solution Manager, and the RFC Library. The exact requirements are still being defined.
The details will be published in SAP Note 620418. You can find a link to this SAP Note on the SAP BC download page at http://service.sap.com/sbc-download.
SAP BC Server Core Enhancements
·        Reverse Invoke
The reverse invoke protocol has been enhanced and now allows you to forward more information, such as IP addresses.
If, for example, an application fails because a connection is broken, and other working connections exist, the connection is checked using a ping.
From now on, the internal server can open or reopen a defined number of connections, if necessary.
A document is generated for any exceptions on the internal server.
·        Email Listener
New Features in the Email Listener
¡        Reprocessing of invalid mails for IMAP Server
¡        Processed mails selected as "unread" if they have not been deleted.
You can also specify whether mails with exceptions are deleted or not.
·        Update Manager
The Update Manager manages fixes and patches for the upgrade of an SAP BC Server. Previously , the Update Manager allowed a fix to set other fixes as obsolete, using the updateVoidList field in the update.cnf file of the fix. An obsolete fix is not shown in classpath, but up to now the Update Manager has not been able to give a fix in classpath priority ahead of this other fix. The Update Manager has now been enhanced to support these fix priorities: The update.cnf file in the fix now contains an updatePrecedeList field.
Incompatible Changes
SAP BC Delivery Without JVM
The Windows Version of SAP BC 4.7 is no longer delivered with a Java Virtual Machine (JVM). The SAP BC 4.7 Installation Guide describes the JVMs that are supported.
See also
For more information, see the documentation on the SAP Business Connector, under
·        http://service.sap.com/connectors (SAP Business Connector ® SAP Business Connector in Detail ® Documentation).

SAP Business Connector on Windows XP

I've been trying to get the SAP Business Connector 4.7 to work on Windows XP professional but haven't been very successful. The business connector seems to install okay, but when I try to start the business connector through the server.bat file it generates the following errors:
(loglevel = 4)
Loading WmPartners package
00000E [B2BSERV.0026.0002] Failure while loading service wm.PartnerMgr.gateway.transport.EmailTransport:startup: [B2BSERV.0026.9106] No method startup in class wm.PartnerMgr.gateway.transport.EmailTransport
00000F [B2BSERV.0026.0002] Failure while loading service wm.PartnerMgr.xtn.admin:saveMessage: [B2BSERV.0026.9106] No method saveMessage in class wm.PartnerMgr.xtn.admin
000010 [B2BSERV.0026.0002] Failure while loading service wm.PartnerMgr.xtn.admin:view: [B2BSERV.0026.9106] No method view in class wm.PartnerMgr.xtn.admin
000011 [B2BSERV.0026.0002] Failure while loading service wm.PartnerMgr.gateway.admin:saveRoutingRule: [B2BSERV.0026.9106] No method saveRoutingRule in class wm.PartnerMgr.gateway.admin
000012 [B2BSERV.0026.0002] Failure while loading service wm.PartnerMgr.gateway.admin:convertWildCards: [B2BSERV.0026.9106] No method convertWildCards in class wm.PartnerMgr.gateway.admin
000013 [B2BSERV.0026.0002] Failure while loading service wm.PartnerMgr.gateway.transport.B2B:startup: [B2BSERV.0026.9106] No method startup in class wm.PartnerMgr.gateway.transport.B2B
000014 [B2BSERV.0026.0002] Failure while loading service wm.PartnerMgr.xtn.admin:editStore: [B2BSERV.0026.9106] No method editStore in class wm.PartnerMgr.xtn.admin
000015 [B2BSERV.0026.0002] Failure while loading service wm.PartnerMgr.gateway.transport.FTPTransport:startup: [B2BSERV.0026.9106] No method startup in class wm.PartnerMgr.gateway.transport.FTPTransport
000016 [B2BSERV.0026.0002] Failure while loading service wm.PartnerMgr.xtn.admin:invokeViewService: [B2BSERV.0026.9106] No method invokeViewService in class wm.PartnerMgr.xtn.admin
000017 [B2BSERV.0026.0002] Failure while loading service wm.PartnerMgr.xtn.admin:viewMsgContent: [B2BSERV.0026.9106] No method viewMsgContent in class wm.PartnerMgr.xtn.admin
000018 [B2BSERV.0026.0002] Failure while loading service wm.PartnerMgr.gateway.admin:updateTransports: [B2BSERV.0026.9106] No method updateTransports in class wm.PartnerMgr.gateway.admin
000019 [B2BSERV.0026.0002] Failure while loading service wm.PartnerMgr.gateway.admin:invokeService: [B2BSERV.0026.9106] No method invokeService in class wm.PartnerMgr.gateway.admin
00001A [B2BSERV.0026.0002] Failure while loading service wm.PartnerMgr.xtn.admin:log: [B2BSERV.0026.9106] No method log in class wm.PartnerMgr.xtn.admin
00001B [B2BSERV.0028.0005] Loading SAP package
00001C [B2BSERV.0026.0002] Failure while loading service wm.PartnerMgr.gateway.transport.RFC:startup: [B2BSERV.0026.9106] No method startup in class wm.PartnerMgr.gateway.transport.RFC
00001D [B2BSERV.0026.0002] Failure while loading service wm.PartnerMgr.gateway.transport.BAPI:startup: [B2BSERV.0026.9106] No method startup in class wm.PartnerMgr.gateway.transport.BAPI
00001E [B2BSERV.0026.0002] Failure while loading service wm.PartnerMgr.gateway.transport.XML:startup: [B2BSERV.0026.9106] No method startup in class wm.PartnerMgr.gateway.transport.XML
00001F [B2BSERV.0026.0002] Failure while loading service sap.bapi:encodeToFile: [B2BSERV.0026.9106] No method encodeToFile in class com.wm.pkg.sap.bapi.BusinessDocumentCoder
000020 [B2BSERV.0026.0002] Failure while loading service sap.bapi.Mapper:bapi2rfc: [B2BSERV.0026.9104] Missing class sap.bapi.Mapper
000021 [B2BSERV.0026.0002] Failure while loading service sap.bapi.Mapper:rfc2bapi: [B2BSERV.0026.9104] Missing class sap.bapi.Mapper
000022 [B2BSERV.0026.0002] Failure while loading service sap.bapi.Mapper:bapi2ale: [B2BSERV.0026.9104] Missing class sap.bapi.Mapper
000023 [B2BSERV.0026.0002] Failure while loading service sap.admin:listGatewayServices: [B2BSERV.0026.9106] No method listGatewayServices in class sap.admin
000024 [B2BSERV.0026.0002] Failure while loading service sap.bapi.Mapper:ale2bapi: [B2BSERV.0026.9104] Missing class sap.bapi.Mapper
000025 [B2BSERV.0026.0002] Failure while loading service wm.PartnerMgr.gateway.transport.ALE:startup: [B2BSERV.0026.9106] No method startup in class wm.PartnerMgr.gateway.transport.ALE
000026 [B2BSERV.0028.0005] Loading WmSamples package
000027 [B2BSERV.0028.0026] Warning: Deprecated service type (webtap) in service sample.webtap:logApp in package WmSamples
000028 [B2BSERV.0028.0005] Loading WmDB package
These errors don't stop the business connector from starting up, but the errors are not normal behaviour. When I try to start the business connector through a Windows service then I get the message "Could not start the SAP Business Connector Service on Local Computer. Error 126: The specified module could not be found".
I have a working business connector installation on a Windows 2000 server, and when I checked the error log of that installation I noticed that it had logged the same errors about the 'WmPartners' package. It on the other hand didn't have any problems loading the 'SAP' package.
I tried installing the business connector on two different systems with identical results. Has anybody been able to get the business connector to work on Windows XP?

HI,
I have no idea clearly about BC.. but ..
See the following links.. may be helpfull..
Business connector
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a8609b90-0201-0010-c6bc-a41b611c6dac
SAP Business Connector on Windows XP
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/92e5bd90-0201-0010-b799-dfdc27f3100a
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a8424011-0d01-0010-e19d-e5bd8ca52244
If usefull .. points rewarded..
Regards
Chilla..

How do we Integratet SAP to Non-SAP Using Business Connector

Hi Experts,
I am new to SAP Business Connector !!
and what are the Forms ? for SAP Business Connector Related Postings ??
!! I have a requirement to integrate sap to non-sap with Business Connector !!
We need to Generate the SAP Data In xml Format ? and the Non-sap System can Understand Only XML Formated data.
Is there any way Business Connector Box can Pull the XML file from R/3 Application Server and store the file in the Business Connector Server. from that How do we Sent XML file to Non-sap. How do we Integrate ??
what transaction code will trigger this event ? I mean is ther any SAP Transaction Code to Integrate Business Connector?
For Eg. like in R/3 SD to FICO and MM Integration.
Please Give your Valuable Suggests..
Thanks .
Upender.

Hi,
It is not an issue, It will be a separate project :-).
The right forums for this,
Expert Forums » SAP NetWeaver » Process Integration
www.wmusers.com
Also go through the following links:
http://www.sapgenie.com/interfaces/businessconnector.htm
http://www.sapgenie.com/mysap/bus_connector.htm
/people/bla.suranyi/blog/2006/07/10/xi--sap-business-connector-integration-using-the-http-adapter
http://help.sap.com/saphelp_nw04/helpdata/en/6a/3f93404f673028e10000000a1550b0/frameset.htm
http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b4f3755a-0401-0010-b6b3-9b65bb7d4503
https://websmp104.sap-ag.de/connectors
Thanks and Regards,
Chandra Madapati

Problem establishing Business Connector 4.8 and R/3 connection

Hello,
I'm currently running a few SAP Business Connectors 4.7 servers for my company, all connected to SAP R/3 4.7 backend, and everything works fine.
I tried to setup the new BC 4.8, on a fresh Windows 2003 server, the install went fine, but when I try to make a new R/3 connection, with a working and existing RFC user (previously used by the former BC 4.7), I have the following error message :
Error : class com.sap.conn.jco.JCoRuntimeException
Message : Name or password is incorrect. Please re-enter on 192.168.0.4 sysnr 00
Service : sap.admin.server:getInfo
I don't understand because if I unplug the 4.8 server and plug back the 4.7 one with exactly SAME user/password and same R/3 connection properties, it works fine...
I precise I re-typed manually the login/passwords in both BCs to ensure it's not due to a typo error.
I have read that JCO has changed between 4.7 and 4.8 releases. Could it have an impact ? Also do I still need to install a librfc32.dll in my windows/system32 directory ?
Any clues ?
Thanks in advance for your help
P.
Edited by: Patrick TOURNEUR on Jul 21, 2008 6:40 PM

Hello,
just for your info, the JCo implementation has changed about this login function. BC 4.8 is using JCo 3, 4.7 used JCo 2.
I never understood the whole problem completely, but as you found out by yourself, you are safe if you enter the user/pwd in SAP only uppercase, and also in BC
SAP changed this user/login up/lowcase stuff at some time, which has caused many trouble in projects.
CSY

NULL Value in SAP Business Connector (BC47_CoreFix7 )

Dear All,
I am working with SAP Business Connector and some times i get NULL value in (PROXY SERVER) in Secure Proxy (HTTPS) so i need usualy to remove it manully and save the changes.
Would you plesae help me to solve this issue either to delete automatically or to have any idea to prevent getting this NULL value.
Thanks in advance..
Message was edited by: Hassan Hakeem

Dear,
i need the answer ASAP pleasssssssssssse.
Thanks..
Message was edited by: Hassan Hakeem

RFC Error while trying to access function module from business connector

Hi,
I am getting the following RFc exceptions in BC server when we invoke the service pub.sap.client:invoke fail as a flow step in Idoc_Status_Add(this service is calling a function module in sap namely ZYBC_IDOC_STATUS_ADD_FROM_BC which Adds status to Idoc (from Business Connector).But no trace of failures are recorded in sap side
except 1: rfc_failure in BC trace files under monitoring.I need to know the root cause of these errors as the same services have run finely later and IDOCs were also processed successfully without any problem.
com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: See RFC trace file or SAP system log for more details
at com.sap.mw.jco.rfc.MiddlewareRFC$Client.nativeExecute(Native Method)
at com.sap.mw.jco.rfc.MiddlewareRFC$Client.execute(MiddlewareRFC.java:1217)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3684)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3129)
at com.wm.pkg.sap.rfc.SAPSession.invoke(SAPSession.java:437)
at pub.sap.client.invoke(client.java:297)
at java.lang.reflect.Method.invoke(Native Method)
at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:281)
at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:709)
at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:140)
at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:292)
at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:559)
at com.wm.lang.flow.FlowState.step(FlowState.java:430)
at com.wm.lang.flow.FlowState.invoke(FlowState.java:400)
at com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1786)
at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:709)
at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:140)
at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:292)
at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:559)
at com.wm.lang.flow.FlowState.step(FlowState.java:430)
at com.wm.lang.flow.FlowState.invoke(FlowState.java:400)
at com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1786)
at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:709)
at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:496)
at wm.server.net.EmailTransaction$RunService.write(EmailTransaction.java:1375)
at wm.server.net.EmailTransaction$RunService.run(EmailTransaction.java:1218)
at com.wm.util.pool.PooledThread.run(C:/NT/Perforce/basis/4.1.0-terra/module/core/source/com/wm/util/pool/PooledThread.java:103)
at java.lang.Thread.run(Unknown Source)
could anyone throw light on how this kind of error can be resolved and why it occured?
Thanks.

What does the RFC trace file and log say? Has there been any dump on the SAP server? Check the logs and transaction st22 in your SAP system to see if the RFC-module has dumped.
My guess is the problem is in the RFC-module, I think you should start looking there.
regards,
Dionisios

Flat File Transfer from SAP R/3 4.7 to SAP Business Connector 4.8

Hi Experts,
I have a requirement of transferring a flat file from my R/3 SAP 4.7 Box Application Server to the Business Connector 4.8 Box. I am new to SAP Business Connector and I am not to sure whether FTP works if I use a shell script in SAP R/3. Also, is there any way Business Connector Box can pull the file from R/3 Application Server and store the file in the Business Connector Server.
Any help will be appreciated!!!
Regards,
Subhhrangsu

Hi,
There are many ways thru which you can pass document to SAP BC:
You can HTTP, FTP, Email document to SAP BC.
SAP BC has predefined services for all of them.
For FTP document to SAP BC:
1 Initiate an FTP session on SAP BC Serveru2019s FTP listening port ( this can be found out from SAP BC administrator or from SAP BC homepage).
2 Point to the directory that contains the service to which you want to pass the XML
document.
Example cd \ns\Purchasing\SubmitOrder
3 Copy the XML document to this directory using the following command:
put XMLDoc.xml
Where XMLDoc.xml is the name of the file that you want to pass to SAP BC Server.
Example put PurchaseOrder.xml
Above code can be written in a batch file and you can schedule it to run at interval of minutes.
You can write java client program as well to upload file and map it to String variable of Flow service of SAP BC.
As Micheal said, you can look at sapbc/Developer/doc folder to look for more options.
Best Regards,
Divyesh

Pipeline concept in Business connector

Hi All,
I am working in Business connector 4.7, but I am finding tough to understand the SAP BC pipeline concept of defining java like services in BC.
Basically I do not have experience of Java programming and I work on pure SAP ABAP programming.
Please can any one help if they have some documents on it.
Appreciate your great help.
Thanks in advance.

Hi,
A set of services to be performed in a fixed sequence on a message.
A pipeline consists of pipeline elements that are linked to pipeline services
You have to write a java service which takes that particular pipeline
variable and writes to the file. Then in your pub.client.SMTP service you
have to specify that particular file path for attachment.
Refer
http://help.sap.com/saphelp_nw04/helpdata/en/6a/3f93404f673028e10000000a1550b0/frameset.htm
www.b41425.info/work/publications/_binary/3%20BC%20Application%20Development.ppt -
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/e29161d3-0401-0010-3495-8593de5f5da6
http://www.techboy.co.uk/misc%5CSAP%20Business%20Connector%5C4.7%5CBusiness%20Connector%5COfficial%20SAP%20Documentation/SAP%20BC%204.7%20Adapter%20Guide%20-%20SAPBCSapAdapterGuide.pdf
Thanks
Swarup

RFC function callls a SAP Business Connector Flow - only upper case

Hi everybody,
I wrote a function in SE37 which is calling a Flow in SAP Business Connector.
R/3 and SAP BC, both are Non Unicode systems.
The export parameter is TYPE makt-maktx.
The call to SAP BC works fine. Only all the text I can see in the pipeline of SAP BC is upper case.
I checked wether the domain of the makt-maktx allows case sensitive texts.
This is OK.
I have no idea how I can tell SAP BC to receive case sensitive texts.
I checked the forums. Seems nobody had such a problem.
Can somebyody help?
Best regards
Jochen
Hi to all,
it was not the JAVA Version, or a bug or whatelse.
I just ingnored while testing in SE37 that there is
a Flag [X] case sensitive - That's all!
Shame on me!
Greetings Joe
Message was edited by:
Jochen Seeliger

Hi Priya
Seeing the messages, it appears that server is down.
"java.net.ConnectException" occurs whenever you try to connect to a system which is not up and running.
cheers
Sameer
PS: Please award points if you find the answer useful

Forwarding XML/EDI from SAP Business connector to EDI (cloverleaf)

Hello,
We are having issues setting SAP up to work with the business connector and our EDI system - cloverleaf.
For testing, we would like to:
1. Create an idoc in SAP and send it to the Busness Connector.
2. Have the busness connector send the doc via XML to our EDI system cloverleaf.
Currently, I have things setup like so:
SAP/ECC6:
SM59: RFC setup as type T and works fine.
WE20: Partner Type LS:
I have 2 message types setup (in outboard: I have "orders" and in Inbound I have the same).
in WE21: I have a cloverleaf (our EDI system) to run with the RFC destination I setup in SM59.
On the Business connector, I have the following under routing rules:
From SAP to the Business connector:
Sender: 8805
Reciver: 10000000008
Message Type: Orders
ACL Group: none
Package: default
Main Flow Services: wm.PartnerMgr.flows.88605.1000000008:ORDERS
Transport: ALE (R3/IDOC)
SAP destination: RD1 (our sid).
FOR my outgoing to our EDI system cloverleaf:
I am using the sender: * - Not sure if this should be SAP or the BC.
Reciver: * - Our EDI system. our EDI system is listening on port 49001.
Message Type: Orders
Under URL (not sure about this one)
I have http://reg2lxap0725:5555/MessagingSystem/receive/BcAdapter/BC
I am however stummped on how the URL shold look..
Now, when we test the above config... I recive the following results in WE02.
0000000000003024 25 03 Green Light: IDoc Successful Green LS/ /SAPBC ORDERS05 ORDERS Outbox CLOVERLEAF
For some reason, we also have an "inbound" that fails.
0000000000003025 25 56 Red Light: IDoc Has Errors KU/ /0000088605 ORDERS05 ORDERS Inbox SAPRD1
My main question is however around routing...
We are trying to send these to our EDI system which is listening on 49001.
I am not sure how they want us to setup the routing rules to pass this over to the right port..
I have also searched the documentation, and have not found any real step by step guides, so I may be missing a few things..
Any advice to point me to the right direction is greatly appriciated....
Thanks everyone,
Richard

Hello Prateek,
Thank you very much for your answer. The AdapterGuide was really helpfull.
Now the routing rule is associated to the correct Service (that was a the problem). So the rule started to process the XML files from the folder (the XML files disappeared immediately after I corrected the rule).
But now my problem is that on the SAP side there is no inbound IDOCs so it seems the trasmission may failed.
Moreover under "Routing"-->"Transactions" I don't see these entries with the the current date.
Our routing rule is simple: "wildcard" "wildcard" "wildcard" "ALE (R/3 IDOC)"--><OUR SAP SYSTEM>
The SAP connection is working as I can test under "SAP..." menu.
Is there any other way to monitor what had happened with these XML files? I'm sure the BC processed as the files are gone, but there is no IDOC in the destination SAP...
Thanks a lot!

Error message when calling a Business Connector RFC destination from SRM

Hello all,
We are facing one problem with data Purchase Order transmission between SRM 5.0 (SRM_SERVER 5.5, extended classic scenario) and Business Connector 4.7.
We made needed customizing in order to have "XML / XI" output medium available in tab 'Company Data' in "Manage Business Partners" web transaction (by updating BBP_USE_AI table in SM30 transaction).
Then, we implemented BAdI definition BBP_EBPXML_OUT_BADI with method PURCHASEORDER in order to change XI system type to Business Connector.
In this way, PO transfer data between SRM and BC is done using BC Module Function BAPI_POEC_XML_SEND (TCP/IP RFC connection was defined for Purchase Order in BBPC_RFCDEST table).
Nevertheless, even if method BBP_PO_SEND_XML is correctly triggered when PO is created with a vendor with XML output medium, we have in the document output log ("Process Purchase Order" web transaction) an error message:
' Error (Unknown Partner and Message Type. Routing Rule created. Sender: SMR Receiver:) when calling RFC destination BC '
where SRM is the SRM log. sys. and BC the Business Connector log. sys.
Our EAI team is working on it, but if you have any idea, your are welcome !
Thank you in advance.
Regards.
Laurent

Hello Christian,
Thank you for your help. However, we abandoned this solution between SRM and Business Connector.
So, we followed instructions indicated in OSS note 883693 - "ECS: PO output determination in R/3".
Nevertheless, in order to restrict this behaviour for specific vendors and purchasing organizations, we added some filters.
It is working fine.
However, when the PO is modified in SRM, then order again, PO is modified in R/3 (by the RFC user from SRM) more than once.
As a consequence, we have as much messages as modifications of the order in R/3 (due to multiple RFC access with the SRM RFC user).
Does anybody have an idea to have only one R/3 output message when the PO is modified in SRM ?
One solution could be to check in the NAST table if the time creation of the last output message is lower than, for example, one minute.
If it is the case, we do not allow R/3 ouput message.
Any suggestions is welcome.
Regards.
Laurent.

Plugging XSLT / XML processors into Business Connector 4.7

Hi,
I need to use Xalan 2.6.0 and the associated XML parsers
in the Business Connector.
Does anyone know whether any built-in services or
SAP Adapter services would be negatively impacted by
this change? I have found nothing in the documentation.
(Among the reasons I need to do this are that the
processors in package com.inqmy.lib.jaxp do not seem to
be JAXP 1.2 compliant. Also, they neither respect the
encoding-attribute of <xsl:output>, nor allow to override
it from the outside. When generating HTML, this has
created problems for some clients).
In order to use Xalan/Xerces, one needs to set the
variable PREPENDCLASSES in server.bat to contain
the Xalan jars, and change the value of the configuration
variable watt.xslt.jaxp.properties in the server.cnf file.
The value of this variable is the name of a file in normal
Java properties syntax, which contains values for the
relevant System properties:
javax.xml.transform.TransformerFactory
javax.xml.parsers.DocumentBuilderFactory
javax.xml.parsers.SAXParserFactory
I'm using BC 4.7 SR2, Core Fix 2, JDK 1.3.1_09 under WinXP
At first glance everything seems to work fine (I can
still use recordToDocument), but I'd like to be sure.
And what about BC 4.6?
-- Sebastian Millies
IDS Scheer AG

Check out this weblog series for starters: /people/tobias.trapp/blog
Then I would suggest you post your question to the ABAP forum.

Making a call to a Business Connector Flow Service from within an ABAP prog

Hello,
I am trying to make a change to one of the flow services within BUsiness COnnector.
The way the system is currently set up is that the flow service is called from within an ABAP program via an RFC call.
A remote FM exists in SAP and this is called by the program and there is a corresponding flo service within Business Connector.
I have basically copied an existing flow service which works fine and made a few minor tweaks. Within SAP, I have copied the remote FM and again made a few minor tweaks.
However, when I run the program, it short dumps at the point whee my remote FM is called with th following message :-
"Unknown Partner and Message Type. Sender: xxxx Receiver: xxxx MsgType: "
I am not a Business Connector expert and I guess I am missing a ste but I'm not sure what it is.
Can anyone advise?
Thanks,
Ruby

Hello,
I am trying to make a change to one of the flow services within BUsiness COnnector.
The way the system is currently set up is that the flow service is called from within an ABAP program via an RFC call.
A remote FM exists in SAP and this is called by the program and there is a corresponding flo service within Business Connector.
I have basically copied an existing flow service which works fine and made a few minor tweaks. Within SAP, I have copied the remote FM and again made a few minor tweaks.
However, when I run the program, it short dumps at the point whee my remote FM is called with th following message :-
"Unknown Partner and Message Type. Sender: xxxx Receiver: xxxx MsgType: "
I am not a Business Connector expert and I guess I am missing a ste but I'm not sure what it is.
Can anyone advise?
Thanks,
Ruby

JCO Timeout for SAP Business Connector 4.7

Environment :
Windows 2000, SAP Business Connector (BC) 4.7
General Description :
SAP BC is used to invoke BAPI's in the SAP R/3 system.
Issue :
Some BAPI's are taking some time to return response depending on user load. Need to provide a timeout for RFC calls invoked by SAP BC using JCO.
Following is the entry in the rfc trace log file when BC starts up ...
000000 -
2005-05-12 11:07:20 EDT
000001 [B2B-SAP.0011.0001] [JNI-LAYER] RFC.nativeSetTraceLevel()                with rc = RFC_OK   leave, [SUCCESS]
000002 [B2B-SAP.0002.0022] Log level set to 10
000003 [B2B-SAP.0002.0025] Registered SAP package trace with core trace
000004 [B2B-SAP.0002.0014] Starting SAP services
000005 [B2B-SAP.0011.0001] [JAV-LAYER] JCO.setProperty(jco.jdsr.comp_name, SAP BC server0023 5555)
000006 [B2B-SAP.0003.0001] Loading native libraries
000007 [B2B-SAP.0003.0002] JCO version: 2.1.4 (2004-10-20) sapjcorfc 2.1.4 (2004-10-20)
000008 [B2B-SAP.0003.0004] jRFCLibrary info: 2.1.4 (2004-10-20)(C:\sapbc47\Server\packages\SAP\code\libs\sapjcorfc.dll)
000009 [B2B-SAP.0003.0003] RfcLibrary version:
This RFC library belongs to the SAP R/3 Release *** 640,0,41 *** MT-SL
Versions of SAP internal libraries:
dptr:    2
ni :   37
cpic:    3
rfc :    3
00000A [B2B-SAP.0011.0001] MiddlewareRFC.setProperty(jco.middleware.wait_for_request_time, 1)
00000B [B2B-SAP.0002.0016] Loaded SAP server configurations
00000C [B2B-SAP.0002.0015] SAP services started
00000D [B2B-SAP.0011.0001] [JAV-LAYER] JCO.Client.setAbapDebug(false), current state false
00000E [B2B-SAP.0011.0001] [JAV-LAYER] JCO.Client.setTrace(true), current state false
00000F [B2B-SAP.0011.0001] [JAV-LAYER] JCO.Client.setAbapDebug(false), current state false
000010 [B2B-SAP.0011.0001] [JAV-LAYER] JCO.Pool.setMaxWaitTime(30000)
000011 [B2B-SAP.0011.0001] [JAV-LAYER] JCO.Pool.setConnectionTimeout(600000)
000012 [B2B-SAP.0011.0001] [JAV-LAYER] JCO.Pool.setTimeoutCheckPeriod(30000) on pool SERVER-300&USER_RFC&300&EN
000013 [B2B-SAP.0011.0001] [JAV-LAYER] JCO.PoolManager.addPool:
      name = SERVER-300&USER_RFC&300&EN,
      connection = USER_RFC|300|EN|AS=[11.12.7.296|00|]G0|,
      pool_size = 10,
      max_wait_time = 30000,
      pooled_connection_timeout = 600000,
      timeout_check_period = 30000
000014 [B2B-SAP.0005.0003] Pool changed: SERVER-300&USER_RFC&300&EN containing 0 connection(s)
007E72 [B2B-SAP.0006.0001] Executing invoke for ZBAPI_TEST_Service on SERVER-300
007E73 [B2B-SAP.0011.0001] [JAV-LAYER] JCO.Client.execute (ZBAPI_TEST_Service) on handle [2]
Questions :
   1) Is there a SAP BC configuration parameter for RFC execution timeout ??
   2) Any other way of enforcing the RFC time out ??
   3) If there is a way to set timeout on JCO.Client.execute method ??
I really appreciate your help !!

I have tried changes the connection timeout value but if doesnot affect the time RFC. Following is from SAP BC adapter guide ..
Delay (minutes) until an unused connection to a SAP
System is timed out (default: 5)
I think I need similar setting as that for RFC connection !!

Business Connector Combine MATMAS & CLFMAS

Similar Messages

Maybe you are looking for