Embed Size (px)
Transcript of Idoc Overview
Idoc overview- WE02
IDoc correction BD87\WE02
Configuration for partner profile WE20 Outbound ASN ( advanced shipment notification) Message type DESADV POA ( PO Acknowledgment) Message type ORDRSP INV ( Invoice) Message type INVOIC Inbound PO Message type ORDRS
Enter Partner roleMessage typeProcess code F4 or WE64 for possible process code list Save
VOE2Update EDSDC table
VOE4Update EDPAR table
EDSDC and EDPAR are used for inbound sales processing only.EDSDC, however, you are simply automatically allocating a sales area (sales org, distr. chan., division) to an incoming sales order from a customer.EDPAR (the transaction used is VOE4) is map the customers external partner numbers (their plants/ship to addresses) to your own internal customer numbers in KNA1.Outbound
Receiver PortPack sizeOutput Mode IDOC Type Basic Extension
Message Control F4 for options Message Type Same as Printed Options Process Code F4 or WE64 for options Double click to see function module Do required configuration in NACE SAVE.
VOE4Update EDPAR table
Create PortsGo to transaction WE21 for creating ports. WE21 -> Transactional IR -> Create
Creating IDOC Segments: 1. Go to transaction WE31 -> Give your segment name -> Press Create.2. Type your field name and data element and press save then segment definition will be created automatically.Create Basic IDoc type Transaction WE30Go to Transaction WE301. For new IDOC type select the radio button Basic type and press Create button.2. Then select the IDOC option to create and press Enter. Give segment name, minimum and maximum number for and save it. Check if this is mandatory segment.3. If you want Header and Item create the segment tree according to that, you can view as follows then press Save.4. Then go back and set release the IDOC type for using it further. Idoc type will be created successfully once we release that status. We have to release the segments (in WE31) and IDOC type as well.Create Message TypeGo to transaction WE81 for new message type. Go to change mode and click New Entries for creating our own message type.Associate Message Type with Basic Idoc TypeGo to transaction WE82 for associating the message type with basic IDOC type.Associate Message Type with Basic Idoc TypeGo to transaction WE82 for associating the message type with basic IDOC type.Create Logical SystemGo 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 SystemElse go to transaction SALE then go to Basic settings-> logical system then Define logical system. We can create the same.
Create Logical Connection1. Go to transaction SM59 for creating Logical Destination. a. SM59 -> logical connections -> Create b. Then Click Connection test icon after marking the current user checkbox in logon and security tab. c. Then Destination client will automatically open Create Ports Go to transaction WE21 for creating ports. WE21 -> Transactional IR -> Create Steps to be done in Source client1. Go to transaction SE11 -> create a table with entries.2. Go to transaction WE31 -> create segments as shown before. Here you have to mention all the fields mentioned in the database table.3. Go to transaction WE30 -> create basic IDOC type and release the segments and basic type.4. Go to transaction WE81 -> create message type.5. Go to transaction WE82 -> assign message type to basic Idoc type.6. Go to transaction BD64 -> Click on Display/change button7. Click on Edit menu -> model view -> create8. Specify description and technical name and press continue.9. Select your model view -> click edit -> Add message type10. In dialog box specify sender, receiver, and message type and continue.11. Click on environment menu -> generate partner profile12. It will show the following screen. Select your model view and click on execute.13. It will show the partner profile log in next screen.14. Click on back button 2 times it will take to distribution model screen.15. Click on Edit -> Model view -> Distribute16. In displayed dialog box select the partner system and continue.17. Then it will show the log of model view distribution.18. To check partner profile go to transaction WE20.19. Then write the report program in SE38 to create IDOC control records and transfer it to destination partner system.20. Go to Transaction WE02 to check the generated IDOC control records. Steps to be done in Destination client1. Go to transaction SE37 to create the function module for updating the table from IDOC segments.2. Specify import, export and table parameters.3. Go to transaction WE57 for assigning the FM to logical system. Click on Display/ change button.4. Specify FM name, function type, basic type(IDOC ), message type and direction then save it.5. Go to transaction BD51 to define input method for inbound function module and click on Displaychange button6. Specify your function module and input type by clicking the new entries.7. Go to transaction WE42 and create process code.8. Go to transaction BD64 and generate the partner profile again.9. Got o transaction SE 38 and execute the transaction in source system (client100).10. Check in destination system (client 800). Go to Transaction WE02 and check your table in SE11. (You can get the transferred entries in that table).
The Outbound status as follows:00Not used, only R/201IDoc generated02Error passing data to port03Data passed to port OK04Error within control information of EDI subsystem05Error during translation06Translation OK07Error during syntax check08Syntax check OK09Error during interchange handling10Interchange handling OK11Error during dispatch12Dispatch OK13Retransmission OK14Interchange Acknowledgement positive15Interchange Acknowledgement negative16Functional Acknowledgement positive17Functional Acknowledgement negative18Triggering EDI subsystem OK19Data transfer for test OK20Error triggering EDI subsystem21Error passing data for test22Dispatch OK, acknowledgement still due23Error during retransmission24Control information of EDI subsystem OK25Processing despite syntax error (outbound)26Error during syntax check of IDoc (outbound)27Error in dispatch level (ALE service)28Not used29Error in ALE service30IDoc ready for dispatch (ALE service)31Error - no further processing32IDoc was edited33Original of an IDoc which was edited34Error in control record of IDoc35IDoc reloaded from archive36Electronic signature not performed (timeout)37IDoc added incorrectly38IDoc archived39IDoc is in the target system (ALE service)40Application document not created in target system41Application document created in target system42IDoc was created by test transactionInbound status of an Idoc50IDoc added51Application document not posted52Application document not fully posted53Application document posted54Error during formal application check55Formal application check OK56IDoc with errors added57Test IDoc: Error during application check58IDoc copy from R/2 connection59Not used60Error during syntax check of IDoc (inbound)61Processing despite syntax error (inbound)62IDoc passed to application63Error passing IDoc to application64IDoc ready to be transferred to application65Error in ALE service66IDoc is waiting for predecessor IDoc (serialization)67Not used68Error - no further processing69IDoc was edited70Original of an IDoc which was edited71IDoc reloaded from archive72Not used, only R/273IDoc archived74IDoc was created by test transaction75IDoc is in inbound queue