線上論文資源好去處

台大電子書圖書館-free

http://ebooks.lib.ntu.edu.tw/Home/ListBooks


Google
http://books.google.com.tw/books?hl=zh-TW&source=gbs_hp_logo


Ytowaer- 烹飪電子書、教學影片
http://www.ytower.com.tw/ebook/ebook.asp

SCJP認證線上資源

SCJP認證應試教戰手冊勘誤表
https://sites.google.com/site/ronforwork/Home/correct-1

志凌-SCJP完全擬真試題講解影片
http://www.yesgood.com.tw/contents/scjp6.aspx

SAP如何恢復已刪除的程式

先去TRDIR table查找是否有已經刪除的程式


http://naveenvishal.wordpress.com/2009/08/07/retrieve-deleted-programs/

合併多個pdf檔案

http://foxyutils.com/mergepdf/

合併完後的檔案會順便解密

Compatibility Data type

Compatibility 
Two data types or data objects are compatible when all of their technical attributes (field length, number of decimal places, type) are exactly the same.
Do not confuse the two terms compatible and convertible. When working with data objects, you will often make assignments between data objects that have different technical attributes. In this case, the data types are converted. In order for non-compatible data types to be converted, a
Compatibility applies to fully-specified data types, since all data objects are fully typed at runtime. This compatibility is symmetrical. There is also an asymmetrical compatibility, which is used to test the types of interface parameters in procedures and of field symbols. In this case, generic types are compared with fully-specified data types.
Consequences of definition for the compatibility of data types: conversion rule must exist. Only compatible data objects can be assigned to one another without a conversion being necessary. Elementary Data TypesElementary data types are compatible with other elementary data types if they are identical in type, field length, and the number of decimal places.
Elementary data types are not compatible with references or aggregated types. ReferencesReferences are compatible with other references when their construction rules (type constructor REF TO <class>|<interface>) are the same.
References are not compatible with elementary data types or aggregated types. Aggregated Data TypesAggregated data types are compatible with other aggregated data types if their construction rules are the same.
Aggregated data types are not compatible with elementary data types or references. structuresStructures are compatible with other structures if their constructions are identical and their components are compatible. This means that the way in which field strings are constructed from elementary fields to form the overall structure from sub-structures must be the same and their elementary components must be compatible with each other. If two structures consist of the same sequence of elementary fields, but these fields are combined differently to substructures, the structures are not compatible.
Structures are not compatible with internal tables. Internal tablesInternal tables are compatible with other internal tables if their line types are compatible and all other attributes are also the same for both tables. The compatibility of internal tables does not depend on the number of lines.
Internal tables are not compatible with structures.

Screen Painter Introduction

Screens (dynpros)

• Added by MANSI ASNANI, last edited by Sandra Rossi on May 07, 2010  (view change)
• show comment

• Introduction
• Flow Logic
• Links

Introduction

Screens (also known as dynpros) are the most general type of user dialog in SAP applications before SAP NetWeaver.
You do not define them in ABAP programs, but instead in the Screen Painter.
A screen consists of the layout and the flow logic.
You can define screens for any program with type 1 (executable), M (module pools), or F (function groups).

Screens are some kind of dynamic programs, and have their own data objects, called screen fields. These are linked to the input/output fields that appear on the screen itself. When the screen is displayed, and when it finishes processing, the system passes data between the screen fields and data objects in the ABAP program. Data is copied between identically-named fields.

Each screen needs a GUI status to be assigned at runtime during PBO in your ABAP program. The GUI status contains a menu bar, standard toolbar, and an application toolbar. Like screens, GUI statuses are independent components of the ABAP program. You create them in the ABAP Workbench using the Menu Painter.

The screens in a single ABAP program can be combined to form screen sequences. You can call single screens or screen sequences either using a transaction code from outside the ABAP program, or by using the CALL SCREEN statement in the corresponding ABAP program. When you call a screen or screen sequence, the screen flow logic takes control of the ABAP program execution. You can define screen sequences dynamically by setting the next screen attribute for a screen dynamically in the ABAP program.

Selection screens are special screens that use the same technology but are not created using the Screen Painter. Instead, they are defined via ABAP statements PARAMETERS, SELECT-OPTIONS, SELECTION-SCREEN, etc.

Flow Logic

The screen flow logic is divided into the Process Before Output (PBO) event, which is processed before the screen is displayed, and the Process After Input (PAI) event, which is processed after a user action on the screen. The screen flow logic calls dialog modules in the ABAP program, either to prepare the screen for display (PBO event) or to process the user's entries (PAI event).

https://wiki.sdn.sap.com/wiki/display/ABAP/Screens+%28dynpros%29

Recruitment instrument

Recruitment instrument

A recruitment instrument is the specific tool used to publish a job advertisement or to provide information on the company with the aim of attracting unsolicited applications.

Examples

Examples of recruitment instruments include:

• The Wall Street Journal

• The employment office in Twin Falls, Idaho

• CeBIT (trade fair)

SAP說明