SPAU showing in QA but not in DEV

[Former Member]

Hi SAP experts,

We are applying Service Pack to our system but we found we have some SPAU objects in red in our QA system. We didn't have same SPAU objects in DEV but suddenly same objects show up in QA.

Any idea why we are getting these objects only in QA and not in DEV and how to correct this?

Thanks,

Sunny Thakur

[Former Member · Accepted solution]

Hi,

I might have to ask you if you have parallel landscape running and was QUA recently refreshed from production.

If parallel landscape running it can be that the object were changed in another development sysem and those changes have not been retrofitted in the DEv system.

Second can be as sunny suggested that you could have changed or applied the notes directly in QUA.

So go in se03 and check how the object was charged.

Did you take screen shot of SPAU before and after . Hope that these object are not there already before in the QUA system.

Just run SPAU in production and see if you find this object if your QUA was refreshed from PRD.

Thanks

Rishi Abrol

[Former Member · Accepted solution]

Hi Rishi,

Thanks your reply!

Yes our QA system was refreshed from our PROD before we upgraded the QA with latest SP?

I'll have to check with Basis and try to run SPAU in PROD to check whether we have objects in RED or not?

In case there is no SPAU objects in PROD, any other idea why would we have this error only in QA.

We do have another DEV/QA system but that were not touched/upgraded with SP.

Could you let me know how to correct these errors in QA and move to PROD. Should i fix this in QA and move the transport to PROD.

Thanks,

Sunny Thakur

[Former Member · Accepted solution]

Hi Rishi,

I checked with my Basis team and these error exists in PROD.So I guess we might have to open up QA fix it and then move to PROD.

Thanks for all your help.

Sunny Thakur

[sunny_pahuja2 · Accepted solution]

Hello,

In order to keep your all systems in sync, I will suggest you to change those objects in development system and then transport it to quality & production system.

Thanks,

Sunny

[Former Member · Accepted solution]

Hi,

If you do this then you are going to have this issue again.

So you need to follow some of the below steps.

First approch.

Identify if these object came fro second landscape. If yes then you should retrofit this DEV with these changes as they are in production. Then do the fix and move to QUA and can later be passed to production after upgrade.

If not then follow the second approch.

Ask the developers to Do remote compared between DEV- Upgraded QUA  and then fix the code in DEV and pass it to QUA. So that you can do the same when you go for production and you dont loose any fix.

I would never suggest to do in QUA as you might get issue in next support pack and it might be difficult to analyse again.

Thanks

Rishi Abrol

[Former Member · Accepted solution]

Hi Rishi,

We have error in table types. We did a compare between DEV/QA it was same, we once again activated the affected table types in DEV and moved to QA but it did not solve our problem.

So I guess only option left is to do it in QA and move to PROD.

Thanks,

Sunny Thakur

[Former Member · Accepted solution]

Hi,

Can you please provide the details of the table and the related issue.

Thanks

Rishi Abrol

[Former Member · Accepted solution]

Hi Rishi,

These are the table types for which we get error in SPAU. Even though we have compared between DEV/QA they are same maybe the way we built our system thats' we get this in SPAU.

HRDESV_EE_T_BW_FREK

HRDESV_T_T5D0P

HRPAYDE_RBM_T_BTRSUM

P01S_B2A_T_SVEM

P01S_B2A_T_T5D4U

P01S_B2A_T_XML

P01_SYMSG_FIELDLIST_TAB

Thanks

Sunny Thakur

[sunny_pahuja2]

Hello,

It might be possible that you have done changes in QA system but not in development system that's why objects are coming in SPAU.

You can use version management to check if some changes were done in quality system and compare it with development system.

Thanks,

Sunny

[Former Member]

Hello,

Thanks for your reply!

No we haven't done any change in QA, as soon as QA system was upgraded we got objects in SPAU. These objects were never under SPAU in DEV so kind of confused why it is only coming in QA.

If it would have been coming in DEV, we would have created TR and moved to QA and cleared SPAU queue in QA.

Thanks,

Sunny Thakur