Processing Constraints and Blanket Sales Agreement

Hi all,
We are using Blanket Sales Agreement, and we have defined a processing constraint to make Payment Term a required field.
If user adds a blanket and informs payment term before saving, everything goes fine. However, if user tries to save before informing payment term, the error message from processing constraint is presented, until now everything working as planned.
After that, user informs payment term and tries to save it again. In this case, OM does not generate blanket number and does not allow saving the blanket agreement. In order to be able to add the blanket, user must delete the current agreement, and add a new one, this time informing the required field. Is this supposed to work like that or is there additional setup to use processing constraints with blanket sales agreement?
Thanks for your help,
Ketter Ohnes

Hi Ketter,
to me this sounds like a BUG. I can not imagine that this is the intended behaviour. Sounds like the blanket number gets generated only once, when the form opens.
I would recommend to open a Service Request (SR) on Metalink for that issue and ask Oracle Support for help on that.
best regards,
David.

Similar Messages

Pricing Agreements vs Blanket Sales Agreements

What is the difference between Pricing Agreements and Blanket Sales Agreements? As far as I can see, they are basically the same, except you have more functionality with a Blanket Sales Agreement.

Hi,
The pricing agreement is an agreement with the customer where we can attach the Agreement price list and it will assign the agreement number as a qualifier to refer in the sale order.
Where as the blanket sale order agreement is like an standard agreement where you have to attach the standard price list and it won't assign any qualifier to refer in the sale order.
Regards,
Arumugam S.

Difference between Blanket sales agreement and pricing agreement

Hi guys
I wasted hours the other day trying to get a blanket sales agreement number in the 'agreement' field on order management. Just to learn that there's two types of agreements in OM and it seems like there's some sort of overlap.
Can someone please give me a few functional tips of key indicators of when to use which.
Similarities between Blanket & Pricing agreements:
- Both can fix payment terms
- Both can have new pricing implications (set a new price other than existing pricelists)
Differences between blanket & pricing agreements:
I tried to read the manual for OM and Pricing but the pricing agreement was a bit short of a nice introduction explaining what it was. I was hoping it would read something like this: You go to your customer, you agree the following and therefore you need a pricing agreement.
Thanks!

Ah,
It struck me that hte most obvious difference is that sales agreements track the amount/qty of releases against that agreement. So the whole release process is some functionality that sales agreements can do that price agreements can not do.
So I'm wondering what can you achieve with a pricing agreement that you cannot achieve with a sales agreement?

Item/lot Reservation against blanket sales agreement

Hi all.
my client has a requirement (in warehousing environment 11.5.10 CU2) to reserve the entire lot for a customer (preferably against a blanket sales agreement) and release the BSA in small quantities over a period of time. The lot is has to be reserved for a specific customer, may stay in warehouse for 1 or 2 years sometime, but, client agreed to received in small quatities.
Currently we are creating a dummy sales order line to reserve for that customer and manually decreasing the total reserved quantity everytime, we ship a small quatity to customer. Thinking of creating as BSA and release the shipment as and when needed, instead of standard sales order, but, no way to hold reservation at BSA level.
Any options to reserver at BSA level or any better way to hold the item in stock for a customer over multiple SO or releases over 1 or 2 year period. A particular lot is reserved for a customer, until the whole quantity of the lot is exhausted.
thanks.
Ganesan.

If you have a small number of customers, can you create a subinventory for each customer?
When you receive the material for a customer, move it to the appropriate subinventory.
And in your defaulting rules, you can default a given subinventory for a given customer.
This way, whenever you get a "Real" order for a customer, the onhand in appropriate subinventory will get reserved to that customer. This way, you don't have to create dummy orders, dummy reservations and then delete the dummy ones later to create real ones.
Just a thought,
Sandeep Gandhi

What is difference process constraints and hold and defaulting rule.

hi,
what is difference process constraints and hold and defaulting rule.
please give me a brief about all three.

Your question is quite broad but I will try.
1) Processing constraints are rules that you can define in OM that help you control the actions you can take on Order Headers, Order Lines, Invoices etc.
e.g. you can setup a processing constraint that says if you have picked an order, then you cannot cancel it.
Oracle comes with some seeded constraints but you can define your additional constraints as well.
See http://www.oracleug.com/user-guide/order-management/holds for details
2) Hold is a way of stopping progress on an order. e.g. If the customer's credit limit has been exceeded, you can have a hold applied to it. This will stop the order from getting shipped.
See http://www.oracleug.com/user-guide/order-management/holds for details
3) Defaulting rule is a mechanism to default values on sales order headers / lines etc. You can specifiy defaulting conditions and associate them with custom actions. e.g. you can say that if order type is INTERNAL then default the SUBINVENTORY on the order line to SPARES. Again, Oracle comes with some seeded ones. You can write your own. The defaulting rules also let you encapsulate complex logic in a pl/sql function and invoke it to default fields.
see http://www.oracleug.com/user-guide/order-management/defaulting-rules for examples
Hope this helps,
Sandeep Gandhi

Blanket Sales Agreements

Can Blanket sales agreements be captured as demand in ASCP?

Blanket Sales agreements are intentionally not collected by ASCP. ASCP will pick up the specific sales order releases only.
What is your intent?
Regards,
Kevin
PS. I'd like if you would add your first name to your profile or your posts.

Sales Agreement workflow errored on 3205: is not a valid role or user name.

Hi experts,
We're currently on EBS R12.1.2 We're running into an issue that seems like a very general issue that other businesses would have encountered before. We have a business user who creates most of sales agreements. When this business user left the company, we set active end date on the particular userid. Now, when we go into these sales agreements originally created by this particular userid, and put in the expiration date to expire these sales agreement. We're seeing the sales agreement workflow erroring out in the pre-notification workflow email with error 3205: is not a valid role or user name.
It seems to be this is a very typical business scenario. If you have encountered this problem, please share how you resolved this issue within your oracle apps environment.
Thank you in advance for your help,
Jennifer

Hello,
We have the same problem in 11.5.10.2. If we want use this blanket sales agreement I have to skipped this notification by sysadmin and after this I can extend end date and another user can use this BSA.
Look at Extend The Expiration Date For Closed Non-Active Expired BSA Blanket Sales Agreement [ID 1394888.1]
Regards,
Luko

Query on Blanket Purchase Agreement-- Lines Agreement

Hi friends,
I have a query on Blanket purchase agreement.When a minimum release amount is provided in the Terms >Agreement controls it is holding fine and taking that value perfectly for each release.
But when in the PO Lines,under the Agreement when i specify a Minimum relase,Quantity agreed and Amount agreed for a line,the system is not picking up the values mentioned here when i create a release.
Eg. Created a Blanket PO with a line.
For the line under the Agreement tab, specified the following values.
Minimum release : 100.00
Quantity agreed : 100
Amount agreed : 10,000.00
1.When i created a release,it allowed me to create with the release amount of 20.00
2. When i created one more release for a quantity of 500,it allowed me to go ahead.System didn't stop me or throw me any message like you are crossing the qty agreed.
How come these two cases 1 and 2 happen.
This is contradicting the agreement controls for the blanket PO line.
FYI: At the header level ,the minimum release amount are holding good and working fine.
Only at the PO Line ,the system is not taking the agreement values.
Any pointers in this regard would be great help.
Regards,
Bala.

Hi All,
I have issue with Blanket Sales Agreement(BSA) in PDF format for approval.
NOTE: To Preview and Print from the Blanket Sales Agreement header, you can use the Action, Preview and Print or right mouse click to access Preview and Print, to Preview and Print from the Blanket Sales Agreement header. When a specific blanket is open, you can initiate preview of the formatted contract document. The document always displays in PDF format when previewed from the blanket sales agreement; you will not be required to choose a file output format.
In our test instance,
I am not able Preview Blanket Sales Agreement and send it for approval through the Workflow Notification.
Requirement is customer should view the document.
Please, let me know the reason for not able to Preview the BSA.
Many thanks.
Regards
Dass
Edited by: user10255615 on Nov 2, 2008 10:38 PM

Sales Agreement query - multiple agreements

I'm wondering if there are any queries or reports out there that will show multiple sales agreements, the customers sales amounts and their accrual amounts related to COOP and Volume Rebates? Typically you need to run VB01,02 or 03 but this only produces the data for one agreement at a time. Running VB(8 will return multiple agreement but provides no financial data.
Our IT department claims this would be a major project which means it is stuck on the backburner. I feel like this should be a very basic and commonly requested report. Does anyone have any suggestions?

Hello,
We have the same problem in 11.5.10.2. If we want use this blanket sales agreement I have to skipped this notification by sysadmin and after this I can extend end date and another user can use this BSA.
Look at Extend The Expiration Date For Closed Non-Active Expired BSA Blanket Sales Agreement [ID 1394888.1]
Regards,
Luko

BLANKET SALES ORDER의 DATA가 ORDER의 DEFAULT 값으로 되지 않는 이유?

제품 : MFG_OM
작성날짜 : 2004-10-12
BLANKET SALES ORDER의 DATA가 ORDER의 DEFAULT 값으로 되지 않는 이유?
===================================================================
PURPOSE
Blanket Sales Agreement form에서 Create Release button을 선택하면
Blanket Sales Agreement의 정보들이 Sales Order form의 default 값으로
입력되어 보여야 하나 현재는 Sales Order form은 open 되지만 header나
line에 blanket의 data가 populated 되지 않는다.
이 note에서는 그 원인과 해결책을 알아본다.
Explanation
Change(s)
=========
Blanket Sales Agreement는 정의 되어 있고, Customer 정보는 Header에 입력
되어 있다. 또한 Line item은 특정 products을 위해 정의되어 있다.
Blanket agreement는 blanket order type과 연관되어 있다.
원인
====
보통 Agreements에 대한 Orders/Releases를 신청하는 Customers는 먼저
folder를 만들어야만 한다. 이 folder는 order header에 blanket number
field는 가지며 default folder로 저장되야 한다.
Blanket Sales Agreement form에서 Create Release button을 click 하면
Sales Order form이 열리고 cursor는 blanket agreement field로 이동할
것이다.
User가 다른 field로 tab을 하면 customer data는 blanket에서 release
order로 default 조회된다.
만약 Customer data가 아닌 다른 data를 blanket agreement에서 release
order로 default 하길 원한다면, 먼저 그 영향을 주는 defaulting rule을
생성해야 한다.
Fix
=====
Blanket으로부터 data를 default로 받길 원하면 Sales order header와
line에 있는 모든 field에 대한 defaulting rules은 정의되어져 있어야 한다.
Defaulting rule에서 defaulting source로 'Blanket'을 이용하여 가능하다.
Example
Price List는 blanket agreement의 값을 default로 해야 하는 business rule
이 있다면, Price List의 defaulting rules을 아래와 같이 변경한다.
Price List First Default
=========================
Source Type : Related Record
Default Source : Blanket Agreement
위와 같은 rules은 blanket header를 sales order header default로 하거나
blanket line을 sales order line의 default로 하려면 먼저 생성되어져야
한다.
Reference Documents
Note 253150.1

U00A7ECH Engineering Change with Purchase Order, Process Order and Sales Order

Hello All,
Can someone kindly explain me the integration points of Engineering Change with
1. Purchase Order
2. Process Order
3. Sales Order
I know we can see the Rev Letter in the first two. Is there a 'refresh' function inside the PO, Process Order, Sales Order by which we can get the latest and greatest revision, incase the material rev is updated/changed after the PO, Proc Order, SO is already created. Also if yes,after what status in PO, Process Order or Sales Order we cannot use the 'Refresh' button, and than what needs to be done to fix this situation.
Thanks in advance,
Sachin

Hi,
really, this depends on several factors, especially the valid from date of the ECM and its impact on changes on a BOM (which I suppose is the use case you are looking at? Or just a change on the material revision of the BOM header material?
Interesting for you should also be Order Change Management, although not applicable to process orders as far as I know:
[http://help.sap.com/saphelp_erp60_sp/helpdata/en/41/3699761bc211d2b62b0000e8359890/frameset.htm]
Regards, Ulf.

Link India Localization with Blanket Purchase Agreements and Releases

Could anyone highlight on how India Localization Taxes be linked with Blanket Purchase Agreements and Blanket Releases?
Any additional Setups required?
Shubhendu Chakraborty
Kolkata.INDIA.

Only Amount Agreed field on header level can control the checks on the blanket purchase order.

Expiration date and Price break date in blanket purchase agreement

Hi,
In Blanket purchase agreement i see expiration date and in price break i see the from date and to date, can some one tell me the difference between these two dates?
Issue
1.when i try to put an end date(expiration date) to one of the line i get this error message or when i try to cancel the po line by giving some reason it throws the same error.
The error
"You cannot cancel or finally close this agreement line because there are open purchase order lines referencing this document."
Regards
Sudharshan

Hi Sudarshan,
Expiration date under BPA is used to prevent ordering of the item after the date appearing in this expiration field. It will stop you to create new releases incase you are trying to create one after the expiry date of the BPA.
In short, If the item on the agreement has expired but already exists on an open release, you can still use the release. However, the expired line item will not be used for sourcing, and any future releases you create will not allow using the expired item.
Under Price Break, Effective from and to date indicates the validaity of Price break rule for a particular duration. This is restricted to Price break rule only.
Hope this will help.
Regards,
S.P DASH

Sales Agreements and Sales Contracts

Hello Friends,
Could anybody clarify me about what are the key differences between Sales Aggrements and Sales Contracts in SAP CRM 5.0 ?
Thanks in advance,
Sridhar Reddy.P

hi Shridhar,
A<b> sales agreement</b> is a long-term agreement between business partners in which you can define conditions (for example, prices and terms of delivery) and releasable products. These conditions and products are valid for all contracts or sakes orders that a customer creates with reference to the sales agreement.
You use sales agreements to offer (better) prices to a particular customer group (business partner type) for a particular list of products, without committing them to particular purchase quantities.
<b> Sales Contracts</b> are information related to quantity and value contracts. Therefore it delivers data on the target values and quantities of contracts for certain sold-to parties or sales organizations. It contains validity periods and released amounts as well as details about the contract status, for example, whether the contract is open, has expired or been rejected.
Hope it clears your doubt.
Regards
Arun Kumar

Contracts and sales agreements.

Hello All,
I just want to understand what is sales contract and sales agreement.
How we can set up these in ECC and CRM.
How we can download these from ECC to CRM.
Please help me.
Thanks and Regards
shanto aloor

Hi Shanto,
See documentation http://help.sap.com/saphelp_crm70/helpdata/en/46/377a08b2ea4bee8eb9f47e5c067064/frameset.htm for details on difference between contract and sales agreement - basically sales agreement doesnt have a quantity or value whereas contract do. Agreements are mainly for pricing terms.
There are standard transaction types for these WK1 WV in ERP and CRM.
SALESCONTRACT is the adapter object used to download these - just make sure the filter allows the download and then they will be automatically replicated to CRM during create. An initial load must have been executed first for sales transaction so that the delta load happens automatically.
Kind regards,
Vanessa

Processing Constraints and Blanket Sales Agreement

Similar Messages

Maybe you are looking for