GL account based on the 'commodity mobde' (product category)
The requirement is
System shall default the GL Account with sequence number u201801u2019 when there are multiple GL Accounts mapped to a Product Category and the mapping table needs to have u2018Sequence numberu2019 added to ensure that in case of u2018Many-to-Oneu2019 the default proposed GL Account can be selected.
Requester will be allowed to change the u201CGL Accountu2019 to a different value.
The system will show the allowed u2018GL Accountsu2019 that are mapped to this product Category when performing the search ( Narrow down only to allowed values ).
Hi,
Please check the BADI BBP_F4_READ_ON_EXIT.
Regards,
Masa
Similar Messages
-
How to stop the charges incurred to my account based on the action of itunes storing U2's newest album into my iPhone that I personally did not pay for?
There was no charge. The album was free.
-
Generating Supplier Liability Account based on the Supplier Classification
Hi ,
In R12 I have a custom requirement like follows. Need to generate the Supplier Liability Account based on the Supplier Classification. When we select supplier type then by default liabilty account value will be the value from supplier--> setup --> options --> fianancial otpions --> accounting tab (GL -accounts liability value).
so when we change the supplier type the liability account should changed based on that classification value.
I have code in 11i where custom.pll was modified to acheive this, but how to implement this in R12 as supplier form is OAF based.
the code from custom.pll for this is
procedure event(event_name varchar2)
is
lCurrBlock varchar2(30);
lVendorType varchar2(30);
lDefaultCCID number(15);
lCustomCCID number(15);
cursor customCC(x_vendor_type varchar2,x_default_cc_id number) is
select
cst.code_combination_id
from
fnd_lookup_values vty,
gl_code_combinations dfl,
gl_code_combinations cst
where 1=1
and vty.view_application_id = 201
and vty.lookup_type = 'VENDOR TYPE'
and vty.language = 'US'
and vty.lookup_code = x_vendor_type
and dfl.code_combination_id = x_default_cc_id
and dfl.segment1 = cst.segment1
and vty.tag = cst.segment2 --account no
and dfl.segment3 = cst.segment3
and dfl.segment4 = cst.segment4
and dfl.segment5 = cst.segment5
and (dfl.segment6 = cst.segment6 or (dfl.segment6 is null and cst.segment6 is null))
and (dfl.segment7 = cst.segment7 or (dfl.segment7 is null and cst.segment7 is null))
and (dfl.segment8 = cst.segment8 or (dfl.segment8 is null and cst.segment8 is null))
and (dfl.segment9 = cst.segment9 or (dfl.segment9 is null and cst.segment9 is null))
and (dfl.segment10 = cst.segment10 or (dfl.segment10 is null and cst.segment10 is null))
and (dfl.segment11 = cst.segment11 or (dfl.segment11 is null and cst.segment11 is null))
and (dfl.segment12 = cst.segment12 or (dfl.segment12 is null and cst.segment12 is null))
and (dfl.segment13 = cst.segment13 or (dfl.segment13 is null and cst.segment13 is null))
and (dfl.segment14 = cst.segment14 or (dfl.segment14 is null and cst.segment14 is null))
and (dfl.segment15 = cst.segment15 or (dfl.segment15 is null and cst.segment15 is null))
and (dfl.segment16 = cst.segment16 or (dfl.segment16 is null and cst.segment16 is null))
and (dfl.segment17 = cst.segment17 or (dfl.segment17 is null and cst.segment17 is null))
and (dfl.segment18 = cst.segment18 or (dfl.segment18 is null and cst.segment18 is null))
and (dfl.segment19 = cst.segment19 or (dfl.segment19 is null and cst.segment19 is null))
and (dfl.segment20 = cst.segment20 or (dfl.segment20 is null and cst.segment20 is null))
and (dfl.segment21 = cst.segment21 or (dfl.segment21 is null and cst.segment21 is null))
and (dfl.segment22 = cst.segment22 or (dfl.segment22 is null and cst.segment22 is null))
and (dfl.segment23 = cst.segment23 or (dfl.segment23 is null and cst.segment23 is null))
and (dfl.segment24 = cst.segment24 or (dfl.segment24 is null and cst.segment24 is null))
and (dfl.segment25 = cst.segment25 or (dfl.segment25 is null and cst.segment25 is null))
and (dfl.segment26 = cst.segment26 or (dfl.segment26 is null and cst.segment26 is null))
and (dfl.segment27 = cst.segment27 or (dfl.segment27 is null and cst.segment27 is null))
and (dfl.segment28 = cst.segment28 or (dfl.segment28 is null and cst.segment28 is null))
and (dfl.segment29 = cst.segment29 or (dfl.segment29 is null and cst.segment29 is null))
and (dfl.segment30 = cst.segment30 or (dfl.segment30 is null and cst.segment30 is null));
begin
if name_in('SYSTEM.CURRENT_FORM') != 'APXVDMVD' then
return;
end if;
lCurrBlock := name_in('SYSTEM.CURSOR_BLOCK');
if event_name = 'WHEN-NEW-FORM-INSTANCE' then
-- app_item_property.set_property('VNDR.VENDOR_TYPE_DISP_MIR',required,property_true);
copy(name_in('WORLD.ACCTS_PAY_CODE_COMBINATION_ID'),'GLOBAL.XX_APXVDMVD_ACCTS_PAY_CC_ID');
elsif lCurrBlock = 'VNDR' and event_name in ('WHEN-VALIDATE-RECORD','WHEN-NEW-RECORD-INSTANCE') then
open customCC(name_in('VNDR.VENDOR_TYPE_LOOKUP_CODE'),name_in('GLOBAL.XX_APXVDMVD_ACCTS_PAY_CC_ID'));
fetch customCC into lCustomCCID;
close customCC;
if lCustomCCID is null then
copy(name_in('GLOBAL.XX_APXVDMVD_ACCTS_PAY_CC_ID'),'WORLD.ACCTS_PAY_CODE_COMBINATION_ID');
else
copy(lCustomCCID,'WORLD.ACCTS_PAY_CODE_COMBINATION_ID');
end if;
end if;
end;
end;
please helpHi,
While you can refer to the SLA guide, for quick pointers what you need to do is:
1. Identify the transaction types and associated events for that transaction.
2. Build an accounting rule for the above.
An example would be AP invoice validation or application of prepayments.
The SLA guide provides step by step details on the above.
Good Luck !!!
Regards,
Udit -
GR/IR accounts based on the country of origin
Dear All,
My client business requirement is like below:
when we are posting goods receipt GR/IR account has to be posted based on the country of origin of the materials. we have one chart of accounts, we don't have any business areas. we have defined 14 GR/IR accounts for this purpose.
Please any one can suggest me the solution in SAP, how we can do? even customized one also?
thanks & regards,
Ramesh Buu
-
Can you disable an AD account based on the email address
New to Powershell so hopefully this makes sense. I have a script to disable users from a list of user names and it works fine. However our HR system doesn't use the same naming convention as AD.
The only common field is the e-mail address. Does anyone know a script that will search a list of email addresses and disable the associated AD account? The e-mail address from the HR system should be the primary address of the user but it may not always
be so I need to search all the users addresses.
thanksHi,
I'd do something along these lines:
Get-Content .\emailList.txt | ForEach {
Get-ADUser -Filter "proxyAddresses -like '*$_*'" | Disable-ADAccount -WhatIf
Remove -WhatIf if you're happy with the initial output to actually disable the accounts.
Braham - note on your method:
Error Message: 'Operator Not supported: -contains' at position: '46'.
Don't retire TechNet! -
(Don't give up yet - 13,085+ strong and growing) -
Which table the characteristic values of accounting based COPA are stored?
Hi Guru,
we are using Accounting based COPA. we need to generate a report based on the characteristic values updated while posting to revenue accounts.
i searched the CE4XXXX and COSP tables but i am unable to get the results. COSP is not havinf the the revenue GL accounts PA characteristics.
CE4XXXX is not having the the PAOBJNR(profitability object no) updated in BSEG for the revenue accounts.
from which table can i capture the characteristic values for a line item posted in BSEG.
regards
JayaHI
refer CE4XXXX_ACCT for account based COPA
The function module to read chars from PSG is RKE_GET_CHARS_FOR_PAOBJNR
Regards
Ajay M -
How to default inv mtl accnt based on the item categories for all trxns
Hi all,
There is a requirement for defaulting inventory material account based on the item categories accounts defined in the category accounts window. instead of defaulting from the inventory organization parameters.
I researched on that and found that we need to do product line accounting setups and modify the accounting client extension code ( Cost Management PDF)
Am i correct in the approach? will i succeed if we go ahead and do these?
Need your kind comments....
Regards,
PrasadHi,
I can think of one of the probable solution for your requirement.
Your need to create new condition table with item Category as one of the key combination. I think you need to update the item category in field catalog as well as in Doc Structures. Then maintain free goods condition record all the item categories except for the Return item category. This way you can exclude free goods activation for return items.
Note : If the number of active item categories are more then it may be difficult to maintain condition records for the item categories.
Hope this will help
Regards,
Sanjay -
Qty from VA88 Settlement for Account based copa
Hi Gurus,
I have a question on VA88 in MTO-E scenario. In account based copa the qty will update in Delivery. In MTO-E Scenario there is no accounting entries in Delivery(PGI).
Is there any way to derive Billing qty in Settlement.(VA88)
Thanks
Vasanth K.Hi Castles
It depends on your segment level chars in KEQ3.... Suppose you defined Customre and Product as Seg Levle CHar
Each time you enter a new Cust or Prod in sales order - The record will be written to CE4 and a new PSG no would be generated... Next tieme when you enter same Cust / Prod - Same PSG would be used
If you see carefully in KEQ3 - Sale order is not a segment level char by default.. hence, Sales order is not written in CE4
However, you can see it in table CE4xxxx_ACCT
Regarding jumping no.s you can refer table SNRO and check your buffer... your basis guys should help in this
In Account based COPA, PSG is determined at sale order itself.. refer note 1351257 for more details
Regards
Ajay M -
Hi all,
I activated the Account Based COPA, but why customer & product (which is the fixed characteristics from SAP) can not be taken during the report execution.
Everytime I try to see a report with those characteristics it always come back as unassign field.
Can anyone help me regarding this problems?
Thanks.
LeaHi,
Costing-based Profitability Analysis is the form of profitability analysis that groups costs and revenues according to value fields and costing-based valuation approaches, both of which you can define yourself. It guarantees you access at all times to a complete, short-term profitability report.
Account-based Profitability Analysis is a form of profitability analysis organized in accounts and using an account-based valuation approach. The distinguishing characteristic of this form is its use of cost and revenue elements. It provides you with a profitability report that is permanently reconciled with financial accounting.
You can also use both of these types of CO‑PA simultaneously.
Hope this helps.
Rgds
Manish -
Characterstics Assignment in Accounting Based COPA Config.
HI,
How to give Characterstics in Accounting Based COPA Config. and what is the TCode....
regards
JKHi
It is strongly recommended, however, that you do not activate both types of CO-PA. The
major reason being is that you will have significant table size impacts. You must be careful
with account based CO-PA as this creates additional line items in the existing CO tables of
COEP (actual), COEJ (plan), COSP & COSS (summary records). Hence if you want to do any
cost center reporting, say, from any of these existing tables you will run the risk that
performance will be degraded by these additional and unnecessary records.
The only advantage of account based over costing based CO-PA is it's ability to
automatically reconcile back to FI, in much the same manner as you would reconcile
cost center accounting back to FI. However you don't have the flexibility in account
based CO-PA to perform valuations using product cost estimates etc. as you do in
costing based CO-PA. If the reason you were advised to turn on account based CO-PA
as well as costing based was to facilitate reconciliation, it is suggested that you look
at alternatives that won't have the same negative impacts that turning on account
based would have. In addition to the serious table space issues, it is not that easy to
turn on and off account based at will (especially in production).
Instead what you should look at doing is creating a series of reports that enable you to
reconcile costing based CO-PA back to CCA/PCA and FI, if this is required. The complexity
of the costing based functionality you have used will determine the complexity of the
reports that will be needed to reconcile back, but it can be done without turning on
account based CO-PA.
Regards -
Hi co experts,
In COPA divided two ways one is costing based copa and another one is accounting based copa
I have worked in costing based copa.
My query is in which situation we can use accounting based copa and what are the settings I have do in STD SAP,
Kindly explain the total accounting based copa concept and required settings
Regards
venkataswamyHi
It is strongly recommended, however, that you do not activate both types of CO-PA. The
major reason being is that you will have significant table size impacts. You must be careful
with account based CO-PA as this creates additional line items in the existing CO tables of
COEP (actual), COEJ (plan), COSP & COSS (summary records). Hence if you want to do any
cost center reporting, say, from any of these existing tables you will run the risk that
performance will be degraded by these additional and unnecessary records.
The only advantage of account based over costing based CO-PA is it's ability to
automatically reconcile back to FI, in much the same manner as you would reconcile
cost center accounting back to FI. However you don't have the flexibility in account
based CO-PA to perform valuations using product cost estimates etc. as you do in
costing based CO-PA. If the reason you were advised to turn on account based CO-PA
as well as costing based was to facilitate reconciliation, it is suggested that you look
at alternatives that won't have the same negative impacts that turning on account
based would have. In addition to the serious table space issues, it is not that easy to
turn on and off account based at will (especially in production).
Instead what you should look at doing is creating a series of reports that enable you to
reconcile costing based CO-PA back to CCA/PCA and FI, if this is required. The complexity
of the costing based functionality you have used will determine the complexity of the
reports that will be needed to reconcile back, but it can be done without turning on
account based CO-PA.
Regards -
KEA0 Deactivating Account-based PA
Hello SAP Guru,
Currently my COPA has both costing-based and account-based activated. I would like to deactivate account-based but I am not sure of all the steps involved other than uncheck the box for account-based in the config. Also, we are currently live with COPA, what are some of the things I should watch out for by turning off account-based in the production environment.
Thank you for your help.
HTKindly remove the activation in KEKE and save it without assigning the costing based COPA. Then in KEA0, select the operating concern and go to the menupath extras-settings where you will be able to remove the flag on account based COPA. Then you need to save the settings and generate the operating concern. After completing this, you may activate
the costing based copa in KEKE.
In the transaction OKKP (in the view activate components/control indicators) you have to change the customizing to Component active for costing based profitability analysis (2)
The data for the account-based CO-PA is written into the already existing CO-tables: COEP, COEJ, COSP und COSS. So there will be no impact on the tables.
Reposting existing documents ( like invoices) could be a problem since at the time of posting there was a account based COPA document. So at the time of reversal system will expect the same else will throw error KI144. This error message can be changed into an information or a warning message .Read note 98262 regarding this. This problem could also come for documents 'in process' i.e if sales order and GI has been done with account based COPA and at the time of billing it is inactive.
The cost accounting document created with account based CO-PA active is a different one than that with account based turned off. If account based isn't active the posting leaving CO-OM is put to a reconciliation object. If account based is active the same posting will go to a profitability segment for account based CO-PA. This 'trick' made the introduction of account based CO-PA possible without creating extra tables. The reconciliation object is naturally on a higher aggregation
level, so that the number sum records in CO is smaller than with account based CO-PA active.
There is a note that describes the differences between the
costing-based and the account-based Profitability Analysis types. Please review the attached note 69384.
Nevertheless please test this throughly first in your test-system before going live in production -
Costing based and account based
HI All
Kindly let me know difference between costing based copa and accounting based copa with examples
Thanks & Regards
PhaneendraTwo forms of Profitability Analysis are supported: costing-based and account-based.
Costing-based Profitability Analysis is the form of profitability analysis that groups
costs and revenues according to value fields and costing-based valuation approaches,
both of which you can define yourself. It guarantees you access at all times to
a complete, short-term profitability report.
Account-based Profitability Analysis is a form of profitability analysis organized in
accounts and using an account-based valuation approach. The distinguishing
characteristic of this form is its use of cost and revenue elements. It provides you with
a profitability report that is permanently reconciled with financial accounting.
You can also use both of these types of CO-PA simultaneously.
(courtesy: help.sap.com)
It is strongly recommended, however, that you do not activate both types of CO-PA. The
major reason being is that you will have significant table size impacts. You must be careful
with account based CO-PA as this creates additional line items in the existing CO tables of
COEP (actual), COEJ (plan), COSP & COSS (summary records). Hence if you want to do any
cost center reporting, say, from any of these existing tables you will run the risk that
performance will be degraded by these additional and unnecessary records.
The only advantage of account based over costing based CO-PA is it's ability to
automatically reconcile back to FI, in much the same manner as you would reconcile
cost center accounting back to FI. However you don't have the flexibility in account
based CO-PA to perform valuations using product cost estimates etc. as you do in
costing based CO-PA. If the reason you were advised to turn on account based CO-PA
as well as costing based was to facilitate reconciliation, it is suggested that you look
at alternatives that won't have the same negative impacts that turning on account
based would have. In addition to the serious table space issues, it is not that easy to
turn on and off account based at will (especially in production).
Instead what you should look at doing is creating a series of reports that enable you to
reconcile costing based CO-PA back to CCA/PCA and FI, if this is required. The complexity
of the costing based functionality you have used will determine the complexity of the
reports that will be needed to reconcile back, but it can be done without turning on
account based CO-PA. -
GL account based on account assignment group
Set the GL account based on the account assignment group of the customer. How is it done?
hi Zarah,
in enhacement SAPMF02D you can check if the right recon. account is selected, however you cannot change, but you can issue an error message.
hope this helps
ec -
Mapping an account based on a column in source file.
I need to map an account based on the value of a different column. It is not used in FM so I don’t think I can use the varvalue function. So in this case based on store 1000 and account 1103-000 I need to map to 22222. For combination store 20000 and account 1203-000 I need to map to 33333. I can’t use concatenate in my import format because the mapping table would need to be huge to accommodate all possible combinations of account and store. Any ideas?
co 005,fy2009,jan,1000,1103-000,529749.41 map to 22222
co 005,fy2009,jan,2000,1203-000,1521.50 map to 33333
co 005,fy2009,jan,1000,1203-000,-1182514.62 map to 33333
co 005,fy2009,jan,0000,1203-000,-41480.28 map to 44444
Edited by: user6464465 on Mar 16, 2010 10:26 AMDo you have any available user defined fields that you could use in FDM? You could have this mapped to a Custom 4 in HFM, or an available custom in Essbase depending on your application and utilize conditional map scripts (Look up VarValues in the Admin guide) if there is not a large number of accounts.
JTF
Maybe you are looking for
-
Transaction iview Unable to Connect to Backend
Transaction iview Unable to Connect to Backend Hi guys, I am new to SAP and i am having several issues. Right now i am stuck here, in the NetWeaver Portal: I have created a Transaction iview and a System with Alias "SAP_R3". When i preview the iview
-
After instaling Mavericks, my Mac has slowed down so much, when I turn on my Mac it takes forever to load, and after it loaded, takes longer (then what it did before) to load any program. Any help please? My specs: MacBook PRO 13" late 2011, 4Gb RAM,
-
Merging numbers documents into single PDF for emailing
I have 23-50 numbers documents (invoices) that I want to send as one single PDF (to save time). When I select them all in Finder and open in Preview they are not full size and are rotated the wrong way. When I open them seperately in Numbers and cmd
-
I need help converting a file to a word document to edit it
How do I convert the file to a word document for editing?
-
"OracleBI Spreadsheet Add-In" â bug on the page items
I detected that "OracleBI Spreadsheet Add-In" has a bug on the page items. It occurs when I have more than one page item. What happens is that all the page items (except the first), donât permit to select other values. This is, I can click in the C