se80, Author at SAP Help, Training and Education

All posts by se80

ABAP SUBMIT to execute second SAP report

Below is example code snippet to use the ABAP SUBMIT statement within your SAP report programs so that you can execute a second report with the required values. And control whether the process flow then

Populate SAP table t-code

There are two basic ways you can add data to a database table within your SAP system. The first method is to do it manually via transactions such as SM30, SE16, SE80 etc. The second method is to use ABAP

ABAP to populate SAP table

As discussed in the previous post there are two basic ways you can add data to an SAP database table, manually using standard SAP transactions or via ABAP code. In that post, we have already discussed

RFC_LOGIN_INFO Function module

RFC_LOGIN_INFO is a standard SAP function module available within R/3 SAPsystems depending on your version and release level. Below is the pattern details for this FM showing its interface including any

SAP table field attributes

Short Description Description of field Position of field in table This defines the position of field within the definition of the SAP table Keyfield: This identifies a field as being a key field

SAP Domain attributes

Domain name Name of domain A domain describes the technical attributes of a field, such as the data type or the number of positions in a field. The domain can define a value range describing the valid

SAP Data Element attributes

See below for a list of sap data element attributes, description and what each one is used for Data Element name Name of SAP data Element(semantic domain) A data element is an elementary type. It describes

SAP Report Documentation

It is a simple process to retrieve the SAP Report documentation available within your SAP system and can be done via SAP transactions SE80 or SE38Step 1 - Execute transaction SE38 First

SAP message 010 ICF_SYSTEM_LOGIN – log on again

Messsage Text for 010(ICF_SYSTEM_LOGIN) Client, name, or password is not correct; log on again CAUSE This message is self-explanatory and is quite simply caused when you enter the wrong user

SAP Message class within ABAP reports

As you may already know using the ABAP “MESSAGE” statement allows you to display various types of message to the user, to let them know if processes have been successful or not and what

« Previous 1 … 3 4 5 6 7 … 15 Next »