Invoice match option on PO to Default to "PO"

Can someone tell me how to get the Invoice match option on the PO shipments more tab to be set to default to "PO" currently it is defaulting to Receipt.
Thanks

I know the value is stored at the vendor level, but can it be overridden at the line item level on the PO?
For example, you are purchasing 10 widgets which will be delivered & you want to pay for them based on receipt, however,
the vendor is charging you a set up fee because you have special requirements. This setup fee is a 2-way match, and will need to
be paid by invoice. Can this be done on one PO?

Similar Messages

  • PO Releases 'invoice match option'

    Hi,
    The PO has one match option at the header and a different match option at the release line. This is causing an inability to match the invoice in Payables until it gets correctd.
    How do i check where this invoice match option is defaulting from?
    Is it from the supplier level or the Po header level.
    and how can this problem be corrected?
    Any ideas?
    Thanks,
    Ashwathy

    Hi,
    I think you are mixing the two things,well i think anyway. Match approval level and match invoice options are independent. You can set the match approval level as default in the setup to say 2-way. Assuming you have done that when you enter the shipment details you can select the match invoice option to PO or to receipt.
    Now match approval and match invoice are part of the optional information on the shipments. SO if you do not enter the match approval the default which is set to 2-way will be picked up.If you want match invoice to be PO, i suggest you don't enter any value for it, if the match invoice is NULL it will be displayed as PO so i am assuming it will be default unless you change it to receipt.
    I think this should resolve your issue.
    Regards,
    Utsav.

  • Invoice Match Option for PO in iSupplier Portal

    What should be the invoice match option for POs transmitting through iSupplier Portal?

    Pl do not post duplicates - Invoice Match Option for PO in iSupplier Portal

  • Navigation for invoice match option

    Hi Members,
    Can any one let me know the navigation for "Invoice Match Option" for the purchase order shipment.
    I want to set the invoice match option for a supplier site to "Receipt".

    Hi
    Navigation for changing Invoice match Option
    Financial Option-> Supplier Entry (Tab)
    In Supplier Entry Tab Change Invoice Match Option: To Receipt
    Thanking You
    Sunil

  • Script to update vendor inactive date and invoice match option

    As part of a review of our precure to pay process in 11.5.10, we have to make a change to a large number of suppliers (vendors).
    We want to disable about 7000 suppliers by setting the inactive date and for the remaining suppliers change the invoice match option from receipt to purchase order
    There does not appear to be any api that I can use to make these changes.
    Does anyone have any experience in using a baisc update script to change the data.
    Scripts would be something like:
    Inactivate suppliers
    update po_vendors
    set end_date_active = sysdate
    where vendor_id in <list of vendors to update>
    update po_vendor_sites_all
    set inactive_date = sysdate
    where vendor_site_id = <list of vendors sites to update>
    Change invoice match option
    update po_vendors
    set match_option = 'P'
    where vendor_id in <list of vendors to update>
    update po_vendor_sites_all
    set match_option ='P'
    where vendor_site_id = <list of vendors sites to update>

    Hello.
    In your place i would not have the guts to use SQL for a task like that. You know what Oracle says about using tools to modify data in the database. They always say that it is not supported and to use forms to modify the data. So I would suggest you to use a tool like DataLoad to query and modify your suppliers.
    Octavio

  • Purchase Orders - Invoice Matching Option=PO with 4 way matching

    Hi
    i am new to AP and would like to clarify the following
    what does the following combination mean ?
    Invoice matching option = PO and 4 way matching.
    Does it mean: invoice is matched against PO with out giving consideration for inspection and Delivery quantites ? because with 4 way matching, inspection, delivery are also matched, isnt it ?
    kindly can someone clarify this confusion ?
    Thanks in Advance

    Hi ,
    4 way matching should be with Receipt only , not with PO.
    pl.refer following link to clear your doubts.
    http://oracleappsyashrajvarsity.blogspot.in/2009/04/ramification-of-invoice-match-to-po-and.html
    http://docs.oracle.com/cd/A60725_05/html/comnls/us/ap/point04.htm
    HTH
    Sanjay

  • Needs Restriction of Receipt against 2-way & PO match option setting

    Hi
    We have approved Standard PO with Match Approval Level = 2-Way & Invoice Match Option = PO .
    Now, it is allowing to take a receipt against such PO .
    We want to restrict receipt against PO who has such type of setting .
    How we can do this ?
    regards
    SD

    On the receipts screen, write a when-validate-record personalization that checks the type of the po and displays an error message. This will stop the user from saving the receipt transactions.
    Hope this helps
    Sandeep Gandhi

  • PO default invoice matching issue

    Hi All,
    I'm facing a PO default invoice matching issue. As we know, we can use the PO default invoice type to copy the invoice detail information from PO e.g. PO distribution. The following is the problem details:
    Oracle Application Version: 11.5.10.2
    1. PO distribution (PO Charge Account) 01-110-1570-0000-000
    2. Receiving Option (Expense AP Accrual Account) 01-000-2225-0000-000
    3. Item destination type is Expense.
    When I create the PO default invoice, give the po number and click the match button, Match to Purchase Order form comes out. And then I give the Qty invoiced and click the match button. Ideally, the invoice distribution account should be same as the PO distribution account e.g 01-110-1570-0000-000. But the invoice distribution account is 01-000-2225-0000-000. Could you please explain my doubt on this?
    Thanks & Best Regards,
    Jerome
    Edited by: Jerome.Yin on Aug 21, 2009 8:25 PM
    Duplicate Thread, Please look into the another one. Sorry for inconvenience

    Hi All,
    I'm facing a PO default invoice matching issue. As we know, we can use the PO default invoice type to copy the invoice detail information from PO e.g. PO distribution. The following is the problem details:
    Oracle Application Version: 11.5.10.2
    1. PO distribution (PO Charge Account) 01-110-1570-0000-000
    2. Purchasing Option (Expense AP Accrual Account) 01-000-2225-0000-000
    3. Item destination type is Expense.
    When I create the PO default invoice, give the po number and click the match button, Match to Purchase Order form comes out. And then I give the Qty invoiced and click the match button. Ideally, the invoice distribution account should be same as the PO distribution account e.g 01-110-1570-0000-000. But the invoice distribution account is 01-000-2225-0000-000. Could you please explain my doubt on this?hi
    this is a general rules. invoice distribution shows the Debit entries. and AP Expense Accrual A/C is debited in Invoice while it is credit in Receiving.
    Thanks
    Lisan

  • Which table find the matching options of invoice level in ap in oracle apps

    hi
    which table find the matching options of invoice level in ap in oracle apps
    thnks

    Hi,
    Have a look at the following note:
    Note: 190156.1 - AP: Which Tables Are Populated When Invoices Are Matched To A PO?
    https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=190156.1
    Refer to [eTRM |http://etrm.oracle.com] for more details about the tables.
    Regards,
    Hussein

  • Invoice Match to be set as PO in Purchase Orders

    In Purchase orders, I need the Invoice Match level to be set as 'PO' for the items defined with 'Receipt Required' as 'NO'. Is it possible?
    If so, please guide.
    Thanks,
    Kaveri

    The invoice match level gets it default from various sources such as Supplier, quote etc.
    You can consider writing a when-validate-record personalization on shipments block that warns the user if the option is not set correctly.
    Hope this helps,
    Sandeep Gandhi

  • Prepayment invoice matched to PO going on receiving hold

    Hi everybody,
    I want to know why a prepayment invoice will go on a receiving hold in oracle AP when matched to an unreceived PO. Outside of manually releasing the hold and making the payment is there some other set up that allows ONLY prepayment invoices not to go on a receiving hold whether they have been received or not. (This is in 11i)
    All responses highly appreciated!
    Thanks!!

    Hi ,
    Kindly check the option in the Invoice tab for this particular supplier site..the match option would have been set to Receipt ..Change this to PO and no 2 uncheck the option hold unmatched Invoice.
    Hope this will resolve your issue.
    Regards,
    Ramaa

  • Preventing Overbilling in payable invoices matched to PO/Receipts

    Hi,
    how to prevent overbilling of a overbilling of a payable invoice matched to a po/receipt. (placing hold). we are in 11.5.10.2.
    In the payable invoice find receipts window, fully matched receipts also getting displayed against a PO, users are able to enter quantity billed, (warning is displayed), but data saved.
    Is this standard functionality?

    Keep in mind that we do not know what is going on in your system (what procedures are being followed). First thought - are the users failing to pick the Final Match option during matching? If you select Final Match, the system updates the closure status of the entire purchase order to "Finally Closed" when you validate the invoice. No further actions can be performed against a PO level that is closed. Sounds like your users can still match against fully received POs, which makes me think that your POs are not being closed out.
    Also, what have you set up for your invoice tolerances? The downside of tolerances is that they work both ways. But using tolerances may help reduce the problems somewhat. So you may wish to look at that as well.
    Hope this helps a bit.
    John Dickey

  • WHAT IS  THE USE OF COPY/MATCH OPTION  IN BUISNESS CONTENT

    WHAT IS  THE USE OF COPY/MATCH OPTION  IN BUISNESS CONTENT  GIVE DETAILS

    Hi,
    Match (X) or Copy
    If the SAP delivery version and the active version can be matched, a checkbox is displayed in this column.
    With the most important object types, the active version and the SAP delivery version can be matched.
    From a technical point of view, the SAP delivery version (D version) is matched with the M version. As in most cases the M version is identical to the active version (A version) in a customer system, this is referred to as a match between the D and A versions for reasons of simplification.
    When a match is performed, particular properties of the object are compared in the A version and the D version. First it has to be decided whether these properties can be matched automatically or whether this has to be done manually. A match can be performed automatically for properties if you can be sure that the object is to be used in the same way as before it was transferred from Business Content.  When performing matches manually you have to decide whether the characteristics of a property from the active version are to be retained, or whether the characteristics are to be transferred from the delivery version.
    Example of an automatic match
    Additional customer-specific attributes have been added to an InfoObject in the A version. In the D version, two additional attributes have been delivered by SAP that do not contain the customer-specific attributes.  In order to be able to use the additional attributes, the delivery version has to be installed from Business Content again. At the same time, the customer-specific attributes are to be retained. In this case, you have to set the indicator (X) in the checkbox.  After installing the Business Content, the additional attributes are available and the customer-specific enhancements have been retained automatically. However, if you have not checked the match field, the customer-specific enhancements in the A version are lost.
    Example of a manual match
    An InfoObject has a different text in the A version than in the D version. In this case the two versions have to be matched manually. When Business Content is installed, a details screen appears which asks you to specify whether the text should be transferred from the active version or from the D version.
    The Match indicator is set as default in order to prevent the customer version being unintentionally overwritten. If the Content of the SAP delivery version is to be matched to the active version, you have to set the Install indicator separately.
    The active version is overwritten with the delivery version if
    ¡        the match indicator is not set and
    ¡        the install indicator is set.
    In other words, the delivery version is copied to the active version.
    If the Install indicator is not set, the object is not copied or matched. In this case, the Match indicator has no effect.
    In the context menu, two options are available:
                                a.      Merge All Below
    The object in the selected hierarchy level and all objects in the lower levels of the hierarchy are selected as to Match.
                                b.      Copy All Below
    The Match indicators are removed for the object in the selected hierarchy level and all objects in the lower levels of the hierarchy. If the Install indicator is also set, these objects are copied from the delivery version to the active version.
    The most important properties which are taken into account when versions are matched are now listed.
    When referring to InfoObjects it is important to differentiate between:
    §         Characteristics
    §         Time characteristics
    §         Key figures and
    §         Units
    Valid for All InfoObjects Named Above:
    Properties Matched Automatically:
    Properties Matched Manually:
    ·        Texts
    ·        Description
    If texts/descriptions in the delivery version do not yet exist in the active version, they are transferred.
    ·        Attribute only (flag)
    ·        Short and long text (description)
    ·        Time dependency of attributes
    ·        Transfer routine
    Valid for Characteristics
    Properties Matched Automatically:
    Properties Matched Manually:
    ·        Compounding
    New InfoObjects are included in compounding
    ·        Referenced characteristic
    Reference characteristics are transferred automatically. A warning is issued.
    ·        Attributes / navigation attributes
    New attributes are included.
    If an attribute is added by the customer, the settings for this attribute are transferred (for example, F4 sequence).
    ·        Application components
    If the entry for the active version is initial, the delivery version is used.
    ·        BEx display
    ·        Characteristic constants
    ·        Default member
    ·        Authorizations (flag and field)
    ·        Selection (CHASEL)
    ·        InfoObject is document attribute
    ·        Data type
    ·        Length
    ·        Output length
    ·        Conversion routines
    ·        Lower case allowed (flag)
    ·        Contains master data (flag)
    ·        Master data is authorization relevant (flag)
    ·        Export DataSource (Flag)
    ·        F4 query design
    ·        F4 query runtime
    ·        Check ODS object
    ·        Contains text tables (flag)
    ·        Texts are language-dependent (flag)
    ·        Short, medium and long texts exist (each with flag)
    ·        Default currency
    ·        GIS attribute
    ·        Hierarchies exist (flag)
    Valid for Key Figures
    Properties Matched Automatically:
    Properties Matched Manually:
    ·        Type of key figure
    ·        Fixed unit
    ·        Fixed currency
    ·        Aggregation
    ·        Exception aggregation
    Valid for Units
    Properties Matched Automatically:
    Properties Matched Manually:
    ·        See the table above (Valid for Characteristics), if these properties are also relevant for the units.
    When referring to InfoProviders it is important to differentiate between:
    ¡        MultiProviders
    ¡        InfoCubes
    ¡        ODS Objects and
    ¡        InfoObjects
    InfoObjects are discussed above (see the first table Valid for All Objects Named Above).
    Valid for All InfoProviders Named Above:
    Properties Matched Automatically:
    Properties Matched Manually:
    ·        New InfoObjects
    If InfoObjects in the delivery version do not yet exist in the active version, they are transferred.
    ·        Manual matching is not necessary.
    Valid for MultiProviders
    Properties Matched Automatically:
    Properties Matched Manually:
    ·        New InfoProviders
    If InfoProviders in the delivery version do not yet exist in the active version, they are transferred.
    ·        Manual matching is not necessary.
    Valid for InfoCubes
    Properties Matched Automatically:
    Properties Matched Manually:
    ·        New dimensions
    If dimensions in the delivery version do not yet exist in the active version, they are transferred.
    ·        Manual matching is not necessary.
    With the InfoObject catalog object type, InfoObjects that are assigned to a catalog in the delivery version are transferred to the active version automatically. Manual matching is not necessary.
    With the transfer rule object type, those objects that exist in the delivery version but are not yet contained in the active version (for example, additional attributes) are added automatically when the match is performed.  Manual matching is not necessary.
    With the process chain object type, those objects that exist in the delivery version but are not yet contained in the active version (for example, additional objects in the process chain) are added automatically when the match is performed.  Manual matching is not necessary.
    ·        Active Version Available
    In this column, the following display options are available:
    ¡        : The object is available in an active version. You decide whether you want to retain this version or reinstall the latest version of the object.
    ¡        Date symbol: The object is already available in an active version. However, the active version belongs to an older Content release. SAP recommends that you install the latest version.
    ¡        Gray symbol: An activated version of the object is available in the system. However, the object status is inactive. If an object version is activated, this indicates that all metadata for the object can be created successfully. The inactive object status indicates that the processed object is inconsistent and cannot currently be used for processing data. Transfer the object again from the SAP delivery version (D version).  If this is not enough to change the object status from “inactive” to “active” the object has to be postprocessed. You find notes on postprocessing in the activation log.
    Postprocessing: An inactive object status may also occur for an InfoObject if changes are made to the structure at field level. Postprocessing the object involves converting the relevant tables in accordance with the activation log.
    ¡        No indicator: The object is not available in an active version.
    7. Make Settings in the Selection List and Install.
    Make the required settings in the  Install selection list:
    Installation Type
    Installation Type
    Information
    Simulate installation
    The system runs a test to see whether any errors are likely to occur during the installation. However, not all errors that may occur can be identified during simulation: Some error messages can only be generated when a real A version (and not just a simulation) is available in the system. You should, therefore, only use the simulation function as a rough guide to help you identify and remove basic errors.
    Install
    The selected objects are installed immediately.
    Install in background
    The selected objects are installed in the background.
    Install and transport
    The selected objects are installed immediately and then written to a transport request.
    SAP recommends you use the Install in background option because installing a large number of objects can take a long time. Modifying objects that are already active can take an especially long time to complete. Make sure that when you install objects in the background that the versions are not matched. It is always the delivery versions that are installed. These are not matched with any available customer versions.
    Refer
    Business Content (Versions)
    http://help.sap.com/saphelp_nw04/helpdata/en/c1/ea683cc5e8ca68e10000000a114084/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/80/1a66d5e07211d2acb80000e829fbfe/frameset.htm
    Thanks,
    JituK

  • Payables Import Performance after Match Option changed to PO

    We changed the match option from 'R' to 'P' and since then payables import has been running longer and taking nearly 100% of the CPU while all other pending processes are erroring out with Signal 11.
    Has anybody here got this kind of issue with Payables Invoice Import?
    Looking for suggestions
    Thank a lot.

    Not seen this kind of an issue. May be you n can try taking a sql trace for both the cases and locate what the problem might be.

  • Invoice matching report in AR Donwpayment Invoice

    Hi Expert,
    Customer would like to see AR Downpayment Invoice matching report as follow. May I know how to derive the information?
    BP name(A)   D/P Inv No(B).  Total amount in D/P Inv(C)    Amount applied in invoices(D)    Remaining balance(E)=C-D
    and the report must include supporting information about paid invoices
    Inv No.    Posting date      Amount.--> Total of these amount must be same with (D)
    Regards
    Thomas

    Dear Thomas,
    In order to get this information you need a query that would work out the values in the ar down payment invoice.
    This can be a beginning. However, some values must be calculated in the query because they are not in the table.
    SELECT T0.DocNum, T0.CardCode, T1.VatSum, T1.LineTotal, (T1.LineTotal * T0.DpmPrcnt/100) as DPM, (t1.LineTotal - (T1.LineTotal * T0.DpmPrcnt/100) - T1.VatSum) as PAYM_LEFT FROM ODPI T0  INNER JOIN DPI1 T1 ON T0.DocEntry = T1.DocEntry WHERE T0.DocNum = '1'
    Please, let me know if this is sufficient or you need some more information from the query.
    Kind Regards,
    Marcella Rivi
    SAP Business One Forums Team

Maybe you are looking for