ALE/IDOCs

[Former Member]

HI,

Can anyone plz let me know all the transaction codes involved in ale-idocs all types, and how to handle errors by looking at the status numbers and which transactions to look for rectifying the errors.

i need them very urgently and if anyone has the HCL FAQs on ALE/IDOCs please post it immediately.

Thanq very much.

[Former Member]

HI,

Can anyone plz let me know all the transaction codes involved in ale-idocs all types, and how to handle errors by looking at the status numbers and which transactions to look for rectifying the errors.

i need them very urgently and if anyone has the HCL FAQs on ALE/IDOCs please post it immediately.

Thanq very much.

[Former Member]

Hi Harun,

1 Can anyone plz let me know all the transaction codes involved in ale-idocs all types.?

and This for Custom Idoc creation means Scratch from basic

Outbound

1.1. create segement WE31 Then,Create IDoc type (WE30)

1.2. Create message type (WE81) Client independent

1.3 Link message to IDoc type (WE82 & BD69) Client independent

1.4 Maintain object type for message type (BD59) Client independent

1.5 Distribute customer model and Manual Configuration (BD64)

1.6. Distribute customer model (BD71)

1.7. Maintain sending system partner profile (WE20)

Inbound

1.8 Debugging inbound FM-WE19

1.9 Link Message Type to Function Module (WE57)

1.10 Recognizing the FM as Inbound FM BD51

1.11. Maintain process codes (WE42)

1.12. Create inbound partner profile(WE20)

2 how to handle errors by looking at the status numbers and which transactions to look for rectifying the errors.

Processing Technical IDoc Errors

Use

During communication between the external system and the Warehouse Management system (WMS), technical problems can occur in the ALE layer. The following errors can occur:

• Syntax error in the IDoc

• Missing partner profile

• The IDoc was not transferred to a synchronous Remote Function Call on transmission

• The IDoc was not transferred to the application on receipt

Error During Outbound IDoc Processing

IDoc status 07: Syntax error in IDoc

On sending and receiving IDocs, the system checks the syntax of the individual IDocs. The IDoc definition defines the syntax of the IDoc. The syntax includes:

• The individual segments of an IDoc type

• The relationship between the individual segments

• How many segments can be sent in one IDoc

Normally, incorrect syntax in IDocs only occurs in testing. IDocs with incorrect syntax cannot be repaired. You correct the IDoc structure in the SAP system and send the IDoc again.

We recommend only switching on the syntax check during testing of IDocs created yourself. You activate the syntax check via the partner profile for one IDoc type and a one particular partner.

IDoc status 29: Missing or incorrect partner profile

To send an IDoc from the SAP system to the external system, you must define outbound parameters for the message type and all relevant partners.

For more information, see Interfaces  External Systems  Configure Warehouse Management  Communication R/3 -> External System  Maintain Partner Profile in the Implementation Guide for Warehouse Management.

If the system cannot find the partner (that is, the connected partner system) for sending the IDocs, proceed as follows:

• Define the missing partner profile.

• Resend all existing IDocs, which the system has not yet been able to send.

For this error, the system triggers a workflow work item for the standard task Output: Error processing with IDoc and sends a message to the inbox of the corresponding user.

You trigger subsequent sending of the IDocs that contained errors from the inbox.

On subsequent transmission, the incorrect IDoc is flagged with status 31 and copied to a new IDoc, which is enhanced with data from the partner profile and transferred to the asynchronous RFC.

Errors in partner profiles normally only occur in the test run.

IDoc status 30: The IDoc is not transferred to the asynchronous RFC

Although the partner profile is defined and the IDoc has been constructed, the IDoc cannot be transferred to the asynchronous RFC. The IDoc is not sent, and there is no official entry in the RFC valuation (/nSM58) for the relevant subsystem.

You trigger transmission of the IDoc using report RSEOUT00. To start the report manually, choose Tools  Business Communication  IDoc Basis  Test  Outbound Processing from IDoc (/nWE14), or schedule a regular job in background processing for this report.

Check the outbound processing mode for the IDoc in the partner profile.

• Outbound processing mode 2: The system sends the IDoc immediately

• Outbound processing mode 4: The system collects IDocs that have been created and sends them in packets of a predefined size.

IDocs are not intended to be sent directly.

Status 30 in the IDoc can normally only occur if outbound mode is set to 4.

Error During Outbound IDoc Processing

IDoc status 60: Syntax error in IDoc

On sending and receiving IDocs, the system checks the syntax of the individual IDocs. The IDoc definition defines the syntax of the IDoc. The syntax includes:

• The individual segments of an IDoc type

• The relationship between the individual segments

• How many segments can be sent in one IDoc

Normally, incorrect syntax in IDocs only occurs in testing. IDocs with incorrect syntax cannot be repaired. You correct the IDoc structure in the SAP system and send the IDoc again.

You activate the syntax check via the partner profile for one IDoc type and one particular partner. We recommend that you activate the syntax check, particularly for any IDocs that you have created yourself.

IDoc status 63: Missing or incorrect partner profile

To receive an IDoc in the SAP system from the external system, you must define the outbound partner profile for the message type and all relevant partners.

For more information, see Interfaces  External Systems  Configure Warehouse Management  Communication Ext. System -> R/3  Maintain Partner Profile in the Implementation Guide for Warehouse Management.

If the system cannot find the partner (that is, the connected partner system) for receiving the IDocs, proceed as follows:

• Define the missing partner profile.

• Trigger receipt of all existing IDocs, which the system has not yet been able to process, again.

For this error, the system triggers a workflow work item for the standard task Input: Error processing with IDoc and sends a message to the inbox of the corresponding user.

From the inbox, you trigger the subsequent transmission of the IDocs which contained errors.

Errors in partner profiles normally only occur in the test run.

IDoc status 64: IDoc is not transferred to the application

Although the partner profile is defined and the IDoc has been received, the IDoc cannot be transferred to the application.

You trigger transmission of the IDoc using report RBDAPP01. To do this, plan a regular job in background processing for this report.

Check the processing mode for the IDoc in the partner profile:

• Processing mode 1: The system transmits the IDoc immediately after receipt in the application.

• Output mode 3: The system collects received IDocs.

IDocs are not intended to be transmitted directly to the application.

Status 64 in the IDoc can normally only occur in conjunction with processing mode 3 and output mode 2.

Rgds

Sree m

Edited by: Sree M on Mar 26, 2008 11:05 PM

[Former Member]

hi,

Transaction codes of EDI/IDOC.

=>sale - ALE Customizing

=>bale - Distribution Administration (ALE)

=>wedi - IDOC Type and EDI Basis

=>shdb - BDC (Transaction Recorder)

=>lsmw - LSMW

=>bapi - BAPI

=>spau - Display Modified DE Objects

=>spdd - Display Modified DDIC Objects

=>sara - central idoc archiving

=>stms - Transport Management System

=>wedi - IDOC Type and EDI Basis (IDOC Configuration)

=>bd21 - Analyze change pointers - create IDOC from change pointer

=>bd10 - Send Material Master

=>bd12 - Send Customer Master

=>bd14 - Send Vendor Master

=>bd50 - Activate Change Pointer for Message Type

=>bd55 - Conversion rule user exit (Link conversion rule user exit to the different system \ partner combinations)

=>bd54 - Maintain Logical Systems

=>bd71 - Distribute Customer Model

=>bd87 - Process Inbound IDOCs

=>bd88 - Process Outbound IDOCs

=>bdm2 - Cross-system IDOC Reporting

=>bdm7 - ALE Audit - statistical analyses

=>bdm8 - ALE Audit - sending confirmations

=>bd61 - Activate Change Pointer generally

=>bmv0 - Direct Input Data Transfer Administration

=>rz04 - Operation Mode

=>rz12 - RFC Server Group Maintenance

=>sar3 - Archiving object customizing

=>s001 - SAPoffice Inbox

=>s010 - Standards Texts (SAP Script)

=>se01 - Transport Organizer (Extended View - Performing and managing the transport of development object across different systems)

=>se09 - Transport (Workbench) Organizer (Controlling and keeping track of Development work and Development Objects)

=>se78 - Administration of Form Graphics (Import Graphics into SAP System)

=>se84 - ABAP Repository Information (search for SAP objects)

=>su01 - User Maintenance (Security)

=>su02 - Maintain Authorization Profiles

=>su03 - Maintain Authorizations

=>sm36 - Background Job Scheduling

=>sm37 - Background Job Monitoring (display batch jobs)

=>sm31 - Table Maintenance

=>sm30 - Calling View Maintenance

=>sm35 - Batch Input Monitoring (Error Logs)

=>sm50 - Process Overview

=>sm58 - Transactional RFC Monitoring

=>sm59 - Maintain RFC Destinations (Define RFC Configuration)

=>snro - Number Range Objects (for IDOCs)

=>we02 - Display IDOC

=>we05 - IDOC lists

=>we07 - IDOC statistics

=>we12 - Inbound processing of outbound file - convert outbound to inbound file

=>we14 - Process (dispatch) IDOCs through Port - RSEOUT00

=>we15 - Outbound IDOC from NAST - message control

=>we16 - Inbound File

=>we18 - Generate status file

=>we19 - Test tool

=>we20 - Add new Message Type to Partner Profile

=>we21 - Maintain Port Definition

=>we30 - IDOC Type development

=>we31 - IDOC Segment development

=>we41 - Process Code Outbound

=>we42 - Process Code Inbound

=>we46 - IDoc Administration

=>we47 - Status Code Maintenance

=>we57 - Assign function module to logical message and IDoc type

=>we63 - IDOC Type for Parser Output

=>we82 - Assign IDOC to Message Type

=>we60 - IDOC Documentation - IDOC Types

=>we61 - IDOC Documentation - IDOC Record Types

=>we81 - Create new IDOC Message Types

=>we82 - Assign IDOC to Message Type

=>pa20 - Display HR Master Data

=>pa30 - Maintain HR Master Data

=>bd59 - Create and assign Filter Object Type for Message Type

=>bd64 - Maintenance of ALE or any other Distribution Model

For FAQ's follow this link.

http://abapprogramming.blogspot.com/2007/03/abap-cross-applications-ale.html

Hope this helps, Do reward.