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

Similar Messages

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.

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.

What Message type and Process Code to use for Purchase Order Change in 4.6C

I like to implement in SAP R/3 4.6C a scenario for Purchase Order Change, via inbound IDoc.
I have been searching, but could not find what Message Type, Idoc Basic Type and Process Code to use.
I can not imagine this functionality does not exist in 4.6C.
Any suggestions for my problem are welcome.

Hello,
In this case you should use the message PORDCH and BAPI method BAPI_PO_CHANGE but only exist as of release 4.7.
Function module    BAPI_IDOC_INPUT1
Idoc Type              PORDCH01
Message Type      PORDCH
So check carefully the following OSS notes:
[Notes 589066 - BAPI_PO_CHANGE: Incorrect account assignment to network |https://service.sap.com/sap/support/notes/589066] (not be fooled by the description)
[ Notes 197958 - BAPIs for purchase orders - Missing Functions|https://service.sap.com/sap/support/notes/197958]
Regards,
Andrea
Edited by: Andrea Olivieri on Sep 3, 2009 10:17 AM

Bind message type and process code

Hi everyone,
I want to bind one message type with two procee code,How can I do this?Thanks in advance!
Best Regars,
Yu

Hi ,
goto to transaction we41 if outbound process code ,go to respective process code or create ur own process code and add message type .
goto to transaction we42 if inbound process code ,go to respective process code or create ur own process code and add message type .
But when you add this message type in the partner profile or distribution model then i think it will give an option.
Please reward if useful.

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.

Message type, Idoc type and process code in ALE/Idoc

Each Idoc version(creams01 or cremas03) will have seperate process codes in Inbound process?
Whether Message type triggers the process code or the Idoctype/idoc triggers the process code in Inbound process?
regards
Message was edited by: henry

Hi Henry,
About your question as how should you assign seperate process code for the same message type ( with different IDoc Type )-
In We42, the message type can be assigned to the processing code. But here you will find that along with message type there are two more fields - Message Code & Message Function.
You can use any one these to serve your purpose.
e.g. you can assign
-process code P1 to message type M with Message code 1
-process code P2 to message type M with Message code 2
Further these process types can be configured to call separate FMs.
Now depending on IDOC types your external system should populate the message type as well as Message code so that accordingly process code will be determined at the time of inbound processing.
I hope it's clear & correct
Thanks,
Ram

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.

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

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

Confusion on pair type and Processing Type

Dear Experts
I have the the below doubt in TIP Table
Pair type gives the information on the how the Time pairs being generated as
0-      Non recorded Time
1-      Attendences
2-      Absences
3-      Attendences Recorded from client
Processing Types also gives information on how the Time pairs are coming with below spec
- Pair is deleted at a later stage
BLANK Pair not included in calculation of productive time
P Attendance pair, included in calculation
of planned working time
A Absence pair, included in calculation
of planned working pair
S Planned working time pir
M Overtime pair
Kindly let me know on what senerios we go with pair type and processing type as they have the same meaning
Regards
Giri

Hi Shruit
i am clear but as mentioned in pair type 1= attendence (2011 - Positive) and Planned working time for negative . in processing type S, A,P also signifies the information how the Time pairs are Generated   and also we have Origin indicator of time pair O which specifies wheather the time pairs are coming from E,M.A,P and D.
Since they have same information why Sap has defined pair Type processing Type and Origin Indicator
                                                             I got the inputs theriotically but practically i am not able to get the TIP Table to read and understand .
Thank you very much for the inputs
Giri

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

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

No archive information found for object type and document type

Hi All,
When i try to view the print preview for a perticular doc type, system is giving the error as "No archive information found for object type and document type"
Diagnosis
    No information was found about optical archiving. This may be due to
    either of the following reasons:
    1. No valid archiving parameters were passed
    2. Your system is not configured for optical archiving
System Response
    Processing is cancelled.
Procedure
    Specify valid archiving parameters or check whether your system is configured for optical archiving
Regds,
CB

Hello,
You are trying to Print & also archive by selecting the option Print & Archive.
You have to do archivelink configurations and then create document type and assign to the object type with content repository with archivelink table.
If you want to archive the spool or output then you have to use object type as DRAW. If you are archiving invoice document or letters or so on then you have to know the object type/Business object of the transaction.
Please note that for archivelink configuration, attachment will be either stored in archive server or in SAP database table based on business requirement.
Hope this will give you some understanding on archiving area.
-Thanks,
Ajay

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

Urgent information required regarding message type and process code

Similar Messages

Maybe you are looking for