MLS Support in AIA PIPs involving Oracle EBS as an edge application
By ankit.goel on Jul 30, 2009
Oracle EBS supports UTF-8 characters and hence the PIPs involving EBS as a participating application would normally be a candidate for being MLS (Multiple Language Support) compliant. All language specific operations in EBS are done based on EBS User preference settings and hence through FND APPS context.
In EBS Provider flows, the data sent into the PL/SQL API gets inserted/updated into the user's language specific row in TL tables. So AIA layer needs to set the FND APPS context or use the correct integration user in Oracle Apps Adapter. This can be done based on EBM Header's language code using which we can set the integration user dynamically, say using a DVM or some configuration mapping.
In Requestor flows, again an EBS API returns data in one language at a time. Most of the EBS APIs return data based on the user preferences set in FND APPS context. So AIA layer needs to set the FND APPS context or use the correct integration user in Oracle Apps Adapter for each language, and then call the PL/SQL API.
For EBS Interface tables, generally no language specific rows are maintained for transaction data i.e. whatever data gets inserted into the Interface table, the same data is pushed into the EBS product tables based on User language set in the calling session. So AIA layer just need to insert data into the Interface table, and then before calling the Concurrent Program or any post-processing API, FND APPS context need to be set.