Manual creation of user aliases for email

Hi,
I was able, to create email users using command line tools. Works fine so far. Is there also a way to add aliases and distribution lists.
If so, how does the syntax look like.
Cheers
Eric

Hi Subash,
Finally am able to create client and user also successfully.
by again doing the client copy with change of  selected profile SAP_CUST----.
Customizing.
Regds
phanikumar

Similar Messages

  • How can I reduce the amount of user prompts for Email setup in Apple Configurator?

    I am working on deploying profiles via Apple's new Apple Configurator which allows me to install apps and settings exactly how I want them. My question pertains to the email setup where anything left blank in the payload gets prompted on the device for user input. Is there anyway to have the user only enter in their user name and password once and use that for the SMTP outgoing settings as well? I'd like to reduce the user interaction to a minimal.Currently they enter in their full name, email address, user name for incoming, password for incoming, and then user name AGAIN for outgoing (I checked the box for 'Outgoing password same as incoming'). Is there anyway to retain the username and avoid having the user enter it in twice?
    If not, I can make do with how it is, but was rather curious if this is possible. Any help would be greatly appreciated.

    I'll try this again starting it as new, but when I restored it before (after deleting all the apps and music off it) it didn't help.  Thanks for the suggestion!

  • I use Earthlink for email but want to change.  What else do Apple-users like for emails?  I use MBA and iPod Touch.  My concerns are security and ease of changing pswds --had a scary experience at Elink.

    I use Earthlink for email but want to change.  What else do Apple-users like?  I use MBA mid 2012 and iPod 5 touch.  Concerns are email security and ease of changing pswds.

    Apple has made several well-publicised statements regarding their commitment to privacy and the security of their various iCloud services. If they were to fall short of a goal they stated so prominently for so long, it would have a material effect on the company's value, not to mention being extremely embarrassing. I think they're pretty serious about it.
    Like anything else though, iCloud is as secure as the passwords you use. To change your iCloud password read iCloud: Change your iCloud account password.

  • Get logged in users name for email notification

    Hi all,
    I am using LC Update 1 with email notifications. In the notification email I would like to write:
    Hi "logged in users name"
    You have got a task in your to do-list...
    The thing is that I can not get the id of the user because the email is sent before he/she completes any step in the process. So I guess I need to look up the user in the same way as the notification-function makes the lookup... How is this done?
    Can you help me here?
    Sincerely
    Kim

    You can use a parameter for the user ID:
    http://livedocs.adobe.com/livecycle/8.2/wb_help/001330.html
    scott

  • Aliases for email on iCloud

    I have used mac.com then me.com now icloud.com, now I cannot find a way to create new aliases for my email....where is it is at all or am I doomed to my old aliases and no more(used to allow 5).

    This article has information about email aliases. http://help.apple.com/icloud/index.html?localePath=English.lproj#mm6b1a490a
    Best of luck.

  • Creation of  Enterprise aliases for LDAP or AD accounts in BO XIR2

    Hello All,
    As per the SAP note --u201C1401058 I tried to run the script attached for creating enterprise aliases for LDAP account in BO XIR2.However am getting the error "Couldn't create SessionManager ".Below is my system configuration:
    BO XIR2
    Windows 2003
    Tomcat 5.5
    Kindly advice how this error could be resolved and also is there any other way to create enterprise aliases for ~5000 LDAP account in BO XIR2.
    Regards,
    Aniket
    +919665262169

    What happens if you hit update without trying to add a group? This is not a normal issue to get a page not displayed error but it has happened on occasion, possible causes have been bad LDAP groups mapped in the plugin, LDAP configuration issues, LDAP SSL configuration issues, or deployment corruption etc. It really hard to tell. Your best bet may be to open an incident with support(authentication team) to have an engineer take a look.
    Regards,
    Tim

  • Creation of user steps for an custyomizing client ex: 100 in SAP R3 4.7 EE

    Hi All,
    What are the steps involved for creation of new client EX: 100 as a customizing client and what is the procedure to create an user in client 100, becaz am able to create a client but user is not created proeprly
    PLZ help me
    ADV THANX
    Regds
    phanikumar

    Hi Subash,
    Finally am able to create client and user also successfully.
    by again doing the client copy with change of  selected profile SAP_CUST----.
    Customizing.
    Regds
    phanikumar

  • Transfer order creation Any User-Exit for item ?

    Hi all,
    I’m working with transfer order. What I’d like is to apply to the TO item my own fields.
    Is there a possibility to overwrite some of the fields of the ‘LTAP’ segment at transfer order item creation, using any enhancement (User-exit, …) ?
    Transaction used to create TO is LT43.
    I’ve try to use MWMTO001( but it doesn’t work, only for specific data (z table)).
    I’ve also try MWMTO008 ( doesn’t work for that )
    Fields I want to overwrite are VLTYP(Source storage type), VLPLA(Source Storage Bin), VPTYP, VLQNR.
    Hope someone can help me…Please ?

    Hi Erwan,
    give MWMTO004(EXIT_SAPLL03A_005) a try. It's a different event/time in document creation, but looks good comparing your fields you want to change.
    It's of course not only 'overwriting' VLTYP, VLPLA, ... but implementation of own / additional removal strategy. Might be more complicated, but sounds better for whole process.
    Regards,
    Christian

  • Manual creation of Project Site for a project is taking old project site template.

    Dear All,
    I have modified the project site and save it as a template to associate it with an EPT so that the modification will reflect in new project sites.
    For existing projects, I am deleting the old project sites (after taking backup) and recreating so that new modifications will be there for existing projects and I am able to do so.
    But, for 1 of the project, when I have deleted the project site and recreated, still it is taking the old template (i.e. new modifications has not been seen).
    Kindly advice in some areas so that I can jump in and around and can find out a solution so that the project site will take modified project template.
    Example to get the issue in an easy way:
    ProjectA:
    Project Site: http://epm/pwa/ProjectA
    Issue List:
    Column: Category [data type as Choice: Cat1, Cat2, Cat3]
    Have saved 1 project site as a template and associated with an EPT with the following changes:
    Column: Category [data type as Choice: Choice1, Choice2, Choice3]
    Then, deleted the project site: http://epm/pwa/ProjectA and recreated.
    So, it should take the modifications in the project site.
    But, it is showing as Column: Category [data type as Choice: Cat1, Cat2, Cat3].
    Regards,
    Shravan

    Dear Guillaume,
    Thanks for your response.
    Please seem my comments inline:
    Which Project Server version do you use?
    PS 2010
    It is working well and as expected for all projects except for 1 specific project?
    Yes. It is working well for other projects except 1 project.
    Has this project something particular?
    Nope. It is similar as other projects.
    How do you proceed to create the new project site? Do you go to the site actions, then new site and pick up your new template?
    First I have modified 1 of the project site and saved that site as a template.
    Then, I have deleted the existing project site (from Project Sites under Operational Policies) and recreated so that project site will gets created from the new template. But, it's not happening.
    Regards,
    Shravan

  • Needs Manual Verification by User for 508 Compliant Docs

    Can anyone tell me how to fix that?
    I'm making a document 508 compliant using Adobe Acrobat 9 Pro and everything runs smoohtly, except it won't become compliant, because of this message in the summery report.
    Does anyone know how I can fix that?
    Thanks!

    When you have the Accessibility Full Check dialog open & have selected the Section 508 checking option you'll observe the (a) through (p).
    These correspond the paragraphs in 1194.22 (which, in turn, have a correlation to WCAG 1.0).
    What needs manual verification will depend on which paragraph the comment is associated with.
    Reference: https://www.section508.gov/index.cfm?fuseAction=stdsdoc#Web
    In all cases (c) will have "Needs manual verification by user".
    For (c), the requirement is that all information conveyed with color is also available without color.
    Only a "warm body" can do this; hence, "Needs manual verification...".
    You may find Duff Johnson's article "How Section 508 applies to PDF" useful.
    http://www.appligent.com/talkingpdf-howsection508appliestopdf
    An additional observation — A "pass" from Full Checker (using both "Adobe PDF" & "Section 508..." does not mean you've an Accessible PDF (S508 compliant &/or usable). One example would be the Scope of table header cells (Row | Column | Both | None) and Table Summary. Neither are evaluated.
    You'll have to provide the appropriate value for Scope and provide the text for the Table Summary.
    After using Full Checker you will need to "walk" the structure tree in the Tags panel (with the Highlight option selected) to look for possible issues.
    Are any lists present properly tagged?
    Are Headings properly used?
    Do the various chunks of content have the correct PDF Tag?
    Tags inappropriately used can really goober the PDF.
    As always, proper mastering in the authoring file results in minimizing remediation activity with Acrobat Pro in the requisite post-processing.
    Be well...
    Message was edited by: CtDave

  • What are the User Exits for Sales Order creation process?

    Hi,
    what are the User Exits for Sales Order creation process? how can I find them?
    thanks in advance,
    will reward,
    Mindaugas

    Please check this info:
    User Exits In Sales Document Processing
    This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
    Involved program components
    System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
    MV45ATZZ
    For entering metadata for sales document processing. User-specific metadata must start with "ZZ".
    MV45AOZZ
    For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".
    MV45AIZZ
    For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".
    MV45AFZZ and MV45EFZ1
    For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.
    User exits in the program MV45AFZZ
    The user exits which you can use for modifications in sales document processing are listed below.
    USEREXIT_DELETE_DOCUMENT
    This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
    For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
    The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
    USEREXIT_FIELD_MODIFICATION
    This user exit can be used to modify the attributes of the screen fields.
    To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
    The usage of the field groups (modification group 1-4) is as follows:
    Modification group 1: Automatic modification with transaction MFAW
    Modification group 2: It contains 'LOO' for step loop fields
    Modification group 3: For modifications which depend on check tables or on other fixed information
    Modification group 4: is not used
    The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
    This FORM routine is called up by the module FELDAUSWAHL.
    See the Screen Painter manual for further information on structuring the interface.
    USEREXIT_MOVE_FIELD_TO_VBAK
    Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
    The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
    USEREXIT_MOVE_FIELD_TO_VBAP
    Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".
    The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
    USEREXIT_MOVE_FIELD_TO_VBEP
    Use this user exit to assign values to new fields at the level of the sales document schedule lines.
    The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
    USEREXIT_MOVE_FIELD_TO_VBKD
    Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".
    The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
    USEREXIT_NUMBER_RANGE
    Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
    The user exit is called up in the FORM routine BELEG_SICHERN.
    USEREXIT_PRICING_PREPARE_TKOMK
    Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
    USEREXIT_PRICING_PREPARE_TKOMP
    Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
    USEREXIT_READ_DOCUMENT
    You use this user exit if further additional tables are to be read when importing TA01 or TA02.
    The user exit is called up at the end of the FORM routine BELEG_LESEN.
    USEREXIT_SAVE_DOCUMENT
    Use this user exit to fill user-specific statistics update tables.
    The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
    Note
    If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
    USEREXIT_SAVE_DOCUMENT_PREPARE
    Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
    The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
    User exits in the program MV45AFZA
    USEREXIT_MOVE_FIELD_TO_KOMKD
    Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
    USEREXIT_MOVE_FIELD_TO_KOMPD
    Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
    USEREXIT_MOVE_FIELD_TO_KOMKG
    Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
    USEREXIT_MOVE_FIELD_TO_KOMPG
    Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
    USEREXIT_REFRESH_DOCUMENT
    With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
    For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
    The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
    The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
    User-Exits in program MV45AFZB
    USEREXIT_CHECK_XVBAP_FOR_DELET
    In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
    USEREXIT_CHECK_XVBEP_FOR_DELET
    In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
    USEREXIT_CHECK_VBAK
    This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
    USEREXIT_CHECK_VBAP
    This user exit can be used to carry out additional checks (e.g. for completion) at item level.
    USEREXIT_CHECK_VBKD
    The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
    USEREXIT_CHECK_VBEP
    This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
    USEREXIT_CHECK_VBSN
    You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
    USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
    USEREXIT_FILL_VBAP_FROM_HVBAP
    You can use this user exit to fill additional fields in the sub-item with data from the main item.
    USEREXIT_MOVE_FIELD_TO_TVCOM_H
    You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
    USEREXIT_MOVE_FIELD_TO_TVCOM_I
    You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
    User-Exits for product allocation:
    The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
    USEREXIT_MOVE_FIELD_TO_COBL
    Option to include new fields in structure COBL.
    USEREXIT_COBL_RECEIVE_VBAK
    Option to assign values from the document header to the new fields.
    USEREXIT_COBL_RECEIVE_VBAP
    Option to supply values from the item to the new fields.
    USEREXIT_COBL_SEND_ITEM
    A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
    USEREXIT_COBL_SEND_HEADER
    A changed field can be copied from the structure to the header (see source text MV45AFZB)
    USEREXIT_SOURCE_DETERMINATION
    You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
    USEREXIT_MOVE_FIELD_TO_ME_REQ
    With this user exit you can include additional fields for the following fields:
    EBAN (purchase requisition)
    EBKN (purchase requisition-account assignment)
    USEREXIT_GET_FIELD_FROM_SDCOM
    Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
    USEREXIT_MOVE_WORKAREA_TO_SDWA
    You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
    User-Exits for first data transfer:
    The following user exits can only be used for the first data transfer.
    Note
    Only use the user exits if the names/fields do NOT have the same name.
    USEREXIT_MOVE_FIELD_TO_VBAKKOM
    Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
    USEREXIT_MOVE_FIELD_TO_VBAPKOM
    Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
    USEREXIT_MOVE_FIELD_TO_VBEPKOM
    Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
    USEREXIT_MOVE_FIELD_TO_VBSN
    You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
    USEREXIT_MOVE_FIELD_TO_KOMKH
    You can use this user exit to include new fields for batch determination (document header).
    USEREXIT_MOVE_FIELD_TO_KOMPH
    You can use this user exit to include new fields for batch determination (document item).
    USEREXIT_CUST_MATERIAL_READ
    You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
    USEREXIT_NEW_PRICING_VBAP
    Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
    USEREXIT_NEW_PRICING_VBKD
    Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
    User-Exits in Program MV45AFZD
    USEREXIT_CONFIG_DATE_EXPLOSION
    The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
    User exits in the program FV45EFZ1
    USEREXIT_CHANGE_SALES_ORDER
    In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
    If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
    User-Exits in Program RV45PFZA
    USEREXIT_SET_STATUS_VBUK
    In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
    The following workareas are available for this user exit:
    VBUK (header status)
    FXVBUP (item status)
    FXVBUV (Incompletion)
    USEREXIT_SET_STATUS_VBUP
    In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
    The following workareas are available for this user exit:
    FXVBAP (Item data)
    FXVBAPF (Dynamic part of order item flow)
    FXVBUV (Incompletion)
    USEREXIT_STATUS_VBUK_INVOICE
    You can use this user exit to influence billing status at header level.
    User exits in the screens
    Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
    Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
    For field transports, you do not have to make changes or adjustments.
    Example
    A new field, VBAK-ZZKUN, should be included in table VBAK.
    If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
    User Exits in Program MV45AFZ4
    USEREXIT_MOVE_FIELD_TO_KOMK
    You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
    USEREXIT_MOVE_FIELD_TO_KOMP
    You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
    User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
    EXIT_SAPFV45P_001
    You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.
    Regards
    Eswar

  • Scenarios for "manual creation of inspection lot"

    Hi QM gurus!!
       I would just like to ask the main function of QA01 or "<b>Manual creation of inspection lot</b>"
    What are the cases/scenarios where this tcode is used? I would really appreciate if you could help me.. Thank you.
    Regards,
    Heinrick Palad

    HI,
    The table below provides a brief overview of the functions you can use to process inspection lots. Appropriate cross references are included for the more extensive tasks or for those for which additional information is available.
    Prerequisites
    The inspection lot processing functions can be linked to various authorizations that are checked by the system whenever you try to process an inspection lot. The following types authorizations are relevant to inspection lot processing:
    Material authorizations
    The material authorization for QM is stored in the material master. For more information, see  Creating and Changing QM-Specific Data for a Material.
    Inspection type authorizations
    This authorization controls which inspection type the user can access in order to create an inspection lot. The inspection type authorization is plant-specific.
    No authorization checks are executed in QM when an inspection lot is created automatically.
    Features
    Function
    Pushbutton / Menu path
    What you should know
    Accessing the initial screen for the inspection lot processing functions
    Logistics ® Quality management ® Quality inspection ® Inspection lot processing ® Inspection lot
    Creating an inspection lot manually
    See Creating an Inspection Lot Manually
    Changing an inspection lot
    Choose Change
    Enter the number of the inspection lot you want to change and then choose Enter.
    Displaying an inspection lot
    Choose Display
    Enter the number of the inspection lot you want to display and then choose Enter.
    Creating a new batch in an inspection lot
    See Batch Creation in Inspection Lots
    Cancelling an inspection lot
    Call up an inspection lot in the change mode and choose Inspection lot ® Functions ® Cancel lot.
    See Cancellation of an Inspection Lot
    Blocking/unblocking an inspection lot
    Call up an inspection lot in the change mode and choose Inspection lot ® Functions ® Block lot.
    To unblock an inspection lot, choose Inspection lot ® Functions ® Unblock lot.
    When you block an inspection lot, you cannot process the lot further. You must unblock the lot if you want to perform any additional operations.
    Transferring stock in an inspection lot
    See Stock Transfers
    Making corrections to inspection lot quantities
    See Corrections to Inspection Lot Quantities
    Creating a QM order
    Call up an inspection lot in the create or change mode and choose Goto ® Insp. lot acc. assgnmt.
    See QM Order Creation
    Resetting the sample calculation
    See Resetting the Sample Calculation
    Printing inspection instruction/sample-drawing instruction
    See Printout of Instructions
    Approving a task list
    Call up an inspection lot in the create or change mode and choose Inspection lot ® Functions ® Give approval
    If the task lists in your company must be approved before they can be used, you should make sure that only approved task lists are assigned to an inspection lot. If the system selects a task list that has not yet been approved, you can use this function to approve the task list (provided you have the necessary material authorization).
    this link help u.
    http://help.sap.com/saphelp_erp2004/helpdata/EN/be/00bbe7ca5311d2961800a0c930e04c/frameset.htm
    reward is usefull.
    tahnks.

  • User Exit for ME21 PO Creation at the time of saving--Urgent

    Hi,
    Can some one help me out in finding the user exit for PO creation at the time of saving.
    The Requirement is:
    I need to create a custom field in EKKO table.
    After appending the structure with the field to the EKKO table, i need to create a PO.
    Now i need to update the field which has been created at the time of pressing the SAVE button.
    I need to update the EKKO table it self.
    I could find the user exits but none of them have the EKKO table either in Changing or in Tables.
    Thanks,

    Hi,
              You may want to check this user exits.
    EXIT_SAPMM06E_012 - Check Customer-Specific Data Before Saving
    EXIT_SAPMM06E_013 - Update Customer-Specific Data in Purchasing Document
    Here is the list of available user exits for ME21.
    EXIT_SAPMM06E_001 - Other Number Range or Own Document Number
    EXIT_SAPMM06E_004 - User Exit for Cust.-Specific Control of Import Data Screens in Purchasing
    EXIT_SAPMM06E_005 - Field Selection Control: Vendor Address Screen
    EXIT_SAPMM06E_006 - Export Data to Customer Subscreen for Purchasing Document Header (PBO)
    EXIT_SAPMM06E_007 - Export Data to Customer Subscreen for Purchasing Document Header (PAI)
    EXIT_SAPMM06E_008 - Import Data from Customer Subscreen for Purchasing Document Header
    EXIT_SAPMM06E_009 - Reset Customer Data at Beginning of New Document (Without Dialog)
    EXIT_SAPMM06E_012 - Check Customer-Specific Data Before Saving
    EXIT_SAPMM06E_013 - Update Customer-Specific Data in Purchasing Document
    EXIT_SAPMM06E_014 - Read Customer-Specific Data when Importing Purchasing Document
    EXIT_SAPMM06E_016 - Export Data to Customer Subscreen for Purchasing Document Item (PBO)
    EXIT_SAPMM06E_017 - Export Data to Customer Subscreen for Purchasing Document Item (PAI)
    EXIT_SAPMM06E_018 - Import Data from Customer Subscreen for Purchasing Document Item
    EXIT_SAPMM06E_020 - User Exit: Change Document for Requisitions (Conversion into PO)
    EXIT_SAPMM06E_021 - Fulfillment of Target Value: Release Orders Against a Contract
    <b>Reward points</b>
    Regards

  • Creation of rule file for adding aliases to Members

    Please help me in creation of rule file for adding of aliases to the members. I have created a new alias table along with default alias table.
    These are the members and alias names for the newly created alias table.
    0000002452     TA     
    0000002459     HJ
    0000002460     HK
    0000002462     HM
    0000004012     CB
    0000004015     EA
    0000004025     BA
    0000004070     DA
    0000004087     GC     
    0000004088     FD
    0000006231     CM
    0000009103     WP
    0000009106     WV
    0000009126     WW
    0000008458     NH
    0000008475     NY
    0000008481     NF
    0000008483     NG
    The below are the members and aliases for the default alias table.
    0000001209     P&S Storage Facilities
    0000001210     1210 US Procurement & Supply
    0000002452     Warren Truck Assembly
    0000002459     Toledo I Assembly
    0000002460     Toledo II Assembly
    0000002462     Toledo III Assembly
    0000004001     US Manufacturing Group Office
    0000004012     Jefferson North Assembly
    0000004015     Belvidere Assembly
    0000004025     Sterling Heights Assembly
    0000004070     Newark Assembly
    0000004087     St Louis North Assembly II
    0000004088     St Louis South Assembly II
    0000004199     Pilot Operations
    0000004501     Opm
    0000005111     Kokomo Casting
    0000005203     Trenton Engine
    0000005205     Kenosha Engine
    0000005209     New Mack Avenue Engine
    0000005304     Detroit Axle
    0000005305     Kokomo Complex
    0000005308     Indiana Transmission
    0000005403     New Castle Machining & Forge
    0000005404     McGraw Glass
    0000005406     Toledo Machining
    0000006203     Warren Stamping
    0000006204     Twinsburg Stamping
    0000006215     Sterling Heights Stamping
    0000006231     Conner Avenue Assembly
    0000002100     2100 Sales & Marketing
    0000005221     GEMA - Plant1 Ops
    0000009006     9006 Canadian Customs
    0000009008     Canadian Manufacturing Group Office
    0000009103     Windsor Assembly
    0000009104     Etobicoke Casting
    0000009106     Pillette Road Assembly
    0000009126     Bramalea Assembly
    0000008458     Atos
    0000008475     Saltillo Truck Plant
    0000008481     Toluca Assembly Plant
    0000008483     Lago Alberto Truck Plant
    Now I have to create rule files to update these aliases.
    Please elaborate, so that it will be clear for me. As I am new, please make it up with steps.

    You dont need to create a rule file. You can create a alias table like this in a notapad
    $ALT_NAME 'First'
    0000002452 TA
    0000002459 HJ
    0000002460 HK
    0000002462 HM
    0000004012 CB
    0000004015 EA
    0000004025 BA
    0000004070 DA
    0000004087 GC
    0000004088 FD
    0000006231 CM
    0000009103 WP
    0000009106 WV
    0000009126 WW
    0000008458 NH
    0000008475 NY
    0000008481 NF
    0000008483 NG
    $END
    and Save it as First.alt and You can import like this
    1)Open the outline in edit mode.
    2)Select Outline > Import alias table.
    3)In the Open dialog box, select the alias table import file.
    4)Click OK.
    go to outline properties and the new alias table must be made Set as active to view the alias names.
    you can create and import up to 10 alias tables

  • Need User Exits for Creation of Delivery and for Posting Goods Issue

    Hi,
    I need User Exits for
    Creation of Delivery
    Posting Goods Issue
    I need to make some checks regarding customer license expiration and if checks fail, I need to stop Creation of Delivery and Posting Goods Issue.
    Thanks in advance,
    Will reward,
    Mindaugas

    In the delivery you can use userexit USEREXIT_SAVE_DOCUMENT_PREPARE to make your checks and send an error message to the user in case they fail.
    You can find this user exit (form routine) in include MV50AFZ1.
    Hope that helps,
    Michael

Maybe you are looking for