1 / 21

Software Logistics

Software Logistics. Client 200. Client 300. User Master data. User Master data. Application data. Application data. Customizing data. Customizing data. Cross-Client (Client-independent) Customizing. SAP Repository Modifications Enhancements Development.

channing-marcel
Télécharger la présentation

Software Logistics

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Software Logistics

  2. Client 200 Client 300 User Master data User Master data Application data Application data Customizing data Customizing data Cross-Client (Client-independent) Customizing SAP Repository Modifications Enhancements Development Data and Customizing

  3. Application Transaction data Master data Customizing data Client Data User Master data

  4. Client 200 Client 300 System Clients and Systems Clients and Systems separate and protect data

  5. Client User Master data Application data Customizing data Cross-Client Customizing SAP Repository Adaptation Customizing Development Enhancements Modification

  6. Customizing

  7. Development • Add functionality using ABAP/4 programming • Frequently report generation • Requires a Developer Key • Can add objects (tables) • Begin with Y or Z • Append Structures • Add fields to any table

  8. Include Enhancements • User Exits • Defined places in ABAP code where SAP expects users may want to perform additional processing

  9. Modifications • Not recommended • Can create problems with upgrades • Requires Change Registration Key • Changing a repository object delivered by SAP is flagged as a repair • Source of future user exits • SAP, while not recommending modifications, does provide tools to minimize the impact

  10. QAS System Production System Development System 000 000 000 066 066 066 DB DB DB System Landscape Cust. Integ. Testing 100 100 Unit Test 200 Sandbox Training 300 300 Backup Backup Production 400 400 400

  11. Transport Directory Change Transport System DEV QAS PRD CUST TEST SAND QTST TRNG QTST

  12. Change Requests • Customizing changes are transported as change requests, which are key to managing system changes • Change request can be created automatically during customization

  13. Controlling Change Requests • Single biggest mistake in managing customizing and development changes is the lack of clearly defined and enforced transport processes and procedures. Good transport processes and procedures: • Reduce the exposure of the production system to problems caused by premature or incorrect transports • Minimize the amount of manual intervention required • Reduce e-mail communications and paperwork required from the customizing team

  14. DEV QAS PRD CUST TEST SAND QTST TRNG QTST Transport Directory Controlling Change Requests • QA Approval Process

  15. DEV QAS PRD Controlling Change Requests • QA Approval Process • With the QA Approval process configured, change requests placed in the transport directory for the PRD system are flagged as inactive, and can only be imported when all approval steps are processed. • QA Approval can only be performed by designated users with appropriate authorizations.

  16. DEV QAS PRD Controlling Change Requests • Import Queues • When a change request is released, it is placed on the import queue of the target system. There are four methods of controlling the import of change requests into the target system: • Single Imports • Mass Imports • Import by Project • Transport Workflow

  17. DEV QAS PRD Controlling Change Requests • Single Imports • Change requests can be selected individually to be imported into the target system • This is not a recommended approach • Increased administration • Selected transport requests may not constitute a complete configuration modification • Requests must imported in correct sequence

  18. DEV QAS PRD Controlling Change Requests • Mass Imports • All change requests in the import queue are imported into the target system • Requests are imported in the order they were exported • A transport schedule can be established to help maintain a consistent changes from developers • Example • Hourly imports into QAS • Weekly imports into PRD • Reduces administrator workload

  19. DEV QAS PRD Controlling Change Requests • Mass Imports • Controlling Change Requests is primarily a behavior issue. Developers can get in the habit of releasing change requests before a completely functioning change has been developed. • Mass Imports functions “force” developers to make sure their change requests are ready to be released before they are released. • Like making sure that your chess move is correct before removing your hand from the chess piece

  20. DEV QAS PRD Controlling Change Requests • Import by Project • Can filter to import only changes related to a configuration project

  21. Key Points in Landscape Management • No application data goes in customizing client in DEV system • Like Accounting, you don’t undo or delete transport requests, you create correcting requests—means that you have to manage the order of importing change requests carefully

More Related