Oracle R12 Order Management - Back to Back (B2B) Order Flow

Oracle R12 Order Management - Back to Back (B2B) Order Flow:

Back to Back Order type is used in the below scenarios:

1. If the Customer ordered part is not in stock
2. If the Customer ordered part is not manufactured 
3. Customer will place the order to the organization, organization will generate the purchase order to the supplier and the supplier will ship the parts to the organization and organization ships the part to the customer.
4. Here in Back to Back order Sales order is linked to the purchase order

The below attributes should be defined in Item Master for the items as B2B Orderable:

• In Purchasing Tab - Purchased, Purchasable, Use Approved Supplier, Default Buyer & List Price to be defined
• In General Planning Tab - To be defined as "Buy"
• In Work In Process Tab - "Build in WIP" attribute flag to be enabled
• In Order Management Tab - Customer Ordered, Customer Orders Enabled, Shippable, OE Transactable & Assemble to Order flag to be enabled
• B2B Orderable Items should be assigned in the order receiving organization.
• B2B Orderable Items should be defined in the Price List

Oracle Order Management - Back to Back Order Flow:

• Enter a sales order and enter the B2B Item

Ensure whether the ATO flag is enabled in sales order line level - Main tab & Source Type is "Internal" in Shipping tab.

Once the Sales order is entered for the B2B Part, the Sales order Line status will be "Entered"

• Book the sales order 

Once the Sales order is booked, the Sales order Line status wil be "Supply Eligible"

• Progress the B2B Orderable

Right Click on the line and select Progress Order, Create Supply Order - Eligible Windows Opens. Click OK.

Once the Progress order is done for the Sales order line, the Sales order Line status will be "External Req Requested"

• Import the Requisition

Run the Requisition Import Concurrent with Import Source as CTO

• Query the B2B Part number in Requisition Summary

Requisition would have been created with Sales Order details in Note to Buyer 

you can see the sales order delivery line id is linked with requisition, while querying in "po_requisition_header_all" table for the requisition header id.

Once the Requisition is imported, the sales order line status will be "External Req Open"

• Auto create the Purchase Release 

Query the Requisition in Auto Create form and Auto create the Purchase order for the defined supplier.

Once the purchase order is created & approved, the sales order line status will be "PO Open"

• Receive the parts

Query the PO number in the Receipt form and receive the part.

Once the receipt is created, the sales order line status will be "In Receiving"

• Inspect the parts

Query the receipt number in Receiving Transaction form and accept the part.

• Deliver the parts

Query the receipt number in Receiving Transaction form and deliver the part.

Once the part is delivered to the subinventory, the sales order line status will be "Awaiting Shipping"

• Stage pick & Ship the parts

Release and ship the sales order 

Please note below the sales order line status for each activity in Back to Back order flow in Oracle R12 Order Management.

Oracle AIM Documentation

Oracle AIM Documentation

In Continuation to my previous post on Oracle Application Implementation Methodology Phases & Processes. In this post, provided the deliverable of Oracle AIM Processes.

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

Oracle AIM Life Cycle:

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

1.     Business Process Architecture [BP]

This phase explains the Existing Business Practices, Catalog change practices, Leading practices & Future practices

BP010            Define Business and Process Strategy

BP020            Catalog and Analyze Potential Changes

BP030            Determine Data Gathering Requirements

BP040            Develop Current Process Model

BP050            Review Leading Practices

BP060            Develop High-Level Process Vision

BP070            Develop High-Level Process Design

BP080            Develop Future Process Model

BP090            Document Business Procedure

2. Business Requirement Definition [RD]

This phase explains about the initial baseline questionnaire and gathering of requirements.

RD010             Identify Current Financial and Operating Structure

RD020             Conduct Current Business Baseline

RD030             Establish Process and Mapping Summary

RD040             Gather Business Volumes and Metrics

RD050             Gather Business Requirements

RD060             Determine Audit and Control Requirements

RD070             Identify Business Availability Requirements

RD080             Identify Reporting and Information Access Requirements

3. Business Requirement Mapping [BR]

In this phase the requirements of business are matched with the standard functionality of the oracle applications.

BR010             Analyze High-Level Gaps

BR020             Prepare mapping environment

BR030             Map Business requirements

BR040             Map Business Data

BR050             Conduct Integration Fit Analysis

BR060             Create Information Model

BR070             Create Reporting Fit Analysis

BR080             Test Business Solutions

BR090             Confirm Integrated Business Solutions

BR100             Define Applications Setup

BR110             Define security Profiles

4. Application and Technical Architecture [TA]

This outlines the infrastructure requirements to implement oracle applications.

TA010             Define Architecture Requirements and Strategy

TA020             Identify Current Technical Architecture

TA030             Develop Preliminary Conceptual Architecture

TA040             Define Application Architecture

TA050             Define System Availability Strategy

TA060             Define Reporting and Information Access Strategy

TA070             Revise Conceptual Architecture

TA080             Define Application Security Architecture

TA090             Define Application and Database Server Architecture

TA100             Define and Propose Architecture Subsystems

TA110             Define System Capacity Plan

TA120             Define Platform and Network Architecture

TA130             Define Application Deployment Plan

TA140             Assess Performance Risks

TA150             Define System Management Procedures

5. 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.

MD010           Define Application Extension Strategy

MD020           Define and estimate application extensions

MD030           Define design standards

MD040           Define Build Standards

MD050           Create Application extensions functional design

MD060           Design Database extensions

MD070           Create Application extensions technical design

MD080           Review functional and Technical designs

MD090           Prepare Development environment

MD100           Create Database extensions

MD110           Create Application extension modules

MD120           Create Installation routines

6. Data Conversion [CV]

Data Conversion is the process of converting or transferring the data from legacy system to oracle applications. Ex. Transferring customer records from the legacy to the Customer Master.

CV010             Define data conversion requirements and strategy

CV020             Define Conversion standards

CV030             Prepare conversion environment

CV040             Perform conversion data mapping

CV050             Define manual conversion procedures

CV060             Design conversion programs

CV070             Prepare conversion test plans

CV080             Develop conversion programs

CV090             Perform conversion unit tests

CV100             Perform conversion business objects

CV110             Perform conversion validation tests

CV120             Install conversion programs

CV130             Convert and verify data

7. Documentation [DO]

Documentation prepared per module that includes user guides and implementation manuals.

DO010            Define documentation requirements and strategy

DO020            Define Documentation standards and procedures

DO030            Prepare glossary

DO040            Prepare documentation environment

DO050            Produce documentation prototypes and templates

DO060            Publish user reference manual

DO070            Publish user guide

DO080            Publish technical reference manual

DO090            Publish system management guide

8. Business System Testing [TE]

A process of validating the setup’s and functionality by QA (Functional Consultant) to certify status.

TE010              Define testing requirements and strategy

TE020              Develop unit test script

TE030              Develop link test script

TE040              Develop system test script

TE050              Develop systems integration test script

TE060              Prepare testing environments

TE070              Perform unit test

TE080              Perform link test

TE090              Perform installation test

TE100              Prepare key users for testing

TE110              Perform system test

TE120              Perform systems integration test

TE130              Perform Acceptance test

9. Performance Testing [PT]

Performance testing is the evaluation of transactions saving time, transaction retrieval times, workflow background process, database performance, etc

PT010              Define Performance Testing Strategy

PT020              Identify Performance Test Scenarios

PT030              Identify Performance Test Transaction

PT040              Create Performance Test Scripts

PT050              Design Performance Test Transaction Programs

PT060              Design Performance Test Data

PT070              Design Test Database Load Programs

PT080              Create Performance Test Transaction Programs

PT090              Create Test Database Load Programs

PT100              Construct Performance Test Database

PT110              Prepare Performance Test Environment

PT120              Execute Performance Test

10. Adoption and Learning [AP]

This phase explains the removal of the legacy system and oracle application roll out enterprise wide.

AP010             Define Executive Project Strategy

AP020             Conduct Initial Project Team Orientation

AP030             Develop Project Team Learning Plan

AP040             Prepare Project Team Learning Environment

AP050             Conduct Project Team Learning Events

AP060             Develop Business Unit Managers’ Readiness Plan

AP070             Develop Project Readiness Roadmap

AP080             Develop and Execute Communication Campaign

AP090             Develop Managers’ Readiness Plan

AP100             Identify Business Process Impact on Organization

AP110             Align Human Performance Support Systems

AP120             Align Information Technology Groups

AP130             Conduct User Learning Needs Analysis

AP140             Develop User Learning Plan

AP150             Develop User Learning ware

AP160             Prepare User Learning Environment

AP170             Conduct User Learning Events

AP180             Conduct Effectiveness Assessment

11. Production Migration [PM]

The process of “decommissioning” of legacy system and the usage (adoption) of oracle application system.

PM010            Define Transition Strategy

PM020            Design Production Support Infrastructure

PM030            Develop Transition and Contingency Plan

PM040            Prepare Production Environment

PM050            Set Up Applications

PM060            Implement Production Support Infrastructure

PM070            Verify Production Readiness

PM080            Begin Production

PM090            Measure System Performance

PM100            Maintain System

PM110            Refine Production System

PM120            Decommission Former Systems

PM130            Propose Future Business Direction

PM140            Propose Future Technical Direction

Oracle Application Implementation Methodology- Oracle AIM

Oracle Application Implementation Methodologies:

•      Oracle AIM 3.1 (Application Implementation Methodology)

•      Oracle EMM (Easy Migration Methodology)

•      Oracle Unified Method (OUM)

Oracle AIM:

•      Oracle AIM is a methodology showing what tasks are required, what order it should be completed in and what resources are required

•      Oracle AIM provides templates for all the tasks that require them.

•      The methodology is purpose built for Oracle Applications and the detailed deliverables produced are designed with the Oracle Application products in mind.

Oracle AIM Structure:

•      A phase is a chronological grouping of tasks. It enables a flexible way to organize tasks, schedule major deliverables, and deliver projects.

•      A process is a closely related group of dependent tasks which meets a major objective. A process is usually based on a common discipline.

•      A task is a unit of work, which results in a single deliverable. I. e reports, schedules, code, or test results for example.

Oracle AIM Process Flow:

Oracle AIM Project Phases:

•      An AIM project is conducted in phases that provide quality and control checkpoints to co-ordinate project activities that have a common goal.

•      During a project phase, project team will be executing tasks from several processes

•      Oracle AIM Project Phases as follows (6 Phases)

–     Definitions

–     Operation Analysis

–     Solution Design

–     Build

–     Transition

–     Production

  

Oracle AIM Phases:

•      Definition

–     Plan the project

–     Review the organization's business objectives

–     Evaluate the feasibility of meeting those objectives under time, resource, and budget constraints

–     Emphasis is on building an achievable work plan and introducing it with guidelines.

–     Strategies, objectives and approaches are determined for each AIM process

•      Operations Analysis

–     Project team develops Business Requirements

–     Assess the level of fit between the business requirements and standard application functionality.

–     Gaps are identified and corresponding solutions developed.

–     Solutions for gaps evolve into detailed designs during Solution Design.

•      Solution Design

–     Develop the detailed designs to meet the future business requirements.

–     Project team members create detailed narratives of process solutions developed during Operations Analysis

–     Supporting business requirements may require building application extensions to standard features

–     The project team carefully scrutinizes these solutions and chooses the most cost effective alternatives.

•      Build

–     Coding and testing of all customizations and other custom software

–     Coding & testing of enhancements, data conversions, and interfaces

–     Policy and procedure changes relating to business process modifications are developed.

–     Business system testing is performed to validate that the developed solutions meet business requirements.

•      Transition

–     Deploys the finished solution into the organization

–     The project team trains the end users

–     Technical team configures the production environment and converts data

–     Transition ends with the cutover to production, when end users start performing their job duties using the new system.

•      Production

–     It marks the last phase of the implementation, and the beginning of the system support cycle.

–     The Information Systems (IS) personnel work quickly to stabilize the system and begin regular maintenance.

–     Provide the ongoing support to the organization for the remaining life of the system.

–     Compare actual results to project objectives.

Oracle AIM Processes:

•      A process in AIM represents a related set of objectives, resource skill requirements, inputs, and deliverable outputs.

•      A task can belong to only one process.

•      Project team members are usually assigned to a process according to their specialization and background.

•      12 Processes as referred in AIM –

–     Project Management

–     Business Process Architecture

–     Business Requirement Definition

–     Business Requirement Mapping

–     Application & Technical Architecture

–     Module Design & Build

–     Data Conversion

–     Documentation

–     Business System Testing

–     Performance Testing

–     Adoption & Learning

–     Production Migration

•      Project Management (PJM)

–     Task Code/ID : CR: Control & Reporting, WM: Work Management, RM: Resource Management, QM: Quality Management & CM: Configuration Management

–     Project & Phase Planning, Execution, Control, Reporting & Completion

–     Work Management & Resource Management

–     Quality Management & Configuration Management

–     Project Management itself is a comprehensive process and has separate way to handle it, i.e. PMBOK , Oracle PJM etc

•      Business Process Architecture

–     Task Code/ID : BP

–     Provide the framework for combining change in business processes with implementation of software applications

–     It focuses on high-level business processes and operations generally applicable to the organization

–     Make business focused decisions either to change the current processes to suit the application or to customize the application.

•      Business Requirements Definition

–     Task Code/ ID: RD

–     Defines the business needs that must be met by the implementation project.

–     Develop a complete set of business requirements scenarios that can be used to map business requirements to application functionality.

–     Analyze and identify the reporting requirements for the business

–     Carefully document audit and control requirements to satisfy financial and quality policies.

•      Business Requirements Mapping

–     Task Code/ ID: BR

–     Ascertain the fitness for use of application features in satisfying detailed business requirements expressed at a business process step level.

–     Business Requirements Mapping encompasses the following areas:

•      Mapping

•      Business system testing

•      Application setups

–     Mapping is an iterative approach with the following objectives:

•      Prove business process designs through demonstration

•      Identify gaps in the application

•      Propose feasible bridges to gaps

•      Application & Technical Architecture

–     Task Code/ ID: TA

–     Design an information systems architecture to realize the business vision.

–     This process divide into two areas:- 1. Application Architecture, 2. Technical Architecture

–     The process takes the business and information systems requirements and develops a blueprint for deploying and configuring:

•      Oracle, third-party, and custom applications

•      Supporting application server environments

•      Critical interfaces and data distribution mechanisms between applications, servers, and sites

•      Computing hardware, including servers and client desktop platforms

•      Networks and communications infrastructure

•      Module Design & Build

–     Task Code/ ID: MD

–     Focus on the design and development of customizations to satisfy functionality gaps identified during Business Requirements Mapping (BR).

–     Modification — changes to the base Oracle Applications code

–     Extension — new forms, reports, programs, tables, interfaces and triggers that add functionality without changing the base application code

–     Configurable Extension — addition of functionality through  flex fields, alerts, and other configuration options provided by the Applications

•      Data Conversion

–     Task Code/ ID: CV

–     Convert and test all necessary legacy data for the operation of the new system

–     Conversion Approaches

•      Manual Conversions

•      Programmatic Conversion with or w/o tools

•      Automated Data Entry

•      Documentation

–     Task Code/ ID: DO

–     Reference that shows the users how to use application functionality

–     Set of procedures for using the application in response to day-to-day business events

–     Documents that describe the technical details of the application for the maintenance staff

–     Produce a set of procedures for managing the system

•      Business System Testing

–     Task Code/ ID: TE

–     Three main aspects of Business Testing – Planning, Early Introduction of Testing & CRP

–     Business System Testing does not address performance testing or the testing of data conversion programs

•      Performance Testing

–     Task Code/ ID: PT

–     Enables you to define, build, and execute a performance test.

–     To make decisions on whether the performance is acceptable for the business

–     Propose tactical or strategic changes to address the performance quality shortfall.

–     Automated V/s Manual

–     Types of Performance Testing

•      System Performance

•      Module/ Code Performance

•      Hardware and Networks

•      Adoption & Learning

–     Task Code/ ID: AP

–     Training prepares both users and administrators to assume on the tasks of running the new application system

–     Adoption and Learning impacts the following five major audiences:

•      Executives

•      Implementation project teams

•      Functional managers

•      Users

•      Information technology groups

•      Production Migration

–     Task Code/ ID: PM

–     To migrate the organization, systems, & people to the new enterprise system

–     Assessing readiness for transition to production

–     Executing cutover to the new system

–     Conducting post-production support

Oracle AIM Advantages:

•      Oracle's AIM is a proven approach for implementing packaged applications. It comprises a set of well-defined processes that can be managed in several ways to guide you through an application implementation project.

•      AIM provides the tools needed to effectively and efficiently plan, conduct, and control project steps to successfully implement business solutions.

•      AIM defines business needs at the beginning of the project and maintains their visibility throughout the implementation.

•      It defines internal, external, and time sensitive business events and maps each event to the responding business and system processes.

•      Client gains an accurate understanding of the business requirements that need to be focused on during the course of the implementation.