Manual Idoc Creation

Hi
Someone today pointed to me that its possible to create/trigger a IDoc manually, i mean we have one inbound IDoc in Production server data comes from External vendor creates SO there is some problem in that Idoc.
to replicate the same scenario in Quality first i need to create a Idoc (For which data has to come from Ext vendor but its nor possible) for that some one pointed out that you can copy the same Idoc or create the same idoc in quality.
Can anyone explain me wahts the Tcode and how do we do the same?
Reg
Shankar1242

Hi,
Go to tcode-we19 and in the initial screen give your idoc number if you have any existing idoc of same type press enter then on the application toolbar there is a pushbutton standard inbound if you press this push button it will create same idoc.
If you want to change the data it is also possible.
If you have no existing idoc number then give basic type such as orders05 and press enter then it will dispalys screen with all segments in these segments fill the requried data and execute then you will get idoc number which is created.
Thanks,
shyla

Similar Messages

No cubes are reflecting in XIP ,after creation of manual IDOC

Hi Experts,
I am got a mail from client saying that "No cubes are reflecting in XIP ,after creation of manual IDOC"..
Please tell me weather this is issue is related to XI or not if it so, Can you please anybody tell me how to look into this type of issue...
Please help me..
Many thanks in advance..
Regards
Raj

Hi ,
Thank you Sourabh, so I need to get the IDOC basic type from customer and need to check the IDOC using IDX5. Please correct me if I am wrong..
With Warm Regards
Raj

IDOC creation after the creation of a purchase order

Hi everybody,
 I want some configuration details regardign IDOC creation. The requirement is, once i create a purchase order in one system, the details should automatciaclly transfer to other system through IDOC. could any one suggest any document or detailed procedure to accomplish the task. Thanks in advance,
 Santosh.

hi santosh kumar,
Creating an IDoc Segment WE31:
The segment defines the structure of the records in an IDoc. They are defined with transaction WE31.
We will define a structure to send a text from the text database.
Transaction WE31 calls the IDoc segment editor. The editor defines the fields of a
single segment structure. The thus defined IDoc segment is then created as a data
dictionary structure. You can view the created structure with SE11 and use it in an
ABAP as any TABLES declaration.
To demonstrate the use of the IDoc segment editor we will set up an example, which
allows you to send a single text from the text pool (tables STXH and STXL) as an
IDoc. These are the texts that you can see with SO10 or edit from within many
applications.
We will show the steps to define an IDoc segment YAXX_THEAD with the DDic
structure of THEAD.
To facilitate our work, we will use the "copy-from-template-tool", which reads the
definition of a DDIC structure and inserts the field and the matching definitions as
rows in the IDoc editor. You could, of course, define the structure completely
manually, but using the template makes it easier.
The tool in release 4.0b lets you use both DDIC structures or another IDoc segment
definition as a template.
The thus created structure can be edited any time. When saving, it will create a data
dictionary structure based on the definition in WE31. The DDIC structure will retain
the same name. You can view the structure as a table definition with SE11 and use it
in an ABAP the same way.
Defining the Message Type (EDMSG)
The message type defines the context under which an IDoc is transferred to its destination. It allows for using the same IDoc file format for several different applications.
Imagine the situation of sending a purchase order to a supplier. When the IDoc with
the purchase order reaches the supplier, it will be interpreted as a sales order
received from a customer, namely you.
Simultaneously you want to send the IDoc data to the supplier's warehouse to inform
it that a purchase order has been issued and is on the way.
Both IDoc receivers will receive the same IDoc format; however, the IDoc will be
tagged with a different message type. While the IDoc to the supplier will be flagged
as a purchase order (in SAP R/3 standard: message type = ORDERS), the same IDoc
sent to the warehouse should be flagged differently, so that the warehouse can
recognize the order as a mere informational copy and process it differently than a
true purchase order.
The message type together with the IDoc type determine the processing function.
The message types are stored in table EDMSG.
Defining the message type can be done from the transaction WEDI
EDMSG: Defining the message type (1)
The entry is only a base entry which tells the system that the message type is
allowed. Other transactions will use that table as a check table to validate the entry.
IT is as shown .
EDMSG: Defining the message type (1):
The entry is only a base entry which tells the system that the message type is
allowed. Other transactions will use that table as a check table to validate the entry.
Sales Orders are being created through inbound IDocs using FM 'EDI_DATA_INCOMING'. Now a Report is required to check the status of these Inbound IDocs along with Sales Orders generated against customer Purchase Orders.
Requirement:
Sales Orders are being created through inbound IDocs using FM 'EDI_DATA_INCOMING'. Now a Report is required to check the status of these Inbound IDocs along with Sales Orders generated against customer Purchase Orders.
Processing:
The report selects, 'ORDERS' IDoc numbers & status, generated between given time range, from table EDIDC. Further, it calls Function Module 'IDOC_READ_COMPLETELY' to get the IDoc details. Then required information is extracted by reading relevant field data of IDoc segments.
sampl code:
REPORT Z_EDI_FILE_LOAD_STATUS_REPORT .
Staus Report for Inbound IDOCs ( Sales Orders )
Program : Z_EDI_FILE_LOAD_STATUS_REPORT
Presented By : www.rmtiwari.com
TABLES : EDIDC.
ALV stuff
TYPE-POOLS: SLIS.
DATA: GT_FIELDCAT TYPE SLIS_T_FIELDCAT_ALV,
 GS_LAYOUT TYPE SLIS_LAYOUT_ALV,
 GT_SORT TYPE SLIS_T_SORTINFO_ALV,
 GT_LIST_TOP_OF_PAGE TYPE SLIS_T_LISTHEADER.
DATA : BEGIN OF T_REPORT OCCURS 0,
 IDOC_NO TYPE EDI_DOCNUM,
 IDOC_DATE TYPE SY-DATUM,
 IDOC_TIME TYPE SY-UZEIT,
 SORDER_NO TYPE VBELN,
 STP_NO TYPE KNA1-KUNNR,
 STP_NAME(35) TYPE C,
 STP_PHONE(12) TYPE C,
 PO_NO(15) TYPE C,
 STATUS TYPE C,
 S_TEXT(70) TYPE C,
 ERROR(70) TYPE C,
 END OF T_REPORT.
--PARAMETER--
selection-screen begin of block date with frame title TEXT-S01.
select-options: UDATE for EDIDC-UPDDAT
 default SY-datum obligatory, "Changed On
 UTIME for EDIDC-UPDTIM . "Changed Time
selection-screen end of block date.
INITIALIZATION.
START-OF-SELECTION.
PERFORM SHOW_STATUS_REPORT.
*& Form alv_grid
 text
--> p1 text
< -- p2 text
FORM ALV_GRID.
IF GT_FIELDCAT[] IS INITIAL.
 PERFORM FIELDCAT_INIT.
 PERFORM LAYOUT_INIT.
 PERFORM SORT_INIT.
ENDIF.
PERFORM GRID_DISPLAY.
ENDFORM. "alv_grid
*& Form layout_init
FORM LAYOUT_INIT.
GS_LAYOUT-ZEBRA = 'X'.
GS_LAYOUT-CELL_MERGE = 'X'.
GS_LAYOUT-COLWIDTH_OPTIMIZE = 'X'.
GS_LAYOUT-NO_VLINE = ' '.
GS_LAYOUT-TOTALS_BEFORE_ITEMS = ' '.
ENDFORM. " layout_init
*& Form fieldcat_init
FORM FIELDCAT_INIT.
DATA: LS_FIELDCAT TYPE SLIS_FIELDCAT_ALV.
 CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME = 'IDOC_NO'.
LS_FIELDCAT-KEY = 'X'.
LS_FIELDCAT-REPTEXT_DDIC = 'IDOC'.
LS_FIELDCAT-OUTPUTLEN = 10.
Fix for ALV print bug, which puts 'N/A' over last digit
Set inttype to 'N' to stop corruption of printed ALV cell.
LS_FIELDCAT-INTTYPE = 'N'.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME = 'IDOC_DATE'.
LS_FIELDCAT-REPTEXT_DDIC = 'Creation Date'.
LS_FIELDCAT-OUTPUTLEN = 10.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME = 'IDOC_TIME'.
LS_FIELDCAT-REPTEXT_DDIC = 'Creation Time'.
LS_FIELDCAT-OUTPUTLEN = 8.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME = 'STATUS'.
LS_FIELDCAT-REPTEXT_DDIC = 'St'.
LS_FIELDCAT-OUTPUTLEN = 2.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME = 'ERROR'.
LS_FIELDCAT-REPTEXT_DDIC = 'Message'.
LS_FIELDCAT-OUTPUTLEN = 70.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME = 'STP_NO'.
LS_FIELDCAT-REPTEXT_DDIC = 'S.T.Party No'.
LS_FIELDCAT-OUTPUTLEN = 10.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME = 'STP_NAME'.
LS_FIELDCAT-REPTEXT_DDIC = 'Sold to Party Name'.
LS_FIELDCAT-OUTPUTLEN = 35.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME = 'PO_NO'.
LS_FIELDCAT-REPTEXT_DDIC = 'Purch Order'.
LS_FIELDCAT-OUTPUTLEN = 15.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME = 'STP_PHONE'.
LS_FIELDCAT-REPTEXT_DDIC = 'S.T.Party Phone'.
LS_FIELDCAT-OUTPUTLEN = 15.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
ENDFORM. "fieldcat_init
*& Form sort_init
FORM SORT_INIT.
DATA: LS_SORT TYPE SLIS_SORTINFO_ALV.
CLEAR LS_SORT.
LS_SORT-FIELDNAME = 'IDOC_DATE'.
LS_SORT-SPOS = 1.
LS_SORT-UP = 'X'.
APPEND LS_SORT TO GT_SORT.
CLEAR LS_SORT.
LS_SORT-FIELDNAME = 'IDOC_TIME'.
LS_SORT-SPOS = 2.
LS_SORT-UP = 'X'.
APPEND LS_SORT TO GT_SORT.
CLEAR LS_SORT.
LS_SORT-FIELDNAME = 'STATUS'.
LS_SORT-SPOS = 3.
LS_SORT-UP = 'X'.
APPEND LS_SORT TO GT_SORT.
CLEAR LS_SORT.
LS_SORT-FIELDNAME = 'IDOC_NO'.
LS_SORT-SPOS = 4.
LS_SORT-UP = 'X'.
APPEND LS_SORT TO GT_SORT.
ENDFORM. "sort_init
*& Form grid_display
FORM GRID_DISPLAY.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
 EXPORTING
 IS_LAYOUT = GS_LAYOUT
 IT_FIELDCAT = GT_FIELDCAT
 IT_SORT = GT_SORT
 i_callback_program = SY-REPID
 I_CALLBACK_TOP_OF_PAGE = 'TOP_OF_PAGE'
 I_DEFAULT = ' '
 I_SAVE = 'X'
 TABLES
 T_OUTTAB = T_REPORT
 EXCEPTIONS
 PROGRAM_ERROR = 1
 OTHERS = 2.
ENDFORM. "grid_display
*& Form COMMENT_BUILD
 Processing of listheader
FORM COMMENT_BUILD USING P_FK_LIST_TOP_OF_PAGE TYPE SLIS_T_LISTHEADER.
DATA: LS_LINE TYPE SLIS_LISTHEADER.
REFRESH P_FK_LIST_TOP_OF_PAGE.
List Heading : Typ H
CLEAR LS_LINE.
LS_LINE-TYP = 'H'.
LS_LINE-INFO = 'Sales Order Interface: Z_EDI_FILE_LOAD'.
APPEND LS_LINE TO P_FK_LIST_TOP_OF_PAGE.
List : Typ S
clear LS_LINE.
LS_LINE-typ = 'S'.
LS_LINE-key = 'Date Range:'.
LS_LINE-info = UDATE-low.
if not UDATE-high is initial.
 write ' To ' to LS_LINE-info+30.
 LS_LINE-info+36 = UDATE-high.
endif.
APPEND LS_LINE TO P_FK_LIST_TOP_OF_PAGE.
ENDFORM. " COMMENT_BUILD
 FORM TOP_OF_PAGE *
 Ereigniss TOP_OF_PAGE *
 event TOP_OF_PAGE
FORM TOP_OF_PAGE.
PERFORM COMMENT_BUILD USING gt_LIST_TOP_OF_PAGE[].
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
 EXPORTING
 IT_LIST_COMMENTARY = GT_LIST_TOP_OF_PAGE.
ENDFORM. "TOP_OF_PAGE
*& Form show_status_report
FORM SHOW_STATUS_REPORT .
Report to show status.
DATA: BEGIN OF T_TEDS2 OCCURS 0.
 INCLUDE STRUCTURE TEDS2.
DATA: END OF T_TEDS2.
DATA: BEGIN OF T_IDOC_CONTROL_TMP OCCURS 0.
 INCLUDE STRUCTURE EDIDC.
DATA: END OF T_IDOC_CONTROL_TMP.
CONSTANTS: C_STATUS_IN_IDOC_POSTED LIKE EDIDC-STATUS VALUE '53'.
DATA : T_EDIDS TYPE STANDARD TABLE OF EDIDS WITH HEADER LINE.
DATA : T_EDIDD TYPE STANDARD TABLE OF EDIDD WITH HEADER LINE.
DATA : GV_PARTNER_SEG TYPE E1EDKA1,
 GV_PO_REF_SEG TYPE E2EDK02.
Get text for status values
SELECT * FROM TEDS2 INTO TABLE T_TEDS2 WHERE LANGUA = SY-LANGU.
Read the IDoc's status after processing
SELECT * FROM EDIDC
 INTO TABLE T_IDOC_CONTROL_TMP
 WHERE UPDDAT IN UDATE
 AND UPDTIM IN UTIME
 AND MESTYP = 'ORDERS'.
LOOP AT T_IDOC_CONTROL_TMP.
IDoc has been processed, since control record changed.
 READ TABLE T_TEDS2 WITH KEY STATUS = T_IDOC_CONTROL_TMP-STATUS.
 T_REPORT-IDOC_NO = T_IDOC_CONTROL_TMP-DOCNUM.
 T_REPORT-IDOC_DATE = T_IDOC_CONTROL_TMP-CREDAT.
 T_REPORT-IDOC_TIME = T_IDOC_CONTROL_TMP-CRETIM.
 T_REPORT-S_TEXT = T_TEDS2-DESCRP.
 IF T_IDOC_CONTROL_TMP-STATUS = C_STATUS_IN_IDOC_POSTED.
 ok status
 T_REPORT-STATUS = 'S'.
 ELSE.
 error status
 T_REPORT-STATUS = 'E'.
 ENDIF.
 Get IDoc details.
 CALL FUNCTION 'IDOC_READ_COMPLETELY'
 EXPORTING
 DOCUMENT_NUMBER = T_REPORT-IDOC_NO
 TABLES
 INT_EDIDS = T_EDIDS
 INT_EDIDD = T_EDIDD
 EXCEPTIONS
 DOCUMENT_NOT_EXIST = 1
 DOCUMENT_NUMBER_INVALID = 2
 OTHERS = 3.
Get Error status
 READ TABLE T_EDIDS WITH KEY STATUS = T_IDOC_CONTROL_TMP-STATUS.
 IF SY-SUBRC EQ 0.
 REPLACE FIRST OCCURRENCE OF '&1' IN T_EDIDS-STATXT
 WITH T_EDIDS-STAPA1.
 REPLACE FIRST OCCURRENCE OF '&2' IN T_EDIDS-STATXT
 WITH T_EDIDS-STAPA2.
 REPLACE FIRST OCCURRENCE OF '&3' IN T_EDIDS-STATXT
 WITH T_EDIDS-STAPA3.
 REPLACE FIRST OCCURRENCE OF '&4' IN T_EDIDS-STATXT
 WITH T_EDIDS-STAPA4.
 REPLACE FIRST OCCURRENCE OF '&' IN T_EDIDS-STATXT
 WITH T_EDIDS-STAPA1.
 REPLACE FIRST OCCURRENCE OF '&' IN T_EDIDS-STATXT
 WITH T_EDIDS-STAPA2.
 REPLACE FIRST OCCURRENCE OF '&' IN T_EDIDS-STATXT
 WITH T_EDIDS-STAPA3.
 REPLACE FIRST OCCURRENCE OF '&' IN T_EDIDS-STATXT
 WITH T_EDIDS-STAPA4.
 T_REPORT-ERROR = T_EDIDS-STATXT.
 ENDIF.
 LOOP AT T_EDIDD.
 CASE T_EDIDD-SEGNAM.
 WHEN 'E1EDKA1'.
 GV_PARTNER_SEG = T_EDIDD-SDATA.
 CLEAR : T_REPORT-STP_NAME.
 CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 INPUT = GV_PARTNER_SEG-PARTN
 IMPORTING
 OUTPUT = T_REPORT-STP_NO.
 SELECT SINGLE NAME1 TELF1
 INTO (T_REPORT-STP_NAME,T_REPORT-STP_PHONE)
 FROM KNA1
 WHERE KUNNR = T_REPORT-STP_NO.
 WHEN 'E1EDK02'.
 GV_PO_REF_SEG = T_EDIDD-SDATA.
 T_REPORT-PO_NO = GV_PO_REF_SEG-BELNR.
 ENDCASE.
 ENDLOOP.
 APPEND T_REPORT.
ENDLOOP .
SORT T_REPORT BY STATUS IDOC_NO.
Show Report
PERFORM ALV_GRID.
ENDFORM. " show_status_report
thanks
karthik
reward me points if usefull.

Idoc creation TCODE??

Hi
I had created a IDCO,with z-segment with the Vendor Details(LFA1-table) fileds.
Please tell me the TOCDE for Creating the idoc.
Vipin

Hi Vipin,
I am giving you some additional info about idocs:
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.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
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 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
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
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough 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://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
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.
Hope these points help you.
Please reward if any of the above points are helpful.
Regards,
Kalyan Chakravarthy
Edited by: Kalyan Chakravarthy Misra on May 28, 2008 10:45 AM

Problem in Idoc creation in ME22N

Hi All,
We are facing a problem in Idoc creation in transaction ME22N.Our requirement is to trigger an output type and create a idoc everytime a change is made to a particular Purchase Order.
Presently however,for some vendors,when we change the plant at the item level,an Idoc is not created(with a message that the changes are not relevant to create an Idoc).Any other change to the Purchase Order like changes in quantity or price,results in successful Idoc creation.
We have also noticed that this happens only in the case of certain vendors.The Customer Info records and vendor data are all believed to be fine.
Are any other config settings required to be maintained for this?
Thanks in advance!
Regards,
Nejuma Iqbal

Hi Nejuma,
I don't think there is any problem with cofiguration settings.u r getting the idocs for some vendors .
if iam not wrong u r giving LS in the tcode(we20).The method which u r using is change pointers.As u r using standard idoc all the settings will be done.
Only settings u have to do is
1>generate partner profiles(WE20)
2>Distribute model view(BD64).
REGARDS,
Nagaraj

PROBLEM IN CUSTOM IDOC CREATION

Hi Friends,
                I'm facing a problem in custom idoc creation plz try to assist me
1.As per the information i have i'm creating segment in we31
for cremas01 idoc.But when i enter the name for segment i'm getting message "Name range Voilation particular name which i had given is not permitted in customer system?
Plz clarify this,and are there any formalities which i should look for before creating custom idoc?
Good answers will be rewarded.
                                                                          Regards,
                                                                           Vinod.

The Problem might be.... with the naming of the segment.
Standard segments should be created with 'E1' and all the custom segments are created using 'Z1' and the name with 8 characters long only is permitted.
Reward Points if useful.

Idoc creation when sales order is saved

Hi all,
I have a requirement of Idoc creation in CRM 7.0 server. Whenever Sales order will be created , upon SAVE , idoc should be created and will be passed to XI server. This is a scenario of Idoc to XML conversion .
I am new to CRM server . Kindly guide me how to tigger idoc when Sales Order created (Kindly name the transactions).
Thanks & Regards,
Madhura Nadgauda

Hello All,
Link given below describes scenario on similar lines.
[https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/406efa7e-388a-2910-f9b8-81913b0ca57f]
Issue resolved.
Thanks.

R/3 to XI manually IDOC sending and problem:

R/3 to XI manually IDOC sending and problem:
I sent IDOC using we19 transaction from R/3 system. After sending it asks me userid and password for XI system. I give necessary UID and PASS. R/3 system says me sucessfully sent.
I check XI (sxmb_moni) but there is nomessage there.
Problem 1: I don't want R/3 ask me UID and password for XI access
Problem 2: I want to see message in XI (sxmb_moni)
Thanks

Hi Cemil,
>>>>After sending it asks me userid and password for XI system. I give necessary UID and PASS. R/3 system says me sucessfully sent.
check the RFC destination from R3 to XI (SM59)
you will find the right one from your port (We21)
you can also check step by step procedures
for IDOC - XI in my book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Value mapping in the ERP system during IDOC creation

We have a PI File-IDOC scenario.
We can translate simple mappings such as currency or unit of measure in PI(7.1) using the Value Mapping function. For complicated mappings involving business logic (e.g. Tax code which is derived from multiple fields) we want to perform these mapping in the ERP (ECC6) system. Is there an approved generic SAP standard process where these value mappings can be done in the IDOC creation which is still valid when re-processing?
e.g. a specific BADI or enhancement point recommended for these mapping?
There might also be a requirement to add segments based on value mapping logic for example when a tax record segment is only required for a non-zero tax code which is mapped via business logic.
Can someone please direct me in the right direction.

Thanks for your answers but I assumed that using a user exit / Enhancement point was obvious. What I'd like to know is a generic entry point that I can estabolish a IDOC enhancement framework. Somewhere I can call a class containing methods linked to IDOC message types
e.g. Call similar to my prototype (this will be where dependant on mappings certain segments will need to be inserted such as tax segments.
ASSIGN control-mestyp TO <mestyp>.
 CALL METHOD (<mestyp>)
 EXPORTING
 control = control
 data = data
 IMPORTING
 have_to_change = have_to_change
 protocol = protocol
 new_entries = new_entries.
The "entry point" must be processed both at creation and reprocess. We are also dealing with Inbound IDOCs not outbound

Debugging EDI output (IDOC creation) for purchase order...

Hi,
We have a EDI output type defined for Purchase order. When I go to Messages tab in ME22N transaction and repeat the EDI output and save it, it creates a IDOC which I can see using transaction WE02.
Now the problem is there is a user exit which I know gets triggered, when the IDOC is created for this PO. When we do some changes in this user exit, I see those changes are reflected when new IDOC is created. But if I put breakpoint, and do repeat output -> save, the debugger does not stop there.
Is there is some technique I can see the breakpoint stoppage in user exit for IDOC creation during EDI output for Purchase order ?
Regards,
Rajesh

Hi
Youc can set the output Peridoically (After Giving the output type, set the furthere data as periodic).
Save.
Set the break point in your user exit.
Go to se 38 -> Run RSNAST00,
Give the object id (Your PO #)
Give the output type and execute, the control will stop at break point.
Regards,
Baburaj

Manual Report Creation!

Hi friends,
I would like to learn about reports is there any place where i can get some videos about this. And i Especially for time being need to know about manual report creation i have little bit knowledge on creating reports.
Any links to videos or tutors would help me a lot.
Regards,
Manoj Chakravarthy

Hi friends any info on my above request it is of great importance for me please any help would be appreciated.

Regarding Custom IDOC Creation

Hi All,
I Am New to ABAP , Any one Please Give me the Step -By Step Procedure to create Custom IDOC.
I Have this Link with me.
Step by step custom IDOC creation
But I Don't Know that What should i Give field names and Data elements
How to create Field names And Data elements
Regards
Vamsi

Hi,
U need a custom IDOC when the elements in the standard IDOC is not there according to requirement. ex. in IDOC cremas04 u want the Country code should be there.
Then U go for custom iDOC and create a Y/Z i.e custom idoc and add one structure and add the required fiellds.
Check this link for Step by Step guide
http://www.erpgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
CHeck this link for a IDOC ...The steps are mentioned in details about creating custom idoc..
http://www.allsaplinks.com/idocbasicsunderstanding.html
http://www.allsaplinks.com/idoc.html
http://www.allsaplinks.com/idoc_sample.html
Please check this link.
http://help.sap.com/saphelp_46c/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
Regards

Idoc creation debug I ha /   VL02n delevery

Hello ,
I am working on Z transaction   that picks the best carrier after creration of the deliveryand shipement.
This transaction is related with standard SAP transaction that creates idoc and send it to customer .
Some of fields in data segment are not populated correctly.
When I look in delevery > Header > Extras> delevery output>
I can see that idoc is created
"Processing log for program RSNASTED routine EDI_PROCESSING
IDoc '0000000034617883' added"
But when I set up external break points in RSNASTED > EDI_PROCESSING.
I cannot reached the point when the idoc data segment is created .
Break points are external and system & uupdate debuging are activated.
I know that Z transaction is creatin batch input for Vl02n .
Do you know some user exit where idoc is populated with data or
some other vay to get to idoc creation in debugger .
Thanks
Krsto

Hello ,
I am working on Z transaction   that picks the best carrier after creration of the deliveryand shipement.
This transaction is related with standard SAP transaction that creates idoc and send it to customer .
Some of fields in data segment are not populated correctly.
When I look in delevery > Header > Extras> delevery output>
I can see that idoc is created
"Processing log for program RSNASTED routine EDI_PROCESSING
IDoc '0000000034617883' added"
But when I set up external break points in RSNASTED > EDI_PROCESSING.
I cannot reached the point when the idoc data segment is created .
Break points are external and system & uupdate debuging are activated.
I know that Z transaction is creatin batch input for Vl02n .
Do you know some user exit where idoc is populated with data or
some other vay to get to idoc creation in debugger .
Thanks
Krsto

Output type for movement type for IDOC creation

Dear Experts,
Can anybody tell how to create "Output type for different movement types for IDOC creation"
Specially for Movement type used for Inbound & outbound.

Hi,
pls find below link's
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/abap/idoc%2bsteps
BAPI & IDOC material
IDOC Scenario Steps
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://sap.niraj.tripod.com/id51.html
http://www.thespot4sap.com/Articles/SAP_ALE_IDOCS.asp
Changing fields in an Idoc segment
Regards
Raj.

Output type for IDOC creation

Hi Sapgurus,
Can anybody help as per below.
Client has third party interface system from which they access stock data from SAP system to front end system.They required stock quantity.As per below transaction I have to create output type for IDOC creation for below t codes.Pls guide for creating output type.
Note: Consider as per MM point of view.Output type is not for printout,It is for IDOC to display stock at front end system.
MB1C u2013 Inward + Outward (As per movement types)
MB1B u2013 Inward + Outward (As per movement types)
VL02N - Inward + Outward (As per Delivery types (Inbound & Outbound))
VL06G - Outward
VL09 - Inward + Outward (As per Delivery types (Inbound & Outbound)
MB0A u2013 Inward
MB01 u2013 Inward
MBST u2013 Reversal of Inward stock

Hi,,
Check the below idoc WMIVID01
"IDoc for Inventory"" in help.sap.com
regards,
Lalita

Manual Idoc Creation

Similar Messages

Maybe you are looking for