/SAPAPO/TS_DM_GET = LC-ERROR 40020

Hi,
i have to read time-series data with /SAPAPO/TS_DM_GET.
With few data selection this works fine.
But with a great selection it fails.
Background the interal counter "Z" of table et_tab - ddic-structure /SAPAPO/TS_TAB_EXT wil be only int4.
if i split the selection in blocks to handle it in the SAME REPORT, it would be necessary to reset counter and ... for the live-cache.
Will there be a function module or method for this?
Kind reagards

solved

Similar Messages

Error when generating program /SAPAPO/TSM141 and Errors in source system

Hello APO Experts!
I had to include a new key figure in the cube and the planning area with configuration semantic = 000.
The problem is, in my DEV system, the modification was perfect. Then when I did in the QA system, I´ve got the error "Error when generating program /SAPAPO/TSM141" and u201CErrors in source systemu201D when trying to load data in the Infopackage.
Do you have any idea of what this could be?
Best Regards
Nik

Hello,
The problem may come from the inconsistency between the datasource settings and the content in table /SAPAPO/TSAREATE.
- SE16, go to table /SAPAPO/TSAREATE, input the planning area name, check the extraction structure, which is started from '/1APO/EXT_STRU'.
- SE16, go to table /SAPAPO/TSAREAEX, input the datasource name, and check the extraction structure.
Are the two extraction structures the same or different ?
If they're different, please read the below solutions, otherwise, you can ignore the following.
In general and most customer cases this inconsistency happens during transporting of datasource alone. In many cases the planning area is directly created at target system and datasoucre transported from a a different system which causes incorrect export structure entry in planning area table.
Please refer to following content from note 549184:
Q4: Why could I have extraction problem after transport of DataSource?
A4: DataSources for DP/SNP planning areas depend directly on the structure of the planning areas. That's why the planning area MUST ALWAYS be transported with or before the DataSource.
The simple solution will be to create a dummy data source for this planning area. This will regenerate the extract structure for all other data sources as well and update the corresponding tables. After that you can delete the dummy datasource.
After delete the dummy datasource, in case of inconsistency, please also run the report /SAPAPO/TS_PSTRU_GEN report for
- Basis - form routines
- Create planning objects
- Planning area extractor
with the flags "Reset generation time stamp" and "Generate" set.
And in order to transfer datasource correctly, please also refer to the consulting note 514524.
Best Regards,
Ada

Error while Saving in /SAPAPO/MC77 - Maintain Selection Assignments

Hi All,
While saving selection assignments for users in SAP APO Demand Planning through the Transaction code /SAPAPO/MC77
I am getting an information message whenever I click the save button
"Inconsistency identified during save
Message no. /SAPAPO/MA863"
This error message is only for the planning book belonging to a specific planning area.
What can be done to resolve this issue?

Hello,
There should be duplicated entries in your selections.
You can set a BP in Form check_single_profile in program /SAPAPO/LMCPSFC2 in the debugger.
Check parameter lt_tsselorg_ext[].
For the entries in lt_tsselorg_ext[]. the 'ORDERKEY' field must be continous and no duplicate.
Please delete the inconsistent ones.
Best Regards,
Ada

Error "E:/SAPAPO/RRP:003 0000036534"

Hi Gurus,
When i was doing txn MD12 ie change in the planned order for make-to order and i am trying to look for the component availability (shift+F7), it is giving me error as "E:/SAPAPO/RRP:003 0000036534"
What is this msg all about?

Hello addhya
Please check if the following notes are already implemented in your system:
1068815: /SAPAPO/RRP003 : Order xxxxxx does not exist
734455: /SAPAPO/RRP 003 error message after ATP check
913396: Bypass popup "Order does not exist" in SCM ATP check
951819: ATP check for maintenance order
Also, the following information you can find in the error longtext:
++++++++++++++++++++++++++++++++++++++++++++++++++++
NA /SAPAPO/RRP003
Short Text
Order &1 does not exist
Diagnosis
There are inconsistencies
In SAP APO between the database and liveCache or
Between SAP APO and the OLTP system
System Response
The system cannot read the order from the database.
Procedure
This message can occur, for example, if you perform an availability check for a manufacturing order in SAP R/3 and the manufacturing order is not yet in SAP APO. In this case, repeat the check at a later time.
Remove the inconsistencies. Use the following transactions:
If there are inconsistencies in SAP APO, use the consistency check
Call Consistency Check Immediately.
If there are inconsistencies between SAP APO and SAP R/3, use the Compare/Reconcile Function
Call Compare/Reconcile Function Immediately
++++++++++++++++++++++++++++++++++++++++++++++++++++
I hope it helps
Best regards
Gabriel

DP - Seasonality groups posting period conversion error

Hi,
I have recently configured Seasonality Groups which was released in APO SCM7 EHP2 with the Demand Planning Worklist. We are using posting periods (fiscal periods) in all planning books and background jobs,
The following notes have been implemented in our system: 1871842-1879577-1900933-1855921, and our latest APO support pack is SAPKY70204.
The following steps were successfully processed:
- Specify planning level
- Maintain settings for seasonality
- Create seasonality groups
However, the assignment of planning objects to seasonality groups generate an error when using period indicator P. It was successful with period indicator M. Here is a sample message from the short dump generated.
The following error occurred in system XXX : Period for date 0000.00.00 cannot be determined
The error occurred on application server XXXX and in work process. 8
The termination type was: ERROR_MESSAGE_STATE
The ABAP call stack was:
Function: /SAPAPO/MC_PERIODE_ZUM_DATUM of program /SAPAPO/SAPLMCP2
Function: /SAPAPO/MC_PERDY_GET of program /SAPAPO/SAPLMCP2
Function: /SAPAPO/DM_GET_COLS of program /SAPAPO/SAPLDM_DEMAND_PLANNING
Form: CREATE_COLS_FOR_PERKZ of program /SAPAPO/SAPLOO_TS_DM
Form: GET_COLS_FOR_PERKZ of program /SAPAPO/SAPLOO_TS_DM
Form: CREATE_COLS of program /SAPAPO/SAPLOO_TS_DM
Function: /SAPAPO/TS_DM_GET of program /SAPAPO/SAPLOO_TS_DM
Method: GET_HISTORY_COMBI of program /SAPAPO/CL_DP_SEASON_CONF=====CP
Method: GET_SEASONALITY_COMBI of program
/SAPAPO/CL_DP_SEASON_CONF=====CP
Method: GET_HISTORY of program /SAPAPO/CL_MDL_SEAS_PLM=======CP
I believe it is a program error, but I am wondering if anyone has any suggestions?
Thanks,
MZ

As per SAP, periodicity P is not supported.

Error in reading Livecache in Parallel

Dear All,
        We have a Z program which uses the function module '/SAPAPO/TS_DM_GET' to read the live cache data. In SCM 4.0 the program was working fine when executed in parallel or standalone. But in SCM 7.0 if we execute the same program in parallel it gives dump as below. So please let me know if there any setting needs to done in the planning area for reading the live cache in parallel.
Error Message:
Key already exists
Error for COM routine using application program (return code 6)
Thanks,
Siva.

Hi Siva,
Check your settings under /SAPAPO/SDP_PAR
(both parallel processes and block size)
Regards
R. Senthil Mareeswaran.

Error while creating planned order in product view

I am getting following error when I try to create planned order for a product in a Location manually in product view using /SAPAPO/RRP5.
Error occurred while creating order
Message no. /SAPAPO/RRP251
I checked the product and resource. Everything looks good.
Block is available in the resource WMP1_2041_001 for characteristics specified in planned order.
Product master and PDS look good.
In the planning log, I see the following error message.
Plan explosion failed for product LBRA1050-661 in location 2041
Message no. /SAPAPO/RRP718
I have not found SAP notes for above error.
Can you pl let me know what this is due to?
Thanks,
Srini

Srini,
The message was created as a result of several notes, such as 1582997. There are others.
The implication is that you have an invalid source somewhere in your BOM. Maybe a bad component part, maybe a bad transportation lane, maybe an invalid BOM, or maybe a bad PPM/PDS.
If you can't find the problem using logical troubleshooting steps, have one of your programmers debug. Have him put breakpoints in FM /SAPAPO/RRP_PLORD_CREATE . If you are particularly lucky, you will find a developer that understands German, because all the internal comments in this FM are in German.
Best regards,
DB49

Invalid I/O node config error while passing project reservations to APO

Guys,
I had created a Project with WBS Element, Network & Internal activity in ECC Project Systems. This data was ciffed and seen in APO without any issue.
Upon creating a Material component, as a reservation, under network activity in PS and releasing it, there is an error in the APO side log(SLG1) as shown below.
Source system: xyz, user: abc transaction:CJ20N function module:/SAPAPO/CIF_PRJ_INBOUND
-----Error start--
New order (warning)
Error in activity of operation 0010 order 4001740(warning)
Invalid I/O node configuration (error)- Message no. /SAPAPO/OM_ERROR258
Diagnosis-The I/O node cannot be scheduled using the value combination specified.
--Error end--
Error while processing project order: 000001234- (error)- Message no. /SAPAPO/PRJ003
------Log Information
The registered objects of the queue are marked as faulty - Message no. /SAPAPO/CIF_ERRHDLG604
CIF error handling activated - Message no. /SAPAPO/CIF_ERRHDLG504
End of processing registered for RFC 00000001 of the LUW with ID xxx
Message no. /SAPAPO/CIF_ERRHDLG605
checked the APO post processing and manaully triggered the transfer of selected order . even then order reservation wasn't pushed to APO.
Would appreciate if any one can provide with info on why this error is being produced and ways to resolve it!!!
Thanks

please check if you have any issues under network activity..if you could not find any please try to debug the failed queue with the help of your Abap counterpart. here is the process
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d0d1265d-db32-2b10-79ba-ccf6fe2c161d

Runtime Errors         CONVT_NO_NUMBER

Hi Experts,
we got a runtime error in program CONVT_NO_NUMBER ,here are the details of the error ,could not find a sap note on this.
same program is ran with same variant recently but got this runtime error today ,please suggest how to correct this
The termination occurred in the ABAP program "/SAPAPO/SAPLMSDP_CAP" in
"PROD_LIST_RESULT".
The main program was "/SAPAPO/RMSDPCAP ".
The termination occurred in line 1078 of the source code of the (Include)
program "/SAPAPO/LMSDP_CAPF02"
of the source code of program "/SAPAPO/LMSDP_CAPF02" (when calling the editor
10780).
The program "/SAPAPO/SAPLMSDP_CAP" was started as a background job.
Processing was terminated because the exception "CX_SY_CONVERSION_NO_NUMBER"
occurred in the
procedure "PROD_LIST_RESULT" "(FORM)" but was not handled locally, not declared
in the
RAISING clause of the procedure.
The procedure is in the program "/SAPAPO/SAPLMSDP_CAP ". Its source code starts
in line 1001
of the (Include) program "/SAPAPO/LMSDP_CAPF02 ".
Error analysis
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_CONVERSION_NO_NUMBER',
     was neither
    caught nor passed along using a RAISING clause, in the procedure
     "PROD_LIST_RESULT" "(FORM)"
    Since the caller of the procedure could not have expected this exception
     to occur, the running program was terminated.
    The reason for the exception is:
    The program attempted to interpret the value "*08" as a number, but
    since the value contravenes the rules for correct number formats,
    this was not possible.
Thanks in Advance.
Edited by: Brahamananda reddy Arikatla on Aug 23, 2010 7:05 AM

Hi
"*08
1. I think this is some chararater that you have declared and the value is shooting to bypass the length. It is not able to handle the
value and a * is in place.
declare with appropriate data type by int or quan.. or char(xx) length to handle this.
SInce this is dealing with some background job its not clear loading of the data type . But u you can place the breakpoint at the code of line mentioned and observe the value .
2.
if u r doing a char comparision then see that RHS is in quotes .
Ex : ZB eq 11 will go for a dump
ZB eq '11' - > no dump
BR,
Vijay

APO DP: Message no. /SAPAPO/TSM241

Hi
In planning book when we tried to plan for some characteristics we get this error.
"Inconsistent state: No. of charctstc combinations <-> no. of LC anchors
Message no. /SAPAPO/TSM241"
I tried to solve the problem using programs
1. /SAPAPO/TS_LCM_PLOB_DELTA_SYNC
2. re-initializing planning area
3. /SAPAPO/TS_LCM_CONS_CHECK
4. /SAPAPO/TS_LCM_REORG
Still not solved, please share if you have any idea how else it can be solved, it will be grateful.
Note: Only some characteristics are not able to be planned, i.e. we are able to plan for existing selections Id's.
Please share your thoughts
Thanks
Venkatesh

Hi Tibor
The client has only DP, so SNP master data is irrelevant, I tried re-initializing the planning area. When I run the report /SAPAPO/TS_LCM_CONS_CHECK, the error I am getting is "Characteristics combinations inconsistent
Message no. /SAPAPO/TSM517".
Aparna, I did enable the repair option.
Thanks for your interest!
Venkatesh

Live cache COM routine ended with own error code 38

Hi Experts,
the process chain got failed and it is showing the error as error 38.when we are doing the analysis the error itself coming in the extractin level and it is showing as errors in the source system and not more than that. Please gimme some solution how to solve it.

Hello,
This is the object not found error for /SAPAPO/OM_PEGAREA
These error codes are generated if you try to access or manipulate an
object that cannot be found in the live cache (any more).
Normally this means that there is no object with the key (GUID) provided
by the ABAP.
Please execute the transaction /SAPAPO/OM17 inorder to resolve the
inconsistencies regarding missing pegkeys.
Best Regards
Barry

Error while performing Master Data transfer from SAPR/3- ECC5.0 to SCM4.1

Hi all,
Am getting an error while transfering Master data from SAP R/3 system ECC5.0 to SCM4.1 through Core Interface (CIF).
After creating an Integration model and while activating the same am getting the following error,
" System: SCMCLNT800 User: SMART03 06/17/2006 13:32:14
Function: /SAPAPO/CIF_LOC_INBOUND
Text:Error in address data for location DC2000/ECC800 "
Could anyone provide me how to fix this?.
Regards
Bharanidharan

Hi Veera,
Am sorry for the delayed response. Well am using XI as integration engine for transfer of transactional data from R/3 to SCM4.1. I resolved this issue which was because of master data problem. Thanks for your input.
Regards
Bharanidharan

The error "-10709" occurred in the current database connection "LEA"

Hi,
I've Updated forecast and I have the followoing error message,
(/SAPAPO/MMSDP)
Database error text........: "Connection failed (RTE:protocol error)"
Database error code........: "-10709"
Triggering SQL statement...: "EXECUTE PROCEDURE LCK_DEQUEUE_OWNER"
Internal call code.........: "[DBDS/NEW DSQL]"
Please check the entries in the system log (Transaction SM21).
the error "-10709" occurred in the current database connection "LEA"
just after it was ok .
I knwo LEA is the lock table to the liveache, is there parametes tied to the lock (like R/3 enque/table...?)
Does someone have an idea of this issue (which happened regulary for the first time this morning, we're SCM 5.0)
Best Regards,
John

John,
It looks like a support pack issue.
Check this post, maybe it will help:
the error "-10401" occurred in the current database connection "LCA"
Let me know if this was helpful.
Abhi

Upgrade SCM 4.1 - 7.0 issues

Dear All,
We have just Upgraded our Devolopment System from SCM 4.1 to 7.0....
After that we have run " RS_BW_POST_MIGRATION" for activating the BI objects...
After that we run the MPOS and Planning area Consistency Check...
When i load the data in the pllanning book we are getting the below error...
"Internal Error/sapapo/SCMB_PSTRU_TEMPL=>RAISE_EXCEPTION_FRO"
"Error reading data - Planning book Can not processed further"
Plz help us to resolve the same...
Thanks in advance,,,
Regards,
Rajesh Patil

Hi,
We have solved the issue...
it is happened becasue of Agreegates , we have deleted the agregates and created it again and done the con check...
now it is working fine
Regards,
Rajesh Patil

Functions not possible because of transfer to OLTP system

Hi gurus,
when i am doing /SAPAPO/VERMER, getting error like "functions not possible because of transfer to OLTP system" can you suggest me and elaboratly.
Thx
moon

turn off transfer to OLTP for both SNP and Deployment via SDP110.

/SAPAPO/TS_DM_GET = LC-ERROR 40020

Similar Messages

Maybe you are looking for