| Author |
Message
|
| SKK |
 Posted: Sat Dec 29, 2012 2:35 pm Post subject: WMB 8 - SAP Request Node - BAPI RFC Synchronous Call |
 |
|
Acolyte
Joined: 09 May 2005
Posts: 67
|
Hi
We are using WMB 8 to integrate with SAP for Synchrnous RFC simple BAPI Call. (Retrieve verb)
We are able to connect to SAP and execute function, but we are getting emty data object. Paramters passed to function call are valid, as its getting executed success within SAP
There is date parameter in function call and we are using yyyymmdd format.
Query is as per documentation, SAP request node, we need to specify message set and its mandatory. but its blank becuase in adapter configuration, we dont get message set option.
below is user trace.
2012-12-27 14:12:13.001991 3099 UserTrace BIP3484E: ''Trace SAP logon configuration values*****''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2012-12-27 14:12:13.002222 3099 UserTrace BIP3484E: ''UserName=xxxx''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2012-12-27 14:12:13.002342 3099 UserTrace BIP3484E: ''Password=******''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2012-12-27 14:12:13.002532 3099 UserTrace BIP3484E: ''Language=EN''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2012-12-27 14:12:13.002698 3099 UserTrace BIP3484E: ''Codepage=1100''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2012-12-27 14:12:13.002860 3099 UserTrace BIP3484E: ''Client=530''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2012-12-27 14:12:13.003061 3099 UserTrace BIP3484E: ''ApplicationServerHost=xxxxxx'
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2012-12-27 14:12:13.003236 3099 UserTrace BIP3484E: ''SystemNumber=00''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2012-12-27 14:12:13.003422 3099 UserTrace BIP3484E: ''GatewayHost=''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2012-12-27 14:12:13.003604 3099 UserTrace BIP3484E: ''GatewayService=''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2012-12-27 14:12:13.003774 3099 UserTrace BIP3484E: ''LogonGroup=''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2012-12-27 14:12:13.003945 3099 UserTrace BIP3484E: ''SAPSystemID=''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2012-12-27 14:12:13.004136 3099 UserTrace BIP3484E: ''MessageServerHost=''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2012-12-27 14:12:13.004266 3099 UserTrace BIP3484E: ''RFCTraceOn=false''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2012-12-27 14:12:13.004460 3099 UserTrace BIP3484E: ''RFCTraceLevel=''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2012-12-27 14:12:13.004587 3099 UserTrace BIP3484E: ''RFCTracePath=''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2012-12-27 14:12:13.004714 3099 UserTrace BIP3484E: ''ABAPDebug=false''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2012-12-27 14:12:13.004834 3099 UserTrace BIP3484E: ''END of Trace SAP logon configuration values*****''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2012-12-27 14:12:13.004961 3099 UserTrace BIP3484E: ''X509cert=''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2012-12-27 14:12:13.005088 3099 UserTrace BIP3484E: ''SncMode=false''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2012-12-27 14:12:13.005214 3099 UserTrace BIP3484E: ''SncLib=''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2012-12-27 14:12:13.005340 3099 UserTrace BIP3484E: ''SncPartnername=''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2012-12-27 14:12:13.005466 3099 UserTrace BIP3484E: ''SncQop=0''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2012-12-27 14:12:13.005591 3099 UserTrace BIP3484E: ''SncMyname=''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2012-12-27 14:12:13.005711 3099 UserTrace BIP3484E: ''END of Trace SAP logon configuration values*****''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2012-12-27 14:12:13.006025 3099 UserTrace BIP3484E: ''++ Inside (SPI) the MANAGED Resource Adapter! Calling SAPManagedConnection.begin().''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2012-12-27 14:12:13.006286 3099 UserTrace BIP3484E: ''AFC Version : 7.0.0.3''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2012-12-27 14:12:13.006929 3099 UserTrace BIP3484E: ''BapiName is ZBAPI_xxxxxxxx''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2012-12-27 14:12:13.017838 3099 UserTrace BIP11002I: The call to method ''executeSapZbapixxxxxxx'' was successful.
The message flow ''MF_POC'' includes a ''SAP'' request node. The request to call method ''executeSapxxxxxxxx'' was successful.
2012-12-27 14:12:13.018291 3099 UserTrace BIP4142I: Evaluating cniElementSet'Name'. Changing value from ''XMLNSC'' to ''DataObject''.
Element ''Name'' has been changed to ''DataObject''.
No user action required.
2012-12-27 14:12:13.018348 3099 UserTrace BIP4144I: Entered function 'cniCreateElementAsLastChild'((*ptr)118295700, (*ptr)1150c3800, 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A').
Entered the specified function with the specified parameters.
No user action required.
2012-12-27 14:12:13.018364 3099 UserTrace BIP4145I: Exiting function 'cniCreateElementAsLastChild' with result: 'CCI_SUCCESS'(0).
About to exit the specified the function with the specified result.
No user action required.
2012-12-27 14:12:13.018382 3099 UserTrace BIP4142I: Evaluating cniElementSet'Type'. Changing value from '0' to '16777216'.
Element ''Type'' has been changed to '16777216'.
No user action required.
2012-12-27 14:12:13.018398 3099 UserTrace BIP4142I: Evaluating cniElementSet'Name'. Changing value from '''' to ''SapZbapixxxxxxxx''.
Element ''Name'' has been changed to ''SapZbapixxxxxx''.
No user action required.
2012-12-27 14:12:13.018418 3099 UserTrace BIP4142I: Evaluating cniElementSet'Namespace'. Changing value from '''' to ''http://www.ibm.com/xmlns/prod/websphere/j2ca/sap/sapzbapixxxxxxxxx''.
Element ''Namespace'' has been changed to ''http://www.ibm.com/xmlns/prod/websphere/j2ca/sap/sapzbapixxxxxxxxxxx''.
No user action required.
2012-12-27 14:12:13.020689 3099 UserTrace BIP3903I: Node (class='ComIbmSAPRequestNode', name='SAP Request') propagating to 'out' terminal.
The specified node is about to propagate a message to the specified terminal.
No user action required. This is an information message.
below is RFC Trace
*> RfcCall
FUNCTION ZBAPIXXXXXXXXX
handle = 1
parameter[0].name = RPA_BDD
parameter[0].type = DATE
parameter[0].length = 16
parameter[1].name = RPA_TNR
parameter[1].type = CHAR
parameter[1].length = 40
parameter[2].name = RPA_WID
parameter[2].type = CHAR
parameter[2].length = 20
parameter[3].name = RT_LOCATIO
parameter[3].type = CHAR
parameter[3].length = 8
parameter = <null>
tables = <null>
>>>> [1] <unknown> R/3 <ac: 11> >>> FLUSH (READ) (17437739)
UUID: RfcCallNew sent the uuid to the partner:12731280-503B-11E2-902B-C012C0A87F26
>>>> [1] <unknown> R/3 <ac: 12> >>> WRITE (17437739)
000000 | 05020000 0502000B 00060037 00320030 |...........7.2.0
000010 | 000B0102 0028005A 00420041 00500049 |.....(.Z.B.A.P.I
000020 | 005F0046 00520041 00550044 005F0044 |._.xxxxxxxxx._.D
000030 | 00450054 00450043 00540030 00310102 |.xxxxxxxxxxxx.1.
000040 | 05140010 12731280 503B11E2 902BC012 |.....s..P;...+..
000050 | C0A87F26 05140512 00000512 02050022 |...&..........."
000060 | 00450058 005F0049 00540045 004D005F |.xxxxxxxxxxxxxx._
000070 | 00440049 00530043 004F0055 004E0054 |.xxxxxxxxxxxxx
000080 | 00530205 0201000E 00520050 0041005F |.S.......R.P.A._
000090 | 00420044 00440201 02030010 00320030 |.B.D.D.......2.0
0000a0 | 00310030 00300036 00300039 02030201 |.1.0.0.6.0.9....
0000b0 | 000E0052 00500041 005F0054 004E0052 |...R.P.A._.T.N.R
0000c0 | 02010203 00280036 00340032 00320020 |.....(.6.4.2.2.
0000d0 | 00200020 00200020 00200020 00200020 |. . . . . . . .
0000e0 | 00200020 00200020 00200020 00200203 |. . . . . . . ..
0000f0 | 0201000E 00520050 0041005F 00570049 |.....R.P.A._.W.I
000100 | 00440201 02030014 00330035 00200020 |.D.......3.5. .
000110 | 00200020 00200020 00200020 02030201 |. . . . . . ....
000120 | 00140052 0054005F 004C004F 00430041 |...R.T._.L.O.C.A
000130 | 00540049 004F0201 02030008 00310032 |.T.I.O.......1.2
000140 | 00370020 0203FFFF 0000FFFF 00000000 |.7. ............
>> CPIC native call CMSEND [1] convid: 17437739 15:35:41,863
<< CPIC native call CMSEND [1] convid: 17437739 rc: 0 15:35:41,864
>>>> [1] <unknown> R/3 <ac: 13> >>> FLUSH(WRITE) (17437739)
<* RfcCall >Thu Dec 27 15:35:41,864< successful *>
>>> RfcReceive [1] >Thu Dec 27 15:35:41,865< ...
>>>> [1] <unknown> R/3 <ac: 14> >>> FLUSH(WRITE) (17437739)
>> CPIC native call cpic_coxread [1] convid: 17437739 15:35:41,865
<< CPIC native call cpic_coxread [1] convid: 17437739 rc: 0 15:35:41,869
>>>> [1] <unknown> R/3 <ac: 15> >>> READ (17437739)
000000 | 05000000 05000503 00000503 05140010 |................
000010 | 12731280 503B11E2 902BC012 C0A87F26 |.s..P;...+.....&
000020 | 05140512 00000512 3C020000 3C023C05 |........<...<.<.
000030 | 00133C45 585F4954 454D5F44 4953434F |..<xx_xxxx_xxxxx
000040 | 554E5453 3E3C053C 0500143C 2F45585F |xxxx><.<...</xx_
000050 | 4954454D 5F444953 434F554E 54533E3C |xxxxxxxxxxxxx><
000060 | 053C0200 003C0201 30005000 53004100 |.<...<..0.P.S.A.
000070 | 50004C00 5A004200 41005000 49005F00 |P.L.Z.B.A.P.I._.
000080 | 46005200 41005500 44005F00 44004500 |xxxxxxxx._.xxxx.
000090 | 54004500 43005400 5F005000 4F004300 |xxxxxxxxxxxxxxx.
0000a0 | 20002000 20002000 20002000 20002000 | . . . . . . . .
0000b0 | 20002000 20002000 20002001 30066700 | . . . . . .0.g.
0000c0 | 084091BC 00000000 000667FF FF0000FF |.@........g.....
0000d0 | FF000000 00000000 00000000 00000000 |................
Received DebugStop = 0
UUID: ab_rfccheck_uuid compare uuid's 12731280-503B-11E2-902B-C012C0A87F26
Receiving XML parameter: xxxxxxxx
*> RfcReceive ...
handle = 1
parameter[0].name = xxxxxxxxx
parameter[0].type = XMLDATA
parameter[0].length = 39
parameter = <null>
tables = <null>
<* RfcReceive >Thu Dec 27 15:35:41,874< successful *>
>>> RfcCall [1] >Thu Dec 27 15:35:41,882< ...
*> RfcCall
FUNCTION BAPI_TRANSACTION_COMMIT
handle = 1
parameter = <null>
parameter = <null>
tables = <null>
>>>> [1] <unknown> R/3 <ac: 16> >>> FLUSH (READ) (17437739)
UUID: RfcCallNew sent the uuid to the partner:12731280-503B-11E2-902B-C012C0A87F26
>>>> [1] <unknown> R/3 <ac: 17> >>> WRITE (17437739)
000000 | 05020000 0502000B 00060037 00320030 |...........7.2.0
000010 | 000B0102 002E0042 00410050 0049005F |.......B.A.P.I._
000020 | 00540052 0041004E 00530041 00430054 |.T.R.A.N.S.A.C.T
000030 | 0049004F 004E005F 0043004F 004D004D |.I.O.N._.C.O.M.M
000040 | 00490054 01020514 00101273 1280503B |.I.T.......s..P;
000050 | 11E2902B C012C0A8 7F260514 05120000 |...+.....&......
000060 | 05120205 000C0052 00450054 00550052 |.......R.E.T.U.R
000070 | 004E0205 FFFF0000 FFFF0000 00000000 |.N..............
>> CPIC native call CMSEND [1] convid: 17437739 15:35:41,885
<< CPIC native call CMSEND [1] convid: 17437739 rc: 0 15:35:41,886
>>>> [1] <unknown> R/3 <ac: 18> >>> FLUSH(WRITE) (17437739)
<* RfcCall >Thu Dec 27 15:35:41,886< successful *>
>>> RfcReceive [1] >Thu Dec 27 15:35:41,887< ...
>>>> [1] <unknown> R/3 <ac: 19> >>> FLUSH(WRITE) (17437739)
>> CPIC native call cpic_coxread [1] convid: 17437739 15:35:41,888
<< CPIC native call cpic_coxread [1] convid: 17437739 rc: 0 15:35:41,896
>>>> [1] <unknown> R/3 <ac: 20> >>> READ (17437739)
000000 | 05000000 05000503 00000503 05140010 |................
000010 | 12731280 503B11E2 902BC012 C0A87F26 |.s..P;...+.....&
000020 | 05140512 00000512 0201000C 00520045 |.............R.E
000030 | 00540055 0052004E 02010203 04400020 |.T.U.R.N.....@.
000040 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000050 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000060 | 00200020 00200020 00300030 00300020 |. . . . .0.0.0.
000070 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000080 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000090 | 00200020 00200020 00200020 00200020 |. . . . . . . .
0000a0 | 00200020 00200020 00200020 00200020 |. . . . . . . .
0000b0 | 00200020 00200020 00200020 00200020 |. . . . . . . .
0000c0 | 00200020 00200020 00200020 00200020 |. . . . . . . .
0000d0 | 00200020 00200020 00200020 00200020 |. . . . . . . .
0000e0 | 00200020 00200020 00200020 00200020 |. . . . . . . .
0000f0 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000100 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000110 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000120 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000130 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000140 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000150 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000160 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000170 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000180 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000190 | 00200020 00200020 00200020 00200020 |. . . . . . . .
0001a0 | 00200020 00200020 00200020 00200020 |. . . . . . . .
0001b0 | 00200020 00200020 00200020 00200020 |. . . . . . . .
0001c0 | 00200020 00200020 00200020 00200020 |. . . . . . . .
0001d0 | 00200020 00200020 00200020 00200020 |. . . . . . . .
0001e0 | 00200020 00200020 00200020 00200020 |. . . . . . . .
0001f0 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000200 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000210 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000220 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000230 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000240 | 00200020 00200020 00200020 00200030 |. . . . . . . .0
000250 | 00300030 00300030 00300020 00200020 |.0.0.0.0.0. . .
000260 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000270 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000280 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000290 | 00200020 00200020 00200020 00200020 |. . . . . . . .
0002a0 | 00200020 00200020 00200020 00200020 |. . . . . . . .
0002b0 | 00200020 00200020 00200020 00200020 |. . . . . . . .
0002c0 | 00200020 00200020 00200020 00200020 |. . . . . . . .
0002d0 | 00200020 00200020 00200020 00200020 |. . . . . . . .
0002e0 | 00200020 00200020 00200020 00200020 |. . . . . . . .
0002f0 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000300 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000310 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000320 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000330 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000340 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000350 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000360 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000370 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000380 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000390 | 00200020 00200020 00200020 00200020 |. . . . . . . .
0003a0 | 00200020 00200020 00200020 00200020 |. . . . . . . .
0003b0 | 00200020 00200020 00200020 00200020 |. . . . . . . .
0003c0 | 00200020 00200020 00200020 00200020 |. . . . . . . .
0003d0 | 00200020 00200020 00200020 00200020 |. . . . . . . .
0003e0 | 00200020 00200020 00200020 00200020 |. . . . . . . .
0003f0 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000400 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000410 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000420 | 00200020 00200020 00200000 00000020 |. . . . . .....
000430 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000440 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000450 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000460 | 00200020 00200020 00200020 00200020 |. . . . . . . .
000470 | 00200020 00200020 00200020 00200203 |. . . . . . . ..
000480 | 01300050 00530041 0050004C 00420041 |.0.P.S.A.P.L.B.A
000490 | 00500054 00200020 00200020 00200020 |.P.T. . . . . .
0004a0 | 00200020 00200020 00200020 00200020 |. . . . . . . .
0004b0 | 00200020 00200020 00200020 00200020 |. . . . . . . .
0004c0 | 00200020 00200020 00200020 00200020 |. . . . . . . .
0004d0 | 00200020 01300667 000840B4 66000000 |. . .0.g..@.f...
0004e0 | 00000667 FFFF0000 FFFF0000 00000000 |...g............
Received DebugStop = 0
UUID: ab_rfccheck_uuid compare uuid's 12731280-503B-11E2-902B-C012C0A87F26
Receiving parameter RETURN
*> RfcReceive ...
handle = 1
parameter[0].name = RETURN
parameter[0].type = STRUCTURE
parameter[0].length = 1088
parameter = <null>
tables = <null>
_________________
Regards,
SKK |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Sat Dec 29, 2012 10:58 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
Are you sure the SAP system number is 00?
According to the trace this is what you are passing upon logon...
I suppose the /etc/services table contains all the sap ports (300 of them)...
Also I would avoid passing null as a table. You might be better off creating a table of the right format and passing it with 0 rows... As I understand it this is really more of an input/output thing...
Also make sure to query your result before the BAPI commit call as it will overwrite the current results.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| SKK |
| Posted: Mon Dec 31, 2012 2:38 am Post subject: |
|
|
Acolyte
Joined: 09 May 2005
Posts: 67
|
We confirmed with SAP team on SAP System number as 00
can you elaborate on table as null? is it in SAP side on their function call response?
_________________
Regards,
SKK |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Dec 31, 2012 2:45 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
| SKK wrote: |
We confirmed with SAP team on SAP System number as 00
can you elaborate on table as null? is it in SAP side on their function call response? |
For SAP the table is an input/output parameter. So passing in a table as null could pretty much ensure that you never get the corresponding return table filled. Pass a table with 0 rows, if your call does not require a table, and you might get the return table filled....
Have fun.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| SKK |
| Posted: Mon Dec 31, 2012 3:19 am Post subject: |
|
|
Acolyte
Joined: 09 May 2005
Posts: 67
|
Thanks for quick reply
But we are passing the respective values to function call. there are four paraemters and we are passing them in XMLNSC message (Schema created during Adapter discovery)
parameter[0].name = RPA_BDD
parameter[0].type = DATE
parameter[0].length = 16
parameter[1].name = RPA_TNR
parameter[1].type = CHAR
parameter[1].length = 40
parameter[2].name = RPA_WID
parameter[2].type = CHAR
parameter[2].length = 20
parameter[3].name = RT_LOCATIO
parameter[3].type = CHAR
parameter[3].length = 8
parameter = <null>
tables = <null>
Are you suggesting, function is invoked with null paramters and that why we are receiving null data object.
_________________
Regards,
SKK |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Dec 31, 2012 3:37 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| SKK wrote: |
parameter[3].name = RT_LOCATIO
parameter[3].type = CHAR
parameter[3].length = 8
|
the .length param value might not be correct. 'RT_LOCATIO' is more than 8 chars
SAP is exceedingly picky about everything under the sun.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| SKK |
| Posted: Mon Dec 31, 2012 6:16 am Post subject: |
|
|
Acolyte
Joined: 09 May 2005
Posts: 67
|
Thanks.
Actually, for all parameters in RFC trace, they are showing the double length of actual
for example : RT_LOCATIO is actually CHAR 4, but in RFC trace it shows CHAR 8.
also below Trace suggests, we are getting some reply parameter back
Receiving XML parameter: EX_XXXXXXXXXXX
*> RfcReceive ...
handle = 1
parameter[0].name = EX_XXXXXXXXXX
parameter[0].type = XMLDATA
parameter[0].length = 39
parameter = <null>
tables = <null>
<* RfcReceive >Thu Dec 27 15:35:41,874< successful *>
>>> RfcCall [1] >Thu Dec 27 15:35:41,882< ...
FUNCTION BAPI_TRANSACTION_COMMIT
But in SAP Request out terminal , it come as blank data object.
Question here, is message set mandatory for SAP Request node?
_________________
Regards,
SKK |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Dec 31, 2012 6:31 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
In my dealings with SAP (using the SAP Request Node) I have always used a message set.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| SKK |
| Posted: Mon Dec 31, 2012 6:43 am Post subject: |
|
|
Acolyte
Joined: 09 May 2005
Posts: 67
|
Thanks!!
WMB 8, doesnt provide option of creating message set from SAP Discovery and since its not editable, we cannot specify customised message set either 
_________________
Regards,
SKK |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Dec 31, 2012 1:27 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
There is nothing stopping you from doing the discovery from a V7 toolkit and creating the message set that way.
As for V8, I'd probably raise a PMR to get an official explanation as to why this IMHO essential feature is missing from V8.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| GeneRK4 |
| Posted: Tue Aug 20, 2013 12:09 pm Post subject: |
|
|
Master
Joined: 08 Jul 2013
Posts: 220
|
Does anyone know how to get the message set from SAPRequest node BAPI discovery?As it is missing from version8 ,I am unable to create the message set.Even if I try to create from the xsd generated ,it is throwing errors.
I need to create WSDLs.Please help me how to resolve this or what is the alternate solution. |
|
| Back to top |
|
|
| Simbu |
| Posted: Wed Aug 21, 2013 12:23 am Post subject: |
|
|
Master
Joined: 17 Jun 2011
Posts: 289
Location: Tamil Nadu, India
|
|
| Back to top |
|
|
| GeneRK4 |
| Posted: Thu Aug 22, 2013 5:03 am Post subject: |
|
|
Master
Joined: 08 Jul 2013
Posts: 220
|
Yes.I have enabled.But still no.
This is actually WMB version8 product level constraint.
Now,I have created a message set and created a message definiton from xsd.It created mxsd for me !!!Its exactly the same what we got for 6.1. |
|
| Back to top |
|
|
|
|
