look up

[Former Member]

Why lookup needed in XI?

Is there any other way??

[Former Member · Accepted solution]

Hi Gautam,

In XI look up's are of three types videlicet :

a)JDBC

b)SOAP

c)RFC

Lookups are used to request or call the data from mapping ,

The current process halts the it starts looking for data which was stored some where and get that data and comback to process and continue with that data.

Check this https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/8e7daa90-0201-0010-9499-cd347ffb...

explains how to perform look ups in XI

Should help u out

[Former Member]

HI Gautam,

I would like to add some more info to ur question.Lookups are really helpfull when u are dealing with B2B scenarios,where u need to do EDI mapping.When u are dealing with EDI mapping some times u require to query up the databases of the Parties to generate Proper ANSI(EDI) output based on the trading partner details.SEEBURGER BIC ADAPTER provides u that facilitie too.

Thanks,

Kopparaju.

[Former Member]

Look Up at its simplest is the process of taking a source data value, comparing that source value to a list of values on an external data source (normally a relational datastore), retrieving the corresponding target value, and applying that target value to the outgoing data stream to allow proper identification in the recipient system.

The reality is much more complex and critical. The majority of interfaces will require some form of cross reference (referred to forward as u2018Xrefu2019 for simplicity). Xrefs, from a performance perspective, are one of the largest time u2018consumersu2019 within the execution of an interface. Datastores need to be robust / available and kept up to date as soon as the related source / target identification values are changed in their respective systems. Neglecting any of these areas will at the minimum result in execution degredation, and at the worst case execution failure. As such, the Xref approach must be given careful consideration prior to any interface design / development with a focus on the following areas:

1. Maintains Performance : Maximizes performance from the establishment of the relational datastore connection to the Xref request execution to the retrieval / formatting of that data.

2. Robust : Guarantees transactional integrity, integrated error handling / restart / recovery.

3. Promotes Re-use : Integrates easily to existing developments and designed generically enough to address a large scope of Xref needs dynamically with minimal, if any , modification.

4. Simplifies Maintenance : Minimizes the number of u2018routinesu2019 to be maintained and promotes centralized / standard maintenance of those routines.

To accomplish these goals, the Xref discussion will be broken down into the following areas for better understanding:

u2022 Datastore Infrastructure : The underlying details of the Xref datastore itself, such as physical location, access method(s), maintenance, etc.

u2022 Decision Matrix for Cross Reference Approach: Given the characteristics of the Xref requirement (volumes, table size, etc.) a decision tree to determine the most efficient access method (single / direct, subset / consolidated, all / table cache, etc.).

u2022 Conceptual Implementation : High level description of alternatives available / chosen for datastore connectivity and Xref execution.

u2022 Technical Implementation : Technical details for the low-level implementation of the conceptual approach.

[former_member537867]

Hi Gautam,

With the Lookup API you can call remote application systems via adapters during the execution of a mapping program. You can use the Lookup API to read data from the application system or to execute an existing mapping on the application system. The call to the application system is synchronous. Lookups are possible via the central adapter engine. The Lookup API supports the RFC, JDBC, and SOAP adapter.

Lookups are used to identify / request the data from mapping , i mean interupting the process and looking for data which was stored in some where and get that data and comback to process and continueWe will use these type of lookups in Message mapping for refering DB Lookup for data base which is not SAP, RFC lookups for SAP data with that data.

Lookups are used to identify / request the data from mapping , i mean interupting the process and looking for data which was stored in some where and get that data and comback to process and continue with that data.

Lookup - /people/alessandro.guarneri/blog/2006/03/27/sap-xi-lookup-api-the-killer

DB lookup - /people/siva.maranani/blog/2005/08/23/lookup146s-in-xi-made-simpler

SOAP Lookup - /people/bhavesh.kantilal/blog/2006/11/20/webservice-calls-from-a-user-defined-function

http://help.sap.com/saphelp_nw04/helpdata/en/cf/406642ea59c753e10000000a1550b0

Lookup’s in XI made simpler - /people/siva.maranani/blog/2005/08/23/lookup146s-in-xi-made-simpler

How to check JDBC SQL Query Syntax and verify the query results inside a User Defined Function of the Lookup API -

http://help.sap.com/saphelp_nw04/helpdata/en/2e/96fd3f2d14e869e10000000a155106/content.htm

/people/prasad.illapani/blog/2006/10/25/how-to-check-jdbc-sql-query-syntax-and-verify-the-query-results-inside-a-user-defined-function-of-the-lookup-api

Lookups - /people/morten.wittrock/blog/2006/03/30/wrapping-your-mapping-lookup-api-code-in-easy-to-use-java-classes

Lookups - /people/alessandro.guarneri/blog/2006/03/27/sap-xi-lookup-api-the-killer

/people/siva.maranani/blog/2005/08/23/lookup146s-in-xi-made-simpler

http://help.sap.com/saphelp_nw04/helpdata/en/cf/406642ea59c753e10000000a1550b0/content.htm

/people/sap.user72/blog/2005/12/06/optimizing-lookups-in-xi

Lookups with XSLT - https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/8e7daa90-0201-0010-9499-cd347ffb...

/people/sravya.talanki2/blog

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/05a3d62e-0a01-0010-14bc-adc8efd4...

How we have to create the lookups?

Check this weblogs with some screenshots on how to achieve this:

/people/siva.maranani/blog/2005/08/23/lookup146s-in-xi-made-simpler

/people/sravya.talanki2/blog/2005/12/21/use-this-crazy-piece-for-any-rfc-mapping-lookups

/people/alessandro.guarneri/blog/2006/03/27/sap-xi-lookup-api-the-killer

/people/sap.user72/blog/2005/12/06/optimizing-lookups-in-xi

/people/morten.wittrock/blog/2006/03/30/wrapping-your-mapping-lookup-api-code-in-easy-to-use-java-classes

Regards,

Vinod.