Receiving Price/Sales Catalog Information thru EDI

Receiving Price/Sales Catalog Information thru EDI

Your supplier can send you the latest price/sales catalog information and responses to requests for quotation through the Purchasing Documents Open Interface. The Purchasing Documents Open Interface processes catalog data in the Oracle Applications interface tables to ensure that it is valid before importing it into Purchasing. One way to import catalog data into the Purchasing Documents Open Interface, and finally into Purchasing, is through Electronic Data Interchange (EDI). EDI programs import the catalog information into Purchasing directly as blanket purchase agreement lines or catalog quotations, whichever you choose. You can also choose to have the programs automatically populate the item master and/or apply sourcing rules to the imported item information. If you import price/sales catalog information as blanket purchase agreement lines, you can also specify release generation methods. You can import new documents, replace existing documents entirely, or update existing documents.

The catalog information is sent by the supplier in the form of a "flat file." Your supplier can send you flat files with any of three kinds of action codes: Original, Replace, or Update. An Original file is one in which all the catalog information is new to your system. A Replace file replaces already-created blanket purchase agreement lines or catalog quotations with new documents containing new price/sales catalog information. (The Purchasing Documents Open Interface program replaces the old documents by invalidating their effectivity dates; then it creates new documents with the new price/sales catalog information and the old effectivity dates.) An Update file updates existing blanket purchase agreement and catalog quotation lines without replacing the documents entirely. It updates the unit Price, item Description, unit of measure (UOM), Price Breaks, Expiration Date, and the supplier URL descriptive flexfield if you use one.

Note: An Update submission does not update the UOM on an agreement line for which an open release exists. Instead, it uses the Expiration Date field to expire the line on the agreement, and creates a new line with the updated UOM, which will be used on future releases.

The Purchasing Documents Open Interface also imports price breaks. In an updated price/sales catalog, if the supplier updates an item's price, the Purchasing Documents Open Interface deletes the item's price breaks since they are no longer current with the new price. If the supplier sends new price breaks for an existing line, the current price breaks are deleted and the new price breaks sent by the supplier are created.

The Purchasing Documents Open Interface supports the Oracle e-Commerce Gateway transmissions of the price/sales catalogs (ANSI X12 832 or EDIFACT PRICAT) and responses to RFQs (ANSI X12 843 or EDIFACT QUOTES).

For e-Commerce Gateway to distinguish between Original, Replace, and Update action codes, you need to set up code-conversion categories and values in e-Commerce Gateway. See: Defining Code Conversion Categories. See: Defining Code Conversion Values.

Other setup includes making sure that default category sets are set up appropriately for both Purchasing and Inventory, setting Purchasing profile options, and allowing updating of the item master if you want to update the item description in the item master as well as on the blanket purchase agreement or quotation. For complete instructions on setup requirements, see the Oracle Manufacturing, Distribution, Sales and Service Open Interfaces Manual.

How Sourcing Works

When you import price/sales catalog information into Purchasing, you have the option of choosing Yes or No in the Create Sourcing Rules field in the Parameters window to enable Purchasing to create sourcing rules out of the supplier, item, and document information that the supplier sends.

Original and Replacement Price/Sales Catalogs

If you choose Yes to create sourcing rules in an original or replacement price/sales catalog, Purchasing checks if a sourcing rule is assigned to the item at the item level and does the following:

If no sourcing rules exist for the item, Purchasing generates a sourcing rule automatically, allocating 100 percent to the supplier importing the information.

If a sourcing rule exists for the item, Purchasing compares the effectivity dates of the incoming document with those of the existing sourcing rule for the item. To ensure that only one sourcing rule is used for the item, Purchasing does the following:

If the effectivity dates of the incoming document are the same as the existing sourcing rule's effectivity dates, Purchasing checks to see if the supplier is in the sourcing rule. If not, Purchasing adds the supplier to the existing sourcing rule with an allocation of 0 percent. Later, you can query the sourcing rule and define your own percentage splits between suppliers.

If the effectivity dates of the incoming document are different than the existing sourcing rule's effectivity dates, but are within or overlap the existing effectivity dates, then a new sourcing rule is not created, so as not to conflict with the existing sourcing rule.

If the effectivity dates of the incoming document do not overlap the existing sourcing rule's effectivity dates, Purchasing updates the item's sourcing rule with the new effectivity dates, adding the supplier at an allocation of 100 percent.

Purchasing checks for an Approved Supplier List entry for the item and supplier/site combination. If an entry exists, Purchasing adds the document to the entry. If an entry does not exist, Purchasing creates a new entry with the new source document.

Updated Price/Sales Catalogs

If you choose Yes to create sourcing rules in an Update submission, new sourcing information is created (as described above) only if the Update submission results in a new line being created.

How Sales Order Attachement can transfer or Copy to corresponding Dropship Purchase Order?

Hello..

Recently We migrated a Business Processes from Legacy JDE system to Oracle 11.5.10.x.

Business is using Drop shipments and had a requirement like the Sales Order attachment is created in Sales order form and it should be retrieved from PO form.

11.5.10.X version of Oracle we don't have this functionality as a standard process, upon further investigation & research i found this workaround.. But that will require Set up changes and Custom Code to implement  and to achieve this requirement.

Here is the following set up:

Choose the Application Object Library Resp > Attachment > Attachment Functions

1) In the attachment function search "Purchase Orders"(User Name) function.

2) Go to blocks, select block "PO_HEADERS".

3) Click on Entities;

Add a new entity "OM Order Header" with Display Method as "Main Entity".

·         In the      privileges make Query as "Always" and rest all as "Never".

·         In the primary key fields, put      "PO_HEADERS.ATTRIBUTE3" and save it.

NOTE: This means that in the "PO_HEADERS" , need to see the documents attached in "OM Order Header" and the primary key of "OM Order Header" in sales order form and purchase order form should match. In sales order its "ORDERS.HEADER_ID" and the corresponding field in purchase order is "PO_HEADERS.ATTRIBUTE3")

You can use any attribute till the time same is available.

We have to write some custom code to ensure the Attribute is getting populated with the Order_header_id.  Oracle will not populate this filed.

n  I remember I gather this info from oracle support. You feel helpful, pls leave a tiny comment that boosts my motive of sharing.

How to handle Inventory Periods End / Closing Process

 

Inventory Period End Process steps

• Introduction
• Business Requirements
• Steps
• Procedures
• Complete All Transactions for the Period Being Closed
• Check Inventory and Work in Process Transaction Interfaces
• Check Oracle Order Management Transaction Processes
• Review Inventory Transactions
• Balance the Perpetual Inventory
• Validate the Work in Process Inventory
• Transfer Summary or Detail Transactions
• Close the current Oracle Payables and Oracle Purchasing Periods
• Close the Current Inventory Period
• Open the Next Inventory Period
• Run Standard Period-End Reports (Optional)

Introduction

The procedures for performing period-end processing in Oracle Inventory Release 11i.

Business Requirements

The period close process for Oracle Inventory enables summarizing of costs related to inventory and manufacturing for a given accounting period. These costs are then transferred to the General Ledger for posting.

 Steps

Oracle Inventory and Oracle Cost Management provide the required features to effect the necessary period-end procedures to:

·         Reconcile the inventory and work in process costs and values.

·         Transfer inventory and manufacturing costs to the General Ledger.

·         Transfer summary or detail accounting information to the general ledger.

·         Independently open and close periods for each inventory organization.

·         Perform interim transfers to the General Ledger without closing the period.

·         Maintain the same set of periods and fiscal calendar as for the General Ledger.

Attention: For period-end adjustment purposes, it may be appropriate to hold more than one period open per inventory organization at the same time, although at other times, having only one period open at a time ensures that transactions are correctly dated and posted to the correct accounting period.

Procedures

The following steps are taken in performing period-end processing for Oracle Inventory:

Complete All Transactions for the Period Being Closed

·         Ensure that all issues, receipts, and adjustments have been entered and verify that no hard copy records exist or are awaiting data entry, e.g. packing slips in receiving.

·         Optional Report - Cycle Count Report

This report will highlight any unconfirmed ad-hoc Stock takes.

Check Inventory and Work in Process Transaction Interfaces

Check the Interface Managers window to ensure that there are no background or concurrent programs unprocessed.

Check all three selections, Transactions Interface, Internal Transactions, and Demand Interface, and fix any rejected transactions.

The interface managers that need to be run are as follows:

·         Material Transaction Manager

·         Material Cost Transaction

·         Move Transaction Manager

·         Resource Cost Transaction Manager

·         Check the Reservation Managers window

·         Demand Reservation Manager

Check Oracle Order Management Transaction Processes

Ensure all sales order (Pick Release) issues through Oracle Order Management have been completed and transferred successfully to Oracle Inventory.

Attention : If orders have not been released, they do not have to be completed.

Review Inventory Transactions

Before closing a period, review all of the transactions for the period that have a high dollar value and/or a high transaction quantity. Verify that the correct accounts have been charged. Correcting incorrect account charges before closing the period is easier than writing manual journal entries to resolve them later.

Balance the Perpetual Inventory

Check that the perpetual inventory value up to the end of the period being closed matches the value reported in the General Ledger. This balancing is usually effected automatically, but one of the following three sources may create a problem:

·         Other inventory journal entries

Journal entries from products other than Oracle Inventory, that update the inventory accounts.

·         Charges to improper accounts

For example, material issued from a sub-inventory to a miscellaneous account, but one of the sub-inventory accounts was used as that miscellaneous account.

·         Transactions after period end reports

This occurs when the period-end inventory valuation reports are submitted before all transactions for the period have been completed.

Use the Historical Inventory Balance Report to obtain period valuation information before the extra transactions.

The following reports can be run to help with these reviews:

·         Inventory Value Report

Use the Inventory Value Report to show quantity, valuation, and detailed item information for the sub-inventories specified.

·         Period Close Value Summary Report

Use the Period Close Value Summary to see summary balances for sub-inventories. If you run this report for a closed accounting period, the report displays the sub-inventory values at the end of that period. If you run the report for an open period, the report displays the sub-inventory value at the point in time you run the report. You can see more sub-inventory balance detail by running the Inventory Value Report, or the Elemental Inventory Value Report.

·         Material Account Distribution Detail Report

Use the Material Account Distribution Detail Report to view the accounts charged for inventory transactions. Review inventory transaction values transferred to the general ledger by GL batch.

·         Material Account Distribution Summary Report

Use the Material Account Distribution Summary report to review inventory accounting activity. If you detect unusual accounts or amounts, use the Material Account Distribution Detail report to print the transaction in detail.

Use the Material Account Distribution Summary Report to verify inventory account activity against inventory valuation increases or decreases for the accounting period. Finally, use this report to reconcile an account across several periods.

Validate the Work in Process Inventory

If Oracle Work in Process is installed, check the work in process inventory balances against transactions with the WIP Account Distribution Report, by summary or detail.

The WIP Account Distribution Report details account information for work in process cost transactions, including resource, overhead and outside processing charges, cost updates, and period close and job close variances. The system groups your transactions by job or schedule, by transaction type, and orders your transactions by earliest transaction date. You can list detailed account information for specific accounts, general ledger batches, or both to help you reconcile your general ledger.

This report does not list material cost transactions such as issues, completions, and scrap. You can list this information using the Material Account Distribution reports in Oracle Inventory.

Transfer Summary or Detail Transactions

If time permits, run the Transfer transactions to GL process up to the period end date before closing the period. Closing a period automatically executes the general ledger transfer, but the process can be run without closing the period, using the General Ledger Transfer window. Since a period, once closed, cannot be reopened, running this process prior to closing the period facilitates proofing of the interfaces transactions, and any adjustments to the period can be made via new inventory transactions as required.

Attention: The Transfer transactions to GL Process must be run for each Inventory Organisation.

Attention: If this step was by-passed, and the period was closed, a GL Transfer would automatically be initiated, but no adjustments to that period could then be entered, since transactions cannot be posted to a closed period, and a closed period cannot be re-opened.

View the General Ledger Transfer History to ensure that all transactions have been successfully transferred to the General Ledger. Navigate to the General Ledger Transfer window and search for all transfers with a status of Error.

Close the current Oracle Payables and Oracle Purchasing Periods

Complete all steps required to close Oracle Payables and Oracle Purchasing. Oracle Payables is closed prior to Oracle Purchasing to enable running of purchase accruals to accrue expenses on un-invoiced receipts.

If Oracle Purchasing or Oracle Inventory are closed, a receipt cannot be entered for that period. However, as a manual procedure, Oracle Purchasing should be closed before Oracle Inventory.

Close the Current Inventory Period

Closing the inventory period using the Inventory Accounting Periods window automatically transfers summary transactions to the general ledger interface table.

Attention: This process needs to be actioned for each Inventory Organisation defined.

Prior to closing the inventory period, click on the Pending button to display pending transactions. This will display transactions under the following statuses:

Resolution Required: displays the number of unprocessed material transactions, uncosted material transactions, and pending WIP costing transactions existing in this period. These must be resolved before the period is closed.

Resolution Recommended: Displays the number of pending receiving transactions, pending material transactions, and pending shop floor move transactions existing in this period. You can close the accounting period, however, after it is closed these transactions cannot be processed.

The period close performs the following:

·         Closes the open period for Oracle Inventory and Oracle Work in Process.

·         Creates summary or detail inventory accounting entries in the GL interface.

·         Creates summary or detail work in process accounting entries in the GL interface.

·         Calculates period-end sub-inventory balances.

For each sub-inventory, the period close period adds the net transaction value for the current period to the previous period’s ending value. This creates the period-end value for the current period. The period-end values by sub-inventory can be viewed via the Period Close Enquiry form, or reported with the Period Close Summary Report.

The period close process automatically transfers all job costs and variances by general ledger account. Discrete jobs and certain non-standard jobs are closed separately. Job close performs the necessary accounting for each job, including variance calculations. For expense non-standard jobs, the period close process writes off any remaining balances and transfers any period costs to the general ledger.

Warning: Closing an inventory period permanently closes the period and no further transactions can be charged to that period.

Open the Next Inventory Period

Open the next inventory period using the Inventory Accounting Periods window.

Attention: This process needs to be actioned for each Inventory Organisation defined.

Run Standard Period-End Reports (Optional)

·         Inventory Value Report

Reconcile Oracle Inventory with the General Ledger.

The above details are gathered and compiled from different sources and applicable to 11.5.10.x version..just for info. 

How to handle Oracle Inter Org Transfer Make items cost rollup

We recently came up with a situation where there are assemblies that are manufactured in Plant-A and that assembly is being used as a component in Plant-B. ( for such items the oracle cost is not matching with Legacy JDE cost),Solution to Cost Rollup in this type of scenarios is as follows:

1. Identify all the Items of this type ( eg: XXX) that are manufactured in Plant-A

2. Create a Sourcing Rule in Plant-B for these items ( Name the sourcing Rule as “ B Transfer”)

3. Perform a complete cost Rollup in Plant-A. ( with this Rollup, all the assemblies in Plant-A and Plant-B will get rolled up, to the Parent assemblies in Plant-A)

4. Copy cost of all the items from Plant-A to Plant-B,doing so the rolled up cost of item like XXX will get copied to Plant-B.

5. Now perform a cost rollup in Plant-B, we can see the Parent assembly with the assemblies that are manufactured in Plant-A and that assembly is being used as a component in Plant-B,will get costed.
 

Concurrent Programs need to be scheduled in such a manner first Complete cost rollup in Plant-A, second copy cost to Plant-B, third Run complete Rollup in Plant-B.

From conversion point of view::

a) We need to collect data from business and add all Items to the sourcing Rule “ B Transfer” in Plant-B.

b) We need to run a new concurrent program to “update the lead time”

Logic for this will be :

1) Based on sourcing Rule “ B Transfer From” copy the cumulative lead time from Plant-A and Paste to the Processing Lead time in Plant-B.

There should not be Planner code for these items in Planner-B, but planner code is must in Plant-A. Then ASCP will create a Planned work order for Plant-A, similar to “ B Transfer” Items

This is just my thought, you can leverage to the extent to match with your case.

How to resolve Oracle Inventroy Pending Transactions

Resolution Required Transactions:

“Unprocessed Material” indicate there are unprocessed material transactions in the
MTL_MATERIAL_TRANSACTONS_TEMP table.

- To resolve Unprocessed Material

transactions, users need to identify and resolve the errors and issues preventing a record from being processed through the MTL_MATERIAL_TRANSACTIONS_TEMP table. Details of transactions can be viewed through the Applications by navigating to the Pending Transactions form .- By using the Pending Transactions window, users view, edit, correct and resubmit unprocessed material transactions. There are five tabs to select the type of information: Error, Location, Source, Intransit
and Others, which provide detailed Information on the transactions. - In the Pending Transactions window either select the Resubmit check box to resubmit one record or choose Select All to Resubmit from the Special Menu and selectively deselect individual transaction you do not want to resubmit, save your work.
- Verify transactions to be resubmitted since there may be Move Order Transactions that must be processed through the Transact Move Order Form.

“Uncosted Material” indicate there are material transactions in the
MTL_MATERIAL_TRANSACTIONS table with unprocessed accounting entries.

- To resolve uncosted Material Transactions you need to determine and fix what is preventing a record from being processed through the MTL_MATERIAL_TRANSACTIONS table. Details of uncosted transactions can be viewed through the Applications by navigating to the Material Transactions form.

In the find Parameter Window there is a field “Costed” and from the list of values “Yes, No, Error or Null” can be selected. The failed transactions are the ones that will need to be corrected and the transactions that are not costed will need to be costed to close the period.

Cost > View Transactions > Material Transactions

“Pending WIP Costing” transactions indicate there are unprocessed resource and overhead accounting transactions in the WIP_COST_TXN_INTERFACE table.

“Uncosted WSM txn” indicate there are uncosted transactions in the
WSM_SPLIT_MERGE_TRANSACTIONS table.

“Pending WSM interface” indicate there are pending transactions in the
WSM_SPLIT_MERGE_TXN_INTERFACE table.

Resolution Recommended Transactions:

“Pending Receiving” transactions indicate there are unprocessed purchasing transactions in the RCV_TRANSACTIONS_INTERFACE table. These transactions include purchase order receipts and returns for inventory. These transactions are not included in your receiving value if they are not resolved prior to closing the period.

“Pending Material” transactions indicate there are unprocessed material transactions in the MTL_TRANSACTIONS_INTERFACE table.

“Pending Shop Floor Move” transactions indicate there are unprocessed shop floor move transactions in the WIP_MOVE_TXN_INTERFACE table.

Unprocessed Shipping Transactions:

“Pending Transactions” in the Unprocessed Shipping Transactions zone indicate there are transactions in the WSH_DELIVERY_DETAILS table in a status of shipped and next step is Run Interfaces. Run the Tripstop Interface SRS Program with either Trip or Delivery number and see. If COGS workflow customized you may see request get completed with Warning. Verify Request log for the error details. Mostly we can see here error # Unable to get account for delivery detail id XXXXX    For more details and complete detailed approach..pls refer this document Inventory Transactions Guide [ID 102878.1]