cancel
Showing results for 
Search instead for 
Did you mean: 

IDOC -FILE ERROR

Former Member
0 Kudos

HI experts,

My scenario is sending IDOC(DEBMAS06) to FILE.

I have configured all the requirements BD54,SM59,WE21,WE20 IN R/3 and SM59,IDX1,IDX2.

WHEN I AM SENDING AN IDOC USING TrCode:BD12, I AM GETTING AN ERROR IN WE02 THAT "EDI: Partner profile inbound not available".

AND IN IDX5 I AM GETTING AN ERROR "No receiver could be determined"

NOTE: IT IS IDOC - FILE SCENARIO

THANKS IN ADVANCE

Accepted Solutions (0)

Answers (6)

Answers (6)

Former Member
0 Kudos

Hi,

The No receiver could be determined problem indicates that IDOC is properly coming to XI and later on its not able to find out the Receiver in Receiver determination.

Please can you check the Receiver Determination, Agreement and Interface Determination parameters.

In ID, You can have Configuration test to identify the exact problem,

ID --> Tools ---> Test Configuration

Here give the IDOC-XML that you will get as sender payload in IDX5 or SXMB_MONI.

It will give you the exact root of the cause.

Thanks

Swarup

Former Member
0 Kudos

HI SWARUP,

AFTER DOING ALL THE STEPS U GUIDED, THE RESULT IS AS FOLLOWS IN ID,

***************************************************************************

Interface Mapping

<Not found>

Runtime error

java.lang.NullPointerException thrown during application mapping com/sap/xi/tf/_CUSTOMER_MM_:

<Trace level="1" type="B">CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV</Trace>... (109 lines)

*******************************************************************************

THANKS IN ADVANCE

Former Member
0 Kudos

hi ALL,

WHAT IS THE ISSUE I AM FACING, AFTER ID TEST CONFIGURATION I AM FACING THIS ERROR.

***************************************

Interface Mapping

<Not found>

Runtime error

java.lang.NullPointerException thrown during application mapping com/sap/xi/tf/_CUSTOMER_MM_:

<Trace level="1" type="B">CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV</Trace>... (109 lines)

Former Member
0 Kudos

Hi,

In this situation the Inbound Interface not found means then Interface mapping also failed.

Better check configuration step by step and do some Test configuration in ID -


Tools---Test configuration

Boopathi

Former Member
0 Kudos

hI MAHESWARI,

I HAVE CHECKED THE CONTROL RECORD OF THE OUTBOUND.

EVERYTHING IS FINE. THE CONTROL RECORD PARAMETERS ARE SAME AS IT WAS FOR CREMAS. BUT I AM FACING PROBLEM WITH DEBMAS.

WHILE SENDING CREMAS I AM NOT GETTING ANY ERROR AND THE IS ONLY ONE LINE IN WE02 WITH STATUS 03.

WHEN I AM SENDING DEBMAS, I AM GETTING TWO LINES WITH FIRST ONE STATUS 03 AND SECOND ONE STATUS 56.

THANKS IN ADVANCE

Former Member
0 Kudos

Hi,

In TC:BD12 check your Output type and logical system name.

Thanks,

Boopathi

Former Member
0 Kudos

hi BHUPATHI,

IN BD12 I AM GIVING THE CORRECT ENTRIES: DEBMAS AND LS

Former Member
0 Kudos

HI ALL,

I HAVE CONFIGURED PARTNAER PROFILES CORRECTLY. I HAVE USED THE SAME PORT IN PARTNER PROFILE THAT I HAVE USED FOR CREMAS. IT IS WORKING FINE AND THIS IS GIVING ERROR.

Former Member
0 Kudos

Hello Shanti,

go to WE02, open ur outbound IDOC.......... then double click on control record

Now go to Partner tab.

Here check Sender & receiver Information.

U may find what u r missing

Thanks,

Mahi

Former Member
0 Kudos

hi shanti,

check ur partner profile....

u have to configure the partner profile w.r.t the rcvr system...

Former Member
0 Kudos

Check partner profile WE20..

Receiver partner profile is creating this error