IDocs not created in file to IDoc scenario

[Former Member]

Hi all

I am trying this file to IDoc scenario.

File picked up successfully and sent to R/3 Backend…But Idoc is not posted…the status records

In /n we05 in R/3 Backend shows that EDI: Partner profile inbound not available

I created/tested all basics like RFC dest, port etc.

File service that I am using is a business service …hence I am specifying a Logical system name in

<b>Adapter specific Identifiers</b> of the file service.

I disabled EDI_DC40 control tag record as IDoc adapter

takes care of it.

So at first I tried the configuration of IDoc comm. Channel by checking the Apply control record values from payload

But SXMB monitor gave an error regarding this control record tag…I guess as we have disabled it so there won’t be any values

for control record in payload (correct me if I am wrong).

So I unchecked the checkbox Apply control record values from payload and monitor showed up as successfully processed.

But in the backend I am getting this error regarding partner profile.

I also tried to use an existing profile (<b>LS</b> type) by modifying it’s inbound parameters to accept <b>CREMAS</b> Idoc.

But the error is as persistent as me

Pls help

Sudhir

[Former Member]

hi johan,

I'm trying to resolve this...

one last thing dos this error...

"Make entry in all req fields" related to Control Record

or data records???

Regards

Sunita

[Former Member]

Data

[Former Member]

The error is caused by incomplete/incorrect data records on the IDoc in R/3.

The function module that processes the IDoc makes use of BDC or Bapi to make changes on your database. The error you get is when the function module doesn't have the information nessesary to complete the BDC or BAPI call. The Control Record was already used to determine the partner profile and from that the function module to use to process the data.

How you can test:

Enter your IDoc number in the IDoc number field in transaction WE19.

Click inbound processing and copy the function name that is given to you. Close that window.

Click the menu item IDoc - Test inbound idoc - inbound function module.

Paste the funtion module name you coppied, select debug and then select foreground and continue.

Debug the function module and try to determine what field is missing on the IDoc data records.

I hope this helps you.

[Former Member]

Sorry guys...

The current error in WE05 tht i am getting is

<b>Make entry in all required fields</b>

[Former Member]

This is good to hear. This means your IDoc was processed using the partner profile. Now you only have to make sure that all the required fields on the idoc is filled with data.

Good Luck.

[Former Member]

Hi

Sender --> LEGACY, maintained in SLD (Logical system).

Receiver--> ENI maintained in SLD with logical sys name M700.

Partner Profile LEGACY maintained in R3.

<b>Following is the IDocOutbound in SXMB monitor in XI</b>.

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Response

-->

- <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">

<SAP:TABNAM>EDI_DC40</SAP:TABNAM>

<SAP:MANDT>100</SAP:MANDT>

<SAP:DOCREL>640</SAP:DOCREL>

<SAP:DOCNUM>0000000000001013</SAP:DOCNUM>

<SAP:DIRECT>2</SAP:DIRECT>

<SAP:IDOCTYP>CREMAS03</SAP:IDOCTYP>

<SAP:CIMTYP />

<SAP:MESTYP>CREMAS</SAP:MESTYP>

<SAP:MESCOD />

<SAP:MESFCT />

<SAP:SNDPOR>SAPAXI</SAP:SNDPOR>

<SAP:SNDPRN>LEGACY</SAP:SNDPRN>

<SAP:SNDPRT>LS</SAP:SNDPRT>

<SAP:SNDPFC />

<SAP:RCVPOR>SAPENI</SAP:RCVPOR>

<SAP:RCVPRN>M700</SAP:RCVPRN>

<SAP:RCVPRT>LS</SAP:RCVPRT>

<SAP:RCVPFC />

<SAP:TEST />

<SAP:SERIAL />

<SAP:EXPRSS />

<SAP:STD />

<SAP:STDVRS />

<SAP:STATUS />

<SAP:OUTMOD />

<SAP:SNDSAD />

<SAP:SNDLAD />

<SAP:RCVSAD />

<SAP:RCVLAD />

<SAP:STDMES />

<SAP:REFINT />

<SAP:REFGRP />

<SAP:REFMES />

<SAP:CREDAT>0000-00-00</SAP:CREDAT>

<SAP:CRETIM>00:00:00</SAP:CRETIM>

<SAP:ARCKEY>DF57A2C0532811D9AD84000F206A031B</SAP:ARCKEY>

</SAP:IDocOutbound>

<b>Control record of IDoc in R3</b>

Tab: Typeinfo

Basic type-->CREMAS03

Message Type-->CREMAS

Tab: Partner

Recipient

Port -->SAPENI

Partner Number--> M700

Partner Type-->LS

Sender

Port -->SAPAXI

Partner Number--> LEGACY

Partner Type-->LS

Pls help

Regards

Sudhir

[Former Member]

I have created a Business sys LEGACY in SLD.

also I am maintaining a partner profile in R3 as LEGACY (LS type)and msg type as CREMAS.

But still I am getting this error in WE05

Partner profile Inbound not available...

Following is the diagnosis of the error...

EDI: Partner profile inbound not available

Message no. E0337

Diagnosis

An inbound partner profile could not be found with the following key:

/LEGACY/LS//CREMAS////

This involves the key fields of table EDP21:

-SNDPRN partner number of sender

-SNDPRT partner type of sender

-SNDPFC partner function of sender

-MESTYP logical message type

-MESCOD logical message code

-MESFCT logical message function

-TEST test flag

Procedure

Please check the inbound partner profiles.

I am unable to resolve this...pls help

Sunita

[Former Member]

Please make sure that the Partner profile matches the control record of the inbound idoc. The sender must be LS LEGACY, the <u>inbound</u> parameters must be CREMAS and on our system and from your error message, the partner function must be blank. The process code must be something like CRE1. Also make sure that the <i>test</i> flag must match the flag on the control record. Also make sure that on the partner function definition under the Classification tab that the partner is A for Active.

If you still can't resolve this problem, please post the control record of the IDoc. You are also welcome to email me any additional information.

My email address is jhschoeman@mweb.co.za

[Former Member]

Your XI IDoc adapter will change some of the fields on the control record of the IDoc that it sends to SAP. To check this, go to transaction BD87 and see what the new value is for the sender field in the control record and make the changes necessary in you partner profiles in WE20.