Create Authorization Object Field behaving like ACTVT

[Former Member]

Dear Gurus,

I am currently trying to create authorization object field which should behave like ACTVT. That means when I click to maintain the field, the following window shows up, I can only select some of the values but not inputing free text:

I tried to create authorization object field even directly using the data element from ACTVT (ACTIV_AUTH):

but it still shows window like following (free text input, but not check box):

When I click the search help (F4) button, then I get the following window:

My question is, it it possible to let the field behave eactly like ACTVT? Is it hard coded or I missed something here?

Thanks a lot!

[Former Member]

Hi,

its hardcoded for field ACTVT....

So you need to use ACTVT instead of your Z-field.... But its no problem to use ACTVT in your Z-object.....

b.rgds, Bernhard

[yakcinar]

Hello Deming,

I know that you can add ACTVT field to any custom authorization objects with custom activities.

Why are you trying to create another ZACTVT field?

Regards,

Yuksel AKCINAR

[Former Member]

Hello Yüksel,

yes, you are right, it works if I directly use the ACTVT Field.

But my authorization object delivers different content, not ACTVT content. So I need to create a Z-Object.

Regards,
Deming

[Bernhard_SAP]

Hi,

its hardcoded for field ACTVT....

So you need to use ACTVT instead of your Z-field.... But its no problem to use ACTVT in your Z-object.....

b.rgds, Bernhard

[Former Member]

Hi Bernhard,

thank for your answer.

What a piece of sad news...

My Z-Object should deliver different content but not ACTVT content... ;-(

Regards,

Deming

[yakcinar]

Hello Deming,

This link can help.

Can you also explain your need in detail, if doesn't mind?

Regards,

Yuksel AKCINAR

[Former Member]

Hello Yuksel,

thanks for the link. But it does not help me out, it is only general knowledge for authorization objects which documents the process in a good way via an example. Might be useful if my customer needs to understand SAP authorization deeper.

Due to a IT-Redisgn Project, my customer wants to centrally manage all authorizations from different legacy systems in SAP. So I cannot use SAP standard authorization objects to manage those non-SAP authorizations, but I still want to have the benifit which ACTVT brings (no free text input which avoids input errors).

I will try something else to realize it.

Regards,
Deming