Schemas and pcr's

Hello every body,
i am little bit confused about schemas and pcr's could someone tell me a website or any document where i can understand them easily.
Thanks
srikanth

Hi Srikanth,
Check out this document <a href="http://www.hrexpertonline.com/downloads/08-03.doc">Relationship of Payroll Driver, Schema (Functions), PCR (Operations) on www.hrexpertonline.com</a>
Also see <a href="http://help.sap.com/saphelp_erp2005/helpdata/en/60/d8d8c7576311d189270000e8322f96/frameset.htm">SAP help on HR Tools</a>
Regards,
Ahmad

Similar Messages

Hoe to create HR Schema and PCR's

Hi experts,
I am new to HR-ABAP. and I want to know about HR schema and PCR's and how it can be implemented???Plz. help me

Hi,
Generally schemas and PCR's are written by Functinal guys. They are mainly used in payroll processing. Schemas and PCR's are written using T-codes PE01,PE02 and PE03 there you have details explanantion for each step.
Regards,
Ramu N.

Training on Schema and PCR is required?

HI All,
I am Six month old to SAP world, i have learned a lot about SAP-HR module but unable to understand clearly on working, modifying and creation of new SCHEMA and PCR.
I request you all, if any one know about any institute or a individual who can provide training on Schem and PCR.
Information provider will be highly appreciated,
Thanks in Advance,
rare.prd

Hi,
Pls go through the sites.
http://www.easymarketplace.de/online-pdfs.php?Area=4asu&name=volker&pw=vg&
http://www.sapbrainsonline.com/TUTORIALS/FUNCTIONAL/HR_tutorial.html
http://help.sap.com/saphelp_nw04/helpdata/en/bb/bdb000575911d189240000e8323d3a/frameset.htm
Thanks and Regards,
Revathi.

Regarding schemas and pcrs

Hi gurus,
Though i know about schemas and pcrs..i ahve a small confusion..can anybody clarify me these questions?
1)why we use schema and functionality of the schema?
2)why we use subschema and functionality of subschema?
3)what are the parameters1,2,3,4.
   why do we use these paremters?
   and how it helps... where can we get the documentation for parameters?
4) what an Function does for schema and subschema?
5)what an operation does?
//jack//
Edited by: michael jack on May 22, 2008 8:47 AM
Edited by: michael jack on May 22, 2008 8:57 AM

In simple words schema guides Payroll driver that following path will follow for processing of info types in system. for example if u see the payroll log just think that why infotype 0001 read at start whey system creates bank payment after reading all data? this is all schema
Second part is subschema help schema if you have little know how of programming you can take it as conditional loop sort of things. :).
Technical detail is as under (From sapexpert.com)
Each country payroll version supported by SAP has a program called the "payroll driver" that calculates payrolls. For example, in the U.S., the payroll driver is RPCALCU0, in Mexico it is HMXCALC0, in Canada RPCALCK0 and for international RPCALCX0. Each one is different, but they share a common core of functionality. The job of the payroll driver is to process payroll functions as specified in a payroll schema. These payroll functions each perform a specific job, for example - reading data from infotypes, calculating taxes, and processing wage types. Some functions process payroll rules. Rules are a collection of payroll operations. Each operation does a small unit of work, such as multiplying a wage typeu2019s number by a rate to get an amount.
Schemas are edited with transaction PE01, and rules
with PE02. Functions and operations are maintained with transaction PE04. To view payroll results,
use transaction pc_payresult (or in earlier R/3 releases go to Tools>Payroll result>Display in the Payroll menu). (See Figure 1.)The standard payroll schema for a country can be derived from table T500L (see the screen blow). If the country in table T500L has an X in the Old Naming Conv field, then the schema is HR Country Indicator plus 000. Otherwise, it is the ISO Code plus 00. So the U.S. has schema U000, for Mexico it is MX00 and for international its X000.
Good Luck
Syed

Schemas and PCRs

hi, experts.
i need help in learning schemas and writing PCRs. please suggest me any book or send me any document that will help.
regards,
madhu

hai..
How to read rules and Schemas
1.Structure of relationship in Rules and Schemas:
a)Schemas consist of Functions and Sub-schemas
b)Some functions have the rules attached to it as one of its parameter
c)Rules consist of a set of operations to perform some actions
d)Operations and Functions are the executable components
As per the diagram Set of Operations make a Rule which in turn attached to some functions and those functions embedded in Schemas or Sub-schemas (Inside the main schemas) to decide the flow of the payroll program.
Structure of a Schema:
Func:
This column is used to give a function name.
Par1, Par2, Par3, Par4:
1. Function has maximum four parameters.
2. The function can have zero to four parameters as per the definition of the function.
3. Pressing F4 we can get the list of all the values which can be used as parameters.
4. For some functions in the first parameter is the name of the rule created.
5. These parameter values are predefined the function is being created.
D:
1. This column is used to comment and uncomment a function.
2. If (*) is being put then the line is commented and will not be executed in Payroll processing.
3. If nothing is given then the line would be executable.
Desc
1. In this column description for the function is being used.
Functions:
Functions are used for;
Performing some payroll computations (E.g. INEPF function calculates the PF amount of an employee during payroll run)
Calling rules (E.g. P0045 function calls a rule INLN to compute the loan details of a personnel number).
Getting data from Infotypes (E.g. P0581 will get the data from Infotype-581 for payroll processing).
For some decisions. (E.g. IF & ENDIF function is used to execute as per the true and false decisions) etc.
Rules:
Rules are used for holding a set of operations for a particular requirement to be accomplished.
Attributes:
1. Program Class.
a. There are two program classes to be assigned to the rule while creating.
i. Payroll (C).
ii. Time (T).
2. Country Grouping.
a. For Payroll program class the country grouping should be mentioned. (E.g. 40 for India).
b. For Time management rule the country grouping should be (*).
3. Employee Sub-grouping.
a. All the wagetypes have an attribute of employee sub-grouping.
b. It varies client to client.
c. Value 3 means EE sub-grouping is 3.
d. Value * means all EE Sun-groupings.
4. Wagetypes.
a. The wagetype in the internal table which is meant to be processed by the rule.
b. If a value for Wagetype is being given then the particular wagetype is being queried for processing.
c. If **** has been given then all the wagetypes present in the particular internal table will be processed.
Structure of the Rule.
Frequently Used Internal Tables in PY Processing:
The Payroll driver uses lots of internal tables used for storing data temporarily in the program for processing. Some of the important internal tables are:
The structure of internal tables:
EE Sub-grouping:
1. The Wagetype is assigned to a particular Employee sub-group.
2. 3 is a particular employee subgroup for basic pay wagetype.
3. * value means for all EE sub-grouping.
Wagetype Code:
1. The Wagetype code number is the number assigned to a particular pay component.
Wagetype Description:
1. The description for the wagetype code.
NUM:
1. If there is a split for the wagetypes then this NUM field will make them different.
2. If A persons basic salary is changed in the mid of the month then the wagetype will be split in two amounts with NUM = 01 and NUM = 02.
RTE:
1. The RTE column stores a value for;
a. Rate of interest.
b. Number of leave days.
c. Projection factor. Etc.
2. E.g. In the above diagram /401 wagetype has RTE value 10 which is the projection factor used for different calculations.
AMT:
1. This column possesses the amount of the particular wagetype.
Use of the internal tables:
1. The internal tables are being used for calculations on the NUM, RTE & AMT fields.
2. These internal tables are being read by the rules row by row.
3. The Calculation rule would be only processed for those wagetypes which are specified in the rules source code.
4. The row in the internal table containing the wagetype which has been defined in rule attributes will be placed in the header of the internal table for processing.
5. The processing would be as per the operations used in the rule.
Some important Operations & Functions:
The editor for Operations and Functions is PE04.
While the payroll driver encounters a function and operation it would call a subroutine written in the payroll driver.
The subroutine name for the operation will be OP****, Where **** will be the name of the operation.
For E.g. for Operation AMT the subroutine name would be OPAMT.
The code written for the function will be found as a subroutine in payroll driver as FU****, where **** will be the name of the function.
For E.g. for function INEPF the subroutine name would be FUINEPF.
Operations:
AMT:
1. This Operation would fetch the Amount of the wagetype queried in the rule, in the Variable AMT for processing.
2. The Syntax of the Operation is ZZZOVVVV.
3. ZZZ -> AMT.
4. O -> Operand.
5. VVV -> Value or Variable.
6. For E.g. (AMT= 1000) will fetch the Amount of Wagetype 1000 into AMT.
7. Pressing F1 on the AMT Operation will provide the documentation.
RTE:
1. This Operation would fetch the Rate of the wagetype queried in the rule, in the Variable RTE for processing.
2. The Syntax of the Operation is ZZZOVVVV.
3. ZZZ -> RTE.
4. O -> Operand.
5. VVV -> Value or Variable.
6. For E.g. (RTE= /401) will fetch the Rate of Wagetype /401 into RTE.
7. Pressing F1 on the RTE Operation will provide the documentation.
NUM:
1. This Operation would fetch the Split indicator of the wagetype queried in the rule, in the Variable NUM for processing.
2. The Syntax of the Operation is ZZZOVVVV.
3. ZZZ -> NUM.
4. O -> Operand.
5. VVV -> Value or Variable.
6. For E.g. (NUM= 1000) will fetch the Split indicator of Wagetype 1000 into NUM.
7. Pressing F1 on the NUM Operation will provide the documentation.
ADDWT:
1. This Operation will append one more row in the internal table (Processed by the rule).
2. After calculating an amount from a particular wagetype the amount can be assigned to another wagetype and append to the internal table.
3. For E.g. ADDWT 2050 will add the NUM, RTE, AMT calculated to the NUM, RTE & AMT of the wagetype 2050.
4. If the Wagetype 2050 is not there before in the internal table then NUM, RTE & AMT would be 0.
5. If any value of these three variables are present before then they will be added to the calculated ones.
Functions:
PIT:
1. This function will read the internal table IT (Input table).
2. The function will hold a rule as first parameter.
PRT:
1. This function will read the internal table RT (Results table).
2. The function will hold a rule as first parameter.
PDT:
1. This function will read the internal table IT (Input table).
2. The function will hold a rule as first parameter.
PORT:
1. This function will read the internal table ORT (Old results table).
2. The function will hold a rule as first parameter.
P0014:
1. This function will read the Infotype 0014 for processing.
2. The function will hold a rule as first parameter.

HR schema and rule function overview

Hello, is there any HR schema and rule function overview there ? I mean for example function VARST, ADDDB, HRS, PCY etc., which are under PE01 and PE02 available to use.
Thanks.

Schemas can be viewed and modified through pe01. Schemas use functions and Personnel Calculation Rules (PCR).
PCRs can be viewed and modified through pe02. Time Evaluation PCRs use operations such as HRS, VARST, ADDDB and OUTWP. Payroll Calculation PCRs use operations such as RTE, NUM, AMT, VARGB, ADDWT and OUTWP.
Functions and Operations can be viewed through pe04, along with their parameters.
Documentation on Functions and Operations can be viewed either in the schema or rule by selecting the object + F1 (or the ? icon), or through pe04.

Difference between schema and DTD

Difference between schema and DTD
<author>
<firstname></firstname>
<lastname></lastname>
</author>
How will u write dtd and schema for above XML ?

DTD:
<!ELEMENT author(firstname, lastname)>
<!ELEMENT firstname(#PCDATA)>
<!ELEMENT lastname(#PCDATA)>
Schema:
<xs:element name="author">
<xs:complexType>
<xs:sequence>
<xs:element name="firstname" type="xs:string"/>
<xs:element name="lastname" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>

Forms pulling Multiple Records from an XML Schema and XML data files - Adobe LiveCycle Designer

I built a form in Adobe LiveCycle with an xml schema and data file. The problem is with how the form renders the xml data file.
I have a statement element that consists of about 6 fields (statementID, statementName, statementAddress, statementCountry, statementZip, statementDate, etc) of data in the schema that allows for multiple iterations - so one xml data file can contain multiple statements. These fields allow for null values.
But here's the problem: When any of the statements - say statement 2 of 6 - has a null value in one of the fields, if the xml data file doesn't have a placeholder
(example of placeholder: <statementName type="String"/> )in the xml for that field, my form pulls the field value from the NEXT statement.
This corrupts all the rest of the statement records, as this field is shifted up for all the rest.
I know that in the past I haven't needed a placeholder when a field was null. But I'm wondering if when the data allows for multiple records the xml data file needs to generate the placeholder. And where is the problem? In the Schema? The xml data file? My form? And the 64-thousand-dollar question: How to fix it?

If your <statement> element is the one that repeats, it should be bound to a subform with the binding string of something like $.statement[*]. Then in that subform should be your fields and they should have bindings of $.statementID, $.statementName, $.statementAddress, etc.
Kyle

Create XML dynamically from schema and Java bean

Hi,
I'm looking for suggestions on the best approach to create an XML file programatically from a schema and Java bean.
The schema used is not fixed and may vary with each request so a dynamic way to create the XML is required.
Is there an API available that allows me to achieve this easily? Any help would be appreciated to point me in the right direction.
Thanks.

XMLBeans or JAXB should work for you.
- Saish

Can't i use xml schema and oledb data connection at the same time?

Hello to all and thanks in advance.I use xml schema and oledb data connection at the same time and the problem is that when I try to export the xml, the outcome is not what i expect.Without the oledb connection everything is ok (just the schema) and the xml complies with the schema.
Can't i have both schema and oledb and the exported xml be as i want it?

You can use both at the same time, but not gor Internet access if that's what you're asking.
Now there is a thing called Link Aggregation, which combines a number of interfaces for speed/redundancy, but it really only works locally, and then only with ALL special equipment in the route, and most likely OSX Server involved.
Sorry.

XML DevCon 2001: Submit schema and stylesheet problems- win XML Spy

There are only a few days to submit schema and stylesheet problems for XML
DevCon 2001 in London. If the workshop instructors use your submission
during the conference, you win a copy of XML Spy.
<shamelessPlug>
XML DevCon 2001 has a content-rich technical program with a faculty that
includes Henry Thompson (W3C Fellow), Peter Chen (IEEE Fellow, ACM
Fellow),
Martin Bryan (DIFFUSE Project), and authors such as Bob DuCharme, Ian
Graham, Elliotte Rusty Harold, G. Ken Holman, Benoît Marchal, JP
Morgenthal,
and Simon St. Laurent. There are a variety of eBusiness sessions,
including
panel discussions and presentations about ebXML, Web Services, and UDDI.
The program includes presentations by Jonathan Borden, Ron Bourret, Lee
Buck, Alex Chaffee, Mark Colan, John Evdemon, Meike Klettke, Andy
Longshaw,
Ingo Macherius, Simon Nicholson, David Orchard, Sebastian Rahtz, Daniel
Rivers-Moore, Michael Rys, Krishna Sankar, Matt Sergeant, Richard Tobin,
Priscilla Walmsley, David RR Webber and other distinguished faculty.
</shamelessPlug>
http://www.xmldevcon2001.com/London/html/conference.php
For a free pass to exhibits and special events (keynotes, joint XML UK and
British Computer Society meeting, OASIS XPath/XSLT meeting, vendor
presentations):
http://www.xmldevcon2001.com/London/html/special_events.php
Public submissions (schemas and stylesheets)
Three members of the W3C Schema Working Group (Michael Rys, Henry
Thompson, Priscilla Walmsley) will teach a Schema Workshop. Submit
problem schemas to them by e-mail:
[email protected]
or
http://www.xmldevcon2001.com/London/html/session.php?code=W5
Sebastian Rahtz, Bob DuCharme, Benoît Marchal, and Ken Holman will
present the "Stylesheets and Transformations: Best Practices" workshop on
Thursday, February 22 in London. To submit a stylesheet or problem
description for their workshop:
[email protected]
or browse to:
http://www.xmldevcon2001.com/London/html/session.php?code=T17
========== Ken North ======================
See you at Javacon 2001 (New York, March 1)
www.javacon2001.com
XML DevCon 2001: London (February 21-23) New York (April 8-11)
www.xmldevcon2001.com
=======================================

Looks okay to me. But then I have no idea of what those "problems" are that you mentioned. Was there a particular reason you didn't tell us what they are?

Schemas and workspaces in Apex 3.0

Hi Friends
We are quite new to HTML DB. We have few queries pertaining to schemas and workspaces.
We are developing an application in workspaces X which is associated with database user/schema X. We need to give this application for testing to the users. For that we need to have different set of environment so that it does not hamper our development.
So what should be our plan of action.?
Currently we have created a different database user/schema in the same database and associated a different workspace Y to it. But we are facing import/export issues across the workspaces. We have already raised this issue in the forum.
Can we have same workspace associated with 2 different database schemas/users? If yes, then how does HTML DB handle the same?
Thanks in advance.
Regards
Minakshi

Hi Friends,
As per Scott's suggestion, we attached our workspace X to 2 schemas A and B. Then we exported the app say 555(here the schema is A) and imported it using the parsing schema B in new application id say 500. But now the real problem starts. If we have added some new functionality in a page in our application 555 and now only that page we want to export and import it in application 500, then it gives error as "This page was exported from a different application or from an application in different workspace. Page cannot be installed in this application." So in the sql file that we exported, we changed few things as follows(marked in bold)
--application/set_environment
prompt APPLICATION 500 - Load_Factor_System
-- Application Export:
-- Application: 500
-- Name: Load_Factor_System
-- Date and Time: 12:01 Monday May 21, 2007
-- Exported By: ADMIN
-- Flashback: 0
-- Export Type: Page Export
-- Version: 3.0.0.00.20
-- SET APPLICATION ID
wwv_flow.g_flow_id := 500;
wwv_flow_api.g_id_offset := 0;
After we changed the export file as above and then tried to import it in application 500 it gives error as "ORA-20001: GET_BLOCK Error. ORA-20001: Execution of the statement was unsuccessful. ORA-00001: unique constraint (FLOWS_030000.WWV_FLOW_PAGE_PLUGS_PK) violated <pre>declare s varchar2(32767) := null; l_clob clob; l_length number := 1; begin s := null; wwv_flow_api.create_page_plug ( p_id=> 6303905775095939 + wwv_flow_api.g_id_offset, p_flow_id=> wwv_flow.g_flow_id, p_page_id=> 1020, p_plug_name=> 'User Master', p_region_name=>'', p_plug_template="
Can anybody please help us with this issue? The other solution for this is to delete the complete application 500 and then freshly install the application. But we do not want this since any change in few pages should not result in deletion of complete application.
Also Scott, thanks a lot for your detailed solution as to how to put an example on apex.oracle.com. We shall definitely put an example and post it.
Regards
Minakshi

Context,Physical schema and Logical schema

Hi,
How the context,physical schema,logical schema and agent are interrelated.
Please explain
Thanks
Jack

Hi Jack,
Context:
A context is a set of resources allowing the operation or simulation of one or more data processing applications. Contexts allow the same jobs (Reverse, Data Quality Control, Package, etc) to be executed on different databases and/or schemas.
Its used to run the object(process) in different database.
Physical Schema:
The physical schema is a decomposition of the data server, allowing the Datastores (tables, files, etc) to be classified. Objects stored in data servers with this mode of classification can be accessed by specifying the name of the schema attached to the object name.
Ex
Oracle classifies its tables by "schema" (or User). Each table is linked to a schema, thus SCOTT.EMP represents the table EMP in the schema SCOTT.
Logical schema:
A logical schema is an alias that allows a unique name to be given to all the physical schemas containing the same datastore structures.
->The aim of the logical schema is to ensure the portability of the procedures and models on the different physical schemas. In this way, all developments in ODI Designer are carried out exclusively on logical schemas.
Thanks
Madha

New User Database schema and table name

When i create a new user in Oracle Webcenter Spaces 11g, I am not able to get the name of the database schema and table, where it is stored. Any insight on this will be very helpful.

WebCenter (and WebCenter spaces) uses an 'identity store' instead of database schema for storing user information - in an 'out of the box' installation, users are maintained through an embedded WebLogic LDAP store.
See the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter, p. 34-2.
At the end of section 34.4.1:
WebCenter Spaces supports self-registration. When new WebCenter users
self-register, they create their own login and password and a new user account is
created in the identity store. See also, Section 34.4, "Allowing Self-Registration".
user9097357 wrote:
When i create a new user in Oracle Webcenter Spaces 11g, I am not able to get the name of the database schema and table, where it is stored. Any insight on this will be very helpful.

XSU Generated Schemas and DTDs are bad input for oracg

Hi,
I'm trying to write a utility that accepts a database schema name and writes XML Schemas and a DTDs for each table based on a:
select * from table_name
over each table in the schema. I would then like to use those files as input to the oracg utility to produce java files. There are some problems though. The DTD representation is not meant as a standalone DTD. In other words its of the form:
<!DOCTYPE NAME [
...dtd defs here ...
]>
which oracg doesn't like. Its not a big deal to do some post processing and delete the DOCTYPE defenition, but then oracg barfs with the following error:
Error: DTD Class Generator failed to generate classes. oracle.xml.parser.v2.XMLParseException: Expected 'DOCTYPE'.
Here is the DTD I was trying to generate a class from:
<!ELEMENT STATION (ROW)*>
<!ELEMENT ROW (STN_THTR_AREA_CODE, STN_ID_CD, STN_NM?, STN_ESTD_DATA?, STN_CTRY_CD?, STN_SW_TYPE_CD?, STN_AGNY_CD?, STN_
MFR_CD?, STN_CURR_SFTWR?, STN_TIME_ZONE?, STN_LATD?, STN_LNGTD?, STN_NM_VLD_CALLS_1?, STN_NM_VLD_CALLS_2?, STN_NM_VLD_CA
LLS_3?, STN_NM_VLD_CALLS_4?, STN_NM_CALLS_1?, STN_NM_CALLS_2?, STN_NM_CALLS_3?, STN_NM_CALLS_4?, STN_STDY_ID_1?, STN_STD
Y_ID_2?, STN_STDY_ID_3?, STN_STDY_ID_4?, STN_CLASS_A_PHONES_ESTD_QTY?, STN_CLASS_B_PHONES_ESTD_QTY?, STN_POC_TTL?, STN_P
OC_FIRST_NM?, STN_POC_LAST_NM?, STN_POC_OFC_SYM_NM?, STN_POC_APO_PPO?, STN_POC_PSTL_CD?, STN_POC_AUTVN_TLPHN_NBR?, STN_M
ODIFIED_DT?, STN_TANDEM?, STN_MEMO?, STN_SW_TYPE_DESC?, STN_FREQ?, STN_THTR, STN_STDY_ID, STN_GEOLOC?, STN_SHIFT_FLG, ST
N_SEQ?, STN_TMPLT_NM?)>
<!ATTLIST ROW num CDATA #REQUIRED>
<!ELEMENT STN_THTR_AREA_CODE (#PCDATA)>
<!ELEMENT STN_ID_CD (#PCDATA)>
<!ELEMENT STN_NM (#PCDATA)>
<!ELEMENT STN_ESTD_DATA (#PCDATA)>
<!ELEMENT STN_CTRY_CD (#PCDATA)>
<!ELEMENT STN_SW_TYPE_CD (#PCDATA)>
<!ELEMENT STN_AGNY_CD (#PCDATA)>
<!ELEMENT STN_MFR_CD (#PCDATA)>
<!ELEMENT STN_CURR_SFTWR (#PCDATA)>
<!ELEMENT STN_TIME_ZONE (#PCDATA)>
<!ELEMENT STN_LATD (#PCDATA)>
<!ELEMENT STN_LNGTD (#PCDATA)>
<!ELEMENT STN_NM_VLD_CALLS_1 (#PCDATA)>
<!ELEMENT STN_NM_VLD_CALLS_2 (#PCDATA)>
<!ELEMENT STN_NM_VLD_CALLS_3 (#PCDATA)>
<!ELEMENT STN_NM_VLD_CALLS_4 (#PCDATA)>
<!ELEMENT STN_NM_CALLS_1 (#PCDATA)>
<!ELEMENT STN_NM_CALLS_2 (#PCDATA)>
<!ELEMENT STN_NM_CALLS_3 (#PCDATA)>
<!ELEMENT STN_NM_CALLS_4 (#PCDATA)>
<!ELEMENT STN_STDY_ID_1 (#PCDATA)>
<!ELEMENT STN_STDY_ID_2 (#PCDATA)>
<!ELEMENT STN_STDY_ID_3 (#PCDATA)>
<!ELEMENT STN_STDY_ID_4 (#PCDATA)>
<!ELEMENT STN_CLASS_A_PHONES_ESTD_QTY (#PCDATA)>
<!ELEMENT STN_CLASS_B_PHONES_ESTD_QTY (#PCDATA)>
<!ELEMENT STN_POC_TTL (#PCDATA)>
<!ELEMENT STN_POC_FIRST_NM (#PCDATA)>
<!ELEMENT STN_POC_LAST_NM (#PCDATA)>
<!ELEMENT STN_POC_OFC_SYM_NM (#PCDATA)>
<!ELEMENT STN_POC_APO_PPO (#PCDATA)>
<!ELEMENT STN_POC_PSTL_CD (#PCDATA)>
<!ELEMENT STN_POC_AUTVN_TLPHN_NBR (#PCDATA)>
<!ELEMENT STN_MODIFIED_DT (#PCDATA)>
<!ELEMENT STN_TANDEM (#PCDATA)>
<!ELEMENT STN_MEMO (#PCDATA)>
<!ELEMENT STN_SW_TYPE_DESC (#PCDATA)>
<!ELEMENT STN_FREQ (#PCDATA)>
<!ELEMENT STN_THTR (#PCDATA)>
<!ELEMENT STN_STDY_ID (#PCDATA)>
<!ELEMENT STN_GEOLOC (#PCDATA)>
<!ELEMENT STN_SHIFT_FLG (#PCDATA)>
<!ELEMENT STN_SEQ (#PCDATA)>
<!ELEMENT STN_TMPLT_NM (#PCDATA)>
I'm also having problems dealing with schemas. The call to OracleXMLQuery.getXMLMetaData(OracleXMLQuery.SCHEMA, false) returns the following for this particular table:
<DOCUMENT xmlns:xsd="http://www.w3.org/2000/10/XMLSchema"<xsd:schema xmlns:xsd="http://www.w3.org/2000/10/XMLSchema">
<xsd:element name="STATION">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ROW" minOccurs="0" maxOccurs="unbounded">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="STN_THTR_AREA_CODE" type="xsd:string" minOc curs="0"/>
<xsd:element name="STN_ID_CD" type="xsd:string" minOccurs="0"/>
<xsd:element name="STN_NM" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_ESTD_DATA" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_CTRY_CD" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_SW_TYPE_CD" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_AGNY_CD" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_MFR_CD" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_CURR_SFTWR" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_TIME_ZONE" type="xsd:integer" nullable="true" minOccurs="0"/>
<xsd:element name="STN_LATD" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_LNGTD" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_NM_VLD_CALLS_1" type="xsd:integer" nullable="true" minOccurs="0"/>
<xsd:element name="STN_NM_VLD_CALLS_2" type="xsd:integer" nullable="true" minOccurs="0"/>
<xsd:element name="STN_NM_VLD_CALLS_3" type="xsd:integer" nullable="true" minOccurs="0"/>
<xsd:element name="STN_NM_VLD_CALLS_4" type="xsd:integer" nullable="true" minOccurs="0"/>
<xsd:element name="STN_NM_CALLS_1" type="xsd:integer" nullable="true" minOccurs="0"/>
<xsd:element name="STN_NM_CALLS_2" type="xsd:integer" nullable="true" minOccurs="0"/>
<xsd:element name="STN_NM_CALLS_3" type="xsd:integer" nullable="true" minOccurs="0"/>
<xsd:element name="STN_NM_CALLS_4" type="xsd:integer" nullable="true" minOccurs="0"/>
<xsd:element name="STN_STDY_ID_1" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_STDY_ID_2" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_STDY_ID_3" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_STDY_ID_4" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_CLASS_A_PHONES_ESTD_QTY" type="xsd:integer" nullable="true" minOccurs="0"/>
<xsd:element name="STN_CLASS_B_PHONES_ESTD_QTY" type="xsd:integer" nullable="true" minOccurs="0"/>
<xsd:element name="STN_POC_TTL" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_POC_FIRST_NM" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_POC_LAST_NM" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_POC_OFC_SYM_NM" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_POC_APO_PPO" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_POC_PSTL_CD" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_POC_AUTVN_TLPHN_NBR" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_MODIFIED_DT" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_TANDEM" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_MEMO" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_SW_TYPE_DESC" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_FREQ" type="xsd:integer" nullable="true" minOccurs="0"/>
<xsd:element name="STN_THTR" type="xsd:string" minOccurs="0"/>
<xsd:element name="STN_STDY_ID" type="xsd:string" minOccurs="0"/>
<xsd:element name="STN_GEOLOC" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_SHIFT_FLG" type="xsd:string" minOccurs="0"/>
<xsd:element name="STN_SEQ" type="xsd:integer" nullable="true" minOccurs="0"/>
<xsd:element name="STN_TMPLT_NM" type="xsd:string" nullable="true" minOccurs="0"/>
</xsd:sequence>
<xsd:attribute name="num" type="xsd:integer"/>
</xsd:complexType&g t;
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
/>
The oracg utility gives the following errors with this as input:
file:/export/home/kennedy/generatedSchemas/STATION.xsd<Line 1, Column 58>: XML-0190: (Fatal Error) Whitespace required.
file:/export/home/kennedy/generatedSchemas/STATION.xsd<Line 1, Column 58>: XML-0201: (Fatal Error) Expected name instead of <.
file:/export/home/kennedy/generatedSchemas/STATION.xsd<Line 1, Column 58>: XML-0122: (Fatal Error) '=' missing in attribute.
file:/export/home/kennedy/generatedSchemas/STATION.xsd<Line 1, Column 59>: XML-0125: (Fatal Error) Attribute value should start with quote.
Error: Schema Class Generator failed to generate classes. oracle.xml.parser.v2.XMLParseException: Whitespace required.
which clearly points to the fact that the XSD:SCHEMA element is enclosed in the Document Element. Removing the document tag completely and leaving XSD:SCHEMA as the root element works. But thats a lot of post processing to be doing and I was wondering if there was a way to generate XML Schemas and DTDs using the standalone representations.
If there is no way to do that, could somebody help me fix the error generated by oracg with my DTD?
Thanks,
Matt

Hi,
I'm trying to write a utility that accepts a database schema name and writes XML Schemas and a DTDs for each table based on a:
select * from table_name
over each table in the schema. I would then like to use those files as input to the oracg utility to produce java files. There are some problems though. The DTD representation is not meant as a standalone DTD. In other words its of the form:
<!DOCTYPE NAME [
...dtd defs here ...
]>
which oracg doesn't like. Its not a big deal to do some post processing and delete the DOCTYPE defenition, but then oracg barfs with the following error:
Error: DTD Class Generator failed to generate classes. oracle.xml.parser.v2.XMLParseException: Expected 'DOCTYPE'.
Here is the DTD I was trying to generate a class from:
<!ELEMENT STATION (ROW)*>
<!ELEMENT ROW (STN_THTR_AREA_CODE, STN_ID_CD, STN_NM?, STN_ESTD_DATA?, STN_CTRY_CD?, STN_SW_TYPE_CD?, STN_AGNY_CD?, STN_
MFR_CD?, STN_CURR_SFTWR?, STN_TIME_ZONE?, STN_LATD?, STN_LNGTD?, STN_NM_VLD_CALLS_1?, STN_NM_VLD_CALLS_2?, STN_NM_VLD_CA
LLS_3?, STN_NM_VLD_CALLS_4?, STN_NM_CALLS_1?, STN_NM_CALLS_2?, STN_NM_CALLS_3?, STN_NM_CALLS_4?, STN_STDY_ID_1?, STN_STD
Y_ID_2?, STN_STDY_ID_3?, STN_STDY_ID_4?, STN_CLASS_A_PHONES_ESTD_QTY?, STN_CLASS_B_PHONES_ESTD_QTY?, STN_POC_TTL?, STN_P
OC_FIRST_NM?, STN_POC_LAST_NM?, STN_POC_OFC_SYM_NM?, STN_POC_APO_PPO?, STN_POC_PSTL_CD?, STN_POC_AUTVN_TLPHN_NBR?, STN_M
ODIFIED_DT?, STN_TANDEM?, STN_MEMO?, STN_SW_TYPE_DESC?, STN_FREQ?, STN_THTR, STN_STDY_ID, STN_GEOLOC?, STN_SHIFT_FLG, ST
N_SEQ?, STN_TMPLT_NM?)>
<!ATTLIST ROW num CDATA #REQUIRED>
<!ELEMENT STN_THTR_AREA_CODE (#PCDATA)>
<!ELEMENT STN_ID_CD (#PCDATA)>
<!ELEMENT STN_NM (#PCDATA)>
<!ELEMENT STN_ESTD_DATA (#PCDATA)>
<!ELEMENT STN_CTRY_CD (#PCDATA)>
<!ELEMENT STN_SW_TYPE_CD (#PCDATA)>
<!ELEMENT STN_AGNY_CD (#PCDATA)>
<!ELEMENT STN_MFR_CD (#PCDATA)>
<!ELEMENT STN_CURR_SFTWR (#PCDATA)>
<!ELEMENT STN_TIME_ZONE (#PCDATA)>
<!ELEMENT STN_LATD (#PCDATA)>
<!ELEMENT STN_LNGTD (#PCDATA)>
<!ELEMENT STN_NM_VLD_CALLS_1 (#PCDATA)>
<!ELEMENT STN_NM_VLD_CALLS_2 (#PCDATA)>
<!ELEMENT STN_NM_VLD_CALLS_3 (#PCDATA)>
<!ELEMENT STN_NM_VLD_CALLS_4 (#PCDATA)>
<!ELEMENT STN_NM_CALLS_1 (#PCDATA)>
<!ELEMENT STN_NM_CALLS_2 (#PCDATA)>
<!ELEMENT STN_NM_CALLS_3 (#PCDATA)>
<!ELEMENT STN_NM_CALLS_4 (#PCDATA)>
<!ELEMENT STN_STDY_ID_1 (#PCDATA)>
<!ELEMENT STN_STDY_ID_2 (#PCDATA)>
<!ELEMENT STN_STDY_ID_3 (#PCDATA)>
<!ELEMENT STN_STDY_ID_4 (#PCDATA)>
<!ELEMENT STN_CLASS_A_PHONES_ESTD_QTY (#PCDATA)>
<!ELEMENT STN_CLASS_B_PHONES_ESTD_QTY (#PCDATA)>
<!ELEMENT STN_POC_TTL (#PCDATA)>
<!ELEMENT STN_POC_FIRST_NM (#PCDATA)>
<!ELEMENT STN_POC_LAST_NM (#PCDATA)>
<!ELEMENT STN_POC_OFC_SYM_NM (#PCDATA)>
<!ELEMENT STN_POC_APO_PPO (#PCDATA)>
<!ELEMENT STN_POC_PSTL_CD (#PCDATA)>
<!ELEMENT STN_POC_AUTVN_TLPHN_NBR (#PCDATA)>
<!ELEMENT STN_MODIFIED_DT (#PCDATA)>
<!ELEMENT STN_TANDEM (#PCDATA)>
<!ELEMENT STN_MEMO (#PCDATA)>
<!ELEMENT STN_SW_TYPE_DESC (#PCDATA)>
<!ELEMENT STN_FREQ (#PCDATA)>
<!ELEMENT STN_THTR (#PCDATA)>
<!ELEMENT STN_STDY_ID (#PCDATA)>
<!ELEMENT STN_GEOLOC (#PCDATA)>
<!ELEMENT STN_SHIFT_FLG (#PCDATA)>
<!ELEMENT STN_SEQ (#PCDATA)>
<!ELEMENT STN_TMPLT_NM (#PCDATA)>
I'm also having problems dealing with schemas. The call to OracleXMLQuery.getXMLMetaData(OracleXMLQuery.SCHEMA, false) returns the following for this particular table:
<DOCUMENT xmlns:xsd="http://www.w3.org/2000/10/XMLSchema"<xsd:schema xmlns:xsd="http://www.w3.org/2000/10/XMLSchema">
<xsd:element name="STATION">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ROW" minOccurs="0" maxOccurs="unbounded">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="STN_THTR_AREA_CODE" type="xsd:string" minOc curs="0"/>
<xsd:element name="STN_ID_CD" type="xsd:string" minOccurs="0"/>
<xsd:element name="STN_NM" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_ESTD_DATA" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_CTRY_CD" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_SW_TYPE_CD" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_AGNY_CD" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_MFR_CD" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_CURR_SFTWR" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_TIME_ZONE" type="xsd:integer" nullable="true" minOccurs="0"/>
<xsd:element name="STN_LATD" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_LNGTD" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_NM_VLD_CALLS_1" type="xsd:integer" nullable="true" minOccurs="0"/>
<xsd:element name="STN_NM_VLD_CALLS_2" type="xsd:integer" nullable="true" minOccurs="0"/>
<xsd:element name="STN_NM_VLD_CALLS_3" type="xsd:integer" nullable="true" minOccurs="0"/>
<xsd:element name="STN_NM_VLD_CALLS_4" type="xsd:integer" nullable="true" minOccurs="0"/>
<xsd:element name="STN_NM_CALLS_1" type="xsd:integer" nullable="true" minOccurs="0"/>
<xsd:element name="STN_NM_CALLS_2" type="xsd:integer" nullable="true" minOccurs="0"/>
<xsd:element name="STN_NM_CALLS_3" type="xsd:integer" nullable="true" minOccurs="0"/>
<xsd:element name="STN_NM_CALLS_4" type="xsd:integer" nullable="true" minOccurs="0"/>
<xsd:element name="STN_STDY_ID_1" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_STDY_ID_2" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_STDY_ID_3" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_STDY_ID_4" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_CLASS_A_PHONES_ESTD_QTY" type="xsd:integer" nullable="true" minOccurs="0"/>
<xsd:element name="STN_CLASS_B_PHONES_ESTD_QTY" type="xsd:integer" nullable="true" minOccurs="0"/>
<xsd:element name="STN_POC_TTL" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_POC_FIRST_NM" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_POC_LAST_NM" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_POC_OFC_SYM_NM" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_POC_APO_PPO" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_POC_PSTL_CD" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_POC_AUTVN_TLPHN_NBR" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_MODIFIED_DT" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_TANDEM" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_MEMO" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_SW_TYPE_DESC" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_FREQ" type="xsd:integer" nullable="true" minOccurs="0"/>
<xsd:element name="STN_THTR" type="xsd:string" minOccurs="0"/>
<xsd:element name="STN_STDY_ID" type="xsd:string" minOccurs="0"/>
<xsd:element name="STN_GEOLOC" type="xsd:string" nullable="true" minOccurs="0"/>
<xsd:element name="STN_SHIFT_FLG" type="xsd:string" minOccurs="0"/>
<xsd:element name="STN_SEQ" type="xsd:integer" nullable="true" minOccurs="0"/>
<xsd:element name="STN_TMPLT_NM" type="xsd:string" nullable="true" minOccurs="0"/>
</xsd:sequence>
<xsd:attribute name="num" type="xsd:integer"/>
</xsd:complexType&g t;
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
/>
The oracg utility gives the following errors with this as input:
file:/export/home/kennedy/generatedSchemas/STATION.xsd<Line 1, Column 58>: XML-0190: (Fatal Error) Whitespace required.
file:/export/home/kennedy/generatedSchemas/STATION.xsd<Line 1, Column 58>: XML-0201: (Fatal Error) Expected name instead of <.
file:/export/home/kennedy/generatedSchemas/STATION.xsd<Line 1, Column 58>: XML-0122: (Fatal Error) '=' missing in attribute.
file:/export/home/kennedy/generatedSchemas/STATION.xsd<Line 1, Column 59>: XML-0125: (Fatal Error) Attribute value should start with quote.
Error: Schema Class Generator failed to generate classes. oracle.xml.parser.v2.XMLParseException: Whitespace required.
which clearly points to the fact that the XSD:SCHEMA element is enclosed in the Document Element. Removing the document tag completely and leaving XSD:SCHEMA as the root element works. But thats a lot of post processing to be doing and I was wondering if there was a way to generate XML Schemas and DTDs using the standalone representations.
If there is no way to do that, could somebody help me fix the error generated by oracg with my DTD?
Thanks,
Matt

Schemas and pcr's

Similar Messages

Maybe you are looking for