topic Re: Table maintenance Standard Recording routine error in Application Development and Automation Discussions

Table maintenance Standard Recording routine error

Former Member — Tue, 07 Feb 2012 06:56:10 GMT

Hi experts,

I have a Ztable of two step view, whose recording routine was no or user recording since user wanted to enter data directly in productio template. Now user doesnot want the data to be entered directly in Production and hence I changed the maintenace generator to standard recording routine.

Now it asks for transport request in Develoment template while saving data, but in QA it allows direct entry and saving data. What could be teh reason for this and how can i resolve this isue.

Thanks in advance.

Re: Table maintenance Standard Recording routine error

Former Member — Tue, 07 Feb 2012 07:34:20 GMT

Hi Satya,

Can you check if your changes are moved to Quality, i mean if the TMG in quality system for the same table is haveing "user routine" or "standard routine".

If it still remains in "user routine" means that your transport with the changes to TMG did not move to quality system yet.

(TMG - table maintenance generator.)

Thanks!

Praveenkumar T.

Re: Table maintenance Standard Recording routine error

Former Member — Tue, 07 Feb 2012 08:36:26 GMT

Hi Praveen,

No the TMG have standard Routine in QA system. in spite of that it is allowing to save the contents directly.

Re: Table maintenance Standard Recording routine error

Former Member — Tue, 07 Feb 2012 08:38:08 GMT

Hi,

As you already moved transport request to quality, when you done any changes , it will allow. But in development side, it will asks new request number.So assign it new request and transport to quality, check the changes

if you select recording routine is no or use it means-no transport request number is asked while saving the entries.

if it is standard ,'it means it will ask for transport request number

Edited by: Parupelly on Feb 7, 2012 2:12 PM

Re: Table maintenance Standard Recording routine error

Former Member — Tue, 07 Feb 2012 08:53:03 GMT

Hi parupelly,

Thanks for your answer. But I already have selected the STandard recording routine and It asks for Transport request while Saving table contents which is correct as per requirement.

But since it is standard routine, it should not allow entering data in QA system. But still it is allowing to enter and save data directly in QA system.

So It is working correctly in Dev system but in QA system also t shd do same.

Re: Table maintenance Standard Recording routine error

SuhaSaha — Tue, 07 Feb 2012 10:25:22 GMT

Hello Satya,

But since it is standard routine, it should not allow entering data in QA system.

I don't think so. Actually the behaviour of "Standard Recording" routine depends on the client settings. You can check the client setting in your QAS via trxn. SCC4.

Read the F1 documentation for further details.

BR,

Suhas

Re: Table maintenance Standard Recording routine error

Former Member — Tue, 07 Feb 2012 10:43:20 GMT

Hi Suhas,

Yes I am surprised only becz of this. I have encountered such problem first time although it is standard recording it allows saving data in QA system directly. I cheked SCC4 as per ur suggestion and found below setting

1. Under Chnages and Transports for client specific objects -> NO changes allowed radio button selected.

2. Cross-client objects : Noc hanges to cross client objects selected.

Can you please let know which settings to check in SCC4 for standard recording.

Re: Table maintenance Standard Recording routine error

SuhaSaha — Tue, 07 Feb 2012 11:32:59 GMT

1. Under Chnages and Transports for client specific objects -> NO changes allowed radio button selected.
2. Cross-client objects : Noc hanges to cross client objects selected.

I think these settings are correct. Lets see what other members have to say.

BR,

Suhas

Re: Table maintenance Standard Recording routine error

Former Member — Tue, 07 Feb 2012 12:20:15 GMT

Hi,

Try providing the following option in client settings.

Transp. connection - 2 ( Customizing in this client cannot be changed )

No cross-client - 3 ( No changes to Repository and cross-client Customizing objs ).