Process code in IDoc processing

Hi!
I can use WE42 to define my own process code, for example ZINV, but where to define its 'behaviour',
which is maybe coding or anything else?
Many thanks,
Aries

Hi Lakeshman,
Thanks for your help.
When define my own process code in WE42, there is a step that assign a function module to my process code at Identification field, but I cannot find my self-defined function module in the dropdown list.
What is the relationship between WE57 and WE42?
And in WE20 inbound processing, there is no basic type just process code, which seems inconsistent to WE57.
Regards,
Aries

Similar Messages

Process code for IDOC Output from MIRO

Hi,
We need to find the Process code for IDOC output to assign Output type in ECC. We need the IDOC output to some other system like PR while doing the invoice Posting (Transaction code MIRO). We tried Using process code SD09 for the IDOC with IDOC Type INVOIC02. In SD09 we are getting error (Update terminated) when we trigger the output while saving in MIRO transaction.
Further we understand that process code SD09 is used for SD billing and Invoice process.
We need your help in
1. getting the correct process code for the IDOC generation for Invoice posting thru MIRO.
2. If we need to configure one process code, let me know the correct function module for the same.
Please Note, we need this as Output Idoc from Invoice Posting MM (MIRO).

Hi Shankar,
Thanks for quick for reply. We have tested this process code with IDoc type - GSVERF03 and message type - GSVERF. It worked for us for MIRO transaction.
we are testing with IDoc type INVOIC02.
once again thanks for sharing the process code.
Regards,
Brahma

How to assign function module with process code in IDOC ?

how to assign function module with process code in IDOC ? and what code i have to write in that function module for custom IDOC ?
helpful answer will be rewarded?

Hi,
First goto transaction we42 -->editing mode --> new entries -->give name of your process code and description --> processing with alv service and function module -->then press enter -->after that enter the name of the function module you want to associate from the drop down and save it.
Thats the way to assign function module with process code.
In that process code we will have the Function modules and Bapi's which will take the data which we are sending through IDOC and then process it.
for example: i am triggering the IDOC for every purchase order created then this process code in the receiver system will take the data which i have enetered in the sender system to create the purchase order and process it and creates the same purchase order in the receiver's system.
Reward if helpful.
with regards,
Syed

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.

T.code wise IDoc list

Hi,
Can we get T.code wise IDoc list...
rgds,
balu

Hi,
Plz check the sequence of trasaction codes that are required for idoc.
Sequence of transaction already done
1.BD54(Create Logical Systems on Sender & Reciever),
2.SALE(Assignment of Logical System to client on Sender & Reciever)
3.SM59(To create RFC destination on Sender only)
Outbound settings:
1.WE31(Create Segments),
2.WE30(Create IDOC types),
3.WE81(Creation of Logical Message type),
4.WE82(To attach message type and idoc type),
5.BD64(To create a distribution model),
6.WE20(To create Partner Profile).
7.WE21(To create Ports)
Write Program to Trigger Idoc from Sender Side.
Inbound settings:
1.WE31(Creation of Segments)
2.WE30(Creation of IDOC Objs)
3.WE81(Creation of Message Types)
4.WE82(TO link Message Types and Idoc Type Objs)
5.WE42(To Create Process Code)
6.BD67(To attach FM to Process Code , On saving it goes to BD51 directly)
6.1 BD51 (To Configure FM as per input)
7.WE57(Assign. of FM to Msg Type and IDOC Type)
8.WE20(To create Partner Profile)
Write code for accepting data from IDOC send by sender . This has to be written in FM source tab with appropriate inport fields
and export fields .
Tips: The name of message type , idoc type , segment type and logical systems name on both sides should be same.
Hope this helps you.
<removed_by_moderator>
thanks,
dhanashri.
Edited by: Julius Bussche on Aug 13, 2008 4:21 PM

Need all transaction codes for idocs

need all transaction codes for idocs

Hi,
ALE IDOC
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
I know how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
BAPI tcode --- BAPI.
Also:
IDOC:
IDOC ADMINISTRATION
WE09 / WE02 IDoc lists according to content. View IDocs via specific IDoc number or business application detail contained within the contents of a segment.
WE05 View IDocs
WE60 IDoc type documentation tool
WE20 Partner profile configuration. Add partner detail together with inbound and outbound relationships. We also incorporate message control on the outbound IDocs. Utilize the organizational units to trap functional errors for further processing.
BD87 Reprocess IDocs in error or waiting for action. (Both inbound and outbound in 4.6. Use BD88 in prior versions)
1.4 IDOC DEVELOPMENT
BD55 Conversion rule user exit. Link conversion rule user exit to the different system \ partner combinations.
WE19 EDI test tool. Use to test inbound Function module changes.
WE31 Segment create
WE30 Create IDoc extension type
WE82 Link Release detail to Extension IDoc Type
WE57 Assign function module to logical message and IDoc type
BAPI: BAPI, SWO1.
Transaction codes Related for IDOC Configurations
WEDI: Area Menu for IDOCs
WE02: Display IDoc
WE19: ALE Test tool
WE30: Development of IDOC Type
WE31: Development of IDOC Segment
WE41: Process Codes, Outbound
WE42: Process Codes, Inbound
WE47: Status Maintenance
WE81: Logical Message Types
WE57: Assignment Messages for Appl. Objs
SM59: RFC Destinations (Display/Maintain)
SALE: Display ALE Customizing
BD54: Maintaining Logical Systems
BD67: Maintain methods (inbound)
BD64: Maintenance of Distribution Model
BD87: Status Monitor for ALE Messages
Reward points if found helpful...
Cheers,
Chandra Sekhar.

37 Status code in IDoc to File Scenario

Hi Experts,
I developed Idoc to file scenario, in the PI side all the design time and configuration objects are good .
while I am testing from SAP backend system (All required configuration steps are also good).
I was send the Vendor information details (CREMAS05) by using the Transaction code WE19 , after that I was test with IDoc list by using Transaction code WE05(IDoc list) I am getting status code 37 . what might be the problem.
please help me.
Thanks in advance,
Regards,
Sudeepth.

Dear All,
For file to idoc scenario is there any possibility to get line items details or xml details i.e the segments and its related field details using reference id, transaction id or interface name or message id in SAP PI 7.0. I know we need to click each and every message in sxi_monitor and look for details.
For SAP(R3 System) I can create a report and set the job for specific time period so automatically it throws the details(like reference no, document date, invoice no from) in ftp path as .csv file. The same ftp path is maintained in program.
I wanted to check FTP--->PI postings and I have set the job at r3 system it is working fine and Im monitoring it too.
Now the end to end scenario is FTP--->PI--->ECC(R3 system). Please help.Many Thanks.

IBAN Code in IDOC

Hi Group
I have a requirement of sending IBAN code in IDOC to bank.
I saw in IDOC segment - E1DB02 BB - Bank details including bank key, bank accounts, Swift Code but there is no IBAN code which is there in Vendor Master - Vendor Bank Information.
Can anybody tell me how to get this?
Regards,
Amit

You can try transaction SE38 - RFFOEDI1 - You will see for selection parameters - Go to Last output control section in that you will see "TRANSFER IBAN"
Select this option and paying company code combination for which you want to transfer IBAN (Mostly Europe) and save as a variant. Use this variant in F110 against program RFFOEDI1.
Regards,
Amit Patel

Process code for Idoc BANK_CREATE01 and BANK_CHANGE01

hi,
I want to create partner profile for Idoc BANK_CREATE01 and BANK_CHANGE01 standard Idocs.
But in transaction we64 , i am not finding the inbound process code for it.
So di i have to create a process code for it??
If yes , how do i create it and also the function module to be created.
kindly help.
Regards,
Loveena

hi ,
To create a partner profile Tcode WE20.
for your inbound or outbound idocs , just add these idocs in outbound or inbound parameters . For Idoc to File or File to Idoc , it is sufficient.
before creating partner profile you have to create port Tcode WE21
hope this will help
regards
HONEY

How to create process code for idoc bank_create01 in testing client

hi,
I am using Idoc BANK_CREATE01 and BANK_CHANGE01 to post idoc to R/3 in inbound side.
there is no standard process code available for this idoc
But there is a function module idoc_input_bank_create which posts data to r/3 from the idoc.
So i created a zprocess code and attached this function module to it.
But all this i have done in the development client , but it is not being reflected in the testing client
And i am not able to create Process code in we42 in testing client since it is not modifiable.
So , is transaction we42 client 42??
Or is there any way that whatver i create in dev client should also reflect in testing client
Please help
Regards,
Loveena

Hi,
While Creating the process code u have to save under transport ID under which id u have stored it,transfer that id into QA system then u can test ur IDOC.
If u have created it under local object then u have to agin store into one tranport id and then transfer it.
Regards,
Phani
Reward points if Helpful

Process code in IDOC..

Hi
can anybody clarify me the term PROCESS CODE..
upto my knowledge ...
a FM wud be attached to this..which wud process the IDOC..
i find N number of Pcodes for a msg type (ORDRSP)..
actually what this process code does in each turn?
thanks in advance...

Hi Raja,
Process code is for identification of a inbound function module in the inbound processing. Now coming to your question, it is not just enough if you have a process code for the corresponding message type but it should also have to be configured in the partner profiles.
For your question which process code would be chosen, depends upon the process code that you have configured for the partner.
For your question no.2 why?, This may be because I want to handle the same message type coming from two different partners differently.
Hope this helps.
Regards,
Srikanth

Process code in idocs

WHat is the purpose of the process code in the inbound processing od IDOCS(WE42)

you need the process code to determine which Function is used for creating/processing the IDoc.
Go to WE20 (Partner) and choose you inbound processing messages.
In the first tab you´´ll find the processing code.
Transaction: WE42 to define the processing code
Tcode: WE57 and BD51 to map the Function to this processing Code.

Process codes for Idoc types

Hi All,
Can you please send me the process codes for the following IDOC types as I could not find them in WE64. Also let me know how did you found out.
IDOC types are:
1) INTERNAL_ORDER_CREATE01
2) PROFITCENTER_CREATE01
3) COSTCENTERGROUP_CREATE01
Urgent help is really appreciated.
Regards,
Shahu

Hi,
1) INTERNAL_ORDER_CREATE01
           Please clarify for which order you are using this.
2) PROFITCENTER_CREATE01 -
           PRCM (PRCMAS)
3) COSTCENTERGROUP_CREATE01
           COSM (COSMAS)
Reward points if useful.
Regards,
Atish

Wht is process code in idoc

plz tell me the meaning and necesity of processcodes(we41 and we42) in idocs.

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 via 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:
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.
If you do not know what process code is relevant for your business process, but you know the message type, then you can display the process code defined for this message type: Choose Documentation ® Process codes in the initial node of the IDoc interface or use the F4 Help in the partner profiles after you have entered the message type.
There are also the process codes for exception handling:
System Process Code - names the workflow which is triggered in inbound or outbound processing when an exception occurs.
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 via a process code.
http://help.sap.com/saphelp_46c/helpdata/en/dc/6b804043d711d1893e0000e8323c4f/content.htm
thanks
mrutyun^

Process code for IDoc

Hi,
I have a function module which is assigned to a Process Code. How can i find the Process code for this Function Module?..Pls help
Ram

Hi Prabha,
If it is Outbound Process Code use WE41.
If it is Inbound Process Code use WE42.
Regards,
Raghav

Process code in IDoc processing

Similar Messages

Maybe you are looking for