EDI to RFC interface

Hi,
I'm about to implement Spec2000 to RFC interface. since XI does not support EDI (no EDI adaptors available) i'll have choose one out of two options:
1. manipulate EDI as it was regular text file.
2. use 3rd party tool as an adaptor.
i belies my first option is complicated and clearly has great risk, so i'm looking for as much leads as i can get.
Tnx in advance
Uri

>
uri karagila wrote:
> Hi,
>
> I'm about to implement Spec2000 to RFC interface. since XI does not support EDI (no EDI adaptors available) i'll have choose one out of two options:
>
> 1. manipulate EDI as it was regular text file.
> 2. use 3rd party tool as an adaptor.
>
> i belies my first option is complicated and clearly has great risk, so i'm looking for as much leads as i can get.
>
> Tnx in advance
>
> Uri
Option 1 - I guess that is not a good idea considering the complexity in EDI messages. But then it denpends how many interfaces you have. If there are very less say under 10 interfaces using the EDI spec. then it is still worth investing time and money on coming up with the manipulation but else.... its a night mare.
Option 2 - There are various third party adapter available ex. seeburger, iway etc which you can make use. Only thing is it comes with a cost but life becomes much easier.

Similar Messages

EDI to RFC

Hi,
could you please explain the scenario EDI to RFC.
do we have any weblogs on this?
Best regards
GSR

Hi;
See if you can get something out of these
Business To Business Integration
/people/shailesh.mane/blog/2006/06/27/b2b-configuration-part-i--creating-an-integration-scenario
/people/shailesh.mane/blog/2006/06/29/b2b-configuration-part-ii--creating-the-configuration-using-the-automated-configuration-tool
General Business To business Integration Series
/people/james.guanzon/blog/2006/02/22/how-to-support-industry-standards-in-xi-part-i-of-iii--interfaces
/people/james.guanzon/blog/2006/03/23/how-to-support-industry-standards-in-xi-part-ii-of-iii--mapping
/people/james.guanzon/blog/2006/09/09/how-to-support-industry-standards-in-xi-part-iii-of-iii--config-test
SAP XI supports EDIFACT
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
Mudit

ALE/EDI and RFC

Dear All,
Please, can anyone tell me what is the difference between ALE/EDI and RFCs?
Thanks in advance.
Kind Regards,
Umesh.

Hi prasad,
1) ALE = Application Link Enable: Initially developed for SAP as an abstract layer to extract master and transactional data to be sent ellectronically to other SAP systems. These days is also being used to send data no non-SAP systems. ALE is not a protocol or anything like that, it's just abstract layer composed by a set of applications which are capable of extracting aplication data on a 1-time basis or periodically, by selection criteria or incrementally by deltas.
2) In contrast, EDI = Electronic data interface, this is a comunication protocol not designed by SAP but it´s an industry standard. Of course most SAP software supports EDI, but EDI it's no software but the specification of the protocol in itself.
These r some major difference b/w ALE and EDI:
ALE: used to transfer IDOC with in the R3 distributed system.
EDI: used to transfer IDOC from R3 system to non sap system
ALE --This method is used to transfer master data
EDI--This method is maximum used to transfer transactional data.
ALE--RFC port is used
*EDI*-- FILE port is used
ALE--Data transfer takes place from one mother client to N different clients
EDI-- one partner 2 other partner thru customer distribution model
The philosophical difference between EDI and ALE can be pinned as follows:
If we send data to an external partner, we generally speak of EDI, while ALE is a mechanism to
reliable replicate data between trusting systems to store a redundant copy of the IDoc data.
The difference is made clear, when we think of a purchase order that is sent as an IDoc.
If we send the purchase order to a supplier then the supplier will store the purchase order as a sales order.
However, if we send the purchase order via ALE to another R/3 system, then the receiving system will store the purchase order also as a purchase order.
ALE
ALE is SAP proprietary technology that enables data communications between two or more SAP R/3 systems and/or R/3 and external systems. When a new enterprise resource planning (ERP) solution such as R/3 is implemented, companies have to interface the ERP system with legacy systems or other ERP systems.
ALE provides intelligent mechanisms where by clients can achieve integration as well as distribution of applications and data.
ALE technology facilitates rapid application prototyping and application interface development, thus reducing implementation time.
The ALE components are inherently integrated with SAP applications and are robust, leading to a highly reliable system.
ALE comes with application distribution/integration scenarios as well as a set of tools, programs, data definitions, and methodologies that you can easily configure to get an interface up and running.
ALE allows for efficient and reliable communication between distributed processes across physically separate SAP systems.
ALE is based on application to application integration using messaging architecture. A message defines data that is exchanged between two processes. IDocs are containers that hold data exchanged between the two systems.
Benefits of ALE:
Integration with non-SAP systems: ALE architecture allows third party applications to integrate with SAP system.
Reliable Distribution: Once message type created and the receiver of the message is determined, ALE delivers the message to the recipient. If there is any network problem it will buffer the message and delivers the message once the network is restored. It also ensures that the message is not delivered twice.
Release Upgrade: Any of the distributed system can be upgraded to the new release of SAP without affecting the functionality. The ALE layer ensures backward compatibility of messages exchanged between systems.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
The philosophical difference between EDI and ALE can be pinned as follows: If we send data to an external partner, we generally speak of EDI, while ALE is a mechanism to reliable replicate data between trusting systems to store a redundant copy of the IDoc data. The difference is made clear, when we think of a purchase order that is sent as an IDoc. If we send the purchase order to a supplier then the supplier will store the purchase order as a sales order. However, if we send the purchase order via ALE to another R/3 system, then the receiving system will store the purchase order also as a purchase order.
REWARD IF USEFUL
THANKS AND REGARDS
SUMA SAILAJA PVN

NWDS import RFC interface for the structure issue??

Hi Gurus,
I'm working on the SAP NetWeaver BPM with NWDS 7.3 SP12 rite now and got confused about the RFC interface structure stuff.
I have a mapping activity defined in the process and the receiver interface needs a RFC. So I go to "Process Modeling" -> "Services Interfaces", right click and choose "Import RFC",type the correct RFC/BAPI name connecting with the SAP ECC system. The issue is that when I finished importing the RFC, went to the "Data Types", the RFC interface namespace shows out but the structure shows seperately with individual segment, so the whole nested RFC interface structure messed up in parallel which is incorrect for the data object and output mapping for later process activities.
Anyone has ran into such kind of issue or experience the same, any solution or suggestion?
Thanks in advance,
Rajesh

William,
Another two questions relates to NWDS BPM development:
1. Sometimes after I import the service interface into NWDS, the structure displays differently from it defines in ESR, I mean the fields sequence. I dont know why
2. Refer to your screenshot,
Assume the occurence of node HEADER and item is (0..1), when I want to map a blank constant to them to generate the target structure, the editor not allows and display error which is very different with ESR mapping tool, could you please help to advise? Tons of thanks!
Thanks a lot in advance,
Rajesh

Rfc interface generator

Hallo Gurus,
as far as you know is the "RFC Interface Generator" still active?
It should be under:
Tools --> ABAP Workbench ---> Development --> Function library
and then utilities -> RFC generate
I am working on a SAP ECC 6.0.
I need it to generate the code to call an RFC from an external program...
Thank you very much indeed!

se37 > <fm_name>
goto > furture options> generate RFC include
generate RFC/ update include

RFC Interface Generation

Under 4.6C, in SE37 you could generate RFC interface code (.c and .h files) for a function by going to the menu bar: Utilities / RFC Interface / Generate
Under 4.7, there is no RFC Interface option under Utilities. Any idea if this has been moved elsewhere, or if it is gone altogether?

Hi Lisa,
Look at oss note 551830. It tells you the replacement.

Generating RFC Interface skeleton code

hi
In SAP R346C the menu for generating Rfc skelecton code was present in the utilities menu.
I am not able to locate it in sapr347. Can somebody point it to me.

Hi,
this is OSS-Nr. 551830:
Symptom
There is no code generator for RFC interfaces in transaction SE37, menu option Utilities -> RFC interface -> Generate.
Other terms
RFC stub, C programming
Reason and Prerequisites
Since functions were changed in the Web Application Server, the generation function is no longer provided.
Solution
Instead of directly using the RFC library, you can use the Java Connector (JCo) or the .NET Connector.
As of Version 6.20, you can also use our SOAP implementation for calls to SAP.
You can download both connectors from SAPnet. Here you will also find information on the release as well as use of SOAP implementation. This information is available on http://service.sap.com/connectors.
sorry ...
Viktor

Performance Tuning in HTTP - RFC Interface

Hi,
I'm currently working on a HTTP --> RFC scenario and facing slow performance issues. When I test this interface with a transaction having 1 line item, the response from RFC is instantaneous. However, when there are about 400 line items, the average response time from RFC is about 8-9 seconds. When this interface goes live, there will be transactions with > 1000 line items. I'm really worried about the performance going down, as performance is a major criteria for deploying this interface.
Could you suggest any steps to improve the performance/reduce the response time?
Thanks,
Guru

Guru,
Disable all the Fields in the RFC which you are not using / populating.
One of my colleagues faced a similar problem and when they disabled the fields which were not being used when triggering the RFC call, the perfromance improved drastically.
Also, turn off logging of Synch Messages as this also can cause perfromance issues.
SXMB_ADM --> Integration Engine Configuration --> LOGGING_SYNC should be set to 0
Regards
Bhavesh

EDI Process Delivery interface

Dear Experts,
I have a Outbound Delivery Interface, i need to trigger an outbound IDoc through VL71 transaction. Please let me soon.
Thanks
Kp

Hi ,
Through delivery Process ASN can be sent to customer.
All other master data and process steps are same.
You have to make following settings in the system
1) Create port (WE21)
2) Set up Partner Profile WE20
3) Create condition records in NACE for V2(Shipping) , output type LAVA. (Communication type withh me EDI (6))
4) during outbound delivery save/Goods issue , the o/p type should be triggered and generate the IDoc.
This IDoc is an outbound idoc. Check WE02 for idocs. You will find a inbound Idoc -> which we will inturn create an Inbound delivery (ASN) automatically.
Configure the steps.If you need further more help on this.Please get back.
Best Regards,
Nisha

EDI 850's Interface File Data program errors out

This is interface dile data program completes in error for EDI 850. Prior to this we had issues saying "error starting toolkit", but that was resolved by the DBA's. Now that error has gone and this error is coming up.
Below is the error message:
Version 12.1.3
DB : 11g
+-----------------------------
| Starting concurrent program execution...
+-----------------------------
Arguments
P_TRANSACTION_TYPE='POO'
P_FILE_PATH='/interface/infvmmci/ECRP2/outgoing'
P_FILE_NAME='VMMC850.dat.20120702215742'
P_MAP_CODE='EC_POO_FF'
Execution options
VERSION=2.0b ORIENTATION=LANDSCAPE
Current NLS_LANG and NLS_NUMERIC_CHARACTERS Environment Variables are :
American_America.US7ASCII
Enter Password:
REP-1401: 'p_run_idformula': Fatal PL/SQL error occurred.
REP-0069: Internal error
REP-57054: In-process job terminated:Terminated with error:
REP-1401: 'p_run_idformula': Fatal PL/SQL error occurred.
Report Builder: Release 10.1.2.3.0 - Production on Mon Jul 2 21:58:53 2012
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Start of log messages from FND_FILE
End of log messages from FND_FILE
Program exited with status 1
Concurrent Manager encountered an error while running Oracle*Report for your concurrent request 5710284.
Review your concurrent request log and/or report output file for more detailed information.
Executing request completion options...
Output file size:
0
Finished executing request completion options.
Kindly help,
Ganapathy

Please see if these docs help.
Interface File Data Program Fails With REP-1401 Error [ID 1415103.1]
850 POI Inbound EDI ECEPOI Error ORA-29284: file read error. [ID 565059.1]
Running Interface File Data, Completes With Error. [ID 563879.1]
How to Ensure Outbound 856 (DSNO) documents are generated [ID 1432829.1]
Thanks,
Hussein

Proxy to FILE/RFC Interface

Hi Experts,
Recently your ECC is upgrade, My Scenario is PROXY - > PI -> FILE/RFC, There are 2 issues for the same interface.
Getting CCMS Alerts as below. When I check in SMQ2, i dont see any messages are stucked in the queue, but we are receiving this alerts frequently from after upgrade.
Issue 1:-
ALERT for MIP \ Transactional RFC and Queued RFC \ Int. Server Outbound Messages (XBQO*) \ Blocked queues: Client 001 at 20140801 101549 ( Time in UTC ) RED CCMS alert for monitored object Blocked queues: Client 001 Alert Text:Blocked inbound queue: Client 001 Q name XBQO0___XI_SERIALIZE0068 status RETRY dest CHGVA-SAP-MIP_MIP_14 System:MIP
Segment:SAP_CCMS_CHGVA-SAP-MIP_MIP_14
MTE:MIP\Transactional RFC and Queued RFC\Int. Server Outbound Messages (XBQO*)\Blocked queues: Client 001
Client:000
User:SAPSYS
Severity: 50
Issue 2:-
The messages is getting successful in message monitoring when going into details Audit log is showing the below error. Once is successfully delivered the message the message Id is trying to deliver the same message ID and getting the below error.
This is also comming after upgrade.
Putting message into receive queue failed, due to: com.sap.aii.af.ra.ms.api.DuplicateMessageException: Message ID e4196a30-56ac-59f1-a2e0-0050569a0002(INBOUND) already exists in database: com.sap.sql.DuplicateKeyException: Violation of PRIMARY KEY constraint 'PK__XI_AF_MS__99C1915D08BFA0D4'. Cannot insert duplicate key in object 'SAPMIPDB.XI_AF_MSG'..
Can any one help me out from this both issues.
Thanks in Advance for your responces
G V Anil

Hi Sarojkanta,
Its a Production issue, The messages comming form ECC as a scheduled background job.
We upgraded our ECC system to 6.0 EHP6 from EHP5 and now all asynchronous. Sender PROXY Interfaces hits PI and go immediately into RETRY status and the messages are getting successful to teh receiver. but its trying second time with the same Message ID and then we are facing this issue as show in the above screen shot.
When checked in MONI for this interface all the messages are showing as below.
Call Adapter is getting failed and trying second time.
Thanks
G V Anil

HTTP to RFC Interface Determination problem

Hi experts,
I am doing HTTP <-> RFC scenario mentioned in blog
/people/community.user/blog/2006/12/12/http-to-rfc--a-starter-kit
almost everthing is done; but while configuring the interface determination, i am not able to see the inbound interface.
your valuable help would be appreciated
Regards
Sumit Bhutani

Hi Bhavesh,
Thanks for your quick response; this problem has been resolved, but while testing my scenario using RWB i am getting this error.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">CANNOT_READ_PAYLOAD</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to read payload from the message object</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Please suggest on this
Thanks
Sumit

RFC interface failed without mapping

HELLO ALL,
I was working on SOAP to RFC scenario having a simple message mapping in it. The interface was working perfectly fine.
Later on I got a requirement to remove the mapping from my interface.
I was able to run the interface after the changes but It doesnt return any value, which usually happens when we pass wrong parameters to the RFC for which RFC doesnt find any entry.
I tested the RFC with the same test data using se37 and it returned me the records.
Any clue, why the RFC doesnt understand the input values when we dont have a mapping ? Does the message mapping convert/format the input data ?
I will appreciate for your inputs.
Thanks to all.
PEERU

Thanks both, for your replies.
As per my understanding mapping is optional in XI.
I am using the RFC request and response structure for the SOAP end. I just created a message interface for the SOAP sender, based on the RFC request and response structures.
Correct me if in the case of RFC, SAP makes mapping a mandatory object. I dint find any document which says that mapping is always needed for RFC receiver interface.
Thank You.
PEERU

Receiver RFC - Interface Objects

Hi every one,
I have a scenario, SOAP (SYNC)- XI - RFC (SYNC), MY question is do we need to create and interface objects for the receiver. Or can I use the RFC as the interface object.
Technical explanation would really help me.
Please clear.
Thanks,
-Naveen.

Hi Naveen,
>>>>>do we need to create and interface objects for the receiver. Or can I use the RFC as the interface object.
As RFC itself is a interface you need not create a seperate interface for an RFC.
In message mapping you will need to create two message mapping.
One SOAP_Req to RFC_Req
two RFC_Res to SOAP_Res.
When you will try to implement Interface Mapping, the source interface would be the imported 'External defination' of WSDL and the receiver would be the RFC. In the lower section of the same screen click 'Response' tab and add RFC_Res to SOAP_Res as mapping prog and under 'Request' tab add SOAP_Req to RFC_Req.
Let me know if you further assistance.
regards,
Ashish

EDI - SAP -- Sterling Interfacing

Hello ,
I am currently working on IDoc - EDI 810 to sterling & EDI 850 to IDoc .
I want to understand interfacing using IDOC - EDI 810 . 850 with Sterling & role of XI/PI in case needed .
Can we send XML files to sterling ?
Also want to understand any thing sterling would need us to provide them
Thanks.

The only one i know of is True Commerce
http://www.truecommerce.com/complete_solution/acct_pkg/sap.php
not sure of what the price is.

EDI to RFC interface

Similar Messages

Maybe you are looking for