Comments (5)
@spacem, node-rfc issues here are related to nodejs/RFC connectivity. If node-rfc technically works, questions regarding particular function module usage or parameters' semantic can be posted and discussed on https://www.sap.com/community.html
from node-rfc.
@bsrdjan node-rfc technically does not work for calling this bapi
I believe node-rfc automatically passes all the tables right? Well that is great for most cases but for this bapi we need to NOT pass the hierarchy table.
from node-rfc.
@spacem, can you test this BAPI using test transaction SE37, or small ABAP test report, and check if correct results returned there, without using node-rfc? You are right, all result tables are returned from node-rfc to nodejs client and not sending some of them could be considered as a new feature.That might however not help in this particular case.
Can you try to get correct results in ABAP report or SE37 and post correct input / output parameters' values? I will also check this BAPI in more detail.
from node-rfc.
Sorry for the long delay in replying. This has been a stopper for us so we started implementing by exposing bapi via soamanager (ie. soap requests). In an se37 test the bapi gives the same error and I cant see how to exclude the tables from there.. I can give you examples using soap XML though if that is useful.
Calling this gives the same error as with node-rfc:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:sap-com:document:sap:rfc:functions">
<soapenv:Header/>
<soapenv:Body>
<urn:EAM_TASKLIST_GET_DETAIL>
<ET_HDR_HIERARCHY>
</ET_HDR_HIERARCHY>
<ET_OPR_HIERARCHY>
</ET_OPR_HIERARCHY>
<ET_HEADERS>
</ET_HEADERS>
<ET_RETURN>
</ET_RETURN>
<IV_PLNTY>A</IV_PLNTY>
<IV_PLNNR>00000008</IV_PLNNR>
<IV_PLNAL>01</IV_PLNAL>
</urn:EAM_TASKLIST_GET_DETAIL>
</soapenv:Body>
</soapenv:Envelope>
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
<soap-env:Header/>
<soap-env:Body>
<n0:EAM_TASKLIST_GET_DETAILResponse xmlns:n0="urn:sap-com:document:sap:rfc:functions">
<ET_COMPONENTS/>
<ET_HDR_HIERARCHY/>
<ET_HEADERS/>
<ET_MPACKAGES/>
<ET_OPERATIONS/>
<ET_OPR_HIERARCHY/>
<ET_PRTS/>
<ET_RELATIONS/>
<ET_RETURN>
<item>
<TYPE>E</TYPE>
<ID>DIWP1</ID>
<NUMBER>212</NUMBER>
<MESSAGE>Task list A 00000008 is not hierarchical</MESSAGE>
<LOG_NO/>
<LOG_MSG_NO>000000</LOG_MSG_NO>
<MESSAGE_V1>A</MESSAGE_V1>
<MESSAGE_V2>00000008</MESSAGE_V2>
<MESSAGE_V3/>
<MESSAGE_V4/>
<PARAMETER>HIERARCHY</PARAMETER>
<ROW>0</ROW>
<FIELD/>
<SYSTEM>ARTEST</SYSTEM>
</item>
</ET_RETURN>
<ET_SPACK_CONTR_LIMITS/>
<ET_SPACK_LIMITS/>
<ET_SPACK_LINES/>
<ET_SPACK_OUTLINES/>
<ET_TEXT/>
<ET_TEXT_LINES/>
</n0:EAM_TASKLIST_GET_DETAILResponse>
</soap-env:Body>
</soap-env:Envelope>
but when I pass only the tables I need (ie. the headers) it works fine:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:sap-com:document:sap:rfc:functions">
<soapenv:Header/>
<soapenv:Body>
<urn:EAM_TASKLIST_GET_DETAIL>
<ET_HEADERS>
</ET_HEADERS>
<ET_RETURN>
</ET_RETURN>
<IV_PLNTY>A</IV_PLNTY>
<IV_PLNNR>00000008</IV_PLNNR>
<IV_PLNAL>01</IV_PLNAL>
</urn:EAM_TASKLIST_GET_DETAIL>
</soapenv:Body>
</soapenv:Envelope>
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
<soap-env:Header/>
<soap-env:Body>
<n0:EAM_TASKLIST_GET_DETAILResponse xmlns:n0="urn:sap-com:document:sap:rfc:functions">
<ET_COMPONENTS/>
<ET_HDR_HIERARCHY/>
<ET_HEADERS>
<item>
<MANDT>000</MANDT>
<PLNTY>A</PLNTY>
<PLNNR>00000008</PLNNR>
<PLNAL>01</PLNAL>
<ZAEHL>00000001</ZAEHL>
<DATUV>2017-09-12</DATUV>
<TECHV/>
<AENNR/>
<LOEKZ/>
<PARKZ/>
<ANDAT>2017-09-12</ANDAT>
<ANNAM>S0017500464</ANNAM>
<AEDAT>2018-02-06</AEDAT>
<AENAM>S0017500464</AENAM>
<VERWE/>
<WERKS>TEST</WERKS>
<STATU>4</STATU>
<PLNME/>
<LOSVN>0.0</LOSVN>
<LOSBS>99999999.0</LOSBS>
<VAGRP/>
<AESZN/>
<KTEXT>test group counter</KTEXT>
<TXTSP/>
<ABDAT>0000-00-00</ABDAT>
<ABANZ>0</ABANZ>
<PROFIDNETZ/>
<KOKRS/>
<QVEWERKS/>
<QVEMENGE/>
<QVEVERSION/>
<QVEDATUM>0000-00-00</QVEDATUM>
<QVEGRUPPE/>
<QVECODE/>
<QDYNREGEL/>
<QDYNHEAD/>
<QPRZIEHVER/>
<QVERSNPRZV/>
<QKZRASTER/>
<QDYNSTRING/>
<STRAT>A</STRAT>
<PPOOL/>
<ISTRU>000000000000000001</ISTRU>
<IWERK>TEST</IWERK>
<ANLZU/>
<ARBID>00000000</ARBID>
<EXTNUM/>
<DELKZ/>
<ARBTY/>
<STUPR/>
<CLNDR/>
<PRTYP>0</PRTYP>
<REODAT>0000-00-00</REODAT>
<NETID>00000000</NETID>
<FLG_CHK>X</FLG_CHK>
<PSPNR>00000000</PSPNR>
<TTRAS>000000</TTRAS>
<KZKFG/>
<PLNNR_ALT/>
<FLG_CAPO/>
<STLTY/>
<STLNR/>
<STLAL/>
<SLWBEZ/>
<PPKZTLZU/>
<CHRULE/>
<CCOAA>000</CCOAA>
<ST_ARBID>00000000</ST_ARBID>
<MEINH/>
<UMREZ>1</UMREZ>
<UMREN>1</UMREN>
<BMSCH>1.0</BMSCH>
<ADPSP/>
<MS_FLAG/>
<TSTMP_BW>20180206052934</TSTMP_BW>
<MES_ROUTINGID/>
<XHIERTL/>
<TL_EXTID/>
<DATUB>9999-12-31</DATUB>
<AENNR_AUS/>
<KAP_ARBPL/>
<ST_ARBPL/>
<STAUFG/>
<LINE/>
<AEUZEIT>00:00:00</AEUZEIT>
<QM_IP_TYPE_ALLOWED/>
<ARBPL/>
<NNAME/>
<EQUNR/>
<TPLNR/>
</item>
</ET_HEADERS>
<ET_MPACKAGES/>
<ET_OPERATIONS/>
<ET_OPR_HIERARCHY/>
<ET_PRTS/>
<ET_RELATIONS/>
<ET_RETURN/>
<ET_SPACK_CONTR_LIMITS/>
<ET_SPACK_LIMITS/>
<ET_SPACK_LINES/>
<ET_SPACK_OUTLINES/>
<ET_TEXT/>
<ET_TEXT_LINES/>
</n0:EAM_TASKLIST_GET_DETAILResponse>
</soap-env:Body>
</soap-env:Envelope>
While it is a nice feature of node-rfc not have to pass the correct structures you are limiting calls to this type of bapi. Maybe this is the only bapi function that gives different results based on the parameters but I feel also it is useful for many standard bapi to be able to load only the data you want instead of all the data available.
from node-rfc.
@spacem it took a bit longer and new feature is now added to 0.1.15 release, together with few other improvements.
Please check the unit test for the semantic and let me know if works for you?
from node-rfc.
Related Issues (20)
- The specified module could not be found. node.napi.node HOT 2
- Docker container hung if sap does not respond to RFM call HOT 1
- error: ‘condition_variable’ in namespace ‘std’ does not name a type
- Can't able to upload excel file using node rfc HOT 1
- Change we change the default port 3300 to 3600 without changing connection string HOT 4
- receving idoc using node-rfc HOT 3
- Installation fails HOT 14
- [rl-reuse_tool-2] Violation against OSS Rules of Play
- [rl-reuse_tool-4] Violation against OSS Rules of Play
- Problem with node 20.10 LTS HOT 1
- Can't get environment on Windows env HOT 2
- Dynamic Connection and Cache HOT 8
- node-rfc installation not working HOT 2
- Difference between client.call and client.invoke HOT 4
- Using node-rfc on web workers HOT 1
- Getting Error: Conversion Error between Character Sets HOT 1
- SAP document listener in node js HOT 1
- TypeScript types for exceptions
- Node Js server crashes after a few RFC calls
- device or resource busy
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from node-rfc.