BI-IP with non SAP environment

Hi,
How is BI-IP suitable for Planning , Budgeting and Forecasting with non-SAP environment?
Regards,
UR

Hi UR,
BI-IP works on top of BI (datawarehouse). If you mean load data from non sap into BI and then plan with IP, it can be a good solution, if you mean plan data outside BI it is not possible.
br
Michele

Similar Messages

How to integrate the portal system with non-sap system

Hi Gurus,
How to integrate Portal system with non-SAP system?
I know few ways .......Using Usermapping UIDPW method.
Using Appintegrator .....and using Business repository objects in JCA?
Is there anyother way to integrate if so please give me the names and steps for integrating it?
Thanks in Advance,
Dharani

Hi Dharani,
You can get information from the following links:
http://help.sap.com/saphelp_nw04s/helpdata/en/43/d08b00d73001b4e10000000a11466f/frameset.htm
https://www.sdn.sap.com/irj/sdn/thread?threadID=744043
SAP CONNECTORS:- Basically Connectors are like middlewares , that we use to connect to the backend system including Non SAP systems also. Will try to explain it to u with some examples of SAP Connectors:-
a) SAP Business Connectors:-
A middleware application based on the B2B integration server from webMethods.
The SAP Business Connector enables both bi-directional synchronous communication and asynchronous communication between SAP applications and SAP and non-SAP applications.
The SAP Business Connector makes all SAP functions that are available via BAPIs or IDocs accessible to business partners over the Internet as an XML-based service.
The SAP Business Connector uses the Internet as a communication platform and XML or HTML as the data format. It integrates non-SAP products by using an open, non-proprietary technology.
b) SAP Java Connector:-
SAP Java Connector (SAP JCo) is a middleware component that enables the development of SAP-compatible components and applications in Java. SAP JCo supports communication with the SAP Server in both directions: inbound calls (Java calls ABAP) and outbound calls (ABAP calls Java).
SAP JCo can be implemented with Desktop applications and with Web server applications.
SAP JCo is used as an integrated component in the following applications:
1) SAP Business Connector, for communication with external Java applications
2) SAP Web Application Server, for connecting the integrated J2EE server with the ABAP environment.
SAP JCo can also be implemented as a standalone component, for example to establish communication with the SAP system for individual online (web) applications.
To Know more go through,
SAP Java Connectors
II) ALE Concept:-
ALE is not restricted to communication between SAP systems, it can also be used for connecting SAP Systems to non-SAP systems.
By using IDocs as universal information containers, ALE can reduce the number of different application interfaces to one single interface that can either send IDocs from an SAP system or receive IDocs in an SAP system.
SAP certified Translator Programs can convert IDoc structures into customer-defined structures.
Alternatively, the RFC interface for sending and receiving IDocs can be used in non-SAP systems.
In both cases you need the RFC Library of the RFC Software Development Kit (RFC-SDK).
This link gives a great insight into landscape for Connectivity to Non-SAP systems:-
SAP to Non-SAP systems
III) Communication Between SAP Systems and External (Non-SAP) Systems using RFC:-
When you use RFC for communication with an external (non-SAP) system, you can also implement the SAP Java Connector or the SAP .Net Connector for the conversion of data. However, there are no specific security requirements for these components, since they only perform internal system conversion functions.
The additional security recommendations for communication with external systems in this section make particular reference to cases where an external system is used as a server (SAP calls the external system). If you use an external system as a client (the external system calls SAP), the appropriate SAP-specific security mechanisms are implemented on the SAP side.
This link explains in detail all the security considerations you need to take for connecting to an External Non SAP system like, User administration, Network Security etc.
Communication Between SAP Systems and External (Non-SAP) Systems using RFC
Hope this helps,
Regards,
Rudradev Devulapalli
Reward the points if helpful

Ale master data scenario integration with non sap syetem i.e seebeyound

hi
we have a business process scenario integrating with non sap system (i.e seebeyound)
action code      itemnumber    plant code
a(add)          material1     plant 2
d(delete)       material 3    plant 6
etc
we have upto one million materials assigned to 300 plants
we have to send all the above data to non-sap system (see beyound)
should we go for a custom idoc and setup the rfc configuration for the two sytems.
or can you please help how to go for this scaneriao

this is not one time.it is on daily basis.
please look at this scenario.what i need is how should i go for ale/idoc scenario for this one
Business case for Heiler Part/Plant Interface:
A key function of the Heiler PBC tool is to provide users a choice
between a "Global Catalog View" (e.g. all parts in the catalog) or a
"Local Catalog View" (e.g. the subset of parts in the catalog that have
a Material Master established for the user's plant in SAP). The "Local
Catalog View" is the default condition and encourages users to procure
parts that are on contract for their plant and potentially already
stocked as an inventory item at their plant. Parts that are not in a
user's "Local Catalog View" can only be procured as a spot buy purchase
order, requiring processing by a buyer.
The new Part/Plant interface is required in order for the Heiler PBC
tool to provide this "Local Catalog View" function. The Heiler
Part/Plant table will document what plants in SAP have a Material Master
record established for each part. SAP will maintain the Heiler
Part/Plant table using this interface. When a user performs a part
search in the Heiler PBC tool, the Part/Plant table determines if a part
is included in the user's "Local Catalog View".

IDoc adapter with Non SAP systems

SAP XI 3.0 help says:
You can use the IDoc adapter to connect SAP systems (as of release 3.1) and non-SAP systems with the Integration Server using native IDoc structures
What does this mean?
-Naveen.

Hi Naveen,
Let me give a use-case in one of our projects ....we have 2 middlewares in our landscape...webmethods and XI...and in one particular instance there was a need to send an FI IDoc from webmethods to XI and forward it to R/3....
In this case, the webmethods was treated like any other sap system for receiving IDoc into XI(with settings in IDX1)...
Hope this might clarify a little bit...
Thanks,
Renjith

Http communication with non-sap system

Hi ,
We have a requirement to send OM related data to a non-sap system using HTTP post in XML format and receive the response from that external system. We are on ECC 6.0 and we cannot use XI at this time.
What would be the correct approach to do this? I read that we could use ICM for HTTP communication am I on the right track?
Thanks

Hi ,
We have similar type of requirement, if you have the solution then let me know .
Thanks in adv
Vishnu

Non-XI HTTP Communication with non-sap system

Hi ,
We have a requirement to send OM related data to a non-sap system using HTTP post in XML format and receive the response from that external system. We are on ECC 6.0 and we cannot use XI at this time.
What would be the correct approach to do this? I read that we could use ICM for HTTP communication am I on the right track?
Thanks

What setup do we need for this ?
We are on ECC 6.0. I am trying to run the program, I am getting http_communication_failure = 1 in the receive function.
I am not sure if I am missing any authorizations/setup.
Thanks for your help.
VV

How BAPI communicates with Non-SAP

How a BAPI can communicate to non-SAP system? How to create one?

BAPI communicates woth Non-SAP systems using RFC.
RFC is very relative term in SAP they call it RFC, in other technology it can refered by a different term.
The basic meaning of these terms is to communicate between two system in there binary form. It simply means that you can use the functionality of Microsoft Word, spell check for example without even knowing the code of it. Microsoft call it ActiveX technology.
Even in Micosoft Visual Basic you need to follow some rule to make an application ActiveX enable so that its functionality can be reused in binary form. It similar to the restriction which we follow in SAP to make a function module RFC enabled.
One more example, in java you can use the functionality of a code once you have the class file of it. You do not need its source code, Its called Byte code.
SAP release class libraries for each type of platform (C, C++, Java, ActiveX) so that you can use those and make RFC calls. Here is the link for it
[http://help.sap.com/saphelp_46c/helpdata/de/77/39594b622f11d2804b00c04fada2a1/content.htm|http://help.sap.com/saphelp_46c/helpdata/de/77/39594b622f11d2804b00c04fada2a1/content.htm]
You can make a sample application in Excel Macro to call a RFC in SAP, see following link
[http://sapass.metro.client.jp/Sap_Active_X/SapFunction1.htm|http://sapass.metro.client.jp/Sap_Active_X/SapFunction1.htm]
PS: this is of my best knowledgw, please correct me if i am wrong

SAP 4.7 Interface through RFC with non-sap system

We have SAP 4.7 instance and no XI and currently we are looking at following solutions using SAP connector, need following infrormation:
1. Which standard connector can be used ?
2. How Master Data to be replicated from SAP system to non-sap system( Outbound) ?
3. How Transactional data from non-sap sytem to SAP system ( Inbound)?
We need the above input considering that we don't have XI
regards

hi ,
Can you tell me which other non-sap system you are using
either it is dot net or some other
Regards
Deepak .

EDW layer as HANA for Non SAP environment

Dear All,
We would like to build HANA as EDW Layer, Would please suggest best practice , Node configuration etc
Regards,
manoj.

Hi Manoj,
I suggest you check out the material about BW on HANA on http://experiencesaphana.com.
There is no general answer, as the configuration highly depends on you data volume, update frequency, etc.
The largest single HANA server available comes with 2 TB of memory - that gives you about 1 - 1.2 TB in data storage (the rest will be used for processing the data). That doesn't sound like much, but early BW on HANA projects have seen a data volume reduction of about 1:5, so if your existing data warehouse is less than 5 TB, a single node might be an option...
If you go for a multi-node system, there's not a lot of options for landscape configuration. Just follow the [scaleout guide|http://help.sap.com/hana/hana1_imdb_scale_en.pdf]...
Not an official best practice, but personally I would say that bigger is better - so if you decide to build a multi-node landscape, I would go with XL servers...
cheers
--Juergen

Can PMI be used with non-SAP systems?

For example we have an interface that travels through several systems and servers before being fed into XI (and back).
So far as I know PMI only starts when XI picks up the message. Are there any agents, API's or any method to PMI enable other applications to send data to the central PMI collector system so we can see a complete view of the process? Or is that just wishful thinking? Thanks folks,
David

Hi David,
The solution seems to be difficult as per below link.
Please let me know if you find any solution.
http://help.sap.com/saphelp_nw04/Helpdata/EN/a8/a81b0b6473cb49bc34effad6eab13b/frameset.htm

SLT not working properly with Non-SAP source

Dear All,
We have MSSQL 2005 as a source. We are doing SLT to load data in HANA.
The issue here is:
MSSQL has an integer field whose default value is set to NULL. However, after doing SLT, data in HANA default data comes as Zeros instead of NULLS.
The issue is with columns with integer datatypes only.
Please help.
Regards,
Ankit

Hi! Thank you for advice!
I did next:
ap(config)#dot11 ssid CISCO_WIFI
ap(config-ssid)#authentication open
ap(config-ssid)#authentication key-management wpa version 2
ap(config-ssid)#guest-mode
ap(config-ssid)#wpa-psk ascii WIFI_PASSWORD
ap(config-ssid)#vlan 1
ap(config-ssid)#infrastructure-ssid
ap(config-ssid)#exit
ap(config)#interface Dot11Radio0.1
ap(config-subif)#encapsulation dot1Q 1 native
ap(config-subif)#end
ap#write memory
ap#configure terminal
ap(config)#interface Dot11Radio0
ap(config-if)# encryption vlan1 mode ciphers aes-ccm
ap(config-if)# ssid CISCO_WIFI
ap(config-if)# no shutdown
ap(config-if)# exit
ap#write memory
And...It doesn't work as I want..my repeater also connect to AP, but didn't give DHCP adressing to him wireless clients..
may be something wrong in my configuration? I'm not familiar with Cisco IOS..so help me in details please..

Share the cluster with a non-SAP application

Hi,
We need to install the SAP Systems on existing Oracle Cluster Environment (10g).
The scenario is there is an existing Oracle cluster which the client is using for different applications,we need to use the same existing Oracle cluster (RAC) to setup the SAP Systems.
So what we would like to do is to share an already existing non-SAP application on RAC with a new ( to be installed) SAP System.
Can someone guide me what are the pre-requisites and process for this kind of installation? The SAP Installation is on Linux environment.
Thanks and regards,
Silvio

Hi James
have a look on these links for Integration with Non-SAP Legacy Systems 

How ToConnect non-SAP RFCPrograms with SAP Netweaver Exchange Infrastructure
Refer this PDF....
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d0a8949b-098d-2910-2b8e-b5e9b7daeb26
Integration With Microsoft
http://help.sap.com/saphelp_nw04s/helpdata/en/75/b8a742d2efc611e10000000a1550b0/frameset.htm
SAP XI 3.0 help says:
You can use the IDoc adapter to connect SAP systems (as of release 3.1) and non-SAP systems with the Integration Server using native IDoc structures
Integration SAP EM 4.0 and SAP ICH 4.0 via SAP XI Pdf
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/50acad90-0201-0010-43ba-f8fc18ebb6ba
Integration of SAP CRM with non-SAP-Systems
Using XI, you can make use of the JDBC receiver adapter at the non-sap system since i believe its a database.
http://help.sap.com/saphelp_nw04/helpdata/en/64/ce4e886334ec4ea7c2712e11cc567c/content.htm
Please go through the following Blog
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
Thanks !!
Questions are welcome here!!
Also mark helpful answers
Thanks,
Abhishek Agrahari

SSO with Logon Ticket to non-SAP Unix based application

Hi all,
Anyone has implemented SSO with Logon Ticket to a Unix box ?
We need to achieve Single Sign On between our EP5.0 SP5 Portal and a third-party web application with a front-end on a Unix AIX machine with Apache.
We achieved SSO with non-SAP applications with Logon Tickets, but one was to an IIS system in another domain (we therefore used the standard Web Filter for IIS and declared it in usermanagement for cross-domain support) and another one running on Windows platform (we used the C libraries provided in the "Logon Ticket Toolkit": NT or Linux only).
From what we understand and found on the web sites, we cannot reuse any standard web filter (none for Unix, am I correct ???) and want to implement custom code using SAP libraries, if possible using Java
-> Are there any Java libraries that are available to both:
. verify the logon ticket with the deployed Portal public key
. decrypt/extract the authenticated username from this ticket ??
I've seen a mention of Java libraries, and Unix, in a SAP EP 6.0 document but I'm not sure where to find them...
Is the SAP Logon Ticket issued the same way in EP 5.0 and EP 6.0 ?
I managed to find something called SAPSSOEXT, for AIX, which contains some partial library and a sample, but it is dated 2000 !! Anyone has more information about this ?
Any hint is very much appreciated.
Thanks a lot
Olivier

Check these links for reference regarding AIX and Apache using X.509 certificates:
http://publib16.boulder.ibm.com/pseries/en_US/aixbman/security/cas_pki.htm
And just using cookies -
http://forums.devshed.com/archive/t-105611 (perl based)
You can also use mod_ssl built into your Apache to facilitate both certificate based authentication as well as encryption.
The mod_ssl route is most secure (because of the encryption), the IBM link is comprehensive but requires extra infrastructure (LDAP).
Nick
Nick

Solution manager 7.0 and Non-SAP Sys. for managing whole IT infrastructure

Hello Gurus,
ive tried to search the allmighty google and SDN network for an answer how can we use the SolMan 7.0 for external applications (non-SAP).
What is our concern is that basically the Sol Man is described for using with whole SAP product environment. project management, chagne management, support, updating and etc.
My idea is:
Can we use SolMan for describing our whole IT projects and processes?
What i mean is if for example we have a payroll system which is running in non-SAP environment, can we describe the project for it? track the changes to it? document everything and etc. Its like to use the SolMan for whole IT infrastructure no matter if the application is SAP or non-SAP environment.
Best regards
Laurynas Prikockis
Edited by: Laurynas Prikockis on Aug 18, 2010 6:50 AM

Hello there,
SAP Solution Manager contains some functionality to work with non SAP products. For example, in transaction SMSY (system landscape) you can define non SAP products and therefore non SAP systems, although the functionatlity that you get thus is somewhat limited (no automatic refresh, no logon from RFC destination, etc).
The same applies for the project (SOLAR_PROJECT_ADMIN) part of Solution Manager. It is possible to assign a logical component for a non SAP product to a project, then in the project it is possible to describe the process and document it but it will not be possible to use the more SAP oriented functionality like links to IMG projects, etc.
Best regards,
Miguel Ariñ

Using ale u can send from sap to sap and sap to non sap systems

hi,
using ale u can send from sap to sap and sap to non sap systems,
then what is diff b/w ALE and EDI

Hello KALYAN KUMAR,
Application Link Enabling (ALE)
1.You distribute data using ALE if you want to communicate from one system to one or more other (mostly internal) systems.
2.ALE transfers data in IDoc format and uses the methods of tRFC for data transfer.
3.ALE enables the integration of business processes across several SAP or non-SAP systems.
Electronic Data Interchange (EDI)
1.You use EDI if you want to exchange business application documents with an (external) partner system (for example, a customer or vendor).
2. The SAP system sends EDI messages in IDoc format to an EDI subsystem, where they are converted to a universal EDI standard (UN/EDIFACT or ANSI/X12).
3. This enables communication with non-SAP systems.
By definition, two partners are involved in the process in an EDI application scenario: The sender and the recipient of an EDI message
I hope u understands the difference:)

BI-IP with non SAP environment

Similar Messages

Maybe you are looking for