Sending IDOC to xMII

Hi All,
I would like to send the IDOC (MATMAS & LOIPRO) from SAP to xMII. I have already created the RFC destination in SAP and configured the IDOC Listener in xMII. And I have sent the IDOCs successfully to xMII.
Now I want to proceed with the transaction, which Interface I have to use what is the input I have to give?
can anyone help me in telling the steps to be used in the transaction?
Best Regards,
Ajit Dubal.

Sushma,
The Schema needs to be saved on the xMII Server in:
<DriveLetter>:\Lighthammer\Xacute\ReferenceDocuments\....\IDocSchemaFile.xsd
The ... should correspond with the "Best Practices" directory structure you are using. I recommend namd the schema file after the IDoc type that it represents for example for a MATMAS05 type schema call it MATMAS05.xsd
Then use the schema loader action to point to this file and then Assign the reference XML to the InputXML property of the transaction. This will allow you to see what the IDoc XML sent in from the IDoc listener will look like during runtime. This way you can make sure that the XML Paths are correct.
Hope this helps.
-Sam

Similar Messages

Issue in sending iDoc to xMII server

Hi,
I am trying to send iDoc from R3 to xMII. In this process, when I select the distribution model and try to distribute, I get error which says - Communication error occurred. JCO.Server could not create server function 'MODEL_VIEW_REPLICATE'. Has anyone faced this issue before? Am I missing something? Please help.
Regards,
Harini S

Harini
Probably u hv mislead in ur steps. Pls see the recent thread (Name : <b>R/3 to xMII Posted: Sep 28, 2007 6:10 AM </b>) sent by Mudit Mehra who has done the same (sending IDocs) successfully. U may ask Mudit for the issue if possible.
Regards
Som
Message was edited by:
Som Sarkar

Send IDOC from XMII to SAP

Hi All,
I want to send an IDOC from xMII to SAP. Can anyone suggest me the steps and how to configure in SAP and xMII.
thanks
Manoja

Hi,
What ever Dipankar Saha said is correct.
SAP xMII is used for the purpose of connecting ERP and shop floor.
Usually from R/3 system, you can get info in the form of idoc.(through other forms also you can get data. I hope that you have got the data through idoc)
From shop floor, you get data in the form of B2MML.
If you want some data back to ERP, you can use JCO interface present in the
business logic editor. Use this, to find correct BAPI which can push some data into ERP.
Link the data from B2MML field to BAPI field.
Save this transaction and call this where you want.
Hope this may help you...
Regards,
P.S.Kishore kumar

Process IDOCS in xMII

Hi All,
I am trying to send material and process order data to an external application and it should be through xMII. So, i am trying to use IDOCS for this.
First, I configured my SAP system and xMII so that IDOCS can be sent. Finally, i am able to send IDOC to xMII and can see it in the JCO\Output folder.
Now i want to write a new transaction which reads this IDOC and sends out the data to the external application.
Can any one tell me is my approach correct or there are any other easy options for this ?
Thanks in advance,
Srinivas.

Paul,
I'm sure a lot of times the tone of some respones may seem irritating...mainly because we are irritated with questions on how to do other people's work.
Simple document manipulation is a basic feature of xMII that anyone familiar with the product will know how to configure; especially when we have all the templates for this already defined. A glance through the best practices guide would have already solved this problem. Simply logging on to the SDN and asking people on how to do one's work is unacceptable.
We are not mean people nor do we not care about our community. The exact opposite is true: we care enough to try and filter out all the mundane content so that questions that can help OTHER people as well are more apparent than questions asking what xMII is, how can i use xMII or how i just installed xMII and don't know how to use it.
We are all here to make things better....which is why there are a multitude of sources to LEARN xMII and then come in here asking techincal questions.
I thank you for listening and reading....

Regarding ALE/IDOC in XMII

Can anyone explain me the procedure of using ALE/IDOC in xMII

Hi,
In xMII we don't have IDOC system,we can not send IDOC directly.
We can receive IDOCS in xMII sent from SAP using IDOC Listner.
If you want some data back to ERP, you can use JCO interface.
Use this, to find correct BAPI which can push some data into ERP.
And have a look at this thread
Re: send IDOC from XMII to SAP
Vijaya

Sending Idocs from SAP-R/3 to XI, bundle and map them to one XML-file

Hi All,
We need to send IDoc's (DEBMAS06) from R/3 to XI and bundle and map them to a single xml-file. Please help us with your suggestions on how to proceed using a simple solution (probably need of BPM).
Regards,
Theo

Hi Theo,
there is an example in SAP Library: <a href="http://help.sap.com/saphelp_nw04/helpdata/en/08/16163ff8519a06e10000000a114084/frameset.htm">Collecting and Bundling Messages - One Interface</a>. Plz post us your detailed quetions.
Regards,
Udo

Getting error code 37 while sending IDOC via WE19

Hello experts,
I am facing a very unlikely error which is preventing me from testing my scenario.
I dont have XI quality server and hence I am using my development server as both dev and quality. Hence I need to connect both dev and quality SAP R/3 system to my XI dev system. While I have done all the configurations in my XI and both SAP R/3 systems, its giving me error when i am trying to send IDOC from quality system.
In quality R/3 i have done the following:
1) Created RFC for my XI dev server
2) Created port for this RFC
3) Created partner profile adding all required IDOCS in the outbound parameters
4) Created distribution channel for all the idocs
In XI dev system i have done the following:
1) Created RFC for both dev and quality of R/3
2) Created port for both the RFCs
3) Maintained the IDOC metadata for both the ports
Now when I am pusing IDOC via dev of r/3 (we19) is working fine but when I am doing the same from quality of r/3 its giving me status code of idoc as 37 that says "An error was identified in the control record while adding an IDoc. The sender port SAPQTY_510 is invalid."
But I have created this sender port SAPQTY_510 in my XI dev system and have also maintained the idoc metadata. I dont know why this error is coming.
Can anyone please point out what mistake i have done or if i missed sometig as I am trying to connect 2 r/3 systems to one XI system.
Its really urgent hence your help will be highly apreciated.
Thanks,
Yash

hi yash,
where you created SAPQTY_510 ,it should be created in R/3 Quality RFC destinations.
In XI DEV create port like SAPxxx WHERE xxx is SID of quality system.
actually we are getting confused.
i guess you used same name SAPQTY_510 in quality R/3 and XI DEV .
In error it says sender port SAPQTY_510 is invalid mean port of Source not XI DEV(receiver).
just try to use some other name say SAPXXX_QUA and confirm the error.
when IDOC is sent to XI DEV ,port of XIDEV SAPQTY_510 has nothing to play any role .
just check whether rfc destination of sender port (QUALITY R/3)you used is of type 3.
so please check at which port error is coming.
Thanks & Regards,
Rama Krishna
Edited by: rama krishna talluri on Mar 5, 2008 10:02 AM

Message SR 053 when i send idoc from SAp R/3 4.6C to PI 7

Hi,
I try to send idoc from SAP r/3 4.6C to PI 7. I had made ALE configuration in my sender system ( SAP 4.6C) but idocs are not sent to PI. In SM58 i have message "Name or password is incorrect (repeat logon)". Yet i'm sure that user and password are correct because if i test RFC destination using SM59 , test is OK.
Is somebody can help me ?

Hi,
In R/3 :
my RFC destination is type 3 and point to XI. The port in the partner profile point to this RFC destination. ( all seems good !).
In Xi : i created a port and i load manually idoc in idx2 to be sure that RFC destination was OK. Nothing in IDX5.
When i send idoc MATMAS using BD10 from R3 to Xi i have something very strange: first the message B1 038 "1 master IDocs set up for message type MATMAS" and just after
the XI logon screen appears !! Then message "1 communication IDoc(s) generated for message type MATMAS" and this idoc stay in SM58 with message "Name or password is incorrect (repeat logon)".
Somebody can give me requires caracteristics for XI user used in R/3 RFC destination ?

Partner profile to send Idoc to PI 7.4 system from ECC

Dear Experts ,
Do we need a partner profile to send Idoc to PI 7.4 system from ECC.
or Just Port on TRFC is enough ..?
if i need to create a Partner profile ...how to define a logical system and how Assign Logical System to Client... when there is no client for JAVA only PI system ..?
thanks
Shakif

Hi Mohamed,
You need to create a tRFC port on sending ECC system. The RFC destination selected in this port os the one created for IDOC transfer.
Also you need a logical system, use client 000, i.e. PI1CLNT000.
At last you have to create a partner profile to define the IDOC type used.
Best Regards
Harald

Doubt in Sender IDoc Adapter

Hi Gurus
I have doubts regarding the sender IDoc adapter.The sender IDoc adapter is present by default and we do not create manually. the qos of this is EO by default.
How can we change the QOS of the sender IDoc adapter? do we have to maitain any settings on the R/3 side, please explain??
thanking you

Dear Abhinav,
Check my comments in this forum thread:
[IDOC Serialization|Re: IDOC Serialization in PI]
Regards
Praveen K

Idoc to file scenaro ( sending IDOC as it is to NON-SAP)

Hi Experts,
I am doing idoc to file scenario.
I am having SAP R/3 system with 3 clients(100, 200 & 300), IDOC is comming from SAP R/3( any one of the client)
In this is scenario, I am sending IDOC-XML as it is to the NON-SAP system.
I heard that, i can do in 3 ways. those are
1. Without any repository objects: you can go ahead with No interface mechanism on the target side.
2. Without message type: create a message interface whose message type would be idoc itself
3. With message type: export the IDOC as xsd file and re import the xsd file as an external definition.
If i go without IR objects,Please tell me whether i need to create Interface objects(i.e. DT,MT & MI) & Mapping objects (MM & IM) or not for the reciever.
MY ASSUPTION:
step1: I will import the IDOC into IR.
step2: Directly i will go to the ID without desiging any object in IR ( is it ok).
Is my assuption or correct or not?, please tell me.
So please tell me the entire scenario how to achieve this.
Please help in this issue.

Hi Laxmi
1. Without any repository objects: you can go ahead with No interface mechanism on the target side.
-- Not Possible
2. Without message type: create a message interface whose message type would be idoc itself
-- No need for the Message Interface for IDOC. You will directly import the IDOC and do the Mapping
3. With message type: export the IDOC as xsd file and re import the xsd file as an external definition.
-- This is Possible. you are export the IDOC as XSD File and reimport the same. so there is no difference. If you are going to change the IDOC Structure then this is possible.
Here I am sending some links which are useful for IDOC to File Scenario. Please go thru the links given below..
While doing an IDOC -> XI -> File scenario, The Points to noted are:
1. You dont need a DT, MT or a message interface for the IDOC as it itself acts as the Message Interface.
2. You import the IDOC and use the same in your mapping.
3. In this configuration note that you dont have a sender agreement as you dont have a sender IDOC adapter.
If it is that you wanted to send an IDOC from XI (File to IDOC) , then in this case:
points 1 and 2 will remain, but the 3 will not. You will need a sender agreement for the file and a receiver agreement for the IDOC.
IDOC -> File scenario ref:
IDoc-XI-File scenario
File -> IDOC ref:
File to IDOC
To be able to trigger your IDOC from the SAP ISU system, you will have to set the partner profile in we20. Select your Business System (mostly under Logical system) and then create Outbound entries for whichever IDOC you want to trigger.
You define your basic type also in your partner profile settings, Please go thru the following links to get a better idea about partner profile:
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b833243d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7cd343d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/32/692037b1f10709e10000009b38f839/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5e/b8f8bf356dc84096e4fedc2cd71426/frameset.htm
Also, I would suggest that you go through this blog by michal if any issue arises,
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
I hope this answers your query.
Award the POINTS if it is useful **
Cheers
Vasu

Need of ALE settings to connect 4.7 to 5.0 to send IDOc

Hi
I have two servers 4.7 and 5.0 .
Now I want to send Idoc from 4.7 client 800 to 5.0 client 800.
Can anybody provide me the steps to create ALE settings and to send IDOC.
creating logical systems in source and destination and creating RFC and partner profile and port.
Thanks in Advance

Hi,
For ALE senerion for sending the material from one system there are three methods are there
1) Executable program only for Master Data
2) Message type Master As well as Transcation Data
2) Change Pointers Master As well as Transcation Data
1) SCC4 Create the Logical systems.
ALG800 for 800
ALG810 for 810
2) Assign the Logical systems to the Client using SCC4> selecting the Client and Double click> maintain the logical system name which you had created in the step 1
3) Main RFC destination SM59---> use the same Logical system name as the Logical system name
log on to 800 and goto SM59 --> create
ALG810 --> provide the 810 logon details and save
test with remote logon...it will open the client 810..
logon to client 810 goto--> sm59 --> create
   ALG800 --> provide the 800 logon details and save
test with remote logon...it will open the client 800..
logon to 800 goto BD64 maintain CDM-->change
create CDM
ZCDM01 CDM
ALG800 sender
ALG810 Reciever
MATMAS Message type
ZCDM01 CDM
ALG810 sender
ALG800 Reciever
MATMAS Message type
save
Environment ---> Generate partner porfile.
edit --> distribute CDM
Logon to 810
goto BD64---> select CDM ZCDM01 ---> Environment ---> Generate Pratner Profile.
Edit --> distribute.
ALE Setting are compleated.
Logon to sender system 800.
create material in MM01
Material   10001
Industry sector mechanical engee
Material Type finished
enter
Base Unit of Measure KG
Weight unit         KG
Gross Weight         100
Net Weight           100
save
Execute BD10 in client 800
Check the Idoc in WE05.
Log on to Client 810
Execute BD11
check the IDOC status in WE05
goto MM03 provide the material numer enter...
Thansk,
Nelson

Sending IDoc from Non-SAP system to XI

Dear all,
We have a non sap system which needs to send IDoc to XI, Please could you answer my following four questions
1. What should be the values for the following fields in the IDoc control record
e.g. RCVPRN = <logical system name of XI>
SNDPOR
SNDPRT
SNDPRN
RCVPRT
RCVPOR
2. How does XI decide which port(idx1) to be used when it receives an idoc
3. The third party system is a non sap one, so it does not have a client no, so I would assume, I need to use another SAP system as a meta data provider, in that case, how would i tell XI to use that port when it receives IDocs from the non-SAP system ?
4. In what step does XI use the logical system name of the Business system(in SLD)?
Thanks in advance
cheers
danus
Edited by: Chidambaram Danus on Jan 25, 2008 2:21 PM

Hi
there is bit wrong interpretation of the statement
If the sender system is a non-SAP system, the sender service is identified from the logical system name of the sender port.
If the sender system is nonSAP it indicates taht the data is coming to XI from non sap systems such as file, database, webservice etc. to XI and from XI it will pass to sap as IDOC inbound.
For this you need to create the logical system in SAP (receiver) and pass on that value to IDOC header.
You could maintain it in the Business service used for Sender system (nonSAP). here it will be available in the tabs ---> History.
note : IDOC is the concept of data container in SAP, you will not be able to have the IDOCs in non sap systems...
Thanks
Swarup
Edited by: Swarup Sawant on Jan 25, 2008 2:54 PM

Error in Sending IDoc to XI

Hi Gurus,
We are not being able to send Idocs from one of our Back-end SAP system. The Idoc status in we05 is successful but it doesn't reach XI. So we checked in SM58 in the Back-end R/3 system and there it shows the error:
No Service For System SAP*** , Client *** in Integration Directory
We tried almost every possible setup
-The System is defined in SLD and has the logical system name.
-The Adapter Specific Identifiers are correct for the corresponding business system in ID
-The RFC destination in R/3 system is defined.
- Read through other similar threads in SDN about the similar problem.
Do anyone have a more definite solution for this particular problem? The other R/3 systems are connected to XI system and all IDocs from those systems are arriving at XI.
Waiting for your valuable advices!
Regards,
Suddha

Hi All,
We had eventually found the solution to this problem we were facing in sending IDoc, though I couldn't manage to update the thread with the solution. I think this would be a very helpful information for those who face similar problems.
Let me describe the scenario first briefly,
We are sending an IDoc (Idoc extension), from SAP system to XI and then send the XML payload as mail attachment to the receiver via receiver mail adapter. Since this is a cross company transaction, hence we have configured the scenario as a B2B in ID, which means we use Parties for both the sender and receiver.
Now in the ID we had done all necessary configurations and used parties and services under Party. For the sender SAP system we assigned a Business System to Sender Partner, configured the Party Alternative Identifiers correctly. The ports were created in IDX1.
On the other hand the SAP system was also configured successfully - including Partner Profile, Distribution List, RFC destinations and ports.
In SLD we created Business System for the SAP system and in ID the Business System under party had the correct logical system name as Adapter Specific Identifiers.
But after all these, the IDoc was not arriving at XI, though in R/3 the status of the IDoc was 03 in we02. When we checked in sm58 in R/3, it showed us the error message that "No Service For System SAP*** , Client *** in Integration Directory".
The cause to this problem was:
We created (assigned from SLD) Business System only under Party (Sender), as this was a B2B scenario, and didn't create (assign) a Business System without Party, as we didn't need one at all in the scenario configuration. And this the reason behind this error. When an Idoc arrives at XI, before the Inbound IDoc adapter converts the IDoc to IDoc XML using IDoc metadata............it checks in Configuarion to see if any Service without Party (Busniess System) is defined for the Sender SAP System and Client (The SNDPOR and MANDT field values from IDoc Control header are taken as the SAP SID and Client). If it finds one it accepts the IDoc and starts the Normalization (Sender Party, Service......in the message header) and IDoc to XML conversion. If it cannot find an Service without Party in ID for sender system, it rejects the Idoc with the error message that we saw in sm58 in backend R/3 system.
In this step the Service under Party doesn't help, because at this point the Inbound IDoc adapter can not deterimine the sender party.
Hence for sending an IDoc from an SAP system to XI, we need to have an Service Without Party in ID, whether or not we require it in our actual Scenario Configuration, which is ofcourse not a case for the Reverse Scenario, ie Sending an IDoc into SAP system from XI.
This is the similar with BC adapter as well. I was already aware about this behaviour of BC adapter from my past experience and this actually helped to troubleshoot this IDoc adapter problem.
This was ofcourse a useful and new learning for me and hope would be helpful to others as well. Let me know if anyone has any doubts on this.
Regards,
Suddha
Edited by: Suddhasatta Guha on Aug 28, 2008 1:03 PM

Steps required for Sender IDOC adapter PI 7.0

Hi all,
My basis guy has installed SAP EHP1 for PI7.0 for handling the idoc packaging(sending idocs in packs)...
Please can any one let me know the further settings required in PI after it has been installed...
and even when i open the sender IDOC in comminication channel in ID i am able to see only 3 options
Transport prtocol, message protocol,Adapter engine...
But i am not able to see the other fields...
Can any one help me...
Thanks and Regards,
sridhar

Hi Michael,
Thanks for your reply..
I searched for the docs in many ways.. but couldnt find proper information regarding the IDOC packaging with sender IDOC adapter and steps required...
Could you please let me know if i can get the book in Singapore since our project, because almost 90% interfaces are related to IDOC...
And request you if you can share me the steps required in PI to confirgure IDOC packaging for EHP1...
Regards,
Sridhar Reddy
Edited by: sridhar reddy kondam on Jun 15, 2009 4:35 AM

Sending IDOC to xMII

Similar Messages

Maybe you are looking for