Idoc for sending Purchase Requsitions

Hi
We have a distributed enviroment where we want to transfer purchase requsitions from one SAP client (local) to a central system. But I can't find any interfaces or anything to trigger souch a transfer.
Have anyone a idea on how we can solve this?
Best Regard,
Morten Gummedal

Hello,
I think u can use the type PREQCR01 for sending the PR.
If useful reward.
Vasanth

Similar Messages

Message type for generating IDOC for SUBCONTRACTING PURCHASE ORDER

Hi All,
I have to generate IDOC for PO creation or change .
I am using IDOC_OUTPUT_ORDERS and IDOC_OUTPUT_ORDCHG.
The messagetype.idoctype I am using is ORDERS. ORDERS05 and ORDCHG. ORDERS05.
Now the confusion is regarding whether this message type will work in case of SUBCONTRACTING PURCHASE ORDER as well ?
As I have gone through some websites and came to know that I will have to use PORDCR1.PORDCR102 specially for subcontracting.
And programs we need to use is BUS2012_ICH_R3 instead of RSNASTED and Form Routine SEND_PORDCR1 instead of EDI_PROCESSING.
Purchase Order Collaboration scenario - Not generating IDOC in ECC
http://www.erpgenie.com/faq/edi_purchasing.htm on this site question no 8.
Subcontract PO IDOCs
I hope your experience will help me .
Please reply ASAP.
Edited by: uttam27 on Dec 4, 2011 1:47 PM

There is a generic function to create change pointers for all message typs - 'CHANGE_POINTERS_CREATE_DIRECT'. This is triggered only if you configure your message type to create change pointers from BD50.
Once you activate it do any change to orders you can see change pointer tables BDCPV filled. Then BD21 will read the changes and generated outbound idocs accordingly.

IDOC for sending material including classification data?

Hi everyone,
I'm just looking for an IDOC to send to an external system all data of certain materials but including classification system data, variant configuration data...
I have checked MATMAS0x but I am not sure if those IDOCs match with my requirement.
I would be very grateful if someone could please help me.
Thanks in advance and best regards,
Ben

Hi,
CLFMAS01     Master object classification
CLFMAS02     Master object classification
STTMAT01     STTMAT: Material variants
BOMMAT01     Master BOM - material
BOMMAT02     Master BOM - material (2)
BOMMAT03     Material BOM (from 4.6B)
BOMMAT04     Material BOM with UPS Link
MATMAS01     Material Master
MATMAS02     Material Master
MATMAS03     Material Master
MATMAS04     Material Master
MATMAS0x with CLFMAS0x should solve your problem.
Regards,
Srilatha.

IDOC for sending material data including classification data?

Hi everyone,
I'm just looking for an IDOC to send to an external system all data of certain materials but including classification system data, variant configuration data...
I have checked MATMAS0x but I am not sure if those IDOCs match with my requirement.
I would be very grateful if someone could please help me.
Thanks in advance and best regards,
Ben

Hi Ben
Kindly follows the below steps and trasaction screens, I believe you will be able to send the mat data incl. classification data to other external system through IDOC.
Steps:
Create material master record in SAP
Enter T.Code BD10 to send material master data from SAP to 3rd Party Logistics Provider
Enter Material,Logical System and click Execute(F8)
Press ENTER to continue
Press ENTER to continue
Enter T.Code WE09 to check the status and content of the Idoc created
Enter Idoc Segment name in Search in Segment, Field name in Search in Field, Material No in "for Value" and press F8 to execute
Double click on the Idoc number to check the content and status of the Idoc
Expand the Status records to check the STATUS of the Idoc
To check the fields in the Idoc, expand Data records and check the Mandatory fields in each Segment
Transaction Screens:
Transaction / Screen
MM01
BD10
BD10 Screen
BD10 Screen
BD10 Screen
WE09
WE09 Screen
WE09 Screen
WE09 Screen
WE09 Screen
Expected Result:
Expected Result
Material Master Record Created
Send Material Screen appears
A popup window appears with a message "1 master Idoc(s) set up for message type MATMAS"
A popup window appears with a message "1 Communication Idoc(s) generated for message type MATMAS"
Send Material Screen appears
Idoc Search for Business Content screen appears
Idoc corresponding to the material no is displayed
Idoc along with the 3 records(Control Record,Data Record,Status Record) appers
Final STATUS should be 03(Data passed to port OK)
All Mandatory fields must be populated with correct data
If it is useful reward points
Thanks
Saravana

EDI IDOC OUTBOUND send Purchase Orders from sap to vendors

Hi Experts,
I am new to EDI IDOCS, but i got object on this. So my requirement is purchase orders are send to vendors from sap (OUTBOUND) through EDI-850 format. and also i have to add some more fields to standard idoc type ORDERS05, one more condition is if vendor type is not EDI, then the POs should send through fax, email, how can we solve this condition.
So plaese send some sample code on this object.
Thanks in advance,
S Reddy

Hi ,
You can send the purchase order to the vendors using different outytpes configurations in NACE transaction .
If you define a particular output type where you need to give medium 6 and define partner functions within this you can also set condition which partner needs to recieve EDI output and which one FAX or email all this will be done by Functional expert.
For adding extra segments to your basic type ORDERS05 you need to extend the idoc you can do it via WE30 and WE31 .Link you message type to basic type and extension . Please follow below tcodes for further help . Create all the requested steps in the tcodes mentioned below.
we20:patner profile
we21:port
we30:idoc creation
we30:segment creation
we81:message type
we82:link message with idoc type.
we02:to status of idocs.
Now you need to write code for filling those extra segments you have added to you extension type. For that you need to check where your new segment is placed in Idoc structure . There will be a exit avaliable to attach your code to fill those segments .
Please go through previous SDN links to see more info.
One the settings are done in the NACE , issue output from PO transction and once your output is processed check your Idoc in WE02 to see if the segments are coming with the desired data.
Regards
Vikas

Issue with Idoc for creating purchasing contracts

Hello everyone,
I'm trying to create purchasing contracts using Idoc BLAORD3 through LSMW.
But i have a problem : all informations concerning account assignement are missing on this Idoc.
Does anyone know how to solve this problem? Maybe is there a BAPI which could replace my Idoc? Or is there another Idoc which could create account assignement seperatly?
Thanks in advance for your help.
Cédric

Hi,
Try using E1EDK18 segment. Put "Number of days" ,Qualifier and check if this achievs the desired result or not? If yes then you have to use an user exit to put the number of days in the IDOC.
Cheers,

Sending purchase order by email to vendor

hi
what conf steps required for sending purchase order by email to vendor and internal users?
rgds
sara

In Vendor Master mention the email id of the vendor and in PO in Item detail tab in delivery address maintain the email id for the respective internal user.
Also configure message determination schema for the PO.
Regards
Ankur

IDoc For Sales Document

Hi All,
I have a requirement to create IDOC for sales order that should have all data related to SO document flow (History). Using output determination, I am able to create IDOC but the history is not populated in the IDOC.
I did not see any message type for SO history, Is it possible to create an IDOC for sending sales order history.
Thanks in advance/

Yes, you could create a absolutely new IDOC type for the SO history or using a custmized IDOC which only added some new field into the current IDOC type.
If the structure you need is very different with the current exist IDOC type, you can choose to create a former solution.
Import a new type IDOC, you need to do the structure defination for it, and create a process function and process code to the system which receive it and handle it. And of course, you need to fill the IDOC and send it by yourself in ABAP code, using e.g. FM MASTER_IDOC_DISTRIBUTE.
Hope it will be helpful

How to Send Purchase Order through EDI/IDOC.

Hi Experts,
We are using SAP ECC.5. And intending to send the Purchase Order to Supplier through EDI/IDOC and Receive the Inbound Acknowledgement.
Appreciate, if you could help me, the required Configuration details for outbound and inbound (PO & Acknowledgement).
Reg
Kumar

Hi Kiran
Many thanks for the response. It is true that by changing the message type to EDI can generate idoc. What is not clear is any other config we need to do interms of Message generation, Resubmitting failed IDOC etc..
Out requirement is that we would generate the IDOC for New and changed docs and send to external EDI converter.
Inbound, receive the IDoc and post the acknowledgement.
Appreciate, if you could forward any document link which can explain the details.
Reg
Kumar

Send Purchase Order via ALE/IDOCS

hi,
How can i send one PO from one client to another via ALE/IDOCS?
Pls provide few important steps.
Thanks and Regards,
Gaurav

For sending IDOC for Purchase order you will use idoc
Message type : ORDERS
Basic Type : ORDERS05
Create one RFC Destination in SM59 and give that entry in Port in WE21.
Create Partner profile in WE20 and Port for receiver system in WE21.
Use your port in Partner profile in WE20.
In Partner Profile create one entry for Message type ORDERS as Outbound.
In your tcode when you are creating Purchase order set output message in your header condition for Outbound to send that purchase order to that Partner Profile.
Check link :
http://www.****************/Tutorials/ALE/AutoIDOCGen/AutomaticIDocGeneration1.htm
Regards,
Sandeep Kaushik

Creating an IDOC for purchase order

Hello gurus,
I want to generate an IDOC for purchase order.
The Logical System, RFC connection, ports definition is already defined.
In my system i have 800 client as source/sender and 100 client as target/reciever.
On Outbound side-> In Partner profile
I defined-
1. Partner No.- devclnt100
2.Type- US (User)
3. Agent - SAPUSER
In Outbound parameters-
I created message type as Orders.
One thing to note that my partner system is LS i.e. Logical System
Then in Outbound Options-
I mentioned Reciver Port - 800Port
Output Mode- I selected "Transfer Idocs immediately"
& "Do not start subsystem"
In Idoc type-
I gave following information-
Basic Type - Orders05
In Message Control tab i mentioned-
Application - EF
Message Type - NEU
Process Code - ME10
In NACE Transaction Code-
I selected EF Purchase Order as my condition for output control
In that- In output types-
I selecte NEU and double clicked. I checked whether Access to Conditions check box is checked and multiple issuing is checked.
In Dialog structure-Processing routines I checked that -
For Output type - NEU
Application - EF
Processing routines are defined-
medium-Distribution ALE
Program -RSNASTED
Form Routine - ALE_PROCESSING
I think these are the very basic settings that need to be done for creation of Idoc.
Now when i create a PO and then SAVE it an IDOC must be generated.
But when i go to transaction Code WE02. It shows me message "No Idocs genereated".
What is the problem? Where am i going wrong?

Hi Yayati,
Here are all the settings that you need to do. I am not sure which all settings are present so kindly confirm.
Sending side Client800:
1. WE20 - under LS - Outbound parameters - message type = Orders , basic type = Orders05
2. BD64 - message type - sender = client800, receiver = client100, message type = Orders
3. NACE - App = EF - Output Types - Processing Routines - Add medium = A (Distribution (ALE)) , Program = RSNASTED, Routine = ALE_PROCESSING.
4. NACE - App = EF - Output Types - Partner Functions - Add medium = Distribution (ALE), Funct = VN.
5. Name - App = EF - Condition Records - Output type = NEU , Choose ur combination (Mine is DocType/Purc Grp)
Pur.Doc Type = NB (Execute) , Add row Medium = A ,Function = VN and other details u choose.
Receiving side Client100:
1. WE20 - under LS - Inbound parameters - message type : Orders ; Process Code : ORDE
2. BD64 - message type - sender = client800, receiver = client100, message type = Orders
For the PO which you have created, go to the PO in ME23N, click on messages .
There should be a line : Output = NEU, Medium = Distribution (ALE)... etc.
If its present then the configuration was correct.
If it has a yellow triangle means it was not processed.
Regards,
Jovito.
Edited by: dsouzajovito on Dec 30, 2010 10:24 AM

Sending Purchasing record to external system by Idoc

Hi,
We need to send Purchasing Info Records to external system via idocs when a Purchasing info record is created or changed.
Please let me know how can we do this.

Check with your technical team message type INFREC for Purchasing info record.Create one custom program and this should check the inforecord new ones and changed ones then it should trigger idocs in background then it sent to external system.To do this automatically setup custom program batchjob.

Sending Purchase order outbound thro IDoc

We have a scenario to send Purchase order in Idoc format.
I have created a Distribution model, Partner profile and change pointer for msg type ORDERS and Global change pointer are activated.
When I execute the program RBDMIDOC for msg type ORDERS, I am getting an error message as
" Message type ORDERS cannot be sent with change pointers
Message no. B1157"
All ur ideas will be appreciated.
Thanks,
Sivaraman

hi
it is not possible to send transactional data by using change pointers
it is for only for sending master data .
Thanks&Regards
Nagesh.Paruchuri

Send Idoc For Purchse Order

Hi Friends,
I have Configure All the things require to send idoc for purchse order..........when i m creating purchase order from source system
it's getting send to traget system....................
but in target system giving error in idoc.that
VKORG, VTWEG, SPART cannot be determined for customer S004 , vendor 0006000023
i m using message type....ORDERS............
can antbody pls tell me how to maintain VKORG, VTWEG, SPART
in oreders message type.......there no fields in this message type.......i have checked it through se19...............

Hi ,
I have same problem ,
How to send IDOC of Purchase Order to URL of our vendor.
The Idoc is created , but how to send it to the web?
Anyone knows?
Thanks
Edited by: Moshe Stein on Feb 28, 2008 11:08 AM

Idocs for Purchase RFQ

Hi Friends,
Does anybody knows how to configure, an Outbound Idoc to non SAP application for Purchase Request For Quotation? And after inbound a similar Idocr for update Quotation into SAP using estandar Idocs messages?
Thanks for your help,
Andres.

Hi
Check these links for Idoc
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
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.
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/
<b>Reward points for useful Answers</b>
Regards
Anji

Idoc for sending Purchase Requsitions

Similar Messages

Maybe you are looking for