Your SlideShare is downloading. ×
Ale edi
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
561
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
37
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. EDI-ALE Information Exchange 1
  • 2. Amit Trifaleamit.trifale@capgemini.comCell: 98334 29239Ext: 7345 2
  • 3. Introduction EDI-ALE Overview Conceptual flow EDI Setup ALE setup Assignment 3
  • 4. EDI-ALE Overview What is EDI? What is ALE? Why do we need EDI-ALE? 4
  • 5. EDI-ALE Overview Benefits –  Reduced Data Entry Errors  Reduced Processing Cycle time  Availability of Data in electronic form  Reduced Paperwork  Reduced Cost  Reduced Inventory and better planning  Standard means of communication  Better Business Process  Competitive Advantage 5
  • 6. EDI-ALE Overview Document Exchange: Customer Vendor RFQ Quotation Purchasing Purchase Order Sales Order Acknowledgement Purchase Order Change Shipping Notice Receiving Shipping Invoice Accounts Accounts Payment Details Vendor Customer Bank Bank 6
  • 7. EDI-ALE Overview Jargons in EDI-ALE:  IDOC  Control Record  Data Record  Status Record  IDOC Type (WE30/31)  Eg: ORDERS02  Message Type (WE81/82)  Eg: DELINS  Output Determination/Output Type  RFC Destination (SM59)  Process Code (WE41)  Port (WE21)  Partner Profile  EDI Subsystem 7
  • 8. EDI-ALE Overview EDI Standards  Messages  856 – DESADV  850 – ORDERS  830 – DELINS  810 – INVOIC  File Standards  ANSI X12  EDIFACT  VDA  Translators 8
  • 9. Conceptual flow Outbound FlowApplication Output Output Partner Profile Process FunctionDocument Determination Type RSNAST00 code Module File to IDOC EDI IDOC Port RFC Destination File Subsystem 9
  • 10. Conceptual flow Inbound Flow File From IDOC Process EDI RFC Start RFC IDOC Partner Destination File Profile codeSubsystem Function Application Module Document 10
  • 11. EDI Setup Inbound Processing:  Partner Profile  Partner Number  Message Type  Process code  Table Entries  EDPAR  EDSDC  KNMT 11
  • 12. EDI Setup Outbound Processing:  Output Determination  Partner Profile  Partner Number  Port/RFC Destination  Message Type  Output Type  Process code 12
  • 13. ALE Setup ALE – Distributed Processing  Geographical Location  Consolidation  System Capacity  Mission-Critical Applications  Upgrading a module separately  Data Security  Business Reasons IDOCs  Master IDOC  Communication IDOC 13
  • 14. ALE Setup Filtering  Filtering at IDOC Level (BD59)  Segment Filtering (BD56)  Reduced IDOC Type (BD53) 14
  • 15. ALE Setup Outbound Processing:  Maintain Logical system  Assign Logical system to Client  Setup an RFC destination (SM59) (Name same as Logical System Name)  Port Definition  Maintain Customer Model (BD64)  Generate Partner Profile (BD82)  Distribute Customer Model (BD64) 15
  • 16. ALE Setup Master Data Distribution:  Stand alone Program (Eg BD10)  Change Pointers  Enable Change Pointers Globally (BD61)  Enable Change Pointers for a Message Type (BD50)  Specify Fields for which Change Pointers are to be written (BD52)  Execute Program RBDMIDOC 16
  • 17. Assignment Simulate an Inbound ORDERS. Add code in user exit to create Purchase Order. Trigger an outbound Purchase Order giving reference of Sales Order Number in Extended IDOC. Trigger PO from one system and it should create SO at other system. Create your own message type, assign IDOC type, Extension and process code to it. Create your own function module and assign it to Process code. Use this process code in Z message type. Create Message type/IDOC type/Process Code/Function Module to create a Inbound Delivery and do a GR on it. 17

×