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

Similar Messages

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

MASS ADDITIONS POST 시 DR/CR 계정이 안 생기는경우

제품 : FIN_FA
작성날짜 : 2003-12-02
MASS ADDITIONS POST 시 DR/CR 계정이 안 생기는경우
========================================
PURPOSE
Mass Additions Post 에 의해 생기는 DR/CR clearing accounts 가
merged mass additions lines에서는 잘 안생기는 경우가 있다. 이에 대한
해결책을 제시한다.
Problem Description
다음 Query문으로
DR/CR Clearing Accounts 가 안생기는 자산을 찾을수 있다.
select distinct th.asset_id "ID",th.book_type_code "BOOK"
,th.invoice_transaction_id "TRX_ID"
,ai.fixed_assets_cost "COST"
,ai.payables_code_combination_id "CC_ID"
from fa_transaction_headers th,
fa_asset_invoices ai,
fa_deprn_periods dp
where (th.transaction_type_code = 'ADJUSTMENT'
or th.transaction_type_code = 'ADDITION')
and dp.book_type_code = th.book_type_code
and dp.period_close_date is not null
and th.date_effective between
dp.period_open_date and nvl(dp.period_close_date, sysdate)
and th.asset_id = ai.asset_id
and th.invoice_transaction_id = ai.invoice_transaction_id_in
and ai.payables_code_combination_id = gcc.code_combination_id
and (0 =
(select sum (ai1.fixed_assets_cost)
from fa_asset_invoices ai1
where th.asset_id = ai1.asset_id
and th.invoice_transaction_id = ai1.invoice_transaction_id_in
and ai1.fixed_assets_cost != 0
and ( ai1.merged_code = 'MC'
or ai1.merged_code = 'MP')))
and not exists
( select ad2.transaction_header_id
from fa_adjustments ad2,
fa_asset_invoices ai2
where th.asset_id = ad2.asset_id
and th.asset_id = ai2.asset_id
and th.invoice_transaction_id = ai2.invoice_transaction_id_in
and th.book_type_code = ad2.book_type_code
and th.transaction_header_id = ad2.transaction_header_id
and ( ad2.source_type_code = 'ADJUSTMENT'
or ad2.source_type_code = 'ADDITION')
and ad2.adjustment_type = 'COST CLEARING'
and ad2.code_combination_id = ai2.payables_code_combination_id
and ad2.adjustment_amount = ai2.fixed_assets_cost );
Workaround
한꺼번에 넘어오는 Invoice들중 먼저 하나를 Asset으로 등록하고 나머지 Invoice들을 기존 자산에 'Add to Asset' 을 이용하여 등록한다.
Solution Description
Apply 11i.FA.J (2230269) 이상에서 해결되었다.
Reference Documents
205765.1

Hi
Supplier invoice debit an account XXXX. This should be a CIP account (construction in progress), which is an Asset type account in GL.
When you capitalize the project, the system is populating the mass addition 'clearing account' field with the account debited by Projects (in your case, by AP). This will be the XXXX account.
The Expense Account should be the account you intend to charge periodic depreciation costs.
The Asset Account should be the account you intend to charge the value (the cost) of the asset in GL balance sheet.
Both, expense and asset, accounts are derived from the asset category.
If you have not defined asset categories, the system will use the default accounts from the system implementation setup.
Usually when you create an asset in Projects, before capitalizing, you are expected to setup the asset category. Asset category derives accounting and depreciation method.
Dina

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.

Mass addition transfer

Hello,
What are the conditions to transfer items to FA?
Is that the combination that have same category in FA?
If the line in distribution in AP is matched to PO and has an item that defined "Fixed asset" - it will transfer to FA ?
thanks,
Kobi Idah

For doing the Mass Transfer in Fixed Assets the following conditions is to be met.
a) Define the Asset Category for that Asset.
b) If it is matched to PO, then in the Charge account you need to choose the Asset Clearing Account only.
c) When the Invoice been matched to Purchase Order, make ensure from the Show->Field-> Track as Asset need to be enabled otherwise the payables distributions will not be identified as a 'Asset'.
d) Validate an Invoice
e) Account an Invoice.
f) Payable Transfer to General Ledger.- Report Need to be run.
g) Run the Report
-- Mass Addition Create
-- Mass Addition Create Report.
Navigate to Fixed Asset Module.
Go to Prepare Mass Addition.
Query with your asset book / Invoice Number.
Change the status from Queue to Post.
Go to Post Mass Addition.
Choose your Asset Book and submit the concurrent.
Make ensure these concurrents should complete Normal.
I have also mentioned the Accountign entries at different stages--
In Purchasing Module
Expense accural a/c Dr
Asset Clearing a/c.
In Payables Module
Asset Cost a/c
To Liability
In Fixed Assets Module
Asset Clearing a/c
To Asset Cost

Mass Additions Errors

Hi,
I am trying to create/load an asset using fa_mass_additions interface by running Post Mass Additions Program
Initially i got &EXPENSE_CODE_COMBINATION_ID cannot be null and now i am getting the below error
The Location for &LOCATION cannot be NULL.
Mass Addition ID: 49701 ==> ** Failed **
Number of successes: 0
Number of failures: 1
Module Mass Additions Post ended with error
I am passing both EXPENSE_CODE_COMBINATION_ID and LOCATION_ID into fa_mass_additions interface but the trigger on it is overwriting to null
Please let me know if any one of you came across this issue.
Thanks,
Nagaraj

Hi Devidas,
1. Balance of ORD 1000010 is not zero.
For this please get in touch with Costing persons. Orders are not yet settled. hence this problem is there.
2. Unprocessed future change recs for order 1000012 prevent del. flag/completion.
Few transactions are open for this material please close it.
3. System status CRTD is active (ORD 1000220)
Please put status TECO for this orders this will solve your problem.
Please confirm,
Regards,
Amit Kulkarni.

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

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 WEB ADI Issue

All,
Has anyone come across a need to modify the mass additions upload via web adi, to do validation on asset numbers. We find that if we use web adi to mass additions, the error of duplicate asset numbers is only picked up when we do a post. Our users require that validation, when they do the upload from web adi. As this was a functionality that desktop adi provided.
Any help here would be much appreciated.

Hi
Can you think about one work around
1. Import Asset table containing Asset Number before uploading the asset using Web ADI.
2. Compare the Imported data with Web ADI Template using EXCEL macro check or using a sql script
Have you loged SR & wether Oracle can think of some Validation (as this is the standard functionality) ?
Regards
Sunil Kumar

Necessary to empty Mass-Addition Workbench before run Depreciation?

Hi!
Is it necessary to empty the Mass-Addition Transactions in Workbench before the Depreciation Run will be started or the Period will be closed?
Which impact does it have if few Transactions will remain in the Mass-Addition Workbench? Because till Depreciation - Run or Month End Closing it will be not possible to finish editing all Mass Additions Transactions.
Thank you!
kind regards
Evelyn

Hi
Answer can be both Yes and No
Case I : Say you have pending transaction for the current period in Mass Addition, then it is required to post them before running depreciation and they can't be processed later.
Case II: If you have future trsanctions in mass addition, no need to worry . when you will close the period depreciation request set will run Proces sPending Transactions and will post any elligible lines from mass addtiions
Thanks
Sunil

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

Undelete 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

Getting error while posting reports on Unix Process Scheduler Server

Hello ,
I am getting the below error while posting reports on Unix Process Scheduler Server .
PSDSTSRV.14338 (2) [09/08/09 08:21:34 PostReport](1) (JNIUTIL): Java exception thrown: java.io.IOException: Stream closed.
PSDSTSRV.14338 (2) [09/08/09 08:21:34 PostReport](3) HTTP transfer error.
PSDSTSRV.14338 (2) [09/08/09 08:21:34 PostReport](3) Post Report Elapsed Time: 0.0900
PSDSTSRV.14171 (10) [09/08/09 08:21:34 PostReport](1) (JNIUTIL): Java exception thrown: java.io.IOException: Stream closed.
Please advise ,thank you.

user5838027 wrote:
Node name :PS_HTTP
URL: http://ddas1020.dev.com:16000/psreports/hrdmo
URI:SchedulerTransfer/hr90dmo
URI Port: 16000
Please let me know if any other info is needed.
Thanks.
typo...
URL: http://ddas1020.dev.com:16000/psreports/hr90dmo
Hopefully, your application URL looks like http://ddas1020.dev.com:16000/psp/hr90dmo/..., your URI host looks like ddas1020.dev.com (or corresponding ip address), and hhtp is checked.
Did you also tried to give the web login/password ?
Nicolas.

No additional posting to asset

We have this message when try to make a payment for the transaction F110 or F-53
No additional posting to asset
Message no. AA444
Diagnosis
A downpayment was already posted to the asset 1001000004 0 in the currently displayed document. Additional posting to the same asset in this document is not possible for technical reasons.
Procedure
Combine the two downpayments into one.
In the transaction F-47 we capture a down payment request that is reference to purchase document, and this document is reference to asset. This down payment have more than one lines or position.
We look for a solution in Market Place and find the NOTE 562264, here show us the same error, but is only for the 4.6c version and we have the 5.0. This note recommended a change in the program LAMDPU10, we check this program with the ABAP people but they say that this change isnu2019t appear in the 5.0 SAP version.
The solution given for this people was make 2 down payments but this mean more work for the acounts payable (AP) people, or combine the two downpayments into one but we lost the relation downpayment with the purchse document position.
Do you please help us with this situation?

Refer OSS note 6061. Here is the text from the notes-->
Symptom: Several down payment requests exist for a vendor that are assigned to the same asset and are to be cleared with a payment run. => The vendor payment is rejected with error message AA444.
Additional key words: Down payment
Cause and prerequisites: The system rejects a multiple account assignment to assets in one down payment document because of the offsetting of down payments in foreign currency areas has been revised and restricted.
Solution: Post down payments that are assigned to the same asset manually and also create the
payment medium manually.

Mass Additions Posting Report customization

Similar Messages

Maybe you are looking for