↧
Oracle Inventory Subinventories and Locators Table Links
↧
Script to Push Performance Appraisal back to Manager
Use below queries to push performance appraisal back to managers
SELECT pap1.full_name appraiser,
Pa.Appraisal_Id,
Pap.Full_Name,
Pa.Appraisal_System_Status,
Pa.Appraiser_Person_Id,
Pa.Appraisee_Person_Id,
Pa.Appraisal_Template_Id,
Pat.Name,
Pa.Appraisal_Period_Start_Date,
Pa.Appraisal_Period_End_Date
FROM Per_Appraisals Pa,
Per_All_People_F Pap ,
Per_Appraisal_Templates Pat,
per_all_people_f pap1
WHERE Pa.Appraiser_Person_Id=20780
--and appraisee_person_id=27405
AND Pap.Person_Id =Pa.Appraisee_Person_Id
AND Pap1.Person_Id =Pa.Appraiser_Person_Id
AND Pat.Appraisal_Template_Id=Pa.Appraisal_Template_Id
AND TRUNC(Sysdate) BETWEEN TRUNC(Pap.Effective_Start_Date) AND TRUNC(Pap.Effective_End_Date)
AND TRUNC(Sysdate) BETWEEN TRUNC(Pap1.Effective_Start_Date) AND TRUNC(Pap1.Effective_End_Date)
ORDER BY Pap.Full_Name;
UPDATE per_appraisals pa
SET system_params = SUBSTR(system_params,1,instr(pa.system_params,'pItemKey=')-2),
Appraisal_System_Status = 'ONGOING'
WHERE Pa.Appraisal_Id IN (330409,330396);
SELECT pap1.full_name appraiser,
Pa.Appraisal_Id,
Pap.Full_Name,
Pa.Appraisal_System_Status,
Pa.Appraiser_Person_Id,
Pa.Appraisee_Person_Id,
Pa.Appraisal_Template_Id,
Pat.Name,
Pa.Appraisal_Period_Start_Date,
Pa.Appraisal_Period_End_Date
FROM Per_Appraisals Pa,
Per_All_People_F Pap ,
Per_Appraisal_Templates Pat,
per_all_people_f pap1
WHERE Pa.Appraiser_Person_Id=20780
--and appraisee_person_id=27405
AND Pap.Person_Id =Pa.Appraisee_Person_Id
AND Pap1.Person_Id =Pa.Appraiser_Person_Id
AND Pat.Appraisal_Template_Id=Pa.Appraisal_Template_Id
AND TRUNC(Sysdate) BETWEEN TRUNC(Pap.Effective_Start_Date) AND TRUNC(Pap.Effective_End_Date)
AND TRUNC(Sysdate) BETWEEN TRUNC(Pap1.Effective_Start_Date) AND TRUNC(Pap1.Effective_End_Date)
ORDER BY Pap.Full_Name;
UPDATE per_appraisals pa
SET system_params = SUBSTR(system_params,1,instr(pa.system_params,'pItemKey=')-2),
Appraisal_System_Status = 'ONGOING'
WHERE Pa.Appraisal_Id IN (330409,330396);
↧
↧
“Inventory transaction worker” Program
Open Transaction Interface supports following type of transactions:
· Inventory issues and receipts (including user-defined transaction types)
· Subinventory transfers
· Direct inter-organization transfers
· In transit Shipments
· WIP component issues and returns
· WIP assembly completions and returns
· Sales Order shipments
· Inventory Average Cost Updates
· With a miscellaneous transaction users can issue material to or receive material from general ledger accounts in your current organization
What is the difference between "Transaction Open Interface" and "Pending Transactions"
· Navigate Inventory Responsibility -> Transactions -> Transaction Open Interface
This form queries the MTL_TRANSACTIONS_INTERFACE table
· Navigate Inventory Responsibility -> Transactions -> Pending Transactions
This form queries the MTL_MATERIAL_TRANSACTIONS_TEMP table
Q. What is the MTL_TRANSACTIONS_INTERFACE table used for?
A. This is the Interface between non-Inventory applications and the Inventory Transactions module.
In other words any other module other than Inventory that wants to update Inventory has to come through this table. Modules such as WIP (Work In Progress) and OE (Order Entry) first pass their records to the MTL_TRANSACTIONS_INTERFACE (MTI) for validation.
The Transactions Manager (INCTCM) reads records from the MTI table, validates them and moves the successful transactions into the MTL_MATERIAL_TRANSACTIONS_TEMP table, and submits Transaction workers (sub-processes - INCTCW) which then process these records through inventory. This process consists of data derivation, validation, and the transfer of records from MTL_TRANSCTIONS_INTERFACE, MTL_TRANSACTIONS_LOTS_INTERFACE and MTL_SERIAL_NUMBERS_INTERFACE into their associated TEMP (temporary) tables from where the transactions processor processes them.
Q. What is the MTL_MATERIAL_TRANSACTIONS_TEMP table used for?
A. The transactions are passed to the MTL_MATERIAL_TRANSACTONS_TEMP table after initial validation by the Transactions Manager (INCTCM) from the MTL_TRANSACTIONS_INTERFACE. A job id is attached and a Transactions Worker (INCTCW) is submitted by the INCTCM process to get the records processed and moved to the MTL_MATERIAL_TRANSACTONS table.
This table is also used by the Inventory and Purchasing modules which write transactions directly into this table after validation.
Inventory Module Forms like the Miscellaneous transactions form write directly into this table. The transactions which are created through this form are via on-line processing. It is from this table that the inventory quantities finally get updated and serial/lot numbers get updated.
Navigation Inventory:Transactions >Transaction Open Interface
Click in the check box under the "Submit" column then Save
↧
Interface Trip Stop Functionality
There are typically four interface program get triggered at the time of ship confirm. They are
Interface Trip stop
Packing Slip Report
Bill of Lading
Invoice
Interface Trip Stop is one of the main interface programs which can be triggered at the time of ship confirm or later as Interface Trip stop - SRS concurrent request.
Interface trip stop has two parts
Order Management Interface (First part)
Inventory Interface (Second part)
Order Management Interface part update the order management tables like OE_ORDER_LINES_All (Update Shipped_Quantity, Shipping_Quantity, Actual_Shipment_Date) and also WSH_DELIVERY_DETAILS (make Released_status, OE_INTERFACED_FLAG = ‘Y’) table.
The Inv_Interfaced_Flag remains = X (Pending) or N which will changes to Y after execution of second part
The second part i.e. Inventory Interface will be triggered only if the value of OE_INTERFACED_FLAG = ‘Y’ otherwise second part will not be triggered. Even if you try to run this from SRS, these lines will not be picked for processing.
Inventory Interface part move data from MTL_TRANSACTIONS_INTERFACE to MTL_MATERIAL_TRANACTIONS and MTL_MATERIAL_TRANSACTIONS is updated with Sales Order Issue transaction. Also data is deleted from MTL_DEMAND, MTL_RESERVATIONS and WSH_NEW_DELIVERIES. Item quantity reduced from MTL_ONHAND_QUANTITIES and
MTL_TRANSACTION_ACCOUNTS is updated with accounting information.
Both these parts are executed simultaneously.
Interface Trip stop
Packing Slip Report
Bill of Lading
Invoice
Interface Trip Stop is one of the main interface programs which can be triggered at the time of ship confirm or later as Interface Trip stop - SRS concurrent request.
Interface trip stop has two parts
Order Management Interface (First part)
Inventory Interface (Second part)
Order Management Interface part update the order management tables like OE_ORDER_LINES_All (Update Shipped_Quantity, Shipping_Quantity, Actual_Shipment_Date) and also WSH_DELIVERY_DETAILS (make Released_status, OE_INTERFACED_FLAG = ‘Y’) table.
The Inv_Interfaced_Flag remains = X (Pending) or N which will changes to Y after execution of second part
The second part i.e. Inventory Interface will be triggered only if the value of OE_INTERFACED_FLAG = ‘Y’ otherwise second part will not be triggered. Even if you try to run this from SRS, these lines will not be picked for processing.
Inventory Interface part move data from MTL_TRANSACTIONS_INTERFACE to MTL_MATERIAL_TRANACTIONS and MTL_MATERIAL_TRANSACTIONS is updated with Sales Order Issue transaction. Also data is deleted from MTL_DEMAND, MTL_RESERVATIONS and WSH_NEW_DELIVERIES. Item quantity reduced from MTL_ONHAND_QUANTITIES and
MTL_TRANSACTION_ACCOUNTS is updated with accounting information.
Both these parts are executed simultaneously.
↧
Oracle Work in Process – Discrete Job Interface (WIP Mass Load) Common Errors
The following are some of the general errors we will be getting while running the WIP Mass Load
1. Invalid or missing WIP Accounting Class
ANS): Set a default WIP accounting class in the WIP parameters for the organization.
2. Invalid value for Scheduling Method
ANS): Normally you will get this kind of error when the ALLOW_EXPLOSION is set to No and no value was assigned to SECHDULING_METHOD. Routing based scheduling cannot be done if BOM explosion is not allowed. Please change the scheduling method to manual, and provide start and completion dates, or set the ALLOW_EXPLOSION to Y.
3. System cannot add or change operation because requested department_id does not exist in bom_departments table.
ANS): We will get this kind of error in case we missed to provide department information while adding the operation or the department we have provided is not in the same organization.
4. Invalid resource. Check Bom_Resources table. Resource does not exist in Bom_resources table.
ANS): We will get this kind of error in case the resource you are adding is not in the operation department. You need to make sure that the resource is already attached to the department which is available for the operation.
5. System cannot add resource or material because the requested operation_seq_num does not exist
ANS): You will be getting this error incase if you are trying to enter the resource/component to an operations which is not exists against the discrete job.
6. System cannot add or change material requirement because requested job/operation_seq_num /inventory_item_id_new combo has already existed
ANS): If a particular component is already exists and you are trying to add same component is again using detail interface, you will be getting this error. You should be careful enough, such that you should not add a component with the job, operation_seq_num, and inventory_item_id_new combination if the same is already exists in the discrete job.
7. Cannot read value for profile option RPM_CONC_PROCESS_ID in routine &ROUTINE.
ANS): There are multiple possibilities for getting such errors. Make sure that all the following setups are place a. When updating a job through interface by inserting rows in the table WIP_JOB_DTLS_INTERFACE ensures that there is a corresponding operation_seq_num in WIP_OPERATIONS. When updating the components of the current job, the operation_seq_num should exist for that job in the table WIP_OPERATIONS. b. Please make sure that you have done proper WIP setup c. Check whether the current accounting period is open or not. If not please open the accounting periods where the job dates falls. The navigation for checking the accounting period status is Inventory - Accounting Close Cycle - Inventory Period
8. Exiting with warning! calling mrepgrm_end_program 1
ANS): There are multiple possibilities for getting this type of errors. Make sure that all the following precautions were taken care. a. Please check the profile option INV: Dynamic Precision Option for Quantity on Reports to a valid value at site level. This profile should not have null value. b. If you are releasing the planned order from ASCP, please check whether the default job class is set or not. You can use the following steps for achieving this. ==>Navigate: Adv Supply Chain Planner -> Supply Chain Plan -> Workbench ==>Once the organization is selected, go Tools > Preferences ==>Set a Default Job Class c. Check whether the accounting period is open or not
↧
↧
Oracle Serial Number
Here is a list of common serial number statuses and ids:
Status Codes (ID and Description)
---------------------
1 Defined but not used
3 Resides in stores
4 Issued out of stores
5 Resides in intransit
6 Pending status
7 Resides in receiving
8 Resides in WIP
You can get a full list of the codes with the following SQL:
SELECT
lookup_type,
lookup_code,
meaning
FROM mfg_lookups
WHERE lookup_type = 'SERIAL_NUM_STATUS'
ORDER BY lookup_type, lookup_code;
Here is a list of common serial control code ids and there descriptions:
Control Codes (ID and Description)
---------------------
1 No serial number control
2 Predefined serial numbers
5 Dynamic entry at inventory receipt
6 Dynamic entry at sales order issue
You can get a full list of the codes with the following SQL
SELECT
lookup_type,
lookup_code,
meaning
FROM mfg_lookups
WHERE lookup_type = 'MTL_SERIAL_NUMBER'
ORDER BY lookup_type, lookup_code;
Here is a version of the query from R12.1 - The actual query is against the view RCV_TRX_INT_SERIALS_V but the SQL below shows the underlying tables: (Receiving Transaction Form)
SELECT rss.serial_num
FROM rcv_serials_supply rss, rcv_shipment_lines rsl
WHERE rss.shipment_line_id = rsl.shipment_line_id
AND upper(serial_num) LIKE '&yourserial')
AND rss.shipment_line_id = &yourshiplineid
AND (rss.lot_num IS NULL OR rss.lot_num = '&YourLot')
AND EXISTS
(SELECT 1
FROM mtl_serial_numbers msn
WHERE msn.serial_number = rss.serial_num
AND msn.current_status = 5
AND (msn.group_mark_id IS NULL
OR msn.group_mark_id = -1)
AND (msn.line_mark_id IS NULL
OR msn.line_mark_id = -1)
AND (msn.lot_line_mark_id IS NULL
OR msn.lot_line_mark_id = -1)
AND msn.inventory_item_id = rsl.item_id
)
ORDER BY rss.serial_num;
INV: Restrict Receipt of Serials?
Here is a query that might help you look for serials that were received again after being shipped. You might add additional logic to check for the existence of a customer install base:
a. This one gives the list of serials shipped then received back:
select mut.serial_number, mut.organization_id
from mtl_unit_transactions mut, mtl_material_transactions mmt
where ((mut.transaction_source_type_id = 11 -- inventory transaction
and mmt.transaction_type_id = 42) -- misc. receipt
or (mut.transaction_source_type_id = 3 -- account transaction
and mmt.transaction_type_id = 40) -- account receipt
or (mut.transaction_source_type_id = 6 -- account alias transaction
and mmt.transaction_type_id = 41)) -- account alias receipt
and mut.transaction_id = mmt.transaction_id
and exists
(select 1 from mtl_unit_transactions mut2
where mut2.transaction_id != mut.transaction_id
and mut2.transaction_date < mut.transaction_date
and mut2.transaction_source_type_id IN (2,8) -- sales/internal order
and mut.serial_number = mut2.serial_number
);
b. This gives a summary count by status and organization of serials shipped and received back:
select msn.current_status, msn.current_organization_id, count(*)
from mtl_serial_numbers msn
where msn.serial_number IN
(select mut.serial_number, mut.organization_id
from mtl_unit_transactions mut, mtl_material_transactions mmt
where ((mut.transaction_source_type_id = 11 -- inventory transaction
and mmt.transaction_type_id = 42) -- misc. receipt
or (mut.transaction_source_type_id = 3 -- account transaction
and mmt.transaction_type_id = 40) -- account receipt
or (mut.transaction_source_type_id = 6 -- account alias transaction
and mmt.transaction_type_id = 41)) -- account alias receipt
and mut.transaction_id = mmt.transaction_id
and exists
(select 1 from mtl_unit_transactions mut2
where mut2.transaction_id != mut.transaction_id
and mut2.transaction_date < mut.transaction_date
and mut2.transaction_source_type_id IN (2,8) -- sales/internal order
and mut.serial_number = mut2.serial_number
))
group by msn.current_status, msn.current_organization_id;
How to track a serial number across organizations
prompt
accept YourSerial DEFAULT 'JBP10000' prompt 'Please enter your serial (Default JBP10000): '
prompt
break on serial_number
select c.serial_number, a.transaction_id, a.transaction_type_id, a.transaction_quantity, 'No Lot'
from MTL_MATERIAL_TRANSACTIONS a, MTL_UNIT_TRANSACTIONS c
where a.TRANSACTION_ID = c.TRANSACTION_ID
and c.serial_number like '&YourSerial'
UNION
select c.serial_number, a.transaction_id, a.transaction_type_id, a.transaction_quantity, b.lot_number
from MTL_MATERIAL_TRANSACTIONS a, MTL_TRANSACTION_LOT_NUMBERS b, MTL_UNIT_TRANSACTIONS c
where a.TRANSACTION_ID = b.TRANSACTION_ID
and b.SERIAL_TRANSACTION_ID = c.TRANSACTION_ID
and c.serial_number like '&YourSerial'
/
How to enter serial number descriptions (or Descriptive Flexfields / DFF)?
You can enter descriptions for serial numbers using descriptive flexfields.
There are two that would be helpful: Serial Attributes or Serial numbers
Serial attributes apper in the onhand > serial number screen in the Serial Info tab with the column name of Attributes. This is similar to the serial entry screens that label the field attributes as well. The Serial numbers descriptive flexfield is visible upon placing the cursor in the descriptive flexfield field usually labled with two brackets like [] also called mug-handles.
To maintain descriptive flexfields for serial numbers:
Navigate to Inventory > Setup > Flexfield > Descriptive > Segments
Query Serial Attributes or Serial numbers
You could then setup descriptions for the serials
Performance Issues with Serial Numbers
For example, one customer found this query to be especially slow working with serials in the Transact Move Order form. They found the query by running a trace on the process using Help > Diagnostics > Trace. Selecting one serial was taking over a minute as there were 3 million available serial numbers in MTL_SERIAL_NUMBERS. Here is the SQL that had bad performance:
SELECT MSN.SERIAL_NUMBER
FROM
MTL_SERIAL_NUMBERS MSN, MTL_SERIAL_NUMBERS_TEMP MSNT WHERE
MSNT.TRANSACTION_TEMP_ID = DECODE(:B5 , 1, :B4 , :B3 ) AND
MSN.CURRENT_ORGANIZATION_ID = :B2 AND MSN.INVENTORY_ITEM_ID = :B1 AND
MSN.SERIAL_NUMBER BETWEEN MSNT.FM_SERIAL_NUMBER AND
NVL(MSNT.TO_SERIAL_NUMBER, MSNT.FM_SERIAL_NUMBER) AND
LENGTH(MSN.SERIAL_NUMBER) = LENGTH(MSNT.FM_SERIAL_NUMBER)
Status Codes (ID and Description)
---------------------
1 Defined but not used
3 Resides in stores
4 Issued out of stores
5 Resides in intransit
6 Pending status
7 Resides in receiving
8 Resides in WIP
You can get a full list of the codes with the following SQL:
SELECT
lookup_type,
lookup_code,
meaning
FROM mfg_lookups
WHERE lookup_type = 'SERIAL_NUM_STATUS'
ORDER BY lookup_type, lookup_code;
Here is a list of common serial control code ids and there descriptions:
Control Codes (ID and Description)
---------------------
1 No serial number control
2 Predefined serial numbers
5 Dynamic entry at inventory receipt
6 Dynamic entry at sales order issue
You can get a full list of the codes with the following SQL
SELECT
lookup_type,
lookup_code,
meaning
FROM mfg_lookups
WHERE lookup_type = 'MTL_SERIAL_NUMBER'
ORDER BY lookup_type, lookup_code;
Here is a version of the query from R12.1 - The actual query is against the view RCV_TRX_INT_SERIALS_V but the SQL below shows the underlying tables: (Receiving Transaction Form)
SELECT rss.serial_num
FROM rcv_serials_supply rss, rcv_shipment_lines rsl
WHERE rss.shipment_line_id = rsl.shipment_line_id
AND upper(serial_num) LIKE '&yourserial')
AND rss.shipment_line_id = &yourshiplineid
AND (rss.lot_num IS NULL OR rss.lot_num = '&YourLot')
AND EXISTS
(SELECT 1
FROM mtl_serial_numbers msn
WHERE msn.serial_number = rss.serial_num
AND msn.current_status = 5
AND (msn.group_mark_id IS NULL
OR msn.group_mark_id = -1)
AND (msn.line_mark_id IS NULL
OR msn.line_mark_id = -1)
AND (msn.lot_line_mark_id IS NULL
OR msn.lot_line_mark_id = -1)
AND msn.inventory_item_id = rsl.item_id
)
ORDER BY rss.serial_num;
INV: Restrict Receipt of Serials?
Here is a query that might help you look for serials that were received again after being shipped. You might add additional logic to check for the existence of a customer install base:
a. This one gives the list of serials shipped then received back:
select mut.serial_number, mut.organization_id
from mtl_unit_transactions mut, mtl_material_transactions mmt
where ((mut.transaction_source_type_id = 11 -- inventory transaction
and mmt.transaction_type_id = 42) -- misc. receipt
or (mut.transaction_source_type_id = 3 -- account transaction
and mmt.transaction_type_id = 40) -- account receipt
or (mut.transaction_source_type_id = 6 -- account alias transaction
and mmt.transaction_type_id = 41)) -- account alias receipt
and mut.transaction_id = mmt.transaction_id
and exists
(select 1 from mtl_unit_transactions mut2
where mut2.transaction_id != mut.transaction_id
and mut2.transaction_date < mut.transaction_date
and mut2.transaction_source_type_id IN (2,8) -- sales/internal order
and mut.serial_number = mut2.serial_number
);
b. This gives a summary count by status and organization of serials shipped and received back:
select msn.current_status, msn.current_organization_id, count(*)
from mtl_serial_numbers msn
where msn.serial_number IN
(select mut.serial_number, mut.organization_id
from mtl_unit_transactions mut, mtl_material_transactions mmt
where ((mut.transaction_source_type_id = 11 -- inventory transaction
and mmt.transaction_type_id = 42) -- misc. receipt
or (mut.transaction_source_type_id = 3 -- account transaction
and mmt.transaction_type_id = 40) -- account receipt
or (mut.transaction_source_type_id = 6 -- account alias transaction
and mmt.transaction_type_id = 41)) -- account alias receipt
and mut.transaction_id = mmt.transaction_id
and exists
(select 1 from mtl_unit_transactions mut2
where mut2.transaction_id != mut.transaction_id
and mut2.transaction_date < mut.transaction_date
and mut2.transaction_source_type_id IN (2,8) -- sales/internal order
and mut.serial_number = mut2.serial_number
))
group by msn.current_status, msn.current_organization_id;
How to track a serial number across organizations
prompt
accept YourSerial DEFAULT 'JBP10000' prompt 'Please enter your serial (Default JBP10000): '
prompt
break on serial_number
select c.serial_number, a.transaction_id, a.transaction_type_id, a.transaction_quantity, 'No Lot'
from MTL_MATERIAL_TRANSACTIONS a, MTL_UNIT_TRANSACTIONS c
where a.TRANSACTION_ID = c.TRANSACTION_ID
and c.serial_number like '&YourSerial'
UNION
select c.serial_number, a.transaction_id, a.transaction_type_id, a.transaction_quantity, b.lot_number
from MTL_MATERIAL_TRANSACTIONS a, MTL_TRANSACTION_LOT_NUMBERS b, MTL_UNIT_TRANSACTIONS c
where a.TRANSACTION_ID = b.TRANSACTION_ID
and b.SERIAL_TRANSACTION_ID = c.TRANSACTION_ID
and c.serial_number like '&YourSerial'
/
How to enter serial number descriptions (or Descriptive Flexfields / DFF)?
You can enter descriptions for serial numbers using descriptive flexfields.
There are two that would be helpful: Serial Attributes or Serial numbers
Serial attributes apper in the onhand > serial number screen in the Serial Info tab with the column name of Attributes. This is similar to the serial entry screens that label the field attributes as well. The Serial numbers descriptive flexfield is visible upon placing the cursor in the descriptive flexfield field usually labled with two brackets like [] also called mug-handles.
To maintain descriptive flexfields for serial numbers:
Navigate to Inventory > Setup > Flexfield > Descriptive > Segments
Query Serial Attributes or Serial numbers
You could then setup descriptions for the serials
Performance Issues with Serial Numbers
For example, one customer found this query to be especially slow working with serials in the Transact Move Order form. They found the query by running a trace on the process using Help > Diagnostics > Trace. Selecting one serial was taking over a minute as there were 3 million available serial numbers in MTL_SERIAL_NUMBERS. Here is the SQL that had bad performance:
SELECT MSN.SERIAL_NUMBER
FROM
MTL_SERIAL_NUMBERS MSN, MTL_SERIAL_NUMBERS_TEMP MSNT WHERE
MSNT.TRANSACTION_TEMP_ID = DECODE(:B5 , 1, :B4 , :B3 ) AND
MSN.CURRENT_ORGANIZATION_ID = :B2 AND MSN.INVENTORY_ITEM_ID = :B1 AND
MSN.SERIAL_NUMBER BETWEEN MSNT.FM_SERIAL_NUMBER AND
NVL(MSNT.TO_SERIAL_NUMBER, MSNT.FM_SERIAL_NUMBER) AND
LENGTH(MSN.SERIAL_NUMBER) = LENGTH(MSNT.FM_SERIAL_NUMBER)
↧
ShipConfirm Button Is Not Enabled at Shipping Transactions Form
ShipConfirm Button Is Not Enabled at Shipping Transactions Form
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1.Responsibility : Oracle Order Management
2.Navigate to Shipping
3.Transactions
4.query order
5.Select Delivery tab
6.Ship Confirm Button is grayed out
Solution
To implement the solution, please execute the following steps:
1. Go into the responsibility:Oracle Order Management
2. Navigate to Shipping > Set up
3. Grants and Roles > Grants > query the user and select the upgrade role > then select the edit roles button at bottom of the form and verify that the ship confirm button is selected
4. Retest the issue.
5. Migrate the solution as appropriate to other environments.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1.Responsibility : Oracle Order Management
2.Navigate to Shipping
3.Transactions
4.query order
5.Select Delivery tab
6.Ship Confirm Button is grayed out
Solution
To implement the solution, please execute the following steps:
1. Go into the responsibility:Oracle Order Management
2. Navigate to Shipping > Set up
3. Grants and Roles > Grants > query the user and select the upgrade role > then select the edit roles button at bottom of the form and verify that the ship confirm button is selected
4. Retest the issue.
5. Migrate the solution as appropriate to other environments.
↧
How do you Change the Word "iRecruitment" on Each Page
How do you Change the Word "iRecruitment" on Each Page to "Careers?"
In System Administrator > Application > Function, you will need to modify the 'User Function Name' of function IRC_BRAND from 'iRecruitment' to 'Careers.'
In System Administrator > Application > Function, you will need to modify the 'User Function Name' of function IRC_BRAND from 'iRecruitment' to 'Careers.'
↧
FRM-41034: Cannot set NAVIGABLE attribute of non-displayed item TOLINES_BLK.SALES_ORDER_NUM
ERROR
FRM-41034: Cannot set NAVIGABLE attribute of non-displayed item TOLINES_BLK.SALES_ORDER_NUM
FRM-41034: Cannot set NAVIGABLE attribute of non-displayed item TOLINES_BLK.SO_LINE_NUM"
Cause:
1. The code transact move order form (INVTOTRX.fmb) checks if data is populated in a field or not. When data IS populated, the form executes code to make the field navigable so the user can click on the field. The setting to navigable fails when the field is hidden from the page using the folder tool. The code does NOT check if the field is hidden by the folder tool already.
For example, you set these fields to Hidden using Folder > Hide Field...
TOLINES_BLK.SALES_ORDER_NUM"
TOLINES_BLK.SO_LINE_NUM"
Solution
Workaround
As a workaround, you can SHOW fields that raise the error. Do NOT hide fields that have values. User hides some fields for productivity. This was done using the FOLDER utility standard in forms
FRM-41034: Cannot set NAVIGABLE attribute of non-displayed item TOLINES_BLK.SALES_ORDER_NUM
FRM-41034: Cannot set NAVIGABLE attribute of non-displayed item TOLINES_BLK.SO_LINE_NUM"
Cause:
1. The code transact move order form (INVTOTRX.fmb) checks if data is populated in a field or not. When data IS populated, the form executes code to make the field navigable so the user can click on the field. The setting to navigable fails when the field is hidden from the page using the folder tool. The code does NOT check if the field is hidden by the folder tool already.
For example, you set these fields to Hidden using Folder > Hide Field...
TOLINES_BLK.SALES_ORDER_NUM"
TOLINES_BLK.SO_LINE_NUM"
Solution
Workaround
As a workaround, you can SHOW fields that raise the error. Do NOT hide fields that have values. User hides some fields for productivity. This was done using the FOLDER utility standard in forms
↧
↧
Default subinventory is not defined in the destination organization
Error:
Default subinventory is not defined in the destination organization
Action: Either the transfer subinventory should be populated or a default subinventory should be setup for the destination organization using the inventory forms
Solution:
ITS Fails With Error "Default Subinventory is not Defined in the Destination Organization" (Doc ID 1223013.1)
Default sub inventory in mtl_transactions_interface is not populated for the struck record. it is required to be populated in case of direct transfer shipping network.
Intransit means we can give sub inventory at the time of receiving in internal orders. shipping network direct means default subinventory should be required and is populated using the below setup.
1. Navigate to Inventory > Setup > Transactions > Item Transaction Defaults.
2. Select the organization.
3. Enter the item, select 'Receiving' in the "Default For" dropdown, enter the default subinventory, save the record.
for current record, we can update transfer subinventory field in mtl_transactions_interface. for future records, we will not get that error because of above setup.
Default subinventory is not defined in the destination organization
Action: Either the transfer subinventory should be populated or a default subinventory should be setup for the destination organization using the inventory forms
Solution:
ITS Fails With Error "Default Subinventory is not Defined in the Destination Organization" (Doc ID 1223013.1)
Default sub inventory in mtl_transactions_interface is not populated for the struck record. it is required to be populated in case of direct transfer shipping network.
Intransit means we can give sub inventory at the time of receiving in internal orders. shipping network direct means default subinventory should be required and is populated using the below setup.
1. Navigate to Inventory > Setup > Transactions > Item Transaction Defaults.
2. Select the organization.
3. Enter the item, select 'Receiving' in the "Default For" dropdown, enter the default subinventory, save the record.
for current record, we can update transfer subinventory field in mtl_transactions_interface. for future records, we will not get that error because of above setup.
↧
Projects Publish WorkPlan Tables
The following SQLs identified the invalid / incorrect data:
a) select * from pa_projects_all where project_id=;
b) select * from pa_tasks where project_id=;
c) select * from pa_proj_elements where project_id=;
d) select * from pa_proj_elem_ver_structure where project_id=;
e) select * from pa_proj_element_versions where project_id=;
f) select * from pa_proj_workplan_attr where project_id=;
g) select * from pa_proj_structure_types where proj_element_id in (select
proj_element_id from
pa_proj_elements where project_id = );
h)select * from pa_object_relationships where object_id_from1 in (
select element_version_id from pa_proj_element_versions where project_id =
) or object_id_to1 in (
select element_version_id from pa_proj_element_versions where project_id =
);
i) select * from pa_budget_versions where project_id=;
j)select * from dba_source where (substr(name,1,3)='PA_' or name like 'PJI%')
and type in ('PACKAGE','PACKAGE BODY') and line=2;
a) select * from pa_projects_all where project_id=;
b) select * from pa_tasks where project_id=;
c) select * from pa_proj_elements where project_id=;
d) select * from pa_proj_elem_ver_structure where project_id=;
e) select * from pa_proj_element_versions where project_id=;
NOTE: The project id of the project can be found from the following SQL query:
SELECT project_id
FROM pa_projects_all
WHERE segment1='';
a) select * from pa_projects_all where project_id=;
b) select * from pa_tasks where project_id=;
c) select * from pa_proj_elements where project_id=;
d) select * from pa_proj_elem_ver_structure where project_id=;
e) select * from pa_proj_element_versions where project_id=;
f) select * from pa_proj_workplan_attr where project_id=;
g) select * from pa_proj_structure_types where proj_element_id in (select
proj_element_id from
pa_proj_elements where project_id = );
h)select * from pa_object_relationships where object_id_from1 in (
select element_version_id from pa_proj_element_versions where project_id =
) or object_id_to1 in (
select element_version_id from pa_proj_element_versions where project_id =
);
i) select * from pa_budget_versions where project_id=;
j)select * from dba_source where (substr(name,1,3)='PA_' or name like 'PJI%')
and type in ('PACKAGE','PACKAGE BODY') and line=2;
a) select * from pa_projects_all where project_id=
b) select * from pa_tasks where project_id=
c) select * from pa_proj_elements where project_id=
d) select * from pa_proj_elem_ver_structure where project_id=
e) select * from pa_proj_element_versions where project_id=
NOTE: The project id of the project can be found from the following SQL query:
SELECT project_id
FROM pa_projects_all
WHERE segment1='
↧
How to give access to OLM Administrator page
Provide ‘Learning Management Administrator’ responsibility to a user account including access to ‘Learning Administrator’ role to user account
↧
Monitoring Open and Cached Cursors
To monitor open cursors, query v$sesstat where name='opened cursors current'. This will give the number of currently opened cursors, by session:
If you're running several N-tiered applications with multiple webservers, you may find it useful to monitor open cursors by username and machine:
--total cursors open, by session
select a.value, s.username, s.sid, s.serial#
from v$sesstat a, v$statname b, v$session s
where a.statistic# = b.statistic# and s.sid=a.sid
and b.name = 'opened cursors current';
If you're running several N-tiered applications with multiple webservers, you may find it useful to monitor open cursors by username and machine:
--total cursors open, by username & machine
select sum(a.value) total_cur, avg(a.value) avg_cur, max(a.value) max_cur,
s.username, s.machine
from v$sesstat a, v$statname b, v$session s
where a.statistic# = b.statistic# and s.sid=a.sid
and b.name = 'opened cursors current'
group by s.username, s.machine
order by 1 desc;
↧
↧
serial number query
1. Determine the status of the serial number that you are attempting to use:
SELECT segment1 "ITEM", msn.serial_number, ml.meaning
FROM mtl_serial_numbers MSN,
mtl_system_items_b MSIB,
mfg_lookups ml
WHERE msn.inventory_item_id = msib.inventory_item_id
AND ml.lookup_code = msn.current_status
AND ml.lookup_type = 'SERIAL_NUM_STATUS'
AND msib.segment1 = '&your_item'
AND msn.serial_number ='&your_serial_number';
2. If the status is 'Issued Out Of Stores', the serial number is used in some organization. You will need another serial number for your transaction
SELECT segment1 "ITEM", msn.serial_number, ml.meaning
FROM mtl_serial_numbers MSN,
mtl_system_items_b MSIB,
mfg_lookups ml
WHERE msn.inventory_item_id = msib.inventory_item_id
AND ml.lookup_code = msn.current_status
AND ml.lookup_type = 'SERIAL_NUM_STATUS'
AND msib.segment1 = '&your_item'
AND msn.serial_number ='&your_serial_number';
2. If the status is 'Issued Out Of Stores', the serial number is used in some organization. You will need another serial number for your transaction
↧
Concurrent Program "Serial Number Generation" Completes With Warning Or Error
Symptoms
Concurrent program "Serial number generation" completes with Warning.Run for quantity 100, but only 9 serials are generated.
Run again for qty 100, request complete with error.
No serials are generated.
Cause
Serial generation have starting number 1.Starting number also control number of digits allowed for serial.
Starting number 1 means that only one digit is allowed for serial , 1 to 9.
Solution
To implement the solution, please execute the following steps:1. Go into the responsibility: Inventory
2. Navigate to Items>Organization item
3. In tab Inventory change starting number.
Fill out with '0' to control number of digits that is allowed for the serial number.
Par example starting number 0001, will generate serials up to 9999.
4. Retest the issue.
5. Migrate the solution as appropriate to other environments.
↧
Forms Personalizations Not Visible
Symptoms
On 12.1.3:The Forms Personalizations made on the Service Request Form are not visible.
The Personalizations are active and working, but it is not possible to see them and maintain the Personalizations.
Steps:
- Open Service Request form
- Help - Diagnostics - Custom Code - Personalize
Cause
In new versions of the Personalizations form FNDCUSTM.fmb, there is a new field called Key.The personalizations form (FNDCUSTM.fmb) now has two modes. When the form is displayed, the 'FND: Enable Industry Editing' profile value is checked. If the profile is set to Yes, only personalizations that have a value for the KEY column will be displayed. If the profile is set to No or not set at all, only personalizations that have a null value for the KEY column will be displayed.
Solution
When creating Forms Personalizations, make sure the profile option'FND: Enable Industry Editing'
is set to No or Null
↧
What are the main tables involved in Inter-Organization Transfer?
What are the main tables involved in Inter-Organization Transfer?
A check is carried out to see if the transaction date is in an open period as specified in the profile option (INV: Transaction Date Validation). The column is acct_period, the table is ORG_ACCT_PERIODS.
The organizations setting, cost information, etc, are derived from:
ORG_ORGANIZATION_DEFINITIONS, MTL_PARAMETERS, MFG_LOOKUPS, MTL_INTERORG_PARAMETERS
[HR_ORGANIZATION_INFORMATION - for rel 11I].
The transaction information is derived from MTL_TRX_TYPES_VIEW for inter-org transactions where transaction_source_type_id=13.
The item information is derived from MTL_SYSTEM_ITEMS [MTL_SYSTEM_ITEMS_B - for rel 11I].
A check is carried out to verify the available item quantity on MTL_DEMAND and
MTL_ONHAND_QUANTITIES [MTL_RESERVATIONS included in rel 11I].
MTL_SUBINVENTORIES_TRK_VAL_V keeps track of the values of the subinventories.
MTL_ITEM_LOCATIONS is searched for the locators specified (if used).
GL_CODE_COMBINATIONS is searched for a valid locator combination (if used).
The cost of the item is gotten from CST_CG_ITEM_COSTS_VIEW.
The transaction is inserted into MTL_MATERIAL_TRANSACTIONS_TEMP table.
If the item is under lot control, lot information is deleted from MTL_TRANSACTION_LOTS_TEMP, likewise the serial numbers information if the item is serialized is deleted from MTL_SERIAL_NUMBERS_TEMP, MTL_SERIAL_NUMBERS.
The new lot information is inserted into MTL_TRANSACTION_LOTS_TEMP.
A check is carried out to see if the transaction date is in an open period as specified in the profile option (INV: Transaction Date Validation). The column is acct_period, the table is ORG_ACCT_PERIODS.
The organizations setting, cost information, etc, are derived from:
ORG_ORGANIZATION_DEFINITIONS, MTL_PARAMETERS, MFG_LOOKUPS, MTL_INTERORG_PARAMETERS
[HR_ORGANIZATION_INFORMATION - for rel 11I].
The transaction information is derived from MTL_TRX_TYPES_VIEW for inter-org transactions where transaction_source_type_id=13.
The item information is derived from MTL_SYSTEM_ITEMS [MTL_SYSTEM_ITEMS_B - for rel 11I].
A check is carried out to verify the available item quantity on MTL_DEMAND and
MTL_ONHAND_QUANTITIES [MTL_RESERVATIONS included in rel 11I].
MTL_SUBINVENTORIES_TRK_VAL_V keeps track of the values of the subinventories.
MTL_ITEM_LOCATIONS is searched for the locators specified (if used).
GL_CODE_COMBINATIONS is searched for a valid locator combination (if used).
The cost of the item is gotten from CST_CG_ITEM_COSTS_VIEW.
The transaction is inserted into MTL_MATERIAL_TRANSACTIONS_TEMP table.
If the item is under lot control, lot information is deleted from MTL_TRANSACTION_LOTS_TEMP, likewise the serial numbers information if the item is serialized is deleted from MTL_SERIAL_NUMBERS_TEMP, MTL_SERIAL_NUMBERS.
The new lot information is inserted into MTL_TRANSACTION_LOTS_TEMP.
↧
↧
Inter-Organization and Internal Sales Order Receipts
1. What is the order of defaulting of the Receipt Routing on the receipts screen which may be set at various levels?
For Inter-Org Shipments (In-Transit Receipts) the Receipt Routing is defaulted as follows:1. Item Attribute
2. if 1 is null, then Shipping Network for the Receiving Organization
3. if 2 is null, then Receiving Option
2. What are the different types of Inter-Organization Transfers?
Inter-Organization transfers can be performed as either direct or intransit shipments.
Direct inter-organization transfers:
Inventory is moved directly from a shipping organization to the destination organization. Receipt is not required to be made as the transfer is direct to inventory
Intransit inventory:
Usually done when transfer time is significant. Delivery location isn't specified during transfer transaction, You only need to enter subinventory you are shipping from, a shipment number, the freight information and inter-organization transfer charge. Then you need to perform Receipt from the Receiving forms.
Direct inter-organization transfers:
Inventory is moved directly from a shipping organization to the destination organization. Receipt is not required to be made as the transfer is direct to inventory
Intransit inventory:
Usually done when transfer time is significant. Delivery location isn't specified during transfer transaction, You only need to enter subinventory you are shipping from, a shipment number, the freight information and inter-organization transfer charge. Then you need to perform Receipt from the Receiving forms.
3. What are the minimum setups required for Items which we use for Internal Sales Order?
The items which we use for Internal Sales Order must be Inventory enabled, internally orderable and stockable, shippable, and Order Management transactable for the source organizations. Under Inventory, you need to select the Inventory Item, Transactable, and Stockable options. Under Order Management, you need to select the Internal Ordered, Internal Orders Enabled, OE Transactable, and Shippable options.4. How do we define the Inter-Organization Shipping Network?
Use the Shipping Networks window to define your inter–organization network. You must enable the network between each source (shipping) and destination (receiving) organization.-Select Internal Order Required if you want all transfers between these two organizations to use internal orders.
-Specify whether you ship material directly, or use intransit inventory for shipments between these two organizations.
-For intransit transfers, you can choose from the following primary receipt routings: Standard receipt, Inspection required, or Direct delivery.
5. What are the steps to perform Inter-Organization Transfer?
Follow these 3 simple steps:1. Setup Shipping Network: This information describes the relationships and accounting information that exists between a from (shipping) organization and a to (distribution) organization.
Navigation path:
A. Choose the Inventory Manager responsibility.
B. Setup/Organizations - Make sure that there is an entry for from/to organization (between the organizations you intend to perform the transfer). When you click on this form, you will get a LOV with orgs.
-Choose the From Org.
-Transfer Type can be either Intransit or Direct (Direct would ship directly to Inventory, so it would be a Direct Delivery).
-FOB can be either Receipt or Shipment, if the transfer type is entered as Intransit.
If Receipt the source inventory quantities get updated at time of receipt.
If it be Shipping, then the quantities get updated as soon as the shipment is done.
2. Inventory/Transactions/Interorganization Transfer: When you click on this form, you will get a LOV with orgs. Choose the from org. Specify the to-org, transfer type as intransit, and input a value for shipment-number.
Click on the transaction lines button. Input the item, the quantity and the subinventories between which you want to do the transfer. (Sometimes there might not be enough quantity in the from-org to do this. For this : Go to: Inventory/Transactions/Miscellaneous Transactions. Specify the Type as Miscellaneous Receipt. Click on transaction lines button and specify item/quantity).
3. Receive against an Inter-org Transfer: Choose Purchasing Super User responsibility.
Under Purchasing/Receiving/Receipts - Query up against Shipment Number in the find window. In RCV Transactions block, specify the quantity you want to receive and commit the transaction.
6. What are the steps required for receiving against Internal Sales Order?
The process of receiving against Internal Sales Orders involves the following steps:1. Create an Internally Orderable Item - To do this you need to create an Item and in the Order Entry attributes, check the Internally Orderable check box.
2. Setup Shipping Network: This information describes the relationships and accounting information that exists between a from (shipping) organization and a to (distribution) organization.
Navigation path:
A. Choose the Inventory Manager responsibility.
B. Setup/Organizations - Make sure that there is an entry for from/to organization (between the organizations you intend to perform the transfer e.g.. GLO -> SAC).
When you click on this form, you will get a LOV with orgs.
-Choose the From Org.
-Transfer Type can be either Intransit or Direct (Direct would ship directly to Inventory, so it would be a Direct Delivery).
-FOB can be either Receipt or Shipment, if the transfer type is entered as Intransit.
If Receipt the source inventory quantities get updated at time of receipt.
If it be Shipping, then the quantities get updated as soon as the shipment is done.
3. Create an Internal Requisition.
-Enter the item you created in step 1.
-Enter the Source and Destination Organization. Source Organization is on the right of the form and Destination to the left.
-Enter location (e.g.. SACHQ) and Source as Inventory.
-Save and approve requisition.
4. Run the Create Internal Orders concurrent program.
5. Change responsibility to Order Entry Superuser.
6. Run Order Import concurrent program.
7. When the process completes, you will see the Order Number in the log file.
8. If the process errors : "You must enter Tax Code. Tax code attribute is missing" then:
-Change responsibility to AR Manager (Receivables)
-Navigate Setup->Transaction->Transaction Types
-Query up record with Name = "Invoice Hdwe/svcs"
-Uncheck the Tax Calculation check box
-Save
9. Run the Demand Interface concurrent program.
10. Run the Manufacturing Release concurrent program.
11. Navigate to:
-Orders, Returns -> Orders, Returns -> Do a Find on the Order Number
-Click on the View button
-Click on Cycle Status
-Your Order should now be Pick Release Eligible
12. Navigate to Shipping -> Pick Release -> Release Sales Order
-Enter a Batch Name and your Order Number
-Save
-Note the Batch_ID by doing a Help->Tools->Examine.
13. Run the Pick Release concurrent program. Use Batch Name/Order Number as parameter. This can be run from command line as:
./OESREL apps_appdemo/fnd@comp16p 0 Y (from step L)
Perform Step K. Your Order should now be Ship Confirm Eligible
14. Navigate to Shipping->Confirm Shipments->Pick Slip
-Do a Find on the Order Number
-Click on Open
-Click on details
-Check if all values of quantity to be shipped are correct
-Save
15. Change Responsibility to Purchasing Super User.
Navigate to the Enter Receipts form and query on the Requisition Number.
You can now receive against the Internal Order.
To override the destination type at receipt time you need to set the profile option RCV: Allow routing override = Yes.
7. How are Lot and Serial Numbers handled in Inter-Organization Transfers?
When you perform an inter–organization transfer, the source and destination organization may have different lot/serial controls. Purchasing handles this situation as follows:1. When the source organization uses controls and the destination organization does not, the control numbers are recorded as being issued from the source organization. Lot/serial transactions are recorded for the destination organization.
2. When the source organization does not use controls and the destination organization does, the transaction is processed normally.
3. When both source and destination organizations use controls, the control numbers are recorded as being issued from the source organization. These control numbers are tracked to insure that the same control numbers that were shipped are the ones
that are received. When items are returned from inventory to receiving or to the supplier, only the control numbers originally recorded for the delivery transaction can be used.
8. What's the cause of the error RVTSH-150 and what's the solution for it?
Error RVTSH-150 is because the following select is failing, returning 0 rows:SQL> select ms.unit_of_measure
from mtl_supply ms
where supply_type_code = 'REQ'
and supply_source_id = :req_line_id;
The error is because the Req. Supply missing. This is mostly a data problem caused at customer site. Look into why the records are missing. May be the data has been manually changed or some cancellations for the req. shipment has taken place.
For data fix, reference Note: 267439.1
9. What are the main tables involved in Inter-Organization Transfer?
A check is carried out to see if the transaction date is in an open period as specified in the profile option (INV: Transaction Date Validation). The column is acct_period, the table is ORG_ACCT_PERIODS.The organizations setting, cost information, etc, are derived from:
ORG_ORGANIZATION_DEFINITIONS, MTL_PARAMETERS, MFG_LOOKUPS, MTL_INTERORG_PARAMETERS
[HR_ORGANIZATION_INFORMATION - for rel 11I].
The transaction information is derived from MTL_TRX_TYPES_VIEW for inter-org transactions where transaction_source_type_id=13.
The item information is derived from MTL_SYSTEM_ITEMS [MTL_SYSTEM_ITEMS_B - for rel 11I].
A check is carried out to verify the available item quantity on MTL_DEMAND and
MTL_ONHAND_QUANTITIES [MTL_RESERVATIONS included in rel 11I].
MTL_SUBINVENTORIES_TRK_VAL_V keeps track of the values of the subinventories.
MTL_ITEM_LOCATIONS is searched for the locators specified (if used).
GL_CODE_COMBINATIONS is searched for a valid locator combination (if used).
The cost of the item is gotten from CST_CG_ITEM_COSTS_VIEW.
The transaction is inserted into MTL_MATERIAL_TRANSACTIONS_TEMP table.
If the item is under lot control, lot information is deleted from MTL_TRANSACTION_LOTS_TEMP, likewise the serial numbers information if the item is serialized is deleted from MTL_SERIAL_NUMBERS_TEMP, MTL_SERIAL_NUMBERS.
The new lot information is inserted into MTL_TRANSACTION_LOTS_TEMP.
10. How can we return or correct delivered lines in an Internal Requisition?
It is not possible to perform Returns or Corrections on Internal Shipments. Once the Internal Order is ship confirmed and interfaced to Inventory, the shipment is created in Receiving tables, and there is no way to back out or modify the shipments.In order to return an internally ordered item the original process needs to be reversed. An internal requisition for the item has to be created in the source organization, and then that order has to be processed back to the source organization. This can be done as followed:
Reverse the original process to return an internally ordered item.
Create an internal requisition for the item in the source organization.
Process the order back to the source organization.
Or as a second option, a miscellaneous receipt and miscellaneous issue may be completed, as a workaround.
Enhancement request Bug 2206351 has been logged to enhance the functionality to enter returns for internal shipments.
This is also true for Inter Organization Transfers entered on Inter-organization Transfer form INVTTMTX
For IOT shipments the only solution is to create a new inter org transaction from inventory org B to inventory org A if the initial IOT is from org A to org B
Also online help clearly indicates
Finding Returns
Use the Find Returns window to find source documents for which you can enter returns. Use the Supplier and Internal tabbed region to search for Purchasing documents. If Order Management is installed, use the Customer tabbed region to search for customer return material authorizations (RMAs).
Note: You cannot enter returns for internal shipments (that is, shipments with a Source Type of Internal).
11. What to do if the physical quantity received does not match quantity shipped?
Case 1: When physical qty received is more than qty shipped.Example: Source org ships 80 pieces, but receiving org wants to receive only 100 pieces.
An intransit shipment cannot be over-received. Receive the entire qty shipped in the receiving org and create a new intransit shipment for the remaining qty shipping it from the source org.
Case 2: When physical qty received is less than qty shipped.
Example: Source org ships 100 pieces, but receiving org receives only 80 pieces.
Partial receipt of intransit shipment is allowed, but there is no way to cancel the remaining qty. Hence, entire qty shipped should be received. To adjust the on-hand quantity:
o A reverse intransit shipment can be done for the excess qty from receiving org to source org.
OR
o A miscellaneous issue from the receiving org for the excess qty can be done.
If only a partial receipt is done, then the remaining qty will continue to show in intransit until its received.
↧
FRM-40735: WHEN-VALIDATE-ITEM trigger raised unhandled exception ORA-01403
R12 TRYING TO ENTER INVOICE: FRM-40735: ON-COMMIT TRIGGER AND ORA-01403 ERROR - was logged for this issue and it was determined to be an issue due to the existence of duplicate payees.
Patch 10140168 was released for this but was obsoleted and replaced with GDF patch 13857555 which delivers a select and fix scripts for this issue.
Solution
1. Download and review the readme and pre-requisites for the following patch:
For R12.0.x: Patch 13857555:R12.IBY.A: RCA: ISSUES WITH DUPLICATE PAYEE DELETION GDF: 10140168
For R12.1.x: Patch 13857555:R12.IBY.B: RCA: ISSUES WITH DUPLICATE PAYEE DELETION GDF: 10140168
2. Ensure that you have taken a backup of your system before applying the recommended patch.
3. Apply the patch in a test environment.
This patch does not fix any data it just delivers the data fix scripts.
For R12.0.x:
iby_dup_payee_fix.sql 120.0.12000000.5
iby_dup_payee_sel.sql 120.0.12000000.6
For R12.1.x:
iby_dup_payee_fix.sql 120.0.12010000.3
iby_dup_payee_sel.sql 120.0.12010000.2
You can use the commands like the following:
strings -a $XX_TOP/filename |grep '$Header'
4. Run $IBY_TOP/patch/115/sql/iby_dup_payee_sel.sql
This is a select script and does not update any data, just shows/confirms the extent of the corruption in the html output file.
5. Run $IBY_TOP/patch/115/sql/iby_dup_payee_fix.sql
This is the actual data fix script that will correct the corruption and allow the invoice to be entered.
Patch 10140168 was released for this but was obsoleted and replaced with GDF patch 13857555 which delivers a select and fix scripts for this issue.
Solution
1. Download and review the readme and pre-requisites for the following patch:
For R12.0.x: Patch 13857555:R12.IBY.A: RCA: ISSUES WITH DUPLICATE PAYEE DELETION GDF: 10140168
For R12.1.x: Patch 13857555:R12.IBY.B: RCA: ISSUES WITH DUPLICATE PAYEE DELETION GDF: 10140168
2. Ensure that you have taken a backup of your system before applying the recommended patch.
3. Apply the patch in a test environment.
This patch does not fix any data it just delivers the data fix scripts.
For R12.0.x:
iby_dup_payee_fix.sql 120.0.12000000.5
iby_dup_payee_sel.sql 120.0.12000000.6
For R12.1.x:
iby_dup_payee_fix.sql 120.0.12010000.3
iby_dup_payee_sel.sql 120.0.12010000.2
You can use the commands like the following:
strings -a $XX_TOP/filename |grep '$Header'
4. Run $IBY_TOP/patch/115/sql/iby_dup_payee_sel.sql
This is a select script and does not update any data, just shows/confirms the extent of the corruption in the html output file.
5. Run $IBY_TOP/patch/115/sql/iby_dup_payee_fix.sql
This is the actual data fix script that will correct the corruption and allow the invoice to be entered.
↧
SQL query for Concurrent Request Paused Jobs
--Admin Concurrent Request Paused Jobs
SELECT DISTINCT cr.request_id, cr.description,
cp.user_concurrent_program_name, u.user_name,
cr.actual_start_date
FROM apps.fnd_lookup_values lv,
apps.fnd_concurrent_programs_vl cp,
apps.fnd_executables e,
apps.fnd_concurrent_requests cr,
apps.fnd_user u
WHERE e.executable_id = cp.executable_id
AND lv.lookup_type = 'CP_EXECUTION_METHOD_CODE'
AND lv.lookup_code = e.execution_method_code
AND cr.concurrent_program_id = cp.concurrent_program_id
AND cr.requested_by = u.user_id
AND u.user_name IN ('TFADMIN', 'BIADMIN', 'SYSADMIN')
AND cr.status_code = 'W'
AND cr.phase_code = 'R'
AND TRUNC (cr.actual_start_date) >= TRUNC (SYSDATE - 1)
ORDER BY cr.actual_start_date DESC, cr.request_id;
SELECT DISTINCT cr.request_id, cr.description,
cp.user_concurrent_program_name, u.user_name,
cr.actual_start_date
FROM apps.fnd_lookup_values lv,
apps.fnd_concurrent_programs_vl cp,
apps.fnd_executables e,
apps.fnd_concurrent_requests cr,
apps.fnd_user u
WHERE e.executable_id = cp.executable_id
AND lv.lookup_type = 'CP_EXECUTION_METHOD_CODE'
AND lv.lookup_code = e.execution_method_code
AND cr.concurrent_program_id = cp.concurrent_program_id
AND cr.requested_by = u.user_id
AND u.user_name IN ('TFADMIN', 'BIADMIN', 'SYSADMIN')
AND cr.status_code = 'W'
AND cr.phase_code = 'R'
AND TRUNC (cr.actual_start_date) >= TRUNC (SYSDATE - 1)
ORDER BY cr.actual_start_date DESC, cr.request_id;
↧