Distributed contract release query!

Hi all,
Need help!
As I have created ''distribution contract'' without any plant. Now when trying to release the contract without putting any'' plant'' as I want to leave it open so that as when required ......my other company ''plant'' can create a release order against the contract later.
But during my release order creation... ..system is asking for Plant and now allowing me to save the document. Is it correct for system to ask for PLANT or is there any problem whcih need to be rectified.
Let me know your thoughts and advice.
Thanks in advance.
Cheers!

Thanks to both of you for your time.
But clear me out if I am wrong. I am trying to do my scenerio as per the theory goes for DISTRIBUTED CONTRACT, as follows,,
EXAMPLE -I have company code- ABCD...... & pur org -ABCD............. and plant -A & B with same company code.
now i have created contract with MATERIAL-A (1000 qty) ''without account assignment'' and ''Plant'' in my CENTRAL SYSYTEM.
Therefore now i am trying to do realease order against the contract with proper account assignment , but ''without a plant'' so that my central system makes the contract available to my local system ( so my local company plant A & B can create release order later as per thier need using thier own plant number in my LOCAL SYSTEM)
I guess theory says the same as I describe above. Now could any body let me know if I need to correct somewhere OR how do the actual FLOW happens.
Many thanks in advance.

Similar Messages

Central Contract release in ME35K

In SRM a central contract was created and then distributed to SAP ERP ECC 6.0 Backend.
In backend system a release strategy exists for the distributed contract.
When trying to release this contract with ME35K the contract will not be found.
Checking the table EKKO the contract is there and the release strategy is correct.
Debugging transaction ME35K we found that the following statement deletes the distributed contract.
*- Check for EhP4-Switch and Central Contract
IF cl_ops_switch_check=>mm_sfws_p2pse( ) = 'X'.
DELETE xekko WHERE bstyp EQ 'K'
AND statu EQ 'K'.
The question is if there is a switch which needs to be activated or deactivated that the contract can be released by ME35K?
The switch should be: MM_SFWS_P2PSE
Or is it SAP standard that distributed central contracts cannot be released in ERP backend with ME35K?
Thanks in advance.
Manjunath and Reagan

Hi
Are the contract originated in SRM ?
In CCTR contract, all approval process happened in SRM web front itself.
Do you want to make approval process again in ECC ?
After approval of CCTR , the contract ventured from SRM to ECC and this contract is available as source of supply for SRm as well as ECC.
Muthu

Central Contract Release Orders

Hi,
I've done all the necessary steps for central contract management and my contracts are distributing successfully to ERP.
This is contract is used in both SRM and ERP as a source of supply.
But my issues is, when i create contract release order in SRM for the contract i've distibuted to ERP it doesn't update the contract in ERP with the contract release order create in SRM. Or if a Contract release order is created in ERP it does update SRM.
What BADI or a program i can use to achieve update contract both ways? Or is it a standard functionality not to update the contract in both system?
Regards,
Gigies

I am not sure as I have to test this in system but i found this some where which needs to be checked.
Section 3: Default Transaction Types
If there are multiple transaction types determined, then the default entry in the transaction type dropdown box is set to 'space'. If there is only one entry found for the user then this will be displayed as the default entry in the dropdown box. Here is the code section where it happens: /SAPSRM/CL_CH_WD_DOM_SOCO_GAF3, /SAPSRM/IF_CLL_MAPPER~REFRESH:

Contract Release value is not updated with Limit item value

We have SRM 4.0 with ECS scenario.
Contract are created in SRM and replicated to ERP.
If we create PO with Service line and Limit line using contract in both of these line items, contract Release value is getting updated only with Service line item value.
But the contract Total value is the addition of Service and Limit value of PO.
Why Contract Release value is not getting updated with Limit item value. Please help as early as possible.

Hi Sandeep
Yes. there are various reasons .upon your contract incorrect status and linkage not establised / or more attachment in SRM GOA.
what type of contract are you using? GOA or CCTR
If it is GOA - which version of SRM and service pack ?are you in ?
If it is a GOA , BLAREL idoc might failed to post the release value in the SRM .
How contracts are created material / mat group ?
to fix or understand the issue, you need to recreate the issue.
what is the ERROR in BLAREL in SRM idoc monitoring ?

Contract Release Value is not updated with Confirmation or Invoice value

The release value for a contract in SRM EBP shows the value of purchase orders created using that contract. It does not take into account confirmation and/or invoice values.
For example I create a PO for 10 items at £100/each using Contract ABC. The total value of the PO is £1000 and the release value contract ABC would be £1000. If I then only confirm and invoice 5 items (£500) for the PO, the release value of contract ABC stays at £1000 even though I would expect it to update to £500
Therefore the release value of the contract could be incorrectly overstated if purchase orders are created against the contract but not actually invoiced/confirmed for their total value.
Please could you confirm the correct functionality and how I could find out the the true invoice value of purchases made using a contract?

Hi
Which SRM and R/3 versions are you using ?
Meanwhile, please go through the following SAP OSS Notes, which will help in this case ->
Note 622045 Net value in release overview of contract is incorrect
Note 493519 Release quantities are not updated
Note 1108322 BBP_CONTRACT_CHECK wrong calculation of values
Note 1102886 Contracts: Lesser Field length for Target Value
Note 1082548 Check of Released quantity and released value in contract
Note 656181 Release synchronization of releases on services
Note 874920 Currency not allowed to be changed for a 'Released' Contract
Note 703771 Resetting release values during purchase order item deletion
Note 643823 BLAREL: Incorrect values in service segment
Note 519879 BBP_CTR_MAIN: No message when values in Contract are reset
Note 520734 Target value not converted if currency is changed
Note 528897 Documents not displayed in contract release order overview
Note 430373 BBP_CON_MNT: No releases available
Note 491993 Entry of contracts with target values
Note 437491 Purchase contract: Incorrect update of the call-off values
Note 406799 BBP_CON_MNT: Fields after contract release ready for input
Note 398168 Purchase contract: Target value is not changed
Do let me know.
Regards
- Atul

How to configure release procedure for rate contracts release

Dear all,
How to configure release procedure for rate contract following are the requirements
they are two release codes c1 & c2 <=100000,>=100000
 if c1 is not there c2 has to be approved
 Change in the value of the rate contract contract
 Change in the validity of the rate contract
 Addition of deletion of line items
While using a non u2013 released rate contract in the PO an error message should shoot out.
Also the logic should be changed while using the rate contract in the PO.
The usage of the rate contract should be till the validity of the rate contract. i.e. the measurement should be end date of the rate contract and the PO creation date and not the delivery date of the PO. &
It should be possible to refer existing valid rate contracts in purchase orders.
Regards,
bhaskar

Hi,
In SAP rate contract is known as value contract denoted with wk. The release procedure for rate contract is same as that of other contracts and scheduling agreements. The tables for contracts will vary with SA (Scheduling agreement) .You may try and maintain condition records based on the customer combination and maintian the validity date of condition records as per your requirement.For contract and PO will have the same header/item table as EKKO/EKPO, and the release
class in standard is the same FRG_EKKO, you can use the same for contract.
To distinguish if it's a contract or PO, EKKO-BSART can be used.
For contract EKKO-BSART will be MK or WK, while PO will have NB/UB etc..
You can restrict the document type to set up the release strategy for only contract.
Of cause, you can also create your own release class Z* for contract copying standard
one FRG_EKKO via CL01/Class type 032, and then assign the class Z* to customizing:
OLME:
-> contract
->Release Procedure for Contracts
->Define Release Procedure for Contracts
->Release Groups
If you have already created the PO release class.
Assign a new chracteristic of Document Category -BSTYP
Please check below link for detailed release procedure. I hope this wil help you out .Thanking you.
http://wiki.sdn.sap.com/wiki/display/ERPSCM/RELEASE+PROCEDURE#RELEASEPROCEDURE-TABLESUSEDFORRELEASEPROCEDURES

Contract Release strategy

Dear Guru,
We have three types of contracts like A type, B type, C type......with these three types of contracts we have release strategy with different conditions.
               For A type of contract : Release Strategy should trigger on cost center and value base.
               For B Type of Contract : Same conditons like above.
               For C type of contract : it should trigger on duration base like.....if contract create for one year itshould trigger manager........if one year to two years it should trigger to director........if above two years it should trigger to CEO.
          This is my requirement.....how to configure this pls explain me.
Best Regards,
Bhaskar.

Hi,
You can only have one class and so you will have to use all of the characteristics from each type of check that you want.
So you would need a characteristic of Cost centre, one for Value and one for start and end date. (in addition to whatever characteristic you are using to determine if the contract is type A, B or C.)
With the release strategies you need to ensure that for type A and B contracts the date range characteristic is not checked and so you need to specify that all date ranges are included (so if the difference between the two dates is one day to 999 years).
then on the release strategy for the type C contract, make sure that the cost centre and value characteristics are set to include all too (so cost centre 0000 to ZZZZ and value from 0.01 to 9999999, if you don't want either to be checked).
this should work, the basic idea is that you ahev to have ALL characteristics included in every strategy but you use the values to make sure that you ignore certain characteristics in certain situations.
Steve B

Services formula value in contract release order

Hi
We have a quantity contract with services, the services contain a formula ABC to determine quantity. After selecting the service in the contract release order the full contract quantity is imported resulting in an error message.
Is there a specific user exit or other method to default the service formula values ABC to 111 after selecting the service in the contract release order?
thanks

Anyone any ideas? is there a user exit/enhancement or could a user parameter work?
Any guidance most appreciated.
Adrian

Contract release orders only allowed for sche.agreements with dep.condition

hi frnds,
i got this error msg while i try to create a scheduling agreement with ref. to contracts
help me out...
thanks in advance....

Hi
Check whether you have used contract or Contract release order.
Also check the allowed document types for the scheduling agreement.
Thanks/Karthik

Deliveries and contract release order ( LIKP ; LIPS tables)

Hi,
We have an extractor for SAP BW based on LIKP and LIPS tables.This extractor is fetching all the deliveries.
What I want to know is , Do this tables have all the deliveries i.e deliveries against a sales order and also
contract release order ( or call offs or deliveries against sales order for customer with Contract).
If yes, how can I seperate the deliveries for contract release orders, I mean based on which field?
And also is there information on Total quantity of the Contract available from this tables?
Thank you
Regards
mandha

Hi Mandha
Find field definition for following:
VBELN : Delivery
POSNR : Delivery Item
LFART : Delivery Type
PSTYV : Item Category
LFIMG : Delivery Quantity
KCMENG: Cumul Batch Quantity
VGBEL : Reference Document
VGPOS : Reference Item
VGTYP : Sales Document Category
ABRLI : Int Dlv Sched No.
ABART : Release Type
QUANT : Store Quantities
You can use SE11 for definition of fields and table details.I hope this will help you.
Regards
Nagendra P Boggarapu

Mass upload contract with "Distribute Contract to Catalog" flag

I need to mass upload contract to update the flag "Distribute Contract to Catalog" (for srm mdm). What are the options. I don't see any option of that flag in the screen "Change Contracts: Mass Processing"

Solved on own
One needs to maintain System type as 'CATALOG' in SPRO >Define Backend Systems.
This makes the Distribute Contract Catalog check box to be visible in the Header tab of contract.
Regards
Sarath

Distribute contract to SRM-MDM 2.0 catalog in SRM 4.0

Hi,
My client is using SRM 4.0 and need to distribute his contracts to SRM-MDM 2.0 catalog.
Once you set the flag "Distribute contract to catalog" in the contract the XI Sender Interface that the system uses is CatalogUpdateNotification_Out form the Sender Namespace http://sap.com/xi/EBP.
The question is whether there is an XI content for SRM-MDM 2.0 and if so then how can i redirect the distribution to another interface.
Thanks,
Raz
Edited by: Raz Golan on Jan 14, 2009 8:55 AM

Hi,
You can download XI contents for SRM-MDM Catalog 2.0 from SAP Service Marketplace same as other patches. http://service.sap.com/swdc
Regards,
Masa

Contract Release Stragery

Hi All,
My Contract Release Strategy is based on duration .. When i save the Contract the release stragery trigeers...
But if the Workflow is rejected at first level then the initiator should have the option to Re-trigger ( the option is available in ME22N AND ME52N ) But it is not available in ME32K ...
IS there any solution to trigger the Workflow for the contract so that workflow can start.
Appreciate your time.
Thanks and Regards
Mahesh

Hello,
You may use CEKKO-REVNO and set version as characteristic of release class. Then any changes to contracts will trigger release procedure.
Hope this helps.
JM

Contract Release Procedure

Hi Experts,
I am new to the Release procedure,can anyone please tell me the configuration steps for this contract release procedure.
My client needs a release procedure for the quantity contract.
Please guide me how to configure this in the system.
Thanks in Advance.
Regards,
Venu

Hi,
Your question is not clear, you asked two level but each level values are not clear.Ok.
As I understand , if you want release two levels, create release charactristics with CEKKO with GNETW & with values <=15000 & >15000, Create two release codes(C1 & C2) & cretae two Release statergy( T1 & T2). Now during designing release statergy, you can keep value <=15000 with C1 release code under T1 release statergy and keep value >15000 with C2 release code under T2 release statergy
if you want release three levels, create release charactristics with CEKKO with GNETW & with values <=5000 , 5000.01-15000.00 & >15000, Create thre release codes(C1 ,C2 & C3) & cretae three Release statergy( T1 , T2 &T3). Now during designing release statergy, you can keep value <=5000 with C1 release code under T1 release statergy, keep value 5000.01-15000.00 with C2 release code under T2 release statergy and keep value >15000 with C3 release code under T3 release statergy.
For Contract Document type MK( quantity), create release characteristics with CEKKO with BSART & keep value MK only(if WK not required)
For Value in Contract, create release charactristics with CEKKO with GNETW & with values as required.You need to add all release characteristics under a release class.
Regards,
Biju K

Contract Release Reset when decreasing the Value

Hi,
As per our client requirement we need to reset the contract Release Strategy when there is a change in Total Value of contract.
As per standard behaviour on decreasing the total value of the contract release is not reset.
How we can acheive this.
Regards,

As you already have the answers in your question..
That release strategy will never re-set if the value is decreased.
It always gets reset if the value is increased with earlier value.
Why you want to reset the release when the value is decreased, as the system value which was set earlier already had been released by your approver.
And contract is ready to proceed for further process.
The system behaves like even you decrease the value which was falling under the old value so it will not trigger the release again.
If you want to reset the release again then you need yo increase the value which has not been released earlier..

Distributed contract release query!

Similar Messages

Maybe you are looking for