Document types need restricted to specific posting keys

Hi,
When posting a KR document type with transaction F-43 we are able to post GL posting key (40) and posting key(50) without ever entering a vendor posting key(31).
The question is how do we prevent this situation and make sure that a vendor posting key is used. We can use a validation rule but can this be done with standard configuration.
Thx,
-John

Use a Validation OB28. You can use document type or transaccion code(f-43) in order to make mandatory the posting key 31. Keep in mind that you would need to use the accounting key 40 in order to post the expense.
Regards

Similar Messages

Controlling Specific Posting Key Access by Security Roles

I am currently implementing Z-Option GLSU which is an excel based general ledger posting tool. The way it operates is that it runs FB01 and FBV1 as an SM35 batch job but basically allows a user to post to SAP without having to directly go into the SAP client.
There are security concerns now because users can change the posting keys to allow postings to areas other than the general ledger (vendor, customer, etc) though it may not have been intended for that user's security profile. Can someone tell me if the user's security authorization will automatically prevent them from posting to a vendor for example (if they don't have FB60 access) or if that is not possible if there is some user exit that can specifically restrict access for those t-codes to posting keys 40 and 50? Any suggestions would be greatly appreciated, thanks.

FYI...
We were able to resolve this dilemma. Here is how....
We created two types of access: application and content. We applied the "user type" access to the application, web intelligence, in the CMC. Then, applied the Content security to the folders.
Thanks

SC based on item category po document type need to be choosen

Hi I have a require ment
Based on the SC item category or ........ etc    the PO document type must be choosen
ex: If SC item is   LIMIT item then when ur creating the po The PO document type must be zlimit PO ...some thing like
same way for service   --- PO doc tyep may be Zsercie PO
and same way for catalouge - PO doc type may be Z cat PO
please guide me how to do this
Basaed on the SC item the PO doc type need to be automaticlly choosen.
Sekhar babu dasari

Hi,
This has been discussed several times on this FORUM..Pls refer the foll threads for more details:
PR document type in the back end system
Change "Document Type in R/3 System" in SC
Changing document type of PO backend
Re: Change PO number/document type
BR,
Disha.
Do reward points for useful answers.

Duplicate BP Reference Numbers for same document type -need check on orders

Version: (2007A)
Description of requirements:
The user is allowed to create two sales orders for the same customer that have exactly the same BP Reference. When the user invoices one of them and then tries to invoice another, they are warned that there is already a document of the same type with this reference number. The problem is, they ship the goods out physically before they actually create the invoice document, so that by the time they are entering the invoice in the system, the goods have already been shipped twice, when they should only have been shipped once, If they were warned when they were adding or updating the order, then this could be prevented from happening. Same thing for vendors. Our customers would like to have the check for duplicate BP references on the purchase order as well as on the AP Invoices.
Business needs: Our Clientsu2019 customers are receiving duplicate shipments and this has a negative impact on their business relationship as it creates costly extra work and inconvenience for all.
Examples: Would like the same check that is currently on AR and AP Invoices for the same BP reference number existing already on the same document type implemented on the sales order and purchase order. When the user is adding an invoice for a BP and there is already an invoice for the BP with the same BP reference number, the user is warned and asked if they want to continue.
Current Workaround: None. As our customers often physically ship the goods before creating an invoice from the order, there are duplicate shipments and this is most inconvenient and costly to our customers as well as their customers.
Proposed solution: see above. This is a high priority item for our customers.
Sally Weinrauch,
Senior Support Analyst
Coastal Range Systems Inc.
Recipients of: SAP's Partner of the Year 2007 & 2005,
North America's Top Ten 2008, 2007 & 2006.
200 - 6400 Roberts Street, Burnaby, BC, V5G 4C9

hi,
Use SP_TransactionNotification to block sales order & purchase order from adding having duplicate bp reference number.
SAP Note 1258097 - Can the Suppliers Reference number be
made unique? activated approval procedure also for ar invoice.
It may solve problem.
Jeyakanthan

New Document Type Created but not allowing posting under that Document type

Hi Gurus,
I have created new document type 'JV' & assigned number ranges to that document type. But when I started posting the entries under this document type, system has thrown one error 'NO ACCOUNTING TRANSACTION VARIANT ASSIGNED TO FB01/JV'
Now after assigning transaction 000 (unspecified posting) & varaint 0001 to document type JV I can able to post the entry under this document type. (Classify document type for document spitting)
But I am not still sure whether my assignment to this particular document type is correct or not?
What is the basic criteria on the basis of which we have to select this assignment to particular document type?
Thanks
Sonal

What you have defined is correct. Since you are defining the document type jv meant for any type of posting and not restriciting like payments/receipts/vendors/customers.

Financial impact - Need to correct the posting key

Dear All,
During a configuration,by mistake in OBYC in transaction key COC, in posting key, a entry 40 and 50 in the field Debit & credit was made.
However, It was blank in initially. Now when going to change it by making it blank, system throwing an error as:
"Specify at least one posting key "
Message no. F4837
Please suggest me to rid out from this issue, I would like to maintain it again as blank.
Thanks in advance..........
Warm Regards
Jayesh

Thanks Bijay,
The values of posting key in COC were blank.
I changed and save that. but surprising thing is that, just immediately when I tried to made its blank.
system was not allowing to made it blank by thrown the error "Specify at least one posting key "
I do not want any value in it and would like as it was in initially i.e. blank (standard)

IDoc Basic Type needed for FI & CO posting with local & document currency

Hi All,
I am using basic type u201CFIDCCP02u201D which has local and document currency separately and posts to FI and CO segments but without any validations. This results in erroneous entries like posting to a cost center that cost center is not linked to company code.
Is there a basic type that I can use which posts to FI and CO with all validations similar to t-code FB01 and have fields to post local and document currency separately?
Thanks,
Leo

Hi Umesh,
Select 'Display Currency' button
Choose Local currency radiobutton and click Enter.
Let me know if it worked.....
Deepthi.

Document Type (Extension) restriction while uploading file.

Hi all,
Is there a way by which I can restrict uploading only certain types (rather extensions - .xls, .doc, .pdf etc) in cFolders.
Regards,
Reema.

>
Thomas Jung wrote:
> >I want to check 6th letter, if 6th letter is eq 'H', i want to upload data otherwise should display some message.
>
> Everything that you have been told about using the filename property of the FileUpload is correct. However you should note that the filename will not be available until after the file has already been upload to the server. So you can't stop the fileUpload based upon a check of the filename - its too late and the upload has already occured.
yeah that is true. but is there anyway to check it otherwise.
or we need to wait for something in coming versions 7.3 or 7.4.

Where to change posting key for Document type RG?

Hi ,
May I know where is IMG path to change posting key for Document type RG?
Thanks.

Hi,
Posting key is not assigned to the document types.
Posting key can be assigned to a particular trnsaction event etc., for example in OB40 for each transaction key in tax area, you can ddefine the posting key for bedit and credit.
However you have the option to create a validation to check that this particular document type is allowed to be posted with certain posting keys. Validation can be created in OB28, GGB0. The details are available in SDN. Please search that.
Regards,
Gaurav

Document Posting restriction using posting key,document type combination

Hi
We have a authorization restriction issue using posting key&document type&Accoutn type combination.
Requirement is
User A should be able to post to vendors only for particular posting key&document type.He should be able to post to with any other posting keys and document types to vendors.
We have tried with document type authorization object/vendor authorization objects from user profile but it does,t work.
can any one suggest some way please/
r
regards

Hi
I think you should be able to achieve the same through Validation rule:
Prerequisite
Document Type - XXXX
Check
User name = 123 and Posting Key = XX
You can set a an error messsage which would be bleeped when the check fails
Regards
Sanil Bhandari

Posting Key and Document type

Hello,
I have just detected an inconsistency in one of my SAP environment (Development). I have an invoice posted from the SD module, document type of this invoice is RV.
If there is a reason to cancell this invoice, the transaction used is VF11. The document type in SD for this cancellation is S1. Thereafter an FI document is generated with document type AB.
Even though the settings in both Production and Acceptance and Developement are the same.
I have realised that the initial document when cancelled (reversed) has an FI document RV and posting key 11. whiles in customizing the settings for posting keys and document types are different from what has been customized. Below is my current settings.
The posting key 01 has a reversed posting key 12 and the document type RV has a reverse document type AB. This customizing is in correct in SPRO.
Transactions : OB41 and OBA7
Can anyone help on this....
Thanks
Elvis

Hello,
Did you verify whether AB document type in OBA7 is marked in "Account Types allowed" the Customer checkbox?
If not, maybe that is why it is not selecting AB as the reversal document type for RV, even though it is set up in RV document the AB document type as reverse document type.
Other than this (if the mentioned above doesn't solve your issue), I would say there should be any user-exit that can be changing the document type, according to some specific business rule of your SAP client or even a substitution.
I hope it helps you.
Regards,
Daniel.

Document type for Posting to Accounting

The standard program RPRFIN00_40 is used to Post to Accounting.
The document type is specified at the Posting Doc.
it has a parameter ID BAR.
I assign BAR at the user's parameter via SU01, however the document type did not get default.
Any one can advice?

Hi All,
To put different document type other then the standard AB that SAP sets for all users, you will have to apply the SAP Note 340977 (if not applied already).
P.S. This note had come with support pack SAPKE47095.
After Implementing this note or import the relevant Support Package. We can then maintain the attribute DOCTYPE_PRFI in the view TA20SWITCH, and maintain the receipt type as a value. If the attribute is not created or if the value is blank, the default remains AB.
Thanks,
Vaibhav

Document type with posting level 12 not being carryforward

Hi gurus,
We are now implementing SEM-BCS 6.0 in the BI 7.0 server.
We have a document type u201CMIu201D which properties are:
Posting level: 12
Balance check: 0 error when balance note equal to zero
Application: Other
Posting: Manual posting
Inversion: No automatic inversion
The problem is that when we execute the Balance Carryforward in the subsequent year this is the only document type that is not being carryforward.
Why is this happening?
Thanks for your help.
Best regards.

This is by design
http://help.sap.com/saphelp_erp60_sp/helpdata/en/0c/ab0240536fe369e10000000a155106/content.htm
"Data records for preparatory postings for consolidation group changes are neither translated nor carried forward."
I'll try an example...
Company A is sold from company 1 to company 2 in June (EoP)
For periods 0 - 6:
BCS reports company A's balance sheet under company 1
BCS reports company A's income statement under company 1
starting period 7
BCS reports company A's balance sheet under company 2
BCS reports company A's 0 - 6 income statement under company 1
BCS reports company A's 7 income statement under company 2
this is managed through the posting level 02 12 and 22 document types, as well as PL30 if using CoI.
Assuming the period of first consolidation and period of divestiture were set correctly in the groups for company 1 and company 2, BCS wants to read all 0 - 6 data under group 1 and all 7 + data under group 2. This is obviously incorrect from an accounting standpoint and the PCC postings correct that.
So BCS books a PL02/12/22 in group 1 to zero out the balance sheet. It then books another set of entries in group 2 to write up the entire balance sheet in the new group.
However, once you get to the end of the year and run your BCF, the entire balance sheet is now sitting in period 0. The system is able to report company A's balance sheet under group 2 withou the aid of the PCC documents. Therefore, the system does not roll these documents forward into the new year.
The PCC documents were only required because of the periodic nature of the BCS data storage vs. the LTD nature of the balance sheet for reporting. Once the full LTD balance is available in a single period, as is the case just after a BCF, the PCC documents are no longer required.
Anyway, hope that made some sense. If not, I'd encourange you to create an Excel sheet replicating how BCS stores the data in the cube, perfrom a divestiture, and see why the system is not carrying forward the documents. This is how I came to understand it.
Now, if you're doing something "non-standard" with the PL12, all bets are off
Good luck,
Chris

Validation of document type in VA01

23.12.2008
Hi Gurus,
We create a Sales Order (eg. ZXXX) through a Z-development. My requirement is that this particular document type should not be created using t.code VA01. Need a validation for VA01 in the first screen itself ( where the document type, Sales Org, Dist Channel and Divn is entered) to restrict creation of document type ZXXX thru t.code VA01
Regards

Dear Sanjay,
If your requirement is - To restrict Creation of Sales Document Type "ZXXX" with Transaction Code: VA01
which, I have understood from your query:
My requirement is that this particular document type should not be created using t.code VA01.
...the same could be achieved by changing/ modifying the Transaction Group in to Sales Document type.
Path: T. Code: VOV8 --> Key-in Sales Doc. Type --> Go in to Detail-page --> Tab: Transaction Flow --> Field: Transaction Group
If, we maintain entry as "0", the sale doc.will be created with VA01
If, we maintain entry as "1", the sales doc. will be created with VA11.
Note: If, you change Transaction Group to "1" for Standard Sales Doc. Type - OR; it will be created with VA11 and not with VA01.
So, change the Transaction Group from "0" to "as reqd." for Sales Document Type "ZXXX" in VOV8
Best Regards,
Amit

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

Document types need restricted to specific posting keys

Similar Messages

Maybe you are looking for