Block ifo record when Vendor rating below accp limit

Dear All,
Can a QM Info for a vendor be blocked automatically (by using any enhancement) when the Vendor Quality rating goes below the certain limit.?
Kindly Suggest.
Regards,
Anil

Yes and no.
You can use the Q-info record (QI01/QI02/QI03) to release vendors for specific materials.   You can use QI06 to mass maintain these.  In the info record you can set specific blocks.  For instance, you can block any new PO's for the vendor/material combination.
The blocks however are not automatically set.  Typcially, someone runs the vendor evaluation on a regular basis (ME61 or ME63) and reviews the poor performing vendors.  These vendors can then be blocked using the QI06 transaction as explained above.
Vendor evaluation is not a dynamic value.  It is only changed when the vendor evaluation program is run.  So their Quality score would not change or 'drop' on a day-to-day basis unless some one ran vendor evaluation on a day-to-day basis.  (ME6G sets up a batch job to do this and can be run daily).
To make it automatic, a program would need to be written to look up the vendor scores after the vendor evaluation job was run and then set the block in the quality info record for vendors with a score below a certain value.
Be careful.  If you have materials that are primarily single-sourced, you could winid up blocking your only or primary vendor.  This can also be especially true for materials that are purchased on an infrequent basis.  If you only order twice a year, one failed inspection can swing the Q-score down a lot.  Thus possibly blocking your vendor.
Craig

Similar Messages

  • Supressing creation of BP record when creating Customer / Vendor in MDG.

    Hi MDG Experts
    As far as i understand the Business Partner record is always created when Vendor / Customer record(s) are created. This is true even when the Lean Vendor / Customer scenario is setup.
    Is it possible to suppress the creation of Business Parter record when Vendor / Customer record(s) are created ? If this possible, how can it be achieved ?
    Thanks in advance.
    Regards
    Neelesh

    Hello,
    No, you can't. BP will always be created first and then a corresponding supplier/customer will be created depending on CVI configurations.

  • Cursor Jumping to last record when query mode for Multi-record block.

    I have a multi-record block. the seq field has this validation to check that there should not be a gap
    in sequence for S_type and cer_dl field.The program unit is as below.
    PROCEDURE seq_validation IS
    --Validation to check that there is no gaps in sequence for S_TYPE and cer_dl fields
    l_value_to_check varchar2(100);
    l_seq_found number;
    l_curr_sequence number;
    l_new_value varchar2(100);
    l_found boolean:=FALSE;
    l_new_set boolean := FALSE; --s_type and cer_dl are different from previous set.
    begin
    if trim(:b1.s_type) is not null
    or trim(:b1.cer_dl) is not null
    then
    -- Program continues here only if all the items are not null
    -- Get information from record that needs to be validated
    l_value_to_check := trim(:b1.s_type) || ':'|| trim(:b1.cer_dl) ;
    l_curr_sequence := :sequence;
    if :SYSTEM.CURSOR_RECORD = '1' then
    ---to check sequence is entered as 1 in the first record
    message('Error:Sequence should start with 1');
    raise form_trigger_failure;
    end if;
    go_item('b1.XYZ');
    else
    FIRST_RECORD;
    while :SYSTEM.LAST_RECORD != 'TRUE'
    loop
    l_found := FALSE;
    l_new_value := trim(:b1.S_type) || ':'|| trim(:cer_dl) ;
    if l_new_value = l_value_to_check then --
    l_new_set:= FALSE;
    l_seq_found := :seq;
    if l_seq_found >= l_curr_sequence then
    go_item('b1.seq');
    l_new_set := FALSE;
    elsif l_seq_found < l_curr_sequence - 1 then
    go_item('b1.sequence');
    l_found := FALSE;
    elsif l_seq_found = l_curr_sequence - 1 then
    l_found:= TRUE;
    go_item('b1.xyz); --go to next item
    end if;
    else
    l_new_set := TRUE;
    end if;
    NEXT_RECORD;
    end loop;
    if l_new_set then
    go_item('b1.xyz'); -- go to next item
    else
    if not l_found then
    message('Error:Sequence should be in order.');
    go_item('b1.seq');
    raise form_trigger_failure;
    end if;
    end if;
    go_item('b1.xyz'); ---go to next item
    end if;
    end if;
    end;     
    In the insert mode its working fine(unless you gurus feel to change to make it more perfect.
    When I say enter-query and put 'IAS' in the s_type field and then do a execute query it brings all the records of 'IAS'.
    Now as I want to update the records, and when I navigate across field(s_type,cer_dl,Seq,xyz) using tab and move the cursor down on second
    record(IAS N 2 N), what happens is when I navigate to sequence field the cursor jumps to LAST RECORD( IAS Y 3 N ) of LAST field XYZ.
    I am putting the sample record
    s_type cer_dl seq xyz
    IAS N 1 N
    IAS N 2 N
    IAS N 3 N
    IAS N 4 N
    IAS Y 1 N
    IAS Y 2 N
    IAS Y 3 N
    The cursor moves to last record --IAS -Y -3-N when I tab across the second record.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

    When I say enter-query and put 'IAS' in the s_type field...For your validation to work you must not allow users to enter records in the middle of a block, clear records from the block or query specific records. If you allow the users to enter a query then you are allowing 2 of the rules to be broken.

  • Automatic Creation of Employee Vendor record when hired in HR

    Hi Gurus,
    Any assistance in Automatic creation of Employee vendor record when the employee is hired in HR master data.
    Thanks in Advance
    BLITZZ

    Hi,
    Use the t.code: PRAA. Give reference to an existing employee vendor.
    Or, you can also create a batch job that runs this daily. Before that you need to create a reference employee vendor and input the most common fields in it (like, Recon Account, Payment method, etc.).
    Regards,
    Kiron Kumar T.

  • Is it standard behavior for VL10A/table VEPVG to show two records when a Sales Document has been blocked?

    Hi Experts,
    Is it standard behavior for VL10A to show two records when a Sales Document has been blocked? Their only difference is the field Delivery Block. In VL10A, the first record has a delivery block of BLANK, the second has 99.
    Here's how to replicate the issue.
    Create sales order.
    When you check VL10A, the Sales document is there.
    Change sales order field (RSD) in VA02, Save.
    When you check VL10A, there are now two records, one has a blank delivery block, the other has 99.
    The expected result here is that after changing in VA02, there will be only 1 record in VL10A and it should have delivery block of 99.
    Assumptions:
    1. We know that VL10A retrieves its records from VEPVG. The problem is, in VEPVG, delivery block is a key field. So I think that during VA02, when the delivery block of 99 is assigned, this creates a record in VEPVG instead of updating the existing one. Is this standard behavior, and are my assumptions correct?
    Thanks in advanced experts. Appreciate your prompt response,
    Jack

    Hello Jack,
    This is the standard behavior. When I check in our system, I too can see two entries but with different good issue date and delivery date and the block is specific to good issue date, delivery date.
    So there is no problem in it. try to give the delivery date which includes two table entries delivery date and execute the transaction VL10A.
    Regards,
    TP

  • Losing unprocessed records when blocking queue entries are serialized

    Hi,
    I am developing a batch framework using the Java 1.5 thread APIs. We have a requirement to save the state of the batch processes when it terminates abnormally or when it is killed for any reason. I have implemented this functionality using shutdown hooks.
    I have initialized the thread pool with two thread instances. Now, while things are behaving as expected, I am losing upto 2 records when I kill the batch process. These are those 2 records which were being processed by the threadpool threads when the kill signal was sent.
    Is there a mechanism to prevent the batch job from exiting before these two threads have processed finishing or maybe keep these 2 threadpool tasks in the pool till they have completed gracefully. I.e. remove these tasks from the threadpool task queue when have they have finished execution
    Regards,
    Hitesh

    ExecutorService.shutdown()
    ExecutorService.awaitTermination()
    One would expect the jobs that are currently executing to have been already removed from the queue.

  • Role VN not defined in master record for vendor 1000000465

    dear alll,
    while preparing PO, with one vendor system is giving the below message and
    when observed the vendor master data,last view vendor partner roles not updated.
    If i go ahead with the same vendor, after giving tax code, taxes tab not getting open to calculate taxes
    Despite,condition records  are there  for the respective condition types with the key combination material,vendor,plant why system is not picking taxes?
    Role VN not defined in master record for vendor 1000000465
    Message no. ME329
    Diagnosis
    The vendor may only operate as a partner for other vendors (e.g. as ordering address or invoicing party), not as the vendor who actually fulfills the order.
    Procedure
    u2022     If this is a warning message, you can ignore it.
    u2022     If this is an error message add partner role VN to the vendor master record:
    Perform function
    some times taxes getting calculated properly but in print priew, tax related informaton(values) missing.
    what might be the possible reason? please suggest the way

    Message no. ME329
    Check these threads
    [Re: steps to create PO for service order |Re: steps to create PO for service order]
    [How to change the wording of System Messages?|How to change the wording of System Messages?]
    thanks
    G. Lakshmipathi

  • How to deactivate/ignore R/3 info records when creating Shopping Cart?

    Hi all and thanks for reading...
    We have the requirement of ignoring/deactivating R/3 info records when creating Shopping Carts SRM , so that no Vendor is proposed in transactions BBPSC01/BBPSC02.
    At the moment, when info records exist in backed, system is proposing vendor and other data and we want them to be completely ignored, both in classic and extended classic scenarios.
    How can we accomplish that? Is it possible to use BBP_SOS_BADI or is this BADI only valid for SRM local sources of supply?
    Has anybody had the same problem and solved it before?
    Thanks in advance for your help, regards
    David

    Hi  David
    Inforecord  is only source of supply for classic scenario only.
    Find and Check Sources of Supply
    Use
    With the Business Add-In BBP_SOS_BADI, you can search for and check sources of supply according to your own rules. These sources of supply include contracts, vendor list entries and product linkages. For this, the customer fields of the shopping cart or purchase order are transferred to the BAdI.
    Standard settings
    The BAdI provides the following methods:
    1. BBP_SOS_INDEX_UPDATE_CHECK
    Use: Check and update contract items in the source of supply table.
    2. BBP_SOS_SEARCH
    Use: Search for sources of supply according to your own rules.
    3. BBP_SOS_CHECK
    Use: Check and filter the sources of supply found by the standard search according to your own rules.
    4. BBP_SOS_PD_CHECK
    Use: Carrying out your own additional checks when creating a shopping cart document item with an assigned contract.
    Activities
    Implement the BAdI if you wish to determine or check sources of supply according to your own rules.
    See also
    Implementation
    As prasanna mentioned - do you want disable both sides or only one side .
    Muthu

  • How to block a record.

    hi
    1)
    i heard about blocking a record in the DAtaBase.
    may i know how to do this...
    2)
    i am working into plsql developer at backend. my project using front end as .Net and back end as Oracle 10g...
    when i am creating SP's at database side, i am giving input and output to Front end peoples...this is the way.
    now my problem is.. SP giving correct output at front end.. while deploying my modules at client side, they didnt get result..???
    a) front end peoples have checked their code, it was correct.
    b) at backend output is coming correctly, and data is valid in database,
    But at client side we didnt get output for one particular field (ListItem)..???

    The question is so vague.
    One thing I understand. If you are getting an output on the backend test (pl/sql developer or some other IDE), and you are not getting the output on the front end (.NET in this case), then, obviously there is a difference in the environments.
    Your (along with your front-end developers) trick is to find what the difference in the env's is. You can put some debugging in the code to make sure the procedure is even getting called from the front end... Good luck.

  • CAN WE MAINTAIN VENDOR RATING IN Q.M

    Hi GURUS,
    Is it possible to maintain vendor rating in Q.M.
    We have 5 Quality parameters for rating each vendor for particular material,with these parameters my client wants to rate the vendors.
    Regards
    Ram

    Hi Shyamal,
    Our scenario is like this,we have five materials for which we have 5 M.I.cs like Fe,Moisture,Fines,Carbon and Sulpur. for these M.I.Cs we have weightage as 50,20,10,10,10 respectively.
    Foe Example M.I.C Fe the weightage is as follows.
    Fe             weightage
    >= 87           =   50
    86 to 86.9     =   45
    85 to 85.9     =   40
    < 84             =   25
    the above procedure is followed for the other M.I.Cs and based on the weightage all five M.I.Cs a vendor rating is decided as follows
    GOOD                =90 AND ABOVE
    SATISFACTORY = 75 TO 89
    POOR                = BELOW 75
    How can we map this map this scenario,
    Regards
    Ram
    Edited by: RAMKUMAR WARIYAR on Nov 5, 2008 3:17 PM

  • Block zero quantity when creating Inventory Transfer

    Hi all,
    does anyone know how to block zero quantity when creating inventory transfer?
    for example: I have zero quantity in warehouse A. Then I want to transfer it to warehouse B. The system accept that. So, when I check that item in warehouse A, the in stock column become negative. How I can protect it?
    please help me. it's very urgent.
    thanks
    sisca

    Go to Administration > System Initialization > Document Settings > General Tab
    Check Manage Inventory nu Whse and also check Block negative inventory. Read details below of their functionality.
    Manage inventory by whse
    Defines whether the check is performed for the warehouse selected in the document row. If you select the checkbox, the system checks the minimum inventory level in the warehouse that was selected for the item when the sales document was entered.
    If the transaction causes the inventory level in that warehouse to fall below the minimum inventory level, a warning message appears even if the total available inventory of the item is greater than the minimum warehouse quantity. If you do not select this checkbox, the system checks the total available inventory in all warehouses where this item is stored.
    You can also define automatic notification for a specific user when the inventory level falls below the minimum level. A purchase transaction can then be initiated.
    Block negative inventory
    Select to block documents that would cause the level of inventory to fall below zero. If you deselect the checkbox, the message “Negative inventory usage is not in accordance with accounting rules. Are you sure you want to enable negative inventory usage?”
    If you select Manage inventory by whse and Block negative inventory, SAP Business One calculates the block per warehouse. However, if the item is not handled by a warehouse and you do not select Manage inventory by Whse, the block is calculated for all the warehouses.

  • How to get Value of a item of first record when current record is second

    How to get Value of a item of first record when current record is second in Form6i ?
    get_item_instance_property dose not allow to get value.

    Gerd,
    You're right, there are several other triggers that must be coded, but I was responding to Steve's statement about Inserting or deleting records from the multi-record block. For the record, I use the following to manage a Record Group:
    * When-New-Block-Instance - Initialize the RG
    * block Post-Query - populate the RG
    * When-Create-Record - add new record to RG
    * When-Remove-Record - remove record from RG
    * block When-New-Item-Instance - capture previous value of the item or row
    * When-Validate-Item - Item specific Insert, Update, Delete of values in the RG
    There are a few other places as well, but these are the minimum. It might seem like a lot of code, but then again, I don't use this solution for every multi-line block. Like all tools, you use the right tool for the job. :-)
    Craig...

  • Role VN not defined in master record for vendor

    Hi Experts,
    I have created new partner role (Z1) coping VN and I am using only that in Vendor master. When I create a PO, it still asks for partner role VN to be defined in vendor master. I have checked in partner schema's and the partner role VN is not mandatory. I want to use only customized role Z1 in PO's. Please let me know why the system throws the message "Role VN not defined in master record for vendor XXXX" ?
    Thanks and Regards,
    Venkata Prasanna R

    if you use partner functions, then VN is a mandatory role, regardless if it is set optional.
    There is some coding which only checks on VN partner.
    E.g. in message processing like described in OSS Note 457497 - FAQ: Message processing in purchasing:
    In Customizing, I have configured the partner role OA (ordering address) for message determination and I have assigned this role to the vendor master. However, why is message determination performed for the corresponding vendor (role VN) and not the ordering address (role OA)?
    Answer:
    In the purchase order, correct message determination can be processed only with partner role VN (vendor). If you select the "New partner role determination" (NEUPR) checkbox in Customizing of the message determination for purchase orders, the system proposes all partners for message determination and it transfers the role VN (vendor).
    *If you do not select this checkbox, only the role OA (ordering address) is used for message determination, but the role is changed to VN (vendor) for program-technical reasons.
    It is a restriction of the SAP Basis components that faxes can be sent to vendors only*.

  • Vertical scrollbar not showing all the records when I scroll down.

    Vertical scrollbar not showing all the records when I scroll down.
    Using Oracle forms 10g , operating system windows
    I have two fields with number of items dispayed = 15.
    I have a vertical scroll bar with them. There are 34 records in the table but the scrollbar only shows 15 records.
    Here are the properties for block / scrollbar.
    WORK_CATEGORY
    - Subclass Information                           
    - Comments                                       
    * Navigation Style                                Same Record
    - Previous Navigation Data Block                 
    - Next Navigation Data Block                     
    - Current Record Visual Attribute Group          
    - Query Array Size                                0
    - Number of Records Buffered                      0
    * Number of Records Displayed                     60
    * Query All Records                               No
    - Record Orientation                              Vertical
    * Single Record                                   No
    - Database Data Block                             Yes
    - Enforce Primary Key                             No
    - Query Allowed                                   Yes
    - Query Data Source Type                          Table
    * Query Data Source Name                          WORK_CATEGORY
    * Query Data Source Columns                      
    * Column Name                                   JOB_TYPE
    * Column Type                                   VARCHAR2
    - Column Type Name                             
    - Parent Column                                
    * Length                                        30
    * Precision                                     0
    * Scale                                         0
    * Mandatory                                     Yes
    * Column Name                                   WORK_CATEGORY
    * Column Type                                   VARCHAR2
    - Column Type Name                             
    - Parent Column                                
    * Length                                        30
    * Precision                                     0
    * Scale                                         0
    * Mandatory                                     Yes
    - Query Data Source Arguments                    
    - Alias                                          
    - Include REF Item                                No
    * WHERE Clause                                   
    * ORDER BY Clause                                 job_type
    - Optimizer Hint                                 
    - Insert Allowed                                  Yes
    - Update Allowed                                  Yes
    - Locking Mode                                    Automatic
    - Delete Allowed                                  Yes
    - Key Mode                                        Automatic
    - Update Changed Columns Only                     No
    - Enforce Column Security                         No
    - Maximum Query Time                              0
    * Maximum Records Fetched                         0
    - DML Data Target Type                            Table
    - DML Data Target Name                           
    - Insert Procedure Name                          
    - Insert Procedure Result Set Columns            
    - Insert Procedure Arguments                     
    - Update Procedure Name                          
    - Update Procedure Result Set Columns            
    - Update Procedure Arguments                     
       Don't know where am I going wrong. I'll really appreciate if you can help me in this.
    Thanks.
    Edited by: 831050 on Sep 14, 2011 8:05 AM

    One of the items is a list item.. here are it's properties:
    * Name                                          JOB_TYPE
    * Item Type                                     List Item
    - Subclass Information                         
    - Comments                                     
    - Help Book Topic                              
    - Enabled                                       Yes
    * Elements in List                             
    * Label                                      
    * List Item Value                             LIST20
    * List Style                                    Combo Box
    - Mapping of Other Values                      
    - Implementation Class                         
    - Case Restriction                              Mixed
    - Popup Menu                                   
    - Keyboard Navigable                            Yes
    - Mouse Navigate                                Yes
    - Previous Navigation Item                     
    - Next Navigation Item                         
    - Data Type                                     Char
    - Data Length Semantics                         Null
    - Maximum Length                                30
    - Initial Value                                
    * Required                                      Yes
    * Copy Value from Item                         
    - Synchronize with Item                        
    - Calculation Mode                              None
    - Formula                                      
    - Summary Function                              None
    - Summarized Block                             
    - Summarized Item                              
    - Current Record Visual Attribute Group        
    - Distance Between Records                      0
    * Number of Items Displayed                     15
    - Database Item                                 Yes
    * Column Name                                   JOB_TYPE
    - Primary Key                                   No
    - Query Only                                    No
    - Query Allowed                                 Yes
    - Insert Allowed                                Yes
    - Update Allowed                                Yes
    - Update Only if NULL                           No
    - Visible                                       Yes
    * Canvas                                        CANVAS2
    - Tab Page                                     
    * X Position                                    47
    * Y Position                                    137
    * Width                                         187
    * Height                                        18
    - Visual Attribute Group                        DEFAULT
    - Prompt Visual Attribute Group                 DEFAULT
    - Foreground Color                             
    * Background Color                              white
    - Fill Pattern                                 
    - Font                                         
    * Font Name                                     Tahoma
    * Font Size                                     10
    * Font Weight                                   Demilight
    * Font Style                                    Plain
    * Font Spacing                                  Normal
    * Prompt                                        Job Type
    - Prompt Display Style                          First Record
    * Prompt Justification                          Start
    * Prompt Attachment Edge                        Top
    - Prompt Alignment                              Start
    * Prompt Attachment Offset                      10
    * Prompt Alignment Offset                       0
    - Prompt Reading Order                          Default
    - Prompt Foreground Color                      
    - Prompt Font                                  
    * Prompt Font Name                              Tahoma
    * Prompt Font Size                              10
    * Prompt Font Weight                            Bold
    * Prompt Font Style                             Plain
    * Prompt Font Spacing                           Normal
    - Hint                                         
    - Display Hint Automatically                    No
    - Tooltip                                      
    - Tooltip Visual Attribute Group               
    - Direction                                     Default
    - Initial Keyboard State                        Default
    - Keyboard State                                Any
        

  • Blocking certain records

    Hi!
    i have a little problem like, i want to block certain records in USER1, so that other user should not see those blocked records when they issue SELECT STATEMENT from USER1,USER2 . like example (blocking record 1,2 in user USER1) . USER2,USER3 should see only 3,4 if they issue select statement.
    USER1(table name TEMP)
    A B
    1 cat
    2 rat
    3 mat
    4 hat
    USER2 (select * from USER1.TEMP)
    A B
    3 mat
    4 hat
    USER3 (select * from USER1.TEMP)
    A B
    3 mat
    4 hat
    hope its clear.
    thanks
    viq.

    Hi!
    I got the solution . i have applied VPD.
    thanks

Maybe you are looking for