Frqently used process code in message control

Hai,
Ca you send me some frequently used process code used in Messge control to transfer transactional data
thanks and regards
murali rkishna

Hi
it may sound like not good news, but I think the answer is described in OSS Note 198252 - Special features of POI message category LOI*.
There all LOI* idocs are mentioned and then they say:
The message categories named are part of the POI (Production Optimization interface) interface.This interface and the message categories contained in it were developed for the transfer to non-R/3 systems.Therefore, an inbound processing in the R/3 system is not planned.The message categories are transferred via separate transactions / reports of the POI interface (Transactions POIM, POIT).Functions which exceed these transactions are not supported.For this reason, the above-mentioned ALE functions cannot be used for the message categories described.
So, in short, there is no inbound process code for LOIPRO.
Inbound processing then should be done through self-developed programs / idocs, calling BAPI-s (for example).
Regards,
Joe
Edited by: Joseph Yasman on Jun 30, 2009 1:46 PM

Similar Messages

Process Code for Message Type LOIPRO(in ALE/IDOCS)

Hi all,
I have to implement Production order Interface(create Production order,change Production order etc).The requirement is for eg:,I created one production order and posted it;it should get reflected in the recieving system.Does anyone know the process code for LOIPRO.I checked it in we42,WE64 and even the tables TEDE1 and TEDE2.But its not available.Process code and function module is necessary to continue with WE20.
Thanking you in advance,
anjaly

Hi
it may sound like not good news, but I think the answer is described in OSS Note 198252 - Special features of POI message category LOI*.
There all LOI* idocs are mentioned and then they say:
The message categories named are part of the POI (Production Optimization interface) interface.This interface and the message categories contained in it were developed for the transfer to non-R/3 systems.Therefore, an inbound processing in the R/3 system is not planned.The message categories are transferred via separate transactions / reports of the POI interface (Transactions POIM, POIT).Functions which exceed these transactions are not supported.For this reason, the above-mentioned ALE functions cannot be used for the message categories described.
So, in short, there is no inbound process code for LOIPRO.
Inbound processing then should be done through self-developed programs / idocs, calling BAPI-s (for example).
Regards,
Joe
Edited by: Joseph Yasman on Jun 30, 2009 1:46 PM

What is the process code for Message type FUNDMA

Hi,
I am sending CO elements to the distributed server using ALE. Can somebody tell me what is the process code for the message type FUNDMA?
Thanks
William

Check entries of table VEDI_TMSG1. This contains Message types and associated Process codes.
Hope this helps.
ashish

How to read the processing log of message control ....

Hi,
    I would like to find the idoc # generated by message control ...
    The input is delivery number that uses message control....
    In the delivery header output part, we can see the idoc # by pressing the
    processing log button, but i don't know how to get this log in ABAP program
    any good suggestions? Thanks

Hi,
Do you mean to read the mail content in R/3 inbox or UWL..?
If in R/3 then SBWP transaction Unread Documents..
If in UWL see notifications part.
Please if this does not solve your problem> please elaborate on your problem
Regards
Sai

PO invoice through IDOC --Need Standard Process code and Message Type

Hi All,
could any one send me SAP Standard Message type and SAP Standard process code for posting Vendor PO invoice.
Thanks
Raghu

Hello,
Standard Message type: INVOIC, Process Code: INVL, IDOC type INVOIC02.
Thanks,
Venu

Process codes for message types IORDER and INOTIF

Hi All,
I need to know the process code for above message types.
I could not get specific process code in WE64.
Regards,
Shahu

Hi,
Try searching in WE42.
This is what i found we64 (same for both message types):
ABI_AIDN_IN
ED00
ED00_XML
ED08
Good luck! Reward if helpful.
Message was edited by:
John Damion

What is the process code for message type FIXEDASSET_CREATE?

Hi all
please tell me that what is the process code for
MESSGAE TYPE = FIXEDASSEt_CREATE,
FUNCTION MODULE = IDOC_INPUT_FIXEDASSET_CREATE,
BASIC TYPE = FIXEDASSET_CREATE01 ?
thanx in advance.......
Edited by: Prachi Sharma on Jan 11, 2008 7:45 AM
Edited by: Prachi Sharma on Jan 11, 2008 8:03 AM

Hi,
Check the Tcodes WE41 and WE42 for Outbound and Inbound process codes
Check below Tables as well
EDE1T
EDE2T
EDE5T
EDE6T
TEDE5
TEDE6
Regards,
Satish

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

Wrong processing code used in inbound processing

Hi
We are on 4.6C and have configured a dist. model for material distribution using message type MATMAS. On receiving end IDOC is properly received but processed with code 51 which is "IDOC Interface not complete for message type".
While testing it in we19 with standard inbound option we found that its using process code AFSA though in the inbound partner profile its set to MATM. (In the table tbd52 AFSA is not even defiend for MATMAS but for ARTMAS) While using INBOUND FM option there with FM specified as IDOC_INPUT_MATMAS_MDM we were able to process the IDOC properly in receiving end. We are not sure which code is being defaulted to during automatic inbound processing but we guess its same as AFSA as shown during standard inbound option. It will be of great help if someone can explain what might have gone wrong.

Dear Renjith
I got it. Actually the process code was correctly attached in sending system but in receiving system it was unfortunately set to AFSA which I ignored. Thanks a lot for the response.
regards
saurav

Specific process code for Production order message type LOIPRO

Hello,
Is there any specific process code for Production order message type LOIPRO.
Request you to reply.
Thanks
Prashanth

Hi Prashanth,
sorry for last thread ... that not contain full information ...
For message type LOIPRO you can use process code APLI.
In IDOC PARTNER definition, the partner is linked with an IDOC TYPE and PROCESS CODE for inbound processing. This process code is in turn linked with a FUNCTION MODULE to process the IDoc such as IDOC_INPUT_INVOIC_MRM (Reff.. http://searchsap.techtarget.com/expert/KnowledgebaseAnswer/0,289625,sid21_cid519558,00.html)
Regards,
Amit

Use of process codes

hi,
why do we use process codes,what is the exact functionality of the process codes?
thanks in advance,
sravanthi

Hi
Process Code turn drives which Function Module to use,which in turn will determine the content of the message.
This link will be helpful for teh second query
http://logosworld.com/www7/EDI/HTML/IDocBook.htm.
Suggest to do search in SDN with key - 'Process Code'
Will get a lot of helpful discussions.
<b>Reward points if this helps.
Manish</b>

Need help in creating process codes

Hi All,
I need to create some message type and assign it to some idoc type , and i need to create process code and inbound function module for this.
Can some one please help me in this regard.
Thanks ,
Hem

hi
CATSDB CUSTOM IDOC TRANSFERMATION BETWEEN 2 DIFFERENT APPLICATION SERVERS
For this scenario Client 800 of application server SAPADM is the Sender and client 800 of application server SAP-REMOTE is the Receiver
1. Creating Logical Systems
o       Login using 800 client
o       Go to T. Code SALE
o       Expand Sending and Receiving Systems
o       Expand Logical Systems
o       Click on Define Logical System
o       Click on New Entries
o       Create CATSSENDER, ECC Logical Systems
o       Save and come back
o       Assign the CATSSENDER Logical System to client 800 of Application Server SAPADMAssign the ECC Logical System to client 800 of Application Server SAP-REMOTE
2. Creating the RFCs
o       Go to T. Code SM59
o       Expand R/3 Connections
o       Enter RFC Name as CATSSENDER
o       Connection Type as 3
o       Language as EN
o       Client as 800
o       User as SAPUSER
o       Password as YESV13
o       Target host as SAPADM
o       Click on Remote logon button to test the RFC
o       Enter RFC Name as ECC
o       Connection Type as 3
o       Language as EN
o       Client as 800
o       User as SAPUSER
o       Password as YESV123
o       Target host as SAPADM
o       Click on Remote logon button to test the RFC
3. Creating the Message Type
o       Go to T. Code WE81
o       Click on change, continue
o       Click on New Entries button
o       Give message type as ZCATSTIME and description
o       Save and back
4. Creating the Segment
o       Go to T. Code WE31
o       Give segment name as ZSEGMENTTIME
o       Enter Short Text
o       Enter the Field Name and Data Element in the text boxes
o       Save, continue,
o       Click on Edit -> Set Release
5. Creating the Basic IDOC Object
o       Go to T. code WE30
o       Give obj. name as ZTIMEIDOC
o       Click on create
o       Select create new radio button, give description and continue
o       Select the IDOC obj name and click on create button
o       Enter the segment name which is create earlier
o       Select the check box if you want to make the segment mandatory
o       Enter 1 in minimum number 99999 in maximum number, continue
o       Save and backo       Click on Edit -> Set Release
6. Creating Customer Distribution Model
o       Go to T. Code BD64
o       Click on change and Create model view button
o       Enter the short text and Technical name as CATSSENDER
o       Select the model and click on Add Message Type Button
o       Give the Sender as CATSSENDER,
o       Receiver as ECC,
o       Message Type as ZCATSTIME
o       Select the model view & click on Environment -> Generate Partner Profiles
o       Select Transfer IDOC Immediately and Trigger Immediately radio buttons
o       Click on Execute
o       You should get a list in green color which means it executed successfully.
o       Back to main screen, select the model view
o       Click Edit->Model view->Distribute
o       Click on continueo
You should get a list saying model view is distributed successfully.
7. Checking the Port
o       Go to T. Code WE21
o       Expand Transactional RFC
o       Find the port from the list which is created using BD64 for ECC (Receiving system) RFC Destination.
8. Checking the Partner Profiles.
o       Go to T. Code WE20
o       Expand Partner Type LS
o       Select the Partner profile ECC
o       Double click on Message Type ZCATSTIME in Outbound parmtrs.
o       Check Receiver Port is assigned correctlyo
Check the Basic type as your Basic IDOC object.
9. Assigning the Message Type to Basic IDOC Object
o       Go to T. Code WE82
o       Click on Change & continue, New Entries button
o       Give the Message type as ZCATSTIME
o       Give Basic Type as ZTIMEIDOC
o       Release as 4.6C
o       Save and back10. Creating Inbound Function Module (Posting Program)
o       Go to T. Code SE37
o       Create a function Module ZCATSDB_TIMESHEET_SURESH
o       Set the Processing type as Remote Enabled Module and mode as start immed, in Attributes Tab.
o       Import Parameters
          P_WORKDATE                    LIKE               CATSDB-WORKDATE
          P_COUNTER                        LIKE               CATSDB-COUNTER
          P_LSTAR                               LIKE               CATSDB-LSTAR
o       Export Parameters
o       Tables
             S_PERNR                      LIKE           ZCATSPERNR
[PERNR is select option parameters in ZCUSTOMIDOC report program so that it should be passed to function module ZCATSDB_TIMESHEET_SURESH in tables section. And also in tables section we used ZCATSPERNR, which is a global structure, which contains four fields as
Ø     SIGN
Ø     OPTION
Ø     LOW
Ø     HIGH]
o       Exceptions
o       Source Code
FUNCTION zcatsdb_timesheet_suresh.
""Local interface:
*" IMPORTING
*"     VALUE(P_WORKDATE) LIKE CATSDB-WORKDATE
*"     VALUE(P_COUNTER) LIKE CATSDB-COUNTER
*"     VALUE(P_LSTAR) LIKE CATSDB-LSTAR
*" TABLES
*"      S_PERNR STRUCTURE ZCATSPERNR
TABLES: catsdb, edidc, edidd. " using structures of catsdb, edidc, edidd
CONSTANTS: c_doctyp TYPE edidc-idoctp VALUE 'ZTIMEIDOC', " idoc type
             c_segnam TYPE edidd-segnam VALUE 'ZSEGMENTTIME',   "segment type
             c_mestyp TYPE edidc-mestyp VALUE 'ZCATSTIME'.   " message type
*001 comment begin
     creating internal tables with out header lines for catsdb, edidc, edidd and also
-           work areas
*001 comment end
DATA: it_edidc TYPE edidc OCCURS 0,    " control internal table with out header line
        it_edidd TYPE edidd OCCURS 0, " data internal table with out header line
        wa_catsdb TYPE it_catsdb1, " work area for it_catsdb internal table
        wa_edidc TYPE edidc, " work area for it_edidc internal table
        wa_edidd TYPE edidd, " work area for it_edidd internal table
        wa_zsegmenttime TYPE zsegmenttime, " work area for zsegment internal table
        v_occmax TYPE idocsyn-occmax,
        v_nbseg   TYPE i.
CLEAR wa_catsdb. " clears work area of catsdb
CLEAR wa_edidc. " clears edidc work area
*002 comment begin
Save the message type and the basic IDoc type in the control segment.
*002 comment end
MOVE c_mestyp TO wa_edidc-mestyp. " assigning custom message type to edidc workarea
MOVE c_doctyp TO wa_edidc-idoctp. " assigning custom idoc type to edidc workarea
*003 comment begin
Retrieve the maximum number of segments in the basic IDoc type.
*003 comment end
SELECT MIN( occmax ) FROM idocsyn INTO v_occmax WHERE idoctyp EQ c_doctyp AND segtyp EQ c_segnam.
*004 comment begin
Save the whole CATSDB table content in the IT_ZCATSDB internal table.
*004 comment end
SELECT pernr workdate lstar counter FROM catsdb INTO CORRESPONDING FIELDS OF TABLE it_catsdb WHERE pernr IN s_pernr AND workdate EQ p_workdate.
*005 comment begin
Create a data segment for each line of IT_ZCATSDB.
*005 comment end
IF sy-subrc EQ 0.
    LOOP AT it_catsdb INTO wa_catsdb WHERE pernr IN s_pernr.
      MOVE-CORRESPONDING wa_catsdb TO wa_zsegmenttime.
      CLEAR wa_edidd.
      MOVE c_segnam TO wa_edidd-segnam.
      MOVE wa_zsegmenttime TO wa_edidd-sdata.
      APPEND wa_edidd TO it_edidd.
      CLEAR wa_catsdb.
      CLEAR wa_zsegmenttime.
    ENDLOOP.
ELSE.
    MESSAGE 'NO DATA FOUND FOR GIVEN SELECTION' TYPE 'I'.
ENDIF.
*006 comment begin
Count the number of data segments.
*006 comment end
DESCRIBE TABLE it_edidd LINES v_nbseg.
*007 comment begin
If the number of data segments exceeds the maximum allowed number,then display an error message.
*007 comment end
IF v_nbseg GT v_occmax.
    MESSAGE 'IDOC ERROR Message' TYPE 'E000'.
ENDIF.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE' " for creating an catsdb idoc
EXPORTING
master_idoc_control = wa_edidc
OBJ_TYPE = ''
CHNUM = ''
TABLES
communication_idoc_control = it_edidc
master_idoc_data = it_edidd
EXCEPTIONS
error_in_idoc_control = 1
error_writing_idoc_status = 2
error_in_idoc_data = 3
sending_logical_system_unknown = 4
OTHERS = 5
   IF sy-subrc <> 0.
     MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
     WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
   ENDIF.
ENDFUNCTION.
Save, check and activate
111. Assigning the Inbound Function Module to Basic Type & Message Type
o       Go to T. Code WE57
o       Click on change, continue, continue and New Entries Button
o       Enter the Module as ZCATSDB_TIMESHEET_SURESH Type as "F"
o       Basic Type as ZTIMEIDOC
o       Message Type as ZCATSTIME
o       Direction as 2
o       Save and back
Now Login in 800 client of Application Server SAP-REMOTE
12. Assigning the Inbound Function Module in ALE Table
o       Go to T. Code BD51
o       Click on continue, New Entries button
o       Give the Inbound Function Module ZCATSDB_TIMESHEET_SURESH
o       Give Input t. as 0 (zero)
o       Save and back13. Creating Process Code
o       Go to T. Code WE42
o       Click on Change, New Entries Button
o       Give Process Code name as ZCATSDB, give Description & Save
o       Select Processing with ALE Services Radio button
o       Select Processing by Function Module Radio button
o       Click the ALE Table (arrow Icon) in Identification
o       Give the Function Module Name ZIDOC_INPUT_ZBAPI_STUD_MAS
o       Give maximum number of repeats 0
o       Save and back, back
o       Select the process code from the list & click on Logical Messages Icon
o       Give the Message Type as ZCATSTIME
o       Save & Back, Save & Back, Save & Back
14. Changing the Customer Distribution model in receiving system
o       Go to T. Code BD64
o       Click on change and Create model view button
o       Enter the short text and Technical name as CATSECC
o       Select the model view & click on Environment -> Generate Partner Profiles
o       Select Transfer IDOC Immediately and Trigger Immediately radio buttonso       Click on Execute You should get a list in green color which means it executed successfully.15. Assigning the Process Code to Message Type in Receiving System
o       Go to T. Code WE20
o       Expand Partner Type LS
o       Select the Partner Profile CATSSENDER
o       Double click on Message Type ZCATSTIME in Inbound parmtrs.
o       Give the Process Code as ZCATSDB
o       Click on Trigger Immediately Radio button
o       Save & Back
Save & Back
16. Creating the Selection Program (Outbound Program)
-         Login in client 800.
-         Go to T. Code SE38
-         Create a Report Program as ZCUSTOMIDOC with the following code
REPORT ZCUSTOMIDOC
       NO STANDARD PAGE HEADING.
TABLES:catsdb. " using structure of cats db table
*000 comment begin
     this selection screen contains one select option and one parameter
*000 comment end
SELECTION-SCREEN: BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
SELECT-OPTIONS pernr FOR catsdb-pernr.
PARAMETER: workdate LIKE catsdb-workdate,
          LSTAR like catsdb-LSTAR,
          COUNTER like catsdb-counter.
SELECTION-SCREEN: END OF BLOCK b1 .
DATA: wa_val TYPE i.
wa_val = pernr-high - pernr-low.
*001 comment begin
      calling custom function module
*001 comment end
CALL FUNCTION 'ZCATSDB_TIMESHEET_SURESH'
EXPORTING
    p_workdate = workdate " passing workdate parameter
    p_LSTAR = LSTAR
    p_counter = counter
TABLES
    s_pernr    = pernr. " passing pernr select option
IF sy-subrc EQ 0.
MESSAGE i000(zaluri) WITH 'IDOCS CREATED FOR EMPLOYEES BETWEEN' pernr-low ' AND ' pernr-high .
MESSAGE i000(zaluri) WITH   'IDOCS CREATED FOR EMPLOYEES BETWEEN' PERNR-LOW 'TO' PERNR-HIGH.
gives information message if idocs are created for given employees
ELSE.
MESSAGE e000(zaluri) WITH 'NO IDOCS CREATED FOR EMPLOYEES' pernr-low 'TO' pernr-high. " gives error message
" if idoc is not created
17. Transferring the CATSDB records from sender Application Server SAPADM to receiver Application Server SAP-REMOTE
-         Execute Report Program ZCUSTOMIDOC
-         Give the Range of PERSONNEL NO'S, Date, Activity Type, Counter to Transfer
-         Give Message Type as ZCATSTIME
-         Give Receiver Logical system as ECC
-         Execute
-         You should get the IDOC Number
-         Take the IDOC Number and go to T. Code WE05 & Execute
-         In Outbox you can see the IDOC Status
-         Select the status record in left side window
-         Double click on the Status record in right side window-         You can see the Control Record, Data Record and Status Records for that IDOC
If the ICON is green and the status code is 3, it means the IDOC is passed to PORT Successfully
18. SENDING IDOCS FROM APPLICATION SERVER SAPADM
TO APPLICATION SERVER SAP-REMOTE USING WEDI
-         Go to T. Code WEDI & execute or T. Code WE19
-         Give idoc number it is generated recently
-         Continue & double click on segment to view data in segment
-         Click on EDIDC to give port, partner no, message type, partner
type of receiver. [For sender no need to give any port no leave it as
blank]
-         Click on Standard Outbound Processing button and click continue
-         You will get a message as idocs successfully transferred
Now Login in Receiver 800 client
-         Go to T. Code WE05 & Execute
-         You can see the status record in left side window
-         If the status no is 53 and color is green, it means the IDOC is posted to Application successfully.
-         You can see the Log Information by double clicking on the status record in right side window.
-         Now in left side window, you can see the Control Record, Data Record & Status Record of the IDOC
-         Now go to T. Code SE16
-         Give the table name CATSDB & press F7
-         See the contents of the table
-         The table is updated with the catsdb records transferred from 800 client with our selection program.
regards
Nagesh.Paruchuri

Process code

Dear All,
I have my idoc number and message type, partner type.
I checked WE20 and in partner type, message type is defined.
When i double click on message type, i found no process code.
This is outbound idoc.
Could you please let me know how to find the process code for message type for outbound process?
Also, in WE19, if i click on Inbound function module option, we can specify our own function modules here.
Kindly let me know how to find if we have multiple function modules attached with one message type.
Thanks in advance for your kind help and spending your time reading my questions.
Regards,
T

Hi tarun,
if you are dealing with an outbound idoc , then we generally dont attach a process code with it. If the idoc is that of a master data (ex. customer master or vendor master), then the idoc posting is done via change pointer activation or manual triggering of the application specific transaction.
if the idoc is of transaction data type, then we use the output type and corresponding process code to trigger the idoc. Take an example of outbound delivery (VL02N). This application comes under application area V2 - Shipping. Corresponding to this application , you can find out the relavant output type and the process code through the transaction NACE. In this case,you require some functional knowledge abt the application to be able to correctly determine the relevant output type. Kindly state your appliaction (message type of idoc) to be more specific.
As far as inbound idoc is concerned, you can assign multiple process code to one message type , by defining message variants of the same. If you go to partner profile maintanance (WE20), then you can see that there is an option of specifying the message variant along with the message type. So, when the idoc comes in R/3, the control records of the idoc contains (or should contain) the desired messgae variant and then the system identifies the appropriate process code (and hence the FM), to post the idoc.
Revert in case of any queries,
Pls reward points if helpful.
Karan

Doubt in IDOC Regarding Process codes

Please check the link
http://idocs.de/www5/books/IDocBook/cook_A5.pdf
In page no: 32 (Topic: 8.5 Assigning a processing function ) ,FM is assigned directly to Message type and Idoc type combination.
But in the next page, Process code is created for that FM and Asigned that process code to message type and Idoc type combination.
What's the differece.
Another thing is in which transaction we assign Process codes to Message type and Idoc type Combinations
Above tutorial looks like old version. In my system Transactions are looking different ,than they are in Tutorial. I am working in version 5.0. If possible, Please provide me perfect material.

Hi
Process code always points to a Function module
Means it calls the fun module
In We41/42 you creata process code and assigns to a Message type
so means that Process Code, Idoc Type and Message type are interlinked
Even you can check in WE20 partner profile
in the Outbound
double click on the Message type and press message control , it shows the process code attached
and double click on the process code it shows the fun module attached to it.
Reward points if useful
Regards
Anji

Doubt in IDOC's - Process Codes

Hi,
Currently i am working on an object related to IDOC generation. This is my first object in IDOC's. I am doing it from the scratch including creation of segments, IDOC type, message type, process codes...
In this process, I am developing a function module that should be assigned to the process code. My doubt here is, is there any standard interface to the function module that we have to assign to the process code?
I am also giving the flow which i will be using in developing the Function module. Please go through it and kindly let me know if I am doing it in the right way or not?
1. Extract data from data base based on the entry in NAST
2. Filling IDOC DATA & Control records
3. Calling the FM MASTER_IDOC_DISTRIBUTE to generate the IDOC
Please suggest me whether i am doing it in the correct way or not?
Thanks in Advance,
Best Regards,
Phani

Hi,
For outbound u need to attach ur FM to the process code in WE41 tcode..I think u r using message control method for ur requirement.please look at the configurations for outbound using message control method.we use we41 (outbound process code) and we use this in the message control tab in the partner profiles.
The transaction codes that are required for this method are
We81
We30
We31
We82
We21
We20
Bd64
Nace
Me22n (purchase order), va02 (sales order) etc.
Ex: purchase order.
Message type: ORDERS
Idoc type: ORDERS05
Outbound process code for purchase order: me10
Regards,
Nagaraj

Frqently used process code in message control

Similar Messages

Maybe you are looking for