Viewlink between Custom VO "Cannot set user query to view"

We have an application where we have extended custom VO and EO’s to get data from flat files. It all looks fine till we create a viewlink for a LOV with two related VO’s. The viewlink VO fails we get message of the form -Cannot set user query to view "CustomVO1" because it is a destination in a view link”. Are there any methods to override in the custom VO/EO or any parameter to be added to configs. Has someone tried this out

Thanks for the update and for sharing the solution!
Regards,
Hussein

Similar Messages

  • Cannot set user query to view "{0}" because it is a destination in a view link

    Hi
    11.1.1.7 - I have 2 programatically view objects. I have created a viewLink between them and I am getting the error:
    Cannot set user query to view "MyView2" because it is a destination in a view link.
    Does anyone know what are the methods I need to implement? I have follow the Frank Nimphius Post: Oracle ADF: Service, Please! and it is working fine. However, after seeing this example: Decompiling ADF Binaries: Building programmatically managed business components - Part 2 - I realised that I am missing some other stuff to make the view link work. There are too many methods and its quite difficult to understand and digest all classes and methods etc.
    Anyone can please point me in the right direction?
    Regards

    Which version are you using? Could you maybe turn on logging (http://blog.goverco.com/p/psmalogging.html) and post content of log file if you still have the issue...
    Also, remember that even though you set credentials in the PARAM section, these values are overwritten by the ones specified on the properties of the MA - so make sure that you specify correct creds on the MA. Specifying creds directly in the script makes
    for an easy way of testing from the PowerShell prompt, but not for running the script from the MA / Run Profiles
    Regards, Soren Granfeldt
    blog is at http://blog.goverco.com | facebook https://www.facebook.com/TheIdentityManagementExplorer | twitter at https://twitter.com/#!/MrGranfeldt

  • Su: cannot set user id: Resource temporarily unavailable

    Hi ,
    One my server when i try to su - oracle as root user
    [root@stcfusion02 etc]# su - oracle
    su: cannot set user id: Resource temporarily unavailable
    [root@stcfusion02 etc]#
    and when i directly try to login as oracle session is getting exit..
    Please gimme a resolution on this....:(
    Regards,
    Ashlee

    Some things to try:
    1) Please confirm you are not using a naming service and that oracle is in /etc/passwd:
    This can usually be shown by:
    grep passwd /etc/nsswitch.conf
    grep oracle /etc/passwd2) Also worth trying su oracle rather than su - oracle to see if same messages occurs.
    3) The may be clues in the /var/log/messages log.
    Please confirm:
    a) whether or not you have access to root
    b) What is the exact version of your operating system.
    Rgds - bigdeboy

  • Slaris 10 u6 auditing - pam_unix_cred: cannot set user audit Bad address

    When I switch on auditing (execute /etc/security/bsmconv command), after rebooting system I cannot login to the system. When I try to login I can see the followin message:
    pam_unix_cred: cannot set user audit Bad address
    I have not idea, what to do

    Thanks for this. Parent chmod o+x fixed it.

  • Cannot set time in month view

    Until a few days ago I could create a new activity in the month view edit it and set the appropriate time. Now when I create an entry the time is set at the initial creation, changing it does not effect the entry.
    ie. I create an entry and the time is set at from 19:00 til 20:00. I select edit and change it to 10:0 till 11:00 hit save. When I re-open the entry the time is back to 19:00 till 20:00.
    Doing the same exercise in week or day view does work. Also items created in month view and edited in week or day view are correct.
    Any ideas?
    Thanks

    Welcome to Apple Discussions,
    Go to Apple Menu > System Preferences > Language & Text > Formats > Region. Region should be set to the country of your choice. Do not have it set to "Custom" as this can have unexpected results in the iCal window.
    If that isn't the cause then:
    First make an iCal backup, File > Export > Archive.
    Remove the following to the trash and restart your computer:
    Home > Library > Caches
    Home > Library > Calendars > Calendar Cache, Cache, Cache 1, 2, 3, etc. (Do not remove Sync Cache or Theme Cache)
    Home > Library > Preferences > com.apple.ical (There may be more than one of these. Remove them all.)
    __NOTE: Removing these files will remove any shared (CalDAV) calendars you may have access to. You will have to re-add those calendars to iCal > Preferences > Accounts.
    Once the computer is back up and running open iCal and test.
    Hope that helps.

  • Differnce Between Customer & User Exits

    Pls tell me
    What are various types of exits?
    with Regards,
    Manmeet singh

    Hi Manmeet,
    Differnce Between Customer & User Exits
    In contrast to customer exits, user exits allow developers to access and modify program components and data objects in the standard SAP System. On upgrade, each user exit must be checked to ensure that it conforms to the standard system.
    There are the following types of user exit:
    User exits that use INCLUDEs -
    These are customer enhancements that are called directly in the program.
    User exits that use tables -
    These are used and managed using Customizing.
    Customer Exit
    SAP creates customer exits for specific programs, screens, and menus within standard applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.
    If you want to enhance the functionality of your SAP System, you should take advantage of the exits available in standard applications. There are two main reasons why you should use exits rather than modifying SAP software yourself. Add-ons attached to exits have the advantage that:
    · They do not affect standard SAP source code
    When you add new functionality to your SAP System using SAP’s exits, you do not alter the source code of standard SAP programs in any way. The code and screens you create are encapsulated as separate objects. These customer objects are linked to standard applications, but exist separately from SAP’s standard software package.
    · They do not affect software updates
    When you add new functionality to your SAP System using SAP’s exits, your objects (called customer objects) must adhere to strict naming conventions. When it comes time to upgrade a to a new software release, customer objects’ names ensure that they will not be affected by any changes or new additions to the standard software package.
    Customer exits are not available for all programs and screens found in the SAP System. You can only use customer exits if they already exist in the SAP System. You find find more information about locating applications with pre-defined exits in Locating Applications that have Exits
    User Exits:
    User exits allow you to add additional functions to the SAP standard.
    Programs with user exits contain subroutine calls at certain points in their syntax that are identified by the prefix USEREXIT. The actual user exits are located in an include that has been assigned to a module pool. This is where customers can include any changes (enhancements) that they want to make to the system. These includes are always processed during program flow.
    Advantage: In principle, customers can modify anything they want that is found in the include (tables, structures, and so forth).
    Disadvantage: SAP cannot check the individual enhancements themselves which often leads to errors in the enhancement process.
    Types of Exits.
    1)MENU EXITS
    2)FUNCTION EXITS
    3)TABLE EXITS
    4)SCREEN EXITS
    5)KEYWORD EXITS
    6)FIELD EXITS
    Menu Exits
    Menu exits add items to the pulldown menus in standard SAP applications. You can use these menu items to call up your own screens or to trigger entire add-on applications.
    Function Module Exits
    Function module exits add functions to R/3 applications. Function module exits play a role in both menu and screen exits.
    When you add a new menu item to a standard pull down menu, you use a function module exit to define the actions that should take place once your menu is activated.
    Function module exits also control the data flow between standard programs and screen exit fields. SAP application developers create function module exits by writing calls to customer functions into the source code of standard R/3 programs.
    These calls have the following syntax:
    CALL CUSTOMER-FUNCTION ‘001’.
    screen exits:
    http://help.sap.com/saphelp_erp2005/helpdata/en/94/bef83770798b76e10000009b38f842/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/13/1f2d1a831a43be8a43ecd14170bf1c/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm
    Function Module Exits
    Function module exits add functions to R/3 applications. Function module exits play a role in both menu and screen exits.
    When you add a new menu item to a standard pull down menu, you use a function module exit to define the actions that should take place once your menu is activated.
    Function module exits also control the data flow between standard programs and screen exit fields. SAP application developers create function module exits by writing calls to customer functions into the source code of standard R/3 programs.
    These calls have the following syntax:
    CALL CUSTOMER-FUNCTION ‘001’.
    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 company’s 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.
    Screen exits:
    http://help.sap.com/saphelp_erp2005/helpdata/en/94/bef83770798b76e10000009b38f842/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/13/1f2d1a831a43be8a43ecd14170bf1c/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm
    Regards,
    Priyanka.

  • Cannot use user classes in webservices interface of appmodule custom method

    Hi,
    I need to expose an application module's custom method that uses user defined classes as parameters and return types as a web service interface. I have not been able to do that. Below are more details.
    In particular, I have an app module that has a client interface with a custom method that takes and returns a serializable Emp object (user defined classes/objects). I need to expose this app module as a web service through the use of a service interface.
    When i run the "Create Service Interface" wizard, under service custom methods (Create Service Interface Step 2 of 4 wizard), i don't see my custom method under "Available."
    In addition, the JDev message log says: Business Components: Method "yourCustomMethod(Emp):Emp" cannot be exposed via service interface because the return type "com.mypackage.Emp" is not supported.
    From what i understand by reading the docs below, it seems that in an application module's service interface (Webservice) you only can use simple data type or java.util.list or AttributeList (which is a wrapper for any viewRow). In other words, i cannot use my user defined object in the custom method parameters and return types.
    This seems to be an artificial limitation of webservice creation through the use of app module because one can use complex/user defined objects in methods of a java class and expose them through a webservice.
    I would appreciate if of the tooling PMs can make a well thought out comment.
    11.2.3 What You May Need to Know About Method Signatures on the Service Interface
    http://docs.oracle.com/cd/E12839_01/web.1111/b31974/bcextservices.htm#CJAEHFJD
    9.8.4 What You May Need to Know About Method Signatures on the Client Interface
    http://docs.oracle.com/cd/E12839_01/web.1111/b31974/bcservices.htm#CHDFHGII
    Thanks,
    AJ
    ps: I am using Build JDEVADF_11.1.1.5.0_GENERIC_110409.0025.6013.

    Hi,
    question 2 doesn't apply as the client interface is for Java access to public methods. For the Service Interface, the document lists the supported data types you can use in arguments and return values. To expose a custom methods, what about using a POJO that accesses ADF BC (using create root application module) and then expose your POJO as a JAWS service. This will allow you to expose the data queried from ADF BC through your custom classes.
    Frank

  • IAM-3056160:Modify User Profile request cannot set or change attribute Job Code, since it is not defined in the corresponding data set.

    I am trying to modify the value of the field "Job Code" through API I am getting the following error.(OIM11gr2). I do not get this error when updating the other fields. There is a field by the name USR_JOB_CODE in the database. When I poked around I found that there is no Job Code field in the User Form. Any ideas?
    IAM-3056160:Modify User Profile request cannot set or change attribute Job Code, since it is not defined in the corresponding data set.:Modify User Profile:Job Code
    oracle.iam.identity.exception.ValidationFailedException: IAM-3056160:Modify User Profile request cannot set or change attribute Job Code, since it is not defined in the corresponding data set.:Modify User Profile:Job Code
           at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:237)
           at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
           at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
           at oracle.iam.identity.usermgmt.api.UserManager_nimav7_UserManagerRemoteImpl_1036_WLStub.modifyx(Unknown Source)
           at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
           at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
           at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
           at java.lang.reflect.Method.invoke(Unknown Source)
           at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.invoke(RemoteBusinessIntfProxy.java:85)
           at $Proxy2.modifyx(Unknown Source)
           at oracle.iam.identity.usermgmt.api.UserManagerDelegate.modify(Unknown Source)
           at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
           at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
           at sun.reflect.DelegatingMethodAccessorImpl.invoke

    THanks for your reply. Here is the snippet from User.xml that contains info about job code.
    <entity-attribute>Job Code</entity-attribute>
    <target-field>usr_job_code</target-field>
    <field name="usr_job_code">
    <type>string</type>
    <required>false</required>
    </field>
    <attribute name="Job Code">
    <type>string</type>
    <required>false</required>
    <searchable>true</searchable>
    <multi-valued>false</multi-valued>
    <MLS>false</MLS>
    <multi-represented>false</multi-represented>
    <attribute-group>Basic</attribute-group>
    <metadata-attachment>
    <metadata>
    <name>multi-valued</name>
    <value>false</value>
    <category>properties</category>
    </metadata>
    <metadata>
    <name>user-searchable</name>
    <value>true</value>
    <category>properties</category>
    </metadata>
    <metadata>
    <name>category</name>
    <value>Preferences</value>
    <category>properties</category>
    </metadata>
    <metadata>
    <name>bulk-updatable</name>
    <value>true</value>
    <category>properties</category>
    </metadata>
    <metadata>
    <name>read-only</name>
    <value>false</value>
    <category>properties</category>
    </metadata>
    <metadata>
    <name>visible</name>
    <value>true</value>
    <category>properties</category>
    </metadata>
    <metadata>
    <name>encryption</name>
    <value>CLEAR</value>
    <category>properties</category>
    </metadata>
    <metadata>
    <name>display-type</name>
    <value>TEXT</value>
    <category>properties</category>
    </metadata>
    <metadata>
    <name>system-controlled</name>
    <value>false</value>
    <category>properties</category>
    </metadata>
    <metadata>
    <name>max-size</name>
    <value>512</value>
    <category>properties</category>
    </metadata>
    <metadata>
    <name>custom</name>
    <value>false</value>
    <category>properties</category>
    </metadata>
    </metadata-attachment>
    </attribute>
    I am able to retrieve the value of the Job Code attribute without any problem with the following code.
    System.out.println("JOB Code: "+user.getAttribute("Job Code"));

  • Cannot set alarm between 2:00 am and 2:59 am

    iPhone 4 with iOS 4.3
    I cannot set an alarm between 2:00 am and 2:59 am. The alarm actually sets itself as 1:xx am. It's only 11:30 pm eastern as I write this and I'm guessing as the clock ticks over to March 14th this will go away but what the heck?
    Guess I should sleep till 3.

    The reason you get the exception is right there in the message. You are trying to insert a datetime value that is out of range. The valid SQL Server datetime range is between 1/1/1753 12:00:00 AM and 12/31/9999 11:59:59 PM. If you send in a datetime outside
    of this range, you will get the exception you mention.
    Now, there is a thing or two to know about this. First off, the .net datetime has a different range than the SQL datetime and ranges from the year 0001 up to year 9999. That means that while the .Net datetime is valid, it might break when you try to send
    it to SQL Server.
    In order to get around this, you have several options, depending on your preference and how your code is structured.
    One idea is to change the datatype in the SQL Server column to datetime2 which has the same range as the .Net datetime.
    Another is to catch the exception and handle it in your code after it has occured using a try/catch.
    Most likely you want to validate the data BEFORE sending it to SQL Server though, and you can check that your datetime variable is in the valid range by comparing it to the max and min values in SQL Server datetime type using System.Data.SqlTypes.SqlDateTime.MinValue
    and .MaxValue respectively. If your variable is outside of these, you can alert the user or whatever you need to do.
    (Yet another option is to declare your variable as a System.Data.SqlTypes.SqlDateTime and use that, but I would not go that route, but rather use the native .Net datatypes and validate the range).
    

  • Difference between customer exit and user exit?

    hi experts
    difference between customer exit and user exit?

    These r the main differences between user exits and customer exits
    1) user exits r subroutines where as customer exits r function modules
    2) user exits r not upgraded where as customer exits r will upgrade
    3) customer exits r used for creating and additional fields or menu items to stadard tcode where as user exits r used for enabling or disabling the fields on the standrd screen or concatenating the key fields,it is not used adding an additional componenats to stadard tcode
    4) customer exits r reusable where as user exits r not reusable.
    Also:
    1. Customer exits: Implemented as Function Modules within z includes. Anybody can change it and no access key is required.
    2. User Exit: Implemented as subroutines within includes (any include except y or z includes). You need access for the specific include and then you can any subroutine (user exit) within that Include.
    BADIs are the enhanced version of user exits where the same logic is implemented via classes and object (OOP)
    Enchancement point is the latest once introduces with ECC6.0 . Not very sure about that but you can change it without any access key.
    Please go through the following link which will help you understand the exits in a much better way:
    http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec07a25db911d295ae0000e82de14a/content.htm
    http://www.sap-img.com/abap/what-is-the-difference-between-smod-and-cmod.htm
    http://sap.niraj.tripod.com/id21.html
    http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm
    http://www.sap-img.com/ab038.htm
    User Exits.
    http://www.erpgenie.com/sap/abap/code/abap26.htm
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sapgenie.com/abap/code/abap26.htm
    http://www.sap-img.com/abap/what-is-user-exits.htm
    http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
    http://www.easymarketplace.de/userexit.php
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sappoint.com/abap/userexit.pdfUser-Exit
    customer exits
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f1a7e790-0201-0010-0a8d-f08a4662562d
    Menu Exit.
    http://www.sappoint.com/abap/spmp.pdf
    http://www.sappoint.com/abap/userexit.pdf
    http://www.sapdevelopment.co.uk/enhance/mod_sapmenu.htm
    http://www.sapdevelopment.co.uk/enhance/enhancehome.htm
    1. Previously there were only user-exits.
    2. Then came the concept of customer-exits.
    3. user exits were nothing but subroutines
    FORM/PERFORM
    called from standard programs.
    4. The FORM defintion was placed inside
    an empty include file.
    5. So It was called EVERYTIME.
    and we need to MODIFY/REPAIR the
    standard include .
    6. Then it came with concept of customer-exit
    7. It consists of calling a FUNCTION MODULE,
    which is called only if
    the user-exit is ACTIVATED (other wise not called)
    In this case, the code in put inside
    a pre-defined Z include.
    8. Functionality of both is same, howerver
    we can note the following important differences
    a) Customer exit is called only if activated.
    (hence, it does not waste resources)
    b) in customer exit, REPAIR does not happen
    to the standard include.
    Exits are basically the hooks whcih SAP has provided to add your own code.
    User Exits: These are provided only SD module .
    They are Empty subroutines with naming like USEREXIT_.
    We need to have Access key to implement them.
    Customer Exits: These are enhancement techniques.
    There are defined in SMOD and implemented in CMOD.
    Types of Customer exits: Function exit, Screen Exit, Menu exit.
    User Exit and Customer Exit are same ,but SAP Exit and Customer exit are different...
    Customer Exit,
    Enables you to determine values for variables by means of Functional Module exit.The function module used is EXIT_SAPLRRSO_001.
    Create a project in CMOD by selecting the SAP Enhancement RSR00001 and assign this to the enhanced proj and activate it.
    Customer Exit
    SAP creates customer exits for specific programs, screens, and menus within standard applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.
    If you want to enhance the functionality of your SAP System, you should take advantage of the exits available in standard applications. There are two main reasons why you should use exits rather than modifying SAP software yourself. Add-ons attached to exits have the advantage that:
    • They do not affect standard SAP source code
    When you add new functionality to your SAP System using SAP’s exits, you do not alter the source code of standard SAP programs in any way. The code and screens you create are encapsulated as separate objects. These customer objects are linked to standard applications, but exist separately from SAP’s standard software package.
    • They do not affect software updates
    When you add new functionality to your SAP System using SAP’s exits, your objects (called customer objects) must adhere to strict naming conventions. When it comes time to upgrade a to a new software release, customer objects’ names ensure that they will not be affected by any changes or new additions to the standard software package.
    Customer exits are not available for all programs and screens found in the SAP System. You can only use customer exits if they already exist in the SAP System. You find find more information about locating applications with pre-defined exits in Locating Applications that have Exits
    http://help.sap.com/saphelp_nw04/helpdata/en/1d/ca10d858c2e949ba4a152c44f8128a/frameset.htm
    SAP EXIT:this processing type contained in variables that are delivered with SAP BW business content.
    http://help.sap.com/saphelp_nw04/helpdata/en/1d/ca10d858c2e949ba4a152c44f8128a/frameset.htm
    User Exits: allow you to add additional functions to the SAP standard.
    Programs with user exits contain subroutine calls at certain points in their syntax that are identified by the prefix USEREXIT. The actual user exits are located in an include that has been assigned to a module pool. This is where customers can include any changes (enhancements) that they want to make to the system. These includes are always processed during program flow.
    Advantage: In principle, customers can modify anything they want that is found in the include (tables, structures, and so forth).
    Disadvantage: SAP cannot check the individual enhancements themselves which often leads to errors
    reward points if found useful
    regards
    palak

  • What is the difference between customer exits and user exits?

    hello friends,
    what is the difference between customer exits and user exits?

    Hi
    User exit - A user exit is a three character code that instructs the system to access a program during system processing.
    SXX: S is for standard exits that are delivered by SAP.   XX represents the 2-digit exit number.
    UXX: U is for user exits that are defined by the user.  XX represents the 2-digit exit number
    Customer exit - The R/3 enhancement concept allows you to add your own functionality to SAP’s standard business applications without having to modify the original applications. SAP creates customer exits for specific programs, screens, and menus within standard R/3 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.     *-- Mani
    The following document is about exits in SAP :-
    The R/3 enhancement concept allows you to add your own functionality to SAP’s standard business applications without having to modify the original applications. 
    SAP creates user exits for specific programs, screens, and menus within standard R/3 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.
    Types of Exits 
    There are several different types of user exits. Each of these exits acts as hooks where you can attach or "hang" your own add-ons.
    Menu Exits
    Menu exits add items to the pulldown menus in standard SAP applications. You can use these menu items to call up your own screens or to trigger entire add-on applications.
    SAP creates menu exits by defining special menu items in the Menu Painter. These special entries have function codes that begin with "+" (a plus sign). You specify the menu item’s text when activating the item in an add-on project.
    Screen Exits
    Screen exits add fields to screens in R/3 applications. SAP creates screen exits by placing special subscreen areas on a standard R/3 screen and calling a customer subscreen from the standard screen’s flow logic.
    Function Module Exits 
    Function module exits add functions to R/3 applications. Function module exits play a role in both menu and screen exits. 
    When you add a new menu item to a standard pull down menu, you use a function module exit to define the actions that should take place once your menu is activated. 
    Function module exits also control the data flow between standard programs and screen exit fields. SAP application developers create function module exits by writing calls to customer functions into the source code of standard R/3 programs. 
    These calls have the following syntax: 
    CALL CUSTOMER-FUNCTION ‘001’.
    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 company’s 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'.
                             SET SCREEN 100.
                             LEAVE SCREEN.
                 ENDCASE.
          ENDCASE.

  • Users are not able to use Outlook 2010 to view free/busy information and cannot set Out Of Office automatic reply

    Hi All,
    Please help me.
    I have an issue where users are not able to use Outlook 2010 to view free/busy information and cannot set Out Of Office automatic reply. But they are can set Out Of Office automatic reply from OWA. My exchange server is Ms Exchange 2010.
    The test E-mail AutoConfiguration failed with this error:
    Autodiscover to https://mydomain.com/autodiscover/autodiscover.xml starting
    GetLastError=12175; httpStatus=0.
    Autodiscover to https://mydomain.com/autodiscover/autodiscover.xml Failed (0x800C8203)
    Autodiscover to https://autodiscover.mydomain.com/autodiscover/autodiscover.xml starting
    GetLastError=12007; httpStatus=0.
    Autodiscover to https://autodiscover.mydomain.com/autodiscover/autodiscover.xml Failed (0x800C8203)
    Local autodiscover for mydomain.com starting
    Local autodiscover for mydomain.com Failed (0x8004010F)
    Redirect check to http://autodiscover.mydomain.com/autodiscover/autodiscover.xml starting
    Srv Record lookup for http://autodiscover.mydomain.com/autodiscover/autodiscover.xml Failed (0x80072EE7)
    Srv Record lookup for mydomain.com starting
    Srv Record lookup for mydomain.com Failed (0x8004010F)
    Any idea?
    Thanks,
    Pieter

    OK.
    Please follow this step.
    1. As you said you are in coexistence step , so for now all endpoint already point to Exchange 2010 right?
    2. Check legacy owa redirect that you already configure
    3. In Exchange 2010 , Make sure that you already configure "Autodiscoverinternaluri" by this command set-clientaccessserver -identity "servername" -autodiscoverinternaluri
    https://autodiscover.domain.com/autodiscover/autodiscover.xml. and don't forget to create autodiscover record in DNS
    4. in Exchange 2010 , Make sure that you already configure "EWS" path by this command set-webservicesvertualdirectory -identity "XXX\Default web site name" -internalurl
    https://yourinternalurl/EWS/Exchange.asmx -externalurl https://yourexternalurl/EWS/Exchange.asmx
    5. don't forget to replicate freebusy from Exchange 2003 to Excahnge 2010 via public folder.
    You error look like client cannot get autodiscover process please check it again.

  • I cannot set up a blue tooth connection between my apple ipod and phone

    I cannot set up a bluetooth connection between my apple ipod touch and an external speaker wirelessly. The speaker is a boombar and although I have been able to set  it up successfully between the speaker and my iphone, I have not been able to set it up with the ipod.  Please , any advice?

    Unpair the spear from the phone.
    Reset the speaker.
    Try with the Mac again.

  • Set PO query for all users in POWL screen

    Dear All,
    In Purchase order work list (POWL) need to define a new query and set it for all the users.
    Request to please let us know how we can create and set that query in POWL for all users?
    thanks,
    mahesh.

    Dear All,
    In Purchase order work list (POWL) need to define a new query and set it for all the users.
    Request to please let us know how we can create and set that query in POWL for all users?
    thanks,
    mahesh.

  • Re:User group,info set and Query combination table

    Hi,
      I would like to know the combination table of User group,info set and Query.
    Can any body please respond to my question?
    Regards,
    Suresh Kumar.

    Hi,
    Check the tables starting with AQG*.
    Reward points if useful.
    Regards,
    Atish

Maybe you are looking for