File to RFC problem- data is not inserting into ztable in R3 system

[Former Member]

Hi

i have done File to RFC scenario which picks data from flat file and inserts into ztable via RFC in R3. but while testing my scenario everything is successful in XI monitoring (Successful flag in MONI and RWB) and in auditlog message status is DLVD.

it seems to be everything successful in XI and RFC call also successful in R3 system.

but for some reason data is not inserting into table (RFC is used to insert data into ztable)

Is there any way to debug RFC call excecution in XI..?

RFC code is like this:

insert ZMM_AUTO_GR from INPUT_TABLE.

commit work.

END FUNCTION.

please advice what could be the reason not inserting into table.

Help would be appreciated.

Regards,

Rajesh

[Former Member · Accepted solution]

Dear Rajesh,

If you couldnt solve yet after good suggestions from experts, try this way to locate the error.

log in to Runtime work bench, choose

Component Monitoring-->

communication channel Monitoring-->

provide the necessary details like :

Business Service, CC name, Adapter Type and Direction and try use filter.

check audit log to see exactly where u r getting error.

let us know what does it say.

hope we can rectify with in this way.

Best Regards

Praveen

[Former Member · Accepted solution]

Hi Praveen,

please see audit log- from communication channel monitoring..

Receiver channel 'CC_INCA_RFC_SAPECC_Receiver' for party '', service 'R3DCLNT210' (internal name 'RfcClient[CC_INCA_RFC_SAPECC_Receiver]')

Client data: {jco.client.lang=EN, jco.client.snc_mode=0, jco.client.client=210, jco.client.passwd=******, jco.webas.ignore_jdsr_error=1, jco.client.user=jsaha, jco.client.sysnr=00, jco.client.ashost=ausr3devdc02}

Repository data: {jco.client.lang=EN, jco.client.snc_mode=0, jco.client.client=210, jco.client.passwd=******, jco.webas.ignore_jdsr_error=1, jco.client.user=jsaha, jco.client.sysnr=00, jco.client.ashost=ausr3devdc02}

Current pool size: 1, maximum pool size : 1

Channel History

- OK: 2008-07-28 04:32:04 PDT: Message processed for interface ZAUTO_GR_STAGE_INCA

- OK: 2008-07-28 04:31:04 PDT: Message processed for interface ZAUTO_GR_STAGE_INCA

- OK: 2008-07-28 03:56:56 PDT: Message processed for interface ZAUTO_GR_STAGE_INCA

- OK: 2008-07-28 03:49:04 PDT: Message processed for interface ZAUTO_GR_STAGE_INCA

- OK: 2008-07-28 03:48:04 PDT: Message processed for interface ZAUTO_GR_STAGE_INCA

[Former Member · Accepted solution]

Hi,

As per the thread u said when setting External breakpoint. u r not able to see the import parameters value.

1) Well check the Outbound Interface (From File) and Inbound Interface (RFC Import parameters) are of same Data type.

2) If u have made any changes in the RFC in btw please reimport.

since u had said u r rfc works when executed locally , i sense it's pure data type mis-match check Data from Outbound Interface is not getting in to import para

regd

srini

[Former Member]

thanks.. this issue is resolved

[Former Member]

Hi Rajesh,

First of all try to check runtime workbench if the RFC call was successfull. Later verify if you if you checked Commit Control for Single BAPI Calls in Advanced Mode. in the end if it doesn't work you can check external debugging by stopping the queues and later restarting them. there should be an external breakpoint.

/wg

[Former Member]

use Commit work statement after your Insert statement...

[prateek]

Use an External breakpoint at ur receiver RFC source code. Use the same user ID as that of the communication channel setting in ID. Then run ur complete scenario.

Regards,

Prateek

[Former Member]

Hi Prateek,

I have kept 'External Breakpoint' in RFC at 'sy-subrc' check, and i run complete scenario. how can i check this external break point. do i need to run RFC explicitly in R3 once XI call the RFC or will it automatically executes external break point.

Regards,

Rajesh

[prateek]

It should automatically stop at breakpoint while running the scenario.

Regards,

Prateek

[Former Member]

Hi Prateek,

thanks..

it was automatically stop at break point, but i couldn't see input values in input structure of RFC. please advice what could be the reason..

My RFC developed this way:

im using only Table parameters (but not neither import nor export parameters).

My code is like this:

TABLES

*" INPUT_TABLE STRUCTURE ZMM_AUTO_GR

insert ZMM_AUTO_GR from INPUT_TABLE .

commit work.

END FUNCTION.

Please advice this RFC is ok to communicate via RFC, or if any changes required ??

Regards,

Rajesh

[Former Member]

> My code is like this:

> TABLES

> *" INPUT_TABLE STRUCTURE ZMM_AUTO_GR

> insert ZMM_AUTO_GR from INPUT_TABLE .

> commit work.

> END FUNCTION.

Better you careate an internal talbe and put Loop at INPUT_TABLE and move alll the values to this internal table and then from this internal table you can update the data in you R/3 table.

[santhosh_kumarv]

Hi,

Check your RFC function module, execute it in the debugging mode and confirm that the RFC is updating the required table.

Thanks

SaNv...

[Former Member]

Thankx All,

My RFC is working fine, i have already checked in debbugging mode. RFC is inserting in ztable fine.

please advice if any other reasons which could cause this problem.

Regards,

Rajesh

[Former Member]

The only way to know the problem is to set an external break point.

Do same as Parteek suggested.

[Former Member]

please set a commit work in communication channel

/wg

[Former Member]

did u try manually running RFC in SE37 screen... give the inputs there and debug it,...

check sy-subrc after insert statement..