How to work on RFC, IDOCs in IDES?

In my laptop, I have IDES 4.7 installed. But, it needs atleast two servers to b configured so that I can work on RFCs and IDOCs to test them in the two servers.
Is it possible in my system?

Hi
but i have only one client in my laptop. ie. 800.
how to configure different client?
Also, can I do RFC and IDOC with diff. clients instead of servers?

Similar Messages

Hi gurus what is RFC , how to work on RFC explain to me plz,

hi gurus what is RFC , how to work on RFC explain to me plz,FROM WHERE TO WHERE TO WHERE SEND THE DATA USING RFC , AND HOW TO SEND .

RFC
rfc
Re: what is Remote Function Call (RFC)?
RFC
/message/4752331#4752331 [original link is broken]
What are idocs, BAPI, RFC?
Reward points..

How to work on inbound idoc

how to work on inbound idoc

Azeez,
Check this...
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 -- Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 --Getting Material Data
Tcode WE05 -- Idoc List for inbound status codes
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
Regards.

I have an old AOL account not used for years. No I have realized some years ago I have signed in into the apple storewith this email. Now I am not able to change this apple ID. Has s.o. an idea how to work this out?

I have an old AOL account not used for years. No I have realized some years ago I have signed in into the apple storewith this email. Now I am not able to change this apple ID. Has s.o. an idea how to work this out?

See this -> http://support.apple.com/kb/TS1299

I have no idea how to work iMovie 10.0.3

I have an iPad and I've been using it for imovie for a while now and now I have a laptop. I do not own my iPad because it is a school iPad and so I won't be able to use imovie anymore over summer. I have some plans for imovie, but I have no idea how to work it on my Macbook pro, it's all very confusing and they don't have any tutorials for 10.0.3

Hey there LiziG,
It sounds like you need a bit of help getting familiar with the new iMovie 2013. I have a couple of links that you may find useful. First, here is the iMovie for Mac Help:
http://help.apple.com/imovie/mac/10.0/#
And here is the general iMovie support page with articles about camera compatibiltity, Importing content to the new iMovie, various walk throughs on how to do certain functions, and even troubleshooting in case you need it:
Mac Apps Support
https://www.apple.com/support/mac-apps/imovie/
Thank you for using Apple Support Communities, and I hope you enjoy iMovie once you get the hang of it.
All the very best,
Sterling

How can i set the IDOC Status to 03 without doing a "COMMIT WORK"

Hello Geeks,
I want to set the status of the Outgoing IDOC to 03 , without doing a "COMMIT WORK" . Actually only after i do a commit work are my IDOCs dispatched. But with a commit work the IDOCs are dispatched immidiately. I do not want to dispatch it immidiately. Instead i want to hol the IDOCs till my LUW finishes , but the IDOC status should be set to "03" instead of "30".
Thanks,
Bashir

Hi,
After collecting all the idocs which are under status 30, run the program RSEOUT00 to change the status from 30 to 03.
If you want to do this process automatically then set the program RSEOUT00 in background.
Regards,
Lokeswari.

How to call two RFC in a single JAVA method.

Dear all,
I just want to know that how to call two RFC in a single java method which is defined in CRM implementation file. I'm using NWDS as the customization IDE & working on ISA 7.0.

Hi Sunil,
In the Backend Implementation class, in any method you can call multiple RFCs.
It will be the same way as you do for the single RFC call.
Following syntax is for your reference.
Get the JCO connection
JCoConnection connection = getDefaultJCoConnection();
JCO.Function func = connection.getJCoFunction("ZXXXXXXX");
set the import parameters
Execute it.
connection.execute(func);
get the data from export / table parameters
Now call the second RFC
func = connection.getJCoFunction("ZYYYYYYYYYY");
set the import parameters
Execute it.
get the data from export / table parameters
close the connection
Hope this will help you.
-Chandra.
Edited by: Chandra Sekhar Seeli on Jan 13, 2011 2:04 PM

How to use the RFC SDK as part of a QTP test script

Hi there,
after having recorded some business transactions, I want to insert some checks into the QTP test script: an easy example would be an existence check in a database table. Instead of recording a SE16 or SE16N, I would find the approach much more elegant and much more efficient to use a (VB-)programmed RFC call for this purpose.
Unfortunately, I didn't find a way to address an RFC using the actual connection that QTP is working on. Creating a new connection would probably be possible but is not what I want.
Any idea how I could proceed? Does anybody else have experiences in this area?
I think this issue is not restricted to QTP but shared by any tool working on top of the SAP GUI Scripting API.
Thanks and regards
- Rüdiger
Edited by: Rüdiger Plantiko on Nov 21, 2008 4:24 PM

bigbrain28 wrote:
> Thank You, cfsearching! I don't quite understand 100%
how it works
As all three of us indicated you use array notation for this
type of
requirement. In ColdFusion you can use array notation or dot
notation
to access structure data. Almost all data in ColdFusion is
now some
type of structure.
I.E. #Form['myField']# is the same as #Form.myField#.
The advantage is that with array notation you can do things
you can not
do with dot notation. You can reference elements that have
keys that
are illegal variable names such as one with a space.
I.E. #url['my field'] is allowed, #url.my field# would fail
or course.
And you can concatenate the key string as we did with your
example.
I.E. #Form['aString' & aVariable]#
There are many powerful things one can do with this
knowledge. One can
access record sets with array notations. This can allow for
very
sophisticated parsing of a record set.
I.E. #myQuery['column'][row]#
You can dynamical call a variable. Thus creating dynamic code
that does
not even need to know what variables exist until run time.
I.E. #variables[anyName]#
This just scratches the surface.

System copy : how to backup your rfc connections, partner profiles ...

system copy : how to backup your rfc connections, partner profiles (we20) amd ports in IDOC processing (we21) ???
Hi forum,
if you want to copy your production system to your quality assurance system you can export users and later on reimport
it to save work. That's good.
But how about RFC connections, partner profiles and ports in IDOC processing ? Anyway to export and reimport it later on ?
Thank you for your help.
Kind regards
O.Eggert

Hi forum,
in the meantime I found out how to handle this matter. May be this solution is not very elegant, but it works.
As for RFC-Connections there are several tables beginning with rfc. e.g., rfccheck. But 4 of it only differ from one system
to the next. These are rfcdes, rfcdoc, rfcattrib and rfccheck. What I did is the following : I used
brspace -u sapsr3/<password> -f tbexport -t "RFC3"
and quite simply exported these tables. Then I deleted some of the RFC-Connections, both ABAP and TCP/IP. After reimporting
what I exported before all these destinations were availlable again. As for ABAP the password had to be reentered but this
can be avoided, too. Have a look at transaction /nsecstore. The tables behind it are RSECTAB and RSECACTB, rspectively.
Export it after having exported the rfc* tables and reimport it after having reimported the rfc* tables. Very important : enable
the option "consistent export" !!!
It worked this way although there might be better and more elegant solutions.
As for transaction we20 check sap not 182172.
Hope that I could be of profit to this forum.
Kind regards
Olaf Eggert
p.s.
import command : brspace -u sapsr3/<password> -f tbimport.
Them select what you exported before.

Reg: RFC / IDOC required for doing CIDX Scenario

Hi! Gurus,
This is Amar Srinivas Eli. I have task here to work and implement CIDX Scenario succesfully. There are some business cases as per the CIDX standards from that I was selected one Business case i,,e, FORECASTING.
But inorder to implement that scenario I need some RFC's or IDOC lists from SAP side whether it may be a source or target side..what ever it may be...and other side will be CIDX format.
Here I need your help in the below mentioned tasks. Kindly help me out in a detailed step by step guide and do the needful to me.
1. How to get RFC / IDOC name from R3 System and I know that I can get RFC from SE37 and IDOCs
from WE05 but I need whether all the required fileds are statisfying in the RFC's or not.
2. My first preference is only for STANDARD SAP RFCs or IDOCs.
3. Please let me know how to see the inner fields present in those RFC's
4. ALso please provide any configuration guide which contains screen shots if you already worked
earlier on CIDX Scenario I mean step by step and also for testing
5... tell me if there is any other tool other than STK kit for testing CIDX messages.
6. Is there any Freeware STK tool kit is there or not...
Also share your experience and errors that you have faces while doing this CIDX Scenario.
Regards:
Amar Srinivas Eli

Hi! All,
Thanks for your fast response..
Hi! Raja,
I gone through your points. Here I have few doubts on those please clarify that.
1. Coming to testing i didt used any testing tool , but you can comre your output using XML Spy or Stylus studio.*
*CIDx Documents,you wil find in SDN please search in SDN.
Means Without using STK Tool or else some other tool How can I get the CIDX response for my request in the Testing environment. See I am not doing this in real time I am trying to findout the solution for Business cases so I need one testing environment tool right ? Is that ALTOVA XML spy will give no right ?
Note: You told that you have done that business case IDOC--CIDX Order change / req Will you please share the information documentation I mean step by step procedure for end to end doc...based on your scenario ?
2. I know those R3 and PI settings I mean configurations means ports and RFC destinations and all those..but only thing I dono is "How you got that IDOC I mean on what basis and how did u search the IDOC?"
3. See Here I am working on topic FORECASTING it includes so many sub tasks like Deman PLan req and response, supply plan req and response and replenishment order and etc....so based on that how can I get those related RFC's or IDOC's in order to communicate from R3 Side
If Suppose I have seen one RFC/IDOC and for example out of 10 fields few are there in one IDOC and another few are there in another IDOC then in that case I need to go for Multimapping IDOCs I mean 2 Senders to one Receiver if yes Is it possible?
My first requirement is based on the above mentioned business cases how can I get the corresponding RFC's or IDOCs ?
Regards:
Amar Srinivas Eli
Edited by: Amar Srinivas Eli on Jan 5, 2009 12:19 PM

Error importing RFC / idoc despite following note 769356

We have been experiencing a number of problems where we cannot import RFC / idocs in the integration repository. The BASIS team have followed note 769356 and originally this solved the problem but meant that we reverted back to old screens in the Integration Builder and some German texts in the Integration Repository.
Current patch version is Support Stack 4
To get to this point the following steps were followed:
Undeployed com.sap.xi.repository
Deployed the install version of com.sap.xi.repository.
In order to correct the problems with the incorrect screens etc.. The following steps were carried out:
Undeployed com.sap.xi.repository
Deployed the Support Stack 4 version of XITOOLS (includes com.sap.xi.repository)
Applied Support Stack 5 for the Abap kernel
Applied SAPXIAFC04P_1-20000272 and SAPXITOOL04P_1-20000274 via SDM
This fixed all of the problems with German texts etc.. but now we cannot import RFC / idocs again. In the Java Web Start Log (attached) we still get the error message
mentioned in note 769356. We have deleted the Web Start Cache on the client hosts (several restarts of the machine and deletions of the cache). The BASIS guys are going to undeploy and redeploy the repository again but failing that we are running out of ideas.
Does anyone have any suggestions?
Here is the entry in the log file:
java.lang.AbstractMethodError: com.sap.aii.ibrep.sbeans.upload.UploadServiceRemote_Stub.openSAPSource(Lcom/sap/aii/utilxi/misc/r3Connect/SAPConnectionData;Lcom/sap/aii/utilxi/misc/r3Connect/SAPLoginData;Lcom/sap/aii/ib/bom/gen/VersionContext;)Lcom/sap/aii/ibrep/sbeans/upload/SourceID;at com.sap.aii.ibrep.clsif.upload.RemoteUploadClient$ConnectionImpl.connectBean(RemoteUploadClient.java:107)at com.sap.aii.ibrep.clsif.upload.RemoteUploadClient$ConnectionImpl.<init>(RemoteUploadClient.java:91)at com.sap.aii.ibrep.clsif.upload.RemoteUploadClient.getSAPUploadConnection(RemoteUploadClient.java:66)at com.sap.aii.ibrep.gui.tools.r3import.wizard.SAPLogonPage.connect(SAPLogonPage.java:94)at com.sap.aii.ibrep.gui.tools.r3import.wizard.R3ImportWizard$LoginTask.run(R3ImportWizard.java:456)at com.sap.aii.utilxi.misc.thread.ThreadPool$ThreadPoolThread.run(ThreadPool.java:321)

Dan,
you are almost there!
If you religiously follow note 769356, you should not have this problem.
Just do the following as the note suggests:
- From SDM, undeploy only the com.sap.xi.repository
- Unzip SAPXITOOL04P_1-20000274.SCA.zip
- The file ExchangeRepository.sda will be one of the extracted files
- Only import the ExchangeRepository.sda. Do not import the entire ZIP package.
- Restart the J2EE engine.
- Delete Webstart Cache
- From the XI admin page:
http://XIhost:50000/rep/support/admin/status.html
Re-Initialize the Jars for resigning.
- Wait for 5 minutes for the jar signing to finish. Sometimes, the jar signing gets interrupted, you have to let it finish.
The above steps worked for me.
thanks,
Manish

How many types of rfcs are there

Hello,
Can any body explain about how many type of rfcs are there. give the difference also.
Thanks.

Hi,
Check this info.
These are the types of RFC
Asynchronous RFC (aRFC)
Synchronous RFC (sRFC)
Transactional RFC (tRFC)
Queued RFC (qRFC)
Parallel RFC (pRFC)
Asynchronous RFC :
This is used when you need to increase the performance of ABAP program by having system call more than one function module in parallel than forcing the program to wait for results .
Transactional RFC
This let you group one or more function module call together o tRFC LUW and ensure that fucnction module within LUW is called once . In contrast to aRFC and sRFC the tRFC belonging to tRFC LUW are executed in order .
tRFC is always used if a function is executed as a Logical Unit of Work (LUW). Within a LUW, all calls are
1.Executed in the order in which they are called
2.Executed in the same program context in the target system
3.Run as a single transaction: they are either committed or rolled back as a unit.
Implementation of tRFC is recommended if you want to guarantee that the transactional order of the calls is preserved
Asynchronous remote function calls (aRFCs) are similar to transactional RFCs, in that the user does not have to wait for their completion before continuing the calling dialog. There are three characteristics, however, that distinguish asynchronous RFCs from transactional RFCs:
When the caller starts an asynchronous RFC, the called server must be available to accept the request.
The parameters of asynchronous RFCs are not logged to the database, but sent directly to the server.
Asynchronous RFCs allow the user to carry on an interactive dialog with the remote system.
The calling program can receive results from the asynchronous RFC.
You can use asynchronous remote function calls whenever you need to establish communication with a remote system, but do not want to wait for the functions result before continuing processing. Asynchronous RFCs can also be sent to the same system. In this case, the system opens a new session (or window). You can then switch back and for between the calling dialog and the called session
RECEIVE RESULTS FROM FUNCTION Remotefunction is used within a FORM routine to receive the results of an asynchronous remote function call. The following receiving parameters are available:
IMPORTING
TABLES
EXCEPTIONS
The addition KEEPING TASK prevents an asynchronous connection from being closed after receiving the results of the processing. The relevant remote context (roll area) is kept for re-use until the caller terminates the connection.
Transactional RFC (tRFC) and Queued RFC (qRFC).
tRFC is used mainly to transfer ALE Intermediate Documents (IDocs).
Transactional RFC:
If an error occurs during a synchronous remote function call, the system cannot tell at what point the error occurred (most crucially, whether the function module was actually processed in R/3 before the operation failed). Restarting a failed call is therefore a dangerous thing to do, since you risk duplicating a completed function call.
To alleviate this problem, you can use transactional RFC, which guarantees that each function call you issue will only be executed once, even if you submit it repeatedly to the R/3 System. The system implements this safeguard by assigning a unique transaction ID (TID) to each transaction that you submit. When you attempt to process the transaction, the system checks whether that TID has already been processed. If it has, the transaction is ignored.
Disadvantages of tRFC
- tRFC processes all LUWs independent of one another. Due to the amount of activated tRFC processes, this procedure can reduce performance significantly in both the send and the target systems.
- In addition, the sequence of LUWs defined in the application cannot be kept. Therefore, there is no guarantee that the transactions are executed in the sequence dictated by the application. The only guarantee is that all LUWs are transferred sooner or later.
Queued RFC:
When you use transactional RFC, you cannot guarantee the order in which the function calls will be processed in the system (it is quite possible that one call might overtake another). For cases where you need to specify a particular processing order, you can use queued RFC, which is an extension of transactional RFC. In qRFC, you place each function call in a logical queue. A function call cannot be executed until all of its predecessors in the queue have been processed. Queued RFC calls are processed asynchronously
Therefore, Queued RFC is better than Transactional RFC.
Remote Function Call:
RFC is an SAP interface protocol. Based on CPI-C, it considerably simplifies the programming of communication processes between systems.
RFCs enable you to call and execute predefined functions in a remote system - or even in the same system.
RFCs manage the communication process, parameter transfer and error handling.
http://help.sap.com/saphelp_47x200/helpdata/en/22/042860488911d189490000e829fbbd/frameset.htm.
Remote Function Call (RFC) is the standard SAP interface for communication between SAP systems. The RFC calls a function to be executed in a remote system.
Synchronous RFC:
The first version of RFC is synchronous RFC (sRFC). This type of RFC executes the function call based on synchronous communication, which means that the systems involved must both be available at the time the call is made.
Transactional RFC (tRFC) and Queued RFC (qRFC). tRFC is used mainly to transfer ALE Intermediate Documents (IDocs).
Transactional RFC:
If an error occurs during a synchronous remote function call, the system cannot tell at what point the error occurred (most crucially, whether the function module was actually processed in R/3 before the operation failed). Restarting a failed call is therefore a dangerous thing to do, since you risk duplicating a completed function call.
To alleviate this problem, you can use transactional RFC, which guarantees that each function call you issue will only be executed once, even if you submit it repeatedly to the R/3 System. The system implements this safeguard by assigning a unique transaction ID (TID) to each transaction that you submit. When you attempt to process the transaction, the system checks whether that TID has already been processed. If it has, the transaction is ignored.
Queued RFC:
When you use transactional RFC, you cannot guarantee the order in which the function calls will be processed in the system (it is quite possible that one call might overtake another). For cases where you need to specify a particular processing order, you can use queued RFC, which is an extension of transactional RFC. In qRFC, you place each function call in a logical queue. A function call cannot be executed until all of its predecessors in the queue have been processed. Queued RFC calls are processed asynchronously
For more information on RFC, please go through the link.
http://help.sap.com/saphelp_nw04/helpdata/en/6f/1bd5b6a85b11d6b28500508b5d5211/content.htm
Have a look at this link.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE2/BCFESDE2.pdf
http://help.sap.com/saphelp_47x200/helpdata/en/22/042860488911d189490000e829fbbd/frameset.htm.
Rewords some points.
Rgds,
P.Nag

How to create a simple idoc in practice? can you provide an example?

how to create a simple idoc in practice? can you provide an example with full source code?

Try with the follwoing steps
Sending System(Outbound ALE Process)
Tcode SALE ³ for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ¡V Create Model View
Tcode BD82 ¡V Generate partner Profiles & Create Ports
Tcode BD64 ¡V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ³ for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ¡V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ¡V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 ¡V Send Material Data
Tcode WE05 ¡V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Thanks & regards
Sreenivas
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Take a look at this guide.
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
http://www.sappro.com/downloads/OneClientDistribution.pdf
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
Create The Extension Segment
Transaction: WE31
The first step in extending an IDoc is to create the new segments that will go into that IDoc. There are some rules that you need to follow when creating the segments:
- The name of each segment type must start with Z1
- For each field in the segment you need to define a field name and a
data element.
- The data element for the segment structure must be of data type CHAR.
How to create new segments:
Run the segment maintenance transaction WE31.
Type your new segment name, and click on Create.
Define the fields of your segment:
Field name
Data Element for the field (from the ABAP dictionary).
Do not change the Export length!
Save the segment
Run Segment -->Check to check the segment for consistency.
Release the segment for transport. Select Edit -->Set Release. Note that the Release column now has a check mark.
Create the Extension IDoc Type
Transaction: WE30
After you create the segments to be added to the extension type, you can create the extension type itself. Execute transaction WE30, enter the extension name, select Extension type, and click Create. You now have three options:
Create new type: Does not refer to other extension types
Create copy: Copies info from an extension type that already exists
Create successor: Extends an extension type from a previous release
of R/3. You can only have one version of an extension type for
each release.
Enter the Basic IDoc type that this extension type will extend.
The screen now shows the structure of the IDoc type you used as
a reference.
Position the cursor on one of the segments and click Create. This will insert an extension segment as a child of the selected segment.
NOTE: A segment cannot appear more than once in an IDoc type! You must control the use of duplicate segments with the segment attributes (the next screen).
The segment attribute screen appears. Enter the information and save.
Extension segments should not be mandatory (for future upgrades), and will need to have minimum and maximum number of instances defined. This answers the question, for each instance of the parent segment, how many instances of the child segment may we have?
You can press the Segment Editor pushbutton to view or change the segment definition.
Create the new Message Type
You can only use an extension IDoc type by assigning it to a message type. You can create a new message type for this.
First the message type itself needs to be created.
Transaction: WE81
Create a new entry and save. Use SAP established customer naming conventions (good form is to start with a Z and retain the rest of the related SAP message type, so, for example, MATMAS becomes ZMATMAS).
After creating the message type, associate it with the corresponding Basic IDoc Type and Extension Type. This relationship is used when IDocs are sent to or received from a partner to determine what segments are valid and what the hierarchy for those segments is.
Transaction: WE82
Create a new entry and enter the Message type, Basic IDoc type, Extension type, and Release, and save your data. Note: the release assignment is not valid for prior SAP releases.
One message type can be associated with many basic IDoc types; however, you need a one-to-one relationship for distribution via ALE.
regards,
srinivas
*reward for useful answers*</b>

How to process the Received Idoc in SAP R/3 ? What to be done ?

Hi All
I am working for file to Idoc scenario.....
Idoc received into SAP R/3 but how to process the Idoc data ?
Such it will store in SAP R/3 DB.....
Clearly
How to Process the received idoc data into SAP R/3 ? (this is for inbound idoc)
I hope any one can help me on the processing steps ?
Waiting for valuable inputs form experts
Regards
Rakesh

rakesh
chec <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660">Sample IDoc</a>
normally, based on the idoc types it will get processed. if it is an idoc with master record it will create appropriate master records or if it based for a transaction it will create one.
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098">https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098</a>

How IE works for flat file

Hi all:
As we all know that, when IE gets a idoc's service name from SLD, then use it with idoc's message type and Idoc type to do receiver determniation, what about flat file ? how can we know its Service name and interface name if there is only a flat file on FTP? how IE works for Flat file ?
Couldn't thank you more

Hi,
For any idoc scenarious, you would use business systems rather than business service which is stored in SLD. So the IE would fetch it from SLD at runtime.
For file based scenarious also, you can create business system as type third party and use the same.
Is that answer your question?
Regards
Krish

How to work on RFC, IDOCs in IDES?

Similar Messages

Maybe you are looking for