Joachim Rees @Joachim_Rees@mastodon.technology

Hey @naii ,

kürzlich war in "Die Höhle der Löwen" die App "Music Traveler".

-> Das hat mich (vom Konzept her) sofort an dein #studiolist-Projekt erinnert!

I sometimes think about (not) providing links.
On one hand, it might be considered nice, if I talk about something to also provide a link to it.

On the other hand, no-link toots are also very nice, as it is a "just read it, and you're done"- experience -> no urge to also click the link, open a new tab, get distracted.

Also, no-link toots have a certain quality towards me not trying to 'sell' you something.

If afterwards "things don't work", how could I tell wehter my refactoring broke it, or it wasn't working all along?!

I know #automatedTest (#unitTests and other) would help, but we don't have those.... 😞

3/3

5. Now it gets hard:

For each "program"/"addOn" (= a functional unit of custom coding - may contain one or more findings (=Code-Problems)):

- get a full understanding of what this program does. Verify that it "is working". (Functional Consultants have to help with that).
--> I can't go ahead changing code without that, can I?!

2/3

Very high level:

- I'm tasked with improving our #SAP #ABAP-Codebase.
- ATC / HANA-readiness (/s4-readiness) should be used to identify problems/todos

Tasks:

1. Find/define the right ATC-Checks (others in the company are working on defining company-wide check-definitions; they are not done yet)

2. Run checks on all custom code

-> get a list of problems

-> maybe prioritize.

1/?

*kopfrauch*

...jetzt hab ich mich selbst verwirrt: ich hab vorhin "Datum des letztes Zugriffs " als Lese-Zugriff interpretiert? ist das so?

Was ich will, ist: Dateien, die in den letzten N Tagen "Erstellt oder Geändert" wurden. bzw. die Ausschließen, für die das nicht der Fall ist.

..ich merke grade, dass ich in meiner #Backup-Strategie mit #Robocopy (unter #Windows) etwas anderes mache, als ich dachte:

Ich verwende /MAXLAD , hatte aber immer das Verhalten von /MAXAGE im Kopf...
(Wunderte mich eben, warum da so alten Daten in den Backups landen.... )

/MAXLAD:n :: Maximales Datum des letztes Zugriffs - schließt Dateien aus, die seit n nicht verwendet wurden.

/MAXAGE:n :: Maximales Dateialter - schließt Dateien aus, die älter als n Tage/Datum sind.

It would make for a clear cut, not carrying old stuff over.
Inspired by a piece of coding that shouldn't have been there ("I'll quickly try that it here!"), which didn't cause any problem for ~2 Upgrades, but the in the 3rd it did! (no big deal, but still...).

So every year we would get rid of the burden of old, unwanted coding and also of old, unwanted data (e.g. pre-€-Documents), eliminating them as a source of trouble.

Anyone doing this already?

2/2

#Thinking:

We're doing #SAP software development. (Putt very simple: a bunch of #ABAP-Code, called "AddOns".)

Every year, with the new S/4HANA release, we upgrade our Dev-System.
Then we test if everything still works.

Recently I was wondering:

Instead of an upgrade, we could
1. do a new installation of the latest release
2. Bring out AddOns to that
3. Create test master data (e.g. via #eCatt).
4. do our tests.
5. throw away the old system.

1/2

Nice service by #guerrillamail: Disposable Temporary E-Mail Address

https://www.guerrillamail.com/

#SAPNote 2835193 is found when searching for ISCMMDTYRISKOBJITMTP :

https://launchpad.support.sap.com/#/notes/2835193

It seems relevant(IS-OIL 804 - I didn't know, but that's part of a S/4HANA 1909 !) and up to date (Version 1 from 21.11.2019 )

...but I'm note sure if that will help, it seems to only change some coding in CL_CMMOI_NOMINATION_INTEGRATE ....

#SAPUpgrade1909 brings us
structure (SE11) ISCMMDTYRISKOBJITMTP , which is 'Partly active' and cant be activated because
"Too many nested INCLUDEs".

Phase: ACT_UPG
DDIC ACTIVATION ERRORS
1EEAD226 Too many nested INCLUDEs
1EEDO519 "Table" "ISCMMDTYRISKOBJITMTP" could not be activated

(It doesn't seem to hurt us (#IS_OIL something...) , as our test ran fine so far, but still it's not pretty....

#SAPupgrade

It's upgrade-time!

We're going S/4HANA 1909 (from 1809).

I'll use #SAPUpgrade1909 to tag funny (or not) things we'll encounter on that way.
(Like last year's looing dictionary types: https://mastodon.technology/@Joachim_Rees/101737928140488210 )

#SAP #S4HANA #Upgrade

#SapKnowHow

#LearnedSomething:

While #embeddedEWM (in S/4HANA) will keep using the #qRFC-interface, the standalone version of #EWM is now connected via #IDOC.

#S4HANA #SAP

Oh, it's #RandomDaySurprise at #SAPCommunity!
(-> log in today and interact once (e.g. like something) I think, to get the badge! )

https://answers.sap.com/articles/12927853/yay-random-day-surprise-10-dec-2019.html

Hey @fakefred , I just discovered your comics and I like them! Thanks for drawing and sharing!

Being called crazy (in a very friendly and positive way!) in #SapCommunity by @mmcisme 😉

Just because I tried (and succeeded) in writing a blog post (+ a comment) solely with the keyboard! #nomouse #keyboardOnly

https://blogs.sap.com/2019/10/17/adt-and-other-editors-more-general-keyboard-navigation/comment-page-1/#comment-477278