topic Re: Variant CUS&SPEC intended only for background processing in Application Development and Automation Discussions

Variant CUS&SPEC intended only for background processing

Former Member — Tue, 15 Dec 2015 05:21:17 GMT

Hello Experts,

After the Upgrade, one of the Transaction code is throwing this error - Variant intended only for background processing.

This is a System Variant.

Kindly advise how to change the background only mode for System Variants.

Thank you!

-Sowmya

Re: Variant CUS&SPEC intended only for background processing

RaymondGiuseppi — Tue, 15 Dec 2015 06:45:02 GMT

This is not related to the system attribute of the variant, check in development, this is another attribute:

Regards,
Raymond

Re: Variant CUS&SPEC intended only for background processing

karthikeyan_p3 — Tue, 15 Dec 2015 06:49:45 GMT

Hi Sowmya,

All the system variants that start with 'SAP&' or 'CUS&' are stored in client '000'. You cannot directly edit this variant in the production system, if you don't allow it in client administration (SCC4 - Client-Independent Object Changes allowed).

Deactivate the "Background processing" from the variant attribute in development system and save it in transport request & move it to production system.

Thanks,

Karthikeyan

Re: Variant CUS&SPEC intended only for background processing

Former Member — Tue, 15 Dec 2015 07:15:46 GMT

Thanks for the reply Karthik.

Even in Dev System, it didn't allow me to edit. It says the Variant is Protected. I do not have authorization.

How do we see the User id of the variant creator?

-Sowmya

Re: Variant CUS&SPEC intended only for background processing

former_member192467 — Tue, 15 Dec 2015 07:34:05 GMT

Hi,

You can see the details of the variant in table VARID by passig the report name.

Usually for variant maintenance the auth object S_program is used.

To add authorisation u can add auth obj S_PROGRAM with field values

P_ACTION = Variant and P_GROUP = AM*

Regards,

Renjith

Re: Variant CUS&SPEC intended only for background processing

Former Member — Tue, 15 Dec 2015 07:49:07 GMT

Hi Renjith,

These are System Variants. It's not stored in VARID table.

Re: Variant CUS&SPEC intended only for background processing

RaymondGiuseppi — Tue, 15 Dec 2015 07:55:44 GMT

You can un-protect such variant with report RSVARENT. (Bypass authorization, for example when the original creator left.)

Regards,

Raymond

Re: Variant CUS&SPEC intended only for background processing

Former Member — Tue, 15 Dec 2015 08:09:14 GMT

Thanks Ray. But it's not working.

System Variants are not being directly displayed via SE38 / Table, etc.

Hence, it is not detecting the Variant CUS&SP* in RSVARENT report.

Re: Variant CUS&SPEC intended only for background processing

RaymondGiuseppi — Tue, 15 Dec 2015 08:26:05 GMT

Then try z-report of note 709619 - Changing CUS& system variants

NB: system variants are in VARID but in client 000


SELECT * FROM  VARID CLIENT SPECIFIED.

Regards,

Raymond

Re: Variant CUS&SPEC intended only for background processing

Former Member — Tue, 15 Dec 2015 10:24:20 GMT

Thank you very much Ray... That's useful Note.

Re: Variant CUS&SPEC intended only for background processing

Former Member — Thu, 17 Dec 2015 08:34:51 GMT

Hi Ray,

Business Analyst says we need not change the Attributes of the Variant. The functionality requirement is to run it in the background.

This was working fine in 4.6C, but after the upgrade, it is throwing Error.

Any suggestions on this? Please advise.

Thanks & Regards,

Sowmya

Re: Variant CUS&SPEC intended only for background processing

RaymondGiuseppi — Thu, 17 Dec 2015 09:23:49 GMT

Which error(s) is(are) raised, always same error or depends on report executed
Can you compare screen in both versions, are those variants no longer compaatible (so you have to remove the flag, update the variant data and set again the flag before releasing transport)
Did the basis convert the variants during upgrade (look for a log in DIR_PUT\tmp\rasuvar2.<sy-sysid>)

Regards,

Raymond

Re: Variant CUS&SPEC intended only for background processing

Former Member — Fri, 18 Dec 2015 04:02:28 GMT

Hi Ray,

The Error is always same - "Variant CUS&SPE intended only for background processing".

I assumed it might not be compatible & I even tried to create a new Variant with same Values & Attributes. It still throws the same error.

Will it be an issue with SAP Standard Transaction START_REPORT after the Upgrade?

Please advise.

Thanks & Regards,

Sowmya

Re: Variant CUS&SPEC intended only for background processing

RaymondGiuseppi — Fri, 18 Dec 2015 09:47:22 GMT


Business Analyst says we need not change the Attributes of the Variant

So Business doesn't require those variants to be executed interactively, so only use those in SM36/SM37 and nowhere else, you are not allowed to display those from transaction/SA38 and then schedule background execution (F13)

Regards,

Raymond

Re: Variant CUS&SPEC intended only for background processing

Former Member — Fri, 18 Dec 2015 13:15:43 GMT

Ray,

The tcode needs to be run in the foreground, but it will be scheduled later in the background after providing Date values.

Date value is editable for the Users.

Thanks,

-Sowmya

Re: Variant CUS&SPEC intended only for background processing

RaymondGiuseppi — Fri, 18 Dec 2015 13:23:28 GMT

So you MUST remove the flag as already described.