Skip to content

How To Use Source Line Transfer To Transfer Cost From One Asset Into Another Asset?

APPLIES TO:

Oracle Assets – Version 11.5.10.2 and later
Information in this document applies to any platform.

GOAL:

How to perform a source line transfer to transfer cost from one asset into another asset?

SOLUTION:

Perform the following steps:

1.  Query the “Transfer Out” asset in the Asset Workbench.  Navigate to Assets > Asset Workbench, query the asset number.
2.  Place the cursor in the record for the asset, then click the Source Lines button.
3.  In this form, check the line for the invoice, click the “Transfer To” button.
4.  In this form, do a blind query to find all the assets that this could be transferred to, or simply hit F11 to initiate the query.  Or enter query mode (f11), then key the desired “Transfer To” asset on the first line, then hit Ctrl+F11 to bring it back. Click Done to commit the Source Line Transfer to the asset.

Doc ID 1447559.1

This case just happened today, when 1 user was wrong Add new Invoice to an Asset Number. Lucky I have this document.

Xoxo,

Ann

Advertisements

Re-Assign Buyer

Hi,

To disable the function “Reassign To Buyer” from the Tools menu in Autocreate, please implement following steps.
I’ve already tested following steps in our internal instance and got the result as expected.

1. Navigate to Application Developer responsibility

2. Navigate to Application> Function

3. Query the function ‘PO_REASSIGN_BUYER’, e.g. F11> Enter PO_REASSIGN_BUYER> CTRL-F11

4. Go to Properties Tab

5. Select ‘Offline’ from Maintenance Mode Support LOV

6. Save changes

7. Check the result in Autocreate form

Thanks,
Eun Sil

SA: How to Add New Profile Options

Hi All,

This is the how-to to create new Profile Options:

http://webcache.googleusercontent.com/search?q=cache:nG-mtBqR2PcJ:oracleappsinfo-r12.blogspot.com/2015/02/steps-to-create-custom-profile-option.html+&cd=1&hl=te&ct=clnk&gl=in

Xoxo,
Anne

 

Applied Prepayment

Hello,

We had a prepayment cases, where user cannot applied standard invoice to a prepayment. The reason is simple, because the discarded flag is already stated Y. This is the script to udpate the data.

UPDATE AP_INVOICE_DISTRIBUTIONS_ALL
SET PARENT_REVERSAL_ID= null, reversal_flag = NULL, prepay_amount_remaining= &inv_amount
WHERE invoice_id = &Invoice_num;

UPDATE AP_INVOICE_LINES_ALL
SET DISCARDED_FLAG = ‘N’
WHERE invoice_id = &Invoice_num;

Commit;

Test again in the environment.

Regards,

Anne

Relation RCV – GL

The table that stores the receiving transactions from the RECEIPT is RCV_RECEIVING_SUBLEDGER. The DELIVERY portion is stored in MTL_MATERIAL_TRANSACTIONS (transaction) and MTL_TRANSACTION_ACCOUNTS (distributions).

You must run the Create Accounting – Receiving program from Purchasing to create the SLA entry for the Receipt, and the Create Accounting – Cost Management program from Cost Management to create the SLA entry for the delivery.

The entry for the receipt should be:

Inventory in Receiving Po price * qty
Uninvoiced Rcpt Liability PO price * qty

The entry for the delivery should be

Inventory in Stock std cost * qty
Inventory in Receiving PO price * qty
PO/Invoice variance var * qty (only if PO price is different from std cost)

The SLA information is stored in the following tables:

SLA_DISTRIBUTION_LINKS
there is a column in this table called SOURCE_DISTRIBUTION_ID_NUM1 which is the foreign key back to the original distribution from RCV_RECEIVING_SUBLEDGER

XLA_EVENTS
shares EVENT_ID with the table above

XLA_AE_HEADERS
shares EVENT_ID with the table above.

XLA_AE_LINES
shares AE_HEADER_ID with the table above

GL_IMPORT_REFERENCES
shares GL_SL_LINK_ID with table above

GL_JE_HEADERS
shares JE_HEADER_ID with table above.

If you do a join between all the tables above you can get from the receiving distribution to the SLA entry and from the SLA entry to the corresponding General Ledger entry.

SLA also has a number of good reports which show you what has not made it to General Ledger:

Subledger Period Close Exceptions Report
Journal Entries report (run with the status parameter set to “Not Transferred” to see SLA entries with no corresponding GL entry.

Share from: Andrea

Audit: Journal Data

Hi All,

This is as a reminder for journal data that our auditor always request each year. Here is the script:

/*begin
mo_global.set_policy_context (‘S’, 81);
end;*/

select glh.je_header_id,
gll.JE_LINE_NUM,
glh.doc_sequence_value,
glh.ledger_id,
glh.actual_flag,
— gll.JE_HEADER_ID,
gcc.SEGMENT3 account_number,
gll.ACCOUNTED_CR,
gll.ACCOUNTED_DR,
gcc.SEGMENT2 cost_center,
— gll.CODE_COMBINATION_ID,
gll.EFFECTIVE_DATE,
gll.PERIOD_NAME,
gll.CREATION_DATE,
gll.CREATED_BY PREPARER_ID,
— fu.USER_NAME CREATED_BY,
glh.je_source source_name,
gll.DESCRIPTION
— gcc.segment1||’-‘||gcc.segment2||’-‘||gcc.segment3||’-‘||gcc.segment4||’-‘||gcc.segment5||’-‘||gcc.segment6||’-‘||gcc.segment7 acc,
from gl_je_headers glh,
gl_je_lines gll,
gl_code_combinations gcc
where glh.JE_HEADER_ID = gll.JE_HEADER_ID
and gll.CODE_COMBINATION_ID = gcc.CODE_COMBINATION_ID
and to_char(gll.effective_date,’yyyymm’) between ‘201510’ AND ‘201512’
AND GLh.Actual_Flag = ‘A’
and glh.ledger_id = ‘1’
order by glh.JE_HEADER_ID;

Xoxo,

N

Encumbrance Q & A

Q: How to perform drilldown for Encumbrance shows as Obligation is Funds Inquiry ?

A:

Please run create accounting from Purchasing responsibility for the date ending the specific period
Set Transfer to Genera Ledger as Yes. This would move the data to general ledger and user can perform the
drilldown

Q: Is there any encumbrance period that user to need to open?

A:

There is no specific period open/close process for encumbrance
Periods opened for budget would be applied for encumbrance also

Q: How to know the table that store the encumbrance data ?

A:

Encumbrance is used by general ledger and sub ledgers purchasing and payables.
There is no single table and data would get populated in many tables
In general encumbrance data is populated in the below tables

PO_BC_DISTRIBUTIONS
XLA_AE_HEADERS
XLA_AE_LINES
GL_BC_PACKETS

Please review the section ‘Generation of Encumbrance Entries’ in the Note : 429105.1 : “Impact of R12 Design in Procure To Pay Accounting Flow”

Xoxo,
Ann