Port creation error

hi..
while creating parner profile i am getting this error
<b>
port could not be created
RFc destination MLS_100 not specified for system mls_100
enter the rfc destination and restart the genartaion</b>
Please hel pme to solve this error..
regards
kumar

hi
Check out whether you assigned logical systems to your clients.Next check the ports(for inbound and outbound) also in we20..
Go through these documents for the settings that need to be done.
http://www.sappro.com/downloads/OneClientDistribution.pdf
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.

Similar Messages

  • Logical port creation error through SOAMANAGER

    Hi,
    When I try to create a logical port through SOAMANAGER I got the following error.
    Error: Uninstantiated object "subject sidl service" in method IF_SRT_WSP_CONFIG_SIDL~CREATE_CLNT_CFG_FROM_WSDL_D of class CL_SRT_WSP_CONFIG_SIDL
    When I actually look into the class CL_SRT_WSP_CONFIG_SIDL I could'nt find the method CREATE_CLNT_CFG_FROM_WSDL_D in SAP 720 version.
    I had seen some discussions in the forum on this error but I could'nt find a proper solution.
    Can someone explain me on how to resolve this issue.
    Do I need to apply a oss note ? Is it mandatory. Also in one thread they talked of SICF transaction usage which is also not clear. Is there any other way.
    Thanks,
    Shashi

    Sorry - I should have been more clear earlier.
    I am using SOAMANAGER to create the logical port.  The error occurs when I choose 'WSDL Access Settings' to obtain the WSDL.  I was able to get around the problem by going into SOAMANAGER on my provider system, locating the service & binding I want, and then downloading that file.  This is a workaround as I would like to get the file via HTTP access.
    I suspect this has to do with configuration but I do not know where this needs to be setup.

  • INFA 9.0.1 Domain creation error [Port number already in use]

    Hi Experts,
    I've installed INFA 9.0.1 HF2 recently on my Linux 64bit box and due to some configuration issue, I endup in uninstalling the same and deleted the complete installation folder.
    Now I'm trying fresh INFA 9.0.1 HF2 install on the same Linux box, but getting the following port number error while creating domain.
    "Node port number. This port is in use. Select another port number"
    I tried with another port number also but all went in vain.
    Anybody faced this situation before? Please help me to resolve this issue.
    Regards,
    Ram Sankar

    Actually I'm new to Linux environment.. so I'm not sure on remove/killing the port number which are already in use. Hence I tried with different port number, but I'm getting popup like below,
    "The Command to create the domain failed
    Select Ok to correct the domain information and try the command again.
    Select Continue to continue the installation without creating the domain.
    you can run the command again to create a domain after the installation."
    I'm not sure whether we can create a domain successfully after the installation.
    Please anybody help me to remove/kill the existing port number (6005) which I was using it before. so that I can use the same to create a domain during installation only.
    I appreciate your help in this regard.
    Thanks

  • WSDL version used for port creation in SOAMANAGER for Netweaver 7.01 SP-5.

    Hi,
    Does SOAMANAGER refer to a particular version of WSDL while creating the logical ports for consumer proxies. I'm asking this because after one of the upgrades in our ECC system we find that the authentication configurations of the port are automatically done based on the WSDL now, however this was not the case earlier.
    Also logical ports created manually are giving runtime exception (Soap FAult Code : 1). Does logical ports creation necessarily have to be done from WSDL.
    Please throw some light on the above, if any of you have faced this issue already.
    Regards,
    Avishek.

    We got a reply from SAP that from NetWeaver 7.0 SP3, logical ports will be created based on Security policy mentioned in WSDL. We can however override this by creating the port manually and the SOAP fault code error can be resolved by manually entering the SOAP Action for each method of the Service in the 'Operation Specific' tab of the Logical Port details.

  • Download Helper, even with paid converter upgrade, gives "Invalid Capture File" errors and will not record audio, with "File Creation Error - Unable to rename/copy audio file" Error.

    Download Helper Screen Capture worked to capture video if the default "no audio" option is active. But, no audio. The "speakers" or "microphone" audio options are confusing....the audio to be captured is from the video, so what do you choose? With either "speakers" or "microphone" selected, the captured file has poor audio and no video. Re-capture efforts (speakers) get "Invalid capture file error" and "File Creation error- Unable to rename/copy audio file"
    The paid upgrade of "Converter" doesn't work.
    Instructive documentation - not very good.
    Suggestions - Need time delay between initiation of "Record" and starting the video to be recorded.
    Could use timer tracking of the record process.
    Are there operating system limitations? (Have Windows XP Pro)

    That is an issue for the developer of that Download Helper.

  • Phone number ported in error; can't access e-mails

    I bought a new cell phone and requested that my cell number be ported.  Instead of porting the cell number, our Verizon land line was ported in error.  Shortly thereafter, our account was canceled, and our access to Verizon e-mail was terminated.  Numerous calls to Verizon have been in vain.  Any suggestions on how I can impress the importance of getting our e-mail account returned to us?  My wife still has her Verizon cell phone, and Verizon has told me that they will re-port the number back to our home later this week.  Will our e-mail accounts return?

    Hi and welcome to the forums!
    I would suggest you run a diagnostics test. This will register your device and create a report that can be sent to your vendor.
    Thanks,
    Bifocals
    User Guide for your device
    Diagnostic reports
    About diagnostic reports
    Diagnostic reports provide wireless configuration and connection information for your BlackBerry® device. If you cannot connect to the wireless
    network or access services such as email messaging, your wireless service provider or administrator might ask you to run and submit a diagnostic
    report. Your wireless service provider or administrator can use the report to help you troubleshoot the problem.
    Run a diagnostic report
    If you cannot connect to the wireless network or access services such as email messaging, your wireless service provider or administrator might
    ask you to run and submit a diagnostic report. Your wireless service provider or administrator can use the report to help you troubleshoot the
    issue.
    1. On the Home screen or in a folder, click the Options icon.
    2. Click Mobile Network.
    3. Press the Menu key.
    4. Click Diagnostics Test.
    5. Press the Menu key.
    6. Click Run.
    View a diagnostic report
    1. On the Home screen or in a folder, click the Options icon.
    2. Click Mobile Network.
    3. Press the Menu key.
    4. Click Diagnostics Test.
    5. Highlight a report.
    6. Press the Menu key.
    7. Click View Report.
    Submit a diagnostic report
    1. On the Home screen or in a folder, click the Options icon.
    2. Click Mobile Network.
    3. Press the Menu key.
    4. Click Diagnostics Test.
    5. Highlight a report.
    6. Press the Menu key.
    7. Click Email Report or PIN Report.
    Click Accept as Solution for posts that have solved your issue(s)!
    Be sure to click Like! for those who have helped you.
    Install BlackBerry Protect it's a free application designed to help find your lost BlackBerry smartphone, and keep the information on it secure.

  • Port overrun error while reading data in queue

    I am trying to read data from various wireless sensors(5-6 in number)  which are communicating with my PC using rs232 port.
    the size of data from each sensor that i am getting is 39 bytes.
    I want to extract some bytes of these data for which i am using a string subset function.
    Now the issue is due to the high baud rate i am not able to read data from each of them individually because before one set of data is worked on another set arrives and port overrun error occurs.
    I am trying to do this using queue but could not find a possible solution.

    This shouldn't be a difficult problem, as serial communication is "slow" (compared to the speed of the CPU).  You want to take advantage of LabVIEW's parallel nature and have each of your Serial devices running in parallel, taking 39 bytes of data and passing it to an "Extract useful information" subVI.  Note that you can use the same subVI for each of the 6 lines, and the time it takes to "extract the useful information" (by doing some string parsing) should take no more than a few microseconds, so it can easily be "shared" by all of your serial devices.  Alternatively, you could make this VI reentrant, so a separate and independent copy would be assigned to each device, again allowing parallel operation.
    If you are still having problems, post some code.

  • What is "Missing Port Information" error?

    Setting FINEST log level on JAXRPC in the AS8 2004Q04 Beta reveals nothing.
    Searches on this forum provides only 3 matches for "Missing port information" (this one makes 4). In http://forum.java.sun.com/thread.jsp?forum=136&thread=508958 the same problem that I have is described, and the problem is left unresolved, despite a plea from a second user. ( I wonder what happened to these people...Did they sell short or become .NET developers. Neither are an answer for me. )
    Searches in the bug parade shows that this error is generic: In 6157880, classpath was not set correctly. In 4859401, service used a J2SE 1.4 API in a 1.3 environment. In 4802443 there is a getter for a public field and so jaxrcp was confused. There are more bugs matching but I'm not listing them all here. My point is that there doesn't seem to be a single root cause for this problem.
    So, logs don't help, forum doesn't have answer, bug parade is too noisy. This problem seems unresolved here on Sun's web pages, but here I try again:
    Here are some questions:
    1) What is "port information"?
    2) From where is it missing? Where does AS8 expect to find it?
    3) Anyone have a strategy on how to debug this?
    I have Axis TCPMON tracing the soap messages and can verify that AS8 originates the error, not the client. The limited information from the server log verifies this too:
    [#|2004-11-01T16:28:20.008-0500|SEVERE|sun-appserver-pe8.1|javax.enterprise.resource.webservices.rpc.server.http|_Thre
    adID=11;|JAXRPCSERVLET22: no endpoint specified|#]Here is the output of a client that dumps the exception:
         [java] Endpoint address = http://Stratocaster:8080/ym/ym-alias
         [java] javax.xml.rpc.soap.SOAPFaultException: JAXRPCSERVLET28: Missing port information
         [java]     at com.sun.xml.rpc.client.StreamingSender._raiseFault(StreamingSender.java:515)
         [java]     at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:294)
         [java]     at svcp.XXXAPIR0501_Stub.create2(XXXAPIR0501_Stub.java:282)
         [java]     at SubClient.main(SubClient.java:31)

    I believe I've gotten to the bottom of this error and will report it here in case there is anyone that is also having this problem and in case there is anyone that can make sense of it.
    The alias and endpoint fields must be equal.
    The deploy tool allows you to enter an alias and an endpoint for your web service. I'll show you the user interface specifics below. The data you enter in these fields show up in the wsdl, the web.xml and the sun-web.xml, and I'll show what elements below.
    Except for the preceding '/' in the alias field (the '/' is inserted by deploytool), the alias and the endpoint string must be identical: if '/imp-alias' is the alias value, the endpoint must be 'imp-alias'.
    If they are not equal and your client uses the alias value in endpoint address, you will get "Missing port information" error.
    If they are not equal and your client uses the endpoint value in endpoint address, you will get '404 Not Found' error.
    For example, lets say I set alias to 'api-alias' and endpoint to 'api-endpoint'. Using my browser, I can get the wsdl with http://localhost:8080/context/api-alias?wsdl (where context is also a value set in deploytool gui). The returned wsdl will show that the soap:adress location attribute is: http://localhost:8080/context/api-endpoint. If your client uses the wsdl to generate stubs, the default endpoint is this location and your client will get the '404 Not Found' error. If you client provides an endpoint address by setting the ENDPOINT_ADDRESS_PROPERTY to http://localhost:8080/context/api-alias, your client will get the "Missing port information" error.
    You get to the alias and endpoint fields in deploytool from the File panel on the left. Open the subfolder that represents your war file. There will be your web service. Select the web service and the main panel will change to contain about 4-6 tabs. One tab labelled Aliases another tab labelled Endpoint.
    The alias field shows up in the web.xml file like this:
    <servlet-name>APIImpl</servlet-name>
    <url-pattern>/api-alias</url-pattern>
    </servlet-mapping>The endpoint field show up in the web.xml file under the same servlet-mapping element as alias:
    <servlet-name>APIImpl</servlet-name>
    <url-pattern>/api-endpoint/__container$publishing$subctx/*</url-pattern>
    </servlet-mapping>The endpoint field shows up in the wsdl in the soap:address element's 'location' attribute:
          <soap:address location="http://localhost:8080/context/api-endpoint" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"/>The endpoint field shows up in the sun-web.xml file
    <endpoint-address-uri>api-endpoint</endpoint-address-uri>John

  • Service Contracts Billing Schedule Creation Error

    Hi,
    I have a requirement of creating service contracts from back-end for which I am using the oks_contracts_pub.create_contract_header, create_service_line, and create_bill_schedule. I am creating my contracts with active status and renewal type of EVN (Header level), FUL(Line Level). My contract is of type subscription. The contract header and line are creating fine but the Bill schedule API is throwing an UNEXPECTED ERROR. The billing schedules need to be created based on accounting rule which can be quarterly or monthly. I have included the bill schedule code (hard coded values) for review. Any help is greatly appreciated.
    Also the version I am working on is R12
    ________________________________________________CODE___________________________________________________________________
    CREATE OR REPLACE PROCEDURE BILLING_SCHEDULE AS
    l_strm_level_tbl OKS_BILL_SCH.STREAMLVL_TBL;
    v_bill_qtrs NUMBER := 0;
    v_bill_mths NUMBER := 0;
    v_bill_days NUMBER := 0;
    v_net_amount NUMBER := 468;
    v_acct_rule_name VARCHAR2(50) := 'QUARTERLY';
    v_amt_per_day NUMBER;
    x_error_locator VARCHAR2(2000);
    v_start_date DATE := '04-MAY-2010';
    v_end_date DATE := '25-MAY-2010';
    x_return_status VARCHAr2(3);
    x_msg_count NUMBER;
    x_msg_data VARCHAR2(2000);
    v_billing_sequence NUMBER;
    x_chr_id NUMBER := 17000;
    x_line_id NUMBER := 223248604345353294444923586786456728480;
    g_day_uom VARCHAR2(10) := 'DAY';
    g_month_uom VARCHAR2(10) := 'MTH';
    g_quarter_uom VARCHAR2(10) := 'QTR';
    v_amt NUMBER;
    v_invoicing_rule_id NUMBER := -2;
    BEGIN
    --Create Billing Schedule based on accounting rule
    okc_context.set_okc_org_context;
    MO_GLOBAL.INIT('OKS');
    MO_GLOBAL.SET_POLICY_CONTEXT('S', 83);
    v_bill_qtrs := 0;
    v_bill_days := 0;
    v_bill_mths := 0;
    SELECT NVL(v_net_amount, 0)/(v_end_date - v_start_date)
    INTO v_amt_per_day
    FROM dual;
    dbms_output.put_line('Calculated amt per day ' || v_amt_per_day);
    IF v_acct_rule_name LIKE '%QUARTERLY%' THEN
    --Quarterly billing schedule
    SELECT FLOOR(MONTHS_BETWEEN( v_end_date,
    v_start_date)/3),
    v_end_date - ADD_MONTHS(v_start_date, (FLOOR(MONTHS_BETWEEN(v_end_date, v_start_date)/3)*3))
    INTO v_bill_qtrs,
    v_bill_days
    FROM dual;
    dbms_output.put_line('Calculated the qtrs and days');
    IF v_bill_qtrs > 0 THEN
    SELECT (ADD_MONTHS(v_start_date, (FLOOR(MONTHS_BETWEEN(v_end_date, v_start_date)/3)*3)) - v_start_date)*v_amt_per_day
    INTO v_amt
    FROM dual;
    dbms_output.put_line('Calculated qtr amt');
    SELECT NVL(MAX(sequence_no), 0) + 1
    INTO v_billing_sequence
    FROM oks_stream_levels_b
    WHERE dnz_chr_id = x_chr_id
    AND cle_id = x_line_id;
    --Populating the stream line variables
    l_strm_level_tbl(v_billing_sequence).sequence_no := v_billing_sequence;
    l_strm_level_tbl(v_billing_sequence).dnz_chr_id := x_chr_id;
    -- l_strm_level_tbl(v_billing_sequence).id := x_line_id;
    l_strm_level_tbl(v_billing_sequence).cle_id := x_line_id;
    l_strm_level_tbl(v_billing_sequence).uom_code := g_quarter_uom;
    l_strm_level_tbl(v_billing_sequence).uom_per_period := 1;
    l_strm_level_tbl(v_billing_sequence).level_periods := v_bill_qtrs;
    l_strm_level_tbl(v_billing_sequence).start_date := v_start_date;
    l_strm_level_tbl(v_billing_sequence).end_date := v_end_date;
    l_strm_level_tbl(v_billing_sequence).invoice_offset_days := NULL;
    l_strm_level_tbl(v_billing_sequence).amount := v_amt/v_bill_qtrs;
    l_strm_level_tbl(v_billing_sequence).level_amount := v_amt/v_bill_qtrs;
    l_strm_level_tbl(v_billing_sequence).lines_detailed_yn := 'Y';
    l_strm_level_tbl(v_billing_sequence).due_arr_yn := 'Y';
    dbms_output.put_line('Before calling the Bill Sch API for QTR');
    OKS_CONTRACTS_PUB.CREATE_BILL_SCHEDULE ( p_billing_sch=>'E',
    p_strm_level_tbl=>l_strm_level_tbl,
    p_invoice_rule_id=>v_invoicing_rule_id,
    x_return_status=>x_return_status);
    dbms_output.put_line('After calling the Bill Sch API for QTR');
    IF x_return_status <> 'S' THEN
    x_msg_count := 1;
    dbms_output.put_line('Quarterly schedule creation error ' || x_msg_data);
    ---DBMS_TRANSACTION.ROLLBACK_SAVEPOINT('OKS_A');
    -- RETURN;
    END IF;
    END IF;
    IF v_bill_days > 0 THEN
    SELECT NVL(MAX(sequence_no), 0) + 1
    INTO v_billing_sequence
    FROM oks_stream_levels_b
    WHERE dnz_chr_id = x_chr_id
    AND cle_id = x_line_id;
    dbms_output.put_line('sequence '||v_billing_sequence);
    --Populating the stream line variables
    l_strm_level_tbl(v_billing_sequence).sequence_no := v_billing_sequence;
    l_strm_level_tbl(v_billing_sequence).dnz_chr_id := x_chr_id;
    --l_strm_level_tbl(v_billing_sequence).id := x_line_id;
    l_strm_level_tbl(v_billing_sequence).cle_id := x_line_id;
    l_strm_level_tbl(v_billing_sequence).uom_code := g_day_uom;
    l_strm_level_tbl(v_billing_sequence).uom_per_period := v_bill_days;
    l_strm_level_tbl(v_billing_sequence).level_periods := 1;
    l_strm_level_tbl(v_billing_sequence).start_date := v_start_date;
    l_strm_level_tbl(v_billing_sequence).end_date := v_end_date;
    l_strm_level_tbl(v_billing_sequence).invoice_offset_days := NULL;
    l_strm_level_tbl(v_billing_sequence).amount := v_net_amount;--v_amt_per_day*v_bill_days;
    l_strm_level_tbl(v_billing_sequence).level_amount := v_net_amount;--v_amt_per_day*v_bill_days;
    l_strm_level_tbl(v_billing_sequence).lines_detailed_yn := 'Y';
    l_strm_level_tbl(v_billing_sequence).due_arr_yn := 'Y';
    dbms_output.put_line('Before calling the Bill Sch API for QTR days');
    OKS_CONTRACTS_PUB.CREATE_BILL_SCHEDULE ( p_billing_sch=>'E',
    p_strm_level_tbl=>l_strm_level_tbl,
    p_invoice_rule_id=>v_invoicing_rule_id,
    x_return_status=>x_return_status);
    dbms_output.put_line('After calling the Bill Sch API for QTR days ' || v_bill_days || ' ' || x_return_status);
    IF x_return_status <> 'S' THEN
    x_msg_count := 1;
    dbms_output.put_line('Day schedule, for quarterly accounting rule, creation error ' || x_msg_data);
    --DBMS_TRANSACTION.ROLLBACK_SAVEPOINT('OKS_A');
    --RETURN;
    END IF;
    END IF;
    ELSE
    --Monthly billing schedule
    SELECT FLOOR(MONTHS_BETWEEN( v_end_date,
    v_start_date)),
    v_end_date - ADD_MONTHS(v_start_date, FLOOR(MONTHS_BETWEEN(v_end_date, v_start_date)))
    INTO v_bill_mths,
    v_bill_days
    FROM dual;
    dbms_output.put_line('Calculated the mths and days');
    IF v_bill_mths > 0 THEN
    SELECT (ADD_MONTHS(v_start_date,FLOOR(MONTHS_BETWEEN(v_end_date, v_start_date))) - v_start_date)*v_amt_per_day
    INTO v_amt
    FROM dual;
    dbms_output.put_line('Calculated the mths amt');
    SELECT NVL(MAX(sequence_no), 0) + 1
    INTO v_billing_sequence
    FROM oks_stream_levels_b
    WHERE dnz_chr_id = x_chr_id
    AND cle_id = x_line_id;
    --Populating the stream line variables
    l_strm_level_tbl(v_billing_sequence).sequence_no := v_billing_sequence;
    l_strm_level_tbl(v_billing_sequence).dnz_chr_id := x_chr_id;
    --l_strm_level_tbl(v_billing_sequence).id := x_line_id;
    l_strm_level_tbl(v_billing_sequence).cle_id := x_line_id;
    l_strm_level_tbl(v_billing_sequence).uom_code := g_month_uom;
    l_strm_level_tbl(v_billing_sequence).uom_per_period := 1;
    l_strm_level_tbl(v_billing_sequence).level_periods := v_bill_mths;
    l_strm_level_tbl(v_billing_sequence).start_date := v_start_date;
    l_strm_level_tbl(v_billing_sequence).end_date := v_end_date;
    l_strm_level_tbl(v_billing_sequence).invoice_offset_days := NULL;
    l_strm_level_tbl(v_billing_sequence).amount := v_amt/v_bill_mths;
    l_strm_level_tbl(v_billing_sequence).level_amount := v_amt/v_bill_mths;
    l_strm_level_tbl(v_billing_sequence).lines_detailed_yn := 'Y';
    l_strm_level_tbl(v_billing_sequence).due_arr_yn := 'Y';
    dbms_output.put_line('Before calling the Bill Sch API for MTHS');
    OKS_CONTRACTS_PUB.CREATE_BILL_SCHEDULE ( p_billing_sch=>'E',
    p_strm_level_tbl=>l_strm_level_tbl,
    p_invoice_rule_id=>v_invoicing_rule_id,
    x_return_status=>x_return_status);
    dbms_output.put_line('After calling the Bill Sch API for MTHS');
    IF x_return_status <> 'S' THEN
    x_msg_count := 1;
    dbms_output.put_line('Monthly schedule creation error ' || x_msg_data);
    --DBMS_TRANSACTION.ROLLBACK_SAVEPOINT('OKS_A');
    --RETURN;
    END IF;
    END IF;
    IF v_bill_days > 0 THEN
    SELECT NVL(MAX(sequence_no), 0) + 1
    INTO v_billing_sequence
    FROM oks_stream_levels_b
    WHERE dnz_chr_id = x_chr_id
    AND cle_id = x_line_id;
    --Populating the stream line variables
    l_strm_level_tbl(v_billing_sequence).sequence_no := v_billing_sequence;
    l_strm_level_tbl(v_billing_sequence).dnz_chr_id := x_chr_id;
    --l_strm_level_tbl(v_billing_sequence).id := x_line_id;
    l_strm_level_tbl(v_billing_sequence).cle_id := x_line_id;
    l_strm_level_tbl(v_billing_sequence).uom_code := g_day_uom;
    l_strm_level_tbl(v_billing_sequence).uom_per_period := v_bill_days;
    l_strm_level_tbl(v_billing_sequence).level_periods := 1;
    l_strm_level_tbl(v_billing_sequence).start_date := v_start_date;
    l_strm_level_tbl(v_billing_sequence).end_date := v_end_date;
    l_strm_level_tbl(v_billing_sequence).invoice_offset_days := NULL;
    l_strm_level_tbl(v_billing_sequence).amount := v_amt_per_day*v_bill_days;
    l_strm_level_tbl(v_billing_sequence).level_amount := v_amt_per_day*v_bill_days;
    l_strm_level_tbl(v_billing_sequence).lines_detailed_yn := 'Y';
    l_strm_level_tbl(v_billing_sequence).due_arr_yn := 'Y';
    dbms_output.put_line('Before calling the Bill Sch API for MTH days');
    OKS_CONTRACTS_PUB.CREATE_BILL_SCHEDULE ( p_billing_sch=>'E',
    p_strm_level_tbl=>l_strm_level_tbl,
    p_invoice_rule_id=>v_invoicing_rule_id,
    x_return_status=>x_return_status);
    dbms_output.put_line('After calling the Bill Sch API for MTH days');
    IF x_return_status <> 'S' THEN
    x_msg_count := 1;
    dbms_output.put_line('Day schedule, for monthly accounting rule, creation error ' || x_msg_data);
    --DBMS_TRANSACTION.ROLLBACK_SAVEPOINT('OKS_A');
    --RETURN;
    END IF;
    END IF;
    END IF;
    COMMIT;
    EXCEPTION
    when others then
    dbms_output.put_line('Error ' || sqlerrm);
    END;
    Thanks,
    Yash.

    Hi There,
    I have a similar requirement to create rental service contracts and create billing schedules.
    Can you please pass on your functional docs so that i can refer to them.
    Thanks,
    Raidu

  • Request creation error for mitigation control workflow

    Dear Expert,
             I had activiate the workflow from RAR to CUP on Mitigated User assignment, I had completed following customizing:
    1)RAR->configaration->Workflow
    2)CUP->configaration->initiator, stage, path.
    but when I created mitigated user assignments in RAR, after click "Submit", error popup: "Request creation error"
    can some one help?
    thanks!

    Dear,
         the log is below:
    ERROR       service 'SAPGW00' unknown
    TIME        Thu May 20 13:33:16 2010
    RELEASE     701
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -3
    MODULE      niuxi.c
    LINE        1732
    DETAIL      NiPGetServByName2: service 'SAPGW00' not found
    SYSTEM CALL getservbyname_r
    COUNTER     375
    May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
    INFO: Exception in Server YYY:
    com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
    This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
    Could not start server: Connect to SAP gateway failed
    Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
    ERROR       service 'SAPGW00' unknown
    TIME        Thu May 20 13:33:16 2010
    RELEASE     701
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -3
    MODULE      niuxi.c
    LINE        1732
    DETAIL      NiPGetServByName2: service 'SAPGW00' not found
    SYSTEM CALL getservbyname_r
    COUNTER     375
    May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
    INFO: Exception in Server YYY:
    com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
    This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
    Could not start server: Connect to SAP gateway failed
    Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
    ERROR       service 'SAPGW00' unknown
    TIME        Thu May 20 13:33:16 2010
    RELEASE     701
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -3
    MODULE      niuxi.c
    LINE        1732
    DETAIL      NiPGetServByName2: service 'SAPGW00' not found
    SYSTEM CALL getservbyname_r
    COUNTER     375
    May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
    INFO: Exception in Server YYY:
    com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
    This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
    Could not start server: Connect to SAP gateway failed
    Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
    ERROR       service 'SAPGW00' unknown
    TIME        Thu May 20 13:33:16 2010
    RELEASE     701
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -3
    MODULE      niuxi.c
    LINE        1732
    DETAIL      NiPGetServByName2: service 'SAPGW00' not found
    SYSTEM CALL getservbyname_r
    COUNTER     375
    May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
    INFO: Exception in Server YYY:
    com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
    This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
    Could not start server: Connect to SAP gateway failed
    Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
    ERROR       service 'SAPGW00' unknown
    TIME        Thu May 20 13:33:16 2010
    RELEASE     701
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -3
    MODULE      niuxi.c
    LINE        1732
    DETAIL      NiPGetServByName2: service 'SAPGW00' not found
    SYSTEM CALL getservbyname_r
    COUNTER     375
    May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
    INFO: Exception in Server YYY:
    com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
    This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
    Could not start server: Connect to SAP gateway failed
    Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
    ERROR       service 'SAPGW00' unknown
    TIME        Thu May 20 13:33:16 2010
    RELEASE     701
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -3
    MODULE      niuxi.c
    LINE        1732
    DETAIL      NiPGetServByName2: service 'SAPGW00' not found
    SYSTEM CALL getservbyname_r
    COUNTER     375
    May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
    INFO: Exception in Server YYY:
    com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
    This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
    Could not start server: Connect to SAP gateway failed
    Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
    ERROR       service 'SAPGW00' unknown
    TIME        Thu May 20 13:33:16 2010
    RELEASE     701
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -3
    MODULE      niuxi.c
    LINE        1732
    DETAIL      NiPGetServByName2: service 'SAPGW00' not found
    SYSTEM CALL getservbyname_r
    COUNTER     375
    May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
    INFO: Exception in Server YYY:
    com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
    This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
    Could not start server: Connect to SAP gateway failed
    Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
    ERROR       service 'SAPGW00' unknown
    TIME        Thu May 20 13:33:16 2010
    RELEASE     701
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -3
    MODULE      niuxi.c
    LINE        1732
    DETAIL      NiPGetServByName2: service 'SAPGW00' not found
    SYSTEM CALL getservbyname_r
    COUNTER     375
    May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
    INFO: Exception in Server YYY:
    com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
    This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
    Could not start server: Connect to SAP gateway failed
    Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
    ERROR       service 'SAPGW00' unknown
    TIME        Thu May 20 13:33:16 2010
    RELEASE     701
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -3
    MODULE      niuxi.c
    LINE        1732
    DETAIL      NiPGetServByName2: service 'SAPGW00' not found
    SYSTEM CALL getservbyname_r
    COUNTER     375
    May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
    INFO: Exception in Server YYY:
    com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
    This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
    Could not start server: Connect to SAP gateway failed
    Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
    ERROR       service 'SAPGW00' unknown
    TIME        Thu May 20 13:33:16 2010
    RELEASE     701
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -3
    MODULE      niuxi.c
    LINE        1732
    DETAIL      NiPGetServByName2: service 'SAPGW00' not found
    SYSTEM CALL getservbyname_r
    COUNTER     375
    May 20, 2010 2:10:50 PM com.virsa.cc.workflow.bo.WorkflowBO submit
    INFO: END POOINT URL: http://9.186.143.129:50100/AEWFRequestSubmissionService_5_2/Config1?style=document
    May 20, 2010 2:10:50 PM com.virsa.cc.workflow.bo.WorkflowBO submit
    INFO: before submit:
    May 20, 2010 2:10:50 PM com.virsa.cc.workflow.bo.WorkflowBO submit
    INFO: wftype: MITIOBJ reqid: GRC01
    May 20, 2010 2:10:50 PM com.virsa.cc.rulearchitect.dao.dto.MitObjDTO getObjContext
    FINEST: validfrom: 2010-05-20 validto: 2011-05-20
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Data Type: String
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Descripton: MITREFNO
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Name: MOMITREFNO
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Value: CT01
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Data Type: String
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Descripton: RISKID
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Name: MORISKID
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Value: ZC02
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Data Type: String
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Descripton: LANG
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Name: LANG
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Value: EN
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Data Type: String
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Descripton: MONITORID
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Name: MONITORID
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Value: GRC01
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Data Type: Integer
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Descripton: STATUS
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Name: MOSTATUS
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Value: 0
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Data Type: DATE
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Descripton: VALIDFROM
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Name: VALIDFROM
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Value: 05/20/2010
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Data Type: DATE
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Descripton: VALIDTO
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Name: VALIDTO
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Value: 05/20/2011
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Data Type: String
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Descripton: BU ID
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Name: BUID
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Value: null
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Data Type: String
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Descripton: Approver ID
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Name: MOAPPROVERID
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Value: null
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Data Type: String
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Descripton: OBJTYPE
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Name: OBJTYPE
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Value: U
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Data Type: String
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Descripton: OBJID
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Name: OBJID
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Value: 207471
    May 20, 2010 2:10:50 PM com.virsa.cc.workflow.bo.WorkflowBO submit
    INFO: Return code: 2010 Message: com.virsa.ae.core.ObjectNotFoundException: Invalid Priority Value : MO_HIGH workflow id: null Status: null
    May 20, 2010 2:10:50 PM com.virsa.cc.workflow.bo.WorkflowBO submit
    WARNING: 2010: null

  • Campus Manager report - Ports in error Disabled state

    Hi,
    I have LMS 3.2 and I wonder how Campus Manager collects information from the switch to generate a report of discrepancies, namely a report of "Ports in Error Disabled state"??
    I find that I have ports in errDisabled state but Campus Manger doesn´t show this information in "Ports in Error Dissabled state" report. What could be the problem?
    Thanks.

    Hi,
    Campus Manager do snmpwalk on the ciscoErrDisableMIB to get the status of the error disabled ports.
    Thanks,
    Gaganjeet Singh

  • Error: "Cannot connect to the provider. Make sure it is running in the specified host/port. Error (12031)"

    Hi,
    EPM version: EPM 11.1.2.1
    When we are using Zoom In Level as All Levels and tring to drill down for dimention of HFM application we are getting below error.
    Error: "Cannot connect to the provider. Make sure it is running in the specified host/port. Error (12031)"
    As we found some solution from comunity , we have performed below workaround but still we are getting same error.
    ·              We have done the changes in mod_wl_ohs.conf file of OHS  with (WLIOTimeoutSecs 3600 and WLIOSocketTimeoutSecs 3600)
    ·              And then restarted OHS and  APS service but still we found same error.
    Could anyone please suggest ,where can we trace its log from web server and the solution for this issue?
         Thanks,
             D.N. Rana

    Hi,
    We have already performed the changes for APS in OHS as mentioned in the solution and the path also same as under OHS.
    Intially we were getting error for "to increase netRetryCould and NetRetryInterval"  as a solution we have added below 3  registry DWORD keys under  path
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings
    "KeepAliveTimeout"=dword:00180000                   (26 Minutes)
    "ReceiveTimeout"=dword:00dbba00                      (240 Minutes)
    "ServerInfoTimeout"=dword:00180000                  (26 Minutes)
    Above error resolved but then we received Error"12031"
    Now we have added above 3 DWORD keys under path HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings
    and now we are not getting the  error "12031".
    But here we are not getting how it(LB issue) resolved with above solution?
    Thanks,
    D.N.Rana

  • Cannot find the maps stored in import manager during port creation

    Hi All,
    I am unable to find any maps that i saved in import manager during port creation ,the maps are not showing in dropdown list during port creation in console.Do i need to store the maps that i have in import manager in specific place under mdm server,so that i can see them during port creation.
    All i need to do is assign my import map during inbound port creation,but i cannot find any maps in console.
    Could I know whether i am storing my maps some where other than default location.
    Thanks
    Aravind

    Hi Aravind,
    First of all check the remote system assigned to ur Port. After that go to import manager. When u logon to the import manager, u get a window "Connect to source". Mention the same remote system over there.Select the file type.Browse the file and map the fields,values,field matching and save the map. then unload the repo and assign the map to the port.
    Second way is, u create the port first and give any particular remote system to it. Put the file (u want to use for mapping) in the ready folder of that port and in connect to source window select the type as port, remote system(ame as used port port) and port.then map and save. unload the repo and assign the map to port. Ready folder will be in ur server at location: C drive or D drive->SAP MDM 5.5 ->server->distributions->repo name->inbound->port code->ready. For this option, Ur port type should be manual. After assigning the map u can change it to automatic or keep it manual as per ur requirement.
    Hope this solves ur problem.
    Regards,
    Dheeraj.
    Edited by: Dheeraj Kumar on May 6, 2008 9:16 AM

  • Delivery Note to Subcontract creation error "Essential transfer parameters

    Hi
    I am facing issue in return delivey
    Delivery Note to Subcontract creation error "Essential transfer parameters are missing in record:000001".
    Could you please let me know the casue of this error and where exactly i can see error.
    Regards
    vikcy

    Hi Vicky,
                   Check If the Customer number(Plant) has been maintained in the vendor master record control data and the vendor should also be maintained in the customer master data. Once you maintain this system determines the shipping point based on the  customer master and the shipping data missing. Kindly try delivering after maintaining these and let me know If you need any more information on this.
    Regards
    Ram Pedarla

  • Child creation Error on vms HELP

    Hi,
    Iam trying to execute a file from withing a java program on VMS This is my code
    public class BAMBOE {
      public static void main(String[] args) { 
        BamboeRunner boe = new BamboeRunner();
        boe.start();
    import java.io.*;
    public class BamboeRunner extends Thread implements Runnable { 
      public void run() {
        try {
          Process process = Runtime.getRuntime().exec("@SIMPEL");
          process.waitFor();
          return ;
        catch (Exception e) {
          e.printStackTrace();
          return ;
    }But I keep getting the following error:
    java.io.IOException: Child creation error: error 100052
    VMS error code: error 100052
            at java.lang.UNIXProcess.<init>(Compiled Code)
            at java.lang.Runtime.exec(Compiled Code)
            at java.lang.Runtime.exec(Compiled Code)
            at BamboeRunner.run(Compiled Code)Anybody that can help me fix this problem please??

    I've managed to get somewhere with this...
    I've got it to work by having the system command I want to run in a com file and specifying the full path to that file in the exec method without the '@'...
    e.g.
    Process proc = Runtime.getRuntime.exec("ppoi_dev:[user.dba_ppoi.matt.proc]proc.com");
    where the file
    ppoi_dev:[user.dba_ppoi.matt.proc]proc.com
    contains
    $ dir
    When I run this I can get the output from the dir command by reading from the InputStream of the Process object.
    Have fun.

Maybe you are looking for