Upgrade Authorisation Objects between 4.6c and ECC 6.0

[Former Member]

Hello Guru's

I am in the early stages of upgrading from 4.6C TO ECC6.0 and I have worked through transaction SU25. During step 2c all of our Z Roles required editing and regenerating, during this step a number of authorisation objects appeared in the roles that I could not find within the individual profiles from SAP_NEW for each release. These objects are F_FAGL_LDR, F_FAGL_SEG, B_BUPA_RLT among others.

Does anyone know how these objects will have been added to the roles at this point in the process ?

Thanks

Simon

[former_member239282]

When you have finished the conversion of profiles to roles, during the step 2C of transaction SU25, all roles that are affected by newly added authorization checks and must be correspondingly supplemented. Edit and regenerate their authorization profiles. The system assigns the status Profile comparison required to the affected roles. (Step 2C uses a traffic light system to display which roles must be checked after an upgrade. For revised roles, the traffic light is green. For roles that have not yet been revised, the traffic light is red. You can call the report repeatedly without overwriting adjustments that you have already made).

Transaction SU25 would have produced no output for profiles. It makes sense to create the roles beforehand, in order to find out which roles authorization checks have been added for.

· Call step 2D to find out if transaction codes have been changed in the new release. You can also download this list to a Microsoft Excel sheet and then remove the old transaction codes during the test phase once the testers are satisfied with the new transactions.

Step 2D uses a traffic light system to display which roles have already been revised after the upgrade. For revised roles, the traffic light is green. For roles that have not yet been revised, the traffic light is red. You can switch the traffic light from red to green by double clicking it. You can call the report repeatedly without overwriting adjustments that you have already made.

In Step 2D, you can use the following pushbuttons to add new transactions to roles or to replace old transactions with new ones:

§ Manually adjust menu

You can manually replace or add transactions.

§ Automatically adjust menu

Old transactions are automatically replaced by new ones.

§ Automatically add menu

You can use this function to add the new transactions to each role. The system checks whether the role already contains each individual transaction. It is only added to the role if this is not the case. In this way, the users can continue using the old transactions until they have had time to learn how to use the new ones.

• if may be useful rewards point are appreciated

[Former Member]

Hi Simon,

In my experience the SAP_NEW<i>release</i> rarely contain all new auth objects.

These new objects will have been updated in the USOB* check indicator tables and pulled through when you edited the roles in default edit mode "read old status & merge with new data" prior to regenerating the roles.

a bit off topic, but the F_FAGL* objects are related to the New G/L functionality & are assigned to a few of the FI posting and balance transactions

[Former Member]

hi, SIMON

could you please mail me the upgrade document

<b><removed by moderator></b>

thanks