Error while filling set up table SD-Billing Documents - Perform Setup

Hello friends,
while filling set up table of SD-Billing Documents - Perform Setup
i am getting error 'TSV_TNEW_PAGE_ALLOC_FAILED' . i am executing this job in background process . Please suggest me a solution .
Regards
Nilesh Vakil

Hi,
Try some other LO extractor in RSA3 to check if you get the same error.
If you dont then it may not be system memory issue, check if thr is some user exit written for the extractor.The problem could be in the user exit whr the internal table may get overflown and lead to the page overfloen dump.
If this is also not the case try reducing the packet size.
Let me know if the issue is resolved.
Regards,
Ashwin

Similar Messages

Error while filling set up table for Inventory

Hi,
While filling up setup table for Inventory, 2lis_03_bf, i get an error, Plant F041 doesnot exist. I am trying to fillup the table without any selections. Can anyone please suggest me a solution.
Thanks,
Praveen

Please check the following link:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
Hope it helps you.

Error while filling set up tables for 2LIS_11 data sources

hello All ,
I tried to fill setup tables for 2LIS_11 data sources in OLI7BW , but the job RMCVENUA is getting cancelled. below is the Job Log ,
Job started
Step 001 started (program RMCVNEUA, variant &0000000000005, )
Start of order processing
Error determining rate: foreign curr. local curr. INR date 10.09.2008 (doc. 1)
Job cancelled
Is there any setting required in R3 side before filling setup tables of SD ?
I am able to fill the setup tables for 2LIS_05 ( Notifications) successfully.
Regards ,
Amol Kulkarni
Edited by: Amol Kulkarni on Dec 4, 2008 3:59 AM
Edited by: Amol Kulkarni on Dec 4, 2008 4:00 AM

Hi,
one of the sales document currencies is not maintained properly in the system and therefore its failing.
you need to correct those documents before filling the set up tables.
Either you can chose the option fault document toleration limit to 1000...so that 1000 records wrong records can be tolerated or you have to crrect it first before filling up the set up tables.
This will generally happen in test systems.... but very rare in production...so try to maintain currrency again in the system.
generally you will see the sales doc number in the error for which its failing.
May be at the time of filling some óne was working on some sales document and tried it save it.
correct that doc and fill the set up tables again.
Thanks
Ajeet

Error while filling setup table for 2LIS_03_BF

Hello,
I am getting an error while filling set-up table for 2LIS_03_BF.
Following is the screenshot of the same.
If I check in ST22, I get following,
I could fill the setup table for other datasource 2LIS_03_BX without any problem.
Please suggest.

Hi,
Can you try filling the setup table data for that range in background?
Sometimes because of huge data that you are trying to fill it might through you a dump. So please execute it in background and see if it works?.
But still can't really say what that dump tells from what you attached.
Thanks,
Sathya

Error while filling the set up table for 2LIS_11_VAITM

Dear Experts,
i am facing an error while filling the set up table for 2LIS_11_VAITM in the source system.
The error was "Company code for sales org 9000 does not exist (document 1326)".
when i checked the document in the Header table VBAK,company code was blank for the document .
Company code was there in the selections for the setup table.
The error means that company code should be maintained for the sales document as per my knolwedge.i think document was not created properly in the source system.
Could you please help me out to over come the problem.
Regards,
Sunil...

in the selection screen for filling the setup table, there is a parameter No. tolerated faulty documents
you'll have to enter at least '1' here in your case
it might be that there are other erronuous records, in that case it will crash again, and you'll have to increase the value for this parameter
(under "normal" circumstances, all documents in the source should be correct... but apparently it's possible to circumvent this)

Error while filling setup table for Sales

Dear Team,
We are getting following error while filling setup table for Sales (application component 11) and for Billing (application component 13),
application component 11
Error determining rate: foreign curr. local curr. INR date 08.10.2007 (doc. 673624) (JOB - RMCVNEUA)
Message No M2810
application component 13
Billing document 480050000: error determining stats. currency rate (no updating)
More faulty documents found than the tolerated 0000000000 (JOB - RMCVNEUF)
I have seen lot of threads based on this but all r showing diffrenent currency to INR but for the above mentioned documents currency is in INR only so why it is showing the error I am not able to determine.
If anybody faced this problem kindly reply to this.
Best Regards,
SG

Hi There,
Might be your using a wrong document number.
I mean if your using the 11 you should use only Sales document number and for 13 you should only use billing document number.
If you use vice versa that error will throw.
Regards,
MQ

Timeout error while filling setup tables

HI all
I am getting timeout error while filling setup tables(OLI1BW).I clicked on execute button on hte screen.Its not scheduled as a background job.
Going through threads i have come to know that to solve this issue
1.BASIS team have to increase backgroung processses or memory
2.run it as a background job.
When I went to Program->Executein the backgroundPrint background parameters window has popped up.
What to do in there?I am afraid if I include parameters like printer name....what is it and how long is it going to print?
Please let me know.
Thanks,
Harika.

thanks for the reply.
it was set to LOCL only.
But i have 3 options in the dropdown windowsprinter :Send to onenote2007
Microsoft XPS document writer
OUrprinteraddress
WHich one to choose here?
Edited by: harikag on Aug 10, 2011 8:47 AM

Error while filling setup tables for 2lis_13_vahdr

Dear friends,
I am getting below Error while filling setup tables for 2lis_13_vahdr.
More faulty documents found than the tolerated 0000000000
Message no. M2222
Can any one guide me how to address this issue.
Thanks and Regards
Nithya

Hello Nithya,
It seems the No of tolerated faulty documents that you have given is 0. So when you initialize try to these.
While executing OLI*BW including a value in the maintain "No. tolerated faulty documents" - 5000 or 10000.
Then execute the program in background.
Once the job is completed check the background job log if any errors.
Thanks
Chandran

Dump error while filling the Setup table

Hi All,
I am trying to fill the setup table.While filling the stup table for 2lis_03_BF datasource, i got the Dump error after some time. I have checked the data in Setup table and found 9000 records.
Shall i proceed further by pulling the data from R/3 to BW.I have checked the data in RSA3 and got some data.
Shall i schedule the data from BW side.
Pls help on this issue.
Thanks,
Siva.

Thanks Reddy and JS.
I have checked the TCODE SM37 and found no jobs are available. I have checked the TCODE : NPRT and found some logs.In this, it is not showing any errors.
I have checked in SM21 and found some errors.
Time_______________Text
17:08:10____________Transaction Canceled M2 630 ( )
17:23:47____________Run-time error "TIME_OUT" occurred
17:23:47____________> Short dump "090302 172347 sand1_W2 2_00 " generated
17:30:08____________Status: 80% of IL00.DAT is in use
17:30:17____________Status: 90% of IL00.DAT is in use
17:30:18____________Overflow of Paging File (032768 Blocks)
17:30:18____________Run-time error "MEMORY_NO_MORE_PAGING" occurred
17:30:19____________> Short dump "090302 173018 sand1_W2 2_00 " generated
Shall i execute filling the setup table again. Do i need to give termination time More ( 2 Hrs difference)
Any issue on refilling the setup table again.
Pls suggest.
Thanks,
Siva.

Short dump error while filling setup tables for 2LIS_06_INV

Hi All,
I am trying to fill the setup table.While filling the stup table for 2lis_06_inv datasource, i got the Dump error after some time.
Error
Runtime Errors         DBIF_RSQL_SQL_ERROR
Exception              CX_SY_OPEN_SQL_DB
Short text
    SQL error in the database when accessing a table.
plz can anyone help me out...

Dear friends,
I tried it by giving the selection on fiscal year,but again same problem.If i give 1 0r 2 document numbers in selection then extractor works fine.
error:in detail.
Runtime Errors         DBIF_RSQL_SQL_ERROR
Exception              CX_SY_OPEN_SQL_DB
Short text
    SQL error in the database when accessing a table.
Information on where terminated
    Termination occurred in the ABAP program "SAPLMRMBW" - in "BW_RETRIEVE_DB_CO".
    The main program was "RMCENEUR ".
    In the source code you have the termination point in line 827
    of the (Include) program "LMRMBWF01".
    The program "SAPLMRMBW" was started as a background job.
    Job Name....... "RMCENEUR"
    Job Number..... 10524100
    The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
    procedure "BW_RETRIEVE_DB_CO" "(FORM)", but it was neither handled locally nor
     declared
    in the RAISING clause of its signature.
    The procedure is in program "SAPLMRMBW "; its source code begins in line
    806 of the (Include program "LMRMBWF01 ".
806 FORM bw_retrieve_db_co USING    t_mcrbkey_bv    TYPE mcrbkey_t
807                                  t_mcrbkey_nbv   TYPE mcrbkey_t
808                                  t_ekbe_acc      TYPE t_ekbe
809                         CHANGING t_mcrbco        TYPE mcrbco_t.
810
811   TYPES: BEGIN OF s_target.
812   TYPES: table_left LIKE rbco.
813   TYPES: table_right TYPE rbex.
814   TYPES: END OF s_target.
815   TYPES: t_target TYPE TABLE OF s_target.
816
817
818   DATA: t_rbco_nbv TYPE t_target,
819         t_rbco_bv   TYPE t_target,
820         s_rbco      TYPE s_target,
821         s_ekbe      LIKE ekbe,
822         s_mcrbco    TYPE mcrbco,
823         l_index     LIKE sy-tabix.
824
   825 * Data source: invoice item non-background
826   IF NOT t_mcrbkey_nbv[] IS INITIAL.
*>>>>>     SELECT * FROM rbco AS r LEFT OUTER JOIN rbex AS i*
828        ON   ( rmandt = imandt AND
829               rbelnr = ibelnr AND
830               rbuzei = ibuzei AND
831               rcobl_nr = icobl_nr )
832        INTO TABLE t_rbco_nbv
833        FOR ALL ENTRIES IN t_mcrbkey_nbv
834        WHERE r~gjahr = t_mcrbkey_nbv-gjahr AND
835              r~belnr = t_mcrbkey_nbv-belnr.
836   ENDIF.
837 * Data source: invoice item background
838   IF NOT t_mcrbkey_bv[] IS INITIAL.
839     SELECT * FROM rbco AS r LEFT OUTER JOIN rbex AS i
840        ON   ( rmandt = imandt AND
841               rbelnr = ibelnr AND
842               rbuzei = ibuzei AND
843               rcobl_nr = icobl_nr )
844        INTO TABLE t_rbco_bv
845        FOR ALL ENTRIES IN t_mcrbkey_bv
846        WHERE r~gjahr = t_mcrbkey_bv-gjahr AND
Thnks in advance

Fatal error while filling connection pool

I was not getting a connection to an Oracle database and I was getting the following error in cms.log: "FATAL Connector - Unable to create connection pool for T_Orbis_Oracle: Fatal error while filling connection pool for jdbc:oracle:thin:@MESDB:1521:ASPENB21" where T_Orbis_Oracle is the xMII link name and the database ASPENB21 is on server MESDB. I changed the database username in the link to SYSTEM and I then got a connection and a Created Connection pool message in the log. I then changed back to the username which originally was giving the error and it now also gave me a successful connection. I am now worried that there is an issue in the background which is gradually building up and will begin to fail again as previously. Can anyone explain what is causing this problem and suggest how I can correct it? Thanks, John.

John,
Check you have installed the JDBC driver ojdbc14.jar (works for both 9 and 10).
Also check the server package:
MII 11.x--->ServerPackage com.lighthammer.Illuminator.connectors.IDBC
MII 12.x--->com.sap.xmii.Illuminator.connectors.IDBC
Carefull when you set up the string because some oracle databases have servicenames instead of SID, and the url was different if you use them instead of the SID.
For services names the url is jdbc:oracle:thin@host:port:SID
Also check your Network firewall between MII and DB and ports too.
Oracle9i installs with a number of default accounts.You must unlock all other accounts before using them. Oracle recommends changing all user passwords immediately after installation.
-Suresh
Edited by: Suresh Hiremath on Jul 29, 2009 8:20 AM

Problem about fill set up table

Hi all,
I got a problem when I run the fill set up table for sales billing data source. what I did is:
first delete the setup table then oli9bw->type in a sales document no.(as I only want this order data), then give a run name, last execute, but I got the message as follow:
Data source 2LIS_13_VDITM contains data still to be transferred
Could you pls explain what this means, and what should I do to solve the problem
Thanks

Set up table definition
Setup table is store the historical data, where as the delta records are updated in delta queue not to set up table.
So once historical data is loaded you can delete the contents of the set up table.
name is extract sturcture of your data source + setup
also data is taken from setup table when an init / full/ full repair load is done.
so in order to take ur records from the table delete the setup table(LBWG) and initialize it with ur records.
You can find the contents SE16
Filling set up tables
transac LBWG
+ SBIW -> Logistics -> Managing Transfer Information Structures-> Setup of Statistical Data-> Application-Specific Setup of Statistical Data
set up tables
Set up tables
Set up tables
view of set up tables data in se11??????????
Set Up tables..
lo: delete set up tables: DOUBT
LBWQ is the extraction queue and RSA7 is delta queue. Data is sent to delta queue from extraction queue through collective job scheduled in transaction LBWE.
when we want to extract the data using LO Cockpit, the data will be come to the extraction queue first and from there it will processed to the delta queue. SO lbwq works as a outbound queue.
If the update mode is Unserialised V3 then as soon as the document is posted it comes update table which you can see in Tr. Code SM13. After the jonb is scheduled the records come to RSA7 i.e delta queue from which BW pulls the data
If you use u201CQueued Deltau201Dupdate method then the data moves to Extraction queue(LBWQ). Then run Collective update to move the data from LBWQ into Delta Queue (RSA7). Then schedule the data using the infopackage by selecting Delta Load in the update tab.
So in If you are going to do Setup table filling, delete the data from LBWQ.
The usage of Extraction queue(LBWQ) comes in to picture in delta loading. But actually system starts collecting the data (whenever there is document creation in R/3) after activating the EXtraction structure.
Steps to Be Performed
We know that there are 4 types of delta extraction that are available in LO. If you use u201CQueued Deltau201Dupdate method then the data moves to Extraction queue(LBWQ). Then run Collective update to move the data from LBWQ into Delta Queue (RSA7). Then schedule the data using the infopackage by selecting Delta Load in the update tab.
Here is Roberto's weblog:
/people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
check this out...
LBWQ - T code is for what?
Ttransaction LBWQ
What is LBWQ?
Assign points if it helps
Hope it helps
regards
Bala

2LIS_11_VAHDR - Filling set up tables chanceled

Hello,
I set up a new cube. Here filling set-up tables of application 11 is necessary.
The job chanceled. Error message:
Error converting quantity: unit KG numerator 0 denominator 0 (doc. 75555833)
Is there a possibility to start from the point where it failed or is a complete new start
(delete of set-up tables of area 11) necessary?
In the corresponding set-up tables I don't see the doc.-numbers.
Than

Hello,
thanks for you input!!!! It was very helpful.
As I understand - ALL documents must be correct in order to fill the set-up table.
Over the weekend I scheduled the job again - chanceled after 24 hours.
I set the no. of records to be ignored = 999.999. Nevertheless the job failed.
Question: Is there a way to find out how many douments are wrong? I assumed in the job-log....but here was only a doc. number.
By the way - it's all in production system.
Any idea how I can proceed? ...time slot for weekend on the system is already reserved.

Error while creating the DWH tables using DAC

Hi,
I am getting error while creating the DWH tables using DAC. I have created a ODBC DSN using merant driver with DAC repository DB credentials and the test connection is successful. And while creating the tables i gave the olap dw credentials and the DSN name which i created earlier. But it throws the error as below:
Please find the below mentioned error message
=====================================
STD OUTPUT
=====================================
CREATING SIEBEL DATABASE OBJECTS
F:\DAC\bifoundation\dac\UTILITIES\BIN\DDLIMP /I N /s N /u infdomain /p ******* /c DB_DAC /G "SSE_ROLE" /f F:\DAC\bifoundation\dac/conf/sqlgen/ctl-file/oracle_bi_dw.ctl /b "" /K "" /X "" /W N
Error while importing Siebel database schema.
=====================================
ERROR OUTPUT
=====================================
Siebel Enterprise Applications ODBC DDL Import Utility, Version 7.7 [18030] ENU
Copyright (c) 2001 Siebel Systems, Inc. All rights reserved.
This software is the property of Siebel Systems, Inc., 2207 Bridgepointe Parkway,
San Mateo, CA 94404.
User agrees that any use of this software is governed by: (1) the applicable
user limitations and other terms and conditions of the license agreement which
has been entered into with Siebel Systems or its authorized distributors; and
(2) the proprietary and restricted rights notices included in this software.
WARNING: THIS COMPUTER PROGRAM IS PROTECTED BY U.S. AND INTERNATIONAL LAW.
UNAUTHORIZED REPRODUCTION, DISTRIBUTION OR USE OF THIS PROGRAM, OR ANY PORTION
OF IT, MAY RESULT IN SEVERE CIVIL AND CRIMINAL PENALTIES, AND WILL BE
PROSECUTED TO THE MAXIMUM EXTENT POSSIBLE UNDER THE LAW.
If you have received this software in error, please notify Siebel Systems
immediately at (650) 295-5000.
F:\DAC\bifoundation\dac\UTILITIES\BIN\DDLIMP /I N /s N /u infdomain /p ***** /c DB_DAC /G SSE_ROLE /f F:\DAC\bifoundation\dac/conf/sqlgen/ctl-file/oracle_bi_dw.ctl /b /K /X /W N
Connecting to the database...
28000: [DataDirect][ODBC Oracle driver][Oracle]ORA-01017: invalid username/password; logon denied
Unable to connect to the database...
any help is appreciated.
Thanks,
RM

The fact that you are getting an "ORA-01017: invalid username/password; logon denied" message indicates that you are at least talking to the database.
The log shows that username "infdomain" is being used. Can you double check the username and password you have in DAC in a SQL*Plus/SQL Developer session?
Please mark if useful/helpful,
Andy.

Error while creating data warehouse tables.

Hi,
I am getting an error while creating data warehouse tables.
I am using OBIA 7.9.5.
The contents of the generate_clt log are as below.
>>>>>>>>>>>>>>>>>>>>>>>>>>
Schema will be created from the following containers:
Oracle 11.5.10
Universal
Conflict(s) between containers:
Table Name : W_BOM_ITEM_FS
Column Name: INTEGRATION_ID.
The column properties that are different :[keyTypeCode]
Success!
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
There are two rows in the DAC repository schema for the column and the table.
The w_etl_table_col.KEY_TYPE_CD value for DW application is UNKNOWN and for the ORA_11i application it is NULL.
Could this be the cause of the issue? If yes, why could the values be different and how to resolve this?
If not, then what could be the problem?
Any responses will be appreciated.
Thanks and regards,
Manoj.

Strange. The OBIA 7.9.5 Installation and Configuration Guide says the following:
4.3.4.3 Create ODBC Database Connections
Note: You must use the Oracle Merant ODBC driver to create the ODBC connections. The Oracle Merant ODBC driver is installed by the Oracle Business Intelligence Applications installer. Therefore, you will need to create the ODBC connections after you have run the Oracle Business Intelligence Applications installer and have installed the DAC Client.
Several other users are getting the same message creating DW tables.

Error while filling set up table SD-Billing Documents - Perform Setup

Similar Messages

Maybe you are looking for