Community
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
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

IDOC process

Former Member

‎2008 Jan 23 5:56 AM

0 Likes
818

gud mrng,

after creating the idoc function module,how are we writing the code?

how are we using the standard idoc?

3 REPLIES 3
Read only

Former Member

‎2008 Jan 23 6:03 AM

0 Likes
530

1) Create segment (WE31)

Of course it will have naming convention for different company. Here are some tips:

If you copy from existing or std segment eg: Z1E1EDP01_01.

If not you can just put Z1….but this is only the example.

2) Create IDOC Types (WE30)

3) Create message type (WE81)

4) Link message type with basic type (WE82)

5) Create FM

In the FM all the attributes should be the same for Inbound or Outbound. Basically you can get an example from the std FM eg: Inbound - IDOC_INPUT_DELVRY

Outbound - IDOC_OUTPUT_SHPMNT.

6) Create Process Code (Inbound - WE41/ Outbound - WE42)

IMPORTANT: Before you key in the FM, you are required to add the FM in this table V_TBD51.

7) Link FM with Basic Type

For testing go to WE19.

Here are some of the std program that you can use for IDOC:

1) RSNAST00 - Issuing Output type

2) RBDINPUT - Processing Inbound idocs

3) RBDAPP01 - Processing Idocs that already processed before

4) RBDSEMAT- Stand alone program to generate IDocs (Send Material)

5) RBDMIDOC - Outbound triggered from change pointer

6) RSEINB00 - Convert file to IDOC in status 64

http://www.sapmaterial.com/idoc_sample.html

http://www.sapmaterial.com/idoc_sample.html

Reward if usefull

Read only

Former Member

‎2008 Jan 23 6:11 AM

0 Likes
530

Hi Priya ,

Check this .....

An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...

1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.

2.IDOCs are independent of the sending and receiving systems.

3.IDOCs are independent of the direction of data exchange.

The two available process for IDOCs are

Outbound Process

Inbound Process

AND There are basically two types of IDOCs.

Basic IDOCs

Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.

Extended IDOCs

Extending the functionality by adding more segments to existing Basic IDOCs.

To Create Idoc we need to follow these steps:

Create Segment ( WE31)

Create Idoc Type ( WE30)

Create Message Type ( WE81)

Assign Idoc Type to Message Type ( WE82)

imp links

http://www.allsaplinks.com/idoc_sample.html

http://www.sapgenie.com/sapedi/idoc_abap.htm

www.sappoint.com

--here u can find the ppts and basic seetings for ALE

http://sappoint.com/presentation.html

www.sapgenie.com

http://www.sapgenie.com/ale/index.htm

WE30 - you can create a IDOC type.

An IDOC with data, will have to be triggered by the application that is trying to send out the data.

Try this..Hope this will help

Steps to configuration(Basis) >>

1. Create Logical System (LS) for each applicable ALE-enabled client

2. Link client to Logical System on the respective servers

3. Create background user, to be used by ALE(with authorizaton for ALE postings)

4. Create RFC Destinations(SM59)

5. Ports in Idoc processing(WE21)

6. Generate partner profiles for sending system

The functional configuration(Tcode: SALE)

• Create a Customer Distribution Model (CDM);

• Add appropriate message types and filters to the CDM;

• Generate outbound partner profiles;

• Distribute the CDM to the receiving systems; and

• Generate inbound partner profiles on each of the clients.

Steps to customize a new IDoc >>>

1. Define IDoc Segment (WE31)

2. Convert Segments into an IDoc type (WE30)

3. Create a Message Type (WE81)

4. Create valid Combination of Message & IDoc type(WE82)

5. Define Processing Code(WE41 for OUT / WE42 for IN)

6. Define Partner Profile(WE20)

Important 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.

Reward if useful.

Regards,

Chitra