What is the filed in ORDRSP idoc to stop changes in PO?

Hi,
SO gets created from PO and when ORDRSP idoc comes from SO to PO, there should be filed in the IDoc that will not allow to change PO anymore when ORDRSP is received to PO. Could anyone let me know the filed in IDoc and where in that will be in the ORDRSP idoc to stop the PO from being changed. appreciate your help. Thank you!

i think you should use the BADI ME_PROCESS_PO_CUST to check if there is an entry in table EKES. If yes, the Method FILDSELECTION_HEADER or FIELDSELECTION_ITEM have to be used to set the the whole PO to 'display only'
Edited by: Gabor Harsfalvi on Aug 4, 2010 4:40 PM

Similar Messages

What is the need of ALE/ IDOC

Hi All,
What is the need of ALE/ IDoc and why we go for ALE?IDOC with conditions
Let me know the answers if anyone have the solution
Regards'
Ramesh

ALE (Application Linking and Enabling)
Ale Technology is SAPs technology to support distributed yet integrated processes across several SAP systems.
IDocs (Intermediate Documents) are the crux of ALE. These are the documents with the help of which data is exchanged between SAP R/3 and non-R/3 systems. As the name suggests, these documents act as intermediate storage of information, which can be sent bi-directionally. Message types are responsible for creation of Idocs.
IDocs
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
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,

What are the ways to handle Idocs which are failed to post to R/3

Hi Experts
What are the ways to handle Idocs which are failed to post to R/3 after sucessfully configuration of the Scenario.
Thanks & Regards
Aravind

Hi
Check the Idoc Status in R/3 with WE05.
Idocs will fail in following conditions
1) Idoc will be in error if all the mandatory field are not mapped.
2) If partner profile is not maintained.
3) Most of the times, idocs will be in error due to functional issues.....check the status and take help from functional guys.
Once the error resolved, reprocess the same idoc using BD87
Regards
Abhijit
Edited by: Abhijit Bolakhe on Mar 18, 2010 3:11 PM

Hi Friends what are the actual differences between AT NEW & ON CHANGE

what are the actual differences between AT NEW & ON CHANGE ? can you list some of the differences?

Hi,
At New
1. When a new record comes at new triggers. Atnew only used inside loop and endloop.
2. At new is controlbreak statment on at new the left side field change, the event
trigers and the values become 0 and *
On Change
1. On change of works same like at-new but the diff is it can be used out side of a loop,like select and endselect,case endcase.
2.. on change of is not a control break statement and we can use onchange of out side the loop
and
The Major difference between the two is that AT NEW can be used ONLY for INTERNAL TABLES, while ON CHANGE OF can be used for any loop processing i.e do..enddo, while..endwhile and loop..endloop also.
AT NEW <field>
The block will be executed when the SY-TABIX is 1 (or) when the SY-TABIX 1 value has a change with the SY-TABIX value.
With this block the field towards the right to the field are not accessable with in the block, and are shown with '*'. They can be accessed outside the block.
ON CHANGE OF <itab>-<field>
The block also works similar to the AT First. In this block all the fields are accesseble.
ON CHANGE OF triggers whenever there is a change in that particular field.
AT NEW triggers whenever there is a change in the fields before that particular field.ie. if there is a change in that combinations from the first field.
On change off' works on variabels. The 1st time the statement isreached a memory copy is made of the value. The next time the statementis reached, the current value is compared to the stored value. If thereis a difference, the coding between ON... and ENDON. is executed. Youcan use this for a table workarea field, but if you have the table loopin a routine and the routine called several times, you can get unwantedresults. (Check the value of the last loop with the value of the firstnew loop.)
The AT NEW (and others like AT END OF...) are specially for table loopprocessing. The coding between AT new FIELD and ANDAT is triggerdwhenever a the field or any field defined to the left is changed. Yourtable should be sorted by all fields from the left up to the consideredFIELD. Btw all fields to the right contain *, so it can be usefull tohave a second workarea filled to be printed or what ever you want.
REWARD IF HELPFUL
RAAM

As a abap programmer what is the role in ale/idoc.

hi guru.
i am a abap programmer. please tell me<b> what is the role of abap programmer
in ale/ idoc.</b>
regards.
subhasis.

Hi,
ALE is Application Link Enabling.
ALE
A means of creating and operating distributed applications.
Application Link Enabling (ALE) guarantees a distributed, but integrated, R/3 installation. This involves business-controlled message exchange using consistent data across loosely linked SAP applications.
Applications are integrated using synchronous and asynchronous communication - not by using a central database.
ALE consists of the following layers:
Application services
Distribution services
Communication services
Refer
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
Check this link ALE and EDI
ABAP Programmer must know how to create inbound n outbound interfaces to send IDOCs through ALE.
Please refer to the details mentioned in the hyper-links beow.
You will get the details how to go about it.
To see the IDOC & status check it in WE02/WE05
You will get step by step process.
ABAP Development
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.geocities.com/xplosion78/customised_ALE_IDOC_BY_SACHIN_DABHADE.zip
http://help.sap.com/saphelp_45b/helpdata/en/35/b0ea5187a62488e10000009b38f9b7/content.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/c4/6bc368fef411d28d0900104b56737d/frameset.htm
ABAP Development
Follow below steps to create custom IDOC.
1.Create segments through transaction WE31.
2.Create IDoc Type through transaction WE30 by attaching created segments.
3.Message type through transaction WE81.
4.Link Idoc and message type in WE82 transaction.
Check the transaction WEDI for ALE settings
Check these links for more details on IDoc's:
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
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
IDOC Convertion
/people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
http://www.intelligententerprise.com/channels/applications/feature/archive/kasturi.jhtml
Hope this will help.
Regards,
Priyanka.

What is the internal processing for idocs

Dear friends this is subbu working as a abap consultant.
can any body explain the how idocs are transfered (inbound process and outbound process)

1.Here out bound means sender.Inbound mens --receiver.
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.
There are two filtering in IDoc.
Segment Filtering:
Segment filtering can be achieved using T/Code BD56. Here you can suppress a whole segment irrespective of data inside it . You have to give Message Type / Sender Prrtner / Receiver Partner.
Data Filtering:
Data filtering can be done in dustribution model (BD64) where you can restrict whole IDOCS or partials IDOCS to be send based on data in fields inside IDOC depending on whether the segment in which you filter is at the highest level or at a lower level. For example in MATMAS if you put a filter of E1MARCM for a particular plant , only data for this plant will go and other plants will be ignored.
Please check this link for more information.
http://help.sap.com//saphelp_470/helpdata/EN/0b/2a611c507d11d18ee90000e8366fc2/frameset.htm
Reward points..

Create ORDRSP Idoc on creation, change or deletion of outbound delivery

We have ORDRSP Idocs being created when a sales order is created or modified. Now our customer would like an ORDRSP Idoc sent to them when the outbound delivery is created for the sales order. The reason that the customer would like an additional ORDRSP sent is because the time between the entry of the sales order and the creation of the outbound delivery may be a few weeks or more and the actual delivery may not be able to satisfy the quantity ordered. The customer is not set up to allow partial deliveries.
The customer uses the ORDRSP to feed into their billing system and would like updated quantities at delivery time. They do not want an ASN record.
Does anyone have any ideas or suggestions on how to trigger the ORDRSP Idoc when the delivery is created, modified or deleted? We are on SAP release ECC 6.0
Thanks for any help,
Russell

Vinit and Abhishek,
Thanks for your replies and information. Sorry I was not clear in my question. The ORDRSP Idoc is already being created when the order is created or changed. ORDRSP works fine. The partner profile is set up, NACE is already configured for ORDRSP, change pointer is working properly, output determination is configured and working, the ORDRSP Idoc is being created.
What I would additionally like to do is trigger the creation of an ORDRSP Idoc when the delivery for the order is created or modified. I suspect this will require using a user exit in the delivery program to trigger the ORDRSP Idoc and not standard SAP configuration. This is what I would like help on (trigger the creation of an ORDRSP Idoc when the delivery for the order is created or modified).
Also this site is a small shop. I am the ABAP programmer, the functional consultant and the EDI consultant for all SAP modules. There is no one else on the team here other than one person that does transports and security for SAP.
Thanks,
Russell

What is the best methodology to handle database schema changes after an application has been deployed?

Hi,
VS2013, SQL Server 2012 Express LocalDB, EF 6.0, VB, desktop application with an end user database
What is a reliable method to follow when there is a schema change for an end user database used by a deployed application? In other words, each end user has their own private data, but the database needs to be expanded for additional features, etc.
I list here the steps it seems I must consider. If I've missed any, please also inform:
(1) From the first time the application is installed, it should have already moved all downloaded database files to a separate known location, most likely some sub-folder in <user>\App Data.
(2) When there's a schema change, the new database file(s) must also be moved into the location in item (1) above.
(3) The application must check to see if the new database file(s) have been loaded, and if not, transfer the data from the old database file(s) to the new database file(s).
(4) Then the application can operate using the new schema.
This may seem basic, but for those of us who haven't done it, it seems pretty complicated. Item (3) seems to be the operative issue for database schema changes. Existing user data needs to be preserved, but using the new schema. I'd like
to understand the various ways it can be done, if there are specific tools created to handle this process, and which method is considered best practice.
(1) Should we handle the transfer in a 'one-time use' application method, i.e. do it in application code.
(2) Should we handle the transfer using some type of 'one-time use' SQL query. If this is the best way, can you provide some guidance if there are different alternatives for how to perform this in SQL, and where to learn/see examples?
(3) Some other method?
Thanks.
Best Regards,
Alan

Hi Uri,
Thank you kindly for your response. Also thanks to Kalman Toth for showing the right forum for such questions.
To clarify the scenario, I did not mean to imply the end user 'owns' the schema. I was trying to communicate that in my scenario, an end user will have loaded their own private data into the database file originally delivered with the application.
If the schema needs to be updated for new application features, the end user's data will of course need to be preserved during the application upgrade if that upgrade includes a database schema change.
Although I listed step 3 as transferring the data, I should have made more clear I was trying to express my limited understanding of how this process "might work", since at the present time I am not an expert with this. I suspected my thinking
is limited and someone would correct me.
This is basically the reason for my post; I am hoping an expert can point me to what I need to learn about to handle database schema changes when application upgrades are deployed. For example, if an SQL script needs to be created and deployed
then I need to learn how to do that. What's the best practice, or most reliable/efficient way to make sure the end user's database is changed to the new schema after the upgraded application is deployed? Correct me if I'm wrong on this,
but updating the end user database will have to be handled totally within the deployment tool or the upgraded application when it first starts up.
If it makes a difference, I'll be deploying application upgrades initially using Click Once from Visual Studio, and eventually I may also use Windows Installer or Wix.
Again, thanks for your help.
Best Regards,
Alan

Changing filed name description - idoc segment creation/change

HI,
is it possible to change the fieldname description in an IDoc Segment without changing the DataElement ?
Exampel:
I Used CHAR40 as dataelement for my own ZZFIELD. In the Idoc the fieldname description of the data element CHAR40 is shown.
Can i change this description ?
thx,
Gordon

No, The IDOC always displays the texts based on the Data Element which is assigned to that field. If you want to display your own text you have two options:
1. Create an enhancement and change the text of the data element which is not recopmmended because it will be changed wherever that data element is used.
2. Instead just create an own data element where you can maintain any texts you need.
Hope that helps,
Michael

What is the best program or app for "track changes"?

I am a book editor and I require a system to track changes while I am editing. Is there an app for that or is MS Word the best? If MS Word is the best, what is the cheapest, but still gets the job done?
Thanks

THANKS! STATION_TWO for the "over-correct-answer" you give................
If I'm honest, the answer of Richard was for me enough to realize where I made a "wrong inference" in understanding color management.
He is for me the best teacher in this case, I've learned something from him because he's talking on my level.
By the way: the english language is not my native language... so my questions should have to be read with understanding of grammatical expressions from other languages >> ("The color management is know by me…").
Again: Richard, in this case, read my question properly and has helped me on my way.

What are the views/fields that we can't change by Mass maintenance of MMR(material master record)?

Hello friends,
I would like to know the fields/views that we can not change by using mass maintenance of MMR if there are open PO for that particular material in concern. Likewise there was a question in SAP certification exam having options: "base unit of measure", "material type" and so on....

in general you can change any field that can be changed in MM02. if the field is grayed then you cannot. e.g. if you make use a MRP profile. and in this profile the maintenance of those fields is disabled then you cannot do it MM17 either.

What is the relevancy of BBPCO idoc?

Dear SAP gurus,
We're using SRM server 550 (SP08) with extended classic scenario. From the documentation I know that the PO will be created in R/3 using a BAPI which is BAPI_PO_CREATE (our backend is 4.6C). So I think if the PO is created using BAPI then the commitment will be created as per standard PO in R/3.
Then why do we still need BBPCO as an outbound idoc from SRM side to go to R/3 side? Wouldnt PO created by BAPI_PO_CREATE creating commitment as well?
Please enlight.
Best regards,
John.

Hi Yann,
Thanks for your quick reply. I ask this question because I got a very weird situation. We are using Extended Classic with SRM server 550 (SP08) and R/3 4.6C. So if the PO is approved by the last approver it should ALWAYS replicated to backend.
However we got some cases where the PO is not replicated. And for such POs, we see that idoc BBPCO is being sent from SRM. So we notice that if the PO is going to R/3 no BBPCO sent and if it is not going to R/3 then BBPCO is sent. So if what you said is correct, thus I think SRM thought that for these PO, standalone scenario applied, so rather than transferring the PO, BBPCO is being sent. But how is it possible? We already maintained that the product category * then the backend is set to the R/3. So it should NEVER be standalone, and we dont use any BADI related to the backend definition and transfer.
Based on our observation, this kind of thing usually happen if we generate PO from the accepted bid. But this bid should come from bidding invitation created from Shopping Cart (thru Sourcing Application). Even this would not ALWAYS happen, as we copied the SC into a new SC, push it to Sourcing, create bidding invitation and then accept bid and generate PO and now it is working. So we are really blank why does it happen in the first place.
Do you have any idea?
Thanks in advance.
John.

What is the Process code for IDoc SISCSO01

Hi all,
I am using 4.6c version.
I am going for an outbound IDoc SISCSO01 for sales Order confirmation.
I want the process code (we41) which suits this IDoc SISCSO01.
Can you please help to get the process code so that my IDoc can be sent succesfully.
Best Regards,
Gangolu

Hi Gangolu,
I don't think there is an outbound process code for IDoc type SISCSO01.
But you can generate the IDoc with this FM <b>MCV_STATISTICS_ALE_OUT_ORDER</b>. But you still need to setup partner profile, distribution model and etc.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

What is the Std Program for IDOC Blocking ?

Hi friends,
Tell me standard program for IDOC blocking.
Thanks and Regards..
naveen

Hi,
You have to write a program to do this:
tables: edidc.
data: idoc_status like EDI_DS occurs 0 with header line.
parameter: docnum like edidc-docnum.
idoc_status-logdat = sy-datum.
idoc_status-logtim = sy-uzeit.
idoc_status-status = '59'.
append idoc_status.
call function 'EDI_DOCUMENT_OPEN_FOR_PROCESS'
       exporting
            document_number = docnum.
      importing
           idoc_control    = edidc
      exceptions
           others          = 4.
CALL FUNCTION 'EDI_DOCUMENT_STATUS_SET'
EXPORTING
    DOCUMENT_NUMBER               = docnum
    IDOC_STATUS                   = IDOC_STATUS.
IMPORTING
IDOC_CONTROL                  =
EXCEPTIONS
DOCUMENT_NUMBER_INVALID       = 1
OTHER_FIELDS_INVALID          = 2
STATUS_INVALID                = 3
OTHERS                        = 4
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
CALL FUNCTION 'EDI_DOCUMENT_CLOSE_PROCESS'
EXPORTING
    DOCUMENT_NUMBER           = docnum
BACKGROUND                = NO_BACKGROUND
NO_DEQUEUE                = ' '
IMPORTING
IDOC_CONTROL              =
EXCEPTIONS
DOCUMENT_NOT_OPEN         = 1
FAILURE_IN_DB_WRITE       = 2
PARAMETER_ERROR           = 3
STATUS_SET_MISSING        = 4
OTHERS                    = 5
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
regards
Aveek

What is the cheapest way to end service and change to Tmobile?

I currently have a family plan with 5 phones and 1 tablet and am paying way too much. I would like to switch to Tmobile. 4 of the phones have contracts up in a month but the other phone and tablet have another year. However we do not use those lines, they were added in order to get a premature phone upgrade (I now see the mistake I made there..). What ETFs am I looking at for those two lines? What would be the best way to change to Tmobile?

Actually you can port all the numbers over as Lizdance stated on the 4 lines. Do this when the lines are free from contract. Otherwise T-Mobile will pay $120 per line if you leave one month early. However you have to pay the etfs first.
The other two lines can also be ported out but again you will be paying the fees first.
Please be aware if you read up on the reimbursement of the T-Mobile program many complaints about not getting the money from them (actually gift cards) they are denying many submission's for a number of reasons, some they claim were not submitted on time, some have missing information etc. So be very careful.
Also you will need to purchase all new devices, pay activation fees and may have to pay deposits. The service may not be all that great coverage wise so be certain all works before you switch.
Good Luck

What is the filed in ORDRSP idoc to stop changes in PO?

Similar Messages

Maybe you are looking for