Idoc Related Material

Hi!
I want to learn Idoc.I want to start it as a beginner.
So pls provide me useful material for this.
Thanxs

hi
you can go to this thread
Re: Basics of Idoc Development
you'll find various useful links which would certainly help you out
regards'
Aakash Banga

Similar Messages

IDOC related to employee deta

Hello,
Can anyone send me an example in IDOC related to employee details
What are the steps to be followed for triggerring IDoc.
Regards,
Libin

Hi Libin,
As for finding your needed idoc.
   1. Choose the transaction WE09 (SAP Menu ® Tools ® IDoc Interface/ALE ® Administration ® Services ® IDoc Search by Contents ® WE09).
   2. Choose the Data Source button to specify whether you want to search for IDocs from the database or the archive (or both) .
   3. If you have set the u201AArchiveu2019 flag, you can select files in the archive information system, or manually.
Regarding to the steps to trigger an idoc , search SDN. But before that you will need to do ALE settings.
http://help.sap.com/saphelp_nw04/helpdata/en/d5/edf15ddcdc11d1890c0000e8216438/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b815e43d711d1893e0000e8323c4f/frameset.htm
Rgds
joel
Edited by: joel trinidade on Feb 23, 2009 5:46 PM

Idoc related issuse

Dear all,
I have some problem in idoc related issuses.i preparing technical documents from FS.
There are some filds coming from the client system to sap systmm,.there r nearly 7 field(parent).
And 9 fields (childs).this is from cls to WBI . I have to conclude TO fileds fromWBI to sap.
How can I pick the fields , shall I send all the fields or some paticuler fields only.. can any one
regars
vc

Hi Libin,
As for finding your needed idoc.
   1. Choose the transaction WE09 (SAP Menu ® Tools ® IDoc Interface/ALE ® Administration ® Services ® IDoc Search by Contents ® WE09).
   2. Choose the Data Source button to specify whether you want to search for IDocs from the database or the archive (or both) .
   3. If you have set the u201AArchiveu2019 flag, you can select files in the archive information system, or manually.
Regarding to the steps to trigger an idoc , search SDN. But before that you will need to do ALE settings.
http://help.sap.com/saphelp_nw04/helpdata/en/d5/edf15ddcdc11d1890c0000e8216438/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b815e43d711d1893e0000e8323c4f/frameset.htm
Rgds
joel
Edited by: joel trinidade on Feb 23, 2009 5:46 PM

URGENT : can any one please give me BAPI related material

Hi there,
please help me i am a new learner to BAPI i dont know any thing about it can any one please send me the BAPI related material and also related videos or screen cams if available.

http://www.sapmaterial.com/?gclid=CN322K28t4sCFQ-WbgodSGbK2g....>ALL
STEP BY STEP for BAPI
http://sap-img.com/abap/bapi-step-by-step-guidance.htm
BAPI Programming Guide
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
BAPI User Guide
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
http://techrepublic.com.com/5100-6329-1051160.html#
http://www.sap-img.com/bapi.htm
http://www.sap-img.com/abap/bapi-conventions.htm
http://www.sappoint.com/abap/bapiintro.pdf
http://ifr.sap.com/catalog/query.asp
http://www.****************/Tutorials/BAPI/BAPIMainPage.htm
step by step BAPI Creation with screen shots.
http://www.sapgenie.com/abap/bapi/example.htm
BAPI Programming guide: -
http://help.sap.com/saphelp_nw04/helpdata/en/e0/9eb2370f9cbe68e10000009b38f8cf/frameset.htm
BAPI user guide: -
http://help.sap.com/saphelp_46c/helpdata/en/7e/5e115e4a1611d1894c0000e829fbbd/frameset.htm
BAPI STEP BY STEP PROCEDURE: -
http://www.sap-img.com/abap/bapi-step-by-step-guidance.htm
Example:-
http://www.erpgenie.com/abap/bapi/example.htm
PDF download: -
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/200dd1cc-589e-2910-98a9-bb2c48b78dfa
list of all bapis
http://www.planetsap.com/LIST_ALL_BAPIs.htm
for BAPI's
http://www.sappoint.com/abap/bapiintro.pdf
http://www.sappoint.com/abap/bapiprg.pdf
http://www.sappoint.com/abap/bapiactx.pdf
http://www.sappoint.com/abap/bapilst.pdf
http://www.sappoint.com/abap/bapiexer.pdf
http://service.sap.com/ale
http://service.sap.com/bapi
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE8/BCFESDE8.pdf
http://www.planetsap.com/Bapi_main_page.htm
http://www.topxml.com/sap/sap_idoc_xml.asp
http://www.sapdevelopment.co.uk/
http://www.sapdevelopment.co.uk/java/jco/bapi_jco.pdf
Also refer to the following links..
http://www.sap-img.com/bapi.htm
http://www.sap-img.com/abap/bapi-conventions.htm
http://www.planetsap.com/Bapi_main_page.htm
http://www.sapgenie.com/abap/bapi/index.htm
Checkout !!
http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
http://techrepublic.com.com/5100-6329-1051160.html#
http://www.****************/Tutorials/BAPI/CustomBAPICreation2/page1.htm
There are 5 different steps in BAPI.
Create BAPI Structure
Create BAPI Function Module or API Method.
Create BAPI object
Release BAPI Function Module.
Release BAPI object.
Step1. Creating BAPI Structure:
Go to <SE11>.
Select Data Type & Enter a name.
Click on Create.
Note: Always BAPI should be in a development class with request number (Not Local Object).
Select Structure & hit ENTER.
Enter the fields from your database. Make sure that the first field is the Primary Key Field.
Then SAVE & ACTIVATE.
Step 2. Creating BAPI module:
Enter TR.CODE <SE37>.
Before entering any thing, from the present screen that you are in, select the menu
Goto -> Function Groups -> Create Group.
Enter a name (Note: This name Must start with ZBAPI)
Let this screen be as it is and open another window and there, enter TR.CODE <SE80).
Click on the Third ICON that says Inactive Objects.
Select the group that you just created and click on Activate.
Notice that the group you created will disappear from the list of inactive objects.
Go back to <SE37> screen and enter a name and hit <ENTER>. Then enter the group name that you just created and activated.
NOTE: When you release a function module the respective group will be attached to that particular application. It cannot be used for any other application. NEVER include an already existing group that is attached to another module.
Now click on the first Tab that says ATTRIBUTES and select the radio button that says remote-enabled module since we will be accessing this from any external system.
Then click on the second tab that says IMPORT.
Enter a PARAMETER NAME, TYPE and the structure you created in the first step. Also select the check box Pa. All remotely enabled functional modules MUST be Pa enabled, where Pa means Passed by Value and if you dont select Pa, then that means it will be passed by reference..
Then click on tab that says EXPORT.
Enter the following as is in the first three fields
RETURN TYPE BAPIRETURN (These 3 field values are always same)
Here also select Pa meaning Pass by value.
Note: BAPIRETURN contains structure with message fields.
Then SAVE and ACTIVATE.
Step 3. Creating BAPI object:
Enter Tr.Code <SWO1> (Note. It is letter O and not Zero).
Enter a name and then click on create. Enter details.
NOTE: Make sure that that Object Type and Program name are SAME.
Enter Application M, if you are using standard table Mara. If you are using your own database then select Z at the bottom.
Then hit <ENTER>.
Now we have to add Methods. High light METHODS and then select the following from the menu:
Goto Utilities -> API Methods -> Add Methods.
Enter function Module name and hit <ENTER>.
Select the second FORWARD ARROW button (>)to go to next step.
Check if every thing looks ok and again click on FORWARD ARROW button (>).
Then select YES and click on <SAVE>.
Now on a different screen goto TR.CODE <SE37>. Enter Function Module name and select from the top menu Function Module -> Release -> Release.
Goback to TR.CODE <SWO1>.
Here select the menu combination shown below in the same order.
Edit -> Change Release Status -> Object Type Component -> To Implemented.
Edit -> Change Release Status -> Object Type Component -> To Released.
Edit -> Change Release Status -> Object Type -> To Implemented.
Edit -> Change Release Status -> Object Type -> To Released.
Then click on <SAVE>.
Then click on Generate Button (4th button from left hand side looks like spinning wheel).
Then Click on the button that says PROGRAM to see the source code.
To check if this is present in work flow goto TR.CODE <BAPI>.
Here it shows business object repository.
First click on the middle button and then select ALL and hit ENTER.
Goto tab ALPHABETICAL and look for the object that you created. This shows that the BAPI object has been created successfully
BAPI/RFC Interface
A remote function call is a call to a function module running in a system different from the caller's.
The remote function can also be called from within the same system (as a remote call), but usually caller and callee will be in different systems.
In the SAP System, the ability to call remote functions is provided by the Remote Function Call interface system (RFC). RFC allows for remote calls between two SAP Systems (R/3 or R/2), or between an SAP System and a non-SAP System.
RFC consists of the following interfaces:-
A calling interface for ABAP programs
Any ABAP program can call a remote function using the CALL FUNCTION...DESTINATION statement. The DESTINATION parameter tells the SAP System that the called function runs in a system other than the caller's.
RFC communication with the remote system happens as part of the CALL FUNCTION statement.
RFC functions running in an SAP System must be actual function modules, and must be registered in the SAP System as "remote".
When both caller and called program are ABAP programs, the RFC interface provides both partners to the communication. The caller may be any ABAP program, while the called program must be a function module registered as remote.
Calling interfaces for non-SAP programs
When either the caller or the called partner is a non-ABAP program, it must be programmed to play the other partner in an RFC communication.
To help implement RFC partner programs in non-SAP Systems, SAP provides-
External Interfaces
RFC-based and GUI-based interfaces can be used by external programs to call function modules in SAP R/2 or R/3 systems and execute them in these systems.
Vice versa, ABAP programs in R/2 or R/3 can use the functions provided by external programs via these interfaces.
Reward points..

Regarding IDOC's Material

Hi,
Can any one help me with IDOC's Material,
Thanx ,
Suresh

Hi Kutam,
Please check this online document for ALE and IDoc.
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
Also check this links for additional information.
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
Hope this will help to start with.
Regards,
Ferry Lianto
Please reward points if helpful.

Any BAPI or IDoc related to Warehouse Bin Master conversion

hi all,
Is there any BAPI or IDoc related to warehouse Bin Master conversion?
Regards,
Asha

There is no standard BAPI / IDOC for this.
Created custom BAPI for this.

ALE IDOC Transfering Material Master From One Client to Another Client

I am using ALE Idoc transfering material master from one client to another client with MATMAS msgtype the details of Idoc received on receiver side is showing message i.e no Idoc is selected at receiving side after passing partner number in WE02 transaction.
As I am new to ALE/IDOCS , I am transferring material master from one client to another client with in same system on IDES using ALE/Idocs the details of IDOC received on receiver side is showing message i.e no IDOC is selected at receiving side after passing partner number in WE02 transaction and showing current status 51 instead of 53 i.e no details of IDOC is received at receiver side using MATMAS Message-Type. It is <removed by moderator>
Kindly provide solution.
Naveen
Message was edited by: Naveen Grover
Message was edited by: Manish Kumar : Subject and formatting changed

Hello Naveen,
If the connection is available (test with SM59 + Connection identifier),
after choosing your Connection you can test the connection:
you might find the idocs with the daate when they where sent in SM58:
The message says in this case there was no service, there might also be other errors like "wrong password" and so on.
After solving the error, you can restart sending the idoc from this screen.
Hope this helps .
Regards,
Gerlinde

What is the need of xi in idoc to idoc related scenarios

Hi all,
Can any one explain me what is the need of xi in idoc to idoc related scenarios.\
we can Send Idoc with out Xi right?
Thanks,
Srinivas

IDOC to IDOC Scenario
pass through idoc to idoc scenario
IDoc to IDoc Scenario with High Volumes
SM58 Error For IDOC to IDOC Scenario

Problem with mass IDoc for Material Master

Hi All,
Can anyone suggest a solution to work with mass IDocs for Material master?
We have DEBMDM and CREMDM as mass capable IDocs for Customer and Vendor. How do we get mass Material Master IDocs from R/3 in a single XML file?
Also the standard Material repository supplied with SAP MDM 5.5 SP3 doesn't have any XSD definition for MATMDM. Can anyone throw some light on this problem?
Regards
Pooja

Hello Pooja:
The standard way to do it is to generate a single file containing multiple idocs (And for the sake of performance, I suggest you stick to this technique).
In the case of material master, everything is straight forward. In the case of customer and vendor master, when data flows from R/3 to MDM no idoc conversion needs to be performed by XI.
However, for the case of customer and vendor master, when data flows from MDM to R/3, XI needs to separate the data in CREMDM to CREMAS and ADRMAS in order for R/3 to be able to process the idocs; as well as separate the data in DEBMDM to DEBMAS and ADRMAS.
The good thing is that you do not need to worry about all this mappings and conversions in XI. The only thing you need to do in XI is to import the standard business content for SAP MDM 5.5 into XI.
Hope this helps.
Regards,
Jorge.

Regarding the Message Type and IDOCS related to IS-Banking

Hi Gurus,
can any one provide me the Message Type and IDOCs related to IS-Banking.
Regards.
Kiran kumar.

Hi,
Refer this link,
http://www.stylusstudio.com/edifact/d04b/BANSTA.htm
Hope it helps you.

Idoc for Material Change

Hi Experts,
The requirement is to receive a standard Idoc for material change and trigger the material creation process in case the material does not exist.
Secondly, what is the Idoc for material change?
Thanks and Regards,
Ravi

Hi,
Go through the following Steps for Creating IDoc Via ALE
ALE IDOC
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
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 : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
I know how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error.
hope this helps you.
plz reward if useful.
thanks,
dhanashri.

Provide me some IDOC related docs.

I want to learn IDoc. Can any boddy sent me material that guide me to create IDocs, and also clear concept related to idocs

Hi Dilip,
Just go through this and learn whatever you want....

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://help.sap.com/printdocu/core/Print46c/en/data/pdf/SDEDI/SDEDI.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
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

ALE/ IDOC/ XML
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
EDI
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.onestopsap.com/interview-Question/edi/
http://www.intelligententerprise.com/channels/applications/feature/archive/kasturi2.jhtml
http://www.sapgenie.com/sapgenie/docs/i830v3020.xls
http://help.sap.com/saphelp_46c/helpdata/en/0b/2a655d507d11d18ee90000e8366fc2/frameset.htm
http://www.hud.gov/offices/hsg/comp/edi/0306sec1.cfm
http://www.sapgenie.com/sapedi/index.htm
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.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b828943d711d1893e0000e8323c4f/frameset.htm
http://www.sapgenie.com/ale/whitepaper.htm
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 this IDoc online document:
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
Also check this links for additional information:
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
For IDOC Convertion:
/people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
For Idoc Processing:
http://www.sapgenie.com/sapedi/idoc_abap.htm
The procedure to start configuration, populating idoc and then sending is ....
1. Define Logical System and Assign Logical System
TCODE sale
2. Define RFC
TCODE sm59
3. Define Port
TCODE we21
4. Define Partner Profile
TCODE we20
5. Define Distribution Model
TCODE bd64
6. Send Data
TCODE bd10
7. Get Data
TCODE bd11
8. IDoc List
TCODE we02
Hope this will guide you to start working on it..
Regards,
Abhy
PN: Let us know if the information was helpful....
Message was edited by: Abhy Thomas

How to generate Outbound idoc for Material Reservation

Hi Experts,
I want to send outbound IDoc when a material reservation is created with tcode MB21.
I have been working on this issue and finding the solution in SCN for a week...
I found some messages similar to this but I could not find out the correct way how to do that.
At this moment, I configured BD64/WE20 referring the following topic which seems to be feasible solution but could not find any outbound IDocs created, unfortunately.
Implement ALE_RESERVATION_CREATE
I appreciate if someone can help me how to create outbound IDoc with MB21 or advice some possibility of missing configuration or steps.
Best Regards,
Kenji

Hi;
Have been able to find the solution to create the IDoc MRESCR after entering a reservation?
I am in the same situation and I do not see the IDoc output in the BD87.
It would be nice if you share the solution.
Thanks in advance

Idoc Related queries

1.     How can we view and rectify the errors or warnings caused ,while we create a new idoc ,which may be an extension of an existing basic Idoc type(at Transaction code we30)?
2.     How can we delete an Idoc created,if its already been released (at Transaction code we30) and configured(at transaction code we82)?
3.     Is that mandatory that the check box Mandatory field should always be checked,whenever we create(extend) a new segment to an existing segment(at transaction code we30)?
4.     On what basis,we can identify that To which existing segment - we can append our needed segment(new segment if any to be appended)?

Hi Nagarajan,
Answers for your questions:
1)How can we view and rectify the errors or warnings caused ,while we create a new idoc ,which may be an extension of an existing basic Idoc type(at Transaction code we30)?
   WE30 is created for IDOCs. First set break point related user exit.For testing WE19. Just enter that error IDOC number in WE19 and press F8. Then it will display the segments. Then press /H in the command box and press inbound function module push button (Just side of inbound push button). Then it will open in debug mode. we can test.
2. How can we delete an Idoc created,if its already been released (at Transaction code we30) and configured(at transaction code we82)?
Yes it is possible to delete hte IDOC which is released from our system, i think thorugh remote function but i am not sure.
3. Is that mandatory that the check box Mandatory field should always be checked,whenever we create(extend) a new segment to an existing segment(at transaction code we30)?
Based on the requirement we can select that check box. suppose it u upload the data for MM01 t-code then observe what are all the manditory feilds in that screen. Based on that choose mandotory check box for proper fields in the segment.(In MM01 suppose meterail number is manditory then while creating segment select that manditory chk box for MATNR)
4. On what basis,we can identify that To which existing segment - we can append our needed segment(new segment if any to be appended)?
Based on the basic IDOC type and given information from the user.
Hope this helps you, reply for queries,
Regards.
kumar.

IDoc related doubt .......Please see..

Hi all,
What is message in Idoc? Please tell in layman terms. Is it part of the data records? Please point me to related files or threads.
Thanks,
Charles.

Hi,
The Message type are mornally assign to SAP document type (IDOC). A message type represents a business function ( Purchase order data, Invoivce data etc). The technical structure of the message type is the IDoc type.
An IDoc type can be implemented for various "logical" messages; one message can also be assigned to different IDoc types (m:n relationship).
The message is defined by the values for message type (required), message code (optional) and message function (optional). These three fields belong to the key fields in the partner profiles, which are used, for example, to determine inbound processing. If the 'Message type' field is not maintained (e.g. in the case of a control record from Release 2.1, in which MESTYP did not exist), the IDoc Interface uses the value from STDMES (EDI message type).
Example
The message ORDERS (= message type) identifies purchase orders (outbound) and sales orders (inbound).
Check transaction WE81, for Message type in SAP.
Also, follow this link for more infomation related to IDOC processing
http://help.sap.com/saphelp_46c/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm
Check this lin for information about "Distribution Using Message Types".
http://help.sap.com/saphelp_46c/helpdata/en/78/2174a351ce11d189570000e829fbbd/frameset.htm
Let me know if you need any other information.
Regards,
RS

Idoc Related Material

Similar Messages

Maybe you are looking for