Releasing Customizing Request

Hi All,
I have created a layout in FBL3N in development and saved it as a customizing Request.
While releasing this request it show an error message
"8: Transport carried out with errors.
Individual objects could not be transported successfully"
How to solve this issue.
Thanks,
Bala G

Dear Markus ,
Thanks for your reply, I am repeating the same with for clear understanding
this customizing request created and released, after releasing the request ( carries 5 objects in main task and 2 in Sub task)
from DEV to PRD , when we opened the same request after importing into PRD we found the main task objects are available but
the subtask or child task objects are missing, we tried recreating a new task and tried but still not working what is the problem
Hope this is clear?
regards
Praveen

Similar Messages

How can I re-release the Customizing request

Hi,
Yesterday, I released a customizing request to QAS. At the QAS, I used the T-code STMS to check the import request, I could not find out it.
But, today, I released another customizing request to QAS. I can find out it. I don't known what had happened.
Could I re-release the CR? How to deal with this question?
Waiting for answer, THX
jk

Dear all,
Thanks for your time. The problem is still have.
I have released the Task and Sub-task, and I checked the import queue in which there isn't the TR.
I released a new customizing request, it can be find out the import queue.
I think the transport routes maybe have problem at yesterday, so I want to re-transport the customizing request.
Which method can I choose to do that?
jk

Unable to release transport request because of control program tp

I have create a customized transaction type as a copy of urgent correction SDHF. I am not able to release the transport requests using the action in the toolbox 'Release Transport Request' and I obtain the following error in the log:
could not start transport control program tp
But if I directly execute the task 'Release Transport Request' in the task list, it works.
Another strange thing is that at the beginning both ways worked, but after some days I started to have this problem.
Thanks
Antonello

I did not find any note about this error.
Someone can help me?
Thanks.
Antonello

Customizing request

Hi All,
what is the difference between Parent Request and Child Request?
Regards,
Sasmita

Child Request can be considered as the request which actually holds the objects to be transported & resides within Parent Request / Main Request. In T.Code: SE10, we select the appropriate request & expand the same. Now we can see the child request / request holding objects. First we release the Child request & then we release the main request, which is to be imformed to basis consultant along with approval from your project manager to be imported to relevant server.
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.

Customizing request for a workflow

Dear experts,
I have created a workflow. I want to move the workflow from one client to other for testing it. For this i need to transport workbench and customizing requests of my workflow. Can you please tell me how to find the workbench and customizing request of my workflow. Is there any option in SWDD which will show the specific workflow & customizing request for that workflow.

Hi,
se01 will help you find the transport with your workflow but not the any other transports which may be part of your workflow project.
se10 transaction can be used to see transports by user. Check off both customizing and workbench requests since you will have both types of transports. The user id needs to be that of the developer that created the transport. Modified vs Released - select both if you are not sure if the transports have been released or not.
Paul.

Customizing request: Table T001L

Hi,
We are currently customizing SAP in two parallell ongoing projects. IN both projects, we must create entries in table T001L (storage locations). But the customizing must be transported at different times.
Our question: When the customizing request is released; will the complete table T001L be included in the transport or ONLY the newly added entries that were added in this request?
Our concern is that we ONLY want to include some of the storage locations in the request not all newly added entries in table T001L,
Have you come across this issue, please advice,
//Eva

SAP automatically creates a transport request for any new added locations.
It is certainly not the entire table that gets transported, like it is for calendars or account assignments.
However you can create at any time a manual transport and only include what you like.
But ..... I recommend to release the transports soon with its compelte entries, this causes less issues than keeping transports for a long time and then releasing it ( after an other one has done customizing later but transported earlier ).
I have seen it many times, especially if you transport entire table and do not release it, that newer entries got overwritten by old customizing.

Customizing Request not Prompting while saving the spro setting

Hi Everybody
I configured some settings in spro like PROUCT ALLOCATION, ATP Group etc.
While creating those objects customizing request was assigned to all my configuration settings in spro.
Recently i unlocked the request in se03 and deleted the Customizing request because it was not in the sequence.
Now when i go to the same transaction and save the object it is not prompting me new customizing request.
When i change existing settings then system is prompting the Custoizing request.
I would like to reassign custoizing request for all my objects which were created earliar.
Please help.
Thanks in Advance.

Hi,
Generally in SAP If u have changed any object whether it is customize or Workbench object once it is saved in one request and if u have deleted the same form request and if u r trying to change the same objects then the system will automatically save into the same request.
IF the old request is released then system will ask new request.Please check the old request ...
Regards,
Srinivas

Customizing request & Workbench request

Dear all,
What is the differance between Customizing Request & workbench request?

Hi,
Workbench Requests
When you change a Repository object of the ABAP Workbench, a query window appears in which you need to specify a Workbench request. You can only save the changes if you have assigned the object to a change request.
Workbench requests and the tasks assigned to them are normally used to record changes to Repository objects and Customizing for all clients. However, you can also include client-specific Customizing.
Whether the changes to Repository objects are transported depends on whether a transport route is defined from the current SAP System for the package of these objects. From the system settings, the system automatically determines whether the change requests are transportable and to which target system they should be transported.
Workbench requests record changes made to ABAP Workbench objects.
There are local and transportable Workbench requests. (Local Workbench requests have the target system <space>.)
The package of the object and the transport route settings in the Transport Management System determine whether changes are recorded in a local or a transportable Workbench request.
Customizing requests
Customizing requests record client-specific Customizing settings made in a single client (the source client of the request).
Automatic recording of configuration activities in the Customizing work for a client can be activated or deactivated for each client with Client Control. If automatic recording is active, a query window appears when you change Customizing settings, asking you to specify a Customizing request.
Whether Customizing requests are transported or not, does not depend on the objects entered, as is the case with Workbench change requests. The Customizing requests in an SAP System (or in a client if you use Extended Transport Control) are either all transportable or all local, depending on the system setting. The system uses the standard transport layer to determine automatically whether the change requests are transportable and to which target system they should be transported. However, you can change this manually.
Changes to Customizing settings are recorded in Customizing requests.
When you release the requests, the current status of the recorded settings is exported, and can then be imported into the consolidation system and, if necessary, into subsequent delivery systems.
The client settings determine whether
o changes to the Customizing settings are possible
o the changes are recorded
When you create Customizing requests, the transport target is automatically assigned the standard transport layer by the R/3 System.
Regards,
Satish

Problem while releasing the request

I created a customized Z report from the existing standard SAP report and also created a new tcode into the development server, and released the request via se09 into quality server. Now when I try to execute this tcode in the quality server, its giving me a error message 'status STANDARD of the user interface ZRM06ENDR_ALV missing'. Due to which its not displaying various push buttons like 'print preview' 'messages' etc. However its working fine in the dev server

You should creat GUI status. You can copy it from another report by clicking right on the gui status from which you copy. Then specify the target report. Then in your Z report activate the gui status. Also write the code below:
form alv_menu using rt_extab type slis_t_extab.
set pf-status 'STANDARD_FULLSCREEN'. " Write here your gui status' name .
endform.
In call function reuse_alv_grid_display set i_callback_pf_status_set parameter as 'ALV_MENU'.

Prompt for Customizing request when saving Sales Employee (VPE1)

Hi,
When we try to create Sales Personnel through SD Menu path (VPE1), on saving the system prompts for customizing request. Since this transaction is a master data and we dont transport this data to our production system. Suggest me a way to avoid this transport request while creating Sales Personnel.
We are currently using version 3.1i and upgrading to ECC6.0. In 3.1i we use transaction PAL1 to create Sales Personnel However it will not prompt for Customizing request
Also checked the SAP Note Note 854390 - FAQ: Use of the sales representative in SD without HR
Help me on how to turn off this customizing request. Basis and Security team could not able to turn this off.
Regards,
Pradeep Maddi

hello, friend.
you have 2 choices:
1. create a transport request, save the data but do not release it for transport.
2. when the dialog asks you for transport request, just close this. the system will give you a message about links. just ignore it.
hope this helped. reward if so.
regards.

Change "Create a request" button in SMPortal (SSP) to point to custom Request Offering (not Generic Incident Request)

Hello MSSCSM community,
is it possible to change the request offering mapping of the "Create a request" button (Image1)? By default it points to "Generic Incident Request" request offering. But this is related to a sealed MP and cannot be edited. So i cannot
change name, image, user prompts etc. I created a new custom request offering "Incident request" and disabled "Generic Incident Request". But now the "Create a request" button throws an error (Image2) because Generic
Incident Request is not available anymore. How to map the button to a custom request offering?
Thanks an regards
Vesp

Thanks a lot for your replies. The blog entry is very interesting for having a diffrent "Request offering" mapped to the button instead of standard "Genereic Incident Request (EN)". But i now figured out a very easy solution for me.. i unpublished and disabled "Genereic
Incident Request (EN)" and then system takes the sealed "Genereic Incident Request" (without (EN)) that cannot be edited. I simply reenabled and published "Genereic Incident Request (EN)" and now i can modify this completely and its mapped to the button
by default. I think system always uses sealed "Genereic Incident Request" as fallback. Only constraint is that i cannot change the MP and Template in Request Offering "Genereic Incident Request (EN)". But template can be edited also.. so its fine for
me. Sorry for this kind of questions, i am new to the MSSCSM topic.
Maybe this will get more flexible in future releases of scsm.
Thanks
Vesp

Customizing requests

hi all sd gurus
plz send me some information about the transport requests ,and how do we post when do we release?who releases etc,in realtime work..
i know se09,but what dowe do in that tcode.
id- [email protected]
thank u all
vivek

Dear Vivek,
You would release the transport using Transction SE09/SE10/SE01. You would release the request in the current server so that it can be imported in QA/PROD etc. Releasing of the requests does not automatically take them in to QA/PROD. You would have to import them.
Transport Layers and Transport Routes are defined based on your system landscape.
BASIS people would import them using transaction STMS in to QA/PROD. Only released requests can be imported.
Transport Layers and Transport Routes:
http://help.sap.com/saphelp_nw04/helpdata/en/57/38ddff4eb711d182bf0000e829fbfe/frameset.htm
All development projects developed in the same SAP System and transported on the same transport routes are grouped together to form a transport layer.
Before you start the first development project, you create a transport layer in the TMS transport route editor. This transport layer is assigned to the development system as its standard transport layer. Objects delivered by SAP belong to the transport layer "SAP". Other transport layers are generally only needed when new development systems are included in the system group.
After you have set up the transport layer you set up the transport routes. There are two types of transport routes. First you set up consolidation routes, and then you set up delivery routes:
Consolidation routes
To make your changes transportable, set up a consolidation route for each transport layer. Specify your development system as the starting point (source) of these consolidation routes. Specify the quality assurance system as the transport target (in a two-system landscape, specify the production system as the transport target).
Any modified objects that have a consolidation route set up for their transport layer are included in transportable change requests. After the request has been released the objects can be imported into the consolidation system.
If you make changes to objects which have no consolidation route defined for their transport layer, then the changes are made automatically in local change requests (or in Customizing requests without a transport target). You cannot transport them into other SAP Systems.
You can set up one consolidation route only for each SAP System and transport layer.
When you define consolidation routes, note the additional functions available when you use Extended Transport Control.
Delivery routes
After you have imported your development work into the quality assurance system, you then want to transport it into your production system. You may even want to transport it into several SAP Systems (for example, additional training systems). To do this, you have to set up delivery routes.
Delivery routes have a source system and a target system.
When you set up a delivery route, you are making sure that all change requests that are imported into the routes source system are automatically flagged for import into the routes target system.
You can set up several delivery routes with the same source system and different target systems (parallel forwarding). You can also set up delivery routes in sequence (multilevel forwarding).
CTS transport control makes sure that all requests from the development system are flagged for import into all other SAP Systems in the same order in which they were exported. This is important, since different requests can contain the same Repository object or the same Customizing setting at different development levels, and you must avoid overwriting a more recent version with an older version.
Hope this will help.
Regards,
Naveen.

Difference between work bench request and customizing request

in abap point of view please give me the difference between work bench request and customizing request

In simple terms -
Work bench Request is used by ABAPer.(Creatation of Programs, TCodes or ABAP Dictionary Objects)
Customizing Request is used by Functional Consultants. (Used to configure the system as per clients Business requirements).
The Change Request is that request when you do some thing new in customizing or configuration in the system. The system will automatically pop with the change request pop box , when you can give request name as defined by the system or can give your own request name with heading of what changes you have made while customization. The system will generate a request number and you save it. (e.g.:- VEDK-2785467) VEDK- means the Clients System name then followed by the system generated request number.
Now when you want to release the request you have to use the T-code SE10 where you can see the requests under the heading modifiable or released. Go to the modifiable option. Each request will have again an internal request number. First you have to release the internal request and then release the external request number. This will in turn released by the basis guys thru the T-code SM64 in a group when all the requests are pooled from different users.
The task which you have mentioned in your question is nothing but the what task you have performed while customizing the client system and the heading name which have given it for that task and generated a request for that task.
Change Request Management ...
http://help.sap.com/saphelp_nw04/helpdata/en/0c/5b2160f6fa4b83a3674a210b1cdeb0/content.htm
Creating Change Request Management
http://help.sap.com/saphelp_nw04/helpdata/en/42/157408dd674a9cbc099f634e9bd069/content.htm
Change Request
http://help.sap.com/erp2005_ehp_02/helpdata/en/e5/e5bc42348a43fba6f1b390fc8c4b36/frameset.htm
Customizing Request:- which will be used when any customization changes are doing.
Example:- In your standard Tcode always you cannot find all the fields or options, if you want to enable/disable some fields, in this case it will be treated as Customizing request, any customization will comes under this.
Work Bench Request:- for new developments like new reports, BDC....etc, then Work Bench Request will be used.
Reward if useful.

Difference between workbench and customizing request?

Hello
Can somebody tell me the differance between workbench and customizing requests? Should they be transported in differant ways?
Thanks

Hello ,
Changes to Customizing settings are recorded in Customizing requests.When you release the requests, the current status of the recorded settings is exported, and can then be imported into the consolidation system and, if necessary, into subsequent delivery systems.
The client settings determine whetherchanges to the Customizing settings are possible the changes are recorded
When you create Customizing requests, the transport target is automatically assigned the standard transport layer by the R/3 System.
Work Bench Requests
Workbench requests record changes made to ABAP Workbench objects.There are local and transportable Workbench requests. (Local Workbench requests have the target system <space>.)The package of the object and the transport route settings in the Transport Management System determine whether changes are recorded in a local or a transportable Workbench request
Message was edited by:
Karthik Egamparam Venkataraman

Issue regarding Customizing Requests !!!

Hi ,
From Development Server I want to Transport the Customizing Request Ids to the Quality Server...
Please Somebody explain me the steps involved??
Can we transfer back the Request Ids from the Quality to the development box???
thanks
hr user

Hi
We are using client 130 for development, 150 for quality, 200 for Production.
In your 130 client:
1. Goto SE10 T code click on Modifibale check box and say display it will give the list of Tr. Req., Select the request you want to transport first of all click on internal request and release it by clicking on the Truck icon once sub request is done then do the parent requeest.(whatever is release it will show the right sign).
In your 150 client:
1. Goto STMS tcode click on the truck icon, it will show the list double click on the quality server. List will appear first refresh the list and go to the last entry which must be yours, there must be a green icon in front of your request, place the cursor on your request and click on the same icon present on the above bar (near refresh button) pop up will come say yes, now from the two trucks select the second truck (Import Request (Ctr+F11)). Pop up will come give the target client as your qa client i.e. 150. and save.
2. Refresh the page uptil a triangle in front of the query does not turns green.
Award points if useful.
Regards,
Bhupesh Wankar

Releasing Customizing Request

Similar Messages

Maybe you are looking for