Request Idoc : Idoc ready to be transferred to application

Hi
I am getting the above error.
I am not able to process further.
In the details tab i am getting the following errors.
1 Extraction:missing messages
2.Transfer(Idoc and tRfc):ERRORS Occured
Request Idoc : Idoc ready to be transferred to application.
3. Processing : no data
4 Process Chains: Error Occured.
All of these errors are in Red.
I have cheked in BD87 WITHTHE IDOC NO. IT shows red status with Idoc enteries in tRFC queues
I don't know how to proceed further.
Please help in this issue asap.
Thanks in advance.

1) Transact RFC error
tRFC Error - status running Yellow for long time (Transact RFC will be enabled in Status tab in RSMO).
Step 1: Goto Details, Status get the IDoc number,and go to BD87 in R/3,place the cursor in the RED IDoc entroes in tRFC
queue thats under outbound processing and click on display the IDOC which is on the menu bar.
Step 2: In the next screen click on Display tRFC calls (will take you to SM58 particular TRFC call)
place the cursor on the particular Transaction ID and go to EDIT in the menu bar --> press 'Execute LUW'
(Display tRFC calls (will take you to SM58 particular TRFC call) ---> select the TrasnID ---> EDIT ---> Execute LUW)
Rather than going to SM58 and executing LUW directly it is safer to go through BD87 giving the IDOC name as it will take you
to the particular TRFC request for that Idoc.
OR
Go into the JOB Overview of the Load there you should be able to find the Data Package ID.
(For this in RSMO Screen> Environment> there is a option for Job overview.)
This Data Package TID is Transaction ID in SM58.
OR
SM58 > Give * / user name or background (Aleremote) user name and execute.It will show you all the pending TRFC with
Transaction ID.
In the Status Text column you can see two status
Transation Recorded and Transaction Executing
Don't disturb, if the status is second one Transaction Executing. If the status is first one (Transation Recorded) manually
execute the "Execute LUWs"
OR
Directly go to SM58 > Give * / user name or background (Aleremote) user name and execute. It will show TRFCs to be executed
for that user. Find the particular TRFC (SM37 > Req name > TID from data packet with sysfail).select the TrasnID (SM58) --->
EDIT ---> Execute LUW
This should help.
Also check these transactions to get more info on IDOCS.
WE02 Display IDoc
WE05 IDoc Lists
WE06 Active IDoc monitoring
WE07 IDoc statistics
WE08 Status File Interface
WE09 Search for IDoc in Database
WE10 Search for IDoc in Archive
WE23 Verification of IDoc processing
Thanks,
JituK

Similar Messages

IDoc ready to be transferred to application : Automatic Update

Hello All,
We are facing a challenge that during process chain execution, most of the request status is yellow. In most of the request there is one or more idoc which are not getting posted..and can be manually posted to BIW .
To remove the manual efforts what we thought was following ..
Schedule a background job using program RBDAPP01 and idoc status 64 (IDoc ready to be transferred to application)
Please let us know if this is the correct way to solve this problem.Any other way of doing things are welcomed.
Thanks a lot.
Regards
Nimesh

Hi Nimesh,
Yes.This would resolve your issue.
Those IDOCs might not get posted due to non availability of dialog work process.
I hope this is the only way you can do it.
Thank you.
Regards,
Karun.M

IDoc ready to be transferred to application

Hello all,
I have an XI scenario that transfers a producft in MATMAS05 format to ECC, but when it arrives in the ECC system the IDoc is staying in yellow state. It says IDoc ready to be transferred to application, but it's not going for some reason. I'm sorry for the obviously newbie quesion, but does anyone have any idea as to why this may be happening?

Ethan
You can go to BD87 and select option "Process it" if its in yellow state.
Best regards,
raj.

Status64: IDoc ready to be transferred to application

Hi,
The IDOC is coming to SAP but the status is 64 "IDoc ready to be transferred to application". Can you guys help me to process this IDOC successfully.
BR,
Madan Agrawal

Hi Madhan,
Fallow the steps...
1. SAP transaction code: BD64 Type /nbd64 in the SAP input window and press the
Enter key.
2. Notice that the Create model view push button is gray. This means that the function is
disabled.
3. Click the Distributional Model pull-down menu.
4. Select Switch processing mode to enable the Create model view function.
5. Click Create model view.
6. Fill in the Short text field.
7. Enter a meaningful Technical name.
8. Keep the Start date and the End date unchanged. The SAP system will prompt the
current date as the Start date. It will also prompt an end date, which is beyond most of
our lifetimes (December 31, 9999).
9. Click the green check icon to continue.
You will now see a new entry created with the short text you entered on the left side and the technical name on the right side.
10. Highlight the new entry.
11. Click Add message type on the top of the screen.
12. Fill in the information Sender as the SAP LS, Receiver as the LS of the remote system and message Type as MATMAS.
If you expand the new distribution model you will see that a new entry for the
message type MATMAS was created. If you need to support more message types, you need to repeat the Add message type operation for each of the SAP message types you will support.
The message type MATMAS will be supported for the outbound operations. SAP will send the MATMAS message type to remote LS.
If you will support inbound messages, you will need to specify Remote System LS as the sender and SAP LS as the receiver.
After you added all message types you want to support, you need to save your work:
14. Click the save icon (or press Ctrl+S) to save the model you just created.
15. You will see the message Distribution model has been saved displayed at the bottom of the SAP screen indicating that your work has been saved.
Generate a Partner Profile
A Partner Profile is defined for every SAP business partner. A partner is a remote SAP system or legacy system with which you exchange data. In our example, the partner is the remote system LS.
1. Highlight the newly created distribution entry in the SAP distribution model
screen.
2. Click the Environment pull-down menu.
3. Select Generate partner profiles.
4. In the Postprocessing:Authorized processors section of the previous screen, enter US as the user type. In partner system specify the remote LS.
5. Change the ID field if it is necessary. The fields default is the user id currently signed on to the SAP system. You may change it to the person who will be responsible for maintaining this partner profile.
6. Change the Outbound parmtrs: Output mode and Inbound parmtrs: Processing fields if it is necessary. Transfer IDoc immediately and Trigger immediately are selected as the default values,
7. Click on the execute button on the left corner of the system(resembles like a timer).
8. The return screen shown following will display. It is typical for you to receive a warning (pink/red) message such as Port could not be created". The reason for this message is you have not had an opportunity to tell SAP which port you will use for this partner profile. We will set it manually in the next step.
Modify the profile of the partner logical
system
The following steps explain how to modify the profile of the partner logical system.
1. Transaction code: WE20 Type /nwe20 on the SAP input window and press the Enter key.
2. Expand Partner Type LS (Logical System).
3. Click item remote system LS (or the name you use for the partner logical system).
4. Scroll down to see the Create outbound parameter icon +(add) below Outbound parmtrs table.
5. The Partner profiles: Outbound parameters will be displayed. Enter the following information:
Partn. funct.: Leave blank, as it is.
Message type: MATMAS
Receiver port: ALEport (or the port name you used.
Output mode: Select Transfer IDoc immed and Do not start subsystem.
IDoc Type:
o Basic Type: MATMAS03.
o Leave other fields as they are.
6. If you have more outbound parameters, repeat steps 4 and 5. If you support any inbound
parameters, perform the steps for creating inbound parameter. The steps for creating inbound parameters are similar to those for creating outbound parameters. The Create inbound parameter icon is located under the inbound params table, which is located below the outbound parameter table. If you are not sure whether you support any inbound messages, check the previous section, Create a distributional model, or use the SAP transaction code BD64 to view the distributional model.
7. Click the save icon (or press Ctrl+S) to save the outbound parameters you just created for the message type MATMAS.
8. You will see a message, Data saved displayed at the bottom of the SAP screen indicating that your work has been saved.
9. You will see that the MATMAS entry is added to the outbound parameter table.
Generating an Idoc definition file:WE61
give the basic type as matmas03 and right click on the screen you will find Parser click on that
This screen will be displayed.
now go to System-list-save-local file
We will get screen like this and here make sure that radio button is unconverted and then click on enter.
A window or pop up will be coming where in u can specify directory where the file is to be saved.
BD10 will be used for the transportation of the Idoc.
Next go to Go to bd87 and Process It.
Give u r IDOC Number there..
Hope this information is useful to you..
Thanks,
Satya Kumar..
Reward points if it is useful..

BI Load Failure: Error message....IDoc ready to be transferred to applicati

Hello All,
Many loads failed in Production, and in the monitor status it show
Extraction (messages): Missing messages (Status :Yellow)
       Missing message: Request received    (Status :Yellow)
       Missing message: Number of sent records (Status :Yellow)
       Missing message: Selection completed (Status :Yellow)
Transfer (IDocs and TRFC): Missing messages or warnings (Status :Yellow)
       Request IDoc : IDoc ready to be transferred to application (Status :Yellow)
Processing (data packet): No data (Status :Yellow)
I went through the below who has the same issue and solved it by increasing the work process of the IDOC's. Can anybody explain how to increase the work process of the Idocs and also the reason for the failure.
Re: Issue while uploading data from R/3 production to BW production

Hi Ram
I am getting the same error as you have stated here
the error is
Requests (messages): Everything OK (Status:Green)
   Data request arranged (Status:Green)
   Confirmed with: OK (Status:Green)
Extraction (messages): Missing messages
Data request received (Status:Green)
Missing message:No of sent records (Status:Yellow)
Missing message:Selection completed (Status:Yellow)
Transfer (IDocs and TRFC): Missing messages or warnings (Status:Green)
Request IDoc : IDoc ready to be transferred to application (Status:Green)
Info IDoc 1 : Application document posted (Status:Green)
Processing (data packet): No data
Please...... I think you cn guide me in this as u already resolved this type of error
Thanks in advance

Idoc ready to be transferred to app

trying to run an inbound idoc pordcr101
i get status 64 idoc ready to e transferred to app
how do i transfer it???
thank you

hi michal
i think my whole problem is that it is asking for purchase org
i use 3000 which is what i see in me23n when i look at old po
for doc_type is use BTW????is this for creating a po
i guess what i am lacking is a good place to see what is absolutely necessary to enter this idoc pordcr101 i look in bapi explorer it defines the fields but it does not say if they are required. also like doc_type there are no field values shown so i do not know what are actual allowed inputs for this field
there was a good source at the interface repository but it seems that link is gone
any help would be greatly appreciated

How to process idocs ready to be transfered

Hi Gurus,
I've an idco in we02 and its status is 64 idcos ready to be transfered can you pleae suggest me how to transfer this idoc.
Thanks in advance.

For Inbound Idocs, use the program RBDAPP01
For Outbound Idocs, use the program RSEOUT00
Thanks,
Srinivas

Hi In ALE ,IDOC HOW CONTROL DATA IS TRANSFERRED

Hi Experts,
Hi In ALE ,IDOC HOW CONTROL DATA IS TRANSFERRED .
Thanks & Regards
Bhaskar Rao.M

Hi Bhaskar Rao,
Good Check out the following documentation.
/people/kevin.wilson2/blog/2006/11/13/ale-scenario-development-guide
http://searchsap.techtarget.com/tip/0,289483,sid21_gci1230385,00.html
Some good links on ALE/IDOC
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
Please check this online document for ALE and IDoc.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
Also check this links for additional information.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
Good Luck and thanks
AK

Post system refresh, "Request IDoc : IDoc with errors added"

Hello All,
Post system refresh, we are not able to execute the data loads.
While loading the Infopackage, the overall status is still showing in YELLOW status. but in the Transfer (IDOCs & TRFC), it shows an Error message as "Request IDoc : IDoc with errors added"
Yesterday immediately after the refresh, we were able to execute the master data loads (full loads)...
However, transaction loads (delta) is facing issues.
Today, we are facing the problem in both master and transaction data.
Please help!!!! Its a very critical issue!!!
Edited by: Siegfried Szameitat on Aug 9, 2011 10:17 AM

Hi,
While selecting the Infopackage to run the INIT load, it is taking me to the ECC login screen. Once i enter my credentials, its showing a dump with the message:
Short text of error message:
No RFC authorization for user XXXXX ( RSA8 ).
Long text of error message:
Technical information about the message:
Message class....... "RSAR"
Number.............. 051
Variable 1.......... "No RFC authorization for user XXXXX ( RSA8 )."
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Please advice.
Regards
sneha

IDoc for "ready to Ship" in SD

Can the IDoc for "Ready to Ship" be DELVRY04 or we have to use something else?
Thanks,
Bhaskar

Is "Ready to Ship" is "Advance Shipment Notification" or some kind of shipping confirmation sent to your customer? If so, yes that is the IDoc type.

"Request message IDOC"?

What is the Request Message IDOC, and when is it used?
For example, MATFET, DEBFET and CREFET (material, customer and vendor request message IDOC respectively).
Any idea would be appreciated.
VT

>
Asit Purbey wrote:
> Hi,
> Go to transaction WE62 to see the documentation of the message types.
>
>
>
> Thanks,
> Asit Purbey.
Checking in WE62, I found that it's actually a message type. It is using with the IDOC type ALEREQ01. However, I still do now know when to use the message the IDOC type.
In the document, it only says that: "General request - Basis IDoc type "

R3 settings for IDOC-IDOC scenario

Hi,
For IDOC to IDOC scenario what are the settings we have to in R3 System other than XI configuration settings.
What are setting for both sender and receiver side.
Thanks,
Kishore

Hi Kishore,
http://help.sap.com/saphelp_nw04/helpdata/en/18/22b800773211d396b20004ac96334b/content.htm
http://www.erpgenie.com/index.php?option=com_content&task=view&id=346&Itemid=57
http://searchsap.techtarget.com/loginMembersOnly/1,289498,sid21_gci994575,00.html?NextURL=http%3A//searchsap.techtarget.com/expert/KnowledgebaseAnswer/0%2C289625%2Csid21_gci994575%2C00.html
http://www.thespot4sap.com/Articles/SAP_ALE_Other_Concepts_Conclusion.asp
Refer this material..
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.
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.
You can directly create an iDoc using some transaction like...
Use TCODE bd10 - to Send Data
and TCODE bd11 - to Get Data
and you can check the IDoc List using TCODE we02.
As you want step by step procedure.
1. Define Logical System and Assign Logical System
TCODE sale
2. Define RFC
TCODE sm59
3. Define Port
TCODE we21
4. Define Partner Profile
TCODE we20
5. Define Distribution Model
TCODE bd64
6. Send Data
TCODE bd10
7. Get Data
TCODE bd11
8. IDoc List
TCODE we02
There are basically two types of IDOCs.
Basic IDOCs
Extended IDOCs
Idoc Components
Basic Idoc
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extension Idoc
Extending the functionality by adding more segments to existing Basic IDOCs.
Creation of IDoc
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.
Create IDOC Type
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
u can also check all these links related to idocs
http://www.allsaplinks.com/idoc_sample.html
http://www.allsaplinks.com/
http://www.sap-img.com/
http://www.sappoint.com/abap.html
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
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://expertanswercenter.techtarget.com/eac/knowledgebaseCategory/0,295197,sid63_tax296858_idx0_off50,00.html
http://sap.ittoolbox.com/documents/popular-q-and-a/extending-a-basic-idoc-type-2358
http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b7eee43d711d1893e0000e8323c4f/frameset.htm
Reward points if this helps
Regards
Pragathi.

EDI / IDoc : While posting inbound IDocs, IDocs gets into status 56

EDI / IDoc : While posting inbound IDocs, IDocs gets into status 56 with message "EDI: Sender port in control record is invalid".
But if I reprocess the same idoc without doing any changes using RBDINPUT and select radio button to processs idocs for status 56, then it gets successfully posted.
So not getting why this stucks for the first time.
Thanks in Advance..........

i fixed this my self

EDI: IDoc ' IDOC No ' is already open in process mode

Hi,
I have a File to IDOC scenario. Everything is fine in PI. But in R/3, (WE05) there is an error. Please suggest what might be the problem.
IDoc: <IDOC No> Status: Application document not posted
EDI: IDoc <IDOC No>' is already open in process mode
Best Regards,
Madan Agrawal

Madan Agrawal,
I wonder whether this issue is related to SAP XI. It seems related to this thread: Re: Inbound Idoc not processed gives an error message
There the problem is related to some ABAP code is SAP R/3.
Kind regards,
Koen

IDOC - IDOC scenario with different message types

Dear Experts
I will like to have your expert opinion in the following question:
I have an IDOC -> IDOC scenario. Wherein at the destination system I have a message type which does not exist at the source system.
Also the IDOC type at destination system does not exist at the source system.
Let say, I will be creating custom message type at source system (Z****) and will also be creating the custom IDOC type (z****) with the same structure, definition as the destination.
Now my question is, even if there will be different message types and different IDOC types but with the same structure (the segment level definition
and field attribute remains the same at both the system). The difference lies with the names. And I have proper mapping though process code.
Will I be able to receive the IDOC correctly at destination?
Thanks & Best Regards

Hi All
I figured out the answer myself now.
You got to have same name for message type. All of you said this and this is rite.
Coming to IDOC type, I did not really got clear idea on this from this discussion.
But after working on a scenario, I learnt that, you can have different names for IDOCs, but provided that, whichever IDOC type the source system is sending, the same type must exist in your destination as well. Otherwise, system wont process your IDOC. But from mapping point of view, its upto individual how do thay handle mapping inside inbound process code for different idoc types / strucutes.
Lesson learnt by me, ideally try to keep same name for both logical message and idoc type at both source and destination. If possible try to keep the structure level also the same. This is my view, learnt it the hard way.
Cheers
Shane

Request Idoc : Idoc ready to be transferred to application

Similar Messages

Maybe you are looking for