Trailing space issue in Unix File

Hi All,
I am facing an issue with the trailing space in Unix file content.
When the file is being created in Unix server the trailing space is getting trimmed automatically.
As per the requirement,this space should be retained in the Unix file as it is when the file is being downloaded to PC.
Is there any solution for this issue? Request your help for resolving this.
Thanks in Advance,
Savitha

Hi,
When you're writing youd data to the file (assume you're using the TRANSFER command), you could try explicitly specifying the length of the data line to write, ie.
TRANSFER data(200) TO DATASET filename.
Regards, Andy

Similar Messages

DMEE : Delete Trailing spaces in the output file..

Dear Friends
I am using a DMEE Tree t generate a payment file.
Everything is fine except that teh bank requires the trailing spaces to be deleted.
i.e. I am getting an output like below but with spaces in place of dots
:50H:/09618078222002EUR....................<CR/LF>
Sana'a............................................ <CR/LF>
:70:DMEE-TEST14.................<CR/LF>
Note:The dots represents spaces which I want to remove. The dots are added to show you the output...
The <CR/LF> is printing at the end of the field length. I mean if the field is 34 Chr long then the
<CR/LF> is getting printed at 35th Char irrexpective of teh field contents...
But the bank requires in the below format. i.e. remove the spaces thats all.
:50H:/09618078222002EUR<CR/LF>
Sana'a<CR/LF>
:70:DMEE-TEST14<CR/LF>
Can anyone help.
I am working on SAP 4.6C
Help will surely be reawrded....

Hello Sam,
I DO NOT know if i can make you understand the logic, but will give it a try )
The <CR/LF> is printing at the end of the field length. I mean if the field is 34 Chr long then the
<CR/LF> is getting printed at 35th Char irrexpective of teh field contents...
You define an element of length 35 char, then in the "Mapping Procedure" select the "Own Mapping (Atoms)" & set the "Atom Handling" as 01 (Concatenate values in element).
Then create the ATOMS: one with the value "DMEE-TEST14" & the other atom with the value "<CR/LF>
". The output will be a concatenation of the two fields )
Did you get what i wanted to tell you )
BR,
Suhas

Trailing Spaces in the output file

I am executing one script from the cron. This script extracts some data from the Oracle database and creates a spool file. But it is creating the file with lot of trailing spaces for each record.
1. If the same script is executed from the command prompt there are no trailing spaces.
2. Same script is working fine from the other box.
3. No problems in the data ( obvious from the point 1).
Any ideas why this happns only from the cron ?

Not sure why, (a code snippet would help). But there are some differences between cron and command line.
1. By default cron uses /bin/sh
2. What user are you running as in crontab?
3. The default PATH for non-root cron jobs is /usr/bin:/usr/ucb:.
4. The default PATH for root cron jobs is /usr/sbin:/usr/bin
5. Take a look at /etc/default/cron to see if the PATH is set to something you don't expect.
6. Read the manpages for cron and crontab. Lots of useful info there.
My guess is that you're picking-up a different version of a command.
HTH,
Roger S.

Disk space issue with log files

I noticed that I was running out of disk space, so I downloaded OmniDiskSweeper and ran it. Turns out that the main culprit is log files. They are located in /private/var/log/asl. However, OmniDiskSweeper won't let me delete them (it doesn't give an error message or anything--it just won't delete the files). What are these .asl files and how can I delete them? I cannot see them when I open up the Finder, so I assume they are hidden. Any help would be most appreciated. Thanks!

plarkin wrote:
I noticed that I was running out of disk space, so I downloaded OmniDiskSweeper and ran it. Turns out that the main culprit is log files. They are located in /private/var/log/asl. However, OmniDiskSweeper won't let me delete them (it doesn't give an error message or anything--it just won't delete the files). What are these .asl files and how can I delete them? I cannot see them when I open up the Finder, so I assume they are hidden.
Those log files are created by the "Apple System Log" process. The first thing I'd do is to use the Console utility to examine what's in them to see if there's anything obvious that should be fixed. In Console, open the "/var/log" item on the left, open the "asl" item, then select the first item in the list. You'll see a lot of gibberish, but you'll also see some text.
To navigate to those files in the Finder, use the menu item Go -> Go to Folder and type "/var/log/asl" (without the quotes) in the field, and click "Go".

SAP DME Nodes - Can we have leading/trailing spaces?

Hi All,
I have a requirement to populate a DME node from a REGUP value by offsetting that accordingly.
As an example: I used 1 Exit-Module where I wrote like:
C_VALUE = REGUP-<FIELD>+0(10). " The node is defined in tree as 10 Characters.
It must work properly. But I found, if REGUP-<FIELD> returns a value like '12345ABCD EFGH' [Mind the 10th position is a space] then the NODE is showing 12345ABCD only and just after immediate 9th position a COMA is coming as I am using COMA delimiter. So, an extra space shoud be there after the D which is missing.
In one word, the Trailing spaces are not coming and same is happening for Leading spaces as well. In between spaces are coming fine.
Can anybody please help me to have that Leading and Trailing spaces in DME output file?
I could not found any suitable 'Conversion Function' for that node. Is there anything?
Can we write custom 'Conversion Function'? Or any Exit/BAdI to manipulate the output?
-Thanks, Arghya

After consulting other ADF experts offline, we have come to conclusion that there is no off-the shelf component which caters to my requirement.
We are now going with complete custom solution to achieve shuttle behavior.
I am marking this query as answered.
Thanks,
Sandeep

How to remove trailing spaces in SQL PLUS spool

Hi,
I've requirement to pull data from tables and I'm using sqlplus spool to automate data fetch from various tables:
I'm using the following script for the same :
set echo off
set feedback off
set pagesize 0
set linesize 2000
set heading on
set trimspool on
Spool table1.TXT;
prompt col1|col2|col3|col4|col5
select
LTRIM(RTRIM(col1))||'|'||
LTRIM(RTRIM(col2)) ||'|'||
LTRIM(RTRIM(col3)) ||'|'||
LTRIM(RTRIM(col4)) ||'|'||
LTRIM(RTRIM(col5)) ||'|'||
from TABLE1 ;
spool off
After using trimspool on option also I'm having trailing spaces issue how to fix it?
Thanks,
Mahender.
Edited by: user518071 on Oct 11, 2010 1:05 PM

Hi,
do you need LTRIM/RTRIM? This is namely your problem. By using a function around your column Oracle reserves the maximum lenght for the column. So what do you get without those functions? Furthermore you are concatenating all the columns. This is also a function. For getting '|' in between columns you can also set a seperator by using
set colsep '|'Herald ten Dam
http://htendam.wordpress.com

How to remove trailing space-sqlldr failed OCI-30951-exceeds max length

sqlldr failed to load the xml into xdb ( table created through schema registration) because of the padded space in element 'Country' whose maximum length is defined as '3'…Is there any way to remove the extra trailing space using the control file or xdb annotation in the xsd? Thanks!
<Address>
<StreetAddress1>1 BRKSTONE SQ </StreetAddress1>
<StreetAddress2>SUITE 5 </StreetAddress2>
<City>ANDOVER </City>
<State>MA</State>
<Country>USA </Country>
<ZipCode>01810</ZipCode>
</Address>
Here is the errors I got:
kgepop: no error frame to pop to for error 30951
OCI-30951: Element or attribute at Xpath /BranchRegulatoryFiling/Branches/Branch[1]/Address/Country exceeds maximum length
Errors in file :
OCI-30951: Element or attribute at Xpath /BranchRegulatoryFiling/Branches/Branch[1]/Address/Country exceeds maximum length
----- Call Stack Trace -----
Bus Error (core dumped)
Here is my ctl file:
load data
infile *
into table xml_stg_tbl
append
reenable disabled_constraints exceptions cnstr_xcptn_tbl
xmltype(XMLDATA)(
lobfn filler char terminated by ',',
XMLDATA lobfile(lobfn) terminated by EOF
BEGINDATA
/tmp/1025552.xml
Edited by: user10954036 on Jul 27, 2009 8:12 AM

Hi,
Its good that u pasted the complete log file. In your environment you have to run this upgrade tool only once from any of the middle tier.
And with respect to your error that u got in precheck is quite simple. All u have to do is just run this script from by connecting to portal schema using sqlplus.
Run dropupg.sql
Location-------- /raid/product/OraHome_1/upgrade/temp/portal/prechktmp/dropupg.sql
Later you re-run the upgrade tool and let me know the status.
Good luck
Tanmai

Trailing space (encode base64) dn:: dWlkPWphdjg3MDIsb3U9dmVuZG9ycyxvdT1wZW

If there is a space at the end of DN, the dn will become encode base64. The DN is looked like this
dn:: dWlkPWphdjg3MDIsb3U9dmVuZG9ycyxvdT1wZW
Put an "-e" option on the ldapsearch can make the "dn:: dWlkPWphdjg3MDIsb3U9dmVuZG9ycyxvdT1wZW" becomes visible.
My question is how I can fix the "dn:: dWlkPWphdjg3MDIsb3U9dmVuZG9ycyxvdT1wZW" back to "dn: cn=abc, dc=xxx, dc=com".
Do I have to delete the whole record and remove the trailing space at the ldif file and insert the record with the fixed ldif file ? Since I have 90% records like that or around 7000 records need to be fixed, and this in production environment. I want to minimize the impact to the production users, please advise a better solution.
Thanks

It's only 7000 entries. Deleting and readding shouldn't pose too much of a problem. Might just be a little scripting involved, depending on how you want to handle the maintenance. If the entries are effectively non-functional due to the base 64 encoding on the DN already, you might not have much to lose in just extracting them to LDIF, using something like sed on the LDIF, and then doing a batch delete / add. If you want to be more sophisticated about it, you can write a script that takes each entry at a time, does some checking on it, deletes and then readds it, and logs a result. That's probably what I'd do. If the data doesn't change much and/or you can drop changes from the past day or two, you can even pull the entries out of an LDIF backup.

Transfering trailing space to unix file.

I have a variable of length (400) type c.
When I transfer this variable to a unix file and if
<b>the variable is blank or assigned 400</b> spaces nothing seems to show up in the unix file(not even the spaces).
This is the also true for structures that end with a
char component and are space filled. <b>When transferred the trailing spaces in a line are truncated</b>.
How can i overcome this if i have to write even these spaces into the file?

Hi,
Use the TRANSFER statement with LENGTH.
TRANSFER <f> to <dsn> [LENGTH <len>].
You can specify the length of the data you want to transfer using the LENGTH addition. The system then transfers the first <len> bytes into the file. If <len> is too short, excess bytes are truncated. If <len> is greater than the length of the field, the system adds trailing blanks.
OPEN DATASET FNAME FOR OUTPUT IN TEXT MODE.
TRANSFER: RECORD TO FNAME LENGTH 400,
CLOSE DATASET FNAME.
Regards,
Maha

Gui_download issue - trailing spaces getting truncated for fixed length fil

Hi All,
I have a requirement where I need to download an internal table as a fixed length file.
The code is as follows:
CALL FUNCTION 'GUI_DOWNLOAD'
EXPORTING
BIN_FILESIZE =
FILENAME = L_FILE
FILETYPE = 'ASC'
APPEND = 'X'
WRITE_FIELD_SEPARATOR = ' '
HEADER = '00'
TRUNC_TRAILING_BLANKS = ' '
WRITE_LF = ' '
COL_SELECT = ' '
COL_SELECT_MASK = ' '
DAT_MODE = ' '
IMPORTING
FILELENGTH =
TABLES
DATA_TAB = IT_TEXT
EXCEPTIONS
FILE_WRITE_ERROR = 1
NO_BATCH = 2
GUI_REFUSE_FILETRANSFER = 3
INVALID_TYPE = 4
NO_AUTHORITY = 5
UNKNOWN_ERROR = 6
HEADER_NOT_ALLOWED = 7
Each row in the internal table IT_TEXT is 242 chars long.
The FM is truncatinf the trailing blanks on the file. How do I get the FM to not truncate the trailing blanks in each row?
My internal table has multiple rows and the number of rows on the table should be same as the number of rows on the downloaded file.
I tried setting the WRITE_LF parameter to space.
In this case, the trailing spaces are not truncated(which is as per my requirement), BUT all the rows in the internal table appear in a single line on the downloaded file instead of multiple rows.
I also tried setting the TRUNC_TRAILING_BLANKS field to space but that does not work either. Spaces at the end of the row are still truncated.
so the requirement is: the spaces at the end of each row should not be truncated and
each row on the internal table should have a corresponding row on the downloaded file.
(it is a fixed length file)
I also tried using the following code
class cl_abap_char_utilities definition load.
DATA: BEGIN OF IT_TEXT OCCURS 0,
       TEXT(242) TYPE C,
       cr_lf TYPE c VALUE cl_abap_char_utilities=>cr_lf,
      END OF IT_TEXT.
when i compile, i get the following error
The type "CL_ABAP_CHAR_UTILITIES" is unknown.
Im using R/3 4.6C. Could this be a problem?
Please suggest a solution for this problem.
Thanks!
Sandeep
Edited by: sandeep reddy on Jul 25, 2008 7:16 PM

Hi,
Try this..This worked..Add a dummy character at the end of the internal table...Then pass trunc_trailing_blanks   = ' '...
PARAMETERS: p_file TYPE rlgrap-filename
            DEFAULT 'c:\test_download.txt'.
DATA: BEGIN OF s_data,
        data TYPE char10,
        dummy,      " Added this.
      END OF s_data.
DATA: t_data LIKE TABLE OF s_data.
s_data-data = 'Test'.
APPEND s_data TO t_data.
s_data-data = 'Test2'.
APPEND s_data TO t_data.
s_data-data = 'Test3'.
APPEND s_data TO t_data.
s_data-data = 'Test4'.
APPEND s_data TO t_data.
* Download.
DATA: v_file TYPE string.
v_file = p_file.
CALL FUNCTION 'GUI_DOWNLOAD'
EXPORTING
    filename                = v_file
    trunc_trailing_blanks   = ' '
TABLES
    data_tab                = t_data
EXCEPTIONS
    file_write_error        = 1
    no_batch                = 2
    gui_refuse_filetransfer = 3
    invalid_type            = 4
    no_authority            = 5
    unknown_error           = 6
    header_not_allowed      = 7
    separator_not_allowed   = 8
    filesize_not_allowed    = 9
    header_too_long         = 10
    dp_error_create         = 11
    dp_error_send           = 12
    dp_error_write          = 13
    unknown_dp_error        = 14
    access_denied           = 15
    dp_out_of_memory        = 16
    disk_full               = 17
    dp_timeout              = 18
    file_not_found          = 19
    dataprovider_exception = 20
    control_flush_error     = 21
    OTHERS                  = 22.
Thanks
Naren

File Adapter: trailing space in field using XSD:Decimal in a CSV file

Hi Folks,
I have a problem which i am unable to understand fully.
We have a SAP to file via XI scenario where a mail adapter is used. We are producing a CSV file as an mail attachment.
The issue is all the decimal fields have an extra space before the next delimiter i.e. comma.
The data type used in mapping is XSD:Decimal with 'fraction' set as 2.
I have checked the source XML and there is no trailing spaces there. Initially i thought this might be due to doing the conversion using transformation beans in mail adapter, to rule this out i checked other files produced using FILE adapter they also appear to have same issue.
I can't get my head around it, could not find any parameter i need to pass in content conversion either in MAIL adapter or FILE adapter to supress trailing space before the delimiter.
I suppose this must have occured with others as well.
Any directions would be greatly appreciated.
Btw, we are on PI 7.0 and ECC 6
-Praveen
Edited by: - External Consultants Mouchel on Sep 15, 2009 5:34 PM

Hi Mouchel,
I personally didnot encounter this kind of issue with the file adapter at any point of time. I would suggest you to check the message mapping before and after payload in sxmb_moni. If you see in mapping you may not find out, so view the source in notepad and then see.
Regards,
---Satish

DATA TRANSFER - How to get a SINGLE SPACE in downloaded txt file from UNIX?

Hi Experts,
Am sending data from SAP to UNIX/ Application server and text file on desk top as well.
So, I am keeping a single character just SPACE at the END of each record.
Then, When I see the downloaded text file, I found a SINGLE SPACE at the end of each record, fine.
Then, by using CG3Y t code, I downloaded the UNIX file to my desk top.
But, When I see this UNIX downloaded file from UNIX, I did NOT find any SPACE at the end of each record!!!
Am doing every thing same in both cases.
So,
1 - Why its happening in case of UNIX file?
2 - How to get a SINGLE SPACE at the END in the downloaded file from UNIX?
thanq

Its there, I am talking abut this -
OPEN DATASET - linefeed
Syntax
... WITH { NATIVE
         | SMART
         | UNIX
         | WINDOWS } LINEFEED ... .
Alternatives:
1. ... WITH NATIVE LINEFEED
2. ... WITH SMART LINEFEED
3. ... WITH UNIX LINEFEED
4. ... WITH WINDOWS LINEFEED
Effect
: These additions determine which line end marker is used for text files or legacy text files. If these additions are used, the profile parameter abap/NTfmode is ignored. Simultaneous specification of the values "UNIX" or "NT" in the addition TYPE is not permitted.
If these additions are not used, the line end marker is determined as follows, depending on the operating system of the current application server:
The line end marker for Unix is "LF". Under Unix, OS390 and OS400, only "LF" is used for reading and writing.
The line end marker for MS Windows is "CRLF". Under MS Windows, however, the values of the profile parameter abap/NTfmode can also be used to set whether new files are handled according to Unix conventions or Windows conventions. If the profile parameter has the value "b", the Unix line end marker "LF" is used. If the profile parameter has the value "t" or is initial, the Windows line end marker "CRLF" is used. The setting using the profile parameter can be overridden with the addition TYPE and the value "UNIX" or "NT". If an existing file is opened without the addition TYPE, this is searched for the first line end marker ("LF" or "CRLF"), and this is used for the whole file. If no line end marker is found, the profile parameter is used. This applies particularly if an existing file is completely overwritten with FOR OUTPUT.
If an addition WITH NATIVE|SMART|UNIX|WINDOWS LINEFEED is used, this setting can be changed for the open file using the statement SET DATASET. If neither of the additions is used, the line end marker also cannot be changed using SET DATASET.
Notes
: Without the use of an addition WITH LINEFEED, the line end marker is dependent on diverse implicit factors such as the operating system of the application server, a profile parameter, and line end markings that are already used. For this reason, the explicit use of WITH LINEFEED is recommended, which renders the use of the addition TYPE for setting the line end marker obsolete.
The line end marker that is currently used can be determined for every open file using GET DATASET.
Alternative 1
... WITH NATIVE LINEFEED
Effect
: This addition defines the line end marker independently of the access type according to the operating system of the application server, i.e. "LF" for Unix OS390 or OS400, and "CRLF" for MS Windows.
The line end marker is interpreted according to the current codepage. If a code page is explicitly specified using the addition CODE PAGE, the characters of the line end marker must exist be available or be written in accordance with this code page.
Note
: The addition WITH NATIVE LINEFEED is intended for editing files on an application server that can also be accessed by other means. The addition receives the appropriate line end marker without the program needing to know the operating system.
Alternative 2
... WITH SMART LINEFEED
Effect
: This addition depends on the access type:
In files that are opened for reading using FOR INPUT, both "LF" and "CRLF are interpreted as a line end marker. When opening an EBCDIC file with the addition CODEPAGE, in addition to "LF", "CRLF", and the EBCDIC character strings, the corresponding ASCII character strings are also recognized. In addition, the EBCDIC character "NL" (line separator) is also interpreted as a line end marker.
In files opened for appending or changing with FOR APPENDING or FOR UPDATE, the program searches for a line end marker that is already used in the file. In this process, first the end of the file is identified. If no line end marker is found there, a certain number of characters at the beginning is analyzed. If a line end marker is found, this is used when writing to the file. This is also affected by the addition CODE PAGE. For example, ASCII line end markers are recognized and used in a file opened with EBCDIC, but not the other way round. If no line end marker is found or no search is possible (for example, if the file is opened with the addition FILTER), the line end marker is determined according to the operating system of the application server, as with the addition WITH NATIVE LINEFEED.
In files opened for writing using FOR OUTPUT, the line end marker is determined according the operating system of the application server, as with the addition WITH NATIVE LINEFEED.
Note
: The addition WITH SMART LINEFEED is intended for the generic editing of files in heterogeneous environments. The line end marker is recognized and set for different formats. The use of this addition is the best solution for most application cases.
Alternative 3
... WITH UNIX LINEFEED
Effect
: The line end marker is set to "LF" regardless of the access type and operating system of the application server.
The line end marker is interpreted according to the current code page. If a code page is specified explicitly using the addition CODE PAGE, the characters of the line end marker must be available or be written according to this code page.
Note
: The addition WITH UNIX LINEFEED is intended for editing Unix files in which the specific line end markers are to be retained, even if the operating system of the current application server is MS Windows.
Alternative 4
... WITH WINDOWS LINEFEED
Effect
: The line end marker is set to "CRLF" regardless of the access type and operating system of the application server.
The line end marker is interpreted according to the current code page. If a code page is specified explicitly using the addition CODE PAGE, the characters of the line end marker must be available and be written according to this code page.
Note
: The addition WITH WINDOWS LINEFEED is intended for use with MS Windows files in which the specific line end marker is to be retained, even if the operating system of the current application server is Unix, OS390 or OS400.

DATA TRANSFER - How to get a SINGLE SPACE in the downloaded file from UNIX?

Hi Experts,
Am sending data from SAP to UNIX/ Application server and text file on desk top as well.
So, I am keeping a single character just SPACE at the END of each record.
Then, When I see the downloaded text file, I found a SINGLE SPACE at the end of each record, fine.
Then, by using CG3Y t code, I downloaded the UNIX file to my desk top.
But, When I see this UNIX downloaded file from UNIX, I did NOT find any SPACE at the end of each record!!!
Am doing every thing same in both cases.
So,
1 - Why its happening in case of UNIX file?
2 - How to get a SINGLE SPACE at the END in the downloaded file from UNIX?
thanq

Hi,
I don't know if this works:
perform SET_TRAIL_BLANKS(saplgrap) using 'X'.
perform SET_FIXLEN(saplgrap) using '0' '060'. "put length of your line from-to
... download ...
It will put space at the end of your line, according to the length.
Hope it works,
Chang

Trailing spaces problem during file content conversion

I have developed a proxy to file scenario.And am using file content conversion for creating the file. The file is to be a fixed length file.
File Structure
<Header>
<Item>
<Item Trailer>
<File Trailer>
Each tab in the file has the last character mapped to spaces.
Eg: Header00000001 2006011700000000020060<blank   space>
Item00000001        2006011700000000020060<blank   space>
The problem is that during file content conversion. XI does not preserve trailing spaces at the end of the line i.e.if a particular line in the file ends with space. It terminates the line at the last non-space character (in this case at 060).
However we are required to maintain these trailing spaces at the end of each line.
I have tried preserve white space in data type that does not work.
I know that xslt mapping may solve the problem but I am looking for a workaround with my current graphical mapping.
Looking for suggestions !!
Thanks,
Rashida

Hi,
I have the problem quite opposite to this where we are getting the trailing spaces at end of each record which should not come.
File structure is
<Record>
- <Data>
<Content>11/09/2007@210@ZACSL007@GBB-56436@PS01@29@1044@19@646@0</Content>
</Data>
</Record>
............. n records
<Header>
<File_Name>UK01</File_Name>
</Header>
Record structure in communication channel used is
Header, Data
Data.fieldFixedLengths     1024
Data.addHeaderLine     0
Header.addHeaderLine     0
Header.fieldFixedLengths     0
Header.fixedLengthTooShortHandling     Cut
Data.fixedLengthTooShortHandling     Cut
Header.endSeparator     '0'
Actually if the length of record is less than 1024, rest of the length is being filled with spaces which should not occur.
Many advanced thanks.
Jitender

Opening a file for write access [trailing spaces required]

Hi,
i am opening a file for write access using:
OPEN DATASET W_FILENAME FOR OUTPUT IN TEXT MODE.
However, when i perform transfer W_LINE to W_FILENAME, trailing spaces in W_LINE are trimmed off automatically. I have tried various methods without success.
Appreciate if help can be offered. Thank You~

haiiiiiii,
OPEN DATASET OUTFILE FOR OUTPUT IN TEXT MODE encoding default.
TRANSFER OUTREC TO OUTFILE.
CLOSE DATASET OUTFILE.
here out rec we are moving to the out put file.
for ur requrement concatinate all the fioelds to outrec and then move it to file.
then u wont get any problems with spaces

Trailing space issue in Unix File

Similar Messages

Maybe you are looking for