Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Creating an IDOC type

Former Member
0 Likes
506

Hi All,

I am trying to create an IDOC type, using an existing one that is already released as the predecessor.

But apparently this cannot be done in the IDOC editor (TA WE30).

Does any one know how this can be done?

Also, what is the advantage of creating a successor over the other options?

Thanks,

-Elham

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
423

HI Elham,

Extending an IDoc Type

Purpose

In the case of a customer extension, you add additional segments to an IDoc type supplied by SAP (basic type), so that you can transfer more (or simply other) business information. This extension is upward compatible, that is, it will be supported by future releases.

Prerequisites

This checklist requires that the basic type to be extended is already included in the processing: This means, in particular, that the processing (inbound and outbound) is defined using process codes in the partner profiles and that the corresponding programs (for example, function modules) which lie behind the process codes are extended in the same way as the basic type.

You require development authorizations (authorization object S_IDOCDEFT, for example, in the role SAP_BC_SRV_EDI_DEVELOPER) for the extensions. Development takes place in the customer system.

Process flow

The following subsections contain the individual steps. The list can be used as a checklist when creating the extension. More information about the required steps and any alternatives can be found in the process flow diagram.

With the help of an example, you can define an actual IDoc type and process the type in a number of different ways. The example is used in each individual step. As a prerequisite, master data for the test customer TESTCUST (partner type KU) and the test vendor TESTVEND (partner type LI) must be present in the system. In addition, the example also assumes that the file port TESTPORT has been created.

Process flow diagram

Individual steps

General Definitions

· Combining Segments

· Extending Basic Types

· Assign Message Type Basic Type and Extension

Configuring outbound processing (outbound under Message Control)

· Extending Outbound Function Modules

· Changing Partner Profiles (Outbound)

· Testing Outbound Processing

Configuring inbound processing (direct inbound processing using ALE function module)

· Extending Inbound Function Modules

· Extending Function Module Assignments (Direct Inbound)

· Checking Partner Profiles (Inbound)

· Testing Inbound Processing

see this link

http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b7d6243d711d1893e0000e8323c4f/content.htm

thanks

sagar

reward me if usefull

2 REPLIES 2
Read only

Former Member
0 Likes
424

HI Elham,

Extending an IDoc Type

Purpose

In the case of a customer extension, you add additional segments to an IDoc type supplied by SAP (basic type), so that you can transfer more (or simply other) business information. This extension is upward compatible, that is, it will be supported by future releases.

Prerequisites

This checklist requires that the basic type to be extended is already included in the processing: This means, in particular, that the processing (inbound and outbound) is defined using process codes in the partner profiles and that the corresponding programs (for example, function modules) which lie behind the process codes are extended in the same way as the basic type.

You require development authorizations (authorization object S_IDOCDEFT, for example, in the role SAP_BC_SRV_EDI_DEVELOPER) for the extensions. Development takes place in the customer system.

Process flow

The following subsections contain the individual steps. The list can be used as a checklist when creating the extension. More information about the required steps and any alternatives can be found in the process flow diagram.

With the help of an example, you can define an actual IDoc type and process the type in a number of different ways. The example is used in each individual step. As a prerequisite, master data for the test customer TESTCUST (partner type KU) and the test vendor TESTVEND (partner type LI) must be present in the system. In addition, the example also assumes that the file port TESTPORT has been created.

Process flow diagram

Individual steps

General Definitions

· Combining Segments

· Extending Basic Types

· Assign Message Type Basic Type and Extension

Configuring outbound processing (outbound under Message Control)

· Extending Outbound Function Modules

· Changing Partner Profiles (Outbound)

· Testing Outbound Processing

Configuring inbound processing (direct inbound processing using ALE function module)

· Extending Inbound Function Modules

· Extending Function Module Assignments (Direct Inbound)

· Checking Partner Profiles (Inbound)

· Testing Inbound Processing

see this link

http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b7d6243d711d1893e0000e8323c4f/content.htm

thanks

sagar

reward me if usefull

Read only

0 Likes
423

Hi Sagar,

Thanks for the info.

The issue is that I am trying to create a new basic type using the current one as the predecessor. Thsi would be for the SAP in the new release.

Extending it by the customer is not an issue here.

Regards,

-Elham