Qs on generating SAP proxy dll

[irislauyk]

Hi all,

I just starting to use the SAP DCOM Connector Object Builder to create a VC++ proxy dll, so that I can retrieve SAP data from the VB Client.

However, the proxy dll being generated cannot recognize the bapiret1 structure when I call DimAs procedure. Also when I look at the source being generated by the Object Builder the bapiret1.h file is missing. In the class.cpp file, the Return1 parameter has the following definition:

SAP_SCHEMA_PARAMETER(Return1, RETURN1, L"Return parameter", VT_VARIANT, RFCTYPE_STRUCTURE, 470, 0, SAP_ID_SCHEMA_NULL | SAP_ID_SCHEMA_EXPORT | SAP_ID_SCHEMA_OPTIONAL | SAP_ID_SCHEMA_SCALAR)


which in some of the old files should be

SAP_SCHEMA_PARAMETER_STRUCT_1(Return1, RETURN1, L"Return parameter", VT_VARIANT, RFCTYPE_STRUCTURE, BAPIRET1, BAPIRET1, SAP_ID_SCHEMA_NULL | SAP_ID_SCHEMA_EXPORT | SAP_ID_SCHEMA_OPTIONAL | SAP_ID_SCHEMA_STRUCTURE)


how come it does not recognize the BAPIRET1 as a structure anymore ? does anyone has any clues ? where should the problem be ? SAP setting ? the RFC Function Definition ? the BAIPRET1 structure problem ? or the Object Builder ?

any information will be welcome, thanks.

 

[irislauyk]

more information:

current generated cpp:

try
{
CallFunction(L"Z_TEST");
Importing(L"RETURN1", &CAbapScalarType(RFCTYPE_STRUCTURE, 470, 0), Return1);
... ...

EndCallFunction();
}

which should be:

try
{
CallFunction(L"Z_TEST");
ImportingStructure(L"RETURN1", &BAPIRET1_Type, Return1);
... ...

EndCallFunction();
}

what kind of problems will led to this situation? any help will be appreciated. thanks.