Port, Message type and Function Group

Hai,
  Iam working on an inbound process for four different Partners.
Is there any need of Port for Inbound?
Shall i use the same message type and Idoc type?
And what about the function Group?
Thanks
Avi

Hello,
<b> If the functionality is same , you can use the same function Group.
If functionality is different , you want to use different Function Group.
Obvisouly, it is suggested to use different Message types .
If you are using same fields ,you can use the same idoc type.
depends on the scenior , the process code is needed. Generally no need.</b>
Thanks
Manju

Similar Messages

  • IDOC message type and message code and function?

    Hai...
      anyone can explain with example what is IDOC message type and message code and function? how it is used?
    regards,
    prabakaran

    Hi
    An IDoc type can be implemented for various "logical" messages; one message can also be assigned to different IDoc types (m:n relationship).
    The message is defined by the values for message type (required), message code (optional) and message function (optional). These three fields belong to the key fields in the partner profiles, which are used, for example, to determine inbound processing. If the 'Message type' field is not maintained (e.g. in the case of a control record from Release 2.1, in which MESTYP did not exist), the IDoc Interface uses the value from STDMES (EDI message type).
    If possible, the descriptions of the message type should be linked to the corresponding EDI message type.
    The message ORDERS (= message type) identifies purchase orders (outbound) and sales orders (inbound).
    Message code or Process Code for Inbound Processing
    Code which identifies a process type.
    The process type determines which process is used to convert an IDoc to an SAP document.
    Process code for outbound processing
    Code which identifies the type of data which is to be sent via the IDoc interface.
    Using the process code, the IDoc interface finds the application selection module which converts the SAP document into an IDoc.
    The process code is only used with applications which perform outbound processing via Message Control (NAST).
    Thanks & Regards
    Kishore

  • 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 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 corresponding Functional area

    Hi All,
    How can i get a Message type corresponding functional area?
    For example : MATMAS---- MM
    I have 900 message types i need Funational areas of all these Message type.Please let me know if we have any table or functional module to completes this task.

    Hi Tashvi,
    This is an article from ERP Genie.
    [AFS Message, Idoc Types and segments |http://www.erpgenie.com/component/content/article/788]
    [SAP ALE and IDOC Transactions  |http://sap.niraj.tripod.com/id52.html]
    [Message types Master Data|http://www.erpgenie.com/sapedi/message_types_masterdata.htm]
    Hope it helps.
    Thanks & regards,
    Dileep .C

  • Function modules and function groups

    Hi alll
       Can anybody explain me abt function module and function groups...please
    Thanks and Regards
    vijaya

    <b>Function groups</b> are containers for function modules. You cannot execute a function group. When you call an function module, the system loads the whole of its function group into the internal session of the calling program (if it has not already been loaded).
    The name of a function group can be up to 26 characters long. This is used by the system to create the components of the group (main program and corresponding include programs). When you create a function group or
    function module in the Function Builder [Ext.] , the main program and include programs are generated automatically.
    When you create a new function group, the system automatically creates a main program containing two includes. Like any other programs and includes, you can display them in the Repository Browser.
    The name of the main program is assigned by the system. This is made up of the prefix SAPL followed by the function group name. For example, the main program for function group SXXX is called SAPLSXXX.
    The names of the include files begin with L followed by the name of the function group, and conclude with UXX ( or TOP for the TOP include). The TOP include contains global data declarations that are used by all of the function modules in the function group. The other include file within the main program is used to hold the function modules within the group.
    You cannot declare a COMMON PART in a function group. Function groups have their own table work areas (TABLES). Function groups encapsulate data.
    All of the function modules in a function group can access the global data of the group. For this
    reason, you should place all function modules that use the same data in a single function group.
    For example, if you have a set of function modules that all use the same internal table, you could
    place them in a function group containing the table definition in its global data.
    Like executable programs (type 1) and module pools (type M), function groups can contain screens, selection screens, and lists. User input is processed either in dialog modules or in the corresponding event blocks in the main program of the function group. There are special include programs in which you can write this code. In this way, you can use function groups to
    encapsulate single screens or screen sequences.
    For function module, have a look at
    http://help.sap.com/saphelp_nw04/helpdata/en/26/64f623fa8911d386e70000e82011b8/content.htm
    I hope it helps.
    Best Regards,
    Vibha

  • Creation and Change Date for Tcode and Function Groups

    Hello All,
    I need to display the Creation and Change Dates for Custom Tcodes and Function Groups in a Report. Can anyone please let me know the logic of retrieving it.
    regards,
    Mahesh

    Hi,
    TADIR and TRDIR is the tables where you can find all these data
    Regards
    Sudheer

  • 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

  • Idoc type, message type and process code for EDI 940 & 945

    Hi,
    We are implementing a scenario wherein we are required to send a Wharehouse Shipping Order to the warehouse (forwarding agent) using EDI 940. The output of the o/b is triggered from the Delivery (VA01) after creation of a Delivery in SAP. Once the warehouse ships the goods, it notifies us back by sending EDI 945 (Warehouse Shipping Advice). Using this inbound 945 we are required to update the existing delivery in SAP, i.e., it should do the Pick, Pack and PGI.
    Can someone tell me which Idoc type, Message Type and Process code should be used for the above scenario.
    Thanks in advance for the help.
    Regards,
    Gajendra

    Hi Gajendra,
    For EDI940, you can use message type SHPORD or WHSORD,  IDOC type DELVRY01 and process code DELV.
    For EDI945, you can use message type SHPCON or WHSCON,  IDoc type DELVRY01 and process code DELV.
    Hope this will help.
    Regards,
    Ferry Lianto
    Please reward points if helpful.

  • Idoc Message type and Process Cosde for CJ01 transaction

    Hi,
    What is the Idoc message type and inbound Process code for CJ01 transdaction?
    Is there Any standard procedure to find out Idoc Mesage type and process codes for particular application?
    Thanks.

    Hi,
    All the sending and receiving programs(transaction) start with BD. e.g. if you want to send the material you can use the BD10 transaction and IDOC is available for the same.
    Go to se93 and search for BD* and look for the description.
    Regards,
    Nilesh.

  • IDOC question on Message type and Basic Type - Partner Profile

    Hi all,
    I am wonder if I can post any IDoc question in this right forum/module. If not please direct me to the right forum/module. I am a newbie in IDOC setup.
    My question is about the setup of Partner Profile creation (WE20).
    When creating a new partner, for example with partner type LI, I notice there is outbound parameter and inbound parameter.
    Questions:
    1 u2013 It makes sense to have only one message type record appear in EITHER one of these two tables.  I notice that some partner in my system has message type record exist on both the inbound and outbound parameters table, why system allows? What is the business rational?
    2 u2013 May I have a list of standard SAPu2019s Message Type object of its usage description, and its allowable Basic Type (ie. IDOC TYPE). Basically a website to describe their (i.e. Message type and its Basic Type) business usage.
    Thanks.
    tuff

    Tuff,
    Below are my thoughts,
    There is a partner sing partner type LI. This partner in the WE20, has one record (i.e. with Message Type ORDERS) exist in the Outbound Parameter table. This partner also has 4 records (i.w. with Message Type DESADV, INVOIC, MBGMCR, and ORDRSP) exist in the Inbound Parameter table. So my question is what is the business rational behind this kind of setup. Because I am confuse when come to create a partner profile, whether I need to create a message type in Inbound Parameter table or Outbound Parameter table, or I need both.
    OK, so looking at the above example, you have an orders message type(This is for creating an order) in the outbound, this means that you are sending out an IDOC(purchase order for ex) to this partner, so that this partner can create an SO in his system and fulfill your order.
    Now you also, mention that you have other four Message types for the same partner on the inbound, now let us look at the above scenario, you have asked your partner to fulfill the order, i guess you would like to get a confirmation from him/her if the order was created or not in his/her system and how and when is he/she going to fulfill your order requirement. This he/she does by sending an response to your order -  ORDRSP.
    And when the partner is ready to ship your order to you, he/she sends out a Advance Shipping Notice - ASN via the IDOC of message type DESADV.
    Finally and most importantly , he/she will send you the invoice - INVOIC for the order.
    In general, you interact with your partner via Business Docs - Order, Delivery, ASN, Invoice etc, so whatever document come from your partner - ORDRSP, INVOIC etc will be on the inbound profile of the partner. Whatever docs that you send ORDERS, ORDCHG etc etc will be on the outbound profile of the partner.
    2 - Bascially I would like a reference in any website that allow me to choose which message type is best use for my partner profile, so that I don't have to reinvent.
    Well, there is no choice of choosing/best message type for a given requirement - So for sending an Invoice the message type is INVOIC, ORDERS - For order creation, ORDCHG for order change etc. However the IDOC type, is some thing that you can choose, for Ex: ORDERS01 - ORDERS05, these are the IDOC types that are available, so if you are interacting with a partner who are running an old version of SAP and their system has only upto ORDERS02 in their version of SAP then you would use ORDERS02.
    Regards,
    Chen

  • 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

  • Urgent information required regarding message type and process code

    Hi All
    We am working on EDI895 transaction (Delivery/Return acknowledgment) and we are using TXTRAW01 Idoc type for the mapping. Can anyone please let me know what the message type and the process code for the IDoc type is???
    thanks

    Hi,
    Welcome to SDN.
    Please go to transaction WE64 to find out all process codes available for IDoc type TXTRAW01 with message type TXTRAW.
    There are four process codes for message type TXTRAW.
    - ED00
    - ED00_XML
    - ED08
    - TXT1
    Regards,
    Ferry Lianto

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

  • Message type and Process Code for 940 IDoc

    Hi,
    what Message type and Process Code can be used for 940 IDoc when a SHPMNT05 IDoc is being used. We are using SHPADV message, SHPM process code for ASN. Can I use the SHPMNT message type for 940?
    thanks,
    Kumar.

    should SD11 be the only process code to be used or can we use SHPM. I guess we can use both for shpmnt05. But how do I know which process code is more suitable for my purpose. is there any place where i can check that info?
    Can we link SHPORD message type to a SHPMNT05 IDoc? i think this message type is more suitable.
    thanks,
    Kumar.

Maybe you are looking for