/SAPAPO/RESLCT

Hi,
When I go to product view for a location product, when I click on periods tab, I get the message :
===
"Time stream from resource XXXXXX not valid for total display period"
Time stream from resource WHTST5_0158_001 not valid for total display period
Message no. /SAPAPO/RRP_PT055
Diagnosis
The time stream for resource XXXXX is not valid for the general display period. This can cause the display of the time buckets profile for this resource in the product planning table to be inaccurate.
Procedure
Update the resource time stream. To do this, see note 449452.
===
When I looked at the note 449452, it says in table /SAPAPO/RESLCT, there should be only one entry for 30 days in past and 180 in future.
But when I looked at the table in our system, it has two entries. Is this an inconsistency?
What does the error message mean? I looked at the validity in period for the resource and it is 30 days in past and 180 in future. I also ran the report /SAPAPO/CRES_CREATE_LC_RES but it doesnot help.
Any suggestions please?

ok..looks like the report did not work.
Do one more thing. Go in to /SAPAPO/RES01 transaction and and make sure you pick up the resource with the planning version in edit mode. Once you bring up the master data screen for resource, pick up the line item by selecting the row and then clicking on Capacity Profile button above the table. There is a red and white button called "All Bucket profiles". Click on that icon and save the resource.
let us know if it works.

Similar Messages

Table /SAPAPO/RES_HEAD update?

Hi All,
There is an inconsistancy between the values shown in the Resource Master and those in the table /SAPAPO/RES_HEAD.
What could be the possible reasons for the same? Does the table refresh from the parent structure periodically? What do I do if I need the updated values in /SAPAPO/RES_HEAD???
Warm Regards,
Shiva

Shiva,
Do you mean the below fileds not matching?
LC DAYS MINUS
LC DAYS PLUS
Is yes:
These values are stored in the table: /sapapo/reslct
the values in CFC9 defines how many time slots CIF transfers to APO
for each resource with external time stream. If there is nothing
defined the system uses -30...+600 as default values.
But the length of the time stream of the resource itself has to be
defined in the resource itself. Otherwise the system uses a default
value defined in database table /SAPAPO/RESLCT.
If you delete them and create yor own entry this should work as
expected for new resources.
Since this values are created while you tranfer the resource first time.,the values are taken from CFC9 settings.
If my understanding is wrong for your problem , let me know the exact field value you have the inconsistency.
-sundar

Message /SAPAPO/SDP_PAR023: "Some CVCs cannot be processed in block..."

Hi,
We are using SAP SCM release 5.1, the component Demand Planning. We are running macros in background jobs, e.g. a macro that populates a key figure by summarizing other key figures etc. We are using parallel processing, configured based on recommendation from SAP. When the number of CVCs to be processed by the macros becomes very high (we are processing ~300.000 CVCs at the moment), we get the following message in the job log in SM37:
"Some CVCs cannot be processed in block 2 ", message number /SAPAPO/SDP_PAR023. Obviously the block number varies, and in our case we have had the above message for up to 19 blocks. Users have spotted CVC's that were not updated by the background job, but we don't have a specific list of the CVCs that were not processed.
OSS notes mentioning this behaviour:
Note 1282811 - Error processing 1 CVC, terminates the Parallel Profile
Note 1501424 - DP Job with parallel processing - job status message
Note 1494099 - DP Job with parallel processing - job status
The question below is only to those who have encountered the same message in a DP background job:
Did you find a log of the CVCs that were not processed, and what did you do to overcome the problem?
Thanks in advance!
Kind regards,
Geir Kronkvist

Hi Rico,
Thanks for your reply! The spool consists of 23.145 pages so I looked for the word "Lock" using the "Find in request" in the "Spool request" menu. The searched found two entries where there was a message stating that a CVC was locked. It must be noted that no users are logged on while our background job is running, and there are no other processes (background or dialog) running in parallel. When checking transaction SM12 prior to running the job, there are no locks in the system.
Our job schedule consists of a nightly process chain transferring data from BI to liveCache, and a monthly job that prepares historical data and calculates the forecast. We are now running the monthly job.
Is it possible that the parallel processing may cause the locking by itself?
Kind regards,
Geir Kronkvist

BADI /SAPAPO/AM_ALERTLIST - How to fill values in new field catalogue

Hi,
I need some help for passing values into the field Catalog of an ALERT Monitor.
The requirement is to add new fields in the ALERT Monitor and then populate them with values form the PRODUCT view.
I have implemented method MODIFY_ALERTLIST of BADI /SAPAPO/AM_ALERTLIST. I am able to add the new columns but I am unable to add the values. Actually while debugging i found that even though the NEW values are going into the table T_ALERTS, but the space between the New Added values and the original value is HUGE. Therefore when the Field Catalog is displayed in the Alert Monitor, the NEW Values are not shown.
I am attaching my Code
DATA: l_table_ref TYPE REF TO data,
l_table_ref_1 TYPE REF TO data,
l_fieldcat_str TYPE /sapapo/am_aot_fieldcat_str,
ls_fieldcat TYPE LINE OF lvc_t_fcat,
ls_t_fieldcat LIKE LINE OF t_fieldcat,
l_alert_str TYPE LINE OF /sapapo/alert_tab,
l_str_ref TYPE REF TO data,
l_str_ref_1 TYPE REF TO data.
FIELD-SYMBOLS: <aot_tab> TYPE STANDARD TABLE,
<aot_tab_1> TYPE STANDARD TABLE,
<alert_str> TYPE /sapapo/alert_str,
<aot_str> TYPE ANY,
<alert_str1> TYPE c,
<alert_str_uc> TYPE c.
FIELD-SYMBOLS: <zat103> TYPE c. "ANY.
DATA : l_col_pos TYPE i,
gv_entries TYPE i,
xlength TYPE i.
FIELD-SYMBOLS : <info> TYPE ANY,
                  <aot_str1> TYPE ANY.
DATA olen1 TYPE i.
DATA: t_pegid TYPE STANDARD TABLE OF /sapapo/amopegid_tab,
        t_ordid TYPE STANDARD TABLE OF /sapapo/amoordid_tab.
CLEAR: l_alert_str,
    l_table_ref ,
    l_table_ref_1 ,
    l_fieldcat_str ,
    ls_fieldcat ,
    ls_t_fieldcat ,
    l_str_ref .
*Add new column
READ TABLE t_fieldcat INTO ls_t_fieldcat INDEX 1.
DATA: x1 TYPE lvc_t_fcat,
       y1 LIKE LINE OF x1.
x1 = ls_t_fieldcat-fieldcat.
LOOP AT x1 INTO y1 WHERE reptext NE space.
    CHECK y1-fieldname NE 'DELIVERY_DATE'.
    xlength = xlength + y1-intlen.
ENDLOOP.
DESCRIBE TABLE x1 LINES gv_entries.
Appending Delivery Date
ls_fieldcat-col_pos = gv_entries + 1.
ls_fieldcat-fieldname = 'DELIVERY_DATE'.
ls_fieldcat-ifieldname = 'DELIVERY_DATE'.
ls_fieldcat-tabname = '1'.
ls_fieldcat-seltext = 'Delivery Date'.
ls_fieldcat-outputlen = '10'.
ls_fieldcat-rollname = '/SAPAPO/DELIVERY_DATE' . "'DATS'.
ls_fieldcat-domname = '/SAPAPO/CHAR20'."'/SAPAPO/DATUM'.
ls_fieldcat-coltext = 'Delivery Date'.
APPEND ls_fieldcat TO ls_t_fieldcat-fieldcat.
Appending Start Date
ls_fieldcat-col_pos = gv_entries + 2.
ls_fieldcat-fieldname = 'STARTDAT'.
ls_fieldcat-tabname = '1'.
ls_fieldcat-seltext = 'Start Date'.
ls_fieldcat-outputlen = '10'.
ls_fieldcat-rollname = 'DATS'.
ls_fieldcat-domname = '/SAPAPO/DATUM'.
ls_fieldcat-coltext = 'Start Date'.
APPEND ls_fieldcat TO ls_t_fieldcat-fieldcat.
Appending Required Shelf Life Date
ls_fieldcat-col_pos = gv_entries + 3.
ls_fieldcat-fieldname = 'SL_MIN_DAT'.
ls_fieldcat-tabname = '1'.
ls_fieldcat-seltext = 'Req.SL dte'.
ls_fieldcat-outputlen = '10'.
ls_fieldcat-rollname = 'DATS'.
ls_fieldcat-domname = '/SAPAPO/DATUM'.
ls_fieldcat-coltext = 'Req.SL dte'.
APPEND ls_fieldcat TO ls_t_fieldcat-fieldcat.
Appending Shelf Life Date/Required Maximum Shelf life Date
ls_fieldcat-col_pos = gv_entries + 4.
ls_fieldcat-fieldname = 'SL_MAX_DAT'.
ls_fieldcat-tabname = '1'.
ls_fieldcat-seltext = 'SL Date 2'.
ls_fieldcat-outputlen = '10'.
ls_fieldcat-rollname = 'DATS'.
ls_fieldcat-domname = '/SAPAPO/DATUM'.
ls_fieldcat-coltext = 'SL Date 2'.
APPEND ls_fieldcat TO ls_t_fieldcat-fieldcat.
Appending (Availability/Requirements) Date of a Schedule Line
ls_fieldcat-col_pos = gv_entries + 5.
ls_fieldcat-fieldname = 'AVL_REQ_DATE'.
ls_fieldcat-tabname = '1'.
ls_fieldcat-seltext = 'Schedule Date'.
ls_fieldcat-outputlen = '10'.
ls_fieldcat-rollname = 'DATS'.
ls_fieldcat-domname = '/SAPAPO/DATUM'.
ls_fieldcat-coltext = 'Schedule Date'.
APPEND ls_fieldcat TO ls_t_fieldcat-fieldcat.
Appending Req Date/ Shipment end date
ls_fieldcat-col_pos = gv_entries + 6.
ls_fieldcat-fieldname = 'SHIP_MAX_DATE'.
ls_fieldcat-tabname = '1'.
ls_fieldcat-seltext = 'Req Date/ Shipment end date'.
ls_fieldcat-outputlen = '10'.
ls_fieldcat-rollname = 'DATS'.
ls_fieldcat-domname = '/SAPAPO/DATUM'.
ls_fieldcat-coltext = 'Req Date/ Shipment end date'.
APPEND ls_fieldcat TO ls_t_fieldcat-fieldcat.
Appending Expected Grading Date
ls_fieldcat-col_pos = gv_entries + 7.
ls_fieldcat-fieldname = 'GRAD_DATE'.
ls_fieldcat-tabname = '1'.
ls_fieldcat-seltext = 'Expected Grading Date'.
ls_fieldcat-outputlen = '10'.
ls_fieldcat-rollname = 'DATS'.
ls_fieldcat-domname = '/SAPAPO/DATUM'.
ls_fieldcat-coltext = 'Expected Grading Date'.
APPEND ls_fieldcat TO ls_t_fieldcat-fieldcat.
Appending Available Date
ls_fieldcat-col_pos = gv_entries + 8.
ls_fieldcat-fieldname = 'AVAIL_DATE'.
ls_fieldcat-tabname = '1'.
ls_fieldcat-seltext = 'Available Date'.
ls_fieldcat-outputlen = '10'.
ls_fieldcat-rollname = 'DATS'.
ls_fieldcat-domname = '/SAPAPO/DATUM'.
ls_fieldcat-coltext = 'Available Date'.
APPEND ls_fieldcat TO ls_t_fieldcat-fieldcat.
MODIFY TABLE t_fieldcat FROM ls_t_fieldcat.
DATA lvc_t_fcat TYPE lvc_t_fcat.
*CODE FOR ADDING THE NEW VALUES*
ASSIGN Alert Structure to Field Symbols for Unicode
ASSIGN COMPONENT 0 OF STRUCTURE l_alert_str
                     TO            <alert_str>           CASTING.
CALL METHOD cl_alv_table_create=>create_dynamic_table
    EXPORTING
      it_fieldcatalog = ls_t_fieldcat-fieldcat
    IMPORTING
      ep_table        = l_table_ref.
*assign dynamic structure
ASSIGN l_table_ref->* TO <aot_tab>.
CREATE DATA l_str_ref LIKE LINE OF <aot_tab>.
ASSIGN l_str_ref->* TO <aot_str>.
ASSIGN l_str_ref->* TO <alert_str_uc> CASTING.
LOOP AT t_alerts INTO l_alert_str.
   READ TABLE t_fieldcat WITH KEY aot = l_alert_str-aot
   INTO l_fieldcat_str.
   CALL FUNCTION '/SAPAPO/ATAB_FIELDCAT_GET'
     EXPORTING
       aot        = l_fieldcat_str-aot
       mview      = l_fieldcat_str-mview
     IMPORTING
       table_ref = l_table_ref
       t_fieldcat = lvc_t_fcat.
    ASSIGN l_alert_str TO <alert_str>.
*copy alert to aot-specific structure
    MOVE <alert_str>-info TO <alert_str_uc>.
*Write this code inside the loop
    ASSIGN COMPONENT 'DELIVERY_DATE' OF STRUCTURE <aot_str> TO <zat103>. "CASTING.
    IF sy-subrc = 0.
      CLEAR <zat103>.
*Fetch ur own custom value and move to the field symbol. This
*dynamically populates ur structure.
      <zat103> = '22.11.1999'.
    ENDIF.
    ASSIGN COMPONENT 'STARTDAT' OF STRUCTURE <aot_str> TO <zat103> CASTING.
    IF sy-subrc = 0.
      CLEAR <zat103>.
*Fetch ur own custom value and move to the field symbol. This
*dynamically populates ur structure.
      <zat103> = '22.11.1999'.
    ENDIF.
    ASSIGN COMPONENT 'SL_MIN_DAT' OF STRUCTURE <aot_str> TO <zat103> CASTING.
    IF sy-subrc = 0.
      CLEAR <zat103>.
*Fetch ur own custom value and move to the field symbol. This
*dynamically populates ur structure.
      <zat103> = '22.11.1999'.
    ENDIF.
    ASSIGN COMPONENT 'SL_MAX_DAT' OF STRUCTURE <aot_str> TO <zat103> CASTING.
    IF sy-subrc = 0.
      CLEAR <zat103>.
*Fetch ur own custom value and move to the field symbol. This
*dynamically populates ur structure.
      <zat103> = '22.11.1999'.
    ENDIF.
    ASSIGN COMPONENT 'AVL_REQ_DATE' OF STRUCTURE <aot_str> TO <zat103> CASTING.
    IF sy-subrc = 0.
      CLEAR <zat103>.
*Fetch ur own custom value and move to the field symbol. This
*dynamically populates ur structure.
      <zat103> = '22.11.1999'.
    ENDIF.
    ASSIGN COMPONENT 'SHIP_MAX_DATE' OF STRUCTURE <aot_str> TO <zat103> CASTING.
    IF sy-subrc = 0.
      CLEAR <zat103>.
      <zat103> = '22.11.1999'.
    ENDIF.
    ASSIGN COMPONENT 'GRAD_DATE' OF STRUCTURE <aot_str> TO <zat103> CASTING.
    IF sy-subrc = 0.
      CLEAR <zat103>.
*Fetch ur own custom value and move to the field symbol. This
*dynamically populates ur structure.
      <zat103> = '22.11.1999'.
    ENDIF.
    ASSIGN COMPONENT 'AVAIL_DATE' OF STRUCTURE <aot_str> TO <zat103> CASTING.
    IF sy-subrc = 0.
      CLEAR <zat103>.
*Fetch ur own custom value and move to the field symbol. This
*dynamically populates ur structure.
      <zat103> = '22.11.1999'.
    ENDIF.
    MOVE <alert_str_uc> TO <alert_str>-info.
    MODIFY t_alerts FROM l_alert_str INDEX sy-tabix.
    CLEAR : <alert_str>, <alert_str_uc>.
ENDLOOP.
I have even tried Concatenating Values, with that method even though the NEW Values are available but they do not fall under the correct Column.
PLEASE help me out cos I am really Stuck.
Regards
Abhishek Sahi

Hi,
I need some help for passing values into the field Catalog of an ALERT Monitor.
The requirement is to add new fields in the ALERT Monitor and then populate them with values form the PRODUCT view.
I have implemented method MODIFY_ALERTLIST of BADI /SAPAPO/AM_ALERTLIST. I am able to add the new columns but I am unable to add the values. Actually while debugging i found that even though the NEW values are going into the table T_ALERTS, but the space between the New Added values and the original value is HUGE. Therefore when the Field Catalog is displayed in the Alert Monitor, the NEW Values are not shown.
I am attaching my Code
DATA: l_table_ref TYPE REF TO data,
l_table_ref_1 TYPE REF TO data,
l_fieldcat_str TYPE /sapapo/am_aot_fieldcat_str,
ls_fieldcat TYPE LINE OF lvc_t_fcat,
ls_t_fieldcat LIKE LINE OF t_fieldcat,
l_alert_str TYPE LINE OF /sapapo/alert_tab,
l_str_ref TYPE REF TO data,
l_str_ref_1 TYPE REF TO data.
FIELD-SYMBOLS: <aot_tab> TYPE STANDARD TABLE,
<aot_tab_1> TYPE STANDARD TABLE,
<alert_str> TYPE /sapapo/alert_str,
<aot_str> TYPE ANY,
<alert_str1> TYPE c,
<alert_str_uc> TYPE c.
FIELD-SYMBOLS: <zat103> TYPE c. "ANY.
DATA : l_col_pos TYPE i,
gv_entries TYPE i,
xlength TYPE i.
FIELD-SYMBOLS : <info> TYPE ANY,
                  <aot_str1> TYPE ANY.
DATA olen1 TYPE i.
DATA: t_pegid TYPE STANDARD TABLE OF /sapapo/amopegid_tab,
        t_ordid TYPE STANDARD TABLE OF /sapapo/amoordid_tab.
CLEAR: l_alert_str,
    l_table_ref ,
    l_table_ref_1 ,
    l_fieldcat_str ,
    ls_fieldcat ,
    ls_t_fieldcat ,
    l_str_ref .
*Add new column
READ TABLE t_fieldcat INTO ls_t_fieldcat INDEX 1.
DATA: x1 TYPE lvc_t_fcat,
       y1 LIKE LINE OF x1.
x1 = ls_t_fieldcat-fieldcat.
LOOP AT x1 INTO y1 WHERE reptext NE space.
    CHECK y1-fieldname NE 'DELIVERY_DATE'.
    xlength = xlength + y1-intlen.
ENDLOOP.
DESCRIBE TABLE x1 LINES gv_entries.
Appending Delivery Date
ls_fieldcat-col_pos = gv_entries + 1.
ls_fieldcat-fieldname = 'DELIVERY_DATE'.
ls_fieldcat-ifieldname = 'DELIVERY_DATE'.
ls_fieldcat-tabname = '1'.
ls_fieldcat-seltext = 'Delivery Date'.
ls_fieldcat-outputlen = '10'.
ls_fieldcat-rollname = '/SAPAPO/DELIVERY_DATE' . "'DATS'.
ls_fieldcat-domname = '/SAPAPO/CHAR20'."'/SAPAPO/DATUM'.
ls_fieldcat-coltext = 'Delivery Date'.
APPEND ls_fieldcat TO ls_t_fieldcat-fieldcat.
Appending Start Date
ls_fieldcat-col_pos = gv_entries + 2.
ls_fieldcat-fieldname = 'STARTDAT'.
ls_fieldcat-tabname = '1'.
ls_fieldcat-seltext = 'Start Date'.
ls_fieldcat-outputlen = '10'.
ls_fieldcat-rollname = 'DATS'.
ls_fieldcat-domname = '/SAPAPO/DATUM'.
ls_fieldcat-coltext = 'Start Date'.
APPEND ls_fieldcat TO ls_t_fieldcat-fieldcat.
Appending Required Shelf Life Date
ls_fieldcat-col_pos = gv_entries + 3.
ls_fieldcat-fieldname = 'SL_MIN_DAT'.
ls_fieldcat-tabname = '1'.
ls_fieldcat-seltext = 'Req.SL dte'.
ls_fieldcat-outputlen = '10'.
ls_fieldcat-rollname = 'DATS'.
ls_fieldcat-domname = '/SAPAPO/DATUM'.
ls_fieldcat-coltext = 'Req.SL dte'.
APPEND ls_fieldcat TO ls_t_fieldcat-fieldcat.
Appending Shelf Life Date/Required Maximum Shelf life Date
ls_fieldcat-col_pos = gv_entries + 4.
ls_fieldcat-fieldname = 'SL_MAX_DAT'.
ls_fieldcat-tabname = '1'.
ls_fieldcat-seltext = 'SL Date 2'.
ls_fieldcat-outputlen = '10'.
ls_fieldcat-rollname = 'DATS'.
ls_fieldcat-domname = '/SAPAPO/DATUM'.
ls_fieldcat-coltext = 'SL Date 2'.
APPEND ls_fieldcat TO ls_t_fieldcat-fieldcat.
Appending (Availability/Requirements) Date of a Schedule Line
ls_fieldcat-col_pos = gv_entries + 5.
ls_fieldcat-fieldname = 'AVL_REQ_DATE'.
ls_fieldcat-tabname = '1'.
ls_fieldcat-seltext = 'Schedule Date'.
ls_fieldcat-outputlen = '10'.
ls_fieldcat-rollname = 'DATS'.
ls_fieldcat-domname = '/SAPAPO/DATUM'.
ls_fieldcat-coltext = 'Schedule Date'.
APPEND ls_fieldcat TO ls_t_fieldcat-fieldcat.
Appending Req Date/ Shipment end date
ls_fieldcat-col_pos = gv_entries + 6.
ls_fieldcat-fieldname = 'SHIP_MAX_DATE'.
ls_fieldcat-tabname = '1'.
ls_fieldcat-seltext = 'Req Date/ Shipment end date'.
ls_fieldcat-outputlen = '10'.
ls_fieldcat-rollname = 'DATS'.
ls_fieldcat-domname = '/SAPAPO/DATUM'.
ls_fieldcat-coltext = 'Req Date/ Shipment end date'.
APPEND ls_fieldcat TO ls_t_fieldcat-fieldcat.
Appending Expected Grading Date
ls_fieldcat-col_pos = gv_entries + 7.
ls_fieldcat-fieldname = 'GRAD_DATE'.
ls_fieldcat-tabname = '1'.
ls_fieldcat-seltext = 'Expected Grading Date'.
ls_fieldcat-outputlen = '10'.
ls_fieldcat-rollname = 'DATS'.
ls_fieldcat-domname = '/SAPAPO/DATUM'.
ls_fieldcat-coltext = 'Expected Grading Date'.
APPEND ls_fieldcat TO ls_t_fieldcat-fieldcat.
Appending Available Date
ls_fieldcat-col_pos = gv_entries + 8.
ls_fieldcat-fieldname = 'AVAIL_DATE'.
ls_fieldcat-tabname = '1'.
ls_fieldcat-seltext = 'Available Date'.
ls_fieldcat-outputlen = '10'.
ls_fieldcat-rollname = 'DATS'.
ls_fieldcat-domname = '/SAPAPO/DATUM'.
ls_fieldcat-coltext = 'Available Date'.
APPEND ls_fieldcat TO ls_t_fieldcat-fieldcat.
MODIFY TABLE t_fieldcat FROM ls_t_fieldcat.
DATA lvc_t_fcat TYPE lvc_t_fcat.
*CODE FOR ADDING THE NEW VALUES*
ASSIGN Alert Structure to Field Symbols for Unicode
ASSIGN COMPONENT 0 OF STRUCTURE l_alert_str
                     TO            <alert_str>           CASTING.
CALL METHOD cl_alv_table_create=>create_dynamic_table
    EXPORTING
      it_fieldcatalog = ls_t_fieldcat-fieldcat
    IMPORTING
      ep_table        = l_table_ref.
*assign dynamic structure
ASSIGN l_table_ref->* TO <aot_tab>.
CREATE DATA l_str_ref LIKE LINE OF <aot_tab>.
ASSIGN l_str_ref->* TO <aot_str>.
ASSIGN l_str_ref->* TO <alert_str_uc> CASTING.
LOOP AT t_alerts INTO l_alert_str.
   READ TABLE t_fieldcat WITH KEY aot = l_alert_str-aot
   INTO l_fieldcat_str.
   CALL FUNCTION '/SAPAPO/ATAB_FIELDCAT_GET'
     EXPORTING
       aot        = l_fieldcat_str-aot
       mview      = l_fieldcat_str-mview
     IMPORTING
       table_ref = l_table_ref
       t_fieldcat = lvc_t_fcat.
    ASSIGN l_alert_str TO <alert_str>.
*copy alert to aot-specific structure
    MOVE <alert_str>-info TO <alert_str_uc>.
*Write this code inside the loop
    ASSIGN COMPONENT 'DELIVERY_DATE' OF STRUCTURE <aot_str> TO <zat103>. "CASTING.
    IF sy-subrc = 0.
      CLEAR <zat103>.
*Fetch ur own custom value and move to the field symbol. This
*dynamically populates ur structure.
      <zat103> = '22.11.1999'.
    ENDIF.
    ASSIGN COMPONENT 'STARTDAT' OF STRUCTURE <aot_str> TO <zat103> CASTING.
    IF sy-subrc = 0.
      CLEAR <zat103>.
*Fetch ur own custom value and move to the field symbol. This
*dynamically populates ur structure.
      <zat103> = '22.11.1999'.
    ENDIF.
    ASSIGN COMPONENT 'SL_MIN_DAT' OF STRUCTURE <aot_str> TO <zat103> CASTING.
    IF sy-subrc = 0.
      CLEAR <zat103>.
*Fetch ur own custom value and move to the field symbol. This
*dynamically populates ur structure.
      <zat103> = '22.11.1999'.
    ENDIF.
    ASSIGN COMPONENT 'SL_MAX_DAT' OF STRUCTURE <aot_str> TO <zat103> CASTING.
    IF sy-subrc = 0.
      CLEAR <zat103>.
*Fetch ur own custom value and move to the field symbol. This
*dynamically populates ur structure.
      <zat103> = '22.11.1999'.
    ENDIF.
    ASSIGN COMPONENT 'AVL_REQ_DATE' OF STRUCTURE <aot_str> TO <zat103> CASTING.
    IF sy-subrc = 0.
      CLEAR <zat103>.
*Fetch ur own custom value and move to the field symbol. This
*dynamically populates ur structure.
      <zat103> = '22.11.1999'.
    ENDIF.
    ASSIGN COMPONENT 'SHIP_MAX_DATE' OF STRUCTURE <aot_str> TO <zat103> CASTING.
    IF sy-subrc = 0.
      CLEAR <zat103>.
      <zat103> = '22.11.1999'.
    ENDIF.
    ASSIGN COMPONENT 'GRAD_DATE' OF STRUCTURE <aot_str> TO <zat103> CASTING.
    IF sy-subrc = 0.
      CLEAR <zat103>.
*Fetch ur own custom value and move to the field symbol. This
*dynamically populates ur structure.
      <zat103> = '22.11.1999'.
    ENDIF.
    ASSIGN COMPONENT 'AVAIL_DATE' OF STRUCTURE <aot_str> TO <zat103> CASTING.
    IF sy-subrc = 0.
      CLEAR <zat103>.
*Fetch ur own custom value and move to the field symbol. This
*dynamically populates ur structure.
      <zat103> = '22.11.1999'.
    ENDIF.
    MOVE <alert_str_uc> TO <alert_str>-info.
    MODIFY t_alerts FROM l_alert_str INDEX sy-tabix.
    CLEAR : <alert_str>, <alert_str_uc>.
ENDLOOP.
I have even tried Concatenating Values, with that method even though the NEW Values are available but they do not fall under the correct Column.
PLEASE help me out cos I am really Stuck.
Regards
Abhishek Sahi

/SAPAPO/SDRQCR21 program is not working correctly if we run the program for range of material and plant wise

Hi APO Experts,
In our project, we have received more sales order inconsistencies which is not clearing by CCR program and it is clearing by program /SAPAPO/SDRQCR21 with option as Build Reqmts from Doc. Flow, So We have decided to schedule the background job on daily basis for program /SAPAPO/SDRQCR21 with option as Build Reqmts from Doc. Flow, performing the testing in our quality system and observed the below strange behavior.
When I am running the program /SAPAPO/SDRQCR21 with Range of products and some location range with option as Build Reqmts from Doc. Flow, in Background job. In output it is suggesting to delete one sales order. If I checked that Sales order in ECC, it is for an different location, that is not part of my selection and the order is open. In MD04 the Qty is showing 1 ( as per sales order) but in APO RRP3 view the order qty is showing Zero. I have run the CCR, it is coming in different in content and if I push, the different is not going to APO.
I have tried running the program /SAPAPO/SDRQCR21 with plant which is mentioned in that sales order with option as Build Reqmts from Doc. Flow, in Background job , it is suggesting this sales order under update option correctly.
Can you please help me understand why it is behaving differently like the location is not part of my selection and why it is suggesting the wrong action. And also whether is it advisable to run the /SAPAPO/SDRQCR21 with option as Build Reqmts from Doc. Flow at plant range and material range in background job.
Thanks & Regards,
Sundaram Radhakrishnan

Sundaram,
It sounds to me like the sales document records in the OLTP and in APO were created at different times. This is common in Dev and Qual environments when the systems are commonly created at two different times, and each was a copy of an existing system that contained sales data. The order number you see in //rrp3 is somewhat irrelevant; system generally uses the guid for many activities.
FYI during Dev and Qual refreshes, if you are copying from a production environment that contains data, it is always best to create the OLTP and SCM images at the same time, and to copy them both to the Dev and Qual systems at the same time. If you don't do this, you are faced with the additional tasks associated with getting the copied systems back into synch.
If this is Dev or Qual, I suggest that you just completely wipe out all sales orders in APO and rebuild them using the CIF.
If this is a mature production environment, the only time I have ever seen this issue is due to improperly created CIF enhancements. Speak to your developers to find the root cause, and correct this problem. Then, wipe out all sales orders and rebuild with CIF.
Best Regards,
DB49

Sales orders in /SAPAPO/RRP3

Colleagues,
I have a question regarding the display of sales orders/deliveries within the transaction /SAPAPO/RRP3. We are currently utilising SCM7.0 and my question realtes to the following process.
1. Sales orders are created in ECC and transferred to APO
2. Sales orders are visible within the ransaction /SAPAPO/RRP3, with the quantity and dates being the same as the sales order
3. Deliveries are created from the sales order in ECC and transferred to APO
4. Deliveries are transferred to APO and also visible within the transaction /SAPAPO/RRP same date and quanity.
My quesition is should both the Sales order and delivery be visible within the transaction /SAPAPO/RRP3, the sales order exists with zero quantity and the delivery exists with the correct quntity and date.
I cannot find any key completion erors, or inconsistency messages in any of the logs.
Regards
Paul

Hi ,
In a simple Full Delivery scenario, you will only see a delivery for a sales order in /sapapo/rrp3 and the corresponding Sales Order will not be seen once a delivery is created. But in case you have multiple schedule lines(Delivery Proposal) and partial deliveries are allowed, you will still see the sales order and the delivery.
Let's say you have a Sales Order with confirmation situation like below
                                                                                Req.Qty              Conf Qty              Req.Dt     Conf.Dt
example, Sales Order 100034/0010/001          100                       0                          05/13
               Sales Order 100034/0010/002                                      50                                         05/17
               Sales Order 100034/0010/003                                      50                                         05/18
This will look something like this in RRP3(assuming transit, pick/pack, load equals zero)
05/13        100034/0010/001          100-       0
05/17        100034/0010/002            0         50
05/18        100034/0010/003            0         50
05/13        100034/0010/001                 100-       0
05/17        Delivery#/0010                       0         50
05/18        100034/0010/003                   0         50
If a delivery is created for first confirmed schedule line, you will see the sales order first schedule replaced by the delivery like shown above.
If you don't see this behavior and if you suspect some inconsistencies, try running CCR report with Sales Orders.
Hope it helps.
Regards
Mohan
Edited by: V R Mohan Chunchu on May 14, 2010 7:33 PM

Report "/SAPAPO/TS_BATCH_RUN" ????

Hi All,
Can someone tell why the report "/SAPAPO/TS_BATCH_RUN" is used and what are the prerequisites before we execute this report.??
Regards,
Chandan

Dear Chandan,
with this report the macros are executed in mass processing.
At first you should create an activity (Prerequisite: You have already defined a planning book and a data view) in customizing for Demand Planning.
Afterwards create a planning job in transaction /SAPAPO/MC8D and schedule this planning job in transaction /SAPAPO/MC8G.
In the report /SAPAPO/TS_BATCH_RUN, the program process each step.
I hope these informations can help you further.
Regards,
Tibor

Internal error [/SAPAPO/OM_TS_TGRID_CREATE]

Hi All,
I am using BAPI BAPI_PBSRVAPS_GETDETAIL to read live cache key figure. Its working finr when I execute the program in foreground and returns values but when I try executing this is background it gives me following error in Job Log:-
Internal error [/SAPAPO/OM_TS_TGRID_CREATE].
Can somebody suggest me the root cause and remedy for the same. I try doing planning area initializationa and live cache consistency check also but no luck.
A timely reply will be highly appreciated.
Thanks !
Regards,
Chandan

Hi Chandan,
I checked and found no sap notes similar to scm 4.0. I would suggest to raise a OSS message to SAP so that they will advise on suitable support pack or sap note to implement.
Regards
R. Senthil Mareeswaran.

/SAPAPO/VERSION_COPY job getting cancelled

Hi,
Whenever we schedule the /SAPAPO/VERSION_COPY job for copying versions, it terminate swith the below dump:
TSV_TNEW_BLOCKS_NO_ROLL_MEMORY.
ztta/roll_area is currently set to 6.5 GB, standard recommendation for AIX.
If we increase this, would there be any other parameters that need to be modified.
Pls. help.
Thanks,
Saba.

Hi,
Better create an OSS message.

SNP - Planning Book/Data View not showing up in /SAPAPO/SNP94

Hi All:
I created a planning Book out of a custom SNP planning area. While I could see the Planning Book in the list of Planning Book in the /SAPAPO/SDP94 - Interactive Supply Network Planning (all Books) I could not see the custom planning book in /SAPAPO/SDP94 - Interactive Supply Network Planning (all Books) . I could ony see the SAP supplied PB there. Will SDP94 transaction display only the standard SNP Planning book? How can I make sure that the custom PB is displaed in /SAPAPO/SDP94?
pl. help
Thanks
Ryan

Hi Narayanan,
a couple of simple checks..
can you please check that you have not set a filter critera in the shuffler in planning book/data view?
you can also check if by mistake only a limited number of users are assigned to this planning book and data view ?
else you may want to check note : , 327371
Let me if this helps.
Rgds, Sandeep

APO Planning Calendar error /SAPAPO/CAL404

Hello friends, I am working in the transaction /sapapo/calendar trying to change a Planning Calendar and when I try to Calculate the periods in the view "Calculation Rule" i got a error message saying: Factory calendar TU not found (message number /SAPAPO/CAL404).
I have looked into SCAL transaction and the factory calendar is OK created and valid.
Thank you very much in advance.
Regards.
Ricardo Pereira

Hello Senthil,
Thank you for your help!!
In the Time Stream I have changed the field Factory Calendar for another one for testing and it worked well, I mean I could caculate the periods using another calendar. Comparing both It's all the same there is no difference beteween them.
But when I put the one that I really have to use (the correct one) in the time stream it gives the message Calendar not found. Although it exists and appears in the match code and If I get in the SCAL in APO as well as in R/3 I can edit it.
I have checked the calendar parameters in SCAL and also the time zone including in one of the locations that use this time stream and it's all fine.
Do you have any other idea?
:O(
Thank you very much indeed.
Regards.
Ricardo

Error while creating Order - ERROR S:\SAPAPO\RRP3

Hello all.
We have a planning version called "Planej". The goal of this
version is for forecasting simulation .
A few days ago, starts showing this error:
"S:/SAPAPO/RRP:718 40401681 WAS0
Error occurred while creating order"
I thinking in inconsistency in this version.
I tried /SAPAPO/DELETE_PP_ORDER but don't delete the forecasts.
Someone know another function?
Best Regards

Hi
Try /SAPAPO/RLCDEL

Error while activating POS - Message /SAPAPO/TSM154

Hi,
We have installed SCM 2007 in our landscape recently. We are facing problem in Activating the standard POS objects like 9ADPBAS, 9ASNPBAS etc., we get error as " Planning Object Structure is invalid".
We tried to create a new MPOS in the system, but can not activate the same. We get error message /SAPAPO/TSM154. In Service Marketplace we have a note 1152453 for this kind of error, but while implementing we again get error stating "Cannot be implemented". Diagonsis states " SAP Note does not contain valid correction instructions".
Have anyone faced similar problems? Please help us out.
Thanks,
Rajesh Manoharan

Hi,
Thanks for the reply.
I tried to use the report "/SAPAPO/TS_PSTRU_GEN" to check, but it gives Generation Error when I run it. No diagonsis attached to that error.
When I tried to use the transaction and check for inconsistency, it says the POS is not active.
Please give me more pointers to check.
Regards,
Rajesh Manoharan

Error while running background deployment, program /SAPAPO/RMSDPDEP

Hi all,
For the second time in 3 months, I encounter this strange error while running a daily background deployment job, using program /SAPAPO/RMSDPDEP.
The job starts correctly and does a part of its job, but then interrupt with this message in the job log :
--> "no valid simulation guid" (class SAPAPO/OM_TS, n° 101)
--> "Unknown error" (class SAPAPO/OM, n° 100)
--> "Job cancelled after system exception ERROR_MESSAGE" (class 00, n° 564)
I just can't find any clue about what causes the problem...
Did anyone encounter that kind of difficulties before ? Any help would be usefull...
Thanks !
Fabrice

Hi Siva,
In this range of time, I effectively run 13 parallel deployment jobs, as follow :
n° 1, 2, 3, 4 and 5 : same location (factory 1) and each treats a products selection
n° 6, 7, 8, 9 and 10 : same location (factory 2) and each treats a products selection
n° 11 : all products of factory 3
n° 12 : all products of factory 4
n° 13 : all products of factory 5
A product can only be produced in a single location, so there might not have access concurencies during parallel jobs. Do you think it could be some kind of a technical problem (not enough process available ?). Note that the problem can't come from CPU, we use CPU auto-allocation, and it works well.
What do you think ?
Thanks
Fabrice

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

/SAPAPO/RESLCT

Similar Messages

Maybe you are looking for