BADI for adding subcontract quantity while running MRP

Dear All,
Here we have developed a BADI which will collect subcontract data and add to the stock and show in MD04 Transaction.
For this in development server we had developed BADI It is working fine in development server. But same thing we have ported into production server ,BADI
also in activation mode in production server but still it is not working ..
please help me to solve this.
Reards,
Kumar.

this is not the way SAPs MRP run works.
Where is the benefit for this?
the requisitions are not even split into header and item table, it is just one table EBAN, and either way you would get exact the same number of records in EBAN.

Similar Messages

  • Validation while running MRP

    Hello Experts,
                          Currently while running MRP, system has the provision of taking material which are in scrap stock, We want to put a validation so that material of scrap location cannot be used while MRP run .
    Please suggest.
    Regards,
    Ankur

    You need to exclude the scrap storage location from MRP through IMG tcode S_ALR_87006263
    Also for all the materials you need to change the MRP indicator = 1 in MMSC for that storage location. You can do it in a mass way using tcode MM17.

  • Is it bad for your mac to completely run out of battery?

    Is it bad for your Macbook Air to run completely out of battery?

    don't let it happen too often.

  • I have implemted badi  for adding tab vl01 t.code?

    Hi abapers,
    I have implemented badi  for adding tab vl01 t.code?But additional tab is not appearing in vl01?

    Hi,
    I found something similar.hope it helps.
    lets say u have to add fields to standard table  EKPO.
    U can add a customer field in a standard table only for those standard table which has given the provision for adding fields .
    Go to se11 and check out the table. there u will have CI_EKPODB  . "CI " stands for custom include.
    i u can add my field.
    Read the following----
    To add the customer field :
    Go to SE11 --> EKPO -->Display --> then doube click the data element "CI_EKPODB"... it will ask whether u want to create a field ...press YES and then continue with adding the field.. "ZZPAYMENT" in that ...
    Creating the field in the table:
    Give the name of the componenet "ZZPAYMENT" and the related data element (if the field "ZZPAYMENT" is of type CHAR give the data element as "CHAR" and give the needed length of the field say (15)...... then save and activate ur table........ it will show some warnings .... (ignore that) now ur table with the customer field will be ready
    Hope this helps u out.
    regards,
    Hari Kiran

  • One pr for multiple materials with line items while running mrp

    Hi SAP gurus,
                  I am config the system for MRP as per my client requerement.
                     We use CBP for different RAW materialsfor example they having a 10 materials for planning,were,
             MRP type is VB,
              LOT size is FX,with Different Reorder points and fix order quantity for all materials,
             My client whant run MRP for all these materials in single time that means they whant multiple item at single levels,
            i soles these requirement with the help of Product Group(sop) and its working but when we running md02 for product group all materials have planed and they give different purchase requistion numbers for all these materials but my client Wants single purchase requistion with line items for all these materials.
         Pls give me the solution for that requirement.
    thanks and Regards,
    abhi

    this is not the way SAPs MRP run works.
    Where is the benefit for this?
    the requisitions are not even split into header and item table, it is just one table EBAN, and either way you would get exact the same number of records in EBAN.

  • ERROR : in BADI for MIGO  Enter quantity on external screen

    Hi,
    I am doing MIGO and getting the following error:
    Enter quantity on external screen Message no. M7895
    I Have added an external tab at the header level as well as the item level using the badi for tab addion in MIGO .
    If i deactivate the BADI  MIGO works fine  .
    How to analyse for the error .
    Please help
    Regards
    Swapnil

    HI Experts,
    As mentioned in above thread for the Error: Enter unit of measure on external screen Message no. M7895;and same is solved by your functional consultant,since i am also getting same error,It would be very helpfull to me,if you tell me the solution for this error what exactly your functional consultant has done.
    Regards
    varunraj

  • While running MRP

    Hi guru's,
      Is it possible...to create the Purchase Order automatically while running the MRP..if so how...
    Thanks in Advance....

    Hi
    If u have created PR after MRP run these can be converted to Automaticaly to PO but need to maintain following settings
    1) Material Master purchasing view tick automatic PO check box
    2) Vendor Master purchasing view tick automatic PO check box.
    3) Maintain Source list for Vendor & Material.
    4) Maintain Purchase Info Record.
    5) Create a Purchase Requisition.
    6) Use T.Code: ME59N & execute for PR for vendor, you will be able to create automatic PO.
    ( To convert pr in PO PR must be assigned with source  )
    Vishal...

  • Dump while running MRP: MD03:   PERFORM_CONFLICT_TAB_TYPE CX_SY_DYN_CALL_IL

    Dear All,
    I am trying to run MRP for a single item at a single level. The program is giving a dump.
    If anyone knows a way around kindly tell me.
    Thanks. Anu.
    SHORT DUMP:
    Runtime errors         PERFORM_CONFLICT_TAB_TYPE                                         
    Exception              CX_SY_DYN_CALL_ILLEGAL_TYPE                                       
           Occurred on     28.02.2008 at   12:19:49                                                                               
    Illegal type when passing an internal table to a FORM                                                                               
    What happened?                                                                               
    Error in ABAP application program.                                                                               
    The current ABAP program "SAPLEINU" had to be terminated because one of the              
    statements could not be executed.                                                                               
    This is probably due to an error in the ABAP program.                                    
    A FORM was called incorrectly.                                                                               
    What can you do?                                                                               
    Print out the error message (using the "Print" function)                                 
    and make a note of the actions and input that caused the                                 
    error.                                                                               
    To resolve the problem, contact your SAP system administrator.                           
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer                 
    termination messages, especially those beyond their normal deletion                     
    date.                                                                               
    Error analysis                                                                               
    An exception occurred. This exception is dealt with in more detail below                 
    . The exception, which is assigned to the class 'CX_SY_DYN_CALL_ILLEGAL_TYPE',           
    was neither                                                                             
    caught nor passed along using a RAISING clause, in the procedure                         
    "ME_UPDATE_AGREEMENT_PO" "(FUNCTION)"                                                   
    Since the caller of the procedure could not have expected this exception                 
    to occur, the running program was terminated.                                           
    The reason for the exception is:                                                         
    Incorrect FORM call.                                                                     
    The FORM call is incorrect for parameter number 1.                                       
    The current internal table passed to the formal table parameter has                      
    a type that is not compatible with the type of the formal parameter.                     
    The condition selected below has been violated:                                                                               
    (" ") The access types defined for the tables are incompatible.                          
          The following hierarchy shows the compatibility rules:                                                                               
    ANY_TABLE                                                                               
                        INDEX_TABLE   HASHED_TABLE                                           
                STANDARD_TABLE    SORTED_TABLE                                                                               
    A concrete access type is only compatible with types higher                        
          in the hierarchy. For example, STANDARD_TABLE is compatible                        
          with INDEX_TABLE and ANY_TABLE, but not with HASHED_TABLE.                                                                               
    ("X") The line types of the tables are incompatible.                                                                               
    (" ") The table keys of the tables are not identical.                                                                               
    (" ") One of the tables has a UNIQUE key, but the other has a                            
          NON-UNIQUE key.                                                                               
    How to correct the error                                                                               
    The exception must either be prevented, caught within the procedure                      
    "ME_UPDATE_AGREEMENT_PO"                                                                
    "(FUNCTION)", or declared in the procedure's RAISING clause.                             
    To prevent the exception, note the following:                                                                               
    You may able to find an interim solution to the problem                                  
    in the SAP note system. If you have access to the note system yourself,                  
    use the following search criteria:                                                                               
    "PERFORM_CONFLICT_TAB_TYPE" CX_SY_DYN_CALL_ILLEGAL_TYPEC                                 
    "SAPLEINU" or "LEINUU04"                                                                 
    "ME_UPDATE_AGREEMENT_PO"                                                                 
    If you cannot solve the problem yourself, please send the                                
    following documents to SAP:                                                                               
    1. A hard copy print describing the problem.                                                
       To obtain this, select the "Print" function on the current screen.                       
    2. A suitable hardcopy prinout of the system log.                                           
       To obtain this, call the system log with Transaction SM21                                
       and select the "Print" function to print out the relevant                                
       part.                                                                               
    3. If the programs are your own programs or modified SAP programs,                          
       supply the source code.                                                                  
       To do this, you can either use the "PRINT" command in the editor or                      
       print the programs using the report RSINCL00.                                                                               
    4. Details regarding the conditions under which the error occurred                          
       or which actions and input led to the error.

    Dear All,
    I am trying to run MRP for a single item at a single level. The program is giving a dump.
    If anyone knows a way around kindly tell me.
    Thanks. Anu.
    SHORT DUMP:
    Runtime errors         PERFORM_CONFLICT_TAB_TYPE                                         
    Exception              CX_SY_DYN_CALL_ILLEGAL_TYPE                                       
           Occurred on     28.02.2008 at   12:19:49                                                                               
    Illegal type when passing an internal table to a FORM                                                                               
    What happened?                                                                               
    Error in ABAP application program.                                                                               
    The current ABAP program "SAPLEINU" had to be terminated because one of the              
    statements could not be executed.                                                                               
    This is probably due to an error in the ABAP program.                                    
    A FORM was called incorrectly.                                                                               
    What can you do?                                                                               
    Print out the error message (using the "Print" function)                                 
    and make a note of the actions and input that caused the                                 
    error.                                                                               
    To resolve the problem, contact your SAP system administrator.                           
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer                 
    termination messages, especially those beyond their normal deletion                     
    date.                                                                               
    Error analysis                                                                               
    An exception occurred. This exception is dealt with in more detail below                 
    . The exception, which is assigned to the class 'CX_SY_DYN_CALL_ILLEGAL_TYPE',           
    was neither                                                                             
    caught nor passed along using a RAISING clause, in the procedure                         
    "ME_UPDATE_AGREEMENT_PO" "(FUNCTION)"                                                   
    Since the caller of the procedure could not have expected this exception                 
    to occur, the running program was terminated.                                           
    The reason for the exception is:                                                         
    Incorrect FORM call.                                                                     
    The FORM call is incorrect for parameter number 1.                                       
    The current internal table passed to the formal table parameter has                      
    a type that is not compatible with the type of the formal parameter.                     
    The condition selected below has been violated:                                                                               
    (" ") The access types defined for the tables are incompatible.                          
          The following hierarchy shows the compatibility rules:                                                                               
    ANY_TABLE                                                                               
                        INDEX_TABLE   HASHED_TABLE                                           
                STANDARD_TABLE    SORTED_TABLE                                                                               
    A concrete access type is only compatible with types higher                        
          in the hierarchy. For example, STANDARD_TABLE is compatible                        
          with INDEX_TABLE and ANY_TABLE, but not with HASHED_TABLE.                                                                               
    ("X") The line types of the tables are incompatible.                                                                               
    (" ") The table keys of the tables are not identical.                                                                               
    (" ") One of the tables has a UNIQUE key, but the other has a                            
          NON-UNIQUE key.                                                                               
    How to correct the error                                                                               
    The exception must either be prevented, caught within the procedure                      
    "ME_UPDATE_AGREEMENT_PO"                                                                
    "(FUNCTION)", or declared in the procedure's RAISING clause.                             
    To prevent the exception, note the following:                                                                               
    You may able to find an interim solution to the problem                                  
    in the SAP note system. If you have access to the note system yourself,                  
    use the following search criteria:                                                                               
    "PERFORM_CONFLICT_TAB_TYPE" CX_SY_DYN_CALL_ILLEGAL_TYPEC                                 
    "SAPLEINU" or "LEINUU04"                                                                 
    "ME_UPDATE_AGREEMENT_PO"                                                                 
    If you cannot solve the problem yourself, please send the                                
    following documents to SAP:                                                                               
    1. A hard copy print describing the problem.                                                
       To obtain this, select the "Print" function on the current screen.                       
    2. A suitable hardcopy prinout of the system log.                                           
       To obtain this, call the system log with Transaction SM21                                
       and select the "Print" function to print out the relevant                                
       part.                                                                               
    3. If the programs are your own programs or modified SAP programs,                          
       supply the source code.                                                                  
       To do this, you can either use the "PRINT" command in the editor or                      
       print the programs using the report RSINCL00.                                                                               
    4. Details regarding the conditions under which the error occurred                          
       or which actions and input led to the error.

  • ABAP runtime error for 0CRM_OPPT_H and I while running RSA3

    hello Gurus,
         I'm having problems while running RSA3 transaction for these data sources.
    0CRM_OPPT_H
    0CRM_OPPT_I
    0CRM_SALES_ACT_1
    0CRM_SALES_ACT_I.
    I'm getting ABAP runtime error for these.
    This is the error:
    Runtime Error          CALL_FUNCTION_CONFLICT_TAB_TYP
    Exception              CX_SY_DYN_CALL_ILLEGAL_TYPE
    I tried finding OSS notes for these, but I didn’t succeed.
    I activated the data source from RSA5, and then I tried RSA3. That time I got “Errors occurred during extraction”.
    After that I activated delta at BWA5, then I started getting runtime error.
    Even though I activated at BWA5, I am not able to see the data sources at BWA7.
    Am I missing any thing…please guide me through this….
    Thanks
    RKR

    Thanks for your replay... All the DS and related tables are active..
    But wen I tried to re-generate the DS again... this is the warning I'm getting... Any idea why I'm getting this....
    The even-numbered length of the DEC field SAMPLE_QTY_ALLOW can lead to problems
    <b>Message no. R8569</b>
    <b>Diagnosis</b>
    You want to use the field SAMPLE_QTY_ALLOW in the extract structure for DataSource 0CRM_OPPT_I. This field has a field of type 'DEC' (or 'CURR' or 'QUAN') with an even number of characters.
    This can create problems since the length resulting from calculations in ABAP (for example, in extractors or Customer Exits for extraction) is too large to be inserted in the database later (PSA in BW), causing a short dump.
    <b>Procedure</b>
    This warning is only relevant when the maximum length of this field is exceeded during extraction, for example when the field is expanded in the Customer Exit through a calculation.
    More information and a remedy can be found in SAP Note 641744.
    When I search the OSS note, SAP suggesting to apply 883310 note.
    In my company we are using CRM 4.0 servie pak8. SAP suggsting to install service pak 11, but my client is not interested to upgrade to 11 as CRM people are working on service pak 8.
    By any chance we can use specific note which change the ABAP code to solve this problem... Please give me some suggetions...
    Thanks
    RKR

  • Implementing 2 Badis for adding new internal follow-up actions and saving

    Hi Guys
    I would like assistance with the implementations of two badis in EMW.  The one badi is called /SCWM/IF_EX_QFU and is used for adding new internal follow-up actions and the second badi is called /SCWM/EX_QFU_SAVE and is used for saving the new follow-up actions that that have been created.
    Regards
    Maud

    Hi Guys
    I would like assistance with the implementations of two badis in EMW.  The one badi is called /SCWM/IF_EX_QFU and is used for adding new internal follow-up actions and the second badi is called /SCWM/EX_QFU_SAVE and is used for saving the new follow-up actions that that have been created.
    Regards
    Maud

  • Authorization for adding attachments only while approving P.O

    Hi
    We work with SRM5 SP14.
    we are intrested in adding an authorization to PO approvers for adding attachments/texts in the "documents" tab in item & header.
    Is this a customizing process or role change?
    Thanks
    Hila

    Anyone???

  • BADI For Changing Planned order Qty during MRP Run

    Hi,
      My requirement is i want to change Planned order qty based on some conditions during MRP run(MD02). Is there any BADI to fullfill my requirement.
    Thanks,
    Kishore

    Not sure I understand the situation correctly...You want to delete the planned orders before MRP runs again. WHy do you want to do that ? Are these firmed Planned orders ?

  • Procurement qty restriction while running MRP

    Dear Expert,
    In our plant there is a GCPB consent issue,in GPCB consent issue we can dispatch only limited quantity of product as per the approved quantity per month, in other words we can't dispatch the material above GPCB approved quantity.
    For example :
    We have a product Sodium chloride which GPCB approved quantity is of 25 kg per month, that means we can't procure more then 25kg for this product. So please guide me how can i control the procurement of this product during MRP Run so that system will not generate the PR if the quantity including the stock is more than the GPCB approved quantity.
    Regards,
    Phalgun Patel

    Mario asked you planning method which means MRP type , not planning strategy.
    From your reply I assume that you're using PD. Change it to VB and enter the manual re-order point values.
    For example: enter your re-order point as 5, lot size as HB and maximum stock level as 25, in this case as soon as stock goes below 5 (let assume it goes to 4) it's gonna create a procurement proposal for a quantity of 21.
    or
    enter your re-order point as 5, lot size as MB (monthly lot size) and rounding value as 25, so whenever stock goes below 5 it will create a procurement proposal for 25.

  • Super BOM doesn't generate while run MRP from Sales Order

    Hi all,
    I am trying to make a Super BOM
    where i have a material x as finished product, and i have 2 material as component for that finish product ( A and B )
    i already create characteristic and assign it to the class 300, i also have created the configuration profile for the finish goods material and the object dependencies selection condition type for those material component in the BOM Item,
    i also have check using simulation CU50 and the BOM is ok
    But when i try to create Sales Order, entry the characteristic and run the MRP using MD02, the Super BOM doesn't explode
    Is there anyone who can help to solve this problem??
    Regards,
    Marufat

    Hi,
    Does any planned order generated for the finished material? or you are talking about the components explosion?
    If all the answer is Yes, then check and maintain the 2 collective requirement in MRP4 tab for the components material master.
    And reprocess the MRP and check.
    Thanks
    Hrishi

  • Screen exit/BADI for adding custom field in IW31/IW32

    Hi all,
    The requirement is to add the permit field in the Header component of IW31. Searched SDN and found user exit IWO10018 for the same which includes a screen exit.
    The activation of the same is adding a tab in the screen while user wants the field under header Component tab.
    How this can be done. Any suggestion.
    Thanks
    anya

    Hi,
      You can perform append structure to add your custom field(s)in VBAP table. Next step, go to SE51 (Screen Painter)to modify SAP Program SAPMV45A Screen number 4459 for Additional data A or Screen number 8459 for Additional data B to add your append structure custom fields.
    Once the above steps done, you can place your logic to populate custom fields in include program MV45AFZZ. i.e USEREXIT_MOVE_FIELD_TO_VBAP.
    At the end, please ensure all program and screen are activated. Hope this will help.
    Regards
    Kiran Sure

Maybe you are looking for