Data element on structure for interface

Hi all,
I'm working on the development of one interface from a non-sap system to SAP where on a first step SAP will capture a flat file into one structure "ZZZ" but I'm doubting about how to create this structure.
At first I was thinking on identifying a suitable component type/data element for each field (f.i. WAERS for currency field ZZZ-WAERS) but meanwhile I have noticed that for a similar interface the corresponding XXX structure was created using as data elements CHAR* type, where the * was the field length.
Which criteria would you choose in my case? and what will it depend on?
Thanks in advance.
Abdali

I think it is a good idea to use only CHAR-definitions for importing flat file data. Here the focus is to have a fixed column length and avoid conversion errors during import, as opposed to neat F1 help texts, for example.
When further processing the data inside SAP you can move the data to another structure with proper data elements (like WAERS or WRBTR), checking for consistency and catching conversion errors in the process.
Thomas

Similar Messages

  • How to find Where does Data Elements and structures are used ?

    Hi everyone .
    Is there any table which stores data elements/structures and where they are used ?
    If not is there any way to find by writing some <b>program</b> where does a data element or a structure is used ? Which tables will require for that ? If any one can give example it will be most helpful .
    Thanks and Regards,
    Kaushal N. Shah

    Hi Kaushal,
    DD04L stores the data elements.
    DD02L stores the structures.
    So you can query these tables & find them.
    Regards,
    Chetan.
    PS:Reward points if this helps.

  • Cannot change shift due date in Repayment Structure for Final Repayment

    Hi Expert,
         For creating new transaction of  product type 'Interest Rate Instrument' , In Repayment Structure for Flow type - Final Repayment I want to change working day from the default in "No Shift" to "Next working day" but the screen display in gray color.
    In this case i have not been post any flow types to G/L account.
         Do you have any ideas or the correct solution to solve my issue?
    Thank you in advance,
    PK
    Edited by: Pleassure on Feb 23, 2012 10:32 AM

    Hi,
    This is becuase you have settled the instrument. Please reverse the settlement , the required filed will be available for change.
    Brijendra

  • Procedure for creating transparent table, data element and domain

    Hi,
    Can anybody let me know the procedure for creating transparent table, data element and domain.
    Thanks,
    Mahathi

    Hi
    Database table and its components
    A database table is the central data structure of the ABAP/4 data dictionary.
    The structure of the objects of application development are mapped in tables on the underlying relational database.
    The attributes of these objects correspond to fields of the table.
    A table consists of columns (fields) and rows (entries). It has a name and different attributes, such as delivery class and maintenance authorization.
    A field has a unique name and attributes; for example it can be a key field.
    A table has one or more key fields, called the primary key.
    The values of these key fields uniquely identify a table entry.
    You must specify a reference table for fields containing a currency (data type CURR) or quantity (data type QUAN). It must contain a field (reference field) with the format for currency keys (data type CUKY) or the format for units (data type UNIT). The field is only assigned to the reference field at program runtime.
    The basic objects for defining data in the ABAP Dictionary are tables, data elements and domains. The domain is used for the technical definition of a table field (for example field type and length) and the data element is used for the semantic definition (for example short description).
    A domain describes the value range of a field. It is defined by its data type and length. The value range can be limited by specifying fixed values.
    A data element describes the meaning of a domain in a certain business context. It contains primarily the field help (F1 documentation) and the field labels in the screen.
    A field is not an independent object. It is table-dependent and can only be maintained within a table.
    You can enter the data type and number of places directly for a field. No data element is required in this case. Instead the data type and number of places is defined by specifying a direct type.
    The data type attributes of a data element can also be defined by specifying a built-in type, where the data type and number of places is entered directly.
    <b>Two Level Domain Example</b>
    A domain defines a field technically and therefore it may
    be used at different business levels.
    A data element describes the meaning of a domain in a certain business context.
    A domain, however, is used for the technical definition of a table field (for example field type and length).
    Therefore, although a take-off airport (data element S_FROMAIRP) would have a different business meaning from an airport where a plane lands (data element S_TOAIRP), they could still have the same domain(here S_AIRPID) because technically we could assign the same number of characters whether the airport is a take-off or a landing airport.
    <b>Definitions of Table in Database</b>
    In SAP R/3 tables are defined as
    A) Transparent tables: All of the fields of a dictionary table correspond to a field in the real database table.
    B) Pooled tables: Different tables which are not linked to each other with a common key are combined into a TABLE POOL. Several logical tables thus exist as a single real database table.
    C) Cluster tables: Several tables linked by a common key may sometimes be combined by the data dictionary and made to exist on the database schema as a single table.
    SAP is evolving R/3 tables in transparent tables.
    <b>Elaboration on each of the definitions</b>
    A transparent table is automatically created on the database when it is activated in the ABAP Dictionary. At this time the database-independent description of the table in the ABAP Dictionary is translated into the language of the database system used.
    The database table has the same name as the table in the ABAP Dictionary. The fields also have the same name in both the database and the ABAP Dictionary. The data types in the ABAP Dictionary are converted to the corresponding data types of the database system.
    The order of the fields in the ABAP Dictionary can differ from the order of the fields on the database. This permits you to insert new fields without having to convert the table. When a new field is added, the adjustment is made by changing the database catalog (ALTER TABLE). The new field is added to the database table, whatever the position of the new field in the ABAP Dictionary.
    Tables can also reside on the database as Pooled tables or cluster tables
    Pooled Tables: Different tables which are not linked to each other with a common key can be combined into a Table Pool. The tables contained within this pool are called Pooled Tables. A table pool is stored in the database a simple table. The table's data sets contain, in separate fields, the actual key for the data set to be stored, the name of the pooled table and the contents of the data set to be stored.
    Using this schema, several logical tables are combined into a single real database table. Although the data structure of each set is lost during the write to the table pool, it is restored during the read by the ABAP/4 Data Dictionary. The ABAP/4 Data Dictionary utilizes its meta-data to accomplish this.
    Since information must be prepared (defined) within the ABAP/4 Data Dictionary when it is read or written to (or accessed), this process itself defines these as not transparent tables
    Cluster Tables: Occasionally, several tables may be linked by a common key. The ABAP/4 Data Dictionary can also combine these tables into a single table. Each data set of the real table within the database contains a key and in a single data field, several data sets of the subsequent table for this key.
    As mentioned above, these table types require special data handling, therefore they are not transparent tables.
    <b>Technical Settings in Dictionary</b>
    The data class logically defines the physical area of the database (for ORACLE the table space) in which your table should be created. If you choose the data class correctly, the table will automatically be created in the appropriate area on the database when it is activated in the ABAP Dictionary.
    The most important data classes are master data, transaction data, organizational data and system data.
    Master data is data that is rarely modified. An example of master data is the data of an address file, for example the name, address and telephone number.
    Transaction data is data that is frequently modified. An example is the material stock of a warehouse, which can change after each purchase order.
    Organizational data is data that is defined during customizing when the system is installed and that is rarely modified thereafter. The country keys are an example.
    System data is data that the R/3 System itself needs. The program sources are an example.
    Further data classes, called customer data classes (USER, USER1), are provided for customers. These should be used for customer developments. Special storage areas must be allocated in the database.
    The size category describes the expected storage requirements for the table on the database.
    An initial extent is reserved when a table is created on the database. The size of the initial extent is identical for all size categories. If the table needs more space for data at a later time, extents are added. These additional extents have a fixed size that is determined by the size category specified in the ABAP Dictionary.
    You can choose a size category from 0 to 4. A fixed extent size, which depends on the database system used, is assigned to each category.
    Correctly assigning a size category therefore ensures that you do not create a large number of small extents. It also prevents storage space from being wasted when creating extents that are too large.
    Modifications to the entries of a table can be recorded and stored using logging.
    To activate logging, the corresponding field must be selected in the technical settings. Logging, however, only will take place if the R/3 System was started with a profile containing parameter 'rec/client'. Only selecting the flag in the ABAP Dictionary is not sufficient to trigger logging.
    Parameter 'rec/client' can have the following settings:
    rec/client = ALL All clients should be logged.
    rec/client = 000[...] Only the specified clients should be logged.
    rec/client = OFF Logging is not enabled on this system.
    The data modifications are logged independently of the update. The logs can be displayed with the Transaction Table History (SCU3).
    Logging creates a 'bottleneck' in the system:
    Additional write access for each modification to tables being logged.
    This can result in lock situations although the users are accessing different application tables!
    <b>Create transparent table</b>
    Go to transaction SE11. Enter name of table you want to create (beginning with Y or Z) and click on create pushbutton
    Enter the delivery class and the table maintenance criteria
    The delivery class controls the transport of table data when installing or upgrading, in a client copy and when transporting between customer systems .
    The display/maintenance indicator specifies whether it is possible to display/maintain a table/view using the maintenance tools Data Browser (transaction SE16) and table view maintenance (transactions SM30 and SM31).
    Enter the name of the table field and the data element. The
    System automatically populates the technical details for
    existing data elements.
    So far as possible it is advisable to use existing data elements which befit the business requirements.
    However, we may create data elements if need be. The same is shown in the next slide.
    To create a data element simply double click on it.
    Alternately create a data element by simply choosing the
    data type radio button on SE11 initial screen.
    <b>Create data element</b>
    The system prompts you to create a new data element.
    Choose the Yes pushbutton.
    Under the data type tab enter the domain name which
    determines the technical characteristics of the field.
    Further characteristics tab: Allows you to specify a search help assigned to the data element.
    It also allows you to specify a parameter id which helps you populate a field from SAP memory.
    Field label: Can be assigned as prefixed text to a screen field referring to the ABAP Dictionary. The text is displayed on the screen in the logon language of the user (if the text was translated into this language).
    <b>Create domain</b>
    If the domain does not exist in the data dictionary the
    system prompts you to create one.
    Give the technical characteristics under the definition
    tab. Value range allows you value restriction at domain
    level.
    Value range tab:
    As explained in the section Consistency through input checks one can restrict the possible values for a field at domain level itself by either entering fixed values or by specifying a value table under the tab Value range.
    <b>Currency/Quantity fields in a table</b>
    A currency or a quantity field must be assigned a reference field from a reference table containing applicable qty unit or currency unit.
    Field of the reference table, containing the applicable quantity unit or currency
    A field containing currency amounts (data type CURR) must be assigned a reference field including the currency key (data type CUKY).
    A field containing quantity specifications (data type QUAN) must be assigned a reference field including the associated quantity unit (data type UNIT).
    <b>Create transparent table continue</b>
    Maintain the technical settings of the table by clicking on the tab

  • Data element for time in 12 hour format HH:MM

    Hi friends,
    Is there any data element which is for HH:MM format 12 hour format?
    i see uzeit, but its HH:MM:SS. i dont want this.
    i want HH:MM.
    Niraja

    Rohan,
    I am trying to create a new Domain with data type Tims. Basically when i change the no. character to 4.. its not taking
    by default its making it as 6. How to make this to 4.
    i can give Numc, but i needed in HH:MM format.  with : in between.
    can u help me out.
    Niraja

  • Internal length ( dd03l-intlen ) of data element

    Hi Experts,
    I have created structure using data elements.
    intlen  updated in table dd03l is double than Whatever length I defined for data elements.
    e.g.
    I defined custom data element ZDEPOT  of domain type WERKS of type char 4.
    but it's length in table DD03L-INTLEN is 8 char.
    Please let me know what is the connection of data element and DD03L-INTLEN
    and how we can control it as per the length of domain.
    Thanks,
    Yogesh.

    Hmm, everything I can find in table DD03L with the domain WERKS shows up with INTLEN of 4 and INTTYPE of C.  Our custom data elements and structures appear to all have INTLEN values that match our LENG values.  Have you saved and activated your custom data element and your structure?
    - April King

  • Data elements visible on dynpros

    Hi there,
    I want to find out if a data element is visible for a customer (not only one - approximately 500). So I am looking for a report, which checks if a data element is on a dynpro (or selection list) or is in a structure and the corresponding field of the structure is on the dynpro? Or shall I write a new one?
    Kind regards,
    Norbert

    Hi,
    I dont know of any such standard report which would suit your requirement. By the way can u let me know how ur gonna do it.

  • Releation between fields and data element

    Dear Abapers,
    What is the relation between the fields and data element,  while cretion of fields system will ask the data element, can we have one data element to more than one fields.  Can you plese explain me.
    Regards

    Hi,
    data elements are structures defined in SAP Dictionary. 
    Fields you meen in a table? or in programs? in both places you create in reference to SAP Dictionary. 
    data element char20.  TEXT20
    Programs  data:  l_text type char20.
    Tables  ... field   ZTEXT  type CHAR20...TEXT20

  • A problem when using a data element in BAPI

    Hi there,
    I build a function module, and want to use it as a BAPI. But when I add the function module as a method of a BAPI object, it gives me the following error: data type xxxxx cannot be used for methods.
    I guess the problem happens because of the type of data element I used for the input parameter of the function module. Thus I tried many other data elements, but I keep getting the same error. I am really out of the game. Could anyone tell me which data element I should use for the input parameter of the function module? The function module has only one input parameter, which should be a string with length less than 100.
    Thank you so much!!
    Sincerely,
    Bing

    The function module has only one input parameter, which should be a string with length less than 256. (I tried many predefined data element like RPLM_STRING, but when I tried to add the function module as a method of BAPI, the SAP always gave me the error: data type xxxxx cannot be used for methods)
    It only has one output parameter: RETURN (associated type: BAPIRETURN)
    I am really not familiar with ABAP program, let alone BAPIs. Any suggestions would be very helpful to me. I sincerely appreciate your help.
    Bing

  • How to deal with the change of data element?

    Hi, experts
    My trouble's background is:
    A CBO table(ZIEBTCIITM) saves invoice items .
    There are three fields relevant to quantity in it.
    And they have the corresponding data elements with the same type QUAN,13 characters and 3 decimals.
    Now because the quantity is so small,for example 0.00004,that the 3 decimal digit is not suitable.
    I want to change the CBO table to adapt my business,so the quantity fields' decimal should be expanded firstly,and there are transction data in the CBO table.
    My question is :
    1) Is it necessary to backup the CBO table before data element change?
    2) What should I do is Only to expand the data elements' decimals?
    Anyone can give me suggestion?

    Hello Mic
    To be on the save side I would suggest to export the table entries to Excel and create a transport request containing the original table and its entries:
    R3TR TABL ZIEBTCIITM
    R3TR TABU ZIEBTCIITM *
    Next you should create your own data element (or search for a suitable standard data element), e.g. ZQUAN13_5 (13 digits, 5 decimals).
    Replace the data element of the DB fields with your new data element and activate the DB table.
    I expect that nothing will happen to the entries in the DB table except that your quantity fields should have 5 decimals now.
    Regards
      Uwe

  • How to get data from  INVFO structure

    Hi Guys,
                Can anybody tell me How to get the Data from INVFO structure for field WRBTR and i am also down loading from BSEG WRBTR field. so i have to display these 2 fileds in the Final Ouput of ALV grid. so can anybody tell me how to download INVFO-WRBTR value?
    Thanks,
    Gopi.

    Hi Gopi,
    INVFO is a structure of BSEG and other tables.
    You can get the WRBTR from BSEG table not from INVFO structure.
    Regards,
    Atish

  • FM to lock data element and messages

    Hi All,
    I need a FM to enque data element and messages for translation.
    I have found out one FM for ABAP program texts - ENQUEUE_EABAPTEXTE.
    Can you please tell me the corresponding ones for data element and messages.
    Thank you.
    Ajith

    Hi Krishna,
    Use function modules    enqueue_<<lock object>>u2019 and dequeue_<<lock object>>u2019
    With Regard's
    SHAIK.

  • How to read data from INVFO structure

    Hi Guys,
                Can anybody tell me how to get the Data from INVFO structure for field ZUONR as I have to assign it into  from BSEG-ZUONR field. using FI Assignment technique. so can anybody tell me any table where INVOF-ZUONR are stored in FV60 transaction?
    Thanks & Regards,
    Ashish

    Hi Ashish,
    I'm not clear with your query, however if you are looking for a table, where Assignment field for Park document is stored, you can use Table VBSEGK - Document Segment for Vendor Document Parking.
    Just park one doucment with FV60, and than go to SE16N give table VBSEGK, and pass this doucment number and company code to table VSEGK, or your assignment vlue in ZUONR fied.
    You will see your documents there.
    VSEGK-ZUONR
    Regards
    Javed

  • What is the best data structure for loading an enterprise Power BI site?

    Hi folks, I'd sure appreciate some help here!
    I'm a kinda old-fashioned gal and a bit of a traditionalist, building enterprise data warehouses out of Analysis Service hypercubes with a whole raft of MDX for analytics.  Those puppies would sit up and beg when you asked them to deliver up goodies
    to SSRS or PowerView.
    But Power BI is a whole new game for me.  
    Should I be exposing each dimension and fact table in the relational data warehouse as a single Odata feed?  
    Should I be running Data Management Gateway and exposing each table in my RDW individually?
    Should I be flattening my stars and snowflakes and creating a very wide First Normal Form dataset with everything relating to each fact? 
    I guess my real question, folks, is what's the optimum way of exposing data to the Power BI cloud?  
    And my subsidiary question is this:  am I right in saying that all the data management, validation, cleansing, and regular ETTL processes are still required
    before the data is suitable to expose to Power BI?  
    Or, to put it another way, is it not the case that you need to have a clean and properly structured data warehouse
    before the data is ready to be massaged and presented by Power BI? 
    I'd sure value your thoughts and opinions,
    Cheers, Donna
    Donna Kelly

    Dear All,
    My original question was: 
    what's the optimum way of exposing data to the Power BI cloud?
    Having spent the last month faffing about with Power BI – and reading about many people’s experiences using it – I think I can offer a few preliminary conclusions.
    Before I do that, though, let me summarise a few points:
    Melissa said “My initial thoughts:  I would expose each dim & fact as a separate OData feed” and went on to say “one of the hardest things . . . is
    the data modeling piece . . . I think we should try to expose the data in a way that'll help usability . . . which wouldn't be a wide, flat table ”.
    Greg said “data modeling is not a good thing to expose end users to . . . we've had better luck with is building out the data model, and teaching the users
    how to combine pre-built elements”
    I had commented “. . . end users and data modelling don't mix . . . self-service so
    far has been mostly a bust”.
    Here at Redwing, we give out a short White Paper on Business Intelligence Reporting.  It goes to clients and anyone else who wants one.  The heart
    of the Paper is the Reporting Pyramid, which states:  Business intelligence is all about the creation and delivery of actionable intelligence to the right audience at the right time
    For most of the audience, that means Corporate BI: pre-built reports delivered on a schedule.
    For most of the remaining audience, that means parameterised, drillable, and sliceable reporting available via the web, running the gamut from the dashboard to the details, available on
    demand.
    For the relatively few business analysts, that means the ability for business users to create their own semi-customised visual reports when required, to serve
    their audiences.
    For the very few high-power users, that means the ability to interrogate the data warehouse directly, extract the required data, and construct data mining models, spreadsheets and other
    intricate analyses as needed.
    On the subject of self-service, the Redwing view says:  Although many vendors want tot sell self-service reporting tools to the enterprise, the facts of the matter are these:
    v
    80%+ of all enterprise reporting requirement is satisfied by corporate BI . . . if it’s done right.
    v Very few staff members have the time, skills, or inclination to learn and employ self-service business intelligence in the course of their activities.
    I cannot just expose raw data and tell everyone to get on with it.  That way lies madness!
    I think that clean and well-structured data is a prerequisite for delivering business intelligence. 
    Assuming that data is properly integrated, historically accurate and non-volatile as well, then I've just described
    a data warehouse, which is the physical expression of the dimensional model.
    Therefore, exposing the presentation layer of the data warehouse is – in my opinion – the appropriate interface for self-service business intelligence.
    Of course, we can choose to expose perspectives as well, which is functionally identical to building and exposing subject data marts.
    That way, all calculations, KPIs, definitions, and even field names, and all consistent because they all come from the single source of the truth, and not from spreadmart hell.
    So my conclusion is that exposing the presentation layer of the properly modelled data warehouse is – in general - the way to expose data for self-service.
    That’s fine for the general case, but what about Power BI?  Well, it’s important to distinguish between new capabilities in Excel, and the ones in Office 365.
    I think that to all intents and purposes, we’re talking about exposing data through the Data Management Gateway and reading it via Power Query.
    The question boils down to what data structures should go down that pipe. 
    According to
    Create a Data Source and Enable OData Feed in Power BI Admin Center, the possibilities are tables and views.  I guess I could have repeating data in there, so it could be a flattened structure of the kind Melissa doesn’t like (and neither do I). 
    I could expose all the dims and all the facts . . . but that would mean essentially re-building the DW in the PowerPivot DM, and that would be just plain stoopid.  I mean, not a toy system, but a real one with scores of facts and maybe hundreds of dimensions?
    Fact is, I cannot for the life of me see what advantages DMG/PQ
    has over just telling corporate users to go directly to the Cube Perspective they want, that has already all the right calcs, KPIs, security, analytics, field names . . . and most importantly, is already modelled correctly!
    If I’m a real Power User, then I can use PQ on my desktop to pull mashup data from the world, along with all my on-prem data through my exposed Cube presentation layer, and PowerPivot the
    heck out of that to produce all the reporting I’d ever want.  It'd be a zillion times faster reading the data directly from the Cube instead of via the DMG, as well (I think Power BI performance sucks, actually).
    Of course, your enterprise might not
    have a DW, just a heterogeneous mass of dirty unstructured data.  If that’s the case,
    choosing Power BI data structures is the least of your problems!  :-)
    Cheers, Donna
    Donna Kelly

  • Data element creation for custom 'data element orgchart'

    Hi all,
    I'd like to create my own Data element orgchart, using self-developed functional modules to achieve more flexibility in outputting data. Is any recommendations or examples for in-out interface of such modules?
    Regards,
    Sergey Aksenov

    Hi Sergey,
    What are you trying to achieve here? It sounds like you want to create new structures or use FMs to replace the data retrieval for the existing structures. This cannot be done in OrgChart, at least not through the AdminConsole.
    The structure is called in one call, as well as the data in the nodes. However, for each data source (e.g. NakisaRFC) used in a node there will be a call. For example, if you show position data from HRP1000 and employee data from PA0001 in a node then there will be 2 calls (which calls the data for all nodes at once). You can use an FM to do one call, but this would be in the view and not in the structure. The details panel makes multiple calls to retrieve data, so you can write an FM to call all data in one call rather than many.
    You should refer to page 58 of the OrgChart Admin Guide for more information on custom RFCs.
    Best regards,
    Luke

Maybe you are looking for