Responsibility Assigned to Users

SELECT  DISTINCT 
            u.user_id ,SUBSTR (u.user_name, 1, 30)  user_name 
           ,SUBSTR (r.responsibility_name, 1, 60)     responsibility 
           ,SUBSTR (a.application_name, 1, 50)       application 
FROM    fnd_user u, 
           fnd_user_resp_groups g, 
           fnd_application_tl a, 
           fnd_responsibility_tl r 
WHERE  g.user_id(+)                         =   u.user_id 
AND      g.responsibility_application_id  =   a.application_id 
AND      a.application_id                     =   r.application_id 
AND      g.responsibility_id                  =   r.responsibility_id 
ORDER BY SUBSTR (user_name, 1, 30), 
SUBSTR (a.application_name, 1, 50), 
SUBSTR (r.responsibility_name, 1, 60); 

Read More»

List of Responsibilities in an Instance

SELECT (SELECT application_short_name
FROM   fnd_application fa
WHERE fa.application_id = frt.application_id) application,
          frt.responsibility_id, frt.responsibility_name
FROM  apps.fnd_responsibility_tl frt;

Read More»

How to determine Oracle Database And OS version

You can use following two queries to find out the Apps/Database/OS version

select * from v$version;

select * from product_component_version;

Thanks
Mandeep

Read More»

Session Timeout in Oracle Apps

This post is about how to increase your session time out for oracle application. Sometime its very annoying that session time out is set at very low value. You can increase it for your login by setting profile option "ICX: Session Timeout" from sysadmin responsibility

Please navigate to Sysadmin > Profile > System and query for "ICX: Session Timeout" after checking both at Site and User checkbox and increase the value of User.

Thanks
Mandeep

Read More»

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.

Read More»

Shipping Parameters Quick Reference

Lets see Oracle Order Management Shipping parameter setups. Please note shipping parameters are inventory org specific where as Global parameters are not.

1) General Tab

#Weight UOM Class: Default Weight UOM class used in shipping from this Organization V1.
#Volume UOM Class : Default Volume UOM class used in shipping from this Organization V1.
#Percent Fill Basis : Select Percent fill basis from Quantity, Volume or Weight. This is the used to determine whether or not container met there minimum fill percentage.
For Weight or Volume, the calculation uses the physical attribute of item and container in Inventory and for Quantity, the calculation uses the Container Load Relationship details to determine the maximum number of items that will fit into the container.

#Export Compliance Screening: is used to enforce export compliance screening at Delivery Creation, Ship Confirm, or At Delivery creation and Ship Confirm
#Enable Workflow : This is used to enable workflow for delivery. You can configure workflow to achieve specific task like sending notification for over ship or backorder to a user
#Raise Business Events: This check box is used to enable business events.
#Enable Ship to Deliver Workflow: If you want to use ship to deliver workflow then enable this box here

2) Pick Release

# Release Sequence Rule : You can define release sequence rule at OM>Setups>Shipping>Picking>Define Release Sequence Rule. This is used to specify the Order in which delivery lines are allocated inventory.
# Pick Slip Grouping Rule: You can define release sequence rule at OM>Setups>Shipping> Pick Slip Grouping Rule. This rule specify how release delivery lines are grouped on Pick slip. Both above rules are default only and you can change them during pick release
#Print Pick Slip:  This specify when you want to print pick slip.
At the End: Pick slip will be printed at the end of the pick release process.
Immediate : In this case you must specify the "Number of Pick Slip lines". Once the threshold is reached it will start printing
# Number of Pick Slip lines:  This is used specify the number of lines will print on each pick slip and is mandatory when Print Pick slip is set to Immediate.
# Default Pick Release Document set: This is the default document set which is printed for pick release. You can change its value at the time of pick release.
# Default Stage Subinventory/Locator: Pick Confirm (Transact move orders) transfer material to this subinventory/Locator.
# Auto Create Deliveries: If this is selected then pick release auto create deliveries based on delivery grouping rules. You can override this option at the time of pick release.
# Auto Allocate: If this is selected then pick release automatically create and transact move orders. You can override this option at the time of pick release
# Enforce Ship Set and Ship Model: If this is selected then all ship lines in ship set or ship model will be released nor back ordered together.
#Plan Task: this is enabled if Warehouse management is used.
#Pull Replenishment: This is used to fill up a locator up to maximum capacity when there is a shortfall. this is also used with WMS.
# Retain Unstated Quantity during over pick:This is used to retain unstaged quantity during over shipment. We will see the effected of this in another post.

3) Shipping Transactions

# Default Ship Confirm Document Set: This is a document which are printed at ship confirm.
# Ship Confirm Rule: This is default auto ship confirm rule.
#Auto pack Option: If this is Yes then delivery lines are packed based on item container relationship
and if this is set as Autopack master then container further packed in another container such as frieght container for transport.
#Good Dispatch Account : The sales order issue transaction uses this account if the Oracle Order Management workflow cannot determine one.
#Enforce Packing in Containers: if yes, ship confirm displays a warning when confirming a delivery or trip with unpacked delivery line items.

4) Delivery

# Delivery  Grouping Attribute: This is used to select attributes for grouping of delivery lines.
#Autocreate Delivery Criteria: If you have enabled auto create delivery in pick release tab then thi sis used specify the criteria for that. Across Order means all selected delivery lines that match on the Delivery Grouping Attributes across orders are eligible to appear on one delivery.
#Append Limit: This is used to indicate the point at which you want to stop the system from adding lines to a delivery.

If you are using Oracle transportation Management then use other parameters

Thanks
Mandeep

Read More»

Copy Inventory Organization

Copy Inventory Organization in Oracle Apps is used to create a new inventory organization from exiting model organization. You can create multiple Inventory organizations with very little effort which is otherwise very tedious process during implementation.

You can optionally copy Organization Definition, Shipping network, Item and its attributes, Department, Resources, Routings, BOM.

Please note Subinventories, Locators, WIP Parameters, WIP accounting classes, Planning Parameters, and Shipping Parameters data from your model organization are always copied.

Copy Inventory Organization works only within same operating unit and new org created under same Business group, Operating unit, Legal entity and Ledger as that of model organization.

Pre-requisites 

1) Please define at least one inventory organization and all its steps. Please note you cannot use master organization as Model organization.
2) It is recommended to complete BOM setups if you want to copy that also
3) Location for new inventory organization. We will use "Test Location" in our demonstration.

Steps
1) Maintain Interface
2) Launch Organization Copy Program


Step 1) Maintain Interface step is used to put the data in Copy Inventory Organization interface tables.

Navigate to Inventory>Setup>Organization>Organization Copy>Maintain Interface

# Group Code: This is used to identify new org code and is one of the mandatory parameter Copy Organization Program. You can define multiple records under this Group Code.
# Organization Name: Please enter a name for new organization which will be created after running Copy Organization Program
# Organization Code: This is used to identify new org
# Location Name: Location for the new org. As mentioned before, we will use "Test Location" in our demonstration.

Now click on Populate Interface Table. A Confirmation Message will be displayed.

After Clicking ok, you can enter another inventory org which you want to create and use this form as many times as you want. You can also use this form to find previous records entered e.g,

The Status field here shows the status after running the program (Whether it is successful or failed). Blank mean the records are yet to be processed.

Step 2) Launch Organization Copy Program

Next step is to populate base tables by running Launch Organization Copy Program.

#Take model Organization as M1
#Group Code: use "Copy Test"
#Assign to Exiting Organization:  If yes, then new org will be assigned to same hierarchy as model org.
#Copy Shipping Networks: If yes the model org shipping network setup copied to new org.
#Copy Item: If yes, all item assigned to model org copied to new org
# Validate Item: Used to check inconsistencies before copied to new org.
# Copy BOM: BOM and its parameters will get copied to new org
# Copy Routings: If defined in model org, all departments, Resources and Routings will be copied to new org
# Purge: If yes then group code will be purged after running this program.

Click OK and Submit

Thanks
Mandeep

Read More»