ABAP Tutorials, Guides, Training, Manuals
SAP allows to modify its Keywords/Field names using the Customer Modification Transaction(CMOD).
To adjust/change any keyword or DDIC field name, navigate to CMOD and browse to the option Goto->Text Enhacements->Keywords->Change.
Many times we have seen many threads related to performance issues on BSEG table. It takes quite a lot of time when fetching data directly from BSEG if we do not have proper key fields. Here is the solution for this.
Since it is not possible to create the secondary INDEX for cluster tables, SAP came up with new concept called INDEX tables.
Many a times there are business scenarios wherein there is a possibility of migration to a new entity, for example if your organization decides to go for the implementation of a standard chart of account for the existing company codes, new company codes might be created. In such cases when the company code changes we also have to ensure that in all the Report variants the new company code needs to be updated. In case the report numbers cross hundreds it would be a painstaking process to change each and every variant. (Same case for background jobs too)
Example Scenario
Now? There was a business change and company code IN01 would no longer be used and will be replaced with IN02. The ABAP and BASIS teams are entrusted with the responsibility of creating new variants/change the existing variants.
There have been some cases where we, as an ABAP programmer, want to take SAP table data backup. Specially for the case where Basis Team refuses to get it back-up and restore the data for us.
There have been some codes available on net where data is backed-up but not restored back to SAP.
It is basically Dynamic table export / import facility.
When handling the objects which are Client dependent like SAPScripts, we need to transport (say from test to development or quality or production on same R/3 System but different Clients) them from one client to another as per requirement.
For the same purpose, we can use SCC1 Tcode. SCC1 T-Code u can do the transport in same R/3 System but different client like
Source : 100(DEV)
Target-1 : 200 (QAS)
Target-2: 300 (PRD)
SCC1 Just specify Source Client and the Request number and import the request.
In this process u don’t have to release the transport request.
