GL_Interface Errors

Period Error Codes

EP01 This date is not in any open or future enterable period.
EP02 This set of books does not have any open or future enterable periods.
EP03 This date is not within any period in an open encumbrance year.
EP04 This date is not a business day.
EP05 There are no business days in this period.

Unbalanced Journal Error Codes
WU01 Warning: This journal entry is unbalanced. It is accepted because suspense posting is allowed in this set of books.
EU02 This journal entry is unbalanced and suspense posting is not allowed in this set of books.
EU03 This encumbrance journal entry is unbalanced and the Reserve for Encumbrance account is not defined.

Flexfield Error Codes
EF01 This Accounting Flexfield is inactive for this accounting date.
EF02 Detail posting not allowed for this Accounting Flexfield.
EF03 Disabled Accounting Flexfield.
EF04 This is an invalid Accounting Flexfield. Check your cross-validation rules and segment values.
EF05 There is no Accounting Flexfield with this Code Combination ID.

Foreign Currency Error Codes
EC01 A conversion rate must be entered when using the User conversion rate type.
EC02 There is no conversion date supplied.
EC03 A conversion rate type or an accounted amount must be supplied when entering foreign currency journal lines.
EC06 There is no conversion rate for this currency, conversion type, and conversion date.
EC08 Invalid currency code.
EC09 No currencies are enabled.
EC10 Encumbrance journals cannot be created in a foreign currency.
EC11 Invalid conversion rate type.
EC12 The entered amount must equal the accounted amount in a functional or STAT currency journal line.
EC13 The entered amount multiplied by the conversion rate must equal the accounted amount.
ECW1 Warning: Converted amounts could not be validated because the conversion rate type is not specified.

Budget Error Codes
EB01 A budget version is required for budget lines.
EB02 Journals cannot be created for a frozen budget.
EB03 The budget year is not open.
EB04 This budget does not exist for this set of books.
EB05 The encumbrance_type_id column must be null for budget journals.
EB06 A period name is required for budget journals.
EB07 This period name is not valid. Check calendar for valid periods.
EB08 Average journals cannot be created for budgets.
EB09 Originating company information cannot be specified for budgets.

Encumbrance Error Codes
EE01 An encumbrance type is required for encumbrance lines.
EE02 Invalid or disabled encumbrance type.
EE03 Encumbrance journals cannot be created in the STAT currency.
EE04 The BUDGET_VERSION_ID column must be null for encumbrance lines.
EE05 Average journals cannot be created for encumbrances.
EE06 Originating company information cannot be specified for encumbrances.

Reversal Error Codes
ER01 A reversal period name must be provided.
ER02 This reversal period name is invalid. Check your calendar for valid periods.
ER03 A reversal date must be provided
ER04 This reversal date is not in a valid period.
ER05 This reversal date is not in your database date format.
ER06 Your reversal date must be the same as or after your effective date.
ER07 This reversal date is not a business day.
ER08 There are no business days in your reversal period.
ER09 Default reversal information could not be determined.

Descriptive Flexfield Error Codes
ED01 The context and attribute values do not form a valid descriptive flexfield for Journals - Journal Entry Lines.
ED02 The context and attribute values do not form a valid descriptive flexfield for Journals - Captured Information.
ED03 The context and attribute values do not form a valid descriptive flexfield for Value Added Tax.

Miscellaneous Error Codes
EM01 Invalid journal entry category.
EM02 There are no journal entry categories defined.
EM03 Invalid set of books id.
EM04 The value in the ACTUAL_FLAG must be "A" (actuals), "B" (budgets), or "E" (encumbrances).
EM05 The encumbrance_type_id column must be null for actual journals.
EM06 The budget_version_id column must be null for actual journals.
EM07 A statistical amount belongs in the entered_dr(cr) column when entering a STAT currency journal line.
EM09 There is no Transaction Code defined.
EM10 Invalid Transaction Code.
EM12 An Oracle error occurred when generating sequential numbering.
EM13 The assigned sequence is inactive.
EM14 There is a sequential numbering setup error resulting from a missing grant or synonym.
EM17 Sequential numbering is always used and there is no assignment for this set of books and journal entry category.
EM18 Manual document sequences cannot be used with Journal Import.
EM19 Value Added Tax data is only valid in conjunction with actual journals.
EM21 Budgetary Control must be enabled to import this batch.
EM22 A conversion rate must be defined for this accounting date, your default conversion rate type, and your dual currency.
EM23 There is no value entered for the Dual Currency Default Rate Type profile option.
EM24 Average journals can only be imported into consolidation sets of books.
EM25 Invalid average journal flag. Valid values are "Y", "N", and null.
EM26 Invalid originating company.
EM27 Originating company information can only be specified when inter company balancing is enabled.

Order Management

1) What are the Base Tables and Interface Tables for Order Management?

Interface Tables :
OE_HEADERS_IFACE_ALL,
OE_LINES_IFACE_ALLOE_PRICE_ADJS_IFACE_ALL, OE_ACTIONS_IFACE_ALLOE_CREDITS_IFACE_ALL (Order holds like credit check holds etc)

Base Tables : OE_ORDER_HEADERS_ALL: Order Header Information
OE_ORDER_LINES_ALL: Items Information
OE_PRICE_ADJUSTMENTS: Discounts Information
OE_SALES_CREDITS: Sales Representative Credits.

Shipping Tables :
WSH_NEW_DELIVERIES,
WSH_DELIVERY_DETAILS,
WSH_DELIVERY_ASSIGNMENTS,
WSH_DELIVERIES.

2) What is Order Import and What are the Setup's involved in Order Import?

• Order Import is an open interface that consists of open interface tables and a set of API’s. It imports New, updated, or changed sales orders from other applications such as Legacy systems.
• Order Import features include validations, Defaulting, Processing Constraints checks, Applying and releasing of order holds, scheduling of shipments, then ultimately inserting, updating or deleting orders from the OM base tables.
• Order management checks all the data during the import process to ensure its validity with OM. Valid Transactions are then converted into orders with lines, reservations ,price adjustments, and sales credits in the OM base tables.
• Setups:· Setup every aspect of order management that we want to use with imported orders, including customers, pricing, items, and bills.· Define and enable the order import sources using the order import source window.

4) Explain the Order Cycle?i

• Enter the Sales Order
• Book the Sales Order(SO will not be processed until booked(Inventory confirmation))
• Release sales order(Pickslip Report is generated and Deliveries are created)(Deliveries – details about the delivery. Belongs to shipping module (wsh_deliveries, wsh_new_deliveries, wsh_delivery_assignments etc) they explain how many items are being shipped and such details.
• Transaction Move Order (creates reservations determines the source and transfers the inventory into the staging areas)
• Launch Pick Release
• Ship Confirm (Shipping Documents(Pickslip report, Performa Invoice, Shipping Lables))
• Auto invoice and closed
  

5) Explain the Order to Cash Flow?

• Enter the Sales Order
• Book the Sales Order(SO will not be processed until booked(Inventory confirmation))
• Release sales order(Pickslip Report is generated and Deliveries are created)(Deliveries – details about the delivery. Belongs to shipping module (wsh_deliveries, wsh_new_deliveries, wsh_delivery_assignments etc) they explain how many items are being shipped and such details.
• Transaction Move Order (Selects the serial number of the product which has to be moved/ shipped)
• Launch Pick Release
• Ship Confirm (Shipping Documents(Pickslip report, Performa Invoice, Shipping Lables))
• AutoInvoice (Creation of Invoice in Accounts Receivable Module)
• Autolockbox ( Appling Receipts to Invoices In AR)
• Transfer to General Ledger ( Populates GL interface tables)
• Journal Import ( Populates GL base tables)
• Posting ( Account Balances Updated).

5. What are the Process Constraints?

Process Constraints prevent users from adding updating, deleting, splitting lines and canceling order or return information beyond certain points in the order cycle. Oracle has provided certain process constraints which prevent data integrity violations.Process constraints are defined for entities and attributes. Entities include regions on the sales order window such as order, line, order price adjustments, line price adjustments, order sales credits and line sales credits. Attributes include individual fields (of a particular entity) such as warehouse, shit to location, or agreement.

6. What are Validation Templates?

Validation Templates are used to define the validation conditions in process constraints. A validation template names a conditions and defines the semantic of how to validate that condition.

• These are used in processing constraints framework to specify the constraining conditions for a given constraint. These conditions are based on1 Where the entity is in its work flow.
• The state of attributes on an entity.
• Any other validation condition that cannot be modeled using the above condition.

7. What are different types of Holds?

• GSA(General Services Administration) Violation Hold(Ensures that specific customers always get better pricing for example Govt. Customers)
• Credit Checking Hold( Used for credit checking feature Ex: Credit Limit)
• Configurator Validation Hold ( Cause: If we invalidate a configuration after booking)

8. What is Document Sequence?

Document sequence is defined to automatically generate numbers for your orders or returns as you enter them. Single / multiple document sequences can be defined for different order types.Document sequences can be defined as three types Automatic (Does not ensure that the numbers are contiguous), Gapless (Ensures that the numbering is contiguous), Manual Numbering. Order Management validates that the number specified is unique for order type.

9. What are Defaulting Rules?

A defaulting rule is a value that OM automatically places in an order field of the sales order window. Defaulting rules reduce the amount of information one must enter. A defaulting rule is a collection of defaulting sources for objects and their attributes.It involves the following steps:

• Defaulting Conditions - Conditions for Defaulting
• Sequence – Priority for search
• Source – Entity ,Attribute, Value
• Defaulting source/Value

10. When an order cannot be cancelled?

An order cannot be cancelled if,

• It has been closed
• It has already been cancelled
• A work order is open for an ATO line
• Any part of the line has been shipped or invoiced
• Any return line has been returned or credited.

11. When an order cannot be deleted?

you cannot delete an order line until there is a need for recording reason.

12. What is order type?

An order type is the classification of order. It controls the order work flow activity, order number sequence, credit check point and transaction type. Order Type is associated to a work flow process which drives the processing of the order.

13. What are primary and secondary price lists?

Every order is associated to a price list as each item on the order ought to have a price. A price list is contains basic list information and one or more pricing lines, pricing attributes, qualifiers, and secondary price lists. The price list that is primarily associated to an order is termed as Primary price list.The pricing engine uses a Secondary Price list if it cannot determine the price of the item ordered in the Primary price list.

14. What is pick slip? Types?

It is an internal shipping document that pickers use to locate items to ship for an order.1 Standard Pick Slip – Each order will have its own pick slip with in each picking batch.2 Consolidated Pickslip – Pick slip will have all the orders released in the each picking batch.

15. What is packing slip?

It is an external shipping document that accompanies the shipment itemizing the contents of the shipment.

16. What are picking rules?

Picking rules define the sources and prioritization of sub inventories, lots, revisions and locators when the item is pick released by order management. They are user defined set of rules to define the priorities order management must use when picking items from finished goods inventory to ship to a customer.

17. Where do you find the order status column?

In the base tables, Order Status is maintained both at the header and line level. The field that maintains the Order status is FLOW_STATUS_CODE. This field is available in both the OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL.

18. When the order import program is run it validates and the errors occurred can be seen in?

Responsibility: Order Management Super UserNavigation: Order, Returns > Import Orders > Corrections

[OM] Order Line Status Did Not Changed to Shipped After Ship Confirm

It was still remain status "Picked" after Ship Confirm process. I could not find any more outstanding shipment at Shipping Transactions form.
Manual submit concurrent program, Shipping -> Interfaces -> Run, Interface Trip Stop - SRS, you will see the stuck Delivery number at the LOV. Submit it and the order line will change from "Picked" to "Shipped".
This is a very common problem in Oracle OM module (they even created a menu for this), hope Oracle can further improve its OM module.

Setup -> Rules -> Security -> Processing Constraints

Application: Order Management
Entity: Order Line
Operation: Update
Attribute: Request DateUser
Action: Require Reason and Require History
Scope: AnyValidation
Entity: Order Line
Record Set: LineValidation
Template: Entered
Applicable To: All responsibilities

I am expecting a prompt for Reason Code if I update the Request Date field in Order Line. It works for my existing responsibility but NOT for my new responsibility that tied to my new Operating Unit (OU).

At OM setup, System Parameter Value, select the new OU, Generic Parameters category, Audit Trail parameter, the initial value was blank. Now, set it to "Enable when Order is Booked". The window for Reason Code will appear after you updated the Request Date and Save.

Question: I have been asked to customize Invoice Print program which happens to be an Oracle Report. What will be the steps, that I must follow.

Answer : Follow the steps below.

1. You will be told the name of the existing report that must be customized. Note down the exact name and query that name in Concurrent Program screen.

Click on “Copy Program button” selecting checkbox option “Copy Parameters”. This will help you copy the current program definition to custom version of the program. Also note down the name of the executable as it appears in concurrent program definition screen.

2. In same responsibility i.e. Application Developer, navigate to screen concurrent executable and query on the field labeled "Executable Short Name".
Note down the application within which it is registered. If the application is Oracle Receivables, then you must go to the database server and get hold the file named RAXINV.rdf in $AR_TOP/reports/US.

3. Copy that file to your custom AR Top directory. Basically that is the directory where custom reports for AR will be deployed..
cd $XXAR_TOP/reports/us
cp $AR_TOP/reports/us/RAXINV.rdf $XXAR_TOP/reports/us

Order Import Interface

Order Import Interface (Sales Order Conversion)

 

          Interface tables:

·         OE_HEADERS_IFACE_ALL        

·         OE_LINES_IFACE_ALL                               

·         OE_ACTIONS_IFACE_ALL                           

·         OE_ORDER_SOURCES                      

·         OE_CUSTOMER_INFO_IFACE_ALL       

·         OE_PRICE_ADJS_IFACE_ALL    

·         OE_PRICE_ATTS_IFACE_ALL

         

          Base tables:  

·         OE_ORDER_HEADERS_ALL         

·         OE_ORDER_LINES_ALL

          Pricing tables          

·         QP_PRICING_ATTRIBUTES

 

          During import of orders, shipping tables are not populated.

 

If importing customers together with the order, OE_ORDER_CUST_IFACE_ALL

Base Tables: HZ_PARTIES    HZ_LOCATIONS

 

Orders can be categorized based on their status:

                   1. Entered orders              

2. Booked orders               

3. Closed orders

                  

Concurrent Program: Order Import

 

Validations:

·         Check for sold_to_org_id. If does not exist, create new customer by calling create_new_cust_info API.

·         Check for sales_rep_id. Should exist for a booked order.

·         Ordered_date should exist. -------- header level

·         Delivery_lead_time should exist. ----------- line level

·         Earliest_acceptable_date should exist.

·         Freight_terms should exist

 

Order Import API    OE_ORDER_PUB.GET_ORDER, PROCESS_ORDER

 

          Concurrent programs will in turn call APIs.

          2 APIs are called during order import process.

·         OE_CNCL_ORDER_IMPORT_PVT (cancelled orders)                    

·         ORDER_IMPORT_PRIVATE

          Procedure: import_order()