Hide Document Sturucture Field

Hi Gurus
How can we hide the document structure field in DMS tcodes (CV01N/ CV02N/ CV03N/ CV04N)
Regards
Harris

Hi Harris,
Please remove the transactions codes pertaining to Document structure from Authorization profiles viz
CV11                 Create Document Structure
CV12                 Change Document Structure
CV13                 Display Document Structure
This will disable the options atleast.
Hope this helps.
Regards,
Deepak Kori

Similar Messages

SharePoint 2013: Hide/Show Column fields while uploading document in Document Library

Dear all,
I have created a document Library LIB001 and I have created One Column of type Choice, drop down list, (CCHOICE) and I have created 3 other columns, (Column1, Column2, Column3).
What I want is while uploading a file in the document library, when I choose a certain value from CCHOICE, i want to show/hide and/or make the column mandatory.
Can anyone help/guide me how to achieve this?
Many Thanks
Vinay

Dear all, I am trying the following code, but it's not entering the onchange of drop down list event. <script> $(document).ready(function () { var countryField = SPUtility.GetSPField('Document Type'); var countryFieldValue = countryField.GetValue(); alert
(countryFieldValue); // ----- Hide/Show the field based on new selected value. var id = SPUtility.GetSPField('Document Type').Dropdown.id; alert ('field ID: '+id); $('#' + id).on('change', function () { alert ('Inside on Change:'+countryFieldValue); if (countryFieldValue
== 'Type1') { SPUtility.GetSPField('Column1').Hide(); } else if (countryFieldValue == 'Type2') { SPUtility.GetSPField('Column2').Hide(); } }); }); </script> Can anyone help me please. Many Thanks & Regards Vinay

Hide grand total field on ALV report, But keep the sub total fields

Dear Experts,
1) How to hide grand total field on ALV report, But keep the sub total fields.
2) How to populate rate per ton & calculate total price according to the qty in delivering document.

Dear Experts,
1) How to hide grand total field on ALV report, But keep the sub total fields.
2) How to populate rate per ton & calculate total price according to the qty in delivering document.

Hide a standard field

Hello all,
I need to know: is there a way to hide a field in SRM web portal? For example, I know, in SAP ECC there is 'Field Status'; in SAP SRM.
Thanks,
Best Regards,
Maria

Hi,
As I told you the BADI "BBP_UI_CONTROL_BADI" can be used only in some trasnsactions to hide the std fields/links etc.
Pls read the documentation of the BADi:
Field Control in Purchasing Document
Use
Using the Business Add-In BBP_UI_CONTROL_BADI, you can change the visibility and the ready-to-input status of interface objects (for example, fields and pushbuttons) in a document.
You can use the BAdI to override the following documents and applications:
Purchase contract and global outline agreement
(Filter value BUS2000113)
Bid invitation (Filter value BUS2200)
Bid (Filterwert BUS2202)
Auction (Filter value BUS2208)
Purchase order (Filter value BUS2201)
Purchaser's Sourcing application
Confirmation (Filter value BUS2203)
Invoice (Filter value BUS2205)
Vendor list
Note
Changing the ready-to-input status of fields as designated in the standard can lead to errors. You should, therefore, avoid switching the status of a field that is not ready-to-input in the standard to ready-to-input. Do not, for example, set the object ID of an already existing contract to changeable.
Standard settings
Using the following methods of the BAdI, you can control the visibility and ready-to-input status of header and item fields, pushbuttons, and navigation links of the concerned applications and also interface objects of cross-application screens, for example, the partner overview, account assignment, status overview or approval:
BBP_CTR_UI_CTRL
for field control in the contract and in the global outline agreement
BBP_BID_UI_CTRL
for field control in the bid invitation
BBP_QUOT_UI_CTRL
for field control in the bid
BBP_AUC_UI_CTRL
for field control in the auction
BBP_PO_UI_CTRL
for field control in purchase orders, including the screens for purchase order response and price data in the item details.
BBP_AVL_UI_CTRL
for field control in the vendor list.
Using the following methods, you can override the visibility and ready-to-input status of header and item fields, pushbuttons, and navigation links of the relevant application, however not that of interface objects of cross-application screens:
BBP_SOCO_UI_CTRL
for field control in the purchaser's Sourcing application
BBP_CONF_UI_CTRL
for field control in the confirmation
BBP_INV_UI_CTRL
for field control in the invoice
Using the following method, you can set up the mass change transaction in such a way that the previous step need not be completed before the user switches to the next screen.
BBP_CTR_MASS_UI_CTRL
for control of the mass change transaction.
Other then the transactions mentioned above,you need to modify the Std ITS templates(in tcode SE80) to hide the required fields/buttons.For this you first need to find the corresponding ITS service and HTML template for the screen in which you want to remove the button/links from.
E.g.,This is the sample code for Bid invitation screen fields:
*To make the TYPE OF PUBLICATION field under BASIC DATA tab in BI screen as display only
IF iv_fieldname = 'BBPS_BID_UI_HEADER-BID_TYPE'.
cv_input_ready = c_space.
ENDIF.
HTH.
Similarly,You can debug at runtime and see the structures and names for the fields/buttons as per the CATALOGUE screen.
BR,
Disha.
P.S. DO reward points for useful answers.

How to identify relevant BADIs to hide a screen field from specific users

We have a business requirement to hide a document item field (BSEG-XREF3) from specific users (i.e make the field invisible if the userid does not exist in a Z table) during FI invoice entry/maintenance/display via transactions FB01, FB02, FB03, FV50, FV60, FBV0, etc.. We know that it would be possible to do this via modification to the Process Before Output sections of LF040O00, LFDCBFM0, MF05AO00_DYNPRO_MODIFIZIEREN, MF05LO00, but would prefer to avoid modification if possible.
I believe that BADIs could possibly be used for screen enhancements, but have not had any previous exposure to BADIs, so I'm really not sure whether it's possible to use BADIs for our specific requirement. For example, using the advice given in the 2nd post in thread BADI for contract, I've searched SAPMF05A for all 'CALL METHOD cl_exithandler=>get_instance' statements, and have found that a single BADI (FBAS_CIN_MF05AFA0 - EWT - Downpayment Clearing - Tax transfer for CIN) seems to exist for FB01. The description of this BADI sounds completely inappropriate for our requirement. However, subsequent posts in that thread suggest far more BADIs for the relevant transaction than were given when searching the ABAP for all 'CALL METHOD cl_exithandler=>get_instance' statements, so I'm not convinced that the procedure I'm following will provide me with all the relevant BADIs for the transaction.
Please can you advise me how to identify which BADIs - if any - can be used to control screens before output for FB01 screen SAPMF05A/332 (SAP R/3 4.6C)?
Many thanks in anticipation,
Jules

Hi Kuntal,
Thank you very, very much for your prompt response and very useful alternative suggestion.
The screen variant solution would be invaluable under different circumstances, but would be too complex to administer for this particular issue because we're trying to hide the field from unauthorised users in over 100 invoice entry/maintenance/display transactions.
We can make a Process Before Output modification to 4 SAP standard programs (LF040O00, LFDCBFM0, MF05AO00_DYNPRO_MODIFIZIEREN, MF05LO00) to make the field invisible for unauthorised users (i.e. whose user-ids are not in a Z* table), but would prefer to avoid modification if we could use BADIs instead. You've said that you're not sure how we can identify the relevant BADIs, but I very much appreciate the suggestion you've made anyway - it might be useful to others who find themselves in a similar situation for a more limited number of transactions.
Please can someone advise me how to identify which BADIs - if any - can be used to control screens before output for FB01 screen SAPMF05A/332 (SAP R/3 4.6C)?
Many thanks,
Jules

Hide Unwanted Excise Fields in MIGO & J1IEX

In our business process, the duties such as NCCD and SED are not required and consequently we don't want these fields to appear in MIGO and J1IEX so that users can't put any value by mistake.
Can any one provide some idea what the settings required for this?
Thanks in advance

Hi,
To hide some fields in MIGO, NEED to do configuration settings. Then you can hide the required fields. The pathway as follows...
SPRO->SAP REFERENCE IMG->NATERIAL MANAGEMENT->INVENTORY MANAGENET AND PHYSICAL INVENTORY->SETTINGS FOR GOODS MOVEMENT(MIGO)---> FIELD SELECTION FOR MIGO(CHACK THE RADIO BUTTON FOR HIDE AGAINST THE REQUIRED FIELD).
By following path way you can hide the required fields in MIGO.
For J1IEX also there are options to hide the fields. I hope this will clear your issue. Thanking you.

We are trying to do a Quick payment from payment workbench and getting 'FRM-41830: List of values contains no entries' error for payment document column/field. Payment document setup looks good. Not sure what the issue is.

We are trying to do a Quick payment from payment workbench and getting 'FRM-41830: List of values contains no entries' error for payment document column/field. Payment document setup looks good. Not sure what the issue is.

Already gone through following three notes but didn't found resolution.
APXPAWKB: FRM-41830 When Clicking on Payment Document LOV (Doc ID 1081305.1)
R12: APXPAWKB: Payment Document Lov Is Empty When Entering A Payment (Doc ID 857587.1)
R12: Payment Workbench Error: FRM-41830 List Of Values Contains No Entries (APXPAWKB.FMB) (Doc ID 1323875.1)

Reference document number field on Invoice line item

Can anyone please tell me , where in customization , do i define what should get copied in the reference document number field on the line item of an invoice.
Currently in our system, credit memo request number is getting populated for a credit memo.
Thank you for your help in advance.

Hi,
If you are talking about line item level, then it is called Allocation Number. At the header level, it is called Reference number.
This is controlled using the copy control for billing - at the header level control.
The reference number & allocation number once maintained in the configuration, will show up in the Accounting doc - header level & item level, respectively.
For example - if the customer payment always refers to his PO number, then it really helps to use the allocation number for the accounting doc line items - which helps in clearing incoming payment faster. In this case, the reference number could be our delivery number. This is one of the examples for using both Ref & allocation #'s.
Hope, this helps!
S. Siva

Document number field F4 help in transaction cv01n

Hi,
I would like to not display deleted documents in Document Number field search help in CV01n transaction only.
How do I go about doing this?
Regards,
K

Hello,
The search help used for document no is H_TDWA. Add a search help exit to this search help to filter out deleted document numbers. Search sdn for "search help exit" you eill get several links to implement it.
Regards
Vishal Kapoor

In accounting document ..field reference / assignment (invoice no) is empty

Dear all
I opened VF03 and open accounting document saw field reference / assignment (invoice no) is empty because of that field reference (invoice no ) display empty in FBL5N.
Sanj

Its a very basic question.
Based on your sales process.
Refer following copying control header you need to maintain reference & assignement number based on your business requirement.
For your reference.
TCODE
Sales Process
Assignment Number
Reference number
VTFA
order related billing
B-Sales order number
A-Purchase order number
VTFL
delivery related billing
B-Sales order number
A-Purchase order number
Regards
JP

Need a document for field exit....urgent

Can any one please send a document for field exit or have a simple document on how to work on a field exit with screen shots. pls send it ...its urgent
Thanks and regards
Nandha kumar R

Hi,
A field exit is a type of user exit.
A user exit is a hook where you can inject your own add-on functionality or behavior to SAPs standard business applications without having to modify the original applications.
Field exits allow you to create your own programming logic for any data element in the Dictionary. You can use this logic to carry out checks, conversions, or business-related processing for any screen field.
Field Exits
Field exits allow you to create your own programming logic for any data element in the Dictionary. You can use this logic to carry out checks, conversions, or business-related processing for any screen field. Example: The data element BBBNR identifies a companys international location number. You might want to set up your R/3 System so that all international location numbers are larger than 100.
The field exit concept lets you create a special function module that contains this logic.
You assign the special function module to the data element BBBNR. You then assign the module to any programs and screens in which users can add new international location numbers. When you activate your field exit, the system automatically triggers your special routine whenever a user enters a company location number.
In 4.6c, you can use "RSMODPRF" program to create field exits.
An example of a user exits :-
MODULE user_exit_0001 INPUT
    CASE okcode.
        WHEN 'BACK OR EXIT'.
            CASE sy-dynnr.
                    WHEN '100'.
                         SET SCREEN 0.
                         LEAVE SCREEN.
                    WHEN '200'.
Note that you can write any code that satisfy your needs.                                                     ****
But in this case, this was wrote as a sample code for reference sake.                                    ****
And you can test it.                                                                                ****
                         SET SCREEN 100.
                         LEAVE SCREEN.
             ENDCASE.
      ENDCASE.
Field exits (SMOD/CMOD) Questions and Answers
1. Field exit was created with CMOD, but is not processed when calling the screen.
- Since the field exit is not processed until PAI, an action must be triggered on the screen (Return, Save, ...).
- Set profile parameter abap/fieldexit to YES and restart the system.
- After activating the function module FIELD_EXIT... and the field exit, leave the transaction on whose screen the field exit is to be executed. The screen is not generated until the transaction is started.
- Do not work on different application servers since there may be some delay before the field exit is activated.
- The profile parameter must be set on all or none of the application servers.
- If the field exit is to only be active on specific screens, check whether you chose the correct program and the correct screen
      number (take care with subscreens).
- Using SE51 -> Field list, check that the screen field does have a reference to a data element. In the name of the field exit use the name of the data element and not the field name.
- After transport, field exits are marked as active but will not be processed.
   Tip: First try deactivating the field exit once more and then afterwards, activate it again.
2. How is performance affected by setting abap/fieldexit?
- If a screen is generated and the profile parameter is set, a check is run on 2 tables (TDDIR, TDDIRS) to see whether a field exit must be generated for the respective field. In practice, the screen load is not generated until the screen is selected after an
update. The user should not notice any difference because screen generation is very fast.
3. Can you read the contents of other screen fields in the field exit?
- In principle, every field exit can store its value in the global variables of the function group (TOP) and hence make them
available to other field exits. Note here that field exits are always called and not only if an entry is made in the field or if the field is empty. In addition, it is not possible to make any assumptions about the order in which the field exits will be called in the future.
4. How does the field exit behave on step loop fields ?
- After the user has entered data, the field exit is called in PAI as often as there are visible fields in the step loop. The system
variable SY-STEPL is incremented each time. If a new value is assigned to the field, it is displayed in the module between LOOP and ENDLOOP. This module is also called once for each visible step loop line.
5. Can field exits be debugged ?
- No. Field exits must be tested separately in the ABAP/4 Development Workbench. For errors which only occur in the screen environment, it is helpful to write interesting variable to the file system using TRANSFER... . These can then be analysed there.
6. What can you do if the field contents are no longer transported to to ABAP/4.
- Check whether a value is assigned to the field OUTPUT.
7. When is the field exit called if a conversion exit is attached to the
   data element ?
- The field exit is called after the conversion exit. This means that the INPUT field receives the data in the same format as the
ABAP/4 program also receives it.
8. Although a global field exit is inactive, a function module is called which does not exist (for example FIELD_EXIT_PROGRAMM_@)
- This is an error in the kernel which no longer occurs as of 3.0C. As a temporary measure, it is useful to assign a program and a screen which do not exist to the field exit and then activate the field exit.
9. Field exit is not visible in CMOD, although created.
- If you want to create a field exit for a data element, a function module is proposed with the name FIELD_EXIT_. This
function module must exist for the field exit to work. If you do not create this function module, but do create one with a suffix,
the data element is not displayed in CMOD.
10. Field exit is not executed although it is active.
- Fields which do not have the 'Input field' attribute usually do not trigger a field exit. The field exit is designed to allow an
extended input check. It is therefore only called for input fields - even if they are not ready for input at runtime of the         application by LOOP AT SCREEN.
This rule does not apply, however, if the field is located within a steploop. Here the field will be always activated, even if it is
invisible.
- Field exits can only be executed for fields that are directly related tothe dictionary. If the relation is indirect, i.e. via an       ABAP declaration ( LIKE ), no field exit can be executed.
11. Field exits on check buttons do not work
- Field exits are only intended for input fields. As check buttons count as graphical elements, you cannot install field exits on
them.
12. Field exits do not work on selection screens
SAP Field Exits
From 4.6c onwards, Field exits will no more be supported by SAP. They removed the function of field exit but they had given lot of flexibility through userexit.
However, if you still required it, here is how to activate it :-
First called up transaction CMOD.
Then called up transaction PRFB.
or
Activation of the field exits and assignment of the dynpros can also be carried out using program RSMODPRF. For this purpose, the program must be started without parameters (input fields remain blank). If required, new field exits can be created using program RSMODPRF (see the program documentation).
REFER THIS LINK ALSO.
defining screen fields using FIELD-SYMBOL
Thanks,
Shankar

How to hide dynamic selection fields in variants

hi,
When a selection variant is saved, we have the option to 'hide' a selection field. That field may contain a value, but it is not shown on the selection screen. There is, however, a button that will display these hidden field when required.
Is it possible to do this also with dynamic selection fields ?
The column 'Hide field' is shown in the variant atttributes screen, but it is not active.
Please suggest
MS

Explore SHD0 T code

ESS portal: Hide additional info field in release working time screen

Hi,
I need to know how can i hide 'additional info' field in the release working time screen?
I know i would use personalization but don't know the way to do that.

it will be shown in header only in release application, let me explain
In the time recording application, when you enter a record and click
on review, the additional info columns shows the text. This works
because the data is entered by the user and the entered record is
mapped to additional info column.
In time release application, all the records from database are retrieved
and displayed. The user does not enter any data. Hence in this case it
is not possible to map the records to text in the additional info
column. The Error/Warning messages are displayed in the top of the list
with detailed information. We feel the information displayed is
sufficient for the user to take necessary action. Usually in the release
application, there would be lots of records. Displaying text in both
additional info column and also at the top of the list is not a feasible
solution.
Technically it would be difficult for us to change this behavior in the
standard application.
we have new application in EHP5.
Edited by: Siddharth Rajora on Mar 9, 2012 7:10 PM

How to Hide the Parameter field at run time....

Hi,
I have a parameter field which behaves differently depending on the User logged in.
It has the LOV coming from following SQL.
SELECT customer_name FROM Cust_mast;
If the user = 'INTERNAL' then the Where clause will be
WHERE cust_id in('DELL', 'SBC', 'BANK')
Else there will be no WHERE clause or the parameter field
should be hidden in the parameter form.
So my questions are:
1) How to hide the Parameter field during Run time?
OR OR OR
2) How to change the LOV select statement during Run time?
Thanks.
Ram.

Hi Ram,
Is there any way to play with the sql query SELECT using DECODE ?I'm not sure of this part, maybe someone else can suggest a way.
However, what you want can be done in 2 other ways:
1. Build 2 reports. Both reports will just be duplicates of each other, only difference being that the 'LoV where clause' will be different. Now you can fire the appropriate report in many ways. For example, if the customer is alreay logged inside your custom application, and therefore you already know whether the user is internal of external, you can design your button or link which launches the report to contain logic such that one of the 2 reports is fired depending on who the user is.
1. Use a JSP parameter form, not a paper parameter form In this case, just build an HTML parameter form in the web source of your report. Use Java logic to populate the LoV drop-down list. When you have to launch the final report, just launch the paper-layout of the report. For example (you will have to modify this):
<form action="http://machine:port/reports/rwservlet?report=ParamForm.jsp+..." name="First" method="post">
<select name="selected_customer" onChange="First.submit()" >
<option value="">Choose a Customer Name
<rw:foreach id="G_cust_id" src="G_cust_id">
<rw:getValue id="myCustId" src="CUSTOMER_ID"/>
<rw:getValue id="myCustName" src="CUSTOMER_NAME"/>
<option value="<%=myCustId%>"><%=myCustName%>
</rw:foreach>
</select>
</form>
In the code above, you will have to make sure that your report's data model defines 2 CUSTOMER_ID's (like CUSTOMER_ID_INT and CUSTOMER_ID_EXT). These 2 will be internal and external Cust ID's. Use Java logic to show one of them.
Navneet.

How to hide the Parameter field during Run time?

Hi,
How to hide the Parameter field during Run time?
I have a parameter field which behaves differently depending on the User logged in.
I am using reports 10G
For ex: I have 3 field created in JSP
CUSTOMER
PROVIDER
FROM DATE
END DATE
If the user = 'SUPER show all the parameter
CUSTOMER
PROVIDER
FROM DATE
END DATE
If the user is 'GATEKEEPER" Just show
PROVIDER
FROM DATE
END DATE
Can I do that?
Please help
Thanks.
KK

hi, i'm not familiar much with JSP. but i think workaround is to create two window one which have 4 fields and the other which have 3. if user is SUPER then call the first screen otherwise if user is GATEKEEPER then call the second screen.

Hide Document Sturucture Field

Similar Messages

Maybe you are looking for