EDI
EDI(Electronic Data Interchange )
RFC DESTINATION:
A logical name used to identify the remote system on which a function needs to be executed.
Partner Profile:
It defines the characteristics of data being exchanged with the business partner.
Partner Function:
Role of the partner Eg:Ship-to-party,bill-to-party,etc in EDI and in ALE legacy system or remote SAP system.
Partner type:
The type of your business partner .
EDI – KU/LI
ALE -- LS.
Archiving:
-Need to archive the important transmitted document
-Created in SARA
-Assigned in WE20.
PartnerProfile Tips:
• RSECHK07- Consistency check for Partner Profile.
• If you want to modify partner profile; copy it and then modify. If you can’t modify it , u have to delete it.
• To move partner profile to production system choose Partner -> Transport
Port defintion:
It defines the medium through which data is exchanged between systems.
• tRFC - Used by ALE
• FILe - Used by EDI
• R/2 system system port – For R/2 system
• Internet port - to connect with internet applications
• It also depends on the receiving side. If the receiving subsystem accepts tRFC, EDI also can use tRFC.
Remote Function modules required by Subsystem to send status and inbound idoc to SAP:
Startrfc - Program to execute RFC – enabled Fun.mod. in SAP
EDI_DATA_INCOMING - To send data as inbound
EDI_STATUS_INCOMING - To send status to SAP
RSPARAM - To know the gateway service of the SAP system.
Message Control:
• Output controller
• A service program for determining the output type
• To generate and manage various outputs from an application and control their medium and timing of exchange.
• To retransmit the document without duplicating it
Procedure:
• A procedure defines a set of possible outputs for an application
• There may be more than one procedure but only one can be active
• Requirement field in procedure specifies the condition which the sales docu. should reach,for sending the sales order response.
Output type:
Defines the characteristics and attributes of the output.
Access Sequence :
Defines a sequence in which the business rules are checked using condition record of the condition table for proposing output type.
Sapfans Q & A
SREL_GET_NEXT_RELATIONS -
Function Module that will provide me the number of the document that was created by an IDoc
RLSUB020
Program which uses the above function module.
Upgradation problem
When the old version program is upgraded in to newer version(4.0b  4.6c) the SE38 editor won’t allow u get thru’ the programs normally to get rid of this.
Solution:
EDIT > MODIFICATION OPERATIONS > SWITCH OFF ASSISTANT. Hit Enter on the subsequently shown Warnings window. You should now be able to maintain the code as before.
When transporting the dialog program sometimes the links may be missing in the testing and production area. To overcome just check u have properly save your all includes and other stuff in the same request if not, do so. Other options In ver 4.6c -> Within ABAP editor try utilities/Update navigation index
this fixes the links
Check these thread for more details -
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
Hope this helps.
ashish
Bluesky
