02-08-2005 4:23 PM
Wrote programs that calls IDOC_INPUT_PORDCR1. The PO is created but the IDOC is not. This should be same process as for IDOC_INPUT_FIDCC1 for which I saw some postings. I did the following setup:
1. Create RFC destination R3DLS150
2. Create tRFC port ( RFC dest = R3DLS150)
3. Create Partner profile R3DLS150
--> Inbound: Message Type: PORDCR1
4. Assigned FM IDOC_INPUT_PORDCR1 to Msg type/Idoc Type: PORDCR1/PORDCR101 using tcode WE57
5. Maintained Characteristics for FM using BD51
Note: The one thing I am unsure of are the sender/receiver parameters in structure EDIDC of the FM
Thanks
02-08-2005 4:43 PM
Hi,
If you look at the code of this function module, it is directly calling a BAPI to create the PO. So if you call this function module directly in some custom program and pass all the IDOC segment details to it, then the IDOC will not be created. It looks like this is called post-Idoc creation in a normal EDI scenario.
Srinivas
02-08-2005 4:43 PM
Hi,
If you look at the code of this function module, it is directly calling a BAPI to create the PO. So if you call this function module directly in some custom program and pass all the IDOC segment details to it, then the IDOC will not be created. It looks like this is called post-Idoc creation in a normal EDI scenario.
Srinivas
02-08-2005 4:47 PM
Raynald,
This function module will not create an Idoc. This function will be used by an inbound idoc to create a PO.