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.

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.

  • 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...

  • 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.

  • 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.

  • Re: STOC . not considered while running MRP

    Hi Experts,
    I having one doubt in the following scenario.
    Plant1000  needs 5 qty of  AB Material from 1001 , requiremnt given thro Stock transfer order ME21N. date :21.03.2008
    1001 is producing the goods based on PIR. Presently,  plant 1001 have stock qty of 10 Nos. as on 21.03.2008
    If I run the MRP , instead of considering the stock 10 nos.
    It's throwing new requiremnt of 5 Nos.
    Please guide me to sort out this issue.
    Thanking you
    Regards
    Chandru

    Hi,
    Alreday I have a PIR of 10 Qty in that production plant. Now i'm  rasing one  STOC from some other plant for 5 Nos.
    It should consider the PIR as like sale order consumption on PIR. Then it should throw the PLnd order for 5 Qty.
    Here tis is not happening, it's giving plnd order for 15 qty.
    Please guide me.
    Thanking you
    Regards
    Chandru

  • 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

  • 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.

  • Donot run mrp for available stock in md01 ?

    hi frenz,,,
    i ve got one requirement,,,
    while running mrp theo transaction md01 ,the mrp plan must not consider the stock availability,,
    for e.g.,
    if stock available = 10.
    if requirement = 20.
    if user run mrp ,,it must plan for 20 only excluding the available stock ,,,
    how to use the badi ,,,
    MD_CHANGE_MRP_DATA and method CHANGE_MDPSX_MARD,,
    Thanks in advance,

    Hello,
    The scope of planning is used to control whether the total planning run is executed on a multi-plant level
    several plants
    one MRP area
    several MRP areas
    a combination of plants and MRP areas.
    Here the planning will cover all the material which is relevant for planning in all the above given areas.
    You can carry out the total planning run for the scope of planning online or in background mode. The planning run, however, must always be started with parallel processing.
    Hope it helps. Please revert back.
    Alok Tiwari

  • Hi Experts , I am currently facing problems while running restricted version copy .. The log says 0 location products copied and that the process has has timed out. the error message is /SAPAPO/MVM_INT_SVC_CO_VER_LCW reported exception in task DP00014, th

    Hi Experts , I am currently facing problems while running restricted version copy in sap apo .. The log says 0 location products copied and that the process has timed out. the error message is " /SAPAPO/MVM_INT_SVC_CO_VER_LCW reported exception in task DP00014 " , then ending in time limit exceeded. could anyone explain why this happens. please note even if the log says 0 location products copied , in reality they have have been partially copied.
    Regards
    Jerel

    Hi, thank you for your replies, I found out few things about my servlet, and its portability
    and i have few questions, although i marked this topic as answered i guess its ok to post
    I am using javax.servlet.context.tempdir to store my files in that servletcontext temporary directory. But i dont know how to give hyperlink
    of the modified files to the user for them to download the modified files.
    What i am using to get the tempdir i will paste
    File baseurl = (File)this.getServletContext().getAttribute("javax.servlet.context.tempdir");
    System.out.println(baseurl);
    baseurl = new File(baseurl.getAbsolutePath()+File.separator+"temp"+File.separator+"files");
    baseurl.mkdirs();so i am storing my files in that temp/files folder and the servlet processes them and modifies them, then how to present them as
    links to the user for download ?
    and as the servlet is multithreaded by nature, if my servlet gets 2 different requests with same file names, i guess one of them will be overwritten
    And i want to create unique directory for each request made to the servlet , so file names dont clash.
    one another thing is that i want my servlet to be executed by my <form action> only, I dont want the user to simply type url and trigger the servlet
    Reply A.S.A.P. please..
    Thanks and regards,
    Mihir Pandya

  • STOCK OF FINISHED PRODUCT BY PIR NOT CONSIDERING WHILE TAKING MRP RUN

    DEAR SAPGURUS,
           I have finished product stock of 50 nos through planned independent requairement. now i am creating sales order for finished product but mrp run generate the planned order for finished product. I dont have planned order for finished product because material already have stock. what can i do please give solution.
    thanks.
    Regards
    Atul

    Hi Atul,
    Please describe your problem better, it's not easy to understand...
    Strategy 10 is net reqirement planning:
    - SAP considers only PIRs as requirements, SOs are not considered
    - SAP considers stock levels
    - requirements should be LSF (check in MD04)
    If you input sales order SAP won't create PldOrd for it. If you have stock and you want to create more to fulfil you SO, you have to input PIR accordingly and run MRP.
    Please clarify your problem...in a way that we may understand it.
    http://help.sap.com/saphelp_47x200/helpdata/en/60/9ea1536fbd11d191820000e8a5f6e6/frameset.htm
    http://help.sap.com/saphelp_47x200/helpdata/en/e0/71bb199c9f11d191920000e8a5f6e6/frameset.htm
    Thanks,
    Csaba

  • Error while running the Report

    Hi ,
    I am trying to run the Report in Bex Analyzer. and once I enter the value for the variable, it gives me message that "Element is not correctly define (please check query)" and when i click on the error it gives me detail message as below :
    <b><b>Diagnosis
    Additional elements that do not have the same dimension, such as quantities and amounts or amounts and ratios, are added to element Sales Qty Gallons .
    Procedure
    Check your definition.
    If you still want to use this addition, you can suppress the dimensionality of one or both subexpressions by using the 'NODIM' operator. The system then interprets this or these subexpressions as nondimensional numbers.
    In the executed query, you can use the Key Figure Definition function to analyze element Sales Qty Gallons .</b></b>
    Now the thing is I am already using "NODIM" operator to add those elements. and I m not sure why this error is coming up now because I have created this query a while ago and it wasnt giving me any error at that time but now I have make some changes into it and it;s giving me this error while running the Report. But the thing is I didnt change anything in the element for which it;s showing me error.
    Thanks,
    Naitik

    Naitik,
    There are two or more key figures in your report. They are defined by different dimensions and somewhere you have a formula with both these key figure.
    Edit your query and select the Check Query icon. It will tell you which calculation you have the problem with. Edit this calculation to see which key figures are present.
    If the formula is logically correct, best thing to do is to put a NODIM( ) on your key figures that make up the formula, and then change you formula to look at the NODIM( ) version.
    That will fix things for you,
    Regards
    Gill

  • Error while running OBIA configuration configApps.bat

    I am receiving error while running configapps.bat.
    I have the following wnvironment installed:
    64 Bit windows
    Java 6 (JDK1.6.x)
    Weblogic server 10.3.6 in software only mode
    Ran OBIEE 11.1.1.7.0 RCU utility to create BIPLATFORM and MDS schemas.
    configured OBIEE 11.1.1.7
    Installed ODI 11.1.1.7 with All components and “Skip Repository Configuration”
    Ran OBI Apps RCU to create schemas for:
    ODI Master and Work Repositories (DEV_BIA_ODIREPO)
    Oracle Business Applications Components (DEV_BIACOMP)
    Oracle Business Analytics Datwarehouse (DEV_DW)
    Update to MDS schema.
    Installed BI Apps 11.1.1.7.1
    Applied FMW Platform Patches
    Updated BIACOMP Schema with ATGLite patch scripts
    Everything was up and running until now, when i try to configure OBIA via running configApps.bat, it is getting stuck at ODI configuration.
    Also the server seems to be going to idle/suspended state every now and after 5-6 mins of startup and i see this message repeated again and again in server log :
    <Warning> <oracle.mds> <BEA-000000> < The MDS session was created by the ADF framework with a transaction key for its "single flush" feature, and the call to flushchanges is restricted to that framework. This call does not use that transaction key and although working now, will fail with an exception in future. To find the originator of the call, set the log level for logger "oracle.mds.transkey" to FINEST. Note that the ADF framework manages the MDS session created for the request so an explicit call to flushchanges should be removed>
    Has anyone encountered this issue and any idea how to resolve this.
    Appreciate any help in advance ...

    The re-install has been successful. Didnt encounter any issues in any configuration.
    However the waring still appears
    <Warning> <oracle.mds> <BEA-000000> < The MDS session was created by the ADF framework with a transaction key for its "single flush" feature, and the call to flushchanges is restricted to that framework. This call does not use that transaction key and although working now, will fail with an exception in future. To find the originator of the call, set the log level for logger "oracle.mds.transkey" to FINEST. Note that the ADF framework manages the MDS session created for the request so an explicit call to flushchanges should be removed>
    Also in the log i am getting the following errors as well in the Weblogic server log
    BEA -101020  Servelet failed with exception Java.lang.illegalstateexception: Cannot forward a response that is already committed
    Oracle.as.management.mbeans.opmn  OPMN.queryProcessStatus failed with the following exception  oracle.as.management.opmn.optic.OpticBadConnectionException: Failed to create secure socket for OPMN
    All patches were applied successfully, including weblogic one's.
    Has anyone got any idea how to resolve these issues.
    Thanks in advance.

  • Material in two plants, I run MRP with the BOM is not found in prod plant

    Hi all,
    I have plant 1020 material 12345
    Plant 1020 is the production plant for material 12345
    The material 12345 exists in plant 1070.
    The material 12345 in plant 1070 has no MRP.
    Plant 1020 material 12345 config in MM03
    MRP1 --> MRP Type = PD
    MRP1 --> MRP Controller = G03
    MRP3 --> Planning material = PLAN_1020_GR03
    MRP3 --> Planning plant = 1020
    Plant 1070 material 12345 config in MM03
    MRP1 --> MRP Type = P3
    MRP1 --> MRP Controller = 017
    MRP3 --> Planning material = empty
    MRP3 --> Planning plant = empty
    The BOM in cs11 for plant 1020 material 12345
    has 3 components
    Comp#1
    Comp#2
    Comp#3
    The Dependency is code
    TABLE TB_1020_SUPERBOM (PP_nuance_interne = $ROOT.PP_nuance_interne,
    PP_dim_billette_bom = $ROOT.PP_dim_billette_bom,
    PP_CODE_LONG_BILL = $ROOT.PP_CODE_LONG_BILL,
    pp_component_bom =$self.pp_component_bom).
    The dependency is not found because it is looking for it in the plant 1070 and not the plant 1020.
    When the MRP runs for a Delivery type stock transfer order I get
    CONFIG_1020_BILLET <---- This is the BOM item component field in CS11 in the Basic data tab
    Comp#2
    Comp#3
    instead of
    Comp#1
    Comp#2
    Comp#3
    When I run MRP for the same material, if there's no
    "Delivery based on Stock transfert orders" the MRP associates the correct components
    Hope this explains m'I situation.
    Regards!
    Curtis

    Hi,
    If you want a reply in one line, it would be SAP R/3 does not supoort this feature.
    You will have to go for APO module.
    There are few things which can be done in R/3 side, as in maintaining a scope for MRP run in OM0E, maintaining special procurement key etc etc, but all these will not do any check of stock in another plant & can only help in a very limited way if all any for your specific need.
    But SAP R/3 provides a cross plant evaluation via MD48 to know the stock & demands at all plants, this can help only for evaluation purpose.
    Hope it clarifies.
    Regards,
    Vivek

  • Error in while running a query in SAP B1

    Hi All,
    I am creating one Q-PLD so i have to run the following query. Query is working fine in SQL Server
    But while running with SAP B1 showing error 'Cant convert into varchar to small int'
    Query is
    Select (select M1.[GroupName] from OCRG M1 where M1.[GroupCode] = T2.[GroupCode]) As 'State',
    T0.[CardCode] AS 'Customer Code',T0.[CardName] AS 'Customer Name',T4.[U_SchNo] As 'Scheme Ref No',
    T1.[U_Itmgrp] AS 'Item Group',T1.[U_TAdvAmt] AS 'Actual Adv',T0.[DocDate] As 'Doc Date',
    T0.[DocNum] AS 'Invoice No.',T1.[U_QtyKgs] AS 'Qty In KG',T1.[U_CAdvRate] AS 'Advance Rate',
    T1.[U_DedAdvA] AS 'Actual Adv. Adj.',T1.[U_BalAdvA]- T1.[U_DedAdvA] As 'Balance'
    from [dbo].[OINV] T0  INNER JOIN [dbo].[INV1] T1 ON T0.DocEntry = T1.DocEntry
    INNER JOIN [dbo].[OCRD] T2 ON T0.CardCode = T2.CardCode
    INNER JOIN [dbo].[OCRG] T3 ON T2.GroupCode = T3.GroupCode
    LEFT OUTER JOIN [dbo].[@CUSTAMT] T4 ON T0.[CardCode] = T4.[U_Custcode]
    And T1.[U_Itmgrp] = T4.[U_Itemgrp]
    Where T0.[DocDate] between '[%0]' And '[%1]' And
    T0.[CardCode] between '[%2]' And '[%3]'
    And T1.[U_Itmgrp]  between '[%4]'  And '[%5]'   ' This line i am getting error
         ' If i this line will remove error will disappear or i will pass parameter directly like 'ItemGrop1'
    And T3.[GroupName] between '[%6]' And '[%7]'
    By
    Firos C

    Hello Firos,
    Now, first I assume that the t1.[U_Itmgrp] refers to the [ItmsGrpCod] in the OITM.
    I have tested this simple query in SAP Business One (Query Generator) as your query uses user defined fields I do not have in any database here.
    If this is the case you need the number associated with the item group name. This is the 'ItmsGrpCod' and you can find it in table OITB, therefore I would suggest to add this table to the query and search for the ItmsGrpNam that is the one that appear in the Item Master Data. E.g.:
    SELECT T0.[ItemCode] FROM OITM T0  INNER JOIN OITB T1 ON T0.ItmsGrpCod = T1.ItmsGrpCod WHERE T1.[ItmsGrpNam] = 'server'
    If this is the wrong assumption please consider CAST, but in this case you would need something similar to this:
    CAST ([U_PriceKG.NUMBER ]AS NUMERIC(19,6))
    Hope this helps, but if it doesn't can you please tell me what kind of values you have in U_Itmgrp and if it is written by the user or there is a formatted search?
    Thank you for your information.
    Marcella Rivi
    SAP Business One Forums Team

Maybe you are looking for