AR Invoice Presentation / Invoice Lines diff than Sales Order Lines

Question

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

Answer 1

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