Definition of Message Type and Transaction Type from the Implementation per

My assumption is that both, Notification Type and Message Types are same.
<b>Is the above assumption right?</b>
In Sol Man 4.0, the notification types required are
1)     ABSC  2) SLF1 3) TASK
<b>Are there any other notification types required for Sol Man 4.0?</b>
The main transaction types required in Sol Man 4.0 are
SLFI, SLFT and SLFN
<b>What is the significance of External Number range and Internal Number range used in the transaction type?</b>

Hi
1 > A data type</i> in a programming language is a set of data with values having predefined characteristics. Examples of data types are: integer, floating point unit number, character, string, and pointer.
The characteristic of columns and variables that defines what types of data values they can store. Examples include character, floating point and integer
Check out the details:
http://en.wikipedia.org/wiki/Data_type
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:
details:
http://help.sap.com/saphelp_nw04/helpdata/en/2d/c0633c3a892251e10000000a114084/content.htm
2) Regarding the difference between XI 3.0 and PI 7.0, this threads will clear your doubts:
difference between XI 3.0 and P.I 7.0
Difference/ changes from XI 3.0 to PI 7.0
Regard's
Chetan Ahuja

Similar Messages

  • Document type and Transaction type

    Hi,
    Can someone give me a clear and detailed understanding of how to maintain transaction types in SRM system and document types in the backend system based on various scenarios (i.e standalone,classic. extended.....)
    Is it mandatory that the document type assigned in org plan attribute BSA be maintained in the local system as well??
    Thanks
    sunny

    Lol Sunny,
    Thanks for the compliment, but no, I'm in france. I work on SRM for now 5 years, so it helps
    In fact META BAPI are only BAPIs, with a certain way of developping: What SAP calls "Abstraction Layer".
    This allow you to manage Partner system version differences, and backend unavailability, the process is:
    ->META_BAPI
    -First try synchronously
    -->Read table BBP_FUNCTION_MAP (and now get into BADI) to get the exact function module to be called depending on the partner system type and its version
    --->Call of this function (which either makes local actions, or call the backend system with RFC)
    If the system was unable to call the partner system , it creates a job to re-try the call (based on what you entered in customizing).
    Here is the SAP description:
    <i>- Depending on the release level used, you can use various Business Application Programming Interfaces (BAPIs) to implement the business processes in the back end system. The abstraction layer encapsulates the BAPI calls in the back end system that are necessary to generate the back end documents from requirement coverage requests. The abstraction layer accesses the following sources of information:
    -Dispatcher: This function module analyzes the Customizing settings and then knows:
    --     Which driver it must call
    --     Which back end system it is communicating with
    --     The back end system release
    --     Driver: For each release level supported and each abstraction layer, there is a driver module that calls the BAPIs in the back end system.
    --     Spoolers: The spooler controls the transfer of documents from the Enterprise Buyer system to the back end system. If errors occur during the transfer, for example, the back end system cannot be contacted, the spooler is used as the queue for the requirement coverage requests. The spooler tries to contact the back end system at regular intervals and to transfer the documents.</i>
    Regards.
    Vadim.
    PS if you are really "amazed" please be more generous in your rewards

  • TPM12 Report not shwoing Product Type and Product Type Text

    Hi ,
    After we went live with a upgrade the report TPM12 which is run by the Treasury department every day, is now showing the blank values for  "Product Type", "Product Type Text", "Transaction Type", and "Transaction Type Text". 
    Which was not the case earlier.
    Any adivce please.
    Thanks,
    Venkat

    Good day
    We have a similar issue.
    In our system the line item type for the CW product was IDCW.  When we however split them by batch into two sub-lines, the new lines defaulted to IDLV (instead of the expected IDCW).
    So I think Alexander's diagnosis is spot on?
    My question though...  What logic does EWM use to derive the item type for the sub-lines?  Because surely it should be the same as the 'parent' line item (IDCW in the case) ?
    Please advise
    Callie

  • Loading masterdata and transaction data from same flat file

    hi all,
    how can i load master data and transaction data from the same flatfile at a time.

    I am afraid it is possible.
    Go thru this Uploading Master & Transaction Data together from Flat File

  • 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

  • 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

  • Creation of new movement type and transaction code

    Hi
    As per my business requirement i want to create new movement type 911 in  1M and how to assign to transaction code MIGO and if possible can some body can guide me with configuration.
    With regards
    G Narendra kumar

    Hi Narendra,
    1 . To copy a movement type,
    select the field Movement type and choose Continue. The dialog box
    Define work area appears.
    2. In the dialog box Define work area, enter the movement type you want
    to copy in the From: field. In the To: field, enter the name of the
    new movement type you want to create. To go to the overview of the
    selected movement types, choose Continue .
    3. Select the movement type you want to copy, and choose Edit -> Copy
    as.
    Overwrite the selected movement type with the new movement type
    (beginning with 9, X, Y, or Z) and copy all dependent entries.
    The system copies all control indicators from the reference movement
    type to the new movement type.
    4. Copy the reversal movement type and enter it in the view
    Reversal/follow-on movement types.
    5. In SE38, execute the program RDDKOR54 and then give the entry T156 as table name and again execute. Check if the entries 9,Y, and Z* are available in the namespace.
    Thanks
    Dipak

  • 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

  • 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

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

  • Business Object type and Transactions

    Hi, gurus.
    Where can i check the matching of Business Object type with transaction type , i.e. CRM Service Process ( BUS2000116 and SLFN)?
    Is it possible to change these kind of settings? Where?
    Thanks a lot

    Hi Michele 
    The transaction you are looking for should be SWO1
    Then put the ex "BUS2000116" into the Object/Interface type and ...
    Guess it will help you
    Best Regards
    Daniel

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

  • I want the message types and basic types for catsdb table

    i want the message types and basic types for catsdb table

    Hi Jagrut,
    Message Class is "LR".
    <b>Reward points, if helpful.</b>
    Regards,
    Atin

  • Cardinality between Message Type and Data Type

    Hi SAP gurus,
    Could anyone please tell me the cardinality between the Message Type and Data Type?
    Thanks,
    Adnan Abbasi

    1:1
    Sameer

Maybe you are looking for