Skip to Content
avatar image
Former Member

Source RSDS XXXXXX DBPCLNT300 does not exist. RSTRAN803


We encountered that there are some data sources that had been already migrated (to version 7.x), however after changes they appear in version 3.x. Example DS 0UNSAPPGRP_TEXT:

Another unexpected behavior is that they don’t present neither PSA table nor technical attributes.

When we try to modify the datasource we receive the error message “A 3.x DataSource can only be processed with transfer rule maintenance. Do you want to maintain the transfer rule now?”. If we press “Yes”, then we receive the error message “The object name is not allowed to be empty. Message no. R7105”.

Actually, since data flow was migrated to version 7.x before client copy, no transfer rules exist. It seems that part of the dataflow stayed in 7.x version (transformation) but the data source is in emulated version 3.x since no record is available for it in RSDS table. When we try to display the transformation we receive the error message “Source RSDS XXXXXX DBPCLNT300 does not exist. RSTRAN803".

These datasources don’t present an ‘Active’ record in RSDS table for the new ECC DEV environment (DBPCLNT300). That’s to say, there isn’t any record for these datasources with OBJVERS = ‘A’ and LOGSYS = ‘DBPCLNT300’. Data sources are pointing to the old ECC DEV environment (PBDCLNT300).

I think this is the main cause of every unexpected behavior. Please refer to attachment for further information, print screens of tables, data sources and details about error messages.

Below many notes we have already analyzed:

925228925228: Replication and manual activation of DS don’t solve the problem.

936644936644 936644 936644: It seems that this note is describing our scenario however we cannot access transfer rules because they don’t exist anymore since data flow was already migrated to version 7.x. I could migrate the DS but I would like to run a process that fix all datasources under the same scenario. It seems that if we had these datasources active in the new ECC DEV (in RSDS table) data flows would get fixed and error messages would disappear.

1655766: Will the execution of DBLS fix the situation? From “Old logical system name” PBDCLNT300 to “Logical system name” DBPCLNT300?

Is there any process that we can execute in order to get these datasources active in the new ECC DEV environment?

Thanks in advance.



1qr2h.jpeg (12.9 kB)
iqlth.png (11.2 kB)
rgnna.png (3.5 kB)
jjioh.png (19.8 kB)
gzqnt.png (10.6 kB)
vksiv.png (9.9 kB)
5tmcj.png (11.6 kB)
rpsvx.png (15.7 kB)
Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

0 Answers