Quantcast
Channel: Oracle Apps
Viewing all 116 articles
Browse latest View live

EBS R12 Period Close Advisor: Order Management and Shipping

$
0
0


NOTE:1273931.1 - Information Center: Oracle Order Management
NOTE:751026.1 - FNDWFPR - Purge Obsolete Workflow Runtime Data - OEOH / OEOL Performance issues
NOTE:863454.1 - Detailed Functional Flow of Customer Acceptance feature in Release 12
NOTE:1400757.1 - How to Find E-Business Suite Recommended Patches
NOTE:255045.1 - bde_wf_err.sql - Profile of Workflow Activities in Error
NOTE:1331647.1 - How to run the Period Close Pending Transactions Report in R12
NOTE:262979.1 - Unprocessed Shipping Transactions Troubleshooting Techniques
NOTE:878032.1 - How To Use Concurrent Program "Purge Order Management Workflow"
NOTE:961285.1 - R12: Period-End Procedures for Oracle Financials E-Business Suite
NOTE:290432.1 - How to Create a Debug File in Shipping Execution
NOTE:335.1 - Period Close Advisor: E-Business Suite (EBS)
NOTE:398822.1 - Order Management Suite - Some Data Fix Patches and Scripts
NOTE:1069492.1 - Resolving Period Close Pending Transaction R12
NOTE:458665.1 - How To Troubleshoot When Email Notification Responses Are Processed But The Approval Workflow Still Shows In Process
NOTE:1083807.1 - Diagnostic Test Catalog for 12.1.3
NOTE:739401.1 - R12 Diagnostics APPS CHECK Report: OMCHECK.sql OMCHECK.sql

EBS R12 Period Close Advisor: Inventory & Costing

$
0
0


NOTE:733863.1 - Transaction Setup (Chapter 10: R12 Inventory User's Guide in a Note)
NOTE:748704.1 - How to resolve Pending or Erred Cost Manager or Cost Workers
NOTE:753741.1 - Oracle Inventory Basic Setup Labs E-Business Suite R12
NOTE:732235.1 - R12.0.6+ : Inventory Organization Data Collection Setup Test
NOTE:1222453.1 - Diagnostic Training for Oracle Cost Management Costing Transactions Setup Test
NOTE:726226.1 - INV/WMS/RCV Family Patch Release History / Patchsets / RUPs
NOTE:732336.1 - R12.0.6+ : Oracle Cost Management Costing Transactions Setup Test
NOTE:732454.1 - R12.0.6+ : Item Master Items Data Health Check Setup Test
NOTE:605395.1 - Index: R12 Inventory User's Guide in a Note
NOTE:1312579.1 - REDIRECT: Oracle EBS Items Product Information Center
NOTE:143004.1 - Inventory Close Period Notes - Uncosted or Pending Transactions Diagnostic SQL Scripts
NOTE:206576.1 - 11i : Oracle Inventory Period Closing Activity Test
NOTE:242927.1 - 11i/R12 - Resolving Period Close Pending Transaction
NOTE:291005.1 - Costing Reports and Reconciliation
NOTE:105328.1 - Oracle Work in Process White Papers
NOTE:1055597.1 - Table of Contents For The Oracle Work In Process User's Guide, Release 12.1 (Part No. E13678-03)
NOTE:105647.1 - WIP and COST Frequently Used Troubleshooting Scripts
NOTE:1069492.1 - Resolving Period Close Pending Transaction R12
NOTE:1264685.1 - Information Center: Oracle Work In Process (WIP)
NOTE:1266644.1 - R12 Period-End Process Flow For Oracle Discrete Manufacturing - e-Business Suite
NOTE:1271813.1 - R12 Oracle Cost Management Diagnostic Scripts within E-Business suite Application
NOTE:1237963.1 - Release 12 Inventory Period-End Process Flow For Oracle Process Manufacturing - e-Business Suite
NOTE:1262392.1 - Information Center: Manufacturing Period Close
NOTE:801794.1 - Manufacturing Transaction Diagnostics - FUNCTIONAL USER SQL INVESTIGATION and REPAIR
NOTE:802966.1 - SLA Data Flow and Table Links
NOTE:857001.1 - How To Create A Wip Job And Associated Setups
NOTE:295182.1 - Period Close Reconciliation Report (CSTRPCRE)
NOTE:860522.1 - Recommended and High Priority Patches for Oracle Process Manufacturing (OPM) Release 12.1
NOTE:1099958.1 - Diagnosing Pending WIP Move Transactions
NOTE:110424.1 - FAQ: Unprocessed Transactions / Closing Inventory Accounting Period
NOTE:1141334.1 - Pending Move Transactions FAQ
NOTE:378348.1 - Data Collection Scripts for Cost Management
NOTE:414470.1 - How To Determine the Product Information Management (PIM) Patchset and Rollup Patch Version
NOTE:335.1 - Period Close Advisor: E-Business Suite (EBS)
NOTE:732479.1 - Oracle Cost Management To Check Uncosted Transactions At Period End Transaction Data Test
NOTE:333572.1 - Diagnosing WIP Related Transaction and Data Issues
NOTE:865438.1 - How to resolve Costing Errors & Problems
NOTE:961285.1 - R12: Period-End Procedures for Oracle Financials E-Business Suite
NOTE:986473.1 - Critical and Recommended Patches on Release 12.0.x for Work in Process - WIP
NOTE:76440.1 - Inventory Organization Setup Steps
NOTE:1203809.1 - Information Center: Oracle Cost Management
NOTE:1222123.1 - Rel 12: Oracle Inventory Period Close Activity Test [VIDEO]
NOTE:472631.1 - Re-Open a Closed Inventory Accounting Period
NOTE:568012.1 - FAQ: Inventory Standard Datafixes
NOTE:601639.1 - Generic Receiving Datafix Scripts and Root Cause Patches
NOTE:304313.1 - Understanding Cost Manager

update on STATUS column on the GL_INTERFACE table

$
0
0


Problem Description
What are the possible values for the STATUS column on the GL_INTERFACE table?

Solution Description
There are several common codes -  'NEW', 'P', 'PROCESSED', and 'CORRECTED'.
There are also primary error codes listed at the end of the Journal Import
Execution Report.  See Note 1056801.6 for a list of the primary error codes
and step-by-step instructions on how to correct these Journal Import errors.

There is no list for all of the possible values of the STATUS column.
This is a text field and sub-ledgers are allowed to put any
value in the field other than 'PROCESSED'. Also, a line can have multiple
errors, and therefore multiple error codes in the STATUS column.

When data is loaded into the GL_INTERFACE table, STATUS must be 'NEW' in order
to be ready for Journal Import processing.   (For a complete description of how to load
this table, see the Oracle General Ledger User Guide.)

'P' indicates that Journal Import passed this line successfully but other
lines in the same transaction failed.

'PROCESSED' indicates that journal import passed the entire transaction
successfully and has created a journal for the transaction.

'CORRECTED' indicates that the line was in error and was corrected through
the Correct Journal Import form.

WebAdi Links

$
0
0


Metalink Note#603169.1 -WebADI and Report Manager Webcasts for EBS 11i/R12 — Replay is Now Available
Metalink Note#360105.1 -Understanding and Using Web ADI in Oracle HRMS.

Read-only responsibilities in HRMS

$
0
0


This can be done by setting the Profile Option ‘Profile: HR:Query Only Mode’ to ‘Yes’. This will make forms/functions read-only. This works only for HRMS applications though.

Finding the name of a DFF in a seeded Form

$
0
0


The first step in enabling a Descriptive Flex Field (DFF) in a seeded Form is to find out the name of the DFF. Identifying a DFF involves the following steps:

1. Navigate to the Form which contains the DFF which needs to be identified.
2. Click on the DFF and then go to Help>Diagnostics>Examine to open the  ’Examine Field and Variable Values’ window, note down the Block and Field names.
3. In the ‘Examine Field and Variable Values’ window, select  $DESCRIPTIVE_FLEXFIELD$ as the Block and enter . as the Field. and are the values obtained in Step#2. Press the TAB key or click on the Value field. The name of the DFF will be displayed in the Value field along with the application under which it is registered.
4. You can now navigate to Application Developer>Flexfield>Descriptive>Register  and execute a query with the DFF name (obtained in Step#3) in the Title field to obtain the complete details of the DFF.

Query to find KEY FLEX FIELDS (KFF)

$
0
0


Query to find KEY FLEX FIELDS (KFF)

select  FIF.APPLICATION_ID  ,
        FIF.ID_FLEX_CODE    ,
        FIF.ID_FLEX_NAME    ,
        FIF.APPLICATION_TABLE_NAME ,
        FIF.DESCRIPTION     ,
        FIFS.ID_FLEX_NUM    ,
        FIFS.ID_FLEX_STRUCTURE_CODE  ,
        FIFSE.SEGMENT_NAME,
        FIFSE.SEGMENT_NUM,
        FIFSE.FLEX_VALUE_SET_ID
from    FND_ID_FLEXS FIF    ,
        FND_ID_FLEX_STRUCTURES FIFS ,
        FND_ID_FLEX_SEGMENTS FIFSE
where   FIF.APPLICATION_ID = FIFS.APPLICATION_ID
and     FIF.ID_FLEX_CODE   = FIFS.ID_FLEX_CODE
and     FIFSE.APPLICATION_ID = FIF.APPLICATION_ID
and     FIFSE.ID_FLEX_CODE = FIF.ID_FLEX_CODE
and     FIFSE.ID_FLEX_NUM = FIFS.ID_FLEX_NUM
and     FIF.ID_FLEX_CODE LIKE 'GL#'
and     FIF.ID_FLEX_NAME LIKE 'Accounting Flexfield';

OLM How to Update Classes Status

$
0
0


Is there An API To Update Scores Or to UPDATE/CREATE Records For OTA_ATTEMPTS, OTA_PERFORMANCES,OTA_TEST_QUESTIONS, OTA_QUESTION_BANKS, OTA_UTEST_RESPONSES, OTA_LO_FOLDERS, OTA_LEARNING_OBJECTS ? (Doc ID 406223.1)


Column LESSON_STATUS in table OTA_PERFORMANCES hold the player status value. Currently there are no publicly callable API's available the will permit a user to manually manipulate LESSON_STATUS. The only supported method for changing this value would require having the learner attempt and complete the learning object again though the Learner UI.

So We have to do direct base table update if this is feasible. I have done the direct base table update for one class and it worked fine.

select * from ota_activity_versions
where version_name like ‘Course Name’;-- course

select * from OTA_OFFERINGS
where activity_version_id=83037;-- offering

select * from ota_events
where activity_version_id=83037;-- class

select * from ota_learning_objects
where learning_object_id=81017;--learning objects

select * from OTA_DELEGATE_BOOKINGS
where event_id=108019
and delegate_contact_email='Jon.Hillegeist@taconic.com';--contains enrollments

select * from ota_performances
where lesson_status='P'
and user_id=22461
and   learning_object_id=81017; -- contains test results

select * from ota.ota_attempts
where event_id=108019
and  learning_object_id=81017
and user_id=22461
and attempt_id=217626
and attempt_status='F';-- contains attempt details for the test

update ota_performances
set lesson_status='P'
where performance_id=293169;

update ota_attempts set attempt_status='P'
where attempt_id=217626;

commit;
 

Can't Delete Enrollments When Attempts Exist

$
0
0


Can't Delete Enrollments When Attempts Exist

Why does one get the error "you cannot delete class because there are attempts against this class" when attempting to deleting a class?

Content attempts are a lower level of of detail, subordinate to the class catalog object. Once a learner "plays" content and a row is inserted into the "Attempts" table, the current OLM architecture prevents the catalog object from being deleted. A history will be maintained of the learning for data integrity purposes.

We can use below data Fix
select * from ota_activity_versions
where version_name like 'SkillSoft Books 24 X 7';-- course

select * from ota_events
where activity_version_id=94037;-- class

select * from OTA_OFFERINGS
where activity_version_id=94037;-- offering

select * from OTA_DELEGATE_BOOKINGS
where event_id=123019;--enrollments

select * from ota_performances
where learning_object_id=97018; -- contains test results

select * from ota_attempts
where learning_object_id=97018;

delete from ota_attempts
where learning_object_id=97018;
commit;

delete from ota_performances
where learning_object_id=97018;
commit;

Navigation to DownLoad new WebAdi Template

$
0
0
Go to Respective General Ledger Responsibility
Journals -- Launch Journal Wizard (Click on This), New page will be opened and in new page
Layout 'Functional Actuals -Multiple'
Content :   'None' and click on Create Document.  New WebAdi template will be downloaded, save to system/desktop and open Excel Sheet after doing required Excel setups(Macros etc) and login to Oracle through Excel sheet you should use this WebAdi Template 

Unable to Find Oracle Add in on WebAdi

$
0
0
Unable to Find Oracle Add in on WebAdi
When you Download the WebAdi and try to save to your Desktop and Open you might not see the Oracle AddIn on WebAdi, this issue can be resolved simple by Unprotecting your excel sheet before saving your Original WebAdi sheet.

How to Add a New Legal Entity, Ledger and Operating Unit for a New Country

$
0
0


How to Add a New Legal Entity, Ledger and Operating Unit for a New Country [ID 1064366.1]
  Solution
     Step 1 - Set Up Country Geography Hierarchy in TCA
     Step 2 - Create a Legal Entity
     Step 3 - Validate Legal Entity, Establishment and Registration
     Step 4 - Set up a Ledger for the new Legal Entity
     Step 5 - Set Up an Operating Unit
     Step 6 - Associate the Operating Unit with the Legal Establishment
     Step 7 - Run Replicate Seed Data

 References Applies to:
Oracle Legal Entity Configurator - Version: 12.0 and later   [Release: 12.0 and later ]
Oracle E-Business Tax - Version: 12.0 and later    [Release: 12.0 and later]
Oracle General Ledger - Version: 12.0 and later    [Release: 12.0 and later]
Oracle Human Resources - Version: 12.0 and later    [Release: 12.0 and later]

Information in this document applies to any platform.
Goal
E-Business Tax Information Center > EBTax Integration With EBS Modules > Legal Entity Manager > Note 1064366.1
This note was authored to provide a detailed example of the steps required to add a new Legal Entity to an existing instance.  The scenario covered is the addition of a new country to an already configured application environment. 

The original onus for this note was to provide expanded guidance for a customer attempting to configure E-Business Tax for Canada using Case Study Note 577996.1.  The steps documented within this note should also hold true for other scenarios outside of E-Business Tax.  Note that this is not intended to serve as a comprehensive note on setting up Legal Entities, Ledgers and Operating units.  Rather this is attempting to show how these objects are linked together and in doing so, remove some of the potential confusion that exists when performing this setup using the various implementation manuals for HR, GL, Legal Entity and Tax.
Solution
Step 1 - Set Up Country Geography Hierarchy in TCA

Refer to Note 554492.1 for details.  This step is required so that you can select the State/province from the list of values when defining your Address.

Step 2 - Create a Legal Entity
Create legal entities with minimum required information using the Create Legal Entity page.

If you create a legal entity from an existing organization, the country, organization name, and organization number are defaulted from the organization. In this case, the organization number is not updatable even if the HZ: Generate Party Number profile option is set to No.

When you create a legal entity, the main establishment is created automatically. The legal entity territory, name, address, effective date, and other information are defaulted to the main establishment. The establishment inherits the registration number of the legal entity only if the establishment does not have it own number.

Responsibility -  Legal Entity Manager
Navigation - "Create a Legal Entity"

Enter the required fields (See example below)

Territory: The territory where the legal entity is registered. This list displays territories at the country level and shows only territories for which the identifying jurisdiction has been defined. Therefore, the territory determines the identifying jurisdiction to which the legal entity needs to register. The territory also determines the context for the information that needs to be displayed in the General Information region.  For Canada the BIN number is one such field

How To Add New Legal Entity Registration Code For Countries That Are Not Available In The List?

For example there is no Registration Code available for country China.

Solution
Please follow the steps below to add a Registration Code for China or any other country that is
not listed in the LOV when defining Jurisdictions.

1) Log in to the responsibility 'Application Developer'.
2) Go to Menu (Application > Lookups > XLE Lookups).
3) Query for the Lookup Type XLE_REG_CODE.
4) Add a new Lookup Code for the country of your choice.
5) Save the record.
6) Bounce Apache.
7) Now log into the responsibility 'Legal Entity Manager'
8) Go to Jurisdictions (Setup > Jurisdictions)
9) Define the new Jurisdiction for the Country and select your Reg Cod from LOV.

NOTE:   These steps may also be required in order for the country to appear in the LOV for territories.  For example:  Vietnam must be added to the XLE_REG_CODE in order for the legal entity to be created.

Organization Number: The organization number is a number used to identify organizations. This field is displayed only when the HZ: Generate Party Number profile option is set to No. In this case, the main establishment organization number is built as a concatenation of the legal entity organization number and ETB (establishment). Otherwise it is not displayed and is generated automatically. For example, if the legal entity organization number entered is 12536, the establishment's organization number will be 12536ETB.

Legal Entity Identifier: The identification number used to uniquely identify the legal entity. It is displayed only when the LE: Generate Legal Entity Identifier profile option set to No and you must enter it manually. If this option is set to Yes, the legal entity identifier is generated automatically based on the International  Organization for Standardization (ISO) code of the country of registration, plus the registration number of the identifying jurisdiction, which qualifies an entity to be a legal entity in that particular territory.

For example:
Example
Territory: Singapore
ISO Country Code: SG

Registration number of the identifying jurisdiction (RCN number) = 23231 (this is a user enterable field)
If the profile option is set to Yes, the legal entity identifier will be SG23231, otherwise you are required to enter the legal entity identifier manually. If you enter an identifier that is not unique, an error message will be displayed.

Registration Number: The identifying jurisdiction determines the prompt for the registration number (in the U.S., the EIN/TIN). The Establishment registration prompt is displayed if it is defined for the identifying jurisdiction. In this case the main establishment is created with this registration number. The registration
number must be unique within a jurisdiction.

Legal Address: The address a legal entity uses to register with a legal authority. A legal entity may use different addresses for different authorities and hence, may have more than one registered address. This legal address must be located within the territory entered.

Place Of Registration: Optionally enter the place of the legal entity registration.

Inception Date Optionally enter the date of legal entity registration (creation). It can be on or before the system date and on or after legal entity's inception date but must not be a future date.

 Once the above information is entered, select "Save and add details"

Refer to Note 1104887.1 for instructions on how to configure the Address Format used for the Legal Address.


Step 3 - Validate Legal Entity, Establishment and Registration
After saving the legal entity record will be displayed as follows.

Note that in this test instance the organization number was updated.  This occurred because we have our system configured to automatically generated an organization number.

 Make sure the Registration was properly created

 Make sure the Legal Establishment was properly created


Step 4 - Set up a Ledger for the new Legal Entity
Responsibility- General Ledger Super User
Navigation - Setup : Financials : Accounting Setup Manager : Accounting Setups

Select "Create Accounting Setup" then "Add Another Row"
Select the Legal Entity created in step 2
Create the new ledger (step 1 shown below, steps 2-4 not shown)


Once finished, make sure the ledger status (circled in red) is showing with a green checkbox.  This is required in order for the next step to begin.


Refer to the Financials Implementation Guide, page 3-29 for more details on each of the configuration settings available when setting up a ledger.

Step 5 - Set Up an Operating Unit
An Operating Unit can be defined from many different responsibilities.  For this example we are using the seeded "Receivables Manager" responsibility.

Responsibility:  Receivables Manager
Navigation:  Setup : System : Organizations : Organizations

Enter the operating unit information as indicated below.  Note that you select the Location defined in the Legal Entity setup.

Once saved and with the cursor on "Operating Unit", select "Others" and then "Operating Unit Information"

Select the data as indicated below


Step 6 - Associate the Operating Unit with the Legal Establishment
Responsibility: Legal Entity Manager

From the LE manager screen, click to view the legal entity created in step 2.  Select the "Establishments" tab and then "View Details"

Once you have the establishments page open select "Associate Business Entities" and then "Update"
Add a row under "Operating Units" to link the legal establishment with the operating unit.


Step 7 - Run Replicate Seed Data
At this point the minimum setup requirements are completed.  Proceed with running replicate seed data and continue with the remainder of your implementation/configuration.

Replicate Seed Data sets defaults in the system for an operating unit after it is created

To see how to run replicate seed data, Refer to Note 134385.1 How to Run the Replicate Seed Data Program

For more details on the purpose of the seed data program refer to Note 274974.1 What Effect Does "Replicate Seed Data" concurrent request have on Appls?


References
NOTE:1104887.1 - How to Setup a Legal Address Using HR Address Formats in R12 Legal Entity Configurator
NOTE:577996.1 - Case Study: Setup R12 E-Business Tax (EBTax) for Canada: Includes 2010 HST Changes

Transactions Stuck in Shipping Transaction Form with Status next as "Interface"

$
0
0
If Interface Trip Stop Program got Terminated and Sales Order got closed but Transaction stuck in Shipping Transaction Form with Status next as “Interfaced” the follow below steps

1. Please execute below scripts  for  Duplicates

create or replace view mmt_mti_records_v as
select a.transaction_interface_id ,
a.picking_line_id from
mtl_material_transactions b,  mtl_transactions_interface a
where a.picking_line_id = b.picking_line_id
and a.trx_source_line_id = b.trx_source_line_id
and a.inventory_item_id = b.inventory_item_id
and b.transaction_type_id = a.transaction_type_id
and b.transaction_source_type_id in (2,8)
and b.picking_line_id is not null ;

create or replace view mmtt_mti_records_v as
select a.transaction_interface_id ,
a.picking_line_id from
mtl_material_transactions_temp b,  mtl_transactions_interface a
where a.picking_line_id = b.picking_line_id
and a.trx_source_line_id = b.trx_source_line_id
and a.inventory_item_id = b.inventory_item_id
and b.transaction_type_id = a.transaction_type_id
and b.transaction_source_type_id in (2,8)
and b.picking_line_id is not null ;

create or replace view mmt_mmtt_records_v as
select a.transaction_temp_id,
a.picking_line_id from
mtl_material_transactions b,  mtl_material_transactions_temp a
where a.picking_line_id = b.picking_line_id
and a.trx_source_line_id = b.trx_source_line_id
and a.inventory_item_id = b.inventory_item_id
and b.transaction_type_id = a.transaction_type_id
and b.transaction_source_type_id in ( 2,8)
and b.picking_line_id is not null;

create table mti_dup_backup as (select * from mtl_transactions_interface
where transaction_interface_id in (select transaction_interface_id from mmt_mti_records_v));

create table msni_dup_backup as (select * from mtl_serial_numbers_interface
where transaction_interface_id in (select transaction_interface_id from mmt_mti_records_v))
union
(select * from mtl_serial_numbers_interface msni where msni.transaction_interface_id in (
select mtli.serial_transaction_temp_id
from mtl_transaction_lots_interface mtli
where mtli.transaction_interface_id in (select transaction_interface_id from
mmt_mti_records_v )));

create table mtli_dup_backup as (select * from mtl_transaction_lots_interface where transaction_interface_id in (select transaction_interface_id from mmt_mti_records_v));

create table mti_dup_backup_mmtt as (select * from mtl_transactions_interface
where transaction_interface_id in (select transaction_interface_id from mmtt_mti_records_v));

create table msni_dup_backup_mmtt as (select * from mtl_serial_numbers_interface
where transaction_interface_id in (select transaction_interface_id from mmtt_mti_records_v))
union
(select * from mtl_serial_numbers_interface msni where msni.transaction_interface_id in (
select mtli.serial_transaction_temp_id
from mtl_transaction_lots_interface mtli
where mtli.transaction_interface_id in (select transaction_interface_id from
mmtt_mti_records_v )));

create table mtli_dup_backup_mmtt as (select * from mtl_transaction_lots_interface where transaction_interface_id in (select transaction_interface_id from mmtt_mti_records_v));

create table mmtt_dup_backup as (select * from mtl_material_transactions_temp
where transaction_temp_id in (select transaction_temp_id from mmt_mmtt_records_v));

create table msnt_dup_backup as
(select * from mtl_serial_numbers_temp
where transaction_temp_id in (select transaction_temp_id from mmt_mmtt_records_v))
union
(select * from mtl_serial_numbers_temp msnt where msnt.transaction_temp_id in (
select mtlt.serial_transaction_temp_id
from mtl_transaction_lots_temp mtlt
where mtlt.transaction_temp_id in (select transaction_temp_id from
mmt_mmtt_records_v )));

create table mtlt_dup_backup as (select * from mtl_transaction_lots_temp
 where transaction_temp_id in (select transaction_temp_id from mmt_mmtt_records_v ));

delete from mtl_serial_numbers_interface where transaction_interface_id
in (select transaction_interface_id from mmt_mti_records_v );

delete from mtl_serial_numbers_interface msni
where msni.transaction_interface_id in (
select mtli.serial_transaction_temp_id
from mtl_transaction_lots_interface mtli
where mtli.transaction_interface_id in (select transaction_interface_id from
mmt_mti_records_v ));

delete from mtl_transaction_lots_interface where transaction_interface_id in
(select transaction_interface_id from mmt_mti_records_v );

delete from mtl_transactions_interface where transaction_interface_id in
(select transaction_interface_id from
mmt_mti_records_v );

delete from mtl_serial_numbers_interface where transaction_interface_id
in (select transaction_interface_id from mmtt_mti_records_v );

delete from mtl_serial_numbers_interface msni
where msni.transaction_interface_id in (
select mtli.serial_transaction_temp_id
from mtl_transaction_lots_interface mtli
where mtli.transaction_interface_id in (select transaction_interface_id from
mmtt_mti_records_v ));

delete from mtl_transaction_lots_interface where transaction_interface_id in
(select transaction_interface_id from mmtt_mti_records_v );

delete from mtl_transactions_interface where transaction_interface_id in
(select transaction_interface_id from
mmtt_mti_records_v );

delete from mtl_serial_numbers_temp where transaction_temp_id
in (select transaction_temp_id from mmt_mmtt_records_v );

delete from mtl_serial_numbers_temp msnt
where msnt.transaction_temp_id in (
select mtlt.serial_transaction_temp_id
from mtl_transaction_lots_temp mtlt
where mtlt.transaction_temp_id in (select transaction_temp_id from
mmt_mmtt_records_v ));

delete from mtl_transaction_lots_temp where transaction_temp_id in
(select transaction_temp_id from mmt_mmtt_records_v );

delete from mtl_material_transactions_temp where transaction_temp_id in
(select transaction_temp_id from mmt_mmtt_records_v );

COMMIT;
 

2. Review and commit.

3. Then run the below 3 queries  -

select a.transaction_interface_id ,
a.picking_line_id from
mtl_material_transactions b,  mtl_transactions_interface a
where a.picking_line_id = b.picking_line_id
and a.trx_source_line_id = b.trx_source_line_id
and a.inventory_item_id = b.inventory_item_id
and b.transaction_type_id = a.transaction_type_id
and b.transaction_source_type_id in (2,8)
and b.picking_line_id is not null ;

select a.transaction_interface_id ,
a.picking_line_id from
mtl_material_transactions_temp b,  mtl_transactions_interface a
where a.picking_line_id = b.picking_line_id
and a.trx_source_line_id = b.trx_source_line_id
and a.inventory_item_id = b.inventory_item_id
and b.transaction_type_id = a.transaction_type_id
and b.transaction_source_type_id in (2,8)
and b.picking_line_id is not null ;

select a.transaction_temp_id,
a.picking_line_id from
mtl_material_transactions b,  mtl_material_transactions_temp a
where a.picking_line_id = b.picking_line_id
and a.trx_source_line_id = b.trx_source_line_id
and a.inventory_item_id = b.inventory_item_id
and b.transaction_type_id = a.transaction_type_id
and b.transaction_source_type_id in ( 2,8)
and b.picking_line_id is not null;

4. If none return records, follow with the below steps .

5. Run the below query to reprocess the transactions from TEMP -

update MTL_MATERIAL_TRANSACTIONS_TEMP
set TRANSACTION_MODE = 3,
LOCK_FLAG = 'N',
PROCESS_FLAG = 'Y',
ERROR_CODE = NULL,
ERROR_EXPLANATION = NULL
where transaction_mode = 8;

6. Review the updated transactions.  Then issue a commit:
commit;

7. Please resubmit the transaction from

Inventory -> Transactions -> Pending Transactions, Query for stuck transactions for this item, and resubmit by selecting Tools -> Resubmit All.

Note: Ensure that you have the transaction managers (Inventory -> Setup -> Transactions -> Interface Managers - Material Transaction Manager) up and running.


Check if all Transactions got Processed successfully

Email Notifications are not getting received to company Emails from Oracle Workflow

$
0
0
Issue Might be with 'Workflow Notification Mailer was hung and stopped processing.'  If we did stop/start the Workflow Notification mailer and lo and behold which resolved the issue, after this Emails will Flow to the Company Emails successfully 

The following script will get rid of outstanding reservation records that exist for order lines which are closed or cancelled

$
0
0
Negative Qty Showing on OnHand Qty Form for Items

The following script will get rid of outstanding  reservation records that exist for order lines which are closed or cancelled. For both external sales orders and internal orders. Also script cleans reservations left after Order line is deleted
REM but reservations exist
 Script deletes from mtl_demand which are not in sync with Mtl_reservations.

If Qty is Showing Negative on OnHand QTy Form for Items than we might need to execute below script

SELECT  V.PROFILE_OPTION_VALUE OE_PROFILE
FROM    FND_PROFILE_OPTION_VALUES V
WHERE   (V.PROFILE_OPTION_ID, V.APPLICATION_ID, V.LEVEL_ID) =
                (SELECT V2.PROFILE_OPTION_ID,V2.APPLICATION_ID,MAX(V2.LEVEL_ID)
                FROM FND_PROFILE_OPTIONS OO,
                     FND_PROFILE_OPTION_VALUES V2
                WHERE ((V2.LEVEL_ID = 10001 AND V2.LEVEL_VALUE=0)
                          OR (V2.LEVEL_ID = 10002 AND V2.LEVEL_VALUE=660))
                AND   OO.PROFILE_OPTION_ID = V2.PROFILE_OPTION_ID
                AND   OO.APPLICATION_ID = V2.APPLICATION_ID
                AND   OO.APPLICATION_ID = 660
                AND   UPPER(OO.PROFILE_OPTION_NAME) = 'ONT_SOURCE_CODE'
                GROUP BY V2.PROFILE_OPTION_ID, V2.APPLICATION_ID)
AND   V.LEVEL_VALUE = DECODE(V.LEVEL_ID, 10001, 0, 10002, 660);

PROMPT ** This gets rid of extraneous demand and reservations that are left
PROMPT ** after a line has been cancelled  

SELECT L.LINE_ID, L.HEADER_ID
FROM OE_ORDER_LINES_ALL L, MTL_RESERVATIONS M
WHERE  M.PRIMARY_RESERVATION_QUANTITY>0
AND nvl(L.CANCELLED_FLAG,'N')='Y'
AND L.CANCELLED_QUANTITY IS NOT NULL
AND L.LINE_ID = M.DEMAND_SOURCE_LINE_ID
AND NOT EXISTS (SELECT NULL FROM MTL_TRANSACTIONS_INTERFACE MTI
                WHERE  MTI.TRX_SOURCE_LINE_ID = L.LINE_ID
                AND    MTI.SOURCE_HEADER_ID = L.HEADER_ID
                AND    MTI.SOURCE_CODE = '&OE_SOURCE_CODE');


UPDATE MTL_RESERVATIONS
SET    PRIMARY_RESERVATION_QUANTITY = 0
,      RESERVATION_QUANTITY = 0
,      LAST_UPDATED_BY=-2471362
WHERE  PRIMARY_RESERVATION_QUANTITY>0
AND    EXISTS (SELECT 'X'
               FROM   OE_ORDER_LINES_ALL L
               WHERE  nvl(L.CANCELLED_FLAG,'N')='Y'
               AND L.CANCELLED_QUANTITY IS NOT NULL
               AND L.LINE_ID = MTL_RESERVATIONS.DEMAND_SOURCE_LINE_ID
               AND NOT EXISTS (SELECT NULL FROM MTL_TRANSACTIONS_INTERFACE MTI
                               WHERE  MTI.TRX_SOURCE_LINE_ID = L.LINE_ID
                               AND    MTI.SOURCE_HEADER_ID = L.HEADER_ID
                               AND    MTI.SOURCE_CODE = '&OE_SOURCE_CODE'));



PROMPT ** This gets rid of extraneous demand and reservations that are left
PROMPT ** after a line has been closed or delivery detail is cancelled

SELECT L.LINE_ID, L.HEADER_ID
FROM OE_ORDER_LINES_ALL L, MTL_RESERVATIONS M
WHERE   M.PRIMARY_RESERVATION_QUANTITY>0
AND nvl(L.OPEN_FLAG,'Y')='N'
AND L.LINE_ID = M.DEMAND_SOURCE_LINE_ID
AND NOT EXISTS (SELECT NULL FROM MTL_TRANSACTIONS_INTERFACE MTI
                WHERE  MTI.TRX_SOURCE_LINE_ID = L.LINE_ID
                AND    MTI.SOURCE_HEADER_ID = L.HEADER_ID
                AND    MTI.SOURCE_CODE = '&OE_SOURCE_CODE')
AND NOT EXISTS              (SELECT 1 FROM WSH_DELIVERY_DETAILS WDD
                 WHERE WDD.SOURCE_LINE_ID=L.LINE_ID
                   AND WDD.SOURCE_CODE ='OE'
                   AND WDD.INV_INTERFACED_FLAG IN ('N','P')
                   AND WDD.RELEASED_STATUS <> 'D');


UPDATE MTL_RESERVATIONS
SET    PRIMARY_RESERVATION_QUANTITY = 0
,      RESERVATION_QUANTITY = 0
,      LAST_UPDATED_BY=-2471362
WHERE  PRIMARY_RESERVATION_QUANTITY>0
AND    EXISTS (SELECT 'X'
               FROM   OE_ORDER_LINES_ALL L
               WHERE  nvl(L.OPEN_FLAG,'Y')='N'
               AND L.LINE_ID = nvl(MTL_RESERVATIONS.DEMAND_SOURCE_LINE_ID,-99)
               AND NOT EXISTS (SELECT NULL FROM MTL_TRANSACTIONS_INTERFACE MTI
                               WHERE  MTI.TRX_SOURCE_LINE_ID = L.LINE_ID
                               AND    MTI.SOURCE_HEADER_ID = L.HEADER_ID
                               AND    MTI.SOURCE_CODE = '&OE_SOURCE_CODE')
               AND NOT EXISTS               (SELECT 1 FROM WSH_DELIVERY_DETAILS WDD
                 WHERE WDD.SOURCE_LINE_ID=L.LINE_ID
                   AND WDD.SOURCE_CODE ='OE'
                   AND WDD.INV_INTERFACED_FLAG IN ('N','P')
                   AND WDD.RELEASED_STATUS <> 'D'));



PROMPT ORDER DETAILS WITH ORPHAN RESERVATIONS AFTER LINE IS DELETED

SELECT MSO.SEGMENT1 ORD_NUMBER,
       MSO.SEGMENT2 ORD_TYPE,
       MSO.SALES_ORDER_ID sALES_ORDER_ID,
       MR.DEMAND_SOURCE_LINE_ID oRDER_LINE_ID,
       MR.iNVENTORY_ITEM_ID iTEM_ID,
       MR.ORGANIZATION_ID ORGANIZATION_ID,
       MR.PRIMARY_RESERVATION_QUANTITY pRSV_QTY,
       MR.RESERVATION_QUANTITY RSV_QTY
 FROM MTL_RESERVATIONS MR,
      MTL_SALES_ORDERS MSO
WHERE MSO.SALES_ORDER_ID=MR.DEMAND_SOURCE_HEADER_ID
  AND MR.DEMAND_SOURCE_TYPE_ID IN (2,8)
  AND MR.DEMAND_SOURCE_LINE_ID NOT IN (SELECT LINE_ID FROM OE_ORDER_LINES_ALL
                                         WHERE LINE_ID=MR.DEMAND_SOURCE_LINE_ID );


PROMPT UPDATING MTL_RESERVATIONS

UPDATE MTL_RESERVATIONS MR
SET PRIMARY_RESERVATION_QUANTITY=0,
    RESERVATION_QUANTITY=0,
    LAST_UPDATED_BY=-2471362
   WHERE MR.DEMAND_SOURCE_TYPE_ID IN (2,8)
     AND MR.DEMAND_SOURCE_LINE_ID NOT IN (SELECT LINE_ID FROM OE_ORDER_LINES_ALL
                                            WHERE LINE_ID=MR.DEMAND_SOURCE_LINE_ID);
COMMIT;

PROMPT **Updating records for closed /cancelled lines in mtl_demand where records are not in sync
UPDATE MTL_DEMAND D
SET    PRIMARY_UOM_QUANTITY = 0
,      LINE_ITEM_QUANTITY   = 0
,      COMPLETED_QUANTITY   = 0
,      LINE_ITEM_RESERVATION_QTY = 0
,      RESERVATION_QUANTITY = 0
,      LAST_UPDATED_BY=-2471362
WHERE  DEMAND_SOURCE_TYPE IN (2,8)
AND RESERVATION_TYPE = 2
AND    DEMAND_SOURCE_LINE = ( SELECT O.LINE_ID
                                FROM OE_ORDER_LINES_ALL O
                                WHERE  ( NVL(o.OPEN_FLAG,'Y') = 'N'
                                         OR NVL(O.CANCELLED_FLAG,'N') ='Y')
                                AND  O.LINE_ID =D.DEMAND_SOURCE_LINE )
AND   DEMAND_SOURCE_LINE NOT IN  ( select TRX_SOURCE_LINE_ID
                    FROM  MTL_TRANSACTIONS_INTERFACE MTI
                    WHERE  MTI.SOURCE_LINE_ID = D.DEMAND_SOURCE_LINE)
AND DEMAND_SOURCE_LINE NOT IN (SELECT SOURCE_LINE_ID
                   FROM WSH_DELIVERY_DETAILS WDD
                 WHERE WDD.SOURCE_LINE_ID=D.DEMAND_SOURCE_LINE
                   AND WDD.SOURCE_CODE='OE'
                   AND WDD.INV_INTERFACED_FLAG IN ('N','P'));

PROMPT FINAL UPDATING MTL_DEMAND

UPDATE MTL_DEMAND SET PRIMARY_UOM_QUANTITY=0,
                      COMPLETED_QUANTITY=0,
                      RESERVATION_QUANTITY=0,
                      LAST_UPDATED_BY=-2471362
       WHERE DEMAND_SOURCE_TYPE IN (2,8)
         AND RESERVATION_TYPE=2
         AND DEMAND_ID IN (SELECT N_COLUMN1 FROM MTL_RESERVATIONS WHERE
                                    DEMAND_SOURCE_TYPE_ID IN (2,8)
                                AND PRIMARY_RESERVATION_QUANTITY=0
                                AND RESERVATION_QUANTITY=0
                                AND LAST_UPDATED_BY=-2471362);



PROMPT **Deleting reservations which are complete

COMMIT;

DELETE FROM MTL_RESERVATIONS WHERE
       DEMAND_SOURCE_TYPE_ID IN (2,8)
 AND   LAST_UPDATED_BY=-2471362;

PROMPT **Deleting records from mtl_demand where reservations are complete

DELETE FROM MTL_DEMAND WHERE
    DEMAND_SOURCE_TYPE IN (2,8)
AND RESERVATION_TYPE=2     
AND LAST_UPDATED_BY=-2471362;


What do the transaction mode (like transaction_mode = 8) numbers mean in the pending transactions table (MTL_MATERIAL_TRANSACTIONS_TEMP)?

$
0
0


What do the transaction mode (like transaction_mode = 8) numbers mean in the pending transactions table (MTL_MATERIAL_TRANSACTIONS_TEMP)?

Goal
What do the transaction mode numbers mean in the pending transactions table (MTL_MATERIAL_TRANSACTIONS_TEMP)?

Solution
The pending transactions can be found in the pending transactions form available from Inventory > Transactions > Pending Transactions or by looking directly in the pending transactions table (MTL_MATERIAL_TRANSACTIONS_TEMP).  The transaction modes have the following meanings:

Transaction Mode Number / Description
NULL or 1:  Online Processing
2:  Concurrent Processing
3:  Background Processing
8:  Internal Processing (Not visible in the pending transactions form)

Explanation
Here is an explanation of each:

NULL or 1:  Online Processing
Online processing is used by the Oracle Applications to immediately process records. This does not require that a concurrent program be run. The Transaction Manager does not process transactions marked for online processing.

2: Concurrent Processing
Transactions marked as concurrent transaction mode are processed by a dedicated transaction worker to explicitly process a set of transactions. The Transaction Manager does not process transactions marked for concurrent processing.

3: Background Processing
Interface transactions marked for Background processing will be picked up by the transaction manager polling process and assigned to a transaction worker. These transactions will not be processed unless the transaction manager is running.

8:  Internal Processing
Transaction mode 8 is not a mode normally visible to the user as it is used for internal processing.  Transactions with this mode are not visible in the Pending transactions form. Transaction_mode of 8 is used internally to identify if records came from the interface table to the pending table or came directly into the pending table.

** If you find stuck transactions with a mode of 8, you should log a Service Request with Oracle Support to get assistance processing these records.  This is often caused by transactions that exist both in the transaction open interface and in the pending transactions table.  In such a case, the transaction open interface records would be removed and the pending transactions would be processed by resetting the transaction mode to 3: Background Processing.

Identification
The following script can be used to identify the corrupted records in case the duplicate scripts do not return any data:

SELECT msi.segment1, tmp.PROCESS_FLAG, tmp.LOCK_FLAG,
tmp.TRANSACTION_MODE, tmp.ERROR_CODE, tmp.transaction_quantity,
to_char(tmp.transaction_date,'dd-mm-yyyy hh24:mi:ss')
FROM mtl_material_transactions_temp tmp, mtl_system_items_b msi
WHERE transaction_mode = 8
AND tmp.inventory_item_id = msi.inventory_item_id
AND msi.organization_id = &organization_id

WORKLIST PROXY - PURCHASE REQUISITION APPROVAL

$
0
0

WORKLIST  PROXY-  PURCHASE  REQUISITION  APPROVAL

WorklistAccessisusedtograntanotheruserproxyaccesstoapproverequisitionsonbehalfofan Approver.  Accesscanbegrantedforaspecificperiodorindefinitely.  Theproxyuserwillonlybeableto viewandtakeactiononnotificationsforpurchaserequisitionapprovals.  Requisitionscanberejected, approved,orreassignedtoadifferentuserto takeaction.  Aproxyuserwillberestrictedfromapproving or re-assigningarequisitiontheysubmittedtopreventtheapprovalprocessfrombeingbypassedinOracle.
Asecondaryproxyuserisrecommendediftheuserbeinggrantedaccessforapprovalsalsosubmits
purchaserequisitionsthatrequireapprovalbytheApprover.

ToGrantProxyAccess ToAWorklist:

1.  Gotothe'NotificationsSummary'selectiononthemainNavigatormenu
2.   Choosethe'WorklistAccess'linkonthelowerlefthandsideoftheNotificationsscreen
3 Selectthe'GrantWorklistAccess'button

Name:Selectionontheleftwilldefaultto'AllEmployeesAndUsers'.  Inthefieldto theright usethesearchfunctiontoselecttheuserbeinggrantedWorklistaccess

Description:Titletheproxy"POReqApproval-  EnterNameOfUsef'

StartDate:Enterthestartdate theuserwillbegrantedproxyaccess

EndDate:Entertheenddatetheuserwillbenolongerbegrantedproxyaccess.  Leavethis fieldblanktogranttheuserindefiniteproxyaccess

GrantAccessTo:Enabletheoption'SelectedItemTypes'.  Movethechoice'POApproval' fromAvailableItemTypesto theSelectedItemTypessection

4.   Selectthe'Apply'button

Tograntproxyaccesstoadditionalusersselectthe'GrantWorklistAccess'button andrepeatthesteps. Choosethe'CloseWindow'linkintheupperrightsection of thescreenwhendonetoreturntothemain menu.
worklist:
1.  Goto the'NotificationsSummary'selectiononthemainNavigatormenu
2.   Selectthe'SwitchUser'button
3.   SelecttheApprover'sWorklisttobeaccessed
4.   Selectthe'Apply'button
 
WorklistNotificationsforrequisitionapprovalsshouldnowbevisible.  Openthelinkforeachnotification, reviewtheinformation,andselecttheappropriateactionbuttontoApprove,Reject,orReassign.


Choosethe'CloseWindow'linkintheupperrightsection of thescreenwhen

Purpose and usage of Tax Rate Variance Account

$
0
0


Purpose and usage of Tax Rate Variance Account.

Tax Rate Variance reflects the tax variance between the invoice and the PO distributions due to difference in tax applicability.

Tax Rate Variance is normally computed for the Non recoverable portion of the Tax. It is computed in two cases:

a) When there is a difference in the Tax amount of the PO and Invoice.
For Example: PO# 122046
Lines Amount: 14.49
Tax Amount: 1.16
Total Amount: 15.65

-----------------------------------

AP invoice# 135324
Item Amount: 14.49
Freight Amount: 14.62
Tax Amount: 0
Total Amount: 29.11
Tax Rate Variance: 1.16

In this case, Tax is calculated on PO# 122046 which is 1.16. But, on invoice there is no tax calculated. Hence, the Tax Rate Variance account recorded the difference in tax amount 1.16.

b) When there is a difference in the Taxes computed (for instance an extra tax calculated on Invoice and the same did not exist in PO).

For Example: On PO# 121985
Lines Amount: 57.62
Tax Amount: 4.60 (State Level Tax: 2.30 + County level Tax: 2.30)
Total amount: 62.22

----------------------------------------

On AP Invoice# FJ17597
Item Amount: 57.62
Freight Amount: 13.71
Tax Amount: 5.70 (State Level Tax: 2.85 + County Level Tax: 2.85)
Total Amount: 77.03

Here the applicable tax rate is 4 and State Level and County level tax is calculated in following way.

Tax for Items+Freight (57.62+13.71) = 71.33 * 0.04 = 2.85
If tax is calculated only for Freight: 13.71 * 0.04 = 0.54
Difference of Total tax and Freight Tax (2.85 - 0.54) = 2.31 which has 0.01 difference from the tax on PO.

Hence, Tax Rate Variance account has recorded the tax variance amount on Invoice Distributions as 0.01.

@Article Submitted  by Amrutha

Unable to access Diagnostics through Oracle forms

$
0
0
Unable to access Diagnostics through Oracle forms

Reference of action: open form choose help>diagnostics>forms personalization and receive "Your responsibility does not have permissions. Contact System Administrator".

Changed: 'FND: Diagnostics' and 'Utilities:Diagnostics' to Yes on site level.

Found that above profiles were disabled on responsibility level "US Quality Super User".  Which has Issue
For now "Help > Diagnostics > Examine" should be accessible for any user.
We can setup this access for any specific user also 

Oracle Pending Transaction Queries

$
0
0

Oracle Pending Transaction Queries
Unprocessed Material:
SELECT *
  FROM mtl_material_transactions_temp
 WHERE     organization_id = :p_org_id
       AND transaction_date < TO_DATE ('31.12.2012', 'dd.mm.rrrr') --period close date
       AND NVL (transaction_status, 0) <> 2 -- 2 indicates a save-only status;

Uncosted Material/WSM:
SELECT  /*+ INDEX (MMT MTL_MATERIAL_TRANSACTIONS_N10) */     *
  FROM mtl_material_transactions MMT
 WHERE     organization_id = :p_org_id
       AND transaction_date <= TO_DATE ('31.12.2012', 'dd.mm.rrrr') --period close date
       AND costed_flag IS NOT NULL;

Pending WIP Costing:
SELECT *
  FROM wip_cost_txn_interface
 WHERE organization_id = :p_org_id
       AND transaction_date <= TO_DATE ('31.12.2012', 'dd.mm.rrrr'); --period close date

Pending WSM Interface:
SELECT *
  FROM wsm_split_merge_txn_interface
 WHERE     organization_id = :p_org_id
       AND process_status <> wip_constants.completed
       AND transaction_date <= TO_DATE ('31.12.2012', 'dd.mm.rrrr'); --period close date

Pending LCM Interface:
/* Support for Landed Cost Management: Pending landed cost adjustment transactions */
SELECT *
  FROM cst_lc_adj_interface
 WHERE organization_id = :p_org_id
       AND transaction_date <= TO_DATE ('31.12.2012', 'dd.mm.rrrr'); --period close date

Pending Receiving:
SELECT *
  FROM rcv_transactions_interface
 WHERE     to_organization_id = :p_org_id
       AND transaction_date <= TO_DATE ('31.12.2012', 'dd.mm.rrrr') --period close date
       AND destination_type_code IN ('INVENTORY', 'SHOP FLOOR');

Pending Material:
SELECT *
  FROM mtl_transactions_interface
 WHERE     organization_id = 102
       AND transaction_date <= TO_DATE ('31.12.2012', 'dd.mm.rrrr') --period close date
       AND process_flag <> 9;

Pending Shop Floor Move:
SELECT *
  FROM wip_move_txn_interface
 WHERE organization_id = :p_org_id
       AND transaction_date <= TO_DATE ('31.12.2012', 'dd.mm.rrrr');

Incomplete Work Orders : If the maintenance is enabled in mtl parameters.eam_enabled_flag = ‘Y’

SELECT *
  FROM wip_discrete_jobs WDJ, wip_entities WE
 WHERE WDJ.organization_id = :p_org_id
       AND WDJ.scheduled_completion_date <=TO_DATE ('31.12.2012', 'dd.mm.rrrr') --period close date
       AND WDJ.status_type = 3                                     -- Released
       AND WDJ.wip_entity_id = WE.wip_entity_id
       AND WDJ.organization_id = WE.organization_id
       AND WE.entity_type = 6                       -- Maintenance Work Order;
Viewing all 116 articles
Browse latest View live