At this client we encountered a very strange problem and i can't find the cause of it. So maybe someone can give me some pointers to look at.
We have a batchjob that consists of 7 jobsteps. Each step is run with its own variant.The batchjob termina...
Hello there...
Currently i'm trying to fix a syntax error in standard SAP BADI implementations of /POSDW/CONDITION, according to note 987226 https://launchpad.support.sap.com/services/pdf/notes/987226/E
Importing the support package as described ...
As a developer with over 20 years of experience, this is my very first blog on blogs.sap.com. But don't let that fool you: i have been a visitor of the old SCN forum, posted numerous times (not with this S-id but my old ones) and oh how i miss the o...
In table /POSDW/TLOGF a customer append exists. In this append structure fields have been inserted and deleted again. The table is active and has been adjusted accordingly through SE14. In SE11 everything looks ok.When we view the table on the HANA d...
System: SAP ERP 6.0 / EHP7 FOR SAP ERP 6.0SAP NETWEAVER 7.4HANA DB release 1.00.122.05.1481577062Software Component Version
Support
Package Patch LevelSAP KERNEL 7.45 64-BIT UNICODE
SP310 000310Currently i'm facing a peculiar problem. I hav...
I ran into the same error a few weeks back. In my case the error was a result of a changed characteristic. It used to be a characteristic with multiple allowed values. Someone changed it to only one single value allowed. And in the end table AUSP oft...
It would help if you showed your code for your AMPD. But without it my guess would be: pass an internal table that will hold your company codes and use that in your AMPD.
The Z-programs in step 1 and 2 don't trigger message DB 612 (at least not visibly programmed in the Z code)Step 1 Z program creates an inventory document: result is ok, so next to step 2Step 2 Z program creates WVINVE idocs; upon completion we have a...