Hide bank number field from all transaction code

Hi ABAP Gurus,
we have requirement to hide bank number from all sap transaction codes in display mode only.
Is there any way we can do it through configuration .
Thanks,
Troy,

On 13 Dec 2006 in macromedia.dreamweaver.appdev, AdonaiEchad
wrote:
> How do I do that? I can only change what is on the page
not the
> mysql tables on the mysql server.
Set '3' as the default value for the MySQL field, and don't
do anything
with it on the insert
Joe Makowiec
http://makowiec.net/
Email:
http://makowiec.net/email.php

Similar Messages

  • Set the default field value to transaction code field, when calling from WD

    Hi all,
    Can we pass the value in a input field of a standard transaction calling from WD application. Suppose we are calling a transaction VA03 in an external window, then how will be pass the value in the VBAK_VBELN screen field.
    Is there any way to pass the value to this transaction field. I have also tried out to set the parameter ID 'AUN' for VA03 transaction VBELN field. But it did not work for me.
    Is there any way to set the default field value to transaction code field, when calling from WD?
    Please suggest, if anyone have any idea.
    Thanks
    Sanket

    Hi,
    I am using the below code to open a standard transaction. It will help you to explain my point more easily.
    DATA: url TYPE string,
              host TYPE string,
              port TYPE string.
    *Call below method to get host and port
      cl_http_server=>if_http_server~get_location(
         IMPORTING host = host
                port = port ).
    *create URL
      CONCATENATE 'http'
      '://' host ':' port
      '/sap/bc/gui/sap/its/webgui/?sap-client=&~transaction=' 'VA03'
       INTO url.
    *get the window manager as we are opening t code in external window.
      DATA lo_window_manager TYPE REF TO if_wd_window_manager.
      DATA lo_api_component TYPE REF TO if_wd_component.
      DATA lo_window TYPE REF TO if_wd_window.
      lo_api_component = wd_comp_controller->wd_get_api( ).
      lo_window_manager = lo_api_component->get_window_manager( ).
    call the url which we created above
      lo_window_manager->create_external_window(
      EXPORTING
      url = url
      RECEIVING
      window = lo_window ).
      lo_window->open( ).
    Note*
    One more query I want to add to this thread, that is there any possibility to call a custom transaction as well?

  • Hi, all transactions codes are saved in which table?some transaction codes?

    hi,
    all transactions codes are saved in which table?i want some transaction codes?

    All transaction codes are stored in table TSTC. Their texts are displayed in TSTCT.
    Here are some T-CODE's..
    OSS1      SAP Online Service System
    OY19      Compare Tables
    S001      ABAP Development Workbench
    S002      System Administration.
    SA38      Execute a program.
    SCAT      Computer Aided Test Tool
    SCU0      Compare Tables
    SE01      Old Transport & Corrections screen
    SE09      Workbench Organizer
    SE10      Customizing Organizer
    SE10      Customizing organizer – requests for user (To release for transport – enter user name, press Enter. Select changed object and select ReleaseSE10 New Transport & Correction screen
    SE11      ABAP/4 Dictionary Maintenance SE12 ABAP/4 Dictionary Display SE13 Maintain Technical Settings (Tables)
    SE11      ABAP/4 Dictionary.
    SE12      Dictionary: Initial Screen – enter object name
    SE13      Access tables in ABAP/4 Dictionary.
    SE14      ABAP/4 Dictionary: Database Utility.
    SE14      Utilities for Dictionary Tables
    SE15      ABAP/4 Repository Information System
    SE15      ABAP/4 Repository Information System.
    SE16      Data Browser
    SE16      Data Browser: Initial Screen.
    SE16      Display table contents
    SE17      General Table Display
    SE30      ABAP/4 Runtime Analysis
    SE30      ABAP/4 Runtime Analysis: Initial Screen.
    SE30      Run Time Analysis (press Tips and Tricks button for good stuff)
    SE32      ABAP/4 Text Element Maintenance
    SE35      ABAP/4 Dialog Modules
    SE36      ABAP/4: Logical Databases
    SE37      ABAP/4 Function Library.
    SE37      ABAP/4 Function Modules
    SE38      ABAP Editor
    SE38      ABAP/4 Editor.
    SE38      ABAP/4 Program Development
    SE39      Splitscreen Editor: Program Compare
    SE41      Menu Painter
    SE43      Maintain Area Menu
    SE51      Screen Painter
    SE51      Screen Painter: Initial Screen.
    SE54      Generate View Maintenance Module
    SE61      R/3 Documentation
    SE62      Industry utilities
    SE63      Translate Short/Long Text.
    SE63      Translation
    SE64      Terminology
    SE65      R/3 documents. Short text statistics SE66 R/3 Documentation Statistics (Test!)
    SE68      Translation Administration
    SE71      SAPscript layout set
    SE71      SAPscript Layouts Create/Change
    SE72      SAPscript styles
    SE73      SAPscript font maintenance (revised)
    SE74      SAPscript format conversion
    SE75      SAPscript Settings
    SE76      SAPscript Translation Layout Sets
    SE77      SAPscript Translation Styles
    SE80      ABAP/4 Development Workbench
    SE80      Repository Browser: Initial Screen.
    SE81      SAP Application Hierarchy
    SE82      Customer Application Hierarchy
    SE84      ABAP/4 Repository Information System
    SE85      ABAP/4 Dictionary Information System
    SE86      ABAP/4 Repository Information System
    SE87      Data Modeler Information System
    SE88      Development Coordination Info System
    SE91      Maintain Messages
    SE92      Maintain system log messages
    SE93      Maintain Transaction Codes
    SE93      Maintain Transaction.
    SEU      Object Browser
    SHD0      Transaction variant maintenance
    SM04      Overview of Users (cancel/delete sessions)
    SM04      Overview of Users.
    SM12      Deletion of lock entries (in the event you have you are locked out).
    SM12      Lock table entries (unlock locked tables)
    SM21      View the system log, very useful when you get a short dump. Provides much more info than short dump
    SM30      Maintain Table Views.
    SM31      Table Maintenance
    SM32      Table maintenance
    SM35      View Batch Input Sessions
    SM37      View background jobs
    SM50      Process Overview.
    SM51      Delete jobs from system (BDC)
    SM62      Display/Maintain events in SAP, also use function BP_EVENT_RAISE
    SMEN      Display the menu path to get to a transaction
    SMOD/CMOD      Transactions for processing/editing/activating new customer enhancements.
    SNRO      Object browser for number range maintenance.
    SPRO      Start SAP IMG (Implementation Guide).
    SQ00      ABAP/4 Query: Start Queries
    SQ01      ABAP/4 Query: Maintain Queries
    SQ02      ABAP/4 Query: Maintain Funct. Areas
    SQ03      ABAP/4 Query: Maintain User Groups
    SQ07      ABAP/4 Query: Language Comparison
    ST05      Trace SQL Database Requests.
    SU53      Display Authorization Values for User.
    Human Resources
    PA03      Change Payroll control record
    PA20      Display PA Infotypes
    PA30      Create/Change PA Infotypes
    PP02      Quick Entry for PD object creation
    PU00      Delete PA infotypes for an employee. Will not be able to delete an infotype if there is cluster data assigned to the employee.
    Sales and Distribution (SD)
    OLSD      Config for SD. Use Tools-Data Transfer-Conditions to setup SAP supplied BDC to load pricing data
    VA01      Create Sales/Returns Order Initial Screen
    VB21      Transaction for Volume Lease Purchases (done as a sales deal)
    VK15      Transaction used to enter multiple sales conditions (most will be entered here)
    VL02      Deliveries
    SAP Office
    SO00      send a note through SAP, can be sent to Internet, X400, etc
    Financial Accounting (FI)
    FGRP      Report Writer screen
    FM12      View blocked documents by user
    FST2      Insert language specific name for G/L account.
    FST3      Display G/L account name.
    KEA0      Maintain operating concern.
    KEKE      Activate CO-PA.
    KEKK      Assign operating concern.
    KL04      Delete activity type.
    KS04      Delete a cost centre.
    KSH2      Change cost centre group – delete.
    OBR2      Deletion program for customers, vendors, G/L accounts.
    OKC5      Cost element/cost element group deletion.
    OKE1      Delete transaction data.
    OKE2      Delete a profit centre.
    OKI1      Determine Activity Number: Activity Types (Assignment of material number/service to activity type)
    OMZ1      Definition of partner roles.
    OMZ2      Language dependent key reassignment for partner roles.
    Material Management (MM)
    MM06      Flag material for deletion.
    OLMS      materials management configuration menu, most of the stuff under this menu is not under the implementation guide
    MM configuration transactions
    OLMB      Inventory management/Physical Inventory
    OLMD      MM Consumption-Based Planning
    OLME      MM Purchasing
    OLML      Warehouse Management
    OLMR      Invoice Verification
    OLMS      Material Master data
    OLMW      MM Valuation/Account Assignment
    Configuration related
    OLE      OLE demo transaction
    OLI0      C Plant Maintenance Master Data
    OLI1      Set Up INVCO for Material Movements
    OLI8      Set Up SIS for Deliveries
    OLIA      C Maintenance Processing
    OLIP      C Plant Maintenance Planning
    OLIQ      New set-up of QM info system
    OLIX      Set Up Copying/Deleting of Versions
    OLIY      Set Up Deletion of SIS/Inter.Storage
    OLIZ      Stat Set Up INVCO: Invoice Verify
    OLM2      Customizing: Volume-Based Rebates
    OLMB      C RM-MAT Inventory Management Menu
    OLMD      C RM-MAT MRP Menu
    OLME      C MM Menu: Purchasing
    OLML      C MM Menu for Warehouse Management
    OLMR      C RM-MAT Menu: Invoice Verification
    OLMS      C RM-MAT Master Data Menu
    OLMW      C RM-MAT Valuation/Acct. Asset. Menu
    OLPA      SOP Configuration
    OLPE      Sales order value
    OLPF      SPRO Start SAP IMG (Implementation Guide).
    OLPK      Customizing for capacity planning
    OLPR      Project System Options
    OLPS      Customizing Basic Data
    OLPV      Customizing: Std. Value Calculation
    OLQB      C QM QM in Procurement
    OLQI      Analysis OLVD C SD Shipping Menu
    OLVF      C SD Billing Menu
    OLQM      Customizing QM Quality Notifications
    OLQS      C QM Menu Basic Data
    OLQW      C QM Inspection Management
    OLQZ      Quality Certificates
    OLS1      Customizing for Rebates
    OLSD      Customizing: SD
    OLVA      C SD Sales Menu           
    OLVS      C SD Menu for Master Data
    Regards,
    Pavan

  • Orders, deliv. and conRel fields in MD04 transaction code

    Hi All,
    I want to know the database tables and fields for Orders, deliveries and conrel fields in MD04 transaction code.
    In MD04 if you give material and plant as input details and say continue, we are getting the Stock requirement list. In that MRP elements : Orders, deliveries and conrel  and the quantity fields against to these elements ,, from where we are getting the data. Is there any function modules for the same?
    Kindly advice me.
    Thanks in advance.
    Regards
    Ramesh.

    Hi Ram Kumar,
    I'm not sure about the screen enhancements can be done for the transaction FBCJ as we don't have any screen exits.
    But we have only BAdI for FBCJ transaction called CJ_DOCUMENT - Change to External Document before Cash Journal Doc. Check.
    Workaround on the method CHANGE with the changing parameter C_ITCJ_SPLIT_POSTINGS.
    Enhance the structure ISCJ_POSTINGS to add your new fields and write the logic in the BAdI method to populate the values to these fields.
    Please give a try and let us know.
    Regards
    Gangadhar
    Message was edited by: Gangadhar Ragula

  • Need all transaction codes for idocs

    need all transaction codes for idocs

    Hi,
    ALE IDOC
    Sending System(Outbound ALE Process)
    Tcode SALE ? for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 ? Create Model View
    Tcode BD82 ? Generate partner Profiles & Create Ports
    Tcode BD64 ? Distribute the Model view
    Message Type MATMAS
    Tcode BD10 ? Send Material Data
    Tcode WE05 ? Idoc List for watching any Errors
    Receiving System(Inbound ALE )
    Tcode SALE ? for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 ? Check for Model view whether it has distributed or not
    Tcode BD82 -- Generate partner Profiles & Create Ports
    Tcode BD11 Getting Material Data
    Tcode WE05 ? Idoc List for inbound status codes
    ALE IDOC Steps
    Sending System(Outbound ALE Process)
    Tcode SALE ?3 for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 !V Create Model View
    Tcode BD82 !V Generate partner Profiles & Create Ports
    Tcode BD64 !V Distribute the Model view
    This is Receiving system Settings
    Receiving System(Inbound ALE )
    Tcode SALE ?3 for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 !V Check for Model view whether it has distributed or not
    Tcode BD82 -- Generate partner Profiles & Create Ports
    Tcode BD11 Getting Material Data
    Tcode WE05 !V Idoc List for inbound status codes
    Message Type MATMAS
    Tcode BD10 !V Send Material Data
    Tcode WE05 !V Idoc List for watching any Errors
    1)a Goto Tcode SALE
    Click on Sending & Receiving Systems-->Select Logical Systems
    Here Define Logical Systems---> Click on Execute Button
    go for new entries
    1) System Name : ERP000
    Description : Sending System
    2) System Name : ERP800
    Description : Receiving System
    press Enter & Save
    it will ask Request
    if you want new request create new Request orpress continue for transfering the objects
    B) goto Tcode SALE
    Select Assign Client to Logical Systems-->Execute
    000--> Double click on this
    Give the following Information
    Client : ERP 000
    City :
    Logical System
    Currency
    Client role
    Save this Data
    Step 2) For RFC Creation
    Goto Tcode SM59-->Select R/3 Connects
    Click on Create Button
    RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
    give the information for required fields
    RFC Destination : ERP800
    Connection type: 3
    Description
    Target Host : ERP000
    System No:000
    lan : EN
    Client : 800
    User : Login User Name
    Password:
    save this & Test it & RemortLogin
    3)
    Goto Tcode BD64 -- click on Change mode button
    click on create moduleview
    short text : xxxxxxxxxxxxxx
    Technical Neme : MODEL_ALV
    save this & Press ok
    select your just created modelview Name :'MODEL_ALV'.
    goto add message type
    Model Name : MODEL_ALV
    sender : ERP000
    Receiver : ERP800
    Message type :MATMAS
    save & Press Enter
    4) Goto Tcode BD82
    Give Model View : MODEL_ALV
    Partner system : ERP800
    execute this by press F8 Button
    it will gives you sending system port No :A000000015(Like)
    5) Goto Tcode BD64
    seelct the modelview
    goto >edit>modelview-->distribute
    press ok & Press enter
    6)goto Tcode : BD10 for Material sending
    Material : mat_001
    Message Type : MATMAS
    Logical System : ERP800
    and Execute
    7)goto Tcode : BD11 for Material Receiving
    Material : mat_001
    Message Type : MATMAS
    and Execute --> 1 request idoc created for message type Matmas
    press enter
    Here Master Idoc set for Messge type MATMAS-->press Enter
    1 Communication Idoc generated for Message Type
    this is your IDOC
    Change Pointers
    I know how to change the description of a material using ALE Change Pointers.
    I will give the following few steps
    1) Tcode BD61---> check the change pointers activated check box
    save and goback.
    2) Tcode BD50---> check the MATMAS check box save and comeback.
    3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
    4) Tcode BD52---> give message type : matmas press ok button.
    select all what ever you want and delete remaining fields.
    save & come back.
    5) 5) go to Tcode MM02 select one material and try to change the description and save it
    it will effects the target systems material desciption will also changes
    6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
    give Message type : MATMAS and Executte
    ALE/IDOC Status Codes/Messages
    01 Error --> Idoc Added
    30 Error --> Idoc ready for dispatch(ALE Service)
    then goto SE38 --> Execute the Program RBDMIDOC
    29 Error --> ALE Service Layer
    then goto SE38 --> Execute the Program RSEOUT00
    03 Error --> Data Passed to Port ok
    then goto SE38 --> Execute the Program RBDMOIND
    12 Error --> Dispatch ok
    Inbound Status Codes
    50 Error --> It will go for ALE Service Layer
    56 Error --> Idoc with Errors added
    51 Error --> Application Document not posted
    65 Error --> Error in ALE Service Layer
    for 51 or 56 Errors do the following steps
    goto WE19 > give the IDOC Number and Execute>
    Press on Inbound function Module
    for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
    BAPI tcode --- BAPI.
    Also:
    IDOC:
    IDOC ADMINISTRATION
    WE09 / WE02 IDoc lists according to content. View IDocs via specific IDoc number or business application detail contained within the contents of a segment.
    WE05 View IDocs
    WE60 IDoc type documentation tool
    WE20 Partner profile configuration. Add partner detail together with inbound and outbound relationships. We also incorporate message control on the outbound IDocs. Utilize the organizational units to trap functional errors for further processing.
    BD87 Reprocess IDocs in error or waiting for action. (Both inbound and outbound in 4.6. Use BD88 in prior versions)
    1.4 IDOC DEVELOPMENT
    BD55 Conversion rule user exit. Link conversion rule user exit to the different system \ partner combinations.
    WE19 EDI test tool. Use to test inbound Function module changes.
    WE31 Segment create
    WE30 Create IDoc extension type
    WE82 Link Release detail to Extension IDoc Type
    WE57 Assign function module to logical message and IDoc type
    BAPI: BAPI, SWO1.
    Transaction codes Related for IDOC Configurations
    WEDI: Area Menu for IDOC’s
    WE02: Display IDoc
    WE19: ALE Test tool
    WE30: Development of IDOC Type
    WE31: Development of IDOC Segment
    WE41: Process Codes, Outbound
    WE42: Process Codes, Inbound
    WE47: Status Maintenance
    WE81: Logical Message Types
    WE57: Assignment Messages for Appl. Objs
    SM59: RFC Destinations (Display/Maintain)
    SALE: Display ALE Customizing
    BD54: Maintaining Logical Systems
    BD67: Maintain methods (inbound)
    BD64: Maintenance of Distribution Model
    BD87: Status Monitor for ALE Messages
    Reward points if found helpful...
    Cheers,
    Chandra Sekhar.

  • Bank number field compulsory in FI01

    Hi
    While defining bank masters in FI01, i want to make Bank Number field compulsory. Let me know how to do it ?
    Edited by: Meenu_ND on Jun 21, 2010 3:51 PM

    Hi,
    As bank name field is mandatory in bank key transaction which is not flowed through any field status which we can set. it is in build in the program..so if you want to make any field mandatory then you may have to add routines...ask your ABAPer
    It will be a change in standard program which is not recommended.
    Regards,
    Chintan Joshi

  • Short cut assign all transactions code to a user, restrict only few tr code

    Hi,
    I know how to assign transaction code to user, and restrict transaction codes to the user through pfcg assigning role.
    If I want to assign all transaction codes to a user except say su01, and pfcg, then I have to write all the transaction codes to a profile assigned to the user except pfcg and su01, which is a tedious job.  Thus is there any way like in sap_all if I can exclude only those transaction codes which I want to exclude to a user. 
    No one would like to write down 1000 tr code assigned to a user. Is there a short and better way?
    Thanks
    syed

    Create a new role using PFCG go to the authorization tab and use the sap_all template and remove the authorizations for the transaction you don't want to assign.
    Thats it
    Regards
    Juan

  • Hide a library object from all but selected users

    Perhaps I just missed this in the documentation, but is there a way to hide
    a library object from all but selected users who will have access to the
    docs in that library. I know I can uncheck access rights and assign them
    only for selected users who can access the documents, but I would like to
    hide the ibrary object as well, best that only those who have access even
    know the library exisits in this case. Thanks.

    PatM wrote:
    > Thanks to all for your comments and confirmation--I think this is worthy of
    > an enhancement request, and I will put one in. Anyone else who thinks it is
    > a good idea, your support is appreciated. In the case of a library for
    > something like the human resource or finance department, I think it is
    > pretty important, as one cannot rely on an individual user to set the rights
    > correctly for just those documents in the real world of the work-a-day rush.
    How do you give this support? This is a real issue with us as we
    generate information that affects the price and "tradeability" of public
    companies.
    If it's only moral support -- you got it.
    If you have to "vote" on these issues -- how?
    > "Dave Parkes" <[email protected]> wrote in message
    > news:[email protected]..
    >> If there is, I don't know of it. Removing all the rights is as far as you
    >> can go I think.
    >>
    >> I'd probably still just use document rights within a single library. If
    >> these people who can access this library don't have their default set to
    >> it, then things will end up in the wrong place anyway. Not a fan of
    >> multiple active libraries, docs are inevitably in the wrong one <g>
    >>
    >> Cheers Dave
    >>
    >>
    >> --
    >> Dave Parkes [NSCS]
    >> Occasionally resident at http://support-forums.novell.com/
    >
    >
    Will R
    PMC Consulting

  • Need all transaction codes related to SD and MM

    hi
    i am in need of need all transaction codes related to SD and MM.
    can anyone help me to get it.
    thanks in advance.

    Hi,
    The most frequently used transaction codes are as follows:
    1. VS00 - Master data
    2. VC00 - Sales Support
    3. VA00 - Sales
    4. VL00 - Shipping
    5. VT00 - Transportation
    6. VF00 - Billing
    Others as follows:
    At Configuration:
    1. VOV8 - Define Sales documents type (header)
    2. OVAZ - Assigning Sales area to sales documents type
    3. OVAU - Order reasons
    4. VOV4 - Assign Item categoreies(Item cat determination)
    5. VOV6 - Scedule line categories
    6. OVAL - To assign blocks to relevant sales documents type
    7. OVLK - Define delivery types
    8. V/06 - Pricing
    9. V/08 - Maintain pricing procedure
    10.OVKP - Pricing proc determination
    11.V/07 - Access sequence
    Enduser:
    1. Customer Master Creation-VD01 and XD01 (for full inclu company code)
        VD02 - Change Customer
        VD03 - Display Customer
        VD04 - Customer Account Changes
        VD06 - Flag for Deletion Customer
        XD01 - Create Customer
        XD02 - Modify Customer
        XD03 - Display Customer
    2. Create Other material -
    MM00
    3. VB11- To create material determination condition record
    4. CO09- Material availability Overview
    5. VL01 - Create outbound delivery with ref sales order
    6. VL04 - Collective processing of delivery
    7. VA11 - Create Inquiry
        VA12 - Change Inquiry
        VA13 - Display Inquiry
    Sales & Distribution
    Sales order / Quote / Sched Agreement / Contract
    · VA01 - Create Order
    · VA02 - Change Order
    · VA03 - Display Order
    · VA02 - Sales order change
    · VA05 - List of sales orders
    · VA32 - Scheduling agreement change
    · VA42 - Contract change
    · VA21 - Create Quotation
    · VA22 - Change Quotation
    · VA23 - Display Quotation
    Billing
    · VF02 - Change billing document
    · VF11 - Cancel Billing document
    · VF04 - Billing due list
    · FBL5N - Display Customer invoices by line
    · FBL1N - Display Vendor invoices by line
    Delivery
    · VL02N - Change delivery document
    · VL04 - Delivery due list
    · VKM5 - List of deliveries
    · VL06G - List of outbound deliveries for goods issue
    · VL06P - List of outbound deliveries for picking
    · VL09 - Cancel goods issue
    · VT02N - Change shipment
    · VT70 - Output for shipments
    General
    · VKM3, VKM4 - List of sales documents
    · VKM1 - List of blocked SD documents
    · VD52  - Material Determination
    MM Transaction Code
    All transaction are stored in table TSTC. 
    Transaction for MM module start with M. 
    IH09 - Display Material
    MM01 - Create Material 
    MM02 - Change Material 
    MM03 - Display Material
    MM50 - List Extendable Materials
    MMBE - Stock Overview
    MMI1 - Create Operating Supplies
    MMN1 - Create Non-Stock Material 
    MMS1 - Create Service
    MMU1 - Create Non-Valuated Material
    ME51N - Create Purchase Requisition
    ME52N - Change Purchase Requisition
    ME53N - Display Purchase Requisition
    ME5A - Purchase Requisitions: List Display
    ME5J - Purchase Requisitions for Project
    ME5K - Requisitions by Account Assignment
    MELB - Purch. Transactions by Tracking No.
    ME56 - Assign Source to Purch. Requisition
    ME57 - Assign and Process Requisitions
    ME58 - Ordering: Assigned Requisitions
    ME59 - Automatic Generation of POs
    ME54 - Release Purchase Requisition
    ME55 - Collective Release of Purchase Reqs.
    ME5F - Release Reminder: Purch. Requisition
    MB21 - Create Reservation
    MB22 - Change Reservation
    MB23 - Display Reservation
    MB24 - Reservations by Material
    MB25 - Reservations by Account Assignment
    MB1C - Other Goods Receipts
    MB90 - Output Processing for Mat. Documents
    MB21 - Create Reservation
    MB22 - Change Reservation
    MB23 - Display Reservation
    MB24 - Reservations by Material
    MB25 - Reservations by Account Assignment
    MBRL - Return Delivery per Mat. Document
    MB1C - Other Goods Receipts
    MB90 - Output Processing for Mat. Documents
    MB1B - Transfer Posting
    MIBC - ABC Analysis for Cycle Counting
    MI01 - Create Physical Inventory Document
    MI02 - Change Physical Inventory Document
    MI03 - Display Physical Inventory Document
    MI31 - Batch Input: Create Phys. Inv. Doc.
    MI32 - Batch Input: Block Material
    MI33 - Batch Input: Freeze Book Inv.Balance
    MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
    MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
    MIQ1 - Batch Input: PhInvDoc. Project Stock
    MI01 - Create Physical Inventory Document
    MI02 - Change Physical Inventory Document
    MI03 - Display Physical Inventory Document
    MI31 - Batch Input: Create Phys. Inv. Doc.
    MI32 - Batch Input: Block Material
    MI33 - Batch Input: Freeze Book Inv.Balance
    MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
    MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
    MIQ1 - Batch Input: PhInvDoc. Project Stock
    MI01 - Create Physical Inventory Document
    MI02 - Change Physical Inventory Document
    MI03 - Display Physical Inventory Document
    MI31 - Batch Input: Create Phys. Inv. Doc.
    MI32 - Batch Input: Block Material
    MI33 - Batch Input: Freeze Book Inv.Balance
    MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
    MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
    MIQ1 - Batch Input: PhInvDoc. Project Stock
    MI21 - Print physical inventory document
    MI04 - Enter Inventory Count with Document
    MI05 - Change Inventory Count
    MI06 - Display Inventory Count
    MI09 - Enter Inventory Count w/o Document
    MI34 - Batch Input: Enter Count
    MI35 - Batch Input: Post Zero Stock Balance
    MI38 - Batch Input: Count and Differences
    MI39 - Batch Input: Document and Count
    MI40 - Batch Input: Doc., Count and Diff.
    MI08 - Create List of Differences with Doc.
    MI10 - Create List of Differences w/o Doc.
    MI20 - Print List of Differences
    MI11 - Physical Inventory Document Recount
    MI07 - Process List of Differences
    MI37 - Batch Input: Post Differences
    CT01 - Create Characteristic
    CT02 - Change Characteristic
    CT03 - Display Characteristic
    CL01 - Create Class
    CL02 - Classes
    CL03 - Display Class
    CL04 - Delete Class
    CL2B - Class Types
    <REMOVED BY MODERATOR>
    Edited by: Alvaro Tejada Galindo on Apr 7, 2008 12:53 PM

  • Where to find "Partner Text", field from inside transaction IW33?

    Hi all!
    Inside the transaction IW33, there is a folder/screen Partner. Inside this Partner screen it is a field u201CNameu201D. This is the third line from left. Do anyone now where in the database the data inside the field u201CNameu201D is been read? If I look into the technical details, I do only se the structure name. And that is DIADR-NAME_LIST. I do want to find out where this data has been read from.

    Hi,
    In Tcode: ME42, enter the request for quotation number (RFQ) and press enter. System will take you to 'Item Overview' screen. From menu select 'Header' -- 'Details' or press F6. Then the system will take you to 'Header screen' there you can see the 'company code' after RFQ number field.
    Or
    Directly from Tcode: ME42, enter the request for quotation number,then from menu select 'Header' -- details. Here you can have the company code field.
    The data for company here too will get updated in table and field EKKO-BUKRS.
    Hope this helps.
    Thanks,
    Viswanath

  • 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

  • How to add related fields from one transaction to other transacction?

    Hi all,
    I have a problem. I need to add an OPPORTUNITY field (SALESCYCLE) to the ACTIVITY transaction because of an upgrade and I'm now in a new world... The CRM 2007 is an unexplored place to me.
    I added some custom fields (Z fields from the CUSTOMER_H) by adding the context node BTCUSTOMERH to the BT126H_APPT component, view ApptDetails, with transaction BSP_WD_CMPWB (thanks Stephen Johannes for your blogs) and all works correctly.
    I tried doing the same with the SALESCYCLE and it doesn't worked... :_(
    I added the context node BTOPPORTH, but I'm sure I failed at the wizard step with the "Higher level context node" or with the "BOL Relation", but I can't find the correct answer. I found the field in the "Configuration tab", I put it in my view but the GET method doesn't work... The field remains always void.
    I don't have problems adding activity related fields, but when I try to add some flow related (opportunity one in my case) fields it's different.
    I have been looking for any solution but I have only seen that I can add this attribute directly to one context node and modify some BAdI or do any thing similar, but I don't know how to do that either. I will accept this solution if someone tells me how to do that... But I think the first solutions could be the most appropiate (I can be wrong... of course!)
    Thanks in advance....
    Sergio

    Thanks for your answer, Subhasis!
    Your solution is correct if I want to add to the Activity a field related to the Activity or some field on the DocFlow structure (the case you described), but it's not my case. I did that with customer fields before and all worked correctly.
    My scene is like this. I have an Opportunity and there is a follow-up Activity created. When I want to see the Activity, I need to show on the Activity transaction the preceding Opportunity field SALESCYCLE, which is at the CRMD_OPPORT_H table (BTOPPORTH context node).
    The problem comes when I add this context node to the Activity. I think the application is trying to get the field from the CRMD_OPPORT_H with ACTIVITY data and it returns void to the field. I think it forgets to get the opportunity data first and after that try to get the SALESCYCLE value from the CRMD_OPPORT_H (with the Opportunity GUID).
    By the moment, I have added the attribute SALESCYCLE to the BTDOCFLOW context node and, at the moment he do the GET, I change the field it gets by the GUID of the opportunity:
         dref = current->get_property( 'SALESCYCLE' ). "#EC NOTEXT
          dref = current->get_property( 'OBJKEY_A' ). "#EC NOTEXT
    Then I go to the CRMD_OPPORT_H directly to get the SALESCYCLE value...
    I know it's a bad solution... but it works and I don't know any other solution by now. If anyone can help me to do it correctly I'll be greatly appreciated!
    Regards,
    Sergio

  • Adding custom fields to CN41 Transaction code

    Hi Experts,
    I have a requirement to display few SAP standard fields (like VORN1 from AFABD structure) in CN41 transaction code. I modified the custom include structure CI_PROJ in table PROJ. When I ran CN41 tcode, this field doesn't show up in the layout list. But I can see the same feild in CN42 transaction code. Can anyone advise what is the difference between CN41 & CN42 and how this field to be shown in CN41?
    Also, can some one advise, if SAP will take care by itself to fill the data since it is standard field or do we have to write any custom code in user exit?
    Finally, can anyone explain me the difference between Structure Overview & Project Definitions?
    Really appreciate your help.
    Regards,
    Sailesh.

    Thanks Rod,
    But SAP gave us a provision to modify the custome structures CI_PROJ or CI_PRSP etc so that we can add the fields here.  My question was, I am able to see these fields in CN42 tocde but not in CN41.  Is there a way, that I can display the fields fromm CI_PROJ onto CN41 report?
    And for second part, I thoguht, if I add the SAP standard fields from PSJ logical database, then SAP should update these fields automatically.  I might be wrong on this.
    Any ideas?
    Shylesh

  • MM17 Delete a Field from this Transaction

    Hi,
      Could someone tell me how to delete a field from the MM17 transaction code.
       Please let me know if this is feasible.
    Thanks & Regards,
    YJR.
    Message was edited by:
            YJR

    Hello,
    I think it is not possible to delete fields or add tables in MM17.
    Vasanth

  • Field Status by Transaction code or User Exit

    Hi all,
      Is it possiblee to change field status group according to transaction code and GL account? Any configuration or user exit?
      For example, transaction FB01 account 100000 using Field status group A and transaction FB60 account 100000 using field status group B.
      Or is there any user exit to change the screen of FI transaction?
    Thanks,
    Phon

    Maybe you could try with FI Validations...Tx. <b>OB28</b>
    Greetings,
    Blag.

Maybe you are looking for