IDOCs are triggered from R/3 and they sit in the ABAP stack. You don't need sender configuration for IDOC communication. So, in your case, you need not to configure IDOC comm channel but a FILE comm channel for the receving end. (Since sender is R/3).
R/3 Settings you need:
1. Using WE20, create the Partner Profile (LS type) and assign DEBMAS message type to the Outbound Parameters.
2. Enter the Sending PORT, Packet Size, IDOC Type (leave the Partner Function Box empty. This is needed for other types like LI, KU etc.,).
3. You are almost set at this point of time and for your info, you don't have to maintain MESSAGE CONTROLS as they are used more in transaction data like PO, SO, DELIVERY, BILLING etc., where you control the trasmission using OUTPUT TYPES etc.,).
4. One important thing to check before using the RFC port is to check the Connection which you can do from SM59, select R/3 connections, double click on PORT then TEST CONNECTION. This is to ensure that it is in place as I have seen people just spending huge time in debuggin in MONI with a message as "RFC connection failure which appears in (may be) bottom most part of the message displayed). " Consulting Tip---just kidding.
5. To read and understand XML message from MONI, just look for fields SNDPRN, RCVRPN etc., for troble shooting purpose and be patient while doing so.
XI Steps needed:
1. Create the a receiver business systems along with necessary SWCV, SWC, PROD (I am sure you are thru with this).
2. In the Int Repository, create the Data Types and Message type (Use standard Message type DEBMAS.DEBMAS06 from Basis Comp drawn from Usage dependencies which you do in SLD, Software catalog)
3. Perform the mapping (you can simplify this by opting to map simlar fields (named identical in the source and receiver). (Seconde ICON from left on top tool bar). Make sure you assign all that you need. ( I would advise to check with your Oracle guys what data they are looking for). I would make this easy if I do an XSLT mapping otherwise, I would prefer to the mapping with most of the config handling. Example: imagine CUSTOMER Account group (KNA1-KTOKD - SAP Table and filed) in R/3 is "0003" and in ORACLE you want this to be like "ABCD" etc., kind of stuff at BASIC LEVEL can be done here.
4.Create an inbound Async message interface. Tip: Async, as you want the message to be persistant and may want to have the retriggering done automatically incase of failures. This helps in fact to debug and if this SYNC, you will not have a clue (unless you know how to track) as it is termed as QoS-BE.
SO you have the Source interface, Target Interface and Mapping program as well. Create Interface and link the SOURCE and TARGET with MESSAGE MAPPING TYPE and drop down to locate the MAPPING PROGRAM created in the above step.
5. Save, generate the change list.
6. Do a test in MESSAGE MAPPING for your confortness.
7. Get into Integration Directory and do the following.
7.1 Create the scenario and assign the business systtems created in first step mentioned above.
7.2 Create the RECEIVER COMM CHANNEL ( uncheck the Check box while assiging the business system which specifies the COMM CHANNEL generation...you don't want to do it this way). Make sure it is FILE ADAPTER, Provide FTP protocol, Specify SERVER,Port, User ID, P/w etc., specify the FOLDER which is accessible to ORACLE (which you have specified in SHELL Script for automatic pickup of the file and make sure they are identical..just to avoid risk)
7.3 Create the Receiver determination and leave SENDER Aggreement as it is not needed. Reason, IDOC need not to have SENDER Config.
7.4 Make sure you have everything set and generate the change list. (Consulting tip....Hit F7 to check the CONSISTENCY when you think you messed it up. This gives you clues (rather a detailed log) in the process log...)
Log into R/3, create a Customer using XD03 and maintain the Basic Data (if you are curious to see what you have done just now).
Check in SXMB_MONI in XI..
I would do this using IDX5 than doing it using SXMB_MONI as it puts everthing in XML and you need to scroll down like 50-60 pages to understand where it failed. IDX5 gives kind of R/3 interface similar to WE02/WE05. Check this initially and get used to MONI too.
If the message looks successful, then go to ADAPTER FRAME WORK and look for your FILE ADAPTER (Comm chanel you created in 7.1, 7.2 above). If is successful, check the FILE in the location you specified and run the shell script then check in the ORACLE table.
Thatz it...
One suggestion;;;
Guys, Please use SAP RECOMMENDED NAMING CONVENTIONS and this makes life easy to understand what you have named. CREATE one name space for every project/scenario you are doing if you think Tech Landscape is reusable.
Still questions...reply..
Good Luck,
Srini.
Incase of Inbound into R/3, you would need an IDOC and corresponding inbound process code and other settings.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.