SAPScript: includung a domain documentation in a data element documentation

Dear ABAPers,
I have a couple of (self-defined) DDIC data elements referring all to the same domain. How does the SAPScript INCLUDE-command need to look like in order to include the domains text in the data element text? (which object and which ID needs to be provided for domain documentation?).
Thanks in advance
Andreas

Hi Pushpraj,
for any kind of DDIC-object (table, structure, data element, domain...) you can maintain documentation, which is saved as SAPScript (there is a button "Documentation" or in the case of the domains you have to go via the menu "Goto -> documentation"). In that sort of SAPScript-based texts you can basiscally include any other SAPScript-Text with the INCLUDE-Command.
Example: with SAPScript Command "INCLUDE BELEGART" you can reuse SAPs standard help-text for field BKPF-BLART. But usually the SAPScript INCLUDE command looks like this:
INCLUDE <name_of_text> OBJECT <object> ID <ID>.
Thanks
Andreas
Edited by: Andreas Fluegel on Mar 9, 2009 3:11 PM

Similar Messages

URL link in data element documentation

Is it possible to create a url link within the documentation of a data element to allow the user to launch the web browser and navigate directly to a specified webpage?
Regards
Mark Briggs

Hello,
I am not sure but you can try this out. Go to se38 and documentation for a test program. Click on Goto and then Change editor. write a text that you want to give a link to. Make its paragraph format as SAPfind Reference. Select the text goto insert link. It will pop you up with a box. give the name of your program but how to link it is another mystery.
Try these function modules.
IWB_HTML_HELP_OBJECT_SHOW
IWB_HTML_HELP_EXTENDED_HELP
and see this program BCALV_GRID_F4_HELP may be of some help.
REgards,
SHekhar Kulkarni

Use of documentation flow in data element!!!!

hi experts,
what is the use of documentation flow in data element.
if that field is selected then where will be changes reflected ?
thanks in advance,

Hi,
Changing Data Element documentation (F1 help text)
SAP allows you to modify data element documentation (F1 help text), this could be useful if you want to add/remove information from the F1 help text. E.g. If you are using the field to store info it was not intended for.
Step 1
Using transaction CMOD chose the following menu option
Menu Goto->TExt Enhancements_>data elements->list cust docu.
Enter the data element that you wish to change the documentation text for, then click the change icon(Pencil in 4.6c and tick in 4.6b). You will then be presented with the following screen, which allows you to create new versions of the data element documentation. Simply click on the Change button and enter a name within the customer name range.
Regards

URL in data element documentation (F1 help)

Hi, is it possible to insert a URL within a data element documentation ? I know it is possible to link the F1 help functionality to go to a URL instead of the data element documentation, but what was asked is to display the regular documentation for the data element, but include a URL to a web site for further information. Any idea how to do this ?

Hi,
Check This Link
http://help.sap.com/saphelp_erp2005/helpdata/en/49/e8884118aa1709e10000000a155106/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/b6/ab3a9003ac11d4a73f0000e83dd863/frameset.htm
Also to add link in Documentation
Do this
1) Open Program
2) Click on documention ( open documentation Window for any program )
3) Follow this Menu Option.
Insert--->Link
A dialog Box will Be opened
In Documentation Class
Select WeB Application From F4 Help Option
Save and activate.
Rewards Points & Mark Helpful Answers if it helps.
Message was edited by: Manoj Gupta

How to translate data element documentation

Hi,
Please help me finding the solution to the above issue.
Here i am trying to translate Documentation for custom Data Element.
Thanks

Call transaction SE63: menu Translation, Long texts, ABAP dictionary, Data Element Documentation.
Regards

What is domain and dataelement.....diff b/w domain and data element

dear all
what is domain?
what is data element?
In one domain how many data elements are possible to used?
with out data element how can u create a table? explain briefly.

To clarify it little further the Data element and Domains are used in combination where similiar type of data fields are to be used with some more additional characteristics to each Data element.
For example consider creating a table which contains Employee details. The Columns Name1 and Name2 are to be of type char and length 40. There are 2 ways to do this,
1. You can assign the fields Name1 and Name2 directly to CHAR40(as the data element) in SE11. But this will make both the fields to have same characteristics with no difference among them.
2. The other way is to assign the columns Name1 and Name2 to seperate Data elements say DE_NAME1 and DE_NAME2. This method has tha advantage of adding further charectristics and labels to the data element. Hence in this case you can add a label "Name1" for the data element DE_NAME1 and "Name2" for data element DE_NAME2. And both these data element will point to the same domain CHAR40, hence length and type is same.
Hope this helps.
Thanks,
Prasath N

Mechanism for Info Object Data elements inherit source documentation?

Say I am in ECC. I go to SE11, give table name MARA and then doubleclick on the dataelement 'MATNR'. Then I click on documentation. I get a popup with Short text " Material Number" and Definition "Alphanumeric key uniquely identifying the material'.
I am interested in the latter information that is 'Definition' - & in general whatever documentation comes up for data element in ECC/CRM/SCM/SRM.
Now I log into SAP BI. I find that under characteristic 0Material, the data element is /BI0/oimaterial. When I double-click this datamaterial and press the documentation button, the system says 'No documentation'.
My Questions:
1. IS there a switch we could turn on in source [ECC/SRM/CRm/SRM] so that the data element in SAP BI inherits the original source field data element documentation.
{ I am not too convinced of the argument- that in BI we have info objects in ECC we have fields - since I am talking of data element level information- I would tend to think of this as an oversight of the designers [or de-prioritization] !!}.
2. Could we have an ABAP workaround? That is, in BI we identify the tables that house the mapping between the source and destination data elementsa and take out this information. Then we extract the dataelement documentation [by function DOCU_GET] and use the mapping info above to link SAP BI data element with source data element documentation.
WHY do I want to punish myself as above? My use case is, we take out SAP BI Table, field, metadata etc and create a model in a modeling tool and physical implementation in a 3rd party DW database as our own canonical, application-agnostic corporate datawarehouse. I would want the source data element documentation to flow to this last system as well as the modeling tool.
Regards
Sasanka

go through this links:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9214b1e5-0601-0010-fdb0-ec32d43b06e0
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/8d7cc990-0201-0010-27a3-d0f74b75a1ee

Doubt in data element creation

Hi,
I have doubt in data element creation ie, there is 2 options elementary type
(domain and built-in-type) and reference type (name of the reference type &
ref to predefined type). if there is built in type here then what is the use of
built-in-type in initial screen of the table and also explain me about the use of
reference type.
with regards,
nanjunda sharma

Hi!
With the use of the built-in type, you have to set always in every different data element the exact type.
With the use of the domains (pre-defined types) you just have to enter the domain name into the data element. If you have to modify the type, you can maintain it in the domain (only once) but the built in types have to modifyed in every data element (which means more work).
Domains have a little more options also, than the built in types.
Regards
Tamá

How to make BI Info obj Data element in-herit source DE documntn?

Say I am in ECC. I go to SE11, give table name MARA and then doubleclick on the dataelement 'MATNR'. Then I click on documentation. I get a popup with Short text " Material Number" and Definition "Alphanumeric key uniquely identifying the material'.
I am interested in the latter information that is 'Definition' - & in general whatever documentation comes up for data element in ECC.CRM.SCM,SRM.
Now I log into SAP BI. I find that under characteristic 0Material, the data element is /BI0/oimaterial. When I double-click this datamaterial and press the documentation button, the system says 'No documentation'.
My Questions:
1. IS there a switch we could turn on in source ECC/SRM/CRM/SRM so that the data element in SAP BI inherits the original source field data element documentation.
{ I am not too convinced of the argument- that in BI we have info objects in ECC we have fields - since I am talking of data element level information- I would tend to think of this as an oversight of the designers or de-prioritization !!}.
2. Could we have an ABAP workaround? That is, in BI we identify the tables that house the mapping between the source and destination data elementsa and take out this information. Then we extract the dataelement documentation by function DOCU_GET (from eCC) and use the mapping info above to link SAP BI data element with source data element documentation.
WHY do I want to punish myself as above? My use case is, we take out SAP BI Table, field, metadata etc and create a model in a modeling tool and physical implementation in a 3rd party DW database as our own canonical, application-agnostic corporate datawarehouse. I would want the source data element documentation to flow to this last system as well as the modeling tool.
Regards
Sasanka

That is, in BI we identify the tables that house the mapping between the source and destination data elementsa and take out this information. Then we extract the dataelement documentation by function DOCU_GET (from eCC) and use the mapping info above to link SAP BI data element with source data element documentation.
1) SAP don't supply this, I would imagine, because R/3 isn't the only possible source of data. I'm currently working on an app that extracts from R/3, an Oracle database and APO. From whence should I take the documentation for my MATERIAL info object? While being able to transfer the documentation of data elements might be very useful for your app, I can't see that generally it would be of interest to clients - I've certainly never heard of such a requirement. So, my opinion at least, it isn't a design flaw.
2) As you've pointed out, you can get the tables that do the mapping, so you know the source data elements, so you can get the documentation. I'm not sure of how to store the documentation, but the obvious candidate for a link between infoobject and dataelement would be master data of an own infoobject. You could wrap DOCU_GET in an RFC (if it isn't RFC enabled), and do a direct call between your 3rd party app and r/3 to get the documentation. For information about the mapping tables, I'd suggest asking that question specifically in one of the BI forums.
matt

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.
Two Level Domain Example
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.
Definitions of Table in Database
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.
Elaboration on each of the definitions
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.
Technical Settings in Dictionary
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!
Create transparent table
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.
Create data element
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).
Create domain
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.
Currency/Quantity fields in a table
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).
Create transparent table continue
Maintain the technical settings of the table by clicking on the tab

Is an assigned value to an variable in the domain of the data element

Hi
how can I check if the value, which I want to assign to an variable is in the domain of the data element of that variable.
Example:
I defined a data element myDataElement. The Elementary Type of myDataElement is the Domain myDomain.
myDomain has the Format: Char with Length 1 and the fixed values 'A' and 'B'.
The following code works, but IMHO should not:
DATA testVar TYPE myDomain.
testVar = 'Foo'.
The value of testVar is now: 'F' .
As 'F' is not in the fixed values, this is a behaviour which I don't want. How can I prevent this from not happening (without using a bunch of IFs)?
In such a case, it were nice if an exception were raised.
Regards
Gilles

Thanks Gungor.
I tried it with DDUT_DOMVALUES_GET. Works so far. I think I will write some FMs on my own, like this one:
FUNCTION z_valueisindomain.
*"*"Local Interface:
*" IMPORTING
*" REFERENCE(IV_DOMAINNAME) TYPE DDOBJNAME
*" REFERENCE(IV_EVALUATING_VALUE) TYPE ANY
*" EXPORTING
*" REFERENCE(EV_DESTINATION) TYPE ANY
*" EXCEPTIONS
*" ILLEGAL_INPUT
*" NOT_IN_DOMAIN
DATA domainvalues TYPE TABLE OF dd07v.
CALL FUNCTION 'DDUT_DOMVALUES_GET'
 EXPORTING
 name = iv_domainname
 TABLES
 dd07v_tab = domainvalues
 EXCEPTIONS
 illegal_input = 1
 OTHERS = 2.
IF sy-subrc <> 0.
 RAISE illegal_input.
ENDIF.
DATA oneline TYPE dd07v.
LOOP AT domainvalues INTO oneline.
 IF oneline-domvalue_l EQ iv_evaluating_value.
 ev_destination = iv_evaluating_value.
 EXIT.
 ENDIF.
ENDLOOP.
IF ev_destination IS INITIAL.
 RAISE not_in_domain.
ENDIF.
ENDFUNCTION.
I'm pretty new to ABAP, so this FM might not be very elegant.
Regards
Gilles

Automatic creation of BW data flow documentation

Dear Gurus,
I need to write documentation of the data flow of a huge project which I haven't implemented by myself.
The documentation should contain a mapping of the objects in the dataprovider, towards objects in the source system(s).
Eventually with the info in which dataproviders the objects are included, e.g. between the multiprovider and the source system.
Details of transformations can be ignored; eventually mentioning there's a routine involved, but that's the maximum.
With the data repository, I can have the content of cubes in a graphical overview, but it doesn't really provide me useful information.
You can imagine I prefer an automatic way to create this documentation.
Anybody who knows a solution, even if it only provides part of the purpose?
Any solution via query, standard SAP or customized program, ...
Recommendations would be very highly appreciated!
Thx & Rgds, sam

Worldwide documentation is made on SAP BW projects, but no reply on automatic documentation.
A lot of time must be lost by manually creating documentation on mapping objects to source system fields.
==> SAP, please, work out a solution.
I didn't find a satisfying solution, but I've done it the following way:
List all objects for a multiprovider via the meta data repository, and paste in excel document.
Then listing all objects for the underlying dataproviders, and paste in separate sheets of this excel.
Compare the objects of the MP with the objects on the other sheets using excel functions, and sign when a dataprovider contains a certain object.
For the datasources, I checked if an object is present, and if yes, give the original source field.
This in summary as a not optimal and not complete solution, but it prevents making mistakes.
Rgds. sam

Data Socket Documentation

Could someone please help me find detail Data Socket documentation regarding allowed urls and Timouts.. For example what expressions are not allowed for making connections(.html)? And what is the maximum Timeout (seems to be limited to ~20secs)? -SS

Unfortunately, there isn't a single source that I would call the "definitive" data connection resource for LC Designer. I would suggest using information from the following resources at your disposal:
These forums. There are lots of examples here on data connections and some Adobe personnel along with many other very knowledgeable customers providing answers.
The
Working with Data Sources help topic in LC Designer Help.
Data Connection samples found on the
Adobe LiveCycle Designer Samples page.
My personal favorite: Looking at the JavaScript code in the Initialize event of the Data List Box object found in the Library palette's Custom tab (drag one on to a form and look through it's Initialize event code using the Script Editor).
If you have a specific question about a problem you're trying to solve using Data Connections in LC Designer, please post to a thread in this forum. We'll be happy to help you solve it.
Stefan
Adobe Systems

COPA unable to create as charac data element with LIFNR as domain HELP ASAP

Hi
We had a data element created with KUNNR as domain.
We added to PAPARTNER STRUCUTRE and created as characteristics in our operating concern.
Now there is a need to change to LIFNR as domain instead of KUNNR.
There we created a new dala element with LIFNR as domain and added to PAPARTNER
structure and when we tried to create them as characterisc system did not let us transfer to
our operating concern.
We do not know why we are unable to create this characterisic.
When we tried to create the characteristic it was shown under 'Transfer from'
But when we wanted to move right to left it was shown under 'grey' status and not ready for transfer.
We need a solution very urgent and any help is greatly appreciated.
Thanks
Raj

Hi
KEA0 - Display Data Structure
Now, Extras > Chars > Unlock
after this try to push from right to left
br, Ajay M

Oracle 9i Data Guard Documentation

Hi,
I am trying to get documentation on Oracle 9i Data Guard.
When I am at this url: http://www.oracle.com/technology/deploy/availability/htdocs/DataGuardOverview.html
I then activate the link on the right for "Oracle 9i Data Guard Documentation".
However, the link moves me to "Oracle 9i list of books", instead of where I want to be.
Can you please rectify this or send me the link to get this documentation.
Thanks,
Jason Metzker

Hi
The response I received in regards to the links to the Oracle 9i Data Guard Documentation page is that the link is correct.
The Data Guard doc is part of the database documentation set which is why the Oracle 9i Data Guard Documentation links takes you to the list of books. The Data Guard Documentation is also listed in the list of books.
Thanks & Regards,
Chao

SAPScript: includung a domain documentation in a data element documentation

Similar Messages

Maybe you are looking for