2007 Feb 26 11:14 AM
Hi,
can any one pls let me know the steps we should fallow in an inbound idoc processing.
I have the messagte type , basic type, process code and i have to create partner profile , pls let me know what are the steps to be fallowed
thanks,
Deepak
2007 Feb 26 11:43 AM
Create the link for the idoc type and message type using transaction WE82.
Create a process code where you assign the function module to be called using transaction WE42.
And create the partner profile using transaction WE20.
Reward u find this useful
Regards,
Sandeep
2007 Feb 26 11:17 AM
Hi,
The steps are:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.
3. Data in Control Record is validate against the Partner Profile.
4. IDoc is generated in Database and syntax check is carried out.
5. IDoc file is deleted once file read.
6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
7. Check for Process Immediately.
If NO
Execute RBDAPP01 Program
Else
Read Process Code from Partner Profile
Process Code Points to Function Module
Application Document Posted.
Regards,
Anji
2007 Feb 26 11:38 AM
Hi
currently i have message type --ORDERSP
basic type ---ORDERS05
process code-----ORDR
this is an EDI inbound idoc so i have to create partner profile for Vendor frorm WE20, please let me know after this what are the steps i have to fallow , as iam new to idocs please give clear process
2007 Feb 26 11:43 AM
Create the link for the idoc type and message type using transaction WE82.
Create a process code where you assign the function module to be called using transaction WE42.
And create the partner profile using transaction WE20.
Reward u find this useful
Regards,
Sandeep
2007 Feb 26 1:00 PM
Hi,
U need to update the Purchase Order based on the idoc.
The Process Code for this development is: ORDR,
Basic IDOC Type: ORDERS05
Function Module: IDOC_INPUT_ORDRSP,
Message type: ORDRSP.
Enhancement: MM06E001
Customer Enhancement: EXIT_SAPLEINM_008
The logic should be written in the Include ZXM06U20.
LOOP AT idoc_data.
CASE idoc_data-segnam.
WHEN 'E1EDP01'.
Move Structure ACKNOW_PO info to Confirmations.
ENDCASE.
ENDLOOP.
Regards
Kannaiah
2007 Feb 27 10:45 AM
Hi Kannaiah,
your answer is correct , this is an Incomming Purchase order confirmation Idoc,
as iam new to idocs iam not sure why we need to write code in the user exit
we have standard
Basic IDOC Type: ORDERS05
Function Module: IDOC_INPUT_ORDRSP,
Message type: ORDRSP.
and Process code:ORDR
in WE42 the process code contains the same function module(IDOC_INPUT_ORDRSP)
and also i need to configure partner profile and give the message type and process code in Inbound parameters in WE20
as per my knowledge i thought the functionmodule will take care of updating EDIDD and EDIDC table with the contents in the Idoc
please let me know how i have to update the EDIDD and EDIDC tables with the incomming idoc.
2007 Feb 27 11:06 AM
Hi Deepak,
Incoming IDOC contains the data related to purchase order confirmations. As you check ME23N, you can find the confirmations in the ITEM level. As these cannot be updated by BAPI, u need to go for Process Code ORDR.
When you check the FM in Process Code, it has the table EDIDD "Internal table with IDoc data" in which all the IDOC data will be there. U need update the Purchase Order according to the IDOC data. This FM will update the purchase order according to the IDOC.
So in the standard FM, it has many standard includes, which SAP wont allow to modify. So u need to use the user exit and you can find the suitable according to the requirement.
In this case, you need to update the PO for the confirmation lines. PO confirmation lines are present in EKET table. SO choose the user exit which has table EKET and EKKO and which has table I_DATA structure EDIDD.
Regards
Kannaiah
2007 Feb 27 11:33 AM
Hi kannaiah,
Thanks a lot ... i think iam clear now ,
will get back if i have some other queries
Deeepak.
2007 Feb 27 11:22 AM
Hi saideepak,
U are using standard idoc type ,basictype and process code.generally the steps for inbound idoc is
1>WE81(CREATE message type)
2>WE31(create segments)
3>WE30(Create basic type)
4>WE57(Attach the FM to basic type and message type)
5>BD51(Attach FM)
6>WE42(Create process code)
7>WE20(Create partner profiles).
As u r using standard idoc so ,u can omit from 1 to 6.Only thing u have to do is create partner profiles in WE20 tcode.
So go to WE20 tcode->Give the reciver Logical system name(LS)and in the inbound parameters give the MESSAGE TYPE AS ORDERS and process code as ORDE.thats it ..
As this is an incoming idoc ,so ur idoc will have data.So the tables EDIDD AND EDIDC are filled only.no need to pass data to it.
regards,
nagaraj