Get More Insight into an SAP Customizing Request and See How to Release It for Transport

  • by Patrick Imhen, Business Analyst and Senior SAP MM/SD/PM Functional Consultant, ZOCODE Limited
  • May 18, 2017
Learn some useful tips on how to better organize your customizing requests and how to release a customizing request for transportation from a development server to a quality assurance or production server.
Learning Objectives

Reading this article you will learn how to:

  • Organize your customizing request for easy identification  
  • Assign a customizing request to multiple users
  • Update an already generated transport request
  • Change the description of an already generated customizing request
  • Release a customizing request
  • Display a customizing request change date in the Transport Organizer
  • Merge and reassign a customizing request in the Transport Organizer
Key Concept
SAP provides a customizing request so that changes in standard SAP software customization or settings can be recorded and moved to other target servers by a transport program. The customizing request records user-specific changes (i.e., changes made by the SAP software user) that are usually generated by the customization tasks of SAP functional consultants.

A misappropriation of a customizing request can cause unnecessary issues and wasted time during an SAP implementation or support service. On my first SAP implementation project, although I knew how to create customizing requests, I lacked the know-how to properly manage them. My entire customizing task was generated under a single customizing request. Although part of my work scope was to release my customizing requests for transport from the development system, I initially did not know how to do the release. Now as a senior SAP functional consultant, I have observed that some new SAP professionals experience this same challenge during their first project or support service.

I give you insight on how to better organize customizing requests to avoid mistakes and how to release a customizing request for transport (move the customizing request to other targeted servers).

I provide tips and recommendations with a step-by-step procedure on how to:

  • Organize a customizing request and rename it
  • Update an already generated transport request
  • Carry out quality assurance as a lead consultant on customizing done by new junior functional consultants by having their customizing requests assigned to your user account
  • Release a customizing request for transport in two steps
  • Set the display customizing request change date in the Transport Organizer
  • Merge and reassign a customizing request

How to Organize Your Customizing Request

Organizing your customizing request consists of two steps:

1. Save your customizing task by sets or individually. This step provides easy navigation to locate your customizing requests. For example, you could save all customizing tasks for price IMG activities under one customizing request description named Pricing, or you could be more specific by saving a single IMG activity such as document type under a customizing request named Sales Order.

During my experience at my first SAP implementation, the Basis consultant had issues with easily locating my various customizing tasks because they were all under one customizing request and the consultant had to transport all my customizing tasks any time there was a need for transporting my request.

2. When generating a customizing request, use descriptions that relate to the customizing task. This step makes it easy to identify the customizing request by team members and Basis experts. For instance, you could use Sales Order as a description to generate the customizing request for defining sales document type customizing tasks.

For my example, use the IMG activity Define Sales Document Type. To define a sales document type use transaction code VOV8 or follow IMG menu path Sales and Distribution > Sales > Sales Documents > Sales Document Header > Define Sales Document Types. The screen in Figure 1 shows a newly created Sales Order Type Standard Order (ZS) that I already defined via the Define Sales Document Type IMG Activity to demonstrate how a customizing request should be named (Description).

Figure 1
Overview screen for defining the sales document type

Patrick Imhen

Patrick Imhen is a business analyst and a certified SAP ERP consultant with proficient knowledge, skills, and experience in Materials Management (MM), Sales and Distribution (SD) and Plant Maintenance (PM) gathered from successful SAP implementations projects, support, training, business process analysis, modeling, unit testing, and integration testing. He has profound understanding of the supply chain process across industries and helps organizations cut the cost of operation and improve process optimization. He has more than 10 years’ experience in the business environment and six years’ experience in the SAP domain.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.