Brief description of object type in TADIR

Go to:
SE11 -> Table TADIR -> show contents -> on the selection-screen click in the field "OBJECT" and browse - you will see a list of all object types.
My question: Where do I get from these brief descriptions? In whichsoever tables are these descriptions saved?

Hi Heiko.
I would like to suggest,
TJ03T - Texts for object types.
Hope that's usefull.
Good Luck & Regards.
Harsh Dave

Similar Messages

How to read PP01- Object type u0091Positionu0092- Description- Text

Hi All,
How to read PP01->Object type Position->Description->Text
I tried to use READ_TEXT but i am not able to figure out what combination
to be given in input fields of this BAPI.
Please Guide.
Regards

Hi Amit,
Thanks for reply.
It is coming in HRT1002 table which is linked with HRP1002 with field TABNR.
But problem is that I have to capture this value in BADI-HRBAS00INFTY.
Before save. Because with BADI i need to update data in it.
any solution of it?
Regards

Long text for object type.

Hi,
Is there any table which stores long text for object type?
I am fetching list of objects from table TADIR for particular user, I am getting objects as DOMA, TABL, PROG ..etc But I want long text for these object type for eg. Domain for DOMA, Program for PROG and so on.. Is there any method to get the long text for object type?
Regards,
Parshuram.

Hello Vinod,
Looks like the FM 'TRINT_OBJECT_TABLE' is tightly coupled to SAP CTS & hence the hard-coding! Also i don't see where the long text of the object is returned.
On the contrary if you check the FM 'DOCU_READ' you've the table DOKTL which stores the long text(or the documentation) of the object.
Btw, i'm not sure what did the OP actually mean by "long-text". Does he mean the documentation?
Dammit! I get it now. Imho, "description" should have been a more appropriate word
BR,
Suhas
Edited by: Suhas Saha on Jan 13, 2012 4:57 PM

Error in creation of Object Type from XML passed

Hi,
I am facing a problem creating a appropriate a object type for a XML.
Below are the details:
XML Passed
<mer_offer_action_data>
<form_id>
134039588
</form_id>
<action_cd>
OA
</action_cd>
<offer_decline_reason_cd>
</offer_decline_reason_cd>
<start_dt>
</start_dt>
<candidate>
<ds_prs_id>
109315
</ds_prs_id>
<ds_prs_id>
110534
</ds_prs_id>
<ds_prs_id>
110059
</ds_prs_id>
</candidate>
</mer_offer_action_data>
Types Declaration
+CREATE OR REPLACE type MER_OFF_CANDIDATE
AS
OBJECT
DS_PRS_ID NUMBER
CREATE OR REPLACE TYPE MER_OFF_CANDIDATE_t
AS
TABLE OF MER_OFF_CANDIDATE;
CREATE OR REPLACE type MER_OFFER_ACT_DATA
AS
OBJECT
FORM_ID NUMBER,
ACTION_CD VARCHAR2(6),
OFFER_DECLINE_REASON_CD VARCHAR2(6),
START_DT VARCHAR2(11),
CANDIDATE MER_OFF_CANDIDATE_t
CREATE OR REPLACE TYPE MER_OFFER_ACT_DATA_t
AS
TABLE OF MER_OFFER_ACT_DATA;
CREATE OR REPLACE type MER_OFFER_ACTION_DATA
AS
OBJECT
MER_OFF_ACT_DATA MER_OFFER_ACT_DATA_t
/+
My Declaration
+merOffActDataXML xmltype;
merOffActData MER_OFFER_ACTION_DATA := MER_OFFER_ACTION_DATA(MER_OFFER_ACT_DATA_t());+
Inside Pl/SQL block
+-- Converts XML data into user defined type for further processing of data
xmltype.toobject(merOffActDataXML,merOffActData);+
when I run the Pl/Sql block it gives me error
ORA-19031: XML element or attribute FORM_ID does not match any in type ORADBA.MER_OFFER_ACTION_DATA
which means the object type mapping is wrong
I would like to know whether the object type I had created is correct or not.
Thanks for your help
Beda

Bedabrata Patel wrote:
Below are the details:The details except for a description of the problem
I am facing a problem creating a appropriate a object type for a XML.And which error you are getting
Error in creation of Object Type http://download.oracle.com/docs/cd/E11882_01/server.112/e10880/toc.htm
And which version of Oracle you are getting the unknown error creating the unknown problem.

Error in creation of Object Type

Hi,
I am facing a problem creating a appropriate a object type for a XML.
Below are the details:
XML Passed
<mer_offer_action_data>
     <form_id>
          134039588
     </form_id>
     <action_cd>
          OA
     </action_cd>
     <offer_decline_reason_cd>
     </offer_decline_reason_cd>
     <start_dt>
     </start_dt>
     <candidate>
          <ds_prs_id>
               109315
          </ds_prs_id>
          <ds_prs_id>
               110534
          </ds_prs_id>
          <ds_prs_id>
               110059
          </ds_prs_id>
     </candidate>
</mer_offer_action_data>
Types Declaration
+CREATE OR REPLACE type MER_OFF_CANDIDATE
AS
OBJECT
DS_PRS_ID NUMBER
CREATE OR REPLACE TYPE MER_OFF_CANDIDATE_t
AS
TABLE OF MER_OFF_CANDIDATE;
CREATE OR REPLACE type MER_OFFER_ACT_DATA
AS
OBJECT
FORM_ID NUMBER,
ACTION_CD VARCHAR2(6),
OFFER_DECLINE_REASON_CD VARCHAR2(6),
START_DT VARCHAR2(11),
CANDIDATE MER_OFF_CANDIDATE_t
CREATE OR REPLACE TYPE MER_OFFER_ACT_DATA_t
AS
TABLE OF MER_OFFER_ACT_DATA;
CREATE OR REPLACE type MER_OFFER_ACTION_DATA
AS
OBJECT
MER_OFF_ACT_DATA MER_OFFER_ACT_DATA_t
/+
My Declaration
     +merOffActDataXML          xmltype;
     merOffActData          MER_OFFER_ACTION_DATA := MER_OFFER_ACTION_DATA(MER_OFFER_ACT_DATA_t());+
Inside Pl/SQL block
     +-- Converts XML data into user defined type for further processing of data
     xmltype.toobject(merOffActDataXML,merOffActData);+
Thanks for your help
Beda
Edited by: Bedabrata Patel on Jul 12, 2010 5:51 AM

Bedabrata Patel wrote:
Below are the details:The details except for a description of the problem
I am facing a problem creating a appropriate a object type for a XML.And which error you are getting
Error in creation of Object Type http://download.oracle.com/docs/cd/E11882_01/server.112/e10880/toc.htm
And which version of Oracle you are getting the unknown error creating the unknown problem.

Support for unit testing object types

There's a Feature Request that suggests expanding the unit test tool to object types:
Title
Provide object type support for unit tests
Description
In the current version (2.1.0.63) I can perform only unit test for packages, function and procedures. But we use a lot of object types in the database and would like to test them. When is a support for object types scheduled?
Average Rating
10
Development Comment
This is planned for the next release.
Status
Scheduled for 3.0
Although the status suggests inclusion in v3, in my current version 3.2.20.09 there is nothing.
This is clearly an important issue for those who have voted for it as it scores a perfect 10 on average rating.
Is there any sign of object types being supported in the 4.0EA1 release? There is a strong desire within my organisation to move to a more object-based approach to PL/SQL coding but until we are able to unit test easily there will be no real progress.

If you are ready to learn a little bit of Ruby then you can try [PL/SQL unit testing with Ruby|http://blog.rayapps.com/2009/11/27/oracle-plsql-unit-testing-with-ruby/]. ruby-plsql library [supports also PL/SQL object types|http://blog.rayapps.com/2009/11/25/more-oracle-data-types-supported-by-ruby-plsql-gem/] as input and output parameters and return values.

Need some help on procedure calling procedure using object type reg

dear all,
i need to test one procedure by passing only one value but how do i pass single value. i am showing the details of few section on which i am working on. here is few details about the package.
Description: package pkj_emp contains two procedure pkj_emp and procedure proc_rem.
purpose:based on passing dname values to procedure pkj_emp, cursor cur_emp will fetch empid from emp table and then we are passing 4 empid records to procedure proc_rem using empid object type.Inside the procedure proc_rem it will delete all 4 records of table A,B,C and D at one short.
Requirement:i need to test for only one value that means is it possible i can pass only one value using the cursor cur_emp.
create or replace package pkj_emp
TYPE obj_emp IS TABLE OF NUMBER INDEX BY BINARY_INTEGER;
procedure proc_emp(empid obj_emp);
create or replace package body pkj_emp
as
procedure(
dname varchar2;
as
cursor cur_emp is select emp_id from emp a,dept d
where a.deptid=d.deptid
and d.deptname=dname;
begin
count:=0;
               for cur_emp_rec in cur_emp LOOP
               empid(count) := cur_emp_rec.emp_id;
          IF (count = 4) THEN
               proc_rem(empid); // calling another procedure
               commit;
               END IF;
               count := count + 1;
               END LOOP;
end;
proc_rem(
empid obj_emp;
is
begin
delete from A where emp_id in (empid(0),empid(1),empid(2),empid(3));
delete from B where emp_id in (empid(0),empid(1),empid(2),empid(3));
delete from c where emp_id in (empid(0),empid(1),empid(2),empid(3));
delete from d where emp_id in (empid(0),empid(1),empid(2),empid(3));
end;
regards
Laxman

You have hardcoded your IN LIST in the REM procedure. I recommend changing the code to take a variable number of inputs. You could do something like the following:
SQL> CREATE TABLE A (ID NUMBER);
Table created.
SQL> CREATE TABLE B (ID NUMBER);
Table created.
SQL> CREATE TABLE C (ID NUMBER);
Table created.
SQL> CREATE TABLE D (ID NUMBER);
Table created.
SQL> INSERT INTO A VALUES(7566);
1 row created.
SQL> INSERT INTO B VALUES(7902);
1 row created.
SQL> INSERT INTO C VALUES(7876);
1 row created.
SQL> INSERT INTO D VALUES(7369);
1 row created.
SQL> CREATE OR REPLACE TYPE EMP_TYPE AS TABLE OF NUMBER(4);
2 /
Type created.
SQL> CREATE OR REPLACE PACKAGE PKJ_EMP
2 AS
3          PROCEDURE PKJ_EMP
4          (
5                  DNAME   IN      SCOTT.EMP.DEPTNO%TYPE
6          );
7
8          PROCEDURE REM
9          (
10                  pEMPList IN      EMP_TYPE
11          );
12 END PKJ_EMP;
13 /
Package created.
SQL> CREATE OR REPLACE PACKAGE BODY PKJ_EMP
2 AS
3          PROCEDURE PKJ_EMP
4          (
5                  DNAME   IN      SCOTT.EMP.DEPTNO%TYPE
6          )
7          AS
8                  pEMPList        EMP_TYPE := EMP_TYPE();
9                  i               NUMBER := 1;
10          BEGIN
11                  FOR r IN
12                  (
13                          SELECT EMPNO
14                          FROM    SCOTT.EMP
15                          WHERE   DEPTNO = DNAME
16                  )
17                  LOOP
18                          pEMPList.EXTEND;
19                          pEMPList(i) := r.EMPNO;
20
21                          i := i + 1;
22                  END LOOP;
23
24                  REM(pEMPList);
25          END PKJ_EMP;
26
27          PROCEDURE REM
28          (
29                  pEMPList IN      EMP_TYPE
30          )
31          AS
32          BEGIN
33                  DELETE FROM A WHERE ID IN (SELECT   COLUMN_VALUE FROM TABLE(pEMPList));
34                  DELETE FROM B WHERE ID IN (SELECT   COLUMN_VALUE FROM TABLE(pEMPList));
35                  DELETE FROM C WHERE ID IN (SELECT   COLUMN_VALUE FROM TABLE(pEMPList));
36                  DELETE FROM D WHERE ID IN (SELECT   COLUMN_VALUE FROM TABLE(pEMPList));
37          END REM;
38 END PKJ_EMP;
39 /
Package body created.
SQL> EXEC PKJ_EMP.PKJ_EMP(20);
PL/SQL procedure successfully completed.
SQL> SELECT * FROM A;
no rows selected
SQL> SELECT * FROM B;
no rows selected
SQL> SELECT * FROM C;
no rows selected
SQL> SELECT * FROM D;
no rows selected
SQL> spool off;HTH!

Running a SQL Script to Create an Object Type

When I do Database Development with JDeveloper and fellow the instruction at
http://www.oracle.com/technology/obe/obe1013jdev/dbdevelopment/obe_%20dbasedevmt.htm
and try to Running a SQL Script to Create an Object Type by Right-clicking emp_rec.sql in the editor and
choose Run in SQL*Plus > hrconn, the new Obuect type can not created. The screen flashs and I only got the
message
"Invoking SQL*Plus...
D:\oracle\product\10.2.0\db_1\BIN\cemutls.exe
hr@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521)))(CONNECT_DATA=(SID=ORCL)))
@emp_rec.sql" and nothing else (No error like JBO-XXXXX).
Can anybody Help Me? Thanks a lot!
SID: ORCL

Hi Simon,
Having had a closer look at your original message it seems that rather than selecting the SQL*Plus executable in the directory you have managed to select the file 'D:\oracle\product\10.2.0\db_1\BIN\cemutls.exe'.
If you go to 'Tools | Preferences' and select the 'Database Connections' node and alter the 'SQL*Plus Executable' field to 'D:\oracle\product\10.2.0\db_1\BIN\sqlplus.exe' and then try again, this should then work.
Regards,
Lisa

Can plsql return table of object type

Dear All,
I am trying to return a set of data using object type.
But i am able to return only a single row but I want to return multiple rows.
I am trying to create the procedure which will return the table of object type but I am not able to assign value to table of object type.
Any ideas will be appreciated.
Regards
Abhishek

ArchitectView wrote:
The intention is to create a tree structure of data.Is this structure stored in the database? If so, then what data model is used? Relational? Hierachical? Object?
Each of these have pros and cons. The object model has many when persisted in a database as it nowhere near as flexible and robust as relational. Simple example, you can define an object class called Address. You can define a collection class called addressList. You can make that collection class a column in the Customers table. This allows you to store multiple addresses for a customer - as part of the same row for a customer.
However, there is a data modeling issue here. How do you index the region code in the address to do region based sales and marketing queries? There is a performance issue here - every time a customer row is read, the Addresses column is also read and this column contains a collection of addresses... Expensive I/O wise.
If relational data model was used, there would have been an Addresses table. It would have had a region index. And every time you read a customer row, all the addresses of that customer is not automatically read into memory too.
This Pl/SQL is to be called by another program which will accept the tree structure.So PL/SQL is to deliver a tree structure class?
You have mentioned about the design being not optimal, please elaborate.
I am doing these steps to improve performance.
i already have a java code which creates the data in the tree form {common data model - XML} .
I am thinking that if I create the structure in database , it will be better for performance.What makes sense to me (performance, usability and data modeling wise) is to use a relational design to store the tree data in Oracle. Each tree item will have a unique identifier and an optional parent identifier. The latter will be a foreign key constraint to the unique identifier.
The PL/SQL procedure can use a hierachical SQL to select the relevant root nodes from the tree table (i.e. start with tree items that have null parent identifiers) and transform this into a XML and supply XML output.
This allows Java to call this PL/SQL procedure, and get XML in response.
An alternative would be to not use XML, but instead define the tree structure as Java expects it, using SQL advance data types (i.e. classes). But instead of using that for store of the tree's data, the PL/SQL proc uses it to transform the tree data (selected via a hierarchical query) into this class object structure.
The Java client then needs to have wrapper classes for these SQL classes - and when it calls the PL/SQL proc, it gets a class structure returned that it can natively use on its side.
This a tad more complex to do than the XML interface - but could be faster as the Java layer does not need to transform the XML into a local data structure... it gets an equivalent data structure directly from PL/SQL.
The only issue ito performance I can see, is attempting to use such an object structure also as data storage (Oracle table) structure. This is usually less than optimal. Fair to say, that relational data modeling still reigns supreme ito usability, integrity and performance. (at least within RDBMS products, like Oracle)

Oracle Object type

Can anyone tell me how to do this ? Thanks!!!
i have a table dept (dept_no, description) and trying to create an object type with member function to insert the values into the table. I would like to know, whether I have to member function with input parameter or just newdept.dept_ins.
create type depto OBJECT AS
( dept_no number(3),
description varchar2(100),
member PROCEDURE dept_ins);
create type body depto
member procedure dept_ins IS
begin
insert into dept(dept_no, description) values depto.dept_no, depto.description;
end dept_ins;
end;
null

Yould could check the type of the returned object:
ResultSet rs = ... ;
int columnIndex = ...;
Object o = rs. getObject( columnIndex );
System.out.println(o.getClass().getName());

Object Type HLPF

Hi All
What is Object Type HLPF in SAP.....?
Thanks In Advance,
Chetan

Creating Business Logic Callable Objects
Use
You use the Business Logic callable object type to make process flow decisions based on dynamic expressions. They can be defined for output parameters and result states and are evaluated at runtime depending on the actual values of the input parameters. This is possible without any coding or use of an external rule engine.
To construct dynamic expressions, you can use a built-in expression editor that provides predefined operators and functions, as well as a validation tool.
The following categories are available:
·        Text functions
·        Numeric functions
·        Date functions
·        Time functions
·        Conditional functions
·        Scientific functions
·        Operators
Prerequisites
You have the appropriate rights to work with Guided Procedures (GP) design time.
For more information, see Portal Roles.
Procedure
       1.      Open the gallery and from the contextual panel choose Create Callable Object.
       2.      From the Type list, select Process Control ® Business Logic and enter the required basic data as follows:
Parameter
Description
Name
Enter a name for the new object.
Description
Provide a short and meaningful description.
Original Language
Choose the language in which the translatable texts of the callable object definition are created.
Folder
Select a destination folder in the gallery.
You can either use an existing folder, or create a new one.
       3.      Choose Next.
The Define Object screen appears. You can see a short description of the object characteristics and purpose. Continue by choosing Next.
       4.      On the Define Input screen, choose Insert New to create input parameters. You can define an arbitrary set of input parameters.
       5.      Once you have created the parameters you need, choose Next to continue.
       6.      On the Define Output screen, choose Insert New to add output parameters.
You can have an arbitrary number of output parameters on the root level. However, you cannot create parameters of type Structure.
       7.      Choose Next to continue.
       8.      On the Set Configuration screen, enter expressions for the output parameters defined previously:
                            a.      Select an output parameter from the list and choose (Browse).
                            b.      If you are familiar with expression syntax, enter an expression in the text area on the left.
                            c.      If you are not sure about the syntax, use the predefined functions from the list on the right.
For a list of some frequently used functions, see Frequently-Used Dynamic Expressions in the SAP Visual Composer Documentation.
                            d.      To insert a function into the text area, expand a node and select the relevant entry.
Each of these functions provides a quick info text description with syntax rules and examples. To view this information, point at the specific entry in the list.
                            e.      To test the expression, choose Validate.
                              f.      Once you have defined the expression, choose Apply to save it.
       9.      If you want to define result states for the callable object, choose the Add option under Result States.
   10.      Enter a name for the new result state and choose Add State.
The state appears in the list.
   11.      Repeat steps 9 through 10 to define an arbitrary number of result states.
   12.      To define expressions for the result states you have created, select a result state from the list and follow the procedure in step 8.
Result state expressions should evaluate to Boolean.
   13.      Choose Next and Finish and Open.
Result
You can test the callable object in GP design time or include it in a process to test it in runtime. If you insert it in an action, you should be able to see all result states that you have defined.
Example
You can create a callable object that calculates the monthly payments to redeem a certain credit amount based on a specified interest rate and time period. It approves the credit request if the monthly payment does not exceed half the monthly income of the person and outputs the amount of the payment. Otherwise, it rejects the credit request.
This callable object has the following characteristics:
Parameter Type
Name
Type
Dynamic Expression (uses the technical names of the input parameters)
Input
First Name
Last Name
Income (monthly)
Credit amount
Period (years)
Interest rate (percent)
String
String
Double
Double
Integer
Double
Output
Name
Monthly Payment
String
Double
CAPITAL(@FirstName)& & CAPITAL(@LastName)
ROUND(@credit* POW((1+@interest/100), @period) /(12@period)100)/100
Result states
(all result states evaluate to Boolean)
Approved
@credit* POW((1+@interest/100), @period) /(12*@period)<(@income/2)
Rejected
@credit* POW((1+@interest/100), @period) /(12*@period)>=(@income/2)

/SAPQUERY/HR_LSO_TRNG1 Object type 'US' User

Hi ,
In InfoSet /SAPQUERY/HR_LSO_TRNG1 , I cannot change the "selection" in order to include the relation-ship to Object type 'US' User . Not in the list of "infotypes of related objects" under "change info-type selection" in transaction SQ02 .
How can I add that ? Thank you

Hi The SAP Query comprises five components:
      Queries
      InfoSet Query
      InfoSets
      User Groups
      Translation/Query
Classic reporting- the creation of lists, statistics and ranked lists- are covered by the InfoSet Query and Queries components. Other componentsu2019 range of functions cover the maintenance of InfoSets, the administration of user groups and also the translation of texts created in the SAP Query. All data required by a user for a report can be read from various tables.
To define a report, you first have to enter individual texts, such as titles, and select the fields and options, which determine the report layout. In the WYSIWYG (What You See Is What You Get) mode, you can edit the lists using Drag & Drop and various toolbars.
Overview:
The following sections describes the individual SAP Query components and provides general information about query areas, transport and authorizations
Menu Path     Used For     Transaction Code
à SAP Query à Queries     Maintaining Queries     SQ01
à SAP Query à InfoSets     Maintaining InfoSets     SQ02
à SAP Query à User Groups     Maintaining User Groups     SQ03
à Translation à Query     Language Comparision     SQ07
Query Components
The Queries component is used by end users to maintain queries.
You can carry out the following tasks:
      Execute Queries and Generate Lists
      Define Queries
      Change Queries
Infosets Components
      InfoSets are special views of data sources.
      An InfoSet describes which fields of a data source can be reported on in queries.
      InfoSets are assigned to user groups.
      End-users are able to work only with those InfoSets that are relevant to their particular area, as designated by the role or user group that they are assigned to.
      Eg: Vendor master data can be important in purchasing as well as in accountancy. The relevant InfoSet is assigned to both roles/user groups. This means that queries based on this InfoSet can be copied and executed by both groups.
User Groups Components
1.     The User Groups component is used to maintain user groups. The system administrator uses it to set up the work environment for end-users.
2.     Every user assigned to the user group is able to execute the query.
3.     Users are not allowed to modify queries from other user groups, although they may, under certain circumstances, copy and execute
Translation/Query Component
      A great deal of text is generated when defining queries, InfoSets, and user groups.
      The SAP Query displays these texts in the language that you chose when you logged on to the SAP system.
      You can compare the text languages using the component Translation/Query.
      A related text in one or more additional languages is made available for each of the texts created when defining the query.
Query Areas
A query area contains a set of query objects (queries, InfoSets, and user groups) that are discrete and consistent.
There are the following query areas:
      Standard area
      Global area
Standard Area
1.Client specific
2.Query objects are not attached to the Workbench Organizer
Advantage :-End users can develop queries (ad-hoc reports) in their own client that are not meant for use in the rest of the system.
Global Area
1.Cross client
2.Query objects are attached to workbench organizer
Advantage:-The global query area is well suited for centrally developing queries meant for use and distribution throughout the system.
Authorizations
End-users, system administrators, and translators must all be assigned the appropriate authorizations allowing them to work with the SAP Query.
In order to give individual users targeted, specific rights, the following options are available:
      Roles/user groups
      Authorizations
Steps to create a Query
Step     Description     TCODE
1     Create a infoset or functional area     SQ02
2     Assignment of user group to infoset     SQ03
3     Creation of query based on infoset     SQ01
Tools for Queries
The following are the tools to manage, create and change queries.
      Infoset Query
      Queries
      Quick viewer
SAP Query
Step-by-step procedure in configuring SAP Query
SAP R/3 Query tools (SAP Query) are based on the following four main components:
u2022     Query Areas
u2022     Query Groups
u2022     InfoSets
u2022      Administrative Decisions (Company-specific)
Configuration of the Query tools is done in the following manner:
u2022     Create Query Groups
u2022      Assign Users to Query Groups
u2022     Create InfoSets
u2022      Assign each InfoSet to a Query Group.
Create Query Groups
u2022        Go to Transaction SQ03.
u2022        Ensure that you are in the correct SAP Query area by navigating to Environment à Query Areas
u2022        Select the u201CStandard Area (Client-specific).
u2022        Now in the main screen, enter the name of the Query Group in the User Group field and click on CREATE
u2022        Enter the description of the User Group in the next popup that appears.
u2022        User Group ZSAPTECH_GRP is created.
Assign Users to Query Groups
u2022        Click on the u201CAssign Users and InfoSetsu201D button
u2022        Enter the SAP User-Ids of all the users you wish to include in the test group.
Click on SAVE to save your entries.
Create InfoSets
u2022        Go to transaction SQ02
u2022        Ensure that you are in the correct SAP Query area by navigating to Environment à Query Areas
u2022        Enter the name of the InfoSet you wish to create and click on CREATE.
u2022        Enter the title and the logical database on the popup screen that appears.
We have used the LDB F1S (Flight bookings related) for our demo purpose.
u2022        Change InfoSet screen appears.
u2022        Expand the tree on the left hand side to view the fields in each table. As seen on the screen, the left side of the screen shows the tables and the fields. The right side displays the field groups.
u2022        Now we need to assign fields to the field groups. These field groups will display in the SAP Query tool during reporting. Please note that only the fields that are included here will be available for field selection in the SAP Query Tool that uses this infoSet as a data source.
u2022        Select the field group on the right side and then drag and drop the fields from the left side to this field group. u2022        When all the required fields are added, click on SAVE.
u2022        Now generate the InfoSet by clicking on GENERATE.
Attach each InfoSet to a Query Group
u2022        Go to transaction SQ02
u2022        Enter the InfoSet name created above and click on u201CUser Group Assignmentu201D button.
u2022        Select the query group u201CZSAPTECH_GRPu201D from the above list and click on SAVE.

Program error: Object type of receiver cannot be determined

Hello Experts,
               Am getting this error "Program error: Object type of receiver cannot be determined" when creating internal orders using BAPI_INTERNALORDERS_CREATE. I read many forums, but they are not answered. I didn't get any solution. Any Solution Please.
Thanks in Advance

Here is my Code
TYPE-POOLS : TRUXS.
TYPES:BEGIN OF TY_COAS_SVALD,
      AUART TYPE AUFART,         "Order Type
      BUKRS TYPE BUKRS,          "Company Code
      KTEXT TYPE AUFTEXT,        "Description
      GSBER TYPE GSBER,          "Business Area
      WERKS TYPE WERKS_D,        "plant
      KDAUF TYPE KDAUF,          "Sales Order Number
      KDPOS TYPE KDPOS,          "Item
      USER0 TYPE AUFUSER0,       "Applicant
      USER1 TYPE AUFUSER1,       "Applicant's telephone number
      USER2 TYPE AUFUSER2,       "Person responsible
      USER6 TYPE AUFUSER6,       "Department
      KOKRS TYPE KOKRS,          "Controlling area
      AUFWAERS TYPE AUFWAERS,    "Currency
      END   OF TY_COAS_SVALD .
DATA : IT_RETURN LIKE BAPIRET2 OCCURS 0 WITH HEADER LINE.
DATA:T_COAS TYPE STANDARD TABLE OF TY_COAS_SVALD INITIAL SIZE 0,
    WA_COAS TYPE TY_COAS_SVALD.
PARAMETERs : p_file TYPE IBIPPARMS-PATH.
at SELECTION-SCREEN on VALUE-REQUEST FOR p_file.
PERFORM browse_file.
INITIALIZATION.
CLEAR:WA_COAS.
REFRESH:T_COAS.
START-OF-SELECTION.
PERFORM LOAD_FLAT_FILE.
PERFORM SUB_CALL_BAPI_FOR_KO01.
FORM browse_file .
CALL FUNCTION 'F4_FILENAME'
IMPORTING
   FILE_NAME           = p_file
ENDFORM.                    " browse_file
FORM LOAD_FLAT_FILE .
DATA : LT_RAW TYPE TRUXS_T_TEXT_DATA.
CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'
    EXPORTING
      I_FIELD_SEPERATOR          = 'X'
     I_LINE_HEADER              = 'X'
      I_TAB_RAW_DATA             = LT_RAW
      I_FILENAME                 = P_FILE
    TABLES
      I_TAB_CONVERTED_DATA       = T_COAS
   EXCEPTIONS
     CONVERSION_FAILED          = 1
     OTHERS                     = 2
IF SY-SUBRC <> 0.
ENDIF.
ENDFORM.                    " LOAD_FLAT_FILE
FORM SUB_CALL_BAPI_FOR_KO01 .
DATA:L_MASTERDATA TYPE BAPI2075_7,
       LE_MASTERDATA TYPE BAPI2075_2,
       T_BAPI TYPE STANDARD TABLE OF BAPI2075_6 INITIAL SIZE 0,
       WA_BAPI TYPE BAPI2075_6.
clear:l_masterdata,
      le_masterdata,
      wa_bapi.
refresh:t_bapi.
LOOP AT T_COAS INTO WA_COAS.
L_MASTERDATA-ORDER_TYPE = WA_COAS-AUART.
L_MASTERDATA-COMP_CODE = WA_COAS-BUKRS.
L_MASTERDATA-ORDER_NAME = WA_COAS-KTEXT.
L_MASTERDATA-PLANT = WA_COAS-WERKS.
L_MASTERDATA-BUS_AREA = WA_COAS-GSBER.
L_MASTERDATA-SALES_ORD = WA_COAS-KDAUF.
L_MASTERDATA-S_ORD_ITEM = WA_COAS-KDPOS.
L_MASTERDATA-APPLICANT = WA_COAS-USER0.
L_MASTERDATA-APPLICANT_PHONE = WA_COAS-USER1.
L_MASTERDATA-PERSON_RESP = WA_COAS-USER2.
L_MASTERDATA-DEPARTMENT = WA_COAS-USER6.
L_MASTERDATA-CO_AREA = WA_COAS-KOKRS.
L_MASTERDATA-CURRENCY = WA_COAS-AUFWAERS.
WA_BAPI-SALES_ORD = WA_COAS-KDAUF.
WA_BAPI-S_ORD_ITEM = WA_COAS-KDPOS.
WA_BAPI-COMP_CODE = WA_COAS-BUKRS.
APPEND WA_BAPI TO T_BAPI.
CALL FUNCTION 'BAPI_INTERNALORDER_CREATE'
      EXPORTING
        I_MASTER_DATA       = L_MASTERDATA
IMPORTING
   E_MASTER_DATA       = LE_MASTERDATA
TABLES
   SRULES              = T_BAPI
   RETURN              = IT_RETURN
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
ENDLOOP.
WRITE : / IT_RETURN-TYPE, IT_RETURN-MESSAGE.
ENDFORM.                    " SUB_CALL_BAPI_FOR_KO01

Issue with RCDC for Custom "Department" object type

Hey Guys,
Maybe somebody can point out where the issue is with the RCDC. I have a custom object type called Department in FIM portal and wanted to create a simple interface for it so users can add and edit department fields.
The only two fields that should show on the RCDC is department and divisions(this is the name of the custom field) all the fields work but I keep getting the following error "There's an error in the Department display configuration.Please contact your
system administrator"
Below is the RCDC:
<?xml version="1.0" encoding="utf-8"?>

<my:ObjectControlConfiguration xmlns:xd="http://schemas.microsoft.com/office/infopath/2003" xmlns:my="http://schemas.microsoft.com/2006/11/ResourceManagement" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<my:ObjectDataSource my:Name="object" my:TypeName="PrimaryResourceObjectDataSource"/>
<my:ObjectDataSource my:Name="delta" my:TypeName="PrimaryResourceDeltaDataSource"/>
<my:ObjectDataSource my:Name="rights" my:TypeName="PrimaryResourceRightsDataSource"/>
<my:ObjectDataSource my:Name="schema" my:TypeName="SchemaDataSource"/>
<my:XmlDataSource my:Name="summaryTransformXsl" <my:Parameters="Microsoft.IdentityManagement.WebUI.Controls.Resources.DefaultSummary.xsl"/>
<my:Panel my:Name="page" my:Caption="Default Configuration" my:AutoValidate="true">
<my:Grouping my:Name="_caption" my:Caption="Caption" my:IsHeader="true">
<my:Control my:Name="_caption" my:TypeName="UocCaptionControl" my:Caption="Create Department" my:Description="" my:ExpandArea="true">
<my:Properties>
<my:Property my:Name="MaxHeight" my:Value="32"/>
<my:Property my:Name="MaxWidth" my:Value="32"/>
</my:Properties>
</my:Control>
</my:Grouping>
<my:Grouping my:Name="DepartmentInformation" my:Caption="Department Information">
<my:Control my:Name="Department" my:TypeName="UocLabel" my:Caption="{Binding Source=schema, Path=Department.DisplayName}" my:Description="" my:RightsLevel="{Binding Source=rights, Path=Department}">
<my:Properties>
<my:Property my:Name="Required" my:Value="True"/>
<my:Property my:Name="Text" my:Value="{Binding Source=object, Path=Department, Mode=TwoWay}"/>
</my:Properties>
</my:Control>
<my:Control my:Name="Divisions" my:TypeName="UocDropDownList" my:Caption="{Binding Source=schema, Path=Divisions.DisplayName}" my:Description="{Binding Source=schema, Path=Divisions.Description}">
<my:Options>
<my:Option my:Value="" my:Caption="" my:Hint="Please Select a Division"/>
<my:Option my:Value="Division of Academic Affairs" my:Caption="Division of Academic Affairs"/>
<my:Option my:Value="Division of Administration" my:Caption="Division of Administration"/>
<my:Option my:Value="Division of Adult & Continuing Education" my:Caption="Division of Adult & Continuing Education"/>
<my:Option my:Value="Division of Information Technology" my:Caption="Division of Information Technology"/>
<my:Option my:Value="Division of Institutional Advancement" my:Caption="Division of Institutional Advancement"/>
<my:Option my:Value="Division of President's Office" my:Caption="Division of President's Office"/>
<my:Option my:Value="Division of Student Affairs" my:Caption="Division of Student Affairs"/>
</my:Options>
<my:Properties>
<my:Property my:Name="Required" my:Value="{Binding Source=schema, Path=Divisions.Required}"/>
<my:Property my:Name="ValuePath" my:Value="Value"/>
<my:Property my:Name="CaptionPath" my:Value="Caption"/>
<my:Property my:Name="HintPath" my:Value="Hint"/>
<my:Property my:Name="ItemSource" my:Value="Custom"/>
<my:Property my:Name="SelectedValue" my:Value="{Binding Source=object, Path=Divisions, Mode=TwoWay}"/>
</my:Properties>
</my:Control>
</my:Grouping>
<my:Grouping my:Name="summary" my:Caption="Summary" my:IsSummary="true">
<my:Control my:Name="summaryControl" my:TypeName="UocHtmlSummary" my:ExpandArea="true">
<my:Properties>
<my:Property my:Name="ModificationsXml" my:Value="{Binding Source=delta, Path=DeltaXml}"/>
<my:Property my:Name="TransformXsl" my:Value="{Binding Source=summaryTransformXsl, Path=/}"/>
<my:Property my:Name="Hint" my:Value="{Binding Source=schema, Path=%AttributeName%.Hint}"/>
</my:Properties>
</my:Control>
</my:Grouping>
</my:Panel>
</my:ObjectControlConfiguration>
Any advice is appreciated.

I don't know RCDCs well enough to debug it from the xml. One approach when I don't know something too well is to brute it. Copy one of the default RCDCs and make sure it's working then add the required attributes one by one checking that it works each
time. Once it's working with the added attributes remove all the ones you don't need. If that breaks it, go back to where it was working and remove them one by one.

Create object type from multiple tables for select statement

Hi there,
I have 3 tables as given below and I wish to create an object type to group selected columns as 'attribute' from multiple tables.
I need to create 2 input parameters to pass in - 'attribute' and 'attribute value' in PL/SQL and these 2 parameters will be
passing in with 'column name' and 'column value'. e.g. 'configuration' - the column name, 'eval' - the column value.
Then, the PL/SQL will execute the select statement with the column and column value provided to output the record.
Pls advise and thank you.
table ccitemnumber
name                           null     type
ccitemnumber                   not null varchar2(20)
configuration                           varchar2(20)
item_type                               varchar2(30)
table productmodel
productmodelnumber             not null varchar2(6)
description                             varchar2(60)
accesstimems                            number
numberofheads                           varchar2(2)
generation                              varchar2(10)
numberofdiscs                           varchar2(2)
factoryapplication                      varchar2(150)
table topmodel
stmodelnumber                  not null varchar2(30)
productfamily                           varchar2(60
formfactor                              varchar2(10)
modelheight                             varchar2(10)
formattedcapacity                       number
formattedcapacity_uom                   varchar2(20)
object type in database
configuration                           varchar2(20)
item_type                               varchar2(30)
numberofheads                           varchar2(2)
generation                              varchar2(10)
numberofdiscs                           varchar2(2)
factoryapplication                      varchar2(150)
modelheight                             varchar2(10)
formattedcapacity                       number
formattedcapac

user12043838 wrote:
Reason to do this as these fields are required to be grouped together as they are created in different tables. They are treated as 'attribute' (consists of many columns) of the part number. So, the PL/SQL is requested to design in a way able for user to pass in the column name and column value or part number, then the select statement should be able to query for the records. Another reason is a new column can be added easily without keep modifying those effected programs. Reuseable too.This basically equates to ... hard to code, hard to maintain, and poor performance.
Are you really sure you want to do this? This isn't going to be easy-street as you seem to think it is, but it's a one way street to a poorly performing system with security vulnerabilities (google SQL Injection).
I would highly recommend you reconsider your design decision here.

Brief description of object type in TADIR

Similar Messages

Maybe you are looking for