Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

What about NLS data in extended scenarios like Analysis Process Designer (APD), look up against NLS data during transformation, and availability for InfoSet Queries?

April 26, 2017analysis apd Data Designer extended look nls process scenarios Transformation

0

Posted

What about NLS data in extended scenarios like Analysis Process Designer (APD), look up against NLS data during transformation, and availability for InfoSet Queries?

1 Answer

0

Posted

Queries and InfoProviders are allowed in the APD. Currently, the query node in the APD works using the RSCRM BAPI. A new query access in the APD is in development. The adjointed parts from NLS partitioned InfoProviders have to be addressed separately. The adjointed part of an InfoProvider has to be addressed using the naming convention, $N. Concerning lookup scenarios against NLS data, the current situation is as follows: At the moment, there is no API available for unified access to archived and non-archived data of an InfoProvider (InfoCube or DataStore Object). There is only an API available to access the nearline part of an InfoProvider, which can be used for lookups in ABAP routines inside BW (in update rules and APD) against BW and NLS data. In case of InfoSet queries, the system works based on a different access logic that does not work using the BI Data Manager. For each InfoSet query, the system generates an individual data base access without any knowledge a