Contract and scheduling aggremnt

hi
i am sunil basically from BI consultant.
when we go tcode ME33K , we need give aggrement no?
how can i decide is it for contract or scheduling
any other filed will decide ?
field provide me some information
Purchasing (MM-PUR)
A longer-term arrangement between a purchasing organization and a vendor for the supply of materials or provision of services over a certain period based on predefined terms and conditions.
There are two types of outline purchase agreement:
Contracts
Scheduling agreements

>
suneel reddy wrote:
> hi
>
> what is relation between for BSIK table with BSEG table
> i need matnr into BSIK table can i use belnr is primary key to get matnr or its better to get ekpo table with ebeln
>
> which is best possible
Please check this answered link:
Re: RBKP vs BSIK/BSAK

Similar Messages

GOA as contract and schedul agrem

Hi esperts
I am in SRM 5.0 and R/3 4.7, I need to distribute GOA as contract and schedul agreement, so I have created in SRM 2 types of GOA ZMK and ZLP and created in backend the same document types ZLP for schedul agreement and ZMK to contract, IIf I create a GOA ZMK or ZLP in SRM and try to distribute I have an error ERROR DEFINING DOCUMENT TYPE IN BACKEND, but no IDOC is created.
I have done a text with document type GCTR in SRM and backend and if I create a GOA type GCTR and choose in DISTRIBUTION tab SCHED AGREEM, IDOCS are created in R/3 but if I choose CONTRACT I have the same error ERROR DEFINING DOCUMENT TYPE IN BACKEND.
Any help will be welcome.
Thanks
Nilson

Hi Sushil Kumar
It's not my case.
I have created 3 document typesin SRM and R/3.
ZLP in SRM and R/3
ZWK in SRM and R/3
ZMK in SRM and R/3
When I create a GOA in SRM with type ZLP and set Sched Agreem in distribution tab the IDOS are created in R/3.
When I create a a GOA IN SRM with type ZWK and set Contract in distribution tab I have the error ERROR DETERMINING DOCUMENT TYPE
Why the erro occur only with Contract and no with schedul agreement?
Thanks
Nilson

Regarding : Contracts and Scheduling Agreements

Hi All SAP Proffessionals,
Can anybody tell me what do we mean by Contracts/Scheduling Agreements?

Hi Mahesh,
A contract is a type of outline purchase agreement against which release orders (releases) can be issued for agreed materials or services as and when required during a certain overall time-frame.
Contracts are of two types:
1. Quantity contracts - Use this type of contract if the total quantity to be ordered during the validity period of the contract is
known in advance.
2. Value contracts - Use this type of contract if the total value of all release orders issued against the contract is not to exceed a certain predefined value.
But a scheduling agreement is a form of outline purchase agreement under which materials are procured on predetermined dates within a certain time period. A scheduling agreement consists of a number of items, for each of which a procurement type is defined. The
The following are the procurement types:
- Standard
- Subcontracting
- Consignment
- Stock transfer
Delivery of the total quantity of material specified in a scheduling agreement item is spread over a certain period in a delivery schedule, consisting of lines indicating the individual quantities with their corresponding planned delivery dates.
Contracts and Scheduling Agreement transaction codes:
Transaction codes:
Contracts: ME31K to ME35K
Scheduling agreements: ME31L to ME35L.
Please award if helps!
Thanks!
preethi.

Diff btwn contracts and scheduling agreements????

hi buddies.....
i have facing this question in lot of interviews but cant able to answer properly....
plz gimme some interview point of view answers...
thanks in advance...
venkatesh.v

Outline agreements in procurement can be 2 types:
Contracts or Scheduling agreements.
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 matl, you need to make PO ref the contract asking for the delivery of the matl. 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.
Visit : http://help.sap.com/saphelp_srm30/helpdata/en/7d/0a093f7c392e5ae10000000a114084/content.htm

The uses of PO - Contract and Schedule Agreements

Dear friends !
does anyone knows the differences between
1 - PO
2 - Contract
3 - Sched.Agreement
The integration with MRP and other modules ?
We need this to start an study on use this documents in our enterprise.
best regards
Ale

PO is a it's a legal purchasing document used for procuring goods/services from Vendor..
there are various account assignments & Item catogeroies
combinations for which you can procure..
Contract:- It is called outline agreement and used for procurement for longer duration, as it provides you to get discounts based on your requirement.
Sched.Agreement: It is also called outline agreement, used for for procurement for longer duration on specified delivery periods..
The diff between Contract & SA is that ,
for Contract there is no specified time.. we give only period..
ex: I say I need 100 tons of steel from period 01/01/2008 to 31/12/2008..
I may procure the steel as and when required or I may procure
the total Qty of steel on 31/12/2008.
But the SA will have diff schedules for delivery of the material..
we will define the dates & time at which the material needs to be delivered in the SA itself...
The integration with MRP and other modules ?
MRP is an integration between PP & MM

Global contract and scheduling agreements

Hi,
Is it possible to create Global contract independent of company code
Then release subsequent contracts with ref.to global with each company code.
Has anybody worked on this scenario? Please help
I need details with config settings.
BR
Raju

Hi,
Thanks for your reply.
In my scenario, i need to create the contract independent of company codes and release the orders against the company codes.
I created a central purchasing organisation (did not assigned to any company codes), but while creating the contract, system is asking for the company code to enter saying that, the purchasing org. XXXX
not been assigned to a CoCode. Please enter a company code.
Please help me on this issue.
regards,
raju

Purchasing contract or scheduling agreement business flow

Hi everyone!
My user asked me if it is possible to use contract or scheduling agreement instead of purchase order for blanket order? (Bulk order, but staggered delivery throughout the year, upon an agreed price).
I know that SAP have contract and scheduling agreement functions but as far as I am aware, we still have to create PO refer to scheduling agreement or contract. I also noticed that in MIGO and MIRO, both the reference document happens to be purchase order. So, how are my users going to do the MIRO and MIGO for scheduling agreement?
Is there anything I can do in config to allow users to do MIGO and MIRO with reference to scheduling agreement instead of purchase order?
Thank you in advance.
Anisah

You can use SA docuemnt to do MIGO and MIRO as SAP standard process.
Create the SA document and schedule line for the SA document and the you can go MIGO.
Regards
Bhima

Question regarding SAP note 765494 and Scheduling agreements

In a SAP ECC 6.0 environment has anybody dealt with note 765494? It appears that the changes allow the user to change shipping data on stock transfer scheduling purchase orders using the ME22N screen (Enjoy) but not the ME32L scheduling agreement change screen. Does anybody know of a work around to change shipping data on a stock transfer scheduling agreement?

Hi Mahesh,
A contract is a type of outline purchase agreement against which release orders (releases) can be issued for agreed materials or services as and when required during a certain overall time-frame.
Contracts are of two types:
1. Quantity contracts - Use this type of contract if the total quantity to be ordered during the validity period of the contract is
known in advance.
2. Value contracts - Use this type of contract if the total value of all release orders issued against the contract is not to exceed a certain predefined value.
But a scheduling agreement is a form of outline purchase agreement under which materials are procured on predetermined dates within a certain time period. A scheduling agreement consists of a number of items, for each of which a procurement type is defined. The
The following are the procurement types:
- Standard
- Subcontracting
- Consignment
- Stock transfer
Delivery of the total quantity of material specified in a scheduling agreement item is spread over a certain period in a delivery schedule, consisting of lines indicating the individual quantities with their corresponding planned delivery dates.
Contracts and Scheduling Agreement transaction codes:
Transaction codes:
Contracts: ME31K to ME35K
Scheduling agreements: ME31L to ME35L.
Please award if helps!
Thanks!
preethi.

Can't renew contract and upgrade phones 1 1/2 days early?

Last Saturday I tried to renew my contract and upgrade mine and my wife's phones to the Galaxy S5 at the Tunnel Rd, Asheville NC location. My official contract renewal date for both phones was the following Monday, but due to the nature of my work, and the fact that I have to schedule said work around my wife's cancer treatments, I rarely am able to make it to any business within business hours. I had hoped that renewing 1 1/2 days early would be feasible, but upon asking at the Verizon store, I was told by the young lady "assisting" me that, no, they were very strict on not allowing early renewal, and that I should come back Monday. So now it seems that i have missed the buy one get one free deal? That would be very aggravating in and of itself, but imagine my surprise when a friend said no, that you could renew and upgrade 30 days before the official date, and he called customer service in my presence and proved it. So was I pushed out of the store because they were busy, or were they just hoping that I would come back on Monday and pay the normal price for both phones? Is there any way that I can still get the bogo deal? Extremely unhappy with Verizon at the moment, I wish there were more options in the rural are in which I live.

The store service is no good for any situation even MILDLY complicated. We upgraded my husband's phone 3 days early because he was deployed and coming home three days prior to his renewal date and his previous phone no longer worked. He did it over the phone but the order mistakenly got cancelled. Went into a store to try to get it handled and they will literally tell you "We work on a different system that the customer service center." I don't even know what that means, but basically, unless you are starting new service, paying a bill, or buying accessories, they will be of no help. I went home, called back into customer service and got it situated. Had you called in, I am almost certain they would have upgraded you. Unfortunately, as someone has already stated, if the deal is over, they most likely will no longer honor it.

Approval for Contract and Order based on PO date and Document Date Combinat

Dear All,
I have a critical requirement from my client.
1. If the PO date in the contract is less than 10 days or more of the document date [Created date] then further process should not be allowed. Only authorized person should release the contract, and then order creation should be possible.
For example: Customer PO date is 18-07-2011 and if the document date is 28-08-2011, then system should stop for further processing. Only after release this should be allowed to proceed.
2. Sales order scheduled date for item is 30.07.2011 and if the PO date is 18.07.2011 again system should again go for approval. Business requires this because the time gap between the PO date and the delivery date is very short, so only on approval the next process should be allowed.
Is this possible through Status profile? I have tried this but I canu2019t give condition like if it less than the PO date system should go for approval.
Kindly guide me if this is possible and share your ideas.
Best Regards,
Venugopal

Hi Venu,
In user eixt USEREXIT_MOVE_FIELD_TO_VBAP (inlcude MV45AFZZ) write the code to compare the PO date and contract creatioon date and if the PO date is 10days less than the contract creation date reject all the line items with a special reason for rejection at the item level if the document is a contract or if the document is a sales order then populate a delivery block.
Regarding the authorization to release the contract you can think of below options.
Give authorization to only specific people to remove the reason for rejection or remove the delivery block.
Or
If you want to automate the approval process then based on the delivery block setup workflow which will raise an event and trigger an email to the approver inbox. For the approval you can give options like Approve/Reject. Based on the apporver's action design the workflow to change the contract accordingly i.e either removing the delivery block or keep it as it is.

Service Contracts Billing Schedule Creation Error

Hi,
I have a requirement of creating service contracts from back-end for which I am using the oks_contracts_pub.create_contract_header, create_service_line, and create_bill_schedule. I am creating my contracts with active status and renewal type of EVN (Header level), FUL(Line Level). My contract is of type subscription. The contract header and line are creating fine but the Bill schedule API is throwing an UNEXPECTED ERROR. The billing schedules need to be created based on accounting rule which can be quarterly or monthly. I have included the bill schedule code (hard coded values) for review. Any help is greatly appreciated.
Also the version I am working on is R12
________________________________________________CODE___________________________________________________________________
CREATE OR REPLACE PROCEDURE BILLING_SCHEDULE AS
l_strm_level_tbl OKS_BILL_SCH.STREAMLVL_TBL;
v_bill_qtrs NUMBER := 0;
v_bill_mths NUMBER := 0;
v_bill_days NUMBER := 0;
v_net_amount NUMBER := 468;
v_acct_rule_name VARCHAR2(50) := 'QUARTERLY';
v_amt_per_day NUMBER;
x_error_locator VARCHAR2(2000);
v_start_date DATE := '04-MAY-2010';
v_end_date DATE := '25-MAY-2010';
x_return_status VARCHAr2(3);
x_msg_count NUMBER;
x_msg_data VARCHAR2(2000);
v_billing_sequence NUMBER;
x_chr_id NUMBER := 17000;
x_line_id NUMBER := 223248604345353294444923586786456728480;
g_day_uom VARCHAR2(10) := 'DAY';
g_month_uom VARCHAR2(10) := 'MTH';
g_quarter_uom VARCHAR2(10) := 'QTR';
v_amt NUMBER;
v_invoicing_rule_id NUMBER := -2;
BEGIN
--Create Billing Schedule based on accounting rule
okc_context.set_okc_org_context;
MO_GLOBAL.INIT('OKS');
MO_GLOBAL.SET_POLICY_CONTEXT('S', 83);
v_bill_qtrs := 0;
v_bill_days := 0;
v_bill_mths := 0;
SELECT NVL(v_net_amount, 0)/(v_end_date - v_start_date)
INTO v_amt_per_day
FROM dual;
dbms_output.put_line('Calculated amt per day ' || v_amt_per_day);
IF v_acct_rule_name LIKE '%QUARTERLY%' THEN
--Quarterly billing schedule
SELECT FLOOR(MONTHS_BETWEEN( v_end_date,
v_start_date)/3),
v_end_date - ADD_MONTHS(v_start_date, (FLOOR(MONTHS_BETWEEN(v_end_date, v_start_date)/3)*3))
INTO v_bill_qtrs,
v_bill_days
FROM dual;
dbms_output.put_line('Calculated the qtrs and days');
IF v_bill_qtrs > 0 THEN
SELECT (ADD_MONTHS(v_start_date, (FLOOR(MONTHS_BETWEEN(v_end_date, v_start_date)/3)*3)) - v_start_date)*v_amt_per_day
INTO v_amt
FROM dual;
dbms_output.put_line('Calculated qtr amt');
SELECT NVL(MAX(sequence_no), 0) + 1
INTO v_billing_sequence
FROM oks_stream_levels_b
WHERE dnz_chr_id = x_chr_id
AND cle_id = x_line_id;
--Populating the stream line variables
l_strm_level_tbl(v_billing_sequence).sequence_no := v_billing_sequence;
l_strm_level_tbl(v_billing_sequence).dnz_chr_id := x_chr_id;
-- l_strm_level_tbl(v_billing_sequence).id := x_line_id;
l_strm_level_tbl(v_billing_sequence).cle_id := x_line_id;
l_strm_level_tbl(v_billing_sequence).uom_code := g_quarter_uom;
l_strm_level_tbl(v_billing_sequence).uom_per_period := 1;
l_strm_level_tbl(v_billing_sequence).level_periods := v_bill_qtrs;
l_strm_level_tbl(v_billing_sequence).start_date := v_start_date;
l_strm_level_tbl(v_billing_sequence).end_date := v_end_date;
l_strm_level_tbl(v_billing_sequence).invoice_offset_days := NULL;
l_strm_level_tbl(v_billing_sequence).amount := v_amt/v_bill_qtrs;
l_strm_level_tbl(v_billing_sequence).level_amount := v_amt/v_bill_qtrs;
l_strm_level_tbl(v_billing_sequence).lines_detailed_yn := 'Y';
l_strm_level_tbl(v_billing_sequence).due_arr_yn := 'Y';
dbms_output.put_line('Before calling the Bill Sch API for QTR');
OKS_CONTRACTS_PUB.CREATE_BILL_SCHEDULE ( p_billing_sch=>'E',
p_strm_level_tbl=>l_strm_level_tbl,
p_invoice_rule_id=>v_invoicing_rule_id,
x_return_status=>x_return_status);
dbms_output.put_line('After calling the Bill Sch API for QTR');
IF x_return_status <> 'S' THEN
x_msg_count := 1;
dbms_output.put_line('Quarterly schedule creation error ' || x_msg_data);
---DBMS_TRANSACTION.ROLLBACK_SAVEPOINT('OKS_A');
-- RETURN;
END IF;
END IF;
IF v_bill_days > 0 THEN
SELECT NVL(MAX(sequence_no), 0) + 1
INTO v_billing_sequence
FROM oks_stream_levels_b
WHERE dnz_chr_id = x_chr_id
AND cle_id = x_line_id;
dbms_output.put_line('sequence '||v_billing_sequence);
--Populating the stream line variables
l_strm_level_tbl(v_billing_sequence).sequence_no := v_billing_sequence;
l_strm_level_tbl(v_billing_sequence).dnz_chr_id := x_chr_id;
--l_strm_level_tbl(v_billing_sequence).id := x_line_id;
l_strm_level_tbl(v_billing_sequence).cle_id := x_line_id;
l_strm_level_tbl(v_billing_sequence).uom_code := g_day_uom;
l_strm_level_tbl(v_billing_sequence).uom_per_period := v_bill_days;
l_strm_level_tbl(v_billing_sequence).level_periods := 1;
l_strm_level_tbl(v_billing_sequence).start_date := v_start_date;
l_strm_level_tbl(v_billing_sequence).end_date := v_end_date;
l_strm_level_tbl(v_billing_sequence).invoice_offset_days := NULL;
l_strm_level_tbl(v_billing_sequence).amount := v_net_amount;--v_amt_per_day*v_bill_days;
l_strm_level_tbl(v_billing_sequence).level_amount := v_net_amount;--v_amt_per_day*v_bill_days;
l_strm_level_tbl(v_billing_sequence).lines_detailed_yn := 'Y';
l_strm_level_tbl(v_billing_sequence).due_arr_yn := 'Y';
dbms_output.put_line('Before calling the Bill Sch API for QTR days');
OKS_CONTRACTS_PUB.CREATE_BILL_SCHEDULE ( p_billing_sch=>'E',
p_strm_level_tbl=>l_strm_level_tbl,
p_invoice_rule_id=>v_invoicing_rule_id,
x_return_status=>x_return_status);
dbms_output.put_line('After calling the Bill Sch API for QTR days ' || v_bill_days || ' ' || x_return_status);
IF x_return_status <> 'S' THEN
x_msg_count := 1;
dbms_output.put_line('Day schedule, for quarterly accounting rule, creation error ' || x_msg_data);
--DBMS_TRANSACTION.ROLLBACK_SAVEPOINT('OKS_A');
--RETURN;
END IF;
END IF;
ELSE
--Monthly billing schedule
SELECT FLOOR(MONTHS_BETWEEN( v_end_date,
v_start_date)),
v_end_date - ADD_MONTHS(v_start_date, FLOOR(MONTHS_BETWEEN(v_end_date, v_start_date)))
INTO v_bill_mths,
v_bill_days
FROM dual;
dbms_output.put_line('Calculated the mths and days');
IF v_bill_mths > 0 THEN
SELECT (ADD_MONTHS(v_start_date,FLOOR(MONTHS_BETWEEN(v_end_date, v_start_date))) - v_start_date)*v_amt_per_day
INTO v_amt
FROM dual;
dbms_output.put_line('Calculated the mths amt');
SELECT NVL(MAX(sequence_no), 0) + 1
INTO v_billing_sequence
FROM oks_stream_levels_b
WHERE dnz_chr_id = x_chr_id
AND cle_id = x_line_id;
--Populating the stream line variables
l_strm_level_tbl(v_billing_sequence).sequence_no := v_billing_sequence;
l_strm_level_tbl(v_billing_sequence).dnz_chr_id := x_chr_id;
--l_strm_level_tbl(v_billing_sequence).id := x_line_id;
l_strm_level_tbl(v_billing_sequence).cle_id := x_line_id;
l_strm_level_tbl(v_billing_sequence).uom_code := g_month_uom;
l_strm_level_tbl(v_billing_sequence).uom_per_period := 1;
l_strm_level_tbl(v_billing_sequence).level_periods := v_bill_mths;
l_strm_level_tbl(v_billing_sequence).start_date := v_start_date;
l_strm_level_tbl(v_billing_sequence).end_date := v_end_date;
l_strm_level_tbl(v_billing_sequence).invoice_offset_days := NULL;
l_strm_level_tbl(v_billing_sequence).amount := v_amt/v_bill_mths;
l_strm_level_tbl(v_billing_sequence).level_amount := v_amt/v_bill_mths;
l_strm_level_tbl(v_billing_sequence).lines_detailed_yn := 'Y';
l_strm_level_tbl(v_billing_sequence).due_arr_yn := 'Y';
dbms_output.put_line('Before calling the Bill Sch API for MTHS');
OKS_CONTRACTS_PUB.CREATE_BILL_SCHEDULE ( p_billing_sch=>'E',
p_strm_level_tbl=>l_strm_level_tbl,
p_invoice_rule_id=>v_invoicing_rule_id,
x_return_status=>x_return_status);
dbms_output.put_line('After calling the Bill Sch API for MTHS');
IF x_return_status <> 'S' THEN
x_msg_count := 1;
dbms_output.put_line('Monthly schedule creation error ' || x_msg_data);
--DBMS_TRANSACTION.ROLLBACK_SAVEPOINT('OKS_A');
--RETURN;
END IF;
END IF;
IF v_bill_days > 0 THEN
SELECT NVL(MAX(sequence_no), 0) + 1
INTO v_billing_sequence
FROM oks_stream_levels_b
WHERE dnz_chr_id = x_chr_id
AND cle_id = x_line_id;
--Populating the stream line variables
l_strm_level_tbl(v_billing_sequence).sequence_no := v_billing_sequence;
l_strm_level_tbl(v_billing_sequence).dnz_chr_id := x_chr_id;
--l_strm_level_tbl(v_billing_sequence).id := x_line_id;
l_strm_level_tbl(v_billing_sequence).cle_id := x_line_id;
l_strm_level_tbl(v_billing_sequence).uom_code := g_day_uom;
l_strm_level_tbl(v_billing_sequence).uom_per_period := v_bill_days;
l_strm_level_tbl(v_billing_sequence).level_periods := 1;
l_strm_level_tbl(v_billing_sequence).start_date := v_start_date;
l_strm_level_tbl(v_billing_sequence).end_date := v_end_date;
l_strm_level_tbl(v_billing_sequence).invoice_offset_days := NULL;
l_strm_level_tbl(v_billing_sequence).amount := v_amt_per_day*v_bill_days;
l_strm_level_tbl(v_billing_sequence).level_amount := v_amt_per_day*v_bill_days;
l_strm_level_tbl(v_billing_sequence).lines_detailed_yn := 'Y';
l_strm_level_tbl(v_billing_sequence).due_arr_yn := 'Y';
dbms_output.put_line('Before calling the Bill Sch API for MTH days');
OKS_CONTRACTS_PUB.CREATE_BILL_SCHEDULE ( p_billing_sch=>'E',
p_strm_level_tbl=>l_strm_level_tbl,
p_invoice_rule_id=>v_invoicing_rule_id,
x_return_status=>x_return_status);
dbms_output.put_line('After calling the Bill Sch API for MTH days');
IF x_return_status <> 'S' THEN
x_msg_count := 1;
dbms_output.put_line('Day schedule, for monthly accounting rule, creation error ' || x_msg_data);
--DBMS_TRANSACTION.ROLLBACK_SAVEPOINT('OKS_A');
--RETURN;
END IF;
END IF;
END IF;
COMMIT;
EXCEPTION
when others then
dbms_output.put_line('Error ' || sqlerrm);
END;
Thanks,
Yash.

Hi There,
I have a similar requirement to create rental service contracts and create billing schedules.
Can you please pass on your functional docs so that i can refer to them.
Thanks,
Raidu

Difference between Purchase Order and Scheduling Agreement

Can any one explain the main differences between a Purchase Order and a Scheduling Agreement?
Thanks in advance

Hi,
A Purchase Order is a document that is given to Vendor to indicate our intention to buy goods from them. It contains what is the desired goods, how much quantity, price, and the delivery date, among other things.
A standard procurement cycle for this is:
PR --> PO --> GR --> IV
A Scheduling Agreement however, is a type of an Outline Agreement. Outline Agreements are divided into 2, first one is Contracts and second is Scheduling Agreement. So this is basically a long term agreement with a particular vendor that contains details on what is the desired goods, quantity, and the exact delivery dates.
A standard cycle for this is:
PR --> Create Scheduling Agreement --> Maintain Delivery Schedule (agreed dates on when vendor will send the goods and time) --> GR --> IV
As you can see, for Scheduling Agreement, PO is not required, but instead we would need to Maintain Delivery Schedule.
Just to share on Contracts, it appears as below:
PR --> Contract Creation --> PO --> GR --> IV
Regards,
Nazrin

Contract and target quantity

Hi all,
I am raising a sales order against a customer who has a contract with the company. I want the target quantity to be reduced each time a release order is raised. Can somebody explain me the copy control settings of contract to sales order. Also throw some light on the item category and schedule line.
thanks in advance.

Dear svgopal,
In copy controls of contract to order (VTAA) in header level flag the complete reference .
Wit this setting target quantity will be automatically reduced once you raise the sales order with reference to contract .
Check and revert.
Raghu.k

Contracts VS Scheduling Agreements

I have a situation where the business scenarios are totally absorbed within both the Contract and SA document type, but only 1 is to be pursued.
Can someone pls tell me the distinct adv of one over another?
I have done some rudimentary searches and have the basics but I would appreciate more thorough and exhaustive reasons for selection.
sample req:
Documents must be long term, releases issued against the outline agreement, deliveries are a nice to have but can be tied to whenever release scheduled, quantity not of importance but effective supply is, no need for PPV to be measured just so long as deliveries are made by lead time.
Thanks - macj

In that case you have to have schedulling agreement is better soltion

Differences in local Purchasing Contracts and GOA?

Hi all,
I am new to SRM and trying to figure out what are the differences between local purchase contracts and GOA? I know that GOA can be distributed to multiple backend systems whereas the local purchase contracts cannot be. Are there any other differences apart from this? and how does these two make difference to the business?
Thanks in advance...
Regards,
Kumar
Edited by: Kumar on Apr 7, 2008 9:47 AM

Hi Kumar,
As mentioned by you GOAs can be distributed to backend systems.
However the major difference between a GOA and a local SRM contract is that with GOA you can create either a contract or a scheduling agreement in the backend R/3 system.
Whenever you refer these contracts / scheduling agreements while creating a P.O in backend the status gets updated in GOA created in SRM.
You can not refer these contracts / S.A s while craeting a P.O in SRM.
Similarly the local SRM contracts can not be refered while creating P.Os in R/3 system.
Hope this makes you more clear and helps in better understanding of the issue. Clarifications are welcome.
Award points for helpful answers.
Rgds,
Teja

Contract and scheduling aggremnt

Similar Messages

Maybe you are looking for