R12 AP - Split Invoice Lines
Hi Friends,
I would like to split the Invoice lines through our custom package. For Example: There is a invoice Line of 100 USD, i would like to split the lines into 60 USD and 40 USD through our custom package. Hence, i would like to know, if there are any standard API's which can be made use of, for this purpose?
Thanks!!
Hi,
Anybody there watching this thread?
Pl. let me know, if there are any Standard API's to handle the line split in AP.
Thanks in advance.
Similar Messages
-
R12 - AP Invoice Lines Interface & Tax Codes
We have a slight problem getting AP Invoice Lines through the Payables Open Interface. In 11i the value held in the TAX_CODE column was validated (against AP_TAX_CODES I believe), and if wrong or missing the line was rejected. The eTRM for R12 claims this column is still validated, although against ZX_TAXES_B, however testing shows this to be untrue. Support documentation from Oracle (e.g. note 472649.1) suggest a number of other columns are now used for tax validation, however testing agains shows this to be untrue. The only column we can find which is validated is TAX_CLASSIFICATION_CODE, and if this column contains a valid tax code then the invoice line will be accepted, however we cannot find any documentation which shows that this column should be used.
Has anyone out there bottomed out this issue, and if so is there any insight you could offer?
Many thanks.
Edited by: user13317468 on Jul 4, 2011 1:32 AMHi Vinod,
please check the below reference from oracle support ...
Case Study: How Payables Open Interface Import works with EB Tax for importing Invoices [ID 1381400.1]
Regards,
Ivruksha -
HOW TO RESTRICT DISCARD BUTTON AT R12 INVOICE LINES TAB?
Hello
Can someone tell me how to lock/restrict the DISCARD Button at the Invoice Lines tab?
thanks
emgeeHopefully you can achieve the same using forms personalization by setting the required field (DISCARD) to FALSE or HIDDEN.
Thanks and Regards
Manish Jain.
Edited by: Jain, Manish on Jul 12, 2010 8:58 AM -
Missing information when updating invoice line
Dear all,
I am updating invoice line information but system giving and error
declare
begin
for rec in (select l.*
from ap_invoices_all l
where invoice_num = 'akp/445'
and vendor_id = 1068
and org_id = 82) loop
AP_INVOICES_PKG.Update_Row(X_Rowid => 'AABDoVAGSAACZlRAAM',
X_Invoice_Id => rec.invoice_id,
X_Last_Update_Date => rec.last_update_date,
X_Last_Updated_By => rec.last_updated_by,
X_Vendor_Id => rec.vendor_id,
X_Invoice_Num => rec.invoice_num,
X_Invoice_Amount => rec.invoice_amount,
X_Vendor_Site_Id => rec.vendor_site_id,
X_Amount_Paid => rec.amount_paid,
X_Discount_Amount_Taken => rec.discount_amount_taken,
X_Invoice_Date => sysdate,--rec.invoice_date+30,
X_Source => rec.source,
X_Invoice_Type_Lookup_Code => rec.invoice_type_lookup_code,
X_Description => rec.description,
X_Batch_Id => rec.batch_id,
X_Amt_Applicable_To_Discount => rec.amount_applicable_to_discount,
X_Terms_Id => rec.terms_id,
X_Terms_Date => rec.terms_date,
X_Goods_Received_Date => rec.goods_received_date,
X_Invoice_Received_Date => rec.invoice_received_date,
X_Voucher_Num => rec.voucher_num,
X_Approved_Amount => rec.approved_amount,
X_Approval_Status => rec.approval_status,
X_Approval_Description => rec.approval_description,
X_Pay_Group_Lookup_Code => rec.pay_group_lookup_code,
X_Set_Of_Books_Id => rec.set_of_books_id,
X_Accts_Pay_CCId => rec.accts_pay_code_combination_id,
X_Recurring_Payment_Id => rec.recurring_payment_id,
X_Invoice_Currency_Code => rec.invoice_currency_code,
X_Payment_Currency_Code => rec.payment_currency_code,
X_Exchange_Rate => rec.exchange_rate,
X_Payment_Amount_Total => rec.payment_amount_total,
X_Payment_Status_Flag => rec.payment_status_flag,
X_Posting_Status => rec.posting_status,
X_Authorized_By => rec.authorized_by,
X_Attribute_Category => rec.attribute_category,
X_Attribute1 => rec.attribute1,
X_Attribute2 => rec.attribute2,
X_Attribute3 => rec.attribute3,
X_Attribute4 => rec.attribute4,
X_Attribute5 => rec.attribute5,
X_Vendor_Prepay_Amount => rec.vendor_prepay_amount,
X_Base_Amount => rec.base_amount,
X_Exchange_Rate_Type => rec.exchange_rate_type,
X_Exchange_Date => rec.exchange_date,
X_Payment_Cross_Rate => rec.payment_cross_rate,
X_Payment_Cross_Rate_Type => rec.payment_cross_rate_type,
X_Payment_Cross_Rate_Date => rec.payment_cross_rate_date,
X_Pay_Curr_Invoice_Amount => rec.pay_curr_invoice_amount,
X_Last_Update_Login => rec.last_update_login,
X_Original_Prepayment_Amount => rec.original_prepayment_amount,
X_Earliest_Settlement_Date => rec.earliest_settlement_date,
X_Attribute11 => rec.attribute11,
X_Attribute12 => rec.attribute12,
X_Attribute13 => rec.attribute13,
X_Attribute14 => rec.attribute14,
X_Attribute6 => rec.attribute6,
X_Attribute7 => rec.attribute7,
X_Attribute8 => rec.attribute8,
X_Attribute9 => rec.attribute9,
X_Attribute10 => rec.attribute10,
X_Attribute15 => rec.attribute15,
X_Cancelled_Date => rec.cancelled_date,
X_Cancelled_By => rec.cancelled_by,
X_Cancelled_Amount => rec.cancelled_amount,
X_Temp_Cancelled_Amount => rec.temp_cancelled_amount,
X_Exclusive_Payment_Flag => rec.exclusive_payment_flag,
X_Po_Header_Id => rec.po_header_id,
X_Doc_Sequence_Id => rec.doc_sequence_id,
X_Doc_Sequence_Value => rec.doc_sequence_value,
X_Doc_Category_Code => rec.doc_category_code,
X_Expenditure_Item_Date => rec.expenditure_item_date,
X_Expenditure_Organization_Id => rec.expenditure_organization_id,
X_Expenditure_Type => rec.expenditure_type,
X_Pa_Default_Dist_Ccid => rec.pa_default_dist_ccid,
X_Pa_Quantity => rec.pa_quantity,
X_Project_Id => rec.project_id,
X_Task_Id => rec.task_id,
X_Awt_Flag => rec.awt_flag,
X_Awt_Group_Id => rec.awt_group_id,
X_Pay_Awt_Group_Id => rec.pay_awt_group_id,
X_Reference_1 => rec.reference_1,
X_Reference_2 => rec.reference_2,
X_Org_Id => rec.org_id,
X_global_attribute_category => NULL,
X_global_attribute1 => NULL,
X_global_attribute2 => NULL,
X_global_attribute3 => NULL,
X_global_attribute4 => NULL,
X_global_attribute5 => NULL,
X_global_attribute6 => NULL,
X_global_attribute7 => NULL,
X_global_attribute8 => NULL,
X_global_attribute9 => NULL,
X_global_attribute10 => NULL,
X_global_attribute11 => NULL,
X_global_attribute12 => NULL,
X_global_attribute13 => NULL,
X_global_attribute14 => NULL,
X_global_attribute15 => NULL,
X_global_attribute16 => NULL,
X_global_attribute17 => NULL,
X_global_attribute18 => NULL,
X_global_attribute19 => NULL,
X_global_attribute20 => NULL,
X_calling_sequence => null,
X_gl_date => rec.gl_date,
X_award_Id => rec.award_id,
X_approval_iteration => rec.approval_iteration,
X_approval_ready_flag => rec.approval_ready_flag,
X_wfapproval_status => rec.wfapproval_status,
X_requester_id => rec.requester_id,
X_quick_credit => rec.quick_credit,
X_credited_invoice_id => NULL,
X_distribution_set_id => NULL,
X_FORCE_REVALIDATION_FLAG => NULL,
X_CONTROL_AMOUNT => NULL,
X_TAX_RELATED_INVOICE_ID => NULL,
X_TRX_BUSINESS_CATEGORY => NULL,
X_USER_DEFINED_FISC_CLASS => NULL,
X_TAXATION_COUNTRY => NULL,
X_DOCUMENT_SUB_TYPE => NULL,
X_SUPPLIER_TAX_INVOICE_NUMBER => NULL,
X_SUPPLIER_TAX_INVOICE_DATE => NULL,
X_SUPPLIER_TAX_EXCHANGE_RATE => NULL,
X_TAX_INVOICE_RECORDING_DATE => NULL,
X_TAX_INVOICE_INTERNAL_SEQ => NULL, -- bug 8912305: modify
X_QUICK_PO_HEADER_ID => NULL,
x_PAYMENT_METHOD_CODE => rec.payment_method_code,
x_PAYMENT_REASON_CODE => null,
X_PAYMENT_REASON_COMMENTS => null,
x_UNIQUE_REMITTANCE_IDENTIFIER => null,
x_URI_CHECK_DIGIT => null,
x_BANK_CHARGE_BEARER => null,
x_DELIVERY_CHANNEL_CODE => null,
x_SETTLEMENT_PRIORITY => null,
x_NET_OF_RETAINAGE_FLAG => null,
x_RELEASE_AMOUNT_NET_OF_TAX => null,
x_PORT_OF_ENTRY_CODE => null,
x_external_bank_account_id => null,
x_party_id => null,
x_party_site_id => null,
x_disc_is_inv_less_tax_flag => null,
x_exclude_freight_from_disc => null,
x_remit_msg1 => null,
x_remit_msg2 => null,
x_remit_msg3 => null,
x_remit_to_supplier_name => null,
x_remit_to_supplier_id => null,
x_remit_to_supplier_site => null,
x_remit_to_supplier_site_id => null,
x_relationship_id => null,
x_original_invoice_amount => null,
x_dispute_reason => null);
commit;
end loop;
exception
when others then
dbms_output.put_line(sqlerrm);
end;
ORA-20001: APP-SQLAP-10000: ORA-01403: no data found occurred in
AP_INVOICES_PKG.UPDATE_ROW<-
with parameters (X_Rowid = AABDoVAGSAACZlRAAM, X_invoice_id = 180867)
while performing the following operation:Hi;
Please review:
R12: Validate Invoice Errors APP-SQLAP-10000, ORA-01403 and ORA-20001 [ID 1308869.1]
R12: Master Note: Consolidated Error Notes Of EBTax Related Issues In Oracle Payables [ID 1378068.1]
By the way If you make search at metalink such as APP-SQLAP-10000: ORA-01403: ORA-20001 there are 38 doc avaliable, please review them
Regard
Helios -
How to split a line item to 2 line item.
Hi all !
I have a request, help me please !
In system I have a invoice with 1 line item value 1000 USD.
Customer payment 600$. a incoming payment with value 600$ will post to system.
I want incoming payment and invoice will auto clear 600$ but system can't auto clearing because value is not Identical.
I want line item of invoice will split to 2 line item. Line item 1 value 600$ and line item 2 value 400$.
Line item 1 of invoice will auto clear with incoming payment and system will exist a invoice with 1 line item value 400$.
How to split a line item to 2 line item ? Have FM for split a line item to 2 line item in SAP ?
If you have other solution for this request, help me please !
Thanks !Hi,
Have a look at Split line item - Sales Order
Regards -
SRKIM:R12:AP: IMPORT 를 수행 하여 INVOICE 생성 시 DISTRIBUTION LEVEL 의 DFF 값이 생성 안됨
PROBLEM
R12.0.5:
Payables Module 에서 Payables Open Interface Import Process (APXIIMPT) 를 통해 invoice 생성 시 distribution level 의 DFF 정보를 interface table 에 load 하였으나 실제 invoice 생성 시에는 해당 값들이 invoice table 로 넘어 오지 않았다.
SOLUTION
해당 ISSUE 는 Bug 6837035 R12 : CANNOT TRANSFER DFF FROM AP INTERFACE INTO AP THEN INTO PROJECT 에 의한 것으로 아래와 같이 작업 하여야 한다.
1. Patch 6837035 를 DOWNLOAD 받아 TEST INSTANCE 에 적용 한다. PATCH DOWNLOAD 시 요구 되는 PASSWORD 는 Oracle Support engineer 로 부터 전달 받는다.
2. File version 이 patch 로 인해 정상적으로 upgrade 되었는지 확인 한다.
strings -a $XX_TOP/filename |grep '$Header'
위의 명령어를 써서 다음 files version 을 확인 하면 된다.
ap patch/115/import/US ap12apc.ldt 120.1.12000000.4
ap patch/115/sql apamtpob.pls 120.43.12000000.8
ap patch/115/sql apamtrcb.pls 120.45.12000000.7
ap patch/115/sql apiindib.pls 120.59.12000000.13
ap patch/115/sql apmatchb.pls 120.54.12000000.16
ap patch/115/sql apothmtb.pls 120.19.12000000.3
ap patch/115/sql aprcvmtb.pls 120.59.12000000.8
3. Patch 가 정상적으로 적용 된 것이 확인 되면 System Administrator Responsibility >Applications >Profile> System 화면에서 AP: Copy Invoice Lines DFF Profile 을 조회 하여 Value 를 Distributions 으로 설정 한다.
4. Profile 설정 후 다시 Import program 을 수행 하여 DFF값이 정상적으로 생성되는지 확인 한다.
Reference
Note. 784615.1 - Imported Invoices Are Not Created with DFF Information At Distribution Level -
Hi All,
I just want to know how to update INVOICE LINE table by using any interface or by any API.
Please need urgent.Hi;
All APIs are listed in Oracle Integration Repository
http://irep.oracle.com/index.html
API User Notes - HTML Format [ID 236937.1]
R12.0.[3-4] : Oracle Install Base Api / Open Interface Setup Test [ID 427566.1]
Oracle Trading Community Architecture API User Notes, June 2003 [ID 241320.1]
Technical Uses of Customer Interface and TCA-API [ID 269121.1]
Pelase also check below:
Api's in EBS
Re: Api's in EBS
http://sairamgoudmalla.blogspot.com/2009/05/script-to-find-oracle-apis-for-any.html
API
Fixed Asset API
List of API
Re: List of APIs
Oracle Common Application Components API Reference Guide
download.oracle.com/docs/cd/B25284_01/current/acrobat/jta115api.pdf
List of APIs and open interface R12
Re: List of APIs and open interface R12
Regard
Helios -
Error when discarding an invoice line
Hi ,
when i am trying to discard line in a validated invoice to correct its default account i get the following error "Cannot Discard the invoice line because a required call to tax calculation failed due to : &REASON"
will someone tell me what could be that for , as we are not applying tax in the system .
Thanksmiro_feps wrote:
Hi ,
when i am trying to discard line in a validated invoice to correct its default account i get the following error "Cannot Discard the invoice line because a required call to tax calculation failed due to : &REASON"
will someone tell me what could be that for , as we are not applying tax in the system .
Thanks
Please see the following docs.
R12: Unable to Discard Invoice Line where Distributions are Reversed - Required call to tax calculation failed due to: &REASON FRM-50016 (Doc ID 982162.1)
APXINWKB Cannot Discard The Invoice Line Required Call Tax Calculation &REASON (Doc ID 1333484.1)
Troubleshooting Assistant: Oracle Payables (AP) Invoice Cancel and Discard (Doc ID 1561330.2)
Thanks,
Hussein -
Hello,
Is there any standard routine to split invoices based on diffrent payement terms in line item. Tried with standardData VBRK/VBRP - 006 in VTFL but that does not check the payment terms which is mentioned inside the code.
Please help
Reagards,
NiteshDear,
May be it will help you. Please go via this link,
[Is it possible to split invoice Item category wise?;
[Split invoice Item category wise;
[Invoice split;
Regards,
Sandip -
Document splitting generates lines with alternating +/- signs
Hi,
While trying to post GR through MIRO, I am getting a message like "Document splitting generates lines with alternating +/- signs", please clarify why this error is coming.
But I am able to post the moment I am deleting a small amount from planned delivery cost field. Why this is happening, can anyone explain pls.
Regards,
AbHi
We have the same message but we want to clear two FI invoices
Did you ever find out what caused this message?
Regards
Paddi -
Is it possible to split invoice Item category wise?
Is it possible to split invoice Item category wise
In trx VTFA (if your billing is sales order based) choose your billing type and SO type, there select your item categories and there select the field VBRK/VBRP data. In that field you will see the currently used routine. With the help of your ABAP guy create a copy of that routine under a different number and add your lines of code. Let's say you use routine 001.
FORM DATEN_KOPIEREN_001.
Header data
VBRK-xxxxx = ............
Item data
VBRP-xxxxx = ............
Additional split criteria
DATA: BEGIN OF ZUK,
MODUL(3) VALUE '001',
VTWEG LIKE VBAK-VTWEG,
SPART LIKE VBAK-SPART,
END OF ZUK.
ZUK-SPART = VBAK-SPART.
ZUK-VTWEG = VBAK-VTWEG.
VBRK-ZUKRI = ZUK.
ENDFORM.
This is how it should look after modification:
Header data
VBRK-xxxxx = ............
Item data
VBRP-xxxxx = ............
Additional split criteria
DATA: BEGIN OF ZUK,
MODUL(3) VALUE '001',
VTWEG LIKE VBAK-VTWEG,
SPART LIKE VBAK-SPART,
PSTYV LIKE VBAP-PSTYV, <- New line
END OF ZUK.
ZUK-SPART = VBAK-SPART.
ZUK-VTWEG = VBAK-VTWEG.
ZUK-PSTYV = VBAP-PSTYV. <- New line
VBRK-ZUKRI = ZUK.
ENDFORM.
After this routine is created and activated place it as the default copy control routine instead of the old ones -
Hi,
How to setup and Initiate the Invoice approval at Invoice line level in R12
Regards,
SwaroopaAFAIK, you can do Line-level approval only for self service invoices that are matched to a purchase order.
You can confirm this from Oracle.
Sandeep Gandhi -
PAAPINVW -- how to fetch values for invoice line level details
My requirement is such that we define one of our account segments at invoice line dff's while creating the invoice against a project. So the ccid would need to driven from this invoice line dff, to be complete and valid.
Project Supplier Invoice Account Generator (PAAPINVW) has already defined attributes for Invoice Header DFF's and Invoice Distribution level DFF's; but Invoice line level DFF's have not been defined.
Also there are no attributes that would help me query the invoice line to fetch these details.
Working on this workflow in R12. Has anyone tried to fetch any sort of details from invoice lines, using any existing attributes in PAAPINVW; or has anyone done something in accordance to this??
Looking for suggestions.. have anyone faced a similar situation before??Hi user;
Pelase check below note cause and solution part please,which at least can gives u some ideas
Projects Supplier Invoice Account Generation Error: APP-SQLAP-97734: The System Cannot Generate Distributions [ID 823787.1]Regard
Regard
Helios -
XML INVOICE Report RAXINV, Taxline is repeating for each invoice line
Hi Tim
Thanks a lot for your blog
Greeting !!
I have successfully created XML report for AR invoice Printing learning from your blog but stuck to a problem , whenever Invoice is having multiple lines ,say 20, then for each invoice line there is tax line printing 20 times like this:
PART NO.| CUSTOMER PART#/DESCRIPTION | UNIT PRICE | QUNTITY|
A123 | 34 WELD-ROD | 52 | 22 |
Tax Exempt @ 0.00
A234 | 238-AL WIER | 63 | 55 |
Tax Exempt @ 0.00
........ Assume there are 20 lines then tax line also repeating 20 times which i don't want .It should get printed only once if it is same
pls help me to achieve this
Thanks
RahulThanks Tim for Your Instant reply.
I have gone through your duplicate line elimination but my requirement is not this
I'll explain it, I am using LINE_DESCRIPTION tag for printing item description and this tag have two value for it, when the LINE_TYPE =LINE then LINE_DESCRIPTION tag is printing the line description and if LINE_TYPE =TAX
then LINE_DESCRIPTION tag is printing the taxline information. Now if I have 20 lines in Invoice then the tax line will also repeat for 20 times, and if i use duplicate line elimination logic and I have same item it'll not print that item, some times whole invoice become blank.
So I want to print 20 lines and out of that 15 lines are have same tax rate then it should print once at the end of 15th line and for remaining 5 lines if tax rate is different for each line then it should print at the end of each line (5lines)
In the linetreevariable i used <xsl:variable xdofo:ctx="incontext" name="invLines" select=".//G_LINES [LINE_TYPE!='FREIGHT']"/> i.e. I want only line type=LINE and TAX
Thanks
Rahul -
Hi,
I have an issue in split invoicing.
Here is the scenario:
If we have indicated purchase condition for split invoicing (for
example excise tax) we dont want to post them to inventory , i
want to configure an offset condition .In the system i configred
2 cond type for +ve and -Ve.Also configured Act key and Accruals
I used AltCty 409 but i do not get the result..
So Can anyone tell me that how to configure in condition type and
how it works....
Thanks in advance.
NitinHi.
Do not use the alternate condition formula for alternative calculation type. Already you have used the account key and accrual key.
You can use either of the one.
Either you can use accrue key or account key.
Accrual key generally used for freight and freight related cost.
I would suggest use the account key and you need to assign the account key to the condition type in the OB40.
Try this it may resolve your issue. If it helps award me.
Cheers
Umakanth.
Maybe you are looking for
-
Slow wifi on time capsule - 1st generation
Connection 802.11 N - Cox ISP -- I am getting 98mb down directly out of the cable modem. However on WIFI my speed is cut nearly in one-half -- 54 mb down. I have reset the time capsule (version 1). I checked on 2 MacBook Pros (10.6.8) and both
-
I am using 9ids. All reports are run from form in internet explorer. by using web.show_document(); all are working fine and reports are too running very good. now i have created a hyperlink in one report using text item,to run another report. in hype
-
How to put a Dashboard with Prompts in the Cache?
Hi, I want to make Dashboards more efficiently by putting them in the Cache, but they have defined lot of prompts that can take several values. How should I proceed so as the the cache generated contains data required for this dashboards no matter th
-
I got a Qosmio G50-12f n : PQG55E-04C02YFR The problem is: when I plug on the dc power I got a white light on the dc plug picture and a orange light on the battery picture. When I want to power on the laptop, the white light turn off 1 second (maybe)
-
Hi, While tryign to download the SAP Note "1300023", the system gave a message "System setting does not allow changes to be made to object NOTE 0001300023". On further checking the details we got the details "If you want to edit the object NOTE 00013