Mandatory field in production order-reg

Hi,
In production order, I want to make Good recipient field as mandatory (AFPOD-WEMPF) how to do it.
I tried through OIAN and SHD0, it is not happening.
Regards
Karthikeyan

Hi,
You can use transaction variant with transaction SHD0.
http://help.sap.com/saphelp_webas620/helpdata/en/eb/5fab41d79b11d296190000e82de14a/content.htm
In the SAP Reference IMG, you can create transaction variants. Choose Basis Components -> Application Personalization -> Tailoring of Application Transactions -> Configure Transaction-Related Display Values for Fields (Transaction SHD0). Transaction variants allow you to preset values for fields in a transaction, set field attributes, or hide entire screens.
To execute a transaction variant, you define a variant transaction using the Transaction Maintenance transaction (SE93).
Once you have entered a transaction code and short description, choose transaction type Transaction with variant (Variant transaction).
To define a variant, enter the name of the transaction and the name of the variant. You can then use the new transaction code to start the special variant of the transaction.
Hope this will help.
Regards,
R.Brahmankar

Similar Messages

  • Mandatory field in Production order creation field

    Dea All,
    I want to have a field mandatory at the time of production order creation. in CO01 Goods Receipt Tab there is a field of Goods Recipient in the second last row. Please guide me how can i make it mandatory field.

    Dear,
    Yes it is possible through the user exist, input check is carried out for enhancement PPCO0018.
    User exit PPCO00018 should use ful for order header screens GENERAL ASSIGNMENT, GOODS RECEIPT and CONTROL tab.
    Or go to SE51 enter program  SAPLCOKO Screen No 5190 click on change and the Lay out here you can define it as Input field Take help from technical person.
    Regards,
    R.Brahmankar

  • Profit center mandatory field in sales order !

    Hi All !
    How to make profit center mandatory field in sale order can any body let me know...
    Thanks & Rgds
    Naveen

    Hi
    You can either Transaction variant SHD0/User exit
    Refer below<a href="http://www.sap-img.com/sap-sd/supressing-fields-in-sale-order.htm">Fields in Sale Order</a>
    help required: how to makes sales office field mandatory, in inquiry and qu
    Re: supress  some fiels in sales order? user exit?
    Message was edited by:
            SHESAGIRI.G

  • PR to be made mandatory field in Purchase Order

    Hello,
    PR to be made mandatory field in Purchase Order.
    How i can do this in SAP ?
    Regards
    Rahul

    Hi,
    First check your PO document type which you want to make PR number field as mandatory in ME21N.
    Then Goto -> SPRO- Material Management - Purchase order- define document type for Purchase order - E.g NB- check the field selection assignment ( NBF)
    Next,
    Goto - Define screen layout at document level ( t.code OMF4) SELECTION GROUP Reference data, item and under Field selection key as NBF.
    Field name - Purchase Requisition as Required entry with flagged check box.
    Now in purchase order for the choose document type NB=PO the PR field as required entries.
    System will allow to create PO only with reference to PR.
    Thanks
    Thiru

  • Purchase Req as mandatory field at Purchase Order

    Hi Gurus,
    I have the next problem:
    I'm trying to put purchase requisition as mandatory field at purchase order.
    At img i made the following steps:
    Materials Management > Purchasing > Purchase Order > Define screen layout at document level
    I sellected the screen layout that I want to change
    At 'reference data, item' I sellected 'purchase requisition' as 'reqd. entry'.
    Next I try to do a PO and it doesn't work...
    Anyone knows why?
    Regards
    LR

    Force buyers to create Purchase Order with ref. to a Pur. Req., Quotation or Pur. Ord.
    Transaction OMET
    Create a new entry, give it a name and tick :-
    Ref. to PReq
    Ref. to P.O.
    Ref. to quotation
    Next, you've got to associate via SU01
    Click Parameters, insert a new parameter id EFB to the authorization code.
    Type in Parameters value you want e.g. XX
    You have to assign the control for ALL the SAP buyers via thier SAP users id.
    Logoff and login again. Then try to create a Purchase Order without a reference.
    Source link: http://www.academictutorials.com/sap-mm/sap-mm-configuration-tips.asp

  • Negative quantity in deliver field in production order - CO02

    Hi All,
    I am doing production confirmation and goods receipt for production order through back ground using standard BAPI.While doing GR for production order in background the following error occured.
      System is throughing dump - Arithmatical logical conversion problem.when we analysed through ST22 we came to know that negative quantity appearing in field of delivered in production order.
      Screen name.............. "SAPLCOKO1"
      Screen number............ 0120
      Screen field............. "CAUFVD-GWEMG"
    As per standard, delivered field in production order is always in display mode only. So there will not be any chance for user to change the delivered field.
    Pls guide me how to overcome the above issue and what is exact root cause for the above problem.
    System is throwing error in change mode ( Co02) and display mode ( CO03 ) for the respective production order number
    Thanks
    P.Srinivasan

    Hi,
    This inconsistency can be solved with the following correction report. If you want to try by yourself, then implement it manually in transaction SE38 and execute in test mode first to check if the inconsistency is found. And obviously, in a TEST system first.
    If you are NOT confident about it, I recommend you to submit a support message for SAP for further investigation since this is a database inconsistency.
    Regards,
    Marcelo
    <pre>
    *& Report  ZPCON_076B                                                  *
    *& This report checks goods receipt quantity (WEMNG) and value (WEWRT) *
    *& of an order item for consistency with the corresponding material    *
    *& documents. In UPDATE mode, the quantity and the value calculated    *
    *& from the material documents will be written to database table AFPO. *
    REPORT  zpcon_076b LINE-SIZE 90.
    INCLUDE lcokotyp.
    TABLES: afpo.
    SELECTION-SCREEN COMMENT /1(80) text1.                      "#EC NEEDED
    SELECTION-SCREEN COMMENT /1(80) text2.                      "#EC NEEDED
    SELECTION-SCREEN COMMENT /1(80) text3.                      "#EC NEEDED
    SELECTION-SCREEN COMMENT /1(80) text4.                      "#EC NEEDED
    SELECTION-SCREEN COMMENT /1(80) text5.                      "#EC NEEDED
    SELECTION-SCREEN ULINE.
    SELECTION-SCREEN COMMENT /1(80) texta.                      "#EC NEEDED
    SELECT-OPTIONS r_aufnr FOR afpo-aufnr.
    SELECTION-SCREEN ULINE.
    SELECTION-SCREEN BEGIN OF BLOCK block WITH FRAME TITLE title."#EC NEEDED
    SELECTION-SCREEN COMMENT /1(72) texty.                      "#EC NEEDED
    SELECTION-SCREEN BEGIN OF BLOCK block2 WITH FRAME.
    PARAMETERS: testmode RADIOBUTTON GROUP mode DEFAULT 'X'.
    PARAMETERS: update RADIOBUTTON GROUP mode.
    SELECTION-SCREEN END OF BLOCK block2.
    SELECTION-SCREEN COMMENT /1(72) textz.                      "#EC NEEDED
    SELECTION-SCREEN END OF BLOCK block.
    DATA: BEGIN OF ls_afpo.
            INCLUDE STRUCTURE afpo.
    DATA: END OF ls_afpo.
    DATA  lt_afpo LIKE ls_afpo OCCURS 0.
    DATA: BEGIN OF ls_mseg.
            INCLUDE STRUCTURE mseg.
    DATA: END OF ls_mseg.
    DATA  ls_mseg2 LIKE ls_mseg.
    DATA  lt_mseg LIKE ls_mseg OCCURS 0.
    DATA  ls_mkpf TYPE mkpf.
    DATA l_initial_ltrmi TYPE co_ltrmi VALUE IS INITIAL.
    DATA l_orders TYPE sytabix.
    DATA l_entries TYPE sytabix.
    DATA l_sum_wemng TYPE wemng.
    DATA l_sum_wewrt TYPE wewrt.
    DATA l_error TYPE xfeld.
    INITIALIZATION.
      text1 = 'This report checks goods receipt quantity (WEMNG) and'.
      text2 = 'value (WEWRT) of an order item for consistency with the '.
      text3 = 'corresponding material documents. In UPDATE mode, the'.
      text4 = 'quantity and the value calculated from the material'.
      text5 = 'documents will be written to database table AFPO.'.
      texta = 'Please specify order numbers of orders to be processed.'.
      texty = 'If TESTMODE is set, no database update will occur.'.
      textz = 'Set radio button UPDATE for updating the database entries.'.
      title = 'Mode'.
    AT SELECTION-SCREEN.
    orders specified?
      IF r_aufnr IS INITIAL.
        MESSAGE e889(co) WITH 'Please specify order numbers'.
      ENDIF.
    START-OF-SELECTION.
    select order items
      SELECT *
             FROM  afpo
             INTO  TABLE lt_afpo
             WHERE aufnr IN r_aufnr
             AND ( dauty = auftragstyp-fert
                OR dauty = auftragstyp-netw
                OR dauty = auftragstyp-inst
                OR dauty = auftragstyp-rma
                OR dauty = auftragstyp-bord ).
      DESCRIBE TABLE lt_afpo LINES l_orders.
    check order items
      LOOP AT lt_afpo INTO ls_afpo.
        REFRESH lt_mseg.
        CLEAR l_sum_wemng.
        CLEAR l_sum_wewrt.
        CLEAR l_error.
        SELECT *
               FROM  mseg
               INTO  TABLE lt_mseg
               WHERE matnr = ls_afpo-matnr
                 AND werks = ls_afpo-pwerk
                 AND aufnr = ls_afpo-aufnr
                 AND aufps = ls_afpo-posnr
                 AND kzbew = 'F'
               %_HINTS ORACLE 'rule'.
        IF NOT sy-subrc IS INITIAL.
        no goods movements --> nothing to do.
          DELETE lt_afpo.
          CONTINUE.
        ENDIF.
        LOOP AT lt_mseg INTO ls_mseg.
          IF ls_mseg-shkzg ='S'.
          inward movement
            IF NOT ls_mseg-dmbtr IS INITIAL.
              l_sum_wewrt = l_sum_wewrt + ls_mseg-dmbtr.
            ENDIF.
            IF NOT ls_mseg-bstmg IS INITIAL.
              l_sum_wemng = l_sum_wemng + ls_mseg-bstmg.
            ELSE.
              IF ls_mseg-erfme = ls_afpo-amein.
                l_sum_wemng = l_sum_wemng + ls_mseg-erfmg.
              ELSE.
                IF ls_mseg-meins = ls_afpo-amein.
                  l_sum_wemng = l_sum_wemng + ls_mseg-menge.
                ELSE.
                  WRITE: 'ERROR - Order', ls_afpo-aufnr COLOR 6.
                  DELETE lt_afpo.
                  l_error = 'X'.
                  EXIT.
                ENDIF.
              ENDIF.
            ENDIF.
            ls_mseg2 = ls_mseg.
          ELSE.
          outward movement
            IF NOT ls_mseg-dmbtr IS INITIAL.
              IF ls_mseg-dmbtr NE ls_mseg-bualt AND
                 NOT ls_mseg-bualt IS INITIAL.
                l_sum_wewrt = l_sum_wewrt - ls_mseg-bualt.
              ELSE.
                l_sum_wewrt = l_sum_wewrt - ls_mseg-dmbtr.
              ENDIF.
            ENDIF.
            IF NOT ls_mseg-bstmg IS INITIAL.
              l_sum_wemng = l_sum_wemng - ls_mseg-bstmg.
            ELSE.
              IF ls_mseg-erfme = ls_afpo-amein.
                l_sum_wemng = l_sum_wemng - ls_mseg-erfmg.
              ELSE.
                IF ls_mseg-meins = ls_afpo-amein.
                  l_sum_wemng = l_sum_wemng - ls_mseg-menge.
                ELSE.
                  WRITE: 'ERROR - Order', ls_afpo-aufnr COLOR 6.
                  DELETE lt_afpo.
                  l_error = 'X'.
                  EXIT.
                ENDIF.
              ENDIF.
            ENDIF.
          ENDIF.
        ENDLOOP. "AT lt_mseg
      only continue if no error in the calculation occurred
        CHECK l_error IS INITIAL.
        IF ls_afpo-wemng = l_sum_wemng AND
           ls_afpo-wewrt = l_sum_wewrt.
        values are correct, no update necessary
          DELETE lt_afpo.
          CONTINUE.
        ENDIF.
        FORMAT: COLOR 1.
        WRITE: / 'Order', ls_afpo-aufnr, 'material', ls_afpo-matnr.
        FORMAT: COLOR OFF.
        WRITE: /3 'Order item data   : quantity',
                  ls_afpo-wemng UNIT ls_afpo-amein, ls_afpo-amein, 'value',
                  ls_afpo-wewrt CURRENCY ls_mseg-waers, ls_mseg-waers.
        WRITE: /3 'Material documents: quantity',
                  l_sum_wemng UNIT ls_afpo-amein, ls_afpo-amein, 'value',
                  l_sum_wewrt CURRENCY ls_mseg-waers, ls_mseg-waers.
        FORMAT: COLOR 2.
        WRITE: /3 'Material doc.  BWART', 30 'stock qty  UoM',
               52 'entry qty  UoM', 77 'value  Curr'.
        FORMAT: COLOR OFF.
        LOOP AT lt_mseg INTO ls_mseg.
          WRITE: /3 ls_mseg-mblnr, ls_mseg-zeile, ls_mseg-bwart,
                   ls_mseg-menge UNIT ls_mseg-meins, ls_mseg-meins,
                   ls_mseg-bstmg UNIT ls_mseg-bstme, ls_mseg-bstme,
                   ls_mseg-dmbtr CURRENCY ls_mseg-waers, ls_mseg-waers.
        ENDLOOP.
        IF NOT update IS INITIAL.
        set delivery date
          IF l_sum_wemng IS INITIAL.
          initial delivery quantity --> initial delivery date
            UPDATE afpo SET   ltrmi = l_initial_ltrmi
                        WHERE aufnr = ls_afpo-aufnr
                          AND posnr = ls_afpo-posnr.
          ELSE.
          read posting date from last valid goods receipt
            SELECT SINGLE * FROM  mkpf
                            INTO  ls_mkpf
                            WHERE mblnr = ls_mseg2-mblnr
                              AND mjahr = ls_mseg2-mjahr.
            IF sy-subrc IS INITIAL.
              UPDATE afpo SET   ltrmi = ls_mkpf-budat
                          WHERE aufnr = ls_afpo-aufnr
                            AND posnr = ls_afpo-posnr.
            ELSE.
            leave LTRMI untouched
            ENDIF.
          ENDIF.
        set quantity and value
          UPDATE afpo SET   wemng = l_sum_wemng
                            wewrt = l_sum_wewrt
                      WHERE aufnr = ls_afpo-aufnr
                        AND posnr = ls_afpo-posnr.
          FORMAT: COLOR COL_POSITIVE.
          WRITE: /3 'Order item data corrected from material documents.'.
          FORMAT: COLOR OFF.
        ENDIF.
        ULINE.
      ENDLOOP. "AT lt_afpo
      WRITE: / 'Number of checked order items     :', l_orders.
      DESCRIBE TABLE lt_afpo LINES l_entries.
      WRITE: / 'Number of inconsistent order items:', l_entries.
      IF NOT update IS INITIAL    AND
         NOT l_entries IS INITIAL.
        WRITE: / 'Inconsistencies were corrected from material documents.'
                  COLOR COL_POSITIVE.
      ENDIF.
      ULINE.
    </pre>
    Edited by: Wilian Segatto on Jan 25, 2011 12:27 PM

  • Profit center field in production order master data in KKF3

    Hi GUrus,
    is there any way of mass updating the profit center field in production order master data in KKF3 transaction. PLease help
    Anusha

    HI charlie,
    When i try to change the profit center, the system gave this message. We already have a profit center for a production order and we need to change the profit center, That is when we are getting the errror message.
    You have changed the profit center from AR00620800 to AR00620301. This is only allowed when the corresponding configuration was made in Customizing. Then this message is only a warning, which you can ignore.  PLease help
    Thanks
    Anusha

  • Cost Center field in Production Order CO01 and PO tables

    Hi SAP Consultants,
    Is there any Cost Center field in Production Order transaction CO01 ?
    What are the tables where Production order data is stored/saved ?
    Any help would be appreciated.
    Thanks in advance.

    Need to understand your purpose first. Let's not make it any more technical than it should be, talking in terms of fields and layouts.
    All the replies given before mine are referring to the operational costs - which are what are passed on "for performing each operation" of the production order. These are the costs coming to the production order from the work center where the operation is performed. At the end of several operations, the production order would have collected all these costs of different operations, and also those of the materials used in the process. There may be other (overhead, etc) costs coming on to the production order too.
    If you're looking for one "cost center" for the entire production order, what cost center is this? Is it the department to which you want to settle the production costs? This is possible, that all the costs accumulated in the production order over the course of its life are finally "settled" to a different cost object, which can be an inventory account, or a sales order, an internal order, or a cost center etc. (There are exceptions, where a production order need not be settled but lets leave this to save us some complexity).
    What exactly are you looking for? What is the business purpose you are trying to achieve? Or is it just a purely technical reason to write a report or something? Even then we need to know the purpose and objective of the report/enhancement before being able to answer your question.
    -Ram

  • I have change some fields in  (Production order component )

    I have change some fields in (Production order component overview)

    Hi,
    do you want to hide or disable the fields or add new fields ??? by the way can you please let us know the transaction that you are referring to ??
    Regards,
    Santosh

  • Credit memo and mandatory fields in Sales order

    Dear all,
    I have 2 problems, hoping these are not too basic questions I'm asking here.
    1). I have created a sales order for credit memo's and I'm using the standard billing type G2.
    The amounts are negative in the order & in the billing document, however, when transferring to FI, it is posted as a normal invoice (Debit customer) instead of credit memo.
    Where are the posting keys defined or where do you determine which kind of posting will happen in FI based on the billing document?
    2). When creation a sales order (VA01), the sales office and sales group should be mandatory fields. What is the best way to do this? Or is the only option to go via the document completeness check?
    Many thanks!
    Best regards.

    Hi There,
    > 1). I have created a sales order for credit memo's and I'm using the standard billing type G2.
    > The amounts are negative in the order & in the billing document, however, when transferring to FI, it is posted as a normal invoice (Debit customer) instead of credit memo.
    >
    > Where are the posting keys defined or where do you determine which kind of posting will happen in FI based on the billing document?
    This is the standard SAP behavior. Simple thing, All the values are negative so when it will post to FI
    It will be like
    Dr  Customer Invoice amount ( which is negative ) so end result is +ve. ( as Debit is -)
    I hope its understandable.
    For example:
    While creation of simple invoice say of 1000 $
    Entries were Dr Customer 1000 $
                         Cr Revenue    1000$
    Now After Credit memo
                        Dr Customer    -1000 $
                         Cr Revenue    -1000 $
    Which will nullify each other.
    > 2). When creation a sales order (VA01), the sales office and sales group should be mandatory fields. What is the best way to do this? Or is the only option to go via the document completeness check?
    The best way is to include these two fields in the Sales order incomplete procedure in OVA2. Put Error/warning as required by you.
    Thanks,
    Raja

  • Additional Field in Production Order

    Hi,
    I need to add a new field in the production order in the seperate Tab. Can anybody tell me the userexit for this. I need the same field to save some data from that sales order. To save the data i know the Exit but for additional field need ur help.
    Thanks
    SISL

    Hi,
    The exit you're using (PPCO0007) should meet your need.
    The exit - PPCO0006 is called during creation of order, so there could be an option where a user might delete these values.
    Another alternative which you can think of is BADi - WORKORDER_UPDATE.
    Good luck.
    Regards,
    Vivek

  • Quantity Withdrawn field in production order

    Hi all,
    I have a doubt
    there is a component A in production order
    Required quantity is 10
    Initially i issue 15 qty's then the same qty gets updated in "Quantity withdrawn" field (component overview screesn)
    Then i reverse 3 qty's of component A,which is very much visible in documented goods movement
    Whereas the same is not getting update in the ""Quantity withdrawn" field ,Still 15 qty is appearing against "Quantity withdrawn" field
    This may be normal behaviour of the system,I'm not sure
    Can you please confirm on this
    If not then please give me possible reasons why it is not getting updated ?
    Thanks,
    SVP

    Hi all,
    I also wonder about this (actually it's an issue for this customer ... ). As same as production order, Network order (it's activity more correctly) also show withdrawn quantity in CN25 transaction.
    In my case, I've done good issue quantity 2 EA, then I reverse it. and same again. finally I do good issue 2 EA.
    GI         -2 EA : CN25
    cancel GI 2 EA : CN29
    GI         -2 EA : CN25
    cancel GI 2 EA : CN29
    GI         -2 EA : CN25
    (Yeah, normally it will not happen often but it can.)
    I expect withdrawn Quantity 2 EA but it shows 10 EA. So have wonder with actual data table MSEG. It has SMBLN value (referred document number to cancel) as I think. It's very normal.
    Why withdrawn field doesn't count that cancel quantity?
    Is there any configuration that I missed ? or Is it normal result?
    But System should do show 'Cancelled GI Quantity' (so that end-user can notify actual GI quantity) to make it understand.
    Regards,
    Yeum
    Edited by: Hee Chul Yeum on Jan 22, 2009 10:50 AM

  • ED pricing key is mandatory field in purchase order

    Hi,
    where can you specify that the IS-OIL field Excise Duty pricing key (OIINEX) should not be a mandatory field?
    In our production system and test system this is the case, but in our development system where we have turned on new G/L this field is now mandatory.
    Thanks in advance
    Best regards
    Sven

    Dear Sven,
    Did you find the right answer for mentioned above issue? Now I have the same problem in our testing system...
    Thanks in advance!

  • Fixing the quanitity field in production order

    HI,
    I create a sales order for 10,000 numbers and then after MRP run a production order for same 10,000 numbers is created. My Client has people in the production department  who change the prodcution order quantity to say 12,000. Is there any way by which the quanity field in the production order can be fixed and made non modifiable.
    Thanks
    vikrant

    Hi,
      You need to create a status profile in bs02
       Double click the status profile.
       Enter the user status as crtd
       Tick the initial status as enabled
       Place the cursor on the status profile
       Select the object type as PP ORDER HEADER
        Now choose the user status
        Double click the user status
        Goto  create mode
         select change and set forbid radio button
         save.
        Assign this status profile to order type in opjh tcode.
       Now once you have created the production order the system automatically
        forbids any change.
           Regards,
        nandha

  • Make Scrap portion field in production order header as display only

    Hi Experts,
    We have a requirement to make scrap field(CAUFVD-GASMG) in production order header as display field only. We do not want users to enter any values here to denote the quantity scrapped in production orders. I am not aware of any configuration to make this field as display only. Please let me know which user exit or BADI available for this purpose. We do not want to use any screen variants and transaction variants and would like to restrict this at order type or plant level.
    Thanks
    Rijil

    Hello Rijil,
    If not with variants than check with enhancement.
    PPCO0006  Enhancement to specify defaults for fields in order head
    PPCO0012  Production Order: Display/Change Order Header Data
    PPCO0018  Check for changes to production order header
    Regards,

Maybe you are looking for

  • How to get web application to use Tuscany without conflicting with SAP SDO

    Hi, We are attempting to run a web application on SAP NetWeaver CE 7.1 SP1 which uses Tuscany SDO.  As it now stands We must use Tuscany because the web application will not run with the SAP SDO implementation provided by Netweaver. To ensure that Tu

  • Mac Book Pro space bar issue...

    I just received my MBP and the space bar is very difficult to engage. This small thing makes typing an extreme test of patience. I got it at Future Shop Canada two days ago. Should I call Apple Support or deal with Future Shop? It has taken a while t

  • Not logging in?

    After I enter my @mac info in preferences of ichat nothing happens. Everything in the buddy menu is greyed out. I tried a test message to tryichatav, but I get an error saying "could not send instant message to tryichatav" . If I go back to my prefer

  • Re: Replace Nec Tokin on Satelite A300

    Hello, I have a Toshiba Satellite A300 that when the transformer is connected the computer shut down ... if it were started on the current blocked and did not carry the windows. Replaces NEC Tokin then the other. Now the problem is that he does not i

  • Duplicate invoice for third-party IR order

    The order items are 3rd party, IR, nonstock materials. The first invoice was created overnight on 04/28/2007 and that's before the invoice from the vendor was received (05/07/2007). The receive of the vendor's invoice triggered the second invoice on