Create TU via qRFC in EWM

Hi
I knew that SAP supports standard IDoc communication via XI for creation of TU in EWM. Is it possible to change this to qRFC communication?
Thanks
Sasidhar Gupta

Hi Sasidhar
If you are not using shipment functionality in ERP and still want to achieve shipping and receiving (TU and Veh ) functionality in EWM. Please find below way. In this way IBD qrfc will create TU/VHE in EWM directly. No shipment required in ERP-ECC.
Integration of ERP Deliveries in Shipping and Receiving - Shipping and Receiving - SAP Library
Shipping and receiving offers features to create transportation units or vehicles in SAP EWM based on transport information contained in SAP ERP inbound or outbound deliveries. With this integration, you can plan the transportation process for deliveries in ERP without using shipments in ERP.
Prerequisites
You must ensure that the following prerequisites are met:
The DTU status (Assign Transportation Unit) is active for the delivery type and item type used in EWM.
The PPF action /SCWM/WHR_CREATE_VEHICLE is active in the action profile assigned to the delivery type in EWM.
When creating a delivery in ERP, you enter a means of transport type and a means of transport ID in the delivery header.
You have created a link between the means of transport derived from the ERP means of transport type and the TU packaging material. On the Easy Access screen, choose Extended Warehouse Management Settings Shipping and Receiving Link Between Packaging Material (TU) and Means of Transport . This setting determines whether EWM creates a vehicle and/or a transportation unit.
Regards
Suraj

Similar Messages

  • Updating Requisition No while creating PO via FM-BAPI_PO_CREATE1

    Hi ,
    Our requirement is creating Po via FM BAPI_PO_CREATE1 and we are passing data from other Application through that BAPI. Tracking field of  the Application with SAP is only Requisition No.
    I want to know in  which field of that BAPI I'll make the entry to update Requisition  No. of PO?
    Thanks & Regards,
    Biswajit
    Edited by: Biswajit Das on Jan 11, 2009 8:36 PM

    Hi bisjwat.
    In the tabpi u have table paremeters.
    In that u chave poitem type BAPIMEPOITEM.
    with in the BAPIMEPOITEM u have the field 'PREQ_NO'.
    this is the field for the po requistion number.
    I think it will solve u r problem.
    Thanks

  • How to create a via from layer 1 to 3 on a 8 layer PCB?

    I'm working on a design for a 8 layer PCB with Multisim/Ultiboard v10. In Multisim under sheet properties i selected the PCB to contain 8 layers, which makes Ultiboard to create this board with 4 layer pairs and 0 top/bottom build-ups. In the PCB properties of Ultiboard i enabled micro vias and buried/blind vias but i noticed that i'm not able to allow vias between some combinations of layers.
    For example i can enable vias from top to the second layer (1st inner) and from top to the fourth layer (3rd inner), but not from top to the third layer (2nd inner).
    When placing a via, i can select top for the start and the 3rd layer
    for the end, but it will be created as via between top and the 4th
    layer, which will -of course- shorten several traces on the 4th layer.
    So my questions is: Why am i not allowed to create a via, that goes from the top layer to the third layer and how to enable all possible combinations of start and ending layers for the via?
    Thanks for your help
    fhn
    PS: sorry for my bad english :/ 
    Message Edited by fhn on 08-22-2008 04:39 AM

    I am not 100% sure about this, but what I see happening here is that you can only select certain combinations of pairs. Once that selection is made it will gey out other selections as not valid. You might want to carefully look at the options in the via selection and make sure of which layers you want vias to be on. I don't know about enabling all layers in this selection. I would assume this would not be legal from a design rules standpoint, but since most of my boards are either single or double sided I do not have the necessary experience with multi-layers to give a proper answer to that.
    This is the only thing I can advise as when I went through the process I was able tio select the vias for the layers you outlined in your post.
    I hope this helps somewhat as this is all can tell you.
    Kittmaster's Component Database
    http://ni.kittmaster.com
    Have a Nice Day

  • Config settings to gray out "Reqted Qty" field while creating TO via LT03

    Hi Experts,
           Could anyone please me in this. I would like to gray out "Requested Quantity" field when creating TO via LT03 transaction. Can anyone please let me know where the config setting needs to be maintained inorder to gray out the "Requested Quantity" in LT03 transaction.
    Thanks for your help.
    Regards,
    Nagarjun

    Hi,
    no there is not such a functionality.
    From a field settings perspective you may work at account group level, =>OBD2 or OVT0
    and/or at transaction type level => OB20
    With OB20 you can distinguish between creation and change.
    You may also react per authorisation. See F_KNA1_EAN. In that case you may gray out fields individually.
    BR
    Alain

  • Prob in activating a field in delivery while creating delivery via VL04

    hi thx i am also facing the same prob. this badi is working while creating deliveries via VL01N OR VL02N but if we are creating delivery via VL04 this badi is not working, can u please guide me.
    thanx in adv.

    In the Import parameter TECHN_CONTROL  one field called SENDER_SYSTEM is there, it takes the Logical System Name(Default will be Local System). Check whether it is defined or not. This can be viewed in SALE tranasction.
    Tcode SALE > Basic Setting>Logical System-->Assign Logical System to client.
    Here You check ur Client is assigned logical System Name or Not?
    Debug your program and check this value....
    It will resolve ur prob..

  • Creating Routings via LSMW

    Hi all,
    Can anyone give me some pointers when creating Routings via LSMW. I see there are two standard uploads in RCPTRA01 and RCPTRA02. However, the mapping structures seem to be different between the two.
    I need to add PRT's material assignments and long texts to the routing.
    Any help greatly appreciated.

    Hi,
    Use standard batch/Direct input : RCPTRA02
    Source Fields
            MATERIAL_ROUTING          Material
                PLNAL                          C(002)    Group Counter
                MATNR                          C(018)    Article Number
                WERKS                          C(004)    Site
                OPERATION_ROUTING         Operations
                    PLNAL                          C(002)    Group Counter
                    VORNR                          C(004)    Operation/Activity Number
                    STEUS                          C(004)    Control Key
                    ARBPL                          C(008)    Work center
                    WERKS                          C(004)    Site
                    LTXA1                          C(040)    Operation short text
                    MEINH                          C(003)    Quantity unit for operation (batch input)
                    BMSCH                          C(017)    Base quantity (Batch input)
                    LAR02                          C(006)    Activity Type
                    VGE02                          C(003)    Unit for the standard value (batch input)
                    VGW02                          C(011)    Standard Value (Batch Input)
                    LAR03                          C(006)    Activity Type
                    VGE03                          C(003)    Unit for the standard value (batch input)
                    VGW03                          C(011)    Standard Value (Batch Input)
                COMPONENT_ROUTING         Components
                    PLNAL                          C(002)    Group Counter
                    VORNR                          C(004)    Operation/Activity Number
                    POSNR                          C(004)    BOM Item Number
                    MATNR                          C(018)    Article Number
                    WERKS                          C(004)    Site
    Field Mapping and Rule
           RC271_DS                       Work center structure for direct input (for datasets)
               Fields
                   TCODE                        Transaction Code
                                       Rule :   Constant
                                       Code:    RC271_DS-TCODE = 'CA01'.
                   STTAG                        Character Field Length = 10
                                       Rule :   Constant
                                       Code:    RC271_DS-STTAG = '18.03.2014'.
                   AENNR                        Change Number
                   REVLV                        Revision Level
                   WERKS                        Site
                                       Rule :   Transfer (MOVE)
                                       Code:    RC271_DS-WERKS = MATERIAL_ROUTING-WERKS.
                   PROFIDNETZ                   Profile
                   PLNNR                        Key for Task List Group
                   PLNAL                        Group Counter
                                       Rule :   Transfer (MOVE)
                                       Code:    RC271_DS-PLNAL = MATERIAL_ROUTING-PLNAL.
                   STATU                        Status
                                       Rule :   Constant
                                       Code:    RC271_DS-STATU = '4'.
                   VAGRP                        Responsible Planner Group/Department
                                       Rule :   Constant
                                       Code:    RC271_DS-VAGRP = 'KD1'.
                   VBELN                        Sales Document
                   POSNR                        Character field of length 6
                   PSPNR                        Work Breakdown Structure Element (WBS Element)
    MAPL_DI_DS                     Assign routing to article for direct input (for datasets)
        Fields
            ACTTYP                       Processing type for objects to be imported
                                Code:    MAPL_DI_DS-ACTTYP = 'H'.
            MATNR                        Article Number
                                Rule :   Transfer (MOVE)
                                Code:    MAPL_DI_DS-MATNR = MATERIAL_ROUTING-MATNR.
            WERKS                        Site
                                Rule :   Transfer (MOVE)
                                Code:    MAPL_DI_DS-WERKS = MATERIAL_ROUTING-WERKS.
            PLNAL                        Group Counter
                                Rule :   Transfer (MOVE)
                                Code:    MAPL_DI_DS-PLNAL = MATERIAL_ROUTING-PLNAL.
            LIFNR                        Vendor Account Number
            KUNR                         Account Number of Customer
            SUCHFELD                     Search Field for Customer-Specific Task List Selection
            VBELN                        Sales Document
            POSNR                        Sales Document Line Item (Batch Input Field)
            PSPNR                        Work Breakdown Structure Element (WBS Element)
    PLKO_DI_DS                     Header structure for direct input (for datasets)
        Fields
            ACTTYP                       Processing type for objects to be imported
                                Code:    PLKO_DI_DS-ACTTYP = 'H'.
            PLNAL                        Group Counter
                                Rule :   Transfer (MOVE)
                                Code:    PLKO_DI_DS-PLNAL = MATERIAL_ROUTING-PLNAL.
            VERWE                        Use by user or system
                                Rule :   Constant
                                Code:    PLKO_DI_DS-VERWE = '1'.
            WERKS                        Site
                                Rule :   Transfer (MOVE)
                                Code:    PLKO_DI_DS-WERKS = MATERIAL_ROUTING-WERKS.
            STATU                        Status
                                Rule :   Constant
                                Code:    PLKO_DI_DS-STATU = '4'.
            PLNME                        Unit of measure for the task list (batch input)
                                Rule :   Constant
                                Code:    PLKO_DI_DS-PLNME = 'KG'.
            LOSVN                        From lot size (BTCI)
                                Rule :   Constant
                                Code:    PLKO_DI_DS-LOSVN = '0'.
            LOSBS                        To lot size (BTCI)
                                Rule :   Constant
                                Code:    PLKO_DI_DS-LOSBS = '999999999'.
            VAGRP                        Responsible planner group/department
                                Rule :   Constant
                                Code:    PLKO_DI_DS-VAGRP = 'KD1'.
            KTEXT                        Task list description
                                Rule :   Constant
                                Code:    PLKO_DI_DS-KTEXT = 'Article Routing'.
            TXTSP                        Single-Character Indicator
    PLPO_DI_DS                     Routing/item structure for direct input (for datasets)
        Fields
            ACTTYP                       Processing type for objects to be imported
                                Code:    PLPO_DI_DS-ACTTYP = 'H'.
            PLNAL                        Group Counter
                                Rule :   Transfer (MOVE)
                                Code:    PLPO_DI_DS-PLNAL = OPERATION_ROUTING-PLNAL.
            PLNFL                        Sequence
                                Rule :   Constant
                                Code:    PLPO_DI_DS-PLNFL = '000000'.
            VORKN                        Node number (batch input)
            VORNR                        Operation/Activity Number
                                Rule :   Transfer (MOVE)
                                Code:    PLPO_DI_DS-VORNR = OPERATION_ROUTING-VORNR.
            UVOKN                        Node number (batch input)
            UVORN                        Suboperation
            STEUS                        Control key
                                Rule :   Transfer (MOVE)
                                Code:    PLPO_DI_DS-STEUS = OPERATION_ROUTING-STEUS.
            ARBID                        Object ID (batch input)
            OBJTY                        Object types of the CIM resource
            ARBPL                        Work center
                                Rule :   Transfer (MOVE)
                                Code:    PLPO_DI_DS-ARBPL = OPERATION_ROUTING-ARBPL.
            WERKS                        Site
                                Rule :   Transfer (MOVE)
                                Code:    PLPO_DI_DS-WERKS = OPERATION_ROUTING-WERKS.
            KTSCH                        Standard text key
            LTXA1                        Operation short text
                                Rule :   Transfer (MOVE)
                                Code:    PLPO_DI_DS-LTXA1 = OPERATION_ROUTING-LTXA1.
    MEINH                        Quantity unit for operation (batch input)
                        Rule :   Transfer (MOVE)
                        Code:    PLPO_DI_DS-MEINH = OPERATION_ROUTING-MEINH.
    UMREN                        Denominator for conversion from unit to base unit (BTCI)
                        Rule :   Constant
                        Code:    PLPO_DI_DS-UMREN = '1'.
    UMREZ                        Numerator for converting from unit to base unit (BTCI)
                        Rule :   Constant
                        Code:    PLPO_DI_DS-UMREZ = '1'.
    BMSCH                        Base quantity (Batch input)
                        Rule :   Transfer (MOVE)
                        Code:    PLPO_DI_DS-BMSCH = OPERATION_ROUTING-BMSCH.
    ZMERH                        Break time (batch input)
    ZEIER                        Unit for break time (batch input)
    LAR01                        Activity Type
    VGE01                        Unit for the standard value (batch input)
    VGW01                        Standard Value (Batch Input)
    LAR02                        Activity Type
    VGE02                        Unit for the standard value (batch input)
                        Rule :   Transfer (MOVE)
                        Code:    PLPO_DI_DS-VGE02 = OPERATION_ROUTING-VGE02.
    VGW02                        Standard Value (Batch Input)
                        Rule :   Transfer (MOVE)
                        Code:    PLPO_DI_DS-VGW02 = OPERATION_ROUTING-VGW02.
    LAR03                        Activity Type
    VGE03                        Unit for the standard value (batch input)
                        Rule :   Transfer (MOVE)
                        Code:    PLPO_DI_DS-VGE03 = OPERATION_ROUTING-VGE03.
    VGW03                        Standard Value (Batch Input)
                        Rule :   Transfer (MOVE)
                        Code:    PLPO_DI_DS-VGW03 = OPERATION_ROUTING-VGW03.
    PLMZ_DI_DS                     Article component allocation for direct input(for datasets)
        Fields
            ACTTYP                       Processing type for objects to be imported
                                Rule :   Constant
                                Code:    PLMZ_DI_DS-ACTTYP = 'H'.
            PLNAL                        Group Counter
                                Rule :   Transfer (MOVE)
                                Code:    PLMZ_DI_DS-PLNAL = COMPONENT_ROUTING-PLNAL.
            PLNFL                        Sequence
                                Rule :   Constant
                                Code:    PLMZ_DI_DS-PLNFL = '000000'.
            PLNKN                        Node number (batch input)
            VORNR                        Operation/Activity Number
                                Rule :   Transfer (MOVE)
                                Code:    PLMZ_DI_DS-VORNR = COMPONENT_ROUTING-VORNR.
            STLTY                        BOM category
                                Rule :   Constant
                                Code:    PLMZ_DI_DS-STLTY = 'M'.
            STLNR                        Bill of material
                                Rule :   Constant
                                Code:    PLMZ_DI_DS-STLNR = '00000005'.
            STLAL                        Alternative BOM
                                Rule :   Constant
                                Code:    PLMZ_DI_DS-STLAL = '01'.
            STLKN                        Node number (batch input)
            POSNR                        BOM Item Number
                                Rule :   Transfer (MOVE)
                                Code:    PLMZ_DI_DS-POSNR = COMPONENT_ROUTING-POSNR.
    WERKS                        Site
                        Rule :   Transfer (MOVE)
                        Code:    PLMZ_DI_DS-WERKS = COMPONENT_ROUTING-WERKS.
    BOMAT                        Article Number
                        Rule :   Transfer (MOVE)
                        Code:    PLMZ_DI_DS-BOMAT = COMPONENT_ROUTING-MATNR.
    STLST                        Order level
    STLWG                        Order path
    STLTY_W                      BOM category
                        Rule :   Constant
                        Code:    PLMZ_DI_DS-STLTY_W = 'M'.
    STLNR_W                      Bill of material
                        Rule :   Constant
                        Code:    PLMZ_DI_DS-STLNR_W = '00000005'.
    STLAL_W                      Alternative BOM
                        Rule :   Constant
                        Code:    PLMZ_DI_DS-STLAL_W = '01'.
    Map the extra fields according to your requirement. Hope you'll find the code helpful.

  • Encounter error message 61062 when create PR via ME51

    Dear Consultant,
    I encountered error message 61062 - "dd.01.2011 date comes after end of valid factory calendar. (Pls correct)" when create PR via transaction ME51. Although I have changed the Delivery date to "31.12.2010", system still issue error message. FYI, material that I used to create PR has planned delivery time = 185 days (pre-configured by our purchaser via Purchasing info.record) which is equivalent to dd.01.2011. Our factory calendar is configured valid up to Year 2010 and the new year (2011) will only be configured at end of December.
    If using transaction ME51N to create PR for the mentioned material above (with delivery date entered as 31.12.2010), there is no error message being issued by the system. May I know is there any solution to transaction ME51?
    Pls advise asap.
    Thanks & regards,
    LOI

    >
    LOI wrote:
    > May I know if there Is any effect for other modules like PP/PM on changing plant calender to 2011?
    yes, a positive effect, you will not receive error messages because of missing calender anymore.
    I have my calendars maintained until 2015
    ME51N only takes an info record into account when you do source determination, without source determination, the planned delivery time from material master is taken.

  • I have a problem when I create message via t-code notif_create.

    when I create message via 'notif_create',I can't fill the blank 'Component'.How can I get the 'Component'?

    Hi Liu,
    the F4 option is available for the component blank and we can select from them generally.ALso check the following SAP Notes...which may prove useful..Note 813075 - DSWP: Create Support Desk message missing category field
    Note 857793 - Determine system context for messages
    Note 853597 - Sorted display of F4 helps in NOTIF_CREATE
    Hope it helps.
    Br
    Sri
    Award points for helpful answers

  • Create shortcut via batch loader or other API

    Does anyone know whether it is possible (and if so, how) to create shortcuts via batch loader?
    If this is not possible, is there an API which could do this?
    I will need to create a lot of shortcuts, so am looking for a way to do this in bulk, i.e. programmatically.
    Thanks,
    -paul

    (Please excuse if there is any mistakes. this is my first post)
    If you are using the FDM's Task manager for the Batch loading, Just have a lookinto that Script whcih you have scheduled for the Batch process. you will find below row in the script.
    Set BATCHENG.PcolFiles = BATCHENG.fFileCollectionCreate(CStr(strDelimiter))
    BATCHENG.mFileCollectionProcess BATCHENG.PcolFiles, CLng(lngProcessLevel), ,CBool(blnAutoMapCorrect)
    Assume you are loading Sigle file from "OpenBatch" folderwhen ever scheduler executes the script. If so replace the above as below.
    Set BATCHENG.PcolFiles = BATCHENG.fFileCollectionCreate(CStr(strDelimiter), File1)
    BATCHENG.mFileCollectionProcess BATCHENG.PcolFiles, CLng(lngProcessLevel), ,CBool(blnAutoMapCorrect)
    Where File1 = Path for the file name to be loaded. So that file will not be moved from the "OpenBatch" folder. then you can append below VB script to the existing script to rename the file name.
    Set FSO1 = CreateObject("Scripting.FileSystemObject")
    Set File1= FSO1.GetFile("<File Path>")
    File1.move ("New path")
    Where "File Path" = FDM Directory\FDM Application\Inbox\Batches\Openbatch\1_LocationA_WLACTUALS_Nov-2009_RR.txt
    "New Path" = FDM Directory\FDM Application\Inbox\Batches\Openbatch\1_LocationB_WLACTUALS_Nov-2009_RR.txt
    and use the Batch processing script Again.
    Set BATCHENG.PcolFiles = BATCHENG.fFileCollectionCreate(CStr(strDelimiter), File2)
    BATCHENG.mFileCollectionProcess BATCHENG.PcolFiles, CLng(lngProcessLevel), ,CBool(blnAutoMapCorrect)
    Here File2 is the path for new file (LocationB.)
    So that, You can get the Single file from the Source system and you can load to two locations at a time with in the Single execution of the script. and Also make sure to write a script to copy the new file from "OpenBatch" folder to backup location like Inbox or as required as this script will not move the file from the "OpenBatch" directory. (Move script as same as mentioned above)
    Reply me if you have any doubts....

  • Create users via the CLI interface on a SX20

    Hi 
    Are there some who know how to create users via the CLI interface on a SX20. You can do this via the web interface but I have many video installations where I need to create a user account. Therefore, it would be easiest if I can make it through the CLI interface. 
    Best regards 
    Jesper

    Unless there's a very well hidden command somewhere, then no. As far as I know, this can only be done for the remote supportuser account;
    xcommand UserManagement ?
    xCommand UserManagement RemoteSupportUser Create
        ExpiryDays: <1..31>
    xCommand UserManagement RemoteSupportUser Delete
    xCommand UserManagement RemoteSupportUser DisablePermanently
        Confirm(r): <Yes>
    xCommand UserManagement RemoteSupportUser GetState
    /jens
    Please rate replies and mark question(s) as "answered" if applicable.

  • Unable to create Organization via amConsole

    Hi I am unable to create Organization via amConsole, I log in as amAdmin and it has role of Top-Level Admin and has Full Access.
    I am able to create users , Groups and other stuff, but Adding new Organization or Modifyin Organization fails, what could be the reason?

    This is debug message in amSDK:
    DataLayer.addEntry retry: 0
    03/30/2007 12:13:48:261 PM EST: Thread[service-j2ee,5,main]
    WARNING: Exception in DataLayer.addEntry for DN: o=zxvzxcxzz,dc=xyz,dc=com
    netscape.ldap.LDAPException: error result (65); Object class violation
    at netscape.ldap.LDAPConnection.checkMsg(LDAPConnection.java:4866)
    at netscape.ldap.LDAPConnection.add(LDAPConnection.java:2851)
    at netscape.ldap.LDAPConnection.add(LDAPConnection.java:2866)
    at netscape.ldap.LDAPConnection.add(LDAPConnection.java:2816)
    at com.iplanet.ums.DataLayer.addEntry(DataLayer.java:443)
    at com.iplanet.ums.PersistentObject.addChild(PersistentObject.java:722)
    at com.iplanet.am.sdk.ldap.DirectoryManager.createOrganization(DirectoryManager.java:1209)
    at com.iplanet.am.sdk.ldap.DirectoryManager.createEntry(DirectoryManager.java:1532)
    at com.iplanet.am.sdk.AMDirectoryManager.createEntry(AMDirectoryManager.java:651)
    at com.iplanet.am.sdk.AMCacheManager.createEntry(AMCacheManager.java:337)
    at com.iplanet.am.sdk.AMObjectImpl.create(AMObjectImpl.java:1009)
    at com.iplanet.am.sdk.AMOrganizationImpl.createSubOrganizations(AMOrganizationImpl.java:137)
    at com.iplanet.am.console.user.model.UMCreateOrgModelImpl.createOrganization(UMCreateOrgModelImpl.java:223)
    at com.iplanet.am.console.user.UMCreateOrgViewBean.createOrg(UMCreateOrgViewBean.java:239)
    at com.iplanet.am.console.user.UMCreateOrgViewBean.handleBtnCreateRequest(UMCreateOrgViewBean.java:188)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.iplanet.jato.view.command.DefaultRequestHandlingCommand.execute(DefaultRequestHandlingCommand.java:183)
    at com.iplanet.jato.view.RequestHandlingViewBase.handleRequest(RequestHandlingViewBase.java:308)
    at com.iplanet.jato.view.ViewBeanBase.dispatchInvocation(ViewBeanBase.java:802)
    at com.iplanet.jato.view.ViewBeanBase.invokeRequestHandlerInternal(ViewBeanBase.java:740)
    at com.iplanet.jato.view.ViewBeanBase.invokeRequestHandler(ViewBeanBase.java:571)
    at com.iplanet.jato.ApplicationServletBase.dispatchRequest(ApplicationServletBase.java:957)
    at com.iplanet.jato.ApplicationServletBase.processRequest(ApplicationServletBase.java:615)
    at com.iplanet.jato.ApplicationServletBase.doPost(ApplicationServletBase.java:473)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:767)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
    at sun.reflect.GeneratedMethodAccessor75.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:249)
    at java.security.AccessController.doPrivileged(Native Method)
    at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
    at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:282)
    at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:165)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:257)
    at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
    at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:161)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:263)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
    at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:225)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:173)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:161)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:933)
    at com.sun.enterprise.web.connector.httpservice.HttpServiceProcessor.process(HttpServiceProcessor.java:226)
    at com.sun.enterprise.web.HttpServiceWebContainer.service(HttpServiceWebContainer.java:2071)
    03/30/2007 12:13:48:263 PM EST: Thread[service-j2ee,5,main]
    Invoking _ldapPool.close(conn) : LDAPConnection {ldap://dir1.xyz.com:389 ldapVersion:3 bindDN:"cn=puser,ou=DSAME Users,dc=xyz,dc=com"}
    03/30/2007 12:13:48:263 PM EST: Thread[service-j2ee,5,main]
    Released Connection : LDAPConnection {ldap://dir1.xyz.com:389 ldapVersion:3 bindDN:"cn=puser,ou=DSAME Users,dc=xyz,dc=com"}

  • How to transport Secondary Index, If I created it via DB02-directly on DB?

    Hi Experts,
    For curiosity, wuld like to know that,
    How to transport the Secondary Index, If I created it via DB02 i.e. directly on DB?
    thanq.

    Hi srikhar,
    1. How to transport the Secondary Index, If I created it via DB02 i.e. directly on DB?
    Now, There is no question of transport,
    bcos what u will transport.
    We can only transport objects which
    are created from r/3 data dictionary etc.
    regards,
    amit m.

  • DBI re-create reports via dbi designer

    DBI re-create reports via dbi designer
    I am trying to re-create the "revenue by cost center" report in DBI designer. This report is seeded from oracle, but I am re-creating so that I can know how to create custom report. I followed all the cookbooks, yet it does not re-create in the same way. Does anyone know I can get to re-create exactly. (Please proved docs, website, etc.)
    Thanks.

    Hi John,
    Unfortunately ADF does not provide support for reports. You can use though BI Publisher, Oracle reports or Jasper Reports.
    I have demoed this (using BI Publisher) during an Oracle Developers Day/Workshop that I have conducted some time ago. I have even created a post (http://antonis-antoniou.blogspot.com/2010/11/integrating-web-services-into-your-adf_23.html) on my blog with step-by-step instructions and the actual source code.
    Regards
    Antonis

  • Create MP via Powershell in SCOM 2012 SP1

    Is it possible to create MP via Powershell in SCOM 2012 SP1? If so, how?
    (New-SCOMManagementPack is unrecognized cmdlet) 

    $name="NewMP"
    $displayname="NewMP"
    $mpStore = New-Object Microsoft.EnterpriseManagement.Configuration.IO.ManagementPackFileStore
    $mp = New-Object Microsoft.EnterpriseManagement.Configuration.ManagementPack($name, $displayName, (New-Object Version(1, 0, 0,0)), $mpStore)
    import-scommanagementpack $mp

  • Error in R3 system when create the Goods receipt in EWM

    Dear EWM expert,
    I have an error in R3 system when I confirm the goods receipt in EWM for inbound delivery
    the error in SMQ2 is:
    PALLET is an auxiliary packaging material and cannot be used as pack.mate
    PALLET is a packaging matirial type VERP that I've create in in R3 and I have transfer via  cif it in EWM.
    We have the new EWM 7 and i check some OSS note for a programm error in transfering of pakaging material during the GR but they are available only for EWM 5 and they are not available for EWM 7.
    Could you explain me if this error coul be caused by some customising settings or by some master data field.
    Thank you in advance for your help.
    Best regards
    Alessandro
    Edited by: Alessandro Dapiaggi on Jan 29, 2009 5:11 PM

    Hi
    I am not sure of your problem since there may be quite a few reasons why this would happen. However just try one thing - change the Packing material category from "auxaliary packing material" to "packing material" in Define Packaging Material Types under logistics general--->HU Management ---> Basics for the packing material type you are using in VERP and then create a new packing material and try the inbound delivery. It may work
    Thanks
    DJ

Maybe you are looking for