Processing in Idoc

Hi
I have a Scenario.
Loop at idoc records.
Step 1: Thru User Exit Before Posting I Called a BAPI but did not Commit.
Step 2.Idoc is proccessed.
If Idoc _status = successfull
Will My BAPI will commit Automatically ?
Endloop.
Let me know wether my BAPI will commit automatically without BAPI_TRANSACTION_COMMIT ?
Bala.M
Moderator message: vague subject, wrong forum, please try yourself before asking others.
locked by: Thomas Zloch on Aug 6, 2010 2:15 PM

Hi Anshul,
We opted to go for IDOC Serialisation. With this, we achieved the sequential data processing through the PI interface.
I did check a blog in SDN which had step by step instruction to achieve this, but cannot find it now
Anyways, will give you a idea on wat needs to be done at PI and SAP R/3 end.
At PI end:
Using SE16 as the transaction, We need to create a entry in the table: IDXQUEUE
   a.PORT - (SAP R/3 system port)
   b.CLIENT - (SAP R/3 system client)
   c.MESTYP - (IDoc MSGTYP)
   d.QUEUEID - (Random Queuename, for eg: EOIO_PI_Interface)
At SAP R/3 end:
1. Create a function module. The QUEUEID created in SAP PI should be mentioned in this function module. <this basically indicates which PI queue will handle this message>
2. Using transaction we85, create a queue processing rule (which would call the function module)
3. In the partner profile, for the particular Idoc type, queue processing option must be enabled. And the queue processing rule (as defined in step 2 above) should be specified here.
Hope this information helps.
When I find the link to the blog, will post it here.
Thnx,
Prajeet

Similar Messages

Error while processing inbound Idoc (HRMDA_07) with FM IDOC_INPUT_HRMD

Hello,
I have a inbound Idoc of type HRMD_A (basistype HRMD_A07) which is processed by Function module (FM) IDOC_INPUT_HRMD with proofing. After processing an Idoc the status Monitor for ALE messages (BD87) tell me that my Idoc has status 53, which should be the result i would like to have.
Unfortunately when i go to transaction PA20 and check the infotypes, i see that infotype 0302 isn't created. When analyzing this problem i see that during the processing the Infotypes are posted with HR_MAINTAIN_MASTERDATA (dialog mode is 0 and luw_mode = 0 from include LRHA2F02 FORM save_pa_pb_infty) When this is done for infotype 0302 sy-subrc <> 0 the message is A complex application error has occured. This error message is placed in Export parameters
Return and Return1
of HR_MAINTAIN_MASTERDATA. When the program returns to the calling Form it checks if there is message of type E in HR_RETURN (see below) :
CALL FUNCTION 'HR_MAINTAIN_MASTERDATA'
          EXPORTING
            pernr                          = ins_objects-objid       "#EC DOM_EQUAL
            actio                           = 'INS'
            tclas                           = tclas
            dialog_mode               = dial_mode
            luw_mode                  = '0'
            no_existence_check = $cross
            no_enqueue              = $cross
          IMPORTING
            return1                       = return
            hr_return                    = hr_return
          TABLES
            proposed_values    = proposed_values.
        REFRESH proposed_values.
     IF hr_return-msgty = 'E'.                           "note 984409
      CLEAR protocol_error.
      protocol_error-msgty = hr_return-msgty.
      protocol_error-msgid = hr_return-msgid.
      protocol_error-msgno = hr_return-msgno.
      protocol_error-msgv1 = hr_return-msgv1.
      protocol_error-msgv2 = hr_return-msgv2.
      protocol_error-msgv3 = hr_return-msgv3.
      protocol_error-msgv4 = hr_return-msgv4.
      READ TABLE t_hrobjinfty WITH KEY objid = hr_return-pernr
                                       infty = hr_return-infty
                                       subty = hr_return-subty.
      protocol_error-segnum = t_hrobjinfty-segnum.
      protocol_error-routid = 'create_prf_pa_pb_object'
As mentioned above, the error message is only placed in the parameters Return and Return1 and not in HR_RETURN.please read the first reply

Hi,
I think you have preety much done from your end itself .
Could you please tell me what you got in this parameters:
     protocol_error-msgty = hr_return-msgty.
      protocol_error-msgid = hr_return-msgid.
      protocol_error-msgno = hr_return-msgno.
      protocol_error-msgv1 = hr_return-msgv1.
      protocol_error-msgv2 = hr_return-msgv2.
      protocol_error-msgv3 = hr_return-msgv3.
      protocol_error-msgv4 = hr_return-msgv4.
It may help us to track down the issue in more better way .
Thanks!

Desing requriment for processing the IDOC in real time

hi Gurus,
we have a requirement to design for processing the IDOC in real time i.e.all the IDOC must be store and process for give time line with out using BPPM tool.we have suggested to use cache storage or storing the files in file adapter.
please suggested good process with out compromising the Performance of PI.
regards
shankar

hi Raj,
Please find the example below for your reference
let say
System A-->PI--
>system B
system A sends multiple files based on time(daily or weekly) and real time( as an when the record created) to systerm B (CRM) in the form of IDOC Via. PI
we needs to club the real time files and send it to system B.How best we can do without using BPM.
regards
shankar

Problem in processing incoming IDOC

Hi All,
I have a problem while processing Incoming IDOC in the system.
While I try to process and FI IDOC (without purchase order) in the system, by giving the appropriate GL account and cost centre where the document should get posted to (in transaction WE19), I find that the system creates the IDOC successfully with status 53. However, it creates a parked document in the system for the vendor.
When I try to post the document through transaction FBV0, the system asks for a cost centre. Can you please clarify, why the system is asking for a cost object though it is given in WE19 transaction. Ideally while processing the IDOC the system should post the document directly as it has all the relevant details in the IDOC right?
(Just for info, I have given the GL account details in segment E1EDP19 with qualifier 002 and the cost centre in segment E1EDP30 with qualifier 045)
Expecting your help in this regard.
Regards
Nagarajan N

Hi
You can use WE19 to debug the Idoc FM.
Check this link if it is helpful:
Debugging Idocs
Regards
Neha

BADI for post processing of IDOC BOMORD

Hi experts ,
I want a BADI for post processing of IDOC BOMORD. Actually after IDOC processing BOM got updated in system and i want to schedule the explosion of BOM in process order after it. Please update me with the solution.
Thanks
Nitin kapoor

Roberto, thanks for your prompt reply (as always).
Actually, it seems that the deletion of the prior infopackage request is performed before executing the infopackage again (not after), I apologize. I will try your suggestion, though. If this is actually the correct FM, then I will award you full points!
I must admit, though, understanding the parameters of the FM are difficult. Can you aor anyone else provide more details?

Check in BAdi if delivery processed with IDOC or with transaction

Hello to everyone!
I have encountered an issue and hopefully you could help me in solving this.
I have developed an enhancement (BAdi) in delivery processing.
Every time delivery is being changed - method is triggered and line item is being validated against some conditions
But now I would like to prevend BAdi from being launched when delivery comes in IDOC.
For this purpose I just put a simple condition in BAdi method:
IF sy-batch NE 'X'.
//here perform validation.
ENDIF.
Unfortunately validation is still performed. Looks like when IDOC is being sent to ECC from PI, sy-batch is empty.
I would also like to prevent validation from being launched when IDOC re-processed manually (BD87 or sth.)
But then sy-batch is also empty.
Could you please advise some solution for this?
How to check in BAdi if delivery is being processed with IDOC or with transaction (VL32N, VL31N, VL32, ...)
I would appreciate every comment on this.
Kind Regards,
P.
Edited by: Piotr Wojciechowski on Jul 28, 2011 8:59 PM

Hi Max,
Thanks a lot for your reply!
Yes, indeed, IDOC is processed by FModule IDOC_INPUT_DELVRY.
You mean I should for example
find some place in this FModule (exit/enhancement point/...) where I could put-Z-code
and raise a delivery number (or just some flag) to memory (EXPORT TO MEMORY..)
and later on catch it from memory in my BAdi method (IMPORT FROM MEMORY ...)
to check if delivery processed by IDOC/not IDOC ?
Kind Regards,
Piotr.
PS. Maybe you also have some idea how to debug such communication triggered from PI to ECC?
I have posted this in separate [thread|PI-ECC connection (IDOC scenario), how to debug? (External BP);.

What is the internal processing for idocs

Dear friends this is subbu working as a abap consultant.
can any body explain the how idocs are transfered (inbound process and outbound process)

1.Here out bound means sender.Inbound mens --receiver.
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
There are two filtering in IDoc.
Segment Filtering:
Segment filtering can be achieved using T/Code BD56. Here you can suppress a whole segment irrespective of data inside it . You have to give Message Type / Sender Prrtner / Receiver Partner.
Data Filtering:
Data filtering can be done in dustribution model (BD64) where you can restrict whole IDOCS or partials IDOCS to be send based on data in fields inside IDOC depending on whether the segment in which you filter is at the highest level or at a lower level. For example in MATMAS if you put a filter of E1MARCM for a particular plant , only data for this plant will go and other plants will be ignored.
Please check this link for more information.
http://help.sap.com//saphelp_470/helpdata/EN/0b/2a611c507d11d18ee90000e8366fc2/frameset.htm
Reward points..

Converting Process order Idoc to Post a Purchase order

Hi,
we have a requirement where we will get a Process order IDOC that is LOIPRO as an inbound IDOC. We need to use the IDOC to create a purchase order.
Can anybody suggest what can be done.
Sender system sends LOIPRO.
Recieving system recieves it and need to post a purchase order rather than a process order.
Thanks,
Neha.

No Reply..so far..

How to process inbound idoc in R/3 with status 75 - idoc received via qRFC?

Hi gurus,
we are using EOIO for source to R/3, and all the idocs a received in r/3 with this status. But they can't be processed from BD87. How to process these?
Thanks,
Olian
Edited by: Olian Saludew on Sep 11, 2008 11:44 AM

Hi,
Idocs Works on tRFC Queues.
Check this Report to Process Inbound Idocs with Specified Status.
RBDAPP01
Regards
Seshagiri

Processing inbound Idoc ORDERS03 with status 51

Dear ALL
While processing inbound idoc with message type ORDERS03 i am getting a status 51 with below erros
I have maintained the data under VOE2 & VOE4 but not got the solution. We are on SAP ECC6 Version
Customer 1100 is customers purchase organization
Partner no 1109 is customers plant
VKORG, VTWEG, SPART cannot be determined for customer 0000001100 , vendor REN15D
Message no. VG204
Terms of payment in IDoc E1EDK18 have been transferred: Check data
Message no. VG202
Partner number 1109 for customer 0000001100 , partner function WE does not exist.
Message no. VG140
Regards
Arun

Hi,
Vendor 100002 is not maintained in your system. Maintain the same or use some other vendor which is there in your system.
You should be able to post the document.
Regards,
Lalit Kabra

Processing ABAP Idocs in SAP Java AS CE 7.1 web service client applicatin

I am trying to build a Java web service client which would call a web service in a non-SAP system. I am trying to send Idocs from the back-end CRM system to my Java web service client using a Jco RFC Provider. I have already created the RFC Destination on the ABAP side to send my Idocs to my Jco RFC Provider program on the Java side. The connections between the ABAP and Java are working fine. My question is how in my Java web service client do I pick up the IDoc sent from ABAP to the Jco RFC Provider?
Please let me know if more clearification is needed

I do receive the IDoc with the SAP Java AS "RFC Jco Provider" component I created, and in my Java application I created a class for "IDOC_INBOUND_ASYNCHRONOUSBean" which has a method "processFunction(Function function)" and in that method I can do function.write("filename.xml") and it writes out an xml document of the Idoc sent from the ABAP server. I can further process the Idoc by pulling field values from the xml structure. However, my problem is I am now trying to write a second Java application to do the same thing but with a different Idoc type. I created a a second RFC Jco provider(listener) on the server but the Idocs still flow through the first Java application, which is an undesirable affect. I got this idea from this document originally "http://nwadave.com/NwadExplorer/data/SAPDoc/ProcessingIDocsWithTheSAPJavaConnector.doc", and it works fine until now when I'm trying to add a second application to do similar work. This is makeing me wonder if I should have even done the first one this way? Bottomline is what tell the RFC Jco provider(listener) on the Java server which application to send the Idocs too?

CUA - SUIM in client system with background processing of IDOCS

Hi
We have setup CUA in our Solution Manager system 4.0 sr2 SP11 and activated background processing of idocs. When we run SUIM in the child system the user creation/change information is now showing the name of the background user rather than the actual name of the creator/modifier.
Has anyone else seen this before and is it standard functionality or a bug?
Thanks in advance
Justin

Hi Djamel
When you set up CUA you do the inital import of the roles with SCUG, ensure you have the company details correct in each system. Also in each system schedule the background job SUSR_ZBV_GET_RECEIVER_PROFILES, this will get the details of any new roles/profiles setup in the child systems.
Regards
Justin

Inbound Processing of Idocs with status other than success

Hi,
I am new to ALE/Idocs. Can anyone please let me know how can I process the Idocs which have the status other than 53.
Thanks & Regards,
Indira

Hi,
In addition to the previous posts few more programs to process failed inbound IDocs are as mentioned below.
- Use program RBDAGAIE to process edited IDocs (IDocs with status 69)
- Use program RBDAPP01 to process IDocs failing with serialization issue (IDocs with status 66)
- Use program RBDAGAI2 to process IDocs after ALE inbound error (IDocs with status 56, 61, 63, 65)
~ Bineah

Job cancelled while processing inbound IDOcs

Hi All,
we are sceduled job in background processing mode for the program RBDAPP01(Inbound Processing of Idocs),
but job was cancelled due to RAISE_EXCEPTION.
if i cheked in ST22 it is showing as
""The termination occurred in the ABAP program "SAPLMCS2" in "MC_SEND_MAIL".
The main program was "RBDAPP01 ".
The termination occurred in line 108 of the source code of the (Include) program "LMCS2U09""
i didn't understand why it is cancelled ?
can any one pls help me ....
regards,
suresh

Hello,
Sometimes if the Data / Right Data is not present in the IDoc, then it would not help the Standard SAP Program / Programs / Function Modules to fill-in Certain Field Symbols due to which the Short Dump might have occured.
Check the IDocs and try executing the Job again.
Thanks and Regards,
Venkat Phani Prasad Konduri

How to process an IDoc using qRFC of version 6.30.060

Hi all,
Can anyone please tell me how can we process an IDoc using qRFC port of version 6.30.060.
In this version 'Queue Processing' option in WE20 is missing and transaction WE85 is also not available.
thanks & regards
Piyali

HI Piyali,
Check out these links. THey will surely help...
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE2/BCFESDE2.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE5/BCFESDE5.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESRFC/BCFESRFC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE4/BCFESDE4.pdf
Re: SM59
If you find this answer useful, please reward me for the same.
Good luck
Karthik Potharaju

Process Inbound IDOC

Hi there,
I have an IDOC file store in the application server, I would like to know if exist a funcion module to read this Idoc and process it as inbound message in SAP.
Thanks in advance
Alexis

Hi,
You can use standard program RSEINB00 to process inbound IDoc file.
Regards,
Ferry Lianto

Processing in Idoc

Similar Messages

Maybe you are looking for