LSMW : Unable to Specify Files . Logical path incorrect ?
Hi Guys,
I am trying to upload Goods movement Using the Standard LSMW 0110 program RM07MMBL.
When I try to execute the step Specify Files ,system displays an error message "No Logical Path specified."
The Source File is in my Local PC .
When I click the Converted Data File in the Specify files list
I get a popup which asks me for a Logical path and a Logical File and both these parameters a mandatory.
I tried to maintain the parameters and entries in transaction FILE also.
But it says 'logical path not assigned to the physical directory.'
What is the correct method for this.
What steps should I follow ..
Pls advice
Message was edited by: hao fu
Hi,
Refer the oss note 753511 released for this kind of error you face in LSMW, I am pasting the content of the note below,
******************Note Content,
Symptom
The system issues an error message for the logical path or file when you perform the "Specify files" step in the Legacy System Migration Workbench (transaction LSMW) although you have made the correct assignment in transaction FILE.
The error messages are as follows:
The logical path <PATH> does not point to the physical directory.
The logical file <FILE> is not assigned to the physical file.
or
A logical path was not specified.
Other terms
Logical path, logical file, transaction FILE, LSM Workbench
Reason and Prerequisites
Some import interfaces that you can also use with transaction LSMW work with logical path and file names.
Transaction LSMW itself, however, works with physical file names. To be able to transfer the LSMW file with the converted data to the import program, you must specify a logical file name for the file with the converted data in addition to the physical file name. In this case, the system displays additional fields in the 'Specify files' step in which you must enter the logical path and file name.
Solution
The error messages may be due to several causes. Check the following:
Have you maintained the logical path and logical file name and have you assigned them to the physical file specified in the "File" input field of transaction LSMW?
These settings are maintained in transaction FILE.
When you use logical file and path names, you must specify the name of the physical file with its path. If you have not specified any directory, you cannot assign any directory to the logical path in transaction FILE. In this case, the system uses the SAP Home directory on the application server by default. Bear in mind that the file name must not exceed the maximum length of 45 characters, including the path.
Up to LSMW version 1.7.2 (*):
If the logical file name specified does not point to the physical file (although it should do), the system adjusts the logical file name, that is, the information in transaction FILE is changed to the entries made in transaction LSMW. This may lead to unwanted side effects if the logical file is also used somewhere else. Therefore, SAP recommend that you always use separate logical paths and file names for transaction LSMW (the problem is corrected as of LSMW version 1.8.0, see below). If the logical file does not exist yet, it will be created upon request.
As of LSMW version 1.8.0 (*):
The settings of the logical file are checked but no longer adjusted automatically as in version 1.7.2 (see above). If there are inconsistencies, the system issues an error message. If the user is authorized to maintain logical paths and file names (as for transaction FILE: "Maintenance authorization for cross-client tables"), transaction LSMW can create the logical path, the file name and the file. Due to this automatic generation, the user no longer needs to make adjustments in transaction FILE. Therefore, we especially recommend this procedure.
To display the version of transaction LSMW, select "Extras" --> "Display LSMW version" in the main menu of the initial screen.
You should also bear in mind that as of Basis Release 6.20, that is, as of LSMW version 4.0, transaction LSMW is no longer an add-on but is delivered with the standard system.
Hope this helps,
Rgds,
Similar Messages
-
Transaction code to see the archive file logical path
Hello,
Some data is archived.
In which transaction we can get the archive file logical path.
( Just like transaction al11 for sap directories )
Thanks..
VijayHi Vijay,
Check transaction FILE or use FM FILE_GET_NAME_USING_PATH or FILE_GET_NAME_AND_LOGICAL_PATH
to retrieve the path.
Also check program RSFILENA and table PATH.
Thanks
Lakshman
Message was edited by: Lakshman Tandra
Message was edited by: Lakshman Tandra
Message was edited by: Lakshman Tandra -
LSMW by BI : Unable to specify file in step 7; logical Path not assigned
Hi,
I'm trying to uplaod HR DATA using object 0555 and method 0000 for Program RPDUSTD00 using LSMW Batch Input Method.
In step 7 when i specify file which tab delimited text file at front end pc(at my pc) let say c:\test.txt and save I got error message 'Logical path not assigned'.
Please suggest what I'm missing and what i need to do to get it correct.
Thanks,
Anshuman.Hi,
There are other files specified in the screen for imported and converted data. These files must be accessible on SAP application server. If the logical file names are not created use physical ones lik /tmp/blabla.lsmw.read etc.
Make sure you use different files for different objects.
Kind regards
Michael -
Hi Experts,
I have created the logical path and filename in FILE tcode.I am trying to upload the pdf file to application server by using this path.But
I am getting message like "Unable to open the file".Even I cannot find the this path in AL11 tcode.Kindly anyone advise how to upload pdf file using
custom path and file created from FILE tcode.
Thanks & Regards,
Anusha.Hi Anusha,
Please give as below.
I forget to say you cannot open the PDF in AL11 and for that you need some configuration, i think it can be done using content server,not sure completely please wait for some more suggestions.
Regards,
Pavan -
Error in LSMW in step7---specify file
dear all
when i am specifying a file it is not allowing me to save & throwing the error----
"No Logical Path Specified".i have taken a local file as text file with a tabular format....
thanxHi,
Please go through this link. You can achieve ur requirement with this information
Re: 2nd and 4th saturday off problem
Re: How to make every second saturday of month "OFF" for all the employees..
Workschedules generation with first saturday working rest Off
Re: Time Mgt
MVR -
Hello Experts,
I'm trying to use the following FM to check the Application Server Path but always get error 'No Path Found'. Can you please somebody have a quick look at the following code tell me my mistake.
Data: File_path(100),
File(100),
FileName(50),
FileNameWithPath(255) TYPE C.
File_path = '/usr/sap/EC1/DVEBMGS00/work'.
FileName = 'ZZAD_DS_MATERIAL_UPLOAD'.
CALL FUNCTION 'FILE_GET_NAME_USING_PATH'
EXPORTING
CLIENT = SY-MANDT
LOGICAL_PATH = File_path
OPERATING_SYSTEM = SY-OPSYS
PARAMETER_1 = ' '
PARAMETER_2 = ' '
PARAMETER_3 = ' '
USE_BUFFER = ' '
FILE_NAME = FileName
USE_PRESENTATION_SERVER = ' '
ELEMINATE_BLANKS = 'X'
IMPORTING
FILE_NAME_WITH_PATH = FileNameWithPath
EXCEPTIONS
PATH_NOT_FOUND = 1
MISSING_PARAMETER = 2
OPERATING_SYSTEM_NOT_FOUND = 3
FILE_SYSTEM_NOT_FOUND = 4
OTHERS = 5
IF SY-SUBRC <> 0.
message e000 with SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
exit.
ENDIF.
open dataset FileNameWithPath for appending in text mode encoding default.
Thanks a lot in advance.Well your logical file looks more like a physical one. In any event, the documentation for th eFM saus that "The file name must be in upper case letters, since the logical file names are stored in upper case in the Customizing tables for the platform-independent file names."
Maybe you should be filling in the parameter FILE_NAME_WITH_PATH instead.
Rob
Edited by: Rob Burbank on Oct 15, 2010 2:28 PM -
LSMW ERROR AT SPECIFYING FILES
Hi,
I am trying to create an Organization Units using PPOCE transaction code (batch input). I followed the process through until Display read files and Display Convert file.
I got this error that Unable to Read LSMWTest_OrgUnit_OrgUnit_REC.lsmw.read.
Can anyone enlighten me on why I got this error and how I can resolve it? Is it related to authorization?
Thank you in advance,
SunnyHi,
Do you mean that I should make my project and subproject name shorter becasue the file name is derived from the project and subproject name. Also, I am not sure how these files(conv and read files) are created on SAP application server. How you know how it is created?
Sunny -
Error no logical path has been specified
iam transfering inventory balance using standard object goods movement by direct
input method .when iam uploading file at step 7 specify files iam getting error as
no logical path has been specified.can someone answer for this errorAs find in forum -
You just put any, not used logical file name in your file definition step. LSMW will create this logical file byself und will use when is needed, but you just forget about it in future. Don't forget to recreate this file, when you move your LSMW to test and production systems, it is not created automaticaly there.
The way you enter logical path and logical name is,
Within the LSMW option 'Specify Files', Double click on
'Converted Data' and a popup box will allow you enter
file name , logical path and logical file.
Re: LSMW : Unable to Specify Files . Logical path incorrect ?
Hope this may help you.
Regards,
Amit -
LSMW No logical path has been specified
Dear All,
I am trying to create characteristic through LSMW. in the Specify file step i am geeing this error"No logical path has been specified".
Any body can have idea about the error?
Regards
DhirenHi Dhiren,
I have the same problem. I am trying to change a batch characteristics and I am getting the same error.
Could you please share how you resolved your issue?
Regards,
R.S
This is a old and answered thread - please open a thread for your specific query.
-Paul
Moderator
Edited by: Paul Meehan on Aug 25, 2011 11:39 AM -
Error-lsmw -in the step specify file
HI ALL,
Iam struck up in lsmw . I doing for the transaction "mb11" , opening inventory balance .
when i do the step " SPECIFY FILE " , iam getting error like "specify a logical path " . I have choosed a file on the local pc .
what would be the problem .
Plz help me in this.
thanks,
regards,
rajkasi.Just choose one of the logical files from the dropdown. This is not where you specify the file from PC. Hopefully there is one called "TEST". This is what I use for all of my LSMWs. It's just asking for a place to put the data that is read and converted.
Regards,
Rich Heilman -
hi friends,
i have been uploading using the direct input method in lsmw.it is requiring the logical path and the logical file to be given.i tried to create them using the transaction FILE.but while using that in LSMW it is giving error stating that logical path doesn't point to the physical directory.can any how let me know how to create a logical file and logical path.
thanks in advance.
-senthilkumarhi ,
goto the tcode file then u find the relation between the logical and physical paths ...and their assignment..
hope it will helps u..
regards,
venkat. -
Unable to copy file D018 error on pre-install
Hi,
We're on NW6.5 SP5 with ZFD4.01 IR6. We tried to rollout a series of
lights-out pre-install apps to workstations (NT 4.0 SP6b) on Friday and had
98 out of 262 workstations fail with the following error:
"Unable to copy file [\\unc path\939.fil] [D018]"
Workstations do have RF rights to the unc path where the nal files are
stored (via rights to the container hosting the workstations), and the macro
Source_Path is right, all the usual troubleshooting 'D018' checks are ok.
I've checked the AXT file and the Directory Create command comes before the
File Copy. Weirdly, only some of the workstations failed, and all on the
same file, which goes to c:\program files\blah\blah\blah and is called
_alphapm.exe.
To ensure this ran out ok we temporarily lowered the workstation refresh
frequency to 1 min, and the nal ran to all machines in about 6 minutes.
What could be the cause of only some of the machines failing, and all on the
same file?
Thanks,
Steve LawHi,
I've been troubleshooting this issue and now have Zenworks debug logs, which
I've managed to capture for both a machine that succesfully installed a
pre-install nal and one that failed for the same urn of the same nal. I'm
hoping someone can explain what might be happening. Here's the crucial
portion of the failed nal from zapplib.log:
This failed:
01/12/07 16:40:06.805 -- NWAPPSAGetObjectAttributes took 18 milliseconds for
OURCO_TREE
Number of Attributes: 1
1st attribute Name: App:Program Groups
DS Object Name: Lamda 5101401 PatchV2 Lightsout test
#3.Workstations.BHO.UK.SUNLIFE
Attribute list is Not NULL
01/12/07 16:40:06.805 -- This is an AOT delivered app
01/12/07 16:40:06.805 -- Start: ProcessFiles
01/12/07 16:40:06.835 -- NWAPPSAGetObjectAttributes took 18 milliseconds for
OURCO_TREE
Number of Attributes: 1
1st attribute Name: App:Copy Files
DS Object Name: Lamda 5101401 PatchV2 Lightsout test
#3.Workstations.BHO.UK.SUNLIFE
Attribute list is Not NULL
FileSettings: CreateRollbackFile szTempPath is C:\TEMP
FileSettings: CreateRollbackFile szRollbackFileName is
C:\TEMP\NAL6a42\NAL2.tmp
01/12/07 16:40:17.0 -- nwappCopyFileEx: Entering.
01/12/07 16:40:17.0 -- nwappCopyFileEx: sourceFile =
"\\Server1\APPS\Public\Template\Lamda 5101401 PatchV2-3\4.fil".
01/12/07 16:40:17.0 -- nwappCopyFileEx: targetFile =
"C:\Lamda5\Dlls\CLIENTSTATEMENTS.DLL".
01/12/07 16:40:17.0 -- nwappCopyFileEx: targetFile drive type = 3
01/12/07 16:40:17.70 -- nwappCopyFileEx: Calling GetFileVitals or
GetWebFileVitals
01/12/07 16:40:17.70 -- Starting GetFileVitals for
\\Server1\APPS\Public\Template\Lamda 5101401 PatchV2-3\4.fil
01/12/07 16:40:33.604 -- GetFileVitals: FindFirstFile Failed to find any
file matching \\Server1\APPS\Public\Template\Lamda 5101401 PatchV2-3\4.fil
01/12/07 16:40:33.604 -- Exiting GetFileVitals 53
01/12/07 16:40:33.604 -- Exiting nwappCopyFileEx with 53
01/12/07 16:40:35.536 -- Stop: ProcessFiles
01/12/07 16:40:35.556 -- NWAPPSAGetObjectAttributes took 19 milliseconds for
OURCO_TREE
Number of Attributes: 9
1st attribute Name: App:Flags
DS Object Name: Lamda 5101401 PatchV2 Lightsout test
#3.Workstations.BHO.UK.SUNLIFE
Attribute list is Not NULL
The log for the successful workstation is below. As per previous posts I
checked that the same Windows file and folder rights exist on both the
workstations, and the existing file that was to be overwritten
(C:\Lamda5\Dlls\CLIENTSTATEMENTS.DLL) was not set to read-only.
The "FindFirstFile Failed to find any file matching blah blah blah" message
suggests that the problem is related more to accessing the source file on
the server (4.fil) than in writing it to the workstation.
This was a test to 10 machines, the report shows that, chronologically, 2
workstations installed it fine and then the ensuing 8 failed. I can't think
of anything that would lock the 4.fil file - as these are reads they
shouldn't actually lock the file anyway. We run McAfee Netshield 4.63, but
it's set to scan inbound files, not outbound reads.
Any suggestions as to why it was able to read the file for one workstation
and not on another? I have had greater success when I've activated "spread
from start time" over a 15 minute period, but still had one failure out of
ten. A tool that logged all file locks would be useful but I can't find
anything.
Thanks,
Steve Law
Zapplib.log of succesful workstation:
01/12/07 16:40:01.232 -- NWAPPCheckSchedule: PREINSTALL: Found app that has
preinstall set Lamda 5101401 PatchV2 lightsout test
#2.Workstations.BHO.UK.SUNLIFE
01/12/07 16:40:01.232 -- NWAPPCheckSchedule: PREINSTALL: Found app that has
preinstall set Lamda 5101401 PatchV2 Lightsout test
#3.Workstations.BHO.UK.SUNLIFE
01/12/07 16:40:01.242 -- NWAPPCheckSchedule: PREINSTALL: App has not been
pre installed Lamda 5101401 PatchV2 Lightsout test
#3.Workstations.BHO.UK.SUNLIFE
01/12/07 16:40:01.242 -- NWAPPCheckSchedule: PREINSTALL: App has not been
pre installed and it has a schedule Lamda 5101401 PatchV2 Lightsout test
#3.Workstations.BHO.UK.SUNLIFE
01/12/07 16:40:01.242 -- NWAPPCheckSchedule: PREINSTALL: App has not been
pre installed has schedule trying it now Lamda 5101401 PatchV2 Lightsout
test #3.Workstations.BHO.UK.SUNLIFE
01/12/07 16:40:01.242 -- FORCERUN: Adding Item to force run list
01/12/07 16:40:01.242 -- Lamda 5101401 PatchV2 Lightsout test
#3.Workstations.BHO.UK.SUNLIFE
01/12/07 16:40:01.242 -- NWAPPCheckSchedule FORCERUN: we're in ws space and
the APP_USER_FORCE_RUN_WS_ASSOC flag is unset
01/12/07 16:40:01.272 -- STAGG: Found the GUID/version for WMI Agent
Downloader.Maintenance Fixes.BHO.UK.SUNLIFE
01/12/07 16:40:01.272 -- NWAPPCheckSchedule FORCERUN: we're in ws space and
the APP_USER_FORCE_RUN_WS_ASSOC flag is unset
01/12/07 16:40:01.272 -- STAGG: t has NOT been run during this session, run
it. app: Lamda Point at Production Server Auto
#1009.Lamdatest.AutoLoad.GENERAL.NAL.BHO.UK.SUNLIF E
01/12/07 16:40:01.272 -- NWAPPCheckSchedule FORCERUN: we're in ws space and
the APP_USER_FORCE_RUN_WS_ASSOC flag is unset
01/12/07 16:40:01.282 -- NWAPPCheckSchedule FORCERUN: we're in ws space and
the APP_USER_FORCE_RUN_WS_ASSOC flag is unset
01/12/07 16:40:01.282 -- STAGG: t has NOT been run during this session, run
it. app: Lamda idate reg key report.Maintenance Fixes.BHO.UK.SUNLIFE
01/12/07 16:40:01.282 -- NWAPPCheckSchedule FORCERUN: we're in ws space and
the APP_USER_FORCE_RUN_WS_ASSOC flag is unset
01/12/07 16:40:01.312 -- NWAPPCheckSchedule FORCERUN: we're in ws space and
the APP_USER_FORCE_RUN_WS_ASSOC flag is unset
01/12/07 16:40:01.312 -- STAGG: t has NOT been run during this session, run
it. app: Lamda idate reg key report0.Maintenance Fixes.BHO.UK.SUNLIFE
01/12/07 16:40:01.312 -- NWAPPCheckSchedule FORCERUN: we're in ws space and
the APP_USER_FORCE_RUN_WS_ASSOC flag is unset
01/12/07 16:40:01.342 -- STAGG: Found the GUID/version for Viruscan8 epo
fix.Maintenance Fixes.BHO.UK.SUNLIFE
01/12/07 16:40:01.342 -- NWAPPCheckSchedule FORCERUN: we're in ws space and
the APP_USER_FORCE_RUN_WS_ASSOC flag is unset
01/12/07 16:40:01.372 -- NWAPPCheckForScheduledApps::Pre-install::Lamda
5101401 PatchV2 Lightsout test #3.Workstations.BHO.UK.SUNLIFE tree
OURCO_TREE
01/12/07 16:40:01.372 -- TreeName: OURCO_TREE
01/12/07 16:40:01.372 -- UserName: LAMTEST02
00:D0:B7:14:27:61.Workstations.BHO.UK.SUNLIFE
01/12/07 16:40:01.372 -- ConnType: 2
01/12/07 16:40:01.372 -- Entering RunApplication: Lamda 5101401 PatchV2
Lightsout test #3.Workstations.BHO.UK.SUNLIFE
01/12/07 16:40:01.392 -- RegWriteGUIDEntry: No Version to write
01/12/07 16:40:01.392 -- pa.hContext structure
01/12/07 16:40:01.392 -- TreeName: OURCO_TREE
01/12/07 16:40:01.392 -- UserName: LAMTEST02
00:D0:B7:14:27:61.Workstations.BHO.UK.SUNLIFE
01/12/07 16:40:01.392 -- ConnType: 2
01/12/07 16:40:01.403 -- NWAPPNetGetObjectAttributes took 4 milliseconds for
OURCO_TREE
01/12/07 16:40:01.403 -- appLaunchApplicationWrapper::Enter
01/12/07 16:40:01.403 -- AUTHENTICATION DLL: Start
01/12/07 16:40:01.403 -- AUTHENTICATION DLL: szThirdPartyDLL =
01/12/07 16:40:01.403 -- AUTHENTICATION DLL: End
01/12/07 16:40:01.413 -- NWAPPNetGetObjectAttributes took 4 milliseconds for
OURCO_TREE
01/12/07 16:40:01.473 -- NWAPPSAGetObjectAttributes took 25 milliseconds for
OURCO_TREE
01/12/07 16:40:01.503 -- NWAPPSAGetObjectAttributes took 27 milliseconds for
OURCO_TREE
01/12/07 16:40:01.513 -- NWAPPNetGetObjectAttributes took 4 milliseconds for
OURCO_TREE
01/12/07 16:40:01.573 -- NWAPPSAGetObjectAttributes took 25 milliseconds for
OURCO_TREE
01/12/07 16:40:01.583 -- Calling NWAPPSACacheApplications for:
01/12/07 16:40:01.583 -- Calling NWAPPSACacheApplications for:
01/12/07 16:40:01.583 -- nwappsacacheapp: Creating new filstore
01/12/07 16:40:01.583 -- nwappsacacheapp: Creating new appcache
01/12/07 16:40:01.583 -- nwappsacacheapp: Calling importfrom ds
01/12/07 16:40:01.663 -- NWAPPNetGetObjectAttributes took 51 milliseconds
for OURCO_TREE
01/12/07 16:40:02.184 -- Import from DS was successful
01/12/07 16:40:02.194 -- NWAPPNetGetObjectAttributes took 4 milliseconds for
OURCO_TREE
01/12/07 16:40:02.204 -- NWAPPNetGetObjectAttributes took 4 milliseconds for
OURCO_TREE
01/12/07 16:40:02.204 -- NWAPPNetGetObjectAttributes took 4 milliseconds for
OURCO_TREE
01/12/07 16:40:02.204 -- Calling NWAPPSAAddFolderToApp for:
01/12/07 16:40:02.204 -- NWAPPSetRegValAsService: Skip Service since service
is dead or I'm the WS: CreateFile: 183
01/12/07 16:40:02.204 -- NWAPPSetRegValAsService: Skip Service since service
is dead or I'm the WS: CreateFile: 183
01/12/07 16:40:02.214 -- NWAPPNetGetObjectAttributes took 3 milliseconds for
OURCO_TREE
01/12/07 16:40:02.224 -- NWAPPNetGetObjectAttributes took 7 milliseconds for
OURCO_TREE
01/12/07 16:40:02.254 -- NWAPPSAGetObjectAttributes took 28 milliseconds for
OURCO_TREE
01/12/07 16:40:02.734 -- Exiting NWAPPSACacheApplication
01/12/07 16:40:02.774 -- NWAPPSAGetObjectAttributes took 28 milliseconds for
OURCO_TREE
01/12/07 16:40:02.784 -- LaunchApp: Lamda 5101401 PatchV2 Lightsout test
#3.Workstations.BHO.UK.SUNLIFE
01/12/07 16:40:02.784 -- Leaving NALContext Constructor
01/12/07 16:40:02.825 -- NWAPPSAGetObjectAttributes took 27 milliseconds for
OURCO_TREE
01/12/07 16:40:02.835 -- RunThirdPartyScript::Enter
01/12/07 16:40:02.865 -- NWAPPSAGetObjectAttributes took 26 milliseconds for
OURCO_TREE
01/12/07 16:40:02.895 -- NWAPPSAGetObjectAttributes took 27 milliseconds for
OURCO_TREE
01/12/07 16:40:02.925 -- NWAPPSAGetObjectAttributes took 27 milliseconds for
OURCO_TREE
01/12/07 16:40:02.925 -- RunThirdParyScript::Exit
01/12/07 16:40:02.925 -- NWAPPDistributeAppPA: Entering. App = Lamda
5101401 PatchV2 Lightsout test #3.Workstations.BHO.UK.SUNLIFE
01/12/07 16:40:02.955 -- NWAPPSAGetObjectAttributes took 27 milliseconds for
OURCO_TREE
01/12/07 16:40:02.955 -- This is an AOT distributed application
01/12/07 16:40:02.965 -- NWAPPNetGetObjectAttributes took 2 milliseconds for
OURCO_TREE
01/12/07 16:40:02.965 -- Done checking if we should distribute
01/12/07 16:40:02.965 -- Should we prompt before distributing?
01/12/07 16:40:02.965 -- Should we prompt for macros?
01/12/07 16:40:02.995 -- NWAPPSAGetObjectAttributes took 30 milliseconds for
OURCO_TREE
01/12/07 16:40:02.995 -- NWAPPPreDistributionProcess Pre Distribution Script
processing.
01/12/07 16:40:03.5 -- RunThirdPartyScript::Enter
01/12/07 16:40:03.35 -- NWAPPSAGetObjectAttributes took 27 milliseconds for
OURCO_TREE
01/12/07 16:40:03.65 -- NWAPPSAGetObjectAttributes took 27 milliseconds for
OURCO_TREE
01/12/07 16:40:03.65 -- RunThirdParyScript::Exit
01/12/07 16:40:03.95 -- NWAPPSAGetObjectAttributes took 27 milliseconds for
OURCO_TREE
01/12/07 16:40:03.125 -- NWAPPSAGetObjectAttributes took 27 milliseconds for
OURCO_TREE
01/12/07 16:40:03.145 -- NWAPPSAGetObjectAttributes took 27 milliseconds for
OURCO_TREE
01/12/07 16:40:03.175 -- NWAPPSAGetObjectAttributes took 27 milliseconds for
OURCO_TREE
01/12/07 16:40:03.205 -- NWAPPSAGetObjectAttributes took 27 milliseconds for
OURCO_TREE
01/12/07 16:40:03.205 -- This is an AOT delivered app
01/12/07 16:40:03.205 -- Start: ProcessFiles
01/12/07 16:40:03.255 -- NWAPPSAGetObjectAttributes took 27 milliseconds for
OURCO_TREE
01/12/07 16:40:03.516 -- nwappCopyFileEx: Entering.
01/12/07 16:40:03.516 -- nwappCopyFileEx: sourceFile =
"\\Server1\APPS\Public\Template\Lamda 5101401 PatchV2-3\4.fil".
01/12/07 16:40:03.516 -- nwappCopyFileEx: targetFile =
"C:\Lamda5\Dlls\CLIENTSTATEMENTS.DLL".
01/12/07 16:40:03.516 -- nwappCopyFileEx: targetFile drive type = 3
01/12/07 16:40:03.576 -- nwappCopyFileEx: Calling GetFileVitals or
GetWebFileVitals
01/12/07 16:40:03.576 -- Starting GetFileVitals for
\\Server1\APPS\Public\Template\Lamda 5101401 PatchV2-3\4.fil
01/12/07 16:40:05.849 -- GetFileVitals: FindFirstFile found a file that
matched: \\Server1\APPS\Public\Template\Lamda 5101401 PatchV2-3\4.fil
01/12/07 16:40:05.849 -- Exiting GetFileVitals 0
01/12/07 16:40:05.849 -- Starting GetFileVitals for
C:\Lamda5\Dlls\CLIENTSTATEMENTS.DLL
01/12/07 16:40:05.849 -- GetFileVitals: FindFirstFile found a file that
matched: C:\Lamda5\Dlls\CLIENTSTATEMENTS.DLL
01/12/07 16:40:05.849 -- Exiting GetFileVitals 0
01/12/07 16:40:06.239 -- ZLIBCopyFile::BEGIN copying
\\Server1\APPS\Public\Template\Lamda 5101401 PatchV2-3\4.fil to
C:\Lamda5\Dlls\CLIENTSTATEMENTS.DLL
01/12/07 16:40:06.540 -- ZLIBCopyFile::END (returning 0)
01/12/07 16:40:06.550 -- Exiting nwappCopyFileEx with 0
01/12/07 16:40:06.550 -- nwappCopyFileEx: Entering.
01/12/07 16:40:06.550 -- nwappCopyFileEx: sourceFile =
"\\Server1\APPS\Public\Template\Lamda 5101401 PatchV2-3\5.fil".
01/12/07 16:40:06.550 -- nwappCopyFileEx: targetFile =
"C:\Lamda5\Dlls\CLIENTSTATEMENTS_5101401Z03.OL D".
01/12/07 16:40:06.550 -- nwappCopyFileEx: targetFile drive type = 3
01/12/07 16:40:06.550 -- nwappCopyFileEx: Calling GetFileVitals or
GetWebFileVitals
01/12/07 16:40:06.550 -- Starting GetFileVitals for
\\Server1\APPS\Public\Template\Lamda 5101401 PatchV2-3\5.fil
01/12/07 16:40:06.550 -- GetFileVitals: FindFirstFile found a file that
matched: \\Server1\APPS\Public\Template\Lamda 5101401 PatchV2-3\5.fil
01/12/07 16:40:06.560 -- Exiting GetFileVitals 0
01/12/07 16:40:06.560 -- Starting GetFileVitals for
C:\Lamda5\Dlls\CLIENTSTATEMENTS_5101401Z03.OLD
01/12/07 16:40:06.560 -- GetFileVitals: FindFirstFile found a file that
matched: C:\Lamda5\Dlls\CLIENTSTATEMENTS_5101401Z03.OLD
01/12/07 16:40:06.560 -- Exiting GetFileVitals 0
01/12/07 16:40:06.920 -- ZLIBCopyFile::BEGIN copying
\\Server1\APPS\Public\Template\Lamda 5101401 PatchV2-3\5.fil to
C:\Lamda5\Dlls\CLIENTSTATEMENTS_5101401Z03.OLD
01/12/07 16:40:07.371 -- ZLIBCopyFile::END (returning 0)
01/12/07 16:40:07.371 -- Exiting nwappCopyFileEx with 0
01/12/07 16:40:07.371 -- nwappCopyFileEx: Entering.
01/12/07 16:40:07.371 -- nwappCopyFileEx: sourceFile =
"\\Server1\APPS\Public\Template\Lamda 5101401 PatchV2-3\6.fil".
01/12/07 16:40:07.371 -- nwappCopyFileEx: targetFile =
"C:\Lamda5\Dlls\CREATEFPDLETTER.DLL".
01/12/07 16:40:07.371 -- nwappCopyFileEx: targetFile drive type = 3
01/12/07 16:40:07.401 -- nwappCopyFileEx: Calling GetFileVitals or
GetWebFileVitals
01/12/07 16:40:07.401 -- Starting GetFileVitals for
\\Server1\APPS\Public\Template\Lamda 5101401 PatchV2-3\6.fil
01/12/07 16:40:07.401 -- GetFileVitals: FindFirstFile found a file that
matched: \\Server1\APPS\Public\Template\Lamda 5101401 PatchV2-3\6.fil
01/12/07 16:40:07.401 -- Exiting GetFileVitals 0
01/12/07 16:40:07.401 -- Starting GetFileVitals for
C:\Lamda5\Dlls\CREATEFPDLETTER.DLL
01/12/07 16:40:07.411 -- GetFileVitals: FindFirstFile found a file that
matched: C:\Lamda5\Dlls\CREATEFPDLETTER.DLL
01/12/07 16:40:07.411 -- Exiting GetFileVitals 0
01/12/07 16:40:07.651 -- ZLIBCopyFile::BEGIN copying
\\Server1\APPS\Public\Template\Lamda 5101401 PatchV2-3\6.fil to
C:\Lamda5\Dlls\CREATEFPDLETTER.DLL
01/12/07 16:40:07.782 -- ZLIBCopyFile::END (returning 0)
01/12/07 16:40:07.782 -- Exiting nwappCopyFileEx with 0
01/12/07 16:40:07.792 -- nwappCopyFileEx: Entering.
01/12/07 16:40:07.792 -- nwappCopyFileEx: sourceFile =
"\\Server1\APPS\Public\Template\Lamda 5101401 PatchV2-3\7.fil".
01/12/07 16:40:07.792 -- nwappCopyFileEx: targetFile =
"C:\Lamda5\Dlls\CREATEFPDLETTER_5101401Z03.OLD ".
01/12/07 16:40:07.792 -- nwappCopyFileEx: targetFile drive type = 3
01/12/07 16:40:07.792 -- nwappCopyFileEx: Calling GetFileVitals or
GetWebFileVitals
01/12/07 16:40:07.792 -- Starting GetFileVitals for
\\Server1\APPS\Public\Template\Lamda 5101401 PatchV2-3\7.fil
01/12/07 16:40:07.792 -- GetFileVitals: FindFirstFile found a file that
matched: \\Server1\APPS\Public\Template\Lamda 5101401 PatchV2-3\7.fil
01/12/07 16:40:07.792 -- Exiting GetFileVitals 0
01/12/07 16:40:07.792 -- Starting GetFileVitals for
C:\Lamda5\Dlls\CREATEFPDLETTER_5101401Z03.OLD
01/12/07 16:40:07.802 -- GetFileVitals: FindFirstFile found a file that
matched: C:\Lamda5\Dlls\CREATEFPDLETTER_5101401Z03.OLD
01/12/07 16:40:07.802 -- Exiting GetFileVitals 0
01/12/07 16:40:08.383 -- ZLIBCopyFile::BEGIN copying
\\Server1\APPS\Public\Template\Lamda 5101401 PatchV2-3\7.fil to
C:\Lamda5\Dlls\CREATEFPDLETTER_5101401Z03.OLD
01/12/07 16:40:08.513 -- ZLIBCopyFile::END (returning 0)
01/12/07 16:40:08.523 -- Exiting nwappCopyFileEx with 0
01/12/07 16:40:08.523 -- nwappCopyFileEx: Entering.
01/12/07 16:40:08.523 -- nwappCopyFileEx: sourceFile =
"\\Server1\APPS\Public\Template\Lamda 5101401 PatchV2-3\8.fil".
01/12/07 16:40:08.523 -- nwappCopyFileEx: targetFile =
"C:\Lamda5\Dlls\EXITSREQSETTPAY.DLL".
01/12/07 16:40:08.523 -- nwappCopyFileEx: targetFile drive type = 3
01/12/07 16:40:08.553 -- nwappCopyFileEx: Calling GetFileVitals or
GetWebFileVitals
01/12/07 16:40:08.553 -- Starting GetFileVitals for
\\Server1\APPS\Public\Template\Lamda 5101401 PatchV2-3\8.fil
01/12/07 16:40:08.553 -- GetFileVitals: FindFirstFile found a file that
matched: \\Server1\APPS\Public\Template\Lamda 5101401 PatchV2-3\8.fil
01/12/07 16:40:08.553 -- Exiting GetFileVitals 0
01/12/07 16:40:08.553 -- Starting GetFileVitals for
C:\Lamda5\Dlls\EXITSREQSETTPAY.DLL
01/12/07 16:40:08.553 -- GetFileVitals: FindFirstFile found a file that
matched: C:\Lamda5\Dlls\EXITSREQSETTPAY.DLL
01/12/07 16:40:08.553 -- Exiting GetFileVitals 0
01/12/07 16:40:08.753 -- ZLIBCopyFile::BEGIN copying
\\Server1\APPS\Public\Template\Lamda 5101401 PatchV2-3\8.fil to
C:\Lamda5\Dlls\EXITSREQSETTPAY.DLL
01/12/07 16:40:08.873 -- ZLIBCopyFile::END (returning 0)
01/12/07 16:40:08.873 -- Exiting nwappCopyFileEx with 0
01/12/07 16:40:08.873 -- nwappCopyFileEx: Entering.
01/12/07 16:40:08.873 -- nwappCopyFileEx: sourceFile =
"\\Server1\APPS\Public\Template\Lamda 5101401 PatchV2-3\9.fil".
01/12/07 16:40:08.873 -- nwappCopyFileEx: targetFile =
"C:\Lamda5\Dlls\EXITSREQSETTPAY_5101401Z02.OLD ".
01/12/07 16:40:08.873 -- nwappCopyFileEx: targetFile drive type = 3
01/12/07 16:40:08.873 -- nwappCopyFileEx: Calling GetFileVitals or
GetWebFileVitals
01/12/07 16:40:08.873 -- Starting GetFileVitals for
\\Server1\APPS\Public\Template\Lamda 5101401 PatchV2-3\9.fil
01/12/07 16:40:08.883 -- GetFileVitals: FindFirstFile found a file that
matched: \\Server1\APPS\Public\Template\Lamda 5101401 PatchV2-3\9.fil
01/12/07 16:40:08.883 -- Exiting GetFileVitals 0
01/12/07 16:40:08.883 -- Starting GetFileVitals for
C:\Lamda5\Dlls\EXITSREQSETTPAY_5101401Z02.OLD
01/12/07 16:40:08.883 -- GetFileVitals: FindFirstFile found a file that
matched: C:\Lamda5\Dlls\EXITSREQSETTPAY_5101401Z02.OLD
01/12/07 16:40:08.883 -- Exiting GetFileVitals 0
01/12/07 16:40:09.264 -- ZLIBCopyFile::BEGIN copying
\\Server1\APPS\Public\Template\Lamda 5101401 PatchV2-3\9.fil to
C:\Lamda5\Dlls\EXITSREQSETTPAY_5101401Z02.OLD
01/12/07 16:40:09.424 -- ZLIBCopyFile::END (returning 0)
01/12/07 16:40:09.424 -- Exiting nwappCopyFileEx with 0
01/12/07 16:40:09.424 -- nwappCopyFileEx: Entering.
01/12/07 16:40:09.424 -- nwappCopyFileEx: sourceFile =
"\\Server1\APPS\Public\Template\Lamda 5101401 PatchV2-3\5101401PatchV2.cmd".
01/12/07 16:40:09.424 -- nwappCopyFileEx: targetFile =
"c:\lamda5\5101401PatchV2.cmd".
01/12/07 16:40:09.424 -- nwappCopyFileEx: targetFile drive type = 3
01/12/07 16:40:09.424 -- nwappCopyFileEx: Calling GetFileVitals or
GetWebFileVitals
01/12/07 16:40:09.424 -- Starting GetFileVitals for
\\Server1\APPS\Public\Template\Lamda 5101401 PatchV2-3\5101401PatchV2.cmd
01/12/07 16:40:09.434 -- GetFileVitals: FindFirstFile found a file that
matched: \\Server1\APPS\Public\Template\Lamda 5101401
PatchV2-3\5101401PatchV2.cmd
01/12/07 16:40:09.434 -- Exiting GetFileVitals 0
01/12/07 16:40:09.434 -- Starting GetFileVitals for
c:\lamda5\5101401PatchV2.cmd
01/12/07 16:40:09.434 -- GetFileVitals: FindFirstFile found a file that
matched: c:\lamda5\5101401PatchV2.cmd
01/12/07 16:40:09.434 -- Exiting GetFileVitals 0
01/12/07 16:40:09.504 -- ZLIBCopyFile::BEGIN copying
\\Server1\APPS\Public\Template\Lamda 5101401 PatchV2-3\5101401PatchV2.cmd to
c:\lamda5\5101401PatchV2.cmd
01/12/07 16:40:09.574 -- ZLIBCopyFile::END (returning 0)
01/12/07 16:40:09.574 -- Exiting nwappCopyFileEx with 0
01/12/07 16:40:09.584 -- Stop: ProcessFiles
01/12/07 16:40:09.584 -- Start: ProcessTextFiles
01/12/07 16:40:09.614 -- NWAPPSAGetObjectAttributes took 27 milliseconds for
OURCO_TREE
01/12/07 16:40:09.624 -- Start: ProcessRegSettings
01/12/07 16:40:09.664 -- NWAPPSAGetObjectAttributes took 27 milliseconds for
OURCO_TREE
01/12/07 16:40:10.305 -- Start: ProcessINISettings
01/12/07 16:40:10.335 -- NWAPPSAGetObjectAttributes took 27 milliseconds for
OURCO_TREE
01/12/07 16:40:10.335 -- Start: ProcessGroupLnkSettings
01/12/07 16:40:10.375 -- NWAPPSAGetObjectAttributes took 43 milliseconds for
OURCO_TREE
01/12/07 16:40:10.385 -- RunThirdPartyScript::Enter
01/12/07 16:40:10.415 -- NWAPPSAGetObjectAttributes took 26 milliseconds for
OURCO_TREE
01/12/07 16:40:10.446 -- NWAPPSAGetObjectAttributes took 27 milliseconds for
OURCO_TREE
01/12/07 16:40:10.446 -- RunThirdParyScript::Exit
01/12/07 16:40:10.546 -- NWAPPSAGetObjectAttributes took 27 milliseconds for
OURCO_TREE
01/12/07 16:40:10.566 -- NWAPPNetGetObjectAttributes took 4 milliseconds for
OURCO_TREE
01/12/07 16:40:10.576 -- NWAPPNetGetObjectAttributes took 3 milliseconds for
OURCO_TREE
01/12/07 16:40:10.586 -- NWAPPNetGetObjectAttributes took 4 milliseconds for
OURCO_TREE
01/12/07 16:40:10.586 -- NWAPPNetGetObjectAttributes took 3 milliseconds for
OURCO_TREE
01/12/07 16:40:10.596 -- NWAPPNetGetObjectAttributes took 3 milliseconds for
OURCO_TREE
01/12/07 16:40:10.606 -- NWAPPNetGetObjectAttributes took 4 milliseconds for
OURCO_TREE
01/12/07 16:40:10.606 -- NWAPPNetGetObjectAttributes took 2 milliseconds for
OURCO_TREE
01/12/07 16:40:10.616 -- NWAPPNetGetObjectAttributes took 3 milliseconds for
OURCO_TREE
01/12/07 16:40:10.626 -- NWAPPNetGetObjectAttributes took 2 milliseconds for
OURCO_TREE
01/12/07 16:40:10.626 -- NWAPPNetGetObjectAttributes took 5 milliseconds for
OURCO_TREE
01/12/07 16:40:10.636 -- NWAPPNetGetObjectAttributes took 3 milliseconds for
OURCO_TREE
01/12/07 16:40:10.646 -- NWAPPNetGetObjectAttributes took 3 milliseconds for
OURCO_TREE
01/12/07 16:40:10.656 -- NWAPPNetGetObjectAttributes took 4 milliseconds for
OURCO_TREE
01/12/07 16:40:10.876 -- NWAPPNetGetObjectAttributes took 5 milliseconds for
OURCO_TREE
01/12/07 16:40:13.79 -- Write Machine GUID Entry
01/12/07 16:40:13.79 -- RegWriteGUIDEntry: No Version to write
01/12/07 16:40:13.79 -- Close stream list
01/12/07 16:40:13.79 -- Deleted szTreeName
01/12/07 16:40:13.79 -- After Calling NWAPPDistributeAppPA
01/12/07 16:40:13.79 -- Calling GetRegPromptedMacros()
01/12/07 16:40:13.79 -- Calling DistrbiuteAppAlwaysEx
01/12/07 16:40:13.89 -- NWAPPDistributeAppAlwaysPA: Entering. App = Lamda
5101401 PatchV2 Lightsout test #3.Workstations.BHO.UK.SUNLIFE
01/12/07 16:40:13.129 -- NWAPPSAGetObjectAttributes took 44 milliseconds for
OURCO_TREE
01/12/07 16:40:13.159 -- NWAPPSAGetObjectAttributes took 25 milliseconds for
OURCO_TREE
01/12/07 16:40:13.189 -- NWAPPSAGetObjectAttributes took 26 milliseconds for
OURCO_TREE
01/12/07 16:40:13.219 -- NWAPPSAGetObjectAttributes took 26 milliseconds for
OURCO_TREE
01/12/07 16:40:13.240 -- NWAPPSAGetObjectAttributes took 25 milliseconds for
OURCO_TREE
01/12/07 16:40:13.250 -- No content found in any Dist Always streams -
exiting
01/12/07 16:40:13.250 -- RegWriteGUIDEntry: No Version to write
01/12/07 16:40:13.280 -- NWAPPSAGetObjectAttributes took 26 milliseconds for
OURCO_TREE
01/12/07 16:40:13.280 -- RunThirdPartyScript::Enter
01/12/07 16:40:13.310 -- NWAPPSAGetObjectAttributes took 26 milliseconds for
OURCO_TREE
01/12/07 16:40:13.340 -- NWAPPSAGetObjectAttributes took 27 milliseconds for
OURCO_TREE
01/12/07 16:40:13.380 -- NWAPPSAGetObjectAttributes took 26 milliseconds for
OURCO_TREE
01/12/07 16:40:13.380 -- RunThirdParyScript::Exit
01/12/07 16:40:13.380 -- appLaunchApplicationWrapper::Exit 0 -
LSMW -Specify files -No logical path specified
HI,
While i specify a file in lsmw in specify files from pc front end in legacy data and i try to save. It says " no logical path specified " in the message bar.
kindly help me in this issue.
i am unable to go further as I cant specify files.
Thank in advanceHi Srivasta
You just put any, not used logical file name in your file definition step. LSMW will create this logical file byself und will use when is needed, but you just forget about it in future. Don't forget to recreate this file, when you move your LSMW to test and production systems, it is not created automaticaly there.
The way you enter logical path and logical name is,
Within the LSMW option 'Specify Files', Double click on
'Converted Data' and a popup box will allow you enter
file name , logical path and logical file.
cheers
Sameer -
LSMW: Error concerning the logical path in Specify Files step
Hi,
I am trying on an ECC 6.0 EHP6 system to upload (open) POs from an existing SAP ERP system. Since I faced some complications in batch input recording method, I decided to go with the standard batch/direct input method.
I selected object 0085 (Purchase Order) and method 0001 (Purchase Order). The program that is used is RM06EEI0. I followed all the usual steps, but in the "Specify Files" step I get the message:
'****.lsmw.conv' does not exist; edit the logical path using transaction FILE
Being aware of both the FILE and SF01 transactions, I created the logical path and file (through the FILE transaction). However, after the modification, I get the message:
Logical file '****' is not assigned to physical file '****.lsmw.conv'
There is also the related SAP Note 753511 (Logical and physical path and file name in transaction LSMW) that refers to this case.Hi,
Click on specify file radio button>Legacy data-on the PC Front end
where input file location like C:\mydocument\desktop\test.txt
and give input in Name field: mydocument
in delimiter section > select Tabular
File structure section> tick on Field order matches source structure definition
File type: Record end marker(Text file)
then press enter key and other steps as same.
Second thing you said that you have used Batch input recording
after creation and recording finish , scroll the page below on recording and put a cursor unwanted field and remove unwanted input field.
I hope your problem will resolve. you can find the steps pdf on Google search try now.
Thanks
Sanjeet Kumar -
LSMW - Logical Path/File - No logical path has been specified
Hello,
I am trying to create a LSMW with the RM06EEI0 direct input program for ME21N transaction.
At the SpecifyFiles step I get the error message "No logical path has been specified".
My dilemmas are:
1. How can I solve this error? Is the FILE transaction only solution? If yes, where and how I must define the logical path/file?
2. Why in the case of the Batch Input Recording LSMW Method this files are created automatically? (I can see them in the AL11 transaction and I didn't define them by myself).
3. Why on other system this error is just an warning message? If you look at this tutorial http://****************/Tutorials/LSMW/PO/Page4.htm at Step7.g. you can see that there is no need of defining the file/path in FILE transaction.
More info about the system I am working in:
SAP ECC 6.0.
LSMW 4.0.0. Version.
Thank you.
DanielaHi
Refer the oss note 753511 released for this kind of error you face in LSMW, I am pasting the content of the note below,
******************Note Content,
Symptom
The system issues an error message for the logical path or file when you perform the "Specify files" step in the Legacy System Migration Workbench (transaction LSMW) although you have made the correct assignment in transaction FILE.
The error messages are as follows:
The logical path <PATH> does not point to the physical directory.
The logical file <FILE> is not assigned to the physical file.
or
A logical path was not specified.
Other terms
Logical path, logical file, transaction FILE, LSM Workbench
Reason and Prerequisites
Some import interfaces that you can also use with transaction LSMW work with logical path and file names.
Transaction LSMW itself, however, works with physical file names. To be able to transfer the LSMW file with the converted data to the import program, you must specify a logical file name for the file with the converted data in addition to the physical file name. In this case, the system displays additional fields in the 'Specify files' step in which you must enter the logical path and file name.
Solution
The error messages may be due to several causes. Check the following:
Have you maintained the logical path and logical file name and have you assigned them to the physical file specified in the "File" input field of transaction LSMW?
These settings are maintained in transaction FILE.
When you use logical file and path names, you must specify the name of the physical file with its path. If you have not specified any directory, you cannot assign any directory to the logical path in transaction FILE. In this case, the system uses the SAP Home directory on the application server by default. Bear in mind that the file name must not exceed the maximum length of 45 characters, including the path.
Up to LSMW version 1.7.2 (*):
If the logical file name specified does not point to the physical file (although it should do), the system adjusts the logical file name, that is, the information in transaction FILE is changed to the entries made in transaction LSMW. This may lead to unwanted side effects if the logical file is also used somewhere else. Therefore, SAP recommend that you always use separate logical paths and file names for transaction LSMW (the problem is corrected as of LSMW version 1.8.0, see below). If the logical file does not exist yet, it will be created upon request.
As of LSMW version 1.8.0 (*):
The settings of the logical file are checked but no longer adjusted automatically as in version 1.7.2 (see above). If there are inconsistencies, the system issues an error message. If the user is authorized to maintain logical paths and file names (as for transaction FILE: "Maintenance authorization for cross-client tables"), transaction LSMW can create the logical path, the file name and the file. Due to this automatic generation, the user no longer needs to make adjustments in transaction FILE. Therefore, we especially recommend this procedure.
To display the version of transaction LSMW, select "Extras" --> "Display LSMW version" in the main menu of the initial screen.
You should also bear in mind that as of Basis Release 6.20, that is, as of LSMW version 4.0, transaction LSMW is no longer an add-on but is delivered with the standard system.
Hope this helps,
Sunil
Maybe you are looking for
-
Can't find Character styles in Pages 5. After a couple of hours of work I am about ready to jump back to Microsoft Word, which annoys me beyond belief. At least Pages 09/11 had Character styles, AND hot keys for styles (even if they were limited to F
-
What is resolution for uploading photos to Walgreens?
Hi: I just bought my first Mac computer and am trying to do the proper upload to Walgreens. I successfully installed the automated uploader. My question is from a PC, when I upload photos I have the option of choosing to upload in both a medium
-
How to have a UILabel with dynamic height?
Hi, I have a UILabel which I created it programmatically. This UILabel consists of dynamic data and has line break. I tried setting this to my UILabel: CGRect cuisineRect = CGRectMake(94, 66, 180, 50); UILabel *cuisineStr = [[UILabel alloc] initWithF
-
So I accidentally purchased 20,000 coins from hanging with friends for $99.00 and I need to cancel that purchase. How do I do that
-
Update OAS from 9.0.2.3 to 10.1.2
Hi, we are going to update our OAS version 9.0.2.3 to10.1.2. Do you know any note or documentation. Many thanks.