Standard purchase order upload to oracle

hi,
we are on oracle apps 11i, database 9i.
I have a custom requirement that requires importing purchase orders to Oracle Apps through database. I was advised to use the following interface tables:
PO_HEADERS_INTERFACE
PO_LINES_INTERFACE
PO_LINE_LOCATIONS_INTERFACE
PO_DISTRIBUTIONS_INTERFACE
insert the data to these tables using a PLSQL procedure and then running the program IMPORT STANDARD PURCHASE ORDERS from front end.
If someone confirms the above is the right method, it would be appreciated.
thanks & regards

Looks correct. Refer to the below links.
http://docs.oracle.com/cd/E19509-01/820-4390/ggtjd/index.html
http://api-wizard.blogspot.com/2012/10/purchase-order-import.html
http://raghuoaf.blogspot.com/2012/03/po-creation-and-import-po.html
Thanks
Shree

Similar Messages

  • 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

  • How to run "Standard Purchase Order Stylesheet" in EBS

    Hi again,
    Please, anybody can give some clue for this?
    In a r12 instance I have the "Standard Purchase Order Data Source" Data Definitio.
    Related to this Data Definition there are 2 Templates
    - Standard Purchase Order Stylesheet
    - Standard Purchase Order Stylesheet with Logo
    my question is... how and were in Oracle Applications (EBS) can I run this report?
    where are defined the parameters?
    I have searched in the concurrent programs, but I have not been able to find it?
    Thanks and regards.
    Juanje

    The two purchase order stylesheets can be used by the "PO Output for Communication" (POXPOPDF) process found under the Purchasing Responsibilities.
    To designate which template you want the "PO Output for Communication" process to use, you can select the template from Purchasing Super User Responsibility > Setup > Purchasing > Document Types. Then select the document type you want to change the template for (i.e. Standard PO) and change the template in the LOV.
    This template is designed in the XSL-FO format, not RTF, so it is substantially more difficult to customize than normal XML Publisher templates unless you're proficient at working with code (it works a lot like HTML once you get used to it).
    I suggest reading the white paper posted under note: 387670.1 at Metalink ("Oracle Purchasing Document Printing and Communication"). It is a decent document about how the Purchase Order PDF process works and how you can approach customizing the template if desired.
    Also, these two (and many other) R12 templates do work in 11.5.10 if you upload them. However, I have not found any good reason to use the R12 template in this case over the 11.5.10 version. There is a lot of extra code specific to R12 functionality that just creates extra overhead (and no notable enhancements for 11i users).
    Regards,
    -Brian

  • Customize Standard Purchase Order template

    We have requirement to customize the 'Standard Purchase Order Stylesheet', XSL template. I am trying to follow the below approach;
    1. Use standard oracle template 'PO_STANDARD_XSLFO.xsl' and customize it as per client requirements.
    2. Create a template definition 'XX Custom Purchase Order stylesheet' similar to 'Standard Purchase Order Stylesheet' in 'Purchasing' responsibility and upload my custom template.
    3. Navigate to Purchasing Super User > Setup > Purchasing > Document Types > 'Purchase Order Standard' > Update Document Type layout > replace 'Standard Purchase Order Stylesheet' with 'XX Custom Purchase Order stylesheet'.
    Please let me know if i have missed any steps.
    Appreciate your time.

    Another approach is to create a new RTF using the tags generated by the PO Output for Communication program. The tags are generated by the columns in the PO_XXX_XML views.
    Sent from my iPhone

  • 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

  • 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

  • Expense Item - Standard Purchase Order Import

    Hi all,
    I am using import standard purchase order - open interface to upload po from legacy system. I can do that with an inventory item, Can anybody tell me what are the mandatory column or requirements for an EXPENSE ITEM .
    I have given destination_type_code='EXPENSE' in po_distributions_interface , and given category_id , description . Even then po is not created.
    Its urgent.
    Thanks
    AADITYA

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

  • How to modify date format for Standard Purchase Order

    In the Standard Purchase Order I have been trying to modify the date format of the Need by and Promised Date. To display DD-MON-YYYY please could some advise.
    Thanks

    The varaibles and prarameters I am using are.
    <xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format" xmlns:ora="http://www.oracle.com/XSL/Transform/java/" xmlns:xdofo="http://xmlns.oracle.com/oxp/fo/extensions" xmlns:xdoxslt="http://www.oracle.com/XSL/Transform/java/oracle.apps.xdo.template.rtf.XSLTFunctions" xmlns:xdoxliff="urn:oasis:names:tc:xliff:document:1.1">
    <xsl:param name="_XDOCALENDAR">GREGORIAN</xsl:param>
    <xsl:param name="_XDOLOCALE">en-US</xsl:param>
    <xsl:param name="_XDOTIMEZONE">GMT</xsl:param>
    <xsl:param name="_XDODFOVERRIDE">;</xsl:param>
    <xsl:param name="_XDOCTX">#</xsl:param>
    <xsl:variable name="_XDOXSLTCTX" select="xdoxslt:set_xslt_locale($_XDOCTX, $_XDOLOCALE, $_XDOTIMEZONE, $_XDOCALENDAR, $_XDODFOVERRIDE)" />

  • API to add lines to an existing Standard Purchase Order on 11.5.8 version

    Hello All,
    Is there any API in Oracle 11.5.8 Version using which we can add a line to an existing open Standard Purchase Order.
    In 11.5.10 we can do that using Purchasind document import program, how about 11.5.8, i am not able to find one.
    Pls let me know the details, it is bit critical.
    Regards,
    Adarsh

    Yes see http://oracle-ebspro.blogspot.com/2011/12/how-to-programmatically-close-po-using.html
    Sandeep Gandhi

  • Adding Company Logo to a Standard Purchase Order

    Hi,
    I went throigh this forum and tried all the different variations that have been provided.
    With the following one,
    src="url({'${OA_MEDIA}/xxx.jpg'})", I am able to see the logo , when I preview it after I uploaded the xsl-fo file.
    I also updated the stylesheet under the Setup\Purchasing Options\Document types to use the new template that I have created for the Standard Purchase order type.
    But , the logo is still not getting printed, when I submit the Process "PO output for Communication" for a single PO.
    Am I missing a step anywhere in the process. How it is able to resolve the OA_MEDIA in the preview process, but not as part of the "PO output for Communication" Process.
    Any Help would be appreciated.
    Thanks,
    - Vasu -

    I found the other syntax in the forum
    url:{concat('$[OA_MEDIA]/',.//IMAGE_NAME)} where image_name is my xml variable. This didn't work.
    But when I hard code the name of the file as in the following syntax. It worked fine.
    url:{concat('$[OA_MEDIA]/','xxx.jpg')}
    Please let me know, where I am going wrong. This has been a really painful process to get it correct. We have spent lot of hours in resolving this.
    I would really appreciate your help.
    Thanks,
    - Vasu -

  • Add fields to Standard Purchase Order

    How can I change the standard order data definition. I need to add some fields that are not in the standard po definition.
    Must i add fields to po_headers_xml.
    But i think I also have to change the .xsd file. But how can I change them ?

    Nike,
    That is indeed the way of working but what I find strange is when you download the Standard Purchase order XSL-FO.
    You see that Oracle uses Boilerplate messages to fill up the labels on there PO
    print.
    These messages are hard coded in the procedure for generating the xml that is
    used for filling up the data of the database.
    For my customer it is useful to change the messages (labels) in the database
    and not in the template. Now why does the standard PO support this. It is build
    up with boilerplate messages ! And why can you not use these way of programming
    for your custom messages. Or will be this supported in the future?
    Maybe it is usefull to build up the part where the messages are selected in the
    PO_COMMUNICATION_PVT.POXMLGEN not hard coded but dynamicly. So you can set up
    which messages are used.Alse the part wich language the xml is generated based
    upon the language of the supplier. So that you can do View > Document in PO
    summary screen with the language of the supplier.
    These are the problems I have, it seems logical to me that the way the standard
    PO is presented, it also can be used in customisations.
    But these customisations are not supported.

  • Migrating PO using Import Standard Purchase Orders program

    Hi All,
    When am trying to migrating auto created PO's, First i imported Requisition sucessfully and i took the newly generated DISTRIBUTION_ID for the
    imported REQ and i populated the value in REQ_DISTRIBUTION_ID column (PO_DISTRIBUTIONS_INTERFACE table) and then submited program.
    PO is imported sucessfully but the DISTRIBUTION_ID is not populated in the PO_DISTRIBUTIONS_ALL table. If any knows please help on this issuse ASAP.
    Details:
    ORACLE R12
    Version: 12.1.3
    Programs used:
    Requisition Import program
    Import Standard Purchase Orders program
    Regards,
    Siva.

    Hi Siva,
    THis forum is intended for migrating from non-Oracle to Oracle databases. Your questions looks like an EBS issue so try one of the forums that are listed under E-Business -
    Category: E-Business Suite
    https://forums.oracle.com/forums/category.jspa?categoryID=3
    or this fourm where I found a reference to the same table -
    Forum: SCM - General Discussion
    General SCM Discussion
    Regards,
    Mike

  • Import Standard Purchase Orders and matching to the invoice

    Hi Experts,
    Can we import standard purchase orders into oracle from 3rd party systems.
    And also there's a requirement to match the relevant invoice in AP to the purchase Order automatically when the PO is transferred.
    We are on 11.5.10.2
    Regards,
    Migara
    Edited by: user11337190 on May 13, 2010 1:52 AM

    Ensure you pass every  parameter for the request. As far as a know it has 16 parameters.
      fnd_request.submit_request (application 
    => 'PO',
    PROGRAM     
    => 'POXPOPDOI',
    argument1   
    =>  <Default Buyer>,
    argument2   
    =>  <Document Type>,
    argument3   
    =>  <Document SubType>,
    argument4   
    =>  <Create or Update Items>,
    argument5   
    =>  <Create Sourcing Rules>,
    argument6   
    =>  <Approval Status>,
    argument7   
    =>  <Release Generation Method>,
    argument8   
    =>  <Batch Id>,
    argument9   
    =>  <Operating Unit>,
    argument10  
    =>  <Global Agreement>,
    argument11  
    =>  <Enable Sourcing Level>,
    argument12  
    =>  <Sourcing Level>,
    argument13  
    =>  <Inv Org Enable>,
    argument14  
    =>  <Inventory Organization>,
    argument15  
    =>  <Batch Size>,
    argument16  
    =>  <Gather Stats>
    Regards, Andrei

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

Maybe you are looking for