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

Similar Messages

  • 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

  • Program to insert message types in transport

    Hi,
    Just wondering if there is any SAP standard program to insert message type in transport.I know there is program to include IDoc type and its segments in transport(Program RSEREPA3).I have lot of custom message types and I want some handy tool for it.
    Regards
    Nilesh

    Hope this is what you are looking for,
    Goto WE81 transaction in change mode.
    Select the message types you want to transport.
    Take the menu Table View -> Transport and give a transport request number.
    Thanks
    Vinod

  • Creating Message Type

    what are the possible way to create message type and how you link the message type with idoc type.
    Thanks in  Advance....

    Hi Senthil,
    There is a transaction code for link the message type to the idoc type using the T.code we82.
    There we can assign the our own message type and Idoctype (basic type) we can assign. If u want to extension the basic type we have the option and we must release it.
    ********rewords some points if it is helpful.
    Rgds,
    P.Naganjana Reddy

  • Bapi for creating message type in a sales order

    Hi, I am involved in a IS-MAM project for an italian company.
    I need to create or add a message output type in a sales order in a complex batch program. I thought to use a bapi technicality; in particular BAPI_ADMGMTSO_CHANGE in order to change the document.
    How can I create message type in the order? Can I use the same bapi or I need of an other one?
    thanks in advance for your help
    Lucia

    Can you please provide more information...

  • 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

  • Do we need to create message interfaces for idocs and rfcs thatare imported

    do we need to create message interfaces for idocs and rfcs thatare imported
    from sap server
    in scenarios from sap system to file or vice versa
    i knew that we need not create message types
    do we also skip creating message interfaces

    hi,
    you create an abstract message interface for IDOC only if you want to use
    them in a BPM (integration process)
    for more about IDOCs have a look at my book:
    <a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • Error when executing the program RBDMIDOC with Message type HRMD_ABA

    Hello All
    I finished the integration between CRM and HR
    Now I am able to replicate the employees and the organizations, but when I created a schedule job for the program RBDMIDOC and message type HRMD_ABA the system gives me warning and message: no data selected for distribution even if I try to run the program using SE38 I am getting the same error message
    I already activated the message type using BD50 and activated the Change pointers using BD61
    Regards
    Jacopo Fransoice

    us the program
    RHALEINI

  • 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

  • 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

  • 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

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

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

  • What is the Technical Reason for Creating Message Type

    Hi,
          Is there any particular reason to use Message Type. Already we are defining Data Type. Please give me some detailed explanations.
    Thanks in Advance.
    Thanks & Regards,
    Giridhar.C

    Hi Giri,
    SAP telling below reason why we are creating message type
    "A message type comprises a data type that describes the structure of a message. For technical reasons, a data type alone is not sufficient to describe the instance of a message: Data types are defined in XML Schema as abstract types that are not yet tied to an element. You can only describe an instance of a message when you have specified a data type as an element type. Therefore, a message type defines the root element of a message"
    Regards,
    Raj

Maybe you are looking for