Skip to Content
author's profile photo Former Member
Former Member

Key Expansion Atom - missing BIUMETA

Hi all,

i use B1iSN9 with Business one 9.1 (SQL Server) and trying to understand how to use B1isnke atom.

I've followed the documentation instruction but i can not get it to work properly because i always get back a message as "missing BIUMETA document" into the atom payload.

This is what I have done:

  • Goal: i want to enrich my message with some data from the receiver system before handing it to the outbound phase
  • In my processing phase i:
    • Create the KE atom
    • Setup my processing phase into the receiver context (having the "R" letter insted of the "S" one in the scenario flow)
    • Create the BIUMETA (KE definition document) from the KE atom (SBO 9.0 to SBO 9.0)
    • Create the "XSL for JDBC call" (KERequest.JDBC.01.xsl) document from the KE atom
    • Setup the KE receiver side specifing:
      • KE Type: xsl.jdbc
      • System proposed me "KE01" as Object Id
      • I set up my "XLS for JDBC" (KERequest.JDBC.01.xsl) document as XSL Document
    • Into the "Key" form i specify an xPath to get from the Sender Message (payload "S") my "research key" the the framework linked to "Key01"
    • Into the "KERequest.JDBC.01.xsl" document i type the query I want to run against the receiver system to get the desired data. In the where condition i specify the "Key01" key to obtain the value
    • Into the "atom0" i specify the xPath to the KE atom to get my value
  • When i run the flow it get processed succesfully but i do not get any data from the KE atom payload that sais "missing BIUMETA" document

What am I doing wrong?

Is there some other configuration i missed from the documentation?

I really can't figure it out until now.

Thank you

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Best Answer
    Posted on Jul 07, 2016 at 02:47 PM

    Hi Stefano,

    My recommendation if you have a simple sql statement for sender or receiver system, just use the sql call atom.

    The key expansion atom is a relic to support a kind of backwards compatibility for B1iSN8.8.

    With the actual framework versions including B1iSN9.0, it still makes sense to use it for nested key expansions actions but not really for simple requests.

    Having this said and you still want to use the key expansion atom, please make sure you've created a BIUMETA for the system type combination as defined in the SLD of your receiver ID and your sender ID.

    • Is your sender system and your receiver system from type B1 9.0 in the SLD?

    You could add some additional BIUMETAs pointing to the same KERequest.JDBC.01.xsl by creating a new "KE Definition Document" (e.g. generic BIUMETA.B1_B1.xml or explicit BIUMETA.B1.9.0_B1.9.0.xml or BIUMETA.B1.8.8_B1.8.8.xml depending on your concrete sender/receiver type combination).

    To apply the key expansion in the test environment, you need to select a concrete sender and receiver system or a test message having these information.

    Best regards

    Bastian

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.