Non-SOAP WSDL bindings? (GET/POST?)

Hi,
I would like to know if Aqualogic Service Bus can transform SOAP requests into GET/POST requests?
My organization has several legacy services, which are really just CGIs that accept GET query parameters and return XML results in the HTTP response body.
I would like to integrate those services into an SOA based environment.
I hoped that I could model my legacy services as Web Services using an HTTP GET binding (using WSDL). Then I could import them into Aqualogic and design a transforming proxy in front of them. Is that possible?
Thanks,
Erik

Erik,
just define a SOAP based proxy service and before calling the CGI based business service extract data from the SOAP body and add it to the http transport headers for the outgoing business service call. We have done this succesfully in some projects.
-Kai

Similar Messages

  • How do I create only SOAP WSDL bindings when deploying my ESB?

    Currently when I use either jDeveloper or the ant deployESBSuitcase task to deploy the ESB that is the entry point to my application I get two bindings in the deployed wsdl. One soap binding that my client will be using and another esb binding. Is it possible to modify the deployment plan to only generate the SOAP binding? Do I need to have the esb binding for an esb that is only used as the entry point to my application? I would prefer to have the wsdl that is exposed to my clients to not have the vendor extensions if possible.
    thanks

    I have experienced the exact same problem. There is no good solution to these poorly designed and overly complex login protocols. After unsuccessfully trying to retrieve my password or change my password  I finally set up a new email account, a new Apple ID and a new iTunes account.
    I know it is not a good solution, but it worked.

  • Re: Why doesn't WL7.0 support get/post bindings for web services ...

    hi!!!
    Could you pls point to any code example.
    thanks
    Pushpa
    "Richard Berger" <[email protected]> wrote:
    >
    Manoj: Thanks for the answer - do you have or can you point me at any
    code samples
    that accomplish this? (Yes, .NET is limited to strings/ints in their
    get/post
    bindings).
    Thanks so much!
    RB
    PS - Also, can you explain any apparent discrepancy between your answer
    and what
    the WL documentation stated (again, it may be my misunderstanding).
    "manoj cheenath" <[email protected]> wrote:
    WL 7.0 does allow you to access the web service through
    the browser. It even allows you to invoke service methods
    with complex type arguments (.Net only supports primitive
    types) and also to view the request and response soap
    message for the invocation.
    regards,
    -manoj
    "Richard Berger" <[email protected]> wrote in message
    news:[email protected]...
    This might be a naive question, but according to the documentation,WL 7.0
    does
    not support http post/get bindings for web services. Thus, for meto
    access a
    web service, I need to write a "middle tier" of some sort (I used
    the
    automatically
    generated Java proxy code and JSP). All works fine, but it seems
    like
    it
    would
    sure be nice to have HTML forms access web services without havingto
    write a
    middle tier.
    NET does this and it is extremely useful - is there a reason that
    BEA
    chose not
    to provide this feature? (e.g. is it architecturally unsound in anyway?
    or is
    there an easy way to simulate it?). Given some of the Web Workshoppositioning
    re: ease of use and .NET comparison, this seems like an omission.
    Any insights are greatly appreciated.
    Enjoy,
    RB
    PS - Here's the info from the documentation
    Web Services Description Language (WSDL) 1.1 Specification
    WSDL is an XML-based language that describes Web services. WSDL definesWeb services
    as a set of endpoints operating on messages; these message containeither
    message-style
    or RPC-style information. The operations and messages are describedabstractly
    in WSDL, and then bound to a concrete network protocol and messageformat
    to define
    an endpoint. Related concrete endpoints are combined into abstractendpoints (services).
    WSDL is extensible to allow the description of endpoints and theirassociated
    messages regardless of what message formats or network protocols areused
    to communicate,
    however, the only bindings described in the specification describehow to
    use
    WSDL in conjunction with SOAP 1.1, HTTP GET/POST, and MIME.
    Note: WebLogic Server supports only SOAP 1.1 bindings.
    The WSDL 1.1 Specification is available at http://www.w3.org/TR/wsdl.

    This isn't a straight FORM Post as in the http binding support in WSDL. It posts
    a soap message.
    It's apparent that Workshop supports form-post and form-get.
    But I dont see how it is done with straight WebLogic webservices. Does WebLogic
    server read the web-services.xml or the WSDL file? I dont see a way to put in
    http-post binding in the former and in the latter it seems to be ignored.
    Can someone clarify.
    Thanks.
    Chu-chi
    "manoj cheenath" <[email protected]> wrote:
    Here is a live example:
    http://65.193.192.35:7001/base/SoapInteropBaseService
    Here is an example that you can download:
    http://manojc.com/?sample2
    This is how you run it:
    http://manojc.com/?tutorial/doc/howtorun.html
    More info can be found from the edocs:
    7.0:
    http://edocs.bea.com/wls/docs70/webserv/index.html
    8.1:
    http://edocs.bea.com/wls/docs81/webserv/index.html
    Regards,
    -manoj
    http://manojc.com
    "pushpa krishna" <[email protected]> wrote in message
    news:[email protected]...
    hi!!!
    Could you pls point to any code example.
    thanks
    Pushpa
    "Richard Berger" <[email protected]> wrote:
    Manoj: Thanks for the answer - do you have or can you point me at
    any
    code samples
    that accomplish this? (Yes, .NET is limited to strings/ints in their
    get/post
    bindings).
    Thanks so much!
    RB
    PS - Also, can you explain any apparent discrepancy between your answer
    and what
    the WL documentation stated (again, it may be my misunderstanding).
    "manoj cheenath" <[email protected]> wrote:
    WL 7.0 does allow you to access the web service through
    the browser. It even allows you to invoke service methods
    with complex type arguments (.Net only supports primitive
    types) and also to view the request and response soap
    message for the invocation.
    regards,
    -manoj
    "Richard Berger" <[email protected]> wrote in message
    news:[email protected]...
    This might be a naive question, but according to the documentation,WL 7.0
    does
    not support http post/get bindings for web services. Thus, for
    me
    to
    access a
    web service, I need to write a "middle tier" of some sort (I used
    the
    automatically
    generated Java proxy code and JSP). All works fine, but it seems
    like
    it
    would
    sure be nice to have HTML forms access web services without havingto
    write a
    middle tier.
    NET does this and it is extremely useful - is there a reason that
    BEA
    chose not
    to provide this feature? (e.g. is it architecturally unsound in
    any
    way?
    or is
    there an easy way to simulate it?). Given some of the Web Workshoppositioning
    re: ease of use and .NET comparison, this seems like an omission.
    Any insights are greatly appreciated.
    Enjoy,
    RB
    PS - Here's the info from the documentation
    Web Services Description Language (WSDL) 1.1 Specification
    WSDL is an XML-based language that describes Web services. WSDL
    defines
    Web services
    as a set of endpoints operating on messages; these message containeither
    message-style
    or RPC-style information. The operations and messages are describedabstractly
    in WSDL, and then bound to a concrete network protocol and messageformat
    to define
    an endpoint. Related concrete endpoints are combined into abstractendpoints (services).
    WSDL is extensible to allow the description of endpoints and theirassociated
    messages regardless of what message formats or network protocols
    are
    used
    to communicate,
    however, the only bindings described in the specification describehow to
    use
    WSDL in conjunction with SOAP 1.1, HTTP GET/POST, and MIME.
    Note: WebLogic Server supports only SOAP 1.1 bindings.
    The WSDL 1.1 Specification is available at http://www.w3.org/TR/wsdl.

  • Why doesn't WL7.0 support get/post bindings for web services ...

    This might be a naive question, but according to the documentation, WL 7.0 does
    not support http post/get bindings for web services. Thus, for me to access a
    web service, I need to write a "middle tier" of some sort (I used the automatically
    generated Java proxy code and JSP). All works fine, but it seems like it would
    sure be nice to have HTML forms access web services without having to write a
    middle tier.
    .NET does this and it is extremely useful - is there a reason that BEA chose not
    to provide this feature? (e.g. is it architecturally unsound in any way? or is
    there an easy way to simulate it?). Given some of the Web Workshop positioning
    re: ease of use and .NET comparison, this seems like an omission.
    Any insights are greatly appreciated.
    Enjoy,
    RB
    PS - Here's the info from the documentation
    Web Services Description Language (WSDL) 1.1 Specification
    WSDL is an XML-based language that describes Web services. WSDL defines Web services
    as a set of endpoints operating on messages; these message contain either message-style
    or RPC-style information. The operations and messages are described abstractly
    in WSDL, and then bound to a concrete network protocol and message format to define
    an endpoint. Related concrete endpoints are combined into abstract endpoints (services).
    WSDL is extensible to allow the description of endpoints and their associated
    messages regardless of what message formats or network protocols are used to communicate,
    however, the only bindings described in the specification describe how to use
    WSDL in conjunction with SOAP 1.1, HTTP GET/POST, and MIME.
    Note: WebLogic Server supports only SOAP 1.1 bindings.
    The WSDL 1.1 Specification is available at http://www.w3.org/TR/wsdl.

    Manoj: Thanks for the answer - do you have or can you point me at any code samples
    that accomplish this? (Yes, .NET is limited to strings/ints in their get/post
    bindings).
    Thanks so much!
    RB
    PS - Also, can you explain any apparent discrepancy between your answer and what
    the WL documentation stated (again, it may be my misunderstanding).
    "manoj cheenath" <[email protected]> wrote:
    WL 7.0 does allow you to access the web service through
    the browser. It even allows you to invoke service methods
    with complex type arguments (.Net only supports primitive
    types) and also to view the request and response soap
    message for the invocation.
    regards,
    -manoj
    "Richard Berger" <[email protected]> wrote in message
    news:[email protected]...
    This might be a naive question, but according to the documentation,WL 7.0
    does
    not support http post/get bindings for web services. Thus, for meto
    access a
    web service, I need to write a "middle tier" of some sort (I used theautomatically
    generated Java proxy code and JSP). All works fine, but it seems likeit
    would
    sure be nice to have HTML forms access web services without havingto
    write a
    middle tier.
    NET does this and it is extremely useful - is there a reason that BEAchose not
    to provide this feature? (e.g. is it architecturally unsound in anyway?
    or is
    there an easy way to simulate it?). Given some of the Web Workshoppositioning
    re: ease of use and .NET comparison, this seems like an omission.
    Any insights are greatly appreciated.
    Enjoy,
    RB
    PS - Here's the info from the documentation
    Web Services Description Language (WSDL) 1.1 Specification
    WSDL is an XML-based language that describes Web services. WSDL definesWeb services
    as a set of endpoints operating on messages; these message containeither
    message-style
    or RPC-style information. The operations and messages are describedabstractly
    in WSDL, and then bound to a concrete network protocol and messageformat
    to define
    an endpoint. Related concrete endpoints are combined into abstractendpoints (services).
    WSDL is extensible to allow the description of endpoints and theirassociated
    messages regardless of what message formats or network protocols areused
    to communicate,
    however, the only bindings described in the specification describehow to
    use
    WSDL in conjunction with SOAP 1.1, HTTP GET/POST, and MIME.
    Note: WebLogic Server supports only SOAP 1.1 bindings.
    The WSDL 1.1 Specification is available at http://www.w3.org/TR/wsdl.

  • FC valuation not getting posted to non-leading ledger

    Hi Gurus,
    I need your help to resolve the following issue. We have a company code with 1st LC as EUR and 2nd LC as USD which is group currency. We have valuation area V1 assigned to the ledger group that has set-up for postings to both leadine (0L) and non-leading ledger (Z1). When I am trying to run FC valuation using transaction FAGL_FC_VAL, the valuation document gets posted to leading ledger only. There is no posting to non-leading ledger. The other ledger tab is missing in the GL view of the document confirming that the posting happened in the leading ledger only.
    I have gone over lot of threads in the forum but could not figure out the issue. I would really appreciate if someone can guide me to resolve this issue.
    Thanks,
    Shalu

    Hi Shankar
    Thanks for your reply. Yes, the non-leading ledger is active and has been assigned properly to the ledger group. The set-up is working fine for all company codes except one company code. In our set-up, for all company codes, we are using a valuation area V1 with always evaluate as valuation menthod and CC curency as currency type and Group currency as additional currency. We were having some valuation issues with one company code with existing set-up as Local currency 1 was different from LC2. In order to fix that issue, I created new valuation area V3 with same valuation method and currency type but no additional currency. The ledger group and assignemnts were same. The original issue with curency valuation got resolved but the new issue appeared that the posting is happening only in the leading ledger and nothing for this company code is getting posted to non-leading ledger while running transaction FAGL_FC_VAL.
    If I manually force the currency in F-02 in this company code, the posting does happen to the non-leading ledger. The issue is with automatic postings only using area V3.
    Please help.
    Thanks,
    Shalu

  • WSDL bindings

    Hi Experts,
    I would like to use the following bindings in WSDL.
    1. HTTP GET/POST
    2. MIME
    Usually we can do the SOAP binding through our XI's Integration Directory.
    Could you please tell me, from where we can do the HTTP GET/POST and MIME bindings?
    Regards
    Sara

    HI Sara
    The XI cannot send out-of-the-box multipart/form-data. In fact the HTTP adapter cannot deal with MIME type multipart at all.
    Maybe you can add the required data to the prolog and epilog parameters when you know the exact HTTP stream that the server requires.
    refer the below links ....
    Re: Mail Adapter Send Mail with Attachment
    http://help.sap.com/saphelp_nw04/helpdata/en/23/c093409c663228e10000000a1550b0/content.htm
    Thanks !

  • How to send SOAP request by HTTP POST?

    I want to access a SOAP webservice using mx.rpc.soap.mxml.WebService.
    Following is my code:
    <mx:WebService id="miner_service" wsdl="http://localhost:8080">        <mx:operation name="hello" result="echoResultHandler(event);"></mx:operation></mx:WebService>
    When debugging with that, I got such error message:
    [Fault] exception, information=[RPC Fault faultString="HTTP request error" faultCode="Server.Error.Request" faultDetail="Unable to load WSDL. If currently online, please verify the URI and/or format of the WSDL (http://localhost:8080)"]
    Then I use Fiddler try to capture the response returned by server, it's like this:
    Error responseError code 501. Message: Unsupported method ('GET'). Error code explanation: 501 = Server does not support this operation.
    But when I use python to send SOAP request by HTTP POST, the server will return correct response.
    So how can I send SOAP request by HTTP POST?
    (I tried <mx:WebService wsdl="http://localhost:8080" method="POST">, but no luck..)

    Sorry for my late reply..
    There's no WSDL for that SOAP service

  • Migrating SOAP WSDL Defs through environments

    Hey
    I am using the WsdlGenerator component to allow me to create WSDL defs to the Content Server Services. My .Net apps are using the WSDL's to connect to Web Services to perform a variety of functions...
    I have recently moved my processes up from Dev into our UAT environment. I have installed the WsdlGenerator component in UAT, but can't figure out how to move the Wsdl defs up. I tried moving the .wsdl files to the "\weblayout\groups\secure\wsdl\custom" folder on the target server, but my code cannot connect to these webserver defs. For the moment, I have resorted to moving the defs by hand, recreating them in the target environment using the "Soap Wsdl" screen under Administration in the Web Client.
    Is there a better way to do it?
    BTW - I am using Content Server 7.5 on a Microsoft based environment.
    Cheers,
    Al

    Hi,
       It looks HTTP Status code 200. That means you already connected to third party. It may be the reason for response message .
    Standard response for successful HTTP requests. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request the response will contain an entity describing or containing the result of the action.
    Deva

  • OWSM 10.1.3.4 and Non-SOAP XML-based web service

    Hi all,
    According to the OWSM 10.1.3.4 Administrator's Guide, "all Web services registered with an Oracle WSM Gateway are virtualized as both a SOAP and non-SOAP Web service." To access the non-SOAP (XML-only) web service, the documentation states "The non-SOAP virtualized URL can be determined from the virtualized SOAP URL by replacing the services keyword in the URL with the xml keyword."
    For example, if the SOAP virtualized endpoint is:
    http://host:port/gateway/services/SID0003001
    then, the non-SOAP XML service endpoint is:
    http://host:port/gateway/xml/SID0003001
    I have several web services registered with an OWSM gateway, running on SOA Suite 10.1.3.4, and can access those without any problem. However, when I attempt to access the "/gateway/xml" version of these services, I simply get an HTTP 200 response header with a null body.
    Does anyone have any ideas what could be causing this or what the secret is to get the non-SOAP XML service feature of OWSM to work?
    Thanks!
    --Gary                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

    Hi all,
    According to the OWSM 10.1.3.4 Administrator's Guide, "all Web services registered with an Oracle WSM Gateway are virtualized as both a SOAP and non-SOAP Web service." To access the non-SOAP (XML-only) web service, the documentation states "The non-SOAP virtualized URL can be determined from the virtualized SOAP URL by replacing the services keyword in the URL with the xml keyword."
    For example, if the SOAP virtualized endpoint is:
    http://host:port/gateway/services/SID0003001
    then, the non-SOAP XML service endpoint is:
    http://host:port/gateway/xml/SID0003001
    I have several web services registered with an OWSM gateway, running on SOA Suite 10.1.3.4, and can access those without any problem. However, when I attempt to access the "/gateway/xml" version of these services, I simply get an HTTP 200 response header with a null body.
    Does anyone have any ideas what could be causing this or what the secret is to get the non-SOAP XML service feature of OWSM to work?
    Thanks!
    --Gary                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • CREMDM splitted by PI, ADRMAS gets posted, CREMAS in inbound queue

    Hi all,
    I am on SAP MDM 7.1 SP03, SAP PI and SAP ECC6.
    I have gone thorugh all the threads and Guides related to MDM but couldn't find a valid solution for my problem described below. However, I did find some tricks and tweaking which I dont want to use as they are not recommended by SAP.
    We syndicated NEW Vendor records being created in MDM using CREMDM with standard Syndication Map. We have Vendors number generated in MDM and the number range being used exists in ECC and is marked as external. Moreover, the number range uses all of 10 digits, so there is no question of Conversion Routines with it. We deployed PI for splitting CREMDM to ADRMAS and CREMAS. We have serialized ADRMAS to go before CREMAS. We have assured that fields common between these two, have "no data" character i.e. "/" in CREMAS with correct data in ADRMAS. And ADDR_GROUP is mapped as "BP".
    Now the problem is, ADRMAS gets posted but CREMAS remains in the inbound queue. The queue running but still CREMAS remains there with CODE as "75". This results in non-creation od Vendor master record as CREMAS is not posted.
    Can anybody help with this. I really appreciate the support.

    Hi R,
    The ALE inbound function modules treat each IDoc segment as a current set of data. Missing fields (or fields that have no data) are interpreted as a value deletion. To keep the existing value for a single field, you have to add a no-data sign as field value for NAME_1. This no-data sign is a single slash (/).
    Please execute the inbound function module manually in WE19 to test this. If an exception is seen at NAME_1 ,pass a value or '/' and check for successful posting of Idoc.
    If this works, modify inputs to CREMAS accordingly.
    In addition a good SAP Note 1052964 - MDM: Distribution of Business Partners, Customers, Vendors for your reference.
    Regards,
    Vinay M.S

  • Export SOAP WSDL's in UCM

    Hello All,
    I have created WSDL for 'AddCollection' in development env. I can able to create collection (folders) & check-in docs to this collections through a java program using this wsdl. Now i want to export this AddCollection.wsdl file to testing env. I couldn't find any option for exporting & importing soap wsdl's in UCM. (or) I have to generate/create the same structure of collection wsdl in testing env manually, is this right way?
    Could anyone can provide some idea to overcome this tasks.
    My UCM configuration is
    Product Version 10.1.3.3.2 (071031)
    Product Build 7.2.2.184
    Native Version 7.1.0.1
    Thanks.
    Regards,
    Gowri.

    You have several options:
    First, check out the <install>/data/soap/custom directory and you might find the definition of your custom wsdl. You could move that over to the new server, wire it in and see if it shows up?
    Second, there used to be a class called WsdlMerger.java that would allow you to create a component that would install/update custom wsdl's on target machines. This is of limited use for one or two moves, but if you're creating a component with a lot of reuse it works slick. It does take some work to build out and does require some Java skills. If interested, kick me a note and I'll try to get you the Java class for you to toy around with. jason at corecontentonly dot com.
    -Jason
    http://www.corecontentonly.com

  • SOAP/WSDL builder for C programming

    Dear guru,
    is any possibility or can you give any hint if exist some SOAP/WSDL builder for creating C libraries from SOAP/WSDL and vice versa?
    Thanks a lot for help.
    Regards,
    Roman

    Rfcsdk, there is a genh.exe in bin folder, which can be used to generate c headers according to ddic table/struct def (se11).
    and, you may use Nco to generate wsdl / c#  class desc.
    all these two method may use se37 function
    RFC_GET_FUNCTION_INTERFACE(RFC_GET_FUNCTION_INTERFACE_US) to get function parameter info(I,E,T...) and for a struct/table use  RFC_GET_UNICODE_STRUCTURE to get detailed struct info, you may then generate your sql/c#/c typedef/...
    Hope these info can be help, you may reach me at <b><REMOVED BY MODERATOR></b>, good luck.
    Message was edited by:
            Alvaro Tejada Galindo

  • IdcService SOAP WSDLs

    There are lot of idcServices which are OOTB ..is there a way where I can get the wsdl's for those as there are only few wsdl's available under SOAP wsdls link.

    Yes, take a look at this link: http://download.oracle.com/docs/cd/E17904_01/doc.1111/e10807/a01_wsdl_and_soap.htm#sthref1831

  • Data is not getting posted in ABAP Proxy.

    Hi,
    I am working on File to ABAPProxy scenario. The data is not going to proxy.
    In PI sxmb_moni is status is successfull and in the R3 sxmb_moni the status is successfull. But the data is not getting posted in the tables(ABAPProxy). I had checked the inbound and oubound queues. And with the same input data, abapers cheked their code in Abapproxy, then the table is getting updated. When we trigger from PI, the tables are not getting updated.Please help me.
    Thanks,
    Pragathi.

    Hi,
    The problem may be
    Case 1: Cache is not getting refreshed(Check SXI_CACHE)
    Case 2: The Queue Is blocked (Check SMQ1 & SMQ2)
    Regards,
    Sainath

  • EDI vendor invoices do not get posted before GRN is posted

    Hello All,
    The requirement is our vendor sends EDI invoices and they get parked in SAP as IDOCs. IDOC gets posted if GRN exist for a PO.
    In purchase order it is GR based IV. If vendor parks invoice and there is no GRN for purchase order then IDOC fails and it goes in status 51 (Error).
    Our requirement is, IDOC should get posted even if there is no GRN for a purchase order and client do not want to remove GR based IV tick from PO. After through verification of the parked invoice it gets posted in the system.
    We have done the config change in MM>>LIV>>EDI>Enter program parameters, we have maintained value "1" for field "Processing". Inspite of this change system does not process inbound ICOCs and they go in error (51) status.
    Please provide solution for this.
    Thanks & regards.
    Sanjay

    Hello Jurgen,
    The change in piece of code suggested in SAP note no. 501524 was already implemented in our syste, However still invoice IDOC fails and it goes in error "status 51" as there is no GRN for that purchase order. However if material GRN is made for 1 qty then the invoice gets parked with the full amount even if the GRN  is for 1 no.
    Please suggest a suitable solution.
    Thanks.
    Sanjay

Maybe you are looking for

  • How to read data from the excel file using java code.

    Hi to all, I am using below code to getting the data from the excel file but I can't get the corresponding data from the specific file. can anyone give me the correct code to do that... I will waiting for your usefull reply...... advance thanks.... i

  • Problem sending a HTML page

    How can i send a HTML by email?? When i am sending a HTML he shows the code in the mail instead of showing the HTML page?? Anyone knows how can i solve tyhis??

  • Receiver shows in Cc only when using SO_NEW_DOCUMENT_SEND_API1

    I'm using FM SO_NEW_DOCUMENT_SEND_API1 to send external emails from SAP.  I have everything working quite well except... The receivers e-mail address only appears in the "Cc" field in the e-mail's header.  I cannot get it to show in the "To" field.

  • Camparing property with node name in 2 different Version

    Hi Guru, Please help me to extract a report or build validation for comparing the property value of a node in a heirarchy (say Hierarchy 1) of version (Say version 1) against the differnet property value of a node from another heirarchy (Say Hierarch

  • Required inventory level in Item Master

    Hi,                     In the item master data in Inventory tab we have minimum inventory,maximum inventory and also required level.What is the function of that field.Because it is not filled automatically even after the stock level goes below minim