PI system as IDOC receiver

Hi all
My scenario is send idoc's from SAP system to external adapter. This adapter can pick up the data from the logical system defined in we20 in SAP PI. then i will have to dowload the idoc in the logical system defined in SAP PI, . Is it possible to define the logical system in SAP PI and post the idoc's directly in SAP PI.
Can i use SAP PI as system as receiver IDoc system ? Did anyone faced these kind of scenario's ?
Any advice is highly appreciated
Thanks
Faizal

hi,
Interesting topic, 1st times that I hear that...
One of the legacy system has to SAP certified adapter , which has to capaablity to connect directly to SAP ERP system and download the IDoc's defined in the logical system LS.
What's the name of this commercial ECC adapter ? maybe you can contact the company who made it to know if this adapter is compatible with PI.
In my mind, this adapter had perhaps an interest when PI was not on the market to authorized a third-party to catch idoc (*), but with PI (since at least 7 years), I think your flow process has to be changed: PI should push Idoc to this third-party (so an easy flow "IDoc -> PI -> IDoc"), and not the opposite: the third-party which check inside PI... (which is I think not possible).
(*) without PI, in ECC, did your third-party pick-up an Idoc ? (so idoc status = 30 (wait)) or did it pick-up a file ? coz in ECC, as you know in WE20 you can decide how idoc is transfer: by an idoc port or by a XML-file or a HTTP...
I'm the feeling your previous flow is only like that: idoc (ECC) -> idoc (certified adapter for non-SAP third-party to receive idoc).
so maybe what you need is only to do: ECC (idoc) -> PI -> Idoc (adapter) to this third party... and then the third-party contine to use its certified adapter to be able to receive an idoc message.
regards.
Mickael
Edited by: Mickael Huchet on Dec 21, 2011 8:52 AM

Similar Messages

Info IDoc received with status 8 in BI but Data available in source system

Hello Experts,
I am loading Budget Period (attributes) into PSA in BI.
Budget Period data Loading Issue : No data available while loading. But source system ie ECC has data in that data source
Data source: 0PU_BDGTID_ATTR
This is full load.
I checked that whether I am making any mistake during data selection. I could not find any issue. Message while loading data into PSA (Yellow Traffic light)
No data available
Diagnosis
The data request was a full update.
In this case, the corresponding table in the source system does not
contain any data.
System Response
Info IDoc received with status 8.
Procedure
Check the data basis in the source system.
Already looked this thread and googled also.
Re: IDoc received with status 8.
Check points:
sm58 - NO issue
BD87 in ECC (RSINFO Idoc status: 03) -sucessful
BD87 in BI (RSINFO Idoc status : 53)
ST22 - NO issue
sm37 - Job is successful (I could see Idoc no in ECC source system in Job log)
I am not sure if I am missing any thing.
Thanks
Rana

Hi all,
I've got exactly the same issue with several extractors. I'm inialising the Master Data in a all new system, in the Quality the loads succeeded but in Prod it failed.
For instance with the basic DataSource "0FUNCT_LOC_TEXT", I've made the following test:
RS3 (R/3) - > 0 data
ST22 -> no short dump
WE05 (Idoc) - > everything is ok
I reactivated the Datasource in R/3 (RSA5) and then deleted it and replicated it in BW but the same issue occured.
Any ideas?
Thanks
jak

How configure a Logical System (XI) as receiver for an Outbound Idoc?

Hi all,
How can I configure a Logical System (XI) as receiver for an Outbound Idoc?
Points will be given,
Regards,
Daniela

hi,
it all depends on what kind of document you need to send to XI
if you want to send some logistic documents (like orders, deliveries etc)
have a look at my book - where you will find step by step guides
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
then you will undestand where to change to get it send via LS
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

MATERIAL LINK TO ONE SAP SYSTEM TO ANOTHER SAP SYSTEM FOR IDOC TRANSFER

Hi Experts,
How the MATERIAL LINK TO ONE SAP SYSTEM TO ANOTHER SAP SYSTEM FOR IDOC TRANSFER?
Scenario : when 2nd system create the invoice,it will create a po in the 1st system.
51 error msg we are getting material does not exists.but the material is available in the receiving plant.
Please suggest

If you say the material master is available in the 1st system (where you create the order), then the material number in the IDOC may not match with the material number in your database.
leading zeros. material number stored as alphanumeris instead of numeric.

Business system for idoc reciver communication channel.

hi gurus,
iam doing one file to idoc scenerio.
for defining reciver idoc adapter ,which type of businees system i required that is configured in SLD.
pls guide me .
warm regards.

Hi
You can use th Buiness system as a receiver for IDOC.
Making sure
1. the LS of the system(R/3) is same in the SLD and it is also reflecting in the adapter specific attributes in the ID.
2. Use the same LS name for the BS pointng to FIle in the SLD.
Complete the IDOC configuration from XI
1. Create the RFC dest from XI to ECC
2. Create the Trfc port and call this RFC dest created..
3. Use this Trfc port in the IDOC receiver
On ECC:
Make sure the Partner Profiles is created properly.
it is suggested to use always the business systems when you deal with IDOC and Proxies.
Edited by: Nisar Khan on Feb 27, 2008 1:31 PM

A problem about IDOC Receiver

Hi, everybody.
This time, I'm developing a IDOC Receiver though the SAPIDocReceiver class. With the dotnet Connector manual from SAP, the receiver side on dotnet is easy to develop. But how to configure the SAP R/3 to send IDOC to the dotnet side, I can't find the clear steps in the manual.
So I searched some material about how to configure IDOC, and hope it will be useful to my work. But most of them mainly focus on how to configure a IDOC transformation between SAP system but not NON-SAP system.
So what I want to ask is IS there some difference with the two configuration, I mean the SAP to SAP one and the SAP to NON-SAP one. I guess the difference should be have. Are the necessary configure step like create a logic system, allocate logical systems to clients and so on also necessary under the NON-SAP case? I think some of the configure actions is different in this two case. Can anyone give me some clear steps or tell me where I can get them?
thanks to all.

Hi,
for testing purposes you can do the following:
(1) via SM59 create the RFC destination for your dotnet application
(2) via WE21 create a trfc-port pointing to the RFC destination created in (1)
(3) via SM30 maintain view V_TBDLS to create a new logical system for your dotnet application for example DOTNET (and maybe for the SAP client you are testing with - here the name could be for example <SID>CLNT<CLIENT>)
(4) via SCC4 assign the logical system to the SAP client (for example <SID>CLNT<CLIENT>) only if not already maintained.
(5) In WE20 create a partner profile for logical system created for the dotnet application in step (3)
(6) In WE20 add outbound parameters for the message type (for example MATMAS) and idoc type (MATMAS03) you want to send. As partner port use the trfc-port of step (2)
(7) In WE19 create an IDoc via basic type (the idoc type used in step (6), for example MATMAS03) and maintain the following fields in the control record EDIDC:
recipient port the port created in step (2)
recipient partner number the logical system name of the dotnet application created in (2)
recipient partner type'LS'
sender port SAP<SID>, where SID is the SAP system id
sender partner number the logical system name the SAP client maintained in step step (4)
sender partner type'LS'
message type the message type used in step (6), for example MATMAS
In the other segments E1* you can fill in whatever you like
Hit the push button "Standard outbound processing"
(8) you can check if the IDoc has been sucessfully created by BD87. If an error has occurred in the receiving application or there is any other error you can also see it here. Maybe the IDoc is not passed to the receiver, then you can process the IDoc also from here.
This is how you can create your test environment. If you want to get the IDoc created form the SAP application it depends on the application how to do that!
Best regards,
Willy

Problems in IDOC receiver communication channel

Hi,
I am trying to build an interface to get data from 3rd party legacy system using JDBC and post the data into ECC using IDOCS. I have IDOC built in ECC, I am able to import the metadata in IDX2 after creating port in IDX1. But after building the whole interface, I dont see the IDOC receiver communication channel which has to post IDOCS in the ECC 6.0 system.
Please assist.
Rgds
Kishore

OK in that case, we are getting the following error in the Message monitoring:
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="OUTBINDING">CO_TXT_OUTBINDING_ERROR</SAP:Code>
<SAP:P1>-BS_AVN_TO_FILE_JDBCSERVER</SAP:P1>
<SAP:P2>-BS_WOAV_IDOC_SENDER,urn:sap-com:document:sap:idoc:messages.ZAVENTITY01.ZENTITY</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>No standard agreement found for , BS_AVN_TO_FILE_JDBCSERVER, , BS_WOAV_IDOC_SENDER, urn:sap-com:document:sap:idoc:messages, ZAVENTITY01.ZENTITY</SAP:AdditionalText>
<SAP:Stack>Problem occurred in receiver agreement for sender -BS_AVN_TO_FILE_JDBCSERVER to receiver -BS_WOAV_IDOC_SENDER,urn:sap-com:document:sap:idoc:messages.ZAVENTITY01.ZENTITY: No standard agreement found for , BS_AVN_TO_FILE_JDBCSERVER, , BS_WOAV_IDOC_SENDER, urn:sap-com:document:sap:idoc:messages, ZAVENTITY01.ZENTITY</SAP:Stack
Please check and assist.
Rgds
Kishore

One IDOC sent but 8 IDOCs received in backend

Hi,
I have a strange problem:
I generate a IDOC at the end of a simple BPM (receive message, send same message, no transformation step). In sxmb_moni, I can see one message (from process engine to IDOC adapter) as expected. When I click on "IDOC"-field in the message row (sxmb_moni), I can see that 8 identical IDOCs (only different IDOC numbers) were generated and in the SAP Backend system, I also receive 8 IDOCs.
This effect sometimes appears, sometimes not. I cannot see why or why not.
Has anyone an idea where I could search to stop this phenomen?
Kind regards,
Torsten

Hi Bhavsh,
no, I'm not using a collect pattern. BPM simple consists of one receive step and one send step.
I don't think that there are any Packaging settings on XI, because it worked already for a long time and we didn't change settings.
Or could Packaging settings in the backend system influence the XI?
But I got a step further: If I double-click on one of these IDOC messages in IDX5, I can see a lot of error status entries (6x status 51, 2x status 54). Is it possible that XI sends an IDOC multiple times if an error occurs?
Kind regards,
Torsten

IDOC Receiver - Unable to convert sender service to ALE

Hi!!!
I am trying to configure the following scenario: FILE - XI - IDoc to R/3.
A business service called IDOC_Demo recovers from the server the file, and after mapping it, it tries to send it to IBP, the R/3 system using a IDOC Receiver comunication channel.
IBP is configured in SLD.
I have in XI System the RFC conexion, and I have define the port via TCODE IDX1.
But it does not work, I am geting the following error:
"Unable to convert sender service IDOC_Demo to an ALE logical system"
I have checked the adapter specific identifiers, but I can not see anything wrong...
I do not know what can I check! Could someone help me?! What can I do?
Thank a lot!!
Araitz.

Thank you very much, but I still get the error message! Of course, I read your blogs Michal before posting the question, and they have been very useful, but still...
In SLD I only have the R/3 system, the name is IBP and the business landscape and the logical system name (I do not know if this could cause a problem).
The connexion is IBP, and it works, and in idx1 I have configured a port, and its name is SAPIBP, using the IBP connexion.
Design I have imported the CREMAS.CREMAS03 IDOC, and I have done a mapping interface, I have disabled the EDI_DC40, and set begin and segment to 1.
Configuration I have created a business service, IDOC_Demo, that has a communication channel, sender, file type.
And I have the IBP service. In adapter specific I can see: logical system IBP, and R/3 System IBP, client 100. If I push the Compare with SLD button, nothing happens what should happen?
IDOC_Demo receives the file, and via an Outbound, async interface, calls IBP, that receives the IDoc using a receiver IDoc type adapter
Now the receiver agreement has information in the header mapping, sender service, IDOC_Demo, receiver service, IBP.
And I do not know why, but it does not work any idea?
Than you!
Araitz.

Idoc Receiver - Header Data does not update

Hi there
I have an Idoc receiver in a scenario where I send a Idoc from a file to the R/3 system. My config is all fine but the Idoc status in we19 shows red. My Header data for the idoc is incorrect. The idoc is WALREQ01. In my Message Mapping Im setting the SDNPOR, SDNPRT, SDNPRN, RCVPOR, RCVPRN to the correct values and the I activate the scenario but in we19 it still shows the incorrect idoc header. It does however change the idoc segment data, just not the header. Is there maybe some other place I have to set the Idoc header data?
Thanx,
Jan

Hi Jan,
From help.sap:
Apply Control Record Values from Payload
If you set the indicator, the conversion of communication parties to the IDoc partner is only possible for systems that are not logical systems.
If you do not set the indicator, all combinations of communication parties and services are handled as services without party.
If the IDoc XML structure contains a control record during outbound processing on the Integration Server, it is rejected and created again by the IDoc adapter. If you want to include additional values in the control record, set the indicator and provide an appropriate mapping for the values. See also: Fields of the IDoc Control Record
http://help.sap.com/saphelp_nw04/helpdata/en/13/95244269625633e10000000a155106/content.htm
Carlos

Stop IDOC receiver channel

Hi folks,
I have what seems like a simple question about IDOC receiver channels, but I have yet to find an elegant answer.
My scenario is a Non-SAP system with an http sender through XI to an R/3 IDOC receiver. My R/3 system will go down for upgrade for a 2 day period but the external system will continue to send messages.
I suspect the IDOCs will queue in XI while R/3 is down because the RFC destination is unreachable, but I would like to stop attempts to send while the R/3 system is down.
I know about availability times for other channels but this technique is not available for IDOC. Is there some way of scheduling the IDOC distribution from XI so that no attempt to send to R/3 is made during the outage ???
Thanks in advance,
Guy

Thanks Karthik,
That's exactly what I did to demonstrate what might happen (used the wrong password). The message went into error, I reset the password and re-processed and all was fine.
It just seems to me that there should be a cleaner way - maybe something in QOut scheduling ??
Thanks,
Guy

Basic IDOC Receiver Issues - help

Hi,
I'm just starting development with the .Net connector and am trying to get the sample IDOC sender and IDOC receiver to work.
We have a remote test system with SAP, connected via a VPN from my site. A SAP Router is used for the GUI connection to SAP and I'm setting the sapDestination.SAPRouterString in the IDOC submit sample.
The IDOC sender is working and I can see the sent IDOCS in the SAP GUI, but I cannot get the IDOC receiver to work.
I have defined a TCP/IP RFC destination, with the IP address and program ID of my program, but the test button on the RFC destination does not work.
Also, after I start the IDOC receiver sample, transaction SMGW (Gateway Monitor) does not list my application.
Please could someone verify what I should configure on the SAP test system and what parameters I should be providing to the sample IDOC receiver program ?
Thanks,
Andrew

Managed to get the correct gateway/host combination and my application now registers !

IDOC Receiver Adapter

Hi,
We have IDOC receiver adapter and data for control record is fed from mapping. For this we have checked the flags " apply control record" and sender receiver from payload.
Recently we copied our QA system from Dev and while testing the Control records are coming from Dev. We have mapping in place whcih looks at the value of receiver and if it does not match with QA, by default it assignment the dev system as receiver
When i am running the interface this mapping is failing and IDOC of QA is getting DEV Control record parameter.
How doe this receiver/sender value is determined in mapping. I checked the SLD and everything looks good.
I cannot test the mapping as while testings is giving 'Test_SenderService' etc which is expected.
Thanks!

We have mapping in place whcih looks at the value of receiver and if it does not match with QA, by default it assignment the dev system as receive
>>> Can you share the UDF?
Are you reading the system name(System.getProperty("SAPSYSTEMNAME")) to determine the environment of the XI system??
Make sure that updated the logical system names in SLD..

IDoc received with status 8

Hi Experts,
Please find the below Error now i am getting.
No data available
Diagnosis
The data request was a full update.
In this case, the corresponding table in the source system does not
contain any data.
System Response
Info IDoc received with status 8.
Procedure
Check the data basis in the source system.
Please provide me solutions ASAP, this issue.
Thanks & Regards,
Bharathi.

Hi Ananda,
I have followed ur post, but same problem i am facing.
The Error below following:
No data available
Diagnosis
The data request was a full update.
In this case, the corresponding table in the source system does not
contain any data.
System Response
Info IDoc received with status 8.
Procedure
Check the data basis in the source system.
Please give me any other solutions, how to resolved this issue.
Thanks in Advance.
Regards,
Bharathi.

SAP Sending IDOCs to DOTNET IDOC Receiver

We are setting up a DOTNET IDOC Receiver to receive IDOC's from our SAP system. While doing a proof of concept today, we tested the case of SAP trying to send the IDOC while the DOTNET IDOC Receiver was not available (I had turned it off). The IDOC status in SAP reported that it had been sent (03). If I turned on the IDOC Receiver (using the sample program), it received the IDOC's with no trouble and the IDOC status in SAP reported sent also.
Questions: Does anyone know why SAP thinks it has sent the IDOC yet when we do a test connection from WE20 it fails?
We need to insure that all IDOC's from SAP have been sent to the IDOC receiver -- any suggestions on how to insure this transfer has taken place?

Hi,
The Spell Checker made some changes in my last response and I have to change the changes:
The status Sent (03) just means that the IDOC has been sent from the ALE/IDOC layer to the communication layer (tRFC). If the IDOC receiver is not available, the sent IDOC will stay in the RFC outbound queue (SM58). If the receiver become available again, the RFC engine will send the IDOC from the tRFC queue to the receiver. After receiving the IDOC, the receiver will in turn send back a confirmation to the tRFC outbound queue. Up to this moment, the status of the IDOC in ALE/IDOC is still 03. Sometime later, a pre-scheduled ABAP report (RBDMOIND)will check the tRFC queue and update the IDOC's status to "Confirmed" (12) if the IDOC has been removed from the tRFC outbound queue. There are also other means can be used to update the final status of the IDOC.
For details about IDOC processing inside SAP, please refer to the related documents.
Hope it somehow helps,
Guangwei

PI system as IDOC receiver

Similar Messages

Maybe you are looking for