Oracle Cloud offers a broad portfolio of software as a service applications, platform as a service, and social capabilities, all on a subscription basis. Oracle Cloud delivers instant value and productivity for end users, administrators, and developers alike through functionally rich, integrated, secure, enterprise cloud services.
 Get a Free Magzine ...Profit:The Executive's Guide to Oracle Applications

Subscribe to the OracleAppsHub to receive notifications when there are new posts:

 get RSS feed
 Oracle Fusion Applications (OFA) is a portfolio of next generation suite of software applications from Oracle Corporation. It is distributed across various product families; including financial management, human capital management, customer relationship management, supply chain management, procurement, governance, and project portfolio management
 Get a Free Magzine ...Profit:The Executive's Guide to Oracle Applications

Golden Tax Adaptor for Mainland China : Invoices for VAT in China

Posted on January 24th, 2013 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Do you know, laws in the People’s Republic of China require the use of a government certified tax software called ‘Golden Tax’ for VAT calculation, statutory tax reporting and generating and printing VAT invoices.

Golden Tax is an integrated nationwide value-added tax (VAT) monitoring system in China.

Golden Tax Adaptor enables Oracle’s customers in China to interface their invoices, credit memos and debit memos from Oracle Receivables/Oracle Fusion Receivables to the Aisino Golden tax software in order to calculate VAT, generate and print VAT invoices and report tax to the Chinese Tax authorities.

The user can use discrepancy and mapping reports to audit and reconcile the discrepancies in data between Receivables invoices and Aisino generated VAT invoices.

In China, VAT invoices are generated only for VAT, and not other types of tax that may appear on receivables transaction lines. Tax types identify the applicable VAT tax for each line of a VAT invoice for a given legal reporting unit.

You can use these tax types or create your own, according to your tax requirements. Different tax types are:

  • VAT: VAT for goods or services
  • VAT-GOODS: VAT for goods only
  • VAT-SERVICES: VAT for services only

This support for additional VAT invoice types - Special VAT invoices, common VAT invoices and special VAT Invoices of Waste and Outdated Materials .

The key steps in the Golden Tax process are:

  • Create or import transactions in Receivables.
  • Transfer receivables transactions to the Golden Tax Adaptor as Golden Tax transactions.
  • Modify the Golden Tax transactions to conform to the requirements of VAT invoices for China.
  • Generate a flat file of VAT invoice data for import into the Aisino Golden Tax System.

After the Aisino Golden Tax System generates VAT invoices from the Golden Tax Adaptor data:

  • Import VAT invoice data from the Aisino Golden Tax System.
  • Review and compare the imported VAT invoice data with the flat file exported to the Aisino Golden Tax System.
  • Correct any discrepancies between the two data files.

Further Reading. Goldan Tax

Posted in Localizations, Oracle E-Business Tax | No Comments »

Understanding “Dunning Plans” in Advanced Collections

Posted on January 20th, 2013 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Dunning Plans in Advanced Collections replaced the Receivables Dunning Letter processing in Release 11i. Dunning Plans are relatively “simpler” way of implementing Advanced Collections.

If Dunning letters are used as part of the standard collection process, the Dunning Plans in Release 12 helps achieve the same result but adds more functionality by combining the score calculated using the scoring engine to pick the correct Dunning letter format.This implementation option also lets users create call back tasks in addition to sending the Dunning letters.

Dunning Letters in Release 12 are defined in the BI Publisher.

In 12 the word “delinquency” is new to most 11i users and this means an overdue item. .

dgreybarrowThere are 2 types of Dunning Plans that you may setup.

1. Days Overdue Method - based on the aging buckets you are using to collect your payments

You will setup the Dunning Plan and include Aging Bucket lines for each Aging Bucket Line you have assigned in your Aging Bucket.
For Example - if you are using a 7 Bucket Aging, then the Dunning Plan will have at least 6 Aging Bucket Lines.

2. Staged Method - based on the date of the last letter sent or Dunning Stage

When a Delinquency is created, the Staged Dunning Level is null. Once you run the Staged Dunning and that Delinquency is included in a letter, the Staged Dunning Level count is incremented. You may see this on the Transaction Tab if you bring up the Transaction and show the Staged Dunning Level count.

dgreybarrow Dunning plans limitations

  • Delinquency scoring engine and dunning plan scoring engine is one and same
  • Scoring engine values are used both for delinquency status determination and aging bucket line determination so it can be tricky to obtain desired functionality
  • A transaction can only be scored using one scoring engine – if you add a new scoring engine only new transactions will be scored with this
  • AR Aging Buckets are used for days overdue determination only – unless you customise scoring components
  • Only one aging bucket can be used per dunning plan

dgreybarrowRunning Concurrent Programs for Dunning Plans

You must run the following concurrent programs in Oracle Advanced Collections to execute dunning plans:

  • IEX: Promise Reconciliation: This program updates the open promise information in Advanced Collections with payments received in Oracle Receivables to determine outstanding items.
  • IEX: Territory Assignment: This program assigns collectors to customers who are using Oracle Territory Manager. You can assign collectors at the customer, account, or bill-to level. This program retrieves a list of available collectors for each territory and assigns the first collector on the list. If you are using Territory Assignment, it is advisable to run this concurrent program first whenever you run the IEX: Scoring Engine Harness.
  • IEX: Scoring Engine Harness: You can select up to five scoring engines to run at the same time. The scoring harness assigns a value to an object such as a customer, account, or bill to location. Another score determines whether transactions are delinquent, pre-delinquent, or current.
  • IEX: Send Dunnings for delinquent customers: This program sends the results of the scoring engine harness to Oracle XML Publisher to send out dunning correspondence.
  • IEX: Create Dunning And Broken Promise Call Backs: If you have dunning callbacks as part of your dunning plan, run this program to create callback work items to a collector's task list in the Collector's Work Queue.

dgreybarrow Dunning in Correspondence History

When you select the Correspondence history type on the History tab, Oracle Advanced Collections provides a review of all dunning events initiated by the dunning process. You can view this information by customer, account, bill to location, or delinquency data level. Summary level information on all dunning events are also displayed in the All history.

dgreybarrowWant to Preview the Dunning Letters Before They are Sent to Customers with Dunning Plans

Collections supports preview and selective dunning with "IEX: Send dunning for Delinquent customers" concurrent program ONLY.

There is no Preview/Draft functionality for Strategies when submitting the IEX: Bulk XML Delivery Manager manually.

Added the following parameters to "IEX: Send Dunnings for delinquent customers" concurrent program.
a. Preliminary : possible values are Yes/No
b. Process errors only : possible values are Yes/No
c. No of workers :

Following parameters can be used to process only particular/set of customer/account/bill to locations.
d. Customer name low :
e. Customer name high :
f. Account number low :
g. Account number high :
h. Billto location low :
i. Billto location high :

arrow"IEX: Send Dunnings for delinquent customers" concurrent program always spawns the "Oracle Collections Delivery XML Process (IEX: Bulk XML Delivery Manager)" to process/send the dunning letters.

dgreybarrow Migrating 11i Dunning Letter Sets to R12 Staged Dunning

  • Concurrent program "IEX: Dunning Letter Sets Migration for Staged Dunning"
  • and a profile option called 'IEX: AR Dunning to IEX Dunning Migrated' in 12.1.3

will allow you to migrate the dunning letter sets from 11i AR Dunning to R12 Advanced Collections.

dgreybarrow Know five most common Dunning Plan Issues

  • Missing Corresponding Template - you are missing a template name on an aging line or stage line in the Dunning Plan setup. See Note: 466328.1
  • AgingBucketLineId NotFound - you are missing an aging line in your Dunning Plan setup or you have not covered the range from 1-100 for each Aging line.
  • The send dunning flag in customer profile is set to no - The Send Dunning flag must be checked on the Customer Account or Bill To depending on your Business Level.
  • Missing Score - You have not run the IEX: Scoring Engine Harness for the scoring engine that you linked in the Dunning Plan. That Dunning Plan uses the scores created by the linked engine to send the Dunning Letters.
  • Required min Dunning amount in customer profile - You must set the minimum Dunning on the Account or Bill To depending on the Business Level.

Next Post will more focus on Scoring .

Posted in Advance Collection | No Comments »

Oracle Product Overview – VII : ( Data Quality)

Posted on January 19th, 2013 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Data quality covers all processes and technologies to make sure all relevant information is complete and correct. For this, it is necessary to have a range of
controls from the point of data capture all the way to signing off the annual report.

Data quality management needs to be:

  • Preventive, having processes and systems that do not allow any data capture mistakes;
  • Detective, to check if this is the case, as one may not have control over all necessary data; and
  • Corrective, to make sure problems with data quality are solved.

Typically Requirement for any data quality software consist of these core functional requirements as:

  • Data profiling: assessing the data to understand its overall degree of accuracy
  • Data standardization : utilizing a business rules engine to ensure that data conforms to pre-defined quality rules
  • Generalized "cleansing": The modification of data values to meet domain restrictions, integrity constraints or other business rules that define when the quality of data is sufficient for an organization.
  • Matching and Linking – Comparing data to align similar but slightly different records
  • Monitoring: Deploying controls to ensure that data continues to conform to business rules that define data quality for the organization.
  • Enrichment: Enhancing the value of internally held data by appending related attributes from external sources

1 Oracle Enterprise Data Quality

Helps organizations achieve maximum value from their business-critical applications by delivering fit-for-purpose data.

Enable individuals and collaborative teams to quickly and easily identify and resolve any problems in underlying data.

With Oracle Enterprise Data Quality products, customers can identify new opportunities, improve operational efficiency, and more effectively comply with industry or governmental regulation.

More details can be obtained from datasheet.

1 Oracle Hyperion Data Relationship Management enables your organization to proactively manage changes in master data across operational, analytical and enterprise performance management silos. Business users may make changes in their departmental perspectives while ensuring conformance to enterprise standards.

Whether processing financial information such as cost centers, accounts, and legal entities or analytical information such as members, dimensions, hierarchies, and their attributes, Oracle Hyperion Data Relationship Management delivers timely, accurate and consistent master data to drive ongoing operational
execution, business intelligence and performance management.

Posted in Tool | No Comments »

Oracle Product Overview -VI : ( Knowledge Management)

Posted on January 17th, 2013 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Oracle's products for knowledge management help users find useful knowledge contained in corporate information stores.

1 Oracle Knowledge for Contact Center

Oracle knowledge management capabilities are fully integrated with Siebel Contact Center for a one-stop solution that helps service organizations realize unprecedented levels of agent efficiency, accuracy, and consistency in every service interaction.

One-click intelligence built into the Siebel Contact Center interface offers agents immediate access to a full range of intent-based knowledge management capabilities

Data sheet for further reading.

1Oracle Knowledge for Web Self Service

Builds tools around social networking to enable customers and your organization to glean the best content from the user community on an ongoing basis.

Transform your customers’ self-service experience—increase online resolution rates, reduce calls into the contact center, and substantially reduce support costs

Oracle Knowledge for Web Self Service enables your organization to

  • Empower consumers to comment on the self-service experience in online surveys that capture content ratings and feedback
  • Connect customers with a wide range of opinions and ideas within interactive peer to peer discussion forums
  • Leverage community conversations in the knowledge
  • creation workflow to efficiently turn social discussions into reusable answers
  • Offer subscription services to deliver smart feeds of content that keep customers apprised of vital information
  • Tap into the next generation of service and leverage the power to build social reputations and new communities of experts

Data sheet for further reading.

Posted in Tool | No Comments »

Oracle Product Overview -V : ( Data Security)

Posted on January 17th, 2013 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Oracle Advance Security

Helps customers address regulatory compliance requirements by protecting sensitive data on the network, on storage media and within the database from unauthorized disclosure.

Transparent Data Encryption provides the industry’s most advanced database encryption solution for protecting sensitive information without requiring changes to applications

Oracle Information Rights Management

A complete and effective information security solution must manage who has access to your data, regardless of where it is ultimately copied or forwarded.

Enables your business by extending security, control, and tracking beyond the organization’s network to remote user desktops, laptops, mobile wireless devices, and more.

Posted in Tool | No Comments »

Guide to Punch Out : When To Use Punchout

Posted on January 17th, 2013 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

This is very common question , you might think and try to under stand , when to use PunchOut ?

Punchout is particularly useful for products that are configurable or include highly variable or dynamic items and pricing. These products are difficult and costly to maintain in a buyer hosted catalog.

In last post , you have observed various model of punchout models thats provide you with the flexibility to pick the model that best works for you.

  • Model 1: Punchout from Oracle iProcurement to Oracle Exchange ( XML)
  • Model 2a: Punchout from Oracle iProcurement Directly to Supplier-Hosted Catalog (XML)
  • Model 2b: Punchout from Oracle iProcurement Directly to Supplier-Hosted Catalog(cXML)
  • Model 3a : Punchout from Oracle Exchange to Supplier-Hosted Catalog (XML)
  • Model 3b: Punchout from Oracle Exchange to Supplier-Hosted Catalog (cXML)
  • Model 4: Punchout from Oracle iProcurement to Supplier-Hosted Catalog via Oracle Exchange (XML)
  • Model 5: Punchout from Oracle iProcurement to Supplier-Hosted Catalog via Oracle Exchange (cXML)

OPTING YOUR NEED: SELECTING A PUNCHOUT MODEL

iProcurement and Exchange support various punchout models.

It is important for both buyers and suppliers to decide on the model they want to use before implementing the punchout. The following table compares the punchout models:

Model /Options Buyer Benefits Suppliers Benefits

Model 1:

Punchout from Oracle iProcurement to
Oracle Exchange (XML)

  • iProcurement requesters have access to all supplier catalogs defined on Exchange.
  • They can comparison shop among suppliers on Exchange. They
    have a similar user interface experience as in iProcurement.
  • Suppliers load their catalog items once on Exchange and reach many iProcurement customers in addition to the buyers already registered on Exchange.
  • The Exchange catalog supports features such as buyer pricing , price breaks,and price effective dates

Model 2 (a), 2(b)

Punchout from Oracle iProcurement
Directly to Supplier-Hosted Catalog
(XML)/(cXML)

  • This model offers a unique,point-to-point solution between the
    buyer and supplier
  • Supplier closely manages the content.
  • Supplier can control access by allowing only certain buyers to access the site.

Model 3 (a) , 3(b)

Punchout from Oracle Exchange to
Supplier-Hosted Catalog (XML or cXML)

  • Buyers have access to a centralized collection of punchouts simply by registering with Exchange.
  • Purchasing Managers on Exchange can control buyer access to specificpunchouts using the Control Punchout Access page.
  • Suppliers only have to define their punchouts on Exchange once, rather than configuring punchout separately for each iProcurement customer.
  • Suppliers can control the visibility of their punchout definitions by publishing or unpublishing the punchout on Exchange.

Models 4 and 5


Punchout from Oracle iProcurement to
Supplier-Hosted Catalog via Oracle Exchange (XML or cXML)

  • iProcurement requesters have access to a centralized collection of punchouts.
  • iProcurement administrator does not have to configure a punchout for each supplier, but can just download the supplier’s punchout definition from Exchange.
  • The punchout’s passing via Exchange is transparent to the requester.
    Exchange translates cXML to XML seamlessly.
  • Suppliers only have to define their punchouts on Exchange once, rather than configuring punchout separately for each iProcurement customer.
  • Suppliers can control the visibility of their punchout definitions by publishing or unpublishing the punchout on Exchange.
  • Suppliers already maintaining cXML catalogs can continue to use those

The figure below shows the process for deciding which model to use.

Opting for PuncxhOut Model

For all models, make sure of the following prerequisites:

  • Make sure the supplier supports the punchout.
  • If the supplier’s site is secure, verify your access to secure sites.

Posted in Oracle Purchasing | No Comments »

Oracle Product Overview – IV : ( Data Discovery)

Posted on January 16th, 2013 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Oracle Endeca Information Discovery

An enterprise data discovery platform for advanced, yet intuitive, exploration and analysis of complex and varied data.

Information is loaded from disparate source systems and stored in a faceted data model that dynamically supports changing data.

This integrated and enriched data is made available for search, discovery and analysis via interactive and configurable applications.

Enables an iterative “model-as-you-go” approach that simultaneously frees IT from the burdens of traditional data modeling and supports the broad exploration and analysis needs of business users

Posted in Tool | No Comments »

Guide to Punch Out : XML, CIF or cXML..

Posted on January 16th, 2013 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

What's XML?

An eXtensible Markup Language (XML) file is a general purpose markup language file with a set of rules for encoding documents in machine-readable form.

XML is a subset of Standard Generalized Markup Language (SGML).

The primary purpose of XML is to facilitate the sharing of data across different systems.

The upload process will parse and process the XML file to load agreement lines and its associated attributes provided that the XML file conform to the XML DTD.

What's CIF or cXML?

A Catalog Interchange Format (CIF) file is a comma-separated text file.

A commerce eXtensible Markup Language (cXML) .xml file is based on the XML language.

Put simply, cXML stands for 'Commercial Extensible Mark-up Language' and it is basically a solution that allows different systems to 'talk' to eachother in the simplest and most efficient way possible. It is simply the connection type being used between the e-procurement system and the suppliers website.

Oracle is currently only support cXML up to version 1.1.007

Posted in Oracle Purchasing | No Comments »

Punchout from iProcurement to Supplier

Posted on January 16th, 2013 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

WHAT IS PUNCHOUT (also known as Supplier PunchOut)

Punchout provides the ability to link out from a procurement application (iproc ) to a vendor's eCommerce site to shop, place items into a cart, and return that cart to their own procurement application to continue purchasing within their designated workflow. The resulting purchase order is then sent back to the supplier for order fulfillment.

This is a mechanism by which buyers/requestors can navigate to suppliers website directly from iProcurement.

Punchouts are, typically, for expense items such as office supplies, but are often leveraged by maintenance and IT organizations.

WHAT ARE THE ADVANTAGES OF PUNCH OUT?

Some advantages are:

  • The ability to cost effectively re-use suppliers existing transactional websites to provide custom content to individual buyers.
  • The flexibility which allows suppliers to control product information to ensure real-time quality content, including price and availability.
  • Punch out is a low-cost way to provide easily customised content for many buyers, leading to economies of scale, enhanced customer experience, and reduced customer support costs.
  • Buyers no longer need to manage catalogue content.
  • Punch out enables requisitioners to access supplier catalogues for products / services that reside within the supplier's website.
  • Punch out eliminates the need for the supplier to send electronic catalogues to buying organisations.
  • Punch out reduces buyer and supplier error.
  • cXML is the most widely adopted Business to Business protocol today.

BASIC FLOW

More or less , these are user steps in punchout process irrespective of any model ( as discussed below) ;

  1. The requester in iProcurement or buyer in Exchange clicks a link to the external catalog (punchout) site. Punchout links are available from the Shopping home and
    Search Results pages.
  2. The punchout from application (iProcurement or Exchange) sends the login request to the catalog site.
  3. The punchout to application (Exchange or the supplier site) authenticates the requester or buyer.
  4. The punchout from application redirects the requester’s or buyer’s browser to the catalog site.
  5. The requester or buyer browses or searches for items on the external catalog site and completes shopping on the site.
  6. Via the requester’s or buyer’s browser, the punchout to application returns the shopping cart with the items to the punchout from application.
  7. The requester or buyer completes the checkout process for the items in the shopping cart, and the punchout from application processes the order.

THE PUNCHOUT MODELS

The Punchout Models available are:

  • Model 1: Punchout from Oracle iProcurement to Oracle Exchange (XML)
  • Model 2a: Punchout from Oracle iProcurement Directly to Supplier-Hosted Catalog (XML)
  • Model 2b: Punchout from Oracle iProcurement Directly to Supplier-Hosted Catalog(cXML)
  • Model 3a : Punchout from Oracle Exchange to Supplier- Hosted Catalog (XML)
  • Model 3b: Punchout from Oracle Exchange to Supplier- Hosted Catalog (cXML)
  • Model 4: Punchout from Oracle iProcurement to Supplier- Hosted Catalog via Oracle Exchange (XML)
  • Model 5: Punchout from Oracle iProcurement to Supplier- Hosted Catalog via Oracle Exchange (cXML)

Model 1: PUNCHOUT FROM ORACLE IPROCUREMENT TO ORACLE EXCHANGE (XML)

In model 1, the supplier loads catalog items directly to Oracle Exchange.

The catalog administrator then sets up Oracle iProcurement to use Oracle Exchange as the punchout hub.

How this works:

  • When the user clicks on a punchout link to Oracle Exchange, Oracle Exchange authenticates the requester and returns a response.
  • If the authentication is successful, the user is redirected to the Oracle Exchange site to search for and add items.
  • When the requester finishes adding items to the Oracle Exchange shopping cart, Oracle Exchange returns these items to the requisition.
  • The requester then submits the requisition.

The illustration below shows Model 1.

model1

If you see above diagram , Oracle Exchange can be setup as an aggregator site, where requesters can have access to items from different suppliers.

In this model benefits for the suppliers include:

  • Suppliers only need to load their catalog items once on Oracle Exchange and can reach many Oracle iProcurement customers in addition to the buyers already registered on Oracle Exchange.
  • Suppliers can make use of the functionality offered by Oracle Exchange to control pricing.

MODEL 2A and 2B: PUNCHOUT FROM ORACLE iPROCUREMENT TO SUPPLIER HOSTED CATALOG (XML & CXML)

In models 2a and 2b, the supplier hosts the catalog at their own site or web store. The catalog administrator sets up a punchout catalog to use the supplier as a punchout site.

  • When the requester clicks on a punchout link to the supplier site, the supplier authenticates the requester and returns a response.
  • If the authentication is successful, Oracle iProcurement redirects the requester to the supplier site to search for and add items.
  • When the requester completes adding items to the supplier shopping cart, the supplier site returns the shopping cart items to Oracle iProcurement.
  • The requester then submits the requisition.

The illustration below shows Models 2a and 2b.

MODEL2

 

MODEL 3: PUNCHOUT FROM ORACLE iPROCUREMENT TO SUPPLIER HOSTED CATALOG THROUGH ORACLE EXCHANGE (XML)

In this model, the supplier hosts the catalog at their own site or web store.

  1. When the user clicks on the punchout link, the requester is taken directly to the supplier site.
    • Although behind the scenes, the access is through Oracle Exchange. Using Oracle Exchange for the punchout simplifies the initial setup process and the authentication and maintenance of the punchout.
  2. The supplier must set up a punchout from Oracle Exchange to their site.
    • To setup access to the supplier site through Oracle Exchange, the catalog administrator needs to download the supplier punchout definition from Oracle Exchange.
    • Downloading the supplier punchout definition seeds the punchout definition from Oracle iProcurement to the supplier site through Oracle Exchange, without requiring the catalog administrator to perform manual setup.
  3. The requester clicks on the punchout link, Oracle Exchange authenticates the requester, and sends a punchout request to the supplier.
  4. The supplier site then responds to Oracle Exchange, and in turn Oracle Exchange forwards the supplier site response to Oracle iProcurement .
    • If successful, the requester is redirected to the supplier site for shopping.
  5. When the requester completes adding items to the supplier shopping cart, the supplier site returns the shopping cart items to the requisition. The requester then submits the requisition.

The illustration below shows Model 3.

MODEL3

MODEL 4: PUNCHOUT FROM ORACLE IPROCUREMENT TO SUPPLIER HOSTED CATALOG THROUGH ORACLE EXCHANGE (CXML)

In Model 4, the supplier hosts a cXML catalog at its own site or web store. Similar to Model 3, the requester accesses the supplier site (behind the scenes) through Oracle Exchange.

The supplier must set up a punchout from Oracle Exchange to its site, and the catalog administrator then downloads the supplier punchout definition from Oracle Exchange when setting up the punchout catalog.

  • The requester clicks on the punchout link, Oracle Exchange then authenticates the requester, and sends a punchout request to the supplier.
  • The supplier site then responds to Oracle Exchange, and in turn Oracle Exchange forwards the supplier site response to Oracle iProcurement .
    • If successful, the requester is redirected to the supplier site for shopping.
  • When the requester completes adding items to the supplier shopping cart, the supplier site returns the shopping cart items to Oracle iProcurement .
  • Oracle iProcurement then redirects the shopping cart to Oracle Exchange, where Oracle Exchange converts the shopping cart from cXML to XML and returns the items to Oracle iProcurement . The requester then submits the requisition.

The illustration below shows Model 4.

Model4

ANALYSIS OF PRESENT AND FUTURE STATE

Before developing a PunchOut, you need to perform an in-depth analysis of your current system and what is needed to support the "new" process. A few things to note:

Take some important note for the current state:

  • Do you have an existing e-commerce site deployed?
  • Does your site have XML integration enabled?
  • Do you currently receive orders electronically through XML or EDI?
  • How is integration performed with back-end systems?

For the future state:

  • How will the process flow from time of shopping through order placement and fulfillment?
  • Will you need to interface with multiple XML-based procurement applications?
  • How should your concept of a "shopping cart" be modeled in requisition line items?
  • Which model should be best for my company ?

Remember , There is no additional licensing that you need to purchase for using Punchout. Next post will be more focus on setup and troubleshooting.

Posted in Oracle Purchasing | No Comments »

Difference between ‘balance forward payment terms’ and other ‘payment terms’

Posted on January 16th, 2013 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Balance forward billing payment terms pass the balance forward billing cycle to the Create Balance Forward Bill program . The billing cycle determines when customer balance forward bills are generated.

Because balance forward bills cannot be split across installments , all settings related to installments on balance forward billing payment terms are disabled.

You cannot change existing payment terms back and forth for use as both a non-balance forward billing and balance forward billing payment terms.

Posted in Oracle Receivable | No Comments »

Page 1 of 212

« Previous Entries