Transfer Structure Error

[Former Member]

Hi Guys,

I am getting the following error when trying to activate Transfer Structure for 0PLANT_TEXT in BW.

-

---

Error when creating transfer structure /BIC/CCGB0PLANT_TEXT in source system ORAGDV130

Message no. R3104

Diagnosis

An error occurred when creating transfer structure /BIC/CCGB0PLANT_TEXT as an IDoc segment in source system ORAGDV130 .

System response

The action was terminated. No data was changed.

Procedure

Use the generation log in source system ORAGDV130 to identify the error, and remove the cause.

-

---

I am using PSA as the transfer method. Any help is appreciated.

Thanks.

[Former Member · Accepted solution]

Hi Govind,

Have you tried to replicate in BW your data source?

Best regards,

Eugene

[Former Member · Accepted solution]

Hi Eugene,

Yes, i replicated all Data Sources in BW.

Thanks.

[Former Member · Accepted solution]

Govind,

Are you sure that Roberto's OSS note is not applicable? You have the higher or equal SP?

Best regards,

Eugene

[Former Member · Accepted solution]

Hi Eugene,

Our R/3 version is 4.7. And the PI is 2004_1.

Thanks.

[Former Member · Accepted solution]

Govind,

Try to evaluate if OSS Note # 493422 "Source system inconsistency with IDoc segments/transfer str." is applicable to your situation.

Best regards,

Eugene

[Former Member · Accepted solution]

Hi Eugene,

I went thru that note before. But, the solution applies for R/3 release 3.1i. Since, we are on R/3 4.7, i felt it will not help.

Thanks.

[Former Member · Accepted solution]

Govind,

The applicability of the note:

- Source System Release = 3.1I

- Source system = R/3 Release 4.0B ff (<b>all subsequent releases also 4.7 and so on</b>)

Best regards,

Eugene

[Former Member · Accepted solution]

Hi Eugene,

I am not sure if i can create that program or not. But, i just found a temporary alternative. I changed the Trnasfer method from PSA to IDoc. As i mentioned before, i could activate the transfer structure successfully. So, i went ahead and loaded the text into the plant datatarget. Then, again i switched back IDoc to PSA and then activated the TS. As is expected, i got the error again. Atleast i was able to load data. Will there be a problem later?

Thanks.

[Former Member · Accepted solution]

Hi Govind,

I know my advice will not be very sophisticated but when I am looking for solution for a long time and can not find it I simply copy all InfoSource and a new one very often works good even if it looks the same as old one.

It is because when you change your InfoSource some program may not generate properly. Looking for solution can be very low level task.

Alternatively ask your basis to check generation logs of your transfer structure program.

Regards,

Andrzej

[Former Member · Accepted solution]

Hi Andrej,

We have not changed the 0PLANT_TEXT (Flexible Update) InfoSource at all. Anyway, i will ask our BASIS team to check the generation logs of source system. What is the t-code to check generation logs in source system if i want to view it.

Thanks.

[Former Member · Accepted solution]

Hi Govind,

To implement what is said in the note IS VERY EASY!

I have even created this program in my system. It seems to be very very useful program. Not only for your case. THE PROGRAM CHECKS CONSISTENCIES IN THE SOURCE SYSTEM AND CORRECT THEM! It may help in many problems with source systems.

So, here is a way to implement the program.

- In the text tabstrip of the note click on 'Correction Instructions' tabstrip.

- Then in the 'Ref. Correction' column choose a number that corresponds to your system PI (click on it).

- Click on a report name 'z_rs_scrsystem_r3_check'.

- In your BW system execute tcode SE38 (or ask someone with a development key), give the name 'z_rs_scrsystem_r3_check', click on a button 'create'.

- Enter program description, choose 'executable' option.

- Into the screen of ABAP Editor copy-paste the code from the note correction instructions.

- Click on 'Check', then 'Activate' icons.

- If everything is OK, press F8 (execute).

Then follow the note:

"These programs have the following input parameters:

SLOGSYS Specify the logical system name of your source system here

RLOGSYS Specify the logical system name of the BW system here

If you enter nothing here, all existing BW source system connections are processed.

Use the NO_DB_UP parameter to control whether the program works in check or correction mode. The NO_DB_UP = 'X' default represents check mode.

2. First execute the Z_RS_SCRSYSTEM_R3_CHECK program in check mode. The inconsistencies detected by the program are issued as a log. Now start the programs in correction mode (NO_DB_UP = ' '). Then execute the program again in check mode (NO_DB_UP = 'X'). This program may not eliminate all inconsistencies during the first correction run. Then execute the program again in the check mode (NO_DB_UP = 'X'). This program may not eliminate all inconsistencies during the first correction run.

3. If the error continues to occur:

Check the transfer structure in the source system using transaction SE11. Use note 147195 if namespace conflicts are reported in the consistency log.

After the correction has been made, you should check to see whether it is possible to switch your transfer rules from the IDoc transfer method to the PSA transfer method.

We recommend that you use the PSA transfer method."

Best regards,

Eugene

Message was edited by: Eugene Khusainov

[Former Member · Accepted solution]

Hi Govind,

Ask your basis guys to check the system logs on the source system (r/3).

I had a similar problem and when we checked the logs it showed that the tablespace had reached a 100 %, therefore it was unable to created a copy of the transfer structure on the r/3 side while activating it.

Regards,

Demetrius.

[Former Member · Accepted solution]

Hi,

well the question is: what generation logs you should check?

Maybe try logs of your data source in R3:

RSA6 -> point cursor on your DataSource -> use button 'Display logs'

or

try to check your transfer routine program in BW

RSA1 -> InfoSources -> problematic transfer rule -> Extras -> Display program -> Transfer program XXXXX -> Check

maybe one of those gives you any clue...

Andrzej

[Former Member · Accepted solution]

Hi,

Thanks to one and all. Thanks to Eugene, Andrzej and Demetrius. I will try to implement the things you mentioned and i will let you know.

Thanks again.

[former_member261312]

Yup.

APPLYING NOTE 2214733 (successor to SAP Note 493422) fixed this in one shot in source system. Then re-run Program RSDS_DATASOURCE_ACTIVATE_ALL on any and all troublesome data sources of this sort in BW and they're fixed!

Thanks Marco Modesto for the clue.

[former_member595640]

In the source system, delete the related datasource in the ROOSGENSEG and ROOSGEN tables and re-active it in the BW system.

[Former Member]

Hello to everybody.

I have the same problem, did you solve it?.

I detected a issue very important, when you try to activate any datasource, the displayed problem is that the transfer structure wasn't created.

When you configure the source system into SAP tables is created a relation with a prefix BA / BD, the table is RSBASIDOC, I think this table is used to map the tables to use in SAP r3.

Sample.

Before we did have the prefix BA and the transfer tables was /BIC/CCBA2LIS_11_V_SCL

Now we have the prefix BD and the transfer tables must be /BIC/CCBD2LIS_11_V_SCL, but now this table don't exists and is necessary to activate the data source in SAP BW.

Somebody knows if the not 493422 is usefull to solve this problem?.

[Former Member]

Hi All,

We solved this problem applying SAP Note 493422 in ECC (Inconsistent IDoc segments/transf. structures in srce system). This note has a program (Z_RS_SCRSYSTEM_R3_CHECK) that clean up old IDOC segments and ROOSGEN DDIC structures. This note is for Source System (not BW).

https://websmp230.sap-ag.de/sap/support/notes/convert2pdf/0000493422?sap-language=EN

BR,

Marco Modesto.

[Former Member]

Hi Govind Sehgal

did you solve your problem ? I have the same and I could not find any solution...

Fernando

[Former Member]

Try to activate all the transfer structures using the program RS_TRANSTRU_ACTIVATE_ALL in se38

[Former Member]

Hi Govind,

Change the transfer method from PSA to IDoc and save it. Again change back to PSA and activate transfer rules.

It may works some times.

Srini

[Former Member]

Hi Guys,

Bhanu - I checked ST22 for short dumps in source system. I did not find any.

Roberto - We are on R/3 4.7. I went through the note. But, it didn't seem to apply for us.

Srnini- I already tried changing to IDOC. Then it got activated. When i changed to PSA again, i get the same error.

Bhima - Did you mean ST22.

Thanks.

[Former Member]

Check if 590217 is applicable...

Bye,

Roberto

[Former Member]

Hi Govind,

Check with 0 Plant_Text is Active / Not in Transfer Rule is active / not in the same time check in SM22.

Thanks

Bhima Chandra Sekhar G

[former_member188975]

Hi Govind,

Did you check for any dumps in your source system?