Submit xml for csv generation
Hi
I have a pdf which contains a table, I click a submit button and the data is posted to a url. The response is a csv file from the xml. Is there anyway in which reader 9 will be able to open the resulting csv in a native application without reader being opened in the broswer. This functionality did exist in reader 8, but is now gone in reader 9.
Is there anyway I can achive this?
Thanks in advance.
Dylan
When the httpservices completes isn't the result bound to an arrayCollection (or array) so you could essesntially accomplish anything you want, sort search etc..
Is the XML result directly bound to a datagrid or is it bound to arrayCollection first and then bind the arrayCollection to the data grid?
From the network layer comparison, say you have 100 rows with 10 columns, the file size of XML vs CSV makes a big difference. Do you think this warrants bringing the file as CSV instead of XML? You also have to consider the server side doing the extra formating. You will notice a big difference in an enterprise database if its doing extra work and file I/O.
Being so used to ODBC-RAW data, I'm finding some apps are slow because of the XML format and I'm looking for an alternative similar to the ODBC-RAW data format. I do agree that you can do more with XML but if it's just use for say in drop down list, data grid and not so much for formatting, I think CSV will do just fine. I would however, bring in a single row as XML.
Thanks for replying back so quickly.
-nobody-
Similar Messages
-
In EJB3 entities, what is the equiv. of key-cache-size for PK generation?
We have an oracle sequence which we use to generate primary keys. This sequence is set to increment by 5.
e.g.:
create sequence pk_sequence increment by 5;
This is so weblogic doesn't need to query the sequence on every entity bean creation, it only needs to query the sequence every 5 times.
With CMP2 entity beans and automatic key generation, this was configured simply by having the following in weblogic-cmp-rdbms-jar.xml:
<automatic-key-generation>
<generator-type>Sequence</generator-type>
<generator-name>pk_sequence</generator-name>
<key-cache-size>5</key-cache-size>
</automatic-key-generation>
This works great, the IDs created are 10, 11, 12, 13, 14, 15, 16, etc and weblogic only needs to hit the sequence 1/5 times.
However, we have been trying to find the equivalent with the EJB3-style JPA entities:
We've tried
@SequenceGenerator(name = "SW_ENTITY_SEQUENCE", sequenceName = "native(Sequence=pk_sequence, Increment=5, Allocate=5)")
@SequenceGenerator(name = "SW_ENTITY_SEQUENCE", sequenceName = "pk_sequence", allocationSize = 5)
But with both configurations, the autogenerated IDs are 10, 15, 20, 25, 30, etc - weblogic seems to be getting a new value from the sequence every time.
Am i missing anything?
We are using weblogic 10.3If you are having a problem it is not clear what it is from what you have said. If you have sugestions for improving some shortcomings you see in Flash CC then you should submit them to:
Adobe - Wishlist & Bug Report
http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform -
Generate Photo Gallery XML for Spry with Adobe Bridge
Wanted to post a note to what I've discovered/worked out -- a
way to
generate a very useful photos.xml from Adobe Bridge. If you
use Bridge,
it's very easy to add titles, keywords, ratings -- all kinds
of metadata
that one might use in a photo gallery. Here it is in case
anyone wants
to use.
The script is based on one I found at the Adobe User to User
Bridge
Scripting Forum for exporting a CSV file.
Note 1: this particular script doesn't take into account
CDATA that
might exist in your metadata, like ampersands in your title.
I've just
avoided using those, but you could also have the script write
out a
CDATA node for that info instead.
Note 2: this script does not write out a thumbpath,
thumbwidth or
thumbheight attribute. But usually the thumbpath is the exact
same as
the regular "path" attribute, and the thumbwidth and
thumbheight are
just a ratio of the regular "width" and "height" attributes.
I added a
bit of JS to the gallery.js file to calculate those before
growing the
thumbnail on rollover.
Personally I'm using keywords as categories and titles as
captions and
sorting by rating (stars in Bridge), so here's the .jsx file
I created.
The script should be saved to the folder "StartupScripts" in
Program
Files/Common Files/Adobe.
Hope this is useful for others too!
#target bridge
if (BridgeTalk.appName == "bridge" ) {
// create menu
var menu = MenuElement.create( "command", "Export XML File",
"at the end
of Tools");
menu.onSelect = function(m) {
try {
// ask for the name of the output file
var f = File.saveDialog("Export XML file to:", "XML
File:*.XML");
if ( !f ) { return; }
// open filestream and write first line
f.open("w");
f.writeln("\<photos\>\r\r");
// get a list of all the visible thumbnails in Bridge
var items = app.document.visibleThumbnails;
for (var i = 0; i < items.length; ++i) { var item = items
f.writeln("\<photo path = \"" + item.name + "\"" + "\r" +
"width = " +
"\""+ getWidth(item) + "\"" + "\r" + "height = " + "\""+
getHeight(item)
+ "\"" + "\r" + "rating = " + "\""+ getRating(item) + "\"" +
"\r" +
"categories = " + "\""+ listKeywords(item) + "\"" + "\r" +
"caption = "
+ "\""+ getTitle(item) + "\"" + " \>" + "\r" +
"\<\/photo\>\r\r" ); }
f.writeln("\<\/photos\>");
f.close();
} catch(e) {
function getTitle(tn) {
md = tn.metadata;
md.namespace = "
http://purl.org/dc/elements/1.1/";
var varTitle = md.title;
return varTitle;
function getWidth(tn) {
md = tn.metadata;
md.namespace = "
http://ns.adobe.com/tiff/1.0/"
var varWidth = md.ImageWidth;
return varWidth;
function getHeight(tn) {
md = tn.metadata;
md.namespace = "
http://ns.adobe.com/tiff/1.0/"
var varHeight = md.ImageLength;
return varHeight;
function getRating(tn) {
md = tn.metadata;
md.namespace = "
http://ns.adobe.com/xap/1.0/"
var varRating = md.Rating;
return varRating;
function listKeywords(tn) {
md = tn.metadata;
md.namespace = "
http://ns.adobe.com/photoshop/1.0/";
var Keywords = md.Keywords;
var varKeywords = "" ;
for ( var i = 0; i < Keywords.length; ++i ) { varKeywords
= varKeywords
+ Keywords + ","; }
return varKeywords;I updated the script so it exports an XML file from Bridge
with full
compatibility with the Spry Demo Photo Gallery, to use as
photos.xml.
It's at the same address:
http://www.imagicdigital.com/spry/bridge_export_xml.zip
To Use:
The script goes in the folder "StartupScripts" in Program
Files/Common
Files/Adobe.
Launch Bridge and browse to a folder that contains the files
you want in
your gallery -- the "source" folder, as it were.
Choose the menu command "Tools > Export XML for Spry
Gallery".
Type a name for your XML file in the Save dialog box, choose
a location,
and hit "Save".
In the dialog box that pops up, enter a max length/width for
your
thumbnails, in pixels. Some common sizes are "75" , "100" or
"125".
Hit "OK". You should see an alert pop up telling you "XML
file
successfully created!" -
BI Publisher 10.1.4.3 - To connect to AD for report generation
Hi,
I need to generate a report against an LDAP(Active directory) . I'm using BIP 10.1.4.3. When i try to configure a datasource, the options present are
1. JDBC
2.JNDI
3. File
3.OLAP.
Can any one guide on how to connect to Active Directory in BI Publisher for report generation.
Thanks in Advance.You have posted your question in the Oracle Portal forum. Please submit your question in the [url https://forums.oracle.com/forums/forum.jspa?forumID=47]Identity Management forum.
Thanks,
EJ -
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> -
Conversion from xml to csv using xsl
hi i am converting from xml to csv using xsl i am getting the extra junk character(space) in the csv file.below i written the xml file and xsl file
xml file
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<?xml-stylesheet type="text/xsl"?>
<DOCUMENTS>
<FILE>
<DOCUMENT>
<BUSINESS>finance</BUSINESS>
<PROGRAM>CM</PROGRAM>
<PROJECT>Testing Area</PROJECT>
<NAME>121940~1.doc</NAME>
<TEXT>SQL</TEXT>
<LINK>http://www.sql.org/</LINK>
</DOCUMENT>
<DOCUMENT>
<BUSINESS>finance</BUSINESS>
<PROGRAM>CM</PROGRAM>
<PROJECT>Testing Area</PROJECT>
<NAME>121940~1.doc</NAME>
<TEXT>Information</TEXT>
<LINK>http://google.com/</LINK>
</DOCUMENT>
<DOCUMENT>
<BUSINESS>finance</BUSINESS>
<PROGRAM>CM</PROGRAM>
<PROJECT>Testing Area</PROJECT>
<NAME>121940~1.doc</NAME>
<TEXT>Configuration</TEXT>
<LINK>http://msdn.microsoft.com/</LINK>
</DOCUMENT>
</FILE>
</DOCUMENTS>
xsl file
<?xml version="1.0"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<xsl:output method="text" indent="yes"/>
<xsl:template match="DOCUMENTS">
<xsl:text>Business,Program,Project,DocumentName,Textforlink,Hyperlink</xsl:text>
<xsl:apply-templates/>
</xsl:template>
<xsl:template match="FILE">
<xsl:value-of select="DOCUMENT/BUSINESS"/>
<xsl:value-of select="','"/>
<xsl:value-of select="DOCUMENT/PROGRAM"/>
<xsl:value-of select="','"/>
<xsl:value-of select="DOCUMENT/PROJECT"/>
<xsl:value-of select="','"/>
<xsl:value-of select="DOCUMENT/NAME"/>
<xsl:apply-templates/>
</xsl:template>
<xsl:template match="DOCUMENT">
<xsl:value-of select="','"/>
<xsl:value-of select="','"/>
<xsl:value-of select="','"/>
<xsl:value-of select="','"/>
<xsl:value-of select="TEXT"/>
<xsl:value-of select="','"/>
<xsl:value-of select="LINK"/>
</xsl:template>
</xsl:stylesheet>
for converting to csv i am using java program.
please go through it.<xsl:value-of select="','"/>That's not the correct way to output a literal comma. Just write the comma directly, or use xsl:text. And don't put in those line breaks either. You can reduce the rule for FILE to something like this:
xsl:template match="FILE">
<xsl:value-of select="DOCUMENT/BUSINESS"/>, <xsl:value-of select="DOCUMENT/PROGRAM"/>, <xsl:value-of select="DOCUMENT/PROJECT"/>, <xsl:value-of select="DOCUMENT/NAME"/>
<xsl:apply-templates/>
</xsl:template> -
File adapter: Receiver File Content Conversion problem.. XML to CSV..!!
Hi,
I am facing some problem in FCC for Receiver adapter. It has to convert from XML to CSV File.
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:PaymentFull_Target xmlns:ns0="http://sdn.com/Payment">
- <RECORDSET>
- <Header>
<LineItem>1</LineItem>
<SaleNumber>102</SaleNumber>
<TransNumber>105</TransNumber>
<Store>1326</Store>
<variant>Z6</variant>
<TransType>NEW</TransType>
<Adjustm_Type />
</Header>
- <Header>
<LineItem>2</LineItem>
<SaleNumber>102</SaleNumber>
<TransNumber>105</TransNumber>
<Store>1326</Store>
<variant>Z6</variant>
<TransType>NEW</TransType>
<Adjustm_Type />
</Header>
- <Header>
<LineItem>3</LineItem>
<SaleNumber>102</SaleNumber>
<TransNumber>105</TransNumber>
<Store>1326</Store>
<variant>Z6</variant>
<TransType>NEW</TransType>
<Adjustm_Type />
</Header>
</RECORDSET>
</ns0:PaymentFull_Target>
Output File is coming only with lineitem values , remaining fields are not coming.
*1,2,3*
FCC Used...
RecordSet Structure -- Header
Header.fieldNames -
LineItem,SaleNumber,TransNumber,Store,variant,TransType,Adjustm_Type
Header.fieldSeparator----- ,
Header.endSeparator----- 'nl'
Did I miss anything.. any idea whats going wrong?
Thanks
DeepthiHi Deepthi,
Mention the occurrence of header in Recordset
You specify like this:
Recordset: Header, *
Header.fieldSeparator : u2018Field Separatoru2019
-->For FCC on Receiver side you donu2019t have to mention the field names.
-->The u2018endSeparatoru2019 parameter needs to given for substructure only
Check this links:
http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
/people/shabarish.vijayakumar/blog/2007/08/03/file-adapter-receiver--are-we-really-sure-about-the-concepts
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
Rgds,
Akhila -
FILE model support for CSV and fixed-length format!!
Hi all,
As I'm working on a data conversation project, we are in the middel to design whether the extraction for the data source should be in CSV or fixed-length. Here is the pros and cons:
CSV:
1. There are a lot of remarks field in the data which are all free text. It's really hard to define the record delimiter.
2. Extracted file size for CSV is relatively small compare with fixed-length.
fixed-length:
Even for fixed length, we can either
1. Extract the file without an separator/delimiter (1 row) with fixed column length
2. Extract the file with fixed column length per record and define the record delimiter to separarter the record.
I'd try all the above formats and it seems ODI is more prefer on CSV or combined mode (fixed column length) as:
1. The LKM (file to external table) need to be customzised to handle the file format which without any separator/delimiter
2. It is very hard to reverse the column definition for fixed-length (no delimiter)
Any suggestion?
TaoYou can transform your files to an xml format using respective tags:
eg:
<?xml version="1.0" encoding="UTF-8"?>
<MONEY>
<MoneyID>MoneyID0</MoneyID>
<ContractID>ContractID0</ContractID>
<EffectiveDate>2006-05-04T18:13:51.0Z</EffectiveDate>
<MessageDate>2006-05-04T18:13:51.0Z</MessageDate>
<ReversalIndicator>false</ReversalIndicator>
<PriorMoneyID>PriorMoney, something "ID0" for life;</PriorMoneyID>
<Amount>0</Amount>
<MoneyType>0</MoneyType>
<ExchangeDetails>
<CostBasis>0</CostBasis>
<ExchangeType>0</ExchangeType>
<MEC>false</MEC>
<LoanAmount>0</LoanAmount>
</ExchangeDetails>
</MONEY>
So, as you see, you can embed any symbol in a tag.
After creating this xml file, you can use XML technology in Topology Manager to map to this file and then create a data store based on this technology.
And you will be able to retrieve the data in this file under respective column headers without worrying about delimiters existing in the actual data. -
Hi,
I would like to know as to how can I add links to open xml and csv files stored in another location? Please advice how to place links in my frame maker document?
Kindly advice.
Thanks
PriyaSpecial > Hypertext > Command "open document" will do its best to open the target document inside FrameMaker, which may not be much help; Special > Hypertext > Command "message …" will use the application you specify. The user guide for 7.0 says this about absolute links, and I don't think anything has changed since:
For example, to start PaintBrush and open the Ship.pcx file on drive C you would use the command message system pbrush.exe C:/Ship.pcx
I've not often used a relative link, and not recently: the same source says
folder levels are separated by a slash / even in Windows and Mac
[relative links] FrameMaker searches for a relative pathname beginning in the folder that contains the current document
[absolute links] FrameMaker searches for an absolute pathname beginning at the top of the file system. In Windows, the absolute pathname begins with the drive specifier, a colon and a slash. -
How to convert org hierarchy XML to CSV/Excel format using PI/XI
Hi All,
I am working with SAP PI/XI for the first time and need some help file conversion of complex hierarchy XML to CSV file using PI. I have done plenty of research on SDN and could find much related to what I want to do.
Here is the example of how my input XML would look like:
<?xml version="1.0" encoding="UTF-8"?>
<PartyMaster type="OrgHierarchy" name="Compass Group Owned">
<PartyMasterHierarchy>
<Hierarchy level="3" nodeName="Bon Appetit Sector" type="Sector" ID="A00000" refID="A00000">
<Hierarchy level="4" nodeName="BA Division" type="Division" ID="AB0000" refID="AB0000" >
<Hierarchy level="5" nodeName="BA East Coast Region" type="Region" ID="ABE000" refID="ABE000">
<Hierarchy level="6" nodeName="Engstrom, John RVP" type="District" ID="ABE01" refID="ABE01" >
</Hierarchy>
</Hierarchy>
</Hierarchy>
</Hierarchy>
<Hierarchy level="3" nodeName="Levy Sector" type="Sector" ID="K00000" refID="K00000".
<Hierarchy level="4" nodeName="Levy Sector Division" type="Division" ID="K90000" refID="K90000">
<Hierarchy level="5" nodeName="Levy Sector Region" type="Region" ID="K99000" refID="K99000">
<Hierarchy level="6" nodeName="TBA Total" type="District" ID="K9901" refID="K9901"> </Hierarchy>
</Hierarchy>
</Hierarchy>
</Hierarchy>
</PartyMasterHierarchy>
</PartyMaster>
I would like to get CSV output in the format below
DISPLAY_NAME, DOCUMENT_DESCRIPTION, PARENT, EXTERNAL_ID, ORG_UNIT_TYPE
Bon Appetit Sector, Bon Appetit Sector,constant value, A00000, constant value
Levy Sector, Levy Sector, constant value, K00000, constant value
BA Division, BA Division, A00000, AB0000, constant value
Levy Sector Division, Levy Sector Division, K00000, K90000, constant value
BA East Coast Region, BA East Coast Region, AB0000, ABE000, constant value
Levy Sector Region, Levy Sector Region, K90000, K99000, constant value
Engstrom John RVP, Engstrom John RVP, ABE000, ABE01, constant value
TBA Total ,TBA Total ,K99000, K9901, constant value
1) How do I go about this? I think I have to configure an adapter but which adapter would give me the desired result?
2) How do I tell PI when to pick the file from and where to place it after conversion? Could this be done in adapter configuration?
Any help will be greatly appreciated.
Thanks.
--Mithun>>> 1) How do I go about this? I think I have to configure an adapter but which adapter would give me the desired result?
Use File adapter at the sender side to pick up the xml and use file adapter at the receiver side (message protocol file content conversion) to convert xml format to csv.
Basically you have to configure in the file adapter (FCC) on the receiver side to get desired csv structure from XML.
>>> 2) How do I tell PI when to pick the file from and where to place it after conversion? Could this be done in adapter configuration?
Configure sender file adapter to pick up the file from the specified directory. Configure receiver file (fcc adapter) to drop the csv file after conversion.
For sender adapter
http://help.sap.com/saphelp_nw04/helpdata/en/e3/94007075cae04f930cc4c034e411e1/content.htm
For receiver adapter in our case FCC (FILE content Conversion) follow the link
http://help.sap.com/saphelp_NW04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
Hope answered your question.
Mapping area: simple suggestion. Keep input and output message same structure and do one to one mapping. In the receiver fcc adapter configure for csv structure following instruction given in the above second link
Note: FCC adapter does not support nested structure more than 2. So in your case you can achieve using conversion agent tool. Otherwise you might have to achieve through some graphical mapping. -
How to convert hierarchy XML to CSV/Excel format using PI/XI
posted in PI forum but not many replies, please bear with me as I am in crunch time*
Hi All,
I am working with SAP PI/XI for the first time and need some help file conversion of complex hierarchy XML to CSV file using PI. I have done plenty of research on SDN and could find much related to what I want to do.
Here is the example of how my input XML would look like:
<?xml version="1.0" encoding="UTF-8"?>
<PartyMaster type="OrgHierarchy" name="Compass Group Owned">
<PartyMasterHierarchy>
<Hierarchy level="3" nodeName="Bon Appetit Sector" type="Sector" ID="A00000" refID="A00000">
<Hierarchy level="4" nodeName="BA Division" type="Division" ID="AB0000" refID="AB0000" >
<Hierarchy level="5" nodeName="BA East Coast Region" type="Region" ID="ABE000" refID="ABE000">
<Hierarchy level="6" nodeName="Engstrom, John RVP" type="District" ID="ABE01" refID="ABE01" >
</Hierarchy>
</Hierarchy>
</Hierarchy>
</Hierarchy>
<Hierarchy level="3" nodeName="Levy Sector" type="Sector" ID="K00000" refID="K00000".
<Hierarchy level="4" nodeName="Levy Sector Division" type="Division" ID="K90000" refID="K90000">
<Hierarchy level="5" nodeName="Levy Sector Region" type="Region" ID="K99000" refID="K99000">
<Hierarchy level="6" nodeName="TBA Total" type="District" ID="K9901" refID="K9901"> </Hierarchy>
</Hierarchy>
</Hierarchy>
</Hierarchy>
</PartyMasterHierarchy>
</PartyMaster>
I would like to get CSV output in the format below
DISPLAY_NAME, DOCUMENT_DESCRIPTION, PARENT, EXTERNAL_ID, ORG_UNIT_TYPE
Bon Appetit Sector, Bon Appetit Sector,constant value, A00000, constant value
Levy Sector, Levy Sector, constant value, K00000, constant value
BA Division, BA Division, A00000, AB0000, constant value
Levy Sector Division, Levy Sector Division, K00000, K90000, constant value
BA East Coast Region, BA East Coast Region, AB0000, ABE000, constant value
Levy Sector Region, Levy Sector Region, K90000, K99000, constant value
Engstrom John RVP, Engstrom John RVP, ABE000, ABE01, constant value
TBA Total ,TBA Total ,K99000, K9901, constant value
1) How do I go about this? I think I have to configure an adapter but which adapter would give me the desired result?
2) How do I tell PI when to pick the file from and where to place it after conversion? Could this be done in adapter configuration?
Any help will be greatly appreciated.
Thanks.
--MithunHi Mithun,
You might try this step below :
1. As for xsd schema fo the xml or create xsd schema base on the sample xml file using tools like xmlspy or others free tools.
2. import you xsd schema as outbound Data type
3. apply mapping from source to target (csv).
Configuration
Sender file adapter (without content conversion)
Receiver file adapter (with content conversion).
so the sender adapter will be monitoring inbound directory and write the result to another directory.
Thank You and Best Regards
Fernand. -
XML deployment descriptor generation
How to let OC4J automatically generate ejb-jar.xml, orion-ejb-jar.xml, web.xml for me? It is a nightmare to write these deployment descriptor by hand.
By the way, I know that JDeveloper can generate this for us, but I am not using JDeveloper 9i. Can we just let OC4J generate these files for us?
Thanks.How to let OC4J automatically generate ejb-jar.xml, orion-ejb-jar.xml, web.xml for me? It is a nightmare to write these deployment descriptor by hand.
By the way, I know that JDeveloper can generate this for us, but I am not using JDeveloper 9i. Can we just let OC4J generate these files for us?
Thanks. Hi,
there is no way (so far as I know) that an J2EE Application server (what oc4j is) makes the deployment descriptors, that's why they are called deployment descriptors, without them you can't deploy on any Application server.
I personally use JDeveloper, but most current JAVA IDE's support generation of deployment descriptors.
Basically my approach is to define the architecture within Rational Rose, which generates for me the stubs for the classes and for every ejb a deployment descriptor, later I copy all of them into one ejb-jar.xml and open the whole bunch with JDeveloper, it works fine with 903 preview, although there are some problems with the 902 version of JDeveloper.
Which IDE are you using?
--hery -
Advantages and Disadvantages of XML over CSV
Hi friends,
We have a requirement in our implimentation project. We are implimenting HR module. The company is using SABA for Education and Certification.
We are implimenting Education and certification in BW and the data for BW will be comming from SABA.
We had a discussion on thursday about the integration of SABA to BW. We can do it through DBconnect or by using XI and for this there is time and cost involved.
The techical team has come with some idea where there will give the data in the form of XML or in CSV format.
I would like to know the advantages and disadvantages of each and also please consider the performance point in view.
I would also like to know about the things that need to be considered if we process the data in multiple files.
Please give me inputs and the answers will be appreciated with valuable points.
Regards
Raghav ReddyHi,
my advice is to go for CSV anytime compared to XML.
XML is first made available to the BW system via SOAP ( Simple Object Acess protocol) interface. Next it is updated into the required data targets as before , Via a data source for the myself source system.
SOAP = XML+HTTP.
XML cannot be used for mass data. It is only to load small data into SAP BW on a single document level.
BW provides flat file interface so, there is no all these hassles in case of CSV. go for CSV -
How to convert hierarchy XML to CSV format using PI/XI
Hi All,
I am working with SAP PI/XI for the first time and need some help file conversion of complex hierarchy XML to CSV file using PI. I have done plenty of research on SDN and could find much related to what I want to do.
Here is the example of how my input XML would look like:
<?xml version="1.0" encoding="UTF-8"?>
<PartyMaster type="OrgHierarchy" name="Compass Group Owned">
<PartyMasterHierarchy>
<Hierarchy level="3" nodeName="Bon Appetit Sector" type="Sector" ID="A00000" refID="A00000">
<Hierarchy level="4" nodeName="BA Division" type="Division" ID="AB0000" refID="AB0000" > <Hierarchy level="5" nodeName="BA East Coast Region" type="Region" ID="ABE000" refID="ABE000">
<Hierarchy level="6" nodeName="Engstrom, John RVP" type="District" ID="ABE01" refID="ABE01" >
</Hierarchy>
</Hierarchy>
</Hierarchy>
</Hierarchy>
<Hierarchy level="3" nodeName="Levy Sector" type="Sector" ID="K00000" refID="K00000". <Hierarchy level="4" nodeName="Levy Sector Division" type="Division" ID="K90000" refID="K90000"> <Hierarchy level="5" nodeName="Levy Sector Region" type="Region" ID="K99000" refID="K99000"> <Hierarchy level="6" nodeName="TBA Total" type="District" ID="K9901" refID="K9901"> </Hierarchy>
</Hierarchy>
</Hierarchy>
</Hierarchy>
</PartyMasterHierarchy>
</PartyMaster>
I would like to get CSV output in the format below
*DISPLAY_NAME DOCUMENT_DESCRIPTION PARENT EXTERNAL_ID ORG_UNIT_TYPE*
Bon Appetit Sector Bon Appetit Sector constant value A00000 constant value
Levy Sector Levy Sector constant value K00000 constant value
BA Division BA Division A00000 AB0000 constant value
Levy Sector Division Levy Sector Division K00000 K90000 constant value
BA East Coast Region BA East Coast Region AB0000 ABE000 constant value
Levy Sector Region Levy Sector Region K90000 K99000 constant value
Engstrom, John RVP Engstrom, John RVP ABE000 ABE01 constant value
TBA Total TBA Total K99000 K9901 constant value
1) How do I go about this? I think I have to configure an adapter but which adapter would give me the desired result?
2) How do I tell PI when to pick the file from and where to place it after conversion? Could this be done in adapter configuration?
Any help will be greatly appreciated.
Thanks.
--MithunMithun,
you would get lot of answers if you looking in the PI (process integration forum)... There is something calles File content coversion in XI file adapter (which can convert the xml to csv and viceversa) -
How to ignore prefix from XML while converting XML to csv using XSLT
Hi All,
I am trying to convert XML to csv file.
the XML i have is like....
<?xml version="1.0"?>
<bulkCmConfigDataFile xmlns:es="SpecificAttributes.3.0.xsd" xmlns:un="utranNrm.xsd" xmlns:xn="genericNrm.xsd" xmlns:gn="geranNrm.xsd" xmlns="configData.xsd">
<configData dnPrefix="Undefined">
<xn:SubNetwork id="AU_R">
<xn:SubNetwork id="H5RG_0501">
<xn:MeContext id="Firle_5070020">
<xn:ManagedElement id="1">
<un:RncFunction id="1">
<un:UtranCell id="50390303">
<un:attributes>
<un:userLabel>UtranCell 50390303</un:userLabel>
<un:cId>52383</un:cId>
<un:localCellId>50390303</un:localCellId>
<un:uarfcnUl>9613</un:uarfcnUl>
<un:uarfcnDl>10563</un:uarfcnDl>
<un:primaryScramblingCode>502</un:primaryScramblingCode>
<un:primaryCpichPower>287</un:primaryCpichPower>
<un:maximumTransmissionPower>403</un:maximumTransmissionPower>
<un:primarySchPower>-18</un:primarySchPower>
<un:secondarySchPower>-20</un:secondarySchPower>
<un:bchPower>-20</un:bchPower>
<un:lac>50301</un:lac>
<un:rac>1</un:rac>
<un:sac>52383</un:sac>
<un:utranCellIubLink>SubNetwork=AU_R,SubNetwork=H5RG_0501,MeContext=H5RG_0501,ManagedElement=1,RncFunction=1,IubLink=5039030</un:utranCellIubLink>
</un:attributes>
</un:UtranCell>
</un:RncFunction>
</xn:ManagedElement>
</xn:MeContext>
</xn:SubNetwork>
</xn:SubNetwork>
</configData>
</bulkCmConfigDataFile>now when i am using XSLT functionality to convert this XML into a csv i want ignore all the prefix from this xml like "un" , "xn" etc....
can anybody has idea how i can ignore all this value using XSLTI just dont understand why factory.setIgnoringElementContentWhitespace(true) did not work.That only does something if the XML has a DTD that enables it to know what whitespace can be ignored and what is significant. The API documentation for the method refers you to this document:
http://www.w3.org/TR/REC-xml#sec-white-space
Maybe you are looking for
-
Playback has no theme/menus/chapters.etc.
Hi all, I want my iDVD projects to start just like a DVD movie with theme and menus. I was successful in creating a DVD of my imovie with markers and title but on playback time my DVD player started the movie without showing the theme and menus at be
-
Hey everybody. I just upgraded to leopard, and all the features are very nice, I love it. When I used tiger I used Fn+Backspace in finder to move files to trash, this doesn't work anymore. Though Fn+Backspace works as a forward delete key whilst text
-
Hi MDM Experts, I have a situation over here wherein I am trying to use the Automatic Import for a XML file through an XML Schema. XMl Xchema and the port have been mentioned in the port settings. Everything else has also been configured. But when I
-
Why does Canon NOT support the Canon Utilities software?
The Canon Map Utility software can not detect my Canon GPS Receiver GP-E2. Over the phone, Canon "Customer Support" had me uninstall all 10 Canon Utilities that I had previously installed, and then let me install only 8 older versions of Canon Utili
-
Activity not transported to Assembly
Hi Experts , I import the change to consolidation but after I donu2019t find it to assemble. Donu2019t know where the change goes . We checked in Consolidation History its there. Kindly suggest how to proceed. Regards, Prasanna Kumar.S