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

Similar Messages

  • 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

  • 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 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

  • 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

  • Std Msg Type and Idoc Type to send multiple characteristics for equipment

    Hello Experts,
    I have the requirement to send all the assigned characteristics linked to an Equipment or linked to a Material, along with the all possible values BUT require only standard Message Type and Idoc Basic Type.
    I found Message Type = CHRMAS and Idoc Type = CHRMAS04, BUT it contain information of ONLY one characteristic, not solve my objective (multiple characteristics in one Idoc)
    Will you please provide me any standard Message Type and Idoc Basic Type that solve my above requirement?
    Thanks in advance,
    akg

    Hello Experts,
    Can you at least tell me, is there anything standrad that can fulfill my above requirement?
    If not then I will proceed with custom developments; and in this case is there any complexity to transmit the custom Idoc?
    Thanks in advance,
    Thanks & Regards
    akg

  • Basic type and idoc type

    hi iam having z-basic type how to find what is the standard idoc type(for ex MATMAS,Creamas) for that

    Step1. Go to WE30 and give the extended IDoc name
    Step2. Check the extension button and click on display
    Step3. Click on header button (Top 3rd left button)
    Step4. In Technical Attributes, you will get the name under "Linked Basic Type"
    Hope it solves your query...
    Regards,
    Prasoon Sahay
    Edited by: Prasoon Sahay on Sep 2, 2009 2:18 PM

  • Automatic "Shipping Type" and "Forwarding Agent" from Route to Sales Order

    Need some help...
    When creating a Sales Order, the field "Shipping type" (inside Shipping tab of the Item Level) and the Forwarding Agent (Partners tab) should be automatically get from the configuration made for the Route applied in the order, via SAP Standard Functionality.
    The Route is being automatically determined in the Sales Order and for this Route, there is a "Shipping Type" and a "Freight Agent" assigned.
    Thanks for the help!

    Hi Hrishi.
    Actually, those informations have to be available in the delivery.
    The idea is that the customer organizes all his operations (picking, packing, loading and tranportation processes) based on deliveries that will be transported by the same agent and using the same shipping type.
    As I assigned an agent and a shipping type in the route, I expected to get these values automatically in the Sales Order, and consequently in the delivery.
    Thanks for the help.
    Regards.

  • We57 link between logmessage and idoc type does not exist

    in we57
    i have fm idoc_input_pordcr
    basic type pordcr101
    message type pordcr
    when i try to save
    gives message link between log message pordcr and idoc type does not exist.
    will not let me save
    where do i go to link these up

    Hi,
    Transaction WE82, assign Idoc type to message type.
    Regards
    Vijaya

  • Project Revenue Plan Not Update from Sales Order Item

    I am generating a network and project from the sales order item using Assembly processing. I am using milestone billing on the sales order item and the milestones attached to the project network activities are appearing as billing blocks on the sales order item billing plan. However, the project revenue is not getting updated from the sales order billing plan. Can someone please help?
    I have deleted the billing plan on the billing WBS element and activated revenue planning update from sales order in cusomization for PS. I am looking at CNS41 under the project revenue sched in version 0. Is there a different report I should be looking at?
    Regards,
    Venkat.

    HI Venkat,
    You are looking at the correct report & I believe you have also done the necessary customization. If you create a sales order and reference it to a quotation, the related plan values in the WBS element are refreshed automatically.
    When the payment data is recorded, the terms of payment and the customer payment history are taken into consideration. One of the probable causes could be the credit limit of the customer might have been exceeded. Take help of your SD consultant & increase the credit limit for that customer (from the sales document), t-code FD32 if it is permitted in the business.
    After the new credit limit is set execute the following steps:
    u2022     Go to the t-code Change billing request (VA02)
    u2022     Open the required billing request
    u2022     Remove the account assignment of WBS element from each line item
    u2022     Save the billing request
    u2022     Reopen the billing request in change mode
    u2022     Reassign the WBS elements to all line items
    u2022     Now the changed credit limit will take affect
    u2022     Check the Planned Revenue for the said project in CNS41, it should get updated.
    Rgds
    Deepak

  • Posting goods issue using Message type SHPCON and idoc type DELVRY03

    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. The scenario should be posting goods issue based on the delivery order.
    In some cases, quantity issued is less than the quantity in the DO. For this, I need to change the delv quantity in the DO via VL02N before I select Post goods issue button. This will change at the same time post the goods issue.
    What I have filled up are the fields:
    E1EDL20-VBELN = DO num
    E1EDL20-VSTEL = Plant
    E1EDL18-QUALF = "PGI"
    E1EDTH13-QUALF = "006"
    E1EDTH13-NTANF = date today
    E1EDL24-POSNR = 000010
    E1EDL24-MATNR = material num
    E1EDL24-WERKS = delv plant
    E1EDL24-LGORT = sloc
    E1EDL24-LFIMG = updated quantity
    But everytime I simulate using WE19, the entire quantity in the DO is not changed at all. The goods issue quantity posted is still the original DO quantity.
    May I know how to do this? Thanks.

    Put value in E1EDL24-LGMNG for qty to pgi.

  • What is the message type and basic type used for catsdb in idoc help me

    what is the message type and basic type used for catsdb in idoc help me
    ANY IDOC FOR CATSDB PLEASE TELL,
    Regards,
    Jagrut BharatKumar Shukla
    points will be awarded

    Hi,
    Check these message types.
    ATT_ABS_WITH_COST and WORKSCHED_WITH_COST.

  • 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.

  • 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

Maybe you are looking for