LINEST Standard Error Order

In the online information about the LINEST function, there is a table that lists the additional statistics.  It shows that the slopes are returned in row 1 but in the reverse order (S5, S4...S1), while the standard errors are returned in row 2 in standard (non-reserved) order (SE1, SE2...SE5  This relationship is also stated tbelow the table.
But, this seems to be incorrect.  Both slopes and SE are returned in reverse order. (I am using Numbers version 3.2.2).
For example, with 2 known-x-values, the slope of the first (lefthand) X is obtained using INDEX(LINEST(...), 1,2), and, the correct SE for this slope is obtained using INDEX(LINEST(....), 2, 2) -- not INDEX (..., 2, 1) as the table (and text) would instruct.
Is this an error of interpretation (and use) of the INDEX function, or is there an error in the documentation?

hi friend!!!!!
i face this query i am trying to share with you
1) maintain tax value e.g. 12 or 16 whatever in condition record by VK11
2) go to path IMG--SD-BASIC FUNCTION-TAX---
  now you see
a)define tax determine rule
  in that maintaion MWST  for country and is it liable for tax or not by 0,1,
b)define tax rel....of master re..
   in that for customer and material maintaion
for customer  maintaion no tax , full tax , half tax by 0,1,etc
for material  maintaion  liable, and tax exempt
i hope i try my best
if useful please reward
if not mail me [email protected]
i will try
0

Similar Messages

  • Re: Error in submitting Import Standard Purchase orders from Pl/Sql

    Hi All,
    Iam using the following code to submit a concurret program
    "Import Standard Purchase orders" from pl/sql
    Program is sucessfully submittted but it is Completing in error status i am stuck there please help me in resolving this
    My instance R12
    My Code
    ======
    DECLARE
    v_request_id VARCHAR2 (100);
    BEGIN
    mo_global.set_policy_context ('S', 204); --org_id for the operating unit which the purchase order records belong too
    mo_global.init ('PO'); -- sets the application
    FND_GLOBAL.APPS_INITIALIZE (1013436, 50578, 201); --Consists of the user_id, responsibility_id, responsibility_application_id which is 201 for purchasing
    v_request_id :=
    fnd_request.submit_request (application => 'PO',
    program => 'POXPOPDOI',
    description => NULL,
    start_time => NULL, -- To start immediately
    sub_request => FALSE,
    argument1 => '31348', -- Buyer_ID
    argument2 => 'STANDARD', -- Doc Type
    argument3 => '', -- doc subtype
    argument4 => 'N', -- update items
    argument5 => '', -- create sourcing rules not used
    argument6 => 'INCOMPLETE', -- Approval status
    argument7 => '', -- release generation method
    argument8 => '1021387', -- batch_id
    argument9 => '', -- operating unit null
    argument10 => '', -- global agreement null
    argument11 => '', -- enable sourcing null
    argument12 => '', -- sourcing level null
    argument13 => '', -- inv org enabled null
    argument14 => '' -- inv org null
    DBMS_OUTPUT.put_line ('Request submitted. ID = ' || v_request_id);
    COMMIT;
    EXCEPTION
    WHEN OTHERS
    THEN
    DBMS_OUTPUT.put_line (
    'Request set submission failed - unknown error: ' || SQLERRM
    END;
    output
    =====
    when i check output i am getting the follwing error
    DECLARE
    ERROR at line 1:
    ORA-06510: PL/SQL: unhandled user-defined exception
    ORA-06512: at line 133
    Log message
    ==========
    +-----------------------------
    | Starting concurrent program execution...
    +-----------------------------
    Arguments
    31348
    STANDARD
    N
    INCOMPLETE
    1021387
    Start of log messages from FND_FILE
    To get the log messages for PDOI, please use the following id to query against FND_LOG_MESSAGES table:
    AUDSID = 945297
    ORA-01403: no data found in Package po.plsql.PO_PDOI_PVT. Procedure init_sys_parameters.0
    ORA-01403: no data found in Package po.plsql.PO_PDOI_PVT. Procedure init_startup_values.10
    ORA-01403: no data found in Package po.plsql.PO_PDOI_PVT. Procedure start_process.50
    User-Defined Exception in Package po.plsql.PO_PDOI_Concurrent. Procedure POXPDOI.30
    End of log messages from FND_FILE
    Thanks
    Manoj kumar

    Pass NULL instead of ''
    Check the flag
    SELECT multi_org_category
      FROM fnd_concurrent_programs
    WHERE concurrent_program_name = 'POXPOPDOI'Update it as per the below MOS Doc
    R12 / POXPOPDOI - 'ORA-01422' Error While Running 'Import Standard Purchase Orders' [ID 457628.1]
    Otherwise,
    Follow the below doc and insert values to the interface tables (headers, lines and distribution) and run the Import Standard Purchase Orders from the front end.
    How To Diagnose Problems With Importing Standard Purchase Orders [ID 781351.1]
    HTH
    Cheers,
    ND
    Use the "helpful" or "correct" buttons to award points to replies / Mark the thread as answered, if your question is answered.

  • Error While submitting Import Standard Purchase Order Concurrent Program

    Hello All,
    When I am trying to submit Import Standard Purchase Order Concurrent Program from front end, it gets submitted properly.
    and from backend,I am getting Following error.
    To get the log messages for PDOI, please use the following id to query against FND_LOG_MESSAGES table:
    AUDSID = 27810853
    ORA-01403: no data found in Package po.plsql.PO_PDOI_PVT. Procedure init_sys_parameters.0
    ORA-01403: no data found in Package po.plsql.PO_PDOI_PVT. Procedure init_startup_values.10
    ORA-01403: no data found in Package po.plsql.PO_PDOI_PVT. Procedure start_process.50
    User-Defined Exception in Package po.plsql.PO_PDOI_Concurrent. Procedure POXPDOI.30
    When I looked in Parameters in both program(manually submitted and called from backend) I found a difference.
    difference is Parameter Operating Unit. It not get submitted while program calling from backend.
    Please anybody tell me solution for this. for setting this parameter.
    (Also I have applied for patch 13001705 as per Metalink suggested).
    Thanks in advance.
    Regards
    Ravi Raj.
    Edited by: Ravi Raj on Jan 23, 2013 10:50 PM

    Please paste the code here.. there may be some parameter issue while submission.

  • Import Standard Purchase Orders return error

    Dear All ,
    when i ran the Import Standard Purchase Orders concurent program , it completed with the following errors
    DECLARE
    ERROR at line 1:
    ORA-06510: PL/SQL: unhandled user-defined exception
    ORA-06512: at line 133
    So please can anyone have a solution for this >>

    What is your application release? Please see if these docs help.
    Import Standard Purchase Order Process Fails With Errors 'ORA-06510' and 'ORA-06512' [ID 862819.1]
    PDOI Errors With Exec Fnd_conc_stat.Collect Ora-06510 [ID 735909.1]
    R12 PDOI Fails With ORA-6510 When Loading Quotation [ID 856940.1]
    Error POCIRM-158e : ORA-06510: PL/SQL: unhandled user-defined exception Returned When Running Requistion Import Process. [ID 430797.1]
    Thanks,
    Hussein

  • Calculating Standard Error from Linest

    I graphed some data as a bar chart and included positive & negative standard error bars. When I try to have the calculation of standard error in the associated data table, I find that the only function available is the standard deviation, which is related but not the same. My understanding is that the Linest function will produce an array of numbers, one of which is standard error, but I cannot figure out how that function works. How is the array produced? I tried inserting the Linest function in a cell of a table separate of my data table but it only put the number which is in the A-1 cell of the array shown in the Linest explanation and I don't understand how the rest of the array is filled out. The standard error for Y, which is what I am trying to obtain, is in cell B-4 of the array as I recall.

    S,
    If you open the Function Browser and select LINEST, under Usage Notes you will find a link titled "Additional Statistics". The linked content includes a map of the LINEST array. Use the INDEX function to access the element of the array that you are interested in. You may need to read the INDEX function description to know how to use it.
    Jerry

  • Error while creating standard sales order

    Hi
    While creating a standard sales order , I am getting a problem  in the incompleteness log asking for the internal sales order no. in the 'accounting' tab of my order. It is related to cost assignment and profitability segment no.I am not able to to find the order no. for dat.
    What settings should i make in spro so that this incompletion  does not comes again while saving the order ? Shud i make changes at the item category level or  the sales document type level or at the material master data ???

    Hi Gurulos,
                       Go to transaction "KO01" and create an Internal order by taking a reference order .If you know your controlling area just press "F4" at the Reference order tab and you will find the reference orders. Take one of them and create a new one and assign the same to your order. Kindly please let me know If you need any more information on this.
    Regards
    Ram Pedarla

  • Import standard Purchase Order process and interface tables

    Hi all,
    We are populating three PO interface tables from our custom developed application. PO_HEADERS_INTERFACE, PO_LINES_INTERFACE and PO_DISTRIBUTIONS_INTERFACE. We are using 11.5.10.2 version of Oracle Apps.
    Initially we did not manage to populate the distributions interface table, but, now we are populating it. And after doing so, when we run the Import standard Purchase Order process for 'Approved' POs, the process_id for even the record which has correct distributions info also gets 'Rejected' as a value. The process is considering a mix of records : the approved POs that DO NOT HAVE distribution info in PO_DISTRIBUTIONS_INTERFACE (which we had not managed to populate) and the approved POs that HAVE distribution info in PO_DISTRIBUTIONS_INTERFACE.
    does the Import standard Purchase Order process populate partial data that could be good or it rejects the whole lot of records?
    Can anyone guide on this issue?
    Thanks and kind regards,
    Aparna
    Edited by: Aparna on Jul 24, 2009 3:45 AM
    Another piece of info I would like to share is
    I have run the process for an approved PO with distributions info in PO_DISTRIBUTIONS_INTERFACE. This time no mixed data. In PO_INTERFACE_ERRORS table, an entry was found: for column name : PO_DISTRIBUTION_ID in ERROR_MESSAGE column 'Error: Has no distributions'.
    Edited by: Aparna on Jul 24, 2009 8:03 AM
    After carrying out number of tests, I have found out that
    1) if the approval_status for the po is 'Approved' in the po_headers_interface table, it gives the above mentioned error and the process_id is 'rejected'.
    2) if the approval_status for the po is 'Incomplete' in the po_headers_interface table, the process add the 'accepted' value for the process_id. But, the charge account number is not populated in shipments.
    Edited by: Aparna on Jul 31, 2009 1:07 AM
    There has been some progress on this issue. The process sees distributions data into the PO_DISTRIBUTIONS_INTERFACE table. Yet the following errors are found in the process log file:
    Start dist default process
    before getting period name
    after getting period name
    -->Intfc error occurred ...PO_PDOI_INVALID_GL_ENC_PER
    before workflow
    unit price = 18.5, rate = , unit price in functional currency = 18.5
    after workflow
    Start dist creation process
    Start dist validation process
    -->Intfc error occurred ...PO_PDOI_INVALID_BUDGET_ACCT
    Start insert new record into po_distributions
    Distribution ID: 252
    dist num: 1
    last updated by: 1189
    po header id: 5283
    po line id: 5878
    line loc id: 5924
    sob id: 21
    cc id: 1560
    qty ordered: 10
    Req Header Ref num :
    Req line Ref num :
    Req dist id :
    ROW ID: AAHUc1AFPAAAQ04AAC
    call tax
    Rollback for the Last Errored Line: 10
    All Lines in error - Rolling back the header
    We opened new GL periods for the calendar and yet same errrors are seen. Can anyone suggest any solution?
    Kind regards,
    Aparna

    Hi
    Do you have a copy of your insert statement?
    regards

  • Unable to preview Contract Terms for Standard Purchase Order

    Unable to preview View Contract Terms for Standard Purchase Order,displays error
    We have defined the same contract terms and Document type layouts to documents Contract Purchase Order and Standard Purchase Order.
    Created a Contract PO,Attached a template able to preview the contract template in PDF successfully
    Created a Standard PO,Attached a template not able to preview the contract template in PDF
    Displays the foll error
    Problem: The system could not generate the PDF document.
    Reason: The system detected an error in the following code/object.
    Code: XML
    Object: PO
    Action: Please contact the system administrator and try again
    ### Steps to Reproduce Problem ###
    Steups
    Created a custom XSL-FO template for Contract template and defined it for Standard PO and Contracts PO.
    Steps to Reproduce
    1.Create a PO,give any category of 100 Qty
    2.Click Terms and CLick Author Contract Terms\
    3.Select the custom Template ,Click Apply Template
    4.Click Preview.
    Following error displayed
    Problem: The system could not generate the PDF document.
    Reason: The system detected an error in the following code/object.
    Code: XML
    Object: PO
    Action: Please contact the system administrator and try again
    Please Note:The above scenario works for Contracts PO.
    The problem is only for Standard PO
    We have reviewed note:454479.1
    The file version of POXVCOMB.pls 115.69.11510.28
    But we have another test instance this also has the same version , the scenario works fine
    So we are confused why this is reproducible only for a particular instance with same file versions
    If anyone can suggest a solution pls give me a reply
    Already SR is logged for the same -SR 3-1272761221, awaiting reply from support

    Please reply if any update on the above query is present.

  • ESYU: Importing Standard Purchase Orders에서 문제 발생시 진단 방법

    Purpose
    Oracle Purchasing - Version: 11.5.10.2 to 12.0.6
    Information in this document applies to any platform.
    ConcurrentProgram:POXPOPDOI - Import Standard Purchase Orders
    이 문서는 reader게 Importing Standard Purchase Orders 실행 중 갑자기 발생하는 issue에 대해 어떻게
    대응하는지에 대한 자세한 정보를 제공한다.
    Instroduction
    Purchase Document Open Interface는 다량의 Standard Purchase Order는 Oracle Purchasing으로 빨리
    import 할 수 있게 한다. Import process는 import 되어야 하는 document information을 PO interface tables에
    넣어주는 작업을 필요로하며, data를 validate 하고 application에 PO를 생성하거나 error message를 return 하는
    Import Standard Purchase Orders concurrent program을 실행한다.
    이 문서의 목적은 Importing Standard Purchase Orders에 관련된 process를 이해하거나 갑자기 발생한 문제의
    원인을 찾는데 도움을 주기 위함이다. PO import 문제는 일반적으로 interface tables에 입력된 불일치하는 data가
    원인이며, 일단 문제가 확인되면 Metalink는 비슷한 문제를 찾아주거나 Oracle Support에 Service Request를 log
    할 수 있다.
    Test case Information
    1. 아래 insert 문장을 이용하여 PO interface tables에 data를 입력:
    INSERT INTO po.po_headers_interface
    (interface_header_id,
    action,
    org_id,
    document_type_code,
    currency_code,
    agent_id,
    vendor_name,
    vendor_site_code,
    ship_to_location,
    bill_to_location,
    reference_num)
    VALUES
    (apps.po_headers_interface_s.NEXTVAL,
    'ORIGINAL',
    207, -- Seattle
    'STANDARD',
    'USD', -- Your currency code
    24, -- Your buyer id stock
    'Advanced Network Devices',
    'FRESNO',
    'V1- New York City', -- Your ship to
    'V1- New York City', -- Your bill to
    'Currency test') -- Any reference num
    INSERT INTO po.po_lines_interface
    (interface_line_id,
    interface_header_id,
    line_num,
    shipment_num,
    line_type,
    item,
    uom_code,
    quantity,
    --unit_price,
    promised_date,
    ship_to_organization_code,
    ship_to_location)
    VALUES
    (po_lines_interface_s.nextval,
    po_headers_interface_s.currval,
    1,
    1,
    'Outside processing',
    'Flooring OSP',
    'Ea',
    1,
    --17.50,
    '10-APR-2009',
    'V1',
    'V1- New York City' )
    INSERT INTO po.po_distributions_interface
    (interface_header_id,
    interface_line_id,
    interface_distribution_id,
    distribution_num,
    quantity_ordered,
    charge_account_id)
    VALUES
    (po_headers_interface_s.currval,
    po.po_lines_interface_s.CURRVAL,
    po.po_distributions_interface_s.NEXTVAL,
    1,
    1,
    12975) -- Your Charge Account Id
    2. Interface tables에 data가 insert 되었다면 import progra을 실행전 정보를 확인하기 위해 아래 query 문을 이용한다.
    a - Select * from PO_HEADERS_INTERFACE where INTERFACE_HEADER_ID=&headerid
    b - Select * from PO_LINES_INTERFACE where INTERFACE_HEADER_ID=&headerid
    c - Select * from PO_DISTRIBUTIONS_INTERFACE where INTERFACE_HEADER_ID=&headerid
    3. Data를 review 했으면 Import Standard Purchase Orders program을 실행한다.
    Parameter >>
    Default Buyer: Null
    Create or Update Items: No
    Approval Status: INCOMPLETE
    Batch Id: Null
    4. 만일 program에 문제가 있어 error가 발생한다면 error의 원인을 제공하기 위해 Purchasing Interface Error Report를
    실행할 수 있다.
    Parameter >>
    Source Program: PO_DOCS_OPEN_INTERFACE
    Purge Data: No
    만일 PO가 import 되지 않았다면 Puchasing Interface Errors Report와 동일한 정보를 보기 위해 Interface Errors table을
    아래 SQL을 이용하여 조회할 수 있다.
    SELECT * FROM PO_INTERFACE_ERRORS WHERE INTERFACE_TRANSACTION_ID ='&recordsinterfacetransid';
    Diagnostics
    Import Standard Purchase ORder process의 troubleshoot 도움을 위해 아래 Diagnostics과 Reports를 이용한다.
    1. Diagnostics Tool : Oracle Purchasing Purchasing Documents Open Interface Data Collection Test
    (please refer to Note 224887.1 for assistance)
    이 Diagnostics는 import program에 의해 import 되는 data를 validate 할 것이며 missing 되거나 맞지않는 정보를 highlight 한다.
    이 Tool은 interface tables에 있는 맞지 않거나 불완전한 data의 자세한 정보를 제공할 수 있다.
    Error는 PO를 import 할 때 발생한 문제 분석을 시도하는데 매우 유익하므로 SR을 log시 이 Diagnostic output을 upload 하는
    것을 권장한다.
    2. Purchasing Interface Errors Report
    이 report는 Oracle Purchasing에서 사용가능하며 Import Standard Purchase Orders program을 실행시 발생하는
    error를 강조한다.
    Tracing
    11.5.10 이상의 version에서 Import Standard Purchase Orders program의 trace를 생성:
    1. Navigate to System Administrator responsibility
    2. Navigate to Profiles->System
    3. Query the Profile Option Concurrent: Allow Debugging and set it to Yes at User level
    4. Navigate to Purchasing responsibility
    5. From the Requests form, choose the Import Standard Purchase Orders program and set the required Parameters
    6. Click the Debug button
    7. Check the SQL Trace checkbox and specify Trace with Binds and Waits
    8. Submit the Concurrent program
    9. Retrieve the trace file created.
    Logging
    Import Standard Purchase Orders program의 FND Deug Log 생성:
    1. Log_seq를 아래 SQL을 이용하여 확인.
    select max(log_sequence) from fnd_log_messages;
    2. Set the following profiles at the user level:
    FND: Debug Log Enabled = YES
    FND: Debug Log Filename = NULL
    FND: Debug Log Level = STATEMENT
    FND: Debug Log Module = %
    3. Run Import Standard Purchase Orders program
    4. Using a SQL client run the following query :
    Select * from fnd_log_messages
    where log_sequence > &log_seq_noted_above
    order by log_sequence;
    이 query의 output은 Import Standard Purchase Orders program이 실행 중 발생한 error를 표시한다.
    Reference
    Note 781351.1

  • Need to modify Standard Purchase Order Stylesheet (PO_STANDARD_XSLFO.xsl)

    Hi
    We need to modify Standard Purchase Order Stylesheet (po_standard_xslfo.xsl) . Current stylesheet generating PO like the following.
    <FOR-EACH>
    ITEM_NUM
    ITEM_DESCRIPTION
    <FOR-EACH>
    SHIP_TO_ADDRESS_LINE1 NEED_BY_DATE QUANTITY
    </FOR-EACH>
    </FOR-EACH>
    Based on this, we are getting the output like this:
    Item Num 1
    Itme Description 1
    Ship To: Needed: Quntity
    1234. A1 Avenue JUL 200
    SomeCity, CA 90706
    1234. A1 Avenue AUG 200
    SomeCity, CA 90706
    4567 B1 Avenue JUL 100
    City2 , CA
    Itme Description 2
    Ship To: Needed: Quntity
    5689. c1 Avenue JUL 200
    SomeCity, CA 90706
    Our requirement is like this:
    Item Num 1
    Itme Description 1
    Ship To: 1234. A1 Avenue, SomeCity, CA 90706
    Month: JUL AUG SEP
    Quantity: 200 200 100
    Ship To: VVV4567 B1 Avenue , SomeCity, CA 90706
    Month: JUL AUG SEP
    Quantity: 100 200 100
    So we need to add ship_to group (ITEM/SHIP_TO) .
    How can we use group by item, ship_to..
    <fo:block> <xsl:value-of select="ITEM_NUM"/> </fo:block>
    <fo:block> <xsl:value-of select="ITEM_DESCRIPTION"/> </fo:block>
    <xsl:for-each select="/PO_DATA/LINES/LINES_ROW/LINE_LOCATIONS/LINE_LOCATIONS_ROW">
    <fo:block> <xsl:value-of select="SHIP_TO_ADDRESS_LINE1"/> </fo:block>
    <fo:block> <xsl:value-of select="substring(NEED_BY_DATE,4,3)"/> </fo:block>
    <fo:block> <xsl:value-of select="QUANTITY"/> </fo:block>
    </xsl:for-each>
    </xsl:for-each>
    In the above code I need split the data by ITEM_NUM/ SHIP_TO_ADDRESS_LINE1.
    I am new to xsl-fo. I tried different ways,but ship_to_address_line1 is generating wiith each quanty and need_by_date.
    Please guide me.
    Thank you
    Raju
    Edited by: subbaraju on May 7, 2009 2:36 PM

    Hi Chandra
    Thank you very much for your suggestion.
    I tried that way, I created some sample xml file, I created sample rtf file and I generated xsl-fo file. I copied the part of code into my PO_STANDARD_PO.XSL. I am getting some error.
    I noticed PO_STANDARD_PO.XSL is xsl version 1.0 and the generated sample data is with xsl version 2.0.
    The generated code is using “for-each_group”, “sum()”, “current-group()” etc. Is these functions will work in xslt 1? Or do we need to code different way?
    We are in Oracle APPS 12.0.4.
    Thank you
    Raju
    Edited by: subbaraju on May 26, 2009 11:56 AM

  • How to modify date format for Standard Purchase Order  Template XSL-FO

    I am editing the XSL-FO for the Standard Purchase Order.
    I need to modify the promised date column to 'DD-MON-YYYY’' , tried to use substring in below line but it didn't work
    <xsl:value-of select="LINE_LOCATIONS/LINE_LOCATIONS_ROW/PROMISED_DATE"/>
    Any solution for this ?
    thanks
    Pravin

    Thanks for your response.
    I tried to change the code in below format but it was giving error.
    Original code
    <xsl:value-of select="LINE_LOCATIONS/LINE_LOCATIONS_ROW/PROMISED_DATE"/>
    modified to
    <xsl:value-of select="xdoxslt:format_date(LINE_LOCATIONS/LINE_LOCATIONS_ROW/PROMISED_DATE,'dd-mmm-yyyy','dd/mmm/yyyy hh24:mi:ss',$_XDOLOCALE,$_XDOTIMEZONE)"/>
    also tried with
    <xsl:value-of select="xdoxslt:format_date(LINE_LOCATIONS/LINE_LOCATIONS_ROW/PROMISED_DATE,'dd-mmm-yyyy','dd-mmm-yyyy hh24:mi:ss',$_XDOLOCALE,$_XDOTIMEZONE)"/>
    also tried like
    <xsl:value-of select="xdoxslt:format_date(LINE_LOCATIONS/LINE_LOCATIONS_ROW/PROMISED_DATE,'dd-mmm-yyyy','dd/mmm/yyyy',$_XDOLOCALE,$_XDOTIMEZONE)"/>
    Tried above 3 methods but it didn't work.
    right now the date format in pdf file is 24-MAY-2011 21:56:24 i need to remove 21:56:24 and have only 24-MAY-2011
    any suggestions.
    thanks

  • Unable to approve standard Purchase order

    Hi ,
    We are into 11.5.10.2 , We are getting following error when trying to approve the purchase order by approver . PO Status is in "Pre approved"
    unable To Approve Standard Purchase Order 975761
    Line # 17 At least one or more item attributes failed validation.
    Action: Verify values for the following attributes: purchasing_enabled_flag, stock_enabled_flag, outside_operation_flag and bom_item_type.
    Please, fix the problem and try approving again from this notification or send the document back to the preparer.
    PO is going to top Hierarchy inspite of having enough aprroval limits .
    Item attributes was set to Inactive in Master Level and was active in Organization items . Changed to Active in Master Item and still getting the issue .
    PO is getting forwarded to next approver and finally it is in "pre approved status " with above error
    Thanks in Advance
    Kiran

    Hi Kartik,
    1) In Item Master , status is set to OBSOLETE and purchasable check box is unchecked . Item master organization was set in purchasing options .
    2) Organization item , status is Active . stockable and Purchasable check boxes are checked and outside processing item unchecked . This is receiving org in Purchasing .
    I think Purchasing is considering Master org status as it is validation org for purchasing .
    Thanks
    Kiran

  • How to add Signatre to Standard Purchase Order Template XSL-FO

    I need to add digital signature to the standard Purchase Order Template which is sent to supplier.
    could you let me know the process.
    thanks
    Edited by: 855902 on May 24, 2011 8:00 PM

    Thanks for your response.
    I tried to change the code in below format but it was giving error.
    Original code
    <xsl:value-of select="LINE_LOCATIONS/LINE_LOCATIONS_ROW/PROMISED_DATE"/>
    modified to
    <xsl:value-of select="xdoxslt:format_date(LINE_LOCATIONS/LINE_LOCATIONS_ROW/PROMISED_DATE,'dd-mmm-yyyy','dd/mmm/yyyy hh24:mi:ss',$_XDOLOCALE,$_XDOTIMEZONE)"/>
    also tried with
    <xsl:value-of select="xdoxslt:format_date(LINE_LOCATIONS/LINE_LOCATIONS_ROW/PROMISED_DATE,'dd-mmm-yyyy','dd-mmm-yyyy hh24:mi:ss',$_XDOLOCALE,$_XDOTIMEZONE)"/>
    also tried like
    <xsl:value-of select="xdoxslt:format_date(LINE_LOCATIONS/LINE_LOCATIONS_ROW/PROMISED_DATE,'dd-mmm-yyyy','dd/mmm/yyyy',$_XDOLOCALE,$_XDOTIMEZONE)"/>
    Tried above 3 methods but it didn't work.
    right now the date format in pdf file is 24-MAY-2011 21:56:24 i need to remove 21:56:24 and have only 24-MAY-2011
    any suggestions.
    thanks

  • How to Check Log File for 'Import Standard Purchase Orders' program?

    Hi,
    When the run the standard program 'Import Standard Purchase Orders' after inserting data to PO interface tables. I am getting the log message as mentioned below.
    Start of log messages from FND_FILE
    To get the log messages for PDOI, please use the following id to query against FND_LOG_MESSAGES table:
    AUDSID = 40499066
    End of log messages from FND_FILE
    When I go and check for the message in mentioned table against the AUDSID,I couldn't find any error listed.
    Even I verified the po_interface_errors table, It returns NO ROWS.
    Help me on this issue.
    Thanks.

    Did you checked the imported PO ? follow step 7-8 from MOS note and check
    Vision Demo - How To Import Standard Purchase Orders Using the Purchase Document Open Interface PDOI [ID 1054004.1]
    You can also check
    How To Diagnose Problems With Importing Standard Purchase Orders [ID 781351.1]
    thanks

  • Import Standard Purchase Orders Programs Rejects Records

    Hi Guys
    I have a simple PL/SQL Block to Insert Standard PO Orders into PO_HEADERS_INTERFACE Table.
    The following is the code :
    DECLARE
    V_REQUEST_ID NUMBER:=0;
    -- Start PL/SQL Block --
    BEGIN
    -- Insert Validated Records into PO Interface Tables --
    INSERT INTO PO_HEADERS_INTERFACE
    (INTERFACE_HEADER_ID,
    BATCH_ID,
    ACTION,
    ORG_ID,
    DOCUMENT_TYPE_CODE,
    CURRENCY_CODE,
    AGENT_ID,
    VENDOR_NAME,
    VENDOR_SITE_CODE,
    VENDOR_CONTACT_ID,
    SHIP_TO_LOCATION,
    BILL_TO_LOCATION,
    PAYMENT_TERMS,
    FREIGHT_CARRIER,
    FOB,
    FREIGHT_TERMS,
    APPROVAL_STATUS,
    CREATION_DATE,
    CREATED_BY,
    LAST_UPDATE_DATE,
    LAST_UPDATED_BY,
    LAST_UPDATE_LOGIN)
    VALUES
    (1,
    100,
    'ORIGINAL',
    204,
    'STANDARD',
    'USD',
    13587,
    'Advanced Network Devices',
    'FRESNO',
    1506,
    'M1- Seattle',
    'V1- New York City',
    'Immediate',
    'UPS',
    'Origin',
    'Due',
    'INCOMPLETE',
    '14-NOV-2008',
    1008152,
    '14-NOV-2008',
    1008152,
    1008152);
    DBMS_OUTPUT.PUT_LINE('Header Records Inserted');
    COMMIT;
    END;
    The Records have been sucessfully inserted into PO_HEADERS_INTERFACE Table but whne i run the Import Standard Purchase Orders Program by passing my Batch ID = 100 as the parameter systems Rejects the Records but doesnt
    update the PO_INTERFACE_ERRORS Table.
    Could anybody please guide me. This is quite urgent.
    Regards
    Nakul.V

    Not sure of what release are You working with. Review if You have the Diagnostic Tools responsibility, it has a diagnostic for po documents open interface that reports warning on errors on data on staging tables.

Maybe you are looking for