Leading zeroes when loading data

Hi ,
I have infobject 0gl_account being used in production . I am now using it in a custom ods also.
however , when i load data into the ods , GL account field gets loaded with leading zeroes.
when i load master data to 0gl_account, there are no leading zeroes . My ODS activation gives
an error saying NO SID exists for gl acct 000999999 , whereas gl acct 999999 exists in the
master data.
I can change settings of 0gl_account as it is already being used in production . is there
a way to resolve this without creating a custom infoobject .
pls guide
thanks

Hi,
this sounds very strange, because normally the master data should come with leading zeroes. Additionally the conversion exit ALPHA is switched on for infoobject 0gl_account. Make sure that everything is set up correctly and your master data gets loaded correctly.
regards
Siggi

Similar Messages

Leading zeros when loading file into BPS

Hi all,
i'm trying to load a flat file into BPS cube via sap GUI according to the indication of the correspondent "How to paper".
As first column i have cost center (10 ch lenght). Usually in the File the leading zeros are not specified and in the paper it's specified to pay extra attention to those zeros.
So the question is:
HAVE i to include leading zeros in the file (for cost center)? Is it a mandatory task?
Thanks in advance.
Fabio

Hi Anand,
Is it possible to load Excel or CSV file into BPS using the standard function module ?
If we use CSV format, then the leading zeros should be wiped out anyway.
I tried both format. None of them working. Is only TXT format allowed ?
Your help is much appreciated.
Regards,
Manish Jain

Errors when loading data to ODS

Hi,
I am getting the following dump when loading data to ODS
whta might be the problem
Runtime Error          MESSAGE_TYPE_X
Date and Time          29.09.2006 14:26:52
ShrtText
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
is especially useful if you want to keep a particular message.
Error analysis
Short text of error message:
Test message: SDOK_GET_PHIO_ACCESS 001
Technical information about the message:
Message classe...... "1R"
Number.............. 000
Variable 1.......... "SDOK_GET_PHIO_ACCESS"
Variable 2.......... 001
Variable 3.......... " "
Variable 4.......... " "
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"MESSAGE_TYPE_X" C
"SAPLSDCL" or "LSDCLF00"
"INTERNAL_ERROR"
If you cannot solve the problem yourself and you wish to send
an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
To obtain this, select in the current display "System->List->
Save->Local File (unconverted)".
2. A suitable printout of the system log
To obtain this, call the system log through transaction SM21.
Limit the time interval to 10 minutes before and 5 minutes
after the short dump. In the display, then select the function
"System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, select the Editor function "Further Utilities->
Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
System environment
SAP Release.............. "640"
Application server....... "bomw093a"
Network address.......... "132.186.125.66"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "4x Intel 801586"
Character length......... 8 Bits
Pointer length........... 32 Bits
Work process number...... 16
Short dump setting....... "full"
Database server.......... "BOMW093A"
Database type............ "ORACLE"
Database name............ "BIW"
Database owner........... "SAPDAT"
Character set............ "English_United State"
SAP kernel............... "640"
Created on............... "Nov 4 2004 23:26:03"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "OCI_920_SHARE "
Patch level.............. "43"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.1.7.., ORACLE 9.2.0.."
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Memory usage.............
Roll..................... 8112
EM....................... 6271776
Heap..................... 0
Page..................... 24576
MM Used.................. 3921120
MM Free.................. 258392
SAP Release.............. "640"
User and Transaction
Client.............. 800
User................ "IC881147"
Language key........ "E"
Transaction......... " "
Program............. "SAPLSDCL"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "SAPLSDCL" in "INTERNAL_ERROR".
The main program was "RSRD_BROADCAST_PROCESSOR ".
The termination occurred in line 25 of the source code of the (Include)
program "LSDCLF00"
of the source code of program "LSDCLF00" (when calling the editor 250).
The program "SAPLSDCL" was started as a background job.
Job name........ "SECOQUERY"
Job initiator... "IC881147"
Job number...... 14265102
Source Code Extract
Line
SourceCde
1
2
INCLUDE LSDCLF00                                                   *
3
4
5
6
      FORM INTERNAL_ERROR                                           *
7
8
      Handles unexpected error conditions (internal errors)
9
10
--> VALUE(U_ROUTINE)    Routine/function module where error occured
11
--> VALUE(U_ERROR_CODE) Identifier in routine (e.g. number)
12
--> VALUE(U_VAR1)       Variable containing further information
13
--> VALUE(U_VAR2)       Variable containing further information
14
--> VALUE(U_VAR3)       Variable containing further information
15
--> VALUE(U_VAR4)       Variable containing further information
16
17
form internal_error
18
using value(u_routine)
19
value(u_error_code)
20
value(u_var1)
21
value(u_var2)
22
value(u_var3)
23
value(u_var4).
24
>>>>>
message x000 with u_routine u_error_code u_var1 u_var2.
26
27
endform.
28
29
30
*&      Form BAD_OBJECT_TO_SYMSG
31
32
      maps error information in u_bad_object into system message
33
      variables
34
35
--> VALUE(U_BAD_OBJECT) structure containing error information
36
37
form bad_object_to_symsg
38
using value(u_bad_object) type sdokerrmsg.
39
40
sy-msgid = u_bad_object-id.
41
sy-msgty = u_bad_object-type.
42
sy-msgno = u_bad_object-no.
43
sy-msgv1 = u_bad_object-v1.
44
sy-msgv2 = u_bad_object-v2.
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
1
SY-DBCNT
4
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
Report Dissemaintion Framework: Executing the Transferred Settings
SY-MSGTY
X
SY-MSGID
1R
SY-MSGNO
000
SY-MSGV1
SDOK_GET_PHIO_ACCESS
SY-MSGV2
001
SY-MSGV3
SY-MSGV4
Active Calls/Events
No.   Ty.          Program                             Include                             Line
Name
15 FORM         SAPLSDCL                            LSDCLF00                               25
INTERNAL_ERROR
14 FORM         SAPLSDCI                            LSDCIU13                              303
PHIO_GET_CONTENT_ACCESS
13 FUNCTION     SAPLSDCI                            LSDCIU13                              113
SDOK_PHIO_GET_CONTENT_ACCESS
12 FUNCTION     SAPLSKWF_CONTENT                    LSKWF_CONTENTU02                       63
SKWF_PHIO_CONTENT_ACCESS_GET
11 METHOD       CL_RSRA_KWF_UTILITIES=========CP    CL_RSRA_KWF_UTILITIES=========CM00B    50
CL_RSRA_KWF_UTILITIES=>COPY_MIME_TO_FOLDER
10 METHOD       CL_RSRA_KWF_TMPL==============CP    CL_RSRA_KWF_TMPL==============CM002    28
CL_RSRA_KWF_TMPL=>GET_STYLESHEET
9 METHOD       CL_RSRA_KWF_TMPL==============CP    CL_RSRA_KWF_TMPL==============CM001   227
CL_RSRA_KWF_TMPL=>CONSTRUCTOR
8 METHOD       CL_RSRA_ENGINE_BC=============CP    CL_RSRA_ENGINE_BC=============CM010     9
CL_RSRA_ENGINE_BC=>SET_TEMPLATE_FOLDER
7 METHOD       CL_RSRA_ENGINE_BC=============CP    CL_RSRA_ENGINE_BC=============CM001    75
CL_RSRA_ENGINE_BC=>CONSTRUCTOR
6 METHOD       CL_RSRA_JOB===================CP    CL_RSRA_JOB===================CM003    47
CL_RSRA_JOB=>EXECUTE_SINGLE
5 METHOD       CL_RSRA_JOB===================CP    CL_RSRA_JOB===================CM00E    14
CL_RSRA_JOB=>EXECUTE_SINGLE_RC
4 METHOD       CL_RSRD_PRODUCER_RA===========CP    CL_RSRD_PRODUCER_RA===========CM001   147
CL_RSRD_PRODUCER_RA=>IF_RSRD_F_PRODUCER_RT~PRODUCE
3 METHOD       CL_RSRD_SETTING===============CP    CL_RSRD_SETTING===============CM005    28
CL_RSRD_SETTING=>EXECUTE_NODES
2 METHOD       CL_RSRD_SETTING===============CP    CL_RSRD_SETTING===============CM002    73
CL_RSRD_SETTING=>EXECUTE
1 EVENT        RSRD_BROADCAST_PROCESSOR            RSRD_BROADCAST_PROCESSOR              197
START-OF-SELECTION
Chosen variables
Name
Val.
No.      15 Ty.          FORM
Name INTERNAL_ERROR
U_ROUTINE
SDOK_GET_PHIO_ACCESS
54445445554445444455
34FBF754F089FF133533
SY-MSGV1
SDOK_GET_PHIO_ACCESS
54445445554445444455222222222222222222222222222222
34FBF754F089FF133533000000000000000000000000000000
U_ERROR_CODE
001
333
001
SY-MSGV2
001
33322222222222222222222222222222222222222222222222
00100000000000000000000000000000000000000000000000
U_VAR1
2
0
SY-MSGV3
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
SDOKI_MODE_DELETE
5
0000
5000
U_VAR2
2
0
SY-MSGV4
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
No.      14 Ty.          FORM
Name PHIO_GET_CONTENT_ACCESS
SYST
####################################################A#######P###############è#################
0000000000000000000000000000000000000000000000000000400000005000000000000000E00000000000000000
0000000010002000000000000000000000000000400000001000100010000000000000000000840000000000000000
PHIO_OBJECT_ID-CLASS
2222222222
0000000000
DUMMY_VERSTYPE
0
3
0
DUMMY_FCT_EXPORT
222222222222222222222222222222
000000000000000000000000000000
DUMMY_FCT_IMPORT
222222222222222222222222222222
000000000000000000000000000000
DUMMY_FCT_DELETE
222222222222222222222222222222
000000000000000000000000000000
FCT_VIEW
222222222222222222222222222222
000000000000000000000000000000
BUFF_XPIRE
000000000000
333333333333
000000000000
NO_BUFFER
2
0
SUBRC_AUX
3
0000
3000
SDOKA_EVENT_PH_FROM_REL_PRE
0022
3333
0022
SCREEN
%_17SNS0001592815_%_%_%_%_%_%_
2533545333333333352525252525252222222222222222222222222222222222222222222222222222222222222222
5F173E30001592815F5F5F5F5F5F5F0000000000000000000000000000000000000000000000000000000000000000
<%_TABLE_SDOKSTRE>
SY-XFORM
CONVERSION_EXIT
444545544454545222222222222222
3FE65239FEF5894000000000000000
CONTEXT[]
Table IT_5544[0x89]
FUNCTION=SKWF_PHIO_CONTENT_ACCESS_GETDATA=CONTEXT[]
Table reference: 324
TABH+ 0(20) = 00000000801CE03C0000000044010000A8150000
TABH+ 20(20) = 0000000059000000FFFFFFFF047B0200D00E0000
TABH+ 40( 8) = 10000000C1248000
store        = 0x00000000
ext1         = 0x801CE03C
shmId        = 0     (0x00000000)
id           = 324   (0x44010000)
label        = 5544 (0xA8150000)
fill         = 0     (0x00000000)
leng         = 89    (0x59000000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000058
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 2     (cmpSingleMcmpR)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = Not allocated
pghook       = Not allocated
idxPtr       = Not allocated
refCount     = Not allocated
tstRefCount = Not allocated
lineAdmin    = Not allocated
lineAlloc    = Not allocated
store_id     = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook      = 0x00000000
hsdir        = 0x00000000
ext2         = 0x381CE03C
>>>>> 2nd level extension part <<<<<
tabhBack     = 0x98DC033D
delta_head   = 000000000000000000000000000000000000000000000000000000000000000000000000
pb_func      = 0x00000000
pb_handle    = 0x00000000
CONTEXT
22222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
PROPERTIES[]
Table[initial]
PROPERTIES
22222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
No.      13 Ty.          FUNCTION
Name SDOK_PHIO_GET_CONTENT_ACCESS
ALLOW_MODEL
2
0
CACHE_SERVER
0000000000
2222222222222222222222222222222222222222222222222222222222222222333333333322222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
CLIENT
800
333
800
CONTENT_ONLY
X
5
8
CONTENT_OR_URL_ONLY
2
0
OBJECT_ID
222222222222222222222222222222222222222222
000000000000000000000000000000000000000000
RAW_MODE
2
0
TEXT_AS_STREAM
X
5
8
USE_URL_AT
2
0
ACCESS_MODE
00
33
00
DOCUMENT_HTTPS_URL
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
DOCUMENT_URL
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
MODEL_RETURNED
2
0
COMPONENTS[]
Table[initial]
COMPONENT_ACCESS[]
Table IT_5533[0x8616]
CLASS=CL_RSRA_KWF_UTILITIESMETHOD=COPY_MIME_TO_FOLDERDATA=L_T_COMPONENT_ACCESS
Table reference: 337
TABH+ 0(20) = 00000000481BE03C00000000510100009D150000
TABH+ 20(20) = 00000000A8210000FFFFFFFF04C5010088190000
TABH+ 40( 8) = 01000000C1248000
store        = 0x00000000
ext1         = 0x481BE03C
shmId        = 0     (0x00000000)
id           = 337   (0x51010000)
label        = 5533 (0x9D150000)
fill         = 0     (0x00000000)
leng         = 8616 (0xA8210000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000107
occu         = 1     (0x01000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 2     (cmpSingleMcmpR)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = Not allocated
pghook       = Not allocated
idxPtr       = Not allocated
refCount     = Not allocated
tstRefCount = Not allocated
lineAdmin    = Not allocated
lineAlloc    = Not allocated
store_id     = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook      = 0x00000000
hsdir        = 0x00000000
ext2         = 0x001BE03C
>>>>> 2nd level extension part <<<<<
tabhBack     = 0x985D043D
delta_head   = 000000000000000000000000000000000000000000000000000000000000000000000000
pb_func      = 0x00000000
pb_handle    = 0x00000000
CONTEXT[]
Table IT_5544[0x89]
FILE_CONTENT_ASCII[]
Table IT_5534[0x1022]
CLASS=CL_RSRA_KWF_UTILITIESMETHOD=COPY_MIME_TO_FOLDERDATA=L_T_FILE_CONTENT_ASCII
Table reference: 312
TABH+ 0(20) = 00000000B01BE03C00000000380100009E150000
TABH+ 20(20) = 00000000FE030000FFFFFFFF04C50100D81A0000
TABH+ 40( 8) = 10000000C1248000
store        = 0x00000000
ext1         = 0xB01BE03C
shmId        = 0     (0x00000000)
id           = 312   (0x38010000)
label        = 5534 (0x9E150000)
fill         = 0     (0x00000000)
leng         = 1022 (0xFE030000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000113
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 2     (cmpSingleMcmpR)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = Not allocated
pghook       = Not allocated
idxPtr       = Not allocated
refCount     = Not allocated
tstRefCount = Not allocated
lineAdmin    = Not allocated
lineAlloc    = Not allocated
store_id     = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook      = 0x00000000
hsdir        = 0x00000000
ext2         = 0x681BE03C
>>>>> 2nd level extension part <<<<<
tabhBack     = 0xB813043D
delta_head   = 000000000000000000000000000000000000000000000000000000000000000000000000
pb_func      = 0x00000000
pb_handle    = 0x00000000
FILE_CONTENT_BINARY[]
Table IT_5535[0x1022]
CLASS=CL_RSRA_KWF_UTILITIESMETHOD=COPY_MIME_TO_FOLDERDATA=L_T_FILE_CONTENT_BINARY
Table reference: 325
TABH+ 0(20) = 00000000181CE03C00000000450100009F150000
TABH+ 20(20) = 00000000FE030000FFFFFFFF04C50100101B0000
TABH+ 40( 8) = 10000000C1248000
store        = 0x00000000
ext1         = 0x181CE03C
shmId        = 0     (0x00000000)
id           = 325   (0x45010000)
label        = 5535 (0x9F150000)
fill         = 0     (0x00000000)
leng         = 1022 (0xFE030000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000114
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 2     (cmpSingleMcmpR)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = Not allocated
pghook       = Not allocated
idxPtr       = Not allocated
refCount     = Not allocated
tstRefCount = Not allocated
lineAdmin    = Not allocated
lineAlloc    = Not allocated
store_id     = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook      = 0x00000000
hsdir        = 0x00000000
ext2         = 0xD01BE03C
>>>>> 2nd level extension part <<<<<
tabhBack     = 0xC08FD33C
delta_head   = 000000000000000000000000000000000000000000000000000000000000000000000000
pb_func      = 0x00000000
pb_handle    = 0x00000000
PROPERTIES[]
Table[initial]
COMPONENT_ACCESS
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
FILE_CONTENT_ASCII
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
FILE_CONTENT_BINARY
0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
OBJECT_ID_AUX
222222222222222222222222222222222222222222
000000000000000000000000000000000000000000
X_DOCUMENT_URL
X
5
8
X_DOCUMENT_HTTPS_URL
X
5
8
X_COMPONENT_ACCESS
X
5
8
SUBRC_AUX
0
0000
0000
%_DUMMY$$
2222
0000
%_SPACE
2
0
SY-REPID
SAPLSDCI
5454544422222222222222222222222222222222
310C343900000000000000000000000000000000
No.      12 Ty.          FUNCTION
Name SKWF_PHIO_CONTENT_ACCESS_GET
CACHE_SERVER
0000000000
2222222222222222222222222222222222222222222222222222222222222222333333333322222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
PHIO
2222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000
USE_URL_AT
2
0
X_ALLOW_MODEL
2
0
X_CONTENT_ONLY
X
5
8
X_CONTENT_OR_URL_ONLY
2
0
X_RAW_MODE
2
0
X_TEXT_AS_STREAM
X
5
8
ACCESS_MODE
00
33
00
DOCUMENT_HTTPS_URL
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
DOCUMENT_URL
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ERROR
000
2222222222222222222223332222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
X_MODEL_RETURNED
2
0
COMPONENT_ACCESS[]
Table IT_5533[0x8616]
CONTEXT[]
Table IT_5544[0x89]
FILE_CONTENT_ASCII[]
Table IT_5534[0x1022]
FILE_CONTENT_BINARY[]
Table IT_5535[0x1022]
PROPERTIES[]
Table[initial]
SKWFA_C_ACT_READ
03
33
03
SYST-REPID
SAPLSKWF_CONTENT
5454545454445445222222222222222222222222
310C3B76F3FE45E4000000000000000000000000
%_ARCHIVE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
PHIO+1(42)
222222222222222222222222222222222222222222
000000000000000000000000000000000000000000
CL_ABAP_TABLEDESCR=>TABLEKIND_STD
S
5
3
SKWFC_YES
X
5
8
No.      11 Ty.          METHOD
Name CL_RSRA_KWF_UTILITIES=>COPY_MIME_TO_FOLDER
I_S_MIME_IO
FM_FOLDER 3AA00E1E0D0E3DCBE10000000A1144B5
4454444452234433434343434444333333334333343
6DF6FC4520031100515040534325100000001114425
I_S_FOLDER_IO
FBW_FLD    08BSWBLVV6N1IJCIG3VHEX2H8
4455444222233455445534344444354453432222222
627F6C40000082372C666E19A397368582880000000
L_T_PROPERTY_REQUEST
Table IT_5512[1x25]
CLASS=CL_RSRA_KWF_UTILITIESMETHOD=COPY_MIME_TO_FOLDERDATA=L_T_PROPERTY_REQUEST
Table reference: 316
TABH+ 0(20) = 28D5D23C68D5D23C000000003C01000088150000
TABH+ 20(20) = 0100000019000000FFFFFFFF04C5010038110000
TABH+ 40( 8) = 10000000C1248400
store        = 0x28D5D23C
ext1         = 0x68D5D23C
shmId        = 0     (0x00000000)
id           = 316   (0x3C010000)
label        = 5512 (0x88150000)
fill         = 1     (0x01000000)
leng         = 25    (0x19000000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000069
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 2     (cmpSingleMcmpR)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0xC00BE03C
pghook       = 0x00000000
idxPtr       = 0x00000000
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x10000000)
lineAlloc    = 16    (0x10000000)
store_id     = 3644 (0x3C0E0000)
shmIsReadOnly = 0     (0x00000000)
>>>>> 1st level extension part <<<<<
regHook      = 0x00000000
hsdir        = 0x00000000
ext2         = 0x600DE03C
>>>>> 2nd level extension part <<<<<
tabhBack     = 0x98D5033D
delta_head   = 000000000000000000000000000000000000000000000000000000000000000000000000
pb_func      = 0x00000000
pb_handle    = 0x00000000
L_S_PROPERTY_REQUEST
KW_RELATIVE_URL
4555444545455542222222222
B7F25C14965F52C0000000000
L_T_PHIO
Table IT_5494[1x43]
CLASS=CL_RSRA_KWF_UTILITIESMETHOD=COPY_MIME_TO_FOLDERDATA=L_T_PHIO
Table reference: 309
TABH+ 0(20) = E8D4D23CE0D3D23C000000003501000076150000
TABH+ 20(20) = 010000002B000000FFFFFFFF04C5010018120000
TABH+ 40( 8) = 10000000C1248000
store        = 0xE8D4D23C
ext1         = 0xE0D3D23C
shmId        = 0     (0x00000000)
id           = 309   (0x35010000)
label        = 5494 (0x76150000)
fill         = 1     (0x01000000)
leng         = 43    (0x2B000000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000073
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 2     (cmpSingleMcmpR)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x2010E03C
pghook       = 0x00000000
idxPtr       = 0x00000000
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x10000000)
lineAlloc    = 16    (0x10000000)
store_id     = 3643 (0x3B0E0000)
shmIsReadOnly = 0     (0x00000000)

Hi priya,
Not sure: check syntax in your Update Roules, also at level of start routine.
Ciao.
Riccardo.

Error when loading data

Hi,
Please need help!
I get a strange error message when loading data from R/3 to BW. A lot of rows in the PSA get red with following description (I don't recognize the object REQUESTER):
"InfoObject REQUESTER does not contain alpa-conforming value 3511"
The help says:
"Diagnosis
The system checked whether the loaded InfoObject
value conforms to the conversion exit.The check
failed.
Forexample:
The value '1' was loaded into an InfoObject with alpha exit, even though the value '0000000001' was expected.
Systemresponse
The load process has failed or the erroneous records are displayed in the monitor. This does not depend on how error handling is set up.
                                                         Procedure
Find out why the data does not conform to the conversion exit, and, if possible, correct the cause. Possible causes are errors in Business Content or an error in a customer exit in the source system.
                                                         If you cannot correct the problem, you have the option of removing the conversion exit on the InfoObject. However, since the system has already been converted, duplicates appear in the system again.

Senor Roberto
I seem to have similar problem, the ALPHA conversion is existent at my Infoobject level and in my Comm Struc but not in mY Transfer_Structure/Transfer_Rules_.
I have already been running loads from ods to data target no problem and now out of a sudden the error msg
Err mess: "The value '1' was loaded into an InfoObject with alpha exit, even though the value '0000000001' was expected", appears.
I have tried removing alpha conversion from info object as u have recommended, and I have transported to QA but in QA the infooject status color is grey and it dosen't allow me to activate what should i do? What i would really like is to load ods data to data target without ever seeing this error again .
Any thoughts
Ciao

Want to use sequence object of oracle when loading data in sql loader

Hi,
I want to use sequence when loading data in sqll loader, but the problem is i could not use sequence object of oracle to load the data by sql loader, i can use sequence of sql loader.
I want to use sequence object because in later entries this sequence object will be used.If i use sequence of sql loader how can i use oracle sequence object
Is there any other option

I have a simillar problem, I also want to use a sequence when loading data by the SQL Loader.
My control file is:
load data
infile '0testdata.txt'
into table robertl.tbltest
fields terminated by X'09'
trailing nullcols
(redbrojunos,
broj,
dolazak,
odlazak nullif odlazak=blanks,
komentar nullif komentar=blanks)
And the datafile is:
robertl.brojilo.nextval     1368     17.06.2003 08:02:46     17.06.2003 16:17:18
robertl.brojilo.nextval     2363     17.06.2003 08:18:18     17.06.2003 16:21:52
robertl.brojilo.nextval     7821     17.06.2003 08:29:22     17.06.2003 16:21:59
robertl.brojilo.nextval     0408     17.06.2003 11:20:27     17.06.2003 18:33:00     ispit
robertl.brojilo.nextval     1111     17.06.2003 11:30:58     17.06.2003 16:09:34     Odlazak na ispit
robertl.brojilo.nextval     6129     17.06.2003 14:02:42     17.06.2003 16:23:23     seminar
But all records were rejected by the Loader, for every record I get the error:
Record 1: Rejected - Error on table ROBERTL.TBLTEST, column REDBROJUNOS.
ORA-01722: invalid number

ABAP short dump when loading data into Infocube

Hello All,
I am getting an ABAP short dump error when loading data into Infocube. I tried to load data from PSA and ODS.
I ran the code to compress the Infocube, no improvement still getting the same error.
Error Analysis:
A raise statement in the program "SAPLRSDU_PART" raised in the exception.
Internal Notes:
The termination occured in the function "ab_i fune" of the SAP Basis system. Specifically in the line 2316 of the module "//bas/620/src/krn/runt/abfunc. C#18".
The internal operation just processed is "FUNE"
Advance thanks !!!
Siv

Hello Siv,
try to run program SAP_DROP_EMPTY_FPARTITIONS to display existing partitions. Then compare it to the number of uncompressed requests. Maybe there's a mismatch.
SAP notes that might help: 385163, 590370
Regards,
Marc
SAP NetWeaver RIG, US BI

Error FAGL_SKF008 when loading data from 0FI_GL_8 infosource

Hi,
I am loading data into an infocube, from 0FI_GL_8 infosource.
We have connected ECC-P with BI-D and BI-P.
When loading data into BI-D works Ok, but when loading data into BI-P, the next error message appears:
"No authorization for displaying statistical key figures in General Ledger"
"FAGL_SKF 8"
I cheked ST22 and SM21 in ECC-P and there is no error message.
I cheked rfcuser in ECC-P and it has SAP_ALL.
any ideas???

Do a comparison of the Authorization Objects assigned to the account for your BI-D extractions and that for BI-P. Since the source system is the same and the authorizations are there for BI-D, it sounds as if there's gaps in the Authorization Object assignements for one or more of the Profiles assigned to the system account for BI-P.
The other thing would be to create a test account that looks like the system account for BI-P, logon with that account, do an RSA3 extraction test and if it fails get a screenshot from tcode SU53 to see what Authorization Objects are missing to be authorized to hit that data.
Edited by: Dennis Scoville on Jul 17, 2009 12:43 PM

Truncation of leading Zeros when Down Loading into Excel - OLE Objects

Hi,
Can any one help me on this.
I am using <b>OLE Objects</b> to download Data into Excel Sheet. Data with leading Zeros is getting truncated in Excel.
Ex: Report Output is showing Plant Number as 0002. But when i am downloading to Excel Plant value will become 2 .
   I would like to have it as 0002 in Excel.
I have declared Werks as CHAR of 4.I am using OLE Obects for Downloading into Excel Sheet.
I am using "OLE2_OBJECT" I can not use any other FMs to down load to Excel.As i am modifying this program not creating.
Thanks In Advance.
K.Nirmala
Message was edited by: Nirmala Reddy

Hi Nirmala,
While downloading to excel sheet, u need to change the number format of cell from General to Text, then leading zero's won't get deleted. For that u need to set the property of the cell. Please check this sample code,
INCLUDE OLE2INCL.
tables : zobrent.
data : it_kna1 type table of zobrent with header line.
handles for OLE objects
DATA: H_EXCEL TYPE OLE2_OBJECT,        " Excel object
      H_MAPL TYPE OLE2_OBJECT,         " list of workbooks
      H_MAP TYPE OLE2_OBJECT,          " workbook
      H_ZL TYPE OLE2_OBJECT,           " cell
      H_F TYPE OLE2_OBJECT.            " font
DATA H TYPE I.
DATA: cell1 TYPE ole2_object.
*&   Event START-OF-SELECTION
START-OF-SELECTION.
select * from zobrent into table it_kna1
           where zopanid = '10001'
            and zo_brent = '050'.
start Excel
CREATE OBJECT H_EXCEL 'EXCEL.APPLICATION'.
PERFORM ERR_HDL.
SET PROPERTY OF H_EXCEL 'Visible' = 1.
get list of workbooks, initially empty
CALL METHOD OF H_EXCEL 'Workbooks' = H_MAPL.
PERFORM ERR_HDL.
add a new workbook
CALL METHOD OF H_MAPL 'Add' = H_MAP.
PERFORM ERR_HDL.
output column headings to active Excel sheet
PERFORM FILL_CELL USING 1 1 1 'EDate'.
PERFORM FILL_CELL USING 1 2 1 'Brent'.
PERFORM FILL_CELL USING 1 3 1 'Zopanid'.
PERFORM FILL_CELL USING 1 4 1 'Contract Type'.
PERFORM FILL_CELL USING 1 5 1 'Price Type'.
PERFORM FILL_CELL USING 1 6 1 'Installation Type'.
PERFORM FILL_CELL USING 1 7 1 'Volume'.
PERFORM FILL_CELL USING 1 8 1 'AQ'.
PERFORM FILL_CELL USING 1 9 1 '00000123'.
LOOP AT IT_KNA1.
copy values to active EXCEL sheet
    H = SY-TABIX + 1.
    PERFORM FILL_CELL USING H 1 0 IT_KNA1-zo_effdat.
    PERFORM FILL_CELL USING H 2 0 IT_KNA1-zo_brent.
    PERFORM FILL_CELL USING H 3 0 IT_KNA1-zopanid.
ENDLOOP.
CALL METHOD OF h_excel 'Cells' = cell1
    EXPORTING
      #1 = 1
      #2 = 1.
FREE OBJECT H_EXCEL.
PERFORM ERR_HDL.
if sy-subrc eq 0.
   write : / 'year'(001).
endif.
     FORM FILL_CELL
sets cell at coordinates i,j to value val boldtype bold
FORM FILL_CELL USING I J BOLD VAL.
CALL METHOD OF H_EXCEL 'Cells' = H_ZL EXPORTING #1 = I #2 = J.
PERFORM ERR_HDL.
GET PROPERTY OF H_ZL 'Font' = H_F.
PERFORM ERR_HDL.
SET PROPERTY OF H_F 'Bold' = BOLD .
PERFORM ERR_HDL.
***Changing the format of the cell from General to Text
<b>SET PROPERTY OF H_ZL 'NumberFormat' = '@'.</b>
PERFORM ERR_HDL.
SET PROPERTY OF H_ZL 'Value' = VAL .
PERFORM ERR_HDL.
ENDFORM.
*&      Form ERR_HDL
FORM ERR_HDL.
IF SY-SUBRC <> 0.
WRITE: / 'Fehler bei OLE-Automation:'(010), SY-SUBRC.
STOP.
ENDIF.
ENDFORM.                    " ERR_HDL
U just paste this code in a sample program & see.
Please reward, if found helpful.

Default leading zeros during loading

Hi! I have part numbers that tend to have varying length and I have a requirement to put leading zeros before them when I load the catalog data via Import Manager. The Replace function would not work for this as the number of leading zeros is not fixed. Does anyone know o a way to do that?
Cheers!
SF

Hi,
Have a look at the below approach
Assumption- Max Part Number length would be 10 digits.
Create one Assignment with expression
Mid(10000000000+PartNumber,2,10)
Expression will first add the PartNumber with 1000000000 then using Mid function it will extract the desired result.
E.g.
PartNumber = 3030
1000000000+3030 = 10000003030
After Mid = 0000003030
Create one workflow with the Assign step and use the assignment created above. Launch this workflow on Record Import.
I tried this and its working fine.
Regards,
Jitesh Talreja

Lock tables when load data

Are there any way to lock tables when i insert data with SQL*Loader? or oracle do it for me automatically??
how can i do this?
Thanks a lot for your help

Are there any problem if in the middle of my load (and commits) an user update o query data ?The only problem that I see is that you may run short of undo space (rollback segment space) if your undo space is limited and the user is running a long SELECT query for example: but this problem would only trigger ORA-1555 for the SELECT query or (less likely since you have several COMMIT) ORA-16XX because load transaction would not find enough undo space.
Data is not visible to other sessions, unless, the session which is loading data, commits it. That's the way Oracle handle the read committed isolation level for transaction.
See http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96524/c21cnsis.htm#2689
Or what happens if when i want to insert data someone has busy the table?You will get blocked if you try to insert data that has the same primary key as a row being inserted by a concurrent transaction.

Error when loading data from DSO to Cube

Hi,
After upgrading to 2004s we get the following error message when trying to load data from a DSO to a Cube:
Unexpected error: RSDRC_CONVERT_RANGES_TO_SELDR
Has anyone experienced a similar problem or have some guidelines on how to resolve it?
Kind regards,
Fredrik

Hej Martin,
Tack!
Problem solved
//Fredrik

Dump when loading Data from DSO to Cube

Hi,
i get a short dump DBIF_REPO_PART_NOT_FOUND when trying to load data from a dso to a cube. From DSO to DSO it works fine.
any idea`s?
thx!
Dominik

the Dump occurs in the last step of the last data pakage in the DTP Monitor.
I checked the OSS note, but i don´t know how to check the kernel version.
Now i used another DSO for testing and i got another Dump with a different name.
After that i logged in again and it works with my test DSO data...
But still not working with the original one...
@Kazmi: What detaisl u mean exactly?

Display of leading zeroes when downloaded from ALV to excel

Hi All,
I have a problem in ALV grid display.
There is a specific field which has value starting from '001' to '999'. This is a char(3) type of variable.
The problem is that the display shows the value as '001' which is correct. but when the same file is dwnloaded to excel using standard SAP functionality, the value of the field gets changed to '1' instead of '001'.
Is there any option by which this can be controlled. Please let me know, its urgent!!
thanks

hi Ankur,
the Excel download is done by Z program? IF yes you have to do:
SET PROPERTY OF go_cell 'NumberFormat' = '@'.
this will set the Excel cell to Text type and leading zeros won't be lost.
ec

How to removed leading zeros from a date field.

CONVERT(NVARCHAR, CONVERT(DATETIME, CONVERT(CHAR(8), STM.CreationDate)), 101)
This is what i currently have, but prints 02/03/2014 i would like to print the date without the zeros when applicable.
Thanks in advance.

>>REPLACE(LTRIM(REPLACE(CONVERT(NVARCHAR, CONVERT(DATETIME, CONVERT(CHAR(8), STM.CreationDate)), 101),'0', ' ')), ' ', '0')
Does this query really works? I doubt
Satheesh
My Blog |
How to ask questions in technical forum

Truncating leading zeros for the data

hi ,
I am doing a conversion project from oracle source system(DB2) to BI system. I have a situation here:
I am extracting material numbers from source system(DB2) into a ZXXXX characteristic and in the transfer structure i checked the conversion as well and for infoobject ZXXXX, i am using ALPHA conversion. but the data i get is truncating material numbers. For example, 050302 is coming as 50302 and truncating leading zero. I am not sure what needs to be done here.
Please advise..
Thanks in advance...

Hi J Dorson,
This is the expected bahaviour if your InfoObject is configured to have ALPHA conversion. If the zero's in front of the material number is needed, then turn-off ALPHA conversion in your InfoObject (e.g. by removing the conversion exit).

Leading zeroes when loading data

Similar Messages

Maybe you are looking for