SM30 in Production

Hi,
I created a table maintenance generator for a Z table (in DEV) and set the recording routine as "Standard recording routine".
In DEV, when the table is changed using SM30, it will ask for a transport request upon saving the changes.
However, in PRD, the table still allows me to change it (using SM30) without asking for a transport request.
May I know why it behaves differently in PRD?
Thanks, GK

Hi Mehwish, can you please let me know how to prevent the user from changing the table entry directly (via SM30) in PRD but instead change it in DEV first and then transport the changes to PRD? Currently, although I already set the table as "Standard recording routine" in the table maintenance generator, it still allows the user to change the table entry directly in PRD and then save it. Thanks.
Mehwish,dadasdd

Similar Messages

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.

CST and LST field mandatory

Hi,
How to make a CST and LST number field mandatory in the vendor Master CIN tab.
Thanks,
Samir Bhatt

Hi Prasad,
Goto SM30 in Production server
Ener the table : J_1IMOCOMP
Select Maintain tab
There you can enter the Plant and othes like CST LST /VAT
Hope it clear.
Regards,
Kishore K

SM30/SM31 and SE16 access in Production systems - Confusion

Hi Security Experts,
Could any one give some information why SE16 or Sm30/SM31 access should not be granted directly in production systems even if its for a custom tables which are assigned to authorisation groups?
I have been going through lot of forums where every one says access to tcodes should be restricted or access need to provided in alternate way but i could not see the clear information on why this is should not be granted?
I can think of risk providing to standard table authorisation groups but i don't understand the reason why custom table access via SM30/Sm31/Se16 should be restricted?
Could any one explain the implications of granting the access directly, if possible please provide information from audit point of view.
In our company there are many users who have got access to SM30/Sm31 to maintain z* tables which are assigned to authorisation groups, is this a security risk?
Please shed some light on this. Your information is much helpful in clearing my doubts and is much appreciated.
Thanks,
Sandhya

What you should also consider is that S_TABU_RFC lets you remotely turn the S_TABU_DIS checks off for specific tables if you create a view to them.
It means that the calling application has taken care of the security before the call and the application user authorizations are correct and the view is correctly designed.
Normally display activity in the debuger (s_develop actvt 03 object type DEBUG) is sufficient in the remote system to see everything in the target system - depending on the authorizations of the technical SYSTEM or COMMUNICATION user. These should ideally not access tables directly.
For table / view comparisons you can use a "current user" destination (or use trusted RFC).
It is unrealistic to restrict users to trouble shoot local problems, so you should ideally implement only the business scenarios for the RFC steps and those should be BAPI application type and not direct table access or generic interfaces to run programs, perform subroutines, install programs, etc.
It is quite easy (with lots of time) to build a catalog of access from the (remote) application to datavia APIs, but you must first get away from the direct table access and control the client access to the generic functions and transactions.
SE16 / Sm30 and many reports and function modules which can very easily be started by adventurous users which offer exactly that.
If the users are doing axactly that then from a security administrator perspective you can only try to restrict it and process "tickets" all day long...
Cheers,
Julius
Edited by: Julius Bussche on Oct 2, 2011 9:12 PM

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

Create a Support Message in Production system showing up in Solution Manage

Has anyone setup the link between creating a support message (under help) in a production system (like ECC) and SAP's Solution Manager.
I understand that it uses BADI SBCOS001 with the interface method PREPARE_FEEDBACK_BO, but when I try to run it, it tells me that Customizing for feedback functionality missing. What functionality is missing? And how to I correct this? And how do I ensure it shows in SAP Solution Manager under a solution or project?
Thanks
Paul

Hi Paul
The only way is to use the IMG. I have just completed this via the IMG info. BUT, it is not that simple.
Make sure your RFC's are trusted and that you have SAP ALL during config.
I hope this will help:
Setup Service Desk
Steps to follow while configuring support desk.
1) Implement the note 903587 .
2) Create all the relevant RFC objects in the satellite system and add the appropriate logical components using transaction SMSY.
3) Check all the objects in the table BCOS_CUST using transaction SM30.
Appl : OSS_MSG
+ :W
DEST :BACK RFC NAME (for solution manager system keep this field as 'NONE')
+ :CUST 620
+ :1.0.
*4) Check whether the BC sets are activated or not using the transaction SCPR20.If the BC sets are not activated then implement the note 898614.The steps to activate the BC sets are described below
4.1) Activate SOLMAN40_SDESK_BASICFUNC_000 BC Set.
4.2) Activate this in expert mode with option u201COverwrite everythingu201D.
4.3) Activation of the following components has to be done by replicating the previous steps
3.1) SOLMAN40_SDESK_TPI_ACT_AST_001
3.2) SOLMAN40_SDESK_ACTIONLOG_001
3.3) SOLMAN40_SDESK_ACT_ADVCLOSE_001
3.4) SOLMAN40_SDESK_TEXTTYPES_001
*Depends upon the number of inactive BC set objects that we have after the upgrade.
4.4) if the actions mentioned in 4.3 are not listed while executing the transaction SCPR20, then implement the note 898614.In the source client 000 of the solution manager system create a transport request using transaction SE09, unpack the file 'PIECELIST_SERVICE_DESK_INIT.ZIP' from the attachment of the note. Copy the contents of the file 'PIECELIST_SERVICE_DESK_INITIAL.TXT' to the transport request. And activate the actions. Use transaction SCC1 to import the transport request to the solution manager client. If any short dump occurs during the activation, implement the note 939116.
5) Check whether the number range is set correctly. If not set the number ranges of basic notification (ABA) and the support desk message (Service transaction SLFN).To be able to use the same number ranges for both message types, the internal number range for basic notification (ABA) must correspond to the external number range for the support desk message.
Number ranges for ABA notifications
5.1) create an internal and external number range using transaction DNO_NOTIF.
5.2) assign number range intervals to groups internal and external.
5.3) SLF1 is the internal number range group
5.4) SLF2 and SLF3 is the external number range interval
5.5) Use transaction DNO_CUST01 to assign message categories to the number range.
5.51) Go to transaction DNO_CUST01
5.52) From the GOTO menu select the menu item DETAILS
5.53) Now you can assign the number range of basis notification (ABA) into the notification type.
The number range for ABA notification is 12 characters in length and to make it compatible with the CRM service transaction insert 2 ZEROES at the beginning.
Number ranges for Support Desk notification
5.54) Use transaction CRMC_NR_RA_SERVICE, and define the internal and external number ranges. Intervals must correspond to the intervals of the basic notifications (ABA notification).
5.6) Then assign both the external and internal numbering
5.61) Go to SPRO and then to SAP Solution Manager
5.62) Then select General Settings and then select Transaction types
5.63) Select the transaction type SLFN and then select the menu item DETAILS from the GOTO menu.
5.64) In the Transaction Numbering block, assign the internal and external number range. The Number Range object should be CRM_SERVIC.
5.7) To view the priorities use transaction DNO_CUST01 and select the notification type as SLF1 and then select priorities from the left pane of the screen. The priorities of the first four cannot be deleted, but new priorities can be added.
6) Check the Action profiles for ABA Notifications (Action profiles are used for synchronization of ABA notification with the CRM Service transaction).
6.1) To check the action profiles use the transaction SPPFCADM and select the application type DNO_NOTIF then select u2018DEFINE ACTION PROFILE AND ACTIONSu2019.
6.2) Select the item u2018SLFN0001_STANDARD_DNOu2019 and then from the menu GOTO, select the menu item DETAILS.
7) The Action profile u2018SLFN0001_STANDARD_DNOu2019 has to be assigned to the message category SLF1 (ABA notifications) using the transaction DNO_CUST01.
8) The action profile for the support desk message can be set to u2018SLFN0001_ADVANCEDu2019.
8.1) From SPRO select SAP Solution Manager then Scenario Specific Settings.
8.2) Select the item Service Desk and then to general settings.
8.3) Execute the category u2018Define Transaction Typesu2019.
8.4) Select the transaction type as SLFN
8.5) From the GOTO menu select the menu item u2018DETAILSu2019 and assign the action profile as SLFN0001_ADVANCED .
9) Activate the partner/ Organization
9.1) Go to CRM->MASTER DATA->BUSINESS PARTNER->INTEGRATION BUSINESS PARTNER ORGANIZATION MANAGEMENT->SET UP INTEGRATION WITH ORGANIZATIONAL MANAGEMENT.
9.2)Find the entries starting with HRALX
HRALX-HRAC WITH VALUE 'X'.
HRALX-OBPON WITH VALUE 'ON'.
HRALX-PBPON u2018ONu2019.
HRALX-MSGRE u2013 u20180u2019.
9.3) If entries are not found create it.
10) Generate Business partner screens
10.1) Go to transaction BUSP.
10.2) Execute the report with the following parameters
CLIENT - Client in which business partners should be created (solution manager client)
APPLICATION OBJECT-
SCREEN - *
Generate all/ selected screens - All screens.
delete sub screen containers -
11) implement SAP note 450640.
11.1) Go to transaction SA38 and select the report CRM_MKTBP_ZCACL_UPDATE_30.
11.2) Execute it with test mode box unchecked.
If a new relationship is to be created then steps 12 and 13 has to be followed
12) To create a relationship category
12.1) Go to transaction BUBA
12.2) Select the entry CRMH00: Undefined relationship
12.3) click on copy
12.4) Rename CRMH00 to ZCRMH00.
12.5) CREATE A RELATIONSHIP CATEGORY.
IN GENERAL DATA FILL LIKE ' FROM BP1 : HAS THE ACTIVITY GROUP '.
' FROM BP2 : IS A PART OF ATTUNE
13) Add the relationship category to the support team partner function
13.1)Use SPRO
IMG GUIDE->SAP SOLUTION MANAGER->SCENARIO SPECIFIC SETTINGS->
-> SERVICE DESK->PARTNER DETERMINATION PROCEDURE->DEFINE PARTNER FUNCTION.
13.2) FIND THE PARTNER FUNCTION SLFN0003 (SUPPORT TEAM).
13.3) In the field relation ship category, Select the newly created relationship category and save.
14) Steps 12 and 13 should be repeated for various business partner types like sold-to-party, message processors if new relationship is to be created for the respective business partner types.
15) Create a new access sequence for the support team determination
15.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
SAP Solution Manager -> Configuration ->
-> Scenario Specific Settings ->Service Desk -> Partner Determination Procedure ->
->Define Access Sequence
15.2) Click on New Entries
15.3) Define a new access sequence with sequence name as u2018Z001u2019 and description u2018NEW BP RELATIONSHIP ACTIVITY GROUPu2019
15.4) Create an new Individual Access with the following value:
u2022 Batch Seq: 10
u2022 Dialog Seq : 10
u2022 Source : Business Partner Relationship.
u2022 Detail on the source:
u2022 Partner Function : Reported By (CRM)
u2022 Mapping/restrictions
u2022 Flag Mapping/definition for partner being Searched
u2022 Partner Function in Source: Support Team (CRM).
Save it.
This Access Sequence will give us the Partner which has the relationship assigned
to the Support Team in the Reported By partner data.
16) Adapt the partner determination schema/Function
16.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
SAP Solution Manager -> Scenario Specific Settings ->Service Desk ->
-> Partner Determination Procedure -> Define Partner Determination Procedure.
16.2) The two options to adapt partner determination schema are
16.21) Adapt the standard Procedure (SLFN0001) or to create a new one by copying the standard one.
16.22) select the line starting with SLFN0001 or the newly created procedure.
16.23) Double Click on Partner Function in Procedure.
16.24) Select the Partner Function "Support Team", and click Details.
16.25) in the detail view only change the Partner Determination/access Sequence to
the one we've just created. Save your entry.
17) Create a root organizational model.
17.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration-> Scenario Specific Settings ->Service Desk -> Organizational Model ->Create a Root Unit for Your Organizational Structure.
17.2) creating an organizational unit by entering the data in the BASIC DATA tab.
17.3) enter the organizational unit, the description and save it.
18) Create the support team organization
18.1) go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Scenario Specific Settings ->Service Desk -> Create Organizational Objects in the Organizational Structure. Or use transaction (PPOMA_CRM).
19) Create the business Partners.
19. 1) Key users- End user (Business Partner General) ,Address should be specified.
19.2) go to the transaction BP.
19.3) create a new Person, Select the role: Business Partner (Gen).
For Identification of the key user
19.31) click on the identification tab
19.32) enter a line in the identification number formatted as follows
IDTYPE : CRM001.
Identification number : <SID><INSTALL NUMBERS><CLIENT><USERNAME>
eg: USER NAME : USER1.
CLIENT : 100.
SID : ER1.
INSTALL NUMBER : 123456789.
IDENTIFICATION NUMBER : ER1 123456789 100 USER1.
20) Message Processors- Support Team members .
20.1) they should be created first as the users in the corresponding client of the solution manager.
20.2) As business partners they will have the role 'EMPLOYEE'.
20.3) Go to transaction BP .
20.4) Create New Person with the role employee.
20.5) In the Identification tab you should enter the user name in the employee data/User Name.
eg: username: proc1
enter proc1 in the field User name.
21) Organizational Business Partner- Organizational BPS have the same country in there main address tab. They should be created through the organizational model. Business partner corresponding to the root organization have the role 'SOLD TO PARTY'.
22) Assign the business partners (Message Processors) to the previously created support team.
22.1) Go to transaction PPOMA_CRM.
22.2) Select the support team 1.
22.3) Click on create
22.4) select position
22.5) call it 'MPROC_T1/Message Processors for team 1
22.6) Replicate it for the other support teams.
22.7) Select the position MPROC_T1/Message Processors for team1 and click assign,
choose owner/Business Partner find and select the business partner
22.8) Validate and Save it.
22.9) If the assignment of business partner is not possible then implement the note 1008656
Or 997009
23) Create the iBase component
23.1) IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings -> Standard Configuration of Basic Settings -> Solution Manager -> iBase -> Initially Create and Assign the Component Systems as iBase Components.
23.2) or use the transaction IB51 to create the installed base.
23.3) it is also possible to create the SOLUTION_MANAGER, select the solution and go to menu Edit -> Initial Data Transfer for iBase.
24)Assign Business Partners to iBase Components
IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings
-> SAP Solution Manager System ->ServiceDesk-> iBase -> Assign Business Partners to iBase Components.
*--optional--
If you want to be able to assign the System Administrator: Go to the IMG: SAP Solution Manager Implementation Guide -> Customer Relationship Management -> Basic Function -> Partner Processing -> Define Partner Determination Procedure.
Select the entry "00000032 Installed Base/IBase" and double click on Partner Functions in Procedure.
Then copy the Entry "Contact Person (CRM)" to a new entry with the partner Function "System Administrator (CRM)" , save it.
Go back to transaction IB52, select a component, and Goto -> Partner, you should be able
now to assign the partner Function "System Administrator".
25) Assign the SAP Standard Role to the user. Message Creator should have the role : SAP_SUPPDESK_PROCESS.
26)Define the transaction variant for the message processors
Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration -> Scenario Specific Settings ->Service Desk -> General Settings -> Specify User Selection Variant.
Here we will create variants for the central message processing transaction CRM_DNO_MONITOR.so that the user will have direct access to there dedicated message.
27) Go to transaction PFCG
27.1) Enter the role name as Z_MSG_PROCESSORS and choose single role.
27.2) Give a description Message Processor role and save it.
27.3) Go to the menu tab and choose add report
27.4) select the report type : ABAP Report
27.5) And in the report enter the report name as 'CRM_DNO_SERVICE_MONITOR'.
27.6) Enter the previously created variant.
27.7) flag the skip initial screen box.
27.8) flag the SAPGUI for windows.
27.9) Create a new transaction with tcode starting with Y or Z.
27.10)Display this transaction and check the values at the bottom of the screen
in the subscreen Default Values, you should have the following parameters:
u2022 D_SREPOVARI-REPORT = CRM_DNO_SERVICE_MONITOR
u2022 D_SREPOVARI-VARIANT = MY_TEAM_MSG
u2022 D_SREPOVARI-NOSELSCRN = X
And also all the user should have the correct role.

Product wise COGS

Dear All
We need to create Plant wise balance sheet to meet statutory requirement . And we have maintained our manufacturing units as segment and as profit centre both. As per process Manufacturing units send goods to Selling Depots and selling depots sold goods to distributor . Sales are getting booked from depot point.
During PGI ...... 1
Cost of Goods Sold      Dr.
To Inventory                Cr.
During Sales .....2
Customer A/c            Dr.
To Sales                Cr.
Our requirement is to capture the Product wise Cost of Goods Sold   during PGI ....How to link Cost of Goods Sold with Product. Currently out structure is designed in such way that all mfg.plant and selling depot as profit centre , Departments and Products are cost centres .
Please guide us how to config the system in SAP so that we can achieve our above mentioned requirement.
Thanks in advacne...
Regards
Animesh

Hi
Whatever you have asked for is pretty standard... I dont know what different you want from it
Frankly speaking, the goal of FI is not to analyse Product wise COGS... Thats the job of COPA
however, you can still manage it from FI.. Execute FBL3N with COGS GL account.... Change the layout and include MATNR Field in your Layout... If it is not available, add it as a Special Field from SM30 - Table T021S (BSEG-MATNR)
MATNR is always updated in te COGS GL Account
br, Ajay M

Show Material Group Long Description in SRM Product Category ?

Hi,
We have entered Short and Long Decriptions for Material Groups in R/3 and we have run the replication too. We want to show the Long Description of the Product Category to the users on the web screens.
We know there is a setting in SRM to do this but we don't know what it is.
Please let me know if any one has idea.
Thanks
venkatesh p

Hi Venkatesh,
You can only transfer one of the two descriptions, if you want Long desc, go to
SM30
COMC_HIERARCHY
NEW ENTRIES
SELECT TRANSFER 60 CHAR DESC.
Thanks
Ravi

Maintaining Table Entries directly in production

Hi All,
I have created a Z table. This table has been moved to production. Currently table entries are transported to production from development client. But this table regularly gets changed and so this needs to be maintained day to day basis. As per the policies transport request to production is moved only at specific times. Client in the production is not modifiable (Closed Client where no change authorization). To maintain the entries in the table every time client in the production should be opened.
Can you please let me know is there any way we can maintain the entries without opening the client for changes and without moving the entries with the transport request? Is there any other way to maintain the entries?
Thanks in Advance,
Shravan G.
Moderator message: please use more descriptive subject lines from now on, changed for you this time.
Edited by: Thomas Zloch on Nov 30, 2010 2:26 PM

Dear,
Create a maintainence view on that Z table. In that Maintainence table select Maint status->Delivery class-> select "Customizing" option. If any one creates new entry in Dev, system popsup for a TR. Those new entries will be saved in to TR. You can transport that TR across landscape.
The above one general practice for customization.
If you dont want that, create a table maintainence dialog on that z table and hence create a tcode with SM30 from SE93 transaction code.
Go to SE93-> select transaction with parameter
                      Enter transaction SM30
                      check Skip initial screen
                      In default values maintain below:
                  VIEWNAME     Z table name
                  UPDATE     x
Using that tcode you can maintain values directly in production
Thanks and Regards,
Edited by: chandra madapati on Nov 30, 2010 6:17 AM

Short dump in production

Hello Friends,
I have a z table and it is working fine in development and quality system and it is giving short dump error when I try to maintain the same table in production using SM30 tcode. Please suggest me what would be the issue here?
Thanks,
Shreekant

Please delete the existing table maintenance view and regenerate the same.
1. SE11 > Table Name > MODIFY
2. Menu.. UTILITIES > Table Maintenance Generator
Keep a screen shot of this screen for future use.
3. Click on DELETE in Apps tool Bar
Then regenerate the Table Maintenance View, as usual.
Regard
Vishal

Is it possible to make a slipstream using the recovery CD (SM30-154 WXP)?

Is it possible to make an slipstream using the product recovery (satelite pro SM30-154 and windows XP home) and die windows XP sp 3 update?
If so, how?
grtz
Bert

Hi
What you could do is to create a new image using a 3rd party application like Norton Ghost for example.
You could firstly install the Windows XP using the Toshiba recovery CD.
Then you could install the MS service pack 3 and then you could create the new image.
Such image could be stored on the new CD or as file on the second partition.
I did it too. Ive got two partitions on my HDD and have created a backup of C (system partition) using the Ghost. The file is stored on D (data partition) and if something will go wrong with my Windows I can restore it using this file.
Easy ;)

How to edit customizing view in production system?

Hi,
I wonder if it is possible to edit customizing view (ex: tcode OAV8) directly in production system. I need a method that doesn't require repair.
Any help will be appreciated..

Hey
You can copy view V_T087G to ZV_T087G. After you have to create a new table maintenance for this view. The new table mainteance will have a Z function module so you can select in the "Dialog Data Transport Details" the flag "no user recording routine" instead of "Standard, recording routine".
After you have to call this table maintenance from Sm30 or from a transaction.
Regards

LSMW recording SM30, prompt for customizing request

Hi everyone,
I'm trying to use lsmw for uploading data into a customizing table. For this I recorded the creation of an entry with transaction sm30. At the end of the recording (when saving) the prompt for a customizing request pops up. When executing the resulting batch input, it get's confused (in my opinion because of the transport request popup in the recording).
Is there a way to prevent the popup?
I've read in a different thread that I can create 1 entry, then do the recording for the lsmw in the same session. This sounds good to me, but I don't see how to do this.
If anybody has an idea how to solve this, it would be great.
Regards,
Monika.

Hi
No u can't prevent that popup, because u're trying to update a customing table: you should considere two main things:
- The call of the request popup can depend on the kind of the client, i.e how the client (dev, test or prod) is set;
- If the cleint is closed, so the modifications are not allowed (for example in production system), your lsmw project can't works.
Anyway by SE11 u can try to create a maitenance view table based on the database table u need to update, leave cutomizing flag and generate the maintenance program (for trx SM30) for this new view: probably now it shouldn't show the popup for the transport (but I'n not sure), if it works u can use it in your project.
It's very hard to manage a table control in LSMW, u can't know how many recodrs u need to update and u can't change the bdc program generated for lsmw.
In this situation the best solution is to insert only one record: i.e. for every record u need to update:
- CALL SM30
- Press NEW ENTRY
- Insert the new record to the top of table control
- Save
- exit
In this way your bdc program doesn't depend on the number of records, as you manage only one record, i.e your project will create a bdc session with as many transaction as many records to be inserted.
Max

Table maintenance in production

Hello Folks,
We have setup SM30 access to users to update Z tables in production. How do we get them to update it without the need for a transport request in Production each time they maintain it?
Is there some setting in SE06 that we need to setup for all custom tables?
Thanks
Prakash

Hi Prakash,
You will require to change the properties of Table Maintainance Generator:
1) Go to SE11, Display table
2) Click on "Utilities" -> "Table Maintainance Generator"
3) For Recording Routine select 2nd radio button i.e. "no, or user, recording routine"
and Activate the Maintainace.
Now if you add the table entry it will not ask for transport. You have to move these changes to Production to take effect.
Hope this answers your query.
Regards
Shital

Z Table which can be maintained in productional environment

How can i define a Z-table so that it is maintainable in production?

Create Table Maintenance generator for your Z table
Goto SE11 give ur table name then click Change
now goto Utilities and click Table Maintenance genrator .
Give Authorization Group,Function group and click Create icon to generate.
You need to provide SM30 authorization for the user for maintaining data in table.
Regards
Rajesh

SM30 in Production

Similar Messages

Maybe you are looking for