Fa mass additions (fa_addition_pub.do_addition)

Hi All,
I am working on Mass Addition interface. After successfull execution of fa_addition_pub.do_addition package.I got asset_id too..
output :-
S 0
SUCCESS
THID 167215
ASSET_ID 109950
ASSET_NUMBER 99339
But my issue is i am not able to get this data in fa_mass_addition table ...In which table this data is updated ?
How to get the data in Fa Mass Addition so that i can run 'post mass addition' to get status as posted..?
Your knowledge will be appreciable..
Thanks
Raman Sharma

FA_ADDITIONS_B table in the FA
but will u provide the script or review mine ..
/* Formatted on 2012/05/23 14:19 (Formatter Plus v4.8.8) */
DECLARE
-- CURSOR C1
-- IS
-- SELECT *
-- FROM MCB_FA_TABLE;
P_API_VERSION NUMBER;
P_INIT_MSG_LIST VARCHAR2 (200);
P_COMMIT VARCHAR2 (200);
P_VALIDATION_LEVEL NUMBER;
X_RETURN_STATUS VARCHAR2 (200);
X_MSG_COUNT NUMBER;
X_MSG_DATA VARCHAR2 (200);
P_CALLING_FN VARCHAR2 (200);
PX_ASSET_DIST_REC FA_API_TYPES.ASSET_DIST_REC_TYPE;
PX_TRANS_REC FA_API_TYPES.TRANS_REC_TYPE;
PX_DIST_TRANS_REC FA_API_TYPES.TRANS_REC_TYPE;
PX_ASSET_HDR_REC FA_API_TYPES.ASSET_HDR_REC_TYPE;
PX_ASSET_DESC_REC FA_API_TYPES.ASSET_DESC_REC_TYPE;
PX_ASSET_TYPE_REC FA_API_TYPES.ASSET_TYPE_REC_TYPE;
PX_ASSET_CAT_REC FA_API_TYPES.ASSET_CAT_REC_TYPE;
PX_ASSET_HIERARCHY_REC FA_API_TYPES.ASSET_HIERARCHY_REC_TYPE;
PX_ASSET_FIN_REC FA_API_TYPES.ASSET_FIN_REC_TYPE;
PX_ASSET_DEPRN_REC FA_API_TYPES.ASSET_DEPRN_REC_TYPE;
PX_ASSET_DIST_TBL FA_API_TYPES.ASSET_DIST_TBL_TYPE;
PX_INV_TBL FA_API_TYPES.INV_TBL_TYPE;
LV_COUNT NUMBER := 1;
L_MESG_COUNT VARCHAR2 (2000);
L_MESG VARCHAR2 (2000);
L_RETURN_STATUS VARCHAR2 (2000);
PX_INV_RATE_TBL FA_API_TYPES.INV_RATE_TBL_TYPE;
PX_INV_REC FA_API_TYPES.INV_REC_TYPE;
PX_INV_TRANS_REC FA_API_TYPES.INV_TRANS_REC_TYPE;
BEGIN
BEGIN
FA_SRVR_MSG.INIT_SERVER_MESSAGE;
FND_MSG_PUB.INITIALIZE;
END;
P_API_VERSION := 1.0;
P_INIT_MSG_LIST := FND_API.G_FALSE;
P_COMMIT := FND_API.G_FALSE;
P_VALIDATION_LEVEL := FND_API.G_VALID_LEVEL_FULL;
X_RETURN_STATUS := L_RETURN_STATUS;
X_MSG_COUNT := L_MESG_COUNT;
X_MSG_DATA := L_MESG;
P_CALLING_FN := NULL;
PX_ASSET_DESC_REC------------------------------------------------------
PX_ASSET_DESC_REC.ASSET_NUMBER := 'XPRIA1100'; ---FA.ASSET_NUMBER;
PX_ASSET_DESC_REC.DESCRIPTION := 'Xperia Mobile'; ---FA.DESCRIPTION;
PX_ASSET_DESC_REC.ASSET_KEY_CCID := 2; ---FA.ASSET_KEY;
PX_ASSET_DESC_REC.TAG_NUMBER := NULL; ---FA.TAG_NUMBER;
PX_ASSET_DESC_REC.SERIAL_NUMBER := NULL; ---FA.SERIAL_NUMBER;
PX_ASSET_DESC_REC.MANUFACTURER_NAME := NULL; ---FA.MANUFACTURER_NAME;
PX_ASSET_DESC_REC.MODEL_NUMBER := NULL; ---FA.MODEL_NUMBER;
PX_ASSET_DESC_REC.IN_USE_FLAG := 'YES'; ---FA.IN_USE_FLAG;
PX_ASSET_DESC_REC.INVENTORIAL := 'YES'; ---FA.INVENTORIAL;
PX_ASSET_DESC_REC.OWNED_LEASED := 'OWNED'; --FA.OWNED_LEASED;
PX_ASSET_DESC_REC.NEW_USED := 'NEW'; ---FA.NEW_USED;
PX_ASSET_DESC_REC.CURRENT_UNITS := '10'; ---FA.CURRENT_UNITS;
PX_ASSET_CAT_REC-------------------------------------------------------
PX_ASSET_CAT_REC.CATEGORY_ID := 21; ---FA.CATEGORY_ID;
PX_ASSET_CAT_REC.DESC_FLEX.ATTRIBUTE1 := NULL; ---FA.ATTRIBUTE1;
PX_ASSET_CAT_REC.DESC_FLEX.ATTRIBUTE2 := NULL; ---FA.ATTRIBUTE2;
PX_ASSET_CAT_REC.DESC_FLEX.CONTEXT := 'COMPUTER-PC'; ---FA.CONTEXT;
PX_ASSET_FIN_REC.COST := 2400; ---FA.COST;
PX_ASSET_FIN_REC.ORIGINAL_COST := 2400; ---FA.ORIGINAL_COST;
PX_ASSET_FIN_REC.SALVAGE_VALUE := NULL; ---FA.SALVAGE_VALUE;
PX_ASSET_FIN_REC.DATE_PLACED_IN_SERVICE := SYSDATE; --- FA.DATE_PLACED_SRV;
PX_ASSET_FIN_REC.DEPRECIATE_FLAG := NULL; ---FA.DEP_FLAG;
PX_ASSET_FIN_REC.DEPRN_METHOD_CODE := NULL; ---FA.DEP_METHOD_CODE;
PX_ASSET_FIN_REC.LIFE_IN_MONTHS := NULL; ---FA.LIFE_IN_MONTHS;
PX_ASSET_DEPRN_REC.YTD_DEPRN := NULL; ---FA.YTD_DEP;
PX_ASSET_DEPRN_REC.DEPRN_RESERVE := NULL; ---FA.DEP_RESERVE;
PX_ASSET_HDR_REC.BOOK_TYPE_CODE := 'OPS CORP'; ---FA.BOOK_TYPE_CODE;
PX_ASSET_DIST_REC.UNITS_ASSIGNED := NULL; ---FA.UNITS_ASSIGNED;
PX_ASSET_DIST_REC.EXPENSE_CCID := NULL; ---FA.EXPENSE_CCID;
PX_ASSET_DIST_REC.LOCATION_CCID := NULL; ---FA.LOCATION_CCID;
PX_ASSET_DIST_REC.TRANSACTION_UNITS := NULL;
--PX_ASSET_DIST_REC.UNITS_ASSIGNED;
PX_ASSET_DIST_TBL (1) := PX_ASSET_DIST_REC;
PX_INV_TBL (1) := PX_INV_REC;
--l_inv_rec.source_line_id := i.source_line_id;
PX_INV_REC.FIXED_ASSETS_COST := 2400; ---I.FIXED_ASSETS_COST;
PX_INV_REC.PAYABLES_COST := 2400; ---I.PAYABLES_COST;
PX_INV_REC.PAYABLES_CODE_COMBINATION_ID := NULL;
---I.PAYABLES_CODE_COMBINATION_ID;
PX_INV_REC.INVOICE_NUMBER := NULL; ---I.INVOICE_NUMBER;
PX_INV_REC.PO_NUMBER := NULL; ---I.PO_NUMBER;
PX_INV_REC.UNREVALUED_COST := NULL; ---I.UNREVALUED_COST;
PX_INV_REC.PROJECT_ID := NULL; ---I.PROJECT_ID;
PX_INV_REC.TASK_ID := NULL; ---I.TASK_ID;
PX_INV_REC.DELETED_FLAG := 'NO'; ---I.DELETED_FLAG;
PX_INV_REC.DESCRIPTION := NULL; ---I.DESCRIPTION;
PX_INV_REC.PO_VENDOR_ID := NULL; ---I.PO_VENDOR_ID;
PX_INV_REC.AP_DISTRIBUTION_LINE_NUMBER := NULL;
---I.AP_DISTRIBUTION_LINE_NUMBER;
PX_INV_REC.PAYABLES_UNITS := NULL; ---I.PAYABLES_UNITS;
PX_INV_REC.INVOICE_ID := NULL; ---I.INVOICE_ID;
PX_INV_REC.INVOICE_DATE := NULL; ---I.INVOICE_DATE;
PX_ASSET_TYPE_REC------------------------------------------------------
PX_ASSET_TYPE_REC.ASSET_TYPE := 'CAPITALIZED'; ---FA.ASSET_TYPE;
PX_INV_TRANS_REC.TRANSACTION_TYPE := 2; ---TRANSACTION_TYPE_CODE;
-- PX_DIST_TRANS_REC := NULL; Modify the code to initialize this parameter
-- PX_ASSET_TYPE_REC := NULL; Modify the code to initialize this parameter
-- PX_ASSET_HIERARCHY_REC := NULL; Modify the code to initialize this parameter
-- PX_ASSET_FIN_REC := NULL; Modify the code to initialize this parameter
-- PX_ASSET_DEPRN_REC := NULL; Modify the code to initialize this parameter
-- PX_ASSET_DIST_TBL := NULL; Modify the code to initialize this parameter
APPS.FA_ADDITION_PUB.DO_ADDITION (P_API_VERSION
, P_INIT_MSG_LIST
, P_COMMIT
, P_VALIDATION_LEVEL
, X_RETURN_STATUS
, X_MSG_COUNT
, X_MSG_DATA
, P_CALLING_FN
, PX_TRANS_REC
, PX_DIST_TRANS_REC
, PX_ASSET_HDR_REC
, PX_ASSET_DESC_REC
, PX_ASSET_TYPE_REC
, PX_ASSET_CAT_REC
, PX_ASSET_HIERARCHY_REC
, PX_ASSET_FIN_REC
, PX_ASSET_DEPRN_REC
, PX_ASSET_DIST_TBL
, PX_INV_TBL
, PX_INV_RATE_TBL
-- END LOOP;
LV_COUNT := LV_COUNT + 1;
COMMIT;
DBMS_OUTPUT.PUT_LINE ( X_RETURN_STATUS
|| ' - '
|| X_MSG_COUNT
|| ' - '
|| X_MSG_DATA
L_MESG := 'FAILED (' || SQLERRM || '): ' || L_MESG;
END;
it returns with a message ( E - 1 - OFA )
which is not descriptive at all

Similar Messages

Diff betw FA Mass addition interaface and FA_ADDITION_PUB.DO_ADDITION API

Hi
Can anyone tell me the major difference between FA MASS ADDITION INTERFCAE and FA_ADDITION_PUB.DO_ADDITION API and which one would you recomend to uses for loading assets from legacy system and why?

Hi
Can anyone tell me the major difference between FA MASS ADDITION INTERFCAE and FA_ADDITION_PUB.DO_ADDITION API and which one would you recomend to uses for loading assets from legacy system and why?

Fa_addition_pub.do_addition returns error

Hi all,
I'm using EBS R12.1.3. When i execute fa_addition_pub.do_addition to create Mass Additions i'm receiving the error:
The Expense CCID cannot be NULL for &EXPENSE_CCID.
FAILUREI checked the metalink but no solution was found/may be my research is wrong/. I found that this value should be "Depreciation expense account identification number" but how to find which value to use in this occasion? Does anybody knows in which FA table this ID is stored?
Thanks in advance,
Bahchevanov.

Solved! It's stored in FA_CATEGORY_BOOKS under DEPRN_EXPENSE_ACCOUNT_CCID column.
Best Regards,
Bahchevanov.

Problem In Calling API fa_addition_pub.do_addition

Hello friends,
I am workin on the addition Of asset program
In which i called API fa_addition_pub.do_addition
but when i am executing it it gives me error
Error(157,1): PLS-00306: wrong number or types of arguments in call to 'DO_ADDITION'
Error(196,1): PLS-00201: identifier 'UPDATE_ERROR_MSG' must be declared
THE CODE WHICH I USED IS GIVEN BELOW
PLZ HELP ME TO SOLVE THIS PROBLEM.
CREATE OR REPLACE PROCEDURE APPS.FA_ADDITION_API (p_row_number NUMBER) AS
l_trans_rec fa_api_types.trans_rec_type;
l_dist_trans_rec fa_api_types.trans_rec_type;
l_asset_hdr_rec fa_api_types.asset_hdr_rec_type;
l_asset_fin_rec_old fa_api_types.asset_fin_rec_type;
l_asset_fin_rec fa_api_types.asset_fin_rec_type;
l_asset_fin_rec_new fa_api_types.asset_fin_rec_type;
l_asset_fin_mrc_tbl_new fa_api_types.asset_fin_tbl_type;
l_asset_deprn_rec fa_api_types.asset_deprn_rec_type;
l_asset_deprn_rec_new fa_api_types.asset_deprn_rec_type;
l_asset_deprn_mrc_tbl fa_api_types.asset_deprn_tbl_type;
l_asset_desc_rec fa_api_types.asset_desc_rec_type;
l_asset_type_rec fa_api_types.asset_type_rec_type;
l_asset_cat_rec fa_api_types.asset_cat_rec_type;
l_asset_dist_rec fa_api_types.asset_dist_rec_type;
l_asset_hierarchy_rec fa_api_types.asset_hierarchy_rec_type;
l_inv_rec fa_api_types.inv_rec_type;
l_inv_trans_rec fa_api_types.inv_trans_rec_type;
l_period_rec fa_api_types.period_rec_type;
l_who_rec fa_api_types.standard_who_rec_type;
l_inv_tbl fa_api_types.inv_tbl_type;
l_inv_rate_tbl fa_api_types.inv_rate_tbl_type;
l_asset_dist_tbl fa_api_types.asset_dist_tbl_type;
l_tax_book_tbl fa_cache_pkg.fazctbk_tbl_type;
l_initial_book boolean := TRUE;
CURSOR xx_addition_cur (p_row_number NUMBER)
IS
SELECT *
FROM xx_reg_book_load_interface
WHERE ROW_NUMBER = p_row_number;
-- Get the inventory details for Asset Addition API
CURSOR xx_dist_info_cur (p_asset_id NUMBER)
IS
SELECT fdh.*
FROM fa_distribution_history fdh
WHERE fdh.transaction_header_id_in = (SELECT MIN(transaction_header_id)
FROM fa_transaction_headers fth
WHERE fth.asset_id = p_asset_id
AND fth.transaction_type_code in ('TRANSFER IN', 'TRANSFER IN/VOID') );
-- AND transaction_header_id_in = p_transaction_id
-- AND NVL (transaction_units, 1) > 0;
-- Get the inventory details for Asset Adjustment API
CURSOR xx_inv_rec_type_adj_cur (p_row_number NUMBER)
IS
SELECT fai.invoice_transaction_id_in, fai.deleted_flag,
fai.invoice_number, fai.po_number, fai.unrevalued_cost,
fai.project_id, fai.task_id, fai.payables_code_combination_id,
fai.fixed_assets_cost, fai.source_line_id, fai.payables_cost,
xrbli.transaction_type_code, fai.ap_distribution_line_number,
fai.description, fai.po_vendor_id,
fai.payables_units,
fai.invoice_id,
fai.invoice_date
FROM fa_asset_invoices fai, xx_reg_book_load_interface xrbli
WHERE fai.invoice_transaction_id_in = xrbli.invoice_transaction_id
AND xrbli.ROW_NUMBER = p_row_number;
-- Out parameter for Addition API
l_return_status VARCHAR2 (1);
-- Out parameter for Addition API
l_mesg_count NUMBER := 0;
-- Out parameter for Addition API and used for error tracking
l_mesg VARCHAR2 (4000);
-- Index for inventory record table
l_dist_rec_count NUMBER := 0;
l_inv_rec_count NUMBER := 0;
l_stat_class VARCHAR2(50) ;
BEGIN
-- Open XX_ADDITION_CUR cursor by passing the period
FOR p_asset_addition IN xx_addition_cur (p_row_number)
LOOP
-- ASSET_FIN_REC_TYPE Asset Structure
l_asset_fin_rec.date_placed_in_service :=p_asset_addition.date_placed_in_service;
l_asset_fin_rec.COST := p_asset_addition.COST;
l_asset_fin_rec.depreciate_flag := 'YES'; -- YES for all the records
-- Transaction Info
/* BEGIN
SELECT segment4
INTO l_stat_class
FROM fa_categories_b fcb
WHERE fcb.category_id = p_asset_addition.asset_category_id ;
EXCEPTION WHEN OTHERS THEN
l_stat_class := NULL ;
END ;
IF ( NVL(l_stat_class,'*') = 'I' ) THEN
l_trans_rec.transaction_subtype := 'AMORTIZED' ;
END IF ;
l_trans_rec.who_info := l_who_rec;
-- ASSET_HDR_REC_TYPE Asset Structure (Asset ID should not be there for Addition API)
l_asset_hdr_rec.book_type_code := p_asset_addition.book_type_code;
-- ASSET_DESC_REC_TYPE Asset Structure
l_asset_desc_rec.asset_number := p_asset_addition.asset_number;
l_asset_desc_rec.description := p_asset_addition.description; ----modify by anand
l_asset_desc_rec.current_units := p_asset_addition.current_units;
l_asset_desc_rec.asset_key_ccid := p_asset_addition.asset_key_ccid;
-- ASSET_TYPE_REC_TYPE Asset Structure
l_asset_type_rec.asset_type := p_asset_addition.asset_type;
-- ASSET_CAT_REC_TYPE Asset Structure
l_asset_cat_rec.category_id := p_asset_addition.asset_category_id;
-- Initialize the count
l_inv_rec_count := 0;
-- INV_REC_TYPE Invoice Structure
FOR i IN xx_inv_rec_type_adj_cur (p_row_number)
LOOP
--IF l_asset_id_count p_asset_adjustment.asset_id THEN
l_inv_rec_count := l_inv_rec_count + 1;
l_inv_trans_rec.transaction_type := i.transaction_type_code;
--l_inv_rec.source_line_id := i.source_line_id;
l_inv_rec.fixed_assets_cost := i.fixed_assets_cost;
l_inv_rec.payables_cost := i.payables_cost;
l_inv_rec.payables_code_combination_id :=i.payables_code_combination_id;
l_inv_rec.invoice_number := i.invoice_number;
l_inv_rec.po_number := i.po_number;
l_inv_rec.unrevalued_cost := i.unrevalued_cost;
l_inv_rec.project_id := i.project_id;
l_inv_rec.task_id := i.task_id;
l_inv_rec.deleted_flag := i.deleted_flag;
l_inv_rec.description := i.description;
l_inv_rec.po_vendor_id := i.po_vendor_id;
l_inv_rec.ap_distribution_line_number :=i.ap_distribution_line_number;
l_inv_rec.payables_units := i.payables_units;
l_inv_rec.invoice_id := i.invoice_id;
l_inv_rec.invoice_date := i.invoice_date;
l_inv_tbl (l_inv_rec_count) := l_inv_rec;
--l_asset_id_count := p_asset_adjustment.asset_id;
--END IF;
END LOOP;
-- ASSET_DIST_REC_TYPE and ASSET_DIST_TBL_TYPE Asset Structure
FOR i IN xx_dist_info_cur (p_asset_addition.asset_id
-- , p_asset_addition.transaction_header_id
LOOP
l_dist_rec_count := l_dist_rec_count + 1;
-- l_asset_dist_rec.assigned_to := i.assigned_to;
l_asset_dist_rec.units_assigned := i.units_assigned;
l_asset_dist_rec.expense_ccid := i.code_combination_id;
l_asset_dist_rec.location_ccid := i.location_id;
l_asset_dist_tbl (l_dist_rec_count) := l_asset_dist_rec;
END LOOP;
-- Update to 0 for further use
l_dist_rec_count := 0;
--fnd_file.put_line(fnd_file.log, 'Calling the Addition API') ;
-- Call Addition api
fa_addition_pub.do_addition
(p_api_version => 1.0,
p_init_msg_list => fnd_api.g_false,
p_commit => fnd_api.g_false,
p_validation_level => fnd_api.g_valid_level_full,
x_return_status => l_return_status,
x_msg_count => l_mesg_count,
x_msg_data => l_mesg,
p_calling_fn => 'FA_ADDITION_API', ---modify by anand
px_trans_rec => l_trans_rec,
px_dist_trans_rec => l_dist_trans_rec,
px_asset_hdr_rec => l_asset_hdr_rec,
px_asset_desc_rec => l_asset_desc_rec,
px_asset_type_rec => l_asset_type_rec,
px_asset_cat_rec => l_asset_cat_rec,
px_asset_hierarchy_rec => l_asset_hierarchy_rec,
px_asset_fin_rec => l_asset_fin_rec,
px_asset_deprn_rec => l_asset_deprn_rec,
px_asset_dist_tbl => l_asset_dist_tbl,
px_inv_tbl => l_inv_tbl,
px_inv_rate_tbl => l_inv_rate_tbl
--fnd_file.put_line(fnd_file.log, 'Addition API returned status as : '|| l_return_status) ;
IF (l_return_status = fnd_api.g_ret_sts_success)
THEN
l_mesg_count := fnd_msg_pub.count_msg;
IF l_mesg_count > 0
THEN
l_mesg :=CHR (10)|| SUBSTR (fnd_msg_pub.get (fnd_msg_pub.g_first,fnd_api.g_false),1,512);
FOR i IN 1 .. (l_mesg_count - 1)
LOOP
l_mesg :=l_mesg|| CHR (10)|| SUBSTR (fnd_msg_pub.get (fnd_msg_pub.g_next,fnd_api.g_false),1,512);
END LOOP;
fnd_msg_pub.delete_msg ();
END IF;
l_mesg := 'FAILED (' || SQLERRM || '): ' || l_mesg;
-- Procedure to update XX_REG_BOOK_LOAD_INTERFACE table with rejection reason
update_error_msg ('Addition', l_mesg, p_asset_addition.ROW_NUMBER);
ELSE
-- Display the successful record
fnd_file.put_line (fnd_file.output,p_asset_addition.asset_number|| ' -> '|| p_asset_addition.description|| ' for asset Addition Success.'); --- modify by anand
END IF;
-- Delete PLSQL table and record type variables data
--empty_rec;
END LOOP;
END fa_addition_api;
tahnk you

You call do_addition with a wrong set of parameters or you use the wrong datatypes from your parameters.
Check what parameters ( and their datatypes ) that procedure expects.
Also check if you have the right privileges for using UPDATE_ERROR_MSG and that a synonym exists for it.
fa_addition_pub.do_addition
(p_api_version => 1.0,
p_init_msg_list => fnd_api.g_false,
p_commit => fnd_api.g_false,
p_validation_level => fnd_api.g_valid_level_full,
x_return_status => l_return_status,
x_msg_count => l_mesg_count,
x_msg_data => l_mesg,
p_calling_fn => 'FA_ADDITION_API', ---modify by anand
px_trans_rec => l_trans_rec,
px_dist_trans_rec => l_dist_trans_rec,
px_asset_hdr_rec => l_asset_hdr_rec,
px_asset_desc_rec => l_asset_desc_rec,
px_asset_type_rec => l_asset_type_rec,
px_asset_cat_rec => l_asset_cat_rec,
px_asset_hierarchy_rec => l_asset_hierarchy_rec,
px_asset_fin_rec => l_asset_fin_rec,
px_asset_deprn_rec => l_asset_deprn_rec,
px_asset_dist_tbl => l_asset_dist_tbl,
px_inv_tbl => l_inv_tbl,
px_inv_rate_tbl => l_inv_rate_tbl
);

Mass addition accunting entires from PO to FA

Hi
any one please help me to know what are all acunting entires created in mass addition process - from PO to FA
1) I created asset item in the asset orgainsation
2) for example the item is 'Computer laptop' - in purchasing tab - account code is - asset clearing account.
3) I entered purchase order for 'computer laptop' - the distribution account - asset clearing accounting. it is 3 way match.
4) I received the item - 'Computer laptop' - delivered it
5) same PO matched against AP invoice
6) AP invoice distribition account - showed asset clearing account - Tracked as asset is checked
7) Ran the mass addition program
8) in FA through the mass additioin- I add the new assest.
In this case - what are all accounting entires created from receipt of 'computer laptop', delivery of item, matching to AP invoice and Addition of asset. - please write the down accounting entry.
Thanks
venkatesan
Edited by: user11936275 on Jan 20, 2011 8:55 PM

Hi Vekatesan,
For Asset related invoicess , In AP
Credit Liability
Debit Asset Clearing
Mass additions will create the asset with the following entries
Debit Asset account for computer-Laptop
Credit Asset Clearing
Regards
Muthu

Loading categories to the mass additions interface

Hi,
We are doing an R12 FA implementation.
If I explain it more detail.
We have 11i , but we r going to scrap 11i and implement R12 fresh.
However the data will be extracted from 11i as it is.
As u all know we need to use either mass additions interface or the additions API. In this case we r going to use mass additions interface.For the conversion we r going to use ODI to map the data.
The isssue we are facing is, since the ODI is going to be used it will map data from 11i base tables to the mass_additions_interface table in R12. The mapping of the categories becomes a major issue in this scenario. Since we cannot load the category combinations to the interface, instead only an ID can be populated.As I told you we r populating the 11i values it will be wrong the populate it with 11i values, because in R12 we will have a new set of category IDs.
Can anyone help me to load the categories ( That exist in R12) to the mass additions interface using ODI? or is there a way using the API?
Thanks and Regards,
MPH

Hi,
I believe you need to define another table which maps the Old Category ID with New one. Use ODI to map the Data and this Temp table to Mass additions.
Regards,
Sridhar

Which table tag number is stored after running post mass additions in FA

Hi,
could any one tell me, in which table tag number is get stored after running the post mass additions program in FA (R12).

Hi,
It will be stored in fa_additions_b.
Thanks,
Vinod

Undelete in Mass Additions Queue=Delete

My business user inadvertently deleted all AP transactions from Mass Additions using Tools==>Delete All. The transactions were in queue 'New' but now are in queue 'delete'. Is there a way to put them in the 'New' queue again. No post process has happened as of yet. The trasactions were sent by AP using Mass Additions process.
Thanks in Advance!
mtm

Hi,
We could find the work around for deletion of assets which are in POST Status.
We edited the Description of the Asset and saved it again.This way it allowed to Delete the Mass additions which got stuck with POST status.
Thanks

Assets Mass Addition error-APP-OFA-48400

Hi,
We are working on Oracle Applications 11i. The Assets user have run the post mass additions and the Mass Additions post gave no output when it completes successfully (POST MASS ADDITIONS REPORT and two of the MASS ADDITIONS POST resulted in error before the thired one completes successfully) and there is still one item X in the POST queue in the mass additions.
Item X was one of two items in the same PO and same invoice the second item Y was POSTED successfully and now has an asset number.
I have checked the po charge accounts, ap expense account and fa clearing account and they match.
Any clues?
This matter is urgernt please due to the period closing.
Found the following error in one of the logs:
At least one of the child requests failed.
Cause: At least one of the child requests spawned to run Mass Additions Post failed.
Action: Check the Mass Additions Post log files to find out what caused the request to fail.
Error: function famgpi returned failure (called from FAMAPT)
APP-OFA-48400: Error: function famgpi returned failure (called from FAMAPT)
Edited by: AHS on Feb 4, 2010 1:37 AM
Edited by: AHS on Feb 4, 2010 1:48 AM

Thank you for your help.
unfortunately, i have no access to metalink these days.
We had also the following error ; on the attempt to open the assignment form of the item:
APP-OFA-48317: the employee to which this distribution line is assigned is no longer valid.
when the form opens there is no emmploye visible in the assignment line.
and in the table FA_MASSADD_DISTRIBUTIONS an employee_id is there.
So, I chose an employee in the form and saved it, then I cleared the employee from the line and saved again.
Finally the problem is solved.

Life in months is not populating from interface in Mass Additions Post

Hi,
We have one critical issue in FA conversion.We have popultaed the life_in_months in fa_mass_additions table.When we run the Mass Additions Post,it is defaulting the life_in_months from category and not from fa_mass_additions interface table.As per intended functionality,it should populate from interface table.
If any of you encounter the issue,Please let me know the soultinon.
Thnaks
Praveen

>
DATA showing on front end,but it is not populating into base table AP_INVOICE_DISTRIBUTIONS_ALL.
>
Are you saying you can see the distributions from front end but not in the table?
Did you populate the distribution related columns in AP_INVOICE_LINES_INTERFACE (e.g. DIST_CODE_COMBINATION_ID)?
Sandeep Gandhi

Date in service - AP to FA Mass addition

Hi
In R12, when we ran the AP to FA Mass addition and querying mass addition in FA, system is showing new assets with date in service as the date on which Mass addition was run. Is that the intended functionality..?
Can we change the date in service as invoice date by default through mass addition program..?
regards
Ahsan

Please check in KON* series table in SE16N transaction. I guess KOHN table may help you out. You can see other similar tables.
In any one of the table you will find validity data.

While merging lines in prepare mass additions invoices lines do not appear

Hello,
I am facing an issue in merging mass additions line. I dont see any lines to merge even though many invoice line exist. I even tried query mode where i query the lines based on the invoice number but still lines do not appear for merge.
detailed steps:
Press open button on an oh hold item in the mass additions summary window.
Enter additional information and select done.
Back in the mass additions summary window, pick the first mass addition item again and press 'merge'
button.
Select the other new mass additions items that you want to merge into one asset.
-> Problem, the other new items do not appear for selection.
It was working fine till few months back but seems some patch have created this issue. Have you faced such issue?
We are on 12.0.6.
Any pointer is helpful.
Regards
Bipin

I wish I had a 10.3.9 machine to check, but, since your video card should definitely be up to the task, I think it's probably going to be that Keynote's having a unique problem with your setup. In Keynote, under the Keynote menu, choose "Provide User Feedback" and send your problem to Apple. It could be that it may not have been reported yet.

Mass Additions Posting Report customization

Hi,
I am customizing a standard report that has one mandatory parameter. Requirement is to make the report available for all SOBs by removing the parameter. Report is "Mass Additions Posting Report" (FAS824.rdf). While trying to remove the P_BOOK parameter in the standard RDF, I am unable to derive values for "Accounting_Flex_Structure" variable as it is being derived using the P_BOOK value. This particular value is coming from "FA_BOOK_CONTROLS.accounting_flex_structure". I am unable to group it with the main group in the RDF which is using "FA_SYSTEM_CONTROLS". There is no link for FA_SYSTEM_CONTROLS to any table where I can join it with FA_BOOK_CONTROLS to derive "Accounting_Flex_Structure" and make the report run for all SOBs. Please help.
Thanks in advance.
Kiran

I think you can use database trigger, Whenever they are running the Mass Additions posting, the trigger will submit the concurrent request (FAS824) in a loop, use Fnd_Request.submit_request by the particular SOB parameter, hope this can help you
br,
thanks

KIMYONG: Mass Addition Create 에서 Ctrl + F11 이로 Invoice조회가 되지 않을때

Purpose
Prepare Mass additions form,Ctrl+F11 조회시 모든 Data가 return되지 않는 경우가 있습니다.
이에 대한 원인및 조치사항을 제공하고자 합니다.
Solution
원인은 아래 bug처럼 Security by book setup이 되어 있을경우 발생합니다.
Bug 5186425 FAXMADDS: Can Query Mass Additions of all Secured Books in summary Window
해결책으로는 아래와 같은 것들이 제시되고 있습니다.
This issue has been fixed in the file FAXMADDS.fmb version 115.270 or higher.
If you are on 11i.FA.P , Please apply one-off Patch 5229010.
This patch includes FAXMADDS.fmb version 115.271.
Reference
Note 370480.1

Fixed Assets Mass Addition

Hi,
We have the below requirement in 11i:
When there is a mass addition, there should be an option to assign accounting code combinations at a category or setup level so that it defaults to all items on a divisional accounting basis. This is to enable divisional accounting for Balance Sheet and Depreciation (Profit & Loss).
Is this possible using standard functionality?
thanks.
S.Sriram

Hi
I am using Solution beacon vision instance and have tried entering an asset using mass additions and below are my observations:
I entered the Asset book, Transaction date, asset category, number of units and than clicked on the Assignments button and entered the Expense Account and Location.
For the expense acount the system is automatically defaulting the following:
Company Segment Value - 01 as company value (since the default value has been set at the Key Flexfields segments window)
Account Segment Value - Depreciation expense account (This value is being defaulted from the Asset category window based on the Category setup)
Sub-Account - Defaulted as 0000 (since the default value has been set at the Key Flexfields segments window)
Product - Defaulted as 0000 (since the default value has been set at the Key Flexfields segments window)
The system is prompting me to enter the value for the department segment as it is not automatically defaulted. (No Default value has been set at the Key flexfields segments window)
I didnt find a place where in i can see the asset clearing account or cip clearing account was being asked or used while creating mass additions.
When the asset is being brought from other module such as Payables, than the Asset clearing account or CIP Clearing account would have been entered at the Invoice distributions level and that is being brought into the Mass additions window and is displayed in the source tab screen.
But apart from the above i have not been able to find a tab/field wherein system asks or prompt me to enter the other accounts as mentioned by you.
Based on the above, do you find any difference of what you might be seeing or the accounts being defaulted.
Thanks and Regards
Manish Jain.

Fa mass additions (fa_addition_pub.do_addition)

Similar Messages

Maybe you are looking for