Business Connector Scenario .

Hallo ,
I have been given a scenario, where SRM sends a PO sheet in XML format to BC.I have to map some elements of the XML to the elements of client's application.
They require the xml to be ftp ed to FTP server, from there it's used for application.
My questions:
1) Where can i find the XML file which is sent by BAPI from SRM system.
2) Is just mapping enough ?? and what are the services available for this task.?
3)Service used for FTP and from there how to map to application of client??
Thanks in advance for all ...for your help
Srini

hi,
>>>>1) Where can i find the XML file which is sent by BAPI from SRM system.
did you try with SRM content for business connector ?
>>>>3)Service used for FTP and from there how to map to application of client??
pub.client.ftp:put
>>>>2) Is just mapping enough ?? and what are the services available for this task.?
depends on what your client's application expects
maybe you will need to do some lookups etc <-- you need to find out
Regards,
michal

Similar Messages

To migrate SAP business connector scenario to SAP XI.

Hi,
I want to migrate my IDoc-http sap bc scenario to sap xi.
1:What the basic things do i need ?
2:what basic steps do i need to perform to migrate a sap bc scenario to sap xi?

Hi Shewta,
from a BI perspective, please check the HowTo-Papers available in this area.
You find them at:
<a href="https://websmp202.sap-ag.de/~form/sapnet?_SHORTKEY=00200797470000073641&_SCENARIO=01100035870000000202">SAP Service Marketplace HowTo guides</a>
Cheers
SAP NetWeaver 2004s Ramp-Up BI Back Office Team

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.

Query Related to Business Connector

Hi,
I'm currently working on Business Connector, which is new to me. I am going through the reference documents to understand the working of the same. However, the requirements have started pouring in.
As of now, I have the follwoing requirement.
I've a SAP Function Module say "Z1234" which is RFC enabled. To this FM, all export paramets which are passed are FIELDS, none are table(s).
Now what i require is to fetch this data into Business Connector by writing some code in Business Connector whose FRONT END is JAVA.
Can anyone in here help me to achieve this requirement?
Suggestions welcomed.
Thanks & Regards,
Rajesh

HI,
I think Scenario based is better
1) It's more reasonable to manage your documentation with the business process since they are quite related
2) I suggest that you use the check out /check in functionnality to prevent the modification from multiple users at the same time
3) As the changes happen some time, which means you have to maintain the related document often, it would be a good idea to use the link but not the copy of document
4) In most case, i would insert documents of various types in different tabs like Trainning materials, project documentation, test in SOLAR02
5) What's more, if all your user guides are uploaded to the Trainning material tab, you will be able to use the existant documents to supply the SOLAR_LEARNING_MAP, which in my opinion, simplifies a lot the tranning session of any global-rollout
Jiamin Pan

Delta between Business Connector 4.8 and 4.7

This seemed like the most logical place to put my post so here it goes..
We are assessing our options for replacing/upgrading existing Business Connector installations that will shortly be out of support (OSS Note 571530).Whilst researching our options I have come across OSS Note 1094412 which describes a new version of 4.8 becoming available in July 2008.
Information on BC4.8 is virtually non-existent on the web - can anyone provide me with details of the delta between 4.7 and 4.8, licensing structure, hardware requirements, support/maintenance strategy and ease of migration from 4.6/4.7 to 4.8?
As an aside it is very interesting that SAP has chosen to provide BC 4.8, presumably to ensure BC can continue to runs on supported O/S' and Java environments, when SAP XI/PI is being touted as the de facto integrator for companies with a significant SAP presence. Maybe customers are not quite as keen to move on/remove their BC instances as SAP would hope...

Hi Daniel,
We have been on this topic for years (some vested interest through product development).
What seems to have happened, from what we can gather, is that Netweaver XI/PI uptake hasn't happened as fast as initially hoped (SAP was looking at an intial end of life of Dec 2004 for BC).
The case is quite simple. BC is free, easy to install and maintain. XI/PI, new product, takes a while to stabilize, much more feature rich, but at the same time more complex and less performing (and did I mention the license cost?).
What we know about BC 4.8 and this is purely based on talking to people and reading about it, we have not seen / tested BC 4.8 ourselves - Mainly a platform upgrade, no significant changes. Most likely free as well (the original contract states that if SAP charges money for BC they have to pay extra to Webmethods / Software AG) accordingly. I would expect to see a few new built-in function and hopefully some hooks into standard SAP monitoring tools.
I think you hit the nail on the head. We have seen customers panic and move to non-Netweaver platforms from BC to be on a supported solution (back when EOL was imminent before 4.8 was released). Why non-Netweaver? Because many customers use non-SAP Integration Products as well and they tend to drift to known solutions instead of trying to manage the risk of migrating to a unfamiliar product.
I would not expect any major changes that would make migration to 4.8 hard. If there would be some major issues then that would signal some significant developments from SAP and that would be a strange thing at this point of the product lifecycle.
End of life for BC 4.8 is in 2012 or thereabouts if I remember correctly, this was part of some note which was released/updated towards the end of last year.
You might want to make some design calls if you continue developing your integration scenarios on BC. The best format to allow for an easy / relatively painfree migration to PI one day is by using BC graphical MAPS where possible, NOT XSL maps as wrongfully indicated in so many previous posts and articles. XSL is the hardest format to migrate to PI even though it might look superficially as a compatible format...
Cheers
Kalle

SAP XI over Business connector

Hi All,
As everyone is aware that SAP Business connector is no longer supported by SAP and XI has replaced it in quite many places.
I would like to know the advantages of XI replacing Business connector in a project scenario.Also any disadvantages that XI still has over BC?
I would like to have the reply in detail as this is required for suggesting XI as a replacement for BC.Also the cost benefits highlighted would be of great help.Inputs for this query would be highly appreciated and rewarded.
Thanks in advance!!

Hi Ramya & others,
we at Lost Bearings International have brought the BC2XI(TM) to the market and together with partners delivered successful migrations to XI using it as the underlying platform.
We are currently working on Version 2 of the migration platform to allow for a more scalable use for 100+ BC project migration scenarios at larger customer sites as well as a more generic migration process which will assist in migrations from other EAI platforms to XI on top of the current BC to XI one.
Best way find out more is to contact us directly through http://www.lostbearings.com/exponent/index.php?section=3 and we can discuss the evaluation steps to give you an idea about cost & time savings you can achieve through the BC2XI service offering.
Unfortunately the information on http://www.bc2xi.com is a bit outdated at the moment, but this should be updated in the near future.

Business Connector 4.7

Hi,
I am SRM Consultant and not so specialized with XI or Business Connector.
I am working with a customer on SRM 4.0 / CCM 2.0 / Business Connector 4.7 ( standalone scenario ).
We need to have "contract catalogs" in our system ( CCM 2.0 )
So it is important that our contract data in SRM 4.0 will be changed into XML and send to CCM 2.0 Catalog.
This should be done by Business Connector 4.7
I know, that this works with XI - because there appears a flag " Distribute to Catalog" in SRM 4.0.
But how could this work with Business Connector?!
Would be glad, if someone could give me a hint.
Thanks and Regards,
J.H.

Hi,
I know that Business Connector is antiquated - but the customer works with that.
XI seems to be the future - but it is expensive too.
So - I´ve to find out how it works.
I think I will try to find an BAPI, which mapps the data into XML and send it to BC.
Can anybody tell me what is a "BAPI Driver". I found some of this and they all call up the Business Connector.
Best Regards
J.H.

Corefix 7 in Business connector 4.7

Hi,
Can anyone gimme a description of corefix 7 in business connector 4.7,what it would fix/give us in BC.
or is it related to basis?
Please clarify.
Regards,
ramya.

Hi Ramaya,
I am currently working on BC 4.7.
I have established one HTTP to IDoc scenario.
I want to know more about XSLT mappings in BC.
What is it's structure?
How we can use it in this scenario?
Can you please help me?
Waiting for your reply.

Transport business connector service.......Urgent

Hi Experts,
The scenario is i am sending IDOC from SAP to SQL and SQL sends data for confirmation of Purchase order in SAP.
For this i have 2 services in business connector. Things are working fine and i am at the stage of transporting the object to PRD.
The problem is, I used an existing Package to create these 2 services.and for these services i created a

HI,
See the below links
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
and webAS on http://help.sap.com/saphelp_nw04/helpdata/en/f3/e20f3adfd0a706e10000000a114084/frameset.htm
Check this also-
http://help.sap.com/saphelp_nw2004s/helpdata/en/6f/1bd5c2a85b11d6b28500508b5d5211/frameset.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b4f3755a-0401-0010-b6b3-9b65bb7d4503
Regards
Chilla

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).

Receive XML with Business Connector, convert to IDoc

Hi all,
I am trying to receive XML files with SAP Business Connector (4.7) and convert them to IDOC and then forward the IDoc file to SAP System.
At the moment, I have to do the testing for this.
I don't know how to send the XML file to the special port (5555) of the server. I read that there are serveral possibilities like http, mail, ftp. Can anybody give me an advice how this works?
Next problem is to get the created IDoc file to the SAP system. The SAP server is added in the SAP Business Connector and the connection works.
I would be very pleased if anybody could help me.
Thanks in advance!
Kai

hi,
What i understand from your scenario is XI> BC> SAP system.
1)XI-->BC
U need to configure XI's-BCAdapeter(as receiver).
in URL specify teh follwoing :
http://<hostname>:5555/invoke/folder1.folder2./<service-to-be invoked>
together with the username and password.
2) BC--> SAP
To invoke an IDoc, go to Routing rules and specify the sender, receiver, and the Message Type(IDoc name). In the next page, specify the name of the flow service to be created. and the Flowservice to be invoked whenever a message comes in.
Hope this gives you some input.
Regards,
Siva Maranani

Business Connector Limitations

Hi,
My client wants to use business connector for mutual transfer of the EDI Documents with their customers. For some reason, they dont want to go with XI.
Just wanted to know if there are any limitations with SAP Business Connector? Would it be able to meet all the EDI requirements? What are the scenarios in which the Business Connector would fail?
Thank you in anticipation.

One of the options is to use JOLT.
Using Jolt will enable your Java application or applet to talk with Tuxedo
services in the backend. The Tuxedo service in your case could be the
Elink service, which will connect with your SAP application.
Please check out the latest Jolt documentation or consult BEA Jolt experts.
Baijun Lee
[email protected]
Tuxedo Consulting Service is available.
"Lakshmi Muralidharan" <[email protected]> wrote in message
news:3a405f54$[email protected]..
>
Hi,
We are in the process of web enabling our existing SAP application. Whatwe have right now is a jsp that invokes a BC(Business Connector) service
which calls a SAP function module.But since we have limitations with
Business Connector, we plan to replace the BC service with Elink service.
Now how to invoke the Elink service from my java application? If I have to
create a Tuxedo application for this, is Java version of Tuxedo ATMI
available? How to proceed? Please help.
>
>
Thanks
Lakshmi

Corefix 7 in SAP Business Connector 4.7

Hi,
We are currently using sap business connector version 4.7.we have 2 systems production and test,where in our production system is at Corefix 5 and test system is at Corefix 6.
I need to know what are the patches and fixes provided by Corefix 7 in business connector,also a comparison with other corefixes.
Thanks in advance!!
Regards,
Ramya

Hi Ramaya,
I am currently working on BC 4.7.
I have established one HTTP to IDoc scenario.
I want to know more about XSLT mappings in BC.
What is it's structure?
How we can use it in this scenario?
Can you please help me?
Waiting for your reply.

PI 7 to SAP Business Connector Connectivity

Dear Gurus,
I have to connect our ECC 6.0 System to another ECC 6.0 System using B2B scenario. For B2B purposes we are using PI 7 while the other party is using SAP Business Connector (SAP BC) as it's front-end-tool for ERP-to-ERP connectivity. I am a Basis Consultant and I have been given the task of doing this connectivity. I have never worked on any business connector. Can anyone guide me in this? We do not have any PI Consultant
Also advice what infrastructure will be needed to complete this connectivity
Request you all gurus to kindly advise asap
Best Regards

Well, a PI consultant would be a better choice as you will have to learn some basics before you can implement your project. PI is not an easy system as business connector and it requires deeper skills and expertise on the tool, but with some effort, certainly you can do it yourself.
I do not have any experience on the administration of a dispatcher, so I cannot guide you on that subject. But after achieving the connectivity between the two dispatchers, the rest is the PI development task.
It seems that your scenario is not really a hard one. Play around with the tools(in PI) and try sample scenarios to get used to it. Here are some for your convenience:
And the PI (formerly called XI) library that covers almost everything is here:
http://help.sap.com/saphelp_nw2004s/helpdata/en/0f/80243b4a66ae0ce10000000a11402f/frameset.htm
With the help of the documentation and the sample scenario blogs, you will be able to develop your scenario. But gathering the required skill will take about a month or so, depending on your performance.
After learning the basics, you also need to work on monitoring, alert definitions, going live pratice etc. also which you can also find examples in the blogs. Furthermore, if the messages exchanged are to be changed before reaching the ERP on the PI side, you will also need some mapping practice. Here are two blogs which will teach you graphical mapping in PI:
/people/sravya.talanki2/blog/2005/08/16/message-mapping-simplified--part-i
/people/sravya.talanki2/blog/2005/12/08/message-mapping-simplified-150-part-ii
A B2B scenario can be partly auto-configured after definition of relevant integration scenario in the Integration Builder so it might be a good idea to learn it. I'm assuming you don't need any business processes(which automates A2A and B2B processes, for example a full order-to-cash scenario involving many systems and communications with business logic), so you will mostly need configuration instead of development. You also won't need any ABAP or Java skills in your case.
The content on SDN about PI is pretty rich so I don't think you will be short on examples and instructions. Just search when you need something, almost every aspect is covered by now.
Hope these are useful, feel free to ask anything you may need.
Regards,
Gökhan

SAP Business Connector : Simple Test

Hi Folks,
Before I start , let me mention here that I am completely new to BC . And my requirement (I think) is also very simple.
I have installed the business connector developer in my pc , and the BC server connection to SAP server is also working alright.
My requirement is very simple , I want to pass a XML document to sap server . It is just a simple test as I am not going for any middleware setup etc.
I just want to send this XML document to SAP for testing . I have tried by creating a "Flow" which expects a XML document but somehow it does not seem to work .
Kindly let me know if possible the manual steps for sending XML doc to SAP.
Thanks in Advance....

You may use the standard developer's guide example to configure your scenario.
Suppose you have File to RFC scenario.
1. First create a structure for file system. This should be created as a Record in BC. Import the RFC structure too in BC.
2. There is a standard ftp service (I guess in WmPublic package) which should be the first flow step of your flow service.
3. Then use map steps to map the Records of file structure and Idoc.
4. Then you may use imported RFC flow step to call RFC.
5. At server, you need to define to routing rule from SAP BC -> R/3.
Regards,
Prateek

Business Connector Scenario .

Similar Messages

Maybe you are looking for