Maintenance view- package in another system

Hello all!
I'm trying to create a maintenance view for a Z table, but i can not do it because i get an error message that says: "The original of the table development class YMMI is in DEV". YMMI is the package, but DEV is not the development system of this client, but the one of another client, where data comes from (i think there was a kind of transport). In table attributes, it says: Package: YMMI, but i am not allowed to change this. SAP version is 4.6 C.
To do this, i go to se11, enter table name, then modify, and then utilities--> table maintenance genarator.
(This version doesn't have the part Delivery and maintenance). The same occurs when entering from SE54.
Please give me an idea!!
Thank you!

Hey maitas,
You check the Display and Maintenance table whethere is the is maintainable or Maintenace Not allowed. If the option is Display/Maintenance Display/Maintenance Allowed with Restrictions or you can create the maintenance view otherwise you cannot create.
Regards,
Saravanan M

Similar Messages

Copying Z developed packages to another system

I want to copy the Z developed packages from the system (i-Series) to one of my SAP SQL 2005 system. Is it possible and let me know the procedure with stpes to do it.
I would apprciate your help.

Hi,
Do following
launch SE10 -> create -> transport of copies -> give short description
and target system within your TMS landscape -> this will create a request -> double click on request -> click on change
now enter following value
Program ID -> R3TR
Object Type -> DEVC
Object name -> name of your Z package
press enter
click Release
import this request in target system.
regards,
kaushal

How do I view package bodies in another schema ?

For purposes of SOX and security/audit control, we log in under our network id's in our production environment. We have sourcecode compiled into Oracle seeded schemas ( APPS ) so that scheduled jobs are able to run with submitted from the Oracle Applications environment. We don't compile code into our personal network account areas.
I know how to GRANT EXECUTE privs so that we can execute a package in another schema, but what I want to do is to be able to view the sourcecode in another schema. Compile into APPS but be able to see the package body from my network id schema account.
I can't seem to find what the correct permission is anywhere. Granted I can look at DBA_SOURCE to get to it, but I want to use a tool like SQL Developer or TOAD to look at the code in a more presentable and easier to debug manner.
Any help ?

I did some more searching on the forum... seems its already a request... TOAD gives access to DBA_Views to resolve the issue... SQL Developer has not integrated that functionality yet, but forum entries seem to indicate that it is on the horizon.
Thanks for responding though.
~Barry

Transfer package to another control system

We have an independent control /central system which is busy with a big time reduction TDMS project, now it's at the beginning of the data transfer.
However its CPU has crashed 2 times this week.
Can we transfer this package to another TDMS control/central system, then continue the data transfer?
We have to think about this is because the data-selection cost a lot of time already, no time to start over.
Thanks!

As stated by Marcus if you really want to move your TDMS system to a different hardware the only possibility is to do a system copy. Now there are various ways to do a system copy depending on the Database (backup-restore, detach-attach e.t.c) and may be one of the method can suit your time frame. Your basis team should be in a position to help you plan the same.

How to transport a package(dev class) to another system?

dear gurus,
is it possible to transport a package (development class) from one system to anther system mannully? there is no transport path between the two systems.
best regards.
Jun

Hello Jun
The "correct" way would be to create a transport request of type Relocation of Complete Package (SE10):
DE ORDER_MVE
Short Text
 Select relocation of a complete package
Definition
 Relocations of complete packages are transports with which you
 simultaneously
 o move the original location of all objects in a package to the target
 system and
 o simultaneously assign the package to another transport layer.
Use
 Changing the transport layer means that you can edit and transport the
 objects consistently in their new original location without delay.
However, I assume that this is not possible in your system landscape. In this case you can download the transport files using transaction CG3Y (if available => download as BIN not ASC) yourself. A transport request E01K900100 consists of two files (data and log file), e.g.:
/usr/sap/trans/data/R900100.E01
/usr/sap/trans/cofiles/K900100.E01
Please note that the transport directory is likely to be different on your SAP system (check for directory DIR_TRANS in AL11 or ask your basis colleagues).
Now on your target system you either upload the files into the corresponding transport directories using CG3Z (if available) or ask your basis people to put the files into the directories. Either your basis is importing the request or you can use transaction STMS (Import queue <target system>, menu Extras -> Other Requests -> Add).
Add the request to the import queue and import it.
Finally you need to change the original system of the transported object and the transport layer of the package:
1) SE03 -> Change Object Directory Entries of Objects in Request
2) SE80 -> Package in Change Modus: maintain transport layer
Regards
Uwe

How to view list of all system exceptions from standard package?

Hello,
How to view list of all system exceptions from standard package?
Regards
Krishna

Just for fun:
SQL> conn sys/****** as sysdba
Verbonden.
SQL> select cast(trim(substr(text,instr(text,'(')+1,instr(text,',')-instr(text,'(')-1)) as varchar2(30)) exception_name
2       , to_number(replace(substr(text,instr(text,',')+1,instr(text,')')-instr(text,',')-1),'''')) error_number
3    from user_source
4   where text like '%pragma EXCEPTION_INIT%'
5     and type = 'PACKAGE'
6     and name = 'STANDARD'
7   order by exception_name
8 /
EXCEPTION_NAME                 ERROR_NUMBER
ACCESS_INTO_NULL                      -6530
CASE_NOT_FOUND                        -6592
COLLECTION_IS_NULL                    -6531
CURSOR_ALREADY_OPEN                   -6511
DUP_VAL_ON_INDEX                         -1
INVALID_CURSOR                        -1001
INVALID_NUMBER                        -1722
INVALID_OBJECT_NAME                  -44002
INVALID_QUALIFIED_SQL_NAME           -44004
INVALID_SCHEMA_NAME                  -44001
INVALID_SQL_NAME                     -44003
LOGIN_DENIED                          -1017
NO_DATA_FOUND                           100
NO_DATA_NEEDED                        -6548
NOT_LOGGED_ON                         -1012
PROGRAM_ERROR                         -6501
ROWTYPE_MISMATCH                      -6504
SELF_IS_NULL                         -30625
STORAGE_ERROR                         -6500
SUBSCRIPT_BEYOND_COUNT                -6533
SUBSCRIPT_OUTSIDE_LIMIT               -6532
TIMEOUT_ON_RESOURCE                     -51
TOO_MANY_ROWS                         -1422
USERENV_COMMITSCN_ERROR               -1725
VALUE_ERROR                           -6502
ZERO_DIVIDE                           -1476
26 rijen zijn geselecteerd.Regards,
Rob.

Is there any Program available to Copy a package from one System to Another

Hi all,
Is there any Program available to Copy a package from one System to Another ?
Thanks in advance
Raghu ram

Hi,
Put the Package into a TR using transaction SE80.
Provide the TR no. to BASIS consultant & ask him to provide the file of that TR.
Import the TR file in another system.
Thats it.
Best regards,
Prashant

Unable to edit maintenance view in SM30

hi everyone.
need your help, I have one custom table, let's call it YTAB. This table has several maintenance views created for it, depending on company code. For YTAB, i have created a maintenance view YTABX.
When we moved YTABX to PRD, we cannot edit it in SM30. The user ID has the right authorization. The error message is "client 100 not modifiable". When I try to edit the mother table YTAB in PRD, I am able to go in and do the changes.
I have already compared the settings for YTABX with the other existing views, they are the same. My settings for the view are:
Access: Read, change, delete & insert
Delivery Class: C
In the table maintenance generator, i have a 2-step maintenance type, recording routine is Standard recording routine and compare flag is automatically adjustable.
Attributes for table YTAB also has delivery class C, table category is transparent table, table maintenance is allowed.
Thank you in advance.

Hello roch,
the direction in which mark points is right but i think you should get some more information on the principles of table types and sap system landscape.
Usually you should not be able to directly maintain any table. This is not only bad style but also a huge risk for the system consistency. That's why application data is always maintained via some kind of application which ensures that the data is vilidated before it is stored.
Customizing data should only be maintained within a development system and then transported through the landscape. To maintain these table you can use generated views, customer developed maintenance views, view clusters which all include automatical link to the transport system. If you would maintain these tables directly in the productiion system it would have another configuration than the development and the quality/test system which makes them more or less useless as you can no longer make any serious test if the server configurations differ.
To prohibit changes of customizing tables on production and test servers the admins lock the systems which results in the message you got. This setting is made in TCODE SCC4. Even if you have for any reason the authorization to use this transaction you should in no case change these settings without approval of basis / system owner.
Kind Regards
Roman

Table Maintenance View Generator - 46C to 60 compatibility

Table Maintenance View Generator - 46C to 60 compatibility
I think SAP changed the way it generated its View Maintenance Screens some time after release 46C such that view maintenance dialogs in 46C are maintainable in subsequent releases but that view dialogs created in subsequent releases are not compatible in 46C. This is my hypothesis.
Can someone confirm? Is there a way to revert 60 code to the way the dialog was generated in 46C?
The error in the transport log from a 60 system to a 46C system is:
"Field '<VIM_TOTAL_STRUC>' is unknown. It is neither in one of the specified"

Hi April,
You can use standard program RSWBO052 to change the package. Enter the object and mark the checkbox -> Execute -> Place the cursor in the object -> Right click mouse -> Reassign -> Enter new package -> Save.
or you can go to transaction SE80 -> Select Package -> Enter &TMP -> Hit Enter -> Find your object -> put the cursor and right click -> Other functions -> Object Directory Entry -> Change -> Change the package -> Save.
Hope this will help.
Regards,
Ferry Lianto
Please reward point if helpful.

Hi experts, how to use open sql to read data from one " maintenance view"?

i want to use this part of data within report ,so how to use open sql statement to read data from one " maintenance view"?

Hi
You can't use OPEN SQl statements to fetch data from maintenance view
You have to use only Database views
see the different types of views and the difference
The followings are different types of views:
- Database View (SE11)
Database views are implement an inner join, that is, only records of the primary table (selected via the join operation) for which the corresponding records of the secondary tables also exist are fetched. Inconsistencies between primary and secondary table could, therefore, lead to a reduced selection set.
In database views, the join conditions can be formulated using equality relationships between any base fields. In the other types of view, they must be taken from existing foreign keys. That is, tables can only be collected in a maintenance or help view if they are linked to one another via foreign keys.
- Help View ( SE54)
Help views are used to output additional information when the online help system is called.
When the F4 button is pressed for a screen field, a check is first made on whether a matchcode is defined for this field. If this is not the case, the help view is displayed in which the check table of the field is the primary table. Thus, for each table no more than one help view can be created, that is, a table can only be primary table in at most one help view.
- Projection View
Projection views are used to suppress or mask certain fields in a table (projection), thus minimizing the number of interfaces. This means that only the data that is actually required is exchanged when the database is accessed.
A projection view can draw upon only one table. Selection conditions cannot be specified for projection views.
- Maintenance View ( SE54 )
Maintenance views enable a business-oriented approach to looking at data, while at the same time, making it possible to maintain the data involved. Data from several tables can be summarized in a maintenance view and maintained collectively via this view. That is, the data is entered via the view and then distributed to the underlying tables by the system.
Please have a look at below link. It will help you.
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ed06446011d189700000e8322d00/frameset.htm
for more detailed info look on:
http://www.sap-img.com/abap/what-is-the-different-types-and-usage-of-views.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/abap+dictionary&
Reward points for useful Answers
Regards
Anji

Lis--Updating cannot be tramnsported to another system

Hi All,
am very new to BW. I am having problems to extract LIS info to BW.
read all the mails in SDN on LIS extraction.
IN txn MC24 when i am trying to update my info structure i am getting the message
"Updating cannot be transported to another system"
in log i saw it asks me
"The info structure S998 has the development class $TMP and therefore cannot be transported. For this reason updating definitions for info structure S998 cannot be transported to another systems.
Procedure
It is possible to transport the update rules to another client in the same system.
If you still want to transfer the info structure, call up the function transport features in the info structure maintenance (transaction MC22) and change the development class.
when i went to MC22 and went to "Create object directory entry"...
i see package as $tmp so had selected local object...was the above problem due to it...
If i have to create another package then what do i have to do and what transport layer should i put"
hoping to get some reply. Am very confused with this LIS and LO extractions . Spend a lot of time in tryong to understand it.
Thanks
Mansi

In the past two weeks I did a bit of research but not to much avail. I noticed I had the "Locale Switcher" add on installed, and deactivated it. Switching languages in the "Languages" tab of "Add-ons" still did not work (yes, I restarted every time). I installed the "'''Quick Locale Switcher''' 1.7.4" extension (yes, I restarted), and it displays a number of locales in the "Tools" menu; still choosing one has no effect (yes, I restarted).
Then I juggled with Quick Locale Switchers "options", which actually displayed in Esperanto (so I cannot tell you what they say in English). I check the first one (saying more or less that locale switching should affect the user interface) and switched to German (yes, I restarted) -- and '''it worked'''! I switched to Esperanto -- and Firefox went to ... English!
After a lot of searching in the Web I found on "[https://addons.mozilla.org/en-US/firefox/addon/esperanto-language-pack/ https://addons.mozilla.org/en-US/firefox/addon/esperanto-language-pack/]" that this pack is "'''Not available for Firefox 3.6.16'''". That might explain something (not everything); probably I lost my language when I upgraded from 3.5 to 3.6.
Here a little error message could save people hours of their lives...

HIde table field in maintenance view

HI ,
i have table with 5 column and i want to create new maintenance view but hide one of the field for maintenance ,
i need to deliver this table to prod so i need to keep the changes on transport .
i don't want to do it via code since when i regenerate the maintenance view again it will deleted .
there is another option ?
Regards
Nina
Moderator message - moved to the correct forum.
Edited by: Rob Burbank on Oct 1, 2009 4:26 PM

Hi
1 ) I need to delete the maintenance that i do to the table like i mention in previous post ?
Yes u can delete the maintenance program created for your Z (transparent table): it'll be useless, anyway it's not necessary to delete it, but if you think it won't be used, it's better to delete it.
2 ) create to the table maintenance view and i hide the field
Yes, u need to create a maintenance view based on your Z (transparent) table and set the flag for the fields to be hidden.
when i create it in the tab view fields i see just the key fields of the table why ?
Because the system inserts the key fields by default, the other fields has to be placed manually, u can also decide to insert only the fields u need to show and manage in maintenace program, i.e. the maintenance view (but in generally a table view) can have only certain fields of a transparent table, it's not necessary it has all fields.
in the table join condition i just put the table name do i need to do something else ?
No u don't need to do anythingelse
Max

Maintenance View Validations

I have a custom table for which I am maintaining a Maintenance View.
I want to provide some validations and checks on the fields entered by the user in that maintenance view.
For example, if the user enters a value greater than 1000 in quantity field, I want to display a message saying that " enter only values below 1000". This is part of customer requirement.
Can I provide validations on fields in Maintenance view and if yes, then how ?
Thanks,
Urmila

Hi this may help u.
Maintenance views offer easy ways to maintain complex application objects.
Data distributed on several tables often forms a logical unit, for example an application object, for the user. You want to be able to display, modify and create the data of such an application object together. Normally the user is not interested in the technical implementation of the application object, that is in the distribution of the data on several tables.
A maintenance view permits you to maintain the data of an application object together. The data is automatically distributed in the underlying database tables. The maintenance status determines which accesses to the data of the underlying tables are possible with the maintenance view.
All the tables in a maintenance view must be linked with foreign keys, that is the join conditions for maintenance views are always derived from the foreign key (see Foreign Key Relationship and Join Condition). You cannot directly enter the join conditions as for database views.
There are some restrictions for the attributes of the foreign keys with which the tables in a maintenance view can be linked (see Restrictions for Maintenance and Help Views).
A standardized table maintenance transaction is provided (SM30), permitting you to maintain the data from the base tables of a maintenance view together.
Maintenance mechanisms, like screens and processing programs, must be created from the view definition with the transaction Generate Table View (SE54). This makes it possible to create easy-to-use maintenance interfaces in a simple manner.
You can find out how to create such maintenance mechanisms in the documentation BC - Generate Table Maintenance Dialog.
Creating Maintenance Views
Procedure
Enter an explanatory short text in the field Short text.
You can for example find the view at a later time using this short text.
Enter the primary table of the view under Tables in the Tables/Join conditions tab page.
Only those tables that are linked with the primary table (indirectly) with a foreign key can be included in the maintenance view.
If required, include more tables in the view. In a maintenance view you can only insert tables that are linked to one another with foreign keys.
Place the cursor on the primary table and choose Relationships. All existing foreign key relationships of the primary table are displayed. Select the required foreign key and choose Copy. The secondary table used in such a foreign key is included in the view. The join conditions derived from the foreign keys (see Foreign Key Relationship and Join Condition) are displayed.
You can also insert tables that are linked by foreign key with one of the secondary tables that was already inserted. To do this, place the cursor on the secondary table and choose Relationships. Then proceed as described above.
For maintenance and help views, there are certain restrictions on the foreign keys with which the tables can be included in the view (see Restrictions for Maintenance and Help Views). The foreign keys violating these conditions are displayed at the end of the list under the header Relationships with unsuitable cardinality.
On the View fields tab page, select the fields that you want to copy to the view.
Choose Table fields. All the tables contained in the view are displayed in a dialog box. Select a table. The fields of the table are now displayed in a dialog box. You can copy fields by selecting them in the first column and choosing Copy.
All key fields of the primary table must be included in a maintenance view. In addition, all key fields of secondary tables that are not involved in the foreign key (that is, which are not linked via a join condition to a key field already included in the view) must be included in the view.
This ensures that the records inserted with a maintenance view can be written correctly in the tables contained in the view.
On the Selection conditions tab page, you can (optionally) formulate restrictions for the data records that can be displayed with the view (see Maintaining Selection Conditions for Views).
The selection conditions define the data records that can be selected with the view.
In the Maintenance status tab page, define the maintenance status of the view.
The maintenance status defines how you can access the view data with the standard maintenance transaction (SM30).
Choose .
At activation, a log is written; it can be displayed with Utilities ® Activation log. If errors or warnings occurring when the view was activated, the activation log is automatically displayed.
Go to Transaction SE54 with Environment ® Tab.maint.generator.
From the view definition you can generate maintenance modules and maintenance interfaces that distribute the data entered with the view to the base tables of the view. You can find more information in Creating a Maintenance Dialog.
Other Options
Recording documentation: You can create information about using the view with Goto ® Documentation. This documentation is output for example when you print the view.
Changing the data element of a view field: Select column Mod (modification) for the view field. The Data element field is now ready for input. You can enter a data element that refers to the same domain as the data element of the assigned table field here. Cancel the Mod flag if you want to use the data element of the assigned table field again.
Enter the delivery class of the view: In the Maintenance status tab page, select the delivery class of the maintenance view. If you assign the delivery class G or E to the view, you must also maintain a customer namespace (key block) for the view entries. To navigate to the appropriate maintenance transaction, choose Define Customer Namespace.
Entering the maintenance attributes of the view field: In the View fields tab page you can define the Maintenance Attributes of the view field in column F.
Check functions: With Extras ® Runtime object ® Check you can determine whether the definition of the view in the ABAP Dictionary maintenance screen is identical to the definitions in the runtime object of the view. With Extras ® Runtime object ® Display you can display the runtime object of the view.
table maintai9nenece generator
The Table Maintenance Generator is used to create table maintenance program to add, modify or delete records in the database table. This can be accessed using transaction SE54 or in SE11 using the menu Utilities->Table Maintenance Generator.
Table maintenance allows you to create entries for that table
Follow these steps to generate table maintenance
1) Go to SE11 and check table maintanance check box under attributes tab.
2) Go to menu Utilities -> Table Maintanance Generator ->
Create function group and assign it under function group input box. You can enter same as table name for function group. Also assign authorization group default &NC& .
3) Select standard recording routine radio in table table mainitainence generator to move table contents to quality and production by assigning it to request.
4) Select maintenance type as single step.
5) Maintainence screen as system generated numbers this dialog box appears when you click on create button.
6) Save and activate table.
useful links
http://www.saptechies.com/how-to-create-table-maintenance-generator/
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ecdf446011d189700000e8322d00/content.htm
http://www.saptechies.com/table-maintainance-generator/
with regards,
Hema Sundara.
pls reward if u find it helpful.

What r the trns code for maintenance view, help view and projection view

hi all
what r the transaction code for maintenance view, help view and projection view
can anyone tell me how to create maitenance, help and projection view.
with an example
regs
hari

What is the Different Types and Usage of Views
The followings are different types of views:
- Database View (SE11)
Database views are implement an inner join, that is, only records of the primary table (selected via the join operation) for which the corresponding records of the secondary tables also exist are fetched. Inconsistencies between primary and secondary table could, therefore, lead to a reduced selection set.
In database views, the join conditions can be formulated using equality relationships between any base fields. In the other types of view, they must be taken from existing foreign keys. That is, tables can only be collected in a maintenance or help view if they are linked to one another via foreign keys.
- Help View ( SE54)
Help views are used to output additional information when the online help system is called.
When the F4 button is pressed for a screen field, a check is first made on whether a matchcode is defined for this field. If this is not the case, the help view is displayed in which the check table of the field is the primary table. Thus, for each table no more than one help view can be created, that is, a table can only be primary table in at most one help view.
- Projection View (SE11)
Projection views are used to suppress or mask certain fields in a table (projection), thus minimizing the number of interfaces. This means that only the data that is actually required is exchanged when the database is accessed.
A projection view can draw upon only one table. Selection conditions cannot be specified for projection views.
- Maintenance View ( SE54 )
Maintenance views enable a business-oriented approach to looking at data, while at the same time, making it possible to maintain the data involved. Data from several tables can be summarized in a maintenance view and maintained collectively via this view. That is, the data is entered via the view and then distributed to the underlying tables by the system.
reward points if it is usefull...
Girish

Offline database and table, view, package organization

Hi,
I tried to import my database schema with package, synonyms, tables, and views into a jdev project (11.1.1.1.0) and noticed that unlike the online db view, all object types are imported/organized under one folder (the name of the schema).
For example, online db view shows the following structure
+ my_schema
+ Tables
+ MyTable1
+ Views
+ MyView1
+ Indexes
+ MyIndex1
+ Packages
+ MyPackage1
+ ....
But the imported offline db view shows the following structure that has all different types of db objects listed under myschema folder
+ my_schema
+ MyTable1
+ MyView1
+ MyIndex1
+ MyPackage1
+ ....
This offline representation is hard to work with and unusable if one wants to create database diagrams for different types of large # of database objects.
Any comments?
Thanks,

Hi,
It doesn't sound like it is the different package that is causing this message. Is SB1 a system in your landscape? Are there any differences between the tables?
The message seems to be suggesting that either the second table, or possibly the function group you are using were imported from another system.
Regards,
Nick

Maintenance view- package in another system

Similar Messages

Maybe you are looking for