SAP HANA Articles - Page 55 of 58

You are correct. NET Connector 2.0 uses proxy classes however .NET Connector 3.0 uses generic API. You need to rewrite all code that include NCo interaction..NET Connector 3.0 has many benefits over .NET 2.0:NCo 3.0 Is more stable, robust and supports heavy load.NET 3.0 provides better design of your application by decoupling the connection handling.It consumes less memoryAllows dynamic programming without the need for proxy generationCan dynamically look up metadata (so if something changes in the related ABAP system – e.g. if parameters in a function module signatures are added or the ABAP system is switched from Non-Unicode to Unicode, ... Read More

As per my knowledge, Oracle Bus Service has a SAP adapter that you can use to get data via queries. With 10.3.1 release of the Oracle Service Bus, you have the following adapters for use within Oracle Service Bus:Oracle AQDatabaseOracle ApplicationsSAPJ.D. Ewards OneWorldSiebelPeopleSoftYou can refer to this link to know more about Oracle Service Bus (OSB):Oracle Service BusYou can use API available with Weblogic and ESB for configuration and for creating end points. To see the list of API’s available for Oracle ESB, refer this link:API's for Oracle ESB

You can perform varchar casting using following query:SELECT TO_ALPHANUM(col) FROM ......

In Business Objects 4.1, this can be done by following below steps in Universe:Navigate to Parameters and LOVNext is to go Edit SQL option -> write query with order by to get the order.

Note that IN statement in SQL doesn’t accept a wild character. You have to use OR/AND to make it work as mentioned below:select * from Test1 t INNER JOIN Test2 s ON t.ID = s.RID where t.sdate >= ?1 AND t.edate

Note that when you perform an insertion using an ABAP program, there is no check on foreign key constraint.  Even when you define checks in data dictionary SE11 still there is no check at database level.When you execute using an ABAP code, this checks consistency at application level and not at database level. Errors you see in SE16 shows record rejected at application level.You need to perform validation by checking record from master table with foreign key of child table and incase sy-subrc is not initial then record shouldn’t be inserted to the child table and shows an error message.Read More

As per my knowledge, SAP PI Messaging Server 7.4 AEX is compatible with JMS 1.02 and JMS 1.1. Using Java Messaging Service, you can connect messaging systems to the Integration Engine.You can refer to SAP Note: 856346 - J2EE JMS AdapterThis note says common FAQ’s about JMS and I have JMS message properties that are of significant. How do I get this data into XI? How do I get this data out of XI?A feature generically referred to as XI adapter-specific message properties was introduced in the adapter framework. This allowed additional adapter information to be attached to a XI ... Read More

BELNR is not required however it is useful. Let us say a customer place an order and as he is not sure he place the order again. Now there are 2 orders you are not sure if there are two IDocs for same order.With BELNR, it has order number of customer system and you can add an optional field with Order Number and incase same order is used it can raise a warning message. You can also use session id to check for duplicate posting if you don’t want to use this.

Note that you can’t access Pooled tables directly and it should be accessed via Application server. When a pooled table is created, it involves creation of a suitable transparent table with a suitable delivery class and then it is changed to a pooled table.A pooled table can be flagged as transparent in its technical settings, which is a simple way of transforming it to a transparent table.To fetch information from Pooled tables, you need to write an ABAP code that can extract the data as per requirement.

As per my understanding, CUID is a 35 characters and normally starts with A, B, C, F, K and M. To know formatting of different ID types, you can refer to this:SAP Note: 1285103: What are the different types of IDs used in the BusinessObjects Enterprise repository?CUID: CUIDs are Globally Unique Identifiers that uniquely identify an InfoObject, both within a single CMS cluster and across multiple CMS clusters. Because CUIDs are strings they are less efficient to use and slower to query for. Unlike an object’s ID, an object’s CUID stays the same when it is migrated to a new ... Read More