STANDARD PURCHASE ORDER에 대한 ARCHIVE DATA 읽는법

제품 : MFG_PO
작성날짜 : 2005-11-08
STANDARD PURCHASE ORDER에 대한 ARCHIVE DATA 읽는법
==================================================
PURPOSE
Standard Purchase Order에 대한 archive data 읽는법을 알고 이를 issue
해결에 사용할 수 있다.
(R11 ~ R11i)
Explanation
Standard PO no 125가 생성되고, 이 PO는 하나의 line,shipment,distribution
을 가지고 있다고 가정한다.
User가 이 PO를 approve 했고 status는 'Approved' 상태라고 가정한다.
또한 Standard PO document type이 'Archive on Approve'로 setting 되어 있
다고 가정한다.
아래는 Tables에서 data가 어떻게 보이는지를 보여준다...
PO_HEADERS_ALL:
PO_HEADER_ID SEGMENT1 REVISION_NUM
888 125 0
PO_HEADERS_ARCHIVE_ALL:
PO_HEADER_ID REVISION_NUM LATEST_EXTERNAL_FLAG
888 0 Y
PO_LINES_ARCHIVE_ALL:
PO_HEADER_ID PO_LINE_ID LINE_NUM REVISION_NUM LATEST_EXTERNAL_FLAG
888 777 1 0 Y
PO_LINE_LOCATIONS_ARCHIVE_ALL:
PO_LINE_LOCATION_ID PO_LINE_ID LINE_NUM REVISION_NUM LATEST_EXTERNAL_FLAG
555 777 1 0 Y
PO_DISTRIBUTIONS_ARCHIVE_ALL:
PO_DIST.ID PO_HEADER_ID PO_LINE_ID LINE_NUM REVISION_NUM LATEST_EXTERNAL_FLAG
222 888 777 1 0 Y
이때 PO에 새로운 line을 추가하고 approve를 한다.
관련된 tables의 변화를 볼 수 있다.
PO_HEADERS_ALL:
PO_HEADER_ID SEGMENT1 REVISION_NUM
888 125 1 <- because we added a line
PO_HEADERS_ARCHIVE_ALL:
PO_HEADER_ID REVISION_NUM LATEST_EXTERNAL_FLAG
888 0 N
888 1 Y <-- latest rev on the header is now 1
PO_LINES_ARCHIVE_ALL:
PO_HEADER_ID PO_LINE_ID LINE_NUM REVISION_NUM LATEST_EXTERNAL_FLAG
888 777 1 0 Y <--note line 1 didn't change
888 778 2 1 Y <--note line 2 was created in rev 1
PO_LINE_LOCATIONS_ARCHIVE_ALL :
PO_LINE_LOCATION_ID PO_LINE_ID LINE_NUM REVISION_NUM LATEST_EXTERNAL_FLAG
555 777 1 0 Y
556 778 2 1 Y <--note line 2 was inserted
PO_DISTRIBUTIONS_ARCHIVE_ALL:
PO_DIST.ID PO_HEADER_ID PO_LINE_ID LINE_NUM REVISION_NUM LATEST_EXTERNAL_FLAG
222 888 777 1 0 Y
223 888 778 2 1 Y <--note line 2 was inserted
PO header만 변경 후 approve를 한다.
PO_HEADERS_ALL과 PO_HEADERS_ARCHIVE_ALL tables 만 유일하게 영향을 받을 것이다.
PO_HEADERS_ALL:
PO_HEADER_ID SEGMENT1 REVISION_NUM
888 125 2
PO_HEADERS_ARCHIVE_ALL:
PO_HEADER_ID REVISION_NUM LATEST_EXTERNAL_FLAG
888 0 N
888 1 N
888 2 Y
Line1의 수량을 변경한다. shipment나 distribution은 변경하지 않는다.
PO_HEADERS_ALL:
PO_HEADER_ID SEGMENT1 REVISION_NUM
888 125 3
PO_HEADERS_ARCHIVE_ALL:
PO_HEADER_ID REVISION_NUM LATEST_EXTERNAL_FLAG
888 0 N
888 1 N
888 2 N
888 3 Y
PO_LINES_ARCHIVE_ALL:
PO_HEADER_ID PO_LINE_ID LINE_NUM REVISION_NUM LATEST_EXTERNAL_FLAG
888 777 1 0 N <---latest ext flag
change to N
888 777 1 3 Y <--this row inserted rev num matches header revision in which change was made.
Lower rev for this line had latest external flag changed to N.
888 778 2 1 Y <--no changes
All other tables do not change.
PO line에 세번째 line을 추가 후 다시 approve를 한다.
PO_HEADERS_ALL:
PO_HEADER_ID SEGMENT1 REVISION_NUM
888 125 4
PO_HEADERS_ARCHIVE_ALL:
PO_HEADER_ID REVISION_NUM LATEST_EXTERNAL_FLAG
888 0 N
888 1 N
888 2 N
888 3 N
888 4 Y
PO_LINES_ARCHIVE_ALL:
PO_HEADER_ID PO_LINE_ID LINE_NUM REVISION_NUM LATEST_EXTERNAL_FLAG
888 777 1 0 N <---didn't change
888 777 1 3 Y <---didn't change
888 778 2 1 Y <---didn't change
888 779 3 4 Y <--line 3 added to lines archive.
PO_LINE_LOCATIONS_ARCHIVE_ALL:
PO_LINE_LOCATION_ID PO_LINE_ID LINE_NUM REVISION_NUM LATEST_EXTERNAL_FLAG
555 777 1 0 Y
556 778 2 1 Y
557 779 3 4 Y<--line 3 added to archive.
PO_DISTRIBUTIONS_ARCHIVE_ALL:
PO_DIST.ID PO_HEADER_ID PO_LINE_ID LINE_NUM REVISION_NUM LATEST_EXTERNAL_FLAG
222 888 777 1 0 Y
223 888 778 2 1 Y
224 888 779 3 4 Y<--line 3 added to archive.
마지막 test로 2번째 line의 distribution 정보를 변경 후 PO를 다시 approve한다.
PO_HEADERS_ALL:
PO_HEADER_ID SEGMENT1 REVISION_NUM
888 125 5
PO_HEADERS_ARCHIVE_ALL:
PO_HEADER_ID REVISION_NUM LATEST_EXTERNAL_FLAG
888 0 N
888 1 N
888 2 N
888 3 N
888 4 N
888 5 Y
PO_LINES_ARCHIVE_ALL:
PO_HEADER_ID PO_LINE_ID LINE_NUM REVISION_NUM LATEST_EXTERNAL_FLAG
888 777 1 0 N <---didn't change
888 777 1 3 Y <---didn't change
888 778 2 1 N <--latest ext flag when to N
888 778 2 5 .Y <--row inserted & latest ext flag set to Y
888 779 3 4 Y <---didn't change
PO_DISTRIBUTIONS_ARCHIVE_ALL:
PO_DIST.ID PO_HEADER_ID PO_LINE_ID LINE_NUM REVISION_NUM
LATEST_EXTERNAL_FLAG
222 888 777 1 0 Y
223 888 778 2 1 N <--latest ext flag set to N
223 888 778 2 5 Y
224 888 779 3 4 Y
Reference Documents
Note 251537.1

the error might be that you are just executing programs and you dont know the correct chain.
Better you do archiving always from SARA transaction
there you enter the object MM_EKKO and hit enter.
You get a button for each step.
first you usually have a preprocessing step which sets the deletion indicators
next step is the write step. you always have to check the log and the spool file to be certain that you had written records to an archive. A bigger archiving step may write several archives depending on the customizing of file size.
In the delete step you have to select from against which archive you want delete the records from the table.
SAP checks then if the archive can be read and deletes the corresponding tables entries in EKKO and EKPO and all other related tables.
Depending on customizing the Delete step can be an automatic executed step when the write job has finished, and does not need to be executed manually.
after the deletion you usually store the archive somewhere.
The administer button can give you info about the archive run and files that were created and the status.

Similar Messages

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

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

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 Data Source question

Hi,
I have read the documentation discussing how to create data definitions. They all say make sure that the code is the short name of the concurrent request. However I noticed when I look at the Standard Purchase Order Data Source's code it has is PO_STANDARD_PO which seems to match the XML Schema PO_STANDARD_PO.xsd how is the concurrent request initiated at runtime?
Thanks,
Mark

If you go to the XML administrator screen and lookup the definition of the XML page and what program it is associated to as a start. From memory, i believe that the Definition of the Print PO concurrent job is where the output is required in order for the PO to be printed in the XML format.

Import Standard Purchase Order not picking data when submitted from backend

Hi,
As part of my code, I am inserting Purchase order information in the interface tables with process_code = 'PENDING'. Then using fnd_request , i am triggering the Standard Program for importing these Purchase Orders. The standard program is getting triggered and completing normally. But it is not picking any records. I am calling the program as follows:-
              -- Setting the org_id so that the import program will run for that particular org_id.
              fnd_request.set_org_id(r_org_id.org_id);
               -- Submit the Import Standard Purchase Orders by calling the standard program for respective org_id
              l_req_id := FND_REQUEST.SUBMIT_REQUEST(application => 'PO'
                            ,program      => 'POXPOPDOI'
                            ,description => 'Import Standard Purchase Orders'
                            ,start_time => SYSDATE
                            ,sub_request => FALSE
                            ,argument1 => NULL
                            ,argument2 => 'STANDARD'
                            ,argument3 => NULL
                            ,argument4    => 'N'
                            ,argument5    => NULL
                            ,argument6 => 'APPROVED'
                            ,argument7 => NULL
                            ,argument8 => NULL
                            ,argument9 => NULL
                            ,argument10 => NULL
              COMMIT;
When I am submitting this same program from front end, for the same set of records using the same set of parameters, the records are getting picked.
Any suggestions for this?

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

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

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

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.

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

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.

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

Modify and add new field in standard Purchase Order script

Hi All,
I have some problem with Modify and add some new fields in Standard Purchase Order script. From ME22n transaction code it display PO detail. In item detail with condition tab all data will display in Currently PO script output.
But I want to display ME22n->Item Detail->Invoice->Taxes Data. how to display this data in standard PO script. All data are fetch from Structure like ( KOMV,KOMVD..etc) then How it can be Display?
Waiting for Replay.
Himanshu Patel.

Work with an Abaper.Tell your requirement [ addition of a field] and ask him to include this field by using the functionality " Field Exit".

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

STANDARD PURCHASE ORDER에 대한 ARCHIVE DATA 읽는법

Similar Messages

Maybe you are looking for