User Exit to check whether chapter id for Material and Plant combination is maintained while creating sales order

Hello all,
my requirement is, system should give error message while creating sales order, if chapter ID is not maintained for a material and plant combination.
please suggest the user exit.

Hi
CASE 1 : All Plants are excisable.
In Material master , Foreign Trade data tab- mentioned Control code field mandatory. ( i.e nothing but Chapter ID)
CASE 2 : Few Plants are excisable
In the Case 2 you need to go for Enhancement
Program Name : MV45AFZB
User Exit: USEREXIT_CHECK_VBAP ( Item Level Check )
By using above user exit you write a logic with the help of ABAPer
Plant and Chapter ID combination table : J_1IMTCHID

Similar Messages

Tables for production order number for material and Batch combination

Dear Experts,
Please suggest the table names for finding the production order for material and batch combination .
Thanks in advance for your help...
Best regards
Nitishj

Dear
Please check in AFPO-CHARG
AFPO          Order Item Detail -Batch Number -CHARG
AFFW         Confirmations -- Goods Movements w
AFRD          Confirmations -- Defaults for Collective Confirmation
AFRH          Confirmations -- Header Info for Confirmation
Regards
JH

I want to know about ATP check requirement .generally we assigned yes or no while creating sales order

I want to know about ATP check requirement .generally we assigned yes or no while creating sales order what it means when we give Yes or No. how pegging flows
Regards
virender

Virender,
Can you be a bit more specific about ".....generally we assigned yes or no while creating sales order....." Exactly what field(s) did you 'assign'? Screenshots would be helpful.
With respect to pegging; in general, ATP has very little to do with pegging. Pegging is more of a planning concept, and not an 'availability checking' concept. There are a few exceptions in APO, but they are not commonly implemented.
Can you elaborate about exactly what you want to know with respect to 'pegging' and ATP?
Best Regards,
DB49

To release credit check while creating sales order

Hi,
I have a requirement of releasing credit check for list of open sales orders of a customer while creating a new order in VA01 for a customer.
E.g in va01,i'm creating sales order for kunnr ABC
for kunnr ABC, open sales order existing in database are 1,2,3,4
So i need to release credit check for 1 2 3 4 while creating a new sales order in VA01.
If i use FM 'SD_ORDER_CREDIT_RELEASE' in VA01 user exits it again call standard program and gives some error.
I need to know the exact point to implement the code if someone can help and also if there is another way of releasing credit check other than above FM.

Hello,
Why don't you use the include MV45AFZZ, userexit USEREXIT_SAVE_DOCUMENT_PREPARE.
You can write your code to identity all the sales orders that are due to be released for a customer and then release them.
Edited by: Kanwardeep Singh Gill on Apr 8, 2010 5:28 AM

Error: Validation failed for the field - Status While creating Sales Order

Hi,
I am getting an error while trying to create sales order header.
I have tried using provided in the metalink as well but it still doesn't seem to work.
I am on R12.1.1
Can somebody help me out on this?
The code is
set serveroutput on
DECLARE
l_header_rec OE_ORDER_PUB.Header_Rec_Type;
l_header_rec1 OE_ORDER_PUB.Header_Rec_Type;
l_line_tbl OE_ORDER_PUB.Line_Tbl_Type;
l_line_tbl1 OE_ORDER_PUB.Line_Tbl_Type;
l_action_request_tbl OE_ORDER_PUB.Request_Tbl_Type;
l_header_adj_tbl OE_ORDER_PUB.Header_Adj_Tbl_Type;
l_line_adj_tbl OE_ORDER_PUB.line_adj_tbl_Type;
l_header_scr_tbl OE_ORDER_PUB.Header_Scredit_Tbl_Type;
l_line_scredit_tbl OE_ORDER_PUB.Line_Scredit_Tbl_Type;
l_request_rec OE_ORDER_PUB.Request_Rec_Type ;
l_return_status VARCHAR2(1000);
l_msg_count NUMBER;
l_msg_data VARCHAR2(1000);
p_api_version_number NUMBER :=1.0;
p_init_msg_list VARCHAR2(10) := FND_API.G_FALSE;
p_return_values VARCHAR2(10) := FND_API.G_FALSE;
p_action_commit VARCHAR2(10) := FND_API.G_FALSE;
x_return_status VARCHAR2(1);
x_msg_count NUMBER;
x_msg_data VARCHAR2(100);
p_header_rec OE_ORDER_PUB.Header_Rec_Type := OE_ORDER_PUB.G_MISS_HEADER_REC;
p_old_header_rec OE_ORDER_PUB.Header_Rec_Type := OE_ORDER_PUB.G_MISS_HEADER_REC;
p_header_val_rec OE_ORDER_PUB.Header_Val_Rec_Type := OE_ORDER_PUB.G_MISS_HEADER_VAL_REC;
p_old_header_val_rec OE_ORDER_PUB.Header_Val_Rec_Type := OE_ORDER_PUB.G_MISS_HEADER_VAL_REC;
p_Header_Adj_tbl OE_ORDER_PUB.Header_Adj_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_ADJ_TBL;
p_old_Header_Adj_tbl OE_ORDER_PUB.Header_Adj_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_ADJ_TBL;
p_Header_Adj_val_tbl OE_ORDER_PUB.Header_Adj_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_ADJ_VAL_TBL;
p_old_Header_Adj_val_tbl OE_ORDER_PUB.Header_Adj_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_ADJ_VAL_TBL;
p_Header_price_Att_tbl OE_ORDER_PUB.Header_Price_Att_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_PRICE_ATT_TBL;
p_old_Header_Price_Att_tbl OE_ORDER_PUB.Header_Price_Att_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_PRICE_ATT_TBL;
p_Header_Adj_Att_tbl OE_ORDER_PUB.Header_Adj_Att_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_ADJ_ATT_TBL;
p_old_Header_Adj_Att_tbl OE_ORDER_PUB.Header_Adj_Att_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_ADJ_ATT_TBL;
p_Header_Adj_Assoc_tbl OE_ORDER_PUB.Header_Adj_Assoc_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_ADJ_ASSOC_TBL;
p_old_Header_Adj_Assoc_tbl OE_ORDER_PUB.Header_Adj_Assoc_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_ADJ_ASSOC_TBL;
p_Header_Scredit_tbl OE_ORDER_PUB.Header_Scredit_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_SCREDIT_TBL;
p_old_Header_Scredit_tbl OE_ORDER_PUB.Header_Scredit_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_SCREDIT_TBL;
p_Header_Scredit_val_tbl OE_ORDER_PUB.Header_Scredit_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_SCREDIT_VAL_TBL;
p_old_Header_Scredit_val_tbl OE_ORDER_PUB.Header_Scredit_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_SCREDIT_VAL_TBL;
p_line_tbl OE_ORDER_PUB.Line_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_TBL;
p_old_line_tbl OE_ORDER_PUB.Line_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_TBL;
p_line_val_tbl OE_ORDER_PUB.Line_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_VAL_TBL;
p_old_line_val_tbl OE_ORDER_PUB.Line_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_VAL_TBL;
p_Line_Adj_tbl OE_ORDER_PUB.Line_Adj_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_ADJ_TBL;
p_old_Line_Adj_tbl OE_ORDER_PUB.Line_Adj_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_ADJ_TBL;
p_Line_Adj_val_tbl OE_ORDER_PUB.Line_Adj_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_ADJ_VAL_TBL;
p_old_Line_Adj_val_tbl OE_ORDER_PUB.Line_Adj_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_ADJ_VAL_TBL;
p_Line_price_Att_tbl OE_ORDER_PUB.Line_Price_Att_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_PRICE_ATT_TBL;
p_old_Line_Price_Att_tbl OE_ORDER_PUB.Line_Price_Att_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_PRICE_ATT_TBL;
p_Line_Adj_Att_tbl OE_ORDER_PUB.Line_Adj_Att_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_ADJ_ATT_TBL;
p_old_Line_Adj_Att_tbl OE_ORDER_PUB.Line_Adj_Att_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_ADJ_ATT_TBL;
p_Line_Adj_Assoc_tbl OE_ORDER_PUB.Line_Adj_Assoc_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_ADJ_ASSOC_TBL;
p_old_Line_Adj_Assoc_tbl OE_ORDER_PUB.Line_Adj_Assoc_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_ADJ_ASSOC_TBL;
p_Line_Scredit_tbl OE_ORDER_PUB.Line_Scredit_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_SCREDIT_TBL;
p_old_Line_Scredit_tbl OE_ORDER_PUB.Line_Scredit_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_SCREDIT_TBL;
p_Line_Scredit_val_tbl OE_ORDER_PUB.Line_Scredit_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_SCREDIT_VAL_TBL;
p_old_Line_Scredit_val_tbl OE_ORDER_PUB.Line_Scredit_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_SCREDIT_VAL_TBL;
p_Lot_Serial_tbl OE_ORDER_PUB.Lot_Serial_Tbl_Type := OE_ORDER_PUB.G_MISS_LOT_SERIAL_TBL;
p_old_Lot_Serial_tbl OE_ORDER_PUB.Lot_Serial_Tbl_Type := OE_ORDER_PUB.G_MISS_LOT_SERIAL_TBL;
p_Lot_Serial_val_tbl OE_ORDER_PUB.Lot_Serial_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_LOT_SERIAL_VAL_TBL;
p_old_Lot_Serial_val_tbl OE_ORDER_PUB.Lot_Serial_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_LOT_SERIAL_VAL_TBL;
p_action_request_tbl OE_ORDER_PUB.Request_Tbl_Type := OE_ORDER_PUB.G_MISS_REQUEST_TBL;
x_header_val_rec OE_ORDER_PUB.Header_Val_Rec_Type;
x_Header_Adj_tbl OE_ORDER_PUB.Header_Adj_Tbl_Type;
x_Header_Adj_val_tbl OE_ORDER_PUB.Header_Adj_Val_Tbl_Type;
x_Header_price_Att_tbl OE_ORDER_PUB.Header_Price_Att_Tbl_Type;
x_Header_Adj_Att_tbl OE_ORDER_PUB.Header_Adj_Att_Tbl_Type;
x_Header_Adj_Assoc_tbl OE_ORDER_PUB.Header_Adj_Assoc_Tbl_Type;
x_Header_Scredit_tbl OE_ORDER_PUB.Header_Scredit_Tbl_Type;
x_Header_Scredit_val_tbl OE_ORDER_PUB.Header_Scredit_Val_Tbl_Type;
x_line_val_tbl OE_ORDER_PUB.Line_Val_Tbl_Type;
x_Line_Adj_tbl OE_ORDER_PUB.Line_Adj_Tbl_Type;
x_Line_Adj_val_tbl OE_ORDER_PUB.Line_Adj_Val_Tbl_Type;
x_Line_price_Att_tbl OE_ORDER_PUB.Line_Price_Att_Tbl_Type;
x_Line_Adj_Att_tbl OE_ORDER_PUB.Line_Adj_Att_Tbl_Type;
x_Line_Adj_Assoc_tbl OE_ORDER_PUB.Line_Adj_Assoc_Tbl_Type;
x_Line_Scredit_tbl OE_ORDER_PUB.Line_Scredit_Tbl_Type;
x_Line_Scredit_val_tbl OE_ORDER_PUB.Line_Scredit_Val_Tbl_Type;
x_Lot_Serial_tbl OE_ORDER_PUB.Lot_Serial_Tbl_Type;
x_Lot_Serial_val_tbl OE_ORDER_PUB.Lot_Serial_Val_Tbl_Type;
x_action_request_tbl OE_ORDER_PUB.Request_Tbl_Type;
X_DEBUG_FILE VARCHAR2(100);
l_line_tbl_index NUMBER;
l_msg_index_out NUMBER(10);
BEGIN
oe_debug_pub.debug_on;
DBMS_APPLICATION_INFO.set_client_info (121);
dbms_output.enable(1000000);
fnd_global.apps_initialize(2787,50703,660); -- pass in user_id, responsibility_id, and application_id
oe_msg_pub.initialize;
oe_debug_pub.initialize;
MO_GLOBAL.init('ONT');
X_DEBUG_FILE := OE_DEBUG_PUB.Set_Debug_Mode('FILE');
oe_debug_pub.SetDebugLevel(5); -- Use 5 for the most debuging output, I warn you its a lot of data
dbms_output.put_line('START OF NEW DEBUG');
--This is to CREATE an order header and an order line
--Create Header record
--Initialize header record to missing
l_header_rec := OE_ORDER_PUB.G_MISS_HEADER_REC;
l_header_rec.pricing_date := SYSDATE;
l_header_rec.sold_to_org_id := 2096;
l_header_rec.ordered_date := SYSDATE;
l_header_rec.sold_from_org_id := 121     ;
l_header_rec.salesrep_id := -3;
l_header_rec.order_type_id := 1003;
l_header_rec.operation := OE_GLOBALS.G_OPR_CREATE;
l_line_tbl_index :=1;
-- FIRST LINE RECORD
-- Initialize record to missing
l_line_tbl(l_line_tbl_index) := OE_ORDER_PUB.G_MISS_LINE_REC;
-- Line attributes
l_line_tbl(l_line_tbl_index).inventory_item_id := 124516;
l_line_tbl(l_line_tbl_index).ordered_quantity := 500;
l_line_tbl(l_line_tbl_index).ship_from_org_id := 563;
l_line_tbl(l_line_tbl_index).operation := OE_GLOBALS.G_OPR_CREATE;
-- CALL TO PROCESS ORDER Check the return status and then commit.
OE_ORDER_PUB.process_order (
p_api_version_number => 1.0
, p_init_msg_list => fnd_api.g_false
, p_return_values => fnd_api.g_false
, p_action_commit => fnd_api.g_false
, x_return_status => l_return_status
, x_msg_count => l_msg_count
, x_msg_data => l_msg_data
, p_header_rec => l_header_rec
, p_line_tbl => l_line_tbl
, p_action_request_tbl => l_action_request_tbl
   -- OUT PARAMETERS
, x_header_rec => l_header_rec1
, x_header_val_rec => x_header_val_rec
, x_Header_Adj_tbl => x_Header_Adj_tbl
, x_Header_Adj_val_tbl => x_Header_Adj_val_tbl
, x_Header_price_Att_tbl => x_Header_price_Att_tbl
, x_Header_Adj_Att_tbl => x_Header_Adj_Att_tbl
, x_Header_Adj_Assoc_tbl => x_Header_Adj_Assoc_tbl
, x_Header_Scredit_tbl => x_Header_Scredit_tbl
, x_Header_Scredit_val_tbl => x_Header_Scredit_val_tbl
, x_line_tbl => l_line_tbl1
, x_line_val_tbl => x_line_val_tbl
, x_Line_Adj_tbl => x_Line_Adj_tbl
, x_Line_Adj_val_tbl => x_Line_Adj_val_tbl
, x_Line_price_Att_tbl => x_Line_price_Att_tbl
, x_Line_Adj_Att_tbl => x_Line_Adj_Att_tbl
, x_Line_Adj_Assoc_tbl => x_Line_Adj_Assoc_tbl
, x_Line_Scredit_tbl => x_Line_Scredit_tbl
, x_Line_Scredit_val_tbl => x_Line_Scredit_val_tbl
, x_Lot_Serial_tbl => x_Lot_Serial_tbl
, x_Lot_Serial_val_tbl => x_Lot_Serial_val_tbl
, x_action_request_tbl => l_action_request_tbl
dbms_output.put_line('OM Debug file: ' ||oe_debug_pub.G_DIR||'/'||oe_debug_pub.G_FILE);
oe_debug_pub.debug_off;
-- Retrieve messages
FOR i IN 1 .. l_msg_count
LOOP
   Oe_Msg_Pub.get( p_msg_index => i
    , p_encoded => Fnd_Api.G_FALSE
    , p_data => l_msg_data
    , p_msg_index_out => l_msg_index_out);
   DBMS_OUTPUT.PUT_LINE('message is: ' || l_msg_data);
   DBMS_OUTPUT.PUT_LINE('message index is: ' || l_msg_index_out);
END LOOP;
-- Check the return status
IF l_return_status = FND_API.G_RET_STS_SUCCESS
THEN
dbms_output.put_line('Process Order Sucess');
dbms_output.put_line('new Header id:' || l_header_rec1.header_id);
ELSE
dbms_output.put_line('Failed');
END IF;
Commit;
END; Regards
knick

Kinck
The same script worked for me in vision (R12.1). You may have issues with your defaulting of a number of attributes that you are not passing in the API (like price list, line type and so on). You may want to check them.
Thanks
Nagamohan

Setting user specific contract data while creating sales order using BAPI

Hi all,
I am creating sales order using BAPI - BAPI_SALESORDER_CREATEFROMDAT2.
Now my problem is that there is no structure for contract data (i.e. VEDA), system automatically set contract data using customization values.
I am doing some validations on cotract data in MV45AFZZ which fails, because these validations are performed on standard values, user specific values r not set.
How to handle this issue, your small clue may help a lot.
Regards,
S@meer

HI
Pricing will be carried basing on the pricing
procedure.
Case1: Prices will be carried out automatically if
necessary condition records are maintained for the
condition type.
For this you can go to Sales Order-> Item Conditions
In the screen you can click on command button Analysis,
which gives you the list of condition types associated
to the pricing procedure. By clicking on the condition
type you can know the action that has taken place.
Case2: Manually forcing prices for Items.
To do this, you have to populate ORDER_CONDITIONS_IN &
ORDER_CONDITIONS_INX. Also note to identify the item
numbers, you manually pass the item number for each item
in the sales order, use the same item number for
populating conditions.
Parameters required:
ORDER_CONDITIONS_IN:
ITM_NUMBER, COND_TYPE, COND_VALUE, CURRENCY
ORDER_CONDITIONS_INX:
ITM_NUMBER, COND_TYPE, UPDATEFLAG, COND_VALUE,CURRENCY.
Hope the above info helps you. Do revert back if you
need more info.
Kind Regards
Eswar

Duplication of Purchase Order while creating sales orders for a customer

when we try to create sales order for one customer it have to create by picking up the purchase order from the table linearly.
But the problem is that here when we are trying to create multiple sales orders the same purchase order is being picked.
for example..when we create sales order 1 the purchase order picked is PO1 and
for creation of sales order 2 the same purchase order PO1 is being picked up instead of PO2.
No idocs are being generated in this, even to check them..
How shall i resolve this...? Please help me out ASAP

Hi Kumar,
Thanks for the reply. But actually the problem is that this is related to some customized table in the project. When a EDI Batch job runs in the background then automatically the SO is created and the PO is being picked from the table(custom table) and then posted against the respective SO. we are not aware of that job which is triggering this to debug. Once if we can know that particular batch job or pgm or edi or idoc what ever it is then we can debug.
Do you have any idea how can we find that particular pgm/edi/idoc/job name which triggers this creation of SO?

BAPI or FM for Material and ChapterID Combination(J1ID Transaction)

Dear All,
I need BAPI or FM for Creation of Material and ChapterID combination. I dont need for other options present in J1ID Transaction.
I cannot use Insert statement for Material and ChapterID Creation as it contains only few fields.
Please let me know regarding this.
Regards,
Anilkumar

Hello
The bapi BAPI_INSPECTIONPLAN_CREATE is used for creation. There you can assign several materials through structure MATERIALTASKALLOCATION (BAPI1191_MTK_C). There is no bapi for modifications so you can assign other materials using LSMW or BDC as Gururaj told you or in this special case populate table MAPL directly (better talk to your ABAP to decide it); I did it without issues and I checked and the function CZ_VB_MAPL_POST could update the information you need (talk to your ABAP to validate it).
Best regards
Carlos Díaz

Characteristics values for material and plant

Hi Experts,
I need to fetch characterstic values from a class Y-xx . I belive badi BAPI_CLASS_GET_characteristics
will give the result but my problem is in selection screen I am passing material no and plant
for this material and plant i need to fetch the characteristics values from the Y_xx class
Could any one suggest the BADI or FM or tables to fetch the results
Thanks in advance

Hi,
Go to MEK2, here enter the freight condition type, go to the output screen as pr the access maintained and select the line item and click on "Scales" button to see the from and to value.
Also you can check the same in "Conditions" button in Purchase Info record.

Characteristic values for the material and plant combination...

Hi Friends,
I would like to know how can we maintain the characteristic values for the combination of Material and Plant though the material is not batch managed?
Thanks in advance,
Ram

Hi Rajendra,
Thanks for quick reply. I am maintaining under classification view but it does not ask plant any where. So the value will be same across all the plants but i want to maintain characteristic values separately under each plant for same material.
Regards,
Ram

User Exit for maintaining Checking Rule while creating Sales Order

Hi Gurus,
I have a requirement where I need to assign a particular value to Checking Rule (VA02 -> Display Availability Button -> Checking Rule field (beside Checking Group field)) while creating a Sales Order in SD (via. IDOC's).
In my requirement, within one Checking Group there are multiple checking rules assigned. When I am trying to assign the checking group in userexit_move_field_to_vbap (include MV45AFZZ), it is picking up the default checking rule ('A') and not the customized one defined for our requirement.
Is there any other user exit within which I can directly assign the Checking Group and Checking Rule while creating the sales order, please suggest.
Regards,
Arvind.

You can use userexit 'USEREXIT_MOVE_FIELD_TO_VBAP' in include MV45AFZZ. This is executed every time a user changes anything on a material (e.g. put in a material number) and hits return. Just raise your pop-up window there if the user puts in the particular material you are talking about. The material number is available in xvbap-matnr.
Hope that helps,
Michael

User Exit for correct ship-to Party while Creating Sales Order

Dear Friends,
Pls let me know which User Exit should I use to validate the Ship-to Party on the basis of Sold-to Party, while creating a sales order.
In other words we wish to make sure that the user gives the correct Ship-to party corresponding to the Sold-to party, while creating a sales order.
Regards,
Alok.

Dear Naveen,
Thanks for replying.
I do agree with you that SAP may validate the Ship-to Party in accordance with the Sold-to Party. But still the user may change that Ship-to Party value and save the Sales Order with a wrong Ship-to Party.
Here, my user wants a check/validation that no one should be able to save the sales order with wrong Ship-to Party other than the ones defined in Customer Master.
Hope you got the issue now.
Regards and thanks once again,
Alok.

Stock Reserve for customer while creating sales order

Hi Gurus,
In our scenario,i want to reserve my stock while saving the sales order for customer .when the next order will get placed for same article system should not be allow to use commited stock for pending sales order which is not yet get pgi.
_Scenario:-_
I raised order , say N0.20091076 with quantity 100 Boxes
I raised order , say N0.20091077 with quantity 50 boxes
Availability check was performed and system has confirmed the quantities as above for both the orders
Now i have gone to delivery and raised delivery for order N0. 20091077 ( OR.N0.20091076 --- 100 Boxes is still open).
but in the delivery i changed the quantity to 80 boxes instead of 50 as raised in the order N0.20091077 , but system is allowing to do PGI for order N0. 20091077 with 80 boxes. ( This means order N0.20091076 which contains 100 boxes is having deficit now).
Can i controll this that if i raise the oder with certain quantity and a particular batch then the system should not allow this quantity to be used by other order in the delivery/PGI irrespective of the customer .
Thanks & Regards,
Sunil

Hi
No need to do MB1B movement type 412 E
If include sales requirements is ticked in OVZ9 for the checking group in MMR and checking rule A (SD sales order) you cannot increase the qty in order 2
Example
Material X stock is 10 units
order A is created first for 5 and order B is created second for another 5
Include sales requirements is ticked in OVZ9 for A (sd sales order) combination
Now if you try to deliver order B with 6 units system will throw error as only 5 units is available
If you try to deliver order A also with 6 units system will throw error as only 5 units is available
So stocks are reserved as per sales orders
I already suggested you to do this sales requirements ito be ticked in OVZ9 in my first post but i thought it may not be very effective for the scenario described by you
But on testing it is found to be very effective provided backorder processing and rescheduling is not carried out
For your account determination error you have to check OBYC settings and also in t code OMWD whether the valuation grouping code 0001 has been assigned to your plant
If this not done in then during PGI you will face the same error
In normal circumstances during PGI only material doc is generated and this error is expected at that time
Since you are making a hard reservation during MB1B itself you are facing it as this transaction generates material doc
If you have already done 412 E you can reverse the same with MB1B movement type 411E
Regards
Raja

Error while creating sales order for a new company code

Hello SD Gurus,
The client wanted us to create a new Company Code, Plant, and Sales Organization. We created them. I extended the customer and material in QAS. Now, I'm trying to create one sales order in QAS but the system is throwing one error: "Maintain Profit Center Value in Custom Table in YSD_PROFIT_CNTR".
I googled for this error but found nothing. Could you please give me the solution asap. I need to prepare test script.
Thanks in advance
Regards,
Anwar

Dear Mohammed,
The error message itself states where is the issue. You need to maintain the profit center in table
YSD_PROFIT_CNTR. This is not SAP Standard provided solution. I guess during the time of implementation team has suggested to maintain the profit center in custom table.
If the table is"maintenance view" then you can check through SM30 and maintain the relevant entry. If not check if there is any transaction code with attached to this table. This you can check by going through SE93 and by entering Z* or ZSD* or Y* or YSD* and press F4, If the transaction code is starting with Z or Y it will open all the list of transaction codes. By going through the description of the transaction code. you can pick the right transaction code in case if any exists for this table.
Hope this information is useful to you.
Regards
Murali

Error while creating sales order for material with another DIVISION

Hello Friends,
I have a problem with my sales order creation.
I have defined a new sales area 0010 / 10 / 01. I have the sales order type assigned to this sales area. (in VOV8 for the sales order type, in the 'General Control' the 'item division' is flagged.
Now, I have created the sold to party XYZ with all the partner functions defaulted same as the sold to party for the sales area 0010 / 10 / 01.
NOW, I have the material ABC with the DIVISION 10 in the basic data. I have extended the material to my sales org & dist. channel & plant.
Now, while creating the sales order for my sales area 0010 / 10 / 01 , I enter the sold to party XYZ - it is OK. But when I enter the material ABC, I get the error - "SHIP TO PARTY IS NOT DEFINED FOR SALES AREA 0010 / 10 / 10"
Please help to resolve the issue.
Edited by: Vivek on Aug 13, 2009 9:04 AM

Hi
Common division for Material Master data will not work
Because in the material master Division is a field not an organizational unit
Means when you create MMR you will give sales org, DC, Plant as organizational units and then enter but not division
Division is a field maintained in basic data and sales org data 1
This is the reason in t code you will find in t code VOR2 Common division only customer and conditions but not materials
But in t code VOR1 Common DC ,customer conditions and materials all there are available (you can check these t codes)
Coming to your issue Item div is clecked in your order type
This means the division in MMR has the priority or control for that order type
Your header division is 01 ( taken from customers sales area) and item division is 10 (taken from MMR as per your post)
So it differs
To process this order with Item div is clecked in your order type you need to extend your Sold to party ABC to the sales area 0010/10/10 (the sales area where the division of the material falls)
or alternatively
There should be a customer say DEF created in sales area 0010/10/10 who will be a ship to party ( your error is also the same)
for your ABC that is sold to party in sales area 0010/10/01 where the order is registered
Hope yopu are getting it
ABC in sales area 0010/10/01 will have or should have ship to paty DEF in sales area 0010/10/10
or
ABC should operate in in sales area 0010/10/10 too
If item division is not ticked then these are not necessary as the header division 01 will be valid for all items and syatem will not look MMR at all for division
Regards
Raja

User Exit to check whether chapter id for Material and Plant combination is maintained while creating sales order

Similar Messages

Maybe you are looking for