Subcontract PO IDOCs

Hello Guru(s),
What's the difference between message types PORDCR and PORDCR1, and difference between all the IDOC types: PORDCR01, PORDCR02, ...PORDCR101, and PORDCR102?  Is there a way these different IDOC types can be compared side-by-side with the differences highlighted?
Need to send an outbound subtract PO to a CM (with the component listed).  Which message type, IDOC type, and process code should I use? 
Also, how to send over SubC PO cancellation?  With what message type, IDOC type and process code?   Found PORDCH and PORDCH1 but they are for PO changes, not cancellation.
Thanks,
Jocelyn

Hi Jocelyn,
Did you every solve this issue? Which IDOC type did you end up using?
Regards,
PB

Similar Messages

  • Message type for generating IDOC  for SUBCONTRACTING PURCHASE ORDER

    Hi All,
    I have to generate IDOC for PO creation or change .
    I am using IDOC_OUTPUT_ORDERS and IDOC_OUTPUT_ORDCHG.
    The messagetype.idoctype  I am using is  ORDERS. ORDERS05  and ORDCHG. ORDERS05.
    Now the confusion is regarding whether  this message type will work in case of SUBCONTRACTING PURCHASE ORDER as well ?
    As I have gone through some websites and came to know that I will have to use PORDCR1.PORDCR102 specially for subcontracting.
    And programs we need to use is BUS2012_ICH_R3 instead of  RSNASTED and Form Routine SEND_PORDCR1 instead of EDI_PROCESSING.
    Purchase Order Collaboration scenario - Not generating IDOC in ECC
    http://www.erpgenie.com/faq/edi_purchasing.htm    on this site question no  8.
    Subcontract PO IDOCs
    I hope your experience will help me .
    Please reply ASAP.
    Edited by: uttam27 on Dec 4, 2011 1:47 PM

    There is a generic function to create change pointers for all message typs - 'CHANGE_POINTERS_CREATE_DIRECT'.  This is triggered only if you configure your message type to create change pointers from BD50.
    Once you activate it do any change to orders you can see change pointer tables BDCPV filled. Then BD21 will read the changes and generated outbound idocs accordingly.

  • Posting Subsequent Adjustment (MB04) with idoc WMMBXY

    Hi,
    I need to receive goods movement from a supplier who does subcontracting with  idoc WMMBXY that contains wastes related to a specific PO. Tha waste quantities arrive at the end of production, so they're not related to a finished product quantity.
    I've tried with two positions, one for mvt 121, quantity 0 for the finished product and one for mvt 543, quantity xx for the component, but the system doesn't allow me to put null quantities.
    Then I've tried only with the second one, but the system blocks the post saying special stocks not supported.
    Have any of you tried this management and tell me which field must be filled and how or can suggest another one way to do this with idocs?
    Thank you very much for your suggestions
    Anna

    Ok, I've found where's the problem is.
    During the checks, the system can't correlate through line_id and parent_id the connection between finished product and its components.
    How can I indicate the relationship in the idoc?
    Here's the point in FM MB_CREATE_GOODS_MOVEMENT where the check is done:
    Analyze IMSEG for document structure and assign LINE_IDs if necessary
      CALL METHOD cl_mmim_line_id_manager=>analyze_mb_create
    Thanks again!

  • Post Subcontracting PO using IDOC WMMBID02

    Hello friends,
    I am trying to use IDOC WMMBID02 (Function module L_IDOC_INPUT_WMMBXY) for posting GR for subcontracting Purchase order.
    Error message I am getting is "Out Of the required quantity of material U252309XBC , 0.028 THD remain(s) open".
    Here U252309XBC is raw material provided to vendor for subcontracting.
    I am not getting this error when tried to post using MIGO. I have checked stocks at plants and sufficient quantity is available in batches.
    Can you please advice.
    regards,
    Parshuram

    Hi,
    Check the following links, they are helpful....
    http://www.****************/Tutorials/ALE/ALEMainPage.htm
    http://www.riyaz.net/sap/beginners-guide-to-ale-and-idocs-a-step-by-step-approach/18/
    Regards
    Shiva

  • Problem in creating Purchase order through Idoc

    Hi ABAPers,
    I am trying to post PO document through WE19 t-code using inbound function module BAPI_IDOC_INPUT1 which is calling BAPI_PO_CREATE1 internally.And i am getting below error messages.
    1. Characteristic  does not exist in operating concern AC01
    2. This function only possible for subcontracting items
    3. No instance of object type PurchaseOrder has been created. External reference
    passing data to IDOC:PORDCR102
    Header Segment : E1BPMEPOHEADER and E1BPMEPOHEADERX
    company code    0814
    doc_type            NB
    vendor                0000400001
    poprg-                EPRO
    pgroup               U01
    Item Segment : E1BPMEPOITEM and E1BPMEPOITEMX
    Item                  00010
    material             000000000000000263
    plant                 0374
    Qty                   22.000
    Delivery Segment E1BPMEPOSCHEDULE and E1BPMEPOSCHEDULEX
    Item                  00010
    Schedule line     0001
    delivery date      01.12.2008
    Qty                   22.000
    Note: i am able to create PO successfully, through SE37 by using FM BAPI_PO_CREATE1  with given above data.
    Please confirm me, what else i need to pass to post PO through WE19 t-code using inbound function module BAPI_IDOC_INPUT1.
    Please reply me ASAP.
    Thanks and Regards,
    Sekhar Raju.

    must be data format issue. when you use Function_module/BAPI from SAP GUI, convertion exit is applied automatically. hence data is converted to proper format & submited.

  • Help needed in Idoc To File Scenario

    Hi Experts,
    My scenario is Idoc to File.
    Here my job is to convert the purchase order idoc into xml file.
    In this there are three conditions.
                       converting the standard PO into xml file
    (ii)                 converting the PO with serial number  into xml file
    (iii)                converting the PO using serial number with subcontracting into xml file
    so what I feel is I need to create one scenario and based on the condition that particular PO will convert into xml file.
    Conditions:
                       if no condition is specified then it is standard PO first case
    (ii)                 if field tdline ne space then it is PO with serial number second case
    (iii)                if field pstyp eq 3 then it is PO using serial number with    subcontracting third case.
    Please guide how to do this scenario.
    IR:
    1)       how many data types I need to create
    2)       how many message types I need to create
    3)       how many message interfaces I need to create
    4)       how many message mappings I need to create
    5)       how many message interfaces I need to create
    ID:
    1)       how many receiver determinations I need to create
    2)       how many interface determinations I need create
    3)       how many receiver agreements I need to create
    And where to write the conditions at message mapping level or at receiver determination level.
    Kindly provide solution to every point.
    Regards,
    Venkat.

    1) if no condition is specified then it is standard PO first case
    2) if field tdline ne space then it is PO with serial number second case
    3) if field pstyp eq 3 then it is PO using serial number with subcontracting third case.
    you have to create
    1. outbound ( IDOC)
    2. 3 Inbound (same MT)
    create 3 mapping program each for 1 condition
    create 3 interface mappings
    ID:
    1 reveri BS.
    3 Interface determinations, so 3 receiver agrement.......
    you can put the condition on the mapping or in the condition tab of the interface determinations.

  • Suggestions Required While Doing Idoc To File Scenario

    Hi All,
    My scenario is Idoc To File. I have to take the  Purchase Order Idoc from system "A" and send it as a XML file to system"B".
    The problem here is, i have three types of PO Idoc's with different fields.
    1) Purchase Order (Fields : PO Number, date, vendor, material and quantity)
    2) Delivery with serial number ( Fields : delivery number, est date, vendor, material, serial and quantity)
    3) Delivery using serial number with subcontracting repair ( Fields :
    PO Number, date, vendor, material, serial and quantity).
    I have to convert all the above PO Idoc's into Xml file format and send it to system "B".
    Here i have three different Idocs one per Purchase Order , one per Delivery with serial number and one per  Delivery using serial number with subcontracting repair .
    My question is, shall i need to create three different scenario's for the above requirement or shall i create only one scenario with all the fileds in file structure.
    Is it possible by creating only scenario, to handle the above situation. If so where can i handle the conditions saying that the File Structure
    for Purchase Order  should be (With Fields : PO Number, date, vendor, material and quantity) ,
    for Delivery with serial number should be (With  Fields : delivery number, est date, vendor, material, serial and quantity) and 
    for  Delivery using serial number with subcontracting repair should be ( With  Fields : PO Number, date, vendor, material, serial and quantity).
    Please provide the solution for the above situation.
    And suggest me which is the best method to follow.
    Regards,
    Venkat.

    Prasad,
    My requirement is i will process only  one Idoc at a time either it may be Purchase order or Delivery with serial number or  Delivery using serial number with subcontracting repair . So no chance of multiple targets. For example
    First time i may process Idoc related to Purchase Order then at that time  only fields ( PO Number, date, vendor, material and quantity) should convert into  Xml file and pass it to system "B".
    Second time i may process Idoc related to Delivery with serial number then at that time  only fields ( delivery number, est date, vendor, material, serial and quantity)  should convert into  Xml file and pass it to system "B".
    Third time i may process Idoc related to Delivery using serial number with subcontracting repair then at that time  only fields ( PO Number, date, vendor, material, serial and quantity) should convert into  Xml file and pass it to system "B".
    In all the cases the target is same "B" system.
    I think now it is clear.
    Regards,
    Venkat.

  • Rejection of PO item with reason 06 - IDoc failure

    Hi,
    There is an IDoc failure with message: Rejection of PO item with reason 06.
    The user(supplier) wants to reject first line item of the Subcontracting PO and add a new line item instead with the right data.
    Please suggest.
    Regards,
    Akash Prekar

    Hi Dirk,
    You can actually use the BADI BBP_CREATE_PO_BACK to change the flag value before filling the PO Craetion BAPI interface parameters
    Sangeeta

  • Vmi (vendor managed)- subcontracting problem VMI_PO_CREATE_FROM_ORDRSP_VMI

    Hi can anybody help me to find a solution for my Problem with VMI_PO_CREATE_FROM_ORDRSP_VMI ?
    I need to create an order with ORDERS05 - Ordrsp idoc,
    but we recognized that it is only supported in the way to create positiontype 0 Normal order or positiontype 2 consignation...
    for my process it is necessary to create it with positiontype 3 subcontracting ...
    i tried to implement it like with consignation, but it seems as if the problem appears in BAPI_PO_CREATE.
    Has anybody an idea ??#
    Thanks for your help

    Hi,
    For those who will have the same problem  related to passing the subcontract fields
    The solution is to fill the table EXTENSIONIN : example :
    STRUCTURE VALUEPART1 VALUEPART2
    SERRU 1 00010
    DISUB_SOBKZ "Q" 00010
    DISUB_PSPNR "00000289" 00010
    If it is not working try :
    TYPES: BEGIN OF lty_ebelp,
    ebelp TYPE ebelp,
    END OF lty_ebelp.
    TYPES BEGIN OF lty_adsub.
    include TYPE lty_ebelp.
    include TYPE disub_mepoitem_data.
    TYPES END OF lty_adsub.
    TYPES BEGIN OF lty_adsubx.
    include TYPE lty_ebelp.
    include TYPE disub_mepoitem_datax.
    TYPES END OF lty_adsubx.
    DATA: ls_extensionin TYPE bapiparex,
    lt_extensionin TYPE STANDARD TABLE OF bapiparex,
    ls_adsub TYPE lty_adsub,
    ls_adsubx TYPE lty_adsubx.
    ls_adsub-ebelp = '00010'.
    ls_adsub-serru = '1'.
    ls_adsub-disub_sobkz = 'B'.
    ls_adsub-disub_pspnr = '00000289'.
    MOVE ls_adsub TO ls_extensionin-valuepart1.
    ls_extensionin-structure = cl_adsub_constants=>extin_po_struc.
    APPEND ls_extensionin TO lt_extensionin.
    ls_adsubx-ebelp = '00010'.
    ls_adsubx-serru = 'X'.
    ls_adsubx-disub_sobkz = 'X'.
    ls_adsubx-disub_pspnr = 'X'.
    MOVE ls_adsubx TO ls_extensionin-valuepart1.
    ls_extensionin-structure = cl_adsub_constants=>extin_po_strucx.
    APPEND ls_extensionin TO lt_extensionin.
    So data structure LT_EXTENSIONIN will be used when calling BAPI_PO_CREATE1.
    Note : The solution is explained in the SAP Note 1566153.

  • IDoc type for MD04

    Hello friends,
    I didn't find any IDoc type existing which is related to stock / requirements list (MD04).
    Anyone can help please?

    Hi Fatih,
    Please try the following:
    Stock/Requirements List IDoc
    Definition
    IDoc LOISTD01 is used to pass the stock/requirements list at the material-plant level. The external system needs to read through the IDoc and extract the information it needs. One IDoc includes all the information for one material-plant list.
    Structure
    E1MDSTL Master Material stock (MDSTA)
    E1PLSEL Master Material planning segment (MDPS)
    E1MDPSL Master Stock Demand List (MDPS)
    E1MDSTL
    Fields
    Format
    Length
    Description
    MATNR
    CHAR
    18
    Material number
    WERKS
    CHAR
    4
    Plant
    PLSCN
    NUMC
    3
    Planning scenario in long-term planning
    EINME
    CHAR
    15
    Restricted-use stock
    EISBE
    CHAR
    14
    Safety stock
    INSME
    CHAR
    15
    Stock in quality inspection
    KEINM
    CHAR
    15
    Restricted-use consignment stock
    KINSM
    CHAR
    15
    Consignment stock in quality inspection
    KLABS
    CHAR
    15
    Unrestricted use consignment stock
    KSPEM
    CHAR
    15
    Blocked consignment stock
    LABST
    CHAR
    15
    Valuated stock with unrestricted use
    RETME
    CHAR
    15
    Stock returns
    SPEME
    CHAR
    15
    Blocked stock
    TRAME
    CHAR
    15
    Stock in transit
    UMLMC
    CHAR
    15
    Stock in transfer
    E1PLSEL
    Fields
    Format
    Length
    Description
    PLAAB
    NUMC
    2
    Material requirements planning segment
    PLANR
    CHAR
    20
    Planning segment number
    KDAUF
    CHAR
    10
    Sales order number
    KDPOS
    NUMC
    6
    Item number in sales order
    LGORT
    CHAR
    4
    Storage location
    PSPEL
    CHAR
    24
    Internal project item number
    E1MDPSL
    Fields
    Format
    Length
    Description
    AUFVR
    CHAR
    10
    Source number for order
    BAUGR
    CHAR
    18
    Material number of higher-level assembly
    BESKZ
    CHAR
    1
    Procurement type
    DAT00
    DATS
    8
    Receipt/ Requirements date
    DAT01
    DATS
    8
    Delivery/order finish date
    DAT02
    DATS
    8
    Start/release date
    DEL12
    CHAR
    12
    MRP element number
    DELKZ
    CHAR
    2
    MRP element indicator
    DELET
    NUMC
    4
    Scheduling number planning element
    DELNR
    CHAR
    10
    MRP element number
    DELPS
    NUMC
    6
    MRP element item
    EINVR
    NUMC
    4
    Source schedule line number
    KDAUF
    CHAR
    10
    Sales order number
    KDPOS
    NUMC
    6
    Item number in sales order
    LGORT
    CHAR
    4
    Storage location
    MNG01
    CHAR
    15
    Quantity reserved or quantity required
    MNG02
    CHAR
    15
    Quantity in-transit
    PLUMI
    CHAR
    1
    Receipt/ issue indicator
    POSVR
    NUMC
    6
    Source item number
    PSPEL
    CHAR
    24
    Character field length 24
    SOBES
    CHAR
    1
    Special procurement type
    VERID
    CHAR
    4
    Production version
    VRFKZ
    CHAR
    1
    Availability indicator
    WEBAZ
    CHAR
    5
    R/2 table
    WRK02
    CHAR
    4
    Production plant in planned order
    KUNNR
    CHAR
    10
    Customer number
    AUART
    CHAR
    4
    Sales document type
    FIX01
    CHAR
    1
    Indicator: fixing lot size in planned order
    Fields with asterisks are only available in 3.1H. FIX01=u2019Xu2019 when the planned order is firmed.
    The most important field is DELKZ, which determines what type of MRP element is being dealt with for internal processing. The external system should use this flag to distinguish between the different MRP elements and extract the ones it needs.
    'AR' Dependent reservation
    'BA' Purchase requisition
    'BB' Provided material requirement
    'BE' Schedule order item
    'BP' Gross requirements planning
    'BR' Process order
    'CH' Batch requirements
    'FE' Production order
    'FH' End of planning time fence
    'IM' Actual goods receipt quantity
    'KB' Individual customer stock
    'KD' Customer independent requirements
    'LA' Shipping notification
    'LB' Batch/warehouse stock
    'LC' Batch/warehouse stock
    'LE' Delivery schedule
    'MB' Material issues
    'MR' Reservation
    'NE' Collective order
    'PA' Planned order
    'PB' Project stock
    'PP' Planned independent requirements
    'PR' Forecast requirements
    'QM' Inspection lot for quality management
    'S2' Simulated requirements from availability check
    'SA' Simulation order
    'SB' Dependent requirements
    'SI' Simulation requirements
    'SM' Simulation dependent requirements
    'TB' Transfer requirements WMS
    'U2' Release order for a stock transfer requisition
    'U3' Transfer requirements for simulation order
    'U4' Release order for stock transport scheduling agreement
    'UB' Unplanned requirements
    'UL' Reservation in another plant
    'UR' Stock transfer reservation
    'VA' RFQ
    'VB' Quotation
    'VC' Order
    'VE' Scheduling agreement
    'MS' Direct production
    'VG' Contract
    'VI' Delivery w/o charge
    'VJ' Delivery
    'VP' Planned independent requirements
    'VW' External sales order
    'WA' Goods issue
    'WB' Plant stock
    'WE' Goods receipt
    'WH' End replenishment period
    'VF' Scheduling agreement
    'KK' Consignment stock for customer (availability check)
    'VT' Returns (availability check)
    'E1' Subcontracting purchasing
    'RP' Returns item
    When goods are issued at the supplying plant for a stock transport order, the order is termed in-transit until the goods are received at the destination plant. The stock/requirements list at the supplying plant no longer includes this order, but it remains in the stock/requirements list of the destination plant with E1MDPSL-DELKZ = u2018U1u2019. When IDoc LOISTD is created, the in-transit quantity is written into E1MDPSL-MNG02, and quantity listed in MNG01 is the original requested quantity.
    There are several date fields in the segment E1MDPSL. DAT01 records the stock available date, which takes the GR processing time into account. DAT02 contains the order finish date for a planned order and delivery date for a requisition. DAT03 contains the production start date for internally-produced material and release date for externally-procured material.
    When the aggregation feature of the program RMCPAMRP is selected, sales orders will aggregate per customer per day at material-plant level. Sales order numbers are suppressed.
    Hope it helps!
    Thanks!
    Preethi

  • Batch determination in MIGO of subcontracting orders

    Hi guys,
    We are using batch determination for raw materials and internal batch will be assigned at the time of Goods REceipts.  This particular material will be sent to subcontracting  vendor for producing another end-product.  While doing transfer posting of this item, we have given the batch no also.
    While doing MIGO for the end-product against the subcontracting order, the system should consume the raw material with 543 movement.  While doing this, the batch no has to be selected automatically from the transfer posting document.  But it is  not picked up automatically and we are giving the batch no while doing MIGO for the end-product.  Can we get the batch no from the transfer posting document directly. 
    Do we need to do any config settings for this?
    Please suggest me the solution
    Thanks in advance

    A Question here - can automatic batch determination trigger at MIGO? Since we only set it up for :
    > Automatic Batch Determination for Sales Order Items
    > Activate Automatic Batch Determination for Delivery Item Cat
    I have an external warehouse system with no batch management. I also have an external sales system interfaced with SAP. Hence no sales documents in SAP - just inventory and FI postings. When I will be posting inventory (iDoc) from this external WM and Sales system to SAP - can I trigger an automatic batch determination in order to post inventory with batch????
    BONUS POINTS FOR ANSWER!

  • Logical System in IDOC-XI scenario

    Hi,
         I need help to understand few things in IDOC-XI scenario, could any one help me in this regard.
        we use Adapter specific identifiers to map services, we have following type of identifiers 1) Sys.ID & Client No.  2) Logical System. 
    my questions are
    a) Are we use Logical System in B to B scenario ?
    b) Are we use LS in reference to the SAP system or Non SAP system ? if a non SAP system....how a non SAP system send an IDOC and why a non SAP system receive an IDOC ( conversion is possible in XI ) ?
    Thanks and Regards
    Mahesh.

    Hay Kumar,
    Logical systems can also be used for SAp sytems wich are not installed yet as a virtuall placeholder.
    a) yes. if on of your business is a non sap system or a propritery system that you developed yuo'll ue LS.
    b) non SAP system can send and recieve IDOCs. so it's possiable to get an IDOC from a system and turn it into an RFC for SAP or get an IDOC from an SAP system and then turn it into something else for another system.
    Have a Good One,
    Uri Lifshitz.

  • IDoc not received in MII

    Hi All, 
    I am using SAP MII 12.1.5 Build 87. 
    I am facing problem with iDoc Listner we have configured iDoc Listner properly in SAP ERP, SAP NW and in SAP MII. 
    We are able to send iDoc from SAP but we are not able to receive same in MII. 
    Port and iDoc Server is giving status connected previously it was working fine in SAP MII 12.1.5 Build 83. 
    Following are the log details for SAP MII Logger as well as SAP NW Log. 
    SAP NW Log: 
    Error processing JRA IDOC message  
    SAP MII Log: 
    Error processing JRA IDOC message  
    Error processing JRA IDOC message [server=xxx, client=xxx]  
    [EXCEPTION]
    java.lang.NullPointerException
    at com.sap.xmii.ejb.JRAListenerBean.onMessage(JRAListenerBean.java:130)
    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.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MessageListenerType.invoke(Interceptors_MessageListenerType.java:110)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Lock.invoke(Interceptors_Lock.java:21)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
    at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
    at com.sap.engine.services.ejb3.runtime.impl.MDBProxyInvocationHandler.invoke(MDBProxyInvocationHandler.java:77)
    at $Proxy943.onMessage(Unknown Source)
    at com.sap.mw.jco.jra.idoc.JRAIDocExtension$IDocMessageHandler.onMessage(JRAIDocExtension.java:72)
    at com.sap.mw.jco.jra.JRA$ReaderThread.sendDirectToMdb(JRA.java:6641)
    at com.sap.mw.jco.jra.JRA$ReaderThread.sendAsynchRequest(JRA.java:6601)
    at com.sap.mw.jco.jra.JRA$ReaderThread.handleRequest(JRA.java:6771)
    at com.sap.conn.jco.rt.DefaultServerWorker$RequestDispatcher.handleRequest(DefaultServerWorker.java:989)
    at com.sap.conn.jco.rt.DefaultServerWorker$RequestDispatcher.handleRequest(DefaultServerWorker.java:967)
    at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:142)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:2927)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2659)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2478)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2362)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2207)
    at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:259)
    at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:322)
    at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:220)
    at com.sap.mw.jco.jra.JRA$ReaderThread.run(JRA.java:7260)
    at com.sap.engine.services.connector.jca15.work.TaskImpl.run(TaskImpl.java:255)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
    at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
    Please help me out on this issue.                                         
    Regards,
    Manoj Bilthare
    Edited by: Manoj Bilthare on May 19, 2010 12:57 PM

    Hi Manoj,
    Once you have configured your Listener have you checked pressing the update button and i dont want to ask you which version of NW SP you have installed as you said it was working for you with Build 83, but nevertheless NW SP Level should not be not less than SP3.
    If this doesn't help you,please try  restarting your server again.
    How about the credential editor have you configured this as well?
    Regards,
    Sudhir Kumar
    Edited by: Sudhir Kumar Shambana on May 19, 2010 10:46 AM

  • Report for Material at subcontract AND PO number

    We are preparing for Inventory verification at subcontractors.
    My boss believes it would be easier for the SC vendor if we could supply the PO number for which the material was shipped.
    I haven't found such a report.  Is there one?
    If you know the tables and links, I can write a ABAP query
    Thank you for any help that can be provided.
    Althea

    Hi,
    ME2O works fine if you want to track which subcontracting PO's are still open and what is the current stock at vendor.
    ME2ON is another version of the same basic ME2O report.
    Try also MBLB - Stocks at subcontractor.
    As far as PO to 541 link is concerned, I do not think it is possible to find it unless there is some specific business process being followed which is supported by custom code.
    The reason is that when you issue against 541, you are simply providing materials to vendor that the vendor needs.
    There might be multiple open SC POs for same material/batch and there is no point in tracking against a particluar PO. Its the same material/batch the vendor receives.
    When you post a PGR for a SC PO, then the stock from vendor premises is consumed by 543 and the track to your SC PO is maintained.
    I tried maintaining EBELN as required in OMJJ for 541 but still no MSEG-EBELN is populated. Maybe I am missing something.

  • Open Sales orders through IDOC

    Hi
    We are trying to send the list of open sales orders of a customer in an IDOC to the customer. For example, if the customer has got 15 sales order to be delivered to him , he needs the details of all these 15 orders in an single IDOC
    Is there any IDOC message type available for this in SAP R/3 4.7 version  or is there a standard solution of sending these details through IDOC
    Regards
    Anandh

    Hi
    We are trying to send the list of open sales orders of a customer in an IDOC to the customer. For example, if the customer has got 15 sales order to be delivered to him , he needs the details of all these 15 orders in an single IDOC
    Is there any IDOC message type available for this in SAP R/3 4.7 version  or is there a standard solution of sending these details through IDOC
    Regards
    Anandh

Maybe you are looking for