ABAP Tutorials, Guides, Training, Manuals
The following code helps in uploading the data from flat file on Application Server to ABAP Internal Table.
The following flow diagram shows the generic Process Flow, T-Codes and the SAP Tables involve in the SD domain.
It is not a comprehensive/detailed diagram but an overview to the SD process flow and the relevant objects, making it a good reference for SD/ABAP beginners.
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.
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.
The following documents give an overview of the steps that can be taken during Workflow definition as well as guidelines for the improved performance during Worflow run-time execution.
