Customize ASCP Launch Plan : Consider recipe effective date

Hi all,
I'm interested in customize some feature when launch ASCP plan.
I meet a problem that ASCP is unidentify item recipe which has multiple version, different effective date.
Can you help me how to customize it, I need ASCP consider recipe effectivity date when launch plan
Please see my example:
https://lh6.googleusercontent.com/-6CRUzM2VTKs/TvrpKRMyAkI/AAAAAAAAIjI/Z_jqgkmUBGU/s800/2011-12-28_170052.jpg
Best rgds,
Dai

Similar Messages

How to consider capacity constrain in ASCP unconstrain plan

Is it possible to feed available capacity (Resource & machine) to ASCP unconstrain plan, so that ASCP plan only for available capacity eventhough all the supply exist to fulfill all the demand. The constrain is, the business is not ready to move to constrain plan.
If not possible, what is the alternative solution being used across industry using unconstrain plan in ASCP.
Hoping for your expert advise.
Thanks,
Edited by: user604737 on Nov 10, 2010 9:56 AM

Currently we have constrain in resource and machine capacity, we are using unconstrain plan. It would be gr8, if you provide more clarity how ASCP recommendation consider this fact and display exception for planner, as we are not able to simulate the plan for capacity changes.
Regards,
Edited by: user604737 on Nov 10, 2010 2:08 PM

How planned delivery time effects delivery creation?

Dear All,
Some time before, while placing order thro' CRM, we came across a typical error (hard error).
"date (11/12/2011) lies afterthe end of validity calendar".
we could not place order in CRM but in SAP we could create save the order despite of same error but soft. However system didn't allow to create delivery for same order & same error message populated"
Later it was found that it is because for material " Planned Deliv. Time maintained for say "X "days in material master MRP2 view" & was corrected.
How planned delivery time effects delivery creation?
For material even though planned delivery time was maintained as say for 500 days, sales order requested delivery date & delivery date in order schedule line got determined as order date (Considering avaliability of funds & material).
i.e order date/req. delivery date/delivery date in schedule line are same as date on which order is placed.
Regards
Suhas W

Hi,
Extended your factory calender in SCA3.
Regards,

ASCP Table name for Recipe 'Preference' field

I have separate Planning and Production recipes for the same item. ASCP is required to plan using planning recipes - and batches would be created manually refererring ASCP output using production recipes (there is business reason for this).
All planning recipes have validity rules with Preference = 1 and production recipes have Preference = 10. As per metalink, ASCP would collect both recipes and try to plan using the Planning recipe. But, if required, it may use the production recipe in a constrained plan. I do not want that to happen ever. To ensure this I want to end date / delete the production recipes in the planning server. But I can not find any field corresponding to Preference in MSC_BOMS and MSC_BOM_COMPONENTS. What is the table name where this preference is saved? Also what impact will this have on open OPM batches - which uses the production recipe?

Hi GeertN,
Thanks once again for the prompt response.
I had seen those two fields (Effectivity_date and disable_date) - but they do not contain the validity rule end date. For example, I have a recipe which is end dated for 5 organizations in source and valid for 1 org. In msc_process_effectivity there is only one row for that bill_sequence_id - and that corresponds to the org for which the recipe is valid. Does that mean the collection process does not collect recipes with end dated validity rules?
Also, I had tried "update MSC_PROCESS_EFFECTIVITY set disable_date = sysdate where... " - but with that MBP seems to have hung (running for 3 hours - when it normally finishes in 40 mins).
Regards.

CBO generating different plans for the same data in similar Environments

Hi All
I have been trying to compare an SQL from 2 different but similar environments build of the same hardware specs .The issue I am facing is environment A, the query executes in less than 2 minutes with plan mostly showing full table scans and hash join whereas in environment B(problematic), it times out after 2 hours with an error of unable to extend table space . The statistics are up to date in both environments for both tables and indexes . System parameters are exactly similar(default oracle for except for multiblock_read_count ).
Both Environment have same db parameter for db_file_multiblock_read_count(16), optimizer(refer below),hash_area_size (131072),pga_aggregate_target(1G),db_block_size(8192) etc . SREADTIM, MREADTIM, CPUSPEED, MBRC are all null in aux_stats in both environment because workload was never collected i believe.
Attached is details about the SQL with table stats, SQL and index stats my main concern is CBO generating different plans for the similar data and statistics and same hardware and software specs. Is there any thing else I should consider .I generally see environment B being very slow and always plans tend to nested loops and index scan whereas what we really need is a sensible FTS in many cases. One of the very surprising thing is METER_CONFIG_HEADER below which has just 80 blocks of data is being asked for index scan.
show parameter optimizer
optimizer_dynamic_sampling integer 2
optimizer_features_enable string 10.2.0.4
optimizer_index_caching integer 0
optimizer_index_cost_adj integer 100
optimizer_mode string ALL_ROWS
optimizer_secure_view_merging boolean TRUE
**Environment**
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
CORE     10.2.0.4.0     Production
TNS for Solaris: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
Note: : There are slight difference in the no of records in the attached sheet.However, I wanted to tell that i have tested with exact same data and was getting similar results but I couldn't retain the data untill collecting the details in the attachment
TEST1     COMPARE TABLE LEVE STATS used by CBO
ENVIRONMENT A
TABLE_NAME     NUM_ROWS     BLOCKS     LAST_ANALYZED
ASSET     3607425     167760     5/02/2013 22:11
METER_CONFIG_HEADER     3658     80     5/01/2013 0:07
METER_CONFIG_ITEM     32310     496     5/01/2013 0:07
NMI     1899024     33557     18/02/2013 10:55
REGISTER     4830153     101504     18/02/2013 9:57
SDP_LOGICAL_ASSET     1607456     19137     18/02/2013 15:48
SDP_LOGICAL_REGISTER     5110781     78691     18/02/2013 9:56
SERVICE_DELIVERY_POINT     1425890     42468     18/02/2013 13:54
ENVIRONMENT B
TABLE_NAME     NUM_ROWS     BLOCKS     LAST_ANALYZED
ASSET     4133939     198570     16/02/2013 10:02
METER_CONFIG_HEADER     3779     80     16/02/2013 10:55
METER_CONFIG_ITEM     33720     510     16/02/2013 10:55
NMI     1969000     33113     16/02/2013 10:58
REGISTER     5837874     120104     16/02/2013 11:05
SDP_LOGICAL_ASSET     1788152     22325     16/02/2013 11:06
SDP_LOGICAL_REGISTER     6101934     91088     16/02/2013 11:07
SERVICE_DELIVERY_POINT     1447589     43804     16/02/2013 11:11
TEST ITEM 2     COMPARE INDEX STATS used by CBO
ENVIRONMENT A
TABLE_NAME     INDEX_NAME     UNIQUENESS     BLEVEL     LEAF_BLOCKS     DISTINCT_KEYS     AVG_LEAF_BLOCKS_PER_KEY     AVG_DATA_BLOCKS_PER_KEY     CLUSTERING_FACTOR     NUM_ROWS
ASSET     IDX_AST_DEVICE_CATEGORY_SK     NONUNIQUE     2     9878     67     147     12982     869801     3553095
ASSET     IDX_A_SAPINTLOGDEV_SK     NONUNIQUE     2     7291     2747     2     639     1755977     3597916
ASSET     SYS_C00102592     UNIQUE     2     12488     3733831     1     1     3726639     3733831
METER_CONFIG_HEADER     SYS_C0092052     UNIQUE     1     12     3670     1     1     3590     3670
METER_CONFIG_ITEM     SYS_C0092074     UNIQUE     1     104     32310     1     1     32132     32310
NMI     IDX_NMI_ID     NONUNIQUE     2     6298     844853     1     2     1964769     1965029
NMI     IDX_NMI_ID_NK     NONUNIQUE     2     6701     1923072     1     1     1922831     1923084
NMI     IDX_NMI_STATS     NONUNIQUE     1     106     4     26     52     211     211
REGISTER     REG_EFFECTIVE_DTM     NONUNIQUE     2     12498     795     15     2899     2304831     4711808
REGISTER     SYS_C00102653     UNIQUE     2     16942     5065660     1     1     5056855     5065660
SDP_LOGICAL_ASSET     IDX_SLA_SAPINTLOGDEV_SK     NONUNIQUE     2     3667     1607968     1     1     1607689     1607982
SDP_LOGICAL_ASSET     IDX_SLA_SDP_SK     NONUNIQUE     2     3811     668727     1     2     1606204     1607982
SDP_LOGICAL_ASSET     SYS_C00102665     UNIQUE     2     5116     1529606     1     1     1528136     1529606
SDP_LOGICAL_REGISTER     SYS_C00102677     UNIQUE     2     17370     5193638     1     1     5193623     5193638
SERVICE_DELIVERY_POINT     IDX_SDP_NMI_SK     NONUNIQUE     2     4406     676523     1     2     1423247     1425890
SERVICE_DELIVERY_POINT     IDX_SDP_SAP_INT_NMI_SK     NONUNIQUE     2     7374     676523     1     2     1458238     1461108
SERVICE_DELIVERY_POINT     SYS_C00102687     UNIQUE     2     4737     1416207     1     1     1415022     1416207
ENVIRONMENT B
TABLE_NAME     INDEX_NAME     UNIQUENESS     BLEVEL     LEAF_BLOCKS     DISTINCT_KEYS     AVG_LEAF_BLOCKS_PER_KEY     AVG_DATA_BLOCKS_PER_KEY     CLUSTERING_FACTOR     NUM_ROWS
ASSET     IDX_AST_DEVICE_CATEGORY_SK     NONUNIQUE     2     8606     121     71     16428     1987833     4162257
ASSET     IDX_A_SAPINTLOGDEV_SK     NONUNIQUE     2     8432     1780146     1     1     2048170     4162257
ASSET     SYS_C00116157     UNIQUE     2     13597     4162263     1     1     4158759     4162263
METER_CONFIG_HEADER     SYS_C00116570     UNIQUE     1     12     3779     1     1     3734     3779
METER_CONFIG_ITEM     SYS_C00116592     UNIQUE     1     107     33720     1     1     33459     33720
NMI     IDX_NMI_ID     NONUNIQUE     2     6319     683370     1     2     1970460     1971313
NMI     IDX_NMI_ID_NK     NONUNIQUE     2     6597     1971293     1     1     1970771     1971313
NMI     IDX_NMI_STATS     NONUNIQUE     1     98     48     2     4     196     196
REGISTER     REG_EFFECTIVE_DTM     NONUNIQUE     2     15615     1273     12     2109     2685924     5886582
REGISTER     SYS_C00116748     UNIQUE     2     19533     5886582     1     1     5845565     5886582
SDP_LOGICAL_ASSET     IDX_SLA_SAPINTLOGDEV_SK     NONUNIQUE     2     4111     1795084     1     1     1758441     1795130
SDP_LOGICAL_ASSET     IDX_SLA_SDP_SK     NONUNIQUE     2     4003     674249     1     2     1787987     1795130
SDP_LOGICAL_ASSET     SYS_C004520     UNIQUE     2     5864     1795130     1     1     1782147     1795130
SDP_LOGICAL_REGISTER     SYS_C004539     UNIQUE     2     20413     6152850     1     1     6073059     6152850
SERVICE_DELIVERY_POINT     IDX_SDP_NMI_SK     NONUNIQUE     2     3227     660649     1     2     1422572     1447803
SERVICE_DELIVERY_POINT     IDX_SDP_SAP_INT_NMI_SK     NONUNIQUE     2     6399     646257     1     2     1346948     1349993
SERVICE_DELIVERY_POINT     SYS_C00128706     UNIQUE     2     4643     1447946     1     1     1442796     1447946
TEST ITEM 3     COMPARE PLANS
ENVIRONMENT A
Plan hash value: 4109575732
| Id | Operation                       | Name                   | Rows | Bytes |TempSpc| Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT                |                        |    13 | 2067 |       |   135K (2)| 00:27:05 |
|   1 | HASH UNIQUE                    |                        |    13 | 2067 |       |   135K (2)| 00:27:05 |
|* 2 |   HASH JOIN                     |                        |    13 | 2067 |       |   135K (2)| 00:27:05 |
|* 3 |    HASH JOIN                    |                        |     6 |   900 |       |   135K (2)| 00:27:04 |
|* 4 |     HASH JOIN ANTI              |                        |     1 |   137 |       |   135K (2)| 00:27:03 |
|* 5 |      TABLE ACCESS BY INDEX ROWID| NMI                    |     1 |    22 |       |     5   (0)| 00:00:01 |
|   6 |       NESTED LOOPS              |                        |     1 |   131 |       | 95137   (2)| 00:19:02 |
|* 7 |        HASH JOIN                |                        |     1 |   109 |       | 95132   (2)| 00:19:02 |
|* 8 |         TABLE ACCESS FULL       | ASSET                  | 36074 | 1021K|       | 38553   (2)| 00:07:43 |
|* 9 |         HASH JOIN               |                        | 90361 | 7059K| 4040K| 56578   (2)| 00:11:19 |
|* 10 |          HASH JOIN              |                        | 52977 | 3414K| 2248K| 50654   (2)| 00:10:08 |
|* 11 |           HASH JOIN             |                        | 39674 | 1782K|       | 40101   (2)| 00:08:02 |
|* 12 |            TABLE ACCESS FULL    | REGISTER               | 39439 | 1232K|       | 22584   (2)| 00:04:32 |
|* 13 |            TABLE ACCESS FULL    | SDP_LOGICAL_REGISTER   | 4206K|    56M|       | 17490   (2)| 00:03:30 |
|* 14 |           TABLE ACCESS FULL     | SERVICE_DELIVERY_POINT |   675K|    12M|       | 9412   (2)| 00:01:53 |
|* 15 |          TABLE ACCESS FULL      | SDP_LOGICAL_ASSET      | 1178K|    15M|       | 4262   (2)| 00:00:52 |
|* 16 |        INDEX RANGE SCAN         | IDX_NMI_ID_NK          |     2 |       |       |     2   (0)| 00:00:01 |
| 17 |      VIEW                       |                        | 39674 |   232K|       | 40101   (2)| 00:08:02 |
|* 18 |       HASH JOIN                 |                        | 39674 | 1046K|       | 40101   (2)| 00:08:02 |
|* 19 |        TABLE ACCESS FULL        | REGISTER               | 39439 |   500K|       | 22584   (2)| 00:04:32 |
|* 20 |        TABLE ACCESS FULL        | SDP_LOGICAL_REGISTER   | 4206K|    56M|       | 17490   (2)| 00:03:30 |
|* 21 |     TABLE ACCESS FULL           | METER_CONFIG_HEADER    | 3658 | 47554 |       |    19   (0)| 00:00:01 |
|* 22 |    TABLE ACCESS FULL            | METER_CONFIG_ITEM      | 7590 | 68310 |       |   112   (2)| 00:00:02 |
Predicate Information (identified by operation id):
   2 - access("METER_CONFIG_HEADER_SK"="METER_CONFIG_HEADER_SK")
   3 - access("NETWORK_TARIFF_CD"="NETWORK_TARIFF_CD")
   4 - access("SERVICE_DELIVERY_POINT_SK"="TMP"."SERVICE_DELIVERY_POINT_SK")
   5 - filter("ROW_CURRENT_IND"='Y' AND ("NMI_STATUS_CD"='A' OR "NMI_STATUS_CD"='D'))
   7 - access("ASSET_CD"="EQUIP_CD" AND "SAP_INT_LOG_DEVICE_SK"="SAP_INT_LOG_DEVICE_SK")
   8 - filter("ROW_CURRENT_IND"='Y')
   9 - access("SERVICE_DELIVERY_POINT_SK"="SERVICE_DELIVERY_POINT_SK")
10 - access("SERVICE_DELIVERY_POINT_SK"="SERVICE_DELIVERY_POINT_SK")
11 - access("SAP_INT_LOGICAL_REGISTER_SK"="SAP_INT_LOGICAL_REGISTER_SK")
12 - filter("REGISTER_TYPE_CD"='C' AND (SUBSTR("REGISTER_ID_CD",1,1)='4' OR
              SUBSTR("REGISTER_ID_CD",1,1)='5' OR SUBSTR("REGISTER_ID_CD",1,1)='6') AND "ROW_CURRENT_IND"='Y')
13 - filter("ROW_CURRENT_IND"='Y')
14 - filter("ROW_CURRENT_IND"='Y')
15 - filter("ROW_CURRENT_IND"='Y')
16 - access("NMI_SK"="NMI_SK")
18 - access("SAP_INT_LOGICAL_REGISTER_SK"="SAP_INT_LOGICAL_REGISTER_SK")
19 - filter("REGISTER_TYPE_CD"='C' AND (SUBSTR("REGISTER_ID_CD",1,1)='1' OR
              SUBSTR("REGISTER_ID_CD",1,1)='2' OR SUBSTR("REGISTER_ID_CD",1,1)='3') AND "ROW_CURRENT_IND"='Y')
20 - filter("ROW_CURRENT_IND"='Y')
21 - filter("ROW_CURRENT_IND"='Y')
22 - filter("ROW_CURRENT_IND"='Y' AND "CONROL_REGISTER"='X')
ENVIRONMENT B
Plan hash value: 2826260434
| Id | Operation                            | Name                   | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT                     |                        |     1 |   181 |   103K (2)| 00:20:47 |
|   1 | HASH UNIQUE                         |                        |     1 |   181 |   103K (2)| 00:20:47 |
|* 2 |   HASH JOIN ANTI                     |                        |     1 |   181 |   103K (2)| 00:20:47 |
|* 3 |    HASH JOIN                         |                        |     1 |   176 | 56855   (2)| 00:11:23 |
|* 4 |     HASH JOIN                        |                        |     1 |   163 | 36577   (2)| 00:07:19 |
|* 5 |      TABLE ACCESS BY INDEX ROWID     | ASSET                  |     1 |    44 |     4   (0)| 00:00:01 |
|   6 |       NESTED LOOPS                   |                        |     1 |   131 | 9834   (2)| 00:01:59 |
|   7 |        NESTED LOOPS                  |                        |     1 |    87 | 9830   (2)| 00:01:58 |
|   8 |         NESTED LOOPS                 |                        |     1 |    74 | 9825   (2)| 00:01:58 |
|* 9 |          HASH JOIN                   |                        |     1 |    52 | 9820   (2)| 00:01:58 |
|* 10 |           TABLE ACCESS BY INDEX ROWID| METER_CONFIG_HEADER    |     1 |    14 |     1   (0)| 00:00:01 |
| 11 |            NESTED LOOPS              |                        |     1 |    33 |   116   (2)| 00:00:02 |
|* 12 |             TABLE ACCESS FULL        | METER_CONFIG_ITEM      |     1 |    19 |   115   (2)| 00:00:02 |
|* 13 |             INDEX RANGE SCAN         | SYS_C00116570          |     1 |       |     1   (0)| 00:00:01 |
|* 14 |           TABLE ACCESS FULL          | SERVICE_DELIVERY_POINT |   723K|    13M| 9699   (2)| 00:01:57 |
|* 15 |          TABLE ACCESS BY INDEX ROWID | NMI                    |     1 |    22 |     5   (0)| 00:00:01 |
|* 16 |           INDEX RANGE SCAN           | IDX_NMI_ID_NK          |     2 |       |     2   (0)| 00:00:01 |
|* 17 |         TABLE ACCESS BY INDEX ROWID | SDP_LOGICAL_ASSET      |     1 |    13 |     5   (0)| 00:00:01 |
|* 18 |          INDEX RANGE SCAN            | IDX_SLA_SDP_SK         |     2 |       |     2   (0)| 00:00:01 |
|* 19 |        INDEX RANGE SCAN              | IDX_A_SAPINTLOGDEV_SK |     2 |       |     2   (0)| 00:00:01 |
|* 20 |      TABLE ACCESS FULL               | REGISTER               | 76113 | 2378K| 26743   (2)| 00:05:21 |
|* 21 |     TABLE ACCESS FULL                | SDP_LOGICAL_REGISTER   | 5095K|    63M| 20245   (2)| 00:04:03 |
| 22 |    VIEW                              |                        | 90889 |   443K| 47021   (2)| 00:09:25 |
|* 23 |     HASH JOIN                        |                        | 90889 | 2307K| 47021   (2)| 00:09:25 |
|* 24 |      TABLE ACCESS FULL               | REGISTER               | 76113 |   966K| 26743   (2)| 00:05:21 |
|* 25 |      TABLE ACCESS FULL               | SDP_LOGICAL_REGISTER   | 5095K|    63M| 20245   (2)| 00:04:03 |
Predicate Information (identified by operation id):
   2 - access("SERVICE_DELIVERY_POINT_SK"="TMP"."SERVICE_DELIVERY_POINT_SK")
   3 - access("SERVICE_DELIVERY_POINT_SK"="SERVICE_DELIVERY_POINT_SK" AND
              "SAP_INT_LOGICAL_REGISTER_SK"="SAP_INT_LOGICAL_REGISTER_SK")
   4 - access("ASSET_CD"="EQUIP_CD")
   5 - filter("ROW_CURRENT_IND"='Y')
   9 - access("NETWORK_TARIFF_CD"="NETWORK_TARIFF_CD")
10 - filter("ROW_CURRENT_IND"='Y')
12 - filter("ROW_CURRENT_IND"='Y' AND "CONROL_REGISTER"='X')
13 - access("METER_CONFIG_HEADER_SK"="METER_CONFIG_HEADER_SK")
14 - filter("ROW_CURRENT_IND"='Y')
15 - filter("ROW_CURRENT_IND"='Y' AND ("NMI_STATUS_CD"='A' OR "NMI_STATUS_CD"='D'))
16 - access("NMI_SK"="NMI_SK")
17 - filter("ROW_CURRENT_IND"='Y')
18 - access("SERVICE_DELIVERY_POINT_SK"="SERVICE_DELIVERY_POINT_SK")
19 - access("SAP_INT_LOG_DEVICE_SK"="SAP_INT_LOG_DEVICE_SK")
20 - filter((SUBSTR("REGISTER_ID_CD",1,1)='4' OR SUBSTR("REGISTER_ID_CD",1,1)='5' OR
              SUBSTR("REGISTER_ID_CD",1,1)='6') AND "REGISTER_TYPE_CD"='C' AND "ROW_CURRENT_IND"='Y')
21 - filter("ROW_CURRENT_IND"='Y')
23 - access("SAP_INT_LOGICAL_REGISTER_SK"="SAP_INT_LOGICAL_REGISTER_SK")
24 - filter((SUBSTR("REGISTER_ID_CD",1,1)='1' OR SUBSTR("REGISTER_ID_CD",1,1)='2' OR
              SUBSTR("REGISTER_ID_CD",1,1)='3') AND "REGISTER_TYPE_CD"='C' AND "ROW_CURRENT_IND"='Y')
25 - filter("ROW_CURRENT_IND"='Y')Edited by: abhilash173 on Feb 24, 2013 9:16 PM
Edited by: abhilash173 on Feb 24, 2013 9:18 PM

Hi Paul,
I misread your question initially .The system stats are outdated in both ( same result as seen from aux_stats) .I am not a DBA and do not have access to gather system stats fresh.
select * from sys.aux_stats$
SNAME     PNAME     PVAL1     PVAL2
SYSSTATS_INFO     STATUS     NULL     COMPLETED
SYSSTATS_INFO     DSTART     NULL     02-16-2011 15:24
SYSSTATS_INFO     DSTOP     NULL     02-16-2011 15:24
SYSSTATS_INFO     FLAGS     1     NULL
SYSSTATS_MAIN     CPUSPEEDNW     1321.20523     NULL
SYSSTATS_MAIN     IOSEEKTIM     10     NULL
SYSSTATS_MAIN     IOTFRSPEED     4096     NULL
SYSSTATS_MAIN     SREADTIM     NULL     NULL
SYSSTATS_MAIN     MREADTIM     NULL     NULL
SYSSTATS_MAIN     CPUSPEED     NULL     NULL
SYSSTATS_MAIN     MBRC     NULL     NULL
SYSSTATS_MAIN     MAXTHR     NULL     NULL
SYSSTATS_MAIN     SLAVETHR     NULL     NULL

GL Trial Balance Report with Effective Dates as Parameters

We have a requirement to show the GL Trial Balance report with Effective dates as Parameters.
Current Analysis:
The Journals get updated with corresponding CCID in GL_BALANCES table when the Journal is posted. GL_BALANCE is SOB specific, if the SOB has month as period then the balances in GL_BALANCES would get updated against the month(period).
To overcome the period problem, we explored the option of using a View based on GL_JE_HEADERS and GL_JE_LINES for 'Posted' Journal Batches of a SOB. We are checking whether the GL_JE_HEADERS.default_effective_date lies between the :p_from_date and :p_to_date which is sent to the Report as a parameter. The above idea does not return expected data when the custom Trial Balance Report is run.
Following is the Query being used:
SELECT cc.segment4 ACCOUNT, bal.code_combination_id,
bal.begin_balance_dr
+ SUM (NVL (gljel.accounted_dr, 0)) opening_bal_dr,
bal.begin_balance_cr
+ SUM (NVL (gljel.accounted_cr, 0)) opening_bal_cr,
ffv.description,
(SELECT SUM (NVL (gljel.accounted_dr, 0))
FROM gl_je_headers gljeh,
gl_je_lines gljel,
gl_code_combinations gcc
WHERE gljeh.default_effective_date BETWEEN :p_from_date
AND :p_to_date
AND gljeh.je_header_id = gljel.je_header_id
AND gljel.code_combination_id = gcc.code_combination_id
AND gljel.period_name = gljeh.period_name
AND gljel.set_of_books_id = :p_set_of_books_id
AND gljeh.status = 'P'
AND gljel.status = 'P'
AND gljeh.actual_flag = 'A'
--AND gljel.code_combination_id =
-- bal.code_combination_id
AND gcc.segment4 = cc.segment4
GROUP BY gcc.segment4) c_dr,
(SELECT SUM (NVL (gljel.accounted_cr, 0))
FROM gl_je_headers gljeh,
gl_je_lines gljel,
gl_code_combinations gcc
WHERE gljeh.default_effective_date BETWEEN :p_from_date
AND :p_to_date
AND gljeh.je_header_id = gljel.je_header_id
AND gljel.period_name = gljeh.period_name
AND gljel.code_combination_id = gcc.code_combination_id
AND gljel.set_of_books_id = :p_set_of_books_id
AND gljeh.status = 'P'
AND gljel.status = 'P'
AND gljeh.actual_flag = 'A'
AND gcc.segment4 = cc.segment4
GROUP BY gcc.segment4) c_cr
FROM gl_period_statuses per,
gl_code_combinations cc,
gl_balances bal,
gl_je_headers gljeh,
gl_je_lines gljel,
fnd_flex_values_vl ffv,
fnd_flex_value_sets ffvs
WHERE cc.chart_of_accounts_id = :p_chart_of_accts_id
AND bal.currency_code = :p_currency
AND bal.actual_flag = 'A'
AND bal.period_name = per.period_name
AND cc.template_id IS NULL
AND cc.code_combination_id = bal.code_combination_id
AND per.set_of_books_id = :p_set_of_books_id
AND per.application_id = 101
AND :p_from_date BETWEEN per.start_date AND per.end_date
AND gljeh.period_name = per.period_name
AND gljeh.default_effective_date <= :p_from_date
AND gljeh.je_header_id = gljel.je_header_id
AND gljel.period_name = gljeh.period_name
AND gljel.set_of_books_id = :p_set_of_books_id
AND ffv.flex_value_set_id = ffvs.flex_value_set_id
AND ffvs.flex_value_set_name = 'JSWEL_ACCOUNT'
AND gljeh.status = 'P'
AND gljel.status = 'P'
AND cc.summary_flag = ffv.summary_flag
AND cc.segment4 = ffv.flex_value
AND gljeh.actual_flag = 'A'
AND gljel.code_combination_id = bal.code_combination_id
GROUP BY bal.begin_balance_dr,
bal.begin_balance_cr,
cc.segment4,
ffv.description,
bal.code_combination_id
Kindly suggest if I am missing anything. I am sure that the great guns here can help me out.
Thanks
Sumit

suggest to create customize TB report.

Planning considering the expiry of materials

Dear All ,
We belong to Pharmaceutical industry .We want to carry out material requirement planning for raw materials considering the expiry dates of raw materials .The materials which are due to expire in say next two months should not be considered in planning as unrestricted stock . Kindly suggest the config and master settings for this requirement .

HI
MRP will not check expiry related logics.
it will chekc wether the stock is there or not.
better you need to run the deadline monitoring in back ground that is QA07.
for that your materials should have the batch classification data.
and at the time of GRNs systen will update the expiry dates in the BTCHES.(in material master you need to maintain the shelf life)
So at the time of ruuning the QA07 system will transfer to blocked stock ( all the materials which are expired).
-ashok

Product pricing and effective dates

Hello guys,
Hope all of you are doing fine.
In my current implementation we are going to integrate the pricing in the product repository, however I was asked to find out if anyone in the team has experience with putting pricing in a product or material repository in MDM and specifically dealing with the requirement of having effective dates for different prices.
If you have such experience or thoughts to share please reply.
Also it would be useful to know if you are aware if SAP has any future plans to release such functionality in future versions of the tool (or business content).
Kind Regards,
Jorge

Then my cardinality is drastically reduced to 92K (actual 110M) - leading to Nested Loops further up the query plan....
I don't have histograms on the columns involvedIf you add histograms on the involved columns, is the optimizer picking up a better execution plan?
Also note that the problem might be that you need a combined value distribution on two columns. This is possible from 11g onwards, but not before. Check out http://www.oracle.com/technology/pub/articles/oracle-database-11g-top-features/11g-manage.html (Search for Multi-Column Statistics)

ECM : Effective Date change via the portal - ECC 4.0

Hi ,
We did configure V_T71ADM10 , so the Effective Date cannot be changed , it look like each time we scroll down in the portal, or we complete the Amount or Percentage in the Plan for one persone , the ECM page is refreshed , and an new "Effective on" date is calculated and decremented by 1 Day . ... DATE - 1 day , DATE - 1 day , ......
Anyone run into the same problem ?
Regard's
Christophe.

Hi Deb,
Check this wiki link for creating different type of iView in Portal including Transaction iView.
http://wiki.sdn.sap.com/wiki/display/EP/CreationofDifferentTypesofiViewsinEP7.0
Regards,

Effective Date for Yearly Increment

We are having different effective dates for Salary and Hourly employees for whom I have created two Guideline groups but under the same Comp Plan and Comp Review Item. I am getting the desired increase Dollar amount in Annual figure for Salary and hourly figure for Hourly. But, the effective date is also taking same as per the Comp Review Item. When I tried to add one more comp review item for Hourly, I am not able to do with the same combination of Plan and Review.
So, how can I get the respective effective date as we have only one place to define the same? Do I have to create one more Comp Plan for the Hourly employees?
Thanks

I was thinking your issue was with applying the appropriate guidelines.. If it is only the effective date, you can implement the BAdI HRECM00_EFFDATE & pass back the new effdt in the method GET_DEFAULT_EFF_DATE.
~Suresh

Operation wise total required hours for planned order in given date range

Hello Experts,
My client wants the report to check the capacity utilization of the work centers for the all planned order in particular date range.
Is their any standard report which gives the work center wise operation wise total required hours? or which table should I use to make the customize report so that I will get total required capacity & available capacity.
Thanks in advance for use valuable suggestions.
Sagar

Hi Mario,
Thanks for your reply,
In CM01 or CM05, we are getting requirement on weekly basis.How to get that report on daily basis? I want to give the input as a date range of the planned order.How to go for that?
Edited by: SAGAR GOLIWAR 226 on Jul 3, 2011 8:16 AM

Setting Configuration effective date to promise date

in order management there is a system parameter OM: Configuration Effective Date, which can be set to 1.Model creation Date, 2.System Date till Booking, 3.System DAte date till Pick Realease. How can i set this parameter or the configurator model lookup date and effective date to the entered promise date?
So that every time the configurator is launched it considers the promise date a s the model lookup date and for configuration vaildation as well as BOM validation?

well how about using the following procedure?
1.CZ_CF_API.DEFAULT_NEW_CFG_DATES(p_creation_date IN OUT NOCOPY DATE,
p_lookup_date IN OUT NOCOPY DATE,
p_effective_date IN OUT NOCOPY DATE)---- For new configuration
2.CZ_CF_API.DEFAULT_RESTORED_CFG_DATES(p_config_hdr_id IN NUMBER,
p_config_rev_nbr IN NUMBER,
p_creation_date IN OUT NOCOPY DATE,
p_lookup_date IN OUT NOCOPY DATE,
p_effective_date IN OUT NOCOPY DATE)---- For Restored configuration

Does Make To Order planning consider any SNP/PPDS Horizons

Guys
Does Make To Order planning consider any SNP/PPDS Horizons unike the Make to Stock scenario planning?
Thanks

Thanks for the response guys.
In RRP3 view, when I look at the Individual project segment demand, I do not see any SNP/PPDS Horizons. However, when I see the demands under the MTS segment, I can see the SNP/PPDS Horizons.
In MTS scenario, I understand that only those orders that falls within PPDS horizon are picked up by PPDS planning and orders outisde SNP horizon are picked up by SNP planning.
However, as MTO is purely PPDS planning, I am just wondering whether SNP or PPDS horizon comes into the picture in this scenario or not.
Further more, my primary concern in MTO scenario is, if PPDS horizon is taken into the picture ( which is usually in the near visible term and < SNP horizon, say 15 days), and as PPDS planning doesn't pick the demand in the MTO segment until the demand falls with in this horizon, aren't we not leveraging the full functionality of procurement planning, as PPDS plans the demand by picking it just before 15 days (in this example) of the original requirement date, and the company might not be able to fulfil the customer order as the replenishment time might be long for this particular product being procured/produced.
So, I am basically leaning towards an understanding that what ever demand that falls in the Individual Customer/Project segment (MTO), it will be picked up PPDS planning regard less of SNP/PPDS horizons.
Please advice, if my understanding is wrong and I would appreciate if you quote some examples which might help me better understand the scenario.
Thanks

Effective date in ECN

Dear Sir,
How we can maintain effective date( validity Date) in one ECN.
For example- BOM "A" is having X,Y,Z item
X has the validity date- 13.02.2009 to 31.12.9999
Y has the validity date -13.02.2009-20.02.2009
Z has the validity date - 13.02.2009-25.02.2009
Please help.
Regards,
Sanjay Sahoo

Hi,
You need to create the 3 different change masters. Each change master will be having different validity. Using this change numbers you can control of the materials.
You need to change the BOM for "A" material.
Also one thing you need to consider that, the Valid from dates you can maintain in change master. But the valid to date is default by 31.12.9999. To control this you need to create one more change master. This way only you need to control this.
Regards,
V. Suresh

Is there standard report for planned and actual devlivery date?

Hi Guru,
Could you help me to find standard report to compare planned delivery date in PO and actual delivery date (GR Posting date)?
I wonder, Is there standard report for planned and actual delivery date?
or I have to create a customizing report.
Thank you very much.

hi
i dont think it is possible to see both in one pan so try to create some Z report
u try ME80fn here u have to change the views ,in del shedule view u can see the delivery dtae and in PO histry view u can see the posting date
regards
kunal

Customize ASCP Launch Plan : Consider recipe effective date

Similar Messages

Maybe you are looking for