Reg : Sales order Inbound Idoc

Hi All,
The IDoc type is Inbound.
I am using a IDoc for updating the sales order line item details. when i am triggering the idoc, its creating a new line item apart of updating the existing line item.
The Basic type is ORDERS05.
Message Type is ORDCHG.
Please let me have your valuable points on this.
With Regards,
Sumodh.P

hi,
Adding and inserting an item is done via the same functionality with SAP
idoc_input_ordchg.
The item in the idoc is linked to the old sales order by the filed
POSEX.
To change an item you must provide the same posex in the idoc
as in the old sales order (vbap-posex).
If an item in the old sales order is found with the same posex
as the item in the idoc, the item will be changed.
If the item is not found in the old sales order because no item
in the old sales order has the same item POSEX in the idoc, the item
will be inserted.
The above rules are valide for both ACTION 001 and 002.
kind regards
Paul Quinn

Similar Messages

Confirm sales order with idoc ORDERS05

Hi everybody.
I´d like to know if it´s possible to confirm a sales orders with idoc ORDERS05 and message type ORDCHG and posting FM IDOC_INPUT_ORDCHG_VMI.
How would I have to fill the idoc data??
Thanks a lot

Hi,
For inbound idoc you can use the message Orders , process code ORDE and the function mdoule IDOC_INPUT_ORDERS to create a sales order.
Regards,
Nagaraj

How to populate the billing plan tab for the sales order inbound

Hi Team,
I am new to IDOCS, I have a requirement like IDOC extension of the sales order inbound.
Can anyone explain in brief how can i add billing plan tab in the IDOC extension for the Sales order inbound.
Thanks,
Barathi

U need to use the table vbfa or fololow thw link
[http://www.erpgenie.com/sap-functional/sd/read-sales-document-flow-using-a-function-module]

Problem when setting Reason of Rejection for a sales order using IDOC

Hi All,
I am working on a requirement where i need to put a reason for rejection as 'Item Cancelled' for a sales order via IDOC 'IDOC_INPUT_ORDCHG' in a third party scenerio where the PR is created automatically from the sales order . When the IDOC is run in the foreground I get the information message Subsequent function " 'Purchase requisition from sales document' not possible Item & was rejected "(Message V1579) and the IDOC results in a error when run in the background mode because of the same information message. The message should not appear when a sales order is being processed in the background but still the message is being displayed . Is there any way the message can be suppressed ? Thanks in Advance.
Regards,
Sowmya.

can you send the program how you create a so or po using IDOC, as i've a assignment creating PO using IDOC & then creating a sales order of the PO. and i dont know how to create a IDOC. SO IF you have sample program it would be help full
Thanxs

Creation of sales order via IDoc ORDERS05 - specify a reason of rejectio

Hi,
I want to create a sales order via IDoc (type:ORDERS05), i specify for an E1EDP01 segment a reason of rejection (ABGRU),
The sales order is created succefully by calling the FM IDOC_INPUT_ORDERS but the order quantity of the item where i have specified a reason of rejection is equals to 0.
Is this normal? i want that this will take 3 value either 0?
Could anyone help me?
Thx

Hi,
Thank you for ur answer.
I've followed the procedure that you have explained and the Quantity 3 have been succefully passed to VA01 but is set to zero when i execute the next OK-CODE (=UER2, i think it is llike Enter button ). I simulate the same procedure by creating a sales order on VA01 and i've finally found the problem : at item level, if i enter the Material (MATNR), the order Quantity (KWMENG) and the Reason of rejection (ABGRU), the quantity is set to zero after clicking the enter button ; but if i enter only The material and The quantity followed by enter button, and enter after the Reason of rejection, it works fine, the Quantity doesn't change.
What is the solution that you propose to me?
I've try this one on debugger mode:
The FM which interpret the Idoc create the sales order by CALLING TRANSACTION 'VA01' USING bdcdata....
I've modified the bdcdata to implement the sequence of the steps before (MATNR + QTY <ENTER> ABGRU <ENTER>).
1. Is it possible to code this modification?
2. Is there a way to structure the Idoc for having this sequence in bdcdata?
Thanks in advance!
Narivelo

Creating sales order using IDOC - Delivery hour

Hi,
i've a problem to solve. when creating a sales order i need that when the segment is E1EDK03 and the IDDAT is 002 i need to extract the delivery hour and insert it in the table vbak-vzeit, now what i'm doing in the exit EXIT_SAPLVEDA_001 is:
DATA: hour LIKE vbak-vzeit.
CHECK segment-segnam = 'E1EDK03'.
IF segment-sdata(3) = '002'.
hour = segment-sdata+11(6).
ENDIF.
and now i want to acess the value in hour in the exit EXIT_SAPLVEDA_002 to put it in the dxvbak struct tha i think that is the table correct to then internaly fill the vbak. the problem is that the variable hour is not available in the exit EXIT_SAPLVEDA_002. i do i do to pass the value that i want from the exit EXIT_SAPLVEDA_001 to be available in exit EXIT_SAPLVEDA_002 and then insert that value in the right place to fill vbak.

Can u tell me the steps to create a sales order using idoc, i've created a bapi but thats a temprory use. I wanted to created a sales order automatically when a purchase order is saved.
Please let me know if u can help me, i wanted to do it using idoc
Regards
Sanju

ERROR IN CREATING SALES ORDER,USING IDOC TYPE ORDERS05

I am using exit to write my code for creating sales order of IDOC Type ORDERS05 and order type ZDRX.
IF I proceess the Idoc in background each time error message comes
FIELD kuwev-kunnr(ship to party)is not an input field.
but if i run in foreground in debugging mode,sales order is getting created..
please suggest something.

If thats not working..
try BAPI_SALESORDER_CREATEFROMDAT2
If BAPI is not working. try creating a bdc for the same if there's not error on trying from VA01

Sales Order Using Idoc

Hello All,
We are creating Sales Order through Idocs : Basic Type - ORDERS05 Message Type - ORDERS
Sales Order is being created but for few Items , Reason for Rejection is set (thts not required in our case).
I am trying to figure out why for some items its happening ?
I tried to check the reason by Processing the Idoc in WE19 but could get through.
Also tried to process the Idoc using FM IDOC_INPUT_ORDERS in Debugging but not able to process further as getting error message : 'Idoc Has Different Status'.
Any input on this would be helpful.
Thanks
Praveen

This problem due to your config in the system, try to create a sales order for the item that posted via Idoc then see same item got rejected.. If yes discuss wtih your funtional guys....

Sales Order Outbound IDOC - Restricting Items being created with a Segment

Hi,
I have a requirement to restrict segments being created for Items (Child) in Sales Order Outbound IDOC based on conditions in the Items (Parent & Child). Can you please suggest me a suitable solution?
Basic Type: ORDERS05, Message Type: ORDRSP. What is the IDOC Function Module to be used to create Outbound IDOC for Sales Order?
Appreciate Your Help.
Thanks,
Kannan
Edited by: Kannan SA on Jan 3, 2008 3:03 PM

Hi,
if the segments are mandatory then you can't trigger the idoc without those segments.
Otherwise, you can read the segment and clear all the data in it, the segment will not be attached to the outbound idoc.
Where to do it? Search the CALL CUSTOMER-FUNCTION '002' for the outbound idoc for example IDOC_OUTPUT_INVOICE for Invocing.
Regards,
Baburaj

Problem creating sales order using IDoc ORDERS05 (Inbound)

Hello Experts,
We are trying to create a sales order using the IDoc ORDERS05 with process code ORDE for creating sales order. I am getting the following error "VKORG, VTWEG, SPART cannot be determined for customer 0000006000 , vendor
Diagnosis
No sales organization, distribution channel or division were sent to the IDOC. This data is necessary if a sales order is to be added automatically. If this data is unavailable, you cannot create a sales order document.
I was not able to find the fields to fill the distribution channel and divison in the Idoc structure. I have filled in Sales organization in E1EDK14 segment as 3000.
I am not able to figure out the cause for the error.
Same data works fine from BAPI_SALESORDER_CREATEFROMDAT2.
Please help.
Thanks,
Suma
Edited by: Suma B on Jun 17, 2008 11:12 AM

Hello Suma
In this case I would recommend to debug the IDoc processing.
Call transaction WE19 and start the inbound processing of your IDoc in debugging mode. The error message will most likely occur in function module IDOC_INPUT_ORDERS.
LOOP AT idoc_contrl.
* SET/GET Parameter und interne Tabellen neu initialisieren
* initialize SET/GET Parameter and internal tables
    PERFORM initialize_organizational_data.
* IDOC-Segmente in die entsprechenden Anwendungsdaten übernehmen
* Move IDOC to internal tables
    PERFORM interpret_idoc_orders.                    "<= check here
* Prüfen ob gewisse Segmente gefüllt sind
* check IDOC-Segments
    PERFORM check_idoc_segments.                 "<= check here
* Prüfen und Ermitteln von Organisationsdaten
* check internal tables and determine organization data
Regards
Uwe

Dates fields issue in the sales orders through IDOC

Hi all,
I'm trying to create a sales order through Inbound IDOC using IDOC_INPUT_ORDERS.
I have 2 custom fields in the sales order which are date fields.
I'm populating them from the IDOC segments(using E1EDKT1-tdid, E1EDKT2-tdline) in the user-exit just before the call trasacation statement. These dates are not coming for a few orders... but are getting populated normally for few of them.
But the tricky part is that... if I process the same IDOC for the second time.. the order created is having the dates.
My issue is that.. i need all the orders to be populated with the dates which IDOC have.
Could anyone please help me with this issue.
All the answers/replies are highly appreciated!!
Thanks for you help!

hi,
the following may be of help
There are 2 major exceptions to the batch input internal table. All text data from the segments E1EDKT1/2 and E1EDPT1/2 are not part of the batch input session. Text elements from these segments are posted directly to the data base AFTER the sales order has been created (please note: in order that item texts are posted correctly to the sales order the field POSEX from segment E1EDP01 MUST be transmitted). Also, configurable material information from the IDOC is exported to a global memory and therefore will not be part of the batch input session. Configurable material data is performed in Form CHECK_CONFIGURATION and the data is exported to global memory in the following code:
Exportiert IDOC Daten ins globale Memory
export IDOC data to global memory
call function 'CUXC_IDOC_TO_MEMORY'
       tables
            cfg_instref = xe1curef
            cfg_ref     = xe1cucfg
            inst        = xe1cuins
            part_of     = xe1cuprt
            value       = xe1cuval
       exceptions
            error       = 1
            others      = 2.
One extra piece of useful infomartion if you wish to debug the process is to set your breakpoints at the following points
for Function module IDOC_INPUT_ORDERS
include LVEDAF0F..
CALL TRANSACTION 'VA01' USING bdcdata
                            MODE input_method
                            UPDATE 'S'
                            MESSAGES INTO xbdcmsgcoll.
Now input_method is A foreground process and N for background processing but try changing it to P (pass through mode)
If you have breakpoints in va01, e.g. MV45AF0B_BELEG_SICHERN,(the part where the sales document is saved)
they will be hit, e.g
perform userexit_save_document_prepare.
perform userexit_save_document.
Lastly, don't forget using program SDJEDI , see note 380603 for more information on this
Hope this is useful
Paul Quinn

Replicate Sales Order using IDOC

Hi All,
I want to ask whether all of you have already implemented IDOC for replicating sales order (under same client)
I've already set up partner profile (WE20) as follow:
Partner Type : KU (Customer) --> Outbound
     Message Type: ORDRSP
     Basic Type     : ORDERS05
     Output Type    : BA00
     Process Code : SD10
Partner Type : LS (Logical System) --> Inbound
     Message Type :ORDRSP
     Process Code : ORDE
after creating sales order, IDOC has been successfully produced (outbound), but an error always occurs for inbound IDOC.
Function module not allowed: IDOC_INPUT_ORDERS
Diagnosis
The function module IDOC_INPUT_ORDERS and the application object type BUS2032 which were determined are not valid for this IDoc.
Have you all ever experience this?
Kindly need your advise/help
Thanks
Hendry T

any suggestion from all of you?
Thanks

Create Sales Order using IDoc

Hi All,
Based upon customer's input file which contains header and line item details I have to create sales order in our system. We would like to use IDoc for this. Customer will send us file once a day by email or FTP.
For this I have created a port and partner profile but I am not sure how the process will get initiated?
Can someone please let me know how can I do this? There is now outbound process involved, I just need to create sales order based upon input file using IDoc.
Regards,
Sanjay

HI,
You cannot directly call the function modules that process the idoc, because these functions are called dynamically by the ALE layer and the function expects data in a certian format (IDoc format ).
BAPI would be the best way to go for your scenario.
However there is a workaround if you want to use IDoc only. You can follow this approach :
1. Populate an outbound ORDERS05 IDoc from the file data.
2. Distribute it to the same system, i.e sender system and receiver system is same.
3. On the Inbound side the Idoc that you created on the outbound side will be received and processed.
"R3 File----->Outound ORDRES05 -----
______________________________________|
|
'------> " Inbound ORDERS05 ( in the same R3 system)
The tricky part is sending an Idoc and receiving in the same system, but you can find how to do this on the wiki pages.
regards,
Advait

Sales Order BOM IDoc Steps

Hi all,
I am new to IDoc and got a requirement where I want to mass update the Sales Order BOM in SAP. I have to use the IDOC type BOMORD01, message type BOMORD with the inbound function module IDOC_INPUT_BOMORD in order to mass create Sales Order BOM. I have been provided input file with following fields:
Order Number
Item Number
Material
BOM Usage
Item Category
Components
Quantity
Indicator (Create/Delete)
Could you please tell me the steps-by-step approach with TCODES?
Thanks in advance.
Regards,
Balaji Viswanath.

Hi
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/
Regards
Anji

Open Sales orders through IDOC

Hi
We are trying to send the list of open sales orders of a customer in an IDOC to the customer. For example, if the customer has got 15 sales order to be delivered to him , he needs the details of all these 15 orders in an single IDOC
Is there any IDOC message type available for this in SAP R/3 4.7 version or is there a standard solution of sending these details through IDOC
Regards
Anandh

Hi
We are trying to send the list of open sales orders of a customer in an IDOC to the customer. For example, if the customer has got 15 sales order to be delivered to him , he needs the details of all these 15 orders in an single IDOC
Is there any IDOC message type available for this in SAP R/3 4.7 version or is there a standard solution of sending these details through IDOC
Regards
Anandh

Reg : Sales order Inbound Idoc

Similar Messages

Maybe you are looking for