This action cannot be performed on all selected records

When attempting to ship confirm a sales order the following error is shown

Cause:

The issue is caused as the trip is still open but delivery is confirmed.

Solution:

Query the order in shipping transactions form > Path by Stop tab > Actions > Update status > Close. Be sure to check the ‘Defer Interface’ check box on the form.

Once the trips are closed the line status changes to ‘Shipped’ and Next step to ‘Run Interfaces’.

Run Interface trip stop – SRS program. On completion of the concurrent the line status will change to ‘Interfaced’ 

Note:

To avoid this issue, always ship confirm orders with these two boxes checked:

• Set Delivery In-Transit
• Close Trip

---X---

Receipt Traveler Report

The Receipt Traveler facilitates receiving inspection and delivery of goods you receive within your organization. After you receive the goods, you can print receipt travelers and attach these tickets to the goods.

One receipt traveler gets printed per distribution, and each traveler has space for you to record delivery comments. It prints in the following format:

Item

Source (Supplier/Inventory/Internal requisition/RMA)

Receipt

Delivery Instructions

Lot and Serial Number

WIP Shortage

Note: 
If the receipt is saved after entering only the header information, the report prints only the header information and a blank page since; line information has not been completed. If both the header and line information is entered the receipt traveler will print all the information.

A Receipt Traveler can be automatically printed under the following conditions:

• A standard receipt is performed
• A direct receipt is performed
• An unordered receipt has been matched

In order to print the Receipt Traveler automatically under any of these conditions, the profile options 'RCV: Print Receipt Traveler' must be set to 'Yes' & ‘RCV: Processing Mode’ should be ‘Immediate’.

Setting the 'RCV: Print Receipt Traveler' profile option to 'Yes' will allow for the traveler to print automatically, the number of copies that will actually print is controlled by the 'Concurrent:Report Copies' profile option. If you need the traveler report to be printed on paper at the time the required transaction is performed, this profile should be greater than zero. This profile option will affect all reports within Oracle Applications, hence decide wisely.

Note:

Receipt traveler will not be printed when receipt is taken using iProcurement.

It is advisable to set incompatibility between ‘Receiving transaction Processor’ and ‘Receipt Traveler’ concurrent program.

Navigation: System administrator > Concurrent > Program > Define

Query the program "Receipt Traveler Concurrent program" (RCVDLPDT) & Click ‘Incompatibilities’ button.

Enter ‘Receiving transaction processor’ concurrent and save.

Bounce the concurrent managers, this will force ‘Receipt Traveler’ to wait for ‘Receiving Transaction Processor’ concurrent to complete.

---X---

Unordered Receipts

Through Unordered receipts concept Oracle allows us to take receipt even when we don’t have a corresponding purchase order.

First receive the items as Unordered Receipts in the Receipts window. We can either take a new receipt or add to an existing receipt for the supplier who shipped the unordered items. Then match the Unordered receipt to a purchase order which has pending approved shipments.

Conditions:

• The purchase order must have the same supplier as the unordered receipt.

• The purchase order should not be finally closed or cancelled.

• The purchase order must have at least one approved shipment in the same organization where      

               you performed the unordered receipt.

• The item and the purchasing category on the purchase order must be the same as the item and            

               purchasing category on the unordered receipt.

We can match Unordered receipts only to approved shipments. If you cannot locate a valid matching document for your unordered receipt, you can modify and approve an existing purchase order/release or you can create and approve a new purchase order.

Note:

If ‘RCV: Print Receipt Traveler’ profile option is set to Yes, receipt travelers are printed automatically when you match unordered receipts.

Taking Unordered Receipt:

Click Unordered button in Find Expected Receipts window

Enter the Supplier name in Receipt Header form

Enter Quantity, UOM, Destination type, Item code & save the transaction.

Note the Receipt number.

Matching Unordered Receipts:

Navigation: Purchasing > Receiving > Match Unordered Receipts

Enter the Unordered Receipt No. and click Find

Enter the Purchase order details & Save.

Once Receive & Deliver has been completed, the receipt looks like the following in Receipt transaction summary.

Note:

Not only Purchase receipt, we can also take RMA receipt as Unordered receipt.

---X---

Defining Resource Cost in Oracle Process Manufacturing (OPM)

To reflect the cost of the resource incurred during production in the product cost, set up routings and define the amount or number of resources used.

Outside production, set up overheads to reflect the amount of resources other than the production or ingredients used in the product; you can then include overhead costs in the cost of producing the product. In either case, first we must define nominal usage cost associated with the resource.

To know about defining Overheads, click the following link

http://dj-oracleapps.blogspot.in/2014/06/defining-fixed-overheads.html

Pre-requisites:

Resources

To know about how to define a resource, click the following link

http://dj-oracleapps.blogspot.in/2014/02/creating-resources-in-oracle-process.html

Navigation: OPM Financials > Resource costs

Enter the code of the Organization for which this resource cost is effective.

Note: If Organization is not entered then the resource cost will be considered for all the organizations that fall under the displayed Legal entity.

Enter the Resource for which we are defining the cost.

Enter the Cost Calendar & Period for which this resource cost will be applicable.

Component class displays the component class associated with the resource & Base Currency displays the legal entity’s base currency.

Cost Details

Enter for which Cost Type this resource cost is defined.

Enter a Nominal Cost for the resource for using it for one unit of measure. For example, if you are defining the resource cost for a mixing machine, and its usage is measured in hours, then enter the cost of using the mixing machine for one hour.

Enter the unit of measure in which usage of this resource is measured in UOM. By default the system will display the unit of measure initially defined for this resource. We can edit the value within the same unit of measure class.

Note: Status field is not applicable

---X---

Defining Fixed Overheads in Oracle Process Manufacturing (OPM)

An overhead is a cost associated with a resource other than the resource usage assigned in the routing.

Assume you need a laborer to clean MIXER after each use. To account for the cost of cleanup, instead of adding another component cost to each item that uses MIXER, you can assign an overhead to the items being produced by that laborer on MIXER. The overhead assignment would be the time it takes the laborer to clean MIXER multiplied by the cost per hour for the laborer.

Navigation:

OPM Financials > Fixed Overheads

To define Fixed Overheads:

Enter the Item code to which this overhead is going to assigned.

Enter a valid Calendar, Period code & Cost type.

Base Currency code field will display the base currency of the legal entity.

Overhead Details:

Enter the Resource code and Component Class code.

To know how to create a Resource click the following link  http://dj-oracleapps.blogspot.in/2014/02/creating-resources-in-oracle-process.html

Enter the Analysis code under which this overhead should appear in cost detail.

Enter the Qty of resource used in the production of this item in Resource Count. Ex: If it takes one worker to cleanup Mixer after each use, then enter 1. This number is multiplied by the Resource Usage to calculate the total resource usage.

Enter the amount of the resource used for this overhead in Resource Usage. Ex: If it takes 10 minutes for a worker to cleanup Mixer after each use, then enter 0.10

Enter the unit of measure in which the resource is yielded in Resource UOM.

Enter the amount of the item yielded in this production process during the entered .10 hours of resource usage in Item Quantity.

Enter the unit of measure in which this overhead is measured in Overhead UOM field.

---X---

Oracle Application Implementation Methodology (AIM)

Oracle AIM Methodology encompasses a project management methodology with documentation templates that support the life cycle of an implementation. The life cycle methodology and documentation templates allow AIM to be a very useful tool for managing implementation projects successfully.

The software includes the documentation templates, manuals and an html website to manage these templates.

Application Implementation Method is a proven approach for all the activities required to implement oracle applications. There are eleven processes of implementation.

Business Process Architecture (BP) – This phase outlines Existing business practices, Catalog change practices, Leading practices & Future practices.

BP.010 Define Business and Process Strategy

BP.020 Catalog and Analyze Potential Changes

BP.030 Determine Data Gathering Requirements

BP.040 Develop Current Process Model

BP.050 Review Leading Practices

BP.060 Develop High-Level Process Vision

BP.070 Develop High-Level Process Design

BP.080 Develop Future Process Model

BP.090 Document Business Procedure

Business Requirement Definition (RD) - This phase explains about the initial baseline questionnaire and requirement gatherings.

RD.010 Identify Current Financial and Operating Structure

RD.020 Conduct Current Business Baseline

RD.030 Establish Process and Mapping Summary

RD.040 Gather Business Volumes and Metrics

RD.050 Gather Business Requirements

RD.060 Determine Audit and Control Requirements

RD.070 Identify Business Availability Requirements

RD.080 Identify Reporting and Information Access Requirements

Business Requirement Mapping (BR) - In this phase the requirements of business are matched with the standard functionality of the oracle applications.

BR.010 Analyze High-Level GapsBR.020 Prepare mapping environment

BR.030 Map Business requirements

BR.040 Map Business Data

BR.050 Conduct Integration Fit Analysis

BR.060 Create Information Model

BR.070 Create Reporting Fit Analysis

BR.080 Test Business Solutions

BR.090 Confirm Integrated Business Solutions

BR.100 Define Applications Setup

BR.110 Define security Profiles

Application and Technical Architecture (TA) - This outlines the infrastructure requirements to implement oracle applications.

TA.010 Define Architecture Requirements and Strategy

TA.020 Identify Current Technical Architecture

TA.030 Develop Preliminary Conceptual Architecture

TA.040 Define Application Architecture

TA.050 Define System Availability Strategy

TA.060 Define Reporting and Information Access Strategy

TA.070 Revise Conceptual Architecture

TA.080 Define Application Security Architecture

TA.090 Define Application and Database Server Architecture

TA.100 Define and Propose Architecture Subsystems

TA.110 Define System Capacity Plan

TA.120 Define Platform and Network Architecture

TA.130 Define Application Deployment Plan

TA.140 Assess Performance Risks

TA.150 Define System Management Procedures

Build and Module Design (MD) - This phase emphasizes the development of new functionality (customization) required by the client. It mainly details how to design the required forms, database and reports.

MD.010 Define Application Extension Strategy

MD.020 Define and estimate application extensions

MD.030 Define design standards

MD.040 Define Build Standards

MD.050 Create Application extensions functional design

MD.060 Design Database extensions

MD.070 Create Application extensions technical design

MD.080 Review functional and Technical designs

MD.090 Prepare Development environment

MD.100 Create Database extensions

MD.110 Create Application extension modules

MD.120 Create Installation routines

Data Conversion (CV) - Data Conversion is the process of converting or transferring the data from legacy system to oracle applications.

CV.010 Define data conversion requirements and strategy

CV.020 Define Conversion standards

CV.030 Prepare conversion environment

CV.040 Perform conversion data mapping

CV.050 Define manual conversion procedures

CV.060 Design conversion programs

CV.070 Prepare conversion test plans

CV.080 Develop conversion programs

CV.090 Perform conversion unit tests

CV.100 Perform conversion business objects

CV.110 Perform conversion validation tests

CV.120 Install conversion programs

CV.130 Convert and verify data

Documentation (DO) - Documentation prepared per module that includes user guides and implementation manuals.

DO.010 Define documentation requirements and strategy

DO.020 Define Documentation standards and procedures

DO.030 Prepare glossary

DO.040 Prepare documentation environment

DO.050 Produce documentation prototypes and templates

DO.060 Publish user reference manual

DO.070 Publish user guide

DO.080 Publish technical reference manual

DO.090 Publish system management guide

Business System Testing (TE) - A process of validating the setup’s by QA (functional consultant) to certify status.

TE.010 Define testing requirements and strategy

TE.020 Develop unit test script

TE.030 Develop link test script

TE.040 Develop system test script

TE.050 Develop systems integration test script

TE.060 Prepare testing environments

TE.070 Perform unit test

TE.080 Perform link test

TE.090 perform installation test

TE.100 Prepare key users for testing

TE.110 Perform system test

TE.120 Perform systems integration test

TE.130 Perform Acceptance test

Performance Testing (PT) - Performance testing is the evaluation of transactions saving time, transaction retrieval times, workflow background process, database performance, etc…

PT.010 – Define Performance Testing Strategy

PT.020 – Identify Performance Test Scenarios

PT.030 – Identify Performance Test Transaction

PT.040 – Create Performance Test Scripts

PT.050 – Design Performance Test Transaction Programs

PT.060 – Design Performance Test Data

PT.070 – Design Test Database Load Programs

PT.080 – Create Performance Test Transaction Programs

PT.090 – Create Test Database Load Programs

PT.100 – Construct Performance Test Database

PT.110 – Prepare Performance Test Environment

PT.120 – Execute Performance Test

Adoption and Learning (AP) - This phase explains the removal of the legacy system and oracle application roll out enterprise wide.

AP.010 – Define Executive Project Strategy

AP.020 – Conduct Initial Project Team Orientation

AP.030 – Develop Project Team Learning Plan

AP.040 – Prepare Project Team Learning Environment

AP.050 – Conduct Project Team Learning Events

AP.060 – Develop Business Unit Managers Readiness Plan

AP.070 – Develop Project Readiness Roadmap

AP.080 – Develop and Execute Communication Campaign

AP.090 – Develop Managers’ Readiness Plan

AP.100 – Identify Business Process Impact on Organization

AP.110 – Align Human Performance Support Systems

AP.120 – Align Information Technology Groups

AP.130 – Conduct User Learning Needs Analysis

AP.140 – Develop User Learning Plan

AP.150 – Develop User Learning ware

AP.160 – Prepare User Learning Environment

AP.170 – Conduct User Learning Events

AP.180 – Conduct Effectiveness Assessment

Production Migration (PM) - The process of “decommissioning” of legacy system and the usage of oracle application system.

PM.010 – Define Transition Strategy

PM.020 – Design Production Support Infrastructure

PM.030 – Develop Transition and Contingency Plan

PM.040 – Prepare Production Environment

PM.050 – Set Up Applications

PM.060 – Implement Production Support Infrastructure

PM.070 – Verify Production Readiness

PM.080 – Begin Production

PM.090 – Measure System Performance

PM.100 – Maintain System

PM.110 – Refine Production System

PM.120 – Decommission Former Systems

PM.130 – Propose Future Business Direction

PM.140 – Propose Future Technical Direction

---X---