IDOCS Processing from XI to R3

How are inbound IDOCS to R3 processed from XI.
When the IDocs are transferred to R3 from XI, I can see that there are many messages(Transaction Ids) in SM58 in XI, and these are not executed sequentially.In SM58 the messages are randomly executed(For example,OUT OF 20 messages in SM58 for the same IDOC TYPE and Same Interface, the 1st message and 20th message status says 'TRANSACTION EXECUTING'). SO, When the IDOCS are created and posted in R3 , ARE THE IDOCS NOT POSTED IN SEQUENCE? and what happens if a message which is in the middle gets stuck in SM58,and we do a EXECUTE LUW at the last after all the messages in SM58 are processed.Does this disrupt the sequence.
Please tell the processing sequence.

Hi Michal,
Thanks. I understood how to achieve the queue sequence. when I do the Queue Processing,the EOIO service uses the Outbound Queues XBQOx,XBQAx and XBQZx as per the SAP documentation.
Assume, If I send 10 messages ,
1) Are the 3 queues used in random?
2)If only XBQOx queue is used, and if XBQO_0001 used for the 1st message ;Is XBQO_0002 queue used for the 2nd or 3rd message.
If this is the case then how is Sequence guaranteed again,as they all are processed at the same time.
Regards

Similar Messages

IDOC processing from Workflow.

Hi GURUs,
My scenario is as follows:
SAP is receiving an IDOC from XI. I'll have to receive IDOC in SAP using option - with ALE service and processing by task, as i'll have to send various emails using workflow task.
But how to process the received IDOC from workflow to affect sales order change?
I am thinking of using the function module - IDOC_INPUT_ORDCHG to make the sales order change. But the problem is how to process IDOC and calling the function module to do the needful from workflow along with sending emails.
Thanks in advance,
Deep.
Message was edited by: Deep Chakrabarti

HI,
You can very well stay with the standard process code and your process code should point to a workflow. There are no standard workflow template available for ur scenario. Hence you`ll have to use a custom workflow template and you can very well use BUS2032 and ORDCHG for your application.
Now, in your workflow the flow of steps should be in the sequence by which you want the activities to flow. Every step should essentially bind a method of a bus. obj. If in your scenario, the changes in the sales order are to be carried out automatically use the BAPI else send mail to the corresponding agent and let him change the S.O. in VA02.
Reward points and be generous!!!!!!
Just kidding...
Regards

Excluding idoc processing from user exit code

Hi all,
In a user exit (for VA01 Create Sales Order) we are currently excluding certain order types by hardcoding the document type in the code. This is because some orders are created by IDoc and in this case the IDocs fail if they use the eser exit code (because the code creates pop-up messages intended for online users only). Not the best solution.
Does anybody know if we can use different code so that this part of the user exit does not get triggered by IDocs?
Thanks,
Mike

I've figured out another solution - you can do a test on the field IDOC_NUMBER. If it is filled, then the sales order is created/changed via an Idoc.

Data transfer between SAP & Java and Vice versa using IDOC Process

Dear Experts,
        We are working on one of the good requirement related to data transfer between SAP and Java software. Client requirement is, they want to transfer the data in both the ways (from SAP --> Java and Vice versa also).
In detail is, after sales order creation using one custom program loading plan details will be calculated. Once loading dates are confirmed then, user will release the sales document to transfer the data from SAP to Java using "Outbound IDOC processing". Similarly in that JAVA software some shipment details will be performed, once completed from JAVA software again details needs to be pumped back to SAP as "Inbound IDOC Processing".
For this fields are already identified from external software SAP and we are looking for the same to perform the steps in SAP.
At this stage, I need your expert opinion / feedback how to go about at this stage.
Meaning,
                 1. What are the customizing steps needs to be done in SAP..?
                 2. How to trigger the :Outbound IDOC process" once the documents are "Released" from custom transaction
                 3. How to create the link between SAP and JAVA to transfer the data between these 2 software
                 4. How to trigger the "Inbound IDOC Process" from JAVA software to SAP and how to store the data in SAP
Experts, please give your feedback in terms of reply or by sending the step by step process to fulfill this client requirement.
Thanks for your cooperation.
Regards,
Ramesh

Maybe too many open questions in the same document.
Maybe you should repost a more specific question in a technical forum.
This looks like a small project where you already know what you want, maybe you should contract a technical specialist so he proceeds to the implementation!

Mass processing for inbound orders idoc's from file

Hi Experts,
I have an requirement wherein we need to process all the ORDERS idocs sent from a thrid party system to a particular folder in the SAP system. Now we use a custom programme which in turn calls fn module IDOC_INBOUND_FROM_FILE to process each file. Here if the fn. module IDOC_INBOUND_FROM_FILE hits an erroneous file (control record error) it issues abend message which causes to entire programme to exit leaving rest of the files in the folder unprocessed.
Let me know if there is any other function module or way to tackle this issue so as to process all the files.
Thanks & Regards,
Jimmy.

Add the exception ERROR_MESSAGE = 99 (or some other unique number) to the standard exceptions in the function module call in your custom program. This will allow you to trap the error and continue processing.

IdocReceiver not processing all the idocs produced from PFAL in OrgModeler

Dear experts,
We are on below Nakisa version.
Name Nakisa OrgModeler
Version 4.0 SP1
Build 0910021700
I ran the initial load for the OrgModeler and it produced around 500 idocs. When I followed the command line interface, it processed around 56 idocs. The idoc status becomes 03 (Data Processed to Port OK) at the R/3 end for all the idocs. However idocreceiver is skipping many idocs in between and processing only few. I checked the database for HRP1000 and HRP1001 and the records loaded are not even 20% of the records in R/3 for the objects and relationships(HRP1000 obj types C, O, Q,S and HRP1001 002/003/007/008/011/012 etc) we filter at the distribution model.
I think the issue might not be an authorzation problem as its fetching the records from SAP R/3 and loading few records in the database.
I checked with my Basis consultant about another reciever running and grabing the missing records. He confirmed that only one idocreceiver running at nakisa end. I even happened to check the SAP gateway server(SMGW) and with TP Name NAKIDOC and symbollic destination NAK_RFC_DEST I can see only one record which is appearing on and off. When the record appear on the gatway server, the corresponding idoc being processed at command line interface. Till the other record appears on the sap gateway server, the idocs are missing at the command line interface.
Below is the screen shot from idocreceiver. (After the idoc 1695358 it processed 1695366 then 1695372 etc)
Any suggestions would be a great help.

Dear All,
My Basis guy finally realised that he started a Jco provider at the netweaver end and causing the issue. He stopped it and all the idocs processed successfully.
I learned the below points and might useful for few folks.
1.No idoc being processed and all the idocs failing with 'Bean IDOC_INBOUND_ASYNCHRONOUS not found on host'. It should be an authorization error and assigning the Authorization Object: S_IDOCDEFT (EDI_TCD = "WE30"; ACTVT = "03") will resolve the issue.
2. Few idocs are being processed at idoc receiver end.
i. Check for multiple idoc receivers which might be active and running.
ii. Check the number of connections and timeout parameters and set them to the maximum.
Thanks,
Manohar

Messages from IDoc processing can be found in application log

We are using the IDOC_INPUT_INVOIC_MRM Function Module to post Inbound Vendor EDI Invoices. During testing, we sometimes see the error "Messages from IDoc processing can be found in application log". We then have to check transaction SLG1 to ascertain the 'real' issue, e.g. "No GR documents found". In a Production environment however, this will be very inconvenient. Our business users process their own iDoc errors according to the iDoc Status, so to have to call up another transaction, and select the correct Application Log to find the true error, is not a process I would feel comfortable with for our users.
My question is, can we configure/determine which messages are passed to the iDoc Status, or redirect Application Log messages ? Might a Z version of FM IDOC_INPUT_INVOIC_MRM be the way forward ?
Many thanks,
Paul.

Hi,
Just monitor your error idocs in WE20 transaction. Give idoc number here then execute, you can see the all three records(control, data, status). Click on status record node then double click
on status number(e.g 51), it will take you to another screen there you click on "application log" button on application toolbar. This is the standard way finding the application log of an idoc, even i am finding the application log on production server like this.
Thanks,
Asit Purbey.

Creation of rfilr ports in WE21 from LSMW IDOC Processing

Hi,
I am trying to defile a file port for INBOUND IDOC processing status in LSMW.
Now when I go to create a file port in WE21, I give some dummy Physical directory name. But what should I give in
Function module field and Outbound file field ? Is it compulsary to put something in these fields...
Please help.....

Hi,
Function module field is used to define the path functionality of file generated.
EDI_PATH_CREATE_CLIENT_DOCNUM is the recommned fucntion by SAP .
Function is used to prevent unprocessed files being overwritten.Tihs function generates file directory path dynamically.
Hope this helps.
Thanks.
Mark points if helpful.

Processing Inbound IDOC's from FTP.

Hi,
I have an issue where IDOC's (WPUBON01 & DEBMAS01) are being saved in ftp folder and once these IDOC's are saved, we have to process it in SAP System, i would like to know the simple way of having these IDOC's processed in Unix based SAP system as the IDOC's will be coming in at Real time evey minutes or Seconds.
is there a way to do it with out ABAP process i mean just by using the Unix Scripts or by triggering the SAP background job.
Thanks in Advance.

Hi,
for testing purposes you can trigger inbound IDoc processing in transaction WE16. Otherwise you can schedule program RSEINB00 to periodically import IDoc into system. You can make a copy of that program and made changes if you need to add some extra logic.
Cheers

Outbound delivery creation with inbound IDOC transfer from Java system

Dear Experts,
       The scenario we are having is really very interesting. Hopefully its a good learning for me and also for others also.
The scenario is,
               After sales order creation the details will be sent to one Non SAP system (Java) for performing some tasks related to forwarding agent decision, shipping date and etc. Once the details are finalized in that Java system then, the details needs to be transferred to SAP as "Inbound IDOC" process. For this proposed to use the SAP Jco middle ware.
             Once the details transfered from Java system to SAP then, the outbound IDOC needs to get generated automatically. Assuming the stock for that sales order line item is available. Also one more complexity is, our client is using custom transaction (ZVl10C) for delivery creation.
Now Query is,
               1. Which IDOC, message type and Functional module needs to be used for creating the delivery automatically..??
               2. As per assumption, stock of that sales order line item should be available. Due to some business reason the stock was removed during inbound IDOC transfer then, what will happen to the IDOC..?. How to avoid this situation..??
               3. As we told we are re going to use SAP Jco b/w SAP & Java system. In this case, how the data will get transfered from Java system to SAP..?
Thanks in advance for the replies I am going to get
Regards,
VEL

Didn't get any feedback from experts for long time. So we are closing the question

Stop Inbound IDOC's from being created

I want to stop inbound IDOC's for a particular partner (type LS) from being created in our R/3 system. Is there a way to do this? I am aware these can be stopped in the middleware, but this is not possible in our case. I am also aware that I can stop these IDOC's from being processed via the partner profile, however, there will be a huge number of useless IDOC's that will be created in our system and I want to avoid that.
Hence, I do not want the inbound IDOC's to be created in the first place even though they are transmitted to SAP. Is this possible?
Any inputs will be highly appreciated.
Thanks,
Raghu.

Hi Satwik,
Choose Idoc in WE02.
Get port name, Then in WE21 get RFC name.
Go to transaction SMQS - Here we can block this RFC instead of blocking the queue.
Thanks,
Anil

Get IDoc-number from flat IDoc using dynamic configuration

Dear experts
In an IDoc2File scenario I have added the IDoc-number to dynamic configuration using the folling code in an UDF:
DynamicConfiguration conf = (DynamicConfiguration)
container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey FileName = DynamicConfigurationKey.create("http:/"+"/sap.com/xi/XI/System/File","DOCNUM");
conf.put(FileName, a);
The information is stored in the SOAP message
<SAP:DynamicConfiguration SOAP:mustUnderstand="1">
<SAP:Record namespace="http://sap.com/xi/XI/System/File" name="DOCNUM">0000000000012345</SAP:Record>
</SAP:DynamicConfiguration>
Can anybody tell me how I can access this information in the "variable substitution" section of the CC? Perhaps something like "message:docnum"?
Additional information:
Taking the IDoc-number from the payload using e.g. "payload:ORDERS05,1,IDOC,1,EDI_DC40,1,DOCNUM,1" does not work, since the XML-IDoc has been converted to an flat-IDoc.
Thanks in advance for any good ideas
Markus

Dear Rodrigo and Sarvesh
Thanks for your help so far! I applied your hints and now it is working fine.
But now I have the following additional questions
1.) My message mapping only maps the input IDoc to an output IDoc of the same type and structure. The MM is only required to process the UDF. Is there another, better solution to achieve my requirement that the IDoc-number shall be part of the filename?
2.) In the CC you have the possibility to use temporary files (section "Processing", Option "Put File" = "Use Temporary File". I think this will not work with the given solution, will it?
To possibly help somebody else or clarify the mechanism once again, I wrote down how my solution now looks like.
My UDF in the message-mapping looks like this
- Input = DOCNUM of IDoc, e.g. ORDERS05/IDOC/EDIDC/DOCNUM
- Outpt = DOCNUM of IDoc, e.g. ORDERS05/IDOC/EDIDC/DOCNUM
- UDF:
public String putDynamicConfiguration(String docnum, Container container) throws StreamTransformationException{
try
     DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
     DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");
     String filename = "Prefix_" + docnum + ".txt";
     conf.put(key, filename);
     return docnum;
catch (Exception e)
     return docnum;
In the CC the settings are now as follows
File Name Scheme = . -> only a dot or something else, because this field is obligatory, even if it is not used in this case.
Variable substitution (...)
    Enable -> unchecked
Adapter-Specific Message Attributes
    Use Adapter-Specific Message Attributes -> checked
    Fail If Adapter-Specific Message Attributes Missing -> checked
    File Name -> checked
    Directory, File Type, Temporary Name Scheme for Target File Name -> unchecked
When I send an IDoc to PI and view the Adapte-Engine Version of the message (the SOAP-document, not the payload) I can find the Filename:
<SAP:DynamicConfiguration SOAP:mustUnderstand="1">
<SAP:Record namespace="http://sap.com/xi/XI/System/File" name="FileName">Prefix_0000000000012345.txt</SAP:Record>
</SAP:DynamicConfiguration>

Idoc Scenario from SAP to SAP via PI 7.1o

Q: Two idocs will process from SAP to SAP via SAP-PI 7.1o and generated together.
Requirement :
Sync
2 IDOCs – as we explained our design will require two IDOCs. The first IDOC will be developed by a Z code and the second IDOC is generated by 100% Standard SAP BAPIs and 2 IDOCs send them to PI. Both IDOCs will be generated together by process code in sap and must be moved to PI and later to the receiver client together(SAP). The process can only be 100% completed when both IDOCs will be processed with success in the receiver side. Any one of the IDOC among 2 idoc's failed all the process should stop.
i think that is not possible , PI will not be able to stop successfull IDOC If another IDOC get fails .
Please give me approaches if any chance .
Thanks, Sanakr

Hi Bhavani,
You can use BPM with correlation to achieve this scenario:
Demonstration of ccBPM Scenario: SAP PI 7.1
**************** - BPM Scenario using Fork and correlation
Regards,
Suman

Problem in IDOC processing

Hi,
I have a File to IDOC scenario from third party to ISU.
PI interface is configured to pick up XML files.
Problem is occuring to process single files above 4-5 mb and process multiple files .
Though its showing processed properly in SXMB_MONI but the IDOC is not created in the ISU side.
In the outbound status field of SXMB_MONI we can see red flag with message "Message has error in outbound side".
Please help how to solve this. There is no issue in idoc configuration as it was running properly till date.
Thanks,

Hi Apu,
If the message has error on outbound side, can you please check the RFC once? Also can you please provide more details viz the design in PI
Regards,
Sriram

Inbound Idoc processing issues - Partner Profiles - error status 56

Hello All,
I'm having a little difficulty posting an idoc coming from MDM. It's a CREMDM04 xml coming from an MDM system. It is getting mapped through PI and is being split into ADRMAS02 and CREMAS04 Idocs. The message is being passed through XI and being posted to the ECC system, but certain fields in the EDI_DC40 header table are not being populated correctly (i believe). I'm using nothing but standard mapping/material from the SAP Business Content for XI. After looking through the standard XSLTs i cannot find the field-to-field mapping where the fields below are being populated.
The RCVPOR value (SAP[SID]) is correct when i view it in SOAP Header, but does not appear in the remote system under the receiver port for the inbound idoc.
The RCVPRN value ([String Value]) is incorrect in the SOAP Header and does appear in the remote system under the receiver partner number for the inbound idoc. How is the RCVPRN value being populated?
SOAP Header in IDocOutbound tag
<SAP:RCVPOR>SAP[SID]</SAP:RCVPOR>
<SAP:RCVPRN>[String Value]</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
I've been trying to trace down the string value for the RCVPRN, but i cannot find it anywhere. Perhaps i'm just overlooking it?
When i set the proper values (port = SAP<SIDofECC> and partner number = <LSnameof ECC>) using WE19 in the remote system then the partner profile is found and i'm left with different error to please specify an address group.
Any help is very much appreciated! :-D

Hi Jason ,
Just check out if you have done the following steps most of us make minor mistake here ....... I think this would solve your problem
To Configure the IDOC SCENARIOS ,PROCEED AS FOLLOWS
STEP 1:ALE SETTINGS TO POST IDOC INTO SAP R/3
We need to do the following settings in XI
1) Create an RFC Destination to the Receiving System in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a) Select Create New button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client
d) Enter the RFC Destination created in XI towards R/3
e) Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) Create an RFC Destination to XI in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Inbound Parameters (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Inbound Parameters.So click on ADD TO Create Inbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Message Type and Process Code.
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
do let me know if it helped
Edited by: Tom Jose on Feb 21, 2008 9:04 AM

IDOCS Processing from XI to R3

Similar Messages

Maybe you are looking for