B2B- IDOC 2 IDOC

Hi all,
We are building PI 7.1 from scratch. I have few doubts about it
My client has ECC 6.0 and installing PI 7.1 which able to receive and send IDOC's from it's customers (they also running ECC), so basically it is B2B IDOC 2 IDOC scenario. Can somebody tell me how to setup the Technical systems and Business Systems for this cross company scenario( I never worked on cross company scenario before).
Thanks in Advance,
Rishik.

SOURCE SIDE CONFIGURATION: Client ECC (SAP R/3)
1. Create RFC Destination: To create a RFC destination use transaction SM59.
2. Create Port: To create a port uses the transaction WE21
3. Now Go to Transaction Code SALE and create Logical System.
4.Creation of Partner Profile:
XI SIDE CONFIGURATION: Target SIde ECC (XI SYSTEM)
1. Create a RFC Destination with Target ECC(R/3 System) and select the connection type as 3(Connection to R/3 System).
2. Go to Transaction Code IDX1 and create an IDoc Port PORT_01 (Transactional RFC) and map it with the RFC destination
3. Go to Transaction Code IDX2, Click on Create and enter the details of IDoc Type and Source Port.
TARGET SIDE CONFIGURATION: CGNSAP01 (SAP R/3)
1. Go to SALE and create Logical System.
2. Create Partner Profile:

Similar Messages

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

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.

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

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

IDoc-IDoc scenario - EOIO

Hello,
we've implemented IDoc-IDoc scenario. Sender is regular SAP system, receiver is Non-SAP system supporting IDoc receiving via RFC. We have following problem:
1. Receiver system is stopped.
2. Sender system sends IDoc but the IDoc cann't be delivered into Receiver (it's still stopped). The message is placed into some queue.
3. Receiver system is started again.
4. Sender system sends IDoc and the IDoc is delivered into Receiver (now it's already running).
5. After a few minutes adapter try to re-send the first IDoc. Now the adapter is succesfull and the first IDoc is also delivered into Receiver.
Problem is that we need keep right order of the messages.
Is it possible to resolve it?
Thanks in advance for every advice!
Regards,
Zbynek

I've tried that but it doesn't work.
Also I've tried to follow this blog /people/community.user/blog/2006/11/04/how-to-serialize-idoc-xml-messages-fed-into-xi but it doesn't work either.
I think all IDocs are send from Integration Engine but if they are not delivered they are putted into some special queue of IDoc adapter. Is it possible?

Idoc - Idoc Scenario - Call User-Exit

Hi,
I have an Idoc - Idoc scenario and after receiving the Idoc in the receiver system, I have to call an user-exit, what is the best way to do this?
Or is it possible to do this?
-naveen.

Hi Naveen,
Nice to see here,I think you can do the above scenario by using BPM,i guess we can achieve by using the BPM.
Please proceed with BPM,If you have got stuck in the middle please update the issue so that I can help you out my level best.
Thanks in Advance.
Chandu

Idoc - Idoc scenario --SXMB_MONI

I worked on an Idoc - Idoc scenario. The scenario works fine.
In SXMB_MONIi can see the messages with processed sucessfully flag.
In the column, "Ack Status", there is Green question mark and it means that "Still waiting acknowledgement"
What are the other possible values for the ack status.
links or docs would help me.
-Naveen.

Hello Naveen
I know three acknowledgement symbols:
Green tick: no errors in acknowledgement
Red cross: Acknowledgment: contains applic. errors
Question mark: still awaiting acknowledgement
To figure out what happens, you also have to check the status of your message.
If there is a question mark and a final flag (processed successfully) then it seems that the message was sent successful but the acknowledgement was not able to reach the receiver.
!!!!You need an IDOC Receiver Communication channel called: Ack
This should solve the problem.
Daniel

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

A2A - IDoc - IDoc scenario Use of XI

In an A2A - IDoc -IDoc scenario, is the use of XI justified?
-Naveen.

Hi,
SAP is recommending to use XI to avoid point-to-point connection between two SAP systems like R/3 and SRM etc..
Also if you are planning to incorporate a 3 layer architecture (Presentation-- Integration and Database), then you can go for XI.
Refer thisSAP to SAP integration need XI?
Regards
Suraj

Passing header text into Idoc(Idoc type orders05)

Hi,
we have header text, header note etc in text tab(under details) in PO.
now i have to pass the data's from the header text into the IDoc(idoc type Orders05),
In which segment the data's will be populated, How to shall i go.

Hi,
if you are using idoc PORDCR102 or PORDCR101, header texts are populated in E1BPMEPOTEXTHEADER and both position & header in E1BPMEPOTEXT.
Then you are using ORDERS01-05 Idoc types, header texts were filled in E1EDKT1 & E1EDKT2 while texts are filled in E1EDPT1 & E1EDPT2.
The PO header texts are stored in the segments E1EDKT1 whose child segment is E1EDKT2 in IDoc type ORDERS05.
The actual text will be found in E1EDKT2 and the text id will be found in E1EDKT1.
You have to do some config so that The segment gets update
in the IDoc.
go to SPRO MM->Purchasing ->messages->Text for messages->Define texts for PO. Here you can find out on the left side of the window.In Header texts & supplements text.
Add the text IDF01( with all details like your document type, object for PO will be EKKO) in header text .
Then Add all other to the supplement texts(details).
It is now the IDoc should update the segments.
Regards
Raj.
Moderator message:
Warning. Reason: plagiarism, this is a copy-paste answer from:
PO texts in purchase order idoc*
Edited by: Csaba Szommer on Nov 8, 2011 2:00 PM

Replacing IDoc - IDoc with IDoc - Proxy

Hi every one,
I have an IDoc - IDoc integration scenario between 4.5B and ECC 6.0 systems. The Idoc in the receiver system is not directly posted but an User - Exit is called and every thing is working fine.
I thought of experimenting replacing the scenario with Idoc - Proxy, and the source being 4.5B and target ECC. The User-Exit stuff as told above will taken care while implementing proxy.
Approach:
I create an inbound interface object in IR and use the Idoc as the message type and generate a server proxy using SPROXY in the ABAP stack of XI.
Please correct me. Also notify me if there are any potentials problems.
Regards,
-Naveen.

Hi,
SPROXY on the ECC system should be used to generate the ABAP proxy, not the XI system. Therefore, configurations will be required on the ECC system to point to the XI system in order to retrieve the interfaces to generate the ABAP proxy.
Also, it might be easier to create a simpler message type to use in the interface. IDOC has a quite complex structure and probably contains a lot of elements which will not be used by your proxy. The proxy interface should be as simple as possible to simplify your program development.
Regards,
Bill

Idocs, idocs triggering

Hi SAP gurus,
Please send me some documentation/tutorials/learning material regarding IDOCS, Idoc Triggering. My mail id - [email protected]
Thanks in advance,
Regards,
Balu

Hi Balu,
Please check this online document for ALE and IDoc.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
Also check this links for additional information.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
Hope this will help to start with.
Regards,
Ferry Lianto

File- XI- IDoc: Idoc header data not saved correctly

Hi guys!
I have a very strange problem:
I have a file to xi to IDoc scenario. Everything seems to be fine, IDoc is created in target system, but with strange error: <MESCOD>XX</MESCOD> segment is not written in IDoc header segment. This segment is available in message sent to ECC (after mapping), so there is no problem with ommiting the segment in mapping. But it's not saved.
This scenario worx fine in QA, but not in PRO.
Any ideas, what to look at?
Thanx a lot! Olian

Hi,
check the IDoc which was in PROD. and see the ibound status and actual reason .
depending upon the actual status you can resolve the issue.
Chilla

File to idoc (Idoc is not getting posted in R/3 system)

Hi Experts,
I am having file to idoc scenario. In sxmb_moni i have seen success messages . The flag is checked on both sides.
So when clicked on the right hand side there are 443 idocs.but idoc is not posted on r/3 side. when i give the idoc number in r/3 system in we09 i couldnt find it? soi went for bd 87 transaction and gave the idoc number. it is saying that idoc is strucked in qrfc queue?
Kindly suggest.
Thanks in advance.
Regards
sai

hi,
if the IDoc is stuck in a qRFC queue means that the message did not reach the pipeline to be send to R3 so, anything in wrong at PI side.
please, go to SMQ2 and check whats happening. to know the queue name check the SXMB_MONI, select the proper message and scroll rightto the proper colum.
let us know.
Rodrigo P-.

B2B- IDOC 2 IDOC

Similar Messages

Maybe you are looking for