RE: Posting OUTBOUND idocs

Hello IDOC gurus,
I am creating OUTBOUND idocs in the background using function module MASTER_IDOC_DISTRIBUTE. My question is will this function module process the idoc or do I have to run program RSEOUT00 as a batch job to process the idoc. If this is the case how do I monitor error messages. I need to get them into the application log which I can do if FM MASTER_IDOC_DISTRIBUTE. will do the job.
Please advise
Thanks

I am creating OUTBOUND idocs in the background using function module MASTER_IDOC_DISTRIBUTE. My question is will this function module process the idoc or do I have to run program RSEOUT00 as a batch job to process the idoc.
Yes, You will have to run RSEOUT00 as periodic job
If this is the case how do I monitor error messages. I need to get them into the application log which I can do if FM MASTER_IDOC_DISTRIBUTE. will do the job.
BD87

Similar Messages

Configuring shipping point as Trigger point for posting outbound idoc

Hello All,
I have a requirement that on saving an Outbound Delivery(VL02N), an Outbound Idoc should be posted...but the condtion for posting the idoc should be its shipping point. I am not sure how to configure shipping point as the trigger point for the idoc.
Please suggest.
Thanks for your co-operation.
Regards
Anand

Hi Anand,
1. Go to transaction: NACE & select application V2 and click on output types.
2. change display <->Change mode.
3. select LAVA and press F6 (to copy Standard output type LAVA to ZLAV).
4. Give ur Z name for the new custom output type.
5. change access sequence from 0005 to 0012(shipping point).
6. Press ENTER and click copy all.
7. Now goto trasaction VV21, give the created output type name. ENTER
8. Maintain entries, shipping point, customer#, Medium as '6' ...etc
Now try VL01N with the given shipping point and check the output ZLAV has been triggered or not?
Let's see, if we miss any configs still!
Keep this as reference:
http://www.erpgenie.com/sapedi/messagecontrol.htm
Reddy

Outbound IDOC in status 12

Hi all,
We have posted outbound IDOC from SAP R3 system to the middleware. Middleware system has received all the IDOC except few(2) idocs and in the very next day again they confirmed that they have not received 3 idocs.
missing idocs were manually processed to have a immediate solution.
we would like to konw how to trouble shoot this scenario?
Following checks were done from our side.
1.There are no entries listed in SM58(tRFC queue)
2.No corresponding entries in the table ARFCRSTATE
3.No network issues.
4.No clue in the Gateway trace.
Is there a way to trace the IDOC stats??
Clara

Hi,
Status 12 means that the IDoc has been passed over to the receiving system.
The report RBDMOIND checks that the transaction ID for all IDocs in status 03 are not stuck in the RFC layer If no entry is found, the status is changed to 12.
The receiving system has not acknowledged that this specific IDoc has been received, it is only an indicator that the RFC call is not pending.
aRs

Real processing timestamp of tRFC in outbound IDOCs

We post outbound IDOCs directly via tRFC. Due to heavy load, processing is extremely asynchronous. The timestamp when the tRFC is realeased is loggend in the IDOC status record, but I want to know when it is really processed for trouble shooting reasons. Is there any way to find that out?
Thanks, Manfred

Hi Manfred,
This is indeed a pain. In my experience, you will not be able to get a status record entered at the actual time of sending.
A workaround I have used in the past is report RBDMOIND which will update the IDOC status from 03 to 12 if the corresponding tRFC packet has been processed (ie. is not there anymore).
Whilst it's better than nothing, it still won't give the true picture because the date/time of the status 12 record is the date/time of the RBDMOIND run.
The other alternative, which takes a bit more effort, is to have the receiver (such as Business Connector or XI), send back an audit IDOC (ALEAUD01) when the IDOC has been processed. This allows you to update the IDOC status.
Cheers,
Scott

There is large time differnce in Outbound IDoc's for Interest Run posting

Hi Experts,
When i posting Interest Run (T.code : FINT) i am executing for a range of Customers(For 4500 Customers)
using Background Job it took nearly 3 days to execute the job in Production and i found that there is
no Partner Profile in WE20,IDoc's went in Error.Until this its fine.
The major problem is there are group of 100 idoc's created in no time span and it took 4 hrs time gap to create
another idoc 100 more idoc's.
In between these 2 bunch of idoc's another 700 idoc's created for different message types.
Can you please let me know why there is that much time gap for the same message type for Interest Run.
Thanks in Advance.
Regards,
Sudhakar Reddy Allam.

Bhishma,
Just clarrification for you...when you said..
"R/3 sends an IDOC with IDOC number 100. XI (by default) submits this IDOC to the 3'rd party system with IDOC number 200 (it's own internally generated number)."
Here Idoc number 100 is outbound idoc from R/2 where as Idoc number 200 is inbound idoc...n they are totally different idocs..not same
I think there is work around...while mapping data from XI --> 3rd party assign / store outbound idoc in one of the unused field of inbound idoc...and while mapping back use this field to map it back...I think this will work.
Let us know the result.
Nilesh

Post inbound as well as outbound IDOCs through a report

Hi all,
I have a specific requirement where i need to post an IDOC through a report which ressemble to WE05. This requirement implies for Inbound as well as Outbound for all message types. Can anyone let me know how can this be achieved. Please let me know if this can be acheived through any FM or method.
Regards
Simin.R

Hi,
To create a new inbound idoc use the following function module:
IDOC_INBOUND_SYNCHRONOUS
To Create a outbound idoc use the function module
MASTERIDOC_CREATE_* - search and decide based on your requirement.
Regards,
Baburaj

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!'.

FM for ORDERS05 Outbound Idoc.

Hi,
I have to post an idoc of basic type ORDERS05 from a custom program.
I have populated the fields for control header and the data section of the idoc.I tried using the FM IDOC_OUTPUT_ORDERS to post the idoc,but when I went and checked in WE05,there were no idoc created.I don't understand why the idoc's are not been created.Could you help me in knowing how to use the FM IDOC_OUTPUT_ORDERS or if there are any other FM's to post an outbound idoc.
Please reply asap.
Thanks,
Sandeep.

Hi,
There is a exit in the FM IDOC_OUTPUT_ORDERS line no 50... double click on the '001' it will take u to the Function Module EXIT_SAPLEINM_001... there click on the Zprogram ...
The FM has EKKO table fields has a Impirting parameter .
u write a code in that Z include program
u have to call the FM MASTER_IDOC_DISTRIBUTE in the program
which creates the IDOC
Thanks,
Manjunath MS

Outbound IDoc Error: Status Code 37 'Sender Port' is invalid

Hi
I have an Error when the Outbound IDoc is triggered.
It shows that 'Sender Port in Control Record is invalid'.
Status Code: 37.
I know that there are some issues with the Sender Port Definition.
Please help me out to solve this problem using some checkpoints at each and every step.
Reward Points Assured.
Regards,
Baburaj

Hi Baburaj Manickam
Good
Follow this simple procedure
1) Send an outbound IDOC data(MATMAS) to a flat file on client1(SENDER).
- Create File Port (WE21) for outbound file.
- Maintain Distribution Model (BD64) for sender ->receiver system.
- Create Partner Profile (WE20) for logical system.
- You can use this program RBDSEMAT (t/code BD10) to generate IDoc MATMAS file(s).
_ Then you can FTP the file(s) to receiver system.
2) Upload the flat file as an IDOC on the inbound sytem
which is Client2(RECIEVER).
- Create File Port (WE21) for inbound file.
- Maintain Distribution Model (BD64) for receiver -> sender system.
- Create Partner Profile (WE20) for logical system.
- You can use this program RSEINB00 to upload IDoc MATMAS file(s).
INBOUND IDOC PROCESSING:
Firstly attach your idoc to a process code.
In the process cod you can tell the system that the specified program should be triggered whenever an idoc of that type comes to the system.
Then you want to have a Z-function module for your idoc processing, if I understand correctly.The steps should be:
1. Create a z function module for idoc inbound posting (copy from a function module idoc_input_*).
2. Set Function Modules as Inbound: - Transaction BD51
3. Assign Function Modules to Logical Messages and Idoc types:- Transaction WE57
4. Create process codes : Transaction WE42, and link the z-function module.
5. Create partner profile: transaction WE20 and attach the message type and process code.
6. In the Z- function module, extract data from the idoc segments, do whatever processing you want to do, and then call BAPI_CREATE_SALES_ORDER_FROMDAT2.
Try the Trasaction WE19 for testing your inbound and outbound IDOCs
Good Luck and Reward me for the same
Thanks
Ashok.N

XI generates own IDOC numbers in outbound IDOC

Hello, The scenario we have is R/3 --> XI --> 3'rd party (via IDOC rcvr adapter) AND then SYSTAT back from the 3'rd party to R/3 via XI.
Example: R/3 sends an IDOC with IDOC number 100. XI (by default) submits this IDOC to the 3'rd party system with IDOC number 200 (it's own internally generated number).
Accordingly, the 3'rd party responds back with a status IDOC, SYSTAT, containing IDOC 200 in the E1STATS ==>DOCNUM field.
This is now a problem since if XI submits the SYSTAT as received from the 3'rd party, it has 200 in the DOCNUM field and this fails in R/3 since there is no original IDOC with number 200.
This can be solved if XI is able to pass the original number 100 through to the 3'rd party system (since then when the 3'rd party responds it will send a SYSTAT with IDOCNUM as 100 back, which will setup correctly in R/3).
I have gone through the other pertinent posts and none of them have this specific problem / offer a solution. I'm hoping I have missed something as this seems to be a pretty basic requirement.
Thank you for the time.
Some additional details...
- 3'rd party is non SAP.
- In the IDOC rcvr adapter we have flags 'Apply Control Record Values from Payload', 'Take Sender from Payload' and 'Take Receiver from Payload' fields checked.
- We have not checked any flags in the Rcvr Agreement.
- We are not using BPM and do not have a way to correlate the inbound 200 with the original 100 that went out.

Bhishma,
Just clarrification for you...when you said..
"R/3 sends an IDOC with IDOC number 100. XI (by default) submits this IDOC to the 3'rd party system with IDOC number 200 (it's own internally generated number)."
Here Idoc number 100 is outbound idoc from R/2 where as Idoc number 200 is inbound idoc...n they are totally different idocs..not same
I think there is work around...while mapping data from XI --> 3rd party assign / store outbound idoc in one of the unused field of inbound idoc...and while mapping back use this field to map it back...I think this will work.
Let us know the result.
Nilesh

Validation on outbound idoc

Hello team
I have the below requirement now. please check and suggest me
1. i am sending outbound MATMAS05 idoc from SAP system. but i want to do few validations on the data of idoc (for example i will check the value of plant data with some other value of the table). if my checking is success then only i need to create outbound idoc and send it to downstream systems.
So now i want to know where i need to write the code which performs the validations against the data before creating/posting of idoc.
Please suggest me.
Regards
Raj

Vinod
Dont mine of asking little more clarification. you mean to say go MM01 and find out the package (ie MGA) and then goto SMOD and findout the exits right.
But when check in this way, i didnt find the enhancment MGV00001 you have provided.
please tell me the procedure to check in a detail way. i want to know how can we check for the related enhancments for any idoc type. please tell me to check for MATMAS05 as an example, i will use the same techinque for any idoc type.
Regards
Raj

Error oocuring after posting the IDOC

Hi
i am getting a error in a scenario
the scenario is Idoc to file. when we post the IDoc, its getting posted successfully. but the pipiline is getting failed at the inbound message when monitoring in SXMB_MONI.
i am getting the following error
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Category>XIAdapter</SAP:Category><SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_NO_REQUEST</SAP:Code>
<SAP:P1/><SAP:P2/><SAP:P3/><SAP:P4/>
<SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/>
<SAP:Stack>ALEAUDIT IDoc cannot find request IDoc in Integration Server
</SAP:Stack><SAP:Retry>N</SAP:Retry></SAP:Error>
all the experts help me out in solving this issue

Hi Deepika,
their might be some problems with ur ALE settings.
Here is a detail of the steps to be followed.
Do verify whether u have done the steps or repeat the steps as stated:
Steps for ALE settings:-
Steps for XI
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the R3 system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto IDX1.
     Create a new port.
     Give the port name.
     Give the client number for the R3 system.
     Select the created Rfc Destination.
Step 3)
     Goto IDX2
     Create a new Meta data.
     Give the Idoc type.
     Select the created port.
Steps for R3.
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the XI system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto WE21.
     Create a port under transactional RFC.(R3->XI)
     Designate the RFC destination created in prev step.
Step 3)
     Goto SALE.
     Basic settings->Logical Systems->Define logical system.
     Create two logical systems(one for XI and the other for R3)
     Basic settings->Logical Systems->Assign logical system.
     Assign the R3 logical system to respective client.
Step 4)
     Goto WE20.
     Partner type LS.
     Create two partner profile(one for XI the other for R3).
     Give the outbound or inbound message type based on the direction.
Step 5)
     Goto WE19
     Give the basic type and execute.
     fill in the required fields.
     Goto IDOC->edit control records.
     Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
     Click outbound processing.
Step 6)
     Go to SM58
     if there are any messages then there is some error in execution.
     Goto WE02.
     Check the status of the IDOC.
     Goto WE47.
     TO decode the status code.
Step 7)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
Xi
IDx5(Idoc check)
SU53(authorization check)

Outbound idoc missing

Hi All,
Outbound idocs not created for some documents only when we post from VL02, even the document not blocked in tRFC. Message type added in partner profile for outbound processing.
Please suggest me wht is the reason.....
Thanks in advance!!!!!!!

Hi,
Check if you are maintaining some filter criteria in the distribution model like specific company code or sales org.
Thanks
Krithika

PO outbound IDOC - Issue with Unit of measure

Hi,
I am facing issue with unit of measure.
1) In the PO outbound idoc in segment E1EDP01, the unit is always converted into ISO code and sent. Is there any way to avoid it.
2) Now while changing unit to ISO code, it checks if it is preset in T006 table. Now in some of the cases like Unit FT3, there are no entries in T006 table, hence IDOC is going into error. Let me know how can this be resolved. Do I need to update T006 table if yes then how can I do it.
Thanks.
Regards,
Shahu

Sorry.. Posting it in ABAP Development forum.

Posting multiple idocs of different IDOC/message type

Hi! ALL
It would be very helpful if you please provide your valuable suggestions...
I have 4 different file to IDOC mappings and i am trying to post all the 4 using the same interface determination....out of the 4 ....2 IDOC are of the same message type...this is throwing out an error...
<SAP:Code area="IF_DETERMINATION">CX_ID_PLSRV</SAP:Code>
<SAP:P1>Inbound interface was found more than once (for same sender and receiver) for outbound interface http://ck.com/xi_com/Ship.MI_SHIP</SAP:P1>
<SAP:P2 />
I am trying to use 3 File IDOC mappings in the same Interface determination, for example has the following inbound receivers in the interface determination:
DESADV
WMMBXY
DESADV.........I am using DESADV twice as the Message Mapping is different for each of the inbound DESADV idoc
Please, let me know...if you were able to post similar message type IDOC in the same inteface determination.
Your help is greatly appreciated....
Thank you,
Patrick
Thank you

Hi! Bill
I am using 3 message interface(in 1 interface determination) and i am able to post 3 idocs....the problem only arises when the 4th idoc is of the same message type as any of the first 3.
I am trying to exclude the 4th mapping.....b'cos the issue with similar message/idoc's type issue.....but incase u have a solution let me know...here is an example
Eg:
DESADV
WMMBXY
SHIP...is posting fine!!
But...problem with..posting...
DESADV
WMMBXY
SHIP
DESADV(4th same as first)
And again as mentioned...each have there own message mapping(MI) and interface mapping(IM)....and are in the same interface determination...as outbound interface and BS is the same for and in the inbound as u know is IDOC..R3.
Thank you for your response....
Patrick

RE: Posting OUTBOUND idocs

Similar Messages

Maybe you are looking for