SAP R/3 : System Functions

Hi ,
I was just curios to know abt the Systems C functions available in SAP R/3. DO any one of you have any idea , plz share that in the forum.
I did heard from some one that filename is sapactab.h , but could not trace it ....
Thanks
Rajiv

These are the System 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

Similar Messages

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...

How to develope custom function modules in SAP R/3 system to maintain c...

How to develope custom function modules in SAP R/3 system to maintain cross
referencing tables for sales order number.

Hi Raja,
Steps to crate FM..
Follow these steps..
Go to the T: code SE37
First You Create Function Group
On That u specify
Function Group Name..............
Short Text..............................
save...
Go to SE 37
Specify the Function Module Name: Eg: Z_Bapi_Materialmaster
Short Text.......
Save...
Next Go to Attributes..
Select Radio button : Remote enabled model
Go to Parameters..
Click Import...
Give Parameter Type Associate type S.t
next Click Export...
Give Parameter Type Associate type S.t
Next Click Tables Button..
Specify tables..
Next click source code button..
Write Source code here..
Eg : Select statements Etc..
Finally we should be select the Radio button Enable remorely
https://www.sdn.sap.com/irj/sdn/wiki?path=/pages/viewpage.action?pageId=39728
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/abap/bapi%2bstep%2bby%2bstep
Hope this information is useful to you..
Reward points if it is usefulll....
Thanks ,
Satya Kumar..

What is the best approach to capture TBOM's for a SAP SRM system/functionality?

Hello SCN Community,
It would be much appreciated if somebody could share some information about the following....
What is the best approach to create TBOM's for a SAP SRM system? The SRM functionality is basically consisting out of multiple ABAP Web Dynpro's that are connected as a process via a SAP Portal (as is understand it). The entrypint to the SRM functionality is via the SAP Portal.
Do I first have to create a link to the Portal via an SAP Web Application link in SOLAR01 and then start recording? Will it record only the portal objects or also the ABAP Web Dynpro objects?
Do I have to list all the separate ABAP Web Dynpro's in SOLAR01 and use those as a starting point?
I am myself more familair with more classical SAP ABAP ECC systems and transactions. I could hardly find any information on the use of BPCA and the required TBOM's in the area of SRM.... Any help would be much appreciated!
Kind Regards,
Guido Jacobs

Hi Guido,
today was a new blog released, maybe this helps:
BPCA - Powerful Risk Eliminator
Best Regards,
Christoph

Portal application connecting backend SAP R/3 system

Hi All,
 I am developing one portal application through NWDS. It's JSPDYNPage component.The applications functionality is basicaly is to connect it to backend SAP R/3 system & fetch some data in aparticular table & display that data in a tableview format on one JSP& also when i click any row of the tableview then details of that row should get displayed on the next JSP. So i reached till develpoing a code that connnects to Backend SAP R/3.(Basicaly coding of connection part is done). Now i need to test this code, to check whether it is fine or not? NWDS doesnt give nay error, not compile also or not runtime error also. It simply shows the output as a blank page, where it is supposed to display one line of text in textview(i coded this in my JSP).But as i said it displays a blank page. i tried to debug the application , but debugging also not worked.I performed the debugging twice in right way. The code was not debugged, it run the same way as it normally runs when debugging is off & shown the blank page. I also have done all the the settings or prerequisites for debugging properly. I am stuck at this point now.search many documents , but no relevant help has been received. Can anyonehlep me with this. i am putting below the code for JSP, JSPDYNPAGE component as well as portalapp.xml. Can anyone guide me with this, whhere i am making mistake? what should i change in this?
JSPDYNPAGE code
package com.lti.portal;
//import java.util.ArrayList;
import com.sapportals.htmlb.*;
import com.sapportals.htmlb.enum.*;
import com.sapportals.htmlb.event.*;
import com.sapportals.htmlb.page.*;
import com.sapportals.portal.htmlb.page.*;
import com.sapportals.portal.prt.component.*;
import java.util.ArrayList;
import com.sap.mw.jco.IFunctionTemplate;
import com.sap.mw.jco.JCO;
import com.sun.corba.se.internal.core.Response;
public class Connection_R3 extends PageProcessorComponent {
public DynPage getPage(){
return new Connection_R3DynPage();
public static class Connection_R3DynPage extends JSPDynPage{
private Conn_R3 myBean = null;
public JCO.Client mConnection;
public JCO.Repository mRepository;
public ArrayList al = new ArrayList();
public String output;
public String Ans;
public static String BEAN_KEY="myBean";
public void doInitialization(){
IPortalComponentRequest request =(IPortalComponentRequest) this.getRequest();
IPortalComponentContext context = request.getComponentContext();
IPortalComponentProfile profile = context.getProfile();
//create & initialize the bean.
Conn_R3 test_bean= new Conn_R3();
test_bean.setans("3");
// put the bean into application context.
context.putValue(BEAN_KEY,test_bean);
conn();
//IPortalComponentResponse res = (IPortalComponentResponse)this.getResponse();
//for(int i=0;i<al.size();i++)
//res.write(" "+al.get(i).toString());
public void doProcessAfterInput() throws PageException {
public void doProcessBeforeOutput() throws PageException {
this.setJspName("Connection_R3.jsp");
public ArrayList conn() {
IPortalComponentRequest request =(IPortalComponentRequest) this.getRequest();
IPortalComponentContext context = request.getComponentContext();
IPortalComponentProfile profile = context.getProfile();
Conn_R3 sample_bean = new Conn_R3();
sample_bean.setans("5");
//context.putValue(BEAN_KEY, sample_bean);
//r3-accessing
//connect_to_r3();
try {
// Change the logon information to your own system/user
mConnection = JCO.createClient("800", // SAP client
"********", // userid
"******", // password
null, // language
"*******", // application server host name
"**"); // system number
mConnection.connect();
//System.out.println(mConnection.getAttributes());
mRepository = new JCO.Repository("ABC", mConnection);
} catch (Exception ex) {
ex.printStackTrace();
System.exit(1);
JCO.Function function = null;
JCO.Table codes = null;
try {
function = this.createFunction("ZSAMPLE");
if (function == null) {
System.out.println("ZSAMPLE" + " not found in SAP.");
System.exit(1);
String num1 = "7";
String num2 = "9";
//String ans;
function.getImportParameterList().setValue(num1,"My_import");
function.getImportParameterList().setValue(num2, "My_Import");
mConnection.execute(function);
Object name =function.getExportParameterList().getValue(Ans);
output=name.toString();
sample_bean.setans(output);
//sample_bean.setans(output)
//al.add(name);
//store values into strings
//pushing of values we get from r3 into awt
} catch (Exception ex) {
ex.printStackTrace();
System.exit(1);
disconnect_r3();
return al;
public void connect_to_r3() {
public JCO.Function createFunction(String name) throws Exception {
try {
IFunctionTemplate ft =
mRepository.getFunctionTemplate(name.toUpperCase());
if (ft == null)
return null;
return ft.getFunction();
} catch (Exception ex) {
throw new Exception("Problem retrieving JCO.Function object.");
public void disconnect_r3() {
mConnection.disconnect();
//**********************Code for BEAN****************************
package com.lti.portal;
import java.io.Serializable;
public class Conn_R3 implements Serializable {
public String answer;
public void setans(String a)
answer=a;
public String getans()
return answer;
///////////////////////Code for JSP*****************************
><%@ taglib uri= "tagLib" prefix= "hbj" %>
<jsp:useBean id="myBean" scope="application" class="com.lti.portal.Conn_R3" />
<hbj:content id="myContext" >
<hbj:page title="PageTitle">
<hbj:form id="myFormId" >
<hbj:textView
id="Welcome_message"
text="<%=myBean.getans()%>"
design="STANDARD" >
</hbj:textView>
</hbj:form>
</hbj:page>
</hbj:content>
/////////////////////////////////Portalapp.xml*****************************************
application>
<application-config>
 <property name="PrivateSharingReference" value="com.sap.portal.htmlb"/>
</application-config>
<components>
 <component name="Address_comp">
 <component-config>
 <property name="ClassName" value="com.lti.portal.Address_comp"/>
 </component-config>
 <component-profile>
 <property name="tagLib" value="/SERVICE/htmlb/taglib/htmlb.tld"/>
 </component-profile>
 </component>
</components>
<services/>
</application>

Hi,
 Do onething, please refer this <a href="http://www.i-barile.it/SDN/JCoTutorial.pdf">JCo Tutorial</a> as well as <a href="http://www.apentia-forum.de/viewtopic.php?t=1962&sid=9ac1506bdb153c14edaf891300bfde25">Link</a> also.
Regards,
Venkatesh. K
/* Points are Welcome */

Help on accessing table available in SAP R/3 System

Hi All
A day before I had posted a question regarding the accessing of tables available in SAP R/3 system.
I got the following code as reply. This code is working fine.
But in the below example, the QUERY_TABLE IS BSAUTHORS.
In my case, the QUERY_TABLE is VBKD(Sales Document Table).
When I replace the table name with VBKD in place of BSAUTHORS, I am getting the following error:
ERROR BEGIN----
com.sap.mw.jco.JCO$AbapException: (126) DATA_BUFFER_EXCEEDED: Selected fields do not fit into structure DATA
     at com.sap.mw.jco.JCO$Function.getException(JCO.java:17978)
     at com.sap.mw.jco.JCO$Client.execute(JCO.java:3143)
     at com.insync.JCO.UpdateSalesOrder.main(UpdateSalesOrder.java:34)
ERROR END----
Can anyone please give me a solution for this?
Thanks in Advace,
Vijay.
**********************Code**********************
import com.sap.mw.jco.*;
public class JcoTest {
private static JCO.Client theConnection;
private static IRepository theRepository;
public static void main(String[] args) {
createConnection();
retrieveRepository();
try {
JCO.Function function = getFunction("RFC_READ_TABLE");
JCO.ParameterList listParams = function.getImportParameterList();
listParams.setValue("BSAUTHORS", "QUERY_TABLE");
//listParams.setValue("VBKD", "QUERY_TABLE"); // ERROR
theConnection.execute(function);
JCO.Table tableList = function.getTableParameterList().getTable("DATA");
if (tableList.getNumRows() > 0) {
   do {
    for (JCO.FieldIterator fI = tableList.fields();
      fI.hasMoreElements();)
      JCO.Field tabField = fI.nextField();
      System.out.println(tabField.getName()
           + ":t" +
           tabField.getString());
     System.out.println("n");
   while (tableList.nextRow() == true);
catch (Exception ex) {
   ex.printStackTrace();

I am also facing the same issue when using 4-way CPU for processing RFC_READ_TABLE I get following error (Error: DATA_BUFFER_EXCEEDED: Selected fields do not fit into structure DATA) .
when I set the NO_DATA=X in RFC_READ_TABLE then returned data object is empty , is this expected behavior ? if yes then how do we extract data without getting this error .Help is greatly appreciated

SAP R/3 System analysis

Hello!
Before the upgrade from R/3 4.6C to ECC 6.0 I would like to execute SAP R/3 system analysis.
The following functions should be included in this program:
- detailed analysis of system modifications (effort driver and risk factor during an Upgrade)
- comparison against a SAP ERP 6.0 reference system
- extension SAP tools, including RBE and conflict lists (SPAU/SPDD)
- syntax analysis of program code with respect of adjustement need
- quality control of own development
- control of amount of transports within different company areas
- control of user information, such a user type, logon date, etc.
- basic control, whether a sufficient authorization concept is available
- Identification of objects that should be considered for the archiving in oder to decrease the db-size
My question are:
- which tasks can be convered with SAP standard transactions what are the names of the transactions?
- which effort do I investigate for these tasks?
Thank you very much!
regards

Dear Thom,
To know the functionality changes u can refer http://solutionbrowser.erp.sap.fmpmedia.com/
http://www.sap.com/solutions/business-suite/erp/pdf/BWP_ERP2006_Upgrade.pdf
http://service.sap.com/releasenotes and http://service.sap.com/upgrade for functional changes.
Need to consider the following things:
For Reportsits custom developed program so unless there is any kind of change in requirement from the client regarding the layoutnothing needs to be changedI think it will work fine in ECC 6.0 toexcept few things may needs to be changed..so you need to discuss whether they want the reorts as it is right nowor want to change the layout (adding some new info/fields etc) of any reportso u need to modify the program for thoseand estimate accordinglyfor a medium complexitys Report dev it takes approx 9 pd (FRSTDSCoding+Unit Testing)so to modify it will be less than that (depending upon the scope of changes)
Now say for Batch Inputs(interface/Data Migration) using BDCyou need to see how many BDCs are thereagain if the field lengths and layouts are not changingthen no need to change anything (except the main thing..you need to change the obsolete function modulesthere are some in 4.6 c like for data upload ws_upload_*** is there 4.6C but obsolete in ECC6.0there are some new with enhanced functionality so you need to modify the BDCsand many cases it happens that the whole transaction screen changes for processin that case better to develop new BDCsso you have to consider those parameterlook into and estimate accordinglymodifying a BDC should not take more than 1 PD
Now say for Formsthere was no Smart form in 4.6Cform printer was there..though the same option is there in ECC 6.0 too..but better to go for/should go for Smart formin that caseits complete new devso estimate accordinglya medium complexitys form should take 8 PD (FRSTDSCoding+Unit Testing)you can take it as 10 PD tooeven if client wants to keep it is as it was in older versionyou have to redevelop the layout in ECC 6.0 againas form printer is even client dependentmaximum you can copy the program associated with that form in the new version tooand your effort will be savedagain you have to consider if clients wants to change the layout too
Now for enhancementso in that case u need to see individual casesfor a medium complexity enhancement it should take max 15 PD (FRSTDSCoding+Unit Testing)
One more important thing is that the Unicode Compatibilitythis needs to be done.needs to change the code (variable name) accordingly.also Version management tool is used for the standard programs
Also pls find the following forums:
Re: Data Migration from 4.6C to ECC 6.0
List of transations supported in SAP 4.6c and not in ECC6.0
Re: Upgradation from 4.6C to ECC 6.0
Re: what's the advantage to upgrade 4.6c to ECC5.0...
RE: Help required regarding to upgrade from R/3 4.6c to mySAp ERP 2005
Upgrade batch inputs from 4.6C to mySAP ERP 2005
/thread/317225 [original link is broken]
Upgrade from SAP R/3 to ECC 6.0
Hope it will help you.
Thanks,
Atin
Reward points if it helps.

SAP R/3 System analysis before upgrade 4.6C -- SAP ECC 6.0

Hello!
Before the upgrade from R/3 4.6C to ECC 6.0 I would like to execute SAP R/3 system analysis.
The following functions should be included in this program:
- detailed analysis of system modifications (effort driver and risk factor during an Upgrade)
- comparison against a SAP ERP 6.0 reference system
- extension SAP tools, including RBE and conflict lists (SPAU/SPDD)
- syntax analysis of program code with respect of adjustement need
- quality control of own development
- control of amount of transports within different company areas
- control of user information, such a user type, logon date, etc.
- basic control, whether a sufficient authorization concept is available
- Identification of objects that should be considered for the archiving in oder to decrease the db-size
My question are:
- which tasks can be convered with SAP standard transactions what are the names of the transactions?
- which effort do I investigate for these tasks?
Thank you very much!
regards

Dear Thom,
To know the functionality changes u can refer http://solutionbrowser.erp.sap.fmpmedia.com/
http://www.sap.com/solutions/business-suite/erp/pdf/BWP_ERP2006_Upgrade.pdf
http://service.sap.com/releasenotes and http://service.sap.com/upgrade for functional changes.
Need to consider the following things:
For Reportsits custom developed program so unless there is any kind of change in requirement from the client regarding the layoutnothing needs to be changedI think it will work fine in ECC 6.0 toexcept few things may needs to be changed..so you need to discuss whether they want the reorts as it is right nowor want to change the layout (adding some new info/fields etc) of any reportso u need to modify the program for thoseand estimate accordinglyfor a medium complexitys Report dev it takes approx 9 pd (FRSTDSCoding+Unit Testing)so to modify it will be less than that (depending upon the scope of changes)
Now say for Batch Inputs(interface/Data Migration) using BDCyou need to see how many BDCs are thereagain if the field lengths and layouts are not changingthen no need to change anything (except the main thing..you need to change the obsolete function modulesthere are some in 4.6 c like for data upload ws_upload_*** is there 4.6C but obsolete in ECC6.0there are some new with enhanced functionality so you need to modify the BDCsand many cases it happens that the whole transaction screen changes for processin that case better to develop new BDCsso you have to consider those parameterlook into and estimate accordinglymodifying a BDC should not take more than 1 PD
Now say for Formsthere was no Smart form in 4.6Cform printer was there..though the same option is there in ECC 6.0 too..but better to go for/should go for Smart formin that caseits complete new devso estimate accordinglya medium complexitys form should take 8 PD (FRSTDSCoding+Unit Testing)you can take it as 10 PD tooeven if client wants to keep it is as it was in older versionyou have to redevelop the layout in ECC 6.0 againas form printer is even client dependentmaximum you can copy the program associated with that form in the new version tooand your effort will be savedagain you have to consider if clients wants to change the layout too
Now for enhancementso in that case u need to see individual casesfor a medium complexity enhancement it should take max 15 PD (FRSTDSCoding+Unit Testing)
One more important thing is that the Unicode Compatibilitythis needs to be done.needs to change the code (variable name) accordingly.also Version management tool is used for the standard programs
Also pls find the following forums:
Re: Data Migration from 4.6C to ECC 6.0
List of transations supported in SAP 4.6c and not in ECC6.0
Re: Upgradation from 4.6C to ECC 6.0
Re: what's the advantage to upgrade 4.6c to ECC5.0...
RE: Help required regarding to upgrade from R/3 4.6c to mySAp ERP 2005
Upgrade batch inputs from 4.6C to mySAP ERP 2005
/thread/317225 [original link is broken]
Upgrade from SAP R/3 to ECC 6.0
Hope it will help you.
Thanks,
Atin
Reward points if it helps.

How to creat purchase register in SAP r/3 system?

Dear All,
Please tell me how to creat purchase register in sap R/3 system.

HI
I think there is no standard functionality in sap u need to develop with abaper help with proper logic
if it is for venijula s_alr_87009936 try this t.code
Thanks & Regards
Phaneendra
Edited by: phaneendra Reddy on Jun 12, 2009 9:24 AM

How to upload the data into SAP R/3 System

I have a scenario to upload the flat file data into SAP R/3 System.
I will describe my complete scenario here so that it will be better understanding for you to suggest the solution.
The segments that relevant for the upload of customer master data, namely
HD : Header Segment
PF : Partner Function Segment
OP : Output Segment
TX : Tax Segment
CR : Credit Segment
CT : Customer Text Segment

I think you can achieve this with IDOC creation. If it is so follow the steps below.
Basic Type:
Basic IDoc type defines the structure and format of the business document that is to be exchanged between two systems.
Segments:
Segments form the basic building blocks of an IDoc type and are used to store the actual datta. A segment type is the name of a segment and is independent of the SAP elease. A segment definition is the release-specific name of a segment.
Steps in creating Segments:
T.Code WE31
Enter the name for your segment type and click on the create icon.
Type the Short text.
Enter the variable names and data elements.
Save and Go back.
Go to Edit -> Set Release.
Repeat the steps to create more segments.
IDOC TYPE:
Business data is exchanged with an external system using the IDoc Interface.
IDoc types (Special Structures) An IDoc type is defined through its permitted segments. Segments can be dependent on each other (parent and child segments). The IDoc interface can check for each IDoc whether thhe segments contained are compatible with thhe definitiion of its type. This systax check is activated or deactivated in the Partner Profiles.
Steps in creating IDoc Type:
T.Code WE30 to create IDoc Type.
Enter the Object Name, Select Basic Type and click Create Icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDoc name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press enter
The system transfers the name of the segment type to the IDoc editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation.
Save it and go back.
Go to Edit -> Set Release.
Message Type:
Steps in Creating Message Type:
T.Code WE81.
change the details from Display mode to Change mode
After selection, the system will give this message "The table is cross client (See help for further info)". Press enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back.
Assign Message Type to IDoc Type:
T.Code WE82
Change the details from Display mode to change mode.
After selection, the system will give this message "The table is cross client (See help for further info)". Press enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back.
Reward Points if useful.

Upload of data into SAP R/3 System

The falt file data is in the form of segment types (HD,PF,TX,OP) and we have to upload it to SAP R/3 System by using the Function modules.
How i have to proceed?
Please ping to my question.

I think you are working with IDOC creation. If it is so follow the steps below.
Basic Type:
Basic IDoc type defines the structure and format of the business document that is to be exchanged between two systems.
Segments:
Segments form the basic building blocks of an IDoc type and are used to store the actual datta. A segment type is the name of a segment and is independent of the SAP elease. A segment definition is the release-specific name of a segment.
Steps in creating Segments:
T.Code WE31
Enter the name for your segment type and click on the create icon.
Type the Short text.
Enter the variable names and data elements.
Save and Go back.
Go to Edit -> Set Release.
Repeat the steps to create more segments.
IDOC TYPE:
Business data is exchanged with an external system using the IDoc Interface.
IDoc types (Special Structures) An IDoc type is defined through its permitted segments. Segments can be dependent on each other (parent and child segments). The IDoc interface can check for each IDoc whether thhe segments contained are compatible with thhe definitiion of its type. This systax check is activated or deactivated in the Partner Profiles.
Steps in creating IDoc Type:
T.Code WE30 to create IDoc Type.
Enter the Object Name, Select Basic Type and click Create Icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDoc name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press enter
The system transfers the name of the segment type to the IDoc editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation.
Save it and go back.
Go to Edit -> Set Release.
Message Type:
Steps in Creating Message Type:
T.Code WE81.
change the details from Display mode to Change mode
After selection, the system will give this message "The table is cross client (See help for further info)". Press enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back.
Assign Message Type to IDoc Type:
T.Code WE82
Change the details from Display mode to change mode.
After selection, the system will give this message "The table is cross client (See help for further info)". Press enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back.
Reward Points if useful.

XI system to SAP R/3 system.

hi,
we are using XI and SAP system.the data transfer from XI to SAP system through IDOC format.
my system is INbound system ie SAP system.
here we are using the message type is HRMD_A.
idoc type is HRMD_A05.
the Idoc is generated in the OUTbound system ie XI system..
the same IDOC should process in the Inbound system ie SAP r/3 system..
from my point of view how i need to start ..to connect the XI system.
can any one help in the view of XI -
SAP ALE/IDoc scenero...
thanks.
partha.

Hi,
Just think about your Inbound System (SAP).
Here you have to do some ALE settings with the Outbound.
Create the Logical systems/Assign to clients
RFC destination
port and Partner profiles creation
while creating Inbound/Outbound parameters assign the
function module IDOC_INPUT_HRMD to the process code.
The above FM will tkae care of the posting data in
the DB.
Thanks
Eswar

Implementing UCES in SAP ISU- IDES system

Hi,
We are interested to implement UCES in SAP ISU - IDES system which we have for our internal competency and Customer POCs/Demos. ( ECC 6 with ISU)
Could any body please share their experience or knowledge on this, that would be of very helpfull.
Many Thanks
Raja

Hi,
There is something called UCES - Biller Direct where is there is an Interaction Between SAP Biller Direct and Contract Accounts Receivable and Payable.
Purpose:You should use SAP Biller Direct if you want to present information about customer accounts in your Internet portal and offer your customers the option of paying bills or of creating inquiries and complaints via the Internet.
Implementation Considerations : Your customer does not need to install any SAP software to be able to use SAP Biller Direct. All functions can be carried out using a standard Web browser.
Information on the necessary system requirements and the browsers supported by SAP Biller Direct can be found in the introductory sections of the installation guide.
SAP Biller Direct consists of an application based on JavaServer Pages. The accounting system runs on a standard application server and is used as the back end for SAP Biller Direct. The transfer of data between the front end and back end is done by RFC and is ensured using the SAP Java Connector (JCO), which you install as part of the SAP middleware.
Award points if this is found useful.

MOPZ - Error during call of SAP back end system

Hi Experts,
I have this error during MOPZ - "select OS/DB dependent files" and following option as well.
I have checked SAP NOTE 982045, but still cannot solve the issue.
SM59 - SAP-OSS and SAPOSS connection test is successful.
I have no idea what else is going wrong. kindly advise id you have any idea.
Below are some error logs.
From MOPZ
Error calling SAP back-end system: Local gateway not running / CPIC-CALL: 'ThSAPCMRCV'SAP-OSS via RFC destination.
From SM21
Call of function GwRead failed, RC: -095
Communication error, CPIC return code 017, SAP return code 24
> Conversation ID: 13681187
> CPI-C function: CMRCV
From dev_rfc8
**** Trace file opened at 20140904 134347 Malay Peninsula Standard Time, by disp+work
**** Versions SAP-REL 721,0,300 RFC-VER U 3 1498740 MT-SL
======> CPIC-CALL: 'ThSAPCMRCV' : cmRc=17 thRc=247
Local gateway not running
ABAP Programm: CL_SM_DATA_SENDER_RFC=========CP (Transaction: )
Called function module: /SPN/SBI_INTERFACE
User: BT_BASIS (Client: 100)
Destination: SAP-OSS (Handle: 4, DtConId: 22F633E42CC0F1D280C9A0D3C1069543, DtConCnt: 1, ConvId: 12214252,{22F633E4-2CC0-F1D2-80C9-A0D3C1069543})
EPP RootContextId: A0D3C10695431ED48CFEB45C956820C9, ConnectionId: D3F533E43BF2F12C80C9A0D3C1069543, ConnectionCnt: 1
EPP TransactionId: D3F533E43BF2F12A80C9A0D3C1069543
SERVER> RFC Server Session (handle: 1, 18243574, {D3F533E4-3BF2-F12C-80C9-A0D3C1069543})
SERVER> Caller host:
SERVER> Caller transaction code: (Caller Program: CL_MO_SMP_ADAPTER=============CP)
SERVER> Called function module: AGS_MOPZ_SMP_RFC
Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 3712
CPIC-CALL: 'ThSAPCMRCV' : cmRc=17 thRc=247
Local gateway not running
Error RFCIO_ERROR_MESSAGE in abrfcio.c : 1973
Thank you.
Por.

Hi
there are following things you can do
1. log on to your SAP Router
2. check entries in SAPRoutab.
3. Telnet SAPSERV2 (Sap responding server) (Tcode oss1 will give you details of which SAP serve you are connecting ) on port 3299
4. if you are able to telnet SAPserve from your Router server then raise the call to SAP and ask whether they can reach your saprouter or not
5. check /etc/services files and check for service 3299 defined or not
6. telnet local Router server with port 3299
7 try to download Sap Note from SNOTE in you solman system.
all the best
Regards
Dishant.

You are not recognized as a user in the SAP customer notification system

Hello,
we are in OSS registered as CCC. I am able to send notifications from our SolMan to OSS with components(instalations) which are registered under out SAP customer number(our SolMan instalation etc.).
When I want to sned notification for our customers to OSS but with component of our customer(he has another SAP number, his instalation) then I got an error message
You are not recognized as a user in the SAP customer notification system:
You are not recognized as a user in the SAP customer notification system
Message no. DNO158
Diagnosis
No address data exists for this logon user in the SAP problem notification system.
The function you activated could not be executed.
Activated function Diagnosis
Send notification to SAP The notification was saved, but could
not be sent to SAP.
Update notification at SAP The notification was not updated to
reflect the SAP version.
Check for changes The system cannot compare the notification
with the current version at SAP.
Request list of the The notifications that you sent to SAP
notifications contained cannot be updated.
in the SAP problem notification system.
Procedure
Contact your system administrators.
Could you help me please?
view V_AISAPCUSTNOS ist filled with our customer numbers, I am in AISUSER...
Thanks Miloslav Pudil

Hello Miloslav,
We have the same problem.
Somebody knows how can we resolve this?
Thanks,
Diego.

SAP R/3 : System Functions

Similar Messages

Maybe you are looking for