Ledger Group vs. Ledger Specific Document Types

Can anyone tell me the value in having a document type that is purely used for tracking accounting principle specific adjustments (GAAP Adjustments / STAT Adjustments / IFRS Adjustments / etc.)? If you already have various ledger groups hitting various accounting principles using a standard accounting document why would you need a ledger specific document type and when would it be used in normal business transactions instead of using a ledger group / standard accounting doc type combination?

HI,
In my company I set up IFRS-leading ledger, 2 local ledgers for each comp. code.
Accounting key-user found it easier and more traceable to make ledger specific postings using one special doc.type / number range for each ledger (group). "normal" doc. types can only be used to make posting in all ledgers assigned to each comp. code.
With this setting they can easy identify ledger group specific postings from postings happened to all ledgers using the same account number.
But,as you mentioned, its not really necessary to do so.
BR Christian

Similar Messages

Restrict display and posting for specific document types

Hi,
Is it possible to restrict display and posting for specific document types? I want to restrict authorization to SM document type in FS10N, and KSB1 tcode. Please help
Best Regards,
KIRAN.

Sandipan Choudhury wrote:
FS10N checks for this object ("Check" in Su24) but when user doesnot has this authorization object he gets access to all doc types and when the user is restricted to specific doc types (object present in user's authorization) he will get access to only those doc types. This is how the authorization check for F_BKPF_BLA works, in other words this authorization is Optional.
Sorry, but this is not true and seems to be an invention of how you would like it to work...
The coding works like this (generally):
    if sy-subrc ne 0.
      select single * from t003 where blart = postab-blart.
      check sy-subrc = 0.
      blrtab-blart = t003-blart.
      blrtab-brgru = t003-brgru.
      append blrtab.
    endif.
    if blrtab-brgru ne space.    "<--- important condition!!
      authority-check object 'F_BKPF_BLA'
           id 'BRGRU' field blrtab-brgru
           id 'ACTVT' field actvt.
      if sy-subrc ne 0.
        rcode = 4.
      endif.
    endif.
endif.
The "optional" aspect is whether or not the document type has an auth group on it in T003, failing which the check is suppressed.
If it reaches the check, then it found something and then checks that selected value.
Moral of the story:
--> Do not believe SU53.
--> Do not make assumptions from ST01 traces.
--> Read the documentation carefully.
--> Read the code to see how it really works (you can jump to the coding location from the trace).
Cheers,
Julius

How to get Exchange rate from SO to specific Document type in PO

Dear Experts,
I have an Intercompany scenario in which I need to have Exchange rate used in Sales Order into a specific document type in a PO. Is it possible to achieve this?
Thanks
Manish

Hi ;
To my knowladge , you have two options.
1- Fix exchange rate in PO
2- You can get exchange rate in Miro based on invoiced date.
Another ways will be development ...
Regards.
M.Ozgur Unal

Restriction of GR & IR for PO with specific document type

Hi,
How we can restrict doing Goods Receipt & Invoice Receipt for a Purchase order, instead they do the payment directly for the Purchase order item in FI. We need to restrict GR & IR for PO with particular document type.
Regards,
Srinivas

Hi,
Yes i do feel the same. Normally if a PO is created means system expects a GR and and IR .If you do not expect the ir means it is a free entry.
But however you can control the GR / IR through account assignment .please check the account assignment definition at SPROMMPUR-Account assignment-AAcategory.
Once the PO is created with account assignment the procurement is for consumption (non stock)
if it is a stocked procurement system will check the GR/IR indicator in the PO.
When a PO is created in MM module and the cycle is not completed , it will always show as open PO.I think the context for FI direct posting will be differrant.
Regards,

Business Document Navigator -- Show only specific document types

Hello to all,
I'm using the business document navigator.
With parameter excluding of method cl_bds_document_set=>call_navigator you can disable the standard document types are shown by passing the value NO_STANDARD_DOCS.
Is it possible to define document types that should be shown and aren't a standard document type?
Regards
Christian

It will return an error but yet it allow to be created under HOLD

Material Groups of specific Doc types

Hi, is it possible to default certain material groups in a specific document type?
Thanks so much.. Appreciate your help.
Thanks,
Paula

Hi,
For Service PO, you can set default material group in item level in ML91.
For material ( stock or no-stock)PO, The material group will be from material master.
Regards,
Biju K
Edited by: Bijay Kumar Barik on Aug 26, 2009 10:05 AM

Configuring Document Types by Ledger

There are 3 configuration steps for configuring document types:
1) Define Document Types in Entry View
2) Define Document Types in Entry View by Ledger
3) Define Dcoument Types in General Ledger View
What is the purpose of each step and how would I go about creating unique document types that would only be posted to in specific ledgers and have their own unique number ranges?
If I needed to create a document that posts across all ledgers can I just do step 1 and skip steps 2-3 for those document types?

Hai Hari
Define Document Types for General Ledger View
In this IMG activity, you define for Non-leading ledgers the document types for the documents in the General Ledger view. At the same time, you assign for each document type a number range to be applied in the assignment of document numbers:
u2022     You do not need to make these settings for your leading ledger because, in the case of this ledger, the document number in the entry view always corresponds to the document number in the general ledger view.
u2022     You only have to make these settings for any non-leading ledgers that have a fiscal year variant that differs in at least one company code from the fiscal year variant of the leading ledger in this company code. In this case, the document number in the entry view does not correspond to the document number in the general ledger view and you have to define a separate document type with document number assignment for the general ledger view.
For all non-leading ledgers that, in the company code to which the postings are made, have a fiscal year variant corresponding to the fiscal year variant of the leading ledger in this company code, the document number in the entry view always corresponds to the document number in the general ledger view.
Note
The need to define a document type for documents in the general ledger view depends only on whether the fiscal year variant of the non-leading ledger in the company code (to which the postings are made) differs from the fiscal year variant of the leading ledger in this company code. On the other hand, document type definition is independent of which the type of ledger group to which postings are made, that is, regardless of
o     Whether postings are made without a ledger group
o     Whether postings are made to a ledger group with a leading ledger as the representative ledger
o     Whether postings are made to a ledger group with a non-leading ledger as the representative ledger
Define Document Types for Entry View in a Ledger
Here, you make the settings specifying the document type for postings to non-leading ledgers.
Under Define Document Types for Entry View, you make the document type settings for postings in the entry view that effect all ledgers and for postings to the leading ledger.
Requirements
You work with a leading ledger and with non-leading ledgers.
Activities
To define document types for postings to non-leading ledgers, proceed as follows:
Set up a separate document type for these postings. Assign a unique number range to this document type for each ledger.
Example:
Document Type SX, Closing Postings, Ledger L2, Number Range FI
Document Type SX, Closing Postings, Ledger L3, Number Range FI
Note
By segregating the ledger-related postings (here, for the non-leading ledgers) in a separate number range, you ensure the contiguous assignment of document numbers at the ledger level for each number range.
Within a ledger group, the representative ledger determines the document types and number ranges applied. For this reason, you cannot perform this IMG activity for a ledger group.
If you use a ledger group to make account assignments for postings, it is only possible to verify that document numbers are assigned contiguously at the ledger level for the representative ledger.
Regards
Madhu I

Authorisation group and document type

Dear Experts
I want our users who are using transaction F.14 to be able to process document type ZF only. I have created a role and in the authorisation object F_BKPF_BLA
i can see field authorisation group and activity. What value i should put in the authorizatuion group object which will allow me to restrict users to work in document type ZF only
<removed_by_moderator>
Edited by: Julius Bussche on Apr 30, 2008 4:53 PM

Hi All,
Didnt know whether to start a new post or continue this one. Basically I have the same problem but I seem to be missing something fundamental (and I think it must be obvious!).
Dev Team:-
1) New transaction code created ZF10 by which amongst other things should only process the newly created document type ZF.
Myself (Security Team):-
1) All of our document types are defined in OBA7.
2) The specific document type is ZF that we want to restrict access to.
3) In V_TBRG I have defined the custom authorisation group ZDTF against object F_BKPF_BLA.
4) In SU24 I have defined against the custom transaction code ZF10 the authorisation object F_BKPF_BLA to be inserted with Activity values 01, 02, 03; and Authorisation Group ZDTF.
5) Create new role and add ZF10 which then populates the auth object and values above.
What I cant see / understand is how the document type is then restricted to ZF in the role as it isnt defined anywhere that the authorisation group ZDTF only allows access to document type ZF.
Any help on this will be greatly appreciated. PS Should I have created a new thread for this ?
Cheers
Steve

Restriction of Purchase Group on PO Document Type

Hi Experts,
We have different PO Document Type, and Purchase Group. Now, want to restrict Purchase Group based on PO Document Type.
For Example:
For PO RM Document Type only Purchase group P01 - RM allow in PO; for other purchase group system should not allow saving PO.
Please guide ...
Thanks in advance
With Warm Regards,
Dipen

Hi Dipen,
You can definitely restrict the users via Roles and Authorizations.
in the role for PO creation, the object for Purchasing Grp is M_BANF_EKG
field is EKGRP
Make sure that he has the value as P01(Only)
and the object for the Document Type is M_BANF_BSA
Field is: BSART:
give the field Value as RM
Hope it helps you.
Regards,
Yawar Khan

Document types - gl view & entry view in a gl

Hi Experts
Iam very much confused with the following.
When we are defining document types and document number ranges in ECC 6.0 what is and the difference between
1) Define Document types for entry view in a ledger
2) Define document types for general ledger view
3) Define Document Number Rangers for General Ledger View
Pl. explain clearly,
full points for clear answer.
Vijay
Edited by: VijayKumar Domakonda on Jan 8, 2008 2:08 PM

In General Ledger Accounting, the document types you define for the documents in the entry view need to be different to those for the documents in the general ledger view:
·        Document Types for Documents in Entry View
¡        For your leading ledger, you can use the document types delivered by SAP or you can define your own document types.
¡        For your non-leading ledgers, you only need to define separate document types for documents in the entry view for those ledgers that are used as the representative ledger in a ledger group.
·        Document Types for Documents in General Ledger View
¡        For the leading ledger, the document in the entry view corresponds to the document in the general ledger view. Consequently, you do not need to define separate document types for documents in the general ledger view.
¡        For your non-leading ledgers, you only need to define separate document types for documents in the general ledger view if the fiscal year variant of the non-leading ledger differs from the fiscal year variant of the leading ledger in a given company code.

Credit Limit Check - Exclude Specific Documents / Credits from Exposure

Hi,
I would like to know if it's possible to exclude specific document types (credits) from the credit exposure calculation used during credit limit checks.
The ideia is to exclude "DG" credits in customer GL that are related to Trade Deal/Agreements to avoid over-exposure.
Let me explain:
Currently, our credit management is configured to "Static" + "Open Items" for all credit groups in the CCA. Therefore, SAP calculates the credit exposure as:
          CE = OPEN ORDERS (S066) + OPEN DELIVERIES (S067) + OPEN BILLING (S067) + OPEN ITEMS (BSID)
Regarding "Open Items", I understand that SAP calculates the net value between all debits (receivables) and credits (returns, overpayments, etc...) already posted and not cleared in the Customer GL account. This rationale is correct since the credits are due to the customers and should be deducted from their exposure (i.e. "you may not pay them if you don't receive").
However, in our case, we also pay trade deals contracts (i.e. trade incentives and trade marketing investments) directly to costumers and apart from sales orders or credit memos. The flow is the following: (1) contracts are managed on a satelite system and interfaced to SAP; (2) contracts are created in the costumer GL as a credit (doc. type "DG"); (3) credits are sent to accounts payable for payment via F110.
Problem is that, contract credits volume is significant and are impacting customers credit exposure and limit check, resulting in greater exposure than allowed. That is, orders are being released while contract credits are open in the customer GL up to the max exposure, but when contracts are paid the exposure goes above the limit. For example:
Day 1:
          Costumer Credit Limit: 100
          Sales Balance: 30
          Open Itens: 50 (receivables: 70 / contracts: -20)
          Credit Exposure: 80/100
Day 2:
          Costumer Credit Limit: 100
          Sales Balance: 50
          Open Itens: 50 (receivables: 70 / contracts: -20)
          Credit Exposure: 100/100 (no additional orders are released)
Day 3:
          Costumer Credit Limit: 100
          Sales Balance: 50
          Open Itens: 70 (receivables: 70 / contracts: 0 - contracts are paid on day 3)
          Credit Exposure: 120/100 (exposure is above customer limit since contracts that were being deducted were paid)
Any ideas or thoughts? Is something wrong in the explanation above? Should contracts credits be treated through special GL?
Many thanks!

Hello Julie,
the 2nd, System behavior (how do you interact the credit limit check (yes/no question) via DI?)
Workaround:
Before you issue the Document, you may do a manual check: BP balance againt Credit Limit, and make deceision.
Regards
János

Document type restriction

To restrict access to specific document type (BLART) on transactions FBL5N and FB03, we applied the following settings:
- Assign authorization groups (BRGRU) to document types in OBA7
- Assign authorization groups (BRGRU) to roles in PFCG
- Assigning users to the appropriate roles
but all users can view all types of documents!
how I should proceed to restrict access to particular types of documents for users?
Many thanks in advance!
Ismail

Hi,
Please do to the following steps :
1. Go to SE16
2. Enter table name as TBRG
3. Click on Create
4. Enter Object F_BKPF_BLA
5. Enter Value - this will be yours authorization object value.
6. Enter Description
7. Save
8. Go to transaction code PFCG
9. Create a new role
10. Click on
11. Enter Object F_BKPF_BLA
12. Enter Value - this value is the value created by you in table TBRG.
13. Enter Activities
14. Generate .
15. Assign role to users.
Please remove authorization object F_BKPF_BLA from all the existing roles before assigning newly created role to users.
We hope your problem gets resolved by following this steps else revert.
Regards,
Tejas

Release of parked document affects other document types

Hello,
we are using the standard parked-vendor-invoice-with-workflow scenario in production since 1, 5 years.
Now we want to start using the parking function for customer invoices as well, but without release requirement and workflow.
For some reason the release scenario is automatically also activated for the customer invoices (document type DR) . I. e the "release necessary" flag is set automatically in the workflow tab strip in the parked customer invoice and the workflow (for the vendor invoice scenario) is triggered as well for the customer invoice.
We have configured a workflow variant and defined the document release as active from 1 SEK. We have assigned the wf-variant to a company code.
An approval path has been defined and assigned to the workflow variant, release approval group and the document type KR (vendor invoice). The approval path is also assigned to a workflow.
We thought that by defining the document type specifically in the assignment of the approval path to the combination workflow variant, release approval group and document type, we could restrict the release scenario to be activated only for a specific document type. This does not seem to happen. Is this a known bug?
Kind regards
Viveka Schwartz

Hi,
What is the OSS note?
Thanks,
Steph

Problem with document type on WF for parking document

Hello
Iu2019m actually working on the SAP workflow dealing with the FIPP object and the event u201Ccreatedu201D (FI park document transaction (FV60)).
The problem is that the WF is launched for all document types wich is not the need of the customer. Iu2019m looking for a solution to launch the WF for some specific document types.
Iu2019ve already tried to use the workflow variant, approval groups, paths and procedure with no success. (SPRO -> financial accouting-> accounts receivable and accounts payable -> business transaction -> incoming credit invoice memo -> make and check setting for document parking)
Thank you for help.
SL

Here is the solution I have eventually found :
1- Application of the OSS note 559276 which enables the customizing of the workflow variant (the transaction OBWD becomes here effective)
2- Assignment of the documents types, workflow variants and release approval groups with the transaction OBWD.
Therefore, the document types that are not defined in the transaction OBWD will not require validation (no workflow will be launched).
SL

F150 Dunning creation without increase Dunning level for document Type

Hellò everybody,
I have this request , How I can do a dunning Letter and for a specific Document type , must have always a Dunnng level 1 . I mean do not increase the Dunning Level every time.
For istance :
Every week we make one dunning run. This run has to include all open invoices from ordinary deliveries (dunning level 1 to 3) and also the open invoices for a specific Document type (dunning level 1).   This Specific doc.type have not dunning level 2 or 3 .
I have check on BTE and I have update 00001051 DUNNING: Read additional fields for MHND (BSID) with this Abap code :
IF I_BSID-BUKRS = 'KC01'.
        IF I_BSID-BLART = 'B2'.
      IF C_MHND-MAHNS IS NOT INITIAL.
        C_MHND-MAHNN = C_MHND-MAHNS.
      ENDIF.
    ENDIF.
ENDIF.
ENDFUNCTION.
But nothing happen ...
Who can help to me ?
Thanks in advance for everythings.
Anna Rosa

Hi Vassy , thanks for your prompt answer , I explain better with example :
first time Dunning : Customer AABB
Invoice 1 100   lev 1    Special Invoice
Invoice 2 200   lev 1
Invoice 3 300    lev 1
The Customer do not pay nothing
Second Time Dunning Customer AABB
Invoice 1 100   lev 1    Special Invoice
Invoice 2 200   lev 2
Invoice 3 300    lev 2
Thirt time Dunning Customer AABB
Invoice 1 100   lev 1    Special Invoice
Invoice 2 200   lev 3
Invoice 3 300    lev 3
I mean in the same Dunning letter for invoice 2 and 3 the level Dunning increase(as usual) for Special Invoice number 1 the Dunning Level   still remain 1.
I know that I can change Manually on open Item the Dunning level but I looking for if it's possible to this automatically.
Thanks a lot.
Cheers.
Anna Rosa

Ledger Group vs. Ledger Specific Document Types

Similar Messages

Maybe you are looking for