Sap abap ale idoc


Published on

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • For converting the text IDs: Purchasing and Sales use different text IDs. If order texts are to be copied to the sales orders, a conversion must take place. This can be performed using the ALE conversion. For the purchase order (ORDERS) and the purchase order change (ORDCHG), conversions must take place at header and item level. These conversions can be carried out by generating a conversion rule for the document header (segment E1EDKT1) and the item (segment E1EDPT1). When defining this rule, use TDID for the recipient field. The assignment rule is GROUP, the sender field is TDID. A comparison of IDs for the purchase order and sales order is provided in the documentation on the ‘Stock Transfer Between Distributed Systems’ Scenario in the IMG. EDI settings: 1. EDI settings for incoming sales orders -Configuration of EDI partners (table EDPAR). Derivation of internal partner numbers from the combination sold-to party - partner role - external partner number -Maintenance of possible partner roles -Derivation of the sales area (table EDSDC) from the combination customer - vendor. If the sales area is specified in the IDoc, the table is not required. 2. Message handling for incoming orders Messages that are output for an inbound IDoc (if the IDoc contains conditions or payment conditions, for example) can be defined as information, warnings, or document blocks. 3. Conversion from SAP item category to IDoc item category An item category can be provided in the IDoc. This is converted to an SAP item category via the EDPST table. (If no item category is specified, the SD item category is determined in the standard manner).
  • The distribution of systems makes it necessary to be able to identify every system individually within a network. The "logical system" is used to do this. ALE Configuration Phase 4-2 A logical system is an application system within which the applications are co-ordinated to work in one database. In the SAP sense of the word, a logical system corresponds to a client. A logical system needs to be set up for each client that the system, on which you are working, needs to communicate to via ALE. In the following steps, you must define every client as a logical system by first of all defining logical systems and then assigning the clients in question to the corresponding logical systems. Note: Assignments must be unique (that is, a client may only be assigned to one logical system. Several clients must never be assigned to the same logical system. The same applies to pre-production systems and production systems: the pre-productive system must be assigned to a different logical system than the productive system.
  • Maintain logical systems (Client independent) 1. In the IMG, choose Cross-Application Components -> Distribution (ALE) -> Basic Configuration -> Set up logical system -> Maintain logical systems 2. To create a logical system, choose Edit -> New Entries . 3. Enter a name for the logical system according to the ALE Naming Standards document 4. Enter a clear description for the logical system. If you want to change this short text for a logical system, please proceed as follows: a) Select the appropriate line. b) Choose Edit -> Change field entries. 5. Enter the new short text. 6. Choose Replace. 7. Save your entries. 8. Repeat steps 2-4 for the different clients.
  • Allocate logical systems to the client This step only needs to be performed for the clients that reside on the box where you have just created the logical systems. For those logical systems that refer to clients that exist on other systems, the logical system will be linked to the client on its respective system. E.g., ALExxxCyyy will be linked to client yyy on system xxx. 1. In the IMG, choose Cross-Application Components -> Distribution (ALE) -> Basic Configuration -> Set up logical system -> Allocate logical system to the client 2. Select the relevant client. 3. Choose: Goto -> Detail . You branch into the detail screen. 4. In the field Logical system, specify the name of the logical system to which you want to assign the selected client, as per the naming conventions. 5. Save your entries.
  • This must be set up for all the logical destinations manually. RFC destinations are client independent. The Remote Function Call is controlled via the parameters of the RFC destination. The RFC destinations must be maintained in order to create an RFC port. The name of the RFC destination should correspond to the name of the logical system in question. EG. ALExxxCyyy Procedure 1. Execute SM59 2. Click on R/3 links and choose Edit -> Create; 3. The RFC destination name must be the same as the logical system name in order for the port to be automatically generated. 4. The type of RFC destination is 3. 5. Enter the required parameters dependent on the type. • For an R/3 link, that is, for example, the name of the RFC destination, the name of the partner machine, logon parameter ALE-BATCH with password init. 6. Select the Destination -> TRFC options function from the menu. 7. Enter the value 'X' into the 'Suppress backgr. job in case of comms. error' field. 8. Save and exit. Notes on the transport The maintenance of the RFC destination is not a part of the automatic transport and correction system. Therefore the setting has to be made manually on all systems.
  • Sap abap ale idoc

    1. 1. <ul><ul><li>Overview of ALE-IDOCs </li></ul></ul>Last modified by: Bunty Jain – SAP ABAP, Delhi, India, IT SAP Training [email_address]
    2. 2. Application Linking And Enabling Last modified by: Bunty Jain – SAP ABAP, Delhi, India, IT SAP Training [email_address]
    3. 3. Distributed Process An introduction Last modified by: Bunty Jain – SAP ABAP, Delhi, India, IT SAP Training [email_address]
    4. 4. When a part of a business process is conducted in one system and another part of the same business process in another system, such procedure is termed as a distributed process. Distributed Process. Last modified by: Bunty Jain – SAP ABAP, Delhi, India, IT SAP Training [email_address]
    5. 5. Why a distributed process ?
    6. 6. Reasons for Distributed Process <ul><li>Geographical Location </li></ul><ul><li>Consolidation </li></ul><ul><li>System Capacity </li></ul><ul><li>Critical Applications </li></ul><ul><li>No coding required (Only configuration) </li></ul><ul><li>Separate upgrade of Modules </li></ul><ul><li>Data Security </li></ul>
    7. 7. What SAP wanted for its distribution solutions.
    8. 8. What SAP wanted for its distribution solutions. <ul><li>A system that understands the syntax and semantics of data. </li></ul><ul><li>To base distribution of data on business rules and not on data replication techniques. </li></ul><ul><li>Distributed systems should maintain their autonomy while being integrated as one logical system. </li></ul><ul><li>Distributed systems should handle different data models. </li></ul><ul><li>Sending and receiving systems should handle their own problems and not tie up with each other. </li></ul><ul><li>Distribution process should continue inspite of network failures. </li></ul>
    9. 9. SAP’s solution for its distribution requirements : Application Linking & Enabling.
    10. 10. Application Linking & Enabling. SAP introduced ALE to to support a distributed yet integrated environment. ALE allows for efficient and reliable communication between distributed processes across physically separate systems. ALE is based on application to application integration using message control architecture.
    11. 11. Application Linking & Enabling. ALE is not based on any data replication technique. ALE architecture is independent of participating systems. This allows SAP to allow SAP to Non-SAP communication also. This allows third party applications to integrate with SAP using ALE at data distribution level. IDOCs constitute a major component of ALE. Release upgrades are supported by ALE. Features
    12. 12. Provisions of the standard system for ALE Pre-configured Master Data Scenarios Several master data objects in SAP have been enabled for ALE. Master data is the critical information that needs to be shared between several applications in a company. ALE is used to transfer both master & transactional data
    13. 13. ALE Technology and Components
    14. 14. IDOC <ul><li>The term IDOC stands for Intermediate document. It is simply a data container used to exchange information between any two process. That can understand the syntax and semantics of the data. </li></ul><ul><li>IDOC’s are made using the segments </li></ul><ul><li>IDOC’s are stored in the data base </li></ul><ul><li>Every IDOC has unique number </li></ul><ul><li>An IDOC is attached to a message type and identified by its message type </li></ul><ul><li>IDOC consists of three types of records </li></ul><ul><ul><ul><ul><li>One control record </li></ul></ul></ul></ul><ul><ul><ul><ul><li>One or many data records </li></ul></ul></ul></ul><ul><ul><ul><ul><li>One or many status records. </li></ul></ul></ul></ul>
    15. 15. <ul><li>Control Record : </li></ul><ul><li>A control record contains all of the control information about an IDOC, </li></ul><ul><ul><ul><ul><li>Sender and receiver information </li></ul></ul></ul></ul><ul><ul><ul><ul><li>port </li></ul></ul></ul></ul><ul><ul><ul><ul><li>partner type </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Message type it represents </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Its direction </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Idoc Type </li></ul></ul></ul></ul><ul><li>Data Record </li></ul><ul><li>In an IDOC the data record contains the application data. </li></ul><ul><li>Status Record </li></ul><ul><li>Status records are attached to an IDOC throughout the process as the IDOC achieves different milestones or encounter an error. At every milestone a status code, date and time are assigned. </li></ul><ul><li>The system defines numerous status code, </li></ul><ul><ul><ul><ul><li>0 – 49 are reserved for outbound process </li></ul></ul></ul></ul><ul><ul><ul><ul><li>50 and above are reserved for inbound process </li></ul></ul></ul></ul>
    16. 16. ALE Customizing <ul><li>distribution model: </li></ul><ul><ul><li>Standard Message types: IDoc types (depends on scenario): </li></ul></ul><ul><ul><li>MATMAS (for material) MATMAS05 </li></ul></ul><ul><li>CREMAS (for vendor) CREMAS05 </li></ul><ul><li>DEBMAS (for customer) DEBMAS06 </li></ul><ul><li>ORDERS - Purchase order ORDERS05 </li></ul><ul><li>ORDRSP - Order confirmation ORDRSP05 </li></ul><ul><li>Complete documentation on IDOC is obtained by using transaction WE60. </li></ul>
    17. 17. Idoc type is subdivided into so many segments. Each segment will have one or more fields. Group functionally related fields into segments. Then use segments to create the IDOC. Structure description MATMAS05 Material master E1MARAM General data E1MAKTM Short text E1MARMM Unit of measure E1MARCM Plant data Field list E1MARAM _ MATNR Material no. _ MTART Material type _ MBRSH Industry sector _ MATKL Material group _ WRKST Basic material ...
    18. 18. IDOC Structure as seen in transaction WE02
    19. 19. Control Record
    20. 20. Steps in ALE <ul><li>The basic settings for the IDOC interface must be maintained once on each system involved in distributed process </li></ul><ul><li>Basic settings for IDOCs </li></ul><ul><ul><ul><ul><li>Maintaining logical system (BD54) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Assigning logical system to the client (SCC4) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Setting up an RFC destination (SM59) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>The port definition (WE21) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Maintain the distribution model (BD64) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Create a partner profile (WE20) </li></ul></ul></ul></ul>
    21. 21. Configuring the ALE Infrastructure <ul><li>1. Maintaining logical system – Transaction ‘SALE’ </li></ul>
    22. 22. Configuring the ALE Infrastructure <ul><li>1. Maintaining logical system </li></ul>
    23. 23. Configuring the ALE Infrastructure <ul><li>2. Allocating logical system to the client – Transaction ‘SALE’ </li></ul>
    24. 24. Configuring the ALE Infrastructure <ul><li>2. Allocating logical system to the client – Transaction ‘SALE </li></ul>
    25. 25. Configuring the ALE Infrastructure <ul><li>3. Setting up an RFC destination – Transaction ‘SM59’ </li></ul>Transaction SM51 to Identify the Target Host of remote system
    26. 26. Configuring the ALE Infrastructure <ul><li>4. The Port definition – Transaction ‘WE21’ </li></ul>
    27. 27. Configuring the ALE Infrastructure <ul><li>5. Maintaining the distribution model – Transaction ‘BD64’ </li></ul>
    28. 28. Configuring the ALE Infrastructure <ul><li>6. Create the partner profile – Transaction ‘WE20’ </li></ul>
    29. 29. Configuring the ALE Infrastructure <ul><li>Partner profile : outbound parameters </li></ul>
    30. 30. Configuring the ALE Infrastructure <ul><li>Partner profile : Inbound parameters </li></ul>
    31. 31. <ul><li>We can also create Custom Idoc. </li></ul><ul><li>Important Tcodes </li></ul><ul><li>Configuring the outbound process </li></ul><ul><li>Create the segments – Transaction (WE31) </li></ul><ul><li>Create the basic IDOC type Transaction (WE30) </li></ul><ul><li>Create the new message type (WE81) </li></ul><ul><li>Link the IDOC type to the message type (WE82) </li></ul><ul><li>Add the message to the ALE distribution model (BD64) </li></ul><ul><li>Create the partner profile (WE20) </li></ul><ul><li>Configuring the inbound process </li></ul><ul><li>Create the new message type (WE81) </li></ul><ul><li>Link the IDOC type to the message type (WE82) </li></ul><ul><li>Allocate the function module to the logical message (WE57) </li></ul><ul><li>Define the attributes for the inbound function module (BD51) </li></ul><ul><li>Create new process code (WE42) </li></ul><ul><li>Assign the process code to the function module (WE42) </li></ul><ul><li>Create the partner profile (WE20) </li></ul>Last modified by: Bunty Jain – SAP ABAP, Delhi, India, IT SAP Training [email_address]
    32. 32. <ul><li>Thank You </li></ul>Last modified by: Bunty Jain – SAP ABAP, Delhi, India, IT SAP Training [email_address]