cancel
Showing results for 
Search instead for 
Did you mean: 

SAP BW : SPO transport error RC-12

Former Member
0 Kudos

Hi Floks,

Facing SPO transportation issue with RC-12  DEV to QTY system

error messages from logs:

The internal session was terminated with the runtime error MESSAGE_TYPE_X (see ST22)

DUMP MESSAGES

Error analysis
    Short text of error message:
    Unexpected program status

    Long text of error message:

    Technical information about the message:
    Message class....... "RSBK"
    Number.............. 899
    Variable 1.......... " "
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "

How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    -
    You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    please use the following search criteria:

        "MESSAGE_TYPE_X" " "
        "CL_RSBK_DTP_DATABASE==========CP" bzw.
     "CL_RSBK_DTP_DATABASE==========CM003"
        "COPY_FROM_DB"
    If you cannot solve the problem yourself, please send the
    following documents to SAP:

Information on where terminated
    Termination occurred in the ABAP program "CL_RSBK_DTP_DATABASE==========CP" -
     in "COPY_FROM_DB".
    The main program was "RDDEXECU ".

    In the source code you have the termination point in line 208
    of the (Include) program "CL_RSBK_DTP_DATABASE==========CM003".
    The program "CL_RSBK_DTP_DATABASE==========CP" was started as a background job.
    Job Name....... "RDDEXECL"
    Job Initiator.. "DDIC"
    Job Number..... 19403000

quality screen shot :

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Actually for SPO source is Bex query.

  • if we want to use bex query as source we need select "Quesry is used as Infoprovider"in query properties but  in QTY system checkbox option is disabled.
  • is there any possible method to capture the Query property.

Thanks

Hari

Former Member
0 Kudos


Hello , RC-12 comes when there is a issue with basis , so please contact your basis team. i would suggest to create new transport and collect the query and then ask for migartion.

Thanks, Saveen.

KodandaPani_KV
Active Contributor
0 Kudos

Hi,

have you collected the properly in DEV and while collecting all objects should be active.

activatet the transformation through program - RSDS_DATASOURCE_ACTIVATE_ALL using SE38

after check the obejects.

have you missed any routines while collecting the TR in dev

Thanks,

Phani.

Former Member
0 Kudos


Hi Phani,

Yes we collected objects manually in DEV & all the objects are in active version.

Thanks

Hari

KodandaPani_KV
Active Contributor
0 Kudos

HI,

you are saying RC12 it is the problem same TR don't move to PRD system.

go through the logs and find the error where are the problem

go to STMS -> select the TR -> double click on the TR -> then expand the node -> find the errors.

please share the Fail TR screen shot.

other wise collect the fresh TR in dev move to qas system.

Thanks,

Phani.