Validation for vendor for invoice Rs.20000

H expert
I would like to build a validation for one time vendor for which it should not allow invoice value for <20000
How to do it. Please suggest me a  step by step config involved in this.Points will be rewarded.
sk

Better to write Validation :
Prereqisit:
BKPF-LIFNR>=1 AND BKPF-LIFNR<=100
**Check**
BSEG-WRBTR
and Write any Message what you want then SAVE
Go to OB28 and assign this validatin to our company code and active and SAVE
I hope this validation useful for you
If it will useful 4 u give rewards
Regards
TML

Similar Messages

  • Validation for duplicate AP invoice

    We would like to prevent duplicate AP invoices from being posted through FB60.   We created an FI validation in OB28 in which the prerequisite = Tcode FB60, and the check is a user exit to check the values in vendor / company code / reference fields and if those 3 fields have the same values as in an existing document, to generate an error message preventing the duplicate document from being posted.
    The above works well for creating new invoices.   However, when we have to make changes to an existing invoice (created through FB60), the system also calls on that validation and generates the error message, even though the only fields we can change on the invoice is payment terms, payment method, payment method supplement and text. 
    Other than modifying the user exit, does anybody know of a better way to do this validation or to prevent duplicate manual invoice from being created?  
    thank you.

    This has already been answered before so extracted part of the reply
    there are two duplicate checks in SAP:
    1. the one for FI documents, this is relevant for all F... postings (but nor for MIRO!)
    this can be turned off or on (in vendor master record) and 6 fields are checked:
    Check Flag for Double Invoices or Credit Memos
    Indicator which means that incoming invoices and credit memos are checked for double entries at the time of entry.
    Use
    Checking Logistics documents
    Firstly, the system checks whether the invoice documents have already been entered in the Logistics invoice verification; the system checks invoices that are incorrect, or invoices that were entered for invoice verification in the background.
    Checking FI documents
    The system then checks whether there are FI or Accounting documents that were created with the original invoice verification or the Logistics verification, and where the relevant criteria are the same.
    Checking Logistics documents
    In checking for duplicate invoices, the system compares the following characteristics by default:
    Vendor
    Currency
    Company code
    Gross amount of the invoice
    Reference document number
    Invoice document date
    If all of these characteristics are the same, the system issues a message that you can customize.
    When you enter credit memos or subsequent adjustments, the system does not check for duplicate invoices.
    Exception: Country-specific solution for Argentina, where invoices and credit memos are checked for duplicate documents.
    No message is issued if you enter a document that has previously been reversed.
    Dependencies
    The system only checks for duplicate invoices in Materials Management if you enter the reference document number upon entering the invoice.
    In Customizing for the Logistics invoice verification, you can specify that the following characteristics should not be checked:
    Reference document number
    Invoice document date
    Company code
    This means that you can increase the likelihood that the system will find a duplicate invoice, because you can reduce the number of characteristics checked.
    Example
    The following document has already been entered and posted:
    Reference document number: 333
    Invoice date: 04/28/00
    Gross invoice amount: 100.00
    Currency: EUR
    Vendor: Spencer
    Company code: Munich
    You have made the following settings in Customizing:
    The field "Reference document number" and "Company code" are deselected, which means that these characteristics will not be checked.
    Now you enter the following document:
    Reference document number: 334
    Invoice date: 04/28/00
    Gross invoice amount: 100.00
    Currency: EUR
    Vendor: Spencer
    Company code: Berlin
    Result
    Because you entered a reference document when you entered the invoice, the system checks for duplicate invoices.
    The reference document number and the company code are different from the invoice entered earlier, but these characteristics are not checked due to the settings you have made in Customizing.
    All other characteristics are the same. As a result, the system issues a message that a duplicate entry has been made.
    If the "Reference document number" had been selected in Customizing, the system would have checked the document and discovered that it was different from the invoice entered earlier, so it would not have issued a message.
    Checking FI documents
    Depending on the entry in the field "Reference", one of the following checks is carried out:
    1. If a reference number was specified in the sequential invoice/credit memo, the system checks whether an invoice/credit memo has been posted where all the following attributes agree:
    Company code
    Vendor
    Currency
    Document date
    Reference number
    2. If no reference number was specified in the sequential invoice/credit memo, the system checks whether an invoice/credit memo has been posted where all the following attributes agree:
    Company code
    Vendor
    Currency
    Document date
    Amount in document currency
    2. the one for LIV.
    this can be customized (as stated above) and is relevant for MIRO (and not for F... postings!).
    Company, Reference and Invoice date
    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

  • Validation for Duplicate Invoice Entry

    Hi Everyone,
    Currently, it seems that SAP reviews an incoming invoice for reference field (invoice number), invoice date, vendor and company code.  If the comibation of the criteria are met, then a warning message appears stating to review the entry due to a possible duplication.  I've since changed the warning message to an error so that users can not post the duplicate invoice. 
    Now, what is the process of stopping an invoice from being posted that meets the following criteria: (1) vendor, (2) invoice number, (3) amount.  Would this be a validation formula or some sort of user exit or is there standard SAP IMG that can be performed?
    Thanks for the assistance,
    Pete

    hi Peter,
    this should be a substitution exit, should happen in FI, on line item level (check transaction GGB1), for all vendor credit postings (posting key between 31 and 39). The substitution has to be done on field amount (WRBTR), because this is the first point where you have all information you need (I guess the vendor invoice number is saved into header). You have to write a small code in the exit to select possible vendor invoices from BSIK and BSAK. If any found you should issue an error message and block the process.
    hope this helps
    ec

  • Vendor wise/Invoice wise consumption for each WBS element

    Any standard report from SAP, which provide details of Vendor Purchase order / Contract, details of SES with WBS no. and details of Vendor invoice in columnar form.
    SAP system can not generate standard reports giving vendor wise/Invoice wise consumption for each WBS element of particular asset.
    Please help me to get this report.
    Thanks in Advance.

    Hi
    Your starting point should be CJI3 report or any PS report... Here you get the FI Doc no
    If this FI Doc No is generated from MM, check the Header segment of the document.. It would have MM Doc NO + Fisc Yr populated in the ref key... This gives you the link between FI & MM
    From here on, you can take it forward... You can look up this doc no in MSEG Table and find the PO no... Then go to EKBE table for other PO details....
    br, Ajay M

  • Subsequent debit for a vendor before invoice??? (URGENT!!!!!)

    hi all,
    i want to post subsequent debit for a vendor before invoice.  but the system is giving a message "The quantity to be debited/credited cannot be any greater than the quantity invoiced so far."
    can anybody tell me how to post subsequent debit before posting the invoice (i haven't got the vendor invoice yet but i must pay the freight cost).

    Hi,
    Subsequent debit : Rarely, you receive from your vendors invoices or credit memos that refer to transactions that have already been invoiced. Your company wants to use subsequent debits/credits to process these documents. A subsequent debit/credit changes the total invoice value only of a purchase order item but the total invoice quantity remains unchanged.
    The processes are:
    1)     Subsequent credit or even subsequent debit is done when total “VALUE" of invoice is changed.
    2) Total invoice Quantity is remained same.
    3) Only value based transaction takes place & not quantity base.
    4) If credit memo is received from memo then subsequent credit is done in MIRO.
    For example vendor has submitted invoice of 100 Qty for Rs 1000 & we have posted the invoice & subsequently he realized that he has invoice for higher price i.e. it should have been actually 900 Rs as against Rs 1000 .In this case he will send a credit memo of Rs 100 for which we will be doing subsequent credit.
    5) This is done for PO items if an invoice is already posted
    6) cannot refer to particular invoice
    7) Listed separately in PO history
    8) In PO total values is updated but not Quantity.
    For ur case you can pay to Vendor(freight cost ) by selecting Planned Delivery Cost instead of Goods/Services items in MIRO T.Code
    Regards,
    Biju K

  • How to produce an XML file in OAGIS format ( for Vendor Master & Invoices)

    Hi Guys,
    I've requirement to produce an XML file in OAGIS format ( for Vendor Master & Invoices) under Oracle AP and PO.
    Any inputs?
    thanks.

    Not sure,you are looking for inbuild product to produce the OAG XML format, or trying to build custom one.
    If options is Inbuild Product, Oracle Exchange is yeh another product has such kind of capability. Refer this
    http://download-west.oracle.com/docs/cd/A97329_03/web.902/a88894/adx16orx.htm#1007387
    FOr second , check out these two document in metalink
    150083.1 XML Utilities
    123491.1 How To Insert XML Documents Into The Database And Validate Them Using PL/SQL ?
    Hope this will be help

  • How system will automatically populate clearing date field for invoices paid similar to when payments are made to the vendors

    Hi SAP Gurus,
    Could you help me on this, How system will automatically populate clearing date field for invoices paid similar to when payments are made to the vendors.
    Regards
    Mohan

    Hi Ramakrishnappa,
    If you clear the invoice against payment, then the invoice clearing date would be payment document posting date.
    Regards,
    Mukthar

  • Validation for Cash Payment Rs 20000/-

    Hi friends,
    There is one way to set the limit on document not exceeding particular value, i.e. by setting limit on the basis of document type. ( since this is client level setting we can not do the same in our scenario )
    Is there any other way to do the same at company code level ( i.e. any other way which will not have client level setting ) to do such validation.
    We require to do the same for legal requirement of Cash Payment > Rs 20000/- in one Cash Payment Document. We are using the Cash Journal ( FBCJ ) . If anyone know , pls suggest. Will assign full marks if gets the solution.
    Thanks.
    PS

    Hi,
    You can create the validation rule for your requirement without touching cross client configuration.
    Validation will be possible. Pls follow the proceedure thorugh OB28/GGBO
    Cash Validation for More than Rs.20,000/-
    Prerequisite:
    t-code (SYST-TCODE) = fbcj
    company code (BSEG-BUKRS) = 'xxxx'
    GL account (BSEG-HKONT) = 'cash account defined for cj'
    Dr/Cr indicator (BSEG-SHKZG) = 'H/S' ( if you want to resrtict payment upto the prescribed amount enter H and to restrict receipt enter S
    Check:
    Amount (BSEG-DMBTR) > 20000
    Message:
    Create a message in se91 and assign it.
    please assign the points if its useful.
    Regards
    sai krishna

  • Create a validation for check double invoice

    Hi,
    I have read here on SDN for check double invoice on reference number. We want to create an warning message if same reference number is posted twice, not depending on invoice date. So if I, on 1st of October have posted an invoice with reference number 123 and then want to post with same reference number on 2nd of October I want to have an warning message. If I had understand right I need to make a validation for that. Is it true that I need to have a programmer to do that or how am I doing (one thread said that this was the solution, see; )?
    I suppose that my prerequisite will look as follows:
    BKPF-BLART = 'KR' OR BKPF-BLART = 'RE' (I want the check when entering both an invoice in FB60 and MIRO)
    How will my "check step" look like when I want to check if this reference has been entered before? Please describe in technical name.
    Is it possible to do a validation for getting a warning, or is it just possible with error message?
    I have also tried to change in IMG, in Material management > Logistics Invoice Verification > Incoming invoice > Set check for Duplicate invoices. Here we have all fields selected (check co. code, check reference, check inv. date). I changed to just select check reference, but this doesn´t solved my problem.
    Best regards Lisa

    Hello Lisa,
    Your first question,
    Yes system does not check MIRO invoice while posting FB60 invoice. Because when you post invoice with using FB60 transaction, system check BSIP table for duplication. But when you post MIRO invoice system doesn't fill BSIP table.
    So that your question answer is YES, you can register an invoice in MIRO with same reference without a warning.
    Your second question,
    BTE means Business Transaction Event. Those events are known as FI user-exit.
    So that when you posting an invoice with using FB60, system triggered on BTE 00001110 as i said on my previous message.
    I try to explain step by step how can you activate this BTE. But you need to ABAPer for giving warning message on this exit.
    Call FIBF transaction -> Settings -> Products -> ...of a customer
    Create a new line,
    Product : ZXX
    Text : BTE Products for FI Exit
    Product active : tick checkbox.
    Call SE37 for exit function and copy from FM SAMPLE_PROCESS_00001110 to ZFI_PROCESS_00001110. Then active your FM and go to FIBF transaction again.
    FIBF -> Settings -> Process Modules -> ...of a customer
    Define a new line.
    Process : 00001120
    Function Module : ZFI_PROCESS_00001110
    Product : ZFI
    And then you can some write ABAP code for validation and give warning message.
    In this FM, If you don't want to check duplicate invoice for your cases you can set export parameter e_nostd = 'X'.
    I hope it helps to you,
    Regards,
    Burak

  • I have creatd smartform for vendor return invoice and i m using std zprog o

    i have creatd smartform for vendor return invoice and i m using std zprog of other client and corresponding prog.. when i run this program using  .....after creating transc in se93. is it not workin ..
    where should i check for error and i am not getting selection screen in se38 program which i am using with this smartform..
    can u tel me step wise....what is the procedure so i can run and execute and see my output..
    please
    regards.

    Hi,
    when you run program from SE38 are you able to see the selection screen and able to exucute with out error....
    And when you run the t-code which you created for your Z-prog whats the message its giving...
    Regards,
    Shankar.

  • Available Invoices for Invoice Validation Concurrent Script in R12.1.3

    First you need to run the below script
    1) Begin
    mo_global.set_policy_context('S','Org_id');
    End;
    2)
    select * from ap_invoices where
    VALIDATION_REQUEST_ID IS NULL and APPROVAL_READY_FLAG <> 'S'
    and CANCELLED_DATE IS NULL
    and PAYMENT_STATUS_FLAG ='N' AND FORCE_REVALIDATION_FLAG='N'
    AND Invoice_id in (SELECT invoice_id  FROM AP_HOLDS_ALL H
                             WHERE H.INVOICE_ID = INVOICE_ID
                               AND H.HOLD_LOOKUP_CODE IN
                                      ('QTY ORD', 'QTY REC', 'AMT ORD', 'AMT REC', 'QUALITY',
                                       'PRICE', 'TAX DIFFERENCE', 'CURRENCY DIFFERENCE',
                                       'REC EXCEPTION', 'TAX VARIANCE', 'PO NOT APPROVED',
                                       'PO REQUIRED', 'MAX SHIP AMOUNT', 'MAX RATE AMOUNT',
                                       'MAX TOTAL AMOUNT', 'TAX AMOUNT RANGE', 'MAX QTY ORD',
                                       'MAX QTY REC', 'MAX AMT ORD', 'MAX AMT REC',
                                       'CANT CLOSE PO', 'CANT TRY PO CLOSE', 'LINE VARIANCE',
                                       'CANT FUNDS CHECK','Expired Registration','Amount Funded','Quantity Funded')
                               AND H.RELEASE_LOOKUP_CODE IS NULL)
    The above script will provide the available invoices for Invoice Validation Concurrent.
    Thanks
    Hari

    Hello,
    I had the same problem in R12.1.3, then I found out that both organizations are not used by same application. Please have a look at note 1066753.1, where as you can see, it is not allowed to merge parties from AP to AR.
    Don´t know if this is the solution for your problem, but just wanted to share the information.
    Regards,
    Wim

  • CRR: Need script for Validated, unpaid and unhold invoices

    Hello Friends,
    Kindly give me report to prepare Cash Requirment Report. Which should have validated, unpaid and unhold invoices in the output.
    Thanks in advance.
    Regards,
    Raj
    Below is the my query -- Getting wrong data
    select decode(ia.set_of_books_id ,224,'TGB Australia - Primary SOB'
    ,225,'TGB Australia - Reporting SOB'
    ,446,'TGB Belgium - Primary SOB'
    ,447,'TGB Belgium - Reporting SOB'
    ,324,'TGB Bermuda GBRM SOB'
    ,364,'TGB Bermuda Holding Limited SOB'
    ,306,'TGB Bermuda International Holding SOB'
    ,284,'TGB Bermuda SOB'
    ,45, 'TGB Canada - Primary SOB'
    ,44, 'TGB Canada - Reporting SOB'
    ,244,'TGB Consolidation SOB'
    ,84, 'TGB France - Primary SOB'
    ,85, 'TGB France - Reporting SOB'
    ,70, 'TGB Germany - Primary SOB'
    ,71, 'TGB Germany - Reporting SOB'
    ,168,'TGB Hong Kong - Primary SOB'
    ,169,'TGB Hong Kong - Reporting SOB'
    ,72, 'TGB Italy - Primary SOB'
    ,73, 'TGB Italy - Reporting SOB'
    ,409,'ITXC Corp. - Primary SOB'
    ,408,'ITXC Global SOB'
    ,404,'ITXC Hold - Primary SOB'
    ,405,'ITXC Hold - Reporting SOB'
    ,406,'ITXC Hold 2 - Primary SOB'
    ,407,'ITXC Hold 2 - Reporting SOB'
    ,424,'ITXC IPCO SOB'
    ,170,'TGB Japan - Primary SOB'
    ,171,'TGB Japan - Reporting SOB'
    ,285,'TGB Luxembourg - Primary SOB'
    ,286,'TGB Luxembourg - Reporting SOB'
    ,287,'TGB Luxembourg Holding - Primary SOB'
    ,288,'TGB Luxembourg Holding - Reporting SOB'
    ,289,'TGB Netherlands BV - Primary SOB'
    ,290,'TGB Netherlands BV - Reporting SOB'
    ,304,'TGB Netherlands Holding BV - Primary SOB'
    ,305,'TGB Netherlands Holding BV - Reporting SOB'
    ,172,'TGB Norway - Primary SOB'
    ,173,'TGB Norway - Reporting SOB'
    ,444,'TGB Poland - Primary SOB'
    ,445,'TGB Poland - Reporting SOB'
    ,344,'TGB Puerto Rico SOB'
    ,384,'TGB Singapore - Primary SOB'
    ,385,'TGB Singapore - Reporting SOB'
    ,68, 'TGB Spain - Primary SOB'
    ,69, 'TGB Spain - Reporting SOB'
    ,465,'TVC Teleglobe-VSNL Consolidation'
    ,164,'TGB United Kingdom - Primary SOB'
    ,165,'TGB United Kingdom - Reporting SOB'
    ,265,'TGB USA SOB'
    ,484,'VSNL International SOB (301)'
    ,485,'VSNL America SOB (302)'
    ,486,'VSNL Bermuda SOB'
    ,487,'VSNL Guam SOB'
    ,504,'VSNL Japan Primary SOB'
    ,505,'VSNL Japan Reporting SOB'
    ,506,'VSNL Singapore SOB'
    ,508,'VSNL Hong Kong SOB'
    ,509,'VSNL UK TEL - Primary SOB'
    ,510,'VSNL UK TEL - Reporting SOB'
    ,511,'VSNL France - Primary SOB'
    ,512,'VSNL France - Reporting SOB'
    ,513,'VSNL Netherlands - Primary SOB'
    ,514,'VSNL Netherlands - Reporting SOB'
    ,515,'VSNL Germany - Primary SOB'
    ,516,'VSNL Germany - Reporting SOB'
    ,517,'VSNL Belgium - Primary SOB'
    ,518,'VSNL Belgium - Reporting SOB'
    ,519,'VSNL UK LTD - Primary SOB'
    ,520,'VSNL UK LTD - Reporting SOB'
    ,521,'VSNL Spain - Primary SOB'
    ,522,'VSNL Spain - Reporting SOB'
    ,523,'VSNL Portugal INS - Primary SOB'
    ,524,'VSNL Portugal INS - Reporting SOB'
    ,525,'VSNL Portugal UNI - Primary SOB'
    ,526,'VSNL Portugal UNI - Reporting SOB') Sob_Name
    ,decode(tl.due_days,NULL,to_char(tl.fixed_date,'DD-MON-YYYY')
    ,to_char((inv.due_date),'DD-MON-YYYY')) Due_Date
    ,ib.batch_name
    ,v.segment1 Vendor_Number
    ,v.vendor_name
    ,ia.invoice_num
    ,to_char(ia.invoice_date,'DD-MON-YYYY') Invoice_Date
    ,ia.invoice_currency_code
    ,pos.po_number PO_Number
    ,(inv.amount_remaining) Currency_Invoice_Amount
    ,ia.exchange_rate
    ,round(inv.amount_remaining * nvl(ia.exchange_rate,1),2) USD_Invoice_Amount
    ,ia.description
    ,ia.pay_group_lookup_code
    ,decode(hld.holds_count,NULL,'Yes'
    ,hld.holds_count) Approved
    from (select invoice_id
    ,count(invoice_id) Holds_Count
    from ap_holds_all
    where release_lookup_code is null
    group by invoice_id) hld
    ,(select psa.invoice_id
    ,psa.due_date
    ,psa.gross_amount
    ,psa.amount_remaining
    ,psa.payment_method_lookup_code
    ,psa.payment_status_flag
    from ap_payment_schedules_all psa
    where psa.payment_status_flag in ('N','P')
    and amount_remaining is not null) inv
    ,(select ida.invoice_id
    ,max(po.segment1) po_number
    from po_headers_all po
    ,po_distributions_all pd
    ,ap_invoice_distributions_all ida
    where ida.po_distribution_id = pd.po_distribution_id
    and pd.po_header_id = po.po_header_id
    and ida.po_distribution_id is not null
    group by ida.invoice_id) pos
    ,ap_Terms_Lines tl
    ,ap_terms t
    ,po_vendor_sites_all vsa
    ,ap_batches_all ib
    ,ap_invoices_all ia
    ,po_vendors v
    where ia.vendor_id = v.vendor_id
    and ia.invoice_id = hld.invoice_id
    and ia.terms_id = t.term_id
    and t.term_id = tl.term_id
    and ia.vendor_id = vsa.vendor_id
    and ia.vendor_site_id = vsa.vendor_site_id
    and ia.batch_id = ib.batch_id(+)
    and ia.invoice_id = inv.invoice_id
    and ia.invoice_id = pos.invoice_id(+)
    and ia.invoice_id = decode(vsa.hold_future_payments_flag,'N',decode(vsa.hold_all_payments_flag,'N',inv.invoice_id))
    and inv.amount_remaining != 0
    and (inv.due_date <= &<name="Pay Through Date"
    hint="Please enter a Pay Through Date (eg: 31-MAY-2007)"
    type="string"
    required="yes">
    or tl.fixed_date <= &<name="Pay Through Date"
    hint="Please enter a Pay Through Date (eg: 31-MAY-2007)"
    type="string"
    required="yes">)
    order by (inv.due_date)

    Hello Friends,
    Kindly give me report to prepare Cash Requirment Report. Which should have validated, unpaid and unhold invoices in the output.
    Thanks in advance.
    Regards,
    Raj
    Below is the my query -- Getting wrong data
    select decode(ia.set_of_books_id ,224,'TGB Australia - Primary SOB'
    ,225,'TGB Australia - Reporting SOB'
    ,446,'TGB Belgium - Primary SOB'
    ,447,'TGB Belgium - Reporting SOB'
    ,324,'TGB Bermuda GBRM SOB'
    ,364,'TGB Bermuda Holding Limited SOB'
    ,306,'TGB Bermuda International Holding SOB'
    ,284,'TGB Bermuda SOB'
    ,45, 'TGB Canada - Primary SOB'
    ,44, 'TGB Canada - Reporting SOB'
    ,244,'TGB Consolidation SOB'
    ,84, 'TGB France - Primary SOB'
    ,85, 'TGB France - Reporting SOB'
    ,70, 'TGB Germany - Primary SOB'
    ,71, 'TGB Germany - Reporting SOB'
    ,168,'TGB Hong Kong - Primary SOB'
    ,169,'TGB Hong Kong - Reporting SOB'
    ,72, 'TGB Italy - Primary SOB'
    ,73, 'TGB Italy - Reporting SOB'
    ,409,'ITXC Corp. - Primary SOB'
    ,408,'ITXC Global SOB'
    ,404,'ITXC Hold - Primary SOB'
    ,405,'ITXC Hold - Reporting SOB'
    ,406,'ITXC Hold 2 - Primary SOB'
    ,407,'ITXC Hold 2 - Reporting SOB'
    ,424,'ITXC IPCO SOB'
    ,170,'TGB Japan - Primary SOB'
    ,171,'TGB Japan - Reporting SOB'
    ,285,'TGB Luxembourg - Primary SOB'
    ,286,'TGB Luxembourg - Reporting SOB'
    ,287,'TGB Luxembourg Holding - Primary SOB'
    ,288,'TGB Luxembourg Holding - Reporting SOB'
    ,289,'TGB Netherlands BV - Primary SOB'
    ,290,'TGB Netherlands BV - Reporting SOB'
    ,304,'TGB Netherlands Holding BV - Primary SOB'
    ,305,'TGB Netherlands Holding BV - Reporting SOB'
    ,172,'TGB Norway - Primary SOB'
    ,173,'TGB Norway - Reporting SOB'
    ,444,'TGB Poland - Primary SOB'
    ,445,'TGB Poland - Reporting SOB'
    ,344,'TGB Puerto Rico SOB'
    ,384,'TGB Singapore - Primary SOB'
    ,385,'TGB Singapore - Reporting SOB'
    ,68, 'TGB Spain - Primary SOB'
    ,69, 'TGB Spain - Reporting SOB'
    ,465,'TVC Teleglobe-VSNL Consolidation'
    ,164,'TGB United Kingdom - Primary SOB'
    ,165,'TGB United Kingdom - Reporting SOB'
    ,265,'TGB USA SOB'
    ,484,'VSNL International SOB (301)'
    ,485,'VSNL America SOB (302)'
    ,486,'VSNL Bermuda SOB'
    ,487,'VSNL Guam SOB'
    ,504,'VSNL Japan Primary SOB'
    ,505,'VSNL Japan Reporting SOB'
    ,506,'VSNL Singapore SOB'
    ,508,'VSNL Hong Kong SOB'
    ,509,'VSNL UK TEL - Primary SOB'
    ,510,'VSNL UK TEL - Reporting SOB'
    ,511,'VSNL France - Primary SOB'
    ,512,'VSNL France - Reporting SOB'
    ,513,'VSNL Netherlands - Primary SOB'
    ,514,'VSNL Netherlands - Reporting SOB'
    ,515,'VSNL Germany - Primary SOB'
    ,516,'VSNL Germany - Reporting SOB'
    ,517,'VSNL Belgium - Primary SOB'
    ,518,'VSNL Belgium - Reporting SOB'
    ,519,'VSNL UK LTD - Primary SOB'
    ,520,'VSNL UK LTD - Reporting SOB'
    ,521,'VSNL Spain - Primary SOB'
    ,522,'VSNL Spain - Reporting SOB'
    ,523,'VSNL Portugal INS - Primary SOB'
    ,524,'VSNL Portugal INS - Reporting SOB'
    ,525,'VSNL Portugal UNI - Primary SOB'
    ,526,'VSNL Portugal UNI - Reporting SOB') Sob_Name
    ,decode(tl.due_days,NULL,to_char(tl.fixed_date,'DD-MON-YYYY')
    ,to_char((inv.due_date),'DD-MON-YYYY')) Due_Date
    ,ib.batch_name
    ,v.segment1 Vendor_Number
    ,v.vendor_name
    ,ia.invoice_num
    ,to_char(ia.invoice_date,'DD-MON-YYYY') Invoice_Date
    ,ia.invoice_currency_code
    ,pos.po_number PO_Number
    ,(inv.amount_remaining) Currency_Invoice_Amount
    ,ia.exchange_rate
    ,round(inv.amount_remaining * nvl(ia.exchange_rate,1),2) USD_Invoice_Amount
    ,ia.description
    ,ia.pay_group_lookup_code
    ,decode(hld.holds_count,NULL,'Yes'
    ,hld.holds_count) Approved
    from (select invoice_id
    ,count(invoice_id) Holds_Count
    from ap_holds_all
    where release_lookup_code is null
    group by invoice_id) hld
    ,(select psa.invoice_id
    ,psa.due_date
    ,psa.gross_amount
    ,psa.amount_remaining
    ,psa.payment_method_lookup_code
    ,psa.payment_status_flag
    from ap_payment_schedules_all psa
    where psa.payment_status_flag in ('N','P')
    and amount_remaining is not null) inv
    ,(select ida.invoice_id
    ,max(po.segment1) po_number
    from po_headers_all po
    ,po_distributions_all pd
    ,ap_invoice_distributions_all ida
    where ida.po_distribution_id = pd.po_distribution_id
    and pd.po_header_id = po.po_header_id
    and ida.po_distribution_id is not null
    group by ida.invoice_id) pos
    ,ap_Terms_Lines tl
    ,ap_terms t
    ,po_vendor_sites_all vsa
    ,ap_batches_all ib
    ,ap_invoices_all ia
    ,po_vendors v
    where ia.vendor_id = v.vendor_id
    and ia.invoice_id = hld.invoice_id
    and ia.terms_id = t.term_id
    and t.term_id = tl.term_id
    and ia.vendor_id = vsa.vendor_id
    and ia.vendor_site_id = vsa.vendor_site_id
    and ia.batch_id = ib.batch_id(+)
    and ia.invoice_id = inv.invoice_id
    and ia.invoice_id = pos.invoice_id(+)
    and ia.invoice_id = decode(vsa.hold_future_payments_flag,'N',decode(vsa.hold_all_payments_flag,'N',inv.invoice_id))
    and inv.amount_remaining != 0
    and (inv.due_date <= &<name="Pay Through Date"
    hint="Please enter a Pay Through Date (eg: 31-MAY-2007)"
    type="string"
    required="yes">
    or tl.fixed_date <= &<name="Pay Through Date"
    hint="Please enter a Pay Through Date (eg: 31-MAY-2007)"
    type="string"
    required="yes">)
    order by (inv.due_date)

  • Accounting dcoument for vendor excise invoice

    Hi,
    Here
    While posting vendor excise invoice ,there is no accounting doc generated.But when i saw the details,i found the doc post date is 23/2/2010 and vendor exicse invoice year is 2009.So please suggest me over thsi matter.

    1.check your tax code configuration in FTXP . it must be assigned to accont key NVV then it will inventorize
    2.check the materil type in J1ID it could be non-cenvatable
    3.excise condition types activated against your tax code could be configured to post inventory account.
    check in the config under ' classify condition type '
    hope it helps

  • Gr for invoicing plan?

    Hi,
    Can we have GR for invoicing plan? If yes, what impact it will make? I no...than what is the reason?
    Regards,
    Satyendra

    Hi Satya,
    I think GR will not be ther for Framework Document pos.
    Multiple invoices can be processed. Main point is that invoices must be processed within the validity period spesified in PO. The total value of invoices must also not exceed the limit spesified in PO item. The validity period is spesified on PO Header Level, while the Limit is on Item level. The creation of Purchase requisition is Optional.
    Purchase Requisitions doesn't have validity period fields, although the limit can be spesified on item level. So if users create PR's then they could type the validity period simply as text in one of the long text fields.
    During invoicing, if the date is outside validity period or the amount is bigger, either a Warning or Error will occur. This setting is done in customising.
    Examples on where this business process can be used include: Services: example buying flowers, travel. Perticular if the receipt process is not very formalised. It is also sometimes used for utilities (water, electricity...).
    Look at processes where Financial invoices (no PO) are used. To improve control, a lot of vendor invoices could be moved to Blanket Order process.
    Reg,
    Ashok

  • How to restrict a hold GR document for invoicing

    Dear all,
    I made the GR against a PO in MIGO. for that document no also generated. But due to some reason i want to hold the document no, so that it can't be further processed.
    I also hold the same document no by performing "DISPLAY" "MATERIAL DOCUMENT" & entering the same document no and click on the "HOLD" button in MIGO.
    After this, it shows in the document overview tree under "HELD DATA". but it still allowes for invoicing in MIR7 and MIRO which i want to restrict.
    Is it possible to restrict for invoicing.
    Quick reply will be appriciated.
    thanks
    Prasant sekhar

    Hi
    Goto Transaction code: XK05 and Block that particular vendor for Invoice posting at select Company code level..
    Reward if useful
    Regards
    S.Baskaran

Maybe you are looking for