Allow mov type 261 and 262 for a material type only

Requirement is to allow movt type 261 and 262 for a particular material type.( Assume Only 261 - 262 issue transactions happen against that material type.)
User to be restricted, while material issue (migo), for the material type XXXX to 261 - 262 movt type only.
No any other movt type allowed for this material type while issuing material.
All suggestions welcomed.
Regards,
Rakesh

Thanx amit.
But same user uses all other movt types for other material type also.

Similar Messages

  • How to block movement type 261 and 262 from several storage locations

    Dear Expert,
    Can we block the  261 and 262 movement type from several storage locations? These storage locations are not affected by the MRP run, where for the materials that have been moved to these storage locations their existance are not count. These storage locations could not be used for confirmation production order, therefore i want to block  261 and 262 movement type from these storage locations.
    Thanks
    Pauline

    Dear Pauline,
    if my understanding is correct abt ur query,
    1) you want in confirmation screen, Consumption should happen only from one storage location
    2) Rest all storage locations should not be allowed
    3) Maintain Storage location in BOM component view, in mass you can maintain in CEWB
    4) Now GO with SHD0, Make storage location field as Out put only, for CO11N Transaction
    Plz refer this link for SHD0 Demo
    [https://www.sdn.sap.com/irj/scn/wiki?path=/display/snippets/transactionVariant-AStepbyStepGuidefor+Creation]
    Regards
    Madhu Kumar

  • Material Type Configuration and Creating Z configured Material Types

    All-
    Every solution architect I have contacted has told us that itu2019s standard practice to create copies of standard SAP material types (and all other configuration) and then update configuration to make the object client specific rather than just modifying SAP standard.  You do that because when SAP delivers upgrades they may update standard configuration keys and that can cause disruptions.  We talked to some folks at SAP who told us the same thing.
    My Client had previously agreed to this but now some of their IT resources have pushed back with their primary argument being u201Cthis hasnu2019t affected us for the last 15 years so we want to continue with what we haveu201D i.e. modifying configuration and customizing the SAP delivered material types.  Theyu2019ve also found some SAP documentation that says itu2019s fine to do it either way.  I donu2019t have the depth of technical knowledge to get into all of the arguments for / against this.
    Request u2013 Can anyone point us to a position paper or document that states why we suggest this (reasons, pros, consu2026) or someone that could provide us with the expertise to clearly state why and what the consequences are if they donu2019t?  Or if this is really just something that is suggest based upon the potential for problems and they can do whatever they want?
    Any information would be greatly appreciated

    You obviously can modify a lot of standard objects because the config. option is there.
    The main reason not to is because they act as models e.g. what is the SAP standard model for configuration of a Traded material (in the given Solution, Country etc.).  If you have copied the std and modified the Z version you can always refer back to the std if you run in to unexpected difficulties. If you've modified the std, you have no model to refer to.  If you modify the std and it then doesn't do what you want or you hit an issue of some form, you pretty much have to figure out why yourself because SAP would probably charge you.
    Material Types in particular involve a huge potential number of fields (900+) and complex field selection.
    If you do modify a standard, at least document exactly what changes were made so you and subsequent support personnel can understand how the object has been modified. 'Small' modifications of objects you may well have no future issue with, 'big' modifications of big objects could well come back to haunt you.
    Regards,
    Nick

  • Movement 261 and 262

    Hi All,
    I am having a problem regarding movement type 261 and 262.
    When I am doing 261, in production order withdrawn quantity is getting updated and acording to that the Cost of that component also gets updated. And storage location Stock getting decreased respectively.
    But when I am doing 262, nothing is updated(withdrawn quntity in production order - component overview  & Cost of that component). But respective Stock is getting increased in storage location.
    What is the problem. OR what procedure should I follow to overcome from this problem.

    Again i m clearifying my problem with example...
    Suppose, i m doing GI (movement type 261) using MIGO or CO27 for one component in production ordr.
    Then it is appearing as a "Quantity withdrawn"  in "Component overview" in production order. say 10 pc.
    Then stock of perticular storage location will be decrease by 10 pc.
    But when I am doing reverse GI (mvnt 262) using MB1A then "Quantity withdrawn" field should become blank, i mean zero. but that is not happening. But stock of perticular sorage location is Increased by 10 pc in right way.
    So, I can say it is right according to Stock increase and decrease. But, by seeing component overview i can't say the situation of GI.
    Is there any setting in SPRO?
    plz give guidence.
    Points will be rewarded.

  • How to stop 261 and 262 MVT types after GR for production Order.

    hi,
    After GR [MB31] against the Production order,  261 and 262 movments should not be happen, but in  present proces its taking place,
    Client dont want to happen it,
    Can any body tell me how to controll this.
    Veera.

    Hi  Veerakumar ,
    You can TECO the production order if reqd since delivery complete status of the order.
    or you can go to system status and do as explained .
    Regards,
    Vimal

  • I have been a customer of ITunes and Apple since 2007. Movies, Apps, Music and books  Itunes has been my only source for my media needs.

    I have been a customer of ITunes and Apple since 2007. Movies, Apps, Music and books  Itunes has been my only source for my media needs. 397 Apps 759 Songs over 100 Videos 13 books 3 IPhones 2 IPods So here is my problem with ITunes I purchased an App and it is identical to one I have already brought. The App description did not say anything that it would not do what I was trying to do. I wrote sup[port and asked if they could issue a credit. Mari at support wrote back and said he checked with his supervisor and they could not issue a credit.  I told them what a good loyal customer I have been to Itunes and Apple and they still refused.  Granted the App did not cost a lot of money (3.99) but it’s the principle. With customers having options to shop anywhere I would think a business would do whatever it takes to retain the loyal customers they do have Occasionally I rush to buy an App without fully understanding if it meets my needs. According to ITunes support that has occurred nine times. Here is the last reply that I received Roger, I know how frustrating it can be when things don't work the way they should be  and I do apologize for the inconvenience that this may have caused you. I am sorry but we could not be able to grant your request as we have made 9 exceptions on you. For more information on Apple's requirements for using the iTunes Store, please refer to the iTunes Store Terms and Conditions:http://www.apple.com/legal/itunes/us/terms.html Again, I am hoping for your kind understanding regarding this matter. Sincerely Mari iTunes Store/Mac App Store Advisor

    "The App description did not say anything that it would not do what I was trying to do."
    You've already had 9 refunds? You understand that apps are sold on a non-return policy, presumably. You bought an app that didn't claim to do something that you wanted from it, and now that you've found that it doesn't, you want your money back.
    Perhaps you've failed to explain your point properly but I can't see why you expect any sympathy from users here, not that it would make any difference. Only the store staff can issue refunds if they think appropriate. Chalk it up to experience. You could even contact the developer in advance of a purchase if you want to be certain an app does what you want. Then if it really fails to live up to the promise you would at least have a better argument for a refund.
    tt2

  • SCD type 2 and 3 for Relational Dimension?

    SCD type 2 and 3 for Relational Dimension?
    ==========================
    Thanks for your replies.
    I searched this forum and web on SCD 2 and 3 implementation using Relational Dimension (Table) using OWB.
    I find some thread talks about implementing Oracle Dimensional structures, which has levels/hierarchy etc.
    If we design our dimension in pure relational fashion, how do we go about using OWB for SCD 2 and 3?
    Are there any new SQL features of 11g to help us here?
    Thanks in helping.
    RI

    Hi,
    several years ago Oracle published whitepaper which described steps for designing OWB mappings for loading SCD (types 1,2,3) tables.
    But recently (after website reorganization) this whitepaper was removed, although you can stil find it by googling with "scdwhitepaper",
    or you can directly download it from http://sourceforge.net/projects/owbland/files/Stuffs_from_Oracle_site/SCDWhitePaper.zip/download
    Also it is available for download OWB experts which implement generation of SCD2 mappings according this whitepaper:
    http://odi-ee.blogspot.com/2009/02/scd-type2-expert-table-operator.html
    http://owbexpert.blogspot.com/2008/12/hallo-hallo.html
    Also look at this thread {message:id=4336731} with discussion of bug which force to update all rows in target table, even they not changed between mapping executions.
    Regards,
    Oleg

  • Restrict display and posting for specific document types

    Hi,
    Is it possible to restrict display and posting for specific document types? I want to restrict authorization to SM document type in FS10N, and KSB1 tcode. Please help
    Best Regards,
    KIRAN.

    Sandipan Choudhury wrote:
    FS10N checks for this object ("Check" in Su24) but when user doesnot has this authorization object he gets access to all doc types and when the user is restricted to specific doc types (object present in user's authorization) he will get access to only those doc types. This is how the authorization check for F_BKPF_BLA works, in other words this authorization is Optional.
    Sorry, but this is not true and seems to be an invention of how you would like it to work...
    The coding works like this (generally):
        if sy-subrc ne 0.
          select single * from  t003 where blart = postab-blart.
          check sy-subrc = 0.
          blrtab-blart = t003-blart.
          blrtab-brgru = t003-brgru.
          append blrtab.
        endif.
        if blrtab-brgru ne space.    "<--- important condition!!
          authority-check object 'F_BKPF_BLA'
               id 'BRGRU' field blrtab-brgru
               id 'ACTVT' field actvt.
          if sy-subrc ne 0.
            rcode = 4.
          endif.
        endif.
      endif. 
    The "optional" aspect is whether or not the document type has an auth group on it in T003, failing which the check is suppressed.
    If it reaches the check, then it found something and then checks that selected value.
    Moral of the story:
    --> Do not believe SU53.
    --> Do not make assumptions from ST01 traces.
    --> Read the documentation carefully.
    --> Read the code to see how it really works (you can jump to the coding location from the trace).
    Cheers,
    Julius

  • Hide views in MM01 for all material type in one time

    Hi,
    I have a requirement to hide the views for all material type at at time.
    i tried with OMS2 , it is allowing me to do for one matrial type.
    could any one tell me how to hide the views for all material type in one short.
    Thanks in adv..

    Hi Rakesh,
    Up to my knowledge it is not possible to do view setting for all material type in one shot simply because it is material type dependent.
    If trying to change fields in material master then use OMS9. This also material type linked to field reference group. And we can change the setting of field selection group in one shot. This will affect the material types linked to it.
    Hope it helps
    sBk

  • Valuation type need to maintain for Subcontracting material FG

    Hi,
    i have a scenario like plant A is subcontracting SFG  to Plant B and receiving FG to Plant A from Plant B.
    i have maintain this as V valuation type.
    when i am doing billing in Plant A for this product i am getting error like no cost estimate found for product.
    As it is "V"  and it has BOM and it has price in it.
    And i have maintain in KEPC setting aganist this material type against this plant.
    if i remove this setting  probelm can be solved
    but this plant has got some other FG products  which are produced in house so we do costing run for it.
    is there any solution for this material type that can allow billing with  "V" price also with out making changes in KEPC.
    thanks
    kareem

    HI Ajay anna,
    thanks for ur reply
    do i need to assign same costing key for the product in KE4H .
    or do i need to create new costing for it.
    please can you tell me what i need to select if i need to create new costing key for those they dont have cost estimate.
    Like Period indicator,
    costing date.
    waiting for ur reply anna.
    thanks
    kareem

  • Uploading data in MM01 for different material types

    Hi,
    I have a doubt regarding uploading the data in MM01 for different material types.
    Generally in MM01, we have different views for different material types. The number of views will vary depending upon the material type that we select.
    I have a scenario, where in to upload the data, I have a flat file that consists of data for different message types. So, how to upload the data in such case.
    Can anyone help me on the same by providing explanation or sample code...? What would be the possible ways to upload data in such scenario.
    That would be of great help.
    Thanks & Regards,
    Pradeep.

    See the below code and use FM SELECTION_VIEWS_FIND..
    REPORT zjpmuim306 NO STANDARD PAGE HEADING LINE-SIZE 250 MESSAGE-ID
    zjpm001.
    *&   I N B O U N D  V I A   A B A P : Batch input Session method     *
    *&   Development ID: IM_DD_306_LJP                                   *
    *&   Report        : ZJPMUIM306                                      *
    *&   The Purpose of the Object is to interface Create Input Record   *
    *&   for SAP Migration from the Material master of BPCS All the      *
    *&   information received at BPCS is collected into a single record. *
    *&   By using session method upload data from file ,one item is
    *&   created for one record                                          *
    *&   Change Log:                                                     *
    *&   Init       Who              Date         Text                   *
    *&  MALIKDH1   Seshu Reddy    26-07-2003   Initial Version           *
                             Constants                                   *
    CONSTANTS:c_vkorg(4) type c value 'JP20',        " Sales Organization
              c_vtweg(2) type c value 'TR' ,         " Distribution Channel
              c_werks(4) Type c value 'JP01' ,       " Plant
              c_viewlist(15) VALUE 'KDEALBSZXVPCFQG'," View list
              c_scm_view TYPE msichtausw-dytxt VALUE 'SCM View',
              c_sd_view TYPE msichtausw-dytxt VALUE 'SD View',
              c_seq_code(2) VALUE 'Z1',              " Sequential Code
              c_keep(1) TYPE c VALUE  'X',           " Keep
              c_group LIKE apqi-groupid VALUE 'IM306', " Session Name
              c_tcode  LIKE tstc-tcode VALUE 'MM02',  " Transaction Code
              c_blank(1) VALUE ' ',                   " Blank
              c_intls(1) VALUE 'N'.                  " Logistic Status
                  Variables                                      *
    DATA: g_flag1(1),  " Variable to hold
          g_flag(1),   " Variable to hold
          g_file LIKE rlgrap-filename VALUE
         'C:\Documents and Settings\seshur\Desktop\HCLT123.CSV'. " File name
           Internal tables/ Work area                           *
    Internal Table for Delimter
    DATA : BEGIN OF t_delim OCCURS 0,
           text(1000),
           END OF t_delim.
    Internal table for BDC processing
    DATA : t_bdcdata LIKE bdcdata OCCURS 0 WITH HEADER LINE.
    Internal table for holding the data which has to be uploaded.
    DATA: BEGIN OF t_bpcs OCCURS 0,
          matnr(15) TYPE c,  " material no
          dosage(40) TYPE c, " Dosage form(Local)
          appearance(40) TYPE c, " Appearance
          idcode(6) TYPE c,     " Identification Code
          prostformno(10) TYPE c, "SOP
          weitab(7) TYPE c,    " Weight/tablet
          uom1(2) TYPE c,     " UOM of Carton
          uom2(2) TYPE c,     " UOM of Case
          carsize(14) TYPE c, " Carton size
          cassize(14) TYPE c, " Case size
          rupqty(11) TYPE c,  " Round up
          abvname(3) TYPE c,  " Product short name
          END OF t_bpcs.
    *Internal table for t_bpcs
    DATA: BEGIN OF t_mdata OCCURS 0,
          matnr  LIKE marc-matnr, " Material number
          zzjp_dos_frm LIKE marc-zzjp_dos_frm, " Dosage form(Local)
          zzjp_aprn LIKE marc-zzjp_aprn, " Appearance
          zzjp_con_id LIKE marc-zzjp_con_id," Identification Code
          zzjp_nyu_sop LIKE marc-zzjp_nyu_sop,"SOP
          zzjp_wei_tab(10) type c , " Weight/tablet
          zzjp_bio  LIKE marc-zzjp_bio,"Biologics Indicator
          zzjp_itf LIKE marc-zzjp_itf, " ITF code
          zzjp_car(2) type c, " UOM of Carton
          zzjp_cas(2) type c, " UOM of Case
          zzjp_car_size(11) type c," Carton size
          zzjp_cas_size(11) type c, " Case size
          zzjp_rupqty(11) type c,  " Round up
          zzjp_init_ls LIKE marc-zzjp_init_ls, " Logistic Status
          zzjp_re1 LIKE marc-zzjp_re1, "Document type(Local)
          zzjp_re2 LIKE marc-zzjp_re2, "Report type
          zzjp_re3 LIKE marc-zzjp_re3, "Shipping report type
          zzjp_pro_id LIKE mvke-zzjp_pro_id," Product output sequence
          zzjp_bu_id LIKE mvke-zzjp_bu_id, " Business unit indicator
          zzjp_abv_name LIKE mvke-zzjp_abv_name," Product short name
          zzjp_abv_id1 LIKE mvke-zzjp_abv_id1," Product short name output
          zzjp_abv_id2 LIKE mvke-zzjp_abv_id2," Product short name internal
          zzjp_spl_id LIKE mvke-zzjp_spl_id,  " Sample internal order
          END OF t_mdata.
    Internal table for Mara Table
    DATA: BEGIN OF t_mara OCCURS 0,
          matnr LIKE mara-matnr,  " material Number
          vpsta LIKE mara-vpsta,  " Maintenance status of complete material
          pstat like mara-pstat,  " Maintenance status
          END OF t_mara.
    Internal table for Material Master View Selection Screens
    DATA: BEGIN OF t_bildtab OCCURS 0.
            INCLUDE STRUCTURE mbildtab.
    DATA: END OF t_bildtab.
    internal table for T_bildtab
    DATA: t_bildtab_dup LIKE t_bildtab OCCURS 0 WITH HEADER LINE.
    *Work area for T_bildtab internal table(Views Selection)
    DATA: BEGIN OF w_data,
          flag1 type c,
          anzd70 TYPE i,
          field1(20) type c,
          field2(20) type c,
          field3(20) type c,
          field4(20) type c,
          count(2) TYPE c,
          END OF w_data.
                Main Processing                           *
    START-OF-SELECTION.
    Store data from file into internal table
      PERFORM f_uplaod_data.
    Transfer the uploaded data into t_mdata internal Table
      PERFORM f_process_data.
    Selecting The views based on Material number
      PERFORM f_view_list.
    Open a BDC Session
      PERFORM f_bdc_open.
    *Selecting the fields from mara table
      SELECT matnr
             vpsta
             pstat
        FROM mara
      INTO TABLE t_mara
      FOR ALL ENTRIES IN t_mdata
      WHERE matnr = t_mdata-matnr.
      SORT t_mara BY matnr.
      SORT t_mdata BY matnr.
    Transfer the uploaded data into BDCDATA structure
      PERFORM f_process_bdc.
    Close The BDC Session
      PERFORM f_close_group.
    *&      Form  F_VIEW_LIST                                             *
             Routine to used for Calling the function module            *
              Selection_views_find                                      *
    FORM f_view_list.
      CALL FUNCTION 'SELECTION_VIEWS_FIND'
           EXPORTING
                bildsequenz     = c_seq_code
                pflegestatus    = c_viewlist
           TABLES
                bildtab         = t_bildtab
           EXCEPTIONS
                call_wrong      = 1
                empty_selection = 2
                OTHERS          = 3.
      IF sy-subrc <> 0.
             MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
             WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    ENDFORM.                    " F_VIEW_LIST
    *&      Form  f612_view_sort                                          *
      Routine to used for Selecting The views based on Material Number  *
    FORM f612_view_sort.
      t_bildtab_dup[] = t_bildtab[].
    Reading the Internal table t_mara
      READ TABLE t_mara WITH KEY matnr = t_mdata-matnr.
      TRANSLATE t_mara-pstat USING ' $'.
      CLEAR: w_data-flag1, w_data-anzd70.
      LOOP AT t_bildtab_dup.
        IF t_bildtab_dup-pstat CA t_mara-pstat.
          w_data-anzd70 = w_data-anzd70 + 1.
          IF t_bildtab_dup-kzanz IS INITIAL.
            t_bildtab_dup-kzanz = 'X'.
            w_data-flag1 = 'X'.
            MODIFY t_bildtab_dup.
          ENDIF.
        ELSE.
          IF NOT t_bildtab_dup-kzanz IS INITIAL.
            CLEAR t_bildtab_dup-kzanz.
            w_data-flag1 = 'X'.
            MODIFY t_bildtab_dup.
          ENDIF.
        ENDIF.
      ENDLOOP.
      TRANSLATE t_mara-pstat USING '$ '.
      IF NOT w_data-flag1 IS INITIAL.
        SORT t_bildtab_dup BY kzanz DESCENDING idxbd ASCENDING.
      ENDIF.
    *Reading The internal table for T_bildtab_dup
      READ TABLE t_bildtab_dup WITH KEY dytxt = c_scm_view.
      IF t_bildtab_dup-kzanz = 'X'.
        WRITE sy-tabix TO w_data-count.
        w_data-count = w_data-count + 2.
        IF w_data-anzd70 > 18.
          w_data-count = w_data-count - 18.
        ENDIF.
        CONCATENATE 'MSICHTAUSW-DYTXT(' w_data-count ')' INTO w_data-field1.
        CONCATENATE 'MSICHTAUSW-KZSEL(' w_data-count ')' INTO w_data-field2.
      ENDIF.
      READ TABLE t_bildtab_dup WITH KEY dytxt = c_sd_view.
      IF t_bildtab_dup-kzanz = 'X'.
        WRITE sy-tabix TO w_data-count.
        IF w_data-anzd70 > 18.
              w_data-count = w_data-count + 2.
          w_data-count = w_data-count - 18.
        ENDIF.
        CONCATENATE 'MSICHTAUSW-DYTXT(' w_data-count ')' INTO w_data-field3.
        CONCATENATE 'MSICHTAUSW-KZSEL(' w_data-count ')' INTO w_data-field4.
      ENDIF.
    ENDFORM.                    " f612_view_sort
    *&      Form  f_uplaod_data                                           *
    Routine to used for Uploading the data from file to Internal table *
    FORM f_uplaod_data.
      CALL FUNCTION 'WS_UPLOAD'
           EXPORTING
                filename                = g_file
                filetype                = 'DAT'
           TABLES
                data_tab                = t_delim
           EXCEPTIONS
                conversion_error        = 1
                file_open_error         = 2
                file_read_error         = 3
                invalid_type            = 4
                no_batch                = 5
                unknown_error           = 6
                invalid_table_width     = 7
                gui_refuse_filetransfer = 8
                customer_error          = 9
                OTHERS                  = 10.
      IF sy-subrc <> 0.
             MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
             WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      IF t_bpcs IS INITIAL.
        LOOP AT t_delim.
          SPLIT t_delim-text AT ',' INTO t_bpcs-matnr
                                         t_bpcs-dosage
                                         t_bpcs-appearance
                                         t_bpcs-idcode
                                         t_bpcs-prostformno
                                         t_bpcs-weitab
                                         t_bpcs-uom1
                                         t_bpcs-uom2
                                         t_bpcs-carsize
                                         t_bpcs-cassize
                                         t_bpcs-rupqty
                                         t_bpcs-abvname.
          APPEND t_bpcs.
        ENDLOOP.
      ENDIF.
    ENDFORM.                    " f_uplaod_data
    *&      Form  F_BDC_OPEN
          Routine  to create BDC Session to be processed
    FORM f_bdc_open.
      CALL FUNCTION 'BDC_OPEN_GROUP'
           EXPORTING
                client              = sy-mandt
                group               = c_group
                keep                = c_keep
                user                = sy-uname
           EXCEPTIONS
                client_invalid      = 1
                destination_invalid = 2
                group_invalid       = 3
                group_is_locked     = 4
                holddate_invalid    = 5
                internal_error      = 6
                queue_error         = 7
                running             = 8
                system_lock_error   = 9
                user_invalid        = 10
                OTHERS              = 11.
      IF sy-subrc <> 0.
        MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
      ELSE.
      MESSAGE S000 WITH 'Batch input session is created successfully'(T02).
      ENDIF.
    ENDFORM.                    " F_BDC_OPEN
    *&      Form  F_PROCESS_BDC
          Processing of BDCDATA Structure
    FORM f_process_bdc.
      LOOP AT t_mdata.
        PERFORM f612_view_sort.
        PERFORM f_bdc_dynpro USING 'SAPLMGMM' '0060'.
        PERFORM f_bdc_field USING 'BDC_CURSOR'
                                      'RMMG1-MATNR'.
        PERFORM f_bdc_field USING 'BDC_OKCODE'
                                      '=AUSW'.
        PERFORM f_bdc_field USING 'RMMG1-MATNR'
                                      t_mdata-matnr.
        PERFORM f_bdc_dynpro USING 'SAPLMGMM' '0070'.
        PERFORM f_bdc_field USING 'BDC_CURSOR'
                                  'MSICHTAUSW-DYTXT(01)'.
        IF w_data-anzd70 > 18.
          PERFORM f_bdc_field       USING 'BDC_OKCODE'
                                      '=P+'.
          PERFORM f_bdc_dynpro      USING 'SAPLMGMM' '0070'.
          PERFORM f_bdc_field  USING 'BDC_OKCODE' '/00'.
        ENDIF.
    reading the t_bildtab internal table
        READ TABLE t_bildtab_dup WITH KEY dytxt = c_scm_view.
        IF t_bildtab_dup-kzanz = 'X'.
          PERFORM f_bdc_field       USING 'BDC_CURSOR'
                                        w_data-field1.
          PERFORM f_bdc_field       USING w_data-field2 'X'.
          g_flag = 'X'.
        ENDIF.
    reading the t_bildtab internal table
        READ TABLE t_bildtab_dup WITH KEY dytxt = c_sd_view.
        IF sy-subrc EQ 0.
          g_flag = 'X'.
        ENDIF.
        IF t_bildtab_dup-kzanz = 'X'.
          PERFORM f_bdc_field       USING 'BDC_CURSOR'
                                        w_data-field3.
          PERFORM f_bdc_field       USING w_data-field4 'X'.
          g_flag1 = 'X'.
        ENDIF.
        IF g_flag = 'X' AND g_flag1 = 'X'.
          PERFORM f_bdc_dynpro      USING 'SAPLMGMM' '0080'.
          PERFORM f_bdc_field       USING 'BDC_CURSOR'
                                        'RMMG1-VTWEG'.
          PERFORM f_bdc_field       USING 'BDC_OKCODE'
                                        '=ENTR'.
          PERFORM f_bdc_field       USING 'RMMG1-WERKS'
                                        c_werks.
          PERFORM f_bdc_field       USING 'RMMG1-VKORG'
                                        c_vkorg.
          PERFORM f_bdc_field       USING 'RMMG1-VTWEG'
                                        c_vtweg.
          CLEAR g_flag.
          CLEAR g_flag1.
        ELSE.
          IF g_flag = 'X'.
            PERFORM f_bdc_dynpro      USING 'SAPLMGMM' '0080'.
            PERFORM f_bdc_field       USING 'RMMG1-WERKS'
                                        c_werks.
            PERFORM f_bdc_field      USING 'BDC_OKCODE' '/00'.
          ELSE.
            IF g_flag1 = 'X'.
              PERFORM f_bdc_dynpro      USING 'SAPLMGMM' '0080'.
              PERFORM f_bdc_field       USING 'BDC_CURSOR'
                                            'RMMG1-VTWEG'.
              PERFORM f_bdc_field       USING 'RMMG1-WERKS'
                                          c_werks.
              PERFORM f_bdc_field       USING 'RMMG1-VKORG'
                                            c_vkorg.
              PERFORM f_bdc_field       USING 'RMMG1-VTWEG'
                                            c_vtweg.
              PERFORM f_bdc_field       USING 'BDC_OKCODE'
                                             '=ENTR'.
            ENDIF.
          ENDIF.
        ENDIF.
    *Processing of SCM View
        PERFORM f_bdc_dynpro      USING 'SAPLMGMM' '4000'.
        PERFORM f_bdc_field       USING 'BDC_CURSOR' 'MARC-ZZJP_DOS_FRM'.
        PERFORM f_bdc_field       USING 'MARC-ZZJP_DOS_FRM'
                                      t_mdata-zzjp_dos_frm.
        PERFORM f_bdc_field       USING 'MARC-ZZJP_APRN'
                                      t_mdata-zzjp_aprn.
        PERFORM f_bdc_field       USING 'MARC-ZZJP_CON_ID'
                                      t_mdata-zzjp_con_id.
        PERFORM f_bdc_field       USING 'MARC-ZZJP_NYU_SOP'
                                      t_mdata-zzjp_nyu_sop.
        PERFORM f_bdc_field       USING 'MARC-ZZJP_WEI_TAB'
                                      t_mdata-zzjp_wei_tab.
        PERFORM f_bdc_field       USING 'MARC-ZZJP_CAR'
                                      t_mdata-zzjp_car.
        PERFORM f_bdc_field       USING 'MARC-ZZJP_CAS'
                                      t_mdata-zzjp_cas.
        PERFORM f_bdc_field       USING 'MARC-ZZJP_CAR_SIZE'
                                      t_mdata-ZZJP_CAR_SIZE.
        PERFORM f_bdc_field       USING 'MARC-ZZJP_CAS_SIZE'
                                      t_mdata-ZZJP_CAS_SIZE.
        PERFORM f_bdc_field       USING 'MARC-ZZJP_RUPQTY'
                                       t_mdata-ZZJP_RUPQTY.
        PERFORM f_bdc_field       USING 'MARC-ZZJP_BIO'
                                      t_mdata-zzjp_bio.
        PERFORM f_bdc_field       USING 'MARC-ZZJP_ITF'
                                      t_mdata-zzjp_itf.
        PERFORM f_bdc_field       USING 'MARC-ZZJP_INIT_LS'
                                      t_mdata-zzjp_init_ls.
        PERFORM f_bdc_field       USING 'MARC-ZZJP_RE1'
                                      t_mdata-zzjp_re1.
        PERFORM f_bdc_field       USING 'MARC-ZZJP_RE2'
                                      t_mdata-zzjp_re2.
        PERFORM f_bdc_field       USING 'MARC-ZZJP_RE3'
                                      t_mdata-zzjp_re3.
        PERFORM f_bdc_field       USING 'BDC_OKCODE'
                                      '/00'.
    *Processing of SD View
        PERFORM f_bdc_dynpro      USING 'SAPLMGMM' '4000'.
        PERFORM f_bdc_field       USING 'BDC_CURSOR' 'MVKE-ZZJP_PRO_ID'.
        PERFORM f_bdc_field       USING 'MVKE-ZZJP_PRO_ID'
                                      t_mdata-zzjp_pro_id.
        PERFORM f_bdc_field       USING 'MVKE-ZZJP_BU_ID'
                                      t_mdata-zzjp_bu_id.
        PERFORM f_bdc_field       USING 'MVKE-ZZJP_ABV_NAME'
                                      t_mdata-zzjp_abv_name.
        PERFORM f_bdc_field       USING 'MVKE-ZZJP_ABV_ID1'
                                      t_mdata-zzjp_abv_id1.
        PERFORM f_bdc_field       USING 'MVKE-ZZJP_ABV_ID2'
                                      t_mdata-zzjp_abv_id2.
        PERFORM f_bdc_field       USING 'MVKE-ZZJP_SPL_ID'
                                      t_mdata-zzjp_spl_id.
        PERFORM f_bdc_field      USING 'BDC_OKCODE' '/00'.
        PERFORM f_bdc_dynpro      USING 'SAPLSPO1' '0300'.
        PERFORM f_bdc_field       USING 'BDC_OKCODE'
                                      '=YES'.
    perform f_bdc_insert.
    REFRESH T_BDCDATA.
      ENDLOOP.
    ENDFORM.                    " F_PROCESS_BDC
    *&      Form  f_bdc_dynpro
      p_prog is the program name to which data is passed                *
      p_dyno is the screen number to which the data is passed
        Routine for populating the BDCDATA structure with the
        Screen related information
    FORM f_bdc_dynpro USING    p_prog
                               p_dyno.
      t_bdcdata-program  = p_prog.
      t_bdcdata-dynpro   = p_dyno.
      t_bdcdata-dynbegin = 'X'.
      APPEND t_bdcdata.
      CLEAR t_bdcdata.
    ENDFORM.                    " F_bdc_dynpro
    *&      Form  F_BDC_FIELD
          p_fnam is the field name to which value is passed
          p_fval is the field value which is passed
       p_fnam is the field name to which value is passed
       p_fval is the field value which is passed
    FORM f_bdc_field USING    p_fnam
                              p_fval.
      t_bdcdata-fnam = p_fnam.
      t_bdcdata-fval = p_fval.
      APPEND t_bdcdata.
      CLEAR t_bdcdata.
    ENDFORM.                    " F_bdc_field
    *&      Form  F_PROCESS_DATA                                          *
         Routine to used for moving data from T_bpcs internal table to  *
         t_mdata Internal Table                                         *
    FORM f_process_data.
      LOOP AT t_bpcs.
        CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
             EXPORTING
                  input  = t_bpcs-matnr
             IMPORTING
                  output = t_mdata-matnr.
        MOVE t_bpcs-dosage TO t_mdata-zzjp_dos_frm.
        MOVE t_bpcs-appearance TO t_mdata-zzjp_aprn.
        MOVE t_bpcs-idcode  TO t_mdata-zzjp_con_id.
        MOVE t_bpcs-prostformno TO t_mdata-zzjp_nyu_sop.
        MOVE t_bpcs-weitab TO t_mdata-zzjp_wei_tab.
        MOVE c_blank TO t_mdata-zzjp_bio.
        MOVE c_blank TO t_mdata-zzjp_itf.
        MOVE t_bpcs-uom1 TO t_mdata-zzjp_car.
        MOVE t_bpcs-uom2 TO t_mdata-zzjp_cas.
        MOVE t_bpcs-carsize TO t_mdata-zzjp_car_size.
        MOVE t_bpcs-cassize TO t_mdata-zzjp_cas_size.
        MOVE t_bpcs-rupqty TO t_mdata-zzjp_rupqty.
        MOVE c_intls TO t_mdata-zzjp_init_ls.
        MOVE c_blank TO t_mdata-zzjp_re1.
        MOVE c_blank TO t_mdata-zzjp_re2.
        MOVE c_blank TO t_mdata-zzjp_re3.
        MOVE c_blank TO t_mdata-zzjp_pro_id.
        MOVE c_blank TO t_mdata-zzjp_bu_id.
        MOVE t_bpcs-abvname TO t_mdata-zzjp_abv_name.
        MOVE c_blank TO t_mdata-zzjp_abv_id1.
        MOVE c_blank TO t_mdata-zzjp_abv_id2.
        MOVE c_blank TO t_mdata-zzjp_spl_id.
        APPEND t_mdata.
      ENDLOOP.
    ENDFORM.                    " F_PROCESS_DATA
    *&      Form  f_bdc_close
          Routine to close the BDC Session
    FORM f_close_group.
      CALL FUNCTION 'BDC_CLOSE_GROUP'
           EXCEPTIONS
                not_open    = 1
                queue_error = 2
                OTHERS      = 3.
      IF sy-subrc <> 0.
             MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
             WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    ENDFORM.                    " f_close_group
    *&      Form  f_bdc_insert
         routine to input batch data into the Transaction MM02 from the
         session created
    FORM f_bdc_insert.
    CALL FUNCTION 'BDC_INSERT'
             EXPORTING
                  tcode            = c_tcode
             TABLES
                  dynprotab        = t_bdcdata
             EXCEPTIONS
                  internal_error   = 1
                  not_open         = 2
                  queue_error      = 3
                  tcode_invalid    = 4
                  printing_invalid = 5
                  posting_invalid  = 6
                  OTHERS           = 7.
        IF sy-subrc <> 0.
             MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
             WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
        ENDIF.
    ENDFORM.                    " f_bdc_insert
    Reward Points if it is useful
    Thanks
    Seshu

  • How to find classtype and class for a material.

    Hi,
    How to find classtype and class for a material.
    which table contains this data.
    Thanks
    Kiran

    Hi Kiran,
    Check below sample code. Use this BAPI which will give all info about the class for the material.
      DATA:      l_objectkey_imp    TYPE bapi1003_key-object
                                         VALUE IS INITIAL.
      CONSTANTS: lc_objecttable_imp TYPE bapi1003_key-objecttable
                                         VALUE 'MARA',
                 lc_classtype_imp   TYPE bapi1003_key-classtype
                                         VALUE '001',
                 lc_freight_class   TYPE bapi1003_alloc_list-classnum
                                         VALUE 'FREIGHT_CLASS',
                 lc_e               TYPE bapiret2-type VALUE 'E',
                 lc_p(1)            TYPE c             VALUE 'P',
                 lc_m(1)            TYPE c             VALUE 'M'.
      SORT i_deliverydata BY vbeln posnr matnr.
      CLEAR wa_deliverydata.
      LOOP AT i_deliverydata INTO wa_deliverydata.
        REFRESH: i_alloclist[],
                 i_return[].
        CLEAR:   l_objectkey_imp.
        l_objectkey_imp = wa_deliverydata-matnr.
    *Get classes and characteristics
        CALL FUNCTION 'BAPI_OBJCL_GETCLASSES'
          EXPORTING
            objectkey_imp         = l_objectkey_imp
            objecttable_imp       = lc_objecttable_imp
            classtype_imp         = lc_classtype_imp
    *   READ_VALUATIONS       =
            keydate               = sy-datum
            language              = sy-langu
          TABLES
            alloclist             = i_alloclist
    *   ALLOCVALUESCHAR       =
    *   ALLOCVALUESCURR       =
    *   ALLOCVALUESNUM        =
            return                = i_return
    Thanks,
    Vinod.

  • SERVICE  PO using service master and service PO using Material Type DIEN

    Dear Gurus can you differenciate between SERVICE  PO using service master and service PO using Material Type DIEN ?
    Regards
    Vinod Suresh Kakade

    Hi,
    Material type DIEN is used for when you offer "SERVICE" to your customer.
    When you are procuring "SERVICE" from your vendor, you can use external service management where service master is used (Steps are PO created in ME21N with Item Cat. "D" with Acc. ***. Cat. "K" or "C", ML81N, MIRO & F-53).
    In Standard DIEN material type designed for Sales usage only, but you can use DIEN for Purchase also to avoid External Services Management.
    Regards,
    Biju K

  • Customs document type cannot be determined for external document Type F8

    Hello Experts
    Need help
    I am trying to transfer F8 to GTS 10.1 and getting following message in GTS  Transfer log for export:
    Customs document type cannot be determined for external document Type F8
    New implementation
    GTS 10.1 running with SP 12
    ECC side Plug-In settings are fine. BAdi is Active.(There is no document mapping for F8/CUSDEC as it is not required in 10.1)
    GTS side configurations are also fine. Checked several times by 4 sets of eyes!!
    (Include general settings configurations, Customs communication configurations:)
    (Defining technical medium, conditions/output parameters, defining messages for communication process,
    defining determination for activity sequence and control settings for communication process)
    Despite this I am not able to trnasfer F8 successfully
    Can someone throw some light on this issue please?
    Keshav Murthy
    [email protected]

    Hi Dhilipan
    Here we go..
    You asked me to check the following
    Please check following things
    1) Legal regulation is activated. - Yes Activated
    2) Process template assigned to the legal regulation - Yes Assigned
    3) Activity Sequence determination - Yes done
    4) Open the activity sequence in under Control settings for Communication processes and check if there is a document type assigned to it. Table- /SAPSLL/TLEPAF - Yes done.
    It is really puzzling.
    Thanks
    Keshav Murthy

  • Can we capture two types of Serial Numbers for a material?

    Hi,
    I have scenario where i need to capture two different types of serial numbers for a material. This scenario is very similar to the below one -
    Say if a CAR is a serialized material, then i want to capture engine no. and chasis no. for each car.
    I know in standard serial number management, we can capture one kind of serial no. for an item, but can we capture two types of serial number for an item? If yes, how we can do that?
    Please help.
    Thanks,
    Parimal.

    Hi,
    No it is not possible to have two serial numbers for a material.
    The main attribute of a serial number is that it is UNIQUE.
    You can better have the vehicle number as the required serial number and the other numbers under the Manufacturer data of the General data tab of the IQ01 transaction. ( Equipment master creation ).
    You can better change the name of the manufacturer data such as Model number to Engine numeber and Manu serial no to Chasis no etc.., using CMOD transactions.
    Regards

Maybe you are looking for