cancel
Showing results for 
Search instead for 
Did you mean: 

Problem in Delta upload of data source 0BP_DEF_ADDRESS_ATTR

Former Member
0 Kudos

Hi,

In the production server, we have a problem with delta upload of data source 0BP_DEF_ADDRESS_ATTR. The message in SM37 is:

Job started

Step 001 started (program SBIE0001, variant &0000000121844, user ID BIREMOTE)

Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)

DATASOURCE = 0BP_DEF_ADDRESS_ATTR

RLOGSYS    = XXX

REQUNR     = REQU_55P6R5U3I54HK33Z7CW2P3KTE

UPDMODE    = R

LANGUAGES  = *

*************************************************************************

*          Current Values for Selected Profile Parameters               *

*************************************************************************

* abap/heap_area_nondia......... 5368709120                              *

* abap/heap_area_total.......... 5368709120                              *

* abap/heaplimit................ 40000000                                *

* zcsa/installed_languages...... ES                                      *

* zcsa/system_language.......... S                                       *

* ztta/max_memreq_MB............ 2047                                    *

* ztta/roll_area................ 12000000                                *

* ztta/roll_extension........... 5368709120                              *

*************************************************************************

Function module /BI0/QI0BP_DEF_ADDRESS__A1 does not exist

You can only use LIKE and TYPE to specify types in RFC

Internal session terminated with a runtime error MESSAGE_TYPE_X (see ST22)

Job cancelled

Could anybody please help me out.

Thanks

Anaid

Accepted Solutions (0)

Answers (1)

Answers (1)

0 Kudos

Hi Anaid,

Use transaction ST22 to see details about the error. It should be around the same time the system logged line "Internal session terminated with a runtime error MESSAGE_TYPE_X (see ST22)" in SM37.

Read the runtime error explanation thoroughly and follow its instructions. It will also show the code where the failure occurred and the call stack. A Note search using the keywords you can extract from it should point you towards a solution.

Regards,

Roger