Check these reports: RBDAGAIN - Process Outbound IDocs with Errors Again Description: This report reprocesses outbound

IDocs which contain errors. IDocs containing errors have one of the following statuses: 02: Error transmitting data to port 04: Error in EDI subsystem control information 05: Error in conversion 25: Continue processing despite syntax error (outbound) 29: Error in ALE service RBDAGAIE - Reprocessing of Edited IDocs Description: This report reprocesses an edited IDoc in inbound or outbound processing. The edited IDoc has one of the following statuses: 32: IDoc edited (outbound) 69: IDoc edited (inbound) RBDAGAI2 - Re-processing of IDocs after ALE Input Error Description: You use this report to reprocess inbound IDocs containing errors. IDocs containing errors have one of the following statuses: 56: IDoc containing errors added 61: Continue processing despite syntax error (inbox) 63: Error passing IDoc to the application 65: Error in ALE service ---For Inbound

1) Goto WE19, select your IDOC and execute. The details will be shown of IDOC. Change the data in the segment as per your requirement. 2) Click on standard inbound process. If you want to execute the process in foreground, click on standard inbound function module. Select related function module and execute the process in foreground/background. For outbound 1) Follow same step 1. 2) Click on standard outbound processing ----To reprocess Idocs in outbound or inbound you can create back ground jobs using the following programs. For Outbound: For 02 status IDocs follow the below procedure: 1. Open SE38. 2. Give program RBDAGAIN. 3. Give you Idocs and save as variant.(Give any name) 4. Now, go to SM36,and specify a job name(Any name). 5. Now click on STEP give your Variant name in the respective field and you program name as RBDAGAIN. 6. Save and come back. 7. Now click on "START CONDITION".Here you give schedule the job either "Immediately" or "Periodically". 8. To do an immediate job select Immediate and save.Else go for perodic as you need. 9. Now save the screen on SM36. 10. To release the job click "Job selection" -- > select sceduled --> execute.

This would push your Idoc from *02*(Error passing data to port) to 30(Idoc ready to dispatch) status. Now to send the Idoc from 30 to *03*(Data passed to port OK) use the "RSEOUT00" program and run another job as stated above. This would send the Idocs to 03. Similarly at Inbound side: To reprocess an Idoc in 51 status: Use program "RBDMANI2" and run a job.It will push Idocs from 51 to 53 status. For 64 status use "RBDAPP01" program. You can do it in transaction code BD87 -------Receiving System (Inbound ALE) Tcode SALE3 for a) Define Logical System b) Assign Client to Logical System Tcode SM59 -- RFC Destination Tcode BD64 -- Check for Model view whether it has distributed or not Tcode BD82 -- Generate partner Profiles & Create Ports Tcode BD11 -- Getting Material Data Tcode WE05 -- Idoc List for inbound status codes Message Type MATMAS Tcode BD10 - Send Material Data Tcode WE05 - Idoc List for watching any Errors

Inbound Status Codes 50 Error --> It will go for ALE Service Layer 56 Error --> Idoc with Errors added 51 Error --> Application Document not posted 65 Error --> Error in ALE Service Layer For 51 or 56 Errors do the following steps Goto WE19 --> give the IDOC Number and Execute--> Press on Inbound function Module for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error

Important Idoc Transaction Codes

SALE - IMG ALE Configuration root WE20 - Manually maintain partner profiles BD64 - Maintain customer distribution model BD71 - Distribute customer distribution model SM59 - Create RFC Destinations BDM5 - Consistency check (Transaction scenarios) BD82 - Generate Partner Profiles BD61 - Activate Change Pointers - Globally BD50 - Activate Change Pointer for Msg Type BD52 - Activate change pointer per change.doc object BD59 - Allocation object type -> IDOC type BD56 - Maintain IDOC Segment Filters BD53 - Reduction of Message Types BD21 - Select Change Pointer BD87 - Status Monitor for ALE Messages BDM5 - Consistency check (Transaction scenarios) BD62 - Define rules BD79 - Maintain rules BD55 - Defining settings for IDoc conversion WEDI - ALE IDoc Administration WE21 - Ports in Idoc processing

WE60 - IDoc documentation SARA - IDoc archiving (Object type IDOC) WE47 - IDoc status maintenance WE07 - IDoc statistics BALE - ALE Distribution Administration WE05 - IDoc overview BD87 - Inbound IDoc reprocessing BD88 - Outbound IDoc reprocessing BDM2 - IDoc Trace BDM7 - IDoc Audit Analysis BD21 - Create IDocs from change pointers SM58 - Schedule RFC Failures Basic config for Distributed data: BD64: Maintain a Distributed Model BD82: Generate Partner Profile BD64: Distribute the distribution Model Programs: RBDMIDOC Creating IDoc Type from Change Pointers RSEOUT00 Process all selected IDocs (EDI) RBDAPP01 - Inbound Processing of IDocs Ready for Transfer RSARFCEX - Execute Calls Not Yet Executed RBDMOIND - Status Conversion with Successful tRFC Execution RBDMANIN - Start error handling for non-posted IDocs RBDSTATE - Send Audit Confirmations For testing you can use WE19

How to Reprocess the IDOC in Both Inbound & Outbound

RBDAGAIN - Process Outbound IDocs with Errors Again Description: This report reprocesses outbound IDocs which contain errors. IDocs containing errors have one of the following statuses: 02: Error transmitting data to port 04: Error in EDI subsystem control information 05: Error in conversion 25: Continue processing despite syntax error (outbound)

29: Error in ALE service RBDAGAIE - Reprocessing of Edited IDocs Description: This report reprocesses an edited IDoc in inbound or outbound processing. The edited IDoc has one of the following statuses: 32: IDoc edited (outbound) 69: IDoc edited (inbound) RBDAGAI2 - Re-processing of IDocs after ALE Input Error Description: You use this report to reprocess inbound IDocs containing errors. IDocs containing errors have one of the following statuses: 56: IDoc containing errors added 61: Continue processing despite syntax error (inbox) 63: Error passing IDoc to the application 65: Error in ALE service ---For Inbound 1) Goto WE19, select your IDOC and execute. The details will be shown of IDOC. Change the data in the segment as per your requirement. 2) Click on standard inbound process. If you want to execute the process in foreground, click on standard inbound function module. Select related function module and execute the process in foreground/background. For outbound 1) Follow same step 1. 2) Click on standard outbound processing ----To reprocess Idocs in outbound or inbound you can create back ground jobs using the following programs.

For Outbound: For 02 status IDocs follow the below procedure: 1. Open SE38. 2. Give program RBDAGAIN. 3. Give you Idocs and save as variant.(Give any name) 4. Now, go to SM36,and specify a job name(Any name). 5. Now click on STEP give your Variant name in the respective field and you program name as RBDAGAIN. 6. Save and come back. 7. Now click on "START CONDITION".Here you give schedule the job either "Immediately" or "Periodically". 8. To do an immediate job select Immediate and save.Else go for perodic as you need. 9. Now save the screen on SM36. 10. To release the job click "Job selection" -- > select sceduled --> execute. This would push your Idoc from *02*(Error passing data to port) to 30(Idoc ready to dispatch) status. Now to send the Idoc from 30 to *03*(Data passed to port OK) use the "RSEOUT00" program and run another job as stated above. This would send the Idocs to 03. Similarly at Inbound side: To reprocess an Idoc in 51 status: Use program "RBDMANI2" and run a job.It will push Idocs from 51 to 53 status. For 64 status use "RBDAPP01" program. You can do it in transaction code BD87 --------

Receiving System (Inbound ALE) Tcode SALE3 for a) Define Logical System b) Assign Client to Logical System Tcode SM59 -- RFC Destination Tcode BD64 -- Check for Model view whether it has distributed or not Tcode BD82 -- Generate partner Profiles & Create Ports Tcode BD11 -- Getting Material Data Tcode WE05 -- Idoc List for inbound status codes Message Type MATMAS Tcode BD10 - Send Material Data Tcode WE05 - Idoc List for watching any Errors Inbound Status Codes 50 Error --> It will go for ALE Service Layer 56 Error --> Idoc with Errors added 51 Error --> Application Document not posted 65 Error --> Error in ALE Service Layer For 51 or 56 Errors do the following steps Goto WE19 --> give the IDOC Number and Execute--> Press on Inbound function Module for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error

BD50 (Activate change pointer for message type) BD61 (Activate change pointers generally)

Creating IDOC with change pointers. TCODE: BD21 Purpose: Create IDOC type from change pointers Program: RBDMIDOC TCODE: BD22 Purpose: Delete Change Pointers Program: RBDCPCLR

BAPIs
Definition
A Business Application Programming Interface (BAPI) is a precisely defined interface providing access to processes and data in business application systems such as R/3.

BAPIs of SAP Business Object Types

BAPIs are defined as API methods of SAP business object types. These business object types and their BAPIs are described and stored in the Business Object Repository (BOR). A BAPI is implemented as a function module, that is stored and described in the Function Builder.

Archiving IDocs
This document details about the step-by-step process in archiving the IDocs. Archiving is the process of offloading Out-of-date data onto a file at the operating system. The following are the two important reasons for archiving: Improving the performance Saving the disk space on the SAP Server

Archiving of IDocs: There are two methods of archiving IDocs: Using the transaction SARA Using the standard programs like RSEXARCA (for archiving), RSEXARCR (for reading) and RSEXARCL (reloading of data into the system)

There are two ways to archive an idoc 1. 2. Through standard report programs or Through the central archiving transaction SARA.

Through standard report programs: The following are the programs used for archiving IDocs RSEXARCA program for archiving. RSEXARCD program for deleting archived IDocs from the database. RSEXARCR program to read the IDocs from archive file. RSEXARCL Program to Retrieve IDocs from the archive into the database.

Idoc reduction can be done in BD53 transaction. here you can filter the fields which you dont want to send. Segment filetering can be done in BD56 here you can filter the whole segment by specifying the sender and reciver.

Data level filtering BD64

communication IDoc is missing when ... - Distribution Modell is missing - Filter in Distribution Model is existing an no IDoc is generated (Filter at KNA1M segment only)