Solved: file to IDOC error...

I am doing a file to IDOC scenario..

here everything is fine....flat file is sent and is picked up by XI.

at Sender side it shows successfull....but at receiver side it shows red flag...

what would be the cause....

i have been testing the same file from yesterday.....everything went well till yesterday afternoon.....from then it showing a red flag at the receiver....

what would be the problem....

SAP Managed Tags:
SAP Process Integration

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (1)

Hi,

>i have been testing the same file from yesterday.....everything went well till yesterday afternoon.....from then it showing a red flag at the receiver....

Check the flat file which you sending meets the requirement. Data might be issue, in moni go for Trace and look in detail & If you are using Lookup check that one too

Regards

Agasthuri Doss

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi ,

i have been sending the same flat file

Hi,

1) Are you using Cross reference / look up

2) Did you changed FCC in File Adapter / Message Mapping, Check the History

Regards

Agasthuri Doss

no FCC....no lookups....

simple file to IDOC....

and can some guide me in getting the trace.....i am not able to get the trace.

I mean after getting into SXI_monitor,

giving the required parameters then execute that...

i will be in the screen for number of mnoitored XML messages....after that..how to get the trace...can some one help me in by providing step by step...

>>.how to get the trace

double click the failed message,it will take you to screen where on the left side you will see trace under Response->SOAP Header->trace.

If the message failed before message mapping then goto Inbound message->SOAP Header->Trace

Edited by: Aamir Suhail on Jun 6, 2008 11:51 AM

This is the trace for the response...

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

- <!-- Response

-->

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

<Trace level="1" type="T">Party normalization: sender</Trace>

<Trace level="1" type="T">Sender scheme external = XIParty</Trace>

<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>;

<Trace level="1" type="T">Sender party external =</Trace>

<Trace level="1" type="T">Sender party normalized =</Trace>

<Trace level="1" type="T">Party normalization: receiver</Trace>

<Trace level="1" type="T">Receiver scheme external =</Trace>

<Trace level="1" type="T">Receiver agency external =</Trace>

<Trace level="1" type="T">Receiver party external =</Trace>

<Trace level="1" type="T">Receiver party normalized =</Trace>

- <!-- ************************************

-->

<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>

<Trace level="1" type="T">COMMIT is done by XMB !</Trace>

- <!-- ************************************

-->

- <!-- ************************************

-->

<Trace level="1" type="T">XMB entry processing</Trace>

<Trace level="1" type="T">system-ID = DX1</Trace>

<Trace level="1" type="T">client = 220</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = PIAFUSER</Trace>

- <!-- ************************************

-->

<Trace level="1" type="T">Message-GUID = 771D18AAF03846A724B6978019BD72FE</Trace>

<Trace level="1" type="T">PLNAME = CENTRAL</Trace>

- <!-- ************************************

-->

<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>

<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>

<Trace level="1" type="T">Queue name : XBTI0005</Trace>

<Trace level="1" type="T">Generated prefixed queue name = XBTI0005</Trace>

<Trace level="1" type="T">Schedule message in qRFC environment</Trace>

<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>

<Trace level="1" type="T">----

</Trace>

<Trace level="1" type="T">Going to persist message</Trace>

<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>

<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>

<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>

<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>

<Trace level="1" type="T">----

</Trace>

- <!-- ************************************

-->

<Trace level="1" type="T">--start sender interface action determination</Trace>

<Trace level="1" type="T">select interface FFEG_PYDeduction_SENDER_ASYNC*</Trace>

<Trace level="1" type="T">select interface namespace URN:COM.UPRR.PYDeduction.LGCY_FFEG_BS</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">select interface *</Trace>

<Trace level="1" type="T">select interface namespace</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">Note: the following trace entry is written delayed (after read from persist)</Trace>

- <!-- ************************************

-->

<Trace level="1" type="T">----

</Trace>

<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>

<Trace level="1" type="T">system-ID = DX1</Trace>

<Trace level="1" type="T">client = 220</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = PIAFUSER</Trace>

<Trace level="1" type="T">----

</Trace>

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC">

<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>

<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>

- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">

<Trace level="1" type="T">Cache Content is up to date</Trace>

</Trace>

- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">

<Trace level="1" type="T">Cache Content is up to date</Trace>

</Trace>

- <!-- ************************************

-->

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

- <!-- ************************************

-->

<Trace level="1" type="T">number of receivers: 1</Trace>

<Trace level="1" type="T">Single-receiver split case</Trace>

<Trace level="1" type="T">Post-split internal queue name = XBTO2___0002</Trace>

<Trace level="1" type="T">----

</Trace>

<Trace level="1" type="T">Persisting single message for post-split handling</Trace>

<Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>

<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>

<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>

<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>

<Trace level="1" type="T">----

</Trace>

- <!-- ************************************

-->

<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>

- <!-- ************************************

-->

<Trace level="1" type="T">----

</Trace>

<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>

<Trace level="1" type="T">system-ID = DX1</Trace>

<Trace level="1" type="T">client = 220</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = PIAFUSER</Trace>

<Trace level="1" type="T">----

</Trace>

- <!-- ************************************

-->

<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>

<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>

<Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>

- <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

- <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">

<Trace level="1" type="T">Interface Mapping URN:COM.UPRR.PYDeduction.LGCY_FFEG_BS FFEG_ECC_PYDeduction_CREATE</Trace>

<Trace level="1" type="T">ContentType application/xml</Trace>

</Trace>

- <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

</Trace>

- <Trace level="1" type="B" name="PLSRV_CALL_ADAPTER">

- <!-- ************************************

-->

- <!-- ************************************

-->

<Trace level="1" type="T">----

</Trace>

<Trace level="1" type="T">---- Outbound IDoc-Adapter -

</Trace>

<Trace level="1" type="T">----

</Trace>

- <Trace level="1" type="B" name="CL_IDX_IDOC_SERVICE-ENTER_PLSRV">

<Trace level="1" type="T">Pipeline Service ID: PLSRV_CALL_ADAPTER</Trace>

<Trace level="1" type="T">Get Information from IS-Header Objekt</Trace>

<Trace level="1" type="T">Get Information from SD-IDoc-Endpoint</Trace>

<Trace level="1" type="T">Sender and Receiver after Header-Mapping</Trace>

<Trace level="1" type="T">Sender service LGCY_FFEG_BS</Trace>

<Trace level="1" type="T">Receiver service CoreFin_DE1_209_BS</Trace>

<Trace level="1" type="T">Get IDoc-XML from the Resource Objekt</Trace>

- <Trace level="1" type="B" name="IDX_XML_TO_IDOC">

<Trace level="1" type="T">Parse XML-BODY</Trace>

<Trace level="1" type="T">Get the Metadata for port SAPDE1</Trace>

<Trace level="1" type="T">Convert one IDoc</Trace>

<Trace level="1" type="T">Warning: IDoc does not contain control-record</Trace>

<Trace level="1" type="T">Make Syntax check of actual Idoc</Trace>

<Trace level="1" type="T">Convert Segment-Types to Segment-Definitions</Trace>

</Trace>

<Trace level="1" type="T">Call Outbound IDoc-Adapter</Trace>

- <Trace level="1" type="B" name="IDX_OUTBOUND_XMB">

<Trace level="1" type="T">FM IDOC_INBOUND_ASYNCHRONOUS with RFCDEST= DE1</Trace>

</Trace>

</Trace>

<Trace level="1" type="T">----

</Trace>

<Trace level="1" type="T">Async processing completed OK.</Trace>

<Trace level="1" type="T">system-ID = DX1</Trace>

<Trace level="1" type="T">client = 220</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = PIAFUSER</Trace>

<Trace level="1" type="T">----

</Trace>

- <!-- ************************************

-->

</SAP:Trace>

any idea guys

Hi !

As you can see from the trace

<Trace level="1" type="T">Warning: IDoc does not contain control-record</Trace>

the Idoc is not created since "IDoc does not contain control-record"

So check whether u r giving some values to the control record of the Idoc from the sender's payload

(or)

In the receiver idoc adapter check the option "Apply control Record Values from payload" and see whether it is working now

Edited by: Laawanya Danasekaran on Jun 7, 2008 8:45 AM

Hi,

Adding to Laawanya,

Reload the metadata & Receiver determination & Interface determination refresh it.

Regards

Agasthuri Doss

Answers (4)

Hi,

it would be great if you copy and past the trace from the sxi_monitor, so we can

manage the error.

Thanks

Emiliano

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

do u mean the payload....or ?

I mean the trace in the sxi_monitor:

go to sxi_monitor-->open the error msg --> on the left side click on "Trace"

Hey,

Check your setting in SM59, idx1 and idx2 on the XI side.

Check whether the remote login is successful or not(SM59)

refer to this link

/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi

Note:- 940313

regards,

Milan

check the pipeline steps in sxmb_moni

Pipeline steps are (Source message ->RD->ID->MS->MM>TR->CA-> Target message)

RD -> Receiver Determination

ID -> Interface Determination

MS -> Message split

MM -> Message mapping

TR -> Technical routing

CA -> Call adapter

Using the XI pipeline steps we can find out the source payload and the payload after the mapping conversion. It also explains as to what happens in each pipeline step during runtime.

regards

chandra

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

how to check these pipeline steps in sxmb_moni....

check the suitable error category and proceed:

File-To-IDOC scenario in XI. I felt I can share some of my experiences in this regard. Hope this blog helps.

(1) Error scenario - File is not getting picked up from the source

Check if the given source file location path and source file name is same as what is specified in sender communication channel. Then check if the Adapter status is Active in the sender file communication channel.

Using the below URL we can monitor the sender file communication channel status (File Adapter) in Adapter Monitoring.

http://<hostname>:<J2EE Stack Portnumber>/mdt/amtServlet

If the sender communication channel shows processed successfully in adapter monitoring, then check point 4 below.

(ii) Error scenario - File is picked successfully from the given source path but is not getting converted to xml format, The adapter monitoring shows success but no messages in SXMB_MONI.. (This occurs when the file is a fixed length or comma delimited or tab delimited).

The problem could be that file structure lengths and datatype structure lengths in IR are not same. If both structures are same and still if the file is not getting converted into xml format then the problem could be in File Content Conversion (FCC). FCC parameters might not be configured correctly in sender file communication channel.

(2) Error Scenario - Cache is not getting refreshed

Cache needs to be refreshed. To refresh the cache, Tcode SXI_CACHE, XI Runtime Cache -> Start Complete cache refresh.

Check the Cache Notification in IR and ID. Status of the objects should be "Success".

To achieve this,

Go to IR, Environment -> Cache Notification

Status of the objects should be "Success" .

Go to ID, Environment -> Cache Notification

Status of the objects should be "Success" .

Keys:

IR - Integration Repository

ID - Integration Directory

(3) Error Scenario - Message is not appearing in Tcode SXMB_MONI

If there is no message in SXMB_MONI, do the below setting at Tcode SXMB_ADM.

Execute the Integration Engine Configuration

Check if role of business system has been configured to u2018Integration Serveru2019 or not. If it is not ,then configure it to u2018Integration Serveru2019.

(4) If message appeared in Tcode SXMB_MONI, check the XI Pipeline steps.

By default Pipeline steps do not appear in the Tcode SXMB_MONI. To get the Pipeline steps in SXMB_MONI we need to do following external setting in Tcode SXMB_ADM (Usually this setting will be done by an XI technology consultant, but its always better to know the steps)

Category: RUNTIME, Parameter: LOGGING, Current Value: 1

After entering the values, save the settings and test the scenario. Now we can view the pipeline steps in SXMB_MONI for an XML Message.

Using the XI pipeline steps we can find out the source payload and the payload after the mapping conversion. It also explains as to what happens in each pipeline step during runtime.

(5) Error Scenario - ATTRIBUTE_INV_SND_SERV or unable to convert sender service to an ALE logical system name.

The problem occurs when sender and receiver business system or business service does not have a logical system name.

ID - Integration Directory

Posting the IDOC'S into SAP R/3 System, sender and receiver business system or business service requires the logical system name. If the business system (Web As ABAP) does not have the logical system name, then add the logical system for business system. Please see below screen shot.

If business system type = Web AS ABAP, then add the Logical system in Technical System level and Save.

If business system type = Third-Party, then add the logical system in business system level and Save.

If the business service does not have the logical system name in ID, it needs to be configured as follows.

Check the below screen shot which shows how to add the logical system for business service.

Go to ID and click the Business service -> Services -> Adapter Specific Identifiers. Enter the logical system name and Save.

Apply and activate.

(6) Error Category - CO_TXT_OUTBINDING_NOT_FOUND

The problem is in Technical routing.

Check whether the receiver determination and interface determination objects are active in change lists tab. If they are not active, activate the objects.

Also check the if the receiver determination and interface determination objects are referenced to the same namespace or not. Sender and receiver interface objects should always refer to the same Namespace.

(7) Error Scenario - ATTRIBUTE_IDOC_METADATA

Check the receiver communication channel (Created using IDOC adapter). In this communication channel check if the two mandatory parameters are passed correctly.

Following is further info on those two mandatory parameters.

(i)Check if the RFC destination which is created in XI to connect the target SAP R/3 system is working fine.

(ii)Check if the port that has been created in XI is in the form SAP<SID of R/3 system>. If not, create in the form of SAP<SID of R/3 system>. To this port, specify the above RFC Destination.

(8) Error Scenario - IDOC not yet created in target SAP R/3 system.

Go to R/3 system and check at Tcode WE05 if the IDOC has been created successfully. If error is u2018"Partner profile not configured" check point 9.

Suppose IDOC did not get created at R/3 end and all the pipeline steps were successful in SXMB_MONI, then go to Tcode : IDX5 in XI and click on Transaction ID field and check the status description which explains the problem.

(9) Error Scenario - Partner profile not configured.

Go to Tcode WE20 in R/3 system and check if the partner profile has been configured correctly and is filled with the inbound parameters.

regards

chandra

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Log onto the system where the IDOC is being sent to. use tranasaction we02. Find the IDOC and there should be some error associated with it..

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

its not at all reaching there....i dont see any IDOCS in the receiver system

Initially re-check your R/3 configuration settings like sm59, we20,we21.

And check queues smq1 and smq2...

check sxmb_moni in R/3 system...Finally...check we02 on R/3 system...

-Esha

check all the configuration settings in R/3

Connection between sap xi and SAP r/3 4.6c

Check in ST22 if you received some dump

regards

chandra

hi chandra,

i do see one dump for the user PIRWUSER..what is that i should do now....

What's the error associated with the Red Flag...

its timeout error.

pls go thru the below blogs

XI: Timeouts, timeouts, timeouts....

/people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts

*How to: Resolving Progression time error while activating XI Development Objects. *

https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1674 [original link is broken] [original link is broken] [original link is broken]

regards

chandra

how to delete the dumps...

Ask a Question

Top Q&A Solution Author

User

Count

file to IDOC error...

Accepted Solutions (1)

Accepted Solutions (1)

Answers (4)

Answers (4)

Re: Are there plans to update the Spring framework...

Vendor Invoice Screen 'Payment' tab screen field '...

I have data like Date, Net, Gross. I want to deriv...

Re: Re Generate Co files and data files

Re: error during install SAP S/4HANA Server 2022