Adding XML Declaration and Document Type Declaration.

I'm using Oracle's XML Class Generator C++ version 1.0.2.0.0. I can create classes from a defined external DTD and create my XML document. But the document does not contain the XML Declaration <?xml version='1.0?> nor does it contain the Document Type Declaration <!DOCTYPE root-element-name SYSTEM "system-identifier">. What do I need to do to get these as part of my XML document? Does the class generator have methods to do this? Could someone show me an example?

If you invoke the print method on the top-level ELEMENT, you get
just the body of the document with no DTD or XMLDecl. if you invoke
print on the top level NODE (the DOCUMENT node), then the output
document will contain the XMLDecl and DTD.
So please try to print from DOCUMENT node.

Similar Messages

How to set Document Type Declaration of xml Document?

Hi,
I am referring to "org.w3c.dom.Document".
How can we set the Document Type Declaration (DTD) of a document?
Thanks.

Hi,
But when we have to create a document(org.w3c.dom.Document) dynamically, and that document has to be validated against a DTD......How can we do it?
I am using the following code
DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
DocumentBuilder builder = factory.newDocumentBuilder();
DOMImplementation domi = builder.getDOMImplementation();
DocumentType docType = domi.createDocumentType("query", null, "c:\\queryDtd.dtd");
Document doc = domi.createDocument(null, "query", docType);But this code is not working. Resulting document is not having <!DOCTYPE...> tag
I have to build a Doument object (not xml file) whose content is as below
<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE query SYSTEM "queryDtd.dtd">
<query id="abc123">
     <data-source-name>EmployeeDB</data-source-name>
     <fields>
                 <field>id</field>
                 <field>name</field>
                 <field>salary</field>
                 <field>joindate</field>
     </fields>
     <fetch-limit>10</fetch-limit>
</query>

Document type declaration for root element type "web-app" must end with ' '

I am attempting to deploy an application (.war file) using the Sun Access Manager Agent installed, (Reference http://docs.sun.com/app/docs/doc/819-3201/6n5eht3k4?a=view -near the bottom) and I get this error:
Error loading deployment descriptors for ajacs Line 3 Column 19 -- The document type declaration for root element type "web-app" must end with '>'.
Here is the relavent code:
<!DOCTYPE web-app version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
<web-app>
<filter>
<filter-name>Agent</filter-name>
<filter-class> com.sun.identity.agents.filter.AmAgentFilter </filter-class>
</filter>
<filter-mapping>
<filter-name>Agent</filter-name>
<url-pattern>/*</url-pattern>
<dispatcher>REQUEST</dispatcher>
<dispatcher>INCLUDE</dispatcher>
<dispatcher>FORWARD</dispatcher>
<dispatcher>ERROR</dispatcher>
</filter-mapping>
<display-name>AJACS</display-name>
<welcome-file-list>
<welcome-file>frameSet.jsp</welcome-file>
</welcome-file-list>
etc...
Now, when I remove the parts that http://docs.sun.com/app/docs/doc/819-3201/6n5eht3k4?a=view said to add, it deploys just like it used to deploy- just fine with no errors. However, I add that code and it breaks.
Note: The code was a straight copy/paste, so if there is any error in the code, it is because it's written incorrectly on the Sun doc website.
Any help would be MUCH appreciated. Thanks!

Well, if that was pasted on one line, it would be:
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
So it's supposed to be that way. I just tried it with the extra quotes, and no dice...

[svn] 3571: Update SWFLoader ASDoc comment to remove &emdash and data type declaration .

Revision: 3571
Author: [email protected]
Date: 2008-10-10 11:07:09 -0700 (Fri, 10 Oct 2008)
Log Message:
Update SWFLoader ASDoc comment to remove &emdash and data type declaration. ASDoc adds that automatically.
Doc the new types in IndexChangedEvent.as
Checkin Test Passed: Yes
QA: No
Bug:
Doc: No
Modified Paths:
flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/SWFLoader.as
flex/sdk/trunk/frameworks/projects/framework/src/mx/events/IndexChangedEvent.as

lunke you shoude change svn update http://svn.foo-projects.org/svn/xfce/modules/trunk to svn up $startdir/src/trunk
hers a PKGBULID for thunar
pkgname=thunar
pkgver=0.0.2.r17470
pkgdesc="Thunar is a file manager designed for Xfce. It is currently under development."
url="http://thunar.xfce.org/wiki/"
depends=('exo-svn')
makedepends=('subversion')
source=()
md5sums=()
build() {
if [ ! -d $startdir/src/thunar ]; then
echo "Fetching sources..."
svn checkout http://svn.foo-projects.org/svn/xfce/thunar/trunk/ /thunar
else
echo "Updating sources..."
svn up $startdir/src/thunar/
fi
cd $startdir/src/thunar
./autogen.sh --prefix=/opt/xfce4-svn
make || return 1
make DESTDIR=$startdir/pkg install
find $startdir/pkg -name '*.la' -exec rm {} ;
you will need exo from svn as well
pkgname=exo-svn
pkgver=r17470
pkgdesc="Extensions to Xfce by os-cillation"
url="http://libexo.os-cillation.com/"
conflicts=(exo)
provides=(exo)
depends=('xfce4-svn')
makedepends=('subversion')
source=()
md5sums=()
build() {
if [ ! -d $startdir/src/trunk ]; then
echo "Fetching sources..."
svn checkout http://svn.foo-projects.org/svn/xfce/libexo/trunk/
else
echo "Updating sources..."
svn up $startdir/src/trunk
fi
cd $startdir/src/trunk
./autogen.sh --prefix=/opt/xfce4-svn
make || return 1
make DESTDIR=$startdir/pkg install
find $startdir/pkg -name '*.la' -exec rm {} ;
"Operation libtool-slay" compliant

Posting Key and Document type

Hello,
I have just detected an inconsistency in one of my SAP environment (Development). I have an invoice posted from the SD module, document type of this invoice is RV.
If there is a reason to cancell this invoice, the transaction used is VF11. The document type in SD for this cancellation is S1. Thereafter an FI document is generated with document type AB.
Even though the settings in both Production and Acceptance and Developement are the same.
I have realised that the initial document when cancelled (reversed) has an FI document RV and posting key 11. whiles in customizing the settings for posting keys and document types are different from what has been customized. Below is my current settings.
The posting key 01 has a reversed posting key 12 and the document type RV has a reverse document type AB. This customizing is in correct in SPRO.
Transactions : OB41 and OBA7
Can anyone help on this....
Thanks
Elvis

Hello,
Did you verify whether AB document type in OBA7 is marked in "Account Types allowed" the Customer checkbox?
If not, maybe that is why it is not selecting AB as the reversal document type for RV, even though it is set up in RV document the AB document type as reverse document type.
Other than this (if the mentioned above doesn't solve your issue), I would say there should be any user-exit that can be changing the document type, according to some specific business rule of your SAP client or even a substitution.
I hope it helps you.
Regards,
Daniel.

Regarding Delivery and document type

Hi Gurus,
I copied both the delivery type and document type from NL and UB and I also assigned delivery type and checking rule to the supplying plant in SPRO- LE - MM- PUR- PO - set up STO. and also assigned the Document type in SPRO- LE - MM- PUR- PO - set up STO assign doc type, one step....
But when I create the STO the system issues a warning message that
Doc. type YUB should be used for suppl. plant XXXX and receiving plant XXXX
Message no. 06674
can you please give me some suggestions
Shane

Hi narayan,
I am working with INTRA company STO and I have checked with the config what i have did again and now I can get the shipping tab.............. only thing is before I have forgot to assign the Issuing storage location in the transaction process. So now i can create a STO.
Now I am not sure how and where we need to make changes so that the process doesnt ask for Issuing storage location information and still create the STO between two plants in a same company.
Thank you for your responses. They really helped me in figuring where exactly i am going wrong
Shane

SAP Easy DMS - Link between Document Area and Document Types

Deat Friends,
Is there a transaction code or a customizing available to link the Document Area and Document Types??
For example: Document Area (DMS) is linked with Document Type (DRW)
Thank you,
Sri

Hello Chandu,
We are trying to create a documents via TCODE: CVO1N
One of the entry we need to populate is the "DOCUMENT TYPE" to create a document. If, we enter the Document Type = DRW, we are not able to see our custom Storage Category while attaching/Check-in a document.
Where as, If, we enter the Document Type = DMO, we are able to see our custom Storage Category while attaching/Check-in a document.
I see that the Document Type = DRW is linked to Document Area = DMS
Similarly, the Document Type = DMO is linked to Document Area = FILESYSTEM
My question is, Is there a transaction code or a customizing option available to link the Document Area and Document Type?
Thank you,
Sri

Message No delivery type defined for supplying plant BP01 and document type

Hi all,
I am trying to create a purchase order with a BP01 supplier and the BP02 division but I get the following error message No delivery type defined for supplying plant BP01 and document type.
When I create a PO with a BP02 supplier and the BP01 I do not get any message.
How can I fix it ?
Thanks
Regards
Pierre

1)Create one Customer for Supplying Plant Sales area and assign this Customer no with Receiving Plant in OLME---> PO -
> Set up STO -
> define Shipping Data for plants. and maintain the same sales area in your Supplying plant.
2) In OLME---> PO -
> Set up STO.....for your Document Type: UB and Suppying plant Combination assign Del. Type NL and Checking rule RP
3) In OLME---> PO -
> Set up STO...for your Supplying Plant and Receiving Plant combination Maintain Doc. Type : UB
Make sure you are maintaining Sales View for your Material at Supplying Plant.
4) Maintain Shipping point at, SPRO----> Logistics Execution -
> Shipping -
> Basic Shipping Functions -
> Shipping Point Determination for Plants.....there for your Loading group,Shipping Condition, Shipping Plant combination maintain Shipping plant..
Now Create STO in ME21N with Doc.type: UB at Receiving Plant.
Then Create Delivery in VL10B from Supplying Plant...
Then Do PGI in VL02N from supplying Plant.
Then do GR at Receiving Plant based on Outbound Delivery at Receiving Plant...

In PO No delivery type defined for supplying plant and document type MRO

Hi,
i need urgent solution for this problem please.
i am getting this error while creating stock transport order PO(intercompany)
No delivery type defined for supplying plant (ex:1500) and document type MRO .
thanks
madhu

Hi,
i am getting problem in vendor master data
1) recently we started inter company stock transfer order (STO)process for a vendor (delivery plant), the same vendor was using before for internal procurement for some other company code /plant, i made settings in vendor master last screen ie conditions , sales data and control data ,and took path from main menue selected extras-> addtional purchasing data tab to enter plant under plant assignment tab to work STO. now we are unable to create PO for other company and pur org(non STO company code /plant) with the STO vendor,if i remove plant under plant assignment tab in vendor master , it is effecting inter company STO,
i need solution for this , please help me by giving valuable solution.
Thanks and Regards
MM

No delivery type defined for supplying plant 6110 and document type ZSTD

Hi all,
I am trying to create a purchase order with a P6110 supplier and the 6115 plant but I get the following error message No delivery type defined for supplying plant p6110 and document type.
When I create a PO with a 6115 supplier and the 6110 I do not get any message.
How can I fix it ?
Thanks
Regards
SAGAR

>
sagarn wrote:
> Hi all,
>
> I am trying to create a purchase order with a P6110 supplier and the 6115 plant but I get the following error message No delivery type defined for supplying plant p6110 and document type.
>
> When I create a PO with a 6115 supplier and the 6110 I do not get any message.
>
> How can I fix it ?
> Thanks
> Regards
> SAGAR
If ZSTD is a copy of UB type PO, then you need to provide the plant number as the supplier. The delivery type can be configured in the following path
Materials Management -> Purchasing -> Purchase Order -> Set up Stock Transport Order -> Assign Delivery Type and Checking Rule
Copy and existing record and maintain the combination of your PO type (ZSTD), supplying plant (6110) and delivery type (NL). Leave the others the same.
Regards,
Aroop

Error:-No delivery type defined for supplying plant and document type RB

Hi,
Here issue is such that while creating purchase order(Return order type)the error coming as follows.
"No delivery type defined for supplying plant and document type RB"
Scenario:-There are some damaged goods which are coming from france vendor to ukrain customer,now ukrain customer wish to send back the damaged goods to france.
Looking forward:-1>Can anyone please let me know if there is an any customizing setting required if yes then how to maintain(navigation).
2>Is it something like practically it is not possible as goods are dispatched back to the country from where it is coming.
Thanks for your help !!!
Dharmesh

Hi Naveen,
Thanks for the information !!!
Futher while creating PO i am getting an error message as purchase org. not responsile for plant how to solve this error can you plz let me know.
Regards,
Dharmesh

No archive information found for object type and document type

Hi All,
When i try to view the print preview for a perticular doc type, system is giving the error as "No archive information found for object type and document type"
Diagnosis
    No information was found about optical archiving. This may be due to
    either of the following reasons:
    1. No valid archiving parameters were passed
    2. Your system is not configured for optical archiving
System Response
    Processing is cancelled.
Procedure
    Specify valid archiving parameters or check whether your system is configured for optical archiving
Regds,
CB

Hello,
You are trying to Print & also archive by selecting the option Print & Archive.
You have to do archivelink configurations and then create document type and assign to the object type with content repository with archivelink table.
If you want to archive the spool or output then you have to use object type as DRAW. If you are archiving invoice document or letters or so on then you have to know the object type/Business object of the transaction.
Please note that for archivelink configuration, attachment will be either stored in archive server or in SAP database table based on business requirement.
Hope this will give you some understanding on archiving area.
-Thanks,
Ajay

Report that displays Costcenter , Document Number and Document type

Hi All,
Can anyone suggest Report that displays Costcenter for a Document Number of certain Document type - Like G/L accounts .
Thanks in advance ,
Regards,
Ry

Good afternoon.
If you are trying to run a report for a particular cost center (or range of cost centers) and have the report show the GL document number and document type, try transaction KSB1. You can update the line layout to show these fields.
If you are trying to run a report for a GL account and have the report show the cost center, run FAGLL03. You can update the line layout to include cost center.
Apologies if I have mis-understood your question.
Barb

Separate Transaction event key and Document type

Hello Gurus,
Need suggestion and process how to have separate transaction event key and Document types sued in Material document creation with a different number range for the movement types used for SD processes.
Example: 601/602/651 movement types have the Transaction event key as WL
               561 has the Transaction event as WA
               701/702 movement types have the Transaction event as WI
the transaction event keys of WA WH WI WL WQ WR WS WZ have the same number range.
I am looking for solution and suggestion as how do we maintain transaction event key and document type for SD dispatches, cancellation, returns movement types separately.
Thanks and Regards

Hi,
   U can create new document type in OBF4 copy the existing on ee.g WA make new document type and in number range assign the FI number range which u want to assign, MM number range can be create in T. code OMBT and FI number range in FBN1. Documen ttype assignment to t. code is done in OMBA
regards,
zafar
Edited by: zafar_karnalkar on Aug 13, 2010 12:23 PM

Exise Transaction type and Document Type for part 2 record created by J2iun

Hi All ,
We utilized available credit of SERVICE TAX (HCESS and ECESS) and CENVAT (of both RG23A and RG23C) credit against payable SERVICE TAX ( ECESS and HCESS).
At the time of save , system has generated accounting document.I have checked generated accounting document which is perfect.Here the document type selected by the system is ED.
But when I check corresponding part2 entry (in table J_1IPART2) there system has not updated any value in fields Exise Transaction Type (TT) and document Type while internal document and Financial Year are updated with 0 value.
I am not sure if system behaves in the same way for J2IUN generated PART-2 entry.
I need your help to understand it.
Regards
Shrey

Hi,
There is not any transaction type for Excise Utilization and determining the accounts of the fortnightly utilization.
The credit account of the transaction type u2018DLFCu2018 is used as the debit account here. For the credit side we pick the debit accounts from the GRPO, EWPO and TR6C transactions.
This is the reason system only generates a Part II Serial No and updates in table.

Adding XML Declaration and Document Type Declaration.

Similar Messages

Maybe you are looking for