Modify Outline agreements conditions

Hi guy , Does anyone knows a BAPI or Function to update or modify conditions in Contracts , I thougth create a batch input but i think is almost impossible because every contract has diferents numbers of conditions .

Similar Messages

Few condition types missing in Outline agreements

Hi,
In PO, I am getting all conditions but in outline agreements (either contract or sch.agreement) few are missing. How to get all conditions in Outline agreements?
Regards,
Sattuj

dear sattuj
check inforecord tab , wether it is getting field or free , if it is rffering any inforecord than make sure that info record have all the condition type ....
reward points if helpfu
thanks and regards
ravikant dewangan

Find condition record for outline agreement

I want to know how I can find the condition record for an outline agreement. The condition number is not stored in EKKO and within the ME33K transaction I can view the condition by drilling into the item level (EKPO), but I canot find anyway of linking the agreemtn to the condition table KONP.
The reason for the qeustion is we want to outpu all agreements that have a certain condition. Any ideas.

try this code
REPORT zpwtest .
TABLES : ekko , ekpo , lfa1 , komk , komp , t001 , t001w , komv .
DATA : tkomv TYPE TABLE OF komv .
PARAMETER : p_ebeln TYPE ekpo-ebeln ,
            p_ebelp TYPE ekpo-ebelp .
SELECT SINGLE *
FROM ekko
WHERE ebeln = p_ebeln .
SELECT SINGLE *
FROM ekpo
WHERE ebeln = p_ebeln
AND ebelp = p_ebelp.
SELECT SINGLE *
FROM lfa1
WHERE lifnr = ekko-lifnr .
SELECT SINGLE *
FROM t001
WHERE bukrs = ekko-bukrs .
SELECT SINGLE *
FROM t001w
WHERE werks = ekpo-werks .
CALL FUNCTION 'ME_FILL_KOMK_PO'
EXPORTING
    i_ekko = ekko
    i_ekpo = ekpo
    i_lfa1 = lfa1
    i_t001w = t001w
    i_t001 = t001
    i_kalsm = ekko-kalsm
    i_kappl = 'M'
    i_kvorg = '02'             "Preissimulation
IMPORTING
    e_komk = komk.
IF komk-prsdt EQ 0.
komk-prsdt = sy-datlo.
ENDIF.
komk-fbuda = sy-datlo.
CALL FUNCTION 'ME_FILL_KOMP_PO'
     EXPORTING
          i_ekpo = ekpo
          i_t001w = t001w
          i_ekko = ekko
          i_komk = komk
*              I_MT06E = MT06E
*              I_EINA = EINA           "hier nicht gefüllt
     IMPORTING
          e_komp = komp.
CALL FUNCTION 'PRICING'
EXPORTING
    calculation_type = 'B'
    comm_head_i      = komk
    comm_item_i      = komp
IMPORTING
    comm_head_e      = komk
    comm_item_e      = komp
TABLES
    tkomv            = tkomv.
LOOP AT tkomv INTO komv .
WRITE : / komv-kschl , komv-kbetr CURRENCY komv-waers , komv-waers .
ENDLOOP.

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

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

Global Outline Agreement Distribution

Hello,
i try to distribute global outline agreement ( transaction type GCTR ) from SRM 4.0 to ERP 2004.
But I can´t find in my browser ( its service = bbp_ctr_main ) the header data "Distribution".
I see in my header data only following taps:
Basic Data / Documtents / Conditions / Output Logs / Status / Approval Preview
I set up following things till now:
- IDoc type = BLAREL02 as Inbound Processing in SRM System
- IDoc type = BLAREL02 as Outbound Processing in Backend System
- transaction type = GCTR with internale number range in SRM System
- transaction type = GCTR with external number range in Backend System
- BADI: BBP_CTR_BE_CREATE in Method: CONTRACT_PROCESS_TYPE_FILL
   EV_PROCESS_TYPE = 'GCTR'.
- BADI: BBP_DETERMINE_LOGSYS in Method: CONTRACT_LOGSYS_DETERMINE
   CV_LOGSYS = 'our Backend System'.
- PPOMA_BBP - Attributes; Tab: Function -under Local I mapped the Purchasing Organisation and the
   Purchasing Group with Backend System
*Which customizing is still missed to see this tab "Distribution" in the header data?!
Would be glad if someone could help.
Best Regards
J.F.

If you really want to do GOA, you've got the wrong service (CTR_MAINCC is the one you are looking for). The role stratpurchaser* has both transactions: contract and global outline.
BBP_DETERMINE_LOGSYS does not need to be implemented, BBP_CTR_CREATE_BE neither (maybe for condition mapping!).
You are missing blaord for replication to ECC from SRM, you are missing BBP_SRV if you want to make GOA for services.
Along the way you will probably find that some other things need to be customised in ECC (setting up of global company, some other minor stuff like company code that's missing in ECC).
So basically you don't miss any customising for seeing the tab, but for replicating GOA you DO miss something.
In the Wiki section for SRM on this site you can find the configuration guide for setting up of contracts and GOAs, if you follow that you will have done around 90-95% of all necessary steps.
Regards,
Robin

Output determination: Dispatch time for Outline Agreements

Hi gurus,
I have an issue, when I am creating an outline agreement, by defaul the output message type: NEU is showed, and, it is fine, but, the dispatch time is always = 1 - Send with periodically schedule job.
In the customising of the output NEU, I have:
General data:
Access sequence = 0001
Check box active = Access conditions
Check box active = Multiple issuing
Print parameter = Purchasing group
In the fine-tuned control, the "Update Print-Related data" is not active.
And, I do not have defined any message schema for this output.
And, then, I customised the dispatch time for NEU with the value = 4 - Print immediately, but, still is appearing the dispatch time "1".
Then, I created 1 condition record with POrg, Doctype and Vendor, but, still is appearing the dispatch time "1".
Could you help me with this, please?
Kind regards,
Sandra PF

Hi Biju,
The point is that this output message type does not have a "Message schema determination", for that reason, if I am creating the condition record, it will be never updated. I was doing a testing and saw it.
But, if my message type NEU does not have any schema and according to SAP, by default will define the message type NEU, why the dispatch time is still = 1 if in the customising of NEU I have defined the dispatch time = 4?
More ideas?
Kind regards,
Sandra PF

FM for MM Contracts (outline agreements)

Hi everybody !
I need your precious help...
I have to change regulary the price conditions (PB00) for some items in contracts, and I wanted to know if there was a function module or a bapi that could do that, and, is there an FM or a BAPI that could add some items in (known) contracts ?
Thanks a lot,
E.Briot.

Hi,
Use BAPI BAPI_CONTRACT_CREATE
Check this thread for sample code
How to implement create outline agreement ( ME31K) in ABAP
Regards,
Satish

SPRO config field for Material Master & Outline agreement Contracts

Dear Gurus,
I want the Field AUTO PO should be mandatory field - for creating New materials - Can you please suggest me in SPRO configuration?
For outline Agreement ( contracts) - i want to make the Plant field as mandatiry - Can you please suggest me in SPRO configuration?
Please advice
Regards
RS

Hi,
Transaction MEKB is for maintaining Condition records, in you PRD server ask concerned to maintain condition record using MEKB for contract and its line item.
Procedure is
1. Input in the intial screen is Purchase org, Contract number and relevant line item number and execute
2. In the following screen highlight the line item and click on create (F6) button in the tool bar (First one from left)
3. In the following screen inside grid maintain price in amount column agains the condition type
If you have done the above steps then AUTO should work
Check on it as eill:-
Re: pr mandatory for po
Re: Auto PO in ME59N
pherasath

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

Outline Agreement of FS Contarcts

Dear experts,
I'm struggling to try to understand how CRM Outline Agreements works.
Basically I can see that the standard solution privides two kinds of OA:
1. Promo Agreement: trans type DP, item categ DPI
2. Master Agreement: trans type MA, item categ MAF.
II succeeded in understand Promo Agreement, with which I can add third party subvention going to automatically add a Third Party Relationship on the FS contract, according to the access sequences defined in customizing.
Regarding Master Agreement, I already noticed that the determination on contract is customized differently in of respect DP, but is not such a problem.
I'm facing great difficulties in managing price agreements, payment structure and in reporting the results on the FS contract.
Do anyone has a "Best practice documentation" on how to manage and customize an Outline Agreement MA?
- Price agreements: It often gives errors (i.e.: when you try to maintain condition records pricing agreement the condition record is disappears from display during creation.).
I currently assigned a cond function group to the item category MAF to which is assigned a condition type with an access sequence containing the following accesses:
10     SAP00090
20     SAP00099
30     SAP00089
- Payment structure: I cannot insert flow categories in the payment structure of the OA item because the system gives the following error:
tem 1000: Payt struc.: You must enter a flow category before the first program run
Diagnosis
You have not entered a flow category for a step in the payment structure. You must enter a flow category before the first program run, otherwise you must change the flow category later. However, you are not then permitted to change the flow category group.
Procedure
Delete this row and insert a new row in the payment structure. Enter a flow category before the first program run.
When I create an FS Contract and the OA is determined in it, I cannot see any result such as, for example, the price agreement.
Do anyone knows how the outline agreement MA affects the FS contract?
Do anyone knows how to insert the payment structure on the outline agreement's item?
Thanks and regards
Dario

Hello,
Item category 'W' in a contract is not meant for automatic creation of a purchase order. It does not have a net price, where do you expect the system to pick this price from? Tax code only comes in later. Your error also talks about that.
The material group contracts can be used to keep track of orders so that they do not exceed a value limit.
In case, you do not know the material at the time of contract/ or have many similar type of materials use item category 'M' Material instead. In this you can specify price as well as tax code and use for auto POs.
Item Category/Account Assgt. Category in Contracts - Purchasing (MM-PUR) - SAP Library

Modify existing rebate condition and exclusion

Hi
We are rebate agreements for customers. Currently I want to modify rebate condition in one of rebate agreement.
Scenario: let us June 10th 2010 onwards, the rebate % is 3% for Profit center 'xxxx' & customer 'yyyy' instead of 1%. And 3% needs to accrued on billing docs going forward. How to set up this.
I tried to modify existing rebate condition using VBo2 as follows: went into rebate agreement using VBo2, changed rebate % for condition record with effective from 06/11/2010 and Saved. problem when I ran VBOF program, system posted reversal accrual for old rebate condition 1%. Old condition record validity from 01/01/2009 Valid to 12/31/2011.
I have one more question. We want to set up rebate condition for all materials exclude some of them. we have thousands of materials for which we need to calculate rebates. but we want to exclude some materials in the rebate agreement. How to set up such exclus
any ideas really appreciated
thnx

The key of your condition table (the one supporting your condition record in the agreement) is evidently Profit Center / Customer. So for any combination of profit center and customer, you can maintain a rate and validity period.
You are attempting to maintain two separate records having the same key. As you have experienced, the system does not allow it.
The simple solution is to expire that rebate agreement and start a new one with the updated validity period and conditions.
As for excluding certain materials, you need a more detailed key in your condition table. Something else from the material master seems appropriateu2014Commission Group for example. Maintain commissionable materials in group 01 and non-commissionable ones in group 02. Then a key combination of Commission Group / Profit Center / Customer would work well for you.
Regards,
Ken

Error ME 083 if you add outline agreement in a PO

Hello Guru
I have a issue when I perform next process:
1. I create a PO with a item with account assignment Q with a WBS element
2. I create an outline agreement with account assignment Q with the same WBS element
2. I modify the PO by ME22N or Bapi (BAPI_PO_CHANGE) adding the outline agreement, in this step error ME 083 (Please enter WBS element) rise up, but the WBS element field still hold the initial WBS element.
The only manual action to correct it, it is to deleted the initial WBS element and insert it again.
Do you know if there is a OSS note to solve this error?
regards!

Hard to tell what’s going on from the information you are providing; but just looking at the first line of your sample code:
Have you checked in the debugger to see what your dataProvider looks like?
You want a resultHandler to set some kind of list – let’s say a previously declared AC, which then becomes your dataProvider for the DataGrid. Something like:
private function amfCallResultHandler(event:ResultEvent):void{
      Var someVar:ArrayCollection = event.result as ArrayCollection;
      blah blah blah;
      myDataProvider = someVar;
HTH,
Carlos

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>

PR / Outline Agreement - UOM & Charges

Hi,
The client is giving services charges based on % (e.g., For recruiting services, when the candidate (of the vendor) is selected, then the recruiting vendor will receive 10% of that candidate's basic pay). The basic pays varies from position to position. For this scenario how the user has to prepare the PR (which UOM), and how to create outline agreement (i.e.,on which conditions/price).
Thanks,
Edited by: astudent on Dec 18, 2010 7:24 AM

Hi,
Create Service Masters of different position of candidate (like example: Service for Consultant, Service for Software engineer, Service for Sr. Consultant & Service for Sr. Software engineer with UOM is u201CEAu201D for all) & create a service vendor as recruiting service.
Create a service PR and then Service PO with service master with item category D & account assignment K & you can enter manually the price to be entering as 10% of amount of basic pay ( also you can enter service tax in invoice TAB 10.3%, if applicable) & save. Then you can do SES, MIRO and then payment to vendor.
NOTE:
If you want have outline agreement before PR& PO, you can create an outline agreement with ME31 with item category D and account assignment category U. But during creation of PR & PO wrt outline agreement you can enter account assignment category as you required ( K or P) by changing account assignment category U.
Regards,
Biju K

Modify Outline agreements conditions

Similar Messages

Maybe you are looking for