‎2012 Jan 10 11:30 AM
Hi experts,
I am working on LSMW for the legacy object SD pricing.
I am using message type - COND_A
Basic type - COND_A01
process code - COND.
When i try to post idoc , i get the error LOAD_PROGRAM_NOT_FOUND.
cause of error is:
program RV13 000 does not exist in library.
form fill_komg_from_vakey cannot be found.
Please help me to solve this.
‎2012 Jan 10 12:30 PM
Hi,
Apply this note 780707
afetr applying this note, copy all standard programs from client 000 to current client.
Regards,
Ravi
‎2012 Jan 10 12:36 PM
With (or from) which version of SAP do you work, there were such mesages a long time ago after upgrade or creation of new condition ?
(old [Note 163347 - Dump in new cond.maint.: LOAD_PROGRAM_NOT_FOUND|https://service.sap.com/sap/support/notes/163347] and [Note 370900 - Dump LOAD_PROGRAM_NOT_FOUND with variant conditions|https://service.sap.com/sap/support/notes/370900])
Regards;
Raymond
‎2012 Jan 12 11:02 AM
Hi Raymond,
We are having SAP ECC 6.0 with Netweaver 7.0
Sys Component Release level Highest Support Description
Package
SAP_APPL 600 0007 SAPKH60007 Logistics and Accounting
SAP_BASIS 700 0014 SAPKB70014 SAP Basis Component .......
Am Anvardheen (SAP BASIS ) -9566855978 from Krithi25 team... Actually We didn't upgrade/update our server but last week We had restarted this server alone..
‎2012 Jan 12 12:06 PM
‎2012 Jan 12 1:27 PM
Hi Raymond,
Thanks for ur quick reply..... Ya our server is 64-Bit Uniocode system.OS: SUN Solaris.. Also I found this Note : 993499 in this note they mentioned " It will be corrected in Release 600 Until SAPKH60014 " But We are having only SAPKH60007.. Whether is it possible to resolve after this note implement or any other mthd? Plz kindly let me know My no- 095566855978
‎2012 Jan 12 1:41 PM
Our system is an AIX Unicode and SAP_APPL version 604 SP 0008 SAPKH60408, so this note is implemented from SAPKH60402 and we don't have this problem any longer using correct value for the new parameter "open dataset mode" (we got a similar problem some years ago in 4.6C, non-unicode AS400 receiving utf-8...)
So, yes, ask Basis to implement note (from 2008) and use the new parameter.
Regards,
Raymond
‎2012 Jan 12 1:46 PM
Hi Raymond,
My doubt is
(From that Note:
" Summary
Symptom
A runtime error occurs when you use the RV14BTCI program to create a batch
input session in a Unicode system with an AS/400 database.)
They mentioned AS/400 database We have Oracle 10.2..
‎2012 Jan 12 1:57 PM
We have Oracle too, not an AS400 (we had some years ago), and the note is installed, you can proceed to implementation without (nearly) any risk. (AS400 raised the error first due to convesrions to EBCDIC from ASCII or Unicode, but the note applies on other systems too)
Basically it will only add a "dataset open mode" to select the way to read the data file
IF def_val EQ 'X'.
OPEN DATASET ds_name FOR INPUT IN TEXT MODE ENCODING DEFAULT.
ELSEIF is_uc EQ 'X'.
OPEN DATASET ds_name FOR INPUT IN TEXT MODE ENCODING UTF-8.
ELSEIF non_uc EQ 'X'.
OPEN DATASET ds_name FOR INPUT IN TEXT MODE ENCODING NON-UNICODE.
ENDIF.As your system is Unicode, default is UTF-8, if the legacy system is not unicode use the NON-UNICODE option.
Regards,
Raymond
‎2012 Jan 19 10:31 AM
Hi Raymond,
In this note:993499 they mentioned " After note implementation, We need to do some manual changes..
1. Maintain the following text symbol:
Sym Text
101 OPEN DATASET mode
2. Enter the following selection texts:
Name Text
DEF_VAL Default
IS_UC UTF-8 (Unicode)
NON_UC Non-Unicode
3. Save and activate your changes. "
Where do I need to change those things?????????? In source code or any other ???????
‎2012 Jan 19 3:36 PM
in which report was the fix made?
Answer: RV14BTCI
so, in which report do you think you have to add text symbols and selection texts then?
Answer: RV14BTCI or do you see that this OSS note does anything to any other reports?
what transaction is used to work on reports?
SE38
‎2012 Jan 20 10:50 AM
Dear Jurgen,
We have got dump " Program RV13 000" not found..
Current ABAP program "SAPLVKOI" had to be terminated because It has come accross a statement that unfortunately cannot be executed.............. " Also one more thing We didn't make any change in standard program just sent IDoC through LSMW..............