I am stuck on this account determination in SAP.

Please help me out. I have no where to go. I am duing this Global bike inc project for school. and stuck on the point below. this is the doccument flow of my problem.

All of you thankyou for helping me out. I really appreciate it. I am doing an integration of global bike inc its an fictional company as a project for school. I am posting more documents for my problem pleiase help.

Similar Messages

How to change account determination in sap asset accounting when there is a

Dear experts,
how to change account determination in sap asset accounting when there is a posting in previous one.
thanks in advance
Deboleena Ganguly

HI:
You can easily change the account determination of asset class . There is an OSS note regarding the correction of issue which you will face while changing account determination for which there are already posted fixed assets
Error message AC476 upon change of account in AO90 can be customized now
via transactions OBMSG...Application Area-AC
Note 202746
Under certain circumstances, it may still be necessary to make a change
to this account.By implementing this note, the above error message is
replaced by a warning message.Following account maintenance, you may
need to carry out manual intracompany transfers in FI in accordance with
Note 69225.
Regards
Edited by: Atif Farooq on Oct 31, 2011 11:44 AM

Account determination in SAP?

hii experts,
Account determination is major concern in SAP.
Whether account determination will be done only SAP MM consultant or any other module responsibilities in account determination?
Becas SAP has more business scenario , each will have account determination ??
So how ..
Thanks

Both FI and MM can do the account determination. FI does the account determination through OMWB and MM does it through OBYC.
Automatic Account Determination
This is perhaps the part that causes the most heartache for the FI Configurer.   For some reason, although it is an integration area, the FI team always ends up with responsibility for it. To do a good job you need a reasonable understanding of :
the business processes in the source modules
the FI account postings that they should be generating (what sort of account should be debited or credited etc)
the organisation structure and its relationships between the source modules
the reporting requirements that are expected from the General Ledger or Profit Centre Accounting
your chart of accounts
Sounds daunting doesn't it ? Here is a suggested approach ...
The IMG section under GL / business transactions / integration will take you through all the necessary account determination for the automatic postings that the system may need to post. You may not need all of these.You could maintain on an as needed basis. As the project teams test or prototype their expanding functionality, the SAP system will look for the accounts to which it should post. The error message and the SAP documentation and configuration does not always explain clearly which piece of account determination is used for which type of functionality, so it is sometimes difficult to be pro-active.
Being reactive has the benefit that hopefully each side (eg: MM and FI) can develop an understanding of what the business transaction is and therefore where it should be posting. Otherwise the MM person may not even be aware that he has generated a certain type of posting ! (You'd be amazed at some of the lack of ownership from a logistics consultant for the financial postings that they generate).
I will be explaining each account determination area simply and clearly with posting examples
SD to FI Account Determination (aka revenue account determination). This and MM seem to confuse people the most.
More later - This may take a while to complete........
In the meantime, some general warnings:
Whenever you change the field status settings for an account, ensure that you have verified that any automatic postings will be able to meet the requirements. EG: do not make business area mandatory if your system may make a posting which cannot determine and post the business area.
Consider specifying that accounts that are posted to automatically can only be posted to automatically. This will simplify reconciliation between the source module and the GL account should you need to do this.
SD-FI Account Determination and Postings
This is known in the IMG as "revenue account determination", but it covers a lot more than that (discounts, taxes etc). This is what determines how the financial impact of your SD Billing document is posted into the FI General Ledger.
The integration is controlled both in SD and in FI.
In SD there is a awesome area of configuration called the pricing procedures.   The pricing procedure determines the final price quoted to the customer for a particular product. This could be a complicated calculation taking into account the base price, any special prices or discounts that may apply to that scenario, taxes, freight charges etc. These prices or charges are called 'condition types'. This condition technique is used in a number of areas of SAP.
For now all we need to know is that each condition type is assigned to an account key (or in the case of rebates two account keys). You can assign multiple condition types to the same account key. There are a number of account keys that are pre-defined in the system. For example:
ERF freight revenues
ERL revenues
ERS sales deductions
EVV cash settlement
MWS sales tax
Now we start getting to the integration by mapping the account keys to GL accounts. But it is not as simple as that. It can be as flexible (ie: as complex) as you want. Start off with the most simple approach. Generally if one is using a good sales / revenue reporting tool (eg: CO-PA) then one does not need a lot of flexibility and variety in the GL accounts that are posted to. The level of detail that you need in GL should be determined by your financial statement reporting requirements - you may end up with only one Revenue account - it is a good bet!
So, taking the simple approach we would ignore most of the configuration possibilities : procedures, access sequences, condition tables etc (Yes it is that 'condition technique' kicking in again. Once you have worked through it once in one area and encounter it in another then hopefully you will be comfortable in knowing that most of the standard configuration can be left as is. )
We have to decide which access sequences we want to use (Five access sequences are defined in the standard SAP R/3 System). To keep it simple, let us assume we just use one - for example: the access sequence "chart of accounts/sales org./account keys".
The chart of accounts part is standard in all account determinations, so let us look at the rest. This access sequence allows us to specify different GL accounts for different Sales Organisations.
So if we had a billing document line item where the customer had some special deductions for one of the products he purchased, we could map accounts by Sales Organisation. To make it even simpler a document is within one Sales Organisation so we have an overall mapping as follows:
SD Line Item Condition type SD Amount Account Key Sales Organisation GL Account
1 Sales deduction for being such a nice guy $10 ERS 1000 800010 - Sales deductions for 1000
Sales deduction for special promotion on particular product $15 ERS
Base Revenue $200 ERL 800000 - Revenue for Sales Org 1000
Total for item 1 $175
2 Base Revenue $100 ERL 1000 800000 - Revenue for Sales Org 1000
Total for item 2 $ 100
Document Total $ 275
So the invoice that the customer gets (and that you can view in SD) will look something like:
Item (Note this is the SD Invoice line item) Amount
Item 1: $175
Item 2: $100
Total owing , 30 days terms etc: $275
The GL document posting that the system will make to FI will look something like this though:
FI Line Item Debit / Credit Account Amount
1 Debit (PK=01) Customer (AR Account) $ 275
2 Credit (PK=50) Revenue (GL Account) -$ 300
3 Debit (PK=40) Sales Deduction (GL Account) $25
Balancing to 0 as all GL documents must....
$0
Note : There is no direct relation between an SD Line item and an FI Line Item - they are different things.
Other considerations:
Remember that if you are using business areas, then depending on your configuration there, the system may create additional FI line items if it needs to post to different business areas. This may be even more of a reason why you do not need additional GL accounts. If your Sales Organisations already map to different business areas, you could use the GL accounts for all Sales Organisations.
Different access sequences will allow a broader variety of GL accounts (for example: by customer account) group. I strongly suggest having a good understanding of the reporting requirements expected to be supported from the General Ledger vs the SIS (Sales Information System) or CO-PA (Profitability Analysis) or (CO-PCA) Profit Centre modules before you create too many GL accounts. At the risk of repeating myself, the SD to FI account determination should only be as detailed as your statutory reporting requirements.   The reporting from other tools like Profitability Analysis are so much more flexible and powerful, you may never look at the General Ledger for internal profit reporting again except to do a reconciliation check.

Dual "Define Account Determination" under SAP Banking ??

Hi, all
There are two "Define Account Determination" transaction under IMG SAP Banking:
1) SAP Banking -> Loans Management -> Transaction Management -> Update Types -> Define Account Determination, which is the same as the one under FSCM/Treasury and Risk Management.
2) SAP Banking -> Loans Management -> Functions -> Accounting -> General Ledger Update -> Define Account Determination
By trial and error, it seems that the later one should be used in Loans Management. Could anyone tell me under which conditions should the former one be used?
Thanks.

We use product types under both SAP Banking->Loans and FSCM/Treasury and Risk, but I never realized that the Account determination for FSCM was included in the IMG path for SAP Banking->Loans.... When I learned Loans configuration, I was pointed in the direction of the Account determination under Functions, and never noticed it elsewhere.
I poked around the IMG a little and it looks like you would use the Account Determination under Update Types if you set up your Loans for parrallel valuation - that is if you need to maintain multiple valuations for Loans. It appears the Account Determination under Update Types appears to be needed for the postings to the parrallel valuation areas.
We don't use parrallel valuation for Loans, so that would be another reason I've not needed the Account Determination under Update Types.
From what I'm seeing in the IMG, I would say that if you only need one valuation for Loans, like we do, then you shouldn't need the Account determination under Update Types - just the one under Functions.
Regards,
Shannon

G\L Account determination per itemgroup

Hello,
I do have a question about the G\L Account determination in SAP B1. It is my task to find out which G\L Account(s) is/are being used by the program for all different kind of (trans)actions.
I checked out help.sap.com to check out the different GL accounts that can be determined but this wasn't very useful. There is only a description for GL account determination at company level (Administration > Setup > Financial > G\L account determination).
But after a hard (and long) time of searching I found out most of them myself. But I still need to know 6 of them. I can't find out where they are used and the description @ help is not good as well.
It is about these G\L accounts:
Sales credit account
Purchase credit account
Sales credit account foreign
Purchase credit account foreign
Sales credit account EU
Purchase credit account EU
I need to know when these accounts are being used in journal entries.
Thanks in advance,
Kind regards,
Hendri

Do you have access to the SAP Business One Document Resource Center? If you do, there is a 19 page PDF there that you should have. It is called 'How to Determine G/L Accounts for Automatic Creation of Journal Entries'.
You have to dig for it. There is no 2007 release, but the 2005 document is still good. In the Document Resource Center, look under
SAP Business One 2005 A SP01
then
How-To Guides 2005 A & 2005 A SP01
then
How to Determine G/L Accounts 2005 SP01 - US
This link may or may not work to get you to the How To Guide page where you will find the PDF:
https://websmp110.sap-ag.de/~form/sapnet?_FRAME=OBJECT&_HIER_KEY=701100035871000437965&_SCENARIO=01100035870000000183&

Revenue Account Determination in MM

Hi all,
Can i know the path for configuring Revenue Account determination in MM.
Regards,
Ramaswamy.

Dear,
This is how Account determination done in MM,
Movement types have key role as central account determination in MM side.
This account determination is for MM settings u2013 group RMK.
Account determination is based for combination of valuation grouping code, general modifier/account modifier, valuation class in SAP MM.
This will be defined for particular transaction event key. Transaction event key will inturn be defined for each movement type of SAP MM.
Basically GL account are assigned for certain combination of above. To put down in flowchart format-
SAP RMK group (MM)
Movement type-
Transaction event key-
GL account determination (one debit and one credit)- based on below combination
Valuation Grouping code/ Valuation Modification -- Tcode: OMWD
Account modifier -- Tcode: OMSK
Valuation class -- Tcode: OMWN
SAP will see transaction is made in MM, it searches the transaction event key from movement types. Based on valuation grouping code, account modifier and valuation class, determination will be done for GL account for debit and credit.
and concern G/L Account assigned in TCODE- OBYC
Need further clarification revert back.
Dear atleast putup a thanks in responce to people efforts before closing the issue
Regards
AJIT K SINGH
HAPPY TO HELP U
Edited by: AJIT K SINGH on Jan 6, 2010 5:22 PM

MM role in Account determination

hii
What are major MM consultant roles in account determination.??
Explain in detail...?
Thanks

Hi MM Group,
SAP MM Role in Account Determination :
This account determination is for MM settings u2013 Rajgeetha
Account determination is based for combination of valuation grouping code, general modifier/account modifier, valuation class in SAP MM.
This will be defined for particular transaction event key. Transaction event key will inturn be defined for each movement type of SAP MM.
Basically GL account are assigned for certain combination of above.
To put down in flowchart format-
- Movement type-
- Transaction event key
- GL account determination (one debit and one credit)- based on below combination
- Valuation grouping code (see definition below)
- Account modifier (see definition below)
- Valuation class (see definition below)
SAP will see transaction is made in MM, it searches the transaction event key from movement types. Based on valuation grouping code, account modifier and valuation class, determination will be done for GL account for debit and credit.
Some definitions and assignments
1) SAP MM Valuation grouping code: It is maintained as part of plant configuration same for all plants within company code having same chart of account.
This will be applicable only if valuation control is active for organization
2) SAP MM Account modifier: This is defined in each movement type. There may be more than one account modifier per movement type based on combinations of different special stock, movement indicator, consumption type.
3) SAP MM valuation class: This is maintained in material master. Material type is taken from material master. Account category reference is taken from material type which in turn is assigned to valuation class. GL account are assigned to valuation class
Example:
Material 1016101 is received in stock for plant SEPC by movement 101 in SAP MM.
1) Valuation class determination from material master of 1016101.
2) Valuation grouping code determination based on plant SEPC
3) Account modifier will be taken from movement type 101
4) Transaction event key will be always BSX for inventory posting. (that is programmed) and also defined in movement type
5) In account assignment, for combination of above GL account determination as we saw in above hierarchy.
Hope, it is useful for you,
Regards,
K.Rajendran

G/L account determination in VA01

Hi All,
I am trying to create a sales order in VA01. The incompletion log shows that G/L account was not determined. but looking at the Account Determination analysis, SAP is showing that a G/L account has been determined. Also, I was able to save orders for this material and customer before.
May I know the cause of this problem and how i can solve it?
Thanks!!!
Olyn

Dear Olyn,
if it is showing in Account Determination analysis that "G/L account has been determined", but still in the incompletion log it shows "G/L account was not determined", then the most possible chance is that after creating the Sales Order the G/L account was determined for Customer or Material.
You can be able to save the order even it is incomplete.
Solution: you can delete the line item from the sales order & again add it
Please let me know if this solution helps you or not.
Thanks
Bidhu

New account determination for GD goods issue (Delivery)

Hi all,
I have a requirement for a new account determination for delivery (mov. type 601)
In spite of accounts:
3210xxxx (account modif. BSX)
6120xxxx (account modif. GBB/VAX)
I'll need to have
6540xxxx / 3820xxxx
and
3820xxxx / 3210xxxx
For this situation I've created a new movement type (copied from 601) and created new account modif.
How can I customize OBYC to get this account determination?
Thanks in advance!
FT

For GBB/ZLV I've entered accounts 6540xxxx for both debit and credit entries.
But With this account determination it's just:
3210xxxx / 6540xxxx
but I'll need to have
6540xxxx / 3820xxxx
and
3820xxxx / 3210xxxx
Where can I mantain account 3820xxxx ?

Services account determination

Hello Gurus,
I have a question about services account determination.
I have created several valuation classes and linked them with different GL accounts. This is done because there is a requirement that the GL account should be determined according to the service category.
I have entered a valuation class into the service master record (AC02).
The account determination customizing is as follows: OBYC -> WRX -> val. modif. valuation class and GL account
The rules configuration for WRX is:
tick at valuation modification
tick at valuation class
However, during service delivery the GL account is determined from a blank valuation class entered at OBYC.
Why the GL account is not determined according to the valuation class as it happens with the materials?
Thank you in advance!

Dear ,
Kindly refer SAP note 64204 "MM-SRV: Determination of the GR/IR clearing account"
It says
Symptom
The GR/IR clearing account is not found when you post the service recording with
Transaction ML81.
Cause and prerequisites
The valuation class from the service master is not used for the GR/IR clearing account
determination (Transaction WRX) when posting the external services management.
Instead, valuation class ' ' is assumed.Thus, the same account is found as if you make
a posting for a purchase order with material number 0.This account determination
procedure was chosen because there are generally several services with different
valuation classes for each purchase order item.Thus, the GR/IR clearing account cannot
be determined unambiguously by means of the valuation classes from the service master.
Solution
1. In order to determine the GR/IR clearing account for the service entry sheet, add
an entry with valuation class ' ' in the account determination table for
transaction/event WRX. (Customizing path: 'Materials Management -> Valuation and
Account Assignment -> Account Determination -> Create automatic postings)
2. As of Release 4.0, a user exit is available which you can use to set the account
grouping code for transaction/event WRX in relation to the characteristics of the
purchase order. Thus the determination of the GR/IR account can be controlled
separately for material and service orders via the user exit. You can activate the
user exit via customer enhancement LMR1M002.
Edited by: redriver on Feb 9, 2012 2:42 PM

ICloud backup is unable to access the account, because email I used for iCloud account is been deleted. And my iPad is stuck with this note on a screen, can't go Settings. How do I delete my account?

iCloud backup is unable to access my account, because email I used for iCloud account is been deleted. And my iPad is stuck with this note on a screen, can't go Settings. How do I delete or edit my iCloud account?

You can eirther I think go on ITunes or if you can get to settings you would just go to iCloud.

How to have backend account determination working SRM

Hello everybody
Just came across thread
EBP G/L Account Assignment doesn't follow R/3 Account Determination
while I was searching for a solution to this same problem I'm having here as well. I already thought about using BAdI BBP_DETERMINE_ACCT. But I'm stuck to find the right backend function module (R/3 4.7) in order to ask for the G/L account coming from the backend account determination.
Did somebody already solve this and if yes is willing to share knowledge?
Any useful help will of course be rewarded with points!
Best regards,
Renaud

The function module in R/3 backend systems looks like that:
FUNCTION <your function module name here>.
*"*"Lokale Schnittstelle:
*" IMPORTING
*" VALUE(I_MATNR) TYPE MARA-MATNR
*" VALUE(I_BUKRS) LIKE T001-BUKRS
*" EXPORTING
*" VALUE(E_KONTO) LIKE T030-KONTH
*" VALUE(E_BSCHH) LIKE T030B-BSCHH
*" EXCEPTIONS
*" NOT_FOUND
DATA: w_subrc LIKE sy-subrc.
DATA: i_ktopl LIKE t001-ktopl.
DATA: i_bklas LIKE mbew-bklas.
CLEAR: w_subrc, i_ktopl, i_bklas, e_bschh, e_konto.
* Determine chart of accounts
SELECT SINGLE ktopl FROM t001 INTO i_ktopl
 WHERE bukrs = i_bukrs.
w_subrc = w_subrc + sy-subrc.
* Determine bklas from material
SELECT SINGLE bklas FROM mbew INTO i_bklas
 WHERE matnr = i_matnr
 AND bwkey = '1000'
 AND bwtar = space.
w_subrc = w_subrc + sy-subrc.
* Determine G/L account
CALL FUNCTION 'MR_ACCOUNT_ASSIGNMENT'
 EXPORTING
 bewertungsklasse = i_bklas
 bewertung_modif = '1000'
 kontenplan = i_ktopl
 konto_modif = 'VBR'
 soll_haben_kennzeichen = 'S'
 vorgangsschluessel = 'GBB'
 IMPORTING
 buchungsschluessel = e_bschh
 konto = e_konto
 EXCEPTIONS
 NOT_FOUND_T030 = 1
 NOT_FOUND_T030B = 2
 NOT_FOUND_T030R = 3
 NOT_FOUND_T030S = 4
w_subrc = w_subrc + sy-subrc.
IF w_subrc <> 0.
 MESSAGE i100(zpcg_mm) WITH i_matnr RAISING not_found.
ENDIF.
ENDFUNCTION.
The BAdI code in SRM looks like that:
method IF_EX_BBP_DETERMINE_ACCT~DETERMINE_ACCOUNT.
data: e_konto(10) TYPE C,
 e_bschh(2) TYPE C,
 wa_acct_data TYPE BBP_OCI_ENRACCT.
IF NOT item_data-ordered_prod IS INITIAL.
 CALL FUNCTION '<your function module name here>'
 DESTINATION item_data-product_src_sys
 EXPORTING
 i_matnr = item_data-ordered_prod
 i_bukrs = item_data-co_code
 IMPORTING
 e_konto = e_konto
 e_bschh = e_bschh
 EXCEPTIONS
 NOT_FOUND = 1
 IF sy-subrc = 0.
 LOOP AT acct_data INTO wa_acct_data
 WHERE line = item_data-line.
 wa_acct_data-g_l_acct = e_konto.
 MODIFY acct_data FROM wa_acct_data.
 ENDLOOP.
 ENDIF.
ENDIF.
endmethod.

ACCOUNT DETERMINATION "INTERCOMPANY SALES &3RD PARTY SALES" -kishore,AK ,

HI ,
 Rajesh , Kishore , AK ,
 well 2day i had client interview , he was very much stressing on " ACCOUNT DETERMINATION " process in intercompany sales , both in ordering comapny and delvering plant .
 At the same time account determination for 3rd party sales . well got some docs had brief capsule study , still stuck up .
 can u pl throw come clarity .
Regards,
jerry

Dear Jerry
Inter-Company Scenario in SAP is quite different than its literal meaning.
Inter-Company means, customer gives order to company code A (PlantA), but Plant A is not having stock, so it passes on to Plant B(CoCd B).So in Sales order of A you enter Plant B.
So now goods are delivered by Plant B to Customer and commercial invoice for customer is from CoCd A.
Cocd B just gives inter company invoice.
Now Comming to account determination , it totally depends on pricing procedure as account keys are there. There is not much difference from standard scenario, but you can have seperate G/L Accounts
If you are talking about sales between different company codes, then this can be handled having different sales document and thus different pricing procedure, you can ask customer , what is there requirement. and can say that it is like normal sales cycle only
Third-Party Processing
1) two standard process provided by SAP in the frames of the third-party processing:
a) pure third-party process: X creates the sales order, automatically purchase requision and later a purchase order will be created at the vendor. Then the vendor sends the goods directly to your customer and send the invoice to X. The company X creates the invoice to the customer Y.
b) individual purchase order: the same process, but the vendor sends the goods not to the customer directly, but first to X, and then the company X delivers the goods to the customer Y. The invoice is coming from Z to X (transaction MIRO), and then X creates invoice to Y.
you can refer the accounting document to get Idea of account determination
Regards
Jitesh

Account determination error - in creation of invoice

Hello experts,
i have an error in creation of invoice, after( pgi post goods issue)
will you please help me out to solve this error.
thanks & Regards,
yogesh raina

hello sir,
After going throuth this path it shows no gl account in account determination chart
as below
Condition type     Message     Description
ZPR0                                  123     Access KOFI not carried out (initialized field)
Access     Message     Description
10     123     Access KOFI not carried out (initialized field)
20     121     No G/L account found in Account determination type KOFI
30     123     Access KOFI not carried out (initialized field)
40     121     No G/L account found in Account determination type KOFI
50     121     No G/L account found in Account determination type KOFI
60     123     Access KOFI not carried out (initialized field)

Account determination error in VF02

Hai Guru,s
In VF02 when i am going ton release the flag to accounting i am getting following error "Posting keys for accounting determination for transaction EXD does not exist"
I checked VKOA EXD a/c key availabele .This is Exise duty account key.....In pricing procedure also EXD assigned to respectine condition type.............
where i did wrong.........which setting i missed........
Thank u in advance
Regards
Anjan

Dear Anjan,
For Tax Conditions you have to maintain Account Determination in OB40
Go to T-Code OB40
Select the Transaction - EXD - & Double click on it...
Mention required GL Account here...
Your problem would definitely get solved.
Hope this helps...
Give Points if useful...
Thanks,
Jignesh Mehta
Edited by: Jignesh Mehta on Sep 26, 2008 10:42 AM

I am stuck on this account determination in SAP.

Similar Messages

Maybe you are looking for