Material Document Plant wise

Hello,
I want to create GRN numbers seperately to get generated for two different plants.But however Standard SAP does allow us to do so.
Can anyone please help me to find a solution for creating Material Dcoument number range Plant wise.
Is there any User Exit available.If yes, can you please let me know logic and the ABAP coding for the same.
Many thanks for your help.
Regards,
Kumar

i want to create GRN numbers seperately to get generated for two different plants.But however Standard SAP does allow us to do so.
Can anyone please help me to find a solution for creating Material Dcoument number range Plant wise.
Is there any User Exit available.If yes, can you please let me know logic and the ABAP coding for the same.
Many thanks for your help.
Regards,
Kumar

Similar Messages

  • /SAPAPO/SDRQCR21 program is not working correctly if we run the program for range of material and plant wise

    Hi APO Experts,
    In our project, we have received more sales order inconsistencies which is not clearing by CCR program and it is clearing by  program /SAPAPO/SDRQCR21 with option as Build Reqmts from Doc. Flow, So We have decided to schedule the background job on daily basis for program /SAPAPO/SDRQCR21 with option as Build Reqmts from Doc. Flow, performing the testing in our quality system and observed the below strange behavior. 
    When I am running the program /SAPAPO/SDRQCR21 with Range of products and some location range with option as Build Reqmts from Doc. Flow, in Background job. In output it is suggesting to delete one sales order. If I checked that Sales order in ECC, it is for an different location, that is not part of my selection and the order is open. In MD04 the Qty is showing 1 ( as per sales order) but in APO RRP3 view the order qty is showing Zero. I have run the CCR, it is coming in different in content and if I push, the different is not going to APO.
    I have tried running the program /SAPAPO/SDRQCR21 with plant which is mentioned in that sales order with option as Build Reqmts from Doc. Flow, in Background job , it is suggesting this sales order under update option correctly.   
    Can you please help me understand why it is behaving differently like the location is not part of my selection and why it is suggesting the wrong action. And also whether is it advisable to run the /SAPAPO/SDRQCR21 with option as Build Reqmts from Doc. Flow at plant range and material range in background job.
    Thanks & Regards,
    Sundaram Radhakrishnan

    Sundaram,
    It sounds to me like the sales document records in the OLTP and in APO were created at different times.  This is common in Dev and Qual environments when the systems are commonly created at two different times, and each was a copy of an existing system that contained sales data.  The order number you see in //rrp3 is somewhat irrelevant; system generally uses the guid for many activities.
    FYI during Dev and Qual refreshes, if you are copying from a production environment that contains data, it is always best to create the OLTP and SCM images at the same time, and to copy them both to the Dev and Qual systems at the same time.  If you don't do this, you are faced with the additional tasks associated with getting the copied systems back into synch.
    If this is Dev or Qual, I suggest that you just completely wipe out all sales orders in APO and rebuild them using the CIF.
    If this is a mature production environment, the only time I have ever seen this issue is due to improperly created CIF enhancements.  Speak to your developers to find the root cause, and correct this problem.  Then, wipe out all sales orders and rebuild with CIF.
    Best Regards,
    DB49

  • Plant wise mir4

    hi experts
    Can u help me to find  T code for plant wise transaction of mir4,so that i ll get detail information  thanks in advance

    MIR4 is used to display invoice document.
    Use MIR5 to display invoice document plant wise(Click expert mode,Enter respective plant)

  • Regarding : Material document data and PO data do not match (Plant)

    Hi Gurus,
    Please go through this BAPI program.
    While uploading it is giving an error ' Material document data and PO data do not match (Plant) '.
    Please help regarding this issue.For all Other moment types it is working fine except this 351 moment type.
    dATA: i_excel TYPE truxs_t_text_data. "work table for excel upload
    DATA: BEGIN OF it_itab OCCURS 100,
          docdate(10),
          postdate(10),
          mvt_type(3), "Movement Type
          plant(4), "Plant
          lgort(4),
          pur_doc(10), "Purchase Document No
          po_item(3), "Purchase Document Item No
          material(18), "Material Number
         delnote(16),
          erfmg(13),
          uom(3),
         lfmng(13), "Quantity
          batch(10) TYPE c,
          vfdat TYPE vfdat,
          END OF it_itab.
    DATA: it_goodsmvt_head TYPE TABLE OF bapi2017_gm_head_01      INITIAL SIZE 100,
          it_goodsmvt_code TYPE TABLE OF bapi2017_gm_code         INITIAL SIZE 100,
          it_goodsmvt_item TYPE TABLE OF bapi2017_gm_item_create  INITIAL SIZE 100.
    DATA: wa_goodsmvt_head LIKE LINE OF it_goodsmvt_head,
          wa_goodsmvt_code LIKE LINE OF it_goodsmvt_code,
          wa_goodsmvt_item LIKE LINE OF it_goodsmvt_item.
    DATA: w_mat_doc  TYPE bapi2017_gm_head_ret-mat_doc,
          w_year     TYPE bapi2017_gm_head_ret-doc_year.
    DATA: BEGIN OF it_errmsg_goodsmvt OCCURS 10.
            INCLUDE STRUCTURE bapiret2.
    DATA: END OF it_errmsg_goodsmvt.
    DATA : obj_type LIKE bapiache09-obj_type,
           obj_key  LIKE bapiache09-obj_key,
           obj_sys  LIKE bapiache09-obj_sys.
    DATA: v_date1 TYPE sy-datum.
    DATA: v_date2 TYPE sy-datum.
    DATA: w_lines TYPE i.
    DATA: errflag.
    SELECTION-SCREEN BEGIN OF BLOCK bk1 WITH FRAME TITLE text-100.
    PARAMETERS: p_file TYPE  rlgrap-filename.
    SELECTION-SCREEN END OF BLOCK bk1.
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
      CALL FUNCTION 'F4_FILENAME'
        EXPORTING
          field_name = 'P_FILE'
        IMPORTING
          file_name  = p_file.
    Start-of-selection processing
    START-OF-SELECTION.
      CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'
        EXPORTING
          i_line_header        = 'X'
          i_tab_raw_data       = i_excel
          i_filename           = p_file
        TABLES
          i_tab_converted_data = it_itab[]
        EXCEPTIONS
          conversion_failed    = 1
          OTHERS               = 2.
      IF sy-subrc <> 0.
        MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
      ENDIF.
      LOOP AT it_itab.
        REFRESH it_goodsmvt_head.
        REFRESH it_goodsmvt_item.
        CONCATENATE it_itab-docdate6(4) it_itab-docdate3(2) it_itab-docdate+0(2) INTO v_date1.
        CONCATENATE it_itab-postdate6(4) it_itab-postdate3(2) it_itab-postdate+0(2) INTO v_date2.
        wa_goodsmvt_head-pstng_date = v_date2.
        wa_goodsmvt_head-doc_date   = v_date1.
       wa_goodsmvt_head-ref_doc_no = it_itab-delnote.
    wa_goodsmvt_head-pr_uname   = sy-uname.
        APPEND wa_goodsmvt_head TO it_goodsmvt_head.
    Maintain it_goodsmvt_code
        wa_goodsmvt_code-gm_code    = '04'.
    Maintain it_goodsmvt_item
    *LOOP AT it_itab.
    IF wa_goodsmvt_item-po_number IS INITIAL.
        wa_goodsmvt_item-po_number    = it_itab-pur_doc.
        wa_goodsmvt_item-move_type    = it_itab-mvt_type.
        wa_goodsmvt_item-MOVE_PLANT      = it_itab-plant.
        CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
          EXPORTING
            input  = it_itab-material
          IMPORTING
            output = it_itab-material.
        wa_goodsmvt_item-material     = it_itab-material.
        wa_goodsmvt_item-stge_loc     = it_itab-lgort.
        wa_goodsmvt_item-po_item      = it_itab-po_item.
        wa_goodsmvt_item-entry_qnt    = it_itab-erfmg.
        wa_goodsmvt_item-ENTRY_UOM_ISO    = it_itab-uom.
       wa_goodsmvt_item-po_pr_qnt    = it_itab-lfmng.
        wa_goodsmvt_item-batch        = it_itab-batch.
        wa_goodsmvt_item-expirydate   = it_itab-vfdat.
       wa_goodsmvt_item-NO_MORE_GR   = 'X'.
        wa_goodsmvt_item-mvt_ind      = 'B'.
        APPEND wa_goodsmvt_item TO it_goodsmvt_item.
        CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
          EXPORTING
            goodsmvt_header  = wa_goodsmvt_head
            goodsmvt_code    = wa_goodsmvt_code
          IMPORTING
            materialdocument = w_mat_doc
          TABLES
            goodsmvt_item    = it_goodsmvt_item
            return           = it_errmsg_goodsmvt.
    Process of commit work
        IF it_goodsmvt_head[] IS NOT INITIAL.
          DESCRIBE TABLE it_goodsmvt_head LINES w_lines.
        ENDIF.
        IF it_goodsmvt_item[] IS NOT INITIAL.
          DESCRIBE TABLE it_goodsmvt_item LINES w_lines.
          CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
            EXPORTING
              wait = 'X'.
        IMPORTING
        RETURN        =
          CLEAR errflag.
          READ TABLE it_errmsg_goodsmvt INDEX 1.
          IF it_errmsg_goodsmvt-type EQ 'E'.
            WRITE:/'Error in function', it_errmsg_goodsmvt-message.
            errflag = 'X'.
          ELSE.
            WRITE:/ it_errmsg_goodsmvt-message.
          ENDIF.
          IF errflag IS INITIAL.
            COMMIT WORK AND WAIT.
            IF sy-subrc NE 0.
              WRITE:/ 'Error in updating'.
              EXIT.
            ELSE.
              WRITE:/ 'Material Document created successfully and the Document Number for the Material',
                      wa_goodsmvt_item-material,'is:', w_mat_doc, w_year.
            ENDIF.
          ENDIF.
        ENDIF.
      ENDLOOP.

    Hey,
    Just wanted to post that in my case this was the error of MVT_IND field in item table. When I made it from 'B' to blank then it worked.
    Mine is solved....
    Thanks

  • Valuation Class according to Material Master but not Plant wise

    Hi,
    Is there way to find out the Valuation Class according to Material Master but not Plant wise...
    Plant wise, we can get into MBEW table, but I want to find valuation class directly...
    Plz guide..

    I need to change Valuation class against material number...
    We have 18 plant in our company and more than 2,50,000 material's.
    Which one easy task for change in material master, either 2,50,000 material's or 2,50,000 X 18 (45,00,000) material list.
    If I go with plant wise, we need to change 18 times...also this is time consuming process... As I know in all Plant's, valuation class must be same...
    please guide...

  • PO seriel number as per plant wise & Document type wise

    Hi,
    Purchase order seriel numbers should be based on plant wise & Document type wise
    Example:
    Plant    Document Type              Seriel number
    1000       NB                                4500000000 -  4599999999
    1000       UB                                4600000000 -  4699999999
    1000      ZSUB                             4700000000 -  4799999999
    1100       NB                                4800000000 -  4899999999
    1100       UB                                4900000000 -  4999999999
    1100      ZSUB                             4400000000 -  4499999999

    HI,
    U can customize the document type and select the no range depending on the requirements.
    U can even select an internal or a external no range depending on the requirements.
    Suitable no range can be adopted for the document type so that the sequence shall be followed.
    Refer SPRO--MM-PURCHASING-PO----NO RANGES.
    Hope this helps.
    Regards,
    Prasanna
    Pls award if helpful.

  • Material listing by plant wise

    Hi Kings,
                  I want to do material listing by plant wise where can i do customization for this this or i have to do any master data mantainance .
    please help me out very argent
    thanks,

    hi,
    U can try this
    Ur requirement can fulfilled by using combination of fields in condition table  of Listing/exclusion
    menu path:
    Spro-> img>SD-> basic function -
    > listing/exclusion->Maintain condition tables for listing/exclusion--> table 003
    This table u have to assign to the access sequence. Then this access sequence u assign it to the condition type which is maintainesd in the <b>Procedures for maintaining listing/exclusion</b>
    Now try with VB01, then listing/ exclusion for the customer happens at plant
    hope this helps u
    regards,
    Arun prasad

  • WRONG PLANT GENERATED WITH MATERIAL DOCUMENT IN HU02

    Hi All,
    I am packing Handling unit with HU02 with following options.
    Supplying plant 4140
    Storage loc 2000(FG) to 2100(HU) with Batch number 11.
    After Saving this HU, when i check Material Document in Migo generated for
    above Handling unit, it shows Material From 4340 plant & Sto loc. 2000 to 2100.  I had never entered 4340 plant.
    How this is updating?Any setting is missing? Material is Batch Activated.
    Kindly guide
    Reg
    Jay

    clsoed

  • Plant wise material weight

    Hi,
    We have multiple mfg plants under one company code accross the country where same material
    have different weight in different mg plants, but as per my knowladge in material master for one material code
    we can maintain one gross/nett weight which will applicable to all plants.Plz let me
    know how can I  maintain gross / nett weight mfg plant wise for one material code.
    regards,
    sps

    Hi
    probably you can think of putting the weight of the material in some of the views which are plant specific for example MRP/purchasing/general plant data etc. This is much easier than having independent material no.s for each plant.
    Regards

  • Sales office/plant  wise restriction of prices for first 50 nos of X material

    hi
    we have a requirement from our marketing department.
    We have prices  for some material plant wise. Now we want to sell first N number (let us assume first 50 quantity in plant ) should have different pricing and after N quantity ( from 51st quantity ) in that plant should have different one.
    (Ex. Let us say i am selling Reynolds Pen in two different sale offices.
    Pricing in sale office 1 : for first 50 qty of Reynolds pen : Rs.12/-
                                              from 51st qty of Reynolds pen : Rs.15/-
    Pricing in sale office 2 : for first 50 qty of Reynolds pen : Rs.13/-
                                              from 51st qty of Reynolds pen : Rs.16/-
    How to achieve the special scenario ?
    We cannot use  condition update (but it is not going to come plant wise)
    Please guide us in achieving this.
    regards
    padma

    Hi,
    We cannot use  condition update
    what is the reason of not using CONDITION UPDATE ?
    by using Condition update only you can achieve this
    if you want different price based on Sales office or Plant, just activate Sales office and Plant in the access sequence and maintain condition records accordingly
    and Maximum number of orders you can maintain the ADDITIONAL DATA in the condition record for that particular combination
    for example, just maintain maximum number of orders as 50 and maintain price as 12. system will automatically change the value after 50 orders
    please try and revert if you need more help
    thanks
    santosh

  • Maintain plant wise purchase document type

    Hi,
    I want to know that is there any way where I can able to maintain plant wise purchase document type.
    Thanks.

    Please make the following settings
    Scenario:
    Plant 0001 Should create only PO type NB and PR type NB
    Plant 0002 Should create only PO type ZNB and PR type ZNB
    TCode : OLME
    Create new PR type by copying NB (all dependencies): ZNB  <<<Separate number range can be used
    Create new PO type by copying NB (all dependencies) : ZNB <<< Separate number range can be used
    To avoid accidental assignment of (by users)
    Remove linkage of NB PO type to ZNB PR type
    Remove linkage of ZNB PO type to NB PR type
    TCode: OMDT
    Assign PR type per plant per MRP Group for MRP generated PR's
    Once MRP is run for materials PRs are created as follows plant 0001 type NB and plant 0002 type ZNB, when they run ME57 to create POs from PRs, ZNB PO type will default to PR types ZNB and NB type to NB.
    Authorization objects to be changed for each plant respectively (go to SU21 to look up)
    Users of Plant 0001 can only create NB type PR and NB type PO
    Purchase Order:
    M_BEST_BSA   ACTVT=01; BSART=NB; 
    Purchase Requisition:
    M_BANF_BSA   ACTVT=01;BSART= NB;
    M_BANF_WRK  ACTVT=01;WERKS= 0001 ;
    Users of Plant 0002 can only create ZNB type PR and ZNB type PO
    Purchase Order:
    M_BEST_BSA   ACTVT=01; BSART=ZNB; 
    Purchase Requisition:
    M_BANF_BSA   ACTVT=01;BSART= ZNB;
    M_BANF_WRK  ACTVT=01;WERKS= 0002 ;
    Ofcourse you need to create output message config for each PO type.
    Edited by: Jeevan Sagar on Feb 13, 2012 11:16 PM

  • Creating spection lot material document wise.

    Dear Friends,
    There is one RM having  batch management active,  now when i do GR against PO client need to split the quantity to say 25 batches ( ex. 5 tons paper received but there may be 25 roles of 200 kg each having each one separate batch no.) . So going by std process, system is creating 25 insp. lots. My requirement is system should generate  only one lot  per material document. ( since batch management is active , in Quality view of material master in insp setup system is allowing only for each material document item or material doc and batch). Pl guide me is it possible to create singe inspection lot  for split GR with batch management active.
    Since there is no fix quantity of roles coming in truck using of skip inspection won't seem to be right choice. Pl correct if it is other way.
    Best Regards
    Shekhar Mokashi

    Dear Shekhar
    In that case Skip will not also work as you may not have a picture of the stokc coming etc.
    I dont have a solution  for this now. What i can suggest is make use of user exits in this case. Try using this exits and check whether it can help you or else check the exit in MIGO. Give a login in such a way that only for the first line item or so the inspection lot is created
    QAAT0002 Control of acceptance lots/goods receipt          
    |  QBCK0001 |Enhancements to function module group QBCK 
    |  QBCK0002 |Extended check in procurement
      QBCK0003 |Extended QM check for goods receipt                                 
    Regards
    Gajesh

  • Default profit centers Plant wise for Balance Sheet tax relevant Items.

    Dear All,
    We have an issue in profit center acccounting.
    In balance sheet accounts, Vat input tax payable, TDS payable, Cenvat clearing etc are picking profit center from 3KEH. When Exicse is getting captured cenvat clearing account having the profit center but while doing the MIRO cenvat clearing do not have profit center & plant.
    Why it is so?
    Basically we are doing the following steps.
    1. Purchase order creation ME21N.
    2.Goods received via migo
    3. invoice receipt via miro.
    At the time of miro posting, system creates automatically accounting document, with default profit center maintained in 3KEH, which are assigned to Vat input tax payable, TDS payable, other tax accounts. For GR/IR clearing account right profit center is picking without any mistake, while doing MIGO & MIRO.
    We need to extract the Balance Sheet profit center wise at plant level.
    Derivation rule is created for this balance sheet account along with Valuation area condition to post to correct profit center maintained under Tcode: 3KEI . But system is taking only default profit center (3KEH).
    I have checked configuration and the following areas like Material master costing view, tax code areas, and account group but did not find any mistake.
    Please advice and Guide us, how to get correct profit center at plant level for these balance sheet accounts instead of default. (I want to make default profit centers plant wise).
    It is urgent.
    Thanks,
    Shailendra Gupta.

    Hi!
    You can use following report :
    S_ALR_87013336 (Report for Balance sheet at Profit Center and Group Level).
    Hope this will help.
    Thanks & Regards,
    Taral Patel

  • How to get list of docs for particulat billing type on plant wise

    very urgent
    is there any t-code, report to look thi
    how to get list of billing docs grnerated  for particulat billing type and if possible  on plant wise also
    very urgetnt
    points to be rewarded
    eagerly waitng from sap gurus

    Dear chakri
    As you may be aware, in VF05 you need to enter either Payer Code or Material Code and then based on the selection criteria, the report will generate.  Please give the (ensure that this code is exist in billing document) Payer code and now select "Further sel.criteria" and DONT forget to enter the date in from column of "Billing docs.date".  By default, there you can see one month date range. 
    Still if you get error message, please let me know the error message.
    thanks
    G. Lakshmipathi

  • Material Document- Serial Numbers

    Hi All,
    I have a requirement where in I have to fetch the serial numbers of line items in a material document. Please help me in this regard either if any BAPIs available or at the table level. Your help is greatly appreciated.
    Thanks in advance.
    Moderator message: please do some own research before asking.
    Edited by: Thomas Zloch on Feb 21, 2011 11:56 AM

    HI,
    1) Material serial number activation as follows.
    Using T-Code MM01- material code creation to the respective plant,storage location,sales org and then give input data to the material view screen basic data1, basic data2...... In the view Plant data / Stor.2 input screen General plant parameters options Serial no.profile - '0001', SerLevel - '1' data to be given during material creation time. After that doing MIGO for the material, it will ask material serial number.
    2) Material serial number purpose as follows.
    a) Material identification based on serial number.
    b) Material serial number wise issues in FIFO method.
    c) Material stock.
    Hope, it is useful for you.
    Regards,
    K.Rajendran.

Maybe you are looking for