Will values move if maintained in table maintainence sm30

hi,
i have one doubt , i have created a table maintainence sm30, and maintained some values, now if i moved it in to production, will values also move or i have to maintain values in productiona also,
cheers,
vijay

It depends ,but most of the time we maintain data separately i mean system wise.
You can maintain values in production by using SM30 Transaction.
If your client needs transfer data from one system to other system,then you need to create transport request.
Search in forum like " How to transport database records''
Thanks
Seshu

Similar Messages

Error while maintaining a table in SM30

Hi experts,
Im getting the following error when trying to add entries (Maintain) in table T5ASRAUTHMETHOD in SM30 transaction.
The error is " The maintenance dialog foor T5ASRAUTHMETHOD is incomplete or not defined".
Pls tell me how to correct this error.

Hi Shanthi,
the Delivery Class, and the existence of a tablemaintenance dialog,
and the "recording routine" setting. All of this would
be visible through SE11.
Regards,
Md Ziauddin

How to assign 2 transaction codes to maintain a table via SM30

Hi all,
I have created a table with 5 fields. This table must be handled through 2 specific transaction codes (via SM30) in Production system because people from Customs and Packaging departments will directly update it in Production SAP system:
- tcode1 for department1
- tcode2 for department2
through tcode1, department1 should be able to update fields 1, 2 and 3 only.
through tcode2, department2 should be able to update fields 1, 4 and 5 only.
How to handle this?

hi,
1. solution could be by authority objects
2. modification of your dynpro (PBO) dependent on department-
possible if field USR03-ABTLG is available (select user-data with sy-uname)
A.

Insert value to field automatically when maintaining db table

Hi,
I am maintaining Z table in sm30.
The first field is the material code and the second field is the material description (and there are other fields).
The requirement is inserting the description of the material automatically after inserting manually the material code.
How can this requirement be implemented ?
Best Regards.
Ofir

Use event No 5 In table maintenance generator.
Table maintenance Generator -> Environment -> Modification -> Events -> New entries => select event no 5. & do required coding
Regards
Vinod
Edited by: Vinod Kumar on Apr 21, 2010 5:26 PM

Date delimit functionality when maintaining Z table

Hi all,
I have Begin date and End date fields in a Z table and i want to achieve automatic date delimit functionality.
So i have the subscreen area in my screen and called a std program and screen inside the subscreen. I have writen the below coding in the PBO event of my screen.
MODULE DATE_D0001_IF_EXP.
CALL SUBSCREEN DATELIMITS INCLUDING 'SAPLSVIM' '0001'.
" DATELIMITS - name of my subscreen
But when maintaining the table in SM30, the BEGDA and ENDDA field headings are displayed. But those date input fields are not getting displayed.
Can someone tell me why the date fields from the std program, screen are not displayed inside my screen?
Edited by: Shanthi on May 2, 2011 1:59 PM

Hi,
There are some imports being done in the program for screen 0001. Based on these values, the screen fields are made visible and invisible etc.
IMPORT d0001_field_tab
         d0001_status
         x_header TO xheader
         current_date
         date_to_delimit
         date_to_posit
         vim_begdate_name
         vim_enddate_name
    FROM MEMORY ID vim_memory_id_2.
So try doing your validation with the events available in table maintenance,.
Regards,
Harish

Linking intotype listbox to table in sm30 inorder to maintain field values

Hi All,
I got a requirment to create custom infotype with some custom fields adding to stndrd infotype an with also some validations .
So let me know, How to link intotype listbox to table in sm30 inorder to maintain field values?
Thanks for the same.

Hi Vinay,
The best way would be to assign the search help in the table directly and recreate the maintainance...in this manner the search help would be available in the sm30 already..then using "Ëvents" of the table maintainance generator we can validate the fields entered at the time of saving..if a standard search help already exists then t would be availbel in maintainance......
to create events -> go to se11 -> utilities -> table maintainance generator -> click '
then go to environment -> modification -> events ..in the table control..create new entries ....and select the suitable event and write the code in the routine to do validations
Hope it helps
Pls check and revert
Regards
Byju

Gr/ir slip field value is not stored in table mkpf..!!

dear sap gurus,
    i have a typical problem.. i am doing Transfer posting from one storage location to another. using MB1B with 311 mov type.. and mentioning some values in the gr/ir slip field.. but system is not storing the value in table..
Can any one say how to solve this.. if i use MIGO_TR then its storinghte value i mentioned in MKPF table..
Regard,
Manu

Hi Manu,
This GR/GI slip number has only been designed for use in those countries (for example, Italy) whose legislation requires specification of this number for goods that leave the plant and are transported on public roads. In other countries, the material document number printed on the GR/GI slip (in the standard system) is usually sufficient. To enter external documents, you can use the field Material slip or Delivery note.
If still wants to use this field you are required make relevent settings in config.
Please go to transaction OMC1.
There you will find 4 push buttons.
   1. Activation of GR/IR slip for plant.
   2. Number range grouping code.
   3. Intervals for number range.
   4. Object(here you are assigning the number range for the plant, storage location and movement type.
This will allow you to store GR/IR slip number in MKPF with trx. MB1B
Regards
Mauro

Move data from one table to another table

Hi all,
I had a custom table called sales_data in that table there are columns like JAn,FEB,upto DEC including other columns so in each month there is some data total data is 23000 count but each month has has specific data like JAn-2500,FEB-2000 like that it has total 23000 records
My Requirement is i have to move data from one table to another table that too if i will pass jan only jan data should move like that feb,march,.....
in my table there is no month column i had get it from another table called gl_periods and by using cursor and case function i have written the code
well while when i am inserting data am passing year,month as parameters but 23000 data is moving it should get like that.
Please suggest me.its urgent
Thank You

Hi hamid,
               Please go through the below procedure.
CREATE OR REPLACE PROCEDURE APPS.copy_sales_to_forecast(p_fiscal_year varchar2,p_month number)
IS
CURSOR C1 IS select period_year,period_num,start_date,end_date from apps.gl_periods
             where period_set_name='Accounting'
             and   period_year=p_fiscal_year
             and   period_num<=p_month;
type type1 is table of xxc_forecast_data%rowtype;
t1 type1;
BEGIN
FOR CREC IN C1 LOOP
BEGIN
DELETE FROM xxc_forecast2
where fiscal_year = crec.period_year
and attribute1='Copied From Sales to Forecast Table of Month '||crec.period_num;
END;
SELECT
product_category           ,
product_sub_category       ,
product_line               ,
product_style              ,
item_number                ,
item_description           ,
customer_name              ,
customer_number            ,
sales_channel              ,
null      ,
CASE
    WHEN crec.period_num=1 THEN sales_amount_month1
    ELSE 0
END Transaction_quantity_period1,
CASE
    WHEN crec.period_num=1 THEN sales_cost_month1
    ELSE 0
END item_cogs_period1,
CASE
    WHEN crec.period_num=1 THEN sales_mtl_cost_month1
    ELSE 0
END item_material_cogs_period1 ,
CASE
    WHEN crec.period_num=1 THEN sales_mtl_ovhd_cost_month1
    ELSE 0
END item_mtl_ovhd_cogs_period1,
CASE
    WHEN crec.period_num=1 THEN sales_res_cost_month1
    ELSE 0
END item_resource_cogs_period1,
CASE
    WHEN crec.period_num=1 THEN sales_op_cost_month1
    ELSE 0
END item_op_cogs_period1,
CASE
    WHEN crec.period_num=1 THEN sales_ovhd_month1
    ELSE 0
END item_ovhd_cogs_period1,
CASE
    WHEN crec.period_num=1 THEN sales_units_month1
    ELSE 0
END extended_amount_us_period1,
CASE
    WHEN crec.period_num=2 THEN sales_amount_month2
    ELSE 0
END Transaction_quantity_period2,
CASE
    WHEN crec.period_num=2 THEN sales_mtl_cost_month2
    ELSE 0
END item_material_cogs_period2,
CASE
    WHEN crec.period_num=2 THEN sales_mtl_ovhd_cost_month2
    ELSE 0
END item_mtl_ovhd_cogs_period2,
CASE
    WHEN crec.period_num=2 THEN sales_res_cost_month2
    ELSE 0
END item_resource_cogs_period2,
CASE
    WHEN crec.period_num=2 THEN sales_op_cost_month2
    ELSE 0
END item_op_cogs_period2,
CASE
    WHEN crec.period_num=2 THEN sales_ovhd_month2
    ELSE 0
END item_ovhd_cogs_period2,
   CASE
    WHEN crec.period_num=2 THEN sales_units_month2
    ELSE 0
END extended_amount_us_period2,
CASE
    WHEN crec.period_num=3 THEN sales_amount_month3
    ELSE 0
END Transaction_quantity_period3,
CASE
    WHEN crec.period_num=3 THEN sales_mtl_cost_month3
    ELSE 0
END item_material_cogs_period3,
CASE
    WHEN crec.period_num=3 THEN sales_mtl_ovhd_cost_month3
    ELSE 0
END item_mtl_ovhd_cogs_period3,
CASE
    WHEN crec.period_num=3 THEN sales_res_cost_month3
    ELSE 0
END item_resource_cogs_period3,
CASE
    WHEN crec.period_num=3 THEN sales_op_cost_month3
    ELSE 0
END item_op_cogs_period3,
CASE
    WHEN crec.period_num=3 THEN sales_ovhd_month3
    ELSE 0
END item_ovhd_cogs_period3,
CASE
    WHEN crec.period_num=3 THEN sales_units_month3
    ELSE 0
END extended_amount_us_period3,
CASE
    WHEN crec.period_num=4 THEN sales_amount_month4
    ELSE 0
END Transaction_quantity_period4,
CASE
    WHEN crec.period_num=4 THEN sales_mtl_cost_month4
    ELSE 0
END item_material_cogs_period4,
CASE
    WHEN crec.period_num=4 THEN sales_mtl_ovhd_cost_month4
    ELSE 0
END item_mtl_ovhd_cogs_period4,
CASE
    WHEN crec.period_num=4 THEN sales_res_cost_month4
    ELSE 0
END item_resource_cogs_period4,
CASE
    WHEN crec.period_num=4 THEN sales_op_cost_month4
    ELSE 0
END item_op_cogs_period4,
CASE
    WHEN crec.period_num=4 THEN sales_ovhd_month4
    ELSE 0
END item_ovhd_cogs_period4,
CASE
    WHEN crec.period_num=4 THEN sales_units_month4
    ELSE 0
END extended_amount_us_period4,
CASE
    WHEN crec.period_num=5 THEN sales_amount_month5
    ELSE 0
END Transaction_quantity_period5,
CASE
    WHEN crec.period_num=5 THEN sales_mtl_cost_month5
    ELSE 0
END item_material_cogs_period5,
CASE
    WHEN crec.period_num=5 THEN sales_mtl_ovhd_cost_month5
    ELSE 0
END item_mtl_ovhd_cogs_period5,
CASE
    WHEN crec.period_num=5 THEN sales_res_cost_month5
    ELSE 0
END item_resource_cogs_period5,
CASE
    WHEN crec.period_num=5 THEN sales_op_cost_month5
    ELSE 0
END item_op_cogs_period5,
CASE
    WHEN crec.period_num=5 THEN sales_ovhd_month5
    ELSE 0
END item_ovhd_cogs_period5,
CASE
    WHEN crec.period_num=5 THEN sales_units_month5
    ELSE 0
END extended_amount_us_period5,
CASE
    WHEN crec.period_num=6 THEN sales_amount_month6
    ELSE 0
END Transaction_quantity_period6,
CASE
    WHEN crec.period_num=6 THEN sales_mtl_cost_month6
    ELSE 0
END item_material_cogs_period6,
CASE
    WHEN crec.period_num=6 THEN sales_mtl_ovhd_cost_month6
    ELSE 0
END item_mtl_ovhd_cogs_period6,
CASE
    WHEN crec.period_num=6 THEN sales_res_cost_month6
    ELSE 0
END item_resource_cogs_period6,
CASE
    WHEN crec.period_num=6 THEN sales_op_cost_month6
    ELSE 0
END item_op_cogs_period6,
CASE
    WHEN crec.period_num=6 THEN sales_ovhd_month6
    ELSE 0
END item_ovhd_cogs_period6,
   CASE
    WHEN crec.period_num=6 THEN sales_units_month6
    ELSE 0
END extended_amount_us_period6,
CASE
    WHEN crec.period_num=7 THEN sales_amount_month7
    ELSE 0
END Transaction_quantity_period7,
CASE
    WHEN crec.period_num=7 THEN sales_mtl_cost_month7
    ELSE 0
END item_material_cogs_period7,
CASE
    WHEN crec.period_num=7 THEN sales_mtl_ovhd_cost_month7
    ELSE 0
END item_mtl_ovhd_cogs_period7,
CASE
    WHEN crec.period_num=7 THEN sales_res_cost_month7
    ELSE 0
END item_resource_cogs_period7,
CASE
    WHEN crec.period_num=7 THEN sales_op_cost_month7
    ELSE 0
END item_op_cogs_period7,
CASE
    WHEN crec.period_num=7 THEN sales_ovhd_month7
    ELSE 0
END item_ovhd_cogs_period7,
CASE
    WHEN crec.period_num=7 THEN sales_units_month7
    ELSE 0
END extended_amount_us_period7,
CASE
    WHEN crec.period_num=8 THEN sales_amount_month8
    ELSE 0
END Transaction_quantity_period8,
CASE
    WHEN crec.period_num=8 THEN sales_mtl_cost_month8
    ELSE 0
END item_material_cogs_period8,
CASE
    WHEN crec.period_num=8 THEN sales_mtl_ovhd_cost_month8
    ELSE 0
END item_mtl_ovhd_cogs_period8,
CASE
    WHEN crec.period_num=8 THEN sales_res_cost_month8
    ELSE 0
END item_resource_cogs_period7,
CASE
    WHEN crec.period_num=8 THEN sales_op_cost_month8
    ELSE 0
END item_op_cogs_period8,
CASE
    WHEN crec.period_num=8 THEN sales_ovhd_month8
    ELSE 0
END item_ovhd_cogs_period8,
CASE
    WHEN crec.period_num=8 THEN sales_units_month8
    ELSE 0
END extended_amount_us_period8,
CASE
    WHEN crec.period_num=9 THEN sales_amount_month9
    ELSE 0
END Transaction_quantity_period9,
CASE
    WHEN crec.period_num=9 THEN sales_mtl_cost_month9
    ELSE 0
END item_material_cogs_period9,
CASE
    WHEN crec.period_num=9 THEN sales_mtl_ovhd_cost_month9
    ELSE 0
END item_mtl_ovhd_cogs_period9,
CASE
    WHEN crec.period_num=9 THEN sales_res_cost_month9
    ELSE 0
END item_resource_cogs_period7,
CASE
    WHEN crec.period_num=9 THEN sales_op_cost_month9
    ELSE 0
END item_op_cogs_period9,
CASE
    WHEN crec.period_num=9 THEN sales_ovhd_month9
    ELSE 0
END item_ovhd_cogs_period9,
   CASE
    WHEN crec.period_num=9 THEN sales_units_month9
    ELSE 0
END extended_amount_us_period9,
CASE
    WHEN crec.period_num=10 THEN sales_amount_month10
    ELSE 0
END Transaction_quantity_period10,
CASE
    WHEN crec.period_num=10 THEN sales_mtl_cost_month10
    ELSE 0
END item_material_cogs_period10,
CASE
    WHEN crec.period_num=10 THEN sales_mtl_ovhd_cost_month10
    ELSE 0
END item_mtl_ovhd_cogs_period10,
CASE
    WHEN crec.period_num=10 THEN sales_res_cost_month10
    ELSE 0
END item_resource_cogs_period10,
CASE
    WHEN crec.period_num=10 THEN sales_op_cost_month10
    ELSE 0
END item_op_cogs_period10,
CASE
    WHEN crec.period_num=10 THEN sales_ovhd_month10
    ELSE 0
END item_ovhd_cogs_period10,
CASE
    WHEN crec.period_num=10 THEN sales_units_month10
    ELSE 0
END extended_amount_us_period10,
CASE
    WHEN crec.period_num=11 THEN sales_amount_month11
    ELSE 0
END Transaction_quantity_period11,
CASE
    WHEN crec.period_num=11 THEN sales_mtl_cost_month11
    ELSE 0
END item_material_cogs_period11,
CASE
    WHEN crec.period_num=11 THEN sales_mtl_ovhd_cost_month11
    ELSE 0
END item_mtl_ovhd_cogs_period11,
CASE
    WHEN crec.period_num=11 THEN sales_res_cost_month11
    ELSE 0
END item_resource_cogs_period11,
CASE
    WHEN crec.period_num=11 THEN sales_op_cost_month11
    ELSE 0
END item_op_cogs_period11,
CASE
    WHEN crec.period_num=11 THEN sales_ovhd_month11
    ELSE 0
END item_ovhd_cogs_period11,
CASE
    WHEN crec.period_num=11 THEN sales_units_month11
    ELSE 0
END extended_amount_us_period11,
CASE
    WHEN crec.period_num=12 THEN sales_amount_month12
    ELSE 0
END Transaction_quantity_period12,
CASE
    WHEN crec.period_num=12 THEN sales_mtl_cost_month12
    ELSE 0
END item_material_cogs_period12,
CASE
    WHEN crec.period_num=12 THEN sales_mtl_ovhd_cost_month12
    ELSE 0
END item_mtl_ovhd_cogs_period12,
CASE
    WHEN crec.period_num=12 THEN sales_res_cost_month12
    ELSE 0
END item_resource_cogs_period12,
CASE
    WHEN crec.period_num=12 THEN sales_op_cost_month12
    ELSE 0
END item_op_cogs_period12,
CASE
    WHEN crec.period_num=12 THEN sales_ovhd_month12
    ELSE 0
END item_ovhd_cogs_period12,
    CASE
    WHEN crec.period_num=12 THEN sales_units_month12
    ELSE 0
END extended_amount_us_period12,
CASE
    WHEN crec.period_num=2 THEN sales_cost_month2
    ELSE 0
END item_cogs_period2,
   CASE
    WHEN crec.period_num=3 THEN sales_cost_month3
    ELSE 0
END item_cogs_period3,
   CASE
    WHEN crec.period_num=4 THEN sales_cost_month4
    ELSE 0
END item_cogs_period4,
   CASE
    WHEN crec.period_num=5 THEN sales_cost_month5
    ELSE 0
END item_cogs_period5,
CASE
    WHEN crec.period_num=6 THEN sales_cost_month6
    ELSE 0
END item_cogs_period6,
CASE
    WHEN crec.period_num=7 THEN sales_cost_month7
    ELSE 0
END item_cogs_period7,
   CASE
    WHEN crec.period_num=8 THEN sales_cost_month8
    ELSE 0
END item_cogs_period8,
CASE
    WHEN crec.period_num=9 THEN sales_cost_month9
    ELSE 0
END item_cogs_period9,
   CASE
    WHEN crec.period_num=10 THEN sales_cost_month10
    ELSE 0
END item_cogs_period10,
   CASE
    WHEN crec.period_num=11 THEN sales_cost_month11
    ELSE 0
END item_cogs_period11,
CASE
    WHEN crec.period_num=12 THEN sales_cost_month12
    ELSE 0
END item_cogs_period12,
a.fiscal_year   ,
a.budget_entity ,
a.organization_code,
a.customer_id ,
a.inventory_item_id ,
NULL,
NULL,
a.created_by ,
a.last_updated_by ,
a.creation_date ,
a.last_update_date ,
'Copied From Sales to Forecast Table of Month '||crec.period_num,
a.attribute2,
a.attribute3 ,
a.attribute4 ,
a.attribute5 ,
a.attribute6 ,
a.attribute7 ,
a.attribute8 ,
a.attribute9 ,
a.attribute10,
a.attribute11,
a.attribute12,
a.attribute13,
a.attribute14,
a.attribute15
bulk collect into t1
FROM xxc_sales_data a
where a.fiscal_year          = crec.period_year
having CASE
             WHEN crec.period_num=1 THEN sum(sales_amount_month1)
             WHEN crec.period_num=2 THEN sum(sales_amount_month2)
             WHEN crec.period_num=3 THEN sum(sales_amount_month3)
             WHEN crec.period_num=4 THEN sum(sales_amount_month4)
             WHEN crec.period_num=5 THEN sum(sales_amount_month5)
             WHEN crec.period_num=6 THEN sum(sales_amount_month6)
             WHEN crec.period_num=7 THEN sum(sales_amount_month7)
             WHEN crec.period_num=8 THEN sum(sales_amount_month8)
             WHEN crec.period_num=9 THEN sum(sales_amount_month9)
             WHEN crec.period_num=10 THEN sum(sales_amount_month10)
             WHEN crec.period_num=11 THEN sum(sales_amount_month11)
             WHEN crec.period_num=12 THEN sum(sales_amount_month12)
            END !=0;
FORALL i IN t1.first .. t1.last
INSERT INTO xxc_forecast2 VALUES t1(i);
--commit;
END LOOP;
END;
Thank You

How to move field symbol internal table to internal table with header line?

Dear all,
hi...hereby i would like to ask how i can move field symbol internal table to a internal table?
as i know field symbol internal table is without header line..
so, may i know how to do this....to move field symbol internal table to internal table which consist of header line and field and record will same as field symbol internal table...in additional, my field symbol internal table is dynamic table mean everytime will have flexible columns..?
Please advise...
Thanks
Regard,
ToToRo.
Edited by: @ToToRo@ on Aug 20, 2009 6:16 AM

Hello,
Try this way:
If both the type of internal tables are same then you can directly assign dynamic internal table to static internal table.
itab = <itab>.
Suppose you have field symbol internal table <itab> which is different in structure from ITAB.
Now, you can create <wa> as follow:
FIELD-SYMBOLS <wa>.
DATA wa TYPE REF TO DATA.
CREATE DATA wa TYPE LINE OF <itab>.
ASSIGN wa->* to <wa>.
This way your work area is read.
Using [ASSIGN COMPONENT|http://help.sap.com/saphelp_nw04/helpdata/EN/fc/eb3923358411d1829f0000e829fbfe/content.htm] syntax you can read required component of <wa>.
Finally you can use that value to load static internal table.
You can also refer to my thread on [Dynamic table|Re: Creating Dynamic table].
Hope this helps!
Thanks,
Augustin.
Edited by: Augustarian on Aug 20, 2009 10:06 AM

Maintain separate table for these fields

I want to maintain separate table for this fields.
1. Sales order number
2.item number
3.material
4.qty pricing date price change date if u user changes price manually.
5. Order price
6.sales value
Where will we get these fields from which table.

Hi,
1. Sales order number = VBAK-VBELN
2.item number = VBAP-POSNR
3.material = VBAP-MATNR
4.qty pricing date price change date if u user changes price manually.
Qty from VBAP-KWMENG
Price date = VBKD-PRSDT
Change Date = VBAK-AEDAT
5. Order price = VBAK-NETWR
Thanks,
Mandar

Problem with maintain table views SM30 Transaction

Hello All,
i have a problem with the table maintenance view SM30, it doesn't permit me to modify the rows in the table.
we have added a field into the table and when i tried to change the table view from menu: Utilities ==> table maintenance generator==> change the system propose me a message that the screen 0001 will be deleted and recreated...but the system has deleted the screen and doesn't recreate it...in somewehere on internet we find that we should use the transaction SE55 menu:
Environment==> modification ==> Maintenance screen ==> button Layout which open the tool Screen Painter and from that we have created our screen with 4 fields of our table...our result that the screen is created and i can see it from the SM30 transaction but i can't insert rows in the table...when i try to go to maintain table: menu: Utilities ==> Table maintenance generator to try if i can modify something the system give me a message: "set the compare flag dialog ZIV_DP_PLCHAR_LA"
the ZIV_DP_PLCHAR_LA is the name of my table...
can you give me some advices please how should i do to fix this problem to insert rows in table throughout the transaction
SM30 "maintain table views: initial screen"
if i want to delete the screen from the SE55 transaction to recreate it newly what should i do to take care about some options
to have a new screen?
thanks for all
Bilal

Hi
First delete the old table maintainence generator.
Now Recreate the screen and your table is good to go..
These error messages come when we add new fields and different version of the table maintainence generator in database.

Restriction for table maintainence

Hello Gurus,
I am working on a SLO project, where i had merged 5 source systems to one system.
In few roles in source systems for table maintainence the authorization groups is maintained as '*' in production.
In source systems if they maintain * they would be able to display/change the data related to that system only.
But now in target system , if we maintain * in authorization group they are able to display/change the data related to all the 5 systems.
This need to restricted, Please provide some pointers on how this can be done.
This restriction should be in such a way that they should be able to change data related to the system they belong to .
Thanks,
Sanketh.

>
Sanketh Teegala wrote:
> Thanks for the reply prashanth.
>
> But , suppose consider users are maintaining table T001B. ( they are maintaining it through parameter transactions).
> as it is a standard table it has been assigned to same authorization group in both source and target systems.
> In source system , user is able to view data related only that system.
> But in target system user is able to view other system data also.
>
> How can i restrict this data ?
>
> Thanks,
> Sanketh.
Hi Sanketh,
I hope you are progressing with your SLO task. Once you have finished this project, most things will be simple in comparison
Unfortunately your requirement is not a simple one
You could use line item auths (nasty to set up IMO). Have a search for info on auth object S_TABU_LIN
Alternatively you could introduce auth checks on key auth fields (e.g. BUKRS, WERKS etc) into the method that you use to display table data. This would likely require new transactions with validation code that is performed before data is displayed or limits what can be updated. Another messy approach would be to use parameter transactions that pass in an org unit into the table selection criteria. You would need one for each org unit so will likely not be practicable.
What I would say is that focus on what is legally required. If none of it is required by law then focus on getting the rest of your consolidation done first and then address this in partnership with your project development team.

Sorting in table maintainence

hi
i need to have sorting icon in a table maintainece i have crated
a table maintainece tcod in se93 for a table but when i execure teh tcode and go to table maintianece
no sorting icons are shown
my requirment is that user is able to sort on basis or the fields in the table also
pls suggest how to do it.
regards
Arora

first u need to go to /nse11->give the table ->table maintainence generator->click on the Maintain screen-> ..it will take u to a module pool program.
then go to screen .place a button for sort and then write logic for sort in the PAI of the module pool.This should work...
Revert back if any doubt
Reema

COPA user-defined charact. w. own value maint. with existing check-table

Dear Experts,
I need to create a user-defined characteristic with own value maintenance with the pecularity that it needs to refer to the same check table as another user-defined characteristic with own value maintenance.
Could anybody explain me how I can do that?
Thanks in advance for your kind support.
Best Regards,
Eric

Hi Eric,
Generally when you are creating user defined charachteristic with own value maintainance check table is created by the system. So you requirement is not possible to achieve. As a workaounr you can create two char as you want and then copy the content of the first check table to the second one. This will have the same impact as what you have described.
Best Regards,
Abhisek Patnaik

How to maintain BNKA table.

Hi,
I have a requirement to Maintain the table BNKA, where i can able to change the selected entries of the table.
This we can do normally by creating the maintainance view for the table. This case we cannot as this is a standard table.
Could you please let me know a solution to change the selected entries of the table. Is updating the BNKA table using Zprogram is preferable.
Will highly appreciate the solution.
Thanks,
Phani Kumar.

Hi Pani,
please check this
http://sap.ittoolbox.com/groups/technical-functional/sap-hr/bnka-table-values-1501810
https://forums.sdn.sap.com/message.jspa?messageID=7242137
https://forums.sdn.sap.com/message.jspa?messageID=8581624
standard report-RFBVALL_0
Hope there is some clue
No Worries
KG

Will values move if maintained in table maintainence sm30

Similar Messages

Maybe you are looking for