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

Similar Messages

From which table could i get the process code and corresponding FM.

Thanks!

TMSG1 Logical Messages and Process Codes in Outb. Procg
TMSG2 Logical Messages and Process Codes in Inb. Procg
Also check other tables :
TEDE and TEDE1
Another table to look at is EDIFCT. It contains the link between message type and processing function module.
Thanks
Seshu

Purpose of Process code

Hi what is purpose of Process Code
I know there we add Msg type and Function module what is its function that function module will helps in getting the data
and *what abt Msg type* and Process code there

Hi,
R/3 uses the method of logical process codes to detach the IDoc processing and the processing function module. They assign a logical name to the function instead of specifying the physical function name.
Logical pointer to a processing method
The IDoc functions are often used for a series of message type/IDoc type combination. It is necessary to replace the processing function by a different one. E.g. when you make a copy of a standard function to avoid modifying the standard.
Easily replacing the processing method
The combination message type/IDoc will determine the logical processing code, which itself points to a function. If the function changes, only the definition of the processing codes will be changed and the new function will be immediately effective for all IDocs associated with the process code.
For inbound processing codes you have to specify the method to use for the determination of the inbound function.
After defining the processing code you have to assign it to one or several logical message types. This declaration is used to validate, if a message can be handled by the receiving system.
The inbound processing code is assigned analogously. The processing code is a pointer to a function module which can handle the inbound request for the specified IDoc and message type.
The definition of the processing code is identifying the handler routine and assigning a serious of processing options.
Processing with ALE
You need to click "Processing with ALE", if your function can be used via the ALE engine. This is the option you would usually choose. It allows processing via the ALE scenarios.
Associate a function module with a process code
Table TBD51 to define if visible BTCI is allowed
For inbound processing you need to indicate whether the function will be capable of dialog processing. This is meant for those functions which process the inbound data via call transaction. Those functions can be replayed in visible batch input mode to check why the processing might have failed.
WE41 Process code outbound creation
WE42 Process code inbound
Regds
Sivaparvathi
Please reward points if helpful............

Error while creating inbound process code

Hi gurus,Iam creating a custom idoc.
800 -> sender
810 -> Receiver
i have completed outbound processing on 800.
On 810, completed following steps for inbound processing.
1.) I have added my Inbound FM in BD51.
2 ) Assigned my FM to Message type and Idoc type in WE57.
3 ) When adding my FM to process code in BD67, it is showing error that
Entry ZSATPC does not exist in TEDE2 - check your entry.
{ zsatpc is my custom process code }.
4) While Creating Process Code in WE42 with options [processing with ale service / Processing
by FM] and saving it is giving error that
" " is not a valid language.
And when I saw help (?) regarding this error, the following text appeared in a window.
Diagnosis
A key with language "" "" was specified for table "EDE2T". This is not a valid language.
This applies to field "LANGUA"
System Response
The system rejects the key.
Procedure
Enter a valid language. This is usually the language you logged on in.
You logged on in language "EN".
Table T002 contains a list of valid languages.
Please solve this error. Give me steps to create inbound process code.
thanx in advance. Hoping replies soon........
Satish.

Dear Satish,
Very peculiar. The language should come from your log on language. Try to login into the system again. Call we42 again and see if it works.
Regards, Rakesh

Creation of Process code for output type

Hi,
Could someone help me out in defining processcodes for output types.
Thanks in advance,
Yaseen

Hi Yaseen,
The Tr.code WE41 and WE42 are also used for maintaining process codes.
To maintain process codes in WE41 or WE42, Go to these Tr.Codes and Click on the Change button. Then click on "new entries" button to create your new process code.
FYI, Outbound process codes are stored in SAP Table TEDE1 and inbound process codes are stored in SAP Table TEDE2.
Hope this helps.
Rgds,
Sam Raju
Message was edited by: Sam Raju

File 2 IDoc ----- Process Codes

Hi Frnds,
I done one scenario between File 2 IDOC.
I am updating file system data in MATMAS IDOC.
Scenario working prperly, But i am unable to se the results in MATAMAS IDOC.
File adapater picking up tha data it sent IDOC.
how to see the Up dated data in to MATMAS,
Which process codes i need to execute
can any one help me out...
Regards,
Raj

hi,
these are the process codes.
Step 1)
Goto SM59.
Create new RFC destination of type 3(Abap connection).
Give a suitable name and description.
Give the Ip address of the R3 system.
Give the system number.
Give the gateway host name and gateway service (3300 + system number).
Go to the logon security tab.
Give the lang, client, username and password.
Test connection and remote logon.
Step 2)
Goto IDX1.
Create a new port.
Give the port name.
Give the client number for the R3 system.
Select the created Rfc Destination.
Step 3)
Goto IDX2
Create a new Meta data.
Give the Idoc type.
Select the created port.
Steps for R3.
Step 1)
Goto SM59.
Create new RFC destination of type 3(Abap connection).
Give a suitable name and description.
Give the Ip address of the XI system.
Give the system number.
Give the gateway host name and gateway service (3300 + system number).
Go to the logon security tab.
Give the lang, client, username and password.
Test connection and remote logon.
Step 2)
Goto WE21.
Create a port under transactional RFC.(R3->XI)
Designate the RFC destination created in prev step.
Step 3)
Goto SALE.
Basic settings->Logical Systems->Define logical system.
Create two logical systems(one for XI and the other for R3)
Basic settings->Logical Systems->Assign logical system.
Assign the R3 logical system to respective client.
Step 4)
Goto WE20.
Partner type LS.
Create two partner profile(one for XI the other for R3).
Give the outbound or inbound message type based on the direction.
Step 5)
Goto WE19
Give the basic type and execute.
fill in the required fields.
Goto IDOC->edit control records.
Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
Click outbound processing.
Step 6)
Go to SM58
if there are any messages then there is some error in execution.
Goto WE02.
Check the status of the IDOC.
Goto WE47.
TO decode the status code.
Step 7)
Not mandatory.
Goto BD64.
Click on Create model view.
Add message type.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
WE42 process code
WE47 status info.
Thanks,
Vijaya

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

XI-- IDOC scenario, how to link process code with function module

Hi Forum,
I have a XI--->IDOC (R/3) scenario,
where i m creating a IDOC in XI and sending it to R/3,
i have done all settings to send the IDOC from XI to the R/3,
i also have the function module to process that IDOC in R/3,
the problem is:
I want to know in details (step by step) how to make a Idoc Inbound process code, link it with the function module and use the process code in the Partner Profile in R/3,
pls help

HI,
FOr this u need to go to transaction WE41 for inbound and WE40 for outbound there u assign the function module.
Now u go to WE20 transaction for partner profile and u can assign the proces code to the inbound message.
Go to the below help for more information:
http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm
Inbound process code:
http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm
Thnx
Chirag

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

What is a process code in ale idoc

what is a process code in ale idoc,what is the purpose of Process code.

Hi,
     Let me tell some scenario then u would be able to understand what a process code is-------
In ALE ie, the data requested system is receiver and the data already presented system is sender ie, from where we are having the data,
here in sender side----
       we need a program to tranfer required data into idoc--( idoc is just a data container )    in sender side this program logic is in a function module it is configured in we41.
         ie this will transfer the data from database to idoc----in sender side it is a process code
and in receiver side after receiving the data we have to post it in database again program needed it is also ie the required code is also in function module it is configured in we42
it is about receiver side f.m or simply process code
okkkkkkkkkkkk

Custom process code and FM for custom IDoc...

Hello Experts,
I created a custom IDoc based from ARTMAS05 IDoc. This is because we only need 3 segments and
the standard idoc(Artmas05) contains so many segments that we need.
Now, will I create a custom process code and FM for this? how do I go about this?
Thank you guys and take care!

Hello,
Here are the Steps that we need to be following while creating a Custom Process Code with Custom Function Module. ( Since the Segments to be handled are very Less, I am recommending that you go for a Custom Function Module).
1. Go to SE37 Create a Function Module. Please ensure to Create it with the IMPORT / EXPORT /TABLES parameters exactly in the way that they exist in any Standard SAP Inbound FM (Refer to IDOC_INPUT_ORDERS for example).
2. Once our FM is Ready (Need not be Complete with the Code to go ahead with the Process Code Creation) and Active, the next Step is to Create an Entry in the Transaction Code BD51 where we will register the Function Module.
3. Next, we'll have to go to T-Code WE57 where we'll have to make an entry for the Function Module with the IDoc Type & Message Type.
4. Finally, go to WE42 and Create a New Process Code and assign the Function Module and the Message Type.
NOTE 1 : The Process Code is, as we know, Client Dependent. So, once you create a Process Code, we need to have it migrated to the Testing Environment to Start & Carry Out Testing.
NOTE 2: If Step 2 & 3 are missing, then we'll not be able to assign the Function Module in WE42 while Creating Process Code.
Hope it was helpful.
Thanks and Regards,
Venkata Phani Prasad K

IDod Type,Message Type,Inbound Function,Process Code Required

Dear All,
I require
1. IDoc Type
2. Message Type
3. Inbound Function
4. Process Code
for
a. Vendor Master Creation,Updation,Deletion
b. Customer Master Creation,Updation,Deletion
c. Vendor Invoice(TCode-FB60) Creation,Updation,Creation
d. Vendor Credit Memo(Tcode-FB65) Creation,Updation,Creation
e. Customer Invoice(TCode-FB70) Creation,Updation,Creation
f. Customer Credit Memo(TCode-FB75) Creation,Updation,Creation
i require to insert all the above detail into SAP from another system so please provide me the full detail.if the IDoc type is separate for Creation Updation Deletion then provide likewise.
Everybody will rewarded.
Thanks,
RP

hi
use t code wedi and goto EDI administration menu. in that goto development menu. there you can find all items like Idoc type, message type or process code all information is available. You can also use t code WE30,WE31,WE80,WE81, WE42 - Inbound process code and WE41 Outbound process code.
Hope this helps. Assign points if useful.
Rago

Error in Process code creation

Hi All,
I need to create a process code and i need to attach a custom function module for that process code.
So i have created custom FM.
afterward in WE42 ,
I gave custom process code name ,description and FM .
when i tried to save the same its giving following message.
For entry, access 'Function module for ALE-EDI inbound processing'
when i tried to give some entries its not accepting...
Please provide me the steps for process code creation.
Reg,
Hem.

hi
good
Definition
Another name for a specific process, for example function module or workflow. IDocs are read or written in this process.
Use
In the partner profiles, the processing is never addressed directly but rather always using a process code. You can therefore replace an old process with a new one for any number of partners by assigning the existing process code to the new process.
Two types of process code are used in conjunction with the partner profiles:
1) Outbound Process Code - if you are using outbound processing under Message Control, the IDoc is generated in the IDoc Interface. The process code names the relevant function module.
2)Inbound Process Code - names the function module or workflow which reads the IDoc data and transfers the data to the application document.
There are process codes for exception handling:
1) System Process Code - names the workflow which is triggered in inbound or outbound processing when an exception occurs.
2) Status Process Code - names the exception workflow which is triggered when an incorrect status is returned by the external system.
These two types are configured centrally and not on a partner-specific basis and therefore do not have to be maintained when a new process is defined. They were introduced for the sake of completeness, so that each process in the IDoc Interface is addressed using a process code.
reward point if helpful.
thanks
mrutyun^

Need of Process code in ALE Inbound Processing?

Hi All,
What is the need of process code in ALE Inbound Processing? Why do we need to reach the function module through process code? we can as well directly point to function module.

Hi Ravi,
Please chcek this link perhaps it may help.
http://help.sap.com/saphelp_erp2005/helpdata/en/dc/6b804043d711d1893e0000e8323c4f/frameset.htm
Regards,
Ferry Lianto

IDOCs - Simple doubt in INBOUND DELVRY. IDOC-DELVRY03, Process code isDELV?

Hello Experts,
Our SAP system receives the Inbound IDOC for Delivery from Gentran.
Further details are,
Process code: DELV
IDOC type: DELVRY03
Message type: SHPCON
Message code: TOC
Parther profile: Account # of Ship To party
So, my requirement is that,
If this Inbound Delivery IDOC contans the Message Code as TOC, I need to insert/add my logic
so, let me know that,
1) Request u that, let me know How to go ahead, becoz am new IDOCs, like, Is I need to look for the any Usre Exit? I mean, At Wht point I need to add my code in this whole process?
thank you
Edited by: Srinivas on Jun 29, 2008 11:15 PM

Hi Srinivas,
Use the below user exit for creating a STO order.
CALL CUSTOMER-FUNCTION '003'
       EXPORTING
            IDOC_CONTROL        = IDOC_CONTRL
            IDOC_DATA           = IDOC_DATA[]
            DELIVERY_HEAD       = S_KOKO
            DELIVERY_ITEM       = T_KOPO[]
            PACKING_HEAD        = T_VSEK[]
            PACKING_ITEM        = T_VSEP[]
            PROCESSING_STATUS   = F_STAT
       IMPORTING
            WARNING_IGNORE      = F_FLAG
       CHANGING
            PROCESSING_PROTOCOL = T_PROT[]
       EXCEPTIONS
            OTHERS              = 0.
Because by the time you get to this point, the delivery document is created. I believe you need to create the STO order only once the delivery document is created.
Thanks,
Mahesh.

Process Code for Outbound Production Order??

Does anybody know the Process Code for Outbound Production Order??
BASIC Type : LOIPRO01
Message Type : LOIPRO
Regards,
Ravi

Hi Everybody.
There's no standard process code for LOIPRO Outbound Idocs.
This Idocs are threated as master data info, and could only be automatically generated by Data Distribution Model.
BD64.
Anyway, you can define your own Outbound Process Code in WE41 using CLOI_MASTERIDOC_CREATE_LOIPRO FM.
You can choose.
Regards.
Albert.

Process code

Similar Messages

Maybe you are looking for