Hello Akriti,
Some heads up - basXML - is a data format. bgRFC - is an RFC protocol.
You can use bgRFC with "Classic data format" or with "basXML data format".
As a summary, in transaction SM59, the different protocol versions possible are:
"Classic with tRFC" <== with this option, the RFC destination can be used for sRFC, aRFC, qRFC, pRFC, classic t/qRFC but not bgRFC. The data format is the traditional/classic RFC format. By default, this is the setting all destinations have.
"Classic with bgRFC" <== with this option, the RFC destination can be used for sRFC, aRFC, pRFC, bgRFC but not classic t/qRFC. The data format is the traditional/classic RFC format.
"basXML" <== with this option, the RFC destination can be used for sRFC, aRFC, pRFC, bgRFC but not classic t/qRFC. The data format is the new basXML data format.
For your question on basXML performance - see http://help.sap.com/abapdocu_702/en/abenrfc_protocol.htm
Thank you,
Best Regards,
JothiSubaramaniam P
SAP IMS CST
P.S:
If you are wondering about different RFC kinds listed in my reply:
- (1) sRFC – synchronous RFC (CALL FUNCTION...DESTINATION….)
- (2) aRFC – asynchronous RFC (with or without response) (CALL FUNCTION...STARTING NEW TASK… DESTINATION…)
- (3) pRFC – asynchronous RFC over an RFC server group (with or without response) (CALL FUNCTION...STARTING NEW TASK… DESTINATION IN GROUP…).
- (4) Classic tRFC/qRFC – ‘store and execute later’ RFC – execution controlled by qRFC scheduler (CALL FUNCTION...IN BACKGROUND TASK….)
- (5) bgRFC – ‘store and execute later’ RFC – execution controlled by bgRFC scheduler (CALL FUNCTION...IN BACKGROUND UNIT….)