Help: Error in BPM (FILE to FILE)

[Former Member]

Hi All,

I am trying out a file to file scenario using BPM and i'm following the blog "/people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm

<b>But after the file gets picked up, the process fails in the call adapter step</b>.

I see the mapping is done properly.

How to solve the issue?

Regards,

Ajay.

Message was edited by: AKVKN

[Former Member]

Hi,

I don't have access for the transaction PFWS.

And I see only one entry in SXMB_MONI i.e for Sender to XI (Integration Process). There is no entry for XI to receiver ( I think it faild over there ).

Also, in SXMB_MONI there is a column (tab) called C, i.e followed by he column Outbound (Status,Ack.Status,...Inbound,<b>Outbound,C</b> ), which shows RED flag (Message has error status on outbound side).

Any help?

Thanks,

AKVKN.

Message was edited by: AKVKN

[sridharreddy_kondam]

Hi Ajay,

I have also done the same scenario which was working fine...

Check the steps and compare with urs, from below and sure it will help u out..

5) Create Message Interface : We have to create 3 message interfaces,

a. MI_File_to_BPM_OB --> Outbound, Asynchronous

b. MI_File_to_BPM_ABS--> Abstract, Asynchronous ( Since Integration Process will not understand Outbound/Inbound interfaces so abstract interface is used )

c. MI_File_to_BPM_IB --> Inbound, Asynchronous.( used in Receiving side )

6) Create Message Mapping: One to One as both structures are same.

7) Create Interface Mapping

IM_File_to_BPM --> Source Interface: MI_File_to_BPM_OB

Target Interface: MI_File_to_BPM_ABS

8) Create Integration Process Right click new

IP_File_to_File -->

a) Create Container Element ( To process message in BPM we use container elements Bcz its not possible to use abstract interfaces directly )

ReceiverMsg of type MI_File_to_BPM_ABS

b) Insert Receive Step

In Message select the Container

c) SEND step

9) Save and activate all

10) Integration Directory

a. Create Configuration Scenario, Business Service BS_File_BPM

b. Receiver --> Inbound Interface (MI_File_to_BPM_IB )

Sender --> Outbound Interface (MI_File_to_BPM_OB)

c. Import Integration process by right clicking new ( since it acts as sender/receiver service )

d. Create Communication Channels Sender and Receiver channels

e. Create Receiver determinations/Interface determination/Receiver Agreement

We need to create 2 receiver determinations 1 is used from Source to BPM and 2nd is used from BPM to Target

f. Receiver determination -->

1) Service >>BS_File_BPM

Interface >> mi_file_to_bpm_ob

Receiving service : IP_File_to_file

Configuration overview for Receiver det.

IP_File_to_file --

MI_File_to_BPM_ABS , IM_File_to_BPM(mapping)

Receiver agreement not required.

2) Service -- IP_File_to_file

Interface -- MI_File_to_BPM_ABS

Receiveing service-- BS_File_BPM

Configuration overview for Receiver det

BS_file_BPM--

MI_File_to_BPM_IB , Mapping not required

Receiver agreement >> cc_bpm_rec (which has receiver comm. Channel)

Regards,

sridhar

Message was edited by: sridhar reddy kondam

[Former Member]

HI Moorthy,

I have verified the configuration once again. Please find the config details below.

Receiver determination:

1) File_Sender (Outbound) -> IP_F2F (Abstract, integration process)

2) IP_F2F (Abstract) -> File_Receiver (Inbound)

Receiver agreement from BPM to file_receiver is done.

<b>It seems that BPM is not getting called at all. There is no entry in SXMB_MONI_BPE</b>

Please advise.

Regards,

Ajay.

Message was edited by: AKVKN

[Former Member]

Hi,

Just try doing the following steps.

- Transaction PFWS.

- Type in the 8 digit process id, e.g. '90000005'.

- F6, Display.

- Tab 'Trigerring events'.

- Press on the button in the first column of the grid control.

- After 2 transport popus you'll get a green light there.

Try this and let me know if it works.

Regards,

abhy

[Former Member]

Hi,

In SXMB_MONI, there will be two entries for your scenario.

File->BPM

BPM->File,

For the first entry(File->BPM), you would have a PE entry.Clicking on this, will take you directly to the BPM process. There, go to technical settings,and check if all the steps have a green LED.

Regards,

Smitha.

[Former Member]

Thanks for the reply.

In SXMB_MONI I see the following steps are processed successfully.

Inbound msg -> receiver grouping -> Response.

<b>and the process fails at "Call adapter" (No specific error as such, but the flag for Call Adapter is displayed as "<i>Arrow Mark (->)</i>" i.e Transfer to process engine.</b>

Please find the call adapter's trace below.

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

- <!-- Call Adapter

-->

- <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="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />

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

-->

<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="B" name="CL_XMS_MAIN-ENTER_XMS" />

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

-->

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

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

-->

<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />

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

<Trace level="1" type="T">****************************************************</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">* *</Trace>

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

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

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

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

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

<Trace level="1" type="Timestamp">2006-05-22T08:25:54Z EST</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">****************************************************</Trace>

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

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

-->

<Trace level="1" type="T">Message-GUID = 95D7D260E96C11DAB2CD001438BD2DC3</Trace>

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

<Trace level="1" type="T">QOS = EO</Trace>

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

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

-->

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

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

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

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

<Trace level="1" type="T">Generated prefixed queue name = XBTI0007</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="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />

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

-->

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

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

<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />

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

-->

<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 = XI</Trace>

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

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

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

<Trace level="1" type="Timestamp">2006-05-22T08:25:54Z EST</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="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />

<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">R E C E I V E R - D E T E R M I N A T I O N</Trace>

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

</Trace>

</Trace>

</Trace>

</Trace>

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

- <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">I N T E R F A C E - D E T E R M I N A T I O N</Trace>

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

</Trace>

</Trace>

</Trace>

</Trace>

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

<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />

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

-->

- <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_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />

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

-->

<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 = XBTO30__0001</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" />

<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="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />

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

-->

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

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

<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />

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

-->

<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 = XI</Trace>

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

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

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

<Trace level="1" type="Timestamp">2006-05-22T08:25:54Z EST</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="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />

<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 http://abc.com/F2FBPM IM_F2F_BPM</Trace>

</Trace>

</Trace>

</Trace>

</Trace>

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

- <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 level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV" />

</Trace>

</Trace>

</Trace>

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

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

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

-->

<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_XMS_PLSRV_CALL_BPE-ENTER_PLSRV" />

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

-->

</SAP:Trace>

Thanks

Ajay

Message was edited by: Ajay Kumar V

Message was edited by: Ajay Kumar V

[moorthy]

Hi Ajay,

1) As per the post, you are able to get the Message from the File in XI (SXMB_MONI)

2) Is it calling BPM ? Are you able to see 2 messages in XI for this particular scenario.. ie. one from File to BPM and second one from BPM to File.

Go to transaction code SXMB_MONI_BPE and check is the BPM processed or not..

3) Do you configured Receiver Determintaion from BPM to File .. in this did you check for the Receiver Agreement.. If not do the Receiver Agreement..

Hope this helps..

Regards,

Moorthy

[former_member8655]

Hi Ajay

Got to SXi_cache and check for the entry of your integration process.

is entry there?

and if yes is it with status 0?

if it is 99 it is having an error so check your BPM again.

Regrads

Mitesh

[Former Member]

Hi,

goto sxmb_moni and check wat is the error u get.which step u get the error.can u post the error so we can try helping u.

regards

jithesh

[bhavesh_kantilal]

Ajay,

Look into the RunTimeOwrkBench--> Component Monitoring and see the status of your FILE adapter. Does it show any error?

Next, look into the SXMB_MONI and trace the error for your problem.

Regards,

Bhavesh