Function module BAPI_ALM_ORDER_MAINTAIN has too many parameters ???

[Former Member]

Hi all,

im working with ECC 6.0. I have to generate ALE interface from BAPI_ALM_ORDER_MAINTAIN in order to make it accessible from TIBCO.

The interface is not generated, and the system displays the error message:

<b>Function module BAPI_ALM_ORDER_MAINTAIN has too many parameters.</b>

Any suggestion ?

Thanks in advance

Manuel

PS: I've tried both transactions BDBG and BDFG (Business object BUS2007A, method ORDERMAINTAIN)

Message was edited by:

Manuel Bassani

[Former Member]

Hi Manuel,

What parameters are you passing for this FM? Also, I did a Where-Used List for this FM and came across few hits in ECC 6.0...One of include is:

/NRX/ALM_ORDER_PROC

Just check to see if it is of any use for you...

Regards,

Vivek

[manuel_bassani]

Vivek,

thanks for your reply. For now I'm not using the bapi yet. I'm just trying to make it accessible from outside R/3, but it seems that the generation of the ALE interface fails.

The include /NRX/ALM_ORDER_PROC does not esist in my system.

Best regards,

Manuel

[Former Member]

does the error message have a long text when you click on it?

Rob

[manuel_bassani]

Hi Rob,

unfortunately the long text is missing.

Regards, Manuel

[Former Member]

What is the message class and number of the error?

Rob

[manuel_bassani]

I did a mistake in generating the interface. In fact in transaction BDBG the radiobutton should be set to "Object type" instead of "Interface" (like I did)

Thank you anyway.

Regards,

Manuel

[uwe_schieferstein]

Hello Manuel

Compared to more complex BAPIs the fm BAPI_ALM_ORDER_MAINTAIN has not really that many parameters. Thus, to me this looks like a serious limitation of the TIBCO system.

If this limitation cannot be overcome then you could write your own RFC-enabled function modules which simply wrap the BAPI but expose all mandatory parameters (e.g. IT_METHODS, IT_HEADER) and only part of the optional parameters. In this scenario you would need to call the wrapper RFCs consecutively in order to achieve the same functionality as the standard BAPI.

Regards

Uwe