IDoc (Sender ) to File (Receiver): No receiver could be determined

[Former Member]

Hi, Dear Friends,

I’m implementing scenario Idoc-to-File by means XI.

I try to follow this scenario:

Satish Jaiswal. A Step-by-Step Guide on IDoc-to-File Using Business Service in the XI Integration Directory

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd...

But I have an error.

In sender system I send IDoc by transaction WE19. After that in transaction WE05 I see IDoc with status 03 (successful).

After that in XI system:

1) in transaction WE05 I don't see any IDoc (IDoc is not received by the Receiver (XI Integration Server))

2) in transaction SXMB_MONI I see my message with error.

Status - System error.

In detail view at stage "Receiver Identification" in item "Error" I see: "No receiver could be determined"

Unfortunately I'm not expert in IDoc.

Can you recommend me what I need to verify?

Or advice me link on another full good example with IDoc.

What I need to read for quick start in IDoc understanding.

Thank you in advance.

Natalia Maslova.

[prasanthi_chavala · Accepted solution]

Hi Natalia,

>> <i>1) in transaction WE05 I don't see any IDoc (IDoc is not received by the Receiver (XI Integration Server))</i>

You have to check in IDX5 to see the idocs in XI not in we05.

>> <i>In detail view at stage "Receiver Identification" in item "Error" I see: "No receiver could be determined"</i>

Please verify your receiver determination in the Integration directory is active or not and also verify the sender service,interface name and interface namespace in the payload of moni with the values given in the receiver determination.

Let us know if you have any queries..

Regards,

Prasanthi.

[Former Member · Accepted solution]

Hi Prasanthi,

Thanks, really I see IDocs in XI with the help of IDX5.

Please tell me in detail what I need to verify in SXMB_MONI in order to correct the result ''No receiver could be determined''. Because when I realize Test Configuration in ID everything is good!

Hope for your help!

Natalia.

[Former Member · Accepted solution]

please check your receiver agreement if it is pointing to desired Receiver adapter...

Check as well receiver determination ,verify whether receiver service mentioned properly

[prasanthi_chavala · Accepted solution]

Welcome!!

First take the payload in the inbound message and test it in the ID....under the specific configuration and check whether the RCV determination is configured correctly with same values...i mean check the values of the sender service,interface name and interface namepace in the payload with the values given in the rcv determination...

Regards,

Prasanthi.

[Former Member · Accepted solution]

Hi Prasanthi,

Test in ID is implemented successfully.

I verify settings in ID (Receiver Determination, Interface Determination and Receiver Agreement) - everything is ok!

Now I will try to implement scenario with Business System (before I realized the scenario with Business service).

Natalia.

[Former Member · Accepted solution]

Natalia, it doesn't metter, whether services or systems...

Try following: run once the scenario, check sender service and sender interface as displayed in SXI_MONITOR and compare names to those, which receiver determination is configured for. Are they for sure the same?

What about message & its namespace, does it fullfil the interface description?

Peter

[Former Member · Accepted solution]

Hi Peter,

Really Sender Interface is the same, but Sender Service in SXI_MONITOR is DX7_105, but in ID Servise is bserv_IDoc2File. But why?

[bhavesh_kantilal · Accepted solution]

Natalia,

Look into the error message in MONI.

What is the Sender Business System and the Sender Interface and Namespace.

Is this the values for which you have created the Receiver Determination? I think the Receiver Determination you have created has one of these 3 fields in corect (Sender Service, Interface and Namespace) . Correct the same to refer to the values when the Idoc reaches XI and the details in MONI.

Regards

Bhavesh

[Former Member · Accepted solution]

Natalia, what kind of scenario do you want to configure?

SOAP->RFC, Idoc, HTTP... From what to what?

mhmmm, I see, probably IDoc to File )

Well, you can't create business service just so BS are mostly used with SOAP scenarios, where u can determine sending service. If u use IDoc to FIle and this Idoc is sent from r/3 (or ecc) to XI, XI recognizes sending system (DX7 client 105 in your case) based on SLD settings. But it's ok, it have to be so.

Delete ur old receiver determination and create new one for correct sender system: DX-7. U'll have to change ur interface determination as well.

Peter

Message was edited by:

Peter Jarunek

[Former Member · Accepted solution]

Hi!

I was little confused!

I have began to set scenario with business systems.

Before I really set Demo Examples and use name DX7_105 for business system.

Now I want to use the same system for another task.

My scenario is:

IDoc from system DX7, client 105 (Logical system DX7CLNT105) to File (business system bs_file, Logical system LS16) through XI (system DX7, client 001, Logical system DX7CLNT001).

So I create scenario cs_IDoc2File.

Add two business system: bs_file and DX7_105.

Create Communication Channel for bs_file: cc_IDoc2File.

After that I create new Receiver Determination, Interface Determination and Receiver Agreement (as Sender - DX7_105, as Receiver - bs_file, <b>without any links on XI - system DX7, client 001</b>).

I create IDoc in system DX7, client 105 with transaction WE19.

And specify as Sender:

Port: SAPDX7

Partner No.: DX7CLNT105

Part.Type: LS

And specify as Receiver:

Port: SAPDX7

Partner No.: DX7CLNT001

Part.Type: LS

<b>Nothing about Logical system (LS16) of real receiver - file.

</b>

And my scenario now work - I receive file with required data!!!

Thanks a lot for help!!!

I don't understand how in deep.

Can you recommend me some easy brief material for IDoc understanding?

Thanks a lot!!!

With the best regards,

Natalia.

[Former Member · Accepted solution]

Post ur e-mail.. I'll send u smthng..

Peter

[Former Member · Accepted solution]

Hi Peter,

Thanks a lot!

n.maslova@brig-retail.com.ua

With the best regards from Ukraine to Czechia!

Natalia.

[Former Member · Accepted solution]

U r welcome

Peter

[Former Member · Accepted solution]

Natalia, is ur e-mail ok?

This is an automatically generated Delivery Status Notification

Delivery to the following recipient failed permanently:

n.maslova@brig-retail.com.ua

Technical details of permanent failure:

PERM_FAILURE: DNS Error: Domain name not found

[Former Member · Accepted solution]

Peter,

Really: n.maslova@b-retail.com.ua

My alternative mail: maslova_nd@mail.ru

Excuse me.

Wonderful week-end!

With the best regards,

Natalia.

[Former Member · Accepted solution]

Dear Friends!

I execute my scenario IDoc->PI->File with the help of test transaction we19.

Really I can't understand why I have two rows in we05 during my scenario execution:

the first with status 03 (with my specified message type: FLCUSTOMER_CREATEFROMDATA direction: Outbox) and the second with status 56 (with message type: ALEAUD and direction: Inbox)?

0000000000003008 3 03 @08\QGreen Light: IDoc Successful@ Green LS/ /DX7CLNT001 FLCUSTOMER_CREATEFROMDATA01 14.10.2007 22:37:23 FLCUSTOMER_CREATEFROMDATA Outbox SAPDX7

0000000000003009 3 56 @0A\QRed Light: IDoc Has Errors@ Red Lig LS/ /LS16 ALEAUD01 14.10.2007 22:37:30 ALEAUD Inbox SAPDX7

Could you explain, please?

Thank you in advance,

Natalia.

[bhavesh_kantilal · Accepted solution]

XI has been configured to trigger ALEAUDIT Idoc's back to SAP . These are system acknowledgments from XI to provide the processing status of your Idoc.

If you do not want this you can turn of IDOC acknowledgments

Regards

Bhavesh

[Former Member · Accepted solution]

Hi, Bhavesh,

Thank you very much.

And how can I turn off IDOC acknowledgments?

With the best regards,

Natalia.

[prasanthi_chavala · Accepted solution]

Hi Natalia,

You can turn of IDOC acknowledgments using the table "IDXNOALE" in ur XI system.

Go to Tcode se11 and give the table name IDXNOALE and give the respective entries in the port, client and message type of ur idoc. And activate the table.

Thanks,

Prasanthi.

[Former Member · Accepted solution]

Hi, Prasanthi,

I found such setting:

To Enable Acknowledgement:

• SXMB_ADM ->Integration Engine Configuration ->Specific Configuration ->Add New entry -> Select parameters as:

o Category: RUNTIME

o Parameters: ACK_SYSTEM_FAILURE

o Current Value: 1

in SAP R3 (Idocs) To XI -- Steps Summarized https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&

Is it the same action as in your approach?

Thanks,

Natalia.

[former_member184619 · Accepted solution]

Hi Natalia,

these concepts will be clear with time... for understanding IDOC check these links

http://help.sap.com/saphelp_nw70/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm

http://help.sap.com/saphelp_nw70/helpdata/en/0b/2a6095507d11d18ee90000e8366fc2/frameset.htm

and there use in XI

Configuration steps required for posting IDocs

/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi

IDOC not reaching XI not posted in the receiver SAP Systems

/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133

ALE configuration for pushing IDOC from SAP to XI

/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi

How to Configure the IDOC Adapter

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6f...

IDOC Packaging and mapping Techniques

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38...

Regards,

Sachin

[prasanthi_chavala · Accepted solution]

Hi Natalia,

The steps i have mentioned in my above reply is to block the idocs acknowledgement.

The settings that u have done in sxmb_adm is for system error acknowledgements ie.. Whenever a system error occurs within the Integration Server, a system error acknowledgment is sent back to the sender.

Please refer the below guide "How to handle Ack for idoc"

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50...

Hope it should help u to resolve ur problem with acknowledgements.

Regards,

Prasanthi.

[Former Member]

Hi

Please Check the cache Status using transaction SXI_Cache if the cache is up to date perform the following checks

Please check whether u are entering the proper names while sending messages in XI(RWB)

Check the sender namespace

Check the Sender service name

Check the sender interface nem. keep in mind u dont have to create Sender agreement

If this dont work please recreate ur Receiver Determination and Receiver Agreement.

<b>Please Check whether Ports and Parter profile exsists in the sender system.</b>

Please perform the test on IDOC using transaction WE19

click on start outbound Processing to test ur IDOC.

Thanks

Abhishek

*********Please Reward points if find helpful*************

[Former Member]

HI

1)Please perform the complete cache refresh both in Java and ABAP stacks.

Check the cache status using transaction SXI_Cache

2) Please Check whether u have Created ur Receiver Determnation. No sender Agreement will be Created as IDOC is sent from The application system.

3) While Sending Message from RWB please Check follwoing things

The Name of the sender Business System

The sender interface name

The namespace. This could be one minute error u might be doing

4) In case it dont work Please create Receiver Determination and Receiver Agreement objects again

Thanks

Abhishek

*******Reward Points if find Helpful********

[Former Member]

Dear colleagues,

Thanks a lot for good advices and ideas!

Really the IDoc theme is enough complicated.

I read a lot of materials for my first level understanding!

With the best reqards,

Natalia.

[Former Member]

Hi Natalia,

Use IDX5 transaction to see idocs in XI server.

The error in moni is due to receiver determination.

please check your receiver determination.

regards

Sandeep.

[Former Member]

Hi,

Check your receiver determination.and make sure that you have entered valid interface mapping name there as well as interface.

Regards,

Akshay Jamgaonkar.

• Reward points if find useful.

[Former Member]

Natalia,

>>in transaction WE05 I don't see any IDoc (IDoc is not received by the Receiver (XI Integration Server))

Check in tcode : sm58. must have been stuck in queue.

regards,

Vishal

[Former Member]

Try these steps:

<b>ALE Settings</b>

<b>SAP XI</b>

<b>1) RFC Destination (SM59)</b>

a) Choose create.

b) Specify the name of the RFC destination

c) Select connection type as 3 and save

d) In the technical settings tab enter the details SAP SID/URL and system number#.

e) Enter the Gateway host as same details above SID/URL.

f) Gateway service is 3300+system number#.

g) In the Logon /Security tab, enter the client user & Password details of Destination system.

h) Test the connection and remote logon.

<b>2) Create Port (IDX1)</b>

a) Select create new button

b) Enter the port name as SAP+SID (The starting char should be SAP)

c) Enter the destination client.

d) Enter the RFC Destination created in SAP XI towards other system.

e) Save

<b>3) Load Meta Data for IDOC (IDX2)</b>

a) Create new

b) IDOC Message Type

c) Enter port created in IDX1.

<u><b>SAP R/3</b></u>

<b>1) RFC Destination (SM59)</b>

a) Choose create.

b) Specify the name of the RFC destination

c) Select connection type as 3 and save

d) In the technical settings tab enter the details SAP SID/URL and system number#.

e) Enter the Gateway host as same details above SID/URL.

f) Gateway service is 3300+system number#.

g) In the Logon /Security tab, enter the client user & Password details of Destination system.

h) Test the connection and remote logon.

<b>2) Create Port (We21)</b>

a) First Select Transactional RFC and then click create button

b) Enter the destination port name as SAP+SID (The starting char should be SAP)

c) Enter the destination client.

d) Enter the RFC Destination created in SAP R/3 towards other system.

e) Save

<b>3) Create Partner Profile (WE20)</b>

a) Create New

b) Create the Partner no. name as same the logical system name of the destination system.

c) Select Partner type LS

d) Enter details for Type: US/USER, Agent, and Lang.

e) Click on the + button to select the message type.

f) Select Partner no. and LS which ever create above.

g) Select Message type

h) Select Process code related to the Message type.

I) save.

<u><b>In SLD – System Landscape Directory</b></u>

TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.

Ts for Third Party (Logical system):-

BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.

BS for Third Party (Logical system):-Enter the XI logical system name.

<u><b>In Transaction SALE</b></u>

Define and Assign the logical system name.

Message was edited by:

Raghavesh Reddy

null