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

What is In “Order Import”

Posted on May 27th, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

This is yet another powerful tool in EBS to quickly new, changed, and completed Sales Orders or Returns from

  • Legacy System
  • EDI Gateway transactions
  • Other EBS applications like purchasing, contracts etc
  • Other front end applications (web based, 3rdparty )

Order Import Interface consists of Open Interface tables.

Order Import features include validation and defaulting, processing constraint checks, applying and releasing of order holds, scheduling of shipments, then ultimately inserting, updating or deleting the Orders in the base Order Management tables. Order Management checks all the data during the import process to ensure its validity within Order Management. Valid transactions are then converted into Orders with Lines, Reservations, Price Adjustments, and Sales Credits in the base Order Management tables.

dgreybarrow Features of Order Import

  • Have status of imported orders and Workflow
  • use for Cancellation
  • This update existing orders
  • This importing closed orders
  • This add customer
  • This importing Price Adjustments
  • this importing returns (referenced and non referenced)
  • This is use Manual and Automatic Pricing
  • This will do Price Comparison (with customer price)
  • This also check Payment term comparison (with customer terms)
  • Credit Checking , holds and releases
  • Notes and attachments
  • Validating data
  • Defaulting rules
  • Processing constraints
  • Customer item number
  • Corrections form
  • Validate Only Mode
  • Order Import Statistics Concurrent Program

dgreybarrowTable

Interface tables for Order Import

  • OE_HEADERS_IFACE_ALL
  • OE_LINES_IFACE_ALL
  • OE_PRICE_ADJS_IFACE_ALL
  • OE_PRICE_ATTS_IFACE_ALL
  • OE_CUSTOMER_INFO_IFACE_ALL
  • OE_CREDITS_IFACE_ALL
  • OE_LOTSERIALS_IFACE_ALL
  • OE_RESERVTNS_IFACE_ALL
  • OE_ACTIONS_IFACE_ALL

dgreybarrow First timer

These are the steps associated in doing interfacing :

  • Set up Order Source
  • Populate data into interface tables for that source
  • Run the order import concurrent request or Import using the corrections form
  • Query the imported or updated order in Order Organizer

In any time if you encounter error you can use the Order Import Correction window to examine the Order and optionally correct data, if it fails the Import process. You can use the Error Message window to determine if your data failed to import.

dgreybarrowSteps by step

Step 1 :Pre-Requisite setup

The following steps are prerequisites to importing Orders:

  • You can set up every aspect of Order Management that you want to use with imported Orders, including Customers, Pricing, Items, and Bills.
  • You can define and enable your Order Import sources using the Order Import Sources window.
  • Determine if you should submit the Order Import Statistics concurrent program.

Before that , the following Profile Options must be set-up prior to importing Orders:

  • OM: Item Validation Organization - Determines the Organization used for validating Items and Bills of Material structures.
  • OM: Reservation Time Fence - This profile option controls automatic Reservations during scheduling.
  • OM: Apply Automatic Attachments - This profile option determines whether Rule-based attachments are applied without user intervention.

Step 2 :Populate data into interface tables for that source

Importing Order Header Information into OE_HEADERS_IFACE_ALL Table

  • Populate your data into table OE_HEADERS_IFACE_ALL which is a multi-org table for Sales Order Headers Open Interface.
  • This table stores Order Header information that is imported from a feeder system into Oracle Order Management using Order Import
  • A record has be inserted into Order Headers Interface table, for any operation on the Order. The orig_sys_document_ref column is referred when submitting the Order Import Concurrent program

Importing Order Lines Information into OE_LINES_IFACE_ALL Table

  • Populate your data into table OE_LINES_IFACE_ALL which is a multi-org table for Sales Order Lines Open Interface.
  • This table stores Order Lines information that is imported from a feeder system into Oracle Order Management using Order Import.

Importing Customer Information into OE_CUSTOMER_INFO_IFACE_ALL Table

Importing Customer related information is optional. Use this step, only if Customer Accounts / Contacts / Addresses need to be imported, while importing Orders into Oracle Applications.

  • Populate your data into table OE_CUSTOMER_INFO_IFACE_ALL is used to add new Customer, its Address and Contact information.
  • New Customer can be added by populating the required columns in this table, for that Customer new Address can be added, and for these new Account and Addresses, Contact information can also be added using this table
  • If you are importing make sure parent_Customer_Ref must be populated in case the current record needs to be linked to a Parent Customer record.
  • In case the Customer is a Person, columns First_Name, Last_Name, etc. must be populated for Customer_Info_Type_Code = ACCOUNT.

Importing Pricing Adjustments into OE_PRICE_ADJS_IFACE_ALL Table

Importing Pricing Adjustments is an optional .This should be included in Order Import, only if Price Adjustments need to be imported

  • Populate your data into table OE_PRICE_ADJS_IFACE_ALL is a multi-org open interface table for Sales Order/Line Price Adjustments.
  • This table stores Price Adjustment information that is imported from a feeder system into Oracle Order Management using Order Import.

Importing Pricing Attributes into OE_PRICE_ATTS_IFACE_ALL Table

Importing Pricing Attributes is an optional . Include this step, if Pricing Attributes need to be imported for the Order.

  • Populate your data into table OE_PRICE_ATTS_IFACE_ALL .
  • This Table stores Pricing Attributes information that is imported from a feeder system into Oracle Order Management using Order Import.

Importing Lot Serial Information into OE_LOTSERIALS_IFACE_ALL Table

Importing Lot Serials is an optional step. Include this step, only if Lots/Serial Number information needs to be imported for the Order.

  • Populate your data into table OE_LOTSERIALS_IFACE_ALL table .
  • This table used for Return Line Lot Serials Open Interface.
  • This table stores Return Line Lot Serial information that is imported from a feeder system into Oracle Order Management using Order Import.

Importing Reservation Information into OE_RESERVTNS_IFACE_ALL Table

This is an optional step. Include this step, only if Reservation information needs to be imported for the Order.

  • OE_RESERVTNS_IFACE_ALL need to be populated.
  • This table stores Reservation details that need to be imported.

Importing Sales Credit Information into OE_CREDITS_IFACE_ALL Table

Importing Sales Credits is an optional . use this step, only if Sales Credits information needs to be imported for the Order.

  • This is a multi-org table for Sales Order/Line Credits Open Interface.
  • This table stores Sales Credits information that need to be imported.

Step 3 :Populate data into interface tables for that source

You can initiated by submitting a Order Import Concurrent program.

Navigate to Order Management Super User : Orders, Returns : Import Orders : Order Import Request.

This program have these parameters:

  • Order Source : Choose a specific Order Import source that you have defined in step 1 which you setup via Order Import Sources window.
  • Order References: You can enter the System Document Reference, if you want to run Order Import for a specific Order.
  • Validate Only (Yes/No): Choose whether to validate only the data in the interface tables. If 'Yes', the Order will be validated, but not imported into the base Orders tables. The default value is 'No'.

If you are first timer , you can run the Order Import process in the Validation-only mode. This mode allows the transaction to be validated against all the Order ManWelcome to It's All In OrderIt's All In Orderagement Rules, but does not pass valid transactions to the base Order Management tables.

If you choose, you can run production transactions in Validation-only mode for a preview of exceptions. This will allow you to make necessary corrections to the transactions in the Order Import window, then choose the Validate button to perform a validation check.

The Validation-only mode may also facilitate testing of transactions through Order Import even in a production environment to take advantage of all the setup in the production environment.

Step 4 :Corrections to Imported Data from Order Import Corrections Window

If is needed if you stuck or encountered error in the concurrent program. Navigation would be

Navigate to Order Management Super User : Orders, Returns : Import Orders : Corrections .

If any corrections to the imported data are required, changes to the data can be done from the Corrections window. Once the required changes are made, the same window can be used to launch the Order Import Process again.

You can use the request id of step 3 and click on find button to view the corrections window.

Step 5 :Verify the Imported Order Information

Once the Order Import process has been completed successfully, the same can be verified with the following screens :

Navigate to Order Management Super User : Orders, Returns : Order Organizer.

In the Find window, enter values in Order Source and Order Source Reference fields.

Posted in Oracle Order Management | No Comments »

Auto Invoice – Parameter and Profile Options

Posted on May 27th, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Understanding the profile options and some parameter is essential for autoinvoice execution. Understanding is especially helpful when trouble shooting is required to figure out why and where the processing has failed for certain data scenarios. Here is some informative information for profile Options and parameter required for autoinvoice.

As we know system setup can be done from system options, which is as below.

31

 1.Max Memory (in bytes)
  As marked 1 in above picture. This is memory setting for allocating autoinvoice program for validation. It is recommended to set Value to 3,000,000 Bytes.

2.Log File Message Level

This is at 2 in above picture. This is number represents the amount of detail we wish to display Auto Invoice log file.

  • Message Level 0
    This will gives the following entries in the log file:
    Product Version, Program Name, Auto Invoice Start Time, AutoInvoice Concurrent request Arguments, Error and Warning Messages, AutoInvoice End Time, auto Invoice logical Steps.
  •  Message Level 1
    This gives all of the above entries plus:  Time-Stamped function labels
  •  Message Level 2
    This gives you all of the above entries plus:  Sizes of Allocated Arrays, Dynamic SQL Statements, Number of Rows Updated, Inserted and Deleted
  •  Message Level 3
      This gives you all of the above entries plus: Method IV SQL Array Values.

3. Purge Interface Tables
This is marked 3 in above picture. If this is checked then

  • Purges records that are successfully imported into receivables.

It recommended to avoid getting interface tables filled with data that is no more required

4.AR: Autoinvoice Gather Statistics
Specify whether AutoInvoice process analyzes the interface tables or not

  • Null is taken as Yes
  • This profile should be set to "Yes" if type of data populated in the interface tables changes

5.Number of Instances
This is for Load Balancing.

  • Number of CPU -1
  • Maximum allowed 500

6.AR: Maximum Lines per Autoinvoice worker
This is setting for let worker know how many records need to pick. This setting is more important, if you are loading very huge set of data. If any one is doing conversion, it is essential to check this value.

The default value is 100000,But the optimal value should be 10000.

Hope this will give a fair idea who is going to utilize autoinvoice First time.

Posted in Finance, Oracle Receivable | 3 Comments »

Auto Invoice: Transaction Flexfield

Posted on May 26th, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Why set up is important for transaction flex field in autoinvoice? Does my Autoinvoice get failed if I would not do set up or not passing information for Transaction flex field? Yes, You can't. The way the auto invoicing works is designed it worked to Uniquely identify for each transaction.

Then what are those Transaction Flex Fields?

Transaction flexfields are descriptive flexfields that AutoInvoice uses to identify transactions and transaction lines. Oracle Receivables lets you determine how you want to build your transaction flexfield structure and what information you want to capture. There are four types of transaction flexfields:

  • Line Transaction Flexfield
  • Reference Transaction Flexfield
  • Link-To Transaction Flexfield
  • Invoice Transaction Flexfield

The key point is the Line Transaction Flexfield must be defined if AutoInvoice is being used. The Line Transaction Flexfield can be used to reference and link to other lines because the Line Transaction Flexfield is unique for each transaction line. AutoInvoice always uses the Line Transaction Flexfield structure for both the Link-to and Reference information when importing invoices. It is only necessary to explicitly define the Link-to, Reference, and Invoice Transaction Flexfield structures if this information is to be displayed on a custom window.

You must define both the line-level and header-level Transaction Flexfield. To define the line-level Transaction Flexfield, query 'Line Transaction Flexfield' in the Title field of the Descriptive Flexfield Segments window and enter the context and segments associated with this Transaction Flexfield. To define the Transaction Flexfield at the header-level, query 'Invoice Transaction Flexfield' and enter the context and segments associated with this Transaction Flexfield. All segments in the line level transaction flexfield that refer to header information must also exist in the header level transaction flexfield. For example if you define a line-level Transaction Flexfield with 4 segments and only the last 2 segments refer to line-level information, define the header Transaction Flexfield using the first two segments.

Where to setup
AR gives you the option of using QuickPicks to display reference information for imported invoices. You can use the System Profile Option AR: Transaction Flexfield QuickPick to select the Transaction Flexfield Segment you want to display in Invoice QuickPicks throughout Oracle Receivables.
1

Business Case:

Lets say my autoinvoice having two sources,

1.More4Apps - where data is coming from excel based More4apps.
2.PROJECTS INVOICES - for Creating Project invoices.

So to process these, we have set up like this:

If Source is More4Apps then required INTERFACE_LINE_ATTRIBUTE1 till 2 (Fig :2)
If source is PROJECTS INVOICES then required INTERFACE_LINE_ATTRIBUTE1 till 8 (Fig :3)
11

Fig 2: Setup for Fisrt source as above

12

Fig 3: Setup for second source as above

What is mean, pretty simple based out of source the respective column should be populated. At the time of validation auto invoice will try to validate first the DFF field, based out of Context Value, The value in context field would be the same which appears while defining. And the process should take the value as reference and create a transaction in the AR.

Posted in 11i, EBS Suite, Finance, Oracle Receivable | 7 Comments »

Post Archives

Posted on May 26th, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post


Fatal error: Call to undefined function smartArchives() in /home/oracleappshub/oracleappshub.com/wp-content/plugins/exec-php/includes/runtime.php(42) : eval()'d code on line 1