ORACLE APPS GUIDE

What is PO Module in Oracle Apps R12

2025-03-15T21:21:00.002+05:30

What is PO Module in Oracle Apps R12? A Complete Guide

Introduction

The Purchase Order (PO) Module in Oracle Apps R12 is designed to simplify procurement and purchasing operations. It allows organizations to create, approve, track, and manage purchase orders efficiently. This module is integrated with other Oracle EBS modules like Inventory, Accounts Payable, iProcurement, and Sourcing, making procurement seamless across the enterprise.

In this guide, we will explore the key features, types of purchase orders, approval process, and how the PO module works in Oracle R12.

Key Features of Oracle PO Module

Feature	Description
Automated PO Creation	Converts approved requisitions into purchase orders automatically.
Approval Workflow	Uses AME (Approval Management Engine) and position-based approvals.
Multiple PO Types	Supports Standard, Blanket, Contract, and Planned POs.
Integration with AP & INV	Seamless connection with Accounts Payable (AP) and Inventory (INV) for smooth processing.
Supplier Management	Enables supplier qualification, sourcing, and negotiations.
Receiving Controls	Tracks goods received and manages returns.
Price Breaks & Agreements	Handles vendor pricing and long-term purchase agreements.

Types of Purchase Orders in Oracle Apps R12

PO Type	Purpose
Standard PO	Used for one-time purchases where the price and quantity are fixed.
Blanket Purchase Agreement	Used for long-term agreements with suppliers where items are purchased periodically.
Contract PO	A legal agreement with a supplier without specifying items and quantities.
Planned PO	A PO created for future purchases, where releases are required before ordering.

How the Purchase Order Process Works in Oracle R12

The PO module follows a systematic process from request to final payment.

1. Requisition Creation

Users create Purchase Requisitions to request goods or services.
Requisitions can be created manually or through iProcurement.

2. Purchase Order Creation

Approved requisitions are converted into Purchase Orders.
Buyers can create POs manually or use AutoCreate functionality.

3. PO Approval Process

PO goes through Approval Hierarchy (Position-Based) or AME (Approval Management Engine).
Approvers receive workflow notifications and approve/reject POs.

4. Supplier Confirmation & Dispatch

Once approved, POs are sent to suppliers via Email, Fax, or EDI.
Suppliers acknowledge and confirm delivery timelines.

5. Goods Receipt & Inspection

Received goods are verified against the PO in Oracle Inventory (INV).
Quality checks are performed before accepting the delivery.

6. Invoice Matching & Payment Processing

Invoices are matched with POs in Oracle Accounts Payable (AP).
Once verified, payment is processed to the supplier.

Key Tables Used in Oracle PO Module

Table Name	Description
PO_HEADERS_ALL	Stores Purchase Order headers.
PO_LINES_ALL	Stores PO line details (items, quantity, price).
PO_DISTRIBUTIONS_ALL	Stores charge account details.
PO_VENDORS	Stores supplier information.
PO_ACTION_HISTORY	Tracks approval and status changes.

“A GUIDE FOR ORACLE E-BUSINESS SUITE” –A complete Solution and Learning platform For Oracle Apps R12/11i, Training, India Localization, Technical, P2P, O2C, Drop-shipment, AR/AP Cycle, Implementation, Bug or error in Oracle Apps R12/11i, Up-gradation, Support, Alert, Personalization, Discoverer management, OracleApps R12/11i Module, Finance, SCM, MRP, ASCP, WIP, BOM, FA, AP, AR, OM, INV, AOL, MOAC, TCA structure, Project Accounting, CM, Functional,Oracle DBA, ERP, Techno-functional, OAF, Oracle Apps Interview Question and Error in Oracle apps R12/11i. For More Information Visit on www.OracleAppsGuide.com Or Subscribe your email-id on OracleAppsGuide .

Query to find Locked Object in Oracle Apps R12

2016-09-15T22:59:00.000+05:30

How can find Locked Object in Oracle Apps R12 ?or How can find Locked object name and Oracle User name in Oracle Apps R12?

Query 1 -

SELECT b.owner

, b.object_name

, a.oracle_username

, a.os_user_name

FROM v$locked_object a

, all_objects b

WHERE a.object_id = b.object_id

Query 2 -

SELECT c.owner

, c.object_name

, c.object_type

, b.SID

, b.serial#

, b.status

, b.osuser

, b.machine

FROM v$locked_object a

, v$session b

, dba_objects c

WHERE b.SID = a.session_id

AND a.object_id = c.object_id;

Query 3 -

SELECT a.session_id

, a.oracle_username

, a.os_user_name

, b.owner "OBJECT OWNER"

, b.object_name

, b.object_type

, a.locked_mode

FROM ( SELECT object_id

, session_id

, oracle_username

, os_user_name

, locked_mode

FROM v$locked_object ) a

, ( SELECT object_id

, owner

, object_name

, object_type

FROM dba_objects ) b

WHERE a.object_id = b.object_id;

“A GUIDE FOR ORACLE E-BUSINESS SUITE” – A complete Solution and Learning platform For Oracle Apps R12/11i, Training, India Localization, Technical, P2P, O2C, Drop-shipment, AR/AP Cycle, Implementation, Bug or error in Oracle Apps R12/11i, Up-gradation, Support, Alert, Personalization, Discoverer management, OracleApps R12/11i Module, Finance, SCM, MRP, ASCP, WIP, BOM, FA, AP, AR, OM, INV, AOL, MOAC, TCA structure, Project Accounting, CM, Functional,Oracle DBA, ERP, Techno-functional, OAF, Oracle Apps Interview Question and Error in Oracle apps R12/11i. For More Information Visit on www.OracleAppsGuide.com Or Subscribe your email-id on OracleAppsGuide.

Query to find - Is an employer also a buyer or not in oracle Apps or How can check that employee is a buyer

2016-09-15T22:24:00.000+05:30

Query to find Is an employee also a buyer or not In Oracle Apps R12?

Query -

SELECT pa.agent_id, papf.person_id, papf.employee_number, papf.email_address,
pa.category_id, pa.location_id, papf.effective_start_date,
papf.effective_end_date
FROM po_agents pa, per_all_people_f papf, hr_all_organization_units haou
WHERE pa.agent_id = papf.person_id
AND papf.business_group_id = haou.business_group_id
AND TRUNC (SYSDATE) BETWEEN papf.effective_start_date
AND papf.effective_end_date
--AND email_address = 'user@oag.com'
--AND PAPF.EFFECTIVE_END_DATE > SYSDATE
--AND HAOU.BUSINESS_GROUP_ID = 100

Terminology Used in EBS Oracle Apps R12

2016-08-26T11:46:00.000+05:30

What is Implementation, Upgradation, Migration, Reimplementation, Rollout, Support in terms of Oracle Apps R12

or

Difference between Implementation, Upgradation, Migration, Reimplementation, Rollout, Support in terms of Oracle Apps R12

Here are some of Important and frequently use Terminology in Oracle Apps EBS Listed below -:

Implementation
Upgradation
Migration
Reimplementation
Rollout
Support

1- Implementation - First-time implementation or fresh implementation of Oracle application on the server is called Oracle Implementation.

2- Upgradation - Upgrade Any lower version into its higher version is called Oracle Apps EBS Upgradation e.g 11i - R12(12.1.1) or R12 (12.1.1) to R12 (12.2.4).

3- Migration - Migrate some of the Selected data from one instance to another instance as per business requirement is called Migration of Data.

4- Reimplementation - Somehow fresh implementation is not working properly or

it is not suitable for the business then again Application Implement (Reimplement) with the best-fitted design.

5- Rollout - Same Structure develops and design for another Operating Unit within the Busines Group is called Rollout. In this process, one operating unit works for other preceding operating units as a base.

6- Support - Support is the maintenance of Oracle Application after Implementation or GO LIVE of Oracle Apps.

Note -: Link for Oracle Application Implementation guide document.

https://docs.oracle.com/cd/B34956_01/current/html/docset.html

“A GUIDE FOR ORACLE E-BUSINESS SUITE” –A complete Solution and Learning platform For Oracle Apps R12/11i, Training, India Localization, Technical, P2P, O2C, Drop-shipment, AR/AP Cycle, Implementation, Bug or error in Oracle Apps R12/11i, Up-gradation, Support, Alert, Personalization, Discoverer management, OracleApps R12/11i Module, Finance, SCM, MRP, ASCP, WIP, BOM, FA, AP, AR, OM, INV, AOL, MOAC, TCA structure, Project Accounting, CM, Functional,Oracle DBA, ERP, Techno-functional, OAF, Oracle Apps Interview Question and Error in Oracle apps R12/11i. For More Information Visit on www.OracleAppsGuide.com Or Subscribe your email-id on OracleAppsGuide

How can make entry for "TNSNAMES.ORA" on the local host for Oracle Application (In Oracle Apps R12).

2016-08-26T10:54:00.000+05:30

TNSNAMES.ORA entry to runs Oracle Application R12 at local Host
OR
TNS Entry steps to runs Oracle Application R12

Please follow the given steps -:

1- Go to Host Desktop Screen

2- Press Home key + R and Type 'drivers'

Then Press Enter.

3- Now Go to Folder etc < Hosts

Then

In the Host File please make an entry for -

IP Address | Hostname | SID

As - 192.168.1.5 ebs.example.com EBSDB

Important -: Default setup for Oracle Vision Instance to connect database and Application

Host - Host IP Address - 192.168.1.5 (It will be different as per network accordingly)

Port - Port Number - 1521

SID - Service Identification - EBSDB

Note - You can also Explorer the path directly. Follow the given below directory for the same.

C:\Windows\System32\drivers\etc

“A GUIDE FOR ORACLE E-BUSINESS SUITE” –A complete Solution and Learning platform For Oracle Apps R12/11i, Training, India Localization, Technical, P2P, O2C, Drop-shipment, AR/AP Cycle, Implementation, Bug or error in Oracle Apps R12/11i, Up-gradation, Support, Alert, Personalization, Discoverer management, OracleApps R12/11i Module, Finance, SCM, MRP, ASCP, WIP, BOM, FA, AP, AR, OM, INV, AOL, MOAC, TCA structure, Project Accounting, CM, Functional,Oracle DBA, ERP, Techno-functional, OAF, Oracle Apps Interview Question and Error in Oracle apps R12/11i. For More Information Visit on www.OracleAppsGuide.com Or Subscribe your email-id on OracleAppsGuide

2016-05-08T01:27:00.000+05:30

Definition of Lookup in Oracle Apps R12

Or

What is Lookup in Oracle Apps R12?

Or

What is the main purpose of lookups in Oracle Apps R12?

The main purpose of a lookup is to keep programs flexible and easier to configure. Lookups are an approach of creating a configurable “list of values” in E-Business Suite. One of the simplest examples of a lookup type is gender. A “gender lookup” will have definitions as shown next:

Code Meaning
M Male
F Female
U Unknown

Suppose that there is a table for employees named PER_ALL_PEOPLE_F and it has the following columns:

FIRST_NAME
LAST_NAME
DATE_OF_BIRTH
GENDER

The screen that displays an employee’s gender will display a value of Male, Female, or Unknown. However, the database column PER_ALL_PEOPLE_F table. GENDER will store a value of M, F, or U. Hence, the screen displays the meaning, whereas the database columns reference the lookup via a lookup code.

If in the future your organization wants the users to see “Undisclosed” instead of “Unknown,” you will have to make a change to just one record in the lookups table via the lookup screen. By doing so, you will avoid having to update thousands of records in PER_ALL_PEOPLE_F. Your new lookup will look like the following:

Code Meaning
M Male
F Female
U Unknown

Here lies the power of the lookups; you do not need to modify thousands of records in a transactional table. A simple change via the lookup screen will suffice. Using the lookup screen, you can either create new custom lookups or modify existing lookups.

What are the differences between system, extensible, and user lookup types in Oracle Apps R12?

OR

Type of Lookups in Oracle Apps R12

User

Insertion of new codes is allowed
Updating of the start date, end date, and enabled fields are allowed
Deletion of codes is allowed
Updating of the tag is allowed

Extensible

Deletion of lookup type is not allowed
Insertion of new codes is allowed
Updating of the start date, end date, enabled fields, and the tag is allowed only if the code is not 'seed data'
Deletion of codes is allowed only if the code is not 'seed data'
Updating of the module is not allowed

System

Deletion of lookup type is not allowed
Insertion of new codes is not allowed
Updating of the start date, end date, and enabled fields are not allowed
Deletion of codes is not allowed
Updating of the tag is not allowed
Updating of the module is not allowed

The following table shows the differences between system, extensible, and user lookup types:

Brief, some pre-seeded lookups given by Oracle cannot be modified. For example, Oracle has a lookup type called a termination type as shown in the above figure. Oracle has some rules defined within the Payroll Engine program that read the value of a termination type code for employees before calculating their final salaries. Such lookup codes, if changed, can affect the logic within the Payroll Engine. For this reason, Oracle flags some lookups as system lookups, and the Lookup Entry screen will not let you modify those lookup codes.

How can a lookup type be directly attached to a flexfield segment to do validations in Oracle Apps R12?

To do this, create a value set of Table type that validates against FND_LOOKUP_VALUES using the desired lookup. In this manner, you can validate flexfield segments against lookup values.

The point here is that a lookup type cannot be directly attached to a flexfield segment to do validations; however, it is indirectly possible to do so.

Examples and use cases where we use lookups in Oracle Apps R12.

Example: Interfacing Data to Third-Party Systems

Sometimes there is a need to create a database view that becomes the source of information for data transfer to other third-party systems. You might have to put filtration rules in place; for example, for HRMS Extract, people with person types Employee and Applicant should be extracted. To achieve this, instead of hard-coding Employee and Applicant in the database view, you can do the following:

1-Create a lookup type XX_EXTRACT_EMPLOYEE_TYPES.
2-Add lookup codes Employee and Applicant to this lookup type.
3-In the database view, join the HR Person Types from HR Tables with FND_LOOKUP_VALUES for this lookup type.

So through this manner, Lookup also gives you the flexibility to change hard-code Value in Code.

“A GUIDE FOR ORACLE E-BUSINESS SUITE” –A complete Solution and Learning platform For Oracle Apps R12/11i, Training, India Localization, Technical, P2P, O2C, Drop-shipment, AR/AP Cycle, Implementation, Bug or error in Oracle Apps R12/11i, Up-gradation, Support, Alert, Personalization, Discoverer management, OracleApps R12/11i Module, Finance, SCM, MRP, ASCP, WIP, BOM, FA, AP, AR, OM, INV, AOL, MOAC, TCA structure, Project Accounting, CM, Functional,Oracle DBA, ERP, Techno-functional, OAF, Oracle Apps Interview Question and Error in Oracle apps R12/11i. For More Information Visit on www.OracleAppsGuide.com Or Subscribe your email-id on OracleAppsGuide

What are the differences between system, extensible, and user lookup types in Oracle Apps R12?

2016-05-08T01:15:00.000+05:30

What are the differences between system, extensible, and user lookup types in Oracle Apps R12?

OR

Type of Lookups in Oracle Apps R12

User

Updating of the start date, end date, and enabled fields are allowed
Deletion of codes is allowed
Updating of the tag is allowed
Insertion of new codes is allowed

Extensible

Insertion of new codes is allowed

Updating of the start date, end date, enabled fields, and the tag is allowed only if the code is not 'seed data'

Deletion of codes is allowed only if the code is not 'seed data'

Updating of the module is not allowed

Deletion of lookup type is not allowed

System

Insertion of new codes is not allowed
Updating of the start date, end date, and enabled fields are not allowed
Deletion of codes is not allowed
Updating of the tag is not allowed
Updating of the module is not allowed
Deletion of lookup type is not allowed

For more details please click on HERE.

How can be add month in calendar or defining new fiscal year in oracle apps R12

2016-04-24T16:37:00.000+05:30

How can add a month in the calendar or defining new fiscal year in oracle apps R12

Or

How can add an Adjustment Period in Calendar

Go to General Ledger ,Vision Operation (USA) < Setup

Then Setup < Financials < Calendars < Accounting

Now Query (F11) "Accounting" then press Ctrl + F11

Now Go to File < New and add a new line Accordingly.

Fill all mandatory field as required.

Now Save

Finally, Your's Month added in Calendar.

Note -: Use the following Query to check the status of the Periods Details accordingly :

select a.period_name,

a.period_num,

a.gl_status,

b.po_status,

c.ap_status

from

(select period_name, period_num,

decode(closing_status,'O','Open',

'C','Closed',

'F','Future',

'N','Never',

closing_status) gl_status

from gl_period_statuses

where application_id = 101

and start_date >= '01-JAN-98

and end_date < '01-JAN-99'

and set_of_books_id = &&set_of_books_id) a,

(select period_name,

decode(closing_status,'O','Open',

'C','Closed',

'F','Future',

'N','Never',

closing_status) po_status

from gl_period_statuses

where application_id = 201

and start_date >= '01-JAN-15'

and end_date < '01-JAN-16'

and set_of_books_id = &&set_of_books_id) b,

(select period_name,

decode(closing_status,'O','Open',

'C','Closed',

'F','Future',

'N','Never',

closing_status) ap_status

from gl_period_statuses

where application_id = 200

and start_date >= '01-JAN-15'

and end_date < '01-JAN-16'

and set_of_books_id = &&set_of_books_id) c

where a.period_name = b.period_name

and a.period_name = c.period_name

order by a.period_num

How can Open Oracle Apps General Ledger , Inventory and Purchasing Modules Periods in Oracle Apps R12

2015-11-01T09:55:00.000+05:30

How can Open Oracle Apps General Ledger Period in Oracle Apps R12

Or

Step to Open Oracle Apps General Ledger Period in Oracle Apps R12

Note -: Whenever you do Receive inventory transactions, you often get errors if your Inventory/ purchasing/ GL periods are not open.

Here is the navigation where you can set up the periods for your material receipts:

Go to

Setup > Financial > Accounting > Open and Close periods

-OR-

Setup > Open and Close periods

Click On Open/Close

Select Ledger Name and Period Accordingly

Click On Open Periods

Choose Target Period

Once Check the Concurrent Program Status.

Now Your's General Ledger Period Opened. Ensure that the GL Period has Open status.

How can Open Oracle Apps Inventory Period in Oracle Apps R12

Or

Step to Open Oracle Apps Inventory Period in Oracle Apps R12

Go to

Inventory > Accounting close cycle > Inventory Accounting Periods

Choose Respective Inventory Organization

Click on Change Status then OK

Now Your's Inventory Period Opened.

How can Open Oracle Apps Purchasing Period in Oracle Apps R12

Or

Step to Open Oracle Apps Purchasing Period in Oracle Apps R12

Here is the navigation where you can set up the periods

Go to

Setup > Financial > Accounting > Control Purchasing Period

Then

Choose Fiscal Year or Period Name accordingly

Change Periods Status as "Open"

Save

Now Your's Purchasing Period Opened. Ensure that the Purchasing Period has Status Open

"How can Open Oracle Apps General Ledger, Inventory and Purchasing Modules Periods in Oracle Apps R12"

Link Between AP(Account Payable),GL(General Ledger) and SLA(Sub Ledger Accounting _XLA)

2015-07-10T01:12:00.000+05:30

Complete relation Query for SLA(Sub Ledger Accounting _XLA), AP(Account Payable) and GL(General Ledger) Links in oracle apps r12

Link Between AP(Account Payable), GL(General Ledger) and SLA(Sub Ledger Accounting _XLA)

SELECT DISTINCT GJH.PERIOD_NAME, TRUNC (GJH.CREATION_DATE) GL_DATE,

GJH.JE_SOURCE, GJH.JE_CATEGORY, GJH.CURRENCY_CODE,

GJL.DESCRIPTION, GJL.REFERENCE_5, GJL.REFERENCE_10,

GJL.ACCOUNTED_CR, GJL.ACCOUNTED_DR, GJL.EFFECTIVE_DATE,

GJL.REFERENCE_1, GCC.SEGMENT1, GCC.SEGMENT2, GCC.SEGMENT3,

GCC.SEGMENT4, GCC.SEGMENT5, GCC.SEGMENT6, GCC.SEGMENT7,

AERLA.JUSTIFICATION, AERLA.PROJECT_NUMBER,

AERLA.EXPENDITURE_ITEM_DATE, AERLA.RECEIPT_CURRENCY_CODE

FROM APPS.GL_JE_HEADERS GJH,

APPS.GL_JE_LINES GJL,

APPS.GL_CODE_COMBINATIONS GCC,

APPS.GL_IMPORT_REFERENCES GIR,

APPS.XLA_AE_LINES XAL,

APPS.XLA_AE_HEADERS XAH,

APPS.AP_INVOICES_ALL AIA,

APPS.AP_INVOICE_LINES_ALL AILA,

APPS.AP_INVOICE_DISTRIBUTIONS_ALL AIDA,

APPS.AP_EXPENSE_REPORT_HEADERS_ALL AERHA,

APPS.AP_EXPENSE_REPORT_LINES_ALL AERLA

--APPS.XLA_EVENTS XE,

--XLA.XLA_TRANSACTION_ENTITIES XTE,

--APPS.XLA_DISTRIBUTION_LINKS XDL,

WHERE GJH.JE_HEADER_ID = GJL.JE_HEADER_ID

AND GJL.CODE_COMBINATION_ID = GCC.CODE_COMBINATION_ID

AND GJL.JE_HEADER_ID = GIR.JE_HEADER_ID

AND GJL.JE_LINE_NUM = GIR.JE_LINE_NUM

AND GIR.GL_SL_LINK_ID = XAL.GL_SL_LINK_ID

AND GIR.GL_SL_LINK_TABLE = XAL.GL_SL_LINK_TABLE

AND XAL.APPLICATION_ID = XAH.APPLICATION_ID

AND AIA.INVOICE_ID = AILA.INVOICE_ID

AND AIA.INVOICE_ID = AIDA.INVOICE_ID

AND AILA.LINE_NUMBER = AIDA.DISTRIBUTION_LINE_NUMBER

AND AERHA.REPORT_HEADER_ID = AERLA.REPORT_HEADER_ID

AND AIA.INVOICE_ID = AERHA.VOUCHNO

AND AIDA.INVOICE_LINE_NUMBER = AERLA.DISTRIBUTION_LINE_NUMBER

AND AIDA.ACCOUNTING_EVENT_ID = XAH.EVENT_ID

AND XAL.AE_HEADER_ID = XAH.AE_HEADER_ID

AND ( GJH.JE_SOURCE = 'Payables'

AND GJH.JE_CATEGORY = 'Purchase Invoices'

)

AND GJH.CURRENCY_CODE = 'INR'

--AND XAH.EVENT_ID=XE.EVENT_ID

--AND XAH.APPLICATION_ID=XE.APPLICATION_ID

--AND XE.ENTITY_ID=XTE.ENTITY_ID

--AND XE.APPLICATION_ID=XTE.APPLICATION_ID

--AND XTE.SOURCE_ID_INT_1=AIA.INVOICE_ID

--AND XAH.APPLICATION_ID=XTE.APPLICATION_ID

--AND XAH.ENTITY_ID=XTE.ENTITY_ID

--AND XDL.APPLICATION_ID=XAH.APPLICATION_ID

--AND AIDA.INVOICE_DISTRIBUTION_ID=XDL.SOURCE_DISTRIBUTION_ID_NUM_1

--AND XDL.AE_HEADER_ID=XAH.AE_HEADER_ID

--AND XE.EVENT_ID=AIDA.ACCOUNTING_EVENT_ID

--AND AERHA.INVOICE_NUM LIKE '%12345%'

--AND GJH.PERIOD_NAME = 'AUG-15'

FND (Foundation) Basic Table Name in Oracle Apps R12

2015-07-10T01:09:00.000+05:30

FND (Foundation) Basic Table Name in Oracle Apps R12

Basic Table List -:

FND_USER
FND_MENUS
FND_FORM_FUNCTIONS

FND_APPLICATION

FND_APPLICATION_TL

FND_CONCURRENT_PROGRAMS

FND_CONCURRENT_PROGRAMS_TL

FND_CONCURRENT_QUEUES

FND_CONCURRENT_QUEUES_TL

FND_CONCURRENT_QUEUE_CONTENT

FND_CONCURRENT_QUEUE_PARAMS

FND_CONCURRENT_QUEUE_SIZE

FND_CONCURRENT_REQUESTS

FND_CONCURRENT_REQUEST_CLASS

FND_CONCURRENT_TIME_PERIODS

FND_CONC_PP_TEMPLATES_TL

AP, AR, GL, INV, PA, FA, PO, TCA, Workflow - Interface and Base table in Oracle Apps R12

2015-07-05T17:36:00.000+05:30

Main Interface and Base table in Oracle Apps R12

GL Module (General Ledger Module tables in Oracle Apps R12)
Interface Table	Base Table
gl_interface gl_budget_interface	gl_je_batches gl_je_headers gl_je_lines gl_je_sources gl_je_categories gl_sets_of_books gl_daily_rates gl_balances gl_periods gl_period_sets gl_code_conbinations

AR Module (Account Receivable Module tables in Oracle Apps R12)
Interface Table	Base Table
ra_customers_interface_all ra_contact_phones_int_all ra_customer_profiles_int_all	hz_parties hz_cust_accounts hz_cust_acct_sites_all hz_cust_sit_use_all hz_party_sites hz_locations hz_party_site_uses hz_customer_profiles hz_organization_profiles hz_person_profiles

ra_interface_lines_all ra_interface_distributions_all ra_interface_salescredits_all	ra_customer_trx_all ra_customer_trx_lines_all ra_cust_trx_line_gl_dist_all ra_cust_trx_types_all ar_payment_schedules_all ra_batch_sources_All ar_vat_tax_all ra_terms ar_periods ar_period_types

OM Module (Order Management Module tables in Oracle Apps R12)
Interface Table	Base Table
oe_headers_iface_all oe_lines_iface_all oe_actions_iface_all	oe_order_headers_all oe_order_lines_all oe_order_sources oe_transaction_types_tl oe_transaction_types_all

INV Module (Inventory Module tables in Oracle Apps R12)
Interface Table	Base Table
mtl_system_items_interface mtl_item_categories_interface mtl_item_revisions_interface mtl_interface_errors	mtl_system_items_b mtl_system_items_tl mtl_item_locations mtl_item_categories mtl_item_revisions_b mtl_parameters hr_all_organizations_units cst_item_costs qp_list_headers jft_rs_salesreps

Workflow Tables tables in Oracle Apps R12
Interface Table	Base Table
	wf_items wf_process_activities wf_item_activity_statuses wf_item_types_tl

PO Module (Purchase Order tables in Oracle Apps R12)
Interface Table	Base Table
*PO REQUISITIONS* po_requistitions_interface_all po_req_dist_interface_all *PURCHASE ORDERS* po_headers_interface po_lines_interface po_distributions_interface	*PO VENDORS* po_vendors po_vendor_sites_all po_vendor_contacts *PO REQUISITIONS* po_requisition_headers_all po_requisition_lines_all po_req_distributions_all *PURCHASE ORDERS* po_headers_all po_lines_all po_line_locations_all po_distributions_all

AP Module (Account Payables tables in Oracle Apps R12)
Interface Table	Base Table
ap_invoices_interface ap_invoice_lines_interface	ap_invoices_all ap_invoice_distributions_all ap_payments_schedules_all

FA Module (Fixed Asset tables in Oracle Apps R12)
Interface Table	Base Table
fa_inv_interface fa_production_interface fa_mass_additions	fa_additions_b fa_additions_tl fa_books fa_deprn_summary fa_deprn_details fa_deprn_history fa_retirements

PA Module (Project Accounting in Oracle Apps R12)
Interface Table	Base Table
	pa_tasks pa_expenditure_items_all pa_expenditures_all pa_transaction_constrols pa_projects_all pa_budget_versions pa_resource_assigments

TCA Architecture (Trading Community Architecture tables in Oracle Apps R12)
Interface Table	Base Table
	hz_parties hz_cust_accounts hz_cust_acct_sites_all hz_cust_sit_use_all hz_party_sites hz_locations hz_party_site_uses hz_customer_profiles hz_organization_profiles hz_person_profiles

“A GUIDE FOR ORACLE E-BUSINESS SUITE” –A complete Solution and Learning platform For Oracle Apps R12/11i, Training, India Localization, Technical, P2P, O2C, Drop-shipment, AR/AP Cycle, Implementation, Bug or error in Oracle Apps R12/11i, Up-gradation, Support, Alert, Personalization, Discoverer management, OracleApps R12/11i Module, Finance, SCM, MRP, ASCP, WIP, BOM, FA, AP, AR, OM, INV, AOL, MOAC, TCA structure, Project Accounting, CM, Functional, Oracle DBA, ERP, Techno-functional, OAF, Oracle Apps Interview Question and Error in Oracle apps R12/11i. For More Information Visit on www.OracleAppsGuide.com Or Subscribe your email-id on OracleAppsGuide

Setup Step for ECO Cycle (Engineering Change Order) in Oracle Apps

2015-07-04T22:03:00.000+05:30

Setup step for ECO Cycle (Engineering Change Order) in Oracle Apps

Defining ECO Types

Defining ECO Autonumbering

Defining ECO Priorities

Defining ECO Reasons

Defining ECO Approval Lists

Starting the Auto Implement Manager

Engineering Profile Options and Security Functions

Defining Engineering Change Orders

Creating an ECO
Viewing ECO Approval Status
Rescheduling an ECO or Revised Items
Changing the ECO Status
Defining Implementation Costs
Defining an ECO Revision
Defining ECO Revised Items
Viewing ECO Schedule History
Defining Revised Components
Viewing Item Revisions
Assigning or Deleting Substitute Components
Assigning Reference Designators
Attaching Files to ECOs
Engineering Change Orders Field

ECO Statuses

ECO Revised Item Statuses
ECO Approval Statuses
Disposition Field

ECO Reports in Oracle Apps

Engineering Change Order Approval Lists Report

Engineering Change Order Detail Report

Engineering Change Order Priorities Report

Engineering Change Order Reasons Report

Engineering Change Order Schedule Report

“A GUIDE FOR ORACLE E-BUSINESS SUITE” –A complete Solution and Learning platform For Oracle Apps R12/11i, Training, India Localization, Technical, P2P, O2C, Drop-shipment, AR/AP Cycle, Implementation, Bug or error in Oracle Apps R12/11i, Up-gradation, Support, Alert, Personalization, Discoverer management, OracleApps R12/11i Module, Finance, SCM, MRP, ASCP, WIP, BOM, FA, AP, AR, OM, INV, AOL, MOAC, TCA structure, Project Accounting, CM, Functional,Oracle DBA, ERP, Techno-functional, OAF, Oracle Apps Interview Question and Error in Oracle apps R12/11i. For More Information Visit on www.OracleAppsGuide.com Or Subscribe your email-id on OracleAppsGuide

ECO Cycle (Engineering Change Order) in Oracle Apps

2015-07-04T21:42:00.000+05:30

ECO Cycle (Engineering Change Order) in Oracle Apps

Step 1- Go to the Engineering Change Order Responsibility

Step 2- Please Define the Engineering Change Order/Query

Step 3- Now Click on Revision Item

Step 4 - Save the Form.

Step 5 - Click on Tools and Release ECO (Engineering Change Order) Accordingly.

Note - You can Check by

SELECT * FROM APPS.ENG_REVISED_ITEMS

Step 5-: Now Implement ECO (Engineering Change Order)

Step 6-: Now Go to View > Request > Find the "Engineering Change Order" Program.

Error "You have exceeded the transaction quantity". Precision Restriction for Quantity Field Up To 6 Decimal Places Performing Lot Receipts (Doc ID 464983.1)

2015-06-21T04:14:00.000+05:30

Error "You have exceeded the transaction quantity".

Applies to:

Information in this document applies to any platform.

FORM:RCVRCERC.FMB - Enter Receipts GUI

FORM:RCVTXERT.FMB - Enter Receiving Transactions GUI

FORM:RCVTXERE.FMB - Enter Returns GUI

FORM:RCVTXECO.FMB - Enter Corrections GUI

"You have exceeded the transaction quantity"

Symptoms:

"You have exceeded the transaction quantity"

Note: Internal error message may indicate this message:

INV_QUANTITY_TOO_BIG

Steps:

Go to Receiving Screen
Enter the qty like 7200.00000489 (6 digits restriction makes it 7200.000005)
Go to Lot/Serial form
Enter lot number and qty as 7200.00001 (which was rounded to 5 digits)
The message "you have exceeded the transaction quantity "

Cause Can Be-:

a) Restriction of precision support up to 6 decimal places was added for the quantity field

b) Comparing the transaction qty entered in receiving forms and the lot quantity entered in lot-entry form after rounding to 5 decimal precision.

Quantity Precision support from now on will be as follows:

Receiving supports unlimited precision in Receiving forms.

Core Inventory's lot entry block still supports only 5 decimal precision.

Important: The revised Quantity Precision support affects any quantities entered in all of the receiving forms (not just LOT based items).

Solution:

To implement the solution, please execute the following steps:

1. Download and review the readme for Patch 5880504

2. Apply Patch 5880504 on a non-Production instance

3. Confirm the following file version:

$AU_TOP/resource/RCVRCERL.plx 115.157.11510.45

$AU_TOP/resource/RCVTXECO.plx 115.67.11510.20

$AU_TOP/resource/RCVTXERT.plx 115.110.11510.22

$PO_TOp/forms/US/RCVTXERE.fmb 115.79.11510.9

You can use the commands like the following:

strings -a $AU_TOP/resource/RCVRCERL.plx | grep 'Header:'

4. Retest the issue

5. If the issue is resolved, migrate the solution as appropriate to other instances

References:

BUG:6000073 - RECEIVING, INVENTORY, AND PO SHOULD ALL SUPPORT 15 DECIMAL PRECISION

BUG:7626008 - DECIMAL POSITIONS NOT CONSISTENT ON RCV FORMS; CANNOT RETURN SMALL QTY

BUG:5880504 - ON-DEMAND: OUT TO 9-10 DECIMAL PLACES, RECEIVING TRANSACTIONS ROUNDING ONLY TO 5

Note- All Reference Taken from Oracle Forum and manipulate than to make better understandable for Oracle Apps Technical and Oracle Apps Functional Developer.

“A GUIDE FOR ORACLE E-BUSINESS SUITE” – A complete Solution and Learning platform For Oracle Apps R12/11i, Training, India Localization, Technical, P2P, O2C, Drop-shipment, AR/AP Cycle, Implementation, Bug or error in Oracle Apps R12/11i, Up-gradation, Support, Alert, Personalization, Discoverer management, OracleApps R12/11i Module, Finance, SCM, MRP, ASCP, WIP, BOM, FA, AP, AR, OM, INV, AOL, MOAC, TCA structure, Project Accounting, CM, Functional,Oracle DBA, ERP, Techno-functional, OAF, Oracle Apps Interview Question and Error in Oracle apps R12/11i. For More Information Visit on www.OracleAppsGuide.com Or Subscribe your email-id on OracleAppsGuide.

Resolving Period Close Pending Transaction R12 or Inventory Closing Steps in Oracle Apps R12

2015-06-13T00:10:00.000+05:30

Resolving Period Close Pending Transaction R12 (Doc ID 1069492.1)

APPLIED ON:-

Oracle Cost Management - Version 12.0.0 and later

Oracle Shipping Execution - Version 12.0.0 and later

Oracle Purchasing - Version 12.0.0 and later

Oracle Work in Process - Version 12.0.0 and later

Oracle Inventory Management - Version 12.0.0 and later

PURPOSE:-

Troubleshooting Pending Transactions

TROUBLESHOOTING STEPS:-

1 -: VIEWING PENDING TRANSACTIONS

2-: UNPROCESSED MATERIAL TRANSACTIONS

3-: Uncosted Material/WSM Transactions

4-: Pending WIP Costing transactions

5-: Pending WSM interface

6-: Pending LCM Interface Transactions

Resolution Recommended Transactions

1-: Pending Receiving Transactions

2-: Pending Material Transactions

3-: Pending Shop Floor Move

4-: UNPROCESSED SHIPPING TRANSACTIONS

Conclusion:

The key steps to resolving pending transactions are:

-Locate the transactions
-Find the error message to determine what is preventing the transactions from processing.
-Resolve the error
-Resubmit the pending record.

If transactions are pending but not in error the transaction will need to be resubmitted via an SQL statement.

For More Information Visit on www.OracleAppsGuide.com Or Subscribe your email-id on OracleAppsGuide

Ref -: Oracle Doc (Doc ID 1069492.1)

Disclaimer - In this Post, All Contents are taken from Oracle Knowledge and SR experience here we arraigned and make understandable according to Developer.

“A GUIDE FOR ORACLE E-BUSINESS SUITE” – A complete Solution and Learning platform For Oracle Apps R12/11i, Training, India Localization, Technical, P2P, O2C, Drop-shipment, AR/AP Cycle, Implementation, Bug or error in Oracle Apps R12/11i, Up-gradation, Support, Alert, Personalization, Discoverer management, OracleApps R12/11i Module, Finance, SCM, MRP, ASCP, WIP, BOM, FA, AP, AR, OM, INV, AOL, MOAC, TCA structure, Project Accounting, CM, Functional,Oracle DBA, ERP, Techno-functional, OAF, Oracle Apps Interview Question and Error in Oracle apps R12/11i. For More Information Visit on www.OracleAppsGuide.com Or Subscribe your email-id on OracleAppsGuide.

UNPROCESSED SHIPPING TRANSACTIONS(Resolving Period Close Pending Transaction R12 or Inventory Closing Steps in Oracle Apps R12)

2015-06-13T00:02:00.000+05:30

UNPROCESSED SHIPPING TRANSACTIONS

To resolve unprocessed shipping transactions, you need to determine and fix the shipping transactions that are in a status of shipped, BUT not interface to Order Management or Inventory, in the WSH_DELIVERY_DETAILS table. Details of the Shipping transactions in a status of shipped can be viewed through the application by navigating to the Transaction screen through Order Management and quarrying on the status 'Shipped' and the Date of a period:

Order Management > Shipping > Transactions

The Shipping Transactions window provides a consolidated workbench for three major shipping functions: planning, pick releasing, and ship confirming. It enables you to plan and manage trips, stops, deliveries, delivery lines, and LPNs. There are four tabs to select they type of information: Trips, Stops, Contents by Delivery, Contents by Line/Lpn.

Transactions that are in a in a status of 'Shipped' have been shipped confirmed but have not yet been interfaced to Oracle Inventory. These must be processed and resolved before the period is closed. The concurrent process "Order Management Interface" and the concurrent process "Inventory Interface" populate Inventory Interface and Order Management Interface and upon completing successfully the status of the line changes to "Invoice Eligible". These concurrent processes can be submitted through the applications by navigating to:

Order Management > Shipping > Interface > Run

Run the Order Management Interface-SRS first then the Inventory Interface-SRS. These concurrent processes can be submitted by Trip Stop. The Trip Stop of the pending shipping transaction can be found in the Shipping Transactions window under the Stops tab in the Trip column. Reviewing the log file will supply an error message if the concurrent process does not complete successfully.

For More Information Visit on www.OracleAppsGuide.com Or Subscribe your email-id on OracleAppsGuide

Ref -: Oracle Doc (Doc ID 1069492.1)

Pending Shop Floor Move(Resolving Period Close Pending Transaction R12 or Inventory Closing Steps in Oracle Apps R12)

2015-06-12T23:56:00.000+05:30

Pending Shop Floor Move

Resolving unprocessed Move Transactions is a process of determining and fixing what is preventing a record from being processed through the WIP_MOVE_TXN_INTERFACE table. Details of pending move transactions can be viewed through the applications by navigating to the pending move transactions form:

WIP > Move Transactions > Pending Move Transactions

Through the Pending Move Transactions window, you can view, update, delete, and resubmit Move transaction records that have failed validation and remain in the Open Move Transaction Interface table (WIP_MOVE_TXN_INTERFACE). You can also resubmit transactions whose concurrent process has failed and had a processing phase of Complete and process status of Error. You can view error messages associated with failed records. Error messages can assist you in updating failed records before resubmission.

There are seven tabs to select information on the move transaction; Processing, Source, Concurrent Request, Job or Schedule Name, Operations, Transactions, Comments, and Scrap Account which provide detailed information to help you resolve pending move transactions.

Fields Common to all Tabs:

Resubmit(checkBox), When Checked and saved the erred transaction line will be resubmitted, if the line is not in error it can not be resubmitted using the Submit checkbox but will have to be resubmitted through a sqlplus script.
Transactions Id, Transaction Identifier
Errors(button), The error details of an erred transactions can be viewed by selecting the transaction and then clicking on the Errors button. Column indicates the name of the column in the wip move transaction interface that failed validation. The message indicates why the transactions failed.

Fields in Source Tab:

Source Code, Code of the shop floor control system that generated the transaction record (null if created by Oracle Work in Process)
Source Line, Identifier used by source shop floor control system (null if created by Oracle Work in Process)
Created By, the User name of the person who created the record

Fields in Concurrent Request:

Request ID, Line item's request ID
Phase, Transaction processing phase
Status, Transaction processing status
Message, Concurrent Message

Fields in Job or Schedule Name:

Organization, Organization code
Job or Schedule Name, WIP job or repetitive assembly name
Line, Line name
Assembly, Inventory item Identifier for the assembly the job or schedule creates

Fields in Operations Tab:

From Operation, Operation the move is from
Seq, From operation sequence number
Department, From department code
Step, From intra-operation step

To Operation, Operation the move is to
Seq, To operation sequence number
Department, To department code
Step, To intra-operation step

Fields in Transaction Tab:

UOM, Unit of measure used in the transaction
Quantity, Transaction quantity (between operations)
Overcompletion Quantity, Overcompletion quantity specified in the transaction UOM
Date, Transaction date
Type, Transaction type

Fields in Comments and Scrap Account Tab:

Reason, Standard transaction reason name
Reference, Transaction reference descriptive text
Scrap Account, General Ledger account charged when the material is scrapped

Erred transactions will have the Transactions ID and Group ID populated and the Status will be 'Error'. Pending transactions will have the Transactions ID and Group Id fields blank and the Status will be 'Pending'.

Resubmitting Failed Move Transactions:

In the Pending Move Transactions window, either check the transaction's Resubmit checkbox to resubmit one record or choose Select All from the Special Menu. Now save your work. The records can also be resubmitted using the following SQL statement:

Update WIP_MOVE_TXN_INTERFACE

Set GROP_ID = NULL,

TRANSACTIONS_ID = NULL,

PROCESS_STATUS = 1

Where TRANSACTION_ID = <&TRANSACTION_ID>;

When you resubmit a record, the system nulls the Transactions ID, Group ID and changes the processing status to 'Pending'.

Deleting Pending Move Transactions Records:

To delete pending move transactions, in the Pending Move Transactions window, select the transaction to choose Delete from the Edit Menu. You can delete failed records that have a processing status of Error regardless of their processing phase. When you delete transaction records, their corresponding error messages are also deleted.

Records in a BackFlush setup phase; If there is a failure in the Backflush setup phase, there will be a record in WIP_MOVE_TXN_INTERFACE and a corresponding record in WIP_MOVE_TRANSACTIONS. Records left in WIP_MOVE_TXN_INTERFACE with process_phase 3 should not be deleted. Backflush processing will never happen if these records are deleted, leading to data corruption.

For More Information Visit on www.OracleAppsGuide.com Or Subscribe your email-id on OracleAppsGuide

Ref -: Oracle Doc (Doc ID 1069492.1)

Pending Material Transactions(Resolving Period Close Pending Transaction R12 or Inventory Closing Steps in Oracle Apps R12)

2015-06-12T23:47:00.000+05:30

Pending Material Transactions

Resolving Pending Material Transactions is a process of determining and fixing what is preventing a record from being processed through the MTL_TRANSACTIONS_INTERFACE table. Details of pending transactions can be viewed through the application by navigating to the Transaction Open Interface form:

Inventory > Transactions > Transaction Open Interface

Using the Transaction Open Interface window, you can view, edit, correct and resubmit transactions received through the open interface. There are four tabs to view information: Error, Location, Source, Intransit and Other which provide detailed information to help you resolved pending transactions. Select a tabbed region to display a type of information:

Error: Interface transaction error information.
Location: Interface transaction location information.
Source: Interface source information
Intransit: Interface in the transit shipping information.
Others: Miscellaneous header and costing information.

The Main Descriptive fields give detailed information on the type of transaction that the cursor is on:

Primary UOM, Transaction quantity in terms of the primary UOM of the item
Qty, Transaction quantity in the primary unit of measure
Date, Transaction Date
Item Description, Inventory item description
Error Explanation, Full explanation of the error that occurred when attempting to process the line item
Lot/Serial (Button), Used if the transaction is associated with a Lot or Serial Number
Submit (Box), When checked and saved the erred transaction line will be resubmitted, if the line is not in error it can not be resubmitted using the Submit checkbox but will have to be resubmitted through a SQL plus script. All erred transactions can be selected to be resubmitted by clicking on 'Tools' resubmit all.

Fields Common to all Tabs:

Item, Inventory item referenced by the line item.
Transaction Source Type, Source types of the transaction, such as WIP Job or Schedule.

Fields in the Erred Tabbed Region:

Error Code, Code describing the error on the last attempt to process the line item.
Error Explanation, Full explanation of the error that occurred when attempting to process the line item.
Header ID, Line item's transaction header ID.
Interface ID, Interface ID that is assigned by the external system to track a set of transactions through the Oracle Inventory transaction interface processor.
Lock Flag, Indicates if the row and its child rows are locked to update from other processes.
Process Flag, the Indicates whether the row has been successfully processed by the concurrent manager, is available for processing or processed with an error.
Request ID, Line item's request ID
Transaction Mode, Method used to process the line item, such as concurrent processing.

Fields in the Location Tabbed Region:

Locator, Locator referenced by the line item.
LPN, The LPN put away. This field will display if you have Oracle Warehouse Management installed, and you are working with a WMS enabled organization.
Org, Organization code of the organization referenced by the line item.
Name, Organization Name
Revision, Revision of the inventory item referenced by the line item.
Subinventory, Subinventory referenced by the line item.
Transaction Date, Date the transaction was entered for processing.
Transaction Quantity, Quantity of the transaction
Transaction UOM, Unit of measure used in the transaction.
Transfer Locator, Destination location.
Transfer Org, Organization code of the destination organization
Transfer Org Name, Organization name of the destination organization
Transfer Subinventory, Destination sub inventory.
Supplier, Supplier
Planning Org, Planning Organization Code

Source Tabbed Region:

Transaction Source, Source of the transaction, such as account number.
Distribution Account, Distribution account for the line item.
Reason Name, The transaction reason.
Source Code, Source of the transaction, such as account number
Source Line ID, User-entered line ID of the source code for the line item.
Transaction Action Name, The transaction action
Transaction Cost, Cost to process the transaction.
Transaction Reference, Reference text describing the transaction
Transaction Type, The transaction type.

Intransit Tabbed Region:

Containers, Number of containers in which the material is stored
Expected Arrival Date, Date you expected to receive the material at the destination organization
Freight Code, The freight carrier for the transfer
Shipment Number, Number uniquely identifying the item or items transferred
Transfer Cost, Cost to process the transfer
Transportation Account, General ledger account charged with the value entered in the Transportation Cost field
Transportation Cost, Cost to physically transfer the material, such as freight carrier charges
Waybill Airbill, The waybill or airbill number for the transfer

Others Tabbed Region:

Department, Oracle Work in Process department code for the line item
Employee Code, Employee who entered the transaction
Encumbrance Account, Account used by Oracle Purchasing to receive the item
Encumbrance Amount, Amount encumbered, reserved against funds when the purchase order or requisition was approved
Expenditure Org, The expenditure organization
Expenditure Type, The expenditure type.
Demand Source Header ID, Source of the demand for the line item, such as an account number.
Demand Source Delivery, Line item detail identifier of the demand source.
Demand Source Line, Line number from the demand source, such as Sales Order line number.
New Average Cost, Recalculated average unit cost for the item.
Operation Seq Number, Number associated with the job or schedule referenced by the line item
Percentage Change, Percentage used to update the item cost.
Project Number, The project number.
Source Project Number, The source project number.
Source Task Number, The source task number.
Task Number, The task number.
To Project Number, The to project number.
To Task Number, The to task number.
Transaction Source Delivery ID, Line item detail identifier of the demand source.
Transaction Source Line ID, User-entered line ID of the source code for the line item.
Value Change, Amount used to increment the current inventory value.

Resubmitting Pending Material Transactions

In the Transaction Interface window, check the Submit option next to the transactions you want to resubmit or choose Resubmit All. If you have many transactions to resubmit, use the Resubmit All button to select all transactions for processing and then selectively individual transaction you do not want to resubmit. Save your work to submit the transactions for processing.

The erred records can also be resubmitted via the following SQL statement:

Update MTL_TRANSACTIONS_INTERFACE

Set PROCESS_FLAG = 1,

LOCK_FLAG = 2,

TRANSACTION_MODE = 3,

ERROR_CODE = NULL

Where PROCESS_FLAG = 3;

The "Process transaction interface" is the manager that will launch the "Inventory transaction worker" to process the transactions in the MTL_TRANSACTIONS_INTERFACE table. If the error message in the Transactions Interface window is not clear reviewing the log file of the "Inventory transactions Worker" may provide more information that could help in resolving the error.

Note -: See note 148651.1 How to get Debug Information for Inventory Material Transactions

For More Information Visit on www.OracleAppsGuide.com Or Subscribe your email-id on OracleAppsGuide

Ref -: Oracle Doc (Doc ID 1069492.1)

Pending Receiving Transactions (Resolving Period Close Pending Transaction R12 or Inventory Closing Steps in Oracle Apps R12)

2015-06-12T23:39:00.000+05:30

Pending Receiving Transactions

Pending Receiving Transactions are transactions that have not processed through the RCV_TRANSACTIONS_INTERFACE table. These transactions can be viewed and deleted through the "Transaction Status Summary" form:

Purchasing > Receiving > Transactions Status Summary

A Find window will appear and to query all of the unprocessed transactions for that period select from the field Source Type 'All', from the Transactions Details tab input the start and completion dates of the period in question and click 'Find':

Using the Transaction Statuses window, pending transactions can be viewed and deleted. There are four tabs to select: Transactions, Details, Order Information and Outside Services.

The Main Descriptive fields give detailed information on the type of transaction that the cursor is on:

Receipt, Receipt number
Supplier, Source of the receipt
Description, Item description
Errors, Error message
Order, Order Number
Parent Type, Parent transaction type
Routing, Receiving routing name

Fields common to all Tabs:

Quantity, Transaction quantity
UOM, Primary unit of measure of the item

Fields in Details Tab:

Transaction Date, Date of transaction
Reason, Standard transaction reason identifier
Comments, Comments
Packing Slip, Packing slip number

Fields in Order Information Tab:
Order Type, Purchase order types
Order Num, Purchase order number
Rel, Purchase order release number
Line, Purchase order line number
Shipment, Purchase order shipment number
Supplier, Vendor
Customer, Customer
Qty Ordered, Ordered quantity
UOM, Ordered UOM
Due Date, Expected due date

Fields in Outside Services Tab:

Job/Schedule, WIP Job or Schedule name
Line, WIP line identifier
Operation Sequence, WIP operation sequence number within a routing
Department, WIP department name

Resolving Pending Receiving Transactions

In resolving Pending Receiving Transactions the status and quantity received of the actual purchase order of the receiving transaction should be reviewed. If after reviewing the Purchase Order if the status is closed or complete and the purchase order quantity is equal to the quantity received then most likely the Pending Receiving transaction is a duplicate. Duplicate transactions can be deleted through the "Transaction Status Summary" screen by clicking on the transaction line and then clicking on the delete icon.
For additional information review 'How To Remove Pending and Error Receiving Transactions from Transaction Status Summary (Doc ID 303544.1)'

If after reviewing the Purchase Order of the Pending Receiving Transactions it is determined that the transaction should be processed it is recommended that a new receipt is created and processed. The original Pending Receiving Transaction should be deleted through the "Transaction Status Summary" screen.

Receiving transactions are process through the RCV_TRANSACTIONS_INTERFACE table by submitting the "Receiving Transactions Processor"

For More Information Visit on www.OracleAppsGuide.com Or Subscribe your email-id on OracleAppsGuide

Ref -: Oracle Doc (Doc ID 1069492.1)

Pending LCM Interface Transactions (Resolving Period Close Pending Transaction R12 or Inventory Closing Steps in Oracle Apps R12 )

2015-06-12T23:33:00.000+05:30

Pending LCM Interface Transactions

To resolve pending Landed Cost Management (LCM) transactions you need to determine and fix what is preventing a record from being processed through the CST_LC_ADJ_INTERFACE table. Details of transactions can be viewed through the Applications by navigating to the Pending Landed Cost Adjustment form.

Cost Responsibility > View Transactions > Pending Landed Cost Adjustments

The Pending Landed Cost Adjustment Transactions window can be used to view pending landed cost adjustment transactions. You can also use this window to resubmit any erred pending adjustment transactions.

There are three tabs; Processing, Transaction, and Source, to view information on the pending records and an Errors button to view the error if the transactions are in error;

Fields common to all tabs;
Transaction Id, Unique landed cost transaction identifier

Fields in the Processing TAB:

Group Id, Landed cost adjustment processor group id
Phase, Process phase: 1-Pending, 2-Validated, 3-Errored
Status, Process status: 1-Pending, 2-Running

Fields in Transaction TAB:

Item, Inventory Item name
Item Description, Inventory Item description
Organization, Destination inventory organization
Transaction Date, Landed cost adjustment transaction date
Prior Landed Cost, Prior landed cost
New Landed Cost, New landed cost

Fields in the Source TAB:

Rcv Transaction, Parent receipt transaction for LCM shipment
PO Number, Purchase order number
PO Line Num, Purchase order line number
Receipt Number, Receipt number that the PO is received on
Receipt Line Number, Receipt line number the PO is received on

Resubmitting Pending Landed Cost Adjustment Transactions
Select the Resubmit checkbox for each erred transaction that you want to resubmit, and click save. You can also select the Resubmit checkboxes for all rows by clicking Tools > Select All for Resubmit.

For More Information Visit on www.OracleAppsGuide.com Or Subscribe your email-id on OracleAppsGuide

Ref -: Oracle Doc (Doc ID 1069492.1)

Pending WSM interface (Resolving Period Close Pending Transaction R12 or Inventory Closing Steps in Oracle Apps R12 )

2015-06-12T23:10:00.000+05:30

Pending WSM interface

To resolve transactions in the WSM interface, you need to determine and fix what is preventing a record from being processed through the WSM_SPLIT_MERGE_TXN_INTERFACE table.

The user inserts rows into WSM_SPLIT_MERGE_TXN_INTERFACE (WSMTI), WSM_STARTING_JOBS_INTERFACE (WSJI), and WSM_RESULTING_JOBS_INTERFACE (WRJI) tables. Transactions in WSMTI are joined with the transactions in WSJI and WRJI by the HEADER_ID column in these tables.

Errors and Validations:

Whenever any one-row errors out within a given group, the PROCESS_STATUS of the entire group is set to ERROR. But only the transactions that actually erred out will have the

ERROR_MESSAGE column containing the error message.

Errors and warnings, if any, will be written into the WSM_INTERFACE_ERRORS table. Appropriate messages will be given in the parent and child

interface tables to refer to WSM_INTERFACE_ERRORS table when there is an error.

Resubmitting Pending WSM Interface transactions:

To resubmit the erred transactions for processing, the user has to rectify the error and change the PROCESS_STATUS of the required transactions from 3

(ERROR) to 1 (PENDING). Launching the concurrent process Import WIP Lot Transactions (Navigation path; Responsibility, Shop Floor Management > Run Request > Import WIP Lot Transactions) will process the records in the WSM_SPLIT_MERGE_TXN_INTERFACE table by Group_id.

For More Information Visit on www.OracleAppsGuide.com Or Subscribe your email-id on OracleAppsGuide

Ref -: Oracle Doc (Doc ID 1069492.1)

Pending WIP Costing transactions (Resolving Period Close Pending Transaction R12 or Inventory Closing Steps in Oracle Apps R12 )

2015-06-12T23:00:00.000+05:30

Pending WIP Costing transactions

Resolving Pending WIP Cost transactions is a process of determining and fixing what is preventing a record form being processed through the WIP_COST_TXN_INTERFACE table. Details of pending transactions can be viewed through the applications by navigating to the pending resource transaction form.

WIP > Resource Transactions > Pending Resource Transactions

In the Pending Resource Transaction window, you can view, update and resubmit resource transactions that have failed validation and remain in the WIP_COST_TXN_INTERFACE table. You can also resubmit and delete transactions whose concurrent process has failed and have a processing phase of Complete and a process status of Error. There are seven tabs to select the type of information: Processing, Source, Concurrent Request, Job or Schedule Name, Operation, Resource, Transaction, Comments and Project Information which provide detailed information to help in resolving pending resource transactions.

Erred transactions will have the Transaction Id And Group ID populated and the Status will be "Error". Pending transactions will have the Transaction ID and Group ID fields blank and the Status will be "Pending".

To view error details for failed resource transactions, select the transaction and click on the [Error] button. The Pending Resource Transaction error window appears. Column indicates the name of the column in the resource transaction interface table (WIP_COST_TXN_INTERFACE) THAT FAILED VALIDATION.

Transaction ID, Transaction Identifier

Fields in Processing Tab:

Group Id, Transaction group identifier

Phase, the Transaction processing phase

Status, Transaction processing status

Fields in Source Tab:

Source Code, Code of the shop floor control system that generated the transaction record

Source Line, Identifier used by source shop floor control system

Created By, Username of person that created the record

Fields in Concurrent Request Tab:

Request ID, Request Id

Phase, the Transaction processing phase

Status, Transaction processing status

Message, Concurrent Message

Fields in Job or Schedule Name Tab:

Organization, Organization identifier

Job or Schedule Name, WIP job or repetitive assembly name

Line, WIP line identifier

Assembly, Inventory item identifier of assembly that job or schedule creates

Fields in Operation Name Tab:

Op Seq, Operation sequence number within a routing

Dept, Department Identifier

Res Seq, Resource sequence number

Name, Resource code

Type, Resource type

Employee Number, Employee number

Fields in Resource Tab:

Activity, Activity name

Charge Type, Method of charging the resource

PO Number, Purchase order Identifier that the receipt is against

Currency, Unique Identifier for the currency

Actual Rate, Actual rate of the resource

Fields in Transaction Tab:

UOM, Unit of measure used for the transaction

Quantity, Transaction quantity

Date, Date transaction was performed

Type, Transaction type

Fields in Comments Tab:

Reason, Standard transaction reason name

Reference, Transaction reference descriptive text

Fields in Project Information Tab:

Project Number, Project Identifier

Task Number, Project task Identifier

Resubmitting Failed or Pending Resource Transactions

In the Pending Resource Transactions window either check the transaction's Resubmit checkbox to resubmit one record or chose Select All for Resubmit from the Special Menu and selectively deselect individual transaction you do not want to resubmit, save your work. Erred transactions can also be resubmitted via the following SQL statement:

Update WIP_COST_TXN_INTERFACE

Set GROUP_ID = NULL,

TRANSACTION_ID = NULL,

REQUEST_ID = NULL,

PROCESS_STATUS = 1

Where PROCESS_STATUS = 3;

This will resubmit records in PROCESS_STATUS = 3 (Error), nulling out the transaction id, group id, and concurrent request id and change the process status to pending.

The "Cost Manager" is the manager that will launch the "Resource Cost Worker" (short name CMCCTW) or the "Overhead Cost Worker" (short name CMCOCW) to process the resource or resource overhead transactions in the WIP_COST_TXN_INTERFACE table.

For More Information Visit on www.OracleAppsGuide.comOr Subscribe your email-id on OracleAppsGuide

Ref -: Oracle Doc (Doc ID 1069492.1)

Uncosted Material/WSM Transactions (Resolving Period Close Pending Transaction R12 or Inventory Closing Steps in Oracle Apps R12)

2015-06-12T22:46:00.000+05:30

Uncosted Material/WSM Transactions

To resolve uncosted Material Transactions/WSM 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.

Cost > View Transactions > Material Transactions

In the find Parameter Window, the 'Transaction Dates' fields should be populated with the date range of the Period that is being closed and the 'Costed' field from the list of values should be populated with 'Error' or 'No'.

Logical Transaction- A Logical transaction is an accounting event that represents the financial transaction without the physical movement of goods. The Include Logical Transactions box should be checked if Logical Transactions have occurred in the Period.

Notes: By using the Material Transaction window, you can view and resubmit erred costed transactions.

Item Description, Inventory item description

Primary UOM, Transaction quantity in terms of the primary UOM of the item

Secondary UOM, The secondary unit of measure. If the item is under the dual unit of measure control, the secondary unit of measure and the secondary quantity populate automatically.

Primary Qty, Transaction quantity in terms of primary UOM of the item

Secondary Quantity, Quantity of this transaction in terms of the Secondary UOM

Date, Transaction date

Distributions button (to view distributions of costed transactions)

Lot/Serial button (Used the if the transaction is associated with a Lot or Serial number)

Fields common to all Tabs:

Item, Inventory item reference by the line item

Transaction UOM, Unit of measure used in the transaction

Transaction Quantity, Quantity of this transaction

Transaction ID, Displays the item, transfer transaction ID

Transaction Date, Date the transaction was entered for processing

Source Type, Source type of the transaction, such as WIP Job or Schedule

Source, Source of the transaction, such as account number

Transaction Type, Displays the transaction type

Fields in the Location Tab are as follows:

Subinventory, Subinventory referenced by the line items

Locator, Locator referenced by the line item

Location, If the transaction type is move order issue or issue to project, you can enter the ship to the organization.

Revision, Revision of the inventory item referenced by the line item

Transfer Subinventory, Destination subinventory

Transfer Locator, Destination Locator

Transfer Org, The Destination Organization

Owning Party, The third-party owner of the inventory.

Planning Party, The vendor that manages the inventory.

Supplier, Supplier

Primary Quantity, Transaction quantity in terms of primary uom of the item

Primary UOM, Transaction quantity in terms of the primary uom of the item

Secondary Quantity, Quantity of this transaction in terms of the Secondary UOM

Secondary UOM, Secondary unit of measure if the item is under dual of the unit of measure control.

Fields in the Intransit Tab are as follows:

Shipment Number, Shipment number for the line item

Waybill/Airbill, The waybill or airbill number for the transfer

Freight Code, Freight carrier for the transaction

Containers, Number of containers in which the material is stored for the transfer

Fields in the Reason, Reference Tab are as follows:

Reason, The transaction reason

Reference, Reference text describing the transaction

Costed, Indicates the costing status

Transferred to Projects, Indicates the transfer to cost status

Error Code, Code describing the error on the last attempt to process the line items

Error Explanation, Full explanation of the error that occurred when attempting to process the line item

Supplier Lot, Supplier lot number.

Source Code, Source of the transaction, such as account number.

Source Line ID, Line level transaction source id

Fields in the Transaction ID Tab are as follows:

Transfer Transaction ID, Transaction id of the opposing transfer transaction

Parent Transaction ID, Parent Transaction Identifier

Logical Transactions Created, Identifies records created by Create Deferred Logical Transactions concurrent request

Logical Transaction, A Logical transaction is an accounting event that represents the financial transaction between two operating units without the physical movement of goods.

Operating Unit, The legal entity

Organization, Organization the transaction occurred in

Transaction Header, Number used to group transactions in the concurrent manager

Receiving Transaction ID, Receiving transaction cross reference

Move Transaction ID, Move transaction cross reference

Completion Transaction ID, Completion transaction cross reference

Department Code, Oracle Work in Process department code for the line item

Operation Sequence, Operation sequence number within a routing

Source Project Number, the source project number

Source Task Number, the source task number

Project Number, the project number

Task Number, the task number

To Project Number, the to project number

To Task Number, the to task number

Expenditure Type, the expenditure type

Expenditure Org., the expenditure organization

Error Code, the code describing the error on the last attempt to process the line item

Error Explanation, a full explanation of the error that occurred when attempting to process the line item

Fields in the Transaction Type tab are as follows:

Transaction Action, the transaction action

The field in the Consumption Advice tab are as follows:

Revision, Revision of the inventory item referenced by the line item

From Owning Party, Transfer owning organization identifier

Creation Status, Consumption Status

Error Explanation, Error explanation

Resubmitting Uncosted Transactions:

In the Material Transactions Form transactions that are costed in error can be resubmitted by clicking on "Tools, Select All" and then clicking on "Tools, Submit all" or Submit the number of transactions found through the search criteria in the Find window.

"Material cost transaction worker" for a standard costing environment or the "Actual Cost Worker" for an average, FIFO, LIFO or perpetual costing environment.

Changing the de-bug profile options; 'MRP: Debug Mode' set to "Yes"

and

CST: Cost update debug level set to "Full" will provide more information in the log when set prior to the Cost Worker processing.

“A GUIDE FOR ORACLE E-BUSINESS SUITE” – A complete Solution and Learning platform For Oracle Apps R12/11i, Training, India Localization, Technical, P2P, O2C, Drop-shipment, AR/AP Cycle, Implementation, Bug or error in Oracle Apps R12/11i, Up-gradation, Support, Alert, Personalization, Discoverer management, OracleApps R12/11i Module, Finance, SCM, MRP, ASCP, WIP, BOM, FA, AP, AR, OM, INV, AOL, MOAC, TCA structure, Project Accounting, CM, Functional,Oracle DBA, ERP, Techno-functional, OAF, Oracle Apps Interview Question and Error in Oracle apps R12/11i. For More Information Visit on www.OracleAppsGuide.com Or Subscribe your email-id on OracleAppsGuide.

Ref -: Oracle Doc (Doc ID 1069492.1)

ORACLE APPS GUIDE

What is PO Module in Oracle Apps R12

What is PO Module in Oracle Apps R12? A Complete Guide

Introduction

Key Features of Oracle PO Module

Types of Purchase Orders in Oracle Apps R12

How the Purchase Order Process Works in Oracle R12

1. Requisition Creation

2. Purchase Order Creation

3. PO Approval Process

4. Supplier Confirmation & Dispatch

5. Goods Receipt & Inspection

6. Invoice Matching & Payment Processing

Key Tables Used in Oracle PO Module

Query to find Locked Object in Oracle Apps R12

How can find Locked Object in Oracle Apps R12 ?or How can find Locked object name and Oracle User name in Oracle Apps R12?

Query to find - Is an employer also a buyer or not in oracle Apps or How can check that employee is a buyer

Query to find Is an employee also a buyer or not In Oracle Apps R12?

Terminology Used in EBS Oracle Apps R12

What is Implementation, Upgradation, Migration, Reimplementation, Rollout, Support in terms of Oracle Apps R12

or

Difference between Implementation, Upgradation, Migration, Reimplementation, Rollout, Support in terms of Oracle Apps R12

How can make entry for "TNSNAMES.ORA" on the local host for Oracle Application (In Oracle Apps R12).

TNSNAMES.ORA entry to runs Oracle Application R12 at local Host OR TNS Entry steps to runs Oracle Application R12

Important -: Default setup for Oracle Vision Instance to connect database and Application

Top 35 SQL Interview Question asked in Oracle Apps Technical Interview or SQL TOP 35 Frequently asked question in Technical Interview

Top 35 SQL Interview Question asked in Oracle Apps R12 Technical Interview

or

SQL TOP 35 Frequently asked question in Technical Interview

Definition of Lookup in Oracle Apps R12 Or What is Lookup in Oracle Apps R12? Or What is the main purpose of lookups in Oracle Apps R12?

Definition of Lookup in Oracle Apps R12

Or

What is Lookup in Oracle Apps R12?

Or

What is the main purpose of lookups in Oracle Apps R12?

What are the differences between system, extensible, and user lookup types in Oracle Apps R12?

OR

Type of Lookups in Oracle Apps R12

What are the differences between system, extensible, and user lookup types in Oracle Apps R12?

What are the differences between system, extensible, and user lookup types in Oracle Apps R12? OR Type of Lookups in Oracle Apps R12

How can be add month in calendar or defining new fiscal year in oracle apps R12

How can add a month in the calendar or defining new fiscal year in oracle apps R12 Or How can add an Adjustment Period in Calendar

How can add a month in the calendar or defining new fiscal year in oracle apps R12

Or

How can add an Adjustment Period in Calendar

How can Open Oracle Apps General Ledger , Inventory and Purchasing Modules Periods in Oracle Apps R12

How can Open Oracle Apps General Ledger Period in Oracle Apps R12

Or

Step to Open Oracle Apps General Ledger Period in Oracle Apps R12

How can Open Oracle Apps Inventory Period in Oracle Apps R12

Or

Step to Open Oracle Apps Inventory Period in Oracle Apps R12

How can Open Oracle Apps Purchasing Period in Oracle Apps R12

Or

Step to Open Oracle Apps Purchasing Period in Oracle Apps R12

Link Between AP(Account Payable),GL(General Ledger) and SLA(Sub Ledger Accounting _XLA)

FND (Foundation) Basic Table Name in Oracle Apps R12

AP, AR, GL, INV, PA, FA, PO, TCA, Workflow - Interface and Base table in Oracle Apps R12

Main Interface and Base table in Oracle Apps R12

Setup Step for ECO Cycle (Engineering Change Order) in Oracle Apps

Setup step for ECO Cycle (Engineering Change Order) in Oracle Apps

Defining Engineering Change Orders

ECO Statuses

ECO Reports in Oracle Apps

ECO Cycle (Engineering Change Order) in Oracle Apps

Error "You have exceeded the transaction quantity". Precision Restriction for Quantity Field Up To 6 Decimal Places Performing Lot Receipts (Doc ID 464983.1)

Error "You have exceeded the transaction quantity".

Resolving Period Close Pending Transaction R12 or Inventory Closing Steps in Oracle Apps R12

UNPROCESSED SHIPPING TRANSACTIONS(Resolving Period Close Pending Transaction R12 or Inventory Closing Steps in Oracle Apps R12)

Pending Shop Floor Move(Resolving Period Close Pending Transaction R12 or Inventory Closing Steps in Oracle Apps R12)

Pending Material Transactions(Resolving Period Close Pending Transaction R12 or Inventory Closing Steps in Oracle Apps R12)

Pending Receiving Transactions (Resolving Period Close Pending Transaction R12 or Inventory Closing Steps in Oracle Apps R12)

Pending LCM Interface Transactions (Resolving Period Close Pending Transaction R12 or Inventory Closing Steps in Oracle Apps R12 )

Pending WSM interface (Resolving Period Close Pending Transaction R12 or Inventory Closing Steps in Oracle Apps R12 )

Pending WIP Costing transactions (Resolving Period Close Pending Transaction R12 or Inventory Closing Steps in Oracle Apps R12 )

Uncosted Material/WSM Transactions (Resolving Period Close Pending Transaction R12 or Inventory Closing Steps in Oracle Apps R12)

TNSNAMES.ORA entry to runs Oracle Application R12 at local Host
OR
TNS Entry steps to runs Oracle Application R12

What are the differences between system, extensible, and user lookup types in Oracle Apps R12?

OR

Type of Lookups in Oracle Apps R12

How can add a month in the calendar or defining new fiscal year in oracle apps R12

Or

How can add an Adjustment Period in Calendar