Missing session in SM35

[Former Member]

Hello Experts,

There is an issue like while uploading file to a Z transaction everything looks ok but the file does not appear in SM35 so can anybody guide me what & where should i check..??

Regards,

Nisha

[Sandeep_Panghal]

what do you mean by no files uploaded in SM35 ...

Have you already check for errors .

[Former Member]

Hi Sandeep,

Session name is missing in SM35.

Regards,

Nisha

[kesavadas_thekkillath]

You have to build it manually in your program

using fm

CALL FUNCTION 'BDC_OPEN_GROUP'

EXPORTING

client = sy-mandt

group = p_sess

user = p_user.

CALL FUNCTION 'BDC_INSERT'

EXPORTING

tcode = pu_tcode

TABLES

dynprotab = i_bdcdata[].

CALL FUNCTION 'BDC_CLOSE_GROUP'.

[Former Member]

Nisha,

The problem could be in your code. Make sure you are passing Session name in the BDC_OPEN_GROUP function module and your session should have records to process.

And apart from that you should code like this.

BDC_OPEN_GROUP ( make sure to paas the session name in GROUP parameter of this FM)

Loop at your internal table having values

BDC_INSERT

Endloop.

BDC_CLOSE_GROUP.

Please let us know if you are having some doubts.

Cheers

VJ

[Former Member]

Hi VJ,

I am using standard program RFBIBL01 to upload the file.

And i find CALL transaction & BDC session related statements to be greyed out in the code.

Please help.

Regards,

Nisha

[Former Member]

Hi Nisha,

If you are using a BDC session, when you open the group you need to be sure to check the parameter KEEP.

This will keep your session in SM35 even if it was sucessfuly.

Take a look at this example.

Matheus

CALL FUNCTION 'BDC_OPEN_GROUP'

EXPORTING

client = sy-mandt

group = v_group

user = sy-uname

keep = 'X'

EXCEPTIONS

client_invalid = 1

destination_invalid = 2

group_invalid = 3

group_is_locked = 4

holddate_invalid = 5

internal_error = 6

queue_error = 7

running = 8

system_lock_error = 9

user_invalid = 10

OTHERS = 11.

[Former Member]

Hi All,

Thanks for all valuable inputs.

I got the solution,it was due to some interface error.ZS13 transaction called one interface which had some issues.

Regards,

Nisha Verma