Wait upto one second v/s BAPI TRANSACTION COMMIT

Hi All,
I calling the FM BAPI_EQUI_CHANGE and then CALL FUNCTION 'BAPI_TRANSACTION_COMMIT 'EXPORTING wait = 'X'.
But it seems like in the production environment the commit does not happen immediately and happens only when I add a "wait upto one second" statement. I want to avoid the wait and also a bit confused on why the commit BAPI does not work quickly enough. PLease enlightenme on this.
Best REgards,
Shankar.

BAPI_TRANSACTION_COMMIT executes
- a COMMIT WORK, so it starts update task, if WAIT specified, it waits until task are ended, and execute a database commit (native SQL commit on database server)
- a buffer refresh of the BAPI tools only not of the whole database on server...
There can nevertheless be some delay due to database server even if database commit is required it may take time and Abap don't wait at this step, so even a WAIT UP TO n SECONDS can fail ( So [it will happen|http://en.wikipedia.org/wiki/Murphy%27s_law]). If you want to actually be sure that database is updated, you must execute a SELECT from database[ BYPASSING BUFFER|http://help.sap.com/abapdocu_70/en/ABAPFROM_CLAUSE.htm#&ABAP_ADDITION_3@3@] in a DO/ENDDO loop to insure data is created/updated (Of course put a limit at the number of tries performed)
Regards,
Raymond

Similar Messages

How to avoid Wait upto 5 seconds

Dear Friends,
I have used the below code for generating the spool by submitting the standard program.
CALL FUNCTION 'JOB_OPEN'
EXPORTING
jobname = lv_job_name
IMPORTING
jobcount = lv_job_nr
EXCEPTIONS
cant_create_job = 1
invalid_job_data = 2
jobname_missing = 3
OTHERS = 4.
IF sy-subrc EQ 0.
SUBMIT RPCEDTX0
TO SAP-SPOOL WITHOUT SPOOL DYNPRO
SPOOL PARAMETERS mstr_print_parms
USING SELECTION-SET 'ZPDF'
VIA JOB lv_job_name NUMBER lv_job_nr
AND RETURN.
IF sy-subrc = 0.
CALL FUNCTION 'JOB_CLOSE'
EXPORTING
jobcount = lv_job_nr
jobname = lv_job_name
strtimmed = 'X'
IMPORTING
job_was_released = lv_job_released
EXCEPTIONS
cant_start_immediate = 1
invalid_startdate = 2
jobname_missing = 3
job_close_failed = 4
job_nosteps = 5
job_notex = 6
lock_failed = 7
OTHERS = 8.
IF syst-subrc NE 0.
MESSAGE i162(00) WITH
'An error occured while closing the background job.'.
STOP.
ENDIF.
ENDIF.
   WAIT UP TO 5 SECONDS .
*get job details
    CALL FUNCTION 'GET_JOB_RUNTIME_INFO'
    IMPORTING
*eventid = gd_eventid
*eventparm = gd_eventparm
*external_program_active = gd_external_program_active
    jobcount = lv_job_nr " gd_jobcount
    jobname = lv_job_name "gd_jobname
*stepcount = gd_stepcount
    EXCEPTIONS
    no_runtime_info = 1
    OTHERS = 2.
* Get the spool number
    SELECT * FROM tbtcp
    INTO TABLE it_tbtcp
    WHERE jobname = lv_job_name   " gd_jobname
    AND jobcount = lv_job_nr    "gd_jobcount
*   AND stepcount = gd_stepcount
*   AND listident '0000000000'
    ORDER BY jobname
    jobcount.
*stepcount.
    IF sy-subrc = 0.
      READ TABLE it_tbtcp INTO wa_tbtcp INDEX 1.
      IF sy-subrc = 0.
        gd_spool_nr = wa_tbtcp-listident. "gd_spool_nr --> contains spool no.
      ENDIF.
    ENDIF.
    mi_rqident = gd_spool_nr .
*-- Convert Spool to PDF
    CALL FUNCTION 'CONVERT_ABAPSPOOLJOB_2_PDF'
      EXPORTING
        src_spoolid              = mi_rqident
        no_dialog                = space
        dst_device               = mstr_print_parms-pdest
      IMPORTING
        pdf_bytecount            = mi_bytecount
      TABLES
        pdf                      = mtab_pdf
      EXCEPTIONS
        err_no_abap_spooljob     = 1
        err_no_spooljob          = 2
        err_no_permission        = 3
        err_conv_not_possible    = 4
        err_bad_destdevice       = 5
        user_cancelled           = 6
        err_spoolerror           = 7
        err_temseerror           = 8
        err_btcjob_open_failed   = 9
        err_btcjob_submit_failed = 10
        err_btcjob_close_failed = 11
        OTHERS                   = 12.
Iam using in my program as    WAIT UP TO 5 SECONDS , i dont want to use this option as i wanted to use a better way other than this way to increase the performance , please could anyone let me know what i can do.
If iam not using the    WAIT UP TO 5 SECONDS then i found the spool no is not getting generated and there by iam getting an error as spool no found .
Please help me what is the better way of doing .
regards
divya
Formatted by: Vijay Babu Dudla on Apr 27, 2009 9:56 AM

Please use tags around source code in future postings.
Since you are using SUBMIT ... VIA JOB, control comes right back to your program and you don't know when the asynchronous job is finished and the spool data is available.
Do you need to schedule this as a job at all? If you use SUBMIT without VIA JOB, then control comes back when the called program is finished and you can read TSP01 right away (instead of TBTCP) to get the spool ID RQIDENT, using a unique RQ2NAME that you set in the SUBMIT ... LIST NAME ... addition.
Works for me
Thomas

BAPI Transaction commit in JCo

Hi,
I am posting a GL document via JCo (Java Program ) into SAP using the BAPI_ACC_DOCUMENT_POST and then calling the BAPI_TRANSACTION_COMMIT to commit the transaction so that it gets updated in SAP system.
After i execute my program, i get the posting successful message and document number is returned to me. But when i look for this document in the SAP system, it is not found.
Any help will be appreciated.
Below is the piece of code where i execute the BAPI's in java after mapping the required data.
                 function.execute(destination);
                 System.out.println("Function BAPI_ACC_DOCUMENT_POST executed .");
                 commFunct.getImportParameterList().setValue("WAIT", "10");
                 commFunct.execute(destination);
                 System.out.println("Function BAPI_TRANSACTION_COMMIT executed .");
Regards,
Ganesh.

Hi Ganesh,
With JCo3 the connections are no longer stateful by default, so each RFC call is executed within it's own context. In your case though, you want the commit to occur in the same context where you posted the document. You can do this by adding the following static method calls:
JCoContext.begin(destination);
// Execute both RFC functions here
JCoContext.end(destination);
You can also check the Java API help for JCoContext, which explains this in more detail. Once you added the two lines (ideally end the context in a finally block), you should see the document in SAP.
Cheers, harald

WAIT UP TO SECONDS.

Hi,
I use 'BAPI_PROCORD_COMPLETE_TECH' to TECO process order. However, the confirmation prompt it sends is sometimes not showing sometimes it's showing. It's weird.
I introduce WAIT UP TO 2 SECONDS after it commit the work.
What else do i need to do in order for the prompt to appear everytime there is a warning in the TECO? Do I have to extend the time? Thanks a lot!
Sample code is below:
Technically complete process Order
   CALL FUNCTION 'BAPI_PROCORD_COMPLETE_TECH'
     IMPORTING
       return = i_messages
     TABLES
       orders = i_orders.
   IF sy-subrc EQ 0.
     IF i_messages[] IS INITIAL.
       REFRESH i_messages3.
       CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
         EXPORTING
           wait   = ' '
         IMPORTING
           return = i_messages3.
       IF sy-subrc EQ 0.
         WAIT UP TO 2 SECONDS.
         CLEAR x_messages3.
         READ TABLE i_messages3 INTO x_messages3
                    WITH KEY type = c_error.
         IF sy-subrc EQ 0.
           MESSAGE i000 WITH x_messages3-message.
           EXIT.
         ELSE.
           MESSAGE i008.
         ENDIF.
       ENDIF.

Hi
First, If you use your BAPI call independently in your own custom program and you are sure the LUW is complete you don have to set the WAIT parameter (WAIT = ' ').
If you use your BAPI call within another program (standard/User-exit) then you should set the WAIT parameter (WAIT = 'X'). Seting the WAIT parameter will sinchronize the commit with the next commit work (set by standard program), using WAIT parameter in standard program especially in User-exit prevents data inconsistency caused by premature commit work.
Second , Are you checking the return table parameter for any errors? from the first fm? Please check it first. If it is having error then there is no problem.
Else put COMMIT WORK AND WAIT for the BAPI_transaction_COMMIT. Then in order to find wheter if it is a posting problem,
Just put the statement WAIT UPTO 2 SECONDS.
and try if there is some posting proble then the above WAIT will find it for you.
Have a nice day
Reward if useful
~Lakshmiraj~

HT201372 Both Mavericks and Yosemite stall at "One Second Remaining"

This has been a very disappointing experience and I am surprised that it came from Apple. My wife's old Macbook Pro's HDD completely died and so I am replacing it, reinstalling OSX and then putting back what files we could salvage.
I have now tried to create a USB installer for OS X Mavericks and Yosemite. When I tried the Yosemite installer the error log said it could not find a keychain related file and a decent hour after it said that only a second was remaining, the OS never installed.
Now I am trying Mavericks and the log gives many "Could not find package ref" errors and I am coming into an hour of waiting for "one second remaining" to finish and the install to work.
Seriously Apple? This one of the worst and most frustrating installations I have ever done - and that's been a wide range of operating systems in the past. The install program gives no human friendly error, no indication of what to do, no indication it will ever work. Most posts seem to say "just wait" ...
Just wait? How long is a user expected to wait for "about a second remaining" to last anyway?

At this point it looks like I will have to go to a Genius Bar just to installl OSX onto a Macbook Pro. I can't or order a buy a Mavericks or Yosemite install, my wife's HDD is too shot to make a USB installer and it doesn't look like my other laptop will do it (for whatever reason - of which neither Apple nor the installation software can properly report - which is idiotic).
Utterly ridiculous that I have two laptops, the Internet and multiple flash drives but there doesn't seem to be a way to make this work. Massive fail, Apple. Massive. Fail.

COMMIT WORK and WAIT FOR n SECONDS

I am designing a WebDynpro Java application. It makes an update call followed immediately by a display call which should return the data that was just updated. However, it appears that there is some DB latency involved and the data takes a few seconds to update. The application displays old data if the display call is performed too quickly after the update call.
All suggestions I could find point to having a Thread sleep on the Java side for a few seconds or have a WAIT FOR n SECONDS and/or COMMIT WORK AND WAIT statement in the ABAP function module. Neither of these solutions is acceptable in a company-wide application where database latency could vary significantly based on traffic.
I tried all kinds of functions (i.e. BAPI_TRANSACTION_COMMIT) as well as various forms of COMMIT WORK... nothing except a WAIT works correctly. There must be a statement out there that waits for the database write to be complete! How is this solved without picking an arbitrary WAIT time? What am I missing?
Thanks in advance!

You can write the other way.
declare one variable
data : wa_try type i.
wa_try = 10. -> set as 10 ,even you do not get value ,keep on incresing.
after BAPI FM
you can call comitt fm.
after BAPI_TRANSACTION_COMITT
just use simple logic.
do wa_try.
select * from table into table
where record = bapi fm record ( You get in RET2 Message).
if sy-subrc eq 0.
exit.
endif.
Thanks
Seshu

Your computer restarted because of a problem. Press a key or wait a few seconds to continue starting up

Hello,
Yesterday my macbook pro was working fine and i left it before sleeping working and it's go into slepping mode after battery discharged.
today morning i turned it on and i got this message after many times of automatic restart :
" Your computer restarted because of a problem. Press a key or wait a few seconds to continue starting up "
i have searched for the problem and the way to solve it i found many articles and helpful solutions but never changed !
and that's what's happened exactly:
1. I booted into safe mode for only one time and i can't boot again and i don't know why?
2. After botting in safe mode i deleted all non-app store apps and, then restart
3. Still rebooting and the message appear.
4. reseting PRAM
5. Repairing and verifying permissions and disk. = some errors in itunes/resources/.... serval times of repairing and nothing effect on errors.
6. Hardware test = no troubles found.
7. Reinstall OS X mountain lion = i got a message that my apple id is not purchased mountain lion because i bought my mac earlier 2012 with leopard and i have upgraded may be from another Apple id i can't remember.
No backups to restore, and i have a wealth of my work databases i can't return it back
Please help

Morning from QA,
my macbook pro now working and i got this report and sent it to apple.
Interval Since Last Panic Report: 1362 sec
Panics Since Last Report:          1
Anonymous UUID:                    E6D04971-1F3E-80D5-1BC9-1B89279EBEA3
Sat Oct 5 21:58:28 2013
panic(cpu 0 caller 0xffffff80034b8945): Kernel trap at 0xffffff7f83fb104c, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0xffffff80b2f2a000, CR3: 0x000000000bb29018, CR4: 0x00000000000606e0
RAX: 0x0000000000000500, RBX: 0xffffff80b2f28c00, RCX: 0x0000000000bfbfbf, RDX: 0xffffff7f83fb98d0
RSP: 0xffffff8081b12900, RBP: 0xffffff8081b13af0, RSI: 0x0000000000000020, RDI: 0xffffff80b2f28c00
R8: 0x0000000000000fee, R9: 0x0000000000010000, R10: 0x0000000000000000, R11: 0x000000007fffffff
R12: 0x0000000000000fee, R13: 0x0000000000000800, R14: 0x0000000000000000, R15: 0x0000000000000020
RFL: 0x0000000000010206, RIP: 0xffffff7f83fb104c, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0xffffff80b2f2a000, Error code: 0x0000000000000002, Fault CPU: 0x0
Backtrace (CPU 0), Frame : Return Address
0xffffff8081b125a0 : 0xffffff800341d636
0xffffff8081b12610 : 0xffffff80034b8945
0xffffff8081b127e0 : 0xffffff80034cebfd
0xffffff8081b12800 : 0xffffff7f83fb104c
0xffffff8081b13af0 : 0xffffff7f83fa7d51
0xffffff8081b13b50 : 0xffffff7f83fb1503
0xffffff8081b13b70 : 0xffffff7f83fac770
0xffffff8081b13b90 : 0xffffff7f83fb1bba
0xffffff8081b13bc0 : 0xffffff8003870b13
0xffffff8081b13c20 : 0xffffff800386e74f
0xffffff8081b13d70 : 0xffffff8003498c21
0xffffff8081b13e80 : 0xffffff8003420b4d
0xffffff8081b13eb0 : 0xffffff8003410448
0xffffff8081b13f00 : 0xffffff800341961b
0xffffff8081b13f70 : 0xffffff80034a6546
0xffffff8081b13fb0 : 0xffffff80034cf473
      Kernel Extensions in backtrace:
         com.apple.iokit.IOGraphicsFamily(2.3.7)[9928306E-3508-3DBC-80A4-D8F1D87650D7]@0 xffffff7f83f9e000->0xffffff7f83fd5fff
            dependency: com.apple.iokit.IOPCIFamily(2.8)[2FAEA49C-EA4C-39C6-9203-FC022277A43C]@0xffffff 7f83a75000
BSD process name corresponding to current thread: WindowServer
Mac OS version:
12F45
Kernel version:
Darwin Kernel Version 12.5.0: Sun Sep 29 13:33:47 PDT 2013; root:xnu-2050.48.12~1/RELEASE_X86_64
Kernel UUID: EA38B02E-2B88-309F-BA68-1DE29F605DD8
Kernel slide:     0x0000000003200000
Kernel text base: 0xffffff8003400000
System model name: MacBookPro8,1 (Mac-94245B3640C91C81)
System uptime in nanoseconds: 61714428675
last loaded kext at 61660768085: com.apple.driver.AppleHWSensor          1.9.5d0 (addr 0xffffff7f84d07000, size 36864)
loaded kexts:
org.virtualbox.kext.VBoxNetAdp          4.2.14
org.virtualbox.kext.VBoxNetFlt          4.2.14
org.virtualbox.kext.VBoxUSB          4.2.14
org.virtualbox.kext.VBoxDrv          4.2.14
com.apple.driver.AppleHWSensor          1.9.5d0
com.apple.iokit.IOBluetoothSerialManager          4.1.7f2
com.apple.driver.AudioAUUC          1.60
com.apple.driver.AppleTyMCEDriver          1.0.2d2
com.apple.driver.AGPM          100.13.12
com.apple.filesystems.autofs          3.0
com.apple.driver.AppleMikeyHIDDriver          124
com.apple.iokit.IOBluetoothUSBDFU          4.1.7f2
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport          4.1.7f4
com.apple.driver.AppleUpstreamUserClient          3.5.12
com.apple.driver.AppleHDAHardwareConfigDriver          2.4.7fc4
com.apple.driver.AppleHDA          2.4.7fc4
com.apple.driver.SMCMotionSensor          3.0.3d1
com.apple.driver.AppleSMCPDRC          1.0.0
com.apple.driver.AppleMikeyDriver          2.4.7fc4
com.apple.driver.AppleSMBusPCI          1.0.11d1
com.apple.driver.ACPI_SMC_PlatformPlugin          1.0.0
com.apple.driver.AppleLPC          1.6.3
com.apple.driver.AppleSMCLMU          2.0.3d0
com.apple.driver.AppleBacklight          170.3.5
com.apple.driver.AppleMCCSControl          1.1.11
com.apple.driver.AppleIntelHD3000Graphics          8.1.6
com.apple.driver.AppleIntelSNBGraphicsFB          8.1.6
com.apple.driver.AppleMuxControl          3.4.5
com.apple.iokit.IOUserEthernet          1.0.0d1
com.apple.Dont_Steal_Mac_OS_X          7.0.0
com.apple.driver.ApplePolicyControl          3.4.5
com.apple.driver.AppleUSBTCButtons          237.1
com.apple.driver.AppleUSBTCKeyEventDriver          237.1
com.apple.driver.AppleUSBTCKeyboard          237.1
com.apple.driver.AppleIRController          320.15
com.apple.iokit.SCSITaskUserClient          3.5.6
com.apple.driver.AppleFileSystemDriver          3.0.1
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless          1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
com.apple.BootCache          34
com.apple.driver.XsanFilter          404
com.apple.iokit.IOAHCIBlockStorage          2.3.5
com.apple.driver.AppleUSBHub          635.4.0
com.apple.driver.AirPort.Brcm4331          615.20.17
com.apple.driver.AppleAHCIPort          2.6.6
com.apple.iokit.AppleBCM5701Ethernet          3.6.2b4
com.apple.driver.AppleSDXC          1.4.3
com.apple.driver.AppleFWOHCI          4.9.9
com.apple.driver.AppleUSBEHCI          621.4.6
com.apple.driver.AppleUSBUHCI          621.4.0
com.apple.driver.AppleSmartBatteryManager          161.0.0
com.apple.driver.AppleACPIButtons          1.8
com.apple.driver.AppleRTC          1.5
com.apple.driver.AppleHPET          1.8
com.apple.driver.AppleSMBIOS          1.9
com.apple.driver.AppleACPIEC          1.8
com.apple.driver.AppleAPIC          1.7
com.apple.driver.AppleIntelCPUPowerManagementClient          214.0.0
com.apple.nke.applicationfirewall          4.0.39
com.apple.security.quarantine          2.1
com.apple.driver.AppleIntelCPUPowerManagement          214.0.0
com.apple.iokit.IOSerialFamily          10.0.6
com.apple.kext.triggers          1.0
com.apple.iokit.IOBluetoothHostControllerUSBTransport          4.1.7f2
com.apple.driver.DspFuncLib          2.4.7fc4
com.apple.iokit.IOAudioFamily          1.9.2fc7
com.apple.kext.OSvKernDSPLib          1.12
com.apple.driver.IOPlatformPluginLegacy          1.0.0
com.apple.iokit.IOFireWireIP          2.2.5
com.apple.driver.IOPlatformPluginFamily          5.4.1d13
com.apple.driver.AppleThunderboltEDMSink          1.2.0
com.apple.driver.AppleThunderboltDPOutAdapter          2.5.0
com.apple.driver.AppleHDAController          2.4.7fc4
com.apple.iokit.IOHDAFamily          2.4.7fc4
com.apple.driver.AppleSMBusController          1.0.11d1
com.apple.driver.AppleBacklightExpert          1.0.4
com.apple.iokit.IOSurface          86.0.4
com.apple.iokit.IOBluetoothFamily          4.1.7f2
com.apple.driver.AppleSMC          3.1.5d4
com.apple.driver.AppleGraphicsControl          3.4.5
com.apple.iokit.IONDRVSupport          2.3.7
com.apple.iokit.IOGraphicsFamily          2.3.7
com.apple.driver.AppleThunderboltDPInAdapter          2.5.0
com.apple.driver.AppleThunderboltDPAdapterFamily          2.5.0
com.apple.driver.AppleThunderboltPCIDownAdapter          1.3.2
com.apple.driver.AppleUSBMultitouch          237.3
com.apple.iokit.IOUSBHIDDriver          623.4.0
com.apple.driver.AppleUSBMergeNub          621.4.6
com.apple.driver.AppleUSBComposite          621.4.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice          3.5.6
com.apple.iokit.IOBDStorageFamily          1.7
com.apple.iokit.IODVDStorageFamily          1.7.1
com.apple.iokit.IOCDStorageFamily          1.7.1
com.apple.iokit.IOAHCISerialATAPI          2.5.5
com.apple.iokit.IOSCSIArchitectureModelFamily          3.5.6
com.apple.iokit.IOUSBUserClient          630.4.4
com.apple.driver.AppleThunderboltNHI          1.9.2
com.apple.iokit.IOThunderboltFamily          2.7.7
com.apple.iokit.IO80211Family          530.5
com.apple.iokit.IOAHCIFamily          2.5.1
com.apple.iokit.IOEthernetAVBController          1.0.2b1
com.apple.iokit.IONetworkingFamily          3.0
com.apple.iokit.IOFireWireFamily          4.5.5
com.apple.iokit.IOUSBFamily          635.4.0
com.apple.driver.AppleEFINVRAM          2.0
com.apple.driver.AppleEFIRuntime          2.0
com.apple.iokit.IOHIDFamily          1.8.1
com.apple.iokit.IOSMBusFamily          1.1
com.apple.security.sandbox          220.3
com.apple.kext.AppleMatch          1.0.0d1
com.apple.security.TMSafetyNet          7
com.apple.driver.DiskImages          345
com.apple.iokit.IOStorageFamily          1.8
com.apple.driver.AppleKeyStore          28.21
com.apple.driver.AppleACPIPlatform          1.8
com.apple.iokit.IOPCIFamily          2.8
com.apple.iokit.IOACPIFamily          1.4
com.apple.kec.corecrypto          1.0
Model: MacBookPro8,1, BootROM MBP81.0047.B27, 2 processors, Intel Core i5, 2.4 GHz, 4 GB, SMC 1.68f99
Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In, 384 MB
Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1333 MHz, 0x80AD, 0x484D54333235533642465238432D48392020
Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1333 MHz, 0x80AD, 0x484D54333235533642465238432D48392020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xD6), Broadcom BCM43xx 1.0 (5.106.98.100.17)
Bluetooth: Version 4.1.7f2 12718, 3 service, 13 devices, 3 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Serial ATA Device: ST9500325ASG, 500.11 GB
Serial ATA Device: OPTIARC DVD RW AD-5970H
USB Device: hub_device, 0x0424 (SMSC), 0x2513, 0xfd100000 / 2
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd110000 / 3
USB Device: hub_device, 0x0424 (SMSC), 0x2513, 0xfa100000 / 3
USB Device: BRCM2070 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0xfa110000 / 5
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x821a, 0xfa113000 / 6
USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0253, 0xfa120000 / 4
USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8509, 0xfa200000 / 2

Adobe Media Encoder freezes with one second left

Hi all,
All of a sudden now, when I export from Premiere CS4 to AME, regardless of what codec I use, AME hangs with just one second left to go. It will not finish encoding, no matter how long I wait. When I hit "Stop Queue" the program itself hangs, and I have to "Force Quit" to start over.
I have installed the 4.0.1 update for both Premiere and AME. Running on a Macbook Pro 2.5 GHz, 4 GB RAM. Anyone else have this problem and figured out a solution?

Sounds like the empty timeline or premiere's 'black video' freeze issue.
For some reason the encoder freezes when the timeline encounters any 'blank' frames. By blank I mean either an empty timeline, or any of the Premiere generated color mattes, title cards, bars and tone, etc. (if this is overlaid with 'real' video footage it does not seem to be an issue).
So if your project ends with a fade to black, or some black footage at the end, that may be the culprit. Is this happening in your case?
Solution: I've generated a black video file (i created and exported this in After Effects) that I have now laid on the first (bottom) layer of every Premiere project I start. I have a 5 second video file that I just stretch over the duration of the project before I render. This has solved the freeze issue for me. If you search the forum there is other mention of introducing opacity keyframes into your generated footage as another work around. I haven't tried this way myself, so I can't fully comment.
Good luck!

Select Single * and Select upto one row

Hi all,
Can anybody tell me what is difference between Select single * and select upto one row?
And which one is better?
Thanks in advance.......

According to SAP Performance course the SELECT UP TO 1 ROWS is faster than SELECT SINGLE because you are not using all the primary key fields.
select single is a construct designed to read database records with primary key. In the absence of the primary key, it might end up doing a sequential search, whereas the select up to 1 rows may assume that there is no primary key supplied and will try to find most suitable index.
The best way to find out is through sql trace or runtime analysis.
Use "select up to 1 rows" only if you are sure that all the records returned will have the same value for the field(s) you are interested in. If not, you will be reading only the first record which matches the criteria, but may be the second or the third record has the value you are looking for.
The System test result showed that the variant Single * takes less time than Up to 1 rows as there is an additional level for COUNT STOP KEY for SELECT ENDSELECT UP TO 1 ROWS.
The 'SELECT SINGLE' statement selects the first row in the database that it finds that fulfils the 'WHERE' clause If this results in multiple records then only the first one will be returned and therefore may not be unique.
Mainly: to read data from
The 'SELECT .... UP TO 1 ROWS' statement is subtly different. The database selects all of the relevant records that are defined by the WHERE clause, applies any aggregate, ordering or grouping functions to them and then returns the first record of the result set.
Mainly: to check if entries exist.
Select Single is the best one compared to UPto one rows.
Select Single will get the first record from the table which satisfies the given condition.So it will interact once with the database.
UTO 1 rows will get the list of the records for the given match and iwll show the first record from the list.So it will take time to get the record.
SELECT SINGLE VBELN from VBAK
where MATNR = '1M20'.
---Thjis will get the first matched record and will display the record
SELECT VBELN from VBAK
where MATNR = '1M20' upto 1 rows.
---Thjis will get the list of matched records and will display the first record
The Major difference between Select Single and Select UPTO 1 rows is The Usage Of Buffer for each.
Select Single will search for all the satisfied data and bring all that data into Buffer and later it will give to that data to the program.
Select UPTO 1 Rows will end the search after getting the 1st satisfied record and gives that record to the program.
Thus Select Single will take much processing time when compare with Select UPTO 1 rows.
Also
check these threads..
Difference between Select Single and Selct upto 1 row
Difference between Select Single and Select upto 1 row
Difference between select single and select upto one row
Difference between 'select single *' and 'select upto 1 rows'
difference between select single and select up to 1 rows
regards,
srinivas
<b>*reward for useful answers*</b>

Why do I get a black screen telling me to wait for 40 seconds and then to 'skip ad'?

I installed a Firefox update and since then, when I try to connect to a website, I almost always get a black screen telling me to wait for 40 seconds and then to 'skip ad'. This is very irritating and a waste of time. There are no ads to skip. Why is this happening and how can I stop it?

Start Firefox in <u>[[Safe Mode|Safe Mode]]</u> to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance).
*Do NOT click the Reset button on the Safe Mode start window.
*https://support.mozilla.org/kb/Safe+Mode
*https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes
You can check the connection settings.
*Firefox > Preferences > Advanced > Network : Connection > Settings
*https://support.mozilla.org/kb/Options+window+-+Advanced+panel
If you do not need to use a proxy to connect to internet then try to select "No Proxy" if "Use the system proxy settings" or one of the others do not work properly.
See "Firefox connection settings":
*https://support.mozilla.org/kb/Firefox+cannot+load+websites+but+other+programs+can

BDC to update CAT2 transaction.one issue while updating CAT2 transaction

Good Day Friends,
i have one issue while updating CAT2 transaction,
i have enhnced 3 custom fields in CAT2 tx-code. while updating through manually the data is getting stored in CATSDB tx-code for this i have done validation in enhamcement spots ECC 6.0.
but when i am running bdc this custom field data is not updating in CATSDB table.
my dout is will BDC work for enhancement spots or not , also please suggest if you have any idea ?

Hi,
Usually I am trying to avoid BDC. So I would try to use BAPIs BAPI_CATIMESHEETMGR_INSERT and BAPI_CATIMESHEETMGR_CHANGE. Similar to other BAPIs, you can pass values for your extended fields using table EXTENSIONIN. It's described in BAPI's documentation or look for EXTENSIONIN on SDN. The principle is same for all BAPIs.
Regards

Always need Disconnect power, press the power button wait for 10 seconds...

I bought a HP computer for a couple of years ( Pavilion a6695it ) It always works well. But in recent days, I can not start up it. I tried pressed power button on the front of the computer, nothing happend. Then I searched in hp site. finnally, I find this article http://h10025.www1.hp.com/ewfrf/wc/document?docname=c00241069&tmp_task=solveCategory&cc=it&dlc=it&lc...
In english version the article is here:
http://h10025.www1.hp.com/ewfrf/wc/document?docname=bph06788&cc=us&destPage=document&lc=en&product=3...
Power supply light is on or flashes
Perform the following steps, in order, until power is restored or it is determined that there is a hardware failure:
CAUTION:This product contains components that are easily damaged by ElectroStatic Discharge (ESD). To reduce the chance of ESD damage, work over a non-carpeted floor, use a static dissipative work surface (like a conductive foam pad), and wear an ESD wrist strap that is connected to a grounded surface, like the metal frame of a PC.
Disconnect everything from the computer, including the power cord.
With the power cord disconnected , press the power button on the front of the computer and wait for ten seconds.
This is work for me. But now, my computer always need this methond that it can be started up.
Disconnect power -> press the power button and wait for ten seconds -> then the system will start up
So my question: where is the problem? Which part is broken and i should replace? Thanks.
regards,
Youli
This question was solved.
View Solution.

Hello youlichika,
Welcome to the HP Forums, I hope you enjoy your experience! To help you get the most out of the HP Forums I would like to direct your attention to the HP Forums Guide First Time Here? Learn How to Post and More.
I understand that you are not able to power on your desktop, and I would be happy to assist you in this endeavor!
In following the document for Troubleshooting Power Supply Issues, were you able to follow steps 3-9? If so, what were the results?
If you have come to the end of the document, and you still have to drain the power from the computer to power it on, you can find a replacement part (5188-2627) through one of the sites available by following this link.
I hope this helps!
Best Regards
MechPilot
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the right to say “Thanks” for helping!

Diffrence b/w select single & select upto one row

hi
wat is the diffrence b/w select single & select upto one row?
deepak

Hi,
Select single has to be used with a where condition that has all the key fields:
It will always return a unique record(If a match is found).
Select upto 1 rows would get your the first record if multiple matches are found.
and select up to has to be end with endselect statements.
According to SAP Performance course the SELECT UP TO 1 ROWS is faster than SELECT SINGLE because you are not using all the primary key fields.
select single is a construct designed to read database records with primary key. In the absence of the primary key, it might end up doing a sequential search, whereas the select up to 1 rows may assume that there is no primary key supplied and will try to find most suitable index.
The best way to find out is through sql trace or runtime analysis.
Use "select up to 1 rows" only if you are sure that all the records returned will have the same value for the field(s) you are interested in. If not, you will be reading only the first record which matches the criteria, but may be the second or the third record has the value you are looking for.
The System test result showed that the variant Single * takes less time than Up to 1 rows as there is an additional level for COUNT STOP KEY for SELECT ENDSELECT UP TO 1 ROWS.
The 'SELECT SINGLE' statement selects the first row in the database that it finds that fulfils the 'WHERE' clause If this results in multiple records then only the first one will be returned and therefore may not be unique.
Mainly: to read data from
The 'SELECT .... UP TO 1 ROWS' statement is subtly different. The database selects all of the relevant records that are defined by the WHERE clause, applies any aggregate, ordering or grouping functions to them and then returns the first record of the result set.
Mainly: to check if entries exist.
When you say SELECT SINGLE, it means that you are expecting only one row to be present in the database for the condition you're going to specify in the WHERE clause. so that means, you will have to specify the primary key in your WHERE clause. Otherwise you get a warning.
SELECT UP TO 1 ROWS is used in cases where you just want to make sure that there is at least one entry in the database table which satisfies your WHERE clause. Generally, it is meant to be used for existence-check.
You may not want to really use the values returned by the SELECT statement in this case (thought this may not necessarily be so).And in each case the database optimizer may choose a different strategy to retrieve the data.
Knowing when to use SELECT SINGLE or SELECT ... UP TO 1 ROWS
A lot of people use the SELECT SINGLE statement to check for the existence of a value in a database. Other people prefer to use the 'UP TO 1 ROWS' variant of the SELECT statement.
So what's the difference between using 'SELECT SINGLE' statement as against a 'SELECT .... UP TO 1 ROWS' statement ?
If you're considering the statements
SELECT SINGLE field INTO w_field FROM table.
and
SELECT field INTO w_field FROM table UP TO 1 ROWS. ENDSELECT.
then looking at the result, not much apart from the extra ENDSELECT statement. Look at the run time and memory usage and they may be worlds apart.
Why is this ?? The answer is simple.
The 'SELECT SINGLE' statement selects the first row in the database that it finds that fulfils the 'WHERE' clause If this results in multiple records then only the first one will be returned and therefore may not be unique.
The 'SELECT .... UP TO 1 ROWS' statement is subtly different. The database selects all of the relevant records that are defined by the WHERE clause, applies any aggregate, ordering or grouping functions to them and then returns the first record of the result set.
According to SAP Performance course the SELECT UP TO 1 ROWS is faster than SELECT SINGLE because you are not using all the primary key fields.
http://sap-img.com/abap/difference-between-select-single-and-select-upto-one-rows.htm
Check these links -
The specified item was not found.
diff between select single and up to one row
diff b/w SECELT SINGLE * AND SELECT UPTO ONE ROW
Regards,
Priyanka.

Diff bw select single * and select upto one row

hai,
what is the difference between select single * and select upto one row.

hi,
ex code
Report Z_Difference
Message-id 38
Line-Size 80
Line-Count 0
No Standard Page Heading.
Start-Of-Selection.
Data: w_Single type Posnr,
t_Rows type standard table of Posnr
initial size 0
with header line.
Select single Posnr
from zDifference
into w_Single.
Select Posnr
into table t_Rows
from zDifference
up to 1 rows
order by Posnr descending.
Write :/ 'Select single:', w_Single.
Skip 1.
Write :/ 'Up to 1 rows :'.
Loop at t_Rows.
Write t_Rows.
EndLoop.
According to SAP Performance course the SELECT UP TO 1 ROWS is faster than SELECT SINGLE because you are not
using all the primary key fields.
select single is a construct designed to read database records with primary key. In the absence of the primary key,
it might end up doing a sequential search, whereas the select up to 1 rows may assume that there is no primary key
supplied and will try to find most suitable index.
The best way to find out is through sql trace or runtime analysis.
Use "select up to 1 rows" only if you are sure that all the records returned will have the same value for the field(s)
you are interested in. If not, you will be reading only the first record which matches the criteria, but may be the
second or the third record has the value you are looking for.
The System test result showed that the variant Single * takes less time than Up to 1 rows as there is an additional
level for COUNT STOP KEY for SELECT ENDSELECT UP TO 1 ROWS.
The 'SELECT SINGLE' statement selects the first row in the database that it finds that fulfils the 'WHERE' clause
If this results in multiple records then only the first one will be returned and therefore may not be unique.
Mainly: to read data from
The 'SELECT .... UP TO 1 ROWS' statement is subtly different. The database selects all of the relevant records that
are defined by the WHERE clause, applies any aggregate, ordering or grouping functions to them and then returns
the first record of the result set.
Mainly: to check if entries exist.
You can refer to the below link..
http://www.sap-img.com/abap/difference-between-select-single-and-select-upto-one-rows.htm
rgds
anver
if hlped pls mark points

Select single * & Select * upto one row

What is the difference between Select single * & Select * upto one row?Performance wise which is a better one?

Hi,
According to SAP Performance course the SELECT UP TO 1 ROWS is faster than SELECT SINGLE because you are not using all the primary key fields.
Select single is a construct designed to read database records with primary key. In the absence of the primary key, it might end up doing a sequential search, whereas the select up to 1 rows may assume that there is no primary key supplied and will try to find most suitable index.
The best way to find out is through sql trace or runtime analysis.
Use "select up to 1 rows" only if you are sure that all the records returned will have the same value for the field(s) you are interested in. If not, you will be reading only the first record which matches the criteria, but may be the second or the third record has the value you are looking for.
The System test result showed that the variant Single * takes less time than Up to 1 rows as there is an additional level for COUNT STOP KEY for SELECT ENDSELECT UP TO 1 ROWS.
The 'SELECT SINGLE' statement selects the first row in the database that it finds that fulfils the 'WHERE' clause If this results in multiple records then only the first one will be returned and therefore may not be unique.
Mainly: to read data from
The 'SELECT .... UP TO 1 ROWS' statement is subtly different. The database selects all of the relevant records that are defined by the WHERE clause, applies any aggregate, ordering or grouping functions to them and then returns the first record of the result set.
Mainly: to check if entries exist.
Select Single
You need to mention all the key fields of the table.
No END SELECT required.
More performance compared to upto 1 row.
Where as UP to 1 row.
YOu can use if you do not have all the primiary key fields available.
END SELECT requeired.
Since all keys are not passing, possiblities of have other rows which satisfies the condition.
Select Statement with EndSelect is a loop, which in a single run retrieves a single Record. This Record has to be stored in a Work Area and then appended into an Internal Table.
Select Statements without EndSelect is not a loop and it retrieves the whole Record set matching the Criteria in a single shot and has to be Stored in an Internal Table Directly.
The most important thing to remember about the SELECT SINGLE is
There are several things to remember:
1) It retrieves only one row
2) It does not need an ENDSELECT statement
3) THE FULL KEY OF THE TABLE MUST BE INCLUDED IN
THE WHERE CLAUSE OF THE SELECT STATEMENT
Regards

Wait upto one second v/s BAPI TRANSACTION COMMIT

Similar Messages

Maybe you are looking for