AP INVOICE작성중 PO MATCH시 ORA-01403 ERROR.

제품 : FIN_AP
작성날짜 : 2004-10-25
AP INVOICE작성중 PO MATCH시 ORA-01403 ERROR.
========================================
Problem Description
AP Invoice작성시 Tax Code를 User의 코드로 선택후 PO Match를 하게 되면
아래와 같은 Error Message가 뜨면서 전표가 생성이 않됨.
Tax Code가 VAT일 경우에는 PO Match 가 됨.
APP-SQLAP-10000: ORA-01403: no data found occured in
ap_matching_update_info<-AP_MATCHING_PKG.ap_match ...
Solution Description
Bug 2866764 이며, Financial Familypack F를 적용하면 해결됩니다.
개별 patch로는 나온 것은 없으나, Code Fix solution은
나와 있는 것이 있으므로, Oracle Support Center에 연락을
주시면, Code Fix Soluion을 제공받을 수 있습니다.
@00. This is not a patch
@ Please try on a TEST environment first
@ Any issue raised from not implementing correctly, is not supported.
@ Implement on file(s): apmatchb.pls 115.63
@ Re-implement everytime file(s) apmatchb.pls version changes via ADPATCH
@ Re-implement until file apmatchb.pls version is 115.66 or higher.
@01. Backup (Save a copy) fle $AP_TOP/patch/115/sql/apmatchb.pls
@02. Use Text Editor to edit file $AP_TOP/patch/115/sql/apmatchb.pls
@ This is the source code for Package Body AP_MATCHING_PKG
@03. Find the source code for procedure ap_matching_update_info
@04. Within this proceudre, Find the following text:
@<<
@ elsif ( l_tax_type = 'USE') THEN
@ /* Added this condition for bug 2162881 */
@ l_tax_recovery_rate := '';
@>>
@05. Change to the following. Noice the changes marked with the bug number:
@ Notice the new code line added, marked with the bug number.
@<<
@ elsif ( l_tax_type = 'USE') THEN
@ /* Added this condition for bug 2162881 */
@ l_tax_recovery_rate := '';
@ recoveryoverride_tab(i) := 'N'; -- bug 2866764
@>>
@06. Save changes / Save file.
@07. Recereate the package body AP_MATCHING_PKG in the APPS schema
@ using the recently modified file
@ .- Open a SQL*Plus session and log on to the database as the APPS user
@ $ sqlplus apps/apps
@ .- Run the modified file
@ SQL(APPS)> start $AP_TOP/patch/115/sql/apmatchb.pls
@08. Check for invalidated DB objects and use ADADMIN to recompile the
@ APPS schema if necessary.
@ .- Run ADADMIN using he same user used to apply patches (i.e. applmgr)
@ .- Choose the option 2. "Maintain DataBase Objects Menu"
@ .- Now, choose option 6. "Compile Apps schema"
@09. Retest functionality.

user9222525 wrote:
while create new vendor site . the error occurred as ‘validate_vendor_site ORA-01403’.ORACLE support said that's bug @ebs 12.1.1.Please see these docs.
Payment Workbench Error: ORA-01403 No Data Found (APXPAWKB.FMB) [ID 1303129.1]
ORA-01403: AP_VENDOR_PUB_PKG Procedure Validate_vendor [ID 553228.1]
When Entering Operating Unit (OU) for Supplier Gets Error ORA-01403 [ID 813205.1]
R12 Ora-01403 Error When Entering A New Uo For A Supplier [ID 843661.1]
CANNOT CREATE SUPPLIER SITE (ADDRESS) [ID 1069032.1]
but we can't apply the patch regarding of 'R12 Ora-01403 Error When Entering A New Uo For A Supplier [ID 843661.1].mht'What is the reason?
Thanks,
Hussein

Similar Messages

ORA-01403 error

hi
The user hsd encountered the error like "FRM 40735" POST QUERY TRIGGER RAISED AN UNHANDLED EXCEPTION
ORA-01403
iT COMES UNDER MATERIAL TRANSACTIONS FORM.
cAN YOU help me ?
Thanks,
aram

Aram,
ORA-01403http://www.orafaq.com/wiki/ORA-01403
FRM 40735" POST QUERY TRIGGER RAISED AN UNHANDLED EXCEPTIONPost your query in EBS forum -
https://forums.oracle.com/forums/forum.jspa?forumID=475
Regards,
Anuj

ORA-01403 error in designer

We are running OWB 10 on Oracle 10 ent. We are getting a 1403 err when we try to do pretty much anything in OWB. When I try to create a project we get OWB_NSFATAL_ERROR100ORA-01403: no data found. This also happens when we try to import target table metadata in OWB..... now I just tried the new project wizard again and it worked. I then went to import some table meta data and got the 1403 again. It seems to be intermittent. Anybody have any ideas?
Mark

To all that enter this thread...
Metalink could not tell me why we were getting the 1403 error. So I went to the all powerfull standby solution.... cycle the instance. The 1403 error has not been back since. All that I can think of was that there could have been an open session with an explicit row lock on some OWB table that held up metadata creation. I know if you kill your client session that connection lingers out there and OWB designer actually tells you what session to kill to clean it up. We have been paying close attention when a developer has to kill their OWB Client and kill their corresponding database session in OEM and the issue seems to have gone away. But before we didn't get any indication when there was a DB session that needed to be killed. Just watch for open sessions when you get this error.
That is all.

ORA-01403: no data found in alert.log

Dear All,
I am getting ORA-01403: no data found in alert.log.Could you pls help me out what could be reasons behind it..Due to this i m getting loads of alerts.Pls suggest.
Thanks

ORA-01403 No Data Found
Typically, an ORA-01403 error occurs when an apply process tries to update an existing row and the OLD_VALUES in the row LCR do not match the current values at the destination database.
Typically, one of the following conditions causes this error:
Supplemental logging is not specified for columns that require supplemental logging at the source database. In this case, LCRs from the source database might not contain values for key columns. You can use a DML handler to modify the LCR so that it contains the necessary supplemental data. See "Using a DML Handler to Correct Error Transactions". Also, specify the necessary supplemental logging at the source database to prevent future errors.
There is a problem with the primary key in the table for which an LCR is applying a change. In this case, make sure the primary key is enabled by querying the DBA_CONSTRAINTS data dictionary view. If no primary key exists for the table, or if the target table has a different primary key than the source table, then specify substitute key columns using the SET_KEY_COLUMNS procedure in the DBMS_APPLY_ADM package. You also might encounter error ORA-23416 if a table being applied does not have a primary key. After you make these changes, you can reexecute the error transaction.
The transaction being applied depends on another transaction which has not yet executed. For example, if a transaction tries to update an employee with an employee_id of 300, but the row for this employee has not yet been inserted into the employees table, then the update fails. In this case, execute the transaction on which the error transaction depends. Then, reexecute the error transaction.
There is a data mismatch between a row LCR and the table for which the LCR is applying a change. Make sure row data in the table at the destination database matches the row data in the LCR. When you are checking for differences in the data, if there are any DATE columns in the shared table, then make sure your query shows the hours, minutes, and seconds. If there is a mismatch, then you can use a DML handler to modify an LCR so that it matches the table. See "Using a DML Handler to Correct Error Transactions".
Alternatively, you can update the current values in the row so that the row LCR can be applied successfully. If changes to the row are captured by a capture process at the destination database, then you probably do not want to replicate this manual change to destination databases. In this case, complete the following steps:
Set a tag in the session that corrects the row. Make sure you set the tag to a value that prevents the manual change from being replicated. For example, the tag can prevent the change from being captured by a capture process.
EXEC DBMS_STREAMS.SET_TAG(tag => HEXTORAW('17'));
In some environments, you might need to set the tag to a different value.
Update the row in the table so that the data matches the old values in the LCR.
Reexecute the error or reexecute all errors. To reexecute an error, run the EXECUTE_ERROR procedure in the DBMS_APPLY_ADM package, and specify the transaction identifier for the transaction that caused the error. For example:
EXEC DBMS_APPLY_ADM.EXECUTE_ERROR(local_transaction_id => '5.4.312');
Or, execute all errors for the apply process by running the EXECUTE_ALL_ERRORS procedure:
EXEC DBMS_APPLY_ADM.EXECUTE_ALL_ERRORS(apply_name => 'APPLY');
If you are going to make other changes in the current session that you want to replicate destination databases, then reset the tag for the session to an appropriate value, as in the following example:
EXEC DBMS_STREAMS.SET_TAG(tag => NULL);
In some environments, you might need to set the tag to a value other than NULL.

ORA-01403: no data found in apply at bi -direction stream

Hi Experts,
we use 10g at window for bi direaction.
after building, I got ORA-01403: no data found in apply process. I check these error LCR
that invloved DML action for different tables in source database.
our stream a schema level capture and no error handle as well as other exception.
former DBA set up this tream.
I just check online got these info.
ORA-01403 No Data Found
An ORA-01403 error message is generated when an Apply process tries to update an existing row and the old_values in the row LCR do not match the current values at this destination database object.
This situation could arise on account of any of the situations below:
Supplemental logging is not specified for columns that require supplemental logging at the source database. In this case, LCRs from the source database may not contain values for key columns.
There may be a problem with primary key in the destination table. If no primary key exists for the table or if the target table has a different primary key than the source table, substitute key columns can be specified using the set_key_columns procedure in the dbms_apply_adm package. Error ORA-23416 may be encountered if a table being applied does not have a primary key.
There is a data mismatch between a row LCR and the table for which the LCR is applying a change. In this case, the destination has to be updated to match the data values before the error transaction can be executed again.
what do i need to do?
Thanks,
Jim

It will be wise to run the Oracle supply streams health check script to check your existing streams environment.
From the result, you can also open a tar with Oracle to see if they can help you with the setup.
In addition to the ORA-01403 error, you can also run some of the Oracle Streams packages (Managing Apply Errors) to see the full detail of what is missing that caused the Ora-01403 error.
I will also try to implement a smoke test using the simple heartbeat table suggested by Oracle Streams, if that is working, then you can begin your full scale setup in your environment knowing that the base Streams Structure is setup correctly.
HTH

Forms application returns "ORA-01403 no data found" exception on Windows 7

Hi everyone,
I am currently involved in an application compatibility project for an O/S migration from Windows XP to Windows 7.
We have a legacy Oracle Dev6i P18 Forms application that has been working perfectly on Windows XP for the last decade or so. When we installed the same application on Windows 7, it returned a pop-up error message with the text: "ORA-01403 no data found" when performing a certain operation (clicking on a Submit button in a specific form). The same operation works successfully on Windows XP displaying the message "Submit has been successful".
This error is well documented and the solution involves adding an exception handler to the faulting SQL statement(s) in order to handle the ORA-01403 exception. Unfortunately, the application is composed of compiled forms (.FMX) and we no longer have the source code so I can't implement this solution.
I ran a file comparison utility (WinDiff from the Windows SDK) and confirmed that all the files in the application folder and the Oracle Dev6i P18 folder are identical on both the Windows XP and Windows 7 systems.
I enabled tracing in SQLNet.ORA by configuring TRACE_LEVEL_CLIENT=SUPPORT (I know, too verbose) and other related settings on both systems and have uploaded the traces to my SkyDrive for public viewing:
http://sdrv.ms/10BNYtI
The traces show that the "ORA-01403" exception occurs many times on both Windows XP and Windows 7 systems as a result of various SQL statements being executed, for instance:
SELECT TASK_ID,TASK_DETAIL_STATUS,ASSIGNED_DATE FROM TASK_DETAILS WHERE TASK_ID = :b1 AND TASK_DETAIL_STATUS = (SELECT ID FROM V_TASK_STATUS WHERE ABBREVIATION = 'PLANNED' ) FOR UPDATE OF TASK_DETAIL_STATUS,ASSIGNED_DATE
UPDATE TASK_DETAILS SET ASSIGNED_DATE=NTMS_UTIL.GET_SERVER_DATE,TASK_DETAIL_STATUS=(SELECT ID FROM V_TASK_STATUS WHERE ABBREVIATION = 'ASSIGNED' ) WHERE ROWID = :b1
ORA-01403: no data found.
So the same error happens on both Windows XP and Windows 7.
On Windows XP, the error is somehow handled, and does not cause the "Submit" operation to fail.
On Windows 7, however, the error bubbles to the surface and is displayed to the user, thus halting the "Submit" operation.

Thank you. I'm well aware that adding an exception handler is the classic solution to the ORA-01403 error. However, like I mentioned in my original post, I don't have the source code. All I have are the compiled .FMX forms so I can't implement such a solution:
From my original post:
This error is well documented and the solution involves adding an exception handler to the faulting SQL statement(s) in order to handle the ORA-01403 exception. Unfortunately, the application is composed of compiled forms (.FMX) and we no longer have the source code so I can't implement this solution.

ORA-01403 - Logical Standby Apply ends on delete/update statement

- This thread is relocated to this forum; advice from Daniel Roy -
After implementing 2 logical standby databases and running pretty smooth for a while 'strange' errors occur which puzzle me. Sometimes I skip a transaction or exclude a schema from replication and hold my breath for what next roars its ugly head.
Despite fulfilling all logical standby prerequisites and maintaining primary keys on tables I now run into ORA-01403 errors. The updated table only contains 1 row and has a foreign key to another small table.
I could instantiate these tables, but I want to understand why these errors occur and prevent them form happing or learn how to resolve them best.
Anyone around who dealt with these matters and won?
I'm running this implementation with Oracle 9.2.0.7 on Tru64 51.b
I'm able to create the logical standby databases manually and with aid of the Data Guard Creation Wizard (EM10g 10.1).
Can anyone also help me out with refining the faulty transaction from e.g. V$LOGMNR_CONTENTS? (Without disrupting the data guard setup).
I've already retrieved redo info from archivelogs, but there must be an easy way.
Regards,
Erik

Any way for you to turn tracing on for the DB where you see this ORA-01403 error? We could then probably find out exactly what goes wrong. It's very hard for us to know exactly what might be wrong, since we don't know your exact setup (except for this table). Let me know if that's not possible, and I could construct a logical DB setup to test (even tho it would be on Windows, I don't have Tru64).
Daniel

ORA-01403 :no data found in apex

dear all
Please, not to view this thread as the contents are same posted in another thread with a different subject.
i have a form with 6 regions.
in one of the region i place a button save.
i have a conditional process to insert the data in the table
after entering the data into the respective fields when i click the save button
it is giving this error.
ORA-01403: no data found
Error UNABLE TO INSERT
OK
what is this error why it is comming?
how to solve it? if anyone gives solution it would be a bright day for me.
Message was edited by:
srikavi

ORA-01403 occurs when an SQL SELECT statement written inside a PL/SQL proceedure/function etc is expected to return a row (or more) but doesn't.
So, your code to save might read along the lines of:
declare
bar number;
begin
select foo into bar from foobar where id=1;
insert into ... where id=bar;
end;
Now, if the SELECT statement didn't return a row (ie, in the example above there are no records with an id of 1) then you will get an ORA-01403 error.
Look at your proceedure for saving and run any select statements seperately in a SQL editor and check that all return one or more rows.

Import job failes with ORA-01403: no data found ORA-06512: at "SYSMAN.MGMT

Hello everyone,
I need a help on importing data from a schema in server 1 to the same schema in server 2 via network link. I receive following error when I try to submit a job on Enterprise Manager:
Import Submit Failed
ORA-01403: no data found ORA-06512: at "SYSMAN.MGMT_JOB_ENGINE", line 5806 ORA-06512: at "SYSMAN.MGMT_JOB_ENGINE", line 7812 ORA-06512: at "SYSMAN.MGMT_JOB_ENGINE", line 8608 ORA-01403: no data found ORA-06512: at "SYSMAN.MGMT_JOBS", line 273 ORA-06512: at "SYSMAN.MGMT_JOBS", line 86 ORA-06512: at line 1
Sql of the job:
declare
h1 NUMBER;
begin
h1 := dbms_datapump.open (operation => 'IMPORT', job_mode => 'FULL', remote_link => 'B_PROD_LINK', job_name => 'BIMPORTFRMPRDTORPT4', version => 'COMPATIBLE');
dbms_datapump.set_parallel(handle => h1, degree => 1);
dbms_datapump.add_file(handle => h1, filename => 'IMPORT.LOG', directory => 'DATA_PUMP_DIR', filetype => 3);
dbms_datapump.set_parameter(handle => h1, name => 'KEEP_MASTER', value => 0);
dbms_datapump.set_parameter(handle => h1, name => 'INCLUDE_METADATA', value => 1);
dbms_datapump.set_parameter(handle => h1, name => 'ESTIMATE', value => 'BLOCKS');
dbms_datapump.set_parameter(handle => h1, name => 'REUSE_DATAFILES', value => 0);
dbms_datapump.set_parameter(handle => h1, name => 'TABLE_EXISTS_ACTION', value => 'TRUNCATE');
dbms_datapump.set_parameter(handle => h1, name => 'SKIP_UNUSABLE_INDEXES', value => 0);
dbms_datapump.start_job(handle => h1, skip_current => 0, abort_step => 0);
dbms_datapump.detach(handle => h1);
end;
It says network link is active when I test the network link to make sure its connectivity. I create the network link as a system account. I'm trying to do an import from an Oracle database 10.2.0.2 to 11.2.0.1. My 10g database is on ms windows 2003x64 while my 11g database is on OEL 5.4x64.
What should I do for now?
Thank you.
Edited by: user12144220 on Nov 4, 2012 5:02 AM

It will be wise to run the Oracle supply streams health check script to check your existing streams environment.
From the result, you can also open a tar with Oracle to see if they can help you with the setup.
In addition to the ORA-01403 error, you can also run some of the Oracle Streams packages (Managing Apply Errors) to see the full detail of what is missing that caused the Ora-01403 error.
I will also try to implement a smoke test using the simple heartbeat table suggested by Oracle Streams, if that is working, then you can begin your full scale setup in your environment knowing that the base Streams Structure is setup correctly.
HTH

Ora-01403, AP_VENDOR_PUB_PKG

while create new vendor site . the error occurred as ‘validate_vendor_site ORA-01403’.ORACLE support said that's bug @ebs 12.1.1. but we can't apply the patch regarding of 'R12 Ora-01403 Error When Entering A New Uo For A Supplier [ID 843661.1].mht'

user9222525 wrote:
while create new vendor site . the error occurred as ‘validate_vendor_site ORA-01403’.ORACLE support said that's bug @ebs 12.1.1.Please see these docs.
Payment Workbench Error: ORA-01403 No Data Found (APXPAWKB.FMB) [ID 1303129.1]
ORA-01403: AP_VENDOR_PUB_PKG Procedure Validate_vendor [ID 553228.1]
When Entering Operating Unit (OU) for Supplier Gets Error ORA-01403 [ID 813205.1]
R12 Ora-01403 Error When Entering A New Uo For A Supplier [ID 843661.1]
CANNOT CREATE SUPPLIER SITE (ADDRESS) [ID 1069032.1]
but we can't apply the patch regarding of 'R12 Ora-01403 Error When Entering A New Uo For A Supplier [ID 843661.1].mht'What is the reason?
Thanks,
Hussein

Getting ORA-01403 in dba_segments query during a trigger

Hi, Everyone --
I need to set up a process which will automatically start Oracle auditing on a table when it's created on a particular tablespace.
I've created an "after create on database" DDL trigger which will fire when (ORA_DICT_OBJ_TYPE = 'TABLE').
In this trigger, I use the DBMS_STANDARD package trigger attribute functions in a query against the dba_segments view to check if the new
table has been created in the targeted tablespace. Here' the query:
SELECT DISTINCT s.tablespace_name
INTO tablespace_name
FROM sys.dba_segments s
WHERE s.owner = ORA_DICT_OBJ_OWNER
AND s.segment_name = ORA_DICT_OBJ_NAME
AND s.segment_type IN ('TABLE', 'TABLE PARTITION')
AND s.tablespace_name = target_tablespace_name;
The only purpose of this query is to make sure that that table is contained in the targeted tablespace identified by the "target_tablespace_name" constant variable used in the WHERE clause. If the query runs without error, then my trigger creates a DBMS_SCHEDULER job that executes an "audit" command to start Oracle auditing on the new table.
To test the trigger, within the trigger code, I put the query inside a PL/SQL block with a "WHEN OTHERS" exception clause that will send formatted error detail to the alert log. Then I successfully create a test table on the targeted tablespace. The trigger fires, but the output shows that the query in my trigger failed with an "ORA-01403: no data found" error, indicating that the dba_segments view contains no records showing that the new table is on the targeted tablespace.
But when, in an already opened PL/SQL session, I immediately run the same query (with the appropriate literals in place of the trigger attribute functions) then the query works with the name of the tablespace returned as expected!
I tried an experiment with the trigger running the same query against the dba_tables view instead of the dba_segments view. It worked without error. The only problem is that if your create a partitioned table, the "tablespace_name" column in the dba_table view is NULL (which makes sense when the various table partitions can be contained in different tablepsaces). So, unfortunately, in the case of creating partitioned tables, the purpose of the query would be defeated.
Why does the trigger work when it queries the dba_tables view, but fails when it queries the dba_segments view? Is there a timing issue which causes a lag between the time the table is created and the time that the dba_segments view is updated? Would the trigger fire inside this time lag, thus causing the dba_segments query to fail? Or is there another explanation?
Thanks in advance for any advice you can give me!

Hi, Solomon --
Thanks for the confirmation! I forgot to mention in my original post that I'm running this on 11.1.0.7.
To test the hypothesis that it's a timing issue, I put a hefty "for loop" before the dba_segments query in the code of the trigger. It caused the trigger to spin its wheels for a few seconds before it ran the query. But this didn't help, because I got the ORA-01403 error again.
So it must not be a timing issue after alll. Perhaps the dba_segments query isn't updated until all triggers associated with the table creation have completed. Just guessing.
Anybody know the reason for this?
Cheers!
--JP

ORA-01403: no data found BPEL Error on DB Adapter

Dear All,
I am using a DBAdapter to call a Stored Procedure in a Package. One of the parameter of the stored procedure is of table type. While invoking the BPEL Process, it shows the following error:
Fault Error.com.oracle.bpel.client.BPELFault: faultName: {{http://schemas.oracle.com/bpel/extension}bindingFault} messageType: {{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage} parts: {{code=<code>1403</code> ,summary=<summary>file:/u03/soauser/product/10.1.3.1/OracleAS_1/bpel/domains/default/tmp/.bpel_InventoryProduct_1.0_579640da6283d0dbd00cca17cf50e0f7.tmp/InvProductDBService.wsdl [ InvProductDBService_ptt::InvProductDBService(InputParameters,OutputParameters) ] - WSIF JCA Execute of operation 'InvProductDBService' failed due to: Error while converting to a Java struct object. Unable to convert the XSD element P_ITEM_TBL_ITEM whose user defined type is APPS.XXHDNL_INV_MTL_SYSITEMS_PKG_2. Cause: java.sql.SQLException: ORA-01403: no data found ORA-06512: at line 1 [Caused by: ORA-01403: no data found ORA-06512: at line 1 ] ; nested exception is: ORABPEL-11802 Error while converting to a Java struct object. Unable to convert the XSD element P_ITEM_TBL_ITEM whose user defined type is APPS.XXHDNL_INV_MTL_SYSITEMS_PKG_2. Cause: java.sql.SQLException: ORA-01403: no data found ORA-06512: at line 1 [Caused by: ORA-01403: no data found ORA-06512: at line 1 ] Check to ensure that the XML data describing the user defined type matches the definition of the struct in the XSD. Contact oracle support if error is not fixable. </summary> ,detail=<detail> Internal Exception: java.sql.SQLException: ORA-01403: no data found ORA-06512: at line 1 Error Code: 1403</detail> }} </ErrorDescription>
What could be the possible solution for this to get fixed. Please update..
Many thanks in advance....

This is a PL/SQL error, it occurs when a cursor (SQL statement) is called and returned no values, typically you should have an exception handler in the PL/SQL to mange this. But sometimes you want the PL/SQL to fail.
The parameters you are using to invoke the PL/SQL procedure returned no values, therefore to fix provide information that does return values, or in the PL/SQL put an exception handler in to manage the no-data-found error, e.g.
begin
Select ...
Into ..
From ..
Where ..
Exception
when no_data_found then
end;cheers
James

Error in AR_INVOICE_UTILS.validate_tax_exemption ORA-01403: no data found

Hi All,,
--API - AR Invoice (Transaction) Creation
CREATE OR REPLACE procedure APPS.xxx_ar_invoice_api
is
l_return_status varchar2(1);
l_msg_count number;
l_msg_data varchar2(2000);
l_batch_source_rec ar_invoice_api_pub.batch_source_rec_type;
l_trx_header_tbl ar_invoice_api_pub.trx_header_tbl_type;
l_trx_lines_tbl ar_invoice_api_pub.trx_line_tbl_type;
l_trx_dist_tbl ar_invoice_api_pub.trx_dist_tbl_type;
l_trx_salescredits_tbl ar_invoice_api_pub.trx_salescredits_tbl_type;
l_cust_trx_id number;
--l_batch_id              number;
--l_batch_id              number;
BEGIN
begin
MO_GLOBAL.SET_POLICY_CONTEXT('S',85);
end;
fnd_global.apps_initialize(1153,50642,222);
l_batch_source_rec.batch_source_id := 1002;
l_trx_header_tbl(1).trx_header_id := 5555;
l_trx_header_tbl(1).trx_date := sysdate;
l_trx_header_tbl(1).trx_currency := 'INR';
l_trx_header_tbl(1).cust_trx_type_id := 1;
l_trx_header_tbl(1).bill_to_customer_id := 24059;
l_trx_header_tbl(1).term_id := 1000;
l_trx_header_tbl(1).finance_charges := 'Y';
-- l_trx_header_tbl(1).status_trx := 'OP';
-- l_trx_header_tbl(1).printing_option := 'NOT';
--l_trx_header_tbl(1).reference_number            := '1111';
l_trx_lines_tbl(1).trx_header_id := 5555;
l_trx_lines_tbl(1).trx_line_id := 501;
l_trx_lines_tbl(1).line_number := 1;
l_trx_lines_tbl(1).inventory_item_id := 10008;
--l_trx_lines_tbl(1).description              := 'TUBRO 100 SAE 20W40 - 5 * 20 LTR Carton;
l_trx_lines_tbl(1).quantity_invoiced := 10;
l_trx_lines_tbl(1).unit_selling_price := 12; --Price
l_trx_lines_tbl(1).uom_code := 'Nos';
l_trx_lines_tbl(1).line_type := 'LINE';
-- l_trx_dist_tbl(1).trx_dist_id := 501;
--l_trx_dist_tbl(1).trx_line_id               := 501;
--l_trx_dist_tbl(1).ACCOUNT_CLASS             := 'REV';
--l_trx_dist_tbl(1).percent                   := 100;
--l_trx_dist_tbl(1).CODE_COMBINATION_ID       := 1012;
--Here we call the API to create Invoice with the stored values
AR_INVOICE_API_PUB.create_invoice
(p_api_version => 1.0
--,p_commit => 'T'
,p_batch_source_rec => l_batch_source_rec
,p_trx_header_tbl => l_trx_header_tbl
,p_trx_lines_tbl => l_trx_lines_tbl
,p_trx_dist_tbl => l_trx_dist_tbl
,p_trx_salescredits_tbl => l_trx_salescredits_tbl
,x_return_status => l_return_status
,x_msg_count => l_msg_count
,x_msg_data => l_msg_data
dbms_output.put_line('Created:'||l_msg_data||l_return_status);
IF l_return_status = fnd_api.g_ret_sts_error OR
l_return_status = fnd_api.g_ret_sts_unexp_error THEN
dbms_output.put_line(l_return_status||':'||sqlerrm);
Else
dbms_output.put_line(l_return_status||':'||sqlerrm);
If (ar_invoice_api_pub.g_api_outputs.batch_id IS NOT NULL) Then
Dbms_output.put_line('Invoice(s) suceessfully created!') ;
Dbms_output.put_line('Batch ID: ' || ar_invoice_api_pub.g_api_outputs.batch_id);
Dbms_output.put_line('customer_trx_id: ' || l_cust_trx_id);
Else
Dbms_output.put_line(sqlerrm);
End If;
end if;
commit;
End;
exec xxx_ar_invoice_api;
when im running this im getting error " Error in AR_INVOICE_UTILS.validate_tax_exemption ORA-01403: no data found" pls send me solution

Pls mention you app/db and OS version.
Please see if below MOS notes helps:-
LNS: Billing Fails With Error In AR_INVOICE_UTILS.validate_tax_exemption ORA - 01403 no data. [ID 797974.1]
Oracle Receivables Invoice API: Known Issues and Patches [ID 1306471.1]
Thanks,
JD

R12 AR-Receipt Refund Error:ORA-01403 no data found

Hi,all
That apply the receipt to refund and enter the refund attribute all are done well ,while I save it it dispalys a warning message:ORA-01403 no data found.
Below is the statement message I get from the fndlog_messages_
ar.plsql.ar_refund_pvt.create_refund 1 Errors found interfacing data to AP ...
ar.plsql.ar_refund_pvt.create_refund ACCT DATE NOT IN OPEN PD
I have checked the AP period that the current period has been opened.,so I' m confused about what the problem is?Does anyone happen to this problem before?
P.S. Can anyone explain what is the effect of IBY_DISBURSEMENT_SETUP_PUB.create_external_payee during the ar refund process ?
Regards,
Chelsea

Chelesa,
Certainly the error suggests that this error is related to period either in AR or AP. Take a close look on dates used.
IBY setup is called to create a party so that AP invoice can be created on that party. If you are refunding the a customer, and you do not want to create a vendor record to create one time refund (create an AP Invoice with the type as Payment Request). Hence this is called to create a party record to create AP invoice. Essentially we do not need a vendor to create an AP invoice using this method.
Thanks
Nagamohan

Error frm-40735 ora-01403

I read that this is a general purpose error for Forms, but I couldn't find an answer for my situation. I have a datablock based on a view, and a command button that has a trigger for selecting values into the block where one of the blocks fields matches those records. Here is the pl/sql code for the button's when-button-pressed trigger:
BEGIN
SELECT VIEW.ATTRIBUTE1, VIEW.ATTRIBUTE2
INTO :DATABLOCK.TEXTFIELD1, :DATABLOCK.TEXTFIELD2
FROM VIEW
WHERE :DATABLOCK.TEXTFIELD = VIEW.ATTRIBUTE3;
END;
When I try to run this in Forms, I get the Error frm-40735 ora-01403. I can run similar code from SQL Plus. I would really appreciate some help.
regards

Let me give a better example: If I have two tables:
create table dept (
dept_no NUMBER,
dept_name VARCHAR2(10),
CONSTRAINT dept_pk PRIMARY KEY (dept_no)
create table Location (
loc_no NUMBER,
loc_name VARCHAR2(10),
dept_no NUMBER,
CONSTRAINT loc_pk PRIMARY KEY (loc_no),
CONSTRAINT loc_fk FOREIGN KEY (dept_no)
REFERENCES dept(dept_no)
and I create a master-detail form between the two. If I try to search by the loc_name, with the two tables joined by the master-detail, and have a trigger on a command button with the code:
BEGIN
SELECT d.dept_no, d.dept_name
INTO :DEPARTMENT.DEPT_NO, :DEPARTMENT.DEPT_NAME
FROM Location l, Dept d
WHERE :LOCATION.LOC_NAME = l.loc_name;
END;
why do I encounter the error?

AP INVOICE작성중 PO MATCH시 ORA-01403 ERROR.

Similar Messages

Maybe you are looking for