BAPI parameter structure and RFC protocol

[raffinkira]

Let's say there is a BAPI A which has a parameter B.

B is a structure and has three fields.

I think the underlying layer would concatenate three fields into a string and transfer it on the internet.

If I change the structure like adding a field to make it four, there is nothing else needs to do, the BAPI still works.

My question is how the RFC protocol works because there seems no re-generation underlying code or something like this.

[Sandra_Rossi]

I think it's not really documented. You may find a few information in the RFC API documentation.

About the topic of parameters, I remember a situation where a component was added in the middle of the structure, there was a short dump at runtime because of incompatible values because values were shifted of one component. It was not due to a check of parameter compatibility, but because of values assigned to the wrong fields. It was with classic RFC parameters, In RFC destinations, there is a code page, so there should be a code page conversion for text parameters (and text components of structures).

I'm not sure how it would react with basXML transmission.