Manage data element UMBSZ in Material Record : Entry too long

Hello
I would like to manage alternatives units of measure with a Numerator defined in more than 5 digits, in the material master record (transactions MM01, MM02).
For example :
A material with a base unit of measure = ST (Items) : view Basic data 1 of the material master record
and the same material must be managed in Pallet : 1 Pallet = 150000 ST
So In additionnal data of the material master record we must assign 1 Pallet (fields UMREN + MEINH) for 150000 ST (fields UMREZ + MEINS)
but when i assign 150000 in the field UMREZ i have the error message
Entry too long (enter in the format __.___)
Message no. 00089
In fact The Field UMREZ is defined as DEC, Length = 5 and Decimal Places = 0
So what could be the Solution? Is it possible to managed this field with more than 5 digits? Is it possible to do something in the transaction CUNI?
Thank you for your answers
Best Regards
Manuel

Did you find a solution for this?

Similar Messages

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

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

Help regarding data element

I need some help regarding data element ZEXPDT. I used it in an infoquery that was transported to QAS and it does not exist in QAS. I thought it might be locked in a transport, but the below screen clip says it is not locked. It was created in 3/2014. Thanks.

Either trick the system, SE11, add a space at end of text desciption and save,
Or call transport workbench (SE01, SE10) create a transport request or use an existing one, then double-click on a task, switch to modify mode, add a line with R3TR DTEL name of the data element, save, then object list, lock in request/task menu.
Or SE80, contextual menu of data element. (other functions, write transport entry)
Regards,
Raymond

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

Geeting error when select UoM BOX- entry is too long

Hi ,
While creating SC , using F4 Unit of measurement , when selected BOX,
system gives entry too long error message.
Please suggest , how we can rectify this,
Thank you
Nilesh

Did you check the following OSS note...OSS Note 1474124?

Nawk message input record too long

I am running a shell script which uses nawk.
I am processing a huge input file.
I get a message that an input record is too long.
What am I supposed to do to indicate to nawk the max record line length ?
My e-mail is [email protected]
Any info will be appreciated

The 6144 limit can be verified with:
% perl -e 'print "A"x6145, "\n"' | nawk '{ print length($0); }'
nawk: input record `AAAAAAAAAAAAAAAAAAAA...' too long
source line number 1
(it works, when you change the perl print statment to
6144 x "A").
Quick solution could be to use gawk instead of nawk
(/opt/sfw/bin/gawk, if you have the Solaris 8 companion
CD installed).

Master data update bringing in multiple records for single entry

Hello,
I found that if I deleted and reloaded data in a master data object, it was showing me correct number of records. However, just a full update was not overwriting it with correct number of data records. there were always 1 or 2 extra blank records. I thought master data update should overwrite previous records and we need not delete and reload it.
Why would this happen?
Thanks!

Hi there,
Are you refering to time dependent master data? From to values are present?
If so, that's the correct situation, since BW (OLAP) instead of R/3 (OLTP) allows you to mantain historical data, i.e., a material can be valid from a specific time period with several attributes and other attributes can be valid for the same material in another time space.
Diogo.

Record entry date - using system date as default not working

Hi,
I have a form which allow users to enter the information... I want to have a field to save the date when they've updated the record...
in order to accomplish the above, here is what I did:
1) I created an item on the form (put the source as table_column that I am using to save the record entry date on the table)...
2) In the Default field I put "sysdate" to capture the current date...
3) I made the item "Display only" so that no one should be able to change it...
so far so good... when my users open the form they see current date populated in the form...
my challenge is that when user saves the form, everything that they enter saves except for the "record modification date"... Not sure if it's due to date format or something else causing it, the date format on my form is DD-MON-YY and seems like the format on my table is DD/MM/YYYY... if it's the date formatting issue then please advice how to fix it...
I've saved a sample on APEX.ORACLE.COM for your review and comments... Here are the log in details
Workspace: tparvaiz
Username: [email protected]
Password: tparvaiz
Application: 28899 Default Date and White Space
Appliaction Page No: 24
ID/PW: TEST/TEST
Thanks

Hi,
Default value only used when item value is null. So when you fetch the from it gets the value from database column and omit the default value. I use trigger to store audit information i.e. create date, username etc.
Here is an example if you want to use -
The following trigger will capture the date and username and store into the table.
CREATE OR REPLACE TRIGGER TRG_BI_TABLE_NAME
BEFORE INSERT
ON TABLE_NAME
REFERENCING OLD AS OLD NEW AS NEW
FOR EACH ROW
BEGIN
/* change the column name as of your table */
:new.create_date := SYSDATE;
:new.created_by := v('APP_USER');
END;This trigger will store user information and date when record been updated -
CREATE OR REPLACE TRIGGER TRG_BU_TABLE_NAME
BEFORE UPDATE
ON TABLE_NAME
REFERENCING OLD AS OLD NEW AS NEW
FOR EACH ROW
BEGIN
/* change the column name as of your table */
:new.update_date := SYSDATE;
:new.updated_by := v('APP_USER');
END;Hope this helps,
Regards,
Tajuddin
web: http://tajuddin.whitepagesbd.com

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

Multiple info records for the same material record in the catalog

Hi Guys,
I have got sort of a puzzle I can not solve at the moment, maybe some one can help me to solve it. The situation in our system landscape is as follows:
Systems:
SRM 5.0 (Classic implementation scenario)
ECC 6.0
SRM-MDM 2.0
PI 2005
Material master is maintained in R/3 and the materials are replicated to SRM. From SRM we replicate all materials to the catalog repository in SRM-MDM.
As the material master in R/3 is vendor independent, the materials replicated to SRM also have no vendor attached. For the first initial material replication from SRM to the catalog SRM-MDM this also means that the products in the main table of the repository, u2018catalog positionsu2019, will not have a vendor or vendor number attached (i.e. no reference to a source of supply).
To assign a source of supply in the repository to a product (record) we will use info records which are replicated from R/3 to SRM-MDM. The mapping for this in the Import Manager can only be based on the product number. As this is the only unique value available which can map a info record to a already existing (but vendor less) ptoduct item in the catalog.
As long as every item in the repository has only one unique info record, meaning one source of supply with a specific price, there is no issue in the above scenario. Based on the product-id, the info record data will be matched with the material item in the catalog.
The issue for me arises when multiple info records exists for the same material. The info records can heave different vendors and different prices. All possible vendors should be available in the catalog for the same material (at least this is the requirement ).
At this point the product-id will no longer be an unique value. Importing the info records will cause problems, as only one material record is available in the repository for the specific product-id (remember that when doing a initial replication of the material master to the catalog, no vendor data is replicated).
Does anyone had this issue before, and knows a solution? Is it for example possible during the import of the info records in the Import manager, to duplicate material records in the destination data, based on the number of info records available in the source data for the same product-id. Or is there an other solution that I am missing?
Your help would be appreciated!
Regards,
Skander

Dear Poster
Your thread has had no response since it's creation over
2 weeks ago, therefore, I recommend that you either:
- Rephrase the question.
- Provide additional Information to prompt a response.
- Close the thread if the answer is already known.
Thank you for your compliance in this regard.
Jason Boggans
SAP SRM SDN Moderator

What is conversion routine which is found in data element

Hi all,
I was just trying to creating a data element assigned to a particular domain in se11. While i am creating i can see a conversion routine
Can anyone tell me what is the use of that conversion routine with an example.
thanxs in advance
hari

Hi,
Depending on the data type of the field, there is a conversion when the contents of a screen field are converted from display format to SAP-internal format and vice versa. If this standard conversion is not suitable, it can be overridden by defining a conversion routine in the underlying domain.
Conversion routines are identified by a five-place name and are stored as a group of two function modules. The function modules have a fixed naming convention. The following function modules are assigned to conversion routine xxxxx:
CONVERSION_EXIT_xxxxx_INPUT
CONVERSION_EXIT_xxxxx_OUTPUT
The INPUT module converts from display format to internal format, and the OUTPUT module converts from internal format to display format.
When is a Conversion Routine Executed?
If a screen field refers to a domain with a conversion routine, this conversion routine is executed automatically when entries are saved in this screen field or when values are displayed in this screen field. The conversion routine of the domain is also triggered when the field contents are output with the WRITE statement.
Table SPFLI in the flight model contains information about the flights offered by the carriers. The time for each flight is recorded in field FLTIME. Enter and display the time of the flight in input templates in the form HHH:MM (hours:minutes). Store the flight time entered in the database as an integer number (number of minutes of the flight). An entry 3:27 is therefore stored in the database as 207 (3 hours, 27 minutes = 207 minutes).
Field FLTIME refers to domain S_DURA, to which conversion routine SDURA is assigned. The value is thus converted by the two function modules CONVERSION_EXIT_SDURA_INPUT and CONVERSION_EXIT_SDURA_OUTPUT.
A conversion routine can also be triggered by specifying its five-place name in the attributes of a field in the Screen Painter or with the addition USING EDIT MASK <Name of conversion routine> in the WRITE command in the program. With the USING NO EDIT MASK addition in the WRITE statement, you can skip a conversion routine defined for a domain when outputting.
Parameters
The two function modules of a conversion routine must have precisely two parameters with the names INPUT and OUTPUT for the value to be converted and the converted value.
The INPUT parameter in the INPUT conversion and the OUTPUT parameter in the OUTPUT conversion should not have any reference fields because the value passed in the call could have a different length than that expected.
Programming Conversion Routines
ABAP statements that result in an interruption of processing (such as CALL SCREEN, CALL DIALOG, CALL TRANSACTION, SUBMIT, COMMIT WORK, ROLLBACK WORK, MESSAGE I, MESSAGE W) are not allowed in conversion routines.
Only A messages are meaningful in output conversion, but A, E and S messages can be triggered in input conversion (although S messages are not very meaningful here). E messages result in an error dialog. Exceptions are not intercepted in the call.
The output conversion is also triggered with WRITE and WRITE TO. The conversion routine may therefore occur very frequently with lists. The output conversion should therefore be programmed as efficiently as possible.
No external performs should be used in conversion routines. Programs that are called externally use the table work areas of the first calling main program. In conversion routines this can result in errors that cannot be easily analyzed since they are sometimes called at unpredictable times in the program flow.
Pls refer link which contains code as an example to conversion routine used in abap.
<a href="http://www.bwexpertonline.com/downloads/source_code.doc">http://www.bwexpertonline.com/downloads/source_code.doc</a>
Pls reward points.
Regards,
Ameet

Extraction and loading of Training and Event Management data (0HR_PE_1)

hello,
I've got the following doubt:
before BI 7.0 release, extractor 0HR_PE_1 extracts event data (eventid, attendee id, calday,...) but if you load straight to cube 0PE_C01, as Calendar year/month needs a reference date (for example, event start date), you'll get total duration of event in hours or days refered to event star date.
So in a query filtered by month, you get total duration of an event that starts in the filtered month but it couldn`t end until few months later o year later, so you don´t get appropiate information.
Example:
Event calday Hours
10004377 20081120 500 but from event_attr event end date is 20090410.
In a query filtered by 200811 you get total duration time (500 hours when in 200811 event hours have been 20) or if you filter by any month of 2009 you don´t get information of duration of that event.
I had to create a copy of standar cube (without calday, only Calendar year/month, Calendar year in time dimension) and disaggrate data creating as many entries for an event as months lasts and adjust calculation of ratios duration of event (duration of event in each month/ total duration of event).
The question is: Is there any improvement or change on business content in BI 7.0 to treat Training and Event Management data? Has anybody had to deal with that?
Thank you very much.
IRB

Hi,
TEM data is stored in HRP tables.
You can load the catalog by creating LSMWs for objects Business event group (L), Business event types (D), Locations (F), Organizers (U) as per requirement.
LSMW for tcode PP01 can be used to create these objects.
To create Business Events (E) you can create LSMW for PV10/PV11.
To book attendee create LSMW for tcode PV08 as here you can specify the actual business event ID which reduces ambiguity.
tcode PV12 to firmly book events
tcode PV15 to follow up
Hope this helps.
Regards,
Shreyasi.

Getting Training and Event Management Data using IT0031

Scenerio:
One of the Employee Is Retired. Now we hire it again for the same role ( extending its period after posting it as retired).
So the good thing that we can use the IT0031 "Reference Personnel Numbers" to get the desired ITs and found that can get other cutomized ITs by checking in the "Copy Infotype" attribute of IT records.
Now this seems to be valid if we are in the same module
but waht if i want to get this magic "Referencing of ITs" done for the "Training and Event Managment" Data of the employee.
Is it Possible Automatically ... or have to go fro ABAP... (I will not prefer ABAP)...
I hope i have stated the problem clearly ...
Feedback ... need it ASAP ...

Hi,
TEM data is stored in HRP tables.
You can load the catalog by creating LSMWs for objects Business event group (L), Business event types (D), Locations (F), Organizers (U) as per requirement.
LSMW for tcode PP01 can be used to create these objects.
To create Business Events (E) you can create LSMW for PV10/PV11.
To book attendee create LSMW for tcode PV08 as here you can specify the actual business event ID which reduces ambiguity.
tcode PV12 to firmly book events
tcode PV15 to follow up
Hope this helps.
Regards,
Shreyasi.

How to add a new data element?

friends,
the data elements for the fields ECSRATE and orig_ecsrate in the structure j_1iexitem is different in our development and production systems...the correct one is j_1iexecsrat, which is in development...how to change the data element of this field in the production system..thanks all.

Hi,
Kindly check the transport requests for the structure in both DEV & PRD.
Utilities -> Versions -> Version Management.
Kindly check the transport request in the DEV against the "activ" checked.
Look for the same request number in the PRD for the structure.
If there is a mismatch, kindly transport the request in DEV to PRD.
You cannot directly change the data elements in PRD system.
It should be done through the transport requests from DEV to PRD.
Hope this helps!
best regards,
Thangesh

Manage data element UMBSZ in Material Record : Entry too long

Similar Messages

Maybe you are looking for