on 07-08-2010 2:04 PM
Hi experts,
Material listing has been activated. However, I found it does NOT activate until listing has been created.
Plz help. Thanks.
Example:
Customer A purchases product M1 & M2. If NOT creating any listing, order, let's say order number 1 can be saved. Later, listing for A & M1 is created via VB01. If using M2, order can NOT be saved for A.
Q1: Why order number 1 can be saved when listing is NOT created? Is it the standard system behavior?
Q2: If order should be checked listing once listing A00001 is assigned to order type (spro). How to meet the request?
Hello,
for information about Listing/Exclusion you may refer to the help sap on line:
[http://help.sap.com/saphelp_45B/helpdata/en/19/fdeb47b535d1118b3f0060b03ca329/frameset.htm]
[http://help.sap.com/saphelp_47x200/helpdata/en/dd/5605ce545a11d1a7020000e829fd11/frameset.htm]
Before to post generic and basic questions, please refer first to documentation available and past forums (both have user friendly search function]:
[http://www.sdn.sap.com/irj/scn/index]
[http://help.sap.com/]
Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your prompt reply.
Actually I have gone through the relevant information. But I still got the question.
My key question is why listing check NOT activate in order ONCE listing A0001 has been assigned to order type? It stars to check listing UNTIL one record of listing is created.
In my understanding, as long as listing A0001 is assigned to order type, listing check should activate in order, no matter listing is created (VB01) or not.
Plz correct my understanding if I'm wrong.
Hello,
if your customizing is done but no condition record is mainatined for neither listing and exclusion, it is standard behaviour to allow the creation of the order for all materials.
Scenario A:
> customizing (SPRO) ready
> condition records not created for Listing
> condition records not created for Exclusion
System checks first for Exclusion and then for Listing; as it doesn't find anything, it considers that everything can be sold.
Result: order can be saved.
Only when you start maintaining Listing or Exclusion records than the check is more strict.
As you may take the decision to move for a Listing logic or Exclusion logic (more difficult to maintain), here below you may find other scenarios:
Scenario B:
> customizing (SPRO) ready
> condition created for Listing (Customer A, allowed to buy M1 and M2)
> condition records not created for Exclusion
System check Exclusion first and then as no entry is valid, it continue further. When start checking the Listing find that customer A may buy only M1, M2. If customer A try to buy M3 it gets blocked.
Result: for customer A order cannot saved for M1, M2 and M3; order can be saved for M1 and M2
Scenario C:
> customizing (SPRO) ready
> condition records created for Listing (All customer may buy M1 M2 M3)
> condition records created for Exclusion (Customer may cannot buy M3)
System check Exclusion first and as for customer A one entry exists stops there (listing is checked at item level).
For all other customers M1 M2 and M3 can be bought.
Result: for customer A order cannot saved for M1, M2 and M3; order can be saved for M1 and M2.
Regards,
User | Count |
---|---|
86 | |
7 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.