[Home] [Help]
855:
856:
857: /* extract_discrete_adj_init
858:
859: Extract discrete adjustment entry data from MTL_CYCLE_COUNT_ENTRIES (MCCE),
860: MMT and MTA. Adjustments can get costed well after approval and
861: interim cost updates may cause the values recorded in MCCE to
862: be different. Thus we need to get the cost associated to the item
863: using the value in MTA so that the reported adjustments match
1083: 0),
1084: decode (sum (mmt_mta.primary_quantity),
1085: 0, C_EXACT_MATCH,
1086: C_NO_MATCH)
1087: FROM mtl_cycle_count_entries mcce,
1088: mtl_cycle_count_headers mcch,
1089: mtl_cycle_count_items mcci,
1090: mtl_cycle_count_classes mccc,
1091: mtl_system_items_b msi,
1185:
1186:
1187:
1188: /* extract_process_adj_init
1189: Extract process adjustment entry data from MTL_CYCLE_COUNT_ENTRIES (MCCE),
1190: MMT and GTV. The transactions in GTV can be either in Draft, New or Final Mode.
1191: We will only consider Draft and Final Mode of transactions only.
1192:
1193: For initial load there will not be any separate bounds for Final and Draft
1379: 0),
1380: decode (sum (mmt_gtv.primary_quantity),
1381: 0, C_EXACT_MATCH,
1382: C_NO_MATCH) exact_match
1383: FROM mtl_cycle_count_entries mcce,
1384: mtl_cycle_count_headers mcch,
1385: mtl_cycle_count_items mcci,
1386: mtl_cycle_count_classes mccc,
1387: mtl_system_items_b msi,
1493:
1494:
1495: /* extract_exact_matches_init
1496:
1497: Extract the exact match entry data from the MTL_CYCLE_COUNT_ENTRIES
1498: table. Exact match data is easier to handle than adjustment entries
1499: because exact matches are approved on creation and there are no
1500: other transaction tables that need to be visited.
1501:
1649: 0,
1650: NULL,
1651: NULL,
1652: C_EXACT_MATCH
1653: FROM mtl_cycle_count_entries mcce,
1654: mtl_cycle_count_items mcci,
1655: mtl_cycle_count_classes mccc,
1656: mtl_system_items_b msi,
1657: mtl_secondary_inventories subs,
2674:
2675:
2676: /* extract_discrete_adj_incr
2677:
2678: Extract discrete adjustment entry data from MTL_CYCLE_COUNT_ENTRIES (MCCE),
2679: MMT and MTA. Adjustments can get costed well after approval and
2680: interim cost updates may cause the values recorded in MCCE to
2681: be different. Thus we need to get the cost associated to the item
2682: using the value in MTA so that the reported adjustments match
2880: 0),
2881: decode (sum (mmt_mta.primary_quantity),
2882: 0, C_EXACT_MATCH,
2883: C_NO_MATCH)
2884: FROM mtl_cycle_count_entries mcce,
2885: mtl_cycle_count_headers mcch,
2886: mtl_cycle_count_items mcci,
2887: mtl_cycle_count_classes mccc,
2888: mtl_system_items_b msi,
2983:
2984:
2985: /* extract_process_adj_incr
2986:
2987: Extract process adjustment entry data from MTL_CYCLE_COUNT_ENTRIES (MCCE),
2988: MMT and GTV. The transactions in GTV can be either in Draft, New or Final Mode.
2989: We will only consider Draft and Final Mode of transactions only.
2990:
2991: For initial load there will not be any separate bounds for Final and Draft
3164: 0),
3165: decode (sum (mmt_gtv.primary_quantity),
3166: 0, C_EXACT_MATCH,
3167: C_NO_MATCH) exact_match
3168: FROM mtl_cycle_count_entries mcce,
3169: mtl_cycle_count_headers mcch,
3170: mtl_cycle_count_items mcci,
3171: mtl_cycle_count_classes mccc,
3172: mtl_system_items_b msi,
3266:
3267:
3268: /* extract_exact_matches_incr
3269:
3270: Extract the exact match entry data from the MTL_CYCLE_COUNT_ENTRIES
3271: table. Exact match data is easier to handle than adjustment entries
3272: because exact matches are approved on creation and there are no
3273: other transaction tables that need to be visited.
3274:
3413: 0,
3414: NULL,
3415: NULL,
3416: C_EXACT_MATCH
3417: FROM mtl_cycle_count_entries mcce,
3418: mtl_cycle_count_items mcci,
3419: mtl_cycle_count_classes mccc,
3420: mtl_system_items_b msi,
3421: mtl_secondary_inventories subs,