Doc Types in Contract Management

All,
is there a standard way to distribute Contracts / Scheduling Agreements based on a SRM GOA (Release 4.0 as well 5.0) without maintaining the corresponding Doc Types (GCTR) in R/3? Client expects that the standard R/3 Doc Types (LPA / MK, WK) are linked to a SRM GOA.
Looking forward to your thoughts!
Thanks,
Claudia

Hi
Refer to these links as well.
PO line item displaying incorrectly from contract
BBPV_CONTRACT_CREATE
Code needed for contract BADI's
Need Help in editing an existing Contract
BAPI_CUSTOMERCONTRACT_CHANGE for update pricing
Addition of custom fields in Contract and mapping it with the fields in SRM
Contract Upload to New System
Position Field Costumer in Contract
Source determination in backend (R/3) for distributed contract i.e. GOA
Regards
- Atul

Similar Messages

Requisition doc. type RV not allowed with doc. type

Using the tcode ME51n, I created an Outline agreement(Doc type RV) and when i go to ME31K to create a contract and select With Ref to Purchase requisition and enter the Purchase requisition #, I get the error message Requisition doc. type RV not allowed with doc. type.
I tried changing the settings for doc types for contract, but it doesnt seem to be working. Any solutions will greatly beappreciated.

This is the settings in PR: SPRO-MM-Purchasing-PR-Define document type
Doc type: RV     Outl. agmt. requisn.     10     01     02     RVB     R
once above is correct than
select the doc type RV and click on the allowed item category
where can see as below
Item cat Text item category
     Standard
K     Consignment
D     Service
select the doc type RV and click on the Link purchase requisitio in left side
MK     Quantity contract     M     Material unknown          Standard
WK     Value contract          Standard                          Standard
WK     Value contract     K     Consignment          Standard
WK     Value contract     M     Material unknown          Standard
WK     Value contract     W     Material group          Standard
Now go to contract doe type
you will see
MK     Quantity contract     10     02     AZ          SAP     MKK
WK     Value contract     10     02     AZ          SAP     WKK
select any doc type and click on allowed item category
here you would see
     Standard
K     Consignment
L     Subcontracting
M     Material unknown
D     Service
than click on link purchase requisition by selecting doc type MK or WK
RV     Outl. agmt. requisn.          Standard          Standard
RV     Outl. agmt. requisn.          Standard     K     Consignment
RV     Outl. agmt. requisn.          Standard     M     Material unknown
RV     Outl. agmt. requisn.     K     Consignment     K     Consignment
RV     Outl. agmt. requisn.     D     Service     D     Service
once you have all this set up than you can create the contract based on the RV reqs

What is the doc type 'DC' in contracts

Hi,
Please explain about the doc type 'DC' in contract agreement.
Thanks in advance!
Regards,
Jana

Find the below link.
Its usefull
http://help.sap.com/printdocu/core/print46c/en/data/pdf/CABFAISMM/CABFAISMM.pdf

Condition types and Pricing in Contract management - SRM

Hello,
We have configured Contract management in SRM 5.0 (Global Outline Agreement).
I'm trying to create an exact rpelica of the R/3 pricing in SRM. Surprisingly when I created all condition types in SRM, it needs condition group maintenance. which in turn needs an access sequence. Now following are the problems I'm experiencing..
1. It is allowing to create a condition group maintenance in TTE. Somehow I managed it thru SPRO to create the one under BBP.
2. No menu path available to create a condition table under BBP. Again the same available for TTE. I managed to create this one as well.
3. Now the price/net price maintained at line item should get assigned to PB00 by default, but this does not get assigned.
4. All the documentation talks about implementation of BADI, but that does not help, cuz condition types may be created for new terms/norms in future.
Anyone has created condition types in SRM and implemented the same in Contract management and successfully replicated the contract in the backend with all condition types carried with values?
Regards,
Ashish

Hi
you check the bellow table for contacts data.
ekko--> Contract header data
ekpo--> Contract item data
konh--> Conditions header data
konp--> Conditions Item data
Regards
Anand

WRP1 excluding open POs based on doc type

Hi friends,
We are using SAP IS Retail ECC 6.0
In our business, we are having requirement that Open PO quantity of particular document type (eg ZNBA) should be excluded from the WRP1 requirement calculation.
Eg:
For an article 100001, Site A001, following are the details,
Reorder point - 10
Target stock - 20
Current stock - 5
Open PO quantity: (ZPO1 and ZPO2 are PO doc. types)
ZPO1 - 2
ZPO2 - 1
Now WRP gives requirement of article as of 12 quantities.
My requirement is to it should not include ZPO1 open quantity in consideration but should take ZPO2 into consideration.
Hence requirement is to create PO for 14 quantities
How do I achieve this?
We have a control in SAP IS Retail where we can specify, that stock of which storage location should be considered in replenishment requirment calculation.
Do we have a similar control for the PO Doc type? If not, how do I achieve workaround?
Thank you,
regards,
Gaurav

Hi,
Do the Following, Create a new storage location., "ZL01"
Whenever your creating a PO with this "ZPO1" document type assin this Slocation "ZL01", then do the below settings in SPRO..
SPRO->Materials Management->Consumption-based Planning->Planning->Define Storage Location MRP per plant.
(In RP indicatior please give "1"Storage location stock excluded from RP, this will exclude the stk from this location)
Regards
GK.
Edited by: Gnana Kumar on Oct 22, 2010 11:15 AM

Change the backend doc type from PR to PO in BADI BBP_TARGET_OBJECTS.

Hi,
We have followed below approach for backend document type determination.
1. A custom function module contains the logic to determine the backend document type of a Shopping cart line item. THis function module, performs many checks and hence cannot be called in any BADI that is executed in Foreground.
2. I am using BADI BBP_TARGET_OBJECTS to change the follow document type by calling the custom function module.
Issue here is, if the backend document type of a line item is Purchase requisition (2) by SAP standard, and if I try to change it to Purchase order, it gives run time error and ends up in creation of Purchase order.
After further investigation I found that this line item (with default backend doc type as 2) has a desired vendor. If we change the desired vendor of this line item to fixed(To Partner function 19 from partner function 39), it allows us to change the doc type from Purchase requisition to purcahse order in BADI BBP_TARGET_OBJECTS.
But changing the partner function is possible only in BBP_DOC_CHANGE BADI, and I cannot call the custom function module there, as it may impact the performance.
Is there any other way, I can change the partner function in any of the BADIs called in background?
Or Is there any way by which I can change the backend document type from PR to PO in BBP_TARGET_OBJECTS?

Hi Parab
if you swaping 39 to 19 viadoc change badi
REQUESTER has a control on Purchase ORDER Vendor and BUYER lost a control so your business has to decide.In this case procurement department lost their control.
Fixed vendors are like inforecord and contract negotiated for best price ..
Muthu

Assinment of pricing procedure to doc type

Hi friends,
I am new to MM , how the pricing procedure is assigned to doc type, or how the pp is triggered in PO.
Thanks
madhu

Hi Madhu Sudan,
Pricing Procedure as you know is one and the same as calculation schema.
To administer the PP i.e. Determination of Calculation Schema for PO you will have to go to the transaction SPRO---SAP Reference IMG
Follow the node
Materials Management-Purchasing-Conditions-Define Price Determination Process-Define Calculation Schema.
Once you are there In the calculation schema (pricing procedure), you specify which condition types are to be taken into account in which sequence
Now coming to your query,
1) Assignment a Calculation Schema (PP) to Doc type
-- Remember It is not possible to assign PP to Doc type
2) Trigerring of PP in PO
-- Follow these underwritten simple steps:
i. Define a schema group for vendor under the node> Materials Management-Purchasing-Conditions-Define Price Determination Process-Define Schema group. You will have to assign this same schema group in the relevant vendor master record.
ii. Define a schema group for Purchasing organisation under the node> Materials Management-Purchasing-Conditions-Define Price Determination Process-Define Schema group. & assign it to the relevant Purchasing Organisation in the same step.
iii. Once this is done you have to Determine Calculation Schema for Standard Purchase Order under the node>Materials Management-Purchasing-Conditions-Define Price Determination Process-Define Schema Determination. In this step you assign Calculation Schema to a combination of Schema Group (Purchasing Organisation) & Schema Group (Vendor).
iv. Conclusion: During the time of making a PO; Shema Group of Vendor is picked from the relevant Vendor Master Record, Schema Group of Purchasing Organisation is picked from Customisation (where you assigned it) & A Calculation Schema is triggered for the combination of these two Schema Groups (PP that you defined in step iii)
Hope this explains it, for better understanding please read the IMG activity documentation for each activity.
For any further doubts please reply.
Regards,
Prithviraj

Anybody ever created multple PO doc type/number ranges in extended classic?

I have searched this forum, and found plenty of useful threads which would help me determine different document types/number ranges for back-end purchase orders in a classic scenario. (And I have done something similar many years ago on a classic EBP 3.0 implementation)
However, I have a customer who has an SRM 5 extended classic implementation, and who (Based on certain simple criteria) requires a different PO number range to identify certain types of indirect orders. (They also have direct materials procured using doc type ECDP, but that's not relevant to this requirement)
This would obviously have to apply to the local PO in SRM, as well as the backend ECC PO.
It would also need to be derived for orders created automatically via approved shopping carts, as well as those orders that are created via sourcing.
I've copied ECPO via define transaction types IMG step, as well as assigned a new number range.
Just to test, I've also added the second doc type in the BSA attribute for a particular test user - just initially see if it was possible to manually choose when creating a PO in sourcing. However, I could only get ECDP and ECPO.
I have looked at various BADIs to see if I can determine doc type or number range somewhere in the PO creation, but as far as I can see, they either:
- Seem to apply only to the object type (PO, requisition, reservation etc) rather than the transaction type within that object.
- Or look like they are too late in the process to influence the doc type and number range (BBP_DOC_CHANGE_BADI?) ... which doesn't seem to have those doc type or PO number fields available anyway
- Or I doesn't seem to be trigerred at all when turning requirement into Po and ordering via sourcing. (tried break-point & endless loop in implemnetation of BBP_CREATE_BE_PO_NEW, but nothing happened. In any case the PO number was alreadya ssigned)
If anybody has ever managed this before, or can tell me that I am definitely barking up the wrong tree, it would be gratefully appreciated. The document type is actually lesss important than the different number range... and was really just an attempt to trigger a different number. I'm starting to think that this sort of thing may only be possible in a classic implemntation.
What I need ideally, would have been some kind of 'local PO' equivelent of the BADI that enables you to determine transaction type for a bid.
Regards,
Vince
Edited by: Vincent White on Dec 6, 2010 5:13 PM

Hi. Not sure on this, but I can tell you that with extended classic it is BADI BBP_ECS_PO_OUT_BADI that is called for the backend PO instead of the CREATEPO_BACK BADI.
You can have a look in BBP_ECS_PO_OUT_BADI and see if that helps?
Don't think it will influence the PO in SRM at all though.
Have you tried the number range / grouping BADIs? They definitly work for changing the number range for classic POs.
Regards,
Dave.

Urgent - Automatic output determination for PO doc type

Hello all,
I have created an output type along the lines of NEU and maintained all the necessary setting. new outpout type is ZNEU. I want this to be triggered when i save my PO with new PO order type ZS.
However, when i save my PO type ZS no output determination takes place.
Where exactly is the link between PO type ZS and output type ZNEU.
Any help will be appreciated.
regards
s Datar

Check all the settings as mentioned below
PO Output
Output of Purchase Order
1. Condition Table
SPRO > Material Management> Purchasing -> Message -> Output Control->Condition Tables->Define Condition Table for Purchase Order
Select:
Purchasing Doc. Type,
Purch. Organization,
Vendor
2. Access Sequences
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Access Sequences->Define Condition Table for Purchase Order
3. Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Types->Define Message Type for Purchase Order
4. Message Determination Schemas
4.1. Message Determination Schemas
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Maintain Message Determination Schema
4.2. Assign Schema to Purchase Order
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Assign Schema to Purchase Order
5. Partner Roles per Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control-> Partner Roles per Message Type ->Define Partner Role for Purchase Order
6. Condition Record
Navigation Path: SAP Menu-> Logistics -> Material Management -> Purchasing-> Master data->Messages-> Purchase Order-> MN04-> Create
Now you create PO (ME21N) and save it. Go to ME22N and print the PO by giving output type.
GR Output
Output of GR
After setting table, access sequence and output type for GR,run MB02 transaction, enter material document number. Double click one line item and select messages. Separate screen will be opened to configure outputs. Give the required fields and save the document. Now Run MB90, you can take printout. Output Type: WE03 or WE01 or WE02
Regards,

5 doc type and 2 content repository

Hi
I have 5 document type in DMS and 2 content repository.
Doc type QWE, ASD, JKL - pdf files must be in content repository X
Doc type ABC, BNM - pdf files must be in content repository Y
How should I proceed to do this?
Regards

Hi,
if I understood your latest information correctly your request is that the files are stored automatically to storage category if you add a file to a document info record and save it. To achieve this behavior the first important setting here are the flags "Checkin" and "Checkin required" which are already set for the used
document status.
This first setting enables the automatic start of the checkin process. But to have a specific storage category choosen for an original workstation application, you have to do another setting and create a profile in your system in the customizing under
- Cross Application Components
    - Document Management System
        - General Data
            - Define profile
For this profile pleasee add your workstation applications under "Determine definitions for applications". Here you can maintain the default storage category for this application in field 'Storage cat.'. Since this profile is created assign it to all your users directly. Then if an user adds a new original file and chooses a workstation application the system should take the storage category automatically from the profile.
Another proposal would be to use the BADI DOCUMENT_STORAGE01 which should offer also methods to control which storage category should be taken for which workstation application. I hope that this information could be useful for you. To set up this scenario in detail I would recommend you to contact your local consulting organization too which will help you in realizing a solution that meets all your requirements.
Best regards,
Christoph

RFIDYYWT / 1099 reporting / include doc type AB?

We are preparing to use SAP's 1099 Misc reporting functionality for the 2011 tax year, and have managed to resolve most issues. However, we can't figure out how to get miscellaneous journal entries (doc type AB) included in the reporting. I've confirmed that the line items in BSEG have the appropriate withholding tax code (07), but when I run RFIDYYWT, the 'AB' documents aren't being included.
Can/should AB documents be included in 1099 reporting? And if so, what do we need to do to ensure that they get pulled in?
Thanks in advance!
Allison

Hello Allison,
Please review the following documentation on the field reporting period.
Field ; Reporting period
Posting date in the document
Date which is used when entering the document in Financial Accounting
or Controlling.
Use
The fiscal year and the period for which an update of the accounts
specified in the document or cost elements is made, are derived
from the posting date.
When entering documents, the system checks whether the posting date
entered is allowed by means of the posting period permitted.
Note
The posting date can differ from both the entry date (day of entry
into the system) and the document date
(day of creation of the original document).
The selection criterion in RFIDYYWT is the posting date
(not the clearing date).This is entered in the 'reporting period' field.
Consider the following example:
-invoice document posted in 2004 -payment document posted in 2005
1. if you select period 20010, only the invoice will be reported
2. if you select period 2011, only the payment will be reported
This may cause confusio if the calculation of the w/h tax does not occur
within the posting period selected (the calculation of w/h tax depends
on your settings: it could be w/h tax at time of invoice or at time of
payment).
Please, understand that mainly based on the selection criteria and
the output defined the document will be selected or not.
Currently, documents are getting selected based on the reporting date.
The reporting date is the posting date in the document, that means, the
date which is used when entering the document in financial accounting
and the withholding tax amount is posted.
Hope this helps,
Regards
RAY

Purchase group restrict with doc type

scenario is this like i want to restrict purchase grp with doc type wise, suppose i want purchase group <b>"abc"</b> should not be used in doc type "<b>FO"</b>
then what setting should i do?

this you can only do with the basis person who has authorisation to make changes in user t.codes.
in t.code PFCG, give the user role for which you want to restrict this and then choose display, goto authorisation tab and click n the display authorisation data button, here at the top you can find the organiztional levels button, you can restrict the purchasing group here itself by not specifying it in the list, thus for all t.codes he will not have authorisation for this purchasing group.
then choose the MAterials Management : Purchasing node, here choose the Document Type in Purchase Order to give the doc. types allowed to user and Purchasing Group in Purchase Order to limit the pur. groups.
reward if helpul

STO UB doc type

HI Gurus,
Can anybody please help me with this? When we are procuring the materials from a different plant using STO.(The config is all setup). Do we need to maintain a source list in the procuring plant with the supplyinh plant as the vendor and also do we need to maintain inforecord. Please help and clarify. Also in the STO config can we have these at the same time
Supplying plant plant (receiving plant) doc type
XXXXX yyyy NB
XXXXX yyyy UB
Thanks
Anusha

You will want to have the supplying plant tied to the vendor (shipping) plant in the vendor master data under the vendor purchasing data screen, and menu path Extras -> Add purchasing data. You need the information record as well. Be sure to have the STO config for the plant and customer plant in the IMG path: Materials Management -> Purchasing -> Purchase Order -> Set up Stock Transport Order -> Define Shipping Data for Plants.
If you have ECC 6, you wish to go even further with "Set Up Stock Transfer Between Storage Locations". This is set up with more integration with the LE/SD modules with shipping points in these areas (Set Up Stock Transfer Between Storage Locations and Define Shipping Data for Stock Transfers Between Storage Locations).
Regards

Contract Management

Hi All,
Can anyone help me out with the documents related to Contract Management in SRM like config guides and other doc's.
please send them to my id <removed by moderator>
Thanks,
James

Hi experts,
I m doing SRM contract mgmt configuration. Can any one the configuration guide for the same...
My mail ID - <removed by moderator>
Thnks in adv...
Regards
Raaam's...
Edited by: Raaam'S on Apr 21, 2008 1:40 PM

IE or Contract Management v13 thinks my DOCX file is a zip

When trying to open an attachment IE or Contract Management v13 thinks my DOCX file is a zip. This started last Thursday. Outta the blue. We’ve been searching for a days now for a solution. Nothing has helped. I have a few hundred users all with various combinations of applications on their boxes. XP PRO, Windows 7, Office; 2007, 2010, WordPerfect 5.1 files work just fine. :)

We are having the same problem and are wondering whether you found a solution. A workaround is to disable MIME handling in IE (this is what Oracle support will suggest), but this is far from ideal as it does compromise security slightly.
The problem arises when WebLogic (or JBoss, WebSphere....) sends the file to your browser. It marks the file as Content type "application/octet-stream" instead of identifying it as a MS Word 2010 document. This causes IE to try to identify the type itself. First it checks the extension of the file and looks in the registry to see what's there. If it finds an entry, it then reads the first part of the file to see if the content matches what the registry says. Something appears to be broken in the way IE identifies Word 2007+ files, causing it to identify them as .zip files. Users are then prompted to save the file to their desktop.
Word 2007+ files actually ARE zip files under the hood, but until recently we had no problem with them. There appear to be three possible routes to resolve this issue.
One, take Oracle's "pass the buck" advice and disable MIME handling in IE so that IE no longer tries to identify the file (registry hack set HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_MIME_HANDLING\iexplore.exe to 0). This bypasses the problem and introduces security holes to your workstation configuration.
Two, configure your Java application server to send the files with the correct content-type header. I can't find a way to do this in WebLogic so far as you have to modify the web.xml file, which is created by the application installation/deployment. Oracle Primavera CM support has yet to respond to my request on this other than to say "consult WebLogic support". Oracle WebLogic's support will (as they have in the past) tell me it's application specific and to consult Oracle CM support. Neither support group seems to be able to support Oracle's products. (Dear Oracle, please get your act together. You own both products and should be embarrassed by the lack of customer service here.)
Three, figure out why IE is failing to match up the 2007+ file types with the file content. We're assuming a recent patch did this, but haven't identified which one. In any event, we will probably not be allowed to roll back a security patch to fix this.
Anyway, I hope this helps you. I have a case open currently, as well as another post in the forums.
Lowell

Doc Types in Contract Management

Similar Messages

Maybe you are looking for