Subtype supertype and delegationtype

i need to create an object type zself which is delegated to BOR selfitem
on going to settings and clicking on delegate i see a few BOR objects i dont see self item so i went ot new entries and treid to create one
it asks for objecttype:?(is it selfitem)
delegation type:?
2.in the tcode swo1 i wrote zself and on the top of it there is subtype creation i ihave clicked on it it asked for super type where i have given it as selfitem
i could create one
but does it imply that it is delegated to selfitem with out physycally going to
settings tab and delegating

Hii Kittu,
For ur first query------
Yes, U need to give SELFITEM as object type and in delegation type, give z-object name and save it.
delegation will be created.
For ur 2nd Query-------
No, Subtype creation is similar to inheritance i.e. u have created a child of parent object, thus it accesses all the methods, attri etc.
. Now u can extend this for ur own requirement.
But delegation means the changes (rather extension u r doing in z-object), u can access it in standard object (In other words u r editing the standard object).
So u explicitly need to create a delegate for this. Only subtype creation is not suffice.
Another thing to add, U can create any no of subtypes for a BO but only 1 delegate for it.
hope it solves ur query.
<b>"Dont forget to reward points if helpful"</b>
regards,
Ashish

Similar Messages

  • How to implement SubType/SuperType in Oracle ?

    Hi,
    I have a supertype and three subtypes, as attached below, how is the
    best approach to implement it in Oracle (9i/10g) ?
    Thank you for your help,
    Krist
    Supertype : Employee
    Employee_Number
    Employee_Name
    Address
    Employee_Type
    Date_Hired
    SubType : Hourly_Employee
    Hourly_Rate
    SubType : Salaried_Employee
    Annual_Salary
    Stock_Options
    SubType : CONSULTANT
    Contract_Number
    Billing_Rate

    Assuming you want to model this relationally, try something like this.
    http://groups-beta.google.com/group/comp.databases.oracle.server/msg/a23ffb19bfde2f20?hl=en
    Note its a generic SQL approach, and somewhat over fussy but I think the genral approach holds up for this type of relationship.
    I would sort of stay away from objects in the database, it over complicates everything else you will ever do.

  • Change time constraint of Infotype 0006 subtype 1 and subtype 2

    Hi
    Can anyone tell me how to change the TC of infotype 0006 subtype 1 and subtype 2.
    Currently I tried to change the TC in table V_T582A but its giving me an error : "Text maintenance not permitted as infotype part of Data Sharing (T582G)  "
    Can anyone please advise.
    Currently the TC is T
    I want to change it to 2.

    hi ,
    you can use SE38 to create a report like :
    to change the time constraint for IT0006 +subty 1 + 2
    REPORT  ZTEST.
    tables: t591a.
    data: wt_tc type table of t591a.
    select * from t591a into table wt_tc where infty = '0006' AND
                                                 ( subty = '1' OR
                                                  subty = '2').
    if sy-subrc = 0.
    loop at wt_tc into t591a.
    t591a-zeitb = 'x'. "new TC that you need
    modify table t591a from t591a.
    endloop.
    endif.
    regards

  • Time constraint of Infotype 0006 subtype 1 and 2

    Hi All,
    Currently the TC of infotype 0006 subtype 1 is 1.
    I have changed it to 2, so that the gaps are there but no overlapping.
    However, when I go in SAP and create a new record, its delimiting the previous record. But if I click on change button, its overwriting the original record instead of delimiting it.
    Please advise what can be done regarding the same.

    So that means, whenever an employee updates his address from the front end, the create address standard BAPI should be fired to update the data in R/3.
    This will delimit the previous record, since I have maintained TC as 2 for subtype 1 and 2.
    Please correct me if I am wrong.

  • Resolving Supertypes and Subtypes in the Database Design Transformer

    Hi,
    I have a design question re. converting Logical to Physical Data Models in Designer.
    For the mapping approach from my ERD to my SMD, I chose the Implicit Subtype Implementation, i.e. separate tables for each subtype and for the supertype. However, the subtypes have all the supertype columns. I wondered why Designer enforces this? It makes my SMD very cluttered. I would prefer to have the supertype columns in the supertype only.
    But, before you ask, I know this can be avoided by chosing the Arc Implementation. The problem I have with this approach is that the supertype has a separate FK column for each subtype. I am potentially dealing with many subtypes (50+), so am concerned about the number of null id columns in the supertype table. (Have used this approach before, but with only a handful of tables.)
    Thanks,
    Antony

    The reason that DDT creates one FK column per subtype is that Oracle cannot enforce referential integrity if the same FK references more than one table. You could reverse the foreign keys and have the subtype tables reference the supertype table, but I'm not sure that DDT can generate this - I guess I'd have to try it. Actually, null columns take up little or no space, so they really shouldn't cause a problem. If I remember correctly, the keys are enforced as exclusive arcs - only one of the FKs can be not null.

  • Supertype and Subtypes

    Hello,
    I created an employees table with 3 types, although when I insert the values, it works but doesn't display the last value which is from a different type. Any idea how to fix this?
    DROP TYPE employees_type FORCE;
    DROP TYPE hourly_employees FORCE;
    DROP TYPE salaried_employee FORCE;
    DROP TYPE consultant_employee FORCE;
    DROP TABLE employees;
    CREATE OR REPLACE TYPE employees_type AS OBJECT
    emp_id CHAR(4) ,
    fname VARCHAR2(20),
    lname VARCHAR2(20),
    date_hired DATE ,
    emp_type CHAR(1)
    )NOT FINAL;
    CREATE OR REPLACE TYPE hourly_employees UNDER employees_type
    hourly_rate NUMBER(6,2)
    )NOT FINAL;
    CREATE OR REPLACE TYPE salaried_employee UNDER employees_type
    annual_salary NUMBER(9,2),
    stock_option     CHAR(1)
    )NOT FINAL;
    CREATE OR REPLACE TYPE consultant_employee UNDER employees_type
    contract_number NUMBER,
    billing_rate     NUMBER(8,2)
    CREATE TABLE employees OF employees_type;
    INSERT INTO employees
    VALUES (hourly_employees(1234,null,null,null,null,0));

    SQL> SELECT TREAT(VALUE(e) AS hourly_employees)
      2    FROM employees e
      3   WHERE VALUE(e) IS OF(hourly_employees);
    TREAT(VALUE(E)ASHOURLY_EMPLOYEES)(EMP_ID, FNAME, LNAME, DATE_HIRED, EMP_TYPE, HOURLY_RATE)
    HOURLY_EMPLOYEES('1234', NULL, NULL, NULL, NULL, 0)or
    SQL> SELECT e.*,
      2         TREAT(VALUE(e) AS hourly_employees).hourly_rate AS hourly_rate
      3    FROM employees e
      4   WHERE VALUE(e) IS OF(hourly_employees);
    EMP_ FNAME                LNAME                DATE_HIR E HOURLY_RATE
    1234                                                                0Regards

  • Can I use subtype/supertype Entity Object with JHeadstart ?

    Hi,
    I am using Generalization on our entity object design, i,e : Employee(SuperType), Hourly_Employee(SubType), SalariedEmployee(SubType), Consoltant(SubType). The attributes attached below.
    All SubTypes will EXTEND the supertype : Employee.
    The questions are :
    Can JHeadstart handle the generalized entity objects ?
    How can the UI look like with JHeadstart ?
    Thank you for your help,
    Krist
    Supertype : Employee
    Employee_Number
    Employee_Name
    Address
    Employee_Type
    Date_Hired
    SubType : Hourly_Employee
    Hourly_Rate
    SubType : Salaried_Employee
    Annual_Salary
    Stock_Options
    SubType : CONSULTANT
    Contract_Number
    Billing_Rate

    Krist,
    If I understand you correctly you want to have a number of View Object attributes in a page to be accessible through 'subtabs', and want the correct subtab to be shown when the 'discriminator' field is changed. I am sorry for the confusion, I got thrown off track with all the super-subtype Entity details, but in the UI you are only dealing with ViewObject (usages), and not Entity Objects.
    Anyway, we can not generate 'subtabs'. There is a feature on our 'Enhancement list' to make the Regions have a 'stacked' property, which I think would come pretty close to what you need: you could group ViewObject Atributes together in Regions, and 'stacked' Regions would be generated as tab pages. We have not implemented this feature yet, and even if we had, you would have to change it post-gen because in your case, you would not want the end user to be able to 'switch tabs', but only a change of the 'discrimitator' field should do that.
    We have shipped some templates, though, for creating subtabs for child groups. Perhaps you could take a look if some of that code could be useable for your.
    I would suggest the following approach:
    1.) In the application structure file, create 'Regions' for all subtypes, and in the BC4J Property Editor, assign the 'subtype' attributes to the corresponding Region.
    2.) Regenerate the page. Now you should have a separate 'header' element for each subtype, containing the appropriate attributes.
    3.) Now you will need to transform those 'headers' to 'subtype tabs'. You could do that by borrowing code from our 'tabbed child' templates, or, alternatively, you could use a similar, Javascript-based technique that we use for switching between Quick Search and Advanced Search.
    4.) Finally, you should device a mechanism to change the active tab when changing the 'discriminator' column in the area above the tabs, with the supertype fields.
    Hope this helps,
    Peter Ebell
    JHeadstart Team

  • ALE distribution of HR master data to CRM - subtype CELL and MAIL

    Hello,
    Overview/Introduction:
    we are using the ALE distribution of HR master data to CRM. The distribution has already been set up and it is running. We know that the infotype communication (0105) is especially distributing the subtypes 0010 (e-Mail) and 0020 (telephone number). This e-Mail address and the telephone number are stored in the business partner in the CRM system.
    For this infotype 0105 there are also the subtypes CELL (cell phone) and MAIL (e-Mail address). Unfortunately this cell phone number and the mail address (from subtype MAIL) are not stored at the business partner in CRM.
    Our request is on the one hand to store the data from subtype CELL into the field mobile number of the business partner. And on the other hand we want to store the e-mail address of subtype MAIL at the business partner instead of subtype 0010.
    For some reason it seems that these requests canu2019t be setup within SAP standard.
    So we found SAP note 758426 which suggests to use the BAdI HRALEX_INBOUND and the report RH_ENHANCE_BP_TEMPLATE.
    Problem:
    Now the problem is that the BAdI does not get called! The BAdI is active! We tried to set break points -> unfortunately did not stop! And we also implemented an endless loop in the BAdI -> even with this the system did not u2018stopu2019!?
    Any ideas?
    Thank you,
    Roman

    Hi,
    First you need to create a distribution model using transaction BD64 : Edit > Model View > create.
    Then you will need to maintain fields for description and technical name. In partner box you need to enter the source system (HR) and the target system (FI) in the second field. Then you need to assign a message type and filter settings if you need it. You need to create this distribution model in source system (HR).
    After, still in BD64, go to environment > change partner profile or transaction WE20
    Select your target system and enter the corresponding message type ( HRMD_A or HRMD_ABA depends on your scenario) with the correct customizing (receiver port, packet size, idoc type, syntax check and output mode).
    Then please do the same things in your source system using WE20 for your source system and define your inbound parameters (Process code HRMD, processing by function module : use trigger immediately if it is not a production system or else trigger by background program and this case you will need to run report RBDAPP01 to process Idocs).
    Once done, then go back to your model view in your source system (BD64) and go to Environment > generate partner profiles. Then please go to Edit > Model View > distribute
    After all these settings done, it should work.
    Please also check out documentation :
    http://help.sap.com/erp2005_ehp_04/helpdata/EN/82/933b90aa9e11d6b28800508b5d5211/frameset.htm
    Best Regards
    Christine

  • Subtypes and Supertypes help required urgently!

    Hi all
    Oracle Apex is proving to be the undoing of me as i find the Program really confusing and so i need help with my current situation.
    I am trying to create a database for an equine advertising website.
    Basically I have a supertable called ADVERTISEMENT
    I also have 6 subtables HORSES, EQUIPMENT, HORSE_BOXES, PRODUCTS, PROPERTY and SERVICES
    I am having a terrible time trying to implement this. I have tried creating supertypes and subtypes but I found that I wasnt able to implement forms from these types
    I tried to Just create them normally as tables seperate tables (Primary key from ADVERTISEMENT being the foreign key in the HORSES, EQUIPMENT, HORSE_BOXES, PRODUCTS, PROPERTY and SERVICES) but again i found it difficult as the foreign key index would not copy the primary key.
    I would just like a little help to prevent me going any greyer than i already am.
    Thanks very much
    Michael Oakman

    Hi
    Thanks very much for the responses.
    I decided to use super types and sub types purely because of my design model, basically using rules of inheritance (super table with all common attributes, sub tables with distinctive attributes) however I am seeing that apex is a royal pain in the backside in terms of implementing this. I've seen examples of people using the create type method but have not fully understood what is going on there, I figured if I just created the tables with the subtype primary key referencing to that of the super type(and being the same) that it would work normally, obviously not though.
    I will have a go at the master detail forms with tabs on same page and thanks for the idea, I'll have a go then let you know how I get on
    Once again thanks
    Michael Oakman

  • Attribute of  subtype  not showing in supertype after delegation

    Hi, i've created a subtype of BUS2089 called ZBUS2089 added some attributes and then delegated to the BUS2089 but the new attributes are not showing, Any ideas?
    Thanzs in advanced to all
    Regards
    Jaime

    Hi Martina,
    Try to test the supertype and see if the delegated method is there.
    If that don't work say something and we find the problem.
    regards
    Jaime

  • Am I right with my supertype/subtype tables creation

    hi there,
    i have subtype/supertype relationship with a disjoint rule and
    partial specialisation
    ---table supertype
    create table gift(
    gift_id number,
    constraint pk_gift primary key (gift_id));
    ---table subtypes
    create table stock(
    gift_id number not null,
    no_of_shares number,
    curr_price number,
    constraint pk_gift primary key (gift_id)),
    constraint uk_gift unique (gift_id)delete cascade);
    create table property(
    gift_id number not null,
    prop_address1 varchar2(5),
    prop_address2 varchar2(15),
    prop_address3 varchar2(20),
    post_code varchar2(8)'
    curr_prop_value number,
    constraint pk_gift primary key (gift_id)),
    constraint uk_gift unique (gift_id)delete cascade);
    create table cash(
    gift_id number not null,
    amount number,
    constraint pk_gift primary key (gift_id)),
    constraint uk_gift unique (gift_id)delete cascade);
    create table artwork(
    gift_id number not null,
    description varchar2(30),
    artist varchar2(10),
    curr_art_value number,
    constraint pk_gift primary key (gift_id)),
    constraint uk_gift unique (gift_id)delete cascade);
    could you point out any mistakes in terms of unique constraints
    and gift_id appearing as inherited by the subclasses from the
    superclass. Notice gift_id is inherited by the sub classes as
    primary key and not foreign key.
    Are there other ways of doing this assuming i am wrong?
    Much appreciation.
    Ayo

    Your unique constraints are unnecessary as primary key
    constraints enforce uniqueness.
    You should have foreign key contraints to indeicate that GIFT is
    the master of the sub-type tables...
    ...having said which: what is the point of GIFT - it has no
    attributes of its own so it is completely unnecessary.
    The fact that th esub types have no key of their own also makes
    me nervous. I would expect all subtypes to have a composite
    primary key eg. GIFT_ID, STOCK_NO.
    Furthermore, can a GIFT be both (say) STOCK and PROPERTY? If
    not then you will need to enforce that exclusivity, which is
    quite difficult to do. It's easier to do if you implement the
    subtypes in one table, thus:
    create table gift(
    gift_id number,
    GIFT_TYPE varchar2(5),
    stk_no_of_shares number,
    stk_curr_price number,
    prop_address1 varchar2(5),
    prop_address2 varchar2(15),
    prop_address3 varchar2(20),
    prop_post_code varchar2(8)'
    prop_curr_value number,
    cash_amount number,
    art_description varchar2(30),
    art_artist varchar2(10),
    art_curr_value number,
    constraint pk_gift primary key (gift_id));
    You can then create a check constraint that ensures that only
    columns relating to stock are filled when GIFT_TYPE = 'STK',
    artwork when GIFT_TYPE = 'ART', etc. Note the use of prefixes
    to make it easier to see which columns are for which type.
    This will impose a slight overhead in terms of space usage, but
    not as much as you think - empty varchar2 columns don't take up
    any space and you're saving the overheads of multiple tables.
    You could save additional space by amalgamating the value/amount
    columns into a single gift_value column.
    This implementation is not definitely better - these things
    often depend on what you're going to do with the tables and
    which business rules you need to enforce. If a gift can consist
    of stocks and cash then you should go for the multi-table
    approach otherwise go for a single table approach.
    regards, APC

  • Data Modeler: How to prevent auto surrogate key in supertype/subtypes?

    When forward engineering supertype/subtypes, how can I prevent the automatic creation of a surrogate key (propagated to all super/subs)? Data Modeler creates this SK only at the relational level. I have already defined a surrogate identifier in the logical; the intent is to engineer this to the relational model and propagate to each subtype.
    Thanks,
    Patrick

    Thank you Philip for the explanation. I'd like to dig into this a little deeper, as I may be misinterpreting your explanation, and especially the last bit ( "...but foreign keys from subtype table to super-type table are not created" ).
    My preferred super/subtype implementation consists of a supertype parent table (ideally with a [manually created] discriminator code value) and any number of subtype child tables, all referencing the parent (via FK column/RI). Note that RI is from the supertype/parent to each subtype/child table, not the other way round as Designer docs suggest (one of three different approaches: all-inclusive single-table, detail tables only, master/detail w/ RI from child to parent [arced]). The implementation I suggest ("the fourth way") allows the painless addition of a new subtype simply by creating a new child table and a new discriminator value for the parent. I've had consistent success using this approach with Designer for many years.
    I've verified this successfully with a bare bones logical (3 levels), with appropriate UID on supertype/parent. All seems to transform well to relational model (i.e., all tables have inherited the parent PK, and individual attributes transformed to columns in the appropriate tables). The transform did not include a SurrogateID column.
    However, the transform doesn't work quite so well in my full-blown Party model, even though I ensured that a UID was defined on the logical supertype/parent. also confirmed that Hierarchy relationships are defined between supertypes and subtypes. What else could I be doing wrong that causes the transform to create a SurrogateID column on each super/subtype table?
    And on a similar note: are you suggesting that SQLDev Modeler transforms a supertype/subtype hierarchy with RI from detail tables to the parent table (i.e., backwards) when selecting "Table for each entity"? This approach would require a new FK column added to the parent table whenever a new subtype table was required.

  • How can we track the flow of Delegation and how it differ with subtype

    HI,
    Do any can tell me the difference between the Delegation Object and SubType Object, and how to track when the delegation object is triggered and what is the need of delegation and the subtype.
    Issues is: I have developed the delegate object and iam not able to track that delegate object whether that object is triggered or not, now i want to know that whether my delegated object is triggered or not.
    Thanks,
    Ravi Kumar.

    hi
    use this link
    http://www.erpgenie.com/sap/abap/bor.htm
    Cheers
    Snehi

  • Loosing preset for Entity and Subtype generation

    I can change the two options in
      Entitiy Properties->Subtypes->Entitiy and subtypes generation preset
    and the change has some kind of effect. But when I save and reopen the model the changes are lost. And during the next engineering some strange things happen.
    Is this a bug in my model or a bug in the modeler?

    it's not a property, it's preset functionality - Entity Inheritance
    Philip

  • SDDM EA 3.1: Engineer to Relational Model (subtypes)

    It seems that mandatory attributes of entity subtypes become mandatory columns on the corresponding tables even when you engineer to "one table" (the super type).
    In that case I would expect that the column would become optional.
    Even better: a check constraint would verify that the column was not null for records belonging to the originating subtype.
    / Marc de Oliveira

    1) Funny, when I dropped the column, and had it recreated by the engineering process, it worked correctly. But re-engineering the old column kept setting it to mandatory even when I manually set it to optional. I have a sense that some of my objects are ignored by the tool... Only when I drop them and recreate them they seem to be recognized. I had the same issue with some entities that consistenetly did not got engineered into my relational model. Only when I created a new ER-diagram and included the same entities they would get engineered into the relational model...
    2) Designer did this. When a supertype table was generated in the "one table" mode there would always be a new column called SUBTYPE with a constraint allowing the short names of each subtype as values (ex: for the table PARTIES the SUBTYPE column could only contain the values PERS and ORG). With this in place you could create constraints such as "SUBTYPE = 'PERS' and FIRST_NAME is not null or SUBTYPE = 'ORG' and FIRST_NAME is null".
    Regards,
    Marc de Oliveira

Maybe you are looking for

  • Regarding: material report

    Hi, I am making a report in ehihc i have to display the minimum,maximum,reorder point and stock level of a material . plzz tell me the tables where i can have these data as i want to display the cureent status of stock level . reagrds, ric.s Edited b

  • Filtering Issues

    Hello Aperture Users, I am having filtering problems that do not make sense. When I filter a folder with in the library for "Calliope Hummingbirds" only I get 508 images but when I apply an additonal keyword of "Male" I get 1094 images that are the o

  • Forms Configurator - DFF Error?

    Hi guys, Please excuse the long post. I am currently investigating an issue with a form designed in 'Forms Configurator'. The form is used for a remote team to simply update a 'user id' field in a Descriptive Flexfield on the Person Form, and save it

  • Can't Conncet to an old DLINK wireless modem

    Hey all, I don't know if this is the right place to ask the question or get the answer but here goes nothing. I currently have a DLINK DI-714P+ Network System and I can't seem to connect onto the network with my Macbook on the mac os system. However,

  • Is my Motherboard Toast

    Hi all, Mac mini Core Solo / 1GB RAM / OS 10.4.6 fully software updated save the last security update. All functioning well for a few weeks, then put the mini to sleep for a few hours. Got the dreaded couldn't wake from sleep. Black screen all that.