Привет всем!
Не подскажите как можно записать таблицу через удаленный функциональный модуль
call function 'ZUPDATE' DESTINATION 'QRWCLNT200'
exporting
l_doc = doc_no
tables
R_table = lt_table.
в самом функциональном модуле хочу записать в таблицу данные
пытался использовать Insert и MODIFY к примеру
MODIFY Ztable from table R_table.
но система падает в дамп. Говорит что типа такие вещи через RFC не доступны.

А поподробнее - что именно говорит, как и где? Привидите дамп полностью.

Да ну? А как бы тогда BAPI через RFC работали?

Для начала вызывайте remote фм с обработкой exception.



И дамп в студию)

Краткий текст
"Invalid request."

Что произошло?
Error in the ABAP Application Program

The current ABAP program "ZAYAVKA" had to be terminated because it has
come across a statement that unfortunately cannot be executed.

The error occurred during an RFC call to another system.
In the target system, a short dump has been written as well.
More detailed information on the error cause can be found there.

Анализ ошибки
An error occurred when executing a REMOTE FUNCTION CALL.
It was logged under the name "DBIF_RSQL_INVALID_REQUEST"
on the called page.

А остальное? И нужен дамп в вызываемой системе, а не в вызывающей.
Если хотите чтобы Вам помогли, приводите больше подробностей. Здесь ведь не сайт викторин

Краткий текст
Error in module RSQL of the database interface.



Что произошло?
Error in the ABAP Application Program

The current ABAP program "SAPLZ_MNR" had to be terminated because it has
come across a statement that unfortunately cannot be executed.



Что Вы можете сделать?
Note down which actions and inputs caused the error.


To process the problem further, contact you SAP system
administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Note which actions and input led to the error.

For further help in handling the problem, contact your SAP administrator
.

You can use the ABAP dump analysis transaction ST22 to view and manage
termination messages, in particular for long term reference.




Анализ ошибки
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
in
procedure "ZEBANUPD" "(FUNCTION)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
In a SELECT access, the read file could not be placed in the target
field provided.
Either the conversion is not supported for the type of the target field,
the target field is too small to include the value, or the data does not
have the format required for the target field.



Указания по устранению ошибки
Check the entries in the developer trace of the relevant work process
(transaction ST11).
Here you can find detailed information about the type and length of the
database field as well as the ABAP field into which the field was to be
imported.


If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:

"DBIF_RSQL_INVALID_RSQL" "CX_SY_OPEN_SQL_DB"
"SAPLZ_MNR" or "LZ_MNRU09"
"ZEBANUPD"



The exception must either be prevented, caught within proedure
"ZEBANUPD" "(FUNCTION)", or its possible occurrence must be declared in the
RAISING clause of the procedure.
To prevent the exception, note the following:
Информация о месте прерывания
Termination occurred in the ABAP program "SAPLZ_MNR" - in "ZEBANUPD".
The main program was "SAPMSSY1 ".

In the source code you have the termination point in line 25
of the (Include) program "LZ_MNRU09".
The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
procedure "ZEBANUPD" "(FUNCTION)", but it was neither handled locally nor
declared
in the RAISING clause of its signature.

The procedure is in program "SAPLZ_MNR "; its source code begins in line
1 of the (Include program "LZ_MNRU09 ".



Фрагмент исходного текста программы

Строк ИсхднТкст

1 FUNCTION ZEBANUPD. "#EC ENHOK
2 *"----------------------------------------------------------------------
3 *"*"Локальный интерфейс:
4 *" IMPORTING
5 *" VALUE(SKIP_ITEMS_WITH_ERROR) LIKE BAPIMMPARA-SELECTION OPTIONAL
6 *" VALUE(AUTOMATIC_SOURCE) LIKE BAPIMMPARA-SELECTION DEFAULT 'X'
7 *" VALUE(L_BANFN) TYPE BAPIEBANC-PREQ_NO OPTIONAL
8 *" EXPORTING
9 *" VALUE(NUMBER) LIKE BAPIEBANC-PREQ_NO
10 *" TABLES
11 *" REQZEBAN STRUCTURE ZEBAN OPTIONAL
12 *" RETURN STRUCTURE BAPIRETURN OPTIONAL
13 *"----------------------------------------------------------------------
14 *ENHANCEMENT-POINT BAPI_REQUISITION_CREATE_G8 SPOTS ES_SAPLMEWQ STATIC.
15
16 *ENHANCEMENT-POINT BAPI_REQUISITION_CREATE_G6 SPOTS ES_SAPLMEWQ.
17
18 data: zfistl1(4) type c,
19 zfinpos1(5) type c,
20 wt_outtab like ZEBAN,
21 ZZDPRMT TYPE EBAN-ZDPRMT.
22
23 * loop at REQZEBAN into wt_outtab.
24 * MODIFY ZEBAN from wt_outtab .
>>>>> INSERT ZEBAN FROM TABLE REQZEBAN.
26
27 * ENDLOOP.
28
29 if sy-subrc = 0.
30 write: /'готово ))'.
31 else.
32 write: /'не исправлено (('.
33 ENDIF.
34
35 ENDFUNCTION.

Учитывая

в первую очередь проверьте структуру и соответствие таблицы БД и словарного объекта, все ли активировано, затем проверьте соответствие и тождественность структур в обеих системах.

В приведенном ФМе параметр REQZEBAN STRUCTURE ZEBAN необязательный. Он точно передан?

А при чём тут это?

C DESTINATION 'NONE' работает?

Проверил действительно структуры различались в одной было DEC 17.3 в другой DEC 14.3
привел к одному элементу данных и все получилось.
Спасибо, за помощь!