Regarding the Outbound IDOC process

Hi Experts,
Please answers the following questions which i have some doubts in Outbound Process.
1) Which program is resposible to fill the segments of IDOC(Std IDoc) in case of Outbound IDOC Process with message control , Is it FM in Process code or any other FM based on message type( Std Msg)?.
2) Where we need to code or search the exit in Case of extension of basic IDOC type with and without message control?
3)Which prog is responsible to fill the IDOC in case of outbound process without message control but using std basic IDOC.
Regards,
Kali Pramod

Kali,
1. You can search in SE37 using IDOC_OUTPUT* for finding out corresponding function modules. It is based on message types.
2. You can search user exit in above mentioned function module. So first get the correct populating FM & then you can search for Call Customer Function inside the code for user exit.
3.Again ans is same as in point 1.

Similar Messages

How to find the Program that triggered the outbound idoc

Hi,
I need to find the program that triggers a particular Outbound IDoc.
I have the IDoc number/segment/message type.
We need to Debug the Outbound IDoc but we do not know from where the IDoc got triggered.
Is there a way we can find which program triggered it?
Thanks!

Hi Suresh,
Go to tcode WE20, select ur partner profile type, which configured in output type for EDI documents.
On right side, double click on the Message type in outbound parameters.
go to message control Tab, double click on process code variable to see FM triggers for the IDOC.
same as for Inbound also.
Regards
Syed A

Creation of Inbound Idoc for the Outbound Idoc in same client

Hi,
My requirement:
Whenver an PO is created an Outbound IDOC is generated in system ABC with client 100.I want to pass this IDOC data to create an Inbound Idoc for Sales Order(SO) in the same client.
It would be helpful if anyone can answer on how to Transfer the Outbound Idoc after it crosses the port.
I found there is a field for function module in WE21,can this be used to get the requirement done.
Please suggest.
Regards,
Amar

Example of a program that create and post an inbound idoc....maybe that will help you:
report zzinbound_idoc.
data: g_idoc_control_record like edi_dc40 occurs 0 with header line.
data: g_edidd like edi_dd40 occurs 0 with header line.
data: g_e1bpache09 like e1bpache09.
parameter: mode type c default 'A'.
refresh: g_idoc_control_record, g_edidd.
clear:   g_idoc_control_record, g_edidd.
*-Build Control Record -*
g_idoc_control_record-mestyp = 'ACC_DOCUMENT'.   "Message type
g_idoc_control_record-idoctyp = 'ACC_DOCUMENT03'. "IDOC type
g_idoc_control_record-direct = '2'.              "Direction
* Receiver
case sy-sysid.
when 'DE2'.
    g_idoc_control_record-rcvpor = 'SAPDE2'.     "Port
    g_idoc_control_record-rcvprn = 'IDOCLEGACY'. "Partner number
endcase.
g_idoc_control_record-rcvprt = 'LS'.             "Partner type
g_idoc_control_record-rcvpfc = ''.               "Partner function
* Sender
g_idoc_control_record-sndpor = 'A000000002'.      "tRFC Port
case sy-sysid.
when 'DE2'.
    g_idoc_control_record-sndprn = 'IDOCLEGACY'. "Partner number
endcase.
g_idoc_control_record-sndprt = 'LS'.             "Partner type
g_idoc_control_record-sndpfc = ''.               "Partner function
g_idoc_control_record-refmes = 'Customer clearing'.
append g_idoc_control_record.
*-Build Idoc Segments -*
*---E1KOMG
clear g_edidd.
clear g_e1bpache09.
g_edidd-segnam               = 'E1BPACHE09'.
g_edidd-segnum               = 1.
move g_e1bpache09 to g_edidd-sdata.
append g_edidd.
*-Create idoc -*
*-Syncronous
if mode = 'S'.
call function 'IDOC_INBOUND_SINGLE'
    exporting
      pi_idoc_control_rec_40              = g_idoc_control_record
*     PI_DO_COMMIT                        = 'X'
*   IMPORTING
*     PE_IDOC_NUMBER                      =
*     PE_ERROR_PRIOR_TO_APPLICATION       =
    tables
      pt_idoc_data_records_40             = g_edidd
    exceptions
      idoc_not_saved                      = 1
      others                              = 2.
if sy-subrc <> 0.
    message id sy-msgid type sy-msgty number sy-msgno
            with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
*-Asynchronus
else.
call function 'IDOC_INBOUND_ASYNCHRONOUS'
    in background task as separate unit
    tables
      idoc_control_rec_40 = g_idoc_control_record
      idoc_data_rec_40    = g_edidd.
commit work.
endif.
write: / 'Well done!'.

Scheduling inbound and outbound idoc processing

Hi everybody.
I ´d ike to know which is the best way to schecule the outbound and inbound idoc process.
Nowadays we are using this:
INBOUND PROCESSING
- In WE20 the idocs are checked with "Trigger with a background program".
- The program RBDAPP01 is scheduled with a job to trigger the process of the inbound idocs.
OUTBOUND PROCESSING
- The program RBDMIDOC is scheduled to create the idocs than have been created with change pointers.
- The program RSEOUT00 is scheduled with a job to trigger the process of the outbound idocs.
Is there any better option to improve de perfomance????
Edited by: Christian Abad Chico on Nov 13, 2009 10:09 AM

Any answer

Enhancements in Outbound IDoc Processing

Hi,
How do I find the function module where the Outbound IDoc structures are filled.
Basic type: SHP_OBDLV_SAVE_REPLICA02
Message type: SHP_OBDLV_SAVE_REPLICA
Thanks,
Regards,
Morten

go to transaction WE57 and search for messagetype/idoc type.

How to Debug the Outbound IDOC

Dear SDN Members,
How to debug the outbound idoc please.
Thanks in advance
Yerukala Setty

Hi,
IDocs are processed by a function module, which are mapped against in table EDIFCT. When you process an IDoc in transaction BD87 you can put a breakpoint in the function module and it will stop there.For outbound processing it depends on which program is sending the IDoc. For transactional data like purchase orders, the IDoc is created via RSNAST00 which in turn calls a function module assigned to the processing code (BD41).
Thanks,
Asit Purbey.

Re: outbound idoc process

Can someone explain me on outbound idoc process.
I am facing problem with an idoc transimission. From sap its getting triggered and showing status 3 ( Sending to port OK ). But third party is not able to receive.
I am not much aware of the middile ware trasmission runs during idoc transfer.
Please can anyone tell me possible cause of error?

Outbound Idoc process
sap outbound program->outbound ALE program (this takes data from application repository)>Craete master Idoc (master Idoc is a virtual Idoc)->ALE service laye (which takes data from distribution model)>communication Idoc--->communication layer
The status os Idoc will becaome 03 if its pass from the communication layer and it doesnt have any gaurntee that Idoc has reached at receiver end or not.
To varify that Idoc has reached at receiver end we have two advance method
1- TRFC method
2- Auditing method
In TRFC method a standard program, RBDMOIND, is scheduled or executed online to determine whether the communication was successful.
If the Idoc has successfully reached to the destination then the status changed from 3 to 12 else status remains 3.
hope this information helps u.

How to debugg the outbound idoc

Hi all,
I am adding one segment standard Invoic02 outbound idoc.
Executing invoice number ,idoc automaticall y trigger and populate the data.
1)problem is my new adding segment is not populated idoc level.
2)I am testind idoc (WE19) showing a 02 error.
3) How to debugg the outbound idoc.
Thanks
Sreddy

Take a look at your outbound processing code (transaction WE41). When you double click on the entry you are using you can find the function module which is used to process the IDOC. Just set a breakpoint at the beginning of that function module and you can debug the creation of your outbound IDOC.
Hope that helps,
Michael

Where to put break point when debugging the inbound IDOC processing

Hi, Dear Experts,
If IDOC has error and want to debug, which program or function module to put break point when debugging the inbound IDOC processing
Thank you so much!
Helen

It depends on if you have the custom FM or standard FM...Is it MM invoice or FI invoice? ... You can find out your FM by going to partner profile (WE20) for your sender partner and partner function.. Drill down to your partner and the message type and find the inbound process code.. Double clicking on the process code will help you find the FM...
If you don't have access to WE20, You can also put BP into any of the IDOC_INPUT_INVOIC* FM and see if it is getting triggered (assuming your IDOC is standard FM)...

Outbound IDOC process - Using standard or Custom Program

Hi all,
i'm having some doubts regarding IDOC's outbound processing.
I'm trying to understand 2 scenarios:
1- Trigger Standard Outbound IDOC without writting any Z program ou IDOC FM.
It's possible to trigger a outbound idoc for exemple, whenever a sales order is created. To do this is, i suposed i don't need to write any code at all, correct?
What i need to do is create a logical system (SALE), define Transmission protocol (WE20, in here i associate the partner, and the outbound message type? After this point is the idoc automatic triggered?
If not, what is the correct procedure?
2 Trigger Ountbound IDOC using Z program.
Whats is diferent from the point 1 to this situation?
Best regards,
Pedro

Kali,
1. You can search in SE37 using IDOC_OUTPUT* for finding out corresponding function modules. It is based on message types.
2. You can search user exit in above mentioned function module. So first get the correct populating FM & then you can search for Call Customer Function inside the code for user exit.
3.Again ans is same as in point 1.

How to find the outbound idoc function module?(Urgent)

Dear All,
How to identify the outbound function module if there is process code assigned to message type.
For partner profile the mesasge type is assigned and idoc type .This is the only information maintained .
Now my question is how to identify the fucntion module which is getting trigger in the system is there any data maintained in the standard table or any t-code .
Points will be rewarded for right answers.
Thank You.
Regards,
Ravi Ganji

Hi,
If u know the message and basictype then we can know the process code for that message type in transaction code WE64.
if we know process codes then we can know the function modules in transaction codes WE41(Outbound process code) and WE42(Inbound process code).
Each process code is attached with a FM...
Reward if helpful
Regards,
Nagaraj

To send the outbound IDOC DEBMDM from R/3

Hi,
I have created an extension for DEBMDM06 as ZDEBMDM06.
Please sent me the outbound FM and the process code that is used for the above type.
When i checked with the system i got the peocess code DEBM that is relevant for DEBMAS type.
And also the transaction that is used for creating the IDOCS, because BD12 is relvant for DEBMAS idoc type.
please confirm me whether the tcode MDM_CLNT_EXTR is used for sending the IDOC from R/3.
Above mentioned is an outbound IDOC that will be sent from R/3. please suggest me some solution for solving this issue.
Thanks in advance.
Praba

Hello,
As you rightly said, you can use the Transaction BD12 to Send Customer Master Data.
However, if you have a specific requirement to add some Extended Segment / Fields, you can go for a Custom Program / Report in which you can extract all the Customer Master Data required along with the Extended Segment Fields and send it through MASTER_IDOC_DISTRIBUTE. This program can be scheduled for Background Job as and when you want.
Thanks and Regards,
Venkat Phani Prasad Konduri

How to stop the duplicate idoc processing ? whar need to done SAP R/3

Hi All
If the Same Idoc is processed to SAP R/3 then what to do for not processing
the duplicate IDOC ?
Or some thing like this...
If by mistake same idoc processed then how to avoid to process the idoc?
what i need to in SAP R/3 side?
Regards
Kiran lvs

Hi
some thing like this:Using T.code: we19 ...Idoc processed a day ago
                                       today by using the same t.code we19 ..processed the
                                       same idoc, what i sent a day ago.
                                       Here how to stop this duplicate processing ?
I hope this is clear...else pl put a note
regards
Kiran lvs

Debug the Outbound IDoc

Hi,
I have a outbound IDoc.
I would like to reprocess the same and test the FM.
I am going through the Tcode :WE19.
put the IDOC : XXX in the exisiting IDoc field. Execute.
I get to see the IDoc structure and the data.Then i click on the "standard outbound processing".
I would like to get into the FM and debug it.
But once i press "standard outbound processing".
It is giving a pop up which says "start outbound processing of file immediately"
No of IDoc's to be generated.
Receiver port
Port type
output file
etc.
But i would like to get into the debug mode.
Pls advise.

Set ur Break point at your code
now come to VA02 Transaction and use order number.
click on enter
GOTO->HEADER->OUTPUT
Give the output type and print medium should be 6(EDI) or A( ALE)
Click on Further data and select->select send with periodically scheduled job and save it.
Now Come to SE38 and use RSNAST00
Output Application : V1
Object key - order Number ( 10 digit)
Output type - BA00( SAP Standard)
Transmission medium = 6(EDI) ,A(ALE)
Now it will stop at your code.
Reward Points if it is helpful
Thanks
Seshu
Message was edited by:
Seshu Maramreddy
Message was edited by:
Seshu Maramreddy

OutBound IDOC Processing

Hi Experts,
I am getting the following error while sending outbound IDOC (Multiple IDOCS as a single message) to SAP-XI.I am trying to send the IDOC using WE19 transaction and getting the following error.
500 error during parsing of SOAP Header.Status record 02
Thanks
Ajay Garg

HI,
500 error during parsing of SOAP Header.Status record 02
The Idoc Status code 02 indicates as 02---> Error passing data to port
And the 500 error of parsing of SOAP header is internal server error.
HTTP 500 can be any problem at XI. Plz chk all the setting on the XI side.
Check this SAP SOAP Note for FAQ-856597 (Question No 1)
By default, the SOAP adapter sends the SOAP message with the content type text/xml.
When you check "Do not use SOAP envelope", the default contnet type is application/xml.
You can change the content type like this: Go to the SOAP receiver communication channel module tab. Add the module "localejbs/AF_Modules/MessageTransformBean" before the standard module. Add the parameter name Transform.ContentType and value text/xml.
Check out this
/people/varadharajan.krishnasamy/blog/2007/01/09/troubleshooting-soap-message--xi
One way of testing ur scenario
/people/michal.krawczyk2/blog/2005/08/25/xi-sending-a-message-without-the-use-of-an-adapter-not-possible
Can you refer below steps for troubleshooting. it may help you
Troubleshooting IDOC scenario
1. Start with checking the status in sm58 of sender R/3
Follow the steps
No message in found in XI in IDOC to FILE scenario
2. Try deleating the IDoc from IDX2 and refiring the same.
3. Check your RFC destination definition (the one pointing to your XI server) to confirm that it is of type '3' (R/3 system) and not 'T' (TCP/IP).
In your ID, in the Sender Business System --> Adapter Specific Identifiers, give the logical name for the business System pointing to the R3 system
4. Monitor the SM58 in R/3 for IDOC status.
5. Trouble shooting file to IDOC and IDOC to file
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/error%2bhandling%2bin%2bfile-idoc%2bscenario
Refer below links for indepth troubleshooting
File to IDOC, trouble shooting
Thanks
Swarup
Edited by: Swarup Sawant on May 26, 2008 11:15 AM

Regarding the Outbound IDOC process

Similar Messages

Maybe you are looking for