topic Re: Regarding idoc in Application Development and Automation Discussions

Regarding idoc

Former Member — Fri, 11 Jan 2008 12:47:27 GMT

Hello every1

i have one billing doc. no. , and i have one client i want to know how i can create Partener profile, idoc and how i can assign my billing doc to Idoc, please describe me all the steps from logical system to outbound process its urgent. waiting for your reply.

Thanks & Regards

Vimarsh B.

Re: Regarding idoc

former_member404244 — Fri, 11 Jan 2008 12:54:46 GMT

Hi,

The transaction codes that are required for ur method are

We81

We30

We31

We82

We21

We20

Bd64

Nace

Message type: INVOIC

Idoc type: INVOIC02

Outbound process code for purchase order: SD09

Regards,

nagaraj

Re: Regarding idoc

Former Member — Fri, 11 Jan 2008 13:04:36 GMT

Hi Vimarsh,

These are some of the the transactions used in idocs.

SALE Area Menu for ALE configurations.It includes transactions for

Logical System definition and linking it to a client, Transactions for

RFC Destination and Port Definition Etc.

SM59 RFC Destination

Here we specify the login settings for the destination including

the I.P address or Application Server name and the User name and

password.The information entered here is used to run Remote Function

Calls(RFC ) on the destination server .We can create number of types

of RFC Destinations but 3 types are important .

R/3 (R/3 to R/3), LS(logical system) and TCP/IP.

The name of the RFC destination should be same as that of Logical

System as it helps in creation of automatic partner profiles.

WE21 Port Definition.

There are 6 types of ports but only 2 types File and Transactional RFC

types of ports are important.

We have to specify the RFC Destination before a port can be created.

WE57 This is used to assign the Inbound function module to the Message Type

and to the IDOC Type.

WE42 This is used to define the process Code for Inbound Processing.

BD95 Define Filter object type .We can specify the field and the table it belongs

to as a filter object .

BD59 Assignment of Filter object type to the Message Type .Here we create the

link between Filter object and the segment and the message type and the

segment Field.

BD50 Set message Type to reducible.

BD65 Define Mandatory Fields.

BD64 Distribution Model . Also known as Customer Distribution Model Used to

define all the messages that will be exchanged between remote systems

and the name of thes logical systems. Any filters can also be specified.

The model once created has to be distributed on every system which will

be communicating ,It can be maintained on only One system.

BD21 Creating IDOcs from change pointers.

This can be used to create IDOCs from change pointers for a particular

message LIKE MATMAS.

BD22 This can be used to delete change pointers.

BD87 Status Monitor. Idocs can be selected base on number of criteria and there

processing status can be seen in detail.

BD10 Material Master Data Distribution .

Based on Message MATMAS.

BD12 Customer Master Data Distribution .

Based on Message CREMAS.

BD14 Vendor Master Data Distribution

Based on Message DEBMAS .

BDFG Generate ALE Interface for BAPI.

Here we specify the Business Object and the BAPI Function module for

which the interface has to be created.

WE31 Segment Editor.

This is used to create segments. We create the segment type and

segment definition is automatically created by editor e.g. Z1DUMMY is

segment type and Z2DUMMY is the segment definition .We specify the

fields and the data elements these cporresponds to create segments.

WE30 IDOC Editor

It is used to create a new IDOC Type or IDOC Extension .We specify the

segments that will be addd to the IDOC type.

WE02/05 IDOC List.

Various selct options and parameters are provided to select IDOCs

depending on the date, direction , mesage type etc.

WE20 Partner Profile

Here we create partner profile for each and every partner from / to which

the messages will be exchanged.There are 6 types of PF generally only

profiles of type LS(Logical System) ,KU(Customer) ,LI(Vendor) is used.

We specify the partner number and partner type and the agent and

the agent type responsible for handling of errors .

For every message send to the partner we have a outbound record and for

evry message coming from the partner we have the inbound record .

We specify the message in the otbound/inbound records ,double

clicking will take us to the detailed screen where the IDOC Type ,Port

and whether the IDCO will be immediatelt processed or collected are

mentioned.

Check thes links :

http://www.sapsecurity.co.uk/index.php?option=com_dbquery&Itemid=36&task=ExecuteQuery&qid=1&limit=1000&limitstart=11000

ttp://azustyle.blogspot.com/2007/08/idoc-technical-document.html

http://sap.niraj.tripod.com/id51.html

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

ALE/ IDOC

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

Check these step-by-step links

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/ccab6730-0501-0010-ee84-de050a6cc287

https://sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/8fd773b3-0301-0010-eabe-82149bcc292e

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/3c5d9ae3-0501-0010-0090-bdfb2d458985

http://idocs.de

These links have helped me.These links have screenshots of the step by step procedure that is to be carried out right from creating an idoc type till the outbound processing.

This is a sample function module which is used in IDOCs.This might help you better understand about the process codes and function module in IDOCs.:

CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'

EXPORTING

VALUE(MASTER_IDOC_CONTROL) LIKE EDIDC STRUCTURE EDIDC

" Control record of master IDoc

VALUE(OBJ_TYPE) LIKE SERIAL-OBJ_TYPE DEFAULT ''

VALUE(CHNUM) LIKE SERIAL-CHNUM DEFAULT ''

TABLES

COMMUNICATION_IDOC_CONTROL STRUCTURE EDIDC

" Control records of created comm. IDocs

MASTER_IDOC_DATA STRUCTURE EDIDD

" Data records of master IDoc

EXCEPTIONS

ERROR_IN_IDOC_CONTROL

" Incorrect entry in IDoc control record

ERROR_WRITING_IDOC_STATUS

" Error when writing IDoc status records

ERROR_IN_IDOC_DATA

" Incorrect entry in IDoc data records

SENDING_LOGICAL_SYSTEM_UNKNOWN

" Own logical system unknown

CALL FUNCTION 'CHANGE_POINTERS_READ'

EXPPORTING

VALUE(ACTIVATION_DATE_HIGH) LIKE SY-DATUM DEFAULT SPACE

VALUE(ACTIVATION_DATE_LOW) LIKE SY-DATUM DEFAULT SPACE

VALUE(ACTIVATION_TIME_HIGH) LIKE SY-UZEIT DEFAULT '000000'

VALUE(ACTIVATION_TIME_LOW) LIKE SY-UZEIT DEFAULT '000000'

VALUE(CHANGE_DOCUMENT_OBJECT_CLASS) LIKE CDPOS-OBJECTCLAS

DEFAULT SPACE

VALUE(CREATION_DATE_HIGH) LIKE SY-DATUM DEFAULT SPACE

VALUE(CREATION_DATE_LOW) LIKE SY-DATUM DEFAULT SPACE

VALUE(CREATION_TIME_HIGH) LIKE SY-UZEIT DEFAULT '000000'

VALUE(CREATION_TIME_LOW) LIKE SY-UZEIT DEFAULT '000000'

VALUE(MESSAGE_TYPE) LIKE BDCPS-MESTYPE

VALUE(READ_NOT_PROCESSED_POINTERS) LIKE BDCPS-PROCESS DEFAULT

'X'

TABLES

CHANGE_POINTERS STRUCTURE BDCP

MESSAGE_TYPES STRUCTURE BDMSGTYP OPTIONAL

EXCEPTIONS

ERROR_IN_DATE_INTERVAL

ERROR_IN_TIME_INTERVAL

CALL FUNCTION change_pointers_status_write.

IMPORTING

VALUE(MESSAGE_TYPE) LIKE EDIDC-MESTYP

TABLES

CHANGE_POINTERS_IDENTS STRUCTURE BDICPIDENT

Examples of Inbound function modules are

IDOC_INPUT_BLAOCH IDoc inbound processing: change Ccontract

IDOC_INPUT_BLAORD IDoc inbound processing: Create Contract

IDOC_INPUT_MATMAS01 IDoc inbound processing: Material Master

Examples of Outbound function modules are

IDOC_OUTPUT_BLAOCH

IDOC_OUTPUT_BLAORD

<REMOVED BY MODERATOR>

Regards,

Kashyap Ivaturi

Edited by: Kashyap Ivaturi on Jan 11, 2008 2:09 PM

Edited by: Alvaro Tejada Galindo on Jan 11, 2008 5:20 PM

Re: Regarding idoc

Former Member — Fri, 11 Jan 2008 13:06:09 GMT

Hi Nag

Thanks for ur reply, i want to know from where i have to start, i have one partener profile, i got one billing doc. so what i will do with this two, actually i am very new for ALE IDoc, so can you please elaborate ur answer.

Thanks & Regards

Vimarsh B.

Re: Regarding idoc

Former Member — Fri, 11 Jan 2008 13:21:27 GMT

Hi,

Link for step by step procedure for IDOCS----

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

Useful transactions------

•Bd87 is the transaction for manual processing of idoc.

• WE47 is for viewing all idoc status information.

•WE 20 Maintain partner profiles manually

•BD82 Generate partner profiles automatically

•WE21 Port definitions

•SM59 RFC Definitions

•BD64 Customer Model

•WE19 Test tool for Idocs

•WE02 Idoc Display

•WE05 Idoc list

•WE60 Idoc documentation

•WE 31 Segment Editor

•WE 30 Idoc editor to create and extend IDoc

•WEDI Main menu for EDI related activities

•BALE Main menu for ALE related activities

•SALE Main Menu for ALE Configuration

Statuses of IDOCs---

See table TEDS1 for all status codes via SE16 in SAP. Outbound ALE Status Codes

Successful Transmission:

03 - Successful outbound transmission

12 - Dispatch OK

IDoc being processed:

01 - IDoc created

30 - IDoc ready for dispatch (ALE service) (Program RSEOUT00 needs to be executed)

ALE Error Messages:

02 - Error passing data to port

04 - Error within control information on EDI subsystem

05 - Error during translation

25 - Processing despite syntax errors (outbound)

29 - Error in ALE service

32 - Resubmit edited intermediate document (DO NOT USE)

Syntax Error Messages:

26 - Error during syntax check of IDoc (outbound) Inbound ALE Status Codes

IDoc Processed Successfully:

50 - IDoc added

53 - Successful posting

IDoc ready for processing:

64 - IDoc ready to be passed to application. The IDoc will be passed to the application by program RBDAPP01.

Errors in IDoc Processing:

51 - Error - application document not posted

56 - IDoc with errors added (You should never see this error code)

60 - Error during syntax check of IDoc (inbound)

61 - Processing despite syntax error (inbound)

63 - Error passing IDoc to application

65 - Error in ALE service - indicates partner profiles are incorrect

69 - IDoc was edited

thanks and regards

suma sailaja pvn

Re: Regarding idoc

Former Member — Fri, 11 Jan 2008 13:28:28 GMT

Hi Vimarsh,

Follow these steps:

1) Goto Tcode SALE

Click on Sending & Receiving Systems à Select Logical Systems

Here Define the Logical Systems à Click on Execute Button

Go for New Entries

1) System Name : LOG1

Description: Sending System

2) System Name : LOG2

Description: Receiving System

Press Enter & Save it will ask for Request if you want new request create new request or press continue for transferring the objects.

Assigning Client to the Logical System:

Select Assign Client to Logical Systems -> Execute

Ø 100 -> Double click on this and give the following information

Client : Sending System

City : Chennai

Logical System : LOG1

Currency :

Client role :

Ø 250 -> Double click on this and give the following information

Client : Receiving System

City :

Logical System : LOG2

Save this Data.

Step 2) For RFC Creation:

· Goto Tcode SM59 -> Select R/3 Connects

Click on create Button

RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles

Give the information for required fields:

RFC Destination : LOG2

Connection type : 3

Target Host :

System No : 00

Client :

User : Login user name

Password :

Save this & Test it and Remote Login

Step 3) Goto Tcode BD64: – Click on the change button

Click on the create model view

Short Text: model view

Technical Name: LMOD

Save this & press ok

Select just created model view

Name: “LMOD”

Goto add message type

Model Name : LMOD

Sender : LOG1

Receiver : LOG2

Message type: ZAZHARMESS

Save and press Enter.

4) Goto Tcode BD82:

Give Model View : LMOD

Partner system : LOG2

Execute this by pressing F8

It will gives you sending system port No: A00000000089 (Like)

5) Goto Tcode BD64:

Select the model view

Goto à Edit à model view à Distribute

Press ok & Press Enter.

Run your Zprogram

This sample program might help you.

DATA: Begin of imara occurs 0,

matnr like mara-matnr,

mtart like mara-mtart,

end of imara.

DATA: wamas_con LIKE edidc,

imas_data LIKE edidd OCCURS 0 WITH HEADER LINE,

icom_con LIKE edidc OCCURS 0 WITH HEADER LINE.

PARAMETERS: e_matnr LIKE mara-matnr,

e_msgtyp LIKE edidc-mestyp,

e_rcvprn LIKE edidc-rcvprn.

retrive app. data from DB

SELECT matnr mtart FROM mara INTO TABLE imara WHERE

matnr = e_matnr.

*Master idoc control record

wamas_con-rcvprt = 'LS'.

wamas_con-rcvprn = e_rcvprn.

wamas_con-idoctp = 'ZAZHARIDOC'.

wamas_con-mestyp = e_msgtyp.

master idoc data records

LOOP AT imara.

imas_data-segnam = 'ZAZHARSEG'.

move imara to imas_data-sdata .

APPEND imas_data.

ENDLOOP.

CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'

EXPORTING

master_idoc_control = wamas_con

TABLES

communication_idoc_control = icom_con

master_idoc_data = imas_data

COMMIT WORK.

6) Verifying Transfer of IDOCs Tcode – we05

ALE/IDOC Status Codes (outbound):

01 IDoc Added

30 IDoc ready for dispatch

29 Error in ALE service Layer

12 Dispatch ok

03 Data passed to port ok.

Inbound Process (Receiving System) Steps:

Do the same step as you did in sending system

Creating IDoc

Defining the Segment

Creating Message Type

Assigning the Message Type

Defining the Logical System

Assigning the Logical System

Creating the Distribution Model

Goto Tcode – we57:

Assign function module to IDoc type

Module: Function module

Basic type:

Message type:

Direction: 2 (inbound)

Creating Inbound process code – we42

Verifying Idoc List Tcode – we05

ALE/IDOC Status Codes (Inbound):

50 IDoc Added

51 Application Document not posted

64 IDoc ready to be transferred to application

62 IDoc passed to application

53 Application Document posted

<REMOVED BY MODERATOR>

Regards,

Kashyap Ivaturi

Edited by: Alvaro Tejada Galindo on Jan 11, 2008 5:20 PM