You are on page 1of 3

IDOC Status Description Status Description 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 50 51 52 53 54 55 56 57 58 Not used, only R/2 IDoc generated Error passing data to port

Data passed to port OK Error within control information of EDI subsystem Error during translation Translation OK Error during syntax check Syntax check OK Error during interchange handling Interchange handling OK Error during dispatch Dispatch OK Retransmission OK Interchange Acknowledgement positive Interchange Acknowledgement negative Functional Acknowledgement positive Functional Acknowledgement negative Triggering EDI subsystem OK Data transfer for test OK Error triggering EDI subsystem Error passing data for test Dispatch OK, acknowledgement still due Error during retransmission Control information of EDI subsystem OK Processing despite syntax error (outbound) Error during syntax check of IDoc (outbound) Error in dispatch level (ALE service) Not used Error in ALE service IDoc ready for dispatch (ALE service) Error - no further processing IDoc was edited Original of an IDoc which was edited Error in control record of IDoc IDoc reloaded from archive Electronic signature not performed (timeout) IDoc added incorrectly IDoc archived IDoc is in the target system (ALE service) Application document not created in target system Application document created in target system IDoc was created by test transaction IDoc added Application document not posted Application document not fully posted Application document posted Error during formal application check Formal application check OK IDoc with errors added Test IDoc: Error during application check IDoc copy from R/2 connection

59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74

Not used Error during syntax check of IDoc (inbound) Processing despite syntax error (inbound) IDoc passed to application Error passing IDoc to application IDoc ready to be transferred to application Error in ALE service IDoc is waiting for predecessor IDoc (serialization) Not used Error - no further processing IDoc was edited Original of an IDoc which was edited IDoc reloaded from archive Not used, only R/2 IDoc archived IDoc was created by test transaction

SALE Area Menu for ALE configurations.It includes transactions for Logical System definition and linking it to a client, Transactions for RFC Destination and Port Definition Etc. SM59 RFC Destination Here we specify the login settings for the destination including the I.P address or Application Server name and the User name and password.The information entered here is used to run Remote Function Calls(RFC ) on the destination server .We can create number of types of RFC Destinations but 3 types are important . R/3 (R/3 to R/3), LS(logical system) and TCP/IP. The name of the RFC destination should be same as that of Logical System as it helps in creation of automatic partner profiles. WE21 Port Definition. There are 6 types of ports but only 2 types File and Transactional RFC types of ports are important. We have to specify the RFC Destination before a port can be created. WE57 This is used to assign the Inbound function module to the Message Type and to the IDOC Type. WE42 This is used to define the process Code for Inbound Processing. BD95 Define Filter object type .We can specify the field and the table it belongs to as a filter object . BD59 Assignment of Filter object type to the Message Type .Here we create the link between Filter object and the segment and the message type and the segment Field. BD50 Set message Type to reducible. BD65 Define Mandatory Fields. BD64 Distribution Model . Also known as Customer Distribution Model Used to define all the messages that will be exchanged between remote systems and the name of thes logical systems. Any filters can also be specified. The model once created has to be distributed on every system which will be communicating ,It can be maintained on only One system. BD21 Creating IDOcs from change pointers.

This can be used to create IDOCs from change pointers for a particular message LIKE MATMAS. BD22 This can be used to delete change pointers. BD87 Status Monitor. Idocs can be selected base on number of criteria and there processing status can be seen in detail. BD10 Material Master Data Distribution . Based on Message MATMAS. BD12 Customer Master Data Distribution . Based on Message CREMAS. BD14 Vendor Master Data Distribution Based on Message DEBMAS . BDFG Generate ALE Interface for BAPI. Here we specify the Business Object and the BAPI Function module for which the interface has to be created. WE31 Segment Editor. This is used to create segments. We create the segment type and segment definition is automatically created by editor e.g. Z1DUMMY is segment type and Z2DUMMY is the segment definition .We specify the fields and the data elements these cp\orresponds to create segments. WE30 IDOC Editor It is used to create a new IDOC Type or IDOC Extension .We specify the segments that will be addd to the IDOC type. WE02/05 IDOC List. Various selct options and parameters are provided to select IDOCs depending on the date, direction , mesage type etc. WE20 Partner Profile Here we create partner profile for each and every partner from / to which the messages will be exchanged.There are 6 types of PF generally only profiles of type LS(Logical System) ,KU(Customer) ,LI(Vendor) is used. We specify the partner number and partner type and the agent and the agent type responsible for handling of errors . For every message send to the partner we have a outbound record and for evry message coming from the partner we have the inbound record . We specify the message in the otbound/inbound records ,double clicking will take us to the detailed screen where the IDOC Type ,Port and whether the IDCO will be immediatelt processed or collected are mentioned.

You might also like