Outbound process code

Hi
I need to create outbound Process code for ME22N T code for outbound IDoc
I am using we41 T code to create the above
but i am unable make
any suggestions plz
Regards
Rasheed

Hi,
i think you no need to create 'process code' if u r using standard outbound F.M.
this is the way you can check the corresponding standard 'Process Code'.
If you know any F.M or Message type or Basic type, then from WE57 you can find the corresponding process code.
Goto WE57 and make use position button and u will get one popup screen and then press F4 on any field then it will open the other screen in that screen make search for process code by giving the input values in Ctr+F search.
How to create Process code for outbound.
-Goto WE41- select change mode- then press 'new entries' button, then u will get one screen in that give name and discription for new 'Process code' and assign corresponding F.M, select the radio buttons of 1-process with ALE service and 2-process with F.M.
then press Save button it will ask the customer request not workbech request save under customer request.
This is the way how to create process code.
Reward with points if useful.
Regards,
Vijay

Similar Messages

Required Outbound Process Code for MessageType LOIPRO (Basic type-LOIPRO01)

Hi EDI Gurus,
I need to know the outbound Process Code for MessageType LOIPRO (Basic type-LOIPRO01).

Hi,
there is no process code for MessageType LOIPRO .
check the below link u will get the clear idea.
Re: Process Code for Outbound Production Order??
Reward if helpful.
Regards,
Nagaraj

Function Module for Outbound process code

Hi,
I have a scenario in which i have to send MBGMCR02 Idoc from SAP to XI.
I created a new Outbound process code and now I have to code the function module that populates data into the segments.
Does anyone have sample code for this, i.e code to put in the finction module of an outbound process code?

hi...
please find the below code.
*& Report ZPROGRAM11
REPORT ZPROGRAM11.
tables : likp,vbuk,vbfa,ibin,vbap,vbak,kna1.
types : begin of iy_tab,
 vbeln type vbfa-vbeln,
 vbelv type vbfa-vbelv,
 posnv type vbfa-posnv,
 end of iy_tab.
types : begin of iy_tab1,
vbeln type vbuk-vbeln,
wbstk type vbuk-wbstk,
end of iy_tab1.
types : begin of iy_tab2,
vbeln type vbak-vbeln,
kunnr type vbak-kunnr,
vkorg type vbak-vkorg,
vtweg type vbak-vtweg,
spart type vbak-spart,
end of iy_tab2.
data : i_ibase type ib_ibase.
data : i_kunnr type vbak-kunnr.
data : it_tab type table of iy_tab with header line,
it_tab1 type standard table of iy_tab1 ,
wa_tab1 type iy_tab1,
it_tab2 type standard table of iy_tab2 ,
wa_tab2 type iy_tab2.
data : t_edidd type standard table of edidd .
data : t_edidc type edidc.
data : t_edidc1 type standard table of edidc .
data : wa type edidd.
data : wa1 type e1edl20.
data : wa2 type zibase.
data : wa3 type e1edl32.
data : wa4 type e1edl44.
data : wa5 type e1edl37.
data : wa6 type e1edl28.
data : wa7 type e1edl30.
data : wa8 type e1edl24.
data : wa9 type e1adrm1.
data : begin of it_tab3 occurs 10,
 vbeln type iy_tab-vbelv,
 posnr type iy_tab-posnv,
 i_ibase type ib_ibase,
 end of it_tab3.
types : begin of iy_tab4 ,
 valfr type ibin-valfr,
 ibase type ibin-ibase,
 amount type ibin-amount,
 unit type ibin-unit,
 end of iy_tab4.
 data : it_tab4 type standard table of iy_tab4,
 wa_tab4 type iy_tab4.
data : begin of it_tab5 occurs 10,
 vbeln type vbfa-vbelv,
 posnr type vbfa-posnv,
 ibase type ibib-ibase,
 valfr type ibin-valfr,
 amount type ibin-amount,
 unit type ibin-unit,
 matnr type vbap-matnr,
 kunnr type vbak-kunnr,
 vkorg type vbak-vkorg,
 vtweg type vbak-vtweg,
 spart type vbak-spart,
 name1 type kna1-name1,
 end of it_tab5.
 types : begin of iy_tab6,
 vbeln type vbap-vbeln,
 posnr type vbap-posnr,
 matnr type vbap-matnr,
 end of iy_tab6.
 data : it_tab6 type standard table of iy_tab6,
 wa_tab6 type iy_tab6.
types : begin of iy_tab7,
 kunnr type kna1-kunnr,
 name1 type kna1-name1,
 end of iy_tab7.
data: it_tab7 type standard table of iy_tab7,
 wa_tab7 type iy_tab7.
 data : wa_table type ytable1.
selection-screen: begin of block b1 with frame title text-t00.
parameters: p_vbeln type vbfa-vbeln.
selection-screen: end of block b1.
start-of-selection.
select vbeln vbelv posnv from vbfa into table it_tab
where vbeln = p_vbeln.
if sy-subrc eq 0.
 loop at it_tab.
 select vbeln wbstk from vbuk into table it_tab1
 for all entries in it_tab
 where vbeln = it_tab-vbeln.
 endloop.
endif.
loop at it_tab1 into wa_tab1.
 if wa_tab1-wbstk = 'C'.
 loop at it_tab.
 call function 'IBSD_CREATE_IBASE'
 exporting
 i_vbeln = it_tab-vbelv
 i_posnr = it_tab-posnv
 i_as_sold = '0'
 i_as_build = '0'
 i_capid = '0'
 I_CHANGE = ' '
 i_commit = 'X'
 I_COMMIT_WAIT = ' '
 importing
 e_ibase = i_ibase
 exceptions
 order_not_found = 1
 position_not_found = 2
 nothing_to_do = 3
 too_much_to_do = 4
 missing_authorization = 5
 foreign_lock = 6
 others = 7
 if sy-subrc <> 0.
 message id sy-msgid type sy-msgty number sy-msgno
 with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
 else.
 move it_tab-vbelv to it_tab3-vbeln.
 move it_tab-posnv to it_tab3-posnr.
 move i_ibase to it_tab3-i_ibase.
 append it_tab3.
 if sy-subrc eq 0.
 select valfr ibase amount unit from ibin into table it_tab4
 for all entries in it_tab3
 where ibase = it_tab3-i_ibase.
 if sy-subrc eq 0.
 select vbeln posnr matnr from vbap into table it_tab6
 for all entries in it_tab3
 where vbeln = it_tab3-vbeln and posnr = it_tab3-posnr .
 if sy-subrc eq 0.
 select vbeln kunnr vkorg vtweg spart from vbak into table it_tab2
 for all entries in it_tab
 where vbeln = it_tab-vbelv.
 sort it_tab2 by vbeln.
 delete adjacent duplicates from it_tab2 comparing all fields.
 if sy-subrc <> 0.
 select kunnr name1 from kna1 into table it_tab7
 for all ENTRIES IN it_tab2
 where kunnr = it_tab2-kunnr.
 endif.
 endif.
 endif.
 endif.
 endif.
 endloop.
 else.
 exit.
 if sy-subrc eq 0.
 endif.
 endif.
endloop.
loop at it_tab3.
 move it_tab3-vbeln to it_tab5-vbeln.
 move it_tab3-posnr to it_tab5-posnr.
 move it_tab3-i_ibase to it_tab5-ibase.
 if sy-subrc eq 0.
 read table it_tab4 into wa_tab4 with key ibase = it_tab3-i_ibase.
 move wa_tab4-valfr to it_tab5-valfr.
 move wa_tab4-amount to it_tab5-amount.
 move wa_tab4-unit to it_tab5-unit.
 if sy-subrc eq 0.
 read table it_tab6 into wa_tab6 with key vbeln = it_tab3-vbeln posnr = it_tab3-posnr.
 move wa_tab6-matnr to it_tab5-matnr.
 if sy-subrc eq 0.
 read table it_tab2 into wa_tab2 with key vbeln = it_tab3-vbeln.
 move wa_tab2-kunnr to it_tab5-kunnr.
 move wa_tab2-vkorg to it_tab5-vkorg.
 move wa_tab2-vtweg to it_tab5-vtweg.
 move wa_tab2-spart to it_tab5-spart.
 if sy-subrc eq 0.
 read table it_tab7 into wa_tab7 with key kunnr = wa_tab2-kunnr.
 move wa_tab7-name1 to it_tab5-name1.
 append it_tab5.
 endif.
 endif.
 endif.
 endif.
 append it_tab5.
 endloop.
 loop at it_tab5.
 move it_tab5-vbeln to wa_table-vbeln.
 move it_tab5-kunnr to wa_table-kunnr.
 move it_tab5-vbeln to wa_table-vbeln.
 move it_tab5-ibase to wa_table-ibase.
 move it_tab5-matnr to wa_table-matnr.
 move it_tab5-valfr to wa_table-valfr.
 move it_tab5-unit to wa_table-unit.
 move it_tab5-amount to wa_table-amount.
 move it_tab5-vkorg to wa_table-vkorg.
 move it_tab5-vtweg to wa_table-vtweg.
 move it_tab5-spart to wa_table-spart.
 move it_tab5-name1 to wa_table-name1.
 insert ytable1 from wa_table.
 endloop.
*INSERT ytable1 FROM TABLE it_tab5.
 loop at it_tab5.
 wa1-vbeln = it_tab-vbeln.
 wa1-vkorg = it_tab5-vkorg.
 wa-segnam = 'E1EDL20'.
 wa-sdata = wa1.
 wa-hlevel = 2.
 append wa to t_edidd.
loop at it_tab3.
 wa2-i_ibase = it_tab5-ibase.
 wa2-i_qty = it_tab5-amount.
 wa2-i_dat = it_tab5-valfr.
 wa-segnam = 'ZIBASE'.
 wa-sdata = wa2.
 wa-hlevel = 3.
 append wa to t_edidd.
 endloop.
wa9-name1 = it_tab5-name1.
wa-segnam = 'E1ADRM1'.
wa-sdata = wa9.
wa-hlevel = 3.
append wa to t_edidd.
 wa-segnam = 'E1EDL28'.
 wa-sdata = wa6.
 wa-hlevel = 3.
 append wa to t_edidd.
 wa-segnam = 'E1EDL30'.
 wa-sdata = wa7.
 wa-hlevel = 4.
 append wa to t_edidd.
 wa3-kunnr = it_tab5-kunnr.
 wa-segnam = 'E1EDL32'.
 wa-sdata = wa3.
 wa-hlevel = 5.
 append wa to t_edidd.
 wa8-meins = it_tab5-unit.
 wa8-vtweg = it_tab5-vtweg.
 wa8-spart = it_tab5-spart.
 wa-segnam = 'E1EDL24'.
 wa-sdata = wa8.
 wa-hlevel = 3.
 append wa to t_edidd.
 wa-segnam = 'E1EDL37'.
 wa-sdata = wa5.
 wa-hlevel = 3.
 append wa to t_edidd.
 wa4-vbeln = it_tab5-vbeln.
 wa4-posnr = it_tab5-posnr.
 wa4-matnr = it_tab5-matnr.
 wa-segnam = 'E1EDL44'.
 wa-sdata = wa4.
 wa-hlevel = 4.
 append wa to t_edidd.
 endloop.
 t_edidc-mandt = sy-mandt.
 t_edidc-direct = '1'.
 t_edidc-rcvpor = 'A000000062'.
 t_edidc-rcvprt = 'LS'.
 t_edidc-rcvprn = 'O2C_ASSET'.
t_edidc-rcvpfc = 'LS'.
 t_edidc-sndpor = 'SAPSIT'.
 t_edidc-sndprt = 'LS'.
 t_edidc-sndprn = 'T90CLNT090'.
t_edidc-sndpfc = 'LS'.
 t_edidc-mestyp = 'DELVRY'.
 t_edidc-idoctp = 'DELVRY03'.
*t_edidc-rcvpfc = 'LS'.
t_edidc-sndpfc = 'LS'.
 t_edidc-cimtyp = 'ZDELVRY03'.
 append t_edidc to t_edidc1.
 call function 'MASTER_IDOC_DISTRIBUTE'
 exporting
 master_idoc_control = t_edidc
 OBJ_TYPE = ''
 CHNUM = ''
 tables
 communication_idoc_control = t_edidc1
 master_idoc_data = t_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.
 else.
 CALL FUNCTION 'DB_COMMIT'
 CALL FUNCTION 'DEQUEUE_ALL'
 EXPORTING
 _SYNCHRON = ' '
 COMMIT WORK.
 endif.
 endloop.

What is outbound process code for quotation

hi
what is outbound process code for quotation

Process code for outbound processing - Code which identifies the type of data which is to be sent via the IDoc interface.
Use - 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).
Check with tcode WE41
Process code SD12 - QUOTES: Quotation
Regards,
maha

Outbound process code for MBGMCR02

Hello Experts:
    I need to send out material movement (document) information using IDOC. I found MBGMCR02 is a suitable one but the process code is inbound.
    I read some thread, it said you can create a new outbound process code. But I don't know exactly how to do it.
    Can anyone share some advice?
    Thanks a lot.
Dennis

Hi Dennis,
To solve this problem create the outbound process code using the following method:
Goto txn WE41 : Create a new outbound process code say ZMMGRO and assign your message type MBGMCR to this.
Also maintain a FM say ZMBGMCR_IDOC_OUPUT which process the IDOC in the outbound side.
The FM signature should typically look like this:
""Local Interface:
*" IMPORTING
*"     VALUE(OBJECT) LIKE NAST STRUCTURE NAST
*"     VALUE(CONTROL_RECORD_IN) LIKE EDIDC STRUCTURE EDIDC
*" EXPORTING
*"     VALUE(OBJECT_TYPE) LIKE WFAS1-ASGTP
*"     VALUE(CONTROL_RECORD_OUT) LIKE EDIDC STRUCTURE EDIDC
*" TABLES
*"      INT_EDIDD STRUCTURE EDIDD
*" EXCEPTIONS
*"      ERROR_MESSAGE_RECEIVED
*"      DATA_NOT_RELEVANT_FOR_SENDING
TABLES: MKPF, MSEG.
data wa_mkpf type MKPF.
data it_mseg type TABLE OF MSEG.
data wa_mseg like LINE OF it_mseg.
data wa_E1BP2017_GM_HEAD_01 type E1BP2017_GM_HEAD_01.
data wa_E1MBGMCR type E1MBGMCR .
data wa_E1BP2017_GM_ITEM_CREATE type E1BP2017_GM_ITEM_CREATE.
data wa_E1BP2017_GM_CODE type E1BP2017_GM_CODE.
data wa_E1BP2017_GM_ITEM_CREATE1 type E1BP2017_GM_ITEM_CREATE1.
data wa_E1BP2017_GM_SERIALNUMBER type E1BP2017_GM_SERIALNUMBER.
data wa_edidd type edidd.
Create Control Record **********
move CONTROL_RECORD_IN to CONTROL_RECORD_OUT.
control_record_out-direct = '1'.
control_record_out-serial = sy-datum.
control_record_out-serial+8 = sy-uzeit.
Fill Segment data from MKPF & MSEG ******
clear wa_edidd.
clear wa_E1MBGMCR.
move wa_E1MBGMCR to wa_edidd-sdata.
wa_edidd-segnam = 'E1MBGMCR'.
append wa_edidd to int_edidd.
Select single * from MKPF into wa_mkpf where
mblnr eq OBJECT-OBJKY+0(10)
and mjahr eq OBJECT-OBJKY+10(4).
clear wa_edidd.
clear wa_E1BP2017_GM_HEAD_01.
wa_E1BP2017_GM_HEAD_01-PSTNG_DATE = wa_mkpf-BUDAT.
wa_E1BP2017_GM_HEAD_01-DOC_DATE = wa_mkpf-BLDAT.
wa_E1BP2017_GM_HEAD_01-BILL_OF_LADING = wa_mkpf-FRBNR.
wa_E1BP2017_GM_HEAD_01-PR_UNAME = wa_mkpf-USNAM.
wa_E1BP2017_GM_HEAD_01-HEADER_TXT = wa_mkpf-BKTXT.
move wa_E1BP2017_GM_HEAD_01 to wa_edidd-sdata.
wa_edidd-segnam = 'E1BP2017_GM_HEAD_01'.
append wa_edidd to int_edidd.
SELECT * from mseg INTO TABLE it_mseg where
mblnr eq OBJECT-OBJKY+0(10)
and mjahr eq OBJECT-OBJKY+10(4).
loop at it_mseg into wa_mseg.
CLEAR wa_edidd.
CLEAR wa_E1BP2017_GM_ITEM_CREATE.
wa_E1BP2017_GM_ITEM_CREATE-MATERIAL = wa_mseg-MATNR.
wa_E1BP2017_GM_ITEM_CREATE-PLANT = wa_mseg-WERKS.
wa_E1BP2017_GM_ITEM_CREATE-STGE_LOC = wa_mseg-LGORT.
wa_E1BP2017_GM_ITEM_CREATE-BATCH = wa_mseg-CHARG.
wa_E1BP2017_GM_ITEM_CREATE-MOVE_TYPE = wa_mseg-BWART.
wa_E1BP2017_GM_ITEM_CREATE-STCK_TYPE = wa_mseg-INSMK.
wa_E1BP2017_GM_ITEM_CREATE-SPEC_STOCK = wa_mseg-SOBKZ.
wa_E1BP2017_GM_ITEM_CREATE-VENDOR = wa_mseg-LIFNR.
wa_E1BP2017_GM_ITEM_CREATE-ENTRY_QNT = wa_mseg-MENGE.
wa_E1BP2017_GM_ITEM_CREATE-ENTRY_UOM = wa_mseg-ERFME.
wa_E1BP2017_GM_ITEM_CREATE-PO_NUMBER = wa_mseg-EBELN.
wa_E1BP2017_GM_ITEM_CREATE-PO_ITEM = wa_mseg-EBELP.
move wa_E1BP2017_GM_ITEM_CREATE to wa_edidd-sdata.
wa_edidd-segnam = 'E1BP2017_GM_ITEM_CREATE'.
append wa_edidd to int_edidd.
endloop.
ENDFUNCTION.
Do remember to maintain the message control in WE20 where you maintain this outbound code against your output type.
Hope this helps!

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.

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

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^

Process code for 869(EDI ) Order Status Inquiry Message type.

Hi Gurus,
Please can any one help in providing Process Code for 869 Order Status Inquiry Message type.
Thanks,
Sudhakar

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.

Query for Outbound Processing through change pointers

Hi,
I have a reduced Message type for HRMD_A07, for which change pointers are activated. So whenver the changes are tracked, it sends all the changes into 1 IDOC. My requirement is to send Employee wise single IDOC, rather than collection of all the changes at once.
Any inputs would be helpful.
Regards,
Heena

Hi
Since change pointers are specific to the fields based on the change documents for that so i dont think that you may get the Idoc details based on the emplyee.
1.To get the desired ouput we have to either schedule the program RBDMIDOC for lesser intervals of time so that it can collect the data regularly.
2.Based on the chages updated in CDHDR or CDPOS we have to update the details in the user exits for the outbound process code.
3.Else you collect the changes from CDHDR and CDPOS employee wise and manullay populate the idoc.
Thanks & Regards
Jyo

Process code for extended idoc

Hi,
If we are creating an extended idoc, do we have to assign a new process code to it ?
Or will the process code and the associated function module for the basic type work as well for the extended idoc ?

Process code will come in to picture when you deal with IDOCS .. you need to assign a code which internally will have a Function module or a Include, that will have entire code to run your bussiness for an IDOC or EDI or ALE.
Process Code is a different name for specific purposes like function module. IDocs are written in this process.
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
Inbound Process Code - names the function module or workflow which reads the IDoc data and transfers the data to the application document.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b7d6243d711d1893e0000e8323c4f/content.htm
Enter transaction WE30 (ALE->Extension-> IDOC types->Maintain Idoc type)
Type in your name of the extended IDOC type (usually starting with 'Z') and click on the Basic IDoc type, click the create icon.
Click on Create new and enter a description and press enter.
Click on ZIDOCTYPE01 and then on the Create icon.
Enter ZIDOCTYPE as the segment type, click on Segment Editor.
Enter a description for your segment type and create.
Enter a description for your segment, enter each field required in your IDoc and press enter to validate.
Save and generate, press back
To release the segment choose Goto, Release from the menu.
Check the box on the line of your segment.
Save, back and enter.
Your Idoc type structure should be displayed with your new segment.
Save and back.
To release the Idoc type choose Extras, Release type from the menu and Yes.
Reward points if useful.

Process code's function module required for the IDOC Message type PROACT

Hi,
I am trying to trigger an IDOC from ME32K transaction which will carry my Contract agreement details to XI. The IDOC I am using for this purpose is PROACT.PROACT01. But I couldn't find the outbound process code / Function module for the process code associated to this IDOC message type.
Pls help me out....
Thanks,
Ram Kalyan

I checked table EDIFCT for the message type and found this:
Function module Function type Basic type Message Type
IDOC_INPUT_PROACT F PROACT01 PROACT
Oops...I think you are looking for outbound..Ignore

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

What is the Process code for IDoc SISCSO01

Hi all,
I am using 4.6c version.
I am going for an outbound IDoc SISCSO01 for sales Order confirmation.
I want the process code (we41) which suits this IDoc SISCSO01.
Can you please help to get the process code so that my IDoc can be sent succesfully.
Best Regards,
Gangolu

Hi Gangolu,
I don't think there is an outbound process code for IDoc type SISCSO01.
But you can generate the IDoc with this FM MCV_STATISTICS_ALE_OUT_ORDER. But you still need to setup partner profile, distribution model and etc.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

Outbound process code

Similar Messages

Maybe you are looking for