XML for Forced Return
I use XSLT to create XML documents to be opened in FrameMaker and converted to structured documents. I have one element (called SyntaxPara) in which I'd like multiple lines separated by forced returns, as indicated by "{" symbol in the document (or \r in the Find/Change dialog). Anybody know what the XML coding would be to specify a forced return? I cannot seem to nail it down. I need to do this because my structured template is supporting styles used with unstructured FrameMaker, and that happens to be how they're doing it. Thanks,
John,
I do not know what the Kosher XML method is, but you can define an element in your EDD, say Break, which has no content or attributes. The EDD defines its formatting as character formatting and a prefix or suffix that is the return character, namely \r. Note that this requires an update to your EDD. Your XSLT would then translate the XML object that indicates a break into the element Break.
Van
Similar Messages
-
Forced return, non-breaking hyphens & spaces, suppress hyphenation + XML
Forced return (linefeed), non-breaking hyphens and spaces, suppress hyphenation.
None of these are preserved when exporting from FrameMaker to XML, since they do not seem to be represented by a Unicode code point. My question to you is: How do you deal with those things in XML?
The last issues (non-breaking and suppress hyphen) have recently been brought up in:
http://forums.adobe.com/thread/450363
http://forums.adobe.com/thread/459503
Forced return is a common thing in many FrameMaker documents to improve readability of certain phrases.
For export of FM to XML, there have been proposals to use a special element with a prefix just to capture the special FrameMaker symbol. It works, and may be a valid useful path in certain cases, but I think that it is a questionable way of dealing with it for several reasons:
It is only relevant for roundtrip, since these special elements will hardly be interpreted by other XML tools, which of course limits the value of XML export.
It is unwieldy, to say the least, to require the user to insert special elements for saying simple things that otherwise are just natural key strokes in the regular text flow, and which are not perceived as structural elements of information. Most users would think of these symbols/charactes as control characters, and there is no validation warning that says you may not use these characters/symbols.
An element is used for formatting purposes only, whereas all other elements are used for content or structure.
There is no automatic way of transforming an existing text that has these "symbols" into some special element when a document is structured with a conversion table.
There is no automatic way of transforming a structured FM document to XML such that these special "symbols" get translated to some suitable XML construct.
If the last point could be solved, i.e if all those control characters or markers could automatically be translated to a suitable XML representation, then I would consider the whole issue as solved, otherwise not.
Even without FrameMaker, how do people deal with these things in "pure xml". For instance, when XML is used for publishing (which I know Arnis Gubins is doing), there will guaranteed be a need to control both hyphenation and line breaks. So how do you (they) do that?
How do other vendors cope with these issues, e.g XPP?Lynne,
As anyone can see, entity declarations have not really been in the domain of my expertise (understatement), but I might just learn bits and pieces...
Thanks! I have now done some more reading in various pdfs, such as scructapps etc, but also the w3c xml spec, all of which I have "read" before, but reading is not always the same as understanding...
I now have used the "entity approach" to make both discretionary hyphen and suppress hyphen work, so that it is represented in the XML export and round-trips just fine.
Forced return still puzzles me somewhat though: I have a working solution for that using the same entity approach, but it will not work for text ranges (although it is a bit odd to have forced returns in text range elements). Moreover, I am not certain that it really is the best way. In reading other posts on this issue, I have seen that some people want forced returns to really be linefeeds in the xml output, with no other linefeeds, and conversely, when importing xml that are "formatted" in lines, such as code, they want to preserve that.
One way to achieve that is to use:
reader line break is forced return;
writer line break is 1000 characters; (or more characters)
Then it is completely symmetric (i.e works also if some other app has generated the xml with intentional line breaks. And this method is global for all elements, and it works for me.
Another way to achieve this is to use the following, but it is only valid inside an element:
preserve line breaks;
writer line break is 1000 characters;
Then it is also completely symmetric (in the above sense), and it works for me.
The latter method has the drawback that it only works for text in the element; it is not inherited to its children.
But if we look at only one element, what is the difference between the two methods?
As far as I have been able to see, the results are identical! Why two methods? The first one seems more powerful and general(?)
Scrutinizing the documentation though, it says that 'preserve line breaks' will add an attribute 'xml:space', but I can't see that in my output?
Also, concerning the documentation for line break, it says that FM would ignore line breaks when exporting, but it does NOT do that (fortunately). Forced returns always result in linefeeds, no matter what.
I would be thankful if these issues could be explained, or elaborated.
Also, would you recommend against any of these methods?
With my preferred method of using the global 'reader line break is forced return' instead of a local (or many local) 'preserve line breaks', there is of course the danger that when importing xml, it is absolutely necessary that the xml really only has line breaks where they are intended, and not generated every 80 characters or so!
Is there anything that says it is "ugly" or "bad style" to honor line breaks, and generate long lines?
Finally, why do we need to limit the number of characters written in one line these days? Why 80, why 1000, why not an unlimited number of characters!?
Will software these days really crash if given a very long line (assuming that it doesn't exceed total ram memory of course)?
Sorry about so many questions, but I can't find any answers to them in the docs I have read and searched. -
How to control the force return in table cell data?
I have some xml format files.When I import them into FrameMaker,They display as table data.but when the data is very long in table cell,I want to control the new line by myself.for example,I add some \r\n in my xml file data,then in FrameMaker,It can identify the \r\n, force return.In framemaker I don't know the actual symbol that means the newline.How Can I deal with the problem?thank you!
Hi Russ,
yes, but you have to agree that forcing a return in the SOURCE content is really not a wise thing to do - It would be better to break the content into multiple paragraphs or used an XSLT to determine the column width and insert your own breaks in a version of the XML for rendering in Frame. If, at a later date, your templates in Frame change to allow wider columns in your table, then you'd have to go back into the source code and change every occurrence of the c/r in the data - Yeuch! Better to transform the data once, before importing into Frame and then if the col-width changes it is a simple task to change the width in the XSLT - personally, I would make sure the EDD and DTD allows multi-lines in the table cell and then break-up the data to fit the table cell size in an XSLT before importing. Then you don't taint your source code...and it is quite easy to do this is an XSLT... -
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!" -
Hello, Does anyone know how I can sync my BBZ10 with my computers Outlook Calendar and Contacts? It was working but since my computer returned from being repaired it doesn't sync and gives me the following message
"Device Pin not set in TransConfig.xml.for translator RimBB"I did resolve it, it was so long ago but here's what I suggest:
-First remove the software on your computer by going to the add/remove programs if you're using a PC. If you're using Mac, I'm not sure where you go.
-Then go to BB website and download the correct program for you phone
-Check both your phone and computer have all their updates
With the newest updates I have no trouble syncing my calendar/contacts from my PC to my BB and vice versa. It was just initially when the BB was so new they hadn't updated the programs. Over time the fixed the glitch, this is why I recommend you remove the program you have and start over, it will probably fix itself. -
Looking for raw SOAP XML for Data Card requests
We are neither a .NET nor JAVA programming shop, but the code samples I find are.
And so, we are looking for the raw SOAP XML for calls surrounding entity type DataCardSet. In particular, we want to retrieve a list of them, and then for a particular one, retrieve/describe its available field details.Hi Corey,
I've included SOAP messages below for requests to list and describe DataCardSets in your Eloqua install.
The following SOAP XML call will return a list of all DataCardSets :
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<s:Header>
<VsDebuggerCausalityData xmlns="http://schemas.microsoft.com/vstudio/diagnostics/servicemodelsink">uIDPo6MkWEPC3S5OmHaW8t1VC/kAAAAAI03BGdV8TkmUW00g2vOgE7r/OByVYmdPgXikgEI8ZRsACQAA</VsDebuggerCausalityData>
<o:Security s:mustUnderstand="1" xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<u:Timestamp u:Id="_0">
<u:Created>2013-01-31T13:32:51.750Z</u:Created>
<u:Expires>2013-01-31T13:37:51.750Z</u:Expires>
</u:Timestamp>
<o:UsernameToken u:Id="uuid-43493015-758b-4f34-837f-820c8f2b044c-1">
<o:Username>Company\UserName</o:Username>
<o:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">Password</o:Password>
</o:UsernameToken>
</o:Security>
</s:Header>
<s:Body>
<DescribeEntityType xmlns="https://secure.eloqua.com/API/1.2">
<globalEntityType>DataCardSet</globalEntityType>
</DescribeEntityType>
</s:Body>
</s:Envelope>
The following request will describe the metadata (including custom fields) on your DataCardSet :
(assuming the ID of the DataCardSet is 95)
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<s:Header>
<VsDebuggerCausalityData xmlns="http://schemas.microsoft.com/vstudio/diagnostics/servicemodelsink">uIDPowA6KT+197BLtB+NzsSc1yYAAAAAeE8D6Q/LUUyO4p5XUfsdQf9zTkkCGRRKuRBcBkjafZcACQAA</VsDebuggerCausalityData>
<o:Security s:mustUnderstand="1" xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<u:Timestamp u:Id="_0">
<u:Created>2013-01-31T13:35:40.433Z</u:Created>
<u:Expires>2013-01-31T13:40:40.433Z</u:Expires>
</u:Timestamp>
<o:UsernameToken u:Id="uuid-4f57be51-7af1-4d91-9f98-f1919f587117-1">
<o:Username>Company\UserName</o:Username>
<o:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">Password</o:Password>
</o:UsernameToken>
</o:Security>
</s:Header>
<s:Body>
<DescribeEntity xmlns="https://secure.eloqua.com/API/1.2">
<entityType xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
<ID>95</ID>
<Name i:nil="true"/>
<Type>DataCardSet</Type>
</entityType>
</DescribeEntity>
</s:Body>
</s:Envelope>
Thanks,
Fred -
SAP J2EE Engine JTA Transaction Xml for table TABLE could not be ana
I'm having a weird case. I created 3 entity bean. In my R/3 will call this JCO.Function to do the insert to database. But out of 3 entity bean, only 1 entity bean got error where it unable to insert to database and have this error in the log.
The case is quite weird where i created the same entity but only 1 entity is not working as expected. Wondering what cause this problem.
Thanks.
org.xml.sax.SAXException: Fatal Error: URI=:main: Line=1: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Name expected: 0x20(:main:, row:1, col:218)#
at com.sap.dictionary.database.dbs.XmlExtractor$XMLErrorHandler.fatalError(XmlExtractor.java:279)#
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144)#
at com.sap.dictionary.database.dbs.XmlExtractor.map(XmlExtractor.java:130)#
at com.sap.dictionary.database.catalog.DbGeneralStructure.<init>(DbGeneralStructure.java:86)#
at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:90)#
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)#
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)#
at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)#
at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)#
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)#
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)#
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)#
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)#
at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)#
at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)#
at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)#
at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)#
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)#
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)#
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)#
at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)#
at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)#
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)#
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)#
at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)#
at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)#
at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)#
at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)#
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)#
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)#
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)#
at java.lang.reflect.Method.invoke(Method.java:324)#
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)#
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)#
at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)#
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
at java.security.AccessController.doPrivileged(Native Method)#
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)#
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)#
##0#0#Error##Java###{0}.commit(), Cannot commit due to unexpected exception in beforeCompletion():
[EXCEPTION]
{1}#2#SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b]#java.lang.IllegalStateException: Xml for table <TABLE> could not be analysed
at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:100)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)
at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)
at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)
at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)
at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)
at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)
at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)
at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)
at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)
at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5 #001A6467CDF400590000004E000018D8000459BB785F496C#1224561620123#com.sap.engine.services.ts#sap.com/ESolutionsEGatewayEAR#com.sap.engine.services.ts#J2EE_GUEST#0####95b74d409f2411dd86c4001a6467cdf4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error#1#/System/Server#Java#ts_0004##Exception in beforeCompletition of ( SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b] ).#1#SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b]#
#1.5 #001A6467CDF400590000004F000018D8000459BB785F4BC5#1224561620123#com.sap.engine.services.ts#sap.com/ESolutionsEGatewayEAR#com.sap.engine.services.ts#J2EE_GUEST#0####95b74d409f2411dd86c4001a6467cdf4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error#1#/System/Audit#Java###Exception {0}#1#com.sap.engine.services.ts.exceptions.BaseRollbackException: Exception in beforeCompletition of ( SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b] ).
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:236)
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)
at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)
at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)
at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)
at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)
at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.lang.IllegalStateException: Xml for table ZREASON_CODE could not be analysed
at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:100)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)
at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)
at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)
at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)
at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)
... 16 more
#1.5 #001A6467CDF4005900000050000018D8000459BB785F4E8F#1224561620123#com.sap.engine.services.ejb.entity.Container#sap.com/ESolutionsEGatewayEAR#com.sap.engine.services.ejb.entity.Container#J2EE_GUEST#0####95b74d409f2411dd86c4001a6467cdf4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Java###null
[EXCEPTION]
{0}#1#com.sap.engine.services.ejb.exceptions.BaseRemoteException: Transaction system failure in method net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(net.tnb.model.ReasonCodeBean).
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:573)
at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)
at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)
at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)
at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)
at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.ts.exceptions.BaseRollbackException: Exception in beforeCompletition of ( SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b] ).
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:236)
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)
... 15 more
Caused by: java.lang.IllegalStateException: Xml for table ZREASON_CODE could not be analysed
at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:100)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)
at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)
at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)
at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)
at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)
... 16 more
#1.5 #001A6467CDF4005900000051000018D8000459BB785F5FA9#1224561620123#System.err#sap.com/ESolutionsEGatewayEAR#System.err#J2EE_GUEST#0####95b74d409f2411dd86c4001a6467cdf4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###RemoteException insertOk=false#
#1.5 #001A6467CDF4005900000052000018D8000459BB785F6094#1224561620123#System.err#sap.com/ESolutionsEGatewayEAR#System.err#J2EE_GUEST#0####95b74d409f2411dd86c4001a6467cdf4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###Tue Oct 21 12:00:20 SGT 2008 java.rmi.RemoteException: com.sap.engine.services.ejb.exceptions.BaseRemoteException: Transaction system failure in method net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(net.tnb.model.ReasonCodeBean).
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:573)
at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)
at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)
at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)
at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)
at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.ts.exceptions.BaseRollbackException: Exception in beforeCompletition of ( SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b] ).
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:236)
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)
... 15 more
Caused by: java.lang.IllegalStateException: Xml for table <TABLE> could not be analysed
at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:100)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)
at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)
at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)
at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)
at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)
... 16 more
; nested exception is:
javax.transaction.RollbackException: com.sap.engine.services.ts.exceptions.BaseRollbackException: Exception in beforeCompletition of ( SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b] ).
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:236)
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)
at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)
at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)
at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)
at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)
at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.lang.IllegalStateException: Xml for table ZREASON_CODE could not be analysed
at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:100)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)
at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)
at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)
at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)
at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)
... 16 moreHi Stefan and Everyone,
I have solved my problem. Just want to let everyone know if u have to install the SP's for WEB AS 6.30/6.40.
You start from the installation from CD 6.30/6.40. Everything will be working at this point. You can login to Visual Admin, Config tool and SDM.
Before you apply any SP's, do the following:
a) Create an emergency user with the Administrator rights: Ref OSS Note:669848
Try to follow this route for SP's:
From CD 6.30/6.40 -> SP04 -> SP07
Apply SP04 first before applying SP07 (Recommended Approach).
Refer the installation guide: SAP Web AS Support Package Guide 630SP2 to 640SP4.
Use JDK1.4.2_05 to install SP04. You must reference the following OSS Notes and apply to your system accordingly, this is the key to an error free installation:
a) OSS Note: 697535
b) OSS Note: 709140
c) OSS Note: 716604
d) OSS Note: 706378
You have to be really careful with SP04 installation, because it changes the version from 6.30 -> 6.40.
Once you are able to install SP04 without any problems, you can directly apply SP07 or the highest 6.40 SP.
Kind Regards,
Buddha. -
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> -
Specifying coherence-cache-config.xml for multiple clusters
Hi,
I am running two cache clusters (Cluster A and B that hold different cache types). we have a web application that needs to communicate with both the clusters. we have two coherence-cache-config-g.xml files, one for each cluster.
where do we specify the two coherence-cache-config.xml for each of these clusters in our coherence.jar that we deploy on the web app server.
pls provide some inputs...
thanks in advance,
- G.Hi G,
You can define a path to the cache configuration descriptor in your operation configuration override file (tangosol-coherence=override.xml) or specify it in the system property "tangosol.coherence.cacheconfig".
Please see this Wiki page for details:
http://wiki.tangosol.com/display/COH32UG/configurable-cache-factory-config
Regards,
Gene -
VA00 condition type not getting determined for the returns order
Hi All,
I have a case where VA00 condition type not getting determined for the returns order that has been created with respect to the billing document.
When the pricing conditions are being copied from invoice it is getting copied but later it is getting deleted in the include LV61AA42.
Note:VA00 condition type is getting deleted from the internal table tkomv[].
If any one came across this scenario can you please help me.
Request your valuable inputsHi,
Please check the copy control setting in VTAA.
Maintain the pricing type as "D" at item category level for the respective document type .
Hope this will resolve your issue.
Regards,
Krishna O -
For Customer return, other adjustemnet or Add. excise required ?
Hi All,
While my customer return the finished goods I am making sales return order ,did the PGR & make the credit note.
Now I want to adjust the excise duty through J1IH
In j1ih which option I have to choose <other adjustemnet> or <Add. excise>
In Add. Excise tab. the Gl account detremine are :
C 0013113920 115.00 CENVAT clearing
D 0024822000 5.00 CENVAT Input SECess
D 0024820000 100.00 CENVAT Input BED
D 0024821000 10.00 CENVAT Input ECess
Whereas In case of Other adjustment tab GL account determine are
C 0024822000 5.00 CENVAT Input SECess
C 0024820000 100.00 CENVAT Input BED
C 0024821000 10.00 CENVAT Input ECess
D 0013113920 115.00 CENVAT clearing
Please suggest me which option is correct.......Other adj or Add excise tab.
In my opinion it should be <Add. Excise> where Clearing account is credited and all rest debited.
Please Give me the solution
Regards
SAGARDear Lakshmipathi,
As directed by you I did & come to know that it's triggering MRDY EX TT if I go through J1Ih < Other Adjustment>.
So now I Created one Sub Transaction Type -
CR - Customer Return.
& in Specify Excise Accounts per Excise Transaction I Maintain
MRDY CR Credit Cenvat Suspence Account
MRDY CR Debit RG 23 BED Account
MRDY CR Debit RG 23 ECS Account
MRDY CR Debit RG 23 At1 Account
& maintained thier GL's.
Checked in
Is this right for Customer Returns????
Regards
SAGAR -
Goods Issue for a Return Outbound Delivery for both Sales Returns
Hi gurus..
tell me the approch for the following development....
custom transaction to perform a Goods Issue for a Return Outbound Delivery for both Sales Returns and Consignment Returns (Pickups) process within a lean warehouse in SAP.
it is vry urgnt
thnksI seem to have found the information I required here:
http://wiki.sdn.sap.com/wiki/display/Snippets/Simulating+the+Sales+Cycle+with+BAPI's
I'm going to keep this post active because I'd still like answers to my questions and any advice that you might be willing to share in regards to what I am trying to do.
Edited by: Mikael Nensén on May 18, 2011 3:52 PM -
Issue of Quality Inspection for consignment return delivery
Hello,
I am doing a returns delivery(from a Sales Order) from a Customer Consignment.
I am getting a error when I do a Post Goods Receipt(PGI). QM is active for that material.
The error I am getting is
"Change the inspection stock of material XXX in QM only"
Procedure says
"Check both the QM inspection setup data and the movement type for material XXX in the quality management view of the material master"
The movement type used in the returns delivery is 655(GD returns for QI).
What is the solution for this error. Do I need to change/add new Inspection type based on the Movement type?
Please let me know ASAP.
Thanks
Regards
SAP Fan..Hi,
You can read this link for inspection for customer return [Inspection for customer return|http://help.sap.com/saphelp_47x200/helpdata/en/92/b808b1d52a11d2962200a0c930e04c/frameset.htm]
It looks the material master is set-up inspection type with 06 - returns from customer. Also the movement type 655 moves the goods into QI stock. In this case, the Quality personnel needs to change the inspection stock type using transaction code QA32. They will change the usage decision on the customer returns.
Once the change the inspection type is changed, you can do the post goods receipt.
Regards -
Accounting entries for excise invoice for purchase returns in J1IS
Dear Friends
1) I recorded an excise invoice for goods receips in J1IEX . The accounting entry is
Input BED a/c DR
Input ECS a/c DR
Input H.css A/c DR
CENVAT clearing CR
2) There were some damaged items and same returned to vendor. I did RETURN Delivery in MIGO. The excise invoice in J1IS gives error " BALANCE IN TRANSACTION CURRENCY". Here I used Ref document type - MATD
QUESTION :
What is the Excise transaction type for ' other outward movement' in J1IS to which I should assign the excise accounts to reverse (1) above. Is it OTHR or GPRO.
Thanks
kamalaDear Mathews,
It is not capital goods. Also if I do a JV in J1IH, the entry goes and is as below :
Cenvat clrg DR, Input -BED /E.cess/ S.cess CR
But J1IS does not save, though I have assigned all said accounts in 'Excise accts per excise transation' for OTHR. Also I read in wiki that the entry for purchase return excise inv in J1IS is ' CENV CLRG ....DR , CENV RECEIVABLE ...CR ' .If so, then do i creat new GL for Cenv Receivable ? What is its effect on FORTNIGHTLY UTILIZATION
thanks for telling
kamala
Edited by: Kamala Surianarayanan on Mar 6, 2009 6:38 AM
Edited by: Kamala Surianarayanan on Mar 6, 2009 6:38 AM -
Sales Order Stock (For Repair Returns) - Valuated & Non-Valuated
Greetings All,
We are currently using sales order stock as quantity only for customer returns for repair (RMA Sales Order). As long as we do not give a credit to our customer, this is working. My problem is that some of our customers are requesting credit... This requires that the inventory now be valuated. I want to keep the link with the sales order (RMA). Is there a way to do this?
Thanks for reading!Thanks for your quick response Ajay.
I am aware that I can move it to unrestricted stock but I would lose my link to the RMA sales order. Correct?
We currently are not using split valuation.
Any other suggestions?
Maybe you are looking for
-
I have powerpoint for Mac on my imac. I can't seem to get the active text box function to work like it did on my PC. How can I insert an active textbox into a presentation that will allow me to type while presenting?
-
I created an ESB flow that uses a file adapter service to read a simple xml file in and map required data to a Soap service. I was forced to map all fields for the input to the soap service, either by "hard coding" values in the xsl or modifying the
-
ThinkPad buttons do not function (T430s)
Hello, I just received a new T430s and the buttons below the TouchPad do not function at all. A clean Win7 Enterprise installation was performed as soon as the laptop was received, so I cannot verify if the buttons previously worked. I have upgraded
-
When I typed in Christmas, it was underlined in red. Which means that it wasn't in the dictionary. When I right-clicked on it, there were no spelling suggestions and I had to add it to the dictionary myself. Christmas is a word and as far as I know,
-
How can I use my free trial?
The photoshop 1 month free trial I downloaded will not let you utilize the program, all it lets you do is view a tutorial. I would like to use photoshop to see if I am able to use it and if it is easy for beginners before I make a purchase. Thanks