EDI and Ack 997

Hi,
I have a port in BizTalk on which I receive EDI message from client. Once I receive the EDI, I also receive ack 997 on the same port. What does that mean?
Does it mean that BizTalk has automatically generated that ack and we need to send that back to the client?
Or it means that client has sent that ack to us?
Thanks.
It is EDI receive pipeline which generates 997 (functional ack notifying than EDI message is received). And it does only when it is configured to do so. So if as per the agreement , client expects acknowlegement(997) then you have to send it else you
can turn off generation of 997.
I would ask you to have look at
Tutorial for more insights.
Maheshkumar S Tiwari|User Page|Blog|BizTalk
Server : How Map Works on Port Level

Similar Messages

Adapter Modules & split 997 channel reqd for splitting Edi and Acknowledgement

Hi,
I am using PI 7.11 with B2B add-on installed.We will be using AS2 adapters ,as of now
configured file adapters in place of it.
This B2B scenario does not consists of Party because 1 sender and 1 receiver system is involved as of now.
May be client provides identifiers details and include party.
In my previous B2B scenario(PI 7.3) involving Seeburger , AS2 channel was configured with(image shown below)
SeeClassifier,BIC, message splitter modules and Split997 channel for splitting EDI PO and Functional Acknowledgement.
What are the adapter modules that will be required in case of B2B add on (PI 7.11)and does it requires
EDI separator channel for splitting EDI doc & Func Ack.What can be the other probable issues.
How we will monitor the messages and Ack once its implemented end to end?
Regards,
Mayank Yadav

Hey Mayank,
Inbound Scenario configuration: (3 step)
1) Sender AS2 (EDI messages) -----> EDI separator receiver (no mapping required here; EDI separator is used to split bulk EDI messages and configure acknowledgements (997) if required)
2) EDI separator sender (with message type(eg.850),version and sender ID/receiver ID configuration; here X12convertor module is used to change raw edi into XML) ----> Idoc or any receiver channel (inbound)(here you have your actual mapping)
(if 997 is configured as requested in the first step; then you need to handle the 997 generated by EDI separator)
3) EDI separator sender (997 message type,version,reverse combination of sender ID,receiver ID) to Receiver AS2 ( no modules required pass through)
Outbound Scenario configuration
1) sender channel (say Idoc) to AS2 receiver (requires mapping)
997 file can be sent back by partners (EDI 997 as acknowledgement)
this will be taken care like any other inbound message) which can be then converted to SYSTAT IDOC or so to track the status of outbound message.
B2B status tab in PI monitoring helps you track acknowledgements
Hope this answers your question:
What are the adapter modules that will be required in case of B2B add on (PI 7.11)and does it require
EDI separator channel for splitting EDI doc & Func Ack.What can be the other probable issues.
How we will monitor the messages and Ack once its implemented end to end?
For detailed information on this; please refer Functional Acknowledgement (Inbound and Outbound FA 997)- for Beginners
Regards,
Pooja

Send and Receive ACK 997 over AS2

Hi,
I have AS2/EDI setup in place and is working fine. The only thing remaining is sending and receiving Ack 997. How can I do that? What is the quickest way of doing it?
Please help. I need it urgently. I'm sure there must be some quick way of doing the same.
Thanks.

Hi Dipti,
If you have setup ready with parties then you need to add agreement
and in the agreement configure the acknowledgements section.
Go through following articles:
BizTalk Server EDI Scenario: Send an X12 Message and Receive an Acknowledgement
BizTalk Server EDI Scenario: Send an X12 Message Over AS2 and Receive an
Asynchronous MDN
If you not have parties added then first do that and then create agreement between them:
Create Trading Partners and Business Profiles
Create Trading Partner Agreement
Maheshkumar S Tiwari|User Page|Blog|BizTalk
Server : How Map Works on Port Level

How to set the AS2 fileName for outbound Functional Ack 997 auto generated by Oracle B2B

Hi Friends,
How to set the AS2 fileName for outbound Functional Ack 997 auto generated by Oracle B2B.
External Trading Partner is sending the EDI 856 via AS2 URL to our Oracle B2B Server.
In the inbound 856 agreement, we have checked the option of Funtional Ack and also Functiona Ack handled by B2B is yes.
We have the outbound agreement which is sending that Functional ack 997 (auto generated by oracle b2b) and we have specified the Outbound AS2 channel of the Partner.
997 doc is being sent to external partner using AS2 channel, but the filename is generating as '40101'.
Please can you let me know how to set the AS2 fileName for outbound Functional Ack 997 auto generated by Oracle B2B.
Appreciate your valuable answers!!
Thanks,
Amirineni

Amirineni,
AFAIK, there is no option to set the file name when the 997 is generated automatically by B2B.
Alternatively, if this is a must requirement, you can generate the FA from backend and send to B2B with MSG_TYPE =9. In this case, you can set the header with filename (How to set the actionname property in B2B 11g)

Steps to Process standard EDI ANSI X12 997 file from AS2 Server

Hi All,
I have a scenario where we are receiving PO files from an EDI third party via AS2 adapter.
In return, we are sending PO Acknowledgement and Invoice files to the third party via AS2 adapter.
The fomat of the incoming and outgoing files are ANSI X12 (850 for PO, 855 for PO Ack and 810 for Invoices).
Currently client has informed that they are going to send an EDI ANSI X12 997 (Functional Ack) file for each PO Ack or Invoice they receive.
Kindly let me know steps to configure in SAP PI 7.1 to accept the inbound 997 files successfully and place them as it is in PI application server.
Regards,
Subhajit.

Hi , I too have the same requirement.
i am using
Jdev 11.1.1.6
Oracle Editor : 7.0.5.4016
Document Protocol : EDI_X12
Document type : 810 (Invoice )
Version: 4010
Weblogic server :11.1.1.6.0
I followed all the steps to create EDI X12 810 ecs file, converted this to .xsd and then to .dat in Oracle Document Editor as explained in the B2B user guide.
I also configured the trading partner , created agreements and deployed in B2B console. There is no mistake . as i can able to see the def file while configuring Oracle B2B in my Jdev.
I deployed the same process . But no instance is creating for my process. I also configured listing channel to Generic File 1.0. please help me out in this . Thank you.

Is it possible to catch Ack 997 in orchestration ?

it is possible that I could catch the ACK 997 message in an orchestration which receiving an inbound X12 210?
It seems that I only have a change to create a receive port and filter it to get Ack 997 after deploy the project.
If I could, I can manipulate it.

What do is not helpful?
You can reference the Microsoft.BizTalk.Edi.BaseArtifacts and you can see the schema, or you can put a send port
filter where BTS.MessageType="http://schemas.microsoft.com/Edi/X12#X12_997_Root"
If my explainations don't make sense, please explain how it doesn't make sense and this free technical support will assist
as we can.
We don't know where you are development wise, so help us help you...
Eric Stott [http://blog.biztalk-info.com] - Mark as Answer if this reply does.

Processing functional acks (997s)

Is that possible to process inbound 997s through Middleware from B2B and have B2B generate automatically 997s for outbound.
That means, for the transactions which we receive from the customer let B2B generate functional acks (997s) automatically and for the transactions which we send and functional acknowledgements (997s) which we receive from the customer should be processed through middleware.
I know we have at agreement level to specify for the functional acks but I am not sure is that possible to differentiate that for inbound 997s to be processed from B2B to middleware and for outbound 997s, let B2B handle automatically. Pls advise.
Regards,
Suneel Jakka

Suneel,
Yes, it is possible. In your outbound EDI agreement, enable the "Functional Ack" and select "No" in "FA Handled by B2B" drop-down. Note that "FA Handled by B2B" drop-down has three options - None, Yes and No. For passing inbound 997 to middleware, you must select "No".
In inbound EDI agreement, select "Yes" in "FA Handled by B2B" drop-down and B2B will handle the 997 automatically.
Regards,
Anuj

Functional Ack - 997

Hi,
Here is a scenario,
B2B is configured to send functional acknowledgement automatically. The Exchange Protocal being used is EDI X12 over generic exchange. Few of our customers require 997s for POs(850) Invoices(810) and ASNs(856).
There is an element called "Funcitonal Identifier Code" which has to be populated in GS-01 and AK1-01
Now the problem is:
1. This element is not getting populated in AK1-01.
2. Though this gets populated, the requirement is that this value is different from the one in GS-01. In GS-01 now its FA, and the value in AK1-01 should be PO.
Please let me know if any settings have to be made to get this AK1-01. I kno w that we can set the value in Document Definition parameters for GS01.
Thanks,
Phani

Hello Phani,
Interesting question. Ideally AK1 is used to respond to the functional group header and to start the acknowledgement for a functional group. There shall be one AK1 segment for the functional group that is being acknowledged. This is how
it should work.
1. The incoming business document has one Functional Identifier in the Group which is Code identifying a group of application related transaction sets. Ideally B2B gets this value from the business document and populate in the AK1-01 of
the Functional Acknowledgement. We have tested this in our environment using the default tutorial comes with the product.
2. If you still want to populate something different than the one in the incoming Business document- Functional Group Identifier code , even though it may not be a practical use case you can do this by generating the 997 in the Back end
application and have B2B to translate to EDI and post it to TP.
P.S GS-01 of the FA is not to do anything with AK1-01 of FA, where as AK1-01 of FA is same as GS-01 of Incoming business messages. A sample FA generated is as follows.
ISA~00~ ~00~ ~ZZ~Acme ~ZZ~GlobalChips ~071022~0933~U~00401~000001001~0~P~+'GS~FA~Acme~GlobalChips~20071022~0933~1001~X~004010'ST~997~1001'AK1~PO~1'AK2~850~0001'AK5~A'AK9~A~1~1~1'SE~6~1001'GE~1~1001'IEA~1~000001001'
HTH.
Rgds,Ramesh

EDI-ANSI X12 :::: 997

Hi All,
I am new to the EDI and getting confused with the ANSI X12 code 997. As I know that it's the Functional Acknowledgement, I cant able to get the use of it. Can any 1 please brief me abut this as we always get some errors regarding this during monitoring.
Please help me out.
Thanks.

Hey
A very simple example can be getting functional acknowledgment against Purchase Orders.
I recently worked on interface where the Business partner was sending us the purchase Orders(EDI 850) and we were sending back functional acknowledgment(EDI 997) stating them that we got their purchase order successfully and the data is in correct format.
Similarly you can get 997 against 810,860,820,830 etc
Thanx
Aamir

ALE, EDI and IDOCS

Hi
I am learning some stuff on ALE,EDI and IDOCS... are there any good sites which gives clear step by step procedure for the above.
Thanks in Advance.
Sudhi

Hi Sudhi
You can find details on SAP courses from your country's sap.com site. You can find links from http://www.sap.com/contactsap/countries/index.aspx .
Also some Education Partners of SAP give courses. Some info about these will also be there...
Regards...
*--Serdar

ALE , EDI and IDOC with MM??

hii
What is ALE, EDI and IDOC in SAP??
How its linked with MM??
Explain the above things with example
Thanks

Hi!
IDOC = Intermediate Document
IDoc or Intermediate Document is a standard SAP document format. IDoc's allow different application systems to be linked via a message-based interface.
For more detailled information look in SAPNET under
http://service.sap.com/EDI
For exapmle in purchasing:
The IDoc message type ORDERS is used to send a purchase order to a vendor.
EDI = Electronic Data Interchange
EDI stands for Electronic Data Interchange, which means that data is electronically transmitted from one system to another. The main requirement of EDI is that the systems of the communicating partners understand each other. Usually, the data from one partner gets mapped into the format of the other partner and vice versa.
Supporting this there exist EDI standards (named EDIFACT, ANSIX12, ODETTE, VDA, TRADACOMS, SPEC2000, ...), where the data formatting for exchanging documents are specified. Normally the partners agree using a special standard message (for example EDIFACT message ORDERS for a purchase order).
In the SAP system the outgoing data are stored in IDoc format. When processing a receiving document, the Inbound SAP system receives the data in IDoc format too.
Further processing (converting/mapping from IDoc in another format and vice versa) depends on the partner agreement:
If the partners have agreed using a special EDI standard, mapping between IDoc and the EDI standard is necessary. This mapping is not supported by SAP, external converters or EDI subsystems must be installed by the customers for this purpose.
If both systems use SAP software, there is usually no need for mapping (which can save users a lot of money). The two systems are often connected via ALE (Application Link Enabling).
If partners are using XML, the SAP Business Connector can be used. The business connector is a tool used to help customers connect via EDI. It includes routing and mapping and is XML compatible. To read more about XML at SAP go to SAPNet Alias 'XML' (http://intranet.sap.com/XML).
For example:
Vendor can send the invoice by EDI creating an IDoc with message type INVOIC using IDoc Type INVOICxx. He can determine (depending on the partner agreement) how to create an IDoc for Inbound processing with FI or MM-IV.
ALE = Application Link Enabling
ALE is short for Application Link Enabling. Special Basic programs support this functionaliity (see documentation of BC_MID_ALE).
To link applications you have to configure an ALE model. It contains all relevant data about how a system's configuration (normally a central system and assigned local systems) exchange data.
With help of the ALE technology, the distribution of contracts is possible in MM via the following business process:
Contracts that a central purchasing organization distributes to local purchasing organizations to allow the latter to utilize the more favorable conditions they contain for the procurement of materials or external services.Each local purchasing organization sends information on its own release orders back to the central purchasing organization.
For this purpose the contract in the central system can be copied to the local systems (with message BLAORD and COND_A). When a release order to a distributed contract is created in a local system, the release docu is automatically sent to the central system (with message BLAREL) updating the release docu of the contract in the central system.
Precondition for this scenario is, that in all systems the used master data (material, vendor, sources of supply, ...) are the same. This master data can be distributed by ALE, which should be done before sending the contract from the central system. Available message types for distribution of master data are:
MATMAS (ARTMAS in retail system) for material master
CREMAS for Vendor master
INFREC for info record
SRCLST for source list
COND_A for conditions of info record
SRVMAS for service master data
Technical documentation to ALE can be found by path:
Basis Components / Middleware (BC-MID) / Application Link Enabling (BC-MID-ALE)
The most important Transactions for testing Idoc:
WE02 Display IDOC
WE05 IDOC list
WE19 Testing IDOCs
BD87 Status Monitor for ALE Messages (reprocess)
Notes:
456127 FAQ: Electronic Data Interchange (EDI) in Purchasing
536411 Sample scenario for ALE contract distribution (only internally released)
I hope I could help you fruther
Best regards
Erika

Configuration of EDI and ALE

Hi,
I am new to Idocs i would like to know the cofiguration settings for EDI and ALE from starting.I know abt creating partner profiles and the other stuff. I would like to know in detail. Please let me know.
Thanks in Advance,
Srikanth.N

Hi
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
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.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
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.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
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
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
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.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
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
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
>>>> SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
Check these links.
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.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
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
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
Please check this PDF documents for ALE and IDoc.
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
Outbound:
Step 1. Application document is created when transaction is saved.
         2. Message control is invoked.
         3. Messages are processed by system.
         4. Messages are Edited (if desired).
         5. Output (ALE / EDI) is checked
         6. Validate against Message control record from Partner Profile
         7. Application Document is saved.
         8. Entry NAST table is created for every selected output program
              along with Medium & Timing.
         9. Check for Process Immediately .
                 If (yes)
                   Determine Processing Program from TNAPR Table.
                 ELSE
                   Execute RSNASTED Program.
       10. Read Partner Profile to determine Process Code.
       11. Process Code points to the Function Module & Invoked.
       12. IDoc is generated.
       13. Check for ALE Request.
                    if (Yes)
                        Perform Filters, Conversions, Version Changes etc.
                    Else.
                        IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
        2.   Subsystem calls Functional Module                                 EDI_DATA_INCOMING from startRFC program.
         3. Data in Control Record is validate against the Partner                       Profile.
        4. IDoc is generated in Database and syntax check is                      carried out.
        5. IDoc file is deleted once file read.
        6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
                   7. Check for Process Immediately.
               If NO
                 Execute RBDAPP01 Program
               Else
                  Read Process Code from Partner Profile
                       Process Code Points to Function Module
                 Application Document Posted.
further help:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
<b>Reward points for useful Answers</b>
Regards
Anji

Diff between EDI and ALE

Cand any one of you tell me exact difference between EDI and ALE

hi praneeth,
ALE: Application link enabling is a methodology used to transfer data between two applications
EDI (Electronic Data Interchange) is the standards to integrate data between those applications who support these standards
IDOC s are converted into a standard text format by EDI and send it to receiver application which is able to interpret that message means which support edi standards.
PLS refer existing threads, articles,blogs b4 posting
Regards,
Mandeep Virk

Diff Btn EDI and ALE

Hi Experts,
What is the diff btn EDI and ALE.
Straight answers will be rewarded.
Regards,
SAI

Hi,
In simple words ...
ALE is technology for SAP mainly use to transfer data between SAP systems.
EDI is the independent technology use to transfer data between two systems, they can be SAP systems or non SAP systems.
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.
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.
Regards,
Padmam.

EDI and ALE

hi,
can anyone tell what are the table get affected while using EDI and ALE , and also with their explanation.
thanks
Ganesh

ALE tables.
EDMSG - logical message type
TBD05 - distribution model for message type
TBDLS - logical system
TBD00 - view of customer model
TBD10 - idoc field in ALE objects
BDCP - change pointer
CDHDR - chnage document header
CDPOS - change document item
TBD21 - ale idoc reduction
TBD30 - ale conversion rule
TBD11 - ale object type
EDI Tables
EDI_DC40 - Idoc control record structure
EDI_DC - Control record structur
EDIDC - Idoc control record
EDI_DD40 - Idoc data record structure
EDI_DD - data record structure
EDID4 - Idoc data record from v4
EDID2 - Idoc data record from v3
EDIDS - status record idoc
EDIDD - data record idoc
EDID3 - Idoc data record from v3

EDI and Ack 997

Similar Messages

Maybe you are looking for