Function parameter lost about php7-sapnwrfc HOT 12 CLOSED

Seems they are not active ([...] Active: false [...]) strange.

from php7-sapnwrfc.

Try calling $func->setParameterActive('FMI_MATNR', true) and check if it works.
There is a known bug with parameter activatation, I'll have a look...

from php7-sapnwrfc.

That works.

>> RfcOpenConnection
>> RfcOptions
    // ...
<< RfcOptions

>> RfcConnection name="none"
Handle = 108726000 ConvID = 43018472
<< RfcConnection

<< RfcOpenConnection returned RFC_OK

>> RfcGetFunctionDesc
RfcGetFunctionDesc(Z_PPP_MAT_GET_METADATA) via handle 108726000
RfcGetFunctionDesc(Z_PPP_MAT_GET_METADATA) via handle 108726000 (SID=T11) returned 00000000067237F0
<< RfcGetFunctionDesc returned RFC_OK

>> RfcInvoke
Invoking Z_PPP_MAT_GET_METADATA on handle 108726000

>> RfcFunction name="Z_PPP_MAT_GET_METADATA"
>> IMPORTING parameters
>> FMI_LAEDA, RFCTYPE_DATE, Length: 16, Active: false, Requested: false
    Value: 0000-00-00
<< FMI_LAEDA

>> FMI_MATNR, RFCTYPE_CHAR, Length: 36, Active: true, Requested: false
    Value: 887070
<< FMI_MATNR

>> FMI_MTART, RFCTYPE_CHAR, Length: 8, Active: false, Requested: false
    Value: 
<< FMI_MTART

<< IMPORTING parameters

>> CHANGING parameters
<< CHANGING parameters

from php7-sapnwrfc.

OK, use that as a workaround for now. I hope to find enough time to rework the parameter handling this week. I'll keep you posted.

Thanks for testing 👍

from php7-sapnwrfc.

Maybe just call $func->setParameterActive('FMI_MATNR', true) when a parameter is provided?

NO problem. Testing is important to get it into production asap ;-)

from php7-sapnwrfc.

Yes, the plan is to have a HashTable save the activation state and activate each parameter before invoking the RFC.

from php7-sapnwrfc.

Can't really reproduce this one either... all parameters seem to be active by default.

from php7-sapnwrfc.

Hmm...cant provide you more then the trace and the used code currently...

from php7-sapnwrfc.

No problem.

from php7-sapnwrfc.

I can't really reproduce your issue. For me, all parameters are active by default. Calling setParameterActive() for all FM parameters seems not to be a solution as it causes segfaults when exceptions occur in the FM...
But there have been changes to parameter handling, so maybe your issue is already resolved.

from php7-sapnwrfc.

OK, the new implementation now makes sure that all parameters passed as arguments to invoke() are activated. This seems to work and does not cause any strange errors.

from php7-sapnwrfc.

fixed in 0.7.0

from php7-sapnwrfc.