topic Re: Hi in Application Development and Automation Discussions

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.

>>>> SAP ALE & IDOC<<<<

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.

Check these links.

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

http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc

http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419

http://www.netweaverguru.com/EDI/HTML/IDocBook.htm

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

http://www.sappoint.com/abap/ale.pdf

http://www.sappoint.com/abap/ale2.pdf

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

http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm

http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm

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

http://www.sappoint.com/abap.html

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

http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc

http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419

http://www.netweaverguru.com/EDI/HTML/IDocBook.htm

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

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

http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs

Please check this PDF documents for ALE and IDoc.

http://www.sappoint.com/abap/ale.pdf

http://www.sappoint.com/abap/ale2.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf

Check below link. It will give the step by step procedure for IDOC creation.

http://www.supinfo-projects.com/cn/2005/idocs_en/2/

Reward Points if Useful

Regards

Gokul

Re: Hi

Former Member — Fri, 17 Aug 2007 06:19:10 GMT

Hi Gokul

Most of the links I unable to get the webpage, I want sample coding to populate the data into Idoc,it may be salesorder,purchase.....

reward point awaiting.....

Re: Hi

Former Member — Fri, 17 Aug 2007 06:40:26 GMT

Hi Thiru,

Check this sample code for IDOC.

FORM F_110_SEND_IDOC.

CONSTANTS:

C_MESTYP TYPE EDIDC-MESTYP VALUE 'ZVISTAPM',

C_DOCTYP TYPE EDIDC-IDOCTP VALUE 'ZVISTAPM01',

C_SEGNAM TYPE EDIDD-SEGNAM VALUE 'Z1VISTAPM'.

DATA:

I_ZVISTA_PM TYPE ZVISTA_PM_T OCCURS 6000,

I_EDIDC TYPE EDIDC OCCURS 0,

I_EDIDD TYPE EDIDD OCCURS 0,

WA_ZVISTA_PM TYPE ZVISTA_PM_T,

WA_EDIDC TYPE EDIDC,

WA_EDIDD TYPE EDIDD,

WA_Z1VISTAPM TYPE Z1VISTAPM,

V_OCCMAX TYPE IDOCSYN-OCCMAX,

V_NBSEG TYPE I.

CLEAR WA_ZVISTA_PM.

CLEAR WA_EDIDC.

Save the message type and the basic IDoc type
in the control segment

MOVE C_MESTYP TO WA_EDIDC-MESTYP.

MOVE C_DOCTYP TO WA_EDIDC-IDOCTP.

Retrieve the maximum number of segments in the basic IDoc
type

SELECT MIN( OCCMAX )

FROM IDOCSYN

INTO V_OCCMAX

WHERE IDOCTYP EQ C_DOCTYP AND SEGTYP EQ C_SEGNAM.

Save the whole ZVISTA_PM_T table content
in the I_ZVISTA_PM internal table.

SELECT *

FROM ZVISTA_PM_T

INTO CORRESPONDING FIELDS OF TABLE I_ZVISTA_PM.

Create a data segment for each line of I_ZVISTA_PM

LOOP AT I_ZVISTA_PM INTO WA_ZVISTA_PM.

MOVE-CORRESPONDING WA_ZVISTA_PM TO WA_Z1VISTAPM.

CLEAR WA_EDIDD.

MOVE C_SEGNAM TO WA_EDIDD-SEGNAM.

MOVE WA_Z1VISTAPM TO WA_EDIDD-SDATA.

APPEND WA_EDIDD TO I_EDIDD.

CLEAR WA_ZVISTA_PM.

CLEAR WA_Z1VISTAPM.

ENDLOOP.

Count the number of data segments

DESCRIBE TABLE I_EDIDD LINES V_NBSEG.

If the number of data segments exceeds the maximum
allowed number, then edit a message in the spool,
then display an error message (quit the program)

IF V_NBSEG GT V_OCCMAX.

WRITE:/ TEXT-003, V_OCCMAX.

MESSAGE E751.

ENDIF.

Call the IDoc creation function

CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'

EXPORTING

MASTER_IDOC_CONTROL = WA_EDIDC

TABLES

COMMUNICATION_IDOC_CONTROL = I_EDIDC

MASTER_IDOC_DATA = I_EDIDD

EXCEPTIONS

ERROR_IN_IDOC_CONTROL = 1

ERROR_WRITING_IDOC_STATUS = 2

ERROR_IN_IDOC_DATA = 3

SENDING_LOGICAL_SYSTEM_UNKNOWN = 4

OTHERS = 5.

If there was an error, display a message (quit the
program)

IF SY-SUBRC NE 0.

MESSAGE E746.

ENDIF.

ENDFORM.

Reward Points if Useful

Regards

Gokul

Re: Hi

Former Member — Fri, 17 Aug 2007 08:55:27 GMT

Hi Murugan,

Check this function module

IDOC_INPUT_MATMAS01

Look at line 272

Check any of the function module starting with

IDOC_INPUT_*

Regards

Arun

Re: Hi

Former Member — Fri, 17 Aug 2007 09:02:12 GMT

Hi Murugan,

Check this Function module for outbound

MASTERIDOC_CREATE_MATMAS

MASTERIDOC_CREATE_*

Customising steps for Outbound

Create Message type We81 or use the already existing one

Create segments we31 or use the already existing one

Create IDOC Type we30 or use the already existing one

Link Message type with IDOC Type we82 or use the already existing one

Create RFC destinations sm59 or use the already existing one

Create port we21 or use the already existing one

Create Partner profile we20

Create Customer Distribution model BD64

Distribute the customer distribution model from the menu

Regards

Arun