Yes, We – developers – are end users in the context of transport management. We use variety of transactions on the surface, like ADT, SE80, SE09, STMS etc. to push our changes to test and production systems. We not developed that transactions, which manage changes variety of object types in the ABAP,BSP repository, DDIC etc, and their transport.
Transport requests, right ? Spending decades with Transport Organizer (SE09…) and import queues (STMS), standard extensions to prevent release with special magic logic. Pretty familiar for all of us. Companies with development guidelines, include variety of rules, what should be the proper description for a transport request. Hunting the right request based on the name. Using external tools to administer business requirements and map corresponding requests. Developers put references in the source code based on predefined rules.
Sometimes You have to recognize, that a where-used list for a given repository object, like constant interfac members, messages or data elements etc. are not working, but You are sure, there must some results. SAP has dedicated index tables for that cross-references, which might not be up to date for whatever reason. Upgrades or broken jobs, which are automatically scheduled after installation at certain events, like accessing the object navigator at first time. They are very time-consuming jobs.
Salvation after 5+ years and variety of technological marriages, ABAP RAP is here finally. Fiori and WebAPI development can take a deep breath. This post is about common and uncommon snippets for ABAP RAP. This post is updated on regular manner.
MIME repository is a nice and convenient way to store and provide built in documents for end users. It comes handy, when working with templates. User can download the up to date templates always. This is especially good, when users use excel documents, to load data into the system.
SAP worklfows can be hanging for numerous reasons. This article explains about detecting the failure of saving workflow container data to database, where the container conversion to the database format fails in the middle. This approach applicable to resolve root cause of dumps (happening in the SAP standard WF classes) of hanging workflows.