Idoc as sender

Hello,
Is it not that the port name in SAP XI and the RFC destination in R/3 of type 3 be of the same name, like SAP(r/3 SID) ?
Also, the RFC destination mentioned in the idx1, in XI, isnt that the same name as mentioned in the XI - sm59 R/3 destination pointing to Sender SAP System
Thanks,
Vishal

i created,
a destination in r/3 say, abc pointing to Xi.
i give port name in XI, as SAPSID.
give the rfc name there as def and create the same one in sm59 for Xi.
This seems alright, isnt it?
my idocs were getting posted before, but suddenly stopped..
any specific reasons?
sm58 in sender and Xi shows nothing...
no changes have been made to anything, in R3, it shows successfully send and in Xi, its not recd.
Thanks,
Vishal

Similar Messages

Send orders idoc from sender

Experts
tell me which tcode is used to send the sales order data from sender to receiver.
Example : we use the following tcode to send the master data idocs like
SEND MATERIAL MASTER: BD10
SEND VENDOR MASTER: BD12
1)is there any tcode to send the sales order data also like this.
2)if tcode not there then tell me which function module is used in the sender system to fill the segments of order01 idoc.
3) I want to fill the sales order data in the segments , the following data i need to fill
sales area , document type , customer numeber , payment terms , material , net price , quantity , order data , po number.
tell me which segments are used for this.
4)where to see the segments of the idoc and its fields.
5) if any one having sample code to fill the orders idoc , please give me the link

prabhu
send data through Message control ? means how to send .
My requirement is to fill the idoc segments and then to post.
Which tcode is used to see the segment fileds both header and item other than we60 , we61.
For orders01 idoc how to identify which segment fields are used for sales area , customer , payment term etc becasue po fields are also there, so confusing

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 <b>"real"</b> 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

IDOC for sending material including classification data?

Hi everyone,
I'm just looking for an IDOC to send to an external system all data of certain materials but including classification system data, variant configuration data...
I have checked MATMAS0x but I am not sure if those IDOCs match with my requirement.
I would be very grateful if someone could please help me.
Thanks in advance and best regards,
Ben

Hi,
CLFMAS01     Master object classification
CLFMAS02     Master object classification
STTMAT01     STTMAT: Material variants
BOMMAT01     Master BOM - material
BOMMAT02     Master BOM - material (2)
BOMMAT03     Material BOM (from 4.6B)
BOMMAT04     Material BOM with UPS Link
MATMAS01     Material Master
MATMAS02     Material Master
MATMAS03     Material Master
MATMAS04     Material Master
MATMAS0x with CLFMAS0x should solve your problem.
Regards,
Srilatha.

IDOC for sending material data including classification data?

Hi everyone,
I'm just looking for an IDOC to send to an external system all data of certain materials but including classification system data, variant configuration data...
I have checked MATMAS0x but I am not sure if those IDOCs match with my requirement.
I would be very grateful if someone could please help me.
Thanks in advance and best regards,
Ben

Hi Ben
Kindly follows the below steps and trasaction screens, I believe you will be able to send the mat data incl. classification data to other external system through IDOC.
Steps:
Create material master record in SAP
Enter T.Code BD10 to send material master data from SAP to 3rd Party Logistics Provider
Enter Material,Logical System and click Execute(F8)
Press ENTER to continue
Press ENTER to continue
Enter T.Code WE09 to check the status and content of the Idoc created
Enter Idoc Segment name in Search in Segment, Field name in Search in Field, Material No in "for Value" and press F8 to execute
Double click on the Idoc number to check the content and status of the Idoc
Expand the Status records to check the STATUS of the Idoc
To check the fields in the Idoc, expand Data records and check the Mandatory fields in each Segment
Transaction Screens:
Transaction / Screen
MM01
BD10
BD10 Screen
BD10 Screen
BD10 Screen
WE09
WE09 Screen
WE09 Screen
WE09 Screen
WE09 Screen
Expected Result:
Expected Result
Material Master Record Created
Send Material Screen appears
A popup window appears with a message "1 master Idoc(s) set up for message type MATMAS"
A popup window appears with a message "1 Communication Idoc(s) generated for message type MATMAS"
Send Material Screen appears
Idoc Search for Business Content screen appears
Idoc corresponding to the material no is displayed
Idoc along with the 3 records(Control Record,Data Record,Status Record) appers
Final STATUS should be 03(Data passed to port OK)
All Mandatory fields must be populated with correct data
If it is useful reward points
Thanks
Saravana

What are the idoc to send data from sap hr to sap fi

what are the idoc to send data from sap hr to sap fi

Message type of IDoc depends on the data you wish to send.
please detail on the data that you need to send in the IDocs.
regards,
Nitin

Create idoc and send the purchase order

Hi all,
In transaction code ME22N when the items in PO is changed then it should make delivery zero and in another system another delivery should be created that should be done via IDOC...
so please help me in finding BAPI or FM to send IDOC to another system...
IF u have any question please ask me, i ll tell the requirement...
thanks in adv...

Hi pawan ,
Check this link, it contains info about Sending IDocs to an External System
Link: [http://help.sap.com/saphelp_bw/helpdata/en/52/16ae23543311d1891c0000e8322f96/content.htm]
Regards,
Anand

IDOC AAE sender adapter

Dear all,
I have a question about the IDOC AAE adapter on a PI 7.31 java only system with an ERP --IDoc--> PI --File--> FTP scenario
In my scenario I would need to change IDOC DC40 Segment information before the IDOC is being processed in the PI pipeline. Unforutnately I cannot change the header information directly on the sending system.
The processing on PI will fail due to the faulty DC40 settings, therefore I would like to correct the Segment before PI is processing the file.
I thought about using the PutPayloadValue bean to replace values in the IDOC XML structure but this does not seem to work. If I call the bean before "CallSapAdapter" in the module chain, this will result in the following error: "while trying to invoke the method org.w3c.dom.Node.appendChild(org.w3c.dom.Node) of an object loaded from local variable 'template_parent". Is this because the idoc xml is generated on the PI only after the CalSapAdater step and not already on the ERP? Or might it be due to miss-configuration? (I did not provide a namespace in the module settings of the bean as the IDoc XML structure has no namespace)
What other options would I have on PI to edit the DC40 segment before the pipeline processing?

I had a similar issue on a different adapter type.
Please make sure to insert the appropriate namespace in parameter xmlns AND in the put value. Example:
xmlns xmlns:ns0="http://www.test.com"
put:/ns0:root/ns0:field1 "value"
If the xpath is not correct (you can test it here, for instance Simple online XPath tester) the insertion of the value into the node will fail.
Regards,
Antonio
ps. if you like to DEBUG, the .class bytecode of ALL SAP PI Standard Adapters can be found here: com.sap.aii.af.ejb.zip\com\sap\aii\af\app\modules

Invoice IDOC is sending wrong Net value

Hi Champs,
We have an interface whetre Invoices will be sending to the third system through IDOCS.
These are prepared and being transferred by using Standard FM Invoice_Inbound_Asynchronous. But there is a very peculiar problem when sending some invoices, like some invoices are pushing ITEM wise wrong amount thruogh segment E1EDP01 -> E1EDP26 003 -> BETRG (Field). I could not get from where this amount is being picked.
Could any one help me if you face similar type of issue.
In the IDOCS flow of last two years, only 6 IDOCS are sent with wrong amount until now.
Thank You
With Regards,
Ravi kanth Yechuri.

Friends,
can you please hep me out whether i can apply any SAP note or so...
Thank You
Ravi Kanth Yechuri

IDOC's sending to XI from NON-SAP system

I need to send one IDOC from a NON-SAP sytem to XI. In my scenario I've configured a receiver IDOC adapter with the suitables RFC destination and Port for the SAP R/3 receiver system. We achieve this sending by using the following URL: "http://:/sap/xi/engine?type=entry" but we don´t get any message in XI. We don´t know if we are doing it properly.
Could you help me?
Thank you in advance.
Juan Pablo.

Hi Juan,
Did you try the HTTP client tool that Michal gaves you?
Attention: the URL address that this tool or any other client who wants send messages via XI with http is: http://<our-server>:<http-port>/sap/xi/engine?type=entry and not -> http://<our-server>:<our-port>/sap/xi
This URL must be set on the pipeline of XI Business System (role-> Integration Server) as well on integration server configuration.
If you have http port and adapter_plain service (sifc) running it should be working!!!
Open your browser and put the Integration Engine URL http://<our-server>:<http-port>/sap/xi/engine?type=entry
If its running you should be see this soap message:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Header />
- <SOAP:Body>
- <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode>SOAP:Client</faultcode>
<faultstring>Empty HTTP request received</faultstring>
<faultactor>http://sap.com/xi/XI/Message/30</faultactor>
- <detail>
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="MESSAGE">EMPTY_HTTP_REQUEST_RECEIVED</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Empty HTTP query received. No message processing possible</SAP:Stack>
</SAP:Error>
</detail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>[/code]
Cheers,
Ricardo.
Message was edited by: Ricardo Quintino
Message was edited by: Ricardo Quintino

IDOC Packaging Sender CC

Hi Gurus,
I've been using IDOC packaging in the IDOC sender communication channel very well without any problems so far.
Most of my scenarios I have to group several IDOCS and generate just one file, and using the new functionality I can reach my scenario easily and with good performance.
However I am trying to configure this same thing for a new IDOC, but it's not working.
So, I've checked the option in IDOC sender communication channel as usual, set up the size for 9999, I go to we20 and change the partner profile to collect IDOCs and also set it up to 9999 as package size. Following this blog. IDoc Packaging - SAP PI 7.1 EHP1 (and above)
However for this new configuration, when I trigger 2 or 3 IDOCS at the same time it creates 2 or 3 messages in PI as well, and it should create just ONE message in PI. What make me confuse is If I trigger 2 or 3 IDOCS for the other type of IDOC, regarding the old configuration it works...just one message is created in PI
So I am really confused why for this IDOC is not working and for the OLD configuration is working. Am I missing something ?
Thanks
BEst REgards
Diego

Hi All,
Yes, I had done everything
In fact I wanted to see the IDOC being collapsed with several IDOC nodes in the monitoring.
So the problem was solved quite easily I was triggering the IDOC through the program and the OutPut node was in blank and by default is set to 2 (transfer immediately) it skips the configuration that you have done in we20 and do it by itself.
So I put the propoer Output mode (4) and it worked well
Thank you for the answers
Regards
Diego

Trigger an outbound idoc to sender system after inbound idoc has status 53

Hi all,
We have two different partners (say A and B)which send inbound idoc to ECC of same message type WMMBXY. This updates goods movement. The partner A collects the idocs(WE20 partner profile setting) and partner B trigger's immediately. Now our requirement is after successful processing of idocs (satus 53) we need to send another type of idocs to the sender regarding the updation/ changes occured in ECC.
Since partner A collects the idocs how can we check that it reaches 53 status and send the outbound idoc to A.
Kindly help me in solving this issue.
Thanks,
Aravind

Create a new process code WMMB to ZMMB & assign a FM ZL_IDOC_INPUT_WMMBXY
& call the standard FM L_IDOC_INPUT_WMMBXY , check the status or any error other wise create a new IDOC using
Master_IDOC_CREATE, hope the solution works for you

How to Collect IDOCS before sending to 3rd party

Hi All,
I am sending out PO's using ORDERS idoc from SAP to 3rd party.
In my scenario I need to group the similar IDOC data into a single file before sending it out to the 3rd party using XI. So in Partner profile I have choosen 'Collect IDOC' option and given the count as 10.
Once IDOCS were generated they were in Status '30'. So I then ran RSEOUT00 to flush the PO idocs to XI. It did flush them out but as individual IDOCS.
I had the impression that 'Collect IDOC' files the selected IDOCS into a SINGLE file/IDOC and then sends it out. Was I right in assuming that collect IDOCS merges all idocs into 1 file/idoc or is it wrong.
If it does not, is there a way how I can merge all these IDOCS into a single file before sending to 3rd party ?
Thanks
Shirin

Hi Shirin,
For IDoc packages see -
XI:Idoc Message Packages
The specified item was not found.
For IDoc Bundling see - The specified item was not found.
Also, to see BPM Collect patterns, you can navigate to the SWCV named SAP BASIS in your IR. Under namespace http://sap.com/xi/XI/System/Patterns you will find the integration process called BpmPatternCollectPayload. There are many examples in this namespace.
If you are new to BPM, see this - [Step by Step Guide to BPM|http://www.riyaz.net/blog/index.php/2008/04/16/a-step-by-step-guide-to-bpm-asynch-sync-bridge/].
Hope this helps.
Regards,
Riyaz

[IDOC] WE19 send successfully ...but where it is?

Hi,
creating scenario IDOC -> XI -> File with own IDOC.
After sending it with we19 he said "IDoc sent to SAP system or external program".
In we02 and we05 the IDOC it says "Data passed to port OK".
Business Systems:
Sender : SAPBS Client 200
Receiver: SAPXI Client 001
(Both on same SAP server)
But it never appears in sxmb_moni nor a file is created on receiver system.
How to debug where the error could be?
-RWE doesn't show an error in adapter monitoring.
-Destination is tested successfully
What else?
thanks
chris

Ok, my fault. Looking in XI client for sm58. In Busines system I found IDOCs with following error:
"Transaction IDX1: Port SAPERP_200, client 200, RFC destination contain e"
I think this shoul mean error. But why?
I checked [this guideline|https://wiki.sdn.sap.com/wiki/pages/viewpage.action?spaceKey=XI&title=SAPR3%28Idocs%29ToXI--Steps+Summarized&decorator=printable]
It seems he tries to use a port for ERP_200 (R/3 System), but I think he shouldn't or?
My configuration again:
R/3 system
sm59: ERP_00_001
we21: P_XI_OB (using destination ERP_00_001)
BD54: ERP_00_001 (XI System)
WE20: ERP_00_001 using my Message Type ZPersonal_Test with Receiver port P_XI_OB)
XI system
sm59 : ERP_00_200 (is this for sending back acks or to get meta data?)
idx1: Port: SAPERP Client: 200 Destination ERP_00_200)
IDX2: SAPERP - IDOC Type: ZPersonal_Test - Client 200
While collecting these information I found following:
- My BS for SAP XI (client 001) have no logical system name. The technical system
got ERP_00_100, but the BS didn't take it. How to insert it?
But if this is the error, why he said error in SAPERP_200 ?
- Why I have to use two different transaction (we21 in R/3 and IDX1 in XI)
for creating ports. What's the different?
thx
chris

Idoc as sender

Similar Messages

Maybe you are looking for