Upgrade Creation: Development
System 
Purpose
This process describes the creation of upgrades for mobile clients in the development system.
Process Flow
1. The initial step of upgrading the Mobile Application Repository (MAR) Server is triggered by the person responsible for upgrading machines in the Development system. This upgrade is executed on the MAR Server using the MAR Upgrade tool. The task imports application changes made by SAP. If you have made changes to SAP objects, the update can result in collisions.
2. Development workstations and the repository server (containing the MAR and Transport Services) are upgraded with the latest binaries. This is done by the Framework Upgrade Setup program. When you upgrade the development workstations, additional elements like the Sales Pricing Engine that needs to be sent to the mobile clients as a part of the upgrade is installed.
3. Apply the R/3 support package to the CRM Server, and make necessary changes to the BDoc/Table.
4. Using the Mobile Application Studio (MAS) resolve collisions in the MAR, if any. Furthermore, if you need to make changes to the application, do so now and release the change lists in the CRM Server.
5. Transport the changes (application and BDoc/Table changes) to the Test system in the landscape using the R/3 Change and Transport System tools. This will release and export the change requests.
See also: