Document type control

hi
in my company i have two prequisitons
one is used for imports and one for domestic .Ineed to make the field account asignment category an mandatory field for the domestic purchase requisition and for imports i do not how can i do this
and
can u also specify how this can be done to a purchase order also
With regards
chaitanya

You can make account assignment category mandatory in configuration. The path in SPRO is Materials Management --> Purchasing --> Purchase Requisition --> Define Screen Layout at Document Level.
Remember to make it mandatory in the field selection key at Document Type level. In case the field selection key is same at the document type level, change the field selection key in the document type definition (under Define Document Types). This way you can have different field selections at the document type level.
Same way in Purchase Order also. Menu path in SPRO is Materials Management --> Purchasing --> Purchase Order --> Define Screen Layout at Document Level
Hope this helps.
Lakshman

Similar Messages

Billibg document type controling fields

Hi All
In billing document type controlling fields one field which indicates "credit memo w/val dat".
what is the importence of this field!
Regards
raj

hi,
Credit memo with value date
If the field "Credit memo with value date" is set, the reference billing document is not settled and the payment deadline date for the base billing document comes after the billing date for the credit memo, then field VALDT (fixed value date) in the credit memo request is filled with the payment deadline baseline date of the base billing document.
This does not happen if the payment deadline date of the reference billing document comes before the current billing date of the credit memo.
This is from the documentation on the field.
Rgds,
Rags.

Document type controll with respect to plant

Hi,
I have created two document type NB & ZB for purchase requisition , my requirement is whenever i select plant 1 in item level it should select N document type and for plant 2 ZB doc type, if end user select wrong document type for plant for ex: ZB for plant 1 system should give error message.
thnx.

You have to use ,user exist for that take help of your abaper

Document Type at Company Code Level

Hi All,
I need a clarification with reference to the Number Range for PO Document Type say for NB.
I am having two company codes which uses different number range against the Document Type NB. As we know the Number Range is client dependent, we must create two document types NB and ZNB (ex) to get digfferent Number Range to be effective.
I would like to know if any SAP Standard Solutions available without using two document types, controlling the Number Range with reference to Company Code.
Can any one know how to do this?
Thanks for the Help,
Prakash

Hi
SAP does not have any standard functionality , but you can use the User exit / Enhancement
MM06E003
Number range and document number
function exit - EXIT_SAPMM06E_001
in this you can write the logic for derivation of number range based on the Compnay code.
Maintain the Combintaion in a Z table. & derive the number range group from the table.
This is a well used user exit,
Thanks & Regards
Kishore

PR?PO document types

Hi
What is the purpose behind creating new document types for PR/PO/contact ? as i understood
1. u may need to define different document types for diff company codes according to client needs, to differentiate them better
2. u can assign diff internal/external number groups to each document type , so that it will be easy for searching/auditing purposes
3. this helps to take them through release strategy easily
Is there any other benifits other than this??
Regards
NSB

Hi,
The main purpose of document types is to map the business scenario. This is achieved via Account Assignment Category, Item Category and also additional features like assigning different number ranges etc for easy distinction among document type.
A document type controls which Account Assignment Categories and Item Categories are allowed which in turn controls whether for a particular document type GR is allowed or not (Blanket Orders, GR is not permissible), GR based IV is mandatory or not (Subcontracting scenario), GR is valuated or not (Consignment), Cost Center & GL A/c is mandatory or not, IV is possible or not (Consignment not possible, system generates Invoice) etc and many more.
Hope this helps you.
cheers
Yogi

Alternate document type for MRP requisition

Our purchase scenario is that all MRP purchased items must have an approved contract to move to a purchase order. In 95% of the cases, this will be true, but there will be that 5% that, due to expiration of the contract or quantity/value exceeded, a valid, approved contract will not be available. However, the purchase must still proceed.
Our thought is to create an alternate requisition type that the buyer could change the MRP requisition document to. This new document type would then be subject to requisition release strategy.
However, using an MRP generated requisition (creation indicator B), the document does not allow change of the document type. The new document type is a complete copy of the NB document type used in MRP proposal planning, including the number range. The only difference is that the new document type is subject to requisition release.
Changing the document type at the MRP group level won't solve the problem as very few materials will actually require this change. It would be temporary until the existing contract could be extended and approved or a new one created and approved. Also, it seems that the MRP group setting affects only the purchase order and not the requisition.
Is there a way for us to make this process work more smoothly than to have to copy the items from the NB document type to the alternate document type manually?

Assuming you have a material master involved, why not try MRP Group in TCode OMDT. You can assign the group to the material and that group can determine the PR type that is created.
MRP:doc.type purchase requisitions for standard purchase ord
    Identifier allowing a distinction to be made between various kinds of
    purchase requisitions in the SAP system.
    By means of the document type you can, for instance, differentiate
    between a standard purchase requisition and a requisition relating to a
    stock transport order, although both documents belong to the purchasing
    document category "purchase requisition".
Use
    Among other things, the document type controls number assignment and the
    selection of
Regards

Document type FO to have same layout as NB

Hi all,
I need to activate framework orders and I need to ensure that document type FO has the same layout as NB. Please would you tell me how/where to do this?
Also- do framework orders have a different number range compared to standard PO's?
Thanks in advance.
JJ

Dear,
Why you need screen layout for Frame work order document type same as standard PO?
The documnet type is created and is assigned to a screen layout as per the requirement e.g material group is madatory for document type FO and optional entry for document Type NB.If you will assign NBF screenlayout (standard) to FO order type it will behave as standard .
Document type controls scrren lay out,no range,allowed item categories and freference requisitions.you can assign same no range to more than one document type,But it is advisable to maintain different no-range for each document type.

Confirmation Control Key Should be mandatory for PO document type

Hi All,
I want to know, is there any configuration settings to make mandatory "confirmation control key" for the Particular Purchasing document type's.
If it is not there what should be the best to achieve this requirement.
Thanks in Advance,
Shankar.

Hi
I think there is no standard setting to make mandatory document "confirmation control key" for the Particular Purchasing document type's.
Best way is to maintain in Purchasing view of vendor master record since confirmations rare sent by the vendor.If you want for some perticular materials you can maintain in Purchasing info record.
Regards
Ramakrishna

Maintain Copy Control for Document Types.

Hi Gurus,
My Client has two customized documents both are order Types and wants to maintain Copy control between them.
If i see VTAA i can find either New Entries option or copy option.
When i go for new entries option it asks me Requirements and Routines which needs to be set for this copy control and i am not aware of those.
The Other option is Copy as but since it's customized document types so i am not getting which document should i take as refernce for copying.
Please suggest me how to proceed.
Thanks in Advance!!!!

Hi
Ideally we don't gamble with standard settings. Not only in copy control but for all other settings related to document types, conditions, movement types etc etc. If standard settings or configuration has been deleted by human error then we should restore standard settings first. May be BASIS guy can do it and if it is not possible then open some other server where these settings are there and you should do all settings manually by copying the standard ones.
Why we recommend to always copy standard settings and make necessary changes is that standard settings are done by SAP and they have tested it thoroughly and they have hundreds of consultants who have worked on these settings. Standard settings are reliable and we can copy them without any fear of mistake. Whereas if you copy some Z settings or create new one then there are more chances of some wrong or missing settings. Logically may be it sounds not that important or useful but technically it is really fruitful to do this.
In standard settings system copies all subsequent settings and you don't need to do those settings again and you are already aware of this fact.
One more benefit is that you only need to change document names and in create new entry you'll have to enter all the fields one by one and you don't know which value is more appropriate for this field. It also saves time efforts and people like me always prefer to save efforts
Thank$

Legal Control : Document Type Mapping not Maintained

Getting an error SAP GTS :Legal Control : Document Type Mapping not Maintained ,while creating order in feeder system .
I checked the configuration maintained SAP Global Trade ServicesSAP Compliance ManagementGeneral SettingsDocument StructureAssignment of Document Types from Feeder Systems-Assign Document Type at Feeder System Group Level
Similarly I checked for item category.
Please let me know what further configuration have to be maintained for correcting the error.
Thanks & Regards

Hi,
The document type mapping is required in R/3 system too. You have to maiatain order type say OR/TA in R/3 below path
IMG--> Sales and Distribution --> Foreign Trade/Customs --> SAP Global Trade Services - Plug-In --> Control Data for Transfer to SAP Global Trade Services --> Configure Control Settings for Document Transfer --> SDOA.
Note: If you maintain OR in R/3, you will have to maintain same in GTS. if you maintain TA in R/3, same maintain in GTS.
Regards,
Lakshmikanth

Can vendor be controlled as per PO document type ?

Can vendor be controlled as per PO document type ?
I mean vendor for stock type should not be allowed for non-stock type.

You can maintain vendor as per Account Group But as long as you have a Vendor for a Purchasing Orgainsation and a Plant for Material under the Purchasing Org. System do not stop on the basis of Stock and Non Stock Vendors.
Biren Agnihotri

What are the sources system will pick the document type while creating invo

hi
I would like to know how system will pickup the doucment type while creating invoice in vf01.
i have taken off the fields f1, f2, from the document type. in billing sub tab. so The moment when am creating billing system automatically displaying F2 invoice doucment creation. What are the sources for this.
thanks & Regards
Rack129

Hi,
Hope you have maintained u2018Delivery relevant billing type F2u2019 and u2018Order relevant billing type F1u2019 in the billing tab of the Sales document type in VOV8.
If you create delivery related billing, the system will pick F2. This is controlled in Item category (VOV7). Billing relevance in Business data of Item category decides whether this is delivery related or order related. u2018Au2019 for delivery related billing; u2018Bu2019 for order related billing and so on.
Item category is determined by this combination: Sales document type + Item cat group + usage + higher level item cat.
Regards,
K Bharathi

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,

Immediate Transfer Order Creation not occuring for Sales Document Type

Hello gurus,
I have a situation where a transfer order is not being created immediately for a specific sales document type.
Here is an example document flow of a desired scenario where the system is working:
Sales document type: ZOR
> Delivery type: LF
> WMS transfer order
The Item Category in this scenario is TAN.
Here is an example of the document flow in the current scenario where the system is not working:
Sales document type: ZPRD
> Delivery type: LF
The Item Category is also TAN in this scenario. The only identifiable difference in these scenarios is the sales document type. For the ZOR SaTY, a Transfer Order prints immediately once the delivery is created. For the ZPRD SaTY, a Transfer Order needs to be manually created after delivery creation.
Is there a configuration setting that is controlling this? Any help would be greatly appreciated.

Thank you very much for the link. When I insert the WMTA output type in the delivery output header, the Transfer Order is automatically created.
The problem I'm running into now is the configuration setting that controls this. I thought I figured it out when going to this IMG path:
SAP Customizing Implementation Guide --> Logistics Execution --> Shipping --> Basic Shipping Functions --> Output Control --> Define Print Parameters Shipping
When selecting the Delivery Note, the shipping point I was using was not configured in this location. I added the shipping point into this transaction, saved, and created a new order & delivery. However, the WMTA output type still was not automatically inserted into the delivery when saving. Is there another location I should be looking to fix this so that when I enter an order with a particular Shipping Point, the WMTA output type automatically appears in the delivery?

Billing block for customer for sales document type OR

Hi
I want to block a customer for a particular sales document type OR
How to do it?
Regards

Hi Nikhil
There is a field called "Check Partner Auth.", but it is necessary to create the order from a contract. This field is in sales document customizing VOV8.
SAP Documentation:
Check partner authorizations
This check determines whether a partner is authorized to release against a contract.
Procedure
Here you can specify whether the check is to be performed against the partners in the contract or the partners in the customer hierarchy. If you do not want the check to be performed, leave the field blank.
When you create a release order for a contract, the system determines whether a partner is authorized to release against the contract. The check is performed at header level. Depending on the rule you enter in this field, the system checks against one of the following:
Partners in the contract
If the partner has the partner function AG (sold-to party) or AA (sold-to party authorized to release) in the contract, the system accepts the partner as the sold-to party for the release order.
Partners in the hierarchy
If the sold-to party of the contract is at a higher level in the customer hierarchy to the partner who wants to release against the contract, the system accepts the partner as the sold-to party for the release order.
Note
If you create a contract with reference to another contract, the system does not run a check and it copies all the partners created in the target contract. If you do not want it to do this, use copying control in Customizing to change it.
Regards.
Mikel

Document type control

Similar Messages

Maybe you are looking for