Standard Purchase Order document printing

Hi All,
I need to modify the standard purchase order document and need to print a custom note in that based on the organization criteria.
i have downloaded the .xsl file and as i am not very familiar with that i cant understand the code.
1)could you please let me know, where to open that xsl file either in jdeveloper or some thing like notepad, textpad etc..
2)If possible please share the tags to print the custom message based on organization criteria
3) where to find the xml tags related to that to modify the xsl
Please help!!
Thanks!!

We need to investigate this XSL tags and need to do R&D. I finally did it.

Similar Messages

How to get Information Template fields to Standard Purchase order Document.

Hi Guy's
I Created Information Templates to capture extra information to suit our business needs. But i dont know how to get populate those information into Standard Purchase order docuemnt. After Some research I found that we have to customize the PO_STANDARD_XSLFO.xsl. But i did not get how to get those information.
If any one know knows or has done this type of customization let me know asap
Thanks in advance
Thanks & Regards
Palakondaiah.U

Hi,
I resolved this as following :
Since, i needed the Manufacturer Serial no. to be fetched in custom field at item level ( Enhanced via EEWB the item ) , the moment there is a product available in the sales doc header field.
I wrote badi implementation for definition : CRM_ORDERADM_I_BADI and utilized method : CRM_ORDERADM_I_PRODUCT_DETERM . This method's signature if you check makes me available the header, item guids along with the product available in the field even before i save the sales document. There i fetch the serial number of product from custom table and then poulate the serial no. field in customer_i extension as follows:
LS_CUSTOMER_I_COM-ZZCUSTOMER_I0803 = LV_MFR_SLNO.
LS_CUSTOMER_I_COM-REF_GUID    = IV_ITEM.
LS_CUSTOMER_I_COM-REF_HANDLE = '0000000000'.
LS_CUSTOMER_I_COM-MODE        = 'A'.
APPEND LS_CUSTOMER_I_COM TO LT_CUSTOMER_I_COM.
LS_FIELD_NAME_CUSTAB-FIELDNAME = 'ZZCUSTOMER_I0803'.
APPEND LS_FIELD_NAME_CUSTAB TO LT_FIELD_NAME_CUSTAB.
CALL FUNCTION 'CRM_CUSTOMER_I_MAINTAIN_OW'
    EXPORTING
      IS_CUSTOMER_I_COM    = LS_CUSTOMER_I_COM
*        IV_EXTERNAL_CALL     = 'X'
    CHANGING
      CT_INPUT_FIELD_NAMES = LT_FIELD_NAME_CUSTAB
    EXCEPTIONS
      ITEM_CHANGE_ERROR    = 1
      ITEM_CREATE_ERROR    = 2
      ERROR_OCCURRED       = 3
      OTHERS               = 4.

Logo on a Standard Purchase Order Stylesheet Inquire -- View Document

Hi
I did add "LOGO" to Standard Purchase Order Stylesheet and customized required fields.but, something weird thing is happening.
After changing the Setup to "Customized_Template" which is the new custom template in Document Types->Document type layout , I created new Purchase Order and when i opened document from Inquire -->View Document I see the PDF with the changes as implemented in custom template but i don't see the Log , the strange case is that when i copy this PO Tools-->Copy Document i will get a new PO here when i open the Inquire -->View Document i get the LOGO on the PDF document.
Not sure why LOGO is not appearing for new purchase orders created, could you let me know how i can troubleshoot this?
thanks
praveen

1. You don't create a new data definition. You create a new template and assign the seeded data definition to it. (XML Publisher Administrator).
2. On our version of the EBS there is a parameter on the PO Output for Communication concurrent request which lets you specify the template to use. However for the normal day to day use you need to do the setup in Purchasing:
Setup / Organizations / Purchasing Options / Control TAB / set 'PO Output Format' = 'PDF'
setup / purchasing / document types / select "Standard Purchase Order" / Set the Document Type Layout to your new template.
For the white paper on this see metalink doc id 387670.1 - Incidentally, when checking this I note that appendix C tells you how to change the logo in the XSL-FO template so that may give you a shortcut to your new PO Template. I haven't tried it though!
Cheers,
Dave

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

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

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

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.

Standard Purchase Order Stylesheet PO_STANDARD_XSLFO

Just wondering how to call the Standard Purchase Order Stylesheet PO_STANDARD_XSLFO in the purchasing module from a concurrent request?
There is the Printed Purchase Order Report Concurrent request, but I can't quite figure out run this request that uses the above PO_STANDARD_XSLFO.
Has anyone done this already? What is the output format of the concurrent request? Is it XML?
What is the short name of the concurrent request? Does it have to match the short name of the data definition? How does it all work?

PO output for communication concurrent program uses PO_STANDARD_XSLFO.
It is a java concurrent program that builds the xml and sends the PDF document to the supplier. Refer to Note 364177.1 on how to run the PO Output for Communication program and generate the XML.
Thanks,
Swetha

Purchase Order Text Print ?

Hi
I have created 7 Purchase order Document Types copying Standard(NB).
when i go into print preview of Standard. i could see all the texts entered at header level.
However when i go to print preview of the newly created ones i cant see the texts maintained at header level .
Do i need to link the New purchase order document types to the text field. please help me on this .

Hello Archie,
Goto IMG->Materials Management->Purchasing->Messages->Text for Messages->Define Texts for Prchase Orders
Configure here for all the new document types you have created as per standard one.
I think this will help you.
Rgds,
S.Balaji.

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

How to change the standard purchase order ???

Hi,
i am trying to change the output form of standard purchase order.for that i copied the standard script/form to my own created script/smart form.i modified it as per user requirement and i have given the same name in NACE>EF>output type>NEU>processing routine..in place of the standard one.and i have also activated the standard program i.e. SAPFM06P.but when i am going to me22n and print preview the previous form format is coming...
if i will create my own smartform then it is difficult for mapping all the fields to me22n...user can not input other fields in me21n if i am giving my print program name in NACE...
can anybody please help me...????
pls reply soon,....
Regards
Amayika

Hi,
Are you sure you have set it for medium 1 (print output) and specify the program, FORM routine, and the Form/Script correctly?
Another reason is the output type is not set up yet at the PO. Go to ME22N and click Messages button (next to Print preview button) and check whether your output type is already there. If it is not, then create one.
Please also check that you have copy client the form/script from development client to test client (SAPScript need this but no need for Smartform) using T-Code SCC1. And the config is configured properly in test client.
Regards,
Teddy

BOM in standard PURCHASE order/requisition

I would like to use BOM as a specification of a "group" of materials procured many times in the same or similar configuration.(eg. servers with specific configuration listing all parts).
Is it possible, to use material BOM in standard purchase order (NEITHER SUBCONTRACTING NOR PRODUCTION ORDERS) as a kind of "recipe" for eg. server configuration.
What I would like to achive is to reduce ammount of work in document entry. Instead of entering 30-50 position for each purchase requisition/order, I would like to use for this material BOM.
Is it possible?
If not, what other object can serve for preparing a list of materials to procure?
How the buttons "BOM Explosion" and "Components" can be turned on on standard purchase order/requisition?
Thanks in advance for help.
Best regards,
Wojciech

Hi,
To the best of my knowledge - BOM's are used in the context of value addition say - a manufacturing or processing involved in converting the inputs to the final prodcut.
While configurable items are used in a scenario where in a simple putting together / packaging in to a kit kind of activity is involved.In this scenario the final product is packaged to the requirements from picking the items of choice from the available prodcut list.
As it seemed the requirement as indicated in the question are in line with this concept I had suggested this solution of usage of Configurable materials.
I have not come accross a scenario of BOM and BOM explosion in Procurement excepet for Sub contracting.
How ever , I appreciate if any one can share information on BOM & Explosion in Purchase order.
Hope this information helps.
Thanks & regards
Raghuramam

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)" />

Standard Purchase Order document printing

Similar Messages

Maybe you are looking for