Issue in XML Invoice lines

Hi,
I designed layout for invoice report in xmlp 5.6.2, I have issue when i preview the output, instead of two Invoice lines i am getting 8 times with the repeating of 2 lines.I given the following tags....
Before line : <?for-each:G_INVOICE_LINES?>
End of lines : <?end for-each?>
waiting for tips.
Regards
Prabusiva

Hi Tim/Andrew,
I have only 2 lines for the invoice but when i run the preview in pdf, this 2 lines repeating 4 times. so far i am getting 8 lines.
This is the following tags for lines part
<LIST_G_INVOICE_LINES>
<G_INVOICE_LINES>
<LIST_G_LINE_ALLOC> </LIST_G_LINE_ALLOC> <LIST_G_LINE_COMMENT> /LIST_G_LINE_COMMENT> <LIST_G_LOT_NO_IN_LOTS> </LIST_G_LOT_NO_IN_LOTS>
</G_INVOICE_LINES>
</LIST_G_INVOICE_LINES>
In the RTF template in the starting line i given this <?for-each:G_INVOICE_LINES?> and end of the line i given this <?END FOR-EACH?>
Still i showing only 8 lines but i want to display only 2 lines.
Can any one know please drop your ideas.
with cheers
prabu

Similar Messages

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
Rahul

Thanks 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

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

AP: Invoice Imports/ Miscellaneous Invoice Line types

Hi All,
I had two issues while I was importing my invoices in AP through AP Invoices Open interface:
1. Freight Charges
2. Some Unit Royality Charges.
Both of these things are not included in my PO, so I needed to create additonal invoice distribution lines with in the same invoice and also had to assign a GL account while creating the invoices. The other Item type lines get the GL account code from PO while matching is done during AP Open Import process.
The Freight charges problem is resolved. The solution for that is as follows for your reference.
Functional Steps:
1. With Accounts Payables Manager responsibility , go to
Setup->Options->Payables.
2. Select Invoice from drop down list box.
3. In invoice region Ceck the Automatically Create Freight Distribution Option.
4. Supply default Freight Account for Freight Distributions.
Technical Steps:
1. Create an additional Invoice distributions line for freight in AP_INVOICE_LINES_INTERFACE table which should not have the PO level information.
2. Set AP_INVOICE_LINES_INTERFACE.Prorate_across_flag = 'Y'
3. AP_INVOICE_LINES_INTERFACE.line_type_lookup_code = 'FREIGHT'
4. Set AP_INVOICE_LINES_INTERFACE.LINE_GROUP_Number as same in both the ITEM and Freight Invoice distribtuion line which are interrelated.
The above resolves the Freight issue and you can reproduce it in your environment.
However, I have another amount from my supplier which is called "Royality Charge" on every item which are also not present in my PO. My supplier sends these charges with Invoice lines the same way Freight charges are sent. I am thinking of creating additional Invoice lines marked as "Miscellaneous" Invoice Lines type for this charge. The problem I am facing with Miscellaneous Lines is that I cannot find a place where I can setup the Account code for such Invoice distribution lines, like I got for Freight Type Distribution lines as described above in Functional steps. Can anyone guide me in this regard or can give me an alternative workaround to handle my Unit Royality Charges?
Thanks
Faisal .
[email protected]
null

Apologies for the late response, have only just spotted the question.
You will need to register "line-item job-level chains of approval" under payables transaction type before you can select it from the picklist:
Setup\Action Types\"Use Existing Action Type" button, then select action type and continue.
Hope this helps (if you haven't already resolved yourself)
James

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 AM

Hi 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

Insert/Update/Delete Non-PO Invoice Line Item via FM/BAPI?

Does anyone know of a way to insert/update/delete an Invoice Line item (Non-PO Accounting Invoice - Transaction FB60 or FV60) using a BAPI or Function Module (or set of function modules) using ABAP? I have been trying to find some code to accomplish this and am stuck on a couple of issues.
I have found PRELIMINARY_POSTING_FB01 and PP_CHANGE_DOCUMENT_ENJ but both seem to submit the details to background processes. This is an issue because it gives the user a success message after execution but later delivers the error to Workflow. This is for an interfacing program so the results should be as real time as possible.
Has anyone accomplished this via FM or BAPI and if so would you mind sharing your experiences?
Thank you very much,
Andy

SG- Thank you for the reply.
I have been playing with BAPI_INCOMINGINVOICE_PARK and I'm not sure if it is doing exactly what we want, but it is something that I have considered in the past. I plan on looking into BAPI_ACC_INVOICE_RECEIPT_POST this morning, hopefully that will provide some more for us.
If possible I'd like to avoid BDC sessions because this program could hypothetically interface with multiple SAP systems with different configurations.
I will check into those FM's and thank you very much.

Printing fixed number of Invoice Line in rtf template with level two group

Hi,
I have to print fixed number of invoice lines on a page. Invoce tempalte design has a table with header and summary(Invoice , tax and shiping totals) at each page in table footer. The table should repeate at each page with header and footer. I need to print specific number of rows or number of rows wihich page can accumulate in table body on each page.
I checked few blogs giving solution for fixed number of rows printing say
"Anatomy of a Template I - Fixed Row Enumeration"(http://blogs.oracle.com/xmlpublisher/2007/03/27/)
and
http://oracle.anilpassi.com/xml-publisher-developing-reports-printed-on-pre-printed-stationary-2.html
Above two blogs explanation has only one group at line level. but in my case there are two groups (Parent and child) at line level. I am able to count rows in parent group but it is not counting lines in child group.
Edited by: Bhanu Yadav on Apr 19, 2011 2:10 AM

Will it be possible for you to move the 1st and 3rd sections to header/footer?
So that if the 2nd section spills over to next page too, starting position of 3rd section wont be affected.

Credit Memo DFF does not contain information from the original invoice line

Hi
Customer is facing issue mentioned in Note: 364999.1
Issue: Created a credit memo against the invoice and noticed that the resulting credit memo lines do not contain the DFF information from the original invoice lines.
I found through Metalink that this issue was reported to Oracle for release 11.5.7.
Looks like the fix was to provide a check box in RAXSUMSC.fmb.
- One off Patch for 11.5.7 - Bug / Patch 2803629 (one-off patch)
- One off Patch for 11.5.8 - Bug / Patch 3411221 (one-off patch)
- 11.5.9 - nothing available !!!!
As per bug 2675652 the issue was fixed in a file RAXSUMSC.fmb, version 115.41 This BUG shows that it has been fixed by in 11.5.10
Customer is using 11.5.9 which has RAXSUMSC.fmb, version 115.40, we cant apply patches for 11.5.7 or 11.5.8 that are available.
Any pointers on what can be done ?
Thanks,

Hi Pat,
the project code (PC) on the marketing document may only be applied to the business partner (BP), hence the only row in the associated journal entry (JE) with this project code is that of the BP.
You can link project codes to specific accounts (CoA -> select account -> account details -> project code) & this project code will then be assigned every time the account is found in a JE.
If you require the project code to be applied to the freight, you may assign this project code to the account you have defined for this freight. The drawback is naturally that the project code will then be pulled every time this freight is used, regardless of whether or not the PC is associated with the BP or not.
It is possible to manually assign project codes to every row in a journal entry, hence this should also be possible with SDK. You might explore the possibility whether it might be possible to automatically assign the BP PC to all rows in the JE using a script.
All the best,
Kerstin

Invoice line items - inconsistant data returned from RV_BILLING_PRINT_VIEW

Hi there,
We are using a modified version of SAP standard Print Program RVADIN01 for our invoices, for many years now.
Everything works fine 99.9% of the time. Every now and again though, there is issue with the invoice, the root of which is data brought back from RV_BILLING_PRINT_VIEW .
From debugging the latest issue, I can see that the standard FM RV_BILLING_PRINT_VIEW, which is bringing back data for line items, is not filling all the data in certain cases.
For example, yesterday we had an invoice with 10 line items - this FM brought back full data for 9 line items, but the first was missing data in fields such as LAND_WE, SPRAS_WE etc. This then lead to a problem with text being read from T604T for that line.
I've checked that data being sent to RV_BILLING_PRINT_VIEW, and it looks correct.
I've checked and been assured that Master data is maintained correctly etc.
Does anyone have any thoughts on this or experience of something similar?
Thanks,
David

Hi Vijaymadhur,
Thanks for your response - I checked again in VF03, and the Ship-to is maintained for this line.
Infact, the second invoice line is almost identical to the first (except for quantity) and the FM brings back the correct ship-to etc. for that line.
Thanks,
David

Invoice line items report from DSO compared to Infocube (in HANA)

Hi Folks,
As you know Invoice line items are very granular level information. We are facing performance issues on reports based on the Infocubes to display this information. We are migrating to HANA and looking for options to improve the performance. One of the option we are looking at is instead of Infocube can we we report directly on the DSO. I would like to know whether it will help and its Pro & Con's. Please help.
Thanks,
B

Hi B,
Reading data from a DSO instead of an InfoCube will not improve reporting performance. The benefit in getting rid of the cube is that you have less loading to do. You still need cubes for planning and inventory scenarios.
You do not need a composite provider to report from DSOs in BW. Once you've migrated to HANA you use DSOs just as you would today, and you can report from a multiprovider. Yes, you can use a composite provider, but it is not necessary.
If your report is slow today, you need to find out where it is slow. HANA could provide a huge benefit as soon as you migrate, or it might not help much. It depends on the scenario. OSS 1681396 is a good place to start.
If the DB time is long, and you're not using BWA today, you can expect big benefits when you migrate to HANA.
If the OLAP time is long, you might see big benefits when you migrate, as the OLAP engine during query execution is pushing more to HANA.
If the frontend time is long, migrating to a different database isn't likely to change that, you'd need to address that separately.
Finally, an important point to remember is that once you've migrated you open up additional possibilities for improvement that are not available to you in BW-on-non-HANA. For example, you might be able to rewrite queries as HANA models. I did some performance tests on this in a very simple case of exception aggregation.

XML Invoice - help with Tax Summary

I've been tasked to modify an already modded XML Invoice using XMLP. I need to add a Tax Summary block at the bottom, showing the breakout of the tax codes and amounts charged on the invoice.
I've played around with it, but so far I can only get the first tax line to show up. I can't get the others. I need to insert a conditional, but I don't know how or where.
Has anyone run into anything like this before?
This probably isn't the best problem summary... but if you could help I'd appreciate it!

Hi,
It sounds like you need to use a for-each to show each of your tax lines. If you do not have the for-each XMLP will only show the first tax line that is hits in the XML Output.
Would suggest that you take a quick look at the XMLP User Guide documentation for more information on how to use for-each.
Let me know if this does not solve your problem, or if you are still struggling.
Regards,
Cj

While merging lines in prepare mass additions invoices lines do not appear

Hello,
I am facing an issue in merging mass additions line. I dont see any lines to merge even though many invoice line exist. I even tried query mode where i query the lines based on the invoice number but still lines do not appear for merge.
detailed steps:
Press open button on an oh hold item in the mass additions summary window.
Enter additional information and select done.
Back in the mass additions summary window, pick the first mass addition item again and press 'merge'
button.
Select the other new mass additions items that you want to merge into one asset.
-> Problem, the other new items do not appear for selection.
It was working fine till few months back but seems some patch have created this issue. Have you faced such issue?
We are on 12.0.6.
Any pointer is helpful.
Regards
Bipin

I wish I had a 10.3.9 machine to check, but, since your video card should definitely be up to the task, I think it's probably going to be that Keynote's having a unique problem with your setup. In Keynote, under the Keynote menu, choose "Provide User Feedback" and send your problem to Apple. It could be that it may not have been reported yet.

Retention line doesn't contain the VAT code in the invoice lines.

Hi,
I am facing a problem where in invoice with the retention doesn't carry a VAT code in the invoice line level details.Though there are other draft invoices which contains the VAT code for the retention line.
I have checked the Billing Setup-->Retention-->Output Tax Code.It contains a VAT code which is visible for all the other draft invoices which have retention.
I have also checked the Tax codes defined in the Project Implemnetion options.
These were the two things which I found from the user guide.
Can somebody guide me if I am missing out something?
Thanks,
Tanvi

Hi,
According to your description, my understanding is that the print function of IE8 doesnot print the whole content of SharePoint list item.
For troubleshooting your issue, please turn off Protection Mode for the IE8.
You can refer to the thread:
https://social.technet.microsoft.com/Forums/en-US/b8ab8f65-9b27-4a90-9323-0ca5b7e4466e/print-preview-print-of-web-pages-doesnt-work-in-ie8?forum=w7itproperf
Best Regards,
Eric
Eric Tao
TechNet Community Support

Issue in Split invoicing

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.
Nitin

Hi.
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.

AR Invoice Presentation / Invoice Lines diff than Sales Order Lines

Hi,
Due to business rules I got the following requirement, I'd like to get advice or second opinions please:
Instead of showing 200 lines we want to show 1 line in the invoice summarizing the job done.
The requirement is:
The invoice should summarize the Order Lines, meaning that we want to have different lines in the invoice than those in the orders composing the invoice. The total amounts must equal between both, the invoice and the orders lines been invoiced.
For example:
We need to create an Invoice for 2 Sales orders with 10 lines each, each line for $1 usd.
The invoice could be in any of these situations:
- Having only one line composing the 2 orders. The invoiced amount is $20.
- Having 2 lines composing the 2 orders. The invoiced amount is $20 ($10 line 1, $10 line 2)
The description on the invoice lines must be completly open.
Internaly, the link/reference between the invoice line and the order line(s) composing it must be kept.
This must work with 1 or more Sales Orders (partial or complete)
Can be done via autoinvoice or not. (The user is able to compose and reference the invoice manually)
¿Is there already something done that I can use? Just point me on one direction and I'd be happy to investigate.
I already have 1 or 2 ideas of how to achieve this without customizing at all.
Just wanted to check and get advice and second opinions on this before taking a decision.
Technical Spec:
Oracle EBS 11i (11.5.10.2)
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0
Thanks in advance.
Juan Alcocer

seems to error
APP-AR-11526
ORA-28115
seems the security policy is implemented at your database leval and check which ID you are using to insert the record.Check with your DBA, for security to resolve first for ORA-28115.
Disabled in case if you have any custom triggers defined on RA_CUSTOMER_TRX_ALL.
Few Documentation for ORA-28115
ORA-28115 with EXEMPT ACCESS POLICY privilege
A user USER1 has been granted select, insert, update, delete on all
tables of an application schema (USER2) that uses row-level security.
The RLS policies cover select, insert, update, and delete, and have check option enabled. USER1 has also been granted EXEMPT ACCESS POLICY system privilege.
Each table in the USER2 schema has a trigger that causes insertion of
a row into an audit table whenever DML is performed. When USER1 performs DML on a USER2 table, the operation fails with

Issue in XML Invoice lines

Similar Messages

Maybe you are looking for