In any SAP EDI Process a Sub System is required. Basically an EDI Subsystem does the conversion of SAP IDOCs to to EDI fromat and Vice Versa. An EDI subsystem is a thirdparty systems and deals with standards that are most current. Thus as mentioned above the EDI SubSystem acts like a translator. SAP does certify some EDI subsystems and this is based on the version of SAP.
Basically the SAP EDI process is comprised of
OutBound Process InBound Process
OutBound Process
The OutBound Document is Created. This could be a Sales Order or a Purchase Order or an Invoice. The process of creating the document is no different than the normal way. But prior to this IDOC configuration is made so that on the document is saved an IDOC is generated. The document is saved in the SAP tables in the usual way but in addition to that an IDOC with the same data is also generated and saved. You can view this IDOC using the appropriate transactions. Example WE05 --- IDOC List WE02 Display IDOC. Once the IDOC is generated it is transferred to the operating system level for the EDI system to pick it up. Further to this the IDOC is converted to the EDI standards and the IDOC is then transferred to the desired Partner. The status of this transaction is sent back to SAP.
The following types of Purchasing Documents are present in SAP.
Request For Quotation (RFQ).
This document is sent to the potential vendor. This basically is a request to the vendor to send the quotation for a material or a service.
OutBound Process From Company ----------------------- Vendor From SAP -------------------------------- Non SAP/SAP
Related Transactions: Create ME41, Change ME42, Display ME43, Maintain Supplement ME44, Release ME45 List Display: By Vendor ME4L, ME4M by Material, By Service MSRV4, By Collective Number ME4S, By Material Group ME4C, By Tracking Number ME4B, By RFQ Number ME4N, Transaction Per Tracking Number MELB. Reporting: General Analysis ME80AN, Archived Purchasing Documents ME82
Quotation.
When the receives the RFQ he responds to it by sending the Quotation. The quotation basically contains the prices and conditions and helps in selecting the Vendor.
InBound Process Vendor ------------------------------- Company Non SAP/SAP ---------------------- SAP
Related Transactions: Maintain ME47, Display ME48, Price Comparison ME49. Purchase Order
This is basically a document that makes request for buying the material or service. the vendor does that supply the material or does not provide the service till the point he receives this document. This document formalizes a purchase transaction.
OutBound Process From Company ----------------------- Vendor From SAP -------------------------------- Non SAP/SAP
Related Transactions: Create (Vendor/Supplying Plant Known) ME21N, Vendor Unknown ME25, Via Requisition List ME58, Automatically via Purchase Requisitions ME59. Change ME22N, Display ME23N, Maintain Supplement ME24, Release ME28, Mass Maintenance MEMASSPO.
List Displays: By Vendor ME2L, BY Material ME2M, By Material Group ME2C, By Tracking Number ME2B, By PO Number ME2N, By Supplying Plant ME2W, Transactions per Tracking Number MELB.
For Account Assignment: General ME2K, By Project ME2J.
Reporting: General Analysis ME80FN, Analysis of Order Values ME81N, Achieved Purchasing Documents ME82, SC Stocks per Vendor ME20, Monitor Confirmations ME2A
Contract
This is basically a 'CONTRACT' between the vendor (external entity) and the Company (SAP) and is a legal binding for buying certain material or service over a period of time. The time is specified.
OutBound Process From Company ----------------------- Vendor From SAP -------------------------------- Non SAP/SAP
This is an agreement, or a long term buying arrangement. Basically it defines the delivery schedules. It provides for the creation of delivery schedules and specifies purchase quantities, delivery dates, and defines precise times of delivery over a predefined period.
OutBound Process From Company ----------------------- Vendor From SAP -------------------------------- Non SAP/SAP
Related Transactions: Create Vendor Known ME31L, Stock Transport Scheduling Agreement ME37, Change ME32L, Display ME33L, Maintain Supplement ME34L, Release ME35L
Always use Pretty Printer and Extended Program Check before releasing the code.
Do not leave unused code in the program. Comment the code thoroughly. Align the comments and the Code. Follow the SAP Standards and SAP Best Practices guidelines. It’s a good practice to take a dump of the code on your local drive.
