Topics to cover

 What is EDI, ALE ?  Components of ALE, EDI.  IDOCS - Introduction, Applications, Structure  ALE Processing  Transactions For Testing, Monitoring Interface and Processing IDOCS. ALE in typical Project Scenario.  Questions

Slide 1

| 6/3/2013

Let‟s Understand EDI, ALE and Standards

It is not easy to define EDI in strict terms
-

EDI defines the paradigm of exchanging data electronically more than anything else It is easier to describe the commonly used EDI practices The collection of these common practices amounts to what is known today as EDI EDI can be thus described as an information sharing system  utilizing an intermediate message store-and-forward entity and  premeditated message syntax and interaction processes  which are modeled by trading partners around standard templates

-

-

-

Slide 2

| 6/3/2013

EDI Basics

 The basic EDI structure is given below
-

Each partner has their own internal software systems Special EDI adapters have to be implemented which will be able to interface with the internal system as well as communicate with the value added network The particulars of the message syntax and interaction process are negotiated between partners in advance Sometimes a dominant partner will impose its standards on smaller partners

-

-

Slide 3

| 6/3/2013

EDI Document Flow

Document

Company A

Company B

R/3 System

R/3 System

IDOC Transaction (X12) or Message (EDIFACT)

IDOC

EDI Subsystem
VAN

EDI Subsystem

Slide 4

| 6/3/2013

EDIFACT

 EDIFACT stands for EDI For Administration, Commerce and Transportation

 It has been introduced by the UN center for the facilitation of administration, commerce and transportation (UN/CEFACT) in the mid 1980s

 Older European EDI standards such as TRADACOM, GENCOD, SEDAS and ODETTE have all migrated to EDIFACT

 EDIFACT has furthermore become an international standard as ANSI has stopped all work on X12 since 1997 and X12 systems are migrating to EDIFACT

Slide 5

| 6/3/2013

EDIFACT Structure
 EDIFACT Interchanges consist of messages which are in turn composed of data segments  The segments themselves consist of data elements

Interchange
I’change Header

Message
Data Segment
Data Element

Message
Data Segment
Data Element

Message
Data Segment
Data Element

I’change Header

Message Header

Message Header

Slide 6

| 6/3/2013

their Responsibilities Subsystems  Mercator  Gentran Responsibilities  Partner Profiles  Addresses  Translator  Message Handling  Communication  Archiving  Monitoring Slide 7 | 6/3/2013 .Common EDI Subsystems.

ALE!! What is it ?? It is a set of Tools.  programs and  data definitions  that provides the mechanism for distributing functionality and data across multiple system. Slide 8 | 6/3/2013 .

etc. etc. Sales Orgs. Separate Treasury. FI.What Data can be Exchanged ? Transaction Data –SD. Vendor. Data –Material. distributed applications –Separate HR. Customer. Slide 9 | 6/3/2013 . Master Control Data required to enable tightly coupled. etc. MM. etc. Data –Organizational Reference Information •Plants. CO.

EDI. Applications. Structure.  ALE Processing  Transactions For Testing. ALE in typical Project Scenario.  IDOCS .  Questions Slide 10 | 6/3/2013 .Introduction.Topics to cover  What is EDI. ALE ?  Components of ALE. Monitoring Interface and Processing IDOCS.

Components of ALE Services: Application Services Distribution Services Communication Services Tools: Customizing Tools Development Tools Slide 11 | 6/3/2013 .

MM etc.Application Services Services: Application Services Distribution Services Communication Services Tools: Customizing Tools This is where the SAP applications ( SD. FI. ) generate their data and documents Development Tools Slide 12 | 6/3/2013 .

Distribution Services Services: Application Services Distribution Services Communication Services Tools: Customizing Tools Development Tools Recipients  Formats and Filters the data  Creates IDocs ( Intermediate Documents  Slide 13 | 6/3/2013 .

Communication Services Services: Application Services Distribution Services Communication Services •TCP/IP •RFC Tools: Customizing Tools •tRFC • etc Development Tools Slide 14 | 6/3/2013 .

) Tools: Customizing Tools Development Tools Slide 15 | 6/3/2013 . (for configuring the flow of data Services: Application Services Distribution Services Communication Services between systems ) Shared Master Data(SMD)tools (for distributing master data )  Customization parameters filtering and (within SAP for IDoc conversion.Development Tools  Model Maintenance Tool.

Customizing Tools Services: Application Services Distribution Services Communication Services Tools: Customizing Tools Development Tools Tools for creating and modifying IDocs Slide 16 | 6/3/2013 .

Create IDOC Comm.In a Nut Shell Application Layer Distribution/ ALE Layer Communication Layer Application Master IDOC Determine Receipients Filter/Convert Data. IDOC Slide 17 | 6/3/2013 . IDOC Carrier Application Data Application Functions Filter/Convert Data Comm.

IDOC Applications EDI Message R/3 System ALE Workflow Electronic Form IDOC Form Feed Flows ICR/ OCR Document Legacy R/2 System WWW Message Slide 18 | 6/3/2013 .

: MATMAS. IDOC: An IDOC is an „Instance‟ of an IDOC Type.Message Type. eg: MATMAS03. IDOC – Definitions Message Type: A message type represents the application message being exchanged between R/3™ systems and R/3™ and an external system. INVOIC02. INVOIC IDOC Type: An IDOC type represents the structure of the data associated with a message type. e. it is an object with the data of a particular message type in it. Slide 19 | 6/3/2013 .g. IDOC Type.

IDOC .Structure Control record IDoc-ID Partner IDoc Type / logical message Data records Control area Application data Status records IDoc-ID Status information Slide 20 | 6/3/2013 .

IDOC Structure – Contd. E1HDDOC M 1 E1TLSUM C 2 E1HDADR C 5 E1ITDOC M 1 E1ITSCH Tree of Segments Slide 21 | 6/3/2013 C 99 C 5 .

Control record Data Record Status Record IDOC “Intermediate Document” Slide 22 | 6/3/2013 .

Slide 23 | 6/3/2013 .Control Record The very first record of an IDoc package is always a control record. The structure of this control record of the structure EDIDC and describes the contents of the data contained in the package.

with a segment information part and a data part. They are all structured alike. are the IDoc data. which is 1000 character in length. filling the rest of the line. which come after the control record.Data Record All records in the IDoc. Slide 24 | 6/3/2013 .

Status Record Information about the IDoc status like: IDoc identification number Status number .table verified IDoc type Direction Data and time stamp Slide 25 | 6/3/2013 .

Typical Business Scenario Organization Create SO ORDERS Customer 850 ORDRSP Create PO Order Resp Receive Del Del Resp INVAOIC 855 Create Del / Goods issue Del Bill Block TXTRAW DESADV 856 824 810 Receive Inv Update Status TXTRAW 824 Inv Response Slide 26 | 6/3/2013 .

Another Business Scenario – Interface with Warehouse Management System Picking Request PICKSD External Warehouse Management System Picking Confirmation SDPICK SAP R/3 Application WMMBXY Inventory Status Change Production Receipts Inventory Reconciliation Slide 27 | 6/3/2013 .

Monitoring Interface and Processing IDOCS. Structure .Outbound Processing ii.Topics to cover  What is EDI.Introduction. ALE in typical Project Scenario.Inbound Processing  Transactions For Testing. i.  ALE Processing.  Questions Slide 28 | 6/3/2013 . Applications.  IDOCS . ALE ?  Components of ALE. EDI.

Outbound Processing Slide 29 | 6/3/2013 .

PP modules Slide 30 | 6/3/2013 .Outbound Processing With Message control – SD & MM modules Without Message Control – FI.

What is message Control? Transactional Document (Sales Order) (Billing Document) Message Control Printed Document E-mail EDI IDOC ALE IDOC Fax Slide 31 | 6/3/2013 .

Outbound processing and message control SAP Application document find message control edit process NAST record IDoc Interface/ALE Services Slide 32 | 6/3/2013 .

g.g. e. RSNASTED Slide 33 | 6/3/2013 output.message control SAP application edit application data message finding NAST record message proposal Processing (Table TNAPR) processing program. e. IDoc .

Condition elements SAP application 1:n procedure m:n condition type n:1 access sequence m:n access to table Slide 34 | 6/3/2013 .

message processing Check NAST Record Read Partner Profile Call Selection Module (by Application) Call ALE Services Transfer according to OUTMOD TNAPR R S N A S T E D '3'/ '4' '1'/ '2' Single IDoc Slide 35 | 6/3/2013 IDoc Batch via RSEOUT00 .

-IDoc Comm.-IDoc 3rd Party / Legacy System / R/3 Slide 36 | 6/3/2013 .-IDoc Comm.Outbound – Without Message Control SAP Application Master-IDoc Temporary Document IDoc Interface/ALE Services Multiple Documents Created Comm.

RFC or EDI Application document posted simultaneously with IDOCs Database Version change Dispatch control Links C C Slide 37 | 6/3/2013 . layer Create master IDOC M Receiver determination Segment filter Field value conversion asynch.Outbound processing Application posting Need to create IDOC? ALE layer Customer Distribution Model Comm.

layer Customer ALE supplies APIs (function modules) to allow applications Distribution Model to query the model -   Create master IDOC M Receiver determination Segment filter Field value conversion Is anybody interested in my message type? asynch.Querying the Model Application posting Need to create IDOC? ALE layer Comm. Optional: what filter objects are they interested in? or RFC EDI RFC asynch. or EDI Application document posted simultaneously with IDocs Database Version change Dispatch control Links C C Slide 38 | 6/3/2013 . layer Comm.

RFC or EDI Segment filter Field value conversion Application document posted simultaneously with IDocs Database Version change Dispatch control Links C C Slide 39 | 6/3/2013 . layer Create master IDOC M asynch.The application Technically it is stored as an internal table .Handover IDoc to ALE Application posting Need to create IDOC? ALE layer Customer Distribution Modelcreates the IDOC .Passed to ALE via an API Receiver determination (function module) - Comm.

layer - Create master IDOC M Receiver determination Segment filter Field value conversion If the application has no specified recipients asynch.Receiver determination Application posting Need to create IDOC? ALE layer Customer Distribution Model Comm. RFC  ALE refers to the customer or to determine distribution model EDI RFC them asynch. Application document posted simultaneously with IDocs Database Version change Dispatch control Links C C Slide 40 | 6/3/2013 .  Data not relevant or to receiver (according to model) is removed EDI in ALE layer.

Segment filter Application posting Need to create IDOC? ALE layer Customer Distribution Model - Comm. can be removed The filter is message and receiveror specific EDI asynch. layer Create master IDOC M Receiver determination Segment filter Field value conversion - The filter is data-independent or IDOC segments that are not EDI RFC required asynch. RFC Application document posted simultaneously with IDocs Database Version change Dispatch control Links C C Slide 41 | 6/3/2013 .

layer Create master IDOC M Receiver determination Segment filter Field value conversion - The contents of individual or fields can be EDI RFC asynch. RFC Application document posted simultaneously with IDocs Database Version change Dispatch control Links C C Slide 42 | 6/3/2013 .Field value conversion Application posting Need to create IDOC? ALE layer Customer Distribution Model - Comm.  translated to new values or  suppressed EDI The filter is message and receiver-specific asynch.

versions or Systems with different release EDI levels can communicate without additional application logic Application document posted simultaneously with IDocs Database Version change Dispatch control Links C C Slide 43 | 6/3/2013 . layer Create master IDOC M Receiver determination Segment filter Field value conversion - asynch. layer Comm. RFC or EDI RFCto older IDOCs can be changed asynch.Version change Application posting Need to create IDOC? ALE layer Customer Distribution Model Comm.

RFC or EDI Application document posted simultaneously with IDocs Database Version change Links C Links are written between IDOC and  Application object contained in IDOC  Communication-Layer's Dispatch "Transaction-ID" control C - Slide 44 | 6/3/2013 . layer Create master IDOC M Receiver determination Segment filter Field value conversion asynch.Make Links Application posting Need to create IDOC? ALE layer Customer Distribution Model Comm.

packet size is determined Field value conversion Application document posted simultaneously with IDocs Database - Version change Dispatch control Links C C Slide 45 | 6/3/2013 . Technical comms parameters are or defined EDI EDI or aRFC (asynch. layer Create master IDOC M Receiver determination - Segment filter - asynch. remote function call) Send immediately or cumulate and send via batch job  If batch. RFC or EDI RFC asynch.Dispatch control Application posting Need to create IDOC? ALE layer Customer Distribution Model Comm.

Inbound Processing Slide 46 | 6/3/2013 .

Inbound Processing With ALE SAP Application IDoc Interface/ALE Services 3rd Party / Legacy System / R/3 Slide 47 | 6/3/2013 .

Comm. RFC or EDI Segment filter Field value conversion Input control A Process IDOC A Serialization Simultaneously update IDOC's status Database Post application document Slide 48 | 6/3/2013 . layer C ALE layer Application posting Version change asynch.Inbound Processing.

Input Control Comm. layer C Version change For each message type and sender one can define Segment filter  when to process asynch. RFC (immediate/batch) or  whether to call application Field value conversion EDI directly or start customer workflow Input  who should get work items in control case of error Incoming IDOC packets are passed to A application Serialization - ALE layer Application posting A Process IDOC Simultaneously update IDOC's status Database Post application document Slide 49 | 6/3/2013 .

RFC or EDI - Segment filter Field value conversion Input Inbound IDOCs are passed to control the application via a standardized function A Serialization interface A Process IDOC Simultaneously update IDOC's status Database Post application document Slide 50 | 6/3/2013 .Application Input Comm. layer C Version change ALE layer Application posting asynch.

the IDOC containing it has been overtaken (by the IDOC containing the later change) Input control - ALE layer Application posting When processing the A Process IDOC A Serialization Simultaneously update IDOC's status Database Post application document Slide 51 | 6/3/2013 . 2. layer C Version change Segment filter asynch. 1 arrives after change No. RFC inbound IDOC.Serialization Comm. the or application can call an ALE Field value conversion EDI(function module) to API check that the IDOC has not been overtaken  If change No.

etc )  Define RFC Destinations  Define Ports  Maintain Customer Model  Create Partner Profiles Slide 52 | 6/3/2013 .Basic Configuration Elements  Create and allocate Logical System  Define Ranges (Idocs. Ports.

Logical System TCODE: BD54 Slide 53 | 6/3/2013 .

Allocate Logical System to the client TCODE: SCC4 SALE > BASIC SETTINGS > SET UP LOGICAL SYSTEM > ASSIGN LOGICAL SYSTEM TO THE CLIENT Slide 54 | 6/3/2013 .

Number Ranges     Maintain number ranges for ports Maintain number ranges for IDocs Maintain number ranges for IDoc types and segment version Maintain number range for change pointers Slide 55 | 6/3/2013 .

Maintaining RFC Destinations TCODE: SM59 Slide 56 | 6/3/2013 .

Slide 57 | 6/3/2013 .Displaying and Maintaining Ports TCODE: WE21 A port is a logical representation of a communication channel in SAP with the data communicated being IDocs.

Partner Profiles TCODE: WE20 Slide 58 | 6/3/2013 .

Partner Profiles-Outbound Slide 59 | 6/3/2013 .

Partner Profiles-Inbound Slide 60 | 6/3/2013 .

Distribution Model TCODE: BD64 Slide 61 | 6/3/2013 .

Filter Objects BD95 BD59 Slide 62 | 6/3/2013 .

Scenario analysis • How does the IDOC look like ? • How is data being sent ? • How is the data being received ? Slide 63 | 6/3/2013 .

Idoc Segments TCODE: WE31 Slide 64 | 6/3/2013 .

Idoc Types TCODE: WE30 Slide 65 | 6/3/2013 .

Message Types WE81 WE82 Slide 66 | 6/3/2013 .

FM Assignment to Message Type and IDoc type TCODE: WE57 Slide 67 | 6/3/2013 .

Process Codes WE41 WE42 Slide 68 | 6/3/2013 .

Process Codes in Inbound and Outbound TCODE: WE64 Slide 69 | 6/3/2013 .

Sending Master Data Idocs Master data ? Y Only send objects that have changed ? Y Change Pointer available? y Change Pointer based Program Standalone with custom logic to keep track of changes N Standalone program with user-definable selection criteria N Slide 70 | 6/3/2013 .

Sending Transactional Data Idocs Transaction Data ? Y Ensure transactional Integrity? Y Output Determinat ion available ? y Output determination based Program User-Exit available? N N See Master data N hard coded ALE layer Modification Y Hardcoded ALE layer no Modification Slide 71 | 6/3/2013 .

Change Pointers Application Posting • Post Application document Master data Batch Program (RBDMIDOC) • Determine IDOC module • Call IDOC module • Create Change Document • Are changes ALE relevant ? •Write Change Pointers • Commit Work ALE configuration • ALE relevant Fields IDOC Module • Read Change Pointers • Fill IDOC • Call ALE layer • Update Change Pointer Change pointers ALE layer Slide 72 | 6/3/2013 .

 Change Pointers BD61 BD50 Slide 73 | 6/3/2013 .

 Change Pointers… Continued BD52 BD60 Slide 74 | 6/3/2013 .

ALE Configuration For Change Pointers • Define change pointer creation • Define which change document fields are to be logged • Change pointer activation • • Activate generally Activate per message type • “Publish” new function module • Link message type to function module Slide 75 | 6/3/2013 .

FM For Inbound EDI TCODE: BD67 Slide 76 | 6/3/2013 .

Message func.ALE Inbound configuration IDoc control record IDoc type Send. Input type Dialog? Appl. Slide 77 | 6/3/2013 . partnr type Sender partner no. Message func. Message type Message variant Message function Test flag Partner Profile inbound Process code tables (inbound) Function module's attributes ALE function module registry IDoc type Sender type Sender no. Process code Process type Error events Appl. Inbound func. Message type Message var. obj. type Inbound func.type Inbound func. Fest flag Process code Message type Message var.obj.

 Questions Slide 78 | 6/3/2013 . Applications.  ALE Processing. Monitoring Interface and Processing IDocs.  Transactions For Testing. ALE in typical Project Scenario. ALE ?  Components of ALE.  IDOCS .Introduction.Topics to cover  What is EDI. Structure. EDI.

Testing tools .Outbound Application NAST WE15 IDOC Interface WE14. WE19 External System (Port) Slide 79 | 6/3/2013 .

Inbound Application Workflow WE19 IDoc Interface WE16 Outbound IDoc File WE12 Inbound IDoc File File System Slide 80 | 6/3/2013 .Testing tools .

Testing tool – Status report Application Workflow IDoc Interface WE17 Status report File System Slide 81 | 6/3/2013 .

Consolidated Application NAST WE15 Workflow WE19 IDoc Interface WE14. WE19 WE16 WE17 External System (Port) Outbound IDoc-File WE12 Inbound IDoc-File Statusreport File system Slide 82 | 6/3/2013 .Testing tools .

set Port accordingly) Read NAST record Transfer from interface to further inbound processing Transfer to IDoc interface Transfer to arbitrary port (outbound) : WE15 : WE19 (direct function module call) : WE19 (outbound and standard inbound) : WE19 Slide 83 | 6/3/2013 . WE17 (inbound status report). WE19 (outbound.When to test which program Exchange with file system : WE16 (Inbound).

(Default.List Of All IDocs Created. EDI)-. Additional.WE02 Slide 84 | 6/3/2013 .

Idoc Search For Business Contents (Database). WE09 Slide 85 | 6/3/2013 .

Process All Selected IDocs WE14 Slide 86 | 6/3/2013 .

Selection Program For Issuing Output WE15 Slide 87 | 6/3/2013 .

Program for Triggering Inbound Processing WE16 Slide 88 | 6/3/2013 .

Program for Trigger status Processing WE17 Slide 89 | 6/3/2013 .

Test Tool For IDOC Processing WE19 Slide 90 | 6/3/2013 .

Select IDocs BD87 Slide 91 | 6/3/2013 .

Status Conversion With TRFC Execution BD75 Slide 92 | 6/3/2013 .

ALE error handling flow with Workflow User action R/3 action Error in inbound function module ALE triggers error ev ent i nput Error Occurred Workitem appears in user's Inbox Execute Workitem Display IDoc for user processing (IDoc method "InputForeground") Fix error and reprocess IDoc or Flag IDoc for deletion ALE triggers end ev ent i nput Fi ni shed Workitem completed Slide 93 | 6/3/2013 .

EDI.  Transactions For Testing. ALE ?  Components of ALE.  IDOCS . Structure.Introduction. ALE in typical Project Scenario. Slide 94 | 6/3/2013 .  Questions. Monitoring Interface and Processing IDOCS.  ALE Processing. Applications.Topics to cover  What is EDI.

Case 1: Distribution of Material Master Data . Define Logical Systems [ SALE ]. Create RFC Destination [ SM59 ]. 9. Create Partner Profiles [ WE20 ] or Generate them from distribution model [ BD82 ]. 5.Through Standalone program Steps Involved: 1. 7. partner profiles are generated in the receiver too. Ensure that Logical Systems. 4. 10. 6. Create Port [ WE21 ]. Maintain the Distribution Model [ BD64 ]. (Configured when you distribute a distribution model) In the outbound parameters for sender partner profiles add the message type „SYNCH‟ and IDOC type „SYNCHRON‟ along with the material master message type and IDOC types: „MATMAS‟ and „MATMAS03‟ respectively. Assign Client to Logical System [ SALE ]. 2. 3. Execute the process [ BD10 ]. Distribute the Distribution Model [ BD64 ]. Slide 95 | 6/3/2013 . 8.

Send Material transaction BD10 Slide 96 | 6/3/2013 .

Enable Change Pointers for a Message Type [ BD50 ]. 9. 6. 3. Execute the program RBDMIDOC to process the change pointers [ SE38 ]. Slide 97 | 6/3/2013 . 7. Create RFC Destination [ SM59 ]. 5. Changing the field in Master Data [ MM02 ]. 10. Specify the fields for which Change Pointers are to be written [ BD52 ]. 4.Case 2: Distribution of Material Master Data .Through Change Pointers Steps Involved: 1. 8. Define Logical Systems [ SALE ]. Enable Change Pointers globally [ BD61 ]. Create Port [ WE21 ]. 2. Create Partner Profiles [ WE20 ]. Assign Client to Logical System [ SALE ].

Create RFC Destination [ SM59 ]. Ensure that Logical Systems. 6. Maintain the Distribution Model [ BD64 ]. 4. Assign Client to Logical System [ SALE ]. 3. Create Partner Profiles [ WE20 ] or Generate them from distribution model [ BD82 ]. Define Logical Systems [ SALE ]. 7. (Configured when you distribute a distribution model) Slide 98 | 6/3/2013 .Purchase Orders Steps Involved: 1. 5. Distribute the Distribution Model [ BD64 ]. 2.Case 3: Distribution of Transaction Data . 8. Create Port [ WE21 ]. partner profiles are generated in the receiver too.

9. OUTPUT DETERMINATION: a) Maintain condition table for PO: SPRO -> Materials Management -> Purchasing -> Message Determination -> Message Determination -> Condition Table for Messages -> Define condition table for purchase order -> Messages: Display Condition Table: b) Define Access sequence: SPRO -> Materials Management -> Purchasing -> Message Determination -> Message Determination -> Access Sequences -> Define Access sequence for purchase order.Purchase Orders – contd.Distribution of Transaction Data . c) Configuring the output type: SPRO -> Materials Management -> Purchasing -> Message Determination -> Message Determination -> Message Types -> Define message types for purchase order -> Maintain output types: Purchase order Slide 99 | 6/3/2013 .

Purchase Orders – contd. d) Indicate the permitted operations for which the output is activated SPRO -> Materials Management -> Purchasing -> Message Determination -> Message Determination -> Message Types -> Define message types for purchase order -> FineTuned Control: Purchase Order e) link it to an output procedure (message schema): SPRO -> Materials Management -> Purchasing -> Message Determination -> Message Determination -> Message Schemas -> Define message schemas for purchase order -> Maintain output determination procedure: Purchase order f) Create condition records for the tables that are being accessed in certain sequences that we incorporated in the output type. Create the PO [ ME21 ] enter a purchase order document type that was used for creating condition records during the configuration of output determination. Logistics -> Materials Management -> Purchasing -> Master Data -> Messages -> Purchase Order -> Create 10. Slide 100 Process the output [ WE15 ] | 6/3/2013 . 11.Distribution of Transaction Data .

ALE For Transactional data ---.Output Determination NACE Slide 101 | 6/3/2013 .

Output Determination -.Access Sequence Slide 102 | 6/3/2013 .

Output Determination -- Output Types

Slide 103

| 6/3/2013

Output Types -- Details

Slide 104

| 6/3/2013

Output Types -- Partner Functions

Slide 105

| 6/3/2013

Processing Routines Slide 106 | 6/3/2013 .Output Types -.

Procedures Slide 107 | 6/3/2013 .Output Types -.

Procedures Control Slide 108 | 6/3/2013 .Output Types -.

Output Types -.Condition records Slide 109 | 6/3/2013 .

Transaction Code Inbound/Outbound Description WE20 Partner Profile WE21 WE30 WE31 WE40 WE41 WE42 WE44 WE57 WE60 WE61 BD67 WE81 WE82 BD60 SWLD SALE VOE4 BD84 Slide 110 | 6/3/2013 PU12_IDOC_PROCESS Port Definitions Developing IDOC types Development of Segments Display System Process Codes OUT IN Outbound Process Codes Inbound Process Codes Partner Types IN Allocating Function Module to Message Type Documentation For Idoc Types Documentation For Idoc Record Types To creates link between Process Code and Functional Module Creating Message Types Link between Message type. IDOC type & IDOC extension OUT Link between message type and Function Module Area Menu for Workflow IN OUT IN IN Define Settings for the Inbound Function Module Make entries in EDPAR Reprocessing error Inbound Ready For Process Idocs .

Sign up to vote on this title
UsefulNot useful