Bank statement: problem to load variable length field
we have many bank accounts with different banks, and we would like to use the bank reconciliation module to do bank reconciliation.
we have problem in load the MT940 bank statement. All these banks are providing so called standard SWIFT940 format, which not able to give fixed length field.
we have problem on line 61 which have a lot of variable length fields.
line 61 comprise of 7 fields, which are:
A) Value date - fixed 6 chars.
B) Entry date - fixed 4 chars.
C) Credit/debit - variable 1-2 chars.
D) Fund Code - fixed 1 char
E) Transaction amount - variable 15 chars
F) Transaction code/type - fixed 4 chars
G) MID, cheque#, BIS - variable 16 chars
How can we write the SQL Loader script if there is no delimiter, and the start position of the fields are not fixed?
we can load A and B easily, but C onwards we will have problems.
please help.
INTO TABLE ce_stmt_int_tmp
WHEN rec_id_no = '61'
TRAILING NULLCOLS
(rec_no RECNUM,
rec_id_no POSITION(1:2) CHAR,
column1 POSITION(4:9) CHAR,
column2 POSITION(10:13) CHAR,
column3 ??
column4 ??
column5 ??
column6 ??
column7 ??
------
Hi Linda,
As said by gupta, please check, whether the bank statement has the statement 62F:
If not, please get the statement again from bank and ensure that the end statement 62F exists in the statement..
This will help you to overcome your problem..
Regards,
Praisty
Similar Messages
-
SQL*Loader and "Variable length field was truncated"
Hi,
I'm experiencing this problem using SQL*Loader: Release 8.1.7.0.0
Here is my control file (it's actually split into separate control and data files, but the result is the same)
LOAD DATA
INFILE *
APPEND INTO TABLE test
FIELDS TERMINATED BY ','
OPTIONALLY ENCLOSED BY '"'
first_id,
second_id,
third_id,
language_code,
display_text VARCHAR(2000)
begindata
2,1,1,"eng","Type of Investment Account"
The TEST table is defined as:
Name Null? Type
FIRST_ID NOT NULL NUMBER(4)
SECOND_ID NOT NULL NUMBER(4)
THIRD_ID NOT NULL NUMBER(4)
LANGUAGE_CODE NOT NULL CHAR(3)
DISPLAY_TEXT VARCHAR2(2000)
QUESTION_BLOB BLOB
The log file displays:
Record 1: Warning on table "USER"."TEST", column DISPLAY_TEXT
Variable length field was truncated.
And the results of the insert are:
FIRST_ID SECOND_ID THIRD_ID LANGUAGE_CODE DISPLAY_TEXT
2 1 1 eng ype of Investment Account"
The language_code field is imported correctly, but display_text keeps the closing delimiter, and loses the first character of the string. In other words, it is interpreting the enclosing double quote and/or the delimiter, and truncating the first two characters.
I've also tried the following:
LOAD DATA
INFILE *
APPEND INTO TABLE test
FIELDS TERMINATED BY '|'
first_id,
second_id,
third_id,
language_code,
display_text VARCHAR(2000)
begindata
2|1|1|eng|Type of Investment Account
In this case, display_text is imported as:
pe of Investment Account
In the log file, I get this table which seems odd as well - why is the display_text column shown as having length 2002 when I explicitly set it to 2000?
Column Name Position Len Term Encl Datatype
FIRST_ID FIRST * | O(") CHARACTER
SECOND_ID NEXT * | O(") CHARACTER
THIRD_ID NEXT * | O(") CHARACTER
LANGUAGE_CODE NEXT 3 | O(") CHARACTER
DISPLAY_TEXT NEXT 2002 VARCHAR
Am I missing something totally obvious in my control and data files? I've played with various combinations of delimiters (commas vs '|'), trailing nullcols, optional enclosed etc.
Any help would be greatly appreciated!Use CHAR instead aof VARCHAR
LOAD DATA
INFILE *
APPEND INTO TABLE test
FIELDS TERMINATED BY ','
OPTIONALLY ENCLOSED BY '"'
first_id,
second_id,
third_id,
language_code,
display_text CHAR(2000)
)From the docu:
A VARCHAR field is a length-value datatype.
It consists of a binary length subfield followed by a character string of the specified length.
http://download-west.oracle.com/docs/cd/A87860_01/doc/server.817/a76955/ch05.htm#20324 -
The error is like : Variable length field exceeds maximum length
Hi All,
I am trying to load some signature ascii data from load file. so i wrote the code like below in my controal file to load that to database. For SIGN_IMAGE in oracle db it was mentioned as RAW(2000). The below is worked fine when i tried in window and oracle 8i environment.
SIG_TYPE POSITION(23:23) CHAR,
SIGN_IMAGE POSITION(24:1977) VARRAW(2000)
NULLIF SIGN_IMAGE=BLANKS,
SIGN_IMAGE1 POSITION(1978:3930) VARRAW(2000)
NULLIF SIGN_IMAGE1=BLANKS
But when i ported the same thing to solaris and oracle 10g environment. The below code is giving error when SQL Loder loading.
The error is like for column SIGN_IMAGE : Variable length field exceeds maximum length.
But here i am giving a lenght of 1954 only with including 2 bytes length of the string.
Could any one tell me what is exactly the problem? i am not able sort out the issue.
Thanks,
ShashiMaybe:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14215/ldr_field_list.htm#i1011032 -
Variable length field exceeds maximum length
Hi All,
I am trying to load some signature ascii data from load file. so i wrote the code like below in my controal file to load that to database. For SIGN_IMAGE in oracle db it was mentioned as RAW(2000). The below is worked fine when i tried in window and oracle 8i environment.
SIG_TYPE POSITION(23:23) CHAR,
SIGN_IMAGE POSITION(24:1977) VARRAW(2000)
NULLIF SIGN_IMAGE=BLANKS,
SIGN_IMAGE1 POSITION(1978:3930) VARRAW(2000)
NULLIF SIGN_IMAGE1=BLANKS
But when i ported the same thing to solaris and oracle 10g environment. The below code is giving error when SQL Loder loading.
The error is like : Variable length field exceeds maximum length.
But here i am giving a lenght of 1954 only with including 2 bytes length of the string.
Could any one tell me what is exactly the problem? i am not able sort out the issue.
Thanks,
ShashiHi,
I am getting the error in environment Oracle 10.2.0 and SunOS 5.10. This case was executed fine in Oracle 8.1 and windows xp professional. Please find the details below.
LOG file :
Column Name Position Len Term Encl Datatype
TRANS_NO 1:15 15 CHARACTER
TDR_ID 16:18 3 CHARACTER
DVCE_TYPE 19:20 2 CHARACTER
CAP_CD 21:22 2 CHARACTER
SIG_TYPE 23:23 1 CHARACTER
SIGN_IMAGE 24:1977 2002 VARRAW
NULL if SIGN_IMAGE = BLANKS
SIGN_IMAGE1 1978:3930 2002 VARRAW
NULL if SIGN_IMAGE1 = BLANKS
SIGN_IMAGE2 3931:5883 2002 VARRAW
NULL if SIGN_IMAGE2 = BLANKS
SIGN_IMAGE3 5884 2002 VARRAW
NULL if SIGN_IMAGE3 = BLANKS
value used for ROWS parameter changed from 64 to 31
Record 1: Rejected - Error on table SIGSCH.SIGNATURE, column SIGN_IMAGE.
Variable length field exceeds maximum length.
Record 2: Rejected - Error on table SIGSCH.SIGNATURE, column SIGN_IMAGE.
Variable length field exceeds maximum length.
Record 3: Rejected - Error on table SIGSCH.SIGNATURE, column SIGN_IMAGE.
Variable length field exceeds maximum length.
Record 4: Rejected - Error on table SIGSCH.SIGNATURE, column SIGN_IMAGE.
Variable length field exceeds maximum length.
Controal file :
LOAD DATA
INFILE 'sigc.sig'
BADFILE 'load_7.bad'
DISCARDFILE 'load_7.dis'
APPEND
INTO TABLE sigsch.signature
TRANS_NO POSITION(1:15) CHAR,
TDR_ID POSITION(16:18) INTEGER EXTERNAL,
DVCE_TYPE POSITION(19:20) CHAR,
CAP_CD POSITION(21:22) CHAR,
SIG_TYPE POSITION(23:23) CHAR,
SIGN_IMAGE POSITION(24:1977) VARRAW(2000)
NULLIF SIGN_IMAGE=BLANKS,
SIGN_IMAGE1 POSITION(1978:3930) VARRAW(2000)
NULLIF SIGN_IMAGE1=BLANKS,
SIGN_IMAGE2 POSITION(3931:5883) VARRAW(2000)
NULLIF SIGN_IMAGE2=BLANKS,
SIGN_IMAGE3 POSITION(5884) VARRAW(2000)
NULLIF SIGN_IMAGE3=BLANKS
DATA line
0001200000002480050600?ža4GW ' & ' & _" _! _" ^# ^# _" ^# _" ^# _! _" & ' & ' & !%_!5 & !% & !U & !% ' V X _R _! _Z _Q _" _"__1 _"_ ( _!__2_ (_ 0 & 'pa@NS _! _"_^3 _" ^# _! ^$ ^# _! ^$ _! _" _!paDC' ' P V _ P ^ & '_ ._ 0__*_ 0 ^# _" _! _" _! ^T X _Q! H PpaTI$_ (_ 0_ (_ 0__2_ (^_9 _"_^3 _" _! _R _Z P! H P! H & ^ W !% & & ' _! _" ^# _" _! _" _" _Q _" X P &pa]KA_ 0^ 8_ 0_ (__2_ 0_ ( X _! P P Z! H Q P Z R _!__2 _!^ 8__2_ (^ 8_ 6_ 0 ' Ppe"F; P ^ P & P ' & '_ 0_ 0__)_ 0 _"__) Z " ^S _Y! @!_Jpe3K/ _" _" _! _"__1 ^$ _! _" P _! ' ^ ' & & !% ' & & ' &_ ( _" X P P Y!J R!I!_J ^S R Y _"_ (__1^ 8_ 0^ 8_ 7^ 8_ ( & _" X PpeDF# & & _" _" _! _" ^# _" PpeDKW '_ 0 V P X R X P Q _"_ 0_ 0_ ( _" _! Z P Q Z!J Q R _! _" _"_ 0^ 8__1_ /_ 0_ 6_ ( & ' X V! H W! H! N! H! @ X P Z ! _" _! ^$ _! ^# _" ^# R ! ' & ' !$ !% !% !%_!5 !$ ' & W & & P X _" _R _! _Z _! _" _"__)_ 0__*_ 0 Ppi#J+ X_ (_ 0_ (^ @_ (__1__*__1 _R _Z _Q X P P! H X ' & V_ 7 &_ ( '_ 6 _" Ppi-KG_ 0_ 7__)_ 0_ /__1^ 8_ 0 R Z P Q Z Q Z _" _Q__2__) _"__2_ (^ @_ (_ 6 V ' ^ P P ' X V X P P X P! H P ^ P X W & '_ 6_ (__2_ (__1__2 _! _" _R _Q! H _Z P Ppi@H& _Q P X _" V X ' P_ 6_ (__2__)_ 0__2 _" _! _R _Q X P! H P _ & ' &_ . '_ 6 P XpiTN# &_ (^ 8__2^ 8_ 0__)__2_^3 _" _! ^# R " _! _R _!__2 _"_ 0_ (_ 6_ ._ 7_ 6_ / & & ' X P Q! H!J Ppi\KW _" _R X _Q _Z _Q _R _Zpm&O9_ . _"__2 _!_^3_^, ^#_^3 ^# ^# ^$ Qpm(JS 0_ ( _!_ 0 _"__) _" _" _! _Z P X P V _ &_ ._ 7_ 0 P Ppm1ID_ 0_ 0__* _!__2 _" Q " X _! P P X W X !% P & & W & _" _! _" _" _! ^# _" X V ' !] & V ' & _" _!__2 _" _! _" P & ' & V _ V _! @ ^! H!_B Xpa44V &_ 0____1____2 ^# ^# ^# R !!_J X P V _ !% & !% & '_ . &_ 7_ 6 Ppa<7Q_ 0_ ._ 0 _"__* _! _" ^# _" ]\ ^$ ^S ^# _Z _! W &paE3A _"_ 0 &_ 0_ ( _"_ 0__) _"_^3 _" ^S ^# _Z P!_I W !\ ' "S !%\!% !$ !%_!5 & '_ ( ^# _" ^# _! ^$ ^[ _! ^T ^# _YpaW7)_ 0_ ( _"__1 _" ^# _" ^# _! ^T X _Q! H P! H Xpe 7Q_ 0_ ( X _" _Q ^# _R ^# ^# ^\ ^# ^S _" _! _Z V !% !U !] !T !% !% !% &_ 0 _"__) ^$ _! _" ^# _" ^[ P _Y! @ X W ^ ' &_ ._ 7_ . '_ 6_ 0 & W P ^pe37/ ' _! _" _" _! ^# ^$ _! ^[ ^$ ^# _! ^$ _!pe-3A _" X _Q X! @ X P! H P ' X & V ' & ' !$ ' & _" _! ^$ _! ^# ^$ ^[ ^# ^# ^S _" _" V !% ^ W !\ W P ^ P X P _R _! _Z ^# _R ^# ^# _Z _! _RpeE/G X P X P W X P &_ 7_ (__1_ 0__*__1_^, _! ^# ^\ _Q _Z!_A!_J! H P! HpeU3A &_ 0_ 0__* _" _! _Z _Q _" ^S _" ^# _" _! _"__1 _"__2_ (_ 0pe]5D _" _! _" _" _! ^# ^\ ^# ^S _" ^# X & W & !% !%_"3_!-_ 6_!- &_ 7_ 0 & P V _ P X! @ X P X _Q ^$ _! _" _!__2_ ( _"_ 0_ (_ 0 Vpi&0> _! ^$ _Q _" _! ^$ _! _" & _ !$ ' !% !$ ' !U V ^ P! H P!_J X!_B Xpi65<_ ( _"_ 0 _! _"__2 _!__* _! ^$ ^# _Y _R _R X V ^ !U ' & &_ 7_ . '_ 0_ ( X VpiA1D_ 0^ 8 _"_ 0 _! ^$ _!_^+ ^$ ^[ ^S ^# ^[ _R _R_ 6 &_!5_!- !%_!5 !$ !% !U !% ^ W P X P _Y P _" _! _" ^#__2_ (__1_ (_ 0 ' &piF0> P X P! H P! H! H V __ . &_ 0_ (^ @_ (__2__*__1 _" _Q _Z _R! H!_I! H PpiT3! P &__2 _" _! _R _! _" _" ^# _! ' & ' !$ W & ' ^ V! H P! H Xpm$;! & _" _" _! ^# ^$ _! ^# _" _" ^#pm'3/ _"_ 0 _" _! _R _! _Z P _R! H! H P! N X V W & _Z _! ^$ ^S ^# ]] ^# ]% ]U_^3 _!__*^_:^_A^ 8^ 8^ ?^ 8^ @p -
Variable length field exceeds maximum length for VARRAW in SQLLOADER
Hi All,
I am trying to load some signature ascii data from load file. so i wrote the code like below in my controal file to load that to database. For SIGN_IMAGE in oracle db it was mentioned as RAW(2000). The below is worked fine when i tried in window and oracle 8i environment.
SIG_TYPE POSITION(23:23) CHAR,
SIGN_IMAGE POSITION(24:1977) VARRAW(2000)
NULLIF SIGN_IMAGE=BLANKS,
SIGN_IMAGE1 POSITION(1978:3930) VARRAW(2000)
NULLIF SIGN_IMAGE1=BLANKS
But when i ported the same thing to solaris and oracle 10g environment. The below code is giving error when SQL Loder loading.
The error is like : Variable length field exceeds maximum length.
But here i am giving a lenght of 1954 only with including 2 bytes length of the string.
Could any one tell me what is exactly the problem? i am not able sort out the issue.
Thanks,
ShashiPlease only post in a single forum. Thank you.
-
Variable length field exceeds maximum length for VARRAW
Hi All,
I am trying to load some signature ascii data from load file. so i wrote the code like below in my controal file to load that to database. For SIGN_IMAGE in oracle db it was mentioned as RAW(2000). The below is worked fine when i tried in window and oracle 8i environment.
SIG_TYPE POSITION(23:23) CHAR,
SIGN_IMAGE POSITION(24:1977) VARRAW(2000)
NULLIF SIGN_IMAGE=BLANKS,
SIGN_IMAGE1 POSITION(1978:3930) VARRAW(2000)
NULLIF SIGN_IMAGE1=BLANKS
But when i ported the same thing to solaris and oracle 10g environment. The below code is giving error when SQL Loder loading.
The error is like : Variable length field exceeds maximum length.
But here i am giving a lenght of 1954 only with including 2 bytes length of the string.
Could any one tell me what is exactly the problem? i am not able sort out the issue.
Thanks,
ShashiYou should probably move this question to the General Database Discussions. This forum is for Oracle Forms not SQL:*Loader.
-
FF_5 - Import Bank Statement, Err: Formatting error in the field COBL-KOSTL
Hi
When importing the bank statement I'm getting the error
Error: (00 298) Formatting error in the field COBL-KOSTL ; see next message
Why is it doing this? In OKB9 I have the GL Account and the cost center assigned. It is the ne GL that is giving this problem, in the classic GL I do not have this problem.
Thanks in advanceHi
No, it is not that. For some reason in the new GL it does not seem to determine the cost centers and profit centers as usual.
For exampl to allocate the Profit Center for Balance Sheet Account I used to use 3KEH in the classic gl but in the New gl we must use FAGL3KEH.
Now with cost center i'm having the same problem, does not determine the cost center when importing the bank statement.
Can someone help me.
Thanks in advance
Edited by: Louis De Gouveia on Mar 3, 2009 7:07 AM -
Hi SAP Gurus,
Our client has an issue wherein their Manual Bank Statement Overview (displayed via FF67) does not display the Bank Statements in chronological order, meaning the latest bank statement posted should come out on the top of the list.
What happened was that the bank statement number was already maxed out (00999) which would naturally bring back the bank statement number back to 0001. Though it the system behavior of reverting back to 0001 did take place, the overview doesn't display them in the correct chronological order.
This is an example of what happened to the Bank Statement Overview:
Bank statement# - Date
999 - 25.06.2010
998 - 24.06.2010
997 - 22.06.2010
996 - 21.06.2010
*003 - 02.07.2010*
*002 - 01.07.2010*
*001 - 30.06.2010*
995 - 29.12.2009
994 - 28.12.2009
**As you can see, the view does not display it in chronological order. Instead, it went ahead of bank statements posted in the previous year which is 2009.
This was the system behavior we were expecting:
Bank statement# - Date
003 - 02.07.2010
002 - 01.07.2010
001 - 30.06.2010
999 - 25.06.2010
998 - 24.06.2010
997 - 22.06.2010
996 - 21.06.2010
995 - 29.12.2009
994 - 28.12.2009
Would there be a way to change the layout of the Manual Bank Statement Overview so that I can sort the data by Date? What could have gone wrong/missing in the system settings? Any help/suggestion/comment is greatly appreciated. W
ThanksFor cheque issue use the following config
Use algoritham 11, while creating Business Transaction for Manual Bank Statement.
and Posting Rule settings are:
Posting Area:1
Debit key: (leave Blank)
Debit Symbol: Yourcheckissuesymbol
Credit Key: 50
Credit Symbol: yourmainbanksymbol
document Type: SA
Posting Type: 4
For Cheque Deposit
Leave the algoritham field balnk,
And use this while defining the posting rule:
Posting Area:2
Debit key:40
Debit Symbol: YourMainBank
Credit Key: 50
Credit Symbol: (leave blank)
document Type: SA
Posting Type: 1
This definetly works out. This config is in my system.
Satish
Plese assign points if useful.
Message was edited by:
Satish Kumar
Message was edited by:
Satish Kumar -
How to load 256 length field from r/3 to BW & How to report in Bex Browser
Hi,
We have a field consists of 256 length in r/3 system.
I want to load from R/3 -> BIW -> Bex Reporting.
What are the steps to be taken in R/3 Side.
What are the steps to be taken in BW side.
What are the steps to be taken for Bex.
Thanks,
MadhuMAdhu,
If you want to extract the data from R/3 to BW fro which the field length is 256 then its not possible directly.
Either you need to breeak up the same filed into 5 Infoobjects since the maximum length of the infoobject is 60 or else you need to maintain a conversion routine... And the remaining process of loading the data from R/3 to BIW is the same.
Hope this helps...
Gattu -
Bank statement number not updating in reference field
Hi All,
After importing EBS, reference field of the posted document will be updated default as "HOUSE BANK" ACCOUNT ID" and "Statement number". But in my case statement number in this field is updating up to 11999.
Means, if I run EBS upload with statement number 12000 it is updating as 11000. This is updating in Table FEBEP also. I could see FEBA with statement number 12000.
Do you have any idea where this is controlling.
Regards
SMHi,
the first 2 digits are for the year and the last 3 are for the statement number. -
Hi there,
I have a client who is trying to enter in a manual Reconciliation for the bank and the selection criteria screen is showing a "last balance" of ZAR -164,093.14? I go to manage previous recons for that account and there is nothing there.
Where else could this figure be coming from and how do we get rid of it? It is obviously affecting the balance when doing the recon so we need to fi this before they can do a bank recon.
the SAP version is 2007 SP00 PL 42
Please advise.
Kind regards
Clayton.If you have recently upgraded, I think you will find this is a bug that is corrected in SP01?
If you look in the form settings for main menu & open the Process External Bank Statqament window, this is the OBNK table that stores the transactions from external bank reconcilaitions. -
Problem in sending a variable length string
Hello friends,
I have created a scenario as follows.
Our
Application ==>(SOAP) ==> XI ==> (RFC) ==> SAP TABLE.
I am sending a record with one of the fields of the type 'VARILRAW'
When I send this, it is sending me a response that it was inserted in the table succesfully, But when I try to retrieve, all fields get returned correctly, but not this variable length field. This sends me back a huge string of letter 'A's.
Here is what I see on SXMB_MONI
The following shows that for insertion, the proper data is coming in XML format.
===============================================
<?xml version="1.0" encoding="UTF-8" ?>
- <ns1:ZBAPI_ADD_CONFIG_DNA xmlns:ns1="urn:sap-com:document:sap:rfc:functions">
- <CONFIG_DNA_DATA>
<CONFIG_ID>4607.1164846986188077.494</CONFIG_ID>
<STRING_NAME>USC1</STRING_NAME>
<STRING_FORMAT>TXT</STRING_FORMAT>
<STRING_VALUE>ONE,TWO,THREE,FOUR</STRING_VALUE>
<OBJECT_NAME>TEMP</OBJECT_NAME>
</CONFIG_DNA_DATA>
</ns1:ZBAPI_ADD_CONFIG_DNA>
=================================================
When I try to search for the same data again using the Key field CONFIG_ID,
I am getting back the following. Notice that all fields are coming back with right data but for STRING_VALUE, which is coming as a long string of As
====================================================
<?xml version="1.0" encoding="UTF-8" ?>
- <ns1:SEARCH_CONFIG_DNA_RESPONSE xmlns:ns1="http://cincom.com/config">
- <RETMSG>
<RETURNMESSAGE>1 Records found</RETURNMESSAGE>
<SUBRC>0</SUBRC>
</RETMSG>
- <CONFIG_DATA>
- <item>
<CONFIG_ID>4607.1164846986188077.494</CONFIG_ID>
<STRING_NAME>USC1</STRING_NAME>
<STRING_FORMAT>TXT</STRING_FORMAT>
<STRING_VALUE>AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA</STRING_VALUE>
<OBJECT_NAME>TEMP</OBJECT_NAME>
</item>
</CONFIG_DATA>
</ns1:SEARCH_CONFIG_DNA_RESPONSE>
========================================================
Any help will be greatly appreciated.
Thanks
Ramgo to RFC and insert a BREAK-POINT and check what do you receive in the field. if you receive same you send so its a problem of SAP Team.
try this -
File Sender, Content Conversion - how to define variable length last field?
XI 3.0 SP17
With a File Sender communication channel, that uses Content Conversion - how do I define a 'variable length' last field?
The scenario - the input file has four fields, of which the first three are a known fixed length, and the last (fourth, trailing) field is variable in length.
Using a Message Protocol of 'File Content Conversion', how do I define that last variable length field (field name 'WOData' below) in the Content Conversion Parameters section?
My current parameters are:
Recordset Structure - Row,*
ignoreRecordsetName - true
Row.fieldFixedLengths - 1,12,5,99999
Row.fieldNames - WOType,WONum,WOLine,WOData
I've tried the following for 'Row.fieldFixedLengths' to no avail -
'1,12,5,*'
'1,12,5,0'
'1,12,5,'
'1,12,5'
The last two were grasping at straws )
The only thing I've got to work is specifying a 'large' value for the final field (99999 above).
In addition, does anyone know if specifying a large value (e.g. 99999) for the final trailing field will give rise to performance issues when the file is being processed?
In the help for "Converting File Content in a Sender Adapter", it states -
<Begin Quote>
NameA.fieldFixedLengths
If you make a specification here, the system expects a character string that contains the lengths of the structure columns as arguments separated by commas.
If you also specify a separator for the columns, you must not add its length to the length of the columns.
This entry is mandatory if you have not made an entry for NameA.fieldSeparator.
<End Quote>
http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm<< note that fieldFixedLengths will not take any wildcard entries like *. So in these case it is ideal to provide a maximum char length. But note that while the file is being created that many spaces will be created in your file !!! >>
Hi Shabarish,
Yes, no wildcard is the conclusion I came to, hence my maximum )
The message size did not increase by any 'blank padding'. When I look in [Message Display Tool (Detail Display)] 'Audit Log for Message: X' -
2006-10-17 18:22:42 Success Channel X: Entire file content converted to XML format
2006-10-17 18:22:42 Success Send binary file "X" from FTP server "X", size 103290 bytes with QoS EO
2006-10-17 18:22:42 Success Application attempting to send an XI message asynchronously using connection AFW.
2006-10-17 18:22:42 Success Trying to put the message into the send queue.
2006-10-17 18:22:42 Success Message successfully put into the queue.
2006-10-17 18:22:42 Success The application sent the message asynchronously using connection AFW. Returning to application.
The input flat file in non-XML format was 92,132 bytes and the message payload into XI was 103,290 bytes.
My understanding is that trailing spaces are stripped from XML nodes. -
SQL*LOADER(8I) VARIABLE SIZE FIELD를 여러 TABLE에 LOAD하기 (FILLER)
제품 : ORACLE SERVER
작성날짜 : 2004-10-29
==================================================================
SQL*LOADER(8I) VARIABLE SIZE FIELD를 여러 TABLE에 LOAD하기 (FILLER)
==================================================================
PURPOSE
SQL*LOADER 에서 variable length record와 variable size field를 가진 data
file 을 여러 table에 load하는 방법을 소개하고자 한다.
( 8i new feature인 FILLER 절 사용)
Explanation
SQL*LOADER SYNTAX
여러 table에 load하고자 할때에는 control file에 아래와 같이 하면 된다.
INTO TABLE emp
INTO TABLE emp1
fixed length field을 가진 data file을 여러 table에 같은 data을 load하고자
한다면 아래와 같다.
INTO TABLE emp
(empno POSITION(1:4) INTEGER EXTERNAL,
INTO TABLE emp1
(empno POSITION(1:4) INTEGER EXTERNAL,
위와 같이 양쪽 table의 empno field에 각각의 load할 data로부터 1-4까지를
load 할수 있다. 그러나 field의 길이가 가변적이라면 위와 같이 POSITION 절을
각 field에 사용할 수 없다.
Example
예제 1>
create table one (
field_1 varchar2(20),
field_2 varchar2(20),
empno varchar(10) );
create table two (
field_3 varchar2(20),
empno varchar(10) );
load할 record가 comma로 나누어지며 길이가 가변적이라고 가정하자.
<< data.txt >> - load할 data file
"this is field 1","this is field 2",12345678,"this is field 4"
<< test.ctl >> - control file
load data infile 'data.txt'
discardfile 'discard.txt'
into table one
replace
fields terminated by ","
optionally enclosed by '"' (
field_1,
field_2,
empno )
into table two
replace
fields terminated by ","
optionally enclosed by '"' (
field_3,
dummy1 filler position(1),
dummy2 filler,
empno )
dummy1 field는 filler로 선언되었다. filler로 선언하면 table에 load하지 않는다.
two라는 table에는 dummy1이라는 field는 없으며 position(1)은 current record의
처음부터 시작해서 첫번째 field을 dummy1 filler item에 load한다는 것을 말한다.
그리고 두번째 field을 dummy2 filler item에 load한다. 세번째 field인, one이라는
table에 load되었던 employee number는 two라는 table에도 load되는 것이다,
<< 실행 >>
$sqlldr scott/tiger control=test.ctl data=data.txt log=test.log bindsize=300000
$sqlplus scott/tiger
SQL> select * from one;
FIELD_1 FIELD_2 EMPNO
this is field 1 this is field 2 12345678
SQL> select * from two;
FIELD_3 EMPNO
this is field 4 12345678
예제 2>
create table testA (c1 number, c2 varchar2(10), c3 varchar2(10));
<< data1.txt >> - load할 data file
7782,SALES,CLARK
7839,MKTG,MILLER
7934,DEV,JONES
<< test1.ctl >>
LOAD DATA
INFILE 'data1.txt'
INTO TABLE testA
REPLACE
FIELDS TERMINATED BY ","
c1 INTEGER EXTERNAL,
c2 FILLER CHAR,
c3 CHAR
<< 실행 >>
$ sqlldr scott/tiger control=test1.ctl data=data1.txt log=test1.log
$ sqlplus scott/tiger
SQL> select * from testA;
C1 C2 C3
7782 CLARK
7839 MILLER
7934 JONES
Reference Documents
<Note:74719.1> -
Problem loading variables and controls in Workshop 8.1 (Beta) Palettes
Hi All,
I am getting problem in loading variables and control in the Workshop Data and
Control Palette at times when I open the application. The Workshop interface shows
the variable at times and does not show up at all on another instance. Let me
know if anybody else has faced a similar problem or notAkshay,
Please post this question in the Workshop 8.1 Beta Newsgroup.
weblogic.developer.interest.81beta.workshop
Thanks
Raj Alagumalai
WebLogic Workshop Support
"Akshay Aggarwal" <[email protected]> wrote in message
news:3e9107da$[email protected]..
>
Hi All,
I am getting problem in loading variables and control in the Workshop Dataand
Control Palette at times when I open the application. The Workshopinterface shows
the variable at times and does not show up at all on another instance. Letme
know if anybody else has faced a similar problem or not
Maybe you are looking for
-
Dynamic rendering of date intervals for a single query
Hi, I am new to BW so I am not sure if this is even possible, or if there is a better way to do this. I am trying to build a query in the Query Designer to basically display sales data for a Business Partner where a user is able to select a date rang
-
Hi, First sorry about the long post but any help would be really appreciated. I can't seem to get iscsi working what am i doing wrong? May 24 09:53:39 edsrvscdm-01 iscsi: NOTICE: iscsi connection(5) unable to connect to target iqn.1992-08.com.netapp:
-
My photos looked great but when I made a book in iphoto 09 they all appeared to be corrupted in the pdf preview? There is a white triangular shape with random horizontal lines running through each photo in the ibook preview. Took it to the Genius
-
How to list those employees who do not have a certain pay rate type set up
Hi, I'm trying to create a report that lists all employees who DO NOT have a certain pay rate role type set up. An employee can have multiple pay rate roles - for example: chargeable miles, non-chargeable miles, subsistence, etc. I want to identify
-
Good Day. I am a new user and have downloaded some games from my Sony camcorder to my Mac. I am trying to now send out those games on youtube but am getting a "too large a file" message. If there some way to get this on to youtube that I am not aw