BW Error: S:RSSDK:300 Field APC_MU not a member of /BIC/CAZMSS_PP0000100 00001

[Former Member]

Hi Gurus,

We are facing one issue in our BW system (7.3)

We have added two new fields in our Non-SAP system (SharePoint) and did the same in our BW system. But while previewing data in RSA1, we are getting the below error:

S:RSSDK:300 Field APC_MU not a member of /BIC/CAZMSS_PP0000100 00001

Message no. RSSDK300   

The functionality worked fine before and only after adding two new fields, we are getting this error.

Our BW system(ABAP) is Netweaver 7.3 and it is using UD Connect to connect to SharePoint system using our Portal Java system (7.3)

I have checked in some forums, where they suggested a note 1009063 and check the local bundling option from VA.

But our Java system is 7.3 and we don't have VA and I could not find that option from NWA in our JCO RFC destinations.

The RFC which is used for this UD Connect is working fine.

Please help me out as this is causing issues to us.

Awaiting your inputs and will be greatly appreciated.

Regards,

Ram.

[Former Member]

When  a new RFC destination is created in the visual admin , there is a tab called 'Special Settings'. In the very bottom there is a option "Local_Bundle", selected that issue will get resolve.

Refer this document related to RFC destination errors:

http://scn.sap.com/community/data-warehousing/netweaver-bw/blog/2012/11/29/errors-in-rsa1-when-extra...

[Former Member]

Hi Kalpana,

We are using BW 7.3 connected to Portal 7.3. So we don't have Visual Admin as it was replaced with NWA. I didn't find local bundle option in NWA.

I have checked the link you gave, and that was with ref of SAP NW 7.0 which does not help me.

Thanks,

Ram.

[Former Member]

This message was moderated.

[RamanKorrapati]

Hi,

Seems like you may be maintained field level routine, that's causing issue.

Please recheck your transformations from non sap data source to bw target.

As you said you added two fields to data source then how your filling them?

Please recheck your field APC_MU how you mapped and how you filled at bw side.

Thanks

[Former Member]

Hi Raman,

We have not maintained any field level routine.

At the time of activating and previewing the data at source itself we are not able to view the data and getting the error as stated above.

Thanks,

Ram.

[RamanKorrapati]

Hi,

After adding two fields to your data source, how your passing(filling) data to added fields? enhanced?

is there any field as  APC_MU at your data source level?

Thanks

[former_member182470]

After adding new fields have you reloaded all data to your infoprovider in BW? Have you enhanced your source as well and mapped in transformations?

[Former Member]

Hi Suman,

Yes, we have created a new data source and added the source fields to the target with the transformation, and while previewing we are getting this issue.

Thanks,

Ram

[former_member182470]

Are you trying to preview in PSA or data target? Please drop the data and reload again to target, activate it again.

Please activate your target definition before reloading data.

[MGrob]

HI

Have you checked out the two Notes 1009063 & 1007409

hope that helps

Martin

[Former Member]

Hi Martin,

Yes we have checked both the notes.

Both talk about some configuration using VA. But we don't have VA as we are in 7.3 and we have only NWA.

Please tell me where to do such config in NWA.

One thing that I have observed is, the RFC destination in ABAP side is working fine and it has a registered server program. We need to have a JCo RFC with that server program in JAVA side. But when I check the JCO RFC destination in NWA, there is no JCO RFC with that program id which is used in ABAP RFC.

Please help.

Regards,

Ram

[MGrob]

Hi

To maintain the JCO connections you need to go into the WebDynpro Content Administrator. There is no need fot the same registered  program in JAVA side.

Martin

[filip_sneberger]

For 7.5 go to portal NWA: Availability and Performance -> Resource Monitoring -> JC0 Monitoring -> Metadata Cache -> Structures -> Find and mark the structure from error mesage -> Push Clear button.