Error on standard RKKBCAL2 program

Hi Friends,
We have one standard program RKKBCAL2 in this report Material cost value was not shows the correct values, Any one plz suggest me the note No's
Thanks in advance,

Hi Venkat,
Some notes related to the program are
Note 1140436 - CK40N: Jump from material overview appears to be incorrect
Note 1052825 - Costing analysis: Incorrect display of value fields
Note 853273 - CK40N: Analysis results are incorrect
and many more....
Don't you have SAP market place ID ? You need to analyse all the notes properly before applying them. better to get the ID. Your BASIS consultant should have it
Regards
Rajvansh
Edited by: Rajvansh Ravi on Dec 1, 2008 7:57 AM

Similar Messages

Syntax error in standard SAP program.

Can someone help me. I'm getting the following error while executing
"Include /sapboq/bos_lbos01top, No component exists with the name /sapboq/mitem. Check the program SAPLBOS01"
Error in the ABAP Application Program
The current ABAP program "BS01_SALESORDER_GETDETAIL=====FT" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "SAPLBOS01 " in include
"/SAPBOQ/BOS_LBOS01TOP " in
line 9:
"No component exists with the name "/SAPBOQ/MITEM". ."
Edited by: nithinrayal on Jul 12, 2010 9:54 PM

Hi,
Go to txn SE38 and display program "BS01_SALESORDER_GETDETAIL=====FT". Then do a syntax check. It should tell you what is the error.
I guess its some support pack that is missing. Try contacting SAP for this.
Regards
Prasenjit

Error in Standard Program for Purchase Order

Hello Everyone,
I am getting an ABAP Dump Error while Displaying & Printing Purchase Order using TCODE : ME9F & ME23N.
We have applied new Patches.
for Logistics it is 26 & ABAP it is 58.
I am getting Error in standard INCLUDE
Program : LMEDRUCKF1K at line 64.
The Error is :- "Field "ENJPREVIEW" is unknown. It is neither in one of the specified tables nor defined by a "DATA" statement."
Declaration for "ENJPREVIEW" is also available in
include LMEDRUCKTOP. still it gives an error.
These lines of code is included by SAP note 855263.
Before applying these Patches it was working properly, but now it gives an error.
Please , Can anyone give solution for this.
Regard's
Archana.

Hi Archana ,
Check is there any Inactive Versions in ur Systems ?
useful tcodes are SPAU /SPDD for tables
Regards
prabhu

Error while runing standard SRS program

Hi all,
I had written the interface for po_vendor_sites_all.The data is loaded perfectly into interface table AP_SUPPLIER_SITES_INT.
Now while running standard interface program on SRS(Supplier Sites Open Interface Import) .it is giving following error .
Spawned Process 24209
REP-1419: 'beforereport': PL/SQL program aborted.
And it is not showing any reject code or status on back end on table AP_SUPPLIER_SITES_INT. And it is printing IMPORT_REQUEST_ID as request code in the table.now how many times i will run the SRS it is showing in the table AP_SUPPLIER_SITES_INT the MPORT_REQUEST_ID is not changing .
Thanks in advance
Goutham

the same situation i am also facing everything almost same .... but just i got diffirent error in request log that is
==========================
==========================
P_WHAT_TO_IMPORT='ALL'
P_COMMIT_SIZE='1000'
P_PRINT_EXCEPTIONS='Y'
P_DEBUG_SWITCH='Y'
P_TRACE_SWITCH='Y'
Current NLS_LANG and NLS_NUMERIC_CHARACTERS Environment Variables are :
American_America.US7ASCII
LOG :
Report: d:\oracle\prodappl\ap\11.5.0\reports\US\APXSSIMP.rdf
Logged onto server:
Username:
LOG :
Logged onto server:
Username: APPS
MSG MSG-00001: After SRWINIT
MSG MSG-00002: After Get_Company_Name
MSG MSG-00003: After Get_NLS_Strings
ERR REP-1419: 'beforereport': PL/SQL program aborted.
is anyone got solution and can anybody get me out of this situation
thanks in advance
regards
anwer

Syntax error in standard program after upgrade

Hi,
After upgrade from 7.0 to 7.3, we are facing a syntax error in standard program that is used in one of our process
The error says:
The field "G_REQUIDPARENT" is unknown, but there is a field with the s"
imilar name "G_REQUID_LAST". "G_REQUID_LAST"."
The system cannot find this object inside include LRSBM_REQUEST_GUIP04, that belongs to program SAPLRSBM_REQUEST_GUI
We assume that this is associated with the upgrade but we cannot find any solution in the web. Besides, this is a standard program so we cannot perform any change directly. We look for SAP Notes to apply but we didn't find nothing worthwhile
Basically, we are receiving a dump with the error message posted above and we found the syntax error, but the thing is that we don't know how to fix it, due to the fact that is a standard program and we cannot change it
I know that SAP could remove some object reference during the upgrade, but there should be an anticipated plan to fix this kind of errors, right?
Can you shed some light on this, please ?
Thanks a lot
Ale

Hi Ale,
If you make sure there are no customization around the object and SGEN already run, I think you can just open a OSS message to SAP to looking for a fix.
Regards
Bill

Unicode Error in standard program

Hi,
Iam working on an upgrade project
I am getting an error as below
"In Unicode, DESCRIBE LENGTH can only be used with the IN BYTE MODE or CHAR mode"
How to fix this error, as the error is from STANDARD PROGRAM "Include /IXOS/LDC_CF01"
I know the answer to fix it, But since it is a STANDARD PROGRAM ,how to modify standard program\
Thanks,
Arjun

Dear Arjun,
I had to make some adjustment to an upgrade recently where we also had to upgrade programs to be UNICODE compliant.
And we had to do this for Custom and Standard programs.
So, before writing a message for SAP, go to transaction:
UCCHECK
It was using this transaction that I adapted my Standard SAP programs.
So you should be ok with this as well....
If you have been there already, then by all means do write a message to SAP.
Kind Regards
/Ricardo Quintas

Transport error on standard program during transport of SPAU adjustments

Hi,
We are trying to transport adjustments made for SPAU into our Testing Environment. However, we encountered an error for program: AL01900R, Include MKGALF60: Syntax error in line 001861', 'Field 'DELTA_FGROUPS_REC' is unknown. It is neither in one of the specified tables nor defined'
First of all, the program and include were not modified and not included in the transport request. Not sure why it was being checked. But this is not a serious concern.
The 'DELTA_FGROUPS_REC' field declaration is indeed missing from the program.
Does anyone have any ideas how we can patch this? This is a standard SAP program, is there any way we can get latest code from SAP to patch (because usually OSS note only targets that include and not the entire program and its includes).
Thank you.
Regards,

Hi Snow,
I re-read the OSS note and tried to run allocation for it. Surprisingly, that action re-compiles the main program: AL01900R and now the data declaration is generated automatically. So yes, it works now.
Thank you very much for the suggestion!

Error in executing ABAP program. Error occurred when creating dataset

hi,
when I use LKM SAP ERP to Oracle (SQLLDR) to extract data from SAP ERP server. I execute my interface, and it's stop at extract data step.
This is message:
java.lang.RuntimeException: Error occured in open tool execute method...Error in executing ABAP program...Error in executing ABAP program...Error occurred when creating dataset/abc/ZODI_13001_6001_GLOBAL.txt
I tried others path name, tried slash or backslash. This is content in code tab
OdiSAPAbapExecute "-UPLOAD=1" "-EXECUTE=1" "-EXECUTEBASE_RKM=0" "-ZRFC_RUN_INSTALL=1" "-ABAP_PROGRAM_NAME=ZODI_13001_6001" "-HOST=10.86.87.24" "-USER=sv_hoa" "-PASSWORD=<@=snpRef.getInfo("SRC_PASS") @>" "-SAP_CLIENT=800" "-SAP_LANGUAGE=EN" "-SAP_SYSTEM_NUMBER=02" "-SAP_FUNCTION_GROUP_NAME=ZODI_FGR_13001" "-CONNECTION_POOL_NAME=SAP_ODI_ERP_POOL_10.86.87.24" "-CONNECTION_POOL_SIZE=10" "-FILE_DELIMITER=<@=""+(char)8@>" "-FILE_NAME=ZODI_13001_6001_GLOBAL.txt" "-FTP_HOST=10.86.82.108" "-FTP_USER=anh" "-FTP_PASSWORD=<@=sFtpPassword@>" "-FTP_PASSIVE_MODE=1" "-FTP_TRANSFER_TIMEOUT=100000" "-ODI_VARIABLE_NAMES=" "-ODI_VARIABLE_VALUES=" "-USER_ABAP_PARAMETER_NAMES=IV_DELIMITER,CHAR3;IV_FILENAME,CHAR255;IV_USER,CHAR35;IV_PWD,CHAR35;IV_HOST,CHAR35;IV_HASHVALUE,CHAR35;IV_PATH,CHAR35;IV_MAX_ROW_CNT,SYTABIX;IV_FETCH_BATCH_SIZE,SYTABIX;" "-USER_ABAP_PARAMETER_VALUES=<Value>" "-USER_ABAP_PARAMETER_SEPARATOR=<Value>" "-ABAP_TABLE_PARAMETERS=RETURN,BAPIRETURN;ET_FILE_RETURN,BAPIRET2" "-ABAP_EXPORT_PARAMETERS=ERRORMESSAGE;SY-MSGV1" "-LOG_FILE_NAME=C:\Users\anh\AppData\Local\Temp\SapAbapExecuteOpenTool_13001.log" "-FTP_PATH=/abc/" "-DEV_CLASS=ZODI_DEVCLASS" "-MAX_ROW_COUNT=" "-FETCH_BATCH_SIZE=100000" "-HASH_VALUE_MARKER=HVM" "-ABAP_PROGRAM_BODY=
*Final Type declarations
TYPES : BEGIN OF ty_final,
Y03HOCSINH_HOCSINH_ID TYPE
Y03HOCSINH-HOCSINH_ID,
Y03HOCSINH_MA_HOC_SINH TYPE
Y03HOCSINH-MA_HOC_SINH,
Y03HOCSINH_TEN_HOC_SINH TYPE
Y03HOCSINH-TEN_HOC_SINH,
Y03HOCSINH_GIOI_TINH TYPE
Y03HOCSINH-GIOI_TINH,
Y03HOCSINH_DIA_CHI TYPE
Y03HOCSINH-DIA_CHI,
Y03HOCSINH_GHI_CHU TYPE
Y03HOCSINH-GHI_CHU,
END OF ty_final.
*Final Temp Type Declarations
TYPES : BEGIN OF ty_final_tmp,
Y03HOCSINH_HOCSINH_ID TYPE
Y03HOCSINH-HOCSINH_ID ,
Y03HOCSINH_MA_HOC_SINH TYPE
Y03HOCSINH-MA_HOC_SINH ,
Y03HOCSINH_TEN_HOC_SINH TYPE
Y03HOCSINH-TEN_HOC_SINH ,
Y03HOCSINH_GIOI_TINH TYPE
Y03HOCSINH-GIOI_TINH ,
Y03HOCSINH_DIA_CHI TYPE
Y03HOCSINH-DIA_CHI ,
Y03HOCSINH_GHI_CHU TYPE
Y03HOCSINH-GHI_CHU ,
END OF ty_final_tmp.
*Final Target Type Declarations
TYPES : BEGIN OF ty_final_target,
C0_Y03HOCSINH_HOCSINH_ID TYPE
Y03HOCSINH-HOCSINH_ID,
C1_Y03HOCSINH_MA_HOC_SINH TYPE
Y03HOCSINH-MA_HOC_SINH,
C2_Y03HOCSINH_TEN_HOC_SINH TYPE
Y03HOCSINH-TEN_HOC_SINH,
C3_Y03HOCSINH_GIOI_TINH TYPE
Y03HOCSINH-GIOI_TINH,
C4_Y03HOCSINH_DIA_CHI TYPE
Y03HOCSINH-DIA_CHI,
C5_Y03HOCSINH_GHI_CHU TYPE
Y03HOCSINH-GHI_CHU,
END OF ty_final_target.
* Table type for Y03HOCSINH
TYPES : BEGIN OF ty_Y03HOCSINH,
HOCSINH_ID TYPE
Y03HOCSINH-HOCSINH_ID,
MA_HOC_SINH TYPE
Y03HOCSINH-MA_HOC_SINH,
TEN_HOC_SINH TYPE
Y03HOCSINH-TEN_HOC_SINH,
GIOI_TINH TYPE
Y03HOCSINH-GIOI_TINH,
DIA_CHI TYPE
Y03HOCSINH-DIA_CHI,
GHI_CHU TYPE
Y03HOCSINH-GHI_CHU,
END OF ty_Y03HOCSINH.
TYPES: BEGIN OF gs_text,
line(843) TYPE c,
END OF gs_text.
*Structure Declarations
DATA: wa_final_string TYPE string,
wa_final TYPE ty_final,
wa_final_target TYPE ty_final_target,
wa_Y03HOCSINH TYPE ty_Y03HOCSINH,
*Table Declarations
tt_final TYPE STANDARD TABLE OF ty_final,
tt_Y03HOCSINH TYPE STANDARD TABLE OF ty_Y03HOCSINH,
tt_final_target TYPE STANDARD TABLE
OF ty_final_target,
tt_final_tmp TYPE STANDARD TABLE OF ty_final_tmp,
tt_final_tmp1 TYPE STANDARD TABLE OF ty_final,
gt_result TYPE STANDARD TABLE OF gs_text,
*Variable Declarations
lv_path TYPE string,
lv_flag TYPE char1,
C0_Y03HOCSINH_HOCSINH_ID TYPE
STRING,
C1_Y03HOCSINH_MA_HOC_SINH TYPE
STRING,
C2_Y03HOCSINH_TEN_HOC_SINH TYPE
STRING,
C3_Y03HOCSINH_GIOI_TINH TYPE
STRING,
C4_Y03HOCSINH_DIA_CHI TYPE
STRING,
C5_Y03HOCSINH_GHI_CHU TYPE
STRING,
wa_final_tmp TYPE ty_final_tmp,
lv_file TYPE string,
lv_datum TYPE sy-datum,
lv_date TYPE char10,
wa_result TYPE string,
lv_delimiter type string,
lv_cnt TYPE sytabix,
*-Cursor Declaration
lv_Y03HOCSINH_dbcur TYPE cursor,
lv_tabix_frm TYPE sy-tabix.
lv_delimiter = iv_delimiter.
IF iv_hashvalue = 'HVM'.
*Open/delete output file
CONCATENATE iv_path iv_filename INTO lv_path.
*Check for file existence, if found, delete it
OPEN DATASET lv_path FOR INPUT
IN TEXT MODE
ENCODING DEFAULT.
IF sy-subrc EQ 0.
DELETE DATASET lv_path.
ENDIF.
*Open/create output file
OPEN DATASET lv_path FOR APPENDING
IN TEXT MODE
ENCODING DEFAULT.
IF sy-subrc EQ 0.
*Batch Processing
OPEN CURSOR WITH HOLD lv_Y03HOCSINH_dbcur FOR
SELECT HOCSINH_ID
MA_HOC_SINH
TEN_HOC_SINH
GIOI_TINH
DIA_CHI
GHI_CHU
FROM Y03HOCSINH.
DO.
*Check for the counter, only for first batch
*process new line is required...
lv_cnt = lv_cnt + 1.
REFRESH tt_Y03HOCSINH.
FETCH NEXT CURSOR lv_Y03HOCSINH_dbcur
APPENDING TABLE tt_Y03HOCSINH
PACKAGE SIZE IV_FETCH_BATCH_SIZE.
IF NOT tt_Y03HOCSINH IS INITIAL.
ELSE.
EXIT.
ENDIF.
LOOP AT tt_Y03HOCSINH INTO wa_Y03HOCSINH.
MOVE wa_Y03HOCSINH-HOCSINH_ID
TO wa_final_tmp-Y03HOCSINH_HOCSINH_ID.
MOVE wa_Y03HOCSINH-MA_HOC_SINH
TO wa_final_tmp-Y03HOCSINH_MA_HOC_SINH.
MOVE wa_Y03HOCSINH-TEN_HOC_SINH
TO wa_final_tmp-Y03HOCSINH_TEN_HOC_SINH.
MOVE wa_Y03HOCSINH-GIOI_TINH
TO wa_final_tmp-Y03HOCSINH_GIOI_TINH.
MOVE wa_Y03HOCSINH-DIA_CHI
TO wa_final_tmp-Y03HOCSINH_DIA_CHI.
MOVE wa_Y03HOCSINH-GHI_CHU
TO wa_final_tmp-Y03HOCSINH_GHI_CHU.
APPEND wa_final_tmp TO tt_final_tmp.
ENDLOOP.
free : tt_Y03HOCSINH.
LOOP AT tt_final_tmp INTO wa_final_tmp.
MOVE wa_final_tmp-Y03HOCSINH_HOCSINH_ID
TO wa_final_target-C0_Y03HOCSINH_HOCSINH_ID.
MOVE wa_final_tmp-Y03HOCSINH_MA_HOC_SINH
TO wa_final_target-C1_Y03HOCSINH_MA_HOC_SINH.
MOVE wa_final_tmp-Y03HOCSINH_TEN_HOC_SINH
TO wa_final_target-C2_Y03HOCSINH_TEN_HOC_SINH.
MOVE wa_final_tmp-Y03HOCSINH_GIOI_TINH
TO wa_final_target-C3_Y03HOCSINH_GIOI_TINH.
MOVE wa_final_tmp-Y03HOCSINH_DIA_CHI
TO wa_final_target-C4_Y03HOCSINH_DIA_CHI.
MOVE wa_final_tmp-Y03HOCSINH_GHI_CHU
TO wa_final_target-C5_Y03HOCSINH_GHI_CHU.
Append wa_final_target to tt_final_target.
ENDLOOP.
free : tt_final_tmp.
Clear wa_final_target.
IF NOT iv_max_row_cnt IS INITIAL.
Loop at tt_final_target into
wa_final_target TO iv_max_row_cnt.
MOVE wa_final_target-C0_Y03HOCSINH_HOCSINH_ID
TO C0_Y03HOCSINH_HOCSINH_ID.
MOVE wa_final_target-C1_Y03HOCSINH_MA_HOC_SINH
TO C1_Y03HOCSINH_MA_HOC_SINH.
MOVE wa_final_target-C2_Y03HOCSINH_TEN_HOC_SINH
TO C2_Y03HOCSINH_TEN_HOC_SINH.
MOVE wa_final_target-C3_Y03HOCSINH_GIOI_TINH
TO C3_Y03HOCSINH_GIOI_TINH.
MOVE wa_final_target-C4_Y03HOCSINH_DIA_CHI
TO C4_Y03HOCSINH_DIA_CHI.
MOVE wa_final_target-C5_Y03HOCSINH_GHI_CHU
TO C5_Y03HOCSINH_GHI_CHU.
CONCATENATE
C0_Y03HOCSINH_HOCSINH_ID
C1_Y03HOCSINH_MA_HOC_SINH
C2_Y03HOCSINH_TEN_HOC_SINH
C3_Y03HOCSINH_GIOI_TINH
C4_Y03HOCSINH_DIA_CHI
C5_Y03HOCSINH_GHI_CHU
INTO wa_final_string
SEPARATED BY lv_delimiter.
IF sy-tabix EQ 1 AND lv_cnt EQ 1.
CONCATENATE wa_final_string
lv_delimiter INTO wa_final_string.
ELSE.
CONCATENATE '<@=""+(char)8@>' lv_delimiter wa_final_string
lv_delimiter INTO wa_final_string.
ENDIF.
APPEND wa_final_string TO gt_result.
CLEAR : C0_Y03HOCSINH_HOCSINH_ID,
C1_Y03HOCSINH_MA_HOC_SINH,
C2_Y03HOCSINH_TEN_HOC_SINH,
C3_Y03HOCSINH_GIOI_TINH,
C4_Y03HOCSINH_DIA_CHI,
C5_Y03HOCSINH_GHI_CHU.
ENDLOOP.
ELSE.
Loop at tt_final_target into wa_final_target.
MOVE wa_final_target-C0_Y03HOCSINH_HOCSINH_ID
TO C0_Y03HOCSINH_HOCSINH_ID.
MOVE wa_final_target-C1_Y03HOCSINH_MA_HOC_SINH
TO C1_Y03HOCSINH_MA_HOC_SINH.
MOVE wa_final_target-C2_Y03HOCSINH_TEN_HOC_SINH
TO C2_Y03HOCSINH_TEN_HOC_SINH.
MOVE wa_final_target-C3_Y03HOCSINH_GIOI_TINH
TO C3_Y03HOCSINH_GIOI_TINH.
MOVE wa_final_target-C4_Y03HOCSINH_DIA_CHI
TO C4_Y03HOCSINH_DIA_CHI.
MOVE wa_final_target-C5_Y03HOCSINH_GHI_CHU
TO C5_Y03HOCSINH_GHI_CHU.
CONCATENATE
C0_Y03HOCSINH_HOCSINH_ID
C1_Y03HOCSINH_MA_HOC_SINH
C2_Y03HOCSINH_TEN_HOC_SINH
C3_Y03HOCSINH_GIOI_TINH
C4_Y03HOCSINH_DIA_CHI
C5_Y03HOCSINH_GHI_CHU
INTO wa_final_string
SEPARATED BY lv_delimiter.
IF sy-tabix EQ 1 AND lv_cnt EQ 1.
CONCATENATE wa_final_string
lv_delimiter INTO wa_final_string.
ELSE.
CONCATENATE '<@=""+(char)8@>' lv_delimiter wa_final_string
lv_delimiter INTO wa_final_string.
ENDIF.
APPEND wa_final_string TO gt_result.
CLEAR : C0_Y03HOCSINH_HOCSINH_ID,
C1_Y03HOCSINH_MA_HOC_SINH,
C2_Y03HOCSINH_TEN_HOC_SINH,
C3_Y03HOCSINH_GIOI_TINH,
C4_Y03HOCSINH_DIA_CHI,
C5_Y03HOCSINH_GHI_CHU.
ENDLOOP.
ENDIF.
free : tt_final_target.
IF NOT gt_result IS INITIAL.
CLEAR wa_result.
LOOP AT gt_result INTO wa_result.
TRANSFER wa_result TO lv_path.
ENDLOOP.
ENDIF.
REFRESH gt_result.
*End of main loop for batching
ENDDO.
*Close dataset
CLOSE DATASET lv_path.
CLOSE CURSOR lv_Y03HOCSINH_dbcur.
ELSE.
DATA: lv_mesg TYPE string.
CLEAR et_file_return.
et_file_return-type = 'E'.
CONCATENATE
'Error occurred when creating dataset' lv_path
INTO lv_mesg.
et_file_return-message = lv_mesg.
Append et_file_return.
ENDIF.
ELSE.
CLEAR et_file_return.
et_file_return-type = 'E'.
et_file_return-message =
'Installed ABAP program does not match interface definition'.
APPEND et_file_return.
ENDIF.
Thanks for help

r u able to figure it out..........i got the same error .......can someone help me fix this issue

Error in a submit program

Hello,
In a program, there is a "submit and return" of another program. When they occurs an error in the second program (message error), the traitement stops and don't returns to the first program.
How can it be possible to return to the first program even if there is an error in the second program?
Thanks,
Regards,
Patrice.

Hi,
If your program is not dependent on the SUBMITTED program (Some thing like that standard program doesn't have any output) then you can try in below way.
CALL JOB_OPEN
SUBMIT standard program
CALL JOB_CLOSE.
This creates a batch job for standard program.
If your program is dependent, then i don't see any possibility other than doing the same validations in your program before calling the standard program.
Thanks,
Vinod.

Getting An Error when a Concurrent Program is run

ORA-20001: A value has been provided for a non-enabled or non-existent descriptive flexfield segment. This Error is coming out from the API call - hr_person_api.update_person. Please advise !

Hi,
Please mention the OS version and the application release.
Is this a custom or standard concurrent program?
Has this ever worked? If yes, what changes have been done recently?
Search My Oracle Support for "ORA-20001 hr_person_api.update_person", go through the documents, and see if it helps.
If none of the above helps, enable trace, submit the concurrent program and check the log file for details about the error.
Regards,
Hussein

Error upon executing driver program

Hi guys,
iam getting the following error when executing print program;
I/O error from text Z_TABLE_DATA ST EN.
(actually am trying to pass the subroutine pool prog.through perform statement , in that i inlcuded the standard text).
Regards
chandrakanth.k

please check this text in SO10 tcode ,Z_TABLE_DATA ST EN, this text language EN not maintained..

How to find CUSTOMER EXIT for a Standard SAP program

How to find CUSTOMER EXIT for a Standard SAP program

Hi
To introduce the techniques of enhancement in standard SAP system. SAP creates customer exits for specific programs, screens, and menus within standard R/3 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.
They do not affect standard SAP source code.
When you add new functionality to your SAP System using SAPs exits, you do not alter the source code of standard SAP programs in any way. The code and screens you create are encapsulated as separate objects. These customer objects are linked to standard applications, but exist separately from SAPs standard software package.
They do not affect software updates.
When you add new functionality to your SAP System using SAPs exits, your objects (called customer objects) must adhere to strict naming conventions. When it comes time to upgrade a to a new software release, customer objects names ensure that they will not be affected by any changes or new additions to the standard software package.
Customer exits are not available for all programs and screens found in the SAP System.
Any change made to an SAP object in a customer system is called a modification. Customers usually modify their systems for one of two reasons. Either they make changes to the SAP standard in order to adjust the R/3 System to their specific business needs (actual modifications), or they alter individual SAP objects in order to correct an error (as recommended in an SAP error note).
You should only modify the SAP standard if the modifications you want to make are absolutely necessary for optimizing work flow in your company. Be aware that good background knowledge of application structure and flow are important prerequisites for deciding what kind of modifications to make and how these modifications should be designed.
SAP application programmers create SAP enhancements in transaction SMOD using function module exits, menu exits, and screen exits.
Customers are given a catalog containing an overview of existing SAP enhancements. They can then combine the SAP enhancements they want into an enhancement project using transaction CMOD.
SAP enhancements are made up of component parts. These components include function module exits, menu exits, and screen exits. A specific component may be used only once in a single SAP enhancement (this guarantees the uniqueness of SAP enhancements).
Customer enhancement projects consist of SAP enhancements. Each individual SAP enhancement may be used only once in a single customer enhancement program (this guarantees the uniqueness of a customer project).
SAP application programmers preplan function module exits, menu exits, and screen exits for their applications and combine them to create useful enhancements for the R/3 System.
Customers create their own enhancement projects for their systems using SAP enhancements. You can customize the individual components of an enhancement project by creating your own include programs (for function module exits), texts (for menu exits), and subscreens (for screen exits).

Import Standard PO program produces no output

Hi,
I'm importing standard POs using the Import Standard PO program. Even though the PO gets created fine, I can't see an output when the program completes. Any pointers please?
thanks!

Hi,
You can try the following ways
1. Run Purchasing Interface Errors Report with Source parameters
2. Interface table ERROR field can be also be refered
3. Run Purchase order Details report after configuring Parameters Source
Regards,
Arun

Z TCode for Standard SAP Program

Hi all,
Is it allowed by default (by SAP standard rule) to create a Z TCode for the existing standard SAP program? By doing this, I will have two transaction codes for one standard SAP program. One is the existing SAP standard TCode and the other one is the Z (custom) TCode. Both point to the same SAP standard program.
I tried to copy TCode ME22 to ZME22 but I get error message "Transaction code ZME22 not defined" when I tried run it. ZME22 was successfully created (no error) with the same setting as ME22 during copying.
Thanks in advance.
Regards,
Goh Tiam Tjai

Goh,
yes obvoiusly you can create another t-code.
as i want to add more thing which all were missed is that you have to create parameter transaction from se93.
and give default transaction as me22 in your case.
hope now your problem has been resolved.
please mark all good answer.
Amit.

Hr_utility.trace - standard concurrent program

Hi,
We have a standard concurrent program that we think is falling over due to data error. Looking at the code that is being run, there seems to be a lot of useful info traced out by hr_utility.trace(). How can I enable this for a concurrent program though? It seems that all the references I can find refer to enabling it when calling from sqlplus etc, rather than when the code is running as part of a concurrent program.
Thanks

/dev/null wrote:
Hi,
We have a standard concurrent program that we think is falling over due to data error. Looking at the code that is being run, there seems to be a lot of useful info traced out by hr_utility.trace(). How can I enable this for a concurrent program though? It seems that all the references I can find refer to enabling it when calling from sqlplus etc, rather than when the code is running as part of a concurrent program.
ThanksYou need to take a backup of the package and add the code -- Please see these docs for details.
Using PYUPIP in Oracle HRMS [ID 130374.1]
How To Trace In The HRMS Application [ID 105292.1]
Oracle HRMS Data Pump [ID 226988.1]
If you want to use the regular trace, please refer to:
How To Trace a Concurrent Request And Generate TKPROF File [ID 453527.1]
How To Create Trace File and Run Tkprof in E-Business Suite Applications - Condensed Version [ID 141278.1]
Thanks,
Hussein

Error on standard RKKBCAL2 program

Similar Messages

Maybe you are looking for