Display Range field in *transaction flow*  in order type  OR

HI friends,
please give me an example where we use the field settingsUALL,UHAU,UMAR  for Display Range in transaction flow  in order type OR
path:
img->sale&distribution->sales->sales documents -> sales document header-.define sales document types
select OR
under transation flow
there is field Display range with options UALL,UHAU,UMAR
Thanks

Is it relevent to BOM explosion
I need to know , whether by selecting UHAU
can ristrict the BOM sub items  explosion
could you give me a senarieo where exactly we use this setting  for display range
Thanks for your quick response

Similar Messages

  • Add fields to transaction VOV8  - Sales Order types maintaines

    Hi,
    I want to know if it is possible to add new fields to view V_TVAK (threw table TVAK), and then add them also to the view in transaction VOV8  for a sales order type.
    Thanks naama.

    Hi Nilmini,
    In My case, I have added custom fields to MDC change screen by using /AFS/MDC_CHANGE_CUSTOM_FIELDS but its not appearing in Grid list display. Would like to appreciate if you can Help me to achieve this.
    Regards,
    Jelli

  • Priority field mandatory for planning plant-order type

    Hi
    Is there a standard way through configuration that I may contol priority field in order header to be mandatory for some order types only in one planning plant?
    Problem is that if I make the priority field mandatory for order type, it will be so for all the planning plants which i dont want. Also i dont want it to mandatory at planning plant level since there are many order types under one planning plant and requirement is to make priority field mandatory only for some order types under this plant.
    TIA.

    Hi Tehsin
    Thanks for the reply.
    In the transaction we can separately make it mandatory for either planning plant or order type.
    My requirement is for combination of both.

  • ALV grid is not displaying few fields of final internal table of type DMBTR

    hello frnds,
    i am displaying 10 fields in ALV grid using field catalog.
    among them five fields are currency fields on which i doing some arithematic operations. but all these fields are not getting displayed in alv grid.
    here is my code....
    declaring final strucutre to generate report
    TYPES:BEGIN OF ty_final,
              gjahr   TYPE gjahr,       " Year
              wwert   TYPE wwert_d,     " Traslation date
              bukrs   TYPE bukrs,       " company code
              hkont   TYPE hkont,       " General ledger account
              txt20   TYPE txt20_skat,  " Account name
              belnr   TYPE belnr_d,     " Purchase order number
              shkzg   TYPE shkzg,       " Dt/Cr indicator
              dmbtr1   TYPE dmbtr,       " Ammount in local currency
              v_alc   TYPE dmbtr,       " Ammount in local currency
              wrbtr   TYPE wrbtr,       " Ammount in foreign currency
              ebeln   TYPE ebeln,       " Purchase order number
              ebelp   TYPE ebelp,       " Item number
              matnr   TYPE matnr,       " Material number
              menge   TYPE menge_d,     " Qunatity
              meins   TYPE meins,       " Unit of measure
              stprs   TYPE stprs,       " Std material master
              v_iv    TYPE dmbtr,       " Invoice value
              pswsl   TYPE pswsl,       " Currency
              v_erc   TYPE dmbtr,       " Exchange rate calculated
              v_op    TYPE dmbtr,       " Order price
              v_uos   TYPE dmbtr,       " Unit order to stock
              v_io    TYPE dmbtr,       " Invoice to order
              v_uv    TYPE dmbtr,       " Unit value
              v_t     TYPE dmbtr,       " Total
              v_d     TYPE dmbtr,       " Differecne
              netpr   TYPE bprei,       " Net price in purchasing document
              v_total TYPE dmbtr,       " Total
              v_os    TYPE dmbtr,       " Order to stock
              v_ito   TYPE dmbtr,       " Invoice to order
              saknr   TYPE saknr,       " G/L account number
           END OF ty_final.
    FORM move_data.
      IF NOT i_bseg[] IS INITIAL.
        LOOP AT i_bseg INTO wa_bseg.
          wa_final-gjahr  = wa_bseg-gjahr.
          wa_final-bukrs  = wa_bseg-bukrs.
          wa_final-hkont  = wa_bseg-hkont.
          wa_final-belnr  = wa_bseg-belnr.
          wa_final-shkzg  = wa_bseg-shkzg.
          wa_final-wrbtr  = wa_bseg-wrbtr.
          wa_final-ebeln  = wa_bseg-ebeln.
          wa_final-ebelp  = wa_bseg-ebelp.
          wa_final-matnr  = wa_bseg-matnr.
          wa_final-menge  = wa_bseg-menge.
          wa_final-meins  = wa_bseg-meins.
          wa_final-pswsl  = wa_bseg-pswsl.
          wa_final-dmbtr1  = wa_bseg-dmbtr.
          wa_final-saknr  = wa_bseg-saknr.
          wa_final-v_total = wa_bseg-dmbtr.
          READ TABLE i_bkpf INTO wa_bkpf WITH KEY bukrs = wa_bseg-bukrs.
          IF sy-subrc = 0.
            wa_final-wwert = wa_bkpf-wwert.
          ENDIF.
         CLEAR wa_bkpf.
          READ TABLE i_mbew INTO wa_mbew WITH KEY matnr = wa_bseg-matnr.
          IF sy-subrc = 0.
            wa_final-stprs = wa_mbew-stprs.
          ENDIF.
         CLEAR wa_mbew.
          READ TABLE i_ekpo INTO wa_ekpo WITH KEY ebeln = wa_bseg-ebeln.
          IF sy-subrc = 0.
            wa_final-netpr = wa_ekpo-netpr.
          ENDIF.
         CLEAR wa_ekpo.
          READ TABLE i_skat INTO wa_skat WITH KEY saknr = wa_bseg-saknr.
          IF sy-subrc = 0.
            wa_final-txt20 = wa_skat-txt20.
          ENDIF.
    calculating output values
          IF wa_bseg-shkzg = 'H'.
            wa_final-v_alc = -1 * wa_bseg-dmbtr.
          ELSEIF wa_bseg-shkzg = 'S'.
            wa_final-v_alc = 1 * wa_bseg-dmbtr.
          ENDIF.
         DATA : l_c_v_alc TYPE p DECIMALS 2,
         l_c_v_iv TYPE p DECIMALS 2.
         l_c_v_alc = wa_final-v_alc.
          IF wa_bseg-menge NE 0.
            wa_final-v_iv = wa_bseg-dmbtr / wa_bseg-menge.
          ENDIF.
          IF wa_bseg-dmbtr NE 0.
            wa_final-v_erc  = wa_bseg-wrbtr   / wa_final-dmbtr1.
          ENDIF.
          IF wa_final-v_erc NE 0.
            wa_final-v_op   = wa_ekpo-netpr   / wa_final-v_erc.
          ENDIF.
          wa_final-v_uos  = wa_mbew-stprs   - wa_final-v_op.
          wa_final-v_io   = wa_final-v_iv   + wa_final-v_uos.
          wa_final-v_uv   = wa_final-v_uos  + wa_final-v_io.
          wa_final-v_t    = wa_final-v_uv   + wa_bseg-menge.
          wa_final-v_d    = wa_final-v_t    - wa_final-v_alc.
          wa_final-v_os   = wa_final-v_uos  * wa_bseg-menge.
          wa_final-v_ito  = wa_final-v_io   * wa_bseg-menge.
          CLEAR wa_bseg.
          APPEND wa_final TO i_final.
          CLEAR wa_final.
        ENDLOOP.
      ENDIF.
    ENDFORM.                    "data_retrieval
    *&      Form  build_fieldcat
          text
    -->  p1        text
    <--  p2        text
    FORM build_fieldcat.
      CLEAR wa_fieldcat.
    *  TYPES : v_alc TYPE dmbtr. "curr. " decimal 2.
    DATA: l_c_v_alc TYPE p DECIMALS 2,
    l_c_v_iv TYPE p DECIMALS 2 .
    l_c_v_alc = v_alc.
    l_c_v_iv = v_iv.
    Constant Declarations.
      CONSTANTS:
                l_c_gjahr(5)   TYPE c VALUE 'GJAHR',      " Year
                l_c_wwert(5)   TYPE c VALUE 'WWERT',      " Traslation date
                l_c_bukrs(5)   TYPE c VALUE 'BUKRS',      " company code
                l_c_hkont(5)   TYPE c VALUE 'HKONT',      " General ledger account
                l_c_txt20(10)  TYPE c VALUE 'TXT20',      " Account name
                l_c_belnr(5)   TYPE c VALUE 'BELNR',      " Doc number
                l_c_shkzg(5)   TYPE c VALUE 'SHKZG',      " Dt/Cr indicator
                l_c_dmbtr(5)   TYPE c VALUE 'DMBTR1',      " Ammount in local currency
               " l_c_v_alc      TYPE c VALUE 'V_ALC',      " Ammount in local currency
                l_c_wrbtr(5)   TYPE c VALUE 'WRBTR',      " Ammount in foreign currency
                l_c_ebeln(5)   TYPE c VALUE 'EBELN',      " Purchase order number
                l_c_ebelp(5)   TYPE c VALUE 'EBELP',      " Item number
                l_c_matnr(5)   TYPE c VALUE 'MATNR',      " Material number
                l_c_menge(7)   TYPE c VALUE 'MENGE',      " Qunatity
                l_c_meins(5)   TYPE c VALUE 'MEINS',      " Unit of measure
                l_c_stprs(5)   TYPE c VALUE 'STPRS',      " Std material master
               " l_c_v_iv(4)    TYPE c VALUE 'V_IV',           " Invoice value
                l_c_pswsl(5)   TYPE c VALUE 'PSWSL',      " Currency
                l_c_v_erc(5)   TYPE c VALUE 'V_ERC',      " Exchange rate calculated
                l_c_v_op(4)    TYPE c VALUE 'V_OP',       " Order price
                l_c_v_uos(5)   TYPE c VALUE 'V_UOS',      " Unit order to stock
                l_c_v_io(4)    TYPE c VALUE 'V_IO',       " Invoice to order
                l_c_v_uv(4)    TYPE c VALUE 'V_UV',       " Unit value
                l_c_v_t(3)     TYPE c VALUE 'V_T',        " Total
                l_c_v_d(3)     TYPE c VALUE 'V_D',        " Differecne
                l_c_netpr(5)   TYPE c VALUE 'NETPR',      " Net price in purchasing document
                l_c_v_total(7) TYPE c VALUE 'V_TOTAL',    " Total
                l_c_v_os(4)    TYPE c VALUE 'V_OS',      " Order to stock
                l_c_v_ito(5)   TYPE c VALUE 'V_ITO',      " Invoice to order
                l_c_saknr(5)   TYPE c VALUE 'SAKNR',      " G/L account number
                l_c_i_final(7) TYPE c VALUE 'I_FINAL'.    " Final internal table
    Fieldcat for fiscal year
      wa_fieldcat-col_pos   =  1.
      wa_fieldcat-tabname   = l_c_i_final.
      wa_fieldcat-fieldname = l_c_gjahr.
      wa_fieldcat-seltext_m = text-007.
      APPEND wa_fieldcat TO i_fieldcat.
      CLEAR wa_fieldcat.
    Fieldcat for Translation date
      wa_fieldcat-col_pos   =  2.
      wa_fieldcat-tabname   = l_c_i_final.
      wa_fieldcat-fieldname = l_c_wwert.
      wa_fieldcat-seltext_m = text-008.
      APPEND wa_fieldcat TO i_fieldcat.
      CLEAR wa_fieldcat.
    Fieldcat for Company code
      wa_fieldcat-col_pos   =  3.
      wa_fieldcat-tabname   = l_c_i_final.
      wa_fieldcat-fieldname = l_c_bukrs.
      wa_fieldcat-seltext_m = text-009.
      APPEND wa_fieldcat TO i_fieldcat.
      CLEAR wa_fieldcat.
    Fieldcat for General ledger account
      wa_fieldcat-col_pos   =  4.
      wa_fieldcat-tabname   = l_c_i_final.
      wa_fieldcat-fieldname = l_c_hkont.
      wa_fieldcat-seltext_m = text-010.
      APPEND wa_fieldcat TO i_fieldcat.
      CLEAR wa_fieldcat.
    Fieldcat for Account name
      wa_fieldcat-col_pos   =  5.
      wa_fieldcat-tabname   = l_c_i_final.
      wa_fieldcat-fieldname = l_c_txt20.
      wa_fieldcat-seltext_m = text-011.
      APPEND wa_fieldcat TO i_fieldcat.
      CLEAR wa_fieldcat.
    Fieldcat for Doc number
      wa_fieldcat-col_pos   =  6.
      wa_fieldcat-tabname   = l_c_i_final.
      wa_fieldcat-fieldname = l_c_belnr.
      wa_fieldcat-seltext_m = text-012.
      APPEND wa_fieldcat TO i_fieldcat.
      CLEAR wa_fieldcat.
    Fieldcat for Dt/Cr indicator
      wa_fieldcat-col_pos   =  7.
      wa_fieldcat-tabname   = l_c_i_final.
      wa_fieldcat-fieldname = l_c_shkzg.
      wa_fieldcat-seltext_m = text-013.
      APPEND wa_fieldcat TO i_fieldcat.
      CLEAR wa_fieldcat.
    Fieldcat for Ammount in local currency
      wa_fieldcat-col_pos   =  8.
      wa_fieldcat-tabname   = l_c_i_final.
      wa_fieldcat-fieldname = 'DMBTR1'.
      wa_fieldcat-seltext_m = text-014.
      APPEND wa_fieldcat TO i_fieldcat.
      CLEAR wa_fieldcat.
    Fieldcat for Ammount in local currency
      wa_fieldcat-col_pos   =  9.
      wa_fieldcat-tabname   = l_c_i_final.
      wa_fieldcat-fieldname = 'V_ALC'.
      wa_fieldcat-seltext_m = text-015.
      wa_fieldcat-ref_fieldname = 'DMBTR'.
    wa_fieldcat-no_sign   = 'X'.
    wa_fieldcat-do_sum    =  c_x.
      APPEND wa_fieldcat TO i_fieldcat.
      CLEAR wa_fieldcat.
    Fieldcat for Ammount in foreign currency
      wa_fieldcat-col_pos   =  10.
      wa_fieldcat-tabname   = l_c_i_final.
      wa_fieldcat-fieldname = l_c_wrbtr.
      wa_fieldcat-seltext_m = text-016.
      APPEND wa_fieldcat TO i_fieldcat.
      CLEAR wa_fieldcat.
    Fieldcat for Purchse order number
      wa_fieldcat-col_pos   =  11.
      wa_fieldcat-tabname   = l_c_i_final.
      wa_fieldcat-fieldname = l_c_ebeln.
      wa_fieldcat-seltext_m = text-017.
      APPEND wa_fieldcat TO i_fieldcat.
      CLEAR wa_fieldcat.
    Fieldcat for Item No
      wa_fieldcat-col_pos   =  12.
      wa_fieldcat-tabname   = l_c_i_final.
      wa_fieldcat-fieldname = l_c_ebelp.
      wa_fieldcat-seltext_m = text-018.
      APPEND wa_fieldcat TO i_fieldcat.
      CLEAR wa_fieldcat.
    Fieldcat for Material number
      wa_fieldcat-col_pos   =  13.
      wa_fieldcat-tabname   = l_c_i_final.
      wa_fieldcat-fieldname = l_c_matnr.
      wa_fieldcat-seltext_m = text-019.
      APPEND wa_fieldcat TO i_fieldcat.
      CLEAR wa_fieldcat.
    Fieldcat for Qunatity
      wa_fieldcat-col_pos   =  14.
      wa_fieldcat-tabname   = l_c_i_final.
      wa_fieldcat-fieldname = l_c_menge.
      wa_fieldcat-seltext_m = text-020.
      APPEND wa_fieldcat TO i_fieldcat.
      CLEAR wa_fieldcat.
    Fieldcat for Unit of measure
      wa_fieldcat-col_pos   =  15.
      wa_fieldcat-tabname   = l_c_i_final.
      wa_fieldcat-fieldname = l_c_meins.
      wa_fieldcat-seltext_m = text-021.
      APPEND wa_fieldcat TO i_fieldcat.
      CLEAR wa_fieldcat.
    Fieldcat for Std material master
      wa_fieldcat-col_pos   =  16.
      wa_fieldcat-tabname   = l_c_i_final.
      wa_fieldcat-fieldname = l_c_stprs.
      wa_fieldcat-seltext_m = text-022.
      APPEND wa_fieldcat TO i_fieldcat.
      CLEAR wa_fieldcat.
    Fieldcat for Invoice value,
      wa_fieldcat-col_pos   =  17.
      wa_fieldcat-tabname   = l_c_i_final.
      wa_fieldcat-fieldname = 'V_IV'.
      wa_fieldcat-seltext_m = text-023.
      wa_fieldcat-ref_fieldname = 'DMBTR'.
      APPEND wa_fieldcat TO i_fieldcat.
      CLEAR wa_fieldcat.
    Fieldcat for Currency
      wa_fieldcat-col_pos   =  18.
      wa_fieldcat-tabname   = l_c_i_final.
      wa_fieldcat-fieldname = l_c_pswsl.
      wa_fieldcat-seltext_m = text-024.
      APPEND wa_fieldcat TO i_fieldcat.
      CLEAR wa_fieldcat.
    Fieldcat for Exchange rate calculated
      wa_fieldcat-col_pos   =  19.
      wa_fieldcat-tabname   = l_c_i_final.
      wa_fieldcat-fieldname = 'V_ERC'.
      wa_fieldcat-seltext_m = text-025.
      APPEND wa_fieldcat TO i_fieldcat.
      CLEAR wa_fieldcat.
    Fieldcat for Order price
      wa_fieldcat-col_pos   =  20.
      wa_fieldcat-tabname   = l_c_i_final.
      wa_fieldcat-fieldname = l_c_v_op.
      wa_fieldcat-seltext_m = text-026.
      APPEND wa_fieldcat TO i_fieldcat.
      CLEAR wa_fieldcat.
    Fieldcat for Unit order to stock
      wa_fieldcat-col_pos   =  21.
      wa_fieldcat-tabname   = l_c_i_final.
      wa_fieldcat-fieldname = l_c_v_uos.
      wa_fieldcat-seltext_m = text-027.
      wa_fieldcat-do_sum    = c_x.
      APPEND wa_fieldcat TO i_fieldcat.
      CLEAR wa_fieldcat.
    Fieldcat for Invoice to order
      wa_fieldcat-col_pos   =  22.
      wa_fieldcat-tabname   = l_c_i_final.
      wa_fieldcat-fieldname = l_c_v_io.
      wa_fieldcat-seltext_m = text-028.
      APPEND wa_fieldcat TO i_fieldcat.
      CLEAR wa_fieldcat.
    Fieldcat for Unit value
      wa_fieldcat-col_pos   =  23.
      wa_fieldcat-tabname   = l_c_i_final.
      wa_fieldcat-fieldname = l_c_v_uv.
      wa_fieldcat-seltext_m = text-029.
      APPEND wa_fieldcat TO i_fieldcat.
      CLEAR wa_fieldcat.
    Fieldcat for Total
      wa_fieldcat-col_pos   =  24.
      wa_fieldcat-tabname   = l_c_i_final.
      wa_fieldcat-fieldname = l_c_v_t.
      wa_fieldcat-seltext_m = text-030.
      APPEND wa_fieldcat TO i_fieldcat.
      CLEAR wa_fieldcat.
    Fieldcat for Difference
      wa_fieldcat-col_pos   =  25.
      wa_fieldcat-tabname   = l_c_i_final.
      wa_fieldcat-fieldname = l_c_v_d.
      wa_fieldcat-seltext_m = text-031.
      APPEND wa_fieldcat TO i_fieldcat.
      CLEAR wa_fieldcat.
    Fieldcat for Net Price in Purchasing Document
      wa_fieldcat-col_pos   =  26.
      wa_fieldcat-tabname   = l_c_i_final.
      wa_fieldcat-fieldname = l_c_netpr.
      wa_fieldcat-seltext_m = text-032.
      APPEND wa_fieldcat TO i_fieldcat.
      CLEAR wa_fieldcat.
    Fieldcat for Total
      wa_fieldcat-col_pos   =  27.
      wa_fieldcat-tabname   = l_c_i_final.
      wa_fieldcat-fieldname = l_c_v_total.
      wa_fieldcat-seltext_m = text-033.
      APPEND wa_fieldcat TO i_fieldcat.
      CLEAR wa_fieldcat.
    Fieldcat for Order to stock
      wa_fieldcat-col_pos   =  28.
      wa_fieldcat-tabname   = l_c_i_final.
      wa_fieldcat-fieldname = l_c_v_os.
      wa_fieldcat-seltext_m = text-034.
      APPEND wa_fieldcat TO i_fieldcat.
      CLEAR wa_fieldcat.
    Fieldcat for Invoice to order
      wa_fieldcat-col_pos   =  29.
      wa_fieldcat-tabname   = l_c_i_final.
      wa_fieldcat-fieldname = l_c_v_ito.
      wa_fieldcat-seltext_m = text-035.
      APPEND wa_fieldcat TO i_fieldcat.
      CLEAR wa_fieldcat.
    fieldcat for invoice to order
      wa_fieldcat-col_pos   =  30.
      wa_fieldcat-tabname   = l_c_i_final.
      wa_fieldcat-fieldname = l_c_saknr.
      wa_fieldcat-seltext_m = text-035.
      APPEND wa_fieldcat TO i_fieldcat.
      CLEAR wa_fieldcat.
    ENDFORM.                    "build_fieldcat

    Hi romanch,
    defining the field catalog you must reference all currency fields to the respective currency key field (type CUKY).
    <alv_fieldcat>-cfieldname         = 'HWAER'.
    This is sample for alv output of a currency field. The alv structure has a field HWAER which carries the currency key, e.g. USD or so.
    Obviously you do not provide a cutrrency key for your values. If they are initial (zero), ALV will not display them as 0,00 but leave the field empty if the reference too currency key is not established.
    If you define a DDIC structure for the ALV output this refernce is enforced. You can pass the DDIC structure name to the ALV and don not have to create the field catalog manually.
    Regards,
    Clemens

  • What are the Corresponding fields in CRM for sales order in ECC

    HI! Experts,
    While creating a standard sales order in CRM I want to poulate these fields in ECC Sales order, these fields are
    VBKD-BSARK - Purchase order type
    VBAK-BNAME - Name: user ordered
    VBKD-IHREZ - Web Confirmation Number
    VBAK-TELF1 - Telephone number
    Or the other way round I want to know what are the corresponding fields in CRM for these fields so that when I pass the data in crmd_order in those fields it gets populated in the above mentioned fields.
    Thanks and Regards
    Mayank

    Mayank,
    May I suggest you to create an Order in R/3 with these fields and check that back in CRM. This is not as easy as it may sound. It is possible that some of these fields are "determined" by the system - for example the "Sold-To"'s first telephone number maintained in VBAK-TELF1. So, though it becomes a part of the Order header in R/3, CRM, generally doesn't duplicate them in the transaction but allows to refer back to the master data from the transaction!
    Check the following fields in CRM and see if you find the data you require.
    VBKD-BSARK - Purchase order type There is a field in CRM that "holds" this value. ACTIVITY CATEGORY. This can be found in the ACTIVITY_H set of the transaction. Filed name CATEGORY. Problem with this is, - "Category Type" of a CRM Activity to be mapped to PO type? Didn't workout good for us since the master data for both vary widely. So, we used custom Header Extension data for this (EEWB). So, you have to work
    VBAK-BNAME - Name: user ordered Is usually CREATED_BY in the CRM Order Header (CRMD_ORDERADM_H). But this fills up the VBAK_ERNAM bit not the BNAME.See the next item, that may give a clue if this is related to the next item.
    VBAK-TELF1 - Telephone number is usually "determined". Usually the Sold-To's first telephone number maintained in the Business Partner "Communication" section for that Sold-To.
    VBKD-IHREZ - Web Confirmation Number Actually it is Customer's or vendor's internal reference as per standard use. Looks like your customer is using it for custom purposes. Well, if you maintain the relationship  "Is Correwspondence Recipient for" with the Sold-To partner in CRM, and maintain the details of this Person, then this will be transferred to R/3.
    Hint: Once you have the R/3 order in CRM, try using the Report program (SE38)  CRM_ORDER_READ in CRM. This is a good tool to "dissect and see" and order in CRM. The program needs only the Transaction Number as the input.
    Easwar Ram
    http://www.parxlns.com

  • Restrict Production Order type to Production order transaction

    We have multiple Production order types. We would like to associate order type to order create transaction codes. For example Order type PP01,PP02 to transaction CO01 and order type say XYZ to transaction CO07.
    The reason for doing this is to lock down users from creating material Production orders using CO07 and non-material orders using CO01.
    Any feedback will be appreciated

    Hi Ramesh,
    from your number of posts, I gather you're rather new to SDN.
    The reason why someone asked if this is a suggestion or a comment is that this part of the forum is intended for suggestions and comments only.
    I suggest you click this link: <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/forums">https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/forums</a>
    And search for a forum which suits you.
    Kind regards, Rob Dielemans
    Message was edited by:
            Rob Dielemans
    null

  • Cost center field in sales order type

    Hi
    we have few sales orders type. INsome the order types, cost center field is available for input and in some it is not. Now how to make that field available in the sales order type ?
    Pls help
    Pushkaraj

    Hi Pushkaraj
    See the below link which I feel would be useful to your requirement.
    http://help.sap.com/saphelp_47x200/helpdata/en/eb/13796243c411d1896f0000e8322d00/frameset.htm
    Thanks
    G. Lakshmipathi

  • Number Range for Maintenance Order Type

    Dear All,
    Please help me in regarding for Number range  Change in Maintenance Order Type.
    I have different types of maintenance order...such as PM01,PM02, PM03, PM04, PM05, PM06, PM07, PM08.
    and i have to assign number range different for all the maintenance order type. kindly help how can i assign the same separately.
    also in case of Notification types also.
    Early response is highly appreciated.
    Thanks
    Sushant

    Greetings Sushant,
    Firstly, maintain all the Order Types you want in SPRO.
    To maintain the number ranges, you will need to go to t-code OION. Then select "Maintain Groups (F6)" and create a group with a number range for each of the Order Types that you require.  Each will be a separate interval. Then place the cursor on the unassigned Order Type and select "Assign Element Group (F7)" Repeat for each Order Type.
    Notification number ranges are maintained in t-code IW20

  • Choosing fields as per order type

    hi friends...we have an requirement of making the fields mandatory according to the PM rder type.
    for e.g : we want to make the " equipment " field mandatory for all types of PM orders except "general order".
    actually as the tcode for creating the all types of PM order is IW31 , can we make the "equipment" field mandatory for all PM order type except when user create a general order for the equipment.

    Hi Achal,
    go to
    SPRO >>> Plant Maintenance and Customer Service>>>Maintenance and Service Processing>>>Maintenance and Service Orders>>>>Define Field Selection for Order Header Data (PM) >>>> (select) Field Selection for Order Header Data and Reference Object >>>> (select) Equipment Field >>> Double click on it >>>> (you wil find influencing field) order type (click on it)>>>>> (at top) New Value>>> Add you order type and required against them.
    Your problem will be solved.

  • Internal Orders & Order Types

    Hi..
    I have an issue on internal orders and I need u r help.
    My client has a GL A/C for which they want to create a separate order type and they want to create a set of Internal Oders assigning that Order Type.
    Now whenever they want to use that particular GL Acc they want that Order Type to be defaulted and when u click F4 all the Internal Orders created in that particulat type Order Type have to be displayed.
    How to do it.

    Hi,
    Create an order type and assign a number range to that.
    Now that order type cannot be defaulted while using that GL as there is no field for order type. However you can write a validation OB28, so that is will not allow any other order number for that GL.
    SJ

  • New internal order type--need help

    Dear all:
    i have a case need help.
    now i want to create a new internal order type ,and assign a new number range and a default settlement rule to it .
    the settlement rule is that the actual costs of this  internal order type need to be
    sent to a cost element .
    what should i do step by step?
    thanks!
    best regards!

    Hi,
    2. Order Master Data
    2.1 Define Order types (KOT2_OPA)
    IMG &#61664;Controlling &#61664; Internal Orders &#61664;Order Master Data &#61664; Define Order Types
    An Internal order is created under an Order type. An order type is used for storing various control parameters and various defaults while creating an internal order. It is used for classifying various types of internal orders according to usage for e.g. Real orders for trade fairs, real orders for Capital investment measure, Statistical orders for motor vehicle expenses.
    The order type is client-specific, which means that every order type can be used in all controlling areas. A number range is assigned to the internal order type.
    Click on “New Entries”
    Take a drop in the field Order category and select 01
    Enter
    Update the following
    Give Order Type :- Z810
    Description :- Traders First Real order type
    Object Class :- OCOST overhead
    Reference Order :- Collective order without automatic goods movement
    Residence time 1 :- 12 months
    Residence time 2 :- 1 month
    Check “Commit Management and Check Integrated Planning
    Activate CO Partner Updating -You activate this so that allocations between orders and other CO objects (cost centers, projects, etc.), the partner information is retained and whether for each order a totals record should be written.
    Save
    Click on “Field Selection”
    Here you can hide the various fields or make it as required entry or only display or available for input. Thus while creating internal order only those fields are displayed and available for input.
    Click Save
    2.2 Maintain Number Ranges for Orders (KONK)
    IMG &#61664;Controlling &#61664; Internal Orders &#61664; Order Master Data &#61664;Maintain Number Ranges for Orders
    Number Range needs to be assigned to the internal order type. Number range can be internal or external. In Internal numbering system automatically assigns a number from the given number range. In external numbering the user has to manually assign the number from the given number range.
    We will configure internal number range for our internal order type – Trade Fair
    Click on Group &#61664;Maintain (From the menu bar)
    Click on Group &#61664; Insert (From the menu bar)
    Update the following
    From Number: - 910000000000
    To Number: - 919999999999
    Click in “plus icon” at the left bottom of the screen
    Click Save
    You will find internal order type Z810 in not assigned
    You need to assign the order type to the group we created above. Proceed as follows:-
    Position the cursor on: - Z810 Trade Fair real order type 
    Click on “Arrow”   Z810 Trade Fair real order type note it turns blue                                              
    Select Check mark Z810 A ltd India fair real order
    Click “Element Group”
    The internal order type Z910 moves under the group which can be seen as follows:-
    Z810: A Ltd India Trade fair real order / Z810 Trader Fair real order type.
    Click Save
    Select: - Z810: A Ltd India Trade fair real order / Z810 Trader Fair real order type.
    Click on “Pencil” icon.
    Click Back arrow.
    2.3 Define Model Orders
    IMG &#61664;Controlling &#61664;Internal Orders &#61664;Order Master Data &#61664;Screen Layout
    &#61664;Define Model Orders
    Model orders are not orders in the commercial sense, but serve merely as references for creating "normal" orders. Model orders contain default values for the orders in an order type. The Model order is assigned as the reference order in the order type.
    When you create a new order, all the fields active in the relevant order type are copied from the model order to the new order.
    Example
    You want to settle all your marketing orders to the same sales cost center. Stipulate the cost center as the default value in the model order for marketing orders.
    When you create a new marketing order, the system defaults this cost center. If you want to settle the order to a different cost center, you can overwrite the default cost center in the orders.
    We will create a model order with some defaults and assign it to the Trade fair internal order type
    Click “Create CO Model Order”
    Press F4 and select ($$) 03 model order
    Click on the master data and update the following
    Order: - $$$ Z81000001
    Description text: - A Limited Trade affair
    Click Save
    Assign this model order to the order type Z810
    Update the reference order with the model order number $$$Z81000001 in the reference order field
    Click on save.
    3 Planning
    3.1 Maintain User-Defined Planner Profiles
    IMG&#61664;Controlling&#61664;Internal Orders&#61664;Planning&#61664;Manual Planning&#61664;Maintain User-Defined Planner Profiles
    Check the User defined planner profile ZOCM91 created by us contains the layouts for internal orders.
    Double click on General controlling
    Planning area: Cost element/activity inputs.
    Cost Center: Activities/Prices
    CCtr Statistical key figures
    Orders: Cost Element/Activity inputs
    Ord: Statistical key figures
    Select :- Orders: Cost element/activity inputs
    Double Click on Layouts for control
    3.2 Maintain Planner Profile for Overall Planning (OKOS)
    IMG &#61664; Controlling&#61664;Internal Orders&#61664;Planning&#61664;Manual Planning&#61664;Maintain Planner Profile for Overall Planning
    Here you can specify the time frame for which values are to be planned for Internal order. Further you can also default the number of decimal places and the display factor. Default cost element group while planning.
    Double click on “Define planning profile for overall planning”
    Click on “New Entries”
    Select “05 Planned Total”
    Profile: 810000 General Plan Profile – A Ltd
    Click Save
    Select back arrow
    Double click maintain planning profile for order type
    Give: - Z810 Trader Fairs Real order type
    Give Plan profile: - 910000
    Click Save
    4 Settlement
    4.1 Maintain Allocation structure
    IMG&#61664; Controlling&#61664;Internal Orders&#61664;Actual Postings&#61664;Settlement&#61664; Maintain Allocation Structures
    An Allocation structure comprises one or several settlement assignments. An assignment shows which costs (origin: cost element groups) are to be settled to which receiver type (e.g. cost center, order and so on)
    You have 2 options:- You can settle to a settlement cost element or settle by cost element i.e. settle using the original cost element.
    We will use settle by cost element.
    Click on “New Entries”
    Allocation stru :- Z8
    A Ltd : Internal order settlement structure
    Click Save
    Select Z8 Internal order settlement structure
    Double click on Assignments
    Click on “New Entries”
    Assignment :- 10 Settlement Primary cost Element
    Click Save
    Select 10 Settlement Primary cost Element
    Double Click on Source
    Give From Cost Element To Cost Element
    Save
    Click back arrow
    Note:-The color has become green
    Select: Settlement primary cost element
    Double click on Settlement cost
    Click “New Entries”
    Select CTR Cost Center
    By Cost Element  Check
    Save
    4.2 Maintain Settlement Profile
    IMG &#61664;&#61472;Controlling &#61664;Internal Orders &#61664;Actual Postings &#61664;Settlement&#61664;Maintain Settlement Profile
    Here we define a range of control parameters for settlement.
    Double Click on “Maintain Settlement Profiles”
    Click on “New Entries”
    Select “Settlement not allowed”
    Assign the allocation structure Z9 created earlier in the settlement profile.
    Click on “Save”.
    Select Back Arrow
    Double Click on “Enter Settlement Profile in order types”
    Give Settlement Profile “ Z9100”
    Click on “Save”.
    4.3 Maintain Number Ranges for Settlement Documents
    IMG &#61664;Controlling &#61664;Internal Orders &#61664;Actual Postings &#61664;Settlement&#61664;Maintain Number Ranges for Settlement Documents
    You should define separate number range intervals for settlement documents for each controlling area.
    Click Group &#61664; Maintain
    Click Group&#61664; Insert
    Update the following:-
    Give “From Number” 1000000000- To Number 1999999999
    Click on “+” at the bottom left side.
    Click 8100
    Click on “Arrow” icon.
    Select Settlement documents for “A limited” Check box
    Click “Element group button”
    Click “SAVE”
    Assign Points
    Zia

  • Issue in passing process order related to order type ZGP9.

    Hi Experts,
    There has been a development done in CIF user exit to block process orders having order type ZGPD & ZGP7. But we are also facing issue for process order flow for order type ZGP9. 
    1. To avoid double counting of Depack orders (order type ZGPD) in actual production key figure of SCIPIO, stop sending actual production for order types ZGPD from P1 to SCIPIO.      
    2. To block Rework (ZGP7) and De-pack (ZGPD) Process order in CIF from SCIPIO end, Add one extra field in Custom Structure CI_ORDCUS which transfers Process Orders to APO. This field will capture "Order Type" for Process Orders and send it to APO.
    could any body suggest me why the issue is coming for process order ZGP9.

    Hi Venkat,
    1) Check whether the user exit is implemented properly
    2) Check whether the process order showing ZFGP9 is
    created recently?
    3) Archive that process order and try creating a manual
    process order and check.   If still error persists, use an
    abapper to check which table is calling that order type
    and accordingly you can proceed.
    Regards
    R. Senthil Mareeswaran.

  • DataSource 2LIS_17_I3HDR not loading all order types in setup tables

    I am trying to setup data source 2LIS_17_I3HDR.  I have initialized the setup tables and I am only getting 609 records in RSA3.  The problem is that all the records are from only two order types.  I have run the setup table initialization wide open so i'm not sure why the setup table only contains a subset of our orders.
    Obviously we have numerous other order types that I am expecting to be loaded into the setup tables (AFIH has around 180k entries).  Where can I configure which orders get loaded into the setup tables?
    Thanks,
    Chris

    That is an interesting thread.  I have a few questions though:
    -How can I determine which order types are maintenance orders?  When I look at transaction OIOA for Order Type Configuration I see that order category for numerous order types including the order types currently being loaded as having an order category of "30 Maintenance order" so I am unclear which field I need to be looking at for orders because in OIOA I see at least 8 other order types that look identical to the two order types being loaded.  When I look in IW39 I am seeing orders under order types are being loaded and under order types that aren't being loaded
    -In the linked thread it appears that the person with the issue was trying to pull detail data without header data.  I believe I am doing the opposite with these orders.  I am pulling the header data first.  Currently when I run 2LIS_17_OPER (I think this is the order detail DS) in RS3 I get no data.  Am I misunderstanding how the PM Order data sources work?
    Thanks,
    Chris

  • New order type.

    Dear all,
    We have created a new order type. When we use the new order type, for the sale order item, in the condition tab, for the respective condition type, no gl account is showing against the account key. We are able to see the account key. If we use another order type, we are able to see the gl account tab in the condition tab.
    What would be the issue? Please suggest.
    Regards,
    AR

    As and when u create the new order type(copying frm the existing (OR)).When u try to save the new order type.System will prompt for the (Whether copy controls fields from (OR) to new order type should be done or not.
      If u say yes system will copy all the control to the new order type from the old one.
    If u say no system will not copy.
      In your situation also u have not specified yes while copying controls.And the g/l accounts are not copied from (OR) to new order document type.
      Try to do it again..
    Or else if u want to rectify it (Go to VTAA) t.code this is the copy control for (Sales document to sales document) and in that go to the new entries and specify your new document type and maintain all the copy controls.
      Then only u r issue will be resolved.
    If satisfied with my answer pls issue points to me....

  • How to display the change history of Z-fields in transaction BP?

    Hi,
    we have created an append structure to table ADRC. For all fields of the structure the flag "Change document" in the data element is set. This is still working because the changes are in the table CDPOS.
    But when I choose "Extras => Change history => For this field" in transaction BP the changes will not be displayed.
    Any hints?
    Thanks in advance
    F.T.

    Hi Jaya,
    Just do as follows :-
    1) Find out in which table are those fields.
    2) Then if you find them go to the table, look for the field you want the log to be created for.
    3) Double click on its DATA element. On the DEFINITION tab of the data element, there is a checkbox named as CHANG  
        DOCUMENT. Just TICK it.
    4) So every time there a change on this field from the transaction, you can look for the log in table CDHDR.
    Regards
    Abhii...

Maybe you are looking for

  • When using hdmi to tv, sound is not transmitted. Pls help

    When I use the hdmi port to hook to tv no sound is transmitted.  It was working a few days ago now its not.  I tried to reinstall drivers as well as changing tv's and 2 different new hdmi cables.  Anyone have any clues?  C855D-S5320

  • How to Redeploy application in OC4J using war file

    Hi Am new in area of 9ias and OC4J. I have deployed and application in OC4J of 9ias 902. using enterprise manager web interface. now i have change the contents of current jsp and added more jsp files. do i have to recreate war file and redeploy it in

  • Problem with interactive booklet

    i just bought B'Day, by Beyonce, whihc comes with an interactive booklet. i double click on it and nothing happens.... i tried to open it in Quicktime and RealPlayer but it wouldn't work how does a digital booklet work? does anyone know why this is h

  • Making Pages the Default

    Is it possible to have Pages '09 serve as the default application to open documents? Whenever I receive a word document from someone and try to open it, it opens it in TextEdit. I would prefer that it opened it in Pages so that I could avoid the step

  • Time Capsule and Tiger with wired G5 and wireless PowerBook

    Do I want to create a new wireless network with TC as new base station or just add it to my existing network? Are there performance differences? I currently have the phone line connected to my wireless modem (2Wire812), then the modem connected to th