XI - Idoc scenario

[Former Member]

Hi,

We use File <-> XI -> IDoc scenario.

XI picks the Text file from the fileserver & we have BPM to do the intial validations.

If the validation fails, then the file is again sent back to the fileserver by attaching a trailer record to the file.

If the validation is success, then the file is posted as an IDoc.

At the moment, the IDoc part works fine.

In the BPM if the validations fail, then the file is not sent back properly to the fileserver.

I have checked the graphical log & the status is "Step completed successfully"

In the SXMB_MONI also we didn't get any status in the status column.

The interface that we have used for sending the file has the following Definition attributes:

Definition Attributes:

Category - Abstract

Mode - Asynchronous

Is it possible to create a file using the above interface?

could you kindly suggest a solution?

Kind regards,

KA

[bhavesh_kantilal · Accepted solution]

Hi,

Check the Receievr File adapter in Adapter Monitoring.

Also check Message Monitoring.

Maybe there is some error in your Content Conversion.

Regards

Bhavesh

[Former Member · Accepted solution]

Hi,

Thanx for replying

we have checked the receiver file adapter monitoring,message monitoring and content conversion.No error found in the above monitoring and content conversion.

The interface that we have used for sending the file has the following Definition attributes:

Definition Attributes:

Category - Abstract

Mode - Asynchronous

Is it possible to create a file using the interface with above definition?

Kind Regards,

KA

[Former Member · Accepted solution]

Hi Maran,

For receiver File you need, inbound interface and not Abstract interface. Abstract interface are only for BPMs.

Regards,

Jai Shankar

[Former Member · Accepted solution]

Hi,

We are sending the file from the BPM, so should i use another interface after the BPM to send the file out?

Kind Regards,

KA

[Former Member · Accepted solution]

Yes. The sender interface will be your Abstract interface. But the file receiver interface will be an inbound interface.

Regards,

Jai Shankar

[Former Member · Accepted solution]

In SXMB_MONI, we get the following exception:

name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
  <Trace level="2" type="T">old values in cache (no lock found) - start reading from SLD</Trace> 
  <Trace level="2" type="T">Adapter Framework(s) found</Trace> 
  <Trace level="1" type="T">exception while reading from SLD:Property 
                                        sap_xiadapterservice.adapterType does not exist</Trace>

Is there any configuration in the Integration directory to refresh the cache dynamically?

Regards

KA

[prabhu_s2 · Accepted solution]

i think some issue with ur bpm design and how u used it in the id...maybe u have configured the is right but havent done the id seetings properly. if u can send a detailed view on the items used we can troubleshoot the error

[Former Member · Accepted solution]

i checked the adapter monitor in the runtime workbench & found the reason for the error in the File adapter.

changed the content conversion parameters & now the output file is created successfully.

Thanks again for your valuable replies.

[prabhu_s2]

also u can check the workflow log in PE...maybe some issues in recv.coom channel. u can check its log in rwb