This document provides an overview of the key setup steps for implementing Oracle iProcurement using punchouts, including:
1. Configuring punchouts to integrate iProcurement with supplier websites for requisitioning.
2. Setting up typical iProcurement steps like requisition creation, approval, purchase order creation and approval.
3. Configuring account generation rules, workflows, flexfields, and other options needed to support the iProcurement process in Oracle.
The document discusses several new features in Oracle R12 related to order management. It covers cascading attributes from headers to lines, customer acceptance tracking, deferred cost of goods sold, exception management, multi-org access, sales agreements, actual ship dates, and parallel pick release. Key points include how each feature works and how to set them up in the R12 system.
Tips on setting up an eCcommerce web site using istoreravisagaram
Tips on setting up an eCommerce web site using istore. The deck was presented at NCOAUG. The deck provides several tips based on a full fledged implementation of a global eCommerce web site at a fortune 500 company
The document discusses various types of dates used in order management and shipping processes, including ordered date, request date, scheduled ship date, earliest/latest acceptable dates, promise date, pricing date, actual ship date, and actual arrival date. For each date type, it describes the intended use, whether it is set at the header or line level, defaulting options, and how it can be queried. The document provides details on how these date fields work together to manage ordering, scheduling, shipping, and delivery of products and services to customers.
This presentation is about how to Create Drop Ship Sales Order Across the Operating Units in R12i and then how to perform Inter company Transactions.
Here I will discuss following Process
1.Drop Ship SO Creation
2.PO Creation
3.Receiving against PO
4.AP/AR Invoice Creation
5.Intercompany Invoice Creation
The document discusses Oracle's capabilities for procurement of complex services. It defines complex services and outlines Oracle's end-to-end process for handling complex procurements from requesting services to tracking progress and processing payments according to negotiated terms. Key areas covered include creating RFQs, authoring contracts with provisions for advances, payment schedules, and retainage, and integrating supplier confirmations and invoicing with accounting and projects modules. The presentation provides a case study example and highlights benefits of Oracle's functionality for streamlining complex procurement processes.
Oracle Services Procurement provides an integrated platform for automating and streamlining the services procurement process. It allows users to source, procure, and manage payment for contingent labor, professional services, and business services. Enhancements have been made to increase customer satisfaction by lowering costs and driving adoption. The solution provides flexibility for users to capture job requirements and assign timecards to multiple projects. It aims to address issues like only allowing one purchase order per contingent worker and inaccurate supplier invoices.
This document provides a step-by-step guide on using Business Transaction Events (BTEs) as an enhancement technique in SAP's Financial Accounting module. It describes what BTEs are, the difference between BTEs and BADIs, the two types of BTE interfaces, and provides an example of how to configure a BTE to copy an assignment field with a custom value when accounting documents are posted for a specific company code. The document outlines finding the relevant BTE, copying the sample function module, writing ABAP code to update the field, saving and activating the function module, and assigning it to the appropriate event, country and application.
Create invoice by Oracle iSupplier portalHamdy Elbana
The document discusses a new feature in Oracle Applications that allows suppliers to submit invoices online using the iSupplier Portal. Suppliers can select approved purchase order shipments, enter quantity to invoice, and additional charges. The submitted invoice will be imported into Accounts Payable. The feature requires installation of specific patches and the "Create Invoices" menu must be enabled for supplier responsibilities.
The document discusses several new features in Oracle R12 related to order management. It covers cascading attributes from headers to lines, customer acceptance tracking, deferred cost of goods sold, exception management, multi-org access, sales agreements, actual ship dates, and parallel pick release. Key points include how each feature works and how to set them up in the R12 system.
Tips on setting up an eCcommerce web site using istoreravisagaram
Tips on setting up an eCommerce web site using istore. The deck was presented at NCOAUG. The deck provides several tips based on a full fledged implementation of a global eCommerce web site at a fortune 500 company
The document discusses various types of dates used in order management and shipping processes, including ordered date, request date, scheduled ship date, earliest/latest acceptable dates, promise date, pricing date, actual ship date, and actual arrival date. For each date type, it describes the intended use, whether it is set at the header or line level, defaulting options, and how it can be queried. The document provides details on how these date fields work together to manage ordering, scheduling, shipping, and delivery of products and services to customers.
This presentation is about how to Create Drop Ship Sales Order Across the Operating Units in R12i and then how to perform Inter company Transactions.
Here I will discuss following Process
1.Drop Ship SO Creation
2.PO Creation
3.Receiving against PO
4.AP/AR Invoice Creation
5.Intercompany Invoice Creation
The document discusses Oracle's capabilities for procurement of complex services. It defines complex services and outlines Oracle's end-to-end process for handling complex procurements from requesting services to tracking progress and processing payments according to negotiated terms. Key areas covered include creating RFQs, authoring contracts with provisions for advances, payment schedules, and retainage, and integrating supplier confirmations and invoicing with accounting and projects modules. The presentation provides a case study example and highlights benefits of Oracle's functionality for streamlining complex procurement processes.
Oracle Services Procurement provides an integrated platform for automating and streamlining the services procurement process. It allows users to source, procure, and manage payment for contingent labor, professional services, and business services. Enhancements have been made to increase customer satisfaction by lowering costs and driving adoption. The solution provides flexibility for users to capture job requirements and assign timecards to multiple projects. It aims to address issues like only allowing one purchase order per contingent worker and inaccurate supplier invoices.
This document provides a step-by-step guide on using Business Transaction Events (BTEs) as an enhancement technique in SAP's Financial Accounting module. It describes what BTEs are, the difference between BTEs and BADIs, the two types of BTE interfaces, and provides an example of how to configure a BTE to copy an assignment field with a custom value when accounting documents are posted for a specific company code. The document outlines finding the relevant BTE, copying the sample function module, writing ABAP code to update the field, saving and activating the function module, and assigning it to the appropriate event, country and application.
Create invoice by Oracle iSupplier portalHamdy Elbana
The document discusses a new feature in Oracle Applications that allows suppliers to submit invoices online using the iSupplier Portal. Suppliers can select approved purchase order shipments, enter quantity to invoice, and additional charges. The submitted invoice will be imported into Accounts Payable. The feature requires installation of specific patches and the "Create Invoices" menu must be enabled for supplier responsibilities.
This document provides a detailed overview of the procure-to-pay (P2P) process in Oracle SCM Purchasing R12, including how to create suppliers, requests for quotations (RFQs), purchase orders (POs), receipts, invoices, and post transactions to the general ledger. The presentation walks through each step, providing navigation instructions and explanations of key fields and status updates. It demonstrates the full P2P lifecycle from supplier setup to invoice payment and accounting close.
This document discusses the differences between back to back and drop ship sales order processes in Oracle applications. Back to back orders involve procuring an item after a sales order is created, while drop ship orders involve shipping an item directly from the supplier to the customer. The document outlines the key steps and complexities involved in each process, as well as the pros and cons. It also provides examples of business scenarios that are well-suited for each approach.
This document provides a quick start guide for using Oracle Sourcing to create a request for information (RFI), request for quote (RFQ), or auction. It outlines the 13 key steps: 1) input header details, 2) manage collaboration team, 3) add requirements, 4) manage terms/attachments, 5) create lines, 6) set controls and event timing, 7) select suppliers, 8) review and publish, 9) open invitation, 10) acknowledge participation, 11) create and submit proposal/bid, 12) open negotiations, and 13) closed negotiations and award. Each step includes screenshots and explanations of the relevant fields and options.
The document provides an overview and demonstration of Oracle Sourcing, an application for online sourcing and procurement. It outlines the key steps in an RFQ process from creation and publishing to supplier response, evaluation, and award. It also notes some limitations, including an inability to update existing purchase orders and a lack of APIs to integrate with external systems.
This document discusses configuring business transaction events (BTEs) in SAP to email electronic funds transfer (EFT) remittance advices to vendors. It describes finding relevant BTEs using transaction BERP, customizing an existing BTE function module to extract vendor email addresses from the SAP system and set the message type to internet, and configuring the BTE using transaction FIBF to activate it for a customer product. Testing is done by running a payment through transaction F110 to trigger the BTE, and viewing the email send requests in SOST.
Oracle Service Contracts provides a complete solution to author, execute, and manage various types of service contracts including warranties, extended warranties, subscriptions, and more complex agreements. Key components of a contract include a header, lines, and sub-lines. Contracts go through a lifecycle of creation, approval, extension/renewal, termination, and ongoing management. Oracle Install Base is used to track item instances throughout their lifecycle from receipt to return/repair.
This document provides an overview of Oracle's Financial Data Quality Management, Enterprise Edition (FDMEE). It describes FDMEE's introduction, architecture, key differences from the previous Financial Data Management product, and value-added features. The document also walks through the FDMEE graphical user interface and components for navigation, setup, integration, data loading, and batch processing.
The document discusses challenges with cost management data flow and matching costs of goods sold (COGS) to revenue in Oracle Applications Release 12.0.4. Key issues included duplicate COGS accounting, report performance problems, and difficulty analyzing output. Lessons focused on thorough testing of end-to-end processes, configurations, and performance before go-live and during period closes.
Sometimes you across "technical" terms in Oracle apps(budget book,auto allocation rules etc.) which you might have no idea,this documents would be helpful to understand all the "technical" terms used in Oracle Apps.
The document discusses intercompany transaction flows in Oracle applications between two or three operating units (OUs). It describes how intercompany shipping and procurement flows are triggered when the booking/purchasing OU is different from the shipping/receiving OU. The key steps to set up intercompany transaction flows and the logical and financial transactions generated between OUs are explained. Transfer pricing logic, programs to create intercompany invoices, and examples of material and financial flows with 2-3 OUs are also covered.
The document outlines the basic structure and procedures for a procurement department, including sections for purchase requests, purchase orders, delivery, receiving, expenses, and payments. It also provides details on the desired functionality and reporting capabilities of a software system to manage the procurement process. Key requirements include linking all stages of procurement, maintaining records and logs of activities, and generating status reports at each stage. The target timeline to develop, test, and implement the customized procurement software is 60 days.
Summary accounts provide efficiencies for business processing by representing the sum of multiple detailed account balances. They allow for faster reporting and inquiry compared to reviewing each detailed account individually. A summary account template is used to generate multiple summary accounts based on the detail and parent segment values defined. Maintaining summary accounts involves tasks like adding or removing child accounts to update the rolled-up balances totaled in each summary account.
1) The document discusses tips for coping with intercompany invoicing in Oracle EBS, including reconciliation, scheduling concurrent programs daily, adding descriptions, monitoring for errors, and controlling the valuation cutoff date.
2) It recommends creating a Discoverer worksheet to reconcile intercompany payables and receivables invoices.
3) Scheduling the four required concurrent programs daily helps detect errors quicker than running them monthly.
Oracle EBS ERP user group presentation. Originally presented in June 2005 at the Connection Point 2005 conference in Dallas. Revised in 2007. Addresses EBS 11i but relevant to R12!
The document outlines the key steps in the order to cash cycle in an ERP system. It includes entering a sales order, booking the order, picking and shipping the order, invoicing, receiving payment, and transferring transactions to the general ledger. Details are provided on the underlying tables affected and navigation for each step.
Oracle Install Base is an application that tracks item instances throughout their lifecycle, from receipt to deployment to repair. It provides a centralized repository of information on item instances, including location, status, ownership, and configuration. Key features include item instance maintenance, relationships with parties and accounts, integration with other Oracle modules, and tracking of serialized and non-serialized items.
This document provides instructions for configuring a company code in SAP FICO. It begins with an introduction to SAP FI and relevant terminology. It then outlines the steps to define a company, create a company code, assign the company code to a company and chart of accounts, define relevant organizational structures and assign them to the company code, and configure settings for the currency, fiscal year, posting periods, document numbers, and more. The goal is to fully configure company code 1100 for the fictional company ABC Ltd located in the US.
Here are the key steps the Accrual Diagnostics script performs to help troubleshoot reconciliation issues:
1. It spools data from key accrual related tables like cst_reconciliation_build, cst_reconciliation_summary, cst_ap_po_reconciliation, cst_misc_reconciliation, gl_je_headers, gl_je_lines etc to an HTML file based on the input parameters provided.
2. It calculates the accrual balance in GL for Cost Management transactions by summing amounts from gl_je_lines for the given ledger, operating unit, accrual account and date range.
3. It calculates the accrual balance in subledger by summing amounts from c
The InterCompany Solution enables data consolidation and sharing of financial information between partner companies. It provides visibility across operations, improves control and collaboration. The solution integrates partner companies, replicates master data, automates intercompany transactions, and provides reports like consolidated balances. It supports tasks like allocations, payments, inventory sharing, and financial consolidation across multiple business entities.
This document discusses Oracle's Transaction Account Builder (TAB) which is used to derive accounting flexfields for subledger transactions in Oracle Fusion Applications. TAB replaces prior account generator solutions and provides a more flexible and configurable way to default transaction accounts. The key building blocks of TAB include Transaction Account Definitions, Transaction Account Types, Account Rules, Mapping Sets, and Sources. Seeded TAB setup and custom TAB setup options are also described.
This document discusses Oracle's Transaction Account Builder (TAB) which is used to derive accounting flexfields for subledger transactions in Oracle Fusion Applications. TAB replaces prior account generator solutions and provides a more flexible and configurable way to default transaction accounts. The key building blocks of TAB include Transaction Account Definitions, Transaction Account Types, Account Rules, Mapping Sets, and Sources. Seeded TAB setup and configuration options are also described to help customers understand how TAB can be used to meet their specific account defaulting requirements.
This document provides a detailed overview of the procure-to-pay (P2P) process in Oracle SCM Purchasing R12, including how to create suppliers, requests for quotations (RFQs), purchase orders (POs), receipts, invoices, and post transactions to the general ledger. The presentation walks through each step, providing navigation instructions and explanations of key fields and status updates. It demonstrates the full P2P lifecycle from supplier setup to invoice payment and accounting close.
This document discusses the differences between back to back and drop ship sales order processes in Oracle applications. Back to back orders involve procuring an item after a sales order is created, while drop ship orders involve shipping an item directly from the supplier to the customer. The document outlines the key steps and complexities involved in each process, as well as the pros and cons. It also provides examples of business scenarios that are well-suited for each approach.
This document provides a quick start guide for using Oracle Sourcing to create a request for information (RFI), request for quote (RFQ), or auction. It outlines the 13 key steps: 1) input header details, 2) manage collaboration team, 3) add requirements, 4) manage terms/attachments, 5) create lines, 6) set controls and event timing, 7) select suppliers, 8) review and publish, 9) open invitation, 10) acknowledge participation, 11) create and submit proposal/bid, 12) open negotiations, and 13) closed negotiations and award. Each step includes screenshots and explanations of the relevant fields and options.
The document provides an overview and demonstration of Oracle Sourcing, an application for online sourcing and procurement. It outlines the key steps in an RFQ process from creation and publishing to supplier response, evaluation, and award. It also notes some limitations, including an inability to update existing purchase orders and a lack of APIs to integrate with external systems.
This document discusses configuring business transaction events (BTEs) in SAP to email electronic funds transfer (EFT) remittance advices to vendors. It describes finding relevant BTEs using transaction BERP, customizing an existing BTE function module to extract vendor email addresses from the SAP system and set the message type to internet, and configuring the BTE using transaction FIBF to activate it for a customer product. Testing is done by running a payment through transaction F110 to trigger the BTE, and viewing the email send requests in SOST.
Oracle Service Contracts provides a complete solution to author, execute, and manage various types of service contracts including warranties, extended warranties, subscriptions, and more complex agreements. Key components of a contract include a header, lines, and sub-lines. Contracts go through a lifecycle of creation, approval, extension/renewal, termination, and ongoing management. Oracle Install Base is used to track item instances throughout their lifecycle from receipt to return/repair.
This document provides an overview of Oracle's Financial Data Quality Management, Enterprise Edition (FDMEE). It describes FDMEE's introduction, architecture, key differences from the previous Financial Data Management product, and value-added features. The document also walks through the FDMEE graphical user interface and components for navigation, setup, integration, data loading, and batch processing.
The document discusses challenges with cost management data flow and matching costs of goods sold (COGS) to revenue in Oracle Applications Release 12.0.4. Key issues included duplicate COGS accounting, report performance problems, and difficulty analyzing output. Lessons focused on thorough testing of end-to-end processes, configurations, and performance before go-live and during period closes.
Sometimes you across "technical" terms in Oracle apps(budget book,auto allocation rules etc.) which you might have no idea,this documents would be helpful to understand all the "technical" terms used in Oracle Apps.
The document discusses intercompany transaction flows in Oracle applications between two or three operating units (OUs). It describes how intercompany shipping and procurement flows are triggered when the booking/purchasing OU is different from the shipping/receiving OU. The key steps to set up intercompany transaction flows and the logical and financial transactions generated between OUs are explained. Transfer pricing logic, programs to create intercompany invoices, and examples of material and financial flows with 2-3 OUs are also covered.
The document outlines the basic structure and procedures for a procurement department, including sections for purchase requests, purchase orders, delivery, receiving, expenses, and payments. It also provides details on the desired functionality and reporting capabilities of a software system to manage the procurement process. Key requirements include linking all stages of procurement, maintaining records and logs of activities, and generating status reports at each stage. The target timeline to develop, test, and implement the customized procurement software is 60 days.
Summary accounts provide efficiencies for business processing by representing the sum of multiple detailed account balances. They allow for faster reporting and inquiry compared to reviewing each detailed account individually. A summary account template is used to generate multiple summary accounts based on the detail and parent segment values defined. Maintaining summary accounts involves tasks like adding or removing child accounts to update the rolled-up balances totaled in each summary account.
1) The document discusses tips for coping with intercompany invoicing in Oracle EBS, including reconciliation, scheduling concurrent programs daily, adding descriptions, monitoring for errors, and controlling the valuation cutoff date.
2) It recommends creating a Discoverer worksheet to reconcile intercompany payables and receivables invoices.
3) Scheduling the four required concurrent programs daily helps detect errors quicker than running them monthly.
Oracle EBS ERP user group presentation. Originally presented in June 2005 at the Connection Point 2005 conference in Dallas. Revised in 2007. Addresses EBS 11i but relevant to R12!
The document outlines the key steps in the order to cash cycle in an ERP system. It includes entering a sales order, booking the order, picking and shipping the order, invoicing, receiving payment, and transferring transactions to the general ledger. Details are provided on the underlying tables affected and navigation for each step.
Oracle Install Base is an application that tracks item instances throughout their lifecycle, from receipt to deployment to repair. It provides a centralized repository of information on item instances, including location, status, ownership, and configuration. Key features include item instance maintenance, relationships with parties and accounts, integration with other Oracle modules, and tracking of serialized and non-serialized items.
This document provides instructions for configuring a company code in SAP FICO. It begins with an introduction to SAP FI and relevant terminology. It then outlines the steps to define a company, create a company code, assign the company code to a company and chart of accounts, define relevant organizational structures and assign them to the company code, and configure settings for the currency, fiscal year, posting periods, document numbers, and more. The goal is to fully configure company code 1100 for the fictional company ABC Ltd located in the US.
Here are the key steps the Accrual Diagnostics script performs to help troubleshoot reconciliation issues:
1. It spools data from key accrual related tables like cst_reconciliation_build, cst_reconciliation_summary, cst_ap_po_reconciliation, cst_misc_reconciliation, gl_je_headers, gl_je_lines etc to an HTML file based on the input parameters provided.
2. It calculates the accrual balance in GL for Cost Management transactions by summing amounts from gl_je_lines for the given ledger, operating unit, accrual account and date range.
3. It calculates the accrual balance in subledger by summing amounts from c
The InterCompany Solution enables data consolidation and sharing of financial information between partner companies. It provides visibility across operations, improves control and collaboration. The solution integrates partner companies, replicates master data, automates intercompany transactions, and provides reports like consolidated balances. It supports tasks like allocations, payments, inventory sharing, and financial consolidation across multiple business entities.
This document discusses Oracle's Transaction Account Builder (TAB) which is used to derive accounting flexfields for subledger transactions in Oracle Fusion Applications. TAB replaces prior account generator solutions and provides a more flexible and configurable way to default transaction accounts. The key building blocks of TAB include Transaction Account Definitions, Transaction Account Types, Account Rules, Mapping Sets, and Sources. Seeded TAB setup and custom TAB setup options are also described.
This document discusses Oracle's Transaction Account Builder (TAB) which is used to derive accounting flexfields for subledger transactions in Oracle Fusion Applications. TAB replaces prior account generator solutions and provides a more flexible and configurable way to default transaction accounts. The key building blocks of TAB include Transaction Account Definitions, Transaction Account Types, Account Rules, Mapping Sets, and Sources. Seeded TAB setup and configuration options are also described to help customers understand how TAB can be used to meet their specific account defaulting requirements.
This document provides an overview of new and improved features in Oracle Financials Cloud Release 13, including enhanced integration with EPM Cloud, asset management improvements, expanded budgetary control functionality, and improved cash management tools. Key updates include more seamless data integration between Financials and EPM Cloud, automatic depreciation calculation for assets, expanded budget balance reporting, and ability to import non-standard bank statement formats.
The document provides an overview of the course contents for SAP FI/CO ECC 6.0 training. It includes topics such as enterprise structure settings, financial accounting, general ledger accounting, accounts payable, accounts receivable, bank accounting, controlling, cost center accounting, product costing configuration, and internal orders. It also lists various technical training courses offered by Futurepoint Tech such as Oracle, SAP, Microsoft, Java/J2EE and more.
Fi enhancement technique how-to-guide on the usage of business transaction ...Kranthi Kumar
This document provides a step-by-step guide on configuring and using Business Transaction Events (BTEs) in SAP FI to populate a custom value in an accounting document field. It describes BTEs and their differences from BADIs, the two types of BTE interfaces, and provides an example of using a process interface BTE to copy the text "Demo BTE" to the assignment field when a document is posted for a specific company code. The steps include identifying the BTE, creating a custom function module, assigning ABAP code, assigning the BTE, and testing the configuration.
Fi enhancement technique how-to-guide on the usage of business transaction ...Rajeev Kumar
This document provides a step-by-step guide on configuring and using Business Transaction Events (BTEs) in SAP FI to populate a custom value in an accounting document field. It describes BTEs and their differences from BADIs, the two types of BTE interfaces, and provides an example of using a process interface BTE to copy the text "Demo BTE" to the assignment field when a document is posted for a specific company code. The steps include identifying the BTE, creating and assigning a custom function module to the BTE, and testing the configuration.
This document provides instructions for reconciling postings between the financial accounting (FI) and cost accounting (CO) modules in SAP. It describes using transaction code KALC to generate reconciliation postings that transfer cross-company or cross-functional area postings made in CO to FI. The user runs KALC for a specified company code, period, and fiscal year to create reconciliation documents, which can then be viewed and modified using transaction code FB03.
The document discusses advanced features of authorization in SAP BW reporting. It provides an overview of authorization concepts in BW, the different types of authorization objects, and steps to create reporting authorizations. It also covers special topics like using variable-filled authorizations and the global variable customer exit to dynamically determine authorization values.
This document provides a step-by-step guide on using Business Transaction Events (BTE) as an enhancement technique in SAP's Financial Accounting module. BTEs allow customizing business processes by triggering ABAP code at certain transaction events. The guide describes BTEs and their differences from BADIs, the two types of BTE interfaces, how to find and configure BTEs using transaction codes and the function module approach, and provides an example of using a BTE to copy a custom value to a document line item field on posting.
This document outlines the process for automating intercompany and intracompany billing of training courses between departments within a company. It details how Oracle Projects will be used to generate accounting entries to charge tuition costs to the cost centers of trainees and credit revenue to the departments providing the training. Setup steps are provided for task and transaction setup, expenditure types, data file imports, intercompany and intracompany billing configurations, and reporting. The goal is to use Oracle's cross charge functionality to pass costs and share revenue across organizations for internal billing within and between different operating units in a systematic automated way.
This document provides an overview of the new Oracle Subledger Accounting (SLA) features in Oracle Release 12. SLA is a rules-based accounting engine that allows generating multiple accounting representations for a single business event. It provides a common data model and UI across subledgers to replace disparate 11i setups. SLA generates accounting for Oracle E-Business Suite modules and provides services like detailed accounting entries, subledger reporting and storage of subledger balances.
The document provides details of the configuration settings for the general ledger in SAP for Videocon International Limited (VIL). This includes defining ledgers, currencies, field status variants, fiscal year variants and assigning them to company codes. Parallel ledgers were created for periodic analysis. Field status variants were defined to make fields like cost center and profit center mandatory. Fiscal year variants were set up for the standard financial year as well as for weekly and 4-weekly cycles.
- The document discusses returns and service functions in SAP for media product sales and distribution, including returns, subsequent deliveries, quantity corrections, collection of unsolds, and goods transfers.
- It describes the Service Cockpit as the central interface for processing service operations. Operations can be grouped and configured according to company needs. Users are assigned authorizations for different operations.
- Service operations are defined and assigned to operation groups in Customizing. Users select an operation group in the Service Cockpit and then choose a service operation to process a request document.
Oracle E Business Suite is a software package from Oracle that provides enterprise resource planning functionality. It includes various product families like financials, procurement, customer relationship management, and supply chain management. Oracle is significantly larger than its main competitor SAP based on metrics like market capitalization and revenue. Oracle has advantages like strong vertical integration across its technology stack and an open architecture that makes customization easier for customers.
Created with limited permissions to assist the Standard
User.
Tally.NET User: Created to access data remotely using Tally.NET.
Tally.NET Auditor: Created to audit the data remotely using
Tally.NET.
Application Management and Controls
426
Figure 15.15 User Management
To assign a user to a site:
In the User Management screen
Select the required user and press Alt+S
The Assign User to Site screen appears
Select the required Site ID from the list of Sites
Press Enter to assign the user to the selected site
The user will now have access to the selected site.
Profile Management
Allows you to maintain information related to the Account/Site ID. The
This document provides instructions for configuring profitability analysis in SAP. It discusses defining characteristics and value fields, which are the key dimensions and values used to analyze profitability. Characteristics can be predefined, fixed, copied from reference tables, or custom defined. Instructions are provided for viewing existing characteristics, creating new user-defined characteristics like "Bill to party" and "Business field", and activating the new characteristics for use. The document outlines the overall profitability analysis configuration process and provides a guide to setting up the necessary master data and structures.
This document provides instructions for configuring profitability analysis in SAP. It discusses defining characteristics and value fields, which are the key dimensions and values used to analyze profitability. Characteristics can be predefined, fixed, copied from reference tables, or custom defined. Instructions are provided for viewing existing characteristics, creating new user-defined characteristics like "Bill to party" and "Business field", and activating the new characteristics for use. The document outlines the overall profitability analysis configuration process and provides a guide to setting up the necessary master data and structures.
This document provides instructions for configuring profitability analysis in SAP. It discusses defining characteristics and value fields, which are the key dimensions and values used to analyze profitability. Characteristics can be predefined, fixed, copied from reference tables, or custom defined. Instructions are provided for viewing existing characteristics, creating new user-defined characteristics like "Bill to party" and "Business field", and activating the new characteristics for use. The document outlines the overall profitability analysis configuration process and provides a guide to setting up the necessary master data and structures.
This document provides instructions for configuring profitability analysis in SAP. It discusses defining characteristics, value fields, operating concerns, and other key structures. Characteristics represent dimensions for analysis, like customer or product, while value fields are the metrics like sales or costs. An operating concern defines which characteristics and value fields to use for a specific analysis. The document walks through creating new characteristics and value fields, then defining an operating concern with ID 9100 that uses the Middle Eastern currency. It also assigns a controlling area and activates the configuration. This provides the basic structures for profitability analysis in SAP.
Concept of Control Centre
Tally.ERP 9 provides a powerful feature named Control Centre to its users, which works as an
interface between the user and Tally.ERP 9 installed at different sites, it enables the user to
centrally configure and administer Site/User belonging to an account.
1) Manage Licenses
2) Central Configuration
3) Manage Users
4) Manage Company Profile
5) Manage Accounts (using My Tally.NET Accounts)
6) Change Passwords
7) Activity History
8) Jobs and Recruitments (Coming Soon)
9) Shop
Similar to Apps i procurement setups [not br100] (20)
This presentation was provided by Rebecca Benner, Ph.D., of the American Society of Anesthesiologists, for the second session of NISO's 2024 Training Series "DEIA in the Scholarly Landscape." Session Two: 'Expanding Pathways to Publishing Careers,' was held June 13, 2024.
CapTechTalks Webinar Slides June 2024 Donovan Wright.pptxCapitolTechU
Slides from a Capitol Technology University webinar held June 20, 2024. The webinar featured Dr. Donovan Wright, presenting on the Department of Defense Digital Transformation.
This document provides an overview of wound healing, its functions, stages, mechanisms, factors affecting it, and complications.
A wound is a break in the integrity of the skin or tissues, which may be associated with disruption of the structure and function.
Healing is the body’s response to injury in an attempt to restore normal structure and functions.
Healing can occur in two ways: Regeneration and Repair
There are 4 phases of wound healing: hemostasis, inflammation, proliferation, and remodeling. This document also describes the mechanism of wound healing. Factors that affect healing include infection, uncontrolled diabetes, poor nutrition, age, anemia, the presence of foreign bodies, etc.
Complications of wound healing like infection, hyperpigmentation of scar, contractures, and keloid formation.
How to Download & Install Module From the Odoo App Store in Odoo 17Celine George
Custom modules offer the flexibility to extend Odoo's capabilities, address unique requirements, and optimize workflows to align seamlessly with your organization's processes. By leveraging custom modules, businesses can unlock greater efficiency, productivity, and innovation, empowering them to stay competitive in today's dynamic market landscape. In this tutorial, we'll guide you step by step on how to easily download and install modules from the Odoo App Store.
A Visual Guide to 1 Samuel | A Tale of Two HeartsSteve Thomason
These slides walk through the story of 1 Samuel. Samuel is the last judge of Israel. The people reject God and want a king. Saul is anointed as the first king, but he is not a good king. David, the shepherd boy is anointed and Saul is envious of him. David shows honor while Saul continues to self destruct.
A Free 200-Page eBook ~ Brain and Mind Exercise.pptxOH TEIK BIN
(A Free eBook comprising 3 Sets of Presentation of a selection of Puzzles, Brain Teasers and Thinking Problems to exercise both the mind and the Right and Left Brain. To help keep the mind and brain fit and healthy. Good for both the young and old alike.
Answers are given for all the puzzles and problems.)
With Metta,
Bro. Oh Teik Bin 🙏🤓🤔🥰
Gender and Mental Health - Counselling and Family Therapy Applications and In...PsychoTech Services
A proprietary approach developed by bringing together the best of learning theories from Psychology, design principles from the world of visualization, and pedagogical methods from over a decade of training experience, that enables you to: Learn better, faster!
Elevate Your Nonprofit's Online Presence_ A Guide to Effective SEO Strategies...TechSoup
Whether you're new to SEO or looking to refine your existing strategies, this webinar will provide you with actionable insights and practical tips to elevate your nonprofit's online presence.
Elevate Your Nonprofit's Online Presence_ A Guide to Effective SEO Strategies...
Apps i procurement setups [not br100]
1. 1/23/2018 Apps - iProcurement Setups [not BR100]
http://oracle.anilpassi.com/iprocurement-setups-not-br100.html 1/14
Home Technical Articles Training Articles Receive Email for New Articles Contributors Apps Book
MAIN MENU
Home
Technical Articles
Financials
iProcurement
Oracle Grants
Receivables
General Ledger
HR and Payroll
Oracle Workflows
Oracle Scripts
Installation
Fusion
Training Articles
Receive Email for New
Articles
Contributors
Apps Book
RELATED ITEMS
iProcurement
11.5.10 ReBuild
Charge Account
iProcurement
Interview Questions
In oracle
Load test Oracle
iProcurement - XML
Delivery
Scripts for
iProcurement - XML
Delivery load testing
Home Technical Articles Financials iProcurement
iProcurement
Setups
[not
BR100]
This website has now moved to http://apps2fusion.com
iProcurement Setups [not BR100] | Print |
E-
mail
Written by Anil Passi
Sunday, 26 November 2006
This is not a comprehensive BR100, but this article will give you an outline of the steps to implement Oracle iProcurement using Punchouts.
I will try to cover as many steps for full cycle iProcurement implementation using Punchouts. This is due to email requests & the comment requests that I received to
write something on iProcurement implementation.
What is a punchout?
In your iProcurement homepage, your suppliers can raise requisition to buy items like stationary. By punchout, we integrate iProcurement with Suppliers website. From
a users perspective below steps take place:-
1. Buyer logs into iProcurement Homepage
2. Buyer then sees various suppliers for which punchouts are enabled [depending on their security via realm & secured attributes]
3. Buyer clicks on a stationary supplier and browser displays supplier’s website.
4. Buyer selects the items on supplier website and adds them to his cart.
5. Buyer checks out the basket from Suppliers iStore [website]
6. The items selected are brought in as “Shopping Basket in iProcurement”
7. Requisition is created in iProcurement and sent for Approval [can be auto approved].
Typical iProcurement Steps [assuming no encumbrances setup]
a. Create Requisition
b. Approve Requisition
c. Auto-create & auto-approve Purchase Orders for approved requisitions.
d. Send PO XML to Supplier [if approver is setup as trading partner for XML PO]
e. Create receipts for goods [optional depending on setup]
-----Other non iProc steps----
f. Supplier sends Invoice electronically [posts to your XML Gateway electronically]
g. Invoice is Matched, Approved & Paid
Account Generation for iProcurement Requisition
Decide the rules for your account generation. For this you will need to customize “PO Requisition Account Generator”. For details of account generator implementation
visit link Account Generation using Workflow .
You may also visit Rebuilding Generated Account in iProcurement 11.5.10 using OA Framework
<-----Google Analytics Code Start----> <-----Google Analytics Code Close---->
55% OFF 30% OFF 53% OFF 40% OFF 81% OFF 88% OFF 83% OFF
2. 1/23/2018 Apps - iProcurement Setups [not BR100]
http://oracle.anilpassi.com/iprocurement-setups-not-br100.html 2/14
PO Create Documents Workflow
In iProc you create Requisitions, which then get converted to a Purchase Order using workflow “PO Create Documents”.
In this workflow, you must examine & modify the default values of following attributes[sample defaults values listed below]:-
Is Automatic Creation Allowed -- Y
Should PO be created from iProc requisition without user intervention.
Is Automatic Approval Allowed – Y
Should Contract be used to auto create Doc Y
Should non-catalog request be auto sourced from contract Y
Is Contract Required on Requisition Line N
There could be other attributes of your interest, but my implementation involved usage of contracts to create Purchase Orders. We have a blanket contract against
each iProc supplier. The values above for those attributes are merely indicative of one scenario.
PO Requisition Approval Workflow
Similarly for workflow “PO Requisition Approval”, assign a default value for attribute
Send PO Auto-creation to Background N
This means, as soon as a Requisition is approved, the creation of Purchase Order is kicked off [rather than wait for workflow background process]
Charge Account Flexfield Display-Prior to 11.5.10
If you are not on 11.5.10, then you would be using AK Developer.
Prior to 11.5.10, You will modify below AK regions to enable region items POR_CHARGE_ACCT_SEG1...X [depending upon the number of segments in your
accounting flexfield.]
POR_BILLING_CHARGE_ACCOUNT_R
POR_BILLING_MULT_CHARGE_AC_R
You will also set the profile options to relate to those regions for Accounting KFF
POR: Edit Account Regions: POR_BILLING_CHARGE_ACCOUNT_R
POR: Multiple Account Regions: POR_BILLING_MULT_CHARGE_AC_R
Charge Account Flexfield Display-On or after 11.5.10
You can use personalization to decide which segments are visible in Accounting Flexfield in iProc. Hence you no longer have to touch the “AK Developer”
Indicative Profile options for iProcurement [Assuming punchout implemented & no local hosting of catalogs]
Profile Site Note
Indicate Attachments Yes Show attachment icon
INV: Dynamic Precision Option -9999990
PO: Terms and Conditions File
Name No need for Punchouts
MO: Operating Unit Your operating Unit
3. 1/23/2018 Apps - iProcurement Setups [not BR100]
http://oracle.anilpassi.com/iprocurement-setups-not-br100.html 3/14
ICX: Days Needed By 4 --Change as you desire
ICX: Override Location Flag Yes
ICX: Override Requestor By All
ICX: Allow Funds Override No
POR: Amount Based Services Line Type Services
POR: Approved Pricing Only No
POR : CA Certificate File Name In ApacheTop/conf/ssl.crt/ca-bundle.crt Used for https punchout
POR: Emergency Requisitions Restrict
To Templates No
POR: Goods Line Type Goods
POR: Override Supplier P-card No
POR: Parallel Routing Allowed No
POR : Proxy Server Name Leave this blank
POR : Proxy Server Port Leave this blank
POR: Rate Based Services Line Type Service Quantity
POR: Sort By Relevance No
POR: System Approvers Are Mandatory Yes
POR: Use Sequence for Requisition
Numbering No
POR: Catalog Bulk Load Directory Ignore for punchout
POR: Catalog Bulk Load Host Default Ignore for punchout
POR: Default Currency Conversion Rate
Type Corporate Change as you wish
POR: Edit Accounts Regions POR_BILLING_CHARGE_ACCOUNT_R
POR: Enable Requisition Line
Customisation Yes
POR: Extract BPA/Quote Images Yes
POR: Help Path DBA For help customisations
POR: Hosted Images Directory Ignore for punchout
POR: Items Display Num
POR: Load Auto Category No
POR: Multiple Accounts Region POR_BILLING_MULT_CHARGE_AC_R Prior to 11.5.10
POR: One Time Location
4. 1/23/2018 Apps - iProcurement Setups [not BR100]
http://oracle.anilpassi.com/iprocurement-setups-not-br100.html 4/14
POR: Purge Commit Size 2500
POR:Purge Jobs Older Than (days) 30
POR: ROWS DISPLAY NUM
POR: Result Set Size 10
POR: SSP Version 5
POR: SSP4 Installed Yes
POR: Select Internal Requisition for
Confirm Receipt No
POR: Select Inventory Replenishment
Lines for Confirm Receipt No
POR:Allow Manual Selection of Source Yes
POR:Display Search Box and Browse
Categories No
POR: Load Auto Attrib No
POR: Load Auto Root No
ECE: Output File Path $XXICX_TOP/out
ECX: Log File Path /usr/tmp
ECX: OAG_LOGICALID www.anilpassi.com Your company domain
ECX: Server Time Zone GMT
ECX: System Administrator Email
Address anilpassi@gmail.com
ECX: XSLT File Path /usr/tmp
PO: Workflow Processing Mode Online
RCV: Processing Mode On-line
PO: In File Path No need for Punchouts
Define Approval Groups
Define Approval Groups [In Purchasing super User]
For example, assuming the below approval groups is assigned to Buyer named Anil Passi, this approval group means that Anil Passi can work on documents upto
$5000, within all accounting range of Company and Cost Centre [because 00 to ZZ covers everything].
Similarly you may also exclude a range. In this implementation example, I am assuming one Approval Group per person. You could have one to many relation too.
Once you have defined Approval Groups, you can use Approval Assignments screen to assign approval rules to Positions or Jobs defined in HRMS.
5. 1/23/2018 Apps - iProcurement Setups [not BR100]
http://oracle.anilpassi.com/iprocurement-setups-not-br100.html 5/14
Assign Approval Group
Effectively in this screen, you give ability to your buyers to Approve different document types like Requisitions, Blankets, Contracts within the restrictions as they were
defined in Approval Groups(prior step)
Define Document Types
The different attributes are self explanatory. Refer to Metalink for details.
The example in screenshot displays Document type for Purchase order, but the setup must be configured for other Document Types being used too.
Define Line Types
You can define the default information for a line type. Line types can identify transactions involving goods, services, outside processing, or any line type you define.
They allow you to distinguish between quantity-based and amount-based transactions.
Note: When you have set the Line Types up you can go back and complete these Profiles Options, as in screenshot below:
6. 1/23/2018 Apps - iProcurement Setups [not BR100]
http://oracle.anilpassi.com/iprocurement-setups-not-br100.html 6/14
Define Financial Options
In this screen, some of the fields are used for defaulting and some other fields for defining the behaviour of iProcurement/Purchasing. The setup here is done per
Operating Unit. Here within Accounting Tab, you specify accounts like Liability, Prepayment, Discount accounts.
Also Specify the following here
- Whether supplier numbering is manual or automatic.
- Default payment terms for [say 1month], and default payment type like Electronic.
-Specify FOB, Default inventory location and ship to and bill to, freight etc
-Encumbrance :- specify whether you use encumbrance and the type
- Default tax code
-VAT registration number of Operating unit
Define Purchasing Options
Again, this screen is defined per Operating unit, and it drives defaults & various controls in Purchasing & iProcurement.
Specify various controls like Min release amount , Price Break Type, Price Type(say fixed).
Define Accrual rules and Expense AP accrual account.
Define price tolerance rules, tax defaults & document type numbering.
Define Receiving Options
Various receipts related setup per Operating Unit, like Tolerance, Substitute Receipt Allowed.
Define transaction reasons
Your client specific setup, refer Metalink. Primarily this is an inventory function.
Define locations
The locations/Office Address where your suppliers will deliver goods and also send invoices.
Define Employees
Use this screen in PO if you do not have full HRMS Suite installed, in which case you would be using shared HR installed [cutdown version of HRMS to support
Purchasing].
Define Buyers
Define the people that can use Application to create and approve documents.
Category Search Display
Not needed for punchout implementations.
“XML Gateway” responsibility: Define Hubs
Use this form to define the hubs via which XML documents will be sent & received. If you are using Exchange for punching out, then your setup will look like below
XML Gateway Responsibility: Define Transactions
Here you indicate, the type of Documents you wish to exchange with your suppliers using XML
7. 1/23/2018 Apps - iProcurement Setups [not BR100]
http://oracle.anilpassi.com/iprocurement-setups-not-br100.html 7/14
XML Gateway Responsibility: Define Trading Partner
In this screen you will create a record for each Supplier with whom you wish to exchange XML Documents electronically.
For example, if you wish to send XML Purchase Orders to “Go 4 Gold Management Ltd”, then you will create an entry similar to below. The connection can either be
direct or via exchange server.
You will also capture trading party’s DUNS numbers in this screen.
During the implementations you usually use testexchange.oracle.com.
The DUNS number for the supplier also needs to be entered in the EDI Location field against supplier site in Vendor Definition Screen.
The DUNS number for your implementation client needs to be entered in the EDI Location field on Other Details section of Location form for Client location[lets say
your client for which iProc is being implemented is “XX Machine Inc”].
Process PO 007 is an OAG standard that dictates the structure of XML document which your supplier will receive.
For those that do not know, PO007 is nothing but an Approved Purchase Order sent to the supplier. Its format is XML.
To see its structure, on your middle tier, review the dtd file as listed below. $PO_TOP/xml/oag71/003_process_po_007.dtd
Oracle Apps uses XML Gateway to generate the PO-007 file.
How is this PO 007 file generated?
FTP the xgm file to you PC from $PO_TOP/patch/115/xml/US/process_po_007.xgm
Open that file in XML Gateway Message designer
You will notice that message designer reads information from views like ITG_PO_HEADER_ARCH_V [Prior to 11.5.10 it was PO_ECX_HEADER_ARCH_V]
iProcurement uses the XML Gateway engine in conjunction with PO-007 message definition to generate PO007 XML document.
Configure your Exchange setup
Given that in this setup, we will use Oracle’s exchange server to send PO Documents to supplier, hence we need to enable this Document Type[PO 007] in
exchange[for the company implementing iProc]
Logon to exchange.oracle.com or the testexchange
Navigate to Application Setup tab/ Transaction Delivery
Select the document type PROCESS_PO_007 and edit
Set the communication method and click Apply
Your Supplier will have to register on Oracle Exchange Server too.
To begin with, during implementation, each supplier must register themselves on http://testexchange.oracle.com
Your supplier does the below:-
Clicks on Registration on testexchange, and selects the option to register as an affiliate of your client.
Say your client is “XX Machine Inc”, hence your supplier will search & select “XX Machine Inc”. Supplier will be prompted to enter further details.
Following this, your client will have to approve the request for Supplier’s registration.
Supplier Enables PROCESS_PO_007 for themselves on the Exchange
8. 1/23/2018 Apps - iProcurement Setups [not BR100]
http://oracle.anilpassi.com/iprocurement-setups-not-br100.html 8/14
The sequence of flow for PO 007 in this case is…
XX Machine Inc-->PO 007-->Exchange server-->Supplier
Hence Supplier needs to enable “PO 007” for themselves on the exchange server
For this your Supplier does the below steps:-
Login to the testexchange (i.e. exchange.oracle.com after testing during goLive).
Clicks on Transaction Delivery under Company Administration
Selects Sales Order Outbound (PROCESS_PO_007) [going out from Exchange, becoming sales order in Suppliers System]
Under transaction type they select delivery method HTTPS etc
They specify their URL on server which where exchange will post the PO 007 XML doc.... https://inboundpo...
They also need to specify other connection details to their server like port number, userid password etc.
Exchange server will use those credentials to connect and post the XML PO Document[PO 007]
Note: Oracle Exchange supports various protocols like http,https,smtp . The supplier selects a protocol based on the protocols their server supports.
Supplier Enables themselves for PunchOut on the Exchange Server
Oracle supports both cXML ad XML punchouts. Hence the supplier must support one of these two options.
Supplier does the following steps to enable punchouts:-
Logs in to TestExchange Server or the Exchange Server
Clicks on “setup punchout”
Enters their punchout URL, userid password for their iStore.
Select XML or cXML and then clicks on APPLY.
Supplier can then test whether their punchout setup works by punching out to their iStore from testexchange/exchange.
”XX Machine Inc” reviews suppliers Punchout
Client “XX Machine Inc” logs into testexchange or exchange server, and navigates to “Control Punchout Access” and accepts Suppliers Punchout definition.
”XX Machine Inc” makes Oracle EBS aware of the Punchout setup
It is possible that with some suppliers, you would like to Punchout to their iStores via exchange, and for the other suppliers you may like to punchout directly to their
iStore.
I am detailing both the scenario’s below.
Scenario 1 Use the Supplier punchout definition from Exchange
Navigate to Internet iProcurement Catalog Administrator.
As in picture above, by downloading[click on download], you will bring into Oracle, all the Punchout Suppliers that are enabled for your business in exchange.
Scenario 2 Create Supplier punchout definition directly in Oracle Apps eCatalog Mgr
If you were not to be using Exchange, then you will have to create the Punchout definition from scratch in Oracle Apps itself.
For this, click on “Manage Content” in responsibility “Internet iProcurement Catalog Administrator”
Click on create catalog
Select Punchout catalog and click on continue
9. 1/23/2018 Apps - iProcurement Setups [not BR100]
http://oracle.anilpassi.com/iprocurement-setups-not-br100.html 9/14
As in picture above, we select Supplier and Direct Punchout.
Given that you are creating Punchout definition of the supplier from scratch straight in Oracle Apps, you then need to enter information in below fields like Punchout
URL, Encoding Method, password etc.
NOTE: As you may have noticed, effectively we are trying to create a punchout definition in Oracle Apps…either by downloading the Supplier’s punchout definition from
exchange or by directly creating the Punchout definition in Oracle Apps.
Display the punchout site on iProcurement Homepage
This will be the last step. You need to define a store that is attached to the punchout catalog definition.
For this Click on create store in responsibility “Internet iProcurement Catalog Administrator”
10. 1/23/2018 Apps - iProcurement Setups [not BR100]
http://oracle.anilpassi.com/iprocurement-setups-not-br100.html 10/14
This finishes the punch-out setup with your Supplier.
Further notes:-
1. Your suppliers punchout basket may contain items with UOMs that are not defined in Oracle Apps inventory module. In this case, you must navigate to responsibility
“eCommerce Gateway” and define those mappings using menu “Code Conversion Values”
2. As per the OAG format, the item category used in punchout baskets is 8 digit UNSPSC code. Effectively UNSPSC code is a global code for item categories.
However in Oracle EBS, we implement Item Categories using Key FlexField for Item Categories. For a 3 segment Item category flexfield in inventory, your item
category may look like AA.BB.CC. This value of AA.BB.CC must be mapped with the UNSPSC codes that your suppliers will be sending for their item categories. This
definition is mapped in the same screen under “eCommerce Gateway”.
Comments (30)
Subscribe to this comment's feed
...
written by Janel , January 08, 2007
Extremely better than the Oracle documentation!
...
written by Ramesh, India , January 09, 2007
Hi Anil,
This is excellent documnet... Hat off to you for your efforts.
Thx,
Ramesh
...
written by Siva , February 23, 2007
Hi Anil,
the document is very good and useful.
...
written by Anil Passi , February 24, 2007
Thanks Siva !
...
written by Anil Passi , February 27, 2007
Hi Santosh
Thanks for your kind words.
Not sure where you are based? I occassionally meetup with my ex-colleagues that are Oracle Consultants working on different projects. If you are based
around London, will give you a shout.
Cheers,
anil
11. 1/23/2018 Apps - iProcurement Setups [not BR100]
http://oracle.anilpassi.com/iprocurement-setups-not-br100.html 11/14
...
written by Santosh Desai , February 27, 2007
Hi Anil,
Excellent article , I had been looking for such a detailed explanation for a long time. My interests into Oracle all started with i procurement training to superuser
and then moving on to understand other Oralce modules.
I have gone through the article today more than 3 times and everytime i read it , i feel im catching important features one at a time, which is quite obvious for a
beginner like me.
Hope to meet you some time in the future for you excellent article:-)
Santosh Desai
...
written by Praveen Challa , March 05, 2007
Awesome Anil. Nice article for iprocurement implementation. I came across this site while browsing on google. The content and the effort which has
gone into making this site really amazes me. Great Job!!! I recommend this site to all my collegues.
...
written by Prativa , March 06, 2007
Hi Anil, We have Purchasing setup, I have to impliment i-procurement.I found this as a very good document. Could you please provide more step by
step instructions. We need to have both catalog and non catalogs.
Thanks and regards,
Prativa.
...
written by Jabs , March 20, 2007
Hi anil, I am a newbee to oracle apps and i have joined an organisation recently and in the project assigned i have to enable iprocurement module in
the application where financials and purchasing is already running? can u give me the steps how can i do that? and do i have to apply any patches for that? i
will be very grateful to you anil.
thanks and regards
jabs
...
written by Anurag Bhatt , April 30, 2007
Hi!Anil
I am trying to play around with Oracle Apps Vision Instance. I defined a new business Group which is an Operating Unit also and new responsibility.Define
HR:Security level, Hr:Business Group etc. Under Purchasing responsibility, I am not able to define Purchasing Parameters as It is not allowing update. Under
Document Type window, I see only Quotation & RFQ and not PO etc.
Please tell me what else I need to check??
...
written by Sharon , June 01, 2007
hi Anil,
If you can pls help me out on Advanced Pricing. I want to know if it is possible to invoice the customer with the List price and whatever India Localized taxes
are applied are not added up along with the List price. The List price is not the Unit Price but the Selling Price in Order Management. Also i want to enforce
price list but discounts should be applicable but this is not working even after setting the profile option OM: Discouting Privelege to Unlimited. Your feedback
will be a big help to me
Thanks
...
written by Anil Passi , June 15, 2007
Hi Avinash
Did you load the XML Message Map into the database ? You need to do that step for the new message map to take effect.
Thanks,
Anil Passi
...
written by Aravind , June 15, 2007
Hi Anil,
I am trying to customize the standard PROCESS PO 007 xgm file by adding some more fields to it.I am able to load the map to my custom top but still this is
not reflected in the supplier that I set up to use this xgm file rather it uses the standard xgm file.Should I ftp the custom xgm to PO_TOP rather and try to
reference it..?
Kindly let me know of any possible solutions..
Thanks,
Aravind
12. 1/23/2018 Apps - iProcurement Setups [not BR100]
http://oracle.anilpassi.com/iprocurement-setups-not-br100.html 12/14
...
written by mohd arif ali , July 07, 2007
Hi Anil,
This is the first time I am reading your articles. U had done really a great job.
I may be knowing that can I download ur presentations like audio/video ...
Regards
ARIF
...
written by Anil Passi , July 07, 2007
Hi Arif,
Thanks for your kind words.
I am afraid , at the moment, the only way to watch these are online
Thanks,
Anil
...
written by sarath kumar , July 13, 2007
Hi,
Pls forward me the set up steps and set up document ot implementing isupplier module
thanks in advance,
sharath
...
written by jaihind reddy , July 31, 2007
Hi Anil
Really nice doc. My client is implementing punchout with 2 suppliers. Client is asking how to punchout the inventory items. i.e. when we submit the shopping
cart in supplier site it directly comes to iPro shopping cart and with e-commerce gateway category mapping but where supplier and inventory item is tied. Is it a
standard functionality to procure inventory item through punchout.
Thanks
jaihind
...
written by Anil Passi , July 31, 2007
Hi Jaihind
Been long time now since I worked on iProc.
I think When you punchout, the Supplier Item Item is brought into iProcurement.
At the time of PO Creation, if that Supplier Item Number had ever been associated in invetory_item_id in PO_LINES, then the same inventory item will be
defaulted for new line.
So try this
Step 1. Create a PO with Supplier Item Number and a specific Inventory Item
OR
Step 1. Create a relation between supplier item number and inventory_item_id
--Approve PO
Step 2. Create an iProc requisition for the same Supplier and same Suplier item number
Create a PO for that req
Also check for concurrent program "Catalog Data Extract Classifications and Items" and tables icx_por_items,
ICX_CAT_ITEMS_B and ICX_CAT_ITEMS_TLP in documentation
Thanks,
Anil Passi
...
written by Aamer , August 22, 2007
Anil,
Very useful information, I was looking for what needs to be done for opening firewall (if oracle exchange is used) - we are intranet based right now,
this is the first i-* product dealing with internet. Any thing we need to do for https://
...
written by Anil Passi , August 23, 2007
Aamer
Your network team should open the firewall port.
If you are punching out via exchange, then simply open the firewal for exchange.oracle.com
13. 1/23/2018 Apps - iProcurement Setups [not BR100]
http://oracle.anilpassi.com/iprocurement-setups-not-br100.html 13/14
However, in case of direct punchouts, you will have to open firewall ports for machines of each of your punchout suppliers
Thanks,
Anil Passi
Help
written by Pradeep Konduru , October 23, 2007
Anil
Client wants to implement iP for non inventory items (expense items). These items are not in their INV at all. Currently they create POs for these items by just
filling in the description field in the PO Line. How to create these items then? By using UNSPSC? Please help
Thanks Angle
written by Harish Kumar Sharma , October 27, 2007
Hi Anil,
Excellent. Can I receive the setups and other Ora Apps info at my above email,please sir.
Harish
i procurement
written by chinkanlu , November 02, 2007
Hi Anil,
i have a requirement on iprocurement please see the details and suggest me the procedure to follow.
a)Update iprocurement tables from EBS extract (All item types)
b)Update iprocurement category Mapping & catalogue Content
i am summaririzing the requirement , customer is changing the category structure (from 5 segments to 4 segments) due to which there will be change in
categorys and other related stuff.
so at present they want to update the itemtypes in R12 based on the EBS(11i), so how to go ahead is there any seperate concurrent program or directly we
need to update the base tables(if so) please mention the tables which have to be updated, similarly i need the explanation for question b).
it would be of great help if you can reply me as soon as possible,
...
written by Deva , November 06, 2007
Hi Anil,
The detailed I-proc setup is very useful for a beginner like me and I am in need of a sample i-Proc BR100 Document for reference.
I would greatly appreciate if you can share them.
Thanks
Deva
Changes made to cXML_OrderRequest.xgm not getting reflected
written by MSAMTD , December 07, 2007
Hi:
If anybody can help me in figuring out the below issue regarding XML Gateway Message Designer, I'd greatly appreciate it.
Trying to add a addressID in Linelevel of PO XML (cXML_OrderRequest.xgm)
1) copied the Map from the server
2) Opened the Map using Latest Version of Gateway Designer. (2.6.3.0.0)
3) Mapped the AddressID at the linelevel
4) Uploaded the Map back to Server by physically placing the file and also through LoadMap command.
5) Verified by making sure that the changes in the map are saved by downloading it and also verifying the timestamp in ECX_MAPPINGS table.
6) Restarted the WF Agent Listener.
7) Went to Autocreate the PO and looked at XML in Workflow / OSN but cannot see the modifications.
Can anybody let me know if I'm missing any steps here.
UOM error
written by vijayku , January 09, 2008
Hi Anil,
I was using Model4 , XML via Oracle Exchange for punchout. I m getting UOM not configured for purchasing error upon return of shopping cart. Are you aware
of how to fix this? My data mapping was done right.
...
written by Anil Passi , January 19, 2008
14. 1/23/2018 Apps - iProcurement Setups [not BR100]
http://oracle.anilpassi.com/iprocurement-setups-not-br100.html 14/14
Hi Vijay
You need to map UNSPSC code of UOM received in basket to your Inventory UOM.
This can be done using XML Gateway responsibility.
Thanks,
Anil Passi
IProcurement technical questions
written by tania , January 25, 2008
Hi Anil,
I regularly watch ur site. The way u present ur articles is really nice. I am new to OA Framework.
My question is what type of extensions or customizations we can do with requisitions in Iproc.
Please help me.
Thanks,
Tania.
Amazing article
written by venkatakrishnan , March 07, 2008
Absolutely amazing. Very clear in presentation.
Thanks
Venkat
Amazing Article......
written by Vijayakumar Kasi , March 19, 2008
Anil,
Amazing Article.... A Job Well Done.
Regards,
Kasi, Vijayakumar
You must be logged in to a comment. Please register if you do not have an account yet.
Home Contact Us
COPYRIGHT : This work is licensed under a Creative Commons Attribution-NonCommercial 2.5 License. The content on this site is copyright protected.
Subscribe in NewsGator Online