创建IDOC:
第一步:WE31 创建IDOC所包含的字段.
第二步:WE30 创建IDOC
把Segment分配给IDOC
第三步:WE81 创建信息类型
第四步:WE82 把IDOC类型与信息类型对应.
第
五步:WE57 Assign Message & Idoc Type to a Function Module for Data
Process
第六步:SM59 Define a RFC connection for Idoc transfer
第七步：WE21 Define a Port ( Assign a RFC destination which created in SM59 )
第八步：WE41/42 Creat Process Code
第九步：WE20 Define a Partner
Profiles( Also creat a Outbound parameters with Port, or Inbound
parameters with Process code )
管理IDOC:
WE02 显示IDOC,可以根据时
间，IDOC类型查找IDOC，查看成功，出错信息。
WE46 IDOC管理(出\入)
WE60 IDOC类型文档
(可以查看IDOC结构,和每个字段的描述.
WE19
根据IDOC号进行IDOC处理，可以修改IDOC值进行补发动作，处理分为内向和外向。
消息配置：
WE20
配置伙伴消息进和出IDOC类型
WE21 配置伙伴。
官方介绍：
What is a IDOC?
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. IDoc is not a process.
- IDocs are
stored in the database.
- In the SAP system, IDocs are stored
in database tables.
- IDocs are independent of the sending
and receiving systems.
- IDocs are independent of the
direction of data exchange.
An IDoc Type is SAP's format for data being moved between
applications. Essentially, SAP has defined what a sales order, financial
statement, invoice, etc will look like electronically. This includes
how fields are grouped together (segments), the order and hierarchy of
these groupings, and the format of each individual field.
If
you're familiar with EDI at all, then an IDoc will look very familiar to
you. Nearly everything you're used to is there: from segment name to
allowable codes to min/max occurs.
It is important to note that
an IDoc Type is really just a structure defined on the system and given a
name (i.e., ORDERS04). An actual IDoc, however, consists of data, which
fits within the defined structure of the IDoc Type. This IDoc is
identified by a number rather than by a type.
Creation of IDOCs
Transaction code: WE 30
Steps of Defining Segment
Creating Segment : Tcode - WE31
Creating Message Type : Tcode -
we81
Assigning Message type to Idoc type: Tcode - we82
Process
The two processes for IDoc are Outbound Process and Inbound Process.
Outbound Process
When the data is sent out from the system, the process is called
Outbound Process and the IDoc is known as Outbound IDoc.
Inbound Process
When the data is coming in, the process is called Inbound Process and
the IDoc is known as Inbound IDoc.
Outbound Process (Sending System) Steps :
1) Goto Tcode SALE:
Creating the logical
system
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 -
Client : Sending System
Logical System : LOG1
and
also
Client : Receiving System
Logical System : LOG2
Save this Data.
Step 2) For RFC Creation:
Goto Tcode SM59 and
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 : sappdc.wipro.com
System
No : 00
Client : 210
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
REPORT ZIDOC1
.
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
1) Goto Tcode - we57:
Assign
function module to IDoc type
Module: Function module
Basic type:
Message
type:
Direction: 2 (inbound)
2) Creating Inbound process
code - we42
3) Verifying Idoc List Tcode - we05
4)
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
----------------------实例 ------------------------------------------------Outbound Idoc-
ls_poitem TYPE ypoitem,
ls_edidc TYPE edidc,
lt_edidc TYPE TABLE OF edidc,
lt_edidd TYPE TABLE OF edidd WITH HEADER LINE.
ls_edidc-mestyp = 'YPO'. "Message Type
ls_edidc-idoctp = 'YPOIDOC'. "IDOC Type
ls_edidc-rcvprt = 'LS'. "Partner Type of Receiver
lt_edidd-segnam = 'YPOHEAD'."结点名称
lt_edidd-dtint2 = 0.
CLEAR ls_pohead.
ls_pohead-ebeln = '4001122334'.
ls_pohead-bukrs = '0400'.
ls_pohead-bedat = '20090630'.
lt_edidd-sdata = ls_pohead. "结点内容
APPEND lt_edidd.
lt_edidd-segnam = 'YPOITEM'.
lt_edidd-dtint2 = 0.
CLEAR ls_poitem.
ls_poitem-ebeln = '4001122334'.
ls_poitem-ebelp = '0001'.
ls_poitem-matnr = '000000000000004527'.
ls_poitem-menge = '3'.
ls_poitem-meins = 'ST'.
lt_edidd-sdata = ls_poitem.
APPEND lt_edidd.
lt_edidd-segnam = 'YPOITEM'.
lt_edidd-dtint2 = 0.
CLEAR ls_poitem.
ls_poitem-ebeln = '4001122334'.
ls_poitem-ebelp = '0002'.
ls_poitem-matnr = '000000000000009289'.
ls_poitem-menge = '5'.
ls_poitem-meins = 'M'.
lt_edidd-sdata = ls_poitem.
APPEND lt_edidd.
EXPORTING
master_idoc_control = ls_edidc "Export
TABLES
communication_idoc_control = lt_edidc "Import
master_idoc_data = lt_edidd "Export
EXCEPTIONS
error_in_idoc_control = 1
error_writing_idoc_status = 2
error_in_idoc_data = 3
sending_logical_system_unknown = 4
OTHERS = 5.
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ELSE.
COMMIT WORK.
WRITE: 'Idoc sent:'.
LOOP AT lt_edidc INTO ls_edidc.
NEW-LINE.
WRITE: 'Idoc number is', ls_edidc-docnum,
'; receiver partner is', ls_edidc-rcvprn,
'; sender partner',ls_edidc-sndprn.
ENDLOOP.
ENDIF.
---------------------------------------实例
----------------------------------Inbound Idoc
ls_chead TYPE ypohead,
ls_citem TYPE ypoitem,
ls_pohead TYPE y02_pohead,
lt_poitem TYPE TABLE OF y02_poitem WITH HEADER LINE.
READ TABLE idoc_contrl INDEX 1.
IF idoc_contrl-mestyp <> 'YPO'.
RAISE wrong_function_called.
ENDIF.
CLEAR: ls_pohead, lt_poitem[].
LOOP AT idoc_data WHERE docnum = idoc_contrl-docnum.
CASE idoc_data-segnam.
WHEN 'YPOHEAD'.
CLEAR: ls_chead, ls_pohead.
ls_chead = idoc_data-sdata.
MOVE-CORRESPONDING ls_chead TO ls_pohead.
WHEN 'YPOITEM'.
CLEAR: ls_citem, lt_poitem.
ls_citem = idoc_data-sdata.
MOVE-CORRESPONDING ls_citem TO lt_poitem.
APPEND lt_poitem.
WHEN OTHERS.
ENDCASE.
ENDLOOP.
INSERT y02_pohead FROM ls_pohead.
IF sy-subrc = 0.
INSERT y02_poitem FROM TABLE lt_poitem.
lv_subrc = sy-subrc.
ELSE. "订单号已经存在
lv_subrc = sy-subrc.
ENDIF.
COMMIT WORK.
CLEAR idoc_status.
idoc_status-docnum = idoc_contrl-docnum.
idoc_status-status = '53'. "IDOC处理成功
APPEND idoc_status.
ELSE.
ROLLBACK WORK.
CLEAR idoc_status.
idoc_status-docnum = idoc_contrl-docnum.
idoc_status-status = '51'. "IDOC不成功
idoc_status-msgty = 'E'. "错误信息
idoc_status-msgid = 'YMSG'.
idoc_status-msgno = '001'.
APPEND idoc_status.
ENDIF.
ENDLOOP.
来自 “ ITPUB博客 ” ，链接：https://blog.itpub.net/16794144/viewspace-671175/ ，如需转载，请注明出处，否则将追究法律责任。
