 |
|
|||||||||||||
|
MIT SAP Transport Request Process FAQsProduction Transport RequestWhat is the Transport
Request Process? Production Transport Request What is the Transport
Request Process?
|
|
What is the default transport path?
SF3 
SF2 used for OSS Notes.
SF2
SF3 and SF5 used for configuration, customizing, and development
changes.
SF5
PS1, SF6, and SF7 used for fully tested and approved changes.
How do I request a transport from Development (SF2) to Quality Assurance (SF5)?
The developer with SF2 transport privileges completes ZUTTREQ in the development environment by entering the transport numbers, the required request information, and executing the utility that sends e-mail to the Information Systems R3 Change Management team, R3-chmgt@mit.edu.
If the developer does not have SF2 transport privileges, a person from the team with SF2 transport privileges should complete ZUTTREQ.
Alternatively, the developer can complete ZUTTREQ and send it to a person with SF2 transport privileges for review and approval. The approver should be someone closely associated with the project or functionality affected by the changes in the request. This person reviews the request for completeness and e-mails the request to R3-chmgt@mit.edu with a cc: to the developer and other interested parties.
How do I request a transport from Quality Assurance (SF5) to Production (PS1)?
After testing is completed in the Quality Assurance environment, the Business Process Owner has the opportunity to update their copy of the ZUTTREQ e-mail with the test results, their approval comment, and then forwards the request to the Change Coordinators, fss-chg@mit.edu. This indicates the change is ready for production implementation and is approved by the Business Process Owner.
What information should be communicated to fellow developers regarding validation rules or configuration changes?
Whenever a proposed change affects configuration, alteration of a field on a transaction screen, or changing the status of a field, inform the developers via a message to mit-abap@mit.edu to avoid problems where one change unexpectedly affects another business area or SAP module.
If possible, explain the circumstances in which the validation or substitution rule is invoked, what transpired prior to the rule change, and the expected effect of the rule change. Also, inform developers of the transactions, screens, or programs that are affected by the change.
When is a Technical Program Review by the ABAP Review Team necessary?
A Technical Program Review is required when the transport involves any of the following new:
- report programs
- online programs
- includes (regardless if main program is old or new)
- function modules
- form routine pools
To arrange a review, send e-mail to ABAP-REV@mitvma.mit.edu containing the program name and a brief description. It is recommended that reviews be requested when transporting the program from the development environment to the test environment. Adherence to the development standards and changes that affect program performance must be addressed before submitting a ZUTTREQ for production implementation.
When using ZUTTREQ to generate the transport request for the Quality Assurance environment and new programs are within the transport, a prompt automatically displays asking if mail should be sent to ABAP-REV. When you select yes, ABAP-REV@mitvma.mit.edu is added to the cc:list. The team replies to the email with their review comments and ABAP programming suggestions.
When is a transport considered critical?
A transport is considered critical when it contains a resolution for any of the following business issues:
- The application processing has halted.
- The calculation or formula for a business process is affected.
- SAP OSS Notes critical to system processing are applied.
A transport prioritized as critical can be requested at any time for production implementation. Whether the transport can be processed during the day or after business hours depends on the effect of the changes. These requests require the developer's availability in case R3-Admin needs clarification or has difficulty with importing the transports or with getting the Business Process Owner's approval.
A request that does not meet any of the above criteria will be considered normal priority, and processed accordingly.
When is the submission deadline for a transport request?
Normal transport requests from the Quality Assurance (SF5) to the Production (PS1) environment must be submitted to the Change Coordinators by 3:00 pm Thursday afternoon.
Critical requests can be made at anytime, depending on the effect to the Production environment. The Change Coordinators, fss-chg@mit.edu, should be notified as soon as possible whenever a critical request is in progress.
When are transports processed?
Transports to the Quality Assurance (SF5) environment are processed daily, and transports to Production (PS1) environment are processed between 6:00 pm Thursday evening and 9:00 am Friday morning. Transports to the Training (SF6 & SF7) environments are processed after being imported into Production.
What happens when the scheduled transport day falls on a holiday or end-of-month processing?
If the scheduled transport day (Thursday) falls
on a holiday, the production transport process occurs on the preceding
day.
If the scheduled transport day is the last business day of the month,
the production transport process occurs on the preceding day. If
the transport request is critical for end-of-month processing, the
transport can be imported that evening with proper notification.
For more information regarding the MIT SAP R/3 Transport Request Process, please contact Financial Systems Services, Quality Assurance, fss-qa@mit.edu.
|
|||||
