Dafault document type in MIR7 transaction

HI Friends,
Need your help on the following issue
For MIR7 transcation in OMR4 we configured the default document type as RE . When ever we use MIR7 the default doc type was taking as RE. It is fine
But ,all of as sudden when we use MIR7 today the default doc type is taking as "RN" . This is happening for all users .We did not make any change in OMR4 and still default doc type for MIR7 shows as "Re" in SPRO
Could some one help what would have caused the issue? Is there any other setting where we can make default setting for document type.
Thx
Deva

Hi ,
Thanks for your help
The problem is solved.
Some one has activated the Transcation variant which was created for default document type in MIR7
Thx
deva

Similar Messages

Document type for Asset Transactions

Hi,
I would like to know where the document types for asset transactions i.e acquisition, transfer,retirement are defined.
Thanks
Suresh

Hi,
A073
A074
A076
A077
Best Regards
Ashish Jain
Message was edited by:
Ashish Bohara

Restrict the user   based on document type on migo transaction-prepare GRN

Hi,
We are running ECC6.0 R/3 system.We had a requirement as follows
In MIGO transaction , we want to restrict the user on document type i.e. we want that a particular user can prepare GRN for document type STO only. He cannot prepare GRN for other document type.
We checked SU24->maintain check indicators for transaction codes->enter migo->execute->check indicator.This returned us the authorisation objects present in Migo transaction.We checked the help of all these objects,but none of them we found suitable for above mentioned requirement.We were planning to find out the proper authorisation object to add to Profile generater.
The following is the objects which we have checked for.
A_B_ANLKL-->     Asset Postings: Company Code/Asset Class
A_B_BWART-->     Asset Postings: Asset Class/Transaction Type
B_USERSTAT-->     Status Management: Set/Delete User Status
B_USERST_T-->     Status Management: Set/Delete User Status using Process
C_AFKO_AWK-->     CIM: Plant for order type of order
C_CACL_DSG-->     Interface Design
C_DRAW_BGR-->     Authorization for authorization groups
C_DRAW_DOK-->     Authorization for document access
C_DRAW_TCD-->     Authorization for document activities
C_DRAW_TCS-->     Status-Dependent Authorizations for Documents
C_KLAH_BKP-->     Authorization for Class Maintenance
C_STUE_BER-->     CS BOM Authorizations
C_STUE_WRK-->     CS BOM Plant (Plant Assignments)
C_TCLA_BKA-->     Authorization for Class Types
C_TCLS_BER-->     Authorization for Org. Areas in Classification System
C_TCLS_MNT-->     Authorization for Characteristics of Org. Area
F_BKPF_BUK-->     Accounting Document: Authorization for Company Codes
F_BKPF_BUP-->     Accounting Document: Authorization for Posting Periods
F_BKPF_KOA-->     Accounting Document: Authorization for Account Types
F_FICA_FOG-->     Funds Management: authorization group of fund
F_FICA_FSG-->     Funds Management: authorization group for the funds center
F_FICB_FKR-->     Cash Budget Management/Funds Management FM Area
F_KNA1_APP-->     Customer: Application Authorization
F_LFA1_APP-->     Vendor: Application Authorization
F_SKA1_BUK-->     G/L Account: Authorization for Company Codes
G_GLTP -->       Spec. Purpose Ledger Database (Ledger, Record Type,
                               Version)
J_1IDEP_SL-->     Authorization object for depot sale transaction
J_1IEXC_OT-->     Authorization object for Other Excise Invoice Create
J_1IEX_PST-->     Autorization object for posting Other Excise invoice
J_1IGRPT1-->     Auth. for PART1 at GR
J_1IINEX -->            Incoming Excise Invoice
J_1IRG23D-->     Authorisation object for Depo Transactions
K_CCA-->                     CO-CCA: Gen. Authorization Object for Cost Center
                                Accounting
K_CSKS     -->                CO-CCA: Cost Center Master
K_CSKS_SET-->     CO-CCA: Cost Center Groups
K_PCA-->                    EC-PCA: Responsibility Area, Profit Center
L_TCODE-->                    Transaction Codes in the Warehouse Management System
M_ANFR_BSA-->     Document Type in RFQ
M_ANFR_EKG-->     Purchasing Group in RFQ
M_ANFR_EKO-->     Purchasing Organization in RFQ
M_ANFR_WRK-->     Plant in RFQ
M_BEST_BSA-->     Document Type in Purchase Order
M_BEST_EKG-->     Purchasing Group in Purchase Order
M_BEST_EKO-->     Purchasing Organization in Purchase Order
M_BEST_WRK-->     Plant in Purchase Order
M_MATE_CHG-->     Material Master: Batches/Trading Units
M_MATE_STA-->     Material Master: Maintenance Statuses
M_MATE_WRK-->     Material Master: Plants
M_MRES_BWA-->     Reservations: Movement Type
M_MRES_WWA-->     Reservations: Plant
M_MSEG_BMB     -->Material Documents: Movement Type
M_MSEG_BWA-->     Goods Movements: Movement Type
M_MSEG_BWE-->     Goods Receipt for Purchase Order: Movement Type
M_MSEG_BWF-->     Goods Receipt for Production Order: Movement Type
M_MSEG_LGO-->     Goods Movements: Storage Location
M_MSEG_WMB-->     Material Documents: Plant
M_MSEG_WWA-->     Goods Movements: Plant
M_MSEG_WWE-->     Goods Receipt for Purchase Order: Plant
M_MSEG_WWF-->     Goods Receipt for Production Order: Plant
M_RAHM_BSA-->     Document Type in Outline Agreement
M_RAHM_EKG-->     Purchasing Group in Outline Agreement
M_RAHM_EKO-->     Purchasing Organization in Outline Agreement
M_RAHM_WRK-->     Plant in Outline Agreement
Q_TCODE     QM -->         Transaction Authorization
S_ADMI_FCD-->     System Authorizations
S_ALV_LAYO-->     ALV Standard Layout
S_BDS_DS-->     BC-SRV-KPR-BDS: Authorizations for Document Set
S_BTCH_ADM-->     Background Processing: Background Administrator
S_BTCH_JOB-->     Background Processing: Operations on Background Jobs
S_CTS_ADMI-->     Administration Functions in Change and Transport System
S_DATASET-->     Authorization for file access
S_DEVELOP-->     ABAP Workbench
S_DOKU_AUT-->     SE61 Documentation Maintenance Authorization
S_GUI-->                     Authorization for GUI activities
S_OC_DOC-->     SAPoffice: Authorization for an Activity with Documents
S_OC_ROLE-->     SAPoffice: Office User Attribute
S_OC_SEND-->     Authorization Object for Sending
S_PACKSTRU-->     Internal SAP Use: Package Structure
S_PRO_AUTH-->     IMG: New authorizations for projects
S_RFC-->                     Authorization Check for RFC Access
S_SCD0     -->                Change documents
S_SPO_DEV-->     Spool: Device authorizations
S_TABU_DIS-->     Table Maintenance (via standard tools such as SM30)
S_TCODE     -->                Transaction Code Check at Transaction Start
S_TRANSLAT-->     Translation environment authorization object
S_TRANSPRT-->     Transport Organizer
S_WFAR_OBJ-->     ArchiveLink: Authorizations for access to documents
V_LIKP_VST-->Delivery: Authorization for Shipping Points
V_VBAK_AAT-->Sales Document: Authorization for Sales Document Types
V_VBAK_VKO-->Sales Document: Authorization for Sales Areas

Have you executed a trace while a functional user executes the transaction code for the specific parameters? (i.e. document type). The trace will then show which objects are being checked; then look at the object documentation in txn Su21 to determine if there are any ways to restrict on the particular value; in some cases, if the authorization group field is being checked, additional configuration is needed in order to implement the security (Su21 will explain in detail for the particular object).

New document Type for bank Transaction

Hello Gurus
My client place , If I post any Bank Transactions the system accepting for only BP/BR Document type
Now I am define new Document type , in this new document type itu2019s not accepting ( bank receipt )
System shows some error message:
Document Type should be BP / BR for Bank Transactions
Message no. Z_FI005
So I Want to post bank transaction in new Document type also , what type of configuration shall I do
Can Any one give me the solution
Regards
SRI

Dear Sri,
It seems that Validation has been defined in your system to prevent another document type to be used for the banking transaction....
You can check validation defined in transaction GGB0...
Check the validation assigned to your company code in transaction OB28..
Regards,
Chintan Joshi

Document type to be set blank in transaction code mr41,mrhr

Hi,
I want to set document type and currency field as blank whenever the user go for the transaction MR41 and MRHR. At present whenever user enter transaction MR and MRHR these two fields display some value which is there in memory id, i want to set these field as blank instead of getting the value from memory id. Please help me out if there is any solution.
Regards
karan

Hi,
Good morning and greetings,
Go to the transaction Code OBU1 and make the default Document Type for the transaction code MR41 and MRHR as Blank and the system will not propose the Default Document Type for the same...If you dont want the user to use a document type from History disable History in the SAP GUI options...Hope this meets your requirement.
Please reward points if found useful.
Thanking you
With kindest regards
Ramesh Padmanabhan

Limit document types for transactions

Hi Sapper's,
Besides using a validation, is it possible to limit document types for certain transactions Eg. FB60 - Doc Type KR and KA and KG ONLY.
Cheers

Hi
You can create a transaction variant for FB60 using trancode SHD0, select the document type and make it output display only.
This would prevent the users from using a different document type.
Hope this helps
Deepa

Document types per transaction

Hi Experts,
How to know which document types are determined per transaction?
Ex: what document type can be defaulted for the transactions like FB60 / FB65 etc.
Please indicate the config area.
warm regards
marias

Check the SPRO node under below path:
Financial Accounting (New)>Accounts Receivable and Accounts Payable>Business Transactions>Incoming Invoices/Credit Memos>Incoming Invoices/Credit Memos - Enjoy>Define Document Types for Enjoy Transaction
Regards
Sreenivas

How to define certain document type (BKPF-BLART) for certain movement (101)

Sometimes ( I think it is becuase of the tcode) certain purchase 101 movements create a WA type FI document and some other times purchase 101 movements create WE type FI documents. I have seen a table ( accessing from omba transaction) in which for diffenent tcode´s we have either WE or WA. If we always use migo transaction why sometimes in bkpf we have migo_tr, migo_gi, ....;....
How should I do in order to create always WE FI documents for purchase 101 movements?
Thanks in advance.

Check the settings in SPRO-MM-Inventory Management-Number assignemnt-Define number ranges for accounting documents.
Here you assign accounting document type to tcodes.
Normally , WA is used in receipts for MB1C/MIGO_GI tcode - for e.g for 561 mvmt type.
SAP recomends keeping this setting as it is.
SAP help text copied here for reference:
Define Number Assignment for Accounting Documents
In this step, you set the number ranges for the accounting documents which are created when goods movements or inventory differences are posted.
Accounting documents in inventory management
For accounting-relevant goods movements, the system creates two different documents:
material document
accounting document
Both the material documents and the accounting documents have their own document numbers. When inventory differences are posted, the system also creates an accounting document for the physical inventory document.
In this step, you only maintain the number assignment for accounting documents.
Document types
Accounting documents are split into document types to allow differentiated document number assignment, which is the basis for distinguishing between the various accounting operations. A number range is assigned to each document type. In a company code, you have to define number intervals for each number range and fiscal year.
In inventory management, the transaction determines which document type is used.
Example: Goods receipt for purchase order
Requirements
You have already defined the company code.
Default Settings
In the standard SAP System, the following document types are predefined for inventory management:
WA for goods issues, transfer postings, other goods receipts
WE for goods receipts with reference to purchase orders
WF for goods receipts with reference to production orders
WI for inventory differences
WL for goods issues with reference to deliveries (SD)
WN for net posting of goods receipts
PR for revaluation documents
Each document type is already assigned a number range. In company code 0001, number intervals are defined for each number range both for the current and the previous fiscal year.
Number range 49 with the year-related interval 4900000000 to 4999999999 is assigned to the document types for all goods movements, except goods movements with reference to purchase/production orders.
Document type WE is used for goods receipts with reference to purchase orders and production orders. This document type is assigned number range 50 with the year-related interval 5000000000 to 5099999999.
Please note that net postings of goods receipts (document type WN) are not active in the standard SAP System. If you want to post goods receipts net, you have to assign document type WN (instead of WE) to the transaction MB01.
Document type WI is used for posting inventory differences. This document type is assigned the number range 01 with the year-related interval 0100000000 to 019999999999.
SAP Recommendation
Activities
1. Check whether you can use the standard settings.
2. If not, you have to add new document types to satisfy your requirements:
a) Define a new document type under Financial accounting document
b) types.
c) Assign a number range to the document type.
d) Under Financial accounting number ranges, define the year-related number intervals for the given number range in your company code. If you do not want to use the year-related number assignment method, enter 9999 in the Year field.
e) Under Allocate document type to transaction, assign the relevant document type to the transaction codes of inventory management.
Document type PR (revaluation documents) is already assigned.
Notes on transport
You transport number range objects as follows:
Choose Interval -> Transport in the accounting document Number Range screen.
All intervals for the selected number range object are deleted in the target system first. After the import, only the intervals you export are present. The number statuses are imported with their values at the time of export.
Dependent tables are not transported or converted.
All other activities are linked to the automatic transport.
Edited by: Saurav on Jan 24, 2011 6:03 PM

Document type during Goods Receipt in Intercompany Transfer flow

Hi,
We create a PO, Delivery and GI in company A
We do a Goods Receipt in company B.
Can we customize that FI document type ZZ is used during Goods Receipt in company B?
Document type ZZ may only be used in the Intercompany flow.
Where can I customize this setting?
Thank you in advance,
Best regards,
Eric van Zundert.

Hi,
The following are the standard steps to create an accounting document type and assign it to a transaction.
1) In T-code OBF4, click on "Financial accounting document types" and create a new document type.
2)On the same T-code, Click on "Goods receipt document type" and assign the document type to the transaction.
3)On the same T-code, Click on "Financial accounting No range" and assign the number range for each document type based on company code and fiscal year.
Thanks and Regards,
Maheshwari

Purchase Order Document Type and Account Assignment

Hi ,
We have a requirement to control Account Assignment in Purchase Order Item line based on the Document type selected on the Purchase Order header.
Like if user selects Purchase Order document type "ZNB" (Customized created) , then he will only able to select "K" or Blank or "P" as account assignment and similary we want to limit other Account assignments based on the Purchase Document type.
How can we make this Control settings?
Regards
Shrey

Hi,
You can't really limit the account assignment categories per document type, at least not directly.
You can limit the item categories that can be used for a document type via configuration:
Materials Management > Purchasing > Purchase Order > Define Document Types
Within this transaction you can define which item categories are valid for a specific document type.
You can then define which account assignment categories are valid for each item category
Materials Management > Purchasing > Account Assignment > Define Combination of Item Categories/Account Assignment Categories
BUT
limiting the account assignment categories that are valid for an item category will affect ALL purchase order document types that this item category is valid for. And you can't create your own item categories as this is a SAP standard table that can NOT be altered.
Regards,
Monika

G/L account to restrict the document type selection in F-02

Dear All,
one of my client want that when ever he post any business transaction from F-02 the G/L accounts will determine the document type ,it will resctrict any other documnet type to be used.
for example if their is a payment to bank for bank changes he want only document type BK will come or cash payment only SK will come as default .
If that possible.
Kindly help

Goto TCODE:OBU1
There it is defined for all TCODEs , with default documten type and posting key....
you can change the same as your wish....it is one time as default
but it is cross client config,
and if you want control the document type for seperate transactions...you can control using the validations....that means in case of company code and doctype(sk)....GL should start with 1***series..like
VVR
Message was edited by:
Ramana

Document-Type not known for scanned invoice

Hi experts,
I assign in OAWD a scanned document (Vendor Invoice) with "Storing for subsequent entry" to an user.
Vendor Invoice is linked to TA F-43.
The message appears in the Business Workplace SBWP. After executing a window appears "Process document type (Enter Document)" but without document type and TA F-43 will not be called.
It looks like that the document lost the relation to document type and the transaction.
Has anybody experience with this issue?
Thank you in advance
Martin

Hi Martin,
I suppose you did configure the OAC2, OAC3, SOA0 (BKPF-CREATE) and OACA - with parameter Transactioncode eq. F-43
Now 1st try F-43 for your user in standard dialog mode. Working?
Does the scanned image come up at after executing the workitem? (it should)
Than the F-43 should be called. This has no other pre-set value. So FI document type (BLART) is not set in OAWD.
How far do you get?
Regards
Tomas H

Create DMS document from direct object transaction instead of CV01N

Dear Experts,
I have raised an issue for the same thing in past and got helpful reply also. However it is not working here. I have searched enough but did not get satisfactorily answer.
My requirement here is to create and store DMS document directly from the object attached to DMS document type instead of CV01N e.g. create PR ME51N, create project CJ20N etc.
So far I have done the required configuration to get create option in transaction while entering DMS document number. I kept document description field as an optional for respective document type and created and assigned role in Define profile step. Number range is internal. So I think all necessary configuration in place. Now problem here is when I am clicking on create easy document icon, it ask me to select document type and file from local machine also. But nothing is happening afterwards and document is not getting created and stored. Transaction return on screen without any number and so. Please help me out. Did I miss anything?
Looking forward for your reply. Points will be allocated for answer.
Best Regards,
Bhagat

Hi Bhagat,
Select the document type in question,navigate to "Define object links".Please verify if the following values have been maintained:
Screen no-233
When new version-1
Create document-1
Document version-1
Additional functions-checked
Post this,re-test the scenario and share the results.Also,do confirm if you are able to create documents of the above document type using CV01n transaction successfully.
Regards,
Pradeepkumar Haragoldavar

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

Document type SK

Hi,
the document type AB is used for cash payment(FBCJ) and reversal so its create confusion. As per requirement if we use document type SK for cash payment(FBCJ) then its reversal document will be AB,this is the scenario . Please advise me
Thanks,
Karuna

Dear Karuna,
SAP is very flexible in such scenario. You can create your own Document type SK and assign it to the Cash Journal configuration in Transaction code FBCJC0. When you create the new Document type SK you need to assign the reversal document type AB in transaction code OBA7.
In case you are using SAP latest version and had activated new GL accounting, then you need to further make configuration in Document Splitting in the following path
Financial accounting (NEW)-->General Ledger Accounting (NEW) > Business Transactions>Document Splitting--> Classify Document Types for Document Splitting
If my explanation has helped you in some form, kindly assign some points/rewards to me.
Thanks and Regards.,
Rama

Dafault document type in MIR7 transaction

Similar Messages

Maybe you are looking for