EXTERNAL PARAMETER ENTITY CREATION

Hi All
I am creation the XML file using SAP XML DOM Library objects.
Our requirement is to create the EXTERNAL PARAMETER ENTITY Declaration using DOCTYPE tag.
For Example
<!DOCTYPE descriptSol [
<!ENTITY % references SYSTEM "P_899200_SD01_01.ref">;
%references
]>
We are using following method to create it:
DATA:
lo_doc_type                 TYPE REF TO if_ixml_document_type,
lo_entity_dec               TYPE REF TO if_ixml_entity_decl,
          CALL METHOD go_document->create_document_type
            EXPORTING
              name = 'descriptSol'
            RECEIVING
              rval = lo_doc_type.
          CALL METHOD go_document->set_document_type
            EXPORTING
              document_type = lo_doc_type.
          CALL METHOD lo_doc_type->create_ext_entity_decl
            EXPORTING
              is_parameter_entity = 'X'
              name                            = 'references'
              notation                       = ''
              public_id                      = ''
              system_id                   = 'P_899200_SD01_01.ref'
            RECEIVING
              rval                               = lo_entity_dec
          CALL METHOD lo_doc_type->append_child
            EXPORTING
              new_child = lo_entity_dec
            RECEIVING
              rval      = lw_rval.
The Above code is working and creating following tag in the XML document:
<!DOCTYPE descriptSol [
<!ENTITY % references SYSTEM "P_899200_SD01_01.ref">;
]>;
So hereu201D%referencesu201D at end of the declaration is missing.
This type of entity is called as "EXTERNAL (PARSED) PARAMETER ENTITY Declaration".
Give your suggestions that whether we are using right method to created External entity reference or not.
Thanks in advance
Sukhjinder Singh

I have the same experience. After I correct the error in my dtd file, the message dissapears. Good luck.

Similar Messages

'External Parameter Entity' error?

Hi all,
I wrote some XML tools a few months back using the Crimson, JAXP, and Xalan packages.
I have just revisited that code, intending to start a new XML project, but for some reason all the old source code will compile okay but I get the following run-time error (even on very simple apps):
A nonfatal internal JIT (3.00.078(x)) error 'Relocation error: NULL relocation t
arget' has occurred in :
'org/apache/crimson/parser/Parser2.maybeComment (Z)Z': Interpreting method.
Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cg
i
error1: External parameter entity "%[dtd];" has characters after markup.
I've been a little out of touch with what's going on with Java/XML lately, so I was hoping someone could get me up to date and tell me what's wrong.
thanks!

I have the same experience. After I correct the error in my dtd file, the message dissapears. Good luck.

Problem in parsing-invalid use of a parameter entity reference

Hi
I am getting an error in parsing the xml message. The first few lines of DTD are as follows.
<!ENTITY % contractIdentifier "contractRef , branch">
<!ENTITY % ccyDetails "amount , settlementDate , dealRate">
<!ENTITY % schedule "count , schedule">
<!ENTITY % paymentDetails "payIndicator , ourPayAccount , theirAgent ,
theirAgentsAgent , beneficiaryAccount , receiveIndicator , ourReceiveAccount
, suppressCable , suppressConfirmation , pvpIndicator">
<!ENTITY % commonCore "%paymentDetails; , narrative* , abaNumber ,
cleanRiskIndicator , creditLine , directSent , federalFundsFlag , chipsCode
, riskTakingUnit">
I am getting the error as
invalid use of a parameter entity reference line no 5.
Can somebody help me
Thanks
Prashant

Parameter entity references may not be used within markup in an internal DTD.
To use a DTD with parameter entity reference use a external DTD.

View and Entity creation source code

I would like to know which jars \ classes in JDeveloper are responsible for writing the XML that defines a view or an entity (The XML created by the "Create a new view" wizard). Thanks.

The designtime class responsible for Entity creation is oracle.jbo.dt.objects.JboEntity and the class for View Objects is oracle.jbo.dt.objects.JboView. There is no documentation available for how the designtime apis work, so you are kind of on your own to do much with it.
Ray

Dynamic domain-based entity creation and relation to base entity

Hi everyone -
My first post here... I have a base entity (PROJECT) with an attribute called RecordType (a domain-based attribute). Depending on the value of RecordType, the business wants to use that result set as input for another reference entity, and then
relate them together in a possible {one|many}-to-many relationship. For example:
If RecordType = Strategy, then there is a need to create a separate entity called STRATEGY with the results of that filter. The PROJECT entity and STRATEGY now need to be related together in a PROJECT_STRATEGY relationship table.
There seem to be a couple of options, but none are elegant, and some simply don't work:
Option #1 (doesn't work): I create the relationship table (PROJECT_STRATEGY) with a domain-based attribute of the PROJECT entity and a second domain-based attribute of the PROJECT entity (but called Strategy), and then try to create a business
rule that limits the selection of the second domain-based attribute by RecordType. MDS tells me I can't use a domain-based attribute in the business rule.
Option #2: I create a SQL Server view called STRATEGY (which is a query based on the PROJECT entity - "where RecordType = 'Strategy') and use that as the reference set. However, there is now no way to utilize that result set inside MDS.
In other words, I cannot use it as a domain-based attribute in the PROJECT_STRATEGY relationship table. This means that an external system/UI would need to enable the relationship selection and write back into the PROJECT_STRATEGY relationship table
inside MDS.
Option #3: I create a STRATEGY entity that is auto-updated (via SQL Server job) every 10 minutes or so from the PROJECT entity (can't figure out how to load a reference entity based on a result set from an existing entity). This allows me to create
two domain-based attributes in the PROJECT_STRATEGY table (as described in Option #1), but is also what I call a non-standard customization, so I have been reticent to go this route.
So, my questions/comments are:
Is there any way to make Option #1 work (using business rules)?
Option #2: Our development team doesn't want to create a separate system/UI to relate the list of PROJECTs to the list of STRATEGYs and then write them back into the PROJECT_STRATEGY relationship table. This also limits the ability to maintain the
PROJECT_STRATEGY table inside MDS since the STRATEGY domain-based attribute would become a free-form attribute at that point. Is there any way to register a view as a reference entity?
Should I explore Option #3? Non-standard, non-native functionality introduced into MDS (any system, really) is something I wanted to avoid, but only from a purity and possible upgrade standpoint. Should I get over this?
I have looked at derived and explicit hierarchies for the PROJECT entity, but they do not seem to apply in the scenario above.
Has anyone tried to create {one|many}-to-many relationships between a base entity and a subset of that base entity without resorting to non-standard customizations within MDS? Is this as bizarre as it sounds?
Any help would be greatly appreciated.
Thanks.

Hi,
I f you are going with rtti approach.... for dynamic creation....you can assign the checktable field in field cat
ls_fcat-ref_table = space.
    ls_fcat-ref_table = 'ZST_DISTRIBUTED_EFFORT'.
    ls_fcat-ref_field = 'WORK_EFFORT'.
    ls_fcat-rollname   = 'DPR_TV_EFFORT'.
    ls_fcat-domname    = 'DPR_WORK'.
    ls_fcat-reptext    = ls_fcat-fieldname.
    ls_fcat-scrtext_l = ls_fcat-fieldname.
    ls_fcat-scrtext_m = ls_fcat-fieldname.
    ls_fcat-scrtext_s = ls_fcat-fieldname.
    ls_fcat-emphasize = me->gc_flag_enable.
    ls_fcat-col_pos    = lv_counter.
ls_fcat-checktable = ' '.
    APPEND ls_fcat TO lt_fcat.
CALL METHOD cl_alv_table_create=>create_dynamic_table
    EXPORTING
      it_fieldcatalog           = lt_fcat
    IMPORTING
      ep_table                  = et_dynamic_table
    EXCEPTIONS
      generate_subpool_dir_full = 1
      OTHERS                    = 2.
IF sy-subrc NE 0.
    es_message-id         = sy-msgid.
    es_message-type       = sy-msgty.
    es_message-number     = sy-msgno.
    es_message-message_v1 = sy-msgv1.
    es_message-message_v2 = sy-msgv2.
    es_message-message_v3 = sy-msgv3.
    es_message-message_v4 = sy-msgv4.
Thanks,
Shailaja Ainala.

Significance of Initial (intial_extent)parameter while creation of table

Hi All,
I am designing a new schema for my 10g database and I am in process of creation of tablespaces and tables.
My Tablespace are extent management local autoallocate and auto segment space management.
With “segment space management Auto”, I understand that I don’t have to define storage clause in tablespace and freelist will be taken care by bitmap
My question is
while creation of tables what’s the significance of Intial (intial_extent in user_tables) parameter.?
Do I need to consider this parameter while defining large and small tables?
Is this not controlled by “auto segment space management.” Parameter of tablespace.?

While it is unlikely to make a measurable impact on anything in practice, it is almost always preferable in theory, assuming perfect knowledge of the system, to have a few different tablespaces with different uniform extent sizes and to put each object in the appropriate tablespace for its size (i.e. giant tables in the tablespace with giant extent sizes, tiny tables in the tablespace with tiny extent sizes, etc.). The problem with this, however, is that you very rarely have perfect knowledge in advance about object sizes and growth and size patterns are likely to evolve over the life of the system, so you can suck up a great deal of DBA and developer time gathering and maintaining this sort of information as well as responding to changes over time (i.e. moving objects from one tablespace to another as their usage patterns change). For most systems, the potential benefit to having a perfect setup, rather than putting everything in an AUTOALLOCATE tablespace, is far smaller than the cost of actually doing so.
Unless you have some reason to believe that your application is in the minority where squeezing the last bit of storage efficiency is worth the hassle, I'd tend to suggest throwing everything in an AUTOALLOCATE tablespace.
Justin

BTItemPriceAgreements - entity creation as relation to BTOrderItemAll

Hi,
I have to create items in Sales contracts through BOL logic. In the Component, I created event for this purpose. I am able to create items by creating entities BTOrderITemAll. For the item, I need to create price agreements. When I am trying to create BTItemPriceAgreements - system is throwing message - not allowing creation as related entity. Appreciate any inputs on how to create BTItemPriceAgreements and link to Item.
With regards,
Ravi

Hi,
I did a similar thing, in the approach that i followed i had to do the code for saving in the BTIL class (CL_CRM_METHODS_BTIL), SAVE_ORDERS method, by creating implicit enhancement at the end, there i called my Z-Function module to save in update task, so that whole transaction gets saved at a go or nothing is saved.
Though just display a Z-table on UI as entirely different story, but this wiki link can give some pointers.
[ZTable in Asign Block|http://wiki.sdn.sap.com/wiki/display/CRM/Howtodisplayaz-tableinanassignmentblock]
Let me know if it helped.
Thanks,
Rohit
Edited by: Rohit Khetarpal on Nov 26, 2009 4:21 PM

Business components: detail entity creation

Hi,
Using JDeveloper 10.1.3.1.0.
I've got a master-detail relationship between two entities. To do CRUD operations, I always go through the view objects based on these entities. My problem is when I create a new instance of the detail, it seems the association at the entity level is not maintained before commit.
For example, let's say I have the entities EntityMaster and EntityDetail and the view objects ViewMaster and ViewDetail. There's an association at the entity level and a view link at the view level. This is a one-to-many relationship (one master - many details).
I do the following in an application module method:
ViewObject detailView = getViewDetail(); //returns the detail view object.
Row newRow = detailView.createRow(); //create a new view row backed by an entity row
// initialize the new row
detailView.insertRow(newRow); //insert the row in the view.
// a bit further
EntityMasterImpl master = ...; //obtain somehow a reference on the master.
RowIterator detailEntityIterator = master.getDetailEntity(); //get the detail entity iterator
int count = detailEntityIterator.getRowCount(); //count has not been incremented by one.
Since I have a validation on the master entity that checks if there's at least one detail entity when setting a particular attribute, I really need the association to be maintained at the entity level.
I've worked around the problem by inserting the new detail entity row in the detailEntityIterator like this:
newRow.getDetailEntity().getMasterEntity().getDetailEntity().insertRow(newRow);
It does not seem to me like an elegant solution and I really feel the association should be maintained at the entity level automatically.
Is this a bug or is there any other (more elegant) workaround?
Thank you,
Olivier

Hi Steve,
This is not a composition association. Actually, this is an association from a table to an intersection (many-to-many) table. The code in my service is based on the SRDemo, see SRServiceImpl#updateSkillsForCurrentStaff(List) and is called on a save button from a shuttle page.
The current master is the master I want it to belong to. The link to the master gets correctly saved in the database (just as in the SRDemo). We can also navigate from the master view row to the find the detail view row using the generated RowIterator. However, this does not work from the master entity row to the detail entity row. The problem is really at the entity level.
Thanx
Olivier

/RPM/ITEM_MODIFY is not taking custom number range for external ID during creation

Hi Experts,
I face an issue in trying to create projects through file using /RPM/ITEM_MODIFY.
I have been successfully able to create both item and project but it somehow is not taking the external number range for project ID that we had defined for the item type. It takes the SAP standard number for Project ID (external ID). I want the FM to create using the external number range that we use.
Can someone help me with this?
Regards,
Amit

It is not through PS project. No linkage as we have not integrated this with PS. It is through item.. check the code. This is just to check how to create from backend. This is where we don't get our custom project id. it takes sap project id.
DATA : ls_item_context type /RPM/TS_ITEM_CONTEXT.
DATA : ls_attributes type /rpm/ts_item_d_api.
data : ls_GUID Type /RPM/TT_GUID .
data : ls_detail_guid type /RPM/TT_GUID.
data : l_rc type i.
data : lT_ATTRIBUTES TYPE /RPM/TT_ITEM_D_API.
data : LV_NRLEVEL type NRLEVEL.
data : Lv_NRLEV type char20.
ls_item_context-CREATE_CPROJECT = 'X'.
ls_item_context-CPRO_TEMPLATE = '45A24B95FB43010200000000837FF54C'.
ls_attributes-portfolio_GUID = '456C418E3AED018800000000837FF54C'.
*ls_attributes-EXTERNAL_ID = '102680'.
*ls_attributes-parent_GUID = '4576F8DCF90B01F800000000837FF54C'.
ls_attributes-parent_GUID = '4717C6437A8D010A00000000837FF54C'.
ls_attributes-Proj_description = 'NEW TEST'.
ls_attributes-item_type = 'ZPEP_PT_31'.
*Select single NRLEVEL into lv_nrlevel from NRIV where OBJECT = 'ZPEP_NPO'.
*lv_NRLEVEL = Lv_NRLEVEL + 1.
*lv_NRLEV = lv_NRLEVEL.
*ls_attributes-EXTERNAL_ID = lv_NRLEV.
APPEND ls_attributes to lt_attributes.
CALL FUNCTION '/RPM/ITEM_MODIFY'
EXPORTING
    IV_LANGUAGE             = 'EN'
    IV_CHANGE_MODE          = 'C'
*   IV_COMMENTS             =
*   IV_SHORT_TEXTS          =
   IS_MODIFY_CONTEXT       = ls_item_context
IMPORTING
   EV_RC                   = l_rc
TABLES
    IT_ATTRIBUTES           = lt_attributes
*   IT_ACLS                 =
*   ET_MSG                  =
    ET_GUID                 = ls_GUID
    ET_DETAIL_GUID          = ls_detail_guid
If sy-subrc = 0.
CALL FUNCTION '/RPM/SAVE_CHANGES'
*   EXPORTING
*     IV_CHECK_ONLY           = /RPM/CL_CO=>SC_FALSE
*     IV_REMOVE_OBJECTS       =
*   IMPORTING
*     EV_RC                   =
*     ET_MSG                  =
    if sy-subrc = 0.
    endif.
endif.

Use a external parameter in a foreach loop container

Hi
I use a parameter P1 in a package
This package contains also a foreach loop container including a parameter P2 (P1 is on outside of the foreach loop container)
In this foreach loop container, I need to insert into a table T1 the parameter P1 and P2 from an execute sql task :
INSERT INTO T1 (F1, F2) VALUES (?,?)
My question : how to access to the P1 parameter in the container ?
Thx for your help

I assume when you say parameter its in term of USER Variables defined in packages if yes then its essentially a scope thing, just define the scope of variable to outside and you should be able to access it.
If you mean P1 is something you assign from the Foreach look then assign then store this parameter as variable then assign the variable as you want to use it.
Abhinav http://bishtabhinav.wordpress.com/

TopLink Entity Creation Factory

Is there a way I can customize the creation of the entities specified in persistence.xml? Instead of TopLink creating them, I'd like to create them myself using and then pass it on to TopLink? I'm looking for something like an ObjectFactory that I can implement and have TopLink use it. Is this possible?

I'm looking
for something like an ObjectFactory that I can
implement and have TopLink use it. Is this possible?In both Oracle TopLink and TopLink Essentials you can configure a descriptor's instantiation policy to use an Object Factory.
In Oracle TopLink you'd define an afterLoad method to customize the descriptor and in Essentials you'd define a customizer. Either way, the code to set the factory is the same. There are a number of variants of the useFactoryInstantiationPolicy method so use the one that best suits your needs. Here's one usage:
descriptor.getInstantiationPolicy().useFactoryInstantiationPolicy(MyFactory.class, "create");In this example, when TopLink needs to create an instance of the class of this descriptor, it'll call the static "create" method on MyFactory.
--Shaun

How to give all input parameter in creation of po via bapi

sir plez tell clear process of create po via bapi, i have done upto "BAPI_PO_CREATIVE1, then what to do, plez stepwise explain
thank Q

Dear Baskhar,
After BAPI_PO_CREATE1, you have to run BAPI_TRANSACTION_COMMIT to post
the data.
For example, from SE37:
You can goto menubar: Function Module
Test-> Test sequence,
Fill in BAPI_PO_CREATE1 then follow by BAPI_TRANSACTION_COMMIT .
Best Regards,
Ian Wong

Error while running JSP with custom tag

I am trying to run a jsp with a tag and I am getting the following error when I run the jsp:
"Unable to open taglibrary /WEB-INF/jsp/mytaglib.tld : Parse Error in the tag library descriptor: External parameter entity "%(DOCTYPE);" has characters after markup."
I have no idea what this is, can anyone help me here?
tx
-AB

Its difficult to tell without looking at your TLD file i.e. mytaglib.tld
However, a guess is that you may be refering to an invalid or otherwise corrupted DTD from your TLD.
Check that out.
The official DTD for TLDs in JSP 1.1 is http://java.sun.com/j2ee/dtds/web-jsptaglibrary_1_1.dtd
and the official DTD for TLDs in JSP 1.2 is http://java.sun.com/dtd/web-jsptaglibrary_1_2.dtd

I get "Error: DTDParse:" when using JAXB

I get the error:
Error: DTDParse: External parameter entity "%(null);"
when trying to run:
java -jar C:\jdk1.3.1_01\jre\lib\ext\jaxb-xjc-1.0-ea.jar -roots rxl_2_2.dtd rxl.xjs
I don't know what the error means. Can anyone help?

I took the command from one of the other posts. it appears that the "-roots" part was causing the error. I took this out and it works fine now.

EXTERNAL Entity refrence creation (XML)

Hi All
I am creation the XML file using SAP XML DOM Libarary objects.
My requirement is to create the EXTERNAL ENTITY file reference using DOCTYPE tag.
For Example
<;!DOCTYPE descriptSol [
<;!ENTITY % references SYSTEM "P_899200_SD01_01.ref">;
%references
]>
I am using following method to create it
lo_doc_type                 TYPE REF TO if_ixml_document_type,
lo_entity_dec               TYPE REF TO if_ixml_entity_decl,
          CALL METHOD go_document->;create_document_type
            EXPORTING
              name = 'descriptSol'
            RECEIVING
              rval = lo_doc_type.
          CALL METHOD go_document->set_document_type
            EXPORTING
              document_type = lo_doc_type.
          CALL METHOD lo_doc_type->create_ext_entity_decl
            EXPORTING
              is_parameter_entity = 'X'
              name                = 'references'
              notation            = ''
              public_id           = ''
              system_id           = 'P_899200_SD01_01.ref'
            RECEIVING
              rval                = lo_entity_dec
          CALL METHOD lo_doc_type->append_child
            EXPORTING
              new_child = lo_entity_dec
            RECEIVING
              rval      = lw_rval.
The Above code is working and creating following tag
<;!DOCTYPE descriptSol [
<!ENTITY % references SYSTEM "P_899200_SD01_01.ref">;
]>;
So % references at end of declaration is missing.
This type of entity is called as "EXTERNAL (PARSED) PARAMETER ENTITY Declaration".
Give your suggestions that whether i am using right method to created EXternal entity reference.
Thanks in advance
Sukhjinder Singh

Oracle XML Team wrote:
: Jie (guest) wrote:
: : I added an external entity in sample file class.xml
: : <!ENTITY SYSTEM class2 "class2.xml">
: : &class2;
: : Then I created a file class2.xml in the same directory and
run
: : the program
: : java SAXSample class.xml
: : I got the following error messages at the end of the output
: : ResolveEntity: null file:/D:/oxml/sample/class2.xml
: : Locator:null file:/D:/oxml/sample/class1.xml 24 9
: : Fatal error
: : Expected encoding instead of ?>
: : Did I do something wrong?
: : Thanks,
: : Jie
: What parse method are you using? Also the correct syntax should
: be:
: <!ENTITY class2 SYSTEM "class2.xml">.
: Oracle XML Team
: http://technet.oracle.com
: Oracle Technology Network
Sorry for my typo. I did use the correct syntax in my example
file. I didn't write any code. I just try to use the example
program "SAXSample" you provide in the sample directory, that is,
I was trying to use SAX API to parse a file which contains an
external entity.
null

EXTERNAL PARAMETER ENTITY CREATION

Similar Messages

Maybe you are looking for