Exit and Mark Complete?

Hi,
    This is my first post i'm doing some work for a client who wants the e-learning courses we have created on an LMS which will be accessed using an iPad. I can get this working however it has to have an Exit and Mark complete button at the end of the course which closes the course tab. This however is where the issue lies as I see in the release notes for this converter that the Execute Javascript action isn't supported which is what I normally use to do this. Is there any other way of doing this? This is also using SCORM 1.2 and the client would actually prefer it if we used AICC is there any news on when AICC might be supported? or a full release date for this product? 
Any help or advice would be greatly appreciated!
Many Thanks,
Joe

Hi Shadowtuck,
                        the retrieving status you see via the Lync Server 2013 control panel for the Lync Server 2010 front end is normal behaviour
and nothing to be concerenced about, as is the the green tick not showing for step two in the deployment wizard. I have seen this behaviour in all Lync Server 2010 to Lync Server 2013 migrations I have performed for customers. Thanks.
Regards.
http://www.b4z.co.uk

Similar Messages

  • Captivate 6 issue. Exits and says not complete/issues with videos too

    I use Captivate 6 on a Mac and I publish to SCORM 2.0. Previously we used Captivate 5.5 on a PC and had no problems at all.
    Our e-learning portal provider (World Manager) does not support questions when created in Captivate, so we have always added questions on at the end via the e-learning portal to register 'compete'. This has worked 98% of the time (mostly within 5.5), but occasionally seems to have the following issues:
    It can exit if there is a video inserted (this is sporadic at best - some modules are happy with vids, others are not)
    It exits and says 'not complete' rather than going into the questions - again this is sporadic, and works for some modules and not others.
    All modules have been created from ones that previously worked. Content activities and copy/images would be the only changes - no back end/exit commands have been changed. We seem to have the most problems with Cap 6. I previously installed a patch sent to me from Adobe to fix the issues I had previously with Flash files (this did not fix it either).
    I am utterly at a loss and seem to have tried everything. Please help!
    Thanks, Jen

    Hi Rod, thanks for the reply.  Like I say in the post because of the way the contract is set up (I'm arms-length subcontracting for the physical training provider) I'm not allowed on client site, nor to contact users directly, so am having to trouble shoot via email with single-point-of-contact middleman.)  The arrangement is every bit as frustrating as it sounds, but is what it is.
    So I am taking their word for it. 
    That said, I've no reason to doubt them as the same issue has been reported independently from different physical locations, and all the test users will have managed to find their way sucessfully through far more complex functionality before they get stuck at that point.
    I know that from time to time when you run flash locally you can have problems launching URLs unless local flash player settings are updated to allow it - is there any network level equivalent that a company (or even local machine) may have in place that could cause the same behaviour?   Or am I barking up the wrong tree?

  • NEED VL02N VL09 USER-EXIT FOR DELIVERY COMPLETE INDICATOR IN PURCHASE ORDER

    I NEED VL02N VL09 USER-EXITS FOR DELIVERY COMPLETE INDICATOR IN PURCHASE ORDER POSITIONS.
    F.X: IF POST QUANTITY 10, BUT PURCHASE ORDER POSITION QUANTITY 30, I NEED AT ANY CASE TO SET DELIVERY COMPLETE INDICATOR FOR RELEVANT OUTBOUND DELIVERY AN P. ORDER POSITIONS.
    THANKS/

    Hi Malka,
    It's possible set the system to mark automatically the delivery completed indicator.
    First you need to set the under delivery and over delivery tolerances.You do this in customizing:
    Materials Management under Purchasing -> Material Master -> Define Purchasing Value Keys.
    Once you set this, you can insert this value keys on Material Master Record for the materials.
    When you create the PO with a material with this value keys set the system will check the under delivery and over delivery set on customizing.
    In customizing you also have the option to let the system mark automatically the delivery indicator based on delivery tolerances set.
    In Customizing for Inventory Management and Physical Inventory under Goods Receipt -> Set Delivery Completed Indicator, you can determine for each plant whether the system automatically sets the delivery completed indicator for delivery quantities within the underdelivery and overdelivery tolerances.
    You can test setting the under delivery for 0 (with a warning message) and see if the system will only mark delivery complete only for over delivery.
    You can also work with the following Badi: MB_GOODSMOVEMENT_DCI. This Badi also allows custom logic for setting the delivery completed indicator in a PO item.
    Message: M7 433 (The "delivery completed" indicator is set for the purchase order item)
    Regards,
    Rodrigo

  • Unchecked final invoice and delivery completed indicator via BAPI_PO_CHANGE

    Hi All,
    Is it possible to reset the final invoice and delivery completed indicators of PO in ME23N using BAPI_PO_CHANGE? I need to unchecked the final invoice and delivery completed indicators for all POs in our system that were accidentally updated to delivery completed and final invoice by the user.
    Points will be rewared.

    what i did now is to create a prototype program like the one below:
    CONSTANTS c_po TYPE bapimepoheader-po_number VALUE '0040001816'.
    DATA: t_poitem-po TYPE bapimepoheader-po_number,
          t_return TYPE STANDARD TABLE OF bapiret2,
          t_poitem TYPE STANDARD TABLE OF bapimepoitem,
          t_poitemx TYPE STANDARD TABLE OF bapimepoitemx,
          x_return TYPE bapiret2,
          x_poitem TYPE bapimepoitem,
          x_poitemx TYPE bapimepoitemx.
    t_poitem-po = c_po.
    x_poitem-no_more_gr = 'X'.
    x_poitemx-no_more_gr = 'X'.
    x_poitem-final_inv = 'X'.
    x_poitemx-final_inv = 'X'.
    x_poitem-po_item = c_po.
    x_poitemx-po_item = c_po.
    APPEND x_poitem TO t_poitem.
    APPEND x_poitemx TO t_poitemx.
    CALL FUNCTION 'BAPI_PO_CHANGE'
      EXPORTING
        purchaseorder  = t_poitem-po
        no_messaging   = 'X'
        no_message_req = 'X'
      TABLES
        return         = t_return
        poitem         = t_poitem
        poitemx        = t_poitemx.
    IF sy-subrc = 0.
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
        EXPORTING
          wait = 'X'.
    ENDIF.
    The program is working if you will mark the PO as delivery completed and final invoice with suppressed output. The problem is i need to do the reverse which is to unmark. I replaced the value of no_more_gr and final_inv from 'X' to space but it is not working.

  • BAdi / user exit for QN complete (NOCO Status)

    Hello QM gurus,
    I want to make some custom validations on completing of the Quality notification. These changes have to be done for some specific notification types (eg: Q2/F2).
    The status set on 'Complete' is NOCO.
    Can anyone please let me know some BAdI or user exit where in I can code to make the custom validations?
    Thanks,
    Megha

    Thanks so much for your response.
    Can you please let me how do you figure out the Exits and Badi names.
    And
    When I debugged using exits given by you, QQMA0005 is being triggered.\
    But, this happens when a task is completed and when entire QN is completed.
    Can you please me how to identify the difference in the code.
    In both the cases, only T_VIQMSM  table comes populated. Rest all the initial.

  • There is a problem with Adobe Acrobat/Reader. If it is running, please exit and try again. (4:4)

    Trying to open a streamed PDF in an IFRAME in Internet Explorer 9 on my Win7 64bit machine.
    This results in the following dialog:
    There is a problem with Adobe Acrobat/Reader. If it is running, please exit and try again. (4:4)
    The PDF is streamed (not read from disc) from a servlet in our Java WebSphere environment and the call looks like this:
    https://intranetserver.com/myapplication/OpenDocumentServlet.pdf?documentToOpenID=1
    The Servlet sets content-type header application/pdf and content-length and writes the bytes to the buffer.
    Does the error dialog even come from Acrobat? When the dialog opens there is no active AcrReader process visible in task manager.
    Please advise!
    Meddelandet redigerades av: p b
    Solved. Our IT dept. responsible for packaging and deployment repacked and redeployed 11.0.9. Unknown what changes were made to make it work.

    I don't know what acrofix.exe is; can you explain?
    Issue
    Nothing happens when you launch Acrobat 30 days after installing a CS6 suite.
    Solutions
    Important: Perform the solutions below in order. Do not continue further if an earlier solution resolves the problem.
    Solution1: Install the patch for Acrobat installed as part of a CS6 (Windows Only)
    1.   Log in to your Windows computer as an Administrator.
    2.   Click the following link to download the patch file:
    Acrofix.zip
    3.   When prompted "Do you want to open or save this file?,” click Open.
    4.   Extract the file. The location varies depending on your operating system and the utility.
    5.   Double-click the extracted Acrofix.exe to begin the execution.
    6.   If the execution is successful, Command Prompt closes automatically.
    7.   When the execution is complete, launch Acrobat.
    or
    Solution2: Install the patch for Acrobat installed as part of a CS6 using Command Prompt (Windows Only)
    1. Run the Command Prompt as an Administrator.
    2. Navigate to the location of the extracted hot fix in Solution 1 (Step 4).
    3. Type Acrofix.exe to execute it.
    4. If the execution is successful, Command Prompt shows Exit Code:0
    5. When the execution is complete, launch Acrobat.
    Solution 3: Reactivate Acrobat through another Suite product
    I will try your cleaner, thanks
    [private data removed]

  • Actual finish date and % of completion in Open Ps

    I am unable to download Actual finish date and % of completion while downloading project from SAP PS to MS Projects using Open PS.

    From SAP Note 1332046:
    07.Question: After downloading a project from SAP PS into MS Project, why is the Planned Finish Date in MS Project different when compared to project in SAP PS?
    Answer:
    When downloading projects with actual data, the actual work that has been completed by an activity element on an activity in SAP is assigned to the resource of a task in MSP.If there is remaining work and if the actual finish date in SAP PS is before planned finish date, the remaining work
    will be equally distributed till the planned finish date. If there is remaining work and if the actual finish date in SAP PS is on or after planned finish date, the remaining work will be equally distributed till the forecast finish date for the activity. If a forecast finish date is not
    available for the activity, remaining work will be equally distributed till the forecast finish date for the activity element. If a forecast finish date is not available for the activity element also, then MS Project does the allocation of remaining work.That is, if the actual finish is on or
    after the planned finish and there is work remaining, while entering confirmations in SAP a forecast finish date should be supplied so that when downloading the project to MSP, the remaining work will be scheduled properly.
    I do not understand. If we must mark the final confirmation it shouldn't be remaining work. I still do not understand why my finish dates do not fit with the actual finish date in SAP.

  • Menu Exits and Screen Exits

    hi everyone,
    can you send me some examples on menu exits and screen exits.
    thank you.
    preetham

    Hi Preetham,
    In older versions MENU Exits approached through Transaction CMOD by creating
    PROJECTS and activating the project and assigning Program to that
    Transaction Codes. For MENU Exits, Transaction Codes will be starting with
    "+" sign and with default text "NODE TEXT NOT FOUND" for which you can
    assign your Report or Dialog Program etc., (for Eg:- +DW4 MENU Exits
    Transaction available in TOOLS --> ABAP Workbench --> Utilities --> <Node
    Text Not found>).
    Procedure for Creating MENU Exits.
    1) To get into Area Menu Maintenance Screen Type SE43 T.Code in Command
    Line.
    2) In Area Menu Paramenter type 'S000' (S triple Zero)
    3) Then Press Change Icon in Application Tool Bar. Then It may ask for
    Access Key [or] it may display "Specify Processing mode" window. If it ask
    for the Access Key Check for the availability of OSS Note and apply to open
    Standard SAP Menu to include MENU Exits. Otherwise, if it display "Specify
    Processing mode" window with Three Push Button. In which select "Change" and
    proceed further.
    4) Then it will display "Information" window with the following information
    "Caution : The Original Language of the structure is German (editing lang. :
    English) ". Then press "Enter Key to proceed further.
    5) Then you will get into "Edit Area Menu S000".
    6) for eg:- Expand Tools Menu.
    7) Then Press ABAP Workbench <Icon>.
    8) Then you will get into ABAP Workbench Menu Tree.
    9) Then Expand Utilities Menu.
    10) In the last line you will find one MENU EXIT Provision to include your
    own menu. "Node Text Not Found" This text can be change by double Clicking
    that. There you can find the T.Code. Here for Eg:- "+DW4".
    11) for eg: - Here change the Text to "Sample Menu Exit" and then note down
    the T.Code "+DW4".
    12) Then Save with Change Request Number and come out of Transaction SE43.
    13) Then Goto Transaction SE93.
    14) Then type T.Code "+DW4" and press Create.
    15) Then proceed further to create transaction called "+DW4".
    I hope this could help you in Creating Menu Exit...
    Creating menu exits
    http://help.sap.com/saphelp_nw04/helpdata/en/c8/19762743b111d1896f0000e8322d00/content.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/83/7a18cbde6e11d195460000e82de14a/frameset.htm
    For screen exits.
    http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
    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.
    the tcode is cmod...
    1.From the main screen of the Project management transaction, proceed as follows:
    Select Enhancement components and choose Change.
    2.Choose Edit component.
    3.Choose the screen exit and double click on it
    4.Create your subscreen using the Screen Painter.
    5.Design your screen to be added to the standard screen and activate the particular screen and return back to the flow logic .
    6.Choose the PAI and PBO to write down the logic.
    7.Generate your screen and choose Back (the green arrow) to return to the Project management transaction.
    8.Go to the transaction ME22 to view the customer defined screen exit.
    9.Enter the purchase order number and press Enter.
    10.Go to the menu header --> Details.
    11.Purchase number is visible on the standard screen
    check the foll link,
    http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
    Menu exits allow you to add your own functions to the pulldown menus in standard R/3 transactions. To take advantage of a menu exit, you first need to create a project as described in the section Creating an add-on project. Then, you must include the SAP enhancement package that contains the menu exit you want to use in your project. From the main screen of the Project management transaction, proceed as follows:
    Select Enhancement components and choose Change.
    The system lists all customer exits contained in the enhancements included in your project.
    Place the cursor on the menu exit you want to add your own function to.
    Choose Edit component.
    The system displays technical information about the menu entry. It also displays two input fields where you can specify a language and the text you want your menu item to have.
    Enter the name of your menu function (such as Special order method) in the field New text.
    Choose Save text.
    Your special menu function will not appear in the pulldown menu of the corresponding standard transaction until you activate your enhancement project.
    Specifying a menu text and activating your project are not the only steps you need to take to make your own menu item work. After you carry out these steps, your menu item will appear, but it will not call a corresponding function. To attach your menu entry to its corresponding function, you need to create a function module for the function module exit associated with your menu text. This function module exit is part of the same SAP enhancement that contains the menu exit you used. Creating Customer-Specific Function Modules tells you more about how to use function module exits.
    also refer
    MEnu Exit
    http://www.sap-img.com/abap/what-is-user-exits.htm
    Creating menu exits
    http://help.sap.com/saphelp_nw04/helpdata/en/c8/19762743b111d1896f0000e8322d00/content.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/83/7a18cbde6e11d195460000e82de14a/frameset.htm
    For screen exits.
    http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
    chech these links for user exists its usefull
    http://www.allsaplinks.com/user_exit.html
    Re: Screen exit
    user exit and customer exit
    http://help.sap.com/saphelp_47x200/helpdata/en/dd/561602545a11d1a7020000e829fd11/frameset.htm
    http://www.sap-basis-abap.com/sapab013.htm
    http://www.sap-img.com/abap/what-is-user-exits.htm
    How to implement screen exit for a SAP standard transaction
    Introduction
    SAP provides standard transactions to enter data into database. But a client may want to maintain some additional information in SAP other than what is provided.
    To make provisions for this, additional screens have to be provided and additional fields must be added into appropriate database table.
    To pave way for this, SAP has provided the option for screen exits. Usually, SAP provides the following:
    An append structure in the database table with the new fields.
    A subscreen area into the standard screen – where the programmer can attach his subscreen of his own program with the new fields.
    A function group under which the new subscreen has to be created with the new fields.
    Function exits to synchronize the PBO and PAI of the standard SAP program with the PBO and PAI of the subscreen – so that data can flow back and forth between the standard SAP program and the program written by the developer for the subscreen. These function modules also exist in the same function group under which the subscreen will have to be developed.
    Finally, a linkage has to be done between the subscreen area of standard SAP screen with the custom subscreen constructed by the developer.
    Typically, SAP provides an enhancement in which the developer can create an append structure, use the function exits to synchronize the PBO and PAI of the standard SAP program and the custom subscreen program, and make the necessary linking( as mentioned above in step 4. But, again, this is not a hard and fast rule. Linking in some case, is also done by configurations.) SAP also usually provides the name of the function group under which the subscreen has to be developed.
    Necessary guidance about implementing a screen exit development is usually available in the Documentation section of the enhancement ( can be availed by transaction SMOD).
    Pre-Requisites
    The developer to work on screen exit should have essential knowledge on the following:
    DDIC concepts, including the knowledge of append structure.
    Concept of SAP Enhancements and implementing them using Projects.
    Concept of function exits.
    Knowledge on Module Pool – including subscreens, Tabstrip controls etc.
    Steps
    Guidelines
    So, a developer can follow the guidelines mentioned below to implement a screen exit to a standard SAP transaction, as and when required:
    Find out the Required Enhancements
    Go to SMOD. Press F4 in the Enhancement field. In the next popup window, click pushbutton ‘SAP Applications’. A list will appear that contains information on all the enhancements, categorized under functional areas. Developer must search for the enhancements relevant to his functional area of interest – for e.g., Purchasing, Asset Accounting, etc.
    Note down the enhancements. Then, come to the initial screen of SMOD and view the documentation of each enhancement to find out which one is required for your development.
    Utilize the Enhancement in a Project
    After you have found one, do as directed in the documentation. Generally, the steps are as follows:
    Create a project using CMOD including your enhancement.
    Create the append structure with new fields.
    Go to the desired function group and create a subscreen with the new fields. Write PBO and PAI for the subscreen, if required.
    Use the function exits in the enhancement to link the PBO and PAI of the subscreen with that of the main SAP program supporting the SAP transaction.
    Maintain necessary linkage between the subscreen area of standard SAP program with the custom subscreen developed along with the custom program name. This can be done in the project (developed by CMOD including the enhancement) or outside as a part of configuration.
    Activate the project.
    Test to ensure that required functionality are met.
    Case Study 1
    Add three new custom fields for Asset master and maintain information for them
    Requirement
    Three fields in the legacy system have to be maintained in Asset master. These fields are:
    Original Asset number – 20 characters
    Location 2 – 15 Characters.
    Model no – 20 characters
    Location 2 should start with ‘L’.
    Pre-Analysis
    Finding out the Enhancement
    As described above, the enhancement is determined. It was found, that enhancement AIST0002 will serve the purpose. It contains the following components (can be viewed by transaction SMOD):
    Exit Type Description EXIT_SAPL1022_001 Function Exit Check of User-Defined Fields when Using Create and Change BAPI EXIT_SAPLAIST_002 Function Exit Transfer Data for User Subscreens in PBO. EXIT_SAPLAIST_003 Function Exit Transfer of User-Defined Fields to SAP Master Data Transactions CI_ANLU Customizing Include Include structure to add new fields
    Studying the Function Exits
    The function module level documentation for the function exits are then viewed from transaction SE37. The documentation clearly laid out for the purpose for their use:
    EXIT_SAPLAIST_002
    Function module Level Documentation
    This function module is called by asset master data maintenance at the start of the dialog. (When changing, it is called after reading of the data from the database; when creating it is called after the transfer of the default values from the asset class and reference asset.) The purpose of the function module is to enable this function group to recognize the master data. For interpreting or controlling master data fields that are important for user fields, it is possible to transfer to global variables at this point, so that they can be recognized when the user subscreens are processed.
    Import Parameters
    Understanding
    This function module is called at the PBO to pass the information retrieved from the database to pass them to the custom subscreen and its underlying program. Import parameter : I_ANLU will be populated with the values for user-defined fields which will be passed to the subscreen program. So, there must be some sort of variable assignment from I_ANLU.
    EXIT_SAPLAIST_003
    Function module Documentation: This function module is called by SAP asset master data maintenance after the screens are processed, but before saving. The purpose of the function module is to transfer fields entered on user sub-screens of SAP asset data maintenance to the database for updating. The export parameter for this function module is:
    Understanding
    This function module will be used to transfer the user entered data in the subscreen fields to the main SAP program, which will then be saved into the database.
    Studying the Documentation of the Enhancement
    The enhancement documentation (as is viewed from the initial screen of SMOD] also supports the idea. Moreover, it informs that we need to develop a subscreen under function group XAIS. This is the function group under which the two function exit modules also exist. So, if the custom subscreen refers to the global data of the function group XAIS, then those values will also be available to these function exits as well.
    Going to SE80 and viewing the function group XAIS helps us to inform that there are three DDIC tables declared for it:
    Deciding the Final course of Action
    After making all the investigations, the final course of action was determined.
    SrlNo Step Justification
    A project has to be created using transaction CMOD where the enhancement AIST0002 will be included.
    Customizing include CI_ANLU has to be created with the custom fields demanded When CI_ANLU will be developed, the custom fields will get appended to the database table ANLU. Also, these fields will be used to create screen fields in the new subscreen.
    A custom subscreen, say, 9000 will be developed under function group XAIS. The screen group for the screen will be ‘CUST’ (or any name). The three custom fields added to table ANLU (by creating CI_ANLU) will be used to create new fields in the screen.
    In the PAI of the subscreen, validation for Location to start with ‘L’ will be added. The subscreen with three new fields has to be developed so that it can be attached to a subscreen area of the asset master screens.
    In the custom include of the function exit module ‘EXIT_SAPLAIST_002’, the following code will be written:-
    ANLU = I_ANLU. I_ANLU is the import parameter of this FM. The value is assigned to the global variable ANLU, referring which the three new subscreen fields are developed. So, data retrieved from database table ANLU will be passed to this FM as I_ANLU by the standard SAP main program. The value will be taken and passed to the global variable of the function group XAIS, so that the three custom fields (referring to ANLU of XAIS) get populated.
    In the custom include of the function exit module ‘EXIT_SAPLAIST_003’, the following code will be written:-
    E_ANLU = ANLU. The changed values in the subscreen fields exist in global variable ANLU for the function group XAIS. This function exit module will pass the data back to the SAP main program as E_ANLU.
    Proper linkage/configuration has to be done so that the new subscreens get linked to the appropriate subscreen area of the Asset master screen. This has to be done – otherwise, the new custom subscreen will not be displayed in the Asset master screens.
    Development
    Creating a Project to include the enhancement
    Go to transaction CMOD and create a project.
    Enter a description for the project. Then, click on the pushbutton ‘Enhancement Assignments’ in the Application Toolbar.
    Enter the name of the enhancement and Save.
    Go to ‘Components’.
    Creating Custom Include for ANLU
    The screen shown below will appear, showing all the enhancement components under the assignment AIST0002. Double-click on the name of the Include Structure to create it.
    Create the include structure with three new fields, as required. Then, save and activate it.
    Develop the subscreen and the program
    Go to transaction SE80. For the function group XAIS, create a new subscreen 9000.
    Create it as subscreen.
    Then, go to the Layout of the screen and create three new fields from Database table ANLU.
    Drag the fields in the screen body and place them.
    Then, save and activate the screen and come back to screen flow editor.
    Create the PAI module to add validation for field “Location 2”, as required .
    Activate the whole function group and come out.
    Write code in the Function Exits to synchronize the programs
    Now, code has to be written in the function modules EXIT_SAPLAIST_002 and EXIT_SAPLAIST_003 so that data flows to and fro between the main SAP program and custom subscreen program. For that, go back to transaction CMOD and change the function exits.
    Write code in the function module EXIT_SAPLAIST_002 called once at the beginning of the transaction:
    Write code in EXIT_SAPLAIST_003 to pass the data from the subscreen to SAP main program.
    Then, activate everything – the whole project and come out.
    Complete the configuration to link the subscreen
    The development portion is complete. Now, linking of the subscreen has to be done with the subscreen area of the main program. In most of the cases, this linking can be done in the enhancement itself. But, here, requirement is a bit different. It is done by configuration using SPRO.
    Assets are created under Asset class. And for each asset class, there is a layout assigned to it. For a layout, there are multiple tab pages assigned to it. And, for each tab page, there are multiple screen groups/field groups assigned.
    Here, the requirement is to create these three custom fields in the tab page ‘General’ of asset master screen ( AS01/AS02/AS03/AS91).
    Determine the Layout
    To achieve this, first of all, we need to find out which layout is assigned to asset class 1000.For that, go to transaction AOLK( information has to be obtained from functional consultant).Select the Asset Class ‘1000’ and click on folder ‘General Assignment of Layout’.
    Here, for Asset class 1000, for all the user groups, tab layout SAP is assigned. Since layout ‘SAP’ cannot be changed, it has to be copied and manipulated to include our screen group. Later, the new layout has to be assigned over here.
    Create new tab layout
    Go to transaction AOLA. Copy the tab layout ‘SAP’ to create another layout, say, YSUB.
    System will copy all the settings and will inform you about that.
    Select your newly created layout and double-click on the folder ‘Tab page titles’.
    You want to put your custom fields in the tab page “General”. So, select this tab page entry and double-click on the folder "Position of Groups".
    Here, all the field groups currently residing in the tab-page “General” are shown. Add an entry for your newly created fields.
    Select the group box from the list. An entry will come with “U” padded with the custom subscreen prepared by you.
    Then, save and come out.
    Assign the new Layout to Asset Class
    Now, go to tcode AOLK and assign tab layout YSUB for asset class 1000.
    Save and come out.
    Test the Exit
    Everything is over. Now, go to transaction code AS01/02/03 or AS91 to deal with an asset of asset class 1000. You will see your new fields added to the screen. Add values to them…save. Then, enter into the tcodes again to see whether the values entered by you are being displayed or not.
    Original Source: ittoolbox.com
    MENU
    refer
    MEnu Exit
    just refer to the link below for step by step procedure with screen shots
    http://www.sapmaterial.com/?gclid=CN322K28t4sCFQ-WbgodSGbK2g
    Check this link:
    http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975e643b111d1896f0000e8322d00/frameset.htm
    Menu exits allow you to add your own functions to the pulldown menus in standard R/3 transactions. To take advantage of a menu exit, you first need to create a project as described in the section Creating an add-on project. Then, you must include the SAP enhancement package that contains the menu exit you want to use in your project. From the main screen of the Project management transaction, proceed as follows:
    Select Enhancement components and choose Change.
    The system lists all customer exits contained in the enhancements included in your project.
    Place the cursor on the menu exit you want to add your own function to.
    Choose Edit component.
    The system displays technical information about the menu entry. It also displays two input fields where you can specify a language and the text you want your menu item to have.
    Enter the name of your menu function (such as Special order method) in the field New text.
    Choose Save text.
    Your special menu function will not appear in the pulldown menu of the corresponding standard transaction until you activate your enhancement project.
    Specifying a menu text and activating your project are not the only steps you need to take to make your own menu item work. After you carry out these steps, your menu item will appear, but it will not call a corresponding function. To attach your menu entry to its corresponding function, you need to create a function module for the function module exit associated with your menu text. This function module exit is part of the same SAP enhancement that contains the menu exit you used. Creating Customer-Specific Function Modules tells you more about how to use function module exits.
    User exits (Function module exits) are exits developed by SAP. The exit is implementerd as a call to a function module. The code for the function module is written by the developer. You are not writing the code directly in the function module, but in the include that is implemented in the function module.
    The naming standard of function modules for functionmodule exits is:
    EXIT_<program name><3 digit suffix>
    The call to a functionmodule exit is implemented as:
    CALL CUSTOMER.-FUNCTION <3 digit suffix>
    To find a Exit.
    Goto Transaction -- Find The Package
    SMOD >f4>Use the Package here to Find the Exits In the Package.
    Else if you Want to search by Application Area wise ,
    There is one more tab to find the Exits in the Respective Application Area.
    Implementing the Exit-- CMOD Create ProjectsAssgn your Component .
    Now Run ur Transaction to Check if it Triggers.
    Thats it..
    Suppose you need to find out all the user exits related to a tcode.
    1. Execute the Tcode.
    2. Open the SAP program.
    3. Get the Development Class.
    4. Execute Tcode SE84.
    5. Open the Node 'Envir. -> Exit Techniques -> 'Customer Exits -> Enhancements'
    6. Enter the Development class and execute.
    Check out this thread..
    The specified item was not found.
    1. Type the transaction : system->status-> <PROG. NAME>
    2 open SE37 , type EXIT<PROG NAME> and press F4 to get the list of function exits available.
    3. Open CMOD utilities->SAP enhancements
    EDIT->All selections
    4.type the function module name obtained in step 2, in fields 'component name' in 'additional selections' block. and execute.
    5. The displayed list contains the enhancements names for the transaction You were looking for.
    6. Create a project in CMOD and the code in default include->activate.
    http://www.erpgenie.com/sap/abap/code/abap26.htm
    which gives the list of exits for a tcode
    http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec079f5db911d295ae0000e82de14a/frameset.htm
    For information on Exits, check these links
    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
    http://www.planetsap.com/userexit_main_page.htm
    User-Exits
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sap-img.com/ab038.htm
    http://www.planetsap.com/userexit_main_page.htm
    http://www.sap-basis-abap.com/sapab013.htm
    http://sap.ittoolbox.com/documents/popular-q-and-a/user-exits-for-the-transaction-code-migo-3283
    These links will help you to learn more on user exits.
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm
    http://www.planetsap.com/userexit_main_page.htm
    http://www.allsaplinks.com/user_exit.html
    www.sap-img.com/abap/what-is-user-exits.htm
    Also please check these threads for more details about user exits.
    Re: Screen exit
    user exit and customer exit
    user exit
    1. Document on UserExits in FI/CO
    http://www.ficoexpertonline.com/downloads/User%20ExitsWPedit.doc
    2. Finding User Exits...
    http://sap.ionelburlacu.ro/abap/sap2/Other_Useful_Tips.html#Finding_User_Exits
    3. List of all User Exits...
    http://www.planetsap.com/userexit_main_page.htm
    Reward points if helpful.
    Thanks
    Naveen khan
    Message was edited by:
            Pattan Naveen

  • SQL Server 2012 Installed KB2793634 and it completed successfully but display error in the event log

    Hi
    Running SQL Server 2012 with SP1 on Windows 7 x64 SP1
    One of the machines that this is installed displayed that the Windows Installer was starting repeatedly, like every 30 secs
    I installed KB2793634 and everything completed successfully.  No errors in any of the Summary, Detail, etc and all check marks at the end.  I went throught the event viewer and in the application log and saw the following
    Product: SQL Server 2012 Database Engine Services - Update '{4023B523-7241-4B6D-83A4-92105B0A3DC8}' could not be installed. Error code 1642. Windows Installer can create logs to help troubleshoot issues with installing software packages. Use the
    following link for instructions on turning on logging support:
    Is this something with the KB.  How do I find what the issue is and what do I do to fix it? Or is this a real error?
    I brought up SQL Server and the issue that the KB resolves seems to been resolved.  I can connect to the instance just fine, the version of the KB has been applied to the instance so now it is at 11.0.3128
    Any information will be greatly appreciated.

    Hi,
    According to the description, I know the patch that was successfully installed after the msiinstaller error.
    1. Per
    KB304888 and mentioned the possibility that the hotfix was launched a second time after the initial successful update.
    I suspect if you have installed any hotfixes or Cumulative updates after installing Service Pack 1 for SQL Server 2012.
    Reference:
    http://support.microsoft.com/kb/2793634
    2. Check the application log. Is the error happening intermittently?
    Thanks.
    Tracy Cai
    TechNet Community Support

  • Marking "complete" in the LMS

    Is there a way to have a slide in a project and some how designate that that slide does not need to be visited in order to mark completion in an LMS?
    In my project, I would like to have a Resource page within my course that users can access "if they want/need to", then have that page take them back to their last visited page.
    However, not everyone will need to see this page and therefore not everyone will click to access it, ultimately affecting the LMS conmpletion status since some people won't view the slide.
    I'm trying to replecate a functionality in Articulate where there's a Resource tab users can refer to throughout the course.... 
    I've thought about changing the completion percentage in the preferences, but I'm concerned that isn't the best solution.
    any other ideas for this?

    If you are NOT on Captivate 6, you can use the TickTOC widget to have the Resources slide marked as complete regardless of whether or not it was visited.
    Trial version available here if you want to give it a go: http://www.infosemantics.com.au/adobe-captivate-widgets/download-free-trial-widgets
    Unfortunately, Adobe changed something in Captivate 6 that means this widget cannot work in that version, but it will work in all versions from Cp4 to 5.5.

  • Screen exit and menu exit

    want some examples and step by step guide for menu exits and 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.
    the tcode is cmod...
    1.From the main screen of the Project management transaction, proceed as follows:
    Select Enhancement components and choose Change.
    2.Choose Edit component.
    3.Choose the screen exit and double click on it
    4.Create your subscreen using the Screen Painter.
    5.Design your screen to be added to the standard screen and activate the particular screen and return back to the flow logic .
    6.Choose the PAI and PBO to write down the logic.
    7.Generate your screen and choose Back (the green arrow) to return to the Project management transaction.
    8.Go to the transaction ME22 to view the customer defined screen exit.
    9.Enter the purchase order number and press Enter.
    10.Go to the menu header --> Details.
    11.Purchase number is visible on the standard screen
    check the foll link,
    http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
    Menu exits allow you to add your own functions to the pulldown menus in standard R/3 transactions. To take advantage of a menu exit, you first need to create a project as described in the section Creating an add-on project. Then, you must include the SAP enhancement package that contains the menu exit you want to use in your project. From the main screen of the Project management transaction, proceed as follows:
    Select Enhancement components and choose Change.
    The system lists all customer exits contained in the enhancements included in your project.
    Place the cursor on the menu exit you want to add your own function to.
    Choose Edit component.
    The system displays technical information about the menu entry. It also displays two input fields where you can specify a language and the text you want your menu item to have.
    Enter the name of your menu function (such as Special order method) in the field New text.
    Choose Save text.
    Your special menu function will not appear in the pulldown menu of the corresponding standard transaction until you activate your enhancement project.
    Specifying a menu text and activating your project are not the only steps you need to take to make your own menu item work. After you carry out these steps, your menu item will appear, but it will not call a corresponding function. To attach your menu entry to its corresponding function, you need to create a function module for the function module exit associated with your menu text. This function module exit is part of the same SAP enhancement that contains the menu exit you used. Creating Customer-Specific Function Modules tells you more about how to use function module exits.
    also refer
    MEnu Exit
    http://www.sap-img.com/abap/what-is-user-exits.htm
    Creating menu exits
    http://help.sap.com/saphelp_nw04/helpdata/en/c8/19762743b111d1896f0000e8322d00/content.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/83/7a18cbde6e11d195460000e82de14a/frameset.htm
    For screen exits.
    http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
    chech these links for user exists its usefull
    http://www.allsaplinks.com/user_exit.html
    Re: Screen exit
    user exit and customer exit
    http://help.sap.com/saphelp_47x200/helpdata/en/dd/561602545a11d1a7020000e829fd11/frameset.htm
    http://www.sap-basis-abap.com/sapab013.htm
    http://www.sap-img.com/abap/what-is-user-exits.htm
    How to implement screen exit for a SAP standard transaction
    Introduction
    SAP provides standard transactions to enter data into database. But a client may want to maintain some additional information in SAP other than what is provided.
    To make provisions for this, additional screens have to be provided and additional fields must be added into appropriate database table.
    To pave way for this, SAP has provided the option for screen exits. Usually, SAP provides the following:
    An append structure in the database table with the new fields.
    A subscreen area into the standard screen – where the programmer can attach his subscreen of his own program with the new fields.
    A function group under which the new subscreen has to be created with the new fields.
    Function exits to synchronize the PBO and PAI of the standard SAP program with the PBO and PAI of the subscreen – so that data can flow back and forth between the standard SAP program and the program written by the developer for the subscreen. These function modules also exist in the same function group under which the subscreen will have to be developed.
    Finally, a linkage has to be done between the subscreen area of standard SAP screen with the custom subscreen constructed by the developer.
    Typically, SAP provides an enhancement in which the developer can create an append structure, use the function exits to synchronize the PBO and PAI of the standard SAP program and the custom subscreen program, and make the necessary linking( as mentioned above in step 4. But, again, this is not a hard and fast rule. Linking in some case, is also done by configurations.) SAP also usually provides the name of the function group under which the subscreen has to be developed.
    Necessary guidance about implementing a screen exit development is usually available in the Documentation section of the enhancement ( can be availed by transaction SMOD).
    Pre-Requisites
    The developer to work on screen exit should have essential knowledge on the following:
    DDIC concepts, including the knowledge of append structure.
    Concept of SAP Enhancements and implementing them using Projects.
    Concept of function exits.
    Knowledge on Module Pool – including subscreens, Tabstrip controls etc.
    Steps
    Guidelines
    So, a developer can follow the guidelines mentioned below to implement a screen exit to a standard SAP transaction, as and when required:
    Find out the Required Enhancements
    Go to SMOD. Press F4 in the Enhancement field. In the next popup window, click pushbutton ‘SAP Applications’. A list will appear that contains information on all the enhancements, categorized under functional areas. Developer must search for the enhancements relevant to his functional area of interest – for e.g., Purchasing, Asset Accounting, etc.
    Note down the enhancements. Then, come to the initial screen of SMOD and view the documentation of each enhancement to find out which one is required for your development.
    Utilize the Enhancement in a Project
    After you have found one, do as directed in the documentation. Generally, the steps are as follows:
    Create a project using CMOD including your enhancement.
    Create the append structure with new fields.
    Go to the desired function group and create a subscreen with the new fields. Write PBO and PAI for the subscreen, if required.
    Use the function exits in the enhancement to link the PBO and PAI of the subscreen with that of the main SAP program supporting the SAP transaction.
    Maintain necessary linkage between the subscreen area of standard SAP program with the custom subscreen developed along with the custom program name. This can be done in the project (developed by CMOD including the enhancement) or outside as a part of configuration.
    Activate the project.
    Test to ensure that required functionality are met.
    Case Study 1
    Add three new custom fields for Asset master and maintain information for them
    Requirement
    Three fields in the legacy system have to be maintained in Asset master. These fields are:
    Original Asset number – 20 characters
    Location 2 – 15 Characters.
    Model no – 20 characters
    Location 2 should start with ‘L’.
    Pre-Analysis
    Finding out the Enhancement
    As described above, the enhancement is determined. It was found, that enhancement AIST0002 will serve the purpose. It contains the following components (can be viewed by transaction SMOD):
    Exit Type Description EXIT_SAPL1022_001 Function Exit Check of User-Defined Fields when Using Create and Change BAPI EXIT_SAPLAIST_002 Function Exit Transfer Data for User Subscreens in PBO. EXIT_SAPLAIST_003 Function Exit Transfer of User-Defined Fields to SAP Master Data Transactions CI_ANLU Customizing Include Include structure to add new fields
    Studying the Function Exits
    The function module level documentation for the function exits are then viewed from transaction SE37. The documentation clearly laid out for the purpose for their use:
    EXIT_SAPLAIST_002
    Function module Level Documentation
    This function module is called by asset master data maintenance at the start of the dialog. (When changing, it is called after reading of the data from the database; when creating it is called after the transfer of the default values from the asset class and reference asset.) The purpose of the function module is to enable this function group to recognize the master data. For interpreting or controlling master data fields that are important for user fields, it is possible to transfer to global variables at this point, so that they can be recognized when the user subscreens are processed.
    Import Parameters
    Understanding
    This function module is called at the PBO to pass the information retrieved from the database to pass them to the custom subscreen and its underlying program. Import parameter : I_ANLU will be populated with the values for user-defined fields which will be passed to the subscreen program. So, there must be some sort of variable assignment from I_ANLU.
    EXIT_SAPLAIST_003
    Function module Documentation: This function module is called by SAP asset master data maintenance after the screens are processed, but before saving. The purpose of the function module is to transfer fields entered on user sub-screens of SAP asset data maintenance to the database for updating. The export parameter for this function module is:
    Understanding
    This function module will be used to transfer the user entered data in the subscreen fields to the main SAP program, which will then be saved into the database.
    Studying the Documentation of the Enhancement
    The enhancement documentation (as is viewed from the initial screen of SMOD] also supports the idea. Moreover, it informs that we need to develop a subscreen under function group XAIS. This is the function group under which the two function exit modules also exist. So, if the custom subscreen refers to the global data of the function group XAIS, then those values will also be available to these function exits as well.
    Going to SE80 and viewing the function group XAIS helps us to inform that there are three DDIC tables declared for it:
    Deciding the Final course of Action
    After making all the investigations, the final course of action was determined.
    SrlNo Step Justification
    A project has to be created using transaction CMOD where the enhancement AIST0002 will be included.
    Customizing include CI_ANLU has to be created with the custom fields demanded When CI_ANLU will be developed, the custom fields will get appended to the database table ANLU. Also, these fields will be used to create screen fields in the new subscreen.
    A custom subscreen, say, 9000 will be developed under function group XAIS. The screen group for the screen will be ‘CUST’ (or any name). The three custom fields added to table ANLU (by creating CI_ANLU) will be used to create new fields in the screen.
    In the PAI of the subscreen, validation for Location to start with ‘L’ will be added. The subscreen with three new fields has to be developed so that it can be attached to a subscreen area of the asset master screens.
    In the custom include of the function exit module ‘EXIT_SAPLAIST_002’, the following code will be written:-
    ANLU = I_ANLU. I_ANLU is the import parameter of this FM. The value is assigned to the global variable ANLU, referring which the three new subscreen fields are developed. So, data retrieved from database table ANLU will be passed to this FM as I_ANLU by the standard SAP main program. The value will be taken and passed to the global variable of the function group XAIS, so that the three custom fields (referring to ANLU of XAIS) get populated.
    In the custom include of the function exit module ‘EXIT_SAPLAIST_003’, the following code will be written:-
    E_ANLU = ANLU. The changed values in the subscreen fields exist in global variable ANLU for the function group XAIS. This function exit module will pass the data back to the SAP main program as E_ANLU.
    Proper linkage/configuration has to be done so that the new subscreens get linked to the appropriate subscreen area of the Asset master screen. This has to be done – otherwise, the new custom subscreen will not be displayed in the Asset master screens.
    Development
    Creating a Project to include the enhancement
    Go to transaction CMOD and create a project.
    Enter a description for the project. Then, click on the pushbutton ‘Enhancement Assignments’ in the Application Toolbar.
    Enter the name of the enhancement and Save.
    Go to ‘Components’.
    Creating Custom Include for ANLU
    The screen shown below will appear, showing all the enhancement components under the assignment AIST0002. Double-click on the name of the Include Structure to create it.
    Create the include structure with three new fields, as required. Then, save and activate it.
    Develop the subscreen and the program
    Go to transaction SE80. For the function group XAIS, create a new subscreen 9000.
    Create it as subscreen.
    Then, go to the Layout of the screen and create three new fields from Database table ANLU.
    Drag the fields in the screen body and place them.
    Then, save and activate the screen and come back to screen flow editor.
    Create the PAI module to add validation for field “Location 2”, as required .
    Activate the whole function group and come out.
    Write code in the Function Exits to synchronize the programs
    Now, code has to be written in the function modules EXIT_SAPLAIST_002 and EXIT_SAPLAIST_003 so that data flows to and fro between the main SAP program and custom subscreen program. For that, go back to transaction CMOD and change the function exits.
    Write code in the function module EXIT_SAPLAIST_002 called once at the beginning of the transaction:
    Write code in EXIT_SAPLAIST_003 to pass the data from the subscreen to SAP main program.
    Then, activate everything – the whole project and come out.
    Complete the configuration to link the subscreen
    The development portion is complete. Now, linking of the subscreen has to be done with the subscreen area of the main program. In most of the cases, this linking can be done in the enhancement itself. But, here, requirement is a bit different. It is done by configuration using SPRO.
    Assets are created under Asset class. And for each asset class, there is a layout assigned to it. For a layout, there are multiple tab pages assigned to it. And, for each tab page, there are multiple screen groups/field groups assigned.
    Here, the requirement is to create these three custom fields in the tab page ‘General’ of asset master screen ( AS01/AS02/AS03/AS91).
    Determine the Layout
    To achieve this, first of all, we need to find out which layout is assigned to asset class 1000.For that, go to transaction AOLK( information has to be obtained from functional consultant).Select the Asset Class ‘1000’ and click on folder ‘General Assignment of Layout’.
    Here, for Asset class 1000, for all the user groups, tab layout SAP is assigned. Since layout ‘SAP’ cannot be changed, it has to be copied and manipulated to include our screen group. Later, the new layout has to be assigned over here.
    Create new tab layout
    Go to transaction AOLA. Copy the tab layout ‘SAP’ to create another layout, say, YSUB.
    System will copy all the settings and will inform you about that.
    Select your newly created layout and double-click on the folder ‘Tab page titles’.
    You want to put your custom fields in the tab page “General”. So, select this tab page entry and double-click on the folder "Position of Groups".
    Here, all the field groups currently residing in the tab-page “General” are shown. Add an entry for your newly created fields.
    Select the group box from the list. An entry will come with “U” padded with the custom subscreen prepared by you.
    Then, save and come out.
    Assign the new Layout to Asset Class
    Now, go to tcode AOLK and assign tab layout YSUB for asset class 1000.
    Save and come out.
    Test the Exit
    Everything is over. Now, go to transaction code AS01/02/03 or AS91 to deal with an asset of asset class 1000. You will see your new fields added to the screen. Add values to them…save. Then, enter into the tcodes again to see whether the values entered by you are being displayed or not.
    Original Source: ittoolbox.com
    MENU
    refer
    MEnu Exit
    just refer to the link below for step by step procedure with screen shots
    http://www.sapmaterial.com/?gclid=CN322K28t4sCFQ-WbgodSGbK2g
    Check this link:
    http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975e643b111d1896f0000e8322d00/frameset.htm
    Menu exits allow you to add your own functions to the pulldown menus in standard R/3 transactions. To take advantage of a menu exit, you first need to create a project as described in the section Creating an add-on project. Then, you must include the SAP enhancement package that contains the menu exit you want to use in your project. From the main screen of the Project management transaction, proceed as follows:
    Select Enhancement components and choose Change.
    The system lists all customer exits contained in the enhancements included in your project.
    Place the cursor on the menu exit you want to add your own function to.
    Choose Edit component.
    The system displays technical information about the menu entry. It also displays two input fields where you can specify a language and the text you want your menu item to have.
    Enter the name of your menu function (such as Special order method) in the field New text.
    Choose Save text.
    Your special menu function will not appear in the pulldown menu of the corresponding standard transaction until you activate your enhancement project.
    Specifying a menu text and activating your project are not the only steps you need to take to make your own menu item work. After you carry out these steps, your menu item will appear, but it will not call a corresponding function. To attach your menu entry to its corresponding function, you need to create a function module for the function module exit associated with your menu text. This function module exit is part of the same SAP enhancement that contains the menu exit you used. Creating Customer-Specific Function Modules tells you more about how to use function module exits.
    User exits (Function module exits) are exits developed by SAP. The exit is implementerd as a call to a function module. The code for the function module is written by the developer. You are not writing the code directly in the function module, but in the include that is implemented in the function module.
    The naming standard of function modules for functionmodule exits is:
    EXIT_<program name><3 digit suffix>
    The call to a functionmodule exit is implemented as:
    CALL CUSTOMER.-FUNCTION <3 digit suffix>
    To find a Exit.
    Goto Transaction -- Find The Package
    SMOD >f4>Use the Package here to Find the Exits In the Package.
    Else if you Want to search by Application Area wise ,
    There is one more tab to find the Exits in the Respective Application Area.
    Implementing the Exit-- CMOD Create ProjectsAssgn your Component .
    Now Run ur Transaction to Check if it Triggers.
    Thats it..
    Suppose you need to find out all the user exits related to a tcode.
    1. Execute the Tcode.
    2. Open the SAP program.
    3. Get the Development Class.
    4. Execute Tcode SE84.
    5. Open the Node 'Envir. -> Exit Techniques -> 'Customer Exits -> Enhancements'
    6. Enter the Development class and execute.
    Check out this thread..
    The specified item was not found.
    1. Type the transaction : system->status-> <PROG. NAME>
    2 open SE37 , type EXIT<PROG NAME> and press F4 to get the list of function exits available.
    3. Open CMOD utilities->SAP enhancements
    EDIT->All selections
    4.type the function module name obtained in step 2, in fields 'component name' in 'additional selections' block. and execute.
    5. The displayed list contains the enhancements names for the transaction You were looking for.
    6. Create a project in CMOD and the code in default include->activate.
    http://www.erpgenie.com/sap/abap/code/abap26.htm
    which gives the list of exits for a tcode
    http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec079f5db911d295ae0000e82de14a/frameset.htm
    For information on Exits, check these links
    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
    http://www.planetsap.com/userexit_main_page.htm
    User-Exits
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sap-img.com/ab038.htm
    http://www.planetsap.com/userexit_main_page.htm
    http://www.sap-basis-abap.com/sapab013.htm
    http://sap.ittoolbox.com/documents/popular-q-and-a/user-exits-for-the-transaction-code-migo-3283
    These links will help you to learn more on user exits.
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm
    http://www.planetsap.com/userexit_main_page.htm
    http://www.allsaplinks.com/user_exit.html
    www.sap-img.com/abap/what-is-user-exits.htm
    Also please check these threads for more details about user exits.
    Re: Screen exit
    user exit and customer exit
    user exit
    1. Document on UserExits in FI/CO
    http://www.ficoexpertonline.com/downloads/User%20ExitsWPedit.doc
    2. Finding User Exits...
    http://sap.ionelburlacu.ro/abap/sap2/Other_Useful_Tips.html#Finding_User_Exits
    3. List of all User Exits...
    http://www.planetsap.com/userexit_main_page.htm
    Reward points for useful Answers

  • Adobe Presenter Course not Marking Complete in LMS

    We have a course built with Adobe Presenter and was loaded into our LMS (sumtotal 7.5).  After completing the course, it is not marking completions.
    Here is what the settings are set for the course in Adobe Presenter:
    - enable reporting (checked) for SCORM
    - Incomplete--> Complete
    - success/completion criteria = user access
    - data to report = quiz score = points
    Any suggestions?

    Hopefully your SumTotal folks may have an answer...likely this has come up before?
    If not, better to ask in the Presenter forum (curiously hidden way in the Connect forum):
    http://forums.adobe.com/community/adobeconnect/connectpro_presenter
    Or check out this article - it's old, but maybe still helpful?
    http://www.connectusers.com/forums/viewtopic.php?id=1891

  • Why when i set my mac in sleep it starts alone and also complete stop without I do anything (Mac mini Mid 2011 - Yosemite)

    Why when i set my mac in sleep it starts alone and also complete stop without I do anything (Mac mini Mid 2011 - Yosemite)

    in response to lllaass
    here what I copied from Console:
    27/12/2014 02:29:58,457 WindowServer[185]: WSGetSurfaceInWindow : Invalid surface 1336265605 for window 268
    27/12/2014 02:30:02,516 WindowServer[185]: WSBindSurface : Invalid surface 1040636110 for window 266
    27/12/2014 02:30:17,370 com.apple.xpc.launchd[1]: assertion failed: 14B25: launchd + 160118 [55B9FF23-B298-321A-B776-CF7676586C04]: 0xe
    27/12/2014 02:30:17,371 com.apple.xpc.launchd[1]: assertion failed: 14B25: launchd + 160118 [55B9FF23-B298-321A-B776-CF7676586C04]: 0xe
    27/12/2014 02:30:18,819 Office365Service[2012]: WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.1 instead of 10.10.1. Use NSProcessInfo's operatingSystemVersion property to get correct system version number.
    Call location:
    27/12/2014 02:30:18,819 Office365Service[2012]: 0   CarbonCore                          0x901777e7 ___Gestalt_SystemVersion_block_invoke + 135
    27/12/2014 02:30:18,819 Office365Service[2012]: 1   libdispatch.dylib                   0x960dc130 _dispatch_client_callout + 50
    27/12/2014 02:30:18,819 Office365Service[2012]: 2   libdispatch.dylib                   0x960dc0b5 dispatch_once_f + 251
    27/12/2014 02:30:18,819 Office365Service[2012]: 3   libdispatch.dylib                   0x960dd0d8 dispatch_once + 31
    27/12/2014 02:30:18,819 Office365Service[2012]: 4   CarbonCore                          0x90109fb8 _Gestalt_SystemVersion + 1050
    27/12/2014 02:30:18,819 Office365Service[2012]: 5   CarbonCore                          0x90109b69 Gestalt + 150
    27/12/2014 02:30:18,819 Office365Service[2012]: 6   Office365Service                    0x000589a3 Office365Service + 358819
    27/12/2014 02:30:29,794 warmd[36]: [_bootcachectl_playlist_for_file:3197] Unable to generate playlist for file: 2 No such file or directory
    27/12/2014 02:30:29,794 warmd[36]: [_bootcachectl_playlist_for_file:3197] Unable to generate playlist for file: 2 No such file or directory
    27/12/2014 02:30:29,797 warmd[36]: [_bootcachectl_playlist_for_file:3197] Unable to generate playlist for file: 2 No such file or directory
    27/12/2014 02:30:29,797 warmd[36]: [_bootcachectl_playlist_for_file:3197] Unable to generate playlist for file: 2 No such file or directory
    27/12/2014 02:30:29,797 warmd[36]: [_bootcachectl_playlist_for_file:3197] Unable to generate playlist for file: 2 No such file or directory
    27/12/2014 02:30:29,799 warmd[36]: [_bootcachectl_playlist_for_file:3197] Unable to generate playlist for file: 2 No such file or directory
    27/12/2014 02:30:29,801 warmd[36]: [_bootcachectl_playlist_for_file:3197] Unable to generate playlist for file: 2 No such file or directory
    27/12/2014 02:30:30,870 xscertd-helper[2020]: ldap_search_ext_s returned -1 - Can't contact LDAP server when searching for bdb suffix, exiting
    27/12/2014 02:30:30,883 com.apple.xpc.launchd[1]: (com.apple.xscertadmin[2020]) Service exited with abnormal code: 1
    27/12/2014 02:30:30,928 coreaudiod[1249]: 2014-12-27 02:30:30.927642 AM [AirPlay] Power: SystemWillSleep
    27/12/2014 02:30:30,928 coreaudiod[1249]: 2014-12-27 02:30:30.927798 AM [AirPlay] BTLE client stopping to browse for AirPlay Solo Target Presence.
    27/12/2014 02:30:30,928 coreaudiod[1249]: 2014-12-27 02:30:30.928007 AM [AirPlay] BTLE discovery removing all devices
    27/12/2014 02:30:30,929 coreaudiod[1249]: 2014-12-27 02:30:30.929458 AM [AirPlay] BTLE client stopped to browse for AirPlay Solo Target Presence.
    27/12/2014 02:30:30,931 watchdogd[162]: [watchdog_daemon] @(         pm_callback) - ref=0x0 msg_type=0xe0000280 msg=0x2a0005
    27/12/2014 02:30:30,931 watchdogd[162]: [watchdog_daemon] @(    wd_daemon_thread) - events buffer: 65r1069 3634s1069
    27/12/2014 02:30:30,965 Office365Service[2012]: System shutdown notification
    27/12/2014 02:30:31,001 WindowServer[185]: device_generate_desktop_screenshot: authw 0x0(0), shield 0x7fbf43423ed0(2001)
    27/12/2014 02:30:31,044 identityservicesd[1311]: <IMMacNotificationCenterManager: 0x7ffac2c4fef0>: notification observer: com.apple.iChat   notification: __CFNotification 0x7ffac2d4efa0 {name = _NSDoNotDisturbEnabledNotification}
    27/12/2014 02:30:31,044 imagent[1305]: <IMMacNotificationCenterManager: 0x7fde8a42c1e0>: notification observer: com.apple.FaceTime   notification: __CFNotification 0x7fde8a54a860 {name = _NSDoNotDisturbEnabledNotification}
    27/12/2014 02:30:31,089 WindowServer[185]: device_generate_lock_screen_screenshot: authw 0x0(0)[inf, inf, 0, 0] shield 0x7fbf43423ed0(2001), dev [1680,1050]
    27/12/2014 02:30:31,000 kernel[0]: PM response took 168 ms (1194, UserEventAgent)
    27/12/2014 02:30:31,105 WindowServer[185]: device_generate_desktop_screenshot: authw 0x0(0), shield 0x7fbf43423ed0(2001)
    27/12/2014 02:30:31,180 apsd[59]: Peer [pid=1203] requested push wake but lacks APSPushWakeEntitlement
    27/12/2014 02:30:31,228 imagent[1305]: <IMMacNotificationCenterManager: 0x7fde8a42c1e0>:    NC Disabled: NO
    27/12/2014 02:30:31,228 identityservicesd[1311]: <IMMacNotificationCenterManager: 0x7ffac2c4fef0>:    NC Disabled: NO
    27/12/2014 02:30:31,237 imagent[1305]: <IMMacNotificationCenterManager: 0x7fde8a42c1e0>:   DND Enabled: YES
    27/12/2014 02:30:31,237 identityservicesd[1311]: <IMMacNotificationCenterManager: 0x7ffac2c4fef0>:   DND Enabled: YES
    27/12/2014 02:30:31,237 imagent[1305]: <IMMacNotificationCenterManager: 0x7fde8a42c1e0>: Updating enabled: NO   (Topics: (null))
    27/12/2014 02:30:31,237 identityservicesd[1311]: <IMMacNotificationCenterManager: 0x7ffac2c4fef0>: Updating enabled: NO   (Topics: (null))
    27/12/2014 02:30:31,237 identityservicesd[1311]: <IMMacNotificationCenterManager: 0x7ffac2e30040>: notification observer: com.apple.iChat   notification: __CFNotification 0x7ffac2c43f40 {name = _NSDoNotDisturbEnabledNotification}
    27/12/2014 02:30:31,244 identityservicesd[1311]: <IMMacNotificationCenterManager: 0x7ffac2e30040>:    NC Disabled: NO
    27/12/2014 02:30:31,249 identityservicesd[1311]: <IMMacNotificationCenterManager: 0x7ffac2e30040>:   DND Enabled: YES
    27/12/2014 02:30:31,249 identityservicesd[1311]: <IMMacNotificationCenterManager: 0x7ffac2e30040>: Updating enabled: NO   (Topics: (null))
    27/12/2014 02:30:31,000 kernel[0]: PM response took 347 ms (71, blued)
    27/12/2014 02:30:49,000 kernel[0]: PM response took 3456 ms (31, powerd)
    27/12/2014 02:30:49,000 kernel[0]: Failed to get hibernate image filename
    27/12/2014 02:30:49,000 kernel[0]: AirPort_Brcm43xx::powerChange: System Sleep
    All that is really chinese for me Do you know where i could get anything to be teached about all that
    Thanks

  • Help with BDC, user exits and BAPI

    Hello all:
    1) I posted a question before about BDC documentation and people sent me lot of helpful material. Thanks to all of them. I am very new to ABAP coming from VB background and wondering if someone can tell me how to practice one simple BDC program starting from scratch. What do I first need to do to get started? I have Mini WAS 6.20 test version and like to practice BDC programming.
    2) What are user exits and BADI and can anyone provide some documentation and sample code if possible.
    Thanks everyone in advance.
    --Mithun.

    Hai Mithun Dha
    Go through the following Documentation & Example Code
    Just check these links.
    Diff. between LSMW & BDC?
    BDC SESSION
    CALL TRANSACTION
    CALL DIALOG
    What is BDC or batch input
    The Batch Input is a SAP technic that allows automating the input in transactions. It lies on a BDC (Batch Data Commands) scenario.
    BDC functions:
    E BDC_OPEN_GROUP : Opens a session group
    E BDC_CLOSE_GROUP : Closes a session
    E BDC_INSERT : Insert a BDC scenario in the session
    E The ABAP statement "CALL TRANSACTION" is also called to run directly a transaction from its BDC table.
    It runs the program RSBDCSUB in order to launch automatically the session. The session management is done through the transaction code SM35.
    The object itself is maintanable through the transaction SE24.
    BDC methods:
    Method
    Description
    Parameters
    OPEN_SESSION
    Opens a session
    SUBRC (Return Code ? 0 OK)
    SESSIONNAME (Session to be created)
    CLOSE_SESSION
    Closes a session
    None
    RESET_BDCDATA
    Resets the BDC Internal Table...
    None. Normally, for internal purposec
    BDC_DYNPRO
    Handles a new screen
    PROGNAME (Name of the program)
    DYNPRONR (Screen Number)
    BDC_FIELD
    Puts a value on the screen
    FIELDNAME (Name of the field)
    FIELDVALUE (Value to be passed)
    CONSTRUCTOR
    Constructor - Initializes NO_DATA
    NODATA (No data character). The constructor is called automatically when the object is created.
    RUN_SESSION
    Launches a session with RSBDCBTC
    None
    CALL_TRANSACTION
    Calls a transaction with the current BDC Data
    MODE (Display Mode)
    UPDATE (Update Mode)
    TCODE (Transaction to be called)
    BDC_INSERT
    Inserts the BDC scenario in the session
    TCODE (Transaction to be called)
    BDC techniques used in programs:
    1) Building a BDC table and calling a transaction,
    2) Building a session and a set of BDC scenarios and keeping the session available in SM35,
    3) Building a session and lauching the transaction right after closing the session.
    BDC using Call Transaction
    BDC using Call transaction involves calling an SAP transaction in back ground from within the ABAP
    program. The process involves building an Internal BDC table containing the screen information needed to
    execute the required transaction and then passing this to the Call transaction command (See code example).
    The full procedure for creating a BDC program is as follows:
    What is the difference between batch input and call transaction in BDC?
    Session method.
    1) synchronous processing.
    2) can tranfer large amount of data.
    3) processing is slower.
    4) error log is created
    5) data is not updated until session is processed.
    Call transaction.
    1) asynchronous processing
    2) can transfer small amount of data
    3) processing is faster.
    4) errors need to be handled explicitly
    5) data is updated automatically
    BATINPUT/DIRECT INPUT
    A: Batch-inputs can not be used to fill the "delivery due list" screen because it is not a dynpro. This is a standard SAP report. A SAP report (check with "System -> Status") may be called using SUBMIT sentence with the appropriate options . It is preferred to call a report than create a Batch-input program.
    GO THROUGH THIS LINK
    http://www.guidancetech.com/people/holland/sap/abap/zzsni001.htm
    check with this code
    include bdcrecx1.
    tables : mara.
    data : begin of it_mara occurs 0,
    matnr like mara-matnr,
    mbrsh like mara-mbrsh,
    mtart like mara-mtart,
    maktx like makt-maktx,
    meins like mara-meins,
    end of it_mara.
    start-of-selection.
    perform upload_data.
    perform open_group.
    loop at it_mara.
    perform bdc_dynpro using 'SAPLMGMM' '0060'.
    perform bdc_field using 'BDC_CURSOR'
    'RMMG1-MATNR'.
    perform bdc_field using 'BDC_OKCODE'
    '/00'.
    perform bdc_field using 'RMMG1-MATNR'
    it_mara-matnr.
    perform bdc_field using 'RMMG1-MBRSH'
    it_mara-mbrsh.
    perform bdc_field using 'RMMG1-MTART'
    it_mara-mtart.
    perform bdc_dynpro using 'SAPLMGMM' '0070'.
    perform bdc_field using 'BDC_CURSOR'
    'MSICHTAUSW-DYTXT(02)'.
    perform bdc_field using 'BDC_OKCODE'
    '=ENTR'.
    perform bdc_field using 'MSICHTAUSW-KZSEL(01)'
    'X'.
    perform bdc_field using 'MSICHTAUSW-KZSEL(02)'
    'X'.
    perform bdc_dynpro using 'SAPLMGMM' '4004'.
    perform bdc_field using 'BDC_OKCODE'
    '=BU'.
    perform bdc_field using 'MAKT-MAKTX'
    it_mara-maktx.
    perform bdc_field using 'BDC_CURSOR'
    'MARA-MEINS'.
    perform bdc_field using 'MARA-MEINS'
    it_mara-meins.
    perform bdc_field using 'MARA-MTPOS_MARA'
    'NORM'.
    perform bdc_transaction using 'MM01'.
    endloop.
    perform close_group.
    *& Form upload_data
    text
    --> p1 text
    <-- p2 text
    FORM upload_data .
    CALL FUNCTION 'GUI_UPLOAD'
    EXPORTING
    FILENAME = 'c:\mat_bdc.txt'
    FILETYPE = 'ASC'
    TABLES
    DATA_TAB = it_mara.
    IF SY-SUBRC = 0.
    SORT IT_MARA BY MATNR.
    ENDIF.
    ENDFORM. " upload_data
    flat file structure is
    PRANIT_011 CCOUP This is Testing material kg
    PRANIT_012 CCOUP This is Testing material kg
    PRANIT_013 CCOUP This is Testing material kg
    PRANIT_014 CCOUP This is Testing material kg
    PRANIT_015 CCOUP This is Testing material kg
    when your selecting views
    this particular material will belongs to Po/Sales or some other areas .
    when you select basic 1 --it gives description
    select basic 2 -- it gives tax ,amount, base unit of measurement
    BDC TO BAPI
    The steps to be followed are :
    1. Find out the relevant BAPI (BAPI_SALESORDER_CHANGE for VA02).
    [for VA01 use BAPI_SALESORDER_CREATEFROMDAT2]
    2. Create a Z program and call the BAPi (same as a Funtion module call).
    2. Now, if you see this BAPi, it has
    -> Importing structures.
    eg: SALESDOCUMENT: this will take the Sales order header data as input.
    -> Tables parameters:
    eg: ORDER_ITEM_IN: this will take the line item data as input.
    Note :
    Only specify fields that should be changed
    Select these fields by entering an X in the checkboxes
    Enter a U in the UPDATEFLAG field
    Always specify key fields when changing the data, including in the checkboxes
    The configuration is an exception here. If this needs to be changed, you need to complete it again fully.
    Maintain quantities and dates in the schedule line data
    Possible UPDATEFLAGS:
    U = change
    D = delete
    I = add
    Example
    1. Delete the whole order
    2. Delete order items
    3. Change the order
    4. Change the configuration
    Notes
    1. Minimum entry:
    You must enter the order number in the SALESDOCUMENT structure.
    You must always enter key fields for changes.
    You must always specify the update indicator in the ORDER_HEADER_INX.
    2. Commit control:
    The BAPI does not run a database Commit, which means that the application must trigger the Commit so that the changes are read to the database. To do this, use the BAPI_TRANSACTION_COMMIT BAPI.
    For further details... refer to the Function Module documentation for the BAPi.
    For User Exits
    User Exits
    Screen exits are exits that allow you to use a reserved part of the screen (A subscreen) to display or input data.
    It is determined be SAP where the sub screen will be displayed.
    The syntax is: CALL CUSTOMER-SUBSCREEN
    The screen exit is not processed untill the corresponding subscreen has been created in an enhancement project,
    and the project has been activated.
    Note:
    Function codes are only processed in the main screens flow logic
    You are not allowed to enter a name for the subscreens command field
    You are not allowed to define GUI stauses
    You are not allowed to enter a value for Next screen
    The global data of the program is not available for the subscreen. Data for the subscreen is provided by function modules.
    These function modules belongs to the same function group as the subscreen Subscreens are edited with transaction CMOD.
    When you activate a project containg subscreens, the calling screen is regenerated and the subscreen is displayed next
    time you display the calling screen
    The developer must create the subscreen and the corresponding PBO and PAI modules
    How to identify screen exits
    Look after CALL CUSTOMER-SUBSCREEN in the screenprogram of the screen you want to modify.
    Use transaction CMOD menu Utillities -> SAP enhancements to search for screen exits
    MENU EXITS
    Menu exits allow you to add your own functionallity to menus. Menu exits are implemented by SAP, and are reserved menu
    entries in the GUI interface. The developer can add his/her own text and logic for the menu.
    Function codes for menu exits all start with "+"
    Example
    We want to create a new menu item in the Office menu. The text for the menu should be "Run ZTEST", and the menu will
    run report ZTEST.
    Goto transaction SE43 Area Menu Maintenance
    In Area Menu Paramenter type 'S000' (S triple Zero)
    Select Change and ignore all the warning screens
    Expand the office menu. In the buttom of the office tree you will find a menu named "Customer function"
    Double click on the text. In the pop-up screen change the text to "Run ZTEST". Note that the trsnaction code is +C01
    Goto transaction SE93 and create transaction +C01 that calls report ZTEST.
    Now you will se the menu displayed in the office tree. If you delete transaction +C01 again, the new menu will dissapear.
    USER EXITS
    User exits (Function module exits) are exits developed by SAP. The exit is implementerd as a call to a functionmodule.
    The code for the function module is writeen by the developer. You are not writing the code directly in the function module,
    but in the include that is implemented in the function module.
    The naming standard of function modules for functionmodule exits is: EXIT_<program name><3 digit suffix>
    The call to a functionmodule exit is implemented as: CALL CUSTOMER.-FUNCTION <3 digit suffix>
    Example:
    The program for transaction VA01 Create salesorder is SAPMV45A
    If you search for CALL CUSTOMER-FUNCTION i program SAPMV45A you will find ( Among other user exits):
    CALL CUSTOMER-FUNCTION '003'
    exporting
    xvbak = vbak
    xvbuk = vbuk
    xkomk = tkomk
    importing
    lvf_subrc = lvf_subrc
    tables
    xvbfa = xvbfa
    xvbap = xvbap
    xvbup = xvbup.
    The exit calls function module EXIT_SAPMV45A_003
    2. How to find user exits
    Display the program where you are searching for and exit and search for CALL CUSTOMER-EXIT
    If you know the Exit name, go to transaction CMOD. Choose menu Utillities->SAP Enhancements.
    Enter the exit name and press enter.
    You will now come to a screen that shows the function module exits for the exit.
    3. Using Project management of SAP Enhancements
    We want to create a project to enahance trasnaction VA01
    Go to transaction CMOD
    Create a project called ZVA01
    Choose the Enhancement assign radio button and press the Change button
    In the first column enter V45A0002 Predefine sold-to party in sales document . Note that an enhancement can only
    be used i 1 project. If the enhancement is allready in use, and error message will be displayed
    Press Save
    Press Components. You can now see that enhancement uses user exit EXIT_SAPMV45A_002. Double click on the exit.
    Now the function module is displayed. Double click on include ZXVVAU04 in the function module
    Insert the following code into the include: E_KUNNR = '2155'.
    Activate the include program. Go back to CMOD and activate the project.
    Goto transaction VA01 and craete a salesorder. Note that Sold-to-party now automatically is "2155"
    Have look at this links
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCCIOFFI/BCCIOFFI.pdf
    http://www.sapgenie.com/abap/ole.htm
    http://help.sap.com/saphelp_46c/helpdata/en/59/ae3f2e488f11d189490000e829fbbd/frameset.htm
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCCIOFFI/BCCIOFFI.pdf
    Creation of Field Exits
    Step by step procedure for creating Field Exits
    There are eight steps to creating a field exit:
    Step 1: Determine Data Element
    Step 2: Go To Field Exit Transaction
    Step 3: Create Field Exit
    Step 4: Create Function Module
    Step 5: Code Function Module
    Step 6: Activate Function Module
    Step 7: Assign Program/Screen
    Step 8: Activate Field Exit
    Step 1: Determine Data Element
    - Before you can begin adding the functionality for a field exit, you must know the corresponding data element.
    - An easy way to determine the data element associated to a particular screen field is to:
    Go the appropriate screen.
    Position the cursor in the appropriate field.
    Press eF1f for field-level help.
    Click on the eTechnical infof pushbutton (or press eF9f) on the help dialog box.
    On this Technical Information dialog box, the data element will be specified if the field is 'painted' from the ABAP/4 Dictionary.
    Step 2: Go To Field Exit Transaction
    - The transaction to create field exits is CMOD.
    - You can use the menu path Tools -> ABAP/4 Workbench -> Utilities -> Enhancements -> Project management.
    - From the initial screen of transaction CMOD, choose the Text enhancements -> Field exits menu path.
    - After choosing this menu path, you will be taken to the field exits screen. From here, you can create a field exit.
    NOTE : Even though you use transaction CMOD to maintain field exits, you do not need to create a project to activate field exits.
    Step 3: Create Field Exit
    - From the field exit screen of transaction CMOD, choose the Field exit -> Create menu path.
    - After choosing this menu path, a dialog box will prompt you for the appropriate data element .
    - Enter the data element name and click the eContinuef pushbutton.
    - Now, you will be able to create the function module associated to the data elementfs field exit.
    Step 4: Create Function Module
    - You will automatically be taken to the Function Library (SE37) after entering a data element name and clicking the eContinuef pushbutton.
    - In the eFunction modulef field, a function module name will be defaulted by the system based on the data element specified. This name will have the following convention:
    FIELD_EXIT_<data element>
    - You can add an identifier (an underscore followed by a single character ).
    - The first function module for a data elementfs field exit must be created without an identifier.
    - To create the function module, click on the eCreatef pushbutton, choose menu path Function module -> Create, or press eF5f.
    - After choosing to create the function module, you will get the warning: "Function module name is reserved for SAP". This message is just a warning so a developer does not accidentally create a function module in the field exit name range. By pressing eEnterf, you will be able to go ahead and create the function module.
    - Before coding the function module, you will have to specify the function modules attributes -- function group, application, and short text.
    Step 5: Code Function Module
    - From the function modulefs attributes screen, click on the eSource codef pushbutton or choose the Goto -> Function module menu path to the code of the function module.
    - Here you will add your desired functionality for the field exit.
    - Remember that field exitfs function module will have two parameters -- one importing parameter called "INPUT" and one exporting parameter called "OUTPUT". These parameters will be set up automatically by the system.
    - You must remember to assign a value to the OUTPUT field. Even if the value does not change, it must be moved from the INPUT field to the OUTPUT field.
    Step 6: Activate Function Module
    - After coding the function module, you must remember to activate it.
    - Use the Function module -> Activate menu path to activate the function module.
    - At this point, you can return to the field exit transaction.
    - You should be able to 'green arrow' back to this transaction.
    - When you return to the field exit transaction, you will see an entry for the newly created field exit.
    - At this point, the field exit is global. That is, it applies to all screens that use a particular data element. On any screen that uses the data element, the corresponding field exit function module will be triggered, once it is active.
    - Also, the field exit will not be triggered yet because it is inactive.
    Step 7: Assign Program/Screen
    - This step is only needed if you want to make a field exit local.
    - To make a field exit local, select the field exit and click on the eAssign prog./screenf pushbutton.
    - In the dialog box , indicate the appropriate program name and screen number.
    This information indicates that the field exit is local to the specified screen in the specified program.
    - In the dialog box, you determine which function module gets executed for the field exit by specifying the identifier in the eFld. Exitf field.
    - If this field is left blank, the function module triggered will be 'FIELD_EXIT_<data element>'.
    - If a single-character identifier is entered into the field, the function module triggered will be 'FIELD_EXIT_<data element>_<identifier>'.
    Step 8: Activate Field Exit
    - The field exit must be active for it to be triggered by the system.
    - Activate the field exit by choosing the Field exit -> Activate menu path.
    - After assigning the field exit to a change request, its status will change to eActivef and it will be triggered automatically on the appropriate screen(s).
    NOTE : In order to activate the field exit the profile parameter abap/fieldexit = YES must be set on all application servers
    Thanks & regards
    Sreenivasulu P

  • BADI to get GR done flag , Final Invoice flag and Delivery completed flag

    Hi all,
    An Idoc needs to be triggered for PO line items to indicate different flags. As soon  as MIGO or MIRO is done for PO line item, I have to check three flags namely GR done flag , Final Invoice flag and Delivery completed flag and send information of these flags as set.
    I want to know which BADI or User exit will give information  to indicate that either of one or all above flags are set for PO line item as soon as MIGO or MIRO is used.
    Thanks in advance,
    Madhura

    HI,
    When Purchase order is created with reference to contract, system carry
    out the check whether Document date of PO should be within contract
    "validity start" and "vaidity end" date. If document date is outside
    the "validity start" and "validity end" date of PO, message 06 040
    "Validity period of contract does not start until &" or message
    06 041 " Validity period of contract expired on &" is raised.
    Same check is also carried out during any change in PO (txn ME22N).
    Please use one of following option to close the PO.
    1. Change the category of message 06041 as warning in customization.
    Txn OLME.
    Environment Data -> Define Attributes of System Messages ->System
    Messages
    2. Change the validity end date in contract and close the Purchase order. Validity end date can be reverted.
    BR
    Nadia Orlandi

Maybe you are looking for

  • IPad cannot email a one-page PDF correctly

    This has been a persistent issue since I first bought my iPad 2.5 years ago. Now I'm on iOS 7 and it's still a problem. Create a file in Pages (doesn't matter what app you create the file with). Then send the file from the app as a PDF.  If the file

  • Line Terminator

    The preference change for line terminator in the environmental settings doesn't seem to change the line terminator for table file exports (for example INSERT). I don't get separate lines when viewed by MS Notepad no matter which setting I use, there

  • Phones should be open...

    Nokia started with the 'Phones should be open to anything.' to show their open nature... I would like to see Nokia go even further, by addressing to 'Phones should be open'. The N900 is a good example of an open platform for development. The PushN900

  • ORA-12154: TNS:Could not resolve service name. (WIS 10901).

    HI Gurus, we have the following scenario... Weu2019ve installed Busines Objects EDGE 3.1 SP3. The server of this installation is MS Windows Server 2003 Enterprise Edition SP2, Intel ® Xeon Enterprise TM CPU 2.80 GHz 6.5 RAM. In the Server we have SAP

  • Genius Not So Smart?

    I've had this problem on both my Mac and iPhone in iTunes. I choose a song to build a genius playlist off of and get this message: Try Again This song does not have enough related songs to create a Genius Playlist. The song was from an album, ("Amazi