INCIAP Create Intercompany AP Invoices-Completes in Error

Hi to all,
We ran the following intercompany request:  "Create Intercompany AP Invoices".  In reviewing the logfile the tail end of the file has the following info:
Get if OM is installed
Getting the Sales Order Information
Getting the Inventory Organization from Item Validation Organization.
l_IC_INVENTORY_ORGANIZATION_ID is 1
Call inv_workflow.call_generate_cogs
l_gl_ccid is 132972
global->invInfo.ap.ccid is 132972
    In inliap.lpc, inapcil()
Creating invoice line    Last row processing.
    In inlico.lpc, inilcbk()
End of Processing Inovice Line ID: 191190206.000000
Invoice Line ID: 191190206.000000 Status: SUCCESS
Loading global info structure
Processing invoice line, ID = 68435560
In inciap.opc, processInvoiceLine()
Get if OM is installed
Getting the Sales Order Information
Getting the Inventory Organization from Item Validation Organization.
l_IC_INVENTORY_ORGANIZATION_ID is 1
Call inv_workflow.call_generate_cogs
l_gl_ccid is 132994
API inv_workflow.call_generate_cogs returned failure./PROD/shared/apps/apps_st/appl/inv/12.0.0/bin/INCIAP
Program was terminated by signal 11
We've located the sales order and reviewed the transaction type COGS.  The COGs is valid. Since the last lines state CCID: 132994 is this the root cause? We have checked the CCID and it is enabled.  How do we find which line is giving the issue?  And is the COGs the root cause or something else?
Thanks

Hi,
This concurrent programs log is very limited to conclude the issue, please try to rerun the same program and get the FND log, steps pasted below:
1) Go to the System Profile options and set the following parameters:   
    FND: Debug Log Enabled = YES
    FND: Debug Log Filename = NULL
    FND: Debug Log Level STATEMENT (most detailed log)
    FND: Debug Log Module %
2) run your concurrent program
3).
SELECT LOG.LOG_SEQUENCE, LOG.message_text message
FROM FND_LOG_MESSAGES LOG,
FND_LOG_TRANSACTION_CONTEXT CON
WHERE CON.TRANSACTION_ID = <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<Your Concurrent request ID>>>>>>>>>>>>>>>>>>>>>>>>>>>>
AND CON.TRANSACTION_TYPE = 'REQUEST'
AND CON.TRANSACTION_CONTEXT_ID = LOG.TRANSACTION_CONTEXT_ID
ORDER BY LOG.LOG_SEQUENCE ;
Hope it helps!
Regards,
Yuvaraj

Similar Messages

  • Create Intercompany AR Invoices Request Ends Completed Warning

    Dear All
    When trying to Run the Concurrent 'Create Intercompany AR Invoices' from the shipping OU, the concurrent ends Completed Warning and after Reviewing the Log File it shows,
    Warning: Cannot retrieve price list from bill-to site information Internal Location or from Customer with Customer Number 3705 and Customer Name Internal Areen.
    Action: Please use Define Customer Form to enter the price list information fo
         Returned warning from extra function
    Return Warning from inilco.
         The global status is INVALID.
    Warning: Cannot create invoice line
    End Processing Transaction ID: 3538149
    Transaction ID: 3538149      Status = FAILURE
    Please help to resolve me this issue.
    Thanks
    Dinesh

    Hello,
    In customer definition you should have inter company price list or you do not have price for item in this price list.
    Look also
    11i INCIAR Warning: Cannot Retrieve Price List From Bill-To Site [ID 369274.1]
    11i INCIAR Create Intercompany AR Invoice APP-INV-05706 Cannot Retrieve Transfer Price For The Item [ID 356315.1]
    Cannot Retrieve Price List From Bill-To Site Information &Loc Or From Customer With Customer Number [ID 1097385.1]

  • Spliting accounts while running the "Create Intercompany AP Invoices"

    Hi Guys,
    Need Urgent help if this customization is possible.
    While creating AP invoice(Intercompany), we want to spllit the account of a line into two,
    one for the original account and another for IP(Intellectual property), the ratio of splliting will be taken care.
    But I want two know if spliting into two accounts is possible even before inserting into inerface table.
    If possible please let me know how.
    Please guys need your help.
    Thanks Girish.

    Hi Girish
    If you want split the line during creation of IC AP Invoice, you need to customize the IC AP COGS workflow to accomodate the business requirement
    Thanks
    Krishna

  • Error in creating Depot excise invoice.(J1IJ) 4F:550

    Hi  Gurus.
    I have created. 
    Depot Sales Order->Depot Delivery.
    Now i am creating Depot excise invoice in J1IJ.i am getting error when i enter delivery no, excide group & Series group
    error:-
       4F:550 TDL TD12 E3 E3
    TDL-company code
    TD12- Plant(Depot)
    E3-Excise group
    E3-series group.
    NOTE:-  we dont want to configure default excise group & series group config.
    Reg.
    Amol
    Edited by: Amol Tamhane on Mar 16, 2010 3:17 PM

    Hi all,
    I got the Solution.
    Tell your ABAPER  to find out Object in "SAPMJ1IJ" PROGRAM
    source code of MJ1IJF01.
    in my case the object was "J_1IDEP_S1"
    1) check whether that object is assigned to user or not(from Basis guy)
    2)Check whether values of following are assigned in  that object or not(Basis guy)
    Activity
    Company Code
    Plant
    Excise group
    Excise document series group
    take the help of Basis guy to Resolve it.
    Reg,
    Amol

  • Error while creating inter-company invoice  for stock transport

    Hi ,
    I am facing following errors while creating inter-company invoice for STO order.
    We have scenario where standard PO is created in  company code A  & then replenishment delivery is created in company code B.While raising inter-company invoice to company code A, we are facing problem.
    In replenishment delivery we have 10 line items. But  when we try to do inter company invoice through VF01/VF04 we get following log
    XXXXXXXXXX(delivery Number) 000000 Customer XXXXX: Customer master table KNVV is missing (VF-022)
    XXXXXXXXXX (delivery Number)000010 The bill-to party could not be determined (VF-047)
    XXXXXXXXXX (delivery Number)000010 The payer could not be determined (VF-048)
    With this first line item from delivery is not flows to invoice & if we saves this invoice then it is get saved with account determination error as some of the data does not comes into invoice header like account assignment group for customer, Payment term, destination country,region, tax classification for customer etc. That means invoice gets created without first line item from delivery with account determination error & so,no accounting document gets generated.
    I checked customer master for all SP,SH,BP,PY they are correctly maintained.This was working fine few months back, but not working now.
    If anybody had come across such kind of scenario, your valuable inputs will be highly appreciated.
    Thanks & kind regards,
    Ganesh Palatshaha

    Hello
    Kindly check the sales area of customer involved, whether the customer maintain with sales area for STO.
    If that is note the case the refer following link:
    - Error VF 047 & 048 while creating Inter company billing
    Regards
    JP

  • Error Message while creating A/P Invoice

    hi experts,
    I try to create AP invoice but system shows following error cannot create standalone AP/AR invoice with excisable item. please explain me the reason to understand.

    Hi Ratna Kumari,
    When ever you create Delivery for Excise able Item System Pop Up That You need to Create Excise able Invoice for this Delivery.
    If you will not Create Excise able Invoice then You will not be able to create Invoice.
    If Item is Excise able then you have to Create Excise able Invoice other wise you will not be able to create Invoice.
    If you have included Tax with 100% Non Deductible then also you have to create Excise Invoice for every Delivery of Excise able Item for Creating Invoice.
    This is Standard System Behavior. You to Create Excise able Invoice for Creation Invoice.
    Hope this help
    Regards::::
    Atul Chakraborty

  • When creating a slideshow I get an error message when it's almost done:  the operation couldn't be completed- osstatus error 9459

    When creating a slideshow I get an error message when it's almost done:  the operation couldn't be completed- osstatus error 9459.  Help!

    but I tried that earlier and the same thing happened.
    Why not give us a list of all the things you've tried so we don;t waste your time - and ours - making suggestions that you know won't work?
    Regards
    TD

  • India - VAT Invoice Generation / Accounting Completed with Error

    Hi,
    Can any body explain why below program completed with error
    "India - VAT Invoice Generation / Accounting"
    I checked completion text,It's showing Normal completion,
    Regards,
    Reddy

    Hello..
    is there any one to help me???????

  • Error creating an AP Invoice

    Hi,
    I am trying to create an AP invoice(Doc Type = Service) using DI API.I am getting the following eror message:
    [OPCH.GrosProfit][line: 1] , 'No matching records found (ODBC -2028)'
    My code is as follows:
    Set oCmp = New SAPbobsCOM.Company
    oCmp.UseTrusted = True
    oCmp.Server = "(local)"
    oCmp.CompanyDB = "ABC-Holding"
    oCmp.UserName = "manager"
    oCmp.Password = "manager"
    oCmp.Language = SAPbobsCOM.BoSuppLangs.ln_English
    l = oCmp.Connect()
    Set oApInvoice = oCmp.GetBusinessObject(oPurchaseInvoices)
    oApInvoice.DocType = dDocument_Service
    oApInvoice.CardCode = "VA001S"
    oApInvoice.Lines.ItemDescription = "Banana"
    oApInvoice.Lines.Price = 2.36
    oApInvoice.Lines.AccountCode = "999999-100"
    RetVal = oApInvoice.Add
    If RetVal <> 0 Then
       oCmp.GetLastError ErrCode, ErrMsg
       MsgBox ErrCode & " " & ErrMsg
    End If
    Please help.
    Thanks.

    Hello,
    I think you must use this sentence to add the line before adding the invoice:
    oApInvoice.Lines.Add
    But DI has a problem when you use that method. You have to set another line after calling the add method. Then setting another line this way:
    oApInvoice.Lines.ItemDescription = "Banana 2"
    oApInvoice.Lines.Price = 2.40
    oApInvoice.Lines.AccountCode = "999999-100"
    Don't forget to set the taxCode in Both lines and after that you can add the Invoice:
    RetVal = oApInvoice.Add
    I hope i could help you..

  • Acctg document not created for cancellation invoice

    Hi all,
    We have a vehicle sales order created with payment card. The SO contains one item for vehicle and one item for parts. The items were delivered and invoiced separately. Hence, SO has one vehicle sales invoice (VSI) and one parts sales invoice (PSI).
    The standard procedure was to post VSI first before the PSI. Accounting documents have been created when both invoices were posted. However, there was a need to cancel the PSI. When this was done, cancellation invoice was created but there was no accounting document posted for the cancellation.
    I tried simulating the scenario in our test server and cancelled VSI 90000081 first before cancelling PSI 90000082 to test if this can be an alternative solution. Cancellation for VSI was posted successfully but error persists for PSI cancellation.
    Order 67 06/19/06 Completed
    . Delivery 80000081 06/19/06 Being processed
    .. Picking request 20060619 06/19/06 Completed
    .. GD goods issue:delvy 4900000293 06/19/06 complete
    .. Invoice 90000081 06/19/06 Completed
    ... Accounting document 2000077 06/19/06 partly cleared
    .. Invoice cancellation 90000084 06/19/06 Completed
    ... Accounting document 2000079 06/19/06 partly cleared
    . Delivery 80000082 06/19/06 Completed
    .. Picking request 20060619 06/19/06 Completed
    .. GD goods issue:delvy 4900000294 06/19/06 complete
    .. Invoice 90000082 06/19/06 Completed
    ... Accounting document 2000078 06/19/06 Not cleared
    .. Invoice cancellation 90000083 06/19/06
    .. Invoice 90000085 06/20/06 Blocked
    Accounting status of 90000083 (where error occurs) in VF03->Header->Details is set to K or <b>Accounting document not created (authorization lacking)</b>.
    Any inputs? Thanks in advance.

    Hello Sheila,
    sorry - my first answer was in mistake - Status K means:
    "The transaction is processed using payment cards. The order, however, does not contain valid authorization.
    This problem occurs in billing documents for follow-up deliveries."
    Could you check this ? Last way would be to set a breakpoint into the FM 'RV_ACCOUNTING_DOCUMENT_CREATE'
    and trigger this via VF02 -> Release to accounting.
    Regards Wolfgang

  • XML Report completes with error due to REP-271504897:  Unable to retrieve a string from the Report Builder message file.

    We are in the middle of testing our R12 Upgrade.  I am getting this error from the invoice XML-based report that we are using in R12. (based on log).  Only for a specific invoice number that this error is appearing.  The trace is not showing me anything.  I don't know how to proceed on how to debug where the error is coming from and how to fix this.  I found a patch 8339196 that shows exactly the same error number but however, I have to reproduce the error in another test instance before we apply the patch.  I created exactly the same order and interface to AR and it doesnt generate an error.  I even copied the order and interface to AR and it doesn't complete with error.  It is only for this particular invoice that is having an issue and I need to get the root cause as to why.  Please help.  I appreciate what you all can contribute to identify and fix our issue.  We have not faced this issue in R11i that we are maintaining right now for the same program which has been running for sometime.  However, after the upgrade for this particular data that the user has created, it is throwing this error REP-271504897.
    MSG-00100: DEBUG:  Get_Country_Description Return value:
    MSG-00100: DEBUG:  Get_Country_Description Return value:
    REP-0002: Unable to retrieve a string from the Report Builder message file.
    REP-271504897:
    REP-0069: Internal error
    REP-57054: In-process job terminated:Terminated with error:
    REP-271504897: MSG-00100: DEBUG:  BeforeReport_Trigger +
    MSG-00100: DEBUG:  AfterParam_Procs.Populate_Printing_Option
    MSG-00100: DEBUG:  AfterParam_Procs.Populate_Tax_Printing_Option
    MSG-00100: DEBUG:  BeforeReport_Trigger.Get_Message_Details
    MSG-00100: DEBUG:  BeforeReport_Trigger.Get_Org_Profile.
    MSG-00100: DEBUG:  Organization Id:  117
    MSG-00100: DEBUG:  BeforeReport_Trigger.Build_Where_Clause
    MSG-00100: DEBUG:  P_Choi
    Report Builder: Release 10.1.2.3.0 - Production on Tue Jul 23 09:56:46 2013
    Copyright (c) 1982, 2005, Oracle.  All rights reserved.

    Hi,
    Check on this note also : Purchasing Reports Fail When Changing Output To XML REP-0002 REP-271504897 REP-57054 (Doc ID 1452608.1)
    If you cant reproduce the issue on other instance, apply the patch on the test instance and verify all the funcionality related to the patch works OK. Then move the patch to production. Or you can clone the prod environment to test the patch.
    Regards,

  • Payables Accounting Process Completing with Error

    Hi All,
    After running Payables Accounting Process I am getting error
    Spawned Process 151662
    MSG-00001: After SRWINIT
    MSG-00002: Check that AX is not installed before calling the accounting engine
    MSG-00003: AX is not installed, Calling the accounting engine
    MSG-00004: After the call to AP_Accounting_Engine_Pkg.Do_Accounting
    MSG-00005: Error occured in the accounting process
    MSG-00006: Error Message:
    REP-1419: 'beforereport': PL/SQL program aborted.
    Inside Execute for Invoice_Canc_Event_Core
    Inside Derive_Accounting_Entry for Invoice_Event_Core
    Starting Accrual Basis Accounting for Invoice Event...
    INSERTing Header into AP_AE_Headers ...
    ORA-00001: unique constraint (AP.AP_AE_HEADERS_U2) violated occurred in
    AP_ACCOU
    NTING_MAIN_PKG.Insert_AE_HeaderAP_INVOICE_EVENT_CORE_PKG.Derive_Accounting_Entry
    <-AP_INVOICE_CANC_EVENT_CORE_PKG.Execute<-AP_ACCOUNTING_MAIN_PKG.Create_Accounti
    ng_Entry<-AP_ACCOUNTING_ENGINE_PKG.do_accounting<-APXAEREP
    with parameters (&PAR
    AMETERS)
    while performing the following operation:
    &DEBUG_INFO
    End of log messages from FND_FILE
    Program exited with status 1
    Please suggest what could be the possible error, this is happening in Production so sort of urgent!
    Thanks,
    Anchorage

    Duplicate thread ..
    Payables Accounting Process Completing with Error
    Payables Accounting Process Completing with Error

  • XML Publisher generates PDF but concurrent program still completes in error

    Hello,
    I have a concurent program that is used everyday. It generates PDF output with an average of 500 pages. It completes normal majority of the times, but completes in error sporadicallly. Interestingly, when it completes in error, it still generates the PDF output successfully.
    Question is why does it complete in error when all is good?
    Please note that we just went live on R12 from 11i beginning of this year. This issue never occurred in 11i. Please advise what can be done to fix this issue.
    Below is a log from one such submission. The log was rather long, so I'm only posting chunks from the beginning and end of the log, stripping the middle portion:
    Receivables: Version : 12.0.0
    Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
    XXBREG_RAXINV_NEW_XMLP module: Breg Invoice Print New Invoices - XMLP
    Current system time is 22-JAN-2013 06:46:58
    +-----------------------------
    | Starting concurrent program execution...
    +-----------------------------
    Arguments
    p_order_by='TRX_NUMBER'
    p_cust_trx_class='INV'
    p_cust_trx_type_id='1'
    p_open_invoice='Y'
    p_check_for_taxyn='N'
    p_choice='NEW'
    p_header_pages='1'
    p_debug_flag='N'
    p_message_level='10'
    Forcing NLS_NUMERIC_CHARACTERS to: '.,' for XDO processing
    APPLLCSP Environment Variable set to :
    Current NLS_LANG and NLS_NUMERIC_CHARACTERS Environment Variables are :
    American_America.AL32UTF8
    Enter Password:
    MSG-00100: DEBUG: AfterPForm_Trigger +
    MSG-00100: DEBUG: Multi Org established.
    MSG-00100: DEBUG: AfterParam_Procs.Get_Country_Details
    MSG-00100: DEBUG: AfterParam_Procs.Switch_On_Debug
    MSG-00100: DEBUG: AfterParam_Procs.Get_Trx_Number_Low
    MSG-00100: DEBUG: AfterParam_Procs.Get_Trx_Number_High
    MSG-00100: DEBUG: AfterParam_Procs.Get_Tax_Option
    MSG-00100: DEBUG: AfterPForm_Trigger -
    MSG-00100: DEBUG: BeforeReport_Trigger +
    MSG-00100: DEBUG: BeforeReport_Procs.Populate_Printing_Option
    MSG-00100: DEBUG: BeforeReport_Procs.Populate_Tax_Printing_Option
    MSG-00100: DEBUG: BeforeReport_Trigger.Get_Message_Details
    MSG-00100: DEBUG: BeforeReport_Trigger.Get_Org_Profile.
    MSG-00100: DEBUG: Organization Id: 106
    MSG-00100: DEBUG: BeforeReport_Trigger.Build_Where_Clause
    MSG-00100: DEBUG: P_Choice: NEW
    MSG-00500: DEBUG: About to build WHERE clause.
    MSG-00500: DEBUG: WHERE clause built.
    MSG-00555: :p_choice:NEW
    MSG-00100: DEBUG: Choice is other than ADJ, setting ORDER BY.
    MSG-00555: :p_sel_trx_number:a.trx_number
    MSG-00555: :p_sel_trx_date:a.trx_date
    MSG-00555: :p_sel_trx_id:a.customer_trx_id
    MSG-00555: :p_sel_trx_type:types.type
    MSG-00555: :p_br_where_clause:
    MSG-00500: DEBUG: Table 1: AR_ADJUSTMENTS COM_ADJ,
    AR_PAYMENT_SCHEDULES P,
    RA_CUST_TRX_LINE_GL_DIST REC,
    RA_CUSTOMER_TRX A,
    HZ_CUST_ACCOUNTS B,
    RA_TERMS T,
    RA_TERMS_LINES TL,
    RA_CUST_TRX_TYPES TYPES,
    AR_LOOKUPS L_TYPES,
    HZ_PARTIES      PARTY,
    HZ_CUST_ACCT_SITES A_BILL,
    HZ_PARTY_SITES PARTY_SITE,
    HZ_LOCATIONS LOC,
    HZ_CUST_SITE_USES U_BILL
    MSG-00500: DEBUG: Table 2: RA_TERMS_LINES TL,
    RA_CUST_TRX_TYPES TYPES,
    AR_LOOKUPS L_TYPES,
         HZ_CUST_ACCOUNTS B,
    HZ_PARTIES      PARTY,
    HZ_CUST_SITE_USES U_BILL,
    HZ_CUST_ACCT_SITES A_BILL,
    HZ_PARTY_SITES PARTY_SITE,
    HZ_LOCATIONS LOC,
    AR_ADJUSTMENTS COM_ADJ,
    RA_CUSTOMER_TRX A,
    AR_PAYMENT_SCHEDULES P,
    RA_TERMS T
    MSG-00500: DEBUG: Where 1: A.BILL_TO_CUSTOMER_ID = B.CUST_ACCOUNT_ID
    AND REC.CUSTOMER_TRX_ID = A.CUSTOMER_TRX_ID
    AND REC.LATEST_REC_FLAG = 'Y'
    AND REC.ACCOUNT_CLASS = 'REC'
    AND P.PAYMENT_SCHEDULE_ID + DECODE(P.CLASS,
    'INV', 0,
    = COM_ADJ.PAYMENT_SCHEDULE_ID(+)
    AND COM_ADJ.SUBSEQUENT_TRX_ID IS NULL
    AND 'C' = COM_ADJ.ADJUSTMENT_TYPE(+)
    AND A.COMPLETE_FLAG = 'Y'
    AND A.CUST_TRX_TYPE_ID = TYPES.CUST_TRX_TYPE_ID
    AND L_TYPES.LOOKUP_TYPE = 'INV/CM/ADJ'
    AND A.PRINTING_OPTION IN ('PRI', 'REP')
    AND L_TYPES.LOOKUP_CODE =
    DECODE( TYPES.TYPE,'DEP','INV', TYPES.TYPE)
    AND NVL(P.TERMS_SEQUENCE_NUMBER,nvl(TL.SEQUENCE_NUM,0))=nvl(TL.SEQUENCE_NUM,nvl(p.terms_sequence_number,0))
    AND DECODE(P.PAYMENT_SCHEDULE_ID,'',0, NVL(T.PRINTING_LEAD_DAYS,0))=0
    AND A.BILL_TO_SITE_USE_ID = U_BILL.SITE_USE_ID
    AND U_BILL.CUST_ACCT_SITE_ID = A_BILL.CUST_ACCT_SITE_ID
    AND A_BILL.party_site_id = party_site.party_site_id
    AND B.PARTY_ID = PARTY.PARTY_ID
    AND loc.location_id = party_site.location_id
    AND NVL(LOC.LANGUAGE,'US') = 'US'
    AND NVL(P.AMOUNT_DUE_REMAINING,0) <> 0
    AND A.CUST_TRX_TYPE_ID = 1
    AND TYPES.TYPE = 'INV'
    AND A.TERM_ID = TL.TERM_ID(+)
    AND A.TERM_ID = T.TERM_ID(+)
    AND A.CUSTOMER_TRX_ID = P.CUSTOMER_TRX_ID(+)
    AND A.PRINTING_PENDING = 'Y'
    AND NVL(TL.SEQUENCE_NUM, 1) > NVL(A.LAST_PRINTED_SEQUENCE_NUM,0)
    MSG-00500: DEBUG: Where 2: A.BILL_TO_CUSTOMER_ID = B.CUST_ACCOUNT_ID
    AND P.PAYMENT_SCHEDULE_ID + DECODE(P.CLASS,
    'INV', 0,
    = COM_ADJ.PAYMENT_SCHEDULE_ID(+)
    AND COM_ADJ.SUBSEQUENT_TRX_ID IS NULL
    AND 'C' = COM_ADJ.ADJUSTMENT_TYPE(+)
    AND A.COMPLETE_FLAG = 'Y'
    AND A.CUSTOMER_TRX_ID = P.CUSTOMER_TRX_ID
    AND A.CUST_TRX_TYPE_ID = TYPES.CUST_TRX_TYPE_ID
    AND L_TYPES.LOOKUP_TYPE = 'INV/CM/ADJ'
    AND A.PRINTING_OPTION IN ('PRI', 'REP')
    AND L_TYPES.LOOKUP_CODE =
    DECODE( TYPES.TYPE,'DEP','INV', TYPES.TYPE)
    AND NVL(T.PRINTING_LEAD_DAYS,0) > 0
    AND A.BILL_TO_SITE_USE_ID = U_BILL.SITE_USE_ID
    AND U_BILL.CUST_ACCT_SITE_ID = A_BILL.CUST_ACCT_SITE_ID
    AND A_BILL.PARTY_SITE_ID = PARTY_SITE.PARTY_SITE_ID
    AND B.PARTY_ID = PARTY.PARTY_ID
    AND LOC.LOCATION_ID = PARTY_SITE.LOCATION_ID
    AND NVL(LOC.LANGUAGE,'US') = 'US'
    AND NVL(P.TERMS_SEQUENCE_NUMBER,TL.SEQUENCE_NUM)=TL.SEQUENCE_NUM
    AND NVL(P.AMOUNT_DUE_REMAINING,0) <> 0
    AND A.CUST_TRX_TYPE_ID = 1
    AND TYPES.TYPE = 'INV'
    AND T.TERM_ID = P.TERM_ID
    AND TL.TERM_ID(+) = T.TERM_ID
    AND A.PRINTING_PENDING = 'Y'
    AND P.TERMS_SEQUENCE_NUMBER > NVL(A.LAST_PRINTED_SEQUENCE_NUM,0)
    MSG-00100: DEBUG: BeforeReport_Trigger -
    MSG-05000: DEBUG: Trx No... 1010441
    MSG-00100: DEBUG: Get_Country_Description.
    MSG-00010: 06:47 1 Transaction: 1010441
    MSG-00001: Line type : Line
    MSG-00100: DEBUG: Get_Country_Description.
    MSG-00100: DEBUG: Get_Country_Description.
    MSG-05000: DEBUG: Remit To Address....
    MSG-05000: DEBUG: Address Style:
    MSG-05000: DEBUG: Address 1: PO Box 849991
    MSG-05000: DEBUG: Address 2:
    MSG-05000: DEBUG: Address 3:
    MSG-05000: DEBUG: Address 4:
    MSG-05000: DEBUG: City: Dallas
    MSG-05000: DEBUG: County:
    MSG-05000: DEBUG: State: TX
    MSG-05000: DEBUG: Province:
    MSG-05000: DEBUG: Postal Code: 75284
    MSG-05000: DEBUG: Territory:
    MSG-05000: DEBUG: Country_Code: US
    MSG-05000: DEBUG: Customer Name:
    MSG-05000: DEBUG: Bill To:
    MSG-05000: DEBUG: First Name:
    MSG-05000: DEBUG: Last Name:
    MSG-05000: DEBUG: Mail Stop:
    MSG-05000: DEBUG: Country Code: US
    MSG-05000: DEBUG: Country Desc:
    MSG-05000: DEBUG: Print Home Flag: N
    MSG-05000: DEBUG: Width: 40
    MSG-05000: DEBUG: Height Min: 6
    MSG-05000: DEBUG: Height Max: 6
    MSG-05000: DEBUG: Remit To Formatted... PO Box 849991
    Dallas TX 75284
    MSG-05000: DEBUG: Trx No... 1010442
    MSG-00100: DEBUG: Get_Country_Description.
    MSG-00010: 06:47 2 Transaction: 1010442
    MSG-05000: DEBUG: Bill To Address....
    MSG-05000: DEBUG: Address Style:
    MSG-05000: DEBUG: Address 1: 6560 W ROGERS CIR
    MSG-05000: DEBUG: Address 2: STE 19
    MSG-05000: DEBUG: Address 3:
    MSG-05000: DEBUG: Address 4:
    MSG-05000: DEBUG: City: BOCA RATON
    MSG-05000: DEBUG: County:
    MSG-05000: DEBUG: State: FL
    MSG-05000: DEBUG: Province:
    MSG-05000: DEBUG: Postal Code: 33487-2746
    MSG-05000: DEBUG: Territory:
    MSG-05000: DEBUG: Country_Code: US
    MSG-05000: DEBUG: Customer Name: THE BRACE SHOP
    MSG-05000: DEBUG: Bill To:
    MSG-05000: DEBUG: First Name: LORI
    MSG-05000: DEBUG: Last Name: ESCALANTE
    MSG-05000: DEBUG: Mail Stop:
    MSG-05000: DEBUG: Country Code: US
    MSG-05000: DEBUG: Country Desc:
    MSG-05000: DEBUG: Print Home Flag: N
    MSG-05000: DEBUG: Width: 40
    MSG-05000: DEBUG: Height Min: 8
    MSG-05000: DEBUG: Height Max: 8
    MSG-05000: DEBUG: Bill To Formatted... LORI ESCALANTE
    THE BRACE SHOP
    6560 W ROGERS CIR
    STE 19
    BOCA RATON FL 33487-2746
    MSG-05000: DEBUG: Ship To Address....
    MSG-05000: DEBUG: Address Style:
    MSG-05000: DEBUG: Address 1: 7014 E Appleton Circle
    MSG-05000: DEBUG: Address 2:
    MSG-05000: DEBUG: Address 3:
    MSG-05000: DEBUG: Address 4:
    MSG-05000: DEBUG: City: CENTENNIAL
    MSG-05000: DEBUG: County:
    MSG-05000: DEBUG: State: CO
    MSG-05000: DEBUG: Province:
    MSG-05000: DEBUG: Postal Code: 80112-1155
    MSG-05000: DEBUG: Territory:
    MSG-05000: DEBUG: Country_Code: US
    MSG-05000: DEBUG: Customer Name: Kenneth Grimm
    MSG-05000: DEBUG: Bill To:
    MSG-05000: DEBUG: First Name:
    MSG-05000: DEBUG: Last Name:
    MSG-05000: DEBUG: Mail Stop:
    MSG-05000: DEBUG: Country Code: US
    MSG-05000: DEBUG: Country Desc:
    MSG-05000: DEBUG: Print Home Flag: N
    MSG-05000: DEBUG: Width: 40
    MSG-05000: DEBUG: Height Min: 8
    MSG-05000: DEBUG: Height Max: 8
    MSG-05000: DEBUG: Ship To Formatted... Kenneth Grimm
    7014 E Appleton Circle
    CENTENNIAL CO 80112-1155
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00100: DEBUG: Get_Country_Description.
    MSG-00100: Oracle Error in call to arp_adds.location_description -6503
    MSG-05000: DEBUG: Remit To Address....
    MSG-05000: DEBUG: Address Style:
    MSG-05000: DEBUG: Address 1: PO Box 849991
    MSG-05000: DEBUG: Address 2:
    MSG-05000: DEBUG: Address 3:
    MSG-05000: DEBUG: Address 4:
    MSG-05000: DEBUG: City: Dallas
    MSG-05000: DEBUG: County:
    MSG-05000: DEBUG: State: TX
    MSG-05000: DEBUG: Province:
    MSG-05000: DEBUG: Postal Code: 75284
    MSG-05000: DEBUG: Territory:
    MSG-05000: DEBUG: Country_Code: US
    MSG-05000: DEBUG: Customer Name:
    MSG-05000: DEBUG: Bill To:
    MSG-05000: DEBUG: First Name:
    MSG-05000: DEBUG: Last Name:
    MSG-05000: DEBUG: Mail Stop:
    MSG-05000: DEBUG: Country Code: US
    MSG-05000: DEBUG: Country Desc:
    MSG-05000: DEBUG: Print Home Flag: N
    MSG-05000: DEBUG: Width: 40
    MSG-05000: DEBUG: Height Min: 6
    MSG-05000: DEBUG: Height Max: 6
    MSG-05000: DEBUG: Remit To Formatted... PO Box 849991
    Dallas TX 75284
    MSG-05000: DEBUG: Trx No... 1010930
    MSG-00100: DEBUG: Get_Country_Description.
    MSG-00010: 06:47 506 Transaction: 1010930
    MSG-05000: DEBUG: Bill To Address....
    MSG-05000: DEBUG: Address Style:
    MSG-05000: DEBUG: Address 1: 4412 MANILLA ROAD SE
    MSG-05000: DEBUG: Address 2: UNIT 7
    MSG-05000: DEBUG: Address 3:
    MSG-05000: DEBUG: Address 4:
    MSG-05000: DEBUG: City: CALGARY
    MSG-05000: DEBUG: County:
    MSG-05000: DEBUG: State:
    MSG-05000: DEBUG: Province: ALBERTA
    MSG-05000: DEBUG: Postal Code: T2G 4B7
    MSG-05000: DEBUG: Territory:
    MSG-05000: DEBUG: Country_Code: CA
    MSG-05000: DEBUG: Customer Name: MEDLINES INC DBA PRO CARE MEDICAL LTD
    MSG-05000: DEBUG: Bill To:
    MSG-05000: DEBUG: First Name:
    MSG-05000: DEBUG: Last Name:
    MSG-05000: DEBUG: Mail Stop:
    MSG-05000: DEBUG: Country Code: US
    MSG-05000: DEBUG: Country Desc:
    MSG-05000: DEBUG: Print Home Flag: N
    MSG-05000: DEBUG: Width: 40
    MSG-05000: DEBUG: Height Min: 8
    MSG-05000: DEBUG: Height Max: 8
    MSG-05000: DEBUG: Bill To Formatted... Attn: Accounts Payable
    MEDLINES INC DBA PRO CARE MEDICAL LTD
    4412 MANILLA ROAD SE
    UNIT 7
    CALGARY ALBERTA T2G 4B7
    Canada
    MSG-05000: DEBUG: Ship To Address....
    MSG-05000: DEBUG: Address Style:
    MSG-05000: DEBUG: Address 1: 4412 MANILLA ROAD SE Unit 7
    MSG-05000: DEBUG: Address 2: PH:403 287 0993
    MSG-05000: DEBUG: Address 3:
    MSG-05000: DEBUG: Address 4:
    MSG-05000: DEBUG: City: CALGARY
    MSG-05000: DEBUG: County:
    MSG-05000: DEBUG: State: ALBERTA
    MSG-05000: DEBUG: Province: ALBERTA
    MSG-05000: DEBUG: Postal Code: T2G 4B7
    MSG-05000: DEBUG: Territory:
    MSG-05000: DEBUG: Country_Code: CA
    MSG-05000: DEBUG: Customer Name: MEDLINES INC DBA PRO CARE MEDICAL LTD
    MSG-05000: DEBUG: Bill To:
    MSG-05000: DEBUG: First Name:
    MSG-05000: DEBUG: Last Name:
    MSG-05000: DEBUG: Mail Stop:
    MSG-05000: DEBUG: Country Code: US
    MSG-05000: DEBUG: Country Desc:
    MSG-05000: DEBUG: Print Home Flag: N
    MSG-05000: DEBUG: Width: 40
    MSG-05000: DEBUG: Height Min: 8
    MSG-05000: DEBUG: Height Max: 8
    MSG-05000: DEBUG: Ship To Formatted... MEDLINES INC DBA PRO CARE MEDICAL LTD
    4412 MANILLA ROAD SE Unit 7
    PH:403 287 0993
    CALGARY ALBERTA ALBERTA T2G 4B7
    Canada
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00001: Line type : Line
    MSG-00100: DEBUG: Get_Country_Description.
    MSG-05000: DEBUG: Remit To Address....
    MSG-05000: DEBUG: Address Style:
    MSG-05000: DEBUG: Address 1: PO Box 849991
    MSG-05000: DEBUG: Address 2:
    MSG-05000: DEBUG: Address 3:
    MSG-05000: DEBUG: Address 4:
    MSG-05000: DEBUG: City: Dallas
    MSG-05000: DEBUG: County:
    MSG-05000: DEBUG: State: TX
    MSG-05000: DEBUG: Province:
    MSG-05000: DEBUG: Postal Code: 75284
    MSG-05000: DEBUG: Territory:
    MSG-05000: DEBUG: Country_Code: US
    MSG-05000: DEBUG: Customer Name:
    MSG-05000: DEBUG: Bill To:
    MSG-05000: DEBUG: First Name:
    MSG-05000: DEBUG: Last Name:
    MSG-05000: DEBUG: Mail Stop:
    MSG-05000: DEBUG: Country Code: US
    MSG-05000: DEBUG: Country Desc:
    MSG-05000: DEBUG: Print Home Flag: N
    MSG-05000: DEBUG: Width: 40
    MSG-05000: DEBUG: Height Min: 6
    MSG-05000: DEBUG: Height Max: 6
    MSG-05000: DEBUG: Remit To Formatted... PO Box 849991
    Dallas TX 75284
    MSG-05000: DEBUG: Bill To Address....
    MSG-05000: DEBUG: Address Style:
    MSG-05000: DEBUG: Address 1: 8206 LEESBURG PIKE
    MSG-05000: DEBUG: Address 2: STE 409
    MSG-05000: DEBUG: Address 3:
    MSG-05000: DEBUG: Address 4:
    MSG-05000: DEBUG: City: VIENNA
    MSG-05000: DEBUG: County:
    MSG-05000: DEBUG: State: VA
    MSG-05000: DEBUG: Province:
    MSG-05000: DEBUG: Postal Code: 22182
    MSG-05000: DEBUG: Territory:
    MSG-05000: DEBUG: Country_Code: US
    MSG-05000: DEBUG: Customer Name: NOVA ORTHOPAEDIC AND SPORTS MEDICINE
    MSG-05000: DEBUG: Bill To:
    MSG-05000: DEBUG: First Name: TAYLOR
    MSG-05000: DEBUG: Last Name: CRIGLER
    MSG-05000: DEBUG: Mail Stop:
    MSG-05000: DEBUG: Country Code: US
    MSG-05000: DEBUG: Country Desc:
    MSG-05000: DEBUG: Print Home Flag: N
    MSG-05000: DEBUG: Width: 40
    MSG-05000: DEBUG: Height Min: 8
    MSG-05000: DEBUG: Height Max: 8
    MSG-05000: DEBUG: Bill To Formatted... TAYLOR CRIGLER
    NOVA ORTHOPAEDIC AND SPORTS MEDICINE
    8206 LEESBURG PIKE
    STE 409
    VIENNA VA 22182
    MSG-05000: DEBUG: Ship To Address....
    MSG-05000: DEBUG: Address Style:
    MSG-05000: DEBUG: Address 1: 8206 LEESBURG PIKE
    MSG-05000: DEBUG: Address 2: STE 409
    MSG-05000: DEBUG: Address 3:
    MSG-05000: DEBUG: Address 4:
    MSG-05000: DEBUG: City: VIENNA
    MSG-05000: DEBUG: County:
    MSG-05000: DEBUG: State: VA
    MSG-05000: DEBUG: Province:
    MSG-05000: DEBUG: Postal Code: 22182
    MSG-05000: DEBUG: Territory:
    MSG-05000: DEBUG: Country_Code: US
    MSG-05000: DEBUG: Customer Name: NOVA ORTHOPAEDIC AND SPORTS MEDICINE
    MSG-05000: DEBUG: Bill To:
    MSG-05000: DEBUG: First Name: TAYLOR
    MSG-05000: DEBUG: Last Name: CRIGLER
    MSG-05000: DEBUG: Mail Stop:
    MSG-05000: DEBUG: Country Code: US
    MSG-05000: DEBUG: Country Desc:
    MSG-05000: DEBUG: Print Home Flag: N
    MSG-05000: DEBUG: Width: 40
    MSG-05000: DEBUG: Height Min: 8
    MSG-05000: DEBUG: Height Max: 8
    MSG-05000: DEBUG: Ship To Formatted... TAYLOR CRIGLER
    NOVA ORTHOPAEDIC AND SPORTS MEDICINE
    8206 LEESBURG PIKE
    STE 409
    VIENNA VA 22182
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    MSG-00001: In Line frame trigger
    MSG-00001: Line Type: INV Source:OM Invoices
    REP-0069: Internal error
    REP-57054: In-process job terminated:Finished successfully
    MSG-00100: DEBUG: BeforeReport_Trigger +
    MSG-00100: DEBUG: BeforeReport_Procs.Populate_Printing_Option
    MSG-00100: DEBUG: BeforeReport_Procs.Populate_Tax_Printing_Option
    MSG-00100: DEBUG: BeforeReport_Trigger.Get_Message_Details
    MSG-00100: DEBUG: BeforeReport_Trigger.Get_Org_Profile.
    MSG-00100: DEBUG: Organization Id: 106
    MSG-00100: DEBUG: BeforeReport_Trigger.Build_Where_Clause
    MSG-00100: DEBUG: P_Choice: NEW
    MSG
    Report Builder: Release 10.1.2.3.0 - Production on Tue Jan 22 06:47:00 2013
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    Start of log messages from FND_FILE
    End of log messages from FND_FILE
    Program exited with status 1
    Concurrent Manager encountered an error while running Oracle*Report for your concurrent request 945196.
    Review your concurrent request log and/or report output file for more detailed information.
    Successfully resubmitted concurrent program XXBREG_RAXINV_NEW_XMLP with request ID 953242 to start at 23-JAN-2013 05:15:00 (ROUTINE=AFPSRS)
    Executing request completion options...
    Output file size:
    13010844
    ------------- 1) PUBLISH -------------
    Beginning post-processing of request 945196 on node EBSAPPPROD at 22-JAN-2013 06:49:36.
    Post-processing of request 945196 completed at 22-JAN-2013 06:49:59.
    Finished executing request completion options.
    Concurrent request completed
    Current system time is 22-JAN-2013 06:49:59
    Regards,
    Smita

    Hi,
    Since you said the behavior is sporadic and also the program was running good in 11i instance, I think its a problem with the data [or select query in the concurrent program] .
    Ideal scenario:
    1. Upon the concurrent program completing in error the pdf should not be generated in first place, since it misguides the obtained report. [Concurrent Program should be modified accordingly, before calling the pdf generation logic you need to check the status of the concurrent program].
    2. It is not likely that the pdf generation should error out upon concurrent program's error, since the concurrent program could have a soft closure of its schema definition [inspite of an uncaught/unhandled exception]
    eg:
    <schema def>
    <Xml element 1> </Xml element 1>
    <Xml element 2> </Xml element 2>
    <Xml element 3> </Xml element 3>
    *_ <while generating elements 4, 5 and so on concurrent program could have errored out, but still the schema definition is valid so the pdf is generated>_*
    </schema def>
    Solution:
    Next time when you get the same behaviour, try running the concurrent program and handle the exception for that scenario, this should resolve your issue.
    Regards,
    Yuvaraj

  • Excise invoice already exists  error in J1IS

    Hello
    Created the Subcontracting PO , and Issue the material to vendor ( mov type 541) with payment of duty, after this created the Excise invoice with T.code J1IS, system was generated the Excise entries in table J_1IEXCDTL and J_1IEXCHDR.
    After that we have reversed the excise entries, so now we got "R"Indicator in status field in above said table J_1IEXCDTL.
    Now system should allow me to create one more excise invoice with same Material document number but sytem was giving error message that "excise invoice already exists"
    Why system was allowing us to create new excise invoice?
    Regards
    sapman man

    hi
    you can't create another Excise document with same Material Doc.Because for this Material document already Excise document exit even though it is reversed.i think you have to delete Material document from J_1IEXCDTL and J_1IEXCHDR. then try to create new
    regds
    Rami

  • Deemed exports not getting created when excise invoice generated in backgro

    Hi guys,
    when i create an excise invoice in background .and try to create ARE-3 in J1IA301.I am getting a error (081091004/2009 excise invoice is meant for normal invoice).
    when i create excise invoice manually and click on goto - utilization . The excise invoice type will be local .If i click on the pencil tab it will change to EXPORT and we can see DEEMED in blue color after this i will save and create ARE-3. ARE-3 gets generated.
    while creating excise invoice in background the EXCISE INVOICE TYPE in J1IIN will be LOCAL and we will not be able to change after this when i try to create ARE - 3 IAM GETTINGTHE ERROR..
    Please help me out of this..
    As my client wants to create the excise invoice in background while billing document is created..
    Regards,
    Shivdeep B

    Hi,
    If you want to create excsie invoice in back ground while creating billing document for  Deemed exports.
    Please follow the navigation as mentioned below.
    SPRO - Logistic General - Tax on goods movement - India - Business transaction - Out going Excise invoice - Maintain default Excise group and series group.
    Here please maintain you Plant, Excise group & Series group for deemed exports sales area combination and export type as Deemed exports in *details screen*. Now system will  create excise invoice for deemed exports in background while creating the billing document go to display excise invoice and see the utilization you get Deemed exports.
    This will do for you.

Maybe you are looking for