Connecting the UWL to a non-SAP system

Hi,
I am in need of a solution for showing the tasks from a non SAP system (DotNetNuke to be precise) in the UWL.
Our client wants to change from DotNetNuke to the SAP Portal, but doesn't want to change all the processes at ones.
J

I think I found it myself: It is possible to create a Custom Connector API
check this out: http://help.sap.com/javadocs/NW04S/current/uw/UWL%20Custom%20Connector%20API.pdf
If this doesn't work I will report this on the forum.
J.

Similar Messages

Using UWL from a non sap system

We are intgerating OTM (Oracle transportation management system) with SAP.
We need to have a single point where the users track all their norifications.
Is it possible to add notifications (task or error) into sap UWL from a non sap system.
If yes what are the main steps to do it?
Which set up must be done in SAP UWL to manage this?
Thanks in advance
Regards

Do some searches about "UWL custom connector" or "UWL custom connector API". You should find pretty good documentation about this subject.
Regards,
Karri

Sending special characters to non-unicode non-sap system: user exit

Hello All,
We are sending data from a SAP unicode system to a non-sap non-unicode system via IDOC. The idoc is standard idoc GLMAST which contains gl account information.
Some text fields contained in this idoc can contain special Polish characters. If they are sent unchanged to the non-unicode system, they give problems in the destination system.
What we would like to do is to build a user exit to convert these special characters, for example : 'é' becomes 'e', ....
We used enhancement object ALE00001, function EXIT_SAPLBD11_001 and implemented it, but it seems this exit is not called. Can this user exit be used for this functionality?
We also tried to change in SM59 the type of system of the destination to non-unicode, so that SAP replaces those special characters by #. But, than the error 02. Codepage not found is given in the idoc. Note: the link to the external system is not set up yet, so no actual connection is possible. Is this why we receive this error, and will this functionality work in the end with a non-sap system?
Thanks for helping.
Kind Regards,
Bart Pelsmaekers

I faced this problem in many project i implement below logic.
DATA: c_splchar(2) VALUE '90',
        c_defaultchar(1) type c VALUE '#'.
You have to move one by one character to this function module
          CALL FUNCTION 'URL_ASCII_CODE_GET'
               EXPORTING
                    trans_char = spl_char
               IMPORTING
                    char_code = spl_code.
All non unicode(Better you check) are always greater than 90.
         if spl_code is gt c_splchar.
            move c_defaultchar to c_splchar.
         endif.
"Reward points if usefull"
Thanks,
Narayan

What are the major process to transfer the data from legacy to sap system.

What are the major process to transfer the data from legacy to sap system using BDC at Real Time only?

hi,
BATCH DATA COMMUNICATION
main methods are:
1. SESSION METHOD
2. CALL TRANSACTION
3. DIRECT INPUT
Advantages offered by BATCH INPUT method:
1. Can process large data volumes in batch.
2. Can be planned and submitted in the background.
3. No manual interaction is required when data is transferred.
4. Data integrity is maintained as whatever data is transferred to the table is through transaction. Hence batch input data is submitted to all the checks and validations.
To implement one of the supported data transfers, you must often write the program that exports the data from your non-SAP system. This program, known as a data transfer program must map the data from the external system into the data structure required by the SAP batch input program.
The batch input program must build all of the input to execute the SAP transaction.
Two main steps are required:
To build an internal table containing every screen and every field to be filled in during the execution of an SAP transaction.
To pass the table to SAP for processing.
Prerequisite for Data Transfer Program
Writing a Data Transfer Program involves following prerequisites:
Analyzing data from local file
Analyzing transaction
Analyzing transaction involves following steps:
The transaction code, if you do not already know it.
Which fields require input i.e., mandatory.
Which fields can you allow to default to standard values.
The names, types, and lengths of the fields that are used by a transaction.
Screen number and Name of module pool program behind a particular transaction.
To analyze a transaction::
Start the transaction by menu or by entering the transaction code in the command box.
(You can determine the transaction name by choosing System Status.)
Step through the transaction, entering the data will be required for processing your batch input data.
On each screen, note the program name and screen (dynpro) number.
(dynpro = dyn + pro. Dyn = screen, pro = number)
Display these by choosing System Status. The relevant fields are Program (dynpro) and Dynpro number. If pop-up windows occur during execution, you can get the program name and screen number by pressing F1 on any field or button on the screen.
The technical info pop-up shows not only the field information but also the program and screen.
For each field, check box, and radio button on each screen, press F1 (help) and then choose Technical Info.
Note the following information:
- The field name for batch input, which youll find in its own box.
- The length and data type of the field. You can display this information by double clicking on the Data Element field.
Find out the identification code for each function (button or menu) that you must execute to process the batch-input data (or to go to new screen).
Place the cursor on the button or menu entry while holding down the left mouse button. Then press F1.
In the pop-up window that follows, choose Technical info and note the code that is shown in the Function field.
You can also run any function that is assigned to a function key by way of the function key number. To display the list of available function keys, click on the right mouse button. Note the key number that is assigned to the functions you want to run.
Once you have program name, screen number, field name (screen field name), you can start writing.
DATA TRANSFER program.
Declaring internal table
First Integral Table similar to structure like local file.
Declaring internal table like BDCDATA
The data from internal table is not transferred directly to database table, it has to go through transaction. You need to pass data to particular screen and to particular screen-field. Data is passed to transaction in particular format, hence there is a need for batch input structure.
The batch input structure stores the data that is to be entered into SAP system and the actions that are necessary to process the data. The batch input structure is used by all of the batch input methods. You can use the same structure for all types of batch input, regardless of whether you are creating a session in the batch input queue or using CALL TRANSACTION.
This structure is BDCDATA, which can contain the batch input data for only a single run of a transaction. The typical processing loop in a program is as follows:
Create a BDCDATA structure
Write the structure out to a session or process it with CALL TRANSACTION USING; and then
Create a BDCDATA structure for the next transaction that is to be processed.
Within a BDCDATA structure, organize the data of screens in a transaction. Each screen that is processed in the course of a transaction must be identified with a BDCDATA record. This record uses the Program, Dynpro, and Dynbegin fields of the structure.
The screen identifier record is followed by a separate BDCDATA record for each value, to be entered into a field. These records use the FNAM and FVAL fields of the BDCDATA structure. Values to be entered in a field can be any of the following:
Data that is entered into screen fields.
Function codes that are entered into the command field. Such function codes execute functions in a transaction, such as Save or Enter.
The BDCDATA structure contains the following fields:
PROGRAM: Name of module pool program associated with the screen. Set this field only for the first record for the screen.
DYNPRO: Screen Number. Set this field only in the first record for the screen.
DYNBEGIN: Indicates the first record for the screen. Set this field to X, only for the first record for the screen. (Reset to (blank) for all other records.)
FNAM: Field Name. The FNAM field is not case-sensitive.
FVAL: Value for the field named in FNAM. The FVAL field is case-sensitive. Values assigned to this field are always padded on the right, if they are less than 132 characters. Values must be in character format.
Transferring data from local file to internal table
Data is uploaded to internal table by UPLOAD of WS_UPLOAD function.
Population of BDCDATA
For each record of internal table, you need to populate Internal table, which is similar to BDCDATA structure.
All these five initial steps are necessary for any type of BDC interface.
DATA TRANSFER program can call SESSION METHOD or CALL TRANSACTION. The initial steps for both the methods are same.
First step for both the methods is to upload the data to internal table. From Internal Table, the data is transferred to database table by two ways i.e., Session method and Call transaction.
SESSION METHOD
About Session method
In this method you transfer data from internal table to database table through sessions.
In this method, an ABAP/4 program reads the external data that is to be entered in the SAP System and stores the data in session. A session stores the actions that are required to enter your data using normal SAP transaction i.e., Data is transferred to session which in turn transfers data to database table.
Session is intermediate step between internal table and database table. Data along with its action is stored in session i.e., data for screen fields, to which screen it is passed, the program name behind it, and how the next screen is processed.
When the program has finished generating the session, you can run the session to execute the SAP transactions in it. You can either explicitly start and monitor a session or have the session run in the background processing system.
Unless session is processed, the data is not transferred to database table.
BDC_OPEN_GROUP
You create the session through program by BDC_OPEN_GROUP function.
Parameters to this function are:
User Name: User name
Group: Name of the session
Lock Date: The date on which you want to process the session.
Keep: This parameter is passed as X when you want to retain session after
processing it or to delete it after processing.
BDC_INSERT
This function creates the session & data is transferred to Session.
Parameters to this function are:
Tcode: Transaction Name
Dynprotab: BDC Data
BDC_CLOSE_GROUP
This function closes the BDC Group. No Parameters.
Some additional information for session processing
When the session is generated using the KEEP option within the BDC_OPEN_GROUP, the system always keeps the sessions in the queue, whether it has been processed successfully or not.
However, if the session is processed, you have to delete it manually. When session processing is completed successfully while KEEP option was not set, it will be removed automatically from the session queue. Log is not removed for that session.
If the batch-input session is terminated with errors, then it appears in the list of INCORRECT session and it can be processed again. To correct incorrect session, you can analyze the session. The Analysis function allows to determine which screen and value has produced the error. If you find small errors in data, you can correct them interactively, otherwise you need to modify batch input program, which has generated the session or many times even the data file.
CALL TRANSACTION
About CALL TRANSACTION
A technique similar to SESSION method, while batch input is a two-step procedure, Call Transaction does both steps online, one after the other. In this method, you call a transaction from your program by
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>
Messages into <MSGTAB>.
Parameter 1 is transaction code.
Parameter 2 is name of BDCTAB table.
Parameter 3 here you are specifying mode in which you execute transaction
A is all screen mode. All the screen of transaction are displayed.
N is no screen mode. No screen is displayed when you execute the transaction.
E is error screen. Only those screens are displayed wherein you have error record.
Parameter 4 here you are specifying update type by which database table is updated.
S is for Synchronous update in which if you change data of one table then all the related Tables gets updated. And sy-subrc is returned i.e., sy-subrc is returned for once and all.
A is for Asynchronous update. When you change data of one table, the sy-subrc is returned. And then updating of other affected tables takes place. So if system fails to update other tables, still sy-subrc returned is 0 (i.e., when first table gets updated).
Parameter 5 when you update database table, operation is either successful or unsuccessful or operation is successful with some warning. These messages are stored in internal table, which you specify along with MESSAGE statement. This internal table should be declared like BDCMSGCOLL, a structure available in ABAP/4. It contains the following fields:
1. Tcode: Transaction code
2. Dyname: Batch point module name
3. Dynumb: Batch input Dyn number
4. Msgtyp: Batch input message type (A/E/W/I/S)
5. Msgspra: Batch input Lang, id of message
6. Msgid: Message id
7. MsgvN: Message variables (N = 1 - 4)
For each entry, which is updated in database, table message is available in BDCMSGCOLL. As BDCMSGCOLL is structure, you need to declare a internal table which can contain multiple records (unlike structure).
Steps for CALL TRANSACTION method
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. UPLOAD or WS_UPLOAD function to upload the data from local file to itab. (Considering file is local file)
4. Loop at itab.
Populate BDCTAB table.
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>.
Refresh BDCTAB.
Endloop.
(To populate BDCTAB, You need to transfer each and every field)
The major differences between Session method and Call transaction are as follows:
SESSION METHOD CALL TRANSACTION
1. Data is not updated in database table unless Session is processed. Immediate updation in database table.
2. No sy-subrc is returned. Sy-subrc is returned.
3. Error log is created for error records. Errors need to be handled explicitly
4. Updation in database table is always synchronous Updation in database table can be synchronous Or Asynchronous.
Error Handling in CALL TRANSACTION
When Session Method updates the records in database table, error records are stored in the log file. In Call transaction there is no such log file available and error record is lost unless handled. Usually you need to give report of all the error records i.e., records which are not inserted or updated in the database table. This can be done by the following method:
Steps for the error handling in CALL TRANSACTION
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. Internal table BDCMSG like BDCMSGCOLL
4. Internal table similar to Ist internal table
(Third and fourth steps are for error handling)
5. UPLOAD or WS_UPLOAD function to upload the data from the local file to itab. (Considering file is local file)
6. Loop at itab.
Populate BDCTAB table.
Call transaction <tr.code> using <Bdctab>
Mode <A/N/E>
Update <S/A>
Messages <BDCMSG>.
Perform check.
Refresh BDCTAB.
Endloop.
7 Form check.
IF sy-subrc <> 0. (Call transaction returns the sy-subrc if updating is not successful).
Call function Format_message.
(This function is called to store the message given by system and to display it along with record)
Append itab2.
Display the record and message.
DIRECT INPUT
About Direct Input
In contrast to batch input, this technique does not create sessions, but stores the data directly. It does not simulate the online transaction. To enter the data into the corresponding database tables directly, the system calls a number of function modules that execute any necessary checks. In case of errors, the direct input technique provides a restart mechanism. However, to be able to activate the restart mechanism, direct input programs must be executed in the background only. Direct input checks the data thoroughly and then updates the database directly.
You can start a Direct Input program in two ways;
Start the program directly
This is the quickest way to see if the program works with your flat file. This option is possible with all direct input programs. If the program ends abnormally, you will not have any logs telling you what has or has not been posted. To minimize the chance of this happening, always use the check file option for the first run with your flat file. This allows you to detect format errors before transfer.
Starting the program via the DI administration transaction
This transaction restarts the processing, if the data transfer program aborts. Since DI document are immediately posted into the SAP D/B, the restart option prevents the duplicate document posting that occurs during a program restart (i.e., without adjusting your flat file).
Direct input is usually done for standard data like material master, FI accounting document, SD sales order and Classification for which SAP has provided standard programs.
First time you work with the Direct Input administration program, you will need to do some preparation before you can transfer data:
- Create variant
- Define job
- Start job
- Restart job
Common batch input errors
- The batch input BDCDATA structure tries to assign values to fields which do not exist in the current transaction screen.
- The screen in the BDCDATA structure does not match the right sequence, or an intermediate screen is missing.
- On exceptional occasions, the logic flow of batch input session does not exactly match that of manual online processing. Testing the sessions online can discover by this.
- The BDCDATA structure contains fields, which are longer than the actual definition.
- Authorization problems.
RECORDING A BATCH INPUT
A B recording allows you to record a R/3 transaction and generate a program that contains all screens and field information in the required BDC-DATA format.
You can either use SHDB transaction for recording or
SYSTEM ? SERVICES ? BATCH INPUT ? EDIT
And from here click recording.
Enter name for the recording.
(Dates are optional)
Click recording.
Enter transaction code.
Enter.
Click Save button.
You finally come to a screen where, you have all the information for each screen including BDC_OKCODE.
Click Get Transaction.
Return to BI.
Click overview.
Position the cursor on the just recorded entry and click generate program.
Enter program name.
Click enter
The program is generated for the particular transaction.
BACKGROUND PROCESSING
Need for Background processing
When a large volume of data is involved, usually all batch inputs are done in background.
The R/3 system includes functions that allow users to work non-interactively or offline. The background processing systems handle these functions.
Non-interactively means that instead of executing the ABAP/4 programs and waiting for an answer, user can submit those programs for execution at a more convenient planned time.
There are several reasons to submit programs for background execution.
The maximum time allowed for online execution should not exceed 300 seconds. User gets TIMEOUT error and an aborted transaction, if time for execution exceeds 300 seconds. To avoid these types of error, you can submit jobs for background processing.
You can use the system while your program is executing.
This does not mean that interactive or online work is not useful. Both type of processing have their own purposes. Online work is the most common one entering business data, displaying information, printing small reports, managing the system and so on. Background jobs are mainly used for the following tasks; to process large amount of data, to execute periodic jobs without human intervention, to run program at a more convenient, planned time other than during normal working hours i.e., Nights or weekends.
The transaction for background processing is SM36.
Or
Tools ? Administration ? Jobs ? Define jobs
Or
System ? services ? Jobs
Components of the background jobs
A job in Background processing is a series of steps that can be scheduled and step is a program for background processing.
Job name. Define the name of assigned to the job. It identifies the job. You can specify up to 32 characters for the name.
Job class. Indicates the type of background processing priority assigned to the job.
The job class determines the priority of a job. The background system admits three types of job classes: A B & C, which correspond to job priority.
Job steps. Parameters to be passed for this screen are as follows:
Program name.
Variant if it is report program
Start criteria for the job: Option available for this are as follows:
Immediate - allows you to start a job immediately.
Date/Time - allows you to start a job at a specific name.
After job - you can start a job after a particular job.
After event - allows you to start a job after a particular event.
At operation mode - allows you to start a job when the system switches to a particular operation mode.
Defining Background jobs
It is two step process: Firstly, you define the job and then release it.
When users define a job and save it, they are actually scheduling the report i.e., specifying the job components, the steps, the start time.
When users schedule program for background processing, they are instructing the system to execute an ABAP/4 report or an external program in the background. Scheduled jobs are not executed until they are released. When jobs are released, they are sent for execution to the background processing system at the specified start time. Both scheduling and releasing of jobs require authorizations.
HANDLING OF POP UP SCREEN IN BDC
Many times in transaction pop up screen appears and for this screen you dont pass any record but some indication to system telling it to proceed further. For example: The following screen
To handle such screen, system has provided a variable called BDC_CURSOR. You pass this variable to BDCDATA and process the screen.
Usually such screen appears in many transactions, in this case you are just passing information, that YES you want to save the information, that means YES should be clicked. So you are transferring this information to BDCDATA i.e., field name of YES which is usually SPOT_OPTION. Instead of BDC_OKCODE, you are passing BDC_CURSOR.
BDC_CURSOR is also used to place cursor on particular field.
A simple transaction where you are entering customer number on first screen and on next screen data is displayed for the particular customer number. Field, which we are changing here, are name and city. When you click on save, the changed record gets saved.
Prerequisite to write this BDC interface as indicated earlier is:
1. To find screen number
2. To find screen field names, type of the field and length of the field.
3. To find BDC_OKCODE for each screen
4. Create flat file.
generally Batch Input usually are used to transfer large amount of data. For example you are implementing a new SAP project, and of course you will need some data transfer from legacy system to SAP system.
CALL TRANSACTION is used especially for integration actions between two SAP systems or between different modules. Users sometimes wish to do something like that click a button or an item then SAP would inserts or changes data automatically. Here CALL TRANSACTION should be considered.
2. Transfer data for multiple transactions usually the Batch Input method is used.
check these sites for step by step process:
For BDC:
http://myweb.dal.ca/hchinni/sap/bdc_home.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&
http://www.sap-img.com/abap/learning-bdc-programming.htm
http://www.sapdevelopment.co.uk/bdc/bdchome.htm
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html
Check these link:
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://www.sap-img.com/abap/question-about-bdc-program.htm
http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/
http://www.planetsap.com/bdc_main_page.htm
call Transaction or session method ?
null

Distribute Global outline agreement to non SAP system

Hello,
We have a system called Upside for legal Contract managment where complex workflow and legal team works.
Our requirement is to to send SRM Global outline agreements to that system as metadata and once all the approval in Upside completes they will send the data back which we need to update in Global outline agreement in SRM system.
Does anyone have done such kind of integration i.e. SRM Global outline agreement from SRM system to non SAP system and then get the details back.
Please advise.
Thanks
Ritesh

1) Please try this.
Distribute from SRM to R/3. From R/3 you can use the transaction ME308 to push the contracts to your non SAP system.
After making changes you can use the upload functionality in SRM for the changes.

Connect b/w SAP and Non SAP -system

Hi All,
I have a requirement where i need to connect between a SAP system and Non-Sap System.
the front end is an E-Build tool (for construction Industry) from where the user will pick the data and the data should get store at the backend i.e in the SAP system.
E-build is a tool for construction industry with lots of flexible options for the user to check for their house, along with their prices.
These all data needs to be captured and store at the backend.
Can any one suggest me which method shall i go for this in ABAP(and How) or need to go for the XI-Netweaver or EP technology.
Thanks & Regards
Mona

you better to go for middleware tools . keep files( whichs contains data to be stored in SAP) in one folder at 3p systems and middleware adapters will pick that filles automatically and sent it to Application server or then process the data into SAP.
tks.. venkat

'Error Occured in the Source System' for Non SAP system

Hi Gurus,
We have an Info Package which is getting the data from the Source System 'DOCP' and it has failed due to 'Error Occured in the Source System'.Since the source system is Non SAP system there is no option 'Replicate Data Sources'.So,First I activated the transfer rules by the program and ran the package again .But again the same error occured.
Please suggest me how to proceed for this error for Non SAP Systems?

Hi,
Check the RFC connection in SM59 and reactivate the source system again.
Hope this helps..
Thank you,
S R.

How to connect one SAP system to Non-SAP system(Example:Window's7)?

Hi Experts,
In general, One SAP system can connect another SAP system through RFC.How to connect One SAP system to Non-SAP system(example:window's 7) and is it possible through RFC?
Thanks and Regards,
Nageswar

Hello Wolfgang Schaper,
Thank you so much for quick response.
As you told I am trying to work with BRFplus/DSM to call decision services from nonABAP systems,so I tried with RFC.But it is not possible as you told.
Please give any solution Without using Web Services, is there any ways to connect from SAP system with the Non-SAP Systems.

Integrate or connect SAP system to non-SAP system

Hi All,
We need to connect SAP system or integrate inspHire rental software to SAP. Do you know the process or initial summary on how to integrate this one?
As of now, the only way that we know to integrate SAP to non-SAP for posting is thru LSMW and batch input.
your suggestions will be greatly appreciated.

Hi,
LSMW is just tools for integration and you can use BDC Call Transaction, BDC session or BAPI, or Function to update something ins SAP.
1/Easier is if your non-SAP system is able to create file and ftp to SAP folder.
2/You will have background job running program that will every 5minutes or hour or daily(it is up to you how fast dat has to be bring to SAP) check if file was create in SAP folder.
3/Program will move file to folder in process
4/Program will process file, usinf function, or call transaction to update SAP on the base of file
5/Program will move file to process folder
If you need more info give me detail about what you would like to update in SAP and I could send you code.
Bye Jan

Activating WebService on R/3 to connect a non-SAP system (XML)

Hi Experts,
Apologize if my thread is not on the right category. I'm not sure where to put this.
Is there any steps on how to activate webService to connect to a non-SAP system without using middleware like XI/PI. I'm trying to connect to a non-SAP system that sends an xml format message and then directly connect to an R/3 system. Is this possible? thanks!

Hi,
Check this link.
Web Services from Function Module
it might help u.
Thanks.

RFC Adapter to connect to Non SAP System

Hi,
I have a scenario to connect to a non SAP system using RFC adapter. I am not used to the same. I need to know whether this is possible and what are the steps to be done.
Thanks and regards
Siji

Hi,
These links should help.
Non-SAP application connecting to PI via Sender RFC Adapter
Error by setup RFC Interface with non SAP system
SAP PI to Third Party system through RFC Connectivity ??
Regards,
Jannus Botha

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

SAP to External Non SAP Systems C++ Connections

Hi guys,
i should develop a C++ application that should transfer/receive data from an external Non SAP System to a SAP System (MM SD FI Modules) and viceversa,
This bidirectional integration should be synchronous and asynchronous, depending on the data flow type,
I was thinking to use IDocs for this communications,
I should be able to send purchase and sell orders requests from the Non Sap System to the Sap system and receive the result of SAP processes once the SAP transactions will be finished.
So i'll have a C++ process that send idocs (created with sdk end sent throught RFC to SAP) for SD or MM operations and a SAP Abap module that receive this idocs and start internal operations.
After this i need an internal SAP abap module that send to my external application Idoc's with the result of internal operations.
Are the idocs the common way to transfer data(low cadinality) in this scenario, or there is a better way?
Note: my sap system versions are previous to the netweaver release, so i can't use a Service Oriented comunication...
Thanks in advance!!!

Hi,
try sending the data through BAPI Function Module.
and use the FM in your C++ program.
hope this works....
try
best of luck!!
thanks
ravi aswani

Regarding the Service Registry in SAP PI 7.1 and non SAP System ....!

Hi All ,
I need to know answers for the below Question ...hope to get some answers frm Experts ....
1) How to publish service from non-SAP systems?
2) How to use discovered service in the Service Registry for consumer/provider scenario? With some examples.
Thanks in Advace ...!
Regards ,
Aziz khan .
Edited by: Aziz khan on Sep 16, 2009 11:43 AM

Hi,
1) How to publish service from non-SAP systems?
Publish Service is nothing but making WSDL of that service available. For that you need to Publish the WSDL of the web Service to UDDI. For Non SAP system, Lik .net , Java they have there oun APIs to do so. U can search on net to get it.
For Ex. below link.
http://www.startvbdotnet.com/web/publish.aspx
2) How to use discovered service in the Service Registry for consumer/provider scenario? With some examples.
Once you discover the services, you get the WSDL of that Service. Then You can import this WSDL in IR and you it.
See the below links.
http://help.sap.com/saphelp_nw04/helpdata/en/43/ce993b45cb0a85e10000000a1553f6/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/EN/26/9e97b0f525d743882936c2d6f375c7/frameset.htm
Shweta

Invoice posting for the PO from Non-SAP system

Dear Friends,
I have one requirement like from Non-SAP system PO details will be accessed from SAP and after certain calculations Invoice will be posted for the same PO back to SAP.
Everything needs to be done in Non-SAP system by accessing SAP system.
There are some BAPI which can be used for the purpose, but I am not able to get the correct BAPIs to get the PO details and Posting the Invoice for PO.
Please anybody can help me out with the BAPI details.
Thanks in Advance.

Hi,
Use following BAPIs
BAPI_PO_GETDETAIL - To get Purchase Order details
BAPI_INCOMINGINVOICE_CREATE - For Incoming Invoice
Regards
Vinod

Connecting the UWL to a non-SAP system

Similar Messages

Maybe you are looking for