Attach document to Outline Agreement

Hi All,
I can't seem to find a tool to help me attach a word document to an outline agreement.
Is this possible? If so, please provide instructions.
Thank you!

hi
after entering the Line item in the Outline agreement
select --> Item --> More function --> Documents.
your document must be created in Document Management system of SAP.
Edited by: AP on Apr 6, 2009 9:00 AM

Similar Messages

Table that store outline agreement

Dear All,
Pls tell me what are the table that are used to store the data of the outline agreements
Tks
Sujith

These are the tables where all purchasing documents including outline agreements are stored.
EKKO Purchase document
EKPO Purchase document (item level)

Tax value on Outline Agreement

I am very new to the concept of purchasing and outline agreements and below are some questions. Please help.
Should there be a tax value on outline agreements trxncode me32K?
Are they attached to purchase orders? and if so, how do you find out the PO attached to the contract(outline agreement).
Advance Thanks to those who can help and I will reward points.
Ladysap

Hi
1.For Outline agreement, Tax code is not mandatory. However, you can enter the same by selecting the line item and clicking "Item Details" (F2).
2. Yes, Contracts(Outline agreements) are attached to Purchase Orders. They are called Release Orders. To create a PO against a Contract, go to ME33K, give the Contrcat no and in the Menu go to Contract->Follow On functions->Release Order.
You can view the Pos attached to the Contract in ME33K. Select the item in the item overview and then choose Item -> Statistics -> Release documentation.
For further information on the release order (i.e. on the purchase order), choose Goto -> Release details.
If you wish the goods receipts and values of invoices received to be displayed for the item, choose Goto -> PO history. All GR and invoice documents are then listed.
For more information on Outline Agreements, pls visit http://help.sap.com/saphelp_erp2005vp/helpdata/en/75/ee0f5a55c811d189900000e8322d00/frameset.htm
Hope this clarifies.
Thanks

Unable to prevent Price change for Outline Agreement

Dear Experts,
Once Outline Agreement is generated in SAP, I do not want to allow users to change the price.
I have tried with " Field Selection at Document level" using ME32-Change outline agreement field selection.
I select "Quantity and Price" and select check box Display for "Price and Price Unit",Price Date", "Condition Group".
This will not allow price change at item details level (field grayed out) but user can still select Item condition (for Example PB00) and change the price there.
Is there any solution for this ?
Ideally I want to do this for a particular Document type of Outline Agreement only.
Thanks and Best Regards,
Raju

Hi Ramki,
Thnka s for you reply.
This is not the desired solution. I can not ask Client to change to create different uses for create and change .
In the buinsess process , mostly create an change users are same for outline agreements.
I do not wna to restrict by User Authorization either as this is also not a 100% solution.
Still looking at configuration level only to restrict changes in Pricing for outline agreements.
Regards,
Mitesh Desai

ECC Report showing Outline Agreements WITH related Release Orders

Does anyone know of a report in ECC which will display all Outline Agreements together with all the Related Release Orders associated with each Agreement Number?
I have trawled through hundreds of SAP transaction codes and cannot find something that will give this information - I can use ME3N of course, but ideally my Users want to be able to search on ALL Outline Agreements and see the associated release orders
If anyone is able to help it would save me a headache!
Many thanks
Jane

You can get Goods Movement from MSEG Tables. Why do you need Goods Movement in Sales Flow?
While Creating Every Document in SAP R/3, we will put reference Document and Item.
While Creating Sales Document, Customer PO is reference Document.
For Delivery, we can create againest Sales Document or Invoice etc.
For Invoice, either Delivery or Sales Document.
Pull all the Data Sales, Delivery, Billing and Shipping with Reference Documents into ODS.
You need to create a Infoset on these ODS.
Let me know if you still have any Questions.
Nagesh Ganisetti.
Assign points if it helps.

PO rel procedure carried over to Outline agreements

Hi Experts,
Release procedure created for Purchase order has become active for Contracts & Scheduling agreement also. Infact system doesn't allow to process (MIGO) scheduling agreements (agreement type: LP) without being released.
Is this valid? if yes how do I avoid this carry over.
Thanks,
Rajoo

Hi,
In the classification of the release strategy, create one caracteristik as Document category.
Maintain the value "F" for PO.
It will not pickup the outline agreement
Cheers,
Satish Purandare

Outline Agreement Report with its corresponding POs

Hi,
Is there a standard report where in you will just key in the document date and some other fields in the selection screen and then it will output all the outline agreements based on the date and its corresponding purchase orders?

Hi,
ME2N and ME3N is the report. But i guess this will not suffice your complete requirement but you can have a look and check if this is what your req is.
Prashant Rathore.

Report for outline agreement

Hi Guys:
I`m wondering on R/3, is there some transaction code or dynamic selection i can use to run a report for outline agreement. i am looking for one report that will generate following information: Outline agreements that has not been used since August 2007 till now, which means no Purchase orders drawn off the outline agreement.
In other word, Outline agreement with Purchase order but has not been used since a particular date.
Much appreicate your help indeed.
Forrest

Hi Manish:
Thanks a lot.
If i specify document date from 01.08.2007 to 14.05.2009, meanwhile, input RAHM into Scope of list. Then i will get one report including all the outline agreement created in this period, with filter, i think i can pick up outline agreement is not used until now.
I have another concern, how about the outline agreement created before 01.08.2007, but these outline agreement has not been used from 01.08.2007 to 14.05.2009.
Waiting for your solution.
Forrest

Problems in Global Outline Agreement

Hi friends,
                      We are using SRM 5.0 and R/3 4.7.I want to replicate contract to SRM 5.0 to R/3. For that I have to configure Global Outline Agreement. After creating and distributing GOA i am facing 2 errors. I got those errors from Transaction RZ20 -> SAP Enterprise Buyer Monitors - > Contract Management.
Errors are
Node name - SRD\Business to Business Procurement (500)\...\Contract Management\Contract Distribution
Date - 21.06.2008     Time - 14:37:45
System - SRD
Context - Business to Business Procurement (500)
Object Name - Contract Management
Short Name - Contract Distribution
Status - ACTIVE
Value - 3
Severity - 50
Status Set by - BBP
Status Set on - 21.06.2008
Status Set at - 09:07:45
Msg Class - SAP-T100
Msg Id - 000
Alert Text - Different processing times defined for BLAORD and CONDA
Var1 - 5600000014
Var2 - K77CLNT801       (backend Logical System)
Var3 - 0000000000000000
Var4 - 5600000014K77CLNT8010000000003          01
Node name - SRD\Business to Business Procurement (500)\...\Contract Management\Contract Distribution
Date 21.06.2008
14:37:45
System - SRD
Context - Business to Business Procurement (500)
Object Name - Contract Management
Short Name - Contract Distribution
Status - ACTIVE
Value - 3
Severity - 50
Status Set by - BBP
Status Set on - 21.06.2008
Status Set at - 09:07:45
Msg Class - SAP-T100
Msg Id - BBP_ADMIN 028
Alert Text - Application error in backend system K77CLNT801 (SRM outline agreement 5600000014)
Var1 - K77CLNT801      (backend Logical System)
Var2 - 5600000014
Var3 - 0000000000000000
Var4 - 5600000014K77CLNT8010000000003          01
I have done replication process of Purchase order from SRM to R/3.It is working fine.
I have done this configuration for GOA.
1.     Define GCTR transaction type in SRM.
2.     Define internal number range in SRM for the GOA that is the same as the external number range in the back end system for GCTR.
3.     Implement the badi BBP_CTR_BE_CREATE.
4.     Store, Plant, Material, Material group has been replicated from R/3.
I am getting those mentioned system message from Header Data -> Status
System Status
Complete
Created
Released
Distribution Incorrect
Document Completed
I am not using any conditions in item level.
How can I configure IDocs BLAREL for SRM and MM? I donu2019t have any idea?
Please help me to correct error .
Thanks in advance.

Hello,
check out notes 1053985 and 646903, that should solve your problem (especially the sections Mapping master data and Customizing data of note 646903).
Regards,
Andreas

Delivery date for outline agreement requisition

Hi all,
When I create a purchase requisition (ME51N) for a non stock material, for example, using req type NB or FO, the delivery date defaults to the current date. If I create a req with the same information but using type RV (outline agreement) the delivery date defaults to blank. I found out that in the IMG, under the req doc type config, the type RV is associated with the "Control indicator for purchasing document type" = R (Purchase requisition for outline agreement). If I clear this field, the delivery date starts defaulting to the current date. I created 2 reqs side by side (one with the indicator "R" and the other without) and I did not find any difference except for the delivery date. Does anyone know what the impact is to clear field V_T161-BSAKZ for doc type RV?
Thanks.

Hi
The control indicator "R" determines Filed selection. ie Which requires mandatory or optional. For Doc types RV field selection groups is RVB , in that Delivery date is not a Required/optional/Dsiplay field., this works in conjunction with control indicator "R".
Hence when you try to create with Doc type RV and control indiactor "R" it is not propsoding the current date. When you remove Control indicator "R" the field selcetion groups becomes NBB , in that Delviery date is Required filed, so the system proposes the current date .
The impact of removal of control indicator "R" is nothing.
Regards
DRN
Give points if ok

To change the text of outline-agreement

Hi Experts,
Im using BAPI_CONTRACT_CHANGE function module to change outline agreement.When im executing this im getting the dump.Will you explain me how to use this fm to change the item text of outline-agreement.Will you please give the list of mandatory fields for this function-module.

IMPORTING
*"     VALUE(PURCHASINGDOCUMENT) TYPE BAPIMEOUTHEADER-NUMBER
*"     VALUE(HEADER) TYPE BAPIMEOUTHEADER OPTIONAL
*"     VALUE(HEADERX) TYPE BAPIMEOUTHEADERX OPTIONAL
*"     VALUE(VENDOR_ADDRESS) TYPE BAPIMEOUTADDRVENDOR OPTIONAL
*"     VALUE(TESTRUN) TYPE BAPIFLAG-BAPIFLAG OPTIONAL
*"     VALUE(TECHNICAL_DATA) TYPE BAPIMEOUTTECH OPTIONAL
*" EXPORTING
*"     VALUE(EXP_HEADER) TYPE BAPIMEOUTHEADER
*" TABLES
*"      ITEM STRUCTURE BAPIMEOUTITEM OPTIONAL
*"      ITEMX STRUCTURE BAPIMEOUTITEMX OPTIONAL
*"      ACCOUNT STRUCTURE BAPIMEOUTACCOUNT OPTIONAL
*"      ACCOUNTPROFITSEGMENT STRUCTURE BAPIMEOUTPROFITSEGMENT OPTIONAL
*"      ACCOUNTX STRUCTURE BAPIMEOUTACCOUNTX OPTIONAL
*"      DELIVERY_ADDRESS STRUCTURE BAPIMEOUTADDRDELIVERY OPTIONAL
*"      ITEM_COND_VALIDITY STRUCTURE BAPIMEOUTVALIDITY OPTIONAL
*"      ITEM_COND_VALIDITYX STRUCTURE BAPIMEOUTVALIDITYX OPTIONAL
*"      ITEM_CONDITION STRUCTURE BAPIMEOUTCONDITION OPTIONAL
*"      ITEM_CONDITIONX STRUCTURE BAPIMEOUTCONDITIONX OPTIONAL
*"      ITEM_COND_SCALE_VALUE STRUCTURE BAPIMEOUTITEMSCALEVAL OPTIONAL
*"      ITEM_COND_SCALE_QUAN STRUCTURE BAPIMEOUTITEMSCALEQUAN OPTIONAL
*"      ITEM_TEXT STRUCTURE BAPIMEOUTITEMTEXT OPTIONAL
*"      HEADER_TEXT STRUCTURE BAPIMEOUTTEXT OPTIONAL
*"      HEAD_COND_VALIDITY STRUCTURE BAPIMEOUTHEADVALIDITY OPTIONAL
*"      HEAD_COND_VALIDITYX STRUCTURE BAPIMEOUTHEADVALIDITYX OPTIONAL
*"      HEAD_CONDITION STRUCTURE BAPIMEOUTHEADERCOND OPTIONAL
*"      HEAD_CONDITIONX STRUCTURE BAPIMEOUTHEADERCONDX OPTIONAL
*"      HEAD_COND_SCALE_VAL STRUCTURE BAPIMEOUTSCALEVALUE OPTIONAL
*"      HEAD_COND_SCALE_QUAN STRUCTURE BAPIMEOUTSCALE OPTIONAL
*"      PARTNER STRUCTURE BAPIMEOUTPARTNER OPTIONAL
*"      PARTNERX STRUCTURE BAPIMEOUTPARTNERX OPTIONAL
*"      RELEASE_DOCU STRUCTURE BAPIMEOUTRELEASEINFO OPTIONAL
*"      EXTENSIONIN STRUCTURE BAPIPAREX OPTIONAL
*"      EXTENSIONOUT STRUCTURE BAPIPAREX OPTIONAL
*"      RETURN STRUCTURE BAPIRET2 OPTIONAL
FU BAPI_CONTRACT_CHANGE
Short Text
BAPI to Change a Purchase Contract
Functionality
BAPI for changing a purchase contract.
Notes
Master conditions
When creating outline agreements, you can specify only one period per variable key. This means that just one period can be specified for the document header (i.e. condition table A019). The same applies to each item (i.e. condition table A016) and to each item/plant combination (i.e. condition table A068).
You can use any periods. However they must not overlap for a variable key.
When conditions are changed, new condition records are nevertheless written.
Because volume rebate conditions are not taken into account in outline agreements, they are not processed.
No subitems (e.g. inclusive/exclusive bonus quantities, display, etc.) are taken into account.
The control key for quality management in procurement (EKPO-SSQSS) and the certificate category (EKPO-ZGTYP) are only taken into account to a certain extent. These two items of information are copied from the reference contract or material master, but cannot be changed; neither are any checks carried out for these two fields.
The revision level (EKPO-REVLV) cannot be changed because various quality management routines were not implemented.
Version management (Document Change Management) is not supported.
External services (planned or unplanned) are not supported.
The creation or changing of configurations is not supported.
Further information
When a purchase contract is changed (activity 02), the following authorization objects are checked:
M_RAHM_BSA Document type in contract
M_RAHM_EKG Purchasing group in contract
M_RAHM_EKO Purchasing organization in contract
M_RAHM_WRK Plant in contract
Parameters
PURCHASINGDOCUMENT
HEADER
HEADERX
VENDOR_ADDRESS
TESTRUN
TECHNICAL_DATA
EXP_HEADER
ITEM
ITEMX
ACCOUNT
ACCOUNTPROFITSEGMENT
ACCOUNTX
DELIVERY_ADDRESS
ITEM_COND_VALIDITY
ITEM_COND_VALIDITYX
ITEM_CONDITION
ITEM_CONDITIONX
ITEM_COND_SCALE_VALUE
ITEM_COND_SCALE_QUAN
ITEM_TEXT
HEADER_TEXT
HEAD_COND_VALIDITY
HEAD_COND_VALIDITYX
HEAD_CONDITION
HEAD_CONDITIONX
HEAD_COND_SCALE_VAL
HEAD_COND_SCALE_QUAN
PARTNER
PARTNERX
RELEASE_DOCU
EXTENSIONIN
EXTENSIONOUT
RETURN
Exceptions
Function Group
<b>rewards point for helpful answer.</b>

MM Outline Agreement Screen Flow

Our client has a requirement on contracts and scheduling agreements where they would like to see, displayed, the extended value of the line item and the total value of the outline agreement. I have located the fields needed and they seem to serve the client's requirement, but cannot determine how to get them to display on the outline agreement transactions (ME31,2,3....). The line item extended value field is found on EKPO_BRTWR; the document total is found on EKKO_RLWRT. Is there a way without doing a core mod that I can get these fields displayed on the documents on-screen?
Thanks!

hI,
For any document SAP flow will be header detail and item details.the aggrement total value comes in the header like for contract of type WK Value contract will have the total contract value , and will be available in the header screen of the aggrement . and the item cost will be in the item over view screen of the contract, with its qty and value. if you want furthur details like other conditions for that item , select that item and go to the conditions tab in the menu bar , then those details also will come.
Check the table EKKO for the header details and EKPO for the item details.
Regards,

Difference B/w Framework & Outline Agreement

Hi Gurus
I am new to SAP MM, can anyone please tell me the difference b/w framework orders and outline orders/ agreement.
General examples of this regard will be very helpful.
Regards
Imran

Dear,
A Frame work order is :
Purchasing document used for the procurement of materials or external services. Instead of stipulating a specific delivery date, this type of purchase order has an extended validity period. Goods or services can be supplied or performed against it over this period without the need for any further written instruction to be issued by the buying entity.
Framework orders are defined with document type FO. They are used in accelerated procurement processes in connection with preventive maintenance (servicing) plans or invoicing plans, and for blanket purchase orders (purchase orders with specified limits).
A framework order covers multiple procurement transactions over a longer period in cases where the administrative costs of processing discrete POs would be disproportionately high.
An Outline agreement is :
Outline agreement also referred as Contract in SAP.
Outline Agreement can be of 2 types:- Contract and SA.
Contract is where you have a contract with the vendor,may be a for a predetermined quantity or predefined value. So everytime you need the material, you need to make PO ref the contract asking for the delivery of the material. In such instance when PO is ref with contract its called contract release orders or call off orders.
Scheduling agreement is a long term purchase agreement, where you will keep issuing the delivery schedules whenever there is a change in requirement or at predetermined time intervals. The delivery schedule can be on hour/daily/weekly/monthly basis. But it will contain different zones viz. firm/tradeoff/Forecast. Firm zone schedules are confirmed requirement and need to be taken by ordered party. Tradeoff zone requirement is to purchase the raw materails and ordering party is liable to pay raw material cost, in case of requirement cancellation. Forecast zone requirement is to help the vendor to plan his requirements.
SA is also an agreement with the vendor for the supply of matl, may be a quanity or value. The delivery dates will be maintained in ME38 ref the SA which are called delivery schedules.So you can maintain the delivery schedule and communicate the vendor on Forecase basis or JIT basis. And when you need some more matl then will only create SA deliveries using ME38. SA could be of 2 types:- without release documentation-system will transmit the delivery info to the vendor once you save the document.
With release documentation- after creating the delivery schedules you need to create SA release using ME84.
The main difference between contract and SA is volume of docs generated would be higher in contract since everytime you need to make a PO ref the contract and its time consuming, whereas SA can be integrated with MRP such that it automatically creates delivery schedules during MRP run provided if there is a requirement to the matl.
Regards,
Syed Hussain.

Error while attaching document to report on Portal - Invalid selection valu

Hello All,
We are running our reports on Portal and as per the business requirement the users have to create comments or attach documents to certain amounts in certain columns and once they create the comment a document icon shows up near that amount (for example there are 3 columns Budget, actual, balance then the user have to create comment for some amounts which needs explanation) they do that from context menu Documents -> Create new Comment.
Now we want those documents to be saved on Infoprovider level and not on master data for any particular object. We have activated the flag "Characteristic is document property" on related infoobjects. We have the flag to display document icon on Infoprovider active in the web template. Now when I run the report I am able to create new comments on first two columns and when the report refreshes it shows me icon near that amount but it gives me errors on third column after the report refreshes itself. Now when I go in portal KM repository where documents are stored I do see the document that I created for the third column as well so looks like the document is getting created and being stored but the issue is when it tries to display the icon on that third column.
The error I get is this:
The initial exception that caused the request to fail was:
Invalid selection value: AttributeMember
com.sap.ip.bi.bics.dataaccess.resource.impl.bi.exceptions.BicsResourceBwRuntimeException: Invalid selection value: AttributeMember
at com.sap.ip.bi.bics.dataaccess.resource.impl.bi.selector.selection.ProviderRange.setLowForced(ProviderRange.java:297)
at com.sap.ip.bi.bics.dataaccess.resource.impl.bi.selector.selection.ProviderRange.setLow(ProviderRange.java:291)
at com.sap.ip.bi.bics.dataaccess.resource.impl.bi.selector.selection.ProviderRange.set(ProviderRange.java:469)
at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.selection.SingleMember.set(SingleMember.java:125)
at com.sap.ip.bi.km.common.assignment.AssignmentMember.isContained(AssignmentMember.java:192)
Please give some inputs if anyone is facing same problem or is anyone has worked previously with this kinda of stuff.
Thanks in advance.
Kiran

Hi!
Have you solved this problem? I have the same problem after a SPS implementation (SPS 17). The message appears when we select a single value in a DP (hierarchical filter item) that filters another one, but when I select a node it doesn't.
Before the patch implementation the apliccation worked ok.
Any idea?
Thanks in advance.
Jose

How to reflect variable price in outline agreement

We procure many very complex tools that have options which significantly affect the price of that tool. We would like to be able to reflect those price differences in the outline agreement by option within the following boundary conditions.
1. Do not want to create a new material master for each option
2. Do not want to utilize BOM
3. We are buying the tool so sales order solutions won't work for us
I have looked at configurable materials where I set up characteristics to reflect the options but I have not been able to figure out a way to price those individual options. I do see how I could create multiple line items on the outline agreement for the same material and put unique combinations of the option characteristics in individual lines but that means I have to create a line item per option combination permutation which is much more painful than simply pricing individual options. I also haven't seen any way to get SAP to select the correct line item based on these characteristics when doing source selection on the PR or PO. I have started looking at variant pricing but that is completely new to me and I am not sure if that is going to go in the direction I want. My fear is that this just allows me to price a combination of characteristics vs. pricing individual characteristics then combining the prices at the time of purchase (no different that having to create an OA line item per option combination permutation). My apologies in advance for the convoluted message but it is difficult to ask about solutions when you are not sure what functionality potentially exists.
Thanks,
Ben

Hi
Try to check with variant Configuraqtion may be upto some extent helpful
Check the link
http://help.sap.com/saphelp_erp2004/helpdata/EN/92/58d455417011d189ec0000e81ddfac/frameset.htm

Attach document to Outline Agreement

Similar Messages

Maybe you are looking for