Object '0AXYZ' of type '3.x InfoSource' is not available in version 'D'

[Former Member]

Hello,

I am new to BI in 2004s. In my current project we have a new installation of BI 7 and we are starting from scratch with BI 7.

Is there anything that has changed with activation of BI Content.

When I try to activate few infosouces I get the below error.

<b>Object 0AXYZ (3.x InfoSource) could not be collected for object ()

You have collected objects in the BI Metadata Repository. Associated objects for object of type have also been collected. Object 0AFCONV of type 3.x InfoSource was among these objects. However, this object 0AFCONV of type 3.x InfoSource is not available in the metadata repository.</b>

When I check in the meta data repository for 3.x infosources I get the below error.

<b>Object '0AXYZ' of type '3.x InfoSource' is not available in version 'D'</b>

Could you please let me know whats wrong.

Your imemdiate response is highly appreciated.

thanks

Surya

[former_member186358]

Hi Surya,

The new DataSource concept cannot yet be used for transferring data from external systems (metadata and data transfer using staging BAPIs) or for transferring hierarchies.So have to use 3.x data flow.

Regards,

Anil

[Former Member]

Lots of things changed

It starts from whether you have replicated datasource as NEW or 3.x and then take a look below.

with new 7.0 datasource

R/3---->PSA only (using Infopackage) for all the Loads -Mandatory

PSA -

---

>ODS/Cube -->load using DTP ,create transformation first

no Datamart architecture in NW2004s

so ODS -

---

>Cube load using DTP ,creating transformation first

Once loaded to PSA in DTP you have the option of FULL or DELTA ,full loads all the data from PSA and DELTA loads only the last load of PSA.

Go through the links for Lucid explainations

Infopackage -

http://help.sap.com/saphelp_nw2004s/helpdata/en/43/03808225cf5167e10000000a1553f6/content.htm

DTP

http://help.sap.com/saphelp_nw2004s/helpdata/en/42/f98e07cc483255e10000000a1553f7/frameset.htm

Creating DTP

http://help.sap.com/saphelp_nw2004s/helpdata/en/42/fa50e40f501a77e10000000a422035/content.htm

Pre-requisite-

You have used transformations to define the data flow between the source and target object.

Creating transformations-

http://help.sap.com/saphelp_nw2004s/helpdata/en/f8/7913426e48db2ce10000000a1550b0/content.htm

ODS to Cube -

http://help.sap.com/saphelp_nw2004s/helpdata/en/ce/dc87c1d711f846b34e0e42ede5ebb7/content.htm

Hope it Helps

Chetan

@CP..

[Former Member]

Hey Chetan,

I realise that a lot of things have changed in 7.0

Just wondering if something has changed with the BI content installation.

My system is a fresh BW system with BI 7.0 and we are starting from scratch.(We dont have to migrate).

From the error which I have reported above, as it is an installation of infosource I am assuming that it doesnt matter of the replication of a datasource is new or 3.x.

Do you see anything that has been missed with the issue above. Is it a BI content installation problem or is it something to do with BI 7.0 which I have not done.

thanks for your reply.

Cheers!!

Surya

[Former Member]

It matters as SAP dont have BI content (business content update rules/transfer rules) for NEW datasource.

Only if you replicate datasource as 3.x then you can use the standard business content with business content update rules/transfer rules else NOT.In which case you have to create Transformations ,DTP and the flow I mentioned previously.

Question is did you replicate datasource as 3.x or NEW ??

Rationale for using 3.x or NEW

Hope it Helps

Chetan

@CP..

[Former Member]

Hey Chetan,

I havent replicated the Datasource yet. Today is the first day of using the system and I was trying to install the BI content.

Do I need to replicate the Data source first to install the infosources? I dont understand the link as they are independent unless linked with transfer rules..may be I have not come out of the BW 3.5 mindset yet.

From the link you have provided my understanding is that the migration of the DataSource is needed if you want to convert a 3.X DataSource to a SAP NetWeaver 2004s DataSource.

What would be the best way to do. Replicate the datasource as 3.x and use the old flow or migrate it to 2004s and use new features.

Thanks,

Surya

[Former Member]

I already gave you the rationale ,repeat again.

3.x datasource if you want to use business content updaterules,transfer rules,routines provided by SAP.

NEW datasource - you can only use Infocube provided by SAP ,not business content updaterules,transfer rules,routines provided by SAP.

once you replicate DS as NEW automatically update rules,transfer rules get deleted.

So you have to write routines and do mapping manually if you chose to replicate DS as NEW.

Datasource replication(3.x or NEW) is must before you install any business content in BW.

Hope it Helps

Chetan

@CP..

[Former Member]

Hey Chetan/Anil,

Thank you!! atleast I have clarity on few things now but we have lost on the original issue.

When I check any of the 3.x infosources in the meta data repository it says the object is not available in version D and hence I believe its not able to install the business content.

I am not able to install any of the 3.x infosources. I have replicated one datasource just to check but when I try to install the corresponding infosource it still says its cannot install.

Thanks if you can share your thoughts. I am assining points for the previous replies. They were really helpful.

thanks,

Surya

[Former Member]

Hi,

Replicate the corresponding datasource as 3.x and also activate the datasources in TX: RSDS. Then try to locate the 3.x infosource in Business Content.

Hope this helps.

Best Regards,

Rajani

[former_member186358]

Hi Surya,

Below are important points to note at the time of upgrade.

Lessons Learnt - Upgrade

1)Convert Data Classes of InfoCubes. Set up a new data class as described in SAP OSS Note 46272.

2)Pay attention to the naming convention. Execute the RSDG_DATCLS_ASSIGN report.

3)Run the report RSUPGRCHECK to activate objects.

4)Upgrading ABAP and JAVA in parallel may cause issues. If there is no custom development on J2EE instance, it is recommended to drop the J2EE instance and re-install the latest J2EE instance after the upgrade.

5)Apply SAP OSS Note 917999 if you include the Support Patch 6 with the upgrade or you will get the error at PARCONV_UPG phase. When you upgrade to a product containing Basis 700, the phase PARCONV_UPG terminates. You included Basis Support Packages up to package level 6 (SAPKB70006) in the upgrade. The job RDDGENBB_n terminates with the error RAISE_EXCEPTION. In addition to this, the syslog contains the short dump TSV_TNEW_PAGE_ALLOC_FAILED. The program SDB2FORA terminates in the statement "LOOP AT stmt_tab". An endless loop occurs when the system creates the database table QCM8TATOPGA.

6)Apply the OSS note 917999 if you get the following error during PARCONV_UPG phase: PARCONV_UPG terminates with TSV_TNEW_PAGE_ALLOG_FAILED

Critical OSS Notes:

819655 – Add. Info: Upgrade to SAP NW 2004s ABAP Oracle

820062 - Oracle Database 10g: Patchsets/Patches for 10.1.0

839574 – Oracle database 10g: Stopping the CSS services ocssd.bin

830576 – Parameter recommendations for Oracle 10g

868681 – Oracle Database 10g: Database Release Check

836517 – Oracle Database 10g: Environment for SAP Upgrade

853507 – Usage Type BI for SAP Netwaevers 2004s

847019 - BI_CONT 7.02: Installation and Upgrade Information

818322 – Add. Info: Upgrade to SAP NW 2004s ABAP

813658 - Repairs for upgrades to products based on SAP NW 2004s AS

855382 – Upgrade to SAP SEM 6.0

852008 – Release restrictions for SAP Netweaver 2004s

884678 - System info shows older release than the deployed one

558197 – Upgrade hangs in PARCONV_UPG

632429 – The upgrade strategy for the add-on BI_CONT

632429 - The upgrade strategy for the add-on FINBASIS

570810 - The upgrade strategy for the add-on PI_BASIS

632429 - The upgrade strategy for the add-on SEM-BW

069455 - The upgrade strategy for the add-on ST-A/PI

606041 - The upgrade strategy for the add-on ST-PI

632429 - The upgrade strategy for the add-on WP-PI

Post upgrade Steps :-

1. Read the Post Installation Steps documented in BW Component Upgrade Guide

2. Apply the following SAP OSS Notes

47019 - BI_CONT 7.02: Installation and Upgrade

558197 - upgrade hangs in PARCONV_UPG, XPRAS_UPG, SHADOW_IMPORT_UPG2

836517 – Oracle Database 10g: Environment for SAP Upgrade

3. Install the J2EE instance as Add-in to ABAP for BI 7.0 and apply the Support Patch that equivalent to ABAP Support Patch.

4. Run SGEN to recompile programs.

5. Install the Kernel Patch.

6. Missing Variants - (also part of test script)

look at the RSRVARIANT table in SE16. If it is empty, then you will definitely need to run RSR_VARIANT_XPRA

program - RSR_VARINT_XPRA

OSS -953346 and 960206 1003481

7. Trouble Shootauthorizations

820183 - New authorization concept in BI

Assign points if this helps.

Regards,

Anil