Regarding WHSORD message type in IDOC

Hi ALL,
Please let me know the following things if any one work on IDoc - DELVRY03 and Message Type - WHSORD.
Requirement is when you create a Outbound delivery in SAP if the delivery type is 'NL', Idoc has to create.
1) What are the Process code and message type ( In NACE, we called as output type ) for WHSORD in Partner profiles ( WE20 ).
2) At the time of creating deliveries in SAP, i have to check few conditions, if those are success then only i have to create IDOC else cancel the creation of IDoc. For this requirement what is the procedure.
3) Based on user requirements i have to change the 'Plant' ( E1EDL24-werks ) for this where i have to write the logic, means if it has to done throught user-exit please let me know the user-exit name.
Thanks & Regards
K. Naveen Kumar

Hi Naveen,
1) You can all the Process codes in WE42
2) You can do checks in BD64 (Filed level filtering)
3) you can write the conversion rules using BD55,BD79.
   ( else userexit)
Thanks
Eswar

Similar Messages

  • Regarding the Message Type and IDOCS related to IS-Banking

    Hi Gurus,
    can any one provide me the Message Type and IDOCs related to IS-Banking.
    Regards.
    Kiran kumar.

    Hi,
    Refer this link,
    http://www.stylusstudio.com/edifact/d04b/BANSTA.htm
    Hope it helps you.

  • What is inbound XML message type and idoc type in Purchase Order response

    Hi ,
    We are on SRM 7 ECS , support pack SAPKIBKV08.
    We have a process in which vendor will send a Purchase Order response  which will be
    converted to XML format by a middleware. This XML message will come to
    SRM and post a POR. I want to do the EDI mapping for this XML message,
    but there is no message type and idoc type in SRM for Purchase Order
    response. How do I map my message type in SRM to the vendor sent fields
    in middleware .
    Please advise
    Rgds
    Sumendra

    Hi,
    You can process with XML without IDoc.
    Vendor->  (XML) -> PI -> (XML) -> SRM.
    Please check PurchaseOrderConfirmation_In in namespace "http://sap.com/xi/SRM/Procurement/Global".
    http://esworkplace.sap.com
    Regards,
    Masa

  • Message types and idoc types

    hi,
         i need the list of message types and idoc types for edi.
          can any one of u pls send it.

    Hi,
    Check the OSS notes 104606.
    The following list maps the logical messages and IDoc types to the corresponding ANSI X12 transaction sets.That is, the logical message can be copied to the transaction sets named.
    204 Motor carrier shipment information
               The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
    214 Transportation carrier shipment status message
               The logical message is TRXSTA, the IDoc type TRXSTA01. Inbound processing is supported.
    304 Shipping instructions
               The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
    810 Invoice or billing document (also 880)
               The logical message is INVOIC, the IDoc type INVOIC01.
    812 Credit and debit advice
               The logical messages are CREADV or DEBADV, the IDoc types PEXR2001 and PEXR2002.
    820 Payment order and credit advice
               For the payment order, the logical message is PAYEXT (REMADV), the IDoc types PEXR2001 and PEXR2002.
               For the credit advice (ERS - Evaluated Receipt Settlement), the logical message is GSVERF, the IDoc type GSVERF01.
    823 Lockbox
               The logical message is LOCKBX, the IDoc type FINSTA01. Inbound processing is supported.
    830 Delivery schedule (LAB)
               The logic message is DELINS (from the EDI standard ODETTE) or DELFOR the IDOC type DELFOR01.
    832 Price catalog (also 879, 888, 889)
               The logical message is PRICAT, the IDoc type PRICAT01. Outbound processing is supported.
    834 Benefit enrollment and maintenance
               The logical message is BENREP, the IDoc type BENEFIT1. Outbound processing is supported.
    840 Request
               The logical message is REQOTE, the IDoc types ORDERS01 to ORDERS04.
    843 Quotation
               The logical message is QUOTES, the IDoc types ORDERS01 to ORDERS04.Outbound processing is supported.
    850 Purchase order or order (also 875)
               The logical message is ORDERS, the IDoc types ORDERS01 to ORDERS04.
    852 Stock and sale data
               The logical message is PROACT, the IDoc type PROACT01.
    855 Order confirmation (also 865)
               The logical message is ORDRSP, the IDoc types ORDERS01 to ORDERS04.
    856 Transport and shipping notification (ASN - Advanced Ship Notification)
               For transport in the SAP application, the logical message is SHPMNT or SHPADV, the IDoc types SHPMNT01 to SHPMNT03.
               For the delivery in the SAP application, the logic message is DESADV, the IDoc types DESADV01 (to be discontinued), DELVRY01 and DELVRY02.
    860 Ordering modification (also 876)
               The logical message is ORDCHG, the IDoc types ORDERS01 to ORDERS04.
    861 Credit advice (ERS - Evaluated Receipt Settlement)
               The logical message is GSVERF, the IDoc type GSVERF01.
    862 Delivery schedule (FAB)
               The logic message is DELINS (from the EDI standard ODETTE) or DELJIT, the IDOC type DELFOR01.
    864 Text message
               The logical message is TXTRAW, the IDoc type TXTRAW01. Inbound processing is supported.
    940 Shipping order and stock order
               The logical message is SHPORD or WHSORD, the IDOC type DELVRY01.
    945 Shipping confirmation and stock confirmation
               The logical message is SHPCON or WHSCON, the IDoc type DELVRY01.
    997 Functional acknowledgment
               This is a technical confirmation. This is not exchanged via an individual message but the status report for IDoc processing. The status values used are:
               "22" Shipping OK, acknowledgment has yet to come
               "16" Functional acknowledgment positive
               "17" Functional acknowledgment negative
               The status values "14" and "15" are available for the Interchange Acknowledgment accordingly. Source code corrections
    Cheers
    VJ

  • Multiple message types for IDoc types

    Hi,
    can we assign multiple message types to IDoc Types?
    Is so How to make it
    Thanks in Advance....
    Regards
    Sravya

    Hi,
       For an IDOC Basic Type is the structure which defines the skeleton of the data transfer like what all fields can be present, how many times a field can appear, is it mandatory etc.
      A message type is a label used to identification.
    Message type come into picture because we can use the same IDOC basic type for any number of applications. So it becomes necessary that we need some other tag to identify & distinguish between all these. Message Type helps in this cause.
    Message type & Basic Type are linked in WE82.

  • Difference between message type and idoc type

    Hi
    difference between message type and idoc type
    Regards
    Rama

    Hi,
    Message Type:
    A message type represents the application message exchanged between R/3 systems and R/3 and an external system. A message type characterises the data sent across systems and relates to the structure of the data called an IDOC type.
    Diff. with IDOC type
    An IDoc type specifies the structure of the data.
    A message type specifies the meaning of the data
    Diff. b/w IDOC type and IDOC
    An IDoc type is the definition of a specific data structure.
    An IDoc is an actual instance of data based on an IDoc type. Therefore, there can be many IDocs created from a single IDoc type.
    Example:
    MATMAS is the message type and MATMAS05 is IDoc type for Material Master.
    Thanks,
    Shankar

  • Question on RSSEND message type - based idoc sent from R3 to BW

    Hi
        I am not sure whether this is the right forum for this question, but my question is related to data exchange between R3 and BW and hence thought would ask the question here.
    When data is extracted by BW - from R3, based on RSREQUST idoc , RSINFO is being passed based from R3 showing records passed back from R3, but I don't see RSSEND message type based idocs being sent back from R3.
    I would like to see the RSSEND message type based idocs being sent back so that I can open and browse the contents of these idocs to cross the data here with the target system - i.e BW.
    I have double checked outbound parameters in partner profiles in R3 - for RSSEND, it contains the right Z* idoc type , however I cannot see any RSSEND idoc being generated in R3 even though data is sent from R3 to BW.
    Any idea what I am missing here ?

    I dont think I understand what you are looking for , but in case you want to look for the IDOC in ECC and BI, follow these
    steps.
    In RSMO tranx --> menu -
    > environment ---> ALE management  --->  1 . Datawarehouse & 2. Source System.
    Thanks,
    Ravi.

  • Message type and idoc type

    hi all,
    i'm working on integration between sap and non sap.can anyone please tell me the message types and idoc types available for Funds Management and Project system modules.it will be of a great help,full points will be alloted imm.

    What data you want to send / receive.
    The site contains all message types which sap provides.
    You can select your release and check in FI .
    You can also check in tcode WE81 for available doc types .
    Some of them I found are
    GLCORE     Master data G/L accounts (CORE IDOC)
    GLFETC     Request G/L accounts
    GLM000     Test reduction GLMAST
    GLMAST     Master data G/L accounts (master IDOC)
    GLROLL     FI-GLX message type rollup
    Your requirement is not clear as to what you want to send / receive with IDOCS.
    Cheers

  • Message type and IDoc type to update a sales order

    I can create sales order at WE19 by the message type SALESORDER_CREATEFROMDAT2 and IDoc type SALESORDER_CREATEFROMDAT202 . Can I use the same message type and IDoc type to update a sales document (sales order) and also how can I do (I mean, which structures should I use; at E1BPSDHD1X - UPDATEFLAG what should I enter? Put an X to update a document or etsc?)? I enter the "E1BPSDHD1X - UPDATEFLAG" as X, "E1BP_SENDER - LOG_SYSTEM", "E1BPSDITM - ITM_NUMBER", " E1BPSDITM - MATERIAL", "E1BPPARNR - PARTN_ROLE", "E1BPPARNR - PARTN_NUMB" and "E1BPSCHDL - REQ_QTY". The sales order quantity is at "E1BPSCHDL - REQ_QTY" and it is the field that I want to update. When I look at the transaction code BD87, I see the status text as "Enter a document number between 0005000000 and 0005999999". I cannot update the order. How can I update it? Canybody explain me in a detailed manner?
    Thanks in advance....
    Edited by: Hikmet Akcali on Oct 21, 2009 4:00 PM

    At the IDoc type pop-up selection, there are 3 types. These are: ORD_ID01, ORDERS05 and /NFM/ORDERS05. SAP system component version is SAP ECC 6.0 . I choose ORD_ID01. There are structures EDI_Z1, EDI_Z3, EDI_Z5, EDI_Z9 and EDI_Z53. Where should I enter the number of the sales document to be updated? Also, which function module should I choose?
    Edited by: Hikmet Akcali on Oct 21, 2009 5:34 PM

  • Message type for idoc PROJECT01

    Hi ..
         How to send a PROJECT01 idoc from one r/3 to another or third party system.What is the message type for the idoc and what are the configurations required.
    Tharun

    Hi Tharun,
    The Message Type for the basic type PROJECT01 is PROJECT.
    Using this basic type u can send only project and wbs related Information using BAPI.
    For Configuration the steps are as mentioned below.
    1.Define Logical Systems in sender and receiver.(SALE)
    2.Assign Client to Logical system in the respective systems.(SALE)
    3.Create RFC Destination.(SM59)
    4.Create a distribution model .(BD64)
    5.Click on Add Bapi, specify your sender, receiver the Object name as <b>ProjectDefinition</b> and the select the Method of your interest.
    6.Generate Partner Profiles in the Sender System.
    7.Distribute the Model to the receiver.
    8.Generate Partner Profiles in the Receiver System.
    Hope this helps you..
    Let me know incase u have any questions.
    Thanks & Regards,
    Vanita

  • Incorrect message type in IDOC for Purchase order change

    Hi Gurus.
    Please advise on below.
    We have several purchase orders that are configured to trigger IDOC upon change. But accidentally, someone has deactiveted the automatic proposal of EDI message type for these Purchase orders which resulted to not transmitting purchase order change documents automatically.
    As a workaround, we have proposed to create EDI message manually during Purchase order change. But upon checking in tcode WE09, message type is ORDERS which is PO create instead if ORDCHG for purchase order change.
    Please kindly advice on why it is behaving like this for purchase orders with EDI message previously deactivated.
    Thanks in advance.
    Acel.
    To simulate.
    Create PO. go to messages, select EDI message then deactivate permanently. Save PO. Release PO if needed. Change PO. go to messages, EDI is not automatically proposed. create EDI message mamanually. Save PO. Release PO id needed. check tcode WE09, for PO create, no IDOC since it was deactivated permanently. For PO change, IDOC was triggered but with incorrect message type ORDERS instead of ORDCHG.

    Hi Acel,
    You will need to check the settings in transaction WE20 - You will be using a Partner Profile to determine the outbound message, either for each vendor or a generic one.
    on the outbound parameters, you will need to ensure that ORDCHG is set up as a message type. If not, add it, ensuring that you use the message ORDCHG, the basic type (or extension) that you are using, usually ORDERS05 and make sure that in message control, you have process code ME02 set up. This should enable the correct message type to be determined.
    Regards,
    Rob

  • Message type and IDoc type for PGI-GR?

    hi all,
    I have to send the PGI through ALE which have to create GR . So please mention the Message type , output type of message control and IDoc type?
    Thanks
    Vamshi

    Hi,
    The Idoc Types for Post Goods Issue are
    MBGMCR01 / MBGMCR02.
    Pls check the Message type in tcode WE82.
    For output type GOTO transaction NACE-->Application V2.
    hope this helps.
    Regards,
    Sharath
    Edited by: sharath on Jun 24, 2008 7:16 PM

  • Transaction/Program to create message type LIP076 Idocs

    Hi Idoc Experts,
    Can you please let me know the T-code/program to send MD61(weekly forecast) data thru the idocs.
    FYI- I am planning to use message type LIP076 with basic type SOPGEN01
    Example: BD14 T-code to send the Vendor master details thru idoc.
    I am looking for a similiar transaction/program, so that it will create LIP076 idocs with MD61 details.
    Thankyou,
    Ravi

    Hello Ravindran
    You can also check the documentation in the below path and when you execute it it takes you to transaction SXDA. I am not authorized in my system, may be you can check more detailed in your system about the transaction..
    SPRO -- > IMG --> Production --> Production planning --> Demand management --> tools --> Data transfer workbench: planned independent requirements.
    Regards,
    Thanga

  • Why message type if  idoc type or idoc is already there.

    Experts.
    this has been posted several times and i gone through so many threads but stil some confusion . So anyone can tell in simple terms what is the difference and why sap has given this two instead of one.
    Diff. with IDOC type
    An IDoc type specifies the structure of the data.
    A message type specifies the meaning of the data
    *****from the above statements , by seeing the name of the idoc type ex matmas01 also we ca n say that it is used for material data, then why message type matmas needed?

    Hi,
    Idoc type means combination of segements
    Message type means Combination of idoc type
                              or
    Message type mean combination of Idoc type + Extension idoc type( Custom segments added to idoc type)..
    Example:-
    If you want to fill the data to custom segment which is available at exension idoc ...
    then first check the message type then check basic idoc type then check it contains exetension idoc type ..then fill the segment
    Generally the communication occurs between system through message type...
    Prabhudas

  • Message type SHPCON, idoc type DELVRY01

    Hi SAP Gurus,
    I am using message type SHPCON and idoc type DELVRY01 with processing code DELV to post goods issue for a delivery note.
    I tried to simulate the inbound entry via WE19. I was not able to proceed with the posting because I encountered error 51 in idoc.
    Field EXIDV empty
    Field VHILM empty
    These fields are in E1EDL37 and E1EDL44 respectively, and referring to HU information in which we don't have.
    What I have filled up are the fields:
    E1EDL20-VBELN = DO num
    E1EDL20-VSTEL = Plant
    E1EDL18-QUALF = "PGI"
    E1ADRM1-PARTNER_Q = "WE"
    E1ADRM1-PARTNER_IQ = recv plant
    E1EDTH13-QUALF = "015"
    E1EDTH13-NTANF = date today
    E1EDL24-POSNR = 000010
    E1EDL24-MATNR = material num
    E1EDL24-WERKS = delv plant
    E1EDL24-LGORT = sloc
    E1EDL24-LFIMG = quantity
    E1EDL24-VRKME = unit
    E1EDL24-LGMNG = quantity
    E1EDL24-MEINS = unit
    May I know how to avoid this or if I missed some fields that resulted to this error ? Or am I using the wrong message type?

    Hari,
    I can definitely use WE19 to reprocess it. However my problem is the source of this information. If we implement this process, we would not know where to get this information since we don't use handling units. To add to this, the field VHILM that the system is asking is "packaging material" which we don't use and don;t have.
    How to get rid of these fields? In VL02N, there is no handling units when I click on the pack icon. Only the material and the quantity.
    Thanks.

Maybe you are looking for