ā2012 Oct 04 2:01 PM
Hi All,
I have a requirement to implement an inbound IDoc to transfer Dip Reading data from Non SAP Sytem to SAP System.
For this TIBCO (middleware) will trigger the idoc OILBLM_SAVEMULTIPLE01.
Connection between SAP and TIBCO has been established (partner profile, port , destination etc have been created)
In the link below they have mentioned that once the IDOC is received by SAP ,the IDOC itself will call the function module BAPI_BLM_SAVEMULTIPLE to process the meter reading data.
http://help.sap.com/saphelp_afs64/helpdata/en/ae/ef279e313411d4b613006094b9b833/frameset.htm
Question:
1. Can the IDoc call the function module by itself without any configurations required?
2. If not what steps need to be followed in order to achieve the above.?
Regards,
Varun
ā2012 Oct 04 3:08 PM
Hi,
Yes, you need to maintain ditribution kodel and partner profiles.
1. Create a model view in distribution model (BD64) and specify the source and destination systems.
2. Click on Add BAPI button in application tool bar (since this is a BAPI call)
3. Add Obj. name/interface as BUS3063 and method SAVEMULTIPLE
Now in Partner profiles (WE20), in Inbound parameters, double click on the message type and entr process code as BAPI (Inbound BAPI IDoc: Individual processing) or BAPP (Inbound BAPI IDoc: Package Processing) based on your requirement (or just trail & error). These process codes will internally calls the FM - BAPI_BLM_SAVEMULTIPLE.
The above setting should work, but when i tried in my system I couldn't assign object/interface in distribution model as said in point 3 above.I have also checked the business object BUS3063 in SWO1 and inside the method BuLocMeterReading.SaveMultiple, FM BAPI_BLM_SAVEMULTIPLE is assigned (Std..).
Just check in your system, as we have no OIL & IS related modules activated here in our ECC.(May be some switch activations are not done & hence not working in my system).
Regards,
Sravan Guduru.
ā2012 Oct 04 3:08 PM
Hi,
Yes, you need to maintain ditribution kodel and partner profiles.
1. Create a model view in distribution model (BD64) and specify the source and destination systems.
2. Click on Add BAPI button in application tool bar (since this is a BAPI call)
3. Add Obj. name/interface as BUS3063 and method SAVEMULTIPLE
Now in Partner profiles (WE20), in Inbound parameters, double click on the message type and entr process code as BAPI (Inbound BAPI IDoc: Individual processing) or BAPP (Inbound BAPI IDoc: Package Processing) based on your requirement (or just trail & error). These process codes will internally calls the FM - BAPI_BLM_SAVEMULTIPLE.
The above setting should work, but when i tried in my system I couldn't assign object/interface in distribution model as said in point 3 above.I have also checked the business object BUS3063 in SWO1 and inside the method BuLocMeterReading.SaveMultiple, FM BAPI_BLM_SAVEMULTIPLE is assigned (Std..).
Just check in your system, as we have no OIL & IS related modules activated here in our ECC.(May be some switch activations are not done & hence not working in my system).
Regards,
Sravan Guduru.
ā2012 Oct 05 10:02 AM
Hi Sravan,
Thanks for the response.
1. Is configuring a distribution model the only way to go ahead.?
2. How does the business object BUS3063 help
ā2012 Oct 05 10:39 AM
The requirement is as follows:
Standar Idoc Type is available - OILBLM_SAVEMULTIPLE01
Standard Message Type is available - OILBLM_SAVEMULTIPLE
Will the BAPI be called automatically once i configure in we20.
Inbound IDoc, provide the message type there.
What should be the process code.
ā2012 Oct 05 2:23 PM
Hi Varun,
Since you dealing with Dip Reading data, you need to use BUS3062. (my mistake in earlier thread, I have overlooked the key word DIP ).
But it calls BAPI 'BAPI_BLD_SAVEMULTIPLE' not the one specified by you.. I suggest you to check SWO1.
Varun Jandial wrote:
2. How does the business object BUS3063 help
Business objects BUS2062 in the backend object for Save Dip Readings. The BAPI we use is of this object.
Varun Jandial wrote:
1. Is configuring a distribution model the only way to go ahead.?
Not the only way.. you can have RFC calls also. (in this case you need not maintain partner profiles) also)...
by the way, is maintaining distribution model, causeing issue in your system too?
Regards,
ā2012 Oct 05 2:30 PM
Hi Sravan,
If you can follow the link below and tell me the steps to follow to implement the IDOC.
As i am new to IDocs i am not being able to understand how the link mentions that the message type will call the BAPI.
http://help.sap.com/saphelp_afs64/helpdata/en/ae/ef279e313411d4b613006094b9b833/frameset.htm
Thanks.
ā2012 Oct 08 2:17 PM
Hi Varun,
I have gone through the link.
The process(Distribution model, partner profiles etc...) i mentioned in earlier thread is normal procedure we usually follow for SD/MM/FI etc..modules/related documents.
I am not sure, if something else(configirations) needs to be done in oil related modules..
checking for SAP documents.
lets us gone by trail & error method until then..
Q1: Do you have issue in maintaining distribution model.. (any error)..?
Regards,
SG.