Idoc to idoc scenerio

Hi ,
i have created new tecnical system (web as abap) for receiver R3 system.
When i am sending idoc ,It shows error in XI system:
Receiver service cannot be converted into an ALE
logical system
please help

S0004413518 wrote:>
> Yes Sarvesh,
> you are right .Can u give me solution.
See page no 8 point no 9..
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098?quicklink=index&overridelayout=true

Similar Messages

Complete file not displayed in File server(Idoc - XI File scenerio)

Hi,
Am working on Idoc-XI-File scenerio.
The target file is getting generated properly and complete xml n Adapter Monitoring in RWB.
But in the file server(in the directory)only part of the xml is displayed.The size of the file is 82KB.
Is there any configuration need to see the complete file in File Server.

Hi Amit,
This could be due to Network. How far is the file server from XI server?
I suggest putting the file in to local machine or in the same network and check whether it is OK.
- Pinkle

Idoc-XI-Idoc Scenario

Dear All,
I am working on Idoc-XI-Idoc scenario in which I am getting ORDRSP Idoc in input. In one of its segment I am getting value as either A or B. If value is coming as A in input then in the output we want PORDCR101 Idoc but if we have B as value in the source idoc then we should have multiple PORDCR102 Idocs ie for each line item there will be different idocs.
Please guide me on how we can implement BPM in this scenario as required two MM i have created and they are working fine.
Regards,
NJ

Hi,
If value is coming as A in input then in the output we want PORDCR101 Idoc but if we
have B as value in the source idoc then we should have multiple PORDCR102 Idocs ie for
each line item there will be different idocs.
For Source = A:
SourceField----
-----equalS ----ifwithoutElse ----then Constant(blank) ---> PORDCR101
Constant(A)---
Assuming that A in input then in the output we want PORDCR101 Idoc means that you need only one occurence of the IDOC
For Source = B:
SourceField----
-----equalS ----ifwithoutElse ----then LineItem ---> PORDCR102
Constant(B)---
Regards,
ABhishek.

IDOC-Xi-IDOC: CRM - XI -R/3 (No service for system SAPOCC, client ** in ID)

Hi all
I am doing a scenario IDOC - Xi - IDOC where CRM sends an IDOC to R/3 via PI.
I have configured everything in OCC (CRM system), PI and BSC (R/3 system) but when I test it with the transaction WE19 in OCC nothing happens in PI or BSC.
All i can see if a message in SM58 transaction in OCC.
Function Module - IDOC_INBOUND_ASYNCHRONOUS
Target System - XI.
Status Text - No service for system SAPOCC, client *** in Integration Directory.
Could anyone tell me what is the problem.
Your help will be very much appreciated
Regards
Naina

Error message: No service for system SAPCRD client 201 in the integration directory
Cause: There is no service without party in PI server that represents OCC server with client details.
Solution:
We send IDocs from system OCC to PI. In the control record (Segment EDIDC40) of the IDoc, the SNDPOR (SenderPort) field contains the value "SAPCRD". The client of the sending system is determined by the MANDT field of the control record. The system ID and client are then used to determine a service without party of the type (business-system/business-service)
In System Landscape Directory (SLD) create a technical system for OCC system and assign a client for the same. Don't forget to assign an "ALE logical system" to the technical system created. Create a business system for this technical system. Then Business System can be imported under service without party/update the details existing in PI.
Edited by: Rodrigo Alejandro Pertierra on Jun 23, 2010 10:28 AM

Issue in IDOC-XI-IDOC scenario

Hi,
We are facing a strange issue in an IDOC-XI-IDOC scenario. We are using a SAX parser to parse the code here.
The error we are getting in 'sxmb_moni' is
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/abc/def/dev/sapxi/clfmas/Idoc2IdocMapperCLFMAS</SAP:P1>
<SAP:P2>java.lang.RuntimeException</SAP:P2>
<SAP:P3>For input string: ""</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>During the application mapping com/abc/def/dev/sapxi/clfmas/Idoc2IdocMapperCLFMAS a java.lang.RuntimeException was thrown: For input string: ""</SAP:Stack>
The strange thing is, when I restart the message, it gets processed successfully. Also, when I copy the payload, and test the same on a different environment, it gets processed successfully.
Would really appreciate some pointers here!
cheers,
Prashanth

Hi,
This related to mapping error check it once again.Check in Interface mapping Test tab.see the result.check the sxmb_moni and get the source of mapping come back to interfcae mapping and test .
See the below links
Hi I got EXCEPTION_DURING_EXECUTE in RWB->Message Monitoring
I am getting MAPPING EXCEPTION_DURING_EXECUTE
EXCEPTION_DURING_EXECUTE- Error in Mapping. Doubt about IE and AE
EXCEPTION_DURING_EXECUTE
Mapping problem - EXCEPTION_DURING_EXECUTE
ERR: EXCEPTION_DURING_EXECUTE while using FILE CONTENT CONVERSION
Regards
Chilla..

Error in IDOC-XI-IDOC scenario

Hi folks,
Let me explain the issue. This is an IDOC-XI-IDOC scenario. No BPMs involved. SAX parsing used to parse the IDOCs.
We had around 35000 IDOCs coming in from Brazil system, and they are all stuck in SMQ2 (Inbound queue) in XI. The first message of every queue is in SYSFAIL status, with the status text as Problems found during the EXPORT to specified keyin table.
When I try to execute the queue manually, nothing happens, but an error comes at the bottom of the screen, saying Function module does not exist or EXCEPTION raised.
I checked the dump on ST22, and it shows 130 runtime errors yesterday. The name of the runtime error is EXPORT_TABLE_UPDATE_CONFLICT.
In the what happened? part of the dump, it says Error in ABAP application program. The current ABAP program CL_XMS_PERSIST=============CP had to be terminated because one of the statements could not be executed. This is probably due to an error in the ABAP program.
Even SXMB_MONI is not opening (for yesterdays date). When I try to open it, it hangs for a long time, and finally opens an ABAP Runtime Errors page with the runtime error titled as SNAP_NO_NEW_ENTRY and the error short text as Runtime error: Unable to write short dump
Please advise.Thanks a ton!
cheers,
Prashanth

Hello Prashanth,
First of all this is an XI issue and belongs in that forum.
The export problem is typical to situations where your XI DB is out of space/out of table space. Please check with your Basis team.
Function module does not exist or EXCEPTION raised- This message is a standard ABAP RFC message. For an RFC function call to succeed, you need the same RFC function to exist on both systems. However this is probably not the case- it is more likely that you're out of DB space as I already wrote.
Good Luck (don't forget to award points)
Ofer

IDoc missing in IDoc - XI - IDoc scenario

Hello!
The integration scenario is R/3 4.6C (IDoc) -> XI -> (IDoc) R/3 4.6C for DELFOR, ORDERS, ORDCHG, DESADV and ORDRSP.
Now we switched to a new XI development system and the flow is working for all message types besides DELFOR.
WE20 -> New XI Logical System Name -> DELFOR points to the new receiver port which referenced to the correct SM59 destination that is used by all other message types as well.
There is also no error in SM58 in the sending R/3 system and the DELFOR IDocs are in status 12 in WE02 but when I search the IDoc number in IDX5 on XI the IDocs are not there.
Does anybody have an idea where to find the DELFOR IDocs?
Regards, Tanja

Hello!
> IDOC staus if it is sent out from R/3 should be 03 or
> 12?
First it was 03 but as I was not able to find it anywhere I ran a report and the status changed to 12 afterwards.
> if IDOC is coming out of R/3 without any errors( sm58
> no errors) then it should come in the SXMB_MONI in XI
> as it usess th TRFC Port........
Yes, this is also my understanding but it is not in SXMB_MONI nor in IDX5.
> if it is not check the SMQ2 and SMQ! in both XI and
> R/3...it cannot go anywere else (-:
I have checked SMQ2 and SMQ1, the queues are empty in XI and R/3.
Regards, Tanja

Sender port is not picking in PI for idoc to idoc scenario

Hi Guru's,
i am doing idoc to idoc scenario passing through sap pi ,while executing this idoc from client1 is successfully coming to PI, but while going from PI to client2 , i am getting error 51 (company code is defined for LS(logical system) for 1000 (vendor),i checked the configurations for sender idoc from pi ,it is taking a port value which is not present neither in xi nor in r/3 it is MDM interface port value i tried makking the port value constant in PI mapping ,but still same error is comming.
idoc created with partner type LI in source system.i am posting it as LS in receiver system.
Please help me in resolving this error.
Regards,
reddy

Hi,
The error mentioned by you is not related to the port..but its related to the Application ...
IDoc 51 means idoc has been received in R/3 client and when it tries to process it ended in error..
Check with the functional consultant for the error you have received..
HTH
Rajesh

Sender Namespace and Sender Interface in the IDOC to IDOC scenario

My question maybe very basic...
It is SAP IDOC to SAP IDOC scenario.
Lets assume that I have done config in XI for:
 Sender = A,
 Interface = B,
 Namespace = C.
My question is:
Is there a place in the source system or somewhere to point that
when an IDOC e.g. DEBMAS is triggered in the source system,
then the Interface should be B and Namespace should be C in the xml file ?
Cheers
Agnie

Hi Agnieszka,
 Check these threads/blogs from you may get some help:
/people/michal.krawczyk2/blog/2005/11/21/xi-idoc-to-idoc-tunneling--how-fast-and-easy-can-you-get
Idoc-to-idoc scenario
IDoc to IDoc scenario necessary configuration steps
For A-Z help on IDOC, you can refer Michal's book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi IDoc Business Scenarios with SAP XI</a>
Regards,
Subhasha Ranjan

Sender Communication Channel for Integration Scenario IDoc - XI - IDoc?

Hello All,
One general question. I have to configure an IDoc - XI - IDoc Scenario. For this Scenario I have to configure an Receiver Communication Channel (IDoc Adapter) to the Backend System but what about Sending Communication Channel for the Sending R/3 system.
Is the (IDoc) Communication Channel from Sending system to XI required to configured?
Many thanks in advanced!
Jochen

Hi Jochen,
for sending IDOCs from SAP to XI, sender IDOC adapter is not required. when XI will send the IDOC to a SAP system, then receiver IDOC adapter is needed.
Thanks,
Rajeev Gupta

PI 7.1 scenario -- File to File , File to IDOC and IDoc to File Scenario

Hi All,
*I have PI 7.0 . I have in that File to File , File to IDOC and IDoc to File Scenarios*
File to File -- This scenario is working fine.
File to IDOC -- Setting done in PI 7.0 like SM59, IDXI, IDX2 and in R/3 like SALE (logical system)--- This scenario is working fine.
IDoc to File -- Seeting done in R/3 like SALE (Logical system, Distrubtion Model (Port, Partner Profile)) -- This scenario is working fine.
Now I need to move to PI 7.1 -- for File to File , File to IDOC and IDoc to File Scenarios.
Please let me know do I require to make any changes in Design and Configuration and settings in PI 7.1 and R/3 for above scenarios or it will work fine as it is already working for PI 7.0
If changes are required please let me know what changes to do for each scaenario and pls also send blogs for that.
Regards

>
Rickkk wrote:
> Hi,
>
> Idoc metadeta is updated through idx2?
>
> Regards
If there is no metadata maintained for an idoc type, the metadata for that idoc type gets loaded when an idoc of that type is received by PI for the first time. If you are looking at loading metadata of all idoc types before the first run, its really not required. Just make sure that the port is configured properly. Although, there is no harm in preloading the metadata using IDX2.
You need to use IDX2 mandatorily when the the metadata changes and the metadata in ECC and PI is different. In that case, you need to delete metadata for the changed IDoc type and then either you can update the metada through IDX2 or let the system take care of.

IDOC - BPM - IDOC Error --no sender or receiver interface definition found

I have an integration scenario, IDOC - BPM - IDOC. SAP will send ACC_GL_POSTING IDOC to XI, a BPM will start and then the BPM will send an IDOC to another SAP system.
I have read instructions on weblogs:
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
/people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm
The scenario has been successfully tested in the Test Configuration Tool. However, when I try send IDOC from the source, I received the message below in the trace.
<Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_BPE-ENTER_PLSRV">
<Trace level="3" type="T">Processing mode is</Trace>
<Trace level="3" type="T">created BPE proxy for message B45CB0079DFA814BAD22CD1ED64CA6AB</Trace>
<Trace level="1" type="B" name="interface activity determination">
<Trace level="1" type="T">Version 000</Trace>
<Trace level="1" type="T">Message status 000</Trace>
<Trace level="1" type="T">Interface action INIT</Trace>
<Trace level="1" type="T">(must be INIT for a new determination)</Trace>
<Trace level="1" type="T">start CHECK_INTERFACE</Trace>
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface ACC_GL_POSTING.ACC_GL_POSTING01*</Trace>
<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface ACC_GL_POSTING_abs*</Trace>
<Trace level="1" type="T">select interface namespace http://summaryFinancial.sap.dominofoods.com</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="1" type="T">end CHECK_INTERFACE</Trace>
<Trace level="1" type="T">Set interface action DEL into MAST</Trace>
</Trace>
<Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-GETBLOBDATA" />
<Trace level="3" type="T">inserted message into pipeline PE_ADAPTER</Trace>
<Trace level="1" type="Timestamp">2007-04-30T18:32:30Z EST qRFC raised on XBQO$PE_WS91000003</Trace>
</Trace>
Thanks,
Sergio

Rajeev,
The source system in the receiver determination is connected to R3. Other IDOCs are coming across the XI system.
Below is some trace information in the Receiver Determination.
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Start without given receiver</Trace>
<Trace level="2" type="T">Classic Receiver Determination via Rules.</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: - IP_GeneralLedger</Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
<Trace level="2" type="T">Number of Receivers:1</Trace>
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) IP_GeneralLedger ACC_GL_POSTING_abs</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: ACC_GL_POSTING_abs</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
Thanks,
Sergio

Adapter module in PI 7.1 EhP1 for Falt File Idoc to Idoc xml transformation

Hi Experts,
In PI 7.1 (EhP1) there is a java adapter module that can be added to the file adapter that automatically transforms Flat File representation of IDoc to IDoc XML. Can anyone provide the link to this particular module? Tried searching but could not get the specific module name or parameters.
The same conversion can be achieved using a standard SAP provided ABAP mapping but we need to use the module in this case.
Thanks and regards,
Shiladitya

/people/william.li/blog/2009/04/01/how-to-use-user-module-for-conversion-of-idoc-messages-between-flat-and-xml-formats
FYI~~~

IDoc Packaging in IDoc 2 IDoc Scenario

Hi every one,
Can anyone please throw some light on the following:
Use of Idoc packaging in an Idoc2Idoc scenario. I dont have any clue about this.
Reg,

This should be rather straight forward, if you are using XI to pass IDocs from system to system then you actually don't really have to do any mapping. There are some other good discussions on this topic:
idoc to idoc
IDOC packaging
Re: IDOC to IDOC Scenario
This is a good document on the topic:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
You can import the IDoc data types and go about creating the rest of your scenario, usnig the IDoc adapters and ALE
I would definitely also check out this document on configuring the IDoc adapter:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098

SM58 Error For IDOC to IDOC Scenario

Folks,
I am getting an error in SM58 from Sender system ( IDOC-XI-IDOC Scenario ) IDoc adapter inbound channel: Error Error when reading. The Issue is XI is not receiving any IDOCS. Does anybody know what is the problem
Thanks
Manish

Hi Renjith,
I'm facing the same problem the flow is basically form BW to BO.
When they load the data at sender side the idocs are stucked with error status 2:
"Could not find code page for receiving system" in transaction BD87.
Also when I reprocess it is successful. But its is getting stucked in SM58 with errors like:
1)Error in RFC connnection
2)ERROR REQU_D38IW3WD0XGK1DA48DM96N12J PG# 8 in BW
When I execute it throes an error saying "Function Module does not existsor EXCEPTION raised".
Also are many queues stucked in SMQ1 Outbound.
Please help. Many Thanks.

IDOC - XI - IDOC with strange Config , Still working . Please comment !

I am having an running IDOC interface in Production ...
whose SAP XI Config looks strange to me ...
This Interface is IDOC - XI - IDOC
On receiver IDOC adapter ... following Options are checked...
1. APPLY CONTROL VALUE FROM PAYLOAD
2. TAKE SENDER FROM PAYLOAD
3. TAKE RECEIVER FROM PAYLOAD.
So all three Options are checked , But Now the strange thing is in Mapping ...
When I look into the Mapping ...
Sender IDOC to Receiver IDOC
Sender IDOC is different from Receiver IDOC ..
In Control Record ( EDIDC_40)
TABNAME IS MAPPED WITH TABNAME
DIRECT IS MAPPED WITH DIRECT
IDOCTYPE IS MAPPED WITH IDOCTYPPE
MESTYPE IS MAPPED WITH MESTYPE
SNDPRN IS MAPPED WITH CONSTANT HAVING SAP XI SYSTEM RELATED VALUES
SNDPOR IS MAPPED WITH CONSTANT HAVING SAP XI SYSTEM RELATED VALUES
SNDPRT IS MAPPED WITH CONSTANT HAVING SAP XI SYSTEM RELATED VALUES
RCVPOR IS DISABLED
RCVPRN IS DISABLED
So now my Query are :-
1. IF RCVPRN/ RCVPRN is disables ... How interface is still working as TAKE RECEIVER FROM PAYLOAD Option are checked , still that interface is working ... ??????????
2. IF Receiver DOCTYPE / MESTYPE IS MAPPED WITH Sender DOCTYPE / MESTYPE, How it is getting Correct values .. if both Sender and receiver IDOC are Different????
Please make Comments !
Regards
PS

Hi,
IDoc control record will get generated by the XI runtime and there are certain fields which cannot be controlled using mapping for e.g. in your case disabling of RCVPRN ..if you disable this field stil the value will be generated and passed to the receiver system...
To check what exactly idoc values are passing then go to MONI and check there under Response ->IDoc Outbound which displays the control record values passed exactly...
HTH
Rajesh

Idoc to idoc scenerio

Similar Messages

Maybe you are looking for