Generate and Send WMTOID02 (WMTORD) Idoc to MII

Hi
Like we have POIT transaction in SAP ERP to genereate and Send Idocs Process or production orders ( LOIPRO01) to a RFC listner, is there a similar transaction to generate and send Idocs for WMTORD (WMTOID2) idocs?
I understand that the authomatic way is to have a change pointer progame but i want to test the idoc before we write a changepointer ABAP program.
Regards
Suraj

Hi Mike,
THanks for your responce , below are my answers to your questions....
If I understand you correctly, you are looking for the ECC t-code for generating the WMTORD IDoc, right?
Right
And you probably don't care whether it needs to be processed by either a RFC Listener or an IDoc Listener when it gets to MII?
I would receive it in an IDoc listner and then process using BLS transaction attached to a Processing rule in the message services.
In general, you send IDocs to an IDoc listener MII, but you may also do something along the lines of sending a control recipe (t-code CO53) to an RFC Listener in MII.
I would want to send IDocs to an IDoc listener MII. Similar to the LOIPRO01 example (http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a02bc7[[PDF] How to Send an IDoc from SAP ECC to the SAP MII IDoc Listener|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a02bc706-15f2-2c10-1aab-a1927ada11f0?quicklink=index&overridelayout=true] for production orders
Do you have a t-code or codes you can provide for related activity? Also is this for WM or for EWM?
LT01 and LT10 are the Tcode to create the Transfer orders. This is for WM.
Regards,
Suraj

Similar Messages

Issues with creating and sending BOM XML IDOC to SAP using 2010 WCF-SAP Adapter (without using Biztalk Server)

I'm trying to replace an existing Biztalk 2006 Send BOM IDOC process, and completely remove Biztalk server from the equation. The existing Bizatalk 2006 server receives an input BOM (Bill of Materials) flat file, and using a Biztalk Map (BM08),
and Orchestration, generates an Idoc and sends it to SAP.
In my replacement C# program, I'm using the 2010 WCF-SAP Adapter, and am trying to generate the BOMMAT03 XML IDOC it to SAP.
I generated the BOMMAT03 schema from SAP using the Add Adapter Service in VS 2010. I was able to generate a BM08 XSLT from the existing BMO8 map in the current Biztalk 2006 process. I am able to run a XSLT transform on the input BOM flat
file, and generate an XML file from that.
However, I've run into a few issues. First of which, is that the XML file that is generated from the XSLT transform is NOT the same schema as the BOMMAT03 schema expects. It's somewhat similar, but different enough that I have to manually
translate between the two in my code. I've verified that both the original Bitztalk 2006 process and my replacement program use BOMMAT V3 from SAP. Question--Is Biztalk 2006 server doing some other magic to turn that transormed XML into the BOMMAT03
schema?
I ended writing code which translates the transformed XML into the BOMMAT03 schema (which is a strong typed XML IDOC at this point).
However, when I try to send the BOMMAT03 XML IDOC, I get an exception "Object reference not set to an instance of an object."
idocClient.Send(idocData, ref sadapterTxGuid);
idocData is of type BOMMAT03, and I've verified that the various fields are populated.
Any help is appreciated.

Well, putting in a MSDN subscription support ticket for Biztalk server actually helped with the issue. They didn't find, or fix the issue directly. But one of the examples (https://randypaulo.wordpress.com/tag/idoc/) they sent over, jogged my
memory, and I realized in the code snippet below, I had accidentally deleted the 1st line. Such a simple mistake, yet was easy to overlook. The URL example is almost EXACTLY like my code, but without the transform and translation code to convert
from input XML file to IDOC XML. If someone is interested in that, let me know.
//Forgot the 1st line.
idocClient = new IdocBOMMAT03SIEIS_WED_BOMMAT03V3R700Client(binding, endpointAddress);
idocClient.Send(idocData, ref sadapterTxGuid);
For anyone else interested in knowing, you CAN send a strongly typed IDOC to SAP using C#.NET and the WCF SAP 2010 Adapter, using the IDOC Binding Client class you generated using the Add Adapter Service Reference in VS2010.
The one difference, which no one, not even the tech support from MS could tell me, was why the XSLT which I generated from the original map, did not transform the input BOM XML into the BOMMAT03 XML. Instead, it transformed it into an intermediate
XML, which resembled the BOMMAT03 IDOC XML, but still needed to be translated to the BOMMAT03 IDOC format.
The tech support person swore up and down that it should. But I believe that something happens in Biztalk server, after the Mapping occurs, maybe in the Pipeline, which converts that
intermediate XML into the final BOMMAT03 IDOC XML format.
I do think that the examples are severely lacking in showing how to send a strong typed IDOC using C# and the WCF-SAP Adapter. Even worse, the examples are completely lacking in how to actually generate a weakly typed IDOC. They show how to send
that weakly typed IDOC, but show me, or give me a class to be able to generate it.
I realize that this is not quite the "recommended way" to do it, but in reality, not everyone wants or even needs a full Biztalk installation. For some simple stuff like this, a C#.NET program and WCF-SAP adapter do the trick.

Generate and send Excel format file by mail in bakground.

Hi fellows, i have a requirement, which is to generate an excel file in background and send it attached by e-mail. This file have many characteristics like Freeze pane, Auto filters, and some other format characteristics, One of the ways for achieving this kind of characteristics is using OLE or Desktop Office Integration, but both run in foreground. Other way i found is formatting the excel using XML and then at the moment of sending it by mail, changing extension for xls, but the problem is that it occupies too much space, i imagine cause it is raw xml, for example for a file for 1,000 records and 14 columns generates a file of 1.6Mb which is not like generating the same file using OLE or DOI (24Kb).
I would like to know if there is a way to use an excel component or another way that takes less space for generating the file with format and also send it by e-mail in background??
Thanks.
Noe.

is 1.6 MB the smallest size you can generate, did you remove every optional tag?
XLSX format is a compressed XML format valid since office 2007. Maybe you can try to generate it? (I don't exactly know which ZIP algorithm it requires, SAP can compress using the ZLIB Compression Library)
You may also attach a Windows server to SAP via RFC. You should create an RFC server. You may have a look at this [sdn article - Communication to Presentation Server in Background Mode|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/9831750a-0801-0010-1d9e-f8c64efb2bd2] for some clues about running an RFC server. I guess you could use a VB script on the server.
For sending emails, this is a separate question, you may have a look at wiki: sending mails - home page.

Monitoring and sending alerts for IDocs

Hi ,
I have Idoc scenarios both outbound and inbound.
My requirement is that whenever an Idoc goes into error state an alert should be sent to a specified person automatically.
Please also let me know ways to reprocess Inbound and outbound Idocs.
Thanks

Hi,
Your question is mainly for ECC, than for PI...
but you can acheive it, for instance, by creating an abap program which checks the IDoc status, and send an email to a list of persons you determined for instance in a Ztable for each idoc (message type + idoc type + idoc extension). You can scheduled this program by creating a SAP job (tcode SM36).
Another way could be to add an abap enhancement in each idoc process (inbound / outbound) to check the status of this idoc and send an email. But...
Personally, I prefer the 1st solution, as the program is scheduled, you can group several idoc errors and send only one email (!). Keep in mind this case: among 1000 inbound idocs, 750 are in error, because of a bad or a missing data in the source system... What 's the result with the 2nd solution?... it's a spam of 750 emails to the emailbox of your employees (!!!. Not sure they will appreciate...
To retreat Idoc, you can use tcode BD87. Do not give this tcode to all employees, but only to some key users, to avoid that an employee retreat several idocs which are not in its scope (because he/she did not a godd selection in the selection screen) and which should be not be retreat now (exm due to a fiscel year).
regards
Mickael

Generating and transferring purchase requisition IDoc

In ECC 6.0 there exists ALE_PR_CREATE which gave us all the required fields for generating the IDoc that we needed to transfer to our JCo program. Once the IDoc was generated using this program, it's status was set to '30' automatically.
The next step in order to send this generated IDoc to the designated port was to make use of the standard program RSEOUT00 passing the message type so that it sends all IDocs, of that particular message type (PREQCR and PREQDL in our case) and having a status of 30, to the port, changing the status to 12 once this operation is completed.
Since it was a standard program , I used the same logic in 4.6C. Unfortunately, the function module ALE_PR_CREATE does not exist in 4.6C.
The alternative was to use ALE_REQUISITION_CREATE and ALE_REQUISITION_DELETE.
Why 2 Function modules? Here's why...
The first function module gave us all the required fields except one - the deletion indicator.
Keep in mind that this field was also provided by ALE_PR_CREATE in ECC 6.0 system thus eliminating the need to look elsewhere.
So, to satisfy our requirement of getting the deletion indicator for deleted items of a particular Purchase requisition, we found the second mentioned function module - ALE_REQUISITION_DELETE.
This threw another problem in front of us...
This function module gave us only the purchase requisition number, item number and deletion indicator. All the other data fields that we required for our java app to process the IDoc were missing.
In order to solve this issue, we have designed our program to generate 2 IDocs one after the other. First using ALE_REQUISTION_CREATE and next using ALE_REQUISITION_DELETE in sequence.
This gives us all the fields.
The next problem was that the generated IDocs were having the status 03 (Data passed to port. OK.) but the Java application never seemed to receive the generated IDocs.
A search on SDN led me to check the IDoc queue in SMQ1, a case of stuck IDocs in SM58 and also changing IDoc status in BD75 all in vain.
Finally, on debugging the RSEOUT00 program, found out that it is checking for the status '30' (IDoc ready to be sent to port) which is hard coded in the program.
On doing further research on SDN, find some resources that suggested various function modules.
Tried out all of them one after the other.
By trial and error, finally stumbled upon the Function Module 'DEQUEUE_ES_EDIDOCS' that acted as a replacement to using the RSEOUT00 program.
After the IDoc is generated, just passing the IDoc number to this Function module sends it to the port and this was successfully received by our Java app.
Posting this on SDN for the general benefit.
Has anyone faced any similar issues? Let us know.

Hi,
Im using the non-enjoy BAPI and BAdI for PR and for deletion the outbound IDoc gets send out all the way but for create outbound IDoc it gets stuck in status 30. I did try the FM that you suggested but doesnt have any effect.
FMs that is being used inside my BAdI:
ALE_REQUISITION_CREATE
ALE_REQUISITION_DELETE
Thanks,
Arash

Automate generating and sending reports

Hi All,
Is it possible to automate the following steps in BPC 7.0?
After uploading monthly actual SG&A to BPC...
1. Refresh a report, say C1, by individual function (CTO, Finance, Sales & etc)
2. Convert the above files into paste value format (maybe save the above reports in offline mode)
3. Automatic send each report to a respected functional head each month
If it's not possible in 7.0, is there an alternative? Like using BOBJ to access the BPC 7.0 db directly and formulate/format the reports in BOBJ?
Thanks.

Hi pkrishnas,
Thanks for the info.
I set up a distribution according to the documentation and also set up the appset parameters related to SMTP.
When I want to distribute my report, I get an error something like "Cannot get email address from SQL xxx\myuserid" (where xxx is the BPC server name).
The user myuserid has been entered with a correct email address and security. But the user is not a local user to the server xxx. The user has an email address at a different domain. Below is the user detail:
UserID: xyz\myuserid
User Name: John Doe
Email: myuserid at xyz dot com <rewrite to avoid the forum auto filter>
IM address: <blank>
Do you or anyone else know the cause and how to resolve this issue? Do I have configure something else?
Thanks.
=Hamdy

If buyer side created an PO and send out the IDOC to us...

Hi,
I am seller side. Normally to say, this IDOC will be automaticlly loaded and corresponding SO could be created.
But for now, the corresponding SO has not beeen created. How do i analysis what happened to this inbound IDOC?
Currently i have the IDOC number which provided by Buyer, this IDOC number is not from my system.
Based on this IDOC number, which Transaction could i analysis why the IDOC couldnt be loaded successfully...?
Thanks!!

First of all, request the below information from the buyer about the PO's IDOC.
PO#
IDOC Date
IDOC Control numbers (interchange, message group control # and transaction control #).
Then go to WE05 and give a date range per the information provided by customer. Without giving IDOC number, provide the message as ORDERS (hopefully you are using standard orders processing). Provide the port from where you receive EDI orders.
Then on WE05, you should see the EDI selection tab. GO to that tab and enter the interchange control # (on Interchange file reference), group # (Reference to message group) and transaction control #(Message reference).
You should see the corresponding IDOC in your system if you have received it in SAP. Otherwise, I suggest that you then follow up with your EDI team on whether the EDI sub-system received this PO or not.
Thanks
Nikhil

Error message mes when trying to send PO via IDOCS to another system?

Hi Abap expert,
I am getting wired message what I ma trying to send PO via IDocs to other SAP system.
I went to all partner , port configurations on WE20 and everything there seems to be fine but once I go to ME23N, then GO TO -> MESSAGES , than opens another windows when you key in MESSAGE CONTROL DATA that have been mantained
in the outbound parameters in the PARTNER PROFILE configurations.Then I am getting the message :
'No communication data has been defined for transmission medium 6'-----
The LED on "PO:output screen' is YELLOW and never gets green.
Can someone tell me how to overcome this and send my PO Idocs?Please some more details will be appreciate it!
Thank you much eveyone!
Boby

Hi,
Go and check it in NACE tcode, whether , Condition type, output types are maintained or not? if not maintained, Maintain it for 6 -PO for EDI.
Hope this is the error you are getting.
Thanks
Manju

ME23N Error when trying to send PO via IDOCS to another system?

Hello Experts,
I am getting wired message what I ma trying to send PO via IDocs to other SAP system (XI)
I went to all partner , port configurations on WE20 and everything there seems to be fine but once I go to ME23N, then GO TO -> MESSAGES , than opens another windows when you key in MESSAGE CONTROL DATA that have been mantained
in the outbound parameters in the PARTNER PROFILE configurations.Then I am getting the message :
'No communication data has been defined for transmission medium 6'-----
The LED on "PO:output screen' is YELLOW and never gets green.
Can someone tell me how to overcome this and send my PO Idocs?Please some more details will be appreciate it!
Thank you much eveyone!
Boby

I just got the same problem. Everything worked fine when i was using message type ORDERS01, but when i changed it to ORDERS05 this problem started happening.
This might solve your problem. If you have it solved out can you tell us the solution you found??
regards,
Diogo

T-code ME23N message when trying to send PO via IDOCS to another system?

Hello MM Experts,
I am not sure if my question is more for ABAP guys , but since it is MM related I decided to share it with MM experts as well.
I am getting wired message what I am trying to send PO via IDocs to other SAP system (XI)
I went to all partner , port configurations on WE20 and everything there seems to be fine but once I go to ME23N, then GO TO -> MESSAGES , than opens another windows when you key in MESSAGE CONTROL DATA that have been mantained
in the outbound parameters in the PARTNER PROFILE configurations.Then I am getting the message :
'No communication data has been defined for transmission medium 6'-----
The LED on "PO:output screen' is YELLOW and never gets green.
Can someone tell me how to overcome this and send my PO Idocs?Please some more details will be appreciate it!
Thank you much eveyone!
Boby

Hi Boby ,
TRY going thru this link and check for the details given in it wether they are in place or not specially in the message controls, viz: application EF ,message type NEU and process code ME10
http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b7c9f43d711d1893e0000e8323c4f/frameset.htm
regards
kp

Want to replicate Payext IDocs and send them to another logical system

Hi all
we are generating payext Idocs to a bank partner profile using rffoedi1 program. Our requirement is to replicate the same payext IDoc and send to another logical system using a different partner profile.
I have a rough idea of sucking data from EDID4 table....
Can any one let me know how the code looks like If we have to create same IDocs again with different control record with same kind of data?
can some one throw their ideas of doing this with less development work?
Thanks
Steve

Try this way:-->
1.Using fm IDOC_READ_COMPLETELY get complete data of IDoc you want to send, then change the Header record (EDIDC) with new partner profile, port and other values
2. Pass these values to fm MASTER_IDOC_DISTRIBUTE.
(pl remember to clear EDIDS values before calling above said fm)
This will send your IDoc to new destination
a®s
Edited by: a®s on Apr 10, 2008 3:41 PM

Creating Idoc and sending it to its own...

Hello All,
The functional design specified that an inbound function module needs to be created to process a custom IDOC, let's say ZMMDLRTL, and using the data from the segments from this basic type ZMMDLRTL, I need to create another IDOC of basic type PORDCR101 to create a PO. This PO IDOC would then have to be posted to the same system where the inbound function module that would process the ZMMDLRTL IDOC. So this is just like creating an IDOC and sending it to yourself right?
I used the function module MASTER_IDOC_DISTRIBUTE to create the PORDCR101 Idoc and sends it to itself. But now I am getting an error status 20, which is "Receive of IDOC is its own logical system". I just need some inputs on this.
Thanks,
Kristine

Hi!
In two words - to avoid this error you have to send PORDCR101 to another logical system pointing to the same client and make corresponding settings in distribution model (as you use MASTER_IDOC_DISTRIBUTE).
Proceed as follows:
1. Create a "dummy" logical system name, say LOGSYSD. This dummy logical system will serve as the receiver system in the distribution model.
2. Using SM59 create RFC-destination LOGSYSD for the dummy logical system. The RFC-destination addresses the same client.
3. Create a distribution view in BD64 with your "real" logical system for client as the sender and LOGSYSD as the receiver for your message type.
4. Generate partner profiles for distribution model using BD82.
5. Using WE20 create inbound parameters for your message type for "real" logical system.
Hope it helps.
Regards,
Maxim.

How to create idoc and send it frm one sap to another sap

hi,
can anyone tell me the complete procedure of creating the idoc and sending it to another sap r/3
how to create rfc destination, partner profiles, port and outbound parameter and inbound parameter
thanks

Hi Azhar,
Go through the following Links
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
Go through the following Steps for Creating IDoc Via ALE
ALE IDOC
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
I know how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
        save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
   select all what ever you want and delete remaining fields.
   save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
   it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
   give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
Regards
Sreeni

Why Sender side IDOC adapter doesnt have SenderAgreement and Sender CC

Why Sender side IDOC adapter doesnt have SenderAgreement and Sender CC . But in receiver side it is having.
what i know is
1) Idoc adapter is in ABAP Stack.
2)XI having Idoc Metadata.
3)Once Communication Idoc generated , no control on it.
4)SAP using TRFC to identify XI , XI cant.
Pls explain , in comparition with receiverside. Dont post links.

Hi vijayreddy.veluri
these questions are very general.
Please refer to the
[rules of engagement|/thread/117188 [original link is broken];
before creating threads.
Sender agreements are not required as there is no requirement to bind sender information to a sender communication channel.
[IDoc Processing with the IDoc Adapter|http://help.sap.com/saphelp_nw04/helpdata/en/b9/c5b13bbeb0cb37e10000000a11402f/content.htm]
Thanks and Regards
Kenny Scott
SDN XI/PI Moderator

Why we dont need sender agreement and comm channel in IDOC to file scenario

Hi,
there are 2 queries:
first query :
Scenario is "Idoc to file transfer"
why we dont need sender agreement and communication channel for IDOC to file ,while we do need
both of these for "File to RFC "
Answer : which i got is because IDOC sits at ABAP stack but same is valid for RFC also.
Then why For "IDOC to file" we dont need that.
Second query:
Also when i did scenario for File1-RFC-File2 scenario using BPM i have created a interface
between XI-RFC synchronous to send data which we got from file1 in XI to RFC importing parameter
and getting data from RFC back to File2.
Here in IDOC to file scenario why we dont need any interfface for IDOC-XI Asynchronous.
Regards,
Mayank
Edited by: mayank verdia on Jan 13, 2009 11:49 AM
Edited by: mayank verdia on Jan 13, 2009 11:50 AM

Dear All,
For file to idoc scenario is there any possibility to get line items details or xml details i.e the segments and its related field details using reference id, transaction id or interface name or message id in SAP PI 7.0. I know we need to click each and every message in sxi_monitor and look for details.
For SAP(R3 System) I can create a report and set the job for specific time period so automatically it throws the details(like reference no, document date, invoice no from) in ftp path as .csv file. The same ftp path is maintained in program.
I wanted to check FTP--->PI postings and I have set the job at r3 system it is working fine and Im monitoring it too.
Now the end to end scenario is FTP--->PI--->ECC(R3 system). Please help.Many Thanks.

Generate and Send WMTOID02 (WMTORD) Idoc to MII

Similar Messages

Maybe you are looking for