BPEL to JDE 811, parameters are passed as zero

Hi,
We have finished all configuration from Adapter Installation guide as well as from User's guide.
When we are making a call from our BPEL to JDE 811 functions,
1) For the functions that are not having any parameters (e.g. GetAuditInfo), are returning correct outputs or say valid response. but
2) When we make a call to function that are having parameters (e.g. GetYearDescription, GetEffectiveAddress), the values of the parameters are being passed as zero. Or JDE is sending responses like the parameters we passed were absolute zero.
like for GetYearDescription, i'm giving following XML as input,
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body xmlns:ns1="http://xmlns.oracle.com/JDE_SERVICE2">
<ns1:jdeRequest type="callmethod">
<callMethod name="GetYearDescription" runOnError="no">
<params>
<param name="mnCalendarYear">95</param>
</params>
<onError abort="yes"/>
</callMethod>
</ns1:jdeRequest>
</soap:Body>
</soap:Envelope>
But instead of 1995, we are getting response as 2000 as parameter values is somehow passed as zero.
We have checked on JDE side and tested above functions are working OK.
Can anybody help us and say why the values are being treated as zero.
Thanks,
Nirav

Hi,
Thanks for the response, but I'm still facing the issue.
As you suggested, I configured my Application Explorer for Attribute Style and get connected. I generated the WSDL and Schema for GetYearDescription. I created the BPEL process and again gave the input as I mentioned above, but it is still giving me 2000 as output. Am'I following the correct process ?
Invoke Audit Trail from BPELConsole for after running the process is as below :
<messages><Invoke_1_GetYearDescription_InputVariable><part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="input_GetYearDescription"><jdeRequest type="callmethod" session="" xmlns="urn:iwaysoftware:jde/services/JDEJAVA_CMFGBASE/B3000260/GetYearDescription">
<callMethod name="GetYearDescription" runOnError="no" xmlns="">
<params>
<param name="mnCalendarYear">95</param>
</params>
<onError abort="yes"/>
</callMethod>
</jdeRequest>
</part></Invoke_1_GetYearDescription_InputVariable><Invoke_1_GetYearDescription_OutputVariable><part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="response-headers">[]</part><part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="output_GetYearDescription"><jdeResponse xmlns="urn:iwaysoftware:jde/services/JDEJAVA_CMFGBASE/B3000260/GetYearDescription" user="PSFT" type="callmethod" session="6656.1211956064.15" environment="DV811" role="*ALL">
<callMethod name="GetYearDescription" runOnError="no">
<returnCode code="0"/>
<params>
<szYearDescription>2000</szYearDescription>
</params>
</callMethod>
</jdeResponse>
</part></Invoke_1_GetYearDescription_OutputVariable></messages>
And here is my WSDL which I generated with Attribute_Style JDE Connection from Application Explorer :
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="GetYearDescription"
targetNamespace="http://xmlns.oracle.com/pcbpel/iWay/wsdl/JDEdwards/JDEOne/GetYearDescription"
xmlns:plt="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns:jca="http://xmlns.oracle.com/pcbpel/wsdl/jca/"
xmlns:iWay="http://xmlns.oracle.com/pcbpel/adapter/iWay/"
xmlns:GetYearDescription="http://xmlns.oracle.com/pcbpel/iWay/wsdl/JDEdwards/JDEOne/GetYearDescription"
xmlns:pc="http://xmlns.oracle.com/pcbpel/"
xmlns:iWayRequest="urn:iwaysoftware:jde/services/JDEJAVA_CMFGBASE/B3000260/GetYearDescription" xmlns="http://schemas.xmlsoap.org/wsdl/">
<types>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="urn:iwaysoftware:jde/services/JDEJAVA_CMFGBASE/B3000260/GetYearDescription"
xmlns:ns="urn:iwaysoftware:jde/services/JDEJAVA_CMFGBASE/B3000260/GetYearDescription" elementFormDefault="qualified">
<xsd:element name="jdeRequest">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="callMethod">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="params">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="param" minOccurs="0" maxOccurs="2">
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:attribute name="name" use="required">
<xsd:simpleType>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="mnCalendarYear"/>
<xsd:enumeration value="szYearDescription"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="onError" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:any minOccurs="0"/>
</xsd:sequence>
<xsd:attribute name="abort" use="required">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="yes"/>
<xsd:enumeration value="no"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="name" use="required">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="GetYearDescription"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="app" type="xsd:string" use="optional"/>
<xsd:attribute name="runOnError" use="optional">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="yes"/>
<xsd:enumeration value="no"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="returnNullData" use="optional">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="yes"/>
<xsd:enumeration value="no"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="trans" type="xsd:string" use="optional"/>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="type" use="required">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="callmethod"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="session" type="xsd:string" use="optional"/>
<xsd:attribute name="sessionidle" type="xsd:string" use="optional"/>
</xsd:complexType>
</xsd:element>
</xsd:schema>
...Response Schema ...
Can you tell me that what exactly should be my input XML. soap:Envelope and soap:Body are required right ?
Thanks,
Nirav

Similar Messages

  • How to Identify the count , If multiple parameters are passed using Pipe Delimited string

    Hi,
    We are passing Pipe delimited string to the parameter and I want to know how many values we are passing to the parameter.
    Here is the example
    Parameter.Grant: 24|34|54|67
    I am using below expression, but it is not giving the right values. Please let me know if  I am missing anything or is it possible.
    =iif(parameters!Grant.Count>1,"Multiple value selected",parameters!Grant.Value)

    Hi NaveenCR,
    According to your description, you used pipe delimited multi-value parameter in the report, you want to know how many values passed to the parameter. If that is the case, please refer to the following steps:
    In Design view, click Text Box in the Toolbox.
    On the design surface, click and then drag a box to the desired size of the text box.
    Right-click inside of the text box, then click Expression.
    In Expression text box, type the expression like below:
    =iif(split(Parameters! Grant.Value,"|").Length>1," Multiple value selected",Parameters!Grant.Value)
    The following screenshots are for your reference:
    If you have any more questions, please feel free to ask.
    Thanks,
    Wendy Fu
    If you have any feedback on our support, please click
    here.
    Wendy Fu
    TechNet Community Support

  • How BAPI Tables parameters are passed by reference

    Hi Gurus,
                     I have a genuine doubt regarding BAPI parameters. I would like to point out the genreal rules of bapi like,
    1. BAPI parameters should be passed by value. (Because they are rfc fm's. So both systems will be in different servers. This is the normal scenario.)
    2. But the tables parameters in BAPI can't be passed by value. Instead they are passed by reference.
    3. I know they use some kind of delta mechanism to transfer tables parameters to remote servers.
    So gurus I would like to know what exactly happens when a tables parameter is passed. And also I didn't understand the delta mechanism. Kindly guide me.
    Thanks in advance,
    Jerry Jerome

    You'll see in [SAP Library - RFC - Parameter Handling in Remote Calls|http://help.sap.com/saphelp_nw04s/helpdata/en/22/042551488911d189490000e829fbbd/frameset.htm] that tables are not passed by reference when you use RFC. It also explains the delta.
    When you make a remote function call, the system handles parameter transfer differently than it does with local calls.
    TABLES parameters
    The actual table is transferred, but not the table header. If a table parameter is not specified, an empty table is used in the called function.
    The RFC uses a delta managing mechanism to minimize network load during parameter and result passing. Internal ABAP tables can be used as parameters for function module calls. When a function module is called locally, a parameter tables is transferred u201Cby reference". This means that you do not have to create a new local copy. RFC does not support transfer u201Cby referenceu201D. Therefore, the entire table must be transferred back and forth between the RFC client and the RFC server. When the RFC server receives the table entries, it creates a local copy of the internal table. Then only delta information is returned to the RFC client. This information is not returned to the RFC client every time a table operation occurs, however; instead, all collected delta information is passed on at once when the function returns to the client.
    The first time a table is passed, it is given an object-ID and registered as a "virtual global table" in the calling system. This registration is kept alive as long as call-backs are possible between calling and called systems. Thus, if multiple call-backs occur, the change-log can be passed back and forth to update the local copy, but the table itself need only be copied once (the first time).

  • SSRS,MDX- Passed parameters are not hitting the main query in Dataset

    I have created a SSRS report which has to accept two parameters i.e., store name, Date(to show sales on particular date) in report. which are working fine for me. but, those passed parameters are not hitting the main query in main Dataset. what ever i
    pass in parameters, it is displaying all the rows(every city values). i think i am not correct in creating the statement in  Main dataset query, to receive those 2 parameters into the main query. can anybody please help me how to create the statement
    in main date set to display the results for the exact parameter i am passing(which has to be in MDX).
    ram

    Hi ramprasad74,
    According to your description, you want to use parameter in the report, then after parameter values are selected, corresponding data will be displayed in the report. But the parameters do not work and all the rows are displayed.
    To pass parameter to main report dataset, we need to define parameter for MDX query and assign parameter name same as SSRS report parameter. For detail information, please refer to the following steps:
    Create a Dataset to retrieve data for Store name parameter.
    Create Store name parameter, type name and prompt, set Date type to Text, check Allow multiple values check box, then select get values from the dataset.
    Create a Dataset for Date parameter.
    Create Date parameter, type name and prompt, set Date type to Date/Time, then select get values from the dataset.
    Create a new dataset used to retrieve data for the report, add statement like below to the mdx query: {STRTOMEMBER(@Date)} * {STRTOSET (@Store_name)}.
    In Query Designer pane, click Query Parameters and assign parameter name same as SSRS report parameter.
    For more information about SSRS Report with Single and Multi Selection Parameter using MDX Query, please refer to the following blog:
    http://www.codeproject.com/Articles/799265/SSRS-Report-with-Single-and-Multi-Selection-Parame
    If you have any more questions, please feel free to ask.
    Thanks,
    Wendy Fu
    If you have any feedback on our support, please click
    here.

  • BAPI_SHIPMENT_COST_ESTIMATE  What are the min. required parameters to pass

    Hi All,
       I would like to know what are the minimum required  parameters to pass in BAPI BAPI_SHIPMENT_COST_ESTIMATE. And from which tables I can pull out that information to pass to this BAPI.
    Does this BAPI creates a shipment cost document in the system or just shows the estimate of the shipment cost.
    If it creates a shipment cost document then its good for me. but if it shows us just the estimate does it shows estimate for each delivery (total Qty, Unit Price & Total Price). 
    What will be the item category it will pick. I like to see it picks  basic price related item category.
    Does any body has used this bapi ?
    Appreciate your fast reply.
    Regards,
    Leona

    Hello, I´ll try to answer your question:
    1. is it possible to run the bapi without actual shipment number and the shipment ( & cost ) will be created in simulation mode ?
    I think that the bapi only run with external shipment number and only run in simulation mode, that´s mean the bapi can not create any shipment and cost document, if you want to create a shipment use BAPI_SHIPMENT_CREATE, to create a cost document I don´t know if there is a bapi but you can create easily with transaction VI01 (batch-input)
    The shipment number that you use to call the bapi is a ficticious number always between external range indicated in field V_TVTK-NUMKE with the shipment type that you use.
    2. is it possible to perform estimation to inbound shipments ?
    Yes it´s depend on the shipment type. In standard system 0010 is used
    In the example that I have I use an inbound delivery
    3. does the bapi creates shipment and scd in simulate mode like transaction VICI ( from sales order ) ?
    I think that the bapi only run in simulation mode and it can not create any document
    4. is there any problem if i customized my scd item categories to open manualy ?
    I think that the bapi needs to work properly automatic iten categories
    can you please post sample code ( or any other doc's ) for this bapi ?
    I send you a document with an example if you give me an e-mail because I don´t know how to attach a word document
    Best regards,

  • Parameters are not Passed in a Struts(JPDK) Portlet

    Dear All,
    I am getting below problem in Oracle Portal Environment(10.1.2)
    I am passing news_id parameter along with title from one page to another page like below code
    In CompanyNewsShowPage.jsp
    <tr>
    <td class="desc">
    <%
    page_url ="/showpageNews.do?news_id="+com_events[0];
    // System.out.println("value of page url : "+ page_url);
    %>
    <input type="hidden" value="<%=page_url%>" id="hdnpageurl"/>
    <pdk-html:link page="<%=page_url%>" styleClass="desc">
    <%
    String obj_title= com_events[1];
    if((obj_title.length())>30)
    out.println(obj_title= obj_title.substring(0,15)+ "...");
    else
    out.println(com_events[1]);
    %>
    </pdk-html:link>
    </td>
    TO passing
    shownews.jsp
    The code for accepting parameter is below
    <%
    System.out.println("value of newsid :"+ newsid);
    String news_id=request.getParameter("news_id");
    if(news_id !=null)
    newsid= Integer.parseInt(news_id);
    System.out.println("value of newsid :"+ newsid);
    %>
    Kindly any one help me how to pass the parameter from one page to another page above problem, because our go live date is very close.
    But same code it is works in IE browser, but not working after deployed in Oracle Portal Environment.
    However, the
    parameters are not passed from the form to the Struts action. When retrieving the parameters, then
    a null value is retrieved, even when the parameter was specified in the form.
    Regards,
    Chandrashekhara
    Message was edited by:
    user487286
    Message was edited by:
    user487286

    Hi Anton,
    I make some tests and it appeared that it's only the output parameter which is not passed through the step (why ?).
    I get this output parameter by a post-running action which parse the joblog and retrieve the sequence number at the line with the pattern  "vendor" (hereunder) :
    100601 20091008 00 516 Job started  0       
    100601 20091008 00 550 Step 001 started (program ZCO_MANAGE_FILE, variant ECLO2, user ID ABAPUSER)  0 001 ZCO_MANAGE_FILE ECLO2 ABAPUSER   
    100601 20091008 00 001 No vendor specified  0 00233      
    100602 20091008 00 517 Job finished  0
    Here is the postrunning action script wich was working before we upgrade :
      JobFile log = jcsJob.getJobFileByName("log");
      if (log != null)
        com.redwood.scheduler.api.search.SearchResultSet myResultSet = log.search("No vendor specified");
        com.redwood.scheduler.api.search.SearchResult myResult = null;
        while (myResultSet.next())
          myResult = myResultSet.getSearchResult();
          String [] line = myResult.getLineText().split(" ");
          JobParameter jp = jcsJob.getJobParameterByName("VendorCode");
          if (jp != null)
            jp.setOutValueString(line[line.length-1]);

  • Import and export parameters of an FM are passed by value---why?

    Q]      By default the import and export parameters of an FM are passed by value---what is  the advantage of this system?

    Hi,
    Import and export parameters are, by default, passed by value. However, they can also be passed by reference. Tables parameters can only be passed by reference.
    Pass by reference means, passing the address itself rather than passing the value.
    I guess passing by value is easier and advantageous

  • Problem with empty report parameters when passed to PL/SQL function

    Hi,
    We have come across what appears to be a bug in the JRC. When passing a report parameter to a PL/SQL function as a parameter, empty parameters are changed before being sent to the function. More specifically, an empty string "" ends up as the value "(')" in the PL/SQL function parameter. In our report we print the report parameters on the first page so we know that the parameters are OK before being passed to the database.
    The problem exists for version 12.2.203, 12.2.204 and 12.2.205 of the JRC.
    We have identified a workaround, but it is not exactly elegant: Before executing the report we modify all empty  parameters ("") to " " . In the PL/SQL function, we trim all parameters before using them.
    We call the function using a command object with a sql syntax like this example:
    select * from table (qa_batch_release.get_qa_br('{?p_report_id}','{?p_reg_set_number}','{?p_cr_number}','{?p_change_id_decode}','{?p_country_id}','{?p_mfg_item_no}','{?p_4_no}','{?p_5_no}','{?p_7_no}'))
    The PL/SQL function is a table returning function.
    Best regards, Thor

    Hi Kishore,
    using #COLUMN_VALUE# would probably not make much sense, because normally a report has multiple columns and not just the numeric column which you want to verify if it's negative. But APEX will fire the template condition for each column, because the report template is a column cell template.
    What you can do to make it more generic is to use for example
    #CHECK_AMOUNT#
    in the template and provide a not displayed column in your SQL statement which contains your value which is named CHECK_AMOUNT. For example:
    SELECT NAME
         , BALANCE
         , BALANCE AS CHECK_AMOUNT
    FROM XXX;Because this CHECK_AMOUNT column would be a generic name, you can use this template in all your reports as long as you provide this column.
    Thope that helps
    Patrick

  • RFC Function Module - Message Reference parameters are not allowed with RFC

    Hi,
    I’ve checked the Remote-Enabled Module radio button, declared Import and Export parameters using ‘Type’ typing and checked the ‘Pass Value’ in export and import parameters but I still receive message ‘Reference parameters are not allowed with RFC’ and not able to activate the function module.
    Am I missing something?
    Regards,
    ...Naddy

    Hi all,
                   I faced the same problem and solved it ,
    You have defined a reference parameter for a remotely called
      function module. However, only value parameters are allowed
      for this type of module.
      Procedure
      Change the reference parameter to a value parameter.
    Guys  pls .don't leave the thread un-asnwered when you solved problem , post the solution it might be useful for others also.
    Regards
    Krishna Acharya

  • SOAP - PI- R/3 RFC  Scenario RFC parameters are not comming

    Hi Experts,
    I created one scenario as SOAP ->PI 7.1 -> R/3 RFC call.
    When I am testing this scenario Backend RFC is getting called but somehow RFC parameters are coming as blank. In XSMB_MONI it is creating two messages as successful one with correct payload.  But when I put debug code at the start of RFC , it is going to the debug code  and input parameter values are showing as empty.  Please tell me where can I check?
    Thanks,
    Siva Rama

    Hi Siva,
    Please check in the SXMB_MONI of the receiver SAP System.
    If the parameters are getting populated here then it must be passed to the RFC.
    Make sure you have imported the RFC from the receiver system itself.
    regards,
    Piyush

  • The page parameters are not showing in the URL .

    I my appliaction all the pages have textboxes with some values . But the URL for none of the page shows the parameters like every page has url :
    http://127.0.0.1:8080/apex/f?p=105:8:598450314306501::NO:::
    but none of the page parameters are being shown . What is the problem here
    please help

    You can setup a page branch that responds to your specific button and within that branch definition you can specify page items and values to be set when that branch fires.
    Is there a specific reason that you want the values passed on the URL? That's not really required to make ApEx function properly.
    Earl

  • Crystal Report "some parameters are missing values" while exporting/printin

    I am able to pass parameters from a JSP to a crystal report through CrystalReportViewer and view the report. (I tried doing it using the code provided on this help forum. I was getting a message: "Some Parameters are missing values". I had to add 1 line: pfield1.setReportName(""); for every parameter field. And It worked..)
    Now I can see the "Print" and "Export" buttons. But when I try to print or export the report, I get the same message "Some Parameters are missing values".

    see posting "parameter driven export to excel" on April 26th

  • Some parameters are missing values

    I am trying to invoke a crystal report using JRC API. I am using Business Objects XI.
    When I try to invoke the report after setting all parameters I am getting an error message "Some parameters are missing values ". Here is how my JSP code looks like
    ReportClientDocument oReportClientDocument = new ReportClientDocument();
    oReportClientDocument.open(reportName, 0);
    CrystalReportViewer oCrystalReportViewer = new CrystalReportViewer();
    //set the reportsource property of the viewer
    oCrystalReportViewer.setReportSource(reportSource);
    //set viewer attributes
    oCrystalReportViewer.setOwnPage(true);
    oCrystalReportViewer.setOwnForm(true);
    //set the CrystalReportViewer print mode
    oCrystalReportViewer.setPrintMode(CrPrintMode.ACTIVEX);
    //refresh the CrystalReportViewer if necessary (only required once)
    if (session.getAttribute("refreshed") == null)
    oCrystalReportViewer.refresh();
    session.setAttribute("refreshed", "true");
    String userid="emagia";
    String password="emagia";
    String rptuserid="tjordan";
    String fromdate="07/01/2008";
    String todate="07/12/2008";
    ConnectionInfo ci = new ConnectionInfo();
    ci.setUserName(userid);
    ci.setPassword(password);
    ConnectionInfos connections = new ConnectionInfos();
    connections.add(ci);
    oCrystalReportViewer.setEnableLogonPrompt(false);
    oCrystalReportViewer.setDatabaseLogonInfos(connections);
    ParameterFieldDiscreteValue val1 = new ParameterFieldDiscreteValue();
    val1.setValue(rptuserid);
    Values vals1 = new Values();
    vals1.add(val1);
    ParameterField param1 = new ParameterField();
    param1.setName("User Id");
    param1.setReportName("");
    param1.setCurrentValues(vals1);
    Fields fields = new Fields();
    fields.add(param1);
    ParameterFieldDiscreteValue val2 = new ParameterFieldDiscreteValue();
    val2.setValue(fromdate);
    Values vals2 = new Values();
    vals2.add(val2);
    ParameterField param2 = new ParameterField();
    param2.setName("Date Range from");
    param2.setReportName("");
    param2.setCurrentValues(vals2);
    fields.add(param2);
    ParameterFieldDiscreteValue val3 = new ParameterFieldDiscreteValue();
    val3.setValue(todate);
    Values vals3 = new Values();
    vals3.add(val3);
    ParameterField param3 = new ParameterField();
    param3.setName("Date Range To");
    param3.setReportName("");
    param3.setCurrentValues(vals3);
    fields.add(param3);
    oCrystalReportViewer.setEnableParameterPrompt(false);
    oCrystalReportViewer.setParameterFields(fields);
    oCrystalReportViewer.processHttpRequest(request, response,getServletConfig().getServletContext(), null);
    oCrystalReportViewer.dispose();
    In the Tomcat log this is what I get
    - JRCAgent3 received request: refreshData
    - JRCAgent3 attempting to acquire license
    - JRCAgent3 successfully acquired license
    - JRCAgent3 releasing license
    - JRCAgent3 received request: getPromptConnInfos
    - JRCAgent3 received request: compoundRequest
    - JRCAgent3 received request: setSQLLogonInfoRequest
    - JRCAgent3 received request: setSQLLogonInfoRequest
    - JRCAgent3 received request: fetchReportPageRequest
    - JRCAgent3 attempting to acquire license
    - JRCAgent3 successfully acquired license
    - Logon: Connecting to database using local JNDI server ...
    - Connection Opened null
    - Connection opened (Connection:  databaseType=JDBC  serverName=reports_dsn.dsn  state=open  databaseDriverName=crdb_odbc.dll).
    - Report parameters is not valid
    - Report parameters is changed
    - Handling report parameters changes
    - Validating report parameters
    - com.crystaldecisions.reports.dataengine.l: Some parameters are missing values
    - The report requires parameter values that need to be supplied by the client before further processing
    com.crystaldecisions.reports.dataengine.l: Some parameters are missing values
         at com.crystaldecisions.reports.dataengine.j.a(Unknown Source)
         at com.crystaldecisions.reports.dataengine.a9.a(Unknown Source)
    Can anybody tell me why I am getting this error??
    Any help will be appreciated.

    The problem may be that you are setting your report date parameters as a string when you pass the value to the report.   If the JRC does not recognize the parameter value as the correct type, it will throw the error you see when trying to pass them to the report.
    If they are a date type or a date time type in the report, they must be set as such using the Java Calendar object.
    Below is an example of how one would pass a date parameter to a report:
    //DATE VALUE PARAMETER.
         Calendar calendar = Calendar.getInstance();
         calendar.clear();
         calendar.set(2004, 1, 17);
         Date dateParamVal = calendar.getTime();     
         pfieldDate.setName("dateParam");
         pfieldDVDate.setValue(dateParamVal);
         //Add the parameter field values to the Values collection object.
         vals5.add(pfieldDVDate);
         //Set the current Values collection for each parameter field.
         pfieldDate.setCurrentValues(vals5);
         //Add each parameter field to the Fields collection.
         //The Fields object is now ready to be used with the viewer.
         parameterFields.add(pfieldDate);
         //DATE-TIME VALUE PARAMETER.
         Calendar calendar2 = Calendar.getInstance();
         calendar2.clear();
         calendar2.set(2002, 5, 12, 8, 23, 15);
         Date dateTimeParamVal = calendar2.getTime();
         pfieldDateTime.setName("dateTimeParam");
         pfieldDVDateTime.setValue(dateTimeParamVal);
         //Add the parameter field values to the Values collection object.
         vals6.add(pfieldDVDateTime);
         //Set the current Values collection for each parameter field.
         pfieldDateTime.setCurrentValues(vals6);
         //Add each parameter field to the Fields collection.
         //The Fields object is now ready to be used with the viewer.
         parameterFields.add(pfieldDateTime);
         //TIME VALUE PARAMETER.
         Calendar calendar3 = Calendar.getInstance();
         calendar3.clear();
         calendar3.set(2002, 5, 12, 13, 44, 59);
         Date timeParamVal = calendar3.getTime();     
         pfieldTime.setName("timeParam");
         pfieldDVTime.setValue(timeParamVal);
         //Add the parameter field values to the Values collection object.
         vals7.add(pfieldDVTime);
         //Set the current Values collection for each parameter field.
         pfieldTime.setCurrentValues(vals7);
         //Add each parameter field to the Fields collection.
         //The Fields object is now ready to be used with the viewer.
         parameterFields.add(pfieldTime);
    Edited by: Merry Enns on Aug 5, 2008 8:11 PM

  • New in NW04s: FL069 TABLES parameters are obsolete (in function modules)

    Can somebody explain what is the fundamental reason for this behaviour in NW04s?
    In Netweaver 2004s system (like ERP2005 ) you get a warning message in SE37:
    FL069 TABLES parameters are obsolete! when defining quite ordinary tables parameter using LIKE and reference to a structure in ddic.
    I now speak normal function modules, not RFC enabled.
    This example of tables parameter definition will cause the warning message:
    return LIKE BAPIRET2
    I of course looked the additional help provided by this message FL069. I understood it as following:
    you should stop using TABLES parameter and more often use CHANGING parameter by referring a TABLE TYPE defined in dictionary.
    if using CHANGING parameter and still want to pass the header line of your internal table you should use a separate parameter (EXPORT or CHANGING parameter)
    Developers have too much used TABLES parameters for passing internal tables for reading (by value) rather than to be modified (by reference). As a consequence, fm could have change the header line without caller to know it.
    in my opinion the message help is missleadingly telling that header line is no longer passed to function module if TABLES parameter is used. I made a small test program and fm (with TABLES paramerer), and everything worked as before.
    The warning message can be ignored by pressing Enter a few times and your fm with TABLES parameter works as it had in older versions of Netweaver.
    SAP is still using a lot of TABLES parameters in their own function modules. For example SD_SALES_HEADER_MAINTAIN.
    So what is the point of this warning message while everything still works as it used to be and SAP uses this same "OBSOLETE" feature itself? Is there anything more fundamental behind this message? Like TABLES paremeters will no longer work in future versions of ABAP (or header line passing will be ignored in future versions) and therefore developers should switch to CHANGING/EXPORT parameters with TABLE TYPES as soon as possible??
    Please understand that I don't need any assistance how to avoid this message, just interested to share your opinions what is the purpose of this warning message.
    That is why I did not marked this thread as a question.
    Br: Kimmo

    Hello,
    This is the view under Tables tab in my function builder:
    I_T_SELECT     TYPE     SRSC_S_IF_SIMPLE-T_SELECT
    I_T_FIELDS     TYPE     SRSC_S_IF_SIMPLE-T_FIELDS
    E_T_DATA     LIKE     SFLIGHT (which I change to YBWxxxx)
    The moment I change to YBWxxxxx it gives me that error '"TABLES parameters are obsolete! "'
    and unfortunately hitting enter several times is not helping  either
    Thanks!

  • BIP report parameters are comming in given sequance.

    Hi..
    I have report in which i m passing two parameters.
    <?param@begin:fromdate?>
    <?param@begin:todate?>
    While taking report these parameters are not coming in given sequance means i want first para as Fromdate then todate, but every time todate is get displyed first.
    I tried by chaging sequace also but the same thing i m getting.

    I had to modify slightly the logic in your RTF template and add some values in your XML sample data for this to test.
    It is working as expected.
    regards
    Jorge
    p.s If you consider your original question answered then please grant the points and close the thread

Maybe you are looking for

  • Lock Box Reason Code.

    Hi Experts, I am getting one issue in lock box, If Suppose customer has invoice of $ 1000, he is eligible for discount of $ 50 so he should pay net amount $ 950. But customer is paying full amount without knowing that he is eligible for discount i.e

  • How to connect e66 to pc

    i have a small office with small network LAN (wired) as well as wlan router. i want to acces my computer data using wlan on network with my e66 . can it be possible if yes than how.

  • 2 way restriction of select lists

    Hello all, I have a requirement in my application in which I need to restrict the select lists in both ways unlike the cascading select lists. I have Select lists for Department and Application. If a user selects Department first, I need to restrict

  • Chrome extension claims does not have latest ver of Acrobat despite CC

    Trying to use the Adobe Acrobat - Create PDF Chrome extension on up-to-date Yosemite with CreativeCloud - extension gives "Unknown Error" and claims computer doesn't have the 'right' version of Acrobat: "A supported version of Acrobat could not be fo

  • All Folders and Sub Folders aren't Adding to Library

    When I added my songs located on an external hard drive via the "add folder to library" option, I selected a root folder and let itunes add all of the folders and music located inside. The problem is that itunes did not detect all of the folders. Alo