Need Message Type Creation Steps for Different Scenarios

Hi Friends,
I have done following steps for Outbound IDoc [Extended IDoc]
1. Create custom Message Type                           WE81
2. Create custom Segments               WE31
3. Create IDoc Extension               WE30
4. Create IDoc Type [Basic+Extu2019n]          WE30
5. Link Custom IDoc with Message Type          WE82
6. Activate CP for Custom Message Type                     BD50
7. Activate Change Pointers globally Flag on     BD61
8. Maintain custom message type in CDM                     BD64
9. Define partner profile for custom msgtype                    WE20
After completion of the above steps.
I am unable to do the following steps.
10. Checking the IDoc Creation                          BD10
          or
11. Execute CP IDoc generation Program     RBDMIDOC
Here  these steps I am unable to find Message Type.
If we create message type thru BD53 [std idoc] it will come.
but my situation is for extended IDoc I need to create message type.
If any one worked on this situation Help me out.
Regards,
Mutyapu4u.
Edited by: naveen mutyapu on Jun 24, 2008 2:51 PM

Hi,
Check the link below:
http://www.****************/Tutorials/ALE/ALEMainPage.htm
Hope this helps..
Regards,
Sharath

Similar Messages

  • Need pdf file links for different scenarios

    Hi folks,
    I am new to PI.Please can any body provide me pdf file links for different scenarios like   File to File, File to JDBC,JDBC to File,File to RFC, RFC to File, File to IDOC, IDOC to File, Http to RFC, Web services to RFC, File to Mail,ABAP to ABAP proxy and  Java Proxies to JDBC.
    Thanks in advance.
    SAP XI/PI Moderator ****************
    Very Simple. Search SDN.
    Thread Locked.
    SAP XI/PI Moderator ****************
    Edited by: Aashish Sinha on Feb 21, 2012 1:36 PM

    hi chandra, do you have the pdf file for fi-ca configuration

  • I need output type NEU automaticaly for create purchase order document type

    Dear Experts,
    I need output type NEU automaticaly for create purchase order document type NB
    when transaction code MN04, I am doing the following:
    (1) I selected the third option Purchasing Output determination: Document type
    (2) I selected the output type NEU.
    (3) In condition records in document type , i have chosen NB.
    (4) In name its automatically coming as Purchase requisition
    Please suggest how Purchase Order NB will come

    Hi,
    Check & press F4, NB Purchase Order (for catagory F) will be there after entering PO output type NEU & then maintaion the condition record in MN04.
    Output type NEU automaticaly defaulted during purchase order creation with document type ,then just fine tune the output (message) type in following path:
    SPRO--->MM->Purchasing>Message>Output control->Message types> Define message type for Purchase Order----->Fine-Tuned Control: Purchase Order
    Now here select the check box corresponding to your output(message) type NEU to have print output automatically displayed & save.
    Now try to creating Purchase Order & you will have default message type NEU.
    Regards,
    Biju K

  • Why need message type when u create data type...

    why need message type when u create data type...

    Hi,
    A message type comprises a data type that describes the structure of a message. At the following points in SAP Exchange Infrastructure you can refer to the message to be exchanged at runtime by using the message type:
    ·        More than one message interface can use the same message type. For example, an asynchronous outbound message interface and an asynchronous inbound message interface can reference the same message type because the request message does not need to be mapped.
    ·        When defining a message mapping you can directly reference message types to map messages from an outbound interface to messages from a receiver interface.
    For technical reasons, a data type is not sufficient to describe the instance of a message. In XML schema, data types are defined as abstract types that are not yet fixed 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.
    A message type does not define the direction of the message exchange, in other words, whether it is a request or a response. In exceptional cases you can use the same message type for both the request and the response message.
    A message type has the following characteristics:
    ·        It comprises exactly one data type, which determines the content of the message to be transferred.
    ·        It is identified by a name and an XML namespace. The name (together with the namespace) of a message type is located in the uppermost tag of the message to be exchanged. This is an element tag.
    You have defined a message type GreetingRes that references a simple data type of type xsd:string. The XML namespace of the message type is http://sap.com/xi/myExample. The corresponding payload might look like this:
    <?xml version="1.0" encoding="utf-8" ?>
    <ns1:GreetingRes xmlns:ns1="http://sap.com/xi/myExample"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
       Hello Mrs. Miller
    </ns1:GreetingRes>
    You can specify how a message type is used in more detail in the description
    hope this will help you.
    regards
    Aashish Sinha
    PS : reward points if helpful

  • Documentation on Designing tips - for different scenarios

    Hi Gurus:
    Is there any good doc's for 'Designing tips - for different scenarios' like using Line Item Dimensions, aggregates, copying ODS to ODS, cube modelling, cache....
    The common scenarios we come across in real life..Of course I understand it varies from client to client
    Would really appreciate any help..
    Many thanks

    hi,
    there are docs in sdn forum may help, explore in business intelligence section, also service.sap.com/bi
    efficient infoprovider modeling
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/79f6d190-0201-0010-ec8b-810a969028ec
    aggregate
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3f66ba90-0201-0010-ac8d-b61d8fd9abe9
    cache
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/31b6b490-0201-0010-e4b6-a1523327025e
    hope this helps.

  • Which IDoc Type and Message Type to use for Credit Memo?

    Could you guys please tell me which IDoc type and Message Type to use for Credit Memo? Also if possible tell me the process code/ function module.
    Will certainly give points for right answer. Thank you for reading.

    Hi,
    You can use IDoc type FIDCCP02 with message type FIDCC1/FIDCC2 for Credit Memo.
    Also you can use this FM FI_IDOC_CREATE_FIDCC1/
    FI_IDOC_CREATE_FIDCC2 to generate the IDoc.
    Regards,
    Ferry Lianto

  • What message type to use for syndicating data back to R3 from XI

    What message type to use for syndicating data back to R3 from XI. It gives a Message type IDOC error code 51.

    Hi Rehman,
    You are getting error 51 which means "Error: Application document not posted".
    This might because of two reasons:
    1. Your IDoc doesn't contains all the mandatory fields required by the inbound function module to post the IDoc.
    2. You have assigned wrong inbound function module to post the IDoc.
    Please check these cases.
    Hope this will help you.
    Thanks,
    Shiv Prashant Dixit

  • Data Type, Message Type and Mapping for FTP

    Thanks in advance for your replies.
    As our first production XI scenario, we need to move several (at least 46) files from our SAP instance to a couple of different servers to support our legacy systems.  Once all locations are on SAP this requirement should go away.
    I only want to pick up the file from the one server and place it on the other and this leads me to some questions.
    How do I define the Data Type and Message Type for each of the files?   Do I need to consider the size of the record in each interface and create DT/MT with different sizes.
    Do I need a mapping program that simply maps one structure to the other?

    I recently completed a similar exercise.
    It looks like this...
    server1 ftp (Sender - delete file) - XI - Server2 ftp (receiver - create file).  This will move the file from one server to another.
    I used the same schema and mapped fields on a one to one basis.
    The Size of the files I process are between 6kb and 500kb each, but the mapping/fields remain constant, just the numebr of items change.
    Worked seemelessly for the last three weeks (since go-live)

  • Need an IDOC EDI STEPS for material document(MB03)

    HI ALL,
    i need an IDOC for material document. For example, user in SAP make material document (t-code MIGO or MB11), then automatical is downloading outbound IDOC, which contain information about material document.HOW TO PROCESS IT THROUGH EDI .GIVE THE STEPS.

    like below you can do your settings
    The EDI Configuration required to be done for Transfering IDoc to non SAP System is.
    1. First of all, we need to identify the Transaction Data which is required to be Transfered to external System.(Ex: Sales Order Data or Shipment Data or Delivery Related Data).
    2. Secondly, Identify the IDoc Type & Message Type. IDoc Type can be found in Transaction WE30 & Message Type Can be explored in Transaction WE81.
    3. After that, assign the IDoc Type to Message Type in WE82.
    4. Identify the Selection Program (Outbound) which is generally a Function Module in the Form of IDOC_OUTPUT_<Message Type>. Example, if the Message Type is ORDERS, the FM will be IDOC_OUTPUT_ORDERS.
    5. Assign the Function Module to a Process Code in WE41 (Process Code for Outbound).
    6. Configure Port Definitions in WE21 for which the RFC destinations are to be maintained in Transaction SM59.
    7. Maintain Partner Profiles for the Outbound Message Processing in WE20.
    8. Last, but not the Least, we need to Focus Mainly on Message Control Configuration which is nothing but maintaining the Output Type for the Outbound IDoc to be Triggered for the Sales Order Application or Delivery Application.
    i. In Message Control Configuration, we'll maintain
    a. Condition Tables
    b. Access Sequences
    c. Output Types
    ii. To Create the above elements, we can go to SPRO Transaction and do the same depending on the Application Area such as Sales / Shipping / Logistics Execution etc.
    iii. For Output Types & Access Sequences, we can go to the Transaction NACE or VK01 in which we'll maintain the Output Types / Access Sequences & Condition Records.
    Please note that all the above steps may not be needed if we are using some of the Standard Elements provided by SAP such as Message Type, Process Code, IDoc Type & Selection Program as many of the Standard SAP Applications have their own Elements for different Application Areas.
    For example, if you want to send an Order Confirmation IDoc when the Sales Order is saved, you can use the Message Type ORDRSP, IDoc Type ORDERS05 & Selection Program as IDOC_OUTPUT_ORDRSP.
    However, Message Control Configuration is the Key Factor and is required for all the Applications as per the Customer's / Client's Requirements.

  • Receiver Determination steps for BPM scenario

    Hi Experts,
    Scenario : SOAP -> Calling different webservices
    1. SOAP Client Request
    2. Call the Initial webserive to get the unique Id. No need to pass any request to call this webservice, but it will give the response.
    3. Take the Initial websrevice's response as a request to second webservice
    4. Pass the SOAP client request to Third webservice
    BPM steps
    1. Receive Step for SOAP Request
    2. Send Step for the Initial webservice call.
    3. Transformation step Initial webservice response to request change.
    4. Send Step for Second webservice (Pass the the Transformation step's target interface as a request)
    5. Send Step for Third webservice ( Pass SOAP client request)
    I am done with the BPM flow. Could you please help to do the Receiver Determination steps.
    Usually I follow the below steps.
    1. Sender Service to BPM
    2. BPM to other services. I have a doubt with the second step. I am not passing the SOAP client request to Initial webservice. So, please tell me how to proceed further for the BPM Receiver Determination steps..
    Thanks & Regards
    Sara

    Hey,
         First, what is th purpose of your SOAP client request.
    Is it just to trigger the BPM.
    Second on what basis are you fetching the unique Id from initial web service.
    If it is a normal scenario then, the reciever determination will be like this.
    Soap client-> BPM
    BPM->initial webservice
    BPM->second webservice
    BPM->third webservice
    but in this particular scenario i dont know which data is being used to fetch the unique Id.
    regards,
             Milan

  • IDOC Message type  ACC_DOCUMENT -  Same Client different company Code

    Hi guys ,
    I need your advice , I´m trying to create an IDOC to send my accounting  postings via IDOC from one company to other in the same client  , I did I think the whole process to achive that ,  meaning I went to tnx : SALE , SM59, WE21  but now in BD64 im facing the following problem  : in the message type box , i filled the fields like this :
    Model view       TEST                          
    Sender             GCQCLNT100                     
    Receiver           GCQCLNT100                     
    Message Type  ACC_DOCUMENT 
    but I got the error : Client and server must be different. !! , so I dont know what to do now ,  any advice ?  Im not sure if  I need a Distribution model for what I want to do ? or maybe i can´t send idocs in the same client ??
    thank you Guys.

    When I stored an IDOC with the IDOC_INBOUND_ASYNCHRONOUS  function, I believe I only had the receiver configured.
    I created the idoc table, control structure, etc., did the save with the FM above...then the receive side had a process code and standard FM....

  • How to main the message type is I for the exceptions when we create the FM

    HI ,
    I have created one FM.in that i need to maintain the exceptions. for handling the exceptions message type is I.
    where can i maintain the exceptions message type I.is it at the creation of FM or calling of FM?
    tell me in details.
    for handling exceptions:
    No Sales Order Created  = Message type 'I'
    OTHERS = Message type 'I'
    thanks in advance

    Exceptions are only code and text, the kind of message comes from the raising statement in the FM code.
    RAISE <Exception>.
    MESSAGE..... RAISING <Exception>.
    The management of the resulting code is in the caller program. ([Calling Function Modules From Your Programs|http://help.sap.com/saphelp_nw70/helpdata/en/d1/801edb454211d189710000e8322d00/frameset.htm])
         EXCEPTIONS
              no_values_found = 1
              ERROR_MESSAGE   = 2
              OTHERS          = 3.
    CASE SY-SUBRC.
      WHEN 1.
    I don't understand your requirement, try to read some documentation like [Specifying Parameters and Exceptions|http://help.sap.com/saphelp_nw70/helpdata/en/d1/801ee8454211d189710000e8322d00/frameset.htm] in [Function Builder|http://help.sap.com/saphelp_nw70/helpdata/en/d1/801e9a454211d189710000e8322d00/frameset.htm] and reformulate please.
    Regards,
    Raymond

  • Steps for IDOC scenario

    Hi all,
    I am doing an File to IDOC scenario.I have done with all the mappings and configurations in IR and ID.Please can anyone let me know the configurations that are to be done in R/3 and SLD for the posting of IDOC.
    Please can anyone explain this to me.
    Awaiting for ur reply
    Amit

    Hi Amit,
    the following is from a thread/blog I cant find anymore. So I copy and pasted it!
    SAP XI
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (IDX1)
    a) Select create new button
    b) Enter the port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Load Meta Data for IDOC (IDX2)
    a) Create new
    b) IDOC Message Type
    c) Enter port created in IDX1.
    SAP R/3
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (We21)
    a) First Select Transactional RFC and then click create button
    b) Enter the destination port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Create Partner Profile (WE20)
    a) Create New
    b) Create the Partner no. name as same the logical system name of the destination system.
    c) Select Partner type LS
    d) Enter details for Type: US/USER, Agent, and Lang.
    e) Click on the + button to select the message type.
    f) Select Partner no. and LS which ever create above.
    g) Select Message type
    h) Select Process code related to the Message type.
    I) save.
    In SLD – System Landscape Directory
    TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
    Ts for Third Party (Logical system):-
    BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
    BS for Third Party (Logical system):-Enter the XI logical system name.
    In Transaction SALE
    Define and Assign the logical system name.
    Regards Mario

  • Inbound Idoc Type / Message Type / Process Code for Delivery via Tcode VL0N

    Guys,
      I need to to Idoc Type and Message type for to create Delivery ( Tcode VL01N ) for a sales order.
      I tried Idoc Type DELVRY03 and Message Type DESADV, but this is for Purchase Order  ( VL31N ).
    Kindly help me.
    Regards
    Srikanth M

    Guys
    I could not use above message type/idoc type as they are not released in SAP.
      So i am again back to where i have come from. I am trying to use DESADV01 and Mess Type DESADV.
    Regards
    Srikanth M

  • 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

Maybe you are looking for