sap edi config document - complete (03!23!2014)
TRANSCRIPT
SAP EDI Tables:WE20 Partner ProfileWE02 – idoc listBD87 – To check and process i-docsWE31 – Create SegmentWE05 – See i-docWE19 – Modify i-doc and repost to create new idocWE81 – Create New Message TypeWE21 – Create Ports
Create Logical System:Go to transaction SPRO and press SAP Reference IMG for creating the logical system for source and destination.
Click the node define logical system from SPRO -> SAP Reference IMG -> SAP customizing Implementation Guide -> SAP xApp Resource and Portfolio Management (SAP xRPM) -> Base system Interfaces -> SAP Human Capital Management Integration -> Common system configuration and SAP HCM ALE setup -> Application link enabling (ALE) -> Basic Settings -> Logical Systems -> Define Logical System
Else go to transaction SALE then go to Basic settings-> logical system then Define logical system. We can create the same.
Message Output Configuration:
1. Condition TableSPRO >Material Mangement> Purchasing -> Message -> Output Control->Condition Tables->Define Condition Table for Purchase Order Select:Purchasing Doc. Type,Purch. Organization,Vendor2. Access SequencesSPRO -> Material Management-> Purchasing -> Message -> Output Control->Access Sequences->Define Condition Table for Purchase Order3. Message TypeSPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Types->Define Message Type for Purchase Order4. Message Determination Schemas4.1. Message Determination SchemasSPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Maintain Message Determination Schema4.2. Assign Schema to Purchase OrderSPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Assign Schema to Purchase Order 5. Partner Roles per Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control-> Partner Roles per Message Type ->Define Partner Role for Purchase Order6. Condition RecordNavigation Path: SAP Menu-> Logistics -> Material Management -> Purchasing-> Master data->Messages-> Purchase Order-> MN04-> CreateNow you create PO (ME21N) and save it. Go to ME22N and print the PO by giving output type.
1. What is the difference Between IDOC type and Message type? How to link the IDOC type with Message type?Message type gives the meaning of the IDOC . IDOC type gives the structure of an IDOC.The messages exchanged between systems are of various message types. The message type depends on the data contained and the process involved. It determines the technical structure of the message and the IDOC type.The IDoc type indicates the SAP format that is to be used to interpret the data of a business transaction.
EDI Message Output – for PO change / Create
Set-up PO Message Output Determination Procedure:
Step 1 : Transaction – NACE
Step 2 : Select ProceduresVerified in the SPRO that the active procedure in SPRO is RMBEF1.
Step 3 : Select EF and select Output types
Step 4: Double click the Output type NEU
Step 5: Verified the following 2 options are checked.
Step 6 :Now Click on the Processing Routine.
Step : 7Need to verify that there is an entry for Medium for ALE Processing.
Setting-up Message Output : Condition Records
Step 1 : Now In the Main screen , select EF and Condition records
Step 2 : Select NEU output type and select Condition Records
Step 3 : Select one Document Type option from the following popup.
Step 4 : Create a new record with the Document type and Partner type LS
Step 5 : In transaction WE21 Enter Create a record for the Sender system with theMessage type ORDERS and IDoc Type ORDERS05.
EDI / ALE Difference:ALE Technology : Application Link Enabling (ALE) is a technology to create and run distributed applications. ALE Technology is proprietary of SAP.
ALE Objectives - ALE incorporates controlled exchange of data messages ensuring data consistency across loosely coupled applications. ALE comprises of three layers. Application Services Distribution Services and Communication Services .Basic principle of ALE is to provide a distributed and fully integrated R/3 system. Each application is self-sufficient. The use of self-sufficient system implies a certain measure of data redundancy.Hence data has to be both distributed and synchronized.
Difference Between ALE and EDI :Normally we refer to EDI technology when a non SAP system is one of the communication channel. ALE communication occurs from the SAP side and EDI from the non-SAP
side. IDOCs uses ALE and EDI to deliver the data to the receiving system. If the data needs to be exchanged between two SAP systems, then IDOC uses ALE technology . For the exchange of data between a SAP and Non SAP system, IDOC uses EDI subsystem to convert and deliver the data.
ALE Communication Diagram