I didnt get the relevent reply for my query thats why i post again.
Re: How to unlock Users in client from a different client
Re: How to unlock Users in client from a different client
Just review this post from top to bottom, you will get your answers.
Code inspector or test cockpit
Hi all,
I'm having some problems in the company that work. Always compare the current development version with the previous (0010 to 0009 for example) and evaluate only the changes and not the whole. In Cockpit inspector or test code can do this? Another question is whether there is a rule that validates whether the program is new or not. Sorry for English, but I'm using the google translator.
Regards,
Erlon Lourenço
Re: Code inspector or test cockpit
Hi Erlon.
From SE38 you can check the changes between two versions by selecting from Menu-->Utilities-->Versions-->Versions Management.
There you can select the both versions you want to compare and click the Compare button or F8.
Re: Code inspector or test cockpit
Hi Diogo.
Thanks for the feedback Diogo. Today we make the comparison as suggested, but as we are using the code inspector, I would be there to see how to configure it for him to get the current changes with the latest version. It using the code inspector.
Thanks,
Erlon Lourenço
Re: Drop Down is not Visible
Hi,
is it a custom BSP app? It's really hard to say what is causing this issue. If it's a custom app then the logic might not be using only authorizations to determine what is visible to user. Have you traced it in ST01?
Cheers
Re: How to unlock Users in client from a different client
And also it's not necessary nor a good idea to cross-post (how to reset the password of user of different client).
Re: Drop Down is not Visible
Rakesh Navandar wrote:
One HR Manager is synching his id with another user id and then going to the Proxy link to change the employee information for the another user as a proxy manager. Here The user is not able see the drop down to select and Action item to complete job.
The likelihood of the problem being in this part of the coding block and exchanges is very high.
You must consider that "drop downs" are also implemented from remote enabled search helps, and some user in some foreign system might now be subject to a new application authorization to display vendors etc which was not there before.
On EHP7 you can also use SU53 for non-SAPGui applications and get more results back than just the latest check. So run the errors, and then on the backend system check the trace and the Su53 for the connection user whether it can return the data.
Theory B is that the backend table of the dropdown has more records than what a dropdown supports, so a search help is needed but there is no search help passed to the BSP field.
Both are equally likely and cover 90% of EhP7 problems with such fields with remote search helps from the perspective of authorization problems which are "blamed" for the problem.
Cheers,
Julius
Re: Drop Down is not Visible
Re: Drop Down is not Visible
Then it is possibly a coding error which reacts to that rc=4 incorrectly in EHP7. PSIGN=* should have no meaning as it can either be I or E.
'*' should be ignored.
If both trace results are the same, then the coding in the function module must have changed in how it reacts to it, or the calling BSP (looks like it is coming in with a logon ticket from a portal) has implications on the BSP side that dropdowns are not supported anymore in the way it has been coded. Eg. the search help has changed or the structure for the output has changed.
I tip on incompatibility with your BSP. SAP made a few changes to this FM recently...
Is there no BAPI for this?
What we do here is that we classify data objects and have a list of APIs for them. Then we scan our code to check that the call stack comes from the stables APIs and not some FMs which happen to be remote enabled. Same for correct use of methods which contain correct validations and checks - particularly if the data model changes.
You could try to open a customer message with SAP and tell them which FM you are calling, but 90% sure they will say it is not supported and 99,9% sure they will say that your BSP code is the problem.
Try it and let us know (if you did not do that already).
Cheers,
Julius
Re: How to kill process/Actavity in SAP ?
The core file contains the memory state of the work process at the point it was terminated. You could use it for debugging the work process if you had access to the kernel source code, which you don't unless you are SAP. For most people, then, the core file is of no interest and just takes up space in the operating system's file system. Using "cancel without core" is the thing to do.
That said, sometimes I find "cancel without core" doesn't actually work but "cancel with core" does. I always try without core first, but occasionally have to resort to with core. If you do cancel with core, make sure to go and delete the core file afterwards to avoid the file system filling up. Work process core files can be large. You'll find it in a directory/folder here - /usr/sap/SID/DVEBMGS00/work (substitute DVEBMGS00 as appropriate).
Steve.
Re: Personalization Dialog “DIA_LO_SRS”.
Thanks Martin !!
Re: SAP BI analysis authorization combination is not working
Hi Krishna Kumar,
It works like this:
1. When the characteristic 0TCAIPROV is on an Analysis Authorization, and when you have 0COMP_CODE on the "same" AA, the check takes place for AND condition on the values of the 0COMP_CODE on the "same" AA. It "will not" look for 0COMP_CODE in rest of the AAs.
2. If you want to merge the characteristic values from other AAs, leave your 0TCAIPROV on one AA(lets say AA1) and create another AA with 0COMP_CODE values mentioned(lets say AA2) - make sure the AA with 0COMP_CODE doesn't have 0TCAIPROV on it(on AA2) and it should work good.
Try out and let me know.
Regards,
Pranaam
Re: Blocking issue after replacing a SSL certificate ok with a new SSL EV (Extended Validation) one
Issue solved by our SAP Partner Present Milano (currently in test environment) after reference to SSSLERR_SERVER_CERT_MISMATCH and updating kernel patch level and SAP crypto libraries
Timestamp in OM and structural Authorization
Hey Guy's, I've got a question
In our Organisation there are movements from Org1 to Org2.
Org1 is old and in OM it's been validated from 01.01.2010 - 31.08.2014
Org2 is new and is valid from 01.09.2014 - 31.12.9999
Below of Org1 there are Org-Units (Org1.1, Org1.2, ...) which are valid from 01.01.2010 - 31.12.9999.
Now the "under Org-Units" are moved from Org1 to Org2 and the P-Objects, which decided to leave our Organisation till 31.08.2014 aren't anymore in access.
Only the Persons which only have for example Org1.1 in access (no superordinate Org2 or something like that), has access to the P-Objects.
The persons which has Org2 in access, doesn't see via O-S-P the person for the period of time 01.01.2010 - 31.08.2014
It seems like SAP is looking for the timestamp of the 1001 connection between Org1.1 to Org2 (01.09.2014 - 31.12.9999) and not of the P-Object to Org1.1
I have to say, that we are working with an custom table, where we can switch the O-object individually to every person via function block.
We also have the RHBAUS00 with Index listings in use.
Do you understand what I'm trying to explain?
Is it normal for those cases, where an manager decide to create an new Orgunit with an better name, or something like that, and move any "under Org-Units" to the new one, that no person has access anymore?
Is there an switch in T77S0 which I can set or should I try to ask SAP via OSS-Note?
Thanks in advance for your answers
Lars
Re: SAP BI analysis authorization combination is not working
Thanks you so much Collen and Pranam!
I tried the points given by pranam and it worked out. Got more clarity now.
Encryption and Decryption critical fields using 3rd party tools
We are looking at a use case scenario to encrypt certain personnel data (for e.g. Social Security Number or Bank Account No) using AES algorithm. We would like to encrypt and decrypt the personnel data so that unauthorized user won't be able to see the critical data. I know SAP has limitations and it is not straight forward mechanism.
Are there any third party vendors/tools or partners who can provide solution to encrypt/decrypt critical fields. I found one such service provider called "Dolphin" who is SAP Partner too. similarly are there any more such service providers. Please provide the information.
Thanks
Vik
Re: Encryption and Decryption critical fields using 3rd party tools
The best strategy to follow is not to have the data at all, and rather use tokenization services to access the data from a service. Your system only contains a token for the data and at runtime the system retrieves the data via an encrypted webservice call to the service provider.
If you use the SAP built in encryption, then it only supports selected fields (payment cards and credit card data) to encrypt the data in the DB / data browsers. But if user has access to the application or function which decrypts, then they can access the data in plain text. So you have more requirements to protect your application and basis authorizations and client copies.
I am not aware of anything for the US Social Security Number encrytion (either as supported service or encrypted field), however if you take a look on wikipedia you will see that the whole mechanism is about as secure as your birthday in the internet...
Cheers,
Julius
Re: SAP BI analysis authorization combination is not working
Great!! Thanks for confirming.
<"doing the needful" removed by moderator> -> guru can decide for himself.
Regards,
Pranaam
Message was edited by: Julius von dem Bussche
Re: Timestamp in OM and structural Authorization
I can only comment that there is a default tolerance of 15 days built in for OM (which probably triggered your question 20 working days later.
People normally only complain when they loose access... so it could also be a lot of things. Personnel status (select no longer performed) or personnel number changed (IT 0105 no longer matches)?
Unfortunately HR is riddled with macros in the LDBs which you cannot debug easily, but it is always worth a try to see whether your data is the problem or the program.
If you cannot debug it then I would suggest that opening a customer message with SAP is the fastest route.
Little tip: Describe the problem well and suggest the solution after debugging and use priority "low" -> a ninja will find it as a "snack" and fix it very fast or tell you what the problem is... ;-)
Cheers,
Julius