Error Standard Purchase order form POXPOEPO

Hi ,
I am unable to save any information in my PO screen (POXPOEPO) . Actually it's not throwing any error . Whenever we try to close it ask us save . If click ok and save the form and try to exit . Samething happeining again .
And also , we see some strange checkbox available in the screen "Enable all Site" below Terms button . I never came across this before .
Oracle Release :R11i
Database : 10.1.0.4
Linux x86.
Thanks
Regards
Muthu

Hi ,
This is due to compilation of forms . Once we compiled and regenerated neccessary form files . Everthing solved .
Thanks
Regards
Muthu

Similar Messages

  • How to find Script Style for Standard Purchase Order Form "MEDRUCK".

    Hi ,
    I need to convert script style using by Sap-script form 'Medruck' to Smart form style and for this i have to find Sap-script style name for Medruck.
    If anyone have a idea about it then plz tell me.
    It's very urgent for me.
    Thanks & Regards,
    Gaurav.

    Hi Gaurav,
    If I'm not wrong, we don't have any SAP-Script Style, but when we are trying to upgrade to SmartForms simply u upgrade using smartforms transaction code, and it will convert all your character formats and paragraph formats and try to assign as SYSTEM Style in Smartforms.
    If you find the difference then you need to create SmartStyle manually and assign it.
    Thanks,
    -Pavan

  • RAISE form_trigger_failure not working in purchase order form

    Hi,
    I am working on a customization in Purchase Order Form (poxpoepo)
    This is what I tried to do.
    CURSOR 1_cur IS
    SELECT pol.LINE_NUM v_line
    ,gcc.segment1 v_seg
    FROM gl_code_combinations gcc
    ,PO_DISTRIBUTIONS_ALL pod
    ,po_lines_all pol
    WHERE SUBSTR(gcc.SEGMENT1,1,1) = 'X'
    AND gcc.code_combination_id = pod.code_combination_id
    AND pod.PO_LINE_ID = pol.PO_LINE_ID
    AND pol.po_line_id = v_po_line
    AND pol.PO_HEADER_ID = v_po_header;
    CURSOR 2_cur IS
    SELECT pol.LINE_NUM v_line
    ,gcc.segment1 v_seg
    FROM gl_code_combinations gcc
    ,PO_DISTRIBUTIONS_ALL pod
    ,po_lines_all pol
    WHERE SUBSTR(gcc.SEGMENT1,1,1) = 'X'
    AND gcc.code_combination_id = pod.code_combination_id
    AND pod.PO_LINE_ID = pol.PO_LINE_ID
    AND pol.PO_HEADER_ID = v_po_header;
    BEGIN
    v_error_found := false ;
    IF (form_name = 'POXPOEPO' AND
    (block_name IN ('PO_LINES' ,
    'PO_SHIPMENTS',
    'PO_DISTRIBUTIONS') AND
    event_name = 'WHEN-NEW-ITEM-INSTANCE') OR
    (block_name = 'PO_HEADERS' AND
    event_name = 'WHEN-NEW-RECORD-INSTANCE' AND
    name_in('SYSTEM.BLOCK_STATUS') = 'QUERY' ) OR
    (block_name = 'PO_APPROVE' AND
    event_name = 'WHEN-NEW-BLOCK-INSTANCE' )
    ) AND
    NAME_IN('PO_LINES.PO_HEADER_ID') IS NOT NULL AND
    NAME_IN('PO_LINES.PO_LINE_ID') IS NOT NULL AND
    name_in('PO_LINES.LINE_NUM') >= 1 ) THEN
    v_po_header_id := NAME_IN('PO_LINES.PO_HEADER_ID');
    v_po_line_id := NAME_IN('PO_LINES.PO_LINE_ID');
    v_line_num := NAME_IN('PO_LINES.LINE_NUM');
    IF block_name in ('PO_LINES' , 'PO_SHIPMENTS', 'PO_DISTRIBUTIONS') THEN
    v_seg := null;
    FOR cursor1 in 1_cur
    LOOP
    if cursor1.v_seg = 'X' THEN
    v_seg := 'X';
    v_line_num := cursor1.v_line;
    EXIT;
    end if;
    END LOOP;
    ELSIF block_name in ('PO_HEADERS','PO_APPROVE') THEN
    FOR cursor2 in 2_cur
    LOOP
    if cursor2.v_seg = 'X' THEN
    v_seg := 'X';
    v_line_num := cursor2.v_line;
    EXIT;
    end if;
    END LOOP;
    END IF;
    IF v_seg = 'X' then
    fnd_message.set_string('custom message to be displayed.');
    FND_MESSAGE.ERROR;
    IF block_name = 'PO_APPROVE' THEN
    go_block('PO_HEADERS');
    raise form_trigger_failure;
    END IF;
    END IF;
    END IF;
    END;
    I actually want to achieve somewhat like this. When ever the charge account field start with 'X' or in other words if segment1 is 'X' and if changes are made to that line like note to supplier is changed and saved then the user should not be allowed to approve/reapprove the order and it shall pop up the message and ONLY restrict from going further if the user hits the APPROVE button. Highlighted in bold should have actually taken care of the requirement from proceeding to the next level of approval but it is not. I have had several debug messages and I am pretty sure that it is satisfying the condition of going to the PO_APPROVE block and still not raising form trigger failure. Could you please help me handle this scenario?

    Your Raise works -- it will terminate your procedure, Change_Detail_Block_Status.
    But, how are you calling the procedure? It is in THAT place that you should look for your problem.
    If you call the procedure, and then have coded EXCEPTION WHEN OTHERS THEN.... or something similar, you might be ignoring the "Raise FTF".
    In addition, you probably need to add these lines in your form where navigation or a commit or similar code causes a trigger to call your procedure:
    If not Form_Success then
    Raise Form_Trigger_Failure;
    End if;

  • Purchase order form printing is required in preprinted stationary format

    Dear All,
    I need one VERY URGENT HELP from you.
    Client wants to do printing Purchase order form in preprinted stationary format i.e. using this format they want to print PO document only for certain variable fields each time in our Laser printer,but some fields (which are already) lying will not be printed. (But in the PDF Download of the form for each document number all the fields must appear).
    Could you please guide me what are the sequential steps need to be followed, where & how in order to incorporate "preprinted stationary format" scenario in my
    Purchase order form. Also, if possible, please tell me in brief what is the meaning of preprinted stationary format & why we are using it / purpose of it.
    Awaiting your favorable reply at the earliest.
    FYI. Anyways, I have convinced Client that we will provide PDF attachment of form only to them, not Excel attachment. Thanks very much for encouraging me.
    Thanks & Regards
    Sudipta

    Hi,
    Thank you for your valuable input.
    Please tell me what should be my approach i.e. sequential steps need to be followed & where ( with the related configuration / settings changes, necessary coding changes & where, if possible, please send me one realtime scenario and its related documentation related to my concerned issues at the earliest as it will be very beneficial for mine. I have come across this scenario for the 1st time. Kindly guide me with your documents) in order the incorporate the below requirement:
    After modication of standard Purchase order form using SAPSCRIPT I / Client want to download it into PDF attachment individually corresponding to each PO number. In this PDF attachment all the fields will appear.
    But when I / Client will take Printout of this modified PO form (say for example ZMEDRUCK) only certain important information / certain field values will be getting printed, not all.
    User will be able to give ranges of PO document numbers for printing at a time based on their requirement, here all documents as specified by the user will be getting printed at a time, but one document printout followed by another document printout , and so on.
    We want to print PO sapscript form in "Print output" only. Also, please guide me how many & which output types, message type etc we need to configure & how for the above requirement ( i.e. download of the ZMEDRUCK form into PDF with its all the fields values + printing this ZMEDRUCK form for printing certain important information using "preprinted stationary format".)
    FYI. We are using Laser Printer for printing SAPSCRIPT forms.
    Awaiting your valuable fruitful feedback with necessary documents at the earliest.
    Thanks a lot.
    Have a very nice time ahead.
    Thanks & Regards
    Sudipta

  • Alignment Changing in the Purchase Order Form

    Hi,
    We are using 11i( 11.5.10.2) with oracle 9i database. I am adding one text item in the Standard Purchase Order form.next to the Unit price text item. when i change the canvas.total alignment is changing and also coming blank space in the form when i open in the application.
    Can anybody suggest on that issue.
    Thanks.

    Hi,
    I am adding one text item in the Standard Purchase Order formI believe this is not supported -- See (Note: 105127.1 - FAQ (Customization)) for details.
    However, if you still want to have this working please verify that you have compile the form successfully after doing the necessary changes.
    Thanks,
    Hussein

  • 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

  • Purchase Order form printing error.

    Hi all experts,
    I am not sure which category I should put this question to. Please guide me if I have raised the question in the wrong category, so that I can raise it at the right category. Sorry!
    I am having some problems in printing Purchase Order form using Simple Mail, let's say I am using output type MAHN. Whenever the PO is generated in Simple Mail, a print preview screen with Output Device is pop up, and require me to key in the details like printer name in order to proceed to next step (which is not necessary for my case).
    Whereas, in normal print preview, there is no such pop up display.
    I am suspecting of it is caused of the setting. But I do not know how to solve it.
    Anyone experienced this before? Please help.
    Thanks in advance.

    Hi Sachin D C,
    I am sorry for the confusing query. Actually what I wanted to say is: -
    1) printing the PO - maintain condition records for output type NEU (working fine)
    2) printing Dunning Deliv Remind - output type MAHN (working fine in manual print out)
    3) printing Dunning Deliv Remind - output type MAHN (not working in simple mail)
    Whenever the Dunning Deliv Remind is generated in Simple Mail, a print preview screen with Output Device is pop up and following by another pop up screen Output Processing analysis.
    Do you have better understanding now?
    Please help.

  • Purchase Order form printout error.

    Hi all experts,
    I am not sure which category I should put this question to. Please guide me if I have raised the question in the wrong category, so that I can raise it at the right category. Sorry!
    I am having some problems in printing Purchase Order form using Simple Mail, let's say I am using output type MAHN. Whenever the PO is generated in Simple Mail, a print preview screen with Output Device is pop up, and require me to key in the details like printer name in order to proceed to next step (which is not necessary for my case).
    Whereas, in normal print preview, there is no such pop up display.
    I am suspecting of it is caused of the setting. But I do not know how to solve it.
    Anyone experienced this before? Please help.
    Thanks in advance.

    Hi Sachin D C,
    I am sorry for the confusing query. Actually what I wanted to say is: -
    1) printing the PO - maintain condition records for output type NEU (working fine)
    2) printing Dunning Deliv Remind - output type MAHN (working fine in manual print out)
    3) printing Dunning Deliv Remind - output type MAHN (not working in simple mail)
    Whenever the Dunning Deliv Remind is generated in Simple Mail, a print preview screen with Output Device is pop up and following by another pop up screen Output Processing analysis.
    Do you have better understanding now?
    Please help.

  • 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

  • Customized R12 Standard Purchase Order report with custom data and layout

    Hi all,
    We need to customize the seeded Purchase Order report in R12 to add an additional section to include cost data coming from our custom table. The key is that our customized report should be launched instead of the seeded report via various PO forms (e.g. View Document menu option, PO Communications form to email, fax and print PO, etc).
    I manually set up a custom Document Type Layout for the Document "Standard Purchase Order" to use my customized template so my custom layout is shown instead of the R12 layout, but according to Oracle support the report can only draw data from a set of seeded Oracle views like po_headers_xml,po_lines_xml etc.
    Any suggestions how we can add our custom data to PO report in R12?
    Thanks! Mike.

    Hi Mike
    thats a tough one, the PO generation is a bit restrictive to say the least when it comes to customizing. It sounds like you have worked out how to get your own template in there to render the PO.
    On the data front, all I can think of is to customize and replace the seeded PO view with one that incorporates your extra data.
    Or, get into the page customization world and write your own extract and format concurrent program/procedure and then hook it onto the buttons where you want to launch it.
    You might have more luch, response wise from the EBS PO forum.
    Procurement : Procurement
    OAF: OA Framework
    Regards
    Tim

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

  • Purchase Order form in Query only mode for some users

    Hi All,
    I want to make the Purchase Orders form as query only for a single user. I tried by giving 'Query_only=Yes' in the parameters section. I am getting 'FRM-04151: You cannot query records here' message more than 10 time. I know we get this message and this is applicable to all the users. But this message is comming more than 10 times.
    Is there anyway that I can restrict the Query only mode to a single user and please suggest about the message also.
    Thanks in Advance,
    Naresh

    Naresh,
    Since you want to achieve this for one user only, I would suggest you create a new function/menu/responsibility and assign this responsibility to the user.
    Note: 400380.1 - How To Create a QUERY-ONLY FORM
    https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=400380.1
    For the FRM error, please review the following document.
    Note: 116074.1 - ACCESS LEVEL - REVIEW ONLY - PO
    https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=116074.1
    Regards,
    Hussein

Maybe you are looking for