Sap Ecc 6.0 Manual New! -
In SAP ECC 6.0, "producing a text" (creating or maintaining text) is handled through several specialized transactions and editors depending on whether you are managing reusable standard texts, application-specific document texts, or developer-focused text elements. 1. Standard Texts (SO10)
Standard texts are reusable text modules that can be included in various documents or SAPscripts. Transaction Code: SO10. Steps to Create: Enter the Text Name (e.g., Z_PURCHASE_TERMS). Select the Text ID (usually ST for Standard Text). Choose the Language (e.g., EN). Click Create. The SAPscript Editor will open. Enter your text and click Save. 2. Text Elements in ABAP Programs (SE38/SE32)
Used to maintain language-independent texts like selection screen labels, headers, and hardcoded symbols within a program.
Transaction Code: SE32 or via SE38 (Environment > Text Elements). Categories: Text Symbols: Defined in code as TEXT-001.
Selection Texts: Descriptions for input parameters on the selection screen. List Headers: Titles for output report columns. 3. Document Texts (Business Objects)
Many business transactions (Sales Orders, Purchase Orders, Customer Master) have dedicated "Texts" tabs for specific notes.
Sales Orders (VA01/VA02): Go to the Header or Item level, select the Texts tab, and choose a text type (e.g., "Form Header") to type directly.
Customizing Texts: Use transaction VOTXN to define how these texts flow (Access Sequences) from master data to documents. 4. Message Maintenance (SE91) sap ecc 6.0 manual
Used for system messages that appear in the status bar or as pop-ups. Transaction Code: SE91.
Steps: Enter a Message Class, choose a number, and type the short text. These are triggered in ABAP using the MESSAGE statement. 5. SAP Interactive Forms by Adobe / Smart Forms
For modern form output, texts are created as nodes within the form's context. Editing Standard Texts - SAP Help Portal
In SAP ECC 6.0, "preparing a story" typically refers to the SAP SuccessFactors Story Reports framework or the process of breaking down business requirements into user stories during an implementation or upgrade project.
While "stories" are more common in newer SAP analytics tools, they are integrated into ECC 6.0 environments during modern reporting migrations or when using SAP Cloud ALM for project management. 1. Preparing Story Reports (Analytics)
If you are using the Story Reports feature (often linked via SuccessFactors or SAP Analytics Cloud integration with ECC), follow these steps to build your narrative:
Access the Query Designer: Start a new story and add your required data tables. In SAP ECC 6
Define Relationships: Link these tables to visualize how data flows across different business components.
Configure Connections: Ensure that your Identity Authentication Service (IAS) and Identity Provisioning Service (IPS) are properly synced between your ECC HCM suite and the analytics cloud. 2. Preparing User Stories (Project Management)
For implementation or technical upgrades (like moving to EHP8), a "story" is a way to document a specific business requirement:
Open the Requirements App: Ensure you have the Project Admin or Lead role in SAP Cloud ALM.
Break Down Requirements: Take a high-level business need and decompose it into manageable user stories and features.
Assign Roles: Each story should be assigned to a specific team (e.g., ABAP for technical tasks or Functional for business process configuration). 3. Key Manual Resources for ECC 6.0
For a standard ECC 6.0 setup, refer to these central guides available on the SAP Help Portal: If you know the code (e.g.
Master Guide: The primary entry point for each solution, listing required components and business scenarios.
Configuration Manuals: Detailed guides for specific modules like Plant Maintenance (PM) or Financial Accounting (FI).
Operations Guide: Essential for running daily production operations at peak performance. ECC 6.0 Manual - SAP Community
2. Types of Manuals for SAP ECC 6.0
Depending on your role, you may need different manuals:
| Manual Type | Primary Audience | Purpose | |-------------|------------------|---------| | End User Manual | Daily business users (e.g., order processors, accountants) | Step-by-step instructions for executing transactions (e.g., create sales order, post invoice) | | Configuration Guide | SAP functional consultants | How to customize the system using the Implementation Guide (IMG) | | ABAP Developer Guide | Technical developers | How to write programs, reports, and enhancements using ABAP Workbench | | Security & Authorization Guide | Security administrators | Managing user roles, profiles, and authorizations | | Basis Administration Manual | System administrators (Basis team) | System monitoring, backup, performance tuning, transport management | | Master Data Management Guide | Data stewards | Creating and maintaining master data (customer, vendor, material, etc.) | | Upgrade Guide | Project teams | Steps to upgrade from older ECC versions or apply support packs |
3.2 The Command Field (Transaction Codes)
The Command Field is the fastest way to navigate.
- If you know the code (e.g.,
VA01for Create Sales Order), type it and press Enter. - Note: Precede codes with
/nto open in the current window (e.g.,/nVA01) or/oto open in a new window (e.g.,/oVA01).
1. The Three Categories of Manuals
When users search for an "SAP Manual," they are usually looking for one of three distinct things. It is vital to distinguish between them to find the right information.
