PO 가 IN PROCESS 상태이고, 해당 PO의 WF_ITEM_TYPE 또는 WF_ITEM_KEY 이 존재하지않는 경우의 처리 방안

제품 : MFG_PO
작성날짜 : 2004-05-24
PO 가 IN PROCESS 상태이고, 해당 PO의 WF_ITEM_TYPE 또는 WF_ITEM_KEY이 존재하지
않는 경우의 처리 방안.
============================================================================
PURPOSE
In Process 상태의 PO의 Data fix 방안.
Problem Description
어떠한 원인(Data corruption 및 Workflow purge)에 의하여 In Process 상태의
PO의 wf_item_type 또는 wf_item_key 이 삭제 되었을 경우 PO Data fix 방안.
Workaround
N/A
Solution Description
Inprocess 상태인 PO 의 wf_item_type 또는 wf_item_key 이 삭제되거나,
존재하지 않으면, PO 는 더 이상 진행되지 않는다. 이 경우 하기의 스크
립트를 이용하여 PO 의 상태를 Requires Reapproval 상태로 만들고,
Re-submit Approval 하여 PO를 처리한다.
1) 관련 data를 backup 한다.
2) PO_HEADER_ID 를 parameter 로하여 아래의 sql을 수행한다.
SQL> Update PO_HEADERS_ALL
Set AUTHORIZATION_STATUS = 'REQUIRES REAPPROVAL',
APPROVED_FLAG = 'R'
Where PO_HEADER_ID = &PO_HEADER_ID;
3) 정상 완료되었으면, commit 한다.
Reference Documents
Note 198595.1 - POXPOEPO - PO in Process Status Has No wf_item_type or
wf_item_key in Workflow

Similar Messages

SYSTEM FAILURE로 PO STAUTS가 INPROCESS 상태시 해결방법

제품 : MFG_PO
작성날짜 : 2006-05-17
SYSTEM FAILURE로 PO STAUTS가 'INPROCESS' 상태시 해결방법
========================================================
PURPOSE
Document approval manager가 fails 되어 down 되면 PO는 IN PROCESS 상태가
된다.이 PO에 대한 available한 workflow가 없고,reprocess 하기 위해
wfretry를 시도해도 실패한다면 아래 script를 이용한다.
(Oracle Purchasing - Version: 11.5.9)
Explanation
Document approval시 발생하는 Document Approval Manager crashing은 PO의상태를 IN PROCESS로 만드는 원인이 된다.
Workflow는 완전히 처리되지 못하고 workflow activities processes와
system 안에서 "lost" 상태가 된다.
이 때 wf_item_key는 어떤 active한 workflow와도 상응하지 못하기 때문에
불필요한 상태가 되어 버린다.
System crash로 인해 session variable data를 잃어버렸기 때문에 wfretry
를 실행해도 workflow는 restart 되지 못한다.
Solution :
아래 steps에 따라 작업한다.
NOTE: 이 script는 oracle의 승인 및 review 없이 사용할 수 없으며, 예산
계정을 사용하는 경우 사용할 수 없다.
1. Please run the following sql update:
-- START OF RESET SCRIPT
set serveroutput on size 100000
DECLARE
CURSOR potoreset is
SELECT wf_item_type, wf_item_key, po_header_id, segment1,
revision_num, type_lookup_code
FROM po_headers_all
WHERE segment1 = '&PO_NUMBER '
and authorization_status IN ('IN PROCESS', 'PRE-APPROVED')
and NVL(cancel_flag, 'N') = 'N'
and NVL(closed_code, 'OPEN') != 'FINALLY_CLOSED';
CURSOR maxseq(id number, subtype po_action_history.object_sub_type_code%type) is
SELECT nvl(max(sequence_num), 0)
FROM po_action_history
WHERE object_type_code IN ('PO', 'PA')
AND object_sub_type_code = subtype
AND object_id = id
AND action_code is NULL;
CURSOR poaction(id number, subtype po_action_history.object_sub_type_code%type) is
SELECT nvl(max(sequence_num), 0)
FROM po_action_history
WHERE object_type_code IN ('PO', 'PA')
AND object_sub_type_code = subtype
AND object_id = id
AND action_code = 'SUBMIT';
submitseq po_action_history.sequence_num%type;
nullseq po_action_history.sequence_num%type;
BEGIN
dbms_output.put_line('------------------------------------');
dbms_output.put_line('Data Manipulation Scripts Disclaimer');
dbms_output.put_line('------------------------------------');
dbms_output.put_line('As always please ask customer to run the scripts on their test instance first ');
dbms_output.put_line('before applying it on production. Make sure the data is validated for ');
dbms_output.put_line('correctness and related functionality is verified after the script has been');
dbms_output.put_line('run on a test instance. Customer is responsible to authenticate and verify ');
dbms_output.put_line('correctness of data manipulation scripts.');
FOR pos in potoreset LOOP
dbms_output.put_line('Processing '||pos.type_lookup_code||' PO Number: '||pos.segment1);
dbms_output.put_line('......................................');
dbms_output.put_line('Closing Notifications...');
BEGIN
UPDATE wf_notifications set status = 'CANCELED'
WHERE notification_id in (
select ias.notification_id
from wf_item_activity_statuses ias,
wf_notifications ntf
where ias.item_type = pos.wf_item_type
and ias.item_key = pos.wf_item_key
and ntf.notification_id = ias.notification_id)
AND NVL(status, 'OPEN') = 'OPEN';
EXCEPTION
WHEN OTHERS THEN
null;
END;
dbms_output.put_line('Aborting Workflow...');
BEGIN
WF_Engine.AbortProcess(pos.wf_item_type, pos.wf_item_key);
EXCEPTION
WHEN OTHERS THEN
null;
END;
dbms_output.put_line('Updating PO Status...');
UPDATE po_headers_all
set authorization_status = decode(pos.revision_num, 0, 'INCOMPLETE','REQUIRES REAPPROVAL'),
wf_item_type = NULL,
wf_item_key = NULL,
approved_flag = decode(pos.revision_num, 0, 'N', 'R')
where po_header_id = pos.po_header_id;
OPEN maxseq(pos.po_header_id, pos.type_lookup_code);
FETCH maxseq into nullseq;
CLOSE maxseq;
OPEN poaction(pos.po_header_id, pos.type_lookup_code);
FETCH poaction into submitseq;
CLOSE poaction;
IF nullseq > submitseq THEN
dbms_output.put_line('Deleting PO Action History...');
DELETE FROM po_action_history
WHERE object_id = pos.po_header_id
AND object_type_code IN ('PO', 'PA')
AND object_sub_type_code = pos.type_lookup_code
AND sequence_num >= submitseq;
END IF;
dbms_output.put_line('Done Processing.');
dbms_output.put_line('................');
dbms_output.put_line('Please issue commit, if no errors found.');
END LOOP;
END;
-- END OF RESET SCRIPT
2. If the above sql update completes without error the please issue a
commit:
commit;
If the above sql update errors then issue a rollback:
rollback;
3. When the above sql updates are complete, then query up the purchase
order in theEnter Purchase Order form and resubmit the document for
approval.
Reference Documents
Note 297980.1

PO, PR 의 승인을 위한 NOTIFICATION 이 발송되지 않았거나 삭제된 경우 NOTIFICATION 메일의 재발송 방법

제품 : MFG_PO
작성날짜 : 2004-11-29
PO, PR 의 승인을 위한 NOTIFICATION 이 발송되지 않았거나 삭제된 경우 NOTIFICATION 메일의 재발송 방법
=======================================================================
PURPOSE
Purchase/Requisition Approval Notification 메일의 재발송 방법.
Explanation
Notification 은 메일로 보내져도 Notifications Summary window 에서 조회
가 가능하며, Notification 메일이 삭제되면 Notifications Summary window
에서 처리할 수있다.
또한, PO/PR approval workflow 는 초기 Notification 에 응답이 없을 경우
remainder notifications 기능이 있다.
참조 : Purchasing Setup, Automatically Forward Notifications When Users
Do Not Respond.
만약, Notification 이 누락되었을 경우, employee 에 대한 user 의 중복
assignment, 중복 Login 를 확인한다.
참조 : Purchasing Template: Documents Stuck In Process.
상기와 같은 경우 email notification 을 재발송할 수있다.
1) Purchasing Document 의 WF item key and item type 을 확인한다.
SQL>
SELECT
wf_item_type,
wf_item_key
FROM po_headers_all
WHERE segment1=&po_number;
sQL>
SELECT
wf_item_type,
wf_item_key
FROM po_requisition_headers_all
WHERE segment1=&pr_number;
2) 발송할 Notification ID 확인 :
SQL>
SELECT
wf.notification_id nid,
wf.status,
wf.mail_status,
wf.begin_date,
wf.end_date,
substr(wf.from_user,1,25) from_user,
substr(wf.to_user,1,25) to_user,
substr(wf.subject,1,80) subject
FROM
wf_notifications wf,
wf_item_activity_statuses wias
WHERE
wias.item_type = '&item_type'
and wias.item_key = '&item_key'
and wias.notification_id = WF.NOTIFICATION_ID
and wias.activity_status = 'NOTIFIED'
order by wf.begin_date desc
Notification ID 는 notification subject 에 있는 Document number 를 사용
할수 있다.
SQL>
SELECT
wf.notification_id nid,
wf.status,
wf.mail_status,
wf.begin_date,
wf.end_date,
substr(wf.from_user,1,25) from_user,
substr(wf.to_user,1,25) to_user,
substr(wf.subject,1,80) subject
FROM
wf_notifications wf
WHERE
subject like '%&document_number%'
order by wf.begin_date desc
3) 발송할 Notification 을 Update :
SQL>
UPDATE wf_notifications
SET status ='OPEN',
mail_status ='MAIL',
end_date = NULL
WHERE notification_id= &NID
Notification Mailer 가 상기 Notification 을 메일로 발송한다.
Example
Reference Documents
Note 255209.1 - How To Resend Last Purchase/Requisition Approval
Notification In Case It Was Deleted Or Lost

Oracle WorkFlow, help me, please

Hi,
I don't familiar with Oracle Workflow , I want to use it, in fact I build up the Oracle WorKFlow using WorkFlow
Builder but I don't know how to link the workflow process with the aplication.
Can any one tell me How to execute this work flow
regards
Marma Teresa

Hello Maria,
There are two parts to your question; First, if you want to see how Workflow works in the application a good idea would be to test for example; a Purchasing Workflow. If you have Purchasing do the following: (I'm not sure how your setup is for the apps. so I'll include all steps).
1) Create yourself as a user in the Core applications: (R) System Adminstrator - (N) User/
Define
2) Give yourself the following responsiblities: a) System Adminstrator
b) Purchasing
c) Workflow Adminstrator Web Applications
3) Create a Purchase order in Purchasing - do not approve the PO
4) Open a SQL session and run the following script:
SQL> select segment1, wf_item_type, wf_item_key,po_header_id
from po_headers_all
where segment1 = <PO Number>;
This script will give you the the name of the workflow that got called: wf_item_type and
the unique instance of the definition that got called: wf_item_key.
5) Choose the Workflow Adminstrator Web Applications responsibility and choose Find Process
from the menu
6) In the Item key field enter the value from the SQL script (wf_item_key) - click on Find
7) In the next form chose the View Diagram button - this will launch the Workflow Monitor, it
will allow you view the present state of the definition - the green line indicates
the 'path'Workflow has taken and the color also indicates that everything is ok.
8) Go back into Purchasing and Approve the PO
9) Follow steps 5,6 and 7 - to see the 'continued flow' of the Workflow.
The second part to your question, if you have created a Workflow you have two options;
1) To actually 'call' the Workflow you created, you will have to save your definition to the
database. Chose the Launch Process menu, find your definition. The in the next form, enter
the data for your attributes...then click ok. This will launch your workflow.
Unfortunately, I do not know what your definition looks like so may encounter some errors.
But the Launch Process allows you 'test' the Workflow you created.
2) If you want to 'include' your definition in the Core Applications that might require a
customization. In brief, when users are in the application, depending on what they are
doing, the form will call workflow. If you want the application to call your definition you
will have to cutomize the call the form makes. But, certain modules in the application
do allow you to modify Oracle's definition and call your new process - Oracle Purchasing
is one of those modules.
I hope this information helps. If you need more infomation let me know: [email protected]
Thanks,
Karen

Config Oracle Alert to send mail

Hi everyone !
I want to setup Event Alert to send mail use Unix sendmail in our project.
My Apps is 9.5.10.2 CU2, i have never applied to Rollup4.( Rollup 4 send mail with WF)
If i want system to sent a message from [email protected] to [email protected], i configed sendmail package successfull. What do i do next step ?
Further, In Page 9.3 of Oracle Alert User's Guide, at Setp 2, How to create Mail System Administrator?
Regard !
Edited by: whoami! on Nov 20, 2009 6:19 PM

I config Alert on other table and see issue following: in only Alert but when 8 row updated then create 8 requests, and auto perform 8 actions to sends 8 same mail.But i want only system to send 1 mail .
Can you help me !
Detail:
When I create 1 PO,i want system to send 1 mail to superior to approval, i use SQL:
=====================
select
created_by,
last_updated_by,
rowid,
authorization_status,
LAST_UPDATE_LOGIN,
approved_flag,
wf_item_type,
wf_item_key,
xml_flag,
submit_date
into
&cby,
&last_updated_by,
&rowid,
&auth_status,
&LAST_UPDATE_LOGIN,
&approved_flag,
&wf_item_type,
&wf_item_key,
&xml_flag,
&submit_date
from po_headers_all
where
(last_updated_by=1147
and created_by=1147
and upper(authorization_status)='IN PROCESS'
and LAST_UPDATE_LOGIN = -1
and approved_flag is not null
and wf_item_type is not null
and wf_item_key is not null
and xml_flag is not null
and submit_date is not null
and rowid=:rowid)
===================
Thanks for advance !

PO XML For Loop

Hi
In PO RTF Template I am trying to display short text and long text for each PO. But I am unable to display multiple short and long texts for each line number. I can only display the first short and long text for each line number. How to display all. The Seeded PO template does that. here is my code and XML
for short text(short_text is in the same column as line_num is the RTF table)
<?for-each:LINES_ROW?><?sort:LINE_NUM;'ascending';data-type='number'?>
<?LINE_NUM?> <?format-date:NEED_BY_DATE;'DD-MMM-YYYY'?> <?LINE_AMOUNT?>
<?ITEM_DESCRIPTION?>
<?SHORT_TEXT?>
<?end for-each?>
output is
Line num 1
test for short attachment
Line num 2
short text 1
output should be
Line num 1
test for short attachment
4t attachment
Line num 2
short text 1
short text 2
for Long text
<?if: PO_DATA/LINE_ATTACHMENTS/TEXT !=''?>
<?for-each:LINES_ROW?><?sort:LINE_NUM;'ascending';data-type='number'?>
<?if:LINE_NUM!=''?> <?concat('Line Number ',LINE_NUM)?> <?end if?>
<?variable@incontext:PoLnID;'PO_LINE_ID'?>
<?/PO_DATA/LINE_ATTACHMENTS/ID[child::text()=$PoLnID]/preceding-sibling::TEXT[1]?>
<?end for-each?>
<?end if?>
output is
Line num 1
long text attachment which is 2nd ote
Line num 2
long text 1
output should be
Line num 1
long text attachment which is 2nd ote
see this 5th long attachment
Line num 2
long text 1
long text 2
here is the sample XML
<?xml version="1.0" encoding="UTF-8"?>
<PO_DATA>
<TYPE_LOOKUP_CODE>STANDARD</TYPE_LOOKUP_CODE>
<SEGMENT1>24687</SEGMENT1>
<REVISION_NUM>0</REVISION_NUM>
<PRINT_COUNT>3</PRINT_COUNT>
<CREATION_DATE>29-APR-2009 14:28:52</CREATION_DATE>
<NOTE_TO_VENDOR>this is a test po to supplier in terms window</NOTE_TO_VENDOR>
<DOCUMENT_BUYER_FIRST_NAME>Sanjay</DOCUMENT_BUYER_FIRST_NAME>
<DOCUMENT_BUYER_LAST_NAME>Kumar</DOCUMENT_BUYER_LAST_NAME>
<DOCUMENT_BUYER_AGENT_ID>8756</DOCUMENT_BUYER_AGENT_ID>
<CANCEL_FLAG>N</CANCEL_FLAG>
<CONFIRMING_ORDER_FLAG>N</CONFIRMING_ORDER_FLAG>
<ACCEPTANCE_REQUIRED_FLAG>N</ACCEPTANCE_REQUIRED_FLAG>
<CURRENCY_CODE>USD</CURRENCY_CODE>
<CURRENCY_NAME>US dollar</CURRENCY_NAME>
<PAYMENT_TERMS>NET 30</PAYMENT_TERMS>
<CUSTOMER_NUM>1244</CUSTOMER_NUM>
<VENDOR_NUM>RR10</VENDOR_NUM>
<VENDOR_NAME>OFFICE DEPOT</VENDOR_NAME>
<VENDOR_ADDRESS_LINE1>PO BOX 31533</VENDOR_ADDRESS_LINE1>
<VENDOR_CITY>HARTFORD</VENDOR_CITY>
<VENDOR_STATE>CT</VENDOR_STATE>
<VENDOR_POSTAL_CODE>06150-1533</VENDOR_POSTAL_CODE>
<SHIP_TO_LOCATION_ID>88</SHIP_TO_LOCATION_ID>
<SHIP_TO_LOCATION_NAME>US CORPORATE HDQTRS</SHIP_TO_LOCATION_NAME>
<SHIP_TO_ADDRESS_LINE1>123 JFK RD</SHIP_TO_ADDRESS_LINE1>
<SHIP_TO_ADDRESS_INFO>Broadway, WA 02421</SHIP_TO_ADDRESS_INFO>
<SHIP_TO_COUNTRY>United States</SHIP_TO_COUNTRY>
<BILL_TO_LOCATION_ID>88</BILL_TO_LOCATION_ID>
<BILL_TO_LOCATION_NAME>US CORPORATE HDQTRS</BILL_TO_LOCATION_NAME>
<BILL_TO_ADDRESS_LINE1>123 JFK RD</BILL_TO_ADDRESS_LINE1>
<BILL_TO_ADDRESS_INFO>Broadway, WA 02421</BILL_TO_ADDRESS_INFO>
<BILL_TO_COUNTRY>United States</BILL_TO_COUNTRY>
<ATTRIBUTE1>MA</ATTRIBUTE1>
<VENDOR_SITE_ID>9983</VENDOR_SITE_ID>
<PO_HEADER_ID>27162</PO_HEADER_ID>
<APPROVED_FLAG>N</APPROVED_FLAG>
<VENDOR_ID>826</VENDOR_ID>
<ORG_ID>29</ORG_ID>
<COMMENTS>Test PO to test template</COMMENTS>
<FIRM_STATUS_LOOKUP_CODE>N</FIRM_STATUS_LOOKUP_CODE>
<FROZEN_FLAG>N</FROZEN_FLAG>
<CREATED_BY>3349</CREATED_BY>
<TERMS_ID>10001</TERMS_ID>
<RATE_DATE>29-APR-2009 00:00:00</RATE_DATE>
<AUTHORIZATION_STATUS>N</AUTHORIZATION_STATUS>
<NOTE_TO_RECEIVER>this is a test po to receiver in terms window</NOTE_TO_RECEIVER>
<LAST_UPDATE_DATE>29-APR-2009 14:30:52</LAST_UPDATE_DATE>
<LAST_UPDATED_BY>3349</LAST_UPDATED_BY>
<SUMMARY_FLAG>N</SUMMARY_FLAG>
<ENABLED_FLAG>Y</ENABLED_FLAG>
<LAST_UPDATE_LOGIN>1250381</LAST_UPDATE_LOGIN>
<SUPPLY_AGREEMENT_FLAG>N</SUPPLY_AGREEMENT_FLAG>
<PENDING_SIGNATURE_FLAG>N</PENDING_SIGNATURE_FLAG>
<OU_NAME>ABC LTD</OU_NAME>
<OU_ADDR1>123 JFK RD</OU_ADDR1>
<OU_TOWN_CITY>Broadway</OU_TOWN_CITY>
<OU_REGION2>WA</OU_REGION2>
<OU_POSTALCODE>44421</OU_POSTALCODE>
<OU_COUNTRY>United States</OU_COUNTRY>
<BUYER_ADDRESS_LINE1>123 JFK RD</BUYER_ADDRESS_LINE1>
<BUYER_CITY_STATE_ZIP>Broadway, WA 44421</BUYER_CITY_STATE_ZIP>
<BUYER_CONTACT_PHONE>322-445-4533</BUYER_CONTACT_PHONE>
<TOTAL_AMOUNT>6,000.00</TOTAL_AMOUNT>
<BUYER_COUNTRY>United States</BUYER_COUNTRY>
<DOCUMENT_CREATION_METHOD>ENTER_PO</DOCUMENT_CREATION_METHOD>
<DOCUMENT_TYPE>Standard Purchase Order</DOCUMENT_TYPE>
<COVER_MESSAGE>This document has important legal consequences. </COVER_MESSAGE>
<AMMENDMENT_MESSAGE>This document has important legal consequences.
</AMMENDMENT_MESSAGE>
<TEST_FLAG>D</TEST_FLAG>
<DIST_SHIPMENT_COUNT>1</DIST_SHIPMENT_COUNT>
<DOCUMENT_NAME>Standard Purchase Order 24687, 0</DOCUMENT_NAME>
<SIGNED>F</SIGNED>
<AMENDMENT_PROFILE>Y</AMENDMENT_PROFILE>
<WITH_TERMS>N</WITH_TERMS>
<IS_ATTACHED_DOC>Y</IS_ATTACHED_DOC>
<MESSAGE>
<MESSAGE_ROW>
<MESSAGE>PO_FO_AGREEMENT_CANCELED</MESSAGE>
<TEXT>This agreement CANCELED on</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_WF_NOTIF_VENDOR_NO</MESSAGE>
<TEXT>Supplier No.</TEXT>
</MESSAGE_ROW>
</MESSAGE>
<HEADER_SHORT_TEXT>
</HEADER_SHORT_TEXT>
<LINES>
<LINES_ROW>
<LINE_NUM>1</LINE_NUM>
<ITEM_DESCRIPTION>test po</ITEM_DESCRIPTION>
<CANCEL_FLAG>N</CANCEL_FLAG>
<NOTE_TO_VENDOR>This is a test PO. do not ship.</NOTE_TO_VENDOR>
<UNIT_MEAS_LOOKUP_CODE>Unit</UNIT_MEAS_LOOKUP_CODE>
<ORDER_TYPE_LOOKUP_CODE>QUANTITY</ORDER_TYPE_LOOKUP_CODE>
<ATTRIBUTE1>N</ATTRIBUTE1>
<UNIT_PRICE>5000</UNIT_PRICE>
<QUANTITY>1</QUANTITY>
<PO_HEADER_ID>27162</PO_HEADER_ID>
<PO_LINE_ID>53995</PO_LINE_ID>
<ORG_ID>29</ORG_ID>
<UNORDERED_FLAG>N</UNORDERED_FLAG>
<CLOSED_FLAG>N</CLOSED_FLAG>
<TAXABLE_FLAG>N</TAXABLE_FLAG>
<CAPITAL_EXPENSE_FLAG>N</CAPITAL_EXPENSE_FLAG>
<NEGOTIATED_BY_PREPARER_FLAG>N</NEGOTIATED_BY_PREPARER_FLAG>
<LAST_UPDATE_DATE>29-APR-2009 14:29:36</LAST_UPDATE_DATE>
<LAST_UPDATED_BY>3349</LAST_UPDATED_BY>
<LINE_TYPE_ID>1000</LINE_TYPE_ID>
<LAST_UPDATE_LOGIN>1250381</LAST_UPDATE_LOGIN>
<CREATION_DATE>29-APR-2009 14:28:52</CREATION_DATE>
<CREATED_BY>3349</CREATED_BY>
<CATEGORY_ID>224</CATEGORY_ID>
<ALLOW_PRICE_OVERRIDE_FLAG>N</ALLOW_PRICE_OVERRIDE_FLAG>
<LIST_PRICE_PER_UNIT>5000</LIST_PRICE_PER_UNIT>
<LINE_TYPE>QUANTITY</LINE_TYPE>
<PURCHASE_BASIS>GOODS</PURCHASE_BASIS>
<LINE_AMOUNT>5,000.00</LINE_AMOUNT>
<MANUAL_PRICE_CHANGE_FLAG>N</MANUAL_PRICE_CHANGE_FLAG>
<MATCHING_BASIS>QUANTITY</MATCHING_BASIS>
<PRICE_DIFF>
</PRICE_DIFF>
*<LINE_SHORT_TEXT>*
*<LINE_SHORT_TEXT_ROW>*
*<PO_LINE_ID>53995</PO_LINE_ID>*
*<SHORT_TEXT>test for short attachement</SHORT_TEXT>*
*</LINE_SHORT_TEXT_ROW>*
*<LINE_SHORT_TEXT_ROW>*
*<PO_LINE_ID>53995</PO_LINE_ID>*
*<SHORT_TEXT>4th attachment</SHORT_TEXT>*
*</LINE_SHORT_TEXT_ROW>*
*</LINE_SHORT_TEXT>*
<LINE_LOCATIONS>
<LINE_LOCATIONS_ROW>
<SHIPMENT_NUM>1</SHIPMENT_NUM>
<DUE_DATE>15-MAY-2009 00:00:00</DUE_DATE>
<QUANTITY>1</QUANTITY>
<PRICE_OVERRIDE>5000</PRICE_OVERRIDE>
<QUANTITY_CANCELLED>0</QUANTITY_CANCELLED>
<CANCEL_FLAG>N</CANCEL_FLAG>
<TAXABLE_FLAG>N</TAXABLE_FLAG>
<PO_HEADER_ID>27162</PO_HEADER_ID>
<PO_LINE_ID>53995</PO_LINE_ID>
<LINE_LOCATION_ID>53678</LINE_LOCATION_ID>
<SHIPMENT_TYPE>STANDARD</SHIPMENT_TYPE>
<RECEIVING_ROUTING_ID>3</RECEIVING_ROUTING_ID>
<ACCRUE_ON_RECEIPT_FLAG>N</ACCRUE_ON_RECEIPT_FLAG>
<ORG_ID>29</ORG_ID>
<RECEIPT_REQUIRED_FLAG>N</RECEIPT_REQUIRED_FLAG>
<QTY_RCV_TOLERANCE>10</QTY_RCV_TOLERANCE>
<QTY_RCV_EXCEPTION_CODE>WARNING</QTY_RCV_EXCEPTION_CODE>
<ENFORCE_SHIP_TO_LOCATION_CODE>NONE</ENFORCE_SHIP_TO_LOCATION_CODE>
<ALLOW_SUBSTITUTE_RECEIPTS_FLAG>N</ALLOW_SUBSTITUTE_RECEIPTS_FLAG>
<DAYS_EARLY_RECEIPT_ALLOWED>5</DAYS_EARLY_RECEIPT_ALLOWED>
<DAYS_LATE_RECEIPT_ALLOWED>5</DAYS_LATE_RECEIPT_ALLOWED>
<RECEIPT_DAYS_EXCEPTION_CODE>WARNING</RECEIPT_DAYS_EXCEPTION_CODE>
<INVOICE_CLOSE_TOLERANCE>2</INVOICE_CLOSE_TOLERANCE>
<RECEIVE_CLOSE_TOLERANCE>100</RECEIVE_CLOSE_TOLERANCE>
<SHIP_TO_ORGANIZATION_ID>208</SHIP_TO_ORGANIZATION_ID>
<CLOSED_CODE>OPEN</CLOSED_CODE>
<LAST_ACCEPT_DATE>09-MAY-2009 00:00:00</LAST_ACCEPT_DATE>
<ENCUMBERED_FLAG>N</ENCUMBERED_FLAG>
<FIRM_STATUS_LOOKUP_CODE>N</FIRM_STATUS_LOOKUP_CODE>
<LAST_UPDATE_DATE>29-APR-2009 14:31:31</LAST_UPDATE_DATE>
<LAST_UPDATED_BY>3349</LAST_UPDATED_BY>
<LAST_UPDATE_LOGIN>1250381</LAST_UPDATE_LOGIN>
<CREATION_DATE>29-APR-2009 14:28:53</CREATION_DATE>
<CREATED_BY>3349</CREATED_BY>
<QUANTITY_RECEIVED>0</QUANTITY_RECEIVED>
<QUANTITY_ACCEPTED>0</QUANTITY_ACCEPTED>
<QUANTITY_REJECTED>0</QUANTITY_REJECTED>
<QUANTITY_BILLED>0</QUANTITY_BILLED>
<UNIT_MEAS_LOOKUP_CODE>Unit</UNIT_MEAS_LOOKUP_CODE>
<TAX_USER_OVERRIDE_FLAG>N</TAX_USER_OVERRIDE_FLAG>
<MATCH_OPTION>P</MATCH_OPTION>
<CALCULATE_TAX_FLAG>Y</CALCULATE_TAX_FLAG>
<NOTE_TO_RECEIVER>this is a note in shipments receiver</NOTE_TO_RECEIVER>
<AMOUNT>5,000.00</AMOUNT>
<SHIP_TO_LOCATION_ID>88</SHIP_TO_LOCATION_ID>
<SHIP_TO_LOCATION_NAME>US CORPORATE HDQTRS</SHIP_TO_LOCATION_NAME>
<SHIP_TO_ADDRESS_LINE1>123 JFK RD</SHIP_TO_ADDRESS_LINE1>
<SHIP_TO_ADDRESS_INFO>Broadway, WA 02421</SHIP_TO_ADDRESS_INFO>
<SHIP_TO_COUNTRY>United States</SHIP_TO_COUNTRY>
<NEED_BY_DATE>15-MAY-2009 00:00:00</NEED_BY_DATE>
<PROMISED_DATE>04-MAY-2009 00:00:00</PROMISED_DATE>
<LINE_LOC_SHORT_TEXT>
</LINE_LOC_SHORT_TEXT>
<DISTRIBUTIONS>
<DISTRIBUTIONS_ROW>
<DISTRIBUTION_TYPE>STANDARD</DISTRIBUTION_TYPE>
<ACCRUE_ON_RECEIPT_FLAG>N</ACCRUE_ON_RECEIPT_FLAG>
<ORG_ID>29</ORG_ID>
<DESTINATION_TYPE_CODE>EXPENSE</DESTINATION_TYPE_CODE>
<DESTINATION_ORGANIZATION_ID>208</DESTINATION_ORGANIZATION_ID>
<ACCRUAL_ACCOUNT_ID>1037</ACCRUAL_ACCOUNT_ID>
<VARIANCE_ACCOUNT_ID>22148</VARIANCE_ACCOUNT_ID>
<PREVENT_ENCUMBRANCE_FLAG>N</PREVENT_ENCUMBRANCE_FLAG>
<PO_DISTRIBUTION_ID>55228</PO_DISTRIBUTION_ID>
<LAST_UPDATE_DATE>29-APR-2009 14:32:23</LAST_UPDATE_DATE>
<LAST_UPDATED_BY>3349</LAST_UPDATED_BY>
<PO_HEADER_ID>27162</PO_HEADER_ID>
<PO_LINE_ID>53995</PO_LINE_ID>
<LINE_LOCATION_ID>53678</LINE_LOCATION_ID>
<SET_OF_BOOKS_ID>25</SET_OF_BOOKS_ID>
<CODE_COMBINATION_ID>22148</CODE_COMBINATION_ID>
<QUANTITY_ORDERED>1</QUANTITY_ORDERED>
<LAST_UPDATE_LOGIN>1250381</LAST_UPDATE_LOGIN>
<CREATION_DATE>29-APR-2009 14:28:54</CREATION_DATE>
<CREATED_BY>3349</CREATED_BY>
<QUANTITY_DELIVERED>0</QUANTITY_DELIVERED>
<QUANTITY_BILLED>0</QUANTITY_BILLED>
<QUANTITY_CANCELLED>0</QUANTITY_CANCELLED>
<DELIVER_TO_LOCATION_ID>89</DELIVER_TO_LOCATION_ID>
<DELIVER_TO_PERSON_ID>5324</DELIVER_TO_PERSON_ID>
<RATE_DATE>29-APR-2009 00:00:00</RATE_DATE>
<ENCUMBERED_FLAG>N</ENCUMBERED_FLAG>
<RECOVERY_RATE>0.00</RECOVERY_RATE>
<TAX_RECOVERY_OVERRIDE_FLAG>N</TAX_RECOVERY_OVERRIDE_FLAG>
<DESTINATION_CONTEXT>EXPENSE</DESTINATION_CONTEXT>
<DISTRIBUTION_NUM>1</DISTRIBUTION_NUM>
<CHARGE_ACCOUNT>05-3002-7050-000-000</CHARGE_ACCOUNT>
<FULL_NAME>Devine, Alison</FULL_NAME>
<EMAIL_ADDRESS>[email protected]</EMAIL_ADDRESS>
<REQUESTER_DELIVER_FIRST_NAME>Karen</REQUESTER_DELIVER_FIRST_NAME>
<REQUESTER_DELIVER_LAST_NAME>MA</REQUESTER_DELIVER_LAST_NAME>
</DISTRIBUTIONS_ROW>
</DISTRIBUTIONS>
</LINE_LOCATIONS_ROW>
</LINE_LOCATIONS>
</LINES_ROW>
<LINES_ROW>
<LINE_NUM>2</LINE_NUM>
<ITEM_DESCRIPTION>TEST PO</ITEM_DESCRIPTION>
<CANCEL_FLAG>N</CANCEL_FLAG>
<UNIT_MEAS_LOOKUP_CODE>Unit</UNIT_MEAS_LOOKUP_CODE>
<ORDER_TYPE_LOOKUP_CODE>QUANTITY</ORDER_TYPE_LOOKUP_CODE>
<ATTRIBUTE1>N</ATTRIBUTE1>
<UNIT_PRICE>1000</UNIT_PRICE>
<QUANTITY>1</QUANTITY>
<PO_HEADER_ID>27162</PO_HEADER_ID>
<PO_LINE_ID>54015</PO_LINE_ID>
<ORG_ID>29</ORG_ID>
<UNORDERED_FLAG>N</UNORDERED_FLAG>
<CLOSED_FLAG>N</CLOSED_FLAG>
<TAXABLE_FLAG>N</TAXABLE_FLAG>
<CAPITAL_EXPENSE_FLAG>N</CAPITAL_EXPENSE_FLAG>
<NEGOTIATED_BY_PREPARER_FLAG>N</NEGOTIATED_BY_PREPARER_FLAG>
<LAST_UPDATE_DATE>30-APR-2009 13:52:26</LAST_UPDATE_DATE>
<LAST_UPDATED_BY>3349</LAST_UPDATED_BY>
<LINE_TYPE_ID>1000</LINE_TYPE_ID>
<LAST_UPDATE_LOGIN>1251236</LAST_UPDATE_LOGIN>
<CREATION_DATE>30-APR-2009 13:52:26</CREATION_DATE>
<CREATED_BY>3349</CREATED_BY>
<CATEGORY_ID>224</CATEGORY_ID>
<ALLOW_PRICE_OVERRIDE_FLAG>N</ALLOW_PRICE_OVERRIDE_FLAG>
<LIST_PRICE_PER_UNIT>1000</LIST_PRICE_PER_UNIT>
<LINE_TYPE>QUANTITY</LINE_TYPE>
<PURCHASE_BASIS>GOODS</PURCHASE_BASIS>
<LINE_AMOUNT>1,000.00</LINE_AMOUNT>
<MANUAL_PRICE_CHANGE_FLAG>N</MANUAL_PRICE_CHANGE_FLAG>
<MATCHING_BASIS>QUANTITY</MATCHING_BASIS>
<PRICE_DIFF>
</PRICE_DIFF>
*<LINE_SHORT_TEXT>*
*<LINE_SHORT_TEXT_ROW>*
*<PO_LINE_ID>54015</PO_LINE_ID>*
*<SHORT_TEXT>short text 1</SHORT_TEXT>*
*</LINE_SHORT_TEXT_ROW>*
*<LINE_SHORT_TEXT_ROW>*
*<PO_LINE_ID>54015</PO_LINE_ID>*
*<SHORT_TEXT>short text 2</SHORT_TEXT>*
*</LINE_SHORT_TEXT_ROW>*
*</LINE_SHORT_TEXT>*
<LINE_LOCATIONS>
<LINE_LOCATIONS_ROW>
<SHIPMENT_NUM>1</SHIPMENT_NUM>
<DUE_DATE>07-MAY-2009 00:00:00</DUE_DATE>
<QUANTITY>1</QUANTITY>
<PRICE_OVERRIDE>1000</PRICE_OVERRIDE>
<QUANTITY_CANCELLED>0</QUANTITY_CANCELLED>
<CANCEL_FLAG>N</CANCEL_FLAG>
<TAXABLE_FLAG>N</TAXABLE_FLAG>
<PO_HEADER_ID>27162</PO_HEADER_ID>
<PO_LINE_ID>54015</PO_LINE_ID>
<LINE_LOCATION_ID>53698</LINE_LOCATION_ID>
<SHIPMENT_TYPE>STANDARD</SHIPMENT_TYPE>
<RECEIVING_ROUTING_ID>3</RECEIVING_ROUTING_ID>
<ACCRUE_ON_RECEIPT_FLAG>N</ACCRUE_ON_RECEIPT_FLAG>
<ORG_ID>29</ORG_ID>
<RECEIPT_REQUIRED_FLAG>N</RECEIPT_REQUIRED_FLAG>
<QTY_RCV_TOLERANCE>10</QTY_RCV_TOLERANCE>
<QTY_RCV_EXCEPTION_CODE>WARNING</QTY_RCV_EXCEPTION_CODE>
<ENFORCE_SHIP_TO_LOCATION_CODE>NONE</ENFORCE_SHIP_TO_LOCATION_CODE>
<ALLOW_SUBSTITUTE_RECEIPTS_FLAG>N</ALLOW_SUBSTITUTE_RECEIPTS_FLAG>
<DAYS_EARLY_RECEIPT_ALLOWED>5</DAYS_EARLY_RECEIPT_ALLOWED>
<DAYS_LATE_RECEIPT_ALLOWED>5</DAYS_LATE_RECEIPT_ALLOWED>
<RECEIPT_DAYS_EXCEPTION_CODE>WARNING</RECEIPT_DAYS_EXCEPTION_CODE>
<INVOICE_CLOSE_TOLERANCE>2</INVOICE_CLOSE_TOLERANCE>
<RECEIVE_CLOSE_TOLERANCE>100</RECEIVE_CLOSE_TOLERANCE>
<SHIP_TO_ORGANIZATION_ID>208</SHIP_TO_ORGANIZATION_ID>
<CLOSED_CODE>OPEN</CLOSED_CODE>
<LAST_ACCEPT_DATE>11-MAY-2009 00:00:00</LAST_ACCEPT_DATE>
<ENCUMBERED_FLAG>N</ENCUMBERED_FLAG>
<FIRM_STATUS_LOOKUP_CODE>N</FIRM_STATUS_LOOKUP_CODE>
<LAST_UPDATE_DATE>30-APR-2009 13:53:11</LAST_UPDATE_DATE>
<LAST_UPDATED_BY>3349</LAST_UPDATED_BY>
<LAST_UPDATE_LOGIN>1251236</LAST_UPDATE_LOGIN>
<CREATION_DATE>30-APR-2009 13:52:27</CREATION_DATE>
<CREATED_BY>3349</CREATED_BY>
<QUANTITY_RECEIVED>0</QUANTITY_RECEIVED>
<QUANTITY_ACCEPTED>0</QUANTITY_ACCEPTED>
<QUANTITY_REJECTED>0</QUANTITY_REJECTED>
<QUANTITY_BILLED>0</QUANTITY_BILLED>
<UNIT_MEAS_LOOKUP_CODE>Unit</UNIT_MEAS_LOOKUP_CODE>
<TAX_USER_OVERRIDE_FLAG>N</TAX_USER_OVERRIDE_FLAG>
<MATCH_OPTION>P</MATCH_OPTION>
<CALCULATE_TAX_FLAG>Y</CALCULATE_TAX_FLAG>
<NOTE_TO_RECEIVER>NOT FOR RECEIVER IN shipme</NOTE_TO_RECEIVER>
<AMOUNT>1,000.00</AMOUNT>
<SHIP_TO_LOCATION_ID>88</SHIP_TO_LOCATION_ID>
<SHIP_TO_LOCATION_NAME>US HDQTRS</SHIP_TO_LOCATION_NAME>
<SHIP_TO_ADDRESS_LINE1>123 JFK RD</SHIP_TO_ADDRESS_LINE1>
<SHIP_TO_ADDRESS_INFO>Broadway, WA 53411</SHIP_TO_ADDRESS_INFO>
<SHIP_TO_COUNTRY>United States</SHIP_TO_COUNTRY>
<NEED_BY_DATE>07-MAY-2009 00:00:00</NEED_BY_DATE>
<PROMISED_DATE>06-MAY-2009 00:00:00</PROMISED_DATE>
<LINE_LOC_SHORT_TEXT>
</LINE_LOC_SHORT_TEXT>
<DISTRIBUTIONS>
<DISTRIBUTIONS_ROW>
<DISTRIBUTION_TYPE>STANDARD</DISTRIBUTION_TYPE>
<ACCRUE_ON_RECEIPT_FLAG>N</ACCRUE_ON_RECEIPT_FLAG>
<ORG_ID>29</ORG_ID>
<DESTINATION_TYPE_CODE>EXPENSE</DESTINATION_TYPE_CODE>
<DESTINATION_ORGANIZATION_ID>208</DESTINATION_ORGANIZATION_ID>
<ACCRUAL_ACCOUNT_ID>1037</ACCRUAL_ACCOUNT_ID>
<VARIANCE_ACCOUNT_ID>3908</VARIANCE_ACCOUNT_ID>
<PREVENT_ENCUMBRANCE_FLAG>N</PREVENT_ENCUMBRANCE_FLAG>
<PO_DISTRIBUTION_ID>55248</PO_DISTRIBUTION_ID>
<LAST_UPDATE_DATE>30-APR-2009 13:53:11</LAST_UPDATE_DATE>
<LAST_UPDATED_BY>3349</LAST_UPDATED_BY>
<PO_HEADER_ID>27162</PO_HEADER_ID>
<PO_LINE_ID>54015</PO_LINE_ID>
<LINE_LOCATION_ID>53698</LINE_LOCATION_ID>
<SET_OF_BOOKS_ID>25</SET_OF_BOOKS_ID>
<CODE_COMBINATION_ID>3908</CODE_COMBINATION_ID>
<QUANTITY_ORDERED>1</QUANTITY_ORDERED>
<LAST_UPDATE_LOGIN>1251236</LAST_UPDATE_LOGIN>
<CREATION_DATE>30-APR-2009 13:53:11</CREATION_DATE>
<CREATED_BY>3349</CREATED_BY>
<QUANTITY_DELIVERED>0</QUANTITY_DELIVERED>
<QUANTITY_BILLED>0</QUANTITY_BILLED>
<QUANTITY_CANCELLED>0</QUANTITY_CANCELLED>
<DELIVER_TO_LOCATION_ID>89</DELIVER_TO_LOCATION_ID>
<DELIVER_TO_PERSON_ID>1308</DELIVER_TO_PERSON_ID>
<RATE_DATE>29-APR-2009 00:00:00</RATE_DATE>
<ENCUMBERED_FLAG>N</ENCUMBERED_FLAG>
<RECOVERY_RATE>0.00</RECOVERY_RATE>
<TAX_RECOVERY_OVERRIDE_FLAG>N</TAX_RECOVERY_OVERRIDE_FLAG>
<DESTINATION_CONTEXT>EXPENSE</DESTINATION_CONTEXT>
<DISTRIBUTION_NUM>1</DISTRIBUTION_NUM>
<CHARGE_ACCOUNT>01-3001-7050-000-000</CHARGE_ACCOUNT>
<FULL_NAME>Green, Jan</FULL_NAME>
<EMAIL_ADDRESS>[email protected]</EMAIL_ADDRESS>
<REQUESTER_DELIVER_FIRST_NAME>Jan</REQUESTER_DELIVER_FIRST_NAME>
<REQUESTER_DELIVER_LAST_NAME>Green</REQUESTER_DELIVER_LAST_NAME>
</DISTRIBUTIONS_ROW>
</DISTRIBUTIONS>
</LINE_LOCATIONS_ROW>
</LINE_LOCATIONS>
</LINES_ROW>
</LINES>
*<LINE_ATTACHMENTS>*
*<TEXT>long text attachment which is 2nd note.</TEXT>*
*<ID>53995</ID>*
*<TEXT>see this 5th long atta</TEXT>*
*<ID>53995</ID>*
*<TEXT>long text 1</TEXT>*
*<ID>54015</ID>*
*<TEXT>long text 2</TEXT>*
*<ID>54015</ID>*
*</LINE_ATTACHMENTS>*
<ADDRESS_DETAILS>
<ADDRESS_DETAILS_ROW>
<LOCATION_ID>88</LOCATION_ID>
<ADDRESS_STYLE>US_GLB</ADDRESS_STYLE>
<ADDR_LABEL_1>Address Line1</ADDR_LABEL_1>
<ADDR_LABEL_2>Address Line2</ADDR_LABEL_2>
<ADDR_LABEL_3>Address Line3</ADDR_LABEL_3>
<ADDR_LABEL_4>City</ADDR_LABEL_4>
<ADDR_LABEL_5>County</ADDR_LABEL_5>
<ADDR_LABEL_6>State</ADDR_LABEL_6>
<ADDR_LABEL_7>Zip Code</ADDR_LABEL_7>
<ADDR_LABEL_8>Country</ADDR_LABEL_8>
<ADDR_LABEL_9>Telephone</ADDR_LABEL_9>
<ADDR_LABEL_10>Fax</ADDR_LABEL_10>
<ADDR_LABEL_11>Sales Tax Override</ADDR_LABEL_11>
<ADDR_LABEL_12>Inside City Limits</ADDR_LABEL_12>
<ADDR_DATA_1>123 JFK RD</ADDR_DATA_1>
<ADDR_DATA_4>Broadway</ADDR_DATA_4>
<ADDR_DATA_6>WA</ADDR_DATA_6>
<ADDR_DATA_7>33444</ADDR_DATA_7>
<ADDR_DATA_8>US</ADDR_DATA_8>
<ADDR_DATA_9>322-588-4534</ADDR_DATA_9>
</ADDRESS_DETAILS_ROW>
</ADDRESS_DETAILS>
</PO_DATA>

Hi,
I have used PO_COMMUNICATION_PVT.POXMLGEN procedure and got the CLOB as output. When i am reading and printing in FND_FILE.OUTPUT. Tags are getting shifted to next line. How to print the this XML output as concurrent programs ouput in Oracle apps 11.5.10. It would be really great if anybody can share his experience.
See the sample file:
<?xml version="1.0" encoding="UTF-16"?>
<PO_DATA>
<TYPE_LOOKUP_CODE>STANDARD</TYPE_LOOKUP_CODE>
<SEGMENT1>87710004999</SEGMENT1>
<REVISION_NUM>0</REVISION_NUM>
<PRINT_COUNT>1</PRINT_COUNT>
<CREATION_DATE>28-OCT-2008 21:53:15</CREATION_DATE>
<PRINTED
DATE>28-OCT-08</PRINTEDDATE>
<DOCUMENT_BUYER_FIRST_NAME>Annapoorani</DOCUMENT_BUYER_FIRST_NAME>
<DOCUMENT_BUYER_LAST_NAME>Krishnan</DOCUMENT_BUYER_LAST_NAME>
<DOCUMENT_BUYER_AGENT_ID>251578</DOCUMENT_BUYER_AGENT_ID>
<CONFIRMING_ORDER_FLAG>N</CONFIRM
ING_ORDER_FLAG>
<ACCEPTANCE_REQUIRED_FLAG>N</ACCEPTANCE_REQUIRED_FLAG>
<CURRENCY_CODE>USD</CURRENCY_CODE>
<CURRENCY_NAME>US Dollar</CURRENCY_NAME>
<PAYMENT_TERMS>42 Net</PAYMENT_TERMS>
<VENDOR_NUM>AMER-30954</VENDOR_NUM>
<VENDOR_NAME>CISCO SYSTEMS -
RESALE</VENDOR_NAME>
<VENDOR_ADDRESS_LINE1>PO BOX 91232</VENDOR_ADDRESS_LINE1>
<VENDOR_CITY>CHICAGO</VENDOR_CITY>
<VENDOR_STATE>IL</VENDOR_STATE>
<VENDOR_POSTAL_CODE>60693-1232</VENDOR_POSTAL_CODE>
<VENDOR_COUNTRY>United States</VENDOR_COUNTRY>
<VE
NDOR_PHONE>661-7606</VENDOR_PHONE>
<SHIP_TO_LOCATION_ID>67670</SHIP_TO_LOCATION_ID>
<SHIP_TO_LOCATION_NAME>GFP_877_LOC</SHIP_TO_LOCATION_NAME>
<SHIP_TO_ADDRESS_LINE1>BT Americas Inc.|11440 Commerce Park Drive|Reston, VA 20191</SHIP_TO_ADDRESS_LINE1>
<
SHIP_TO_ADDRESS_INFO> </SHIP_TO_ADDRESS_INFO>
<BILL_TO_LOCATION_ID>67644</BILL_TO_LOCATION_ID>
<BILL_TO_LOCATION_NAME>GFP_877_BILL_TO_LOC</BILL_TO_LOCATION_NAME>
<BILL_TO_ADDRESS_LINE1>Invoice To:</BILL_TO_ADDRESS_LINE1>
<BILL_TO_ADDRESS_LINE2>BT AME
RICAS ACCOUNTS PAYABLE</BILL_TO_ADDRESS_LINE2>
<BILL_TO_ADDRESS_LINE3>PO Box 696025</BILL_TO_ADDRESS_LINE3>
<BILL_TO_ADDRESS_INFO>SAN ANTONIO, TX 78269</BILL_TO_ADDRESS_INFO>
<BILL_TO_COUNTRY>United States</BILL_TO_COUNTRY>
<VENDOR_SITE_ID>27591</VEN
DOR_SITE_ID>
<PO_HEADER_ID>103843</PO_HEADER_ID>
<APPROVED_FLAG>Y</APPROVED_FLAG>
<VENDOR_ID>97015</VENDOR_ID>
<CLOSED_CODE>CLOSED</CLOSED_CODE>
<ORG_ID>52605</ORG_ID>
<CLOSED_DATE>18-NOV-2008 22:25:27</CLOSED_DATE>
<FIRM_STATUS_LOOKUP_CODE>N</FIRM
STATUSLOOKUP_CODE>
<FROZEN_FLAG>N</FROZEN_FLAG>
<CREATED_BY>64914</CREATED_BY>
<TERMS_ID>10084</TERMS_ID>
<RATE_DATE>28-OCT-2008 00:00:00</RATE_DATE>
<AUTHORIZATION_STATUS>APPROVED</AUTHORIZATION_STATUS>
<APPROVED_DATE>28-OCT-2008 21:53:35</APPROV
ED_DATE>
<LAST_UPDATE_DATE>18-NOV-2008 22:25:27</LAST_UPDATE_DATE>
<LAST_UPDATED_BY>73951</LAST_UPDATED_BY>
<SUMMARY_FLAG>N</SUMMARY_FLAG>
<ENABLED_FLAG>Y</ENABLED_FLAG>
<LAST_UPDATE_LOGIN>-1</LAST_UPDATE_LOGIN>
<WF_ITEM_TYPE>POAPPRV</WF_ITEM_TYPE>
<WF_ITEM_KEY>103843-491416</WF_ITEM_KEY>
<XML_FLAG>N</XML_FLAG>
<CONTERMS_EXIST_FLAG>Y</CONTERMS_EXIST_FLAG>
<CONTERMS_ARTICLES_UPD_DATE>28-OCT-2008 21:53:16</CONTERMS_ARTICLES_UPD_DATE>
<PENDING_SIGNATURE_FLAG>N</PENDING_SIGNATURE_FLAG>
<OU_NAME>US
_877_OU</OU_NAME>
<OU_ADDR1>BT Americas Inc.|11440 Commerce Park Drive|Reston, VA 20191</OU_ADDR1>
<BUYER_ADDRESS_LINE1>Invoice To:</BUYER_ADDRESS_LINE1>
<BUYER_ADDRESS_LINE2>BT AMERICAS ACCOUNTS PAYABLE</BUYER_ADDRESS_LINE2>
<BUYER_ADDRESS_LINE3>PO B
ox 696025</BUYER_ADDRESS_LINE3>
<BUYER_CITY_STATE_ZIP>SAN ANTONIO, TX 78269</BUYER_CITY_STATE_ZIP>
<BUYER_CONTACT_PHONE>+914442674662</BUYER_CONTACT_PHONE>
<BUYER_CONTACT_EMAIL>[email protected]</BUYER_CONTACT_EMAIL>
<VENDOR_FAX>216-5724</V
ENDOR_FAX>
<TOTAL_AMOUNT>1,326.00</TOTAL_AMOUNT>
<BUYER_COUNTRY>United States</BUYER_COUNTRY>
<VENDOR_AREA_CODE>309</VENDOR_AREA_CODE>
<DOCUMENT_CREATION_METHOD>AUTOCREATE</DOCUMENT_CREATION_METHOD>
<DOCUMENT_TYPE>Standard Purchase Order</DOCUMENT_TY
PE>
<COVER_MESSAGE>This document has important legal consequences. The information contained in this document is proprietary of US_877_LE. It shall not be used, reproduced, or disclosed to others without the express and written consent of US_877_LE.
Thi
s agreement between US_877_LE and CISCO SYSTEMS - RESALE is authorized for binding commitment. The parties hereto have read and executed this agreement as of the
_______________ day of ______________, ___________.</COVER_MESSAGE>
<AMMENDMENT_MESSAGE>Thi
s Amendment supersedes the Agreement 87710004999 and all its prior modifications. This agreement can only be changed by a signed agreement between the affected parties.
The parties hereto have read and executed this contract modification as of the
___________ day of ______________, _________.
</AMMENDMENT_MESSAGE>
<TEST_FLAG>N</TEST_FLAG>
<DIST_SHIPMENT_COUNT>1</DIST_SHIPMENT_COUNT>
<DOCUMENT_NAME>Standard Purchase Order 87710004999, 0</DOCUMENT_NAME>
<SIGNED>F</SIGNED>
<AMENDMENT_PROFILE>Y</A
MENDMENT_PROFILE>
<WITH_TERMS>Y</WITH_TERMS>
<IS_ATTACHED_DOC>N</IS_ATTACHED_DOC>
<MESSAGE>
<MESSAGE_ROW>
<MESSAGE>PO_FO_AGREEMENT_CANCELED</MESSAGE>
<TEXT>This agreement CANCELED on</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_AMO
UNT_AGREED</MESSAGE>
<TEXT>Amount Agreed</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_AMOUNT_CANCELED</MESSAGE>
<TEXT>Amount CANCELED:</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_BILL_TO</MESSAGE>
<TEXT>Bill To:</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_CHARGE_ACCOUNT</MESSAGE>
<TEXT>Charge Account:</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_COMPANY</MESSAGE>
<TEXT>Company</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_CON
FIRM_NOT_DUPLICATE</MESSAGE>
<TEXT>CONFIRMATION - DO NOT DUPLICATE</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_CONTACT_NAME</MESSAGE>
<TEXT>Contact</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_CONTRACTOR</MESSAGE>
<TEXT
Contractor Details:</TEXT></MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_CONTRACTOR_NAME</MESSAGE>
<TEXT>Contractor Name:</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_CUSTOMER_ACCOUNT_NO</MESSAGE>
<TEXT>Customer Account No.</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_CUST_ITEM_DESC</MESSAGE>
<TEXT>Customer Item Description:</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_CUST_PO_NUMBER</MESSAGE>
<TEXT>Customer PO Number:</TEXT>
</MESSAGE_ROW>
<MES
SAGE_ROW>
<MESSAGE>PO_FO_DATE</MESSAGE>
<TEXT>Date:</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_DELIVER_DATE_TIME</MESSAGE>
<TEXT>Delivery Date/Time</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_DELIVER_TO_LOCATION</MESS
AGE>
<TEXT>Deliver To:</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_DRAFT</MESSAGE>
<TEXT>DRAFT</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_EFFECTIVE_END_DATE</MESSAGE>
<TEXT>Effective End Date</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_EFFECTIVE_START_DATE</MESSAGE>
<TEXT>Effective Start Date</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_EMAIL</MESSAGE>
<TEXT>Email</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_END_DATE</MESS
AGE>
<TEXT>End Date:</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_FAX</MESSAGE>
<TEXT>Fax</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_FORMAL_ACCEPT</MESSAGE>
<TEXT>Please formally accept this order by</TEXT>
</MESSAGE
_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_HAZARD_CLASS</MESSAGE>
<TEXT>Hazard Class:</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_LINE_CANCELED</MESSAGE>
<TEXT>This line CANCELED on</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_F
O_LINE_NUMBER</MESSAGE>
<TEXT>Line number:</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_LINE_REF_BPA</MESSAGE>
<TEXT>This line references Blanket Agreement</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_LINE_REF_CONTRACT</MES
SAGE>
<TEXT>This line references Contract Agreement</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_LINE_SUPPLIER_QUOTATION</MESSAGE>
<TEXT>This line references Supplier Quotation</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_N
AME</MESSAGE>
<TEXT>Name:</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_NO</MESSAGE>
<TEXT>No:</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_NOTES</MESSAGE>
<TEXT>Notes:</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>
PO_FO_ORG_AGR_ASS</MESSAGE>
<TEXT>Organization Agreement Assignments</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_ORIGINAL_AMOUNT_ORDERED</MESSAGE>
<TEXT>Original amount ordered:</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO
ORIGINALQTY_ORDERED</MESSAGE>
<TEXT>Original quantity ordered:</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_ORIGINAL_SHIPMENT_QTY</MESSAGE>
<TEXT>Original shipment quantity:</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_PA
CKING_INSTRUCTION</MESSAGE>
<TEXT>Packing Instructions:</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_PAGE</MESSAGE>
<TEXT>Page &PAGE_NUM of &END_PAGE</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_PO_CANCELED</MESSAGE
>
<TEXT>This purchase order CANCELED on</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_PRICES_EXPRESSED</MESSAGE>
<TEXT>All prices and amounts on this order are expressed in</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_PRICE_
BREAK</MESSAGE>
<TEXT>Price Break:</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_PRICE_DIFFERENTIALS</MESSAGE>
<TEXT>Price Differentials:</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_PROPRIETARY_INFORMATION</MESSAGE>
<TEX
T>Proprietary and Confidential</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_PURCHASING_ORGANIZATION</MESSAGE>
<TEXT>Purchasing Organization</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_PURCHASING_SUPPLIER_SITE</MESSAGE>
<TE
XT>Purchasing Supplier Site</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_QUANTITY_CANCELED</MESSAGE>
<TEXT>Quantity CANCELED:</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_RELEASE_CANCELED</MESSAGE>
<TEXT>This release CANCEL
ED on</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_REVISED_BY</MESSAGE>
<TEXT>Revised By</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_REVISION</MESSAGE>
<TEXT>Revision</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_
FO_REVISION_DATE</MESSAGE>
<TEXT>Revision Date</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_SHIFT_PATTERN</MESSAGE>
<TEXT>Shift Pattern:</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_SHIPMENT_CANCELED</MESSAGE>
<TEXT>This
shipment CANCELED on</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_SHIPPING_INSTRUCTION</MESSAGE>
<TEXT>Shipping Instructions:</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_SHIP_METHOD</MESSAGE>
<TEXT>Ship Method:</TEXT>
<
/MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_SHIP_NUMBER</MESSAGE>
<TEXT>Shipment number:</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_SHIP_TO</MESSAGE>
<TEXT>Ship To:</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_START_D
ATE</MESSAGE>
<TEXT>Start Date:</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_SUBMIT_RESPONSE</MESSAGE>
<TEXT>Please submit your response to:</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_SUPPLIER_CONFIGURATION</MESSAGE>
<
TEXT>Supplier Configuration ID:</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_SUPPLIER_ITEM</MESSAGE>
<TEXT>Supplier Item:</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_TELEPHONE</MESSAGE>
<TEXT>Telephone</TEXT>
</MESSAGE_R
OW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_TEST</MESSAGE>
<TEXT>Test Purchase Order</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_TITLE</MESSAGE>
<TEXT>Title:</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_TOTAL</MESSAGE>
<TEXT>
Total:</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_TRANSPORTATION_ARRANGED</MESSAGE>
<TEXT>Transportation</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_TYPE</MESSAGE>
<TEXT>Type</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<M
ESSAGE>PO_FO_UN_NUMBER</MESSAGE>
<TEXT>UN Number:</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_USE_SHIP_ADDRESS_TOP</MESSAGE>
<TEXT>Use the ship-to address at the top of page</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_VEN
DOR</MESSAGE>
<TEXT>Supplier:</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_FO_WORK_SCHEDULE</MESSAGE>
<TEXT>Work Schedule:</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_WF_NOTIF_ADDRESS</MESSAGE>
<TEXT>Address</TEXT>
</MESSAG
E_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_WF_NOTIF_AMOUNT</MESSAGE>
<TEXT>Amount</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_WF_NOTIF_BUYER</MESSAGE>
<TEXT>Buyer</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_WF_NOTIF_CONFIRM_TO_TELE<
/MESSAGE>
<TEXT>Confirm To/Telephone</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_WF_NOTIF_DESCRIPTION</MESSAGE>
<TEXT>Description</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_WF_NOTIF_EFFECTIVE_DATE</MESSAGE>
<TEXT>Effective
Date</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_WF_NOTIF_EXPIRES_ON</MESSAGE>
<TEXT>Expires On</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_WF_NOTIF_FOB</MESSAGE>
<TEXT>FOB</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO
WFNOTIF_FREIGHT_TERMS</MESSAGE>
<TEXT>Freight Terms</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_WF_NOTIF_HEADER_NOTE</MESSAGE>
<TEXT>Note To Supplier</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_WF_NOTIF_LINE_NUMBER</MESSAGE>
<TEXT>Line</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_WF_NOTIF_MULTIPLE</MESSAGE>
<TEXT>Multiple</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_WF_NOTIF_NEEDBY_DATE</MESSAGE>
<TEXT>Needed:</TEXT>
</MESSAGE_ROW>
<MESSAGE_RO
W>
<MESSAGE>PO_WF_NOTIF_NOTE</MESSAGE>
<TEXT>Justification</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_WF_NOTIF_ORDER</MESSAGE>
<TEXT>Order</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_WF_NOTIF_ORDER_DATE</MESSAGE>
<TEXT>O
rder Date</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_WF_NOTIF_PART_NO_DESC</MESSAGE>
<TEXT>Part Number / Description</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_WF_NOTIF_PAYMENT_TERMS</MESSAGE>
<TEXT>Payment Terms</TEXT>
</M
ESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_WF_NOTIF_PREPARER</MESSAGE>
<TEXT>Created By</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_WF_NOTIF_PROMISED_DATE</MESSAGE>
<TEXT>Promised:</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_WF
NOTIFPURCHASE_ORDER</MESSAGE>
<TEXT>Purchase Order</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_WF_NOTIF_QUANTITY</MESSAGE>
<TEXT>Quantity</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_WF_NOTIF_REQUESTER_DELIVER</MESSAGE>
<TE
XT>Requester/Deliver To</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_WF_NOTIF_REVISION</MESSAGE>
<TEXT>Revision</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_WF_NOTIF_SHIP_VIA</MESSAGE>
<TEXT>Ship Via</TEXT>
</MESSAGE_ROW>
<ME
SSAGE_ROW>
<MESSAGE>PO_WF_NOTIF_SUPPLIER_ITEM</MESSAGE>
<TEXT>Your # :</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_WF_NOTIF_TAX</MESSAGE>
<TEXT>Tax</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_WF_NOTIF_TOTAL</MESSAGE>
<TEX
T>Total</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_WF_NOTIF_UNIT_PRICE</MESSAGE>
<TEXT>Unit Price</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE>PO_WF_NOTIF_UOM</MESSAGE>
<TEXT>UOM</TEXT>
</MESSAGE_ROW>
<MESSAGE_ROW>
<MESSAGE
PO_WF_NOTIF_VENDOR_NO</MESSAGE><TEXT>Supplier No.</TEXT>
</MESSAGE_ROW>
</MESSAGE>
<HEADER_SHORT_TEXT>
</HEADER_SHORT_TEXT>
<LINES>
<LINES_ROW>
<LINE_NUM>1</LINE_NUM>
<ITEM_DESCRIPTION>HWIC-1CE1T1-PRI
</ITEM_DESCRIPTION>
<CANCEL_FLAG
N</CANCEL_FLAG><VENDOR_PRODUCT_NUM>HWIC-1CE1T1-PRI</VENDOR_PRODUCT_NUM>
<UNIT_MEAS_LOOKUP_CODE>EA</UNIT_MEAS_LOOKUP_CODE>
<ORDER_TYPE_LOOKUP_CODE>QUANTITY</ORDER_TYPE_LOOKUP_CODE>
<UNIT_PRICE>1326</UNIT_PRICE>
<QUANTITY>1</QUANTITY>
<P
O_HEADER_ID>103843</PO_HEADER_ID>
<PO_LINE_ID>170164</PO_LINE_ID>
<PRICE_TYPE_LOOKUP_CODE>VARIABLE</PRICE_TYPE_LOOKUP_CODE>
<CLOSED_CODE>CLOSED</CLOSED_CODE>
<CLOSED_DATE>18-NOV-2008 22:25:27</CLOSED_DATE>
<CLOSED_REASON>Close status rolled
up</CLOSED_REASON>
<CLOSED_BY>271332</CLOSED_BY>
<ORG_ID>52605</ORG_ID>
<QTY_RCV_TOLERANCE>10</QTY_RCV_TOLERANCE>
<OVER_TOLERANCE_ERROR_FLAG>WARNING</OVER_TOLERANCE_ERROR_FLAG>
<FIRM_STATUS_LOOKUP_CODE>N</FIRM_STATUS_LOOKUP_CODE>
<LAST_
UPDATE_DATE>18-NOV-2008 22:25:27</LAST_UPDATE_DATE>
<LAST_UPDATED_BY>73951</LAST_UPDATED_BY>
<LINE_TYPE_ID>1</LINE_TYPE_ID>
<LAST_UPDATE_LOGIN>-1</LAST_UPDATE_LOGIN>
<CREATION_DATE>28-OCT-2008 21:53:15</CREATION_DATE>
<CREATED_BY>64914</CRE
ATED_BY>
<CATEGORY_ID>1813</CATEGORY_ID>
<LIST_PRICE_PER_UNIT>1326</LIST_PRICE_PER_UNIT>
<TAX_NAME>ExmptResale</TAX_NAME>
<LINE_TYPE>QUANTITY</LINE_TYPE>
<PURCHASE_BASIS>GOODS</PURCHASE_BASIS>
<LINE_AMOUNT>1,326.00</LINE_AMOUNT>
<BASE
UNITPRICE>1326</BASE_UNIT_PRICE>
<MATCHING_BASIS>QUANTITY</MATCHING_BASIS>
<PRICE_DIFF>
</PRICE_DIFF>
<LINE_SHORT_TEXT>
</LINE_SHORT_TEXT>
<LINE_LOCATIONS>
<LINE_LOCATIONS_ROW>
<SHIPMENT_NUM>1</SHIPMENT_NUM>
<DUE_DATE>03-
NOV-2008 00:00:00</DUE_DATE>
<QUANTITY>1</QUANTITY>
<PRICE_OVERRIDE>1326</PRICE_OVERRIDE>
<QUANTITY_CANCELLED>0</QUANTITY_CANCELLED>
<TAXABLE_FLAG>Y</TAXABLE_FLAG>
<PO_HEADER_ID>103843</PO_HEADER_ID>
<PO_LINE_ID>170164</PO_LI
NE_ID>
<LINE_LOCATION_ID>184959</LINE_LOCATION_ID>
<SHIPMENT_TYPE>STANDARD</SHIPMENT_TYPE>
<CONSIGNED_FLAG>N</CONSIGNED_FLAG>
<RECEIVING_ROUTING_ID>3</RECEIVING_ROUTING_ID>
<ACCRUE_ON_RECEIPT_FLAG>N</ACCRUE_ON_RECEIPT_FLAG>
<
CLOSED_REASON>Update Closure Status Rolled Up</CLOSED_REASON>
<CLOSED_DATE>19-NOV-2008 01:02:29</CLOSED_DATE>
<CLOSED_BY>219351</CLOSED_BY>
<ORG_ID>52605</ORG_ID>
<INSPECTION_REQUIRED_FLAG>N</INSPECTION_REQUIRED_FLAG>
<RECEIPT_REQ
UIRED_FLAG>Y</RECEIPT_REQUIRED_FLAG>
<QTY_RCV_TOLERANCE>10</QTY_RCV_TOLERANCE>
<QTY_RCV_EXCEPTION_CODE>WARNING</QTY_RCV_EXCEPTION_CODE>
<ENFORCE_SHIP_TO_LOCATION_CODE>WARNING</ENFORCE_SHIP_TO_LOCATION_CODE>
<ALLOW_SUBSTITUTE_RECEIPTS_F
LAG>N</ALLOW_SUBSTITUTE_RECEIPTS_FLAG>
<DAYS_EARLY_RECEIPT_ALLOWED>10</DAYS_EARLY_RECEIPT_ALLOWED>
<DAYS_LATE_RECEIPT_ALLOWED>10</DAYS_LATE_RECEIPT_ALLOWED>
<RECEIPT_DAYS_EXCEPTION_CODE>WARNING</RECEIPT_DAYS_EXCEPTION_CODE>
<INVOICE_CL
OSE_TOLERANCE>10</INVOICE_CLOSE_TOLERANCE>
<RECEIVE_CLOSE_TOLERANCE>1</RECEIVE_CLOSE_TOLERANCE>
<SHIP_TO_ORGANIZATION_ID>52438</SHIP_TO_ORGANIZATION_ID>
<CLOSED_CODE>CLOSED</CLOSED_CODE>
<REQUEST_ID>0</REQUEST_ID>
<PROGRAM_APPLICA
TION_ID>0</PROGRAM_APPLICATION_ID>
<PROGRAM_ID>0</PROGRAM_ID>
<PROGRAM_UPDATE_DATE>18-NOV-08</PROGRAM_UPDATE_DATE>
<LAST_ACCEPT_DATE>13-NOV-2008 00:00:00</LAST_ACCEPT_DATE>
<ENCUMBERED_FLAG>N</ENCUMBERED_FLAG>
<APPROVED_FLAG>Y</AP
PROVED_FLAG>
<APPROVED_DATE>28-OCT-2008 21:53:35</APPROVED_DATE>
<LAST_UPDATE_DATE>19-NOV-2008 01:02:29</LAST_UPDATE_DATE>
<LAST_UPDATED_BY>64839</LAST_UPDATED_BY>
<LAST_UPDATE_LOGIN>8132313</LAST_UPDATE_LOGIN>
<CREATION_DATE>28-O
CT-2008 21:53:15</CREATION_DATE>
<CREATED_BY>64914</CREATED_BY>
<QUANTITY_RECEIVED>1</QUANTITY_RECEIVED>
<QUANTITY_ACCEPTED>0</QUANTITY_ACCEPTED>
<QUANTITY_REJECTED>0</QUANTITY_REJECTED>
<QUANTITY_BILLED>1</QUANTITY_BILLED>
<
UNIT_MEAS_LOOKUP_CODE>EA</UNIT_MEAS_LOOKUP_CODE>
<QUANTITY_SHIPPED>0</QUANTITY_SHIPPED>
<TAX_USER_OVERRIDE_FLAG>N</TAX_USER_OVERRIDE_FLAG>
<MATCH_OPTION>P</MATCH_OPTION>
<TAX_CODE_ID>10718</TAX_CODE_ID>
<CALCULATE_TAX_FLAG>N</CALC
ULATE_TAX_FLAG>
<SECONDARY_QUANTITY_RECEIVED>0</SECONDARY_QUANTITY_RECEIVED>
<AMOUNT>1,326.00</AMOUNT>
<AMOUNT_RECEIVED>0.00</AMOUNT_RECEIVED>
<AMOUNT_BILLED>0.00</AMOUNT_BILLED>
<AMOUNT_CANCELLED>0.00</AMOUNT_CANCELLED>
<AMO
UNT_ACCEPTED>0.00</AMOUNT_ACCEPTED>
<AMOUNT_REJECTED>0.00</AMOUNT_REJECTED>
<SHIP_TO_LOCATION_ID>179305</SHIP_TO_LOCATION_ID>
<SHIP_TO_LOCATION_NAME>USMABILL179305</SHIP_TO_LOCATION_NAME>
<SHIP_TO_ADDRESS_LINE1>Lantheus Medical Imaging
</SHIP_TO_ADDRESS_LINE1>
<SHIP_TO_ADDRESS_LINE2>Building 250 ground floor</SHIP_TO_ADDRESS_LINE2>
<SHIP_TO_ADDRESS_LINE3>331 Treble Cove Rd</SHIP_TO_ADDRESS_LINE3>
<SHIP_TO_ADDRESS_INFO>BILLERICA, MA 01862</SHIP_TO_ADDRESS_INFO>
<SHIP
TOCOUNTRY>United States</SHIP_TO_COUNTRY>
<NEED_BY_DATE>03-NOV-2008 00:00:00</NEED_BY_DATE>
<PROMISED_DATE>03-NOV-2008 00:00:00</PROMISED_DATE>
<LINE_LOC_SHORT_TEXT>
</LINE_LOC_SHORT_TEXT>
<DISTRIBUTIONS>
<DISTRIBUTIONS_RO
W>
<AMOUNT_DELIVERED>0.00</AMOUNT_DELIVERED>
<AMOUNT_CANCELLED>0.00</AMOUNT_CANCELLED>
<DISTRIBUTION_TYPE>STANDARD</DISTRIBUTION_TYPE>
<PROGRAM_UPDATE_DATE>18-NOV-2008 22:25:27</PROGRAM_UPDATE_DATE>
<PROJECT_ID>56342</PR
OJECT_ID>
<TASK_ID>650410</TASK_ID>
<EXPENDITURE_TYPE>PC06.S0604 - GTM Cust CAPEX</EXPENDITURE_TYPE>
<EXPENDITURE_ORGANIZATION_ID>46494</EXPENDITURE_ORGANIZATION_ID>
<ACCRUE_ON_RECEIPT_FLAG>N</ACCRUE_ON_RECEIPT_FLAG>
<EX
PENDITURE_ITEM_DATE>27-OCT-2008 00:00:00</EXPENDITURE_ITEM_DATE>
<ORG_ID>52605</ORG_ID>
<DESTINATION_TYPE_CODE>EXPENSE</DESTINATION_TYPE_CODE>
<DESTINATION_ORGANIZATION_ID>52438</DESTINATION_ORGANIZATION_ID>
<ACCRUAL_ACCOUNT_ID
308864</ACCRUAL_ACCOUNT_ID><VARIANCE_ACCOUNT_ID>1335462</VARIANCE_ACCOUNT_ID>
<PREVENT_ENCUMBRANCE_FLAG>N</PREVENT_ENCUMBRANCE_FLAG>
<PO_DISTRIBUTION_ID>170738</PO_DISTRIBUTION_ID>
<LAST_UPDATE_DATE>18-NOV-2008 22:19:12</LAST
UPDATEDATE>
<LAST_UPDATED_BY>64671</LAST_UPDATED_BY>
<PO_HEADER_ID>103843</PO_HEADER_ID>
<PO_LINE_ID>170164</PO_LINE_ID>
<LINE_LOCATION_ID>184959</LINE_LOCATION_ID>
<SET_OF_BOOKS_ID>4155</SET_OF_BOOKS_ID>
<CODE_
COMBINATION_ID>1335462</CODE_COMBINATION_ID>
<QUANTITY_ORDERED>1</QUANTITY_ORDERED>
<LAST_UPDATE_LOGIN>8137792</LAST_UPDATE_LOGIN>
<CREATION_DATE>28-OCT-2008 21:53:15</CREATION_DATE>
<CREATED_BY>64914</CREATED_BY>
<QUANT
ITY_DELIVERED>1</QUANTITY_DELIVERED>
<QUANTITY_BILLED>1</QUANTITY_BILLED>
<QUANTITY_CANCELLED>0</QUANTITY_CANCELLED>
<REQ_DISTRIBUTION_ID>241920</REQ_DISTRIBUTION_ID>
<DELIVER_TO_LOCATION_ID>179305</DELIVER_TO_LOCATION_ID>
<DELIVER_TO_PERSON_ID>271332</DELIVER_TO_PERSON_ID>
<RATE_DATE>28-OCT-2008 00:00:00</RATE_DATE>
<AMOUNT_BILLED>1,326.00</AMOUNT_BILLED>
<ACCRUED_FLAG>N</ACCRUED_FLAG>
<ENCUMBERED_FLAG>N</ENCUMBERED_FLAG>
<RECOVERY_RAT
E>0.00</RECOVERY_RATE>
<DESTINATION_CONTEXT>EXPENSE</DESTINATION_CONTEXT>
<DISTRIBUTION_NUM>1</DISTRIBUTION_NUM>
<REQUEST_ID>0</REQUEST_ID>
<PROGRAM_APPLICATION_ID>0</PROGRAM_APPLICATION_ID>
<PROGRAM_ID>0</PROGRAM_ID>
<CHARGE_ACCOUNT>877.JGK5.XX539100.ZZZZZZZ.ZZZZZ.ZZZZZZ.ZZZZZZZZ.JA078253ZZ.J.ZZZZZZZZZZ</CHARGE_ACCOUNT>
<FULL_NAME>Ansari, Shaheen</FULL_NAME>
<EMAIL_ADDRESS>[email protected]</EMAIL_ADDRESS>
<REQUESTER_DELIVER_FIRST_NAME>Sh
aheen</REQUESTER_DELIVER_FIRST_NAME>
<REQUESTER_DELIVER_LAST_NAME>Ansari</REQUESTER_DELIVER_LAST_NAME>
</DISTRIBUTIONS_ROW>
</DISTRIBUTIONS>
</LINE_LOCATIONS_ROW>
</LINE_LOCATIONS>
</LINES_ROW>
</LINES>
<LINE_ATTACHMENTS>
<TEX
T>CCO Configuration Reference=N/A
Bid/Deal ID=N/A
CCO Key if applicable=N/A</TEXT>
<ID>170164</ID>
</LINE_ATTACHMENTS>
<ADDRESS_DETAILS>
<ADDRESS_DETAILS_ROW>
<LOCATION_ID>67670</LOCATION_ID>
<ADDRESS_STYLE>US_GLB</ADDRESS_STYLE>
<ADDR_LABEL_1>Cou
ntry</ADDR_LABEL_1>
<ADDR_LABEL_2>Address Line1</ADDR_LABEL_2>
<ADDR_LABEL_3>Address Line2</ADDR_LABEL_3>
<ADDR_LABEL_4>Address Line3</ADDR_LABEL_4>
<ADDR_LABEL_5>Zip Code</ADDR_LABEL_5>
<ADDR_LABEL_6>City</ADDR_LABEL_6>
<ADDR_LABEL_7>State</A
DDR_LABEL_7>
<ADDR_LABEL_8>County</ADDR_LABEL_8>
<ADDR_LABEL_9>Fax</ADDR_LABEL_9>
<ADDR_LABEL_10>Sales Tax Override</ADDR_LABEL_10>
<ADDR_LABEL_11>Inside City Limits</ADDR_LABEL_11>
<ADDR_LABEL_12>Telephone</ADDR_LABEL_12>
<ADDR_DATA_2>BT Amer
icas Inc.|11440 Commerce Park Drive|Reston, VA 20191</ADDR_DATA_2>
</ADDRESS_DETAILS_ROW>
<ADDRESS_DETAILS_ROW>
<LOCATION_ID>67644</LOCATION_ID>
<ADDRESS_STYLE>US_GLB</ADDRESS_STYLE>
<ADDR_LABEL_1>Country</ADDR_LABEL_1>
<ADDR_LABEL_2>Address Lin
e1</ADDR_LABEL_2>
<ADDR_LABEL_3>Address Line2</ADDR_LABEL_3>
<ADDR_LABEL_4>Address Line3</ADDR_LABEL_4>
<ADDR_LABEL_5>Zip Code</ADDR_LABEL_5>
<ADDR_LABEL_6>City</ADDR_LABEL_6>
<ADDR_LABEL_7>State</ADDR_LABEL_7>
<ADDR_LABEL_8>County</ADDR_LABEL
_8>
<ADDR_LABEL_9>Fax</ADDR_LABEL_9>
<ADDR_LABEL_10>Sales Tax Override</ADDR_LABEL_10>
<ADDR_LABEL_11>Inside City Limits</ADDR_LABEL_11>
<ADDR_LABEL_12>Telephone</ADDR_LABEL_12>
<ADDR_DATA_1>US</ADDR_DATA_1>
<ADDR_DATA_2>Invoice To:</ADDR_DATA
_2>
<ADDR_DATA_3>BT AMERICAS ACCOUNTS PAYABLE</ADDR_DATA_3>
<ADDR_DATA_4>PO Box 696025</ADDR_DATA_4>
<ADDR_DATA_5>78269</ADDR_DATA_5>
<ADDR_DATA_6>SAN ANTONIO</ADDR_DATA_6>
<ADDR_DATA_7>TX</ADDR_DATA_7>
<ADDR_DATA_8>USA</ADDR_DATA_8>
</ADDRES
S_DETAILS_ROW>
<ADDRESS_DETAILS_ROW>
<LOCATION_ID>179305</LOCATION_ID>
<ADDRESS_STYLE>US_GLB</ADDRESS_STYLE>
<ADDR_LABEL_1>Country</ADDR_LABEL_1>
<ADDR_LABEL_2>Address Line1</ADDR_LABEL_2>
<ADDR_LABEL_3>Address Line2</ADDR_LABEL_3>
<ADDR_LABE
L_4>Address Line3</ADDR_LABEL_4>
<ADDR_LABEL_5>Zip Code</ADDR_LABEL_5>
<ADDR_LABEL_6>City</ADDR_LABEL_6>
<ADDR_LABEL_7>State</ADDR_LABEL_7>
<ADDR_LABEL_8>County</ADDR_LABEL_8>
<ADDR_LABEL_9>Fax</ADDR_LABEL_9>
<ADDR_LABEL_10>Sales Tax Override<
/ADDR_LABEL_10>
<ADDR_LABEL_11>Inside City Limits</ADDR_LABEL_11>
<ADDR_LABEL_12>Telephone</ADDR_LABEL_12>
<ADDR_DATA_1>US</ADDR_DATA_1>
<ADDR_DATA_2>Lantheus Medical Imaging</ADDR_DATA_2>
<ADDR_DATA_3>Building 250 ground floor</ADDR_DATA_3>
<
ADDR_DATA_4>331 Treble Cove Rd</ADDR_DATA_4>
<ADDR_DATA_5>01862</ADDR_DATA_5>
<ADDR_DATA_6>BILLERICA</ADDR_DATA_6>
<ADDR_DATA_7>MA</ADDR_DATA_7>
<ADDR_DATA_8>Middlesex</ADDR_DATA_8>
</ADDRESS_DETAILS_ROW>
</ADDRESS_DETAILS></PO_DATA>

Cancel PO Programatically

Hello All,
I need to cancel a Purchase Order Programatically. Can this be done?
Thanks for any help,
Bradley

It should be taken from po_document_types_all. You can find document_type and sub_type there.
Have you changed the fnd_global.apps_initialize parameters right? Like user_id and responsibility_id and appl_id? Not sure your site setup for the security. If you navigate to setup-->Purchasing-->Document Types and select Purchase Order Standard, you can see Control options there.
To avoid doubt, select user_id of the buyer and initialize apps.
select b.user_id into l_user_Id from po_agents a, fnd_user b, po_headers_all c
where a.agent_id=b.employee_id
and a.agent_id=c.agent_id
and c.segment1='5396';
select wf_item_type,wf_item_key from po_agents a, fnd_user b, po_headers_all c
where a.agent_id=b.employee_id
and a.agent_id=c.agent_id
and c.segment1='5396';
select number_value
into l_responsibility_id
from wf_item_attribute_values
where item_type='POAPPRV' --wf_item_type from above
and item_key='81411-392214' --wf_item_key from above
and name in ('RESPONSIBILITY_ID');
select number_value
into l_application_id
from wf_item_attribute_values
where item_type='POAPPRV'
and item_key='81411-392214'
and name in ('APPLICATION_ID');
fnd_global.apps_initialize(l_user_id,l_responsibility_id,l_application_id);
then call po_document_control_pub.
You can enable FND Debug Profiles and check fnd_log_messages.
Also call this procedure to get any session specifif messages;
PROCEDURE get_error_stack (x_msg_data OUT VARCHAR2)
IS
l_msg_index NUMBER;
l_msg_data VARCHAR2 (32000);
BEGIN
l_msg_index := 1;
x_msg_data := '';
FOR i IN 1 .. fnd_msg_pub.count_msg
LOOP
fnd_msg_pub.get (p_msg_index => i, p_encoded => 'F', p_data => l_msg_data, p_msg_index_out => l_msg_index);
x_msg_data := x_msg_data || l_msg_data;
DBMS_OUTPUT.put_line (x_msg_data);
END LOOP;
END get_error_stack;
THanks
Nagamohan

How to find the workflow for Change Request for the PO's

Hi All,
We have a PO which is pending and we can't receipt it again nor make payment on this. After checking the Approval history for that PO we found that the change request has been made. The change request was to change the amount to be paid to R39196 instead of R58237.00. We don't know where to check the workflow for the change request to identify the cause.
what i need to know is how to find the workflow for that change request? The other workflows can be checked using the po_header_id for the PO's but i am confused with the change request workflow
Your input will be highly appreciated.
Thanks in advance
Rgds,
Sonia

For 11.5.10.2 run this query to determine the keys to search on:
Select wf_item_type, wf_item_key from APPS.po_change_requests where document_type = 'PO' and Document_num = 'put-PO-number-here'
Then use the keys returned by the query to look up the Workflow in
Workflow Administrator Web Applications / Administrator Workflow / Status Monitor
Search using the results returned in fields "Type Internal Name" and "Item Key" in Status Monitor
The query for change requests on a specific Requisition would be:
Select wf_item_type, wf_item_key from APPS.po_change_requests where document_type = 'REQ' and Document_num = 'put-Req-number-here'

HOW TO FIND WF_ITEM_TYPE AND WF_ITEM_KEY FOR PO

제품 : MFG_PO
작성날짜 : 2003-05-14
HOW TO FIND WF_ITEM_TYPE AND WF_ITEM_KEY FOR PO
===============================================
PURPOSE
This solution is for Oracle Purchasing 11 and higher
Explanation
1. Start a SQL*Plus session using the APPS schema.
2. Run the following script and enter the Purchase Order number that is stuck
in process when prompted for the PO_NUMBER:
     SELECT WF_ITEM_TYPE, SUBSTR(WF_ITEM_KEY,1,25) "WF_ITEM_KEY"
     FROM PO_HEADERS_ALL
     WHERE AUTHORIZATION_STATUS='IN PROCESS'
     AND SEGMENT1='&PO_NUMBER';
3. If more than one row is returned, then run the following script and only
refer to the row that contains the OPERATING_UNIT_NAME that equals the
operating unit name tied to the responsibility used when the Purchase Order was
discovered as being stuck in process.
     SELECT SUBSTR(WF_ITEM_TYPE,1,12) "WF_ITEM_TYPE",
     SUBSTR(WF_ITEM_KEY,1,15) "WF_ITEM_KEY",
     SUBSTR(NAME,1,35) "OPERATING_UNIT_NAME"
     FROM PO_HEADERS_ALL PA, HR_ORGANIZATION_UNITS OU
     WHERE PA.ORG_ID=OU.ORGANIZATION_ID
     AND AUTHORIZATION_STATUS='IN PROCESS'
     AND SEGMENT1='&PO_NUMBER';
Example
Reference Documents
-------------------

Hi Kishore,
Welcome to SCN!
to find the sales order from Purchase order , go to SE16, Enter the table name as VBAK and press Enter.
In BSTNK field of VBAK, Enter the Purchase order number. System will return you corresponding sales order.
Hope this will help you.
Regards,
Nikhil

Document in Process but not found in the workflow

Hi,
we have a document entered in purchasing and still in process but it is not found in the workflow, then it can't be approved by users.
help please, thanks.

You can try in test instance it first;
Run this script for your PO number, it will change the status from In Process to incomplete or Required reapproval,
then the PO need to be approved again, and you will be able to see it in the workflow
UPDATE apps.po_headers_all SET authorization_status = decode(approved_date, NULL, 'INCOMPLETE',
'REQUIRES REAPPROVAL'), wf_item_type = NULL, wf_item_key = NULL, approved_flag = decode(approved_date, NULL, 'N', 'R')
WHERE po_header_id= -Po header ID-
Hope it work

DOCUMENT MANAGER가 DOWN되어 PO STATUS가 IN PROCESS 상태로 APPROVE 되지 않는 경우

제품 : MFG_PO
작성날짜 : 2002-11-28
DOCUMENT MANAGER가 DOWN되어 PO STATUS가 IN PROCESS 상태로 APPROVE 되지 않는 경우
==================================================================
PURPOSE
Document Manager가 Down 되거나 하여 PO Approve 시에 정상적인 approve가 되지 않고 PO Status가 Inprocess로 남아 있어 approve할수 없는 경우에 처리 방법
Explanation
Run WFRETRY:
select wf_item_key, wf_item_type, segment1, po_header_id
from po_headers_all
where segment1='<po number>';
select item_key
from wf_items
where item_type='POAPPRV' and item_key like '<po_header_id>%';
wfretry.sql
The parameters passed are:
- <item_type>
- <item_key>
- accept activity prompt "Label: " POAPPRV_TOP
- accept comflag prompt "Command: " (RETRY)
- accept result prompt "Result: " (NULL)
Example
Reference Documents
-------------------

PO Approval Process

Hi,
We have a problem with the Workflow Nofitication page resolving with the host name of our server and it does not come up. I have some POs pending that need approved. Is there any other way a Purchasing Superuser can approve these POs/Releases that are in process without having to go to the notification page?
Thank you
A/A

Hi,
You can use the "Status Monitor" menu, and search your workflows using following criterias :
- Item Type = POAPPRV
- User Key = <order number>
or
- Item Key = (SELECT wf_item_key FROM po_headers_all WHERE segment1 = <order number>)
Then open the workflow step by selecting your workflow, clicking the "Activity history" button and search the notification step (it should be the last) :
Then you can reject or approve from the notification itself.
You may also use "Administration" -> "Notification search" to find pending notifications
Kind regards,
Xavier

Error while invoking a process

Hi Team,
I get the following error while invoking a process.
ALC-DSC-125-000: com.adobe.idp.dsc.registry.EndpointNotEnabledException: SOAP endpoint is not enabled for: ExtractingXML/ReadResource
at com.adobe.idp.dsc.provider.impl.base.AbstractMessageReceiver.validateEndpoint(AbstractMes sageReceiver.java:258)
at com.adobe.idp.dsc.provider.impl.soap.axis.sdk.SoapSdkEndpoint.invokeCall(SoapSdkEndpoint. java:136)
at com.adobe.idp.dsc.provider.impl.soap.axis.sdk.SoapSdkEndpoint.invoke(SoapSdkEndpoint.java :81)
at sun.reflect.GeneratedMethodAccessor755.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCProvider.java:397)
at org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:186)
at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:323)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:454)
at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:699)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper. java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at com.adobe.idp.dsc.provider.impl.soap.axis.InvocationFilter.doFilter(InvocationFilter.java :43)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at com.adobe.idp.um.auth.filter.CSRFFilter.doFilter(CSRFFilter.java:41)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletC ontext.java:3496)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2 180)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Can anyone please help me with this error.

I checked my server (which has all the default Adobe services) and the only service I have that comes close is:
the Repository service's "Read Resource Content" operation. In the list that comes up as RepositoryService.
The Barcode's Extract to XML service. In the list that comes up as BarcodedFormsService
Neither of these is an exact match to the error. Is your process calling a sub process you built? Does that service actually exist on the server? If you do a record/playback (in workbench) on which step does the process fail?
If you look through the entire list of SOAP services (in Adminui) are any of them disabled?

Logical GR in Third Party Process

Hi Friends
There is logical GR involved in third party process. What if we do not want to trigger it?

very useful thraed for your Qn-
[stock not updating after doing MIGO (gr) for third party sales |stock not updating after doing MIGO (gr) for third party sales;
BR
Raj

EH&S WWI for GLM print request processing

Hi all,
we installed EH&S WWI for GLM print request processing scenario, following the note:"1394553", but when we try to print we receive this error from WWI:
Start Function 'WWI_PRINTREQUEST_CREATE'
Initializing parameters
Receiving data from client
   calling RfcGetData returned 0
    receiving data lasted: 0.0 sec.
    Retrieving print request data from RFC interface
    Using Temp Directory E:\WWI\TEMP\BSV100000000000062
   Delete files in E:\WWI\TEMP\BSV100000000000062
    Creating text file E:\WWI\TEMP\BSV100000000000062\r000000000062.val
    Writing data to text file 39 lines, 1009 characters
    Updating print request status from 0 to 1
    [DB time] Writing print request lasted 9 ms
Start processing command 'Create print request' in synchronous mode
Creating print request 000000000062
WwiSapDms::retrieveDocument: RFC error when calling ABAP function moduleRFC connection is not Unicode
WwiSapDms::retrieveDocument: RFC error when calling ABAP function module
key     : RFC_ERROR_SYSTEM_FAILURE
message : See RFC trace file or SAP system log for more details
Reading SBV document IB0120510 from Cache failed
    WwiCacheRead resulted with -1
    Updating print request status from 1 to 5
    [DB time] Writing print request lasted 4 ms
##### Command 'Create print request' finished with status E #####
    Storing ERR file E:\WWI\TEMP\BSV100000000000062\l000000000062.err into DMS succeeded
    22 lines
Sending data to client
   calling RfcSendData returned 0
    sending data lasted: 0.0 sec.
Elapsed time : 0.1 sec.
We don't understand what kind of RFC or what part of customizing we have to check, could you please help us?
Thanks,
Christian

Dear Pugal
we are not using GLM + and I am not sure about the technqiue used there to handle load balancing. Regarding general WWI setup I assume you know this Note: EH&amp;S: Availability and performance of WWI and Expert servers
On the top there is a further SAP Note abvailable which might be of interest. This is referenced here:
http://de.scribd.com/doc/191576739/011000358700000861002013-e
May be check OSS note: 1958655; OSS Note 1155294 is more related to normal WWI stuff; but may be check it as well. May be 1934253 might help better
May be this might help.
C.B.
PS: may be check as well: consolut - EHS_MD_140_01 - EH&amp;S-Management-Server einrichten
The load balancing of synchron WWi servers is donein the "RFC" layer, therefore you have no inffluence here, for asynchron WWI servers you can do a lot to manage the WWI load balancing by using "exits" etc.

PO 가 IN PROCESS 상태이고, 해당 PO의 WF_ITEM_TYPE 또는 WF_ITEM_KEY 이 존재하지않는 경우의 처리 방안

Similar Messages

Maybe you are looking for