Invoice verification only after quality acceptance

The GR stage to Invoice verfication as detailed below:
1.  Once material comes in, the store will check the documents and check the PO and prepare GRN.
2.  Then, Quality will check the quantity and quality of the item and make necessary QM entry for acceptance / Rejection in the system.
3.  Finance does the Invoice verfication and makes the payment depending on the due date.
However, a serious problem arises in this present process at Invoice verfication stage ie., suppose the quality makes delay in checking the quantity and quality of the item and subsequent acceptance / Rejection, there is a scope for making the payment to the vendor even for rejected items since the system allows you to process invoice verification for GRN quantity and make the payment for the same. It is very difficult to recover from the vendor towards rejected items when once the payment is done. 
Therefore, we need some control in the system at Invoice verfiication stage that the system should  not allow us to verify the Invoice for GRN quantity instead the system should allow us to make invoice verification only for accepted quantity by quality.
Is there any method to do this ?

Hi,
If the material is in quality system should not allow to post Invoice verification. Is it your requirement ? Pls correct me if im wrong.
The above requirement can achieve with standard SAP settings. You need to activate QM settings for the plant.
In material master select the Quality Management view, in procuremen data, in QM control key field, select 0007(i.e.Delivery release, Invoice block).
If the material is in quality you cant post invoice.
reg
Durga
*Assign points if the info is useful

Similar Messages

  • Restrict for invoice verification up to Quality accept

    Hi,
    My Scenario 
    Po qty is 100   and i am doing Goods Receipt 100 qty  after posting inspection Lot is creating
    But here If i gone to Invoice verification it is accepting without Quality lot clearing
    i want to Restrict for invoice verification up to Quality accept 
    after  accepting quality only it should go for invoice
    it is possible ??????
    Manjunath

    Hi
    yes possible ,check following link
    [MIRO before Quality lot clearance;
    Regards
    kailas Ugale

  • Block Invoice verification as per quality result

    Hello,
    I made GRN , lot gets generated. not cleared by quality.
    still I can do the invoice verification.
    Can I restrict this ? so i can not pass invoice before quality results and only ok quantity has to appear for invoice verification.
    If such facility is available kindly advice.
    Regards,
    santosh joshi

    Dear Santhosh Joshi,
    Check in IMG (Transaction SPRO) under :
    Materials Management -> Logistics Invoice Verification -> Invoice Block
    You can implement a proper BAdi/Enhancement if you cannot configure your scenario:
    BAdi:
    BAdI MRM_RELEASE_CHECK for additional checks before invoices are released, in other words, you can restrict the list of invoices to be released by defining your own criteria.                       
    The following SAP enhancements are available for maintaining the customer exits in Invoice Verification:                        
    MM08R001        ERS (conventional Invoice Verification)            
    MM08R002        Tolerance checks                                   
    MRMH0001        ERS (Logistics Invoice Verification)               
    MRMH0002        EDI invoice receipt (Logistics Invoice Verification)
    MRMH0003        Revaluation (Logistics Invoice Verification)       
    When processing an invoice, the R/3 System checks each item for variances between the invoice and the purchase order or goods receipt. The different types of variances are defined in tolerance keys.                                                                               
    The system uses the following tolerance keys to check for variances: 
    AN: Amount for item without order reference                        
    If you activate the item amount check, the system checks every line item in an invoice with no order reference against the absolute upper limit defnied.
    AP: Amount for item with order reference                           
    If you activate the item amount check, the system checks specific line items in an invoice with order reference against the absolute upper limit defined. Which invoice items are checked depends on how you configure the item amount check.
    BD: Form small differences automatically                           
    The system checks the balance of the invoice against the absolute upper limit defined. If the upper limit is not exceeded, the system automatically creates a posting line called Expense/Income from Small Differences, making the balance zero and allowing the system to post the document.
    BR: Percentage OPUn variance (IR before GR)                        
    The system calculates the percentage variance between the following ratios: quantity invoiced in order price quantity units : quantity invoiced in order units and quantity ordered in order price quantity units : quantity ordered in order units. The system compares the variance with the upper and lower percentage tolerance limits.     
    BW: Percentage OPUn variance (GR before IR)                        
    The system calculates the percentage variance between the following ratios: quantity invoiced in order price quantity units: quantity invoiced in order units and goods receipt quantity in order price quantity units : goods receipt quantity in order units. The system compares the variance with the upper and lower percentage limits defnied.   
    DQ: Exceed amount: quantity variance                               
    If a goods receipt has been defined for an order item and a goods receipt has already been posted, the system multiplies the net order price by (quantity invoiced - (total quantity delivered - total quantity invoiced)).
    If no goods receipt has been defined, the system multiplies the net order price by (quantity invoiced - (quantity ordered - total quantity invoiced)).
    The system compares the outcome with the absolute upper and lower limits defined.                                                    
    This allows relatively high quantity variances for invoice items for small amounts, but only small quantity variances for invoice items for larger amoutns.
    You can also configure percentage limits for the quantity variance check. In this case, the system calculates the percentage variance from the expected quantity, irrespective of the order price, and compares the outcome with the percentage limits configured.        
    The system also carries out a quantity variance check for planned delivery costs.
    DW: Quantity variance when GR quantity = zero                      
    If a goods receipt is defined for an order item but none has as yet been posted, the system multiplies the net order price by (quantity invoiced + total quantity invoiced so far).                        
    The system then compares the outcome with the absolute upper tolerance limit defined.                                           
    If you have not maintained tolerance key DW for your company code, the system blocks an invoice for which no goods receipt has been posted yet. If you want to prevent this block, then set the tolerance limits for your company code for tolerance key DW to Do not check. 
    KW: Variance from condition value                                  
    The system calculates the amount by which each delivery costs item varies from the product of quantity invoiced * planned delivery costs/ planned quantity. It compares the variance with the upper and lower limits defined (absolute limits and percentage limits).      
    LA: Amount of blanket purchase order                               
    The system calculates the sum of the value invoiced so far for the order item and the value of the current invoice and compares it with the value limit of the purchase order. It then compares the difference with the upper percentage and absolute tolerances defined.                                                                               
    LD: Blanket purchase order time limit exceeded                     
    The system determines the number of days by which the invoice is outside the planned time interval. If the posting date of the invoice is before the validity period, the system calculates the number of days between the posting date and the start of the validity period. If the posting date of the invoice is after the validity period, the system calculates the number of days between the posting date and the end of the validity period. The system compares the number of days with the with the absolute upper limit defined.                                                                               
    PP: Price variance                                                 
    The system determines by how much each invoice item varies from the product of quantity invoiced * order price. It then compares the variance with the upper and lower limits defined (absolute limits and percentage limits).
    When posting a subsequent debit/credit, the system first checks if a price check has been defined for subsequent debits/credits. If so, the system calculates the difference between (value of subsequent debit/credit + value invoiced so far) / quantity invoiced so far * quantity to be debited/credited and the product of the quantity to be debited/credited * order price and compares this with the upper 
    and lower tolerance limits (absolute limits and percentage limits).
    ST: Date variance (value x days)                                   
    The system calculates for each item the product of amount * (scheduled delivery date - date invoice entered) and compares this product with the absolute upper limit defined. This allows relatively high schedule variances for invoice items for small amounts, but only small schedule variances for invoice items for large amounts.                                                                               
    VP: Moving average price variance                                  
    When a stock posting line is created as a result of an invoice item, the system calculates the new moving average price that results from the posting. It compares the percentage variance of the new moving average price to the old price using the percentage tolerance limits defined.                                                           
    Hope this will resolve your issue.
    Regards,
    Naveen.

  • Service PO  - Invoice verification before Service Entry / Acceptance

    Hi SAP Gurus ,
    I have following question ,
    I am creating a Service PO with A/c assignment category K & Item category D .
    system automatically proposes GR Based IV tick for this combination .
    I want to post the invoice first & then do the service entry sheet / acceptance etc.
    but it is not possible as i get an error message as follows
    " Valuated Goods receipt without GR Based IV is not allowed for external services "
    I tried changing message as a warning but no use .
    Is it possible to achieve Invoice - service entry sequence for this type of PO .
    Can anyone pls. answer this ?
    Thanks ,
    Prasad G

    Hi
    As per standard service entry sheet has to be accepted before invoice verification is done.
    If you want invoice to be done prior then uncheck gr-based po field in purchase order and try posting invoice.
    hope it helps.

  • Invoice verification number ranges

    Hi
    After processing a payment in MIR7, document number 5100519088 was assigned. When user processed the next payment 51000519063 was assigned. Can some one explain how these document numbers are being allocated, Normally the documents numbers are allocated in a sequential order..
    Checked in ILV number ranges, for all document types it is taking only one number ranges i.e 51.
    For creation and reversal invoice document it also taking same number ranges i.e 51
    Please help me to understand why it is not taking number ranges sequence wise ( only for 6 invoice documents)
    Thanks
    Andappa

    Hi,
    there can be various reasons for the gaps in invoice numbering.
    Please review the following notes in relation to gaps in numbers used:
    62077   Info: Internal number assignment is not continuous
    193020  Invoice verification: Gaps in number assignment
    175047  Causes for FI document number gaps (RF_BELEG)
    Main reason for numbering gaps is buffering. This is also described
    in attached note 62077.
    Document numbers can get lost in invoice verification if after choosing
    the 'Post' function (F11 or Ctrl+S) the system generates an error
    message or a termination message. In this case instruct users to pay
    attention to whether the system generates terminations or error messages
    after choosing post (F11 or Ctrl S). Ask them to note the message ID and
    the numbers, preferably together with the time. It is worth discovering
    a procedure, peculiar to your company or system configuration, that
    causes the system to generate other error or termination messages after
    posting (that is after number assignment). This should not normally be
    the case. All this is explaind in note 193020.
    Best Regards,
    Arminda Jack

  • Invoice verification related

    is it possible to do automatic Invoice verification right after GR ??

    1) You must maintain the settings in Customizing for purchasing (for example, invoicing plan type, date categories, date descriptions, and date sequence proposals). The related path is IMG ---> Material Management ---> Purchasing ---> Purchase Order ---> Invoicing Plan ......
    2) The Purchasing document with FO Document Type (Framework Order) must be used. This document type requires that a validity period be entered in the PO header. This specification is adopted in the invoicing plan, provided that this has been predefined in Customizing for the relevant invoicing plan type.
    3) The purchase order item must have an account assignment.
    4) The Logistics Invoice Verification must be used.
    5) The vendor must have agreed to use the automatic invoice creation facility (since we will use automatic settlement to create the invoice). In this case, the 'AutoEvalGRSetmtDel.' indicator must be flagged in the vendor master record.
    Furthermore, once Purchase Order is created with order type FO, ensure that the indicators for GR/IR control have been set correctly on the item detail screen. The Goods Receipt indicator may only be set in combination with the Goods Receipt Non-Valuated indicator. The Invoice indicator must be set. For the automatic creation of invoices, the ERS (Evaluated Receipt Settlement) indicator must be also set. A further prerequisite for automatic settlement is that a tax code must be entered in the purchase order.

  • Excise is not calculate in invoice verification

    Dear All,
    I have one issue.
    We have create purchase order for project with account assignment category Q.
    We put excise (10.30) & Vat 15% in purchase order.
    In purchase order all value calculate properly. Good Receipt created against purchase order.
    Now we create invoice verification againat purchase order.
    but at time of invoice verfication creatoin excise value in not calculate properly in invoice verification, only 15% vat calculate in invoice verification.
    All excise detail(J1id) has been maintain for material & vendor master and i have also check tax code in FTXP. All are well maintain.     
    We have capture excise invoice at the time of good receipt creation.
    But Excise value is not calculate
    Regards,
    Mahesh Wagh

    Hi,
    If the excise invoice is not posted (Part-II), then it will not flow in MIRO.  Pls check same. 
    You may even check whether the capter id assigned to the material is extended to new excise calculation period.
    Regards,

  • Invoice Verification MIRO

    Dear All,
    This is about invoice verification block after MIRO posting-
    In PO we have set it as 2 way match, once the PO is equal to Invoice verification then the system should not put any payment block. But if it doesnt match the value of PO to IV then the system should put invoice verifcation block (R) in the accounting document.
    Here, whatever we post that is whether the PO value is matching or not the invoice verification block (R) is appearing in the accounting document. Does any one gone through similar issue....
    I want to know how this can happen?
    Checked validations but nothing that sort appears.....is there a way to find out how this happens....
    Thanks to all in advance.

    Hello
    I do not know of any BAPI. But you can set an automatic block up through your payment terms.
    Check the following customizing path for this:
    Financial Accounting
    ->Accounts Receivable and Accounts Payable
       ->Business Transactions
         ->Incoming Invoices/Credit Memos
           ->Maintain Terms of Payment
    Select the details for the payment term and check for the indicator there to set the default block key.
    Hope this helps
    Ray

  • DUPLICATE INVOICE VERIFICATION CHECKL

    Hi
    How to set control for duplicating invoice verification.
    Like the same Delivery note or the Freight passing twice to be checked by an error message
    Please help
    Krishna

    SPRO-MM-invoice verification-incoming invoice-Set Check for Duplicate Invoices                                                                               
    In this step, you can configure for each company code if the system is to check for duplicate invoices when you enter invoices.                                                                               
    This check should prevent incoming invoices being accidentally entered and paid more than once.                                                                               
    You can choose whether to activate or deactivate the check criteria of company code, reference document number and invoice date for each company code. The more criteria that you activate, the lower the probability of the system finding a duplicate invoice. The Accounting documents are checked first, followed by documents from Logistics Invoice Verification (only incorrect invoices or those entered for verification in the background).                                                                               
    When checking duplicate invoices, the system compares the following attributes in the standard system:                                                                               
    Vendor                                                                               
    Currency Company code                                                                               
    Gross invoice amount Reference document number                                                                               
    1. Invoice date If the system finds an invoice that matches all                         
           attributes, the system                                                               
           -  displays a customizable message.                                                  
           -  If you are entering credit memos, subsequent debits, or subsequent                
           -  credits, the system does not check for duplicate invoices.                        
           -  The exception is the Argentina country version, where the system                  
              checks                                                                               
    -  for duplicate invoices and credit memos.                                          
           -  If a previously processed document is later cancelled and then                    
              entered                                                                               
    -  again, no message is displayed.                                                                               
    Requirements                                                                               
    The system only checks for duplicate invoices in Materials Management                                                                               
    if you specify a reference document number when entering the invoice.                                                                               
    In Customizing (IMG) for Invoice Verification, you can specify that the                                                                               
    system check the following attributes                                                                               
    Reference document number                                                                               
    Invoice date                
       Company code                                                                               
    Because there are fewer attributes to check, it is more likely that the system will find a duplicate invoice.                                                                               
    Standard settings                                                                               
    All check criteria are activated in the standard system.                                                                               
    Example                                                                               
    The following document has been entered and posted:                                                                               
    Reference document number: 333                                                                               
    Invoice date: 28.04.00                                                                               
    Gross invoice amount: 100,00                                                                               
    Currency: EUR                                                                               
    Vendor: Wolf                                                                               
    Company code: Hamburg                                                                               
    The settings for checks for duplicate invoices in Customizing have                                                                               
    been maintained as follows:                                                                               
    The field reference document number and company code are not selected.                                                                               
    This means that these attributes will not be checked. Now enter the                                                                               
    following invoice:                                                                               
    Reference document number: 334                                                                               
    Invoice date: 28.04.00                                                                               
    Gross invoice amount: 100,00                                                                               
    Currency: EUR                                                                               
    Vendor: Wolf                                                                               
    Company code: Berlin                                                                               
    Result                                                                               
    By entering the reference document number and entering an invoice,it is possible to check for duplicate invoices.                              
    The reference document number and the company code contain different data than the invoice you entered. These attributes are not checked because you have deselected them in Customizing.                                                                               
    All other attributes are equal. The system displays a message telling you that a duplicate invoice has been found.                                                                               
    If, for example, you had selected the reference document number in Customizing, the system would check this and recognize that this invoice is different to the previously entered invoice. The system would not then display a message.

  • Invoice verification done doubble times agaisnt  one PO

    Hello,
    SAP has Verified , two invoices two times. Please suggest me.
    I m sure the vendor master has no tick in the check doubble invoice Indicator., what could be the other Reason?
    Best Regards,
    Sridhar.k
    Siemens

    Img>>MM>>Incoming Invoice>>Set Check for Duplicate invoices
    Set Check for Duplicate Invoices
    In this step, you can configure for each company code if the system is to check for duplicate invoices when you enter invoices.
    This check should prevent incoming invoices being accidentally entered and paid more than once.
    You can choose whether to activate or deactivate the check criteria of company code, reference document number and invoice date for each company code. The more criteria that you activate, the lower the probability of the system finding a duplicate invoice. The Accounting documents are checked first, followed by documents from Logistics Invoice Verification (only incorrect invoices or those entered for verification in the background).
    When checking duplicate invoices, the system compares the following
    attributes in the standard system:
    Vendor
    Currency Company code
    Gross invoice amount Reference document number
    1. Invoice date If the system finds an invoice that matches all attributes, the system
    displays a customizable message.
    If you are entering credit memos, subsequent debits, or subsequent
    credits, the system does not check for duplicate invoices.
    The exception is the Argentina country version, where the system checks
    for duplicate invoices and credit memos.
    If a previously processed document is later cancelled and then entered
    again, no message is displayed.
    Requirements
    The system only checks for duplicate invoices in Materials Management
    if you specify a reference document number when entering the invoice.
    In Customizing (IMG) for Invoice Verification, you can specify that the
    system check the following attributes
    Reference document number
    Invoice date
    Company code
    Because there are fewer attributes to check, it is more likely
    that the system will find a duplicate invoice.
    Standard settings
    All check criteria are activated in the standard system.
    Example
    The following document has been entered and posted:
    Reference document number: 333
    Invoice date: 28.04.00
    Gross invoice amount: 100,00
    Currency: EUR
    Vendor: Wolf
    Company code: Hamburg
    The settings for checks for duplicate invoices in Customizing have
    been maintained as follows:
    The field reference document number and company code are not selected.
    This means that these attributes will not be checked. Now enter the
    following invoice:
    Reference document number: 334
    Invoice date: 28.04.00
    Gross invoice amount: 100,00
    Currency: EUR
    Vendor: Wolf
    Company code: Berlin
    Result
    By entering the reference document number and entering an invoice, it
    is possible to check for duplicate invoices.
    The reference document number and the company code contain different
    data than the invoice you entered. These attributes are not checked
    because you have deselected them in Customizing.
    All other attributes are equal. The system displays a message telling
    you that a duplicate invoice has been found.
    If, for example, you had selected the reference document number in
    Customizing, the system would check this and recognize that this invoice
    is different to the previously entered invoice. The system would not
    then display a message.
    Activities
    Maintain the settings for each company code.
    Regards
    Biswajit

  • Reg:Assignment test in Invoice Verification

    Hi,
           We are doing upgrade from 4.6C to ECC6.0.When I checked the delta functionality,SAP has explained the functionality as shown below.Is it a transaction or Program?Please give me the details.
    "You can use the assignment test in the logistics invoice verification. The assignment text is a process step preceding the invoice verification in background processing. The software checks cyclically whether an open goods receipt exists for the invoices entered in background processing. The software begins the invoice verification only when open goods receipts exist for an invoice. Effects on system administration are characterized as follows: the assignment test should be called in background processing before the report for the invoice verification, because the assignment test helps create the worklist for background processing. An assignment test is faster than a complete invoice verification in background processing, inasmuch as the software does not have to process as much data from the database and does not have to execute as many checks and reports. In addition, the software does not execute full assignment of the open goods receipts as in background processing; it executes only basic assignment"
    Thanks&Regards
    Venkadesh

    Hi,
    As per requirement we need to make settings for Assignment test for LIV.
    Has anyone can explain how it works and what settings we need to carry out.
    Thanks

  • Control invoice verification after quality inspection

    Dear all,
    I want to restrict vendor invoice verification to be done after quality notification, I set QM control key 0007: Del. release, invoice block in the QM view of material master, then I post GR for a PO with inspection lot created, then I did invoice verification through MIRO it was successful without even a warning message.
    Does anybody know how to control this?
    Thx
    Danny

    Hi Danny,
    MIRO will be processed, but you will get message as "Blocked for Payment". You can see the reason for block and clear the block in MRBR. Ensure that in PO indicator GR-Based Invoice Verification is flagged.
    For more details Block the payment if inspection lot is not cleared by quality
    Thanks & Regards,
    Ramagiri

  • No invoice verification if stock is not cleared by quality.

    Dear all,
    I believe this had been discussed in length in this forum and the provocation for posting this again is that I feel that i miss something and hence i do not have the privilage to enjoy this functionality.
    I have defined the QM control key 0010 and also the quality information record is available - we are using QM module and material passes via QM only.
    I got information from this forum that the message type M8 280 has to be set as error to achieve this functionality of preventing invoice verification if material is not cleared by quality.
    I have made everything and to my suprise i find this not stopped with the error message by the system.
    Can any one throw some light on where will this error message stop and do I have to maintain any other masters and or corrections to the setting.
    Your help will be highly appreciated.
    Regards,
    M.M

    Hi Craig,
    You are right. Thanks to all experts for your valuable inputs which helped to proceed further. I am not using the exit, instead the message trigger during MIRO "'Blocked for Payment" is fine. As Jurgen already mentioned if QM config is in place QM has done its job of Blocking the Payment if inspection lot is not cleared by quality. Through MRBR block needs to be released and further online payment needs to be processed.
    Since user wants to do manual invoice also for various reasons system is configured by FI in OB27 without flagging "Manual Payments block", hence though Payment is blocked in MIRO, manually able to clear payment in F-53 without releasing the block in MRBR. Looks like more visibility should be given to FI and QM users to avoid manual payments in case of Payment Blocks.
    Currently while testing i am facing another issue. As per SAP Help if Invoice Block is activated in control key then  "'Blocked for Payment" should trigger in two cases like (1) If UD is not done (2) If inspection lot is rejected. But even if inspection lot is accepted and qty is posted to unrestricted stock during MIRO i am getting the message as "'Blocked for Payment". Before posting the invoice  Payment Block is 'Free for Payment" and after posting invoice in display mode i could see the Payment Block as 'Invoice Verification" which is supposted to be "Free for Payment" since inspection lot is cleared. Any suggestion to fix the issue will be appreciable.
    Thanks & Regards,
    Ramagiri

  • How to control quality inspection material to do Invoice verification

    I want to control on which matrial is in quality inspection, I want to bolck for IV. whenever the material not cleared from QM till invoice verification will not done. if clear from QM then IV will process.
    thanks

    Hi,
    If QM is active , you can do that by using suitable QM control key in QM view of the Material master.
    This will allow you to post the invoice , but will stop the Payment for Quality reasons. Once Quality clears the inspection lot, you can clear the invoice block (MRBR) & do the payment.
    But this can be done only if QM is active.
    Refer the link below
    invoice block
    Regards
    K.M.Arun

  • Logistics Invoice verification and Quality Management

    Hi,
    We have good receipts in purchases orders, with materials that must pass quality inspection (with SAP QM quality management)
    I need to know if there is any u201Cstandardu201D way to connect quality management with logistics invoice verification; the requirement is that the invoice cannot be released to payment (unblocked) until the materials of the goods receipt have passed the quality inspection.
    Thank you very much for your help!!
    Manuel

    Dear ,
                  Here is the path
    IMG>> Quality Management -->QM in Logistic --> QM in Procurement -->Define Control Keys
    now here After Defining the Control Key, Go to QM in Procurement Tab
    and Check the Block Invoice Checkbox
    This may help u
    REgards,
    Pardeep Malik

Maybe you are looking for

  • Spry menu bar and IE

    Menu bar works fine in all other major browsers, but there is a gap in the "specialty" submenu.  Also, it is very "twitchy in IE" i have been working on this for way too long, somebody please help.  superfunecotours.com is the site. Here is the spry

  • How do i get a credit card number off

    i need help on how to take my grandma credit card number off of my ipod cause it is charging all my songs and app to the credit card and i dont want that i remdeem my gift card but it didn't take the money off the card to buy the songs and apps with

  • Can we make the weblogic look at custom table for emailid

    Hi, I am implementing the SQL based provider for weblogic. I want the weblogic look for email id of the user in the same custom table for sending notifications. Is it possible ? By defualt I think weblogic maintains some attributes for user, email id

  • Is OHS 10.1.3 compatible with OAS 10.1.2?

    I have an existing 10.1.2 standalone OHS and 10.1.2 OAS, and an existing 10.1.3 standalone OHS and 10.1.3 OAS running on different servers. I'd like to build a new server with 10.1.2 OAS and 10.1.3 OAS on it, but with a single installion of standalon

  • ALE Distribution for Message Type FIDCC2

    Dear all, I would like to confirm my steps below in setting up the ALE distribution of message type FIDCC2, to ensure that I did not do anyhting that impact other company code that already live in the system :- 1. Use tcode OB87 to add the Global Com