Inter Dependent Field Validation in SAP standard TCODEs

Is it possible to build a relationship betwen Screen or Selection Fields. Example Plant and StorageLocation. Default behaviour is SAP shows all possible values even if an interdendent restricting value has been entered - this makes users irritated.
In ABAP it is possible to do Conditional POV on F4 help
- it is tricky you need
'DYNP_VALUES_READ'
'CONVERSION_EXIT_PERI_INPUT'
'DYNP_VALUES_UPDATE'
'F4IF_INT_TABLE_VALUE_REQUEST'
Further Selection screen restrictions can be done by CALL FUNCTION 'SELECT_OPTIONS_RESTRICT'
Hand coded ABAP programs can make Users experience rich & easy.
How to do the same to the best extent possible in all SAP standard TCODES. If a screen field or selection or parameter is filled in then any other screen field selections or parameters should only show restricted values - example Plant if filled in, will show only Storage locations of that plant/plants.
I realize that the way SAP keeps RANGE & SELECTION data with both Inclusive/Exclusive SIGN & complext OPTIONs is not conducive to conditional POV as far as Selection screens are conccerned. But what about EnjoySAp screens?
This is genuine user need & I cannot imagine that there is no easy solution!
For example in a Hospital for Diagnostic tests you enter DEPAERTNET (Xray, Pathology etc) and then TEST - then POV of test should TESTs ONLY of relevant department. Having filled in XRAY no user wants to "wade" through "Urine tests"!
Such restrictions & interfield validations also ensure that processing is never wrong. The mistakes users do are often attributed to the weakness in this area & it is not possible or desirable to write BAdIs for all SAP TCODEs.
Regards
-jnc

Hi,
You the go into debug mode and check at which statement the validation is carried out. (Most of the time it is done by checking the sy-subrc value ). Now put a session breakpoint at this statement. After this every time when the transaction is executed, you can change the value of the variable that is tested and bypass the validation.
But if you are in production system, you wont be authorized to go into debug mode.
Regards,
Bhavesh.

Similar Messages

How to add custom fields to the sap standard program ukm_bp_display

How to add new custom fields to the sap standard program ukm_bp_display .
could u please any one help me on this?

Hello Kumar,
You have to modify below structure, as this structure is providing the field catalog for output display (ALV).
Here you can see there are a lot of include structures, so if you want to add fields in the output display you can add those fileds as an append structure to any of the below mentioned structures (Like ukm_s_account, ukm_s_bp_cms_sgm etc as per your requiremnt and positon at which you need to dispaly your fields.)
DATA: BEGIN OF gt_grid_alv OCCURS 0.
       partner LIKE but000-partner,
       credit_sgmnt LIKE ukmbp_cms_sgm-credit_sgmnt.
        INCLUDE STRUCTURE ukm_s_account.
        INCLUDE STRUCTURE ukm_s_bp_cms_sgm.
DATA:   credit_sgmnt_txt LIKE ukmcred_sgm0t-credit_sgmnt_txt.
      Gruppe Vector
        INCLUDE STRUCTURE ukm_s_bp_vector.
      Gruppe OBL = Obligo
      include structure UKM_S_BP_CMS_MALUSDSP_OUT.
        INCLUDE STRUCTURE ukm_s_display_segment.
        INCLUDE STRUCTURE ukm_s_bp_cms.
        INCLUDE STRUCTURE bus000_dat.
*DATA:   icon(4).
      Gruppe RAST (Raster)
DATA:
         rast01 LIKE ukm_s_display_segment-AMOUNT_GRID,
         rast02 LIKE ukm_s_display_segment-AMOUNT_GRID,
         rast03 LIKE ukm_s_display_segment-AMOUNT_GRID,
         rast04 LIKE ukm_s_display_segment-AMOUNT_GRID,
         rast05 LIKE ukm_s_display_segment-AMOUNT_GRID,
         rast06 LIKE ukm_s_display_segment-AMOUNT_GRID.
DATA:    rast2_6 LIKE ukm_s_display_segment-AMOUNT_GRID.
"Summe raster 2 bis 6
DATA: END OF gt_grid_alv.
Another way is you can go to SE38, and you can create implicit enhancements.One enhancement point is available here in this required area. so create an implementation and add your fileds with data types.This way is also simple.
Hope this will solve yiour problems.
Regards,
Antony Thomas

How to create button in application toolbar in sap standard tcode va03

Hi Gurus,
I want to create a button in the application tool bar of a sap standard tcode : va03.
Can some one help me with this..!
Best Regards,
Navin Fernandes.
Edited by: NAVIN FERNANDES on Aug 12, 2010 10:02 AM
Edited by: NAVIN FERNANDES on Aug 12, 2010 10:07 AM

Go to the coresponding PF status and edit using modification assistant.
http://help.sap.com/saphelp_nw04/helpdata/en/c8/19762743b111d1896f0000e8322d00/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/83/7a18cbde6e11d195460000e82de14a/frameset.htm
Regards,
Nikhil

Facing Problem on Material No field in all the standard TCode

Dear Gurus
I am facing a problem which is like when ever I am trying to fint out the material no of our desire with material text with the Ffour option in Material No field on any of standard report like pending PO material wise party wise r pending pr the Ffour option is nt cming and instead a same material no is cming across all the tcode which is causing us problem to find out the our desire material no. Where as its wrking fine in other usr ids .
Thnz
Subrat

Subrat,
I am a bit confused by your use of abbreviations. However, it sounds like you are having an issue whereby your USERID does not manage the Material Number in the same way that other USERIDs are doing. Pls confirm.
First thing to check are your USERID parameters. SU3 > select parameters tab. Look for any parameter that contains the material number that is plaguing you; if you find one delete the material number from the parameter.
If you don't see the material number, then compare your parameters with the parameters of a user whom you want to emulate. Delete/add parameters from your profile to make yours similar to the 'good' one.
Best Regards,
DB49

HRFORMS - How to add new fields on to SAP Standard Metanet

Hi All
I am working on the Payslip form that is provided as standard
I have the standard meta stars that do not satisfy the requirement entirely.
Can you please let me know how to add more tables/fields to the existing metanet
Thanks

Hi,
There is very nice document from SAP that covers almost everything
http://help.sap.com/printdocu/core/Print46c/EN/data/pdf/PYXXFORM/PYINT_FORMBUILDER.pdf
Cheers

Adding a custom field in a sap standard screen in pa30 for an infotype.

Hi to all..
i'm in a requirement to add a custom field in a standard screen of pa30. for the infotype 0442.
I googled up.. but i was not getting proper solution for it.. can any one provide a solution for it..
With regards.
Aahbha.

Hello Sirs,
Step by step instructions on:
http://help.sap.com/erp2005_ehp_04/helpdata/EN/4f/d52552575e11d189270000e8322f96/frameset.htm
The below thread provide more info on how to create an infotype from scratch, but this is just for the reference:
add custom fields to standard infotype
Regards,
Bentow.

Do you trust the SAP standard rule set ?

Hello all,
I have the impression that, too often, the SAP standard ruleset has been taken for granted : upload, generate and use. Here is a post as to why not to do so. Hopefuly, this will generate a interesting discussion.
As I have previously stated in other threads, you should be very careful accepting the SAP standard rule set without reviewing it first. Before accepting it, you should ensure that your specific SAP environment has been reflected in the functions. The 2 following questions deal with this topic :
1. what is your SAP release ? ---> 46C is different than ECC 6.0 in terms of permissions to be included in the function permission tab. With every SAP release, new authorization objects are linked to SAP standard tcodes. Subsequently some AUTHORITY-CHECK statements have been adapted in the ABAP behind the transaction code. So, other authorizations need to provided from an implementation point of view (PFCG). And thus, from an audit perspective (GRC-CC), other settings are due when filtering users' access rights in search for who can do what in SAP.
2. what are your customizing settings and master data settings ? --> depending on these answers you will have to (de)activate certain permissions in your functions. Eg. are authorization groups for posting periods, business areas, material types, ... being used ? If this is not required in the SAP system and if activated in SAP GRC function, then you filter down your results too hard, thereby leaving certain users out of the audit report while in reality they can actually execute the corresponding SAP functionality --> risk for false negatives !
Do not forget that the SAP standard ruleset is only an import of SU24 settings of - probably - a Walldorf system. That's the reason SAP states that the delivered rule set is a starting point.
So, the best practice is :
a. collect SAP specific settings per connector in a separate 'questionnaire' document, preferably structured in a database
b. reflect these answers per function per connector per action per permission by correctly (de)activating the corresponding permissions for all affected functions
You can imagine that this is a time-consuming process due to the amount of work and the slow interaction with the Java web-based GRC GUI. Therefore, it is a quite cumbersome and at times error-prone activity ...... That is, in case you would decide to implement your questionnaire answers manually. There are of course software providers on the market that can develop and maintain your functions in an off-line application and generate your rule set so that you can upload it directly in SAP GRC. In this example such software providers are particularly interesting, because your questionnaire answers are structurally stored and reflected in the functions. Any change now or in the future can be mass-reflected in all (hundreds / thousands of) corresponding permissions in the functions. Time-saving and consistent !
Is this questionnaire really necessary ? Can't I just activate all permissions in every function ? Certainly not, because that would - and here is the main problem - filter too much users out of your audit results because the filter is too stringent. This practice would lead too false negatives, something that auditors do not like.
Can't I just update all my functions based on my particular SU24 settings ? (by the way, if you don't know what SU24 settings are, than ask your role administrator. He/she should know. ) Yes, if you think they are on target, yes you can by deleting all VIRSA_CC_FUNCPRM entries from the Rules.txt export of the SAP standard rule set, re-upload, go for every function into change mode so that the new permissions are imported based on your SU24 settings. Also, very cumbersome and with the absolute condition that you SU24 are maintained excellent.
Why is that so important ? Imagine F_BKPF_GSB the auth object to check on auth groups on business areas within accounting documents. Most role administrator will leave this object on Check/Maintain in the SU24 settings. This means that the object will be imported in the role when - for example - FB01 has been added in the menu. But the role administrator inactivates the object in the role. Still no problem, because user doesn't need it, since auth groups on business areas are not being used. However, having this SU24 will result in an activated F_BKPF_GSB permission in your GRC function. So, SAP GRC will filter down on those users who have F_BKPF_GSB, which will lead to false negatives.
Haven't you noticed that SAP has deactivated quite a lot of permissions, including F_BKPF_GSB ? Now, you see why. But they go too far at times and even incorrect. Example : go ahead and look deeper into function AP02. There, you will see for FB01 that two permissions have been activated. F_BKPF_BEK and F_BKPF_KOA. The very basic authorizations needed to be able to post FI document are F_BKPF_BUK and F_BKPF_KOA. That's F_BKPF_BUK .... not F_BKPF_BEK. They have made a mistake here. F_BKPF_BEK is an optional auth object (as with F_BKPF_GSB) to check on vendor account auth groups.
Again, the message is : be very critical when looking at the SAP standard rule set. So, test thoroughly. And if your not sure, leave the job to a specialized firm.
Success !
Sam

Sam and everyone,
Sam brings up some good points on the delivered ruleset. Please keep in mind; however, that SAP has always stated that the delivered ruleset is a starting point. This is brought up in sap note 986996     Best Practice for SAP CC Rules and Risks. I completely agree with him that no company should just use the supplied rules without doing a full evaluation of their risk and control environment.
I'll try to address each area that Sam brings up:
1. Regarding the issue with differences of auth objects between versions, the SAP delivered rulset is not meant to be version specific. We therefore provide rules with the lowest common denominator when it comes to auth object settings.
The rules were created on a 4.6c system, with the exception of transactions that only exist in higher versions.
The underlying assumption is that we want to ensure the rules do not have any false negatives. This means that we purposely activate the fewest auth objects required in order to execute the transaction.
If new or different auth object settings come into play in the higher releases and you feel this results in false positives (conflicts that show that don't really exist), then you can adjust the rules to add these auth objects to the rules.
Again, our assumption is that the delivered ruleset should err on the side of showing too many conflicts which can be further filtered by the customer, versus excluding users that should be reported.
2. For the customizing settings, as per above, we strive to deliver rules that are base level rules that are applicable for everyone. This is why we deliver only the core auth objects in our rules and not all. A example is ME21N.
If you look at SU24 in an ECC6 system, ME21N has 4 auth objects set as check/maintain. However, in the rules we only enable one of the object, M_BEST_BSA. This is to prevent false negatives.
3. Sam is absolutely right that the delivered auth object settings for FB01 have a mistake. The correct auth object should be F_BKPF_BUK and not F_BKPF_BEK. This was a manual error on my part. I've added this to a listing to correct in future versions of the rules.
4. Since late 2006, 4 updates have been made to the rules to correct known issues as well as expand the ruleset as needed. See the sap notes below as well as posting Compliance Calibrator - Q2 2008 Rule Update from July 22.
1083611 Compliance Calibrator Rule Update Q3 2007
1061380 Compliance Calibrator Rule Update Q2 2006
1035070 Compliance Calibrator Rule Update Q1 2007
1173980 Risk Analysis and Remediation Rule Update Q2 2008
5. SAP is constantly working to improve our rulesets as we know there are areas where the rules can be improved. See my earlier post called Request for participants for an Access Control Rule mini-council from January 28, 2008. A rule mini-council is in place and I welcome anyone who is interested in joining to contact me at the information provided in that post.
6. Finally, the document on the BPX location below has a good overview of how companies should review the rules and customize them to their control and risk environment:
https://www.sdn.sap.com/irj/sdn/bpx-grc
Under Key Topics - Access Control; choose document below:
    o GRC Access Control - Access Risk Management Guide   (PDF 268 KB)
The access risk management guide helps you set up and implement risk
identification and remediation with GRC Access Control.

Set search help dynamically to SAP Standard Screen

Hi,
I have one issue where I have to Create f4 help For a field present on SAP standard screen.
Please advice how to do that.
Can i dynamically set Search help in any screen-exit of the standard screen?
Please help.
Screen No is 130
and Program is SAPLQM03.
Here I want to attach a Zsearch help to a standard FIELD RQM01-LS_KDPOS.
Thanks,
Ishani

Hi Ishani,
The field that you mentioned here in structure RQM01 is having a check table VBUP. So if some values are there in that table, then that will appear as F4 help to you. Consult with your functional and check how values are coming to this table VBUP. Othertahn this, I am afraid you will not be able attach any help.
Regards,
Abijith

SAP Standard ESS country structure not showing on the iViews

Hi All,
Some of the Fields in the SAP Standard Employee Self Service Country structure not showing on the iViews, if we want to bring those fields to iView level, What would be the solution.
Please suggest.
Thanks
PRadeep

Hi Pradeep
If these are mandatory fields or legall required in that country and delivered in V_T588M or V_T588MFPROPS then you need to check with SAP why they are not shown in the ESS scenario
If these are optional or R3 specific fields it could be they are not delivered in V_T588MFPROPS - try inserting
an overide in V_T588MFPROPC
If still you cannot get these fields you may need to add a field to the ESS application using NWDI
and you may also need to change the model so it recognises the new field - this is effectively changing
the SAP delivery
Best regards
Stuart

Standard tcode naming pattern

Hi all!
As we are all familiar, SAP standard tcodes have some naming patterns. I have found this website (http://www.geocities.com/SiliconValley/Program/8650/trantips.htm) which contains good tips about this pattern.
However, it has more details related to Finance tcodes. Do you know any other references regarding the topic?
Thank you!

Hi Thanks for sharing the info....
I would like to add to this......
GO to Transaction SE93
and search for the required module like this
F* -
Finance
M* -
Materail
V*-------SD
FK
MK
XK
XD
MB
MR
ME
ME1
ME2
MM
VA
VF
FS
FB
O...........etc
Reward Points if useful
Thanks & Regards
vinsee

Query in Field Not updated in SAP Standard.

hi
friends
here is my query
In SAP standard one field is not updated in tcode ME11(Create Info Record) table is EINA --LMEIN, The field is currently in suppress mode,and it is blank now.
Can we able to update this field during debug,or any other way.
Plz give me some appropirate suggestion.
Thanks a lot in Advance.
mrutyun^

If you dont have any screen validations on this field, then you can update (via debug mode) from SE16 for respective record.
As the screen is suppressed you need to first enable the screen in PBO while in debug, then you can enter the values.
Cheers
Manohar

Modify SAP standard fields in an Infotype

Hi friends!
We have enhanced an Infotype successfully added few extra fields and they work perfectly.
In Infotype 28, there are already 3 SAP standard fields and we have added 4 more.
Now, we need to enable/disable according to the our added fields. For Eg by a Custom check box, I need to enable/disable SAP standard field for an infotype.
We tried by LOOP at SCREEN and all but due to SAP standard fields we are unable to do it.
Any ideas?
Please help.
Thanks.

Hi Park,
Standard Infotype Fields configured (enable/disabled/hidden) in the view V_T588M (Tcode-SM30). You can disable any standard infotype field here if it is independent of other fields (i.e. before screen opens itself field is disabled).
If you want the field to be disable at runtime you may need to edit the feature 'PNNNN' (where NNNN is your standard infotype number (transaction -pe03)).
Also have you tried to code (loop at screen. endloop) in badi HRPAD00INFTY (method BEFORE_OUTPUT). I am not sure whether this will work or not.
Regards,
Shrinivas

How to freeze fields on standard Tcodes.

Dear SAP Guru
Can any one plz let me know how to freeze the fields on standars T-codes, as i want our end users to use only particular fields on standard tcodes in SAP
Thanks in Advance
Bhushan

[http://theguruspeaksaboutsap.blogspot.com/2007/12/creation-of-variant-for-making.html]
use transaction SHD0 as in the above link

Adding a new SAP standard field to complaints result BOL

Hi Experts,
There is a requirement to add SAP standard field 'Posting date' to Advance search result BOL of complaints.
This field already exists in search BOL and visible on WEB UI advanced search.
The field is added as attribute in result context node of BT120S_CPL/AdvSearchComplRL through wizard.
But, unable to see the values getting populated. Could you please let us know if any code to be written for getting values populated.
Regards,
Santosh

Hi Santosh ,
My previous post was based on the fact that you have added a model attribute. Since you have added the field as a value attribute and you want to use it for querying , then you would have to do the following
a) Extract the value from the value node.
b) Add the selection param so that 'posting date' is passed to the GENIL. You can use add selection param method in the Advanced query. Use the name of the field in the BOL & the value as yours.
c) Get the result & show it on the way you want.
This is same as it would have been when you had a model field. In that case also you would have extracted the value from model node. I see no difference here except that fetching the field. Rest of the steps remain the same if the field is available in BOL for advanced query.
Yes the difference lies in showing it in the WebUI as now you would have to fill this value node manually. If you had a model node , the framework would have done this for you.
But don't base your choice of model/value node on the ease of coding but on the business case.
Regards
Kavindra

How to change the lenth of existing field in sap standard table

Hi all,
can anybody help,my requirement is, how to change the length of existing field in sap standard table....
thanks in advance..

Which field are you thinking of in particular? Are you wanting to increase or decrease the length?
Some fields are used so extensively that a change to their length will mean adjusting many tables, some of them potentially very large, and hence taking a long time to adjust.
Some standard SAP programs expect certain fields to be of specific lengths and won't work if the length is changed.
Some screens could cease to work.
If you decrease length, then you could lose data.
matt

Inter Dependent Field Validation in SAP standard TCODEs

Similar Messages

Maybe you are looking for