/SAPAPO/OM_REORG_DAILY error

Hi folks,
I have an issue with transaction LCA03 in SCM 5.0. It shows a red light at "Critical logging event" --> ReorgDaily. When I check the log, I can see that the background job /SAPAPO/OM_REORG_DAILY is terminating every night with the following error message:
"No planning version active in current client" and then "Job cancelled after system exception ERROR_MESSAGE."
We work in client 100. In client 100, I checked transaction /SAPAPO/MVM and there is planning version 000 active.
When I check SM36 --> standard jobs, there are several background jobs (standard jobs) scheduled and running, but all seem to run in Client 000. One of these is /SAPAPO/OM_REORG_DAILY.
How can I get this fixed? Do I have to delete the standard job /SAPAPO/OM_REORG_DAILY and create it again, in client 100? What about the other jobs, that are running fine in Client 000 (/SAPAPO/OM_DELETE_OLD_SIMSESS, SLCA_LCK_SYNCHOWNERS)? Do they make sense there? Or does it not matter, in which client these jobs run?
Sorry, but the client concept is new to me and I couldn't find info on this with regard to these jobs.
Thank you for helping, Matthias

Hi, thanks for your answers!
I first checked the job log in transaction SM36 for /SAPAPO/OM_REORG_DAILY. From there comes the error message I provided.
/SAPAPO/OM11 shows all occurences for /SAPAPO/OM_REORG_DAILY, they all failed and only ran in client 000. Also, DelOldRegs (/SAPAPO/OM_DELETE_OLD_SIMSESS) are shown with a yellow light, all are shown for client 000 only.
I now ran the job /SAPAPO/OM_REORG_DAILY manually on client 100 from transaction SE38.
It first shows an information window which says: /sapapo/om_reorg_daily Scheduled Daily: 100 --> See /sapapo/om13.
Then a new Informtion windows with: Analysis of LC and LCA objects shows errors.
If I go again to transaction LCA03, there are only two red traffic lights:
-/sapapo/om_reorg_daily 100 (I think I just have to schedule the job for client 100 here daily, since now it is only scheduled in client 000)
-Critical logging event: This shows the error, that /SAPAPO/OM_REORG_DAILY failed in the last nights (when it was running in client 000. It failed with the error message given earlier.)
What to do? Just schedule the job for client 100 and delelte the standard job for client 000? Because I cannot schedule two standard jobs with the same program to be executed.
Thanks again, Matthias
Message was edited by:
Matthias Sartor

Similar Messages

/SAPAPO/OM_ORDER_CHANGE: Error

Hello Experts,
I am trying to update planned order components qty, but i am getting LC_APPL_ERROR                = 3.
Can any one help me on this , whether i passed required parameters or not.
CALL FUNCTION '/SAPAPO/OM_ORDER_CHANGE'
    EXPORTING
      IS_GEN_PARAMS                = r_gen_params
      IV_SIMSESSION                = w_simsession
      IS_ATP_INFO                  = T_ATP_INFO
      IT_ORDER_METHOD              = T_ORD_METHOD
      IT_ORDKEYS                   = T_ORDKEYS
IT_ORDMAPS                   =
    IT_ORDERS                    = t_orders1
    IT_ACTIVITIES                = T_ACTIVITIES
    IT_MODE                      = T_MODES
    IT_CAP_REQS                  = T_CAP_REQS
IT_POSITIONS                 =
   IT_INPUTS                    = T_INPUTS
    IT_OUTPUTS                   = T_OUTDATA
IT_PRODFLOW                  =
IT_INTERN_CONSTRAINTS        =
IT_EXTERN_CONSTRAINTS        =
    IS_CONTROLPARAMETERS         = is_c
    IT_SCHED_PARAMS              = is_p_t
IT_RES_PLAN_INTERVALLS       =
IT_CHARACT_REQ_INPNODE       =
IT_CHARACT_VAL_OUTNODE       =
IT_CHARACT_VAL_ACTS          =
    IS_GET_CHANGED_OPTIONS       = is_g
IV_GET_ALL_OBJECTS           = GC_FALSE
IS_EXCLUDE_FIELDS            =
IMPORTING
ET_RC                         = t_rc1
ET_CHANGED_ORDERS             = T_CHANGED_ORDERS
ET_CHANGED_CAP_REQS           = T_CHANGED_CAP_REQS
ET_CHANGED_IO_NODES           = T_CHANGED_IO_NODES
ET_CHANGED_IO_PP_NODES        = T_CHANGED_IO_PP_NODES
ET_CHANGED_PEGIDS             = T_CHANGED_PEGIDS
ET_DELETED_FIX_PEGGING        = T_DELETED_FIX_PEGGING
ET_SCHED_FAILURES             = T_SCHED_FAILURES
ET_SCHED_LOG                  = T_SCHED_LOG
EXCEPTIONS
LC_CONNECT_FAILED            = 1
LC_COM_ERROR                 = 2
LC_APPL_ERROR                = 3
OTHERS                       = 4
Thanks
Have a good weekend
Cris

Hi,
Thanks for your reply, Yes I have passed correctly gen_param and simsession, still i am getting error lc_appl error and as you said et_rc is having error code 34.
I am passing 24 records and i am trying to change one of the record with method type 'C'.
Please help me out...
Thanks
Cris

Program: /SAPAPO/CLP_PBEXCHANGE; error: Selection Cannot be Converted

Hello,
when running program /SAPAPO/CLP_PBEXCHANGE I am getting the error Selection Cannot be Converted
Message no. APO_BAPI408 ...
I assume that this was caused by a SP upgrade of the sending system (APO 50 SP13) ... as before we haven't had any issue in this area.
Does anybody have any idea ... what might have changed or whether somewhere a parameter is missing.
Thanks in advance.
Regards,
Andi

REPORT Z_1480178.
data : lt_secresid     TYPE /sapapo/om_resid_tab,
      lt_sec_res      TYPE /sapapo/pt_secres_tab.
CALL FUNCTION '/SAPAPO/RRP_PT_RES_GET_SECRES'
EXPORTING
    iv_simid   = '000'
    it_resid   = 'GxAp7t6MCllX00002X5EvG'
IMPORTING
    et_sec_res = lt_sec_res.
move-corresponding lt_sec_res to lt_secresid.
changed the code as follows...
but still get the error lt_sec_res is not a structure or internal table with header line

Resolution of /SAPAPO/TSM207 errors in APO SNP planning

I am using APO V5.1 connected to a SAP ECC system.
When I CIF across a new product to APO and use it for the first time in SNP interactive planning I get error /SAPAPO/TSM207, because of missing time series objects.
The SAP recommendation in the error help text suggests to either re initialise the planning area, or to use pgm /SAPAPO/TS_LCM_PLOB_DELTA_SYNC. But I can only resolve the problem via the former approach (ie to re initialise the planning area). The use of /SAPAPO/TS_LCM_PLOB_DELTA_SYNC does not resolve the problem.
Is this expected behaviour?
What exactly is /SAPAPO/TS_LCM_PLOB_DELTA_SYNC designed to do?
If I look at help.sap.com for SCM 7 I see mention of a transaction /SAPAPO/TSINIT, which can be used as a 'delta' planning area re initialisation. But I do not see this transaction in APO V5.1 - so is this a new transaction in APO 7?
Thanks for any advice on this...

Hi,
Please refer to he note 402046 which explains this.Eventhough the note validity is not for your release ,but the conent of
note is still valid to all releases.
Regards,
Sunitha

SCM WP trace file error message

Hi,
We are getting the below error in our work process trace files for our SCM 5.1 system
Tue Dec 30 17:35:51 2008
***LOG Q0I=> NiPGetHostByName: hostname 'OPTSERVER' not found: gethostbyname [niuxi.c 1470]
At same time, we have system log entries as below:
19:07:34 BTC 031 009 APOADMIN                Q0 I Operating system call gethostbyname failed (error no. 0 )
Documentation for system log message Q0 I :
The specified operating system call was returned with an error.
For communication calls (receive, send, etc) often the cause of errors
are network problems.
It could also be a configuration problem at operating system level.
(file cannot be opened, no space in the file system etc.).
Does anyone know about this?? The RFC connections between APO server and Optimizer server are working fine and there is no issue. However, for any dialog/background process we are getting the error above. Please suggest.
Regards,
Sandeep.

Hi Senthil,
Thanks for your reply. As in the note 388193 that you have mentioned job /SAPAPO/OM_REORG_DAILY is executed daily in our system and there does not seem to be any issue with optimizer installation as optimizer is working fine and there is no connection problem with scm system.
However the SM21 errors keeps coming.
13:48:15 BTC 031 009 APOADMIN                Q0 I Operating system call gethostbyname failed (error no. 0 )
13:54:38 BTC 031 009 APOADMIN                Q0 I Operating system call gethostbyname failed (error no. 0 )
14:01:24 BTC 031 009 APOADMIN                Q0 I Operating system call gethostbyname failed (error no. 0 )
14:07:59 BTC 031 009 APOADMIN                Q0 I Operating system call gethostbyname failed (error no. 0 )
Regards,
Sandeep

Critical Logging Event Red ( /sapapo/om13)

Hello,
In /sapapo/om13--->checks, we can see critical logging event is red.
I logging section, message are
1> error in /SAPAPO/OM_REORG_DAILY (date 16.10.2007)
2> Planning version was created.(date 13.10.2007)
3> ATP time series active(date 12.10.2007)
4> error OM13 ( date 10.10.2007)
we want to turn this critical loging event to green.
Should we delete livecache application logs via /sapapo/om12 or is there any other way to turn it into green.
As far as I know, /sapapo/OM13->Logging contains last entries from logging log.(/sapapo/om13->Logging----
>Logging Log .)But Last entries means how many? any parameter to do this?(Just a query)
Can somebody please help me turning critical event log to green.
Please feel free to add thougts.Thanks.
Regards,
Tushar
Message was edited by:
        Tushar Chavan

Hello Tushar,
You could turn critical event log to green if you will not have the Critical Logging Events for the last 5 days.
For example, OM13 could Shows the Critical Logging Event as Yellow. You could run the transaction /sapapo/om11 or /sapapo/OM13 -> tab 'logging' to review the critical logging events, which have occurred recently on your system. If , for example, the 'Old transactional simulations deleted' by the //om_ reorg_daily report or corrections of the inconsistencies in /sapapo/om17 were done on your system, the events will be listed in the 'logging' section. And the OM13 Shows Critical Logging Event (Yellow) to pay attention for you to check 'logging' for more details.
Information to the reason of the yellow light can be found via the blue info button.
For example on the my local system in the transaction /sapapo/om13 -Checks -> 'Critical Logging Event' shows the yellow light. Before the yellow light you will see the last Event to be checked in "Logging".
The next info was displayed, when I was clicked blue info button:
At least one critical logging event has occurred recently. See "Logging"
in the Writer for more details.
And when will go to the transaction /sapapo/om13 -> logging ( or you could use the transaction /sapapo/om11 ), you will see "Logging" list of events for more details.
-> In your case if you have red light for the Critical Logging Event, you need to correct the problem with the error in "Logging" event.
-> You should not delete the "Logging" events on your system to get the green light
in //om13->checks, "Logging" events needed for the further analysis of the LCA problems on your system, if you have them or will have in future.
-> If the error in /SAPAPO/OM_REORG_DAILY occurred, it has to be checked/corrected. And if the job will run without errors the problem is gone. See the SAP note 800927.
->"2> Planning version was created.(date 13.10.2007)
      3> ATP time series active(date 12.10.2007)"
    Please review the SAP note: 792286 Repairing/activating ATP time series.
    Are you running the system upgrade?
< If yes, then the note 792286 is NOT needed to be applied or pay attention.
During the upgrade the step to activate the ATP time series is before to load the master data to liveCache in the target release. And during the load master data the planning versions were loaded < created > to the liveCache from APO database. >
    What is the version of your system?
-> I recommend you to create the OSS message to the component 'BC-DB-LCA'
    to check the critical LCA events on your system.
Thank you and best regards, Natalia Khlopina

Error while creating manual planned order in apo

Dear expert
While I am creating manual planned order i am getting error as message /sapapo/rrp251
Every thing is correct BOM and PV's no error after consistency check and it getting succesfully transffered to APO and it is also visible in APO
But while creating manual planned orders planned order are not getting generated I am using BLock planning with PPDS
Please help How to resolve it
Regards
Virender

Hi
The error message /SAPAPO/RRP251 - Error occurred while creating order means While creating an order, the system encountered problems, such as, for example, no available components or components that are available late, orders that could not be scheduled, and so on.
I think system attempted to solve the availability problems by using alternative procurement options. This was not successful. The order could not be created. Check the exceptional situations in the planning protocol, under Goto -> Planning log, and deal with the causes of the exceptional situations if this is possible or necessary.
Thanks
Amol

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

Report /SAPAPO/OM_REORG_ATP frequency

Hi,
We are using GATP for order confirmations, is it recommended to leave the /SAPAPO/OM_REORG_ATP report running frequently? How frequently?
Thanks a lot

Dear,
You can schedule it daily.
However, if you have already scheduled report /SAPAPO/OM_REORG_DAILY, then report /SAPAPO/OM_REORG_ATP is not necessary as the reorganization of the ATP time series is already a part of the report
/SAPAPO/OM_REORG_DAILY.
Claire

/SAPAPO/OM_LCAALERTS

Hi folks,
we run SCM 5.00 (Level 0010) with LiveCache (2005_700, Level 0005).
We already scheduled /SAPAPO/OM_REORG_DAILY and /SAPAPO/OM_DELETE_OLD_SIMSESS as regularily running background jobs in the only liveCache relevant client 100. Do we have to schedule the job /SAPAPO/OM_LCAALERTS for this client as well, or is it obsolete for our version?
Thanks in advance, Matthias

Hi Raghu,
thanks! The Job /SAPAPO/OM_LCAALERTS is currently scheduled and running in client 000 - which is not LiveCache relevant. Does it really matter in which client this job runs - is it client-dependent? LCA03 shows no red lights, but I don't know if it makes sense to let the job run in client 000. Please help...
Thanks,
Matthias
Message was edited by:
Matthias Sartor

ATP Tree Structure error -MATP

Hi Experts,
I am testing MATP with RBA, I could not see the planned orders in ATP tree structure once I saved the sales order in ECC.
Scenario -
I have product A (header) and A1 & A2 are the components of product A (Header)
I have stock on component A1 - 100 & component A2 - 100, STOCK on header material A -0
I have created sales order for header material A - customer requested quantity 201.
THEN system is confirming the sales order only for 100 qty because the components A1 & A2 stock available only 100.
I can see the dependent demand in rrp3 for Components A1 and A2
I can see the planned order in rrp3 for header material A
BUT I could not see any planned orders either in /SAPAPO/RRP_ATP2PPDS - Conversion ATP Tree Structures -> Production Planning OR
/SAPAPO/ATREE_DSP - ATP Tree Structures
below is the error message I am getting in the transaction -/SAPAPO/RRP_ATP2PPDS - Conversion ATP Tree Structure
What could be the wrong in the above case.. can you please suggest.. Advance thanks for your information.

Hi Experts,
Can someone please help in the below ATP Tree Structure error-
I am not able to covert the sales orders from the ATP Tree Structure
The error message as below - Transaction - /SAPAPO/RRP_ATP2PPDS - Conversion ATP Tree Structures -> Production Planning
Can you just help me what could be the wrong in the setting and how to make the sales orders to be converted from this transaction /SAPAPO/RRP_ATP2PPDS
Error appears when I convert the sales orders from the ATP Tree Structure as below -
''The successor reqmts groups of the ATP tree structure were not converted''
Conversion canceled with error
ATP tree for sales order xxxx, item xx could not be converted
Thanks,

Releasing a proocution order get an error

Hi,
When I want to release a production order, it does not let me release it because of a SAPAPO/ATP error (E:/SAPAPO/ATP: 035 011 PP).
What can it be?
Thank you!

Hi,
During the production order release material availability check is carried out automatically.This can be done in ECC by defining
Checking group, Checking rule, Checking Scope and Checking Control in the Shop floor control parameters in SPRO.
Request you to check in the checking control defined for the Order type and Plant for the Business function 2( Check availabilty during order release) under Material availabilty for Release material " No release if there are missing parts " is defined.
With this setting if there is any material shortage for the components then Prodn order will not get released.
Thanks,
nandha

Client error in OM13

Hi,
wrt the subject line. waht does the message mean.
the planning book (DP only) is not being read and gives this msg while loading a selection
Internal error /SAPAPO/OM_TS_CHANGE_TG
Error reading data: planning book cannot be processed.
and thats when i traced down to OM13 assuming this is the problem. On the check tab of OM13, the field client error is RED
To reassure myself i have done the initialization of planning area, deactivation and activation of pos and recreation of cvc's, ts cons checks, om17, tsreorg, pstru etc, everything is consistent. no errors.
planning books is still not read. only DP planning book, SNP books are fine
Regards,
Lok

Thanks Keiji,
I discovered this after wasting a full day on misleading sap messages that led me to lot of admin jobs on apo and live cache.
yes. this was a case of non-existent time bucket profile in data view.
full 10 marks.
Regards,
Loknath

SAP internal error

Hi All,
The user is getting the error while using the planning book.
internal error -- /SAPAPO/OM_TS_CHANGE_TG
Error reading data - Planning book cannot be processed further.
What shall I do ?
Please help.
Thanks in advance,
Prabhat.

Pls run consistency check for Live cache from transaction /sapapo/om17.
This should solve the problem.
Thanks
Mani Suresh

SAPGui 7.20 Patch 6 - sapbarc.ocx - Error

APO users report an activex error when using /SAPAPO/CDPSO
Error is: Illegal objecttype in BarifEstimateChartforObject
I noted that the file in the Front End SAPGUI folder: sapbarc.ocx is changed with Patch 6
Previously we were at Patch 3.
Anyone else?
Bob H
Edited by: Bob Held on May 6, 2011 10:50 PM

Sven,
I opened an OSS Message as you requested. I was give the following response:
Dear Customer,
Many thanks for the information provided. Could you please kindly check
SAP note:
1584140 Barchart: BARC Error on moving timeline phantom
Let us know if this issue still exists after you applied this note.
Best regards
William
Active Global Support - Technology
SAP Asia Pacific(GMT+8)
SAP NOTE 1584140 Simply documents it as a known issue and states it will be fixed with a future patch release. No workaround is provided thus there is 'Nothing' to apply with this note.
I really would like to know is it okay to simply replace the Patch 6 version of sapbarc.ocx with the one from Patch 3 which does not generate the error. I have four users testing with this configuration and no problems reported.
Thank you,
Bob H

/SAPAPO/OM_REORG_DAILY error

Similar Messages

Maybe you are looking for