Info
- Utilizzare la checkbox di selezione a fianco di ciascun documento per attivare le funzionalità di stampa, invio email, download nei formati disponibili del (i) record.
ABAP to the future / / Paul Hardy
| ABAP to the future / / Paul Hardy |
| Autore | Hardy Paul <1968-> |
| Pubbl/distr/stampa | Rheinwerk Publishing |
| Disciplina | 005.1/17 |
| Soggetto topico |
ABAP/4 (Computer program language)
Object-oriented programming languages SAP ERP |
| ISBN | 1-4932-1411-X |
| Formato | Materiale a stampa  |
| Livello bibliografico | Monografia |
| Lingua di pubblicazione | eng |
| Nota di contenuto | ABAP in eclipse -- New language features in ABAP 7.4/7.5 -- ABAP unit and test-driven development -- ABAP test cockpit -- Exception classes and design by contract -- BRFplus -- ABAP2XLSX. |
| Record Nr. | UNINA-9910154789903321 |
Hardy Paul <1968->
|
||
| Rheinwerk Publishing | ||
| Materiale a stampa | ||
| Lo trovi qui: Univ. Federico II | ||
| ||
Complete ABAP / / Kiran Bandari
| Complete ABAP / / Kiran Bandari |
| Autore | Bandari Kiran |
| Pubbl/distr/stampa | SAP PRESS |
| Disciplina | 005.1/17 |
| Soggetto topico | ABAP/4 (Computer program language) |
| ISBN | 1-4932-1273-7 |
| Formato | Materiale a stampa |
| Livello bibliografico | Monografia |
| Lingua di pubblicazione | eng |
| Nota di contenuto | Introduction to ERP and SAP -- Architecture of an SAP system -- Introduction to the ABAP environment -- ABAP programming concepts -- Structures and internal tables -- User interaction -- Modularization techniques. |
| Record Nr. | UNINA-9910150176403321 |
|
Bandari Kiran
|
||
| SAP PRESS | ||
| Materiale a stampa | ||
| Lo trovi qui: Univ. Federico II | ||
| ||
Improving the quality of ABAP code : striving for perfection / / Paul David Hardy
| Improving the quality of ABAP code : striving for perfection / / Paul David Hardy |
| Autore | Hardy Paul David |
| Pubbl/distr/stampa | [Place of publication not identified] : , : Apress, , [2021] |
| Descrizione fisica | 1 online resource (526 pages) |
| Disciplina | 005.133 |
| Soggetto topico | ABAP/4 (Computer program language) |
| ISBN | 1-4842-6711-7 |
| Formato | Materiale a stampa |
| Livello bibliografico | Monografia |
| Lingua di pubblicazione | eng |
| Nota di contenuto |
Intro -- Table of Contents -- About the Author -- About the Technical Reviewer -- Acknowledgments -- Introduction -- Chapter 1: Why Object-Oriented Programming Is a Must for Code Quality -- Why OO Has Never Taken Off in ABAP World -- OO Benefits: The Theory -- Describing OO Programs: UML -- Describing OO Programs: BON -- Seamlessness/Reversibility -- Seamlessness via an Automated Tool -- Seamlessness via Naming Conventions -- Design by Contract -- Design by Unit Tests -- Designing a Worldwide OO Program -- What Is the Existing System State? -- Why Is the Existing System State Not Portable? -- What Can Be Done About Fixing That Problem? -- Breaking Dependencies in General -- Breaking Dependencies via Packages -- Breaking Dependencies via Interfaces -- What Is an Interface in OO Terms? -- How SAP Uses Interfaces to Manage User Exits -- Not Breaking the System -- My Journey to OO Happiness -- OO Happiness: The Theory -- The Clean Coder -- Clean Code -- Head-First Design Patterns -- More on Design Patterns -- OO Happiness: The Reality -- Writing an Interactive Executable Report in OO -- Writing a DYNPRO Program in OO -- Experiment -- Rewriting a Huge, Business-Critical Program in OO -- Slowly Transforming a Huge, Business-Critical Program to OO -- OO Benefits: The Reality -- Soft Benefits -- Design Thinking -- Ease of Maintenance -- No One Goes Back -- Hard Benefits -- Avoidance of Syntax Errors -- Parameter Handling -- IMPORTING -- EXPORTING -- TABLES -- RETURNING -- OPTIONAL -- NAMES -- TYPES -- FORMULAS -- Reuse -- Making Code Testable -- Conclusion -- Recommended Reading -- Articles -- Books -- Chapter 2: Why Test-Driven Development Is a Must for Code Quality -- TDD Theory -- Fragile Code -- Legacy Code -- Automated Regression Tests -- Dependencies and How to Break Them -- The TDD Development Cycle: RED/GREEN/BLUE -- My Journey to TDD Happiness.
Testing After the Event -- Testing Before the Event -- TDD Workflow in Eclipse -- Creating Test Doubles -- Creating a New Test Method -- Coding the Test Method -- Coding the THEN Method -- Coding the GIVEN Method -- Coding the WHEN Method -- Writing the Production Code -- The BLUE Phase -- Does This Actually Give You a Benefit? -- From a Gut Feeling . . . -- . . . to a Concrete Example -- Some Unit Tests Might Seem Pointless . . . -- It's Too Short to Test -- It's Too Simple to Test -- . . . but They Are Not! -- Message in a Model -- You Can't Get There from Here -- Simpler but Wrong -- Why TDD Has Never Taken Off -- I Already Have an Automated Testing Framework -- My Program Is Too Complicated for TDD -- My Program Is Too Simple for TDD -- TDD Is Far Too Expensive -- TDD Reduces Development Costs -- TDD Reduces the Cost of Fixing Bugs -- TDD Reduces the Financial Risk of Failure -- Conclusion -- Recommended Reading -- Chapter 3: Clarity: The First Pillar of Code Quality -- Refactoring: Automated and Manual Checks -- Automated Checks -- Syntax Check -- Extended Program Check -- Code Inspector -- ABAP Open Checks -- Code Pal -- Remote ATC Checks -- Continuous Integration -- Manual Checks -- Clean ABAP -- ABAP Gore -- Creating a Personalized Checklist -- Code Complexity -- Huge Routines -- Confusing Code -- Double Negatives -- Text Symbols -- Pointless Variables -- Contradictory Instructions -- END-OF-SELECTION -- DATA Declarations -- Unrelated Tasks -- Not Being Able to Locate a Routine -- Duplicate Code -- Global Variables -- Why Are Global Variables Bad? -- What Can You Do About Global Variables? -- Global Variables Versus Member Variables -- Naming -- Method/Routine Naming -- Misleading Names -- Totally Incorrect Names -- Sloppy Naming -- Parameter Naming -- Named Parameters -- Functional Methods -- Variable Naming -- Hungarian Notation. Prefixes in an OO Context -- Random Naming Conventions -- Misleading Names -- Very Old Programs -- Inline Declarations -- Self-Documenting -- German Acronyms -- Magic Numbers -- Hard Coding -- Constants -- Redundant Constants -- Meaningless Constants -- How Not to Use Constants -- ABAP Data Dictionary Object Naming -- Tables -- Transaction Codes -- Structures -- Indexes -- Program Names -- CDS Views -- How Correct Naming Enables Reuse -- Comments -- Why, Not How -- Quotation Marks Versus Asterisks -- Meaningless Comments -- Incorrect Comments -- Reference Numbers in Comments -- Comments Going for a Walk -- Commented-Out Code -- It Makes the Program Harder to Follow -- It Causes Short Dumps -- It Doesn't Always Work -- It Should Be Deleted -- Documentation -- Conclusion -- Recommended Reading -- Chapter 4: Stability: The Second Pillar of Code Quality -- Principle of Least Astonishment -- Enhancement Category -- Material Substitution -- Data Declarations in Modules -- Hashed Tables -- Incorrectly Typed RETURNING Parameter -- Programming by Accident -- Wrong Code That Works -- Incorrect Behavior Being Viewed as Correct -- Archaic ABAP Statements -- Strange Data Declarations -- Implicit Work Area -- What Do You Do? -- Don't Repeat Yourself -- Time/Difficulty -- Before the Event -- After the Event -- Riskiness -- Surgeon Example -- Drill-Down Example -- Text Names Example -- Payer Example -- Avoiding Repetition in OO Programming -- Other Common Causes of Instability -- Global Variables -- Cannon Example -- Half-Dog Half-Cat Example -- Function Modules -- Cross-Program Calls -- Table-Based Work Areas -- Parameters -- Importing Parameters -- Exporting Parameters -- Fully Typed Parameters -- Big Trouble with Big Signatures -- Memory Problems -- Dealing with Instability: Using Code -- Problems That Virtually Always Happen -- Fuzzy Searches -- Spreadsheets. Problems That Are Likely to Happen -- SY-SUBRC -- BAPIs -- BDCs -- Field Symbols -- Problems That Really Shouldn't Happen -- Self-Repair: Example 1 -- Self-Repair: Example 2 -- Problems That Should Never, Ever Happen -- Spotting the Impossible -- Dealing with the Impossible -- Dealing with Instability: Using Humans -- What's Wrong #1 -- What's Wrong #2 -- Conclusion -- Recommended Reading -- Chapter 5: Performance: The Third Pillar of Code Quality -- CPO Concept -- Daily Dumps -- Annual In-House CPO -- Static Checks -- Geometric Loops -- Secondary Indexes for Internal Tables -- Runtime Checks -- ST05 in General -- Identical SELECTS -- How to Spot the Problem -- Strategies to Deal with the Problem -- Real-Life Example -- Stuttering -- Asking Stupid Questions -- Reading More Data Than Needed -- Selecting More Columns Than You Need -- Selecting More Rows Than You Need -- The Behavior Never Made Sense -- The Behavior No Longer Makes Sense -- The Behavior Makes Sense -- Existence Checks -- Multiple Reads on the Same Table -- Contract Example -- Partner Function Example -- Shipment Cost Example -- Using FOR ALL ENTRIES -- Indexes -- Indexes: Always Using One -- Indexes: Missing the First Field -- Indexes: SKIP SCAN -- Nested SELECTs -- "Bad" Joins on Database Tables -- Postmortem Checks -- Standard SAP Transactions for Troubleshooting Performance Problems -- SAT -- ST04 -- SRTCM -- Technical Attributes of Database Tables -- Indexes -- Pointless Index -- Terrible Index -- Really Good Index -- Buffering -- Possible Buffering Settings -- Example of How Buffering Can Help -- Common Misconception About Generic Buffering -- How to Decide Which Z Tables to Buffer -- Postmortem Tricks -- Batch Jobs -- Deadlocks -- Sneaky Tricks -- Database Reads in a Loop -- Using Standard SAP "Buffering" Modules -- When to Use Them -- KNA1_SINGLE_READER -- Prefilling Buffers. Constants -- INTO CORRESPONDING -- DDIC Information -- Using Standard SAP Functions Incorrectly -- Conclusion -- Chapter 6: User Friendliness: Ensuring UI Quality -- General Philosophy -- Difference Between UI and UX -- Don't Make Me Think -- Waterfall Projects -- Consistency -- Standards -- Applying Industry Standards -- Non-Standard Icon Appearance -- Non-Standard Icon Usage -- Inconsistency -- Inconsistency in F4 Helps -- Inconsistency in Pop-Ups -- Inconsistency in Master Data Transactions -- Ease of Use -- Laying Traps for the User -- Hiding Icons for No Reason -- Hiding Fields for No Reason -- Slightly Hidden Field -- Totally Hidden Field -- Incorrect Use of Check Boxes -- Confusing the User -- Giving Incorrect Options -- Giving No Options at All -- Accessibility -- Explaining Things to the User -- Avoiding Abbreviations -- Custom Data Elements -- Custom F1 Help -- Custom Domains -- Error Prevention -- Inviting Errors -- Self-Destruct Button -- Stopping Dumps Before They Begin -- Self-Service -- Logging -- Linking Errors to Training Material -- Sneaky Trick: ALV Filter Not Working -- Error Handling -- Shouting at the User -- Preventing the User from Fixing the Problem -- Making the User Reenter Data -- Making It Impossible to Fix the Problem -- Enabling the User to Fix the Problem -- Mandatory Fields -- Taking the User to the Source of the Problem -- Example: IDoc Application Log -- Documentation -- Documentation Guidelines -- Documentation Terminology -- Documentation for Dialog Transactions -- Documentation for Developers -- Conclusion -- Recommended Reading -- Chapter 7: User Exits: Defusing a Potential Time Bomb -- User Exits in On-Premises SAP Systems -- VOFM Routines -- Repairs -- FORM-Based User Exits -- CMOD User Exits -- BAdi User Exits -- The Enhancement Framework -- User Exits in Your Own Z Programs -- User Exits in Cloud SAP Systems. UI Extensibility. |
| Record Nr. | UNINA-9910484705403321 |
|
Hardy Paul David
|
||
| [Place of publication not identified] : , : Apress, , [2021] | ||
| Materiale a stampa | ||
| Lo trovi qui: Univ. Federico II | ||
| ||
Mastering SAP ABAP : a complete guide to developing fast, durable, and maintainable ABAP programs in SAP / / Pawel Grzeskowiak, Wojciech Ciesielski, Wojciech Cwik
| Mastering SAP ABAP : a complete guide to developing fast, durable, and maintainable ABAP programs in SAP / / Pawel Grzeskowiak, Wojciech Ciesielski, Wojciech Cwik |
| Autore | Grzeskowiak Pawel |
| Pubbl/distr/stampa | Birmingham, England ; ; Mumbai : , : Packt, , [2019] |
| Descrizione fisica | 1 online resource (539 pages) |
| Disciplina | 005.133 |
| Soggetto topico | ABAP/4 (Computer program language) |
| Soggetto genere / forma | Electronic books. |
| ISBN | 1-78712-949-7 |
| Formato | Materiale a stampa |
| Livello bibliografico | Monografia |
| Lingua di pubblicazione | eng |
| Record Nr. | UNINA-9910493665103321 |
|
Grzeskowiak Pawel
|
||
| Birmingham, England ; ; Mumbai : , : Packt, , [2019] | ||
| Materiale a stampa | ||
| Lo trovi qui: Univ. Federico II | ||
| ||
Mastering SAP ABAP : a complete guide to developing fast, durable, and maintainable ABAP programs in SAP / / Pawel Grzeskowiak, Wojciech Ciesielski, Wojciech Cwik
| Mastering SAP ABAP : a complete guide to developing fast, durable, and maintainable ABAP programs in SAP / / Pawel Grzeskowiak, Wojciech Ciesielski, Wojciech Cwik |
| Autore | Grzeskowiak Pawel |
| Pubbl/distr/stampa | Birmingham, England ; ; Mumbai : , : Packt, , [2019] |
| Descrizione fisica | 1 online resource (539 pages) |
| Disciplina | 005.133 |
| Soggetto topico | ABAP/4 (Computer program language) |
| ISBN | 1-78712-949-7 |
| Formato | Materiale a stampa |
| Livello bibliografico | Monografia |
| Lingua di pubblicazione | eng |
| Record Nr. | UNINA-9910793681203321 |
|
Grzeskowiak Pawel
|
||
| Birmingham, England ; ; Mumbai : , : Packt, , [2019] | ||
| Materiale a stampa | ||
| Lo trovi qui: Univ. Federico II | ||
| ||
Mastering SAP ABAP : a complete guide to developing fast, durable, and maintainable ABAP programs in SAP / / Pawel Grzeskowiak, Wojciech Ciesielski, Wojciech Cwik
| Mastering SAP ABAP : a complete guide to developing fast, durable, and maintainable ABAP programs in SAP / / Pawel Grzeskowiak, Wojciech Ciesielski, Wojciech Cwik |
| Autore | Grzeskowiak Pawel |
| Pubbl/distr/stampa | Birmingham, England ; ; Mumbai : , : Packt, , [2019] |
| Descrizione fisica | 1 online resource (539 pages) |
| Disciplina | 005.133 |
| Soggetto topico | ABAP/4 (Computer program language) |
| ISBN | 1-78712-949-7 |
| Formato | Materiale a stampa |
| Livello bibliografico | Monografia |
| Lingua di pubblicazione | eng |
| Record Nr. | UNINA-9910808848603321 |
|
Grzeskowiak Pawel
|
||
| Birmingham, England ; ; Mumbai : , : Packt, , [2019] | ||
| Materiale a stampa | ||
| Lo trovi qui: Univ. Federico II | ||
| ||
Programación en ABAP/4 para SAP R/3 / / Raquel Hijón Neira
| Programación en ABAP/4 para SAP R/3 / / Raquel Hijón Neira |
| Autore | Hijón Neira Raquel |
| Pubbl/distr/stampa | Madrid, : Universidad Pontificia Comillas, 2005 |
| Descrizione fisica | 1 online resource (311 p.) |
| Disciplina | 650/.0285/53769 |
| Collana | Ingeniería |
| Soggetto topico |
ABAP/4 (Lenguaje de programación)
ABAP/4 (Computer program language) |
| ISBN |
84-8468-183-1
84-8468-324-9 |
| Formato | Materiale a stampa |
| Livello bibliografico | Monografia |
| Lingua di pubblicazione | spa |
| Nota di contenuto |
PROGRAMACIÓN EN ABA P/4 PARA R/3; PÁGINA LEGAL; MENÚ PRINCIPAL; MENÚ SISTEMA; ABAP/4 DEVELOPMENT WORKBENCH; DICCIONARIO DE DATOS; COMO CREAR UNA TABLA; CREAR, MODIFICAR O VISUALIZAR UN DOMINIO; CREAR, MODIFICAR O VISUALIZAR UNA TABLA; MANDANTE; TABLA DE VERIFICACIÓN; ÍNDICES; CLAVES FORÁNEAS; TABLA SIN ELEMENTOS DE DATOS NI DOMINIOS; OTROS; POR ULTIMO; VISTAS; COMO CREAR ÍNDICES EN UNA TABLA; COMO HACER CLAVES FORÁNEAS Y TABLAS DE VERIFICACIÓN; TabVerif sin '*'; Tablas más usadas en la tabla de verificación; VER EL CONTENIDO, AÑADIR O MODIFICAR DATOS DE UNA TABLA; TABLAS DEL SISTEMA; SCREEN
SYSTOBJETOS MATCHCODE; CREAR UN MATCHCODE; OBJETOS DE BLOQUEO; DATA BROWSER; INTERFASE DE USUARIO; BASES DE DATOS RELACIONALES; VER LA ESTRUCTURA DE UNA BDD RELACIONAL; EDITOR ABAP/4; ATRIBUTOS; VARIANTES; DOCUMENTACIÓN; ELEMENTOS DE TEXTO; SÍMBOLOS DE TEXTO; TÍTULOS/CABECERAS; TEXTO DE SELECCIÓN; TEXTO FUENTE; MENÚS DEL TEXTO FUENTE; BOTONES DEL TEXTO FUENTE; Modelo; Copiar; Borrar; Insertar un trozo de programa en otro; COMANDOS GENERALES; COMANDOS DE LINEA; Comandos de una sola línea; Comandos de bloque de línea; Mover; Insertar un trozo de programa en otro; COMANDOS GENERALES MENÚS DEL EDITOR ABAP/4TRANSPORTE; COMO VER NUESTROS OBJETOS TRANSPORTADOS; BUSCAR OBJETOS; BIBLIOTECAS DE FUNCIÓN; PARÁMETROS DE IMPORT/EXPORT; PARÁMETROS TABLA/EXCEPCIONES; LENGUAJE ABAP/4; ESTRUCTURACIÓN; REPORT; MODUL -POOL; DECLARACIÓN DE TABLAS DICCIONARIO; DECLARACIÓN DE TABLAS INTERNAS; OPCIÓN 1; OPCIÓN 2; CÓMO FUNCIONAN; DECLARACIÓN DE VARIABLES; ASIGNAR LOS ATRIBUTOS DEL CAMPO DE UNA TABLA DE DICCIONARIO CON UNA VARIABLE; Declarar una variable del tipo que queramos; Una variable con la estructura de otra; FIELD-GROUPS; FIELD_GROUPS:; INSTRUCCIONES DE ENTRADAS DE DATOS; INSTRUCCIONES SET PARAMETERTEST; PARAMETERS; RANGES; SELECT-OPTIONS; EVENTOS; INITIALIZATION; START-OF-SELECTION; END-OF-SELECTION; TOP-OF-PAGE; END-OF-PAGE; AT LINE-SELECTION; AT PFn; AT USER-COMMAND; AT SELECTION-SCREEN; LLAMADA A OTROS PROGRAMAS; SUBRUTINAS O PROGRAMAS INTERNOS; PROGRAMAS EXTERNOS; FUNCIONES; Ejemplos de funciones; Download; Upload; EXPORTING; IMPORTING; TABLES; CHANGING; EXCEPTIONS; UPLOAD; IMPRESIÓN DESDE UN ABAP; DESPUÉS DE HABERLO EJECUTADO; MIENTRAS SE EJECUTA; Llamando a un report; Ejecutar e imprimir; Imprimir directamente; GRÁFICOS EN SAP; GRÁFICOS EN DOS DIMENSIONES GRÁFICOS EN TRES DIMENSIONESGRÁFICOS EN 2D, 3D Y 4D.; INSTRUCCIONES; INSTRUCCIONES DE CONTROL DE FLUJO; If; Do; While; Case; Check; Instrucciones de ruptura de un control de flujo; Exit; Continue; LECTURA DE TABLAS DE DICCIONARIO; Consejos; LECTURA DE TABLAS INTERNAS; INSTRUCCIONES DE RUPTURA; At first; At new; At end of; At last; Consejos; OPERACIONES CON LAS TABLAS INTERNAS; AÑADIR; MODIFICAR; BORRAR; COLLECT; COMMIT WORK Y ROLLBACK; REFRESH; CLEAR; FREE; INSTRUCCIONES DE ORDENACIÓN; OPERACIÓN CON LAS TABLAS DE DICCIONARIO; AÑADIR; Registro a registro; A través de una tabla interna MODIFICAR |
| Record Nr. | UNINA-9910139738703321 |
|
Hijón Neira Raquel
|
||
| Madrid, : Universidad Pontificia Comillas, 2005 | ||
| Materiale a stampa | ||
| Lo trovi qui: Univ. Federico II | ||
| ||
