Transport requests.

[Former Member]

Hi Gurus.,

Can any one say the configurations in SPRO which doesnt require to save in transport requets

Thanks in advance

Narayana

[Former Member · Accepted solution]

hi,

it is actually and fully controlled by basis guys in real-time landscape .

and in sap any customising change/creation in spro requires transport requests and basis cannot stop this logically. but if it is not connnected to production servers then it will be controlled by basis.

reward if helps !!!!!!!!!!!!!!!!!!!!!!!!

[Former Member]

No this is not possiblein standard SAP.

regards and reward if it helps.

Kumar sri

[Former Member]

Hello,

All the customisations in SPRO fall in either of customisation request or workbench request, hence the transport request is required if the settings needs to be transported along the servers (say from development to quality/production).

Maintainance of the master records(customer, material), condition records doest not come under customisation settings, but the basic settings in SPRO fall in the customisation request category ( eg: fields in account group for CMR which need to be mandatory, optional, suppressed) and hence require transport request.

If any setting in SPRO directly done in production server doesnot require any transport request.

[Former Member]

Hello,

All the customisations in SPRO fall in either of customisation request or workbench request, hence the transport request is required if the settings needs to be transported along the servers (say from development to quality/production).

Maintainance of the master records(customer, material), condition records doest not come under customisation settings, but the basic settings in SPRO fall in the customisation request category ( eg: fields in account group for CMR which need to be mandatory, optional, suppressed) and hence require transport request.

If any setting in SPRO directly done in production server doesnot require any transport request.

[Former Member]

Transport Request is generated in following scenarios:

1. Customizing Request - When doing or changing some customization.

2. WorkBench Request - When configuration is cross-client. Eg Generating new Table, making changes in access sequence, Abap development, etc.

Transport request is not generated for Master Data. For eg: Customer Master, Material Master, price master, etc.

Benefit of Transport Request:

SAP Landscape normally has 3- Tier system:

Development Server - Where customization takes place. Transport request is generated at this level & then first transported to Quality server for testing whether it meets the requirement or not. Once the requirement is met in Quality server then Request is transported from Development Server to Production Server (Actual / Live System)

Quality Server - Mainly useful for testing.

Production Server Actual / Live server, where the real transactions are created & posted.

Regards,

Rajesh Banka

Reward Points if Helpful.

[Former Member]

Hi Manam,

As per my understanding, most of the config done in spro will generate a Transport request. and this I think can be controlled by Basis guys. for more infor it is better to consult a basis consultant who can throw more light on this issue.

regards

Srini

[Former Member]

Hi Naryana

There are number ranges,taxcodes,G/L accounts,master data are not required for transport requests. Because these are client dependent.

Regarding the Abap program you can save these program aas a local objects, so then it will not ask the transport request.

Reward points if it is helpful

[Former Member]

Hi ,

Most of the times its master data. Customer and material master data does not trigger transport requests. Similarly condition records and standard texts.

Standard texts need to be manually included in the transport requests.

Hope this helps,

Thanks & regards,

CLN