Automate

 View Only
  • 1.  Padding issue in Studio Query

    Posted 09-16-2022 02:04
      |   view attached
    In order to get Batch Search Strategy data out of SAP (S4) I had a query in ECC in which amongst others a join is made between
    table KONDH field CUOBJ_CH and table AUSP field OBJEK.
    In ECC field OBJEK was Type/Length String50 and this join worked. Now in S4 this field OBJEK is String90 and isn't working any more.
    I think it is because of this change. From KONDH-CUOBJ_CH the data I get is without preceding zeroes.

    Luckely i had an old query (made in ECC) in which this same connection existed and rebuild that to what i needed.

    My question however is, how can I influence padding during a join?
    Any ideas?

    ------------------------------
    Ed Meiners | Team leader Business Applications – Master Data Integration Management
    Royal Wessanen nv | +31 (0)20 3123353
    ------------------------------


  • 2.  RE: Padding issue in Studio Query

    Employee
    Posted 09-26-2022 11:07
    Hi Ed, 
    I hope I understood your concern correctly.  I would suggest 2 things: 
    1. Since the data types are different, please recreate the query for S/4ystem. 
    2. I dont think the join is the issue. it worked for string50 , I think it should also work for string90.
    In Evolve, there are some app level settings that influence what developers are allowed to do. I would check to make sure that you are setup at the right developer proficiency for your user, and check these settings under Admin-> App-> Configuration->Preferences. 

    PADDING: If it is greyed out in Query, please ask your App Admin to turn it on. 

    JOIN: Turn on the ability to join between mismatched fields. 


    ------------------------------
    Jayasri Varyani | SE
    Winshuttle North America |
    ------------------------------



  • 3.  RE: Padding issue in Studio Query

    Posted 09-28-2022 11:51
    hello Jayasri,
    These settings i already have.

    As I wrote, the problem starts when I recreate it on S4. I guess the field definition is different and therefore it
    doesn't work.  From KONDH-CUOBJ_CH i get a number like "1133892".
    If i put this number 1:1 (via for example SE16N) in AUSP-OBJEK it is not found. If i put "*1133892" it is found and returns as "000000000001133892"

    Hence, preceding zeroes are to be "added" in the join from table A to B.
    And i don't know how to do that.

    The padding setting is only related to data that is extracted (getting into the spreadsheet), not during the execution of the joins.

    I Do understand that this is not something that Winshuttle easily could fix, was just hoping for some tips/tricks.

    ------------------------------
    Ed Meiners | Team leader Business Applications – Master Data Integration Management
    Royal Wessanen nv | +31 (0)20 3123353
    ------------------------------