Info regarding a system function

Hi all,
Can any one explain me what the system function 'C_RSTS_WRITE' does if it is called like this in the program
call 'C_RSTS_WRITE'
     ID 'HANDLE' field field1
     ID 'BUFF' field field2
     ID 'RC' field field3
     ID 'ERRMSG' field field4.
Regards,
Asha

CALL - Call a System Function
Note
This statement is for internal use only.
Incompatible changes or further developments may occur at any time without warning or notice.
Basic form 8
CALL cfunc.
Addition:
... ID id1 FIELD f1 ... ID idn FIELD fn
Effect
Calls the system function cfunc. The relevant function must exist in the file sapactab.h. If you change or recreate a function, you have to compile and link the SAP kernel again. For this, you need the C source code files.
Normally, external programs should be called by RFC with CALL FUNCTION ... DESTINATION.
Addition
... ID id1 FIELD f1 ... ID idn FIELD fn
Effect
Passes fields to the called program by reference. With "ID id1", you specify the name of a formal parameter, and with "FIELD f1" the relevant field from the ABAP/4 program. If a formal parameter expects an internal table, the latter is passed in the form "FIELD tab[]".
Example
DATA RESULT(8).
CALL 'MULTIPLY' ID 'P1' FIELD '9999'
ID 'P2' FIELD '9999'
ID 'RES' FIELD RESULT.
Note
With some critical C functions, the system automatically performs an authorization check. If the user does not have the appropriate authorization, a runtime error occurs. You can check the authorization with the function module AUTHORITY_CHECK_C_FUNCTION.
Note
Runtime errors:
CALL_C_FUNCTION_NOT_FOUND: Specified system function unknown.
CALL_C_FUNCTION_NO_AUTHORITY: No authorization to call this C function.
CALL_SYSTEM-DISABLED: The system function SYSTEM is disabled (with CALL 'SYSTEM').

Similar Messages

Info regarding Target System in clonning Process

Hi all
In the docs in metalink regarding the clonning process, i have enconterd the "Target System".
"Target System", means only the OS of the same platform, or another installation of EBS in the destination machine.
So if i run pre clone steps in the source, i have to copy the EBS folders in the destination machine that has the same OS platform, or that has an EBS installation in which i want to create the source's clone?
Thanks in advance, Soni

"Target System", means only the OS of the same platform, or another installation of EBS in the destination machine.It means the target node (with an OS which is binary compatible with the source node).
So if i run pre clone steps in the source, i have to copy the EBS folders in the destination machine that has the same OS platform, or that has an EBS installation in which i want to create the source's clone?You have to "copy the EBS folders in the destination machine that has the same OS platform". You do not have to install Oracle Apps on the target node, copying the files from the source node should be enough.

Regarding logical system function module....

hi all,
i migrated one interface program from 4.7 to ecc...both are seperate servers.....its working fine in 4.7 system...when it came to ECC.there s no errors...but in testing they found tat some system id is missing like tat...in RFC they called one FM OWN_LOGICAL_SYSTEM_GET........please guided me in this....

Ok sai. This interface is working in 4.7 why because it has the logical system name has been created and assigned to the client there. So, what you will do is take the logical system name given in 4.7. You can do that by going in to SALE tcode...under Basic Settings>Logical Systems>Assign Logical Systems
Here select the client name, and click on the button next to "change/display", that is the Details button. Here you can see the logical system name. Note that.
Now, in ECC 6.0, go into SALE tcode and then follow the same path...But instead of assign logical systems,select define logical systems. Now, click on New Entries button and then give the name you have in 4.7 and then give the same name in 6.0...and give a description. Save it..
Come Back,, now click on assign logical systems and then move into change mode....then select the client u logged in with and then click on details tab and here change the logical system name. Give the logical system name you just defined. Save it...and come out.
Now, try executing the Interface you migrated. And revert back with the error if there is any.
Vishwa.

System function call 'TPD_CONTRL'

HI All,
What is the work of System function call 'TPD_CONTRL'. Please suggest me how to get the all the informaion regarding any system function?
Can they dubuged also?
Regards,
Anj jain

There were several discussions before like the one SAP R/3 : System Functions.
Please check...

Regarding the Remote Function Module

hi,
Can any body can provide the brief information regarding the Remote Function Module.
1)How to create the remote function module
2)how it differ from the normal function module
3)any special features about this.
Thanks in advance

Hi
RFC (Remote Function Call) is similar to the general SAP fun module: except that in the attributes you click the radio button: RFC enabled;
and you will be passing an Import parameter DESTINATION to it.
Other code and usage will be similar to any fun module;
Have a look at any fun module in SE37 to understand better about the different components of Fun modules;
Refer this link:
http://help.sap.com/saphelp_nw04/helpdata/en/22/042518488911d189490000e829fbbd/frameset.htm
check out the following link it might help you
http://help.sap.com/printdocu/core/Print46c/de/data/pdf/BCFESDE2/BCFESDE2.pdf
Function Modules;
Check this matter.
Function Modules are Global ABAP programs created by SAP for reusable purpose.they have IMPORT,EXPORT and TABLE parameters, and EXCEPTIONS to through when error occurs.
You can create them from TCode SE37.
Go through the following doc:
Function modules are cross-program, reusable procedures that are organized into function groups, and whose functions are implemented between the statements FUNCTION and ENDFUNCTION. Function modules and their interfaces are created in the Function Builder.
Function Module Interfaces
The parameter interface of a function module is defined in the Function Builder. It includes the definition of interface parameters and the specification of exceptions that can be triggered by a function module. The Function Builder automatically generates comment lines below the FUNCTION statement in the source code of the function module, which represent the interface of the function module with the following syntax:
Syntax
... [IMPORTING parameters]
[EXPORTING parameters]
[CHANGING parameters]
[TABLES table_parameters]
[{RAISING|EXCEPTIONS} exc1 exc2 ...]
The syntax and semantics of IMPORTING, EXPORTING, CHANGING, RAISING, and EXCEPTIONS mainly correspond to the definition of method interfaces with [CLASS-]METHODS. The additional option of defining table parameters using TABLES is obsolete.
Interface parameters
The interface parameters are defined on the relevant tab pages in the Function Builder.
IMPORTING parameters are input parameters. When the function module is called, a suitable actual parameter must be specified for every non-optional input parameter. The content of the actual parameter is passed to the input parameter when the call is made. The content of an input parameter for which 'pass by reference' is defined cannot be changed in the function module.
EXPORTING parameters are output parameters. When the function module is called, a suitable actual parameter can be specified for every output parameter. The content of an output parameter that is defined for 'pass by value' is transferred to the actual parameter if the function module is completed without errors. An output parameter that is defined for pass by reference is not initialized when the function module is called.
CHANGING parameters are input and output parameters. When the function module is called, a suitable actual parameter must be specified for every non-optional input or output parameter. When the function module is called, the content of the actual parameter is passed to the input/output parameter, and when the function module is completed, the content of the input/output parameter is passed to the actual parameter.
TABLES parameters are table parameters. Table parameters are obsolete CHANGING parameters that are typed as standard tables with a header line. If an internal table without a header line or a table body is passed as an actual parameter to a formal parameter of this type, an empty local header line is generated in the function module. If an internal table with a header line is used as an actual parameter, both the table body and the header line are passed to the function module. Pass by value is not possible in formal parameters defined using TABLES. Formal parameters defined with TABLES can be replaced by formal parameters defined with CHANGING. A local work area can be created for the internal table in the function module by using the addition LIKE LINE OF itab of the DATA statement.
Exceptions
The exception of a function module are defined on the Exceptions tab page in the Function Builder. Here you can select exception classes to define whether class-based exceptions are declared or non-class-based exception are defined. Class-based exceptions are represented in the above syntax by RAISING, and non-class-based exceptions are represented by EXCEPTIONS.
The addition RAISING is used to declare class-based exceptions that can be propagated from the function module to the caller. Exceptions in the categories CX_STATIC_CHECK and CX_DYNAMIC_CHECK must be explicitly declared, otherwise a propagation can lead to an interface violation. A violation of the interface leads to the treatable exception CX_SY_NO_HANDLER. Exceptions of the category CX_NO_CHECK are implicitly always declared. The declaration of exceptions of the category CX_STATIC_CHECK is statically checked in the syntax check. For exceptions of the category CX_DYNAMIC_CHECK, the check is not performed until runtime. In a function module in which class-based exceptions are declared with the RAISING addition, the statement CATCH SYSTEM-EXCEPTIONS cannot be used. Instead, the relevant treatable exceptions should be handled in a TRY control structure.
The addition EXCEPTIONS is used to define a list of non-class-based exceptions that can be triggered in the function module using the statements RAISE or MESSAGE RAISING. Exceptions defined in this way - as with formal parameters - are bound to the function module and cannot be propagated. If an exception of this type is triggered in a function module, and no return value has been assigned to it with the homonymous addition EXCEPTIONS of the CALL FUNCTION statement when the call was made, this leads to a runtime error.
Note
For new developments after release 6.10, SAP recommends that you work with class-based exceptions that are independent of the function module.
RFC is a technology which is used to access a functions (Modules) from
the remote systems.
If a function module is set as remote enabled which can be access from
the remote system via RFC.Eg: U can access the Remote enabled function modules in ur VB,Webdynpro,Java,Visual composer program.
A function module can be set as remote enabled by SE37->Go to ur FM->click the option Button "remote enabled".
But Normal function modules can not accessd from the remote system.
Good Example for RFC enabled function module is : BAPI(Business Application Programming Interface)
Note: All BAPIs are Remote enabled but not all remote enabled function modules are BAPI.
CALLING A FUNCTION MODULE:
1)In U ABAP Editor --> Click "Patter" ---> Selection Option Button "Call Function"
--> Write the Corresponding FM name --> Hit Enter
2)The appropriate import ,export Parameters will be displayed in ur editor
3)Pass the Values Here.
Also check these links.
http://www.geocities.com/victorav15/sapr3/abapfun.html
Check this link:
http://help.sap.com/saphelp_erp2004/helpdata/en/9f/db988735c111d1829f0000e829fbfe/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/ef/d94b78ebf811d295b100a0c94260a5/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/41341147041806e10000000a1553f6/frameset.htm
Check this link:
http://help.sap.com/saphelp_erp2004/helpdata/en/9f/db988735c111d1829f0000e829fbfe/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/ef/d94b78ebf811d295b100a0c94260a5/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/41341147041806e10000000a1553f6/frameset.htm
See the following links:
http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/26/64f623fa8911d386e70000e82011b8/content.htm
Reward points for useful Answers
Regards
Anji

Call a System Function: CALL 'XXPASS'

Hi All,
I would like to know more about the System Function CALL 'XXPASS' and where does it resides in ABAP any transaction we can have a look into and understand the system functions. Please do suggest me ASAP.
Thank you.
Best Regards, Satya

Hi,
you can check the functions, acessing the kernel file sapactab.h.
best regards,
Pedro Rosa

What is a System Function / Kernel Routines

Hi All,
Can anyone let me know what is a "Sytem Function" or "Kernel Routines", Where can i check the code behind system function, Is the coding done in ABAP or C, Where can I get the list of all available system functions.
Regards,
Simin Raveendran.

These functions are routines that are implemented inside of the kernel code. They are usually implemented in C. Use Google to find a list of all system functions.

Tables used in the system function call

Hi expert,
I want to find out which are the tables used to extract data using system function call on SAP 3.1h system.
here is my specification.
I am using "AUTH_FIELD_GET_INFO" function module to get describtion of attribute
say for example
import parameter to this function module
Fieldname : VIEW
langu : E
and return parameters are DATEL,INTTYPE,LNG,RC,TEXT.
where in this function module there is system funcation call which return text for fieldname pass to this function
system function name:C_DD_READ_FIELD
can any one tell me which are tables used in the above system function.
Regards
John.

hi,
goto: system-utilities- debug system
A.
Message was edited by: Andreas Mann

Info regarding Diswarrior 4 and Leopard compatibility

I emailed Alsoft regarding Diskwarrior 4 and Leopard compatibility. Here is the response I got.
+DiskWarrior 4.0 will successfully rebuild a disk that has Mac OS X 10.5+
+Leopard installed or a disk that has been attached to a computer running+
Leopard.
+However, some operating system functionality has changed within Leopard+
+itself. As such, there are some compatibility issues when running an+
+installed copy of DiskWarrior 4.0 while started up from Mac OS X 10.5+
+Leopard. Alsoft currently recommends that you do not run DiskWarrior 4.0+
+while the computer is started from Mac OS X 10.5 Leopard.+
+Instead, to run DiskWarrior, you should start up the computer from either:+
+1) A DiskWarrior 4.0 CD.+
+2) Any disk that starts up in 10.4.x and then run DiskWarrior 4.0.+
+An updated version of DiskWarrior that has complete Leopard+
+compatibility will be released soon as a free download for existing+
+owners of DiskWarrior 4.0.+
+-- What you can expect when running DiskWarrior 4.0 under Mac OS X+
+10.4.x and rebuilding a Leopard disk.+
+All features work as expected with one exception: FileVaults created+
+while started from Leopard are not visible to DiskWarrior 4.0 and cannot+
+be rebuilt (repaired).+
+-- What you can expect when running DiskWarrior 4.0 under Mac OS X 10.5+
+and rebuilding a Leopard disk.+
+While not recommended (and discouraged), if you do run DiskWarrior 4.0+
+while started from Mac OS X 10.5 you might encounter some problems such as:+
+1) There is a lengthy delay whenever DiskWarrior is determining which+
+drives are currently attached. This delay is dependent upon the number+
+of attached drives and may last up to 2 or 3 minutes. You will+
+experience this delay when first starting DiskWarrior, whenever a disk+
+is attached or detached while DiskWarrior is running but idle, and+
+whenever a rebuild is completed or canceled.+
+2) You cannot rebuild FileVaults or disk images.+
+3) In step 9 (comparing directories) of a rebuild, the progress bar+
+might get to 100% even though the comparison step is not finished.+
+4) When performing Check All Files and Folders the progress bar might+
+get to 100% even though the check is not finished.+
+5) After rebuilding a disk, DiskWarrior may report that some files or+
+folders have had their permissions changed. This is inaccurate and the+
+permissions have not been changed.+
+To repeat, an updated version of DiskWarrior that has complete Leopard+
+compatibility will be released soon as a free download for existing+
+owners of DiskWarrior 4.0.+
+-- What about DiskWarrior 3?+
+DiskWarrior 3 and earlier versions are not compatible with Mac OS X 10.5+
+(Leopard). Alsoft does not recommend running DiskWarrior 3 or earlier on+
+a disk that has Mac OS X 10.5 Leopard installed or a disk that has been+
+attached to a computer running Leopard.+
+-- Marc+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Marc Moorash, Alsoft Technical Support+
+Email: [email protected]+
So, it seems it will work but you need to run it from the disk or if you have it installed on a external drive running Tiger, it will work.
Thom

If you open your Tiger Address Book, select all cards, drag them to the desktop, it will make one big "mega-VCF" card with a name like "Alan Adams and 543 others.vcf" Dump that to a flash drive or email it to yourself, then doubleclick on it on the Leopard machine. They will all import just fine into your Leopard Address Book.
Try doing something similar with your iCal data, Open the application, choose your calendars one at a time, and select File > Export. That should make a big "mega-ics" calendar card with a name like "work.ics" or "home.ics, i.e., "originalcalendarname.ics" with all the events of that calendar. Then same drill: dump that to a flash drive or email it to yourself, then doubleclick on it on the Leopard machine.
Both generation methods create text files, which should import just fine into the Leopard applications.

Regarding CUA System

hi guys,
we are planning to Connect CUA system with IDM and execute Initial load to collect users, roles, groups, assignment of roles to users, groups to users.....etc.
Now I believe IDM will have all the info including CUA system Users, Groups etc and Other child ABAP systems Users, Groups.
1) Later if we remove CUA from IDM and if Child systems directly connected with IDM(Executed Initial load), the Old CUA System Local users and Groups will be removed?
2)How the rules in CUA system can be transferred to IDM system.
(do we need to Create the CUA system rules again in IDM freshly again??)
regards
jaichan

thanks

Using system functions

Hello,
can we assign system functions like "PRINT" -> which will print the documents "SAVE"..etc. to push buttons in web dynpro applications?..
If that is possible please tell the documents regarding that.
Thanks
regards,
Deepti

Hi,
this is not possible.
Regards
Jochen

System Function Calls

Hi Everyone,
How to see all system functions in SAP ??..
For example:
CALL 'RSPOAOSD'
      ID 'ID'     FIELD IDENT
      ID 'TYPE'   FIELD TST05-DTYPE
      ID 'RECTYP' FIELD 'VYL----'
      ID 'RC'     FIELD RC
      ID 'ERRMSG' FIELD ERRMSG.
Here RSPOAOSD is a system function.I want to find the repository of all such System Functions in SAP.
Regards,
Rajeev.N

Hello Rajiv,
These are the System functions but i never try these functions.
ABAP_CALLSTACK
ABAP_CRC64
ABAP_PRECOMPILED_HEADER_USAGE
ABSTOR_TEST AB_CALL_LITL_CHECK AB_CALL_STACK_TRACE
AB_CREATE_SAPHFILE
AB_DELETE_ALL_MEM
AB_DELETE_ALL_SHARED
AB_DELETE_MEM AB_DELETE_SHARED
AB_FIELD_CHECKWRITEADDRESS
AB_FIELD_INFO
AB_FRAG_VIEW_TO_ITAB
AB_GET_CALLER AB_GET_COUNTRY
AB_GET_CX_DATA
AB_GET_CX_FOR_CUSTOMIZE
AB_GET_C_PARMS
AB_GET_DIRECTORY_DB
AB_GET_DIRECTORY_MEM
AB_GET_DIRECTORY_SHARED
AB_GET_GLOBAL_FIELDS
AB_GET_KEYS_MEM
AB_GET_KEYS_SHARED
AB_GET_NEXT_LEVEL_SHARED
AB_GET_TEXT_FROM_CLUSTER
AB_GET_VIEW_TO_ITAB AB_IMPORT_DECOMPRESS
AB_PRINT
AB_PROGTEXT
AB_P_A_CALC
AB_READTABLE_TRACE_GET AB_READTABLE_TRACE_ON
AB_READ_TEXTPOOL
AB_RFC_STATISTIC_TID
AB_RFC_X_SCRAMBLE_STRING
AB_RTM_DUMP
AB_RTM_LOAD_FILE
AB_SET_CODEPAGE_IN_CLUSTER
AB_SET_CX_DATA
AB_SET_C_PARMS
AB_SET_PRINT_PARAMS
AB_STRUC_INFO
AB_STR_GET_REFCOUNT
AB_TEST_CONV_EX
AB_TEST_KRN
AB_TEST_RPERF
AB_VALIDATE_STRREFS
AB_VALIDATE_TABREFS
AB_WORKINGSET
AB_WRITE_TEXTPOOL
ADD_ENTRY_TO_RTM
ALERTS
ANALYSE_USERBUFFER
APPC_HD
ARCHIVE_JOB_DONE
AS400_API
AS4_FREE_STOR
ASIAN_CHAR_WIDTH
ATRA_DECOMPRESS
ATRA_GET_CLOCK_INTERVAL
ATRA_GET_STATE
ATRA_INIT ATRA_INIT_DEFAULT
ATRA_SET_CLOCK
AUDIT_GET_INFO
AUDIT_SET_INFO
AUDIT_WRITE_ENTRY
AUTH_CHECK_TCODE
AUTH_CHECK_USER
AUTH_TRACE
AbGetXtypInfo
BDC_CLOSE_GROUP
BDC_DYNPRO BDC_OPEN_GROUP
BDC_RUNNING
BDC_START_GROUP
BDC_TCODE
BREAK_LINE
BTC_CALL_KERNEL
BUILD_DS_SPEC
BatchDebugging
CAL_BUFSIZE
CAL_CHECK_FOR_HOLIDAY
CAL_CONVERT_DATE_TO_FDATE CAL_CONVERT_FDATE_TO_DATE
CAL_EASTERDATE
CAL_LOAD_NEW
CAL_SYNC
CCMS_MONI_INFRA CCMS_MONI_SYST
CHECKSUM
CHECK_ACCESS_KEY
CHECK_DEVELOPER_KEY
CHECK_LOCALE
CHECK_REFERENCE
CHECK_SECRET_AUTHORITY
CHECK_TADIR_ACCESS_FREE
CHECK_TADIR_ACCESS_KEY
CLOCK CONT_LOC_TIM CONVERSION_EXIT_ALPHA_INPUT
CONVERSION_EXIT_ALPHA_OUTPUT
COV_GET_DATA
COV_INFO COV_MAINTAIN_TESTKEYS
CREATE_DYNAMIC_TYPE
CUADELETE
CUR_LCL C_CAL_GENERATE C_CAL_GET_TIMESTAMP
C_CHAR_CODE_CONV
C_CVT_HOST_TO_NEUT
C_CVT_NEUT_TO_HOST
C_DB_EXECUTE
C_DB_FUNCTION
C_DD_CHECK_VAL
C_DD_COUNT_VAL
C_DD_HEADER
C_DD_H_ADD_V
C_DD_H_DEL_V
C_DD_H_GET_V
C_DD_H_PUR_V
C_DD_H_PUT_V
C_DD_READ_FIELD
C_DIR_READ_FINISH
C_DIR_READ_NEXT C_DIR_READ_START
C_END_SPOOL_JOB
C_ENQUEUE
C_ENQ_WILDCARD
C_FILE_ATTRIBUTES
C_GETENV C_GET_BUFSIZE
C_GET_CPU_ID
C_GET_FILEPOS
C_GET_FILESET
C_GET_FLUSHLEVEL
C_GET_MOD_TIME
C_GET_PROCESS
C_GET_ROOT
C_GET_SWITCH
C_GET_SYSLOG_POS
C_GET_SYSTEM_NUMBER
C_GET_TABLE C_GET_TASK
C_GET_TIMEZONE
C_GET_TRNA
C_GET_USER
C_GUI_SUPPORT
C_GUI_VERSION
C_LOG_ROOT C_MAKE_TEXT_DELTA
C_MG_MCIDGEN
C_MG_MCIDREM
C_MG_MCOGEN
C_MG_MCOREM
C_MOD_TABLE
C_PRINT_LINE
C_PRINT_NORMAL_LINE
C_PRINT_OBJECT
C_PRINT_OTF
C_PRINT_PAGE_BREAK
C_REMOVE C_RSPO_ASK_FOR_PRIO
C_RSPO_CHECK_TAB_IN_DD
C_RSPO_LAST_ERROR
C_RSPO_PRINTJOB_STATE
C_RSPO_PROCESS_DIALOG
C_RSPO_SPOOL_MESSAGE
C_RSPO_TEST
C_RSTRB_READ_BUFFERED C_RSTRDURA_TO_P6_P6
C_RSTRTIME_TO_P6_P6
C_RSTS_CCC_STAT
C_RSTS_CHECK_TAB_IN_DD
C_RSTS_CLOSE C_RSTS_CREATE_OBJ_FOR_FILE
C_RSTS_INVALID_CCC
C_RSTS_LAST_ERROR
C_RSTS_OBJ_INFO
C_RSTS_OPEN_READ
C_RSTS_OPEN_WRITE
C_RSTS_READ
C_RSTS_REMOVE
C_RSTS_REPAIR_OBJ
C_RSTS_WRITE C_SAPGALLPARAM
C_SAPGDEFPARAM
C_SAPGPARAM
C_SET_FILESET
C_SET_MOD_TIME
C_SET_PROCESS C_SET_SWITCH
C_SET_TASK
C_SET_TRNA
C_SET_USER
C_SIZEOF
C_START_PRINT_JOB
C_START_SPOOL_JOB C_SWITCH_MCID
C_TO_HEX
C_TRADR
C_UINT_TO_P5
C_UPDATE_PRINT_JOB
C_UPDATE_SPOOL_JOB C_USE_FLOPPY
C_USHORT_TO_P5
C_WRITE_PRINT_CONTROL
C_WRITE_SYSLOG_ENTRY
CheckLogFile CleanZombieLog
CreateNewBIProt
DATE_CONV_EXT_TO_INT
DATE_CONV_INT_TO_EXT
DBCUADEL
DBG_DELETE_TAB_DATASET
DB_BMN_TEST
DB_CLUSTER_BUFFER_FLUSH
DB_CUA_RESET
DB_C_GET_EXPLAIN
DB_DUMMY
DB_EXPLAIN_PLAN
DB_GET_REL
DB_MAP_DDTYPE
DB_NTABSTA
DB_OBJ
DB_RD_NTABHDR
DB_RM_NTAB
DB_RSQLSTA
DB_SLCCSTA
DB_SYNC_DISPL
DB_SYNC_SWITCH
DB_SYNC_WRITE
DB_TBL_RESET
DB_TBP_RESET
DB_TBX
DB_WR_NTABHDR
DEBUG_CNTL
DELETE_PXA_OBJECT
DIAG_COMBOBOX_SET_SIGTABLE
DIAG_START_PM
DIAG_XMLBLOB_GET_SENDSTRING
DIAG_XMLBLOB_RECEIVE
DIAG_XMLBLOB_SEND
DIAG_XMLBLOB_STATUS
DYCUAGEN
DYNP_CONTAINER_POSITION
DYNP_DELETE_PROPERTY
DYNP_GET_DSTATE DYNP_GET_FIRSTDYNPROELEMENT
DYNP_GET_INFO
DYNP_GET_LPCN
DYNP_GET_NEXTDYNPROELEMENT DYNP_GET_PROPERTY
DYNP_GET_PROPERTYSUPPORT
DYNP_GET_STATUS
DYNP_GET_SUBSCREEN DYNP_INIT_LOCTIM
DYNP_OKCODE_GET
DYNP_OKCODE_SET
DYNP_SET_CURSOR
DYNP_SET_PROPERTY DYNP_SET_STATUS
DY_CHECK_TRANSACTION
DY_COMPOSITES_GET
DY_DOCKING_SIZE_NOTIFY DY_GET_COMBOBOX_FOR_HELP
DY_GET_CURRENT_TRANSACTION
DY_GET_DYNPRO_EVENT
DY_GET_DYNPRO_INFOS DY_GET_ELEMENTS_TO_TRANSLATE
DY_GET_EXT_VID
DY_GET_FIELD_VID
DY_GET_FOCUS DY_GET_FOCUS_CONTROL
DY_GET_LOCAL_PARAMETER
DY_GET_MODAL_LEVEL
DY_GET_PROPERTY_BAG_STRING
DY_GET_SET_FIELD_VALUE
DY_GET_S_MESSAGE
DY_GET_TC_LOOPSIZE
DY_GET_TX_VARIANT DY_INVISIBLE_SCREEN
DY_MODIFY_SCREEN_TX_VARIANT
DY_OBJ_DIFF
DY_OBJ_GET
DY_OBJ_GETALL DY_OBJ_SET
DY_RESET_COMPRESSION
DY_SET_DISPL_AGAIN
DY_SET_DYNPRO_VARIANT DY_SET_FIELD_ATTRIBUTES
DY_SET_FOCUS_CONTROL
DY_SET_PROPERTY_BAG_STRING
DY_SET_TX_VARIANT EG_MEM_MGT
EMPTY_C_CALL
EmInfo
EsMemMgt
ForceCloseJoblog
GET_ABAPTYPE
GET_ACCESS_INFO GET_ACCESS_KEY
GET_BPABLE_STATEMENTS
GET_CURRENT_MAINSCREEN
GET_DEFAULT_SYSTEM_DEBUGGER_TOOL
GET_DEVELOPER_KEY
GET_DYNP_FIELD_VALUE
GET_ENDOFPAGE_SIZE
GET_KEYWORDS
GET_LAST_RABAX GET_LOG_LINESIZE
GET_MESSAGES
GET_NEXT_PARAMETER
GET_NUM_OF_FSREGS
GET_PARAM_TCOD GET_PATTERN
GET_PREDEF_TYPES
GET_PXA_HASH
GET_RTM_TABLE
GET_SHLIB_VERSION GET_SOURCE_POSITION
GET_STORAGE_COSTS
GET_SWITCH_TXEND
GET_SWITCH_UTASK
GET_TADIR_ACCESS_KEY GET_WINDOW_DATA
GUESS_CODEPAGE
Get1NetData
Get1PerfData
GetNetData
GetPerfData GetRuntimeInfo
HELP_CHECK_FIELD
HELP_GET_FIELD
HELP_GET_FIELDLEN
HELP_GET_FIELDS
HELP_PUT_FIELD
HOLD_UPDATE_TASK_LOCAL
ICF_DISPATCH
ICT_DISPATCH
IMPORT_DYNPRO
IMPORT_PROCLOG
INTERNET_USER_LOGON
IPL_SYSTEM
IS_ABAP_DEBUGGER_ACTIVE
IS_DEBUGGING_POSSIBLE
IXARCHIV IXARCHIV_RECEIVE
IXARCHIV_SEND
IXML_DISPATCH
LCL_FOR_LANG
LISTMGR_CONTROL LOAD_PROGRAM_TO_PXA
LOGIN_FOR_SNC_SERVER
LOGIN_INFO
MOVE_NTABS
MULTI_LOGIN_ALLOWED
NEWCKSUM NLS_BIDI_CONVERT
NLS_BIDI_SAP_TO_MS
NTAB_RESET
O2_CONVERT
OBJMGR_CONTROL
OBJMGR_GET_INFO
OMRT_DISPATCH
OMS_DEVICE_QUERY
OMS_GENERIC
OMS_JOB_CANCEL
OMS_JOB_QUERY
OTF_LAYOUT_RTL OTR_SYNC_BUFFER
OVERWRITE_PXA
PASSWORD
PRINT_COVER_PAGE
PROVIDE_SORT_CHECKS_ENABLED
PR_CHECK PR_DECLIT
PR_RESOL
PXA_TEST
PfCall
QUERY_LIST_TO_MEMORY
QUEUE_CLOSE
QUEUE_DELETE
QUEUE_ERASE QUEUE_GET
QUEUE_OPEN
QUEUE_PUT
READ_ACCESS_KEY
REINIT_LANG_CP_LOC
RESET_PROGRAM_TIMESTAMP
RFCControl
RFCSystemInfo
RMCControl
ROUND_F_TO_15_DECS
RSCPF1
RSCPF4
RSCPICT
RSCP_CCC_STAT
RSCP_COBJ_CREATE
RSCP_COBJ_DESTROY
RSCP_COBJ_USE
RSCP_GENERIC
RSCP_ICONS RSCP_NAME_OF_CODEPAGE
RSCP_TCP0F
RSEC_AB_ACCESS
RSEC_AB_RCHECK
RSEC_GEN_PASSWD
RSEC_GEN_RAND RSPOA1DIR
RSPOA1JDIR
RSPOA1PDIR
RSPOA2DIR
RSPOA2JDIR
RSPOA2PDIR
RSPOA9DIR
RSPOA9JDIR RSPOA9PDIR
RSPOACSD
RSPOADP
RSPOAEPJ
RSPOAIP
RSPOAOSD
RSPOAPCC
RSPOARNS
RSPOARPAB
RSPOARSD RSPOAWSD
RSPOVERSION
RSPO_ABAP_DUMMY
RSPO_CACHE_CONTROL
RSTGTEST
RSTR_FUNC
RTM_GET_DATA RTM_INFO
RaiseEvent
ReadLogDirA
ReadLogPartitionA
Reentrance_Ticket
RemoveLogPartitionA RemoveOldBIProt
ReorgLogFile
RfcImport
RstrDateConv
SAPCORE
SAPTUNE
SAVEONERROR
SAVE_BREAKPOINTS
SC_SYMBSTRAT_INIT
SEL_PAR_UC_CONV_CHECK
SEMSTA SET_ACCESS_KEY SET_DEFAULT_DEBUGGER_TOOL
SET_DYNP_FIELD_VALUE
SET_EXPECTED_RABAX
SET_LIST_SIZE SET_LOG_LINESIZE
SET_MAX_RUDILOCKS
SET_P_A_TYPE
SET_SWAP_ALL
SET_SWITCH_TXEND SET_SWITCH_UTASK_OFF
SET_TRANS_VAR
SET_WINDOW_DATA
SHMINFO
SHM_MODELOCKREF_INFO SNC_ABAP_INFO
SNC_ABAP_SERVICE
SSF_ABAP_SERVICE
STORAGE
STORAGE_SET
SUSR_USER_BUFFER SYNTAX_TRACE
SYSTEM
SYST_LOGOFF
SelectionRectangle
SendSubmitReq
SetNetData
SetPerfData TABLEVIEW_GET_INFO
TABLEVIEW_UPDATE
TEST_LANG_CP_LOC
TOUCH_PXA_OBJECT
TOUCH_REPORT TPD_CNTRL_MISC
TPD_CONTROL
ThCPICCall
ThDisplay
ThGwMon
ThNoCall
ThNoGet
ThNoRead ThSndDelUser
ThSysInfo
ThTest
ThUsrInfo
ThVBCall
ThVersion
ThWpInfo
TrCall
TranslateSource TriggerBtcAction
UMG_CP_FOR_TEXT
UMG_WORD_SEP
UNSET_PARAMETER
VMIT_GET_MEASUREMENT_RESULTS VMIT_START_MEASUREMENT
WriteExtLog
WriteTrace
XRfcConverter
XTC_DISPATCH
XXPASS
XXPASSNET ab_SetVisibleCx

System function

Hi.
In the CONVERSION_EXIT_ALPHA_OUTPUT function module there is code:
CALL 'CONVERSION_EXIT_ALPHA_OUTPUT' ID 'INPUT' FIELD INPUT
ID 'OUTPUT' FIELD OUTPUT.
Can I anywhere look at code of system function or where can I find documentation to such system functions.

Hello Kartik,
Just to add to the info you provided. The CALL 'XXX' are Kernel level functions (which you say to be C functions) which should be used only by SAP only.
Better documentation in SAP-F1
BR,
Suhas
PS: We had a custom FM (some CRC key calculation) where we had used this "CALL" function. And believe me it was a pain when upgrading from 4.5(non UC) to ECC5.0

System Functions !!!!!Please help

Hi Experts,
I was copying a program from ECC sandbox to the SAP BW sandbox but the following piece of code does not work in the BW sandbox.
CALL 'SYSTEM' ID 'COMMAND' FIELD l_cmd
ID 'TAB' FIELD it_list-sys.
This was working in the R3 environment.
cant we execute system functions in the BW environment.If yes how?
and
Is it advisable to use system functions at all.
Regards
Ankit

With CALL 'SYSTEM' command, an ABAP prog. can easily execute operating sys. commands
on the application server.Externl command are maintained useing transaction SM69 and
executed using tran. SM59.
In ur case pl. check in ECC, what is command name ur storing in variable l_cmd.And in BW sys. check whether same command
is maintained in SM69 or not. If it is not maintained, then maintain it and populate it in
l_cmd before calling the sys. command.
Regards,
Joy.

Please send me some good links on System Function Calls

Hi,
I want to know more about System Function calls. Please send me some good links on the same.
Eg : CALL 'C_DIR_READ_NEXT'
 ID 'TYPE' FIELD file-type
 ID 'NAME' FIELD file-name
 ID 'LEN' FIELD file-len
 ID 'OWNER' FIELD file-owner
 ID 'MTIME' FIELD file-mtime
 ID 'MODE' FIELD file-mode
 ID 'ERRNO' FIELD file-errno
 ID 'ERRMSG' FIELD file-errmsg.
Rgds,
Raghavendra.

Hi,
CALL - Call a System Function:
Note
This statement is for internal use only.
It cannot be used in application programs.
As of Release 6.20, you should use Kernel Methods instead of system functions.
Syntax
CALL cfunc.
Addition:
... ID id1 FIELD f1 ... ID idn FIELD fn
Effect
Calls the system function cfunc. The relevant function must exist in the file sapactab.h. If you change or recreate a function, you have to compile and link the SAP kernel again. For this, you need the C source code files.
Normally, external programs should be called by RFC with CALL FUNCTION ... DESTINATION.
Addition
... ID id1 FIELD f1 ... ID idn FIELD fn
Effect
Passes fields to the called program by reference. With "ID id1", you specify the name of a formal parameter, and with "FIELD f1" the relevant field from the ABAP/4 program. If a formal parameter expects an internal table, the latter is passed in the form "FIELD tab[]".
Example
DATA RESULT(8).
CALL 'MULTIPLY' ID 'P1' FIELD '9999'
 ID 'P2' FIELD '9999'
 ID 'RES' FIELD RESULT.
Note
With some critical C functions, the system automatically performs an authorization check. If the user does not have the appropriate authorization, a runtime error occurs. You can check the authorization with the function module AUTHORITY_CHECK_C_FUNCTION.
Exceptions
Non-Catchable Exceptions
Cause: You do not have the authorization to call this C function.
Runtime Error: CALL_C_FUNCTION_NO_AUTHORITY
Cause: The system function specified is unknown.
Runtime Error: CALL_C_FUNCTION_NOT_FOUND
Cause: The system function SYSTEM is deactivated (in CALL 'SYSTEM')
Runtime Error: CALL_SYSTEM_DISABLED
Regards,
Bhaskar

Info regarding a system function

Similar Messages

Maybe you are looking for