OpenDocument parameters suppliable limit

Hi All,
We are using openDocument to link reports. We need to pass aroung 700 chars long information as prompt values to the target document (sub-report), and openDocument.jsp itself may add additional values to process the document.
For openDocument documentation suggests the functionality is limited by browser's URL limit (2083 for IE)
What is the maximum limit (no of characters) for parameters to be supplied in openDocument?
(I tired to figure this by passing values in simple prompts but time and again it varies from 400 - 600 charaters)
I have observed the final report display URL crosses the limit easily when supplied with a few hundred characters as prompt values.
PS:
I have also tried POSTING to the openDocument.jsp however ViewReport.jsp (which actually displays the report) uses all the parameter value as QueryString thus exceeding the browser URL limit.
Please suggest.
Kind Regards,
Rishi

POST won't work, since OpenDocument does client-side redirection that changes it to GET for the ultimate viewer call.
OpenDocument also puts there context and environment info, lengthening the URL.
So you won't (1) get consistent results for all environments, and (2) practical max URL would be shorter than expected given the max IE allows.
Sincerely,
Ted Ueda

Similar Messages

RAS Java SKD, parameters size limit with ParameterFieldController?

Hello,
I use the RAS SDK to generate a report and save it to PDF and XML files from a java web application (I'm new to Crystal and its SDK but it works great!). I'm using parameters that I set using ParameterFieldController.setCurrentValue()... everything's allright. Now, I need to add a new parameter (a list of Strings) and the user wants my application to be able to handle thousands of elements in that list... so I'm wondering... what's the limit? is there a limit?
I've not found this information into the SDK documentation or the ParameterFieldController's javadoc...
Can anyone help me on this one?
Thanks!

There's no pre-defined limit.
But note that if you're pushing all that list of data to the RDBMS layer, the Crystal will push all that list of data to the RDBMs layer. No guarantees of what's going to happen here.
Sincerely,
Ted Ueda

Rwcgi60 parameters size limit

Hi all,
Im wondering if theres a size limit to parameters passed from a web page to reports using rwcgi60.
With the tests I did using NT parameters with more than 981 characters causes the following error in the CGI execution:
Oracle Reports Server CGI - Unable to communicate with the Reports Server.
Im using reports6i version 6.0.8.11.3
I tried to use it in a Linux box with the last patch but I got the same error.
Is this a non documented bug?

hello,
you might run into the restriction of 255 characters when passing the parameters on the URL. do you see the parameters in your URL after you hit submit in your form ? if yes, you are using GET to pass the parameters. use POST instead that should solve the problem.
regards,
the oracle reports team

OpenDocument - Parameters is lost when opening the report with token

Hello,
we want to migrate our BO Enterprise (XI R3) from Tomcat to IIS.
We developed an application in which you can open reports by using the opendocument-url.
It was no problem with our old BO-Enterprise Server (tomcat/jsp), but with our new BO-System (IIS / aspx) the parameter is not passed, so that you have got to fill out the parameter mask, before the report is opened.
http://servername/OpenDocument/opendoc/openDocument.aspx?iDocID=1926&lsSParameter=307&token=....2082J38Mfsg5PvRXmk002080JuLfwCe5XZw0T0sT
Any suggestions?
Thanks,
Peter

So does it still prompt for the parameter even if you don't pass the token and you manually log on?
If so, you're asking in the wrong forum - you'd ask in the report-type-specific forum.
Sincerely,
Ted Ueda

Passing Parameters via OpenDocument URL to OLAP Analysis .amw

Hello together,
did anyone ever manage to successfully create an OpenDocument URL which passes parameters to an existing analysis workspace .amw?
We already linked to other .crp and BEx reports, but maybe .amw needs some special syntax..
I appreciate every hint
Thanks
CR Enterprise 4.0 SP2 in usage

Hi,
I can confirm: The situation for A-OLAP is the same as it was for Voyager.
Analysis, like voyager, supports outbound opendoc params (ie pass context to WebI/CR) but not inbound params. The only exception is that you can specify which Voyager workspace to open.
Voyager/analysis supports SAP connection parameters on opendoc, but this is a manual selection in prompts. You cannot programmatically set connection variables.
Today we also support "Jumplinks"... a feature in both Voyager and A-OLAP that allows contextual information to be passed to a pre-defined Crystal Report.
For BI4.1 (end 2012) SAP plans to make A-OLAP more open. This includes supporting SAP's Report-Report-Interface (RRI) and extending the OpenDocument parameters beyond just the workspace name that is supported today.
Regards,
H

Selection Screen Parameters in SQL statements

Very new ABAP programmer here, so sorry if this is a really dumb question.
I'm trying to use my selection screen parameters to limit what is pulled in by my SQL statement (which seems to me to be a very logical thing to do). But I'm having a problem, that when no values are entered in the parameters, no data is returned in the table instead of all the data being returned.
Here is the code I have now:
SELECT cname1 akostl aorgeh asname apernr bbegda bendda bstatu
         bconfl bmedcf breasn breman b~rqday
INTO CORRESPONDING FIELDS OF TABLE it_record
   FROM ( ( pa0001 AS a
      INNER JOIN pa0672 AS b ON bpernr = apernr )
      INNER JOIN t500p AS c ON cpersa = awerks )
WHERE b~reman in so_reman
    AND a~kostl in so_kostl
    AND a~orgeh = p_orgeh
    AND b~begda = p_begda
    AND b~statu = p_statu
    AND b~confl = p_confl
    AND b~medcf = p_medcf
    AND b~reasn = p_reasn
    AND b~rqday = p_rqday
    AND c~name1 = p_name1.
Can anyone tell me what I'd need to do to make it return properly?

When you use parameters and no value is entered, it is treated as initial value. and the select statement looks for the initial values for those fields in the tabl;e...
you can make the parameters mandatory..then the user would be forced to enter something....
also you could do the following..
instead of parameters, use select-options with the addition no intervals and no extension, then practically it looks like a parameter but internally it is a select-option...
and in the select statement, give conditions like....field1 in <s_option name>....in this case if the user is not entering a value ...it is treated as *...
Thnaks & Regards,
Renjith

Limit for EXPORT TO MEMORY ID statement

Hi All,
I would like to know whether is any limit to the size of the data(size of <int_tab> below) which we can export to ABAP memory using statement -
EXPORT <int_tab> TO MEMORY ID 'XXXX'.
I have read the F1 help of export, there size 30000 bytes is mentioned if we export to shared memory but for export to ABAP memory it is mentioned anything like that.
Can someone help me out in finding this, or there is no limitations for exporting to ABAP memory?
Regards
Munish Garg

I supposed that the abap code hasn't limits, but the admin has certain parameters for limit users memory or something else. Overcharging system memory get that machines are slower than usual.

Is it possible to sort report using parameters?

Hi,
I am building a report - which generates select query based on the parameters entered by the user.
Could you help me with how to sort output with the parameter chosen by the user himself? Thanks,

I will give you 2 answers since I am not sure exactly how your report runs.
Lets say your users choose a couple parameters to limit certain columns by in your where clause. In this case, you would want to just create a user parameter, and use that parameter in the where clause.
select col
from table
where job_id = :P_JOB_ID and
start_date between :P_START_DATE and :P_END_DATEPretty simple. Now here is how I would do it if those are optional parameters, and the user could enter a value, or could leave all blank.
select col
from table
where job_id = nvl(:P_JOB_ID, job_id) and
start_date between nvl(:P_START_DATE, start_date) and
nvl(:P_END_DATE, end_date)If its null, it will set the column equal to each other, and will return all the rows (good little trick).
The other case is if you need a different select/where clause entirely based on what the user sends in. For example, lets say you have 2 entirely different queries based on a certain parameter. Then you'd want to use lexical parameters and an after parameter trigger.
I think you are looking for the first scenario, so try that and post back if you are looking for something different

BAPI_SCEC_CREATE creating "limit item" sampe code

Has anyone loaded shopping carts using this BAPI for "Limit Items"? DO you have sample code for setting I_ITEMS & I_LIMIT tables? I can get this BAPI to create carts for goods just fine, but not able to feed it the right parameters for limit items.
ie i_items-item_type = 'LIMI'.
Sample code appreciated.

Dear Poster
Your thread has had no response since it's creation over
2 weeks ago, therefore, I recommend that you either:
- Rephrase the question.
- Provide additional Information to prompt a response.
- Close the thread if the answer is already known.
Thank you for your compliance in this regard.
Jason Boggans
SAP SRM SDN Moderator

Opendocument.jsp in iframes in BOBJ R3

Using BOBJ Relesase 2 we created a dashboard using iframes and targeting each ifreame to a crystal report with opendocument'jsp. Each report had a target object (chart) to set the focus for the viewer. Only issue was a default margin in the viewer that was in the DHTMLViewer.jsp page that needed to be set to zero. Once this was corrected the report would fill the iframe perfectly.
We are now in the process of migrating to R3 and have found the updated viewer uncooperative and have a couple of issues:
All around the chart there is a margin in the viewer. I have changed the page settings to remove the report margins but it looks like I need to find the built in margin on the viewer. Does anyone know where the margin values are kept
The actual frame of the viewer also appears in the hub, Can this be turned off? Especially annoying is that we use web elements to suppress the toolbars and when this si done the footer of the report expands.
Thanks in Advance
Jack

hello Jack,
not sure if this will help out here but there are a couple of opendocument parameters that you can try...
append these to the end of your opendocument url to see if this changes the margins...at least they will help you in formatting with the new viewer...
&toolbar=hide
&drilldowntabs=hide
&sReportMode=weblayout
as an example you may be calling a report in your iframe similar to the following...
WETargetPath ("rpt","Name", "myreport", "weTarget=quadrantA&toolbar=hide&drilldowntabs=hide&sReportMode=weblayout")
toolbar=hide - part of the new javascript sdk wherein you can use this switch in an opendoc link to hide the toolbar, instead of using webelements
drilldowntabs=hide - especially usefull for getting rid of those tabs that pop up in drill down in the new viewer
sReportMode=weblayout - changes background and orientation back to older viewer as close as possible...note that you will still have a frame around the viewer...nothing you can do about that frame
i hope that this may help to resolve your issue.
cheers,
jamie

Avoid report refresh when updating cascade parameters

I have a report with 3 cascade parameters. The first parameter, region, is independent. The second parameter, zone, depends on region. The third parameter, store, depends both on region and zone. These are multi value parameters. The report is
viewed directly in the "/reports" URL, so there are no custom applications that can modify it.
I have a data set for each parameter and obviously use parameters to limit the results of the second and third paramters. My user doesn't want the page to refresh after you set the first and second parameter. I'm not sure that's possible because it's a native
reporting services action.
I've tried to bring all the results in second and third datasets and use filters based in the previous parameter, but the lists go blank even though the "Always refresh" property of the parameter is selected.
Is there a NATIVE way to avoid the page from refreshing?

Hi Dany,
According to your description, you want avoid the second parameter and third parameter to be refresh after change the value on the first parameter, right? In Reporting Services, the report will reload after the parameters value were changed no matter the parameter
is a cascading parameter or not. This is default setting, so as Martina said, your requirement cannot be achieved currently.
Besides, if you have any concerns about this feature, you can submit a feedback at http://connect.microsoft.com/SQLServer/Feedback and hope it is resolved in the next release of service pack or product.
Thank you for your understanding.
Regards,
Charlie Liao
Charlie Liao
TechNet Community Support

Password Parameters

I am trying to find out how to set password parameters in oracle. I want to be able to set minimum length password, password timeouts and so forth. Can this be done in oracle and if so where?
Thanks in advance

CREATE PROFILE
Purpose
Use the CREATE PROFILE statement to create a profile, which is a set of limits on database resources. If you assign the profile to a user, that user cannot exceed these limits.
See Also:
Oracle9i Database Administrator's Guide for a detailed description and explanation of how to use password management and protection
Prerequisites
To create a profile, you must have CREATE PROFILE system privilege.
To specify resource limits for a user, you must:
Enable resource limits dynamically with the ALTER SYSTEM statement or with the initialization parameter RESOURCE_LIMIT. (This parameter does not apply to password resources. Password resources are always enabled.)
Create a profile that defines the limits using the CREATE PROFILE statement
Assign the profile to the user using the CREATE USER or ALTER USER statement
See Also:
ALTER SYSTEM for information on enabling resource limits dynamically
Oracle9i Database Reference for information on the RESOURCE_LIMIT parameter
CREATE USER and ALTER USER for information on profiles
Syntax
create_profile::=
Text description of create_profile
resource_parameters::=
Text description of resource_parameters
password_parameters::=
Text description of password_parameters
Semantics
profile
Specify the name of the profile to be created. Use profiles to limit the database resources available to a user for a single call or a single session.
Oracle enforces resource limits in the following ways:
If a user exceeds the CONNECT_TIME or IDLE_TIME session resource limit, Oracle rolls back the current transaction and ends the session. When the user process next issues a call, Oracle returns an error.
If a user attempts to perform an operation that exceeds the limit for other session resources, Oracle aborts the operation, rolls back the current statement, and immediately returns an error. The user can then commit or roll back the current transaction, and must then end the session.
If a user attempts to perform an operation that exceeds the limit for a single call, Oracle aborts the operation, rolls back the current statement, and returns an error, leaving the current transaction intact.
Notes:
You can use fractions of days for all parameters that limit time, with days as units. For example, 1 hour is 1/24 and 1 minute is 1/1440.
You can specify resource limits for users regardless of whether the resource limits are enabled. However, Oracle does not enforce the limits until you enable them.
See Also:
"Creating a Profile: Example"
UNLIMITED
When specified with a resource parameter, UNLIMITED indicates that a user assigned this profile can use an unlimited amount of this resource. When specified with a password parameter, UNLIMITED indicates that no limit has been set for the parameter.
DEFAULT
Specify DEFAULT if you want to omit a limit for this resource in this profile. A user assigned this profile is subject to the limit for this resource specified in the DEFAULT profile. The DEFAULT profile initially defines unlimited resources. You can change those limits with the ALTER PROFILE statement.
Any user who is not explicitly assigned a profile is subject to the limits defined in the DEFAULT profile. Also, if the profile that is explicitly assigned to a user omits limits for some resources or specifies DEFAULT for some limits, the user is subject to the limits on those resources defined by the DEFAULT profile.
resource_parameters
SESSIONS_PER_USER
Specify the number of concurrent sessions to which you want to limit the user.
CPU_PER_SESSION
Specify the CPU time limit for a session, expressed in hundredth of seconds.
CPU_PER_CALL
Specify the CPU time limit for a call (a parse, execute, or fetch), expressed in hundredths of seconds.
CONNECT_TIME
Specify the total elapsed time limit for a session, expressed in minutes.
IDLE_TIME
Specify the permitted periods of continuous inactive time during a session, expressed in minutes. Long-running queries and other operations are not subject to this limit.
LOGICAL_READS_PER_SESSION
Specify the permitted number of data blocks read in a session, including blocks read from memory and disk.
LOGICAL_READS_PER_CALL
Specify the permitted the number of data blocks read for a call to process a SQL statement (a parse, execute, or fetch).
PRIVATE_SGA
Specify the amount of private space a session can allocate in the shared pool of the system global area (SGA), expressed in bytes. Use K or M to specify this limit in kilobytes or megabytes.
Note:
This limit applies only if you are using Shared Server architecture. The private space for a session in the SGA includes private SQL and PL/SQL areas, but not shared SQL and PL/SQL areas.
COMPOSITE_LIMIT
Specify the total resource cost for a session, expressed in service units. Oracle calculates the total service units as a weighted sum of CPU_PER_SESSION, CONNECT_TIME, LOGICAL_READS_PER_SESSION, and PRIVATE_SGA.
See Also:
ALTER RESOURCE COST for information on how to specify the weight for each session resource
If you specify expr for any of these parameters, the expression can be of any form except scalar subquery expression.
See Also:
"Setting Profile Resource Limits: Example"
password_parameters
FAILED_LOGIN_ATTEMPTS
Specify the number of failed attempts to log in to the user account before the account is locked.
PASSWORD_LIFE_TIME
Specify the number of days the same password can be used for authentication. The password expires if it is not changed within this period, and further connections are rejected.
PASSWORD_REUSE_TIME
Specify the number of days before which a password cannot be reused. If you set PASSWORD_REUSE_TIME to an integer value, then you must set PASSWORD_REUSE_MAX to UNLIMITED.
PASSWORD_REUSE_MAX
Specify the number of password changes required before the current password can be reused. If you set PASSWORD_REUSE_MAX to an integer value, then you must set PASSWORD_REUSE_TIME to UNLIMITED.
PASSWORD_LOCK_TIME
Specify the number of days an account will be locked after the specified number of consecutive failed login attempts.
PASSWORD_GRACE_TIME
Specify the number of days after the grace period begins during which a warning is issued and login is allowed. If the password is not changed during the grace period, the password expires.
PASSWORD_VERIFY_FUNCTION
The PASSWORD_VERIFY_FUNCTION clause lets a PL/SQL password complexity verification script be passed as an argument to the CREATE PROFILE statement. Oracle provides a default script, but you can create your own routine or use third-party software instead.
For function, specify the name of the password complexity verification routine.
Specify NULL to indicate that no password verification is performed.
Restrictions on Password Parameters
If PASSWORD_REUSE_TIME is set to an integer value, PASSWORD_REUSE_MAX must be set to UNLIMITED. If PASSWORD_REUSE_MAX is set to an integer value, PASSWORD_REUSE_TIME must be set to UNLIMITED.
If both PASSWORD_REUSE_TIME and PASSWORD_REUSE_MAX are set to UNLIMITED, then Oracle uses neither of these password resources.
If PASSWORD_REUSE_MAX is set to DEFAULT and PASSWORD_REUSE_TIME is set to UNLIMITED, then Oracle uses the PASSWORD_REUSE_MAX value defined in the DEFAULT profile.
If PASSWORD_REUSE_TIME is set to DEFAULT and PASSWORD_REUSE_MAX is set to UNLIMITED, then Oracle uses the PASSWORD_REUSE_TIME value defined in the DEFAULT profile.
If both PASSWORD_REUSE_TIME and PASSWORD_REUSE_MAX are set to DEFAULT, then Oracle uses whichever value is defined in the DEFAULT profile.
See Also:
"Setting Profile Password Limits: Example"
Examples
Creating a Profile: Example
The following statement creates the profile new_profile:
CREATE PROFILE new_profile
LIMIT PASSWORD_REUSE_MAX DEFAULT
PASSWORD_REUSE_TIME UNLIMITED;
Setting Profile Resource Limits: Example
The following statement creates the profile app_user:
CREATE PROFILE app_user LIMIT
SESSIONS_PER_USER UNLIMITED
CPU_PER_SESSION UNLIMITED
CPU_PER_CALL 3000
CONNECT_TIME 45
LOGICAL_READS_PER_SESSION DEFAULT
LOGICAL_READS_PER_CALL 1000
PRIVATE_SGA 15K
COMPOSITE_LIMIT 5000000;
If you then assign the app_user profile to a user, the user is subject to the following limits in subsequent sessions:
The user can have any number of concurrent sessions.
In a single session, the user can consume an unlimited amount of CPU time.
A single call made by the user cannot consume more than 30 seconds of CPU time.
A single session cannot last for more than 45 minutes.
In a single session, the number of data blocks read from memory and disk is subject to the limit specified in the DEFAULT profile.
A single call made by the user cannot read more than 1000 data blocks from memory and disk.
A single session cannot allocate more than 15 kilobytes of memory in the SGA.
In a single session, the total resource cost cannot exceed 5 million service units. The formula for calculating the total resource cost is specified by the ALTER RESOURCE COST statement.
Since the system_manager profile omits a limit for IDLE_TIME and for password limits, the user is subject to the limits on these resources specified in the DEFAULT profile.
Setting Profile Password Limits: Example
The following statement creates the same app_user2 profile with password limits values set:
CREATE PROFILE app_user2 LIMIT
FAILED_LOGIN_ATTEMPTS 5
PASSWORD_LIFE_TIME 60
PASSWORD_REUSE_TIME 60
PASSWORD_REUSE_MAX UNLIMITED
PASSWORD_VERIFY_FUNCTION verify_function
PASSWORD_LOCK_TIME 1/24
PASSWORD_GRACE_TIME 10;
This example uses Oracle's password verification function, verify_function. Please refer to Oracle9i Database Administrator's Guide for information on using this verification function provided by Oracle or designing your own verification function.
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96540/statements_611a.htm#SQLRF01310
Joel P�rez

Opendocument sReportPart

Hi
I'm currently trying to find a solution where we can display a particular part of a report such as a chart or table within an iFrame of a webpage. I've been looking into one the the opendocument parameters sReportPart though unfortunately haven't been successful in getting it to work.
The URL that is being passed is as follows:
.../businessobjects/enterprise115/InfoView/scripts/openDocument.aspx?sType=wid&sRefresh=Y&iDocID=8649&instance=last&mode=part&sReportPart=UIREF:RID=143035:BID=143057&lsManalyst=-1&lsMcId=all&lsMclientTier=all&lsMresearchDiv=all&lsMsector=-1
Any help would be great
Thanks

Hi
Thanks for your reply. According to other forums developers have achieved this in R2 with webi reports
http://www.forumtopics.com/busobj/viewtopic.php?t=61862&postdays=0&postorder=asc&highlight=hyperlink&start=15
http://www.forumtopics.com/busobj/viewtopic.php?t=133117&highlight=sreportpart
Thanks

Re: stoping sales to customer when credit limit exceeds

Hai
The credit limit for a customer is fixed at certain amount.Also credit period is fixed at a certain no of days say 30 days.Both these conditions are cumulative. Whichever happens earlier further sales to that particular customer should be blocked.How to set up this?I would like to know what changes should be made in business partner master data or in any other window.Is it available insapB1 8.8 by default .Can this be done in sap B18.8 without coding ?
Edited by: aruntb on Jun 17, 2010 10:23 AM
Edited by: aruntb on Jun 17, 2010 10:24 AM
Edited by: aruntb on Jun 17, 2010 11:04 AM

Hi,
Please check your Online Help (F1) !
General Settings > BP Tab
===
Customer Activity Restrictions You can restrict the creation of sales documents for customers and prompt a warning message according to the following parameters:
Credit Limit u2013 Checks whether adding the sales document for the customer causes deviation from the credit limit defined for the customer (Payment Terms tab in the Business Partner Master Data window).
A warning message appears if <the customer's account balance> + <the amount of the current document> exceeds the customer's credit line.
Commitment Limit u2013 Checks whether adding the sales document for the customer causes deviation from the commitment limit defined for the customer (Payment Terms tab in the Business Partner Master Data window).
A warning message appears if <the customer's account balance>+ <the total amount in undeposited checks> + <the amount of the current document> exceeds the customer's commitment limit.
Once you select the required option(s) described above, select the type of documents to which the restrictions apply and for which a warning message is launched:
- A/R Invoice
- Delivery
- Sales Order
These setting are updated immediately per company, for all users.
===
Cheers

CE Bank Statement Open Interface

Hi,
I have successfully run the Bank Statement Loader for Open Interface.
Then I run the 2nd step > Bank Statement Import:
The docs said:
2. Bank Statement Import
The required parameters to this job are the following:
Bank Branch Name - Provide the bank branch name that you setup in the Bank
Account Setup section.
GL Date - Although this parameter is not marked as required, the import will
often fail if you do not provide a value for this parameter. The date must in
an open period in both AP and AR.
Note: If you have multiple files loaded, but only want to import one of them,
use the Statement Date or Statement Number range parameters to limit the import
job.
If successful, this program moves records from the
CE_STATEMENT_HEADERS_INTERFACE and CE_STATEMENT_LINES_INTERFACE tables into
the CE_STATEMENT_HEADERS and CE_STATEMENT_LINES tables.May run request was successful, and I got this logs
Output log
                                                               Execution Report                       Report Date   26-MAR-09 20:28
                                                                                                             Page     1 of      1
Statement Number        -
Statement Date          -
Bank Branch Name       Rufino                                       Bank Name            Asia United Bank
Bank Account Number     -                                           Bank Account Currency    -
Bank Account Name       -
                          ******* Program Ran Successfully, No Error Found. ********View Log
+---------------------------------------------------------------------------+
Cash Management: Version : 12.0.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
CEIMPERR module: Bank Statement Import Execution Report
+---------------------------------------------------------------------------+
Current system time is 26-MAR-2009 20:28:57
+---------------------------------------------------------------------------+
+-----------------------------
| Starting concurrent program execution...
+-----------------------------
Arguments
P_BANK_BRANCH_ID='3104'
P_SQL_TRACE='N'
P_DISPLAY_DEBUG='N'
Current NLS_LANG and NLS_NUMERIC_CHARACTERS Environment Variables are :
American_America.US7ASCII
Enter Password:
Report Builder: Release 10.1.2.2.0 - Production on Thu Mar 26 20:28:58 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
+---------------------------------------------------------------------------+
Start of log messages from FND_FILE
+---------------------------------------------------------------------------+
+---------------------------------------------------------------------------+
End of log messages from FND_FILE
+---------------------------------------------------------------------------+
+---------------------------------------------------------------------------+
Executing request completion options...
+------------- 1) PRINT   -------------+
Printing output file.
               Request ID : 328310
         Number of copies : 0
                  Printer : noprint
+--------------------------------------+
Finished executing request completion options.
+---------------------------------------------------------------------------+
Concurrent request completed successfully
Current system time is 26-MAR-2009 20:29:00
+---------------------------------------------------------------------------+Why is that my
CE_STATEMENT_HEADERS
and
CE_STATEMENT_LINES
have no rows?
Thanks a lot

The error tables has no contents either :(
The trace files does not help much , I want to know the program part that inserts into the target tables, but its just showing other reports process :((
trace file
PARSING IN CURSOR #2 len=11462 dep=0 uid=173 oct=3 lid=173 tim=1209109154828460 hv=1080153458 ad='436471d8'
SELECT /* Created Miscellaneous Receipt */
        l1.meaning                              error_type,
        'D'                             break_group,
        sh.statement_number                     statement_no,
        sh.doc_sequence_value                                   doc_sequence_value,
        sl.line_number                  line_no,
        sh.statement_date                       statement_date,
        sl.trx_date                             trx_date,
        ba.bank_account_num                     bank_acc,
        ba.bank_account_name            bank_account_name,
        ba.currency_code                        acc_currency,
        NULL                            message_name,
        nvl(sl.amount,0)                        amount,
        acr.currency_code                       C_CURRENCY_CODE,
        l2.meaning                              trx_type,
        acr.receipt_number                      trx_no,
        'CE'                            application_short_name,
        bb.branch_party_id                      bank_branch_id
FROM        ce_lookups                  l1,
        ce_lookups                      l2,
        ce_bank_accts_gt_v                      ba,
        ce_bank_branches_v                      bb,
                   ce_statement_headers         sh,
                   ce_statement_lines                   sl,
        ar_cash_receipts_all    acr,
                   ce_222_reconciled_v cr
WHERE l1.lookup_type = 'ABR_REPORT_EXCEPTIONS' AND l1.lookup_code = 'MISC_RECEIPT_CREATED' AND l2.lookup_type = 'BANK_TRX_TYPE' AND l2.lookup_code = sl.trx_type AND bb.branch_party_id = ba.bank_branch_id AND bb.branch_party_id = : P_BANK_BRANCH_ID AND ba.bank_account_id = sh.bank_account_id AND sh.statement_header_id = sl.statement_header_id AND ba.bank_account_id = DECODE ( : P_BANK_ACCOUNT_ID , NULL , ba.bank_account_id , : P_BANK_ACCOUNT_ID ) AND to_char ( sh.statement_date , 'YYYY/MM/DD' ) >= nvl ( to_char ( : P_STAT_DATE_FROM , 'YYYY/MM/DD' ) , to_char ( sh.statement_date , 'YYYY/MM/DD' ) ) AND to_char ( sh.statement_date , 'YYYY/MM/DD' ) <= nvl ( to_char ( : P_STAT_DATE_TO , 'YYYY/MM/DD' ) , to_char ( sh.statement_date , 'YYYY/MM/DD' ) ) AND sh.statement_number >= nvl ( : P_STAT_NUMBER_FROM , sh.statement_number ) AND sh.statement_number <= nvl ( : P_STAT_NUMBER_TO , sh.statement_number ) and acr.cash_receipt_id = cr.cash_receipt_id and cr.statement_line_id = sl.statement_line_id and acr.comments = 'Created by Auto Bank Rec' UNION ALL SELECT    /* Reconciliation errors */
        l1.description                  error_type,
        'C'                             break_group,
        sh.statement_number                     statement_no,
        sh.doc_sequence_value                                   doc_sequence_value,
        sl.line_number                  line_no,
        sh.statement_date                       statement_date,
        sl.trx_date                             trx_date,
        ba.bank_account_num                             ba.bank_account_name            bank_account_name,
        ba.currency_code                        acc_currency,
        e.message_name                          message_name,
        to_number(NULL)                 amount,
        ba.currency_code                        C_CURRENCY_CODE,
        NULL                            trx_type,
        NULL                            trx_no,
        NVL(e.application_short_name,'CE')      application_short_name,
        bb.branch_party_id                      bank_branch_id
FROM        ce_lookups                          l1,
        ce_bank_accts_gt_v                      ba,
        ce_bank_branches_v                      bb,
                   ce_statement_headers         sh,
        ce_reconciliation_errors                e
WHERE l1.lookup_type = 'ABR_REPORT_EXCEPTIONS' AND l1.lookup_code = 'RECONCILIATION' AND bb.branch_party_id = ba.bank_branch_id AND bb.branch_party_id = : P_BANK_BRANCH_ID AND ba.bank_account_id = sh.bank_account_id AND ba.account_classification = 'INTERNAL' AND sh.statement_header_id = e.statement_header_id AND e.statement_line_id is null AND ba.bank_account_id = DECODE ( : P_BANK_ACCOUNT_ID , NULL , ba.bank_account_id , : P_BANK_ACCOUNT_ID ) AND to_char ( sh.statement_date , 'YYYY/MM/DD' ) >= nvl ( to_char ( : P_STAT_DATE_FROM , 'YYYY/MM/DD' ) , to_char ( sh.statement_date , 'YYYY/MM/DD' ) ) AND to_char ( sh.statement_date , 'YYYY/MM/DD' ) <= nvl ( to_char ( : P_STAT_DATE_TO , 'YYYY/MM/DD' ) , to_char ( sh.statement_date , 'YYYY/MM/DD' ) ) AND sh.statement_number >= nvl ( : P_STAT_NUMBER_FROM , sh.statement_number ) AND sh.statement_number <= nvl ( : P_STAT_NUMBER_TO , sh.statement_number ) UNION ALL ( SELECT     /* Header interface errors */
        l.description                   error_type,
        'A'                             break_group,
        e.statement_number                      statement_no,
                  to_number(NULL)                       doc_sequence_value,
        1                               line_no,
        sh.statement_date                       statement_date,
        sh.statement_date                       trx_date,
        e.bank_account_num                      bank_acc,
        ba.bank_account_name            bank_account_name,
        ba.currency_code                        acc_currency,
        e.message_name                  message_name,
        0                               amount,
        ' '                             C_CURRENCY_CODE,
        ' '                             trx_type,
        ' '                             trx_no,
        NVL(e.application_short_name,'CE')      application_short_name,
        bb.branch_party_id                      bank_branch_id
FROM         ce_lookups                 l,
                   ce_statement_headers_int     sh,
                   ce_header_interface_errors   e,
        ce_bank_branches_v              bb,
        ce_bank_accts_gt_v              ba
bank_acc,   WHERE l.lookup_type = 'ABR_REPORT_EXCEPTIONS' AND l.lookup_code = 'STATEMENT' AND sh.bank_account_num = e.bank_account_num AND sh.statement_number = e.statement_number AND sh.bank_branch_name = bb.bank_branch_name AND e.bank_account_num = NVL ( ba.bank_account_num , e.bank_account_num ) AND ba.bank_branch_id = bb.branch_party_id AND bb.bank_branch_name = DECODE ( : C_BANK_BRANCH_NAME_DSP , : C_ALL_TRANSLATION , bb.bank_branch_name , : C_BANK_BRANCH_NAME_DSP ) AND ba.bank_account_id = NVL ( : P_BANK_ACCOUNT_ID , ba.bank_account_id ) AND ba.account_classification = 'INTERNAL' AND to_char ( sh.statement_date , 'YYYY/MM/DD' ) >= nvl ( to_char ( : P_STAT_DATE_FROM , 'YYYY/MM/DD' ) , to_char ( sh.statement_date , 'YYYY/MM/DD' ) ) AND to_char ( sh.statement_date , 'YYYY/MM/DD' ) <= nvl ( to_char ( : P_STAT_DATE_TO , 'YYYY/MM/DD' ) , to_char ( sh.statement_date , 'YYYY/MM/DD' ) ) AND sh.statement_number >= nvl ( : P_STAT_NUMBER_FROM , sh.statement_number ) AND sh.statement_number <= nvl ( : P_STAT_NUMBER_TO , sh.statement_number )thanks

OpenDocument parameters suppliable limit

Similar Messages

Maybe you are looking for