Type table problem

Dear Friends,
We are currently working with Sap R/3 4.7 Enterprise System.
Obviously is the below line not allowed since I am receiving always an error message. Do you know a workaround for
data et_sublist type table.
Thansk in advance
Alexander

Hi,
I do not know what you exaclty mean but are you just want to create a internal table or an table type?
DATA: ta_mara type standard table of mara.
TYPE: tt_mara type standard table mara.
Again, I have difficulties to understand what you need.
Best regards,
Guido Koopmann

Similar Messages

Import object type table problem

After import database i didn't find (User define object type)
or tables based on object
PS. i create another user on the same server and import DMP to it
Thanks
Khalil Sakr

Hi,
I do not know what you exaclty mean but are you just want to create a internal table or an table type?
DATA: ta_mara type standard table of mara.
TYPE: tt_mara type standard table mara.
Again, I have difficulties to understand what you need.
Best regards,
Guido Koopmann

Problem with SUT into bin type table

When in SPRO in strategy -storage unit type search strategy - SUT in bin type table,we have only 30 entries possible.
BUt we need more somewhere like 150 records because of a bulk storage type with a lot of storage bins with different
size and therefore capacity. To define true exact capacity we need different bin types right?
I am not sure how to do this,maybe there is a option in settings to change 30 to 150 or 200 to make the table bigger?
Or any other solution will be great because we do need this because in the way it works now,we have a lot of problems
in putaway,we have huge realocations since we have not exact capacities but we had to group bins with similar capacity
but that means that three bins with 48, 52 and 56 capactiy all have 52.

If I remember correctly this has been asked numerous times before, try searching the discussions.
Anyway, you have a couple of possible solutions for this.
It is understandable that you don't want hundreds of reallocation on daily basis, and you don't want to lose the capacity otherwise, but it feels that your bins should and could have been planned a bit better, there is always a way to unify capacities, split bins, use the storage space in a more meaningful manner. This is the point where your optimization was supposed to be done, not in SAP. But anyway, you are stuck with what you have and here are the solutions that cross my mind.
1. Standard SAP:
Split the bins to multiple storage types, this way you will have 30 bin types, but they will have different capacity for different storage types (in OMM4). Easy and standard, but has the downside that you will have to manipulate with 5 storage types instead of 1. A bit of more customizing but will solve the problem. Also, storage type search will need to be changed to include all the STs... Might be harder to track the strategies but this is the only standard way that crosses my mind.
2. ABAP:
This is the solution I have used and works fine, though you will need an ABAP-er to complete this.
Create a z-table/view having the same structure as the standard one, just add 120 more fields.
Well, not only that, you will have to change the coding to use this custom table instead of standard one, and although this isn't the brightest solution since you won't be able to change this table in customizing in the predefined path in SPRO/OLML, but will need o do it in SM30.
Luckily both of the options should work fine if done correctly, I have used both of these, and both have up and down sides... But I would go with standard SAP if it doesn't complicate your life too much because of several more STs. If it does, go with ABAP.

Insert data into the xml schema-based xmltype table problem!

Hello, there,
I got problem in inserting data into the xmltype table after registered XML schema and created table. details see below:
1) xml schema:
<?xml version="1.0" encoding="UTF-8"?>

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="http://www.emergis.com/eHealth/EHIP/data/meta/profile:v1" targetNamespace="http://www.emergis.com/eHealth/EHIP/data/meta/profile:v1" elementFormDefault="qualified">
     
     <xs:simpleType name="RoutingType">
          <xs:restriction base="xs:string">
               <xs:enumeration value="Synch"/>
               <xs:enumeration value="Asynch"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="StatusType">
          <xs:restriction base="xs:string">
               <xs:enumeration value="ACTIVE"/>
               <xs:enumeration value="VOID"/>
               <xs:enumeration value="PENDING"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="SenderApplicationType">
          <xs:restriction base="xs:string">
               <xs:enumeration value="PR"/>
               <xs:enumeration value="CR"/>
               <xs:enumeration value="POS"/>
               <xs:enumeration value="CPP"/>
               <xs:enumeration value="Other"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="ServiceTypeType">
          <xs:restriction base="xs:string">
               <xs:enumeration value="IS"/>
               <xs:enumeration value="WS"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="RouteDirect">
          <xs:restriction base="xs:string">
               <xs:enumeration value="Request"/>
               <xs:enumeration value="Reply"/>
               <xs:enumeration value="None"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="Indicator">
          <xs:annotation>
               <xs:documentation>can we also change the value to "ON" and "OFF" instead? in this way this cn be shared by all type of switch indicator</xs:documentation>
          </xs:annotation>
          <xs:restriction base="xs:string">
               <xs:enumeration value="YES"/>
               <xs:enumeration value="NO"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="RuleType">
          <xs:restriction base="xs:string">
               <xs:enumeration value="ControlAct"/>
               <xs:enumeration value="WSPolicy"/>
               <xs:enumeration value="AccessControl"/>
               <xs:enumeration value="Certification"/>
               <xs:enumeration value="MessageConformance"/>
               <xs:enumeration value="Variant"/>
               <xs:enumeration value="Routing"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="HL7Result">
          <xs:restriction base="xs:string">
               <xs:enumeration value="ACCEPT"/>
               <xs:enumeration value="REFUSE"/>
               <xs:enumeration value="REJECT"/>
               <xs:enumeration value="ACK"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="IIPType">
          <xs:restriction base="xs:string">
               <xs:enumeration value="PUT"/>
               <xs:enumeration value="GET/LIST"/>
               <xs:enumeration value="NOTIF"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="ProfileTypeType">
          <xs:restriction base="xs:string">
               <xs:enumeration value="IIPProfile"/>
               <xs:enumeration value="BizOperationProfile"/>
               <xs:enumeration value="OrchestrationProfile"/>
               <xs:enumeration value="DomainObjectProfile"/>
               <xs:enumeration value="ServiceProfile"/>
               <xs:enumeration value="ExceptionProfile"/>
               <xs:enumeration value="CustomizedProfile"/>
               <xs:enumeration value="SystemProfile"/>
               <xs:enumeration value="HL7XMLSchemaProfile"/>
               <xs:enumeration value="EnricherParametersProfile"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="ParameterType">
          <xs:restriction base="xs:string">
               <xs:enumeration value="String"/>
               <xs:enumeration value="Object"/>
               <xs:enumeration value="Number"/>
               <xs:enumeration value="Document"/>
          </xs:restriction>
     </xs:simpleType>
     
     
     
     <xs:complexType name="ProfileType">
          <xs:annotation>
               <xs:documentation>
          1.Profile IS USED TO BE AN WRAPPER ELEMENT FOR ALL KIND OF PROFILES NO MATTER WHAT KIND OF PROFILE IT IS
          2.ProfileID used to uniquely identify the current profile
          3.ProfileData used to hold all the necessary profile related data
          </xs:documentation>
          </xs:annotation>
          <xs:sequence>
               <xs:element name="ProfileID" type="ProfileIDType">
                    <xs:annotation>
                         <xs:documentation>this will hold all the common attributes, espically the global unique identifier to the profile, no matter what type of profile is</xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element name="ProfileData" type="ProfileDataType">
                    <xs:annotation>
                         <xs:documentation>all the non-common profile meta data that attached to each specific profile type such as IIPProfile, OrchestrationProfile, and BizOperationProfile will be placed here</xs:documentation>
                    </xs:annotation>
               </xs:element>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="ProfileIDType">
          <xs:annotation>
               <xs:documentation>global unique identifier and all the common attributes across all different profiles, the @ID and @Type together will be used as the primary key to identify the profile data</xs:documentation>
          </xs:annotation>
          <xs:attribute name="ID" type="xs:ID" use="required">
               <xs:annotation>
                    <xs:documentation>ID is the global unique identifier to the profile, no matter what type of profile it is</xs:documentation>
               </xs:annotation>
          </xs:attribute>
          <xs:attribute name="Name"/>
          <xs:attribute name="Description"/>
          <xs:attribute name="Version">
               <xs:annotation>
                    <xs:documentation>version of the profile data</xs:documentation>
               </xs:annotation>
          </xs:attribute>
          <xs:attribute name="Type" type="ProfileTypeType" use="required">
               <xs:annotation>
                    <xs:documentation>value to identify the ProfileType type within
                    IIPProfile,BizOperationProfile,OrchestrationProfile,DomainObjectProfile
                    ServiceProfile,ExceptionProfile,SystemProfile,HL7XMLSchemaProfile,
                    EnricherParametersProfile,CustomizedProfile
                    </xs:documentation>
               </xs:annotation>
          </xs:attribute>
          <xs:attribute name="Status" type="StatusType" default="ACTIVE">
               <xs:annotation>
                    <xs:documentation>used to show the related profile data status like "ACTIVE","PENDING","VOID"...</xs:documentation>
               </xs:annotation>
          </xs:attribute>
          
     </xs:complexType>
     <xs:complexType name="ProfileDataType">
          <xs:annotation>
               <xs:documentation>meta data associated tightly to each specific type of profile</xs:documentation>
          </xs:annotation>
          <xs:choice>
               <xs:element name="EnricherParametersProfileData" type="EnricherParametersDataType">
                    <xs:annotation>
                         <xs:documentation>Enricher Parameters related profile data
               1. one instance of this type may contains all the related System metadata.
               2. idType part may use to identify different version/release/status
               </xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element name="ExtendProfileData" type="ExtendProfileDataType">
                    <xs:annotation>
                         <xs:documentation>If needed, any profile data not defined within the current release scope can be added here </xs:documentation>
                    </xs:annotation>
               </xs:element>
          </xs:choice>
     </xs:complexType>
     <xs:complexType name="ExtendProfileDataType">
          <xs:sequence>
               <xs:element name="ExtendProfile" type="xs:anyType" minOccurs="0"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="EnricherParametersDataType">
          <xs:sequence>
               <xs:element name="EnricherParameter" type="EnricherParameter" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="EnricherParameter">
          <xs:sequence>
               <xs:element ref="Enricher"/>
          </xs:sequence>
          <xs:attribute name="serviceName" type="xs:string" use="required"/>
          <xs:attribute name="interactionID" type="xs:string"/>
     </xs:complexType>
     <xs:element name="Enricher">
          <xs:annotation>
               <xs:documentation>Comment describing your root element</xs:documentation>
          </xs:annotation>
          <xs:complexType>
               <xs:sequence>
                    <xs:element name="Parameters" type="Parameters"/>
                    <xs:element ref="Section" maxOccurs="unbounded"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:complexType name="ValueType">
          <xs:attribute name="field" use="required"/>
          <xs:attribute name="value"/>
          <xs:attribute name="action"/>
     </xs:complexType>
     <xs:element name="Section">
          <xs:complexType>
               <xs:sequence>
                    <xs:element name="Value" type="ValueType" minOccurs="0" maxOccurs="unbounded"/>
                    <xs:element ref="Section" minOccurs="0" maxOccurs="unbounded"/>
               </xs:sequence>
               <xs:attribute name="path" use="required"/>
          </xs:complexType>
     </xs:element>
     <xs:complexType name="Parameters">
          <xs:sequence>
               <xs:element name="Parameter" minOccurs="0" maxOccurs="unbounded">
                    <xs:complexType>
                         <xs:attribute name="name" use="required"/>
                         <xs:attribute name="reference"/>
                    </xs:complexType>
               </xs:element>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="RuleList">
          <xs:annotation>
               <xs:documentation>an array of rules</xs:documentation>
          </xs:annotation>
          <xs:sequence>
               <xs:element name="Rule" type="RuleProfile" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="RuleProfile">
          <xs:attribute name="RName" use="required"/>
          <xs:attribute name="RType" type="RuleType" use="required"/>
          <xs:attribute name="Status" default="ON">
               <xs:annotation>
                    <xs:documentation>By default is ON (or if is missing)</xs:documentation>
               </xs:annotation>
          </xs:attribute>
          <xs:attribute name="Order"/>
          <xs:attribute name="Direction" type="RouteDirect">
               <xs:annotation>
                    <xs:documentation>Request / Reply</xs:documentation>
               </xs:annotation>
          </xs:attribute>
     </xs:complexType>
     
     
     
     <xs:element name="Profile" type="ProfileType">
          <xs:annotation>
               <xs:documentation>Profile IS USED TO BE AN WRAPPER ELEMENT FOR ALL KIND OF PROFILES NO MATTER WHAT KIND OF PROFILE IT IS</xs:documentation>
          </xs:annotation>
     </xs:element>
</xs:schema>
2)register xml schema:
SQL> begin
2 dbms_xmlschema.registerSchema
3 (
4 schemaurl=>'http://rac3-1-vip:8080/home/'||USER||'/xsd/EHIPProfile_v00.xsd',
5 schemadoc=>xdbURIType('/home/'||USER||'/xsd/EHIPProfile_v00.xsd').getClob(),
6 local=>True,
7 gentypes=>True,
8 genbean=>False,
9 gentables=>False
10 );
11 End;
12 /
PL/SQL procedure successfully completed.
SQL>
SQL>
3) xml data:
<?xml version="1.0" encoding="UTF-8"?>

<Profile xmlns="http://www.emergis.com/eHealth/EHIP/data/meta/profile:v1">
     <ProfileID Type="EnricherParametersProfile" Status="ACTIVE" ID="EnricherPP.ID.0001" Name="EnricherPP.ID.0001" Description="EnricherPP.ID.0001" Version="01"/>
     <ProfileData>
          <EnricherParametersProfileData>
               <EnricherParameter serviceName="LRS_BusinessDomainObject.lrs.businessDomainObject.domainObjectBuilder.concrete.ExceptionCreators:createExceptionV50CategoryCanonicalPart" interactionID="">
               <Enricher>
                    <Parameters>
                         <Parameter name="MESSAGE_ID" reference="test"/>
                    </Parameters>
                    <Section path="HEADER">
                         <Section path="RESPONSE_TYPE">
                              <Value field="value" value="I"/>
                         </Section>
                         <Section path="HL7_STANDARD_VERSION">
                              <Value field="value" value="HL7V3"/>
                         </Section>
                         <Section path="DESIRED_ACKNOWLEDGMENT_TYPE">
                              <Value field="value" value="NE"/>
                         </Section>
                         <Section path="SENDING_NETWORK_ADDRESS">
                              <Value field="value" value=""/>
                         </Section>
                         <Section path="SENDING_APPLICATION_IDENTIFIER">
                              <Value field="root" value="2.16.840.1.113883.3.133.1.3"/>
                              <Value field="extension" value=""/>
                         </Section>
                         <Section path="SENDING_APPLICATION_NAME">
                              <Value field="value" value="NL HIAL"/>
                         </Section>
                    </Section>
               </Enricher>
     </EnricherParameter>
          <EnricherParameter serviceName="LRS_BusinessDomainObject.lrs.businessDomainObject.domainObjectBuilder.concrete.DomainObjectCreators:createFindClientsAssociatedIdentifersRequestObject" interactionID="PRPA_IN101105CA">
               <Enricher>
                    <Parameters>
                         <Parameter name="MESSAGE_ID" reference="test"/>
                    </Parameters>
                    <Section path="HEADER">
                         <Section path="RESPONSE_TYPE">
                              <Value field="value" value="I"/>
                         </Section>
                         <Section path="HL7_STANDARD_VERSION">
                              <Value field="value" value="HL7V3"/>
                         </Section>
                         <Section path="PROCESSING_CODE">
                              <Value field="value" value="T"/>
                         </Section>
                         
                         <Section path="DESIRED_ACKNOWLEDGMENT_TYPE">
                              <Value field="value" value="NE"/>
                         </Section>
                         <Section path="RECEIVER_NETWORK_ADDRESS">
                              <Value field="value" value="prsunew.moh.hnet.bc.ca"/>
                         </Section>
                         <Section path="RECEIVER_APPLICATION_IDENTIFIER">
                              <Value field="root" value="2.16.840.1.113883.3.40.5.1"/>
                              <Value field="extension" value=""/>
                         </Section>
                         <Section path="SENDING_NETWORK_ADDRESS">
                              <Value field="value" value=""/>
                         </Section>
                         <Section path="SENDING_APPLICATION_IDENTIFIER">
                              <Value field="root" value="2.16.840.1.113883.3.133.1.3"/>
                              <Value field="extension" value=""/>
                         </Section>
                         <Section path="SENDING_APPLICATION_NAME">
                              <Value field="value" value="NL HIAL"/>
                         </Section>
                    </Section>
               </Enricher>
     </EnricherParameter>
          <EnricherParameter serviceName="LRS_BusinessDomainObject.lrs.businessDomainObject.domainObjectBuilder.concrete.DomainObjectContentEnrichers:enrichPRRequest" interactionID="">

<Enricher>
     <Parameters>
          <Parameter name="MESSAGE_IDENTIFIER" reference="test"/>
     </Parameters>
     <Section path="HEADER">
          <Section path="HL7_STANDARD_VERSION">
               <Value field="value" value="V3PR2"/>
          </Section>
          
          
          <Section path="PROCESSING_CODE">
               <Value field="value" value="T"/>
          </Section>
          
          <Section path="PROCESSING_MODE_CODE">
               <Value field="value" value="T"/>
          </Section>
          
          <Section path="DESIRED_ACKNOWLEDGMENT_TYPE">
               <Value field="value" value="NE"/>
          </Section>
          
          
          <Section path="RECEIVER_APPLICATION_IDENTIFIER[0]">
               <Value field="root" value="2.16.840.1.113883.3.40.1.14"/>
               <Value field="extension" value="SIT1"/>
          </Section>
          
          <Section path="RECEIVER_APPLICATION_NAME[0]">
               <Value field="value" value="receiverAppName"/>
          </Section>
          
          
          <Section path="RECEIVER_AGENT/RECEIVER_ORGANIZATION/RECEIVER_ORGANIZATION_IDENTIFIER[0]">
               <Value field="root" value="2.16.840.1.113883.3.40.4.1"/>
               <Value field="extension" value="receiverOrgId"/>
          </Section>
          <Section path="SENDING_APPLICATION_NAME[0]">
               <Value field="value" value="NLPRSCLNT"/>
          </Section>
          
          
          <Section path="SENDING_AGENT/SENDING_ORGANIZATION/SENDING_ORGANIZATION_IDENTIFIER[0]">
               <Value field="root" value="2.16.840.1.113883.4.3.57"/>
               <Value field="extension" value="3001"/>
          </Section>
          <Section path="PERFORMER/HEALTHCARE_WORKER_IDENTIFIER[0]">
               <Value field="root" value="2.16.840.1.113883.4.3.57"/>
               <Value field="extension" value="HIAL_USR"/>
          </Section>
     </Section>
     <Section path="PAYLOAD">
          
          
          <Section path="AUDIT[0]/AUDIT_INFORMATION">
               <Value field="code" value="LATEST"/>
               <Value field="codeSystem" value="PRSAuditParameters"/>
          </Section>
          
          <Section path="CONFIDENCE/CONFIDENCE_VALUE">
               <Value field="value" value="100"/>
          </Section>
          
          <Section path="HISTORY/INCLUDE_HISTORY_INDICATOR">
               <Value field="value" value="false"/>
          </Section>
          
          <Section path="JURISDICTION/JURISDICTION_TYPE">
               <Value field="value" value="NL"/>
          </Section>
          
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[0]">
               <Value field="code" value="GRS_ADDRESS"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[1]">
               <Value field="code" value="GRS_ELECTRONIC_ADDRESS"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[2]">
               <Value field="code" value="GRS_IDENTIFIER"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[3]">
               <Value field="code" value="GRS_ORGANIZATION_NAME"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[4]">
               <Value field="code" value="GRS_PERSONAL_NAME"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[5]">
               <Value field="code" value="GRS_REGISTRY_IDENTIFIER"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[6]">
               <Value field="code" value="GRS_TELEPHONE"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[7]">
               <Value field="code" value="PRS_CONDITION"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[8]">
               <Value field="code" value="PRS_CONFIDENTIALITY_INDICATOR"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[9]">
               <Value field="code" value="PRS_DEMOGRAPHIC_DETAIL"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[10]">
               <Value field="code" value="PRS_DISCIPLINARY_ACTION"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[11]">
               <Value field="code" value="PRS_INFORMATION_ROUTE"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[12]">
               <Value field="code" value="PRS_NOTE"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[13]">
               <Value field="code" value="PRS_PROVIDER_CREDENTIAL"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[14]">
               <Value field="code" value="PRS_PROVIDER_EXPERTISE"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[15]">
               <Value field="code" value="PRS_PROVIDER_RELATIONSHIP"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[16]">
               <Value field="code" value="PRS_STATUS"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[17]">
               <Value field="code" value="PRS_WORK_LOCATION"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[18]">
               <Value field="code" value="PRS_WORK_LOCATION_ADDRESS"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[19]">
               <Value field="code" value="PRS_WORK_LOCATION_DETAIL"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[20]">
               <Value field="code" value="PRS_WORK_LOCATION_ELECTRONIC_ADDRESS"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[21]">
               <Value field="code" value="PRS_WORK_LOCATION_INFORMATION_ROUTE"/>
          </Section>
          <Section path="RESPONSE_OBJECT[0]/PROVIDER_QUERY_RESPONSE_OBJECT[22]">
               <Value field="code" value="PRS_WORK_LOCATION_TELEPHONE"/>
          </Section>
          
          <Section path="ROLE_CLASS /ROLE_CLASS_VALUE">
               <Value field="value" value="LIC"/>
          </Section>
          <Section path="SORT_CONTROL[0]/SORT_CONTROL_ELEMENT_NAME">
               <Value field="code" value="PrincipalPerson.name.value.family"/>
          </Section>
          <Section path="SORT_CONTROL[0]/SORT_CONTROL_DIRECTION_CODE">
               <Value field="value" value="A"/>
          </Section>
     </Section>
</Enricher>
     </EnricherParameter>
          </EnricherParametersProfileData>
     </ProfileData>
</Profile>
the data is valid against the schema through XML Spy tool... and loaded into the XDB repository...
4) create table and insert data:
SQL> CREATE TABLE EHIP_PROFILE OF SYS.XMLTYPE
2 XMLSCHEMA "http://rac3-1-vip:8080/home/EHIPSBUSER1/xsd/EHIPProfile_v00.xsd" ELEMENT "Profile"
3 ;
Table created.
SQL>
SQL> alter table EHIP_PROFILE
2 add CONSTRAINT EHIP_PROF_PK PRIMARY KEY(XMLDATA."ProfileID"."ID",XMLDATA."ProfileID"."Type");
Table altered.
SQL>
SQL>
SQL>
SQL>
SQL> select xdbURIType('/home/'||USER||'/ProfileData/EnricherPP.ID.0001.xml').getClob() from dual;
XDBURITYPE('/HOME/'||USER||'/PROFILEDATA/ENRICHERPP.ID.0001.XML').GETCLOB()
<?xml version="1.0" encoding="UTF-8"?>
<!--Sample XML file generated by XMLSpy
SQL>
SQL>
SQL> insert into ehip_profile values(xmltype.createXML(xdbURIType('/home/'||USER||'/ProfileData/EnricherPP.ID.0001.xml').getClob()));
insert into ehip_profile values(xmltype.createXML(xdbURIType('/home/'||USER||'/ProfileData/EnricherPP.ID.0001.xml').getClob()))
ERROR at line 1:
ORA-21700: object does not exist or is marked for delete
what's the problem caused the "ORA-21700: object does not exist or is marked for delete" error?
Thanks in advance for your help?

Thanks Marco,
Here're my environment:
SQL> select INSTANCE_NUMBER, INSTANCE_NAME,HOST_NAME,VERSION from v$instance;
INSTANCE_NUMBER INSTANCE_NAME HOST_NAME VERSION
2 rac32 RAC3-2 10.2.0.3.0
I followed your suggested in the above, and always purge recyclebin, but still got the same problem. because in 10gr2, there's no dbms_xmlschema.purge_schema available,
and I did checked the recyclebin after force the delete of schema, nothing inside. any other recommendation?

Autonomous Trigger / Mutating Table Problem

We have a specific problem in one of our applications being developed where by the database needs to enforce a specific business requirement.
We need to use a database trigger to enforce some data integrity which involves more than one table as such cannot use standard constraint. The integrity has to be maintained in the database as the DML statements may be coming from a Java application or PL/SQL code as such we need the logic all in one place.
The problem being that within the trigger we need to examine the state of the table the trigger is associated with as well as one other table. Obviously using a trigger on a table that is being affected by DML statements causes the dreaded mutating table problem.
One suggested solution to this was to make the trigger or the code the trigger called autonomous. This allows the trigger to execute by only showing the trigger the original state of the table before any of the DML statements have affected it.
The problem is this seems to work for single row DML statements but not for multi row DML statements. In multi row the trigger only sees the original state of the table, not the state of the table plus the changes made by any other actions in the same DML statement.
Below I have shown an example of what I'm seeing.
I have grossly simplified the example code below to only refer to a single table and use stupidly simple logic
I do realise i appear to be implementing uniqueness in my own PL/SQL code, this is purely for the example.
CREATE TABLE mutate_test
id INTEGER NOT NULL,
value VARCHAR2(255) NOT NULL
ALTER TABLE mutate_test ADD CONSTRAINT pk_mutate_test PRIMARY KEY(id);
ALTER TABLE mutate_test ADD CONSTRAINT ck_mutate_test CHECK (value = UPPER(value));
CREATE OR REPLACE FUNCTION duplicate_found(in_value IN mutate_test.value%TYPE) RETURN BOOLEAN IS
PRAGMA AUTONOMOUS_TRANSACTION;
v_value_found INTEGER;
BEGIN
SELECT COUNT(*)
INTO v_value_found
FROM mutate_test
WHERE value = in_value;
IF v_value_found > 0 THEN
RETURN TRUE;
ELSE
RETURN FALSE;
END IF;
END;
CREATE OR REPLACE TRIGGER tr_mutate_test BEFORE INSERT OR UPDATE ON mutate_test
FOR EACH ROW
BEGIN
IF duplicate_found(:new.value) = TRUE THEN
RAISE_APPLICATION_ERROR(-20000,'Duplicate value found');
END IF;
END;
INSERT INTO mutate_test (id,value) VALUES (1,'CLIFF');
INSERT INTO mutate_test (id,value) VALUES (2,'SULA');
COMMIT;
SELECT * FROM mutate_test;
-- Should fail as row 1 already has a value of CLIFF
INSERT INTO mutate_test (id,value) VALUES (3,'CLIFF');
COMMIT;
SELECT * FROM mutate_test;
-- Should fail as row 1 is already set to CLIFF
UPDATE mutate_test SET value = 'CLIFF' WHERE id = 2;
COMMIT;
SELECT * FROM mutate_test;
UPDATE mutate_test SET value = 'CLIFFORD' WHERE id = 1;
COMMIT;
SELECT * FROM mutate_test;
INSERT INTO mutate_test (id,value) VALUES (3,'RONNY');
INSERT INTO mutate_test (id,value) VALUES (4,'TIM');
INSERT INTO mutate_test (id,value) VALUES (5,'MONIQUE');
COMMIT;
SELECT * FROM mutate_test;
-- Wanted result would be row 1 would be updated from CLIFFORD to CLIFF
-- and the others raise errors, or all of them raise errors.
UPDATE mutate_test SET value = 'CLIFF' WHERE id IN (1,3,4);
COMMIT;
SELECT * FROM mutate_test;

This is all from a University application that deals with eLearning.
Shell = Mapping from the system to an external eLearning application, ie: unique id of the Blackboard course shell, or WebBoard board.
Term = Academic term
Sector = University sector, ie: Higher Education, TAFE, etc..
Resource = eLearning tool, ie: Blackboard, WebBoard, etc..
Resource Level = Whether the resource is being offered at a Course or Program level
Resource Mapping = Association of a resource to shell
What we are trying to achieve is that shells cannot be used across sector boundaries.
The real table structure is (grossly simplified again)
CREATE TABLE sector (sector_pk INTEGER PRIMARY KEY);
CREATE TABLE sector_pattern (sector_pk INTEGER REFERENCES sector(sector_pk), pattern CHAR(2) NOT NULL UNIQUE CHECK (pattern = UPPER(pattern)));
CREATE TABLE term (term_pk INTEGER PRIMARY KEY, term CHAR(4) NOT NULL UNIQUE CHECK (term = UPPER(term)));
CREATE TABLE resource_level (resource_level_pk INTEGER PRIMARY KEY, term_pk INTEGER REFERENCES term(term_pk));
CREATE TABLE shell_detail (shell_detail_pk INTEGER PRIMARY KEY);
CREATE TABLE resource_mapping (resource_mapping INTEGER PRIMARY KEY, resource_level_pk INTEGER REFERENCES resource_level(resource_level_pk), shell_detail_pk INTEGER REFERENCES shell_detail(shell_detail_pk));
Based on the Ask Tom article linked I'd liked to use a MATERIALIZED VIEW on the following query
SELECT DISTINCT rm.shell_detail_pk,sp.sector_pk
FROM resource_mapping rm, resource_level rl, term t, sector_pattern sp
WHERE rm.resource_level_pk = rl.resource_level_pk
AND rl.term_pk = t.term_pk
AND SUBSTR(t.term,3,2) = sp.pattern;
Then apply a UNIQUE constraint on that VIEW.
But I'm receiving a
SQL Error: ORA-12054: cannot set the ON COMMIT refresh attribute for the materialized view
I'm not sure how to create the MATERIALIZED VIEW LOG entries for the above VIEW.
Any ideas anyone? ;)
Need to do some more reading and research but as Tom says
"I'm asking around about the future of "SQL" as far as enhancments go like that
(will update when I get some feedback), but -- you are not limited to triggers
(in fact, I would avoid triggers as it is virtually IMPOSSIBLE to implement
cross row/cross object constraints with them!!!! at least correctly)"
So I think i'll give up on the TRIGGER approach as it doesn't meet our requirements.

Exporting parameter of type table in Method of a Class

Hi Experts,
I want to pass an internal table from my method in ABAP class to a workflow.
For thi spurpose i have cretaed a parameter of type table in the method.
My problem is that i am not able to bind this to a workflow/task container.
I can see all the other parameters of the method in thw workflow while binding except for the parameter of type table ( i.e internal table ).
Any idea ?
Thanks,
Radhika.

Assuming that you are trying to export the internal table from class method to task conatiner.
I have cretaed a Structure 'zemails' in se11
Already you have created a Structure in the SE11 , why don't you just create one Table Type of ZEMAILS in SE11. Once you hvae created in DDIC then in the class signature declare the ltmails of type the tabale type that you create. and then in the task conatiner also try to declare the container element with the same name and same table type.
In the class method declare the lt_mails as Exporting. save and actiavte. And one more thing if that element is not present in the Task conatiner then as soon as you try to open in the change mode and click on the binding button of the task it will prompt you asking whether you want to trnasfer the mssing elements if you clcik Yes then the same element which you have declared in the class will created with the same type. but make sure in the task conatiner you delcare the lt_mails as IMport export element.

How to execute STP with Named type table as parameter through ODBC calls.

Hi All,
I am using Oracle 10g release 2. I am having a Stored function which takes Named Type Table as its parameter.
For example
CREATE OR REPLACE TYPE tblName is table of someUDT.
CREATE OR REPLACE function nestfunction(t tblName)
return NUMBER
as
//function body here.
end;
Now, I want to call this Stored function nestfunction through ODBC calls. Also want to add multiple rows in tblName parameter.
But am unable to perform the above mentioned task. If you have answers please, reply.
Thanks and regards
ftil555

Hi Arik,
Thanks for the reply. I got the solution by configuring a NonXA data source. The problem was with internal commits of the fnd_global.initialize api.
If the DB adapter is calling aPL/SQL procedure (written inside a pakcage) using the data source configured to support XA, will expect not to have any commits in side the procedure or anywhere, the XA driver will take of the commits and whole transactions. By default the FND_GLOBAL.INITIALIZE(...) procedure will have the internal commits, so it was throwing the errors.
The solution was configuring the a NonXA Data source in the databae adapter configuration will allow the commits inside the callings procedures. So we created Two data sources one for XA and another for NonXA and we are using the NonXA datasource whereever we are calling the EBS APIs which have the internal commits.
-- Khaleel

No argument of type TABLE frm-10764 error

I'm trying to base a data block on a procedure. When I use a cursor ref there is no problem, however when I use a table I get the error no argument of type TABLE or REFCURSOR (frm-10764). In the package I have defined a table and I use an in out variable of the table type defined. In the block I reference the package.procedure and I get the above message. Can any one tell me what I'm doing wrong??
Thanks
Simon

Hello,
If i understood u guys correctly then here is example and it is working perfectly with F5.0 & O8.0. May be u will find some un-necessary code. pl. ingore it.
Step1- Create a stored Package Specification with declaration of ur REF Cursor.
package plsql_tab IS
--Declare REF Cursor Type
type plsql_refcur is ref cursor;
end plsql_tab;
Step2- Create ur own stored procedure and pass REF cursor as an argument.
procedure proc1
(p_cur in plsql_tab.plsql_refcur)
is
k pls_integer := 0;
var1 number;
var2 varchar2(50);
begin
loop
fetch p_cur into var1, var2;
exit when k>=10 or p_cur%notfound;
insert into plsq_tbl values
(k,'In Proc1 : '| |var2);
dbms_output.put_line('In Proc1 : '| |var2);
end loop;
close p_cur;
end;
Step3- Create a form, write form procedure like below and then call this procedure on WHEN-Button-Press or anywhere u needed.
procedure proc2 is
--declare REF Cursor
cur_plsql plsql_tab.plsql_refcur;
begin
--Open REF Cursor for a given Qry
open cur_plsql for select * from plsq_tbl
where rownum < 10;
--Pass REF Cursor as an IN Parameter
proc1(cur_plsql);
--Close REF Cursor
close cur_plsql;
end;
Hope it will help u.
Thanks & Regards,
Anil

Unknown type TABLE for element Error

This question i am posting on behalf of one of my friend
In RF transaction, created a screen that contains table control. The table control has created using wizard
If we run the transaction with in SAPGui its working fine. After creating Internet service, and publish and run thru internet explorer its giving the following said Error
" Unknow type TABLE for element IT_PRODUCT"
I checked the controls statement for table view , its there in the code Here IT_PRODUCT is tableview for tablecontrol
Any Info ?
a®

Solved.
The problem is because , the table control had been created thru "Table Control Wizard" , solved by creating the table control using SE51 has resolved the issue.
Strange ?
May be because wizard unncessary creating lot of HTML code while publishing
a®

To Use Cursor or TYPE table Index by PLS_integer

Hi All,
Let's see if I have table with no. of records 19,26,20,000.
If I want to loop through all the records which will be a optimized way To Use Cursor or TYPE table Index by PLS_integer.
Please guide.
Thanks.

What is it you want to do to/with the rows you're looping through?
Ideally you want to avoid looping, as that's row by row (aka slow by slow) processing and it's expensive time-wise.
If you're doing DML (insert/update/delete) then you're best off doing it in one sql statement, rather than looping.

Unable to read attribute of type TABLE

Hello IDM Gurus,
I was having some trouble reading data in the source tab from a temporary table created in a FROM AD Pass; specifically I am unable to read from an attrribute of type TABLE, which is being used for the memberOf attribute when reading members of a group from AD. I don't get any errors in the FROM Pass, nor do I get any errors when trying to read all other data from the temporary table; I'm able to read all data except the memberOf attribute of type TABLE; I've tried different variations of SELECT statements as well as different possible values in the destination tab but it still hasn't resulted in valid memberOf values from the temporary table.
I thought this would be a lot simpler than it's turned out to be; I would appreciate any help I could get on this issue.
Thanks a lot in advance!
Best regards,
Sandeep

Hi Achim,
Thank you for your quick response! I was actually able to spend a bit of time on the table itself and after experimenting a bit I managed to work out a query to correlate the memberOf values with the appropriate keys from the two separate tables in the same pass.
Thanks again for your suggestions!
Best regards,
Sandeep

A type table as a row in a table

The question is simple. Can I use a type table into a Z table ?? Any way to do this ??
Thanks in advance.

hi maraia,
Structures
A structure is a sequence of any other data types from the ABAP Dictionary, that is, data elements, structures, table types, or database tables. When you create a structure in the ABAP Dictionary, each component must have a name and a data type.
In an ABAP program, you can use the TYPEaddition to refer directly to a structure.
If you define a local data type in a program by referring to a structure as follows:
TYPES dtype TYPE structure.
the construction blueprint of the structure is used to create a local structure dtype in the program. The predefined Dictionary data types of the domains used by the data elements in the structure are converted into the corresponding ABAP types. The semantic attributes of the data elements are used for the corresponding components of the structure in the program. The components of the local structure dtype have the same names as those of the structure in the ABAP Dictionary.
To ensure compatibility with previous releases, it is still possible to use the LIKE addition in an ABAP program to refer to a structure in the ABAP Dictionary (except in classes).
Suppose the structure STRUCT is defined as follows in the ABAP Dictionary:
Field name
Type name
Short Description
COL1
CHAR01
Character field with length 1
COL2
CHAR08
Character field with length 8
COL3
CHAR10
Character field with length 10
The types CHAR01 to CHAR10 are data elements with corresponding domains. We can refer to this structure in ABAP:
TYPES struct_type TYPE struct.
DATA wa TYPE struct_type.
wa-col1 = '1'.
wa-col2 = '12345678'.
wa-col3 = '1234567890'.
This program creates a local structure in the program - struct_type - and a corresponding data object wa. We can address the components using the component names from the original structure.
Table types
Table types are construction blueprints for internal tables that are stored in the ABAP Dictionary. When you create a table type in the ABAP Dictionary, you specify the line type, access type, and key. The line type can be any data type from the ABAP Dictionary, that is, a data element, a structure, a table type, or the type of a database table. You can also enter a predefined Dictionary type directly as the line type, in the same way that you can with a domain.
In an ABAP program, you can use the TYPEaddition to refer directly to a table type.
If you define a local data type in a program by referring to a table type as follows:
TYPES dtype TYPE table.
the construction blueprint of the table type is used to create a local internal table dtype in the program. The predefined Dictionary data types of the domains used by the data elements in the structure are converted into the corresponding ABAP types. The semantic attributes of the data elements are used for the corresponding components of the internal table in the program.
Suppose the table type STRUCT_TABLE is defined in the Dictionary with the line type STRUCT from the previous example. We can refer to this in ABAP:
TYPES table_type TYPE struct_table.
DATA: table_wa TYPE table_type,
line_wa LIKE LINE OF table_wa.
LOOP AT table_wa INTO line_wa.
WRITE: line_wa-col1, line_wa-col1, line_wa-col1.
ENDLOOP.
This program defines an internal table type table_type . From it, we define data objects table_wa and, consequently, line_wa. line_wa corresponds to the line type of the table type in the Dictionary, and is therefore compatible with the structure STRUCT
Type Groups
Before Release 4.5A, it was not possible to define standalone types in the ABAP Dictionary to which you could refer using a TYPEaddition in an ABAP program. It was only possible to refer to flat structures. Structures in programs corresponded to the structures of database tables or structures in the ABAP Dictionary. In ABAP programs, you could only refer to database tables and structures in the ABAP Dictionary using LIKE. It was, however, possible to refer to individual components of the Dictionary type. Complex local data types such as internal tables or deep structures had no equivalent in the ABAP Dictionary. The solution to this from Release 3.0 onwards was to use type groups. Type groups were based on the include technique, and allowed you to store any type definitions globally in the Dictionary by defining them using TYPES statements.
The definition of a type group is a fragment of ABAP code which you enter in the ABAP Editor. The first statement for the type group pool is always:
TYPE-POOL pool.
After that, you define data types using the statement TYPES. It was also possible to define global constants using the CONSTANTS statement. All the names of these data types and constants must begin with the name of the type group and an underscore: pool_
In an ABAP program, you must declare a type group as follows before you can use it:
TYPE-POOLS pool.
if you want complete info just click
http://help.sap.com/saphelp_nw70/helpdata/en/fc/eb3138358411d1829f0000e829fbfe/content.htm
thanks
karthik
<REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Apr 15, 2008 3:09 PM

How to use PL/SQL type table in SQL FROM clause

Hi All,
I have to use a PL/SQL type table in our SQL statement as a table?
I am using the syntax (below) but it gives PL/SQL: ORA-00902: invalid datatype
SELECT ... FROM TABLE(CAST( var_pl/sql_table AS pl/sql_table)) tab WHERE tab.a=1;
Plz reply with an example.
Thanks.. Ratan

You don't need a cast!!!
     select *
     from table ( <nested_table> )
     where <condition>Anyway, are you sure that tab.a is a number?
Here follows an example with an useful function
CREATE OR REPLACE
type string_table as table of varchar2(4000)
CREATE OR REPLACE
FUNCTION split_string (
     string IN varchar2,
     delimiter IN varchar2
) RETURN string_table IS
     tab string_table;
     pre integer;
     post integer;
     step integer;
     i integer;
BEGIN
     pre := 1;
     step := length(delimiter);
     i := 0;
     tab := string_table();
     loop
          tab.extend;
          i := i + 1;
          post := instr(string,delimiter,pre);
          if ( post = 0 ) then
               tab(i) := substr(string,pre);
               return tab;
          end if;
          tab(i) := substr(string,pre,post-pre);
          pre := post + step;
     end loop;
END;
select * from table (split_string('abc,dfg,hij',','))
Query finished, retrieving results...
                                  COLUMN_VALUE
abc
dfg
hij

Dynamic Internal Table problem

Hello all,
I have created a Dynamic ALV using RTTS classes like cl_abap_structdescr,cl_abap_tabledescr and cl_abap_datadescr.
The number of columns to be displayed is dynamic and i am able to display the same.
Now i need to perform SUBTOTAL on few of the columns.
In dynamic table how do i assign those columns as Type 'I' so that i can perform DO_SUM.
I used the method GET_I of class cl_abap_elemdescr but unable to achive the same.
Kindly suggest.
Regards,
Arun

I know when I need to create a dynamic alv I use the following (plumbing code removed).
DATA: it_field_catalog      TYPE lvc_t_fcat.
DATA: dyn_table             TYPE REF TO data.
FIELD-SYMBOLS: <dyn_table>         TYPE table.
create your alv as normal. Or auto create the entries based on the tables, whatever conditions you use to determine the structure of the table at run time.
ls_fcat-fieldname   = '???'.
ls_fcat-inttype     = '?' .
ls_fcat-outputlen   = '?' .
ls_fcat-coltext     = '?' .
ls_fcat-seltext     = '?' .
ls_fcat-f4availabl = '?'.
ls_fcat-edit        = '?'.
ls_fcat-key         = '?'.
APPEND ls_fcat TO it_field_catalog .
    CALL METHOD cl_alv_table_create=>create_dynamic_table
       EXPORTING it_fieldcatalog = it_field_catalog
       IMPORTING ep_table        = dyn_table
       EXCEPTIONS
              generate_subpool_dir_full = 1.
   ASSIGN dyn_table->* TO <dyn_table>.
This field symbol to the table can then be passed in place of the table when calling your alv and performing operations on it.

Dump while executing class method whose exporting parameter of type table

hi,
i am getting dump after executing a method in which i want to export an internal table which will hold all the states name along with its code on the basis of the country name which is my importing parameter.
for the above i am using importing parameter named as country of type too5u-land1 and the exporting parameter named as itab of type table and below is my code for the requirement.
method PROCESS.
select BLAND BEZEI from T005U
         INTO TABLE ITAB WHERE
         LAND1 = COUNTRY.
endmethod.

Hi,
Please check the below code
parameters country type land1.
*Refer the class which we are using like below
data: a type ref to ZCL_TX_SERVICE_01.
data itab type ycountry.
*ycountry is a table type defined in dictionary with fields BLAND and BEZEI
data wa like line of itab.
*If we are using instance method we need to create the instance like below
create object a.
*In the method process define exporting parameter itab as type ycountry which is a table type already defined
CALL METHOD a->PROCESS
EXPORTING
    COUNTRY = country
IMPORTING
    ITAB    = itab.
loop at itab into wa.
write:/ wa-bland.
endloop.
Regards
Dande

Type table problem

Similar Messages

Maybe you are looking for