Can we use OM-AR service mappings for multiple contexts in AR Invoice Header?

Summary:

We have created multiple contexts under AR Invoice Header (flexfield code: RA_CUSTOMER_TRX). We want to use OM-AR service mappings to pass values to more than 1 AR context. However, under a specific AR entity (ex: TransactionInterfaceHeaderDff) we can have only one value provided for context code (i.e. __FLEX_Context).

We want to understand if the system supports only one context for one AR entity. As we would want to always pass values to multiple AR contexts, we cannot use conditions in algorithms/expressions to dynamically set values for XsiType and __FLEX_Context.

Content (please ensure you mask any confidential information):