Automate

 View Only

  • 1.  XD02 script not recognizing address related changes from CUSTOMER ONE to Customer One

    Posted 18 hours ago

    Hello Community,

    We are moving forward with the idea of a hard change from using all uppercase to mixed casing for our Name and Address related fields. What I am experiencing with my original mass XD02 script is that changing from CUSTOMER ONE to Customer One or YOUR CITY to Your City is not counting as a change in SAP. My expectation is that this is a behavior limitation related to BDC scripting, as opposed to anything I am doing wrong? Is there another way to script this to make it accept the change?

    My suggestion for moving forward was to make two entries into the system, but this seems massively clunky and I hope there is a better idea out there!

    Customer # - Name 1 - City
    Row 1: 123- Customer One mc - Your City mc
    Row 2: 123 - Customer One - Your City



    ------------------------------
    Jeremy Maxfield
    Chamberlain Group, LLC
    ------------------------------


  • 2.  RE: XD02 script not recognizing address related changes from CUSTOMER ONE to Customer One

    Posted 8 hours ago

    hi Jeremy,

    When I make a change of those fields in tcode BP, i do see the change in the change log in transaction BP.

    I don't know if storing changes like this, can be customize in SAP. I think it is standard behavior.

    Not sure where you look for your changed data. Looking in for example table KNA1, you have to be aware (could be you already are) that for example the field Name1 is stored in 2 different fields: NAME1 (showing what is there) and MCOD1 (which is by default made uppercase). 

    In table ADRC, something similar happens; filed NAME1 vs field MC_NAME1



    ------------------------------
    Ed Meiners
    Wessanen Nederland Holding BV
    ------------------------------



  • 3.  RE: XD02 script not recognizing address related changes from CUSTOMER ONE to Customer One

    Posted 2 hours ago

    Hi Ed,

    Thank you for the reply and insight as to how S4 Hana would be working in this scenario. Unfortunately, we are still on ECC, which is why I am using XD02.

    The XD02 script returns a result of "No message returned from SAP" in the log field.

    additionally, in XD02, there is no evidence of change inside Environment-->Account Changes

    Jeremy



    ------------------------------
    Jeremy Maxfield
    Chamberlain Group, LLC
    ------------------------------

    Original Message


  • 4.  RE: XD02 script not recognizing address related changes from CUSTOMER ONE to Customer One

    Posted an hour ago

    Hi Jeremy in case it helps I've experienced this before and a workaround was to make an insignificant change such as add a full stop (.) to an unused field as then recognises a change with the view to then mass remove it after your required update is done.



    ------------------------------
    Kelly Nicholson
    Yara International ASA
    ------------------------------

    Original Message


  • 5.  RE: XD02 script not recognizing address related changes from CUSTOMER ONE to Customer One

    Posted an hour ago

    Hi Kelly,

    Yes, that is part of the plan, but the concern is if our middleware software that picks up changes in the SAP master and carries them to Salesforce will catch both - we do not want it to. We are currently investigating when/what is the trigger point to create the idoc for middleware.

    So if we do push forward, I will do first record insignificant update, second record mixed casing update, but I was hopeful that someone in the community was successful in another way that did not present the possible risk of introducing a large volume of "fake" changes to Salesforce.



    ------------------------------
    Jeremy Maxfield
    Chamberlain Group, LLC
    ------------------------------

    Original Message