FPM ABAP: Can't find the hotkey?

As of SAP EhP1 for NetWeaver we can assign hotkey to UI element like buttons in Web Dynpro ABAP.
However, it seems I can't find the way to assign hotkey using the FPM editor or the FPM API,
please help,
PS: We are on EhP 1 SP3.
thanks
Alexandre Giguere

Thanks Thomas, do you know the release date of the NW EhP2 or maybe it will be confirmed at TechEd?
I just write an OSS message to SAP, cause I know from the config. editor we can't assign hotkey to the CNR. But according to Floorplan Manager for ABAP - Developer's Guide (122 pages Release 7.01) .. there should be an API to assign an hotkey to a button. If I look the code at page 36, I should be able to see the import parameter IV_HOTKEY for method DEFINE_BUTTON of the interface IF_FPM_CNR_OIF or IF_FPM_GAF_OIF.
Another option, would be to create an invisible button on my UIBB, assign this button a hotkey. Catching the hokey event and raising by myself and FPM event, that would be a temporary fix.
[http://www.flickr.com/photos/34819919@N06/3862700042/]
Alex

Similar Messages

In which folder can I find the abap instance profile?

Hi,
In which folder can I find the abap instance profile?
This is the parameter that I want to change:
"profile parameter em/address_space_MB = 250 in the instance profile"
Greets
Stefan

Hi Michal,
my actual problom is, that during the Java-Add-In-Installation an error appears. (CJS-20057)
j2ee-engine (dvebmgs00) do not start during this installation.
I also change the value of max. heap size and try a rebase as it is shown in note 129813.
nothing chances.
this error appears all the time.
can anybody help me please?
Thanks.
Greets
Stefan

Can not find the the RBS tables after installing the Remote Blog Storage

Hi,
I am trying to configure the Remote Blob storage on my Sharepoint Server 2013. I am using the SQL Server Express 10.50.6000.
Everything is going fine, but I can not find the tables in the Database.
I am not sure where I did the wrong thing.
machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
but the installation is looking for some other.
Thanks in advance.
=== Verbose logging started: 3/23/2015 13:55:09 Build type: SHIP UNICODE 5.00.7601.00 Calling process: C:\Windows\system32\msiexec.exe ===
MSI (c) (44:F8) [13:55:09:000]: Resetting cached policy values
MSI (c) (44:F8) [13:55:09:000]: Machine policy value 'Debug' is 0
MSI (c) (44:F8) [13:55:09:000]: ******* RunEngine:
******* Product: RBS.msi
******* Action:
******* CommandLine: **********
MSI (c) (44:F8) [13:55:09:000]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (44:F8) [13:55:09:000]: Grabbed execution mutex.
MSI (c) (44:F8) [13:55:09:016]: Cloaking enabled.
MSI (c) (44:F8) [13:55:09:016]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (44:F8) [13:55:09:016]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (90:A4) [13:55:09:016]: Running installation inside multi-package transaction D:\RBS.msi
MSI (s) (90:A4) [13:55:09:016]: Grabbed execution mutex.
MSI (s) (90:34) [13:55:09:016]: Resetting cached policy values
MSI (s) (90:34) [13:55:09:016]: Machine policy value 'Debug' is 0
MSI (s) (90:34) [13:55:09:016]: ******* RunEngine:
******* Product: D:\RBS.msi
******* Action:
******* CommandLine: **********
MSI (s) (90:34) [13:55:09:031]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (90:34) [13:55:09:031]: Setting cached product context: User non-assigned for product: FB42F99F09B0E3646985F32DFE3C9C29
MSI (s) (90:34) [13:55:09:031]: Using cached product context: User non-assigned for product: FB42F99F09B0E3646985F32DFE3C9C29
MSI (s) (90:34) [13:55:09:031]: Setting cached product context: machine assigned for product: 000021599B0090400100000000F01FEC
115C834F46A5E33479CEE53534AD76A0
:34) [13:55:09:265]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (90:34) [13:55:09:265]: Machine policy value 'DisableFlyWeightPatching' is 0
MSI (s) (90:34) [13:55:09:265]: Enabling baseline caching for this transaction since all active patches are MSI 3.0 style MSPs or at least one MSI 3.0 minor update patch is active
MSI (s) (90:34) [13:55:09:265]: APPCOMPAT: looking for appcompat database entry with ProductCode '{56D21E05-679B-40F2-94C1-DB0D7EB2E461}'.
MSI (s) (90:34) [13:55:09:265]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (90:34) [13:55:09:265]: Transforms are not secure.
MSI (s) (90:34) [13:55:09:265]: PROPERTY CHANGE: Adding MsiLogFileLocation property. Its value is 'D:\rbs_install_log.txt'.
MSI (s) (90:34) [13:55:09:265]: Command Line: TRUSTSERVERCERTIFICATE=true FILEGROUP=PRIMARY DBNAME=WSS_Content DBINSTANCE=jpntkyint01\sharepoint FILESTREAMFILEGROUP=RBSFilestreamProvider FILESTREAMSTORENAME=FilestreamProvider_1 CURRENTDIRECTORY=D:\ CLIENTUILEVEL=3 CLIENTPROCESSID=14660
MSI (s) (90:34) [13:55:09:265]: PROPERTY CHANGE: Adding PackageCode property. Its value is '{1AC68E73-94F1-4A01-B229-82B2F73C3326}'.
MSI (s) (90:34) [13:55:09:265]: Product Code passed to Engine.Initialize: '{56D21E05-679B-40F2-94C1-DB0D7EB2E461}'
MSI (s) (90:34) [13:55:09:265]: Product Code from property table before transforms: '{56D21E05-679B-40F2-94C1-DB0D7EB2E461}'
MSI (s) (90:34) [13:55:09:265]: Product Code from property table after transforms: '{56D21E05-679B-40F2-94C1-DB0D7EB2E461}'
MSI (s) (90:34) [13:55:09:265]: Product registered: entering maintenance mode
MSI (s) (90:34) [13:55:09:265]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (90:34) [13:55:09:265]: Determined that existing product (either this product or the product being upgraded with a patch) is installed per-machine.
MSI (s) (90:34) [13:55:09:265]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (90:34) [13:55:09:265]: Product {56D21E05-679B-40F2-94C1-DB0D7EB2E461} is admin assigned: LocalSystem owns the publish key.
MSI (s) (90:34) [13:55:09:265]: Product {56D21E05-679B-40F2-94C1-DB0D7EB2E461} is managed.
MSI (s) (90:34) [13:55:09:265]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (90:34) [13:55:09:281]: MSI_LUA: Credential prompt not required, user is an admin
MSI (s) (90:34) [13:55:09:281]: PROPERTY CHANGE: Adding ProductState property. Its value is '5'.
MSI (s) (90:34) [13:55:09:281]: PROPERTY CHANGE: Adding ProductToBeRegistered property. Its value is '1'.
MSI (s) (90:34) [13:55:09:281]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (90:34) [13:55:09:281]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (90:34) [13:55:09:281]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer 3: 2
MSI (s) (90:34) [13:55:09:281]: Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (s) (90:34) [13:55:09:281]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (90:34) [13:55:09:281]: Specifed source is already in a list.
MSI (s) (90:34) [13:55:09:281]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (90:34) [13:55:09:281]: Machine policy value 'DisableBrowse' is 0
MSI (s) (90:34) [13:55:09:281]: Machine policy value 'AllowLockdownBrowse' is 0
MSI (s) (90:34) [13:55:09:281]: Adding new sources is allowed.
MSI (s) (90:34) [13:55:09:281]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (90:34) [13:55:09:281]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (90:34) [13:55:09:281]: Package name retrieved from configuration data: 'RBS.msi'
MSI (s) (90:34) [13:55:09:281]: Note: 1: 2262 2: AdminProperties 3: -2147287038
MSI (s) (90:34) [13:55:09:281]: Machine policy value 'DisableMsi' is 1
MSI (s) (90:34) [13:55:09:281]: Machine policy value 'AlwaysInstallElevated' is 0
MSI (s) (90:34) [13:55:09:281]: User policy value 'AlwaysInstallElevated' is 0
MSI (s) (90:34) [13:55:09:281]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (90:34) [13:55:09:281]: Product {56D21E05-679B-40F2-94C1-DB0D7EB2E461} is admin assigned: LocalSystem owns the publish key.
MSI (s) (90:34) [13:55:09:281]: Product {56D21E05-679B-40F2-94C1-DB0D7EB2E461} is managed.
MSI (s) (90:34) [13:55:09:281]: Running product '{56D21E05-679B-40F2-94C1-DB0D7EB2E461}' with elevated privileges: Product is assigned.
MSI (s) (90:34) [13:55:09:281]: PROPERTY CHANGE: Adding TRUSTSERVERCERTIFICATE property. Its value is 'true'.
MSI (s) (90:34) [13:55:09:281]: PROPERTY CHANGE: Modifying FILEGROUP property. Its current value is 'default'. Its new value: 'PRIMARY'.
MSI (s) (90:34) [13:55:09:281]: PROPERTY CHANGE: Adding DBNAME property. Its value is 'WSS_Content'.
MSI (s) (90:34) [13:55:09:281]: PROPERTY CHANGE: Adding DBINSTANCE property. Its value is 'jpntkyint01\sharepoint'.
MSI (s) (90:34) [13:55:09:281]: PROPERTY CHANGE: Modifying FILESTREAMFILEGROUP property. Its current value is 'default'. Its new value: 'RBSFilestreamProvider'.
MSI (s) (90:34) [13:55:09:281]: PROPERTY CHANGE: Adding FILESTREAMSTORENAME property. Its value is 'FilestreamProvider_1'.
MSI (s) (90:34) [13:55:09:281]: PROPERTY CHANGE: Adding CURRENTDIRECTORY property. Its value is 'D:\'.
MSI (s) (90:34) [13:55:09:281]: PROPERTY CHANGE: Adding CLIENTUILEVEL property. Its value is '3'.
MSI (s) (90:34) [13:55:09:281]: PROPERTY CHANGE: Adding CLIENTPROCESSID property. Its value is '14660'.
MSI (s) (90:34) [13:55:09:281]: Machine policy value 'DisableAutomaticApplicationShutdown' is 0
MSI (s) (90:34) [13:55:09:328]: PROPERTY CHANGE: Adding MsiRestartManagerSessionKey property. Its value is '489ffd242e95054781e9ce4b8d0b8aa5'.
MSI (s) (90:34) [13:55:09:328]: RESTART MANAGER: Session opened.
MSI (s) (90:34) [13:55:09:328]: TRANSFORMS property is now:
MSI (s) (90:34) [13:55:09:328]: PROPERTY CHANGE: Adding PRODUCTLANGUAGE property. Its value is '1033'.
MSI (s) (90:34) [13:55:09:328]: PROPERTY CHANGE: Adding VersionDatabase property. Its value is '300'.
MSI (s) (90:34) [13:55:09:328]: SHELL32::SHGetFolderPath returned: C:\Users\medsvradmin\AppData\Roaming
MSI (s) (90:34) [13:55:09:328]: SHELL32::SHGetFolderPath returned: C:\Users\medsvradmin\Favorites
Action ended 13:55:09: AppSearch. Return value 1.
Action start 13:55:09: ValidateProductID.
MSI (s) (90:34) [13:55:09:390]: Skipping action: Sqlmsirc_CheckLanguage_64 (condition is false)
MSI (s) (90:34) [13:55:09:390]: Doing action: CostInitialize
Action ended 13:55:09: ValidateProductID. Return value 1.
MSI (s) (90:34) [13:55:09:406]: Machine policy value 'MaxPatchCacheSize' is 10
MSI (s) (90:34) [13:55:09:406]: Baseline: Sorting baselines for {56D21E05-679B-40F2-94C1-DB0D7EB2E461}.
MSI (s) (90:34) [13:55:09:406]: Baseline: New baseline 10.50.1600 from transaction.
MSI (s) (90:34) [13:55:09:437]: Baseline: Sorted order Native: Order 0.
MSI (s) (90:34) [13:55:09:437]: Baseline Data Table:
MSI (s) (90:34) [13:55:09:437]: ProductCode: {56D21E05-679B-40F2-94C1-DB0D7EB2E461} Version: 10.50.1600 Attributes: 0 PatchId: Native BaselineId: -2147483648 Order: 0
MSI (s) (90:34) [13:55:09:437]: Baseline File Table:
MSI (s) (90:34) [13:55:09:437]: PROPERTY CHANGE: Adding ROOTDRIVE property. Its value is 'D:\'.
MSI (s) (90:34) [13:55:09:437]: PROPERTY CHANGE: Adding CostingComplete property. Its value is '0'.
MSI (s) (90:34) [13:55:09:453]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (90:34) [13:55:09:453]: Note: 1: 2205 2: 3: Patch
MSI (s) (90:34) [13:55:09:453]: Note: 1: 2205 2: 3: PatchPackage
MSI (s) (90:34) [13:55:09:453]: Note: 1: 2205 2: 3: MsiPatchHeaders
MSI (s) (90:34) [13:55:09:453]: Note: 1: 2205 2: 3: __MsiPatchFileList
MSI (s) (90:34) [13:55:09:453]: Note: 1: 2205 2: 3: PatchPackage
MSI (s) (90:34) [13:55:09:453]: Note: 1: 2228 2: 3: PatchPackage 4: SELECT `DiskId`, `PatchId`, `LastSequence` FROM `Media`, `PatchPackage` WHERE `Media`.`DiskId`=`PatchPackage`.`Media_` ORDER BY `DiskId`
MSI (s) (90:34) [13:55:09:453]: Delta compression fallback method for this product transaction is 'MSI 2.0 legacy obsolescence'
MSI (s) (90:34) [13:55:09:453]: Note: 1: 2205 2: 3: Patch
Action start 13:55:09: CostInitialize.
MSI (s) (90:34) [13:55:09:453]: Doing action: FileCost
Action ended 13:55:09: CostInitialize. Return value 1.
MSI (s) (90:34) [13:55:09:468]: Note: 1: 2205 2: 3: Class
MSI (s) (90:34) [13:55:09:468]: Note: 1: 2205 2: 3: Extension
MSI (s) (90:34) [13:55:09:468]: Note: 1: 2205 2: 3: TypeLib
Action start 13:55:09: FileCost.
MSI (s) (90:34) [13:55:09:468]: Doing action: IsolateComponents
Action ended 13:55:09: FileCost. Return value 1.
Action start 13:55:09: IsolateComponents.
MSI (s) (90:34) [13:55:09:468]: Doing action: CostFinalize
GE: Adding ClientDir1025 property. Its value is 'C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\Client Library\ar\'.
MSI (s) (90:34) [13:55:09:593]: PROPERTY CHANGE: Modifying ServerDir property. Its current value is 'C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\Server'. Its new value: 'C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\Server\'.
MSI (s) (90:34) [13:55:09:593]: PROPERTY CHANGE: Modifying Eula1033 property. Its current value is 'C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\1033'. Its new value: 'C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\1033\'.
MSI (s) (90:34) [13:55:09:593]: Target path resolution complete. Dumping Directory table...
MSI (s) (90:34) [13:55:09:593]: Note: target paths subject to change (via custom actions or browsing)
MSI (s) (90:34) [13:55:09:593]: Dir (target): Key: TARGETDIR , Object: D:\
MSI (s) (90:34) [13:55:09:593]: Dir (target): Key: WindowsFolder , Object: C:\Windows\
MSI (s) (90:34) [13:55:09:593]: Dir (target): Key: ProgramFiles64Folder , Object: C:\Program Files\
MSI (s) (90:34) [13:55:09:593]: Dir (target): Key: INSTALLDIR , Object: C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\
MSI (s) (90:34) [13:55:09:593]: Dir (target): Key: GAC , Object: C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\
MSI (s) (90:34) [13:55:09:593]: Dir (target): Key: ClientDir , Object: C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\Client Library\
MSI (s) (90:34) [13:55:09:593]: Dir (target): Key: ClientDir3082 , Object: C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\Client Library\es\
MSI (s) (90:34) [13:55:09:593]: Dir (target): Key: ClientDir1025 , Object: C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\Client Library\ar\
MSI (s) (90:34) [13:55:09:593]: Dir (target): Key: ServerDir , Object: C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\Server\
MSI (s) (90:34) [13:55:09:593]: Dir (target): Key: Eula1033 , Object: C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\1033\
MSI (s) (90:34) [13:55:09:593]: Doing action: IsDotNet20Or40Installed
Action ended 13:55:09: CostFinalize. Return value 1.
MSI (s) (90:34) [13:55:09:593]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'IsDotNet20Or40Installed'
MSI (s) (90:34) [13:55:09:609]: Creating MSIHANDLE (1) of type 790542 for thread 9268
MSI (s) (90:6C) [13:55:09:609]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIB261.tmp, Entrypoint: IsDotNetFramework20Or40Installed
MSI (s) (90:FC) [13:55:09:609]: Generating random cookie.
MSI (s) (90:FC) [13:55:09:609]: Created Custom Action Server with PID 14944 (0x3A60).
MSI (s) (90:D0) [13:55:09:640]: Running as a service.
MSI (s) (90:D0) [13:55:09:640]: Hello, I'm your 64bit Impersonated custom action server.
MSI (s) (90!08) [13:55:09:640]: PROPERTY CHANGE: Adding DOTNETCOREPATH property. Its value is '1'.
MSI (s) (90!08) [13:55:09:640]: PROPERTY CHANGE: Adding IsDotNet20Or40Installed property. Its value is '1'.
MSI (s) (90:6C) [13:55:09:640]: Closing MSIHANDLE (1) of type 790542 for thread 9268
One or more .NET Framework assemblies found in MsiAssembly table require the GAC, need to check for the .NET Framework
MSI (s) (90:34) [13:55:09:640]: Skipping action: CA_ErrorPrereqDotNet20Or40 (condition is false)
MSI (s) (90:34) [13:55:09:640]: Doing action: SqlFollowComponentsValidate_Redist_64
Action ended 13:55:09: IsDotNet20Or40Installed. Return value 1.
MSI (s) (90:34) [13:55:09:640]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'SqlFollowComponentsValidate_Redist_64'
MSI (s) (90:34) [13:55:09:687]: Creating MSIHANDLE (11) of type 790542 for thread 9268
MSI (s) (90:04) [13:55:09:687]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIB281.tmp, Entrypoint: SqlFollowComponentsValidate
Action start 13:55:10: InstallServices.
MSI (s) (90:34) [13:55:10:498]: Doing action: StartServices
Action ended 13:55:10: InstallServices. Return value 1.
MSI (s) (90:34) [13:55:10:498]: Note: 1: 2205 2: 3: ServiceControl
MSI (s) (90:34) [13:55:10:498]: Note: 1: 2228 2: 3: ServiceControl 4: SELECT `Name`,`Wait`,`Arguments`,`Event`, `Action` FROM `ServiceControl`, `Component` WHERE `Component_` = `Component` AND (`Action` = 0 OR `Action` = 1 OR `Action` = 2)
Action start 13:55:10: StartServices.
MSI (s) (90:34) [13:55:10:498]: Doing action: RegisterUser
Action ended 13:55:10: StartServices. Return value 1.
Action start 13:55:10: RegisterUser.
MSI (s) (90:34) [13:55:10:498]: Doing action: RegisterProduct
Action ended 13:55:10: RegisterUser. Return value 0.
MSI (s) (90:34) [13:55:10:498]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (90:34) [13:55:10:498]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
Action start 13:55:10: RegisterProduct.
MSI (s) (90:34) [13:55:10:498]: Doing action: PublishComponents
Action ended 13:55:10: RegisterProduct. Return value 1.
MSI (s) (90:34) [13:55:10:498]: Note: 1: 2205 2: 3: PublishComponent
MSI (s) (90:34) [13:55:10:498]: Note: 1: 2228 2: 3: PublishComponent 4: SELECT `PublishComponent`.`ComponentId`, `PublishComponent`.`Qualifier`, `PublishComponent`.`AppData`, `Feature`, `Component`.`ComponentId`, `Component`.`RuntimeFlags` FROM `PublishComponent`, `Component`, `Feature` WHERE `PublishComponent`.`Component_` = `Component`.`Component` AND `PublishComponent`.`Feature_` = `Feature`.`Feature` AND ((`Feature`.`Action` = 1 OR `Feature`.`Action` = 2) OR (`Feature`.`Action` = 4 AND `Feature`.`Installed` = 0) OR (`Feature`.`Action` = 3 AND (`Feature`.`Installed` = 1 OR `Feature`.`Installed` = 2 OR `Feature`.`Installed` = 4)))
Action start 13:55:10: PublishComponents.
MSI (s) (90:34) [13:55:10:498]: Doing action: MsiPublishAssemblies
Action ended 13:55:10: PublishComponents. Return value 0.
Action start 13:55:10: MsiPublishAssemblies.
MSI (s) (90:34) [13:55:10:498]: Doing action: PublishFeatures
Action ended 13:55:10: MsiPublishAssemblies. Return value 1.
MSI (s) (90:34) [13:55:10:498]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (90:34) [13:55:10:498]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
Action start 13:55:10: PublishFeatures.
MSI (s) (90:34) [13:55:10:498]: Doing action: PublishProduct
Action ended 13:55:10: PublishFeatures. Return value 1.
MSI (s) (90:34) [13:55:10:513]: Resolving source to launched-from source.
MSI (s) (90:34) [13:55:10:513]: Setting launched-from source as last-used.
MSI (s) (90:34) [13:55:10:513]: PROPERTY CHANGE: Adding SourceDir property. Its value is 'D:\'.
MSI (s) (90:34) [13:55:10:513]: PROPERTY CHANGE: Adding SOURCEDIR property. Its value is 'D:\'.
MSI (s) (90:34) [13:55:10:513]: PROPERTY CHANGE: Adding SourcedirProduct property. Its value is '{56D21E05-679B-40F2-94C1-DB0D7EB2E461}'.
MSI (s) (90:34) [13:55:10:513]: SOURCEDIR ==> D:\
MSI (s) (90:34) [13:55:10:513]: SOURCEDIR product ==> {56D21E05-679B-40F2-94C1-DB0D7EB2E461}
MSI (s) (90:34) [13:55:10:529]: SECREPAIR: CryptAcquireContext succeeded
MSI (s) (90:34) [13:55:10:529]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (90:34) [13:55:10:529]: Determining source type
MSI (s) (90:34) [13:55:10:529]: Source type from package 'RBS.msi': 2
MSI (s) (90:34) [13:55:10:529]: SECREPAIR: Hash Database: C:\Windows\Installer\SourceHash{56D21E05-679B-40F2-94C1-DB0D7EB2E461}
MSI (s) (90:34) [13:55:10:623]: SECREPAIR: Hash Value for the file:RBS.msi matched
MSI (s) (90:34) [13:55:10:623]: Source path resolution complete. Dumping Directory table...
MSI (s) (90:34) [13:55:10:623]: Dir (source): Key: TARGETDIR , Object: D:\ , LongSubPath: , ShortSubPath:
MSI (s) (90:34) [13:55:10:623]: Dir (source): Key: WindowsFolder , Object: D:\ , LongSubPath: , ShortSubPath:
MSI (s) (90:34) [13:55:10:623]: Dir (source): Key: ProgramFiles64Folder , Object: D:\ , LongSubPath: Program Files\ , ShortSubPath: PFiles\
MSI (s) (90:34) [13:55:10:623]: Dir (source): Key: INSTALLDIR , Object: D:\ , LongSubPath: Program Files\Microsoft SQL Remote Blob Storage 10.50\ , ShortSubPath: PFiles\jfw2d1_t\
MSI (s) (90:34) [13:55:10:623]: Dir (source): Key: Eula3082 , Object: D:\ , LongSubPath: Program Files\Microsoft SQL
MSI (s) (90:34) [13:55:10:623]: Dir (source): Key: DocsDir , Object: D:\ , LongSubPath: Program Files\Microsoft SQL Remote Blob Storage 10.50\Documentation\ , ShortSubPath: PFiles\jfw2d1_t\gsutoqfr\
MSI (s) (90:34) [13:55:10:623]: Dir (source): Key: MaintainerDir , Object: D:\ , LongSubPath: Program Files\Microsoft SQL Remote Blob Storage 10.50\Maintainer\ , ShortSubPath: PFiles\jfw2d1_t\jygjogya\
Files\jfw2d1_t\g-pfawke\pt-PT\
MSI (s) (90:34) [13:55:10:623]: Dir (source): Key: ClientDir2052 , Object: D:\ , LongSubPath: Program Files\Microsoft SQL Remote Blob Storage 10.50\Client Library\zh-CHS\ , ShortSubPath: PFiles\jfw2d1_t\g-pfawke\zh-CHS\
Action ended 13:55:10: PublishProduct. Return value 1.
MSI (s) (90:34) [13:55:10:638]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (90:34) [13:55:10:638]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (90:34) [13:55:10:638]: Note: 1: 2205 2: 3: Shortcut
MSI (s) (90:34) [13:55:10:638]: Note: 1: 2228 2: 3: Shortcut 4: SELECT `Shortcut`,`Name`, `FileName`, `Component`.`Directory_`, `Arguments`, `WkDir`, `Icon_`, `IconIndex`, `Hotkey`, `ShowCmd`, `Shortcut`.`Description`, `Shortcut`.`Directory_`, `Component`.`RuntimeFlags`, `Component`.`Action`, `Target`, `ComponentId`, `Feature`.`Action`, `Component`.`Installed`, `DisplayResourceDLL`, `DisplayResourceId`, `DescriptionResourceDLL`, `DescriptionResourceId` From `Shortcut`, `Feature`, `Component`, `File` WHERE `Target` = `Feature` AND `Shortcut`.`Component_` = `Component` AND `Component`.`KeyPath` = `File`.`File` AND ((`Feature`.`Action` = 1 OR `Feature`.`Action` = 2) OR (`Feature`.`Action` = 4 AND `Feature`.`Installed` = 0) OR (`Feature`.`Action` = 3 AND (`Feature`.`Installed` = 1 OR `Feature`.`Installed` = 2 OR `Feature`.`Installed` = 4)) OR (`Feature`.`Action` = NULL AND (`Component`.`Action` = 1 OR `Component`.`Action` = 2) AND (`Feature`.`Installed` = 1 OR `Feature`.`Installed` = 2 OR `Feature`.`Installed` = 4)))
Action start 13:55:10: CreateShortcuts.
MSI (s) (90:34) [13:55:10:638]: Doing action: FixCounters
Action ended 13:55:10: CreateShortcuts. Return value 0.
MSI (s) (90:34) [13:55:10:638]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'FixCounters'
Return value 0.
Action ended 13:55:20: INSTALL. Return value 1.
Property(S): DiskPrompt = [1]
Property(S): InstallMode = Typical
Property(S): DOTNET20SP = #2
Property(S): DOTNET35SP = #1
Property(S): DBINSTANCEREGISTRY = SHAREPOINT
Property(S): DBNAMEREGISTRY = WSS_Content
Property(S): FILESTREAMSTORENAMEREGISTRY = FilestreamProvider_1
Property(S): SCHEMASUFFIXREGISTRY = <suffix>
Property(S): WelcomeBmp = WelcomeBmp
Property(S): TRUSTSERVERCERTIFICATE = true
Property(S): SCHEDULEMAINTAINERTASK = 1
Property(S): MAINTAINERGC = GarbageCollection
Property(S): MAINTAINERREFSCAN = r
Property(S): MAINTAINERDELETE = d
Property(S): MAINTAINERORPHAN = o
Property(S): MAINTAINERCONSISTENCY = ConsistencyCheck
Property(S): MAINTAINERCONSISTENCYREPAIR = true
Property(S): OPENREADME = 1
Property(S): FilestreamPoolTranLifetimeUnit = time
Property(S): TEXTFILEVALUE = 0
Property(S): CONSOLEVALUE = 0
Property(S): DBTABLEVALUE = 0
Property(S): EVENTLOGVALUE = 4
Property(S): DBINSTANCE = jpntkyint01\sharepoint
Property(S): DBNAME = WSS_Content
Property(S): FILEGROUP = PRIMARY
Property(S): INTEGRATEDSECURITY = 1
Property(S): DBUSERNAME = username
Property(S): DBPASSWORD = **********
Property(S): FSDBINSTANCE = jpntkyint01\sharepoint
Property(S): FSDBNAME = WSS_Content
Property(S): FILESTREAMMETADATAFILEGROUP = PRIMARY
Property(S): FILESTREAMFILEGROUP = RBSFilestreamProvider
Property(S): FILESTREAMSTORENAME = FilestreamProvider_1
Property(S): SCHEMASUFFIX = <suffix>
Property(S): FILESTREAMTRANPOOLSIZE = 5
Property(S): FilestreamPoolTranLifetimeTime = 00:01:00
Property(S): FilestreamPoolTranLifetimeDays = 01
Property(S): FILESTREAMMAXPOOLSIZE = 200000
Property(S): FILESTREAMMAXSIZEINBANDWRITE = 1258290
Property(S): FILESTREAMMAXSIZEINBANDREAD = 1258290
Property(S): FILESTREAMMAXSIZEINLINEBLOB = 61140
Property(S): FILESTREAMWRITEALLOCATIONSIZE = 0
Property(S): MAINTAINERDURATION = 120
Property(S): SQLServerText1 = 0
Property(S): SQLServerVersionText3 = 0
Property(S): _IsMaintenance2 = Modify
Property(S): ModifyIcon = ModifyIco
Property(S): RepairIcon = RepairIco
Property(S): RemoveIcon = RemoveIco
Property(S): ErrorIcon = ErrorIco
Property(S): TARGETDIR = D:\
Property(S): USERNAME = Windows User
Property(S): _IsMaintenance = Reinstall
Property(S): AgreeToLicense = No
Property(S): Interrupted = 0
Property(S): SetupIcon = SetupIco
Property(S): Installed = 00:00:00
Property(S): CreateFilesNoUI = C:\Windows\system32\;D:\RBS.msi
Property(S): FixLogConfig = 4;0;0;0;0
Property(S): FixRemoteFilestreamStoreConfig = remotefilestream;C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\Provider Libraries\Filestream Provider\RemoteFilestreamProviderConfiguration.xml
Property(S): FixFilestreamStoreConfig = filestream;C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\Provider Libraries\Filestream Provider\FilestreamProviderConfiguration.xml
Property(S): RegisterProviderFile = RegisterFilestreamProvider.sql
Property(S): FILESTREAMTRANPOOLTRANLIFETIME = time 00:01:00
Property(S): IsDotNet20Or40Installed = 1
Property(S): ProgramMenuFolder.Sql = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\
Property(S): SAPBINOTEPAD = Notepad.exe
Property(S): MaintainerDir1025 = C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\Maintainer\ar\
Property(S): ClientDir3082 = C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\Client Library\es\
Property(S): FilestreamDir1025 = C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\Provider Libraries\Filestream Provider\ar\
Property(S): ProviderDir = C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\Provider Libraries\
Property(S): Eula3082 = C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\3082\
Property(S): ProgramFiles64Folder = C:\Program Files\
Property(S): SourceDir = D:\
Property(S): VersionNT = 601
Property(S): Privileged = 1
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductCode = {56D21E05-679B-40F2-94C1-DB0D7EB2E461}
Property(S): ProductLanguage = 1033
Property(S): ProductName = SQL Server 2008 R2 Remote Blob Store
Property(S): ProductVersion = 10.50.1600.1
Property(S): UpgradeCode = {BA2FF55A-725F-40E5-956E-D08AD0B8175B}
Property(S): ProductShortName = Remote Blob Store
Property(S): PlatformExtension = _64
Property(S): PlatformId = x64
Property(S): AppGuidRegKey = Redist_Uninstall_RegKey
Property(S): ARPPRODUCTICON = ARPIco
Property(S): ARPHELPLINK = http://www.microsoft.com/sqlserver
Property(S): PIDTemplate = 53934<````=````=````=````=`````>@@@@@
Property(S): PROMPTROLLBACKCOST = P
Property(S): INSTALLLEVEL = 100
Property(S): ALLUSERS = 1
Property(S): SuccessIcon = SuccessIco
Property(S): WarningIcon = WarningIco
Property(S): LicenseIcon = LicenseIco
Property(S): CompleteIcon = CompleteIco
Property(S): CustomIcon = CustomIco
Property(S): NewIcon = NewIco
Property(S): UpIcon = UpIco
Property(S): DialogBanner = BannerBmp
Property(S): Details = 0
Property(S): ReinstallModeText = omus
Property(S): Display_IsBitmapDlg = 1
Property(S): ProductID = none
Property(S): ISENABLEDWUSFINISHDIALOG = 1
Property(S): SQLServerVersionText1 = 0
Property(S): SQLServerVersionText2 = 0
Property(S): CA_ERRORCOUNT = 0
Property(S): CA_WARNINGCOUNT = 0
Property(S): CA_SUCCESSCOUNT = 0
Property(S): UI_SHOWCOPYRIGHT = yes
Property(S): ShowUserRegistrationDlg = 1
Property(S): ButtonTextStyle = {\ButtonTextStyle}
Property(S): DlgTextStyle = {\DlgTextStyle}
Property(S): DlgTextStyleB = {\DlgTextStyleB}
Property(S): DlgTitleStyle = {\DlgTitleStyle}
Property(S): DlgTitleStyleB = {\DlgTitleStyleB}
Property(S): FixedStyle = {\FixedStyle}
Property(S): Error_UninstallDependant = 1
Property(S): DefaultUIFont = Tahoma8
Property(S): ProductFeaturesDefined = 1
Property(S): RBSRegistryKey = Software\Microsoft\Remote Blob Storage
Property(S): SCHEMASUFFIXVALID = 0
Property(S): EnableCustomConfigDlg = 1
Property(S): EnableCustomRemoveDlg = 1
Property(S): EnableDotNetCheck = 1
Property(S): FXAssemblyVersion = 2.0.0.0
Property(S): VSAssemblyVersion = 8.0.0.0
Property(S): EnableFeatureDlg = 1
Property(S): MaintenanceWelcomeDlg_Next = MaintenanceTypeDlg
Property(S): ReadyToRemoveDlg_Back = MaintenanceTypeDlg
Property(S): CustomerInfoDlg_Next = ReadyToInstallDlg
Property(S): CustomerInfoDlg_Back = LicenseAgreementDlg
Property(S): ReadyToInstallDlg_NotInstalled_Back = CustomerInfoDlg
Property(S): ReadyToInstallDlg_Installed_Back = MaintenanceTypeDlg
Property(S): InstallWelcomeDlg_Next = LicenseAgreementDlg
Property(S): LicenseAgreementDlg_Back = InstallWelcomeDlg
Property(S): LicenseAgreementDlg_Next = CustomerInfoDlg
Property(S): ModuleID_REDISTBASE = SQLBASE_Redist_64
Property(S): ErrorDialog = ErrorDlg
Property(S): MsiLogFileLocation = D:\rbs_install_log.txt
Property(S): PackageCode = {1AC68E73-94F1-4A01-B229-82B2F73C3326}
Property(S): ProductState = 5
Property(S): ProductToBeRegistered = 1
Property(S): CURRENTDIRECTORY = D:\
Property(S): CLIENTUILEVEL = 3
Property(S): CLIENTPROCESSID = 14660
Property(S): PRODUCTLANGUAGE = 1033
Property(S): VersionDatabase = 300
Property(S): VersionMsi = 5.00
Property(S): VersionNT64 = 601
Property(S): WindowsBuild = 7601
Property(S): ServicePackLevel = 1
Property(S): ServicePackLevelMinor = 0
Property(S): MsiNTProductType = 3
Property(S): WindowsFolder = C:\Windows\
Property(S): WindowsVolume = C:\
Property(S): System64Folder = C:\Windows\system32\
Property(S): SystemFolder = C:\Windows\SysWOW64\
Property(S): RemoteAdminTS = 1
Property(S): TempFolder = C:\Users\MEDSVR~1\AppData\Local\Temp\
Property(S): ProgramFilesFolder = C:\Program Files (x86)\
Property(S): CommonFilesFolder = C:\Program Files (x86)\Common Files\
Property(S): CommonFiles64Folder = C:\Program Files\Common Files\
Property(S): AppDataFolder = C:\Users\medsvradmin\AppData\Roaming\
Property(S): FavoritesFolder = C:\Users\medsvradmin\Favorites\
Property(S): NetHoodFolder = C:\Users\medsvradmin\AppData\Roaming\Microsoft\Windows\Network Shortcuts\
Property(S): PersonalFolder = C:\Users\medsvradmin\Documents\
Property(S): PrintHoodFolder = C:\Users\medsvradmin\AppData\Roaming\Microsoft\Windows\Printer Shortcuts\
Property(S): RecentFolder = C:\Users\medsvradmin\AppData\Roaming\Microsoft\Windows\Recent\
Property(S): SendToFolder = C:\Users\medsvradmin\AppData\Roaming\Microsoft\Windows\SendTo\
Property(S): TemplateFolder = C:\ProgramData\Microsoft\Windows\Templates\
Property(S): CommonAppDataFolder = C:\ProgramData\
Property(S): LocalAppDataFolder = C:\Users\medsvradmin\AppData\Local\
Property(S): MyPicturesFolder = C:\Users\medsvradmin\Pictures\
Property(S): AdminToolsFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools\
Property(S): StartupFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\
Property(S): ProgramMenuFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\
Property(S): StartMenuFolder = C:\ProgramData\Microsoft\Windows\Start Menu\
Property(S): DesktopFolder = C:\Users\Public\Desktop\
Property(S): FontsFolder = C:\Windows\Fonts\
Property(S): GPTSupport = 1
Property(S): OLEAdvtSupport = 1
Property(S): ShellAdvtSupport = 1
Property(S): MsiAMD64 = 6
Property(S): Msix64 = 6
Property(S): Intel = 6
Property(S): PhysicalMemory = 8192
Property(S): VirtualMemory = 6311
Property(S): AdminUser = 1
Property(S): MsiTrueAdminUser = 1
Property(S): LogonUser = medsvradmin
Property(S): UserSID = S-1-5-21-300911508-3398273753-3262312657-1000
Property(S): UserLanguageID = 1033
Property(S): ComputerName = JPNTKYINT01
Property(S): SystemLanguageID = 1033
Property(S): ScreenX = 1024
Property(S): ScreenY = 768
Property(S): CaptionHeight = 19
Property(S): BorderTop = 1
Property(S): BorderSide = 1
Property(S): TextHeight = 16
Property(S): TextInternalLeading = 3
Property(S): ColorBits = 32
Property(S): TTCSupport = 1
Property(S): Time = 13:55:20
Property(S): Date = 3/23/2015
Property(S): MsiNetAssemblySupport = 4.0.30319.34209
Property(S): MsiWin32AssemblySupport = 6.1.7601.17514
Property(S): RedirectedDllSupport = 2
Property(S): MsiRunningElevated = 1
Property(S): DATABASE = C:\Windows\Installer\6847f.msi
Property(S): OriginalDatabase = D:\RBS.msi
Property(S): UILevel = 2
Property(S): ACTION = INSTALL
Property(S): ROOTDRIVE = D:\
Property(S): CostingComplete = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): DOTNETCOREPATH = 1
Property(S): SourcedirProduct = {56D21E05-679B-40F2-94C1-DB0D7EB2E461}
Property(S): SOURCEDIR = D:\
MSI (s) (90:34) [13:55:20:201]: Note: 1: 1728
MSI (s) (90:34) [13:55:20:201]: Product: SQL Server 2008 R2 Remote Blob Store -- Configuration completed successfully.
MSI (s) (90:34) [13:55:20:201]: Windows Installer reconfigured the product. Product Name: SQL Server 2008 R2 Remote Blob Store. Product Version: 10.50.1600.1. Product Language: 1033. Manufacturer: Microsoft Corporation. Reconfiguration success or error status: 0.
MSI (s) (90:34) [13:55:20:217]: Deferring clean up of packages/files, if any exist
MSI (s) (90:34) [13:55:20:217]: MainEngineThread is returning 0
MSI (s) (90:A4) [13:55:20:217]: RESTART MANAGER: Session closed.
MSI (s) (90:A4) [13:55:20:217]: No System Restore sequence number for this installation.
=== Logging stopped: 3/23/2015 13:55:20 ===
MSI (s) (90:A4) [13:55:20:217]: User policy value 'DisableRollback' is 0
MSI (s) (90:A4) [13:55:20:217]: Machine policy value 'DisableRollback' is 0
MSI (s) (90:A4) [13:55:20:217]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (90:A4) [13:55:20:217]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (90:A4) [13:55:20:217]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (90:A4) [13:55:20:217]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (90:A4) [13:55:20:217]: Restoring environment variables
MSI (s) (90:A4) [13:55:20:217]: Destroying RemoteAPI object.
MSI (s) (90:FC) [13:55:20:233]: Custom Action Manager thread ending.
MSI (c) (44:F8) [13:55:20:233]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (44:F8) [13:55:20:233]: MainEngineThread is returning 0
=== Verbose logging stopped: 3/23/2015 13:55:20 ===

I copied and pasted the strips from SSMS in another computer
CREATE
TABLE [dbo].[Taxonomy](
[fish_id] [numeric](38, 0)
IDENTITY(1,1)
NOT NULL,
[fish_order] [varchar](50)
NOT NULL,
[fish_family] [varchar](50)
NOT NULL,
[fish_genus] [varchar](50)
NOT NULL,
[fish_species] [varchar](50)
NOT NULL,
CONSTRAINT
[Taxonomy_pk] PRIMARY
KEY CLUSTERED
[fish_id] ASC
)WITH
(PAD_INDEX
= OFF,
STATISTICS_NORECOMPUTE =
OFF,
IGNORE_DUP_KEY =
OFF, ALLOW_ROW_LOCKS
= ON,
ALLOW_PAGE_LOCKS =
ON)
ON [PRIMARY]
ON [PRIMARY]

How can we find the list of user exits for a transaction

hi all
iam new in user exits please send the basic details
how can we find the list of user exit for a perticular transaction and how can we determine that a particulr user exit is used for a field
regards
jagadish

hi,
check the below links for userexits
http://help.sap.com/saphelp_46c/helpdata/en/64/72369adc56d11195100060b03c6b76/frameset.htm
FAQ's
http://http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.ficoexpertonline.com/downloads/User%20ExitsWPedit.doc
http://www.easymarketplace.de/userexit.php
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
1. what is the defference between enhancement and user-exits?
http://www.sap-img.com/abap/difference-between-badi-and-user-exits.htm
Re: difference between user exits & customer exits
Some Questions ! Plz help...
http://searchsap.techtarget.com/expert/KnowledgebaseAnswer/0,289625,sid21_gci1190924_tax299358,00.html?bucket=ETA
2. Difference between CMOD and SMOD?
http://www.sap-img.com/abap/what-is-the-difference-between-smod-and-cmod.htm
http://www.sap-img.com/abap.htm
http://sap.ittoolbox.com/groups/technical-functional/sap-r3-dev/diff-between-cmod-and-smod-236095
http://sap.ittoolbox.com/groups/technical-functional/sap-r3-dev/diff-between-cmod-and-smod-236107
check these links..
http://www.sapgenie.com/abap/tips_and_tricks.htm
http://www.sap-img.com/abap/field-exits-smod-cmod-questions-and-answers.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
passing selet-option variable to subrouine...
Finding the user-exits of a SAP transaction code
Finding the user-exits of a SAP transaction code
Enter the transaction code in which you are looking for the user-exit
and it will list you the list of user-exits in the transaction code.
Also a drill down is possible which will help you to branch to SMOD.
Written by : SAP Basis, ABAP Programming and Other IMG Stuff
             http://www.sap-img.com/*
report zuserexit no standard page heading.
tables : tstc, tadir, modsapt, modact, trdir, tfdir, enlfdir.
         tables : tstct.
data : jtab like tadir occurs 0 with header line.
data : field1(30).
data : v_devclass like tadir-devclass.
parameters : p_tcode like tstc-tcode obligatory.
select single * from tstc where tcode eq p_tcode.
if sy-subrc eq 0.
   select single * from tadir where pgmid = 'R3TR'
                    and object = 'PROG'
                    and obj_name = tstc-pgmna.
   move : tadir-devclass to v_devclass.
      if sy-subrc ne 0.
         select single * from trdir where name = tstc-pgmna.
         if trdir-subc eq 'F'.
            select single * from tfdir where pname = tstc-pgmna.
            select single * from enlfdir where funcname =
            tfdir-funcname.
            select single * from tadir where pgmid = 'R3TR'
                               and object = 'FUGR'
                               and obj_name eq enlfdir-area.
            move : tadir-devclass to v_devclass.
          endif.
       endif.
       select * from tadir into table jtab
                     where pgmid = 'R3TR'
                       and object = 'SMOD'
                       and devclass = v_devclass.
        select single * from tstct where sprsl eq sy-langu and
                                         tcode eq p_tcode.
        format color col_positive intensified off.
        write:/(19) 'Transaction Code - ',
             20(20) p_tcode,
             45(50) tstct-ttext.
                    skip.
        if not jtab[] is initial.
           write:/(95) sy-uline.
           format color col_heading intensified on.
           write:/1 sy-vline,
                  2 'Exit Name',
                 21 sy-vline ,
                 22 'Description',
                 95 sy-vline.
           write:/(95) sy-uline.
           loop at jtab.
              select single * from modsapt
                     where sprsl = sy-langu and
                            name = jtab-obj_name.
                   format color col_normal intensified off.
                   write:/1 sy-vline,
                          2 jtab-obj_name hotspot on,
                         21 sy-vline ,
                         22 modsapt-modtext,
                         95 sy-vline.
           endloop.
           write:/(95) sy-uline.
           describe table jtab.
           skip.
           format color col_total intensified on.
           write:/ 'No of Exits:' , sy-tfill.
        else.
           format color col_negative intensified on.
           write:/(95) 'No User Exit exists'.
        endif.
      else.
          format color col_negative intensified on.
          write:/(95) 'Transaction Code Does Not Exist'.
      endif.
at line-selection.
   get cursor field field1.
   check field1(4) eq 'JTAB'.
   set parameter id 'MON' field sy-lisel+1(10).
   call transaction 'SMOD' and skip first   screen.
*---End of Program
if u want to find the function exit
then check the below code
REPORT ZV_FIND_EXIT NO STANDARD PAGE HEADING.
TABLES : TSTC, TADIR, MODSAPT, MODACT, TRDIR, TFDIR, ENLFDIR.
TABLES : TSTCT.
DATA : JTAB LIKE TADIR OCCURS 0 WITH HEADER LINE.
DATA : FIELD1(30).
DATA : V_DEVCLASS LIKE TADIR-DEVCLASS.
PARAMETERS : P_TCODE LIKE TSTC-TCODE OBLIGATORY.
SELECT SINGLE * FROM TSTC WHERE TCODE EQ P_TCODE.
IF SY-SUBRC EQ 0.
SELECT SINGLE * FROM TADIR WHERE PGMID = 'R3TR'
AND OBJECT = 'PROG'
AND OBJ_NAME = TSTC-PGMNA.
MOVE : TADIR-DEVCLASS TO V_DEVCLASS.
IF SY-SUBRC NE 0.
SELECT SINGLE * FROM TRDIR WHERE NAME = TSTC-PGMNA.
IF TRDIR-SUBC EQ 'F'.
SELECT SINGLE * FROM TFDIR WHERE PNAME = TSTC-PGMNA.
SELECT SINGLE * FROM ENLFDIR WHERE FUNCNAME =
TFDIR-FUNCNAME.
SELECT SINGLE * FROM TADIR WHERE PGMID = 'R3TR'
AND OBJECT = 'FUGR'
AND OBJ_NAME EQ ENLFDIR-AREA.
MOVE : TADIR-DEVCLASS TO V_DEVCLASS.
ENDIF.
ENDIF.
SELECT * FROM TADIR INTO TABLE JTAB
WHERE PGMID = 'R3TR'
AND OBJECT = 'SMOD'
AND DEVCLASS = V_DEVCLASS.
SELECT SINGLE * FROM TSTCT WHERE SPRSL EQ SY-LANGU AND
TCODE EQ P_TCODE.
FORMAT COLOR COL_POSITIVE INTENSIFIED OFF.
WRITE:/(19) 'Transaction Code - ',
20(20) P_TCODE,
45(50) TSTCT-TTEXT.
SKIP.
IF NOT JTAB[] IS INITIAL.
WRITE:/(95) SY-ULINE.
FORMAT COLOR COL_HEADING INTENSIFIED ON.
WRITE:/1 SY-VLINE,
2 'Exit Name',
21 SY-VLINE ,
22 'Description',
95 SY-VLINE.
WRITE:/(95) SY-ULINE.
LOOP AT JTAB.
SELECT SINGLE * FROM MODSAPT
WHERE SPRSL = SY-LANGU AND
NAME = JTAB-OBJ_NAME.
FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
WRITE:/1 SY-VLINE,
2 JTAB-OBJ_NAME HOTSPOT ON,
21 SY-VLINE ,
22 MODSAPT-MODTEXT,
95 SY-VLINE.
ENDLOOP.
WRITE:/(95) SY-ULINE.
DESCRIBE TABLE JTAB.
SKIP.
FORMAT COLOR COL_TOTAL INTENSIFIED ON.
WRITE:/ 'No of Exits:' , SY-TFILL.
ELSE.
FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
WRITE:/(95) 'No User Exit exists'.
ENDIF.
ELSE.
FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
WRITE:/(95) 'Transaction Code Does Not Exist'.
ENDIF.
AT LINE-SELECTION.
GET CURSOR FIELD FIELD1.
CHECK FIELD1(4) EQ 'JTAB'.
SET PARAMETER ID 'MON' FIELD SY-LISEL+1(10).
CALL TRANSACTION 'SMOD' AND SKIP FIRST SCREEN.
or
1. in se11, goto table MODSAP
View table contents
2. in Type field, enter 'E' (for function exit)
3. For that tcode, u should know the program name.
eg. SAPLLMOB
4. then type SAPLLMOB and execute
or
REPORT z34331_user_exit .
TABLES : tstc, "SAP Transaction Codes
tadir, "Directory of Repository Objects
modsapt, "SAP Enhancements - Short Texts
modact, "Modifications
trdir, "System table TRDIR
tfdir, "Function Module
enlfdir, "Additional Attributes for Function Modules
tstct. "Transaction Code Texts
DATA : jtab LIKE tadir OCCURS 0 WITH HEADER LINE.
DATA : field1(30).
DATA : v_devclass LIKE tadir-devclass.
SELECTION-SCREEN BEGIN OF BLOCK a01 WITH FRAME TITLE text-001.
SELECTION-SCREEN SKIP.
PARAMETERS : p_tcode LIKE tstc-tcode OBLIGATORY.
SELECTION-SCREEN SKIP.
SELECTION-SCREEN END OF BLOCK a01.
START-OF-SELECTION.
Validate Transaction Code
SELECT SINGLE * FROM tstc
WHERE tcode EQ p_tcode.
Find Repository Objects for transaction code
IF sy-subrc EQ 0.
SELECT SINGLE * FROM tadir
WHERE pgmid = 'R3TR'
AND object = 'PROG'
AND obj_name = tstc-pgmna.
MOVE : tadir-devclass TO v_devclass.
IF sy-subrc NE 0.
SELECT SINGLE * FROM trdir
WHERE name = tstc-pgmna.
IF trdir-subc EQ 'F'.
SELECT SINGLE * FROM tfdir
WHERE pname = tstc-pgmna.
SELECT SINGLE * FROM enlfdir
WHERE funcname = tfdir-funcname.
SELECT SINGLE * FROM tadir
WHERE pgmid = 'R3TR'
AND object = 'FUGR'
AND obj_name = enlfdir-area.
MOVE : tadir-devclass TO v_devclass.
ENDIF.
ENDIF.
Find SAP Modifactions
SELECT * FROM tadir
INTO TABLE jtab
WHERE pgmid = 'R3TR'
AND object = 'SMOD'
AND devclass = v_devclass.
SELECT SINGLE * FROM tstct
WHERE sprsl EQ sy-langu
AND tcode EQ p_tcode.
FORMAT COLOR COL_POSITIVE INTENSIFIED OFF.
WRITE:/(19) 'Transaction Code - ',
20(20) p_tcode,
45(50) tstct-ttext.
SKIP.
IF NOT jtab[] IS INITIAL.
WRITE:/(95) sy-uline.
FORMAT COLOR COL_HEADING INTENSIFIED ON.
WRITE:/1 sy-vline,
2 'Exit Name',
21 sy-vline ,
22 'Description',
95 sy-vline.
WRITE:/(95) sy-uline.
LOOP AT jtab.
SELECT SINGLE * FROM modsapt
WHERE sprsl = sy-langu AND
name = jtab-obj_name.
FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
WRITE:/1 sy-vline,
2 jtab-obj_name HOTSPOT ON,
21 sy-vline ,
22 modsapt-modtext,
95 sy-vline.
ENDLOOP.
WRITE:/(95) sy-uline.
DESCRIBE TABLE jtab.
SKIP.
FORMAT COLOR COL_TOTAL INTENSIFIED ON.
WRITE:/ 'No of Exits:' , sy-tfill.
ELSE.
FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
WRITE:/(95) 'No User Exit exists'.
ENDIF.
ELSE.
FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
WRITE:/(95) 'Transaction Code Does Not Exist'.
ENDIF.
Take the user to SMOD for the Exit that was selected.
AT LINE-SELECTION.
GET CURSOR FIELD field1.
CHECK field1(4) EQ 'JTAB'.
SET PARAMETER ID 'MON' FIELD sy-lisel+1(10).
CALL TRANSACTION 'SMOD' AND SKIP FIRST SCREEN.
Regards,
Naveen

Where can I find the BADI

Hi Gurus,
i am new to concept of BADI. Can any one present application/Use of BADI with an example . Can anyone tell me in which table or under which Tcode can I find the list of abailable BADI's ?
Regards,
NewAbaper

Hi Abaper user,
This will give the clear idea about the badi.
Go through this info.
just run this report u get badi
REPORT ZNEGI16 .
TABLES : TSTC,
TADIR,
MODSAPT,
MODACT,
TRDIR,
TFDIR,
ENLFDIR,
SXS_ATTRT ,
TSTCT.
DATA : JTAB LIKE TADIR OCCURS 0 WITH HEADER LINE.
DATA : FIELD1(30).
DATA : V_DEVCLASS LIKE TADIR-DEVCLASS.
PARAMETERS : P_TCODE LIKE TSTC-TCODE,
P_PGMNA LIKE TSTC-PGMNA .
DATA wa_tadir type tadir.
START-OF-SELECTION.
IF NOT P_TCODE IS INITIAL.
SELECT SINGLE * FROM TSTC WHERE TCODE EQ P_TCODE.
ELSEIF NOT P_PGMNA IS INITIAL.
TSTC-PGMNA = P_PGMNA.
ENDIF.
IF SY-SUBRC EQ 0.
SELECT SINGLE * FROM TADIR
WHERE PGMID = 'R3TR'
AND OBJECT = 'PROG'
AND OBJ_NAME = TSTC-PGMNA.
MOVE : TADIR-DEVCLASS TO V_DEVCLASS.
IF SY-SUBRC NE 0.
SELECT SINGLE * FROM TRDIR
WHERE NAME = TSTC-PGMNA.
IF TRDIR-SUBC EQ 'F'.
SELECT SINGLE * FROM TFDIR
WHERE PNAME = TSTC-PGMNA.
SELECT SINGLE * FROM ENLFDIR
WHERE FUNCNAME = TFDIR-FUNCNAME.
SELECT SINGLE * FROM TADIR
WHERE PGMID = 'R3TR'
AND OBJECT = 'FUGR'
AND OBJ_NAME EQ ENLFDIR-AREA.
MOVE : TADIR-DEVCLASS TO V_DEVCLASS.
ENDIF.
ENDIF.
SELECT * FROM TADIR INTO TABLE JTAB
WHERE PGMID = 'R3TR'
AND OBJECT in ('SMOD', 'SXSD')
AND DEVCLASS = V_DEVCLASS.
SELECT SINGLE * FROM TSTCT
WHERE SPRSL EQ SY-LANGU
AND TCODE EQ P_TCODE.
FORMAT COLOR COL_POSITIVE INTENSIFIED OFF.
WRITE:/(19) 'Transaction Code - ',
20(20) P_TCODE,
45(50) TSTCT-TTEXT.
SKIP.
IF NOT JTAB[] IS INITIAL.
WRITE:/(105) SY-ULINE.
FORMAT COLOR COL_HEADING INTENSIFIED ON.
Sorting the internal Table
sort jtab by OBJECT.
data : wf_txt(60) type c,
wf_smod type i ,
wf_badi type i ,
wf_object2(30) type C.
clear : wf_smod, wf_badi , wf_object2.
Get the total SMOD.
LOOP AT JTAB into wa_tadir.
at first.
FORMAT COLOR COL_HEADING INTENSIFIED ON.
WRITE:/1 SY-VLINE,
2 'Enhancement/ Business Add-in',
41 SY-VLINE ,
42 'Description',
105 SY-VLINE.
WRITE:/(105) SY-ULINE.
endat.
clear wf_txt.
at new object.
if wa_tadir-object = 'SMOD'.
wf_object2 = 'Enhancement' .
elseif wa_tadir-object = 'SXSD'.
wf_object2 = ' Business Add-in'.
endif.
FORMAT COLOR COL_GROUP INTENSIFIED ON.
WRITE:/1 SY-VLINE,
2 wf_object2,
105 SY-VLINE.
endat.
case wa_tadir-object.
when 'SMOD'.
wf_smod = wf_smod + 1.
SELECT SINGLE MODTEXT into wf_txt
FROM MODSAPT
WHERE SPRSL = SY-LANGU
AND NAME = wa_tadir-OBJ_NAME.
FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
when 'SXSD'.
For BADis
wf_badi = wf_badi + 1 .
select single TEXT into wf_txt
from SXS_ATTRT
where sprsl = sy-langu
and EXIT_NAME = wa_tadir-OBJ_NAME.
FORMAT COLOR COL_NORMAL INTENSIFIED ON.
endcase.
WRITE:/1 SY-VLINE,
2 wa_tadir-OBJ_NAME hotspot on,
41 SY-VLINE ,
42 wf_txt,
105 SY-VLINE.
AT END OF object.
write : /(105) sy-ULINE.
ENDAT.
ENDLOOP.
WRITE:/(105) SY-ULINE.
SKIP.
FORMAT COLOR COL_TOTAL INTENSIFIED ON.
WRITE:/ 'No.of Exits:' , wf_smod.
WRITE:/ 'No.of BADis:' , wf_badi.
ELSE.
FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
WRITE:/(105) 'No userexits or BADis exist'.
ENDIF.
ELSE.
FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
WRITE:/(105) 'Transaction does not exist'.
ENDIF.
AT LINE-SELECTION.
data : wf_object type tadir-object.
clear wf_object.
GET CURSOR FIELD FIELD1.
CHECK FIELD1(8) EQ 'WA_TADIR'.
read table jtab with key obj_name = sy-lisel+1(20).
move jtab-object to wf_object.
case wf_object.
when 'SMOD'.
SET PARAMETER ID 'MON' FIELD SY-LISEL+1(10).
CALL TRANSACTION 'SMOD' AND SKIP FIRST SCREEN.
when 'SXSD'.
SET PARAMETER ID 'EXN' FIELD SY-LISEL+1(20).
CALL TRANSACTION 'SE18' AND SKIP FIRST SCREEN.
DEFINING THE BADI
1) execute Tcode SE18.
2) Specify a definition Name : ZBADI_SPFLI
3) Press create
4) Choose the attribute tab. Specify short desc for badi.. and specify the type :
multiple use.
5) Choose the interface tab
6) Specify interface name: ZIF_EX_BADI_SPFLI and save.
7) Dbl clk on interface name to start class builder . specify a method name (name,
level, desc).
Method level desc
Linese;ection instance methos some desc
8) place the cursor on the method name desc its parameters to define the interface.
Parameter type refe field desc
I_carrid import spfli-carrid some
I_connid import spefi-connid some
9) save , check and activateadapter class proposed by system is
ZCL_IM_IM_LINESEL is genereated.
IMPLEMENTATION OF BADI DEFINITION
1) EXECUTE tcode se18.choose menuitem create from the implementation menubar.
2) Specify aname for implementation ZIM_LINESEL
3) Specify short desc.
4) Choose interface tab. System proposes a name fo the implementation class.
ZCL_IM_IMLINESEL which is already generarted.
5) Specify short desc for method
6) Dbl clk on method to insert code..(check the code in AAA).
7) Save , check and activate the code.
Some useful URL
http://www.esnips.com/doc/e06e4171-29df-462f-b857-54fac19a9d8e/ppt-on-badis.ppt
http://www.esnips.com/doc/10016c34-55a7-4b13-8f5f-bf720422d265/BADIs.pdf
http://www.esnips.com/doc/43a58f51-5d92-4213-913a-de05e9faac0d/Business-Addin.doc
http://www.esnips.com/doc/1e10392e-64d8-4181-b2a5-5f04d8f87839/badi.doc
www.sapgenie.com/publications/saptips/022006%20-%20Zaidi%20BADI.pdf
http://www.sapdevelopment.co.uk/enhance/enhance_badi.htm
http://help.sap.com/saphelp_nw04/helpdata/en/04/f3683c05ea4464e10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/e6/d54d3c596f0b26e10000000a11402f/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/c2/eab541c5b63031e10000000a155106/frameset.htm
Now write a sample program to use this badi method..
Look for BBB sample program.
AAA
data : wa_flights type sflight,
it_flights type table of sflight.
format color col_heading.
write:/ 'Flight info of:', i_carrid, i_connid.
format color col_normal.
select * from sflight
into corresponding fields of table it_flights
where carrid = i_carrid
and connid = i_connid.
loop at it_flights into wa_flights.
write:/ wa_flights-fldate,
wa_flights-planetype,
wa_flights-price currency wa_flights-currency,
wa_flights-seatsmax,
wa_flights-seatsocc.
endloop.
BBB
*& Report ZBADI_TEST *
REPORT ZBADI_TEST .
tables: spfli.
data: wa_spfli type spfli,
it_spfli type table of spfli with key carrid connid.
*Initialise the object of the interface.
data: exit_ref type ref to ZCL_IM_IM_LINESEL,
exit_ref1 type ref to ZIF_EX_BADISPFLI1.
selection-screen begin of block b1.
select-options: s_carr for spfli-carrid.
selection-screen end of block b1.
start-of-selection.
select * from spfli into corresponding fields of table it_spfli
where carrid in s_carr.
end-of-selection.
loop at it_spfli into wa_spfli.
write:/ wa_spfli-carrid,
wa_spfli-connid,
wa_spfli-cityfrom,
wa_spfli-deptime,
wa_spfli-arrtime.
hide: wa_spfli-carrid, wa_spfli-connid.
endloop.
at line-selection.
check not wa_spfli-carrid is initial.
create object exit_ref.
exit_ref1 = exit_ref.
call method exit_ref1->lineselection
EXPORTING
i_carrid = wa_spfli-carrid
i_connid = wa_spfli-connid.
clear wa_spfli.
Rewards somw points if it is helpful,
P.Nag
Rgds,

How can i find the fields for &DOPOS_CPY-WRBT1(I13.0)&

Hi All,
In sapscripts, what is the meaning for (13.0)?
how can i find the fields for &DOPOS_CPY-WRBT1(I13.0)&?
Thanks.

meaning for (13.0) is write to form this variable's 13 character non decimal and 0 character decimal places.
shortly not write decimal places.
DOPOS_CPY-WRBT1 is exist in form caller program. check in abap program not in sapscript.
take care
Çağatay

In which tables can I find the sd texts in the material register?

Hi,
In which tables can I find the sd texts in the material register?
Thanks.

Hi,
The texts are stored in tables STXH , STXL etc. But it is not possible to fetch the details directly from the tables. You have to use the function module READ_TEXT where you have pass the parameters Text ID, Language, object as material number etc to fetch the text.
You can take the help of an ABAPer to create a program for this.

Can't find the adapters in communication channel

Hi
I can't find the adapters in communication channel , on hunting the sdn i could find the below soln :
To rectify this you must import the BASIS SWCV 7.0 into the Integration repository.
can any body give me step by step for importing in the integration repository.
rgds
shazia

Hi,
First do SLDCHECK in XI ABAP Stack, then if it has errors means follow this help file
http://help.sap.com/saphelp_nw04s/helpdata/en/78/20244134a56532e10000000a1550b0/frameset.htm
If SLDCHECK is working fine means,
Try to re-import the BASIS SWC into IR againg, then only you will be able to see the list of adapters in the list..
Regards
Seshagiri

How can I find the reference field of components ?

Hi everyone ;
I am a Junior Abap Developer. I am creating a structure that I will use in the report program. When I create a structure , some of the components needs to get reference field.Ex: NETWR,BTGEW,KWMENG. How can i find the reference field of component?

Hi,
You have to put entries for currencies and quantity fields for these fields,
Like for NETWR reference table is VBAK and field is WAERK,
for other Quantity field you can use MEINS as reference field.
You can check the reference table and reference fields in the respective tables( i.e. VBAP here).
Thanks,
Anmol.

Where can I find the the list of transactions for ESS screens?

I want to test an ESS functionality in the SAP GUI. Where can I find the transactions for these screens? Is there such a table where these tcodes are stored?
I believe you can test the ESS screens through inputting the tcode in SE93.
Thanks! Any help will be appreciated.
Points will be awarded.
Olekan Babatonde

Bala? Do you even bother to read the original posts/questions?!?! That is soooooo far off and WRONG.
@Clueless
What version backend are you on? For the most part, you can look at it like this....
For ITS based services....each ITS service will be tied to a transaction. You can find this by looking in the "service" file for the interent service (ie. double click on the top folder shown for the service and it will show you the service parameters in the rigth hand content area in t-code SE80). Most (but not all) can be found that way. Also, if you are on ECC5 or ECC6, you can look in t-code SICF at the individual services to find the parameters there as well (a little more navigation required).
For Java Webdynpro and ABAP Webdynpro ESS services, however, you will not really have a transaction so to speak. They communicte primarily through classes and BAPIs. Nothing there for you to find in SE93.
Hope this helps.

Where can i find the theory for session and call transaction method

hi
where can i find the theory for session and call transaction method
bye

check this link
http://www.sap-img.com/abap/learning-bdc-programming.htm
http://www.planetsap.com/bdc_main_page.htm
lsmw, bapi, bdc- session, bdc-calltransaction
u can get it in help.sap.com also

How can i find the printing program?

hi
i have sap script how can i find the printing program ?
ami

ami bardogo wrote:
hi
what is the different between the commands 'break' and 'break-point'
thanks,
ami
h2 Breakpoints h2
Apart from being able to execute an ABAP program in the Debugger, you can also start the Debugger call by the choosing a breakpoint. This is achieved by setting one or more of these breakpoints in the program. A breakpoint is a signal at a particular point in the program that tells the ABAP runtime processor to interrupt processing and start the Debugger. The Debugger is activated when the program reaches this point.
There is also a special kind of breakpoint called a watchpoint. When you use watchpoints, the Debugger is not activated until the contents of a particular field change. For more information, refer to the chapter Watchpoints.
Breakpoint Variants
The Debugger contains different breakpoint variants:
Static
A user-specific breakpoint is inserted in the source code as an ABAP statement using the keyword BREAK-POINT. A non user-specific breakpoint is set in the ABAP Editor using the BREAK user name statement.
Directly set
dynamic breakpoints
Can be set in the ABAP Editor or the Debugger by double-clicking a line, for example. Dynamic breakpoints are always user-specific, and are deleted when you log off from the R/3 System.
Breakpoints
at statements
The Debugger stops the program immediately before the specified statement is executed.
Breakpoints
at subroutines
The Debugger stops the program immediately before the specified subroutine is called.
Breakpoints at function modules
The Debugger stops the program immediately before the specified function module is called.
Breakpoints at methods
The Debugger stops the program immediately before the specified method is called.
Breakpoints at exceptions and system exceptions
The Debugger stops the program immediately after a system exception, that is, after a runtime error has been intercepted.
Static Breakpoints
Static breakpoints are always user-independent if there is no specification of a user name. Once a user has inserted the statement BREAK-POINT or BREAK name in an ABAP program, the system always interrupts the program at that point for that user or only for the user name. This procedure is only useful in the development phase of an application when program execution is always to be interrupted at the same place. For more information, refer to the chapter Static Breakpoints.
In HTTP sessions, a static breakpoint is skipped if you did not set additional dynamic HTTP breakpoints in the editor of a BSP page. Instead, a corresponding system log entry is written, which can be checked using transaction SM21.
Dynamic Breakpoints
Dynamic breakpoints are user-specific. Therefore, you should use them if you only want the program to be interrupted when you run it yourself, not when it is being executed by other users. All dynamic breakpoints are deleted when you log off from the R/3 System.
Dynamic breakpoints are more flexible than static breakpoints because you can deactivate or delete them at runtime. They have the following advantages:
·        You do not have to change the program code.
·        You can set them even when the program is locked by another programmer.
·        You can define a counter that only activates the breakpoint after it has been reached.
Special dynamic breakpoints are useful when you want to interrupt a program directly before a particular ABAP statement, a subroutine, or an event, but do not know exactly where to find it in the source code. Event here is used to refer to the occurrence of a particular statement, for example, or calling up a method. Special dynamic breakpoints are user-specific. You can only set them in the Debugger. For more information, refer to the chapter Dynamic Breakpoints.
In HTTP sessions, the system stops both at static and dynamic breakpoints if a dynamic breakpoint was set in the editor of a BSP page before program execution.
Lifetime and Transfer of Breakpoints
A static breakpoint remains intact as long as the BREAK-POINT or BREAK-POINT name statement is not removed from the source code. Without saving, dynamic breakpoints only remain intact in the relevant internal session. However, they remain in effect during the entire user session if they are saved by choosing the menu path Breakpoints ® Save in the ABAP Debugger. For more details on the subject of user sessions and modes, refer to Modularization Techniques in the ABAP keyword documentation.
If you call an HTTP session during a user session, only the HTTP breakpoints are loaded when the HTTP session is started. You activate HTTP debugging in the ABAP Editor by choosing Utilities ® Settings ® HTTP Debugging. Depending on the setting, the system then displays either the HTTP or standard breakpoints in the Editor.
If you call an update session during a user session, breakpoints that were defined beforehand in the calling processing unit are copied to the new update session, where they can be displayed under Breakpoints. If, in the ABAP Debugger, you check Update Debugging under Settings and then, for example, call the update module func using CALL FUNCTION func IN UPDATE TASK, a new window is opened in which you can debug this function module in the update session. All the breakpoints that were set in the calling processing unit can also be processed here.
For further information on special breakpoints, refer to:
Breakpoints at Statements
Breakpoints at Subroutines
Breakpoints at Function Module Calls
Breakpoints at Methods
Breakpoints at System Exceptions
h2 page break h2
WINDOW TYPES
When defining a layout set window, you must select a window type for the window. You can choose between three types:
Constant windows (CONST)
Variable windows (VAR)
Main windows (MAIN)
CONSTANT WINDOW
A window of type CONST has the same contents and size on all layout set pages, on which a corresponding page window is defined. This allows the processing of the window contents to be optimized internally.
Page windows whose allocated window is of type CONST must have the same size throughout the layout set. If a window of type CONST is full, all remaining text the application program wants to output in this window, is lost. Constant windows do not trigger a page break. In other words: all text exceeding the window size is simply truncated.
VARIABLE WINDOW
The contents of variable windows is processed again for each page, on which the window appears. The system outputs only as much text as fits into the window. Text exceeding the window size is truncated; the system does not trigger a page break. Unlike constant windows, the page windows declared as variable windows may have different sizes on different layout set pages.
As far as the processing of the window contents is concerned, the system currently treats constant and variable windows alike. The only difference is that constant windows have the same size throughout the layout set.
MAIN WINDOW
Each layout set must have one window of type MAIN. Such a window is called the main window of the layout set. For SAPscript layout sets, the main window has a central meaning:
It controls the page break.
It contains the text body that may cover several pages.
It allows to fix text elements at the upper and lower margins of the allocated page window (for example, for column headings).
As soon as a window of type MAIN is full, SAPscript automatically triggers a page break and continues to output the remaining text in the main window of the subsequent page. Page windows of type MAIN have the same width throughout the layout set. The SAPscript composer thus avoids reformatting of the text after each page break.
If a page does not have a main window, the system implicitly processes all other windows of the page and continues with the subsequent page. This page must not call itself as subsequent page (recursive call), since this would produce an endless loop. In such a case, SAPscript terminates the output after three subsequent pages.
HOW THE COMPOSER WORKS
The composer or layout set processor is the central formatting module for the print output. It prepares the texts for the different output devices by using the allocated styles or layout sets.
Processing a layout set happens in a certain order. You must know some facts concerning the different window types, the setting of subsequent pages, or the dynamic control from within the print program.
Page control in layout sets
Define subsequent page statically
Define subsequent page dynamically
Format a layout set page
PAGE CONTROL IN LAYOUT SETS
SAPscript automatically triggers a page break as soon as the main window of one page is full. To be able to execute the page break, the system must know on which subsequent page to continue outputting the text. You can specify the subsequent page either statically when defining the layout set, or you can set the subsequent page dynamically during layout set output.
If the subsequent page is not specified, SAPscript automatically terminates printing, thereby ignoring any other output statements of the application program.
DEFINE SUBSEQUENT PAGE STATICALLY
You define the subsequent page statically with the layout set maintenance transaction. First, specify the start page in the layout set header. The system automatically calls this page whenever the layout set is started. With this page, or, more correctly, with the page window of this page, the text output starts. For each page, specify the subsequent page in the page definition. After a page break, the system continues text output on the subsequent page defined for the last page. By specifying start page and subsequent pages, you can define a page sequence.
DEFINE SUBSEQUENT PAGE DYNAMICALLY
The page sequence set in the layout set definition can be changed by the application program dynamically at runtime. If you want the layout set to start with a page other than the one defined in the layout set header, specify the desired start page using the parameter STARTPAGE when you call the function module START_FORM. However, this new start page is valid only for the current call of the function module.
If you want to break to a subsequent page other than the one specified in the page definition, use the control statement NEW-PAGE to set the name of the new page.
NEW-PAGE .
NEW-PAGE ends the output on the current page. The new subsequent page is only valid for the current call of the control statement. You can either include the control statement explicitly into the text of a text element or pass it to the layout set output using the function module CONTROL_FORM.
FORMAT LAYOUT SET PAGE
The process of formatting the output is controlled by the text contents in the BODY area of the main window. If the main window is completely filled, or if the control statement NEW-PAGE appears in the main window, the system executes a page break. Only at this point in time the system formats the contents of the windows of the other types and replaces the variables with the current values.
For each other window, the system first outputs the default text element, if it exists. Then it processes and formats the list of the active text elements of this window, which you set using the function module WRITE_FORM with the parameter FUNCTION (SET, APPEND, DELETE). Any text that does not fit into the page window is truncated.
As a consequence to this processing order of the composer, the reservation of space for the TOP and BOTTOM areas must be made beforehand. If the BODY area of the main window already contains text, a new text output to the TOP area does not appear on the current page but on the subsequent page in the TOP area. The same applies for the BOTTOM area. If the BODY area is filled to such an extend that the new BOTTOM text no longer fits into the current main window, this text appears on the subsequent page in the BOTTOM area.
A frequent error in application programs is that for the subsequent page (for example, NEXT) of a layout set no main window is defined. If the formatted text of the previous page did not fit into the corresponding main window , the composer searches the subsequent pages for a main window to output the text remainder. However, if the subsequent page of NEXT is NEXT again, the composer encounters an endless loop.
To be able to create correct page breaks in longer text, you should define a main window on each layout set page.
LAYOUT SET CONTROL
To output SAPscript layout sets, in the print program you must always start the output with OPEN_FORM and end it with CLOSE_FORM. The function module OPEN_FORM initializes the SAPscript composer and opens the specified layout set for subsequent output. The system combines all output for this layout set up to the CLOSE_FORM to one print request. If CLOSE_FORM is missing, nothing will be printed.
To output data in a layout set, you must use the SAPscript function modules WRITE_FORM, WRITE_FORM_LINES, and CONTROL_FORM. You can use these function modules any number of times in any order between opening and closing a layout set.
You cannot use the ABAP/4 statement WRITE to write output to a SAPscript layout set.
Several print requests
Start a layout set again
Switch layout sets
Find layout sets
SEVERAL PRINT REQUESTS
Within one transaction, you can open and close several layout sets using OPEN_FORM and CLOSE_FORM, however not simultaneously. You can use parameters in the OPEN_FORM to control whether the output is stored in the same print request. But also the SAP spool decides, depending on several plausibility checks, whether new output is appended to an existing print request or whether to create a new print request anyway.
CALL FUNCTION 'OPEN_FORM'
CALL FUNCTION 'CLOSE_FORM'
CALL FUNCTION 'OPEN_FORM'
CALL FUNCTION 'CLOSE_FORM'
You cannot combine ABAP/4 list output and SAPscript output in one print request.
START A LAYOUT SET AGAIN
Usually a print program does not print only one urging letter or one account statement, but several layout sets for different customers. To have the output for each customer begin with the start page of the layout set, you must start the current layout set again and again.
To start a layout set again, you must first end the current layout set and then open the layout set again. Within one print request, first call the function module END_FORM. It executes the final processing for the current layout set. Then start the layout set again using START_FORM. Output then begins again on the start page of the desired layout set.
CALL FUNCTION 'OPEN_FORM'
CALL FUNCTION 'START_FORM'
CALL FUNCTION 'END_FORM'
CALL FUNCTION 'START_FORM'
CALL FUNCTION 'END_FORM'
CALL FUNCTION CLOSE_FORM
If you use START_FORM and END_FORM, you must not specify a layout set for OPEN_FORM. However, in this case you can use the SAPscript output functions only after opening a layout set with START_FORM.

I have bought a film from itunes and the credit has come out of my account, but i can't find the film anywhere, it said it was downloading, then i left the laptop and on return i couldn't find the film. how do i find the film?

i have bought a film from itunes and the credit has come out of my account, but i can't find the film anywhere, it said it was downloading, then i left the laptop and on return i couldn't find the film. how do i find the film?

Maybe it is in the Purchased category of iTunes,
Try going there

My external hard drive is 'seen' by my iMac and I can go into the Finder and open files and folders. I am using the hard drive for Time Machine back up. However Time Machine says it can't find the drive. Same thing has happened with Final Cut Express.

My new LaCie external hard drive is 'seen' by my iMac and I can go into the Finder and open files and folders. I am using the hard drive for Time Machine back up. However Time Machine says it can't find the drive.
The same thing happened recently between Final Cut Express and my other LaCie external hard drive used as the Scratch disk. It fixed itself.
I've run out of ideas. Help would be very much appreciated. Thanks.

have you done some searches on FCPx and time machine? Is there a known issue with using a TM drive with FCPx? dunno but ...wait...I'll take 60 sec for you cause I'm just that kind of guy.... google...." fcpx time machine problem" Frist page link
http://www.premiumbeat.com/blog/fcpx-bug-best-practices-for-using-external-hard- drives-and-final-cut-pro-x/
You cannot have time machine backups on your hard drive if you intend to use it in FCPX.
booya!

Fire Fox sent not all the data in text form. Reached only piece of information. Where can I find the cache of sent text?

Fire Fox sent not all the data in text form. Reached only piece of information. Where can I find the cache sent the text?
For example, I posted an article on a news site, but found that only a small part of my article was posted.

I'm not sure whether Firefox saved that information. There is a chance that it is in the session history file, especially if you haven't closed that tab yet. To check that:
Open your currently active Firefox settings folder (AKA your Firefox profile folder) using
Help > Troubleshooting Information > "Show Folder" button
Find all files starting with the name sessionstore and copy them to a safe working location (e.g., your documents folder). In order to read a .js file, it is useful to rename it to a .txt file. Or you could drag it to Wordpad or your favorite word processing software.
The script will look somewhat like gibberish, but if you search for a word in your article that doesn't normally appear in web pages, you may be able to find your data.
Any luck?
For the future, you might want to consider this add-on, although I don't know how long it saves data after you submit a form: [https://addons.mozilla.org/en-US/firefox/addon/lazarus-form-recovery/].

FPM ABAP: Can't find the hotkey?

Similar Messages

Maybe you are looking for