BAPI_PO_CHANGE - error while locking PO iems

All,
We're getting error when trying to lock PO items using BAPI_PO_CHANGE.
The PO item has a closed order as the account assignment in the PO. We do not get the error if the order is open.
Has anybody encountered this problem before? Is there any way to suppress this and allow locking of the item? Any inputs will be highly appreciated.
Regards
Deepthi.

More info on this,
I get the error -
'Material purchase order' not allowed - Order XXXXXX
When we try to lock the same PO item using ME22N it is successful.
Is there any relevant OSS note for this?

Similar Messages

Error while lock object creation

Hi
When I tried to create a lock object, I get the following error.
Error: "Total length of lock argument for table XXXXXXXXX longer than 150"
I have 3 tables in which Table1 is the check table for the value tables (Table2 & Table3). During the process of deletion of a record from Table1 (CT) I need the lock tobe established on value tables and then I delete all the corresponding entries in value tables are also deleted.
Would like to know If there is any other std ways of doing this ? and
Solution to overcome the error.
Regards
Karthick

Hi,
I think the error is becoz you have given too many LOCK parameters in the lock object. the total length of the PARAMTERS of lock object should not exceed 150.
By default all the KEY fields will be taken as Lock paramters, so your table key's length is more than 150.
Also why dont you create 3 lock objects for each table and then use only KEY's of each table as LOCK PARAMETERS.
Then Lock T1 record first then lock T2 and T3 records, then delete records from T2 and T3.
Then you delete T1 record.
The execute DEQUEUE_ALL.
Regards,
Sesh

Encountered : A system error has occurred while locking, pls help

Dear All..
pls help..
while executing some of our remote function module we encountered some locking error.. the message returned by SAP is :
A system error has occurred while locking
from message class : M3 #021
the remote function module is running bapi_goodsmvt_create in background..
the question is.. why this error occured and how to solve it ? and what is the root cause.. ?
because the error is only happened once (until now) we cannot simulate to get the error again.. so it is hard to find out the root cause..
thanks for the help..
sasmente

Hi,
I am also having the same problem. I am running the BAPI_MATPHYSINV_CHANGECOUNT' to count the Articles.
When I print the error on screen, some the data shown as counted. Some are not changed and some with the following error.
System error while locking the data
Furthermore I went to the BASIS and saw that when we run this particular program its showing the locks on MARC and several tables with the same System ID from which we run the program
Can anyone come up ? Its getting too hard to resolve.

BAPI_GOODSMVT_CREATE ERROR: A System Error Has Occurred While Locking

Hi All,
I am having a problem with a Z program that I am writing.
Basically, it uses the BAPI mentioned in the title. The program will read excel file that is being uploaded, and then will segregate the line items by 200 lines.
That means, if I were to upload 1000 line items, the BAPI will be called and executed 5 times (1000/200 = 5).
However, when trying to upload 10000 line items, I received this error after around 3000 line items.
"A system error has occurred while locking".
This happens when IMPORT parameter TEST_RUN is set to 'X'.
I found this after some googling: http://sap.ittoolbox.com/groups/technical-functional/sap-basis/lock-entry-system-error-1674434
I am hoping for your expert thoughts on this.
Thank you.

BAPI TO Upload Inventory Data
* GMCODE Table T158G - 01 - MB01 - Goods Receipts for Purchase Order
*                      02 - MB31 - Goods Receipts for Prod Order
*                      03 - MB1A - Goods Issue
*                      04 - MB1B - Transfer Posting
*                      05 - MB1C - Enter Other Goods Receipt
*                      06 - MB11
* Domain: KZBEW - Movement Indicator
*      Goods movement w/o reference
* B - Goods movement for purchase order
* F - Goods movement for production order
* L - Goods movement for delivery note
* K - Goods movement for kanban requirement (WM - internal only)
* O - Subsequent adjustment of "material-provided" consumption
* W - Subsequent adjustment of proportion/product unit material
report zbapi_goodsmovement.
parameters: p-file like rlgrap-filename default
                                 'c:\sapdata\TEST.txt'.
parameters: e-file like rlgrap-filename default
                                 'c:\sapdata\gdsmvterror.txt'.
parameters: xpost like sy-datum default sy-datum.
data: begin of gmhead.
        include structure bapi2017_gm_head_01.
data: end of gmhead.
data: begin of gmcode.
        include structure bapi2017_gm_code.
data: end of gmcode.
data: begin of mthead.
        include structure bapi2017_gm_head_ret.
data: end of mthead.
data: begin of itab occurs 100.
        include structure bapi2017_gm_item_create.
data: end of itab.
data: begin of errmsg occurs 10.
        include structure bapiret2.
data: end of errmsg.
data: wmenge like iseg-menge,
      errflag.
data: begin of pcitab occurs 100,
        ext_doc(10),           "External Document Number
        mvt_type(3),           "Movement Type
        doc_date(8),           "Document Date
        post_date(8),          "Posting Date
        plant(4),              "Plant
        material(18),          "Material Number
        qty(13),               "Quantity
        recv_loc(4),           "Receiving Location
        issue_loc(4),          "Issuing Location
        pur_doc(10),           "Purchase Document No
        po_item(3),            "Purchase Document Item No
        del_no(10),            "Delivery Purchase Order Number
        del_item(3),           "Delivery Item
        prod_doc(10),          "Production Document No
        scrap_reason(10),      "Scrap Reason
        upd_sta(1),            "Update Status
      end of pcitab.
call function 'WS_UPLOAD'
exporting
    filename                      = p-file
    filetype                      = 'DAT'
* IMPORTING
*   FILELENGTH                    =
tables
    data_tab                      = pcitab
* EXCEPTIONS
*   FILE_OPEN_ERROR               = 1
*   FILE_READ_ERROR               = 2
*   NO_BATCH                      = 3
*   GUI_REFUSE_FILETRANSFER       = 4
*   INVALID_TYPE                  = 5
*   OTHERS                        = 6
if sy-subrc <> 0.
message id sy-msgid type sy-msgty number sy-msgno
          with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
exit.
endif.
gmhead-pstng_date = sy-datum.
gmhead-doc_date = sy-datum.
gmhead-pr_uname = sy-uname.
gmcode-gm_code = '01'.   "01 - MB01 - Goods Receipts for Purchase Order
loop at pcitab.
itab-move_type = pcitab-mvt_type.
itab-mvt_ind    = 'B'.
itab-plant      = pcitab-plant.
itab-material   = pcitab-material.
itab-entry_qnt = pcitab-qty.
itab-move_stloc = pcitab-recv_loc.
itab-stge_loc   = pcitab-issue_loc.
itab-po_number = pcitab-pur_doc.
itab-po_item    = pcitab-po_item.
concatenate pcitab-del_no pcitab-del_item into itab-item_text.
itab-move_reas = pcitab-scrap_reason.
append itab.
endloop.
loop at itab.
write:/ itab-material, itab-plant, itab-stge_loc,
          itab-move_type, itab-entry_qnt, itab-entry_uom,
          itab-entry_uom_iso, itab-po_number, itab-po_item,
                                              pcitab-ext_doc.
endloop.
call function 'BAPI_GOODSMVT_CREATE'
exporting
    goodsmvt_header             = gmhead
    goodsmvt_code               = gmcode
*   TESTRUN                     = ' '
* IMPORTING
    goodsmvt_headret            = mthead
*   MATERIALDOCUMENT            =
*   MATDOCUMENTYEAR             =
tables
    goodsmvt_item               = itab
*   GOODSMVT_SERIALNUMBER       =
    return                      = errmsg
clear errflag.
loop at errmsg.
if errmsg-type eq 'E'.
    write:/'Error in function', errmsg-message.
    errflag = 'X'.
else.
    write:/ errmsg-message.
endif.
endloop.
if errflag is initial.
commit work and wait.
if sy-subrc ne 0.
    write:/ 'Error in updating'.
    exit.
else.
    write:/ mthead-mat_doc, mthead-doc_year.
    perform upd_sta.
endif.
endif.
*       FORM UPD_STA                                                  *
form upd_sta.
loop at pcitab.
    pcitab-upd_sta = 'X'.
    modify pcitab.
endloop.
call function 'WS_DOWNLOAD'
    exporting
      filename                      = p-file
      filetype                      = 'DAT'
* IMPORTING
*   FILELENGTH                    =
    tables
      data_tab                      = pcitab
* EXCEPTIONS
*   FILE_OPEN_ERROR               = 1
*   FILE_READ_ERROR               = 2
*   NO_BATCH                      = 3
*   GUI_REFUSE_FILETRANSFER       = 4
*   INVALID_TYPE                  = 5
*   OTHERS                        = 6
endform.
Code Formatted by: Alvaro Tejada Galindo on Dec 26, 2008 10:20 AM

SAP NAME FILE lock error while creating the TR in development system.

Hi All,
I am getting an error message while saving the changes in my SAP Script that 'SAP names file for <UserId> locked by another process'
The name of the lock file is "/usr/sap/trans/tmp/<UserId>.LOS".
Can any body help me, how to resolve this problem ?
Thanks,

Hi Kamlesh,
did you find any solution? I'm getting the same error while a saving the changes in a Dynpro in the ABAP Development Workbench.
Thanks,
Viktor

IWeb Publish Error - A lock occurred while publishing to MobileMe

iWeb Publish Error - A lock occurred while publishing to MobileMe. Try publishing again later.
I've tried all articles so far on apple support site. Tried on new OS user and publishing to folder and publishing a test page. I still get an error. Publishing to folder works fine, its just when I publish to MobileMe. Also tried different network and restarting computer etc.
Help me. Thanks.

If you are logged in OK maybe you should look at your Keychain.
Finer/Go/Utilities/Keychain Access.app.
Try "Keychain First Aid" from the "Keychain Access" drop down menu.

While processing ALEAUD - "Error when locking the audit statistics"

Hello,
I am sending out IDOC for HR data and then prcessing ALEAUD inbound idoc immediatley (setting is done in WE21 partner profiles).
While processing these incomming idocs, I am getting this error "Error when locking the audit statistics for P01LOGSYS1 IMTIMEDEP HRMD_A" for few idocs. e.g. out of 1000 for 100 idocs this error will happen and IDOC goes to status 51.
If I try to process thes idocs ALEAUD using background processing and if I schedule 2 jobs at a time then I will get same error and IDOC goes to status 51.
Can someone help me out?

Hi
I tried processing the idocs in background processing as you have suggested using program RBDAPP01 (inbound).
There are 2 options in this program serial processing and parallel processing. When I select serial processing everyhting goes smooth but it takes long time. But when I select parallel processing I get same locking error mentioned above and only few idocs will get processed successfully with status 53 and all other will error out with status 51.
If I schedule 2 different jobs in background program RBDAPP01 (inbound) using serial processing then same thing will happen. only few idocs will get processed successfully with status 53 and all other will error out with status 51.
And I will get locking error ....
Note 1333417 says, " these IDocs will be processed via background runs of report RBDAPP01 \ RSEOUT00 (using background work processes) in batch mode leaving dialog work processes free for users and mission-critical processes. Hence you will not encounter the resources problems you are currently experiencing. The only other option would be to try increasing the number of available dialog work processes. The number of dialog processes must be greater than or equal to the total of the number of update and background processes per application server and must be configured across all operation mode
switches (see SAP note 74141). *However when there are a large number of IDocs being processed this is not a practical solution."*
Does that mean there is no possoble solution for this issue. If I increase dialog work processes will it be helpfull ?

A system error has occurred while locking

Hi, we encountered the error "A system error has occurred while locking" when executed transaction mm01. They said it's because the same material was launched in VL02n (outbound delivery) How can I check if it was really because of VL02n? they said that the lock was already deleted by Basis. Is there any tcode I can check where it really came from? thanks so much!

Hi,
If you are authorised for TCode - SE37 then execute the Function Module "TRANSACTION_CALL_VIA_RFC" and then enter TCode SM12 and execute. And then follow the option as suggested in earlier post.

Hi, i just try to update my 3g in itunes unfortunatly it got error while updating it asked me to restore update but unable to restore it , now my 3g i locked and on screen it displying usb symbol connect to itunes ,please help me regarding this

hi, i just try to update my 3g in itunes unfortunatly it got error while updating it asked me to restore update but unable to restore it , now my 3g i locked and on screen it displying usb symbol connect to itunes ,please help me regarding this

I suspect your error was 1015, not 1051. This usually involves a jailbroken iPhone, use Google to find your solution.

A system error has occured while locking

Message no. M3021 : A system error has occured while locking
I get this message in TCODE MM42 (IS RETAIL) after mass updating articles using TCODE MM46.
The lock table size was increased from 4 MB to 10 MB and still the issue occurs. It looks the lock table can store only 3600 entries, is there a way to increase number of entries.
Thanks
Jagadhish Natarajan

First, is this mass update going to happen on reguarly?
If no - you may want to further increase enque/table_size until it can finish this one-time run of the mass update.
If yes - you may want to work with your SAP basis guy and read note 13907. From your side, you may need to reduce the volume of this mass update. From the basis side, they need to determine a proper size for the enqueue table size.

Enqueue: Transfer error while reading lock entries.

Hi
We have an error in our SM21 log in ERP Prod system.
we have enque process on our CI server.
any body could provide the solution?
"Enqueue: Transfer error while reading lock entries
> Destination: prodecccs_ERP_00
> ENQUE_READ exception code: 8
> Name or password is incorrect (repeat logon)"
Thanks,
Ravi.

Thanks Ravi,
that's a big help. unfortunately for us, we're already on a release that includes that note (SAPKB70209). So I'll get a message opened to see if they can update that note so we can apply the fix. at least I know what component to open it under now.
I owe you one man.
--NICK

Unable to Log-in *SAP System Message : Error while reading a Dynpro*

Hi,
We are facing issues while logging-in through SAP logon 710.
The system throws an error dialog box with the below message:
SAP System Message : Error while reading a Dynpro
At the OS level Java process server0 is in stop status with exit code -11113. In ABAP WP Table all processes are in wait status.

Hi Please find the contents of std_server.out below.
stdout/stderr redirect
node name   : server0
pid         : 4124
system name : KEC
system nr. : 01
started at : Mon Jul 27 15:44:57 2009
[Thr 5656] MtxInit: -2 0 0
CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
SAP J2EE Engine Version 7.00   PatchLevel 110760.44 is starting...
Loading: LogManager ... 250 ms.
Loading: PoolManager ... 0 ms.
Loading: ApplicationThreadManager ... 47 ms.
Loading: ThreadManager ... 16 ms.
Loading: IpVerificationManager ... 0 ms.
Loading: ClassLoaderManager ... 16 ms.
Loading: ClusterManager ... 93 ms.
Loading: LockingManager ... 32 ms.
Loading: ConfigurationManager ... 1032 ms.
Loading: LicensingManager ... 0 ms.
Loading: CacheManager ... 93 ms.
Loading: ServiceManager ...
Loading services.:
Service runtimeinfo started. (16 ms).
Service cross started. (31 ms).
Service file started. (31 ms).
Service memory started. (31 ms).
Service timeout started. (16 ms).
Service trex.service started. (32 ms).
Service userstore started. (0 ms).
Service jmx_notification started. (15 ms).
Service p4 started. (62 ms).
Service classpath_resolver started. (16 ms).
Service deploy started. (3722 ms).
Service MigrationService started. (31 ms).
Service bimmrdeployer started. (0 ms).
Service log_configurator started. (5177 ms).
Service locking started. (0 ms).
Service http started. (126 ms).
Service naming started. (157 ms).
Service failover started. (16 ms).
Service appclient started. (31 ms).
Service javamail started. (47 ms).
Service ts started. (47 ms).
Service jmsconnector started. (47 ms).
Service licensing started. (15 ms).
Service connector started. (93 ms).
Service iiop started. (94 ms).
Service configuration started. (16 ms).
Service webservices started. (265 ms).
Service dbpool started. (1204 ms).
Service UT started. (0 ms).
Jul 27, 2009 3:45:09 PM         com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_54] Fatal: Initialization of ABAP data source (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed: "     Error while reading a dynpro                                        ". This message is critical if it appears during the startup of the AS Java.
Jul 27, 2009 3:45:09 PM ...re.server.ume.service.UMEServiceFrame [SAPEngine_System_Thread[impl:5]_54] Fatal:
service com.sap.security.core.ume.service ================= ERROR =================
Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details:      Error while reading a dynpro
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
     at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
     at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
     at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:81)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:152)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException:      Error while reading a dynpro
     at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:236)
     at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:446)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
     at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
     ... 6 more
com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details:      Error while reading a dynpro
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
     at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
     at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
     at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:81)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:152)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException:      Error while reading a dynpro
     at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:236)
     at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:446)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
     at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
     ... 6 more
[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Jul 27, 2009 3:45:09 PM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_54] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

Error while installing OWB

Error while installing OWB
after 50% install.. it says
"Error in writing to file c:\oracle\ora9201\bin\oci.dll
The process cannot access the file because it is being used by another process"
Apparently I have restarted the workstation and closed all oracle related services in services and no other program is running expect the installer.
Can any one help in resolving the issue. Or can I hit the ignore button and continue installing?

Always install OWB into a new ORACLE_HOME unless the Installation and Configuration Guide states otherwise. This has only happened twice. OWB 9.0.2.62.3 was the last version to allow installation into an existing ORACLE_HOME. Another thing you can do is go to www.sysinternals.com and download the utility LISTDLLs. It is great. From a command prompt, start it with the syntax: listdlls >log.txt
This will output the DLLs in use and which executable is using it. Search for the DLL in the log.txt and scroll up until the double line. The executable name locking the DLL will be above the double line. If you have the Microsoft Distributed Transaction Coordinator Service running on the client, it will lock Oracle DLLs. This has been a common issue in the past, going back to the days of Data Mart Suite. This was documented in the Release Notes for it and may still be in the system in a note somewhere. It is in: DMS: Unable To Install; Filesopen/Service Running On Compaq Server Doc ID: Note:1080977.6 and Certain Files which need to be Reinstalled are Being Used Doc ID: Note:117672.1
The first note I wrote back before 2000.
Barry

Error while downloading. message on E71 GPS USA Ma...

“Error while downloading” message on E71 with updated GPS USA Maps
I’m sure I’m not the only one having this problem but I recently updated my maps on my Straight Talk Nokia E71. The phone says I have map download V 3.03 10wk bo4 Mw Open GL LM MN, Map version 0.1.25.114.and I’m using Nokia Ovi Suite 2.2.1.23. After I installed V3.03, I installed it and download the 1.46GB USA map file and the three turn by turn files. But when I first started the GPS app I started getting the following error “Error while downloading”(This is on phone only)
I have tried to factory reset the phone, re-format the 8GB memory card, remove City data and GF files and even unloaded OVI Suite and reload it. But every time I select GPS app and start to find places or my position, I get "Error while downloading" message. I’m new to this phone and didn’t get a respectable book from Straight Talk. So I don’t know much about this phone or Nokia OS. What is this error and how do I fix it. Also when I try to sync from the phone I get the response "system error". Ovi suite on the PC says I have downloaded all the USA maps and English voice with street names. Please help I’m at a lost.
Computer specs
I am running Win-Vista, with a Broadband connection. 3 GB Ram, 2 gig Pentium dual core.
Tran’s flash card has plenty room left on card over 5 gigs left.
If I need to delete a file on the phone please tell me the exact file name because I’m not sure which one to remove from the apps folder.
Solved!
Go to Solution.

@Action_Jackson
Welcome to the forum!
Whilst easy for me to say as keep very little data on device, I would suggest backup essential data then delete E:\cities + ,qf file followed by resetting device to "Out of box" state by keying in #7370# then 12345 (default Nokia lock code unless altered by yourself). At this point you would need to open OVI Maps application on device to re-initialise application and re-define necessary folder structure on memory card for device to be recognised by OVI Suite > Maps to re-download your regional mapping.
Happy to have helped forum with a Support Ratio = 42.5

Error while running a project in em console

It was running fine all these days.server was restarted and i am facing problems shown below.
I am not able run any project(ex.Project1) in em console.I am getting 2 errors like.
1)DBLocker caught exception while retrieving locked messages.Will retry retrieval after 2 seconds
2)Error while invoking endpoint "http://<server name>:7001/soa-infra/services/default/Project1/StdService" from client; Security Subject: Administrators
Even if i unlock the account,its getting locked automatically.
Notifications:1)The DocumentChange is not configured to be allowed for the component: RichTable[org.apache.myfaces.trinidad.component.UIXTable$RowKeyFacesBeanWrapper@7ae15fc6, id=messagesResult]
2)Invalid Remote Targets: [Target Name: /Farm_soa_domain/soa_domain/AdminServer/OracleBamServer, Target Type: oracle_bam_server, Display Name: OracleBamServer (AdminServer) => com.bea:Name=oracle-bam#11.1.1,Location=AdminServer,Type=AppDeployment], [Target Name: /Farm_soa_domain/soa_domain/AdminServer/OracleBamWeb, Target Type: oracle_bam_web, Display Name: OracleBamWeb (AdminServer) => com.bea:Name=oracle-bam#11.1.1,Location=AdminServer,Type=AppDeployment]
3)Calling ClearCacheCanonical Path=oracle.dms:JDBC_DataSource=SOADataSource,Location=AdminServer,name=/JDBC/SOADataSource/CONNECTION_4106,type=JDBC_Connection :::: matched=false
Thanks in advance

ALV Grid control is based on the custom controls on the screen. When the program is scheduled in background, it tries to create GUI related front-end objects and hence the error u201CFatal Error u2013 GUI cannot be reachedu201D. This type of problem is common with all the programs that use the ALV grid control to display the output.
Solution:
Whenever we execute this type of programs in background, we should be passing a blank docking container instead of the custom container as parent to our grid control.
The docking container doesnu2019t need any of the custom controls on the screen; instead it attaches an area to any or all of the four edges of the screen (top, left, right or bottom). The behavior of the areas in the container is determined by the sequence in which they are initialized. Docking Containers are attached to the screen from the inside out. This means that when you create a second container, it is attached to the edge of the screen, and the container that was already there is pushed outwards.
Let us modify the standard program (by taking a copy of it) to enable it to execute it in background.
Following modifications have to be made:
·        Define a docking container in the program
data: or_doc type ref to cl_gui_docking_container .
·        At the time of creating a custom container, check if the program is being executed in background or foreground. If the program is scheduled in background, then create a docking container instead of custom container.
if cl_gui_alv_grid=>offline( ) is initial.
    create object or_custom_container
           exporting container_name = c_container.
create object or_grid
         exporting i_parent = or_custom_container.
else .
create object or_grid
         exporting i_parent = or_doc .
endif .
Now test executing the program in background. The report would be generated.

BAPI_PO_CHANGE - error while locking PO iems

Similar Messages

Maybe you are looking for