Exit for production order creation that update BOM explosion date

Hi Guros
does any one know a user exit for production order creation that update BOM explosion date = AUFLD.
or a UE that run before the BOM explosion.
thanks.

Dear,
I dont think user exist will work for you,
You need to find BAdi for it, cl_exithandler=>get_class_name_by_interface .
Or try with SE84,
Enter the package name and check the " Enhancements"
Regards,
R.Brahmankar

Similar Messages

  • 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

  • IDoc Configuration for Production Order Creation and Change

    Hi All,
    Please Help me out for IDoc Configuration for Production Order Creation and Change
    I have found the IDoc for Production Order
    Messgae Type : LOIPRO and IDoc type : LOIPRO01
    Actually my requirment is to send the (LOIPRO01 )IDoc from SAP R/3 to XI system ,when ever the Production Order Created and Changed,
    I have done following Configurations:
    1. RFC Destination created for XI system
    2. PORT was created for XI
    3. Partner profile created WE20 and LOIPRO01 IDoc is added in OutBound Perameter.
    I need to know how to do the followning.
    1. How do i configure the outbound Production order idocs when Production Order is created or changed.
    2. in NACE (Output control) which is the Application for Production Order.
    3. How can I set IDoc as output Type for Production Order Creation.
    Thanks in advance
    Dhanabal T

    Hi Michal,
    I know that it is the old thread but still want to get clarified from you out of curiosity.
    Unlike other IDOC, i actiavated change pointers for LOIPRO
    1.message and idoc type is linked
    2.function module , message type , idoc type is linked
    function module used is CLOI_MASTERIDOC_CREATE_LOIPRO
    3.BD64, distribution model is created and distributed
    4. port and partner profile is in place.
    5. IDOC is not getting generated after creating the process order.
    do we need to activate the change documents for the message type in BD52,
    if yes can you please provide the object types for the same.
    or i am missing something else. please guide me in this regards.
    Thanks in advance for your time.
    S.Janagar

  • IDOC/BAPI for Production order creation from Legacy system

    Hi all
    We are using an interface to create Production orders from legacy to SAP. Would you recommend an IDOC or a BAPI to create Production orders. If IDOC or BAPI then could you please mention which one?
    thanks a bunch

    Hi John,
    For your purposes, please use BAPI for production order creation from legacy system. There is no standard inbound IDoc available to use. SAP has an IDoc for outbound interface only (message type LOIPRO).
    If there is an inbound IDoc available, I would recommend to use an IDoc.
    IDoc technology has excellent error handling and will allow you to reprocess an error (if any).
    BAPI is also good approach to use and fast in term of  processing.
    For BAPI approach, you can use BAPI BAPI_PRODORD_CREATE.
    Hope this will help.
    Regards,
    Ferry Lianto

  • BAPI for Production order creation against wbs element

    dear all,
    I am using BAPI (BAPI_PRODORD_CREATE) for Production order creation against wbs element.I am putting following input paramters in this
    material no,
    order type
    plant
    qty
    basic start dt & end dt
    wbs
    But during GRN it is not taking the account assignment as project stock i.e. its picking movement type 101 but it should be 101Q.
    For this what changes are required.
    regards
    ravi arora

    Hi,
    2 options i can think of:
    1. Create a BDC program by recording co10
    2. Create a planned order with order type PR using BAPI_PLANNEDORDER_CREATE, specify the WBS element & other details. Now use BAPI_PRODORD_CREATE_FROM_PLORD to create a production order with reference to the planned order created earlier.
    I believe option 2 should meet your need. Check & revert.
    Regards,
    Vivek

  • User exit for Production Order status

    Hi all ,
    Pl tell me about the : user exit for Production Order status
    ( i want CLSD status after settlement of the Production order .)
    regards,

    Hi,
    for production order you have exits PPCO0001 - PPCO0023. In transaction SMOD you can see the documentation for all this exits. Actually I think exit PPCO0007 could be a possiblity for you. This exit is called by saving the order.
    But maybe it would be better for you to use a special status profile? A user status is set if settlement status is set.
    Also BADI WORKORDER_UPDATE could be interessting for you.
    Regards,
    Sabine

  • User exit for Production order confirmation during goodsmovement

    Hi Guru's
    Am in need to find the user exit for Equipment master creation. Equipmentmaster will be created when the goods movement 101 happens.  can someone help me out to find the user exits. thanks

    Hi,
    Ok thanks for that.For Co11n please find the user exits below.But i am not sure which will suit your requirment.Please let me know for any further help.
    CONF0001  Enhancements in order confirmation
    CONFPI01  Process order conf.: Calculate cust.specific default va
    CONFPI02  Process order confirmation: Customer spec. input checks
    CONFPI03  Process order conf.: Cust. spec. check after op. select
    CONFPI04  Process order conf.: Customer specific input checks 2
    CONFPI05  Process order conf.: Cust. spec. enhancements when savi
    CONFPI06  Process order confirmation: Actual data transfer
    CONFPM01  PM/SM order conf.: Determine cust. specific default val
    CONFPM02  PM/SM order confirmation: Customer specific input check
    CONFPM03  PM/SM order conf.: Cust. spec. check after op. selectio
    CONFPM04  PM/SM order conf.: Customer specific input check 2
    CONFPM05  PM/SM order conf.: Cust. specific enhancements when sav
    CONFPP01  PP order conf.: Determine customer specific default val
    CONFPP02  PP order conf.: Customer specific input checks 1
    CONFPP03  PP order conf.: Cust. specific check after op. selectio
    CONFPP04  PP order conf.: Customer specific input checks 2
    CONFPP05  PP order conf.: Customer specific enhancements when sav
    CONFPP06  PP Order Confirmations: Actual Data Transfer
    CONFPP07  Single Screen Entry: Inclusion of User-Defined Subscree
    CONFPS01  PS confirmation: Determine customer specific default va
    CONFPS02  PS confirmation: Customer specific input checks 1
    CONFPS03  PS confirmation: Customer specific check after op. sele
    CONFPS04  PS confirmation: Customer specific input checks 2
    CONFPS05  PS confirmation: Customer specific enhancements when sa
    Thanks,

  • User Exit For production Order Information System

    Dear All,
    I am looking for an User Exit,BADi's for production order Information System where i can see the Quantity which is already produced & The Quantity which is already passed from Quality.I mean the GR Quantity against the Production Order and against that Quantity how much is passed from the Quality.
    This is an Urgent Requirement from The Customer.
    Please Help.
    Thanks
    Sujay Joshi

    Dear
    You use QA33 report with following fields,,,,here you will get all required
    Inspection lot     
    Material     
    Plant     
    Insp. lot quantity     
    Base unit of measure     
    System status     
    Order     
    Unrestrictd-use stck     
    Scrap quantity     
    Sample     
    Blocked stock     
    Reserves     
    New material     
    MatTransfer posting     
    Posted to batch     
    Return to vendor     
    Other quantity     
    Other quantity 2     
    Quantity to be posted     
    Long-term sample qty     
    Inspected quantity     
    Destroyed quantity     
    Actual lot quantity     
    Defect. qty in IQty

  • User exit for Production Order release

    Hi Experts,
    Any User eixt for Prouction Order Mass processing.
    Before releasing the production order i have to do some checks. Can you please provide right user exit. More reward points with best solutions.
    Thanks
    Cris

    Hi,
              check the following userexits and BADI's for Production Order
    Enhancement/ Business Add-in Description
    Enhancement
    PPCO0010 Enhancement in make-to-order production - Unit of measure
    PPCO0012 Production Order: Display/Change Order Header Data
    PPCO0013 Change priorities of selection crit. for batch determinati
    PPCO0015 Additional check for document links from BOMs
    PPCO0016 Additional check for document links from master data
    PPCO0017 Additional check for online processing of document links
    PPCO0018 Check for changes to production order header
    PPCO0019 Checks for changes to order operations
    PPCO0021 Release Control for Automatic Batch Determination
    PPCO0022 Determination of Production Memo
    PPCO0023 Checks Changes to Order Components
    STATTEXT Modification exit for formatting status text lines
    PPCO0009 Enhancement in goods movements for prod. process order
    CCOWB001 Customer exit for modifying menu entries
    COIB0001 Customer Exit for As-Built Assignment Tool
    COZF0001 Change purchase req. for externally processed operation
    COZF0002 Change purchase req. for externally procured component
    PPCO0001 Application development: PP orders
    PPCO0002 Check exit for setting delete mark / deletion indicator
    PPCO0003 Check exit for order changes from sales order
    PPCO0004 Sort and processing exit: Mass processing orders
    PPCO0005 Storage location/backflushing when order is created
    PPCO0006 Enhancement to specify defaults for fields in order header
    PPCO0007 Exit when saving production order
    PPCO0008 Enhancement in the adding and changing of components
    Business Add-in
    AFABD_CHANGE Change Relationship
    CAUFVD_CHANGE BAdI: Overall Network Scheduling with Selection
    PPPI_SEL_ORD_EXT_REL
    SIDAT_UPDATE Change date of price simulation
    Regards

  • User exit for Production Order

    Hi Gurus,
    What user exits are there for Production Order?
    Can anyone throw light.
    Thanks in advance,
    Srini

    Dear ,
    User Exit in SAP PP-Production Order
    PPCO0001 |Application development: PP orders                          |
    PPCO0002
    Check exit for setting delete mark / deletion indicator
    PPCO0003
    Check exit for order changes from sales order
    PPCO0004
    Sort and processing exit: Mass processing orders
    PPCO0005
    Storage location/backflushing when order is created
    PPCO0006
    Enhancement to specify defaults for fields in order header
    PPCO0007
    Exit when saving production order
    PPCO0008
    Enhancement in the adding and changing of components
    PPCO0009
    Enhancement in goods movements for prod. process order
    PPCO0010
    Enhancement in make-to-order production - Unit of measure
    PPCO0012
    Production Order: Display/Change Order Header Data
    PPCO0013
    Change priorities of selection crit. for batch determination
    PPCO0014
    Select process orders for external relationships
    PPCO0015
    Additional check for document links from BOMs
    PPCO0016
    Additional check for document links from master data
    PPCO0017
    Additional check for online processing of document links
    PPCO0018
    Check for changes to production order header
    PPCO0019
    Checks for changes to order operations
    PPCO0020
    Process order: Display/change order header data
    PPCO0021
    Release Control for Automatic Batch Determination
    PPCO0022
    Determination of Production Memo
    |  PPCO0023 |Checks Changes to Order Components 
    Regards
    JH

  • User exits for production order

    Hello,
    Hope all had good weekend. I need some help and would appreciate if someone can guide me here.
    I have a requirement where I need to develop an enhancement point for production orders transaction CO02.
    The enhancement will check the user's authorization profile. Based on authorization profile, enhancement point will decide and direct 'CO02-Change production Order' OR 'ZCO02 - restricted production orders'.
    Here are few question I have related.
    1. What user exit I should use for this above requirement ? This should be triggered whenever CO02 is being called either from SAP easy access menu or from a different transaction.
    2. How can I check/read users authorization profile within this user exit/enhancement point ?
    3. Based on the profile, how do I direct to CO02 or ZCO02 ?
    Will highly appreciate if someone could please share their knowledge on this.
    Thanks,
    JMC

    Hi J,
    can u tell me whats there in ZCO02 - restricted production orders', have u seen SHD0 -->creating screen/transaction variants ?
    Disabling tabs in SHD0
    Regards
    Prabhu

  • User exit for production order settlement

    Hi Experts,
    Can anybody tell me if there is any user exit which will make GR and settlement of Production Orders at the same time i. e. as soon as production order is confirmed ( movement type 101 happens) the same production order will be settlelled immediately.............
    Thanks on advance for your answer.
    Regards,
    Bijay

    Hi,
    for production order you have exits PPCO0001 - PPCO0023. In transaction SMOD you can see the documentation for all this exits. Actually I think exit PPCO0007 could be a possiblity for you. This exit is called by saving the order.
    But maybe it would be better for you to use a special status profile? A user status is set if settlement status is set.
    Also BADI WORKORDER_UPDATE could be interessting for you.
    Regards,
    Sabine

  • Run time error while running BDC for production order creation and confirmation:

    Dear Gurus,
    We have a situation, where the users are trying to do the entries creation of order or confirmation (through manual and BDC). But, if there is any kind of a deficit quantities in consumption or GR quantity, then it is going to run time error and Dumps are coming in program SAPLCORB
    and the transaction code is coming for CO11N.
    How to avoid this error to run the production system in smoothing way...Any flash lights on this will be great full
    Regards,
    Madhu.G

    Hi Madhu,
    Expert Caetano has rightly point out. Refer Note 1840705 - RAISE_EXCEPTION short dump if running CO11N in background
    Cause
    The short dump is triggered because SAP transaction CO11N contains new GUI elements that cannot always be dealt with in a background process,
    such as the confirmation texts.
    Resolution
    SAP recommends that the standard production order BAPIs, such as BAPI_PRODORDCONF_CREATE_TT, should be used to post a confirmation in background.
    If this is not feasible, the following workaround may be uses:
    Define a confirmation profile in transaction OPK0; 
    In the detail areas, remove the area "Confirmation text"; 
    Set this profile as standard, so that it is chosen automatically by the system when a batch-job
    is started; 
    Assign this confirmation profile to the batch user with transaction SU3 using parameter CORUPROF.
    Also see Note 429432 - CO11N: Batch input in background dumps if long text is maintained
    Refer to note 1154692 - Endless loop during confirmation in background if you doing Auto GR during confirmations
    Thanks & Regards,
    Ramagiri

  • User Exit For Production Order Confirmation Using CO15 or COGI

    Hi all,
    I need user exit for the production order confirmation so that i can set
    AFPO-ELIKZ and AUFM-ELIKZ (delivery completedu2019 status flag) to Blank......
    Thanks

    hi,
    check these exits.
    CONFPP01                                PP order conf.: Determine customer specific default values
    CONFPP02                                PP order conf.: Customer specific input checks 1
    CONFPP03                                PP order conf.: Cust. specific check after op. selection
    CONFPP04                                PP order conf.: Customer specific input checks 2
    CONFPP05                                PP order conf.: Customer specific enhancements when saving
    CONFPP06                                PP Order Confirmations: Actual Data Transfer
    CONFPP07                                Single Screen Entry: Inclusion of User-Defined Subscreens
    CONFPS01                                PS confirmation: Determine customer specific default values
    CONFPS02                                PS confirmation: Customer specific input checks 1
    CONFPS03                                PS confirmation: Customer specific check after op. selection
    CONFPS04                                PS confirmation: Customer specific input checks 2
    CONFPS05                                PS confirmation: Customer specific enhancements when saving
    CONF0001                                Enhancements in order confirmation
    CONFPI01                                Process order conf.: Calculate cust.specific default values
    CONFPI02                                Process order confirmation: Customer spec. input checks 1
    CONFPI03                                Process order conf.: Cust. spec. check after op. selection
    CONFPI04                                Process order conf.: Customer specific input checks 2
    CONFPI05                                Process order conf.: Cust. spec. enhancements when saving
    CONFPI06                                Process order confirmation: Actual data transfer
    CONFPM01                                PM/SM order conf.: Determine cust. specific default values
    CONFPM02                                PM/SM order confirmation: Customer specific input checks 1
    CONFPM03                                PM/SM order conf.: Cust. spec. check after op. selection
    CONFPM04                                PM/SM order conf.: Customer specific input check 2
    CONFPM05                                PM/SM order conf.: Cust. specific enhancements when saving
    use the exit which contains both structures AFPO,AUFM.

  • BAPI for Production Order creation ?

    Hi Experts,
    I am new to PP module and as per my requirement I have to:
    1. Create Production order in ECC 6.0
        After searching BAPI explorer, SDN and other sites I could see that there is no BAPI for Create Production order.
        In one of the link I could find FM CLOI_CHANGES_UPL_31 used to create Production order in SAP.
    Is there any BAPI to create ??
    Can anyone let mw know right FM or BAPI to create Production order with an example.
    2. And I have to:
    Delete Production order
    which BAPI is used for deletion of Prd Ord
    BAPI_PRODORD_SET_DEL_INDICATOR or BAPI_PRODORD_SET_DELETION_FLAG
    For Confirm Production order - in ECC 6.0 Let mw know the BAPI for this ..
    Really helpful if you answer my queries...
    Thanks
    Uday

    Hi udaya,
    use the BAPI 'BAPI_PRODORD_CREATE'
    The following BAPIs are available confirmation of production orders:
        Entry
            Time ticket
            ProdOrdConfirmation.CreateTimeTicketMultiple
            BAPI_PRODORDCONF_CREATE_TT
            Time event
            ProdOrdConfirmation.CreateAtHeaderLevelMultiple
            BAPI_PRODORDCONF_CREATE_HDR
            Order confirmation
            ProdOrdConfirmation.CreateAtHeaderLevelMultiple
            BAPI_PRODORDCONF_CREATE_HDR
            Activity confirmation
            ProdOrdConfirmation.CreateActConfMultiple
            BAPI_PRODORDCONF_CREATE_ACT
        Defaults
            Time ticket
            ProdOrdConfirmation.GetTimeTicketProposal
            BAPI_PRODORDCONF_GET_TT_PROP
            Time event
            ProdOrdConfirmation.GetTimeEventProposal
            BAPI_PRODORDCONF_GET_TE_PROP
            Order confirmation
            ProdOrdConfirmation.GetAtHeaderLevelProposal
            BAPI_PRODORDCONF_GET_HDR_PROP
        Cancelling confirmations
        ProdOrdConfirmation.Cancel
        BAPI_PRODORDCONF_CANCEL
        List of confirmations
        ProdOrdConfirmation.GetList
        BAPI_PRODORDCONF_GETLIST
        Detail data for confirmations
        ProdOrdConfirmation.GetDetail
        BAPI_PRODORDCONF_GETDETAIL
        Existence check
        ProdOrdConfirmation.ExistenceCheck
        BAPI_PRODORDCONF_EXIST_CHK
    Regards,
    Ravi

Maybe you are looking for

  • USB thumbdrive won't eject

    I formatted a USB thumbrdive as Extended + Journaled, GUID  partition. Actually I did it on 2 different thumbdrives to see if the problem would repeat and it's the same on both. I use Carbon Copy Cloner to copy the small Boot partition off my machine

  • Same PIR updation for multiple vendors

    Hi, How to update the PIR for multiple vendors at a time whenever there is change in price. Thanks, Kiran Bodla

  • Consignment returns

    Hi All gurus, I am trying to create a delivery for KR (consignment returns), when i am trying to create LR with KR its not allowing, i have chekced the copy controls, incompletion, vov7, vov8. the consignment return order item category is pikced as a

  • Displaying images in imail

    How do I get mail to display images instead of able square with a ? Keith

  • Oracle Apps Manufacturing Functional

    Can any one please tell me any institutes in Mumbai providing training in Oracle Manufacturing Functional Module.