Cannot Relate Look Table to Document Type

I am setting up a new R&D library. They would like to have attributes or
properties based off of the document type. Everytime I try to setup a
look table to use Document Type as the parents it clears it. If I
manually type Document Type in as the Related Table, it give the error:
"You may only relate a table to another table that exists, has no
parent, and is either Document Type or is user-defined table. Select a
table from the list."
Now it show Document type in the lookup selection but will not select
it. Is this a feature that was available at one time and removed or is
it a feature that has been disabled for some reason? Maybe a problem
with the snap-in.
Any Suggestions?

John,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://support.novell.com/forums/faq_general.html
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

Similar Messages

Customs document type cannot be determined for external document Type F8

Hello Experts
Need help
I am trying to transfer F8 to GTS 10.1 and getting following message in GTS Transfer log for export:
Customs document type cannot be determined for external document Type F8
New implementation
GTS 10.1 running with SP 12
ECC side Plug-In settings are fine. BAdi is Active.(There is no document mapping for F8/CUSDEC as it is not required in 10.1)
GTS side configurations are also fine. Checked several times by 4 sets of eyes!!
(Include general settings configurations, Customs communication configurations:)
(Defining technical medium, conditions/output parameters, defining messages for communication process,
defining determination for activity sequence and control settings for communication process)
Despite this I am not able to trnasfer F8 successfully
Can someone throw some light on this issue please?
Keshav Murthy
[email protected]

Hi Dhilipan
Here we go..
You asked me to check the following
Please check following things
1) Legal regulation is activated. - Yes Activated
2) Process template assigned to the legal regulation - Yes Assigned
3) Activity Sequence determination - Yes done
4) Open the activity sequence in under Control settings for Communication processes and check if there is a document type assigned to it. Table- /SAPSLL/TLEPAF - Yes done.
It is really puzzling.
Thanks
Keshav Murthy

Table for document type Number Range interval

Hi,
I want to know the number range interval for document type in the production system but I do not have authorisation for SPRO in the prd system.
Kindly let me know the table name to check this number range interval for the document type.
Table T003 stores only the number range and not the interval.
Thanks
Suresh

Hi,
The table which has document types is T003 but the number ranges are stored in a Structure IRDP. The number ranges are maintained directly in the production system.
regards,
radhika
Edited by: kolipara radhika on Aug 25, 2008 6:01 AM

Problem related to Configuration of Document Types ?

Hi All,
I am going in spro->MM->Purchasing->PO->Define Document Types. In this after clicking job work PO, I am clicking on Link Purchase Requisition,there comes somedata on right. I wanna know the meaning and purpose of each field like (Doc. Type,Description, Item Category Etc Etc.).

Hi Abhinav
Dty
Documnet type
Diffeent documnet types can be mentioned. On the basis of this document type you can differentiate the purchasing document eg Po, RFQ, SA etc
Description
Item category in purchasing document
Key defining how the procurement of a material or service item is
controlled.This determines feild d selection
NAA
Indicator: No account assignment:Thich check box will specifcy if no account assignment is allowed for PO
RS
Indicator: Contract release order/SA delivery schedule
Indicates whether release orders/releases or delivery schedules are
possible in purchasing documents such as contracts or scheduling
agreements.
DI
Dialog indicator
Indicator specifying that the system is to issue a message to the user
in the event of this combination of document types and item categories.
Regards
Vikrant

Relation between partner function & document type

Hi,
Is there any customization setting for vendor partner role & FI document type?
When I use the partner role PI(invoice presented by), MIRO document created against the vendor defined against the partner role 'PI'. However when I defined a new partner role 'XA' - copying from the partner role PI- MIRO document not created vendor against partner role 'XA'.
Your input should be highly appreciable.
regd,
sp sahu

Hi John,
The partner types allow us to distinguish between different business partners such as customer, vendor, employee etc and the partner functions represent the functionality or role each partner plays within the business transaction.
For example under the partner type Customer, you will find - Sold to party, Ship to party, Bill to party, Payer.
The business partners that exist in the market place are represented with a partner type in the R/3 system. Examples of business partners are customer, vendor, employee and contact person.
The following partner types are defined in the partner processing for the sales & distribution module
a.     AP contact person (06)
b.     KU customer (07)
c.     LI vendor (08)
d.     PE employee/personnel (09)
Assigning the partner functions in the SAP system determines the functions of particular partner in the sales process. One partner may take on several functions also.
REWARD POINTS IF HELPFUL
Regards
Sai

Number range table for MM document types

hi
Can anybody help me to find the number range for the mm document types.
Regards
rajeev

Hi,
go to transaction SPRO, Materials Management, then choose one of the following:
Purchasing or
External Services Management or
Logistics Invoice Verification or
Inventory Management and Physical Inventory
and look for the document types you would like to customize.
Like within purchasing for purchase order -> Define Number Ranges. In this step, you maintain the number ranges for the following purchasing documents:
RFQ/quotation
Purchase order
Contract
Scheduling agreement
After that you can add the number ranges to the document types under Define Document Types. ...
Please be more specific next time as MM document types can relate to 4 main areas within MM.
Regards,
Edit

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).

Getting number range interval for document type

Hi All,
My requirement is to display number range interval for any docnument type in SD.
I will elaborate my req. clearly.
We can see document type of SD in TVAK table. If we give document type for ex. ZOR the we will see number range internal assignment (NUMKI). The complete number range we can search through transaction VN01 through NUMKI value. But I didnt get any table to relate NUMKI or Sales document type and internal number range.
Please help me in searching database table to relate Document type or NUMKI and internal number range.
Regards,
Suresh.

Relation is as below:
TVAK --> AUART = "Sales Document Type"
NRIV --> OBJECT = "RV_BELEG" and
NRRANGENR = TVAK-NUMKI
Alternatively you can use FM: NUMBER_GET_INFO with the Number Range Number and Object to extract Intervals.
Regards
Eswar

BASIS--to restrict authorization for a PO document type & 122 movement type

Dear All,
Plz guide me how to restrict authorization for a PO document type & for a movement type 122 i.e. for eg. if a user has authorization for PO document type IC then he should not be able to rum movement type 122 for any T-code he runs.
Thanks in advance
Arpit
Basis

Hi,
Your request was not too clear to me.. As per my unde
Here is some details of Authorization object related to Purchase Order:
Document Type in Purchase Order( M_BEST_BSA )
Purchasing Group in Purchase Order (M_BEST_EKG )
Purchasing Organization in Purchase Order (M_BEST_EKO)
Plant in Purchase Order (M_BEST_WRK )
Document Type in Outline Agreement (M_RAHM_BSA )
Purchasing Group in Outline Agreement (M_RAHM_EKG )
Purchasing Organization in Outline Agreement ( M_RAHM_EKO )
Plant in Outline Agreement ( M_RAHM_WRK )
This can be helpfull to you to restrict authorization to PO..
In Organization Level, it can be restricted by Purchasing group, Purchasing organization and plant..
Regards,
Sandip

Error Document type "" not defined

Hi All,
I am getting below error message when i am trying to see the output of a query build on Infoset in SAP R3 system.
The Infoset is build on top of BKPF,BSEG and EKPO Tables.
Document type not defined
Message no. F5814
Diagnosis
Financial Accounting service: document type "" was not found in the document type table. There are two possible causes:
document type "" has not been set up in FI customizing
document type is supplied incorrectly from the calling application
System Response
System error.
Procedure
There are two possible measures:
set up document type "" in FI customizing
system error within the calling application - get in contact with the SAP Hotline Service.
Any input on above issue will be of great help.
Regards,
Anjali Singh

Hi Anjali,
In which system you are getting this error? Development or Production?
I think you have doc. type just in BKPF (Accounting documents headers). Check if you have any record with document type blank.
You can use t code SE16N for this issue. When you are setting filter on field "document type" (BLART) you can see the list of values. Check if there is any blank item
Regards,
Omid

Credit Group-Document type settings.

Hi All,
i have created one order document type ZFAC for sale from mfg. plant.
company has 5 plants(each plant manufacures different products)
i need to have product division wise credit check.
ZFAC- credit Group- 01 for order -> Plant 1(Product A)
ZFAC- credit Group- 02 for Delivery -> Plant 2(Product B)
ZFAC- credit Group- 03 for PGI -> Plant 3(Product C)
how to achieve this? i cannot create 3 different order document types for 3 different plants.
Reg,
Amol

Dear Amol,
As per your requirement, please test after doing the following settings.
You have to create 3 CCArea based on your business requirement.
lets say it is 1000, 2000 and 3000
lets say we have 3 risk category 001/002/003
We have 3 credit groups 01(sales order /02 delivery /03 PGI)
You can find the configuration for credit management in the WIKI or in FORUM itself.
Hence i will be mentioning only the deviations which you need to make from those standard configuration.
ccarea to company code assignment need to be done based on the configuration steps.
In ovfl, you need to specify the credit control area for the sales areas.
you have to assign different credit control areas created for the 3 sales areas (division)
Now in ova8, there is a combination of credit control area / risk category / credit group.
For the division which needs check in sales order level, in OVA8 for the combination 1000/003/01
check the required checks / blocks and reactions (you can decide whether the check need to be on credit amount or oldest open item or any other factor -- refer the configuration for credit management)
for the remaining combination ie, 1000/003/02 and 1000/003/03 do not maintain any checks.
For the division which needs check in delivery level, in OVA8 for the combination 2000/003/02
check the required checks / blocks and reactions (you can decide whether the check need to be on credit amount or oldest open item or any other factor -- refer the configuration for credit management)
for the remaining combination ie, 2000/003/01 and 2000/003/03 do not maintain any checks.
For the division which needs check in PGI level, in OVA8 for the combination 3000/003/03
check the required checks / blocks and reactions (you can decide whether the check need to be on credit amount or oldest open item or any other factor -- refer the configuration for credit management)
for the remaining combination ie, 3000/003/01 and 2000/003/02 do not maintain any checks.
check and revert back after testing.
One limitation of this scheme (if it works as per requirement ) is that we need to maintain seperate credit limit for the customer in all the 3 divisions.
Thanks & Regards,
Hegal K Charles

DTW - UDT of Document Type

Hi,
Is it possible to implement DTW to UDT of Document Typeu2026 it displaying my UDT in Business object [drop down selection] selection... But while mapping fields itu2019s displaying code and name in target fields. I didnu2019t map this field with any one my fieldu2026. But it displaying error - "To generate this document, first define the numbering series in the administration module application-defined or object defined error65171."u2026
My table is document type, it displaying code and nameu2026.. What mistake I did?
Help me on this issue.
Regards,
Ganesh K
Edited by: Rui Pereira on Jan 19, 2009 4:25 PM

You could use DTW to import data into UDT but Code and Name are two fields that are automatically created when you create a UDT. So you would have to add two columns in your DTW template
Code......Name.......other columns
NOTE: Code and Name have to be unique for each row so you can have
Code......Name.......
1.............1
2.............2
3.............3
The error that you getting might be due to an authorization issue. The user should have authorization to Document Numbering...though this error is totally irirelavent to what you are trying..
Suda

Query regarding document type

This is a basic part of FI
The Document flow in SAP-FI is categorized by the document types attached to them. All this document types differentiates the document flow, i.e. from where the accounting document was generated form SD, MM, FI etc. What SAP does is that for each Document types or rather groups of document types the data goes into four tables 1) Header table BKPF, contains the document type attached to the Document number
2) The Document table ( the table name starts generally with BS*) that is actually contains document number and its transactional details (debit amount and credit amount) for e.g. BSID and BSAD which contains the Sales order open and clear items
4) The Cluster table BSEG which contains the transactional amount of all the tables taken together, so it means that where ever the amount has come from it will go into the BSEG table and the transparent attached to it.
So what the program will do is:
1)     You will have a selection screen that will have a parameter entry for the Document type.
2)     Select all the table names from DD02L table where TABNAME = BS* and TABCLASS = TRANSP
3)     Think of the logic of how to connect the Document types to the BS* transparent table.

using document types u can fetch the revelant document numbers from the header table BKPF.using the fetched document numbers u can fetch the necessary data from the line item tables (BS*).

Document Type " AJ" and "KB"

Hello,
Can anyone let me know What does document type " AJ" and "KB" stands/means in SAP.
I will provide points.Please get back ASAP.
Thanks,
Bala

These are not Standard SAP document types that were delivered. Try look at the description and try to understand the need for creating these document type.
Also look at the document type properties to understand the doucment in a better way.
reward if useful.
sarma

Making condition type mandatory for a particular po document type

I have 2 po document type namely local po and international po. i want a particular condition type ZLCS to be picked automatically as soon as the user picks the po document type.

Hi,
   You may check the condition technique through a new condition table with PO document type. You may proceed as below:
   You may append the standard MM condition structure to include the PO document type field (in structure KOMPAZ), with the help of abapers . Add the field to condition catalogue in the path: OLME - Conditions - Define Price Determination Process - Extend Field Catalog for Condition Tables.
    Now, you can create condition table with document type field in M/03. Maintain the condition table in the access sequence in M/07. Assign the access sequence to condition type in M/06. Include the condition type in pricing procedure. Maintain condition record for the condition type with required document type in MEK1.
    Check the procedure and revert back in case of any doubts.
Regards,
AKPT

Cannot Relate Look Table to Document Type

Similar Messages

Maybe you are looking for